diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/doc.md b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/doc.md deleted file mode 100644 index e9fe934fc55d981aec2225762b095d2cfd68a13d..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/doc.md +++ /dev/null @@ -1,1552 +0,0 @@ - - -# **O-RAN ALLIANCE Test and Integration Focus Group****Certification and Badging Processes and Procedures** - -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., Buschkauer Weg 27, 53347 Alfter, Germany -Register of Associations, Bonn VR 11238, VAT ID DE321720189 - -# --- 1 Contents - -| | | | -|----|------------------------------------------------------------------------------------------|----| -| 2 | Foreword ..... | 3 | -| 3 | Modal verbs terminology ..... | 3 | -| 4 | 1 Scope ..... | 4 | -| 5 | 2 References ..... | 4 | -| 6 | 2.1 Normative references ..... | 4 | -| 7 | 2.2 Informative references..... | 5 | -| 8 | 3 Definition of terms, symbols, and abbreviations..... | 5 | -| 9 | 3.1 Terms 5 | | -| 10 | 3.2 Symbols..... | 7 | -| 11 | 3.3 Abbreviations ..... | 7 | -| 12 | 4 Certification and Badging Overview..... | 7 | -| 13 | 4.1 Objectives..... | 7 | -| 14 | 4.2 Scope 8 | | -| 15 | 4.3 Entities Involved ..... | 10 | -| 16 | 4.3.1 O-RAN ALLIANCE ..... | 10 | -| 17 | 4.3.2 OTICs and the requesting entity(ies) ..... | 10 | -| 18 | 4.4 Outline of Processes and Technical Procedures..... | 11 | -| 19 | 5. Certification and badging processes..... | 12 | -| 20 | 5.1 General ..... | 12 | -| 21 | 5.1.1 Objectives of defining certification/badging processes ..... | 12 | -| 22 | 5.1.2 Principles..... | 12 | -| 23 | 5.1.3 Overview ..... | 13 | -| 24 | 5.1.4 O-RAN Certificates and Badges ..... | 14 | -| 25 | 5.2 Processes ..... | 14 | -| 26 | 5.2.1 O-RAN Certification and Badging process flow ..... | 14 | -| 27 | 5.2.2 Defining Certification/Badging and Set of Tests ..... | 16 | -| 28 | 5.2.3 Test platforms..... | 16 | -| 29 | 5.2.4 Identifying Applicable O-RAN certificate/badge and Tests ..... | 17 | -| 30 | 5.2.5 Executing Tests ..... | 17 | -| 31 | 5.2.6 Verifying Test Results..... | 17 | -| 32 | 5.2.7 Issuing Certificates/Badges ..... | 18 | -| 33 | 5.2.7.1 Certificate/Badge Reference Identifier..... | 18 | -| 34 | 5.2.8 Compliance Folder ..... | 18 | -| 35 | 5.2.9 Storing and Sharing of Summary Reports, Test reports and Measurement Results ..... | 19 | -| 36 | 5.2.10 SH/HW changes to certified/badged devices ..... | 20 | -| 37 | 5.2.11 Multi-vendor Scenario..... | 20 | -| 38 | 5.3 Defined and Available O-RAN Certificates and Badges..... | 20 | -| 39 | 6. O-RAN Conformance Certification Procedures ..... | 22 | -| 40 | 6.1 Subsystems and Interfaces ..... | 22 | -| 41 | 6.2 O-RAN Open Fronthaul interface of O-RU ..... | 22 | -| 42 | 6.3 O-RAN Open Fronthaul interface of O-DU..... | 23 | -| 43 | 6.4 O-RAN A1 services on A1 interface of Non-RT RIC ..... | 23 | -| 44 | 6.5 O-RAN A1 services on A1 interface of Near-RT RIC ..... | 24 | -| 45 | 7. O-RAN IOT Badging Procedures ..... | 24 | -| 46 | 7.1 Subsystems and Interfaces ..... | 24 | - -| | | | -|----|--------------------------------------------------------------------|----| -| 1 | 7.2 O-RAN Open Fronthaul interface ..... | 25 | -| 2 | 7.3 X2 interface ..... | 26 | -| 3 | 7.4 F1 interface ..... | 26 | -| 4 | 7.5 Xn interface ..... | 26 | -| 5 | 7.6 A1 services on A1 interface ..... | 26 | -| 6 | 8. O-RAN E2E Badging Procedures ..... | 27 | -| 7 | Annex A (informative): Certification application ..... | 28 | -| 8 | Annex B (informative): Compliance folder ..... | 29 | -| 9 | Annex C (normative): Trademark License Agreement ..... | 30 | -| 10 | Annex D (normative): Machine readable results artifact ..... | 34 | -| 11 | Annex (informative): Change history/Change request (history) ..... | 39 | - -# --- 12 Foreword - -13 This Technical Specification (TS) has been produced by TIFG (Test and Integration Focus Group) of the O- -14 RAN ALLIANCE. - -15 The content of the present document is subject to continuing work within O-RAN and may change following -16 formal O-RAN approval. Should the O-RAN ALLIANCE modify the contents of the present document, it will -17 be re-released by O-RAN with an identifying change of version date and an increase in version number as -18 follows: - -19 version xx.yy.zz - -20 where: - -21 xx: the first digit-group is incremented for all changes of substance, i.e. technical enhancements, -22 corrections, updates, etc. (the initial approved document will have xx=01). Always 2 digits with -23 leading zero if needed. - -24 yy: the second digit-group is incremented when editorial only changes have been incorporated in the -25 document. Always 2 digits with leading zero if needed. - -26 zz: the third digit-group included only in working versions of the document indicating incremental -27 changes during the editing process. External versions never include the third digit-group. Always 2 -28 digits with leading zero if needed. - -29 - -# --- 30 Modal verbs terminology - -31 In the present document "**shall**", "**shall not**", "**should**", "**should not**", "**may**", "**need not**", "**will**", "**will not**", -32 "**can**" and "**cannot**" are to be interpreted as described in clause 3.2 of the O-RAN Drafting Rules (Verbal -33 forms for the expression of provisions). - -34 "**must**" and "**must not**" are **NOT** allowed in O-RAN deliverables except when used in direct citation. - -35 - -# 1 Scope - -The present document describes the certification and badging processes and associated detail technical procedures that Open Testing and Integration Centre (OTIC) [1] and other testing entities should adopt to: - -- 1) Verify compliance of device under test (DUT) using O-RAN interface and/or service with applicable implementation requirements based on O-RAN conformance test specifications (**conformance certification**), -- 2) Assess interoperability of DUT pairs using O-RAN interfaces based on Interoperability Test (IOT) specifications (**IOT badging**), -- 3) Assess end-to-end system integration of SUT using O-RAN interfaces based on E2E test specifications (**E2E badging**). - -The present main document consists of the following subsidiary documents: - -- O-RAN.TIFG.TS.Cert-Badge.1 contains O-RAN Certificate and Badge Summary Reports -- O-RAN.TIFG.TS.Cert-Badge.2 contains template of O-RAN Certificate and Badge Test Report -- O-RAN.TIFG.TS.Cert-Badge.3 contains JSON scheme for storing machine-readable test results -- O-RAN.TIFG.TS.Cert-Badge.4 contains O-RAN Certification and Banding Profiles (CB-Profiles) -- O-RAN.TIFG.TS.Cert-Badge.5 contains O-RAN Certification and Badging ICS Proformas (CB-ICS Proformas) - -# 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.TIFG.CGofOTIC.0: “Criteria and Guidelines of Open Testing and Integration Centre” -- [2] O-RAN.TIFG.TS.E2E-Test.0: “End-to-end Test Specification” -- [3] O-RAN.WG1.TS.OAD: “O-RAN Architecture Description” -- [4] 3GPP TS 38.300: “NR; NR and NG-RAN Overall Description; Stage 2” -- [5] 3GPP TS 38.401: “NG-RAN; Architecture description” - -- 1 [6] 3GPP TS 37.340: “Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; -2 Stage 2” -- 3 [7] ISO 3534-2:2006: “Statistics — Vocabulary and symbols — Part 2: Applied statistics” -- 4 [8] O-RAN.WG11.TS.STS: “O-RAN Security Test Specifications” -- 5 - -###### 6 2.2 Informative references - -7 References are either specific (identified by date of publication and/or edition number or version number) -8 or non-specific. For specific references, only the cited version applies. For non-specific references, the latest -9 version of the referenced document (including any amendments) applies. In the case of a reference to a -10 3GPP document, a non-specific reference implicitly refers to the latest version of that document in Release -11 18, or the latest 3GPP release prior to Release 18 that includes that document. - -12 NOTE: While any hyperlinks included in this clause were valid at the time of publication, O-RAN -13 cannot guarantee their long-term validity. - -14 The following referenced documents are not necessary for the application of the present document, but -15 they assist the user with regard to a particular subject area. - -- 16 [i.1] 3GPP TR 21.905: “Vocabulary for 3GPP Specifications” -- 17 - -###### --- 18 3 Definition of terms, symbols, and abbreviations - -###### 19 3.1 Terms - -20 For the purposes of the present document, the terms [given in [i.1] and the following] apply: - -21 **Badging:** the process by which interoperability for a pair of products or E2E system integration for a group of -22 products are assessed, and the involved products are authorized to carry a specific set of credentials that -23 indicate successful results. Badging information, which is common to all products involved, will include -24 information on all products (including hardware version and software version) which were involved in -25 interoperability testing or E2E system testing. - -26 **Blueprint:** the set of inputs which is used to describe a specific deployment of O-RAN-based system or -27 solution from several aspects. These aspects include the specification of the O-RAN deployment at the system -28 level (e.g. architecture, performance metrics) as well as subsystem level and the interfaces between the -29 specified subsystems. This would then allow definition and documentation of the testing methodology and -30 the test cases using the blueprint specification. - -31 **Catalogue:** the centralized database providing basic (non-sensitive) information about all issued certificates -32 and badges. This catalogue is publicly available on the O-RAN ALLIANCE web site and maintained by O-RAN -33 ALLIANCE. - -34 **Certification:** the process of verifying that the implementation of product, interface, service, etc. complies -35 with the relevant requirements in O-RAN specifications. Such implementation is authorized to carry a specific -36 set of credentials that indicate that it is conformant. - -- 1 **Certification and Badging ICS proforma (CB-ICS proforma):** An overview of all mandatory/optional/ -2 conditional functions and capabilities defined in base specification(s)/profile and, if exists, in O-RAN -3 Certification and Badging profile, and tabular summary of related tests defined in the test specification(s). It -4 helps vendors ensure that their products meet the necessary requirements for O-RAN Certificates and Badges. -5 When the implementation is done, vendor declares which functions and capabilities have been -6 implemented/supported, and so it becomes Certification and Badging ICS. -- 7 -8 **Certification and Badging ICS (CB-ICS):** A statement made by the vendor of an implementation stating which -9 functions and capabilities have been implemented/supported for the purpose of O-RAN Certificate or Badge. -10 It helps identify the applicable tests. The Certification and Badging ICS (CB-ICS) is attached to O-RAN -11 Certificate, IOT Badge or E2E Badge. -- 12 -13 **Certification and Badging profile (CB-profile):** For the purpose of O-RAN Certification and Badging, the CB- -14 profile may constrain the existing options in base specification(s)/profile, and shall not impose requirements -15 that conflict with the existing requirements in base specification(s)/profile (e.g. a function/capability/ -16 parameter mandatory in the base specification shall not be optional in the profile; or adding new -17 function/capability/parameter that does not exist in the base specification is not allowed). -- 18 **Compliance folder:** the set of detailed measurement results demonstrating an O-RAN ALLIANCE device's -19 compliance with the Badging and Certification Criteria, which includes the ICS, test reports, summary reports, -20 technical documentation, change management documentation and certification information. -- 21 **Implementation Conformance Statement (ICS):** statement of conformance provided by requesting -22 entity(ies) who bring their DUTs/SUT for badging and/or certification service, which is the key element in -23 determining which test cases will be executed on a particular product. -- 24 **Logo:** O-RAN approved logo for certification and badging differentiating products/solutions that passed -25 certification and/or badging. The logo is a part of O-RAN certificate or badge. The logo is intended to be -26 utilized for marketing purposes at websites, brochures, printed at the product itself, etc. -- 27 **Measurement results:** a collection of detailed measurement results collected during the certification or -28 badging including logs, screenshots, packet captures, etc. The file format of measurement results is not -29 specified and unified and depends on used test and measurement equipment and tools. -- 30 **MVP:** the minimum viable plan to be tested for Certification and Badging. -- 31 **Repeatability:** the consistency of consecutive test results with a certain degree of precision obtained under -32 the following conditions: conducting the same test procedure on the same DUT/SUT at the same location -33 (e.g., laboratory) by the same tester(s) using the same measuring and test equipment, tests conducted -34 within short time intervals, as defined in ISO 3534-2 [7], clause 3.3. The measure of precision is usually -35 expressed as the standard deviation or coefficient of variation of the test results. -- 36 **Reproducibility:** the consistency of test results with a certain degree of precision obtained under the -37 following conditions: conducting the same test procedure on the same DUT/SUT in different location (lab) -38 and/or by the different tester(s) and/or using different measuring and test equipment, as specified in ISO -39 3534-2 [7], clause 3.3. The measure of precision is usually expressed as the standard deviation or -40 coefficient of variation of the test results. -- 41 **Test report (O-RAN Certificate and Badge Test Report):** provides detailed information about DUT/SUT, test -42 setup configuration, assessment of measured KPIs, gap analysis, evidence of meeting pass criteria, etc. The -43 unified format of document (template) is used to ensure reusability and sharing of information. The test -44 report is a part of O-RAN certificate or badge. - -1 **Summary report (O-RAN Certificate and Badge Summary Report):** provides a summary of O-RAN -2 certification or badging testing including basic information about issued O-RAN certificate or badge, contacts -3 to all involved entities, list of awarded DUTs, list of used test and measurement equipment and tools, list of -4 applicable and conducted tests, etc. The unified format of document (template) is used to ensure reusability -5 and sharing of information. The Summary report is a part of O-RAN certificate or badge. - -6 - -###### 7 3.2 Symbols - -8 Void - -9 - -###### 10 3.3 Abbreviations - -11 For the purposes of the present document, the abbreviations [given in [i.1] and the following] apply: - -| | | | -|----|-------------|----------------------------------------------------------------| -| 12 | CB-ICS | Certification and Badging Implementation Conformance Statement | -| 13 | CB-Profile | Certification and Badging Profile | -| 14 | DUT | Device Under Test | -| 15 | E2E | End-to-End | -| 16 | FFS | For Future Study | -| 17 | ICS | Implementation Conformance Statement | -| 18 | IOT | Interoperability Testing | -| 19 | IUT | Interface under Test | -| 20 | MVP | Minimum Viable Plan | -| 21 | Near-RT RIC | Near-Real Time RAN Intelligent Controller | -| 22 | Non-RT RIC | Non-Real Time RAN Intelligent Controller | -| 23 | O-CU | O-RAN Central Unit | -| 24 | O-DU | O-RAN Distributed Unit | -| 25 | O-RU | O-RAN Radio Unit | -| 26 | OTIC | Open Testing and Integration Centre | -| 27 | PTC | Profile Test Configuration | -| 28 | RIC | RAN Intelligent Controller | -| 29 | SMO | Service Management and Orchestration | -| 30 | SUT | System Under Test | -| 31 | TIFG | O-RAN Test and Integration Focus Group | -| 32 | | | - -###### --- 33 4 Certification and Badging Overview - -###### 34 4.1 Objectives - -35 The motivation of O-RAN certification and badging is to minimize the repetition of fundamental and common -36 tests which should be performed to verify and validate O-RAN compliant products, systems, and solutions -37 before their deployment in operator networks thus reduce the test effort. The idea is to test only once and -38 reuse/adopt the test results multiple times whenever it is possible. In addition, the use of O-RAN certificates - -1 and badges for network components can be a very important way to promote the O-RAN ecosystem and to -2 encourage implementation and testing of O-RAN products, systems and solutions and their deployment in -3 operator networks. - -4 The purpose of **O-RAN conformance certification** is to verify that a product, interface, service, etc. complies -5 with the relevant requirements in O-RAN specifications through a set of O-RAN defined conformance test -6 cases using unified test procedures and templates for sharing of results. The O-RAN certificate is awarded to -7 a product for one or more interfaces and/or services (e.g. O-RU OpenFH, Near-RT RIC A1 services). - -8 The purpose of **O-RAN IOT badging** is to prove interoperability of a pair of products based on the most -9 fundamental and operator neutral (common) features and parameters through a set of O-RAN defined -10 interoperability tests using unified test procedures and templates for sharing of results. In addition, O-RAN -11 IOT badging can also provide an indication of interoperability of a pair of products based on -12 optional/advanced and operator specific features and parameters through a set of O-RAN defined -13 interoperability tests using unified test procedures and templates for sharing of results. The O-RAN IOT badge -14 is awarded to both products in the DUT pair and is applicable for an O-RAN interface. - -15 The purpose of **O-RAN end-to-end badging** is to demonstrate and verify that a (multi-vendor) end-to-end -16 system meets minimum requirements in terms of functionality, security and other mandatory features -17 defined in related O-RAN test specifications. In addition, O-RAN end-to-end badging can also provide an -18 indication of end-to-end performance and other optional end-to-end capabilities through a set of O-RAN -19 defined end-to-end tests using unified test procedures and templates and data formats for sharing of results. -20 The O-RAN E2E badge is awarded to all products in the SUT and is applicable to the specific scope tested. - -21 With certification and badging in place, operator awareness of an O-RAN-based product, system or solution -22 is expected to increase, and the operator own testing is expected to reduce because the common tests can -23 be performed only once and would not need to be repeated. - -24 O-RAN certification and badging may also be helpful for vendors as it provides some level of evidence that -25 their O-RAN-based products, systems and solutions work, which could be used to promote their products, -26 systems and solutions to operators. Further, for vendors looking for other vendors to interoperate with, -27 certification and badging may also be beneficial to increase acceptance from other vendors. - -28 O-RAN certification and badging should not be used as a substitute for operator-specific testing of O-RAN -29 based products, systems and solutions prior to deployment in operator networks. O-RAN certificate and -30 badge do not mean all the necessary tests have been performed and passed, and O-RAN certified and/or -31 badged products can be automatically deployed in an operator network without any additional testing. -32 Rather, O-RAN certification and badging can improve operator confidence in their chosen O-RAN based -33 blueprint and can reduce the complexity and duration of pre-deployment testing. - -## 34 4.2 Scope - -35 The document defines and unifies the processes, procedures, templates, data format, etc. to ensure -36 reusability and sharing of the test results and repeatability of the executed tests. The required tests for -37 issuing specific O-RAN certificate/badge are decoupled from this document. The document only references -38 O-RAN test specification(s) (but without mentioning a specific version) which shall be used for issuing of -39 specific O-RAN certificate/badge. All the test related information such as test description, test applicability, -40 test procedure, test setup and configuration, expected results, recorded KPIs, pass/fail criteria are defined in -41 the O-RAN test specifications and shall be properly followed. If needed, the specific modifications, -42 clarifications and alignments of O-RAN test specifications required only for the purpose of O-RAN certificates -43 and badges are defined in this document. It is also assumed that the user/tester has properly read and - -1 understood the related O-RAN test specifications. In case of any unclarity in O-RAN test specification, specific -2 O-RAN WG/FG owning O-RAN test specification shall be contacted to resolve the unclarity. - -3 - -4 For certification and badging purposes, OTICs and requesting entity(ies) should use the latest published -5 version of this document. The summary report and test report shall include the versions of this document -6 and relevant O-RAN test specification used to perform O-RAN certification or badging. Each O-RAN certificate -7 or badge shall only be issued against a single version of the corresponding test specification which is indicated -8 in the summary report and test report (i.e. a certificate/badge cannot be issued based on mixing tests from -9 multiple test specification versions). - -10 - -11 The certification and badging described in this document defines the processes and associated technical -12 procedures in the following areas: - -- 13 • Compliance verification of DUT using O-RAN interfaces and/or services with applicable -14 implementation requirements based on O-RAN conformance test specifications (**conformance** -15 **certification**) -- 16 • Interoperability assessment of DUT pairs using O-RAN interfaces based on IOT test specifications (**IOT** -17 **badging**) -- 18 • E2E system integration assessment of SUT using O-RAN interfaces based on E2E test specifications -19 (**E2E badging**) - -20 - -21 The reason to use the term “certification” for conformance testing and “badging” for interoperability and -22 E2E system testing is as follows: - -- 23 • Conformance tests are controllable involving a single DUT with its supported interfaces and services. -24 The testing verifies whether that DUT complies with the applicable requirements from technical -25 specifications (e.g. open fronthaul interface specification); -- 26 • IOT and E2E system tests have some variability as they involve multiple DUTs (from single or multiple -27 vendors) and the results may depend on the DUT/SUT combinations, deployment blueprints and test -28 profiles. - -29 - -30 Figure 4.2-1 provides an illustration for the above-described concept of O-RAN certification and badging. - -31 - -![](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) - -| | | | | | | -|--------------------------|-------------------------------------------------------------------------------|---------------------------------------|-----------------------------------------|----------------------------------------------|------------------------------------------| -| Objectives | Compliance Verification and Interoperability & E2E Use Case/System Assessment | | | | | -| Technical Specifications | Technical Specifications (normative) | | | | | -| | Open Interfaces / APIs | Open Subsystems | O-RAN Use Cases 1 | Open Subsystems & Interfaces / APIs | E2E System | -| Assess implementation | Compliance Verification | | Interoperability and E2E Assessment | | | -| Test specs | Conformance Test Specifications (WGs) | | Use Cases Test Spec (WGs) 1 | IOT Specifications (WGs) | E2E System Testing Specifications (TIFG) | -| Test objects | Single DUT and Interface/API | Subsystem – whitebox, O-cloud, stacks | SUT inc. RICs & I/Fs, APIs 1 | 1 Pair of DUTs with a single Interface / API | SUT with More than 2 DUTs & I/Fs, APIs | -| Testing Outcomes | Certification | | Certification or Badging 1 | | Badging | - -1 this is still to be discussed within TIFG - -1 -2 -3 -4 -5 - -**Figure 4.2-1: O-RAN certification and badging concept** - -Whether or not and how to address 3GPP functional and performance testing for the underlying components and interfaces is for future study (FFS). - -## 4.3 Entities Involved - -### 4.3.1 O-RAN ALLIANCE - -In terms of certification and badging, O-RAN Test and Integration Focus Group (TIFG) only specifies the processes and associated detailed technical procedures, identifies the relevant O-RAN test specifications and test cases specified by O-RAN WGs/FGs, including end-to-end tests defined by O-RAN TIFG [2]. - -### 4.3.2 OTICs and the requesting entity(ies) - -O-RAN certification and badging can only be performed in qualified O-RAN Open Testing and Integration Centers (OTICs), and consequently the O-RAN certificates and badges (with O-RAN approved logos for certification and badging) can only be issued by OTICs. - -Under no circumstances are OTICs under the charter or governed/sponsored by O RAN/TIFG. It is OTICs that will take full responsibility on all certification/badging related activities including certification/badging implementation, verification/assessment as well as certificate/badge issuance. - -O-RAN certificates and badges (with O-RAN approved logos for certification and badging) can be awarded to a product provided by any requesting entity with or without O-RAN membership (O-RAN Member, O-RAN Contributor, O-RAN Academic Contributor). OTICs cannot be the requesting entity for its own certification/badging. - -Further, the requesting entity can be the product original equipment vendors/manufacturers (OEMs), or product owners that have acquired and owned the products. Upon the completion of certification/badging and then the award of O-RAN certificate/badge, the requesting entity is the copyright co-holder of summary and test reports, and can use certificate/badge logo for its marketing, - -1 In case the requesting entity is the product owner but not the original equipment vendor/manufacturer, the -2 following extra steps shall be followed: - -- 3 • The product owner should inform the original equipment vendor/manufacturer of the certification/ -4 badging request even though the consent of such request from the original product vendor/ -5 manufacturer is not required, -- 6 • The product owner does not need to share the test results/reports with the original product -7 vendor/manufacturer, -- 8 • The original product vendor/manufacturer cannot use certificate/badge logo for its marketing -9 without the consent of the product owner who requests for the O-RAN certification/badging, - -10 In case an O-RAN certificate or badge is awarded to a product provided by a requesting entity without O-RAN -11 membership, the legally binding “Trademark License Agreement” (see Annex C) between O-RAN ALLIANCE -12 and that requesting entity without O-RAN membership shall be signed first. The “Trademark License -13 Agreement” is signed only once when the first O-RAN certificate or badge is awarded. The list of entities with -14 signed “Trademark License Agreement” is maintained on [O-RAN wiki](#), and shall be checked by the OTIC before -15 awarding an O-RAN certificate or badge to any entity without O-RAN membership. If an entity is not listed, -16 the entity shall contact O-RAN ALLIANCE (directly or through OTIC) to sign the “Trademark License -17 Agreement”. - -18 In case an O-RAN certificate or badge is awarded to a product provided by an entity with O-RAN membership, -19 no additional agreement is needed. The trademark license policies are part of O-RAN membership agreement -20 signed by each O-RAN Entity. The list of entities with O-RAN membership is available on the [O-RAN wiki](#). - -21 OTICs provide a collaborative, open, and impartial working environment, and the criteria and guidelines for -22 OTICs are specified in [1]. These guidelines stipulate that: - -- 23 • O-RAN summary reports, test reports and detailed measurement results can be freely accessed by -24 O-RAN operator members for the purpose of evaluating the equipment for use in their networks -- 25 • An OTIC may or may not choose to provide certification and/or badging services. If an OTIC intends -26 to provide O-RAN certification/badging services, it is mandatory for them to follow the processes and -27 associated technical procedures specified in this document. -- 28 • Prerequisites for OTICs to be able to provide certification/badging services are defined in [1]. - -29 O-RAN allows the testing to be also performed outside of the OTICs using O-RAN test specifications and -30 following the certification and badging procedures as defined in this document. However, such test results -31 cannot carry an O-RAN certificate or O-RAN badge with O-RAN approved logos but may state that their -32 equipment has been "tested according to O-RAN Certification and Badging Process and Procedures -33 document." - -34 OTICs may require certain pre-requisite testing to be done by the requesting entity(ies) before the start of -35 the certification/badging process. Some examples are illustrated as follows - -- 36 • 3GPP compliance validation as a prerequisite for any O-RAN conformance certification -- 37 • O-RAN conformance certification as a prerequisite for O-RAN IOT / E2E badging - -###### 38 4.4 Outline of Processes and Technical Procedures - -39 Certification and badging include various processes and technical procedures. - -40 Clause 5 will define these processes in following areas: - -- 1       • Describe the Certification and Badging Profile and ICS Proforma/ICS -- 2       • Describe the process of verifying certification/badging test results and responsible entity -- 3       • Describe how to issue a certificate/badge -- 4       • Describe how to share O-RAN summary reports, test reports and detailed measurement results -- 5       • Describe how to improve/enhance the certification/badging process and what triggers a new release -- 6           of this document (e.g. WG spec 1.0 to 2.0, O-RAN Software Community Bronze release to Cherry) -- 7 Corresponding to processes to be described in Clause 5, the detail technical procedures introduced in the -- 8 following clauses include identifying all relevant test specifications given by various O-RAN WGs/FGs in terms -- 9 of conformance, IOT, and E2E verification of underlying subsystems and interfaces. -- 10 Clause 6 defines the procedures related to conformance certification that shall be performed on the O-RAN -- 11 interface/service of DUT. -- 12 Clause 7 defines the procedures related to the IOT badging that shall be performed on the pair of DUTs -- 13 connected via O-RAN interface/service. -- 14 Clause 8 defines the procedures related to E2E badging that are applicable for the operator deployment -- 15 scenario (e.g. LTE, 5G NSA, or 5G SA). -- 16 - -###### --- 17 5. Certification and badging processes - -###### 18 5.1 General - -###### 19 5.1.1 Objectives of defining certification/badging processes - -20 The objective is to have in place some level of uniformity on the certification/badging processes in order to: - -- 21       • Ensure quality and consistency of the certification/badging service provided by different OTICs. -- 22       • Align procedures that users of the certification/badging service (both requesting entity(ies) bringing -- 23           in DUT(s)/SUT(s) for certification/badging, and operators requesting access to summary reports, test -- 24           reports and detailed measurement results of certified/badged DUTs/SUT) experience at different -- 25           OTICs. - -###### 26 5.1.2 Principles - -27 The certification/badging process adheres to the following principles: - -- 28       • A distributed approach is adopted in which (a) roles pertaining to certification/badging are allocated -- 29           to OTICs and (b) related details are left to OTICs' discretion and responsibility. Rather than having -- 30           rigorous centralized O-RAN control and management, this approach helps avoid imposing heavy -- 31           requirements and allows freedom of operation to OTICs. However, a centralized approach is also -- 32           adopted where required, e.g. to ensure quality of certification/badging, sharing of summary reports, -- 33           test reports and detailed measurement results, etc. -- 34       • Defining certification/badging process elements to address near-term needs of the community, while -- 35           also establishing a framework that can evolve and scale with the ecosystem growth, i.e. this Clause -- 36           can evolve over time. - -- O-RAN will, as necessary, issue new versions of its functional specifications. As a result, O-RAN may determine that it will launch an updated version of its certification/badging program. -- O-RAN will, as necessary, determine that an existing version of its functional specification is no longer viable and should be taken out of service for product development and certification/badging. As a result, O-RAN may determine when the specification is to be taken out of service. - -### 5.1.3 Overview - -Figure 5.1-1 shows the relationship between O-RAN and OTICs. - -![Diagram showing the relationship between O-RAN TIFG, OTICs, and Requesting entity(ies). O-RAN TIFG provides a framework, defines tests, provides feedback, and resolves ambiguities for OTICs. OTICs create a catalogue of test results for a Database. Requesting entity(ies) store detailed test results/logs in a Compliance folder.](410562339ce067fdc6fa41940c118658_img.jpg) - -``` - -graph LR - subgraph O_RAN_TIFG [O-RAN TIFG] - direction TB - T1[1. Provide certification/badging process framework] - T2[2. Define tests for certification/badging] - T3[3. Provide feedback on the process and tests] - T4[4. Resolve unclarity, inconsistency, and ambiguity] - end - - subgraph OTICs [OTICs] - direction TB - T5[5. Create catalogue of test results] - end - - subgraph Requesting_entity [Requesting entity(ies)] - direction TB - T6[5. Store detailed test results/logs] - end - - DB[(Database)] - CF[(Compliance folder)] - - O_RAN_TIFG -- 1, 2, 3, 4 --> OTICs - OTICs -- 5 --> DB - Requesting_entity -- 5 --> CF - -``` - -Diagram showing the relationship between O-RAN TIFG, OTICs, and Requesting entity(ies). O-RAN TIFG provides a framework, defines tests, provides feedback, and resolves ambiguities for OTICs. OTICs create a catalogue of test results for a Database. Requesting entity(ies) store detailed test results/logs in a Compliance folder. - -**Figure 5.1-1: Relationship between O-RAN and OTICs** - -1. O-RAN provides the certification and badging process framework in this document. OTICs should follow the processes described in this document. -2. O-RAN defines tests for certification/badging. Further description is provided in Clause 5.2.1. -3. OTICs can provide feedback to O-RAN on the certification/badging process and tests for certification/badging, making it a closed loop operation. -4. O-RAN TIFG is the governing body to resolve any un-clarity, inconsistency, and ambiguity in the present document. -5. OTICs create a catalogue or database to share certification test reports with the vendors whose subsystems/systems were tested, operators, and other OTICs. Detailed measurement results should be stored by the requesting entity(ies) themselves as evidence. Further description on sharing of summary reports, test reports and detailed measurement results is provided in Clause 5.2.8 and on SW/HW update in Clause 5.2.9. - -Figure 5.1-2 shows the certification/badging process framework. This is a general framework to be followed with O-RAN certification/badging. - -![Flowchart of the certification/badging process framework: Identify applicable tests -> Execute tests -> Verify test results -> Issue certificate/badge -> Share test results.](e9d825d87c5f85c8dba0664eace96ef4_img.jpg) - -``` - -graph LR - A[Identify applicable tests] --> B[Execute tests] - B --> C[Verify test results] - C --> D[Issue certificate/badge] - D --> E[Share test results] - -``` - -Flowchart of the certification/badging process framework: Identify applicable tests -> Execute tests -> Verify test results -> Issue certificate/badge -> Share test results. - -**Figure 5.1-2: Certification/badging process framework –parts to be performed by OTICs** - -### 5.1.4 O-RAN Certificates and Badges - -O-RAN certificates or badges issued by OTICs are comprised of: - -- **Logo of the O-RAN certificate or badge**, which the product that is awarded the certificate or badge can display on the product or in corresponding marketing material, e.g. website, brochure, etc. -- **Summary report (O-RAN Certificate and Badge Summary Report)** providing a summary of O-RAN certification or badging testing. The unified structure and format of document (using the same file format as associated template O-RAN.TIFG.TS.Cert-Badge.1) is used to ensure reusability and sharing of the information. If CB-ICS Proforma is specified for a particular O-RAN certificate or badge, the Certification and Badging ICS shall be attached to the summary report. -- **Test report (O-RAN Certificate and Badge Test Report)** providing details of O-RAN certification or badging testing. The unified format of document (associated template O-RAN.TIFG.TS.Cert-Badge.2) is used to ensure reusability and sharing of the information -- Detailed **measurement results** providing a collection of detailed measurement results collected during the certification or badging including logs, screenshots, packet captures, etc. which are captured from DUT/SUT or/and from test and measurement equipment and tools. The file format of measurement results is not specified and unified and depends on used DUT/SUT and test and measurement equipment and tools. - -The summary and test reports shall be encrypted, and editing shall be restricted to avoid unauthorized editing and modification of the reports. The summary and test reports shall be digitally signed by OTIC to provide assurance about integrity, validity, and authenticity of the reported data. It is recommended that the reports be co-signed by participating entity(ies) to confirm their involvement and their approval of reported data. The public key certificate (identity certificate) associated with the digital signature shall be valid and issued by a trusted certificate authority. - -## 5.2 Processes - -### 5.2.1 O-RAN Certification and Badging process flow - -O-RAN Certification and Badging (C&B) process flow with Certification and Badging profile (CB-Profile) and Certification and Badging ICS proforma (CB-ICS proforma) is illustrated in Figure 5.2.1-1. Note that CB-Profile is optional and is used only if necessary. - -![Flowchart of the O-RAN Certification and Badging process. The process starts with 'Base specification or Profile' leading to 'Implementation (DUT/SUT)' via 'Implementation details'. 'Implementation (DUT/SUT)' leads to 'Certification and badging ICS Proforma' via 'References to tests'. 'Implementation (DUT/SUT)' also leads to 'Test Specification' via 'References to tests'. 'Test Specification' leads to 'Testing' via 'Tests'. 'Testing' leads to 'O-RAN Certificate/ Badge' via 'Testing support for functions/capabilities'. 'Certification and badging ICS Proforma' leads to 'Certification and badging ICS' via 'Self-declared support for functions/capabilities'. 'Certification and badging ICS' leads to 'O-RAN Certificate/ Badge' via 'Self-declared support for functions/capabilities'. 'Certification and badging ICS' also leads to 'Selection and parametrization of applicable tests' via 'Self-declared support for functions/capabilities'. 'Selection and parametrization of applicable tests' leads to 'Testing' via 'Tests'. 'Certification and Badging Profile (optional, if necessary)' is shown as a dashed box between 'Base specification or Profile' and 'Implementation (DUT/SUT)'.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) - -Flowchart of the O-RAN Certification and Badging process. The process starts with 'Base specification or Profile' leading to 'Implementation (DUT/SUT)' via 'Implementation details'. 'Implementation (DUT/SUT)' leads to 'Certification and badging ICS Proforma' via 'References to tests'. 'Implementation (DUT/SUT)' also leads to 'Test Specification' via 'References to tests'. 'Test Specification' leads to 'Testing' via 'Tests'. 'Testing' leads to 'O-RAN Certificate/ Badge' via 'Testing support for functions/capabilities'. 'Certification and badging ICS Proforma' leads to 'Certification and badging ICS' via 'Self-declared support for functions/capabilities'. 'Certification and badging ICS' leads to 'O-RAN Certificate/ Badge' via 'Self-declared support for functions/capabilities'. 'Certification and badging ICS' also leads to 'Selection and parametrization of applicable tests' via 'Self-declared support for functions/capabilities'. 'Selection and parametrization of applicable tests' leads to 'Testing' via 'Tests'. 'Certification and Badging Profile (optional, if necessary)' is shown as a dashed box between 'Base specification or Profile' and 'Implementation (DUT/SUT)'. - -1 - -2 **Figure 5.2.1-1: O-RAN Certification and Badging process flow diagram with CB-Profile and CB-ICS** - 3 **proforma** - -4 For the purpose of O-RAN certification and badging and to facilitate O-RAN productionization, the **O-RAN** - 5 **Certification and Badging profile** (CB-Profiles are defined in O-RAN.TIFG.TS.Cert-Badge.4) may be used to - 6 constrain the existing options in base specification(s)/profile, but shall not impose requirements that conflict - 7 with the existing requirements in base specification(s)/profile (e.g. a function/capability/parameter - 8 mandatory in the base specification shall not be optional in the profile; or adding new - 9 function/capability/parameter that does not exist in the base specification is not allowed. - -10 NOTE: The need for CB Profiles is expected to be relatively rare and will only be used to support the - 11 awarding of meaningful O-RAN certificates and badges. - -12 The **Certification and Badging ICS proforma** (CB-ICS proformas are defined in O-RAN.TIFG.TS.Cert-Badge.5) - 13 provides overview of all mandatory/optional/ conditional functions and capabilities defined in base - 14 specification(s)/profile and, if exists, in O-RAN Certification and Badging profile, and tabular summary of - 15 related tests defined in the test specification(s). It helps vendors ensure that their products meet the - 16 necessary requirements for O-RAN certificates and badges. It helps to unambiguously and quickly identify - 17 the mandatory/optional/conditional functions and capabilities. It also includes references to base - 18 specification(s) where the implementation details are specified, and references to related tests in test - 19 specification(s). The CB-ICS proforma uses a unified and machine-readable format. - -20 Vendors make an implementation (DUT/SUT) based on the base specification(s)/profile(s) and, if exists, on - 21 the CB-Profile. When the implementation is done, vendors shall use CB-ICS proforma to declare which - 22 functions and capabilities have been implemented/supported. When filled in, CB-ICS proforma becomes - 23 Certification and Badging ICS (CB-ICS). - -24 NOTE: If CB-ICS proforma is not available, the supported/implemented functions and capabilities should - 25 be declared by other means. - -26 The **Certification and Badging ICS (CB-ICS)** provides an overview of the implemented and supported - 27 functions and capabilities for the purpose of O-RAN certificates and badges. It helps testers to unambiguously - 28 select and parameterize the applicable tests based on functions and capabilities stated as implemented and - 29 supported by the vendors. Tests are applicable for functions and capabilities specified as mandatory - 30 (required) in base specification(s)/profile(s) and, if exists, in CB-Profile, and for optional functions and - 31 capabilities declared as implemented/supported by vendor(s). - -32 The Certification and Badging ICS proforma shall contain the following data: - -- Item – a unique identifier to identify the specific function/capability/parameter -- Description – a brief text description of the specific function/capability/parameter -- References - reference to clause(s) in base specification(s) describing the implementation details for each function or capability -- Status - whether the function or capability is mandatory/optional/conditional to be implemented/supported for the purpose of O-RAN Certificate or Badge -- Support – yes/no selection to allow the requesting entity to indicate if the item is supported/implemented or not -- Relate tests - reference to test(s) that shall be conducted to verify the implementation/support of specific capability or function. If no test is identified to verify the specific capability or function, this field will be blank. - -The CB-Profiles (O-RAN.TIFG.TS.Cert-Badge.4) and CB-ICS proformas (O-RAN.TIFG.TS.Cert-Badge.5) are defined as standalone subsidiary documents to the present main document in the O-RAN TIFG in cooperation with the relevant WG(s)/FG(s). - -For O-RAN conformance certificates, one CB-Profile and one CB-ICS proforma are defined for each device and interface/service under test, e.g. Open FH O-RU, Open FH O-DU. For O-RAN IOT Badge, one CB-Profile and one CB-ICS proforma are defined for each interface/service under test including both devices in the pair, e.g. Open FH (including both O-RU and O-DU). For O-RAN E2E Badge, one CB-Profile and one CB-ICS proforma are defined for the whole system under test (not to individual devices and interfaces) and to E2E functionalities and capabilities. - -If CB-ICS proforma is specified for a particular O-RAN certificate or badge, the Certification and Badging ICS (CB-ICS) is a part of O-RAN certificate or badge and shall be attached to the summary report. - -### 5.2.2 Defining Certification/Badging and Set of Tests - -O-RAN Work Groups (WGs) specify conformance tests and interoperability tests related to their scope of work (e.g. WG4 specifies conformance tests and interoperability tests for Open Fronthaul interface). O-RAN TIFG specifies E2E tests. - -O-RAN TIFG defines certification and badging processes and procedures while conformance, interoperability and E2E tests are defined in O-RAN WG/FG test specifications. This is specified in Clause 6 for O-RAN conformance certification, Clause 7 for O-RAN IOT badging and Clause 8 for O-RAN E2E badging. - -O-RAN TIFG defines certification and badging according to market needs. If any OTIC does not find certificate/badge defined for its intended scenario(s), then the OTIC is encouraged to submit a proposal to the O-RAN TIFG in order to define new certificate/badge. - -### 5.2.3 Test platforms - -To reliably and successfully execute the tests for certification or badging, specialized test equipment and tools are needed. Such test equipment and tools need to meet specific criteria and be designed to execute the identified tests. - -It is the responsibility of OTICs to use appropriate test equipment and tools for certification/badging. O-RAN does not provide qualification or acknowledge processes for test equipment and tools, i.e. the choice of test - -equipment and tools for certification/badging will be left to the test market and their suitability will depend on the self-declaration of OTICs and test equipment vendors. - -The OTICs should use commercially available or open-source test platforms. The OTICs should also ensure proper calibration of test equipment and tools as specified by the test equipment vendors. (Pre-) Commercial UE(s) can also be used as long as it is allowed in the associated O-RAN test specification(s) and the information about the UE(s) is documented as a part of the test setup and test results are reproducible. - -The description of certification/badging test setup including information about used test equipment and tools needs to be documented in the summary report and test report. This will allow the requesting entity to challenge any failed test that may be caused by the test equipment. - -### 5.2.4 Identifying Applicable O-RAN certificate/badge and Tests - -The following steps describe the process for OTICs to identify which O-RAN certificate/badge to apply and which tests to conduct in the course of certification/badging. The process takes into consideration the interfaces, services, capabilities and functions supported by the DUTs/SUT that are subject of certification/badging - -- Step 1: Identify interface(s)/service(s)/device(s)/system to be subject of verification and assessment for O-RAN certification or badging. -- Step 2: Identify applicable O-RAN certificate or badge that can be applied to the identified subject of certification or badging based on available O-RAN certificates and badges (see clause 5.3). -- Step 3: Identify applicable tests for the subject of certification or badging and for identified O-RAN certificate or badge (see clauses 6 to 9). For mandatory capability or function, all related tests are always applicable (regardless of whether the subject of certification or badging supports the mandatory capability/function or not). For optional capability or function that has been declared as supported/implemented, all related tests are applicable. **If CB-ICS proforma is available (see clause 5.3), CB-ICS should be used to identify the applicable tests.** - -NOTE: If CB-ICS proforma is not available, the supported/implemented functions and capabilities should be declared by other means, and applicable tests should be identified in the relevant test specification(s). - -### 5.2.5 Executing Tests - -The OTICs execute all identified applicable tests (as specified in clause 5.2.4) and record the test and measurement results for further evaluation. - -### 5.2.6 Verifying Test Results - -The OTICs shall collect the test results for each executed test and fill in the summary report (template specified in O-RAN.TIFG.TS.Cert-Badge.1) and test report (template specified in O-RAN.TIFG.TS.Cert-Badge.2) to be shared accordingly. The detailed measurement results such as logs, screenshots, packet captures, etc. shall also be collected. Each test in the summary report and test report shall be evaluated against the - -1 expected results in associated test specification(s) to determine whether test passed or failed. The test -2 results should be reproducible, i.e. the same results should be observed under the same conditions. - -3 - -###### 4 5.2.7 Issuing Certificates/Badges - -5 All applicable tests shall be passed to award specific O-RAN certificate or badge. The O-RAN certificate or -6 badge is awarded only to DUT (product) representing O-RAN architecture element (such as Near-RT RIC, O- -7 CU-CP, O-CU-UP, O-DU, O-RU, etc.) with O-RAN interface(s) (such as Open Fronthaul, O1, A1, etc.) as defined -8 in O-RAN architecture [3], or to 3GPP elements (such as eNB, gNB-CU, gNB-DU, etc.) with O-RAN profiled -9 3GPP interfaces (such as Xn, F1, etc.). The OTIC issues O-RAN certificate or badge to each individual DUT -10 involved in the certification or badging. In case of O-RAN IOT badge, both DUTs involved in DUT pair are -11 awarded by O-RAN IOT badge with the same certificate/badge reference identifier (see clause 5.2.7.1). In -12 case of O-RAN E2E badge, all DUTs involved in the entire E2E system (SUT) are awarded by O-RAN E2E badges -13 with the same certificate/badge reference identifier. Assigning the same certificate/badge reference -14 identifier helps to identify which DUTs have been involved in DUT pair for interoperability testing or E2E -15 system for end-to-end testing. - -16 - -###### 17 5.2.7.1 Certificate/Badge Reference Identifier - -18 The OTIC manages and assigns its own certificate/badge reference identifiers with the following naming -19 convention. The naming convention is common for all O-RAN certificates and badges. The certificate/badge -20 reference identifier is unique for each certification or badging testing. The certificate/badge reference -21 identifier is a nine or ten-digit alphanumeric name with the following convention: - -22 *NAMEyy####* - -23 where: - -24 *NAME* is unique 3 or 4 letter OTIC designator (see [OTICs designators](#)) - -25 *yy* are the last two digits of the year of issue - -26 *####* is sequential four-digit serial number within the year of issue (start from '0001') assigned -27 individually by each OTIC - -28 - -###### 29 5.2.8 Compliance Folder - -30 The Compliance Folder represents an electronic collection of all relevant documents for certified/badged -31 products. It is the responsibility of the requesting entity to create and maintain such a Compliance Folder, -32 which shall be kept for a period of no less than six years and shall be available for sharing as specified in -33 Clause 5.2.9. The Compliance Folder contents shall contain the certification and badging report template. It -34 is recommended that requesting entity collect and store all relevant information in such a Compliance Folder. - -35 The requesting entity appoints a person responsible within the requesting entity's organization for all matters -36 related to the submission, execution, and maintenance of the product's certification. requesting entity shall -37 provide evidence that a Quality Management System (QMS), i.e., ISO9001 or equivalent recognized standard, - -1 is followed. The compliance folder shall be uniquely identified, included in the requesting entity's document -2 control system. - -3 In the case of badging process, where multiple requesting entities would participate in the tests, it is -4 recommended each requesting entity create and maintain its own Compliance Folder independently with -5 information relevant to its own products, subsystems or interfaces involved in such tests. Even though it is -6 possible that some information stored is redundant, the independently maintained Compliance Folder by -7 each requesting entity involved in the tests is necessary in case there is need to resolve data or result conflict -8 or dispute. To further clarify, in the case that the requesting entity is the product owner but not the original -9 equipment vendor/manufacturer, it is the responsibility of the requesting entity for maintaining the -10 Compliance Folder for all products involved. - -11 - -###### 12 5.2.9 Storing and Sharing of Summary Reports, Test reports and 13 Measurement Results - -14 The O-RAN public website keeps a catalogue with basic (non-sensitive) information (such as Certificate/Badge -15 ID, Date of issued certificate/badge, Vendor name, OTIC name) about all issued O-RAN certificates and -16 badges from all OTICs. This centralized catalogue has unrestricted access and is available to all O-RAN as well -17 as non-O-RAN entities. Each individual OTIC shall promptly report to O-RAN Office the basic information -18 needed for the O-RAN catalogue for any newly issued O-RAN certificate or badge. The information reported -19 by OTICs is subject to the review and approval by O-RAN Office before publication. - -20 The summary reports and test reports associated with the O-RAN certificate or badge shall be securely stored -21 by the individual OTICs issuing the O-RAN certificate or badge. The detailed measurement results shall be -22 stored either by the requesting entity (in case the measurement results are captured by the requesting entity -23 from its DUT(s)) or by OTIC (in case the measurement results are captured by OTIC from its test and -24 measurement equipment and tools) participating in the certification or badging testing. - -25 Optionally, Annex D defines a machine-readable results artifact, that may be used by OTICs and others for -26 the storage and handling of test results. This results artifact may be directly generated by automation tools -27 employed by the OTIC or by the test platforms (commercial or open source). Similarly, the OTIC may employ -28 automation tools to produce the summary report or the test report from the results artifact. - -29 Since O-RAN certificates and badges can only be issued by OTIC, the test results sharing principles defined -30 for OTIC [1] need to be followed. On request, the OTIC shall share the summary reports and test reports -31 (associated with O-RAN certificates and badges issued by the OTIC) only with O-RAN Members (i.e. mobile -32 network operators) and O-RAN Office. The OTIC shall not share the summary reports and test reports -33 (associated with O-RAN certificates and badges issued by the OTIC) with other O-RAN entities (i.e. O-RAN -34 contributors and academic contributors) as well as non-ORAN entities without the written permission of all -35 copyright holders (i.e. the OTIC and all requesting entities participating in the certification or badging testing). -36 The detailed measurement results may be shared at the discretion of either the requesting entity (the -37 measurement results stored by the requesting entity) or OTIC (the measurement results stored by OTIC). - -38 All sharing requests for the summary reports, test reports and measurement results should be directed to -39 the OTIC that issued the O-RAN certificate or badge. In case of sharing request for measurement results, the -40 OTIC forwards the request to the original participating entity(ies). - -###### 1 2 **5.2.10 SH/HW changes to certified/badged devices** - -3 When SW/HW changes are made to a DUT/SUT, certification/badging for the previous versions of that -4 DUT/SUT may not necessarily hold. On the other hand, a SW/HW change may also have nothing to do with -5 the subject and scope of certification/badging. The requesting entity should judge and self-declare when a -6 redo of certification/badging is necessary with SW/HW changes. - -###### 7 8 **5.2.11 Multi-vendor Scenario** - -9 The products under the O-RAN certification and badging process could present the following two multi- -10 vendor scenarios: - -- 11 • multi-vendor DUT: a single product with multiple internal SW/HW components (e.g. OS, HW, network -12 cards, accelerator cards) from various vendors -- 13 • multi-vendor SUT: a combination of multiple DUTs (products) from single or multiple vendors, -14 where individual DUT (product) can be also multi-vendor DUT - -15 In general, regardless of single vendor or multi-vendor DUT or SUT described above, O-RAN certificate or -16 badge can be awarded only to DUT (product) representing O-RAN architecture element with O-RAN -17 interface(s) or 3GPP element with O-RAN profiled 3GPP interface(s) (see clause 5.2.7). - -18 For the awarding of O-RAN certificates and badges in multi-vendor scenario, the following guidelines shall be -19 observed: - -- 20 • In the case of multi-vendor DUT described above, the single DUT (product) may be awarded the -21 O-RAN certificate or badge although its internal SW/HW components could come from various -22 vendors. -- 23 • In the case of multi-vendor SUT described above, all single or multi-vendor DUTs included in the end- -24 to-end system (SUT) or interoperability DUT pair may be awarded the O-RAN badges. - -25 Underlying OTICs and involved requesting entity(ies) shall record the information about all involved products -26 and products' components in the summary and test reports defined by O-RAN certification and badging -27 process. - -###### 28 **5.3 Defined and Available O-RAN Certificates and Badges** - -29 Based on the current availability of test specifications, the O-RAN certificates and badges have been defined -30 for the following combinations of Interface/Service Under Test and Device Under Test and are ready for -31 issuance under this version of the present document. More O-RAN certificates and badges will be defined for -32 issuance in future versions when the corresponding test specifications become available. Note that the “RAT -33 (Radio Access Technology) under test” is a RAT (5G NR or/and 4G LTE) which is supported by Device under -34 test, and which has been also applied within the testing. - -- 35 • Conformance Certificates - -| Interface / Service | Device Under Test | RAT Under Test | CB-ICS proforma | Notes | -|---------------------|-------------------|----------------|-----------------|-------| -|---------------------|-------------------|----------------|-----------------|-------| - -| Under Test | | | | | -|-------------------------|-------------|---------------------|---------------|------------------------------| -| Open Fronthaul (OpenFH) | O-RU | 4G LTE or/and 5G NR | Not available | | -| Open Fronthaul (OpenFH) | O-DU | 4G LTE or/and 5G NR | Not available | | -| Open Fronthaul (OpenFH) | O-DU/O-CU | 4G LTE or/and 5G NR | Not available | Aggregated O-DU and O-CU [3] | -| A1 services | Non-RT RIC | Not Applicable | Available | | -| A1 services | Near-RT RIC | Not Applicable | Available | | - -1 - -2 - -- IOT Badges - -| Interface / Service Under Test | Device Under Test | RAT Under Test | CB-ICS proforma | Notes | -|--------------------------------|-------------------|---------------------|-----------------|------------------------------| -| Open Fronthaul (OpenFH) | O-RU | 4G LTE or/and 5G NR | Not available | | -| Open Fronthaul (OpenFH) | O-DU | 4G LTE or/and 5G NR | Not available | | -| Open Fronthaul (OpenFH) | O-DU/O-CU | 4G LTE or/and 5G NR | Not available | Aggregated O-DU and O-CU [3] | -| X2 | eNB | 4G LTE | Not available | 3GPP compliant node | -| X2 | en-gNB | 5G NR | Not available | 3GPP compliant node [6] | -| F1 | gNB-CU | 5G NR | Not available | 3GPP compliant node [5] | -| F1 | gNB-DU | 5G NR | Not available | 3GPP compliant node [5] | -| Xn | gNB | 5G NR | Not available | 3GPP compliant node [4] | -| A1 services | Non-RT RIC | Not Applicable | Available | | -| A1 services | Near-RT RIC | Not Applicable | Available | | - -3 - -4 - -- E2E Badges - -| Interface Under Test | Device Under Test | RAT Under Test | CB-ICS proforma | Notes | -|----------------------|-------------------|---------------------|-----------------|------------------------------------| -| Not Applicable | O-RU | 4G LTE or/and 5G NR | Available | | -| Not Applicable | O-DU | 4G LTE or/and 5G NR | Available | | -| Not Applicable | O-CU | 4G LTE or/and 5G NR | Available | | -| Not Applicable | O-RU/O-DU | 4G LTE or/and 5G NR | Available | Aggregated O-RU and O-DU [3] | -| Not Applicable | O-DU/O-CU | 4G LTE or/and 5G NR | Available | Aggregated O-DU and O-CU [3] | -| Not Applicable | O-RU/O-DU/O-CU | 4G LTE or/and 5G NR | Available | Aggregated O-RU, O-DU and O-CU [3] | - -5 - -6 - -NOTE: The CB-ICS proformas are available in O-RAN.TIFG.TS.Cert-Badge.5. - -# 6. O-RAN Conformance Certification Procedures - -This clause provides the procedures for verification of compliance of O-RAN interface implementations with O-RAN defined interface specifications resulting in the award of O-RAN certificate. - -## 6.1 Subsystems and Interfaces - -The O-RAN conformance test specifications have been defined for the following combinations of O-RAN specified interface and subsystem (device under test), and these combinations can be awarded an O-RAN certificate. Table 6.1-1 will be updated following publication of new O-RAN conformance test specifications, and as soon as new combinations of interfaces and subsystems can be awarded an O-RAN certificate. - -**Table 6.1-1: The combinations of interface and subsystem (device under test) which can be awarded by O-RAN certificate, incl. the applicable test specifications** - -| Interface / Service | Subsystem (DUT) | Applicable test specification(s) / CB-Profiles / CB-ICS Proforma | O-RAN WG/FG owning test specification | -|----------------------------------------|-----------------|-------------------------------------------------------------------|---------------------------------------| -| O-RAN Open Fronthaul incl. CUSM-planes | O-RU | Open Fronthaul conformance test specification (O-RAN.WG4.TS.CONF) | O-RAN WG4 | -| O-RAN Open Fronthaul incl. CUSM-planes | O-DU | Open Fronthaul conformance test specification (O-RAN.WG4.TS.CONF) | O-RAN WG4 | -| O-RAN Open Fronthaul incl. CUSM-planes | O-DU/O-CU | Open Fronthaul conformance test specification (O-RAN.WG4.TS.CONF) | O-RAN WG4 | -| A1 services | Non-RT RIC | A1 interface Test Specification (O-RAN.WG2.TS.A1TS) | O-RAN WG2 | -| | | O-RAN CB Profiles (O-RAN.TIFG.TS.Cert-Badge.4) | O-RAN TIFG | -| | | O-RAN CB-ICS Proformas (O-RAN.TIFG.TS.Cert-Badge.5) | O-RAN TIFG | -| A1 services | Near-RT RIC | A1 interface Test Specification (O-RAN.WG2.TS.A1TS) | O-RAN WG2 | -| | | O-RAN CB Profiles (O-RAN.TIFG.TS.Cert-Badge.4) | O-RAN TIFG | -| | | O-RAN CB-ICS Proformas (O-RAN.TIFG.TS.Cert-Badge.5) | O-RAN TIFG | - -11 - -If needed, the following clauses provide details on each combination mentioned in Table 6.1-1. - -## 6.2 O-RAN Open Fronthaul interface of O-RU - -All tests for validation of conformance of O-RAN specified Open Fronthaul interface of O-RU against relevant O-RAN technical specification are specified in the O-RAN “Open Fronthaul conformance test specification” (O-RAN.WG4.CONF). Tests that are mandatory are for those functionalities of the O-RU that by specification are required to be supported. Optional functionality in an O-RU implies that the corresponding tests are - -1 conditionally mandatory and are mandatory only if the O-RU supports the optional functionality. **All M-plane** -2 **and S-plane tests marked as mandatory (M), and all applicable M-plane and S-plane tests marked as** -3 **conditional mandatory (CM) shall be passed for issuing of the O-RAN certificate. For the selected test** -4 **scenario, all UC-plane tests marked as mandatory, and all applicable UC-plane tests marked as conditional** -5 **mandatory shall be passed for issuing of the O-RAN certificate.** The user/tester identifies all conditionally -6 mandatory tests based on the optional functionalities that the O-RU declares as supported. The user/tester -7 also selects one applicable test scenario that can be executed for UC-plane tests. The tests marked as optional -8 (O) or other unmarked tests from the test specification or any tests from other sources (e.g. 3GPP -9 specifications) can be executed, and test results may be added to summary report and test report, but passing -10 of these tests is not required for issuing of the specific O-RAN certificate. - -11 For the purpose of O-RAN Certificate, all the information and data from the testing shall be collected in the -12 summary report (tab “Certificate O-RU OpenFH”) and test report. - -###### 13 6.3 O-RAN Open Fronthaul interface of O-DU - -14 All tests for validation of conformance of O-RAN specified Open Fronthaul interface of stand-alone O-DU (or -15 combined O-DU/O-CU) against relevant O-RAN technical specification are specified in the O-RAN “Open -16 Fronthaul conformance test specification” (O RAN.WG4.CONF). Tests that are mandatory are for those -17 functionalities of the O-DU that by specification are required to be supported. Optional functionality in an O- -18 DU implies that the corresponding tests are conditionally mandatory and are mandatory only if the O-DU -19 supports the optional functionality. **All tests marked as mandatory (M) and all applicable tests marked as** -20 **conditional mandatory (CM) shall be passed for issuing of O RAN certificate.** The user/tester identifies all -21 conditionally mandatory tests based on the optional functionalities that the O-DU declares as supported. The -22 tests marked as optional (O) or other unmarked tests from the test specification or any tests from other -23 sources (e.g. 3GPP specifications) can be executed, and test results may be added to summary report and -24 test report, but passing of these tests is not required for issuing of the specific O-RAN certificate. - -25 For the purpose of O-RAN certificate, all the information and data from the testing shall be collected in the -26 summary report (tab “Certificate O-DU OpenFH”) and test report. - -###### 27 6.4 O-RAN A1 services on A1 interface of Non-RT RIC - -28 The certificate on A1 interface of Non-RT RIC is currently defined at the service level only, and does not -29 include the entire A1 interface, which contains additional functionalities such as functions at transport layer -30 (A1TP). O-RAN A1 services on A1 interface of Non-RT RIC refer to A1 policy management service (A1-P) and -31 A1 enrichment information service (A1-EI). - -32 All tests for validation of conformance of O-RAN A1 services on A1 interface of Non-RT RIC against relevant -33 O-RAN technical specifications are specified in O-RAN.WG2.TS.A1TS. O-RAN CB-Profile (O-RAN.TIFG.TS.Cert- -34 Badge.4) further constrains the options specified in the base specification. O-RAN Certification and Badging -35 ICS (CB-ICS) Proforma for O-RAN A1 services on A1 interface of Non-RT RIC is also available in the subsidiary -36 document O-RAN.TIFG.TS.Cert-Badge.5. - -37 O-RAN certificate of A1 services on A1 interface of Non-RT RIC is issued as a single certificate without the -38 underlying supported A1 service(s) explicitly specified. The relevant information on specific A1 service(s) and -39 procedures supported by Non-RT RIC is recorded and described in the associated Summary Report and Test -40 Report. - -1 - -###### 2 6.5 O-RAN A1 services on A1 interface of Near-RT RIC - -3 The certificate on A1 interface of Near-RT RIC is currently defined at the service level only, and does not - 4 include the entire A1 interface, which contains additional functionalities such as functions at transport layer - 5 (A1TP). O-RAN A1 services on A1 interface of Near-RT RIC refer to A1 policy management service (A1-P) and - 6 A1 enrichment information service (A1-EI). - -7 All tests for validation of conformance of O-RAN A1 services on A1 interface of Near-RT RIC against relevant - 8 O-RAN technical specifications are specified in O-RAN.WG2.TS.A1TS. O-RAN CB-Profile (O-RAN.TIFG.TS.Cert- - 9 Badge.4) further constrains the options specified in the base specification. O-RAN Certification and Badging - 10 ICS (CB-ICS) Proforma for O-RAN A1 services on A1 interface of Near-RT RIC is also available in the subsidiary - 11 document O-RAN.TIFG.TS.Cert-Badge.5. - -12 O-RAN certificate of A1 services on A1 interface of Near-RT RIC is issued as a single certificate without the - 13 underlying supported A1 service(s) explicitly specified. The relevant information on specific A1 service(s) and - 14 procedures supported by Near-RT RIC is recorded and described in the associated Summary Report and Test - 15 Report. - -16 - -###### 17 7. O-RAN IOT Badging Procedures - -18 This clause provides the procedures for validation of interoperability (IOT) of subsystems utilizing O-RAN - 19 specified or profiled open interfaces resulting in the award of O-RAN IOT badge. - -###### 20 7.1 Subsystems and Interfaces - -21 The O-RAN interoperability test specifications have been defined for the following combinations of O-RAN - 22 specified interface and subsystems (device under test), and these combinations can be awarded an O-RAN - 23 IOT Badge. The Table 7.1-1 will be updated following publication of new O-RAN interoperability test - 24 specifications, and as soon as new combinations of interfaces and subsystems can be awarded an O-RAN IOT - 25 Badge. - -26 - -27 **Table 7.1-1 The combinations of interface and subsystems (devices under tests) which can be awarded by** - 28 **O-RAN IOT Badge, incl. the applicable test specifications** - -| Interface / Service
Under Test | Subsystems
(DUT pair) | Applicable test specification(s) /
CB-Profiles / CB-ICS Proformas | O-RAN WG/FG
owning test
specification | -|-----------------------------------|--------------------------|---------------------------------------------------------------------------|---------------------------------------------| -| O-RAN Open Fronthaul | O-RU, O-DU | Fronthaul Interoperability Test
Specification (IOT) (O-RAN.WG4.TS.IOT) | O-RAN WG4 | -| O-RAN Open Fronthaul | O-RU, O-DU/O-CU | Fronthaul Interoperability Test
Specification (IOT) (O-RAN.WG4.TS.IOT) | O-RAN WG4 | -| X2 | eNB, en-gNB | Interoperability Test Specification (IOT)
(O-RAN.WG5.TS.IOT) | O-RAN WG5 | - -| | | | | -|-------------|----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| -| F1 | gNB-CU,
gNB-DU | Interoperability Test Specification (IOT)
(O-RAN.WG5.TS.IOT) | O-RAN WG5 | -| Xn | gNB, gNB | Interoperability Test Specification (IOT)
(O-RAN.WG5.TS.IOT) | O-RAN WG5 | -| A1 services | Non-RT RIC.
Near-RT RIC | A1 interface Test Specification
(O-RAN.WG2.TS.A1TS)
O-RAN CB Profiles
(O-RAN.TIFG.TS.Cert-Badge.4)
O-RAN CB-ICS Proformas
(O-RAN.TIFG.TS.Cert-Badge.5) | O-RAN WG2

O-RAN TIFG

O-RAN TIFG | - -1 If needed, the following clauses provide details on each combination mentioned in Table 7.1-1. - -###### 2 7.2 O-RAN Open Fronthaul interface - -3 All tests for validation of interoperability between O-RU and stand-alone O-DU (or combined O-DU/O-CU) -4 utilizing O-RAN Open fronthaul interface are specified in the O-RAN “Fronthaul Interoperability Test -5 Specification (IOT)” (O-RAN.WG4.IOT). **All tests marked as mandatory (M) and all applicable tests marked** -6 **as conditional mandatory (CM) shall be passed for issuing of O-RAN IOT badge.** The optional tests or other -7 unmarked tests from the test specification or any tests from other sources (e.g. 3GPP specifications) can be -8 executed, and test results may be added to summary report and test report, but passing of these tests is not -9 required for issuing of the specific O-RAN IOT badge. - -10 The Fronthaul Interoperability Test Specification (IOT) (O-RAN.WG4.IOT) defines Interoperability Test (IOT) -11 Profiles along with associated IOT Profile Test Configurations. For O-RAN IOT badge, both O-RU and O-DU (or -12 combined O-DU/O-CU) need to agree and use at least one common IOT Profile Test Configuration or -13 Customized IOT Configuration to verify interoperability. Further, for O-RAN IOT Badge, the participating -14 entity can choose one or both of the following options: - -- 15 • Option 1: selection of **IOT Profile Test Configuration(s)** listed in the Fronthaul Interoperability Test -16 Specification (IOT) (O-RAN.WG4.IOT). The name(s) of used IOT Profile Test Configuration shall be -17 mentioned in the summary report (tab “IOT Badge OpenFH”). -- 18 • Option 2: creation of **Customized IOT Configuration(s)**. The Customized IOT Configuration(s) (incl. -19 the values of all required system parameters) shall be included in the summary report (tab “OpenFH -20 Customized IOT Conf.”). In case of multiple Customized IOT Configurations, individual column shall -21 be created for each Customized IOT configuration. The name(s) of used Customized IOT -22 Configuration shall be mentioned in the summary report (tab “IOT Badge OpenFH”). - -23 The IOT Profile Test Configuration(s) (PTC) may contain a list of “to be validated” capabilities. The utilization -24 of “to be validated” capabilities associated with each PTC shall be validated in C/U-plane IOT tests for issuing -25 of O-RAN IOT badge. The IOT PTC may also contain a list of “to be reported” capabilities. The usage, or -26 absence of usage, of these capabilities shall be reported in the test report for issuing of O-RAN IOT badge. - -27 For O-RAN IOT Badge, all the information and data from the testing shall be collected in the summary report -28 (tab “IOT Badge OpenFH”) and test report. - -29 - -## 7.3 X2 interface - -- All tests for validation of interoperability between subsystems (DUT pairs listed in Table 7.1-1) utilizing X2 interface are specified in the O-RAN “Interoperability Test Specification (IOT)” (O-RAN.WG5.IOT). Based on the supported capabilities, functionalities, and features of Devices under Test (DUTs), the user/tester needs to identify all applicable X2 C-plane and X2 U-plane IOT tests from this test specification. **All applicable X2 C-plane and U-plane IOT tests shall be passed for issuing of O RAN IOT badge.** -- For the purpose of O-RAN IOT Badge, all the information and data from the testing shall be collected in the summary report (tab “IOT Badge X2”) and test report. - -## 7.4 F1 interface - -- All tests for validation of interoperability between subsystems (DUT pairs listed in Table 7.1-1) utilizing F1 interface are specified in the O-RAN “Interoperability Test Specification (IOT)” (O-RAN.WG5.IOT). Based on the supported capabilities, functionalities, and features of Devices under Test (DUTs), the user/tester needs to identify all applicable F1 IOT tests from this test specification. **All applicable F1 IOT tests shall be passed for issuing of O-RAN IOT badge.** -- For the purpose of O-RAN IOT Badge, all the information and data from the testing shall be collected in the summary report (tab “IOT Badge F1”) and test report. - -## 7.5 Xn interface - -- All tests for validation of interoperability between subsystems (DUT pairs listed in Table 7.1-1) utilizing Xn interface are specified in the O-RAN “Interoperability Test Specification (IOT)” (O-RAN.WG5.IOT). Based on the supported capabilities, functionalities, and features of Devices under Test (DUTs), the user/tester needs to identify all applicable Xn IOT tests from this test specification. **All applicable Xn IOT tests shall be passed for issuing of O-RAN IOT badge.** -- For the purpose of O-RAN IOT Badge, all the information and data from the testing shall be collected in the summary report (tab “IOT Badge Xn”) and test report. - -## 7.6 A1 services on A1 interface - -- The IOT badge on A1 interface is currently defined at the service level only between Non-RT RIC and Near-RT RIC (DUT pairs listed in Table 7.1-1), and does not include the entire A1 interface, which contains additional functionalities such as functions at transport layer (A1TP). O-RAN A1 services on A1 interface refer to A1 policy management service (A1-P) and A1 enrichment information service (A1-EI). -- All tests for validation of interoperability between Non-RT RIC and Near-RT RIC utilizing A1 services are specified in O-RAN.WG2.TS.A1TS. O-RAN CB-Profile (O-RAN.TIFG.TS.Cert-Badge.4) further constrains the options specified in the base specification. O-RAN Certification and Badging ICS (CB-ICS) Proforma for the IOT badge of A1 services on A1 interface is also available in the subsidiary document O-RAN.TIFG.TS.Cert-Badge.5. - -1 O-RAN IOT badge for A1 services on A1 interface between Non-RT RIC and Near-RT RIC is issued as a single -2 badge without the underlying supported A1 service(s) explicitly specified. The relevant information on -3 specific A1 service(s) and procedures supported by Non-RT RIC and Near-RT RIC is recorded and described in -4 the associated Summary Report and Test Report. - -5 - -###### --- 6 8. O-RAN E2E Badging Procedures - -7 This clause provides the procedures for verification of end-to-end functionality and security of end-to-end -8 system (SUT) resulting in the award of O-RAN E2E badge. - -9 The entire O-RAN system (integrated O-RU, O-DU, O-CU-CP, O-CU-UP, as specified in OAD [3], from single or -10 multiple vendors) is the System under Test (SUT) and is considered as an integrated black box in the context -11 of E2E functional and security testing. - -12 NOTE 1: O-RAN system with a replaced component(s) (e.g. O-RU) or with a changed SW/HW version of -13 a component (see clause 5.2.10) is considered as a new SUT, and such changes lead to -14 retesting and the awarding of a new E2E badge. - -15 NOTE 2: All components involved in O-RAN system (SUT) are awarded O-RAN E2E badges with the same -16 “certificate/badge reference identifier” (see clause 5.2.7) so that all components in SUT can -17 be identified. - -18 The tests for verification of end-to-end functionality are specified in O-RAN End-to-end Test Specification -19 [2], and the tests for verification of end-to-end security in O-RAN Security Test Specifications [7]. **All** -20 **applicable functional tests, as specified in E2E-test [2], clause 5, and all applicable “3GPP Security** -21 **Assurance Specification (SCAS)” tests, as listed in STS [8], clause 24.1, shall be passed for issuing of O-RAN** -22 **E2E badge.** Specifically, the applicability of tests is defined by O-RAN requirements and 3GPP security -23 requirements, and not by the requesting entity on whether the SUT has implemented the required -24 capability/functionality or not. Further, for optional capabilities, functions and features that have been -25 declared as supported/implemented, all related tests shall be conducted, see examples below. The other -26 end-to-end tests from E2E-test [2] or STS [8], or any end-to-end tests from other sources (e.g. 3GPP -27 specifications) can be executed, and test results may be added to summary report and test report, but passing -28 of these additional tests is not required for issuing of the specific O-RAN E2E badge. - -29 NOTE 3: The applicability of tests does not depend on the supported capabilities, functionalities, or -30 features of test and measurement equipment and tools (test environment). - -31 EXAMPLE 1: If the SUT is 5G SA system, only tests related 5G SA are applicable. - -32 EXAMPLE 2: If the SUT does not support/implement optional interface Xn/X2, then all tests related to -33 the Xn/X2 interface are not applicable. However, if the Xn/X2 interface is -34 supported/implemented, then all related requirements shall be met, and all related tests -35 shall be passed. - -36 For the purpose of O-RAN E2E Badge, all the information and data from the testing shall be collected in the -37 summary report (tab “E2E Badge”) and test report. - -38 O-RAN Certification and Badging ICS (CB-ICS) Proforma for the E2E Badge is also available in the subsidiary -39 document O-RAN.TIFG.TS.Cert-Badge.5. - -# --- 1 Annex A (informative):2 Certification application - -3 Certification application should at least include the following information: - -- 4 • Company -- 5 • Contact Name -- 6 • Contact e-mail -- 7 • Contact Address -- 8 • Contact Phone -- 9 • Product Name/Model -- 10 • Product Software/Firmware Version -- 11 • Product Description -- 12 • Date of Submission -- 13 • Date of expected start of testing -- 14 • Preferred OTIC -- 15 • Sub-system Type - -16 - -17 If the product uses certified building blocks or wishes to reuse results from an already certified/tested - -18 product, provide a description of the sub-assembly/building block and identify the source certified/tested - -19 product(s). Include any potential differences, changes or other factors that may impact the definition of - -20 needed regression testing. - -21 - -## --- 1 Annex B (informative): - -## 2 Compliance folder - -3 Compliance folder should at least include the following information: - -- 4 • Index of contents -- 5 • Completed ICS with test execution information -- 6 • Model/type numbers -- 7 • Brand name -- 8 • Manufacturer detail -- 9 • Technical description including a block diagram, circuit diagram -- 10 • Details of significant design aspects (features, specifications, installation measures, control of -- 11 variants and manufacturing) -- 12 • Variant description (as applicable) -- 13 • Software version(s) / SVN -- 14 • Reference to versions of O-RAN ALLIANCE Certification Criteria used -- 15 • User, installation, or special instructions -- 16 • Test data -- 17 • Internal and the third party test reports -- 18 • Products tested for interoperability -- 19 • Details of changes in hardware and/or software configuration together with evidence of continued -- 20 compliance -- 21 • Evidence that the device has been developed and tested according to the Quality Management -- 22 Program requirements -- 23 • A copy of the Certification Declaration - -## --- 1 Annex C (normative):2 Trademark License Agreement - -# 34 **Trademark License Agreement** - -5 - -6 between - -7 **O-RAN ALLIANCE e.V., Buschkauer Weg 27, 53347 Alfter, Germany** - -8 - hereinafter referred to as "Licensor" - - -9 and - -10 - -11 - hereinafter referred to as the "Licensee" - - -12 - -## 13 **Preamble** - -14 The background of the Trademark License Agreement is to use O-RAN ALLIANCE trademarks for O-RAN -15 Certificates and Badges by non O-RAN ALLIANCE members. The aim of the Trademark License Agreement is -16 to allow the use of the O-RAN ALLIANCE trademarks "**O-RAN Certified**", "**O-RAN Interoperable**" and "**O-** -17 **RAN E2E-Tested**" with certified and/or badged products. - -### 18 **§ 1 License** - -19 (1) The Licensor has been granted by the owner of the trademarks "O-RAN Certified", "O-RAN Interoperable" -20 and "O-RAN E2E-Tested" and registered in the trademark register at the [...] on [...] under No. [...] for [will be -21 detailed by O-RAN] (hereinafter "the contractual trademark"). - -22 (2) The Licensor hereby grants the Licensee the non-exclusive and non-transferable right, for the duration of -23 the Agreement, in the territory of [...] to offer, place on the market, advertise, use on business papers and to -24 label these products (hereinafter referred to as "the Contract Products") with the contractual trademark [...]. - -25 (3) The Licensee is not entitled to grant sub-licenses. - -26 - -### 27 **§ 2 License endorsement** - -28 (1) The Licensee undertakes to use the contractual trademark, in particular on labels, packaging and in -29 advertising, only in the form prescribed by the Licensor and, if the Licensor deems additions necessary, only -30 with the additions prescribed by the Licensor. The Licensee shall always mark the contractual trademark with -31 the registration mark ® and indicate that it is a registered trademark of the Licensor. - -1 (2) The Licensor shall notify the Licensee in writing of any changes to the prescribed form or additions and -2 these shall be implemented without delay, but at the latest within the period set by the Licensor. After expiry -3 of the deadline set by the Licensor, the Licensee may only use the contractual trademark in a non-updated -4 form or with non-updated additions with the written consent of the Licensor. - -5 - -6 - -### **§ 3 Warranty and liability** - -7 (1) The Licensee shall indemnify the Licensor and hold the Licensor harmless from all third-party claims arising -8 from and in connection with the contractual services, unless the Licensor is at least predominantly -9 responsible for the claims and liabilities. The Licensor shall be predominantly responsible for damages which -10 have come about as a result of its rights to issue instructions under this Agreement. Otherwise, Section 254 -11 German Civil Code applies. - -12 (2) The Licensor does not guarantee that the use of the contractual trademark does not infringe any third- -13 party rights. However, the Licensor declares that he is not aware of any such rights. No liability is assumed -14 for freedom from defects, in particular the dependence on third-party property rights. - -15 (3) The Licensor warrants that the contractual trademark has not been pledged, that no rights of use or other -16 rights in rem have been granted and that the contractual trademark is not the subject of enforcement -17 proceedings and is not subject to any other ongoing proceedings. - -18 - -19 - -### **§ 4 Contract duration and termination** - -20 (1) This contract shall enter into force on [...] and has a term until [...]. Thereafter, it shall be automatically -21 extended for a further [...] years, unless it is renewed with a notice period of [...] months to the end of the -22 respective contract period. - -23 (2) The contract shall end without the need for cancellation when the contractual trademark is legally -24 cancelled. - -25 (3) Irrespective of the other ordinary termination provisions or termination events regulated in the contract, -26 this contract may be terminated by the Licensor with immediate effect for the following reasons: - -27 (a) if the Licensee, its commercial agents, wholesalers and importers use the contractual trademark for -28 products/services that are not covered by this Agreement or to which the Licensor has not consented, unless -29 such use is discontinued immediately, at the latest within [...] calendar days after receipt of a written request -30 to cease and desist. - -31 (b) if the Licensee breaches its material contractual obligations or any other material provision of this -32 Agreement, unless such breach occurs within [...] days after written request by the Licensor. - -33 (c) if the Licensee is liquidated or insolvency proceedings are opened against the Licensee's assets or the -34 opening of insolvency proceedings is rejected for lack of assets or similarly serious proceedings are initiated -35 against the Licensee. - -36 - -### **§ 5 Settlement after termination of the contract** - -Upon termination of this Agreement, the Licensee shall immediately refrain from using the contractual trademark; the Licensor shall remain the sole owner of all rights to the contractual trademark in relation to the Licensee. If the Licensee has acquired any rights to the trademark due to the use of the trademark, the Licensee shall transfer these rights to the Licensor upon termination of the Agreement. The Licensor accepts this transfer. - -### **§ 6 Maintenance and defence of the contractual trademark** - -The Licensor undertakes to maintain the registration of the contractual trademark for the duration of this agreement and to defend it against any attacks by third parties. This does not apply if the acts of infringement are insignificant and the litigation costs would be disproportionate to any loss of sales. The assessment of whether an act of infringement is insignificant is the sole responsibility of the Licensor. - -### **§ 7 Attacks by third parties against the use of the trademark by the Licensee** - -(1) If one of the parties becomes aware that a third party is using a labelling and/or registers it as a trademark which could possibly be confused with the contractual trademark or otherwise infringes it, it must inform the other party of this immediately. If a claim is made against the Licensee for injunctive relief and/or damages due to the manufacture of the products and/or the use of the contractual trademark by a third party, the Licensee is obliged to inform the Licensor of this immediately, providing the necessary details about the nature of the claim. - -(2) In principle, the Licensee is not entitled to bring an action in its own name for trademark infringement. The Licensor is primarily entitled to take action against the use of a confusingly or otherwise infringing name. The Licensor can make the action dependent on the Licensee contributing up to half of the costs of the action. The right of the Licensee to join an infringement action brought by the trademark proprietor pursuant to Section 30 (4) MarkenG in order to claim damages remains unaffected. If the Licensor does not take action against the third party within a reasonable period of time despite the Licensee's offer to contribute half of the costs of the action, the Licensor is obliged to authorise the Licensee to pursue the infringement in his own name and at his own expense. Compensation paid by a third party shall be due to the parties in the proportion in which they have borne the costs of the action. - -(3) The Licensor requires the consent of the Licensee to conclude a settlement by which he authorises a third party to use a trademark which, in the opinion of the Licensee, is likely to be confused with the contractual trademark. - -### **§ 8 Non-aggression clause** - -The Licensee undertakes neither to attack the contractual trademark itself nor to support third parties in attacking property rights. - - - -## 1 **Annex D (normative):** 2 **Machine readable results artifact** - -3 This annex describes the architecture and requirements for the machine readable Results Artifact that is - 4 created as the outcome of testing according to O-RAN Alliance test specification or similar specifications. - 5 Implementation of the Results Artifact is optional, however, if implemented, the Results Artifact shall - 6 conform to the requirements within this Annex. Figure D.1 describes the high-level view of the information - 7 created during testing, and thus “stored” as part of the Results Artifact. - -8 - -![Figure D.1: Architecture and key components stored within the Results Artifact. The diagram shows a 'Testing' box containing 'Test Results' (Measurements, Metrics, Artifacts, Notes), 'Test Specification Information', 'DUT / DUT Configuration', 'Test Profile' (e.g., FG2 TC16, WG4 IOT), 'DUT / SUT' (Component #1 to #n, T&M Eqt #1 to #2), and 'Lab Info' (Location, Date, Temp, Testers). An arrow points from 'Test Specification' to the 'Testing' box, and another arrow points from the 'Testing' box to a 'Results Artifact' cylinder with a 'Digital Signature'.](a4b963a07cc368283154762c4b156fe7_img.jpg) - -Figure D.1: Architecture and key components stored within the Results Artifact. The diagram shows a 'Testing' box containing 'Test Results' (Measurements, Metrics, Artifacts, Notes), 'Test Specification Information', 'DUT / DUT Configuration', 'Test Profile' (e.g., FG2 TC16, WG4 IOT), 'DUT / SUT' (Component #1 to #n, T&M Eqt #1 to #2), and 'Lab Info' (Location, Date, Temp, Testers). An arrow points from 'Test Specification' to the 'Testing' box, and another arrow points from the 'Testing' box to a 'Results Artifact' cylinder with a 'Digital Signature'. - -9 - -10 Figure D.1: Architecture and key components stored within the Results Artifact - -11 - -## 12 **D1 Definitions** - -- 13 • **Artifact Container** – A directory or compress archive (zip or tarball), containing a Results Artifact of a - 14 single run (one execution) of a Test Specification against one SUT or DUT. -- 15 • **Measurement** – Value or observable result, recorded during the execution of a test procedure. -- 16 • **Metadata (of test)** – General information about the test execution, such as start time, end time, - 17 overall outcome, identification numbers, etc. -- 18 • **Metric (Test Requirements)** – Measurable outcome of an item within a test case, resulting in a pass - 19 or fail determination. Note, a single Test Case can include multiple Test Requirements. -- 20 • **Results Artifact** – Outcome or deliverable of testing, including details of the system or device under - 21 testing, test and measurement equipment, laboratory, dates of testing, and measurement data. A - 22 Results Artifact should include enough information to ensure the testing could be replicated with - 23 the same conditions, hardware, and firmware/software versions, as a mechanism to ensure the - 24 traceability of the testing, and it can be used by a tool to automatically generate Summary and/or - 25 Test Reports. - -- 1 • **Schema** – Language definition and model, encapsulating requirements, parameters, and syntax of -2 machine readable information within the Results Artifact. -- 3 • **T&M Equipment** – Equipment used within testing to provide test stimulus or measurements -4 according to the test plan requirements. -- 5 • **Test Case** – A construct within a Test Specification that includes at least a procedure and one or -6 more metrics, with the intention to yield an outcome (i.e. a pass or fail result). A Test Specification -7 typically includes one or more Test Cases, which might be organized into groups based on topic or to -8 promote overall readability of the document. -- 9 • **Testbed Component** – A unit or product, included within the network during testing, where the -10 behavior, performance, or operation of the unit or product could influence the outcome of testing. -11 Note, testing is likely performed on multiple interconnected components, where can all be included -12 in the Results Artifact. -- 13 • **Test Lab** – Organization responsible for the execution of the Test Specification, along with the -14 capture and documentation of the Test Results produced from that execution. Test Labs will -15 generally create the Results Artifact described within this annex. -- 16 • **Test Notes** – General information, observations, or other documentation developed and captured -17 during the execution of a Test Specification. -- 18 • **Test Specification** – A version-controlled document of test procedures, test requirements, and -19 required measurement or observable results that provides detailed guidance to laboratory -20 personnel responsible for the operation and execution of testing. -- 21 • **Test Results** – Collection output from the execution of a Test Specification, including Test -22 Measurements, Test Metrics, Artifacts, and other data collected during the testing process. - -### 23 D2 Theory of Operation - -24 The Results Artifact is made up of a collection of files, containing information about the testing conducted -25 by the test lab. A commonly named, results.json (or results.yaml) file, stored at the root of the file -26 connection serves as the machine readable entry point to the Results Artifact. The other files can be -27 organized into one or more sub-directories, but all files referenced within the Results Artifact are stored in -28 this location. This ensures there are no references to external materials needed for the interpretation or -29 review of the Test Results and its outcome(s). The machine readable results file contains, high level -30 metadata type information about testing, information about the device or systems under test, test and -31 measurement equipment, the lab organization responsible for the testing, test results and measurements, -32 as well as contact information for the parties involved the testing. - -33 The schema also provides a means to refer to and describe the contents of other files stored within the -34 Results Artifact. These files are typically referred to as opaque files, where the format may or may not be a -35 commonly understood by the community. For example, a file might be a packet capture file (i.e. pcap -36 format), or it might be a binary file, specific to a test instrument, such as a spectrum analyzer. These -37 referenced files can also be utilized to store information about the configuration of the components of the -38 testbed. Lastly, the schema also provides a means to reference publicly available materials, such as test -39 specifications published by the O-RAN ALLIANCE or 3GPP. - -40 It is anticipated the Results Artifact will be stored as a whole unit, either as a directory or compressed -41 archive. When the results are read by a machine, it is expected the machine will be provided with the path -42 to the Artifact Container. - -1 - -## 2 D3 Requirements - -### 3 D3.1 Artifact Container - -- 4 1. The Results Artifact shall be represented at the root, as a single directory, that MUST contain one -5 or more files or sub-directories. -- 6 2. There shall be at least one file in the root of the directory of the results artifact named either -7 “results.yaml” or “results.json”. This file shall conform to the JSON schema [https://o-](https://o-ran.org/schemas/o-ran-test-results) -8 [ran.org/schemas/o-ran-test-results](https://o-ran.org/schemas/o-ran-test-results), as described below. -- 9 3. The Results Artifact shall contain the complete set of information from the testing, without -10 references to external material, except for references to publicly available materials (i.e. Published -11 O-RAN Alliance test plans) and captured as “decorated links” within the schema. - -12 The contents of the Artifact Container can be used for the generation of the Summary Report and Test -13 Reports in an automated manner, but the total contents of the Results Container are not limited to only the -14 information required for the generation of those reports or formats. - -### 15 D3.2 Test Results Schema - -16 The JSON schema, identified as , describes the complete -17 information schema for the results file stored within the Test Artifact. This file will store information within -18 a number of objects, each defined within the schema for a specific purpose. The clauses below provide -19 additional information and context about each object within the schema. Nothing within this document -20 shall imply or cause an alteration to the interpretation of the actual JSON schema file, such as changing a -21 value within the “required” parameter or any such similar change. - -22 The results schema and sub-schemas are stored within the following files: - -| JSON Schema File Name | Description | -|-------------------------------------|-----------------------------------------------------------------------------------------| -| o-ran-test-results-schema.json | Overall schema used to store information about the testing within the results artifact. | -| o-ran-wg4-iot-profile-schema.json | Values used within the IOT profile parameters, as defined by O-RAN ALLIANCE WG4. | -| o-ran-config-parameters-schema.json | Various configuration parameters that may be applied during testing. | - -23 - -#### 24 D3.2.1 Schema Version - -25 The version shall identify the version of the schema applied to the data, as a constant value. - -###### 26 D3.3.2 Test Metadata - -27 The test metadata object contains high level information about the test, with mandatory objects: start -28 date, device under test (DUT) name, overall result, test type, and the test ID. - -1 The DUT name shall reference a uniquely identifiable component within the testbed components object of -2 the results. The DUT name may reference multiple components, if applicable to the type of test, such as the -3 case for interoperability testing. - -4 The result shall indicate the aggregate result of the testing contained within the Results Artifact. The -5 overall, aggregated, test result. PASS indicates all required test cases also indicate PASS. FAIL indicates one -6 or more required test cases indicate FAIL. WARN indicates behavior observed during the execution of the -7 test case might cause concern, problems, or issues not directly relating to the required test metrics. SKIP -8 should not be used. - -9 The test ID value shall be applied to all Results Archives created by the laboratory and shall be unique -10 across all Results Archives created by the laboratory. - -#### 11 D3.2.3 Testbed Components - -12 The testbed components property contains an array of objects, where each object describes a device, -13 product, system, or test and measurement equipment used within the testing. One or more of these -14 components are the device or system under test, identified by the test metadata object. - -15 Each component shall include the following properties: component description, manufacturer name, -16 manufacturer model. The object shall also include at least one of the following properties: software -17 version, firmware version, or hardware version. - -18 The component description should clearly indicate the component role within the testing, if possible, with -19 reference the O-RAN architecture. - -##### 20 D3.2.4 Test Lab - -21 The test lab object describes the laboratory responsible for the results contained within the Results Artifact. -22 The object shall provide at least one contact object, that describes a person, along with their details: email -23 and phone number. The object may provide one or more decorated links to public information about the -24 laboratory, such as the laboratory website. - -##### 25 D3.2.5 Test Specification - -26 The test specification property contains an array of test specification objects, that shall uniquely identify at -27 least one test specification used to produce the Test Results contained within the Results Artifact. - -##### 28 D3.2.6 Tags - -29 The tags property contains an array of unique strings, that may be utilized to describe the testing data -30 contained within the Results Artifact. Each string is anticipated as a short, free form string, that could be -31 used for results filtering, search, or similar operations within a database of results. - -##### 32 D3.2.7 Notes - -33 The notes property contains an array of note objects. Each note shall contain a title and the text content of -34 the note. - -##### 1 D3.3.8 Test Results - -2 The test results property contains an array of objects. Each object may be either a test group object or a -3 test case object. A test group object contains an array of test group or test case objects. Both the test group -4 and test case objects contain a required property to record the test number. In this way, the structure is -5 intended to mirror the structure and organization of the test specification within the test results. - -6 The test case object includes required properties: number, name, description, result, status, and metrics. -7 Additionally, and number optional properties are defined, including contacts, start date, stop date, notes, -8 measurements, decorated links, and artifacts. - -9 The metrics property contains an array of metrics objects, where each object described a test metrics, also -10 known as a test requirement, including the outcome result of the requirement and measurement values -11 required to validate that outcome. - -12 The measurements property contains an array of measurement value objects. These measurements are in -13 addition to those used directly within the metrics objects. - -### 14 D4 Digital Signature - -15 For further study. - -16 - -17 - -- -- 1 Annex (informative): - - 2 Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2021.03.05 | 01.00 | First published version | -| 2021.07.09 | 02.00 | 1. Clarification of certification/badging objectives in Chapter 4 & test result sharing in Chapter 5
2. Alignment with the updated Conformance and IOT specs from WG4 and WG5 in Chapter 6 & 7
3. Inclusion of custom IOT profile in the badging process in Chapter 7
4. Making security test mandatory in E2E badging process in Chapter 8
5. Alignment with the updated E2E Test Spec by adding load & stress test and additional service tests | -| 2021.11.10 | 03.00 | 1. Clarification in Chapter 4 on what entity can issue certificates and badges with O-RAN logos
2. Removing the sharing mechanism in Chapter 5 related to self-certification by vendors, individual operators, and 3rd party testing houses/labs
3. Adding in Chapter 5 the requirement on universal machine-readable format in test data sharing
4. Making test case 4.2.4.6 in Chapter 7 mandatory
5. Modifying the wording in Section 7.2.1 to be more concise and refer to Fronthaul IOT test specification clearly
6. Revising Figure 5.2-1 and Table 6.2-1 to sync up with the latest reference documents
7. In the companion test report template, making the following changes | -| 2022.03.22 | 04.00 | 1. Adding section 5.3 on available certificates and badges to be issued under this release
2. Adding section 5.1.4 on the composition of O-RAN certificates and badges; Revising section 5.2.8.2 and 5.2.8.4 on test result sharing location and format; Revising the Certificate/Badge reference identifier
3. Revising section 5.2.5 and 5.2.6 on verifying test results and issuing certificates/badges; Revising section 4.3.2 to clarify what equipment can be awarded O-RAN certificate/badges
4. Revising section 6.4.2 to exclude LTE tests in various scenarios when O-RU does not support LTE
5. Many corrections and clean-ups in FH O-RU Conformance Tab inside the companion test report template
6. Many IOT updates in Chapter 7 to align with Nov-2021 WG test specifications
7. Adding all corresponding new test cases in various IOT TABs inside the companion test report template
8. Automating reference version updates inside the companion test report template by adding a “References” tab to list all documents that are referenced on other tabs | -| 2022.07.27 | 05.00 | 1. Decoupling of O-RAN certification and badging processes and procedures from definition of tests in WG/FG test specifications – chapters 6, 7 and 8
2. Revising section 5.2.8.2 to provide further clarifications on centralized O-RAN web catalogue for issued O-RAN certificates and badges | -| 2022.11.10 | 06.00 | 1. Adding Summary report (O-RAN Certificate and Badge Summary Report) and Test report (O-RAN Certificate and Badge Test Report), and updating whole document with these new terms
2. Updating section “7.2 O-RAN Open Fronthaul interface between O-RU and O-DU” with the terminology used in the latest version of O-RAN.WG4.IOT.
3. Adding section “5.2.10 Multi-vendor Scenario” introducing multi-vendor scenario to O-RAN certification and badging processes | -| 2023.03.24 | 07.00 | 1. Clarification of available certificates and badges (Chapters 5.3, 6, 7, 8)
2. Adding subsystem combined O-DU/O-CU to OpenFH
3. Clarification of the tests which need to be passed (conducted) – Chapters 6, 7, 8
4. Updated process in Chapter 5.2 | -| 2023.11.09 | 08.00 | 1. Removing references not quoted
2. Clarification on the relocation of end-to-end security test cases to WG11 Security Test Specification | - -| | | | -|------------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2024.03.22 | 09.00 |
  1. 1. Clarification on F1/Xn IOT badge by including both user-plane and control-plane test cases based on the latest updates in O-RAN.WG5.IOT
  2. 2. Clarification on OpenFH IOT badge based on the latest updates in O-RAN.WG4.IOT related to new assigned status (M/CM/O) for S-plane IOT test cases
| -| 2024.07.18 | 10.00 |
  1. 1. Updated requirements on the summary and test reports to improve confidentiality – the reports shall be encrypted and digitally signed.
  2. 2. To ensure reusability and machine-readability of summary report, the unified file format (.xls/.xlsx) shall be used.
| -| 2025.03.21 | 11.00 |
  1. 1. Added the new process to enable awarding of O-RAN certificates/badges for products from non-O-RAN member entities
  2. 2. Introduced machine readable format for summary report, test report and measurement results
  3. 3. Updated O-RAN Cert/Badging process with the following
    • • O-RAN Certification and Badging process flow diagram
    • • Option to define O-RAN Certification and Badging Profile
    • • New O-RAN Certification and Badging ICS/ICS Proforma
| -| 2025.07.18 | 12.00 |
  1. 1. Added the new process to enable the product owner (while not the original product vendor/manufacturer) to request for O-RAN cert/badging
  2. 2. Introduced O-RAN certificates and badges for A1 services on A1 interface
  3. 3. Clarified O-RAN CB-Profiles and CB-ICS Proformas as two new subsidiary documents to the main Cert/badging process and procedure document
  4. 4. Defined the detail O-RAN CB-Profile and CB-ICS Proforma for A1 services
  5. 5. Updated the OpenFH IOT badging process corresponding to the newly added “to be validated” list for some PTCs in the latest O-RAN.WG4.TS.IOT.0-R004-v13.00
| -| 2025.11.28 | 13.00 |
  1. 1. Revised the format and instructions of CB-ICS proforma based on the latest test specification framework
  2. 2. Clarified the availability and referencing of CB-ICS proforma across the document
  3. 3. Clarified the E2E badging process and introduced the CB-ICS proforma for E2E badge
  4. 4. Revised CB-ICS proforma on A1 service certificate and IOT badge for nearRT-RIC & NonRT-RIC based on the new format
  5. 5. Clarified the applicability of test cases across the whole document
  6. 6. Added the definition of terms: repeatability and reproducibility
| - -1 -2 -3 -4 \ No newline at end of file diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index e9d056186f91071754a1bd66cc5b0f58f9cdcd1d..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a6feea577002af775f92c1c073ef8e278549447e23549760a568e59d2a4c42d6 -size 4142 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index a825d9b99f911d8f827b9553283b5ad21813fd46..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0b8fe5d6b51586629e54302f8e923644b5ad824f552cbb388a721c71c2fdb5bf -size 4236 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 57c1ec40ddd8b65e207ef8b2cf9bc077c1ef5c94..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:824af40599b843085c67553baa10788d2a863049341844c656cd06dd0efa3f1b -size 4042 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index a1a021c6cced459e5a30319f5f0e9eb4cee8c91f..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b15fb625969e26fe1f45975f7f45e9ff2d2a2b3a3006dbcaef44fb07ddd8d3bb -size 4016 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/410562339ce067fdc6fa41940c118658_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/410562339ce067fdc6fa41940c118658_img.jpg deleted file mode 100644 index 06ecae9dd97a086351c28aab0e58f54dd4821793..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/410562339ce067fdc6fa41940c118658_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5f97e819006cad60135a27dc873044fbde7fc884d2169aae7d996c52f775bb96 -size 52332 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index a1a021c6cced459e5a30319f5f0e9eb4cee8c91f..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b15fb625969e26fe1f45975f7f45e9ff2d2a2b3a3006dbcaef44fb07ddd8d3bb -size 4016 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index a1a021c6cced459e5a30319f5f0e9eb4cee8c91f..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b15fb625969e26fe1f45975f7f45e9ff2d2a2b3a3006dbcaef44fb07ddd8d3bb -size 4016 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index a1a021c6cced459e5a30319f5f0e9eb4cee8c91f..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b15fb625969e26fe1f45975f7f45e9ff2d2a2b3a3006dbcaef44fb07ddd8d3bb -size 4016 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 1fc31743339a489814dba2fa6252662a721fba78..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f5e73a43cc343f471e57eec47d620d4591ec117e5371d272679ef34b2045e182 -size 4147 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg deleted file mode 100644 index 8453a37523060794d319e64f30096485ef51719b..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:47457b67a9ea32290f7a63e5c32f81baa6fd2fc24f861615e58b4da39aa3f47f -size 56601 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index c67e27b13b7bd5f6eaf3516b2be8048a10722465..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8048808466f3b735c52639c6de21d00f2b85e822aa8e85e70561aac36f44caaf -size 4228 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 0bea580b82b985ec6bd9836785eb1050583f8682..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b724ecded9a829c53fd8c426a1ba2377d42d7ab25c4731fa9713baf07a0b7e07 -size 4085 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index a1a021c6cced459e5a30319f5f0e9eb4cee8c91f..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b15fb625969e26fe1f45975f7f45e9ff2d2a2b3a3006dbcaef44fb07ddd8d3bb -size 4016 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/854df8ad60507803253274673f9062cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index a1a021c6cced459e5a30319f5f0e9eb4cee8c91f..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b15fb625969e26fe1f45975f7f45e9ff2d2a2b3a3006dbcaef44fb07ddd8d3bb -size 4016 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 44e4ca1e706fffc218594e75b7fbdfaeee43149d..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ba36991bdae993881d357810ae680e8b2718eeb75c0831521a0cdc2d6e038f2 -size 4147 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index eb19008c827757f1b778398b2c199f4b019bd2c2..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8492d90cd0b607a4d2f8f3e2d5cde875b55d740bbf5a11fbf9488fbfe90ca943 -size 4044 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index c67e27b13b7bd5f6eaf3516b2be8048a10722465..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8048808466f3b735c52639c6de21d00f2b85e822aa8e85e70561aac36f44caaf -size 4228 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/a4b963a07cc368283154762c4b156fe7_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/a4b963a07cc368283154762c4b156fe7_img.jpg deleted file mode 100644 index 71721c1ce9c1c956d8c10a5903785f5684ac1763..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/a4b963a07cc368283154762c4b156fe7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0abb326588254e39771c7371d813a2c60d37f4953b5d66e5c5cad8672ed44027 -size 60946 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index a1a021c6cced459e5a30319f5f0e9eb4cee8c91f..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b15fb625969e26fe1f45975f7f45e9ff2d2a2b3a3006dbcaef44fb07ddd8d3bb -size 4016 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index a1a021c6cced459e5a30319f5f0e9eb4cee8c91f..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b15fb625969e26fe1f45975f7f45e9ff2d2a2b3a3006dbcaef44fb07ddd8d3bb -size 4016 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg deleted file mode 100644 index da88d8b774d5d762c87b2ac430934f62bcf646d8..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3a36037900a867bbdd4b644890b596b09989ef74943d51cec13afde4c33d70fe -size 80445 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 55ed49ea9e83a4b5a07746dbf8f28b9bbc55c537..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a4a27b183ca550898d5d045cdda3ca088b8afbed7e6d4b93b2d6e7424fec0a2a -size 4227 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/e9d825d87c5f85c8dba0664eace96ef4_img.jpg deleted file mode 100644 index 8eb3634148518267e7456994672735685752b19f..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/e9d825d87c5f85c8dba0664eace96ef4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:402e1e23afa321603d6f754f9feff7c665d82905ccc7d947a8100f65b451d647 -size 22123 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 8aa3c88dfd0c141451ecb99f490b476e83716aa8..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.0-R005-v13.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c4548607edcf109ae08a8a65abd06881382b150b24752de51a6131e601fd6207 -size 3897 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/doc.md b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/doc.md deleted file mode 100644 index 0053ef76af2ac606a2dc0c2240c80efce70630d1..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/doc.md +++ /dev/null @@ -1,130 +0,0 @@ - - -# TEST REPORT of O-RAN Certificate and Badge - -| | | | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Certificate/Badge ID | Type of award | | -| OTIC name | O-RAN Conformance Certificate
O-RAN IOT Badge
O-RAN E2E Badge | | -| Requesting entity(ies) names – list of all involved requesting entities | | | -| Referenced O-RAN test specification | | | -| Document name | Version | | -| Test report approval | | | -| OTIC representative – full name, e-mail, phone | Requesting entity representative(s) – full name, e-mail, phone | | -| Copyright © | | | -| Upon completion, this document is for restricted distribution only. No portion of this document may be reproduced or distributed without the written permission of the following copyright holder(s). | | | -| Copyright holders - OTIC and requesting entity(ies) | | | - -## Contents - -- 1 Common test setup configuration parameters .....3 -- 2 Information about DUTs/SUT .....3 - - 2.1 DUT 1.....3 -- 3 Test equipment and tools .....3 -- 4 Test results.....4 - - 4.1 “add Test description as defined in test spec” .....4 - - 4.2 “add Test description as defined in test spec” .....5 - -## 1 Common test setup configuration parameters - -The list of test setup configuration parameters and their values which are common for all tests and can affect the test results (e.g. carrier (central) frequency, sub-carrier spacing, total transmission bandwidth, duplex mode). The test specific parameters shall be listed at each related test. - -ⓘ *Please add any related parameters and their values* - -| Test configuration parameter | Value | -|------------------------------|-------| -| | | -| | | -| | | -| | | -| | | -| | | -| | | -| | | - -## 2 Information about DUTs/SUT - -The test-related information such parameters, supported features about all Devices under test (DUTs)/System under test (SUT) - -ⓘ *Please add individual sub-section per DUT/SUT* - -### 2.1 DUT 1 - -| DUT parameter | Value | -|---------------|-------| -| | | -| | | -| | | -| | | - -## 3 Test equipment and tools - -Utilized test and measurement equipment and tools. - -| ID | Equipment/tool | Vendor name | Model | SW/HW version | Notes | -|----|----------------|-------------|-------|---------------|-------| -| 01 | | | | | | -| 02 | | | | | | -| 03 | | | | | | -| 04 | | | | | | - -## 4 Test results - -### 4.1 “add Test description as defined in test spec” - -| | | -|-------------------------------------------------------|------------------------------------------------------------| -| Test number – as defined in test specification | Test description – as defined in test specification | -| | | -| Tester/Contact person | Date | -| | | -| Status (Pass/Fail) | | -| | | - -#### **List of utilized test and measurement equipment and tools, incl. the specific setting/configuration** - -ⓘ *Please refer IDs of test and measurement equipment and tools from Chapter 3.* - -| ID | Specific test-related setting/configuration | Notes | -|----|---------------------------------------------|-------| -| | | | -| | | | -| | | | - -**Test setup – connection/block diagram – deployment scenario – specific test configuration parameters** - -**Test procedure – describe differences in comparison with the test procedures defined in test specification** - -**Test results – measured KPIs – assessment of measured KPI (in comparison of the expected KPIs) – gap analysis** - -Notes, incl. observed issues with the pass to resolution steps - -### 4.2 “add Test description as defined in test spec” - -| | | -|-------------------------------------------------------|------------------------------------------------------------| -| Test number – as defined in test specification | Test description – as defined in test specification | -| | | -| Tester/Contact person | Date | -| | | -| Status (Pass/Fail) | | -| | | - -List of utilized test and measurement equipment and tools, incl. the specific setting/configuration - -ⓘ *Please refer IDs of test and measurement equipment and tools from Chapter 4.* - -| ID | Specific test-related setting/configuration | Notes | -|-----------|----------------------------------------------------|--------------| -| | | | -| | | | -| | | | - -Test setup – connection/block diagram – deployment scenario – relevant configuration parameters - -Test procedure – describe differences in comparison with the test procedures defined in test specification - -Test results – measured KPIs – assessment of measured KPI (in comparison of the expected KPIs) – gap analysis - -Notes, incl. observed issues with the pass to resolution steps - diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 8e9cbee1488db4b1732f20c050d76c5031e688ad..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:125862a109ce6df6a46bef11691edc8d14069b66b8872a194df89ddff8744d1b -size 4146 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 8aaf9238f26aeb3e0a9ff8e88445ab7582b517eb..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c9d8de9800c5ba2cedfaa85592600e2e34794c0c175626882abf5cd6819555a -size 4146 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 4ed78abde2dc2e625863f2ffe2a8053361bff128..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:876d1c7390bbcf0b39a763d6b218edcf06955f60b924e49e19466b0a8401c5b6 -size 4142 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 7c11f3974a154c8415578b69c8e03a418820d455..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8a1a5fa6f62f444ecef1fad2ad7e6016d3f04cb349c0de8d885dc30f09800983 -size 4146 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 657686c184d42ca248d93ecc95a236c4dff23f83..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ddbe36f26690ae70d5f196e76f05eb0faebaefd698e1bf6e124d8aa381dcfa87 -size 4100 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 8aaf9238f26aeb3e0a9ff8e88445ab7582b517eb..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.2-R005-v13.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c9d8de9800c5ba2cedfaa85592600e2e34794c0c175626882abf5cd6819555a -size 4146 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/doc.md b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/doc.md deleted file mode 100644 index 9dbb89b32016a67e1dd4240c07a1174e757dd308..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/doc.md +++ /dev/null @@ -1,187 +0,0 @@ - - -![O-RAN ALLIANCE logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) - -The logo for the O-RAN ALLIANCE, featuring a colorful circular icon to the left of the text "O-RAN" in blue, with "ALLIANCE" in smaller blue letters underneath. - -O-RAN ALLIANCE logo - -# --- **O-RAN Test and Integration Focus Group****Certification and Badging Profiles** - -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 ..... | 4 | -| 3.1 Terms ..... | 4 | -| 3.2 Symbols..... | 5 | -| 3.3 Abbreviations..... | 5 | -| 4 Introduction ..... | 5 | -| 4.1 Scope..... | 5 | -| 5 Certification and Badging Profiles..... | 5 | -| 5.1 O-RAN Certificates ..... | 5 | -| 5.1.1 A1 services on A1 interface of Near-RT RIC..... | 5 | -| 5.1.2 A1 services on A1 interface of Non-RT RIC..... | 6 | -| 5.2 O-RAN IOT Badges ..... | 6 | -| 5.2.1 A1 services on A1 interface ..... | 6 | -| 5.3 O-RAN E2E Badges ..... | 7 | -| Annex (informative): Change history/Change request (history) ..... | 8 | - -# Foreword - -This Technical Specification (TS) has been produced by TIFG (Test and Integration Focus Group) 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 Certification and Badging Profiles (CB-Profiles) for the purpose of O-RAN Certification and Badging. - -# 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.TIFG.TS.Cert-Badge.0: “Certification and Badging Processes and Procedures” -- [2] O-RAN.WG2.TS.A1AP: “A1 interface: Application Protocol” - -## 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. - -Not applicable - -# 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: - -**Certification and Badging ICS Proforma (CB-ICS Proforma):** An overview of all mandatory/optional/ conditional functions and capabilities defined in base specification(s)/profile and, if exists, in O-RAN Certification and Badging Profile. It helps vendors ensure that their products meet the necessary requirements for O-RAN Certificates and Badges. When the implementation is done, vendor declares which functions and capabilities have been implemented/supported, and so it becomes Certification and Badging ICS. - -**Certification and Badging ICS (CB-ICS):** A statement made by the vendor of an implementation stating which functions and capabilities have been implemented/supported for the purpose of O-RAN Certificate or Badge. The Certification and Badging ICS (CB-ICS) is attached to O-RAN Certificate, IOT Badge or E2E Badge. - -**Certification and Badging Profile (CB-Profile):** For the purpose of O-RAN Certification and Badging, the CB-Profile may constrain the existing options in base specification(s)/profile, and shall not impose requirements that conflict with the existing requirements in base specification(s)/profile (e.g. a function/capability/ parameter mandatory in the base specification shall not be optional in the profile; or adding new function/capability/parameter that does not exist in the base specification is not allowed). - -## 3.2 Symbols - -For the purposes of the present document, the symbols [given in [i.1] and the following] apply: - -Void - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations [given in [i.1] and the following] apply: - -| | | -|------------|--------------------------------------------------------------------| -| CB | Certification and Badging | -| CB-ICS | Certification and Badging Implementation and Conformance Statement | -| CB-Profile | Certification and Badging Profile | -| ICS | Implementation Conformance Statement | -| TIFG | O-RAN Test and Integration Focus Group | - -# --- 4 Introduction - -## 4.1 Scope - -For the purpose of O-RAN Certification and Badging and to facilitate O-RAN productization, the O-RAN Certification and Badging Profile (CB-Profile) [1] may be used to constrain the existing options in base specification(s)/profile, but shall not impose requirements that conflict with the existing requirements in base specification(s)/profile (e.g. a function/capability/parameter mandatory in the base specification shall not be optional in the profile; or adding new function/capability/parameter that does not exist in the base specification is not allowed.) - -For O-RAN certificates, one CB-Profile is defined for each device and interface/service under test, e.g. Open FH O-RU, Open FH O-DU. For O-RAN IOT Badge, one CB-Profile is defined for each interface/service under test including both devices in the pair, e.g. Open FH (including both O-RU and O-DU). For O-RAN E2E Badge, one CB-Profile is defined for the whole system under test (not to individual devices and interfaces) and to E2E functionalities and capabilities. - -# --- 5 Certification and Badging Profiles - -## 5.1 O-RAN Certificates - -### 5.1.1 A1 services on A1 interface of Near-RT RIC - -The O-RAN Certificate for A1 services of Near-RT RIC is defined in [1], clause 6.5. The services and related service procedures of A1 application protocol are specified in [2]. - -For the purpose of O-RAN Certification of A1 services of Near-RT RIC, the following constraints applied: - -- 1) At least one A1 service shall be implemented and supported by Near-RT RIC -- 2) If A1 policy management service (A1-P) is supported by Near-RT RIC (A1-P Producer), then the following A1 service procedures shall be supported: - - a) Create Policy [2], clause 5.2.4.3 - -- b) Delete Policy [2], clause 5.2.4.6 -- 3) If A1 enrichment information service (A1-EI) is supported by Near-RT RIC (A1-EI Consumer), then the following A1 service procedures shall be supported: - - a) Create EI job [2], clause 5.3.4.3 - - b) Delete EI job [2], clause 5.3.4.6 - - c) Deliver EI job result [2], clause 5.3.5.2 - -### 5.1.2 A1 services on A1 interface of Non-RT RIC - -The O-RAN Certificate for A1 services of Non-RT RIC is defined in [1], clause 6.4. The services and related service procedures of A1 application protocol are specified in [2]. - -For the purpose of O-RAN Certification of A1 services of Non-RT RIC, the following constraints applied: - -- 1) At least one A1 service shall be implemented and supported by Non-RT RIC -- 2) If A1 policy management service (A1-P) is supported by Non-RT RIC (A1-P Consumer), then the following A1 service procedures shall be supported: - - a) Create policy [2], clause 5.2.4.3 - - b) Delete policy [2], clause 5.2.4.6 -- 3) If A1 enrichment information service (A1-EI) is supported by Non-RT RIC (A1-EI Producer), then the following A1 service procedures shall be supported: - - a) Create EI job [2], clause 5.3.4.3 - - b) Delete EI job [2], clause 5.3.4.6 - - c) Deliver EI job result [2], clause 5.3.5.2 - -## 5.2 O-RAN IOT Badges - -### 5.2.1 A1 services on A1 interface - -The O-RAN IOT Badge for A1 services between Near-RT RIC and Non-RT RIC is defined in [1], clause 7.6. The services and related service procedures of A1 application protocol are specified in [2]. - -For the purpose of O-RAN IOT Badge of A1 services of between Near-RT RIC and Non-RT RIC, the following constraints applied: - -- 1) At least one A1 service shall be implemented and supported by Near-RT RIC and Non-RT RIC. Both Near-RT RIC and Non-RT RIC shall support and implement the same A1 service(s). -- 2) If A1 policy management service (A1-P) is supported by Near-RT RIC (A1-P Producer) and Non-RT RIC (A1-P Consumer), then the following A1 service procedures shall be supported: - - a) Create policy [2], clause 5.2.4.3 - - b) Delete policy [2], clause 5.2.4.6 -- 3) If A1 enrichment information service (A1-EI) is supported by Near-RT RIC (A1-EI Consumer) and Non-RT RIC (A1-EI Producer), then the following A1 service procedures shall be supported: - - a) Create EI job [2], clause 5.3.4.3 - - b) Delete EI job [2], clause 5.3.4.6 - - c) Deliver EI job result [2], clause 5.3.5.2 - -## 5.3 O-RAN E2E Badges - -# --- Annex (informative): Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|------------------------| -| 2025.07.18 | 12.00 | First version (v12.00) | -| 2025.11.28 | 13.00 | | \ No newline at end of file diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 28bb647ed6185969a150f46f2f7fe9830315e540..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:cd1a52e6fa582e32159028a334cf8d6cf16e5d4052d60db17a8cc412be38e72f -size 4534 diff --git a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg deleted file mode 100644 index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_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/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.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/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/7ccb49293384cf59a3bbe659b053f3cc_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/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/8dcca7651accff77ce832523fe2c7e64_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/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.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/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.Cert-Badge.6-R005-v13.00/O-RAN.TIFG.TS.Cert-Badge.4-R005-v13.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/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/doc.md b/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/doc.md deleted file mode 100644 index d8fcc72c3454b4a91f6c7042af0da6759e3b8469..0000000000000000000000000000000000000000 --- a/files/TIFG/O-RAN.TIFG.TS.E2E-Test.0-R005-v09.00/doc.md +++ /dev/null @@ -1,6873 +0,0 @@ - - -# --- **O-RAN Test and Integration Focus Group****End-to-end Test 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., 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.....7 - -3 Definition of terms, symbols and abbreviations.....7 - -3.1 Terms.....7 - -3.2 Symbols.....8 - -3.3 Abbreviations .....8 - -4 Testing methodology and configuration.....9 - -4.0 Testing methodology introduction .....9 - -4.1 System under test .....10 - -4.2 Test and measurement equipment and tools.....11 - -4.3 Test report .....13 - -4.4 Data traffic.....14 - -4.5 Mobility classes.....16 - -4.6 Radio conditions.....16 - -4.7 Inter-cell interference .....17 - -4.8 Spectral efficiency.....18 - -5 Functional tests.....18 - -5.0 Functional tests introduction .....18 - -5.1 LTE/5G NSA attach and detach of single UE .....19 - -5.2 LTE/5G NSA attach and detach of multiple UEs.....21 - -5.3 5G SA registration and deregistration of single UE .....24 - -5.4 Intra O-DU mobility .....26 - -5.5 Inter O-DU mobility .....28 - -5.6 Inter O-CU mobility .....31 - -5.7 Registration and deregistration to a single network slice .....34 - -5.8 Registration and deregistration to multiple network slices.....36 - -5.9 Idle Mode Intra O-DU mobility .....40 - -5.10 Idle mode Inter O-DU mobility .....42 - -5.11 Idle mode Inter O-CU mobility .....45 - -5.12 5G/4G Inter-System Mobility - 5GS to EPS handover .....47 - -5.13 5G/4G Inter-System Mobility - EPS to 5GS handover .....49 - -6 Performance tests .....50 - -6.0 Performance tests introduction.....50 - -6.1 Expected throughput calculation .....51 - -6.2 Downlink peak throughput.....54 - -6.3 Uplink peak throughput.....57 - -6.4 Downlink throughput in different radio conditions .....59 - -6.5 Uplink throughput in different radio conditions .....61 - -6.6 Bidirectional throughput in different radio conditions .....63 - -6.7 Downlink coverage throughput (link budget).....66 - -6.8 Uplink coverage throughput (link budget) .....68 - -6.9 Downlink aggregated cell throughput (cell capacity).....71 - -6.10 Uplink aggregated cell throughput (cell capacity).....74 - -6.11 Impact of fronthaul latency on downlink peak throughput.....77 - -6.12 Impact of fronthaul latency on uplink peak throughput .....80 - -6.13 Impact of midhaul latency on downlink peak throughput .....82 - -6.14 Impact of midhaul latency on uplink peak throughput .....85 - -6.15 End-to-end user plane latency .....87 - -- 7 Services tests .....90 - - 7.0 Services tests introduction.....90 - - 7.1 Data services tests .....90 - - 7.2 Video streaming tests .....97 - - 7.3 Voice Services – Voice over LTE (VoLTE) tests .....111 - - 7.4 Voice Service – EPS Fallback tests.....118 - - 7.5 Voice Service – Voice over NR (VoNR) tests .....123 - - 7.6 Video Service – Video over LTE (ViLTE) tests .....135 - - 7.7 Video Service – EPS Fallback.....142 - - 7.8 Video Service – Video over NR.....146 - - 7.9 URLLC.....158 - - 7.10 mMTC .....163 -- 8 Load and stress tests .....165 - - 8.0 Load and stress tests introduction.....165 - - 8.1 Simultaneous RRC\_CONNECTED UEs .....166 - - 8.2 UE State Transition Rate Testing .....168 - - 8.3 Traffic Load Testing.....171 - - 8.4 Traffic Model Testing .....173 - - 8.5 Long hours stability Testing.....177 - - 8.6 Multi-cell Testing.....178 - - 8.7 Emergency call.....180 - - 8.8 ETWS (Earthquake and Tsunami Warning System) .....181 - - 8.9 MPS call .....183 - - 8.10 Simultaneous RRC\_CONNECTED UEs Stability .....185 -- 9 RIC-enabled end-to-end use case test .....186 - - 9.0 RIC-enabled end-to-end use case test introduction .....186 - - 9.1 Test Setup and Methodology.....187 - - 9.2 Traffic steering with connected mode mobility control.....187 - - 9.3 Network Energy Saving with Carrier and Cell switch off/on using Non-RT RIC .....197 -- 10 Profile-based Performance Tests.....204 - - 10.1 Introduction .....204 - - 10.2 Test Configuration Profile.....205 - - 10.3 Measurements, KPIs and Logs.....210 - - 10.4 Test Cases.....212 -- Annex A (normative): Template of test report .....214 -- Annex B (informative): Example of Pseudo Random Sequence Generation for UE Activity .....217 -- Annex C (informative): Change history/Change request (history).....220 - -# --- Foreword - -This Technical Specification (TS) has been produced by TIFG 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 methodology, procedures, configurations, and pass/fail criteria (when applicable) for end-to-end testing of an O-RAN system. It is focused on validating the end-to-end system functionality, performance, and key features of the O-RAN system as a black box. It is based on the principles outlined in the end-to-end system test framework document [11]. - -# 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] Void -- [2] 3GPP TR 36.104, “Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception” -- [3] NGMN Alliance, “Definition of the testing framework for the NGMN 5G pre-commercial networks trials”, White paper July 2019, version 3.0. Available: -- [4] NGMN Alliance, “NGMN 5G pre-commercial networks trials - major conclusions”, White paper, December 2019, version 1.0. Available: -- [5] 3GPP TR 38.913: “Study on new radio access technology Radio interface protocol aspects”, March 2017. -- [6] IETF RFC7323, “TCP Extensions for High Performance”, September 2014 -- [7] 3GPP TS 38.215, “Physical layer measurements”, September 2020 -- [8] 3GPP TS 36.133, “Requirements for support of radio resource management” -- [9] 3GPP TS 38.133, “Requirements for support of radio resource management” -- [10] O-RAN ALLIANCE, “O-RAN Architecture Description v11.0”, February 2024 -- [11] O-RAN ALLIANCE, “O-RAN End-to-End System Testing Framework Specification 1.0”, July 2020 -- [12] O-RAN ALLIANCE, “O-RAN Fronthaul Interoperability Test Specification (IOT) 2.0”, April 2020 -- [13] ITU-R M.2410-0, “Minimum requirements related to technical performance for IMT-2020 radio interface(s)”, November 2017. -- [14] 3GPP TR 36.814, “Further advancements for E-UTRA physical layer aspects”, March 2017 -- [15] 3GPP TS 38.306, "User Equipment (UE) radio access capabilities", December 2020 -- [16] O-RAN ALLIANCE, “O-RAN Fronthaul Control, User and Synchronization Plane Specification v5.0”, November 2020 -- [17] 3GPP TS 38.300, “NR and NG-RAN Overall Description; Stage 2”, December 2020 -- [18] 3GPP TS 38.101-1, “User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone”, December 2020 - -- [19] 3GPP TS 38.101-2, "User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone", December 2020 -- [20] 3GPP TS 38.211, "Physical channels and modulation", December 2020 -- [21] 3GPP TS 38.213, "Physical layer procedures for control", December 2020 -- [22] 3GPP TS 38.214, "Physical layer procedures for data", December 2020 -- [23] 3GPP TR 38.308, "Physical Layer Aspects", September 2017 -- [24] 3GPP TSG RAN WG1 Meeting #92 R1-1801352, "Discussion on NR UE peak data rate", March 2018 -- [25] 3GPP TS 36.211, "Physical channels and modulation", September 2020 -- [26] 3GPP TR 38.801, "Radio access architecture and interfaces", March 2017 -- [27] 3GPP TS 33.511: "Security Assurance Specification (SCAS) for the next generation Node B (gNodeB) network product class" (Release 16), September 2020 -- [28] 3GPP TS 23.502, "Procedures for the 5G System; Stage-2", December 2020 -- [29] 3GPP TS 23.401 "General Packet Radio Service (GPRS)enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access" -- [30] 3GPP TS 37.340 "Overall description; Stage-2" -- [31] 3GPP TS 38.401 "5G; NG-RAN; Architecture description" -- [32] 3GPP TS 38.473 "5G; NG-RAN; F1 Application Protocol (F1AP)" -- [33] 3GPP TS 37.470 "W1 interface General aspects and principles", July 2020 -- [34] NGM Alliance, "Vertical URLLC Use Cases and Requirements", February 2020, version 2.5.4. Available: -- [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 - -![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.](0bf9346902e9a3bdabf05ceacc1947f5_img.jpg) - -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.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) - -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)'.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) - -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. - -![Diagram of interfaces for applying incremental traffic to System Under Test (SUT).](d26959f4514c26ca19c3d6f00da85956_img.jpg) - -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.](f1fbb1287d999c7034742de35bdab836_img.jpg) - -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.](a149b400127a3e3e50b3c98d27c5935c_img.jpg) - -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.](6ca05954842b17f14dfd52f26b9d43d2_img.jpg) - -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.](f2ea0f64a770b22b902820457d262265_img.jpg) - -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. - -![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.](ca5dc5fde2061d0ca2051ef7840fc842_img.jpg) - -``` - -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.](e05b36c0d46549e681ce6581422c66b2_img.jpg) - -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.](eb1a67ebd688e354edaacb7ec2abf5ad_img.jpg) - -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.](834fb96b114b8fdc001625e1ae28e8b1_img.jpg) - -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.](a97518a839da75f8379c578562b01bc2_img.jpg) - -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.](a780a960b3f2de2493d5785bedae10ff_img.jpg) - -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.](068e6688fd646417399f8e6e50b85816_img.jpg) - -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. - -![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](6b26e27af9601d90852f430c44907bad_img.jpg) - -**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.](66e89867f97592fd4bfab0e4f2b2054f_img.jpg) - -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.](dfe74512a9c9fb620f72c9dbc22874aa_img.jpg) - -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.](b2e5ca10383692a39c97d8b9929bcd6d_img.jpg) - -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.](10f4e3a2f3c016555ee12a5b556ba834_img.jpg) - -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.](f6442d68601dfecfe5f7f8a70449a2f7_img.jpg) - -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.](16d5f9c016e78737423c11d4fba9ae25_img.jpg) - -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 - -![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).](0b8f0df92a831a94cdac664d8b05f0ec_img.jpg) - -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. - -![Figure 9-3: Illustration of UE distribution pattern (a) uniform (b) non-uniform](2427b810c52b62eddbd06f403f165ce7_img.jpg) - -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 - -![Figure 9-4: Illustration of UE trajectory pattern (a) deterministic route (b) random walk](aad0bf105da453377b319a03d9074beb_img.jpg) - -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.](4c4a5bb88d303bdd784fcae1ddb08539_img.jpg) - -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. - -![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.](c68466afb0a12ea87dc7cf27b72fcd20_img.jpg) - -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.](f9802d8871078af5421372727c628e2a_img.jpg) - -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.](03703ee0fb20f67f19e3eb7c97a4b1e4_img.jpg) - -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.](2cdc3be3de33b97cdd52a0805b399419_img.jpg) - -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
    1. Bi-Directional Full-buffer TCP / UDP data transmission (see clause 4.4) from the application server Sections 6.6.3, 6.6.4
    2. Uplink Full-buffer TCP / UDP data transmission
    3. Downlink Full-buffer TCP / UDP data transmission
    4. Voice Service – Voice over NR (VoNR) Section 7.5.1
    5. 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 |
  • VoNR MOS Score
| | -| 1.7 |
  • ViNR MOS Score
| | -| | 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 |
  • RSRP [dBm]
  • RSRQ [dB]
  • CQI
| | -| 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 |
  • VoNR MOS Score
| | -| 2.5 |
  • ViNR MOS Score
| | - -## 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).](29640f9496773db15b016e35bb17d5b8_img.jpg) - -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.](43b05bd1b6ee31fba18d3eb683903504_img.jpg) - -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'.](07bf92e869a2102e532783b036547f26_img.jpg) - -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'.](d26959f4514c26ca19c3d6f00da85956_img.jpg) - -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.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) - -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 - -``` - -![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.](a26e142d3df5bef41a84a9dd099d7825_img.jpg) - -``` - -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'.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) - -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'.](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) - -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'.](9cd90f495b95ad2116ff780248c26d95_img.jpg) - -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.](10781f43062bf3e9601a1e086710556c_img.jpg) - -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.](523ab7b925beb555f88b2e1e1336974f_img.jpg) - -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.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) - -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. - -![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.](bd4617f25d15430eb78c2d6d75a99dde_img.jpg) - -| 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'.](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) - -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'.](d734a6ea1b381280f043fcf70391b6db_img.jpg) - -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.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) - -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.](552265bdbcf6d43d341fd018a9076269_img.jpg) - -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.](f1fbb1287d999c7034742de35bdab836_img.jpg) - -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 - -``` - -![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).](dcb5711d118ae6753b0e12f86eda37db_img.jpg) - -``` - -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 - -``` - -![Sequence diagram showing performance information reporting and scaling triggers between Orchestrator, SMO, IMS/DMS, and Node 1.](e05b36c0d46549e681ce6581422c66b2_img.jpg) - -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.](1142ba0197b158bb198186fe8baccc32_img.jpg) - -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 -``` - -![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.](96bfe678265c45ada94af2d97be9d002_img.jpg) - -``` -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 - -``` - -![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.](b58cedaf15ad4f0edee5621820865ccc_img.jpg) - -``` - -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 - -``` - -![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.](95e259e8cb3519025066052af263f8c0_img.jpg) - -``` - -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.](8269648391c59363ea61243864a2adf7_img.jpg) - -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.](0c80c383f76034e117adf5e5eaadaaf3_img.jpg) - -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 - -``` - -![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.](8e80de0cac529b2c3775d677c5203133_img.jpg) - -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.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) - -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.](a3083eec2a883ee8327b3c24174df6a9_img.jpg) - -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. - -![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.](ec3647789b5c38fb686f2a0833324e79_img.jpg) - -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).](a7c51c18111139f9aca2805114108565_img.jpg) - -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'.](16152cf1d84aea10848758f51a91ff6a_img.jpg) - -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.](bc453b6a6e6a96bdafd56edb6ea9d14b_img.jpg) - -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.](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) - -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.](90ddb84c323b956e2d50a54d3f870566_img.jpg) - -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.](031bd5c072298c549b99e157de88dfbf_img.jpg) - -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'.](39ca823ef41ba00da416ecc099940770_img.jpg) - -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.](a11a74eff5bf35900dc491470141e2e9_img.jpg) - -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.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) - -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:
    1. KEY, AAL - CR 0001 – Introduction - v2
    2. 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:
    1. 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:
    1. KEY, AAL – CR 0005 - fix clause 1-3 and change history - v3
    2. 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:
    1. AAL, KEY, RAD CR-0005
    2. 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. - -![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.](8e14350b4b669119a3bdfca7869110ca_img.jpg) - -``` - -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.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) - -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. - -![Diagram of UAV control vehicle application scenario showing various UAVs and ground stations connected to a central 5G gNB via 5G network transmissions.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) - -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.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) - -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 - -![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).](8307f6b04df072c9332f9987e034272c_img.jpg) - -``` - -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 - -![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.](4356776ca004ecba5d599667a155d7d4_img.jpg) - -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 - -![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).](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) - -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. - -![AI/ML QoE enhancements concept diagram](5445597cceefaca1ac89e710fe339325_img.jpg) - -``` - -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 - -![Radio performance analytics information exposure, through local NEF diagram](e636d7ccca0ad14c6b95201404324823_img.jpg) - -``` - -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 - -![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'.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) - -``` - -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. - -![Diagram of Non-RT and Near-RT optimization loops.](5132b3a97ac70fe4765c1e07e66b72b3_img.jpg) - -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. - -![Diagram of Non-RT Beam Forming (BF) optimization architecture.](a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg) - -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. - -![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.](5a1abd59a95fa47ae192807de151e9eb_img.jpg) - -``` - -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. - -![Diagram of Near-RT Beam Selection Optimized (BSO) function architecture](a149b400127a3e3e50b3c98d27c5935c_img.jpg) - -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).](e9b43ac020435f8121e8592f31afdc52_img.jpg) - -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. - -![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.](b5335262987c819d7f71ce40f99cb71b_img.jpg) - -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. - -![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.](8658cfab6a458b4a80ab2e384c61ff89_img.jpg) - -``` - -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.](dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg) - -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.](a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg) - -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. - -![Figure 4.11.3-1: RIC-based DSS architecture](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) - -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 - -![Figure 4.11.3-2: RIC-based DSS realization](b2f5606b9c7184c1c6070a290080a3e3_img.jpg) - -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. - -![Diagram illustrating the realization of NSSI resource allocation optimization over Non-Real Time RIC.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) - -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.](e05122559f56af5699789b7118d8fe87_img.jpg) - -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.](8269648391c59363ea61243864a2adf7_img.jpg) - -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'.](0c80c383f76034e117adf5e5eaadaaf3_img.jpg) - -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). - -![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.](41aef1f5efab13d4f38f69e86c726062_img.jpg) - -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. - -![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.](a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg) - -``` - -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.](08f6ace0c83e7394657fa372b47aec04_img.jpg) - -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).](640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg) - -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.](255efa1d461fc79b4ed367aaec11637f_img.jpg) - -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. - -![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.](3c99312f83459559d9a301148555d7b9_img.jpg) - -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).](01832e59ebad7ada5e790de6f90cc9b6_img.jpg) - -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. - -![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.](68a5a1a1a761c652b4b4c56da7cf9914_img.jpg) - -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.](fed4a04822c24fb22cca3a14f4ddae83_img.jpg) - -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.](6d2057d7e401741861ca63545a5d7d3b_img.jpg) - -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. - -![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.](9d49325b5cb2d7a1431cb30637b5a7c9_img.jpg) - -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. - -![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.](52c40e2f443985dc63f45dec57d90c8c_img.jpg) - -**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. - -![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.](3ce04f1c7128814978c6b34d654a25cc_img.jpg) - -**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. - -![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.](742a5484e7dd016256ab99921bbd635d_img.jpg) - -**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: - -![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.](b35ea3e304aad7d350a9902270413930_img.jpg) - -``` - - 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: - -![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.](24ca460ee3381aee781887e9e586ec67_img.jpg) - -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).](d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg) - -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'.](350dece6293a0ac3d4c9e4bf41eefa5d_img.jpg) - -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'.](907ece8ef4e70ee3f584e07ad4fd2df4_img.jpg) - -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'.](bb3063a33c89b248574f64b6d8dfc404_img.jpg) - -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. - -![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'.](318f02285df33c4d38cdad30845972d4_img.jpg) - -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.](b1784a5cbeeb3d9fb9e60b333019c721_img.jpg) - -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.](37806e0fc150d857046ebc7e47893d7a_img.jpg) - -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. - -![Diagram of Interference prediction for MCS optimization architecture](2b60ebe01f77d22e53da1fbe73083b01_img.jpg) - -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'.](dcf83796ccf494110638fbd4677b931d_img.jpg) - -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.](90183a52275501da5a0fd5c63d837009_img.jpg) - -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.](b1e7bb95fa1587d870de03df02477df4_img.jpg) - -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. - -![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.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) - -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.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) - -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.](a26e142d3df5bef41a84a9dd099d7825_img.jpg) - -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 - -![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.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) - -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]. - -![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.](2cde062fd82833415971a8bd1a2cafab_img.jpg) - -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. - -![Service-based representation of Near-RT RIC architecture showing xApps connected to a Near-RT RIC platform via Near-RT RIC API(s).](124c6108c63173818afb8ed49521e22d_img.jpg) - -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).](a149b400127a3e3e50b3c98d27c5935c_img.jpg) - -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.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg) - -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. - -![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).](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) - -``` - -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. - -![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.](4af57aad638888edf2062306f8a54a6c_img.jpg) - -``` - -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.](dcb5711d118ae6753b0e12f86eda37db_img.jpg) - -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).](fa01531ea2c45beeb4036005da3037a4_img.jpg) - -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.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) - -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.](dcf37c460c66ec011dbe6ca08de44ff9_img.jpg) - -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.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) - -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.](14252bcd35912bd656e98b16b2ee51c0_img.jpg) - -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.](9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg) - -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** - -![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).](318886a86a1dcc59e1fc83db6f157c60_img.jpg) - -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]. - -![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.](cfb98c691c1af5befe32ff9442eea511_img.jpg) - -``` - -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. - -![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.](a1890b9a9b85f13e67ed59bbad623659_img.jpg) - -``` - -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.](a7d78d22e465dea388b31d0739f9d0cd_img.jpg) - -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.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) - -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. - -![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).](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) - -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.](2cde062fd82833415971a8bd1a2cafab_img.jpg) - -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. - -![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.](523ab7b925beb555f88b2e1e1336974f_img.jpg) - -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. - -![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.](73dff6b45b2b9ffd384bab3235f869af_img.jpg) - -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.](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) - -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. - -![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).](e354b57563dae469c00b412b2abdf765_img.jpg) - -``` - -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.](dcb5711d118ae6753b0e12f86eda37db_img.jpg) - -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. - -![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).](14252bcd35912bd656e98b16b2ee51c0_img.jpg) - -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. - -![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.](dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg) - -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:
  1. a) QoS targets
  2. 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. - -![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.](e151d3468319b81f042ca232c4d82e4b_img.jpg) - -``` - -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. - -![Sequence diagram for Enrichment information-based traffic steering use case flow. The diagram shows interactions between Service Management and Orchestration (Collection & Control), Non-RT RIC (Non-RT RC FW, Traffic Steering rApp, UE Location rApp), Near-RT RIC, and O-RAN E2 Nodes. Key steps include: 1. A1-EI request for UE trajectory prediction. 2-3. R1 requests for trajectory prediction and network data. 4-7. Optional O1 data collection by SMO. 8. R1 data distribution. 9. Determining UEs of interest. 10-12. R1 requests for UE location prediction and network data. 13-16. Another optional O1 data collection. 17. R1 data distribution. 18. Predicting UE location (repeated per UE). 19-23. Returning predictions and analyzing results. 24-25. Near-RT RIC congestion mitigation. 26-30. Ceasing requests. 31-32. Optional SMO cease data collection.](e22af684d8e56d4c61e61bb5ddac1087_img.jpg) - -``` - -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 <> data - end - -``` - -Sequence diagram for Enrichment information-based traffic steering use case flow. The diagram shows interactions between Service Management and Orchestration (Collection & Control), Non-RT RIC (Non-RT RC FW, Traffic Steering rApp, UE Location rApp), Near-RT RIC, and O-RAN E2 Nodes. Key steps include: 1. A1-EI request for UE trajectory prediction. 2-3. R1 requests for trajectory prediction and network data. 4-7. Optional O1 data collection by SMO. 8. R1 data distribution. 9. Determining UEs of interest. 10-12. R1 requests for UE location prediction and network data. 13-16. Another optional O1 data collection. 17. R1 data distribution. 18. Predicting UE location (repeated per UE). 19-23. Returning predictions and analyzing results. 24-25. Near-RT RIC congestion mitigation. 26-30. Ceasing requests. 31-32. Optional SMO cease data collection. - -Figure 4.5.3.2-1: Enrichment information-based traffic steering use case flow diagram - -### 4.5.4 Required data - -The measurement counters and KPIs (as defined by 3GPP and will be extended for O-RAN use cases) shall be appropriately aggregated by cell, QoS type, slice, etc. - -- 1) Measurement reports with RSRP/RSRQ/CQI information for serving and neighboring cells. In multi-access scenarios this will also include intra-RAT and inter-RAT measurement reports, cell quality thresholds, CGI reports and measurement gaps on per-UE or per-frequency. - -- 2) UE connection and mobility/handover statistics with indication of successful and failed handovers, etc. -- 3) Cell load statistics such as information in the form of number of active users or connections, number of scheduled active users per TTI, PRB utilization, and CCE utilization. -- 4) Per user performance statistics such as PDCP throughput, RLC or MAC layer latency, etc. -- 5) UE level measurements useful in calculating UE location, such as RRC and timing advance measurements. - -## 4.6 Massive MIMO optimization - -This use case provides the motivation, description, and requirements for Non-RT and Near-RT loop massive MIMO beamforming optimization use case. Massive MIMO system configuration can allow operators to optimize the network performance and QoS by e.g. Non-RT and Near-RT loop balancing cell loads or reducing inter-cell interference and control electromagnetic (EM) emissions. - -### 4.6.1 Background and goal of the use case - -#### 4.6.1.1 Common aspects & background of all Massive MIMO optimization use cases - -Massive MIMO (mMIMO) is among the key levers to increase performance and QoS in 5G networks. Capacity enhancement is obtained by means of beamforming of the transmitted signals, and by spatially multiplexing data streams for both single user (SU) and for multi-user (MU) MIMO. Beamforming increases the received signal power, while decreasing the interference generated on other users, hence resulting in higher SINR and user throughputs. Beamforming can be codebook based (mainly for FDD), or non-codebook based (TDD). Grid of Beams (GoB) with the corresponding beam sweeping has been introduced to allow beamforming the control channels used during initial access, mainly for high frequency (but can be used also for the sub-6 GHz band) MIMO operation. The codebook and the GoB define the span of the beams, namely the horizontal and vertical aperture in which beamforming is supported, and therefore the coverage area and the shape of the cell. Massive MIMO can be deployed in 5G macro-cells as well as in heterogeneous network, where macro-cells and 3D-MIMO small cells co-exist and complement each other for better aggregated capacity and coverage. In order to obtain an optimal beamforming and cell resources (Tx power, PRB) configuration, one will have to look at a multi-cell environment instead of a single cell. Moreover, different vendors can have different implementations in terms of the number of beams, the horizontal/vertical beam widths, azimuth and elevation range, to achieve the desired coverage. In a multi-node/multi-vendor scenario, centralized monitoring and control is required to offer optimal coverage, capacity and mobility performance as well as control over EM emissions in order to comply with regulatory requirements. Additionally, the number of such combinations of adjustable parameters is in the thousands, hence it is prohibitive for the traditional human expert system to work out the optimal configuration, and a new method is in need. - -State of the art solutions suffer from the following problems: - -mMIMO macro- and small-cells benefit from a flexible way of serving users in their coverage area thanks to beamforming. However, the coverage area itself is defined by (vendor specific) fixed mMIMO system parameters such as the azimuth and elevation angle range, or the GoB parameters. Hence due to user and traffic distribution and terrain topology, the mMIMO cell can suffer from e.g. - -- 1) High inter-cell interference -- 2) Unbalanced traffic between neighboring cells -- 3) Low performance of cell edge users -- 4) Poor handover performance - -Moreover, load balancing functions can be activated in the network nodes, e.g. gNB adapting mobility parameters in order to distribute load between the beams of the neighbor cells, relying on load information exchange over network interfaces. This approach however is partly limited by the cell footprint statically fixed at the initial configuration. - -The objective of this use case is to allow the operator to flexibly configure a mMIMO system parameters by means of policies and configuration assisted by machine learning techniques, according to objectives defined by the operator. - -#### 4.6.1.2 Cell shaping optimization - -Traditionally network coverage in a cellular network is defined by the coverage provided by the union of all the cells in the network. The individual coverage of a cell is determined by aspects including frequency band, radio emission power, orientation and tilt of the antenna, etc. The coverage of a given radio site would include one or multiple cells or sectors, and the coverage if each of these cells/ sectors is relatively static in nature. - -One of the challenges for operators in deployment their networks is maximizing the efficiency of the spectrum deployed. Because spectrum is both very scarce and expensive, enhancing this efficiency can significantly help improve the operations and business for the wireless network operator. - -As the traffic profile evolves during the day and driven by special circumstances and events, it has become necessary to have the ability to dynamically modify the shapes of the cells to tune the cell coverage to the evolving traffic needs. - -The shape of the cell corresponds to the shape of the coverage provided by the sector carrier. - -Cell shaping is designed for FDD or for TDD mid-band deployments for NR and LTE (if and when O-RAN looks into LTE). It allows the adjustment of cell footprint by adjusting by configuring the vertical and horizontal coverage width of the common beam into combinations to describe a valid supported shape as driven by O-RU capabilities and then refined through further adjustments with the tilt. The data beams, which carry user traffic, are impacted the serving cell shape changes from the cell shaping optimization. The configurable cell shape allows for coverage control, interference reduction, and better power utilization. However, with the increased optimization comes the challenge of more complexity. - -NR cell shaping optimizes cell shaping via different configuration of RET and digital tilt. The optimization leverages algorithms to consider the network configuration and conditions in both the acting and the neighbour cells. The benefits from NR cell shaping include: - -- Dynamic, adaptation of the network changes and traffic distribution with beam width optimization. -- Reduction and/or improvements of interference to optimize quality and cell overlapping. -- Intra-frequency load balancing. -- The ability to execute different policies according to operator needs. - -### 4.6.2 Entities/resources involved in the use case - -#### 4.6.2.1 Non-RT massive MIMO GoB beam forming optimization - -- 1) Non-RT RIC: - - a) Retrieve necessary configurations, performance indicators, measurement reports, user activity information and other data from SMO and RAN directly for the purpose of constructing/training relevant AI/ML models that will be deployed in Non-RT RIC to assist in the massive MIMO optimization function. - - b) Retrieve necessary user location related information, e.g., GPS coordinates, from the application layer for the purpose of constructing/training relevant AI/ML models. - - c) Use the trained AI/ML model to infer the user distribution and traffic distribution of multiple cells and predict the optimal configuration of massive MIMO parameters for each cell/beam according to a global optimization objective designed by the operator. The massive MIMO configurable parameters includes horizontal beam width, vertical beam width, beam azimuth and downtilt, maximum and average transmitted power per beam/direction as specified in 3GPP TS 28.541 [5]. - - d) Send the optimal beam pattern configuration to SMO configuration components. - - e) Retrain the AI/ML model and re-optimize the beam pattern configurations based on the monitored performance. - - f) Execute the control loop periodically or event-triggered. - -- 2) SMO: - - a) Collect the necessary configurations, performance indicators, and measurement reports data from RAN nodes triggered by Non-RT RIC if required. - - b) Configure the optimized beam parameters via O1 interface. - - c) Monitor the performance of all the cells; when the optimization objective fails, initiate fall-back procedure; meanwhile, trigger the AI/ML model re-training, data analytics and optimization in Non-RT RIC. -- 3) E2 nodes: - - a) Collect and report to SMO and/or to Near-RT RIC KPI related to user activity, traffic load, coverage and QoS performance, per beam/area, handover, and beam failures statistics. - - b) Collect and report to SMO and/or to Near-RT RIC information about beam and resource utilization. - - c) Apply beam management strategies following SMO and Near-RT RIC configuration and constraints. - -#### 4.6.2.2 Near-RT beam-based mobility robustness optimization - -- 1) SMO: - - a) Trigger bMRO configuration. (O) - - b) Send bMRO configuration target to Near-RT RIC. - - c) Send GoB beam pattern related information (beam pattern configuration, beam pattern configuration list, beam pattern configuration switch timing/condition, beam pattern identifier etc.) to the Near-RT RIC. -- 2) Near-RT RIC: - - a) Retrieve necessary configurations, performance indicators, measurement reports and other data from E2 nodes for the purpose of training of relevant AI/ML models. - - b) Use the trained AI/ML models to infer the correlation between the Grid-of-Beam configuration, handover, and beam failure statistics of multiple cells and beams, and to predict the optimal configuration of mobility parameters (e.g., beam individual offsets for beam mobility) for each cell/beam pair optionally according to a global optimization objective designed by the operator and retrieved from the SMO. - - c) Send the optimal beam mobility parameter configurations to E2 nodes as specified in 3GPP TS 28.541 [5]. - - d) Monitor the performance of the AI/ML model based on configurations, performance indicators, and measurement reports received from the RAN. - - e) Retrain the AI/ML model and re-optimize the beam mobility configurations based on the monitored performance and/or based on a switch of the Grid-of-Beam configuration. - - f) Execute the control loop periodically or event triggered. - - g) Retrieve GoB beam pattern related information from the SMO. -- 3) E2 nodes: - - a) Collect and report to Near-RT RIC KPIs related to Grid-of-Beam configuration, handover, and beam failure statistics. - - b) Apply L3 beam mobility parameter configuration following Near-RT RIC configuration as specified in 3GPP TS 28.541 [5]. - - c) Send GoB beam pattern related information to the Near-RT RIC. - -#### 4.6.2.3 NR cell shaping optimization - -- 1) SMO: - - a. Collect the necessary configurations, performance indicators, and measurement reports data from RAN nodes triggered by Non-RT RIC as required. - - b. Configure the optimized cell shape per cell level for MIMO beam parameters and tilt via the O1 interface. - - c. Monitor the performance of all the cells to determine when to trigger for new data analytics and optimization in Non-RT RIC. -- 2) Non-RT RIC & rApp: - - a. Retrieve necessary performance, configuration, and other data for defining and updating cel shaping policy. - -- b. rApp provides the target optimal pattern settings and configuration to create an optimal cell shape characteristics to be applied to the SMO configuration, as to be applied by the RAN. - -##### 3) RAN: - -- a. Collect and report to SMO KPIs and PMs related to user activity, evolution of radio conditions, traffic load, coverage and QoS performance, per cell/beam/areas. -- b. Collect and report to SMO information and statistics about beam and resource utilization. -- c. Apply beam management strategies following SMO configuration instructions and constraints. - -### 4.6.3 Solutions - -#### 4.6.3.1 Non-RT massive MIMO GoB beam forming optimization - -The context of the massive MIMO beamforming optimization is captured in table 4.6.3.1-1. - -**Table 4.6.3.1-1: Massive MIMO GoB beam forming optimization** - -| Use Case Stage | Evolution / Specification | <> | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Goal | Enable flexible optimization of the multi-cell M-MIMO beamforming performance (capacity and coverage) by means of configuration parameter change with operator-defined objectives and allow for AI/ML-based solutions. | | -| Actors and Roles | Non-RT RIC acting as massive MIMO beamforming configuration optimization decision making function.
SMO acting as the RAN data collection and parameter configuration function.
RAN acting as configuration enforcement function. | | -| Assumptions | O1 interface connectivity is established between RAN and SMO. Network is operational. | | -| Pre-conditions | SMO has processed the collected data and Non-RT RIC has access to this data. | | -| Begins when | Operator specified trigger condition or event is detected. | | -| Step 1 (O) | If required, SMO can initiate the specific measurement data collection request towards RAN for AI/ML model training or to assess the outcome of the applied configuration. | | -| Step 2 (M) | Non-RT RIC retrieve the data from SMO components and trains the AI/ML model with the collected data from the application, the RAN nodes. Trained AI/ML models are deployed and inferenced for long-term configuration parameters optimization. | | -| Step 3 (M) | Upon trigger from Non-RT RIC with the optimized beam parameters, SMO configures the parameters towards the RAN via O1 interface. The relevant parameters can include:
  • a) horizontal beam width, vertical beam width, beam azimuth and downtilt
  • b) maximum and average transmitted power per beam/direction
| | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 4 (M) | SMO monitors the network performance. If the algorithm performance is unsatisfactory in terms of predefined objective/requirement, SMO initiates fallback mechanism to restore previous configuration. It can also gather necessary information and data to retrain and update the AI/ML model or trigger the optimization in Non-RT RIC. | | -| Ends when | Operator specified trigger condition or event is satisfied. | | -| Exceptions | None identified. | | -| Post Conditions | The RAN operates using the newly deployed parameters/models. | | - -``` - -@startuml - -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "Personnel" #lightblue - Actor "Radio \nPlanner" as RP -End box - -box "Service Management & \nOrchestration Framework" #gold - Participant "Non-RT RIC" as NonRTRIC - Participant SMO -end box - -box "O-RAN Components" #lightpink - collections "O-RAN Nodes" as ORANnodes -end box - -box "Application Framework" #lightseagreen - Participant APP -end box - -activate RP -activate APP -activate NonRTRIC - -``` - -``` -activate SMO - -activate ORANnodes - -||| - -RP -> NonRTRIC: Triggering \nCriteria - -group Data Collection - ORANnodes -> SMO : e.g. UE level Measurement report, \nUE-specific Beam ID - SMO -> NonRTRIC: Data retrieval of RAN and other data \ne.g. KPIs, Beam Pattern - Configuration Table -end - -group AI/ML Flow - NonRTRIC -> SMO: Initiate data collection - SMO -> ORANnodes: configure additional KPI/PM jobs - ORANnodes -> SMO: KPI/PM report - SMO -> NonRTRIC: Additional KPI/PM data - APP -> NonRTRIC: e.g. UE GPS info - NonRTRIC -> NonRTRIC: AI/ML model training - NonRTRIC -> NonRTRIC: AI/ML model inference -end - -group Configuration Update - NonRTRIC -> SMO: Updated M-MIMO Configuration - SMO -> ORANnodes: configure new M-MIMO parameters -end - -group Performance Monitoring - ORANnodes -> SMO: KPI/PM report - SMO -> NonRTRIC: KPI/PM data - NonRTRIC -> NonRTRIC: Performance monitoring and evaluation - NonRTRIC -> SMO: Fallback (e.g. restore configuration) - NonRTRIC -> NonRTRIC: Model retraining and update -end - -@enduml -``` - -The flow diagram of the massive MIMO beamforming optimization is given in figure 4.6.3.1-1. - -![Sequence diagram for Massive MIMO beamforming optimization. Lifelines: Personnel (Radio Planner), Service Management & Orchestration Framework (Non-RT RIC, SMO), O-RAN Components (O-RAN Nodes), and Application Framework (APP). The process includes Data Collection, AI/ML Flow, Configuration Update, and Performance Monitoring phases.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) - -``` - -sequenceDiagram - actor Radio Planner as Personnel: Radio Planner - participant Non-RT RIC as Non-RT RIC - participant SMO as SMO - participant O-RAN Nodes as O-RAN Nodes - participant APP as APP - - Note right of Non-RT RIC: Data Collection - Note right of SMO: AI/ML Flow - Note right of Non-RT RIC: Configuration Update - Note right of SMO: Performance Monitoring - - Radio Planner->>Non-RT RIC: 1 Triggering Criteria - O-RAN Nodes-->>SMO: 2 e.g. UE level Measurement report, UE-specific Beam ID - SMO-->>Non-RT RIC: 3 Data retrieval of RAN and other data e.g. KPIs, Beam Pattern Configuration Table - Non-RT RIC->>SMO: 4 Initiate data collection - SMO->>O-RAN Nodes: 5 configure additional KPI/PM jobs - O-RAN Nodes-->>SMO: 6 KPI/PM report - SMO-->>Non-RT RIC: 7 Additional KPI/PM data - SMO-->>Non-RT RIC: 8 e.g. UE GPS info - Non-RT RIC->>Non-RT RIC: 9 AI/ML model training - Non-RT RIC->>Non-RT RIC: 10 AI/ML model inference - Non-RT RIC->>SMO: 11 Updated M-MIMO Configuration - SMO->>O-RAN Nodes: 12 configure new M-MIMO parameters - O-RAN Nodes-->>SMO: 13 KPI/PM report - SMO-->>Non-RT RIC: 14 KPI/PM data - Non-RT RIC->>Non-RT RIC: 15 Performance monitoring and evaluation - Non-RT RIC->>SMO: 16 Fallback (e.g. restore configuration) - Non-RT RIC->>Non-RT RIC: 17 Model retraining and update - -``` - -Sequence diagram for Massive MIMO beamforming optimization. Lifelines: Personnel (Radio Planner), Service Management & Orchestration Framework (Non-RT RIC, SMO), O-RAN Components (O-RAN Nodes), and Application Framework (APP). The process includes Data Collection, AI/ML Flow, Configuration Update, and Performance Monitoring phases. - -Figure 4.6.3.1-1: Massive MIMO beamforming optimization flow diagram - -#### 4.6.3.2 Near-RT massive MIMO beam-based mobility robustness optimization - -The context of the massive MIMO beam-based mobility robustness optimization is captured in table 4.6.3.2-1. - -**Table 4.6.3.2-1: Beam-based mobility robustness optimization** - -| Use Case Stage | Evolution / Specification | <> | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Goal | Enable flexible optimization of the beam-based mobility robustness optimization by means of configuration parameter change with operator-defined objectives and allow for AI/ML-based solutions. | | -| Actors and Roles | Near-RT RIC acting as bMRO function, data collection function, and AI/ML model training function.
E2 nodes acting as configuration enforcement function. | | -| Assumptions | E2 connectivity is established between Near-RT RIC and E2 nodes. O1 connectivity is established between Near-RT RIC and SMO. Network is operational. | | -| Pre-conditions | Active Grid-of-Beams beam pattern is defined. | | -| Begins when | Operator specified trigger condition is set or event is detected or periodically. | | -| Step 1 (M) | Near-RT RIC collects necessary data from E2 nodes and related GoB beam pattern Information and trains the AI/ML model with the collected data. | | -| Step 2 (M) | Trained AI/ML models are executed in Near-RT RIC and infer for configuration parameter optimization based on the operator target. | | -| Step 3 (M) | Continuously or upon trigger (e.g., change in the mMIMO beam pattern configuration, manual trigger etc.), Near-RT RIC configures optimized parameters in E2 nodes (e.g., bCIO-s). | | -| Step 4 (M) | Near-RT RIC monitors the network performance. If the algorithm performance is unsatisfactory in terms of predefined objective/requirement, Near-RT RIC initiates fallback mechanism to restore previous/default configuration. It can also gather necessary information and data to retrain and update the AI/ML model or trigger the optimization. | | -| Ends when | Operator specified trigger condition or event is satisfied. | | -| Exceptions | None identified. | | -| Post Conditions | The E2 Nodes operate using the newly deployed parameters. | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "SMO" #gold - Participant SMO as "Operator/SMO" -end box - -``` - -``` -Box "O-RAN" #lightpink - Participant NearRTRIC as "Near-RT RIC" - Participant ORANnodes as "E2 Nodes" -End box - -group Data Collection - ORANnodes -> NearRTRIC : <> KPI/PM report - Hnote over NearRTRIC - GoB Beam Pattern Information is available - Endhnote -end - -group AI/ML Flow - ORANnodes -> NearRTRIC: <> KPI/PM report - Hnote over NearRTRIC - GoB Beam Pattern Information is available - Endhnote - NearRTRIC -> NearRTRIC: AI/ML model training - NearRTRIC -> NearRTRIC: AI/ML model inference -end - -group Configuration Update - group alt 1 - Hnote over NearRTRIC - GoB Beam Pattern Change - Endhnote - end - group alt 2 - SMO -> NearRTRIC: <> Optimization Trigger:\nNew optimization target - end - group alt 3 - NearRTRIC -> NearRTRIC: Optimization Trigger:\nPerformance degradation - end - NearRTRIC -> ORANnodes: <> Configure new mobility parameters -end -``` - -``` -group Performance Monitoring - ORANnodes -> NearRTRIC: <> KPI/PM report - NearRTRIC -> NearRTRIC: Performance monitoring and evaluation - NearRTRIC -> NearRTRIC: Fallback configuration (O) - NearRTRIC -> NearRTRIC: Model retraining and update -end -``` - -``` -@enduml -``` - -The flow diagram of the massive MIMO beam-based mobility robustness optimization is given in figure 4.6.3.2-1. - -![Sequence diagram for Massive MIMO beam-based mobility robustness optimization. Lifelines: Operator/SMO, Near-RT RIC, E2 Nodes. Phases: Data Collection, AI/ML Flow, Configuration Update, Performance Monitoring.](255efa1d461fc79b4ed367aaec11637f_img.jpg) - -``` - -sequenceDiagram - participant Operator/SMO - participant Near-RT RIC - participant E2 Nodes - - Note right of Near-RT RIC: Data Collection - E2 Nodes->>Near-RT RIC: 1 <> KPI/PM report - Note right of Near-RT RIC: GoB Beam Pattern Information is available - - Note right of Near-RT RIC: AI/ML Flow - E2 Nodes->>Near-RT RIC: 2 <> KPI/PM report - Note right of Near-RT RIC: GoB Beam Pattern Information is available - Near-RT RIC->>Near-RT RIC: 3 AI/ML model training - Near-RT RIC->>Near-RT RIC: 4 AI/ML model inference - - Note right of Operator/SMO: Configuration Update - alt 1: GoB Beam Pattern Change - alt 2: Optimization Trigger: New optimization target - Operator/SMO->>Near-RT RIC: 5 <> Optimization Trigger: New optimization target - alt 3: Optimization Trigger: Performance degradation - Near-RT RIC->>Near-RT RIC: 6 Optimization Trigger: Performance degradation - Near-RT RIC->>E2 Nodes: 7 <> Configure new mobility parameters - - Note right of Near-RT RIC: Performance Monitoring - E2 Nodes->>Near-RT RIC: 8 <> KPI/PM report - Near-RT RIC->>Near-RT RIC: 9 Performance monitoring and evaluation - Near-RT RIC->>Near-RT RIC: 10 Fallback configuration (O) - Near-RT RIC->>Near-RT RIC: 11 Model retraining and update - -``` - -Sequence diagram for Massive MIMO beam-based mobility robustness optimization. Lifelines: Operator/SMO, Near-RT RIC, E2 Nodes. Phases: Data Collection, AI/ML Flow, Configuration Update, Performance Monitoring. - -Figure 4.6.3.2-1: Massive MIMO beam-based mobility robustness optimization flow diagram - -NOTE on **GoB Beam Pattern Information is available**, **GoB Beam Pattern Change**: - -One of the necessary inputs for training and inference of the bMRO function is the (current) GoB beam pattern (or alternative beam pattern) that is determined externally (in the SMO, in the Non-RT RIC, in the E2 nodes, or in the Near-RT RIC by another function). The relevant GoB beam pattern information shall be made available to the Near-RT RIC bMRO function both for training and inference. Depending on implementation, this can be achieved by transmission from the SMO (over O1), or by transmission from the E2 nodes (over E2), or by combined transmission from the SMO and the E2 nodes (or by communication between two Near-RT RIC functions). Moreover, depending how the relevant GoB beam pattern information is defined, the necessary information can be even transmitted separately and asynchronously (e.g., SMO transmits a list of GoB beam patterns for the next, longer time period, while the E2 nodes transmit the exact times of beam pattern change and indicate the ID of the beam pattern in the list). - -#### 4.6.3.3 NR cell shaping optimization - -The context for the cell shaping optimization use case is captured in table 4.6.3.3-1. - -**Table 4.6.3.3-1: Cell shaping optimization** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Detect optimization opportunities for cell shape optimizations and apply new configuration settings to ensure the optimization cells shapes. | | -| Actors and Roles | SMO, Non-RT RIC, O-RAN NFs, rApp | | -| Assumptions | All relevant functions and components are instantiated, and O1, R1, OFH interface connectivity is in place. | | -| Pre-conditions |

Network is operational.

SMO has processed the collected data, and Non-RT RIC has access to this data.

O1 is established between the SMO and RAN Nodes. Non-RT RIC monitors the performance by collecting the relevant performance events and counters from O-RAN nodes from SMO.

| | -| Begins when | Network is in normal operational state, providing regular PM and KPI reports. | | -| Step1 (M) | Network provides regular interval performance measurements, and in one such report there are criteria to optimize the shape of the cells. | | -| Step 2 (O) | Alternate scenario 1 – Automated intervention: Triggering for new cell shape to be applied triggered automatically based on network criteria and performance measurements. | | -| Step 3 (O) | Alternate scenario 2 – Manual Intervention: Triggering for new cell shape to be applied is triggered by manual operator / radio planning intervention. | | -| Step 4 (M) | Once criteria have been triggered field data is provided to the rApp via the Non-RT RIC to determine what new settings to set. | | -| Step 5 (M) | Applicable field inputs are provided to rApp as inputs for the optimization logic to apply. | | -| Step 6 (M) | Based on rApp logic, new configuration settings for cell shape are provided. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 7 (M) | The new settings are made available to the SMO for communication to the RAN. | | -| Step 8-12 (M) | The SMO communicates the new O1 settings to the O-DU and O-RU as driven by hybrid or hierarchical management options - via O1 and M-plane. | | -| Ends when | Operator specified or rApp trigger changes and event are satisfied. | | -| Exceptions | None identified. | | -| Post Conditions | None. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 - -autonumber - -Box "Operator Personnel" #Lightcyan - Actor planner as "Planner" -End box - -Box "SMO Framework" #gold - participant smo as "SMO" - participant non_RT_RIC - participant rApp -End box - -Box "RAN" #lightpink - participant odu as "O-DU" - participant oru as "O-RU" -End box - -== START - Triggering Optimization == - -Note over smo - -``` - -Criteria triggered for cell shaper optimization. - -Two scenarios: - -- 1 - automated based on observed network conditions -- 2 - manual, driven by radio planning - -End note - -===== Scenario 1 - Automated == - -odu -> smo: O1 - Notify SMO criteria triggered - -===== Scenario 2 - Operator intervention == - -planner -> smo: Notify SMO to apply new cell shaper settings - -===== Common flow == - -smo -> non\_RT\_RIC: Data retrieval - pms, metrics - -non\_RT\_RIC-> rApp: R1 - Criteria triggered for rApp - -== Apply rApp logic == - -Note over rApp - -Apply logic to - -re-configure - -to target cell shape - -End note - -rApp -> non\_RT\_RIC: R1 - Provide new configuration settings to RAN - -== Setup new configuration for cell shaper == - -non\_RT\_RIC-> smo: Provide new configuration settings to apply - -smo -> odu: O1 - Provide new configuration settings to ODU - -odu -> oru: OFH - Provide new configuration settings to ORU - -@enduml - -The flow diagram of the cell shaping optimization is given in figure 4.6.3.3-1. - -![Sequence diagram for cell shaping optimization flow. Lifelines: Operator Personnel (Planner), SMO Framework (SMO, non_RT_RIC, rApp), and RAN (O-DU, O-RU). The process starts with 'START - Triggering Optimization' (criteria: 1-automated based on network conditions, 2-manual driven by radio planning). It branches into 'Scenario 1 - Automated' (1 O1 - Notify SMO criteria triggered) and 'Scenario 2 - Operator intervention' (2 Notify SMO to apply new cell shaper settings). Both lead to 'Common flow' (3 Data retrieval - pms, metrics -> 4 R1 - Criteria triggered for rApp). Then 'Apply rApp logic' (Apply logic to re-configure to target cell shape -> 5 R1 - Provide new configuration settings to RAN). Finally 'Setup new configuration for cell shaper' (6 Provide new configuration settings to apply -> 7 O1 - Provide new configuration settings to ODU -> 8 OFH - Provide new configuration settings to ORU).](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) - -Sequence diagram for cell shaping optimization flow. Lifelines: Operator Personnel (Planner), SMO Framework (SMO, non\_RT\_RIC, rApp), and RAN (O-DU, O-RU). The process starts with 'START - Triggering Optimization' (criteria: 1-automated based on network conditions, 2-manual driven by radio planning). It branches into 'Scenario 1 - Automated' (1 O1 - Notify SMO criteria triggered) and 'Scenario 2 - Operator intervention' (2 Notify SMO to apply new cell shaper settings). Both lead to 'Common flow' (3 Data retrieval - pms, metrics -> 4 R1 - Criteria triggered for rApp). Then 'Apply rApp logic' (Apply logic to re-configure to target cell shape -> 5 R1 - Provide new configuration settings to RAN). Finally 'Setup new configuration for cell shaper' (6 Provide new configuration settings to apply -> 7 O1 - Provide new configuration settings to ODU -> 8 OFH - Provide new configuration settings to ORU). - -Figure 4.6.3.3-1: Cell shaping optimization flow diagram - -### 4.6.4 Required data - -#### 4.6.4.1 Non-RT massive MIMO GoB beam forming optimization - -There are different types of data that are required from different parts of the network, and the following list summarizes with some examples: - -- 1) Environment data: Cell site information (location), inter-site distance, BS system configuration, (e.g. operating frequency, bandwidth, frame structure, transmit power, default beam weight configuration); complete set of massive MIMO configurations, i.e., horizontal beamwidth adjustable range, vertical beamwidth adjustable range, azimuth angle adjustable range, elevation angle adjustable range. -- 2) From RAN to SMO and/or Near-RT RIC - - a) Measurement reports with RSRP/RSRQ/CQI/SINR per beam information for the UEs in cells of interest; the time granularity of data collection shall be configurable and satisfy the requirement of the AI/ML model. - - b) Network KPIs: e.g., cell downlink/uplink traffic load, RRC connection attempts, average RRC connected UE, maximum RRC connected UE, average active connections (downlink/uplink), DL/UL throughput, DL/UL spectral efficiency, NI (Noise Interference); beam resource usage (transmitted power per beam/directions and associated PRB usage), beam based handover and beam failure statistics -- 3) From application to SMO - - a) User location related information, e.g., GPS coordinates for the purpose of constructing/training relevant AI/ML models. - -#### 4.6.4.2 Near-RT massive MIMO beam-based mobility robustness optimization - -1) Beam-specific handover related KPMs, as specified in 3GPP TS 28.552 [6] and in 3GPP TS 28.622 [8] from E2 nodes, similar to: - -- a) Too early handovers -- b) Too late handovers -- c) Attempted handovers -- d) Successful handovers -- e) Failed handovers -- f) The time granularity is an integer multiple of 1 second as specified in 3GPP TS 28.622 [8]. - -2) The beam pattern information supplied externally is not defined in the present document. - -#### 4.6.4.3 NR cell shaping optimization - -**Table 4.6.4.3-1: Cell shaping optimization data requirements** - -| Requirement | Category | Parameters | Source | Applicable Interface | Reference | -|-------------|----------------------------------|------------------------------------------------------------------------------------------------|-----------|----------------------|---------------------------------------------------------------| -| Req-4.6.001 | Network Configuration Management | Node Id: Node identification | O-DU | O1 | 3GPP TS 28.541 [5], clause 4.3.1, gnbId + gnbDUID | -| Req-4.6.002 | Network Configuration Management | Sector Id: Sector identification | O-DU | O1 | | -| Req-4.6.003 | Network Configuration Management | Cell Id: Cell identification | O-DU | O1 | 3GPP TS 28.541 [5], clauses 4.3.1, 4.3.5, gnbId + cellLocalId | -| Req-4.6.004 | Network Configuration Management | Antenna Latitude | O-DU | O1 | | -| Req-4.6.005 | Network Configuration Management | Antenna Longitude | O-DU | O1 | | -| Req-4.6.006 | Network Configuration Management | Antenna Azimuth (direction) | O-DU | O1 | | -| Req-4.6.007 | Network Configuration Management | Antenna Elevation (Height) | O-DU | O1 | 3GPP TS 28.662 [41], clause 4.3.2 | -| Req-4.6.008 | Network Configuration Management | Antenna – Remote Electrical Tilt subunit mapping | O-DU/O-RU | O1 | | -| Req-4.6.009 | Network Configuration Management | Antenna – Remote Electrical Tilt subunit mapping | O-DU/O-RU | OFH MP | O-RAN.WG4.MP [28], clause 14.4.2 | -| Req-4.6.010 | Network Configuration Management | Remote Electrical Tilt per antenna | O-DU/O-RU | O1 | 3GPP TS 28.662 [41], clause 4.3.2, retTiltValue | -| Req-4.6.011 | Network Configuration Management | Remote Electrical Tilt per antenna | O-DU/O-RU | OFH MP | O-RAN.WG4.MP [28], clause 14.4.3 and AISG specifications | -| Req-4.6.012 | Network Configuration Management | Digital tilt per antenna | O-DU/O-RU | O1 | | -| Req-4.6.013 | Network Configuration Management | Digital tilt per antenna | O-DU/O-RU | OFH MP | O-RAN.WG4.MP [28], clause 14.4.3 and AISG specifications | -| Req-4.6.014 | Network Configuration Management | Broadcast and Cellular Broadcast (BCB) per cell level | O-DU | O1 | 3GPP TS 28.541 [5], clause 4.3.1, gnbId + gnbDUID | -| Req-4.6.015 | Network Configuration Management | Horizontal coverage width | O-DU | O1 | | -| Req-4.6.016 | Network Configuration Management | Horizontal coverage width | O-DU | OFH MP | | -| Req-4.6.017 | Network Configuration Management | Vertical coverage width | O-DU | O1 | | -| Req-4.6.018 | Network Configuration Management | Vertical coverage width | O-DU | OFH MP | | -| Req-4.6.019 | Network Configuration Management | Supported coverage combinations of vertical / horizontal options (radio specific capabilities) | O-RU | O1 | | - -| | | | | | | -|-------------|----------------------------------|------------------------------------------------------------------------------------------------|-----------|--------|--| -| Req-4.6.020 | Network Configuration Management | Supported coverage combinations of vertical / horizontal options (radio specific capabilities) | O-RU | OFH MP | | -| Req-4.6.021 | Network Configuration Management | Digital tilt per carrier | O-DU/O-RU | O1 | | -| Req-4.6.022 | Network Configuration Management | Digital tilt per carrier | O-DU/O-RU | OFH MP | | - -## 4.7 RAN sharing - -This use case provides the motivation, description, and requirements for RAN sharing use case. The goal of this use case is to enable multiple operators to share the same O-RAN infrastructure, while allowing them to remotely configure and control the shared resources via a remote O1, O2 and E2 interface. - -### 4.7.1 Background and goal of the use case - -RAN sharing is envisioned as an efficient and sustainable way to reduce the network deployment costs, while increasing network capacity and coverage. 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 sharing its RAN infrastructure and computing resources with its partner operators. - -Specifically, this use case analyzes the Multi-Operator RAN (MORAN) sharing scenario, wherein each operator utilizes a separate carrier in order to achieve more freedom and independency on the control of the radio resources. Accordingly, the goal of this use case is to propose a sharing-compliant O-RAN architecture that lets operators to configure the shared network resources independently from configuration and operating strategies of the other sharing operators. Specifically, it is proposed that a home operator (operator A) makes available its O-RAN infrastructure and computing resources to host the Virtual RAN Functions (VNF) of a second operator (operator B), allowing it to configure and control such remote VNFs via a remote O1, O2 and E2 interface. - -![Figure 4.7.1-1: MORAN use case in O-RAN. The diagram shows two sites, Site A and Site B, connected via an O1/O2 + SLA (Remote) interface. Site A (orange) contains a Service Management & Orchestration Framework with an NRT-RIC and a VNF Sharing APP. It has an nRT-RIC connected to two VNFs (VNF A and VNF B) via O1 and O1/O2 interfaces. Each VNF contains O-CU-CP, E1, and O-CU-UP components. These are connected to Shared Computing Resources, which in turn connect to O-DUs (VNF A and VNF B) via F1 interfaces. The O-DUs connect to an Open FH, which connects to a Shared O-RU via O1 and O1/O2 interfaces. Site B (blue) has a similar structure but its nRT-RIC is connected to the VNFs via O1/O2 (Remote) interfaces. Site B's VNFs also connect to Shared Computing Resources, O-DUs, Open FH, and a Shared O-RU. A legend at the bottom identifies the colors for Site Operator A (orange), Site Operator B (blue), IT Infrastructure shared in Site A (light orange), IT Infrastructure shared in Site B (light blue), Network function specific to A (dark orange), and Network function specific to B (dark blue).](3ce04f1c7128814978c6b34d654a25cc_img.jpg) - -Figure 4.7.1-1: MORAN use case in O-RAN. The diagram shows two sites, Site A and Site B, connected via an O1/O2 + SLA (Remote) interface. Site A (orange) contains a Service Management & Orchestration Framework with an NRT-RIC and a VNF Sharing APP. It has an nRT-RIC connected to two VNFs (VNF A and VNF B) via O1 and O1/O2 interfaces. Each VNF contains O-CU-CP, E1, and O-CU-UP components. These are connected to Shared Computing Resources, which in turn connect to O-DUs (VNF A and VNF B) via F1 interfaces. The O-DUs connect to an Open FH, which connects to a Shared O-RU via O1 and O1/O2 interfaces. Site B (blue) has a similar structure but its nRT-RIC is connected to the VNFs via O1/O2 (Remote) interfaces. Site B's VNFs also connect to Shared Computing Resources, O-DUs, Open FH, and a Shared O-RU. A legend at the bottom identifies the colors for Site Operator A (orange), Site Operator B (blue), IT Infrastructure shared in Site A (light orange), IT Infrastructure shared in Site B (light blue), Network function specific to A (dark orange), and Network function specific to B (dark blue). - -Figure 4.7.1-1: MORAN use case in O-RAN - -The logic architecture of the proposed MORAN use case is shown in figure 4.7.1-1. It is assumed that operator A owns the site A and shares the PHY layer (LOW) with operator B (Shared O-RU). Indeed, multiple PLMN IDs are broadcasted, while each operator operates in a different carrier. Moreover, the computing resources of the site A are shared among multiple VNFs, belonging to operator A and operator B, respectively. - -Each VNF represents a logic implementation of the O-DU and O-CU functionalities and is controlled by each partner operator in an independent manner. While operator A can directly orchestrate and configure its VNFs, operator B needs to control its VNFs in a remoted manner. The challenge here is to enable operator B to configure and control resources in an infrastructure that is owned by another operator. - -Accordingly, it is assumed that operator B can monitor and control the remote radio resources via the RIC node of site B, using an “E2 remote” interface. Note that in the proposed architecture, the RIC nodes are not shared and kept independent at the site A and B respectively. - -However, it is assumed that operator B cannot directly orchestrate its VNFs in site A, but it is allowed to communicate the desired initial VNF configuration via an extended O1, O2 interface, hereafter referred to as “O1, O2 + SLA” interface (O1, O2 remote). Note that the O1, O2 nomenclature is used hereafter to refer to both O1 and O2 messages. - -The “O1, O2 remote” interface is connected to a specific “sharing orchestration application”, referred to as “SMO-sharing App”, that is located at the Service Management & Orchestration Framework of each operator. Specifically, the “SMO-sharing App” at site A acts as an SLA (Service Level Agreement) monitoring and filter entity: it checks that O1, O2 requests coming from operator B are in line with a predefined SLA and finally configures the VNF of operator B, according to the initial O1, O2 request. - -### 4.7.2 Entities/resources involved in the use case - -- 1) SMO-sharing App (site A): - - a) SLA monitoring: checks that orchestration/management requests sent by operator B are in line with the SLA. - - b) Remote provisioning and initial VNF deployment: asks the IMF to instantiate the VNFs for operator B. - -- c) Remote management operations via “O1, O2 remote”: configures the VNF of operator B via the Orchestrator, according to “O1, O2 remote” requests sent by operator B. - - d) Forwards RAN related data, collected from the hosted VNFs, to the SMO-sharing App (site B) over the “O1, O2 remote” interface. -- 2) SMO-sharing App (site B): -- a) Detects the “SMO-sharing App” in site A towards which to forward “O1, O2 remote” requests. - - b) Sends “O1, O2 remote” commands for initial deployment and configuration of remote VNFs. - - c) Forwards RAN related data of operator B, collected in site A, to the Non-RT RIC. -- 3) IMF (site A): creates VNFs for operator B in site A on initial request of the SMO-sharing App (site A). -- 4) RAN (site A): -- a) Supports data collection from the hosted VNFs with radio state report over “E2 remote” interface. - - b) Supports data collection from hosted VNFs with UE KPI report over “O1, O2 remote” interface. -- 5) Non-RT RIC (site B): -- a) Configures the initial network policy template, e.g., default scheduling policy, of the remote VNFs. - - b) Elaborates RAN data collected by “SMO-sharing App”, e.g., scheduling performance metrics, and sends AI policy/intentions to the remote virtual O-DU/O-CU (VNF\_B) via the Near-RT RIC. -- 6) Near-RT RIC (site B): -- a) Monitors and collects E2-related parameters from the remote VNFs. - - b) Detects the “E2 remote” interface towards the VNFs hosted in site A. - -### 4.7.3 Solutions - -#### 4.7.3.1 RAN sharing - -The context of the RAN sharing use case is captured in table 4.7.3.1-1. - -**Table 4.7.3.1-1: RAN sharing use case** - -| Use Case Stage | Evolution / Specification | <> | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Goal | Enable two operators to share the same O-RAN infrastructure, while allowing them to remotely configure and control the shared resources via a remote “O1”, “O2” and “E2” interface. | | -| Actors and Roles | Sharing-SMO App handles remote orchestration operations via “O1, O2 remote” interface. Non-RT RIC (operator B): updates configuration of VNFs hosted in site A. Near-RT RIC (operator B): execute remote E2 commands via “E2 remote” interface. RAN (site A): collects and reports RAN statistics to the RIC of operator B (RIC_B) for its VNFs hosted in site A. | | -| Assumptions | All relevant functions and components are instantiated.
A1, O1, O2, E2 interface connectivity is established with local SMO, Non-RT RIC and Near-RT RIC, respectively. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| |

“O1, O2 remote” and “E2 remote” end-to-end connectivity is established with remote SMO and remote Near-RT RIC, respectively. The remote interfaces have been secured through appropriate end-to-end security mechanisms (security configuration details are out of scope of this use case).

Non-RT RIC_B and Near-RT RIC_B are aware of the presence of O-DU_B and O-CU_B in the site A. Near-RT RIC_B is aware of the “E2 remote” interface, to be used to control the remote VNFs hosted in site A.

| | -| Pre-conditions |

An SLA sharing agreement is established between the home (operator A) and host operator (operator B). The SLA defines the amount of physical resources (CPU, memory, etc.), that can be allocated to the host operator and the type of admissible orchestration operations that can be remotely executed by the host operator. Such SLA is translated in appropriate SLA monitoring-check controls to be executed by the SMO-sharing App.

| | -| Begins when |

Phase 1-2: Host operator (operator B) asks to provision and instantiate an O-DU_B and O-CU_B in the site of the home operator (operator A).

Phase 3: Host operator wants to send a new instruction to the shared RAN over the “E2 remote” interface.

| | -| Step 1 (M) |

SMO-sharing App_B sends a request to SMO-sharing App_A for provisioning and deploying a remote virtual O-DU_B and O-CU_B in the site A.

| | -| Step 2 (M) |

SMO-sharing App_A checks that the request is in line with the predefined SLA and ask the IMF (via the Orchestrator) to instantiate the VNFs for the O-CU_B and O-DU_B.

| | -| Step 3 (O) |

IMF creates VNF for operator B in site A as for the request of the SMO-sharing App_A.

| | -| Step 4 (M) |

SMO-sharing App_B notifies SMO-sharing App_A the request to install a default network policy template, e.g., RB scheduling policy, in the remote VNFs.

| | -| Step 5 (M) |

SMO-sharing App_A checks that operator B request is in line with the SLA and configures (via the Orchestrator) the O-DU_B/ O-CU_B via an O1 configuration command.

| | -| Step 6 (M) |

RAN related data from VNF_B in site A are collected at SMO Collector and forwarded to the SMO-sharing App_A, which in turns forwards them to the Non-RT RIC_B, via the SMO-sharing App_B.

| | -| Step 7 |

Non-RT RIC_B decides to update the default network policy of the remote VNFs, e.g., scheduling policy of O-DU_B/O-CU_B and sends an A1 update policy request to the Near-RT RIC_B.

| | -| Step 8 |

Near-RT RIC_B configures the remote O-DU_B/O-CU_B accordingly, over the “E2 remote” interface.

| | -| Ends when |

The VNFs of operator B in site A are instantiated with success and no update-requests are sent by the host operator (operator B).

| | -| Exceptions |

None identified.

| | -| Post Conditions |

RIC of operator B monitors relevant radio KPI from the remote O-CU_B and O-DU_B and decides to reconfigure the scheduling policy as for Step 7.

| | - -``` -@startuml -``` - -``` -skinparam ParticipantPadding 5 -``` - -``` -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber - -Box "O-RAN (Site A)" #lightpink - Participant OCU as "O-CU_B" <<(Z,lime) VNF>> - Participant ODU as "O-DU_B" <<(Z,lime) VNF>> -End box - -Box "Cloud Platform \nInfrastructure" #lightseagreen - participant IMF -End box - -Box "Service Management and Orchestration \n(Site A)" #gold - Boundary Collector - Participant SMO_a as "Orchestration_A" - Participant smos_a as "SMO-Sharing_APP_A" -end box - -Box "Service Management and Orchestration\n(Site B)" #gold - Participant smos_b as "SMO-Sharing_APP_B" - Participant SMO_b as "Orchestration_B" - Participant NON_b as "Non-RT RIC_B" -end box - -Box "O-RAN (Site B)" #lightpink - Participant RIC as "Near-RT RIC_B" -End box - -== STARTUP == -Hnote over smos_a,smos_b -Assuming "O1/O2 remote" interface -established between SMO-Sharing_APP_A -and SMO-Sharing_APP_B -endnote -``` - -``` - -smos_b -> smos_a: VNF_B_initial \n provisioning request \n over "O1/O2 remote" \n (O2 -command) - -smos_a -> smos_a: Provisioning Admission \n Control Verification -smos_a -> SMO_a: <> \n VNF_B instantiation \n request -SMO_a -> IMF: Instantiate VNF_B \n over O2 -IMF -> OCU **: Create O-CU_B \n over O2 -IMF -> ODU **: Create O-DU_B \n over O2 -IMF -> SMO_a: Notify \nVNF_B instantiated -SMO_a -> smos_a: <>\nForward notification \nVNF_B instantiated -smos_a -> smos_b: Forward notification \nVNF_B instantiated \n over "O1/O2 remote" -smos_b -> SMO_b: Notify VNF_B \n instantiated \n in site A - -``` - -##### == CONFIGURATION == - -``` - -SMO_b -> smos_b: Initial Remote \n VNF configuration \n request -smos_b -> smos_a: VNF_B configuration request \nover "O1/O2 remote" \n(O1 -command)\n(binary code, \n MAC Scheduler template...) - -smos_a -> smos_a: Conversion of Conf. Request \nin local O1 command -smos_a -> SMO_a: << SMO Internal >> \nConfigure VNF_B -SMO_a -> OCU: Configure O-CU_B \nover O1 -SMO_a -> ODU: Configure O-DU_B \nover O1 - -``` - -Hnote over RIC,OCU - -Assuming "E2 remote" interface established between near RT-RIC and remote O-CU and O-DU -endrnote - -##### == RUNNING == - -``` - -RIC -> OCU:<> Subscription over "E2 remote" -RIC -> ODU:<> Subscription over "E2 remote" -ODU-> RIC : <> Report over "E2 remote" -OCU-> RIC : <> Report over "E2 remote" -ODU-> Collector : <> SMO data collection -OCU-> Collector : <> SMO data collection -Collector -> smos_a: << SMO Internal >> \nForward VNF_B RAN data -smos_a -> smos_b: Forward VNF_B RAN data\n over "O1/O2 remote" -smos_b -> NON_b: << SMO Internal >> \n Forward VNF_B RAN data -NON_b -> NON_b: Evaluate VNF_B RAN \n performance - -``` - -``` -Alt if need to update VNF_B network policy - NON_b -> RIC: Scheduling_update \npolicy/intent message \n over A1 - RIC -> RIC : "E2 remote" \nInterface\n detection - RIC -> OCU: Update configuration command over "E2 remote" - RIC -> ODU: Update configuration command over "E2 remote" -end - -@enduml -``` - -The flow diagram of the VNF configuration procedure for VNF\_B hosted in site A is given in figure 4.7.3.1-1. - -![Sequence diagram showing the VNF configuration procedure for VNF_B hosted in site A. The diagram is divided into three phases: STARTUP, CONFIGURATION, and RUNNING. Lifelines include O-RAN (Site A), Cloud Platform Infrastructure (IMF), Service Management and Orchestration (Site A) with Collector, Orchestration_A, and SMO-Sharing_APP_A, Service Management and Orchestration (Site B) with SMO-Sharing_APP_B, Orchestration_B, and Non-RT RIC_B, and O-RAN (Site B) with Near-RT RIC_B. The process involves VNF_B instantiation, configuration over O1 and O2 interfaces, and performance monitoring over the E2 interface.](c3254408eadbf152632a8faf16310722_img.jpg) - -The sequence diagram illustrates the VNF configuration procedure for VNF\_B hosted in site A. It is organized into three main phases: STARTUP, CONFIGURATION, and RUNNING. - -- STARTUP Phase:** - - Assuming 'O1/O2 remote' interface established between SMO-Sharing\_APP\_A and SMO-Sharing\_APP\_B. - - VNF\_B initial provisioning request over 'O1/O2 remote' (O2 command) from SMO-Sharing\_APP\_A to SMO-Sharing\_APP\_B. - - Provisioning Admission Control Verification from SMO-Sharing\_APP\_B to SMO-Sharing\_APP\_A. - - <> 3 VNF\_B instantiation request from SMO-Sharing\_APP\_A to Orchestration\_A. - - Instantiate VNF\_B over O2 from Orchestration\_A to IMF. - - 5 +VNF+ O-CU\_B over O2 from O-RAN (Site A) to IMF. - - 6 +VNF+ O-DU\_B over O2 from O-RAN (Site A) to IMF. - - Notify VNF\_B instantiated from IMF to Orchestration\_A. - - <> 8 Forward notification VNF\_B instantiated from Orchestration\_A to SMO-Sharing\_APP\_A. - - Forward notification 9 VNF\_B instantiated over 'O1/O2 remote' from SMO-Sharing\_APP\_A to SMO-Sharing\_APP\_B. - - Notify VNF\_B instantiated in site A from SMO-Sharing\_APP\_B to Orchestration\_B. -- CONFIGURATION Phase:** - - Initial Remote 11 VNF configuration request from Orchestration\_B to SMO-Sharing\_APP\_B. - - VNF\_B configuration request over 'O1/O2 remote' 12 (O1 command) (binary code, MAC Scheduler template...) from SMO-Sharing\_APP\_B to SMO-Sharing\_APP\_A. - - Conversion of Conf. Request in local O1 command from SMO-Sharing\_APP\_A to Orchestration\_A. - - 14 << SMO internal >> Configure VNF\_B from Orchestration\_A to IMF. - - 15 Configure O-CU\_B over O1 from IMF to O-RAN (Site A). - - 16 Configure O-DU\_B over O1 from IMF to O-RAN (Site A). -- RUNNING Phase:** - - Assuming 'E2 remote' interface established between near-RT RIC and remote O-CU and O-DU. - - 17 <> Subscription over 'E2 remote' from O-RAN (Site A) to IMF. - - 18 <> Subscription over 'E2 remote' from O-RAN (Site A) to IMF. - - 19 <> Report over 'E2 remote' from IMF to O-RAN (Site A). - - 20 <> Report over 'E2 remote' from IMF to O-RAN (Site A). - - 21 <> SMO data collection from IMF to Orchestration\_A. - - 22 <> SMO data collection from IMF to Orchestration\_A. - - 23 << SMO internal >> Forward VNF\_B RAN data from Orchestration\_A to SMO-Sharing\_APP\_A. - - 24 Forward VNF\_B RAN data over 'O1/O2 remote' from SMO-Sharing\_APP\_A to SMO-Sharing\_APP\_B. - - 25 << SMO internal >> Forward VNF\_B RAN data from SMO-Sharing\_APP\_B to Orchestration\_B. - - 26 Evaluate VNF\_B RAN performance from Orchestration\_B to SMO-Sharing\_APP\_B. - - alt (If need to update VNF\_B network policy): - - Scheduling update 27 policy/intent message over A1 from SMO-Sharing\_APP\_B to Near-RT RIC\_B. - - 'E2 remote' 28 Interface detection from Near-RT RIC\_B to IMF. - - 29 Update configuration command over 'E2 remote' from IMF to O-RAN (Site A). - - 30 Update configuration command over 'E2 remote' from IMF to O-RAN (Site A). - -Sequence diagram showing the VNF configuration procedure for VNF\_B hosted in site A. The diagram is divided into three phases: STARTUP, CONFIGURATION, and RUNNING. Lifelines include O-RAN (Site A), Cloud Platform Infrastructure (IMF), Service Management and Orchestration (Site A) with Collector, Orchestration\_A, and SMO-Sharing\_APP\_A, Service Management and Orchestration (Site B) with SMO-Sharing\_APP\_B, Orchestration\_B, and Non-RT RIC\_B, and O-RAN (Site B) with Near-RT RIC\_B. The process involves VNF\_B instantiation, configuration over O1 and O2 interfaces, and performance monitoring over the E2 interface. - -Figure 4.7.3.1-1: VNF configuration procedure for VNF\_B hosted in site A - -### 4.7.4 Required data - -Multi-dimensional data are expected to be handled by the SMO-sharing App: - -- 1) SLA data needs to be converted in a set of condition steps to be matched for each request of the host operator (operator B). -- 2) SMO needs to handle O1, O2 messages sent by the host operator, converting them in local O1, O2 commands. - -The RAN of the home operator needs to report to the RIC\_B the network state of the served UEs that belong to the host operator. - -## 4.8 QoS based resource optimization - -This use case provides the background and motivation for the O-RAN architecture to support RAN QoS based resource optimization. Moreover, some high-level description and requirements over Non-RT RIC and A1 interfaces are introduced. - -### 4.8.1 Background and goal of the use case - -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. - -Take an emergency service as an example of a slice tenant. 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. - -### 4.8.2 Entities/resources involved in the use case - -- 1) Non-RT RIC: - - a) Monitor necessary QoS related metrics from network function and other SMO functions. - -- b) Send policies to Near-RT RIC to drive QoS based resource optimization at RAN level in terms of expected behavior. -- 2) Near-RT RIC: - - a) Support interpretation and execution of A1 policies for QoS based resource 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 E2, which are expected to influence RRM behavior. - -### 4.8.3 Solutions - -#### 4.8.3.1 QoS based resource optimization - -The context of the QoS based resource optimization is captured in table 4.8.3.1-1. - -**Table 4.8.3.1-1: QoS based resource optimization** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Drive QoS based resource optimization in RAN in accordance with defined policies and configuration. | | -| Actors and Roles | Non-RT RIC: Creates A1 policies.
Near-RT RIC: Enforces A1 policies.
RAN: Policy enforcement.
SMO: Termination point for O1 interface. | | -| Assumptions | All relevant functions and components are instantiated and configured according wanted default behavior.
A1 interface connectivity is established with Non-RT RIC.
O1 interface connectivity is established with SMO.
The default configuration will handle most situations. | | -| Pre-conditions | Network is operational with default configuration.
SMO has established the data collection and sharing process, and Non-RT RIC has access to this data.
Non-RT RIC analyzes the data from RAN to understand the current resource consumption. | | -| Begins when | Non-RT RIC observes that resources are close to congestion in a certain area. | | -| Step 1 (O) | If needed, Non-RT RIC orders additional RAN observability, SMO configures additional observability over O1. | | -| Step 2 | Non-RT RIC evaluates RAN resource utilization for all users in a slice in specific area. | | -| Step 3 | Non-RT RIC asks for additional information from additional SMO functionality, e.g. e2e slice assurance function. | | -| Step 4 | Non-RT RIC determines dynamic group of users for which QoS target shall be changed. | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 5 | Non-RT issues A1 policy/policies with QoS target based on information from other SMO functionality. | | -| Ends when | Non-RT RIC (through O1 observability) understands that situation of resource constraints within the slice is resolved, and the deployed policies are deleted over A1. | | -| Exceptions | None identified. | | -| Post Conditions | | | - -``` - -@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 - -Box "External enrichment server" #lightcyan - Entity sliceuserdata as "Slice user data" -End box - -ran -> smo : <> Data collection -non-> non: Evaluation of resource consumption -non-> non: Indication of approaching congestion in certain area - -group O1 configuration - non -> smo: Request additional measurements - smo -> ran: <> PM measurement configuration - ran -> smo : <> Data collection - smo -> non : Additional data retrieval - -``` - -``` -end - -non -> non: Detailed evaluation of situation -non -> smo: Request additional info on priorities -smo -> sliceuserdata: Request Non-RAN info on priorities -sliceuserdata -> smo: Non-RAN information on priorities -smo-> non: Additional information on priorities - -group A1 Policies - non -> near : <> QoS based resource optimization policy create message - near -> ran : <> QoS based resource optimization enforcement -end - -ran -> smo: <> Data collection (incl specific data) -smo -> non: Data retrieval of RAN and non-RAN data -non -> non: Detailed evaluation of congestion situation to understand the effect of policy -non -> non: Evaluation of congestion situation to understand when gone - -group A1 policies - non -> near: <> QoS target policy delete message -end - -@enduml -``` - -The flow diagram of the QoS based resource optimization is given in figure 4.8.3.1-1. - -![Sequence diagram for QoS based resource optimization flow. Lifelines: Service Management and Orchestration (Collection & Control, Non-RT RIC), O-RAN (Near-RT RIC, E2 Nodes), External enrichment server (Slice user data). The sequence shows data collection, resource consumption evaluation, congestion indication, configuration requests, policy creation, and policy enforcement steps.](8ab30dbff406204a68c59ae7c1b77413_img.jpg) - -``` - -sequenceDiagram - participant SMO as Service Management and Orchestration - subgraph SMO - direction TB - CC[Collection & Control] - NRT[Non-RT RIC] - end - subgraph ORAN [O-RAN] - direction TB - NRT2[Near-RT RIC] - EN[E2 Nodes] - end - participant EES as External enrichment server - subgraph EES - direction TB - SUD[Slice user data] - end - - Note left of SMO: 1 <> Data collection - NRT->>CC: 2 Evaluation of resource consumption - CC->>NRT: 3 Indication of approaching congestion in certain area - - Note left of SMO: 01 configuration - NRT->>EN: 4 Request additional measurements - EN->>NRT: 5 <> PM measurement configuration - NRT->>EN: 6 <> Data collection - EN->>NRT: 7 Additional data retrieval - - Note left of SMO: 8 Detailed evaluation of situation - NRT->>CC: 9 Request additional info on priorities - NRT->>EES: 10 Request Non-RAN info on priorities - EES->>NRT: 11 Non-RAN information on priorities - NRT->>CC: 12 Additional information on priorities - - Note left of SMO: A1 Policies - NRT->>EN: 13 <> QoS based resource optimization policy create message - EN->>NRT: 14 <> QoS based resource optimization enforcement - - Note left of SMO: 15 <> Data collection (incl. specific data) - NRT->>CC: 16 Data retrieval of RAN and non-RAN data - NRT->>EN: 17 Detailed evaluation of congestion situation to understand the effect of policy - EN->>NRT: 18 Evaluation of congestion situation to understand when gone - - Note left of SMO: A1 policies - NRT->>EN: 19 <> QoS target policy delete message - -``` - -Sequence diagram for QoS based resource optimization flow. Lifelines: Service Management and Orchestration (Collection & Control, Non-RT RIC), O-RAN (Near-RT RIC, E2 Nodes), External enrichment server (Slice user data). The sequence shows data collection, resource consumption evaluation, congestion indication, configuration requests, policy creation, and policy enforcement steps. - -Figure 4.8.3.1-1: QoS based resource optimization flow diagram - -### 4.8.4 Required data - -For this use case, different kind of observability need to be reported to Non-RT RIC. First Non-RT RIC shall monitor resource consumption in the area. As long as resource consumption is low, the RAN scheduler will be able to give all users in an area the needed resources. When resource consumption in an area increases above a threshold, the risk of that the default configuration of RAN will not be enough to fulfil the requirements. At this point, the Non-RT RIC need to be able to configure more detailed reporting for individual UEs that the Non-RT RIC is interested in. This detailed observability shall provide the Non-RT RIC better insight in performance for specific users and therefore includes observability of e.g., user throughput and delay. With this more detailed observability, the Non-RT RIC can understand when pre-configured priorities are not enough for the scheduler to solve the problem and when additional (non-RAN) information to solve the prioritization is needed. - -## 4.9 RAN slice SLA assurance - -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 as specified in 3GPP TS 23.501 [2]. 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 shall be met at any slice subnet during the life-time of a network slice as specified in 3GPP TS 28.530 [4], especially in RAN side. Exemplary slice performance requirements are specified in terms of throughput, energy efficiency, latency, and reliability at a high level in SDOs such as 3GPP TS 22.261 [1] and GSMA NG.116 [17]. 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 as specified in 3GPP TS 28.552 [6] and information model definitions as specified in 3GPP TS 28.541 [5] 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.1 Background and goal of the use case - -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.2 Entities/resources involved in the use case - -- 1) Non-RT RIC: - - a) Retrieve RAN slice SLA target from respective entities such as SMO, NSSMF - - b) Long term monitoring of RAN slice performance measurements - - c) Training of potential AI/ML models that will be deployed in Non-RT RIC for slow loop optimization and/or Near-RT RIC for fast loop optimization - - d) Support deployment and update of AI/ML models into Near-RT RIC - - e) Receive slice control/slice SLA assurance rApps from SMO - - f) Create A1 policies based on RAN intent A1 feedback - - g) Retrieve UE specific performance reports - - h) Send A1 policies and enrichment information to Near-RT RIC to drive slice assurance - - i) Send O1 reconfiguration requests to SMO for slow-loop slice assurance -- 2) Near-RT RIC: - - a) Near real-time monitoring of slice specific RAN performance measurements - - b) Support deployment and execution of the AI/ML models from Non-RT RIC - - c) Receive slice SLA assurance xApps from SMO - - d) Send UE specific performance reports to SMO/Non-RT RIC - - e) Support interpretation and execution of policies from Non-RT RIC - - f) Perform optimized RAN (E2) actions to achieve RAN slice requirements based on O1 configuration, A1 policy, and E2 reports -- 3) E2 nodes: - - a) Support slice assurance actions such as slice-aware resource allocation, prioritization, etc. - - b) Support slice specific performance measurements through O1 - - c) Support slice specific performance reports through E2 - -### 4.9.3 Solutions - -#### 4.9.3.1 Creation and deployment of RAN slice SLA assurance models and control apps - -The context of the creation and deployment of RAN slice SLA assurance models and control apps is captured in table 4.9.3.1-1. - -**Table 4.9.3.1-1: Creation and deployment of RAN slice SLA assurance models and control apps** - -| Use Case Stage | Evolution / Specification | <> | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------| -| | | Related use | -| Goal | Training and distribution of the model, or distribution of control apps. | | -| Actors and Roles | Non-RT RIC, Near-RT RIC, SMO | | -| Assumptions | All relevant functions and components are instantiated.
A1, O1 interface connectivity is established. | | -| Pre-conditions | Near-RT RIC and Non-RT RIC are instantiated with A1 interface and connectivity has been established between them.
O1 interface has been established between SMO and Near-RT RIC. | | -| Begins when | A RAN slice is activated. | | -| Step 1 (M) | Non-RT RIC retrieves a RAN slice SLA from SMO (NSSMF). | | -| Step 2a | Non-RT RIC starts to collect performance measurements (PMs) via O1. Examples of the PMs are CSI, PRB usage, L2 throughput, RAN latency, etc. Applicable PMs are specified in 3GPP TS 28.552 [6]. | Step 2 and 3 are mandatory in case of using the AI/ML model | -| Step 2b (O) | Non-RT RIC starts to collect Enrichment Information (EIs) from external applications. Examples of the external applications are public safety application triggering slice priority during an emergency event, or location-based enrichment information, etc. | | -| Step 2c | Non-RT RIC analyzes collected PMs and/or EIs for long term monitoring, such as during the day or over the weekend. | | -| Step 3 | Non-RT RIC does the model training using the collected data in step 2 and obtains RAN slice SLA assurance models. | | -| Step 4a | In case of using the AI/ML model, Non-RT RIC deploys the trained model internally for slow loop optimization and/or distributes it to the Near-RT RIC via O2 for fast loop optimization. | Step 4a or 4b is mandatory | -| Step 4b | In case of using the control app, the control app is deployed by SMO to Non-RT RIC for slow loop optimization and/or Near-RT RIC via O2 for fast loop optimization. | | -| Step 5 (M) | Non-RT RIC receives feedback internally or from Near-RT RIC via A1 to update the model or control apps based on it. | | -| Ends when | A RAN slice is deactivated. | | -| Exceptions | None identified. | | -| Post Conditions | None identified. | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -``` - -``` -Box "Service Management and Orchestration" #gold - Participant SMO as "SMO Functions" - Boundary Collector - Participant NON as "Non-RT RIC" -end box - -Box "O-RAN" #lightpink - Participant RIC as "Near-RT RIC" - Participant E2NODES as "E2 Nodes" -End box - -Box "External" #lightcyan - Participant APP as "App" -End box - -SMO-> NON : RAN Slice SLA Retrieval -E2NODES-> Collector : <> Data Collection -RIC-> Collector : <> Data Collection - -group opt - APP-> Collector : Enrichment information collection -end - -Collector-> NON : Retrieval of RAN and non-RAN data - -group opt - NON-> NON : Training of AI/ML models -end - -NON-> NON : Deploy internal app -NON-> RIC : <> Deploy xApp -Collector-> NON : Retrieval of RAN and non-RAN data -NON-> NON : Performance monitoring & evaluation - -group opt -``` - -``` - -NON-> NON : Model re-training / update -NON-> RIC : <> Update xApp -end - -@enduml - -``` - -The flow diagram of the creation and deployment of RAN slice SLA assurance models and control apps is given in figure 4.9.3.1-1. - -![Sequence diagram showing the creation and deployment of RAN slice SLA assurance models and control apps. Lifelines include SMO Functions, Collector, Non-RT RIC, Near-RT RIC, E2 Nodes, and App. The process involves SLA retrieval, data collection, enrichment, model training, and deployment of internal apps and xApps.](f97535cdaa4fe017f4659512f4f78028_img.jpg) - -``` - -sequenceDiagram - participant SMO as SMO Functions - participant C as Collector - participant NRT as Non-RT RIC - participant NRR as Near-RT RIC - participant EN as E2 Nodes - participant App as App - - Note left of SMO: Service Management and Orchestration - Note right of EN: O-RAN - Note right of App: External - - SMO->>NRT: 1 RAN Slice SLA Retrieval - NRT->>C: 2 <> Data Collection - C->>NRT: 3 <> Data Collection - opt Enrichment information collection - C->>App: 4 Enrichment information collection - end - NRT->>C: 5 Retrieval of RAN and non-RAN data - opt Training of AI/ML models - NRT->>NRT: 6 Training of AI/ML models - end - NRT->>C: 7 Deploy internal app - NRT->>NRR: 8 <> Deploy xApp - NRT->>C: 9 Retrieval of RAN and non-RAN data - NRT->>NRT: 10 Performance monitoring & evaluation - opt Model re-training / update - NRT->>NRT: 11 Model re-training / update - NRT->>NRR: 12 <> Update xApp - end - -``` - -Sequence diagram showing the creation and deployment of RAN slice SLA assurance models and control apps. Lifelines include SMO Functions, Collector, Non-RT RIC, Near-RT RIC, E2 Nodes, and App. The process involves SLA retrieval, data collection, enrichment, model training, and deployment of internal apps and xApps. - -Figure 4.9.3.1-1: Creation and deployment of RAN slice SLA assurance models and control apps flow diagram - -#### 4.9.3.2 Slow loop RAN slice SLA optimization - -The context of the slow loop RAN slice SLA optimization is captured in table 4.9.3.2-1. - -**Table 4.9.3.2-1: Slow loop RAN slice SLA optimization** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------| -| Goal | Slow loop RAN slice SLA optimization | | -| Actors and Roles | Non-RT RIC, Near-RT RIC, SMO, RAN | | -| Assumptions | All relevant functions and components are instantiated.
A1, O1, E2 interface connectivity is established. | | -| Pre-conditions | Near-RT RIC and Non-RT RIC are instantiated with A1 interface connectivity being established between them.
O1 interfaces are established between SMO and Near-RT RIC, and SMO and RAN nodes.
RAN slice SLA assurance models or control apps have been deployed in Non-RT RIC and Near-RT RIC respectively. | | -| Begins when | A RAN slice is activated. | | -| Step 1a | Non-RT RIC decides that RAN shall be reconfigured based on long term trends collected via O1 using PMs and/or EIs.
Examples of the PMs are layer 2 throughput, PRB usage, CSI, RAN latency. | Config update step 1a or 1b is mandatory | -| Step 1b | Non-RT RIC decides to create slice specific A1 policies based on RAN slice SLA requirements and/or operator-defined RAN intents, A1 feedback from Near-RT RIC, EI from external app server and O1 based long term trends.
The policies include scope identifiers (e.g., S-NSSAI, flow ID, cell ID) and/or policy statements (e.g. slice specific KPI targets). | Policy update | -| Step 2a | The model or control app in Non-RT RIC requests SMO to update slice configuration of Near-RT RIC and/or RAN nodes through O1. | Config request | -| Step 2b | SMO sends the updated slice configuration to Near-RT RIC and/or RAN nodes via O1. Examples of the slice configuration are the number of allocated PRBs, number of flows, slice priorities. | Config delivery step 2b or 2c is mandatory | -| Step 2c | Non-RT RIC sends the updated A1 policies to Near-RT RIC. | Policy delivery | -| Step 3a | Near-RT RIC and RAN nodes process and execute the updated slice configuration. | Config execution step 3a or 3b is mandatory | -| Step 3b | Near-RT RIC receives the updated A1 policy, controls RAN nodes based on the A1 policy and sends the feedback to Non-RT RIC via A1. | Policy execution | -| Ends when | A RAN slice is deactivated. | | -| Exceptions | None identified. | | -| Post Conditions | None identified. | | - -``` -@startuml -``` - -``` -skinparam ParticipantPadding 5 -``` - -``` -skinparam BoxPadding 10 - -skinparam defaultFontSize 12 - -Autonumber - -Box "Service Management and Orchestration" #gold - Participant SMO as "SMO Functions" - Boundary Collector - Participant NON as "Non-RT RIC" -end box - -Box "O-RAN" #lightpink - Participant RIC as "Near-RT RIC" - Participant E2NODES as "E2 Nodes" -End box - -Box "External" #lightcyan - Participant APP as "App" -End box - -SMO-> NON : RAN Slice SLA Retrieval -SMO-> NON : Slice specific O1 configuration data of Near-RT RIC and E2 Nodes -E2NODES-> Collector : <> Data Collection -RIC-> Collector : <> Data Collection - -group Opt: Enrichment information collection - APP-> Collector : Enrichment information collection -end - -Collector-> NON : Retrieval of RAN and non-RAN data - -NON-> NON : Performance monitoring and evaluation -NON-> NON : Trigger for RAN slice SLA assurance - -group Opt: Additional data collection - NON-> Collector : Request additional measurements - Collector-> E2NODES : <> PM measurement configuration -``` - -``` - -E2NODES-> Collector : <> Data Collection - -Collector-> NON : Retrieval of RAN data - -end - -NON-> NON : Decision for RAN slice SLA assurance - -group Alt 1: O1 Configuration update - NON-> NON : Creation of slice specific configuration - NON-> SMO : Request for slice specific RAN configuration update - SMO-> RIC : <> Configuration update - SMO-> E2NODES : <> Configuration update -end - -group Alt 2: A1 Policy generation - NON-> NON : RAN slice SLA assurance policy generation - NON-> RIC : <> RAN slice SLA assurance policy creation - RIC-> RIC : E2 policy generation - RIC-> E2NODES : <> RAN slice SLA assurance enforcement - E2NODES-> RIC : <> Data collection - RIC-> NON : <> RAN slice SLA assurance policy feedback -end - -E2NODES-> Collector : <> Data Collection -Collector-> NON : Retrieval of RAN and non-RAN data -NON-> NON : Performance monitoring and evaluation - -group Opt: A1 Policy removal - NON-> NON : Decision to remove RAN slice SLA policy - NON-> RIC : <> RAN slice SLA assurance policy removal -End - -@enduml - -``` - -The flow diagram of the slow loop RAN slice SLA optimization is given in figure 4.9.3.2-1. - -![Sequence diagram for Slow loop RAN slice SLA optimization flow. Lifelines: SMO Functions, Collector, Non-RT RIC (SMO), Non-RT RIC (O-RAN), E2 Nodes, App. The process involves SLA retrieval, configuration data exchange, optional enrichment and additional data collection, decision making, configuration updates, policy generation, enforcement, and optional policy removal.](d510bddda14c44163bbeee33b491a105_img.jpg) - -``` - -sequenceDiagram - participant SMO Functions - participant Collector - participant Non-RT RIC_SMO as Non-RT RIC (SMO) - participant Non-RT RIC_O as Non-RT RIC (O-RAN) - participant E2 Nodes - participant App - - Note left of SMO: Service Management and Orchestration - Note right of E2: O-RAN - Note right of App: External - - SMO Functions->>Non-RT RIC_SMO: 1 RAN Slice SLA Retrieval - Non-RT RIC_SMO-->>SMO Functions: 2 Slice specific O1 configuration data of Near-RT RIC and E2 Nodes - Non-RT RIC_SMO->>Collector: 3 <> Data Collection - Non-RT RIC_SMO->>Collector: 4 <> Data Collection - - opt Enrichment information collection - Non-RT RIC_SMO->>Collector: 5 Enrichment information collection - end - - Non-RT RIC_SMO->>Collector: 6 Retrieval of RAN and non-RAN data - Non-RT RIC_SMO->>Non-RT RIC_O: 7 Performance monitoring and evaluation - Non-RT RIC_SMO->>Non-RT RIC_O: 8 Trigger for RAN slice SLA assurance - - opt Additional data collection - Non-RT RIC_SMO->>Collector: 9 Request additional measurements - Non-RT RIC_SMO->>E2 Nodes: 10 <> PM measurement configuration - Non-RT RIC_SMO->>Collector: 11 <> Data Collection - Non-RT RIC_SMO->>Collector: 12 Retrieval of RAN data - end - - Non-RT RIC_SMO->>Non-RT RIC_O: 13 Decision for RAN slice SLA assurance - - alt 1: O1 Configuration update - Non-RT RIC_O->>SMO Functions: 14 Creation of slice specific configuration - SMO Functions->>Collector: 15 Request for slice specific RAN configuration update - SMO Functions->>Non-RT RIC_O: 16 <> Configuration update - SMO Functions->>E2 Nodes: 17 <> Configuration update - end - - alt 2: A1 Policy generation - Non-RT RIC_O->>Non-RT RIC_O: 18 RAN slice SLA assurance policy generation - Non-RT RIC_O->>E2 Nodes: 19 <> RAN slice SLA assurance policy creation - E2 Nodes->>Non-RT RIC_O: 20 E2 policy generation - E2 Nodes->>Non-RT RIC_O: 21 <> RAN slice SLA assurance enforcement - E2 Nodes->>Non-RT RIC_O: 22 <> Data collection - Non-RT RIC_O->>Non-RT RIC_O: 23 <> RAN slice SLA assurance policy feedback - end - - Non-RT RIC_O->>Collector: 24 <> Data Collection - Non-RT RIC_O->>Collector: 25 Retrieval of RAN and non-RAN data - Non-RT RIC_O->>Non-RT RIC_O: 26 Performance monitoring and evaluation - - opt A1 Policy removal - Non-RT RIC_O->>Non-RT RIC_O: 27 Decision to remove RAN slice SLA policy - Non-RT RIC_O->>E2 Nodes: 28 <> RAN slice SLA assurance policy removal - end - -``` - -Sequence diagram for Slow loop RAN slice SLA optimization flow. Lifelines: SMO Functions, Collector, Non-RT RIC (SMO), Non-RT RIC (O-RAN), E2 Nodes, App. The process involves SLA retrieval, configuration data exchange, optional enrichment and additional data collection, decision making, configuration updates, policy generation, enforcement, and optional policy removal. - -Figure 4.9.3.2-1: Slow loop RAN slice SLA optimization flow diagram - -#### 4.9.3.3 Fast loop RAN slice SLA optimization - -The context of the fast loop RAN slice SLA optimization is captured in table 4.9.3.3-1. - -Table 4.9.3.3-1: Fast loop RAN slice SLA optimization - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|--------------------------------------|-------------------------| -| Goal | Fast loop RAN slice SLA optimization | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Actors and Roles | Non-RT RIC, Near-RT RIC, SMO, RAN | | -| Assumptions | All relevant functions and components are instantiated.
A1, O1, E2 interface connectivity is established. | | -| Pre-conditions | Near-RT RIC and Non-RT RIC are instantiated with A1 interface connectivity being established between them.
O1 interfaces are established between SMO and Near-RT RIC, and SMO and RAN nodes.
RAN slice SLA assurance models or control apps have been deployed in Near-RT RIC. | | -| Begins when | A RAN slice is activated. | | -| Step 1 | Non-RT RIC decides to generate a policy for Near-RT RIC slice SLA assurance based on RAN slice SLA requirements and/or operator-defined RAN intents, A1 feedback from Near-RT RIC, EI from external app server and O1 based long term trends. | | -| Step 2 | Near-RT RIC receives slice specific O1 configuration and A1 policies from SMO and Non-RT RIC respectively. The former is static and default, the latter is dynamic, optimized and converted from slice SLA. The policies consist of scope identifiers (e.g., S-NSSAI, flow ID, cell ID) and policy statements (e.g., slice specific KPI targets).

In case of using EIs, Near-RT RIC also receives the EIs from Non-RT RIC via A1-EI interface. | | -| Step 3 | Near-RT RIC starts to collect PMs via E2. Examples of the PMs are CSI, PRB usage, L2 throughput, RAN latency, etc. Applicable PMs are specified in 3GPP TS 28.552 [6]. | | -| Step 4 | The model or control app in Near-RT RIC analyzes collected PMs, A1 policies from Non-RT RIC (and optionally EIs from A1-EI interface) to guide RAN nodes via E2 to meet the slice SLA. | | -| Step 5 | Near-RT RIC sends A1 feedback to Non-RT RIC. | | -| Ends when | A RAN slice is deactivated. | | -| Exceptions | None identified. | | -| Post Conditions | None identified. | | - -``` -@startuml -``` - -``` -skinparam ParticipantPadding 5 -``` - -``` -skinparam BoxPadding 10 -``` - -``` -skinparam defaultFontSize 12 -``` - -``` -Autonumber -``` - -``` -Box "Service Management and Orchestration" #gold -``` - -``` -Participant SMO as "SMO Functions" -Boundary Collector -Participant NON as "Non-RT RIC" -end box - -Box "O-RAN" #lightpink -Participant RIC as "Near-RT RIC" -Participant E2NODES as "E2 Nodes" -End box - -Box "External" #lightcyan -Participant APP as "App" -End box - -SMO-> NON : RAN Slice SLA Retrieval -SMO-> NON : Slice specific O1 configuration data of Near-RT RIC and E2 Nodes -E2NODES-> Collector : <> Data Collection -RIC-> Collector : <> Data Collection - -group Opt: Enrichment information collection -APP-> Collector : Enrichment information collection -end - -Collector-> NON : Retrieval of RAN and non-RAN data - -NON-> NON : Performance monitoring and evaluation -NON-> NON : Trigger for RAN slice SLA assurance - -group Opt: Additional data collection -NON-> Collector : Request additional measurements -Collector-> E2NODES : <> PM measurement configuration -E2NODES-> Collector : <> Data Collection -Collector-> NON : Retrieval of RAN data -end - -NON-> NON : Decision for near real time RAN slice SLA assurance -``` - -``` -group A1 Policy generation - NON-> NON : RAN slice SLA assurance policy generation - NON-> RIC : <> RAN slice SLA assurance policy creation -end - -group Opt: A1 Enrichment information transfer - NON-> RIC : <> RAN slice SLA assurance related enrichment information -end - -E2NODES-> RIC : <> Data collection -RIC-> RIC : Performance monitoring and evaluation -RIC-> RIC : Trigger for near real time RAN slice SLA assurance - -group Opt: Additional near real time data collection - RIC-> E2NODES : <> Request additional measurements - E2NODES-> RIC : <> Data collection -end - -group Near real time slice SLA assurance - RIC-> RIC : E2 control or policy generation - RIC-> E2NODES : <> RAN slice SLA assurance enforcement - E2NODES-> RIC : <> Data collection - RIC-> RIC : Performance monitoring and evaluation -end - -group A1 policy feedback - RIC-> NON : <> RAN slice SLA assurance policy feedback -end - -@enduml -``` - -The flow diagram of the fast loop RAN slice SLA optimization is given in figure 4.9.3.3-1. - -![Sequence diagram showing the Fast loop RAN slice SLA optimization flow. Lifelines include SMO Functions, Collector, Non-RT RIC, Near-RT RIC, E2 Nodes, and App. The process involves SLA retrieval, data collection, enrichment information transfer, policy generation, and near real-time SLA assurance.](3b11cc18f8ee769d0076c139dbf81ba3_img.jpg) - -``` - -sequenceDiagram - participant SMO Functions - participant Collector - participant Non-RT RIC - participant Near-RT RIC - participant E2 Nodes - participant App - - Note left of SMO Functions: Service Management and Orchestration - Note right of E2 Nodes: O-RAN - Note right of App: External - - SMO Functions->>Non-RT RIC: 1 RAN Slice SLA Retrieval - Non-RT RIC->>SMO Functions: 2 Slice specific O1 configuration data of Near-RT RIC and E2 Nodes - SMO Functions->>Collector: 3 <> Data Collection - SMO Functions->>Collector: 4 <> Data Collection - - opt Enrichment information collection - Collector->>Non-RT RIC: 5 Enrichment information collection - end - - SMO Functions->>Non-RT RIC: 6 Retrieval of RAN and non-RAN data - Non-RT RIC->>SMO Functions: 7 Performance monitoring and evaluation - Non-RT RIC->>SMO Functions: 8 Trigger for RAN slice SLA assurance - - opt Additional data collection - SMO Functions->>Collector: 9 Request additional measurements - Collector->>Non-RT RIC: 10 <> PM measurement configuration - SMO Functions->>Collector: 11 <> Data Collection - SMO Functions->>Collector: 12 Retrieval of RAN data - end - - SMO Functions->>Non-RT RIC: 13 Decision for near real time RAN slice SLA assurance - - opt A1 Policy generation - Non-RT RIC->>Collector: 14 RAN slice SLA assurance policy generation - Collector->>Non-RT RIC: 15 <> RAN slice SLA assurance policy creation - end - - opt A1 Enrichment information transfer - Non-RT RIC->>Collector: 16 <> RAN slice SLA assurance related enrichment information - end - - Non-RT RIC->>E2 Nodes: 17 <> Data collection - E2 Nodes->>Non-RT RIC: 18 Performance monitoring and evaluation - E2 Nodes->>Non-RT RIC: 19 Trigger for near real time RAN slice SLA assurance - - opt Additional near real time data collection - Non-RT RIC->>E2 Nodes: 20 <> Request additional measurements - E2 Nodes->>Non-RT RIC: 21 <> Data collection - end - - opt Near real time slice SLA assurance - Non-RT RIC->>E2 Nodes: 22 E2 control or policy generation - E2 Nodes->>Non-RT RIC: 23 <> RAN slice SLA assurance enforcement - E2 Nodes->>Non-RT RIC: 24 <> Data collection - E2 Nodes->>Non-RT RIC: 25 Performance monitoring and evaluation - end - - opt A1 policy feedback - Non-RT RIC->>Collector: 26 <> RAN slice SLA assurance policy feedback - end - -``` - -Sequence diagram showing the Fast loop RAN slice SLA optimization flow. Lifelines include SMO Functions, Collector, Non-RT RIC, Near-RT RIC, E2 Nodes, and App. The process involves SLA retrieval, data collection, enrichment information transfer, policy generation, and near real-time SLA assurance. - -Figure 4.9.3.3-1: Fast loop RAN slice SLA optimization flow diagram - -### 4.9.4 Required data - -The data requirements for RAN slice SLA assurance use case are specified below. The required data specified in table 4.9.4-1 shall be supported by the associated interfaces specified in the table. - -Table 4.9.4-1: Required data for RAN slice SLA assurance use case - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|-------------|------------------------------------|--------------------------------------|--------|---------------------------------------|-----------| -| Req-4.9.001 | CQI related measurements | Wideband CQI distribution | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.11.1 | O1 | -| Req-4.9.002 | UE throughput related measurements | Average DL / UL UE throughput in gNB | O-DU | 3GPP TS 28.552 [6], clauses | O1 | - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|-------------|-------------------------------------------------|----------------------------------------------------------------------|--------|-------------------------------------------------------------|-----------| -| | | | | 5.1.1.3.1,
5.1.1.3.3 | | -| Req-4.9.003 | UE throughput related measurements | Scheduled IP throughput in DL/UL | O-DU | 3GPP TS 36.314 [31], clauses 4.1.6.1, 4.1.6.2 | O1 | -| Req-4.9.004 | RRC connection related measurements | Mean / max number of RRC connections | O-CU | 3GPP TS 28.552 [6], clauses 5.1.1.4.1, 5.1.1.4.2 | O1 | -| Req-4.9.005 | RRC connection related measurements | Attempted / successful RRC connection establishments | O-CU | 3GPP TS 28.552 [6], clauses 5.1.1.15.1, 5.1.1.15.2 | O1 | -| Req-4.9.006 | DRB related measurements | Number of DRBs attempted to / successfully setup | O-CU | 3GPP TS 28.552 [6], clauses 5.1.1.10.1, 5.1.1.10.2 | O1 | -| Req-4.9.007 | PDU session management related measurements | Number of PDU sessions requested to / successfully / failed to setup | O-CU | 3GPP TS 28.552 [6], clauses 5.1.1.5.1, 5.1.1.5.2, 5.1.1.5.3 | O1 | -| Req-4.9.008 | Number of active UEs | Mean number of active UEs in the UL / DL per cell | O-DU | 3GPP TS 28.552 [6], clauses 5.1.1.23.1, 5.1.1.23.3 | O1 | -| Req-4.9.009 | Radio resource utilization related measurements | Mean DL / UL PRB used for data traffic | O-DU | 3GPP TS 28.552 [6], clauses 5.1.1.2.5, 5.1.1.2.7 | O1 | -| Req-4.9.010 | PDCP data volume measurements | DL / UL PDCP PDU data volume | O-CU | 3GPP TS 28.552 [6], clauses 5.1.3.6.1.1, 5.1.3.6.1.2 | O1 | -| Req-4.9.011 | PDCP data volume measurements | Data volume in DL/UL | O-CU | 3GPP TS 36.314 [31], clauses 4.1.8.1, 4.1.8.2 | O1 | - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|-------------|-------------------------------|----------------------------------------------------------------------|--------|--------------------------------------------------|-----------| -| Req-4.9.012 | Average user plane delay | UL PDCP packet average delay | O-CU | 3GPP TS 28.558 [52], clause 6.3.1.1.5 | O1 | -| Req-4.9.013 | Average user plane delay | Average delay DL air-interface | O-CU | 3GPP TS 28.552 [6], clause 5.1.1.1.1 | O1 | -| Req-4.9.014 | Average user plane delay | Average delay UL on over-the-air interface | O-CU | 3GPP TS 28.552 [6], clause 5.1.1.1.3 | O1 | -| Req-4.9.015 | Average user plane delay | Average delay DL in gNB-DU | O-DU | 3GPP TS 28.552 [6], clause 5.1.3.3.3 | O1 | -| Req-4.9.016 | Average user plane delay | Average delay DL on F1-U | O-CU | 3GPP TS 28.552 [6], clause 5.1.3.3.2 | O1 | -| Req-4.9.017 | Average user plane delay | Average delay DL in CU-UP | O-CU | 3GPP TS 28.552 [6], clause 5.1.3.3.1 | O1 | -| Req-4.9.018 | Average user plane delay | Average over-the-air interface packet delay in the UL per DRB per UE | O-CU | 3GPP TS 38.314 [32], clause 4.2.1.2.2 | O1 | -| Req-4.9.019 | Average user plane delay | Average delay DL air-interface | O-CU | 3GPP TS 28.558 [52], clause 6.3.1.1.1 | O1 | -| Req-4.9.020 | Packet drop measurements | DL RLC SDU packet drop rate in gNB-DU | O-DU | 3GPP TS 28.552 [6], clause 5.1.3.2.2 | O1 | -| Req-4.9.021 | Packet loss rate measurements | UL / DL F1-U packet loss rate | O-CU | 3GPP TS 28.552 [6], clauses 5.1.3.1.2, 5.1.3.1.3 | O1 | -| Req-4.9.022 | Packet loss rate measurements | Packet Uu loss rate in the DL per DRB per UE | O-CU | 3GPP TS 38.314 [32], clause 4.2.1.5.1 | O1 | -| Req-4.9.023 | Configuration | NRCellCU | O-CU | 3GPP TS 28.541 [5], clause 4.3.4 | O1 | -| Req-4.9.024 | Configuration | NRCellDU | O-DU | 3GPP TS 28.541 [5], clause 4.3.5 | O1 | -| Req-4.9.025 | Configuration | GNBDUFunction | O-DU | 3GPP TS 28.541 [5], clause 4.3.1 | O1 | - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|-------------|---------------|---------------------------|--------|-----------------------------------|-----------| -| Req-4.9.026 | Configuration | GNBCUCPFunction | O-CU | 3GPP TS 28.541 [5], clause 4.3.2 | O1 | -| Req-4.9.027 | Configuration | GNBCUUPFunction | O-CU | 3GPP TS 28.541 [5], clause 4.3.3 | O1 | -| Req-4.9.028 | Configuration | RRMPolicy_ | O-CU | 3GPP TS 28.541 [5], clause 4.3.43 | O1 | - -## 4.10 Multi-vendor slices - -This use case “multi-vendor slices” is a case that vO-DU and vO-CU functions composing each slice is provided from different vendor. In this sub-clause, concept, motivation and benefits of introducing “multi-vendor slices” are explained and candidate solutions are studied. - -### 4.10.1 Background and goal of the use case - -Proposed use case enables multiple slices with functions provided from multi-vendors, such as slice #1 is composed with DU and CU provided from vendor A and slice #2 is composed with DU and CU provided from vendor B (see figure 4.10.1-1). - -![Diagram of multi-vendor slices architecture showing an O-RU connected to multiple vO-DUs (Vendor A and Vendor B) which are then connected to vO-CUs and finally to a 5G Core. Slice #1 (eMBB) uses Vendor A's vO-DU and vO-CU, while Slice #2 (URLLC) uses Vendor B's vO-DU and vO-CU. A legend indicates RAN Vendor A (orange), RAN Vendor B (blue), and RAN Vendor C (green).](b1e7bb95fa1587d870de03df02477df4_img.jpg) - -Diagram of multi-vendor slices architecture showing an O-RU connected to multiple vO-DUs (Vendor A and Vendor B) which are then connected to vO-CUs and finally to a 5G Core. Slice #1 (eMBB) uses Vendor A's vO-DU and vO-CU, while Slice #2 (URLLC) uses Vendor B's vO-DU and vO-CU. A legend indicates RAN Vendor A (orange), RAN Vendor B (blue), and RAN Vendor C (green). - -Figure 4.10.1-1: Multi-vendor slices - -To support multi-vendor slicing, there are many possible configurations to realize this use case; all of which share that one O-RU is connected to one or more O-DUs. For example, one possible configuration might be one where a single cell is shared by two O-DUs, and another possible configuration is where two cells are allocated to two different O-DUs in a Shared O-RU configuration. Under those possible configurations, it is desired to keep frequency efficiency. - -When providing multiple slices, it is assumed that suitable vO-DU/scheduler and vO-CU treat each slice respectively. A vendor who providing 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 -Operator can maximize options to choose suitable vO-DU/scheduler and vO-CU to offer various slice. For example, some vendor has a strength of a scheduler for eMBB service and the other has 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 operator can choose vO-DU and vO-CU functions from vendor A to meet their service requirement. - -Also, when operator will add a new service/slice, new functions from a new vendor can be introduced with less consideration for existing vendor if multi-vendor circumstance was realized. This can lead to 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 lead to expand opportunity reaching agreement of RAN sharing among operators. With expansion of RAN sharing, CAPEX and OPEX by operator will be optimized and additional investment can be done more. - -#### 3) Reducing supply chain risk - -If existing vendor providing a certain pair of vO-DU and vO-CU functions would withdraw of their market due to business reason, operator can deploy new vO-DU and vO-CU functions alternatively from other vendor under this multi-vendor circumstance. This can reduce a risk for operators' business continuity. - -### 4.10.2 Entities/resources involved in the use case - -#### 1) SMO multi-vendor slice App: - -- a) Configures vO-DU and vO-CU. -- b) Configures O-RU to connect to vO-DU. - -#### 2) Near-RT RIC: - -- a) Shares MAC related data unique for UE among vO-DUs. -- b) Supports communication of configuration parameters to RAN. - -#### 3) E2 nodes (vO-CU, vO-DU, O-RU): - -- a) Primary vO-DU processes SRB (Signalling Radio Bearer), DRB (Data Radio Bearer) and other vO-DU related functions. Secondary vO-DU processes only DRB related functions. Note that vO-DU and vO-CU are created as part of network slice creation procedure. - -### 4.10.3 Solutions - -#### 4.10.3.1 Data transmission call flow example for multi-vendor slices use case - -The context of data transmission call flow example for multi-vendor slices use case is captured in table 4.10.3.1-1. - -**Table 4.10.3.1-1: Data transmission call flow example for multi-vendor slices use case** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | UE communicates on slice #1 and #2 respectively. | | -| Actors and Roles |
  • - SMO multi-vendor slice App configures vO-DU and vO-CU with radio resource assignment (via Orchestrator) and collects KPI data.
  • - Near-RT RIC configures vO-DU and vO-CU for resource assignment and shares MAC related information unique for UE among vO-DUs.
  • - Primary vO-DU processes SRB (Signalling Radio Bearer), DRB (Data Radio Bearer). Secondary vO-DU processes only DRB.
| | -| Assumptions | - All relevant functions and components are instantiated. | | - -| Use Case Stage | Evolution / Specification | <> | -|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------| -| | | Related use | -| |
  • - Slice #1 is created over primary vO-DU and vO-CU with logical channel ID #1 and #2, and slice #2 is created over secondary vO-DU and vO-CU with logical channel ID #3.
  • - O-RU is shared between primary vO-DU and secondary vO-DU with one component carrier.
  • - CU-CP is shared between primary vO-CU-UP and secondary vO-CU-UP.
  • - TDD operation is assumed.
  • - UE tries to transmit data on slice #1 and #2.
| | -| Pre-conditions |
  • - Slice #1 and #2 are created and activated on primary vO-DU, vO-CU and secondary vO-DU, vO-CU respectively.
  • - Slice #1 is tied with scheduling request resource 1 and logical channel ID #1 and #2, and slice #2 is tied with scheduling request resource 2 and logical channel ID #3
  • - Primary vO-DU and secondary vO-DU know which timing/resource block they can utilize on for slice #1 and #2 respectively by direction from SMO via O1 interface.
  • - UE has already performed RACH procedure with primary vO-DU.
| | -| Begins when | UE tries to perform registration procedure with RRC Connection Request message. | | -| Step 1 (M) |

[UE performs registration procedure]

UE sends RRC Connection Request message to primary vO-DU and vO-CU through O-RU. Primary vO-CU and vO-DU responds with RRC Connection Setup. UE sends RRC connection Setup Complete message.

Primary vO-DU sends initial RRC message and shared information such as C-RNTI to Near RT-RIC. Near RT-RIC determines to transfer it to secondary vO-DU over E2 interface. Other registration procedure is performed.

| | -| Step 2 (M) |

[PDU session establishment]

UE starts PDU session establishment procedure with PDU session establishment request message with primary vO-DU and vO-CU.

UE initiates PDU session establishment procedure with S-NSSAI 2 for slice #2 via primary vO-DU. UE context modification is made at secondary vO-DU.

| | -| Step 3 (M) |

[U-plane data transmission between primary vO-DU and O-RU]

At allocated timing/resources, primary vO-DU sends Scheduling Command message to O-RU to start transfer and receive DL and UL Data.

UE sends Scheduling Request message on PUCCH with scheduling request resource 1 to primary vO-DU over open fronthaul.

Primary vO-DU responds with UL Grant message to the UE.

| O-RAN.WG4.CUS.0-v02.00 [29], "Figure 6-5: C-plane and U-plane message transfer procedure (DL & UL shown)" | -| Step 4 (M) |

[Buffer notification and transmission user data]

UE notices buffer with Buffer Status Request message to primary vO-DU.

| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------| -| | Primary vO-DU acknowledges with UL Grant message.
UE sends user data on PUSCH with logical channel ID #1 and #2.
Primary vO-DU acknowledges with Ack or Nack.
UE repeats step 3 until buffer becomes empty. | | -| Step 5 (M) | [U-plane data transmission between secondary vO-DU and O-RU]
At allocated timing/resources, secondary vO-DU sends Scheduling Command message to O-RU to start transfer and receive DL and UL Data.
UE sends Scheduling Request message on PUCCH with scheduling request resource 2 to secondary vO-DU over open fronthaul. Secondary vO-DU responds with UL Grant message to the UE. | O-RAN.WG4.CUS.0-v02.00 [29], "Figure 6-5: C-plane and U-plane message transfer procedure (DL & UL shown)" | -| Step 6 (M) | [Buffer notification and transmission user data]
UE notices buffer with Buffer Status Request message to secondary vO-DU.
Secondary vO-DU acknowledges with UL Grant message.
UE sends user data on PUSCH with logical channel ID #3.
Secondary vO-DU acknowledges with Ack or Nack.
UE repeats step 5 until buffer becomes empty. | | -| Step 7 (M) | [Collect data]
RAN related data from RAN nodes are collected at SMO Collector via O1 interface. | | -| Ends when | UE finishes data transmission until buffer becomes empty. | | -| Exceptions | None identified. | | -| Post Conditions | None identified | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "SMO" #gold - Boundary Collector -end box - -Box "O-RAN" #lightpink - Participant NRTRIC as "Near-RT RIC" - Participant OCUCP as "O-CU-CP" - -``` - -Participant pOCUUP as "pO-CU-UP" - -Participant pODU as "pO-DU" - -Participant sOCUUP as "sO-CU-UP" - -Participant sODU as "sO-DU" - -Participant ORU as "O-RU" - -End box - -Participant UE as "UE" - -note right of UE #aqua - -SRR: Scheduling Request Resource - -LCID: Logical Channel ID - -end note - -Hnote over Collector, sODU - -pO-DU and sO-DU are allocated resources for fronthaul usage from SMO - -endnote - -Hnote over Collector, sODU - -Slice #1 and #2 are created - -endnote - -Hnote over OCUCP, UE - -UE performed RACH procedure with primary vO-DU and vO-CU - -endnote - -||| - -== Registration == - -UE-> pODU : RRC Connection Request - -pODU-> OCUCP: <>Initil RRC message - -OCUCP-> pODU: <>DL RRC message transfer - -pODU-> UE : RRC Connection Setup - -UE-> pODU : RRC Connection Setup Complete - -pODU-> OCUCP: <>UL RRC message transfer(shared Info) - -``` -pODU-> NRTRIC: <RAN UE ID, Relay Cell ID, shared Info(C-RNTI, etc.) -``` - -``` -note over NRTRIC -``` - -``` -Determine to transfer it to sO-DU -``` - -``` -end note -``` - -``` -NRTRIC-> sODU: <>Relay above information -``` - -``` -Hnote over sOCUUP,UE -``` - -``` -Other Registration procedure complete -``` - -``` -endnote -``` - -``` -||| -``` - -``` -== PDU Session setup == -``` - -``` -Hnote over sOCUUP,UE -``` - -``` -PDU session establishment procedure on Primary DU (Slice #1 / N-SSAI 1) -``` - -``` -endnote -``` - -``` -note over pODU -``` - -``` -pODU is allocated -``` - -``` -resources from RIC -``` - -``` -end note -``` - -``` -pODU -> ORU: C-plane(Scheduling Command) -``` - -``` -UE -> ORU: PDU Session Establishment Req.(S-NSSAI 2) -``` - -``` -ORU -> pODU: U-plane(UL IQ data) -``` - -``` -pODU -> OCUCP: PDU Session Establishment Req.(S-NSSAI 2) -``` - -``` -OCUCP -> sODU: UE ContextSetup Req -``` - -``` -sODU -> OCUCP: UE ContextSetup Rsp -``` - -``` -pODU -> ORU: C-plane(Scheduling Command) -``` - -``` -OCUCP -> pODU: RRC Reconf / PDU Session Establishment Accept -``` - -``` -pODU -> ORU: U-plane(DL IQ data) -``` - -``` -ORU -> UE: RRC Reconfiguration -``` - -``` -UE -> ORU: RRC Reconfiguration Complete -``` - -``` -ORU -> pODU: U-plane - -pODU -> OCUCP: PDU Session resource setup Rsp - -OCUCP -> sODU: UE Context Modification Req(RRC Reconf Comp Ind) - -sODU -> OCUCP: UE Context Modification Rsp - -||| - -@enduml -``` - -The data transmission call flow example for multi-vendor slices use case – part 1 of 2 is given in figure 4.10.3.1-1. - -![Sequence diagram showing data transmission call flow for multi-vendor slices use case. Lifelines include SMO (Collector), Near-RT RIC, O-CU-CP, pO-CU-UP, pO-DU, sO-CU-UP, sO-DU, O-RU, and UE. The diagram is divided into Registration and PDU Session setup phases.](909726977de6efd2d4df015198a2907b_img.jpg) - -The sequence diagram illustrates the interaction between network functions for multi-vendor slices. It begins with resource allocation and slice creation from the SMO. The UE performs a RACH procedure with the primary vO-DU and vO-CU. The Registration phase involves 8 steps between the UE, pO-DU, O-CU-CP, and Near-RT RIC. The PDU Session setup phase involves 14 steps between the UE, pO-DU, O-CU-CP, and Near-RT RIC, including C-plane and U-plane data exchanges. - -**Legend:** - SRR: Scheduling Request Resource - LCID: Logical Channel ID - -**Sequence of Events:** - -- pO-DU and sO-DU are allocated resources for fronthaul usage from SMO -- Slice #1 and #2 are created -- UE performed RACH procedure with primary vO-DU and vO-CU -- Registration** - - 1 RRC Connection Request (UE to pO-DU) - - 2 <>Initial RRC message (pO-DU to O-CU-CP) - - 3 <>DL RRC message transfer (O-CU-CP to pO-DU) - - 4 RRC Connection Setup (pO-DU to UE) - - 5 RRC Connection Setup Complete (UE to pO-DU) - - 6 <>UL RRC message transfer(shared Indo) (pO-DU to O-CU-CP) - - 7 <>RAN UE ID, Relay Cell ID, shared Info(C-RNTI, etc.) (O-CU-CP to Near-RT RIC) - - Determine to transfer it to sO-DU (Near-RT RIC internal) - - 8 <>Relay above information (Near-RT RIC to pO-DU) - - Other Registration procedure complete -- PDU Session setup** - - PDU session establishment procedure on Primary DU (Slice #1 / N-SSAI 1) - - pO-DU is allocated resources from RIC (Near-RT RIC to pO-DU) - - 9 C-plane(Scheduling Command) (pO-DU to sO-DU) - - 10 PDU Session Establishment Req.(S-NSAI 2) (sO-DU to pO-DU) - - 11 U-plane(UL IO data) (pO-DU to sO-DU) - - 12 PDU Session Establishment Req.(S-NSAI 2) (pO-DU to O-CU-CP) - - 13 UE ContextSetup Req (O-CU-CP to pO-DU) - - 14 UE ContextSetup Rsp (pO-DU to O-CU-CP) - - 15 C-plane(Scheduling Command) (pO-DU to sO-DU) - - 16 RRC Reconf / PDU Session Establishment Accept (pO-DU to UE) - - 17 U-plane(DL IO data) (sO-DU to pO-DU) - - 18 RRC Reconfiguration (pO-DU to UE) - - 19 RRC Reconfiguration Complete (UE to pO-DU) - - 20 U-plane (pO-DU to sO-DU) - - 21 PDU Session resource setup Rsp (sO-DU to pO-DU) - - 22 UE Context Modification Req(RRC Reconf Comp Indo) (pO-DU to O-CU-CP) - - 23 UE Context Modification Rsp (O-CU-CP to pO-DU) - -Sequence diagram showing data transmission call flow for multi-vendor slices use case. Lifelines include SMO (Collector), Near-RT RIC, O-CU-CP, pO-CU-UP, pO-DU, sO-CU-UP, sO-DU, O-RU, and UE. The diagram is divided into Registration and PDU Session setup phases. - -Figure 4.10.3.1-1: Data transmission call flow example for multi-vendor slices use case – part 1 of 2 - -``` -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "SMO" #gold - Boundary Collector -end box - -Box "O-RAN" #lightpink -``` - -Participant NRTRIC as "Near-RT RIC" - -Participant OCUCP as "O-CU-CP" - -Participant pOCUUP as "pO-CU-UP" - -Participant pODU as "pO-DU" - -Participant sOCUUP as "sO-CU-UP" - -Participant sODU as "sO-DU" - -Participant ORU as "O-RU" - -End box - -Participant UE as "UE" - -||| - -== Data transmission on slice #1 == - -note over pODU - -pO-DU is allocated - -resources from RIC - -end note - -note over UE - -SRR 1 is selected - -since UE tries to - -send data on slice #1 - -end note - -pODU -> ORU: Scheduling Command - -alt UE sends data on slice #1 - -UE -> ORU : Scheduling Request (LCGID 1/2) - -ORU -> pODU: U-plane - -pODU -> ORU: U-plane - -ORU -> UE : UL Grant (DCI0) - -loop until buffer empty - -UE -> ORU : Buffer Status Reporting - -ORU -> pODU: U-plane - -``` -pODU -> ORU: U-plane - -ORU -> UE : UL Grant - -UE -> ORU : User Data on PUSCH(LCGID 1/2) - -ORU -> pODU: U-plane - -pODU -> ORU: U-plane - -ORU -> UE : Ack / Nack - -end - -end - -||| - -== Data transmission on slice #2 == - -note over sODU - -sO-DU is allocated - -resources from RIC - -end note - -note over UE - -SRR 2 is selected - -since UE tries to - -send data on slice #2 - -end note - -sODU -> ORU: Scheduling Command - -alt UE sends data on slice #2 - -UE -> ORU : Scheduling Request (LCGID 3) - -ORU -> sODU: U-plane - -sODU -> ORU: U-plane - -ORU -> UE : UL Grant (DCI0) - -loop until buffer empty - -UE -> ORU : Buffer Status Reporting - -ORU -> sODU: U-plane -``` - -``` -sODU -> ORU: U-plane -ORU -> UE : UL Grant -UE -> ORU : User Data on PUSCH(LCGID 3) -ORU -> sODU: U-plane -sODU -> ORU: U-plane -ORU -> UE : Ack / Nack -end -end - -||| -@enduml -``` - -The data transmission call flow example for multi-vendor slices use case – part 2 of 2 is given in figure 4.10.3.1-2. - -![Sequence diagram showing data transmission call flow for multi-vendor slices use case. The diagram illustrates two slices (slice #1 and slice #2) being transmitted from a UE through an O-RU, sDU, pDU, CU-UP, CU-CP, and RIC to an SMO Collector. Slice #1 uses pDU and slice #2 uses sDU. The diagram includes messages for scheduling, data transmission, and buffer status reporting, with loops for until buffer empty and alt blocks for UE sends data.](56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg) - -The diagram illustrates the data transmission call flow for a multi-vendor slices use case. It shows two separate data transmission processes for slice #1 and slice #2. - -**Slice #1 Transmission:** - -- The UE sends a Scheduling Request (LCGID 1/2) to the O-RU. -- The O-RU sends a Scheduling Command to the pDU. -- A note indicates "pDU is allocated resources from RIC". -- An alt block titled "[UE sends data on slice #1]" contains: - - The UE sends 2 Scheduling Request (LCGID 1/2) to the O-RU. - - The O-RU sends 3 U-plane to the pDU. - - The pDU sends 4 U-plane to the sDU. - - The sDU sends 5 UL Grant (DCI0) to the UE. - - A loop titled "[until buffer empty]" contains: - - The UE sends 6 Buffer Status Reporting to the O-RU. - - The O-RU sends 7 U-plane to the pDU. - - The pDU sends 8 U-plane to the sDU. - - The sDU sends 9 UL Grant to the UE. - - The UE sends 10 User Data on PUSCH(LCGID 1/2) to the O-RU. - - The O-RU sends 11 U-plane to the pDU. - - The pDU sends 12 U-plane to the sDU. - - The sDU sends 13 Ack / Nack to the UE. -- A note indicates "SRR 1 is selected since UE tries to send data on slice #1". - -**Slice #2 Transmission:** - -- The UE sends a Scheduling Request (LCGID 3) to the O-RU. -- The O-RU sends a Scheduling Command to the sDU. -- A note indicates "sDU is allocated resources from RIC". -- An alt block titled "[UE sends data on slice #2]" contains: - - The UE sends 15 Scheduling Request (LCGID 3) to the O-RU. - - The O-RU sends 16 U-plane to the pDU. - - The pDU sends 17 U-plane to the sDU. - - The sDU sends 18 UL Grant (DCI0) to the UE. - - A loop titled "[until buffer empty]" contains: - - The UE sends 19 Buffer Status Reporting to the O-RU. - - The O-RU sends 20 U-plane to the pDU. - - The pDU sends 21 U-plane to the sDU. - - The sDU sends 22 UL Grant to the UE. - - The UE sends 23 User Data on PUSCH(LCGID 3) to the O-RU. - - The O-RU sends 24 U-plane to the pDU. - - The pDU sends 25 U-plane to the sDU. - - The sDU sends 26 Ack / Nack to the UE. -- A note indicates "SRR 2 is selected since UE tries to send data on slice #2". - -Sequence diagram showing data transmission call flow for multi-vendor slices use case. The diagram illustrates two slices (slice #1 and slice #2) being transmitted from a UE through an O-RU, sDU, pDU, CU-UP, CU-CP, and RIC to an SMO Collector. Slice #1 uses pDU and slice #2 uses sDU. The diagram includes messages for scheduling, data transmission, and buffer status reporting, with loops for until buffer empty and alt blocks for UE sends data. - -Figure 4.10.3.1-2: Data transmission call flow example for multi-vendor slices use case – part 2 of 2 - -#### 4.10.3.2 Data transmission call flow example for RAN sharing use case - -The context of data transmission call flow example for RAN sharing use case is captured in table 4.10.3.2-1. - -**Table 4.10.3.2-1: Data transmission call flow example for RAN sharing use case** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | UE communicates on secondary vO-DU and vO-CU with PLMN #2. | | -| Actors and Roles |
  • - SMO multi-vendor slice App configures vO-DU and vO-CU with radio resource assignment (via Orchestrator) and collects KPI data.
  • - Near-RT RIC configures vO-DU and vO-CU for resource assignment and shares MAC related information unique for UE among vO-DUs.
  • - Primary vO-DU processes SRB (Signalling Radio Bearer), DRB (Data Radio Bearer). Secondary vO-DU processes only DRB.
| | -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - PLMN #1 is assigned to primary vO-DU and vO-CU, and PLMN #2 is assigned to secondary vO-DU and vO-CU respectively.
  • - O-RU is shared between primary vO-DU and secondary vO-DU with one component carrier.
  • - CU-CP is shared between primary vO-CU-UP and secondary vO-CU-UP.
  • - TDD operation is assumed.
  • - UE tries to transmit data with PLMN #2.
| | -| Pre-conditions |
  • - PLMN #1 and #2 are assigned to primary vO-DU, vO-CU and secondary vO-DU, vO-CU respectively
  • - Primary vO-DU and vO-CU advertise PLMN #1 and #2 over the air.
  • - Primary vO-DU and secondary vO-DU know which timing/resource block they can utilize on for PLMN #1 and #2 respectively by direction from SMO via O1 interface.
  • - UE has already performed RACH procedure with primary vO-DU.
| | -| Begins when | UE tries to perform registration procedure with RRC Connection Request message. | | -| Step 1 (M) |

[UE performs registration procedure with PLMN #2]

UE sends RRC Connection Request message to primary vO-DU and vO-CU through O-RU. Primary vO-CU and vO-DU responds with RRC Connection Setup. UE sends RRC connection Setup Complete message with PLMN#2 in selected PLMN-identity.

Primary vO-DU sends initial RRC message with PLMN-identity and shared information such as C-RNTI to Near RT-RIC. Near RT-RIC determines to transfer it to secondary vO-DU over E2 interface. Other registration procedure is performed through secondary vO-DU.

| | -| Step 2 (M) |

[PDU session establishment]

UE starts PDU session establishment procedure with PDU session establishment request message through secondary vO-DU and vO-CU.

| | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------| -| | | Related use | -| Step 3 (M) | [U-plane data transmission between secondary vO-DU and O-RU]
At allocated timing/resources, secondary vO-DU sends Scheduling Command message to O-RU to start transfer and receive DL and UL Data.
UE sends Scheduling Request message on PUCCH with scheduling request resource 2 to secondary vO-DU over open fronthaul.
Secondary vO-DU responds with UL Grant message to the UE. | O-RAN.WG4.CUS.0-v02.00 [29], "Figure 6-5: C-plane and U-plane message transfer procedure (DL & UL shown)" | -| Step 4 (M) | [Buffer notification and transmission user data]
UE notices buffer with Buffer Status Request message to secondary vO-DU.
Secondary vO-DU acknowledges with UL Grant message.
UE sends user data on PUSCH with logical channel ID #2.
Secondary vO-DU acknowledges with Ack or Nack.
UE repeats step 3 until buffer becomes empty. | | -| Step 5 (M) | [Collect data]
RAN related data from RAN nodes are collected at SMO Collector via O1 interface. | | -| Ends when | UE finishes data transmission until buffer becomes empty. | | -| Exceptions | None identified. | | -| Post Conditions | None identified. | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "SMO" #gold - Boundary Collector -end box - -Box "O-RAN" #lightpink - Participant NRTRIC as "Near-RT RIC" - Participant OCUCP as "O-CU-CP" - Participant pOCUUP as "pO-CU-UP" - Participant pODU as "pO-DU" - Participant sOCUUP as "sO-CU-UP" - -``` - -Participant sODU as "sO-DU" - -Participant ORU as "O-RU" - -End box - -Participant UE as "UE" - -||| - -== Data transmission on slice #1 == - -note over pODU - -pO-DU is allocated - -resources from RIC - -end note - -note over UE - -SRR 1 is selected - -since UE tries to - -send data on slice #1 - -end note - -pODU -> ORU: Scheduling Command - -alt UE sends data on slice #1 - -UE -> ORU : Scheduling Request (LCGID 1/2) - -ORU -> pODU: U-plane - -pODU -> ORU: U-plane - -ORU -> UE : UL Grant (DCI0) - -loop until buffer empty - -UE -> ORU : Buffer Status Reporting - -ORU -> pODU: U-plane - -pODU -> ORU: U-plane - -ORU -> UE : UL Grant - -UE -> ORU : User Data on PUSCH(LCGID 1/2) - -ORU -> pODU: U-plane - -pODU -> ORU: U-plane - -``` -ORU -> UE : Ack / Nack - -end - -end - -||| - -== Data transmission on slice #2 == - -note over sODU -sO-DU is allocated -resources from RIC -end note - -note over UE -SRR 2 is selected -since UE tries to -send data on slice #2 -end note - -sODU -> ORU: Scheduling Command - -alt UE sends data on slice #2 - UE -> ORU : Scheduling Request (LCGID 3) - ORU -> sODU: U-plane - sODU -> ORU: U-plane - ORU -> UE : UL Grant (DCI0) - - loop until buffer empty - UE -> ORU : Buffer Status Reporting - ORU -> sODU: U-plane - sODU -> ORU: U-plane - ORU -> UE : UL Grant - UE -> ORU : User Data on PUSCH(LCGID 3) - ORU -> sODU: U-plane - sODU -> ORU: U-plane -``` - -``` - -ORU -> UE : Ack / Nack - -end - -end - -||| - -@enduml - -``` - -The data transmission call flow example for RAN sharing use case is given in figure 4.10.3.2-1. - -![Sequence diagram showing the data transmission call flow for RAN sharing use case. It involves SMO, Near-RT RIC, O-CU-CP, pO-CU-UP, pO-DU, sO-CU-UP, sO-DU, O-RU, and UE. The process includes registration with PLMN #2 and subsequent data transmission with PLMN #2.](199a8b4c5c620006757a17e930769566_img.jpg) - -The sequence diagram illustrates the interaction for RAN sharing. It starts with the SMO (Service Management and Orchestration) allocating timing for fronthaul usage to the pO-DU and sO-DU. The UE performs a RACH procedure with the primary vO-DU and vO-CU. A note indicates PLMN#1: pO-DU, pO-CU and PLMN#2: sO-DU, sO-CU are advertised. - -**Registration with PLMN #2 phase:** - -- 1: RRC Connection Request from UE to pO-DU. -- 2: <> Initial RRC message from pO-DU to O-CU-CP. -- 3: <> DL RRC message transfer from O-CU-CP to pO-DU. -- 4: RRC Connection Setup from pO-DU to UE. -- 5: RRC Connection Setup Complete (PLMN#2) from UE to pO-DU. -- 6: <> UL RRC message transfer (PLMN #2, shared Info) from pO-DU to O-CU-CP. -- 7: <> RAN UE ID, Relay Cell ID, target PLMN (PLMN2), shared Info (C-RNTI, etc.) from O-CU-CP to Near-RT RIC. -- Near-RT RIC determines to transfer it to sO-DU since PLMN #2 session. -- 8: <> Relay above information from Near-RT RIC to sO-DU. -- Other Registration procedure complete and PDU session establishment procedure follow. - -**Data transmission with PLMN #2 phase:** - -- sO-DU is allocated resources from RIC. -- 9: Scheduling Command from sO-DU to O-RU. -- 10: Scheduling Request from UE to sO-DU. -- 11: U-plane from sO-DU to O-RU. -- 12: U-plane from O-RU to UE. -- 13: UL Grant (DCI0) from sO-DU to UE. -- loop [until buffer empty]** - - 14: Buffer Status Request from UE to sO-DU. - - 15: UL Grant from sO-DU to UE. - - 16: User Data on PUSCH from UE to sO-DU. - - 17: Ack / Nack from sO-DU to UE. - -Sequence diagram showing the data transmission call flow for RAN sharing use case. It involves SMO, Near-RT RIC, O-CU-CP, pO-CU-UP, pO-DU, sO-CU-UP, sO-DU, O-RU, and UE. The process includes registration with PLMN #2 and subsequent data transmission with PLMN #2. - -Figure 4.10.3.2-1: Data transmission call flow example for RAN sharing use case - -### 4.10.4 Required data - -The measurement counters and KPIs (as defined by 3GPP and will be extended for O-RAN use cases) shall be appropriately aggregated by cell, QoS type, slice, etc. - -- 1) Per-UE CSI -- 2) Per slice performance statistics such as PDCP throughput, PRB usage - -## 4.11 Dynamic spectrum sharing (DSS) - -This use case provides the background, motivation, and requirements to realize Dynamic Spectrum Sharing (DSS) over the O-RAN architecture. This is to enable operators to adapt radio resource allocation policies and control to dynamically share radio spectrum between 4G and 5G networks. - -### 4.11.1 Background and goal of the use case - -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 those users close to the cell, this situation worsens in the UL as the UE device is power constrained. A cost-effective way to address this is the 5G deployment on lower bands (i.e., below 2GHz), which are also used in 4G LTE deployments today. 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 varying workloads of the 4G and 5G network. - -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 and necessary QoS to NR devices, under the assumption that the two networks will co-exist in the near term. 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 O-RAN's framework for traffic prediction, DSS related resource management and conduct control functions. Towards this, the intelligent control functions are identified, which can be realized as a DSS application to augment the L3/L2/L1 control functions specified as part of LTE-NR coexistence in 3GPP TS 23.501 [2] and in 3GPP TS 37.340 [12]. - -The architectural context set for this discussion is shown in figure 4.11.1-1. 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 the spectrum resource in addition to the L2/L1 adaptation for 5G-NR to co-exist with LTE. - -Considering the scenario of incremental deployment - in the 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 UE is expected to be dual stacked. 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. - -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 connects 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 using resource management and interference mitigation functions in the RIC between them. - -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 O-RAN. - -An abstracted view of how DSS application can be realized using the Non-Real-Time and Near-Real-Time RIC components is shown in figure 4.11.1-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 traffic prediction and 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 related functions in the CU/DU corresponding to the LTE and 5G cells. The DSS-App engineers at the Non-RT RIC level translates the global DSS policies based on 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. edge or central office). The RAT-App at the Non-RT RIC level also translates the DSS-App’s resource policies to RAT specific configuration and policies at the Near-RT RIC and the CU/DU entities. The DSS-App at the Near-RT RIC uses the data collected by the RAT-App to make dynamic resource sharing decisions that are enforced by the RAT-App using the E2 control APIs. - -![Figure 4.11.1-1: RIC-based DSS architecture diagram. It shows a hierarchy starting from SMO at the top, containing nonRT-RIC with R-APP(DSS). Below it is nRT-RIC with X-APP(DSS). These connect via O1 and A1 interfaces. The nRT-RIC connects to CU+DU (LTE) and CU+DU (5G) via E2 interfaces. The CU+DU (LTE) is connected to NG-eNodeB/eNB, and the CU+DU (5G) is connected to gNodeB. Both base stations are connected to EPC/NGCore. Below the base stations are three user equipment (UE) icons: UE-4G, UE-4G+5G, and UE-5G. Spectrum X is indicated for the LTE side and Spectrum X+Y for the 5G side. An X2/Xn interface is shown between the two CU+DU units.](ba676d18b6a00f27c5bfaec9eeec20be_img.jpg) - -Figure 4.11.1-1: RIC-based DSS architecture diagram. It shows a hierarchy starting from SMO at the top, containing nonRT-RIC with R-APP(DSS). Below it is nRT-RIC with X-APP(DSS). These connect via O1 and A1 interfaces. The nRT-RIC connects to CU+DU (LTE) and CU+DU (5G) via E2 interfaces. The CU+DU (LTE) is connected to NG-eNodeB/eNB, and the CU+DU (5G) is connected to gNodeB. Both base stations are connected to EPC/NGCore. Below the base stations are three user equipment (UE) icons: UE-4G, UE-4G+5G, and UE-5G. Spectrum X is indicated for the LTE side and Spectrum X+Y for the 5G side. An X2/Xn interface is shown between the two CU+DU units. - -Figure 4.11.1-1: RIC-based DSS architecture - -![Figure 4.11.1-2: RIC-based DSS realization diagram. This diagram shows a more detailed breakdown of the RIC components. The SMO contains a NonRT RIC with a Regional Cloud, which hosts a DSS-App and two RAT-Apps (RAT-App-4G and RAT-App-5G). The NonRT RIC connects to the NearRT RIC via O1 and A1 interfaces. The NearRT RIC, located in a Central Office, also contains a DSS-App and two RAT-Apps (RAT-App-4G and RAT-App-5G). The NearRT RIC connects to the RAN via E2 interfaces. The RAN contains two CU/DU units: (CU/DU) 4G and (CU/DU) 5G. These are connected to 4G/5G UEs via base station icons. There is also an O1 interface shown on the right side of the RAN.](b4c825454b7a89b4d7744e4f45521174_img.jpg) - -Figure 4.11.1-2: RIC-based DSS realization diagram. This diagram shows a more detailed breakdown of the RIC components. The SMO contains a NonRT RIC with a Regional Cloud, which hosts a DSS-App and two RAT-Apps (RAT-App-4G and RAT-App-5G). The NonRT RIC connects to the NearRT RIC via O1 and A1 interfaces. The NearRT RIC, located in a Central Office, also contains a DSS-App and two RAT-Apps (RAT-App-4G and RAT-App-5G). The NearRT RIC connects to the RAN via E2 interfaces. The RAN contains two CU/DU units: (CU/DU) 4G and (CU/DU) 5G. These are connected to 4G/5G UEs via base station icons. There is also an O1 interface shown on the right side of the RAN. - -Figure 4.11.1-2: RIC-based DSS realization - -The main goal of the Non-RT DSS-App is to provide long-term scheduling policy to 4G and 5G scheduler considering business, user, spatial and temporal workload factors. - -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.2 Entities/resources involved in the use case - -- 1) Non-RT RIC: - - a) Receive SMO's DSS specific service requirement for the RAN and translate them into resource sharing policies. - - b) Provide long-term policies in terms of scheduling guidance to 4G and 5G scheduler over A1 to Near-RT RIC, considering business, user, spatial and temporal workload factors, policies related to expected performance and actions when it deviates based on KPIs from the 4G and 5G network. - - c) Develop and train AI/ML models with the help of SMO functions for the Near-RT RIC to predict the short-term traffic demand for 4G and 5G network based on near-real-time metrics from RAN. Deployment of these ML model over O1 and xApps over O2 to the Near-RT RIC. - - d) Receive policy feedback from Near-RT RIC and update policy and re-train ML models whenever required. -- 2) Near-RT RIC: - - a) Support deployment, execution, and ability to update DSS xApps from Non-RT RIC. - - b) Support interpretation of policies related to RAT specific resource allocation. - - c) Translate RAT specific SLA policy to configuration, control, and data subscription over E2 interface to E2 nodes (O-CU, O-DU). - - d) Share resource allocation performance and policy feedback report with Non-RT RIC for further evaluation and optimization over O1/A1. -- 3) RAN: - - a) Support discovery of DSS related configuration of E2 nodes over E2 interface. - - b) Share the data collection over O1 interface. - - c) Support resource management related metrics collection over E2 interface. - - d) Support control and policy enforcement from Near-RT RIC over E2 interface. - -### 4.11.3 Solutions - -#### 4.11.3.1 Dynamic spectrum sharing for 4G and 5G - -The context of the dynamic spectrum sharing for 4G and 5G is captured in table 4.11.3.1-1. - -**Table 4.11.3.1-1: Dynamic spectrum sharing for 4G and 5G** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Enable operators to dynamically share spectrum in the existing 4G deployment with 5G systems, based on the dynamic loads of both networks and resource sharing policies. | | -| Actors and Roles | Non-RT RIC: Spectrum resource sharing policy function. | | - -| Use Case Stage | Evolution / Specification | <> | -|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| |

Near-RT RIC: Executes resource sharing models and algorithms, translating RAT specific policy to configuration, control and data subscription over E2 interface with RAN.

RAN: Executes resource sharing enforcement rules and policies, collects and reports RAN statistics and performance over E2 and O1.

| | -| Assumptions |

All relevant functions and components are instantiated. DSS xApps are deployed over O1 with initial configuration.

A1, E2 interface connectivity is established with Non-RT RIC and RAN respectively.

Data report, policy and control subscription established on E2 interface.

| | -| Pre-conditions |

Network is operational.

SMO has established the data collection and sharing interface with Non-RT RIC.

Non-RT RIC analyzes the historical data from RAN, develops, trains with help of SMO functions and deploys the relevant AI/ML models or algorithm as xApps to the Near-RT RIC.

| | -| Begins when | Operator specified trigger condition or event is detected. | | -| Step 1 (M) | Near-RT RIC collects DSS related RAN function capabilities and configuration parameters from RAN over E2 interface. | | -| Step 2 (M) | Non-RT RIC communicates DSS relevant policies to the Near-RT RIC over the A1 interface. | | -| Step 3 (M) | Near-RT RIC communicates RAT specific DSS relevant configuration, control policies to RAN over the E2 interface. | | -| Step 4 (M) | RAN deploys the configuration and control policies received from the Near-RT RIC over the E2 interface. | | -| Step 5 (M) | Near-RT RIC collects relevant observability data from RAN, executes xApp and outputs the optimal resource allocation and cell level resource scheduling decisions to RAN over E2 and policy feedback to Non-RT RIC over A1. | | -| Step 6 (M) | RAN deploys the updated control policies received from the Near-RT RIC over the E2 interface and continues reporting data to SMO over O1 and E2 as configured. | | -| Step 7 (M) | Non-RT RIC adjusts the policy based on PM data from SMO and feedback from Near-RT RIC. | | -| Step 8 (M) | Non-RT RIC updates the resource sharing policy to Near-RT RIC over A1. | | -| Step 9 (O) | Non-RT RIC re-trains/updates the AI/ML model with new data and performance, and deploys the new model or new model configurations to Near-RT RIC. | | -| 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 monitors loads and relevant KPI performance metrics of eNB/gNB to observe the resource sharing efficiency and sets up new policies based on the metrics and business needs.

Near-RT RIC executes the resource sharing model or algorithm. RAN operates with the scheduling guidance from RIC and reports performance data to RIC.

| | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "Service Management and Orchestration" #gold - participant "SMO Functions" as SMO - Boundary Collector - participant "Non-RT RIC\nDSS/RAT APP" as non -End box - -Box "O-RAN" #lightpink - Participant RIC as "Near-RT RIC\nDSS/RAT APP" - Participant E2N1 as "E2 Node RAT1\n (4G) " - Participant E2N2 as "E2 Node RAT2\n (5G) " -End box - -SMO -> non: <> DSS Policies (service requirement, region) -Collector <- RIC: <> DSS related data report -Collector <- E2N1: <> DSS related data report -Collector <- E2N2: <> DSS related data report - -Collector -> non: <> DSS related Data for model development -non -> non: Resource prediction model development/training -non -> SMO: <> Publish trained model -SMO -> RIC: <> Deploy trained model -RIC <- E2N1: <> Service update: RAN configuration and operation parameters -RIC <- E2N2: <> Service Update: RAN configuration and operation parameters - -``` - -``` - -non -> RIC: <> Policies: Cell site identity, DSS band & modality, static/dynamic, -\nRAT SLA requirement, slice priority - -RIC -> E2N1: <> Subscription/Policy/Control: DSS RAT Configuration -\nBand, UL/DL, -semi-static/dynamic configuration resource apportionment - -RIC -> E2N2: <> Subscription/Policy/Control: DSS RAT Configuration -\nBand, UL/DL, -semi-static/dynamic configuration resource apportionment - -loop - - RIC <- E2N1: <> report: load, performance, mobility, scheduling bitmap - RIC <- E2N2: <> report: load, performance, mobility, scheduling bitmap - rnote over RIC: Model & Algorithm Execution - RIC -> E2N1: <> Control/policy: 1) Resource configuration 2) scheduling -coordination - RIC -> E2N2: <> Control/policy: 1) Resource configuration 2) scheduling -coordination - - non <- RIC: <>Policy feedback: right/under/over provisioning - Collector <- E2N1: <> DSS related data report - Collector <- E2N2: <> DSS related data report - Collector -> non: <> DSS related Data - - rnote over non - - Monitoring, evaluation and Policy adjustment - - endrnote - - non -> RIC: <> Updated sharing policies - -group opt - - non-> non : Model re-training / update - - non -> SMO: <> Publish re-trained model - SMO -> RIC: <> Deploy re-trained model - -end - -end loop - -@enduml - -``` - -The flow diagram of the dynamic spectrum sharing for 4G and 5G is given in figure 4.11.3.1-1. - -![Sequence diagram for Dynamic spectrum sharing for 4G and 5G. Lifelines: SMO Functions, Collector, Non-RT RIC DSS/RAT APP, Near-RT RIC DSS/RAT APP, E2 Node RAT1 (4G), E2 Node RAT2 (5G). The diagram shows model development, policy deployment, and a loop for monitoring and policy adjustment.](7e12e1e0d03a03790d2e9d74c3454bff_img.jpg) - -``` - -sequenceDiagram - participant SMO as SMO Functions - participant C as Collector - participant NRT as Non-RT RIC DSS/RAT APP - participant NRTT as Near-RT RIC DSS/RAT APP - participant E2_4G as E2 Node RAT1 (4G) - participant E2_5G as E2 Node RAT2 (5G) - - Note left of NRT: Service Management and Orchestration - Note right of E2_5G: O-RAN - - 1->>NRT: <> DSS Policies (service requirement, region) - NRT-->>C: 2 <> DSS related data report - C-->>NRT: 3 <> DSS related data report - NRT-->>C: 4 <> DSS related data report - C-->>NRT: 5 <> DSS related Data for model development - Note right of NRT: Resource prediction model development/training - NRT-->>C: 6 Resource prediction model development/training - Note left of NRT: <> Publish trained model - NRT-->>C: 7 <> Publish trained model - C-->>NRT: 8 <> Deploy trained model - Note right of NRT: <> Policies: Cell site identity, DSS band & modality, static/dynamic, RAT SLA requirement, slice priority - NRT-->>C: 11 <> Policies: Cell site identity, DSS band & modality, static/dynamic, RAT SLA requirement, slice priority - Note right of NRT: 9 <> Service update: RAN configuration and operation parameters - NRT-->>E2_4G: 9 <> Service update: RAN configuration and operation parameters - Note right of NRT: 10 <> Service Update: RAN configuration and operation parameters - NRT-->>E2_5G: 10 <> Service Update: RAN configuration and operation parameters - Note right of NRT: 12 <> Subscription/Policy/Control: DSS RAT Configuration - Band, UL/DL, semi-static/dynamic configuration resource apportionment - NRT-->>E2_4G: 12 <> Subscription/Policy/Control: DSS RAT Configuration - Band, UL/DL, semi-static/dynamic configuration resource apportionment - Note right of NRT: 13 <> Subscription/Policy/Control: DSS RAT Configuration - Band, UL/DL, semi-static/dynamic configuration resource apportionment - NRT-->>E2_5G: 13 <> Subscription/Policy/Control: DSS RAT Configuration - Band, UL/DL, semi-static/dynamic configuration resource apportionment - - loop Loop - Note right of E2_4G: 14 <> report load, performance, mobility, scheduling bitmap - E2_4G-->>NRT: 14 <> report load, performance, mobility, scheduling bitmap - Note right of E2_5G: 15 <> report load, performance, mobility, scheduling bitmap - E2_5G-->>NRT: 15 <> report load, performance, mobility, scheduling bitmap - - Note right of NRT: Model & Algorithm Execution - Note right of NRT: 16 <> Control(policy: 1) Resource configuration 2) scheduling coordination - NRT-->>E2_4G: 16 <> Control(policy: 1) Resource configuration 2) scheduling coordination - Note right of NRT: 17 <> Control(policy: 1) Resource configuration 2) scheduling coordination - NRT-->>E2_5G: 17 <> Control(policy: 1) Resource configuration 2) scheduling coordination - - Note right of NRT: 18 <> Policy feedback: right/under/over provisioning - NRT-->>C: 18 <> Policy feedback: right/under/over provisioning - C-->>NRT: 19 <> DSS related data report - NRT-->>C: 20 <> DSS related data report - C-->>NRT: 21 <> DSS related Data - - Note right of NRT: Monitoring, evaluation and Policy adjustment - Note right of NRT: 22 <> Updated sharing policies - NRT-->>C: 22 <> Updated sharing policies - - opt Model re-training / update - Note right of NRT: 23 Model re-training / update - NRT-->>C: 23 Model re-training / update - Note left of NRT: <> Publish re-trained model - NRT-->>C: 24 <> Publish re-trained model - C-->>NRT: 25 <> Deploy re-trained model - end - end - -``` - -Sequence diagram for Dynamic spectrum sharing for 4G and 5G. Lifelines: SMO Functions, Collector, Non-RT RIC DSS/RAT APP, Near-RT RIC DSS/RAT APP, E2 Node RAT1 (4G), E2 Node RAT2 (5G). The diagram shows model development, policy deployment, and a loop for monitoring and policy adjustment. - -Figure 4.11.3.1-1: Dynamic spectrum sharing for 4G and 5G flow diagram - -### 4.11.4 Required data - -Multiple observability data from RAN need to be reported to SMO, Non-RT RIC and Near-RT RIC for DSS to operate. The required data for DSS use case is captured in table 4.11.4-1. - -Table 4.11.4-1: Required data for DSS use case - -| Category | Parameters / Measurements | RAT | Source / Interface | Reference | -|--------------------------------------------------|--------------------------------------------------------------------------------------|-------|--------------------|-------------------------------------------| -| 4G/5G DSS configuration and operation parameters | Geography location (e.g., cell site) | 4G/5G | External server | | -| | DSS modality (static, semi-static (MBSFN), dynamic (sub-frame level)) | 4G/5G | E2 | 3GPP TS 38.211 [13], 3GPP TS 38.213 [14] | -| | Cell configuration information (e.g., FDD/TDD, band, signaling/RS allocation bitmap) | 4G/5G | E2 | 3GPP TS 36.423 [30], 3GPP TS 38.211 [13], | - -| Category | Parameters / Measurements | RAT | Source / Interface | Reference | -|----------------------------------------|----------------------------------------------------------------------------|-------|--------------------|------------------------------------------------------------------------------------------------------| -| | | | | 3GPP TS 38.213 [14] | -| 4G/5G scheduling information | Physical resource block used/reserved/requested/blocked bitmap information | 4G/5G | E2 | 3GPP TS 36.423 [30] | -| 4G/5G cell load statistics | Number of active UEs (total, UL/DL, per QCI) | 4G | E2 and O1 | 3GPP TS 36.314 [31] | -| | Mean/Max number of active UEs (DL/UL, total, per DRB(mapped 5QI)) | 5G | E2 and O1 | 3GPP TS 38.314 [32],
3GPP TS 32.425 [33] | -| | Traffic demand/buffer size (total, per QCI/5QI) | 4G/5G | E2 and O1 | | -| | PRB usage (DL, UL, total, per QCI/5QI) | 4G/5G | E2 and O1 | 3GPP TS 36.314 [31],
3GPP TS 36.423 [30],
3GPP TS 28.552 [6] | -| | PDCCH CCE usage | 4G/5G | E2 and O1 | 3GPP TS 36.423 [30] | -| | RRC connection number | 5G | E2 and O1 | 3GPP TS 28.552 [6],
3GPP TS 32.425 [33] | -| 4G/5G QoS configuration and parameters | QoS classes | 4G/5G | E2 | 3GPP TS 23.501 [2] (5G),
3GPP TS 36.300 [34],
3GPP TS 23.401 [35],
3GPP TS 23.203 [36] (4G) | -| | Slice types | 5G | E2 | 3GPP TS 23.501 [2] | -| UE performance statistics | Scheduled IP throughput (DL, UL, per QCI) | 4G | E2 and O1 | 3GPP TS 36.314 [31] | -| | Data volume (DL/UL per CQI) | 4G | E2 and O1 | 3GPP TS 36.314 [31] | -| | UL/DL PDCP SDU data volume | 5G | E2 and O1 | 3GPP TS 28.552 [6] | -| | PDCP packet delay DL/UL per CQI/QCI | 4G/5G | E2 and O1 | 3GPP TS 36.314 [31] (4G) | -| UE mobility statistics | RSRP/RSRQ/SINR/RSSI | 4G/5G | E2 and O1 | 3GPP TS 36.214 [37], | - -| Category | Parameters / Measurements | RAT | Source / Interface | Reference | -|----------|---------------------------|-------|--------------------|---------------------| -| | | | | 3GPP TS 36.331 [38] | -| | UE location information | 45/5G | External Server | | -| | UE capability | 4G/5G | E2 and O1 | 3GPP TS 36.331 [38] | - -## 4.12 NSSI resource allocation optimization - -This use case provides the background, motivation, description, and requirements for the NSSI resource allocation optimization use case, allowing operators to optimize the allocation resources to NSSI(s) with wide range service requirements. - -### 4.12.1 Background and goal of the use case - -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 the various services. However, as eMBB, URLLC, and mMTC services in 5G are typically realized as NSI (Network Slice instance). Therefore, 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 time 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, 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. - -The NSSI resource allocation optimization on the Non-RT RIC is shown in figure 4.12.1-1, and can consist of the following steps: - -- Monitoring: monitor the radio network(s) by collecting data via the O1 interface, for example including the following performance measurements that are measured on per S-NSSAI (3GPP TS 28.552 [6] shall apply): - - Mean DL PRB used for data traffic (3GPP TS 28.552 [6], clause 5.1.1.2.5 shall apply) - - Mean UL PRB used for data traffic (3GPP TS 28.552 [6], clause 5.1.1.2.7 shall apply) - -- Average DL UE throughput in gNB (3GPP TS 28.552 [6], clause 5.1.1.3.1 shall apply) -- Average UL UE throughput in gNB (3GPP TS 28.552 [6], clause 5.1.1.3.3, shall apply) -- Number of PDU sessions requested to setup (3GPP TS 28.552 [6], clause 5.1.1.5.1 shall apply) -- Number of PDU sessions successfully setup (3GPP TS 28.552 [6], clause 5.1.1.5.2 shall apply) -- Distribution of DL UE throughput in gNB (3GPP TS 28.552 [6], clause 5.1.1.3.2 shall apply) -- Distribution of UL UE throughput in gNB (3GPP TS 28.552 [6], clause 5.1.1.3.4 shall apply) -- Number of DRBs successfully setup (3GPP TS 28.552 [6], clause 5.1.1.10.2 shall apply) - -NOTE 1: The above measurements are indicative and are subject to change based on the progress of this use case in O-RAN. - -NOTE 2: Monitoring of the measurements related to O-Cloud (or transport network) that can be required for NSSI resource optimization is not defined in the present document. - -- 2) Analysis & decision: consisting of the following steps: - - 2a. Utilize AI/ML models to analyze 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 (3GPP TS 28.541 [5] shall apply, etc.) for the RAN NFs (E2 nodes included in the respective NSSI at the given time, and location. -- 3) Execution: execute the actions to reallocate the NSSI resources that include: - - 3a. Re-configure the NSSI attributes, including RRMPolicyRatio IOC (3GPP TS 28.541 [5] shall apply) via the OAM Functions in SMO which uses O1 interface to configure the E2 nodes. - - 3b. Update the cloud resources via the O2 interface. - -![Diagram illustrating the realization of NSSI resource allocation optimization over Non-RT RIC. The diagram shows a hierarchy of O-RAN components. At the top is the Service management & Orchestration Framework, which contains the Non-RT RIC. Inside the Non-RT RIC is the NSSI Resource Allocation Optimization function. Below the Non-RT RIC is the Near-RT RIC. Below the Near-RT RIC is a box labeled 'Network functions' containing O-CU-UP, O-CU-CP, O-DU, and O-RU. At the bottom is the O-Cloud. Arrows indicate the flow of information: 1. monitoring from O-RU to NSSI Resource Allocation Optimization; 2. analysis & decision from NSSI Resource Allocation Optimization to O-Cloud M&O; 3.a. execution from NSSI Resource Allocation Optimization to Near-RT RIC; 3.b. execution from NSSI Resource Allocation Optimization to O-Cloud M&O. Interfaces are labeled: O2 between O-Cloud and O-Cloud M&O; A1 between Non-RT RIC and Near-RT RIC; O1 between Non-RT RIC and Network functions; E2 between Near-RT RIC and Network functions; E1 between O-CU-UP and O-CU-CP; F1-U and F1-C between O-CU-CP and O-DU; Open Fronthaul interface between O-DU and O-RU.](d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg) - -Diagram illustrating the realization of NSSI resource allocation optimization over Non-RT RIC. The diagram shows a hierarchy of O-RAN components. At the top is the Service management & Orchestration Framework, which contains the Non-RT RIC. Inside the Non-RT RIC is the NSSI Resource Allocation Optimization function. Below the Non-RT RIC is the Near-RT RIC. Below the Near-RT RIC is a box labeled 'Network functions' containing O-CU-UP, O-CU-CP, O-DU, and O-RU. At the bottom is the O-Cloud. Arrows indicate the flow of information: 1. monitoring from O-RU to NSSI Resource Allocation Optimization; 2. analysis & decision from NSSI Resource Allocation Optimization to O-Cloud M&O 3.a. execution from NSSI Resource Allocation Optimization to Near-RT RIC; 3.b. execution from NSSI Resource Allocation Optimization to O-Cloud M&O. Interfaces are labeled: O2 between O-Cloud and O-Cloud M&O A1 between Non-RT RIC and Near-RT RIC; O1 between Non-RT RIC and Network functions; E2 between Near-RT RIC and Network functions; E1 between O-CU-UP and O-CU-CP; F1-U and F1-C between O-CU-CP and O-DU; Open Fronthaul interface between O-DU and O-RU. - -Figure 4.12.1-1: The realization of NSSI resource allocation optimization over Non-RT RIC - -For association of resource quota policies for the RAN NFs (E2 nodes) per NSSI or group of NSSIs, RRMPolicyRatio IOC (realization of abstract IoC RRMPolicy\_) is currently being specified in 3GPP TS 28.541 [5] which allows definition of maximum, minimum and dedicated values for the percentage of resources to be used per RRMPolicyMemberList – that is group of members with specific plmnID and sNSSAI (applied at NRCellIDU, NRCellICU, GNBDFFunction, GNBCUCPFunction or in GNBCUUPFunction) via RRMPolicyManagedEntity. - -### 4.12.2 Entities/resources involved in the use case - -- 1) SMO: - - a) Pre-provision the default NSSI resource quota policy as constraint for NSSI resource allocation optimization. This information is optionally used by the Non-RT RIC in case the resource quota that needs to be allocated per slice is not specified during the slice creation and for conflict resolution at the time of resource scarcity. -- 2) Non-RT RIC: - - a) Collect the performance measurements related to NSSI resource usage from the O-RAN nodes via the O1 interface. - - b) Train the AI/ML model based on the analysis of historical performance measurements, to predict of the traffic demand patterns of NSSI at different times and locations. - - c) Determine the time/date and locations (i.e. which O-RAN nodes) to add or reduce the resources (e.g. capacity, VNF resources, slice subnet attributes (3GPP TS 28.541 [5] shall apply), RRMPolicyRatio IOC, etc.) for a given NSSI based on inference. - - d) Perform the following action(s) to optimize the NSSI resource allocation, at the time determined by the model. - - i. Re-configure the NSSI attributes via the O1 interface. - - ii. Update the cloud resources via the O2 interface. -- 3) RAN nodes (O-CU-CP, O-CU-UP, O-DU, O-RU): - - a) Support the performance measurement collection with required granularity over O1 interface. - - b) Support the configuration related to the NSSI resource allocation update over O1 interface. - -### 4.12.3 Solutions - -#### 4.12.3.1 NSSI resource allocation optimization - -The context of the NSSI resource allocation optimization is captured in table 4.12.3.1-1. - -**Table 4.12.3.1-1: NSSI resource allocation optimization** - -| Use Case stage | Evolution/Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To automatically optimize the NSSI resource allocation by leveraging the AI/ML model that was trained via the analysis of performance measurements collected from the RAN nodes. | | -| Actors and Roles | SMO: Pre-Provision the default resource quota policy as constraint for resource allocation optimization and monitor runtime context change.
Non-RT RIC: Analysis of performance measurements and AI/ML model training
RAN nodes (O-CU-CP, O-CU-UP, O-DU, O-RU): performance measurements collection and configuration changes execution.
O-Cloud M&O: The cloud resources modification via the O2 interface.
OAM functions: Part of SMO which manages the O1 based OAM functionality.
O-Cloud: Manages virtualization infrastructure and virtualized resources. | | -| Assumptions | - All relevant functions and components are instantiated.
- Non-RT RIC is able to receive performance measurements from RAN nodes via the O1 interface. | | - -| | | | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Pre-conditions |
  • - RAN is operational.
  • - OAM function is pre-provisioned with default NSSI resource quota policy - Non-RT RIC has been collecting the RAN performance measurements from RAN nodes.
| | -| Begins when | An AI/ML model has been trained based on the analysis of performance measurements predict of the traffic demand patterns of NSSI at different times and locations, resource quota per slice. | | -| Step 1 (M) | Non-RT RIC collects the RAN performance measurements from RAN nodes. | | -| Step 2 (M) |

i. Non-RT RIC utilizes the AI/ML models to analyze the measurements and predict future the traffic demand for each NSSI for a given time and location.

ii. Non-RT RIC determines the action based on model inference to update the NSSI resources that can include the following information:

  • a) the time/date
  • b) locations (e.g. gNB ID)
  • c) NSSI ID
  • d) slice subnet attributes
  • e) VNF resources update (e.g. scaling in/out)
  • f) NSSI resource quota policy to be enforced per slice over O1 interface
| | -| Step 3 (M) |

Non-RT RIC executes the action at the time determined by the model inference by performing the following operations:

  • a) Re-configure the slice subnet attributes, including RRMPolicyRatio IOC (3GPP TS 28.541 [5] shall apply) via the OAM functions in SMO which uses O1 interface to configure the E2 nodes.
  • b) Request O-Cloud M&O to update the O-Cloud resources via the O2 interface.

The execution of these steps is carried out by SMO based on the recommendation of the Non-RT RIC.

| | -| Ends when | All the steps identified above are successfully completed. | | -| Exceptions | One of the steps identified above fails. | | -| Post Conditions | Near-RT RIC continues monitoring the NSSI resource usages. | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "Service Management and Orchestration" #gold - participant "Non-RT RIC" as non - participant mo as "NFO" - -``` - -``` - -participant "OAM Functions" as oam End box - -Box "O-RAN" #lightpink - Participant e2 as "E2 nodes" - Participant ocloud as "O-Cloud" -End box - -oam->oam: Pre-provisioning of default\n NSSI Resource quota policy\n per slice -group **1** Monitoring - e2->oam: Collection of NSSI\n Performance Measurements\n via the O1 interface - oam->non: Collection of NSSI PM data\n via SMO internal interface -end - -group **2** Analysis - non->non: **2.i** Utilize the AI/ML model to predict the \ntraffic demand for each NSSI - \nfor a given time and location - non->non: **2.ii** Determine the action based on model inference \nto update the NSSI - resources -end - -group **3** Execution: executes the action at the time determined by the model inference - non->oam: **3.a** Re-configure the \nslice subnet attributes - oam->e2: Re-configure the slice subnet \nattributes via the O1 interface - non->mo: **3.b** Request NFO update - mo->ocloud: NFO Request O-Cloud\n to update the\n VNF resources\n (e.g. scale in/out)\n - via the O2 interface - ocloud->ocloud: Request to update \n the VNF resources\n (e.g. scale in/out) -end - -@enduml - -``` - -The flow diagram of the NSSI resource allocation optimization is given in figure 4.12.3.1-1. - -![NSSI resource allocation optimization flow diagram showing interactions between Service Management and Orchestration (Non-RT RIC, NFO, OAM Functions) and O-RAN (E2 nodes, O-Cloud).](c05763eff20551449de1eac378fed769_img.jpg) - -The diagram illustrates the NSSI resource allocation optimization flow, organized into three main phases: - -- Pre-provisioning:** OAM Functions send a message to E2 nodes: "Pre-provisioning of default 1 NSSI Resource quota policy per slice". -- 1 Monitoring:** - - E2 nodes send "Collection of NSSI 2 Performance Measurements via the O1 interface" to OAM Functions. - - OAM Functions send "Collection of NSSI PM data via SMO internal interface 3" to Non-RT RIC. -- 2 Analysis:** - - Non-RT RIC performs "2.i Utilize the AI/ML model to predict the 4 traffic demand for each NSSI for a given time and location". - - Non-RT RIC performs "2.ii Determine the action based on model inference to update the NSSI resources 5". -- 3 Execution: executes the action at the time determined by the model inference:** - - Non-RT RIC sends "3.a Re-configure the slice subnet attributes 6" to OAM Functions. - - OAM Functions send "7 Re-configure the slice subnet attributes via the O1 interface" to E2 nodes. - - Non-RT RIC sends "8 3.b Request NFO update" to NFO. - - NFO sends "NFO Request O-Cloud to update the 9 VNF resources (e.g. scale in/out) via the O2 interface" to O-Cloud. - - O-Cloud sends "Request to update 10 the VNF resources (e.g. scale in/out)" to E2 nodes. - -NSSI resource allocation optimization flow diagram showing interactions between Service Management and Orchestration (Non-RT RIC, NFO, OAM Functions) and O-RAN (E2 nodes, O-Cloud). - -Figure 4.12.3.1-1: NSSI resource allocation optimization flow diagram - -### 4.12.4 Required data - -The measurement counters, as specified in 3GPP TS 28.552 [6], which are measured on per S-NSSAI include: - -- Mean DL PRB used for data traffic (3GPP TS 28.552 [6], clause 5.1.1.2.5 shall apply) -- Mean UL PRB used for data traffic (3GPP TS 28.552 [6], clause 5.1.1.2.7 shall apply) -- Average DL UE throughput in gNB (3GPP TS 28.552 [6], clause 5.1.1.3.1 shall apply) -- Average UL UE throughput in gNB (3GPP TS 28.552 [6], clause 5.1.1.3.3 shall apply) -- Number of PDU sessions requested to setup (3GPP TS 28.552 [6], clause 5.1.1.5.1 shall apply) -- Number of PDU sessions successfully setup (3GPP TS 28.552 [6], clause 5.1.1.5.2 shall apply) -- Distribution of DL UE throughput in gNB (3GPP TS 28.552 [6], clause 5.1.1.3.2 shall apply) -- Distribution of UL UE throughput in gNB (3GPP TS 28.552 [6], clause 5.1.1.3.4 shall apply) - -- Number of DRBs successfully setup (3GPP TS 28.552 [6], clause 5.1.1.10.2 shall apply) - -NOTE: The above measurements are indicative and are subject to change based on the progress of this use case in O-RAN. The monitoring of the measurements related to O-Cloud (or transport network) that can be required for NSSI resource optimization is not defined in the present document. - -## 4.13 Local indoor positioning in RAN - -This use case provides the background and motivation for the O-RAN architecture to support local indoor positioning. - -### 4.13.1 Background and goal of the use case - -Real-time indoor positioning based on cellular network has aroused attention with the development of 5G vertical industries, individuals and operators. NR positioning is introduced by 3GPP Rel.16. The Location Management Function (LMF) resides in core network request the NG-RAN node to report positioning measurements, which is used by LMF to compute the location of UE. The messages between LMF and the NG-RAN need the AMF to route transparently. However, this long route messages between the NG-RAN node and centralized LMF can suffer network jitters and leads to un-real-time UE location results. - -The main objective is to ensure local positioning be supported within the O-RAN architecture and its open interfaces. 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. The local indoor positioning results can be acquired via positioning xApp to support positioning applications (e.g., indoor navigation, electric security fence, etc.). - -### 4.13.2 Entities/resources involved in the use case - -- 1) Non-RT RIC: - - a) Retrieve necessary positioning-related indicators (e.g., RSSI, labeled user location by manual or by minimal drive test, etc.) from positioning measurement report or network level measurement report or enrichment information from SMO (can acquire data from application). The data is for constructing/training relevant AI/ML model that will be deployed in Near-RT RIC to assist in the position computation function. - - b) Training of potential ML models for real-time positioning optimization, which can be used to compute the position, correct positioning errors, and predict motion. - - c) Send policies/intents to Near-RT RIC to drive the positioning optimization at RAN level. -- 2) Near-RT RIC: - - a) Support selection of positioning algorithms (e.g., according to QoS requirements, etc.). - - b) Support the calculation of positioning results based on the measurements from RAN. - - c) Support update of AI/ML models from Non-RT RIC. - - d) Support execution of the AI/ML models from Non-RT RIC, e.g., positioning result calculation. - - e) Sending positioning results to Non-RT RIC for evaluation and optimization. -- 3) RAN: - - a) Support positioning related measurement report over E2 interface. - - b) Support positioning related measurement report over O1 interface. -- 4) Application server: - - a) Request/subscribe RAN analytics information from Near-RT RIC. - - b) Support positioning related enrichment information (e.g., labeled user location by manual or by minimal drive test, etc.) to SMO. - -### 4.13.3 Solutions - -#### 4.13.3.1 Local indoor positioning in RAN (1) - -The context of the local indoor positioning in RAN (1) is captured in table 4.13.3.1-1. - -**Table 4.13.3.1-1: Local indoor positioning in RAN (1)** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Expose positioning results to external applications. | | -| Actors and Roles | Near-RT RIC, SMO, application server | | -| Assumptions | All relevant functions and components are instantiated. | | -| Pre-conditions | Editor's note: Security related procedure is not defined in the present document. | | -| Begins when | The application server wants to request/subscribe RAN positioning results of target UE. | | -| Step 1 (M) | Application server sends positioning request of target UE to Near-RT RIC or subscribes positioning results from Near-RT RIC to get periodic or event triggered position reporting. | | -| Step 2 (M) | Near-RT RIC receives the request or subscription from application server and requests or subscribes measurements to RAN through E2 interface. The Near-RT RIC selects the positioning algorithm based on the request or the measurement data from RAN. | | -| Step 3 (M) | RAN reports the measurements to Near-RT RIC according to the request or subscription. | | -| Step 4 (M) | Near-RT RIC calculates the positioning results based on the measurement report from RAN, using the selected positioning algorithm. | | -| Step 5 (M) | Near-RT RIC sends the response or notification command to expose radio performance analytics towards application server. | | -| Ends when | Application server gets response or sends subscription deletion toward the Near-RT RIC. | | -| Exceptions | None identified. | | - -The flow diagram of the local indoor positioning in RAN (1) is given in figure 4.13.3.1-1. - -![Sequence diagram for local indoor positioning in RAN (1). The diagram is divided into three vertical zones: Service Management and Orchestration (yellow), O-RAN (pink), and External (light blue). In the Service Management zone, there are two instances of 'Collector' and 'Non-RT RIC'. In the O-RAN zone, there are two instances of 'Near-RT RIC' and 'O-CU/O-DU'. In the External zone, there are two instances of 'Application Server'. The sequence of messages is: 1. Application Server sends 'Positioning Result Request/Subscribe' to the top Near-RT RIC. 2. Near-RT RIC sends '<> Positioning measurement report Request' to the top O-CU/O-DU. 3. O-CU/O-DU sends '<> Positioning measurement report Response' back to the top Near-RT RIC. 4. Near-RT RIC performs 'Positioning result calculation'. 5. Near-RT RIC sends 'Positioning Result Response/Notify' to the Application Server.](9cf678d634932a43b7f6582878972a5d_img.jpg) - -Sequence diagram for local indoor positioning in RAN (1). The diagram is divided into three vertical zones: Service Management and Orchestration (yellow), O-RAN (pink), and External (light blue). In the Service Management zone, there are two instances of 'Collector' and 'Non-RT RIC'. In the O-RAN zone, there are two instances of 'Near-RT RIC' and 'O-CU/O-DU'. In the External zone, there are two instances of 'Application Server'. The sequence of messages is: 1. Application Server sends 'Positioning Result Request/Subscribe' to the top Near-RT RIC. 2. Near-RT RIC sends '<> Positioning measurement report Request' to the top O-CU/O-DU. 3. O-CU/O-DU sends '<> Positioning measurement report Response' back to the top Near-RT RIC. 4. Near-RT RIC performs 'Positioning result calculation'. 5. Near-RT RIC sends 'Positioning Result Response/Notify' to the Application Server. - -Figure 4.13.3.1-1: Local indoor positioning in RAN (1) flow diagram - -#### 4.13.3.2 Local indoor positioning in RAN (2) - -The context of the local indoor positioning in RAN (2) is captured in table 4.13.3.2-1. - -Table 4.13.3.2-1: Local indoor positioning in RAN (2) - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Expose positioning results to external applications. | | -| 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 | Positioning 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 wants to request/subscribe RAN positioning results of target UE. | | -| Step 1 (M) | Application server sends positioning request of target UE to Near-RT RIC or subscribes positioning results from Near-RT RIC to get periodic or event triggered position reporting. | | -| Step 2 (M) | Near-RT RIC receives the request or subscription from application server and requests or subscribes measurements to RAN through E2 interface. The Near-RT RIC selects the positioning algorithm based on the request or the measurement data from RAN and can update the positioning related models from Non-RT RIC. | | -| Step 3 (M) | RAN reports the measurements to Near-RT RIC according to the request or subscription. | | -| Step 4 (M) | Near-RT RIC calculates the positioning results based on the positioning report from RAN, using the selected positioning algorithm. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 5 (M) | Near-RT RIC sends the response or notification command to expose radio performance analytics towards application server. Near-RT RIC can also pass the positioning results to the Non-RT RIC for further analysis. | | -| Ends when | Application server gets response or sends subscription deletion toward the Near-RT RIC. | | -| Exceptions | None identified. | | - -The flow diagram of the local indoor positioning in RAN (2) is given in figure 4.13.3.2-1. - -![Sequence diagram for local indoor positioning in RAN (2). Lifelines: Service Management and Orchestration (SMO) with Non-RT RIC and Collectors; O-RAN with Near-RT RIC and O-CU/O-DU; External with Application Server. The process involves data collection, model training, model deployment, positioning request, measurement reporting, result calculation, and final response/feedback.](9874e3ac6f14360133f8e1674f79824f_img.jpg) - -``` - -sequenceDiagram - participant SMO as Service Management and Orchestration - subgraph SMO - direction TB - C1[Collector] - NRT1[Non-RT RIC] - C2[Collector] - NRT2[Non-RT RIC] - end - subgraph O-RAN - direction TB - NRT3[Near-RT RIC] - OCU[O-CU/O-DU] - end - participant AS as External Application Server - - Note left of SMO: Enrichment information collection - SMO->>O-RAN: <> Data Collection - SMO->>O-RAN: <> Data Collection - SMO->>O-RAN: Retrieval of RAN and non-RAN data - Note right of NRT1: Training of AI/ML models - Note right of NRT1: Deploy internal AI/ML models - SMO->>O-RAN: <> Deploy AI/ML models - Note right of OCU: Positioning Result Request/Subscribe - OCU->>NRT3: <> Positioning measurement report Request - NRT3->>OCU: <> Positioning measurement report Response - Note right of NRT3: Positioning result calculation - Note right of NRT3: ML model inference - Note right of NRT3: Positioning Result Response/Notify - OCU->>AS: Positioning Result Response/Notify - Note right of NRT3: Positioning Result feedback - NRT3->>SMO: Positioning Result feedback - -``` - -Sequence diagram for local indoor positioning in RAN (2). Lifelines: Service Management and Orchestration (SMO) with Non-RT RIC and Collectors; O-RAN with Near-RT RIC and O-CU/O-DU; External with Application Server. The process involves data collection, model training, model deployment, positioning request, measurement reporting, result calculation, and final response/feedback. - -Figure 4.13.3.2-1: Local indoor positioning in RAN (2) flow diagram - -### 4.13.4 Required data - -Multi-dimensional data are expected to be retrieved by Non-RT RIC for AI/ML model training and policies/intents generation. - -- 1) Network level measurement report, including UE level radio channel information, mobility related metrics, e.g., RSRP, RSSI, etc. -- 2) Positioning measurement report, including UE level E-CID, OTDOA, UTDOA, TOA, RSSI, AOA, etc. -- 3) Enrichment information (optional) collected from SMO (can acquire data from application), can including labeled user location by manual or by minimal drive test, etc. - -Near-RT RIC required data to select the positioning algorithm and calculate the positioning results. - -- 1) Positioning measurement report, including UE level E-CID, OTDOA, UTDOA, TOA, RSSI, AOA, etc. -- 2) Performance requirements in positioning requests (optional) such as QoS. - -#### 4.13.4.1 RAN analytics information - -Radio performance analytics data are expected to be exposed by Near-RT RIC to application server. - -- 1) UE positioning results, including location coordinates, coordinate system, position methods used (in the case of success indication provided), failure cause (in the case of failure indication provided), achieved location QoS accuracy (optional). -- 2) Velocity estimation (optional). - -## 4.14 Massive SU/MU-MIMO grouping optimization - -Void - -## 4.15 O-RAN signalling storm protection - -This use case provides the background, motivation, and requirements for the O-RAN signaling storm protection use case, allowing protecting the mobility network against signaling storms initiated by devices. - -### 4.15.1 Background and goal of the use case - -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-RT RIC xApps and Non-RT RIC rApps. - -Currently, the main defense mechanism standardized in 3GPP 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 with 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 under certain conditions 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 vulnerabilities in a large set of these devices remotely can cause an attach storm that could 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 vulnerable devices connected to the same carrier network; the network carrier will not be able to stop this attack without intelligent and fine-grained controls to act against a certain patterns of behavior. - -Fortunately detecting these aggressive devices is possible as their behavior 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. - -The goal of this use case is utilizing O-RAN to detect and mitigate signaling storms DDoS quick and as close to the network edge, thus minimizing affected network nodes. The Near-RT RIC would detect these signaling storms by analyzing signaling events from RAN nodes it controls. When such a storm is detected the Near-RT RIC creates fine grained filters, which cover the aggressive UEs that cause the storm. These UEs registration requests will then be blocked/throttled while the behaving UEs will continue to get service as usual. In some cases, the attack can be spread - -across many locations. It could be that the volume of signaling per location has not crossed a critical threshold but the moderate increase in many locations do cause an overload of central nodes such as the network core elements. In this case a network-wide view is required; thus, the Non-RT performs the network-wide analysis and in the case of a network signaling storm, it pushes policies to the local Near-RT RIC to adjust detection parameters to reduce the moderate increase of signaling from a set of one or more E2 nodes. This combined view of both Non-RT RIC and Near-RT RIC ensures quick reaction to local signaling storms as well as response to widely distributed attacks. - -While flows in this use case focus on the signaling storm scenario, they could be easily extended to include other attack scenarios both in terms of detection and mitigation. For example, the scenario where rogue devices report false CQI measurements that indicate high values while the real channel quality is poor. When exploited by attackers and applied to large set of devices this attack can cause to waste of radio resources and eventually to DoS. Detection of the attack can be achieved by analyzing anomalous CQI reports, or abnormal volume of NACK messages based on signaling messages. For mitigation actions either rejecting the rogue devices or limiting radio resources can be applied. - -### 4.15.2 Entities/resources involved in the use case - -- 1) Non-RT RIC in SMO domain: - - a) Maintains overall view of network wide phenomenon of signaling storms using signaling storm detection rApp. The detection of distributed signaling storms that spread over many geographical locations and are more difficult to be observed locally. This overall view is broken down by location and corresponding policies are pushed to specific instances of Near-RT RIC to respond to abnormal signaling activity in affected geographical areas, over the A1 interface. - - b) Uses enrichment data from non-RAN source (i.e., 5G core or probing framework) to maintain global view and support more accurate detection and classification of attacks. - - c) Utilizes AI/ML models in the signaling storm detection rApp that monitor network-level signaling behavior to support signaling anomalies detection. -- 2) Near-RT RIC in RAN domain: - - a) Monitors E2 interface for connection establishment messages and identifies abnormal levels of signaling activity using the signaling storm detection xApp. - - b) Signaling storm mitigation xApp utilizes policies over E2 to enforce appropriate mitigation action (e.g., reject, throttle, alert) over misbehaving UEs connection establishment. - - c) Signaling storm detection xApp utilizes AI/ML models that monitor cell-level signaling behavior to support signaling anomalies detection. - - d) Applies appropriate detection policy based on policies received from Non-RT RIC (e.g., false-positive levels, UE thresholds, throttling ratios). -- 3) E2 nodes in RAN domain: - - a) Support sending connection establishment messages over the E2 interface. - - b) Support control and policy enforcement from Near-RT RIC over E2 interface - -### 4.15.3 Solutions - -#### 4.15.3.1 Mode 1 – Local signaling storm protection policy - -The context of the local signaling storm protection policy is captured in table 4.15.3.1-1. - -**Table 4.15.3.1-1: Local signaling storm protection policy** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|----------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Detect localized signaling storms based on “default parameters” and apply policy to mitigate the attack. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Actors and Roles |

Near-RT RIC: Detection of local cell-level signaling storms; execution of mitigation policies and controls, maintenance of cell-level normal behavior models.

E2 nodes: Execute mitigation policies, collects and reports RAN signaling events and policy specific statistics over E2.

| | -| Assumptions |

All relevant functions and components are instantiated. Signaling storms detection and signaling storm mitigation xApps are deployed over E2 with initial configuration.

E2 interface connectivity is established with Non-RT RIC and RAN respectively.

Data report, policy and control subscription established on E2 interface.

| | -| Pre-conditions |

Network is operational.

SMO has established the data collection and sharing interface with Non-RT RIC.

Near-RT RIC already established relevant detection mechanisms of normal signaling behavior and adjusted detection parameters accordingly. Non-RT RIC analyzes the historical data from RAN, develops, trains with help of SMO functions and deploys the models or algorithm as part of the signaling storm detection xApp to the Near-RT RIC.

| | -| Begins when | Network is in normal state (attack is described later on). | | -| Step 1 (M) | Signaling storm detection xApp subscribes on connection establishment signaling messages report from the RAN over the E2 interface. | | -| Step 2 (M) | E2 node sends report to signaling storm detection xApp. | | -| Step 3 (M) | Near-RT RIC signaling storm detection xApp monitors reports to detect aggressive UEs that act with abnormal signaling. | | -| Steps 4-7 (M) | UEs send establish connection messages and E2 node accepts these requests. | | -| Step 8 (M) | E2 node sends a connection establishment reports. | | -| Step 9 (M) | Signaling storm detection xApp detects aggressive activity. | | -| Step 10 (M) | Signaling storm detection xApp updates signaling storm mitigation xApp. | | -| Step 11 (M) | Near-RT RIC signaling storm mitigation xApp creates a filter to block/throttle signaling messages from the aggressive UEs. Filter is applied in the E2 nodes as POLICY + REPORT to track filter activity. Near-RT RIC shall notify the Non-RT RIC to avoid conflicts. | | -| Step 12 (M) | Aggressive UE sends connection establishment message. | | -| Step 13 (M) | E2 node evaluate policy with respect to the connection establishment message. | | -| Step 14 (M) | E2 node rejects/throttles connection establishment request. | | -| Step 15 (M) | Near-RT RIC signaling storm mitigation xApp receives relevant signaling messages that the POLICY filter blocked/ throttled to track changes in attack | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | status and aggressive devices (list of UEs blocked, blocked signaling volume, trend). | | -| Step 16 (M) | Near-RT RIC signaling storm mitigation xApp is finds that some devices are no longer aggressive or no longer present. It decides to update filter by updating the E2 node POLICY. | | -| Step 17-19 (M) | Near-RT RIC signaling storm detection xApp detects a new set of aggressive devices and updates the signaling storm mitigation xApp, which updates the filter by updating the E2 node POLICY. | | -| Step 20-21 (M) | Near-RT RIC signaling storm mitigation xApp evaluates signaling level and decides that there is no more aggressive UE activity. The xApp removes the E2 node policy. | | -| Ends when | Attack is over and signaling messages level is back to normal. | | -| Exceptions | None identified. | | -| Post Conditions | Return to normal signaling activity monitoring (step 1). | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "Service Management and Orchestration" #gold - boundary "OAM Functions" as coll - participant "Non-RT RIC" as non -end box - -Box "O-RAN" #lightpink - Participant "Near-RT RIC Detection xApp" as det - Participant "Near-RT RIC Mitigation xApp" as mit - Participant "E2 Nodes" as ran -End box - -Box "External Enrichment Server" #lightcyan - Participant "Core Probing Framework" as ext -End box - -Participant UE as ue - -``` - -``` - -ext -> coll: EI's collection - -ran -> coll: <> alarms & metrics - -coll -> non: Signalling statistics - -group Signaling Storm Detection - - det -> ran: <> Subscription Request:REPORT{connection establishment messages} - ran -> det: <> Report: {connection establishment messages} - det -> det: Detect aggressive devices - ue -> ran: Establish connection request - ran -> ue: Establish connection accept - ue -> ran: Establish connection request - ran -> ue: Establish connection accept - ran -> det: < Report: {connection establishment messages} - det -> det: Detect aggressive devices - det -> mit: Decision to apply policy filter - mit -> ran: <> Subscribe REPORT+POLICY: {policy apply filter} - ue -> ran: Establish connection request - ran -> ran: Evaluate policy - ran -> ue: Establish connection reject - ran -> mit: <> Report: {connection establishment messages} - mit -> ran: <> Send Policy: {update policy filter - remove some UEs} - ran -> det: <> Report: {connection establishment messages} - det -> mit: Decision to apply policy filter - mit -> ran: <> Send Policy: {update policy filter - add some UEs} - ran -> mit: <> Report: {connection establishment messages} - mit -> ran: <> Send Policy: {Remove policy filter} - -end - -@enduml - -``` - -The flow diagram of the local signaling storm protection policy is given in figure 4.15.3.1-1. - -![O-RAN Alliance Logo](32d2216a419e1d11a63f930a6106c627_img.jpg) - -O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00 - -![Figure 4.15.3.1-1: Local signaling storm protection policy flow diagram](ed9323bc95c2008cce304ea1ebeebe8c_img.jpg) - -The sequence diagram illustrates the signaling storm protection policy flow. It involves the following entities: OAM Functions (Non-RT RIC) within SMO, Near-RT RIC Detection xApp, Near-RT RIC Mitigation xApp, E2 Nodes, Core Probing Framework, and UE. The flow includes initial data collection (EI's collection, alarms & metrics, signaling statistics), followed by a 'Signaling Storm Detection' block where E2 nodes report connection establishment messages. The Near-RT RIC detects aggressive devices and makes decisions to apply policy filters. Mitigation steps involve subscribing to reports with policy filters, evaluating policies, and sending policy updates to add or remove UEs from filters, eventually removing the policy filter when the storm is mitigated. - -Figure 4.15.3.1-1: Local signaling storm protection policy flow diagram - -**Figure 4.15.3.1-1: Local signaling storm protection policy flow diagram** - -### 4.15.3.2 Mode 1 – Local signaling storm protection insert-control (optional) - -The context of the local signaling storm protection insert-control is captured in table 4.15.3.2-1. - -**Table 4.15.3.2-1: Local signaling storm protection insert-control** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Detect localized signaling storms based on “default parameters” and apply control to mitigate the attack. | | -| Actors and Roles | Near-RT RIC: Detection of local cell-level signaling storms; execution of mitigation policies and controls, maintenance of cell-level normal behavior models.
E2 nodes: Execute UE level mitigation policies, collects and reports RAN signaling events and policy specific statistics over E2. | | -| Assumptions | All relevant functions and components are instantiated. Signaling storms detection and signaling storm mitigation xApps are deployed over E2 with initial configuration.
E2 interface connectivity is established with Non-RT RIC and RAN respectively. | | - -© 2026 by the O-RAN ALLIANCE e.V. Your use is subject to the copyright statement on the cover page of this specification. - -131 - -| Use Case Stage | Evolution / Specification | <> | -|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| | Data report, policy and control subscription established on E2 interface. | | -| Pre-conditions |

Network is operational.

SMO has established the data collection and sharing interface with Non-RT RIC.

Near-RT RIC already established relevant detection mechanisms of normal signaling behavior and adjusted detection parameters accordingly. Non-RT RIC analyzes the historical data from RAN, develops, trains with help of SMO functions and deploys the models or algorithm as part of the signaling storm detection xApp to the Near-RT RIC.

| | -| Begins when | Network is in normal state (attack is described later on). | | -| Step 1 (M) | Signaling storm detection xApp subscribes on connection establishment signaling messages report from the RAN over the E2 interface. | | -| Step 2 (M) | E2 node sends report to signaling storm detection xApp. | | -| Step 3 (M) | Near-RT RIC signaling storm detection xApp monitors reports to detect aggressive UEs that act with abnormal signaling. | | -| Steps 4-7 (M) | UEs send establish connection messages and E2 node accepts these requests. | | -| Step 8 (M) | E2 node sends a report indicating aggressive devices behavior. | | -| Step 9 (M) | Signaling storm detection xApp detects aggressive activity. | | -| Step 10 (M) | Signaling storm detection xApp updates signaling storm mitigation xApp. | | -| Step 11 (M) | Signaling storm mitigation xApp updates subscription to INSERT-CONTROL. Use control filter to block/throttle aggressive UEs by rejecting some of the messages. | | -| Step 12 (M) | E2 node receives another connection establishment from an aggressive UE. | | -| Step 13 (M) | E2 node forwards the message to the signaling storm mitigation xApp. | | -| Step 14 (M) | Signaling storm mitigation xApp determines that message is from an aggressive device. | | -| Step 15 (M) | Signaling storm mitigation xApp sends a reject/throttle message to the E2 node. | | -| Step 16 (M) | E2 node rejects/throttles connection establishment request. | | -| Step 17 (M) | Signaling storm mitigation xApp continues to monitor its control filter. | | -| Step 18 (M) | Near-RT RIC DDoS mitigation xApp evaluates signaling level and decides that there is no more aggressive UE activity. The xApp updates subscription back to REPORT. | | -| Ends when | Attack is over and signaling messages level is back to normal. | | -| Exceptions | None identified. | | - -``` -@startuml -``` - -``` -skinparam ParticipantPadding 5 -``` - -``` - -skinparam BoxPadding 10 - -skinparam defaultFontSize 12 - -Autonumber - -Box "Service Management and Orchestration" #gold - boundary "OAM Functions" as coll - participant "Non-RT RIC" as non -end box - -Box "O-RAN" #lightpink - Participant " Near-RT RIC Detection xApp" as det - Participant " Near-RT RIC Mitigation xApp" as mit - Participant "E2 Nodes" as ran -End box - -Box "External Enrichment Server" #lightcyan - Participant "Core Probing Framework" as ext -End box - -Participant UE as ue - -ext -> coll: EI's collection -ran -> coll: <> alarms & metrics -coll -> non: Signalling statistics - -group Signaling Storm Detection - det -> ran: <> Subscription Request:REPORT{connection establishment messages} - ran -> det: <> Report: {connection establishment messages} - det -> det: Detect aggressive devices - ue -> ran: Establish connection request - ran -> ue: Establish connection accept - ue -> ran: Establish connection request - ran -> ue: Establish connection accept - ran -> det: < Report: {connection establishment messages} - det -> det: Detect aggressive devices - det -> mit: Decision to apply control filter - mit -> ran: <> Update Subscription: INSERT{connection establishment messages} - -``` - -``` - -ue -> ran: Establish connection request -ran -> mit: <> Establish connection request -mit -> mit: Evaluate filter -mit -> ran: <> Establish connection reject -ran -> ue: Establish connection reject -mit -> mit: Monitor control filter -mit -> ran: Update subscription: REPORT{connection establishment messages} - -end - -@enduml - -``` - -The flow diagram of the local signaling storm protection insert-control is given in figure 4.15.3.2-1. - -![Sequence diagram for local signaling storm protection insert-control. Lifelines: Service Management and Orchestration (OAM Functions, Non-RT RIC), O-RAN (Near-RT RIC Detection XApp, Near-RT RIC Mitigation XApp, E2 Nodes), External Enrichment Server (Core Probing Framework), and UE. The diagram shows the flow of signaling messages and control actions between these components to detect and mitigate signaling storms.](37104233d1b6d7728427e833816594dc_img.jpg) - -The sequence diagram illustrates the interaction for local signaling storm protection insert-control. It begins with the Service Management and Orchestration (OAM Functions) sending an E1's collection request to the Non-RT RIC. The Non-RT RIC responds with alarms & metrics and signaling statistics. The OAM Functions then send a Subscription Request: REPORT{connection establishment messages} to the Near-RT RIC Detection XApp. The Detection XApp sends a <> Report (connection establishment messages) to the E2 Nodes. The E2 Nodes send an Establish connection request to the UE. The UE responds with an Establish connection accept. The E2 Nodes send another Establish connection request to the UE, which again responds with an Establish connection accept. The E2 Nodes then send a <> Report (connection establishment messages) to the Detection XApp. The Detection XApp performs a 'Detect aggressive devices' step and a 'Decision to apply control filter'. Based on the decision, the Detection XApp sends an Update Subscription: INSERT{connection establishment messages} to the Mitigation XApp. The Mitigation XApp sends a <> Establish connection request to the E2 Nodes. The E2 Nodes send an Establish connection request to the UE. The UE responds with an Establish connection reject. The E2 Nodes then send a <> Establish connection reject to the Mitigation XApp. The Mitigation XApp performs an 'Evaluate filter' step and sends an Establish connection reject to the E2 Nodes. The E2 Nodes send an Establish connection reject to the UE. The Mitigation XApp then performs a 'Monitor control filter' step and sends an Update subscription: REPORT{connection establishment messages} to the Detection XApp. The Detection XApp performs another 'Detect aggressive devices' step. The diagram ends with the OAM Functions sending another E1's collection request to the Non-RT RIC. - -Sequence diagram for local signaling storm protection insert-control. Lifelines: Service Management and Orchestration (OAM Functions, Non-RT RIC), O-RAN (Near-RT RIC Detection XApp, Near-RT RIC Mitigation XApp, E2 Nodes), External Enrichment Server (Core Probing Framework), and UE. The diagram shows the flow of signaling messages and control actions between these components to detect and mitigate signaling storms. - -Figure 4.15.3.2-1: Local signaling storm protection insert-control flow diagram - -#### 4.15.3.3 Mode 2 – Distributed signaling storm protection - -The context of the distributed signaling storm protection is captured in table 4.15.3.3-1. - -**Table 4.15.3.3-1: Distributed signaling storm protection** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Detect distributed signaling using Non-RT RIC and A1 policy initiates mode 2 handling in Near-RT RIC with “stricter parameters” mitigation. | | -| Actors and Roles |

Non-RT RIC: Detection of network-level distributed signaling storms, maintenance of cell-level, network slice level and node level normal behavior models.

Near-RT RIC: Detection of local cell-level signaling storms; execution of mitigation policies and controls, maintenance of cell-level normal behavior models.

RAN: Executes UE level or network slice level mitigation policies, collects and reports RAN signaling events and policy specific statistics over E2.

| | -| Assumptions |

All relevant functions and components are instantiated. Signaling storms detection and signaling storms mitigation xApps are deployed over E2 with initial configuration.

A1, E2 interface connectivity is established with Non-RT RIC and RAN respectively.

Data report, policy and control subscription established on E2 interface.

| | -| Pre-conditions |

Network is operational.

SMO has established the data collection and sharing interface with Non-RT RIC.

Non-RT RIC and Near-RT RIC already established relevant detection mechanisms of normal signaling behavior and adjusted detection parameters accordingly. Non-RT RIC analyzes the historical data from RAN, develops, trains with help of SMO functions and deploys the models or algorithm as xApps to the Near-RT RIC.

| | -| Begins when | Network is in normal state when (attack is described later on). | | -| Step 1 (M) | OAM functions start to collect Enrichment Information (EIs) from external sources (e.g. network core probing framework). | | -| Step 2 (M) | OAM functions start to collect alarms & metrics from E2 nodes. | | -| Step 3 (M) | OAM functions sends signaling statistics based on collected information to Non-RT RIC. | | -| Step 4 (M) | Non-RT RIC uses AI/ML model to analyze overall network signaling activity levels based on signaling statistics. | | -| Step 5 (M) | Non-RT RIC applies initial configurations to all Near-RT RIC elements regarding detection and mitigation parameters, including: accepted signaling volume thresholds, throttle/block ratio, accepted false negative levels, filter pause periods, etc. | | -| Step 6 (M) | Non-RT RIC detects distributed signaling storm activity originated from a list of locations. | | -| Step 7 (M) | Non-RT RIC updates configuration to a stricter one in the relevant Near-RT RIC locations over A1 interface. | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 8 (M) | Near-RT RIC performs detection and mitigation as described in 3.15.3.1 or 3.15.3.2 with stricter configuration (e.g. lower thresholds). | | -| Step 9 (M) | Non-RT RIC determines that distributed signaling storm attack is over based on signaling statistics information. | | -| Step 10 (M) | Non-RT RIC updates Near-RT RICs back to initial configuration parameters over the A1 interface. | | -| Step 11 (M) | Near-RT RIC signaling storm detection xApp observed aggressive behavior where temporal identifiers cannot be correlated with the underlying devices. | | -| Step 12 (M) | Near RT RIC alarms the OAM functions over O1. | | -| Step 13 (M) | OAM functions report suspicious behavior to Non-RT RIC. | | -| Step 14 (M) | Non-RT RIC sends enrichment information to Near-RT RIC over A1-EI to support detection of aggressive devices. | | -| Step 15 (M) | Near-RT RIC performs detection and mitigation as described in 3.15.3.1 or 3.15.3.2 with stricter configuration (e.g. lower thresholds). | | -| Step 16 (M) | Non-RT RIC evaluates data and decides that there is no more distributed signaling storm activity. | | -| Step 17 (M) | Non-RT updates configuration of relevant Near-RT RICs over the A1 back to normal. | | -| Ends when | Attack is over and signaling messages level is back to normal. | | -| Exceptions | None identified. | | -| Post Conditions | Non-RT RIC monitors network-level signaling messages statistics.
Near-RT RIC monitors cell-level signaling messages statistics. | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "Service Management and Orchestration" #gold - boundary "OAM Functions" as coll - 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 -``` - -``` -Box "External Enrichment Server" #lightcyan -``` - -``` - Participant "Core Probing Framework" as ext -``` - -``` -End box -``` - -``` -ext -> coll: EI's collection -``` - -``` -ran -> coll: <> alarms & metrics -``` - -``` -coll -> non: Signalling statistics -``` - -``` -group Near-RT RIC Configuration -``` - -``` - non -> non: AI/ML model to analyze overall network signaling activity levels -``` - -``` - non -> near: <> Initial parameters configuration -``` - -``` -end -``` - -``` -group Distributed Signaling StormProtection -``` - -``` - non -> non: Detect distributed signalling storm -``` - -``` - non -> near: <> Configure stricter parameters -``` - -``` - group Signaling Storm Detection -``` - -``` - near -> near: Perfroms detection and mitigation -``` - -``` - end -``` - -``` - non -> non: Evaluate EIs. DDoS is over. -``` - -``` - non -> near: <> Update configuration back to normal -``` - -``` -end -``` - -``` -group Uncorrelated Identifiers Signaling Storm -``` - -``` - near -> near: Identify aggressive behavior with uncorrelated identifiers -``` - -``` - near -> coll: <> Report suspicious behavior -``` - -``` - coll -> non: Report suspicious behavior -``` - -``` - non -> near: <> Reconfigure parameters -``` - -``` - group Signaling Storm Detection -``` - -``` - near -> near: <> Performs detection and mitigation -``` - -``` - end -``` - -``` - non -> non: Evaluate EIs. DDoS is over. -``` - -``` - non -> near: <> Update configuration back to normal -``` - -``` -end -``` - -``` -@enduml -``` - -The flow diagram of the distributed signaling storm protection is given in figure 4.15.3.3-1. - -![Figure 4.15.3.3-1: Distributed signaling storm protection flow diagram. This sequence diagram illustrates the interaction between Service Management and Orchestration (SMO), O-RAN components (Non-RT RIC, Near-RT RIC, E2 Nodes), and an External Enrichment Server (Core Probing Framework). The process involves three main phases: 1) Initial configuration where the Non-RT RIC configures the Near-RT RIC with an AI/ML model and initial parameters. 2) Distributed Signaling Storm Protection where the Near-RT RIC detects a storm, configures stricter parameters, and eventually updates configuration back to normal once the DDoS is over. 3) Uncorrelated Identifiers Signaling Storm where the Near-RT RIC identifies aggressive behavior, reports it to the SMO, reconfigures parameters, and updates configuration back to normal. The External Enrichment Server provides enrichment data to the SMO throughout the process.](1bc1746388cb64bf23b356ce2365dfc2_img.jpg) - -Figure 4.15.3.3-1: Distributed signaling storm protection flow diagram. This sequence diagram illustrates the interaction between Service Management and Orchestration (SMO), O-RAN components (Non-RT RIC, Near-RT RIC, E2 Nodes), and an External Enrichment Server (Core Probing Framework). The process involves three main phases: 1) Initial configuration where the Non-RT RIC configures the Near-RT RIC with an AI/ML model and initial parameters. 2) Distributed Signaling Storm Protection where the Near-RT RIC detects a storm, configures stricter parameters, and eventually updates configuration back to normal once the DDoS is over. 3) Uncorrelated Identifiers Signaling Storm where the Near-RT RIC identifies aggressive behavior, reports it to the SMO, reconfigures parameters, and updates configuration back to normal. The External Enrichment Server provides enrichment data to the SMO throughout the process. - -Figure 4.15.3.3-1: Distributed signaling storm protection flow diagram - -### 4.15.4 Required data - -The measurement counters, detection within the Near-RT RIC is based upon analyzing per UE connection establishment messages events that include the following data: - -- 1) Basic registration event parameters: timestamp, cell ID, temporary ID (e.g., C-RNTI, 5G-GUTI) -- 2) RAN parameters to correlate between a UE and registration events: e.g. RSRP/RSRQ, timing advance, beam ID - -Tracking status of ongoing attack by monitoring statistics of active filters that include the following data: - -- 3) Number of UEs in the filter, number of requests blocked, trend (change over last x periods of time) - -Enrichment information from a non-RAN source regarding network-wide DDoS information: - -- 4) Overloaded regions, overloaded sites, severity (% above normal) - -## 4.16 Congestion prediction and management - -Void - -## 4.17 Industrial IoT optimization - -Void - -## 4.18 BBU pooling to achieve RAN elasticity - -Void - -## 4.19 Integrated SON function within the O-RAN framework - -This use case provides the motivation, description, and requirements for enabling the O-RAN framework to support a minimum SON function set. This use case enables realization of SON functions in the O-RAN architectural framework to help operators address issues seen from vendor specific SON implementation in earlier generation of cellular networks. - -### 4.19.1 Background and goal of the use case. - -SON (Self-Organizing Network) functionalities reduces the cost of running a mobile network by providing control on aspects of network configuration and control 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 perform functionalities like monitoring the network(s) by collecting management data including MDAS (Management Data Analytics Service) data, analysis of the data to determine issues in the network(s) and their resolution. SON intends to achieve the following: - -**Self-configuration:** Aids in seamlessly integrating into the network through automatic configuration of key parameters (initial PCI and ANR functions). - -**Self-optimization:** Aids in enhanced network performance through near real time optimization of radio & network configurations. It is valuable throughout the lifetime of the network and includes SON functionalities such as Mobility Load Balancing [MLB], Mobility Robustness Optimization [MRO], Random Access Channel [RACH] Optimization, etc. - -**Self-healing:** It allows adjacent cells to maintain network quality in case a cell/sector fails, providing resiliency (reliability) in the face of unforeseen outage conditions. It is relevant throughout the lifetime of the network and includes SON functions such as cell outage detection, compensation and recovery. - -The definitions for the SON functionality are specified in 3GPP TS 28.313 [20] but the realization of the SON functions is left to implementation. The SON coordination function for detecting, preventing and resolving conflicts or negative influences between multiple SON functions when there is an attempt to change some (same or associated) network configuration parameters of some (same or associated) nodes is also specified in 3GPP TS 28.313 [20]. Based on the deployment of SON algorithm, the SON solution can be termed as Centralized SON (C-SON – where the SON algorithms are executed in the 3GPP management system), Distributed SON (D-SON - where SON algorithms are executed in the network function layer) and Hybrid SON (where SON algorithm execution is spread across the network function layers and the management layers). - -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. - -NOTE: Other deployment options other than the ones mentioned in this use case are also possible. - -The scope of the integrated SON use case covers the following functions: - -1. Self configuration: - - PCI initial allocation and conflict resolution - - ANR (Automatic Neighbor Relations) -2. Self optimization: - - Mobility Load Balancing (MLB) - - Mobility Robustness Optimization (MRO) - - Coverage and Capacity Optimization (CCO) - - RACH Optimization (RO) - -Editor's note: R1 interface needs to be shown in the UMLs. - -### 4.19.2 Entities/resources involved in the use case - -#### 4.19.2.1 SON inventory and deployment management - -##### 1) SMO - -- Support SON inventory and deployment management for Non-RT RIC(s), Near-RT RIC(s) and E2 node(s). -- Support collection of SON configurations from Non-RT RIC(s), Near-RT RIC(s) and E2 node(s). -- Support decision making on setup of the SON functions in Non-RT RIC(s), Near-RT RIC(s) and E2 node(s). -- Configure Non-RT RIC(s), Near-RT RIC(s) and E2 node(s) based on the decided SON function deployment model. - -##### 2) Non-RT RIC - -- Support exposure of SON functionalities and configurations. -- Support configuration and setup of the SON functions from SMO. - -##### 3) Near-RT RIC - -- Support exposure of SON functionalities and configurations. -- Support configuration and setup of the SON functions from SMO via O1 interface. - -##### 4) E2 node - -- Support exposure of SON functionalities and configurations. -- Support configuration and setup of the SON functions from SMO via O1 interface. - -#### 4.19.2.2 Self configuration (PCI conflict detection/resolution, ANR) - -##### 1) SMO - -- Configure self configuration SON functionality (PCI conflict detection/resolution, ANR) in Non-RT RIC, Near-RT RIC or E2 node. -- Configure/reconfigure the respective SON related parameters and measurements in the Non-RT RIC, Near-RT RIC and E2 node. -- Support collection of measurements or notifications from the respective O-RAN nodes. - -##### 2) Non-RT RIC - -- Retrieve necessary data from SMO. -- Support setup of SON function and configuration of relevant SON data inputs from SMO. -- Support AI/ML training and inference and provide output via O1 or A1 to the relevant O-RAN nodes. - -##### 3) Near-RT RIC - -- Support setup of SON function and configuration of relevant SON data inputs from SMO. -- Configure and receive necessary input data for AI/ML training of SON functions. -- Support notifications to SMO related to SON functions. -- Support AI/ML training and inference and provide output to E2 node via E2 interface. -- Support inputs from Non-RT RIC for AI/ML training and conversion of policies via A1 into E2 inputs. - -##### 4) E2 node - -- Support setup of SON function and configuration of relevant SON data inputs from SMO. -- Support configuration and retrieval of necessary SON function related data for AI/ML model training via E2/O1 interfaces. -- Support policies or configuration changes or relevant inputs via E2/O1 interface to execute RRM functionalities for the respective SON functions. -- Support notifications to SMO related to SON functions. -- Support AI/ML model inference and execute relevant RRM functionalities. - -#### 4.19.2.3 Self optimization (MLB, MRO, CCO, RO) - -##### 1) SMO - -- Configure the self optimization (MLB, MRO, CCO, RO) SON functionality in Non-RT RIC, Near-RT RIC or E2 node. - -##### 2) Non-RT RIC - -- Support setup of SON function and configuration of relevant SON data inputs from SMO. -- Configuration and collection of cell load related information, HO related reports, CCO related measurement reports (RLF (Radio Link Failure), MDT (Minimization Drive Test), RCEF (RRC Connection Establishment Failure)), RACH performance reports for constructing relevant AI/ML models to assist in the self optimization SON functionality. -- Support AI/ML model training and inference based on the input data received. -- Re-configure inter-site/inter-rat cell reselection parameters, HO related parameters, CCO related control parameters and RACH parameters based on AI/ML output. -- Generate relevant A1 policies to execute any RRM function for the configured SON function. - -##### 3) Near-RT RIC - -- Support setup of SON function and configuration of relevant SON data inputs from SMO. -- Configuration and collection of load reports, HO related reports (HO failure and RLF), CCO related measurement reports (RLF, MDT, RCEF), RACH performance reports from E2 nodes over E2 interface. -- Support AI/ML model training and inference based on the input data received via O1 and E2. -- Re-configure HO related, cell reselection parameters, CCO related control parameters and RACH parameters based on AI/ML output. -- Support initiation of RRM functions like HO initiation, trigger cell reselection at E2 node via E2 policies or controls based on AI/ML output. -- Support conversion of A1 policy into relevant E2 actions for executing RRM function for a specific SON function. - -##### 4) E2 node - -- Support setup of SON function and configuration of relevant SON data inputs from SMO. - -- Report Measurement Report (MR), HO related information, coverage information, RACH performance over E2/O1 interface. -- Support reconfiguration of HO related parameters, cell reselection parameters, CCO related parameters, RACH parameters based on inputs via E2 or O1 interface. -- Support initiation of RRM functions like HO initiation, cell reselection, etc. based on inputs received via E2/O1 interface. - -### 4.19.3 Solutions - -#### 4.19.3.1 SON inventory and deployment management - -The context of the SON inventory and deployment management is captured in table 4.19.3.1-1. - -**Table 4.19.3.1-1: SON inventory and deployment management** - -| Use Case Stage | Evolution / Specification | <> | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Goal |
  • • Management of SON configurations of Non-RT RIC, Near-RT RIC and E2 node by the SMO.
  • • Management of deployment of SON functions in Non-RT RIC, Near-RT RIC and E2 node by the SMO.
| | -| Actors and Roles |
  • • SMO acting as controller for the SON inventory and deployment management.
  • • Non-RT RIC, Near-RT RIC and E2 node acting as supporting entities by providing the required information and adhering to SON configuration by SMO.
  • • Operator providing the necessary inputs to SMO for decision making on the SON function deployment.
| | -| Assumptions |
  • • O1 interface connectivity between the SMO and E2 node and Near-RT RIC is established.
  • • E2 interface connectivity is established between E2 node and Near-RT RIC.
  • • A1 interface connectivity is established between Near-RT RIC and Non-RT RIC.
  • • Network is operational.
| | -| Pre-conditions |
  • • SMO is unaware of the SON configurations of the O-RAN nodes.
  • • SMO has necessary inputs from operator to decide the deployment of SON functions in the respective O-RAN nodes.
  • • O-RAN nodes are capable of providing their SON configurations to SMO.
| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Begins when | Network becomes operational and operator configures the SMO for SON inventory and deployment management. | | -| Step 1, 2, 3 (M) |
  • Operator sets the SON targets and the SON function deployment model.
  • SMO analyzes the SON targets and the SON deployment model and notifies the operator on the decision.
  • SMO inspects the SON inventory and decides on the need for retrieval of SON configuration from O-RAN nodes.
| | -| Step 4, 5, 6, 7, 8, 9 (O) |
  • If required, SMO initiates request to retrieve the configuration from O-RAN nodes in a loop until all the necessary configurations are retrieved.
  • Based on the retrieved configuration, SMO re-evaluates the SON deployment model and notifies the operator if any changes to SON deployment model.
| | -| Step 10, 11, 12 (O) |
  • Alternatively, SMO can decide to configure the O-RAN nodes with the necessary SON functions by deploying rApps or xApps to cater to the SON deployment model.
  • SMO can notify the operator on the rApp and xApp deployments if needed.
| | -| Step 13 - 17 (O) | Based on the revised deployment model, SMO communicates the changes to the SON configurations and the SON function setup to the O-RAN nodes. | | -| Step 18 (M) |

The O-RAN nodes collect data, analyze, and decide if any changes are needed to the configuration and notify operator for any modifications done.

This is done in a loop until SON targets are met.

| | -| Step 19 – 27 (M) | If the SON functions need to be terminated based on inputs from operator, then SMO initiates deletion of SON configurations in the respective O-RAN nodes and notifies the operator when the termination is completed. | | -| Ends when | The SON functions are terminated by the operator or when the SON targets are met. | | -| Exceptions | None identified. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Post Conditions | SMO, Non-RT RIC, Near-RT RIC and E2 nodes interwork with each other seamlessly adhering to the SON function setup input from SMO. | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -@startuml -box "Personnel" #lightblue -actor "Operator" as RP -end box - -box "Service Management & \nOrchestration Framework" #gold -participant SMO -participant "Non-RT RIC" as NonRTRIC -end box - -box "O-RAN Components" #lightpink -collections "Near-RT RIC" as NearRTRIC -collections "O-RAN Nodes" as ORANnodes -end box - -autonumber - -RP -> SMO: Triggering Criteria (SON targets \n and SON Deployment Model) - -== Planning phase == - -ref over SMO, NonRTRIC : Analyze & Decide SON targets\n and SON Deployment Model \n - -opt Operator's expectation on visibility exists - -``` - -``` - -SMO -> RP : Notify (progress, deployment model) -end - -== Configuration / deployment phase == - -SMO -> SMO : Inspect SON related inventory data -opt need for inventory update identified - loop for each entity whose inventory data needs to be updated - alt rApp entity - ||| - ref over NonRTRIC, SMO : Obtain information about deployed rApps\n - else xApp entity - SMO -> NearRTRIC : <> Read on MOI - NearRTRIC --> SMO : <> Success - else O-RAN Node - SMO -> ORANnodes : <> Read on MOI - ORANnodes --> SMO : <> Success - end - end -end - -ref over SMO, NonRTRIC : Re-evaluate SON deployment model\n - -opt Deployment model needs to be revised - ref over SMO, NonRTRIC : Revise SON deployment model\n - opt Operator's expectation on visibility exists - SMO -> RP : Notify (progress, deployment model) - end -end - -ref over SMO, NonRTRIC : Decide SON configuration\n - -opt Operator's expectation on visibility exists - SMO -> RP : Notify (progress, SON configuration) -end - -opt Deployment model needs new entities - -``` - -``` - -loop for each new entity - alt rApp entity - SMO <-> NonRTRIC : <> Deploy (rApp) - else xApp entity - SMO <-> NearRTRIC : <> Deploy (xApp) - end -end - -opt Operator's expectation on visibility exists - SMO -> RP : Notify (progress, deployed entities) -end -end - -opt need for configuration update identified - loop for each entity whose configuration needs to be updated - alt rApp entity - ||| - ref over NonRTRIC, SMO : Modify rApp Configuration\n - else xApp entity - SMO -> NearRTRIC : <> Modify MOI (attribute values) - NearRTRIC --> SMO : <> Success - else O-RAN Node - SMO -> ORANnodes : <> Modify MOI (attribute values) - ORANnodes --> SMO : <> Success - end - end -end - -opt Operator's expectation on visibility exists - SMO -> RP : Notify (progress) -end - -== Active phase == - -loop while SON control loop is active - ||| - -``` - -``` - -ref over SMO, NonRTRIC, NearRTRIC, ORANnodes : Collect data\n -ref over SMO, NonRTRIC, NearRTRIC, ORANnodes : Analyze data\n -ref over SMO, NonRTRIC, NearRTRIC, ORANnodes : Decide on necessary actions\n -ref over SMO, NonRTRIC, NearRTRIC, ORANnodes : Act / apply changes\n - -opt Operator's expectation on visibility exists - SMO -> RP : Notify (progress, state of SON targets) -end - -end - -== Termination phase == - -RP -> SMO: Triggering Criteria (SON termination) -loop for each impacted SON entity - alt rApp entity - alt entity no longer needed - ||| - ref over NonRTRIC, SMO : Terminate rApp\n - else entity still needed - ||| - ref over NonRTRIC, SMO : Modify rApp Configuration\n - end - NonRTRIC --> SMO : <> Success - else xApp entity - alt entity no longer needed - SMO -> NearRTRIC : Terminate (xApp instance id) - SMO -> NearRTRIC : Delete MOI (instance id) - else entity still needed - SMO -> NearRTRIC : Modify MOI (attribute values) - end - NearRTRIC --> SMO : <> Success - else O-RAN Node - SMO -> ORANnodes : <> Modify MOI (attribute values) - ORANnodes --> SMO : <> Success - end -end - -``` - -``` -end - -opt Operator's expectation on visibility exists - SMO -> RP : Notify (progress) -end - -@enduml -``` - -The flow diagram of the SON inventory and deployment management is given in figure 4.19.3.1-1. - -![SON inventory and deployment management flow diagram. The diagram shows a sequence of interactions between an Operator and O-RAN components (SMO, Non-RT RIC, Near-RT RIC, O-RAN Nodes) across four phases: Planning, Configuration/deployment, Active, and Termination. The Planning phase involves analyzing and deciding on SON targets and deployment models. The Configuration/deployment phase includes inventory updates, model revisions, and entity deployments. The Active phase involves data collection, analysis, and applying changes. The Termination phase involves terminating entities and modifying configurations. The diagram uses UML sequence notation with lifelines for Operator, SMO, Non-RT RIC, Near-RT RIC, and O-RAN Nodes. Messages are numbered 1 through 27, with optional (opt) and loop constructs.](5a3dccee8ce4d2fa1986aba4ae8ad6e2_img.jpg) - -The diagram illustrates the SON inventory and deployment management flow, organized into four main phases: - -- Planning phase:** - - 1 Triggering Criteria (SON targets and SON Deployment Model) - - ref: Analyze & Decide SON targets and SON Deployment Model - - opt: (Operator's expectation on visibility events) - - 2 Notify (progress, deployment model) -- Configuration / deployment phase:** - - 3 Inspect SON related inventory data - - opt: (need for inventory update identified) - - loop: (For each entity whose inventory data needs to be updated) - - alt: (App entity) - - ref: Obtain information about deployed Apps - - alt: (App entity) - - 4 <> Read on MOI - - 5 <> Success - - alt: (O-RAN Node) - - 6 <> Read on MOI - - 7 <> Success - - ref: Re-evaluate SON deployment model - - opt: (Deployment model needs to be revised) - - ref: Revise SON deployment model - - opt: (Operator's expectation on visibility events) - - 8 Notify (progress, deployment model) - - ref: Decide SON configuration - - opt: (Operator's expectation on visibility events) - - 9 Notify (progress, SON configuration) - - opt: (Deployment model needs new entities) - - loop: (For each new entity) - - alt: (App entity) - - 10 <> Deploy (App) - - 11 <> Deploy (App) - - opt: (Operator's expectation on visibility events) - - 12 Notify (progress, deployed entities) - - opt: (need for configuration update identified) - - loop: (For each entity whose configuration needs to be updated) - - alt: (App entity) - - ref: Modify App Configuration - - alt: (App entity) - - 13 <> Modify MOI (attribute values) - - 14 <> Success - - alt: (O-RAN Node) - - 15 <> Modify MOI (attribute values) - - 16 <> Success - - opt: (Operator's expectation on visibility events) - - 17 Notify (progress) -- Active phase:** - - loop: (whiles SON control loop is active) - - ref: Collect data - - ref: Analyze data - - ref: Decide on necessary actions - - ref: Act / apply changes - - opt: (Operator's expectation on visibility events) - - 18 Notify (progress, state of SON targets) -- Termination phase:** - - 19 Triggering Criteria (SON termination) - - loop: (For each impacted SON entity) - - alt: (App entity) - - alt: (entity no longer needed) - - ref: Terminate App - - alt: (entity still needed) - - ref: Modify App Configuration - - 20 <> Success - - alt: (App entity) - - alt: (entity no longer needed) - - 21 Terminate (App instance id) - - 22 Delete MOI (instance id) - - alt: (entity still needed) - - 23 Modify MOI (attribute values) - - 24 <> Success - - alt: (O-RAN Node) - - 25 <> Modify MOI (attribute values) - - 26 <> Success - - opt: (Operator's expectation on visibility events) - - 27 Notify (progress) - -SON inventory and deployment management flow diagram. The diagram shows a sequence of interactions between an Operator and O-RAN components (SMO, Non-RT RIC, Near-RT RIC, O-RAN Nodes) across four phases: Planning, Configuration/deployment, Active, and Termination. The Planning phase involves analyzing and deciding on SON targets and deployment models. The Configuration/deployment phase includes inventory updates, model revisions, and entity deployments. The Active phase involves data collection, analysis, and applying changes. The Termination phase involves terminating entities and modifying configurations. The diagram uses UML sequence notation with lifelines for Operator, SMO, Non-RT RIC, Near-RT RIC, and O-RAN Nodes. Messages are numbered 1 through 27, with optional (opt) and loop constructs. - -Figure 4.19.3.1-1: SON inventory and deployment management flow diagram - -#### 4.19.3.2 Self configuration (PCI conflict detection/resolution, ANR) - -The context of the self configuration is captured in table 4.19.3.2-1. - -**Table 4.19.3.2-1: Self configuration** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Enable flexible deployment of the self configuration SON functions like PCI conflict detection/resolution, ANR by means of configuration parameter change, regulating RRM function actions and allowing AI/ML-based solutions. | | -| Actors and Roles |
  • SMO acting as parameter configuration function.
  • Non-RT RIC/ Near-RT RIC: Configuration decision making function.
  • E2 node: Configuration enforcement function, and measurement reporting function.
| | -| Assumptions |
  • O1 interface connectivity between the SMO and E2 node, Near-RT RIC is established.
  • E2 interface connectivity is established between E2 node and Near-RT RIC.
  • A1 interface connectivity is established between Near-RT RIC and Non-RT RIC.
  • Network is operational.
| | -| Pre-conditions | SMO has configured the SON functions and required initial parameters in the respective O-RAN nodes via SON inventory and deployment management as shown in clause 4.19.3.1. | | -| Begins when | Operator enables the self configuration SON functions like PCI conflict detection/resolution, ANR and E2 node becomes operational. | | -| Step 1a, 1b, 1c (O) |
  • Non-RT RIC initiates the specific measurement data collection request towards SMO and SMO towards E2 node for AI/ML model training and for analysis of data for optimization.
  • E2 node sends the configured measurement data via O1 interface to SMO and Non-RT RIC retrieves the required data from SMO.
| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 2a, 2b, 2c, 2d, 2e, 2f (O) |
  • Non-RT RIC can train the AI/ML model with the collected data from O1 interface and constantly monitors the performance of the E2 node(s) for optimization.
  • Based on the output of the AI/ML processing the Non-RT RIC can trigger modification of configuration parameters through SMO via O1 interface to E2 node.
  • Optionally Non-RT RIC can also generate and send A1 policies for initiation of HO etc. to Near-RT RIC. Near-RT RIC converts the A1 policies to E2 actions and forwards them to E2 nodes.
  • Non-RT RIC continues to monitor the performance of the E2 nodes and re-trains the AI/ML model in a loop.
| | -| Step 3a, 3b (O) |
  • Near-RT RIC initiates the specific measurement data collection request towards E2 node. Near-RT RIC can use the collected data for optionally AI/ML model training and for analysis of data for optimization.
  • E2 node sends the configured measurement data via E2 interface to Near-RT RIC.
| | -| Step 4a, 4b, 4c, 4d (O) |
  • Near-RT RIC can train the AI/ML model with the collected data from E2 interface and constantly monitors the performance of the E2 node(s) for optimization.
  • Upon trigger from the AI/ML processes, Near-RT RIC performs reconfiguration of parameters.
  • Optionally Near-RT RIC can request initiation of certain E2 node actions like HO or cell reselection, etc.
  • Near-RT RIC continues to monitor the performance of the E2 nodes and re-trains the AI/ML model in a loop.
| | -| Step 5 (O) | E2 node receives required inputs from SMO/Non-RT RIC and Near-RT RIC for execution of self configuration SON functions. | | -| Step 6a, 6b (O) |
  • Based on the inputs received and the inputs from inbuilt RRM algorithm, E2 node reconfigures parameters related to self configuration.
| | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| |
  • E2 node can initiate certain RRM actions like HO or cell reselection, etc.
| | -| Ends when | E2 node becomes non-operational or when the operator disables the self configuration SON functions. | | -| Exceptions | One of the steps identified above fails. | | -| Post Conditions |

SMO/ Non-RT RIC, Near-RT RIC continues real time close loop optimization of self configuration SON functions.

The E2 node operates using the newly deployed parameters.

| | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -@startuml -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid - -box "Service Management & \nOrchestration Framework" #gold -participant "SMO" as smo -Participant "Non-RT RIC" as nonrt -end box - -box "O-RAN Components" #lightpink -participant "Near-RT RIC" as ric -collections "E2 Nodes" as e2node -endbox - -note over smo #white: Operator configures \nSON Function deployment\nand initial SON Parameters - -``` - -hnote over smo, e2node #white: Self Configuration SON Functions (PCI Conflict Detection/Resolution, ANR) is configured in Non-RT RIC/ Near-RT RIC or E2 Node \n via SON Inventory and Deployment Management procedure as shown in figure 4.19.3.1-1 - -alt Deployment Option 1 - -'group Self Configuration SON Functions in Non-RT RIC Loop - -loop Until all SON Functions in Non-RT RIC are configured - -smo->e2node: 1a. <> Data collection request for Self Configuration SON functions - -e2node->smo: 1b. <> Data collection for Self Configuration SON functions - -smo->nonrt: 1c. Data retrieval - -nonrt->nonrt: 2a. AI/ML Model training and inference - -nonrt->smo: 2b. Request for Reconfigurat on of \n Self Configuration SON Parameters - -nonrt->e2node: 2c. <> Reconfiguration of Self Configuration related SON Parameters - -opt - -nonrt->ric: 2d. <> Send A1 policies related to \n Self Configuration related SON Functions - -ric->e2node: 2e. <> Request E2 services corresponding to A1 policy - -end - -nonrt->nonrt: 2f. Performance monitoring \n and re-training - -end - -'end - -else Deployment Option 2 - -'group Self Configuration SON Functions in Near-RT RIC Loop - -loop Until all SON Functions in Near-RT RIC are configured - -ric->e2node: 3a. <> Data collection request for Self Configuration SON functions - -e2node->ric: 3b. <> Data collection for Self Configuration SON functions - -ric->ric: 4a. AI/ML Model training and inference - -ric->e2node: 4b. <> Reconfiguration of Self Configuration related SON Parameters - -opt - -``` - ric->e2node: 4c. <> Request Initiation of RRM Actions like HO, Cell -Reselection etc - end - ric->ric: 4d. Performance monitoring \n and re-training - end - 'end - -else Deployment Option 3 - 'group Self Configuration SON Functions in E2 Node Loop - loop Until all SON Functions in E2 Node are configured - - hnote over smo, e2node #white: 5. Receive required inputs for executing Self -Configuration SON Function from SMO/ Non-RT RIC/ Near-RT RIC - - e2node->e2node: 6a. Reconfiguration of Parameters related \nto Self Configuration -SON Function - e2node->e2node: 6b. Initiate RRM Actions like \nHO, Cell Reselection etc - end -end - -@enduml -``` - -The flow diagram of the self configuration is shown in figure 4.19.3.2-1. - -![Sequence diagram for Self configuration showing interactions between SMO, Non-RT RIC, Near-RT RIC, and E2 Nodes across three deployment options.](53499879d98034410ecba2c386c58f0c_img.jpg) - -The diagram illustrates the 'Self configuration' use case sequence. It features four lifelines: SMO (Service Management & Orchestration Framework), Non-RT RIC, Near-RT RIC, and E2 Nodes. The process is divided into three deployment options: - -- Deployment Option 1:** All SON functions are configured in the Non-RT RIC. The sequence involves data collection, AI/ML model training, and parameter reconfiguration. An optional step (opt) includes sending A1 policies and requesting E2 services. -- Deployment Option 2:** All SON functions are configured in the Near-RT RIC. The sequence involves data collection, AI/ML model training, parameter reconfiguration, and an optional step (opt) for initiating RRM actions like HO or Cell Reselection. -- Deployment Option 3:** All SON functions are configured in the E2 Node. The sequence involves receiving inputs from the SMO/Non-RT RIC/Near-RT RIC and then performing parameter reconfiguration and RRM actions. - -Initial notes indicate that the operator configures SON function deployment and initial SON parameters, and that SON functions (PCI Conflict Detection/Resolution, ANR) are configured via SON Inventory and Deployment Management procedure. - -Sequence diagram for Self configuration showing interactions between SMO, Non-RT RIC, Near-RT RIC, and E2 Nodes across three deployment options. - -Figure 4.19.3.2-1: Self configuration - -#### 4.19.3.3 Self optimization (MLB, MRO, CCO, RO) - -The context of the self optimization is captured in table 4.19.3.3-1. - -Table 4.19.3.3-1: Self optimization - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Enable flexible optimization of the self optimizing SON functions like MRO, MLB, CCO and RACH by means of configuration parameter change, regulating RRM function actions and allowing AI/ML-based solutions. | | -| Actors and Roles |
  • SMO acting as parameter configuration function.
| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| |
  • Non-RT RIC/ Near-RT RIC: Self optimization decision making function.
  • E2 node: Configuration enforcement function, and measurement reporting function.
| | -| Assumptions |
  • O1 interface connectivity between the SMO and E2 node, Near-RT RIC is established.
  • E2 interface connectivity is established between E2 node and Near-RT RIC.
  • A1 interface connectivity is established between Near-RT RIC and Non-RT RIC.
  • Network is operational.
| | -| Pre-conditions |

SMO has configured the SON functions and required initial parameters in the respective O-RAN nodes via SON inventory and deployment management as shown in clause 4.19.3.1.

| | -| Begins when |

Operator enables the optimization functions for SON functions like MRO, MLB, CCO or RACH and E2 node becomes operational.

| | -| Step 1a, 1b, 1c (O) |
  • Non-RT RIC initiates the specific measurement data collection request towards SMO and SMO towards E2 node for AI/ML model training and for analysis of data for optimization.
  • E2 node sends the configured measurement data via O1 interface to SMO and Non-RT RIC retrieves the required data from SMO.
| | -| Step 2a, 2b, 2c, 2d, 2e, 2f (O) |
  • Non-RT RIC can train the AI/ML model with the collected data from O1 interface and constantly monitors the performance of the E2 node(s) for optimization.
  • Based on the output of the AI/ML processing the Non-RT RIC can trigger modification of configuration parameters through SMO via O1 interface to E2 node.
  • Optionally Non-RT RIC can also generate and send A1 policies for initiation of HO etc to Near-RT RIC. Near-RT RIC converts the A1 policies to E2 actions and forwards them to E2 nodes.
  • Non-RT RIC continues to monitor the performance of the E2 nodes and re-trains the AI/ML model in a loop.
| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 3a, 3b (O) |
  • Near-RT RIC initiates the specific measurement data collection request towards E2 node. Near-RT RIC can use the collected data to optionally train the AI/ML model and for analysis of data for optimization.
  • E2 node sends the configured measurement data via E2 interface to Near-RT RIC.
| | -| Step 4a, 4b, 4c, 4d (O) |
  • Near-RT RIC can train the AI/ML model with the collected data from E2 interface and constantly monitors the performance of the E2 node(s) for optimization.
  • Upon trigger from the AI/ML processes, Near-RT RIC performs reconfiguration of parameters related to self optimization.
  • Optionally Near-RT RIC can request initiation of certain E2 node Actions like HO or cell reselection, etc.
  • Near-RT RIC continues to monitor the performance of the E2 nodes and re-trains the AI/ML model in a loop.
| | -| Step 5 (O) | E2 node receives required inputs from SMO/Non-RT RIC and Near-RT RIC for execution of self optimization SON functions. | | -| Step 6a, 6b (O) |
  • Based on the inputs received and the inputs from inbuilt RRM algorithm E2 node reconfigures parameters related to self optimization.
  • E2 node can initiate certain RRM Actions like HO or cell reselection, etc.
| | -| Ends when | E2 node becomes non-operational or when the operator disables the optimization functions for SON functions like MRO, MLB, CCO or RACH. | | -| Exceptions | One of the steps identified above fails. | | -| Post Conditions |

SMO/Non-RT RIC, Near-RT RIC continues real time close loop optimization of self optimization SON functions.

The E2 node operates using the newly deployed parameters.

| | - -``` -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber -``` - -``` - -@startuml -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid - -box "Service Management & \nOrchestration Framework" #gold -participant "SMO" as smo -Participant "Non-RT RIC" as nonrt -end box - -box "O-RAN Components" #lightpink -participant "Near-RT RIC" as ric -collections "E2 Nodes" as e2node -endbox - -note over smo #white: Operator configures \nSON Function deployment\nand SON initial -Parameters - -hnote over smo, e2node #white: Self Optimization SON Functions (MRO/ MLB/ CCO/ RO) is -configured in Non-RT RIC/ Near-RT RIC or E2 Node \n via SON Inventory and Deployment -Management procedure as shown in figure 4.19.3.1-1 - -alt Deployment Option 1 - 'group Self Optimization SON Functions in Non-RT RIC Loop - loop While Self Optimization in Non-RT RIC is active - - smo->e2node: 1a. <> Data collection request for Self Optimization SON -functions - - e2node->smo: 1b. <> Data collection for Self Optimization SON functions - - smo->nonrt: 1c. Data retrieval - - nonrt->nonrt: 2a. AI/ML Model training and inference - - nonrt->smo: 2b. Request for Reconfiguraton of \n Self Optimization SON Parameters - - smo->e2node: 2c. <> Reconfiguration of Self Optimization related SON -Parameters - - opt - -``` - -``` - - nonrt->ric: 2d. <> Send A1 policies related to \n Self Optimization - related SON Functions - - ric->e2node: 2e. <> Request E2 services corresponding to A1 policy - - end - - nonrt->nonrt: 2f. Performance monitoring \n and re-training - - end - - 'end - -else Deployment Option 2 - - 'group Self Optimization SON Functions in Near-RT RIC Loop - - loop While Self Optimization in Near-RT RIC is active - - ric->e2node: 3a. <> Data collection request for Self Optimization SON - functions - - e2node->ric: 3b. <> Data collection for Self Optimization SON functions - - ric->ric: 4a. AI/ML Model training and inference - - ric->e2node: 4b. <> Reconfiguration of Self Optimization related SON - Parameters - - opt - - ric->e2node: 4c. <> Request Initiation of RRM Actions like HO, Cell - Reselection etc - - end - - ric->ric: 4d. Performance monitoring \n and re-training - - end - - 'end - -else Deployment Option 3 - - 'group Self Optimization SON Functions in E2 Node Loop - - loop While Self Optimization in E2 Node is active - - hnote over smo, e2node #white: 5. Receive required inputs for executing Self - Optimization SON Functions from SMO/ Non-RT RIC/ Near-RT RIC - - e2node->e2node: 6a. Reconfiguration of Parameters related \nto Self Optimization - SON Functions - - e2node->e2node: 6b. Initiate RRM Actions like \nHO, Cell Reselection etc - - end - -``` - -end - -@enduml - -The flow diagram of the self optimization is given in figure 4.19.3.3-1. - -![Sequence diagram for Self optimization showing three deployment options involving SMO, Non-RT RIC, Near-RT RIC, and E2 Nodes.](7fdddd449ff61579cf1f067a3bde63b0_img.jpg) - -The diagram illustrates the interaction for self-optimization across three deployment options. The participants are SMO, Non-RT RIC, Near-RT RIC, and E2 Nodes. An initial note indicates that SON functions are configured via SON Inventory and Deployment Management. The diagram is structured as follows: - -- Deployment Option 1:** While Self Optimization in Non-RT RIC is active. - - 1a. Non-RT RIC sends a <> Data collection request for Self Optimization SON functions to E2 Nodes. - - 1b. E2 Nodes respond with <> Data collection for Self Optimization SON functions. - - 1c. Non-RT RIC performs Data retrieval. - - 2a. Non-RT RIC performs AI/ML Model training and inference. - - 2b. Non-RT RIC sends a Request for Reconfiguration of Self Optimization SON Parameters to E2 Nodes. - - 2c. E2 Nodes perform Reconfiguration of Self Optimization related SON Parameters. - - 2d. (opt) Non-RT RIC sends <> Send A1 policies related to Self Optimization related SON Functions to Near-RT RIC. - - 2e. Near-RT RIC sends <> Request E2 services corresponding to A1 policy to E2 Nodes. - - 2f. Non-RT RIC performs Performance monitoring and re-training. -- Deployment Option 2:** While Self Optimization in Near-RT RIC is active. - - 3a. Near-RT RIC sends a <> Data collection request for Self Optimization SON functions to E2 Nodes. - - 3b. E2 Nodes respond with <> Data collection for Self Optimization SON functions. - - 4a. Near-RT RIC performs AI/ML Model training and inference. - - 4b. Near-RT RIC sends a <> Reconfiguration of Self Optimization related SON Parameters to E2 Nodes. - - 4c. (opt) Near-RT RIC sends a <> Request Initiation of RRM Actions like HO, Cell Reselection etc to E2 Nodes. - - 4d. Near-RT RIC performs Performance monitoring and re-training. -- Deployment Option 3:** While Self Optimization in E2 Node is active. - - 5. E2 Nodes receive required inputs for executing Self Optimization SON Functions from SMO/ Non-RT RIC/ Near-RT RIC. - - 6a. E2 Nodes perform Reconfiguration of Parameters related to Self Optimization SON Functions. - - 6b. E2 Nodes initiate RRM Actions like HO, Cell Reselection etc. - -Sequence diagram for Self optimization showing three deployment options involving SMO, Non-RT RIC, Near-RT RIC, and E2 Nodes. - -Figure 4.19.3.3-1: Self optimization - -### 4.19.4 Required data - -#### 4.19.4.1 Self configuration (PCI conflict detection/resolution, ANR) - -##### 1) SMO - -- Network topology, GPS coordinates of the E2 nodes, PCI allocation range as inputs from operator -- Information on PCI confusion or PCI conflict from E2 node via O1 interface - -- Neighbor information (PCI, ECGI, PLMN, TANAC, TAC, frequency bands) based on network topology as input from operator - -##### 2) Non-RT RIC/Near-RT RIC and E2 node - -- 3GPP RRC measurement reports with PCI information of the neighboring cells via E2 interface -- PCI allocation range via O1 interface from SMO -- Information on PCI confusion or PCI conflict from E2 node via O1 interface -- Neighbour cell relation table information of the neighboring cells via E2 interface -- 3GPP XN, X2 and NG mobility related messages via E2 interface from E2 node - -#### 4.19.4.2 Self optimization (MLB, MRO, CCO, RO) - -##### 1) Non-RT RIC/Near-RT RIC and E2 node - -- MLB - Load reports from Xn/X2/F1/E1 interface resource status reporting procedures and Xn, X2 and NG mobility messages defined in 3GPP via E2 interface from E2 node. -- MLB - HO trigger control parameters available as specified in 3GPP TS 28.313 [20], clause 7.1.5 to E2 node via E2 interface or O1 interface. -- MRO - Xn, X2 and NG HO reports, RLF reports, NG uplink and downlink RRC transfer messages, UE history information, coverage, and quality information and XN/NG/X2 mobility related messages defined in 3GPP via E2 interface from E2 node. -- MRO - HO target and control parameters available as specified in 3GPP TS 28.313 [20], clause 7.1.2 to E2 node via E2 interface or O1 interface. -- CCO – RLF, MDT, measurement reports and RCEF related reports defined in 3GPP via E2 interface from E2 node. -- CCO related control parameters and control information available as specified in 3GPP TS 28.313 [20], clause 7.2.3 to E2 node via E2 interface or O1 interface. -- RACH optimization – PRACH parameters available over XN/X2 interface, contention detection per RACH attempt, number of RACH preambles per SSB, information on SSB threshold per RACH attempt defined in 3GPP via E2 interface from E2 node. -- HO target and control parameters available as specified in 3GPP TS 28.313 [20] to E2 node via E2 interface or O1 interface. - -## 4.20 Shared O-RU - -### 4.20.1 Background and goal of the use case - -#### 4.20.1.1 Common aspects & background for all Shared O-RU use cases - -This use case provides the background, motivation, and requirements for the lower layer split multi node support, allowing to share an O-RU between multiple O-DU nodes, including single operator and multi-operator use cases. - -Shared O-RU use cases deliver a range of different benefits depending on specific scenarios. Shared O-RU support for Single-MNO use cases delivers important resiliency and load balancing capabilities. Shared O-RU support for multiple-MNO use cases delivers important network sharing capabilities to complement established MOCN, MORAN and DAS approaches. - -Shared O-RU use cases cover the class 2 BBU pooling specified in clause 4.18. - -Shared O-RU use cases are associated with RAN sharing use case. In particular, RAN sharing depicts a Shared O-RU configuration, specified in clause 4.7. - -Shared O-RU feature also serves to support the Multi-Vendor (MV) network slicing use case, its operation, and scenarios, specified in clause 4.10. Multi-vendor network slicing has implications to the front-haul as well. The multi-vendor slicing use case will use dynamic resource allocation aspects of the Shared O-RU feature. - -The following sub-clauses describe different configurations and deployment scenarios for Shared O-RU. They also describe use cases to accomplish key functionality such as a resiliency use case. - -The Shared O-RU will have common solutions that span the sub-use cases. The clauses that follow describe different aspects, configurations, and deployment scenarios for Shared O-RU; however, they will likely share common solutions which are described in the solution clause. - -Expected use cases that accomplish a purpose between actors comprise the sub-use cases: such as software upgrade of a Shared O-RU, start up of a Shared O-RU, recovery from failed primary O-DUs that are sharing a O-RU, rehoming of a Shared O-RU in a network. - -##### **State management:** - -The Shared O-RU supports lock/unlock operations (administrative state) of a Shared O-RU administrative state management and these are used throughout the sub-use cases. State management of administrative, operation and availability state are specified in ITU-T X.731 [18] and in 3GPP TS 28.624 [9], in 3GPP TS 28.625 [10] (for all classes in the NRM), and in 3GPP TS 28.626 [11]. Some of the sub-use cases can use them, some cannot. Role-based admission control. The host can change administrative state of the O-RU while the tenant cannot. The Shared O-RU sub-use cases shall be as specified in RFC 8348 [19] which is similar to what is specified in ITU-T X.731 [18]. - -#### **4.20.1.2 Resource portioning use case of Shared O-RU for Single-MNO** - -This sub-use case describes the procedures of how to decide on the partitioning of a Shared O-RU. The actors are the sharing co-ordinator, SMO, and the resource partitioning rApp (Shared O-RU). The sharing co-ordinator recovers the inventory from the SMO and decides on how to partition the resources of a Shared O-RU. The sharing co-ordinator uses the rApp to partition the resources of a Shared O-RU between multiple O-DUs. The outcome is that rApp has details on how a Shared O-RU's resource are to be partitioned. - -#### **4.20.1.3 Start-up use case of a Shared O-RU for Single-MNO** - -This sub-use case describes the start-up of a Shared O-RU. The actors are the SMO, the O-DUs, the Shared O-RU, and their interactions that are needed for a Shared O-RU to boot up and enter into operation. The outcome is that the Shared O-RU is operating with the necessary software version and has established network connectivity with the O-DUs and, for hybrid deployments, the SMO. The start-up for a Shared O-RU is the basis of the other Shared O-RU sub-use cases. - -#### **4.20.1.4 Configuration use case of a Shared O-RU for Single & Multi-MNO** - -This sub-use case describes the configuration of a Shared O-RU. The configuration is invoked after the start-up use case has completed. Configuration can occur with different actors in hybrid vs hierarchical management mode. The common aspects of the Shared O-RU configuration are configured by the O-DU when in hierarchical management mode and by the SMO in hybrid management mode. The common aspects include the security, operational, transmission, and connectivity related parameters. The O-DUs are always responsible for configuring the partitioned carrier information on the Shared O-RU through the open front-haul interface. The use case enables the SMO to be notified of the configured carrier parameters. - -This sub-use case includes the configuration of multi-operator role-based access control (configuration) for the management sessions associated with a tenant operator. The Shared O-RU uses the PLMN-Id associated with the management account and used in other aspects of the Shared O-RU's configuration to prevent a tenant from reading configuration associated with a second tenant's partitioned resources or subscribing to performance measurements associated with a second tenant's partitioned resources. - -This sub-use case also describes the procedures of how a sharing co-ordinator can confirm that a tenant operator is complying with the sharing agreements that cover operation of a Shared O-RU. - -The outcome is that the Shared O-RU has been configured with the configuration parameters necessary for operation. - -#### 4.20.1.5 Supervision use case of a Shared O-RU for Single-MNO - -This sub-use case applies to the running/operation of Shared O-RU. - -This sub-use case describes the supervision operations of the Shared O-RU. This sub-use case is triggered after the O-DUs have configured the partitioned carrier information of a Shared O-RU. It is invoked during run-time. The actors are the SMO, O-DUs, and Shared O-RU. The objective that the use case accomplishes is the establishment of watchdog supervision of the Shared O-RU by multiple O-DUs. Supervision enables the Shared O-RU to autonomously cease transmitting on a partitioned carrier if it loses supervision with the O-DU responsible for that carrier. - -#### 4.20.1.6 Performance management use case of a Shared O-RU for Single-MNO - -This sub-use case applies to the running/operation of Shared O-RU. - -This sub-use case describes the performance management operations of the Shared O-RU. This sub-use case is triggered after the O-DUs have configured the partitioned carrier information of a Shared O-RU. It is also invoked during run-time. The actors are the O-DUs, and Shared O-RU. The objective that the use case accomplishes is for each O-DU to establish subscriptions to receive performance management notifications regarding operation of the fronthaul between the O-DUs and Shared O-RU. - -The sub-use case also describes how performance management logs, data and files are passed from the Shared O-RU to the connected O-DUs and data from O-DUs to SMO. Performance measurement data should be supported in three basic ways by the O-DU: - -- **Active push by a producer (O-DU)** – A producer (O-DU) could push performance data to a consumer (SMO). - - o **Streaming** – A persistent connection between consumer & producer exists without having to renegotiate between the data reports to send a steady flow of data. This is like 3GPP performance streaming reporting (as specified in 3GPP TS 28.532 [21], clause 11.5). Once the WebSocket is opened, the meta-data about the streams is exchanged, and the consumer can then receive the serialized data. - - o **Event notifications** – Performance measurement information sent by event notifications will reestablish a new connection between a consumer and producer for each data reporting. This is how 5GC SBA works (as specified in 3GPP TS 23.501 [2] and in 3GPP TS 23.502 [22] services). The data is sent as a payload of a notification. -- **Active collection by a consumer** – The consumer (SMO) could also actively collect data from a producer (O-DU). - - o **Configuration management read only attributes** – Reuse of configuration management approach where attribute conveying the value of performance data is read by the consumer like any other configuration management attribute. - - o **Data scraping** – Use of data scraping common to cloud native implementations where a collector reads the data from a pre-defined URI. -- **File-based reporting** – File based reporting is used for low-priority or background collection for large amounts of performance data. - - o **File upload by producer** – In this method, there is no artificial delay, the data is reported whenever it is available. However, it involves action by the producer. - -- **File download by consumer** – It removes the burden from the producer, but relies upon either periodic polling, or file ready notification from the producer about the data being ready for download. This is how 3GPP file-based reporting works as specified in 3GPP TS 28.532 [21], clause 11.6 and in ETSI GS NFV IFA008 [24] and ETSI GS NFV IFA013 [23] specifications. - -For the Shared O-RU: - -- **Active push by Shared O-RU (producer)** – The Shared O-RU pushes performance data to the O-DU. - - **Event notifications** – The Shared O-RU sends performance measurement information through event notifications to the O-DU by establishing a new connection for each data reporting session. -- **Active collection by O-DU (consumer)** – The O-DU can actively collect data from the Shared O-RU. - - **Attributes** - The performance data is read by the O-DU. The O-DU can invoke a Remote Procedure Call (RPC) towards O-RU giving the O-RU all information it needs to send PM file. Then, the O-RU acts as sftp client and performs file upload to pointed to location. - -NOTE 1: The Shared O-RU does not support streaming-based reporting. - -NOTE 2: The Shared O-RU cannot act as a sftp server but can act as a sftp client. Thus, the Shared O-RU can upload files to a designated location. - -#### 4.20.1.7 Antenna Line Device (ALD) control use case of a Shared O-RU for Single-MNO - -This sub-use case applies to the running/operation of Shared O-RU. - -This sub-use case describes the operation of antenna line devices with the Shared O-RU. This sub-use case is triggered after the O-DUs have configured the partitioned carrier information of a Shared O-RU. The actors are one of the O-DUs, and Shared O-RU. The objective that the use case accomplishes is for the selected O-DU to operate the ALD controller and control the ALD connected to the Shared O-RU. - -ALD control is an end-to-end operation from the operator using the SMO at one end issuing operations to the O-DU and realising that ALD operation through the O-RU on through to the terminating ALD device at the other end. - -Because there is a single ALD controller, and the Shared O-RU can be connected to multiple O-DUs, one of them needs to be nominated as the ALD controller. - -There are many types of operations for ALD control. These include but not limited to software update of ALD devices, setting of RET mechanical/electrical tilt setting, reset of ALD devices, etc. - -#### 4.20.1.8 Basic resiliency use case (active O-DU failure) for Single-MNO - -This sub-use case describes system recovery from a failure (operational state = disabled) of the active O-DU#1 or O-DU switchover may be triggered by SMO in reactions to failure or due to operator's activity for a Shared O-RU in Single-MNO deployment. A switch of the active O-DU to standby O-DU is done. This sub-use case only applies to the hierarchical management of the O-RU. - -The actors are the SMO, O-CU, O-DUs, and Shared O-RU. The actors work together to recover operation from O-DU(s) failures. - -This basic resiliency sub-use case, covers failure of the active O-DU#1 that is unable to provide service. For example, when SMO detects that O-DU is out of service, the SMO assumes operational state for such O-DU as “disabled” and triggers recovery action for cells served by such O-DU. This use case covers a flow of operations that occurs in this situation. - -This use case is triggered when the active O-DU fails (operational state = disabled). - -This use case describes the switch-over of the other O-DU to become the new active O-DU. - -#### 4.20.1.9 Antenna calibration sub-use case of a Shared O-RU for Single-MNO - -This sub-use case applies to the running/operation of Shared O-RU. - -This sub-use case describes the operation of antenna calibration using a Shared O-RU. This sub use case is triggered after the O-DUs have configured the partitioned carrier information of a Shared O-RU. The actors are the O-DUs, and Shared O-RU. The objective that the use case accomplishes is for the Shared O-RU to be able to perform antenna calibration when connected to multiple O-DUs. - -It is typically initiated from the Shared O-RU when it detects that antenna calibration is necessary, which then sends a notification to the O-DU. - -If supported by the O-RU, the O-DU may also set an automatic antenna calibration setting which enables the Shared O-RU to automatically perform antenna calibration. - -#### 4.20.1.10 Rehoming use case of a Shared O-RU for Single-MNO - -This sub-use case describes how a Shared O-RU is rehomed within a network and paired with new parent O-DUs. Rehoming is the process of associating new management (parent) O-DUs with a Shared O-RU. This might be a virtual rehoming in a cloud native deployment, management-requested parent rehoming, or a physical move of the Shared O-RU whereby the Shared O-RU is connected and communicating to new parent O-DUs. - -Rehoming is typically done deliberately. Resiliency flows has some similarity to the rehoming flow; however, the difference is that resiliency is a reaction to a fault in the system, whereas rehoming is typically a planned activity. - -Some typical reasons why rehoming is done is as follows: - -- **Replanning or changing a network** – Altering a network resulting from physical construction work or network optimization may cause an MNO to replan their network necessitating a Shared O-RU to rehome. -- **New greenfield network** – When a new greenfield pocket deployment is created within a brownfield deployment rehoming might happen. -- **Service management-level operations** – The MNO may trigger a rehoming operation for the Shared O-RU which can happen for a variety of purposes. -- **Physical move a Shared O-RU** – The Shared O-RU is physically moved from one location to another. -- **Evolving a network** – The site might be changed from a non-Shared O-RU configuration to a Shared O-RU configuration which will require rehoming as at least there is a new second O-DU now connected to the O-RU. -- **Partnership with a new MNO** – Changing from a Single-MNO type configuration to a Multi-MNO configuration may require the Shared O-RU to be rehomed. -- **Maintenance activities** – When troubleshooting a failure, or other various maintenance activities may cause a Shared O-RU to be rehomed. -- **Parent failure** – The failure of a parent O-DU(s) may result in rehoming of a Shared O-RU being necessary. - -To illustrate an example of rehoming, suppose there is a Shared O-RU with identity #700 that currently exists in an edge cloud with CloudID #20 with parents, O-DU #1 and O-DU #2. And it is physically moved to a different edge cloud CloudID #900 and then subsequently reconnected to new different parent O-DUs, O-DU #19 and O-DU #24. Rehoming is a software-based operation, however, to physically move a Shared O-RU would also require the associated physical front-haul connections to be made. - -O-CUs and O-DUs can also be rehomed to new management entities (SMO). However, this sub-use case will only focus on when a Shared O-RU is rehomed to new O-DU parents. There are two basic forms of rehoming, one that is a physical move of the Shared O-RU and other is a deliberate management level operation: - -**Physical rehoming** – In this kind of rehoming, the Shared O-RU is physically moved from one location to another. There are two cases where after the physical move, the Shared O-RU has either new O-DU parents or stays with the original O-DU parents. For a Shared O-RU this means that the front-haul connections will be separated and reconnected. This may also entail LCM operations, where a Shared O-RU is decommissioned and then subsequently recommissioned and reinstalling with new parent O-DU. These would fall into common LCM operations. Physical rehoming can also happen during maintenance operations, where a Shared O-RU might be disconnected and reconnected to new parent O-DUs for a variety of reasons. - -**Management initiated rehoming** – Management initiated and coordinated rehoming of a Shared O-RU is when the Shared O-RU is given new O-DU parents done at the SMO. This may happen for a variety of reasons and is expected to be an intentionally planned activity. The management entity of the Shared O-RU may be the O-DU in the hierarchical case or SMO in a hybrid configuration. The new parent O-DU may have different carrier support, capabilities, and capacities of than the former parent; for example, it might be more energy efficient with less capabilities or it might an expanded more powerful O-DU. - -#### 4.20.1.11 Reset use case of a Shared O-RU for Single-MNO - -The reset of a Shared O-RU sub-use case describes the operations related to taking a Shared O-RU out of service and resetting it. - -There are some important aspects to reset of Shared O-RU. Only the Shared O-RU host would have permissions to perform the reset operation. - -In a multiple MNO configuration, reset operations would need to be coordinated between operators. The Shared O-RU host operator has the permission to perform the reset of a Shared O-RU. It would expect that the Shared O-RU host operator would try to coordinate with the Shared Resource Operator (SRO). This can entail something as simple as those two operators talking to each other; it can also entail automated coordination between management entities of these operators. The reset of a Shared O-RU would impact Availability, Reliability, and Maintenance (ARM) metrics, and uptime KPIs. - -The reset of a Shared O-RU operation is the basis for maintenance activities, debugging operations, the physically moving, physical rehoming, and recovery from malfunctions of the Shared O-RU. - -There are situations where the Shared O-RU would autonomously reset itself. When the Shared O-RU has lost M-plane connectivity to all of its connected O-DUs the Shared O-RU would autonomously reset itself. This would be the same as if the O-RU was not in a shared configuration. - -A software update will result in a reset of the Shared O-RU. The software update of a Shared O-RU is expected to be coordinated between the Shared O-RU host and the SRO. - -Before removing the Shared O-RU from service, the Shared O-RU carriers and its associated cells on O-DU/O-CU shall be deactivated. - -#### 4.20.1.12 Advanced resiliency sub-use cases of a Shared O-RU for Single-MNO - -Advanced resiliency sub-use cases provide descriptions for the resiliency operations where any of O-DUs or Shared O-RU have either partially failed (for instance, when the availability status is “degraded” for any of them), completely failed (when the operational state is “disabled”), or when there are failures detected in the interfaces (like the FH-C/U/S/M plane, F1, E2, and O1). - -The key actors in this scenario are the SMO, O-CU, O-DUs, and Shared O-RU. These entities may collaborate to recover or maintain operations in the event of partial O-DU(s) failures, software issues, interface disruptions, power outages, connectivity failures, and loss of synchronization. - -This use case shall be triggered when at least one of the aforementioned failures occurs in the network. - -#### 4.20.1.13 Load-balancing sub-use case of a Shared O-RU - -Load-balancing is a use case where relevant actors can reallocate Shared O-RU resources based on triggers, metrics, or policies. - -A key actor is a policy-enforcer that makes Shared O-RU resource allocation decisions based on inputs from measurements. For example, measurements can indicate the amount of traffic on each of the two O-DUs connected to the Shared O-RU. The policy-enforcer decides when a reallocation of Shared O-RU resources is needed. For example, if the policy-enforcer observes that one O-DU has a disproportionate amount of traffic (e.g., more users per MHz) than the other O-DU, the policy-enforcer makes a decision to re-allocate a component carrier from one O-DU to the other O-DUs. - -The policy-enforcer role could be played by the SMO/Non-RT RIC or the Near-RT RIC, depending on the time granularity of load balancing decision-making needed. There are limitations that are governed from the air interface which will influence the mechanisms and time granularity for load balancing. Policies can reflect a variety of triggers or mechanisms to be used to balance traffic or carriers. These might include guaranteed bandwidth, O-DU computational load/capacity (processor occupancy), and time of day triggers among others. Whatever the policy rules are and how often they are evaluated, the policy-enforcer would evaluate the situation, probably periodically, and make a resource re-allocation decision. - -#### 4.20.1.14 Coordinated reset of a Shared O-RU sub-use case for Multi-MNO - -The coordinated reset of a Shared O-RU sub-use case describes the operations related to resetting a Shared O-RU when there are multiple Shared Resource Operator (SRO) O-DUs connected to the Shared O-RU. - -In a multiple MNO configuration, reset operations would need to be coordinated between operators. The active Shared O-RU Host (SOH) operator coordinates the reset of a Shared O-RU. The definition of the active SOH is a SOH that has a state = active. The active SOH can perform a reset on its own volition. The active Shared O-RU Host (SOH) coordinates the reset operation; thus, the SROs can request a reset of the Shared O-RU to be performed by the active SOH. So, the active SOH approves or rejects a reset request of the Shared O-RU coming from other SROs. If the request is accepted by the active SOH, the x would inform all the other SROs x. Then the SOH would perform the reset of the Shared O-RU. If the SOH rejects the operation, then the SOH that originated the SRO that the command was rejected. The SOH can reject a command for example in the middle of a software update or other possible conditions that might prohibit a reset. The reset of a Shared O-RU would impact availability, reliability, and maintenance (ARM) metrics, and uptime KPIs. - -The reset of a Shared O-RU operation is the basis for maintenance activities, debugging operations, the physically moving, physical rehoming, and recovery from malfunctions of the Shared O-RU. - -Before removing the Shared O-RU from service, the Shared O-RU carriers and its associated cells on O-DU/O-CU shall be deactivated. - -The reset of a Shared O-RU is a “hard reset”. - -There can be other variations of coordinated reset of a Shared O-RU possibly based on a policy. - -#### 4.20.1.15 Management of Shared O-RU during O-DU software update sub-use case for Shared O-RU for Single & Multi-MNO - -As part of WG6 Cloudification and Orchestration Use Cases and Requirements for O-RAN, a generic case of software upgrade of network function is described. In the practical implementation context, a variety of strategies are incorporated for updating the network function with a new software version, with the objective of minimizing the impact of modifications and mitigating any disruptions to the overall service delivered to end users. These strategies include well-established practices such as Canary update, Rolling update, Blue/Green update etc. The choice of a specific approach relies on various factors such as the extent of the changes, the associated risk potential, and the cost of incorporating the change. Moreover, such changes necessitate careful consideration of dependencies and the need to re-provision and optimize resources accordingly. Furthermore, it is crucial to incorporate contingency/mitigation plans in the event that the software update does not align with the intended plan for implementing the changes. - -This sub-use case focuses on the management of Shared O-RU during the software update of O-DU. It is a critical consideration for Shared O-RU, particularly when O-RU resources are shared between the updated O-DU and existing O-DUs. To address this, well-defined procedures are necessary to identify the specific O-RU that can be shared, determine the particular O-DU with which the O-RU resources can be shared, and optimize the shared resources effectively. Prior to the software update, it can be essential to identify the candidate O-DU and associated O-RU resources that requires evacuation, thereby necessitating the provisioning of target RAN nodes. Moreover, in the event of performance degradation or negative impact on performance indicators following the completion of O-DU software update and activation, it is essential to establish efficient risk mitigation strategies and evaluate possibility of rolling back the introduced changes. - -Here the consideration of the Shared O-RU arises from the need to minimize the impact of the software update of O-DU. This is achieved by validating the update with minimal traffic or allocating minimal resources, thereby effectively reducing the footprint of affected end users. Utilizing a Shared O-RU effectively fulfils this objective which otherwise can require deployment of dedicated O-RUs solely for validating the O-DU software update. An additional aspect to be considered is the prevention of Shared O-RU restart following a software update at the O-DU level. This is particularly relevant as a software update on the O-DU can entail the establishment of m-lane connections and initiation of the call home procedure, both of which typically require an O-RU restart to be initiated. - -A high-level view of the software update scenario of O-DU wherein the software (SW) updated O-DU shares the O-RU resources with an existing O-DU is shown in figure 4.20.1.15-1. - -![Diagram illustrating the shared O-RU management scenario during O-DU software update. The diagram shows the hierarchy: SMO at the top, connected to Near RT RIC via A1. Near RT RIC is connected to OCu-CP via E2. OCu-CP is connected to OCu-UP via E1. OCu-UP is connected to O-Du Version : n via F1-U. O-Du Version : n is connected to O-Ru via O-FH M-Plane/CUS Plane. O-Du Version : n+m (O-DU with Updated Software) is also connected to O-Ru via O-FH M-Plane. The diagram also shows O1 and O2 interfaces between SMO and Near RT RIC, and F1-C interfaces between OCu-CP and Near RT RIC.](23781f394f3709bc3a1e68044179b0d4_img.jpg) - -Diagram illustrating the shared O-RU management scenario during O-DU software update. The diagram shows the hierarchy: SMO at the top, connected to Near RT RIC via A1. Near RT RIC is connected to OCu-CP via E2. OCu-CP is connected to OCu-UP via E1. OCu-UP is connected to O-Du Version : n via F1-U. O-Du Version : n is connected to O-Ru via O-FH M-Plane/CUS Plane. O-Du Version : n+m (O-DU with Updated Software) is also connected to O-Ru via O-FH M-Plane. The diagram also shows O1 and O2 interfaces between SMO and Near RT RIC, and F1-C interfaces between OCu-CP and Near RT RIC. - -**Figure 4.20.1.15-1: Shared O-RU management scenario during O-DU software update** - -Shared O-RU management scenario during O-DU software update follows a high-level approach as given below: - -1. Selection of O-DU node for software update based on inventory, FM/PM data -2. Deployment and call-home procedures of O-DU -3. O-DU registration with O-CU, Near-RT RIC -4. Common aspect provisioning on Shared O-RU (e.g., ODU-ID, User account) based on SW updated O-DU -5. Selection of the policy for load sharing (e.g., load balancing policy, or selection based on cells having low priority user sessions, S-NSSAI, anticipated traffic, etc.) with the SW updated O-DU -6. O-RU initiates m-plane connection establishment with SW updated O-DU -7. Translation of the load sharing policy to O-RU configuration -8. Inactivation and evacuation of component carriers selected for allocation to SW updated O-DU -9. Provisioning of O-RU with carrier configuration details by SW updated O-DU (e.g., end points, list entries) -10. Activation of carrier configuration associated with SW updated O-DU -11. Initiate KPI and functional log monitoring of SW updated O-DU and associated O-RU resources -12. O-DU SW update mitigation : In case of degraded KPIs reverse SW update process of O-DU - -It is to be noted that this sub-use case does not differentiate based on the extent of change introduced to the O-DU through the software upgrade because it primarily depends on the implementation context. - -This use case does not enforce a specific policy for the SW update as this depends on the particular deployment and implementation choice. Such policies are typically incorporated to define the rules, control logic, constraints, and thresholds to be considered during the particular change being initiated. As an example, if an implementation scenario calls for such flexibility, the component carrier shifting could be omitted by utilizing appropriate SW update policy and limit only to the general health check after O-DU SW update. - -This use case introduces couple of new actors such as O-DU SW change management rApp. An O-DU SW update lifecycle can be managed using these optional functions or using appropriate implementation specific extensions of SMO function. - -Currently this use case considers only single operator Shared O-RU scenario. The impact of SW update on multi-operator Shared O-RU scenarios is not in scope of the current version of this sub-use case. - -#### 4.20.1.16 Resource partitioning sub-use case for Multi-MNO configuration - -This sub-use case describes the procedures of how to decide on the partitioning of a Shared O-RU in a Multi-MNO configuration where one O-DU belongs to an owner operator (MNO) and at least one other O-DU belongs to a participating operator (MNO). The actors are the owner operator MNO sharing co-ordinator, the participating operator MNO sharing co-ordinator, the owner operator SMO, the participating operator MNO SMO, the owner operator resource partitioning rApp, and participating operator MNO resource partitioning rApp. The owner operator MNO sharing co-ordinator retrieves the inventory from the owner operator SMO and decides on how to partition the resources of a Shared O-RU. The owner operator MNO sharing co-ordinator uses the owner operator resource partitioning rApp to partition the resources of a Shared O-RU between multiple O-DUs. The outcome is that the owner operator resource partitioning rApp has details on how a Shared O-RU's resource are to be partitioned. - -#### 4.20.1.17 Start-up sub-use case of for Multi-MNO configuration - -This sub-use case describes the start-up of a Shared O-RU in a Multi-MNO configuration where one O-DU belongs to an owner operator (MNO) and at least one other belongs to a participating operator (MNO). The actors are the owner operator SMO, participating operator SMO, the connected O-DUs, the Shared O-RU, and their interactions that are needed for a Shared O-RU to boot up and enter into operation. The outcome is that the Shared O-RU is operating with the necessary - -software version and has established network connectivity with the O-DUs and, for hybrid deployments, the corresponding SMOs. The start-up for a Shared O-RU is a basis for some of the other Shared O-RU sub-use cases. - -#### 4.20.1.18 Supervision sub-use case for Multi-MNO configuration - -This sub-use case applies to the running or operation of Shared O-RU in a Multi-MNO configuration where one O-DU belongs to an owner operator (MNO) and at least one O-DU belongs to a participating operator (MNO). - -This sub-use case describes the supervision operations of the Shared O-RU. It is triggered after the connected O-DUs have configured the partitioned carrier information of a Shared O-RU. It is invoked during run-time. The actors are the owner operator SMO, participating operator SMO, the connected O-DUs, and Shared O-RU. The objective that the use case accomplishes is the establishment of watchdog supervision of the Shared O-RU by multiple O-DUs. Supervision enables the Shared O-RU to autonomously cease transmitting on a partitioned carrier if it loses supervision with the O-DU responsible for that carrier. - -#### 4.20.1.19 Antenna Line Device (ALD) control sub-use case for Multi-MNO configuration - -This sub-use case applies to the running or operation of Shared O-RU in a Multi-MNO configuration where one O-DU belongs to an owner operator (MNO) and at least one other belongs to a participating operator (MNO). - -This sub-use case describes the operation of Antenna Line Devices (ALD) with the Shared O-RU. This sub-use case is triggered after the connected O-DUs have configured the partitioned carrier information of a Shared O-RU. The actors are one of the O-DUs, and Shared O-RU. The objective that the use case accomplishes is for the selected O-DU to operate as the ALD controller and control the ALD connected to the Shared O-RU. - -ALD control is an end-to-end operation from a technician using the owning operator or participating operator SMO at one end issuing operations to the O-DU and realising that ALD operation through the O-RU on through to the terminating ALD device at the other end. - -Because there is a single ALD controller, and the Shared O-RU can be connected to multiple O-DUs, one of them needs to be nominated as the ALD controller. It is expected that an O-DU of the owning operator would be the ALD controller (but not necessarily). - -There are many types of operations for ALD control. These include but not limited to software update of ALD devices, setting of RET mechanical/electrical tilt setting, TMA updates, reset of ALD devices, etc. - -NOTE: Only the host O-DU (of the owner operator) can control the ALD and the participating operator O-DU would not be able to control the ALD devices. - -#### 4.20.1.20 Antenna calibration sub-use case for Multi-MNO configuration - -This sub-use case applies to the running or operation of Shared O-RU in a Multi-MNO configuration where one O-DU belongs to an owner operator (MNO) and at least one other belongs to a participating operator (MNO). - -This sub-use case describes the operation of antenna calibration using a Shared O-RU. This sub-use case is triggered after the O-DUs have configured the partitioned carrier information of a Shared O-RU. The actors are the connected O-DUs, and Shared O-RU. The objective that the use case accomplishes is for the Shared O-RU to be able to perform antenna calibration when connected to multiple O-DUs. - -#### 4.20.1.21 Rehoming use case of a Shared O-RU for Multi-MNO - -This is rehoming the Shared O-RU in a Multi-MNO configuration where different O-DU (parents of the Shared O-RU) are now under the management of different MNOs. Some considerations among others in the Multi-MNO configuration are that there might be different configuration, security concerns, role based access privileges, physical security, coordination between the two MNOs technicians when performing maintenance activities that require rehoming the Shared O-RU. - -For the Multi-MNO configuration, the three basic forms of rehoming, physical rehoming where the Shared O-RU is physically moved (with original O-DU parents or new O-DU parents), and management initiated rehoming caused from management level planned activities still apply to the Multi-MNO case. - -#### 4.20.1.22 Performance management use case of a Shared O-RU for Multi-MNO - -This sub-use case applies to the running/operation of Shared O-RU. - -This sub-use case describes the performance management operations of the Shared O-RU in a Multi-MNO configuration. Here the Shared O-RU is connected to O-DUs that are owned by different MNOs. This sub-use case is triggered after the O-DUs have configured the partitioned carrier information of a Shared O-RU. It is also invoked during run-time. The actors are the O-DUs, and Shared O-RU. The objective that the use case accomplishes is for each O-DU to establish subscriptions to receive performance management notifications regarding operation of the fronthaul between the O-DUs and Shared O-RU. - -The sub-use case also describes how performance management logs, data and files are passed from the Shared O-RU to the connected O-DUs and data from O-DUs to SMO. Performance measurement data and telemetry information should be supported in three basic ways. - -The same mechanisms described in performance measurement reporting for Single-MNO are also supported in a Multi-MNO configuration. The O-DU supported active push through streaming and event notification methods. The O-DU supports active collection by a consumer through attribute based and data scraping. The O-DU supports file-based reporting. The Shared O-RU supports active push through event notifications and active collection from O-DU via RPC and sftp. See clause 4.20.1.6 for further details. The main difference between the Single-MNO configuration and the Multi-MNO configuration is that there are additional considerations for sending performance information to two different mobile network operators. This entails aspects of security and support for different subscription filters. As such, two MNOs may want different collected data, may have different security controls based on role-access, different subscription filters and session operation. For example, one MNO might employ NetConf and another MNO Virtual Event Streaming (VES) messaging. - -#### 4.20.1.23 Antenna calibration sub-use case of a Shared O-RU for Multi-MNO - -This sub-use case applies to the running/operation of Shared O-RU. This sub-use case describes the operation of antenna calibration using a Shared O-RU in a Multi-MNO configuration. This sub-use case is triggered after the O-DUs have configured the partitioned carrier information of a Shared O-RU. The actors are the O-DUs, and Shared O-RU. The objective that the use case accomplishes is for the Shared O-RU to be able to perform antenna calibration when connected to multiple O-DUs in a Multi-MNO configuration. - -This sub-use case is essentially the same as for the Single-MNO configuration except the O-DUs which are connected to different operators may coordinate. - -#### 4.20.1.24 Dynamic resource shifting - -Dynamic resource shifting is a Shared O-RU sub-use case related to how resources are moved to achieve improvements in performance. In this case, the resources that are shifted are fractions of radio spectrum utilized by cells. These resources correspond to PRBs and can be dynamically addressed by bandwidth parts. See 3GPP TS 38.211 [13], clause 4.4.5. - -This sub-use case describes how radio spectrum resources can be shifted between cells that use overlapping spectrum and are served by Shared O-RU. This is performed automatically and dynamically (autonomously) without the need to perform time-consuming cell reconfiguration process. - -The process of dynamic resource shifting is controlled by Near-RT RIC based on traffic-related KPIs or operator-defined parameters. Exact triggers for RIC to request for dynamic resource shifting are out of scope of this specification. - -Important drivers for this use case are as follows: - -- The use case shall deliver truly dynamic frequency resource shifting between cells. -- The use case shall preserve power consumption usage at the UE level. -- The use case shall utilize existing radio link control procedures. - -#### 4.20.1.25 Static resource shifting use case for Single-MNO - -The Shared O-RU resource shifting use case describes how cell(s)/carrier(s) and their resources are optimally reallocated between O-DUs to achieve performance improvements, and resource optimization. - -Static resource shifting is initiated by the SMO based on pre-configured triggers or policies, where it describes about how cell(s)/carrier(s) are moved between O-DUs. Two or more O-DUs connected to an O-RU utilize their respective carrier frequency resources exclusively during designated time periods, with potential optimization based on various resource reallocation requirements. O-RU configured with respective carrier frequency resources associated with two O-DUs, enabling the transfer of throughput between cells/carriers. This process involves the reconfiguration of cell and carrier resources between O-DUs to optimize performance. - -Important drivers for this use case are as follows: - -- The use case should provide mechanism for cell resource shifting between O-DUs. -- The use case shall utilize the existing cell/carrier configuration scenarios. - -### 4.20.2 Entity/resources involved in the use case - -#### 4.20.2.1 General aspects of entity/resources for Shared O-RU - -The following sub-clauses describe the entity/resources that are important and key players for each of the sub-use cases for Shared O-RU. Many of the sub-use cases will have a similar set of actors/entities/resources involved in realise the operation related to that sub-use case. - -In general, the identification of entity/resources serve as the basis for understanding a service model. The actors are trying to accomplish a particular goal, and the actions between the actors are the services that are the basis of a service model. The service model is a basis for an information model. - -Sometimes, the actors in the sub-use cases perform differing operations, and sometimes there is a variable number of entities depending on the function. - -#### 4.20.2.2 Resource partitioning use case of Shared O-RU for Single-MNO - -- 1) Sharing co-ordinator: - - a) Recovers the inventory of Shared O-RUs and O-DUs and determines how to partition the resources of a Shared O-RU between multiple different O-DUs. -- 2) SMO: - - a) Provides inventory of Shared O-RUs and O-DUs. - - b) Configures call home identities in external transport systems. -- 3) Shared O-RU orchestration rApp: - - a) Supports partitioning of individual carriers of a Shared O-RU between multiple different O-DUs operated by different operators. - -#### 4.20.2.3 Start-up use case of a Shared O-RU for Single-MNO - -- 1) Shared O-RU: - - a) Performs call home and triggers establishment of network management session. -- 2) SMO: - - a) Recovers the software inventory of Shared O-RU and decides whether to upgrade operational software of Shared O-RU (hybrid management model). -- 3) O-DU: - - a) Recovers the software inventory of Shared O-RU and decides whether to upgrade operational software of Shared O-RU (hierarchical management model). - -#### 4.20.2.4 Configuration use case of a Shared O-RU for Single & Multi-MNO - -- 1) SMO: - - a) Responsible for Shared O-RU common configuration (hybrid management model). - - b) Responsible for receiving notifications of modifications to Shared O-RU's configuration (Multi-MNO deployment model). -- 2) O-DU: - - a) Responsible for Shared O-RU common configuration (hierarchical management model). - - b) Responsible for Shared O-RU carrier configuration. -- 3) Shared O-RU orchestration rApp: - - a) Responsible for determining which O-DU performs Shared O-RU common configuration (hierarchical management model). - - b) Responsible for receiving notifications of modifications to Shared O-RU's configuration (Multi-MNO deployment model). -- 4) Shared O-RU: - - a) Responsible for notifying any subscriber of its modified configuration. -- 5) Sharing coordinator: - - a) Confirms that the Shared O-RU's configuration complies with a sharing agreement (Multi-MNO deployment model). - -#### 4.20.2.5 Supervision use case of a Shared O-RU for Single-MNO - -- 1) Shared O-RU: - - a) Responsible for operating supervision on a per O-DU basis. - - b) Responsible for de-activating carriers associated with O-DU if there is supervision failure by O-DU. - - c) Responsible for signalling alarm to subscribers if O-DU supervision is lost. -- 2) O-DU: - - a) Responsible for repeatedly resetting the Shared O-RU's supervision timer. -- 3) SMO: - - a) Responsible for subscribing to alarm notifications (hybrid management model). - - b) Responsible for forwarding alarm notifications to Shared O-RU orchestration rApp. - -#### 4.20.2.6 Performance management use case of a Shared O-RU - -- 1) Shared O-RU: - - a) Responsible for generating performance management notifications on a per partitioned carrier basis. -- 2) O-DU: - - a) Responsible for subscribing to receive performance management notifications from Shared O-RU. -- 3) SMO: - - a) The operator, or SMO, or another entity is an endpoint for the performance measurement data or reports. - -#### 4.20.2.7 Antenna Line Device (ALD) control use case of a Shared O-RU for Single-MNO - -The following actors are involved in the ALD control use case. - -- 1) Antenna line device control rApp (for the Shared O-RU): - - a) Responsible for determining which O-DU is responsible for ALD controller aspects. -- 2) O-DU: - - a) Responsible for implementing ALD controller. -- 3) Shared O-RU (hardware): - - a) Responsible for bridging between OFH and HDLC. -- 4) ALD (one or more ALD devices): - - a) Responsible for terminating HDLC. - -#### 4.20.2.8 Basic resiliency use case (active O-DU failure) for Single-MNO - -The description below outlines the actors involved: - -- 1) Shared O-RU: - - a) The Shared O-RU helps in detection of the O-DU connectivity/availability seen from O-RU perspective during a resiliency recovery operation. For example, when the active O-DU fails, the Shared O-RU informs other available and subscribed NetConf clients about the connection failure towards previously active O-DU. -- 2) O-DUs (host/tenant/ & other O-DUs): - - a) All the O-DUs connected to the Shared O-RU are actors that are relevant in some way during a resiliency operation. The active O-DU is main O-DU that performs the basic LCM and FCAPS functionality and terminates HDLC stack for ALDs operations connected to O-RU. In the various resiliency situations, where the active O-DU fails, then the other O-DU(s) connected to the Shared O-RU get involved in restoring the services for end users. -- 3) O-CU: - - a) O-CU receives cell related configurations from SMO and available cell details from O-DU(s). Based on the available resources reported by O-DU and desired availability of cells received from SMO, the O-CU activates or deactivates the cells in the O-DU using F1 interface. -- 4) SMO: - - a) Based on operator's decision, the SMO assigns initial O-DU roles (active, standby). - - b) The SMO makes high-level decisions related to failures and the various resiliency situations. For example, in a case where a O-DU is taken out of service, it might be intentionally removed, or physically removed permanently, which has impact to the Shared O-RU operation. - -#### 4.20.2.9 Antenna calibration use case of a Shared O-RU for Single-MNO - -The following are the principal actors in the antenna calibration use case for a Shared O-RU. - -- 1) Antenna calibration rApp (Shared O-RU): - - a) This App is responsible for determining which O-DU is responsible for the antenna calibration operation. -- 2) O-DU: - - a) Responsible for supporting Shared O-RU antenna calibration operation. -- 3) Shared O-RU (HW): - - a) Responsible for implementing antenna calibration. - -#### 4.20.2.10 Rehoming use case of a Shared O-RU for Single-MNO - -The following are the principal actors in the rehoming use case: - -- 1) Shared O-RU: - - a) The Shared O-RU is the entity that is being rehomed. -- 2) Original O-DUs: - -- a) The original O-DU(s) are the O-DUs that the Shared O-RU were originally attached to. -- 3) New O-DUs attached to: - - a) These are the new O-DU(s) that the Shared O-RU will now be attached to. -- 4) SMO: - - a) It is also possible to rehomed to a O-RU to a new management system (SMO). As such, the O-RU can be rehomed to a different SMO. For a hybrid configuration this would mean the O-RU is connected to a different SMO. - -#### 4.20.2.11 Reset use case of a Shared O-RU for Single-MNO - -The following are the principal actors in the [shut down/reset] of a Shared O-RU use case. - -- 1) Shared O-RU: - - a) The Shared O-RU is the entity that is being affected by the operation ([shutdown/reset]). -- 2) The [primary/host] O-DU: - - a) The [primary/host] O-DU for the Shared O-RU is the managing entity that will execute the command. -- 3) SMO: - - a) The operator using the SMO can issue the shut-down/reset command, and starts the use case for the operation. - -#### 4.20.2.12 Advanced resiliency sub-use cases of a Shared O-RU for Single-MNO - -The following description details the actors involved in the advanced resiliency sub-use cases of a Shared O-RU: - -- 1) Shared O-RU: - -The Shared O-RU acts as actor in M-plane session supervision towards O-DU. As such O-RU detects M-plane link breaks and reports them in form of alarms towards other NetConf clients who still have active M-plane links with O-RU. - -NOTE: If there is no client with active M-plane session available - the O-RU performs autonomous reset. -- 2) O-DUs (active/stand-by): - - a) All the O-DUs connected to the Shared O-RU are actors during a resiliency operation. The active O-DU performs the LCM, FCAPS functionality, and ALD operations with the O-RU. In various resiliency scenarios, when the active O-DU fails, the SMO may decide to trigger the O-DU role change (active/standby) to restore service availability for end users. -- 3) SMO: - - a) Based on operator's decision, the SMO assigns initial O-DU roles (active, stand-by). The SMO may then decide to perform switch between O-DU's roles for specific O-DUs initially "paired" by operator based on alarms/performance counters/operator's decision. - -NOTE: The sub-use cases assume the hierarchical deployment scenarios. - -#### 4.20.2.13 Load-balancing sub-use case of a Shared O-RU - -The following description details the actors involved in the resiliency use case of a Shared O-RU: - -- 1) Shared O-RU: - - a) The Shared O-RU is actor that has its resources adjusted by the policy enforcer. -- 2) O-DUs (host/tenant/ & other O-DUs): - - a) All the O-DUs connected to the Shared O-RU are actors that are relevant because they perform the load balancing working with the O-RU. They can also provide measurements relevant to the load-balancing policy. -- 3) Policy enforcer (SMO, RIC, etc): - - a) The policy enforcer is an actor that executes the load-balancing policy. The policy defines the characteristics, triggers, and timing of how and when load-balancing occurs. - -#### 4.20.2.14 Coordinated reset of a Shared O-RU sub-use case for Multi-MNO - -The following description details the actors involved in the coordinate reset of a Shared O-RU use case: - -- 1) Shared O-RU: - - a) The Shared O-RU is actor that would be reset from the host O-DU. -- 2) Shared O-RU Host (SOH): - - a) The SOH coordinates and issues the coordinate reset of a Shared O-RU. -- 3) Shared Resource Operators (non-SOH SROs): - - a) All the O-DUs connected to the Shared O-RU are actors that are relevant because they can request a coordinate reset also for the Shared O-RU. -- 4) SMO/Operator: - - a) The SMO operator can initiate a coordinated reset for the Shared O-RU. -- 5) Partner SMO/Partner operator - - a) The SMO/partner operator can initiate a coordinated reset for the Shared O-RU. - -#### 4.20.2.15 Management of Shared O-RU during O-DU software update sub-use case for Shared O-RU for Single & Multi-MNO - -The following description details the actors involved in the management of Shared O-RU during the SW update of O-DU subusecase: - -- 1) Shared O-RU: - - The Shared O-RU which has its resources shared with the SW updated O-DU and other O-DUs. -- 2) O-DU SW change management rApp: - - The rApp that supports SMO and Non-RT RIC in managing the SW change of the O-DU. This is an optional functionality which can alternately be implemented as an extended capability in one of the existing SMO functions. The capabilities of the O-DU SW change management rApp includes but not limited to the following: - - a) Validation of change management plan & impact assessment. - - b) Identification of the candidate Shared O-RU resources that can be shared based on the change plan and associated policies. - - c) Identification of the candidate O-DU for SW update. - - d) Translation of change management plan to O-DU and O-RU configurations. - - e) Recommendation of the configuration for Shared O-RU provisioning for m-plane setup with updated O-DU. - - f) Recommendation of configuration for traffic evacuation of Shared O-RU and O-DU before the O-DU SW update. - - g) Monitoring and management of SW update by coordinating with other SMO functions, Shared O-RU and rApps. - - h) Management of fallout scenarios and recovery. -- 3) Shared O-RU orchestration rApp: - - Supports partitioning of individual carriers of a Shared O-RU between updated O-DU and other O-DUs. This is an optional functionality which can alternately be implemented as an extended capability in one of the existing SMO functions. -- 4) SMO: - - Maintains inventory of Shared O-RUs and O-DUs. - - Configures O-DUs and O-RUs with the support of the rApps. - - Subscribe to alarms, notifications and measurements from O-DU and O-RU. - - Sharing of alarm, notification and measurements from O-DU and O-RU with the rApps. -- 5) O-DU SW planner: Personnel: - - Prepares O-DU SW change management strategy and associated plan. Based on the strategy and plan O-DU SW planner identifies the right software version, prepares target O-DU identification policies (for e.g., least - -loaded O-DU), Shared O-RU load sharing criteria (e.g., component carrier to be allocated), identifies carrier evacuation criteria, etc. - -- 6) Sharing coordinator: Personnel: - - Confirms that the Shared O-RU's configuration complies with a sharing policy defined as per the O-DU SW change management requirement. -- 7) Updated O-DU: - - Responsible for load sharing the O-RU resources such as component carriers with other active O-DUs. -- 8) Original O-DUs: - - The original O-DU(s) are the O-DUs that the Shared O-RU were originally attached to. - -#### 4.20.2.16 Resource partitioning use case of Shared O-RU for Multi-MNO configuration - -- 1) Owning operator sharing coordinator: - - a) Recovers the inventory of Shared O-RUs and O-DUs and determines how to partition the resources of a Shared O-RU between multiple different O-DUs. -- 2) Owning operator SMO: - - a) Provides inventory of Shared O-RUs and O-DUs. - - b) Configures call home identities in external transport systems. -- 3) Shared O-RU owning operator orchestration rApp: - - a) Supports partitioning of individual carriers of a Shared O-RU between multiple different O-DUs operated by different operators. -- 4) Participating operator SMO: - - a) Handles management of participating operator O-DU. - -#### 4.20.2.17 Start-up use case of a Shared O-RU for Multi-MNO configuration - -- 1) Shared O-RU: - - a) Performs call home and triggers establishment of network management session. -- 2) Owning operator SMO: - - a) Recovers the software inventory of Shared O-RU and decides whether to upgrade operational software of Shared O-RU (hybrid management model). -- 3) Participating operator SMO: - - a) Handles management of participating operator O-DU. -- 4) Owning operator O-DU: - - a) Recovers the software inventory of Shared O-RU and decides whether to upgrade operational software of Shared O-RU (hierarchical management model). -- 5) Participating operator O-DU: - - a) Expected to be a Shared O-RU Operator (SRO). The participating operator O-DU handles configuration of its component carriers with the Shared O-RU that it is connected to and has a communication link up. - -#### 4.20.2.18 Supervision use case of a Shared O-RU for Multi-MNO configuration - -- 1) Shared O-RU: - - a) Responsible for operating supervision on a per O-DU basis. - - b) Responsible for de-activating carriers associated with O-DU if there is supervision failure by O-DU. - - c) Responsible for signaling alarm to subscribers if O-DU supervision is lost. -- 2) Owning operator O-DU: - - a) Responsible for repeatedly resetting the Shared O-RU's supervision timer. -- 3) Participating operator O-DU: - - a) Expected to be a Shared O-RU Operator (SRO). Has a heartbeat timer with the Shared O-RU that it is connected to and has a communication link up. -- 4) Owning operator SMO: - - a) Responsible for subscribing to alarm notifications (hybrid management model). - -- b) Responsible for forwarding alarm notifications to Shared O-RU orchestration rApp. -- 5) Participating operator SMO: - - a) Handles management of participating operator O-DU. - -#### 4.20.2.19 Antenna Line Device (ALD) control use case of a Shared O-RU for Multi-MNO configuration - -The following actors are involved in the ALD control use case. - -- 1) Owning operator antenna line device control rApp (for the Shared O-RU): - - a) Responsible for determining which O-DU is responsible for ALD controller aspects. -- 2) Owning operator O-DU: - - a) Responsible for implementing ALD controller. -- 3) Participating operator O-DU: - - a) Expected to be a Shared O-RU Operator (SRO). Does not perform any operations directly with ALD until it becomes host under failure situations. -- 4) Participating operator SMO: - - a) Handles management of participating operator O-DU. -- 5) Shared O-RU (hardware): - - a) Responsible for bridging between OFH and HDLC. -- 6) ALD (one or more ALD devices): - - a) Responsible for terminating HDLC. - -#### 4.20.2.20 Antenna calibration use case of a Shared O-RU for Multi-MNO configuration - -The following are the principal actors in the antenna calibration use case for a Shared O-RU. - -- 1) Owning operator antenna calibration rApp (Shared O-RU): - - a) Responsible for determining which O-DU is responsible for configuring common aspects of antenna calibration. -- 2) Owning operator O-DU: - - a) Responsible for supporting Shared O-RU coordinated calibration. -- 3) Participating operator O-DU: - - a) Expected to be a Shared O-RU Operator (SRO). The participating operator O-DU does not perform calibration operations. -- 4) Shared O-RU (HW): - - a) Responsible for implementing coordinated calibration. - -#### 4.20.2.21 Rehoming use case of a Shared O-RU for Multi-MNO - -The following are the principal actors in the rehoming use case for Multi-MNO: - -- 1) Shared O-RU: - - a) The Shared O-RU is the entity that is being rehomed. -- 2) Original O-DUs: - - a) The original O-DU(s) (the owning operator O-DU and participating operator O-DU) are the O-DUs that the Shared O-RU were originally attached to. These O-DUs belong to different MNOs (the owning MNO and participating MNO). -- 3) New O-DUs attached to: - - a) These are the new O-DU(s) (the owning operator O-DU and participating operator O-DU) that the Shared O-RU will now be attached to. These O-DUs belong to different MNOs. The new O-DU(s) could be different O-DUs than the original O-DU(s). -- 4) Owning operator SMO: - - a) The owning operator SMO connects the owning operator O-DU to the Shared O-RU. - -- 5) Participating operator SMO: - - a) The participating operator SMO connects the participating operator O-DU which is connected to the Shared O-RU. - -#### 4.20.2.22 Performance management use case of a Shared O-RU for Multi-MNO - -- 1) Shared O-RU: - - a) Responsible for generating performance management notifications on a per partitioned carrier basis. -- 2) Managing operator O-DU: - - a) Responsible for subscribing to receive performance management notifications from Shared O-RU. -- 3) Participating operator O-DU: - - a) The O-DU of the participating operator that is also connected to the Shared O-RU. -- 4) Managing operator SMO: - - a) The managing operator SMO, or another entity is an endpoint for the performance measurement data or reports. -- 5) Participating operator SMO: - - a) The SMO of the participating operator which is an endpoint for the performance measurement data or reports from the participating operator O-DU. - -#### 4.20.2.23 Antenna calibration use case of a Shared O-RU for Multi-MNO - -The following are the principal actors in the antenna calibration use case for a Shared O-RU. - -- 1) Antenna calibration rApp (Shared O-RU) of owning operator (SMO): - - a) The owning operator App is responsible for telling the owning operator O-DU that it is responsible for the antenna calibration operation. -- 2) Owning operator O-DU, participating operator O-DU: - - a) The owning operator O-DU is responsible for supporting Shared O-RU antenna calibration operation. -- 3) Shared O-RU (HW): - - a) Responsible for implementing antenna calibration. - -#### 4.20.2.24 Dynamic resource shifting use case of a Shared O-RU - -The following are the principal actors in the dynamic resource shifting use case: - -- 1) Shared O-RU: - - a) The Shared O-RU is the entity that serves cells to the air. -- 2) O-DU1, O-DU2: - - a) Responsible for processing of user data and radio resource handling. -- 3) SMO: - - a) Responsible for configuration of Near-RT RIC, O-DUs and O-RU (used architecture does not matter for this sub-use case). -- 4) Near-RT RIC: - - a) Responsible for control of dynamic resource shifting between cells served by cooperating O-DUs. - -#### 4.20.2.25 Static resource shifting use case for Single-MNO - -The following are the actors in the static resource shifting use case: - -- 1) Shared O-RU: - - a) The Shared O-RU is the entity that serves cells to the air. - - b) The Shared O-RU terminates open fronthaul interface towards O-DU(s) and optionally towards SMO. -- 2) O-DU1, O-DU2: - - a) Responsible for processing of user data and handle radio resources. - - b) O-DU(s) terminate open fronthaul interface towards O-RU. - -- c) O-DU(s) terminate F1 interface towards O-CU. -- 3) O-CU: - - a) O-CU terminates F1 interface towards O-DU(s). - - b) O-CU is responsible for RRC protocol handling for UEs. -- 4) SMO: - - a) Responsible for configuration of O-CU, O-DUs and O-RU (depending on deployment SMO configures O-RU directly or through O-DU). - - b) In hybrid deployment SMO terminates open fronthaul interface towards O-RU. - -### 4.20.3 Solution - -#### 4.20.3.1 General aspects of solutions for all Shared O-RU use cases - -The following clauses describe solutions that apply to each of the sub-use cases. They describe different solutions for key aspects of Shared O-RU operation, such as the start-up, configuration, supervision, and performance management among other things. There are a few general aspects of each of these solutions that share similar goals, assumptions, actors, and roles and are captured in table 4.20.3.1-1. - -**Table 4.20.3.1-1: General aspects of solutions for all Shared O-RU use cases** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Common Goals |

All the following sub-use cases involve either getting the Shared O-RU operational or keeping it operational. Each of the sub-use cases explore a different aspect of these two common goals. Each of the sub-use cases has a different specific goal and is trying to accomplish a particular dimension of Shared O-RU operation. This sub-use case is only applicable to the hierarchical configuration.

Bringing into operation – Many of the sub-use cases have the goal to get the Shared O-RU operational and capable of supporting over the air traffic. These include the resource partitioning, start-up, configuration, and supervision sub-use cases. They are “day 0” related use cases.

Maintaining service – The other set of sub-use cases are related to maintaining service. These include the supervision, performance, and resiliency sub-use cases. These use cases relate to the continued operation of the Shared O-RU, thus “day 2” operation.

| | -| Common Actors |

The Shared O-RU and the multiple O-DUs that the Shared O-RU is connected to are common actors that apply to all the following sub-use cases.

The common configurations that apply to the sub-use cases many also involve the management system between two operators.

Some actors can be controlled by different operators and / or provided by different solution providers.

| | -| Common Assumptions |

For the following sub-use cases it is assumed that all relevant functions and components are instantiated.

Inventory management systems identify Shared O-RU and the available O-DUs as inventory elements.

For all of the sub-use cases, an O-RU resources are statically partitioned between O-DUs (static configuration)

| | - -All the sub-use cases also apply a set of common configurations. These sub-use cases are intended to apply to Single Operator (MNO) and Multiple Operator (MNO) configurations. The configurations will be important to service providers, wireless operators as they roll out new networks. Those configurations can then be further broken down into either hybrid or hierarchical configurations. In a hierarchical configuration the SMO performs configuration and FCAPS/LCM with the O-DU which in does that for the O-RUs. In a hybrid configuration, the SMO can perform operations with either the O-DU and/or the O-RU. The O-DUs that share the O-RU can be from either common or different vendors. It can be envisaged that many more possible configurations or variations of those basic configurations could be supported by the following sub-use cases. For example, more than just two O-DUs. Sub-use cases present solutions that are intended to apply to all these possible configurations. Exceptions can arise from the variations of the resiliency sub-use case. - -The collection of the sub-use cases either bring a Shared O-RU into operation by performing vital aspects of getting a Shared O-RU initially working; or they try to keep a Shared O-RU operational. Additionally, these sub-use cases apply to some other use cases such as class 2 BBU pooling (BBU pooling to achieve RAN elasticity use case), RAN sharing, and advanced multi-vendor multi-operator network slicing operation (multi-vendor slices). Support for different configuration, resiliency operation and, supervision that apply to Shared O-RU will often be relevant to these other related use cases as well. These other related use cases can use the following sub-use cases as building blocks operations because they provide basic goals and objectives to getting a Shared O-RU operational and keeping it running. Thus, the sub-use cases are likely be applicable to many those use cases outside of just this Shared O-RU use case. - -#### 4.20.3.2 Resource partitioning use case of Shared O-RU for Single-MNO - -The following describes the solution for the resource partitioning sub-use case for a Shared O-RU. - -The context of the resource partitioning use case of Shared O-RU is captured in table 4.20.3.2-1. - -For mTLS, TLS and NACM security for this Shared O-RU sub-use case see requirements SEC-CTL-SharedORU-1, SEC-CTL-SharedORU-3 and SEC-CTL-SharedORU-4 in the O-RAN.WG11.TS.Security-Requirements-Specification.O-R004-v11.00 [39], clause 5.1.9.2. - -**Table 4.20.3.2-1: Resource partitioning use case of Shared O-RU** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | rApp has details on how a Shared O-RU's resource are to be partitioned. | | -| Actors and Roles | SMO provides inventory details of Shared O-RU and O-DUs.
Sharing co-ordinator recovers inventory and decides on partitioning of carriers between O-DUs.
Sharing co-ordinator uses resource partitioning rApp to partition resource configuration of a Shared O-RU between O-DUs. | | -| Assumptions | All relevant functions and components are instantiated.
Inventory management systems identify Shared O-RU carrier capabilities and available O-DUs. | | -| Begins when | Sharing co-ordinator decides to share an O-RU between multiple O-DUs. | | -| Pre-conditions | Inventory system is up to date. | | -| Step 1 (M) | Sharing co-ordinator recovers O-RU and O-DU inventory and decides on resource partitioning. | | -| Step 2 (M) | Sharing co-ordinator resource partitioning rApp to partition Shared O-RU between multiple O-DUs. | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|--------------------------------------------------------------------------------------------------------|---------------------------------| -| | | Related use | -| Step 3 (M) | rApp signals O-DU identity(ies) to configuration management system. | | -| Step 4 (M) | Configuration management system configures transport systems with call home identity(ies) for O-DU(s). | O-RAN.WG4.MP [28], clause 6.2.5 | -| Ends when | rApp has details on how Shared O-RU's resource are to be partitioned. | | -| Exceptions | None identified. | | -| Post Conditions | None identified. | | - -``` - -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber - -Box "Personnel" #Lightblue - Actor planner as "Sharing Co-ordinator" -End box - -Box "Service Management and Orchestration\nShared O-RU Operator" #gold - Participant INV as "Inventory\nManagement" - Participant CFG as "Configuration\nManagement" - Participant R_APP as "Resource\nPartitioning\nrApp (shared O-RU)" -end box - -Box "External" - Participant TRANS as "DHCP\nServer" -End box - -== RESOURCE PARTITIONING == - -``` - -``` - -planner <--> INV: Recover inventory and decide on \n resource partitioning - -planner <--> R_APP: Partition shared O-RU between multiple o-DUs - -R_APP --> CFG: Set call home identity(ies) - -CFG-->TRANS: Configure DHCP options for call home - -@enduml - -``` - -The flow diagram of the resource partitioning use case is given in figure 4.20.3.2-1. - -![Sequence diagram for Resource partitioning use case. Lifelines: Personnel (Sharing Co-ordinator), Service Management and Orchestration Shared O-RU Operator (Inventory Management, Configuration Management, Shared O-RU Orchestration rApp), and External (DHCP Server). The diagram shows four steps: 1. Recover inventory and decide on resource partitioning; 2. Partition shared O-RU between multiple O-DUs; 3. Set call home identity(ies); 4. Configure DHCP options for call home.](6cdb31bed6791fa0bd3fbc1e583b07ed_img.jpg) - -``` - -sequenceDiagram - participant Personnel as Sharing Co-ordinator - participant SMO as Service Management and Orchestration Shared O-RU Operator - participant External as External - Note right of SMO: RESOURCE PARTITIONING - Note right of SMO: Inventory Management, Configuration Management, Shared O-RU Orchestration rApp - Note right of External: DHCP Server - Note left of Personnel: Sharing Co-ordinator - Note left of Personnel: Sharing Co-ordinator - Note left of Personnel: 1 Recover inventory and decide on resource partitioning - Note left of Personnel: 2 Partition shared O-RU between multiple O-DUs - Note left of Personnel: 3 Set call home identity(ies) - Note left of Personnel: 4 Configure DHCP options for call home - -``` - -Sequence diagram for Resource partitioning use case. Lifelines: Personnel (Sharing Co-ordinator), Service Management and Orchestration Shared O-RU Operator (Inventory Management, Configuration Management, Shared O-RU Orchestration rApp), and External (DHCP Server). The diagram shows four steps: 1. Recover inventory and decide on resource partitioning; 2. Partition shared O-RU between multiple O-DUs; 3. Set call home identity(ies); 4. Configure DHCP options for call home. - -Figure 4.20.3.2-1: Resource partitioning use case - -#### 4.20.3.3 Start-up use case of Shared O-RU for Single-MNO - -The following describes the solution for the start-up sub-use case for a Shared O-RU. - -The context of the Shared O-RU start-up use case is captured in table 4.20.3.3-1. - -**Table 4.20.3.3-1: Shared O-RU start-up use case** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------| -| Goal | The Shared O-RU is operating with the necessary software version and has established network connectivity with the O-DU(s) and, for hybrid deployments, the SMO. | | -| Actors and Roles |

Shared O-RU calls home and establishes network management session.

SMO is responsible for software management for the Shared O-RU when operating in hybrid management mode.

O-DU is responsible for software management for the Shared O-RU when operating in hierarchical management mode.

| | -| Assumptions | None. | | -| Begins when | Shared O-RU powers on. | | -| Pre-conditions | Transport systems (DHCP server) has been configured with call home configuration information. | | -| Step 1 (M) |

Establish synchronization:

Each O-DU and Shared O-RU establish synchronisation with a timing source, for example PTP (IEEE 1588) or Sync-E. See NOTE 1, NOTE 2.

| | -| Step 2 (M) |

Synchronization State Change Notification:

After the O-RU has a synchronisation source, all subscribed O-DU(s) are notified through a Synchronisation State Change Notification. We expect the O-RU to be in the sync state “LOCKED”.

The Synchronisation State Change Notification goes from Shared O-RU to all subscribed O-DU(s).

It is possible that the synchronisation procedure can happen in parallel to the other steps of the start-up sub-use case. Thus, many of the other steps in this use case can happen as the synchronization procedure occurs. Even though this is shown as “step 2” this can complete after other steps.

| | -| Step 3 (ALT) |

[Shared O-RU operated in hybrid management mode]

Shared O-RU calls home and triggers establishment of network management session with SMO.

| O-RAN.WG4.MP [28], clause 6.3 and/or clause 6.9.2 | -| Step 4 (ALT) |

[Shared O-RU operated in hierarchical management mode]

Shared O-RU calls home and triggers establishment of network management session with O-DU#1.

| O-RAN.WG4.MP [28], clause 6.3 | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------| -| | | Related use | -| Step 5 (ALT) | [Shared O-RU operated in hierarchical management mode]
Shared O-RU calls home and triggers establishment of network management session with O-DU#2. | O-RAN.WG4.MP [28], clause 6.3 | -| Step 6 (ALT) | [Shared O-RU operated in hybrid management mode]
SMO recovers software inventory. | O-RAN.WG4.MP [28], clause 8.4 | -| Step 7 (O) | [Shared O-RU operated in hybrid management mode and software update required]
SMO triggers download of new software. | O-RAN.WG4.MP [28], clause 8.5 | -| Step 8 (O) | [Shared O-RU operated in hybrid management mode and software update required]
O-RU downloads software files. | O-RAN.WG4.MP [28], clause 8.5 | -| Step 9 (O) | [Shared O-RU operated in hybrid management mode and software update required]
SMO triggers the installation and activation of the software. | O-RAN.WG4.MP [28], clauses 8.6 and 8.7 | -| Step 10 (O) | [Shared O-RU operated in hybrid management mode and software update required]
SMO brings active software into operation. | O-RAN.WG4.MP [28], clause 8.7 | -| Step 11 (ALT) | [Shared O-RU operated in hierarchical management mode]
O-DU recovers software inventory. | O-RAN.WG4.MP [28], clause 8.4 | -| Step 12 (O) | [Shared O-RU operated in hierarchical management mode and software update required]
O-DU triggers download of new software. | O-RAN.WG4.MP [28], clause 8.5 | -| Step 13 (O) | [Shared O-RU operated in hierarchical management mode and software update required]
O-RU downloads software files. | O-RAN.WG4.MP [28], clause 8.5 | -| Step 14 (O) | [Shared O-RU operated in hierarchical management mode and software update required]
O-DU triggers the installation and activation of the software. | O-RAN.WG4.MP [28], clauses 8.6 and 8.7 | -| Step 15 (O) | [Shared O-RU operated in hierarchical management mode and software update required]
O-DU brings active software into operation. | O-RAN.WG4.MP [28], clause 8.7 | -| Ends when | The Shared O-RU is operating with the necessary software version and has established network connectivity with the O-DU and, for hybrid deployments, the SMO. | | -| Exceptions | None identified. | | -| Post Conditions | None identified. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------------------| -|

NOTE 1: It is expected the O-RU and all O-DUs connected it would share the same synchronisation source otherwise, the O-DUs will drift in timing.

NOTE 2: For more details on O-RU sync and O-RU loss of sync, see O-RAN.WG4.MP [28], clause 15.3.3.

| | | - -``` - -@startuml - -!pragma teoz true - -skin rose - -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 - -Box "Service Management and Orchestration\nShared O-RU Operator" #gold - - Participant CFG as "Configuration\nManagement" - Participant SWM as "Software\nManagement" - Participant FS as "File\nServer" - -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - - Participant ODU1 as "O-DU\n(#1) " - Participant ODU2 as "O-DU\n(#2) " - - participant ORU as "O-RU\n(Shared)" -End box - -autonumber - -== STARTUP == - -Note over ODU1, ORU - Synchronization Timing is established for O-Dus and Shared O-RU -End Note - -``` - -``` -ORU -> ODU1: <> Synchronization state change notification -ORU -> ODU2: <> Synchronization state change notification - -group Shared O-RU Call Home - -alt call home to SMO (Hybrid Management) -ORU<->CFG: <> Call Home & Network management session establishment -end - -alt call home to ODU (Hierarchical or Hybrid management) -ORU<->ODU1: <> Call Home & Network management session establishment -ORU<->ODU2: <> Call Home & Network management session establishment -end - -end - -group Shared O-RU Software Management -alt Hybrid Software Management -SWM<->ORU: Recover software inventory -opt software update required -SWM->ORU: Trigger Software Download -FS<--ORU: Software Download -SWM<-->ORU: Install & Activate Software -SWM<-->ORU: Bring Software into operation - -end -end - -alt Hierarchical Software Management -ODU1<->ORU: Recover software inventory -opt software update required -ODU1-->ORU: Trigger Software Download -FS<--ORU: Software Download -ODU1<-->ORU: Install & Activate Software -ODU1<-->ORU: Bring Software into operation - -end -``` - -end - -end - -@enduml - -The flow diagram of the Shared O-RU start-up use case is given in figure 4.20.3.3-1. - -![Sequence diagram for Shared O-RU start-up use case. Lifelines: SMO (Hybrid Management), ODU (#1), ODU (#2), and O-RU (Shared). The process includes startup, synchronization, call home to SMO or ODU, and software management (Hybrid or Hierarchical).](dbe4ffa9778863279b48b56fe097cd23_img.jpg) - -``` - -sequenceDiagram - participant SMO as Service Management and Orchestration -Shared O-RU Operator (SMO) - participant ODU1 as O-DU (#1) - participant ODU2 as O-DU (#2) - participant O-RU as O-RU (Shared) - - Note right of O-RU: STARTUP - Note right of O-RU: Synchronization Timing is established for O-DUs and Shared O-RU - O-RU->>ODU1: 1 <> Synchronization state change notification - O-RU->>ODU2: 2 <> Synchronization state change notification - - alt Shared O-RU Call Home: call home to SMO (Hybrid Management) - O-RU->>SMO: 3 <> Call Home & Network management session establishment - else call home to ODU (Hierarchical or Hybrid management) - O-RU->>ODU1: 4 <> Call Home & Network management session establishment - O-RU->>ODU2: 5 <> Call Home & Network management session establishment - end - - alt Shared O-RU Software Management: Hybrid Software Management - O-RU->>SMO: 6 Recover software inventory - alt software update required - O-RU->>SMO: 7 Trigger Software Download - SMO->>ODU1: 8 Software Download - O-RU->>SMO: 9 Install & Activate Software - SMO->>ODU1: 10 Bring Software into operation - end - else Hierarchical Software Management - O-RU->>ODU1: 11 Recover software inventory - alt software update required - O-RU->>ODU1: 12 Trigger Software Download - ODU1->>ODU2: 13 Software Download - O-RU->>ODU1: 14 Install & Activate Software - ODU1->>ODU2: 15 Bring Software into operation - end - end - -``` - -Sequence diagram for Shared O-RU start-up use case. Lifelines: SMO (Hybrid Management), ODU (#1), ODU (#2), and O-RU (Shared). The process includes startup, synchronization, call home to SMO or ODU, and software management (Hybrid or Hierarchical). - -Figure 4.20.3.3-1: Shared O-RU start-up use case - -#### 4.20.3.4 Configuration use case of a Shared O-RU for Single & Multi-MNO - -The following describes the solution for the configuration sub-use case for a Shared O-RU. - -The context of the Shared O-RU configuration use case is captured in table 4.20.3.4-1. - -**Table 4.20.3.4-1: Shared O-RU configuration use case** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| -| Goal | The Shared O-RU is configured to operate with multiple O-DUs. | | -| Actors and Roles |

SMO responsible for Shared O-RU common configuration when operating in hybrid management mode.

SMO optionally can subscribe to receive notifications of modifications to Shared O-RU's configuration.

When operating in hierarchical management mode, rApp is responsible for determining which O-DU is responsible for common configuration aspects.

Shared O-RU responsible for role-based access control based on PLMN-Id.

O-DU is responsible for Shared O-RU carrier configuration and optionally, when operating in hierarchical management mode, the Shared O-RU common configuration.

Sharing co-ordinator can check the Shared O-RU's committed configuration complies with any sharing agreement.

| | -| Assumptions | None. | | -| Begins when | Shared O-RU has started up and has been configured with correct software version. | | -| Pre-conditions | None. | | -| Step 1 (O) | [Shared O-RU operated in hierarchical management mode]
rApp determines which O-DU is responsible for common configuration of Shared O-RU. | | -| Step 2 (M) | rApp triggers the configuration of the common aspects of the Shared O-RU. | | -| Step 3 (M) | Non-RT RIC triggers the configuration of the common aspects of the Shared O-RU. | | -| Step 4 (ALT) | [Hybrid or neutral host management mode]
SMO uses OpenFronthaul interface to configure common aspects of Shared O-RU. | O-RAN.WG4.MP [28], clause 9 | -| Step 5 (ALT) | [Hierarchical management mode]
SMO uses O1 interface to configure Shared O-RU's common aspects via O-DU. | | -| Step 6 (ALT) | [Hierarchical management mode]
O-DU uses OpenFronthaul interface to configure common aspects of Shared O-RU. | O-RAN.WG4.MP [28], clause 9 | -| Step 7 (O) | Shared O-RU calls home to tenant's O-DU (multi-operator). | | -| Step 8 (O) | Shared O-RU calls home to tenant's SMO (multi-operator). | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| -| | | Related use | -| Step 9 (O) | rApp triggers the configuration of the carrier aspects of the Shared O-RU (non-neutral host). | | -| Step 10 (O) | Non-RT RIC triggers the configuration of the carrier aspects of the Shared O-RU. | | -| Step 11 (O) | SMO configures O-DU#1 and partitioned carrier information #1. | | -| Step 12 (O) | O-DU#1 configures partitioned carrier information #1 on Shared O-RU non-neutral host). | O-RAN.WG4.MP [28], clause 9 | -| Step 13 (O) | Tenant's SMO configures O-DU#2 and partitioned carrier information #2 (multi-operator). | | -| Step 14 (M) | O-DU#2 configures partitioned carrier information #2 on Shared O-RU. | O-RAN.WG4.MP [28], clause 9 | -| Step 15 (O) | Shared O-RU implements role-based access control based oplmn-id#2. | | -| Step 16 (O) | The Shared O-RU notifies SMO of its modified configuration. | O-RAN.WG4.MP [28], clause 9.4 | -| Step 17 (O) | SMO signals Non-RT RIC information pertaining to changed configuration. | | -| Step 18 (O) | Non-RT RIC signals changed configuration to Shared O-RU orchestration rApp. | | -| Step 19 (O) | Sharing co-ordinator checks that the changed configuration compliance with the sharing agreement. | | -| Step 20 (O) | Host sharing co-ordinator indicates non-compliance with tenant sharing co-ordinator and remedial actions agreed (out of band exchange). | | -| Ends when | The Shared O-RU is configured with common aspects and partitioned carrier#1 for O-DU#1 and partitioned carrier #2 for O-DU#2. | | -| Exceptions | None identified. | | -| Post Conditions | See NOTE. | | -| NOTE: Before activation of carriers, O-RU needs to have sync state "LOCKED" with its sync source. For more details, see O-RAN.WG4.MP [28], clause 15.3.3. | | | - -``` - -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber - -Box "Personnel\nShared O-RU Host" #Lightblue - -``` - -``` -Actor planner as "Sharing Co-ordinator" -``` - -``` -End box -``` - -``` -Box "Service Management and Orchestration\nShared O-RU Operator" #gold -``` - -``` -Participant CFG as "Configuration\nManagement" -``` - -``` -Participant R_APP as "Shared O-RU\nOrchestration \nrApp" -``` - -``` -Participant SMO_a as "Non-RT\nRIC" -``` - -``` -end box -``` - -``` -Box "O-RAN\nShared O-RU Operator" #lightpink -``` - -``` -Participant ODU1 as "O-DU\n(#1)" -``` - -``` -participant ORU as "O-RU\n(Shared)" -``` - -``` -End box -``` - -``` -Box "O-RAN Tenant\nOperator PLMN-ID#2" #lightpink -``` - -``` -Participant ODU2 as "O-DU\n(#2)" -``` - -``` -End box -``` - -``` -Box "Service Management and Orchestration\nTenant Operator PLMN-ID#2" #gold -``` - -``` -Participant CFG_b as "Configuration\nManagement" -``` - -``` -end box -``` - -``` -Box "Personnel\nTenant Operator" #lightblue -``` - -``` -Actor planner2 as "Sharing Co-ordinator" -``` - -``` -End box -``` - -``` -== CONFIGURATION == -``` - -``` -group Configure common aspects of shared O-RU -``` - -``` - -opt Hierarchical Management - -Hnote over R_APP -1. Decide on O-DU(#1) - -or O-DU(#2) for -common management - -end note -end - -autonumber 2 - -R_APP -> SMO_a: <> Configure\nShared O-RU\nCommon aspects including any tenant -account (with plmn-id) - -SMO_a->CFG: Configure Shared O-RU Common Aspects including any tenant account (with plmn- -id) - -alt Hybrid or Neutral-Host Management - -CFG->ORU: <> Configure Shared O-RU common aspects including any tenant account (with -plmn-id) - -end - -alt Hierarchical Management - -CFG->ODU1: <> Configure Shared O-RU common aspects including any tenant account (with -plmn-id) - -&ODU1->ORU: <> Configure Shared O-RU\ncommon aspects including\nany tenant account -(with plmn-id) - -end - -end - -opt Call home to tenant - -ORU->ODU2: <> Call Home & Network\nmanagement session\nestablishment using\naccount -linked to plmn-id#2 - -opt Call home to tenant SMO - -ORU->CFG_b: <> Call Home & Network management session \nestablishment using account -linked to plmn-id#2 - -end - -end - -group Configure carrier aspects of shared O-RU - -opt non-neutral host - -``` - -``` -R_APP -> SMO_a: <> Configure\nShared O-RU\nCarrier aspects - -SMO_a->CFG: Configure Shared O-RU Carrier Aspects - -CFG -> ODU1: <> Configure O-DU ID#1 and partitioned carrier information #1 -ODU1->ORU: <> Configure O-DU ID#1 and\npartitioned carrier information #1 - -end - -group tenant configuration of carrier aspects -CFG_b -> ODU2: <> Configure\nShared O-RU\ncarrier#2 aspects\nPLMN-ID#2 -ODU2->ORU: <> Configure carrier#2\nPLMN-ID#2 -Hnote over ORU -15. O-RU implements -enhanced role based -access control -based on plmn-id#2 -end note -end - -end - -autonumber 16 - -opt notification of committed configuration -ORU->CFG: <> Notification of Configuration Update -CFG->SMO_a: Notification of Configuration Update -SMO_a->R_APP: <> Configuration Update - -planner <--> R_APP: Sharing Co-ordinator confirms compliance to partitioning rules - -opt Non-Compliant partitioning -Hnote over planner, planner2 -20. Indication of non-compliance and agreement on remedial action (out of band exchange) -end note -end - -end -``` - -Note over ORU - -Before activation of carriers, O-RU needs to have sync lock with its sync source - -End Note - -@enduml - -The flow diagram of the Shared O-RU configuration use case is given in figure 4.20.3.4-1. - -![Sequence diagram for Shared O-RU configuration use case. Lifelines include Personnel Shared O-RU Host, Service Management and Orchestration Shared O-RU Operator, O-RAN Shared O-RU Operator, O-RAN Tenant Operator PLMN-ID#2, Service Management and Orchestration Tenant Operator PLMN-ID#2, and Personnel Tenant Operator. The diagram shows steps for configuring common aspects, carrier aspects, and handling notifications and compliance.](5aa1fd73e15adc4c2fc5e57a9578755d_img.jpg) - -The sequence diagram illustrates the interaction for the Shared O-RU configuration use case. It begins with the 'Configure common aspects of shared O-RU' block, which includes an 'opt (Hierarchical Management)' where the Shared O-RU Operator decides on O-DU#1 or O-DU#2. This is followed by 'alt (Hybrid or Neutral-Host Management)' and another 'opt (Hierarchical Management)' for configuring common aspects. Next is the 'Configure carrier aspects of shared O-RU' block, which includes an 'opt (non-neutral host)' for configuring carrier aspects and a 'tenant configuration of carrier aspects' block involving O-DU#2. The process concludes with 'opt (notification of committed configuration)' for notifications and 'opt (Non-Compliant partitioning)' for compliance checks. A note at the bottom indicates that before carrier activation, the O-RU needs a sync lock with its source. - -Sequence diagram for Shared O-RU configuration use case. Lifelines include Personnel Shared O-RU Host, Service Management and Orchestration Shared O-RU Operator, O-RAN Shared O-RU Operator, O-RAN Tenant Operator PLMN-ID#2, Service Management and Orchestration Tenant Operator PLMN-ID#2, and Personnel Tenant Operator. The diagram shows steps for configuring common aspects, carrier aspects, and handling notifications and compliance. - -Figure 4.20.3.4-1: Shared O-RU configuration use case - -#### 4.20.3.5 Supervision use case of a Shared O-RU for Single-MNO - -The following describes the solution for the supervision sub-use case for a Shared O-RU. - -The context of the supervision use case of a Shared O-RU is captured in table 4.20.3.5-1. - -**Table 4.20.3.5-1: Supervision use case of a Shared O-RU** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The Shared O-RU operates watchdog timers with each of its O-DUs and ceases transmitting on a partitioned carrier associated with an O-DU if is watchdog timer to that O-DU expires. | | -| Actors and Roles | Shared O-RU operates watchdog timers and deactivates any carriers associated with an expired watchdog timer.

O-DU repeatedly resets the Shared O-RU's supervision timer.

SMO forwards any alarms to Shared O-RU rApp. | | -| Assumptions | O-DUs are operating fronthaul control and user plane for their respective partitioned carriers.

SMO has subscribed to receive alarm notifications (hybrid management model). | | -| Begins when | An O-DU subscribes to receive supervision notifications. | | -| Step 1 (Loop) | O-DU#1 performs supervision operations. | | -| Step 2 (O) | Shared O-RU detects supervision failure with O-DU#1 and ceases transmitting on partitioned carrier associated with O-DU. | | -| Step 3 (O) | Shared O-RU sends alarm notification to Fault Management | | -| Step 4 (O) | Fault management sends alarm notification to Non-RT RIC. | | -| Step 5 (O) | Non-RT RIC sends alarm notification to Shared O-RU orchestration rApp. | | -| Step 6 (Loop) | O-DU#2 performs supervision operations. | | -| Step 7 (O) | Shared O-RU detects supervision failure with O-DU#2 and ceases transmitting on partitioned carrier associated with O-DU. | | -| Step 8 (O) | Shared O-RU sends alarm notification to fault management. | | -| Step 9 (O) | Fault management sends alarm notification to Non-RT RIC. | | -| Step 10 (O) | Non-RT RIC sends alarm notification to Shared O-RU orchestration rApp. | | -| Ends when | O-DU terminates subscription to supervision notification. | | -| Exceptions | None identified. | | -| Post Conditions | None identified. | | - -``` - -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber 1 - -``` - -``` -Box "Service Management and Orchestration\nShared O-RU Operator" #gold - Participant FM as "Alarm\nManagement" - Participant R_APP as "Shared O-RU\nOrchestration \nrApp" - Participant SMO_a as "Non-RT\nRIC" -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant ODU1 as "O-DU\n(#1)" - Participant ODU2 as "O-DU\n(#2)" - - participant ORU as "O-RU\n(Shared)" -End box - -== RUNNING == - -hnote over ODU1, ORU -<> Fronthaul Control & User Plane for partitioned carrier #1 -end note - -hnote over ODU2, ORU -<> Fronthaul Control & User Plane for partitioned carrier #2 -end note - -group Per O-DU Supervision - -loop odu #1 supervision -ODU1<->ORU: <> Supervision Operation O-DU #1 -end - -opt Supervision failure to odu-id#1 -hnote over ORU -2. cease transmitting -``` - -``` -partitioned carrier #1 - -end note - -autonumber 3 - -opt SMO has subscribed to reveive alarm notifications -ORU->FM: (Opt) <> O-DU Supervision Alarm O-DU#1 -FM->SMO_a: Alarm Indication -SMO_a->R_APP: <> Alarm\nIndication -end -end - -loop odu #2 supervision -ODU2<->ORU: <> Supervision Operation O-DU #2 -end - -opt Supervision failure to odu-id#2 -hnote over ORU -7. cease transmitting -partitioned carrier #2 - -end note - -opt SMO has subscribed to reveive alarm notifications -autonumber 8 -ORU->FM: (Opt) <> O-DU Supervision Alarm O-DU#2 -FM->SMO_a: Alarm Indication -SMO_a->R_APP: <> Alarm\nIndication -end -end - -end - -@enduml -``` - -The flow diagram of the supervision use case of a Shared O-RU is given in figure 4.20.3.5-1. - -![Sequence diagram for the supervision use case of a Shared O-RU. It shows interactions between Service Management and Orchestration (Shared O-RU Operator), O-RAN Shared O-RU Operator (O-DU #1, O-DU #2, O-RU Shared), and Per O-DU Supervision. The process involves supervision loops for each O-DU, handling supervision failures, and sending alarm indications to the SMO and RIC.](93c9262c68d25c26b8cf8cd547554d9f_img.jpg) - -The diagram illustrates the supervision use case for a Shared O-RU. It is divided into two main lifelines: **Service Management and Orchestration Shared O-RU Operator** (left, yellow background) and **O-RAN Shared O-RU Operator** (right, pink background). The O-RAN Shared O-RU Operator contains three entities: **O-DU (#1)**, **O-DU (#2)**, and **O-RU (Shared)**. The Service Management and Orchestration Shared O-RU Operator contains three entities: **Alarm Management**, **Shared O-RU Orchestration rApp**, and **Non-RT RIC**. A horizontal line labeled **RUNNING** separates the initial state from the active supervision process. Below this line, two messages are shown: **<> Fronthaul Control & User Plane for partitioned carrier #1** and **<> Fronthaul Control & User Plane for partitioned carrier #2**. The supervision process is organized into two main sections: **Per O-DU Supervision**. The first section is a **loop [odu #1 supervision]**. It starts with message **1 <> Supervision Operation O-DU #1** from the O-RU (Shared) to the O-DU (#1). An **opt [Supervision failure to odu-id#1]** block follows. Inside this block, message **2. cease transmitting partitioned carrier #1** is sent from the O-RU (Shared) to the O-DU (#1). Another **opt [SMO has subscribed to receive alarm notifications]** block contains messages **3 (Opt) <> O-DU Supervision Alarm O-DU#1** (from O-DU (#1) to Alarm Management), **4 Alarm Indication** (from Alarm Management to Shared O-RU Orchestration rApp), and **5 <> Alarm Indication** (from Shared O-RU Orchestration rApp to Non-RT RIC). The second section is a **loop [odu #2 supervision]**. It starts with message **6 <> Supervision Operation O-DU #2** from the O-RU (Shared) to the O-DU (#2). An **opt [Supervision failure to odu-id#2]** block follows. Inside this block, message **7. cease transmitting partitioned carrier #2** is sent from the O-RU (Shared) to the O-DU (#2). Another **opt [SMO has subscribed to receive alarm notifications]** block contains messages **8 (Opt) <> O-DU Supervision Alarm O-DU#2** (from O-DU (#2) to Alarm Management), **9 Alarm Indication** (from Alarm Management to Shared O-RU Orchestration rApp), and **10 <> Alarm Indication** (from Shared O-RU Orchestration rApp to Non-RT RIC). - -Sequence diagram for the supervision use case of a Shared O-RU. It shows interactions between Service Management and Orchestration (Shared O-RU Operator), O-RAN Shared O-RU Operator (O-DU #1, O-DU #2, O-RU Shared), and Per O-DU Supervision. The process involves supervision loops for each O-DU, handling supervision failures, and sending alarm indications to the SMO and RIC. - -Figure 4.20.3.5-1: Supervision use case of a Shared O-RU - -#### 4.20.3.6 Performance management use case of a Shared O-RU for Single-MNO - -The following describes the solution for the performance management sub-use case for a Shared O-RU. - -The context of the performance management use case of a Shared O-RU is captured in table 4.20.3.6-1. - -Table 4.20.3.6-1: Performance management use case of a Shared O-RU - -| Use Case Stage | Evolution / Specification | <> | -|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Goal |

Each O-DU has established subscriptions to receive performance management notifications regarding operation of the fronthaul between the O-DUs and Shared O-RU.

The O-DU and Shared O-RU are able to report performance measurement data towards their consumers in a Multi-MNO configuration.

| | -| Actors and Roles |

Shared O-RU generates performance management notifications on a per partitioned carrier basis.

O-DU subscribes to receive performance management notifications from Shared O-RU.

| | -| Assumptions | O-DU has configured performance management metrics for respective partitioned carrier. | | -| Begins when | Fronthaul control and user plane is operational between O-DU and Shared O-RU. | | -| Step 1 (M) | O-DU#1 subscribes to receive PM notifications from Shared O-RU. | | -| Step 2 (M) | O-DU#2 subscribes to receive PM notifications from Shared O-RU. | | -| Step 3 (loop) | Shared O-RU sends PM notification to O-DU#1. | | -| Step 4 (loop) | Shared O-RU sends PM notification to O-DU#2. | | -| O-DU to SMO performance operations | | | -| Step 1 (O) | PM event notification reporting

The O-DU (producer) sends performance data to the SMO (consumer) through an event notification.

| | -| Step 2 (O) | Streaming PM reports

The O-DU establishes a persistent connection to the SMO (consumer) and sends performance data.

| | -| Step 3 (O) | Attribute-based or URI-based collection

Performance data is read by the consumer (SMO) through configuration management attribute. Alternatively, the O-DU can support a data scraping method where a collector (SMO) reads the data from a pre-defined URI.

| | -| Step 4 (O) | Producer or PM file upload (file upload)

O-DU uploads a PM file to the SMO.

| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | See NOTE 1. | | -| Step 5 (O) | Consumer downloads PM file (file download)

O-DU issues file ready notification to SMO about the data being ready for download, or SMO periodically polls the O-DU. Afterwards, the SMO (consumer) can download the PM file. | | -| O-RU to O-DU performance operations (in hierarchical configuration) | | | -| Step 1 (O) | PM event notification reporting

The O-RU sends performance data to the O-DU through an event notification. The notification is sent to a subscriber of performance data. | | -| Step 1 (M) | O-DU requests for O-RU to start sending PM data

O-DU invokes an RPC to give PM credentials, target URI, and periodicity notification interval to the Shared O-RU. This includes all the necessary information for the O-RU to perform a file transfer to an endpoint periodically.

See NOTE 2. | | -| Step 2 (M) | Shared O-RU uploads PM file

The Shared O-RU periodically uploads a performance file to the target URI using the PM credentials given by the O-DU. | | -| O-RU to SMO performance operations (in hybrid configuration) | | | -| Step 1 (O) | PM event notification reporting

The O-RU sends performance data to the SMO through an event notification via M-plane. | | -| Step 1 (O) | SMO requests for O-RU to start sending PM data

SMO invokes an RPC to give PM credentials, target URI, and periodicity notification interval to the Shared O-RU. This includes all the necessary information for the O-RU to perform a file transfer to an endpoint periodically. | | -| Step 2 (O) | Shared O-RU uploads PM file | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | The Shared O-RU uploads performance file to target URI using PM credentials given by the SMO. | | -| Ends when | 1) Subscriptions setup: O-DU terminates subscription to performance management notification.
2) O-DU to SMO sending PM data: Use case ends with the producer (O-DU) sending performance data to the consumer (SMO).
3) O-RU sending performance data: Use case ends with the producer (O-RU) starting to send performance data to the subscriber. | | -| Exceptions | None identified. | | -| Post Conditions | The consumer has received performance data and may perform post processing operations on the data. | | - -NOTE 1: When the O-DU sends performance files received from a Shared O-RU, they are converted to the proper 3GPP format before sending to SMO. See O-RAN WG5.O-DU-O1 [25]. - -NOTE 2: The O-DU establishes a framework for the Shared O-RU to send PM files. This operation is performed only once, thereafter, the Shared O-RU sends the PM files periodically. - -``` - -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber 1 - -Box "Owning Operator\n Service Management and Orchestration (SMO)" #gold - Participant PMS as "Performance Management\nService" -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant ODU1 as "O-DU\n(#1)" - Participant ODU2 as "O-DU\n(#2)" - participant ORU as "O-RU\n(Shared)" -End box - -== SUBSCRIPTION SETUP == - -``` - -``` -hnote over ODU1, ORU -<> Fronthaul Control & User Plane for partitioned carrier #1 -end note - -hnote over ODU2, ORU -<> Fronthaul Control & User Plane for partitioned carrier #2 -end note - -group Per O-DU Performance Management - -ODU1<->ORU: <> Subscribe to receive PM notifications for partitioned carrier #1 -ODU2<->ORU: <> Subscribe to receive PM notifications for partitioned carrier #2 - -loop Shared O-RU performance management -ORU->ODU1: <> PM Notification (partitioned carrier #1) -ORU->ODU2: <> PM Notification (partitioned carrier #2) -end -end - -== SUBSCRIPTION SETUP == - -== ODU TO SMO PERFORMANCE OPERATIONS == - -Autonumber 1 - -Alt O-DU Notification-based Reporting -ODU1->PMS: <> PM Event Notification Reporting -Else O-DU Streaming-based Reporting -ODU1->PMS: <> Streaming PM Reports -Else Consumer Actively Collects -PMS->ODU1: <> Attribute based or URI based collection -Else O-DU File-based Reporting -ODU1->PMS: <> Producer PM File Upload (File Upload) -Else O-DU File-based Reporting -PMS->ODU1: <> Consumer Downloads PM File (File Download) -End -``` - -``` -== ODU TO SMO PERFORMANCE OPERATIONS == -``` - -``` -== ORU TO ODU PERFORMANCE OPERATIONS (Hierarchical Config) == -``` - -``` -Autonumber 1 -``` - -``` -Opt O-RU Notification-based Reporting -``` - -``` -ORU->ODU1: <> PM Event Notification Reporting -``` - -``` -End -``` - -``` -Autonumber 1 -``` - -``` -Group O-DU Actively Collects PM -``` - -``` -ODU1->ORU: <> ODU invokes RPC to give PM Credentials, Periodicity, & Target URI -``` - -``` -ORU-->ODU1: <> ORU uploads Performance File to Target URI using PM Credentials -``` - -``` -End -``` - -``` -== ORU TO ODU PERFORMANCE OPERATIONS (Hierarchical Config) == -``` - -``` -== ORU TO SMO PERFORMANCE OPERATIONS (Hybrid Config) == -``` - -``` -Autonumber 1 -``` - -``` -Opt O-RU Notification-based Reporting -``` - -``` -ORU->PMS: <> PM Event Notification Reporting -``` - -``` -End -``` - -``` -Autonumber 1 -``` - -``` -Group SMO Actively Collects PM -``` - -``` -PMS->ORU: <> SMO invokes RPC to give PM Credentials, Periodicity, & Target URI -``` - -``` -ORU->PMS: <> ORU uploads Performance File to Target URI using PM Credentials -``` - -``` -End -``` - -``` -== ORU TO SMO PERFORMANCE OPERATIONS (Hybrid Config) == -``` - -@endum1 - -The flow diagram of the performance management use case of a Shared O-RU is given in figure 4.20.3.6-1. - -![Sequence diagram showing performance management use cases for a Shared O-RU. Lifelines: Owning Operator (SMO), O-RAN Shared O-RU Operator (O-DU #1, O-DU #2, O-RU (Shared)).](f4aaee6522d9ab40472939a4a178e5a3_img.jpg) - -``` - -sequenceDiagram - participant SMO as Owning Operator (SMO) Performance Management Service - participant ODU1 as O-DU (#1) - participant ODU2 as O-DU (#2) - participant ORU as O-RU (Shared) - - Note over SMO, ORU: SUBSCRIPTION SETUP - ORU-->>ODU1: <> Fronthaul Control & User Plane for partitioned carrier #1 - ORU-->>ODU2: <> Fronthaul Control & User Plane for partitioned carrier #2 - - Note over ODU1, ORU: Per O-DU Performance Management - ODU1->>ORU: 1 <> Subscribe to receive PM notifications for partitioned carrier #1 - ODU2->>ORU: 2 <> Subscribe to receive PM notifications for partitioned carrier #2 - loop Shared O-RU performance management - ORU->>ODU1: 3 <> PM Notification (partitioned carrier #1) - ORU->>ODU2: 4 <> PM Notification (partitioned carrier #2) - end - - Note over SMO, ORU: SUBSCRIPTION SETUP - - Note over SMO, ODU2: ODU TO SMO PERFORMANCE OPERATIONS - alt O-DU Notification-based Reporting - ODU1->>SMO: 1 <> PM Event Notification Reporting - else O-DU Streaming-based Reporting - ODU1->>SMO: 2 <> Streaming PM Reports - else Consumer Actively Collects - SMO->>ODU1: 3 <> Attribute based or URI based collection - else O-DU File-based Reporting - ODU1->>SMO: 4 <> Producer PM File Upload (File Upload) - else O-DU File-based Reporting - SMO->>ODU1: 5 <> Consumer Downloads PM File (File Download) - end - Note over SMO, ODU2: ODU TO SMO PERFORMANCE OPERATIONS - - Note over ODU1, ORU: ORU TO ODU PERFORMANCE OPERATIONS (Hierarchical Config) - opt O-RU Notification-based Reporting - ORU->>ODU1: 1 <> PM Event Notification Reporting - end - rect rgb(255, 255, 255) - Note right of ODU1: O-DU Actively Collects PM - ODU1->>ORU: 1 <> ODU invokes RPC to give PM Credentials, Periodicity, & Target URI - ORU->>ODU1: 2 <> ORU uploads Performance File to Target URI using PM Credentials - end - Note over ODU1, ORU: ORU TO ODU PERFORMANCE OPERATIONS (Hierarchical Config) - - Note over SMO, ORU: ORU TO SMO PERFORMANCE OPERATIONS (Hybrid Config) - opt O-RU Notification-based Reporting - ORU->>SMO: 1 <> PM Event Notification Reporting - end - rect rgb(255, 255, 255) - Note right of SMO: SMO Actively Collects PM - SMO->>ORU: 1 <> SMO invokes RPC to give PM Credentials, Periodicity, & Target URI - ORU->>SMO: 2 <> ORU uploads Performance File to Target URI using PM Credentials - end - Note over SMO, ORU: ORU TO SMO PERFORMANCE OPERATIONS (Hybrid Config) - -``` - -Sequence diagram showing performance management use cases for a Shared O-RU. Lifelines: Owning Operator (SMO), O-RAN Shared O-RU Operator (O-DU #1, O-DU #2, O-RU (Shared)). - -Figure 4.20.3.6-1: Performance management use case of a Shared O-RU for Single-MNO - -#### 4.20.3.7 Antenna Line Device (ALD) control use case of a Shared O-RU for Single-MNO - -The following describes the solution for the ALD control sub-use case for a Shared O-RU. - -The context of the antenna line device control use case of a Shared O-RU is captured in table 4.20.3.7-1. - -**Table 4.20.3.7-1: Antenna line device control use case of a Shared O-RU** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| -| Goal | The ALD connected to Shared O-RU is configured to operate with ALD controller. | | -| Actors and Roles | rApp is responsible for determining which O-DU is responsible for ALD controller aspects.
O-DU is responsible for implementing ALD controller.
O-RU is responsible for bridging between OFH and HDLC.
ALD is responsible for terminating HDLC. | | -| Assumptions | None. | | -| Begins when | Shared O-RU has started up and has been configured with correct software version. | | -| Pre-conditions | None. | | -| Step 1 (M) | rApp determines which O-DU is responsible for performing ALD controller functionality. | | -| Step 2 (M) | rApp triggers the configuration of the ALD controller for Shared O-RU. | | -| Step 3 (M) | Non-RT RIC triggers the configuration of ALD controller for Shared O-RU. | | -| Step 4 (M) | SMO uses O1 interface to configure ALD controller in O-DU. | | -| Step 5 (M) | O-DU uses OpenFronthaul interface to configure ALD aspects of Shared O-RU. | O-RAN.WG4.MP [28], clause 9 | -| Step 6 (M) | O-DU uses OpenFronthaul interface to signal ALD. | O-RAN.WG4.MP [28], clause 14.4 | -| Step 7 (M) | Shared O-RU provides interworking between OFH and HDLC. | O-RAN.WG4.MP [28], clause 14.4 | -| Ends when | ALD connected to Shared O-RU is configured correctly. | | -| Exceptions | None identified. | | -| Post Conditions | None identified. | | - -``` -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -``` - -``` -skinparam defaultFontSize 14 - -autonumber - -Box "Service Management and Orchestration\nShared O-RU Operator" #gold - Participant CFG as "Configuration\nManagement" - Participant R_APP as "Shared O-RU\nOrchestration \nrApp" - Participant SMO_a as "Non-RT\nRIC" -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant ODU1 as "O-DU(#1)\nALD Controller" - - participant ORU as "O-RU\n(Shared)" - participant ALD as "ALD" -End box - -== CONFIGURATION == - -group Configure ALD aspects of shared O-RU - -Hnote over R_APP -1. Decide on O-DU(#1) -or O-DU(#2) for -ALD Control -end note - -autonumber 2 -R_APP -> SMO_a: <> Configure\nShared O-RU\nALD aspects -SMO_a->CFG: Configure Shared O-RU ALD Aspects - -CFG->ODU1: <> Configure Shared O-RU ALD aspects -&ODU1->ORU: <> Configure Shared O-RU ALD aspects - -end - -== RUNNING == -``` - -``` - -group ALD Operation for shared O-RU - -ODU1<->ORU: <> HDLC-over-OFH -&ORU<->ALD: HDLC - -end - -@enduml - -``` - -The flow diagram of the antenna line device use case is given in figure 4.20.3.7-1. - -![Sequence diagram for the antenna line device use case, showing interactions between Service Management and Orchestration (Shared O-RU Operator) and O-RAN (Shared O-RU Operator) components across CONFIGURATION and RUNNING phases.](24ad8881354fe6ad6a21dd40dfe8c8bb_img.jpg) - -The diagram illustrates the sequence of interactions for the antenna line device use case, divided into two main phases: CONFIGURATION and RUNNING. - -**CONFIGURATION Phase:** - -- The **Shared O-RU Orchestration rApp** (part of Service Management and Orchestration) sends a message labeled **2 <> Configure Shared O-RU ALD aspects** to the **O-RU (Shared)**. -- The **O-RU (Shared)** responds with **3 Configure Shared O-RU ALD Aspects** to the **Shared O-RU Orchestration rApp**. -- The **Shared O-RU Orchestration rApp** then sends **4 <> Configure Shared O-RU ALD aspects** to the **O-DU(#1) ALD Controller**. -- The **O-DU(#1) ALD Controller** sends **5 <> Configure Shared O-RU ALD aspects** to the **O-RU (Shared)**. -- A decision box labeled **1. Decide on O-DU(#1) or O-DU(#2) for ALD Control** is shown at the top of the configuration sequence. - -**RUNNING Phase:** - -- The **O-DU(#1) ALD Controller** sends **6 <> HDLC-over-OFH** to the **O-RU (Shared)**. -- The **O-RU (Shared)** sends **7 HDLC** to the **ALD**. - -The components involved are: **Configuration Management**, **Shared O-RU Orchestration rApp**, and **Non-RT RIC** (under Service Management and Orchestration); and **O-DU(#1) ALD Controller**, **O-RU (Shared)**, and **ALD** (under O-RAN). - -Sequence diagram for the antenna line device use case, showing interactions between Service Management and Orchestration (Shared O-RU Operator) and O-RAN (Shared O-RU Operator) components across CONFIGURATION and RUNNING phases. - -Figure 4.20.3.7-1: Antenna line device use case - -#### 4.20.3.8 Basic resiliency use case (active O-DU failure) for Single-MNO - -The following describes the solution for the basic resiliency sub-use case for a Shared O-RU. - -The context of the basic resiliency use case of a Shared O-RU is captured in table 4.20.3.8-1. - -**Table 4.20.3.8-1: Resiliency use case of a Shared O-RU** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal |

The goal of this sub-use case is to handle situations related to resiliency operations with the Shared O-RU when the O-DU is out of service.

This is a service impacting use case.

| | -| Actors and Roles |

Shared O-RU
The Shared O-RU handles the fronthaul and air interfaces and the reporting of performance counters and failures.

O-DUs (active/standby O-DUs)
All the O-DUs connected to the Shared O-RU are actors that are involved in basic resiliency scenario.

O-CU:
O-CU receives cell related configurations from SMO and available cell details from O-DU(s). Based on the available resources reported by O-DU and desired availability of cells received from SMO, the O-CU activates or deactivates the cells in the O-DU using F1 interface.

SMO:
The SMO configures the role of O-DUs as active or standby O-DUs and informs these roles to Shared O-RU through O-DU in hierarchical deployment. It makes high-level decisions related to conditions listed in clause 4.20.1.8.

| | -| Assumptions |

It is assumed that when active O-DU fails, there is still at least one standby O-DU having active NetConf session with the Shared O-RU.

It is assumed that the resiliency operations are intended to take over the Shared O-RU operation and recover the service to the end user.

| | -| Begins when |

There are many possible scenarios that trigger the basic resiliency use case as described in clause 4.20.1.8.

In this basic resiliency use case, only the complete failure of a O-DU is considered.

The purpose of the resiliency use case is to keep the Shared O-RU & O-DU system operational in the case of a failure of the active O-DU.

This use case begins when the active O-DU encounters a failure (operational state = disabled).

| | -| Pre-conditions |

The Shared O-RU has the NetConf connectivity with two or more O-DUs.

CU plane monitoring has been properly configured which sets up a communication monitoring interval for the interface between the Shared O-RU and active O-DU.

| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | O-DUs have subscribed to alarm notifications successfully. | | -| Basic resiliency use case – Initial system setup | | | -| Step 1.1 (M) | The SMO may configure O-DU#1 to take active role in controlling the Shared O-RU. It then configures the cells and corresponding carrier resources (including NRCGI(s) for the cells) via the O1 interface. | | -| Step 1.2 (M) | O-DU configures the carriers in O-RU, corresponding to the carrier resources outlined in step 1. | | -| Step 1.3 (M) | The SMO may configure O-DU#2 to take standby role via O1 interface. | | -| Step 1.4 (M) | SMO may provide O-CU with information via the O1 interface regarding which cell(s) (NRCGI(s)) associated with O-DU#1 need to be activated. See NOTE 1, NOTE 2, NOTE 3, NOTE 4. | | -| Basic resiliency use case – O-DU#1 failure detection | | | -| Step 2 (M) | Active O-DU fails

Active O-DU (the one serving as the active role) is no longer operational. The O-DU is no longer able to provide service. The O-DU has operational state = disabled . The Shared O-RU losses communication with the active O-DU. See NOTE 5. | | -| Step 3 (M) | O-RU raises alarms to subscribers

The Shared O-RU raises the loss of connectivity alarm to subscriber(s). The simple case shows that the O-DU#1 and O-DU#2 are subscribers. The Shared O-RU raises an alarm to subscribers (O-DUs) that are still active that is O-DU #2, connected and subscribed. | | -| Step 4 (M) | Alarm forwarded

The Shared O-RU alarm is forwarded to the managing entity, such as the SMO. It is possible that the SMO will make the decision for making the standby O-DU#2 into the active O-DU. | | -| Step 5 (M) | SMO provides O-CU with information regarding which cell(s) (NRCGI(s)) associated with O-DU#2 need to be made inactive and/or removed. | | -| Recover Shared O-RU operation | | | -| Step 6.1 (M) | The SMO may configure O-DU#2 to take standby role via O1 interface. See NOTE 6. | | -| Step 6.2 (M) | O-DU#2 becomes the active O-DU to recover Shared O-RU operation. See NOTE 7. | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 6.3 (M) | O-DU configures the carriers in O-RU, corresponding to the carrier resources outlined in step 6.1. See NOTE 8. | | -| Step 6.4 (M) | SMO provides O-CU with information regarding which cell(s) (NRCGI(s)) associated with O-DU#2 need to be activated. See NOTE 1, NOTE 2, NOTE 9, NOTE 10, NOTE 11. | | -| Ends when | The use case ends when the standby O-DU, O-DU#2 shown in the flow diagram has taken over for the previously active O-DU, O-DU #1. | | -| Exceptions |

There are many possible exceptions. Some of these include:

  • If the Shared O-RU fails during a switch over.
  • If the standby O-DU#2 also becomes unavailable when it is due to become active.
  • If any event messaging for the flow is lost.
  • If configuration was not done properly.
  • If the standby O-DU losses the configuration data from the configuration replica.
  • If the active O-DU returns to service while the standby O-DU is trying to become the active O-DU.
  • If the connectivity, or functionality of the management system (SMO) becomes unavailable.
| | -| Post Conditions |

Successful post condition – On a successful post-condition, the Shared O-RU is connected to the newly active O-DU, the newly active O-DU is operational and has properly synced with the O-RU.

Failure post condition – If one of the various exception cases occurs, there are a variety of failure post conditions. If no O-DUs are available and the O-RU is orphaned no service is available and the O-RU shall shut down operations. If misconfiguration occurs the O-RU will respond accordingly. If there are ever two active O-DUs, the Shared O-RU will operate accordingly.

| | - -| Use Case Stage | Evolution / Specification | <> | -|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------| -| | | Related use | -|

NOTE 1: When cells and corresponding carriers are configured and available for service, the O-DU informs O-CU about cells availability using F1 interface. O-CU requests O-DU to activate the cell(s) (NRCGI(s)), using the associated messages exchanged via the F1 interface. O-DU activates the carrier in O-RU that are associated with the specific cell(s) (NRCGI(s)) requested for activation.

NOTE 2: O-DU activates carriers related to cell(s) requested by O-CU. O-DU uses the F1 interface to inform O-CU about activation status for cells requested.

NOTE 3: Shared O-RU becomes operational with O-DU#1 with cell on air and ready to serve UEs.

NOTE 4: SMO collects alarms and performance management data from O-DU#1.

NOTE 5: The active O-DU can be no longer operational for a variety of reasons. (see the “Begins when” section).

NOTE 6: There might be multiple other O-DUs, but only one active O-DU. The management system, SMO, shall know and coordinate and ensure that there is only one active O-DU.

NOTE 7: There are preconditions that are relevant and necessary for this to happen. It is necessary that a call home between the O-RU and standby O-DU, and the replication of the configuration information has occurred, and that the standby O-DU has the configuration of the active O-DU.

NOTE 8: The new active O-DU has control only of its carriers. The new O-DU does not handle ALDs.

NOTE 9: Shared O-RU operations are restored with O-DU#2, subsequently services to the users are reestablished, i.e., CUS-plane is up and running.

NOTE 10: SMO collects the alarms and performance management data from O-DU#2.

NOTE 11: The transition of the active role from O-DU#2 back to O-DU#1 involves the same steps as the initial transition from the O-DU#1 to O-DU#2, with the exception of which O-DU is to be activated. This activity is initiated based on a trigger from the SMO and/or the operator's decision.

| | | - -``` - -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber - -Box "Personnel\nShared O-RU Host" #Lightblue - Actor operator as "Operations Actor" -End box - -``` - -``` -Box "Service Management and Orchestration\nShared O-RU Operator" #gold - Participant SMO_a as "Shared O-RU Resiliency\nnrApp" -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant OCU as "O-CU" - - Participant ODU1 as "O-DU\n(#1)" - - Participant ORU as "O-RU\n(Shared)" - - Participant ODU2 as "O-DU\n(#2)" - -End box - -Note over operator, ODU2 - PRECONDITIONS: - Timing setup, all have same sync source - Call home procedure between ORU & (standby) O-DU#2 is done -End Note - -== BEGIN BASIC RESILIENCY USE CASE == - -Note over SMO_a, ODU2 - BASIC RESILIENCY USE CASE - INITIAL SYSTEM SETUP -end Note - -Autonumber 1.1 -group SMO (non RT RIC) configures Cells and O-DUs with Active and Standby operations -SMO_a -> ODU1 : <> Configures O-DU#1 to take active role -ODU1 -> ORU : <> Configuration of Carriers -SMO_a -> ODU2 : <> Configures O-DU#2 to take standby role -SMO_a -> OCU : <> Cell(s) to be activated -Note over OCU, ORU - Cell(s) and carriers activation process -End note -Note over OCU, ORU -``` - -Cell(s) and corresponding carriers activated - -End note - -end - -Note over ODU1, ORU - -Shared O-RU is operational, connected, in service - -(M-Plane, CU-Plane are up and running) - -End Note - -Note over SMO\_a, ODU1 - -SMO collects alarms and performance counters from O-DU#1 - -End note - -Note over SMO\_a, ODU2 - -BASIC RESILIENCY USE CASE - O-DU#1 FAILURE DETECTION - -end Note - -Autonumber 2 - -ODU1 -> ODU1 : ODU #1 Fails (Operational State = disabled) - -note left - -Active ODU for - -the Shared O-RU fails - -end note - -ORU --> ODU2 : <> O-RU raises alarms to Subscriber - -ODU2 --> SMO\_a : <> O-RU alarm (forwarded) - -SMO\_a -> OCU : <> Remove Cell(s) - -Note over SMO\_a, ODU2 - -BASIC RESILIENCY USE CASE - RECOVER SHARED O-RU OPERATION - -end Note - -Autonumber 6.1 - -group SMO triggers O-DU switch for recovering the Shared O-RU operation - -``` - -SMO_a -> ODU2 : <> Configures O-DU#2 to take active role - -ODU2 <- ODU2 : Standby ODU#2 becomes\n the active O-DU - -ODU2 --> ORU : <> Configuration of Carriers - -SMO_a -> OCU : <> Cell(s) to be activated - -Note over OCU, ORU - -Cell(s) and carriers activation process - -End note - -Note over OCU, ORU - -Cell(s) and corresponding carriers activated - -End note - -End - -Note over ORU, ODU2 - -Shared O-RU is operational again, connected, in service - -(M-Plane, CUS-Plane is up and running) - -end Note - -Note over SMO_a, ODU2 - -SMO collects alarms and performance counters from O-DU#2 - -end note - -Note over SMO_a, ODU1 - -Active role transition from O-DU#2 to O-DU#1 involves same steps transitioned -from O-DU#1 to O-DU#2, except which O-DU to be activated. This activity is -based on trigger from SMO and/or operator's decision. - -end note - -== END BASIC RESILIENCY USE CASE == - -@enduml - -``` - -The flow diagram of the basic resiliency use case is given in figure 4.20.3.8-1. - -![Sequence diagram for Basic Resiliency Use Case. Lifelines: Personnel Shared O-RU Host (Operations Actor), Service Management and Orchestration Shared O-RU Operator (Shared O-RU Resiliency rApp), O-RAN Shared O-RU Operator (O-CU, O-DU #1, O-RU (Shared), O-DU #2). The diagram shows system setup, failure detection when O-DU #1 fails, and recovery by activating O-DU #2.](e010000311ed958dd0bc2b16f8cc23d4_img.jpg) - -**PRECONDITIONS:** -Timing setup, all have same sync source -Call home procedure between ORU & (standby) O-DU#2 is done - -**BEGIN BASIC RESILIENCY USE CASE** - -**BASIC RESILIENCY USE CASE - INITIAL SYSTEM SETUP** - -**SMO (non RT RIC) configures Cells and O-DUs with Active and Standby operations** - -- 1.1 «O1» Configures O-DU#1 to take active role -- 1.2 «FH» Configuration of Carriers -- 1.3 «O1» Configures O-DU#2 to take standby role -- 1.4 «O1» Cell(s) to be activated - -Cell(s) and carriers activation process -Cell(s) and corresponding carriers activated - -Shared O-RU is operational, connected, in service (M-Plane, CU-Plane are up and running) - -SMO collects alarms and performance counters from O-DU#1 - -**BASIC RESILIENCY USE CASE - O-DU#1 FAILURE DETECTION** - -- Active ODU for the Shared O-RU fails -- 2 ODU #1 Fails (Operational State = disabled) -- 3 «OFH» O-RU raises alarms to Subscriber -- 4 «O1» O-RU alarm (forwarded) -- 5 «O1» Remove Cell(s) - -**BASIC RESILIENCY USE CASE - RECOVER SHARED O-RU OPERATION** - -**SMO triggers O-DU switch for recovering the Shared O-RU operation** - -- 6.1 «O1» Configures O-DU#2 to take active role -- 6.2 Standby ODU#2 becomes the active O-DU -- 6.3 «OFH» Configuration of Carriers -- 6.4 «O1» Cell(s) to be activated - -Cell(s) and carriers activation process -Cell(s) and corresponding carriers activated - -Shared O-RU is operational again, connected, in service (M-Plane, CUS-Plane is up and running) - -SMO collects alarms and performance counters from O-DU#2 - -Active role transition from O-DU#2 to O-DU#1 involves same steps transitioned from O-DU#1 to O-DU#2, except which O-DU to be activated. This activity is based on trigger from SMO and/or operator's decision. - -**END BASIC RESILIENCY USE CASE** - -Sequence diagram for Basic Resiliency Use Case. Lifelines: Personnel Shared O-RU Host (Operations Actor), Service Management and Orchestration Shared O-RU Operator (Shared O-RU Resiliency rApp), O-RAN Shared O-RU Operator (O-CU, O-DU #1, O-RU (Shared), O-DU #2). The diagram shows system setup, failure detection when O-DU #1 fails, and recovery by activating O-DU #2. - -Figure 4.20.3.8-1: Basic resiliency use case - -#### 4.20.3.9 Antenna calibration use case of a Shared O-RU for Single-MNO - -The following describes the solution for the antenna calibration sub-use case for a Shared O-RU in a Single-MNO configuration. - -The step-by-step details of the antenna calibration use case of a Shared O-RU are captured in table 4.20.3.9-1. - -**Table 4.20.3.9-1: Antenna calibration use case of a Shared O-RU** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal |

The host O-DU performs an antenna calibration procedure with the Shared O-RU.

The O-DU reports antenna calibration results to the SMO.

| | -| Actors and Roles |

Shared O-RU performs the antenna calibration procedure.

O-DU (host) can request for antenna calibration procedure with Shared O-RU.

SMO can receive results from calibration.

| | -| Assumptions |

O-DU has connectivity to O-RU.

All actors are operational and have initialized.

Fronthaul control and user plane is operational between O-DU and Shared O-RU.

| | -| Begins when |
  1. The Shared O-RU has detected that antenna calibration is required.
  2. The O-DU initiates an antenna calibration procedure.
| | -| Step 1.1 (O) |

Recalibration required (O-RU initiated)

The Shared O-RU has detected that antenna calibration is needed and sends an antenna calibration needed notification to the host O-DU over the open FH. In this case, the O-RU initiates the calibration procedure.

| | -| Step 1.2 (O) |

Calibration request

The host O-DU requests for antenna calibration procedure to start for Shared O-RU.

| | -| Step 1 (M) |

Calibration request (O-DU initiated)

The host O-DU requests for antenna calibration procedure to start for Shared O-RU. In this case the O-DU initiates the calibration procedure.

| | -| Step 2 (M) |

Calibration operation at O-RU

Shared O-RU performs antenna calibration procedure.

| | -| Step 3 (M) |

Calibration response

Shared O-RU responds with antenna calibration results.

| | -| Step 4 (M) |

Calibration results

| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | The O-DU returns antenna calibration results to SMO. | | -| Ends when | (1) Antenna calibrated: Antenna calibration procedure has finished, and results reported. | | -| Exceptions | The O-RU may indicate a calibration failure, which is reported to the O-DU. The O-DU logs the failure and notifies north-bound entities. | | -| Post Conditions | None. | | - -``` - -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber 1 - -Box "Service Management\nand Orchestration (SMO)" #gold - Participant SMO as "Antenna Calibration\nService" -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant ODU1 as "O-DU\n(#1) Host" - Participant ODU2 as "O-DU\n(#2)" - participant ORU as "O-RU\n(Shared)" -End box - -== ANTENNA CALIBRATION PROCEDURE BEGIN (Hybrid) == - -hnote over ODU1, ORU -<> Fronthaul Control & User Plane for partitioned carrier #1 -end note - -hnote over ODU2, ORU -<> Fronthaul Control & User Plane for partitioned carrier #2 - -``` - -``` -end note -``` - -``` -alt ORU Initiated Calibration -``` - -``` -Autonumber 1.1 -``` - -``` -ORU->ODU1: <> Recalibration Needed Notification -``` - -``` -ODU1->ORU: <> Request Antenna Calibration Procedure -``` - -``` -Else ODU Initiated Calibration -``` - -``` -Autonumber 1 -``` - -``` -ODU1->ORU: <> Request Antenna Calibration Procedure -``` - -``` -End -``` - -``` -ORU->ORU: Perform\nAntenna\nCalibration\nProcedure -``` - -``` -ORU->ODU1: <> Respond Antenna Calibration Procedure Results -``` - -``` -ODU1->SMO: <> Respond Antenna\nCalibration Procedure Results -``` - -``` -== ANTENNA CALIBRATION PROCEDURE END (Hybrid) == -``` - -``` -@enduml -``` - -The flow diagram of the antenna calibration use case of a Shared O-RU for Single-MNO is given in figure 4.20.3.9-1. - -![Sequence diagram for Antenna calibration use case of a Shared O-RU for Single-MNO. Lifelines: Service Management and Orchestration (SMO), O-RAN Shared O-RU Operator (containing O-DU #1 Host, O-DU #2, and O-RU (Shared)). The procedure begins with 'ANTENNA CALIBRATION PROCEDURE BEGIN (Hybrid)'. It includes two 'Fronthaul Control & User Plane' messages for partitioned carriers #1 and #2. An 'alt' block titled '[ORU Initiated Calibration]' contains steps 1.1 (Recalibration Needed Notification) and 1.2 (Request Antenna Calibration Procedure). Another 'alt' block titled '[ODU Initiated Calibration]' contains step 1 (Request Antenna Calibration Procedure). Step 2 is 'Perform Antenna Calibration Procedure' on the O-RU. Step 3 is 'Respond Antenna Calibration Procedure Results' from the O-RU to the O-DUs. Step 4 is 'Respond Antenna Calibration Procedure Results' from the O-DUs to the SMO. The procedure ends with 'ANTENNA CALIBRATION PROCEDURE END (Hybrid)'.](a4a23a6cfd603aea55a02bae13456e8e_img.jpg) - -Sequence diagram for Antenna calibration use case of a Shared O-RU for Single-MNO. Lifelines: Service Management and Orchestration (SMO), O-RAN Shared O-RU Operator (containing O-DU #1 Host, O-DU #2, and O-RU (Shared)). The procedure begins with 'ANTENNA CALIBRATION PROCEDURE BEGIN (Hybrid)'. It includes two 'Fronthaul Control & User Plane' messages for partitioned carriers #1 and #2. An 'alt' block titled '[ORU Initiated Calibration]' contains steps 1.1 (Recalibration Needed Notification) and 1.2 (Request Antenna Calibration Procedure). Another 'alt' block titled '[ODU Initiated Calibration]' contains step 1 (Request Antenna Calibration Procedure). Step 2 is 'Perform Antenna Calibration Procedure' on the O-RU. Step 3 is 'Respond Antenna Calibration Procedure Results' from the O-RU to the O-DUs. Step 4 is 'Respond Antenna Calibration Procedure Results' from the O-DUs to the SMO. The procedure ends with 'ANTENNA CALIBRATION PROCEDURE END (Hybrid)'. - -Figure 4.20.3.9-1: Antenna calibration use case of a Shared O-RU for Single-MNO - -#### 4.20.3.10 Rehoming use case of a Shared O-RU for Single-MNO - -The following will describe the solution for the rehoming sub-use case for a Shared O-RU. - -The context of the rehoming use case of a Shared O-RU for Single-MNO is captured in table 4.20.3.10-1. - -Table 4.20.3.10-1: Rehoming use case of a Shared O-RU for Single-MNO - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | A Shared O-RU is rehomed and is able to pair with new O-DU or existing (previous) O-DU parents. | | -| Actors and Roles | Shared O-RU is the element that is rehomed.
Host O-DU (old) is the original Shared O-RU parent.
SRO O-DU (old) is another original O-DU Shared O-RU is connected to. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| |

Host O-DU (new) is the new Shared O-RU parent.

SRO O-DU (new) is another new O-DU Shared O-RU is connected to.

SMO can receive results from calibration.

| | -| Assumptions |

The Shared O-RU is in a deployment with the original (old) O-DUs and will be moved to the new ones or could stay with original O-DUs (as parents).

(Typically) the operator will plan a Shared O-RU rehoming activity before they actually perform the operations related to the move.

| | -| Begins when |

This use case starts with any of these three situations:

Case #1 starts when the Shared O-RU is physically moved to a new location (however still connected to original O-DUs).

Case #2 starts when the Shared O-RU is physically moved to a new location but is connected to new O-DUs.

Case #3 starts when the Shared O-RU stays in same physical location but is connected to new O-DUs (management-initiated rehoming).

| | -| Case #1 – O-RU is physically moved with same O-DU parents | | | -| Step 1 (M) |

Shared O-RU is disconnected from original O-DUs

The Shared O-RU is physically disconnected (fiber disconnected) from the existing O-DU parents.

Then, the Shared O-RU is physically moved to a new location.

| | -| Step 2 (M) |

Shared O-RU is reconnected to original O-DUs

The Shared O-RU is either physically reconnected (different fiber) or connected at the transport layer (with the original fiber) to the original O-DU parents, and the following sub-use cases are triggered as a result:

  • • Shared O-RU startup sub-use case
  • • Configuration sub-use case
  • • Resource partitioning sub-use case
  • • Reset sub-use case supervision sub-use case
| | -| Case #2 – O-RU is physically moved with new O-DU parents | | | -| Step 1 (M) |

Shared O-RU is disconnected from original O-DUs

The Shared O-RU is physically disconnected (fiber disconnected) from the former O-DU parents.

| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | Then, the Shared O-RU is physically moved to a new location. | | -| Step 2 (M) | Shared O-RU is connected to new O-DUs

The Shared O-RU is either physically reconnected (different fiber) or connected at the transport layer (with the original fiber) to new O-DU parents, and the following sub-use cases are triggered as a result:
  • • Shared O-RU startup sub-use case
  • • Configuration sub-use case
  • • Resource partitioning sub-use case
  • • Reset sub-use case supervision sub-use case
| | -| Case #3 – Management initiated rehoming | | | -| Step 1 (M) | Management initiated rehoming for Shared O-RU

Shared O-RU already has physical front-haul connections in place.

SMO initiates rehoming operation with connected O-DUs to the Shared O-RU. | | -| Step 2 (M) | Shared O-RU starts up

The Shared O-RU starts up with the new O-DU parents, and the following sub-use cases are triggered as a result:
  • • Shared O-RU startup sub-use case
  • • Configuration sub-use case
  • • Resource partitioning sub-use case
  • • Reset sub-use case supervision sub-use case
| | -| Ends when | The Shared O-RU has been moved and connected to the appropriate O-DUs, and is operational again. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|---------------------------|-------------------------| -| Exceptions | None. | | -| Post Conditions | None. | | - -``` - -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber 1 - -Box "Service Management\nand Orchestration (SMO)" #gold - Participant CFG as "Configuration\nManagement" - Participant SMO as "Shared O-RU\nOrchestration\nrApp" -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant ODU1 as "O-DU\n(#1) Host" - Participant ODU2 as "O-DU\n(#2)" - Participant ORU as "O-RU\n(Shared)" -End box - -== BEGIN CASE #1 PHYSICAL REHOMING OF THE SHARED O-RU SAME O-DUs == - -hnote over ODU1, ORU -The O-RU FH is disconnected -from O-DU #1, O-DU #2 -end note - -ORU -> ORU: O-RU FH is \ndisconnected - -``` - -``` -hnote over ORU -``` - -``` -The O-RU is -``` - -``` -physically moved -``` - -``` -to a new location -``` - -``` -end note -``` - -``` -hnote over ODU1, ORU -``` - -``` -The O-RU FH is reconnected -``` - -``` -to O-DU #1, O-DU #2 -``` - -``` -end note -``` - -``` -ORU -> ORU: O-RU FH is \nconnected -``` - -``` -hnote over ODU1, ORU -``` - -``` -The O-RU Starts up with O-DU1 and O-DU2 -``` - -``` -end note -``` - -``` -Ref over CFG, ORU: Shared O-RU Startup Sub Use Case \n Configuration Sub Use Case\n Resource Partitioning Sub Use Case\n Reset Sub Use Case\n Supervision Sub Use Case -``` - -``` -== END PHYSICAL REHOMING OF THE SHARED O-RU SAME O-DUs == -``` - -``` -@enduml -``` - -The flow diagram of the rehoming use case of a Shared O-RU for Single-MNO is given in figure 4.20.3.10-1. - -![Sequence diagram showing the physical rehoming of a shared O-RU. Lifelines: Service Management and Orchestration (SMO) with Configuration Management and Shared O-RU Orchestration rApp; O-RAN Shared O-RU Operator with O-DU (#1) Host, O-DU (#2), and O-RU (Shared). The process involves disconnecting the O-RU FH, physically moving the O-RU, reconnecting the FH, and starting up with both O-DUs. A 'ref' block lists sub use cases: Startup, Configuration, Resource Partitioning, Reset, and Supervision.](90da64796f3fd458293c318340438e70_img.jpg) - -**Service Management and Orchestration (SMO)** - -- Configuration Management -- Shared O-RU Orchestration rApp - -**O-RAN Shared O-RU Operator** - -- O-DU (#1) Host -- O-DU (#2) -- O-RU (Shared) - -**BEGIN CASE #1 PHYSICAL REHOMING OF THE SHARED O-RU SAME O-DUs** - -The O-RU FH is disconnected from O-DU #1, O-DU #2 - -1 O-RU FH is disconnected - -The O-RU is physically moved to a new location - -The O-RU FH is reconnected to O-DU #1, O-DU #2 - -2 O-RU FH is connected - -The O-RU Starts up with O-DU1 and O-DU2 - -**ref** - -Shared O-RU Startup Sub Use Case - Configuration Sub Use Case - Resource Partitioning Sub Use Case - Reset Sub Use Case - Supervision Sub Use Case - -**END PHYSICAL REHOMING OF THE SHARED O-RU SAME O-DUs** - -Sequence diagram showing the physical rehoming of a shared O-RU. Lifelines: Service Management and Orchestration (SMO) with Configuration Management and Shared O-RU Orchestration rApp; O-RAN Shared O-RU Operator with O-DU (#1) Host, O-DU (#2), and O-RU (Shared). The process involves disconnecting the O-RU FH, physically moving the O-RU, reconnecting the FH, and starting up with both O-DUs. A 'ref' block lists sub use cases: Startup, Configuration, Resource Partitioning, Reset, and Supervision. - -Figure 4.20.3.10-1: Rehome by physically moving Shared O-RU with same O-DU for Single-MNO - -``` -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -``` - -``` -skinparam BoxPadding 10 - -skinparam defaultFontSize 14 - -autonumber 1 - -Box "Service Management\nand Orchestration (SMO)" #gold - Participant CFG as "Configuration\nManagement" - Participant SMO as "Shared O-RU\nOrchestration\nnrApp" -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant ODU1 as "O-DU\n(#1) Host" - Participant ODU2 as "O-DU\n(#2)" - Participant ODU3 as "O-DU\n(#3) Host" - Participant ODU4 as "O-DU\n(#4)" - participant ORU as "O-RU\n(Shared)" -End box - -== BEGIN CASE #2 PHYSICAL REHOMING OF THE SHARED O-RU == - -Opt Configuration\npreparation -Alt Hybrid\n Type -hnote over CFG - Preparation for - SMO & O-RU -end note -Else Hierarchical Type -Hnote over CFG - Preparation - for O-DU -End note -End -End - -hnote over ODU1, ORU -``` - -The O-RU FH is disconnected - -from O-DU #1, O-DU #2 - -end note - -ORU -> ORU: O-RU FH is \ndisconnected - -hnote over ORU - -The O-RU is physically - -moved to a new location - -end note - -hnote over ODU3, ORU - -The O-RU FH is reconnected - -to O-DU #3, O-DU #4 - -end note - -ORU -> ORU: O-RU FH is \nconnected - -hnote over ODU3, ORU - -The O-RU Starts up with O-DU3 and O-DU4 - -end note - -Ref over SMO, ORU: Shared O-RU Startup Sub Use Case \n Configuration Sub Use Case\n Resource Partitioning Sub Use Case\n Reset Sub Use Case\n Supervision Sub Use Case - -== END PHYSICAL REHOMING OF THE SHARED O-RU NEW O-DUs == - -== BEGIN CASE #3 MANAGEMENT INITIATED REHOMING OF THE SHARED O-RU == - -SMO -> ODU1: Rehoming Operation - -SMO -> ODU3: Rehoming Operation - -Ref over SMO, ORU: Shared O-RU Startup Sub Use Case \n Configuration Sub Use Case\n Resource Partitioning Sub Use Case\n Reset Sub Use Case\n Supervision Sub Use Case - -== END MANAGEMENT INITIATED REHOMING OF THE SHARED O-RU == - -@enduml - -The flow diagram of the rehoming use case of a Shared O-RU for Single-MNO is given in figure 4.20.3.10-2. - -![Sequence diagram showing the rehome process for a Shared O-RU. The diagram is divided into two main sections: Case #2 (Physical Rehoming) and Case #3 (Management Initiated Rehoming). It shows interactions between the Service Management and Orchestration (SMO) and the O-RAN Shared O-RU Operator (containing multiple O-DUs and a Shared O-RU).](94563c795d36d598e53b9e5b4c95934c_img.jpg) - -The diagram illustrates the interaction between the Service Management and Orchestration (SMO) and the O-RAN Shared O-RU Operator for two rehome scenarios. - -**Participants:** - -- Service Management and Orchestration (SMO):** Contains Configuration Management and Shared O-RU Orchestration rApp. -- O-RAN Shared O-RU Operator:** Contains O-DU (#1) Host, O-DU (#2), O-DU (#3) Host, O-DU (#4), and O-RU (Shared). - -**Case #2: PHYSICAL REHOMING OF THE SHARED O-RU** - -- opt [Configuration preparation]** - - alt [Hybrid Type]** - - Preparation for SMO & O-RU** - - [Hierarchical Type]** - - Preparation for O-DU -- The O-RU FH is disconnected from O-DU #1, O-DU #2. -- 1 O-RU FH is disconnected (indicated by a return message). -- The O-RU is physically moved to a new location. -- The O-RU FH is reconnected to O-DU #3, O-DU #4. -- 2 O-RU FH is connected (indicated by a return message). -- The O-RU Starts up with O-DU3 and O-DU4. -- ref** block containing: - - Shared O-RU Startup Sub Use Case - - Configuration Sub Use Case - - Resource Partitioning Sub Use Case - - Reset Sub Use Case - - Supervision Sub Use Case - -**END PHYSICAL REHOMING OF THE SHARED O-RU NEW O-DUs** - -**Case #3: MANAGEMENT INITIATED REHOMING OF THE SHARED O-RU** - -- 3 Rehoming Operation (message from SMO to O-RU Operator). -- 4 Rehoming Operation (message from O-RU Operator to SMO). -- ref** block containing: - - Shared O-RU Startup Sub Use Case - - Configuration Sub Use Case - - Resource Partitioning Sub Use Case - - Reset Sub Use Case - - Supervision Sub Use Case - -**END MANAGEMENT INITIATED REHOMING OF THE SHARED O-RU** - -Sequence diagram showing the rehome process for a Shared O-RU. The diagram is divided into two main sections: Case #2 (Physical Rehoming) and Case #3 (Management Initiated Rehoming). It shows interactions between the Service Management and Orchestration (SMO) and the O-RAN Shared O-RU Operator (containing multiple O-DUs and a Shared O-RU). - -Figure 4.20.3.10-2: Rehome by physically moving Shared O-RU with new O-DUs for Single-MNO - -#### 4.20.3.11 Reset use case of a Shared O-RU for Single-MNO - -The following describes the solution for the reset sub-use case for a Shared O-RU. - -The context of the reset use case of a Shared O-RU is captured in table 4.20.3.11-1. - -**Table 4.20.3.11-1: Reset use case of a Shared O-RU** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal |

The goal of this sub-use case is to describe the flow related to reset of Shared O-RU for a Single-MNO operator configuration.

This is a service impacting use case.

| | -| Actors and Roles |

Shared O-RU:
The Shared O-RU is a key actor. It undergoes reset in this use case. The Shared O-RU can be reset by intention/request or autonomously.

O-DUs (host/tenant/ &other O-DUs):
All the O-DUs connected to the Shared O-RU are actors are involved in the reset operation. O-DU#1 has the role of the Shared O-RU host, it also has a role of Shared Resource Operator (SRO). O-DU#2 is only an SRO.

SMO:
The SMO is informed by the O-DU that O-RU has been reset or issues a reset.

| | -| Assumptions |

It is assumed that there is always at least one O-DU still operational with the Shared O-RU.

This use case describes the flow for a Single-MNO operator configuration.

| | -| Begins when |

The reset of a Shared O-RU use case can be invoked when there is a direct request to reset the Shared O-RU, or it can be reset autonomously.

There are many possible reasons why a Shared O-RU can need to be intentionally reset. Maintenance, software upgrade, network failure, power outages, communication link issues are just some of the many possible situations where the active O-RU would be reset.

| | -| Pre-conditions |

The Shared O-RU has connectivity to one or more O-DUs (and one of them is serving the primary role).

The Shared O-DU has been configured originally by the active O-DU, and also carriers for the standby O-DUs.

O-DUs have subscribed to alarm notifications successfully.

| | - -| Use Case Stage | Evolution / Specification | <> | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 1 (M) | [Shared O-RU reset flow]

Reset request from SMO

A reset request is communicated from the SMO to the Shared O-RU host (O-DU #1). The reset request can be originated from the SMO for a variety of reasons. | | -| Step 2 (M) | Reset request from O-DU

The reset request is communicated onward from the Shared O-RU host (O-DU #1) to the Shared O-RU through the open front-haul interface. | | -| Step 3 (M) | Reset reply

The Shared O-RU RPC Reply Acknowledge is sent from the Shared O-RU to the Shared O-RU host (O-DU #1). | | -| Step 4 (M) | Shared O-RU reset

Once invoked, the Shared O-RU goes through its reset sequence to complete the reset operation. | | -| Step 5 (M) | Reset response

The Shared O-RU host (O-DU #1) informs the SMO with a reset response. | | -| Step 6 (M) | [Autonomous reset flow]

Autonomous Shared O-RU reset

The Shared O-RU is autonomously reset. | | -| Step 7 (M) | O-DU initial detects loss of connection. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| |

The Shared O-DU host (O-DU #1) detects loss of polling as a result of the autonomous O-RU reset. It can also detect a call home signal from a Shared O-RU that just had a valid M-plane session.

| | -| Step 8 (M) |

O-DU determines loss of connection.

The O-DU can deduce that O-RU has a lost connection with broken polling with the O-DU. The O-DU does not know if the O-RU was performing a reset or if there was other reason for the lost connection, for example, a broken optical fiber. The O-DU can only report lost connection to O-RU in such a case.

The O-DU redetects the Shared O-RU through a call home from the Shared O-RU. Then the Shared O-RU Start up sequence of that sub-use case happens (see the ref flow). Afterwards, the O-DU can read the reset cause from the Shared O-RU.

| | -| Step 9 (M) |

O-DU informs SMO.

When the O-DU #1 starts sensing call home signals from O-RU, O-DU can deduce that O-RU has returns to service after a reset. Afterwards, the O-DU #1 can read the restart cause. Then, the Shared O-DU host can report to SMO that O-RU is re-detected and what was the reason why the O-RU reset. Then O-DU can fill update its aggregated model with details obtained from the O-RU and populate this information to SMO.

Step 14 When O-DU redetects, the SMO can clear the alarm.

| | -| Ends when |

The use case ends the Shared O-RU has reset whether by reset or by autonomous reset.

| | -| Exceptions |

There are many possible exceptions. Some of these include:

The Shared O-RU was not able to successfully reset.

The O-DU #1 was not able to properly detect lost connection with the Shared O-RU through loss of polling or call home signal was never sent.

The O-DU #1 was not able to establish a restore connection to the Shared O-RU after reset.

| | -| Post Conditions |

Successful post condition – On a successful post-condition, the Shared O-RU is reset, and has restored connectivity to the Shared O-RU host (O-DU #1).

| | - -| Use Case Stage | Evolution / Specification | <> | -|----------------|------------------------------------------------------------------------------|-------------| -| | | Related use | -| | Failure post condition – One of the failure exceptions has been encountered. | | - -``` - -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber 1 - -Box "Service Management and Orchestration\nShared O-RU Operator" #gold - Participant R_APP as "Shared O-RU\nOrchestration \nrApp" -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant ODU1 as "O-DU\n(#1)" - Participant ODU2 as "O-DU\n(#2)" - - participant ORU as "O-RU\n(Shared)" -End box - -== RESET OF SHARED O-RU SUB USE CASE == - -hnote over ODU1, ORU -Shared O-RU Reset Operation -end note - -R_APP->ODU1: <> Reset Request to Shared O-RU Host -ODU1->ORU: <> Reset Request - -``` - -ORU->ODU1: <> Reset rpc-reply Acknowledge - -ORU->ORU : Shared\n O-RU Reset\n sequence - -Ref over ORU : Start-up Sub-Use\n Case for Shared O-RU - -ODU2->ODU2: Detect Loss of \nM-Plane \n Connection\nor Call Home Signal - -ODU2->ODU2: Determines Lost\n Connection to O-RU - -ODU2->R\_APP: <> Shared O-RU Communication Lost Alarm - -ODU2-->R\_APP: O-RU Redetected with Restart Cause - -ODU1->R\_APP: <> Reset Response - -== END RESET OF SHARED O-RU SUB USE CASE == - -== AUTONOMOUS RESET OF SHARED O-RU SUB USE CASE == - -ORU->ORU : Autonomous \nShared\n O-RU Reset - -ODU1->ODU1: Detect Loss of \nM-Plane \n Connection\nor Call Home Signal - -ODU1->ODU1: Determines Lost\n Connection to O-RU - -ODU1->R\_APP: <> Shared O-RU Communication Lost Alarm - -ORU->ODU2: About to Reset notification - -ODU2->ODU2: Detect Loss of \nM-Plane \n Connection\nor Call Home Signal - -ODU2->ODU2: Determines Lost\n Connection to O-RU - -ODU2->R\_APP: <> Shared O-RU Communication Lost Alarm - -Ref over ORU : Start-up Sub-Use\n Case for Shared O-RU - -ODU1-->R\_APP: O-RU Redetected with Restart Cause - -ODU2-->R\_APP: O-RU Redetected with Restart Cause - -``` -== END AUTONOMOUS RESET OF SHARED O-RU SUB USE CASE == -``` - -``` -@enduml -``` - -The flow diagram of the reset use case is given in figure 4.20.3.11-1. - -![Sequence diagram for Reset use case. Lifelines: Service Management and Orchestration Shared O-RU Operator (Shared O-RU Orchestration rApp), O-RAN Shared O-RU Operator (O-DU #1, O-DU #2, O-RU (Shared)). The diagram is divided into two sub-use cases: 'RESET OF SHARED O-RU SUB USE CASE' and 'AUTONOMOUS RESET OF SHARED O-RU SUB USE CASE'.](5b41b3f299c364a673453693f7cf0689_img.jpg) - -**Service Management and Orchestration Shared O-RU Operator** - -Shared O-RU Orchestration rApp - -**O-RAN Shared O-RU Operator** - -O-DU (#1)      O-DU (#2)      O-RU (Shared) - ---- - -**RESET OF SHARED O-RU SUB USE CASE** - -Shared O-RU Reset Operation - -1 <> Reset Request to Shared O-RU Host - -2 <> Reset Request - -3 <> Reset rpc-reply Acknowledge - -4 Shared O-RU Reset sequence - -ref - -Start-up Sub-Use Case for Shared O-RU - -5 Detect Loss of M-Plane Connection or Call Home Signal - -6 Determines Lost Connection to O-RU - -7 <> Shared O-RU Communication Lost Alarm - -8 O-RU Redetected with Restart Cause - -9 <> Reset Response - -**END RESET OF SHARED O-RU SUB USE CASE** - ---- - -**AUTONOMOUS RESET OF SHARED O-RU SUB USE CASE** - -10 Autonomous Shared O-RU Reset - -11 Detect Loss of M-Plane Connection or Call Home Signal - -12 Determines Lost Connection to O-RU - -13 <> Shared O-RU Communication Lost Alarm - -14 About to Reset notification - -15 Detect Loss of M-Plane Connection or Call Home Signal - -16 Determines Lost Connection to O-RU - -17 <> Shared O-RU Communication Lost Alarm - -ref - -Start-up Sub-Use Case for Shared O-RU - -18 O-RU Redetected with Restart Cause - -19 O-RU Redetected with Restart Cause - -**END AUTONOMOUS RESET OF SHARED O-RU SUB USE CASE** - ---- - -Shared O-RU Orchestration rApp      O-DU (#1)      O-DU (#2)      O-RU (Shared) - -Sequence diagram for Reset use case. Lifelines: Service Management and Orchestration Shared O-RU Operator (Shared O-RU Orchestration rApp), O-RAN Shared O-RU Operator (O-DU #1, O-DU #2, O-RU (Shared)). The diagram is divided into two sub-use cases: 'RESET OF SHARED O-RU SUB USE CASE' and 'AUTONOMOUS RESET OF SHARED O-RU SUB USE CASE'. - -**Figure 4.20.3.11-1: Reset use case** - -#### 4.20.3.12 Advanced resiliency sub-use cases of a Shared O-RU for Single-MNO - -Advanced resiliency sub-use cases describe interactions between actors for resiliency operations. - -##### 4.20.3.12.1 Advanced resiliency sub-use case with 1 O-DU active + 1 O-DU standby (1+1) - -The context of the advanced resiliency sub-use case with 1 O-DU active + 1 O-DU standby (1+1) is captured in table 4.20.3.12.1-1. - -**Table 4.20.3.12.1-1: Advanced resiliency sub-use case with 1 O-DU active + 1 O-DU standby (1+1)** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal |

The objective of this sub-use case is to manage resiliency operations involving the active and stand-by O-DUs with the Shared O-RU. This includes system behaviour in situations such as partial O-DU failures, interface failures, and power outages related to the O-DU. This ensures to restore the service availability to end users.

This is a service impacting use case.

| | -| Actors and Roles |

Shared O-RU:
The Shared O-RU handles the fronthaul and air interfaces and the reporting of performance counters and failures.

O-DUs (active/stand-by O-DUs):
O-DUs may receive configurations from SMO. The O-DU may report performance counters and alarms to SMO. The O-DU is also responsible for configuring and collecting the performance data and alarms from O-RU(s) in hierarchical deployment. This use case focusses on active / stand-by role change for O-DUs to minimize service disruption.

O-CU:
O-CU receives cell related configurations from SMO and available cell details from O-DU(s). Respectively to available resources reported by O-DU and desired availability of cells received from SMO. The O-CU activates or deactivates the cells in the O-DU using F1 interface.

SMO:
The SMO configures the role of O-DUs as active and standby O-DUs and informs these roles to Shared O-RU through O-DU in hierarchical deployment or directly in case of hybrid deployment. SMO also makes high-level decisions about O-DU role change based on e.g., received alarms and degraded performance.

| | -| Assumptions |

The assumptions are based on the premise that there will always be at least one O-DU remains operational with the Shared O-RU.

| | -| Begins when |

This use case is triggered when the SMO detects the partial failure related to active O-DU based on alarms or service performance degradation. The use case may also be triggered due to various interfaces malfunction or service degradation.

| | -| Pre-conditions |
  1. The Shared O-RU is on.
  2. Prior carrier activation (step 6) O-RU's sync-state is "locked".
  3. All actors are connected to same sync source.
| | -| Step 1 (M) |

The SMO may configure O-DU#1 to take active role in controlling the Shared O-RU. It then configures the cells and corresponding carrier resources (including NRCGI(s) for the cells) via the O1 interface.

| | -| Step 2 (M) |

O-DU configures the [tr]x-array-carrier(s) in O-RU, corresponding to the carrier resources outlined in step 1.

| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 3 (M) | The SMO may configure O-DU#2 to take stand-by role via O1 interface. | | -| Step 4 (M) | SMO may provide O-CU with information regarding which cell(s) (NRCGI(s)) associated with O-DU#1 need to be activated. | | -| Step 5 (M) | When cells and corresponding carriers are configured and available for service, the O-DU informs O-CU about cells availability using F1 interface. | | -| Step 6 (M) | O-CU requests O-DU#1 to activate the cell(s) (NRCGI(s)), using the associated messages exchanged via the F1 interface. | | -| Step 7 (M) | O-DU#1 activates the [tr]x-array-carrier(s) in O-RU that are associated with the specific cell(s) (NRCGI(s)) requested for activation in step 6. | | -| Step 8 (M) | O-DU#1 activates the cell(s) as requested by O-CU in step 6. | | -| Step 9 (M) | O-DU#1 uses the F1 interface to inform O-CU about activation status for cells requested in step 6.

See NOTE 1. | | -| Advanced resiliency use case for partial failure (interface or node)/performance degrade scenarios. SMO makes a high-level decision to make the Shared O-RU remains operational by initiating an O-DU switch | | | -| Step 10.1 (M) | See NOTE 2 and NOTE 3.

The SMO set the administrative state of the O-DU#1 to “locked” and its operational state is set to “disabled”.

See NOTE 4. | | -| Step 10.2 (M) | SMO removes the cell(s) configuration from O-DU#1. This results in removal of the associated carrier resources from Shared O-RU.

See NOTE 5. | | -| Step 10.3 (M) | O-DU#1 may send the RPCs to the O-RU via fronthaul M-plane to deactivate and remove the U-plane configurations related to cell(s) mentioned in Step 9.1.

See NOTE 6. | | -| Step 10.4 (M) | O-DU#1 informs O-CU about the cell(s) removal using associated messages via F1 interface.

See NOTE 7. | | -| Step 10.5 (M) | The SMO configures the cells (including NRCGI) and corresponding carrier resources to O-DU#2 via O1 interface. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 10.6 (M) | O-DU configures the [tr]x-array-carrier(s) in O-RU, corresponding to the carrier resources outlined in step 10.5. | | -| Step 10.7 (M) | SMO provides O-CU with information regarding which cell(s) (NRCGI(s)) associated with O-DU#2 need to be activated. | | -| Step 10.8 (M) | O-DU#2 informs O-CU, about the added cell(s) (NRCGI(s)) that are ready for activation via F1 interface using the associated messages. | | -| Step 10.9 (M) | O-CU requests O-DU#2 to activate the cell(s) (NRCGI(s)), using the associated messages exchanged via the F1 interface. | | -| Step 10.10 (M) | O-DU#2 activated [tr]x-array-carriers related to cells (NRCGI) requested by O-CU in step 10.9. | | -| Step 10.11 (M) | O-DU#2 activates the cell(s) that were specified by O-CU in step 10.9. | | -| Step 10.12 (M) | O-DU#2 informs O-CU about the cell(s) that are activated using associated messages via F1 interface.

See NOTE 8, NOTE 9 and NOTE 10. | | -| Ends when | This use case ends when roles are changed as per SMO's request (or when their process ends with non-recoverable error). | | -| Exceptions | There are several exceptions that may occur during this process. These include:

  1. 1. Shared O-RU fails during a switch over.
  2. 2. If the standby O-DU #2 also becomes unavailable when it is due to become active.
  3. 3. If same event messaging for the flow is lost.
  4. 4. If configuration provided to O-DU or O-CU is improper.
  5. 5. If the connectivity or functionality of the management system (SMO) becomes unavailable.
| | -| Post Conditions | Successful post condition – O-DU's roles are changed successfully, services for end users are available.

Failure post condition– O-RU does not have active O-DU connected and services for end user are not available. | | -| NOTE 1: Shared O-RU becomes operational with O-DU#1 with cell on air and ready to serve UEs.

NOTE 2: SMO collects alarms and performance management data from O-DU#1.

NOTE 3: When analysing the active alarms and performance counters, SMO may detect a partial failure of O-DU#1. Scenario continues in case of partial failure is detected.

NOTE 4: The meanings of administrate and operational states are defined in ITU-T X.731 [18].

NOTE 5: If the above role change is due to M-plane failure between O-DU#1 and Shared O-RU, then O-DU#1 would not have access to O-RU and hence cannot remove carriers. | | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| |

NOTE 6: If M-plane failure occurs between O-DU#1 and Shared O-RU, then the O-DU#1 would not have access to O-RU and cannot deactivate and remove carriers.

NOTE 7: If F1 interface failure occurs between O-CU and O-DU#1, then the O-DU#1 would not have access to O-CU and hence it cannot request for cell(s) removal.

NOTE 8: Shared O-RU operations are restored with O-DU#2 and begins providing services to the users, i.e., CUS-plane is up and running.

NOTE 9: SMO collects the alarms and performance management data from O-DU#1 (if it is only partial failure and not lost communication, list of available PM counters reported by O-DU#1 will probably be reduced (when compared to the list available from fully operational O-DU)) and O-DU#2.

NOTE 10: The transition of the active role from O-DU#2 back to O-DU#1 involves the same steps as the initial transition from the O-DU#1 to O-DU#2, with the exception of which O-DU is to be activated. This activity is initiated based on a trigger from the SMO and/or the operator's decision.

| | - -``` - -@startuml -!pragma teoz true - -skin rose - -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -skinparam sequenceMessageAlign center -autonumber - -Box "Personnel\nShared O-RU Host" #Lightblue - Actor operator as "Operations Actor" -End box - -Box "Service Management and Orchestration\nShared O-RU Operator (non RT RIC)" #gold - Participant SMO_a as "Shared O-RU Resiliency\nSMO(non-RT RIC)" -End box - -Box "O-RAN\nShared O-RU Operator" #lightpink - - Participant OCU as "O-CU" - - Participant ODU1 as "O-DU\n(#1)" - - participant ORU as "O-RU\n(Shared)" - - Participant ODU2 as "O-DU\n(#2)" - -End box - -``` - -Note over operator, ODU2 - -PRECONDITIONS: - -Shared O-RU is on - -Prior carrier activation (step 6) O-RU's sync-state is "locked" - -All have same sync source - -End Note - -== BEGIN ADVANCED RESILIENCY USE CASE == - -group SMO (non RT RIC) configures Cells and O-DUs with Active and Standby operations - -SMO\_a -> ODU1 : <> Configures O-DU#1 to take active role and configures cell(s) and \ncorresponding carrier(s)resources (including NRCGI(s) for the cell(s)) - -ODU1 -> ORU : <> [tr]x-array-carrier(s) configuration - -SMO\_a -> ODU2 : <> Configures O-DU#2 to take standby role - -SMO\_a -> OCU : <> Provides O-CU with information about which \ncell(s) (NRCGI(s)) to be activated - -OCU <- ODU1 : <> Cell(s) (NRCGI(s)) ready for activation - -OCU -> ODU1 : <> Request for cell(s) (NRCGI(s)) activation - -ODU1 -> ORU : <> Activates the [tr]x-array-carrier(s) in O-RU that \nis associated with specific Cell(s) (NRCGI(s)) - -ODU1 -> OCU : Activates cell(s) as per O-CU request - -OCU <- ODU1 : <> Cell(s) activated - -end - -Note over ODU1, ORU - -Shared O-RU is operational, connected, in service - -CUS-Plane is up and running) - -End Note - -Note over SMO\_a, ODU1 - -SMO collects alarms and performance counters from O-DU#1 - -End note - -Note over SMO\_a, ODU2 - -ADVANCED RESILIENCY USE CASE FOR PARTIAL FAILURES OF O-DU AND PARTIAL FAILURE (INTERFACE OR NODE)/PERFORMANCE DEGRADE SCENARIOS - -End Note - -Note over SMO\_a, ORU - -\*\*Advanced Resiliency use case failure scenarios:\*\* - -SMO detects the partial failure related to O-DU#1 based on alarms or service performance degradation based on KPIs - -End Note - -Note over SMO\_a, ODU2 - -SMO MAKES A HIGH LEVEL DECISION TO THE OPERATION OF THE SHARED O-RU OPERATIONAL BY INITIATING AN O-DU SWITCH - -End Note - -group The SMO(non-RT RIC) initiates an O-DU switch to restore the operation of the Shared O-RU - -Autonumber 10.1 - -group SMO triggers the switch or transition of the O-DU - -SMO\_a -> ODU1 : <> Lock the O-DU - -SMO\_a -> ODU1 : <> Removes the cell(s) that were served - -ODU1 -> ORU : <> Removes the [tr]x-array-carrier(s) \nconfigurations of related cell(s) - -OCU <- ODU1 : <> Cell(s) removal - -SMO\_a -> ODU2 : <> Configures O-DU#2 to take active role and configures cell(s) and corresponding carrier(s)resources (including NRCGI(s) for the cell(s)) - -ODU2 -> ORU : <> [tr]x-array-carrier(s) configuration - -SMO\_a -> OCU : <> Provides O-CU with information about which \ncell(s) (NRCGI(s)) to be activated - -OCU <- ODU2 : <> Cell(s) (NRCGI(s)) ready for activation - -OCU -> ODU2 : <> Request for cell(s) (NRCGI(s)) activation - -ODU2 -> ORU : <> Activates the [tr]x-array-carrier(s) in O-RU that is \n associated with specific Cell(s) (NRCGI(s)) - -ODU2 <- ODU2 : Activates cell(s) as per O-CU request - -OCU <- ODU2 : <> Cell(s) activated - -end - -Note over ODU2, ORU - -Shared O-RU is operational again,connected, in service - -(CUS-Plane is up and running) - -End Note - -Note over SMO\_a, ODU2 - -SMO collects alarms and performance counters from O-DU#2 - -End note - -Note over SMO\_a, ODU1 - -Active role transition from O-DU#2 to O-DU#1 involves same steps transitioned from O-DU#1 to O-DU#2, except which O-DU to be activated. This activity is based on trigger from SMO and/or operator's decision. - -End note - -End - -== END ADVANCED RESILIENCY USE CASE == - -@endum1 - -The flow diagram of the advanced resiliency sub-use case with 1 O-DU active + 1 O-DU standby (1+1) is given in figure 4.20.3.12.1-1. - -![Sequence diagram for Advanced resiliency sub-use case implementation flow for 1 active + 1 standby O-DUs. Lifelines: Personnel Shared O-RU Host (Operations Actor), Service Management and Orchestration Shared O-RU Operator (non RT RIC) (Shared O-RU Resiliency SMO(non-RT RIC)), O-RAN Shared O-RU Operator (O-CU, O-DU (#1), O-RU (Shared), O-DU (#2)).](ed433287faf6ca3f88eaaf14968986d6_img.jpg) - -**PRECONDITIONS:** -Shared O-RU is on -Prior carrier activation (step 6) O-RU's sync-state is 'locked' -All have same sync source - -**BEGIN ADVANCED RESILIENCY USE CASE** - -1 «O» SMO (non RT RIC) configures O-DU#1 to take active role and configures cell(s) and corresponding carrier(s)/resources (including NRCG(s) for the cell(s)) - 2 «FH» [tr]v-array-carrier(s) configuration - 3 «O» SMO (non RT RIC) configures O-DU#2 to take standby role - 4 «O» SMO (non RT RIC) provides O-CU with information about which cell(s)/NRCG(s) to be activated - 5 «F1» Cell(s) (NRCG(s)) ready for activation - 6 «F1» Request for cell(s) (NRCG(s)) activation - 7 «FH» Activates the [tr]v-array-carrier(s) in O-RU that is associated with specific Cell(s) (NRCG(s)) - 8 Activates cell(s) as per O-CU request - 9 «F1» Cell(s) activated - -Shared O-RU is operational, connected, in service (CUS-Plane is up and running) - -SMO collects alarms and performance counters from O-DU#1 - -**ADVANCED RESILIENCY USE CASE FOR PARTIAL FAILURES OF O-DU AND PARTIAL FAILURE (INTERFACE OR NODE)/PERFORMANCE DEGRADE SCENARIOS** - -**Advanced Resiliency use case failure scenarios:** -SMO detects the partial failure related to O-DU#1 based on alarms or service performance degradation based on KPIs - -SMO MAKES A HIGH LEVEL DECISION TO THE OPERATION OF THE SHARED O-RU OPERATIONAL BY INITIATING AN O-DU SWITCH - -**The SMO(non-RT RIC) initiates an O-DU switch to restore the operation of the Shared O-RU** - -**SMO triggers the switch or transition of the O-DU** - -10.1 «O» Lock the O-DU - 10.2 «O» Removes the cell(s) that were served - 10.3 «FH» Removes the [tr]v-array-carrier(s) configurations of related cell(s) - 10.4 «F1» Cell(s) removal - 10.5 «O» SMO (non RT RIC) configures O-DU#2 to take active role and configures cell(s) and corresponding carrier(s)/resources (including NRCG(s) for the cell(s)) - 10.6 «FH» [tr]v-array-carrier(s) configuration - 10.7 «O» SMO (non RT RIC) provides O-CU with information about which cell(s)/NRCG(s) to be activated - 10.8 «F1» Cell(s) (NRCG(s)) ready for activation - 10.9 «F1» Request for cell(s) (NRCG(s)) activation - 10.10 «FH» Activates the [tr]v-array-carrier(s) in O-RU that is associated with specific Cell(s) (NRCG(s)) - 10.11 Activates cell(s) as per O-CU request - 10.12 «F1» Cell(s) activated - -Shared O-RU is operational again, connected, in service (CUS-Plane is up and running) - -SMO collects alarms and performance counters from O-DU#2 - -Active role transition from O-DU#2 to O-DU#1 involves same steps transitioned from O-DU#1 to O-DU#2, except which O-DU to be activated. This activity is based on trigger from SMO and/or operator's decision. - -**END ADVANCED RESILIENCY USE CASE** - -Sequence diagram for Advanced resiliency sub-use case implementation flow for 1 active + 1 standby O-DUs. Lifelines: Personnel Shared O-RU Host (Operations Actor), Service Management and Orchestration Shared O-RU Operator (non RT RIC) (Shared O-RU Resiliency SMO(non-RT RIC)), O-RAN Shared O-RU Operator (O-CU, O-DU (#1), O-RU (Shared), O-DU (#2)). - -Figure 4.20.3.12.1-1: Advanced resiliency sub-use case implementation flow for 1 active + 1 standby O-DUs with various resiliency situations - -#### 4.20.3.13 Load-balancing sub-use cases of a Shared O-RU - -The load-balancing sub-use cases describes the flow of how actors involved execute a policy to load-balance the resources of the O-DUs and Shared O-RU coordinated through a policy enforcer (actor). - -#### 4.20.3.14 Coordinated reset of a Shared O-RU sub-use cases for Multi-MNO - -The coordinated reset of a Shared O-RU sub-use cases describes the flow of how actors coordinate to reset Shared O-RU. - -The context of the coordinated reset of a Shared O-RU sub-use cases is captured in table 4.20.3.14-1. - -**Table 4.20.3.14-1: Coordinated reset of a Shared O-RU sub-use cases** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|---------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Coordinated reset of a Shared O-RU. | | -| Actors and Roles | Host SMO – The connected host SMO to the host O-DU.
Partner SMO – The partner operator SMO. It connects to the SROs.
Host O-DU – Host O-DU connected to the Shared O-RU.
Operator O-DU – The SRO O-DU connected to the Shared O-RU.
Shared O-RU – The target Shared O-RU that will be reset. | | -| Assumptions | None. | | -| Begins when | There are four basic variations of a coordinated reset of a Shared O-RU. These are described in the following steps and diagrams.

(1) Coordinated reset of a Shared O-RU initiated by host personnel
(2) Coordinated reset of a Shared O-RU initiated by SRO personnel
(3) Coordinated reset of a Shared O-RU autonomously initiated by host O-DU
(4) Coordinated reset of a Shared O-RU autonomously initiated by SRO O-DU | | -| Pre-conditions | None. | | -| Coordinated reset of Shared O-RU initiated by host personnel | | | -| Step 1 (M) | Reset request from operator

The request for the coordinated reset of a Shared O-RU is initiated from the host operator and is received by the host operator SMO. | | -| Step 2 (M) | Host SMO informs partner SMOs

The host operator SMO informs associated SMOs that the coordinated reset of a Shared O-RU has been initiated. Associated SMOs are other SMOs which are connected to O-DUs that are connected to the affected Shared O-RU. See NOTE 1, NOTE 2. | | -| Step 3.1 (ALT) | Reset request from host SMO to host O-DU (hierarchal mode) | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | The request for the coordinated reset of the target Shared O-RU is sent from the host operator SMO to the host O-DU over the O1 interface. See NOTE 3. | | -| Step 3.2 (ALT) | Reset request from host O-DU to Shared O-RU (hierarchical mode)

In hierarchical mode, the coordinated reset request of the target Shared O-RU is sent from the host O-DU to the target Shared O-RU through the fronthaul as an RPC request. | | -| Step 3.3 (ALT) | Reset request from host SMO to Shared O-RU (hybrid mode)

In hybrid mode, the coordinated reset request of the target Shared O-RU is sent from the host SMO to target Shared O-RU as an RPC request via the M-plane. See NOTE 4. | | -| Step 4 (M) | Shared O-RU notifies the host O-DU

The affected Shared O-RU notifies the host O-DU (hierarchical mode) or host SMO (hybrid mode). See NOTE 5, NOTE 6, NOTE 7. | | -| Step 5 (M) | Host O-DU notifies the SMO

The host O-DU informs the host SMO with a “ Shared O-RU reset initiated ” notification. | | -| Step 6 (M) | Shared O-RU notifies other connected O-DUs

The target Shared O-RU notifies other connected O-DUs as SROs. This is a notification message originating from the Shared O-RU with no specific ordering. | | -| Step 7 (M) | O-DU notifies associated SMO

The O-DU (SRO) informs its associated SMO with a “ Shared O-RU reset initiated ” notification. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 8 (M) | Shared O-RU notifies other connected O-DUs

The target Shared O-RU notifies other connected O-DUs as SROs. This is a notification message originating from the Shared O-RU with no specific ordering. | | -| Step 9 (M) | O-DU notifies associated SMO

The O-DU (SRO) informs its associated SMO with a “ Shared O-RU reset initiated ” notification. | | -| Step 10 (M) | Shared O-RU notifies connected host O-DU

The target Shared O-RU notifies the host O-DU (hierarchical mode) or host SMO (hybrid mode) with a reset response. This is an RPC reply-acknowledgement. | | -| Step 11 (M) | Host O-DU notifies the SMO

The host O-DU informs the host operator SMO that the Shared O-RU has executed the reset with a “ Shared O-RU Reset Executed ” notification. | | -| Step 12 (M) | Shared O-RU reset & startup

The Shared O-RU resets; and then initiates its start-up sequence. | | -| Coordinated reset of Shared O-RU initiated by SRO personnel | | | -| Step 1 (M) | Reset procedure initiated

The partner operator has identified a need to reset the target Shared O-RU and initiates a reset procedure. | | -| Step 2 (M) | Identify host

The host for the target Shared O-RU is identified. | | -| Step 3 (M) | Reset coordination | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | Coordination between the operators can occur, so that the partner operator can indicate to the host the need for a reset. | | -| Step 4 (M) | Reset request from operator

The reset request from the partner operator is sent to the partner SMO. | | -| Step 5 (M) | Identify host

The partner SMO identifies the proper host SMO for the target Shared O-RU. | | -| Step 6 (M) | Reset request (coordination)

The partner shared operator SMO sends a request to the host SMO to initiate a coordinate reset of the target Shared O-RU. | | -| Step 7 (M) | Reset response (coordination)

The host SMO responds to the partner shared operator SMO regarding the initiation of a coordinate reset of the target Shared O-RU. | | -| Step 8.1 (ALT) | Reset request from host SMO to host O-DU (hierarchical mode)

The request for the coordinated reset of the target Shared O-RU is sent from the host operator SMO to the host O-DU over the O1 interface. See NOTE 8. | | -| Step 8.2 (ALT) | Reset request from host O-DU to SHARED O-RU (hierarchical mode)

In hierarchical mode, the coordinated reset request of the target Shared O-RU is sent from the host O-DU to the target Shared O-RU through the fronthaul as an RPC request. | | -| Step 8.3 (ALT) | Reset request from host SMO to Shared O-RU (hybrid mode) | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | In hybrid mode, the coordinated reset request of the target Shared O-RU is sent from the host SMO to target Shared O-RU as an RPC request via the M-plane. See NOTE 9. | | -| Step 9 (M) | Shared O-RU notifies the host O-DU

The affected Shared O-RU notifies the host O-DU (hierarchical mode) or host SMO (hybrid mode). See NOTE 10, NOTE 11, NOTE 12. | | -| Step 10 (M) | Host O-DU notifies the SMO

The host O-DU informs the host SMO with a “ Shared O-RU reset initiated ” notification. | | -| Step 11 (M) | Shared O-RU notifies other connected O-DUs

The target Shared O-RU notifies other connected O-DUs as SROs. This is a notification message originating from the Shared O-RU with no specific ordering. | | -| Step 12 (M) | O-DU notifies associated SMO

The O-DU (SRO) informs its associated SMO with a “ Shared O-RU reset initiated ” notification. | | -| Step 13 (M) | Shared O-RU notifies other connected O-DUs

The target Shared O-RU notifies other connected O-DUs as SROs. This is a notification message originating from the Shared O-RU with no specific ordering. | | -| Step 14 (M) | O-DU notifies associated SMO

The O-DU (SRO) informs its associated SMO with a “ Shared O-RU reset initiated ” notification. | | -| Step 15 (M) | Shared O-RU notifies connected host O-DU | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | The target Shared O-RU notifies the host O-DU (hierarchical mode) or host SMO (hybrid mode) with a reset response. This is an RPC reply-acknowledgement. | | -| Step 16 (M) | O-DU notifies the SMO

The host O-DU informs the host operator SMO that the Shared O-RU has executed the reset with a “ Shared O-RU Reset Executed ” notification. | | -| Step 17 (M) | Shared O-RU reset & startup

The Shared O-RU resets; and then initiates its start-up sequence. | | -| Coordinated reset of Shared O-RU autonomously initiated by host O-DU | | | -| Step 1 (M) | Reset request from host O-DU to Shared O-RU

The reset request goes from the host O-DU to Shared O-RU through the fronthaul as an RPC request. | | -| Step 2 (M) | Reset notification from host O-DU to SMO

The notification of a coordinated reset for a Shared O-RU goes from host O-DU to the host operator SMO over the O1 interface. | | -| Step 3 (M) | Host SMO informs partner SMOs (coordination)

The host operator SMO informs associated SMOs that the coordinated reset of a Shared O-RU has been initiated. Associated SMOs are other SMOs which are connected to O-DUs that are connected to the affected Shared O-RU | | -| Step 4 (M) | Partner SMOs respond to host SMO (coordination)

The associated SMO responds to the host operator SMO regarding the Shared O-RU reset. | | -| Step 5 (M) | Shared O-RU notifies connected O-DUs | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | The affected Shared O-RU notifies connected O-DUs including the host O-DU, SOH and other connected O-DUs, SROs. This is a notification message originating from the Shared O-RU and sent to all connected O-DUs. | | -| Step 6 (M) | Host O-DU notifies host SMO

The host O-DU notifies the host SMO with a Shared O-RU Reset Initiated message that is triggered from the reset requested by host notification sent from the Shared O-RU. | | -| Step 7 (M) | Shared O-RU notifies connected O-DUs

The affected Shared O-RU notifies connected O-DUs including the host O-DU, SOH and other connected O-DUs, SROs. | | -| Step 8 (M) | O-DU (SRO) notifies the operator SMO

The O-DU (SRO) informs its associated operator SMO that the Shared O-RU has initiated a reset. | | -| Step 9 (M) | Shared O-RU notifies connected O-DUs

The affected Shared O-RU notifies connected O-DUs including the host O-DU, SOH and other connected O-DUs, SROs. | | -| Step 10 (M) | O-DU (SRO) notifies the operator SMO

The O-DU (SRO) informs its associated operator SMO that the Shared O-RU has initiated a reset. | | -| Step 11 (M) | Shared O-RU notifies connected host O-DU

The affected Shared O-RU notifies the host O-DUs with a Reset Response. This is an RPC reply-acknowledgement. | | -| Step 12 (M) | Host O-DU notifies the host SMO with reset executed

The host O-DU informs the host operator SMO that the Shared O-RU has executed the reset with a “ Shared O-RU Reset Executed ” notification. | | -| Step 13 (M) | Shared O-RU reset & startup | | - -| Use Case
Stage | Evolution / Specification | <>
Related use | -|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | The Shared O-RU resets; and then initiates its start-up sequence. | | -| Coordinated reset of Shared O-RU autonomously initiated by SRO O-DU | | | -| Step 1 (M) | Reset request

The SRO O-DU has determined that the target Shared O-RU needs to be reset. The SRO O-DU sends a reset request to its associated SMO. | | -| Step 2 (M) | Reset request (coordination)

The partner shared operator SMO sends a request to the host SMO to initiate a coordinate reset of the target Shared O-RU. | | -| Step 3 (M) | Reset response (coordination)

The host SMO responds to the partner shared operator SMO regarding the initiation of a coordinate reset of the target Shared O-RU. | | -| Step 4.1 (ALT) | Reset request from host SMO to host O-DU (hierarchal mode)

The request for the coordinated reset of the target Shared O-RU is sent from the host operator SMO to the host O-DU over the O1 interface. See NOTE 13. | | -| Step 4.2 (ALT) | Reset request from host O-DU to Shared O-RU (hierarchical mode)

In hierarchical mode, the coordinated reset request of the target Shared O-RU is sent from the host O-DU to the target Shared O-RU through the fronthaul as an RPC request. | | -| Step 4.3 (ALT) | Reset request from host SMO to Shared O-RU (hybrid mode)

In hybrid mode, the coordinated reset request of the target Shared O-RU is sent from the host SMO to target Shared O-RU as an RPC request via the M-plane. See NOTE 14. | | -| Step 5 (M) | Shared O-RU notifies the host O-DU | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | The affected Shared O-RU notifies the host O-DU (hierarchical mode) or host SMO (hybrid mode). See NOTE 15, NOTE 16, NOTE 17. | | -| Step 6 (M) | Host O-DU notifies the SMO

The host O-DU informs the host SMO with a “ Shared O-RU reset initiated ” notification. | | -| Step 7 (M) | Shared O-RU notifies other connected O-DUs

The target Shared O-RU notifies other connected O-DUs as SROs. This is a notification message originating from the Shared O-RU with no specific ordering. | | -| Step 8 (M) | O-DU notifies associated SMO

The O-DU (SRO) informs its associated SMO with a “ Shared O-RU reset initiated ” notification. | | -| Step 9 (M) | Shared O-RU notifies other connected O-DUs

The target Shared O-RU notifies other connected O-DUs as SROs. This is a notification message originating from the Shared O-RU with no specific ordering. | | -| Step 10 (M) | O-DU notifies associated SMO

The O-DU (SRO) informs its associated SMO with a “ Shared O-RU reset initiated ” notification. | | -| Step 11 (M) | Shared O-RU notifies connected host O-DU

The target Shared O-RU notifies the host O-DU (hierarchical mode) or host SMO (hybrid mode) with a reset response. This is an RPC reply-acknowledgement. | | -| Step 12 (M) | O-DU notifies the SMO | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | The host O-DU informs the host operator SMO that the Shared O-RU has executed the reset with a “ Shared O-RU Reset Executed ” notification. | | -| Step 13 (M) | Shared O-RU reset & startup

The Shared O-RU resets; and then initiates its start-up sequence. | | -| Ends when | The target Shared O-RU has been reset. | | -| Exceptions | None identified. | | -| Post Conditions | Success: The target Shared O-RU has been reset.

Failure: The target Shared O-RU fails to be reset. | | - -NOTE 1: There are other use cases exploring operator to operator coordination and in 3GPP specifications as well. These are the exposure of management services (SMO Services). - -NOTE 2: There might be some coordination between SMOs such that the host SMO would not initiate a coordinated reset if the partner SMOs objected, this would be part of the SMO decomposition work. Thus, there might be other transactions happening between the SMOs before step 4. - -NOTE 3: Once the coordinate reset request is issued from the host SMO, the operation will be executed and can no longer be rejected by the system. This implies that any OSS/SMO coordination has finalized before reaching this step. - -NOTE 4: Step 3.3 is specifically for hybrid mode configuration where the SMO could be a host and thus initiate a coordinated reset of a Shared O-RU as an RPC request. - -NOTE 5: These set of notification messages originating from the Shared O-RU and are sent to all connected O-DUs. - -NOTE 6: The notification messages sent to all connected O-DUs in steps 4, 6, and 8 happen in an unspecified order. - -NOTE 7: In both hybrid and hierarchal mode, the Shared O-RU will inform all the connected O-DUs of a reset requested by host notification. - -NOTE 8: Once the coordinate reset request is issued from the host SMO, the operation will be executed and can no longer be rejected by the system. This implies that any OSS/SMO coordination has finalized before reaching this step. - -NOTE 9: Step 8.3 is specifically for hybrid mode configuration where the SMO could be a host and thus initiate a coordinated reset of a Shared O-RU as an RPC request. - -NOTE 10: These set of notification messages originating from the Shared O-RU and are sent to all connected O-DUs. - -NOTE 11: The notification messages sent to all connected O-DUs in steps 9, 11, and 13 happen in an unspecified order. - -NOTE 12: In both hybrid and hierarchal mode, the Shared O-RU will inform all the connected O-DUs of a reset requested by host notification. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|-------------------------| -|

NOTE 13: Once the coordinate reset request is issued from the host SMO, the operation will be executed and can no longer be rejected by the system. This implies that any OSS/SMO coordination has finalized before reaching this step.

NOTE 14: Step 4.3 is specifically for hybrid mode configuration where the SMO could be a host and thus initiate a coordinated reset of a Shared O-RU as an RPC request.

NOTE 15: These set of notification messages originating from the Shared O-RU and are sent to all connected O-DUs.

NOTE 16: The notification messages sent to all connected O-DUs in steps 5, 7, and 9 happen in an unspecified order.

NOTE 17: In both hybrid and hierarchal mode, the Shared O-RU will inform all the connected O-DUs of a reset requested by host notification.

| | | - -``` - -@startuml -!pragma teoz true - -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber 1 - -Box "Personnel\nShared\n O-RU Host" #Lightblue - Actor Operator1 as "Operations\n Actor1" -End box - -Box "Personnel\nShared\n O-RU SRO" #Lightblue - Actor Operator2 as "Operations\n Actor2" -End box - -Box "Service Management\n and Orchestration\nShared O-RU Host" #gold - Participant SMO_a as "Shared O-RU\nrApp" -End box - -Box "Service Management\n and Orchestration\nShared O-RU Operator" #gold - Participant SMO_b as "Shared O-RU\nrApp" -End box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant ODU1 as "O-DU\nSRO#1" - Participant ODU2 as "O-DU\nSRO#2" - -``` - -``` - -Participant Host as "O-DU\nHost" - participant ORU as "O-RU\n(Shared)" -End box - -== COORDINATED RESET OF SHARED O-RU INITIATED BY HOST PERSONNEL == - -Opt Reset requested by host - -Operator1 -> SMO_a: Reset request from operator - -SMO_a -> SMO_b: Reset request\n (coordination) - -Autonumber 3.1 -Alt Reset request in Hierarchical Mode -SMO_a -> Host: <> Reset request to Shared O-DU Host - Host -> ORU: <> Reset Request\n(RPC Reset) -Else Reset request in Hybrid Mode -SMO_a -> ORU: Reset request to Shared O-DU Host (RPC Reset) -end - -Autonumber 4 -Par - ORU --> Host: <> Reset requested\nby Host (Notification) - Host -> SMO_a: <> Shared O-RU Reset initiated - ORU --> ODU2: <> Reset requested\nby Host (Notification) - ODU2 -> SMO_b: <> Shared O-RU Reset initiated - ORU --> ODU1: <> Reset requested by Host (Notification) - ODU1 -> SMO_b: <> Shared O-RU Reset initiated -End - -ORU -> Host: <> Reset Response\n(rpc-reply ACK) -Host -> SMO_a: Shared O-RU Reset executed -ORU -> ORU: Reset &\nStartup\n of Shared\n O-RU - -End - -``` - -== COORDINATED RESET OF SHARED O-RU INITIATED BY HOST PERSONNEL == - -== COORDINATED RESET OF SHARED O-RU INITIATED BY SRO PERSONNEL == - -Autonumber 1 - -Opt Reset triggered by SRO (coordinated by Host) - -Operator2 -> Operator2: Reset procedure\n initiated - -Operator2 -> Operator2: Identify Host - -Operator2 -> Operator1: Reset\ncoordination - -Operator2 -> SMO\_b: Reset request from operator - -SMO\_b -> SMO\_b: Identify Host - -SMO\_b -> SMO\_a: Reset request\n (coordination) - -SMO\_a -> SMO\_b: Reset response\n (coordination) - -Autonumber 8.1 - -Alt Reset request in Hierarchical Mode - -SMO\_a -> Host: <> Reset request to Shared O-DU Host - -Host -> ORU: <> Reset Request\n(RPC Reset) - -Else Reset request in Hybrid Mode - -SMO\_a -> ORU: Reset request to Shared O-DU Host (RPC Reset) - -end - -Autonumber 9 - -Par - -ORU --> Host: <> Reset requested\nby Host (Notification) - -Host -> SMO\_a: <> Shared O-RU Reset initiated - -ORU --> ODU2: <> Reset requested\nby Host (Notification) - -ODU2 -> SMO\_b: <> Shared O-RU Reset initiated - -ORU --> ODU1: <> Reset requested by Host (Notification) - -ODU1 -> SMO\_b: <> Shared O-RU Reset initiated - -End - -ORU -> Host: <> Reset Response\n(rpc-reply ACK) - -``` -Host -> SMO_a: Shared O-RU Reset executed -``` - -``` -ORU -> ORU: Reset &\nStartup\n of Shared\n O-RU -``` - -``` -End -``` - -``` -== COORDINATED RESET OF SHARED O-RU INITIATED BY SRO PERSONNEL == -``` - -``` -@enduml -``` - -The flow diagram of the coordinated reset sub-use case 1 (personnel triggered) is given in figure 4.20.3.14-1. - -![Sequence diagram for coordinated reset sub-use case 1 (personnel triggered).](0603e0bad64a10c96372bbcf8c5d0d14_img.jpg) - -The diagram illustrates the interaction for a coordinated reset of a shared O-RU initiated by host personnel. It features five lifelines: Personnel Shared O-RU Host (Operations Actor1), Personnel Shared O-RU SRO (Operations Actor2), Service Management and Orchestration Shared O-RU Host (Shared O-RU rApp), Service Management and Orchestration Shared O-RU Operator (Shared O-RU rApp), and O-RAN Shared O-RU Operator (O-DU SRO#1, O-DU SRO#2, O-DU Host, O-RU (Shared)). - -**COORDINATED RESET OF SHARED O-RU INITIATED BY HOST PERSONNEL** - -**opt [Reset requested by host]** - -- Reset request from operator (Actor1 to SMO Host) -- Reset request (coordination) (SMO Host to SMO Operator) -- alt [Reset request in Hierarchical Mode]** - - <> Reset request to Shared O-DU Host (SMO Host to O-DU Host) - - <> Reset Request (RPC Reset) (O-DU Host to O-RU (Shared)) -- alt [Reset request in Hybrid Mode]** - - Reset request to Shared O-DU Host (RPC Reset) (SMO Host to O-DU Host) -- par** - - <> Shared O-RU Reset initiated (SMO Host to Actor1) - - <> Reset requested by Host (Notification) (O-DU Host to Actor2) - - <> Shared O-RU Reset initiated (SMO Host to Actor2) - - <> Reset requested by Host (Notification) (O-DU Host to Actor1) - - <> Shared O-RU Reset initiated (SMO Host to Actor1) -- <> Reset Response (rpc-reply ACK) (O-DU Host to SMO Operator) -- Shared O-RU Reset executed (SMO Host to SMO Operator) -- Reset & Startup of Shared O-RU (O-RU (Shared) to O-DU Host) - -**COORDINATED RESET OF SHARED O-RU INITIATED BY HOST PERSONNEL** - -**COORDINATED RESET OF SHARED O-RU INITIATED BY SRO PERSONNEL** - -**opt [Reset triggered by SRO (coordinated by Host)]** - -- Reset procedure initiated (Actor2 to SMO Host) -- Identify Host (SMO Host to Actor2) -- Reset coordination (Actor2 to SMO Operator) -- Reset request from operator (SMO Operator to SMO Host) -- Identify Host (SMO Host to Actor2) -- Reset request (coordination) (SMO Host to SMO Operator) -- Reset response (coordination) (SMO Operator to SMO Host) -- alt [Reset request in Hierarchical Mode]** - - <> Reset request to Shared O-DU Host (SMO Host to O-DU Host) - - <> Reset Request (RPC Reset) (O-DU Host to O-RU (Shared)) -- alt [Reset request in Hybrid Mode]** - - Reset request to Shared O-DU Host (RPC Reset) (SMO Host to O-DU Host) -- par** - - <> Shared O-RU Reset initiated (SMO Host to Actor1) - - <> Reset requested by Host (Notification) (O-DU Host to Actor2) - - <> Shared O-RU Reset initiated (SMO Host to Actor2) - - <> Reset requested by Host (Notification) (O-DU Host to Actor1) - - <> Shared O-RU Reset initiated (SMO Host to Actor1) -- <> Reset Response (rpc-reply ACK) (O-DU Host to SMO Operator) -- Shared O-RU Reset executed (SMO Host to SMO Operator) -- Reset & Startup of Shared O-RU (O-RU (Shared) to O-DU Host) - -**COORDINATED RESET OF SHARED O-RU INITIATED BY SRO PERSONNEL** - -Sequence diagram for coordinated reset sub-use case 1 (personnel triggered). - -Figure 4.20.3.14-1: Coordinated reset sub-use case 1 (personnel triggered) - -``` -@startuml - -!pragma teoz true - -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber 1 - -Box "Personnel\nShared\n O-RU Host" #Lightblue - Actor Operator1 as "Operations\n Actor1" -End box - -Box "Personnel\nShared\n O-RU SRO" #Lightblue - Actor Operator2 as "Operations\n Actor2" -End box - -Box "Service Management\n and Orchestration\nShared O-RU Host" #gold - Participant SMO_a as "Shared O-RU\nrApp" -End box - -Box "Service Management\n and Orchestration\nShared O-RU Operator" #gold - Participant SMO_b as "Shared O-RU\nrApp" -End box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant ODU1 as "O-DU\nSRO#1" - Participant ODU2 as "O-DU\nSRO#2" - Participant Host as "O-DU\nHost" - participant ORU as "O-RU\n(Shared) " -End box - -== COORDINATED RESET OF SHARED O-RU AUTONOMOUSLY INITIATED BY HOST O-DU == - -Autonumber 1 -``` - -Opt Reset triggered by SRO O-DU#1 - -Host -> ORU: <> Reset Request\n(RPC Reset) - -Host -> SMO\_a: Reset initiated - -SMO\_a -> SMO\_b: Reset request\n (coordination) - -SMO\_b -> SMO\_a: Reset response\n (coordination) - -Par - -ORU -> Host: <> Reset requested\nby Host (Notification) - -Host -> SMO\_a: <> Shared O-RU Reset initiated - -ORU -> ODU2: <> Reset requested\nby Host (Notification) - -ODU2 -> SMO\_b: <> Shared O-RU Reset initiated - -ORU -> ODU1: <> Reset requested by Host (Notification) - -ODU1 -> SMO\_b: <> Shared O-RU Reset initiated - -End - -ORU -> Host: <> Reset Response\n(rpc-reply ACK) - -Host -> SMO\_a: Shared O-RU Reset executed - -ORU -> ORU: Reset &\nStartup\n of Shared\n O-RU - -End - -== COORDINATED RESET OF SHARED O-RU AUTONOMOUSLY INITIATED BY HOST O-DU == - -== COORDINATED RESET OF SHARED O-RU AUTONOMOUSLY INITIATED BY SRO O-DU == - -Autonumber 1 - -Opt Reset triggered by SRO O-DU#1 - -ODU1 -> SMO\_b: Reset request\n (coordination) - -SMO\_b -> SMO\_a: Reset request\n (coordination) - -SMO\_a -> SMO\_b: Reset response\n (coordination) - -Autonumber 4.1 - -Alt Reset request in Hierarchical Mode - -``` - -SMO_a -> Host: <> Reset request to Shared O-DU Host - -Host -> ORU: <> Reset Request\n(RPC Reset) - -Else Reset request in Hybrid Mode - -SMO_a -> ORU: Reset request to Shared O-DU Host (RPC Reset) - -End - -Autonumber 5 - -Par - - ORU --> Host: <> Reset requested\nby Host (Notification) - - Host -> SMO_a: <> Shared O-RU Reset initiated - - ORU --> ODU2: <> Reset requested\nby Host (Notification) - - ODU2 -> SMO_b: <> Shared O-RU Reset initiated - - ORU --> ODU1: <> Reset requested by Host (Notification) - - ODU1 -> SMO_b: <> Shared O-RU Reset initiated - -End - -ORU -> Host: <> Reset Response\n(rpc-reply ACK) - -Host -> SMO_a: Shared O-RU Reset executed - -ORU -> ORU: Reset &\nStartup\n of Shared\n O-RU - -End - -== COORDINATED RESET OF SHARED O-RU AUTONOMOUSLY INITIATED BY SRO O-DU == - -@enduml - -``` - -The flow diagram of the coordinated reset sub-use case 2 (autonomous) is given in figure 4.20.3.14-2. - -![Sequence diagram for Coordinated reset sub-use case 2 (autonomous). The diagram shows three lifelines: Personnel Shared O-RU Host (Operations Actor1), Personnel Shared O-RU SRO (Operations Actor2), and O-RAN Shared O-RU Operator (containing Shared O-RU rApp, O-DU SRO#1, O-DU SRO#2, O-DU Host, and O-RU (Shared)). The sequence is divided into three horizontal sections: 1. COORDINATED RESET OF SHARED O-RU AUTONOMOUSLY INITIATED BY HOST O-DU (Reset triggered by SRO O-DU#1). 2. COORDINATED RESET OF SHARED O-RU AUTONOMOUSLY INITIATED BY HOST O-DU (Reset triggered by SRO O-DU#1). 3. COORDINATED RESET OF SHARED O-RU AUTONOMOUSLY INITIATED BY SRO O-DU (Reset triggered by SRO O-DU#1). Each section details the message exchange for reset coordination, including Reset Request (RPC Reset), Reset request (coordination), Reset response (coordination), Shared O-RU Reset initiated, Shared O-RU Reset executed, and Reset & Startup of Shared O-RU.](52b3fa2e98cf5380d8791717d296d9d8_img.jpg) - -The diagram illustrates the message sequence for a coordinated reset. The lifelines are: - - -- Personnel Shared O-RU Host** (Operations Actor1) -- Personnel Shared O-RU SRO** (Operations Actor2) -- O-RAN Shared O-RU Operator** (containing Shared O-RU rApp, O-DU SRO#1, O-DU SRO#2, O-DU Host, and O-RU (Shared)) - - The sequence is divided into three horizontal sections: - - -- COORDINATED RESET OF SHARED O-RU AUTONOMOUSLY INITIATED BY HOST O-DU** (Reset triggered by SRO O-DU#1) - - 1. O-DU SRO#1 sends <> Reset Request (RPC Reset) to O-DU Host. - - 2. O-DU Host sends Reset request (coordination) to Shared O-RU rApp. - - 3. Shared O-RU rApp sends Reset request (coordination) to Shared O-RU rApp. - - 4. Shared O-RU rApp sends Reset response (coordination) to Shared O-RU rApp. - - 5. O-DU Host sends <> Reset requested by Host (Notification) to Shared O-RU (Shared). - - 6. Shared O-RU (Shared) sends <> Shared O-RU Reset initiated to Shared O-RU rApp. - - 7. Shared O-RU (Shared) sends <> Reset requested by Host (Notification) to Shared O-RU rApp. - - 8. Shared O-RU rApp sends <> Shared O-RU Reset initiated to Shared O-RU rApp. - - 9. Shared O-RU (Shared) sends <> Reset requested by Host (Notification) to Shared O-RU rApp. - - 10. Shared O-RU rApp sends <> Shared O-RU Reset initiated to Shared O-RU rApp. - - 11. O-DU Host sends <> Reset Response (rpc-reply ACK) to O-DU SRO#1. - - 12. Shared O-RU rApp sends Shared O-RU Reset executed to Shared O-RU rApp. - - 13. Shared O-RU (Shared) performs Reset & Startup of Shared O-RU. -- COORDINATED RESET OF SHARED O-RU AUTONOMOUSLY INITIATED BY HOST O-DU** (Reset triggered by SRO O-DU#1) - - 1. O-DU SRO#1 sends Reset request (coordination) to Shared O-RU rApp. - - 2. Shared O-RU rApp sends Reset request (coordination) to Shared O-RU rApp. - - 3. Shared O-RU rApp sends Reset response (coordination) to Shared O-RU rApp. - - 4.1. Shared O-RU rApp sends <> Reset request to Shared O-DU Host. - - 4.2. Shared O-DU Host sends <> Reset Request (RPC Reset) to O-DU Host. - - 4.3. Shared O-RU rApp sends Reset request to Shared O-DU Host (RPC Reset) to O-DU Host. - - 5. O-DU Host sends <> Reset requested by Host (Notification) to Shared O-RU (Shared). - - 6. Shared O-RU (Shared) sends <> Shared O-RU Reset initiated to Shared O-RU rApp. - - 7. Shared O-RU (Shared) sends <> Reset requested by Host (Notification) to Shared O-RU rApp. - - 8. Shared O-RU rApp sends <> Shared O-RU Reset initiated to Shared O-RU rApp. - - 9. Shared O-RU (Shared) sends <> Reset requested by Host (Notification) to Shared O-RU rApp. - - 10. Shared O-RU rApp sends <> Shared O-RU Reset initiated to Shared O-RU rApp. - - 11. O-DU Host sends <> Reset Response (rpc-reply ACK) to O-DU SRO#1. - - 12. Shared O-RU rApp sends Shared O-RU Reset executed to Shared O-RU rApp. - - 13. Shared O-RU (Shared) performs Reset & Startup of Shared O-RU. -- COORDINATED RESET OF SHARED O-RU AUTONOMOUSLY INITIATED BY SRO O-DU** (Reset triggered by SRO O-DU#1) - - 1. O-DU SRO#1 sends Reset request (coordination) to Shared O-RU rApp. - - 2. Shared O-RU rApp sends Reset request (coordination) to Shared O-RU rApp. - - 3. Shared O-RU rApp sends Reset response (coordination) to Shared O-RU rApp. - - 4.1. Shared O-RU rApp sends <> Reset request to Shared O-DU Host. - - 4.2. Shared O-DU Host sends <> Reset Request (RPC Reset) to O-DU Host. - - 4.3. Shared O-RU rApp sends Reset request to Shared O-DU Host (RPC Reset) to O-DU Host. - - 5. O-DU Host sends <> Reset requested by Host (Notification) to Shared O-RU (Shared). - - 6. Shared O-RU (Shared) sends <> Shared O-RU Reset initiated to Shared O-RU rApp. - - 7. Shared O-RU (Shared) sends <> Reset requested by Host (Notification) to Shared O-RU rApp. - - 8. Shared O-RU rApp sends <> Shared O-RU Reset initiated to Shared O-RU rApp. - - 9. Shared O-RU (Shared) sends <> Reset requested by Host (Notification) to Shared O-RU rApp. - - 10. Shared O-RU rApp sends <> Shared O-RU Reset initiated to Shared O-RU rApp. - - 11. O-DU Host sends <> Reset Response (rpc-reply ACK) to O-DU SRO#1. - - 12. Shared O-RU rApp sends Shared O-RU Reset executed to Shared O-RU rApp. - - 13. Shared O-RU (Shared) performs Reset & Startup of Shared O-RU. - -Sequence diagram for Coordinated reset sub-use case 2 (autonomous). The diagram shows three lifelines: Personnel Shared O-RU Host (Operations Actor1), Personnel Shared O-RU SRO (Operations Actor2), and O-RAN Shared O-RU Operator (containing Shared O-RU rApp, O-DU SRO#1, O-DU SRO#2, O-DU Host, and O-RU (Shared)). The sequence is divided into three horizontal sections: 1. COORDINATED RESET OF SHARED O-RU AUTONOMOUSLY INITIATED BY HOST O-DU (Reset triggered by SRO O-DU#1). 2. COORDINATED RESET OF SHARED O-RU AUTONOMOUSLY INITIATED BY HOST O-DU (Reset triggered by SRO O-DU#1). 3. COORDINATED RESET OF SHARED O-RU AUTONOMOUSLY INITIATED BY SRO O-DU (Reset triggered by SRO O-DU#1). Each section details the message exchange for reset coordination, including Reset Request (RPC Reset), Reset request (coordination), Reset response (coordination), Shared O-RU Reset initiated, Shared O-RU Reset executed, and Reset & Startup of Shared O-RU. - -Figure 4.20.3.14-2: Coordinated reset sub-use case 2 (autonomous) - -#### 4.20.3.15 Management of Shared O-RU during O-DU software update sub-use case for Shared O-RU for Single & Multi-MNO - -This sub-use case describes the Shared O-RU management scenarios associated with various stages in the O-DU software update such as planning, deployment, and monitoring. The detailed steps for each of these stages are described in the subsequent clauses. - -##### 4.20.3.15.1 Shared O-RU management during O-DU SW change management planning - -The context of the Shared O-RU management during O-DU SW change management planning is captured in table 4.20.3.15.1-1. - -**Table 4.20.3.15.1-1: Shared O-RU management during O-DU SW change management planning** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Management scenarios associated with Shared O-RU during the O-DU SW change management planning. | | -| Actors and Roles |
  • SMO: Maintains up-to-date information about the deployed RAN nodes including inventory, FM and PM data that help to identify appropriate Shared O-RU resources that can be allocated for validating the O-DU SW update.
  • O-DU SW planner: Personnel who prepares deployment strategy of O-DU SW and associated plan based on the Shared O-RU resources that need to be allocated for validation.
  • O-DU SW change management rApp: The rApp that supports SMO and Non-RT RIC in managing the O-DU SW update based on the plan prepared by the planner.
  • Non-RT RIC: Facilitates communication between rApps and SMO services over R1 interface.
| | -| Assumptions |
  • SW updated O-DU shares the O-RU resources with an existing O-DU.
  • SW updated O-DU and existing O-DUs address different set of component carriers and does not have common component carriers among them.
  • SW updated O-DU is considered for single operator Shared O-RU scenario.
| | -| Begins when | O-DU SW planner identifies changes in O-DU software that need to be validated and rolled out on the RAN node deployment with limited service disruption. | | -| Pre-conditions |
  • O-DU SW planner received the O-DU software change specification (for example a document detailing the changes in the O-DU software with information about impact of change and priority).
  • O-DU SW planner collected the information about the RAN nodes from the SMO Topology Exposure & InVENTORY Management (TE&IV) service.
| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| |
  • O-DU SW planner collected the performance indicators and health/fault details of the RAN nodes from the SMO.
  • O-DU SW planner identified the KPIs, PMJobs and scaling parameters of O-DU and Shared O-RU that need to be modified or redefined. This is to ensure that any temporary degradation during the software update does not result in false alarms or unintended actions.
| | -| Step 1 (O) |

O-DU SW planner designs the change management plan for SW update based on the information collected from SMO services.

The plan can include but not limited to

  1. The version of O-DU software to be used for SW update.
  2. The policy to select the target O-DU (e.g., least loaded cell, particular S-NSSAI, random or specific O-DU ID).
  3. Evacuation policies of currently occupied component carriers associated with the Shared O-RU which need to be reallocated based on the O-DU SW update.
  4. The traffic-distribution or component carrier allocation policy between target O-DU and existing O-DU.
  5. Performance and fault indicators with threshold values, monitoring schedule for the updated O-DU.
  6. Mitigation policy in case of a SW update failure or any disruptions.

The availability of plan can be notified to the subscribed SMO services and rApps (for example O-DU SW change management rApp).

See NOTE.

| | -| Step 2 (M) |

The O-DU SW planner initiates SW update of O-DU through the O-DU SW change management rApp with reference to the change management plan prepared and made available to the O-DU SW change management rApp.

| | -| Step 3 (O) |

O-DU SW change management rApp collects the change management plan for O-DU software update.

| | -| Step 4 (O) |

O-DU SW change management rApp validates the change management plan.

| | -| Step 5 (ALT) |

Upon successful validation, the O-DU SW change management rApp prepares the provisioning configurations for the Shared O-RU and O-DU (target and existing), along with the execution steps for the software update, for the designated RAN nodes.

| | -| Step 6 (O) |

O-DU SW change management rApp notifies the O-DU SW planner about the execution steps, target RAN nodes and configuration changes.

| | - -| Use Case Stage | Evolution / Specification | <> | -|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 7 (O) | O-DU SW planner verifies and sends approval to the O-DU SW change management rApp. | | -| Step 8 (O) | Prepares detailed execution plan which can be notified to the subscribed SMO services and rApps. | | -| Step 9 (ALT) | If the validation of the change management plan failed, a notification is sent to the O-DU SW planner with the reason for failure. | | -| Ends when | The change management plan for SW update is ready for execution. The execution can be auto triggered, or it can be manually initiated by the O-DU SW planner. | | -| Exceptions | None. | | -| Post Conditions | None. | | -| NOTE: It is optional to store the change management plan for SW update in SMO TE&IV. The change management plan can be stored in alternate SMO functions registered with and authorized by SMO data management and exposure functions based on the implementation choice. | | | - -``` - -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber - -Box "Personnel" #Lightblue - Actor planner as "O-DU SW planner" -End box - -Box "Service Management and Orchestration\nShared O-RU Operator" #gold - Participant CAN_APP as "O-DU SW Change Management rApp" -end box - -== CHANGE MANAGEMENT PLANNING == - -planner <--> CAN_APP: Prepare change management plan for O-DU SW update - -``` - -``` -planner --> CAN_APP: Request change management for O-DU SW update - -CAN_APP -> CAN_APP : Validate the plan - -Alt If Validation Successful - CAN_APP --> CAN_APP: Identify target RAN Nodes ,\nExecution steps - CAN_APP --> planner: Notify planner about Execution steps - planner --> CAN_APP: Confirm Execution steps - CAN_APP -> CAN_APP: Update Execution steps \n as Approved -Else If Validation Failed - CAN_APP --> planner : Notification of change management\n initiation failure -end - -@enduml -``` - -The O-DU SW update change management planning sequence diagram is given in figure 4.20.3.15.1-1. - -![Sequence diagram for O-DU SW update change management planning. Lifelines: Personnel (O-DU SW planner) and Service Management and Orchestration Shared O-RU Operator (O-DU SW Change Management rApp). The process involves preparing a plan, requesting management, validating, identifying nodes, notifying, confirming, updating steps, and handling failures.](02ca6d9ed0f558acba26f05c300255dc_img.jpg) - -``` - -sequenceDiagram - actor O-DU SW planner as O-DU SW planner - participant Service Management and Orchestration Shared O-RU Operator as Service Management and Orchestration Shared O-RU Operator - Note right of Service Management and Orchestration Shared O-RU Operator: O-DU SW Change Management rApp - - Note over O-DU SW planner, Service Management and Orchestration Shared O-RU Operator: CHANGE MANAGEMENT PLANNING - - O-DU SW planner->>Service Management and Orchestration Shared O-RU Operator: 1 Prepare change management plan for O-DU SW update - Service Management and Orchestration Shared O-RU Operator-->>O-DU SW planner: 2 Request change management for O-DU SW update - Service Management and Orchestration Shared O-RU Operator->>Service Management and Orchestration Shared O-RU Operator: 3 Validate the plan - - alt If Validation Successful - Service Management and Orchestration Shared O-RU Operator->>O-DU SW planner: 4 Identify target RAN Nodes , Execution steps - O-DU SW planner-->>Service Management and Orchestration Shared O-RU Operator: 5 Notify planner about Execution steps - Service Management and Orchestration Shared O-RU Operator-->>O-DU SW planner: 6 Confirm Execution steps - Service Management and Orchestration Shared O-RU Operator->>Service Management and Orchestration Shared O-RU Operator: 7 Update Execution steps as Approved - else If Validation Failed - Service Management and Orchestration Shared O-RU Operator-->>O-DU SW planner: 8 Notification of change management initiation failure - end - - Note right of Service Management and Orchestration Shared O-RU Operator: O-DU SW Change Management rApp - -``` - -Sequence diagram for O-DU SW update change management planning. Lifelines: Personnel (O-DU SW planner) and Service Management and Orchestration Shared O-RU Operator (O-DU SW Change Management rApp). The process involves preparing a plan, requesting management, validating, identifying nodes, notifying, confirming, updating steps, and handling failures. - -Figure 4.20.3.15.1-1: O-DU SW update change management planning sequence diagram - -##### 4.20.3.15.2 Shared O-RU management during O-DU SW update - -The context of the Shared O-RU management during O-DU SW update is captured in table 4.20.3.15.2-1. - -Table 4.20.3.15.2-1: Shared O-RU management during O-DU SW update - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|-----------------------------------------------|-------------------------| -| Goal | Shared O-RU management during O-DU SW update. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Actors and Roles |
  • SMO: Facilitates the execution of O-DU SW update and associated Shared O-RU provisioning by enabling interaction across SMO services, rApps and RAN nodes – These services include but not limited to – TE&IV, OAM functions, O2 related functions.
  • O-RU sharing co-ordinator retrieves change management plan for O-DU SW update and decides on partitioning of carriers between O-DUs.
  • Sharing co-ordinator uses Shared O-RU orchestration rApp to partition resource configuration of a Shared O-RU between O-DUs.
  • O-DU SW change management rApp: The rApp that supports SMO and Non-RT RIC in managing the O-DU SW update based on the plan prepared by the O-DU SW planner.
  • Non-RT RIC: Facilitates communication between rApps and SMO services over R1 interface.
  • O-DU(#n): An active O-DU in the RAN being managed by the SMO.
  • O-DU (updated): O-DU updated with new SW based on the change management plan.
| | -| Assumptions |
  • SW updated O-DU shares the O-RU resources with an existing O-DU.
  • SW updated O-DU and existing O-DUs address different set of component carriers and does not have common component carriers among them.
  • SW updated O-DU and existing O-DUs do not have common cell IDs.
  • SW update for O-DU is considered for single operator Shared O-RU scenario.
| | -| Begins when | O-DU SW change management rApp receives confirmation about the O-DU SW update and Shared O-RU provisioning steps. | | -| Preconditions | O-DU software update and Shared O-RU provisioning steps approved by the O-DU SW planner and made available to the O-DU SW change management rApp. | | -| Step 0 (Ref) |
  • O-DU SW change management rApp, based on the change management plan identifies software version to be updated and recommends (via R1 interface) to SMO the specifics of change like the software version and O-DU identifier.
  • For software update of an existing O-DU, the designated O-DU (updated) is updated using O-RAN.WG6.ORCH-USE-CASES [26], clause 3.2.4 (steps 1 to 4)
| | -| Step 1 (M) |

Initial provisioning of O-DU (updated) as per change management plan– Refer to O-RAN.WG10.OAM-Architecture [27], clause 4.2.1

See NOTE 1.

| | -| Step 2 (M) | O-DU SW change management rApp request (via R1 and SMO/Non-RT RIC) Shared O-RU orchestration rApp to facilitate resource sharing | | - -| Use Case Stage | Evolution / Specification | <> | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| | between O-DU (updated) and existing O-DUs based on the change management plan.

See NOTE 2. | | -| Step 3 (M) | Shared O-RU orchestration r-App initiates configuration of the Shared O-RU common aspects | | -| Step 4-6 (M) | Common aspect provisioning of Shared O-RU as per WG1 Use Cases Detailed Specification, clause 4.20.1.1 which include the include the security, operational, transmission, and connectivity related parameters. | | -| Step 7 (M) | Based on the call home procedure, Shared O-RU establishes management session with O-DU (updated).

See NOTE 3. | | -| Step 8-10 (O) | Notification of configuration update to SMO OAM functions and subsequently to Shared O-RU orchestration rApp.

See NOTE 4. | | -| Step 11-13 (O) | Carrier aspect provisioning to deactivate and evacuate component carriers designated for the O-DU (updated) from the existing O-DU i.e., O-DU (#1). | | -| Step 14-15 (O) | Carrier aspect provisioning to activate component carriers designated for the O-DU (updated). | | -| Step 16-18 (O) | Notification of committed carrier aspect configuration to SMO OAM functions. | | -| Step 19-20 (O) | Notification of configuration aspect to Shared O-RU orchestration rApp. | | -| Step 21 (O) | Notification to sharing coordinator to validate the committed configuration. | | -| Step 22 (O) | Validation of committed configuration by Shared O-RU orchestration rApp. | | -| Step 23 (O) | Validation of committed configuration by O-DU SW change management rApp based on the change management plan. | | -| Step 24 (O) | O-DU SW change management rApp coordinates with OAM functions to provision KPIs, PM jobs or scaling parameters used for assessing the health of the RAN nodes so that any variations anticipated due to O-DU SW update does not lead to false alarms or unintended actions. | | -| Ends when | Committed configuration associated with the Shared O-RU is accepted by sharing coordinator and validation of the configuration is acknowledged by the O-DU SW change management rApp.

SMO TE&IV service is updated with inventory details about the O-DU (updated) and Shared O-RU. | | -| Exceptions | None. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Post Conditions |
  • SW updated O-DU is ready for health & sanity check and is actively handling UE sessions.
| | - -NOTE 1: It is assumed that based on the O-DU (updated) provisioning procedure SMO TE&IV is updated with the inventory information of O-DU (updated) as per change management plan. - -NOTE 2: Refer to the resource partitioning use case described in WG1 Use Cases Detailed Specification, clause 4.20.3.2. - -NOTE 3: After O-DU (updated) deployment, before M-plane connection establishment, there is a possibility of race condition depending on when the Shared O-RU attempts call-home and the readiness of O-DU (updated) to process the call-home requests. There are two potential scenarios and associated approaches for addressing this. - -- Scenario 1: O-DU (updated) is ready for establishing M-plane connection when call home signals are still being sent by Shared O-RU - - In the O-RAN operations yang model (o-ran-operations.yang) there are two parameters that govern the call-home connection attempts – - - re-call-home-no-ssh-timer : A common timer used by the O-RAN equipment to trigger the repeated call-home procedure to all identified call-home servers to which the O-RAN equipment has not already an established NETCONF connection. - - max-call-home-attempts : counter to repeat call-home procedures. In case counter is set with value zero O-RU shall not repeat call-home procedure. - -In order for the deployed O-DU (updated) to be ready to receive and process call-home requests from the shared O-RU, the above parameters shall be optimized, so that adequate time is allocated for the O-DU (updated) to become operational. - -- Scenario 2: O-DU (updated) becomes ready after a long-time duration and Shared O-RU is not performing call home procedure anymore due to expiration of the timers. - - In the O-RAN operations yang model (o-ran-operations.yang) restart-call-home RPC allows any active 'call home O-RU controller' having necessary permissions to instruct O-RU to re-activate call-home procedures. By triggering this request through an existing 'call-home O-RU controller', the O-RU will initiate call home towards all known 'call-home O-RU controllers' that do not currently have an active M-plane session. - -NOTE 4: The steps for hybrid scenario are not shown explicitly, but it is similar to hierarchical scenario. Refer to WG1 Use Cases Detailed Specification, clause 4.20.3.4 for details. - -``` -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber - -Box "Personnel\nShared O-RU Host" #Lightblue -Actor planner as "Sharing Co-ordinator" -``` - -End box - -Box "Service Management and Orchestration\nShared O-RU Operator" #gold - -Participant OAM as "OAM Functions" - -Participant R\_APP as "Shared O-RU\nOrchestration \nrApp" - -Participant CAN\_APP as "O-DU SW\nChange Management \nrApp" - -Participant NRT as "Non-RT\nRIC" - -Participant NFO as "O2 Related \nFunctions" - -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - -Participant ODU1 as "O-DU\n(#1)" - -participant ORU as "O-RU\n(Shared) " - -Participant ODU2 as "O-DU\n(Updated) " - -End box - -== O-DU SW UPDATE == - -Ref over CAN\_APP, NFO - -O-DU Deployment - Refer WG6 Orchestration Use Case - -Clauses 3.2.1, 3.2.4 - -End Ref - -CAN\_APP <--> OAM : <> Initial provisioning of O-DU \n(Updated) as per Change management plan - -Ref over OAM, ODU2 - -Initial provisioning of O-DU (Updated) - Refer WG10 OAM Architecture Clause 4.2.1 - -End Ref - -CAN\_APP <--> R\_APP : <> O-RU sharing request \n(shared O-RU between updated O-DU and \n existing O-DUs)as per the change management \nplan - -Ref over planner,R\_APP - -Resource partitioning as per WG1 Use Case Detailed Spec Clause 4.20.3.2 - -End Ref - -``` - -group Configure common aspects of shared O-RU - R_APP -> OAM : <> Configure Shared O-RU Common aspects - - Alt If Hybrid or Neutral-Host Management - OAM->ORU: <> Configure Shared O-RU common aspects (including O-DU(Updated) IP -Address for Call home) - - Else If Hierarchical Management - OAM->ODU1: <> Configure Shared O-RU common aspects (including O-DU(Updated) IP -Address for Call home) - - ODU1->ORU: <> Configure Shared O-RU\ncommon aspects - - end - - end - - opt Call home to O-DU(Updated)- Loop till NetConf session established - Hnote over OAM,ORU - - Check call-home attempts, re-initiate call-home if max call home attempts expired, adjust -the call home timer with long delay - - End note - - ORU->ODU2: <> Call Home & Network\nmanagement session establishment - - End - - ODU2->OAM: <>Notification of Configuration update (ORU-ID) (WG10 OAM Architecture -Specification Clause 4.2.1) - - OAM->NRT: Configuration Update Notification (ORU-ID) - - NRT->R_APP: <>Configuration Update Notification (ORU-ID) - - Hnote over OAM - - Steps for Hybrid case not shown, but similar to Hierarchical case - - End note - -group Configure carrier aspects of shared O-RU - R_APP -> OAM: <> Configure Shared O-RU Carrier aspects - - OAM -> ODU1: <> Configure O-DU#1 and partitioned carrier information (CC designated -for O-DU(Updated) marked as inactive) - - ODU1->ORU: <> Update \npartitioned carrier information - - OAM -> ODU2: <> Configure O-DU (Updated) and partitioned carrier information -(Designated CC marked as active) - - ODU2->ORU: <> Configure \npartitioned carrier information - -``` - -``` -end - -opt notification of committed configuration -alt Hybrid Management -ORU->OAM: <> Notification of Configuration Update -Else Hierarchical Management -ORU->ODU2: <> Notification of \n Configuration Update -ODU2->OAM: <> Notification of Configuration Update -End - -OAM->NRT: Notification of Configuration Update -NRT->R_APP: <> Configuration Update -planner <--> R_APP: Sharing Co-ordinator confirms compliance to partitioning rules -R_APP <--> OAM : Validates sanity of configuration -CAN_APP <--> OAM : Validates the configuration against change management plan -CAN_APP <--> OAM : Provisioning of KPIs, PM Jobs and Scaling Parameters to avoid false -alarms,unintended actions -End - -@enduml -``` - -The O-DU SW update sequence diagram is given in figure 4.20.3.15.2-1. - -![Sequence diagram for O-DU SW update. Lifelines include Personnel Shared O-RU Host (Sharing Co-ordinator), Service Management and Orchestration Shared O-RU Operator (OAM Functions, Shared O-RU Orchestration rApp, O-DU SW Change Management rApp, Non-RT RIC, O2 Related Functions), and O-RAN Shared O-RU Operator (O-DU #1, O-RU (Shared), O-DU (Updated)). The sequence covers initial provisioning, sharing request, resource partitioning, configuration of common and carrier aspects, and final notification and validation steps.](4c1d8ed1a2c9ff9594c1ca4f179a9c33_img.jpg) - -Sequence diagram for O-DU SW update. Lifelines include Personnel Shared O-RU Host (Sharing Co-ordinator), Service Management and Orchestration Shared O-RU Operator (OAM Functions, Shared O-RU Orchestration rApp, O-DU SW Change Management rApp, Non-RT RIC, O2 Related Functions), and O-RAN Shared O-RU Operator (O-DU #1, O-RU (Shared), O-DU (Updated)). The sequence covers initial provisioning, sharing request, resource partitioning, configuration of common and carrier aspects, and final notification and validation steps. - -Figure 4.20.3.15.2-1: O-DU SW update sequence diagram - -##### 4.20.3.15.3 Shared O-RU management during O-DU SW update monitoring and mitigation - -The context of the Shared O-RU management during O-DU SW update monitoring and mitigation is captured in table 4.20.3.15.3-1. - -Table 4.20.3.15.3-1: Shared O-RU management during O-DU SW update monitoring and mitigation - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|-------------------------------------------------------------------------|-------------------------| -| Goal | Shared O-RU management during O-DU SW update monitoring and mitigation. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Actors and Roles |
  • SMO: Facilitates the monitoring, and mitigation of O-DU SW update and associated Shared O-RU provisioning by enabling interaction across SMO services, rApps and RAN nodes – These services include but not limited to – TE&IV, OAM functions, O2 related functions.
  • O-DU SW planner: Personnel who prepares O-DU SW change management strategy and associated plan based on the identified change in the O-DU software.
  • O-DU SW change management rApp: The rApp that supports SMO and Non-RT RIC in managing the O-DU SW update and associated Shared O-RU provisioning based on the plan prepared by the O-DU SW planner and subsequent health monitoring to decide on mitigation actions.
  • Shared O-RU orchestration rApp is used to rebalance the Shared O-RU resources based on the health monitoring and mitigation action selection by the O-DU SW change management rApp.
  • Non-RT RIC: Facilitates communication between rApps and SMO services over R1 interface.
  • O-DU(#n): An active O-DU in the RAN being managed by the SMO.
  • O-DU (updated): A new O-DU deployed through SW change management procedure.
| | -| Assumptions |
  • Software updated O-DU shares the O-RU resources with an existing O-DU.
  • Software updated O-DU and existing O-DUs address different set of component carriers and does not have common component carriers among them.
  • Software updated O-DU and existing O-DUs do not have common cell IDs.
  • Software update of O-DU is considered for single operator Shared O-RU scenario.
| | -| Begins when |

O-DU SW planner subscribes to the health monitoring events for the updated RAN nodes, based on access granted by SMO external exposure service

OR

As per the predefined plan O-DU SW change management rApp initiates health check of the SW updated O-DU

| | -| Pre-conditions |
  • Successfully completed the SW update of target O-DU
  • Planned Shared O-RU resources allocated to O-DU (updated) and activated
  • O-DU (updated) sharing O-RU resources with an existing O-DU
  • O-DU (updated), existing O-DUs, Shared O-RU are ready for monitoring of KPIs and actively handling the UE sessions
| | - -| Use Case Stage | Evolution / Specification | <> | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 1 (O) | O-DU SW planner subscribes to change management events from O-DU SW change management rApp via SMO/Non-RT RIC. | | -| Step 2 (M) | O-DU SW change management rApp subscribes to PM/FM data from O-DU (updated) and existing O-DU, i.e O-DU (#1) through R1 interface. | | -| Step 3 (M) | Non-RT RIC forwards the subscription request to OAM function. | | -| Step 4 (M) | OAM function subscribes to the FM/PM data updates for O-DU (updated) and existing O-DU, i.e O-DU (#1) via O1 interface. | | -| Step 5 (M) | O-DU (updated) subscribes to FM/PM data updates from Shared O-RU based on the O-DU_ID of O-DU (updated) as the filter criteria. | | -| Step 6 (M) | Notification of FM/PM data from Shared O-RU to O-DU (updated) over OFH. | | -| Step 7 (M) | Notification of FM/PM data from O-DU (updated) to OAM functions over O1. | | -| Step 8 (M) | OAM function forwards notification of FM/PM data received from O-DU (updated) to Non-RT RIC through SMO internal interface. | | -| Step 9 (M) | Non-RT RIC notifies O-DU SW change management rApp about FM/PM data received from O-DU (updated). | | -| Step 10 (M) | O-DU SW change management rApp evaluates FM/PM data against the change management plan. | | -| Step 11 (O) | If the health and sanity of the O-DU (updated) and Shared O-RU are not as per plan, O-DU SW change management rApp analyses mitigation action based on evaluation of the FM/PM data. | | -| Step 12 (O) | If the health and sanity of the O-DU (updated) is not as per plan O-DU SW change management rApp sends change management report consisting of sanity, health details and mitigation action(s) to O-DU SW planner.

See NOTE 1. | | -| Step 13 (O) | O-DU SW planner verifies the mitigation action and sends approval if action is within the scope of the plan. | | -| Step 14 (O) | If mitigation involves provisioning of Shared O-RU, O-DU SW change management rApp recommends to Shared O-RU orchestration rApp re-provisioning of O-RU resources based on recommended action.

See NOTE 2. | | -| Step 15 (O) | Shared O-RU orchestration rApp recommends re-configuration to OAM functions over R1 interface. | | -| Step 16 (O) | Non-RT RIC forwards configuration request to OAM functions. | | -| Step 17 (O) | OAM functions initiates configuration of O-DU (updated) and partitioned carrier information. | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 18 (O) | O-DU (updated) initiates reconfiguration of partitioned carrier information on Shared O-RU. This can include required evacuation procedures if applicable. | | -| Step 19 (O) | OAM functions initiates configuration of O-DU (#n) and partitioned carrier information on the O-RU shared with O-DU (updated). | | -| Step 20 (O) | O-DU (#n) initiates reconfiguration of partitioned carrier information on Shared O-RU. | | -| Step 21 (O) | O-DU (#n) sends notification about configuration update to OAM functions over O1 interface | | -| Step 22 (O) | O-DU (updated) sends notification about configuration update to OAM functions over O1 interface. | | -| Step 23 (O) | O-DU SW change management rApp sends revised report to O-DU SW planner. | | -| Ends when | to O-DU SW planner validates the change management report and certifies the O-DU SW update.

SMO TE&IV service is updated with inventory details about the O-DU (updated) and Shared O-RU. | | -| Exceptions | NA | | -| Post Conditions | SW updated O-DU is functioning as per the change management plan. | | - -NOTE 1: Sanity check and health check are assumed to be implementation specific and depends on the pre-defined change management plan for O-DU SW update. In general, the sanity check assesses whether the SW update satisfies the designated performance and connectivity objectives, while also ensuring compliance with the policies established in accordance with the plan. On the other hand, the health check examines the responsiveness and overall condition of the updated O-DU. - -NOTE 2: The mitigation action depends on the change management plan and specific implementation strategy. This can include but not limited to readjustment of component carriers in Shared O-RU between O-DU (updated) and other O-DUs. - -``` -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber -``` - -``` - -Box "Personnel\nShared O-RU Host" #Lightblue - Actor planner as "O-DU SW Planner" -End box - -Box "Service Management and Orchestration\nShared O-RU Operator" #gold - Participant OAM as "OAM Functions" - Participant R_APP as "Shared O-RU\nOrchestration \nrApp" - Participant CAN_APP as "O-DU \nSW Change Management \nrApp" - Participant NRT as "Non-RT\nRIC" -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant ODU1 as "O-DU\n(#1)" - participant ORU as "O-RU\n(Shared)" - Participant ODU2 as "O-DU\n(Updated)" -End box - -Opt Monitoring of O-DU SW update health -planner <--> CAN_APP: Subscription of O-DU (Updated)& O-DU (#1) Health Updates -CAN_APP -> NRT : <> Subscribe to O-DU(Updated) & O-DU (#1) \nPM/FM Data Updates -NRT -> OAM : Subscribe to O-DU(Updated)& O-DU (#1) PM/FM Data Updates -OAM <--> ODU2 : <> Subscribe to O-DU(Updated) FM/PM Data Updates -ODU2 <--> ORU : <> Subscribe to FM/PM Data Updates \ncorresponding to ODU_ID of O- -DU(Updated) -ORU <--> ODU2: <> Notification of FM/PM data -ODU2 <--> OAM : <> Notification of FM/PM data -OAM <-->NRT: Notification of FM/PM data -NRT ->CAN_APP : <> Notification of FM/PM data -CAN_APP -> CAN_APP : Evaluation of FM/PM data \n against the change management plan -End - -Opt If Mitigation Required based on health evaluation of O-DU (Updated) -CAN_APP -> CAN_APP : Analysis of the mitigation action \nbased on evaluation -CAN_APP <--> planner : Notification of change management report with health and -mitigation action -planner <--> CAN_APP : Approval of the mitigation action - -``` - -``` - -CAN_APP -> R_APP : <> Recommendation for -re-provisioning based on mitigation action - -R_APP <--> NRT : <> Recommendation for re-configuration - -NRT -> OAM : Recommendation for re-configuration - -OAM -> ODU2: <> Configure O-DU (Updated) and partitioned carrier information - -ODU2->ORU: <> Configure partitioned carrier information - -OAM -> ODU1: <> Configure O-DU (Updated) and partitioned carrier information - -ODU1->ORU: <> Configure partitioned carrier information - -ODU1 -> OAM : <> Notification of configuration update - -ODU2 -> OAM : <> Notification of configuration update - -CAN_APP <--> planner : Notification of change management report - -End - -@enduml - -``` - -The O-DU SW update monitoring and mitigation sequence diagram is given in figure 4.20.3.15.3-1. - -![Sequence diagram for O-DU SW update monitoring and mitigation. The diagram shows interactions between Personnel (O-DU SW Planner), SMO (OAM Functions, Shared O-RU Orchestration rApp, O-DU SW Change Management rApp, Non-RT RIC), and O-RAN components (O-DU #1, Shared O-RU, O-DU Updated). It includes two optional blocks: 'Monitoring of O-DU SW update health' and 'If Mitigation Required based on health evaluation of O-DU (Updated)'.](4609bed5ef32a7936e15f90c7abff39e_img.jpg) - -``` - -sequenceDiagram - participant Planner as O-DU SW Planner - box Service Management and Orchestration - participant OAM as OAM Functions - participant R_APP as Shared O-RU Orchestration rApp - participant CM_APP as O-DU SW Change Management rApp - participant NRT as Non-RT RIC - end - box O-RAN - participant ODU1 as O-DU (#1) - participant ORU as O-RU (Shared) - participant ODU2 as O-DU (Updated) - end - - rect rgb(255, 255, 200) - Note over Planner, ODU2: opt [Monitoring of O-DU SW update health] - Planner->>CM_APP: 1 Subscription of O-DU (Updated) & O-DU (#1) Health Updates - CM_APP->>NRT: 2 <> Subscribe to O-DU(Updated) & O-DU (#1) PM/FM Data Updates - NRT->>OAM: 3 Subscribe to O-DU(Updated) & O-DU (#1) PM/FM Data Updates - OAM->>ODU1: 4 <> Subscribe to O-DU(Updated) FM/PM Data Updates - ODU2->>ORU: 5 <> Subscribe to FM/PM Data Updates corresponding to ODU_ID of O-DU(Updated) - ORU->>ODU2: 6 <> Notification of FM/PM data - ODU1->>OAM: 7 <> Notification of FM/PM data - OAM->>NRT: 8 Notification of FM/PM data - NRT->>CM_APP: 9 <> Notification of FM/PM data - CM_APP->>CM_APP: 10 Evaluation of FM/PM data against the change management plan - end - - rect rgb(255, 200, 220) - Note over Planner, ODU2: opt [If Mitigation Required based on health evaluation of O-DU (Updated)] - CM_APP->>CM_APP: 11 Analysis of the mitigation action based on evaluation - CM_APP->>Planner: 12 Notification of change management report with health and mitigation action - Planner->>CM_APP: 13 Approval of the mitigation action - CM_APP->>R_APP: 14 <> Recommendation for re-provisioning based on mitigation action - R_APP->>NRT: 15 <> Recommendation for re-configuration - NRT->>OAM: 16 Recommendation for re-configuration - OAM->>ODU2: 17 <> Configure O-DU (Updated) and partitioned carrier information - ODU2->>ORU: 18 <> Configure partitioned carrier information - OAM->>ODU1: 19 <> Configure O-DU (Updated) and partitioned carrier information - ODU1->>ORU: 20 <> Configure partitioned carrier information - ODU1->>OAM: 21 <> Notification of configuration update - ODU2->>OAM: 22 <> Notification of configuration update - CM_APP->>Planner: 23 Notification of change management report - end - -``` - -Sequence diagram for O-DU SW update monitoring and mitigation. The diagram shows interactions between Personnel (O-DU SW Planner), SMO (OAM Functions, Shared O-RU Orchestration rApp, O-DU SW Change Management rApp, Non-RT RIC), and O-RAN components (O-DU #1, Shared O-RU, O-DU Updated). It includes two optional blocks: 'Monitoring of O-DU SW update health' and 'If Mitigation Required based on health evaluation of O-DU (Updated)'. - -Figure 4.20.3.15.3-1: O-DU SW update monitoring and mitigation sequence diagram - -#### 4.20.3.16 Resource partitioning use case of Shared O-RU for Multi-MNO configuration - -The following describes the solution for the resource partitioning sub-use case for a Shared O-RU in a Multi-MNO configuration. - -The context of the resource partitioning use case of Shared O-RU is captured in table 4.20.3.16-1. - -**Table 4.20.3.16-1: Resource partitioning use case of Shared O-RU** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| -| Goal | rApp has details on how a Shared O-RU's resource are to be partitioned. | | -| Actors and Roles |

Owning operator Service Management & Orchestration (SMO) provides inventory details of Shared O-RU and O-DUs.

Owning operator sharing coordinator recovers inventory and decides on partitioning of carriers between O-DUs.

Owning operator sharing coordinator uses resource partitioning rApp to partition resource configuration of a Shared O-RU between O-DUs.

| | -| Assumptions |

All relevant functions and components are instantiated.

Inventory management systems identify Shared O-RU carrier capabilities and available O-DUs.

| | -| Begins when | Owning operator sharing coordinator decides to share an O-RU between multiple O-DUs. | | -| Pre-conditions | Inventory system is up to date. | | -| Step 1 (M) | Owning operator sharing coordinator recovers O-RU and O-DU inventory and decides on resource partitioning. | | -| Step 2 (M) | Owning operator sharing coordinator resource partitioning rApp to partition shared O-RU between multiple O-DUs. | | -| Step 3 (M) | rApp signals O-DU identity(ies) to owning operator configuration management system. | | -| Step 4 (M) | Owning operator configuration management system configures transport systems with call home identity(ies) for O-DU(s). | O-RAN.WG4.MP [28], clause 6.2.5 | -| Step 5 (M) | Participating operator sharing coordinator recovers O-RU and O-DU inventory and decides on resource partitioning. | | -| Step 6 (M) | Participating operator sharing coordinator resource partitioning rApp to partition Shared O-RU between multiple O-DUs. | | -| Step 7 (M) | rApp signals O-DU identity(ies) to participating operator configuration management system. | | -| Step 8 (M) | Participating operator configuration management system configures transport systems with call home identity(ies) for O-DU(s). | O-RAN.WG4.MP [28], clause 6.2.5 | -| Ends when | Owning operator rApp has details on how shared O-RU's resource are to be partitioned. | | -| Exceptions | None identified. | | -| Post Conditions | None identified. | | - -``` -@startuml - -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber - -Box "Personnel" #Lightblue - Actor planner as "Sharing Co-ordinator" -End box - -Box "Owning Operator\nService Management & Orchestration (SMO)" #gold - Participant INV as "Inventory\nManagement" - Participant CFG as "Configuration\nManagement" - Participant R_APP as "Resource\nPartitioning\nrApp (shared O-RU)" -end box - -Box "Participating Operator\nService Management & Orchestration (SMO)" #gold - Participant INV_PO as "Inventory\nManagement" - Participant CFG_PO as "Configuration\nManagement" - Participant R_APP_PO as "Resource\nPartitioning\nrApp (shared O-RU)" -end box - -Box "External" - Participant TRANS as "DHCP\nServer" -End box - -== RESOURCE PARTITIONING SUB USE CASE == - -planner --> INV: Recover inventory\n and decide on \n resource partitioning -``` - -``` - -planner --> R_APP: Partition shared O-RU between multiple O-DUs -R_APP --> CFG: Set call\n home identity(ies) -CFG-->TRANS: Configure DHCP options for call home - -planner --> INV_PO: Recover inventory\n and decide on \n resource partitioning - -planner --> R_APP_PO: Partition shared O-RU between multiple O-DUs -R_APP_PO --> CFG_PO: Set call\n home identity(ies) - -CFG_PO --> TRANS: Configure DHCP options for call home - -== END RESOURCE PARTITIONING SUB USE CASE == - -@enduml - -``` - -The flow diagram of the resource partitioning use case for Multi-MNO configuration is given in figure 4.20.3.16-1. - -![Sequence diagram for Resource partitioning use case for Multi-MNO. Lifelines: Personnel (Sharing Co-ordinator), Owning Operator SMO (Inventory Management, Configuration Management, Resource Partitioning rApp), Participating Operator SMO (Inventory Management, Configuration Management, Resource Partitioning rApp), External (DHCP Server). The diagram shows two parallel resource partitioning processes. The first process involves the Owning Operator's RApp partitioning O-RUs and configuring DHCP options. The second process involves the Participating Operator's RApp doing the same. The Sharing Co-ordinator initiates both processes by recovering inventory and deciding on resource partitioning.](fa0736695e26abf36c4ab5114e8c9c14_img.jpg) - -``` - -sequenceDiagram - actor Personnel as Sharing Co-ordinator - participant OwningOperatorSMO as Owning Operator Service Management & Orchestration (SMO) - participant ParticipatingOperatorSMO as Participating Operator Service Management & Orchestration (SMO) - participant External as External (DHCP Server) - - Note right of OwningOperatorSMO: RESOURCE PARTITIONING SUB USE CASE - - Note left of OwningOperatorSMO: 1 Recover inventory and decide on resource partitioning - Note left of OwningOperatorSMO: 2 Partition shared O-RU between multiple O-DUs - Note left of OwningOperatorSMO: 3 Set call home identity(ies) - Note left of OwningOperatorSMO: 4 Configure DHCP options for call home - - Note left of ParticipatingOperatorSMO: 5 Recover inventory and decide on resource partitioning - Note left of ParticipatingOperatorSMO: 6 Partition shared O-RU between multiple O-DUs - Note left of ParticipatingOperatorSMO: 7 Set call home identity(ies) - Note left of ParticipatingOperatorSMO: 8 Configure DHCP options for call home - - Note right of OwningOperatorSMO: END RESOURCE PARTITIONING SUB USE CASE - -``` - -Sequence diagram for Resource partitioning use case for Multi-MNO. Lifelines: Personnel (Sharing Co-ordinator), Owning Operator SMO (Inventory Management, Configuration Management, Resource Partitioning rApp), Participating Operator SMO (Inventory Management, Configuration Management, Resource Partitioning rApp), External (DHCP Server). The diagram shows two parallel resource partitioning processes. The first process involves the Owning Operator's RApp partitioning O-RUs and configuring DHCP options. The second process involves the Participating Operator's RApp doing the same. The Sharing Co-ordinator initiates both processes by recovering inventory and deciding on resource partitioning. - -Figure 4.20.3.16-1: Resource partitioning use case for Multi-MNO - -#### 4.20.3.17 Start-up use case of Shared O-RU for Multi-MNO configuration - -The following describes the solution for the start-up sub-use case for a Shared O-RU for Multi-MNO configuration. - -The context of the Shared O-RU start-up use case is captured in table 4.20.3.17-1. - -**Table 4.20.3.17-1: Shared O-RU start-up use case** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The Shared O-RU is operating with the necessary software version and has established network connectivity with the O-DU(s) and, for hybrid deployments, the SMO. | | -| Actors and Roles |

Shared O-RU calls home and establishes network management session.

Owning operator SMO is responsible for software management for the Shared O-RU when operating in hybrid management mode.

O-DU is responsible for software management for the Shared O-RU when operating in hierarchical management mode.

Participating operator SMO handles communication to its connected O-DU.

RAN NF OAM SMO services – provides RAN NF OAM related services for FCAPS and LCM type functions.

| | -| Assumptions | None. | | -| Begins when | Shared O-RU powers on. | | -| Preconditions | Transport systems (DHCP server) has been configured with call home configuration information. | | -| Step 1 (M) |

Establish synchronization:

Each O-DU and Shared O-RU establish synchronisation with a timing source, for example PTP (IEEE 1588) or Sync-E. See NOTE 1, NOTE 2.

| | -| Step 2 (M) |

Synchronization state change notification:

After the O-RU has a synchronisation source, all subscribed O-DU(s) are notified through a synchronisation state change notification. We expect the O-RU to be in the sync state “LOCKED”.

The synchronisation state change notification goes from Shared O-RU to all subscribed O-DU(s).

It is possible that the synchronisation procedure can happen in parallel to the other steps of the start-up sub-use case. Thus, many of the other steps in this use case can happen as the synchronization procedure occurs. Even though this is shown as “step 2” this can complete after other steps.

| | - -| Use Case Stage | Evolution / Specification | <> | -|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------| -| | | Related use | -| | | | -| Step 3 (ALT) | [Shared O-RU operated in hybrid management mode]
Shared O-RU establishes a network management session with owning operator SMO. | O-RAN.WG4.MP [28], clause 6.3 and/or clause 6.9.2 | -| Step 4 | [Shared O-RU operated in hierarchical management mode]
Shared O-RU calls home and triggers establishment of network management session with owning operator O-DU#1. | O-RAN.WG4.MP [28], clause 6.3 | -| Step 5 (ALT) | [Shared O-RU operated in hybrid management mode]
Shared O-RU establishes network management session with participating operator SMO. | O-RAN.WG4.MP [28], clause 8.4 | -| Step 6 | [Shared O-RU operated in hierarchical management mode]
Shared O-RU calls home and triggers establishment of network management session with participating operator O-DU#2. | O-RAN.WG4.MP [28], clause 6.3 | -| Step 7 | [Shared O-RU operated in hybrid management mode]
SMO recovers software inventory request from Shared O-RU. | | -| Step 8 | [Shared O-RU operated in hybrid management mode]
SMO recovers software inventory response from Shared O-RU. | | -| Step 9 (O) | [Shared O-RU operated in hybrid management mode and software update required]
SMO triggers download of new software. | O-RAN.WG4.MP [28], clause 8.5 | -| Step 10 (O) | [Shared O-RU operated in hybrid management mode and software update required]
O-RU downloads software files. | O-RAN.WG4.MP [28], clause 8.5 | -| Step 11 (O) | [Shared O-RU operated in hybrid management mode and software update required]
SMO triggers the installation of the software. | O-RAN.WG4.MP [28], clause 8.6 | -| Step 12 (O) | [Shared O-RU operated in hybrid management mode and software update required]
SMO triggers the activation of the software. | O-RAN.WG4.MP [28], clause 8.7.2 | -| Step 13 (O) | [Shared O-RU operated in hybrid management mode and software update required]
SMO brings active software into operation.

A O-RU reset is required to take the activated software into operation. | O-RAN.WG4.MP [28], clause 8.7.3 | -| Step 14 (ALT) | [Shared O-RU operated in hierarchical management mode]
Owning operator O-DU#1 recovers software inventory request. | O-RAN.WG4.MP [28], clause 8.4 | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| -| | | Related use | -| Step 15 | [Shared O-RU operated in hierarchical management mode]
Owning operator O-DU#1 recovers software inventory response. | O-RAN.WG4.MP [28], clause 8.4 | -| Step 16 (O) | [Shared O-RU operated in hierarchical management mode and software update required]
Owning operator O-DU#1 triggers download of new software. | O-RAN.WG4.MP [28], clause 8.5 | -| Step 17 (O) | [Shared O-RU operated in hierarchical management mode and software update required]
O-RU downloads software files. | O-RAN.WG4.MP [28], clause 8.5 | -| Step 18 (O) | [Shared O-RU operated in hierarchical management mode and software update required]
Owning operator O-DU#1 triggers the installation of the software. | O-RAN.WG4.MP [28], clause 8.6 | -| Step 18 (O) | [Shared O-RU operated in hierarchical management mode and software update required]
Owning operator O-DU#1 triggers activation of the software. | O-RAN.WG4.MP [28], clause 8.7 | -| Step 19 (O) | [Shared O-RU operated in hierarchical management mode and software update required]
Owning operator O-DU#1 brings active software into operation. | O-RAN.WG4.MP [28], clause 8.7 | -| Ends when | The Shared O-RU is operating with the necessary software version and has established network connectivity with the O-DU and, for hybrid deployments, the owning operator SMO. | | -| Exceptions | None identified. | | -| Post Conditions | None identified. | | - -NOTE 1: It is expected the O-RU and all O-DUs connected it would share the same synchronisation source otherwise, the O-DUs will drift in timing. - -NOTE 2: For more details on O-RU sync and O-RU loss of sync, see O-RAN.WG4.MP [28], clause 15.3.3. - -``` - -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 - -Box "Owning Operator\n Service Management and Orchestration (SMO)" #gold - Participant CFG as "Configuration\nManagement" - Participant SWM as "Software\nManagement" - -``` - -``` -Participant FS as "File\nServer" - -end box - -Box "Participating Operator\nSMO" #gold - Participant CFG_PO as "Configuration\nManagement" -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant ODUI as "O-DU\n(#1) " - Participant ODU2 as "O-DU\n(#2) " - - participant ORU as "O-RU\n(Shared)" -End box - -autonumber - -== BEGIN STARTUP FOR MULTI-MNO SUB USE CASE == - -Note over ODUI, ORU - Synchronization Timing is established for O-DUs and Shared O-RU -End Note - -ORU -> ODUI: <> Synchronization state\n change notification -ORU -> ODU2: <> Synchronization\n state change notification - -group Shared O-RU Call Home - -alt Call Home to Owning Operator SMO (Hybrid Management) - ORU<-CFG: <> Network management session establishment - -else Call Home to Owning Operator ODU (Hierarchical Management) - ORU<-ODUI: <> Call Home & Network management\n session establishment -End - -alt Call Home to Participating Operator SMO (Hybrid Management) - ORU<-CFG_PO: <> Network management session establishment -``` - -``` - -Else Call Home to Participating Operator ODU (Hierarchical Management) - -ORU<-ODU2: <> Call Home & Network management\n session establishment - -end - -group Shared O-RU Software Management -alt Hybrid Software Management -SWM-->ORU: Recover software inventory (request) -SWM<-ORU: Recover software inventory (response) -opt software update required - SWM --> ORU: Trigger Software Download - FS-->ORU: Software Download - SWM-->ORU: Install Software - SWM-->ORU: Activate Software - SWM<--ORU: Bring Software into operation -end - -else Hierarchical Software Management -ODU1-->ORU: Recover software inventory (request) -ODU1<-ORU: Recover software inventory (response) -opt software update required - ODU1-->ORU: Trigger Software Download - FS-->ORU: Software Download - ODU1-->ORU: Install Software - ODU1-->ORU: Activate Software - ODU1<--ORU: Bring Software into operation -end - -end - -end - -== END STARTUP FOR MULTI-MNO SUB USE CASE == - -@enduml - -``` - -The flow diagram of the Shared O-RU start-up use case is given in figure 4.20.3.17-1 for Multi-MNO. - -![Sequence diagram for Shared O-RU start-up use case for Multi-MNO. Lifelines include Owning Operator SMO, Participating Operator SMO, and O-RAN Shared O-RU Operator (O-DU #1, O-DU #2, O-RU Shared). The process involves synchronization, call home to SMOs/ODUs, and software management (hybrid or hierarchical).](47aaa88afec21e26eb33420078f4936a_img.jpg) - -The diagram illustrates the interaction for the 'Shared O-RU start-up use case for Multi-MNO'. It begins with a 'BEGIN STARTUP FOR MULTI-MNO SUB USE CASE' message. Synchronization timing is established for O-DUs and the Shared O-RU. The 'Shared O-RU Call Home' section contains an 'alt' block for 'Call Home to Owning Operator SMO (Hybrid Management)' (step 3) and 'Call Home to Owning Operator ODU (Hierarchical Management)' (step 4). Another 'alt' block for 'Call Home to Participating Operator SMO (Hybrid Management)' (step 5) and 'Call Home to Participating Operator ODU (Hierarchical Management)' (step 6) follows. The 'Shared O-RU Software Management' section includes a 'Hybrid Software Management' path (steps 7-13) and a 'Hierarchical Software Management' path (steps 14-20). Both paths include an 'opt' block for 'software update required'. The process concludes with an 'END STARTUP FOR MULTI-MNO SUB USE CASE' message. - -Sequence diagram for Shared O-RU start-up use case for Multi-MNO. Lifelines include Owning Operator SMO, Participating Operator SMO, and O-RAN Shared O-RU Operator (O-DU #1, O-DU #2, O-RU Shared). The process involves synchronization, call home to SMOs/ODUs, and software management (hybrid or hierarchical). - -Figure 4.20.3.17-1: Shared O-RU start-up use case for Multi-MNO - -#### 4.20.3.18 Supervision sub-use case of a Shared O-RU for Multi-MNO configuration - -The following describes the solution for the supervision sub-use case for a Shared O-RU for a Multi-MNO configuration. - -The context of the supervision use case of a Shared O-RU is captured in table 4.20.3.18-1. - -**Table 4.20.3.18-1: Supervision sub-use case of a Shared O-RU** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The Shared O-RU operates watchdog timers with each of its O-DUs and ceases transmitting on a partitioned carrier associated with an O-DU if is watchdog timer to that O-DU expires. | | -| Actors and Roles | Shared O-RU operates watchdog timers and deactivates any carriers associated with an expired watchdog timer.

O-DU repeatedly resets the Shared O-RU's supervision timer.

SMO forwards any alarms to Shared O-RU rApp. | | -| Assumptions | O-DUs are operating fronthaul control and user plane for their respective partitioned carriers.

SMO has subscribed to receive alarm notifications (hybrid management model). | | -| Begins when | An O-DU subscribes to receive supervision notifications. | | -| Step 1 (Loop) | O-DU#1 initiates supervision operations. | | -| Step 2 (Loop) | O-RU response from supervision operations. | | -| Step 3 (O) | O-DU#1 detects that it has lost communication sessions to the Shared O-RU. It raises a communication alarm to the owning operator SMO. | | -| Step 4 (O) | Cease transmission – Shared O-RU detects supervision failure with O-DU#1 and ceases transmitting on partitioned carrier associated with O-DU of the owning operator RAN network. | | -| Step 5 (O) | Shared O-RU sends alarm notification to owning operator fault management in SMO. | | -| Step 6 (O) | Owning operator fault management sends alarm notification to owning operator Non-RT RIC. | | -| Step 7 (O) | Owning operator Non-RT RIC sends alarm notification to owning operator Shared O-RU orchestration rApp. | | -| Step 8 (Loop) | O-DU#2 initiates supervision operations. | | -| Step 9 (Loop) | O-RU response from supervision operations. | | -| Step 10 (O) | O-DU#2 detects that it has lost communication sessions to the Shared O-RU. It raises a communication alarm to the owning operator SMO. | | -| Step 11 (O) | Cease transmission – Shared O-RU detects supervision failure with O-DU#2 and ceases transmitting on partitioned carrier associated with O-DU from the participating operator RAN network. | | -| Step 12 (O) | Shared O-RU sends alarm notification to the participating operator fault management. | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|----------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 13 (O) | Participating operator fault management sends alarm notification to participating operator Non-RT RIC. | | -| Step 14 (O) | Participating operator Non-RT RIC sends alarm notification to participating operator Shared O-RU orchestration rApp. | | -| Ends when | O-DU terminates subscription to supervision notification. | | -| Exceptions | None identified. | | -| Post Conditions | None identified. | | - -``` - -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber 1 - -Box "Owning Operator\nService Management and Orchestration" #gold - Participant FM as "Alarm\nManagement" - Participant R_APP as "Shared O-RU\nOrchestration \nrApp" - Participant SMO_a as "Non-RT\nRIC" -end box - -Box "Participating Operator\nService Management and Orchestration" #gold - Participant FM_PO as "Alarm\nManagement" - Participant R_APP_PO as "Shared O-RU\nOrchestration \nrApp" - Participant SMO_PO as "Non-RT\nRIC" -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant ODU1 as "O-DU\n(#1)" - Participant ODU2 as "O-DU\n(#2)" - -``` - -``` - participant ORU as "O-RU\n(Shared)" - -End box - -== START SUPERVISION SUB USE CASE MULTI-MNO == - -hnote over ODU1, ORU -<> Fronthaul Control & User Plane - for partitioned carrier #1 -end note - -hnote over ODU2, ORU -<> Fronthaul Control & User Plane - for partitioned carrier #2 -end note - -group Per O-DU Supervision - -loop odu #1 supervision -ODU1->ORU: <> Supervision Operation O-DU #1 Req -ODU1<-ORU: <> Supervision Operation O-DU #1 Rsp -end - -opt Supervision failure to odu-id#1 - -ODU1->FM: <> O-DU detects O-RU session lost and sends Alarm notification -ORU->ORU: Cease\n transmitting\n partitioned\n carrier #1 - -opt SMO has subscribed to receive alarm notifications -ORU->FM: (Opt) <> O-DU Supervision Alarm O-DU#1 -FM->SMO_a: Alarm Indication -SMO_a->R_APP: <> Alarm\nIndication -end - -end -``` - -``` -loop odu #2 supervision - -ODU2->ORU: <> Supervision\n Operation O-DU #2 Req -ODU2<-ORU: <> Supervision\n Operation O-DU #2 Rsp -end - -opt Supervision failure to odu-id#2 - -ODU2->FM: <> O-DU detects O-RU session lost and sends Alarm notification - -ORU->ORU: Cease\n transmitting\n partitioned\n carrier #2 - -opt SMO has subscribed to receive alarm notifications - -ORU->FM: (Opt) <> O-DU Supervision Alarm O-DU#2 -FM->SMO_a: Alarm Indication -SMO_a->R_APP: <> Alarm\nIndication -end -end - -end - -== END SUPERVISION SUB USE CASE MULTI-MNO == - -@enduml -``` - -The flow diagram of the Shared O-RU supervision use case is given in figure 4.20.3.18-1 for Multi-MNO. - -![Sequence diagram for Supervision use case of a Shared O-RU in Multi-MNO. Lifelines include Owning Operator SMO, Participating Operator SMO, and O-RAN Shared O-RU Operator (O-DU #1, O-DU #2, O-RU Shared). The process involves starting supervision, looping through each O-DU, handling potential failures, and ending supervision.](c9e3572a1d0a3fd946db179079f95fcb_img.jpg) - -The diagram illustrates the interaction for the 'Supervision use case of a Shared O-RU in Multi-MNO'. It begins with a 'START SUPERVISION SUB USE CASE MULTI-MNO' message from the Participating Operator SMO to the O-RAN Shared O-RU Operator. The O-RAN Shared O-RU Operator responds with two messages: '<> Fronthaul Control & User Plane for partitioned carrier #1' and '<> Fronthaul Control & User Plane for partitioned carrier #2'. The process then enters a 'Per O-DU Supervision' phase. A 'loop [odu #1 supervision]' contains two messages: '1 <> Supervision Operation O-DU #1 Req' and '2 <> Supervision Operation O-DU #1 Rsp'. An 'opt [Supervision failure to odu-id#1]' block contains '3 <> O-DU detects O-RU session lost and sends Alarm notification', which leads to 'Cease transmitting partitioned carrier #1' (4). Another 'opt [SMO has subscribed to receive alarm notifications]' block contains '5 (Opt) <> O-DU Supervision Alarm O-DU#1', '6 Alarm Indication', and '7 <> Alarm Indication'. A similar 'loop [odu #2 supervision]' and 'opt [Supervision failure to odu-id#2]' block follow, with messages 8 through 14. The process concludes with an 'END SUPERVISION SUB USE CASE MULTI-MNO' message. - -Sequence diagram for Supervision use case of a Shared O-RU in Multi-MNO. Lifelines include Owning Operator SMO, Participating Operator SMO, and O-RAN Shared O-RU Operator (O-DU #1, O-DU #2, O-RU Shared). The process involves starting supervision, looping through each O-DU, handling potential failures, and ending supervision. - -Figure 4.20.3.18-1: Supervision use case of a Shared O-RU in Multi-MNO - -#### 4.20.3.19 Antenna Line device (ALD) control sub-use case of a Shared O-RU for Multi-MNO configuration - -The following describes the solution for the ALD control sub-use case for a Shared O-RU for Multi-MNO configuration. - -The context of the antenna line device control use case of a Shared O-RU is captured in table 4.20.3.19-1. - -**Table 4.20.3.19-1: Antenna line device control use case of a Shared O-RU** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| -| Goal | The ALD connected to Shared O-RU is configured to operate with ALD controller. | | -| Actors and Roles | Owning operator rApp is responsible for determining which O-DU is responsible for ALD controller aspects.
O-DU is responsible for implementing ALD controller.
O-RU is responsible for bridging between OFH and HDLC.
ALD is responsible for terminating HDLC. | | -| Assumptions | None. | | -| Begins when | Shared O-RU has started up and has been configured with correct software version. | | -| Pre-conditions | None. | | -| Step 1 (M) | Owning operator rApp determines which O-DU is responsible for performing ALD controller functionality. | | -| Step 2 (M) | Owning operator rApp triggers the configuration of the ALD controller for Shared O-RU. | | -| Step 3 (M) | Owning operator Non-RT RIC triggers the configuration of ALD controller for Shared O-RU. | | -| Step 4 (M) | Owning operator SMO uses O1 interface to configure ALD controller in O-DU. | | -| Step 5 (M) | O-DU uses open fronthaul interface to configure ALD aspects of Shared O-RU. | O-RAN.WG4.MP [28], clause 9 | -| Step 6 (M) | Participating operator rApp triggers the configuration of the ALD controller for Shared O-RU. | | -| Step 7 (M) | Participating operator Non-RT RIC triggers the configuration of ALD controller for Shared O-RU. | | -| Step 8 (M) | O-DU uses open fronthaul interface to signal ALD request. | O-RAN.WG4.MP [28], clause 14.4 | -| Step 9 (M) | O-DU uses open fronthaul interface to signal ALD response. | O-RAN.WG4.MP [28], clause 14.4 | -| Step 10 (M) | Shared O-RU provides interworking between OFH and HDLC request. | O-RAN.WG4.MP [28], clause 14.4 | -| Step 11 (M) | Shared O-RU provides interworking between OFH and HDLC response. | O-RAN.WG4.MP [28], clause 14.4 | -| Ends when | ALD connected to Shared O-RU is configured correctly. | | -| Exceptions | None identified. | | -| Post Conditions | None identified. | | - -``` -@startuml - -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber - -Box "Owning Operator\nService Management and Orchestration" #gold - Participant CFG as "Configuration\nManagement" - Participant R_APP as "Shared O-RU\nOrchestration \nrApp" - Participant SMO_a as "Non-RT\nRIC" -end box - -Box "Participating Operator\nService Management and Orchestration" #gold - Participant CFG_PO as "Configuration\nManagement" - Participant R_APP_PO as "Shared O-RU\nOrchestration \nrApp" - Participant SMO_PO as "Non-RT\nRIC" -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant ODU1 as "O-DU(#1)\nALD Controller" - Participant ODU2 as "O-DU(#2)" - - participant ORU as "O-RU\n(Shared)" - participant ALD as "ALD" -End box - -== START ALD CONTROL SUB USE CASE FOR MULTI-MNO == - -== CONFIGURATION == - -group Configure ALD aspects of shared O-RU -``` - -``` - -Hnote over R_APP -1. Decide on O-DU(#1) -or O-DU(#2) for -ALD Control -end note - -autonumber 2 -R_APP -> SMO_a: <> Configure\nShared O-RU\nALD aspects -SMO_a->CFG: Configure Shared O-RU ALD Aspects - -CFG->ODU1: <> Configure Shared O-RU ALD aspects -&ODU1->ORU: <> Configure Shared O-RU ALD aspects - -R_APP_PO -> SMO_PO: <> Configure\nShared O-RU\nALD aspects -SMO_PO->CFG_PO: Configure Shared O-RU ALD Aspects - -end - -== RUNNING == - -group ALD Operation for shared O-RU - -ODU1->ORU: <> HDLC-over-OFH Req -ODU1<-ORU: <> HDLC-over-OFH Resp -ORU->ALD: HDLC -ORU<-ALD: HDLC - -end - -== END ALD CONTROL SUB USE CASE FOR MULTI-MNO == - -@enduml - -``` - -The flow diagram of the antenna line device sub-use case is given in figure 4.20.3.19-1. - -![Sequence diagram for Antenna line device sub-use case for multi-MNO. Lifelines include Owning Operator Service Management and Orchestration, Participating Operator Service Management and Orchestration, and O-RAN Shared O-RU Operator. The process includes START ALD CONTROL, CONFIGURATION (deciding on O-DU, configuring aspects), RUNNING (ALD Operation), and END ALD CONTROL.](c05d92337f078aa1683a299f3c8b2d51_img.jpg) - -The diagram illustrates the interaction for the Antenna line device sub-use case for multi-MNO. It features three main lifelines: Owning Operator Service Management and Orchestration, Participating Operator Service Management and Orchestration, and O-RAN Shared O-RU Operator. The sequence begins with 'START ALD CONTROL SUB USE CASE FOR MULTI-MNO', followed by 'CONFIGURATION' which includes 'Configure ALD aspects of shared O-RU' (steps 1-7). The 'RUNNING' phase includes 'ALD Operation for shared O-RU' (steps 8-11). The sequence concludes with 'END ALD CONTROL SUB USE CASE FOR MULTI-MNO'. - -Sequence diagram for Antenna line device sub-use case for multi-MNO. Lifelines include Owning Operator Service Management and Orchestration, Participating Operator Service Management and Orchestration, and O-RAN Shared O-RU Operator. The process includes START ALD CONTROL, CONFIGURATION (deciding on O-DU, configuring aspects), RUNNING (ALD Operation), and END ALD CONTROL. - -Figure 4.20.3.19-1: Antenna line device sub-use case for multi-MNO - -#### 4.20.3.20 Antenna calibration use case of a Shared O-RU for Multi-MNO configuration (deferred) - -The following will describe the solution for the antenna calibration sub-use case for a Shared O-RU. - -#### 4.20.3.21 Rehoming use case of a Shared O-RU for Multi-MNO - -The following describes the solution for the rehoming sub-use case for a Shared O-RU in a Multi-MNO configuration. - -The step-by-step details of the rehoming use case of a Shared O-RU is in table 4.20.3.21-1. - -Table 4.20.3.21-1: Rehoming use case of a Shared O-RU in Multi-MNO - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | A Shared O-RU is rehomed and is able to pair with new O-DU or existing (previous) O-DU parents in a Multi-MNO setting. | | -| Actors and Roles | Shared O-RU is the element that is rehomed.
Host O-DU (old) is the original Shared O-RU parent.
SRO O-DU (old) is another original O-DU Shared O-RU is connected to. This is owned by the participating operator.
Host O-DU (new) is the new Shared O-RU parent. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| |

SRO O-DU (new) is another new O-DU Shared O-RU is connected to. This is owned by the participating operator.

SMO can receive results from calibration.

| | -| Assumptions |

The Shared O-RU is in a deployment with the original (old) O-DUs and will be moved to the new ones or stays with the original O-DUs

(Typically) the operator will plan a Shared O-RU move before they actually perform the operations related to the move.

| | -| Begins when |

This use case starts with any of these three situations:

Case #1 starts when the Shared O-RU is physically moved to a new location (however still connected to original O-DUs).

Case #2 starts when the Shared O-RU is physically moved to a new location but is connected to new O-DUs.

Case #3 starts when the Shared O-RU stays in same physical location but is connected to new O-DUs (management-initiated rehoming).

| | -| Case #1 – O-RU is physically moved with same O-DU parents | | | -| Step 1 (M) |

Shared O-RU is disconnected from original O-DUs

The Shared O-RU is physically disconnected (fiber disconnected) from the existing O-DU parents.

Then, the Shared O-RU is physically moved to a new location.

| | -| Step 2 (M) |

Shared O-RU is reconnected to original O-DUs

The Shared O-RU is either physically reconnected (different fiber) or connected at the transport layer (with the original fiber) to reconnected to the original O-DU parents, and the following sub-use cases are triggered as a result:

  • • Shared O-RU startup sub-use case for Multi-MNO configuration
  • • Configuration sub-use case
  • • Resource partitioning sub-use case for Multi-MNO configuration
  • • Coordinated reset sub-use case for Multi-MNO configuration
  • • Supervision sub-use case for Multi-MNO configuration
| | -| CASE #2 – O-RU is physically moved with new O-DU parents | | | -| Step 1 (M) |

Shared O-RU is disconnected from original O-DUs

The Shared O-RU is physically disconnected (fiber disconnected) from the former O-DU parents.

| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | Then, the Shared O-RU is physically moved to a new location. | | -| Step 2 (M) |

Shared O-RU is connected to new O-DUs

The Shared O-RU is either physically reconnected (different fiber) or connected at the transport layer (with the original fiber) to new O-DU parents, and the following sub-use cases are triggered as a result:

  • • Shared O-RU startup sub-use case for Multi-MNO configuration
  • • Configuration sub-use case
  • • Resource partitioning sub-use case for Multi-MNO configuration
  • • Coordinated reset sub-use case for Multi-MNO configuration
  • • Supervision sub-use case for Multi-MNO configuration
| | -| Case #3 – Management initiated rehoming | | | -| Step 1 (M) |

Management initiated rehoming for Shared O-RU

Shared O-RU already has physical front-haul connections in place.

Main operator SMO Initiates rehoming operation with O-DUs connected to the Shared O-RU.

Participating operator SMO initiates rehoming operation with O-DUs connected to the Shared O-RU.

| | -| Step 2 (M) |

Shared O-RU starts up

The Shared O-RU starts up with the new O-DU parents, and the following sub-use cases are triggered as a result:

  • • Shared O-RU startup sub-use case for Multi-MNO configuration
  • • Configuration sub-use case
  • • Resource partitioning sub-use case for Multi-MNO configuration
  • • Coordinated reset sub-use case for Multi-MNO configuration
  • • Supervision sub-use case for Multi-MNO configuration
| | -| Ends when | The Shared O-RU has been moved and connected to the appropriate O-DUs, and is operational again. | | -| Exceptions | None. | | -| Post Conditions | None. | | - -@startuml - -``` -!pragma teoz true - -skin rose - -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber 1 - -Box "Owning Operator\n Service Management\n and Orchestration (SMO)" #gold - Participant CFG as "Configuration\nManagement" - Participant SMO as "Management\nService" -end box - -Box "Participating Operator\n Service Management\n and Orchestration (SMO)" #gold - Participant SMO2 as "Management\nService" -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant ODU1 as "O-DU\n(#1) Host" - Participant ODU2 as "O-DU\n(#2)" - Participant ODU3 as "O-DU\n(#3) Host" - Participant ODU4 as "O-DU\n(#4)" - Participant ORU as "O-RU\n(Shared)" -End box - -== BEGIN CASE #1 PHYSICAL REHOMING OF THE SHARED O-RU SAME O-DUs == - -hnote over ODU1, ORU -The O-RU FH is disconnected -from O-DU #1, O-DU #2 -end note - -ORU -> ORU: O-RU FH is \ndisconnected - -hnote over ORU -``` - -The O-RU is - -physically moved - -to a new location - -end note - -hnote over ODU1, ORU - -The O-RU FH is reconnected - -to O-DU #1, O-DU #2 - -end note - -ORU -> ORU: O-RU FH is \nconnected - -hnote over ODU1, ORU - -The O-RU Starts up with O-DU1 and O-DU2 - -end note - -Ref over CFG, ORU: Shared O-RU Startup Sub Use Case for Multi-MNO Configuration\nConfiguration Sub Use Case\nResource Partitioning Sub Use Case for Multi-MNO Configuration\nReset Sub Use Case for Multi-MNO Configuration\nSupervision for Multi-MNO Configuration Sub Use Case - -== CASE #1 REHOMING PROCEDURE END == - -== CASE #2 PHYSICAL REHOMING OF THE SHARED O-RU TO NEW O-DUs == - -Opt Configuration\npreparation - -Alt Hybrid\nType - -hnote over CFG - -Preparation for - -SMO & O-RU - -end note - -Else Hierarchical Type - -Hnote over CFG - -Preparation - -for O-DU - -End note - -End - -End - -hnote over ODU1, ORU - -The O-RU FH is disconnected - -from O-DU #1, O-DU #2 - -end note - -ORU -> ORU: O-RU FH is \ndisconnected - -hnote over ORU - -The O-RU is physically - -moved to a new location - -end note - -hnote over ODU3, ORU - -The O-RU FH is reconnected - -to O-DU #3, O-DU #4 - -end note - -ORU -> ORU: O-RU FH is \nconnected - -hnote over ODU3, ORU - -The O-RU Starts up with O-DU3 and O-DU4 - -end note - -Ref over SMO, ORU: Shared O-RU Startup Sub Use Case for Multi-MNO Configuration\nConfiguration Sub Use Case\nResource Partitioning Sub Use Case for Multi-MNO Configuration \nCoordinated Reset Sub Use Case for Multi-MNO Configuration \nSupervision for Multi-MNO Configuration Sub Use Case - -== CASE #2 REHOMING PROCEDURE END == - -== BEGIN CASE #3 MANAGEMENT INITIATED REHOMING OF THE SHARED O-RU == - -SMO -> ODU1: Rehoming Operation - -SMO2 -> ODU2: Rehoming Operation - -SMO -> ODU3: Rehoming Operation - -SMO2 -> ODU4: Rehoming Operation - -Ref over SMO, ORU: Shared O-RU Startup Sub Use Case for Multi-MNO Configuration Sub Use Case\n Resource Partitioning Sub Use Case for Multi-MNO Configuration \n Reset Sub Use Case for Multi-MNO Configuration\n Supervision for Multi-MNO Configuration Sub Use Case - -== END MANAGEMENT INITIATED REHOMING OF THE SHARED O-RU == - -@enduml - -The flow diagram of the rehoming use case of a Shared O-RU for Multi-MNO is given in figure 4.20.3.21-1. - -![Sequence diagram showing three cases of rehoming a shared O-RU for Multi-MNO. Case 1: Physical rehoming to same O-DUs. Case 2: Physical rehoming to new O-DUs. Case 3: Management initiated rehoming. Lifelines include Owning Operator SMO, Participating Operator SMO, and O-RAN Shared O-RU Operator (O-DUs and Shared O-RU).](c2ce94f28833f80f049837c2281aa2ba_img.jpg) - -The diagram illustrates the interaction between the Owning Operator Service Management and Orchestration (SMO), Participating Operator Service Management and Orchestration (SMO), and the O-RAN Shared O-RU Operator (consisting of O-DU #1 Host, O-DU #2, O-DU #3 Host, O-DU #4, and O-RU (Shared)). - -**BEGIN CASE #1 PHYSICAL REHOMING OF THE SHARED O-RU SAME O-DUS** - -1. The O-RU FH is disconnected from O-DU #1, O-DU #2. (O-RU to O-DU #1, #2) - -2. The O-RU is physically moved to a new location. - -3. The O-RU FH is reconnected to O-DU #1, O-DU #2. (O-RU to O-DU #1, #2) - -4. The O-RU Starts up with O-DU1 and O-DU2. - -**ref** Shared O-RU Startup Sub Use Case for Multi-MNO Configuration - Configuration Sub Use Case - Resource Partitioning Sub Use Case for Multi-MNO Configuration - Reset Sub Use Case for Multi-MNO Configuration - Supervision for Multi-MNO Configuration Sub Use Case - -**CASE #1 REHOMING PROCEDURE END** - -**CASE #2 PHYSICAL REHOMING OF THE SHARED O-RU TO NEW O-DUS** - -**opt** [Configuration preparation] - -**alt** [Hybrid Type] - -Preparation for SMO & O-RU - -**alt** [Hierarchical Type] - -Preparation for O-DU - -5. The O-RU FH is disconnected from O-DU #1, O-DU #2. (O-RU to O-DU #1, #2) - -6. The O-RU is physically moved to a new location. - -7. The O-RU FH is reconnected to O-DU #3, O-DU #4. (O-RU to O-DU #3, #4) - -8. The O-RU Starts up with O-DU3 and O-DU4. - -**ref** Shared O-RU Startup Sub Use Case for Multi-MNO Configuration - Configuration Sub Use Case - Resource Partitioning Sub Use Case for Multi-MNO Configuration - Coordinated Reset Sub Use Case for Multi-MNO Configuration - Supervision for Multi-MNO Configuration Sub Use Case - -**CASE #2 REHOMING PROCEDURE END** - -**BEGIN CASE #3 MANAGEMENT INITIATED REHOMING OF THE SHARED O-RU** - -5. Rehoming Operation (Owning Operator SMO to Participating Operator SMO) - -6. Rehoming Operation (Participating Operator SMO to O-DU #1 Host) - -7. Rehoming Operation (Participating Operator SMO to O-DU #3 Host) - -8. Rehoming Operation (Participating Operator SMO to O-RU (Shared)) - -**ref** Shared O-RU Startup Sub Use Case for Multi-MNO Configuration - Configuration Sub Use Case - Resource Partitioning Sub Use Case for Multi-MNO Configuration - Reset Sub Use Case for Multi-MNO Configuration - Supervision for Multi-MNO Configuration Sub Use Case - -**END MANAGEMENT INITIATED REHOMING OF THE SHARED O-RU** - -Sequence diagram showing three cases of rehoming a shared O-RU for Multi-MNO. Case 1: Physical rehoming to same O-DUs. Case 2: Physical rehoming to new O-DUs. Case 3: Management initiated rehoming. Lifelines include Owning Operator SMO, Participating Operator SMO, and O-RAN Shared O-RU Operator (O-DUs and Shared O-RU). - -Figure 4.20.3.21-1: Rehoming use case of a Shared O-RU for Multi-MNO - -#### 4.20.3.22 Performance management use case of a Shared O-RU for Multi-MNO - -The following describes the solution for the performance management sub-use case for a Shared O-RU in a Multi-MNO configuration. - -The context of the performance management sub-use case of a Shared O-RU in a Multi-MNO configuration is captured in table 4.20.3.22-1. - -**Table 4.20.3.22-1: Performance management sub-use case of a Shared O-RU in a Multi-MNO** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal |

Each O-DU has established subscriptions to receive performance management notifications regarding operation of the fronthaul between the O-DUs and shared O-RU.

The O-DU and Shared O-RU are able to report performance measurement data towards their consumers in a Multi-MNO configuration.

| | -| Actors and Roles |

Shared O-RU generates performance management notifications on a per partitioned carrier basis

O-DU subscribes to receive performance management notifications from Shared O-RU.

| | -| Assumptions |

O-DU has configured performance management metrics for respective partitioned carrier.

| | -| Begins when |

Fronthaul control and user plane is operational between O-DU and Shared O-RU.

| | -| Step 1 (M) |

O-DU#1 subscribes to receive PM notifications from Shared O-RU.

| | -| Step 2 (M) |

O-DU#2 subscribes to receive PM notifications from Shared O-RU.

| | -| Step 3 (loop) |

Shared O-RU sends PM notification to O-DU#1.

| | -| Step 4 (loop) |

Shared O-RU sends PM notification to O-DU#2.

| | -| O-DU to SMO performance operations | | | -| Step 1 (O) |

PM event notification reporting

The O-DU (producer) sends performance data to the SMO (consumer) through an event notification.

| | -| Step 2 (O) |

Streaming PM reports

The O-DU establishes a persistent connection to the SMO and sends performance data.

| | -| Step 3 (O) |

Attribute-based or URI-based collection

| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | Performance data is read by the consumer (SMO) through configuration management attribute. Alternatively, the O-DU can support a data scraping method where a collector (SMO) reads the data from a pre-defined URI. | | -| Step 4 (O) | Producer or PM file upload (file upload)

O-DU uploads a PM file to the SMO.

See NOTE 1. | | -| Step 5 (O) | Consumer downloads PM file (file download)

O-DU issues file ready notification to SMO about the data being ready for download, or SMO periodically polls the O-DU. Afterwards, the SMO (consumer) can download the PM file. | | -| O-RU to O-DU performance operations (in hierarchical configuration) | | | -| Step 1 (O) | PM event notification reporting

The O-RU sends performance data to the O-DU through an event notification. The notification is sent to a subscriber of performance data. | | -| Step 2 (O) | O-DU requests for O-RU to start sending PM data

O-DU invokes an RPC to give PM credentials, target URI, and periodicity notification interval to the Shared O-RU. This includes all the necessary information for the O-RU to perform a file transfer to an endpoint.

See NOTE 2. | | -| Step 3 (O) | Shared O-RU uploads PM file

The Shared O-RU periodically uploads a performance to the target URI using the PM credentials given by the O-DU. | | -| O-RU to SMO performance operations (in hybrid configuration) | | | -| Step 1 (O) | PM event notification reporting

The O-RU sends performance data to the SMO through an event notification via M-plane. The notification is sent to a subscriber of performance data. | | -| Step 2 (O) | SMO requests for O-RU to start sending PM data | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | SMO invokes an RPC to give PM credentials, target URI, and periodicity notification interval to the Shared O-RU. This includes all the necessary information for the O-RU to perform a file transfer to a endpoint. | | -| Step 3 (O) | Shared O-RU uploads PM file

The Shared O-RU uploads performance file to target URI using PM credentials given by the SMO. | | -| Ends when | (1) Subscription setup: O-DU terminates subscription to performance management notification.

(2) O-DU to SMO sending PM data: Use case ends with the producer (O-DU) sending performance data to the consumer (SMO).

(3) O-RU sending performance data: Use case ends with the producer (O-RU) starting to send performance data to the subscriber. | | -| Exceptions | None identified. | | -| Post Conditions | The consumer has received performance data and may perform post processing operations on the data. | | - -NOTE 1: When the O-DU sends performance files received from a Shared O-RU, they are converted to the proper 3GPP format before sending to SMO. See O-RAN WG5.O-DU-O1 [25]. - -NOTE 2: The O-DU establishes a framework for the Shared O-RU to send PM files. This operation is performed only once, thereafter, the Shared O-RU sends the PM files periodically. - -``` - -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber 1 - -Box "Owning Operator\n Service Management and Orchestration (SMO)" #gold - Participant PMS as "Performance Management\nService" -end box - -Box "Participating Operator\n Service Management and Orchestration (SMO)" #gold - Participant PMS2 as "Performance Management\nService" -end box - -``` - -``` -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant ODU1 as "O-DU\n(#1)" - Participant ODU2 as "O-DU\n(#2)" - - participant ORU as "O-RU\n(Shared)" -End box - -== SUBSCRIPTION SETUP == - -hnote over ODU1, ORU -<> Fronthaul Control & User Plane for partitioned carrier #1 -end note - -hnote over ODU2, ORU -<> Fronthaul Control & User Plane for partitioned carrier #2 -end note - -group Per O-DU Performance Management - -ODU1<->ORU: <> Subscribe to receive PM notifications for partitioned carrier #1 -ODU2<->ORU: <> Subscribe to receive PM notifications for partitioned carrier #2 - -loop Shared O-RU performance management -ORU->ODU1: <> PM Notification (partitioned carrier #1) -ORU->ODU2: <> PM Notification (partitioned carrier #2) -end -end - -== SUBSCRIPTION SETUP == - -== ODU TO SMO PERFORMANCE OPERATIONS == - -Autonumber 1 - -Alt O-DU Notification-based Reporting -``` - -``` -ODU1->PMS: <> PM Event Notification Reporting - -Else O-DU Streaming-based Reporting -ODU1->PMS: <> Streaming PM Reports - -Else Consumer Actively Collects -PMS->ODU1: <> Attribute based or URI based collection - -Else O-DU File-based Reporting -ODU1->PMS: <> Producer PM File Upload (File Upload) - -Else O-DU File-based Reporting -PMS->ODU1: <> Consumer Downloads PM File (File Download) - -End - -Alt O-DU Notification-based Reporting -ODU2->PMS2: <> PM Event Notification Reporting - -Else O-DU Streaming-based Reporting -ODU2->PMS2: <> Streaming PM Reports - -Else Consumer Actively Collects -PMS2->ODU2: <> Attribute based or URI based collection - -Else O-DU File-based Reporting -ODU2->PMS2: <> Producer PM File Upload (File Upload) - -Else O-DU File-based Reporting -PMS2->ODU2: <> Consumer Downloads PM File (File Download) - -End - -== ODU TO SMO PERFORMANCE OPERATIONS == - -== ORU TO ODU PERFORMANCE OPERATIONS (Hierarchical Configuration) == - -Autonumber 1 - -Opt O-RU Notification-based Reporting -ORU->ODU1: <> PM Event Notification Reporting - -End - -Autonumber 1 - -Group O-DU Actively Collects PM -``` - -``` -ODU1->ORU: <> ODU invokes RPC to give PM Credentials & Target URI -ORU->ODU1: <> ORU uploads Performance File to Target URI using PM Credentials -End - -Opt O-RU Notification-based Reporting -ORU->ODU2: <> PM Event Notification Reporting -End - -Autonumber 1 - -Group O-DU Actively Collects PM -ODU2->ORU: <> ODU invokes RPC to give PM Credentials & Target URI -ORU->ODU2: <> ORU uploads Performance File to Target URI using PM Credentials -End - -== ORU TO ODU PERFORMANCE OPERATIONS (Hierarchical Configuration) == - -== ORU TO ODU PERFORMANCE OPERATIONS (Hybrid Configuration) == - -Autonumber 1 - -Opt O-RU Notification-based Reporting -ORU->PMS: <> PM Event Notification Reporting -End - -Autonumber 1 - -Group SMO Actively Collects PM -PMS->ORU: <> SMO invokes RPC to give PM Credentials & Target URI -ORU->PMS: <> ORU uploads Performance File to Target URI using PM Credentials -End - -Autonumber 1 - -Opt O-RU Notification-based Reporting -ORU->PMS2: <> PM Event Notification Reporting -``` - -``` -End -``` - -``` -Autonumber 1 -``` - -``` -Group SMO Actively Collects PM -``` - -``` -PMS2->ORU: <> SMO invokes RPC to give PM Credentials & Target URI -``` - -``` -ORU->PMS2: <> ORU uploads Performance File to Target URI using PM Credentials -``` - -``` -End -``` - -``` -== ORU TO ODU PERFORMANCE OPERATIONS (Hybrid Configuration) == -``` - -``` -@enduml -``` - -The flow diagram of the performance management sub-use case of a Shared O-RU in a Multi-MNO is given in figure 4.20.3.22-1. - -![Sequence diagram showing performance management use case for a Shared O-RU for Multi-MNO. Lifelines: Owning Operator SMO, Participating Operator SMO, O-RAN Shared O-RU Operator (O-DU #1, O-DU #2, O-RU Shared).](372a0b094d72de45d94c6c8d52714e9a_img.jpg) - -The diagram illustrates the interaction for performance management in a Shared O-RU environment. It is divided into several sections: - -- SUBSCRIPTION SETUP:** - - Fronthaul Control & User Plane for partitioned carrier #1 and #2 are established between the O-RU and the O-DUs. - - Per O-DU Performance Management:** - - O-DU #1 and O-DU #2 both subscribe to receive PM notifications for their respective partitioned carriers. - - A **loop [Shared O-RU performance management]** involves PM notifications being sent from the O-RU to each O-DU. -- ODU TO SMO PERFORMANCE OPERATIONS:** - - This section uses **alt** blocks to show different reporting methods from O-DU to SMO: - - [O-DU Notification-based Reporting]:** PM Event Notification Reporting. - - [O-DU Streaming-based Reporting]:** Streaming PM Reports. - - [Consumer Actively Collects]:** Attribute based or URI based collection. - - [O-DU File-based Reporting]:** Producer PM File Upload (File Upload) and Consumer Downloads PM File (File Download). - - This pattern is shown for both the Owning Operator's SMO and the Participating Operator's SMO. -- ORU TO ODU PERFORMANCE OPERATIONS (Hierarchical Configuration):** - - From the O-RU to O-DU #1: - - [O-RU Notification-based Reporting]:** PM Event Notification Reporting. - - O-DU Actively Collects PM:** ODU invokes RPC to give PM Credentials & Target URI, and O-RU uploads Performance File to Target URI using PM Credentials. - - From the O-RU to O-DU #2: - - [O-RU Notification-based Reporting]:** PM Event Notification Reporting. - - O-DU Actively Collects PM:** ODU invokes RPC to give PM Credentials & Target URI, and O-RU uploads Performance File to Target URI using PM Credentials. -- ORU TO ODU PERFORMANCE OPERATIONS (Hybrid Configuration):** - - From the O-RU to the Owning Operator's SMO: - - [O-RU Notification-based Reporting]:** PM Event Notification Reporting. - - SMO Actively Collects PM:** SMO invokes RPC to give PM Credentials & Target URI, and O-RU uploads Performance File to Target URI using PM Credentials. - - From the O-RU to the Participating Operator's SMO: - - [O-RU Notification-based Reporting]:** PM Event Notification Reporting. - - SMO Actively Collects PM:** SMO invokes RPC to give PM Credentials & Target URI, and O-RU uploads Performance File to Target URI using PM Credentials. - -Sequence diagram showing performance management use case for a Shared O-RU for Multi-MNO. Lifelines: Owning Operator SMO, Participating Operator SMO, O-RAN Shared O-RU Operator (O-DU #1, O-DU #2, O-RU Shared). - -Figure 4.20.3.22-1: Performance management use case of a Shared O-RU for Multi-MNO - -#### 4.20.3.23 Antenna calibration use case of a Shared O-RU for Multi-MNO - -The following describes the solution for the antenna calibration sub-use case for a Shared O-RU in a Multi-MNO configuration. - -The step-by-step details of the antenna calibration use case of a Shared O-RU are captured in table 4.20.3.23-1. - -**Table 4.20.3.23-1: Antenna calibration of a Shared O-RU in Multi-MNO** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal |

The host O-DU performs an antenna calibration procedure with the shared O-RU in a Multi-MNO configuration.

The owning operator O-DU reports antenna calibration results to the SMO.

| | -| Actors and Roles |

Shared O-RU performs the antenna calibration procedure.

Owning operator O-DU (host) that requests for antenna calibration procedure with Shared O-RU.

Participating operator O-DU is owned by the participating operator.

Owning operator SMO can receive results from calibration.

Participating operator SMO can also receive results from calibration.

| | -| Assumptions |

All O-DUs have connectivity to O-RU.

All actors are operational and have initialized.

Fronthaul control and user plane is operational between all O-DUs and Shared O-RU.

| | -| Begins when |
  1. The Shared O-RU has detected that antenna calibration is required.
  2. The Owning operator O-DU initiates an antenna calibration procedure.
| | -| Step 1.1 (O) |

Recalibration required (O-RU initiated)

The Shared O-RU has detected that antenna calibration is needed and sends an antenna calibration needed notification to the owning operator host O-DU over the open FH. In this case, the O-RU initiates the calibration procedure.

| | -| Step 1.2 (O) |

Calibration request

The host O-DU of the owning operator requests for antenna calibration procedure to start for Shared O-RU.

| | -| Step 1.1 (M) |

Host O-DU informs SMO

The owning operator SMO together with host O-DU (owning operator) informs that an antenna calibration operation is needed.

| | - -| Use Case Stage | Evolution / Specification | <> | -|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 1.2 (M) | SMO to SMO negotiation

Through exposure of management services, the owning operator SMO negotiates with the participating operator SMO that the host O-DU would like to perform an antenna calibration operation. Here, the participating operator SMO may object to the antenna calibration operation. | | -| Step 1.3 (O) | Host O-DU initiates antenna calibration

If agreed to proceed, owning operator SMO together with host O-DU (owning operator) initiates an antenna calibration operation. | | -| Step 1.4 (M) | SMO informs participating operator O-DU

The participating operator SMO informs its O-DU that the antenna calibration operation will be initiated by the owning operator (host) O-DU. | | -| Step 1.5 (M) | Calibration request (O-DU initiated)

The host O-DU of the owning operator requests for antenna calibration procedure to start for Shared O-RU. In this case the O-DU initiates the calibration procedure. | | -| Step 2 (M) | Calibration operation at O-RU

Shared O-RU performs antenna calibration procedure. | | -| Step 3 (M) | Calibration response

The Shared O-RU responds with antenna calibration results to the owning operator O-DU. | | -| Step 4 (M) | Calibration results

The owning operator O-DU returns antenna calibration results to owning operator SMO. | | -| Step 5 (M) | Calibration results to O-DU #2

Shared O-RU notifies the participating operator O-DU with antenna calibration results. | | -| Step 6 (M) | Calibration results | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| | The participating operator O-DU returns antenna calibration results to the participating operator SMO. | | -| Ends when | (1) Antenna calibrated: Antenna calibration procedure has finished, and results reported. | | -| Exceptions | The O-RU may indicate a calibration failure, which is reported to the owning operator O-DU. The O-DU logs the failure and notifies north-bound entities. | | -| Post Conditions | None. | | - -``` - -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -autonumber 1 - -Box "Owning Operator\n Service Management\n and Orchestration (SMO)" #gold - Participant SMO as "Antenna Calibration\nService" -end box - -Box "Participating Operator\n Service Management\n and Orchestration (SMO)" #gold - Participant SMO2 as "Management\nService" -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant ODU1 as "O-DU\n(#1) Host" - Participant ODU2 as "O-DU\n(#2)" - participant ORU as "O-RU\n(Shared)" -End box - -== ANTENNA CALIBRATION PROCEDURE BEGIN (Hybrid) == - -hnote over ODU1, ORU - -``` - -``` -<> Fronthaul Control & User Plane for partitioned carrier #1 -``` - -``` -end note -``` - -``` -hnote over ODU2, ORU -``` - -``` -<> Fronthaul Control & User Plane for partitioned carrier #2 -``` - -``` -end note -``` - -``` -alt ORU Initiated Calibration -``` - -``` -Autonumber 1.1 -``` - -``` -ORU->ODU1: <> Recalibration Needed Notification -``` - -``` -ODU1->ORU: <> Request Antenna Calibration Procedure -``` - -``` -Else ODU Initiated Calibration -``` - -``` -Autonumber 1.1 -``` - -``` -ODU1<->SMO: <> Antenna Calibration Required -``` - -``` -SMO<->SMO2: Antenna Calibration Required -``` - -``` -ODU1<->SMO: <> Antenna Calibration Required -``` - -``` -SMO2->ODU2: <> Antenna Calibration Initiated -``` - -``` -ODU1->ORU: <> Request Antenna Calibration Procedure -``` - -``` -End -``` - -``` -Autonumber 2 -``` - -``` -ORU->ORU: Perform\nAntenna\nCalibration\nProcedure -``` - -``` -ORU->ODU1: <> Respond Antenna Calibration Procedure Results -``` - -``` -ODU1->SMO: <> Respond Antenna\nCalibration Procedure Results -``` - -``` -ORU->ODU2: <> Antenna Calibration Procedure Results -``` - -``` -ODU2->SMO2: <> Antenna Calibration Procedure Results -``` - -``` -== ANTENNA CALIBRATION PROCEDURE END (Hybrid) == -``` - -``` -@enduml -``` - -The flow diagram of the antenna calibration use case of a Shared O-RU for Multi-MNO is given in figure 4.20.3.23-1. - -![Sequence diagram for antenna calibration use case of a Shared O-RU for Multi-MNO. Lifelines include: Owning Operator Service Management and Orchestration (SMO) with Antenna Calibration Service; Participating Operator Service Management and Orchestration (SMO) with Management Service; O-RAN Shared O-RU Operator with O-DU (#1) Host, O-DU (#2), and O-RU (Shared). The process starts with 'ANTENNA CALIBRATION PROCEDURE BEGIN (Hybrid)' and ends with 'ANTENNA CALIBRATION PROCEDURE END (Hybrid)'. It includes messages for recalibration notifications, requests, and results between the O-DUs and the O-RU, and between the O-DUs and the SMOs. An 'alt [ORU Initiated Calibration]' block contains steps 1.1 to 1.4, and an 'alt [ODU Initiated Calibration]' block contains steps 1.1 to 1.5. Step 2 is 'Perform Antenna Calibration Procedure'.](12b3831f83d090aaff6aecb06354f250_img.jpg) - -Sequence diagram for antenna calibration use case of a Shared O-RU for Multi-MNO. Lifelines include: Owning Operator Service Management and Orchestration (SMO) with Antenna Calibration Service; Participating Operator Service Management and Orchestration (SMO) with Management Service; O-RAN Shared O-RU Operator with O-DU (#1) Host, O-DU (#2), and O-RU (Shared). The process starts with 'ANTENNA CALIBRATION PROCEDURE BEGIN (Hybrid)' and ends with 'ANTENNA CALIBRATION PROCEDURE END (Hybrid)'. It includes messages for recalibration notifications, requests, and results between the O-DUs and the O-RU, and between the O-DUs and the SMOs. An 'alt [ORU Initiated Calibration]' block contains steps 1.1 to 1.4, and an 'alt [ODU Initiated Calibration]' block contains steps 1.1 to 1.5. Step 2 is 'Perform Antenna Calibration Procedure'. - -Figure 4.20.3.23-1: Antenna calibration use case of a Shared O-RU for Multi-MNO - -#### 4.20.3.24 Dynamic resource shifting use case of a Shared O-RU - -The following will describe the solution for dynamic resource shifting sub-use case for a Shared O-RU. - -Table 4.20.3.24-1: Dynamic resource shifting use case of a Shared O-RU - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Cooperating O-DUs serve cells overlapping spectrum in a way, so that frequency resources effectively used by each O-DU can be dynamically shifted between O-DUs and interference is avoided at air interface. There is no impact to regular procedures performed between O-DUs and UEs and UE energy consumption is not increased. | | -| Actors and Roles | Shared O-RU serves radio functions to the air.
O-DU performs radio resource handling. | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| | SMO configures other actors.
Near-RT RIC coordinates dynamic shifting of spectrum resources between O-DUs. | | -| Assumptions | O-RU is configured to serve for 2 or more O-DUs.
O-DUs are configured respectively – including dedicated set of bandwidth parts in UL and DL alike.
Near-RT RIC knows how bandwidth parts are configured to O-DUs.
Near-RT RIC is receiving traffic-related statistics from O-DUs.
Near-RT RIC is provided with traffic shaping policy for cells that use overlapping spectrum. | | -| Begins when | Near-RT RIC decides to change bandwidth effectively used by cells served by O-DUs. | | -| Step 1 (M) | Near-RT RIC provides O-DUs with updated lists of bandwidth parts O-DUs are allowed to utilize. | | -| Step 2 (M) | O-DUs respectively confirm reception of updated list of permitted bandwidth parts to Near-RT RIC. | | -| Step 3 (loop) | O-DUs use actual list of permitted bandwidth parts for scheduling in downlink and uplink respectively. | | -| Ends when | Update of list of permitted bandwidth parts confirmed to Near-RT RIC. | | -| Exceptions | It is feasible that list of permitted bandwidth parts is updated to some (not all) of cooperating O-DUs. | | -| Post Conditions | Lists of permitted bandwidth parts are successfully updated for desired O-DUs. | | - -``` - -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 - -Box "SMO" #gold - Participant RAPP as "rApp" -end box - -Box "Near Real Time RIC" #gold - Participant XAPP as "xApp" - -``` - -``` -end box -``` - -``` -Box "O-RAN\nShared O-RU Operator" #lightpink -``` - -``` - Participant ODU1 as "O-DU\n(#1)" -``` - -``` - Participant ODU2 as "O-DU\n(#2)" -``` - -``` - participant ORU as "O-RU\n(Shared)" -``` - -``` -End box -``` - -``` -== INITIATION == -``` - -``` -note over RAPP, ORU: Configuration and service activation -``` - -``` -loop -``` - -``` - == COLLECTION OF COUNTERS == -``` - -``` - XAPP<-ODU1: Traffic related counters -``` - -``` - XAPP<-ODU2: Traffic related counters -``` - -``` - == DYNAMIC RESOURCE SHIFTING == -``` - -``` - autounumber 1 -``` - -``` - Opt -``` - -``` - XAPP->ODU1: <> Update: list of permitted BWPs -``` - -``` - XAPP<-ODU1: <> Ack -``` - -``` - end -``` - -``` - Opt -``` - -``` - XAPP->ODU2: <> Update: list of permitted BWPs -``` - -``` - XAPP<-ODU2: <> Ack -``` - -``` - end -``` - -``` - ODU1->ORU: <> User traffic and signalling -``` - -``` - ODU2->ORU: <> User traffic and signalling -``` - -``` -end -``` - -``` -@enduml -``` - -The flow diagram of the dynamic resource shifting sub-use case for Shared O-RU is given in figure 4.20.3.24-1. - -![Sequence diagram for dynamic resource shifting sub-use case for Shared O-RU. Lifelines: SMO (rApp), Near Real Time RIC (xApp), O-RAN Shared O-RU Operator (O-DU #1, O-DU #2, O-RU (Shared)). The process includes INITIATION (Configuration and service activation), a loop for COLLECTION OF COUNTERS (Traffic related counters), and DYNAMIC RESOURCE SHIFTING with two optional steps for updating permitted BWPs and handling user traffic.](4628881725ec2d73799a0521cb4036c5_img.jpg) - -``` - -sequenceDiagram - participant SMO as SMO (rApp) - participant RIC as Near Real Time RIC (xApp) - subgraph O-RAN_Shared_O-RU_Operator [O-RAN Shared O-RU Operator] - ODU1[O-DU (#1)] - ODU2[O-DU (#2)] - ORU[O-RU (Shared)] - end - - Note over SMO, RIC, O-RAN_Shared_O-RU_Operator: INITIATION - SMO->>ORU: Configuration and service activation - Note over SMO, RIC, O-RAN_Shared_O-RU_Operator: COLLECTION OF COUNTERS - loop loop - ODU1->>RIC: Traffic related counters - ODU2->>RIC: Traffic related counters - end - Note over SMO, RIC, O-RAN_Shared_O-RU_Operator: DYNAMIC RESOURCE SHIFTING - opt 1 - RIC->>ODU1: 1 «E2» Update: list of permitted BWPs - ODU1->>RIC: 2 «E2» Ack - end - opt 2 - RIC->>ODU2: 3 «E2» Update: list of permitted BWPs - ODU2->>RIC: 4 «E2» Ack - end - ODU1->>ORU: 5 «FH CU-Plane» User traffic and signalling - ODU2->>ORU: 6 «FH CU-Plane» User traffic and signalling - -``` - -Sequence diagram for dynamic resource shifting sub-use case for Shared O-RU. Lifelines: SMO (rApp), Near Real Time RIC (xApp), O-RAN Shared O-RU Operator (O-DU #1, O-DU #2, O-RU (Shared)). The process includes INITIATION (Configuration and service activation), a loop for COLLECTION OF COUNTERS (Traffic related counters), and DYNAMIC RESOURCE SHIFTING with two optional steps for updating permitted BWPs and handling user traffic. - -Figure 4.20.3.24-1: Dynamic resource shifting sub-use case for Shared O-RU - -#### 4.20.3.25 Static resource shifting use case for Single-MNO - -The following will describe the solution for static resource shifting sub-use case for a Shared O-RU. - -Table 4.20.3.25-1: Static resource shifting use case of a Shared O-RU - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Cooperating O-DUs serve cells using a designated chunk of spectrum at a time, allowing carrier frequency resources to be effectively reallocated between O-DUs and ensuring interference is avoided at the air interface.

This is a service impacting use case. | | -| Actors and Roles | Actors:

Shared O-RU | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| |

O-DUs

O-CU

SMO

Roles:

Please refer to 4.20.2.25.

| | -| Initiation | | | -| Assumptions |
  • O-RU is configured to have connectivity with 2 or more O-DUs.
  • O-DUs are configured respectively for connectivity with Shared O-RU.
  • Fronthaul M-plane (Netconf session) sessions are established between Shared O-RU and O-DUs as per provided configurations.
  • SMO knows the capabilities of O-DUs.
  • SMO is receiving traffic-related statistics from O-DUs.
  • SMO manages the entire process and ensures coordination between O-DUs.
  • SMO configures the initial roles and resources for O-DUs and O-RU.
| | -| Collection of counters | | | -| | O-DUs report PM counters to SMO (Non-RT RIC). PM counters are used by SMO as trigger to decide if static resource shifting shall be applied. | | -| Static resource shifting | | | -| Deactivation and removal of cell(s) and carrier(s) associated with O-DU#1 | | | -| Begins when | SMO decides to start static resource shifting for specific cell(s) served by O-DUs through Shared O-RU. | | -| Step 1 (M) | SMO requests O-CU to deactivate cell(s) served by O-DU#1. | | -| Step 2 (M) | O-CU informs O-DU#1 about the cell(s) to be deactivated via F1 interface. | | -| Step 3 (M) | O-DU#1 maps mentioned above cell(s) with corresponding carrier(s) that need to be deactivated on Shared O-RU. | | -| Step 4 (M) | For carriers determined in Step 3, O-DU#1 performs carrier deactivation with O-RU. | | -| Step 5 (M) | Once O-DU#1 knows that relevant carriers(s) are deactivated, it replies to O-CU's request for cell deactivation received in Step 2. | | -| Step 6 (M) | O-CU replies to SMO's request for cell deactivation received in Step 1. | | -| Step 7.1 (M) | Hierarchical deployment – Cell(s) and carrier(s) removal | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| | SMO requests O-DU#1 to remove specific inactive cell(s) and related carrier(s) from configuration. | | -| Step 7.2 (M) | O-DU#1 maps requested cell(s) with carrier(s) that needs to be removed from O-RU's configuration. | | -| Step 7.3 (M) | O-DU#1 informs O-CU about cell(s) being subject of removal. | | -| Step 7.4 (M) | O-DU#1 performs config update scenario to O-RU to remove configuration related to carrier(s) determined in Step 7.2. | | -| Step 7.5 (M) | O-DU#1 responds to SMO's request for cell removal received in Step 7.1. | | -| Step 8.1 (M) | Hybrid deployment – Cell(s) and carrier(s) removal

SMO requests O-RU to remove specific carriers. | | -| Step 8.2 (M) | O-RU notifies O-DU that specific carriers have been removed. | | -| Step 8.3 (M) | O-DU#1 performs carrier-to-cell mapping. | | -| Step 8.4 (M) | O-DU#1 informs SMO about change in resource availability. | | -| Step 8.5 (M) | For cells that have lost their related carriers completely O-DU#1 informs O-CU about cells are no longer operational. | | -| Step 8.6 (M) | O-RU responds to SMO's request for carrier(s) removal. | | -| Step 8.7 (M) | SMO requests O-DU#1 to remove affected cells. | | -| Step 8.8 (M) | O-DU#1 responds to SMO's request. | | -| Configuration of cell(s) and carrier(s) associated with O-DU#2 | | | -| Step 9.1 (M) | Hierarchical deployment – Cell(s) and carrier(s) configuration

SMO configures the cell(s) and related carriers to O-DU#2. | | -| Step 9.2 (M) | Based on provided configuration O-DU#2 maps the cell(s) with related carrier(s) that needs to be configured to O-RU. | | -| Step 9.3 (M) | O-DU#2 provides O-RU with configuration for carrier(s) known from Step 9.1. | | -| Step 9.4 (M) | For cells having their related carriers configured to O-DU, the O-DU#2 informs O-CU about cell(s) being ready to be used. | | -| Step 9.5 (M) | For configured cells requested in Step 9.1 the O-DU#2 sends cell(s) configuration notification to SMO. | | -| Step 10.1 (M) | Hybrid deployment – Cell(s) and carrier(s) removal

SMO requests O-RU to configure carrier(s). | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|----------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 10.2 (M) | O-RU sends carrier(s) configuration change notification to O-DU#2. | | -| Step 10.3 (M) | O-RU sends carrier(s) configuration change notification to SMO. | | -| Step 10.4 (M) | SMO requests O-DU#2 to configure cell(s) and informs O-DU#2 about mapping between cells and carriers. | | -| Step 10.5 (M) | For cells with properly mapped carriers the O-DU#2 informs O-CU about cell(s) that are available and ready for activation. | | -| Step 10.6 (M) | O-DU#2 to SMO's request provided in Step 10.4. | | -| Step 11 (M) | SMO requests O-CU to activate specific cells. | | -| Step 12 (M) | O-CU requests O-DU#2 to activate specific cell(s) mentioned in Step 11. | | -| Step 13 (M) | O-DU#2 maps requested cell(s) with carrier(s) that needs to be activated to O-RU. | | -| Step 14 (M) | O-DU#2 requests O-RU to activate carriers determined in Step 13. | | -| Step 15 (M) | O-RU responds to O-DU#2 with carrier(s) activation notification. | | -| Step 16 (M) | O-DU#2 responds to O-CU with cell(s) activation response. | | -| Step 17 (M) | O-CU responds to SMO with cell(s) activated notification. | | -| Ends when | Shifting of cell(s) and associated carrier(s) from O-DU#1 to O-DU#2 is accomplished. | | -| Exceptions | Error at any of listed steps. | | -| Post Conditions | Frequency resources are used by cells and related carriers handled by O-DU#2. | | - -``` - -@startuml -!pragma teoz true - -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 - -Box "SMO" #gold - Participant RAPP as "rApp" -end box - -Box "O-RAN\nShared O-RU Operator" #lightpink - Participant OCU as "O-CU" - Participant ODU1 as "O-DU\n(#1)" - -``` - -``` -Participant ODU2 as "O-DU\n(#2)" -participant ORU as "O-RU\n(Shared)" -End box - -== INITIATION == -note over RAPP, ORU: Configuration and service activation - -== COLLECTION OF COUNTERS == -RAPP<-ODU1: Traffic related counters -RAPP<-ODU2: Traffic related counters - -== STATIC RESOURCE SHIFTING == -== DEACTIVATION AND REMOVAL OF CELL(S) ASSOCIATED WITH O-DU#1 == - -autonumber 1 - -Opt -RAPP->OCU: <> Deactivates cell(s) on O-DU#1 -Activate OCU -OCU->ODU1: <> Cell(s) deactivation -Activate ODU1 -ODU1->ODU1: Cell-carrier(s) mapping -ODU1<->ORU: <> Carrier(s) deactivation -OCU<-ODU1: <> Cell(s) deactivation response -Deactivate ODU1 -RAPP<-OCU: <> Cell(s) deactivation-notification -Deactivate OCU - -autonumber 7.1 - -Alt Hierarchical Deployment - Carrier(s) removal -RAPP->ODU1: <> Cell(s) / carrier(s) deletion -Activate ODU1 -ODU1->ODU1: Cell to carrier mapping -OCU<->ODU1: <> Cell(s) removal -ODU1<->ORU: <> Carrier(s) removal -``` - -``` -RAPP<-ODU1: <> Cell(s) / carrier(s) deletion notification -``` - -``` -Deactivate ODU1 -``` - -``` -autonumber 8.1 -``` - -``` -else Hybrid Deployment - Carrier(s) removal -``` - -``` -Activate RAPP -``` - -``` -RAPP->ORU: <> Delete carrier(s) -``` - -``` -Activate ORU -``` - -``` -ORU->ODU1: <> Configuration change notification -``` - -``` -Activate ODU1 -``` - -``` -ODU1->ODU1: Carrier to cell mapping -``` - -``` -ODU1->RAPP: <> Configuration change notification -``` - -``` -OCU<->ODU1: <> Cell(s) removal -``` - -``` -Deactivate ODU1 -``` - -``` -RAPP<-ORU: <> Carriers deleted -``` - -``` -Deactivate ORU -``` - -``` -RAPP->ODU1: <> Delete cell(s) -``` - -``` -Activate ODU1 -``` - -``` -RAPP<-ODU1: <> Cell(s) deleted - notification -``` - -``` -Deactivate ODU1 -``` - -``` -Deactivate RAPP -``` - -``` -end Alt -``` - -``` -== CONFIGURATION OF CELL(S) AND CARRIER(S) ASSOCIATED WITH O-DU#2 == -``` - -``` -autonumber 9.1 -``` - -``` -Alt Hierarchical Deployment -``` - -``` -RAPP->ODU2: <> Configure cell(s) -``` - -``` -Activate ODU2 -``` - -``` -ODU2->ODU2: Cell to carrier mapping - -ODU2<->ORU: <> Carrier configuration - -ODU2<->OCU: <> Cell(s) ready to be used - -RAPP<-ODU2: <> Cell(s) configured - notification - -Deactivate ODU2 - -autonumber 10.1 - -else Hybrid Deployment - -Activate RAPP - -Activate ORU - -RAPP->ORU: <> Configure carrier(s) - -ORU->ODU2: <> Configuration change notification - -RAPP<-ORU: <> Carrier(s) configured - notification - -Deactivate ORU - -RAPP->ODU2: <> Configure cell(s) and cell(s) to carrier(s) mapping - -Activate ODU2 - -ODU2->OCU: < Cell(s) ready to be used - -RAPP<-ODU2: <> Cell(s) configured - notification - -Deactivate ODU2 - -Deactivate RAPP - -end Alt - -autonumber 11 - -RAPP->OCU: <> Activate cell(s) on ODU2 - -Activate OCU - -OCU->ODU2: <> Activate cell(s) - -Activate ODU2 - -ODU2->ODU2: Cell(s) to carrier(s) mapping - -ODU2->ORU: <> Carrier activation - -ODU2<-ORU: <> Carrier activation - notification - -OCU<-ODU2: <> Cell(s) activation response -``` - -``` -Deactivate ODU2 -RAPP<-OCU: Cell(s) activated - notification -Deactivate OCU -end - -@enduml -``` - -The flow diagram of the static resource shifting sub-use case for Shared O-RU is given in figure 4.20.3.25-1. - -![Sequence diagram for Static resource shifting sub-use case for Shared O-RU. Lifelines: SMO (rApp), O-CU, O-DU (#1), O-DU (#2), O-RU (Shared). The diagram shows phases for Initiation, Counter Collection, Static Resource Shifting, Deactivation/Removal of cells on O-DU#1, and Configuration/Activation of cells on O-DU#2.](c6a96f95e328ae9493edffdae3d3cb28_img.jpg) - -The sequence diagram illustrates the interaction for static resource shifting. It begins with **INITIATION** where the rApp sends a 'Configuration and service activation' message to the O-CU. This is followed by **COLLECTION OF COUNTERS** where the O-CU sends 'Traffic related counters' to the rApp. The **STATIC RESOURCE SHIFTING** phase follows, leading to **DEACTIVATION AND REMOVAL OF CELL(S) ASSOCIATED WITH O-DU#1**. This section is an **opt** block starting with message 1: '«O1» Deactivates cell(s) on O-DU#1'. It contains an **alt** block for **[Hierarchical Deployment - Carrier(s) removal]** (messages 7.1-7.5) and another for **[Hybrid Deployment - Carrier(s) removal]** (messages 8.1-8.8). The next major phase is **CONFIGURATION OF CELL(S) AND CARRIER(S) ASSOCIATED WITH O-DU#2**, which also has an **alt** block for **[Hierarchical Deployment]** (messages 9.1-9.5) and **[Hybrid Deployment]** (messages 10.1-10.6). Finally, message 11: '«O1» Activate cell(s) on ODU2' initiates the activation sequence (messages 12-17), resulting in 'Cell(s) activated - notification' back to the rApp. - -Sequence diagram for Static resource shifting sub-use case for Shared O-RU. Lifelines: SMO (rApp), O-CU, O-DU (#1), O-DU (#2), O-RU (Shared). The diagram shows phases for Initiation, Counter Collection, Static Resource Shifting, Deactivation/Removal of cells on O-DU#1, and Configuration/Activation of cells on O-DU#2. - -Figure 4.20.3.25-1: Static resource shifting sub-use case for Shared O-RU - -### 4.20.4 Required data - -#### 4.20.4.1 Required data for all Shared O-RU use cases - -The following required data is relevant to the following sub-use cases: resource partitioning, start-up, configuration, supervision, performance management, ALD control, antenna calibration, rehoming, and shutdown: - -- Inventory system maintains inventory data for the Shared O-RUs because it needs to be able to identify Shared O-RUs. -- The resource partitioning rApp maintains carrier resource information because it needs to be able to partition the Shared O-RU carrier resources between different O-DU nodes. -- In hierarchical management mode, the configuration rApp maintains the active/standby state & status for O-DUs because needs to determine which O-DU is responsible for configuring the common aspects of a Shared O-RU. -- The supervision needs to include the O-DU identity because the Shared O-RU needs to be able to support supervision on a per O-DU basis. -- Alarm data needs to be kept at the Shared O-RU because the Shared O-RU needs to be able to terminate transmissions associated with an O-DU when it loses supervision with that O-DU and to continue to operate with other O-DUs. There will be a history of alarm data. -- Shared O-RU measurement counters and KPIs (as defined by O-RAN.WG4.MP [28]) shall be available on a per O-DU basis. -- O-DU needs to include its O-DU identity to enable supervision operation on a per O-DU basis. -- The ALD control rApp maintains data to keep track which O-DU is responsible for ALD controller functionality because it needs to be able to select which O-DU is responsible for ALD controller functionality. - -#### 4.20.4.2 Required data for Single-MNO configurations - -The following data applies for single operator configurations when used by the other Shared O-RU sub-use cases: - -- Non-RT RIC needs to be able to partition the Shared O-RU carriers between O-DU nodes operated by the same MNO. - -#### 4.20.4.3 Required data for Multi-MNO configurations - -The following data applies for multi-operator configurations when used by the other Shared O-RU sub-use cases: - -- The resource partitioning rApp needs to be able to partition the Shared O-RU carrier resources between different O-DU nodes of different MNOs. -- Shared O-RU needs to be able to associate management accounts with an MNO. -- The Shared O-RU needs to be able to implement role-based access control on a per-MNO basis. -- The Shared O-RU needs to associate carrier resources with MNOs. -- Measurement counters and KPIs (as defined by O-RAN WG4) need to be available on a per MNO basis. -- Tenant SMO needs to be able to support common Shared O-RU configuration defined by host operator. - -#### 4.20.4.4 Required data for resiliency use cases - -The following data is used by the resiliency use case: - -- The supervision needs to include the O-DU identity because the Shared O-RU needs to be able to support supervision on a per O-DU basis. -- Alarm data needs to be kept at the Shared O-RU because the Shared O-RU needs to be able to terminate transmissions associated with an O-DU when it loses supervision with that O-DU and to continue to operate with other O-DUs. There will be a history of alarm data. -- The configuration data from the active O-DU is passed to the standby O-DU. -- The configuration information of carriers of the standby O-DU are configured for the O-RU. -- The management system has the state & status data regarding which O-DU is and shall be active. -- The management system has the state & status data regarding which O-DUs are and shall be standby. -- The management system has the alarm history and alarm information for the Shared O-RU. - -NOTE: There are many different situations and variations of the resiliency sub-use cases. Some of them need not require all the above data. - -#### 4.20.4.5 Required data for Shared O-RU management during O-DU SW update sub-use case for Shared O-RU - -The following data is used by SW update of O-DU and associated Shared O-RU provisioning: - -- The *configuration data* for provisioning the SW updated O-DU based on the change management plan for SW update. -- The *configuration information* of carriers of the SW updated O-DU configured on the Shared O-RU. -- The management system *has state and status details* of O-DUs to identify the right candidate to be used for SW update. -- The management system has *state and status details* of SW updated O-DU to verify the status and health of the SW update. -- The management system has the *alarm history and alarm data* of the Shared O-RU to verify functionality and sanity of the SW updated O-DU. -- Non-RT RIC needs to be able to partition the Shared O-RU carriers between SW updated O-DU and other O-DU nodes operated by the same MNO. -- Alarm data and performance data needs to be kept at Shared O-RU to verify the sanity of O-DU SW update -- O-DU SW change management rApp maintains the change management plan data for O-DU SW update to initiate & supervise the SW update process and to validate the sanity of the deployment against the plan. -- Historical configuration and software details of the O-DU is maintained for SW update so that the mitigation step of the SW update can bring the O-DU to the situation before SW update. - -#### 4.20.4.6 Required data for Shared O-RU - Dynamic resource shifting - -The following data is used to perform dynamic resource shifting: - -- The resource partitioning xApp maintains cell resource information because it needs to be able to partition frequency resources between different O-DU nodes. -- O-DU measurement counters and KPIs related to served traffic shall be available for Near-RT RIC on a per O-DU basis. -- Near-RT RIC needs to be able to dynamically update list of allowed bandwidth parts per O-DU nodes in a way so that each O-DU exclusively uses subset of shared bandwidth. -- The configuration information of cells served by O-DUs needs to be known to Near-RT RIC. - -#### 4.20.4.7 Required data for Shared O-RU - Static resource shifting - -The following data is used to perform static resource shifting: - -- The resource optimization rApp may maintain cell resource information because it needs to be able to reallocate the cell and associated carrier frequency resources between different O-DU nodes. -- O-DU measurement counters shall be available for SMO (Non-RT RIC) on a per O-DU and per cell basis via O1 interface. -- The configuration information of cell(s) served by O-DUs needs to be known to SMO (Non-RT RIC). - -## 4.21 Network energy saving - -This clause provides the motivations, descriptions, and proposed solutions for different energy efficiency and energy saving features (sub-use cases). While there are energy savings by improving base station hardware efficiency and by the evolution of radio access technologies, the EE/ES use case primarily addresses enhancements in software efficiency and optimized configuration/control of various elements and functions, which are often AI/ML based. - -### 4.21.1 Background and goal of the use case - -The RAN is responsible for a major part of the Energy Consumption (EC) of a mobile network, and the O-RU accounts for the largest part of the energy consumption of the RAN. The rarefaction of fossil fuel-based energy resources and the urgent need to reduce CO2 emissions make the EC a strategic topic for network operators, in addition to being a significant component of the operators' OPEX. - -EC can be reduced by improving the Energy Efficiency (EE) of the network, and by introducing different Energy Saving (ES) mechanisms. Several ES mechanisms are related to switching off certain components in the network and differ from one another by their scope, time scale and network area. Applicable ES methods are for instance strongly load dependent. Optimization efficiency might be further improved by AI/ML based configuration thereof. - -RAN functions related to network energy saving solutions have been studied in 3GPP RAN3 in Rel.17 as part of the Study on Enhancement for Data Collection for NR and EN-DC. The outcome is documented in 3GPP TR 37.817 [i.2]. 3GPP RAN2 and RAN3 might specify enhancements for the Minimization of Drive Tests (MDT) procedures and/or signaling procedures that rely on Xn signaling in Rel.18. While 3GPP RAN WGs work on solutions with ML model inference within the gNB, O-RAN specifies solutions that benefit from ML model inference in the Near-RT or Non-RT RIC (e.g., optimizing the network in larger service areas). For EE related network management, use cases, requirements and solutions are specified in 3GPP TS 28.310 [43]. Furthermore, EC measurements and KPIs for 5G networks, network functions, NG-RAN and gNBs such as energy efficiency and energy consumption KPIs and performance measurements are specified in 3GPP TS 28.554 [7]. Centralized and distributed ES management functions are specified in 3GPP TS 28.541 [5]. 3GPP TS 28.310 [43] specified the framework on how the operator may configure the energy source and supply information (external power source information) with the information obtained from sources external to 3GPP e.g., energy supplier. - -EE can be considered for the whole network (i.e., end-to-end), for a sub-network or per single network element. Within a network element it could be applicable per specific radio resource management mechanism or per radio or transport network link. Network wise EE is defined as the ratio between the data volume delivered in the network and the network EC observed during the time-period required to deliver such data, with possible adaptations to account for different deployment scenarios and load situations (ETS ES 203 228 [i.5], 3GPP TR 38.913 [i.4]). 3GPP has launched a study item within Rel-18 (RP-213554: “Study on network energy saving for NR”) that will include among others, an evaluation methodology and KPIs for EC and ES gains and their impact on network and UE performance and EE. To assess EE and ES associated to radio resource management mechanisms and links, appropriate KPIs are necessary. - -In a timescale of minutes, hours and above, and when the cell load is low, ES can be achieved by switching off one or more carriers or the cell. In a timescale from seconds to minutes, ES can be achieved by switching off RF channels (including possibly antennas) of a massive MIMO system. Tx and Rx parts might be switched independently. In a very short time scale corresponding to a symbol, subframe or frame, Advanced Sleep Modes (ASM) can be considered. RF channel on/off switching can be used at medium load and ASM might be usable even at high load. Lastly, ES solutions can be applied to the O-Cloud, namely to the O-CU and O-DU, and can cover mechanisms such as scale in/out processes, workload placement or hardware processors’ sleep modes etc. AI/ML is useful for all the above mechanisms with the important role of determining the switch off/on time that maximizes ES gain. - -RF channel switch off/on (also known as RF channel reconfiguration) enables the dynamic, policy-driven activation/deactivation of a subset of RF/antenna resources in the O-RU, allowing: 1. Major reduction in power consumption and 2. Near-instantaneous restoration (wake-up) of all RF chains if demand rises or coverage is threatened. Modern O-RUs and massive MIMO radios are built with a high number of TRX (transceiver) chains and associated digital processing. In periods of low load (night/off-peak, rural/edge cells, etc.), a significant portion of these resources are underutilized, but still consume most of the energy of a fully active radio. - -Advanced Sleep Mode feature is expected to reduce O-RU power consumption by partially switching off certain components. The impact of ASM on O-DU and O-CU energy consumption is not specified in the current document. Using multi-dimensional data—such as traffic load, user service type, and energy efficiency measurements—the SMO and/or Near-RT RIC can configure cell parameters, including SSB periodicity, to enable and optimize sleep mode operations. - -Furthermore, the energy source and supply information may be used as an input data for SMO framework. This framework, leveraging a Non-RT RIC platform with rApps, may use the energy source and supply information to analyze and prepare policy and/or configuration changes to activate the appropriate energy saving methods in the O-RU, thereby minimizing power consumption. - -In addition to the above-mentioned energy saving methods, the O-RU energy saving could be achieved by optimizing its Power Amplifier (PA) operating region according to the traffic scheduling requirements, to reduce the O-RU power consumption. To facilitate this, the SMO framework analyses various network data and KPIs to prepare policy or configuration changes for the O-DU. The O-DU then evaluates the conditions specified in the policies or applies the configuration changes provided by the SMO. When those conditions are satisfied or based on requested configuration changes, the O-DU configures the maximum output power of the O-RU via fronthaul M-plane or C-plane interface. The O-RU subsequently optimizes its power amplifier parameters according to the configured maximum output power. This could result in a reduction of PA power consumption, thereby achieving energy saving in O-RU and enhance the overall energy efficiency of the O-RAN network. - -### 4.21.2 Entities/resources involved in the use case - -*Editor’s note: If possible, single common description for all sub-use cases.* - -The following is an exhaustive list of entities across all the identified solutions for this use case. All the entities may not be applicable for every solution. - -- 1) Energy saving rApp: - - a) Collect configurations, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports, geolocation information, and energy source and supply - -information configured by either operator or available through SMO or exposed via O-RAN networks) from Non-RT RIC/SMO framework. - -- b) Utilize the collected data for EE/ES optimization (e.g., if carriers or cells need to be switched off/on), and initiate O1 configuration updates, A1 policy updates, and/or open FH M-plane configuration updates through R1 interface. - -#### 2) Non-RT RIC/SMO framework: - -- a) Collect configurations, performance indicators, measurement reports, and energy source and supply information from network functions via O1 and optionally via open FH M-plane from O-RUs and provide this information to energy saving rApp. -- b) Determine and signal updated configuration or policy for network energy saving use case (provided by energy saving rApp) to E2 nodes, and/or Near-RT RIC, and optionally O-RU. - -#### 3) NF node: - -- a) Report cell configuration, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports). -- b) Perform actions required for EE/ES optimization per the configuration updates or policies received from Non-RT RIC/rApp and/or Near-RT RIC/xApp. - -#### 4) O-RU node: - -- a) Report EC and EE related information. -- b) Perform actions required to perform EE/ES optimization per the configuration updates received from the O-DU or SMO depending on the hierarchical or hybrid deployment. -- c) Receives the energy source and supply information from energy supplier in an operator specific implementation and forward the same to SMO through O-DU, if the O-RU is provisioned to support the external power source information exposure. - -#### 5) Near-RT RIC: - -- a) Collect configurations, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) from E2 nodes. -- b) Receive EE/ES related policies via A1 interface for consideration during optimization. -- c) Determine and signal updated configuration or policy for network energy saving use case to E2 nodes. -- d) Receive external power source information for the O-RU/NF node via O1/SMO. - -#### 6) Energy supplier control panel (external enrichment provider): - -- a) This is the external power source entity that manages the various energy sources such as grid power supply, battery back-up, generator, and renewable energy sources such as solar power, windmill, etc. -- b) Collect the energy source and supply information and expose them to operator in vendor specific implementation. -- c) Switch the energy source from one to another, for example, switch the energy source from grid supply to solar power or generator power or battery back-up. - -#### 7) Operator: - -- a) A telecom operator who collects the energy source and supply information from energy supplier control panel in a vendor specific deployment and implementation. -- b) Configure the energy source and supply information to SMO framework in a vendor specific implementation as described in clauses 5.1.6 and 8 of 3GPP TS 28.310 [43]. - -### 4.21.3 Solutions - -*Editor's note: Sub-use case specific solutions with detailed descriptions in fully separate clauses.* - -#### 4.21.3.1 Carrier and cell switch off/on - -Mobile networks often utilize multiple frequency layers (carriers) to cover the same service area. At low load, ES can be achieved by switching off one or more carriers or entire cells without impairing the network performance. The switch - -off/on decision can be made by an AI/ML model, deployed in Non-RT RIC/SMO (including option for deployment in an rApp) or at Near-RT RIC. Among others, the AI/ML models' functionality can include prediction of future traffic, user mobility, and resource usage and can also predict expected energy efficiency enhancements, resource usage, and network performance for different ES optimization states. Before switching off/on carrier(s) or cell(s), the E2 node can perform some preparation actions for off switching (e.g., to enable, disable, modify carrier aggregation and/or dual connectivity, to trigger HO traffic and UEs from cells/carriers to other cells or carriers, informing neighboring nodes via X2/Xn interface etc.) as well as for on switching (e.g., cell probing, informing neighboring nodes via X2/Xn interface etc.). - -##### 4.21.3.1.1 Solution 1: rApp-based solution (O1-based) - -The following entities are applicable to this solution: Energy saving rApp, Non-RT RIC/SMO framework, E2 node(s) and O-RU node(s). - -A solution for carrier and cell switch off/on: use case through rApp-based solution is captured in table 4.21.3.1.1-1. - -**Table 4.21.3.1.1-1: Carrier and cell switch off/on: AI/ML inference via Non-RT RIC** - -| Use Case Stage | Evolution / Specification | <> | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Goal | Enable carrier and cell switch off/on energy saving functions in the network by means of configuration parameter change and actions controlled by Non-RT RIC and allow for AI/ML-based solutions. | | -| Actors and Roles | 1) Energy saving rApp
2) Non-RT RIC/SMO framework
3) E2 node(s)
4) O-RU node(s) | | -| Assumptions | O1 interface connectivity is established towards E2 nodes, Non-RT RIC and SMO.
Open FH M-plane interface is established between E2 node and O-RU and/or SMO and O-RU directly.
Network is operational. | | -| Pre-conditions | Operator has set the targets for energy saving functions in the Non-RT RIC. | | -| Begins when | Operator enables the optimization functions for carrier and cell switch off/on energy saving functions and E2 node and O-RU become operational. | | -| Step 1 (M) | SMO initiates specific measurement data collection request towards E2 node and O-RU. | | -| Step 2 (M) | E2 node and O-RU send the configured measurement data to SMO periodically or event based. | | -| Step 3 (M) | Energy saving rApp retrieves the collected measurement data for processing. | | -| Step 4 (M) | Energy saving rApp constantly monitors
(i) performance and energy consumption of the E2 node(s)
(ii) energy consumption of O-RU(s)
(iii) cell utilization and throughput metrics | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| | rApp determines configuration changes for carrier(s) and cell(s) switch off/on use case. AI/ML inference may be used to make the decision. | | -| Step 5 (M) | Energy saving rApp requests Non-RT RIC/SMO framework to make configuration changes to E2 node(s) and O-RU(s). | | -| Step 6 (M) | SMO instructs E2 node via O1 interface to apply the received request(s) for configuration changes from the rApp. O-RU is informed about the updated O-RU configuration via open FH M-plane interface either by E2 node, or by SMO directly. E2 node / O-RU notify SMO once cell or carrier switch off/on is completed. | | -| Step 7 (M) | Energy saving rApp continuously analyzes energy saving objectives and if energy saving objectives are not achieved, it can decide to initiate fallback mechanism, for example, reverting changes over O1 interface for carrier and cell switch off/on optimization. | | -| Ends when | E2 node becomes non-operational or when the operator disables the optimization functions for energy saving. | | -| Exceptions | None. | | -| Post Conditions | Non-RT RIC continues close loop monitoring of energy saving function at E2 node and O-RU.

E2 node(s) and O-RU(s) operate using the configuration provided by the energy saving rApp via Non-RT RIC/SMO framework. | | - -``` - -@startuml -Skin rose -skinparam defaultFontSize 12 -autonumber - -Box "Service Management & \n Orchestration Framework" #gold - -Participant "Collection & Control" as SMO -Participant "Non-RT RIC" as NRTRIC - -End box - -Box "O-RAN Nodes" #lightpink - Participant "Near-RT RIC" as RTRIC - Participant "E2-Nodes" as E2NODES - Participant "O-RUs" as ORUs -End box - -``` - -``` -group Data Collection -autonumber 1.1 -SMO -> E2NODES : <> Data collection request for Energy Saving -E2NODES -> ORUs : <> Data collection request for Energy Saving - -autonumber 2.1 -ORUs -> E2NODES : <> Measurement Data Collection for Energy Saving -E2NODES -> SMO : <> Measurement Data Collection for Energy Saving - -autonumber 3 -SMO -> NRTRIC : Data retrieval - -end - -group Data Analysis Training and Inference -autonumber 4.1 - - NRTRIC -> NRTRIC : Performance and Energy Consumption Monitoring \n(E2 Node(s) & O- -RU(s)) - - NRTRIC -> NRTRIC : AI/ML Model training and inference - -end - -autonumber 5 - -group Actor Decision Making - - NRTRIC -> SMO : Request to prepare and execute \nfor carrier(s) and cell(s) switch -off/on - -autonumber 6.1 - -alt via O1 - -SMO <-> E2NODES : <> E2-Node parameter configurations and actions for carrier(s) and -cell(s) switch off/on \npreparation & execution and notification of execution. - - E2NODES <-> ORUs : <> Update O-RU Configurations \nand notification of -update - -else via OFH-MP -``` - -``` - -SMO <-> E2NODES : <> E2-Node parameter configurations and actions for carrier(s) and cell(s) switch off/on \npreparation & execution \nand notification of execution. - -SMO <-> ORUs: <> Update O-RU Parameters configuration and notification of update - -end - -autonumber 7 - -NRTRIC -> NRTRIC : Performance analysis of AI/ML model \n(with possible actions, e.g. fallback, re-training) - -end - -@enduml - -``` - -The flow diagram of the carrier and cell switch off/on using O1-based solution is given in figure 4.21.3.1.1-1. - -![Sequence diagram showing the interaction between Service Management and Orchestration (App, Non-RT RIC/SMO framework) and O-RAN Nodes (E2-Nodes, O-RUs) for carrier and cell switch off/on. The process includes Data Collection, Actor Decision Making, and Configuration change request over R1. The R1 request is handled via O1 or OFH-MP paths. The O1 path involves E2-Node parameter configurations and actions for carrier(s) and cell(s) switch off/on, preparation & execution and notification of execution. The OFH-MP path involves Update O-RU Parameters configuration and notification of update. Finally, energy saving objectives are monitored.](5911c1f65edf9b3f8469ddacd0756b26_img.jpg) - -``` - -sequenceDiagram - participant App - participant Non-RT RIC/SMO framework - participant E2-Nodes - participant O-RUs - - Note left of Non-RT RIC/SMO framework: Data Collection - Non-RT RIC/SMO framework->>E2-Nodes: 1.1 «O1» Data collection request for Energy Saving - E2-Nodes->>O-RUs: 1.2 «OFH» Data collection request for Energy Saving - E2-Nodes->>O-RUs: 2.1 «OFH» Measurement Data Collection for Energy Saving - E2-Nodes->>Non-RT RIC/SMO framework: 2.2 «O1» Measurement Data Collection for Energy Saving - App->>Non-RT RIC/SMO framework: 3 «R1» Data retrieval - - Note left of Non-RT RIC/SMO framework: Actor Decision Making - Note left of Non-RT RIC/SMO framework: 4.1 Performance and Energy Consumption Monitoring (E2 Node(s) & O-RU(s)) - Note left of Non-RT RIC/SMO framework: Determine configuration changes for - Note left of Non-RT RIC/SMO framework: 4.2 carrier(s) and cell(s) switch off/on - Note left of Non-RT RIC/SMO framework: AI/ML may be used in making the decision - - Note left of Non-RT RIC/SMO framework: Configuration change request over R1 - Non-RT RIC/SMO framework->>E2-Nodes: 5 «R1» Request configuration changes to E2 Node(s) & O-RU(s) - - alt Via O1 - Note right of E2-Nodes: «O1» E2-Node parameter configurations and actions for carrier(s) and cell(s) switch off/on - E2-Nodes->>Non-RT RIC/SMO framework: 6.1 preparation & execution and notification of execution. - Note right of O-RUs: «FH» Update O-RU Configurations and notification of update - O-RUs->>E2-Nodes: 6.2 - else Via OFH-MP - Note right of E2-Nodes: «O1» E2-Node parameter configurations and actions for carrier(s) and cell(s) switch off/on - E2-Nodes->>Non-RT RIC/SMO framework: 6.3 preparation & execution and notification of execution. - Note right of O-RUs: «OFH-MP» Update O-RU Parameters configuration and notification of update - O-RUs->>E2-Nodes: 6.4 - end - - Note left of Non-RT RIC/SMO framework: 7 Monitor energy saving objectives (with possible actions, e.g., fallback) - App->>Non-RT RIC/SMO framework: - -``` - -Sequence diagram showing the interaction between Service Management and Orchestration (App, Non-RT RIC/SMO framework) and O-RAN Nodes (E2-Nodes, O-RUs) for carrier and cell switch off/on. The process includes Data Collection, Actor Decision Making, and Configuration change request over R1. The R1 request is handled via O1 or OFH-MP paths. The O1 path involves E2-Node parameter configurations and actions for carrier(s) and cell(s) switch off/on, preparation & execution and notification of execution. The OFH-MP path involves Update O-RU Parameters configuration and notification of update. Finally, energy saving objectives are monitored. - -![Sequence diagram for Carrier and cell switch off/on flow diagram: AI/ML inference via Non-RT RIC. The diagram shows interactions between Service Management & Orchestration Framework (SMO), Non-RT RIC, Near-RT RIC, E2-Nodes, and O-RUs. It is divided into three main phases: Data Collection, Data Analysis Training and Inference, and Actor Decision Making. In Data Collection, the SMO sends a data collection request to the Near-RT RIC, which then requests data from E2-Nodes and O-RUs. In Data Analysis, the Non-RT RIC performs performance monitoring and AI/ML model training. In Actor Decision Making, the SMO requests a switch off/on, and the Non-RT RIC sends configurations to E2-Nodes and O-RUs via the Near-RT RIC. Finally, a performance analysis is conducted.](72b8a8f5df5818870c46d57b4ac65174_img.jpg) - -Sequence diagram for Carrier and cell switch off/on flow diagram: AI/ML inference via Non-RT RIC. The diagram shows interactions between Service Management & Orchestration Framework (SMO), Non-RT RIC, Near-RT RIC, E2-Nodes, and O-RUs. It is divided into three main phases: Data Collection, Data Analysis Training and Inference, and Actor Decision Making. In Data Collection, the SMO sends a data collection request to the Near-RT RIC, which then requests data from E2-Nodes and O-RUs. In Data Analysis, the Non-RT RIC performs performance monitoring and AI/ML model training. In Actor Decision Making, the SMO requests a switch off/on, and the Non-RT RIC sends configurations to E2-Nodes and O-RUs via the Near-RT RIC. Finally, a performance analysis is conducted. - -Figure 4.21.3.1.1-1: Carrier and cell switch off/on flow diagram: AI/ML inference via Non-RT RIC - -##### 4.21.3.1.2 Solution 2: rApp and xApp-based solution (A1 and E2-based) - -The following entities are applicable to this solution: Energy saving rApp, Non-RT RIC/SMO framework, Near-RT RIC, E2 node and O-RU node. - -A solution for carrier and cell switch off/on through rApp and xApp-based solution is captured in table 4.21.3.1.2-1. - -Table 4.21.3.1.2-1: Carrier and cell switch off/on: AI/ML inference via Near-RT RIC - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Enable carrier and cell switch off/on energy saving functions in the network by means of configuration parameter change and actions controlled by Near-RT RIC and allow for AI/ML-based solutions. | | -| Actors and Roles | 1) Energy saving rApp
2) Non-RT RIC/SMO framework
3) Near-RT RIC
4) E2 node(s)
5) O-RU node(s) | | -| Assumptions | O1 interface connecting the SMO with E2 node and Near-RT RIC is established. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| |

E2 interface connectivity is established between E2 node and Near-RT RIC.

A1 interface is established between Non-RT RIC and Near-RT RIC.

Open FH M-plane interface is established between E2 node(s) and O-RU(s).

Network is operational.

| | -| Pre-conditions | Operator has set the targets for energy saving function in the Non-RT RIC. | | -| Begins when | Operator enables the optimization functions for carrier and cell switch off/on energy saving functions and E2 node and O-RU become operational. | | -| Step 1 (M) | SMO initiates specific measurement data collection request towards E2 node and O-RU. | | -| Step 2 (M) | E2 node and O-RU send the configured measurement data to SMO periodically or event based. | | -| Step 3 (M) | Energy saving rApp retrieves the collected measurement data for processing | | -| Step 4 (M) |

Energy saving rApp constantly monitors

  • i) performance and energy consumption of the E2 node(s)
  • ii) energy consumption of O-RU(s)

Energy saving rApp determines A1 policy for carrier(s) and cell(s) switch off/on use case. AI/ML model inference may be used to make the decision.

| | -| Step 5 (M) |

rApp requests A1 policy function to create or update A1 policy for energy saving.

A1 policy function requests Near-RT RIC to create or update A1 policy for energy saving.

| | -| Step 6 (M) |

Near-RT RIC constantly monitors

  • (i) performance and energy consumption of the E2 node(s)
  • (ii) energy consumption of O-RU(s)

Based on the optional AI/ML inference, and considering A1 policies, the Near-RT RIC can request the E2 node to prepare and execute cell or carrier switch off/on. E2 node can request O-RU node to prepare and execute cell or carrier switch off/on. E2 node will notify Near-RT RIC once cell or carrier switch off/on is completed.

| | -| Step 7 (M) | Non-RT RIC/rApp and/or Near-RT RIC/xApp monitor energy saving objectives (with possible actions, e.g., update of A1 policy, fallback). | | -| Ends when | E2 node becomes non-operational or when the operator disables the optimization functions for energy saving. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|---------------------------------------------------------------------------------------------|-------------------------| -| Exceptions | None. | | -| Post Conditions | E2 node and O-RU operate using configuration provided by the Near-RT RIC over E2 interface. | | - -``` -@startuml - -skin rose -skinparam defaultFontSize 12 -autonumber - -Box "Service Management & \n Orchestration Framework" #gold - -Participant "Collection & Control" as SMO -Participant "Non-RT RIC" as NRTRIC - -End box - -Box "O-RAN Nodes" #lightpink - Participant "Near-RT RIC" as RTRIC - Participant "E2-Nodes" as E2NODES - Participant "O-RUs" as ORUs - -End box - -group Data Collection -autonumber 1.1 -SMO -> E2NODES : <> Data collection request for Energy Saving -E2NODES -> ORUs : <> Data collection request for Energy Saving - -autonumber 2.1 -ORUs -> E2NODES : <> Measurement Data Collection for Energy Saving -E2NODES -> SMO : <> Measurement Data Collection for Energy Saving - -autonumber 3 -SMO -> NRTRIC : Data retrieval - -end - -autonumber 4.1 - -group AI/ML workflow - - NRTRIC -> NRTRIC : AI/ML Model training - - NRTRIC -> RTRIC : <> or <> Deploy AI/ML model -``` - -``` - -end - -autonumber 5.1 -group Optimization Trigger and Policy - alt - SMO -> RTRIC : <> Optimization Trigger/Target - else - NRTRIC -> RTRIC : <> Intent based Policy - end -end - -autonumber 6.1 -group Actor Data Collection & Decision Making - RTRIC -> E2NODES : <> Data collection request for Energy Saving - E2NODES -> ORUs : <> Data collection request for Energy Saving - ORUs -> E2NODES : <> Measurement Data Collection for Energy Saving - E2NODES -> RTRIC : <> Measurement Data Collection for Energy Saving - - RTRIC -> RTRIC: AI/ML model inference - - RTRIC <-> E2NODES : <> E2-Node parameters configuration and actions \nfor -carrier(s) and cell(s) switch off/on preparation & execution \nand notification of -execution - - E2NODES <-> ORUs: <> Update O-RU configurations \nand notification of update - -end - -@enduml - -``` - -The flow diagram of the carrier and cell switch off/on using A1 and E2-based solution is given in figure 4.21.3.1.2-1. - -![Sequence diagrams for carrier and cell switch off/on flow. The top diagram shows an AI/ML inference via Near-RT RIC, involving Data Collection, Actor Decision Making, and A1 policy updates. The bottom diagram shows an AI/ML inference via Non-RT RIC, involving Data Collection, AI/ML workflow, and Optimization Trigger and Policy. Both diagrams show interactions between rApp, Non-RT RIC/SMO framework, Near-RT RIC, E2-Nodes, and O-RUs.](63c45f0c0f8bc8db8db6b78f6d78c264_img.jpg) - -The diagram illustrates two sequence flows for carrier and cell switch off/on. The top flow shows AI/ML inference via the Near-RT RIC, while the bottom flow shows AI/ML inference via the Non-RT RIC. - -**Top Sequence Diagram: AI/ML inference via Near-RT RIC** - -- Data Collection:** - - 1.1 Data collection request for Energy Saving (rApp to E2-Nodes) - - 1.2 Data collection request for Energy Saving (E2-Nodes to O-RUs) - - 2.1 Measurement Data Collection for Energy Saving (O-RUs to E2-Nodes) - - 2.2 Measurement Data Collection for Energy Saving (E2-Nodes to rApp) - - 3.1 Data retrieval (rApp to Non-RT RIC/SMO framework) -- Actor Decision Making:** - - 4.1 Performance and Energy Consumption Monitoring (rApp to E2-Nodes & O-RUs) - - 4.2 Determine A1 policy for carrier(s) and cell(s) switch off/on. AI/ML may be used in making the decision (rApp internal) -- A1 policy create/update request:** - - 5.1 Request A1 policy create/update to A1 policy function (rApp to Non-RT RIC/SMO framework) - - 5.2 Request A1 policy create/update to Near-RT RIC (Non-RT RIC/SMO framework to Near-RT RIC) -- Actor Data Collection & Decision Making (Near-RT RIC):** - - 6.1 Data collection request for Energy Saving (Near-RT RIC to E2-Nodes) - - 6.2 Data collection request for Energy Saving (E2-Nodes to O-RUs) - - 6.3 Measurement Data Collection for Energy Saving (O-RUs to E2-Nodes) - - 6.4 Measurement Data Collection for Energy Saving (E2-Nodes to Near-RT RIC) - - 6.5 Determine E2-node configuration changes for Energy Saving. AI/ML may be used in making the decision (Near-RT RIC internal) - - 6.6 E2-Node parameters configuration and actions for carrier(s) and cell(s) switch off/on preparation & execution and notification of execution (Near-RT RIC to E2-Nodes) - - 6.7 Update O-RU configurations and notification of update (E2-Nodes to O-RUs) -- Monitor energy saving objectives:** - - 7.1 Monitor energy saving objectives (with possible actions, e.g., update A1 policy) (rApp internal) - - 7.2 Monitor energy saving objectives (with possible actions, e.g., feedback) (Near-RT RIC internal) - -**Bottom Sequence Diagram: AI/ML inference via Non-RT RIC** - -- Data Collection:** - - 1.1 <> Data collection request for Energy Saving (Collection & Control to E2-Nodes) - - 1.2 <> Data collection request for Energy Saving (E2-Nodes to O-RUs) - - 2.1 <> Measurement Data Collection for Energy Saving (O-RUs to E2-Nodes) - - 2.2 <> Measurement Data Collection for Energy Saving (E2-Nodes to Collection & Control) - - 3 Data retrieval (Collection & Control to Non-RT RIC) -- AI/ML workflow:** - - 4.1 AI/ML Model training (Non-RT RIC internal) - - 4.2 <> or <> Deploy AI/ML model (Non-RT RIC to Collection & Control) -- Optimization Trigger and Policy:** - - 5.1 <> Optimization Trigger/Target (Collection & Control to Non-RT RIC) - - 5.2 <> Intent based Policy (Non-RT RIC to Collection & Control) -- Actor Data Collection & Decision Making (Near-RT RIC):** - - 6.1 <> Data collection request for Energy Saving (Near-RT RIC to E2-Nodes) - - 6.2 <> Data collection request for Energy Saving (E2-Nodes to O-RUs) - - 6.3 <> Measurement Data Collection for Energy Saving (O-RUs to E2-Nodes) - - 6.4 <> Measurement Data Collection for Energy Saving (E2-Nodes to Near-RT RIC) - - 6.5 AI/ML model inference (Near-RT RIC internal) - - 6.6 <> E2-Node parameters configuration and actions for carrier(s) and cell(s) switch off/on preparation & execution and notification of execution (Near-RT RIC to E2-Nodes) - - 6.7 <> Update O-RU configurations and notification of update (E2-Nodes to O-RUs) - -Sequence diagrams for carrier and cell switch off/on flow. The top diagram shows an AI/ML inference via Near-RT RIC, involving Data Collection, Actor Decision Making, and A1 policy updates. The bottom diagram shows an AI/ML inference via Non-RT RIC, involving Data Collection, AI/ML workflow, and Optimization Trigger and Policy. Both diagrams show interactions between rApp, Non-RT RIC/SMO framework, Near-RT RIC, E2-Nodes, and O-RUs. - -Figure 4.21.3.1.2-1: Carrier and cell switch off/on flow diagram: AI/ML inference via Near-RT RIC - -#### 4.21.3.2 RF channel reconfiguration for network energy savings - -This feature aims at reducing power consumption of O-RU by reconfiguring the RF channels [27], [28]. Using AI/ML assisted solutions, rApp or xApp will trigger RF channels parameters reconfiguration, 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 massive MIMO architecture or reduce the number of layers and/or number of multi-user scheduled UEs in a hybrid architecture. The O-RU reconfiguration can be performed using the open fronthaul M-plane from E2 node or SMO. - -RF channel reconfiguration can be triggered or orchestrated by: - -- i. Solution: rApp-based solution (O1-based or open fronthaul M-plane control, where hybrid architecture based deployment is supported) [27] -- ii. Solution: rApp/xApp-based solution (E2-based) (clause 4.6.3 of [46]) - -##### 4.21.3.2.1 Solution: rApp-based solution - -The following entities are applicable to this solution: energy saving rApp, Non-RT RIC/SMO, E2 node(s) and O-RU node(s). - -A solution for RF channel reconfiguration-based energy saving, implemented as a use case through an rApp-based approach, is captured in table 4.21.3.2.1-1. - -**Table 4.21.3.2.1-1 RF channel reconfiguration: rApp-based solution** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| -| Goal | Enable RF channel reconfiguration energy saving functions in the network by means of configuration parameter change and actions controlled by an energy Saving rApp. | | -| Actors and Roles | 1) Energy saving rApp
2) Non-RT RIC/SMO
3) E2 node(s)
4) O-RU node(s) | | -| Assumptions |
  • • O1 interface connectivity is established between E2 node(s) and SMO.
  • • Open fronthaul M-plane interface is established between O-DU and O-RU and/or SMO and O-RU directly.
  • • Network is operational.
| | -| Pre-conditions | Operator has set the targets for RF channel reconfiguration energy saving in the Non-RT RIC. E2 node and O-RU are operational. | | -| Begins when | Operator enables RF channel reconfiguration energy saving functions. | | -| Step 1 (M) | Energy saving rApp requests to collect necessary CM, PM and FM data towards SMO/Non-RT RIC function over R1 interface. | | -| Step 2 (M) | SMO/Non-RT RIC function requests data collection, including RF channel reconfiguration (TRx control) related capabilities of the E2 node(s) and O-RU(s) over O1 interface and/or open fronthaul M-plane. | O-RAN.WG4.MP [28], clauses 20.3.1.2 and 20.3.2.2;
O-RAN.WG10.OAM-Architecture [27], clause 4.2.5.1 | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| -| Step 3 (M) | E2 node(s) send the O-DU and O-RU RF channel reconfiguration related capabilities, configuration data, and configured measurement data to SMO/Non-RT RIC over O1 interface periodically or event based. | | -| Step 4 (M) | rApp collects the configuration data, collected measurement data for processing. | | -| Step 5 (M) | Energy saving rApp constantly monitors
  • (i) performance and energy consumption of the E2 node(s)
  • (ii) energy consumption of O-RU(s)
  • (iii) cell utilization and throughput metrics
rApp determines configuration changes for RF channel reconfiguration use case. AI/ML inference may be used to make the decision. | | -| Step 6a (Alt) | SMO/Non-RT RIC will provide the policy to E2 node via O1 interface for RF channel reconfiguration (TRx control) in the specific O-RU. | O-RAN.WG10.OAM-Architecture [27], clauses 4.2.5.1 and 5.2.1 | -| Step 6b (Alt) | SMO/Non-RT RIC will provide configuration changes to the E2 node via O1 interface to activate the RF channel reconfiguration (TRx control) feature in the specific O-RU. | O-RAN.WG10.OAM-Architecture [27], clauses 4.2.5.1 and 5.2.1 | -| Step 7 (M) | E2 node analyzes the conditions mentioned in the policy or configuration changes and decides to activate the RF channel reconfiguration (TRx control) feature in the specific O-RU. | O-RAN.WG10.OAM-Architecture [27], clause 4.2.5.1 | -| Step 8 (M) | E2 node sends appropriate commands to the O-RU via open fronthaul M-plane or C-plane to configure (activate) RF channel reconfiguration (TRx control) feature to the specific O-RU, i.e., O-DU configures a specific antenna mask on O-RU. | O-RAN.WG4.MP [28], clause 20.3.2.3;
O-RAN.WG4.TS.CUS.0-R004 [51], clauses 7.4.6, 16, 16.1, and 16.2 | -| Step 9 (M) | O-RU adjusts its antenna array configuration(s) based on the E2 node provided configuration. Then the O-RU transitions to RF channel switch off/on (TRx control) based energy saving mode. | | -| Step 10 (O) | SMO/Non-RT RIC may provide configuration changes to the E2 node via O1 interface to deactivate the RF channel reconfiguration (TRx control) feature in the specific O-RU. | O-RAN.WG10.OAM-Architecture [27], clauses 4.2.5.1 and 5.2.1 | -| Step 11 (M) | E2 node analyzes the policy provided by SMO in Step 6a or configuration changes requested by Non-RT RIC/SMO in Step 10. Then the E2 node decides to deactivate the RF channel reconfiguration (TRx control) feature in the specific O-RU. | O-RAN.WG10.OAM-Architecture [27], clause 4.2.5.1 | -| Step 12 (M) | E2 node sends the appropriate commands to the O-RU via open fronthaul M-plane or C-plane to configure the default antenna array configuration. This is to deactivate the RF channel reconfiguration (TRx control) feature in the O-RU. | O-RAN.WG4.MP [28], clause 20.3.2.3;
O-RAN.WG4.TS.CUS.0- | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------| -| | | Related use | -| | | R004 [51], clauses 7.4.6, 16, 16.1, and 16.2 | -| Step 13 (M) | The O-RU adjusts its antenna array configuration and exits from the energy saving mode. | | -| Ends when |
  • Load or coverage changes, or policy expires/aborts.
  • E2 node and O-RU nodes become non-operational or when the operator disables the optimization functions for energy saving or when optimization criteria are no longer met.
| | -| Exceptions | O-RU/E2 node reports failure or resource is ineligible (e.g., all SSB/PRACH beams masked). | | -| Post Conditions |
  • O-RU is restored to full RF channels off.
  • SMO logs energy gain and status.
  • Non-RT RIC continues closed loop monitoring of energy saving function at E2 node and O-RU.
  • O-DU(s) and O-RU(s) operate using the configuration provided by the energy saving rApp via Non-RT RIC/SMO.
| | - -``` - -@startuml -!pragma teoz true - -' ==== Styling ==== -skinparam sequenceArrowThickness 2 -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -skinparam sequenceMessageAlign center -skinparam NoteBackgroundColor #fff9e6 -skinparam NoteBorderColor #dlb77a -skinparam BoxBorderColor #888 -skinparam BoxBackgroundColor #f7f7f7 - -title RF channel reconfiguration based energy saving - rApp-based solution - -Skin rose - -' ==== Context & Roles ==== -box "Operator" #Lightblue - Actor Host as host -End box - -box "Service Orchestration and Management Framework" #gold - participant "Energy Saving rApp" as rApp - participant "SMO / Non-RT RIC" as smo -end box - -box "O-RAN Nodes" #lightpink - participant "E2 node(s)\n(e.g., O-DU)" as e2 - participant "O-RU node(s)" as ru -end box - -' ==== Step 1 (M) ==== - -``` - -``` - -rApp -> smo : 1 <> – Request CM/PM/FM data collection - -' ==== Step 2 & 3 (M) ==== -note over smo, ru -2 <> Request data collection & O-DU and O-RU RF channel reconfiguration -related capabilities -end note -smo <- e2 : 3 <> Deliver requested data & O-DU and O-RU \nRF channel -reconfiguration related capabilities - -' ==== Step 4 (M) ==== -smo -> rApp : 4 <> Deliver collected configuration/measurement data - -' ==== Step 5 (M) ==== -Loop RF channel reconfiguration implementation -rApp -> rApp : 5 Continuous monitoring & inference -note right of rApp -Monitors: -(i) E2 node performance & energy consumption -(ii) O-RU energy consumption -(iii) Cell utilization & throughput -Determines configuration changes for RF Channel Reconfiguration. -AI/ML inference may be used. -end note - -' ==== Step 6a/6b (Alt) ==== -alt Policy path -smo -> e2 : 6a <> – Provide policy for RF Channel reconfiguration in -specific O-RU -else Direct configuration path -smo -> e2 : 6b <> – Provide configuration to activate TRx control -end - -' ==== Step 7 (M) ==== -e2 -> e2 : 7 Analyze conditions/policy; decide to activate RF channel -reconfiguration - -' ==== Step 8 (M) ==== -e2 -> ru : 8 <> Configure (activate) TRx control\n(e.g., set -antenna mask) - -' ==== Step 9 (M) ==== -ru <- ru : 9 Adjust antenna array; enter energy saving mode - -' ==== Step 10 (O) – Optional deactivation request ==== -opt Deactivation requested by SMO -smo -> e2 : 10 <> – Provide configuration to deactivate TRx control -' ==== Step 11 (M) ==== -e2 -> e2 : 11 Evaluate (policy from 6a or request from 10);\ndecide to deactivate -TRx control - -' ==== Step 12 (M) ==== -e2 -> ru : 12 <> Configure default antenna array\n(to deactivate -TRx control) -' ==== Step 13 (M) ==== -ru <- ru : 13 Adjust antenna array; exit energy saving mode - -deactivate rApp -end - -``` - -end loop - -@enduml - -The flow diagram of the RF channel reconfiguration-based energy saving using rApp-based solution is given in figure 4.21.3.2.1-1. - -![Sequence diagram titled 'RF channel reconfiguration based energy saving - rApp-based solution'. It shows interactions between an Operator/Host, Service Orchestration and Management Framework (containing Energy Saving rApp and SMO/Non-RT RIC), and O-RAN Nodes (containing E2 node(s) and O-RU node(s)). The process involves requesting data, monitoring, policy decision, and reconfiguration of TRx control.](7137a384b59a4b2c2ff2bc879e38a6af_img.jpg) - -``` - -sequenceDiagram - participant Operator - participant Host - subgraph SOMF [Service Orchestration and Management Framework] - ES_rApp[Energy Saving rApp] - SMO[SMO / Non-RT RIC] - end - subgraph ORN [O-RAN Nodes] - E2[E2 node(s) (e.g., O-DU)] - O_RU[O-RU node(s)] - end - - Note right of SOMF: end loop - Note right of SOMF: @enduml - - ES_rApp->>SMO: 1 «R1» — Request CM/PM/FM data collection - SMO->>E2: 2 «O1» Request data collection & O-DU and O-RU RF channel reconfiguration related capabilities - E2->>SMO: 3 «O1» Deliver requested data & O-DU and O-RU RF channel reconfiguration related capabilities - SMO->>ES_rApp: 4 «R1» Deliver collected configuration/measurement data - - loop RF channel reconfiguration implementation - ES_rApp->>SMO: 5 Continuous monitoring & inference - Note right of ES_rApp: Monitors: -(i) E2 node performance & energy consumption -(ii) O-RU energy consumption -(iii) Cell utilization & throughput -Determines configuration changes for RF Channel Reconfiguration. -AI/ML inference may be used. - - alt Policy path: 6a «O1» — Provide policy for RF Channel reconfiguration in specific O-RU - alt Direct configuration path: 6b «O1» — Provide configuration to activate TRx control - end - - Note right of ORN: 7 Analyze conditions/policy; decide to activate RF channel reconfiguration - Note right of ORN: 8 «OFH M-C-Plane» Configure (activate) TRx control (e.g., set antenna mask) - Note right of ORN: 9 Adjust antenna array; enter energy saving mode - - opt Deactivation requested by SMO: 10 «O1» — Provide configuration to deactivate TRx control - Note right of ORN: 11 Evaluate (policy from 6a or request from 10); decide to deactivate TRx control - Note right of ORN: 12 «OFH M-C-Plane» Configure default antenna array (to deactivate TRx control) - Note right of ORN: 13 Adjust antenna array; exit energy saving mode - end - end - -``` - -Sequence diagram titled 'RF channel reconfiguration based energy saving - rApp-based solution'. It shows interactions between an Operator/Host, Service Orchestration and Management Framework (containing Energy Saving rApp and SMO/Non-RT RIC), and O-RAN Nodes (containing E2 node(s) and O-RU node(s)). The process involves requesting data, monitoring, policy decision, and reconfiguration of TRx control. - -Figure 4.21.3.2.1-1: RF channel reconfiguration- based energy saving: rApp-based energy saving - -##### 4.21.3.2.2 Solution: rApp/xApp-based solution - -The following entities are applicable to this solution: energy saving rApp/xApp, Near-RT RIC/SMO, E2 node and O-RU node. - -A solution for RF channel reconfiguration-based energy saving implemented as a use case through an rApp/xApp-based approach, is documented in table 4.21.3.2.2-1. - -**Table 4.21.3.2.2-1: RF channel reconfiguration: rApp/xApp-based solution** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------| -| Goal | Enable RF channel reconfiguration energy saving functions in the network by means of configuration parameter change and actions controlled by Near-RT RIC and allow for AI/ML-based solutions. | | -| Actors and Roles | 1) Energy saving xApp
2) Near-RT RIC
3) Non-RT RIC/SMO
4) E2 node(s)
5) O-RU node(s) | | -| Assumptions |
  • A1 interface connectivity is established between Non-RT RIC of SMO and Near-RT RIC.
  • E2 interface connectivity is established between network functions (O-DU) and Near-RT RIC.
  • Open fronthaul M-plane interface is established between O-DU and O-RU and/or SMO and O-RU directly.
  • SMO, Near-RT RIC, and O-DU aware of O-RU capabilities.
  • Network is operational.
| | -| Pre-conditions | Operator has set the targets for energy saving in Near-RT RIC. | | -| Begins when | Operator enables RF channel reconfiguration energy saving functions, and O-DU and O-RU become operational. | | -| Alt
Step 1a (M) | SMO/Non-RT RIC consumes and analyzes the various measurement data like CM, PM, and FM data and KPIs or operator trigger (requested configuration changes). | Use case | -| Step 1b (M) | Non-RT RIC SMOF prepares A1 policy for Near-RT RIC (xApps) to optimize the RF channel reconfiguration of a specific O-RU. | O-RAN.WG2.TS.Use-Case-Requirements-R004 [50], clause 4.8.2.3.2;
Use case | -| Step 1c (M) | Non-RT RIC SMOF provides policy prepared in Step 1b, to Near-RT RIC via A1 interface. | O-RAN.WG2.TS.Use-Case-Requirements-R004 [50], clause 4.8.2.3.2;
Use case | -| Step 1d (M) | Energy saving xApp constantly monitors
  • (i) energy consumption of O-RU(s)
  • (ii) cell utilization, throughput, and related performance metrics
Near-RT RIC analyzes the A1 policy that it received from Non-RT RIC in Step 1c and the above measurement data. The xApps of Near-RT RIC prepares the E2 policy or determines the configuration changes that need to be provided to O-DU, for RF channel reconfiguration use case. AI/ML inference may be used to make the decision.
The Near-RT RIC provides the E2 policy or configuration changes to O-DU for RF channel reconfiguration of a specific O-RU. | O-RAN.WG2.TS.Use-Case-Requirements-R004 [50], clause 4.8.2.3.2;
Use case | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| -| Alt
Step 2a (M) | Energy saving xApp constantly monitors
(i) energy consumption of O-RU(s)
(ii) cell utilization, throughput, and related performance metrics
Near-RT RIC (xApp) analyzes the above measurement data and KPIs, and prepares the E2 policy or configuration changes for O-DU. | O-RAN.WG2.TS.Use-Case-Requirements-R004 [50], clause 4.8.2.3.2;
O-RAN.WG3.TS.UCR [46], clause 4.6.2;
Use case | -| Step 2b (M) | Near-RT RIC provides the policy or configuration changes (prepared in Step 2a) to O-DU via E2 interface. | O-RAN.WG3.TS.UCR [46], clause 4.6.3;
O-RAN.WG3.TS.E2SM-CCC [47], clause 8.8.2.6;
Use case | -| Step 3 (M) | O-DU analyzes the policy or configuration changes that it received either in Step 1d or 2b. Once the conditions mentioned in that policy are satisfied or based on the requested configuration changes, the O-DU decides to activate the RF channel reconfiguration feature in the O-RU. | Use case | -| Step 4 (M) | O-DU sends appropriate commands to the O-RU via fronthaul M-plane or C-plane to configure (activate) RF channel reconfiguration (TRx control) feature to the specific O-RU, i.e., O-DU configures a specific antenna mask on O-RU. | O-RAN.WG4.MP [28], clause 20.3.2.3;
O-RAN.WG4.TS.CUS.0-R004 [51], clauses 7.4.6, 16.1 and 16.2 | -| Step 5 (M) | O-RU adjusts its antenna array configuration(s) based on the O-DU provided configuration. Then the O-RU transitions to RF channel reconfiguration (TRx control) based energy saving mode. | Use case | -| Step 6 (O) | Near-RT RIC analyses the O&M data and KPIs to prepare the policy or configuration changes required for O-DU to deactivate the RF channel reconfiguration (TRx control) feature and provide them to O-DU via E2 interface. | O-RAN.WG3.TS.UCR [46], clause 4.6.3;
O-RAN.WG3.TS.E2SM-CCC [47], clause 8.8.2.6;
Use case | -| Step 7 (M) | O-DU analyzes the policy provided by Near-RT RIC in Steps 1d or 2b or configuration changes provided by Near-RT RIC in Step 6. Then the O-DU decides to deactivate the RF channel reconfiguration (TRx control) feature in the specific O-RU. | Use case | -| Step 8 (M) | O-DU sends the appropriate commands to the O-RU via fronthaul M-plane or C-plane to configure the default antenna array configuration. This is to deactivate the RF channel reconfiguration (TRx control) feature in the O-RU. | O-RAN.WG4.MP [28], clause 20.3.2.3;
O-RAN.WG4.TS.CUS.0- | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------| -| | | Related use | -| | | R004 [51], clauses 7.4.6, 16.1 and 16.2 | -| Step 9 (M) | The O-RU adjusts its antenna array configuration and exits from the energy saving mode. | Use case | -| Ends when | NF node (O-DU) and O-RU become non-operational or when the operator disables energy saving or when optimization criteria are no longer met.

Change in traffic or coverage.

The policy expires/aborts. | | -| Exceptions | O-RU/O-DU reports failure or resource is ineligible (e.g., all SSB/PRACH beams masked); xApp must retry or rollback. | | -| Post Conditions | O-RU is restored to default antenna array configuration.

SMO monitors the energy consumption status.

Near-RT RIC continues close loop monitoring of energy saving function at NF node (O-DU) and O-RU.

NF node(s) and O-RU(s) operate using the configuration provided by the energy saving xApp via Near-RT RIC. | | - -``` - -@startuml -!pragma teoz true -skinparam sequenceArrowThickness 2 -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 15 -skinparam sequenceMessageAlign center -skinparam sequenceMessageAlign center - -title RF channel reconfiguration-based energy saving - rApp/xApp based solution -Skin rose - -box "Operator" #Lightblue - Actor host as "Host" -End box - -Box "Service Orchestration and Management Framework" #gold - participant "MnS Consumer \n(RAN NF OAM SMOS)" as smo - participant "Non-RT RIC \n(rApps)" as rapp -end box - -box "O-RAN Nodes" #lightpink - participant "Near-RT RIC \n(xApps)" as xapp - participant "O-DU node(s)" as e2odu - participant "O-RU node(s)" as RU -end box - -group RF channel reconfiguration feature implementation -group Policy or configuration changes preparation for O-DU - -``` - -``` - -alt Non-RT RIC provides A1 policy to near-RT RIC based on RAN datas and KPI for O-DU to -optimize the O-RU power consumption -note over host, rapp : 1a Analyze the O&M datas (CM, PM, and FM) and KPIs or -operator trigger -rapp->rapp : 1b Prepare A1 policy for \nRF channel reconfiguration -rapp<->xapp : 1c <> Provides policy \nto near-RT RIC -note over xapp, e2odu : 1d <> Near-RT RIC monitors the KPIs, prepare and -\nprovide E2 policy or configuration changes to E2 node -else Near-RT RIC prepares the E2 policy or configuration changes to O-DU for RF channel -reconfiguration in O-RU -xapp->xapp : 2a Monitor KPIs and prepares E2 policy \nor configuration changes for -O-DU -note over xapp, e2odu : 2b <> Provides E2 policy or configuration changes to -O-DU -end alt -end group - -group O-DU activates the RF channel reconfiguration feature in a specific O-RU -note over e2odu: 3 O-DU analyze the policy or configuration changes and decide to -activate \nRF channel reconfiguration (TRx Control) feature in the specific O-RU -note over RU : 4 <> Configures (activate) \nthe RF channel -reconfiguration (TRx Control) feature -note right RU : 5 O-RU adjust antenna array configuration and \nturn off some -antenna elements (RF Channels) -note right RU : O-RU enters energy saving mode -end group -group O-DU deactivates the RF channel reconfiguration feature in a specific O-RU -opt -note over xapp, e2odu : 6 <> Near-RT RIC provides configuration changes to the -\nO-DU for deactivating the RF channel reconfiguration in O-RU -end opt -note over e2odu: 7 O-DU analyze the policy/configuration details and decide to -deactivate \nRF channel reconfiguration (TRx Control) feature in the specific O-RU -note over RU : 8 <> Configures (deactivate) \nthe RF channel -reconfiguration (TRx Control) feature -note right RU : 9 O-RU adjust antenna array configuration and \noperate with -default antenna array configuration -note right RU : O-RU exits energy saving mode -end group -end group -end loop - -@enduml - -``` - -The flow diagram of the RF channel reconfiguration using rApp/xApp-based energy saving is given in figure 4.21.3.2.2-1. - -![Sequence diagram titled 'RF channel reconfiguration-based energy saving - rApp/xApp based solution'. It shows interactions between Operator, Service Orchestration and Management Framework (MnS Consumer, Non-RT RIC), and O-RAN Nodes (Near-RT RIC, O-DU, O-RU). The process involves policy preparation, activation, and deactivation of RF channel reconfiguration features for energy saving.](4a2d4d9018b37c44a58838114803711f_img.jpg) - -The diagram illustrates the sequence of operations for RF channel reconfiguration-based energy saving. It is divided into three main phases: - -- RF channel reconfiguration feature implementation:** - - Policy or configuration changes preparation for O-DU:** - - alt** [Non-RT RIC provides A1 policy to near-RT RIC based on RAN datas and KPI for O-DU to optimize the O-RU power consumption] - - 1a Analyze the O&M datas (CM, PM, and FM) and KPIs or operator trigger - - 1b Prepare A1 policy for RF channel reconfiguration - - 1c «A1» Provides policy to near-RT RIC - - 1d «E2» Near-RT RIC monitors the KPIs, prepare and provide E2 policy or configuration changes to E2 node - - [Near-RT RIC prepares the E2 policy or configuration changes to O-DU for RF channel reconfiguration in O-RU] - - 2a Monitor KPIs and prepares E2 policy or configuration changes for O-DU - - 2b «E2» Provides E2 policy or configuration changes to O-DU - - O-DU activates the RF channel reconfiguration feature in a specific O-RU:** - - 3 O-DU analyze the policy or configuration changes and decide to activate RF channel reconfiguration (TRx Control) feature in the specific O-RU - - 4 «OFH M-Plane/C-Plane» Configures (activate) the RF channel reconfiguration (TRx Control) feature - - 5 O-RU adjust antenna array configuration and turn off some antenna elements (RF Channels) - - O-RU enters energy saving mode - - O-DU deactivates the RF channel reconfiguration feature in a specific O-RU:** - - opt** [6 «E2» Near-RT RIC provides configuration changes to the O-DU for deactivating the RF channel reconfiguration in O-RU] - - 7 O-DU analyze the policy/configuration details and decide to deactivate RF channel reconfiguration (TRx Control) feature in the specific O-RU - - 8 «OFH M-Plane/C-Plane» Configures (deactivate) the RF channel reconfiguration (TRx Control) feature - - 9 O-RU adjust antenna array configuration and operate with default antenna array configuration - - O-RU exits energy saving mode - -Sequence diagram titled 'RF channel reconfiguration-based energy saving - rApp/xApp based solution'. It shows interactions between Operator, Service Orchestration and Management Framework (MnS Consumer, Non-RT RIC), and O-RAN Nodes (Near-RT RIC, O-DU, O-RU). The process involves policy preparation, activation, and deactivation of RF channel reconfiguration features for energy saving. - -Figure 4.21.3.2.2-1: RF channel reconfiguration-based energy saving: rApp/xApp-based energy saving - -#### 4.21.3.3 Advanced Sleep Mode for network energy savings - -Advanced Sleep Mode (ASM) enables power reduction or shutdown of O-RU components such as TRX chains, digital beamformers, and associated O-RU processing resources. ASM applies for both short and long periods and can use fine-grained symbol or beam masks. ASM can be triggered or orchestrated by: - -- i. Solution: rApp-based solution (O1-based or open fronthaul M-plane control, where hybrid architecture-based deployment is supported) (clause 4.2.5.2 of [27]) -- ii. Solution: rApp/xApp-based solution (E2-based) (clause 4.6.2 of [46]) - -##### 4.21.3.3.1 Solution: rApp-based solution (O1-based) - -The following entities are applicable to this solution: energy saving rApp, Non-RT RIC/SMO, E2 node(s), and O-RU node(s). - -A solution for Advanced Sleep Mode-based energy saving, implemented as a use case through an rApp-based approach, is captured in table 4.21.3.3.1-1. - -**Table 4.21.3.3.1-1 Advanced Sleep Mode: O1-based solution (rApp-based energy saving)** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| -| Goal | Enable Advanced Sleep Mode energy saving functions in the network by means of configuration parameter change and actions controlled by Non-RT RIC and allow for AI/ML-based solutions. | | -| Actors and Roles | 1) Energy saving rApp
2) Non-RT RIC/SMO
3) E2 node(s)
4) O-RU node(s) | | -| Assumptions |
  • O1 interface connectivity is established between E2 node(s) and SMO.
  • Open FH M-plane interface is established between E2 node and O-O-RU node and/or SMO and O-RU node directly.
| | -| Pre-conditions | Operator has set the targets for Advanced Sleep Mode energy saving functions in the Non-RT RIC. | | -| Begins when | Operator intends to enable Advanced Sleep Mode energy saving functions and E2 node and O-RU node become operational. | | -| Step 1 (M) | Energy saving rApp requests to collect necessary CM, PM and FM data towards SMO/Non-RT RIC function over R1 interface. | | -| Step 2 (M) | SMO/Non-RT RIC requests data collection, including Advanced Sleep Mode (ASM) related capabilities of the E2 node(s) and O-RU(s) over O1 interface and/or open fronthaul M-plane. | O-RAN.WG4.MP [28], clauses 20.4.1 and 20.5.2;
O-RAN.WG10.OAM-Architecture [27], clause 4.2.5.2 | -| Step 3 (M) | E2 node(s) send the configuration data, configured measurement data to SMO/Non-RT RIC periodically or event based. | O-RAN.WG10.OAM-Architecture [27], clause 4.2.5.2;
Use case | -| Step 4 (M) | rApp collects the configuration data, collected measurement data for processing. | O-RAN.WG4.MP [28], clauses 20.4.1 and 20.5.2 | -| Step 5 (M) | Energy Saving rApp constantly monitors
  • (i) performance and energy consumption of the E2 node(s)
  • (ii) energy consumption of O-RU(s)
  • (iii) cell utilization and throughput metrics
rApp determines configuration changes for Advanced Sleep Mode use case. AI/ML inference may be used to make the decision. | Use case | -| Step 6a (Alt) | SMO/Non-RT RIC will provide the policy to E2 node via O1 interface for Advanced Sleep Mode in the specific O-RU. | O-RAN.WG10.OAM-Architecture [27], | - -| Use Case Stage | Evolution / Specification | <> | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------| -| | | Related use | -| | | clauses 4.2.5.2 and 5.2.1 | -| Step 6b (Alt) | SMO/Non-RT RIC will provide configuration changes to the E2 node via O1 interface to activate the Advanced Sleep Mode feature in the target O-RU. | O-RAN.WG10.OAM-Architecture [27], clauses 4.2.5.2 and 5.2.1 | -| Step 7 (M) | E2 node analyzes the conditions mentioned in the policy or configuration changes and decides to activate the Advanced Sleep Mode feature in the specific O-RU. | O-RAN.WG10.OAM-Architecture [27], clause 4.2.5.2;
Use case | -| Step 8 (M) | E2 node sends appropriate commands to the O-RU via fronthaul M-plane or C-plane to configure (activate) Advanced Sleep Mode feature to the specific O-RU, i.e., O-DU configures a specific sleep mode on O-RU. | O-RAN.WG4.MP [28], clauses 20.4 and 20.5;
O-RAN.WG4.TS.CUS.0-R004 [51], clauses 7.4.6, 16, 16.1 and 16.3 | -| Step 9 (M) | O-RU applies the sleep mode functionality based on the E2 node provided configuration, achieved through the deactivation of relevant hardware and/or software components. Then the O-RU transitions to Advanced Sleep Mode-based energy saving mode. | Use case | -| Step 10 (O) | SMO/Non-RT RIC may provide configuration changes to the E2 node via O1 interface to deactivate the Advanced Sleep Mode feature in the specific O-RU. | O-RAN.WG10.OAM-Architecture [27], clauses 4.2.5.2 and 5.2.1 | -| Step 11 (M) | E2 node analyzes the policy provided by SMO in Step 6a or configuration changes requested by SMO/Non-RT RIC in Step 10. Then the E2 node decides to deactivate the Advanced Sleep Mode feature in the specific O-RU. | O-RAN.WG10.OAM-Architecture [27], clause 4.2.5.2;
Use case | -| Step 12 (M) | E2 node sends the appropriate commands to the O-RU via fronthaul M-plane or C-plane to reactivate all its components. This is to deactivate the Advanced Sleep Mode feature in the O-RU. | O-RAN.WG4.MP [28], clauses 20.4 and 20.5;
O-RAN.WG4.TS.CUS.0-R004 [51], clauses 7.4.6, 16, 16.1 and 16.3 | -| Step 13 (M) | The O-RU reactivates the relevant hardware and/or software components that were deactivated due to the applied sleep mode in Step 9. This is to deactivate the Advanced Sleep Mode feature in the O-RU.

The O-RU exits from energy saving mode. | Use case | -| Ends when |
  • Load or coverage changes, or policy expires/aborts.
| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| |
  • O-DU and O-RU nodes become non-operational or when the operator disables the optimization functions for energy saving or when optimization criteria are no longer met.
| | -| Exceptions | O-RU/E2 node reports. | | -| Post Conditions |
  • O-RU is restored to the initial configuration.
  • SMO logs energy gain and status.
  • Non-RT RIC continues closed loop monitoring of energy saving function at E2 node and O-RU.
  • O-DU(s) and O-RU(s) operate using the configuration provided by the energy saving rApp via Non-RT RIC/SMO.
| | - -``` - -@startuml -!pragma teoz true - -' ==== Styling ==== -skinparam sequenceArrowThickness 2 -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 14 -skinparam sequenceMessageAlign center -skinparam NoteBackgroundColor #fff9e6 -skinparam NoteBorderColor #d1b77a -skinparam BoxBorderColor #888 -skinparam BoxBackgroundColor #f7f7f7 - -title Advanced Sleep Mode (ASM) based energy saving - rApp-based solution - -Skin rose - -' ==== Context & Roles ==== -box "Operator" #Lightblue - Actor Host as host -End box - -box "Service Orchestration and Management Framework" #gold - participant "Energy Saving rApp" as rApp - participant "SMO / Non-RT RIC" as smo -end box - -box "O-RAN Nodes" #lightpink - participant "E2 node(s)\n(e.g., O-DU)" as e2 - participant "O-RU node(s)" as ru -end box - -' ==== Step 1 (M) ==== -rApp -> smo : 1 <> – Request CM/PM/FM data collection - -' ==== Step 2 & 3 (M) ==== -note over smo, ru -2 <> Request data collection & O-DU and O-RU capabilities -end note -smo <- e2 : 3 <> Deliver requested data & O-DU and O-RU capabilities - -' ==== Step 4 (M) ==== - -``` - -``` - -smo -> rApp : 4 <> Deliver collected configuration/measurement data - -' ==== Step 5 (M) ==== -Loop Advanced Sleep Mode -rApp -> rApp : 5 Continuous monitoring & inference -note right of rApp -Monitors: -(i) E2 performance & energy consumption -(ii) O-RU energy consumption -(iii) Cell utilization & throughput -Determines configuration changes for Advanced Sleep Mode. -AI/ML inference may be used. -end note - -' ==== Step 6a/6b (Alt) ==== -alt Policy path - smo -> e2 : 6a <> – Provide policy for Advanced Sleep Mode in specific O-RU -else Direct configuration path - smo -> e2 : 6b <> – Provide configuration to Advanced Sleep Mode \nin -specific O-RU -end - -' ==== Step 7 (M) ==== -e2 -> e2 : 7 Analyze conditions/policy; decide to activate Advanced Sleep Mode in -specific O-RU - -' ==== Step 8 (M) ==== -e2 -> ru : 8 <> Configure (activate) sleep mode\n(e.g., set sleep -mode 1) - -' ==== Step 9 (M) ==== -ru <- ru : 9 Enter energy saving mode -' ==== Step 10 (O) ==== -Opt Deactivation requested by SMO - smo -> e2 : 10 <> – Provide configuration to deactivate Advanced Sleep Mode -end opt -' ==== Step 11 (M) ==== -e2 -> e2 : 11 Evaluate (policy from 6a or request from 10);\ndecide to deactivate -Advanced Sleep Mode -' ==== Step 12 (M) ==== -e2 -> ru : 12 <> Deactivate Advanced Sleep Mode -' ==== Step 13 (M) ==== -ru <- ru : 13 Exit energy saving mode - -end loop - -@enduml - -``` - -The flow diagram of the Advanced Sleep Mode-based energy saving using O1-based solution is given in figure 4.21.3.3.1-1. - -![Sequence diagram titled 'Advanced Sleep Mode (ASM) based energy saving - rApp-based solution'. It shows interactions between an Operator/Host, Service Orchestration and Management Framework (Energy Saving rApp, SMO / Non-RT RIC), and O-RAN Nodes (E2 node(s), O-RU node(s)). The process involves data collection, monitoring, policy determination, and activation/deactivation of sleep modes.](d379c2e6799a45841ba1304f8e6d374d_img.jpg) - -``` - -sequenceDiagram - participant Operator - participant Host - participant rApp as Energy Saving rApp - participant RIC as SMO / Non-RT RIC - participant E2 as E2 node(s) (e.g., O-DU) - participant O-RU as O-RU node(s) - - Note over rApp, RIC: Advanced Sleep Mode (ASM) based energy saving - rApp-based solution - - rApp->>RIC: 1 «R1» — Request CM/PM/FM data collection - RIC->>E2: 2 «O1» Request data collection & O-DU and O-RU capabilities - E2->>RIC: 3 «O1» Deliver requested data & O-DU and O-RU capabilities - RIC->>rApp: 4 «R1» Deliver collected configuration/measurement data - - loop Advanced Sleep Mode - Note over rApp: 5 Continuous monitoring & inference - Note over rApp: Monitors: -(i) E2 performance & energy consumption -(ii) O-RU energy consumption -(iii) Cell utilization & throughput -Determines configuration changes for Advanced Sleep Mode. -AI/ML inference may be used. - - alt Policy path - rApp->>E2: 6a «O1» — Provide policy for Advanced Sleep Mode in specific O-RU - else Direct configuration path - rApp->>E2: 6b «O1» — Provide configuration to Advanced Sleep Mode in specific O-RU - end - - Note over E2: 7 Analyze conditions/policy; decide to activate Advanced Sleep Mode in specific O-RU - E2->>O-RU: 8 «OFH M-C-Plane» Configure (activate) sleep mode (e.g., set sleep mode 1) - O-RU->>E2: 9 Enter energy saving mode - - alt Deactivation requested by SMO - rApp->>E2: 10 «O1» — Provide configuration to deactivate Advanced Sleep Mode - end - - Note over E2: 11 Evaluate (policy from 6a or request from 10); decide to deactivate Advanced Sleep Mode - E2->>O-RU: 12 «OFH M-C-Plane» Deactivate Advanced Sleep Mode - O-RU->>E2: 13 Exit energy saving mode - end - -``` - -Sequence diagram titled 'Advanced Sleep Mode (ASM) based energy saving - rApp-based solution'. It shows interactions between an Operator/Host, Service Orchestration and Management Framework (Energy Saving rApp, SMO / Non-RT RIC), and O-RAN Nodes (E2 node(s), O-RU node(s)). The process involves data collection, monitoring, policy determination, and activation/deactivation of sleep modes. - -**Figure 4.21.3.3.1-1: Advanced Sleep Mode-based energy saving (method #1): rApp-based energy saving** - -##### **4.21.3.3.2 Solution: rApp/xApp-based solution** - -The following entities are applicable to this solution: energy saving rApp/xApp, Near-RT RIC/SMO, E2 node and O-RU node. - -A solution for Advanced Sleep Mode-based energy saving implemented as a use case through an rApp/xApp-based approach, is documented in table 4.21.3.3.2-1. - -**Table 4.21.3.3.2-1: Advanced Sleep Mode: rApp/xApp-based solution** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Enable Advanced Sleep Mode energy saving functions in the network by means of configuration parameter change and actions controlled by Near-RT RIC and allow for AI/ML-based solutions. | | -| Actors and Roles | 1) Energy saving xApp
2) Near-RT RIC
3) Non-RT RIC/SMO
4) E2 node (s)
5) O-RU node (s) | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| -| Assumptions |
  • A1 interface connectivity is established between Non-RT RIC of SMO and Near-RT RIC.
  • E2 interface connectivity is established between network functions (O-DU) and Near-RT RIC.
  • Open fronthaul M-plane interface is established between O-DU and O-RU and/or SMO and O-RU directly.
  • SMO, Near-RT RIC, and O-DU aware of O-RU capabilities.
  • Network is operational.
| | -| Pre-conditions | Operator has set the targets for energy saving functions in Near-RT RIC. | | -| Begins when | Operator enables the optimization functions for Advanced Sleep Mode energy saving functions, and O-DU and O-RU become operational. | | -| Alt
Step 1a (M) | SMO consumes and analyzes the various measurement data like CM, PM and FM data and KPIs or operator trigger (requested configuration changes). | Use case | -| Step 1b (M) | Non-RT RIC SMOF prepares A1 policy for Near-RT RIC (xApps) to optimize the Advanced Sleep Mode of a specific O-RU. | O-RAN.WG2.TS.Use-Case-Requirements-R004 [50], clause 4.8.2.3.2;

Use case | -| Step 1c (M) | Non-RT RIC SMOF provides policy prepared in Step 1b, to Near-RT RIC via A1 interface. | O-RAN.WG2.TS.Use-Case-Requirements-R004 [50], clause 4.8.2.3.2;

Use case | -| Step 1d (M) |

Energy saving xApp constantly monitors

  • (i) energy consumption of O-RU(s)
  • (ii) cell utilization, throughput, and related performance metrics

Near-RT RIC analyzes the A1 policy that it received from Non-RT RIC in Step 1c and the above measurement data. The xApps of Near-RT RIC function prepares the E2 policy or determines the configuration changes that need to be provided to O-DU, for Advanced Sleep Mode use case. AI/ML inference may be used to make the decision.

The Near-RT RIC provides the E2 policy or configuration changes to O-DU for Advanced Sleep Mode of a specific O-RU.

| O-RAN.WG2.TS.Use-Case-Requirements-R004 [50], clause 4.8.2.3.2;

Use case | -| Alt
Step 2a (M) |

Energy saving xApp constantly monitors

  • (i) energy consumption of O-RU(s)
  • (ii) cell utilization, throughput, and related performance metrics

Near-RT RIC (xApp) analyzes the above measurement data and KPIs, and prepares the E2 policy or configuration changes for O-DU.

| O-RAN.WG2.TS.Use-Case-Requirements-R004 [50], clause 4.8.2.3.2;

O-RAN.WG3.TS.UCR-R004 [46], clause 4.6.2;

Use case | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------| -| Step 2b (M) | Near-RT RIC provides the policy or configuration changes (prepared in Step 2a to O-DU via E2 interface. | O-RAN.WG3.TS.UCR-R004 [46], clause 4.6.2;
O-RAN.WG3.TS.E2SM-CCC [47], clause 8.8.2.6;
Use case | -| Step 3 (M) | O-DU analyzes the policy or configuration changes that it received either in Step 1d or 2b. Once the conditions mentioned in that policy are satisfied or based on the requested configuration changes, the O-DU decides to activate the Advanced Sleep Mode feature in the O-RU. | Use case | -| Step 4 (M) | O-DU sends appropriate commands to the O-RU via fronthaul M-plane or C-plane to configure (activate) Advanced Sleep Mode feature to the specific O-RU, i.e., O-DU configures a specific sleep mode on O-RU. | O-RAN.WG4.MP [28], clauses 20.4 and 20.5;
O-RAN.WG4.TS.CUS.0-R004 [51], clauses 7.4.6, 16, 16.1 and 16.3 | -| Step 5 (M) | O-RU apply the sleep mode functionality based on the O-DU provided configuration, achieved through the deactivation of relevant hardware and/or software components. Then the O-RU transitions to Advanced Sleep Mode-based energy saving mode. | Use case | -| Step 6 (O) | Near-RT RIC analyses the O&M data and KPIs to prepare configuration changes required for O-DU to deactivate the Advanced Sleep Mode feature and provide them to O-DU via E2 interface. | O-RAN.WG3.TS.UCR-R004 [46], clause 4.6.2;
O-RAN.WG3.TS.E2SM-CCC [47], clause 8.8.2.6;
Use case | -| Step 7 (M) | O-DU analyzes the policy provided by Near-RT RIC in Steps 1d or 2b or configuration changes provided by Near-RT RIC in Step 6. Then the O-DU decides to deactivate the Advanced Sleep Mode feature in the specific O-RU. | Use case | -| Step 8 (M) | O-DU sends the appropriate commands to the O-RU via fronthaul M-plane or C-plane to deactivate the sleep mode. This is to deactivate the Advanced Sleep Mode feature in the O-RU. | O-RAN.WG4.MP [28], clauses 20.4 and 20.5;
O-RAN.WG4.TS.CUS.0-R004 [51], clauses 7.4.6, 16, 16.1 and 16.3 | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 9 (M) |

The O-RU reactivates the relevant hardware and/or software components that were deactivated due to the applied sleep mode in Step 5. This is to deactivate the Advanced Sleep Mode feature in the O-RU.

The O-RU exits from energy saving mode.

| Use case | -| Ends when |

E2 node and O-RU become non-operational or when the operator disables the optimization functions for energy saving or when optimization criteria are no longer met.

Change in traffic or coverage

The policy expires/aborts.

| | -| Exceptions | O-RU/O-DU reports failure or resource is ineligible (e.g., all SSB/PRACH beams masked); rApp must retry or rollback. | | -| Post Conditions |

O-RU is restored to default antenna array configuration.

SMO monitors the energy consumption status.

Near-RT RIC continues close loop monitoring of energy saving function at E2 node and O-RU.

E2 node(s) and O-RU(s) operate using the configuration provided by the energy saving xApp via Near-RT RIC.

| | - -``` - -@startuml -!pragma teoz true -skinparam sequenceArrowThickness 2 -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 15 -skinparam sequenceMessageAlign center -skinparam sequenceMessageAlign center - -title Advance Sleep Mode based energy saving - rApp/xApp based solution -Skin rose - -box "Operator" #Lightblue - Actor host as "Host" -End box - -Box "Service Orchestration and Management Framework" #gold - participant "MnS Consumer \n(RAN NF OAM SMOS)" as smo - participant "non-RT RIC \n(rApps)" as rapp -end box - -box "O-RAN Nodes" #lightpink - participant "near-RT RIC \n(xApps)" as xapp - participant "O-DU node(s)" as e2odu - participant "O-RU node(s)" as RU -end box - -group Advance Sleep Mode - -``` - -``` - -group Policy or configuration changes preparation for O-DU -alt Non-RT RIC provides A1 policy to near-RT RIC based on RAN datas and KPI for O-DU to -optimize the O-RU power consumption -note over host, rapp : 1a Analyze the O&M datas (CM, PM, and FM) and KPIs or -operator trigger -rapp->rapp : 1b Prepare A1 policy for \nAdvance Sleep Mode -rapp->xapp : 1c <> Provides policy \nto near-RT RIC -note left xapp : Near-RT RIC prepares E2 policy \nor configuration changes -note over xapp, e2odu : 1d <> Provides E2 policy or configuration changes to -O-DU -else Near-RT RIC prepares the E2 policy or configuration changes to O-DU for Advance -Sleep Mode in O-RU -xapp->xapp : 2a Prepares E2 policy or \nconfiguration changes for O-DU -note over xapp, e2odu : 2b <> Provides E2 policy or configuration changes to -O-DU -end alt -end group - -group O-DU activates the Advance Sleep Mode feature in a specific O-RU -note over e2odu: 3 O-DU analyzes the policy or configuration changes and decides -\nto activate Advance Sleep Mode feature in the specific O-RU -note over RU : 4 <> Configures (activate) \nthe Advance Sleep -Mode feature -note right RU : 5 O-RU activates Advanced Sleep Mode -note right RU : O-RU enters energy saving mode -end group -group O-DU deactivates the Advance Sleep Mode feature in a specific O-RU -opt -note over xapp, e2odu : 6 <> Near-RT RIC provides configuration changes to the -\nO-DU for deactivating the Advance Sleep Mode in O-RU -end opt -note over e2odu: 7 O-DU analyzes the policy/configuration details and decides to -\ndeactivate Advanced Sleep Mode feature in the specified O-RU -note over RU : 8 <> Configures (deactivates) \nthe Advance -Sleep Mode feature -note right RU : 9 O-RU deactivates Advanced Sleep Mode -note right RU : O-RU exits energy saving mode -end group -end loop - -@enduml - -``` - -The flow diagram of the Advanced Sleep Mode using rApp/xApp based energy saving is given in figure 4.21.3.3.2-1. - -![Sequence diagram titled 'Advance Sleep Mode based energy saving - rApp/xApp based solution'. It shows the interaction between an Operator Host, Service Orchestration and Management Framework (MnS Consumer, non-RT RIC), and O-RAN Nodes (near-RT RIC, O-DU, O-RU). The process involves policy preparation, activation, and deactivation of Advance Sleep Mode.](debc37b54fe8de17b46dec2bcab04ed5_img.jpg) - -``` - -sequenceDiagram - participant Operator Host - participant SMO as Service Orchestration and Management Framework - subgraph O-RAN Nodes - participant near-RT RIC - participant O-DU - participant O-RU - end - - Note left of SMO: Advance Sleep Mode - alt Policy or configuration changes preparation for O-DU: [Non-RT RIC provides A1 policy to near-RT RIC based on RAN datas and KPI for O-DU to optimize the O-RU power consumption] - Note right of SMO: 1a Analyze the O&M datas (CM, PM, and FM) and KPIs or operator trigger - Note right of SMO: 1b Prepare A1 policy for Advance Sleep Mode - Note right of SMO: 1c «A1» Provides policy to near-RT RIC - Note right of near-RT RIC: Near-RT RIC prepares E2 policy or configuration changes - Note right of near-RT RIC: 1d «E2» Provides E2 policy or configuration changes to O-DU - Note right of near-RT RIC: [Near-RT RIC prepares the E2 policy or configuration changes to O-DU for Advance Sleep Mode in O-RU] - Note right of O-DU: 2a Prepares E2 policy or configuration changes for O-DU - Note right of O-DU: 2b «E2» Provides E2 policy or configuration changes to O-DU - end - - Note right of O-RU: O-DU activates the Advance Sleep Mode feature in a specific O-RU - Note right of O-DU: 3 O-DU analyzes the policy or configuration changes and decides to activate Advance Sleep Mode feature in the specific O-RU - Note right of O-DU: 4 «OFH M-Plane/C-Plane» Configures (activate) the Advance Sleep Mode feature - Note right of O-RU: 5 O-RU activates Advanced Sleep Mode - Note right of O-RU: O-RU enters energy saving mode - - Note right of O-RU: O-DU deactivates the Advance Sleep Mode feature in a specific O-RU - alt opt: 6 «E2» Near-RT RIC provides configuration changes to the O-DU for deactivating the Advance Sleep Mode in O-RU - Note right of O-DU: 7 O-DU analyzes the policy/configuration details and decides to deactivate Advanced Sleep Mode feature in the specified O-RU - Note right of O-DU: 8 «OFH M-Plane/C-Plane» Configures (deactivates) the Advance Sleep Mode feature - Note right of O-RU: 9 O-RU deactivates Advanced Sleep Mode - Note right of O-RU: O-RU exits energy saving mode - -``` - -Sequence diagram titled 'Advance Sleep Mode based energy saving - rApp/xApp based solution'. It shows the interaction between an Operator Host, Service Orchestration and Management Framework (MnS Consumer, non-RT RIC), and O-RAN Nodes (near-RT RIC, O-DU, O-RU). The process involves policy preparation, activation, and deactivation of Advance Sleep Mode. - -Figure 4.21.3.3.2-1: Advanced Sleep Mode-based energy saving : rApp/xApp-based energy saving - -#### 4.21.3.4 External power source coordination-based energy saving - -External power source coordination-based energy saving is for SMO framework to collect the energy source and supply information (either by operator input or available to SMO framework from external producers or exposed via O-RU by energy supplier in an operator specific implementation) along with other network data. The SMO framework may use those data to configure appropriate energy saving method in O-RU according to the type of energy source and its supply. 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 analyze energy sources and their supply information like capacity and then activate the appropriate energy saving in O-RU to prolong its services. rApp-based solution (O1-based) is described in the following sub-clause. - -##### 4.21.3.4.1 Solution: rApp-based solution (O1-based) - -The following entities are applicable to this solution: energy saving rApp, Non-RT RIC/SMO framework, O-DU node(s) and O-RU node(s). - -A solution for external power source coordination-based energy saving: use case through rApp-based solution with energy source and supply information configured by operator and/or exposed through O-RU is captured in table 4.21.3.4.1-1. - -**Table 4.21.3.4.1-1: External power source coordination-based energy saving: AI/ML inference via Non-RT RIC** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------| -| Goal | Enable external power source coordination-based energy saving functions in the network by means of configuration parameter change and actions controlled by Non-RT RIC and allow for AI/ML-based solutions. | | -| Actors and Roles |
  • 1) Energy saving rApp
  • 2) Non-RT RIC/SMO framework (Non-RT RIC, external producers, DME SMOS, PMI SMOS, RAN NF SMOS, and O-RU controller)
  • 3) O-DU node
  • 4) O-RU node
  • 5) Energy supplier control panel
  • 6) Operator
| | -| Assumptions |
  • • O1 interface connectivity is established between network functions (O-DU) and SMO.
  • • Open Fronthaul (FH) M-plane interface is established between O-DU and O-RU and/or SMO and O-RU directly.
  • • Network is operational.
  • • External control panel (energy supplier) can expose the energy source and supply information to the operator.
  • • O-RU can collect the energy source and supply information that is supplied by the energy operator based on operator specific implementation.
  • • O-DU and O-RU support one of the energy saving methods described in clause 16 of O-RAN.WG4.TS.CUS.0-R004 [51] and clause 20 of O-RAN.WG4.MP [28].
|

O-RAN.WG4.MP [28], clause 20;

O-RAN.WG4.TS.CUS.0-R004 [51], clause 16;

Use case

| -| Pre-conditions |
  • • Operator has set the targets for external power source coordination-based energy saving functions in the Non-RT RIC.
  • • Operator may use one of the following steps to configure the energy source and supply information to SMO framework.
    • ○ Use the external producer termination of SMO framework to supply the energy source and supply information, where DME SMOS can be utilized for data exposure.
    • ○ Configures external power source information (energy source and supply information provided by energy suppliers) through a dedicated rApp that is responsible for external power source coordination-based energy saving, where DME SMOS can be utilized for data exposure.
    • ○ Configures the external power source information (energy source and supply information) to the RAN NF OAM SMOS, where DME SMOS can be utilized for data exposure.
|

3GPP TS 28.310 [43], clauses 5.1.6.2, 5.2.5.1, 8.3.1, 8.3.2, and 8.3.3 and Annex C.1

| - -| Use Case Stage | Evolution / Specification | <>
Related use | -|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Begins when | Operator enables the optimization functions for external power source coordination-based energy saving functions and NFs (O-DU and O-RU) under operational. | | -| Step 1a (Alt) | Hierarchical deployment
O-RU exposes capabilities related to the external power source coordination-based energy saving feature via FH M-plane. | Use case | -| Step 1b (M) | O-DU exposes its capabilities along with associated O-RU capabilities to RAN NF OAM SMOS of SMO framework via O1 interface. | Use case | -| Step 2 (Alt) | Hybrid deployment
O-RU exposes capabilities related to the external power source coordination-based energy saving feature to the SMO via FH M-plane. | Use case | -| Step 3 (O) | Energy supplier exposes the energy source and supply information to O-RU using operator specific implementation. | Use case | -| Alt
Step 4a (O) | Hierarchical deployment
O-RU exposes the energy source and supply information (that it got from energy supplier as in Step 3) to O-DU via FH M-plane. | Use case | -| Step 4b (M) | O-DU forward the energy source and supply information (that it received from O-RU via FH M-plane in Step 4a) to RAN NF OAM SMOS of SMO framework via O1 interface. | Use case | -| Alt
Step 5 (O) | Hybrid deployment
O-RU exposes capabilities related to the external power source coordination-based energy saving feature to the SMO via FH M-plane. | Use case | -| Alt
Step 6a (M) | Energy saving rApp constantly monitors the following by leveraging the SMO framework,
  • (i) performance and energy consumption of the O-DU(s)
  • (ii) energy consumption of O-RU(s)
  • (iii) cell utilization and throughput metrics
  • (iv) external power source(s) and capacity i.e., energy source and supply information.
rApp determines policy or configuration changes for external power source coordination-based energy saving use case. AI/ML inference may be used to make the decision.
Non-RT RIC SMOF (rApp) can provision the policy through the PMI SMOS to provide the policy or configuration changes to RAN NF OAM SMOS.
Non-RT RIC SMOF (rApp) may use the PMI SMOS to provision the policy or configuration changes to the RAN NF OAM SMOS based on the above data. | Use case | -| Step 6b (M) | The operator may alternatively use the PMI SMOS to provision the energy saving policy based on the performance data mentioned in Step 7a and energy source and supply information. | Use case | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| -| Step 6c (O) | SMO framework may use appropriate SMOS to decide to switch power sources depending on various KPIs and then activate appropriate energy saving method(s) in O-RU. | Use case | -| Alt
Step 7a (O) | Hierarchical deployment

SMO framework uses the RAN NF SMOS to provide the energy source switching command (configuration changes) to the O-DU via O1 interface, to enable O-DU to forward the energy source switching command to O-RU via FH M-plane. | Use case | -| Step 7b (O) | The O-DU analyzes the configuration changes that it received in the command sent by the SMO in Step 8a.

The O-DU sends an appropriate RPC command to the O-RU via FH M-plane, where it contains the energy source switching command that is to be forwarded to the energy supplier control panel. | Use case | -| Step 7c (O) | The O-RU forwards the command that it received from O-DU in Step 8b to the energy supplier control panel to switch the energy source based on the operator specific implementation. | Use case | -| Alt
Step 8a (M) | Energy saving rApp constantly monitors the following by leveraging the SMO framework,

  • (i) performance and energy consumption of the O-DUs
  • (ii) energy consumption of O-RU(s)
  • (iii) cell utilization and throughput metrics
  • (iv) external power source(s) and capacity i.e., energy source and supply information.

rApp determines policy and/or configuration changes for external power source coordination-based energy saving use case. AI/ML inference may be used to make the decision.

rApp may provision the policy through PMI SMOS to RAN NF OAM SMOS. Alternatively, the operator may use the PMI SMOS to provision the energy saving policy based on the performance data mentioned in Step 2a and energy source and supply information.

SMO uses the RAN NF OAM SMOS to provide energy saving policy or the configuration changes to O-DU via O1 interface. | O-RAN.WG10.OAM-Architecture [27], clause 5.2.1;

O-RAN.WG10.TS.O1-Interface [44] | -| Step 8b (M) | O-DU analyzes the policy, or the configuration changes provided by SMO in Step 9a. If the conditions mentioned in the policy or configuration changes provided in Step 9a are met, the O-DU sends FH C-plane and/or M-plane commands to activate an appropriate energy saving feature in O-RU, based on its capability. For example, Advanced Sleep Mode, TRx control, deep hibernate etc. | O-RAN.WG4.MP [28], clause 20;

O-RAN.WG4.TS.CUS.O-R004 [51], clause 16;

Use case | -| Alt
Step 9a (O) | Hybrid Deployment

SMO (O-RU controller) sends an appropriate RPC command to the O-RU via OFH M-plane for switching the energy source. | Use case | -| Step 9b (O) | The O-RU forwards the command that it received from SMO (O-RU controller) via FH M-plane in Step 10a to the energy supplier control | Use case | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------| -| | panel to switch the energy source based on the operator's specific implementation. | | -| Step 10a (M) | SMO uses the RAN NF OAM SMOS to configure the O-DU via O1 interface, to make it aware of the energy saving feature activation in the specific O-RU. O-DU performs necessary configurations to the O-RU via fronthaul interface. For example, CUS plane to be terminated if the deep hibernate based energy saving to be activated in the O-RU in Step 11b. | O-RAN.WG10.OAM-Architecture [27];

Use case | -| Step 10b (M) | SMO (O-RU controller) configures the O-RU via fronthaul M-plane with an appropriate energy saving method supported by O-RU. For example, energy saving features such as M-plane controlled TRx control and deep hibernate. | O-RAN.WG4.MP [28], clause 20;

Use case | -| Step 11 (M) | When energy source and supply restore to a default one, the O-DU may deactivate the energy saving feature in the O-RU via fronthaul M-plane or C-plane. This is based on the operator trigger or configuration changes (trigger) from the SMO framework or based on the SMO provided policy in Step 9a. | Use case | -| Ends when | Energy supply information is not available, and O-RU becomes non-operational or when the operator disables the optimization functions for external power source coordination-based energy saving. | | -| Exceptions | None. | | -| Post Conditions | Non-RT RIC continues close loop monitoring of external power sources, energy supply information and energy saving function at O-DU and O-RU. O-DU (s) and O-RU(s) operate using the configuration provided by the energy saving rApp via Non-RT RIC/SMO framework. | | - -``` - -@startuml -!pragma teoz true - -skinparam sequenceArrowThickness 2 -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 15 -skinparam sequenceMessageAlign center -skinparam sequenceMessageAlign center - -title Hierarchical O-RU management procedure - -Title External power source coordination - -Skin rose - -``` - -``` - -box "Operator" #Lightblue - Actor host as "Energy source and supply information" -End box - -Box "Service Orchestration and Management Framework" #gold -participant "MnS Producer \n(External producers)" as extp -participant "DME SMOS" as dme -participant "non-RT RIC \n(rApps)" as rapp -participant "PMI SMOS" as pmi -participant "MnS Consumer \n(RAN NF OAM SMOS)" as smo -participant "O-RU Controller \n(Netconf client)" as smoru -end box - -box "O-RAN NF" #lightpink - box "O-DU" #lightcyan - participant "MnS Producer \n(MnF of O-DU)" as mnfodu - participant "O-RU Controller \n (Netconf client)\n(O-DU)" as client - end box - participant "NETCONF Server/\n(O-RU)" as RU -end box - -Note over host, RU -Pre-condition: - -1. External control panel (energy supplier) can provide the energy source and supply information to operator -2. Operator can configure the energy source and supply information to SMO Framework -3. O-RU has the connection with external power source control unit (Operator specific implementation) -4. External power source control unit can expose the energy source and supply information to O-RU - -End note - -Group Capability exposure -Alt Hierarchical deployment - -client<-RU : [1a] <> Expose the external power source coordination \nfeature capability and associated parameters - -smo<-mnfodu : [1b] <> O-DU forwards the O-RU capabilities - -Else Hybrid deployment - -``` - -``` - -smoru<-RU : [2] <> Expose the external power source coordination feature -capability and associated parameters - -End Alt - -End group - -group Exposing external power source information (Energy source and supply information) -availability to SMO Framework through O-RU -opt -RU<-RU : [3] Collect the external power source \ninformation from energy supplier -alt Hierarchical deployment -client<-RU : [4a] <> Expose the external power source information \neither -through file management or NETCONF Yang -smo<-mnfodu : [4b] <> O-DU forwards the external power source information -Else Hybrid deployment -smoru<-RU : [5] <> Expose the external power source information either -through file management or NETCONF Yang -end opt -end group - -group SMO analyzes the energy source and supply information and perform actions based -them -alt rApp can create a policy and provision \nthrough PMI to RAN NF OAM SMOS -note over rapp,smo: [6a] rApp prepares a policy and provision through \n\tPMI SMOS to RAN -NF OAM SMOS -else PMI provision operator provided \npolicy to RAN NF OAM SMOS -note over pmi,smo: [6b] Energy saving policy based on energy \nsupply and energy source -information -end alt -opt -note over rapp, smoru : [6c] Decide to switch power sources \nand/or activate appropriate -ES features -end opt -end group - -Group External power source coordination based energy saving implementation -Alt Hierarchical deployment -opt Switch power supply source -note over pmi, mnfodu : [7a] <> Provide policy or configuration changes to O-DU for -switching energy source -note over mnfodu, client : Analyze the configuration changes -client->RU : [7b] <> Sends the energy source \nswitching command for control -panel - -``` - -``` - -note left RU : [7c] O-RU forward the power source switching \ncommand and/or implement -requested ES - -end opt - -group Energy saving activation based on energy source and supply information - -smo->mnfodu : [8a] <> Provide ES policy or configures O-DU -note over mnfodu, client : Analyze the policy or configuration changes -client->RU : [8b] <> Activate appropriate ES in \nO-RU or O-RU shutdown -end group - -else Hybrid deployment - -opt Switch power supply source - -smoru->RU : [9a] <> Configures O-RU to switch power supply -note left RU : [9b] O-RU forward the power source switching \ncommand and/or implement -requested ES - -end opt - -group Energy saving activation based on energy source and supply information - -smoru->mnfodu : [10a] <> Updates O-DU about the energy saving \nfeature activation in -the specific O-RU -note over mnfodu, client : Configures O-RU with necessary changes -smoru->RU : [10b] <> Activate appropriate ES in O-RU or O-RU shutdown -end group - -end alt - -note over host, RU : [11] End energy saving when the energy source and supply restored to -default one - -end group - -@enduml - -``` - -The flow diagram of the external power source coordination-based energy saving using O1-based solution with energy source and supply information configured by the operator and exposed through O-RU is given in figure 4.21.3.4.1-1. - -![Sequence diagram titled 'External power source coordination' showing interactions between Operator, Service Orchestration and Management Framework (SMO), O-DU, and O-RAN NF (O-RU).](acbfa72d71d68d0c0cfa9a65623a2dc1_img.jpg) - -The diagram illustrates the sequence of interactions for external power source coordination. It is divided into three main phases: - -- Pre-condition:** - - External control panel (energy supplier) can provide the energy source and supply information to operator - - Operator can configure the energy source and supply information to SMO Framework - - O-RU has the connection with external power source control unit (Operator specific implementation) - - External power source control unit can expose the energy source and supply information to O-RU -- Capability exposure:** - - [Hierarchical deployment]:** - - [1a] eFH M-Plane: Expose the external power source coordination feature capability and associated parameters (O-DU to O-RU) - - [1b] O-DU forwards the O-RU capabilities (O-RU to O-DU) - - [Hybrid deployment]:** - - [2] eFH M-Plane: Expose the external power source coordination feature capability and associated parameters (O-DU to O-RU) -- Exposing external power source information (Energy source and supply information) availability to SMO Framework through O-RU:** - - [3] Collect the external power source information from energy supplier (O-RU to O-DU) - - [Hierarchical deployment]:** - - [4a] eFH M-Plane: Expose the external power source information either through file management or NETCONF Yang (O-DU to O-RU) - - [4b] O-DU forwards the external power source information (O-RU to O-DU) - - [Hybrid deployment]:** - - [5] eFH M-Plane: Expose the external power source information either through file management or NETCONF Yang (O-DU to O-RU) -- SMO analyzes the energy source and supply information and perform actions based them:** - - [App can create a policy and provision through PM1 to RAN NF OAM SMOS]:** - - [6a] App prepares a policy and provision through PM1 SMOS to RAN NF OAM SMOS - - [PM1 provision operator provided policy to RAN NF OAM SMOS]:** - - [6b] Energy saving policy based on energy supply and energy source information - - [opt]:** - - [6c] Decide to switch power sources and/or activate appropriate ES features -- External power source coordination based energy saving implementation:** - - [Hierarchical deployment]:** - - [opt: Switch power supply source]:** - - [7a] Provide policy or configuration changes to O-DU for switching energy source - - Analyze the configuration changes (O-DU internal) - - [7b] eFH M-Plane: Sends the energy source switching command for control panel (O-DU to O-RU) - - [7c] O-RU forward the power source switching command and/or implement requested ES (O-RU internal) - - [Energy saving activation based on energy source and supply information]:** - - [8a] Provide ES policy or configures O-DU - - Analyze the policy or configuration changes (O-DU internal) - - [8b] eFH M-Plane: Activate appropriate ES in O-RU or O-RU shutdown (O-DU to O-RU) - - [Hybrid deployment]:** - - [opt: Switch power supply source]:** - - [9a] eFH M-Plane: Configures O-RU to switch power supply (O-DU to O-RU) - - [9b] O-RU forward the power source switching command and/or implement requested ES (O-RU internal) - - [Energy saving activation based on energy source and supply information]:** - - [10a] Updates O-DU about the energy saving feature activation in the specific O-RU - - Configures O-RU with necessary changes (O-DU internal) - - [10b] eFH M-Plane: Activate appropriate ES in O-RU or O-RU shutdown (O-DU to O-RU) -- [11] End energy saving when the energy source and supply restored to default one:** (O-RU to O-DU) - -Sequence diagram titled 'External power source coordination' showing interactions between Operator, Service Orchestration and Management Framework (SMO), O-DU, and O-RAN NF (O-RU). - -Figure 4.21.3.4.1-1: External power source coordination-based energy saving: AI/ML inference via Non-RT RIC - -#### 4.21.3.5 PA power optimization-based energy saving - -Power amplifier optimization-based energy saving (maximum output power control) is for SMO framework to collect the network data and KPIs from various network functions. By leveraging this information, the SMO can dynamically prepare the policy 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 parameters according to the maximum output power configured by O-DU. This could result in the O-RU energy saving as the power amplifier is a major power consuming component of O-RU. - -##### 4.21.3.5.1 Solution: rApp-based solution (O1-based) - -The following entities are applicable to this solution: energy saving rApp, Non-RT RIC/SMO framework, O-DU node, and O-RU node. - -A solution for PA power optimization-based energy saving: use case through rApp-based solution is captured in table 4.21.3.5.1-1. - -**Table 4.21.3.5.1-1: PA power optimization: AI/ML inference via Non-RT RIC** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| -| Goal | Enable energy saving by optimizing the PA operating region through configuration changes controlled by Non-RT RIC, with support for AI/ML-based solution. | | -| Actors and Roles | 1) Energy saving rApp
2) Non-RT RIC/SMO framework
3) O-DU node
4) O-RU node | | -| Assumptions |
  • O1 interface connectivity is established between network functions (O-DU) and SMO.
  • Open FH M-plane interface is established between O-DU and O-RU and/or SMO and O-RU directly.
  • SMO performs CM, FM, and PM subscriptions to O-DU and O-RU.
  • O-DU performs the CM, FM, and PM subscriptions to O-RU.
  • Network is operational.
| | -| Pre-conditions | Operator has set the targets for energy saving functions in the Non-RT RIC. | | -| Begins when | Operator enables the optimization functions for PA power optimization energy saving functions and NF and O-RU become operational. | | -| Step 1a (M) | Hierarchical deployment
O-DU acting as the O-RU controller retrieves the PA power optimization (maximum output power control) related capabilities from the O-RU via fronthaul M-plane. | O-RAN.WG4.MP [28], clause 20.6. | -| Step 1b (M) | RAN NF SMOS of SMO framework retrieves the O-DU capabilities via O1 interface along with the associated O-RU capabilities that the O-DU retrieved in Step 1a. | Use case | -| Step 2a (M) | Hybrid deployment
RAN NF SMOS of SMO framework retrieves the O-DU capabilities via O1 interface. This enables SMO to determine applicable optimization constraints or actions. | Use case | -| Step 2b (M) | O-RU controller (can be part of the RAN NF SMOS) of SMO framework retrieves the PA power optimization (maximum output power control) related capabilities from the O-RU via fronthaul M-plane. | O-RAN.WG4.MP [28], clause 20.6. | -| Step 3 (M) | SMO framework uses appropriate SMOS(s) to analyze the RAN data and KPIs or operator trigger (requested configuration changes), and prepares policies or configuration changes for O-DU. | Use case | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------| -| | | Related use | -| Step 4a (Alt) | SMO framework may use the RAN NF SMOS to provide the policy to O-DU via O1 interface for PA power optimization in the specific O-RU. | O-RAN.WG10.OAM-Architecture [27], clause 5.2.1 | -| Step 4b (Alt) | SMO framework may use the RAN NF SMOS to provide configuration changes to the O-DU via O1 interface to activate the PA power optimization feature in the specific O-RU. | O-RAN.WG10.OAM-Architecture [27], clause 5.2.1 | -| Step 5 (M) | O-DU analyzes the conditions mentioned in the policy or configuration changes and decides to activate the PA power optimization feature in the specific O-RU. | Use case | -| Step 6 (M) | O-DU sends appropriate commands to the O-RU via fronthaul M-plane or C-plane to configure the target maximum output power to the specific O-RU. | O-RAN.WG4.MP [28], clause 20.6. | -| Step 7 (M) | O-RU adjusts the PA parameters based on the maximum output power configured by the O-DU. Then the O-RU transitions to (PA power optimization) energy saving mode. This is to reduce PA power consumption, thereby improving the O-RU energy efficiency. | Use case | -| Step 8 (O) | SMO framework may use the RAN NF SMOS to provide configuration changes to the O-DU via O1 interface to deactivate the PA power optimization feature in the specific O-RU. | O-RAN.WG10.OAM-Architecture [27], clause 5.2.1 | -| Step 9 (M) | O-DU analyzes the policy provided by SMO framework in Step 4a or configuration changes requested by RAN NF OAM SMOS of SMO framework in Step 8. Then the O-DU decides to deactivate the PA power optimization feature in the specific O-RU, i.e., O-DU configures the nominal output power to the O-RU. | Use case | -| Step 10 (M) | O-DU sends the appropriate commands to the O-RU via fronthaul M-plane or C-plane to configure the nominal output power. This is to deactivate the PA power optimization feature in the O-RU. | O-RAN.WG4.MP [28], clause 20.6. | -| Step 11 (M) | The O-RU adjusts its PA parameters according to the nominal output power configured by the O-DU in Step 10 and exits from the energy saving mode. | Use case | -| Ends when | O-DU and O-RU nodes become non-operational or when the operator disables the optimization functions for energy saving or when optimization criteria are no longer met. | | -| Exceptions | None. | | -| Post Conditions | Non-RT RIC continues closed loop monitoring of energy saving function at O-DU and O-RU.

O-DU(s) and O-RU(s) operate using the configuration provided by the energy saving rApp via Non-RT RIC/SMO framework. | | - -``` -@startuml -!pragma teoz true -``` - -``` - -skinparam sequenceArrowThickness 2 -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 15 -skinparam sequenceMessageAlign center -skinparam sequenceMessageAlign center - -title PA Power optimization (Maximum output power control) based energy saving - non-RT -RIC driven solution - -Skin rose - -box "Operator" #Lightblue - Actor host as "Host" -End box - -Box "Service Orchestration and Management Framework" #gold - participant "non-RT RIC \n(rApps)" as rapp - participant "MnS Consumer \n(RAN NF OAM SMOS)" as smo - participant "O-RU Controller \n(Netconf client)" as smoru -end box - -box "O-RAN NF" #lightpink - box "O-DU" #lightcyan - participant "MnS Producer \n(MnF of O-DU)" as mnfodu - participant "O-RU Controller/\nNetconf client\n(O-DU (CU-Plane))" as client - end box - participant "NETCONF Server/\n(O-RU)" as RU -end box - -Note over RU, smo -Pre-condition: -1) O-RU established netconf session with O-RU Controller(s) -2) SMO subscribed for O&M data (CM, FM, and PM) to O-DU -3) O-DU subscribed for O&M data (CM, FM, and PM) to O-RU -End note - -Group Capability exposure - -``` - -Alt Hierarchical deployment - -client<-RU : [1a] <> Expose the PA power optimization (maximum \noutput control) feature capability and associated parameters - -smo<-mnfodu : [1b] <> O-DU exposes its own and the O-RU capabilities - -Else Hybrid deployment - -smo<-mnfodu : [2a] <> SMO retrieves O-DU capabilities - -smoru<-RU : [2b] <> Expose the PA power optimization (maximum output control) feature capability and associated parameters - -End Alt - -End group - -Loop PA power optimization feature implementation - -group SMO prepare policy/configuration details - -note over host, smo : [3] Analyse the RAN data and KPIs or operator trigger \nand prepare the energy saving policy/configuration \nchanges for PA power optimization - -end group - -Alt SMO provides policy to the O-DU - -note over smo, mnfodu : [4a] <> SMO provides policy to the O-DU for \nPA power optimization of a specific O-RU - -else SMO provides the configuration changes to the O-DU - -note over smo, mnfodu : [4b] <> SMO provides configuration changes to the O-DU \nfor activating the PA power optimization in the O-RU - -end alt - -group O-DU activates the PA power optimization feature in a specific O-RU - -note over mnfodu, client : [5] O-DU analyse the policy or configuration changes and decide to \nactivate PA power optimization feature in the specific O-RU - -note over client, RU : [6] <> Configures (activate) the PA power optimization feature - -note left RU : [7] O-RU adjust the PA parameters based \non the O-DU configured parameters - -note left RU : O-RU enters energy saving mode - -end group - -group O-DU deactivates the PA power optimization feature in a specific O-RU - -opt - -note over smo, mnfodu : [8] <> SMO provides configuration changes to the O-DU \nfor deactivating the PA power optimization in O-RU - -end opt - -note over mnfodu, client : [9] O-DU analyse the policy or configuration details and decide to \ndeactivate PA power optimization feature in the specific O-RU - -note over client, RU : [10] <> Configures (deactivate) the PA power optimization feature - -``` - -note left RU : [11] O-RU adjust the PA parameters \nto operate in default operational mode - -note left RU : O-RU exits energy saving mode - -end group - -end loop - -@enduml - -``` - -The flow diagram of the PA power optimization using O1-based solution is given in figure 4.21.3.5.1-1. - -![Sequence diagram titled 'PA Power optimization (Maximum output power control) based energy saving - non-RT RIC driven solution'. It shows interactions between Operator, Service Orchestration and Management Framework (non-RT RIC, MnS Consumer, O-RU Controller), O-DU (MnS Producer, O-RU Controller/Netconf client), and O-RAN NF (NETCONF Server/O-RU). The process involves capability exposure, policy preparation, activation, and deactivation of PA power optimization features.](826bf0fa6fd822169e7a2b4e5f197dd4_img.jpg) - -**Sequence Diagram: PA Power optimization (Maximum output power control) based energy saving - non-RT RIC driven solution** - -**Participants:** - -- Operator (Host)** -- Service Orchestration and Management Framework** (containing non-RT RIC (rApps), MnS Consumer (RAN NF OAM SMOS), O-RU Controller (Netconf client)) -- O-DU** (containing MnS Producer (MnF of O-DU), O-RU Controller/Netconf client (O-DU (CU-Plane))) -- O-RAN NF** (containing NETCONF Server/O-RU) - -**Pre-conditions:** - -- 1) O-RU established netconf session with O-RU Controller(s) -- 2) SMO subscribed for O&M datas (CM, FM, and PM) to O-DU -- 3) O-DU subscribed for O&M datas (CM, FM, and PM) to O-RU - -**Sequence of Interactions:** - -- Capability exposure** - - alt: **[Hierarchical deployment]** - - 1a) «OFH M-Plane» O-DU exposes its own and the O-RU capabilities to SMO. - - 1b) «O1» O-DU exposes its own and the O-RU capabilities to SMO. - - alt: **[Hybrid deployment]** - - 2a) «O1» SMO retrieves O-DU capabilities from O-DU. - - 2b) «OFH M-Plane» O-DU exposes the PA power optimization (maximum output control) feature capability and associated parameters to SMO. -- loop: [PA power optimization feature implementation]** - - SMO prepare policy/configuration details** - - 3) Analyse the RAN datas and KPIs or operator trigger and prepare the energy saving policy/configuration changes for PA power optimization. - - alt: [SMO provides policy to the O-DU]** - - 4a) «O1» SMO provides policy to the O-DU for PA power optimization of a specific O-RU. - - alt: [SMO provides the configuration changes to the O-DU]** - - 4b) «O1» SMO provides configuration changes to the O-DU for activating the PA power optimization in the O-RU. - - O-DU activates the PA power optimization feature in a specific O-RU** - - 5) O-DU analyse the policy or configuration changes and decide to activate PA power optimization feature in the specific O-RU. - - 6) «FH M-Plane/C-Plane» O-DU configures (activate) the PA power optimization feature to O-RU. - - 7) O-RU adjust the PA parameters based on the O-DU configured parameters. - - O-RU enters energy saving mode. - - O-DU deactivates the PA power optimization feature in a specific O-RU** - - alt: **[O1]** - - 8) «O1» SMO provides configuration changes to the O-DU for deactivating the PA power optimization in O-RU. - - 9) O-DU analyse the policy or configuration details and decide to deactivate PA power optimization feature in the specific O-RU. - - 10) «FH M-Plane/C-Plane» O-DU configures (deactivate) the PA power optimization feature to O-RU. - - 11) O-RU adjust the PA parameters to operate in default operational mode. - - O-RU exits energy saving mode. - -Sequence diagram titled 'PA Power optimization (Maximum output power control) based energy saving - non-RT RIC driven solution'. It shows interactions between Operator, Service Orchestration and Management Framework (non-RT RIC, MnS Consumer, O-RU Controller), O-DU (MnS Producer, O-RU Controller/Netconf client), and O-RAN NF (NETCONF Server/O-RU). The process involves capability exposure, policy preparation, activation, and deactivation of PA power optimization features. - -Figure 4.21.3.5.1-1: PA power optimization-based energy saving (method #1): AI/ML inference via Non-RT RIC - -##### 4.21.3.5.2 Solution: xApp-based solution (E2-based) - -The following entities are applicable to this solution: energy saving xApp, Near-RT RIC/SMO framework, O-DU node and O-RU node. - -A solution for PA power optimization-based energy saving: use case through xApp-based solution is captured in table 4.21.3.5.2-1. - -**Table 4.21.3.5.2-1: PA power optimization: AI/ML inference via Near-RT RIC** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Enable PA power optimization energy saving functions in the network by means of configuration parameter change and actions controlled by Near-RT RIC and allow for AI/ML-based solutions. | | -| Actors and Roles | 1) Energy saving xApp
2) Near-RT RIC
3) Non-RT RIC/SMO framework
4) O-DU node
5) O-RU node | | -| Assumptions |
  • A1 interface connectivity is established between Non-RT RIC of SMO framework and Near-RT RIC.
  • E2 interface connectivity is established between network functions (O-DU) and Near-RT RIC.
  • Open FH M-plane interface is established between O-DU and O-RU and/or SMO and O-RU directly.
  • Network is operational.
| | -| Pre-conditions | Operator has set the targets for energy saving functions in Near-RT RIC. | | -| Begins when | Operator enables the optimization functions for PA power optimization energy saving functions, and O-DU and O-RU become operational. | | -| Alt
Step 1a (M) | SMO framework consumes and analyzes the various measurement data like CM, PM, and FM data and KPIs or operator trigger (requested configuration changes). | Use case | -| Step 1b (M) | Non-RT RIC SMOF prepares A1 policy for Near-RT RIC (xApps) to optimize the PA power consumption of a specific O-RU. | Use case | -| Step 1c (M) | Non-RT RIC SMOF provides policy prepared in Step 1b, to Near-RT RIC via A1 interface. | Use case | -| Step 1d (M) | Energy saving xApp constantly monitors
(i) energy consumption of O-RU(s)
(ii) cell utilization, throughput, and related performance metrics

Near-RT RIC analyzes the A1 policy that it received from Non-RT RIC in Step 1c and the above measurement data. The xApps of Near-RT RIC function prepares the E2 policy or determines the configuration changes that need to be provided to O-DU, for PA power optimization use case. AI/ML inference may be used to make the decision.

The Near-RT RIC provides the E2 policy or configuration changes to O-DU for PA power optimization of a specific O-RU. | Use case | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------| -| Alt
Step 2a (M) | Energy saving xApp constantly monitors
(i) energy consumption of O-RU(s)
(ii) cell utilization, throughput, and related performance metrics

Near-RT RIC (xApp) analyzes the above measurement data and KPIs, and prepares the E2 policy or configuration changes for O-DU. | Use case | -| Step 2b (M) | Near-RT RIC provides the policy or configuration changes (prepared in Step 2a) to O-DU via E2 interface. | O-RAN.WG3.TS.UCR [46], clause 4.6.4;
O-RAN.WG3.TS.E2SM-CCC [47], clause 8.8.2.9;
Use case | -| Step 3 (M) | O-DU analyzes the policy or configuration changes that it received either in Step 1d or 2b. Once the conditions mentioned in that policy are satisfied or based on the requested configuration changes, the O-DU decides to activate the PA power optimization feature in the O-RU. | Use case | -| Step 4 (M) | O-DU may send the appropriate commands to the O-RU via fronthaul M-plane or C-plane to activate the PA power optimization. Here, the O-DU configures the appropriate maximum output power based on the traffic scheduling requirements and energy saving policy received from Near-RT RIC via E2 interface. | O-RAN.WG4.MP [28], clause 20.6;
Use case | -| Step 5 (M) | O-RU adjusts the PA parameters based on the maximum output power configured by the O-DU. Then the O-RU transitions to (PA power optimization) energy saving mode. This is to reduce PA power consumption, thereby improving the O-RU energy efficiency. | Use case | -| Step 6 (O) | Near-RT RIC analyses the O&M data and KPIs to prepare configuration changes required for O-DU to deactivate the PA power optimization feature and provide them to O-DU via E2 interface. | O-RAN.WG3.TS.UCR [46], clause 4.6.4;
O-RAN.WG3.TS.E2SM-CCC [47], clause 8.8.2.9;
Use case | -| Step 7 (M) | O-DU analyzes the policy provided by Near-RT RIC in Steps 1d or 2b or configuration changes provided by Near-RT RIC in Step 6. Then the O-DU decides to deactivate the PA power optimization feature in the specific O-RU, i.e., O-DU to configure nominal output power to O-RU. | Use case | -| Step 8 (O) | O-DU may send the appropriate commands to the O-RU via fronthaul M-plane or C-plane to configure the nominal output power, accordingly O-RU adjusts its PA parameters. This is to deactivate the PA power optimization feature in the O-RU and exit from the energy saving mode. | O-RAN.WG4.MP [28], clause 20.6;
Use case | -| Ends when | NF node (O-DU) and O-RU become non-operational or when the operator disables the optimization functions for energy saving or when optimization criteria are no longer met. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Exceptions | None. | | -| Post Conditions | Near-RT RIC continues close loop monitoring of energy saving function at NF node (O-DU) and O-RU.

NF node(s) and O-RU(s) operate using the configuration provided by the energy saving xApp via Near-RT RIC. | | - -``` - -@startuml -!pragma teoz true -skinparam sequenceArrowThickness 2 -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 15 -skinparam sequenceMessageAlign center -skinparam sequenceMessageAlign center - -title PA Power optimization (Maximum output power control) based energy saving - near-RT -RIC driven solution - -Skin rose - -box "Operator" #Lightblue - Actor host as "Host" -End box - -Box "Service Orchestration and Management Framework" #gold - participant "MnS Consumer \n(RAN NF OAM SMOS)" as smo - participant "O-RU Controller \n(Netconf client)" as smoru - participant "non-RT RIC \n(rApps)" as rapp -end box - -participant "near-RT RIC \n(xApps)" as xapp - -box "O-RAN NF" #lightpink - box "O-DU" #lightcyan - participant "E2 termination" as e2odu - participant "O-RU Controller \n (Netconf client)\n(O-DU)" as client - end -end box - -``` - -``` -end box -``` - -``` -participant "NETCONF Server/\n(O-RU)" as RU -``` - -``` -end box -``` - -``` -Note over smo, RU -``` - -``` -Pre-condition: -``` - -1. O-RU established netconf session with O-RU Controller(s) -2. SMO, near-RT RIC, and O-DU aware of O-RU capabilities -3. SMO and near-RT RIC subscribed for O&M datas (CM, FM, and PM) to O-DU -4. O-DU subscribed for O&M datas (CM, FM, and PM) to O-RU - -``` -End note -``` - -``` -group PA power optimization feature implementation -``` - -``` -group Policy or configuration changes preparation for O-DU -``` - -``` -alt Non-RT RIC provides A1 policy to near-RT RIC based on RAN datas and KPI for O-DU to optimize the PA power consumption in O-RU -``` - -``` -note over host, rapp : [1a] Analyze the O&M datas (CM, PM, and FM) and KPIs or operator trigger -``` - -``` -rapp->rapp : [1b] Prepare A1 policy for \nPA power optimization -``` - -``` -rapp<->xapp : [1c] <> Provides policy \nto near-RT RIC -``` - -``` -note left xapp : Near-RT RIC prepares E2 policy \nor configuration changes -``` - -``` -note over xapp, e2odu : [1d] <> Provides E2 policy or configuration changes to O-DU -``` - -``` -else Near-RT RIC prepares the E2 policy or configuration changes to O-DU for PA power optimization in O-RU -``` - -``` -xapp->xapp : [2a] Prepares E2 policy or \nconfiguration changes for O-DU -``` - -``` -note over xapp, e2odu : [2b] <> Provides E2 policy or configuration changes to O-DU -``` - -``` -end alt -``` - -``` -end group -``` - -``` -group O-DU activates the PA power optimization feature in a specific O-RU -``` - -``` -note over e2odu, client : [3] O-DU analyze the policy or configuration changes and decide \nto activate PA power optimization feature in the specific O-RU -``` - -``` -note over client, RU : [4] <> Configures (activate) \nthe PA power optimization feature -``` - -``` -note left RU : [5] O-RU adjust the PA parameters based \non the O-DU configured parameters -``` - -``` -note left RU : O-RU enters energy saving mode -``` - -``` -end group -``` - -``` -group O-DU deactivates the PA power optimization feature in a specific O-RU -opt -note over xapp, e2odu : [6] <> Near-RT RIC provides configuration changes to the \nO- -DU for deactivating the PA power optimization in O-RU -end opt - -note over e2odu, client : [7] O-DU analyze the policy/configuration details and decide to -\ndeactivate PA power optimziation feature in the specific O-RU - -opt -note over client, RU : [8] <> Configures (deactivate) \nthe PA power -optimization feature -end opt - -note left RU : O-RU exits energy saving mode -end group -end loop -@enduml -``` - -The flow diagram of the PA power optimization using E2-based solution is given in figure 4.21.3.5.2-1. - -![Sequence diagram for PA power optimization. Lifelines: Operator (Host), Service Orchestration and Management Framework (MnS Consumer, O-RU Controller, non-RT RIC, near-RT RIC), O-RAN NF (O-DU: E2 termination, O-RU Controller, NETCONF Server). The process involves policy preparation, feature activation, and optional deactivation.](22117363b092d194772c750e321202cc_img.jpg) - -**PA Power optimization (Maximum output power control) based energy saving - near-RT RIC driven solution** - -``` - -sequenceDiagram - participant Operator as Operator (Host) - participant SMO as Service Orchestration and Management Framework (MnS Consumer, O-RU Controller, non-RT RIC, near-RT RIC) - participant ODU as O-RAN NF (O-DU: E2 termination, O-RU Controller, NETCONF Server) - - Note right of SMO: Pre-condition: -1. O-RU established netconf session with O-RU Controller(s) -2. SMO, near-RT RIC, and O-DU aware of O-RU capabilities -3. SMO and near-RT RIC subscribed for O&M datas (CM, FM, and PM) to O-DU -4. O-DU subscribed for O&M datas (CM, FM, and PM) to O-RU - - Note left of SMO: PA power optimization feature implementation - Note left of SMO: Policy or configuration changes preparation for O-DU - alt Non-RT RIC provides A1 policy to near-RT RIC based on RAN datas and KPI for O-DU to optimize the PA power consumption in O-RU - Note left of SMO: [1a] Analyze the O&M datas (CM, PM, and FM) and KPIs or operator trigger - Note right of SMO: [1b] Prepare A1 policy for PA power optimization - Note right of SMO: [1c] «A1» Provides policy to near-RT RIC - Note right of SMO: Near-RT RIC prepares E2 policy or configuration changes - Note right of SMO: [1d] «E2» Provides E2 policy or configuration changes to O-DU - else Near-RT RIC prepares the E2 policy or configuration changes to O-DU for PA power optimization in O-RU - Note right of SMO: [2a] Prepares E2 policy or configuration changes for O-DU - Note right of SMO: [2b] «E2» Provides E2 policy or configuration changes to O-DU - end - - Note right of ODU: O-DU activates the PA power optimization feature in a specific O-RU - Note right of ODU: [3] O-DU analyze the policy or configuration changes and decide to activate PA power optimization feature in the specific O-RU - Note right of ODU: [4] «FH M-Plane/C-Plane» Configures (activate) the PA power optimization feature - Note right of ODU: [5] O-RU adjust the PA parameters based on the O-DU configured parameters - Note right of ODU: O-RU enters energy saving mode - - Note right of ODU: O-DU deactivates the PA power optimization feature in a specific O-RU - alt - Note right of SMO: [6] «E2» Near-RT RIC provides configuration changes to the O-DU for deactivating the PA power optimization in O-RU - Note right of ODU: [7] O-DU analyze the policy/configuration details and decide to deactivate PA power optimization feature in the specific O-RU - alt - Note right of ODU: [8] «FH M-Plane/C-Plane» Configures (deactivate) the PA power optimization feature - Note right of ODU: O-RU exits energy saving mode - end - end - -``` - -Sequence diagram for PA power optimization. Lifelines: Operator (Host), Service Orchestration and Management Framework (MnS Consumer, O-RU Controller, non-RT RIC, near-RT RIC), O-RAN NF (O-DU: E2 termination, O-RU Controller, NETCONF Server). The process involves policy preparation, feature activation, and optional deactivation. - -**Figure 4.21.3.5.2-1: PA power optimization-based energy saving (method #2): AI/ML inference via Near-RT RIC** - -### 4.21.4 Required data - -#### 4.21.4.1 Carrier and cell switch off/on - -##### 4.21.4.1.1 Solution 1: rApp-based solution - -The data requirements for this solution are specified below. The input data specified in table 4.21.4.1.1-1 shall be supported by the associated interfaces specified in the table. - -**Table 4.21.4.1.1-1: Required input data for energy saving use case** - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|--------------|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------|-----------| -| Req-4.21.001 | Network load and data performance | DL PDCP SDU data volume per interface (data volume in DL delivered from O-CU-UP to O-DU, per PLMN, per QoS level, per slice, per interface (F1-U, Xn-U, X2-U)) | O-CU | 3GPP TS 28.552 [6], clause 5.1.3.6.2.3 | O1 | -| Req-4.21.002 | Network load and data performance | UL PDCP SDU data volume per interface (data volume in UL delivered to O-CU-UP from O-DU, per PLMN, per QoS level, per slice, per interface (F1-U, Xn-U, X2-U)) | O-CU | 3GPP TS 28.552 [6], clause 5.1.3.6.2.4 | O1 | -| Req-4.21.003 | Network load and data performance | DL Total PRB Usage | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.2.1 | O1 | -| Req-4.21.004 | Network load and data performance | UL Total PRB Usage | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.2.2 | O1 | -| Req-4.21.005 | Network load and data performance | Mean number of Active UEs, per cell (and optionally per PLMN, per slice) | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.23.5 | O1 | -| Req-4.21.006 | Network load and data performance | Average DL UE throughput in gNB per cell (and optionally per PLMN, per QoS level, per slice) | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.3.1 | O1 | -| Req-4.21.007 | Network load and data performance | Average UL UE throughput in gNB per cell (and optionally per PLMN, per QoS level, per slice) | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.3.2 | O1 | -| Req-4.21.008 | UE measurement | RSRQ measurement per SSB per cell | O-CU | 3GPP TS 28.552 [6], clause 5.1.1.31 | O1 | -| Req-4.21.009 | UE measurement | RSRP measurement per SSB per cell | O-CU | 3GPP TS 28.552 [6], clause 5.1.1.22 | O1 | -| Req-4.21.010 | UE measurement | SINR measurement per SSB per cell | O-CU | 3GPP TS 28.552 [6], clause 5.1.1.32 | O1 | - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|--------------|--------------------|----------------------------------------------------------------------------------------------|---------------|----------------------------------------------------------------------------------|------------------------| -| Req-4.21.011 | Energy consumption | Energy consumption | O-DU,
O-RU | 3GPP TS 28.552 [6], clause 5.1.1.19.3 | O1,
Open FH M-plane | -| Req-4.21.012 | Energy consumption | Power consumed by physical network function & its components | O-DU,
O-RU | 3GPP TS 28.552 [6], clause 5.1.1.19.2 and in O-RAN.WG4.MP [28], clauses B.1, B.5 | O1,
Open FH M-plane | -| Req-4.21.013 | Energy consumption | Transmit power | O-RU | O-RAN.WG4.MP [28], clauses B.1, B.2.1 | O1,
Open FH M-plane | -| Req-4.21.014 | Topology | Site location and orientation per cell
siteLatitude, siteLongitude, Azimuth / orientation | | 3GPP TS 28.623 [40] | | -| Req-4.21.015 | Configuration | Carrier frequency per cell
arfcnDL | O-DU | 3GPP TS 28.541 [5], clause 4.3.6 | O1 | -| Req-4.21.016 | Configuration | Carrier bandwidth per cell | O-DU | 3GPP TS 28.541 [5], clause 4.3.6 | O1 | -| Req-4.21.017 | Configuration | cellState | O-DU | 3GPP TS 28.541 [5], clause 4.4.1 | O1 | - -The output data specified in table 4.21.4.1.1-2 shall be supported by the associated interfaces specified in the table. - -**Table 4.21.4.1.1-2: Required output data for O1-based solution** - -| Requirement | Category | Parameters / Measurements | Target | Reference | Interface | -|--------------|----------------------------------------------------------|---------------------------|--------|-----------------------------------|-----------| -| Req-4.21.018 | Carrier(s) or cell(s) indicated for energy saving action | CESManagementFunction | O-CU | 3GPP TS 28.541 [5], clause 4.3.63 | O1 | - -#### 4.21.4.2 RF channel reconfiguration for network energy savings - -##### 4.21.4.2.1 Solution: rApp-based solution - -The data requirements for this solution are specified below. The input data specified in table 4.21.4.2.1-1 shall be supported by the associated interfaces specified in the table. - -**Table 4.21.4.2.1-1: Required input data for RF channel reconfiguration-based energy saving use case - O1-based solution** - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|------------------|-----------------------------------|--------------------------------------------------------------------------|---------|----------------------------------------------|-----------| -| Req-4.21.4.2.001 | Network load and data performance | DL PDCP SDU Data Volume per cell | O-CU-UP | O-RAN.WG10.TS.O1PMeas [48], clause A.3.1.22 | O1 | -| Req-4.21.4.2.002 | Network load and data performance | UL PDCP SDU Data Volume per cell | O-CU-UP | O-RAN.WG10.TS.O1PMeas [48], clause A.3.1.19 | O1 | -| Req-4.21.4.2.003 | Network load and data performance | Distribution of DL Total PRB Usage | O-DU | O-RAN.WG10.TS.O1PMeas [48], clause A.4.11.23 | O1 | -| Req-4.21.4.2.004 | Network load and data performance | Distribution of UL Total PRB Usage | O-DU | O-RAN.WG10.TS.O1PMeas [48], clause A.4.11.24 | O1 | -| Req-4.21.4.2.005 | Network load and data performance | Mean number of Active UEs, per cell (and optionally per PLMN, per slice) | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.23.5 | O1 | -| Req-4.21.4.2.006 | Network load and data performance | Distribution of UL UE throughput in gNB | O-DU | O-RAN.WG10.TS.O1PMeas [48], clause A.4.11.33 | O1 | -| Req-4.21.4.2.007 | Network load and data performance | Distribution of DL UE throughput in gNB | O-DU | O-RAN.WG10.TS.O1PMeas [48], clause A.4.11.34 | O1 | -| Req-4.21.4.2.008 | Network load and data performance | TRx Control activation | O-DU | O-RAN.WG10.TS.O1PMeas [48], clause A.4.13.14 | O1 | -| Req-4.21.4.2.009 | Network load and data performance | TRx Control activation failure | O-DU | O-RAN.WG10.TS.O1PMeas [48], | O1 | - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|------------------|-----------------------------------|--------------------------------------------------------------------------------------------------|--------|--------------------------------------------------------|-----------| -| | | | | clause
A.4.13.15 | | -| Req-4.21.4.2.010 | Network load and data performance | TRx Control Cumulative Activity time | O-DU | O-RAN.WG10.TS.
O1PMeas [48],
clause
A.4.13.16 | O1 | -| Req-4.21.4.2.011 | Energy consumption | Energy consumption | O-DU | 3GPP TS
28.552 [6],
clause
5.1.1.19.3 | O1 | -| Req-4.21.4.2.012 | Power consumption | Power consumed by physical network function & its components | O-DU | 3GPP TS
28.552 [6],
clause
5.1.1.19.2 | O1 | -| Req-4.21.4.2.013 | Configuration | cellState | O-DU | 3GPP TS
28.541 [5],
clause 4.4.1 | O1 | -| Req-4.21.4.2.014 | Topology | Site location and orientation per cell

siteLatitude, siteLongitude, Azimuth / orientation | O-DU | 3GPP TS
28.623 [40] | O1 | -| Req-4.21.4.2.015 | Configuration | arfcnDL | O-DU | 3GPP TS
28.541 [5],
clause 4.3.6 | O1 | -| Req-4.21.4.2.016 | Configuration | bSChannelBwDL | O-DU | 3GPP TS
28.541 [5],
clause 4.3.6 | O1 | -| Req-4.21.4.2.017 | Network load and data performance | DL Total PRB Usage per cell | O-DU | 3GPP TS
28.552 [6],
clause 5.1.1.2.1 | O1 | -| Req-4.21.4.2.018 | Network load and data performance | UL Total PRB Usage per cell | O-DU | 3GPP TS
28.552 [6],
clause 5.1.1.2.2 | O1 | -| Req-4.21.4.2.019 | Network load and data performance | PDSCH PRB Usage per cell for MIMO | O-DU | 3GPP TS
28.552 [6],
clause
5.1.1.2.11 | O1 | -| Req-4.21.4.2.020 | Network load and data performance | PUSCH PRB Usage per cell for MIMO | O-DU | 3GPP TS
28.552 [6],
clause
5.1.1.2.12 | O1 | -| Req-4.21.4.2.021 | Network load and data performance | UE Throughput DL/UL | O-DU | 3GPP TS
28.552 [6],
clause 5.1.1.3 | O1 | - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|------------------|-----------------------------------|-------------------------------------------------------------------------------------------------------------|-----------------|--------------------------------------------|-----------------| -| Req-4.21.4.2.022 | Network load and data performance | Cell-level Coverage KPI | O-DU | 3GPP TS 28.552 [6], clauses 5.1.1.7 | O1 | -| Req-4.21.4.2.023 | Network load and data performance | Intra-NRCell SSB Beam switch Measurement | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.21 | O1 | -| Req-4.21.4.2.024 | Network load and data performance | RSRP Measurement | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.22 | O1 | -| Req-4.21.4.2.025 | Network load and data performance | Active UE per cell (per PLMN/slice) | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.23.5 | O1 | -| Req-4.21.4.2.026 | Network load and data performance | SSB beam related Measurement | Beam (O-DU) | 3GPP TS 28.552 [6], clauses 5.1.1.28 | O1 | -| Req-4.21.4.2.027 | Network load and data performance | Transmit power utilization measurements | NRCellDU (O-DU) | 3GPP TS 28.552 [6], clauses 5.1.1.29 | O1 | -| Req-4.21.4.2.028 | Network load and data performance | SS-RSRQ distribution per SSB | Beam (O-DU) | 3GPP TS 28.552 [6], clauses 5.1.1.31.2 | O1 | -| Req-4.21.4.2.029 | Network load and data performance | MU-MIMO related measurements | NRCellDU (O-DU) | 3GPP TS 28.552 [6], clauses 5.1.1.30 | O1 | -| Req-4.21.4.2.030 | Energy consumption | Energy consumption | O-RU | 3GPP TS 28.552 [6], clause 5.1.1.19.3 | Open FH M-plane | -| Req-4.21.4.2.031 | Power consumption | Power consumed by physical network function & its component, especially the power amplifier | O-RU | O-RAN.WG4.MP [28], clauses B.1, B.2.1, B.5 | Open FH M-plane | -| Req-4.21.4.2.032 | Sleep mode details | Supported sleep modes (capabilities) by O-RU | O-RU | O-RAN.WG4.MP [28], clause 20.4.1 | Open FH M-plane | -| Req-4.21.4.2.033 | Sleep mode details | Minimum and Guaranteed Wakeup | O-RU | O-RAN.WG4.MP [28], clause 20.4.1 | Open FH M-plane | -| Req-4.21.4.2.034 | TRx Control details | Supported TRx Control masks (antenna masks) (capabilities) by O-RU (TRx Control via Open Fronthaul C-Plane) | O-RU | O-RAN.WG4.MP [28], clause 20.3.1.2 | Open FH M-plane | - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|------------------|---------------------|-------------------------------------------------------------------------------------------------------------|--------|------------------------------------|-----------------| -| Req-4.21.4.2.035 | TRx Control details | Supported TRx Control masks (antenna masks) (capabilities) by O-RU (TRx Control via Open Fronthaul M-Plane) | O-RU | O-RAN.WG4.MP [28], clause 20.3.2.2 | Open FH M-plane | - -The output data specified in table 4.21.4.2.1-2 shall be supported by the associated interfaces specified in the table. - -**Table 4.21.4.2.1-2: Required output data for RF channel reconfiguration-based energy saving use case - O1-based solution** - -| Requirement | Category | Parameters / Measurements | Target | Reference | Interface | -|------------------|-------------------|----------------------------------------------------|------------|--------------------------------------------------------------------------------------------------------|-----------------| -| Req-4.21.4.2.101 | NES Policy | NESPolicy | O-DU | O-RAN.WG10.TS. O1NRM [45], clause 5.3.5 | O1 | -| Req-4.21.4.2.102 | NES Policy | NESPolicyRelation | O-DU | O-RAN.WG10.TS. O1NRM [45], clause 5.3.6 | O1 | -| Req-4.21.4.2.103 | NES configuration | NES configuration (Open Fronthaul M-Plane) changes | O-DU, O-RU | O-RAN.WG4.MP [28], clause 20.3.2.3 | Open FH M-plane | -| Req-4.21.4.2.104 | NES configuration | NES configuration (Open Fronthaul C-Plane) changes | O-DU, O-RU | O-RAN.WG4.MP [28], clause 20.3.1.3;

O-RAN.WG4.TS.C US.0-R004 [51], clause 7.4.6, 16, 16.1, 16.2 | Open FH C-plane | - -##### 4.21.4.2.2 Solution: rApp/xApp-based solution - -The data requirements for this solution are specified below. The input data specified in table 4.21.4.2.2-1 shall be supported by the associated interfaces specified in the table. - -**Table 4.21.4.2.2-1: Required input data for RF channel reconfiguration-based energy saving use case - A1/E2-based solution** - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|------------------|-----------------------------------|----------------------------------|---------|----------------------------------------------|-----------| -| Req-4.21.4.2.201 | Network load and data performance | DL PDCP SDU Data Volume per cell | O-CU-UP | O-RAN.WG10.TS. O1PMeas [48], clause A.3.1.22 | O1 | - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|------------------|-----------------------------------|--------------------------------------------------------------------------|---------|-----------------------------------------------|-----------| -| Req-4.21.4.2.202 | Network load and data performance | UL PDCP SDU Data Volume per cell | O-CU-UP | O-RAN.WG10.TS. O1PMeas [48], clause A.3.1.19 | O1 | -| Req-4.21.4.2.203 | Network load and data performance | Distribution of DL Total PRB Usage | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.11.23 | O1 | -| Req-4.21.4.2.204 | Network load and data performance | Distribution of UL Total PRB Usage | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.11.24 | O1 | -| Req-4.21.4.2.205 | Network load and data performance | Mean number of Active UEs, per cell (and optionally per PLMN, per slice) | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.23.5 | O1 | -| Req-4.21.4.2.206 | Network load and data performance | Distribution of UL UE throughput in gNB | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.11.33 | O1 | -| Req-4.21.4.2.207 | Network load and data performance | Distribution of DL UE throughput in gNB | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.11.34 | O1 | -| Req-4.21.4.2.208 | Network load and data performance | TRx Control activation | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.13.14 | O1 | -| Req-4.21.4.2.209 | Network load and data performance | TRx Control activation failure | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.13.15 | O1 | -| Req-4.21.4.2.210 | Network load and data performance | TRx Control Cumulative Activity time | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.13.16 | O1 | -| Req-4.21.4.2.211 | Energy consumption | Energy consumption | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.19.3 | O1 | - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|------------------|-----------------------------------|--------------------------------------------------------------------------------------------------|--------|---------------------------------------|-----------| -| Req-4.21.4.2.212 | Power consumption | Power consumed by physical network function & its components | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.19.2 | O1 | -| Req-4.21.4.2.213 | Configuration | cellState | O-DU | 3GPP TS 28.541 [5], clause 4.4.1 | O1 | -| Req-4.21.4.2.214 | Topology | Site location and orientation per cell

siteLatitude, siteLongitude, Azimuth / orientation | O-DU | 3GPP TS 28.623 [40] | O1 | -| Req-4.21.4.2.215 | Configuration | arfcnDL | O-DU | 3GPP TS 28.541 [5], clause 4.3.6 | O1 | -| Req-4.21.4.2.216 | Configuration | bSChannelBwDL | O-DU | 3GPP TS 28.541 [5], clause 4.3.6 | O1 | -| Req-4.21.4.2.217 | Network load and data performance | DL Total PRB Usage per cell | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.2.1 | O1 | -| Req-4.21.4.2.218 | Network load and data performance | UL Total PRB Usage per cell | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.2.2 | O1 | -| Req-4.21.4.2.219 | Network load and data performance | PDSCH PRB Usage per cell for MIMO | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.2.11 | O1 | -| Req-4.21.4.2.220 | Network load and data performance | PUSCH PRB Usage per cell for MIMO | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.2.12 | O1 | -| Req-4.21.4.2.221 | Network load and data performance | UE Throughput DL/UL | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.3 | O1 | -| Req-4.21.4.2.222 | Network load and data performance | Cell-level Coverage KPI | O-DU | 3GPP TS 28.552 [6], clauses 5.1.1.7 | O1 | -| Req-4.21.4.2.223 | Network load and data performance | Intra-NRCell SSB Beam switch Measurement | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.21 | O1 | -| Req-4.21.4.2.224 | Network load and data performance | RSRP Measurement | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.22 | O1 | -| Req-4.21.4.2.225 | Network load and data performance | Active UE per cell (per PLMN/slice) | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.23.5 | O1 | - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|------------------|-----------------------------------|-------------------------------------------------------------------------------------------------------------|-----------------|--------------------------------------------|-----------------| -| Req-4.21.4.2.226 | Network load and data performance | SSB beam related Measurement | Beam (O-DU) | 3GPP TS 28.552 [6], clauses 5.1.1.28 | O1 | -| Req-4.21.4.2.227 | Network load and data performance | Transmit power utilization measurements | NRCellDU (O-DU) | 3GPP TS 28.552 [6], clauses 5.1.1.29 | O1 | -| Req-4.21.4.2.228 | Network load and data performance | SS-RSRQ distribution per SSB | Beam (O-DU) | 3GPP TS 28.552 [6], clauses 5.1.1.31.2. | O1 | -| Req-4.21.4.2.229 | Network load and data performance | MU-MIMO related measurements | NRCellDU (O-DU) | 3GPP TS 28.552 [6], clauses 5.1.1.30 | O1 | -| Req-4.21.4.2.230 | Energy consumption | Energy consumption | O-RU | 3GPP TS 28.552 [6], clause 5.1.1.19.3 | Open FH M-plane | -| Req-4.21.4.2.231 | Power consumption | Power consumed by physical network function & its component, especially the power amplifier | O-RU | O-RAN.WG4.MP [28], clauses B.1, B.2.1, B.5 | Open FH M-plane | -| Req-4.21.4.2.232 | Sleep mode details | Supported sleep modes (capabilities) by O-RU | O-RU | O-RAN.WG4.MP [28], clause 20.4.1 | Open FH M-plane | -| Req-4.21.4.2.233 | Sleep mode details | Minimum and Guaranteed Wakeup | O-RU | O-RAN.WG4.MP [28], clause 20.4.1 | Open FH M-plane | -| Req-4.21.4.2.234 | TRx Control details | Supported TRx Control masks (antenna masks) (capabilities) by O-RU (TRx Control via Open Fronthaul C-Plane) | O-RU | O-RAN.WG4.MP [28], clause 20.3.1.2 | Open FH M-plane | -| Req-4.21.4.2.235 | TRx Control details | Supported TRx Control masks (antenna masks) (capabilities) by O-RU (TRx Control via Open Fronthaul M-Plane) | O-RU | O-RAN.WG4.MP [28], clause 20.3.2.2 | Open FH M-plane | - -NOTE: There is no O1 output. - -#### 4.21.4.3 Advanced Sleep Mode for network energy savings - -##### 4.21.4.3.1 Solution: rApp-based solution - -The data requirements for this solution are specified below. The input data specified in table 4.21.4.3.1-1 shall be supported by the associated interfaces specified in the table. - -**Table 4.21.4.3.1-1: Required input data for Advanced Sleep Mode-based energy saving use case - O1-based solution** - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|------------------|-----------------------------------|--------------------------------------------------------------------------|---------|-----------------------------------------------|-----------| -| Req-4.21.4.3.001 | Network load and data performance | DL PDCP SDU Data Volume per cell | O-CU-UP | O-RAN.WG10.TS. O1PMeas [48], clause A.3.1.22 | O1 | -| Req-4.21.4.3.002 | Network load and data performance | UL PDCP SDU Data Volume per cell | O-CU-UP | O-RAN.WG10.TS. O1PMeas [48], clause A.3.1.19 | O1 | -| Req-4.21.4.3.003 | Network load and data performance | Distribution of DL Total PRB Usage | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.11.23 | O1 | -| Req-4.21.4.3.004 | Network load and data performance | Distribution of UL Total PRB Usage | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.11.24 | O1 | -| Req-4.21.4.3.005 | Network load and data performance | Mean number of Active UEs, per cell (and optionally per PLMN, per slice) | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.23.5 | O1 | -| Req-4.21.4.3.006 | Network load and data performance | Distribution of UL UE throughput in gNB | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.11.33 | O1 | -| Req-4.21.4.3.007 | Network load and data performance | Distribution of DL UE throughput in gNB | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.11.34 | O1 | -| Req-4.21.4.3.008 | Network load and data performance | Advanced Sleep Mode activation | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.13.17 | O1 | -| Req-4.21.4.3.009 | Network load and data performance | Advanced Sleep Mode activation failure | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.13.18 | O1 | -| Req-4.21.4.3.010 | Network load and data performance | Advanced Sleep Mode Cumulative Activity time | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.13.19 | O1 | - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|------------------|-----------------------------------|--------------------------------------------------------------------------------------------------|--------|---------------------------------------|-----------------| -| Req-4.21.4.3.011 | Energy consumption | Energy consumption | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.19.3 | O1 | -| Req-4.21.4.3.012 | Power consumption | Power consumed by physical network function & its components | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.19.2 | O1 | -| Req-4.21.4.3.013 | Configuration | cellState | O-DU | 3GPP TS 28.541 [5], clause 4.4.1 | O1 | -| Req-4.21.4.3.014 | Topology | Site location and orientation per cell

siteLatitude, siteLongitude, Azimuth / orientation | O-DU | 3GPP TS 28.623 [40] | O1 | -| Req-4.21.4.3.015 | Configuration | arfcnDL | O-DU | 3GPP TS 28.541 [5], clause 4.3.6 | O1 | -| Req-4.21.4.3.016 | Configuration | bSChannelBwDL | O-DU | 3GPP TS 28.541 [5], clause 4.3.6 | O1 | -| Req-4.21.4.3.017 | Network load and data performance | DL Total PRB Usage per cell | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.2.1 | O1 | -| Req-4.21.4.3.018 | Network load and data performance | UL Total PRB Usage per cell | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.2.2 | O1 | -| Req-4.21.4.3.019 | Network load and data performance | UE Throughput DL/UL | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.3 | O1 | -| Req-4.21.4.3.020 | Network load and data performance | Cell-level Coverage KPI | O-DU | 3GPP TS 28.552 [6], clauses 5.1.1.7 | O1 | -| Req-4.21.4.3.021 | Network load and data performance | Intra-NRCell SSB Beam switch Measurement | O-DU | 3GPP TS 28.541 [5], clause 5.1.1.21 | O1 | -| Req-4.21.4.3.022 | Network load and data performance | Active UE per cell (per PLMN/slice) | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.23.5 | O1 | -| Req-4.21.4.3.023 | Energy consumption | Energy consumption | O-RU | 3GPP TS 28.552 [6], clause 5.1.1.19.3 | Open FH M-plane | - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|------------------|--------------------|---------------------------------------------------------------------------------------------|--------|--------------------------------------------|-----------------| -| Req-4.21.4.3.024 | Power consumption | Power consumed by physical network function & its component, especially the power amplifier | O-RU | O-RAN.WG4.MP [28], clauses B.1, B.2.1, B.5 | Open FH M-plane | -| Req-4.21.4.3.025 | Sleep mode details | Supported sleep modes (capabilities) by O-RU | O-RU | O-RAN.WG4.MP [28], clause 20.4.1 | Open FH M-plane | -| Req-4.21.4.3.026 | Sleep mode details | Minimum and Guaranteed Wakeup | O-RU | O-RAN.WG4.MP [28], clause 20.4.1 | Open FH M-plane | - -The output data specified in table 4.21.4.3.1-2 shall be supported by the associated interfaces specified in the table. - -**Table 4.21.4.3.1-2: Required output data for Advanced Sleep Mode-based energy saving use case - O1-based solution** - -| Requirement | Category | Parameters / Measurements | Target | Reference | Interface | -|------------------|-------------------|----------------------------------------|------------|-------------------------------------------------------------------------------------------------------|-----------------| -| Req-4.21.4.3.101 | NES Policy | NESPolicy | O-DU | O-RAN.WG10.TS.O1NRM [45], clause 5.3.5 | O1 | -| Req-4.21.4.3.102 | NES configuration | NESPolicyRelation | O-DU | O-RAN.WG10.TS.O1NRM [45], clause 5.3.6 | O1 | -| Req-4.21.4.3.103 | NES configuration | NES configuration (FH M-Plane) changes | O-DU, O-RU | O-RAN.WG4.MP [28], clause 20.5 | Open FH M-plane | -| Req-4.21.4.3.104 | NES configuration | NES configuration (FH C-Plane) changes | O-DU, O-RU | O-RAN.WG4.MP [28], clause 20.4.2;

O-RAN.WG4.TS.C US.0-R004 [51], clause 7.4.6, 16, 16.1, 16.2. | Open FH C-plane | - -##### 4.21.4.3.2 Solution: rApp/xApp-based solution - -The data requirements for this solution are specified below. The input data specified in table 4.21.4.3.2-1 shall be supported by the associated interfaces specified in the table. - -**Table 4.21.4.3.2-1: Required input data for Advanced Sleep Mode-based energy saving use case - A1/E2-based solution** - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|------------------|-----------------------------------|--------------------------------------------------------------------------|---------|-----------------------------------------------|-----------| -| Req-4.21.4.3.201 | Network load and data performance | DL PDCP SDU Data Volume per cell | O-CU-UP | O-RAN.WG10.TS. O1PMeas [48], clause A.3.1.22 | O1 | -| Req-4.21.4.3.202 | Network load and data performance | UL PDCP SDU Data Volume per cell | O-CU-UP | O-RAN.WG10.TS. O1PMeas [48], clause A.3.1.19 | O1 | -| Req-4.21.4.3.203 | Network load and data performance | Distribution of DL Total PRB Usage | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.11.23 | O1 | -| Req-4.21.4.3.204 | Network load and data performance | Distribution of UL Total PRB Usage | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.11.24 | O1 | -| Req-4.21.4.3.205 | Network load and data performance | Mean number of Active UEs, per cell (and optionally per PLMN, per slice) | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.23.5 | O1 | -| Req-4.21.4.3.206 | Network load and data performance | Distribution of UL UE throughput in gNB | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.11.33 | O1 | -| Req-4.21.4.3.207 | Network load and data performance | Distribution of DL UE throughput in gNB | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.11.34 | O1 | -| Req-4.21.4.3.208 | Network load and data performance | Advanced Sleep Mode activation | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.13.17 | O1 | -| Req-4.21.4.3.209 | Network load and data performance | Advanced Sleep Mode activation failure | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.13.18 | O1 | -| Req-4.21.4.3.210 | Network load and data performance | Advanced Sleep Mode Cumulative Activity time | O-DU | O-RAN.WG10.TS. O1PMeas [48], clause A.4.13.19 | O1 | - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|------------------|-----------------------------------|--------------------------------------------------------------------------------------------------|--------|---------------------------------------|-----------------| -| Req-4.21.4.3.211 | Energy consumption | Energy consumption | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.19.3 | O1 | -| Req-4.21.4.3.212 | Power consumption | Power consumed by physical network function & its components | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.19.2 | O1 | -| Req-4.21.4.3.213 | Configuration | cellState | O-DU | 3GPP TS 28.541 [5], clause 4.4.1 | O1 | -| Req-4.21.4.3.214 | Topology | Site location and orientation per cell

siteLatitude, siteLongitude, Azimuth / orientation | O-DU | 3GPP TS 28.623 [40] | O1 | -| Req-4.21.4.3.215 | Configuration | arfcnDL | O-DU | 3GPP TS 28.541 [5], clause 4.3.6 | O1 | -| Req-4.21.4.3.216 | Configuration | bSChannelBwDL | O-DU | 3GPP TS 28.541 [5], clause 4.3.6 | O1 | -| Req-4.21.4.3.217 | Network load and data performance | DL Total PRB Usage per cell | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.2.1 | O1 | -| Req-4.21.4.3.218 | Network load and data performance | UL Total PRB Usage per cell | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.2.2 | O1 | -| Req-4.21.4.3.219 | Network load and data performance | UE Throughput DL/UL | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.3 | O1 | -| Req-4.21.4.3.220 | Network load and data performance | Cell-level Coverage KPI | O-DU | 3GPP TS 28.552 [6], clauses 5.1.1.7 | O1 | -| Req-4.21.4.3.221 | Network load and data performance | Intra-NRCell SSB Beam switch Measurement | O-DU | 3GPP TS 28.541 [5], clause 5.1.1.21 | O1 | -| Req-4.21.4.3.222 | Network load and data performance | Active UE per cell (per PLMN/slice) | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.23.5 | O1 | -| Req-4.21.4.3.223 | Energy consumption | Energy consumption | O-RU | 3GPP TS 28.552 [6], clause 5.1.1.19.3 | Open FH M-plane | - -| Requirement | Category | Parameters / Measurements | Source | Reference | Interface | -|------------------|--------------------|---------------------------------------------------------------------------------------------|--------|--------------------------------------------|-----------------| -| Req-4.21.4.3.224 | Power consumption | Power consumed by physical network function & its component, especially the power amplifier | O-RU | O-RAN.WG4.MP [28], clauses B.1, B.2.1, B.5 | Open FH M-plane | -| Req-4.21.4.3.225 | Sleep mode details | Supported sleep modes (capabilities) by O-RU | O-RU | O-RAN.WG4.MP [28], clause 20.4.1 | Open FH M-plane | -| Req-4.21.4.3.226 | Sleep mode details | Minimum and Guaranteed Wakeup | O-RU | O-RAN.WG4.MP [28], clause 20.4.1 | Open FH M-plane | - -NOTE: There is no O1 output. - -#### 4.21.4.4 External power source coordination-based energy saving - -##### 4.21.4.4.1 Solution: rApp-based solution - -The data requirements for this solution are specified below. The input data specified in table 4.21.4.4.1-1 shall be supported by the associated interfaces specified in the table. - -**Table 4.21.4.4.1-1: Required input data for external power source coordination-based energy saving use case** - -| Category | Parameters / Measurements | Source | Reference | Interface | -|---------------------------|-----------------------------|--------|-------------------------------------|-----------| -| Energy supply information | energySupplyMode | SMO | 3GPP TS 28.310 [43], clause 8.3.1.2 | O1 | -| Energy supply information | energySourceList | SMO | 3GPP TS 28.310 [43], clause 8.3.1.2 | O1 | -| Energy source information | energySourceType | SMO | 3GPP TS 28.310 [43], clause 8.3.2.2 | O1 | -| Energy source information | energySourceCef | SMO | 3GPP TS 28.310 [43], clause 8.3.2.2 | O1 | -| Energy source information | renewableEnergy | SMO | 3GPP TS 28.310 [43], clause 8.3.2.2 | O1 | -| Energy source information | energyCompositionPercentage | SMO | 3GPP TS 28.310 [43], clause 8.3.2.2 | O1 | -| Energy information group | energySupplyModeRefList | SMO | 3GPP TS 28.310 [43], clause 8.3.3.2 | O1 | - -| Category | Parameters / Measurements | Source | Reference | Interface | -|---------------------------|------------------------------------------------------------------------------------------------------------------------|---------------|---------------------------------------|-----------------| -| Energy information group | memberDNList | SMO | 3GPP TS 28.310 [43], clause 8.3.3.2 | O1 | -| Energy supply information | energySupplyMode
This attribute/parameter to be specified according to the FH M-Plane yang model schema. | O-DU,
O-RU | O-RAN.WG4.MP [28] | Open FH M-plane | -| Energy supply information | energySourceList
This attribute/parameter to be specified according to the FH M-Plane yang model schema. | O-DU,
O-RU | O-RAN.WG4.MP [28] | Open FH M-plane | -| Energy source information | energySourceType
This attribute/parameter to be specified according to the FH M-Plane yang model schema. | O-DU,
O-RU | O-RAN.WG4.MP [28] | Open FH M-plane | -| Energy source information | energySourceCef
This attribute/parameter to be specified according to the FH M-Plane yang model schema. | O-DU,
O-RU | O-RAN.WG4.MP [28] | Open FH M-plane | -| Energy source information | renewableEnergy
This attribute/parameter to be specified according to the FH M-Plane yang model schema. | O-DU,
O-RU | O-RAN.WG4.MP [28] | Open FH M-plane | -| Energy source information | energyCompositionPercentage
This attribute/parameter to be specified according to the FH M-Plane yang model schema. | O-DU,
O-RU | O-RAN.WG4.MP [28] | Open FH M-plane | -| Energy consumption | Energy consumption | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.19.3 | O1 | -| Energy consumption | Energy consumption | O-RU | 3GPP TS 28.552 [6], clause 5.1.1.19.3 | Open FH M-plane | -| Energy consumption | Power consumed by physical network function & its components | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.19.2 | O1 | -| Energy consumption | Power consumed by physical network function & its components | O-RU | O-RAN.WG4.MP [28], clauses B.1, B.5 | Open FH M-plane | - -| Category | Parameters / Measurements | Source | Reference | Interface | -|-------------------|---------------------------|--------|---------------------------------------|-----------------| -| Power consumption | Power consumption | O-RU | O-RAN.WG4.MP [28], clauses B.1, B.2.1 | Open FH M-plane | -| Configuration | cellState | O-DU | 3GPP TS 28.541 [5], clause 4.4.1 | O1 | - -The output data specified in table 4.21.4.4.1-2 shall be supported by the associated interfaces specified in the table. - -**Table 4.21.4.4.1-2: Required output data for O1-based solution** - -| Category | Parameters / Measurements | Target | Reference | Interface | -|-----------------------------|-----------------------------------------------------|------------|------------------------------------------|-----------------| -| NES Policy | NESPolicy | O-DU | O-RAN.WG10.TS.O1NRM [45], clause 5.3.5 | O1 | -| NES configuration | NES configuration changes | O-DU | O-RAN.WG10.TS.O1NRM [45], clause 5.3.6 | O1 | -| NES configuration | NES configuration changes | O-DU, O-RU | O-RAN.WG4.MP [28], clause 20 | Open FH M-plane | -| NES configuration | NES configuration (FH C-Plane) changes | O-DU, O-RU | O-RAN.WG4.TS.C US.0-R004 [51], clause 16 | Open FH C-plane | -| Energy Source configuration | Energy source configuration changes to be specified | O-DU | O-RAN.WG10.TS.O1NRM [45] | O1 | -| Energy Source configuration | Energy source configuration changes to be specified | O-RU | O-RAN.WG4.MP [28] | Open FH M-plane | - -#### 4.21.4.5 PA power optimization-based energy saving - -##### 4.21.4.5.1 Solution: rApp/xApp-based solution - -The data requirements for this solution are specified below. The input data specified in table 4.21.4.5.1-1 shall be supported by the associated interfaces specified in the table. - -**Table 4.21.4.5.1-1: Required input data for PA power optimization-based energy saving use case** - -| Category | Parameters / Measurements | Source | Reference | Interface | -|----------------------------------------|---------------------------------------------------------------------------------------------|------------------|-----------------------------------------------------|-----------------| -| Performance measurements | O-CU-UP Performance measurements | O-CU-UP | O-RAN.WG10.TS.O1PMeas [48], clause A.3 | O1 | -| Performance measurements | O-DU Performance measurements | O-DU | O-RAN.WG10.TS.O1PMeas [48], clauses A.4.1 to A.4.12 | O1 | -| Energy consumption | Energy consumption | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.19.3 | O1 | -| Energy consumption | Energy consumption | O-RU | 3GPP TS 28.552 [6], clause 5.1.1.19.3 | Open FH M-plane | -| Energy consumption | Power consumed by physical network function & its components | O-DU | 3GPP TS 28.552 [6], clause 5.1.1.19.2 | O1 | -| Energy consumption | Power consumed by physical network function & its component, especially the power amplifier | O-RU | O-RAN.WG4.MP [28], clauses B.1, B.5 | Open FH M-plane | -| Power consumption | Power consumption | O-RU | O-RAN.WG4.MP [28], clauses B.1, B.2.1 | Open FH M-plane | -| Configuration | cellState | O-DU | 3GPP TS 28.541 [5], clause 4.4.1 | O1 | -| Transmitted data volume | DL Transmitted Data Volume (RLC SDU) | O-DU (NRCELL DU) | O-RAN.WG3.TS.E 2SM-KPM [49], clause 7.10.1 | E2 | -| Percentage of data volume distribution | Distribution of Percentage of DL Transmitted Data Volume to Incoming Data Volume | O-DU (NRCELL DU) | O-RAN.WG3.TS.E 2SM-KPM [49], clause 7.10.3 | E2 | -| Total number of scheduled time slots | Cell-specific DL Total transmission time duration | O-DU (NRCELL DU) | O-RAN.WG3.TS.E 2SM-KPM [49], clause 7.10.10.1 | E2 | - -| Category | Parameters / Measurements | Source | Reference | Interface | -|--------------------------------------|-----------------------------------------------------------------|------------------|-----------------------------------------------|-----------| -| Total number of scheduled time slots | Cell-specific downlink total failed transmission time duration | O-DU (NRCELL DU) | O-RAN.WG3.TS.E 2SM-KPM [49], clause 7.10.10.2 | E2 | -| Total number of scheduled time slots | Cell-specific downlink retransmission time duration | O-DU (NRCELL DU) | O-RAN.WG3.TS.E 2SM-KPM [49], clause 7.10.10.3 | E2 | -| Total number of scheduled time slots | Cell-specific downlink total SU-MIMO transmission time duration | O-DU (NRCELL DU) | O-RAN.WG3.TS.E 2SM-KPM [49], clause 7.10.10.4 | E2 | -| Total number of scheduled time slots | Cell-specific downlink total MU-MIMO transmission time duration | O-DU (NRCELL DU) | O-RAN.WG3.TS.E 2SM-KPM [49], clause 7.10.10.5 | E2 | -| Transmitted data volume | DL Transmitted Data Volume (MAC SDU) | O-DU (NRCELL DU) | O-RAN.WG3.TS.E 2SM-KPM [49], clause 7.10.11 | E2 | - -The output data specified in table 4.21.4.5.1-2 shall be supported by the associated interfaces specified in the table. - -**Table 4.21.4.5.1-2: Required output data for PA power optimization-based energy saving use case** - -| Category | Parameters / Measurements | Target | Reference | Interface | -|-------------------|---------------------------------------------------------------------------------------|------------|-----------------------------------------------|-----------------| -| NES Policy | NESPolicy - PA power optimization related attributes to be specified. | O-DU | O-RAN.WG10.TS.O1NRM [45] | O1 | -| NES configuration | NES configuration changes - PA power optimization related attributes to be specified. | O-DU | O-RAN.WG10.TS.O1NRM [45] | O1 | -| NES configuration | NES configuration (FH M-Plane) changes | O-DU, O-RU | O-RAN.WG4.MP [28], clause 20.6 | Open FH M-plane | -| NES configuration | NES configuration (FH C-Plane) changes - To be specified. | O-DU, O-RU | O-RAN.WG4.TS.C US.0-R004 [51] | Open FH C-plane | -| NES configuration | Constraints | O-DU, O-RU | O-RAN.WG4.TS.C US.0-R004 [51], clause 8.1.3.3 | Open FH C-plane | - -| Category | Parameters / Measurements | Target | Reference | Interface | -|---------------------|---------------------------|--------|----------------------------------------------|-----------| -| NES configuration | PRB blanking optimization | O-DU | O-RAN.WG3.TS.U CR [46], clause 4.6.4. | E2 | -| PRB blanking policy | O-PRBBlankingPolicy | O-DU | O-RAN.WG3.TS.E 2SM-CCC [47], clause 8.8.2.9. | E2 | - -## 4.22 MU-MIMO optimization - -This use case provides motivation, description, and requirements for a near-real-time MU-MIMO optimization control loop deployment. Deploying MU-MIMO application in the Near-RT RIC enables new solutions that can optimize UE and cell level performance in certain deployments by e.g. deriving channel estimation/prediction and UEs selections with their associated precoding coefficients, resulting in increased per UE and overall cell throughput. - -### 4.22.1 Background and goal of the use case - -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 multiple 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's 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 to TDD as well as FDD and can provide high user and cell performance for subscribers moving within a wide range of speeds. - -The objective of this use case is to allow the operator to improve user throughput and overall cell capacity by deploying an application in the Near-RT RIC that can use information collected from the E2 nodes to calculate and send to the E2 nodes user selections and applicable precoding coefficients in a near real time loop. This use case will also open the door for future expansion of the MU-MIMO to supporting CoMP covering both ICIC and joint multi sites MU-MIMO. - -### 4.22.2 Entities/resources involved in the use case - -- 1) Near-RT RIC - - a) Retrieve cell configuration and UE states from E2 nodes - - b) Send configurations for DL channel estimation reporting and UL SRS and DMRS to the E2 nodes - - c) Retrieve DL/UL traffic, and DL/UL channel quality information from E2 nodes - - d) Use the retrieved information to select the UEs to be spatially multiplexed per frequency and time resources and for each selection calculate the relevant MCS and precoder coefficients for optimal UE and cell throughput - - e) Send the recommended UE selections with their resource assignments, MCS, and precoding coefficients to the E2 nodes. -- 2) E2 nodes - - a) Collect and report to Near-RT RIC information related to cell configuration, UE states, DL/UL traffic, and DL/UL channel quality. - -- b) Apply the configurations received from the Near-RT RIC for DL channel estimation reporting and UL SRS transmissions -- c) Apply MU-MIMO parameters following Near-RT RIC recommendations (while handling time critical events separately). - -### 4.22.3 Solutions - -#### 4.22.3.1 MU-MIMO optimization - -The context of MU-MIMO optimization is captured in table 4.22.3.1-1. - -**Table 4.22.3.1-1: MU-MIMO optimization** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | MU-MIMO optimization using Near-RT RIC control loop. | | -| Actors and Roles |

Near-RT RIC: Configures E2 nodes' measurements, collects data from E2 nodes, performs MU-MIMO optimization function, and sends MIMO recommendations to E2 nodes.

E2 nodes: Report measurements to Near-RT RIC and execute MU-MIMO recommendations.

| | -| Assumptions | E2 connectivity is established between Near-RT RIC and E2 nodes. Network is operational. | | -| Pre-conditions |

All relevant functions and components are instantiated. MU-MIMO optimization xApp is deployed with initial configuration

All relevant subscriptions established on E2 interface.

| | -| Begins when | Pre-conditions are met. | | -| Step 1 (M) | Near-RT RIC initiates data collection from E2 nodes (cell configuration, UE states, RRC connection, UL/DL traffic and channel information). | | -| Step 2 (M) | E2 nodes send cell configuration, UE states, and RRC connection information to Near-RT RIC. | | -| Step 3 (M) | E2 nodes send UL/DL traffic and channel information to Near-RT RIC. | | -| Step 4 (O) | Near-RT RIC sends DL channel estimation reporting and UL SRS and DMRS configuration to E2 nodes. | | -| Step 5 (M) | E2 nodes continuously send UL/DL traffic and channel information to Near-RT RIC. | | -| Step 6 (M) | E2 nodes send updated UE states and RRC connections information to Near-RT RIC. | | -| Step 7 (M) | Near-RT RIC uses the collected information to estimate channels and select UE groupings per ranges of frequency and time resources | | -| Step 8 (M) | Near-RT RIC calculates MCS and precoding coefficients for each selection of UEs. | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 9 (M) | Near-RT RIC sends optimized MU-MIMO parameters (UE selections with their resource assignments, MCS, and precoding coefficients) to E2 nodes. | | -| Step 10 (M) | E2 nodes schedule MU-MIMO transmissions using the parameters received from the Near-RT RIC. | | -| Step 11 (O) | Near-RT RIC sends updated DL channel estimation reporting and UL SRS and DMRS configuration to E2 nodes. | | -| Ends when | Operator disables or uninstalls MU-MIMO optimization xApp. | | -| Exceptions | None identified. | | -| Post Conditions | The E2 nodes operate using the newly received parameters. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "O-RAN" #lightpink - Participant NearRTRIC as "Near-RT RIC" - Participant E2nodes as "O-CU/O-DU" -End box - -NearRTRIC->>E2nodes: <> Initiate data collection -E2nodes->>NearRTRIC: <> Cell configuration, UE state, and RRC connection information -E2nodes->>NearRTRIC: <> UL/DL traffic and channel information -group opt - NearRTRIC->>E2nodes: <> DL channel estimation reporting and UL SRS and DMRS configuration -end - -group MU-MIMO Optimization Loop - E2nodes->>NearRTRIC: <> UL/DL traffic and channel information - E2nodes->>NearRTRIC: <> RRC connections and UE states update - NearRTRIC->>NearRTRIC: UE selections and Channel estimation - NearRTRIC->>NearRTRIC: MU-MIMO parameters calculations -end - -``` - -``` - -NearRTRIC->E2nodes: <> Optimized MU-MIMO parameters - -E2nodes->E2nodes: Schedule MU-MIMO transmissions using received parameters - -group opt - - NearRTRIC->E2nodes: <> Updated DL channel estimation reporting and UL SRS and - DMRS configuration - -end - -end - -@enduml - -``` - -The flow diagram of MU-MIMO optimization is given in figure 4.22.3.1-1. - -![Sequence diagram showing MU-MIMO optimization flow between Near-RT RIC and O-CU/O-DU. The process involves data collection, configuration updates, a loop for traffic and channel information, UE selection, parameter calculation, and finally scheduling transmissions.](5a7ef674d3d47e22615920f270a52b5a_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC - participant O-CU/O-DU - Note right of O-CU/O-DU: O-RAN - - Near-RT RIC->>O-CU/O-DU: 1 <> Initiate data collection - O-CU/O-DU-->>Near-RT RIC: 2 <> Cell configuration, UE state, and RRC connection information - O-CU/O-DU-->>Near-RT RIC: 3 <> UL/DL traffic and channel information - - opt - Near-RT RIC->>O-CU/O-DU: 4 <> DL channel estimation reporting and UL SRS and DMRS configuration - end - - loop MU-MIMO Optimization Loop - O-CU/O-DU-->>Near-RT RIC: 5 <> UL/DL traffic and channel information - O-CU/O-DU-->>Near-RT RIC: 6 <> RRC connections and UE states update - Near-RT RIC->>Near-RT RIC: 7 UE selections and Channel estimation - Near-RT RIC->>Near-RT RIC: 8 MU-MIMO parameters calculations - Near-RT RIC->>O-CU/O-DU: 9 <> Optimized MU-MIMO parameters - O-CU/O-DU->>O-CU/O-DU: 10 Schedule MU-MIMO transmissions using received parameters - - opt - Near-RT RIC->>O-CU/O-DU: 11 <> Updated DL channel estimation reporting and UL SRS and DMRS configuration - end - end - - Note right of O-CU/O-DU: O-RAN - -``` - -Sequence diagram showing MU-MIMO optimization flow between Near-RT RIC and O-CU/O-DU. The process involves data collection, configuration updates, a loop for traffic and channel information, UE selection, parameter calculation, and finally scheduling transmissions. - -**Figure 4.22.3.1-1: MU-MIMO optimization flow diagram** - -### 4.22.4 Required data - -The Near-RT RIC requires different types of data from the E2 nodes as summarized below with examples: - -- 1) Cell configuration information (e.g., frequency and BW, FDD/TDD, SCS, UL-DL configuration) -- 2) List of connected UEs -- 3) UE connection updates (setup, release, handover) -- 4) UE RRC state changes (connected, inactive, idle) - -- 5) UL channel information (e.g., SRS, ACK/NACK counts) -- 6) DL channel information (e.g., CQI, RI, PMI, ACK/NACK counts) -- 7) DL PDCP and RLC buffer status and UL BSR - -## 4.23 Sharing Non-RT RIC data with the core - -Void - -## 4.24 Industrial vision SLA assurance - -This use case provides the background and motivation for the O-RAN architecture to support industrial vision Service-Level Agreement (SLA) assurance. Moreover, some high-level description and requirements over Non-RT RIC, A1 and E2 interfaces are introduced. - -### 4.24.1 Background and goal of the use case - -Industrial vision is an image recognition technology used for work piece inspecting, processing and assembling automation, as well as the monitoring and controlling of production process by replacing human eyes with cameras for various measurements and judgments. The main feature of industrial vision system is that it needs to collect the images of the products to be tested or processed in the area with dense production lines, and then transmit the images to the vision server for detection and feed back the results. - -Because the industrial vision system shall accommodate to the production speed of the production line, there are strict delay and reliability requirements for visual acquisition, transmission, judgment and execution. For example, a production line which processes 8000 work pieces per hour has an operation interval of 450ms for each product in the production line. Considering the image recognition, results execution time and the mechanical execution time, the two-way data transmission delay left for the transmission network is even less. When 5G is applied in the industrial vision business scenario, the main challenge is the assurance of image data transmission delay and reliability of 5G wireless network in an ultra-dense networking environment. - -5G pre-scheduling technology is introduced to reduce the transmission delay and improve the transmission reliability. However, the traditional static pre-scheduling mechanism could not adapt to changing production environments. It always allocates fixed air interface resource according to the static configuration, regardless of the actual data arrival, resulting mis-alignment of resource allocation and uplink transmission needs, causing increased and unstable delay, waste of PRB resources and significant decline in the actual bearable traffic of the cell. - -Therefore, dynamic pre-scheduling, which allocates uplink resources according to actual work piece arrival time, is deemed to be a more efficient way to enable industrial vision deployment in production line. In O-RAN, RIC can be used to dynamically optimize the pre-scheduling parameters, so that accurate matching between uplink data arrival and uplink transmission resource allocation could be achieved. This helps to reduce uplink transmission delay and improve the resource efficiency. - -With enrichment information from application server/Manufacturing Execution System (MES), e.g., production-line and industrial camera configuration and image transmission delay related data, Near-RT RIC can calculate and iteratively update pre-scheduling parameter (e.g., pre-scheduling data size, pre-scheduling period and pre-scheduling start time), and send those parameters to E2 nodes via E2 interface. 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. - -One example method to transmit Non-RAN application server/MES data into Non-RT RIC is through SMO external interface. Application server/MES is registered as SMO external system, which serves as a data source outside the O-RAN domain that provides data to the SMO. By leveraging SMO external interface (the interface between the SMO and an SMO external system), production-line and industrial camera configuration and image transmission delay related data is transmitted to SMO as enrichment information, which is consumed by Non-RT RIC and bypassed to Near-RT RIC through A1. - -### 4.24.2 Entities/resources involved in the use case - -- 1) Non-RT RIC: - - a) Support communication of non-RAN data to enrich control functions in Near-RT RIC (enrichment information). -- 2) Near-RT RIC: - - a) Support communication of pre-scheduling configuration parameters to E2 node. -- 3) E2 node: - - a) Support pre-scheduling parameters configuration over E2 interface. - - b) Report necessary performance, configuration, and other data for performing pre-scheduling parameter configuration in the Near-RT RIC over E2 interface. -- 4) Application server/ MES: - - a) Support communication of non-RAN data about production line information and data transmission information to Non-RT RIC as enrichment information. - -### 4.24.3 Solutions - -The context of industrial vision assurance is captured in table 4.24.3-1. - -**Table 4.24.3-1: Industrial vision assurance** - -| Use Case Stage | Evolution / Specification | <> | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Goal | Meeting industrial vision service SLA requirement via dynamic pre-scheduling parameter configuration. | | -| Actors and Roles | Non-RT RIC, Near-RT RIC, E2 node, application server/ MES | | -| Assumptions | All relevant functions and components are instantiated.
A1, E2 interface connectivity is established. | | -| Pre-conditions | Near-RT RIC and Non-RT RIC are instantiated with A1 interface connectivity being established between them.
E2 interface is established between Near-RT RIC and E2 node. | | -| Begins when | Production line is started. Periodical industrial vision service is started. | | -| Step 1 (M) | MES sends the production-line and industrial camera configuration related data to the Non-RT RIC. | | -| Step 2 (M) | The Non-RT RIC sends the enrichment information to the Near-RT RIC over the A1 interface. | | -| Step 3 (M) | Based on the received production-line and industrial camera configuration related enrichment information from the Non-RT RIC over the A1 interface, the Near-RT RIC sends initial time-domain pre-scheduling parameters, which includes pre-scheduling data size, pre-scheduling period and pre-scheduling start time, to the E2 node. | | -| Step 4 (M) | Industrial vision application server sends the image data transmission delay related enrichment data to the Non-RT RIC. | | -| Step 5 (M) | The E2 node and the Non-RT RIC sends service data transmission information, which includes relevant measurement (e.g., pre-scheduling time-domain resource utilization which is the ratio of the time-domain resource of the data to be scheduled to the total pre-scheduled time-domain resource, and the image data transmission delay related enrichment information) to the Near-RT RIC.

Near-RT RIC receives the service data transmission information and then based on those information, evaluates the performance of the pre-scheduling and iteratively updates pre-scheduling start time. Then the Near-RT RIC sends the updated pre-scheduling start time to the E2 node over E2 interface. | | -| Step 6 (M) | Based on the pre-scheduling data size, pre-scheduling period and pre-scheduling start time received from the Near-RT RIC, E2 node pre-schedules the time-domain resource for the terminal device. Repeat step 4, 5, 6 until the situation in step “Ends when” is met. | | -| Ends when | When the industrial vision service data transmission information (including pre-scheduling time-domain resource utilization fed back from E2 node and the image data transmission delay related enrichment information from the Non-RT RIC) becomes stable within reasonable range, the Near-RT RIC stops updating the pre-scheduling start time. | | -| Exceptions | None identified. | | - -| | | | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Post Conditions | The Non-RT RIC monitors the service performance by collecting and monitoring the relevant performance KPIs and counters from the RAN and the application server. | | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| - -``` - -@startuml -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Box "Service Management and Orchestration" #gold - Participant non as "Non-RT RIC" -End box - -Box "O-RAN" #lightpink - Participant near as "Near-RT RIC" - Participant ran as "E2 Node" -End box - -Box "External" #lightblue - Participant server as "Application Server/MES" -End box - -server -> non : 1 Production-line and industrial camera configuration related data -non -> near : 2 <> Enrichment information -near -> near: Calculate pre-scheduling parameters (e.g. pre-scheduling data size, period and start time) -near -> ran :3 <> Initial pre-scheduling parameters configuration -server -> server: Image data processing -loop - - server -> non : 4 Image data transmission delay related enrichment data - non -> near : 5.1 <> Image data transmission delay related Enrichment Information - ran -> near : 5.2 <> Pre-scheduling time-domain resource utilization - near -> near :5.3 Evaluates performance of the pre-scheduling and updates pre-scheduling start time - -``` - -``` - -alt If performance data is out of resonable range - near -> near : Pre-scheduling parameters re-calculation(e.g.,pre-scheduling start time) - near -> ran : 5.4 <> New pre-scheduling start time - ran -> ran: 6 pre-schedules the time-domain resource for the terminal device -else If performance data is stable within resonable range - note over near - Loop ends - end note -end -end -@enduml - -``` - -The flow diagram of industrial vision assurance use case is given in figure 4.24.3-1. - -![Sequence diagram for industrial vision assurance use case showing interactions between Service Management and Orchestration (Non-RT RIC), O-RAN (Near-RT RIC, E2 Node), and External (Application Server/MES).](a56d6272a0cbbd2cf3f1ecbf1d2f9732_img.jpg) - -``` - -sequenceDiagram - participant SMO as Service Management and Orchestration (Non-RT RIC) - box "O-RAN" - participant Near-RT RIC - participant E2 Node - end - participant External as External (Application Server/MES) - - SMO->>Near-RT RIC: 1 Production-line and industrial camera configuration related data - SMO->>Near-RT RIC: 2 *A1* Enrichment information - Near-RT RIC->>Near-RT RIC: Calculate pre-scheduling parameters (e.g. pre-scheduling data size, period and start time) - Near-RT RIC->>E2 Node: 3 *E2* Initial pre-scheduling parameters configuration - External->>External: Image data processing - - rect rgb(255, 255, 0) - Note over SMO, Near-RT RIC: loop - SMO->>Near-RT RIC: 4 image data transmission delay related enrichment data - SMO->>Near-RT RIC: 5.1 *A1* image data transmission delay related Enrichment information - E2 Node->>Near-RT RIC: 5.2 *E2* Pre-scheduling time-domain resource utilization - Near-RT RIC->>Near-RT RIC: 5.3 Evaluates performance of the pre-scheduling and updates pre-scheduling start time - - alt If performance data is out of resonable range - Near-RT RIC->>Near-RT RIC: Pre-scheduling parameters re-calculation(e.g.,pre-scheduling start time) - Near-RT RIC->>E2 Node: 5.4 *E2* New pre-scheduling start time - E2 Node->>E2 Node: 6 pre-schedules the time-domain resource for the terminal device - else If performance data is stable within resonable range - Note over Near-RT RIC: Loop ends - end - end - -``` - -Sequence diagram for industrial vision assurance use case showing interactions between Service Management and Orchestration (Non-RT RIC), O-RAN (Near-RT RIC, E2 Node), and External (Application Server/MES). - -**Figure 4.24.3-1: Industrial vision assurance use case flow diagram** - -### 4.24.4 Required data - -Enrichment information are expected to be retrieved by Non-RT RIC for industrial vision SLA assurance. Service data transmission information from E2 node are also expected to be collected by Near-RT RIC for industrial vision assurance. - -- 1) Enrichment information: - - a. Production-line and industrial vision camera configuration related data, e.g. production line speed, image color, pixel. (collected from application server/MES) - - b. Service-related performance measurement metrics collected from application server, e.g., image data transmission delay. (collected from application server/MES) -- 2) Service data transmission information: e.g., pre-schedule time-domain resource utilization, which is the ratio of the time-domain resource of the data to be scheduled to the total pre-scheduled time-domain resource. (new E2 measurements) - -## 4.25 Void - -## 4.26 Interference detection, prediction and optimization - -This use case provides the background and motivation for the O-RAN architecture to support real-time interference detection and optimization. Moreover, some high-level description and requirements over Non-RT RIC, A1, Near-RT RIC and E2 interfaces are introduced. - -### 4.26.1 Background and goal of the use case - -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 includes 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, with low real-time. - -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. - -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 A1 policy as well as interference relationships, Near-RT RIC ensures optimal radio resource allocation for UE or UE group or RAN slice or PRBs or mMIMO beams 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 for UE to adapt to fluctuating interference. - -### 4.26.2 Entities/resources involved in the use case - -- 1) SMO/Non-RT RIC: - -- a) Generate and send interference detection, prediction and optimization policies to Near-RT RIC. - - b) Retrieve QoS related metrics and send to Near-RT RIC. - - c) Receive interference detection, prediction and optimization performance evaluation updates from Near-RT RIC. - - d) Receive interference related network level measurement data from gNBs. - - e) Generate and send radio resources configuration based on the interference optimization policy to E2 nodes. -- 2) Near-RT RIC: -- a) Retrieve necessary interference related measurement metrics from network level (cell level) measurement report through E2 interface. - - b) Receive interference detection, prediction and optimization policies from Non-RT RIC, and support interpretation and execution of Non-RT RIC policies to derive the interference detection, prediction and optimization control or policy. - - c) Send the controls or policies to E2 nodes through E2 interface for interference detection, prediction and optimization. - - d) Send interference performance report to Non-RT RIC for evaluation and optimization -- 3) E2 node: -- a) Support network state and UE measurements with required granularity to Near-RT RIC over E2 interface. - - b) Support interference configurations and enhancements based on messages from E2, which are expected to influence RRM behavior. - - c) Receive interference detection, prediction results from UE and network, and report to Near-RT RIC. - - d) Update RAN parameters based on radio resources configuration from the SMO/Non-RT RIC over the O1 interface. - -### 4.26.3 Solutions - -#### 4.26.3.1 Fast loop optimization - -##### 4.26.3.1.1 Interference detection - -The context of the interference detection is captured in table 4.26.3.1.1-1. - -**Table 4.26.3.1.1-1: Interference detection** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Interference detection | | -| 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 | Near-RT RIC and Non-RT RIC are instantiated with A1 interface connectivity being established between them. | | -| Begins when | Near-RT RIC triggers interference detection. | | -| Step 1-2 (M) | Non-RT RIC generates interference detection policy and sends the policy to Near-RT RIC via A1 interface. | | -| Step 3 (M) | Near-RT RIC receives A1 policy, converts and generates E2 control or policy. E2 control or 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) information for UL PRBs to be monitored; 4) for example, for mMIMO deployment scenario, information for mMIMO beams to be monitored. | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| |

The reference signal can be NZP CSI-RS and ZP CSI-IM, which is used by UE(S) accessed in the gNB(S) for channel measurement, channel estimation and interference measurement respectively:

  • a) For channel measurement and channel estimation reference signal: based on the Information transmission strategy, intra-frequency cells adjacent to the cells corresponding to the gNB(S), such as the cells corresponding to gNB(N), keep silent at the allocated resource(s) of the reference signal.
  • b) For interference measurement reference signal: based on the Information transmission strategy, intra-frequency cells adjacent to the cells corresponding to the gNB(S), such as the cells corresponding to gNB(N), can send data at the allocated resource(s) of the reference signal.
| | -| Step 4, 6 (M) | Near-RT RIC sends E2 control or policy to the target gNBs via E2 interface, such as sending allocated resource(s) of the reference signal for the gNB(S), sending information transmission strategy to the intra-frequency cells adjacent to the cells corresponding to the gNB(S), for example the cells corresponding to gNB(N), and sending information for UL PRBs and for mMIMO deployment scenario mMIMO beams to be monitored. | | -| Step 5,7 (M) |

gNB(S) allocates resources for reference signal based on the E2 control or policy. gNB(N) allocates resources for DL data transmission to UE(N). gNB(N) allocates resources for UL data transmission. gNB(S) allocates resources for UL PRBs and for mMIMO deployment scenario mMIMO beams to be monitored.

| | -| Step 8-10 (M) |

gNB(S) sends reference signal at allocated resources to UE(S). UE detects interference based on the reference signal configured by gNB(S) and sends the interference detection results to the Near-RT RIC through RAN.

gNB(S) detects uplink interference based on interference levels and patterns of UL PRBs among intra-frequency cells and sends the interference detection results to the Near-RT RIC.

gNB(S) detects interference levels of mMIMO beams among intra-frequency cells and sends the interference detection results to the Near-RT RIC.

| | -| Step 11-20 (O) | If required, Near-RT RIC can configure specific performance measurement data to be collected from RAN to monitor the performance of E2 control or policy and sends the result to Non-RT RIC for updating the A1 and E2 policies based on the performance evaluation results. | | -| Ends when | Operator triggers to stop interference detection. | | -| Exceptions | None identified. | | -| Post Conditions | | | - -The flow diagram of the interference detection is given in figure 4.26.3.1.1-1. - -![Sequence diagram showing the interference detection flow between Service Management and Orchestration (Non-RT RIC), Near-RT RIC, E2 nodes, and UE(s).](56a00f931e8602f822917af7fa379c0d_img.jpg) - -The sequence diagram illustrates the interaction for interference detection. It starts with the **Service Management and Orchestration** (Non-RT RIC) sending **A1 policies** (1. Interference detection policy generation, 2. «A1»Interference detection policy) to the **Near-RT RIC**. The **Near-RT RIC** then sends **E2 control or policy** messages (3. E2 control or policy generation, 4. «E2» control or policy message) to the **E2 node(S)**. The **E2 node(S)** allocate resources (5. allocate resource(s) for DL reference signal, 6. allocate resources for UL PRBs to be monitored, 7. allocate resources for mMIMO beams to be monitored) and send **E2» control or policy message** (8) to the **Near-RT RIC**. The **Near-RT RIC** then sends **E2» control or policy message** (8) to the **E2 node(N)**. The **E2 node(N)** allocate resources (9. allocate resource(s) for DL data transmission, 10. allocate resource(s) for UL data transmission) and send **reference signal** (11) to the **UE(S)**. The **UE(S)** send **reference signal measurement result** (12) to the **E2 node(N)**, which then send **E2» reference signal measurement result** (13) to the **Near-RT RIC**. The **E2 node(S)** send **E2» UL PRBs measurement result** (14) and **E2» mMIMO beams measurement result** (15) to the **Near-RT RIC**. The **Near-RT RIC** then enters a **Performance evaluation and optimization** phase. It sends **E2» Data collection** (16) and **Performance monitoring & evaluation** (17) to the **E2 node(S)**. The **E2 node(S)** send **A1»Performance monitoring & evaluation result** (18) to the **Near-RT RIC**. The **Near-RT RIC** then sends **Update A1 policy** (19) and **A1»policy update** (20) to the **Non-RT RIC**. The **Near-RT RIC** also sends **E2»Data Data collection** (21) and **Resource allocation** (22) to the **E2 node(N)**. The **E2 node(N)** send **Update E2 control or policy** (23) to the **Near-RT RIC**. The **Near-RT RIC** then sends **E2»control or policy update** (24) and **E2»control or policy update** (25) to the **E2 node(S)**. - -Sequence diagram showing the interference detection flow between Service Management and Orchestration (Non-RT RIC), Near-RT RIC, E2 nodes, and UE(s). - -Figure 4.26.3.1.1-1: Interference detection flow diagram - -``` -@startuml -Skin rose -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-RT RIC" as near - participant "E2 node(S)" as s - participant "E2 node(N)" as n -``` - -``` - participant "UE(S)" as ues -end box - -group A1 policies -non -> non : Interference detection policy generation -non -> near : <>Interference detection policy -end - -group E2 control or policy -near -> near : E2 control or policy generation -near -> s : <> control or policy message -s -> s : allocate resource(s) for DL reference signal -s -> s : allocate resources for UL PRBs to be monitored -s -> s : allocate resources for mMIMO beams to be monitored -near -> n : <> control or policy message -n -> n : allocate resource(s) for DL data transmission -n -> n : allocate resource(s) for UL data transmission -s -> ues: reference signal -ues -> s: reference signal measurement result -s -> near : <> reference signal measurement result -s -> near : <> UL PRBs measurement result -s -> near : <> mMIMO beams measurement result -end - -group Performance evaluation and optimization -alt if need to update A1 policy and E2 control or policy -s -> near : <> Data collection -near -> near : Performance monitoring & evaluation -near -> non : <>Performance monitoring & evaluation result -non -> non : Update A1 policy -non -> near : <>policy update -s -> near : <>Data collection -near -> near : Resource allocation -near -> near : Update E2 control or policy -near -> s : <>control or policy update -``` - -``` -near -> n : <>control or policy update - -end alt - -end - -@enduml -``` - -##### 4.26.3.1.2 Interference relationships construction - -The context of the interference relationships construction is captured in table 4.26.3.1.2-1. - -**Table 4.26.3.1.2-1: Interference relationships construction** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Interference relationships construction | | -| Actors and Roles | Near-RT RIC, gNB | | -| Assumptions | All relevant functions and components are instantiated.
E2 interface connectivity is established with Near-RT RIC. | | -| Pre-conditions | Interference detection results have been sent to Near-RT RIC. | | -| Begins when | Near-RT RIC triggers interference relationship construction. | | -| Step 1-4 (M) | QoS related metrics from SMO and network level measurements reported by RAN through E2 interface are reported to Near-RT RIC for instantiating or modifying interference relationships. | | -| Step 5 (M) | Near-RT RIC constructs interference relationships (e.g., interference graph) based on the received QoS related metrics from SMO and network level measurement from RAN.

Near-RT RIC constructs uplink interference relationships among intra-frequency cells based on the interference levels and patterns of UL PRBs.

Near-RT RIC constructs interference relationships among mMIMO beams located at different intra-frequency cells based on interference levels of mMIMO beams.

Near-RT RIC uses interference relationships for further interference optimization. | | -| Step 6-8 (O) | If required, Near-RT RIC can configure specific performance measurement data to be collected from RAN to assess the performance of the interference relationships and update the interference relationships in Near-RT RIC based on the performance evaluation and model retraining. | | -| Ends when | Operator specified trigger condition or event is satisfied. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|----------------------------------------------------------------------------------------------------------|-------------------------| -| Exceptions | None identified. | | -| Post Conditions | Near-RT RIC stores the interference relationships for interference optimization function in Near-RT RIC. | | - -The flow diagram of the interference relationships construction is given in figure 4.26.3.1.2-1. - -![Sequence diagram showing the interference relationships construction flow. Lifelines: Non-RT RIC (Service Management and Orchestration), Near-RT RIC, gNB(S), gNB(N) (O-RAN). The process involves QoS metrics exchange, data collection from gNBs, construction of interference relationships, and a performance evaluation loop that may update the relationships.](0a7bd7c5b5e975e353b207d6845215c1_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC as Non-RT RIC - participant Near-RT RIC as Near-RT RIC - participant gNB_S as gNB(S) - participant gNB_N as gNB(N) - - Note left of Non-RT RIC: Service Management and Orchestration - Note right of gNB_N: O-RAN - - Non-RT RIC->>Near-RT RIC: 1 <> QoS related metrics - Near-RT RIC->>gNB_S: 2 <> Data collection - Near-RT RIC->>gNB_N: 3 <> Data collection - Note right of Near-RT RIC: Interference relationships construction - Near-RT RIC->>Near-RT RIC: 4 interference relationships construction - Note right of Near-RT RIC: Performance evaluation and optimization - alt if need to update interference relationship - Near-RT RIC->>gNB_S: 5 <> Data collection - Near-RT RIC->>Near-RT RIC: 6 Performance monitoring & evaluation - Near-RT RIC->>Near-RT RIC: 7 interference relationships update - end - -``` - -Sequence diagram showing the interference relationships construction flow. Lifelines: Non-RT RIC (Service Management and Orchestration), Near-RT RIC, gNB(S), gNB(N) (O-RAN). The process involves QoS metrics exchange, data collection from gNBs, construction of interference relationships, and a performance evaluation loop that may update the relationships. - -Figure 4.26.3.1.2-1: Interference relationships construction flow diagram - -``` - -@startuml -Skin rose -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" #rose - participant Near-RT RIC - participant gNB_S as gNB(S) - participant gNB_N as gNB(N) -end box - -Non-RT RIC->>Near-RT RIC: 1 <> QoS related metrics -Near-RT RIC->>gNB_S: 2 <> Data collection -Near-RT RIC->>gNB_N: 3 <> Data collection -Note right of Near-RT RIC: Interference relationships construction -Near-RT RIC->>Near-RT RIC: 4 interference relationships construction -Note right of Near-RT RIC: Performance evaluation and optimization -alt if need to update interference relationship - Near-RT RIC->>gNB_S: 5 <> Data collection - Near-RT RIC->>Near-RT RIC: 6 Performance monitoring & evaluation - Near-RT RIC->>Near-RT RIC: 7 interference relationships update -end - -``` - -``` -Box "O-RAN" #lightpink - participant "Near-RT RIC" as near - participant "gNB(S)" as s - participant "gNB(N)" as n -end box - -non -> near : <> QoS related metrics -near <- s : <> Data collection -near <- n : <> Data collection -group Interference relationships construction - near -> near : interference relationships construction -end - -group Performance evaluation and optimization -alt if need to update interference relationship - s -> near: <> Data collection - near -> near : Performance monitoring & evaluation - near -> near : interference relationships update -end alt -end - -@enduml -``` - -##### 4.26.3.1.3 Interference optimization - -The context of the interference optimization is captured in table 4.26.3.1.3-1. - -**Table 4.26.3.1.3-1: Interference optimization** - -| Use Case Stage | Evolution / Specification | <> | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Goal | Interference optimization 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 | Interference relationships required by interference optimization have been constructed by Near-RT RIC. | | -| Begins when | The network operator/manager want to generate interference optimization policy based on user QoS. | | -| Step 1 (M) | Non-RT RIC generates the appropriate interference optimization policy based on the configured QoS parameters. | | -| Step 2 (M) | Non-RT RIC sends the interference optimization policy to Near-RT RIC via A1 interface. | | -| Step 3 (M) | Network level measurements reported by RAN through E2 interface are reported to Near-RT RIC. | | -| Step 4 (M) | Near-RT RIC receives the policy from the Non-RT RIC over the A1 interface and measurement data from the RAN over the E2 interface. Near-RT RIC generates radio resources configuration based on the interference relationships (e.g., interference graph) as well as A1 policy. | | -| Step 5 (M) | Near-RT RIC sends the radio resources configuration through E2 interface towards RAN for interference optimization. RAN enforces the received control or policy from the Near-RT RIC over the E2 interface. | | -| Step 6-12 (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 | If required, Near-RT RIC can configure specific performance measurement data to be collected from RAN to monitor the performance of E2 control or policy and sends the result to Non-RT RIC for updating the A1 and E2 policies based on the performance evaluation results. | | - -The flow diagram of the interference optimization is given in figure 4.26.3.1.3-1. - -![Sequence diagram showing interference optimization flow between Service Management and Orchestration (Non-RT RIC) and O-RAN (Near-RT RIC, gNB).](8abd61b74f37672d2b282ed022beab0f_img.jpg) - -``` - -sequenceDiagram - participant SM as Service Management and Orchestration - participant NonRT as Non-RT RIC - subgraph O-RAN - participant NearRT as Near-RT RIC - participant gNB as gNB - end - - Note right of NonRT: A1 policies - Note right of NearRT: E2 control/policy - Note right of NonRT: Performance evaluation and optimization - - Note left of NonRT: 1 Interference optimization policy generation - Note right of NonRT: 2 <> Interference optimization policy - Note left of NearRT: 3 <> Data collection - Note left of NearRT: 4 radio resources configuration generation - Note right of NearRT: 5 <> radio resources configuration - Note left of NearRT: 6 <> Data collection - Note left of NearRT: 7 Performance monitoring & evaluation - Note right of NearRT: 8 <> Performance monitoring & evaluation result - Note left of NonRT: 9 Update A1 policy - Note right of NonRT: 10 <> policy update - Note left of NearRT: 11 radio resources configuration update - Note right of NearRT: 12 <> radio resources configuration update - - SM->>NonRT: 1 Interference optimization policy generation - NonRT->>NonRT: 2 <> Interference optimization policy - NonRT->>NearRT: 3 <> Data collection - NearRT->>NearRT: 4 radio resources configuration generation - NearRT->>gNB: 5 <> radio resources configuration - gNB->>NearRT: 6 <> Data collection - NearRT->>NearRT: 7 Performance monitoring & evaluation - NearRT->>NonRT: 8 <> Performance monitoring & evaluation result - NonRT->>NonRT: 9 Update A1 policy - NonRT->>NearRT: 10 <> policy update - NearRT->>NearRT: 11 radio resources configuration update - NearRT->>gNB: 12 <> radio resources configuration update - -``` - -Sequence diagram showing interference optimization flow between Service Management and Orchestration (Non-RT RIC) and O-RAN (Near-RT RIC, gNB). - -Figure 4.26.3.1.3-1: Interference optimization flow diagram - -``` - -@startuml -Skin rose -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-RT RIC" - participant "gNB" -end box - -Note right of Non-RT RIC: A1 policies -Note right of Near-RT RIC: E2 control/policy -Note right of Non-RT RIC: Performance evaluation and optimization - -Note left of Non-RT RIC: 1 Interference optimization policy generation -Note right of Non-RT RIC: 2 <> Interference optimization policy -Note left of Near-RT RIC: 3 <> Data collection -Note left of Near-RT RIC: 4 radio resources configuration generation -Note right of Near-RT RIC: 5 <> radio resources configuration -Note left of Near-RT RIC: 6 <> Data collection -Note left of Near-RT RIC: 7 Performance monitoring & evaluation -Note right of Near-RT RIC: 8 <> Performance monitoring & evaluation result -Note left of Non-RT RIC: 9 Update A1 policy -Note right of Non-RT RIC: 10 <> policy update -Note left of Near-RT RIC: 11 radio resources configuration update -Note right of Near-RT RIC: 12 <> radio resources configuration update - -SM->>NonRT: 1 Interference optimization policy generation -NonRT->>NonRT: 2 <> Interference optimization policy -NonRT->>NearRT: 3 <> Data collection -NearRT->>NearRT: 4 radio resources configuration generation -NearRT->>gNB: 5 <> radio resources configuration -gNB->>NearRT: 6 <> Data collection -NearRT->>NearRT: 7 Performance monitoring & evaluation -NearRT->>NonRT: 8 <> Performance monitoring & evaluation result -NonRT->>NonRT: 9 Update A1 policy -NonRT->>NearRT: 10 <> policy update -NearRT->>NearRT: 11 radio resources configuration update -NearRT->>gNB: 12 <> radio resources configuration update - -``` - -``` - - participant "Near-RT RIC" as near - - participant "gNB" as s - -end box - -group A1 policies - -non -> non: Interference optimization policy generation -non -> near : <> Interference optimization policy -end - -group E2 control/policy - - near <- s : <> Data collection - - near -> near: radio resources configuration generation - - near -> s: <> radio resources configuration - -end - -group Performance evaluation and optimization - -alt if need to update A1 policy and E2 control or policy - - s -> near: <> Data collection - - near -> near : Performance monitoring & evaluation - - near -> non: <> Performance monitoring & evaluation result - - non -> non: Update A1 policy - - non -> near: <> policy update - - near -> near : radio resources configuration update - - near -> s: <> radio resources configuration update - -end alt - -end - -@enduml - -``` - -#### 4.26.3.2 Slow loop optimization - -##### 4.26.3.2.1 Interference detection and relationships construction - -The context of the interference detection and relationships construction is captured in table 4.26.3.2.1-1. - -**Table 4.26.3.2.1-1: Interference detection and relationships construction** - -| Use Case Stage | Evolution / Specification | <> | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Goal | Interference detection and relationships construction | | -| Actors and Roles | SMO/Non-RT RIC, gNB | | -| Assumptions | All relevant functions and components are instantiated.
O1 interface connectivity is established with SMO/Non-RT RIC.
SMO/Non-RT RIC has RAN topology including the relationship of geographical location among cells. | | -| Pre-conditions | Network level measurement data generated at gNBs through O1 interface are reported to SMO/Non-RT RIC. | | -| Begins when | SMO/Non-RT RIC triggers interference detection and relationship construction. | | -| Step 1 (M) | SMO/Non-RT RIC collects the interference data and RB usage rate as network level measurement data from gNBs. | | -| Step 2 (M) | SMO/Non-RT RIC analyzes the interference relationship among cells based on the network level measurement data and the RAN topology. SMO/Non-RT RIC constructs interference relationships (e.g., interference graph) based on network level measurement data from gNBs. The interference relationships indicate a table for each cell, listing the neighboring cells that have a significant interference impact. | | -| Step 3-5 (O) | If required, SMO/Non-RT RIC can update the interference relationships based on the network level measurement data and the RAN topology. | | -| Ends when | Operator specified trigger condition or event is satisfied. | | -| Exceptions | None identified. | | -| Post Conditions | SMO/Non-RT RIC stores the interference relationships. | | - -The flow diagram of the interference detection and relationships construction is given in figure 4.26.3.2.1-1. - -![Sequence diagram showing interference detection and relationships construction flow between Service Management and Orchestration (SMO/Non-RT RIC) and O-RAN (gNBs).](b6f547443a63be9de3a9aedf66f517b2_img.jpg) - -``` - -sequenceDiagram - participant SMO/Non-RT RIC as SMO/Non-RT RIC - participant gNBs as gNBs - Note right of SMO/Non-RT RIC: Interference relationships construction - Note right of SMO/Non-RT RIC: Performance evaluation and optimization - alt if need to update interference relationship - Note right of SMO/Non-RT RIC: Performance monitoring & evaluation - end - SMO/Non-RT RIC->>gNBs: 1 «O1» Data collection - SMO/Non-RT RIC->>SMO/Non-RT RIC: 2 interference relationships construction - alt if need to update interference relationship - SMO/Non-RT RIC->>gNBs: 3 «O1» Data collection - SMO/Non-RT RIC->>gNBs: 4 Performance monitoring & evaluation - SMO/Non-RT RIC->>SMO/Non-RT RIC: 5 interference relationships update - end - -``` - -Sequence diagram showing interference detection and relationships construction flow between Service Management and Orchestration (SMO/Non-RT RIC) and O-RAN (gNBs). - -Figure 4.26.3.2.1-1: Interference detection and relationships construction flow diagram - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "Service Management and Orchestration" #gold - participant "SMO/Non-RT RIC" as non -end box - -Box "O-RAN" #lightpink - participant "gNBs" as g -end box - -non <- g : <> Data collection -group Interference relationships construction - non -> non : interference relationships construction -end - -``` - -``` - -group Performance evaluation and optimization - -alt if need to update interference relationship - g -> non: <> Data collection - non -> non : Performance monitoring & evaluation - non -> non : interference relationships update -end alt -end - -@enduml - -``` - -##### 4.26.3.2.2 Interference optimization - -The context of the interference optimization is captured in table 4.26.3.2.2-1. - -**Table 4.26.3.2.2-1: Interference optimization** - -| Use Case Stage | Evolution / Specification | <> | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Goal | Interference optimization policy generation and performance evaluation | | -| Actors and Roles | SMO/Non-RT RIC, gNB | | -| Assumptions | All relevant functions and components are instantiated. O1 interface connectivity is established with SMO/Non-RT RIC. | | -| Pre-conditions | Interference relationships required by interference optimization have been constructed by SMO/Non-RT RIC. | | -| Begins when | The network operator/manager want to generate interference optimization policy based on the interference relationship. | | -| Step 1-2 (M) | SMO/Non-RT RIC can monitor the performance and creates cell groups for interference optimization based on the interference relationship and network level measurement data | | -| Step 3 (M) | SMO/Non-RT RIC generates the appropriate interference optimization policy based on the network level measurement data. Non-RT RIC creates the radio resources configuration based on the interference optimization policy for each cell group. | | -| Step 4 (M) | SMO/Non-RT RIC sends the radio resources configuration through O1 interface to the cell group. gNBs update the RAN parameters based on radio resources configuration from the SMO/Non-RT RIC over the O1 interface. | | -| Step 5-7 (O) | If required, SMO/Non-RT RIC can update the optimization policy based on the network level measurement data and the RAN topology. SMO/Non-RT RIC updates the radio resources configuration and sends the radio resources configuration through O1 interface to the cell group. | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|-------------------------------------------------------------|-------------| -| | | Related use | -| Ends when | Operator specified trigger condition or event is satisfied. | | -| Exceptions | None identified. | | -| Post Conditions | | | - -The flow diagram of the interference optimization is given in figure 4.26.3.2.2-1. - -![Sequence diagram showing the interference optimization flow between Service Management and Orchestration (SMO/Non-RT RIC) and O-RAN (gNBs).](fa054fa02ab72ff83b76d80c22078856_img.jpg) - -``` - -sequenceDiagram - participant SMO/Non-RT RIC as SMO/Non-RT RIC - participant gNBs as gNBs - - Note left of SMO/Non-RT RIC: Service Management and Orchestration - Note right of gNBs: O-RAN - - SMO/Non-RT RIC->>gNBs: 1 «O1» Data collection - gNBs-->>SMO/Non-RT RIC: 2 Performance monitoring & evaluation - - Note left of SMO/Non-RT RIC: Optimization policies - SMO/Non-RT RIC->>SMO/Non-RT RIC: 3 Interference optimization policy generation - SMO/Non-RT RIC->>gNBs: 4 «O1» radio resources configuration - - Note left of SMO/Non-RT RIC: Performance optimization - alt if need to update Optimization policy - SMO/Non-RT RIC->>SMO/Non-RT RIC: 5 Update optimization policy - SMO/Non-RT RIC->>SMO/Non-RT RIC: 6 radio resources configuration update - SMO/Non-RT RIC->>gNBs: 7 «O1» radio resources configuration update - end - - Note left of SMO/Non-RT RIC: SMO/Non-RT RIC - Note right of gNBs: gNBs - -``` - -Sequence diagram showing the interference optimization flow between Service Management and Orchestration (SMO/Non-RT RIC) and O-RAN (gNBs). - -Figure 4.26.3.2.2-1: Interference optimization flow diagram - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -``` - -``` - -Box "Service Management and Orchestration" #gold - participant "SMO/Non-RT RIC" as non -end box - -Box "O-RAN" #lightpink - participant "gNBs" as g -end box - -g -> non: <> Data collection -non -> non : Performance monitoring & evaluation -group Optimization policies -non -> non: Interference optimization policy generation -non -> g : <> radio resources configuration -end - -group Performance optimization -alt if need to update Optimization policy - non -> non: Update optimization policy - non -> non : radio resources configuration update - non -> g: <> radio resources configuration update -end alt -end - -@enduml - -``` - -#### 4.26.3.3 Interference prediction for MCS optimization - -The context of the interference prediction for MCS optimization is captured in table 4.26.3.3-1. - -**Table 4.26.3.3-1: Interference prediction for MCS optimization** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Interference prediction and MCS optimization | | -| Actors and Roles | Non-RT RIC, Near-RT RIC, E2 nodes | | -| Assumptions | All relevant functions and components are instantiated. | | -| Pre-conditions | Near-RT RIC and Non-RT RIC are instantiated with A1 interface connectivity being established between them.
E2 nodes and Non-RT RIC are instantiated with E2 interface connectivity being established between them. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Begins when | Non-RT RIC triggers interference prediction. | | -| Step 1-2 (M) | Non-RT RIC generates interference prediction policy and sends the policy to Near-RT RIC via A1 interface. The policy including neighborhood list of serving cell, prediction granularities and prediction steps, etc. | | -| Step 3 (M) | Data collection from E2 node(S) for serving cell:
1) Near-RT RIC initiates data collection request to E2 node(S) via E2 interface, to request uplink interference reported periodically;
2) E2 node(S) collects the uplink interference on each RB in the bandwidth of the serving cell and reports the uplink interference to Near-RT RIC periodically as request. | | -| Step 4 (M) | Data collection from E2 node(N) for neighbouring cell:

Neighbouring cell corresponding to E2 node(N) is a intra-frequency cell adjacent to the serving cell corresponding to the E2 node(S).

1) Data collection to construct uplink interference users set.
a. Near-RT RIC initiates data collection request to E2 node(N) via E2 interface, to request DL RSRP for the serving cell corresponding to E2 node(S) reported periodically.

b. E2 node(N) collects the DL RSRP and reports the DL RSRP to Near-RT RIC periodically as request.
c. Near-RT RIC constructs the uplink interference users set based on the DL RSRP. The users with high DL RSRP, whose uplink service may cause more uplink interference to the serving cell corresponding to E2 node(S) are included in the set.

2) Data collection of uplink interference users in the set.
a. Near-RT RIC initiates data collection request to E2 node(N) to request uplink interference related information (e.g., UL PRB usage rate, PHR, BSR, location and velocity) of users in the set reported.
b. E2 node(N) collects the information of users in the set and reports uplink interference related information to Near-RT RIC as request. | | -| Step 5 (M) | Over multiple historical time periods, the collected uplink interference from the serving cell and/or uplink interference related data from the neighbouring cell, could be processed as a training data set for the AI/ML model training and/or processed as input data for the AI/ML model inference. | | -| Step 6 (M) | 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. | | -| Step 7 (M) | Near-RT RIC performs AI/ML model inference and outputs the predicted uplink interference value based on the latest input data. | | -| Step 8 (M) | Near-RT RIC sends the RIC control or policy with the predicted uplink interference value to E2 node(S) via E2 interface. | | -| Step 9 (M) | E2 node(S) could use the predicted uplink interference value for UE(s) to be scheduled to estimate the uplink channel quality (e.g., SINR) at the future PUSCH transmission slot. E2 node(S) could realize this by replacing the uplink interference collected when the last uplink reference signal of the scheduled UE(s) is received by E2 node(S). | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|---------------------------------------------------------------------------------------------------------------------|-------------------------| -| | The E2 node(S) then uses the uplink channel quality (e.g., SINR) to decide the MCS in DCI sent to the scheduled UE. | | -| Ends when | Operator triggers to stop interference prediction. | | -| Exceptions | None identified. | | -| Post Conditions | | | - -The flow diagram of the interference prediction is given in figure 4.26.3.3-1 - -![Sequence diagram showing the interference prediction flow between Service Management and Orchestration (Non-RT RIC) and O-RAN (Near-RT RIC, E2 Node(S), E2 Node(N)).](edf47be5955638360f03d017636599c5_img.jpg) - -``` - -sequenceDiagram - participant SM as Service Management and Orchestration - participant NRT as Non-RT RIC - subgraph O-RAN - participant RT as Near-RT RIC - participant E2S as E2 Node(S) - participant E2N as E2 Node(N) - end - - Note right of NRT: A1 policies - NRT->>NRT: 1 Interference prediction policy generation - NRT->>RT: 2 «A1» Interference prediction policy - - Note right of RT: Interference prediction flow - RT->>E2S: 3 «E2» Data collection - RT->>E2N: 4 «E2» Data collection - Note right of RT: 5 Data Processing - RT->>RT: 6 AI/ML model deployment - Note right of RT: 7 AI/ML model inference - RT->>RT: 8 «E2» Uplink Interference predicted Value - - Note right of RT: E2 control/policy - RT->>E2S: 9 MCS optimization - -``` - -Sequence diagram showing the interference prediction flow between Service Management and Orchestration (Non-RT RIC) and O-RAN (Near-RT RIC, E2 Node(S), E2 Node(N)). - -Figure 4.26.3.3-1: Interference prediction flow diagram - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -Autonumber - -Box "Service Management and Orchestration" #gold - participant "Non-RT RIC" as non -end box - -Box "O-RAN" #lightpink - -``` - -``` - - participant "Near-RT RIC" as near - participant "E2 Node(S)" as s - participant "E2 Node(N)" as n -end box - -group A1 policies -non -> non: Interference prediction policy generation -non -> near : <> Interference prediction policy -end - -group Interference prediction flow - near <-> s : <> Data collection - near <-> n : <> Data collection - near -> near: Data Processing - near -> near: AI/ML model deployment - near -> near: AI/ML model inference -end - -group E2 control/policy - near -> s: <> Uplink Interference predicted Value - s -> s: MCS optimization -end - -@enduml - -``` - -### 4.26.4 Required data - -Multi-dimensional data are expected to be retrieved by Near-RT RIC for interference prediction, interference relationship generation, and interference optimization, including network level measurement data from O-CU/O-DU, which indicates network status, as well as QoS related metrics from SMO which indicates service requirements. - -- 1) Network level measurement report, including - - a) UE level information, e.g., CQI, SINR, MCS, UL/DL RSRP, DL/UL PRB usage rate, throughput, DU/UL PRB usage, mMIMO beams, BSR, PHR, location and velocity - - b) Cell level information: e.g., DL/UL PRB usage rate, throughput, uplink interference -- 2) QoS related metrics collected from SMO, e.g., 5QI, throughput, latency, packet loss rate, BLER requirement etc. - -## 4.27 Communication and computing integrated networks - -### 4.27.1 Background and goal of the use case - -#### 4.27.1.1 Common aspects & background for communication and computing integrated networks use cases - -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.6]. 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.7]. 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.8], [i.9]. 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]. - -The O-RAN ALLIANCE focuses on promoting the openness and intelligence of RAN. Its architecture provides a solid foundation for the integration of communication and computing. 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. - -#### 4.27.1.2 Sub-use case 1: Multi-aspect handover optimization - -CCIN 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 CCIN 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.13], clause 4.1.1), V2X (see 3GPP TR 38.885 [i.14]) can benefit from CCIN but they require application mobility in addition to posing stringent requirements on both communication and computing. New network architecture for CCIN 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 node used in CCIN is given below in figure 4.27.1.2-1. - -![Diagram illustrating a cloud-based joint RAN + computing node. At the top, three user equipment (UE) icons are shown in separate blue clouds, each connected by a radio signal to a central cloud. The central cloud contains a stack of components: O-CU, O-DU, and a base layer with NPU, DPU, GPU, and other resources. A yellow box labeled 'apps' and 'MEC' is positioned within the central cloud, with a dashed line connecting it to a text box on the right that reads: 'Cloud Resources in a RAN deployment that could be shared with other computing applications'.](8d7444ed03f97cc793846fdac8e2ed3a_img.jpg) - -Diagram illustrating a cloud-based joint RAN + computing node. At the top, three user equipment (UE) icons are shown in separate blue clouds, each connected by a radio signal to a central cloud. The central cloud contains a stack of components: O-CU, O-DU, and a base layer with NPU, DPU, GPU, and other resources. A yellow box labeled 'apps' and 'MEC' is positioned within the central cloud, with a dashed line connecting it to a text box on the right that reads: 'Cloud Resources in a RAN deployment that could be shared with other computing applications'. - -**Figure 4.27.1.2-1: Example illustration of cloud based joint RAN + computing node** - -In CCIN, 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 nodes 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 nodes while supporting the mobility of UE and applications in it. - -In particular, it is important to create the awareness in a cloud-based RAN nodes of the information regarding the computing capability and availability of other cloud-based RAN nodes 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 node has some overlap with the coverage area of the cells served by target cloud-based RAN node. - -In order to address aforementioned use case and related challenges it is proposed to extend the CCIN framework. Such extensions focus on obtaining information about the computing capabilities of cloud-based RAN nodes and utilizing this information in UE handover decisions. This helps the handover of the UE to a target cloud-based RAN node in the proximity with computing resource types of relevant capabilities and availability required for the applications in that UE. - -![Figure 4.27.1.2-2: Example illustration of multi-aspect handover. The diagram shows a central red square labeled 'XR' surrounded by four colored ellipses representing different network aspects: Yellow (top-left), Green (top), Blue (bottom), and Pink (right). Each ellipse contains several small white squares representing mobile devices. Below each ellipse is a cloud icon labeled 'Node' (Yellow Node 3, Green Node 4, Blue Node 1, Pink Node 2) containing a 'GPU' icon. Arrows indicate connections between the central XR device and the nodes, and between the nodes and the mobile devices.](6febae75ca030f36c2e737a316d1bc81_img.jpg) - -Figure 4.27.1.2-2: Example illustration of multi-aspect handover. The diagram shows a central red square labeled 'XR' surrounded by four colored ellipses representing different network aspects: Yellow (top-left), Green (top), Blue (bottom), and Pink (right). Each ellipse contains several small white squares representing mobile devices. Below each ellipse is a cloud icon labeled 'Node' (Yellow Node 3, Green Node 4, Blue Node 1, Pink Node 2) containing a 'GPU' icon. Arrows indicate connections between the central XR device and the nodes, and between the nodes and the mobile devices. - -**Figure 4.27.1.2-2: Example illustration of multi-aspect handover** - -#### 4.27.1.3 Sub-use case 2: RAN edge computing resource information exposure - -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 resource utilization efficiency and reduce operators' investment on the edge computing infrastructure. - -The main objective is to provide RAN edge computing information exposure service based on O-RAN architecture and its open interface. In O-RAN, SMO is a great candidate to provide RAN edge computing information exposure service to the service consumers for using RAN edge computing capability. This helps service consumer perceive RAN edge computing resources in the O-Cloud infrastructure, such as total, allocated, reserved or available computing capacity. The service consumers might be other orchestrators, e.g., central cloud orchestrator, edge cloud orchestrator, RAN edge cloud orchestrator, device edge cloud orchestrator etc. The orchestrators could request computing information for multi-cloud collaboration, such as task migration between multiple clouds or edge intelligence. The service consumers could also be application servers, e.g., RAN service computing center serving vertical customers, VR consumers, etc., which could request computing information for application deployment using shared computing resources in a secured way. - -#### 4.27.1.4 Sub-use case 3: O-RAN and mobile devices collaborative AI/ML inference - -Void - -#### 4.27.1.5 Sub-use case 4: XR rendering collaboration - -Void - -#### 4.27.1.6 Sub-use case 5: Joint communication and computing optimization for V2X communications - -It is expected that there will be approximately 8 million autonomous or semi-autonomous vehicles on the road by 2025 [i.11]. 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 4.27.1.6-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 pedestrians (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 has to obtain information by exchanging information with other vehicles or infrastructures, which may result in high latency and high risk of collision. - -![Diagram illustrating potential collisions at an intersection. Vehicle 1 (green) is moving straight through the intersection. Vehicle 2 (blue) is behind Vehicle 1, intending to turn left. Vehicle 3 (yellow) is approaching from the right. Pedestrian 1 (red) is crossing the street from the left. Pedestrian 2 (red) is near Building 2. Buildings 1 and 2 are shown. A radio tower is visible. Risk areas are indicated by yellow starburst icons.](9d81a26facbcf05a73cb7c027e66c1c8_img.jpg) - -Diagram illustrating potential collisions at an intersection. Vehicle 1 (green) is moving straight through the intersection. Vehicle 2 (blue) is behind Vehicle 1, intending to turn left. Vehicle 3 (yellow) is approaching from the right. Pedestrian 1 (red) is crossing the street from the left. Pedestrian 2 (red) is near Building 2. Buildings 1 and 2 are shown. A radio tower is visible. Risk areas are indicated by yellow starburst icons. - -**Figure 4.27.1.6-1: An illustration of the potential collisions at intersections** - -In collision warning scenarios, the latency requirement for data collection and computing are in a few milliseconds (e.g., the maximum end-to-end latency for cooperative collision avoidance in the advanced driving scenario is 10ms.) [i.12], so that the results and warns can be fed back to vehicles and pedestrians in a 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 optimizing the network or computing resource. Hence, joint optimization of network and computing resources 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. - -The main objective of the use case 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 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. - -## 4.27.1.7 Sub-use case 6: Exposure of performance information to assist computing resource scheduling - -Void - -### 4.27.2 Entities/resources involved in the use case - -#### 4.27.2.1 General aspects of entities/resources for communication and computing integrated networks use cases - -The following clauses describe the entities/resources that are important and key players for each of the CCIN sub-use cases. - -#### 4.27.2.2 Sub-use case 1: Multi-aspect handover optimization - -1) SMO/Non-RT RIC framework: - -- a) Collects necessary CM/PM data from different cloud-based RAN nodes such as O-CU 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 nodes such as O-CU over O2 interface. -- b) 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 nodes such as O-CU to rApp over R1 interface. -- c) Provides O1 configurations to Near-RT RIC via O1 interface or A1 policies to Near-RT RIC via A1 interface based on the request from rApp. - -2) rApp: - -- a) Retrieves necessary CM/PM data related to different cloud-based RAN nodes such as O-CU from SMO/Non-RT RIC framework. -- b) Retrieves supported types of computing resources, capabilities of computing resource types, and load/availability of computing resources in different cloud-based RAN nodes such as O-CU from SMO/Non-RT RIC framework. -- c) Derives the proximal computing capabilities and availability information (e.g., represented in tabular formats) for each cloud-based RAN node, use this information to create related O1 configurations or A1 policies to support multi-aspect handover optimization in Near-RT RIC. - -3) Near-RT RIC: - -- a) Performs multi-aspect handover optimization based on the O1 configurations or A1 policies received. -- b) Sends E2 control or E2 policy messages to E2 nodes (O-CU) related to multi-aspect handover optimization. - -4) E2 nodes: - -- a) Support CM data read requests from SMO over O1 interface. Collect and report PM data to SMO over O1 interface. -- b) Support UE handover related control and/or policy enforcement from Near-RT RIC over E2 interface. - -## 5) O-Cloud: - -- a) Support 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 nodes such as O-CU to SMO over O2 interface. - -## 4.27.2.3 Sub-use case 2: RAN edge computing resource information exposure - -## 1) SMO: - -- a) Support collection and analysis of computing related resources from O-Cloud. -- b) Support RAN edge computing information service, send the RAN 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) RAN edge computing information exposure service consumer: - -- a) Request/subscribe RAN edge computing information from SMO. -- b) The service consumer might be orchestrator/application server. - -## 4.27.2.4 Sub-use case 3: O-RAN and mobile devices collaborative AI/ML inference - -Void - -## 4.27.2.5 Sub-use case 4: XR rendering collaboration - -Void - -## 4.27.2.6 Sub-use case 5: Joint communication and computing optimization for V2X communications - -## 1) SMO: - -- a) Receive available communication and computing resources information from E2 nodes and O-Cloud. -- b) Expose integrated communication and computing service and/or computing service. -- c) Receive integrated communication and computing service requests from external entities. -- d) Generate and send joint communication and computing resource optimization policies. - -## 2) Near-RT RIC: - -- a) Receive communication resource optimization policies from SMO through A1 interface, and send the policies to E2 nodes over E2 interface. -- b) Send communication performance report to SMO for evaluation and optimization. -- c) Retrieve available communication resource information from E2 nodes over E2 interface. - -## 3) E2 nodes: - -- a) Report available communication resource information with required granularity to SMO over O1 interface. -- b) Update RAN parameters based on communication optimization policies from the Near-RT RIC. - -## 4) O-Cloud: - -- a) Report available computing resource information with required granularity to SMO over O2 interface. -- b) Receive workload deployment policies and/or computing resource optimization policies from SMO over O2 interface. - -4.27.2.7 Sub-use case 6: Exposure of performance information to assist computing resource scheduling - -Void - -### 4.27.3 Solutions - -#### 4.27.3.1 General aspects of solutions for communication and computing integrated networks use cases - -The following clauses describe solutions that apply to each of the CCIN sub-use cases. - -#### 4.27.3.2 Sub-use case 1: Multi-aspect handover optimization - -The context of the multi-aspect handover optimization use case is captured in table 4.27.3.2-1. - -**Table 4.27.3.2-1: Multi-aspect handover optimization use case** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Configure and update the proximal computing information for multi-aspect handover optimization. | | -| Actors and Roles |

SMO/Non-RT RIC framework: Provide relevant R1 services to enable the rApp to read relevant OAM data, O2 related data and write configuration changes.

rApp: Create related O1 configurations or A1 policies to support multi-aspect handover optimization.

Near-RT RIC: Performs multi-aspect handover optimization.

E2 node: Support UE handover related control and/or policy enforcement from Near-RT RIC over E2 interface.

O-Cloud: Support data requests related to computing information.

| | -| Assumptions | Operator has set the targets for multi-aspect handover optimization in the rApp. | | -| Pre conditions |

A1/O1 interface connectivity is established with Non-RT RIC.

O1/O2 interface connectivity is established with SMO.

| | -| Begins when |

Operator triggers the rApp for multi-aspect handover optimization.

rApp is set to periodically monitor network status and computing information.

| | -| Steps 1-4 (M) | rApp collects O1 related data using R1 services provided by SMO/Non-RT RIC framework. | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 5-8 (M) | rApp collects O2 related data using R1 services provided by SMO/Non-RT RIC framework. | | -| Step 9 (M) | Create O1 configurations which contain proximal computing capability and availability information for each O-Cloud based RAN nodes for multi-aspect handover optimization. Alternatively, create A1 policies which contain proximal computing capability and availability information for each O-Cloud based RAN nodes for multi-aspect handover optimization. | | -| Step 10 (M) | rApp sends O1 configurations or A1 policies for multi-aspect handover optimization via R1 interface. | | -| Step 11(M) | SMO/Non-RT RIC framework sends O1 configurations via O1 interface or A1 policies via A1 interface to Near-RT RIC. | | -| Step 12(M) | Near-RT RIC sends E2 control or E2 policies for multi-aspect handover optimization. | | -| Ends when | Operator stops the rApp. | | -| Exceptions | None identified. | | -| Post Conditions | E2 node(s) operate using the new configurations/policies. | | - -``` - -@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 : Creates O1 configurations or A1 polices which contains proximal -computing capability information \nand availability information for each O-Cloud based RAN -nodes for multi-aspect handover optimization -end - -group Policy Creation - rApp -> nonRTRICFramework : <> O1 configurations or A1 polices for multi-aspect -handover optimization via R1 interface - - nonRTRICFramework -> NearRTRIC : <> O1 configurations via O1 interface \nor -A1 polices via A1 interface - - NearRTRIC -> RANNodes : <> E2 control or E2 policies \nfor multi-aspect handover -optimization - -end - -@enduml - -``` - -The flow diagram of the multi-aspect handover optimization is given in figure 4.27.3.2-1. - -![Sequence diagram for Multi-aspect handover optimization flow. Lifelines: O-Cloud(s), rApp, SMO / Non-RT RIC Framework, Near-RT RIC, E2-Node(s). The diagram shows four phases: O1 Data Collection, O2 Data Collection, Data Analysis and Inference, and Policy Creation. It details the message exchanges between the rApp, SMO, Near-RT RIC, and E2-Node(s) to achieve handover optimization.](3b74c6d31e743e85101650db369fe692_img.jpg) - -Sequence diagram for Multi-aspect handover optimization flow. Lifelines: O-Cloud(s), rApp, SMO / Non-RT RIC Framework, Near-RT RIC, E2-Node(s). The diagram shows four phases: O1 Data Collection, O2 Data Collection, Data Analysis and Inference, and Policy Creation. It details the message exchanges between the rApp, SMO, Near-RT RIC, and E2-Node(s) to achieve handover optimization. - -Figure 4.27.3.2-1: Multi-aspect handover optimization flow diagram - -### 4.27.3.3 Sub-use case 2: RAN edge computing resource information exposure - -The context of the RAN edge computing information exposure is captured in table 4.27.3.3-1. - -Table 4.27.3.3-1: RAN edge computing information exposure - -| Use Case Step | Description of the step | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | RAN edge computing 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 not defined in the present document. | -| Begins when | Orchestrators or application servers want to request/subscribe RAN edge computing information. | -| Step 1 (M) | Service consumer (i.e., orchestrator or application server) sends RAN edge computing information request to SMO for updated RAN edge computing resource information, or reserving RAN edge computing resources to be used. | -| Step 2 (M) | SMO requests or subscribes the measurement data from O-Cloud and receives computing related resource data 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) | Based on the received request from service consumer, SMO sends RAN edge computing information response indicating the RAN side computing related information managed by SMO, which includes updated or reserved RAN edge computing resource information. | -| Ends when | Orchestrators or application servers get the response. | -| Post Conditions | | - -``` - -@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 RAN Edge Computing 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 RAN Edge Computing Information Response -@enduml - -``` - -The flow diagram of the RAN edge computing information exposure is given in figure 4.27.3.3-1. - -![Sequence diagram showing the interaction between Service Consumer (Orchestrator/Application Server), Service Management and Orchestration (SMO), and O-Cloud Platform (IMS/DMS). The sequence of messages is: 1. Radio Edge Computing Information Request from app to smo; 2.1. <> Data Collection Request/Subscribe from smo to ims; 2.2. <> Data Collection Response/Notify from ims to smo; 3. Data analysis (internal to smo); 4. Radio Edge Computing Information Response from smo to app.](2965c9e826cfc7efc1936b2e25f48e63_img.jpg) - -``` - -sequenceDiagram - participant app as Orchestrator/Application Server - participant smo as SMO - participant ims as IMS/DMS - Note left of app: Service Consumer - Note right of smo: Service Management and Orchestration - Note right of ims: O-Cloud Platform - app->>smo: 1 Radio Edge Computing Information Request - smo->>ims: 2.1 <> Data Collection Request/Subscribe - ims->>smo: 2.2 <> Data Collection Response/Notify - Note right of smo: 3 Data analysis - smo->>app: 4 Radio Edge Computing Information Response - -``` - -Sequence diagram showing the interaction between Service Consumer (Orchestrator/Application Server), Service Management and Orchestration (SMO), and O-Cloud Platform (IMS/DMS). The sequence of messages is: 1. Radio Edge Computing Information Request from app to smo; 2.1. <> Data Collection Request/Subscribe from smo to ims; 2.2. <> Data Collection Response/Notify from ims to smo; 3. Data analysis (internal to smo); 4. Radio Edge Computing Information Response from smo to app. - -Figure 4.27.3.3-1: RAN edge computing information exposure - -4.27.3.4 Sub-use case 3: O-RAN and mobile devices collaborative AI/ML inference - -Void - -4.27.3.5 Sub-use case 4: XR rendering collaboration - -Void - -4.27.3.6 Sub-use case 5: Joint communication and computing optimization for V2X communications - -The context of the joint communication and computing optimization for V2X communications is captured in table 4.27.3.6-1. - -**Table 4.27.3.6-1: Joint communication and computing optimization for V2X communications** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Joint communication and computing optimization for V2X communications | | -| Actors and Roles | SMO, Near-RT RIC, O-Cloud, E2 nodes, service consumer | | -| Assumptions | All relevant functions and components are instantiated. | | -| Pre conditions | All relevant functions and components are instantiated. | | -| Step 1-2 (M) | SMO retrieves data from E2 nodes and O-Cloud via O1 and O2 interfaces to obtain available communication resource (e.g., network load, bandwidth) and computing resource information (e.g., resource type, available CPU/GPU frequency, storage), respectively. | | -| Step 3-4 (M) | SMO exposes integrated communication and computing services or computing services to service consumers (e.g., vehicles or other third-party consumers). | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 5 (M) |

SMO retrieves service requests from service consumers, which indicate the V2X service requirements. The service request includes but not limited to following information:

  • - Service profile ID
  • - Service type (e.g., ID indicates service type in V2X scenarios, such as safety, advanced driving assistance)
  • - Computing data volume
  • - Location of UE
  • - Service end-to-end latency requirements
  • - UE mobility level, UE trajectory
  • - Uplink/downlink throughput requirements
  • - Computing resource requirements, including resource type, resource description, etc.
  • - Storage resource requirement

If the service consumer is a third-party service provider, following information should also be included in the service request:

  • - Maximum number of UEs
  • - Coverage for communication part of communication and computing services provided by RAN
  • - Overall uplink/downlink throughput requirements
| | -| Step 6-9 (M) |

SMO performs joint communication and computing resource optimization via AI/ML inference based on service requests and generates policies. The policies include but not limited to workload deployment (e.g., offload the workload to which endpoint) and/or computing resource scheduling policies.

SMO sends the workload deployment policies including service requirements, and/or computing resource allocation policies to O-Cloud via O2 interface.

SMO sends communication optimization policies to Near-RT RIC via A1 interface to facilitate that Near-RT RIC optimized communication resources of E2 nodes.

| | -| Step 10 (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 11 (M) |

SMO evaluates the performance (e.g., network performance, QoS of service), updates AI/ML model and /or policy accordingly.

| | -| Exceptions | None identified | | -| Post Conditions | | | - -``` -@startuml -skin rose -``` - -``` -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -box #lightcyan -Participant "Service consumer" as consumer -endbox - -box #lightseagreen - Participant "O-Cloud" as cloud -endbox - -box #gold - Participant "SMO/Non-RT RIC" as SMO -endbox - -box "O-RAN Nodes" #lightpink - Participant "Near RT-RIC" as RIC - Participant "E2 nodes" as e2 -Endbox - -SMO<-cloud: Computing resource information -SMO<-e2: Communication resource information - -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->SMO:AI/ML inference - -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 - -``` - -The flow diagram of the joint communication and computing optimization for V2X communications is given in figure 4.27.3.6-1. - -![Sequence diagram showing the joint communication and computing optimization for V2X communications. Lifelines: Service consumer, O-Cloud, SMO/Non-RT RIC, Near RT-RIC, E2 nodes. The diagram includes three main interaction blocks: 'service exposure', 'joint communication and computing resource optimization', and 'Performance monitoring'.](2db1000cc36f2eeb41c57c2ba7fd2dc6_img.jpg) - -``` - -sequenceDiagram - participant SC as Service consumer - participant OC as O-Cloud - participant SMO as SMO/Non-RT RIC - participant NRT as Near RT-RIC - participant E2 as E2 nodes - - Note right of E2: O-RAN Nodes - - OC->>SMO: 1 Computing resource information - SMO->>E2: 2 Communication resource information - - Note left of SMO: service exposure - SC->>SMO: 3 service discovery request - SMO-->>SC: 4 service discovery response - SC->>SMO: 5 service request - - Note left of SMO: joint communication and computing resource optimization - SMO->>SMO: 6 AI/ML inference - SMO->>OC: 7 Workload offload policy and/or computing resource optimization policy - SMO->>NRT: 8 Communication resource optimization policy - NRT->>E2: 9 Communication resource optimization policy - SMO->>SC: 10 Notifications (e.g., service availability) - - Note left of SMO: Performance monitoring - Note right of SMO: Performance monitoring and evaluation - SMO->>SMO: 11 AI/ML model or policy update - -``` - -Sequence diagram showing the joint communication and computing optimization for V2X communications. Lifelines: Service consumer, O-Cloud, SMO/Non-RT RIC, Near RT-RIC, E2 nodes. The diagram includes three main interaction blocks: 'service exposure', 'joint communication and computing resource optimization', and 'Performance monitoring'. - -**Figure 4.27.3.6-1: Joint communication and computing optimization for V2X communications flow diagram** - -**4.27.3.7 Sub-use case 6: Exposure of performance information to assist computing resource scheduling** - -Void - -## 4.27.4 Required data - -### 4.27.4.1 Required data for communication and computing integrated networks use cases - -The following clauses describe the required data that is relevant to each of the CCIN sub-use cases. - -### 4.27.4.2 Sub-use case 1: Multi-aspect handover optimization - -**Table 4.27.4.2-1: Required data for multi-aspect handover optimization** - -| Requirement | Category | Parameters / Measurements | Description | Source | Availability (Available/ Required) | Reference | Interface | -|--------------|---------------------------------------------|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|------------------------------------|-----------------------------------------------------------------|-----------| -| Req-4.27.001 | Network configuration management | Base station identifier | Uniquely identify the base station, including PLMN identifier and other identifiers of both the serving base station and the target base station in the proximity. | O-CU | Available | 3GPP TS 28.541 [5], clause 4.3.1, gnbld | O1 | -| Req-4.27.002 | Proximal computing capability information | Computing resource type | Identifies the type of resource, such as CPU, GPU, FPGA, NPU, DPU, AI accelerator, etc. | O-Cloud | Available | O-RAN.WG6.TS.O-CLOUD-IM [42], clause 4.2.1.4.1.2, resourceTypes | O2 | -| Req-4.27.003 | Proximal computing capability information | Computing task type | Identifies the type of computational task, such as AI/CU/DU, FFT/IFFT/DFT/L DPC/POLAR/PD CP encryption/decryption, or user access-related processing, etc. | O-Cloud | Required | | O2 | -| Req-4.27.004 | Network configuration management | Location | The geographical location of both the serving base station and the target base station in the proximity. | O-CU | Available | 3GPP TS 28.541 [5], clause 5.4.1, ntnGeoArea | O1 | -| Req-4.27.005 | Proximal computing availability information | Computing availability | The total capacity and available capacity of computing resource types for both the | O-Cloud | Available | O-RAN.WG6.TS.O-CLOUD-IM [42], clause | O2 | - -| Requirement | Category | Parameters / Measurements | Description | Source | Availability (Available/ Required) | Reference | Interface | -|-------------|----------|---------------------------|--------------------------------------------------------------------|--------|------------------------------------|-----------------------|-----------| -| | | | serving base station and the target base station in the proximity. | | | 4.2.1.4.5.2, capacity | | - -#### 4.27.4.3 Sub-use case 2: RAN edge computing resource information exposure - -**Table 4.27.4.3-1: Required data for RAN edge computing information exposure** - -| Requirement | Category | Parameters / Measurements | Source | Availability (Available/ Required) | Reference | Interface | -|--------------|---------------------------------|------------------------------------------------------------------|---------|------------------------------------|------------------------------------------------------------|-----------| -| Req-4.27.006 | Computing related resource data | CPU number for O-Cloud, cluster, or node | O-Cloud | Required | | O2 | -| Req-4.27.007 | Computing related resource data | vCPU number for O-Cloud, cluster, or node | O-Cloud | Required | | O2 | -| Req-4.27.008 | RAN edge computing information | Total capacity of computing or number of computing resources | O-Cloud | Available | O-RAN.WG6.TS.O-CLOUD-IM [42], clause 4.2.1.4.5.2, capacity | O2 | -| Req-4.27.009 | RAN edge computing information | Allocated capacity of computing or number of computing resources | O-Cloud | Available | O-RAN.WG6.TS.O-CLOUD-IM [42], clause 4.2.1.4.5.2, capacity | O2 | -| Req-4.27.010 | RAN edge computing information | Reserved capacity of computing or number of computing resources | O-Cloud | Available | O-RAN.WG6.TS.O-CLOUD-IM [42], clause 4.2.1.4.5.2, capacity | O2 | -| Req-4.27.011 | RAN edge computing information | Available capacity of computing or number of computing resources | O-Cloud | Available | O-RAN.WG6.TS.O-CLOUD-IM [42], clause 4.2.1.4.5.2, capacity | O2 | -| Req-4.27.012 | RAN edge computing information | Cloud identifier | O-Cloud | Available | O-RAN.WG6.TS.O-CLOUD-IM [42], clause 4.2.1.4.1.2, oCloudId | O2 | - -| Requirement | Category | Parameters / Measurements | Source | Availability (Available/ Required) | Reference | Interface | -|--------------|--------------------------------|---------------------------|---------|------------------------------------|------------------------------------------------------------------|-----------| -| Req-4.27.013 | RAN edge computing information | Resource identifier | O-Cloud | Available | O-RAN.WG6.TS.O-CLOUD-IM [42], clause 4.2.1.4.3.2, resourceId | O2 | -| Req-4.27.014 | RAN edge computing information | Resource pool identifier | O-Cloud | Available | O-RAN.WG6.TS.O-CLOUD-IM [42], clause 4.2.1.4.4.2, resourcePoolId | O2 | -| Req-4.27.015 | RAN edge computing information | Computing location | O-Cloud | Available | O-RAN.WG6.TS.O-CLOUD-IM [42], clause 4.2.1.4.31.2, locationId | O2 | - -#### 4.27.4.4 Sub-use case 3: O-RAN and mobile devices collaborative AI/ML inference - -Void - -#### 4.27.4.5 Sub-use case 4: XR rendering collaboration - -Void - -#### 4.27.4.6 Sub-use case 5: Joint communication and computing optimization for V2X communications - -**Table 4.27.4.6-1: Required data for joint communication and computing optimization for V2X communications** - -| Requirement | Category | Parameters / Measurements | Source | Availability (Available/ Required) | Reference | Interface | -|--------------|---------------------------------|--------------------------------------------------------------------|---------|------------------------------------|-----------------------------------------------------------------|-----------| -| Req-4.27.016 | Computing resource related data | Resource type of computing resources in O-Cloud, e.g., CPU/GPU/NPU | O-Cloud | Available | O-RAN.WG6.TS.O-CLOUD-IM [42], clause 4.2.1.4.1.2, resourceTypes | O2 | -| Req-4.27.017 | Computing resource related data | Available capacity of computing or number of computing resources | O-Cloud | Available | O-RAN.WG6.TS.O-CLOUD-IM [42], clause 4.2.1.4.5.2, capacity | O2 | -| Req-4.27.018 | Computing resource related data | Available storage | O-Cloud | Required | | O2 | - -| Requirement | Category | Parameters / Measurements | Source | Availability (Available/ Required) | Reference | Interface | -|--------------|-------------------------------------|-------------------------------|---------|------------------------------------|--------------------------------------------------------------------------|-----------| -| Req-4.27.019 | Computing resource related data | Cloud identifier | O-Cloud | Available | O-RAN.WG6.TS.O-CLOUD-IM [42], clause 4.2.1.4.1.2, oCloudId | O2 | -| Req-4.27.020 | Communication resource related data | PRB Usage | O-CU | Available | 3GPP TS 28.552 [6], clause 5.1.1.2.3, Distribution of DL Total PRB Usage | O1 | -| Req-4.27.021 | Communication resource related data | Maximum uplink bandwidth | O-CU | Available | 3GPP TS 28.541 [5], clause 5.4.1, maxbrUl | O1 | -| Req-4.27.022 | Communication resource related data | Maximum downlink bandwidth | O-CU | Available | 3GPP TS 28.541 [5], clause 5.4.1, maxbrDl | O1 | -| Req-4.27.023 | Communication resource related data | Guaranteed uplink bandwidth | O-CU | Available | 3GPP TS 28.541 [5], clause 5.4.1, gbrUl | O1 | -| Req-4.27.024 | Communication resource related data | Guaranteed downlink bandwidth | O-CU | Available | 3GPP TS 28.541 [5], clause 5.4.1, gbrDl | O1 | -| Req-4.27.025 | Communication resource related data | Link quality | O-CU | Available | 3GPP TS 28.541 [5], clause 4.4.1, qQualMin | O1 | - -#### 4.27.4.7 Sub-use case 6: Exposure of performance information to assist computing resource scheduling - -Void - -## 4.28 RAN intent-driven management services - -This use case provides the background and motivation for implementing intent-driven management capabilities in the O-RAN architecture to enable high-level, goal-oriented service automation and orchestration. It focuses on how an RMIO and an RMIH interact to provision, manage, and terminate RAN services based on expressed intents, without requiring the RMIO to configure low-level details. - -### 4.28.1 Background and goal of the use case - -Intent-driven management enables operators or external consumers to manage network behavior in a goal-oriented manner by specifying what outcome is desired rather than how to achieve it. This abstraction simplifies service management, accelerates deployments, and allows dynamic adaptation to changing RAN conditions. - -In the RAN context, intents can express performance optimization targets, specific service-level objectives for slices (without explicitly requiring parameter configuration). An external consumer (e.g., E2E management system) or an internal SMO consumer (e.g., SO/SA or rApps) that needs to provide a RAN management intent must first discover the - -RAN intent handling capabilities supported by a particular RMIH within SMO. This ensures the consumer can select and formulate a suitable intent for SMO. Then, the RAN Management Intent Handler (RMIH) receives the intent, translates it into actionable configurations, and executes the necessary operations, while keeping the RAN Management Intent Owner (RMIO) informed on progress and service status. - -To enable this, the SMO must support capabilities for registering and discovering RMIHs. This can be a natural add-on to the Service Management and Exposure (SME) in the SMO, where enhancements to the SME services would accommodate the registration and discovery of information specific to the RMIHs capabilities. RMIHs can register information about the intents they support, the management operations available, their reachability details, and other relevant metadata. - -## 4.28.2 Entities/resources involved in the use case - -- 1) RAN Management Intent Owner (RMIO): - - a) Defines high-level RAN service or management objectives without specifying detailed configurations. - - b) Discovers available RMIHs and reviews their capabilities via the SME. - - c) Formulates, sends, updates, and deletes intents as needed. - - d) Evaluates intent reports received from RMIHs. -- 2) Service Management and Exposure (SME): - - a) Produces registration and discovery services for intent handling capabilities. - - b) Provides RMIHs endpoints to RMIOs. -- 3) RAN Management Intent Handler (RMIH): - - a) Exposes their endpoints through SME. - - b) Exposes their intent handling capabilities through SME. - - c) Interprets the received RAN intents and maps them into actionable configurations. - - d) Executes required operations to fulfill the intents and continuously monitors performance. - - e) Reports fulfillment progress/status back to the RMIO via the SMO. - -## 4.28.3 Solutions - -### 4.28.3.1 RAN intent lifecycle management - -The context for the intent lifecycle management is described in table 4.28.3.1-1. - -Table 4.28.3.1-1: RAN intent lifecycle management - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | Enable RMIOs to request handling of RAN intent. | | -| Actors and Roles | RMIO
RMIH
SMO
SME | | -| Assumptions | SMO has services that support capabilities for RAN management intent.
SME supports RMIH capability registration and discovery. | | -| Pre-conditions | The SMO consumer is an authorized consumer of the SMO services.
RMIHs have registered their service capabilities in SME. | | -| Begins when | The RMIO identifies a need for a RAN management intent. | | -| Step 1 (M) | The RMIO queries SME for available RMIHs and their capabilities. | | -| Step 2 (M) | The SME returns the RMIH endpoints and RMIH capabilities to the RMIO. | | -| Step 3 (M) | The RMIO selects the appropriate RMIH. | | -| Step 4 (M) | The RMIO formulates a RAN intent and sends it to the RMIH including subscription to intent reports. | | -| Step 5 (M) | The RMIH validates the request. | | -| Step 6 (M) | The RMIH sends initial acceptance/acknowledgment report to RMIO. | | -| Step 7 (M) | The RMIH initiates execution procedures to fulfill the intent. | | -| Step 8 (M) | The RMIH reports fulfillment status. | | -| Step 9 (O) | The RMIO evaluates the report; if needed, it can modify the intent. | | -| Step 10 (M) | The RMIO request intent deletion when the intent is no longer required. | | -| Step 11 (M) | The RMIH deletes the intent and sends final confirmation to RMIO. | | -| Ends when | The intent is deleted by the RMIO. | | -| Exceptions | None. | | -| Post Conditions | Service associated with the intent has been cleanly terminated. | | - -The flow diagram of the RAN intent-driven management services use case is given in figure 4.28.3.1-1 and figure 4.28.3.1-2. - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam Boxpadding 10 -skinparam defaultFontSize 12 -Autonumber -Box External #lightcyan - participant RMIO as "RMIO" -end box -Box "Service Management and Orchestration" #gold - participant RMIH as "RMIH" - participant SME as "SME" -end box - -``` - -``` -== Capability Discovery == -RMIO -> SME: Query available RMIHs and their capabilities -SME -> RMIO: Returning RMIH endpoints -RMIO -> RMIO: Selecting appropriate RMIH - -== Intent Request == -RMIO -> RMIH: Formulating and sending RAN management intent -RMIH -> RMIH: Validating the request -RMIH -> RMIO: Initial acceptance/acknowledgment - -== Intent Execution == -RMIH -> RMIH: Initiating execution to fulfill intent -RMIH -> RMIO: Reporting fulfillment status -group Optional Modification - RMIO -> RMIH: Requesting modification of intent if needed -end - -== Intent Deletion == -RMIO -> RMIH: Requesting intent deletion -RMIH -> RMIO: Deleting the intent and sending final report status -@enduml -``` - -![Sequence diagram showing RAN management intent capabilities discovery use case flow. Lifelines: External (RMIO), Service Management and Orchestration (RMIH, SME). Phases: Capability Discovery, Intent Request, Intent Execution, Optional Modification, Intent Deletion.](ec5285869660f31441ecb3c7527fe1cc_img.jpg) - -``` - -sequenceDiagram - participant RMIO as RMIO - participant RMIH as RMIH - participant SME as SME - - Note over RMIO, RMIH: Capability Discovery - RMIO->>SME: 1 Query available RMIHs and their capabilities - SME-->>RMIO: 2 Returning RMIH endpoints - Note right of RMIO: 3 Selecting appropriate RMIH - - Note over RMIO, RMIH: Intent Request - RMIO->>RMIH: 4 Formulating and sending RAN management intent - Note right of RMIH: 5 Validating the request - RMIH-->>RMIO: 6 Initial acceptance/acknowledgment - - Note over RMIO, RMIH: Intent Execution - Note right of RMIH: 7 Initiating execution to fulfill intent - RMIH-->>RMIO: 8 Reporting fulfillment status - - Note over RMIO, RMIH: Optional Modification - RMIO->>RMIH: 9 Requesting modification of intent if needed - - Note over RMIO, RMIH: Intent Deletion - RMIO->>RMIH: 10 Requesting intent deletion - RMIH-->>RMIO: 11 Deleting the intent and sending final report status - -``` - -Sequence diagram showing RAN management intent capabilities discovery use case flow. Lifelines: External (RMIO), Service Management and Orchestration (RMIH, SME). Phases: Capability Discovery, Intent Request, Intent Execution, Optional Modification, Intent Deletion. - -Figure 4.28.3.1-1 RAN management intent capabilities discovery use case flow diagram (external RMIO) - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam Boxpadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "Service Management and Orchestration" #gold -participant RMIO as "RMIO" - -``` - -``` -participant RMIH as "RMIH" -participant SME as "SME" -end box - -== Capability Discovery == -RMIO -> SME: Query available RMIHs and their capabilities -SME -> RMIO: Returning RMIH endpoints -RMIO -> RMIO: Selecting appropriate RMIH - -== Intent Request == -RMIO -> RMIH: Formulating and sending RAN management intent -RMIH -> RMIH: Validating the request -RMIH -> RMIO: Initial acceptance/acknowledgment - -== Intent Execution == -RMIH -> RMIH: Initiating execution to fulfill intent -RMIH -> RMIO: Reporting fulfillment status - -group Optional Modification - RMIO -> RMIH: Requesting modification of intent if needed -end - -== Intent Deletion == -RMIO -> RMIH: Requesting intent deletion -RMIH -> RMIO: Deleting the intent and sending final report status@enduml -``` - -![Sequence diagram titled 'Service Management and Orchestration' showing interactions between RMIO, RMIH, and SME. The diagram is divided into five phases: Capability Discovery, Intent Request, Intent Execution, Optional Modification, and Intent Deletion. The flow starts with RMIO sending a query to SME, followed by SME returning RMIH endpoints. RMIO then selects an RMIH and sends an intent request. RMIH validates and acknowledges. Intent execution is initiated by RMIH, and status is reported to RMIO. An optional modification step follows. Finally, RMIO requests intent deletion, and RMIH confirms.](a179c59b95e3e871a830494d80dc7ec5_img.jpg) - -``` - -sequenceDiagram - participant RMIO - participant RMIH - participant SME - - Note over RMIO, SME: Service Management and Orchestration - - Note over RMIO, SME: Capability Discovery - RMIO->>SME: 1 Query available RMIHs and their capabilities - SME-->>RMIO: 2 Returning RMIH endpoints - RMIO->>RMIO: 3 Selecting appropriate RMIH - - Note over RMIO, SME: Intent Request - RMIO->>RMIH: 4 Formulating and sending RAN management intent - RMIH->>RMIH: 5 Validating the request - RMIH-->>RMIO: 6 Initial acceptance/acknowledgment - - Note over RMIO, SME: Intent Execution - RMIH->>RMIH: 7 Initiating execution to fulfill intent - RMIH-->>RMIO: 8 Reporting fulfillment status - - Note over RMIO, SME: Optional Modification - RMIO->>RMIH: 9 Requesting modification of intent if needed - - Note over RMIO, SME: Intent Deletion - RMIO->>RMIH: 10 Requesting intent deletion - RMIH-->>RMIO: 11 Deleting the intent and sending final report status - -``` - -Sequence diagram titled 'Service Management and Orchestration' showing interactions between RMIO, RMIH, and SME. The diagram is divided into five phases: Capability Discovery, Intent Request, Intent Execution, Optional Modification, and Intent Deletion. The flow starts with RMIO sending a query to SME, followed by SME returning RMIH endpoints. RMIO then selects an RMIH and sends an intent request. RMIH validates and acknowledges. Intent execution is initiated by RMIH, and status is reported to RMIO. An optional modification step follows. Finally, RMIO requests intent deletion, and RMIH confirms. - -Figure 4.28.3.1-2 RAN management intent capabilities discovery use case flow diagram (RMIO in SMO) - -## 4.28.4 Required data - -The required data is measurements of metrics that are used in the intent expression to formulate intent requirements (e.g, performance metrics). Typically, also data from the inventory such as topology data is needed in the intent handling processes. - -## Annex A (informative): Additional information - -### A.1 Traffic steering use case A1 interface usage example - -NOTE: Please refer to WG2 Use Cases and Requirements Specification for more details and up to date definitions of this use case A1 interface usage examples. - -An example scenario is here used to describe the use of A1 for traffic steering, implying the Non-RT RIC sending policies for allocation of the control plane (RRC) and the user plane for different services, identified by their 5QI. - -In the scenario a UE with UEid=1, belonging to a subnet slice identified by S-NSSAI=1, having a voice (5QI=1) and an MBB (5QI=9) connection established, enters an area covered by four frequency bands. The Non-RT RIC understands the requirements and characteristics of the services and decides to let the voice and RRC connection reside on the low band (here covered by a macro cell B becoming the PCell), while the MBB connection should preferably use the higher band (here provided by a smaller cell C and D becoming the SCells) and avoid the low band if possible. Cell A is used for MBB if required for coverage reasons. - -Policies are sent to any cell of concern, e.g. where the UE resides and can move. - -The desired use of the cells is shown in figure A.1-1. - -![Diagram showing four cells (CellA, CellB, CellC, CellD) and their associated network characteristics. CellA is labeled 'Low band, Narrow bandwidth, Low latency'. CellB is labeled 'High band, Wide bandwidth, High latency'. CellC and CellD are grouped together and labeled 'MBB'. CellB is also labeled 'RRC and Voice'. A UE icon is shown within CellC/CellD.](d44f82cf884db0e1f1ffb2c18e4dd8d6_img.jpg) - -The diagram illustrates a network scenario with four cells: CellA, CellB, CellC, and CellD. CellA is a macro cell on the left, associated with 'Low band', 'Narrow bandwidth', and 'Low latency'. CellB is a macro cell on the right, associated with 'High band', 'Wide bandwidth', and 'High latency'. CellC and CellD are smaller cells located within the coverage area of CellB. CellC and CellD are associated with 'MBB' (Mobile Broadband). CellB is associated with 'RRC and Voice'. A User Equipment (UE) icon is shown within CellC/CellD, indicating its current location. - -Diagram showing four cells (CellA, CellB, CellC, CellD) and their associated network characteristics. CellA is labeled 'Low band, Narrow bandwidth, Low latency'. CellB is labeled 'High band, Wide bandwidth, High latency'. CellC and CellD are grouped together and labeled 'MBB'. CellB is also labeled 'RRC and Voice'. A UE icon is shown within CellC/CellD. - -Figure A.1-1: Desired use of the cells - -Two policies over A1 are needed to accomplish the desired behavior, described in JSON format below. Note that as part of the scope, the cell\_id is optional, and if omitted it is up to the Near-RT RIC to locate the UE and there enforce the policy. - -``` -{ - "policy_id": "1", - "scope": { - "ue_id": "1", - "slice_id": "1", - "qos_id": "1", -``` - -``` - "cell_id": "X" // Policy for Cell X, where X is one of A, B, C or D - }, - "statement": { - "cell_id_list": "B", - "preference": "Shall", - "primary": true // Control plane on Cell B (becoming PCell) - }, - "statement": { - "cell_id_list": "B", - "preference": "Shall", - "primary": false // Voice on Cell B - } -} -``` - -``` -{ - "policy_id": "2", - "scope": { - "ue_id": "1", - "slice_id": "1", - "qos_id": "9", - "cell_id": "X" // Policy for Cell X, where X is one of A, B, C or D - }, - "statement": { - "cell_id_list": {"B", "A"}, - "preference": "Avoid", - "primary": false // Avoid MBB on Cell A and Cell B - }, - "statement": { - "cell_id_list": {"C", "D"}, - "preference": "Prefer", - "primary": false // Prefer MBB on Cell C and Cell D - } -} -``` - -## Annex (informative): Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2019.07.07 | 01.00.00 | Draft template | -| 2019.09.18 | 01.00.01 | Addition of CR:
- ORAN-WG1.UseCasesDetailedSpecification_CR_NOK_DHO_20190909 | -| 2019.09.19 | 01.00.02 | Addition of QoE optimization use case from WG2 UCR specification | -| 2019.09.20 | 01.00.03 | Addition of Traffic Steering use case from WG2 UCR specification | -| 2019.09.23 | 01.00.04 | Addition of CR:
- ORAN-WG1.UAV Control Vehicle Use Case -INSPUR-20190911
Editorial changes | -| 2019.09.27 | 01.00.05 | Addition of CR:
- ORAN-WG1.UAV_Use Case for dynamic UAV Radio Resource Allocation
_CMCC_CR
Editorial changes for improved sections, consistency, typo fixes | -| 2019.09.28 | 01.00.06 | Updates to Radio Resource Allocation for UAV Application Scenario from UC Analysis doc

Addition of CR:
- ORAN-WG1.UAV_Use Case for dynamic UAV Radio Resource Allocation
_CMCC_CR_v2 | -| 2019.10.11 | 01.00.07 | Updates to the following use cases based on use case review meeting:
- Fight Path Based Dynamic UAV Radio Resource Allocation (CMCC)
- Radio Resource Allocation for UAV Application (Inspur) | -| 2019.10.17 | 01.00.08 | Add plantuml code and diagram for OoE use case to add E2 interaction between Near-RT RIC and RAN

Modified UAV Control Vehicle use case required data to remove IMSI and replace with user identification clarification

Corrected UAV Resource Allocation plantuml code and diagram with ML model deployment over O1 (rather than A1)

Corrected QoE use case plantuml code and diagram for ML model deployment over O1 (rather than A1)

Merged updates from ORAN-WG1.Correction on UAV_UseCasesDetailedSpecification_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.11.25 | 02.00.02 | Addition of CR (new use case):
- ORAN-WG1.UseCasesDetailedSpecification_CR_ORANGE_20191120.docx | -| 2019.12.06 | 02.00.03 | Addition of CRs:
- UAV Control Vehicle-CR-INSPUR-20191204.docx
- ORAN-WG1.UseCasesDetailedSpecification_CR_ORANGE_20191125-update-uml.docx | -| 2019.12.08 | 02.00.04 | Addition of CRs:
- ORAN-WG1.UseCasesDetailedSpecification_CR_CMCC_20191204.docx | - -| | | | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | - ORAN-WG1.UseCasesDetailedSpecification_CR_NOK_DHO_20191203.docx | -| 2020.01.10 | 02.00.05 | Addition of CRs:
- ORAN-WG1.UseCasesAnalysisReport_CR_Traffic_Steering_Ericsson_2020.01.08.docx
- ORAN-WG1.Usecase_QoS_based_resource_optimization_1_6-2020.docx | -| 2020.01.22 | 02.00.06 | Editorial updates and terminology corrections | -| 2020.02.12 | 02.00.07 | Addition of CR:
- ORAN-WG1.UCTG_CMCC_QoE Optimization Use Case
Editorial updates to plantUML diagrams to add interface names, and rearranging components per O-RAN plantUML guidelines | -| 2020.02.13 | 02.00.08 | Addition of CR:
- ORAN-WG1.UseCasesDetailedSpecification_CR_(UC_M-MIMO)_TIM-ORANGE-CMCC_20200114-v2 | -| 2020.02.23 | 02.00.09 | Editorial updates, O-RAN license agreement additions, update RAN Sharing diagram with latest version, | -| 2020.03.01 | 02.00.10 | Editorial updates, fixing table of contents issues, spec naming corrections | -| 2020.03.11 | 02.00.11 | Updates to definitions and RAN Sharing use case (update O1* to O2) 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.20 | 03.00.02 | Addition of CR:
- O-RAN_WG1_2020.03.11-Netsia_KDDI_ATT_TEF_UCTG_CR_UCDS_SliceAssurance .docx | -| 2020.06.20 | 03.00.03 | Addition of CR:
- INT-2020.05.21-WG1-D-CR-UCDR_MultiAccess_UC_v1.docx | -| 2020.07.15 | 03.00.04 | Updates based on WG1 review comments (very minor editorial corrections to section 3.9) | -| 2020.07.16 | 03.00.05 | 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.11.01 | 04.00.02 | Addition of CR:
- STL.AO-10.14.2020-WG1(UCTG)-CR-0001-DSS-v1.2 | -| 2020.11.02 | 04.00.03 | Addition of CR:
- INT-2020.11.02-WG1(UCTG)-CR-0001-NSSI-Rsrc-Opt-D-UC-v1.3
Editorial updates/corrections | -| 2020.11.05 | 04.00.04 | Addition of CR:
- KDDI.AO-2020.11.05-WG1-CR-0001-Multi-vendor Slices Use Case-v01 | -| 2020.11.13 | 04.00.05 | Correction of plantuml source and diagram for Multi-vendor Slices use case and other editorial updates | -| 2020.11.13 | 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.03.04 | 05.00.02 | To keep the same use case numbering as Use Case Analysis Report, addition of
  • - Use case 13 "Local Indoor Positioning in RAN"
  • - Use case 16 "Congestion Prediction and Management"
  • - Use case 17 "Industrial IoT Optimization"
  • - Use case 18 "BBU Pooling to achieve RAN Elasticity"
as FFS items. Use case 14 and 15 will be defined in further sub versions of this v5 specification.

Addition of CR:
  • - ATT.AO-2020.12.01-WG1-CR-0001-UseCaseDetailedSpecification_SSP-v04
| -| 2021.03.08 | 05.00.03 | Updating use case 14 name to "Massive SU/MU-MIMO Grouping Optimization" | -| 2021.03.08 | 05.00.04 | Addition of CR:
  • - NOK-2021.02.10-ORAN-CR-0001-UseCaseDetailedSpecification_mMIMO_BF_Optimization-v01
Editorial updates | -| 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:
  • - NOK-2021.05.03-ORAN-CR-0001-UseCaseDetailedSpecification_mMIMO_BF_Optimization
| -| 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.13 | 07.00.02 | Addition of CR:
  • - NC.AO-2021.07.20-WG1-CR-0001-NSSIResourceAllocationWithQuota-v04
| -| 2021.11.13 | 07.00.03 | Correction of terminology used in NSSI optimization use case | -| 2021.11.14 | 07.00.04 | Clean version for WG1 approval | -| 2021.11.23 | 07.00.05 | Updates to address WG1 review comments | -| 2021.11.23 | 07.00 | Final version 07.00 | -| 2022.03.27 | 07.00.06 | Adopted new spec revision numbering per O-RAN Work Procedures
Initial version towards v08.00, starting with v07.00.06 per new revision numbering | -| 2022.03.27 | 07.00.07 | Addition of CR:
  • - CMCC-2022.1.13-WG1-CR-0001-UseCasesDetailedSpecification-QOE-Optimization-v3.0
| -| 2022.03.27 | 07.00.08 | Addition of CR:
  • - CMCC-2022.03.10-WG1-CR-0001-UseCasesDetailedSpecification-Local-Indoor-Positioning-in-RAN-v1
| -| 2022.03.27 | 07.00.09 | Addition of placeholders for new use cases added to Use Case Analysis Rreport
  • - Use Case 20: Lower Layer Split Multi Node Support (Shared O-RU)
  • - Use Case 21: Energy Saving
| -| 2022.03.27 | 07.00.10 | Changes accepted from v07.00.09
Baseline for WG1 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:
- NOK.AO-2022.04.25-ORAN-CR-0001-RevisedUseCaseDetailedSpecification_EE-ES_v10

Editorial updates and corrections | -| 2022.07.25 | 08.00.03 | Addition of CR:
- COT.AO-2022.06.29-WG1-CR-0002-UseCaseDetailedSpecification-MU-MIMO-Optimization-v05

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.07.27 | 08.00.06 | Addition of CR:
- CIS.AO-2022.07.21-WG1-CR-0001-UseCaseDetailedSpecification-shared-ORU-v04

Editorial corrections and updates | -| 2022.07.27 | 08.00.07 | Updated version for WG1/TSC approval | -| 2022.08.01 | 09.00 | Final version 09.00 | -| 2022.11.09 | 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.04.12-ORAN-CR-0001-UseCaseDetailedSpecification_TrafficSteeringEI - Rev 2 | -| 2022.11.10 | 09.00.02 | Addition of CR:
- FJT-2022.08.25-ORAN-CR-0001-UseCaseDetailedSpecification_RANSliceSlaAssurance_ReliabilityAssurance-Rev1 | -| 2022.11.10 | 09.00.03 | Addition of CR:
- QCM.AO-2022.06.14-ORAN-CR-0001-UseCaseDetailedSpecification_ISRM-v14-clean | -| 2022.11.10 | 09.00.04 | Addition of CR:
- NOK.AO-2022.10.27-WG1-CR-0001-UseCaseDetailedSpecification-shared-ORU-v01
Editorial updates

Addition of Section 3.23 as placeholder to align with new use case addition to O-RAN Use Cases Analysis Technical Report | -| 2022.11.13 | 09.00.05 | 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: | - -| | | | -|------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | - NOK.AO-2023.02.09-WG1-CR-0001-SharedORU_CoordinatedReset-v02.00 | -| 2023.03.16 | 10.00.03 | Addition of CR:
- KDDI.AO-2023.03.07-WG1-CR-0000-UseCaseDetailedSpecification-MultiVendorSlicesAddRequirement-v02

Addition of placeholder for “use case #24: Industrial vision SLA Assurance” as this use case is approved and merged to Use Case Analysis Report | -| 2023.03.16 | 10.00.04 | All changes accepted, clean version for WG1 approval | -| 2023.03.24 | 10.00.05 | 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-0012-O-RAN-Use-Cases-Detailed-Specification-ODR-References-Section-v01 | -| 2023.05.04 | 11.00.02 | Addition of CR:

- JNPR-2023.05.02-WG1-CR-0013-O-RAN-Use-Cases-Detailed-Specification-ODR-References-Section-v01 | -| 2023.05.16 | 11.00.03 | Addition of CRs:

- JNPR-2023.05.16-WG1-CR-0021-O-RAN-Use-Cases-Detailed-Specification-References-Update-v01
- JNPR-2023.05.16-WG1-CR-0022-O-RAN-Use-Cases-Detailed-Specification-References-Correction-v01 | -| 2023.05.29 | 11.00.04 | Addition of CR:

- JNPR-2023.05.17-WG1-CR-0023-O-RAN-Use-Cases-Detailed-Specification-References-Wording-v01 | -| 2023.06.06 | 11.00.05 | Addition of CR:

- JNPR-2023.05.29-WG1-CR-0025-O-RAN-Use-Cases-Detailed-Specification-ODR-Figures-References_Wording_Corrections-v01 | -| 2023.06.13 | 11.00.06 | Addition of CR:

- JNPR-2023.06.13-WG1-CR-0032-O-RAN-Use-Cases-Detailed-Specification-ODR-Tables-References-Headings-Corrections-v01 | -| 2023.06.13 | 11.00.07 | Addition of CR:

- JNPR-2023.06.13-WG1-CR-0033-O-RAN-Use-Cases-Detailed-Specification-ODR-Notes-v02 | -| 2023.06.27 | 11.00.08 | Addition of CR:

- JNPR-2023.06.27-WG1-CR-0036-O-RAN-Use-Cases-Detailed-Specification-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-0038-O-RAN-Use-Cases-Detailed-Specification-ODR-Modal-Verbs_Can_Cannot_May_Need_not-v01 | -| 2023.07.19 | 11.00.10 | Addition of CR: | - -| | | | -|------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | |
  • - KDDI.AO-2023.03.08-WG1-CR-0002-UseCaseDetailedSpecification-update-SLA-Assurance-v01
| -| 2023.07.19 | 11.00.11 | Addition of CR:
  • - CMCC-2023.2.6-WG1-CR-0001-UseCasesDetailedSpecification-Industrialvision-guarantee-v3
  • - Addition of section 4.25 as placeholder for Use Case 25: Non-Public Network (NPN) RAN-Sharing via Midhaul for Multi-Operator Coverage
| -| 2023.07.19 | 11.00.12 | Addition of CR:
  • - NOK.AO-2023.06.30-WG1-CR-0002-ResiliencyUseCase-SharedORU-v02.01
| -| 2023.07.19 | 11.00.13 | Addition of CR:
  • - NEC-2022.12.12-WG1-CR-0008-ODU_SW_Update-shared-ORU-v08.00
| -| 2023.07.20 | 11.00.14 |
  • - 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.15 | Clean version for WG1 approval | -| 2023.07.27 | 11.00.16 | WG1 review comments are addressed, and approval is completed. | -| 2023.07.27 | 11.00.17 | 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:
  • - NOK.AO-2023.10.17-WG1-CR0004-MultiMNO-SharedORU_SubUseCase-v01.01
Addition of section 4.26 as placeholder for Use Case 26: Interference Detection and Optimization

Editorial Modifications | -| 2023.11.06 | 12.00.02 | Clean version for WG1 approval | -| 2023.11.16 | 12.00.03 | WG1 review comments are addressed, and approval is completed. | -| 2023.11.16 | 12.00.04 | 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-0047-O-RAN-Use-Cases-Detailed-Specification-ODR-FFS-Concepts-v01
| -| 2024.02.26 | 13.00.02 | Addition of CRs:
  • - JNPR-2024.01.16-WG1-CR-0051-O-RAN-Use-Cases-Detailed-Specification-ODR-Clauses-v01
  • - JNPR-2024.01.16-WG1-CR-0053-O-RAN-Use-Cases-Detailed-Specification-ODR-Figures-Numbering_Capital_Letters_Editorial_Changes-v01
  • - JNPR-2024.01.16-WG1-CR-0054-O-RAN-Use-Cases-Detailed-Specification-ODR-Tables-Numbering_Capital_Letters_Editorial_Changes-v01 copy
| - -| | | | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2024.03.07 | 13.00.03 | Addition of CRs:

  • - CMCC-2023.09.12-WG1-CR-0004-UseCasesDetailedSpecification-Interference-Detection-and-Optimization-v05
  • - KDDI.AO-2023.11.14-WG1-CR-0004-UseCaseDetailedSpecification-update-SLA-Assurance-v01
| -| 2024.03.08 | 13.00.04 | Addition of CR:

  • - KDDI.AO-2023.12.11-WG1-CR-0005-UseCasesDetailedSpecification-Interference-Detection-and-Optimization-v03
| -| 2024.03.20 | 13.00.05 | Addition of CRs:

  • - NOK-2024.01.25-WG1UCTG-CR0009-SharedORU_SubUseCaseTitleUpdates-v01.00
  • - RMI.AO-2023.08.30-WG1-UCTG-CR-0002-Shared-ORU-Advanced-Resiliency-sub-use-case#1(1+1)-v01.00
  • - NOK.AO-2024.01.25-WG1UCTG-CR0008-SharedORU_PerformanceMgmt_SubUseCase-v01.04
  • - NOK.AO-2024.02.15-WG1UCTG-CR0010-SharedORU_AntennaCalibration_SubUseCase-v01.00
| -| 2024.03.22 | 13.00.06 | Clean version for WG1 approval | -| 2024.03.31 | 13.00.07 | WG1 review comments are addressed, and approval is completed. | -| 2024.03.31 | 13.00.08 | All changes accepted, clean version. | -| 2024.03.31 | 14.00 | Final version 14.00 | -| 2024.06.25 | 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-0056-O-RAN-Use-Cases-Detailed-Specification-ODR-Capital_Letters-Editorial_Changes-Fixes-v01
| -| 2024.06.28 | 14.00.02 | Addition of CRs:

  • - JNPR-2024.06.03-WG1-CR-0059-O-RAN-Use-Cases-Detailed-Specification-ODR-References-v01
  • - NOK-2024.04.10-WG1-CR-0066-Shared_O-RU_Dynamic_Resource_Shifting-v02
  • - NOK.AO-2024.06.11-WG1UCTG-CR0065-SharedORU_Rehoming_SubUseCase-v03
  • - RMI-2023.05.17-WG1-CR-0001-Shared-ORU-Basic-Resiliency-use-case-v01
| -| 2024.07.05 | 14.00.03 | Clean version for WG1 approval | -| 2024.07.18 | 14.00.04 | WG1 review comments are addressed, and approval is completed. | -| 2024.07.18 | 14.00.05 | All changes accepted, clean version. | -| 2024.07.18 | 15.00 | Final version 15.00 | -| 2024.09.10 | 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.03-WG1-UCTG-CR-0027-UseCasesDetailedSpecification-Use Case 26-Interference-Prediction_v2
| - -| | | | -|------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | |
  • - JNPR-2024.08.05-WG1-CR-0061-O-RAN-Use-Cases-Detailed-Specification-ODR-References-Editorial_Change-v01
  • - MTR.AO-2024.06.02-WG1UCTG-CR0002-Detailed-Specification-Use Case 26-Interference Detection and Optimizatio-r4
| -| 2024.11.04 | 15.00.02 |

Addition of CRs:

  • - JNPR-2024.10.22-WG1-CR-0070-O-RAN-Use-Cases-Detailed-Specification-ETSI_PAS_Comments-v01
  • - DTAG-2024.09.24-WG1-CR-0003-Use case numbering-v03
  • - RMI.AO-2024.09.05-WG1-CR-0003-Shared-ORU-Resource-Shifting-use-case-v02
| -| 2024.11.15 | 15.00.03 |

Updated copyright statement on the cover page and footer to 2025

Editorial changes to align to O-RAN TS template v02.01

Added 3GPP Release 18 related text to Normative and Informative References clauses

Editorial updates

| -| 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 CR:

  • - JNPR-2024.12.10-WG1-CR-0089-O-RAN-Use-Cases-Detailed-Specification-ETSI_PAS_Comments-v01
| -| 2025.01.29 | 16.00.02 |

Addition of CRs:

  • - JNPR.AO-2025.01.13-WG1-CR-0090-O-RAN-Use-Cases-Detailed-Specification-Reference_Correction-v01
  • - JNPR-2025.01.13-WG1-CR-0091-O-RAN-Use-Cases-Detailed-Specification-Removal_of_TBDs-v01
| -| 2025.03.05 | 16.00.03 |

Addition of CRs:

  • - JNPR-2025.02.13-WG1-CR-0098-O-RAN-Use-Cases-Detailed-Specification-Rel-18-Upgrade-Normative-References-v01
  • - JNPR-2025.02.13-WG1-CR-0099-O-RAN-Use-Cases-Detailed-Specification-Rel-18-Upgrade-28.552-v01
  • - JNPR-2025.02.13-WG1-CR-0100-O-RAN-Use-Cases-Detailed-Specification-Rel-18-Upgrade-28.313-v01
  • - JNPR-2025.02.13-WG1-CR-0101-O-RAN-Use-Cases-Detailed-Specification-Rel-18-Upgrade-37.817-v01
  • - JNPR-2025.02.13-WG1-CR-0102-O-RAN-Use-Cases-Detailed-Specification-Rel-18-Upgrade-Informative-References-v01
  • - JNPR-2025.02.13-WG1-CR-0103-O-RAN-Use-Cases-Detailed-Specification-Rel-18-Upgrade-28.624-v01
  • - JNPR-2025.02.13-WG1-CR-0104-O-RAN-Use-Cases-Detailed-Specification-Rel-18-Upgrade-38.213-v01
| - -| | | | -|------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | |
  • - JNPR-2025.02.13-WG1-CR-0105-O-RAN-Use-Cases-Detailed-Specification-References-Corrections-v01
  • - JNPR-2025.02.13-WG1-CR-0106-O-RAN-Use-Cases-Detailed-Specification-Reference-Fix-v01
| -| 2025.03.20 | 16.00.04 |

Addition of CR:

  • - NOK-2025.02.24- O-RAN.WG1.TS.UCDS-CR0267-ShdORU_UC_SecurityReqmtReference-v03

Editorial updates to align to O-RAN TS 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 CRs:

  • - QCM.AO-2025.05.14-WG1-CR-0001-NES_Carrier_Cell_Switch_Off_On_update_entities-v01
  • - QCM.AO-2025.05.14-WG1-CR-0002-NES_Carrier_Cell_Switch_Off_On_update_solutions-v01
  • - QCM.AO-2025.05.14-WG1-CR-0003-NES_Carrier_Cell_Switch_Off_On_required_data_update-v01
  • - JNPR.AO-2025.05.15-WG1-CR-0107-O-RAN-Use-Cases-Detailed-Specification-RAN_Slice_SLA_Assurance_Use_Case_Improvement-v01
  • - ERI.AO-2025.05.01-WG1-UCTG-CR-01- Cell Shaping Optimization-v03
| -| 2025.07.08 | 17.00.02 |

Addition of CRs:

  • - CMCC-2025.02.12-WG1-CR-0029-O-RAN-Use-Cases-Detailed-Specification-RAN Edge Computing Resource Information Exposure-v06
  • - CMCC-2025.02.11-WG1-CR-0030-O-RAN-Use-Cases-Detailed-Specification-Joint Communication and Computing Optimization for V2X Communications for CCIN-v06
  • - CMCC.AO-2025.02.11-WG1-CR-0031-O-RAN-Use-Cases-Detailed-Specification-Multiaspect handover optimization for CCIN-v06

Editorial updates

Editorial updates to align to O-RAN TS template v05

| -| 2025.07.10 | 17.00.03 | Clean version for WG1 approval | -| 2025.07.18 | 17.00.04 | WG1 review comments are addressed, and approval is completed. | -| 2025.07.18 | 17.00.05 | All changes accepted, clean version. | -| 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-UCDS-CR-0033-NES-External_Power_Source_Coordination_based_ES_Solution-v02
| - -| | | | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | |
  • - RMI.AO-2025.08.05-WG1-UCTG-UCDS-CR-0034-NES-External_Power_Source_Coordination_based_ES_Required_data-v01
  • - RMI.AO-2025.08.06-WG1-UCTG-CR-0036-NES-PA_Power_Optimization_ES_O1 based solution-v01
  • - RMI.AO-2025.08.06-WG1-UCTG-CR-0037-NES-PA_Power_Optimization_ES_E2 based solution-v01
  • - RMI.AO-2025.08.06-WG1-UCTG-CR-0038-NES-PA_Power_Optimization_ES_Required_data-v01
| -| 2025.11.21 | 18.00.02 | Addition of CRs:
  • - ERI.AO-2025.10.01-WG1-UCTG-CR-002- Cell Shaping Optimization Updates - v02
  • - ERI.AO-2025.10.01-WG1-CR-175-UCTG-Intent-driven-management-v04
  • - RMI.AO-2025.10.15-WG1-UCTG-CR-0041-NES-RF_Channel_Reconfiguration_O1_based_solution-v05
  • - RMI.AO-2025.10.15-WG1-UCTG-CR-0042-NES-RF_Reconfiguration_E2_based_solution-v05
  • - RMI.AO-2025.10.15-WG1-UCTG-CR-0043-NES-RF_Reconfiguration_Required_data-v04
  • - RMI.AO-2025.10.15-WG1-UCTG-CR-0044-NES-Advanced_Sleep_Mode_O1_based_solution-v04
  • - RMI.AO-2025.10.15-WG1-UCTG-CR-0045-NES-Advanced_Sleep_Mode_E2_based_solution-v04
  • - RMI.AO-2025.10.15-WG1-UCTG-CR-0046-NES-Advanced_Sleep_Mode_Required_data-v03
Editorial corrections | -| 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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/01b37b45a159c6e8efb7e2f67f99ba68_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/02ca6d9ed0f558acba26f05c300255dc_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/02ca6d9ed0f558acba26f05c300255dc_img.jpg deleted file mode 100644 index e26bdf7001785f0939bce9c74a3dd99165343652..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/02ca6d9ed0f558acba26f05c300255dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d557d318158c46721f1d43def828f9e5f09769955314d2e418321d90399770c -size 148836 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/041486a30f2434ca0821ab7bed8e6492_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/041486a30f2434ca0821ab7bed8e6492_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/041486a30f2434ca0821ab7bed8e6492_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/05ec650892a1d3916ffe3d2a7ec29928_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0603e0bad64a10c96372bbcf8c5d0d14_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0603e0bad64a10c96372bbcf8c5d0d14_img.jpg deleted file mode 100644 index 21f65734b7a842b796bceb4d8afa5e9327681529..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0603e0bad64a10c96372bbcf8c5d0d14_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0c9e1d9c97bd83851eae44bf4e7ac52748558d74fea78f5d03ec0e840ebfbc84 -size 205855 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/06e272c534fab6c7202d1355b043faf6_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/07bae2d456e460215a6b74db040d9b6c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/07bae2d456e460215a6b74db040d9b6c_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/07bae2d456e460215a6b74db040d9b6c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0827b9260fe5458dbe416ebfc78c469e_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/09032127b49c74c07fdc4e0d5275a115_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/09032127b49c74c07fdc4e0d5275a115_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/09032127b49c74c07fdc4e0d5275a115_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0a278c1194f7b78236442a1c85cf70b5_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0a278c1194f7b78236442a1c85cf70b5_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0a278c1194f7b78236442a1c85cf70b5_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0a65720e640be13541e947c06c7a8c7f_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0a7bd7c5b5e975e353b207d6845215c1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0a7bd7c5b5e975e353b207d6845215c1_img.jpg deleted file mode 100644 index 131b7eea32172b50e54edf2ca044ab961f948d2d..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0a7bd7c5b5e975e353b207d6845215c1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:56badda7761eb0c445c82df50d659bf12523eb0058486956bd4f22cd36fa2467 -size 89429 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0c6aeaf9973cd03cff19dd3f0ca1314e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0c6aeaf9973cd03cff19dd3f0ca1314e_img.jpg deleted file mode 100644 index 92d27ee55b83f9ccec60a37fcf6a95e199d64d6c..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0c6aeaf9973cd03cff19dd3f0ca1314e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2312360e34fc4a340e90f11be0be455145a1ef170498991548901caf35196790 -size 4522 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0d2f92b554f88f7f5b03f23faec94dba_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0d2f92b554f88f7f5b03f23faec94dba_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0d2f92b554f88f7f5b03f23faec94dba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0e2a8954ad6cb6a913374fe51484fce5_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0e2a8954ad6cb6a913374fe51484fce5_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0e2a8954ad6cb6a913374fe51484fce5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg deleted file mode 100644 index 92d27ee55b83f9ccec60a37fcf6a95e199d64d6c..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2312360e34fc4a340e90f11be0be455145a1ef170498991548901caf35196790 -size 4522 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0e50822d868aa19c8aa37bfb98002a25_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0e50822d868aa19c8aa37bfb98002a25_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/0e50822d868aa19c8aa37bfb98002a25_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1099a4137017f2d9721d546bbb1e9362_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/116a62c978d6a7d1b7830c1ea13e2993_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/116a62c978d6a7d1b7830c1ea13e2993_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/116a62c978d6a7d1b7830c1ea13e2993_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/118d1daec0d1a3e2a27924fe38e6d3cc_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/118d1daec0d1a3e2a27924fe38e6d3cc_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/118d1daec0d1a3e2a27924fe38e6d3cc_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/11b3d3cc56f71f80a268a31bd42103e9_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/11b3d3cc56f71f80a268a31bd42103e9_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/11b3d3cc56f71f80a268a31bd42103e9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/12b3831f83d090aaff6aecb06354f250_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/12b3831f83d090aaff6aecb06354f250_img.jpg deleted file mode 100644 index 088336c145b9e8279945e0a1608ea310c1f0ef8b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/12b3831f83d090aaff6aecb06354f250_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:db87bd5c94709b49dd69e8fd74cdb2ea5d02bd496e65460395f362f2106c7cf6 -size 158847 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg deleted file mode 100644 index b7a22be3bbf4634a01e74146584a5ce6c7cb38ea..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/13249a22bfff48bf6d20110d7228bfcd_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1396371bb5cf61891981fff2e338ec58_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/13fbd97d3a93abb4c723c50966c8cd14_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/13fbd97d3a93abb4c723c50966c8cd14_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/13fbd97d3a93abb4c723c50966c8cd14_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg deleted file mode 100644 index 0384f5e8e824e50ff48b1fbe08f24c83f014cff2..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5d1eef2d33d275031cd8dcb5ffd6bc48799861b16d2d1f5a4622d9f1e3af54aa -size 143378 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/14af8d47efd24c21fddf71b2415b6397_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/153b4763edcf6b16d783052c7ad165f1_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/15574508acc09ee822bfbd5ad0954c5a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/15574508acc09ee822bfbd5ad0954c5a_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/15574508acc09ee822bfbd5ad0954c5a_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/16b08981199f29066db206d1e31e6e47_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/16b08981199f29066db206d1e31e6e47_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/16b08981199f29066db206d1e31e6e47_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/189ac86054d2d468016d2091f22dfc5d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/189ac86054d2d468016d2091f22dfc5d_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/189ac86054d2d468016d2091f22dfc5d_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/199a8b4c5c620006757a17e930769566_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/199a8b4c5c620006757a17e930769566_img.jpg deleted file mode 100644 index 3f032df74539406cb90c75fb1d0f2f5a94df5fde..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/199a8b4c5c620006757a17e930769566_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:96517aa41e177ec222fa3c82c94dfcd2a56224b52dbc71bcc3d9bd557cdcd050 -size 118916 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1b7861077e6bb3e95f508e0ceeda5b0e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1b7861077e6bb3e95f508e0ceeda5b0e_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1b7861077e6bb3e95f508e0ceeda5b0e_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1baaba7a6e54e77197475726c871067d_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1baf92180f2964741688e8215d7183da_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1baf92180f2964741688e8215d7183da_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1baf92180f2964741688e8215d7183da_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1bc1746388cb64bf23b356ce2365dfc2_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1bc1746388cb64bf23b356ce2365dfc2_img.jpg deleted file mode 100644 index ebfba35668d46b46a2435da79e13826b9c382912..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1bc1746388cb64bf23b356ce2365dfc2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f5a418571abb7d6dd7b5de78d605f130292feaf36c95bd883f570594e2d31e0a -size 125704 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1d7348fac9ef4446e3f7e5f0e15c007b_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1d7348fac9ef4446e3f7e5f0e15c007b_img.jpg deleted file mode 100644 index 4d19f68b0f14ca5c4624d387346b192683b0c84b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1d7348fac9ef4446e3f7e5f0e15c007b_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg deleted file mode 100644 index 4d19f68b0f14ca5c4624d387346b192683b0c84b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1d92d4ad55f2aa411dc849438982f26b_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1da00d32e4d978dc1064b4d6b74d865c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1da00d32e4d978dc1064b4d6b74d865c_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1da00d32e4d978dc1064b4d6b74d865c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg deleted file mode 100644 index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1e7157ed1c2b915b5b1823b6ad189038_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.Use-Cases-Detailed-Specification-R005-v19.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1f0d4018f872bfcffec260045c6dd734_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1ff7828d681947990fac3e7bad35dd86_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1ff7828d681947990fac3e7bad35dd86_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/1ff7828d681947990fac3e7bad35dd86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/21023d70b19c3181ccce4390ea153e38_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/21023d70b19c3181ccce4390ea153e38_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/21023d70b19c3181ccce4390ea153e38_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/21b431575d18ed23db9ef488c8dec706_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/21b431575d18ed23db9ef488c8dec706_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/21b431575d18ed23db9ef488c8dec706_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/21cfcb7e235dba52c53c8cf7b10f36aa_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/21cfcb7e235dba52c53c8cf7b10f36aa_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/21cfcb7e235dba52c53c8cf7b10f36aa_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/22117363b092d194772c750e321202cc_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/22117363b092d194772c750e321202cc_img.jpg deleted file mode 100644 index d5c073d8d3adae95756b9aa3a420329c14c07706..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/22117363b092d194772c750e321202cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:653e42d96a085b546971dc38769016af19d63ed665faa9c4370b22c37945a329 -size 228795 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/226bcc7921bff55dc14cac630460ab92_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/226bcc7921bff55dc14cac630460ab92_img.jpg deleted file mode 100644 index 040bff082765b416400d0486644cf62df290ce39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/226bcc7921bff55dc14cac630460ab92_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2a81f4ba14b71ab8680f1eab388e6eb42152402d827b2710500d799ca57c980c -size 4683 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/226f5e462c99b71e08dc9abaa5ae260c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/227840abf8cd09f4f3e83336421daccb_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/22f30783614672d201275c116a5d8516_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/233a8b9743fe86cccae4bfca4aa9a0b0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/233a8b9743fe86cccae4bfca4aa9a0b0_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/233a8b9743fe86cccae4bfca4aa9a0b0_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/23781f394f3709bc3a1e68044179b0d4_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/23781f394f3709bc3a1e68044179b0d4_img.jpg deleted file mode 100644 index 0eccc6be206aebc37de06ad66f4f51039ef22852..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/23781f394f3709bc3a1e68044179b0d4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5ca2ab3c23ba68a944001a0b3cb372234901bec02fa4a8bd40daf076b4837d6b -size 43034 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/23b110b75da6b415520918830060195e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/23b110b75da6b415520918830060195e_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/23b110b75da6b415520918830060195e_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/24a3cc3bc7bd963ec2c4ceaf3e548457_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/24a3cc3bc7bd963ec2c4ceaf3e548457_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/24a3cc3bc7bd963ec2c4ceaf3e548457_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/24ad8881354fe6ad6a21dd40dfe8c8bb_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/24ad8881354fe6ad6a21dd40dfe8c8bb_img.jpg deleted file mode 100644 index ebe27e9a6033c77ab42e82750ff02f9762231442..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/24ad8881354fe6ad6a21dd40dfe8c8bb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d124f0603aa14c55625ef532d34287ca8fedc798b6601aa3a02d1163f08c10d6 -size 131065 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/253600420ae7bd7d0119563b895cbf8a_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/255efa1d461fc79b4ed367aaec11637f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/255efa1d461fc79b4ed367aaec11637f_img.jpg deleted file mode 100644 index bc8b1866db59de5f57f665f106edafa8572832a0..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/255efa1d461fc79b4ed367aaec11637f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ce229c9cc27484cfba6297aa72c473ca48f067885b8a2013c6d69496ff0c04c1 -size 184208 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/256ec100c3aeedb411eee5a09386812e_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg deleted file mode 100644 index 671085354705cced783627c4002fb68a8761eea8..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:34510de37113edf5ecd7b609e1b9913a50ce23466055d436e0f3d1840567e86d -size 4526 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/266ed4b8590c3bfce2d6ccf95b143242_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/266ed4b8590c3bfce2d6ccf95b143242_img.jpg deleted file mode 100644 index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/266ed4b8590c3bfce2d6ccf95b143242_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.Use-Cases-Detailed-Specification-R005-v19.00/images/26f0c643a3e0c8034b16008c351b5b65_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/26f0c643a3e0c8034b16008c351b5b65_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/26f0c643a3e0c8034b16008c351b5b65_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg deleted file mode 100644 index 2b88127555626af55fc0d3f9358d08985adcda0b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5bc5aeb2df0ff72d49d991d8ac9e205858b1a95e29bcc9969411fff8465662cb -size 4259 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2965c9e826cfc7efc1936b2e25f48e63_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2965c9e826cfc7efc1936b2e25f48e63_img.jpg deleted file mode 100644 index 72358cecdcc0054d3e6af1419205cc3cb5664118..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2965c9e826cfc7efc1936b2e25f48e63_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5430acb844920254ce6c4e081774d522b03d5ac7f8284b3de8afa126f9bdd8f4 -size 45268 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2981200c3b8faff326c7ace0c91f0687_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2981200c3b8faff326c7ace0c91f0687_img.jpg deleted file mode 100644 index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2981200c3b8faff326c7ace0c91f0687_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.Use-Cases-Detailed-Specification-R005-v19.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/29f3760c0230631eb03f67030ef65ed0_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2a185522b492253375ed16f0c515c230_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2a185522b492253375ed16f0c515c230_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2a185522b492253375ed16f0c515c230_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2b7c350726e78976d2dfd3ce90daa9f7_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2c4b84a66cab050595b6ee02d8799bb0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2c4b84a66cab050595b6ee02d8799bb0_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2c4b84a66cab050595b6ee02d8799bb0_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg deleted file mode 100644 index d5389accc8d3638e5156f7a38a21b29359d79293..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e0ef78e54358d4470c88cf57129be5f112b99967de6fc84d00f7b0a8c9a3eb36 -size 23220 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2cf96b55beaa98ebc755c7405b1adbeb_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2cf96b55beaa98ebc755c7405b1adbeb_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2cf96b55beaa98ebc755c7405b1adbeb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2d1bc5eed8281b9364808514bacdb32a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2d1bc5eed8281b9364808514bacdb32a_img.jpg deleted file mode 100644 index 2d51a4e23db6f1017e35a922429fca516d60f0c1..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2d1bc5eed8281b9364808514bacdb32a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:65e3cda1fa0e627fe775b1f863f4ba28c2a91ab60cb3b25104c35ce434502e39 -size 4500 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2db1000cc36f2eeb41c57c2ba7fd2dc6_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2db1000cc36f2eeb41c57c2ba7fd2dc6_img.jpg deleted file mode 100644 index 6c1a0cdca63e81126a71c4b1f453108dc092dfa7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2db1000cc36f2eeb41c57c2ba7fd2dc6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9dcf00c15e89eab59c267f830045d125f5b069dcf780f76855312f9d53a591bd -size 101396 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2de65c6883946871f46308ff85ad7faf_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2de65c6883946871f46308ff85ad7faf_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2de65c6883946871f46308ff85ad7faf_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2e1d7b4c07a00dd0f26b51558abbe428_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2e1d7b4c07a00dd0f26b51558abbe428_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2e1d7b4c07a00dd0f26b51558abbe428_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2eea01382188b70064fa2818361d89f1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2eea01382188b70064fa2818361d89f1_img.jpg deleted file mode 100644 index c29201d0030fdecc62b33137d8230a2ddd5a36a3..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2eea01382188b70064fa2818361d89f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1bf1eebb35af4b3e59eda8ec62436ea4f24c245995dbce276c9f29a2ef5e9569 -size 4544 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2f6073b866a873087bacb1adb0b0852c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2f6073b866a873087bacb1adb0b0852c_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2f6073b866a873087bacb1adb0b0852c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2f983ce3451ef9194e19e72e0ad04c83_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2f983ce3451ef9194e19e72e0ad04c83_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2f983ce3451ef9194e19e72e0ad04c83_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2fcfff451a38d27b4253203bae9c5a48_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2fcfff451a38d27b4253203bae9c5a48_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2fcfff451a38d27b4253203bae9c5a48_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2ffb32ca2d8acda8228f0301aa7f52e0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2ffb32ca2d8acda8228f0301aa7f52e0_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/2ffb32ca2d8acda8228f0301aa7f52e0_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3107f66da1c3556cee065608ee86f7e4_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3107f66da1c3556cee065608ee86f7e4_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3107f66da1c3556cee065608ee86f7e4_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3117e1f4e4767bab3f5c7cfaf4804652_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/318db222fae24a59c370fa6471d541b8_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/318db222fae24a59c370fa6471d541b8_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/318db222fae24a59c370fa6471d541b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/31a464e0e5a8a9c5d10fd33d2ed26347_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/31a464e0e5a8a9c5d10fd33d2ed26347_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/31a464e0e5a8a9c5d10fd33d2ed26347_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/320bb6a0e7b3cc0803a15b231b3bc311_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/320bb6a0e7b3cc0803a15b231b3bc311_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/320bb6a0e7b3cc0803a15b231b3bc311_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/32d2216a419e1d11a63f930a6106c627_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/32d2216a419e1d11a63f930a6106c627_img.jpg deleted file mode 100644 index ec3ee1e099e4d8c2d4222d5dff1c2630111603a2..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/32d2216a419e1d11a63f930a6106c627_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4391252b8dd3d236a616c9a91f4c94f689fc69d5b4db910d91930cd5b7afbd9e -size 3650 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/35037145df6cd8b5520bbfebf46c9433_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/35037145df6cd8b5520bbfebf46c9433_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/35037145df6cd8b5520bbfebf46c9433_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/359093c76d121867106328fa8adfe8ff_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/359093c76d121867106328fa8adfe8ff_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/359093c76d121867106328fa8adfe8ff_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/365fdce90bacd7a819819a2e05e70403_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/365fdce90bacd7a819819a2e05e70403_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/365fdce90bacd7a819819a2e05e70403_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/366398d17120ce12a2c36b95c54033c5_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/366398d17120ce12a2c36b95c54033c5_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/366398d17120ce12a2c36b95c54033c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/36e2350ea1a3ef6ca68c655394300a91_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg deleted file mode 100644 index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/36e4a08fb5114c98c80f946714cc6c30_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.Use-Cases-Detailed-Specification-R005-v19.00/images/37104233d1b6d7728427e833816594dc_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/37104233d1b6d7728427e833816594dc_img.jpg deleted file mode 100644 index eb26325b4d7df6348113d3a0b633768ac257480f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/37104233d1b6d7728427e833816594dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:402906701dd0eb90de5f77aca4b89077ce670d750c7d4934f14316098d68723e -size 110872 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/372a0b094d72de45d94c6c8d52714e9a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/372a0b094d72de45d94c6c8d52714e9a_img.jpg deleted file mode 100644 index e2f185125a3bc3c013eefd91df5de010d1285b61..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/372a0b094d72de45d94c6c8d52714e9a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c9d9478e58f9a3476c0be7954550a945d98f5bf01e701c23d0765c5ed7015862 -size 300597 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/378417d45871e98cf0371e2dfe49ef55_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/378417d45871e98cf0371e2dfe49ef55_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/378417d45871e98cf0371e2dfe49ef55_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/37d5d6957e175201847002c556b5a29d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/37d5d6957e175201847002c556b5a29d_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/37d5d6957e175201847002c556b5a29d_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/37d8d885fed5ec107803a8eeceb71686_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/37d8d885fed5ec107803a8eeceb71686_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/37d8d885fed5ec107803a8eeceb71686_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/384d97a0c67bd4f219a452c3cd658684_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/384d97a0c67bd4f219a452c3cd658684_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/384d97a0c67bd4f219a452c3cd658684_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index 2d51a4e23db6f1017e35a922429fca516d60f0c1..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:65e3cda1fa0e627fe775b1f863f4ba28c2a91ab60cb3b25104c35ce434502e39 -size 4500 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/39e964ecd6d6a7fd1d783271aa934f23_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/39e964ecd6d6a7fd1d783271aa934f23_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/39e964ecd6d6a7fd1d783271aa934f23_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3a3831d50dc74b7ebbec3e1d96eea588_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3a3831d50dc74b7ebbec3e1d96eea588_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3a3831d50dc74b7ebbec3e1d96eea588_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3a4f4369128594c5db0aa6b853c0666e_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg deleted file mode 100644 index 49e08bd7d534ac4322f84843a7456380dcec579f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e97339d138477b3fc4f7576137b0850d72619e7bda08e298a2c6e821ed5b086e -size 165075 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3b6c4e5a462a828bef2d462df300da37_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3b6c4e5a462a828bef2d462df300da37_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3b6c4e5a462a828bef2d462df300da37_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3b74c6d31e743e85101650db369fe692_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3b74c6d31e743e85101650db369fe692_img.jpg deleted file mode 100644 index e375d96ba0a2aa63aed7e284db37dca91842700a..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3b74c6d31e743e85101650db369fe692_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5735d971fb9d7c521c2c565e949c57390d02f1fa1a20a5194abe6686123dc3a -size 95033 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3ce04f1c7128814978c6b34d654a25cc_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3ce04f1c7128814978c6b34d654a25cc_img.jpg deleted file mode 100644 index bfe21d9d6b60d695a838dbb098ab8696f891bcdc..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3ce04f1c7128814978c6b34d654a25cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:691719a56842f1956926dcb70bbe9325b2d5f3d2db4a8e1dc45c445e454632aa -size 95464 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3cf773bd0581c54adb3aea51556f70b9_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3cf773bd0581c54adb3aea51556f70b9_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3cf773bd0581c54adb3aea51556f70b9_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/3f727e6c0d6658bc53ea10905c4561dd_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/40e106822047971ea364d73846848ecd_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/40e106822047971ea364d73846848ecd_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/40e106822047971ea364d73846848ecd_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/41863cc6f48c5a6ff0290186547042d9_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/41d2a2a58f53d1013a114da9c02f726e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/41d2a2a58f53d1013a114da9c02f726e_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/41d2a2a58f53d1013a114da9c02f726e_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/426342bd710b59091374594dd7d65234_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/426342bd710b59091374594dd7d65234_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/426342bd710b59091374594dd7d65234_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4312b91d86300ea45d4ed0884648d447_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4312b91d86300ea45d4ed0884648d447_img.jpg deleted file mode 100644 index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4312b91d86300ea45d4ed0884648d447_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.Use-Cases-Detailed-Specification-R005-v19.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/448ea8ec42a54ed159e2974fe85dd4f5_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/45a161027983c0b508f6269c35551968_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/45a161027983c0b508f6269c35551968_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/45a161027983c0b508f6269c35551968_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4609bed5ef32a7936e15f90c7abff39e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4609bed5ef32a7936e15f90c7abff39e_img.jpg deleted file mode 100644 index 81079d3b2f3b846614f56453692fde8ea061d483..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4609bed5ef32a7936e15f90c7abff39e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0815a342b8e119da2a71df250c72dc3c38c65aa40df09ffe5de52d7e9c48f743 -size 142403 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4628881725ec2d73799a0521cb4036c5_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4628881725ec2d73799a0521cb4036c5_img.jpg deleted file mode 100644 index b024a3cbd7829b51aa0bd687e412d44769965b37..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4628881725ec2d73799a0521cb4036c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:72343e8fa23a0016bf438885ca5e57135c5c8f3d53d2fab3058b2f8938056e4f -size 131078 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4665bbd9c3079135f242a62a0e931eec_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4665bbd9c3079135f242a62a0e931eec_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4665bbd9c3079135f242a62a0e931eec_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/47aaa88afec21e26eb33420078f4936a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/47aaa88afec21e26eb33420078f4936a_img.jpg deleted file mode 100644 index 19ab635c9b2ea409462f891ece66711012ce50f7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/47aaa88afec21e26eb33420078f4936a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f12da8d5e4c1c056c065a1a97c5d91d21250fc13c7c909a44288ee5b3cd54477 -size 287110 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/47c8f3782d7566332f5685e1b7958b33_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/47c8f3782d7566332f5685e1b7958b33_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/47c8f3782d7566332f5685e1b7958b33_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/488b6387bc5fe15b9528eca7968a8733_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4932f76f000f1673ac40baf1419fbb3b_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/496e5dfc146af6bcc2b3bc2eaf82826c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/496e5dfc146af6bcc2b3bc2eaf82826c_img.jpg deleted file mode 100644 index 4d19f68b0f14ca5c4624d387346b192683b0c84b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/496e5dfc146af6bcc2b3bc2eaf82826c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 6612f9450ea5be62816aa85d35bd3da2b8a92d8d..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6e8b0cc383947a7679f11ff80d617ca5ec6b2da5282678485bf03cc5a8f6f68 -size 4508 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4a2d4d9018b37c44a58838114803711f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4a2d4d9018b37c44a58838114803711f_img.jpg deleted file mode 100644 index 13fa1b5fe02c11211c7e82814c99b68c2c352007..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4a2d4d9018b37c44a58838114803711f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e8fd7ab891a36bb0d1150e357978fdf063e5cc38f1c29ae9c2d44485e6ad6f42 -size 178712 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4b241e690aacaf391e2b28dd9307575c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg deleted file mode 100644 index b7a22be3bbf4634a01e74146584a5ce6c7cb38ea..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4b297191fa254f84c021e73b3b79e860_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4c1d8ed1a2c9ff9594c1ca4f179a9c33_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4c1d8ed1a2c9ff9594c1ca4f179a9c33_img.jpg deleted file mode 100644 index 4ddee966eb5429f264fd4492bb1aabbcf1ebe493..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4c1d8ed1a2c9ff9594c1ca4f179a9c33_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e2697e98f572f246fc74710daeb12c25a3f5cb142c0caa99723d2bc054d26c2e -size 201010 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4ced45096fe3cf5adc96ec6b94f07e4f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4ced45096fe3cf5adc96ec6b94f07e4f_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4ced45096fe3cf5adc96ec6b94f07e4f_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4d6f13ca04e51575f82581193c077f64_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4e58d71a7f0cda1ca24fac1ee80a0c7c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4e58d71a7f0cda1ca24fac1ee80a0c7c_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4e58d71a7f0cda1ca24fac1ee80a0c7c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4ecfb2f8adee0634d48422a73bd1a491_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4ecfb2f8adee0634d48422a73bd1a491_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/4ecfb2f8adee0634d48422a73bd1a491_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5009e30a55479d3941af523871208f9d_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5009e30a55479d3941af523871208f9d_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/523ab7b925beb555f88b2e1e1336974f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/523ab7b925beb555f88b2e1e1336974f_img.jpg deleted file mode 100644 index 607da6d0467dfc47a9120536b68a885711cf0516..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/523ab7b925beb555f88b2e1e1336974f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1364ae9bf822f74b63c41ff6124d5bc8eadaa6f5431f1df1e774bf25c0ff371d -size 91461 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg deleted file mode 100644 index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/527578a453197a501cd46c0d0e579cd1_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.Use-Cases-Detailed-Specification-R005-v19.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/52a225f71b166b0c65c2f29f32a79f7f_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/52b3fa2e98cf5380d8791717d296d9d8_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/52b3fa2e98cf5380d8791717d296d9d8_img.jpg deleted file mode 100644 index 6646b4531a4f6fdff1309b0047ccb91a40cf778d..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/52b3fa2e98cf5380d8791717d296d9d8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d2e8640887536e25f4c2ddaf04f1418c42c7ea8bf3446186f5e1568054acd78f -size 237241 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/53499879d98034410ecba2c386c58f0c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/53499879d98034410ecba2c386c58f0c_img.jpg deleted file mode 100644 index ae7944bc412f4292004794791f44afdbcd97ac4a..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/53499879d98034410ecba2c386c58f0c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:31c6033d6964f47c43c672287f3421b78d07db4bff2902081a300d3f36f95f8e -size 171529 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg deleted file mode 100644 index 4d19f68b0f14ca5c4624d387346b192683b0c84b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5441c05741f8a35ee5d6673b0b0ebb8b_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5441c05741f8a35ee5d6673b0b0ebb8b_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5441c05741f8a35ee5d6673b0b0ebb8b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/54e6016445a458d4c0aef4acc71bb0c8_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/54e6016445a458d4c0aef4acc71bb0c8_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/54e6016445a458d4c0aef4acc71bb0c8_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/55c1b9efdb97c2b7dd16b497c5b56d3c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/55c1b9efdb97c2b7dd16b497c5b56d3c_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/55c1b9efdb97c2b7dd16b497c5b56d3c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/568031aac86c633aab96b734dba3835e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/568031aac86c633aab96b734dba3835e_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/568031aac86c633aab96b734dba3835e_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/56a00f931e8602f822917af7fa379c0d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/56a00f931e8602f822917af7fa379c0d_img.jpg deleted file mode 100644 index 4bb6438470eda4d24e5b8c1a84147e76d2d45292..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/56a00f931e8602f822917af7fa379c0d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0ea0533c5de40411187d4ea844ebad115b05b8d2be4d262901c1a235c64c9108 -size 99944 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg deleted file mode 100644 index c427a0417c84bff52292b3e90e5aa5007c4023d6..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a37887af953398552545d5e05eb3c882b400543d24497e5c9175b7cb46ad0f37 -size 183526 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/56c8fcd83f1ab2e62033a1f6e7cfa3a1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/56c8fcd83f1ab2e62033a1f6e7cfa3a1_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/56c8fcd83f1ab2e62033a1f6e7cfa3a1_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5911c1f65edf9b3f8469ddacd0756b26_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5911c1f65edf9b3f8469ddacd0756b26_img.jpg deleted file mode 100644 index 09653b0ad0b480906ca38177bbb332f54f18b38a..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5911c1f65edf9b3f8469ddacd0756b26_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4e600760c3f9db85498621019afc937aebecd46a466f61f6b6dbad5a654935de -size 100016 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index b7a22be3bbf4634a01e74146584a5ce6c7cb38ea..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/59368942873b0c35eef79a7a985025dc_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg deleted file mode 100644 index c29201d0030fdecc62b33137d8230a2ddd5a36a3..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1bf1eebb35af4b3e59eda8ec62436ea4f24c245995dbce276c9f29a2ef5e9569 -size 4544 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/59fcc0e3699f239444841881a2e75da0_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5a3dccee8ce4d2fa1986aba4ae8ad6e2_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5a3dccee8ce4d2fa1986aba4ae8ad6e2_img.jpg deleted file mode 100644 index daccbeb70dc196ff2ea761e98ba0d576473743da..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5a3dccee8ce4d2fa1986aba4ae8ad6e2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57442bcc9ec0bcab0617bca8a36df5d973d23b07bab17b6782ec396109996538 -size 123962 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5a7ef674d3d47e22615920f270a52b5a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5a7ef674d3d47e22615920f270a52b5a_img.jpg deleted file mode 100644 index b235abc234f318b94db1eb669d27fe04d48d2a23..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5a7ef674d3d47e22615920f270a52b5a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:04fe0010c6b026d3e6a4927b8ad29acd46b8b84888d919b2f34b16d037b3f202 -size 112057 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5aa1fd73e15adc4c2fc5e57a9578755d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5aa1fd73e15adc4c2fc5e57a9578755d_img.jpg deleted file mode 100644 index 2003edf3292cb081cbf807ebe2d19597b02bc991..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5aa1fd73e15adc4c2fc5e57a9578755d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1ad0c83e0fe0dbd7a496a5626d4b3e0eeeef4263cffa9823f0838837dd27c204 -size 155969 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 2b88127555626af55fc0d3f9358d08985adcda0b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5bc5aeb2df0ff72d49d991d8ac9e205858b1a95e29bcc9969411fff8465662cb -size 4259 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5b41b3f299c364a673453693f7cf0689_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5b41b3f299c364a673453693f7cf0689_img.jpg deleted file mode 100644 index e40291c9d5b9f66d1702d4c2702f13115e2653d8..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5b41b3f299c364a673453693f7cf0689_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3b72c9ad824efb1b90cfcd66a1baa72ae197287e4398881c78ce27a3a7130619 -size 179658 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5e185b54d270cd15d1299478a13f1f97_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5e185b54d270cd15d1299478a13f1f97_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5e185b54d270cd15d1299478a13f1f97_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5e38bd2f95d0f22ab5091fa99f29ff01_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5e38bd2f95d0f22ab5091fa99f29ff01_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5e38bd2f95d0f22ab5091fa99f29ff01_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5fa61cb21e87cecbe7049420f633a811_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5fa61cb21e87cecbe7049420f633a811_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5fa61cb21e87cecbe7049420f633a811_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5fbe6b9515c3d8f7d2526ca5bfbd012d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5fbe6b9515c3d8f7d2526ca5bfbd012d_img.jpg deleted file mode 100644 index 0b3b5084704d07132c45e9aa20700ebe0e2589ec..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/5fbe6b9515c3d8f7d2526ca5bfbd012d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:48a3522d0074881020c494e87bf30cbebcafb0855f0f63df7607e42074948410 -size 4573 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/600fbaabf10e40148498bda9961511ab_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/600fbaabf10e40148498bda9961511ab_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/600fbaabf10e40148498bda9961511ab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg deleted file mode 100644 index 92d27ee55b83f9ccec60a37fcf6a95e199d64d6c..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2312360e34fc4a340e90f11be0be455145a1ef170498991548901caf35196790 -size 4522 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index 571bc5618e7030e532b0944daa152a663439850f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57412e51da277a08af65bb44adea03223ad684f4dc8f6404914421b553365a40 -size 4507 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6254e6ff201e39d022a590c8b6e3de2b_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/62616918653bd50bc70542647d4caaed_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/62616918653bd50bc70542647d4caaed_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/62616918653bd50bc70542647d4caaed_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/62bcbcd2d72c7add43fc43355a3d212a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/62bcbcd2d72c7add43fc43355a3d212a_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/62bcbcd2d72c7add43fc43355a3d212a_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/638d4a1e55dbf75a122c4f778258f3cb_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/638d4a1e55dbf75a122c4f778258f3cb_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/638d4a1e55dbf75a122c4f778258f3cb_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/63c45f0c0f8bc8db8db6b78f6d78c264_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/63c45f0c0f8bc8db8db6b78f6d78c264_img.jpg deleted file mode 100644 index d54480b8dd7cdacbb53b4b175460cd73145208cb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/63c45f0c0f8bc8db8db6b78f6d78c264_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b0fb8e773091864a0448403bb0a408a1ff0b07a72dcbf54977b0afec5245a147 -size 213339 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/654cccb64b578f1e4a7d09b7ee5626b5_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/654cccb64b578f1e4a7d09b7ee5626b5_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/654cccb64b578f1e4a7d09b7ee5626b5_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6588b1c7f14069d96744b473ad663248_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/65cd234286445e716c91a9f734e510d9_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/65cd234286445e716c91a9f734e510d9_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/65cd234286445e716c91a9f734e510d9_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/65cf9633846ecab19f1a0b92fa8ecd9a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/65cf9633846ecab19f1a0b92fa8ecd9a_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/65cf9633846ecab19f1a0b92fa8ecd9a_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/65e8c0628536d6d4245e9ab46ba070c3_img.jpg deleted file mode 100644 index b3f1173a7811fa7f6c5778b0153025d198a3f3b7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/65e8c0628536d6d4245e9ab46ba070c3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ca28b8335c6f3984bbc66bddeb9e73dc2d1a4534e844b18967a0921d7f092a23 -size 101097 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6665298b5cd4fc5f777d91df7863dc6c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6665298b5cd4fc5f777d91df7863dc6c_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6665298b5cd4fc5f777d91df7863dc6c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/671d724633c3474b8092064d750ce939_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/671d724633c3474b8092064d750ce939_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/671d724633c3474b8092064d750ce939_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/67da7316a30be623c4c053d4d1eff952_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/67da7316a30be623c4c053d4d1eff952_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/67da7316a30be623c4c053d4d1eff952_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/67fd5cc2c3bec87e3a06d5ad92744560_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/67fd5cc2c3bec87e3a06d5ad92744560_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/67fd5cc2c3bec87e3a06d5ad92744560_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg deleted file mode 100644 index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/681c354e00e1c0fe098ba665ff155cb8_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.Use-Cases-Detailed-Specification-R005-v19.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg deleted file mode 100644 index 4d19f68b0f14ca5c4624d387346b192683b0c84b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/686705f78594bdc18af4f9cb04b455e0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/686705f78594bdc18af4f9cb04b455e0_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/686705f78594bdc18af4f9cb04b455e0_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6883c4a2aeca4cb08a9a7a95faa2645a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6883c4a2aeca4cb08a9a7a95faa2645a_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6883c4a2aeca4cb08a9a7a95faa2645a_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6983ff962c0a32659de18c30790e1519_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6983ff962c0a32659de18c30790e1519_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6983ff962c0a32659de18c30790e1519_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6a9c5a85a12499d60c5a3a75c643b852_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.Use-Cases-Detailed-Specification-R005-v19.00/images/6aff07583f1535949164b1e6f4ffd9ee_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6aff07583f1535949164b1e6f4ffd9ee_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6aff07583f1535949164b1e6f4ffd9ee_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6b0834ca8cdd18832ed461378d51dcb7_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6b1e3597147ab3d3e747185d6505a8ef_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6b1e3597147ab3d3e747185d6505a8ef_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6b1e3597147ab3d3e747185d6505a8ef_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6c8a96787f532bd1fa4719e738cf556f_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6cdb31bed6791fa0bd3fbc1e583b07ed_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6cdb31bed6791fa0bd3fbc1e583b07ed_img.jpg deleted file mode 100644 index d77dd8f0947567944bec8a445e1fd201f165fa35..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6cdb31bed6791fa0bd3fbc1e583b07ed_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:318f8bc8629042aed61f13b57b1652aa8d656c653546aa2fee8d2cc3f180bd56 -size 97430 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6d8454e3fdef6561c6f64adf0092e9b9_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6da08196de6831d44259c8a25e416c2d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6da08196de6831d44259c8a25e416c2d_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6da08196de6831d44259c8a25e416c2d_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6f52aa6e2a0da763ca0091b3771d1c25_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6f52aa6e2a0da763ca0091b3771d1c25_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6f52aa6e2a0da763ca0091b3771d1c25_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6f794c8c41326b510934ce3f3d622202_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6faa2c6456db4413927b19b9cbfe4176_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6faa2c6456db4413927b19b9cbfe4176_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6faa2c6456db4413927b19b9cbfe4176_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6fd1b2efc24f6bc630680f8de7c31576_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6fd1b2efc24f6bc630680f8de7c31576_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6fd1b2efc24f6bc630680f8de7c31576_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6fdf990c9cc944ccf5688a804f6ed35c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6fdf990c9cc944ccf5688a804f6ed35c_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6fdf990c9cc944ccf5688a804f6ed35c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6febae75ca030f36c2e737a316d1bc81_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6febae75ca030f36c2e737a316d1bc81_img.jpg deleted file mode 100644 index 2dcca11b370222167c5a06b5b4f4d49570891c0d..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/6febae75ca030f36c2e737a316d1bc81_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b8bd48b68939bae6d18084183879c7f7e2f7a49475198fb1af73152eabb91c20 -size 22228 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/70dab5b17ce15a319dd531324de9c9fe_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/70dab5b17ce15a319dd531324de9c9fe_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/70dab5b17ce15a319dd531324de9c9fe_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7137a384b59a4b2c2ff2bc879e38a6af_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7137a384b59a4b2c2ff2bc879e38a6af_img.jpg deleted file mode 100644 index a1ccfa96c8df5cfc7daa0ca4ce80d32f9657e2de..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7137a384b59a4b2c2ff2bc879e38a6af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4aef05dbc4abe9f74ef7480f2e94139e3f7e6c373549b655bb1bae1f93b19e7a -size 101732 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7183d7b44e8c46abd64438b3894a0902_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7183d7b44e8c46abd64438b3894a0902_img.jpg deleted file mode 100644 index 4d19f68b0f14ca5c4624d387346b192683b0c84b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7183d7b44e8c46abd64438b3894a0902_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/728298e0fbc8de5f3894ce6cb10fb413_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/72b8a8f5df5818870c46d57b4ac65174_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/72b8a8f5df5818870c46d57b4ac65174_img.jpg deleted file mode 100644 index 0c644200f13acc70268e4cd4afdcd434355d111b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/72b8a8f5df5818870c46d57b4ac65174_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2bf24c34ac982ce81e7cb2a162768d4e9bfb55610a6323fe056a1ccd8a401a98 -size 141128 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/73923a5d4eee13d96aa9bd1622b0976f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/73923a5d4eee13d96aa9bd1622b0976f_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/73923a5d4eee13d96aa9bd1622b0976f_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/73dff6b45b2b9ffd384bab3235f869af_img.jpg deleted file mode 100644 index 55f8343b76e7af3084c9996b71fb065f745045ca..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/73dff6b45b2b9ffd384bab3235f869af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:97560064abcd9d9bab6d4de642002e1a688923a66c899537b8f2deb0119b76df -size 57342 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7469f7d890531be66ff585ef273e6c1b_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7469f7d890531be66ff585ef273e6c1b_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7469f7d890531be66ff585ef273e6c1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg deleted file mode 100644 index 215db06c9de06a57fe41f54e761c56f92dc337e0..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a92572b511cb140935d4e39b662efa3d3b84941ea67fbeeeb9208afb911b9b8d -size 150177 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/76fb24764e6c9c644b30056855c81aa5_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/775e52e123d544d7749813722a13e82f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/775e52e123d544d7749813722a13e82f_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/775e52e123d544d7749813722a13e82f_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/77d11d3a8152805a6323635895fdea41_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/77d11d3a8152805a6323635895fdea41_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/77d11d3a8152805a6323635895fdea41_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/78b47bea9d645c52984f5f4c6740db05_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/78cc63c311cd723d756e4d38fc16ed2a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/78cc63c311cd723d756e4d38fc16ed2a_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/78cc63c311cd723d756e4d38fc16ed2a_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/79898de98da3367d0ea9beef38f5c01c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7a3d4c97055e3021cefb0c5850050bff_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7b0303896a557a9a495591a36349e5f7_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7b0303896a557a9a495591a36349e5f7_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7b0303896a557a9a495591a36349e5f7_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7c66f12495a47e87f0a0314a0d3a2eff_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7ccb49293384cf59a3bbe659b053f3cc_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.Use-Cases-Detailed-Specification-R005-v19.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index 6612f9450ea5be62816aa85d35bd3da2b8a92d8d..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6e8b0cc383947a7679f11ff80d617ca5ec6b2da5282678485bf03cc5a8f6f68 -size 4508 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7e12e1e0d03a03790d2e9d74c3454bff_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7e12e1e0d03a03790d2e9d74c3454bff_img.jpg deleted file mode 100644 index 20701ee3e0bd3aada5e741a7876ec8e7c074a01f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7e12e1e0d03a03790d2e9d74c3454bff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8a4970b75cc7efcb72a58992c2dbbebd1b23de7ce77d467a00aa6906db014d4a -size 120427 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7e86b957cd3c33e57d22a8389947ce46_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7e86b957cd3c33e57d22a8389947ce46_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7e86b957cd3c33e57d22a8389947ce46_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7fdddd449ff61579cf1f067a3bde63b0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7fdddd449ff61579cf1f067a3bde63b0_img.jpg deleted file mode 100644 index 1487e6ed57bf3823ee866812a517e753401af5cf..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/7fdddd449ff61579cf1f067a3bde63b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a3bbe49b42b5a07cce7030a914076a301d6d3bf01f271faf57b6d35998837118 -size 168213 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8071f58c3d57408857130711daf9effe_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8071f58c3d57408857130711daf9effe_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8071f58c3d57408857130711daf9effe_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/81513bd390d91f2e7a9b865cf50dce69_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/81513bd390d91f2e7a9b865cf50dce69_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/81513bd390d91f2e7a9b865cf50dce69_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/81b34087cd6755a80f84a70cf28fba82_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8237c46643affc7cc057ae950dbcf1f2_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/826bf0fa6fd822169e7a2b4e5f197dd4_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/826bf0fa6fd822169e7a2b4e5f197dd4_img.jpg deleted file mode 100644 index 0d0c3c5996fe41f4790a0e4b779aeb6e977e28e1..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/826bf0fa6fd822169e7a2b4e5f197dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b8c8384d2713a8c2e337d4d5c61fd01f1e5a0daf564b99c1bb9006f41afefc22 -size 227161 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg deleted file mode 100644 index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_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.Use-Cases-Detailed-Specification-R005-v19.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/83ee9f10bd3636e192d68decf7f04cec_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8447c5519e85d7a9e029fbf321da4c4f_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/854df8ad60507803253274673f9062cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/89100a6476d1d96f22c192db16502fec_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8a02c1bd6ac8111aead3a70a4aba750e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8a02c1bd6ac8111aead3a70a4aba750e_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8a02c1bd6ac8111aead3a70a4aba750e_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8ab30dbff406204a68c59ae7c1b77413_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8ab30dbff406204a68c59ae7c1b77413_img.jpg deleted file mode 100644 index 3b30ce6d6b609631489396ecee402e8981a333e6..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8ab30dbff406204a68c59ae7c1b77413_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fc61624ac2d3f2129231f95d4f0eb99b8a86c9aab7f33ccf49ba5d84bab4da42 -size 108322 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8abd61b74f37672d2b282ed022beab0f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8abd61b74f37672d2b282ed022beab0f_img.jpg deleted file mode 100644 index 13d3947c6f0eac53687d99c08b0c92691654f32c..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8abd61b74f37672d2b282ed022beab0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:afc993d9389459ca60134575af91006dbcb8a9aed7414fbb5377080cc83e96ba -size 120424 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8b36c56b042bf3e7ec9b29f35568fe66_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8b36c56b042bf3e7ec9b29f35568fe66_img.jpg deleted file mode 100644 index 6612f9450ea5be62816aa85d35bd3da2b8a92d8d..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8b36c56b042bf3e7ec9b29f35568fe66_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6e8b0cc383947a7679f11ff80d617ca5ec6b2da5282678485bf03cc5a8f6f68 -size 4508 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8b4befaffc5166da571069410e207aea_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg deleted file mode 100644 index 92d27ee55b83f9ccec60a37fcf6a95e199d64d6c..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2312360e34fc4a340e90f11be0be455145a1ef170498991548901caf35196790 -size 4522 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8bd9527f7ae16517a90c44e34ced8589_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8bd9527f7ae16517a90c44e34ced8589_img.jpg deleted file mode 100644 index b7a22be3bbf4634a01e74146584a5ce6c7cb38ea..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8bd9527f7ae16517a90c44e34ced8589_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8becef26f03c7a4b80768cf8100e0951_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8becef26f03c7a4b80768cf8100e0951_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8becef26f03c7a4b80768cf8100e0951_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8cf3db894a4e83dbac8b094528b24430_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8cf3db894a4e83dbac8b094528b24430_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8cf3db894a4e83dbac8b094528b24430_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8d129c93d18909f0643766f372e9ebf6_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8d7444ed03f97cc793846fdac8e2ed3a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8d7444ed03f97cc793846fdac8e2ed3a_img.jpg deleted file mode 100644 index 6b80c5bd1b18efa36cb69f2b92ec86c72c5e2bf9..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8d7444ed03f97cc793846fdac8e2ed3a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:596eab3070b53b6510a8cc40fe87d60475e1937a1a867e4d2d25314a9370732c -size 26332 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index f9941a813acc847f22c58f84e923f1ab14ef488e..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ddc1179492f370a27ad892748b76b6a8cd235792f56cf7fc4607018ed82319fe -size 4541 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8e0160fd55391f6f2bbdef38ceb6f823_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/8fbe9e67b51710384633b6407d60420d_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/901b345e560dfa29a2c7967f95bd54bb_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/901b345e560dfa29a2c7967f95bd54bb_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/901b345e560dfa29a2c7967f95bd54bb_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/909726977de6efd2d4df015198a2907b_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/909726977de6efd2d4df015198a2907b_img.jpg deleted file mode 100644 index b5961ff77f6229728681b6cb9f4646d077a88e65..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/909726977de6efd2d4df015198a2907b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ef14bbf763fa867dea45bcdddac4a7b2687bc24b76faabeedac22c16b1ef6148 -size 162715 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/90da64796f3fd458293c318340438e70_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/90da64796f3fd458293c318340438e70_img.jpg deleted file mode 100644 index 4000e2ead325150a16f373ca79bc3e982de0e0ca..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/90da64796f3fd458293c318340438e70_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d2c11b61ca2c78d75deb80440b4f8e7b1fff7bf067d3d84734e95b231684f1e3 -size 201083 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9156549264d36ead617a1dec7987f970_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9159d999b6514420a64eae80e52f1fd5_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/92e0feed183e6643329e6c9d933b50f1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/92e0feed183e6643329e6c9d933b50f1_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/92e0feed183e6643329e6c9d933b50f1_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/92eab1c7ce3162be3f7dabe7a3035249_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/933f4267f9d2b0ece044e7649be53447_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/933f4267f9d2b0ece044e7649be53447_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/933f4267f9d2b0ece044e7649be53447_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/93c9262c68d25c26b8cf8cd547554d9f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/93c9262c68d25c26b8cf8cd547554d9f_img.jpg deleted file mode 100644 index 5a478dd3f097ac08cbb3ea5122dd5ec35b60c114..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/93c9262c68d25c26b8cf8cd547554d9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:413b04a2b84cff089d57c9ab64b3072e855f301d81efcca0b072ce86b5f852e6 -size 219381 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/94563c795d36d598e53b9e5b4c95934c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/94563c795d36d598e53b9e5b4c95934c_img.jpg deleted file mode 100644 index c5ad53102799e9874ab02e0e44f7070fb9bae10b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/94563c795d36d598e53b9e5b4c95934c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:692407cf19eee706339f3d3a5576856819e30761a6e63271d15815827a307d10 -size 230736 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/94b678292f1b426e0d16117bb08bfba5_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/94b678292f1b426e0d16117bb08bfba5_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/94b678292f1b426e0d16117bb08bfba5_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/964fc0fd54c825b85166fb5a00aa716d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/964fc0fd54c825b85166fb5a00aa716d_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/964fc0fd54c825b85166fb5a00aa716d_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg deleted file mode 100644 index 2d51a4e23db6f1017e35a922429fca516d60f0c1..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:65e3cda1fa0e627fe775b1f863f4ba28c2a91ab60cb3b25104c35ce434502e39 -size 4500 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/970a901d8e537da4b6ff719d8931912f_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/970df246bd8b45f590e294d25c1bb60a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/970df246bd8b45f590e294d25c1bb60a_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/970df246bd8b45f590e294d25c1bb60a_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9874e3ac6f14360133f8e1674f79824f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9874e3ac6f14360133f8e1674f79824f_img.jpg deleted file mode 100644 index da0b13f77c8d6f7bab6ff541766027c6ddfd77a4..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9874e3ac6f14360133f8e1674f79824f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bbacf3b3594a1c6c581831a4896fef767220cd2a3afae7e5fd37795e8926257a -size 71033 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/98d7c3a3783b091ac41fd87427f1c8e1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/98d7c3a3783b091ac41fd87427f1c8e1_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/98d7c3a3783b091ac41fd87427f1c8e1_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/990afa9d07fb81cf8760867cb4247a79_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg deleted file mode 100644 index c29201d0030fdecc62b33137d8230a2ddd5a36a3..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1bf1eebb35af4b3e59eda8ec62436ea4f24c245995dbce276c9f29a2ef5e9569 -size 4544 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9b3e75266694bdf164036baf1bb25422_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9b3e75266694bdf164036baf1bb25422_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9b3e75266694bdf164036baf1bb25422_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9b5bae50a8a287c353f79cf9b43c8a4a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9b5bae50a8a287c353f79cf9b43c8a4a_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9b5bae50a8a287c353f79cf9b43c8a4a_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9ba81901bf408ed950fce012b4890b1d_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9bf98e5234e80aa178c89e99397928bf_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9bf98e5234e80aa178c89e99397928bf_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9bf98e5234e80aa178c89e99397928bf_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9c34076a317aa1ad4225725b4b578f9f_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg deleted file mode 100644 index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9c7046c19fb32a2d21ac26f5e90a7098_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.Use-Cases-Detailed-Specification-R005-v19.00/images/9cf678d634932a43b7f6582878972a5d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9cf678d634932a43b7f6582878972a5d_img.jpg deleted file mode 100644 index 54bd9c256bd59bf788e7498843e6328a7eada635..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9cf678d634932a43b7f6582878972a5d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f680ab32ef4f37d8aa81b1691d35184dd3e46d7bb36a794f869af86c028ac8fe -size 51225 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9d81a26facbcf05a73cb7c027e66c1c8_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9d81a26facbcf05a73cb7c027e66c1c8_img.jpg deleted file mode 100644 index f791e9c5fa2d8cc636a5069202539bf32028a532..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9d81a26facbcf05a73cb7c027e66c1c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e29cc072638e489c5aaab926b67963635bf8b6d122ab670fd03e6c7513a57fbc -size 27062 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9e4bce3d0ef8a18588aa58fd3db1cbe3_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9e4bce3d0ef8a18588aa58fd3db1cbe3_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9e4bce3d0ef8a18588aa58fd3db1cbe3_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg deleted file mode 100644 index 2d51a4e23db6f1017e35a922429fca516d60f0c1..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:65e3cda1fa0e627fe775b1f863f4ba28c2a91ab60cb3b25104c35ce434502e39 -size 4500 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9edb9da00a36a0e140e99e072096ee53_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9edb9da00a36a0e140e99e072096ee53_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/9edb9da00a36a0e140e99e072096ee53_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a0e8fe7862a6d7341faf5dac275277cc_img.jpg deleted file mode 100644 index ef8e9abd52d20ad846eab58268dfe2ad085152b5..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a0e8fe7862a6d7341faf5dac275277cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:98972692b656912a5e0a9cdd6c7514807b204c98a8056b4e6feacafcf70f97ce -size 180521 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a179c59b95e3e871a830494d80dc7ec5_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a179c59b95e3e871a830494d80dc7ec5_img.jpg deleted file mode 100644 index 2bf11cd9ff45a54a78f4ba19ef54287b6960793b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a179c59b95e3e871a830494d80dc7ec5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:be9f3fe20a0a07d24dbd0dfe26962ded07ec85f9097a9e7fa08473a4c272fcd8 -size 145436 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a28ab03366399b5e0a61445bc57e3724_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg deleted file mode 100644 index 671085354705cced783627c4002fb68a8761eea8..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:34510de37113edf5ecd7b609e1b9913a50ce23466055d436e0f3d1840567e86d -size 4526 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a4a23a6cfd603aea55a02bae13456e8e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a4a23a6cfd603aea55a02bae13456e8e_img.jpg deleted file mode 100644 index d89457bf6cba9bc52941c476faa25ede4772a698..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a4a23a6cfd603aea55a02bae13456e8e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bd2a80cc566c3b41921f6a5d83644ec5d7531b41f2ea48eafa553e55698abe43 -size 151547 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a56d6272a0cbbd2cf3f1ecbf1d2f9732_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a56d6272a0cbbd2cf3f1ecbf1d2f9732_img.jpg deleted file mode 100644 index bf0ceef024be6aff7ac7f8878f75bb551bb13230..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a56d6272a0cbbd2cf3f1ecbf1d2f9732_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d82d704f9498582f962a89b21711213e1a5ca985ee31a16ceb1d7bc0ddb80d4b -size 56034 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a5b5f7018c1568c86f11e01fb258093e_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a5f09d21af8c3e909361c622a501c7f2_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a5f09d21af8c3e909361c622a501c7f2_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a5f09d21af8c3e909361c622a501c7f2_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 571bc5618e7030e532b0944daa152a663439850f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57412e51da277a08af65bb44adea03223ad684f4dc8f6404914421b553365a40 -size 4507 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a7fcb275d0eed586509a47f4f86a9725_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a82aef1d2f3f1a527328950e9db947ee_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a93f84544e1dc2029d8b41292b8b5c03_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a93f84544e1dc2029d8b41292b8b5c03_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a93f84544e1dc2029d8b41292b8b5c03_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a9be8b5aa78ae267adfc1152523ec42d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a9be8b5aa78ae267adfc1152523ec42d_img.jpg deleted file mode 100644 index 4d19f68b0f14ca5c4624d387346b192683b0c84b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a9be8b5aa78ae267adfc1152523ec42d_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/a9f8bc87c084c4c84bae1128815c277c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/aa05feb33e250a75136ea52816d3c19a_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/aa5879e72c990f924e434bf9208b0094_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/aa5879e72c990f924e434bf9208b0094_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/aa5879e72c990f924e434bf9208b0094_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ab56946aacb4682bb58d2c3e64a9c59e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ab56946aacb4682bb58d2c3e64a9c59e_img.jpg deleted file mode 100644 index b7a22be3bbf4634a01e74146584a5ce6c7cb38ea..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ab56946aacb4682bb58d2c3e64a9c59e_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/abdd3f96a1e296c46300f2a326213dc0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/abdd3f96a1e296c46300f2a326213dc0_img.jpg deleted file mode 100644 index f8909aa1a287adb243bd5b0d75351eee49e9ac41..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/abdd3f96a1e296c46300f2a326213dc0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8dfe84e14884944b67dddc051c94eca17be70a19754c16056719c8e4306c6e0c -size 4541 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ac1c0fb704fa8fc69e7934267bc074d4_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ac1c0fb704fa8fc69e7934267bc074d4_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ac1c0fb704fa8fc69e7934267bc074d4_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/acbfa72d71d68d0c0cfa9a65623a2dc1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/acbfa72d71d68d0c0cfa9a65623a2dc1_img.jpg deleted file mode 100644 index ff18e6207c6f863b0eedbc85ea992e770977498f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/acbfa72d71d68d0c0cfa9a65623a2dc1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:af21d42845afe2c4a5c911fda30dda3829d2231558bac0dba63e0240d7f0c1b7 -size 202976 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/acfb2707966cd2618f2dc86b1a02702c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/aef4390a4629604196222b9ed006a786_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/aef4390a4629604196222b9ed006a786_img.jpg deleted file mode 100644 index 4d19f68b0f14ca5c4624d387346b192683b0c84b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/aef4390a4629604196222b9ed006a786_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b1e7bb95fa1587d870de03df02477df4_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b1e7bb95fa1587d870de03df02477df4_img.jpg deleted file mode 100644 index 09194d7c45534474cb247ec428ffbad2fb0e5ade..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b1e7bb95fa1587d870de03df02477df4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:32929c4e89b37ab2e819d1b484cc3138f5bac6c9c9827b21728adff5c0c4ee6b -size 37692 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b1fe142ff4f5589424237da7b11b41b6_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b1fe142ff4f5589424237da7b11b41b6_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b1fe142ff4f5589424237da7b11b41b6_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b324224acc41e653a93d145e61f98d8c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b324224acc41e653a93d145e61f98d8c_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b324224acc41e653a93d145e61f98d8c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b4c825454b7a89b4d7744e4f45521174_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b4c825454b7a89b4d7744e4f45521174_img.jpg deleted file mode 100644 index 573624a656ece33c3e73639ee969ab8037647a1b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b4c825454b7a89b4d7744e4f45521174_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:977bff1dadd6c12190dfaa0cb6cfefb3a7ea5189f51f561693fc90d6e774407f -size 31770 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b62e6e3b1cbec5de7e750dc0d46bcc79_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b62e6e3b1cbec5de7e750dc0d46bcc79_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b62e6e3b1cbec5de7e750dc0d46bcc79_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b6cafcdfab7ca53f640ddc2d2bae5261_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b6cafcdfab7ca53f640ddc2d2bae5261_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b6cafcdfab7ca53f640ddc2d2bae5261_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b6f547443a63be9de3a9aedf66f517b2_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b6f547443a63be9de3a9aedf66f517b2_img.jpg deleted file mode 100644 index 294d8774d2fb3b0168e3014fef0752aa786b3caf..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b6f547443a63be9de3a9aedf66f517b2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c991f31a7e20ccb8f6b5fe71e0a9325ac5c9364b08f0faf1a1a278fe23632de5 -size 99155 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b7c458c8f40fa7621871a6777ae65dbb_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b7c458c8f40fa7621871a6777ae65dbb_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b7c458c8f40fa7621871a6777ae65dbb_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b7deb15a64425aa7a86d391b2f4c848f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b7deb15a64425aa7a86d391b2f4c848f_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b7deb15a64425aa7a86d391b2f4c848f_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b7e8758ea655fc07d3aadaf2d8408d6e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b7e8758ea655fc07d3aadaf2d8408d6e_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b7e8758ea655fc07d3aadaf2d8408d6e_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/b9335fb94d07a154a00c3c63aaa36096_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg deleted file mode 100644 index 040eef753e4c8e5b728b0fb275e87ee4d3bb5265..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:23715c5578c61dd36da61194e23cc133037817bc5a8341570add5502a92664e5 -size 33047 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bb8abc0cc19db87acc1c3d7321599690_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bb9f586190c7197099d25db7df9050af_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bb9f586190c7197099d25db7df9050af_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bb9f586190c7197099d25db7df9050af_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bc0074c9be2d587e0b85224d9cb083ec_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bc4568cde39ed422b1f3231304177da0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bc4568cde39ed422b1f3231304177da0_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bc4568cde39ed422b1f3231304177da0_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bcae27bc6aeb49b97b6d51dce8d5c1af_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bcae27bc6aeb49b97b6d51dce8d5c1af_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bcae27bc6aeb49b97b6d51dce8d5c1af_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bcb0b443fcfea25dcb7005487af9200d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bcb0b443fcfea25dcb7005487af9200d_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bcb0b443fcfea25dcb7005487af9200d_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bd74854ea023b9c189707fa35cdd37ba_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/be8d4d130f4e1f103926de61c4bfc23c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bec099e513efaa5246b7005bfccbd8f6_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bec099e513efaa5246b7005bfccbd8f6_img.jpg deleted file mode 100644 index 2d51a4e23db6f1017e35a922429fca516d60f0c1..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bec099e513efaa5246b7005bfccbd8f6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:65e3cda1fa0e627fe775b1f863f4ba28c2a91ab60cb3b25104c35ce434502e39 -size 4500 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bfcea196796f3bc23aeb4499b396cab1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bfcea196796f3bc23aeb4499b396cab1_img.jpg deleted file mode 100644 index 0f4f7f7af0760cad7c69244fc77e2eb6a81786f6..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/bfcea196796f3bc23aeb4499b396cab1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9dfe11756d33a6d126eaf7a71a8174a631497582e866526c0f0e1e997e160721 -size 4465 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c05763eff20551449de1eac378fed769_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c05763eff20551449de1eac378fed769_img.jpg deleted file mode 100644 index 7a5bf40ad80d87d544677948a41ec1f1dbbab1e7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c05763eff20551449de1eac378fed769_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:545c93bb488f6502963afa2d9b60cfe8081b18e3f964c6ee7e50938400cb8807 -size 137032 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c05d92337f078aa1683a299f3c8b2d51_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c05d92337f078aa1683a299f3c8b2d51_img.jpg deleted file mode 100644 index b615519a4d2d1369d2c7fecc806b69f6dc90be44..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c05d92337f078aa1683a299f3c8b2d51_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f9c9e6c413d304bf698761d4093349886eebfe18569fa98c6fff4b22817185e6 -size 150004 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c075f11b8ee283222cbed999bc5a392c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c075f11b8ee283222cbed999bc5a392c_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c075f11b8ee283222cbed999bc5a392c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c0912cb53f8cc1be7ad8d288f5cb0fd0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c0912cb53f8cc1be7ad8d288f5cb0fd0_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c0912cb53f8cc1be7ad8d288f5cb0fd0_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c18b9d7d4dc149266c9bf688a50497a5_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c18b9d7d4dc149266c9bf688a50497a5_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c18b9d7d4dc149266c9bf688a50497a5_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c2ce94f28833f80f049837c2281aa2ba_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c2ce94f28833f80f049837c2281aa2ba_img.jpg deleted file mode 100644 index 039fa375e85b153c634dd642010eccca0f15ab7b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c2ce94f28833f80f049837c2281aa2ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:696e47e56e68a5a714c280258b9cf8621d8de12bc41335ad15149e604fbfc823 -size 253145 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c2ff6339c62f961f2abd954e987c0082_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c2ff6339c62f961f2abd954e987c0082_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c2ff6339c62f961f2abd954e987c0082_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c3254408eadbf152632a8faf16310722_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c3254408eadbf152632a8faf16310722_img.jpg deleted file mode 100644 index 99f5ad1820c9b741824cab679a861f80b042ed43..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c3254408eadbf152632a8faf16310722_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:42fc3aefa71b1b5057d9d285234182c30338ab5928139a2430de4a295bc12adb -size 178115 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 6612f9450ea5be62816aa85d35bd3da2b8a92d8d..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6e8b0cc383947a7679f11ff80d617ca5ec6b2da5282678485bf03cc5a8f6f68 -size 4508 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c41b4b0e4f4258e3c69ede6717f6dd33_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c41b4b0e4f4258e3c69ede6717f6dd33_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c41b4b0e4f4258e3c69ede6717f6dd33_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c4315e81a5a818379fcf31519a9c2cbe_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c521036a3eb59673388f5e034f4e6c9f_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c5eb42ed730ecb12621fc63444830d4b_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c5eb42ed730ecb12621fc63444830d4b_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c5eb42ed730ecb12621fc63444830d4b_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c6a96f95e328ae9493edffdae3d3cb28_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c6a96f95e328ae9493edffdae3d3cb28_img.jpg deleted file mode 100644 index 4356d322f9b152e03154cf5d865bc3690ee4fbe6..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c6a96f95e328ae9493edffdae3d3cb28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ccce59778e52c1a4b0abeea52d82bb60b6caede011625af9e1141dd869555711 -size 259973 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c6fd5cb542ee6c63f2acd62896ffcc35_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c6fd5cb542ee6c63f2acd62896ffcc35_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c6fd5cb542ee6c63f2acd62896ffcc35_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c6ffc947df5e0a0aee6304d52999ee3b_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c6ffc947df5e0a0aee6304d52999ee3b_img.jpg deleted file mode 100644 index 4d19f68b0f14ca5c4624d387346b192683b0c84b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c6ffc947df5e0a0aee6304d52999ee3b_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c76f518c4d95210969837b001e52d73b_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c76f518c4d95210969837b001e52d73b_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c76f518c4d95210969837b001e52d73b_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c95ab75ce8f67ea4200944468d7aea30_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c95ab75ce8f67ea4200944468d7aea30_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c95ab75ce8f67ea4200944468d7aea30_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c964194b41a0636cf95ab198c9196bcd_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c9b9d380332d98e5579876adfa04eb0f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c9b9d380332d98e5579876adfa04eb0f_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c9b9d380332d98e5579876adfa04eb0f_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c9e3572a1d0a3fd946db179079f95fcb_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c9e3572a1d0a3fd946db179079f95fcb_img.jpg deleted file mode 100644 index 63f3c54b6cfd6ac6e421e9e808a394e615c9b4bb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/c9e3572a1d0a3fd946db179079f95fcb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ae6907767ded8541864e2bd336157e44f30ef0634073b16b639a743227b65c24 -size 228344 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/cb01dfc2db37c44f7ff39b67b5f9d3da_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/cb01dfc2db37c44f7ff39b67b5f9d3da_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/cb01dfc2db37c44f7ff39b67b5f9d3da_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/cd9d31fecf784261aecb1220c3fe10a5_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/cd9d31fecf784261aecb1220c3fe10a5_img.jpg deleted file mode 100644 index c29201d0030fdecc62b33137d8230a2ddd5a36a3..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/cd9d31fecf784261aecb1220c3fe10a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1bf1eebb35af4b3e59eda8ec62436ea4f24c245995dbce276c9f29a2ef5e9569 -size 4544 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ce68ff30159c3788e28d166216807520_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ce68ff30159c3788e28d166216807520_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ce68ff30159c3788e28d166216807520_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/cf08e441bafa27592ca7f62e33866b53_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/cf08e441bafa27592ca7f62e33866b53_img.jpg deleted file mode 100644 index 4d19f68b0f14ca5c4624d387346b192683b0c84b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/cf08e441bafa27592ca7f62e33866b53_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/cf8309144b64cc604254b140a5986dc0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/cf8309144b64cc604254b140a5986dc0_img.jpg deleted file mode 100644 index 92d27ee55b83f9ccec60a37fcf6a95e199d64d6c..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/cf8309144b64cc604254b140a5986dc0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2312360e34fc4a340e90f11be0be455145a1ef170498991548901caf35196790 -size 4522 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d175930b7519b8f2f801b636dcce54c8_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d175930b7519b8f2f801b636dcce54c8_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d175930b7519b8f2f801b636dcce54c8_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d1c239cc875fea808eda1d61ca630fac_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d1c239cc875fea808eda1d61ca630fac_img.jpg deleted file mode 100644 index 92d27ee55b83f9ccec60a37fcf6a95e199d64d6c..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d1c239cc875fea808eda1d61ca630fac_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2312360e34fc4a340e90f11be0be455145a1ef170498991548901caf35196790 -size 4522 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d1ec9820fe8d23d83e066389a9cd7338_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d2c29dfabebacb6f853683a6c3759320_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d35a80e3faed208324083399568c7461_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d35a80e3faed208324083399568c7461_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d35a80e3faed208324083399568c7461_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d379c2e6799a45841ba1304f8e6d374d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d379c2e6799a45841ba1304f8e6d374d_img.jpg deleted file mode 100644 index b826f6b91ef05bb9789760422c4dfcf05620f153..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d379c2e6799a45841ba1304f8e6d374d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bb14f09365f74db8157cc962f61da26f433ab8509997e23842bc6a1d6aeddc4a -size 94277 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d44f82cf884db0e1f1ffb2c18e4dd8d6_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d44f82cf884db0e1f1ffb2c18e4dd8d6_img.jpg deleted file mode 100644 index e1db740ede3607d7c1ee646a22733185dabbad2b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d44f82cf884db0e1f1ffb2c18e4dd8d6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9c5025f77e37035b90599a258964632a0249450b015b3810ade3c76580f1223b -size 39251 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg deleted file mode 100644 index 7f30bdbcb252a6e0ee7d92bf6bc3f1f854a57862..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d4a9a1e5b2d8b51e6bf1abacd2421c83_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:dfededb045429ba0ce4e73ac48ef4952b23754d06b5c95c4ba5264116b083fbf -size 61157 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d510bddda14c44163bbeee33b491a105_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d510bddda14c44163bbeee33b491a105_img.jpg deleted file mode 100644 index bf8a571d877cace85827d908c1e3aecffbe4d4b6..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d510bddda14c44163bbeee33b491a105_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ee0779b5c5c091f9947f537f94067f31c1ca50eb01e250a22889d98c00954e76 -size 182181 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d53c20c28af383ce49c214cf2603fbc3_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d53c20c28af383ce49c214cf2603fbc3_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d53c20c28af383ce49c214cf2603fbc3_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg deleted file mode 100644 index 503b61867ef7bf9b958243cf59e10aa84ff2dcbe..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3d103dd4732ec0e49dee5d24212569ddcbb2f80e8aabc43763089cfb4dfdc1c3 -size 43452 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d597715604d00e1ab3b00cc3f16e59de_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d5a832cb05eb9106e3139f2c68ba9dc4_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d5a832cb05eb9106e3139f2c68ba9dc4_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d5a832cb05eb9106e3139f2c68ba9dc4_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d74bbadcdb9933d40a743043ad865c65_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d74bbadcdb9933d40a743043ad865c65_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d74bbadcdb9933d40a743043ad865c65_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d7b324ee9d9caae532ed5e898261c278_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d7b324ee9d9caae532ed5e898261c278_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d7b324ee9d9caae532ed5e898261c278_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d7b50eca959bf7bb5bc7a1e2fda6008b_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d7b50eca959bf7bb5bc7a1e2fda6008b_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d7b50eca959bf7bb5bc7a1e2fda6008b_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d7cfea99678a163f260c6ecfba27ce8d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d7cfea99678a163f260c6ecfba27ce8d_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d7cfea99678a163f260c6ecfba27ce8d_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d809da419492e18bada207fd4e79bba1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d809da419492e18bada207fd4e79bba1_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d809da419492e18bada207fd4e79bba1_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d809dd2cb221ce06a3226cb75e31d75d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d809dd2cb221ce06a3226cb75e31d75d_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d809dd2cb221ce06a3226cb75e31d75d_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d90d939bcbf43d474efaeeaa335a635c_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.Use-Cases-Detailed-Specification-R005-v19.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d90f17b29a73eddf151f51effa8912e0_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg deleted file mode 100644 index 92d27ee55b83f9ccec60a37fcf6a95e199d64d6c..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2312360e34fc4a340e90f11be0be455145a1ef170498991548901caf35196790 -size 4522 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d98654b856f97c5210b36c88cd3dcf37_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d98654b856f97c5210b36c88cd3dcf37_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/d98654b856f97c5210b36c88cd3dcf37_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/da03733d99ab91ed54613c6799a153ba_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/da03733d99ab91ed54613c6799a153ba_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/da03733d99ab91ed54613c6799a153ba_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/db17b491805d766560e8c237b84299f1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/db17b491805d766560e8c237b84299f1_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/db17b491805d766560e8c237b84299f1_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dbe4ffa9778863279b48b56fe097cd23_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dbe4ffa9778863279b48b56fe097cd23_img.jpg deleted file mode 100644 index ed596e73567659ddf8c0b81f3eb9dc9903964567..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dbe4ffa9778863279b48b56fe097cd23_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ee3ea47b9399a242bf4a8c5b0d48133af4c051eca261730e8d6af6fe8da7c5ae -size 241397 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg deleted file mode 100644 index fbb4980c2825ea195c1526380851fe9afad6eb79..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:82f72186d8bd80269fc07870befb05ec0698a0f924d7e4323fd2f1e8b368de29 -size 92295 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg deleted file mode 100644 index d51f99e8a9871e85930cafda5378c4032ec2064e..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ca1ad0988780106e8ad71b83c9238dca07cc3cd350a294534c729e0d90c2b33c -size 64040 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dda029be056105746c70a40e80692e58_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dda029be056105746c70a40e80692e58_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/dda029be056105746c70a40e80692e58_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/de35ef8911c5beed69b407fe13b6de3c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/de35ef8911c5beed69b407fe13b6de3c_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/de35ef8911c5beed69b407fe13b6de3c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/debc37b54fe8de17b46dec2bcab04ed5_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/debc37b54fe8de17b46dec2bcab04ed5_img.jpg deleted file mode 100644 index 18a014dbc8577e3c3fef5401b33df8658f2ef10f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/debc37b54fe8de17b46dec2bcab04ed5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ee37464f3a6fb4b0234adc4d7e9112a51aac5f3e140e442c0318bf5a97a829eb -size 181847 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/df495bddeb5d8826c7571714e6db1478_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e010000311ed958dd0bc2b16f8cc23d4_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e010000311ed958dd0bc2b16f8cc23d4_img.jpg deleted file mode 100644 index 76f156b6efa64e25eb1c4350b7a8e8757a31db68..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e010000311ed958dd0bc2b16f8cc23d4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b5d3482e36ecb29644d00e9aa38675dfce2edfee9d406ce3989f0304d5cfb1a9 -size 241168 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e06de71ced5f7c5e97414f01f39d550c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e0c32e027f49e7404cffe15b93075903_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e0c32e027f49e7404cffe15b93075903_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e0c32e027f49e7404cffe15b93075903_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e151d3468319b81f042ca232c4d82e4b_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e151d3468319b81f042ca232c4d82e4b_img.jpg deleted file mode 100644 index 8bfd24b79ec6421f33c38e21e9a1e246e5c6ee20..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e151d3468319b81f042ca232c4d82e4b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6a62f935eaf11b6d10dc3a05b20953bcadc0ce88eb1872708baf7ff13a32b912 -size 131167 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg deleted file mode 100644 index c29201d0030fdecc62b33137d8230a2ddd5a36a3..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1bf1eebb35af4b3e59eda8ec62436ea4f24c245995dbce276c9f29a2ef5e9569 -size 4544 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg deleted file mode 100644 index 64431012751a9f6de6b381838951eeea46b8a057..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a6b8dff4d50a2f74dbd00941521c44cf10d1dd2ac6425bee64d9f671f37668c -size 219420 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e2bef29cdcf149c935e170586b26ae9c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e2bef29cdcf149c935e170586b26ae9c_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e2bef29cdcf149c935e170586b26ae9c_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e32e1bcf367a284cc7a4186056810d22_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e339d97a55f726bb82f15798d7eb80b7_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e354b57563dae469c00b412b2abdf765_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e354b57563dae469c00b412b2abdf765_img.jpg deleted file mode 100644 index d9f93813c825788f8f8551c26b023175abf70577..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e354b57563dae469c00b412b2abdf765_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bec8fdf32780839f049836b0c2e2b93413db04e57ea7b9a90e3424ae41508cc1 -size 63321 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e374c531ea6c45899ce8ec331e437bd1_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg deleted file mode 100644 index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_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.Use-Cases-Detailed-Specification-R005-v19.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e63b8cb7ecf440e9fa5f83769248f236_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e63b8cb7ecf440e9fa5f83769248f236_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e63b8cb7ecf440e9fa5f83769248f236_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e7b5a7456650ca93650c140cc9a7cab1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e7b5a7456650ca93650c140cc9a7cab1_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e7b5a7456650ca93650c140cc9a7cab1_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e7beed289e3bb0399e3188df934dbd85_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e7beed289e3bb0399e3188df934dbd85_img.jpg deleted file mode 100644 index 6612f9450ea5be62816aa85d35bd3da2b8a92d8d..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e7beed289e3bb0399e3188df934dbd85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6e8b0cc383947a7679f11ff80d617ca5ec6b2da5282678485bf03cc5a8f6f68 -size 4508 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg deleted file mode 100644 index 92d27ee55b83f9ccec60a37fcf6a95e199d64d6c..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2312360e34fc4a340e90f11be0be455145a1ef170498991548901caf35196790 -size 4522 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e882a6bdfd0e868314f3a26f536145a3_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e88514a46354e0a227f104f25530288e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e88514a46354e0a227f104f25530288e_img.jpg deleted file mode 100644 index f11929de567f8be51bf85ef91bd12658cb11fbe7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e88514a46354e0a227f104f25530288e_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.Use-Cases-Detailed-Specification-R005-v19.00/images/e8edb46e6932fd994c7cbef114ad743a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e8edb46e6932fd994c7cbef114ad743a_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e8edb46e6932fd994c7cbef114ad743a_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg deleted file mode 100644 index b7a22be3bbf4634a01e74146584a5ce6c7cb38ea..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e9d7df9758d9a042bb17daa9842760db_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e9f27efdab43ce5b3ecbe74f09c4cfe2_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e9f27efdab43ce5b3ecbe74f09c4cfe2_img.jpg deleted file mode 100644 index f8909aa1a287adb243bd5b0d75351eee49e9ac41..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/e9f27efdab43ce5b3ecbe74f09c4cfe2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8dfe84e14884944b67dddc051c94eca17be70a19754c16056719c8e4306c6e0c -size 4541 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/eb48ed8d7efab7455ebd9f62bb214f33_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/eb48ed8d7efab7455ebd9f62bb214f33_img.jpg deleted file mode 100644 index b7a22be3bbf4634a01e74146584a5ce6c7cb38ea..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/eb48ed8d7efab7455ebd9f62bb214f33_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ec5285869660f31441ecb3c7527fe1cc_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ec5285869660f31441ecb3c7527fe1cc_img.jpg deleted file mode 100644 index b32703b00100695cda06575c4e6a3c97a115b173..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ec5285869660f31441ecb3c7527fe1cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:42fd4669fb65256ff43f6f9c90c301b72bd9a6350efb7bfaa62e08d7c40f45f5 -size 140479 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ecc17272f7951b956169a2905f5862ea_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ecc17272f7951b956169a2905f5862ea_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ecc17272f7951b956169a2905f5862ea_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ed433287faf6ca3f88eaaf14968986d6_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ed433287faf6ca3f88eaaf14968986d6_img.jpg deleted file mode 100644 index 39ccd71c5fe9e381ee705408115fb77b20de7e58..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ed433287faf6ca3f88eaaf14968986d6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:da7c0bc8d7cc1ba1fc7403e49763a848230150be4d6eb20f3c7ccbbf743d0758 -size 183169 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ed9323bc95c2008cce304ea1ebeebe8c_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ed9323bc95c2008cce304ea1ebeebe8c_img.jpg deleted file mode 100644 index 282f2e67310d37b1ac9132df97c2fbd751d0918f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ed9323bc95c2008cce304ea1ebeebe8c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:dad0ab513eefc91e17e6ee01480cc7166bb8df340a6673c2c1b0cc5e66e2464f -size 135324 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/eda00580f1bc1ce2aa1e306b85a94dbd_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/eda00580f1bc1ce2aa1e306b85a94dbd_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/eda00580f1bc1ce2aa1e306b85a94dbd_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/edcab60b3c92e05a58f7411ce1d16288_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/edcab60b3c92e05a58f7411ce1d16288_img.jpg deleted file mode 100644 index 4d19f68b0f14ca5c4624d387346b192683b0c84b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/edcab60b3c92e05a58f7411ce1d16288_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/edf47be5955638360f03d017636599c5_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/edf47be5955638360f03d017636599c5_img.jpg deleted file mode 100644 index d7e2950696e8d1227bdafa57d2e0904c77c88e78..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/edf47be5955638360f03d017636599c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0cacd0fbc0d83b6e11796fc959bc54f9af8de38fa768bdca35726198c58ef824 -size 75003 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ee5bafe10ff1ed7c138abb928006e86d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ee5bafe10ff1ed7c138abb928006e86d_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ee5bafe10ff1ed7c138abb928006e86d_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ef484b2179ee14c86e53e9f5b3c0d848_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f0c19cb19ae7a343d5f9202936fb6073_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f0c19cb19ae7a343d5f9202936fb6073_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f0c19cb19ae7a343d5f9202936fb6073_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f19f0f73f11a36b497d3c8ef01dff1b5_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f19f0f73f11a36b497d3c8ef01dff1b5_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f19f0f73f11a36b497d3c8ef01dff1b5_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f1d870c901879a8a045ece56cc5b1980_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f1d870c901879a8a045ece56cc5b1980_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f1d870c901879a8a045ece56cc5b1980_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f250ba4162fe40d8ddfd05b74fa48895_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f3d3e0a60abdafe4358260627581113a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f3d3e0a60abdafe4358260627581113a_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f3d3e0a60abdafe4358260627581113a_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index b7a22be3bbf4634a01e74146584a5ce6c7cb38ea..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f3d768b0299c4763bc703b606391c48b_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f48cf940639a2d36749ccb71f4e3faea_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f48cf940639a2d36749ccb71f4e3faea_img.jpg deleted file mode 100644 index d9e2c6713cc2d1886f64d21f9f48eee19b6abc39..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f48cf940639a2d36749ccb71f4e3faea_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f4aaee6522d9ab40472939a4a178e5a3_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f4aaee6522d9ab40472939a4a178e5a3_img.jpg deleted file mode 100644 index 714b4b73c8f040451d99af373d68da4ce30f0f25..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f4aaee6522d9ab40472939a4a178e5a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7ffaa735ecacd94714d3ba0a5162b152da33360aaa84f573c0c5444cf5129c16 -size 279508 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f4c40d970ceccdbca2595357cd06a080_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f54a2a3dde9b823d049845884cbd166a_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f54a2a3dde9b823d049845884cbd166a_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f54a2a3dde9b823d049845884cbd166a_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f55d491cfb2497e8becc9cf1fc6be4c8_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f55d491cfb2497e8becc9cf1fc6be4c8_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f55d491cfb2497e8becc9cf1fc6be4c8_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f74adaa1840504407cd4272995426f82_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index c29201d0030fdecc62b33137d8230a2ddd5a36a3..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1bf1eebb35af4b3e59eda8ec62436ea4f24c245995dbce276c9f29a2ef5e9569 -size 4544 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f92ebf4eb3d62b7dfa401644b0b6e40d_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f92ebf4eb3d62b7dfa401644b0b6e40d_img.jpg deleted file mode 100644 index 4d19f68b0f14ca5c4624d387346b192683b0c84b..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f92ebf4eb3d62b7dfa401644b0b6e40d_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f97535cdaa4fe017f4659512f4f78028_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f97535cdaa4fe017f4659512f4f78028_img.jpg deleted file mode 100644 index 49d2c6f8906828a780b7c42df5de641c0a335ea1..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f97535cdaa4fe017f4659512f4f78028_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:05ed3252c74110fbc21a0eb6850996c6b721f90d778b5c36e3b44ef2e3782c1e -size 124036 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/f9b17af787dbdc9711539cd71df3d782_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fa054fa02ab72ff83b76d80c22078856_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fa054fa02ab72ff83b76d80c22078856_img.jpg deleted file mode 100644 index 3fd8d3e3521b9ec37ea54298fe31435d3b46ccfb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fa054fa02ab72ff83b76d80c22078856_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5258cf5d915d707b972dc253bfa3298db12b642f1cb7cc883b1a198fa38028c1 -size 116212 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fa0736695e26abf36c4ab5114e8c9c14_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fa0736695e26abf36c4ab5114e8c9c14_img.jpg deleted file mode 100644 index ec719741c2465b9de28c718ad3c300a20f949e5f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fa0736695e26abf36c4ab5114e8c9c14_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7b9bc7136dae459fb12c79925f8fa1f0b6924d383a522ac4271ad7db4ba4aca2 -size 135698 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fa9f113a14954a4741c64d911be324e9_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fa9f113a14954a4741c64d911be324e9_img.jpg deleted file mode 100644 index 6612f9450ea5be62816aa85d35bd3da2b8a92d8d..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fa9f113a14954a4741c64d911be324e9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6e8b0cc383947a7679f11ff80d617ca5ec6b2da5282678485bf03cc5a8f6f68 -size 4508 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fabe931a97ba32b2e81af497e57033f1_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fabe931a97ba32b2e81af497e57033f1_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fabe931a97ba32b2e81af497e57033f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fac227c65a311c313325216dcf59591f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fac227c65a311c313325216dcf59591f_img.jpg deleted file mode 100644 index 6612f9450ea5be62816aa85d35bd3da2b8a92d8d..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fac227c65a311c313325216dcf59591f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6e8b0cc383947a7679f11ff80d617ca5ec6b2da5282678485bf03cc5a8f6f68 -size 4508 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fbd10feb132607962f09a7f6bfb69df6_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fbd10feb132607962f09a7f6bfb69df6_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fbd10feb132607962f09a7f6bfb69df6_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fbee1b51966e04afd72119133d952535_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fbee1b51966e04afd72119133d952535_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fbee1b51966e04afd72119133d952535_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 7ba23e9ce9b362f282351061dad0907a0f90167f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e04ac2ecb554e68f7278d26838cc694f99eb38f2eddc980b0318802b52cddf87 -size 4595 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fdff3385d0aee2b2113ba512b60f194e_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fdff3385d0aee2b2113ba512b60f194e_img.jpg deleted file mode 100644 index 92d27ee55b83f9ccec60a37fcf6a95e199d64d6c..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fdff3385d0aee2b2113ba512b60f194e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2312360e34fc4a340e90f11be0be455145a1ef170498991548901caf35196790 -size 4522 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fe07d230fde7b9a0c4efa6ddb07e8595_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fe07d230fde7b9a0c4efa6ddb07e8595_img.jpg deleted file mode 100644 index e39906bd4f59b0215f6f99ebebf4ee9bd8aa2526..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fe07d230fde7b9a0c4efa6ddb07e8595_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fe77f3082a0ce5eaa1f8f74877eb10bd_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fe77f3082a0ce5eaa1f8f74877eb10bd_img.jpg deleted file mode 100644 index 14808400fab5bf2e6b0ce1f90847789d11b465eb..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fe77f3082a0ce5eaa1f8f74877eb10bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c0eac7f294bd2d760e3dd74d1a858b04a0018f54af3c20bd8c406072daf1590 -size 4548 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fec5f1bac5cf3187f7618d1adb95871f_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fec5f1bac5cf3187f7618d1adb95871f_img.jpg deleted file mode 100644 index 265408f1d130817c50a24bc2d100a81e45786ac7..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/fec5f1bac5cf3187f7618d1adb95871f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ce83340f2bd636fc41ecbd83f01c7f43c79e5a6e0fe7f973c9b3a341dac6b33 -size 4495 diff --git a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index a9995c238ac97466dce8b0c2bea3aa2bb6023e9f..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ff748955b94dcb8337283fbe12baa475_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.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ff81d88ebb5c5673a41bbcf9e41f6763_img.jpg b/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ff81d88ebb5c5673a41bbcf9e41f6763_img.jpg deleted file mode 100644 index b1d7397492383d22034bb528172d5fac25bbb445..0000000000000000000000000000000000000000 --- a/files/WG1/O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R005-v19.00/images/ff81d88ebb5c5673a41bbcf9e41f6763_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/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/doc.md b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/doc.md deleted file mode 100644 index dec79af17681e1cae13997fd034c11e423d1c8b1..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/doc.md +++ /dev/null @@ -1,1121 +0,0 @@ - - -![O-RAN ALLIANCE logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) - -The logo for the O-RAN ALLIANCE, featuring a colorful circular icon to the left of the text "O-RAN" in blue, with "ALLIANCE" in smaller blue letters underneath. - -O-RAN ALLIANCE logo - -# --- **O-RAN Work Group 10 (OAM for O-RAN)****Application Packaging General Aspects & Principles** - -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 - -| | | -|---------------------------------------------------------------------------------|----| -| List of figures..... | 4 | -| List of tables ..... | 4 | -| Foreword..... | 5 | -| Modal verbs terminology..... | 5 | -| 1 Scope ..... | 6 | -| 2 References ..... | 6 | -| 2.1 Normative references ..... | 6 | -| 2 Informative references..... | 6 | -| 3 Definition of terms, symbols and abbreviations..... | 7 | -| 3.1 Terms..... | 7 | -| 3.2 Symbols..... | 7 | -| 3.3 Abbreviations ..... | 7 | -| 4 General aspects of application packaging ..... | 8 | -| 4.1 Aspect: artifact management ..... | 8 | -| 4.1.1 Original artifacts ..... | 8 | -| 4.1.2 Artifact security ..... | 8 | -| 4.1.3 Artifact references to other artifacts..... | 8 | -| 4.1.4 Package directories ..... | 8 | -| 5 Principles of application packaging ..... | 9 | -| 5.1 Principle: data minimization..... | 9 | -| 5.1.1 Data reduction..... | 9 | -| 5.1.2 Data caching ..... | 9 | -| 5.1.3 Data replication balance point ..... | 9 | -| 6 Use cases of application packaging ..... | 9 | -| 6.1 Use case conventions..... | 9 | -| 6.1.1 Overview ..... | 9 | -| 6.1.2 Use case description..... | 9 | -| 6.1.3 Use case analysis ..... | 10 | -| 6.1.4 Use case information model relationships ..... | 10 | -| 6.1.5 Use case requirement traceability ..... | 10 | -| 6.2 Cloudified NF with NF Deployment decomposition: packaging use case ..... | 10 | -| 6.2.1 Description..... | 10 | -| 6.2.2 Analysis ..... | 11 | -| 6.2.3 Information model relationships ..... | 11 | -| 6.2.4 Requirement traceability..... | 12 | -| 6.3 Cloudified NF without NF Deployment decomposition: packaging use case ..... | 12 | -| 6.3.1 Description..... | 12 | -| 6.3.2 Analysis ..... | 12 | -| 6.3.3 Information model relationships ..... | 13 | -| 6.3.4 Requirement traceability..... | 15 | -| 6.4 PNF application: packaging use case ..... | 16 | -| 6.4.1 Description..... | 16 | -| 6.4.2 Analysis ..... | 16 | -| 6.4.3 Information model relationships ..... | 17 | -| 6.4.4 Requirement traceability..... | 17 | -| 6.5 NF management application: packaging use case ..... | 18 | -| 6.5.1 Description..... | 18 | -| 6.5.2 Analysis ..... | 18 | -| 6.5.3 Information model relationships ..... | 18 | -| 6.5.4 Requirement traceability..... | 21 | -| 6.6 rApp package use case ..... | 22 | - -- 6.6.1 Description.....22 -- 6.6.2 Analysis .....23 -- 6.6.3 Information model relationships .....23 -- 6.6.4 Requirement traceability .....23 -- 7 Requirements for Application Packaging.....23 - - 7.1 Requirement Conventions .....23 - - 7.2 Non-Functional Requirements.....24 - - 7.2.1 Requirements for all Application Packages .....24 - - 7.2.2 Requirements for Cloudified Network functions .....24 - - 7.2.2 Requirements for Physical Network Elements .....25 - - 7.2.3 Requirements for Application Management Packages .....25 - - 7.2.4 Requirements for rApp Packages.....25 -- Annex (informative): Change history/Change request (history) .....26 - -# --- List of figures - -| | | -|----------------------------------------------------------------------------------------------------------------------------------|----| -| Figure 6.3.3-1 Cloudified NF Package Relationships: monolithic Cloudified NF Package..... | 13 | -| Figure 6.3.3-2 Cloudified NF Package Relationships: dependent NF Deployment Packages with distributed management descriptor..... | 14 | -| Figure 6.3.3-3 Cloudified NF Package Relationships: dependent NF Deployment Packages and centralized management descriptor..... | 14 | -| Figure 6.3.3-4 Information Model for a Package Descriptor of a Cloudified NF Package ..... | 15 | -| Figure 6.3.3-5 Information Model for a Package Descriptor of an NF Deployment Package ..... | 15 | -| Figure 6.4.3-1 PNF Application Package Relationships ..... | 17 | -| Figure 6.4.3-2 Information Model for a PNF Application PackageDescriptor ..... | 17 | -| Figure 6.5.3.1-1 Relationship UML Color Scheme..... | 18 | -| Figure 6.5.3.1-2 Management Descriptor Relationships ..... | 19 | -| Figure 6.5.3.3.1-1 Telemetry Schema Descriptor relationships ..... | 19 | -| Figure 6.5.3.3.2-1 NRM Schema relationships ..... | 19 | -| Figure 6.5.3.3.3-1 Configuration Data relationships ..... | 20 | -| Figure 6.5.3.4-1 Accounting Descriptor Relationships ..... | 20 | -| Figure 6.5.3.6-1 Management Security Descriptor Relationships..... | 21 | - -# --- List of tables - -| | | -|------------------------------------------------------------|----| -| Table 6.2.4-1 Requirements derived from this use case..... | 12 | -| Table 6.3.4-1 Requirements derived from this use case..... | 16 | -| Table 6.6.4-1 Requirements derived from this use case..... | 23 | - -# --- Foreword - -This Technical Specification (TS) has been produced by WG10 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 general aspects, principles, use cases, information model, and requirements pertaining to the format and content of an Application Package which then allows the Network Operator to Onboard the Solution Provider's Application to the SMO through the Onboarding SMOS. - -# --- 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.WG11-O-RAN-Security-Requirements-Specification: "O-RAN Security Requirements" -- [2] O-RAN.WG10.TS.Information Model and Data Models, "O-RAN Information Model and Data Models Specification" -- [3] O-RAN.WG10.TS.O1-Interface, "O1 Interface Specification" -- [4] O-RAN WG1.OAD: "O-RAN Architecture Description". - -# 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] O-RAN WG10.OAM-Architecture: "O-RAN OAM Architecture" -- [i.3] O-RAN-WG6.ORCH-Use-Cases: "Cloudification and Orchestration Use Cases" -- [i.4] O-RAN-WG11.AppLCM-Security-TR: "Security for Application Lifecycle Management" - -# 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: - -**Application:** The software aspect of a vendor product for a Network Element [i.2], an xApp or rApp which is sold/delivered to an operator. - -**Accounting Descriptor:** An artifact which describes any license and/or usage records used to identify measured license accountability. - -**Alarm Dictionary:** An artifact which describes all alarms which can be emitted by the Application. - -**Application Artifact:** A file contained within an archive such as the Application Package. - -**Application Management Package:** The set of information provided by a Solution Provider to a Service Provider in a dedicated package containing only Management Descriptors. - -**Application Package:** The set of artifacts provided by a Solution Provider to a Service Provider representing the Application as a whole. - -**Network Element:** The definition of a Network Element (NE) is given in 3GPP TS 21.905 [i.1] clause 3.N. - -**NF Deployment:** Refer to the Cloudification and Orchestration Use Cases [i.3]. - -**Network Function:** A standardized set of functionality which is used to implement the RAN. - -**Management Descriptor:** A descriptor describing some aspects for the FCAPS management for a Network Function. - -**Onboarding:** The process of validating and ingesting an Application Package to make it available to other services within the SMO. - -**Performance Dictionary:** An artifact which describes all performance measures which can be collected by the Application and sent to a management system according to its subscription criteria. - -**Security Descriptor:** An artifact which can describe needed information for the Security Aspects of FCAPS for the Application. - -**Service Provider:** The RAN service provider often referred to as the operator. - -**Software Package:** A binary image to be downloaded to a PNF as some or all of its software build. - -**Solution Provider:** Application development entity often referred to as a vendor. - -**Telemetry Schemas:** Artifacts which describe the schema for telemetry data sent from the Application to a management system. - -## 3.2 Symbols - -Void - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations [given in [i.1] and the following] apply: - -| | | -|-----|-----------------------------| -| AAS | Active Antenna System | -| CNF | Cloudified Network Function | - -| | | -|------|------------------------------------| -| eNB | e NodeB (applies to LTE) | -| gNB | g NodeB (applies to NR) | -| JSON | JavaScript Object Notation | -| NE | Network Element | -| NF | Network Function | -| NRM | Network Resource Model | -| O-DU | O-RAN Distributed Unit | -| O-RU | O-RAN Radio Unit | -| PNF | Physical Network Function | -| SDO | Standards Development Organization | -| SMO | Service Management & Orchestration | -| YAML | Yet Another Markup Language | -| XML | eXtensible Markup Language | - -# --- 4 General aspects of application packaging - -## 4.1 Aspect: artifact management - -### 4.1.1 Original artifacts - -Artifacts are expected to be preserved in the original, as-is format, received from the vendor. This is not only crucial for artifact integrity checks but also for audit of what was received. Artifacts may be duplicated and modified by later lifecycle operations. Those modified artifacts may need to be compared to the original artifact when troubleshooting is needed. - -### 4.1.2 Artifact security - -All artifacts contained or referenced within the package shall be identified in a manifest artifact. All artifacts in the package and external references identified in the manifest are required to be checked for authenticity and integrity according to O-RAN Security Requirements Specification [1]. - -### 4.1.3 Artifact references to other artifacts - -#### 4.1.3.1 Local relative reference - -Artifacts can reference other artifacts within their content. This can be done using a relative address local to the root artifact. It is expected that the Onboarding SMOS can resolve a local relative reference to the absolute path of an onboarded artifact. - -#### 4.1.3.2 External URL reference - -Artifacts can reference another using a URL which is external to the Onboarding Package. It is expected that the Onboarding SMOS can resolve a external URL reference to the absolute path of an onboarded artifact. - -### 4.1.4 Package directories - -#### 4.1.4.1 Standardized directories - -Some directories in the Onboarding Package may be standardized, and certain types of artifacts may be required to be placed in those - -#### 4.1.4.2 Vendor extended directories - -It is expected that a vendor may further organize their data within the standardized directories. Therefore, a vendor is free to add any sub-directories they deem fit to the standardized directories. - -# --- 5 Principles of application packaging - -## 5.1 Principle: data minimization - -### 5.1.1 Data reduction - -Generally, it is not desirable to replicate data. Anytime data is replicated a source-of-truth needs to be identified and consistency of the copy comes into question. Additionally, depending on the size of the copied data the size of the overall object can be drastically increased as there will be one or more copy of that data in the entire data set. The copy may also be transformed into a different format. Such a translation may inject discrepancies or inaccuracies into the copy while also requiring consumers to have different translators for the copies. Therefore, the ideal situation is that there never is any duplication of data. - -### 5.1.2 Data caching - -There are cases where data replication adds value. If the format of the source of truth is opaque to the different consumers, then it may be advantageous to put the burden of translation on the supplier. Another scenario is one of latency, if the access to the source-of-truth takes too long for the use case then the data may be replicated as a cache. Techniques to ensure accuracy of the cache when the source-of-truth is modified are usually required. - -### 5.1.3 Data replication balance point - -Data Reduction which demands duplication elimination, and data caching which demands data replication are at odds with each other. Therefore, the balance point between them is based on the use cases which use any potential replica of the data. - -# 6 Use cases of application packaging - -## 6.1 Use case conventions - -### 6.1.1 Overview - -The present document follows the Use Cases methodology described in clauses 6.1.2, 6.1.3, 6.1.4 and 6.1.5. - -Typical use cases are comprised of actors who interact with each other passing data. Those interactions are often translated into functional requirements. In the case of application packaging the requirements are non-functional and there are no interactions. The interactions occur in the lifecycle which have data demands. Those interactions are described in the O-RAN OAM Architecture [4]. This does not mean that there are not scenarios in which analysis can be performed to identify the data requirements. Therefore, this specification has adopted the following conventions to document a scenario, or use case, in a relevant manner to drive the creation of the non-functional requirements for application packaging. The Use Cases can be merged into a composite but for the sake of requirements analysis all their combinatorial variations are not needed and therefore may not be represented. - -### 6.1.2 Use case description - -This is the first subclause (6.2.1) in the use case. It is written in natural language. It sets the context for an onboarding activity. It provides enough detail to describe the scenario, set its scope and identify how it is different to other scenarios. - -### 6.1.3 Use case analysis - -The "Analysis" is the second (6.2.2) subclause in the use case. It describes why certain information elements are required and why some are not required. Some information elements can be optional, however there is no attempt to address requirements covered by a different scenario. - -### 6.1.4 Use case information model relationships - -The Information Model Relationships is a UML Class diagram and is the third subclause (6.2.3) of a use case. It describes the information elements of the application package but does not describe any artifact in the package. - -### 6.1.5 Use case requirement traceability - -Requirements are the goal and fourth (6.2.4) subclause of a use case. The section identifies applicable non-functional requirements which are defined in clause 7.2 of this specification. The traceability is a table where each requirement can be associated with an optional comment to clarify its specific applicability to the use case - -## 6.2 Cloudified NF with NF Deployment decomposition: packaging use case - -### 6.2.1 Description - -#### 6.2.1.1 Initial package delivery - -A solution provider has implemented an O-RAN NF, e.g. an O-CU-CP, consisting of three sets of microservices. Each set contains one or multiple microservice and each set has an independent life cycle. Therefore, the solution provider has decomposed the NF to be realized with three NF Deployments. - -In addition, for the management of the NF via the O1 interface the solution provider has prepared a set of management descriptors including NF configuration modules, an alarm dictionary and a performance dictionary. - -In relation to the management descriptors, two sub-cases are considered: - -- Disaggregated management information: information in the management descriptors is broken down into parts, where each of the part is very tightly coupled with a particular NF Deployment. In other words, if the software of that particular NF Deployment changes, it is likely that the related part of the management descriptor also has to change while other parts of the management information will likely not need to. -- Centralized management information: information in the management descriptors is kept undivided in one single artifact for each of the management descriptor types – configuration, alarm dictionary, performance dictionary- e.g. because it is not tightly coupled to a particular NF Deployment. - -#### 6.2.1.2 New NF Deployment software or artifacts with new functionality - -The solution provider updates one of the sets of microservices that make up the NF in order to enhance the functionality of the NF. Therefore, it creates a new version of the corresponding NF Deployment containing new versions of software images, Helm charts and of the NF Deployment descriptor. - -In addition, in this particular case the management information is affected by the functionality enhancement introduced by the software change. This may not always be the case, i.e. changes in the software of the NF Deployments don't necessarily imply a change in the management information. If the software change affects the management information, depending on the mode used to deliver the management information, it results in a different impact: - -- With the disaggregated management information only the part of the management information related to the updated NF Deployment is affected. -- With the centralized management information, as it is not decomposed in parts, a new version of the entire management descriptor is required. - -#### 6.2.1.3 New NF Deployment software with a security patch - -The solution provider updates a software image in one of the NF Deployments in order to address a security issue. Therefore, it creates a new version of the corresponding NF Deployment containing the new versions of the software image, Helm chart and NF Deployment descriptor. - -In this case the management information is not affected by the security patch so there is no need to deliver again the management information. - -### 6.2.2 Analysis - -From the use case described in the previous clause the following types of packages are identified: - -- A Cloudified NF package -- An NF Deployment package -- A Management package - -Where the Cloudified NF package contents are: - -- A manifest listing package contents and referencing NF Deployment packages and a Management package. The latter is needed only in the case of centralized management information -- A Cloudified NF descriptor -- Signatures - -The contents of the NF Deployment package are: - -- A manifest listing package contents and URLs to external artifacts, if any -- An NF Deployment descriptor (e.g. an ASD) -- Software images -- Cloud native descriptor files, e.g. Helm charts -- Management descriptors (configuration modules, alarm dictionary, performance dictionary). These are only needed in the case of disaggregated management information. -- Signatures - -The contents of the Management package (only needed in the case of centralized management information) are: - -- A manifest listing package contents -- Management descriptors (configuration modules, alarm dictionary, performance dictionary) -- Signatures - -### 6.2.3 Information model relationships - -The information model relationships for the Cloudified NF package, the NF Deployment package and the Management package is shown in 6.3.3. - -### 6.2.4 Requirement traceability - -Table 6.2.4-1 lists the requirements in clause 7.2.6 that are derived from this use case. - -**Table 6.2.4-1 Requirements derived from this use case** - -| Requirement | Comment | -|----------------|-------------------------------------------------------------------------------------------------------------| -| REQ-CNF-CON-01 | | -| REQ-NFD-CON-01 | | -| REQ-CNF-CON-02 | Requirement applicable for the manifest both in the Cloudified NF package and in the NF Deployment package. | -| REQ-CNF-CON-03 | | -| REQ-NFD-CON-02 | | -| REQ-NFD-CON-03 | | -| REQ-NFD-CON-04 | | -| REQ-CNF-CON-04 | | -| REQ-CNF-CON-05 | | -| REQ-CNF-CON-06 | | -| | | -| | | - -## 6.3 Cloudified NF without NF Deployment decomposition: packaging use case - -### 6.3.1 Description - -#### 6.3.1.1 Initial package delivery - -A solution provider has implemented a logical NF which consists of an aggregation of O-RAN NFs, for example a gNodeB which includes the functionality of a O-CU-CP, an O-CU-UP and an O-DU. In this case the whole NF is realized with a single NF Deployment. - -In addition, for the management of the NF via the O1 interface the solution provider has prepared a set of management descriptors including NF configuration modules, an alarm dictionary and a performance dictionary. - -#### 6.3.1.2 New Cloudified NF software - -The solution provider needs to update the software. Since it is not divided into multiple NF Deployments, the complete software, including software images and Helm charts, and deployment descriptor, has to be delivered for the upgrade. - -In this particular case, the management information is not affected by the software change. - -### 6.3.2 Analysis - -From the use case describe in the previous clause the following packages are identified: - -- A Cloudified NF package -- A Management package - -Where the Cloudified NF package contents are: - -- A manifest listing package contents and URLs to external artifacts, if any, and referencing a Management package. -- A Cloudified NF descriptor -- An NF Deployment descriptor (e.g. an ASD) -- Software images -- Cloud native descriptor files, e.g. Helm charts -- Signatures - -The contents of the Management package are: - -- A manifest listing package contents -- Management descriptors -- Signatures - -### 6.3.3 Information model relationships - -![UML Class Diagram showing relationships for CloudifiedNFPackage. The central class is CloudifiedNFPackage. It has associations with: ManagementDescriptor_ (0..N), ManagementPackage (0..1), PackageDescriptor (1), CloudifiedNFDescriptor (1), NfDeploymentDescriptor (1), CloudNativeDescriptorFile (1..N), SoftwareImage (0..N), NfDeploymentPackageDescriptor (1), NonOranArtifact (0..N), and SoftwareImageDescriptor (0..N).](4636adff5682a064f0ae5f13a1d464a6_img.jpg) - -``` - -classDiagram - class ManagementDescriptor_ - class ManagementPackage - class PackageDescriptor - class CloudifiedNFPackage - class CloudifiedNFDescriptor - class NfDeploymentDescriptor - class CloudNativeDescriptorFile - class SoftwareImage - class NfDeploymentPackageDescriptor - class NonOranArtifact - class SoftwareImageDescriptor - - CloudifiedNFPackage "1" -- "0..N" ManagementDescriptor_ - CloudifiedNFPackage "1" -- "0..1" ManagementPackage - CloudifiedNFPackage "1" -- "1" PackageDescriptor - CloudifiedNFPackage "1" -- "1" CloudifiedNFDescriptor - CloudifiedNFPackage "1" -- "1" NfDeploymentDescriptor - CloudifiedNFPackage "1" -- "1..N" CloudNativeDescriptorFile - CloudifiedNFPackage "1" -- "0..N" SoftwareImage - CloudifiedNFPackage "1" -- "1" NfDeploymentPackageDescriptor - CloudifiedNFPackage "1" -- "0..N" NonOranArtifact - CloudifiedNFPackage "1" -- "0..N" SoftwareImageDescriptor - -``` - -UML Class Diagram showing relationships for CloudifiedNFPackage. The central class is CloudifiedNFPackage. It has associations with: ManagementDescriptor\_ (0..N), ManagementPackage (0..1), PackageDescriptor (1), CloudifiedNFDescriptor (1), NfDeploymentDescriptor (1), CloudNativeDescriptorFile (1..N), SoftwareImage (0..N), NfDeploymentPackageDescriptor (1), NonOranArtifact (0..N), and SoftwareImageDescriptor (0..N). - -**Figure 6.3.3-1 Cloudified NF Package Relationships: monolithic Cloudified NF Package** - -Figure 6.3.3-1 shows the composition and relationships of a Cloudified NF Package for the case where all software is delivered as part of the Cloudified NF Package, without any dependent NF Deployment Packages. This case only supports a Cloudified NF with one single NF Deployment. - -The Cloudified NF Package contains a Package Descriptor, i.e. a manifest, and a Cloudified NF Descriptor. It may contain non O-RAN specified artifacts, e.g. a ReadMe file. - -The Cloudified NF Package in this case contains also the artifacts of one NF Deployment (one NF Deployment Package Descriptor, one NF Deployment Descriptor, one or more Cloud Native Descriptor Files, and zero, one or multiple Software Images). The NF Deployment Package Descriptor (the manifest of the NF Deployment) is required as the consumers of the Onboarding SMOS need to know the list of artifacts that make up the NF Deployment. - -If the Cloudified NF Package contains Software Images it also contains one Software Image Descriptor for each Software Image. Whether the Software Image Descriptor is realized as a separate artifact or its contents are part of the Package Descriptor (the manifest) is not determined in the information model. - -The Cloudified NF Package can contain Management Descriptors or refer to a dependent Management Package. - -![UML Class Diagram showing Cloudified NF Package Relationships with distributed management descriptor. The diagram shows a CloudifiedNFPackage containing a PackageDescriptor, a CloudifiedNFDescriptor, and multiple NfDeploymentPackages. Each NfDeploymentPackage contains an NfDeploymentPackageDescriptor, an NfDeploymentDescriptor, one or more CloudNativeDescriptorFiles, zero or more SoftwareImages, zero or more SoftwareImageDescriptors, and zero or more NonOranArtifacts. Some NfDeploymentPackages also contain a ManagementDescriptor_.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) - -``` - -classDiagram - class PackageDescriptor - class CloudifiedNFPackage - class CloudifiedNFDescriptor - class NfDeploymentPackage - class NfDeploymentPackageDescriptor - class NfDeploymentDescriptor - class CloudNativeDescriptorFile - class SoftwareImage - class SoftwareImageDescriptor - class NonOranArtifact - class ManagementDescriptor_ - - PackageDescriptor "1" -- "1" CloudifiedNFPackage - CloudifiedNFPackage "1" -- "1" CloudifiedNFDescriptor - CloudifiedNFPackage "1" -- "0..N" NfDeploymentPackage - NfDeploymentPackage "1" -- "1" NfDeploymentPackageDescriptor - NfDeploymentPackage "1" -- "1" NfDeploymentDescriptor - NfDeploymentPackage "1" -- "1..N" CloudNativeDescriptorFile - NfDeploymentPackage "1" -- "0..N" SoftwareImage - NfDeploymentPackage "1" -- "0..N" SoftwareImageDescriptor - NfDeploymentPackage "1" -- "0..N" NonOranArtifact - NfDeploymentPackage "1" -- "0..N" ManagementDescriptor_ - -``` - -UML Class Diagram showing Cloudified NF Package Relationships with distributed management descriptor. The diagram shows a CloudifiedNFPackage containing a PackageDescriptor, a CloudifiedNFDescriptor, and multiple NfDeploymentPackages. Each NfDeploymentPackage contains an NfDeploymentPackageDescriptor, an NfDeploymentDescriptor, one or more CloudNativeDescriptorFiles, zero or more SoftwareImages, zero or more SoftwareImageDescriptors, and zero or more NonOranArtifacts. Some NfDeploymentPackages also contain a ManagementDescriptor\_. - -**Figure 6.3.3-2 Cloudified NF Package Relationships: dependent NF Deployment Packages with distributed management descriptor** - -Figure 6.3.3-2 shows the composition and relationships of a Cloudified NF Package and NF Deployment Packages for the case where software delivery is distributed across one or multiple NF Deployment Packages and the management descriptors are distributed across the NF Deployment Packages. This case supports a Cloudified NF with one or multiple NF Deployments. - -The Cloudified NF Package contains a Package Descriptor, i.e. a manifest, and a Cloudified NF Descriptor. It may contain non O-RAN specified artifacts, e.g. a README file. - -The Cloudified NF Package in this case refers to one or multiple NF Deployment packages. An NF Deployment Package contains an NF Deployment Package Descriptor (a manifest), an NF Deployment Descriptor, one or more Cloud Native Descriptor Files, and zero, one or multiple Software Images. It may also contain non O-RAN specified artifacts. - -If the NF Deployment Package contains Software Images it also contains one Software Image Descriptor for each Software Image. Whether the Software Image Descriptor is realized as a separate artifact or its contents are part of the NF Deployment Package Descriptor (the manifest) is not determined in the information model. - -Some or all the NF Deployment Packages contain in this case Management Descriptors. - -![UML Class Diagram showing Cloudified NF Package Relationships with centralized management descriptor. This diagram is similar to Figure 6.3.3-2 but instead of ManagementDescriptor_ being inside NfDeploymentPackage, it is shown as a separate ManagementPackage that is associated with the CloudifiedNFPackage. The CloudifiedNFPackage has a 1-to-0..N relationship with ManagementDescriptor_ and a 1-to-0..1 relationship with ManagementPackage.](c036e2540a94b31357ceb0002f0cacab_img.jpg) - -``` - -classDiagram - class PackageDescriptor - class CloudifiedNFPackage - class CloudifiedNFDescriptor - class NfDeploymentPackage - class NfDeploymentPackageDescriptor - class NfDeploymentDescriptor - class CloudNativeDescriptorFile - class SoftwareImage - class SoftwareImageDescriptor - class NonOranArtifact - class ManagementDescriptor_ - class ManagementPackage - - PackageDescriptor "1" -- "1" CloudifiedNFPackage - CloudifiedNFPackage "1" -- "1" CloudifiedNFDescriptor - CloudifiedNFPackage "1" -- "0..N" NfDeploymentPackage - CloudifiedNFPackage "1" -- "0..N" ManagementDescriptor_ - CloudifiedNFPackage "1" -- "0..1" ManagementPackage - NfDeploymentPackage "1" -- "1" NfDeploymentPackageDescriptor - NfDeploymentPackage "1" -- "1" NfDeploymentDescriptor - NfDeploymentPackage "1" -- "1..N" CloudNativeDescriptorFile - NfDeploymentPackage "1" -- "0..N" SoftwareImage - NfDeploymentPackage "1" -- "0..N" SoftwareImageDescriptor - NfDeploymentPackage "1" -- "0..N" NonOranArtifact - -``` - -UML Class Diagram showing Cloudified NF Package Relationships with centralized management descriptor. This diagram is similar to Figure 6.3.3-2 but instead of ManagementDescriptor\_ being inside NfDeploymentPackage, it is shown as a separate ManagementPackage that is associated with the CloudifiedNFPackage. The CloudifiedNFPackage has a 1-to-0..N relationship with ManagementDescriptor\_ and a 1-to-0..1 relationship with ManagementPackage. - -**Figure 6.3.3-3 Cloudified NF Package Relationships: dependent NF Deployment Packages and centralized management descriptor** - -Figure 6.3.3-3 shows the composition and relationships of a Cloudified NF Package and NF Deployment Packages for the case where software delivery is distributed across one or more NF Deployment Packages and the management descriptors are centralized, either in the Cloudified NF Package or in a separate Management Package. This case supports a Cloudified NF with one or multiple NF Deployments. - -The Cloudified NF Package contains a Package Descriptor, i.e. a manifest, and a Cloudified NF Descriptor. It may contain non O-RAN specified artifacts, e.g. a ReadMe file. - -The Cloudified NF Package in this case refers to one or multiple NF Deployment packages. An NF Deployment Package contains an NF Deployment Package Descriptor (a manifest), an NF Deployment Descriptor, one or more Cloud Native Descriptor Files, and zero, one or multiple Software Images. It may also contain non O-RAN specified artifacts. - -If the NF Deployment Package contains Software Images it also contains one Software Image Descriptor for each Software Image. Whether the Software Image Descriptor is realized as a separate artifact or its contents are part of the NF Deployment Package Descriptor (the manifest) is not determined in the information model. - -The Cloudified NF Package can contain Management Descriptors or refer to a dependent Management Package. - -![UML Class Diagram for Figure 6.3.3-4: Information Model for a Package Descriptor of a Cloudified NF Package. The central class is PackageDescriptor, which has attributes: vendorPackageID (string), vendorName (string), packageType (String = Cloudified NF), applicationManagementDescriptors (0..N) ManagementDescriptor_, cloudifiedNFDescriptor (CloudifiedNFDescriptor), nDeploymentPackageDescriptors (0..1) NDeploymentPackageDescriptor, nDeploymentDescriptor (0..1) NDeploymentDescriptor, cloudNativeDescriptorFiles (0..N) CloudNativeDescriptorFile, softwareImages (0..N) SoftwareImage, softwareImageDescriptors (0..N) SoftwareImageDescriptor, vendorApplicationManagementPackageIds (0..1) string, vendorNfDeploymentPackageIds (0..N) string, and nonOranArtifact (0..N) NonOranArtifact. Associations: 1..N PackageDescriptor to 0..1 ApplicationManagementPackage (role: +vendorApplicationManagementPackageId); 0..N PackageDescriptor to 0..N ManagementDescriptor_ (role: +applicationManagementDescriptors); 1 PackageDescriptor to 1 CloudifiedNFDescriptor; 1 PackageDescriptor to 0..1 NDeploymentDescriptor; 1 PackageDescriptor to 0..N CloudNativeDescriptorFile; 1 PackageDescriptor to 0..N SoftwareImage; 1 PackageDescriptor to 0..N SoftwareImageDescriptor; 1 PackageDescriptor to 0..1 NDeploymentPackageDescriptor; 1 PackageDescriptor to 0..N NonOranArtifact; 1 NDeploymentPackageDescriptor to 0..N NDeploymentPackage (role: +vendorNfDeploymentPackageIds).](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) - -UML Class Diagram for Figure 6.3.3-4: Information Model for a Package Descriptor of a Cloudified NF Package. The central class is PackageDescriptor, which has attributes: vendorPackageID (string), vendorName (string), packageType (String = Cloudified NF), applicationManagementDescriptors (0..N) ManagementDescriptor\_, cloudifiedNFDescriptor (CloudifiedNFDescriptor), nDeploymentPackageDescriptors (0..1) NDeploymentPackageDescriptor, nDeploymentDescriptor (0..1) NDeploymentDescriptor, cloudNativeDescriptorFiles (0..N) CloudNativeDescriptorFile, softwareImages (0..N) SoftwareImage, softwareImageDescriptors (0..N) SoftwareImageDescriptor, vendorApplicationManagementPackageIds (0..1) string, vendorNfDeploymentPackageIds (0..N) string, and nonOranArtifact (0..N) NonOranArtifact. Associations: 1..N PackageDescriptor to 0..1 ApplicationManagementPackage (role: +vendorApplicationManagementPackageId); 0..N PackageDescriptor to 0..N ManagementDescriptor\_ (role: +applicationManagementDescriptors); 1 PackageDescriptor to 1 CloudifiedNFDescriptor; 1 PackageDescriptor to 0..1 NDeploymentDescriptor; 1 PackageDescriptor to 0..N CloudNativeDescriptorFile; 1 PackageDescriptor to 0..N SoftwareImage; 1 PackageDescriptor to 0..N SoftwareImageDescriptor; 1 PackageDescriptor to 0..1 NDeploymentPackageDescriptor; 1 PackageDescriptor to 0..N NonOranArtifact; 1 NDeploymentPackageDescriptor to 0..N NDeploymentPackage (role: +vendorNfDeploymentPackageIds). - -Figure 6.3.3-4 Information Model for a Package Descriptor of a Cloudified NF Package - -NOTE: This information model does not prevent a data model in which the SoftwareImageDescriptor is contained in the Package Descriptor. - -![UML Class Diagram for Figure 6.3.3-5: Information Model for a Package Descriptor of an NF Deployment Package. The central class is NfDeploymentPackageDescriptor, which has attributes: vendorPackageID (string), vendorName (string), packageType (String = NF Deployment), applicationManagementDescriptors (0..N) ManagementDescriptor_, nDeploymentDescriptor (NfDeploymentDescriptor), cloudNativeDescriptorFiles (1..N) CloudNativeDescriptorFile, softwareImages (0..N) SoftwareImage, softwareImageDescriptors (0..N) SoftwareImageDescriptor, and nonOranArtifact (0..N) NonOranArtifact. Associations: 1..N NfDeploymentPackageDescriptor to 0..N ManagementDescriptor_ (role: +applicationManagementDescriptors); 1 NfDeploymentPackageDescriptor to 1 NfDeploymentDescriptor; 1 NfDeploymentPackageDescriptor to 1..N CloudNativeDescriptorFile; 1 NfDeploymentPackageDescriptor to 0..N SoftwareImage; 1 NfDeploymentPackageDescriptor to 0..N SoftwareImageDescriptor; 1 NfDeploymentPackageDescriptor to 0..N NonOranArtifact.](a7c51c18111139f9aca2805114108565_img.jpg) - -UML Class Diagram for Figure 6.3.3-5: Information Model for a Package Descriptor of an NF Deployment Package. The central class is NfDeploymentPackageDescriptor, which has attributes: vendorPackageID (string), vendorName (string), packageType (String = NF Deployment), applicationManagementDescriptors (0..N) ManagementDescriptor\_, nDeploymentDescriptor (NfDeploymentDescriptor), cloudNativeDescriptorFiles (1..N) CloudNativeDescriptorFile, softwareImages (0..N) SoftwareImage, softwareImageDescriptors (0..N) SoftwareImageDescriptor, and nonOranArtifact (0..N) NonOranArtifact. Associations: 1..N NfDeploymentPackageDescriptor to 0..N ManagementDescriptor\_ (role: +applicationManagementDescriptors); 1 NfDeploymentPackageDescriptor to 1 NfDeploymentDescriptor; 1 NfDeploymentPackageDescriptor to 1..N CloudNativeDescriptorFile; 1 NfDeploymentPackageDescriptor to 0..N SoftwareImage; 1 NfDeploymentPackageDescriptor to 0..N SoftwareImageDescriptor; 1 NfDeploymentPackageDescriptor to 0..N NonOranArtifact. - -Figure 6.3.3-5 Information Model for a Package Descriptor of an NF Deployment Package - -NOTE: This information model does not prevent a data model in which the SoftwareImageDescriptor is contained in the Package Descriptor. - -### 6.3.4 Requirement traceability - -Table 6.3.4-1 lists the requirements in clause 7.2.6 that are derived from this use case. - -**Table 6.3.4-1 Requirements derived from this use case** - -| Requirement | Comment | -|----------------|---------| -| REQ-CNF-CON-01 | | -| REQ-CNF-CON-02 | | -| REQ-CNF-CON-04 | | -| REQ-CNF-CON-05 | | -| REQ-CNF-CON-06 | | - -## 6.4 PNF application: packaging use case - -### 6.4.1 Description - -The PNF is a physical network appliance containing one or more Network Functions. Life cycle of the device is managed by the SMO as well as provisioning and assurance of the device. A PNF Application Package must be onboarded to create an inventory record which is a pre-requisite for PNF Registration. Detection occurs when a registration message is received from the PNF after it is powered on. To create that inventory record, a PNF Application Package with its management descriptors must be onboarded. The management descriptors are included in the PNF Application package or in one or several of the dependent packages, referenced from the PNF Application package. - -The PNF can be delivered either as a single package, or it can be composed of several related packages enabling independent life cycles for PNF components. This use case provides the analysis for data requirements for the PNF Application Package. The contents of an Application Management Package are documented in a separate use case. - -### 6.4.2 Analysis - -As depicted in figure 6.4.3-1 the PNF Application Package is an archive containing a manifest identifying all contained artifacts and dependent packages. Delivery of the PNF application software can be done in a single package, or in a component manner using references to PNF Component Packages. This enables independent life cycle management of the PNF components. - -The Software Package is an artifact which is the binary data to be provided to the PNF as its software. - -Both the PNF Application Package and the PNF Component Package may contain Software Packages, but the PNF Component Package only contains one. - -Artifacts are files in the PNF Application Package or in the PNF Component Package, e.g. the package manifest, a SoftwarePackage, etc. - -The PNF does require Management Descriptors, such as data to inform the SMO what security settings need to be applied to the hardware after its registration. These can be included in the PNF Application Package, distributed across the PNF Component Packages, or in an independent Application Management Package, see figure 6.4.3-2. As the PNF must have at least one Software Package, there shall also be at least one Software Package Descriptor. - -### 6.4.3 Information model relationships - -![UML Package Diagram showing relationships between PNFComponentPackage, PackageDescriptor, ManagementDescriptor_, PNFApplicationPackage, SoftwarePackage, and ManagementPackage.](8307f6b04df072c9332f9987e034272c_img.jpg) - -``` - - graph TD - PNFComponentPackage[PNFComponentPackage] --> PackageDescriptor[PackageDescriptor] - PNFComponentPackage --> ManagementDescriptor_[ManagementDescriptor_] - PNFComponentPackage --> SoftwarePackage[SoftwarePackage] - PNFComponentPackage --> PNFApplicationPackage[PNFApplicationPackage] - PNFApplicationPackage --> PackageDescriptor - PNFApplicationPackage --> ManagementDescriptor_ - PNFApplicationPackage --> SoftwarePackage - PNFApplicationPackage --> ManagementPackage[ManagementPackage] - -``` - -UML Package Diagram showing relationships between PNFComponentPackage, PackageDescriptor, ManagementDescriptor\_, PNFApplicationPackage, SoftwarePackage, and ManagementPackage. - -Figure 6.4.3-1 PNF Application Package Relationships - -From the relationships depicted in Figure 6.4.3-1 we see that A PNF Component Package contains part of the software of the PNF. A PNF Component Package is limited to only one Software Package. It cannot refer to other packages. The PNF Application Package, in contrast, can contain more than one Software Packages. The PNF Application Package can refer to many PNF Component Packages and it can reference a dependent Application Management Package if desirable. - -![UML Class Diagram for PackageDescriptor with attributes and associations.](21ad58fee90f2be50708ff541d225507_img.jpg) - -``` - - classDiagram - class PackageDescriptor { - vendorPackageID string - vendorName string - packageType String = PNF - softwarePackageFileNames [0..N] String - applicationManagementDescriptors[0..N] ManagementDescriptor_ - vendorApplicationManagementPackageId[0..1] string - vendorComponentPackageIds[0..N] string - } - PackageDescriptor "1" -- "0..N" SoftwarePackage : +softwarePackageFileNames - PackageDescriptor "1" -- "0..1" ApplicationManagementPackage : +applicationManagementPackageId - PackageDescriptor "1" -- "0..N" PNFComponentPackage : +componentPackages - PackageDescriptor "1" -- "0..N" ManagementDescriptor_ : +applicationManagementDescriptors - -``` - -UML Class Diagram for PackageDescriptor with attributes and associations. - -Figure 6.4.3-2 Information Model for a PNF Application PackageDescriptor - -### 6.4.4 Requirement traceability - -| Requirement | Comment | -|----------------|---------| -| REQ-COM-CON-01 | | -| REQ-PNF-CON-01 | | -| REQ-PNF-CON-02 | | - -## 6.5 NF management application: packaging use case - -### 6.5.1 Description - -The NF Management Application Package use case is about what information is required to manage a Managed Element based on what it can expose over the O1 interface. The use case focuses on when a management application package referenced by the main Application Package is delivered. However, the Management Descriptors may also be provided in the Application Package or across several dependent application component packages. - -### 6.5.2 Analysis - -The Management artifacts are used by the SMO to enable operational management of a NF, rApp, or xApp. In this version of this document only the management of NFs is supported. It is directly focused on those artifacts used to manage the application over the O1 or FH M-Plane interfaces. If a license is required to operate any contained management functions or usage data is required for validation that the volume of any contained NF does not exceed its licensed limits, then an accounting descriptor may be supplied. The Security Descriptor is optional in that elements may not exist and RBAC values and assignments can be discovered once the element has been deployed. - -### 6.5.3 Information model relationships - -#### 6.5.3.1 Management descriptors - -Elements of the NF Management package can be included in other packages. There is no one Management Descriptor but multiple types of Management Descriptors. An abstract class is used to identify the common data that is required in each Management Descriptor. Figure 6.5.3.1-2 shows the inheritance relationships between the different types of Management Descriptors and the abstract class. Each type of specific Management Descriptor is independently described in the following clauses. The diagrams in this section use a convention of yellow as mandatory and light blue as optional. See Figure 6.5.3.1-1 as the diagramming legend. - -![UML Class diagram showing inheritance from ManagementDescriptor_ to various specific descriptors. TelemetrySchemaDescriptor, PackageDescriptor, NRMPParameterValues, PerformanceDictionary, AlarmDictionary, NRMSchema, and AccountingDescriptor are yellow (Required). SecurityDescriptor is light blue (Optional). Arrows point from the specific descriptors to the base class ManagementDescriptor_.](124c6108c63173818afb8ed49521e22d_img.jpg) - -Required Element - -Optional Element - -**Figure 6.5.3.1-1 Relationship UML Color Scheme** - -``` - -classDiagram - class TelemetrySchemaDescriptor { - <> - } - class PackageDescriptor - class NRMPParameterValues { - <> - } - class ManagementDescriptor_ { - <> - } - class SecurityDescriptor { - <> - } - class PerformanceDictionary { - <> - } - class AlarmDictionary { - <> - } - class NRMSchema { - <> - } - class AccountingDescriptor { - <> - } - - TelemetrySchemaDescriptor --|> ManagementDescriptor_ : 1..N +managementDescriptors - PackageDescriptor --|> ManagementDescriptor_ : 1 - NRMPParameterValues --|> ManagementDescriptor_ - SecurityDescriptor --|> ManagementDescriptor_ - PerformanceDictionary --|> ManagementDescriptor_ - AlarmDictionary --|> ManagementDescriptor_ - NRMSchema --|> ManagementDescriptor_ - AccountingDescriptor --|> ManagementDescriptor_ - style TelemetrySchemaDescriptor fill:#ffff00 - style PackageDescriptor fill:#ffff00 - style NRMPParameterValues fill:#ffff00 - style ManagementDescriptor_ fill:#ffff00 - style SecurityDescriptor fill:#add8e6 - style PerformanceDictionary fill:#ffff00 - style AlarmDictionary fill:#ffff00 - style NRMSchema fill:#ffff00 - style AccountingDescriptor fill:#ffff00 - -``` - -UML Class diagram showing inheritance from ManagementDescriptor\_ to various specific descriptors. TelemetrySchemaDescriptor, PackageDescriptor, NRMPParameterValues, PerformanceDictionary, AlarmDictionary, NRMSchema, and AccountingDescriptor are yellow (Required). SecurityDescriptor is light blue (Optional). Arrows point from the specific descriptors to the base class ManagementDescriptor\_. - -Figure 6.5.3.1-2 Management Descriptor Relationships - -#### 6.5.3.2 Alarm dictionary - -Fault management consists of being able to handle alarms. An element which detects a fault may elevate the detection by notifying a management system. This is known as an alarm. Several O-RAN interfaces support the reporting of alarms. To inform the management system or SMO of those alarms and information helpful to operations personnel which is not carried in the alarm event data a definition of the alarm is added to an Alarm Dictionary. The Alarm Dictionary is described in the O-RAN Information Model and Data Models Specification [2]. The Alarm Dictionary provides an interface map to map the interface event data to the definitions in the Alarm Dictionary. - -#### 6.5.3.3 Configuration descriptors - -##### 6.5.3.3.1 Telemetry schema descriptor - -The NF sends many types of telemetry data to the management system and therefore there are several different structures applicable to the messages to be received. The structures of those messages are called Telemetry Schemas. The SMO needs to receive telemetry data with a “collector”. Those collectors need the schema in order to validate and accept the data from the NF. The schema definition itself is in an artifact separate from its descriptor and is normally defined by an SDO and are typically a YAML file describing a JSON schema. - -![UML Class diagram showing Telemetry Schema Descriptor relationships. It includes classes for InformationObjectClass ManagementDescriptor_, TelemetrySchemaDescriptor, TelemetrySchemaFile, and TelemetrySchemaInfo with their attributes and associations.](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg) - -``` - -classDiagram - class ManagementDescriptor_ { - <> - } - class TelemetrySchemaDescriptor { - descriptorVersion String - telemetrySchemas[1..N] TelemetrySchemaInfo - } - class TelemetrySchemaFile { - } - class TelemetrySchemaInfo { - <> - referenceURL uri - schemaFileName String - } - - ManagementDescriptor_ <|-- TelemetrySchemaDescriptor - TelemetrySchemaDescriptor "1" *-- "1..N" TelemetrySchemaInfo : +telemetrySchemas - TelemetrySchemaInfo "1" -- "1" TelemetrySchemaFile : +schemaFileName - -``` - -UML Class diagram showing Telemetry Schema Descriptor relationships. It includes classes for InformationObjectClass ManagementDescriptor\_, TelemetrySchemaDescriptor, TelemetrySchemaFile, and TelemetrySchemaInfo with their attributes and associations. - -Figure 6.5.3.3.1-1 Telemetry Schema Descriptor relationships - -##### 6.5.3.3.2 NRM schema - -A NF configuration model is described as a Network Resource Model (NRM), as specified in the O1 Interface Specification [3]. The schema is usually defined in YANG via several NRMSchemaFiles which reference each other. One file will be the NRMSchemaRoot. Figure 6.5.3.3.2-1 shows the relationships of the NRMSchema. - -![UML Class diagram showing NRM Schema relationships. It includes classes for InformationObjectClass ManagementDescriptor_, NRMSchema, and NRMSchemaFile with their attributes and associations.](f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg) - -``` - -classDiagram - class ManagementDescriptor_ { - <> - } - class NRMSchema { - <> - NRMSchemaRoot String - NRMSchemaFileNames[1..N] String - } - class NRMSchemaFile { - } - - ManagementDescriptor_ <|-- NRMSchema - NRMSchema "1" *-- "1..N" NRMSchemaFile : +NRMSchemaFileNames - -``` - -UML Class diagram showing NRM Schema relationships. It includes classes for InformationObjectClass ManagementDescriptor\_, NRMSchema, and NRMSchemaFile with their attributes and associations. - -Figure 6.5.3.3.2-1 NRM Schema relationships - -##### 6.5.3.3.3 NRM parameter values - -An application may be provided an partial set of parameters values which follow the NRM. The parameter values can be an XML formatted file but can also be other forms. Figure 6.5.3.3.3-1 which depicts the relationships of the parameter set to other package elements. - -![UML Class diagram showing ConfigurationData inheriting from ManagementDescriptor_ and having a 1-to-1 association with ConfigurationDataFile via the attribute +configurationDataFileName.](523ab7b925beb555f88b2e1e1336974f_img.jpg) - -``` - -classDiagram - class ManagementDescriptor_ { - <> - } - class ConfigurationData { - <> - configurationVersion String - configurationDataFileName String - } - class ConfigurationDataFile - ManagementDescriptor_ <|-- ConfigurationData - ConfigurationData "1" --> "1" ConfigurationDataFile : +configurationDataFileName - -``` - -UML Class diagram showing ConfigurationData inheriting from ManagementDescriptor\_ and having a 1-to-1 association with ConfigurationDataFile via the attribute +configurationDataFileName. - -Figure 6.5.3.3.3-1 Configuration Data relationships - -#### 6.5.3.4 Accounting descriptor - -In a Radio Access Network (RAN) billing records are not normally collected. However, applications may require a license to operate. A license may be tied to some level of usage. Both the license and the application come from the same vendor. Therefore, the vendor knows in advance the metadata values which are provided with a license and can also provide them in the Accounting Descriptor to automate license assignment. Usage records which define which performance metrics should be collected to validate that application usage is aligned with the license limits can also be defined in the Accounting Descriptor. Figure 6.5.3.4-1 shows the relationships of the Accounting Descriptor. - -![UML Class diagram showing AccountingDescriptor inheriting from ManagementDescriptor_, with associations to LicenseDescriptor (0..N licenses) and UsageDescriptor (0..N usageSchemas).](1a85642ed2356d183ce598f2c8b3ee8b_img.jpg) - -``` - -classDiagram - class ManagementDescriptor_ { - <> - } - class LicenseDescriptor { - <> - licenseDescriptorId String - usageLimits KeyValuePair[0..N] - selectionTags KeyValuePair[0..N] - licenseKey String[0..1] - } - class AccountingDescriptor { - <> - descriptorVersion String - entityType String - licenses LicenseDescriptor [0..N] - usageSchemas UsageDescriptor [0..N] - } - class UsageDescriptor { - <> - usageDescriptorId String - name String - description String[0..1] - version String - usageRecordSchema KeyValuePair[1..N] - } - ManagementDescriptor_ <|-- AccountingDescriptor - AccountingDescriptor "1" --> "0..N" LicenseDescriptor : +licenses - AccountingDescriptor "1" --> "0..N" UsageDescriptor : +usageSchemas - -``` - -UML Class diagram showing AccountingDescriptor inheriting from ManagementDescriptor\_, with associations to LicenseDescriptor (0..N licenses) and UsageDescriptor (0..N usageSchemas). - -Figure 6.5.3.4-1 Accounting Descriptor Relationships - -#### 6.5.3.5 Performance dictionary - -Performance management consists of being to identify what each performance metric means and how it can be used to assist operations in determining network health and/or troubleshooting when problems are detected. Several O-RAN interfaces support the reporting of performance metrics. To inform the management system or SMO of the available performance metrics alarms and information helpful to operations personnel a definition of the performance metric to a Performance Dictionary. The Performance Dictionary is described in the O-RAN Information Model and Data Models Specification [2]. The Performance Dictionary provides an interface map to map the performance data to the definitions in the Alarm Dictionary. - -#### 6.5.3.6 Security descriptors - -Security is done at different levels. Application security can be based on Role Based Access Controls (RBAC). In these cases, the privileges, roles, and any pre-defined users may be specified as part of the Management Security Descriptor. Other security descriptors may be added as needed to address other aspects of security management. - -![UML Class diagram showing Management Security Descriptor Relationships. The diagram includes classes: ManagementDescriptor_ (base class), SecurityDescriptor (subclass), RolePrivileges (dataType), SecurityRoles (dataType), SecurityUsers (dataType), and SecurityServiceAvailabilityLevel (dataType). Relationships include inheritance, associations with multiplicities, and compositions.](a3472689858b068ef469213682965325_img.jpg) - -``` - -classDiagram - class ManagementDescriptor_ { - <> - ManagementDescriptor_ - } - class SecurityDescriptor { - <> - SecurityDescriptor - descriptorVersion String - rolePrivileges [1..N] RolePrivileges - securityRoles [1..N] SecurityRoles - securityUsers [1..N] SecurityUsers - } - class RolePrivileges { - <> - RolePrivileges - rolePrivilegeId UUID - name String - description String - roles[1..N] UUID - } - class SecurityRoles { - <> - SecurityRoles - securityRoleId UUID - name String - description String - } - class SecurityUsers { - <> - SecurityUsers - userId UUID - name String - password[] bytes; - roles[0..1] UUID - } - class SecurityServiceAvailabilityLevel { - <> - SecurityServiceAvailabilityLevel - } - - ManagementDescriptor_ <|-- SecurityDescriptor - SecurityDescriptor "1" *-- "0..N" RolePrivileges : +rolePrivileges - SecurityDescriptor "1" *-- "0..N" SecurityRoles : +securityRoles - SecurityDescriptor "1" *-- "0..N" SecurityUsers : +securityUsers - SecurityDescriptor "1" *-- "0..N" SecurityServiceAvailabilityLevel : +serviceAvailabilityLevels - RolePrivileges "1" *-- "1..N" SecurityRoles : +roles - SecurityUsers "1" *-- "1..N" SecurityRoles : +roles - -``` - -UML Class diagram showing Management Security Descriptor Relationships. The diagram includes classes: ManagementDescriptor\_ (base class), SecurityDescriptor (subclass), RolePrivileges (dataType), SecurityRoles (dataType), SecurityUsers (dataType), and SecurityServiceAvailabilityLevel (dataType). Relationships include inheritance, associations with multiplicities, and compositions. - -Figure 6.5.3.6-1 Management Security Descriptor Relationships - -### 6.5.4 Requirement traceability - -This aspect should be numbered 6.5.4. The section should identify applicable non-functional requirements which are defined in clause 7.2 of this specification. The traceability should be in the form of a table including the requirement identifier and an optional comment or clarification of the requirement as it applies to the use case. - -| Requirement | Note | -|----------------|------| -| REQ-OAM-CON-21 | | -| REQ-OAM-CON-31 | | -| REQ-OAM-CON-32 | | -| REQ-OAM-CON-33 | | -| REQ-OAM-CON-41 | | -| REQ-OAM-CON-42 | | -| REQ-OAM-CON-51 | | -| REQ-OAM-CON-61 | | -| REQ-OAM-CON-62 | | -| REQ-OAM-CON-63 | | -| REQ-OAM-CON-71 | | -| REQ-OAM-CON-81 | | -| REQ-OAM-CON-82 | | -| REQ-OAM-CON-91 | | -| REQ-OAM-CON-92 | | - -## 6.6 rApp package use case - -### 6.6.1 Description - -#### 6.6.1.1 rApp package Delivery - -A solution provider has developed an rApp for deployment on the SMO platform. The rApp is delivered as a package and is capable of being lifecycle managed through the rApp management SMOS once onboarded through the onboarding SMOS. - -An rApp is composed of one or more App components. Each App component contains the information needed for a set of R1 Services [4] that the rApp will produce or consume. Information relevant to a specific SMOS shall be defined within one component except for the rApp management SMOS capabilities. Information relevant to a specific rApp management SMOS capability shall be defined within one component. An App component may contain one or several files defining the content of the component. A list of the App components present in the rApp package will be contained in the App descriptor. - -The following are examples of App components: - -- SME – Provides a list of Service API's for rApp registration and/or discovery -- DME – Provides a list of DME Data types and data jobs for rApp registration and/or discovery -- Configuration – Provides instance configuration settings for an rApp -- Fault – Provides a list of alarms and alerts that can be raised by an rApp -- Workload – Provides the deployment descriptor, cloud native deployment artifacts and software images for an rApp - -Additional App components may contain items necessary for interaction with other R1 Services. A solution provider shall include one or more App components to realize the rApp functionality. - -#### 6.6.1.2 rApp with SME component - -The solution provider packages an rApp with a component to produce and consume SME related R1 Services. This includes a list of service API's it would like to produce and/or consume. - -#### 6.6.1.3 rApp with DME component - -The solution provider packages an rApp with a component to produce and/or consume DME related R1 Services. This includes a list of DME types the rApp will produce and a list of DME data jobs the rApp will consume. - -### 6.6.2 Analysis - -From the use case described in the previous clause the following artifacts are identified in the rApp package: - -- A manifest listing the package contents. -- An App descriptor listing the App components -- App components describing how the rApp wants to use the R1 Service, e.g.: - - A workload component containing a Deployment descriptor (e.g. an ASD), software images and Cloud native descriptor files, e.g. Helm charts. - - A SME component for listing R1 API's to be produced/consumed. - - A DME component for listing Datatypes to be produced and data jobs to be consumed. - -### 6.6.3 Information model relationships - -*Editor's Note: This section will be completed at a later date* - -### 6.6.4 Requirement traceability - -**Table 6.6.4-1 Requirements derived from this use case** - -| Requirement | Comment | -|---------------|---------| -| REQ-RAPP-X-01 | | -| REQ-RAPP-X-02 | | -| REQ-RAPP-X-03 | | -| REQ-RAPP-X-04 | | -| REQ-RAPP-X-05 | | -| REQ-RAPP-X-06 | | -| REQ-RAPP-X-07 | | - -# --- 7 Requirements for Application Packaging - -## 7.1 Requirement Conventions - -Requirement categories are described in the “Management interface specification methodology”, clause A.1.3. In those descriptions the conceptual (CON) requirements description best matches the requirements of the Application Packaging in regard to concept, data type, relation, format, or structure. - -Requirements are be written based on the following template: - -REQ-Label-CON-Number {Category, number} Details {Source Citation} - -where "Label" is an abbreviation for the application type the requirement is scoped to, and “Number” is unique 2-digit numerical value within the label. - -- COM Common to all application types - -- PNF Packaging requirements specific to the Physical Network Function -- OAM Packaging requirements specific to the Management of Network Functions and/or their components -- CNF Packaging requirements specific to the Cloudified Network Function -- NFD Packaging requirements specific to the Network Function Deployment -- RAPP Packaging Requirements specific to the rApp -- XAPP Packaging Requirements specific to the xApp - -## 7.2 Non-Functional Requirements - -### 7.2.1 Requirements for all Application Packages - -- REQ-COM-CON-01:** The Application Package shall be compliant to the packaging requirements as specified in O-RAN Security Requirements [1]. -- REQ-COM-CON-02:** The Application Package shall contain information enabling an Onboarding Service to identify the type of application contained in the package (Cloudified NF package, NF Deployment package, etc.) - -### 7.2.2 Requirements for Cloudified Network functions - -- REQ-CNF-CON-01:** The Cloudified NF package shall contain a manifest listing all package contents, including URLs to external artifacts if any, and references to subordinated NF Deployment packages and a subordinated Management package, if they exist. -- REQ-NFD-CON-01:** The NF Deployment package shall contain a manifest listing all package contents, including URLs to external artifacts if any. -- REQ-CNF-CON-02:** The manifest shall contain metadata that identifies the type of artifact (e.g. software image) for each entry in the list of contents. -- REQ-CNF-CON-03:** The Cloudified NF package shall contain a Cloudified NF Descriptor. -- REQ-NFD-CON-02:** The NF Deployment package shall contain an NF Deployment Descriptor. -- REQ-NFD-CON-03:** If the NF Deployment is based on containerized workloads, the NF Deployment package shall contain one or more cloud native descriptor files or refer to them as external artifacts -- REQ-NFD-CON-04:** If the NF Deployment uses executable software, the NF Deployment package shall contain one or multiple software images, or refer to them as external artifacts. -- REQ-CNF-CON-04:** If the Cloudified NF consists of more than one NF Deployment there shall be an NF Deployment package for each NF Deployment and the Cloudified NF package shall contain references to all the NF Deployment packages. -- REQ-CNF-CON-05:** If the Cloudified NF consists of a single NF Deployment the Cloudified NF Package shall either contain a reference to an NF Deployment package or directly contain the NF Deployment package files (NF Deployment descriptor, software images, etc.) without a separate NF Deployment package. -- REQ-CNF-CON-06:** For a Cloudified NF, a management descriptor shall either be included in a Management package referred to in the manifest of the Cloudified NF package or included in one or multiple NF deployment packages. - -### 7.2.2 Requirements for Physical Network Elements - -- REQ-PNF-CON-01:** The PNF Application Package or its referenced dependent package(s) shall contain a SoftwarePackageDescriptor for every part of the PNF software architecture. - -### 7.2.3 Requirements for Application Management Packages - -- REQ-OAM-CON-21:** The Application Management Package shall contain an AlarmDictionary which identifies all alarms that can be sent from the application to the management system. -- REQ-OAM-CON-31:** The Application Management Package shall contain an NRM or its equivalent which provides the schema definition for the configuration of the application. -- REQ-OAM-CON-32:** The Application Management Package shall contain a TelemetrySchemaDescriptor which provides the schema definitions and their associated identifying URL for all messages sent from the application to the management system. -- REQ-OAM-CON-33:** The Application Management Package may contain a set of initial NRM parameter values defined for the application. -- REQ-OAM-CON-41:** When the application requires a license key then an AccountingDescriptor with at least one LicenseDescriptor shall be included in the Application Management Package. -- REQ-OAM-CON-42:** When the application requires a license key and requires specific usage data to monitor key limits then a UsageDescriptor shall be added to the AccountingDescriptor and be included in the Application Management Package. -- REQ-OAM-CON-51:** The Application Management Package shall contain a PerformanceDictionary which identifies all performance measures that can be sent from the element to the management system. -- REQ-OAM-CON-61:** When the application supports role-based access controls the default users, roles, privileges and their assignments to each other, the Application Management Package shall include a SecurityDescriptor. -- REQ-OAM-CON-62:** An Application Management descriptor may include a Security Descriptor with a service availability level, as required in O-RAN Security Requirements [1] and described in [i.4]. For CNFs and VNFs this data would be informative only. - -### 7.2.4 Requirements for rApp Packages - -- REQ-RAPP-CON-01:** The rApp package shall contain a manifest listing all package contents. -- REQ-RAPP-CON-02:** The rApp package shall contain an App descriptor identifying the App components included. -- REQ-RAPP-CON-03:** The rApp package shall contain a workload component containing a deployment descriptor, cloud native descriptor files and software images. -- REQ-RAPP-CON-04:** The rApp package may contain a SME component listing R1 API's to be produced or consumed. -- REQ-RAPP-CON-05:** The rApp package may contain a DME component listing Datatypes to be produced and data jobs to be consumed. -- REQ-RAPP-CON-06:** The rApp package may contain a Configuration component listing the configuration settings for the rApp instance. -- REQ-RAPP-CON-07:** The rApp package may contain a Fault component listing the Alarms and Alerts that the rApp instance can raise. - -# Annex (informative): Change history/Change request (history) - - - - - - - -| Date | Revision | Description | -|------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2024.10.09 | 00.00.01 | Create initial O-RAN version from TS Template. | -| 2024.12.03 | 00.00.02 | Includes CRs:
ATT-2024.09.17-WG10-CR-0003-Initial Outline and Skeleton Cleanup-v02
ATT-2024.09.17-WG10-CR-0004-Principle Data Minimization-v02 | -| 2025.11.10 | 00.00.03 | Includes CRs:
ATT-2024.10.10-WG10-CR-0005-GA Artifact Management-v04
ATT-2024.12.18-WG10-CR-0007-UC Conventions-v03
ERI-2025.03.25-WG10-CR-0164-CloudifiedNFUseCase_v05
ERI-2025.09.22-WG10-CR-0195-CloudifiedNF_InfoModel-v02
ATT-2025.01.29-WG10-CR-0008-UC PNF-v15
ATT-2025.01.29-WG10-CR-0009-UC Application Management v12
ERI-2025.10.06-WG10-CR-0203-rAppPkgUseCase-v01 | -| 2025.11.10 | 00.00.04 | CR conflict and editorial cleanup for release | -| 2025.11.13 | 00.00.05 | Removed unused definitions | -| 2025.11.25 | 00.00.06 | Editorial comments from release review | \ No newline at end of file diff --git a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.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/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_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/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/124c6108c63173818afb8ed49521e22d_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/124c6108c63173818afb8ed49521e22d_img.jpg deleted file mode 100644 index 40d03deee00ca6cb9f62fc25b97fccf99d592169..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/124c6108c63173818afb8ed49521e22d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4f99cfd14bd844571523d3866025f22bb65cf25dbf9f805a8e98f80a2fefafad -size 91729 diff --git a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.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/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg deleted file mode 100644 index b7ec675326745de1d026dad5b1d7a2b4090a4da9..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/1a85642ed2356d183ce598f2c8b3ee8b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6082d1c6f5cc8e6d6cf8244743ed0b1e41c956856bbbb0ae3fc1444a8d90529e -size 55499 diff --git a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/21ad58fee90f2be50708ff541d225507_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/21ad58fee90f2be50708ff541d225507_img.jpg deleted file mode 100644 index eb5b5e681ebd1d03fe15545b09a424a9577353b3..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/21ad58fee90f2be50708ff541d225507_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ca06f4eaba993bd3ea7fa00aac6c26dcf1f91c41ff6dd29c2c744b1552c9a8ce -size 45213 diff --git a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/253600420ae7bd7d0119563b895cbf8a_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/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg deleted file mode 100644 index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_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/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/38222c3ae003223a67635bfcc6950fbb_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/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg deleted file mode 100644 index 9ebeef0e001b2d8b5cb8ee0658db5bc561be6653..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c81e7ae48085f92cae23f5c8251e5fdd384dbd3f336b58ccbcc76252f9ca8fd -size 48381 diff --git a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/4636adff5682a064f0ae5f13a1d464a6_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/4636adff5682a064f0ae5f13a1d464a6_img.jpg deleted file mode 100644 index 846f7bd4f2b673945fae979fd72bab4a4d8e7e88..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/4636adff5682a064f0ae5f13a1d464a6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f86ea449380a699efe8142461157fae9307feb4ca0022b0826eb85f6f4bfcbed -size 45041 diff --git a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg deleted file mode 100644 index d6e5213e58a210ddd29e8896c525adf19f9a5f2f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8bed75e1c9a110dc88673ba0146d849c2902155feca1d5e89ba6f12834d96d92 -size 47814 diff --git a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index f3a71b98fcfc274b0603208cc5e23601d7fc924a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:84a0e505aa8e8fcec39c03736b466858a7c1ef91abe309cdd2974ee18257e23b -size 4531 diff --git a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/523ab7b925beb555f88b2e1e1336974f_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/523ab7b925beb555f88b2e1e1336974f_img.jpg deleted file mode 100644 index e1e5347819716546b24a78fde7c8d930ff52e92d..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/523ab7b925beb555f88b2e1e1336974f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f9725381cffec0079c6094330a5e3438578e101c475e12c13fd49d639dd294c3 -size 30703 diff --git a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.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/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/8307f6b04df072c9332f9987e034272c_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/8307f6b04df072c9332f9987e034272c_img.jpg deleted file mode 100644 index 688548275fea66eb8bf4cfcd224ac593aa43ef3c..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/8307f6b04df072c9332f9987e034272c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:725557506cd15d53faf29a68cdacb986effae6c8c72c461d4cefc3a92b3efa12 -size 45568 diff --git a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.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/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/8dcca7651accff77ce832523fe2c7e64_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/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg deleted file mode 100644 index 536ff6931c42b5a7d21b25af1002ef815c3626cc..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8477185b4e6e1e9d5cb0b92ec8598063d448d07fe2a2cd5bab6f87c431d39e03 -size 53278 diff --git a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/a3472689858b068ef469213682965325_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/a3472689858b068ef469213682965325_img.jpg deleted file mode 100644 index 78ebfa301fed7bd77fb5fb704a5eadca1cc9d34d..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/a3472689858b068ef469213682965325_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3b49e883dc2d1b719ba162c48b966a232c04c6880b8bf8c51adddee4ad2bf80b -size 94810 diff --git a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/a7c51c18111139f9aca2805114108565_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/a7c51c18111139f9aca2805114108565_img.jpg deleted file mode 100644 index af0a30f4512d016fae0e9e6fe4dc6b3e0b133a60..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/a7c51c18111139f9aca2805114108565_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60ed30aa61ec0b746e3686090c1dac8a2be67511641a39e5edc2e3858a6816c8 -size 57373 diff --git a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/c036e2540a94b31357ceb0002f0cacab_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/c036e2540a94b31357ceb0002f0cacab_img.jpg deleted file mode 100644 index d3eb520e5b194b5cefc325052836bb9a23c308cd..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/c036e2540a94b31357ceb0002f0cacab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bff566a7ac117bad73b0b7ea4f72f924944f46c634c6ed3b45c9e22adfcbeb70 -size 53663 diff --git a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/c389468860cd886ab9c732473e959f0f_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/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.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/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/e511e373339b5f948f239b19e0c37dd4_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/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg b/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg deleted file mode 100644 index 18920aeb6eb2b421326da01b292dbe93a0f54586..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.AppPkgGAP-R005-v01.00/images/f388cbdae6f0ef3aeb96fdf9984d1284_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f87c3d11b0c60220e46c4a47a6a1d77122f0f733a2a1b6a8bf5eb6c9023e6b11 -size 30341 diff --git a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/doc.md b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/doc.md deleted file mode 100644 index b76813e470252d119a475d98049f3e4e81163d8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/doc.md +++ /dev/null @@ -1,1291 +0,0 @@ - - -![O-RAN ALLIANCE logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) - -The logo for the O-RAN ALLIANCE, featuring a colorful circular icon to the left of the text "O-RAN" in blue, with "ALLIANCE" in smaller blue letters underneath. - -O-RAN ALLIANCE logo - -# O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00 *Technical Specification* --- - ---- - -## **O-RAN Work Group 10 (OAM for O-RAN)** - -# **O-RAN Information Model and Data Models 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., Buschkauler Weg 27, 53347 Alfter, Germany -Register of Associations, Bonn VR 11238, VAT ID DE321720189 - -# Contents - -| | | -|--------------------------------------------------------------------------------------------------------------------------|----| -| Foreword ..... | 3 | -| Modal verbs terminology ..... | 4 | -| 1 Scope ..... | 4 | -| 2 References ..... | 4 | -| 2.1 Normative references ..... | 4 | -| 2.2 Informative references ..... | 5 | -| 3 Definitions of term, symbols and abbreviations ..... | 7 | -| 3.1 Terms ..... | 7 | -| 3.2 Symbols ..... | 7 | -| 3.3 Abbreviations and acronyms ..... | 7 | -| 4 Overview and Philosophy ..... | 8 | -| 4.1 Relationship between O-RAN and Standards Development Organizations ..... | 8 | -| 5 O-RAN Information Model ..... | 9 | -| 5.1 Information Modeling Conventions ..... | 9 | -| 5.1.1 Modeling approach, Unified Modeling Language (UML) ..... | 9 | -| 5.1.2 Namespaces in the Information Model ..... | 9 | -| 5.2 O-RAN Information Model Definitions ..... | 9 | -| 5.2.1 Namespace: ORAN.ManagementArtifacts ..... | 9 | -| 6 O-RAN Data Models ..... | 26 | -| 6.1 Formal relationship (traceability) between O-RAN Data Models and the O-RAN Information Model ..... | 26 | -| 6.2 YANG Conventions ..... | 27 | -| 6.2.1 General ..... | 27 | -| 6.2.2 Naming ..... | 27 | -| 6.2.3 Revision Statement ..... | 28 | -| 6.2.4 Indents ..... | 28 | -| 6.2.5 YANG Language Usage ..... | 28 | -| 6.2.6 Cross Working Group Co-ordination ..... | 29 | -| 6.2.7 Void ..... | 29 | -| 6.2.8 Augmentations of YANG Data Models ..... | 29 | -| Annex A (informative): Links to Data Models approved for use ..... | 30 | -| Annex B (informative): Relations between Information Model and Data Models ..... | 31 | -| B.1 Information and Data Models as a Modeling Continuum ..... | 31 | -| B.2 Information and Data Modeling Co-Evolution ..... | 31 | -| B.3 Model and Use Case Development (process) ..... | 32 | -| Annex C (informative): Classes/components and interfaces that comprise the O-RAN Information Model and Data Models ..... | 34 | -| Annex D (informative): Usage of models ..... | 36 | -| D.1 Usage of 3GPP Data Models ..... | 36 | -| D.2 Usage of non-3GPP data models ..... | 38 | -| Annex (informative): Change History ..... | 43 | - -# --- Foreword - -This Technical Specification (TS) has been produced by WG10 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 - -This document is both a Specification and an Informational Report in that it specifies the Information Model and the Data Models that are foundational for O-RAN's model-driven architecture and for the functions carried out over O-RAN interfaces. - -In addition, this document includes information about existing standards and industry work that serve as a basis for work items in O-RAN. There is a "prosumer" relationship evolving between O-RAN and 3GPP, as each makes its model available and provides model feedback to the other. - -Lastly, this document describes the de facto methods and procedures with respect to a "modeling continuum" that aims to establish and evolve an O-RAN Information Model from which O-RAN Data Models may be generated manually or with a set of tools. - -# 2 References - -## 2.1 Normative references - -References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version 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 TR 21.905: "Vocabulary for 3GPP Specifications" -- [2] 3GPP TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)" -- [3] RFC 8342: "Network Management Datastore Architecture (NMDA)", IETF -- [4] RFC 8407: "Guidelines for Authors and Reviewers of Documents Containing YANG Data Models", IETF, October 2018 -- [5] RFC 7950, "The YANG 1.1 Data Modeling Language", IETF -- [6] 3GPP TS 32.156: "Telecommunication management; Fixed Mobile Convergence (FMC) Model repertoire" -- [7] 3GPP TS 32.160: "Management and orchestration; Management service template" - -- [8] O-RAN.WG10.TS.O1-Interface: “O-RAN O1 Interface Specification” -- [9] OMG formal/2017-12-05: OMG® Unified Modeling Language® (OMG UML®), Version 2.5.1 -- [10] O-RAN.WG3.TS.O1-Interface-for-Near-RT-RIC: “O1 Interface Specification for Near Real Time RAN Intelligent Controller” -- [11] 3GPP TS 28.625: “Telecommunication management; State Management Data Definition Integration Reference Point (IRP); Information Service (IS)” -- [12] O-RAN.WG6.TS.O2IMS-INTERFACE: “O2ims Interface Specification” -- [13] 3GPP TS 32.404: “Technical Specification Group Services and System Aspects; Telecommunication management; Performance Management (PM); Performance measurements” -- [14] ETSI GS NFV-IFA 027 V4.2.1, ”Network Functions Virtualisation (NFV) Release 4; Management and Orchestration; Performance Measurements Specification” -- [15] 3GPP TS 28.620: “Telecommunication management; Fixed Mobile Convergence (FMC), Federated Network Information Model (FNIM), Umbrella Information Model (UIM)” -- [16] 3GPP TS 28.111: “Management and orchestration; Fault Management (FM)” - -## 2.2 Informative references - -References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version 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.WG4.TS.MP.0: “O-RAN Alliance Working Group 4 Management Plane Specification” -- [i.2] RFC 6241, “Network Configuration Protocol (NETCONF)”, IETF, June 2011 -- [i.3] “Modeling, Use Case and Architecture Process,” B. Cheung et al, May 2019, ONAP -- [i.4] O-RAN.WG2.TS.A1AP: “O-RAN Working Group 2 (Non-RT RIC and A1 interface WG) A1 interface: Application Protocol” -- [i.5] O-RAN.WG3.TS.E2GAP: “O-RAN Working Group 3 Near-Real-time RAN Intelligent Controller Architecture & E2 General Aspects and Principles” -- [i.6] O-RAN.WG5.O-CU-O1: “O1 Interface specification for O-CU-UP and O-CU-CP” -- [i.7] O-RAN.WG5.O-DU-O1: “O1 Interface specification for O-DU” -- [i.8] 3GPP TS 28.623: “Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions” -- [i.9] 3GPP TS 36.423: “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 application protocol (X2AP)” - -- [i.10] 3GPP TS 38.460: “Technical Specification Group Radio Access Network; NG-RAN; E1 general aspects and principles” -- [i.11] 3GPP TS 38.470: “Technical Specification Group Radio Access Network; NG-RAN; F1 general aspects and principles” -- [i.12] 802.1X-2020, “IEEE Standard for Local and Metropolitan Area Networks--Port-Based Network Access Control”, IEEE, 2020-02-28 -- [i.13] RFC 5717: “Partial Lock Remote Procedure Call (RPC) for NETCONF”, IETF, December 2009 -- [i.14] RFC 6022: “YANG Module for NETCONF Monitoring”, IETF, October 2010 -- [i.15] RFC 6243: “With-defaults Capability for NETCONF”, IETF, June 2011 -- [i.16] RFC 6470: “Network Configuration Protocol (NETCONF) Base Notifications”, IETF, February 2012 -- [i.17] RFC 6643: “Translation of Structure of Management Information Version 2 (SMIv2) MIB Modules to YANG Modules”, IETF, July 2012 -- [i.18] RFC 6991: “Common YANG Data Types”, IETF, July 2013 -- [i.19] RFC 7224: “IANA Interface Type YANG Module”, IETF, May 2014 -- [i.20] RFC 7317: “A YANG Data Model for System Management”, IETF, August 2014 -- [i.21] RFC 7758: “Time Capability in NETCONF”, IETF, February 2016 -- [i.22] RFC 7952: “Defining and Using Metadata with YANG”, IETF, August 2016 -- [i.23] RFC 8072: “YANG Patch Media Type”, IETF, February 2017 -- [i.24] RFC 8341: “Network Configuration Access Control Model”, IETF, March 2018 -- [i.26] RFC 8343: “A YANG Data Model for Interface Management”, IETF, March 2018 -- [i.27] RFC 8344: “A YANG Data Model for IP Management”, IETF, March 2018 -- [i.28] RFC 8348: “A YANG Data Model for Hardware Management”, IETF, March 2018 -- [i.30] RFC 8525: “YANG Library”, IETF, March 2019 -- [i.31] RFC 8526: “NETCONF Extensions to Support the Network Management Datastore Architecture”, IETF, March 2019 -- [i.32] RFC 8528: “YANG Schema Mount”, IETF, March 2019 -- [i.33] RFC 8575: “YANG Data Model for the Precision Time Protocol (PTP)”, IETF, May 2019 -- [i.34] RFC 8632: “A YANG Data Model for Alarm Management”, IETF, September 2019 -- [i.35] RFC 8641: “Subscription to YANG Notifications for Datastore Updates”, IETF, September 2019 -- [i.36] draft-ietf-netconf-crypto-types: “YANG Data Types and Groupings for Cryptography”, IETF -- [i.37] 3GPP TS 28.541: “Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3” -- [i.38] RFC 3198: “Terminology for Policy-Based Management” , -- [i.39] SemVer: “Semantic Versioning 2.0.0.” , -- [i.40] O-RAN.WG6.TS.O-CLOUD-IM: “O-Cloud Information Model” - -# 3 Definitions of term, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. - -**Information Model:** See Information Model in RFC 3198 [i.38]. - -**Data Model:** See Data Model in RFC 3198 [i.38]. - -**Model:** See Model [Class] in UML [9], clause 12.4.4. - -**Data Dictionary:** a centralized repository of information about data such as meaning, relationships to other data, origin, usage, and format. - -**Namespace:** See namespace as specified in UML v2.5.1 [9], clause 7.8.10 Namespace [Abstract Class]. - -**Primary Key:** value which is distinctive for each record of the table. - -**Key value pairs:** a set of data consists of two related data elements, key which is constant describing data set and its value. - -## 3.2 Symbols - -For the purposes of the present document, the symbols given in 3GPP TR 21.905 [1] and the following apply. A symbol defined in the present document takes precedence over the definition of the same symbol, if any, in 3GPP TR 21.905 [1]. - -## 3.3 Abbreviations and acronyms - -For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] 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 [1]. - -| | | -|-------|---------------------------------------------------------| -| 3GPP | 3 rd Generation Partnership Project | -| API | Application Programming Interface | -| CR | Change Requests | -| EMS | Element Management System | -| FCAPS | Fault, Configuration, Accounting, Performance, Security | -| IOC | Information Object Class | -| LS | Liaison Statement | -| MA | Managed Application | -| MANO | Management and Orchestration | -| ME | Managed Element | -| MF | Managed Function | -| MnS | Management Service | -| MO | Managed Object | -| MOC | Managed Object Class | -| MOI | Managed Object Instance | - -| | | -|--------------------|-------------------------------------------------| -| NAT | Network Address Translation | -| Near-RT RIC | O-RAN near real time RAN Intelligent Controller | -| NMS | Network Management System | -| Non-RT RIC | O-RAN non real time RAN Intelligent Controller | -| NRM | Network Resource Model | -| O-CU-CP | O-RAN Central Unit – Control Plane. | -| O-CU-UP | O-RAN Central Unit – User Plane | -| O-DU | O-RAN Distributed Unit | -| OMG | Object Management Group | -| O-RAN | Open Radio Access Network | -| O-RU | O-RAN Radio Unit | -| ONAP | Open Network Automation Platform | -| PNF | Physical Network Function | -| RAN | Radio Access Network | -| RRH | Remote Radio Head | -| SDO | Standards Development Organization | -| SMO | Service Management and Orchestration (layer) | -| TR | Technical Report | -| TS | Technical Specification | -| UML | Unified Modeling Language | -| SA5 | Services & System Aspects Working Group 5 | -| Telecom Management | VNF Virtualized Network Function | - -# 4 Overview and Philosophy - -## 4.1 Relationship between O-RAN and Standards Development Organizations - -The O-RAN Alliance complements the work of other Standards Development Organizations (SDO): 3GPP, IETF, and IANA are among the primary sources for Management specifications for O-RAN components. - -3GPP has published: - -- its Generic Network Resource Model (NRM), including: - - a Stage 2 NRM Information Model, in 3GPP TS 28.622 [2]; - - corresponding Stage 3 Solution Sets, one of which consists of YANG Data Models, in 3GPP TS 28.623 [i.8]; -- its 5G Network Resource Model (NRM), including the Stage 2 NR NRM Information Model and corresponding Stage 3 Solution Sets, one of which consists of YANG Data Models, in 3GPP TS 28.541 [i.37]; -- “Management and Orchestration APIs”, including YANG data models from both NRMs, in a publicly available git repository - -O-RAN Information Model, Data Models, and modeling processes should complement the work of other SDOs, not conflict or compete. - -When 3GPP makes updates to their specification, they are incorporated into the O-RAN OAM Interface Specification [8]. This, in turn, drives the updates that are to be made to both the Information Model and Data Models within O-RAN. - -# 5 O-RAN Information Model - -## 5.1 Information Modeling Conventions - -### 5.1.1 Modeling approach, Unified Modeling Language (UML) - -The Information Model within O-RAN shall use the Unified Modeling Language™ (UML®) version 2.5.1 [9] from the Object Management Group (OMG). - -O-RAN Information Model shall follow methodology documented in 3GPP TS 32.160 [7] Clause 5.2. - -### 5.1.2 Namespaces in the Information Model - -A Namespace provides a container for named elements, which are called its members. A Namespace may also import named elements from other specifications, in which case those elements become members of the importing Namespace. - -## 5.2 O-RAN Information Model Definitions - -### 5.2.1 Namespace: ORAN.ManagementArtifacts - -#### 5.2.1.1 Namespace Overview - -The O-RAN Management Artifacts namespace identifies classes required to represent documentation descriptions that supplement the management aspect of elements represented by the classes in the NRM. - -#### 5.2.1.2 Imported and associated information entities - -##### 5.2.1.2.1 Imported information entities and local labels - -| Label reference | Local label | -|------------------------------|-------------| -| 3GPP TS 28.622 [2], IOC, Top | Top | - -##### 5.2.1.2.2 Associated information entities and local labels - -| Label reference | Local label | -|------------------------------------------------------------------------|--------------------| -| WG6.O2-Infrastructure Management Specification [12], IOC, ResourceType | OcloudResourceType | - -#### 5.2.1.3 Class diagrams - -##### 5.2.1.3.1 Relationships - -![UML Class diagram showing Performance Dictionary Relationships. Classes include OCloudResourceType, PerformanceMeasureDictionary, Product, SupportedInterface, StandardReference, PerformanceMeasureDefinition, EventToDictionaryMap, PerformanceDictionaryMap, ETSIPerformanceMeasureDefinition, and 3GPPPerformanceMeasureDefinition. Relationships include names, implements, supportedProducts, ReportedOver, SpecificTo, HasA, and eventToMeasureDefinitionMap. Notes indicate that PerformanceMeasureDefinition is abstract and that EventToDictionaryMap is a choice based on Dictionary type.](daa4a6fa7e2ba1954258f86b4928eb32_img.jpg) - -``` - -classDiagram - class OCloudResourceType { - <> - } - class PerformanceMeasureDictionary { - <> - performanceDictionaryId : String - performanceDictionaryVersion : String - performanceDictionarySchemaVersion : String - vendor : String - supportedProducts : Product{1..*} - supportedInterfaces : SupportedInterface{1..*} - supportedMeasures : PerformanceMeasureDefinition{1..*} - } - class Product { - <> - product : String - version : String - } - class SupportedInterface { - <> - managementInterfaceId : ManagementInterface - eventToDictionaryMap : EventToDictionaryMap - } - class ManagementInterface { - O1 - O2DMS - O2IMS - OpenFH - } - class StandardReference { - <> - standardsDefinitionOrganization : String - standardSpecification : String - versionOrRelease : String - clause : String - } - class PerformanceMeasureDefinition { - <> - performanceMeasureDefinitionID : UUID - performanceMeasureID : Uint - standardReference : StandardReference{0..1} - supportedInterfaces : SupportedInterface{0..*} - extensions : KeyValuePair{0..*} - } - class EventToDictionaryMap { - <> - } - class PerformanceDictionaryMap { - <> - eventToMeasureDefinitionMap : String - } - class ETSIPerformanceMeasureDefinition { - <> - --Attributes-- - Conforms to NFV IFA-027 [14] Clause 5 - } - class 3GPPPerformanceMeasureDefinition { - <> - --Attributes-- - Conforms to TS 32.404 [13] Clause 3.3 - } - - OCloudResourceType "1" -- "0..1" PerformanceMeasureDictionary : names - PerformanceMeasureDictionary "1" -- "1..*" Product : +supportedProducts - PerformanceMeasureDictionary "1" -- "1..*" SupportedInterface : ReportedOver - PerformanceMeasureDictionary "1" -- "1..*" PerformanceMeasureDefinition : supportedMeasures - StandardReference "1" -- "1" PerformanceMeasureDefinition : implements - PerformanceMeasureDefinition "1" -- "1..*" PerformanceMeasureDictionary : SpecificTo - SupportedInterface "1" -- "1" EventToDictionaryMap : HasA - EventToDictionaryMap "1" -- "1" PerformanceDictionaryMap : +eventToMeasureDefinitionMap - PerformanceMeasureDictionary "1" -- "1..*" PerformanceMeasureDefinition : SpecificTo - PerformanceMeasureDefinition <|-- ETSIPerformanceMeasureDefinition - PerformanceMeasureDefinition <|-- 3GPPPerformanceMeasureDefinition - -``` - -UML Class diagram showing Performance Dictionary Relationships. Classes include OCloudResourceType, PerformanceMeasureDictionary, Product, SupportedInterface, StandardReference, PerformanceMeasureDefinition, EventToDictionaryMap, PerformanceDictionaryMap, ETSIPerformanceMeasureDefinition, and 3GPPPerformanceMeasureDefinition. Relationships include names, implements, supportedProducts, ReportedOver, SpecificTo, HasA, and eventToMeasureDefinitionMap. Notes indicate that PerformanceMeasureDefinition is abstract and that EventToDictionaryMap is a choice based on Dictionary type. - -Figure 5.2.1.3.1-1 Performance Dictionary Relationships - -![UML Class Diagram for Alarm Dictionary Information Model](e9314c83043183351ed74908e9bf2f90_img.jpg) - -``` - -classDiagram - class OcloudResourceType - class AlarmDictionary { - <> - alarmDictionaryId: String - alarmDictionaryVersion: String - alarmDictionarySchemaVersion: String - vendor: String - supportedProducts: Product[1..*] - supportedEntityTypes: String[0..*] - supportedInterface: SupportedInterface[1..*] - alarmDefinition: AlarmDefinition[1..*] - probableCauses: ProbableCauseInfo[0..*] - } - class ProbableCauseInfo { - <> - probableCause: String or Integer - probableCauseDescription: String - standardReference: StandardReference[0..1] - } - class StandardReference { - <> - standardsDefinitionOrganization: String - standardSpecification: String - versionOrRelease: String - clause: String - } - class AlarmDefinition { - <> - alarmDefinitionId: String - alarmName: String - alarmLastChange: String - alarmChangeType: AlarmChangeType - alarmDescription: String - proposedRepairActions: String - clearingType: AlarmClearingType - managementInterfaceId: ManagementInterface - extensions: NameValuePair[0..*] - } - class Product { - <> - product: String - version: String - } - class ManagementInterface { - O1 - O2DMS - O2IMS - OpenFH - } - class AlarmClearingType { - AUTOMATIC - MANUAL - } - class AlarmChangeType { - ADDED - DELETED - MODIFIED - } - class SupportedInterface { - <> - managementInterfaceId: ManagementInterface - eventToDictionaryMap: EventToDictionaryMap - } - class EventToDictionaryMap { - <> - } - class AlarmDictionaryMap { - <> - eventToAlarmDefinitionMap: String[0..*] - } - - OcloudResourceType "1" -- "0..1" AlarmDictionary : <> - AlarmDictionary "1" -- "0..*" ProbableCauseInfo - ProbableCauseInfo "1" -- "0..*" StandardReference - AlarmDictionary "1" -- "1..*" AlarmDefinition - AlarmDictionary "1" -- "1..*" Product : +supportedProducts - AlarmDictionary "1" -- "1..*" SupportedInterface - AlarmDefinition "1" -- "1" ManagementInterface - AlarmDefinition "1" -- "1" AlarmClearingType - AlarmDefinition "1" -- "1" AlarmChangeType - SupportedInterface "1" -- "1" EventToDictionaryMap : HasA - EventToDictionaryMap "1" -- "1" AlarmDictionaryMap : +eventToAlarmDefinitionMap - Note right of EventToDictionaryMap: This choice is based on the Dictionary type - Note bottom of AlarmDictionaryMap: This alternative is applicable to the AlarmDictionary - -``` - -The diagram illustrates the information model for the Alarm Dictionary. At the top, **OcloudResourceType** is associated with **AlarmDictionary** (information object class) via a relationship labeled **<>**. **AlarmDictionary** contains attributes such as **alarmDictionaryId**, **alarmDictionaryVersion**, **alarmDictionarySchemaVersion**, **vendor**, **supportedProducts** (linked to **Product** data type), **supportedEntityTypes**, **supportedInterface** (linked to **SupportedInterface** data type), **alarmDefinition** (linked to **AlarmDefinition** data type), and **probableCauses** (linked to **ProbableCauseInfo** data type). **ProbableCauseInfo** includes **probableCause**, **probableCauseDescription**, and **standardReference** (linked to **StandardReference** data type). **StandardReference** contains **standardsDefinitionOrganization**, **standardSpecification**, **versionOrRelease**, and **clause**. **AlarmDefinition** includes **alarmDefinitionId**, **alarmName**, **alarmLastChange**, **alarmChangeType** (linked to **AlarmChangeType**), **alarmDescription**, **proposedRepairActions**, **clearingType** (linked to **AlarmClearingType**), **managementInterfaceId** (linked to **ManagementInterface**), and **extensions**. **ManagementInterface** lists **O1**, **O2DMS**, **O2IMS**, and **OpenFH**. **AlarmClearingType** includes **AUTOMATIC** and **MANUAL**. **AlarmChangeType** includes **ADDED**, **DELETED**, and **MODIFIED**. **Product** includes **product** and **version**. **SupportedInterface** includes **managementInterfaceId** and **eventToDictionaryMap** (linked to **EventToDictionaryMap** choice). **EventToDictionaryMap** is a choice between **AlarmDictionaryMap** data type (containing **eventToAlarmDefinitionMap**) and other options, with a note that this choice is based on the dictionary type. A note at the bottom indicates this alternative is applicable to the AlarmDictionary. - -UML Class Diagram for Alarm Dictionary Information Model - -Figure 5.2.1.3.1-2 Alarm Dictionary Relationships - -##### 5.2.1.3.2 Inheritance - -![UML class diagram showing inheritance for PerformanceMeasureDictionary. Top_ is the root class, defined in 3GPP TS 28.620 [15] clause 4.3.29. PerformanceMeasureDictionary inherits from Top_. PerformanceMeasureDefinition_ inherits from Top_. ETSIPerformanceDefinition and 3GPPPerformanceDefinition inherit from PerformanceMeasureDefinition_.](1439cb942d9e363bbb3161b5540dd8c6_img.jpg) - -``` - -classDiagram - class Top_ { - <> - } - class PerformanceMeasureDictionary { - <> - } - class PerformanceMeasureDefinition_ { - <> - } - class ETSIPerformanceDefinition { - <> - } - class 3GPPPerformanceDefinition { - <> - } - Top_ <|-- PerformanceMeasureDictionary - Top_ <|-- PerformanceMeasureDefinition_ - PerformanceMeasureDefinition_ <|-- ETSIPerformanceDefinition - PerformanceMeasureDefinition_ <|-- 3GPPPerformanceDefinition - note for Top_ "defined in 3GPP TS 28.620 [15] clause 4.3.29" - -``` - -UML class diagram showing inheritance for PerformanceMeasureDictionary. Top\_ is the root class, defined in 3GPP TS 28.620 [15] clause 4.3.29. PerformanceMeasureDictionary inherits from Top\_. PerformanceMeasureDefinition\_ inherits from Top\_. ETSIPerformanceDefinition and 3GPPPerformanceDefinition inherit from PerformanceMeasureDefinition\_. - -Figure 5.2.1.3.2-1 PerformancemeasureDictionary inheritance - -![UML class diagram showing inheritance for AlarmDictionary. Top_ is the root class, defined in 3GPP TS 28.620 [15] clause 4.3.29. AlarmDictionary inherits from Top_.](08441fa90c5fd11994626f662ac13f19_img.jpg) - -``` - -classDiagram - class Top_ { - <> - } - class AlarmDictionary { - <> - } - Top_ <|-- AlarmDictionary - note for Top_ "defined in 3GPP TS 28.620 [15] clause 4.3.29" - -``` - -UML class diagram showing inheritance for AlarmDictionary. Top\_ is the root class, defined in 3GPP TS 28.620 [15] clause 4.3.29. AlarmDictionary inherits from Top\_. - -Figure 5.2.1.3.2-2 Alarm Dictionary inheritance - -#### 5.2.1.4 Class definitions - -##### 5.2.1.4.1 PerformanceMeasureDictionary - -###### 5.2.1.4.1.1 Definition - -Resource Types in the O-Cloud provide the SMO a dictionary of performance measures available by Resources of the Resource Type. The O-Cloud Deployment Management Services also report performance of workloads deployed into the cloud. The DMS Performance follows ETSI-NFV specification IFA027 [14]. The performance dictionary should be structured - -to allow resource vendors to specify their unique performance measures while also supporting performance measures which are defined by a standard. - -###### 5.2.1.4.1.2 Attributes - -The `PerformanceMeasureDictionary` includes attributes inherited from Top IOC (defined in 3GPP TS 28.622 [2], clause 4.3.29) and the following attributes: - -| Attribute name | S | isReadable | isWritable | isInvariant | isNotifyable | -|-------------------------------------------------|---|------------|------------|-------------|--------------| -| performanceDictionaryId | M | T | F | T | F | -| performanceDictionaryVersion | M | T | F | T | F | -| performanceDictionarySchemaVersion | M | T | F | T | F | -| vendor | M | T | F | T | F | -| supportedProducts | M | T | F | T | F | -| supportedInterfaces | M | T | F | T | F | -| supportedMeasures | M | T | F | T | F | - -###### 5.2.1.4.1.3 Attribute constraints - -None - -###### 5.2.1.4.1.4 Notifications - -This class does not support any notification. - -###### 5.2.1.4.1.5 State diagram - -None - -##### 5.2.1.4.2 `PerformanceMeasureDefinition_ <>` - -###### 5.2.1.4.2.1 Definition - -The `PerformanceMeasureDefinition` defines the O-RAN attributes common to both variants of performance measurement definition. - -###### 5.2.1.4.2.2 Attributes - -The `PerformanceMeasureDefinition` inherits attributes from Top IOC (defined in 3GPP TS 28.622 [2], clause 4.3.29) and extends it with the following attributes: - -| Attribute name | S | isReadable | isWritable | isInvariant | isNotifyable | -|---------------------------------------------|---|------------|------------|-------------|--------------| -| performanceMeasureDefinitionId | M | T | F | T | F | -| performanceMeasureId | M | T | F | T | F | -| standardReference | M | T | F | T | F | -| supportedInterfaces | M | T | F | T | F | -| extensions | M | T | F | T | F | - -###### 5.2.1.4.2.3 Attribute constraints - -None - -###### 5.2.1.4.2.4 Notifications - -This class does not support any notification. - -###### 5.2.1.4.2.5 State diagram - -None - -##### 5.2.1.4.3 ETSIPerformanceMeasureDefinition <> - -###### 5.2.1.4.3.1 Definition - -The `ETSIPerformanceMeasureDefinition` is an extension of the `PerformanceMeasureDefinition_` abstract class. It provides extended attributes specific to an ETSI based performance measurement definition. - -###### 5.2.1.4.3.2 Attributes - -The `ETSIPerformanceMeasureDefinition` is a specialized class of the `PerformanceMeasureDefinition_` class which inherits attributes from. It extends the class with the attributed defined in ETSI NFV IFA027 [14] clause 5. - -###### 5.2.1.4.3.3 Attribute constraints - -None - -###### 5.2.1.4.3.4 Notifications - -This class does not support any notification. - -###### 5.2.1.4.3.5 State diagram - -None - -##### 5.2.1.4.4 3GPPPerformanceMeasureDefinition <> - -###### 5.2.1.4.4.1 Definition - -The `3GPPPerformanceMeasureDefinition` is an extension of the `PerformanceMeasureDefinition_` abstract class. It provides extended attributes specific to a 3GPP based performance measurement definition. - -###### 5.2.1.4.4.2 Attributes - -The `3GPPPerformanceMeasureDefinition` is a specialized class of the `PerformanceMeasureDefinition_` class which inherits attributes from. It extends the class with fields defined in 3GPP TS 32.404 [13] clause 3.3. - -###### 5.2.1.4.4.3 Attribute constraints - -None - -###### 5.2.1.4.4.4 Notifications - -This class does not support any notification. - -###### 5.2.1.4.4.5 State diagram - -None. - -##### 5.2.1.4.5 StandardReference <> - -###### 5.2.1.4.5.1 Definition - -When definition has been provided by another Standards body this dataType provides a reference to the standard body that is author of particular definition, as well as to where the definition can be found. - -###### 5.2.1.4.5.2 Attributes - -The `StandardReference` contains attributes used to identify where in a standard the definition is provided. - -| Attribute name | S | isReadable | isWritable | isInvariant | isNotifyable | -|--------------------------------|---|------------|------------|-------------|--------------| -| standardDefinitionOrganization | M | T | F | T | F | -| standardSpecification | M | T | F | T | F | -| versionOrRelease | M | T | F | T | F | -| clause | M | T | F | T | F | - -###### 5.2.1.4.5.3 Attribute constraints - -None - -###### 5.2.1.4.5.4 Notifications - -This class does not support any notification. - -###### 5.2.1.4.5.5 State diagram - -None. - -##### 5.2.1.4.6 SupportedInterface <> - -###### 5.2.1.4.6.1 Definition - -Provides mapping between fields of particular MOI to management interface over which it can be reported. - -###### 5.2.1.4.6.2 Attributes - -The `SupportedInterface` contains attributes used to identify which interface field(s) are used to match the mapping. - -| Attribute name | S | isReadable | isWritable | isInvariant | isNotifyable | -|-----------------------|---|------------|------------|-------------|--------------| -| managementInterfaceId | M | T | F | T | F | -| eventToDictionaryMap | M | T | F | T | F | - -###### 5.2.1.4.6.3 Attribute constraints - -None - -###### 5.2.1.4.6.4 Notifications - -This class does not support any notification. - -###### 5.2.1.4.6.5 State diagram - -None. - -##### 5.2.1.4.7 EventToDictionaryMap <> - -###### 5.2.1.4.7.1 Definition - -The `EventToDictionaryMap` is a choice stereotype represents one of a set of data types as shown per dictionary type in figures 5.2.1.3.1-1 and 5.2.1.3.1-2. - -###### 5.2.1.4.7.2 Attributes - -As a choice stereotype the class has no intrinsic attributes. Instead, the attributes of the class are specified in the alternative class type definitions. - -###### 5.2.1.4.7.3 Attribute constraints - -None - -###### 5.2.1.4.7.4 Notifications - -This class does not support any notification. - -###### 5.2.1.4.7.5 State diagram - -None. - -##### 5.2.1.4.8 PerformanceDictionaryMap <> - -###### 5.2.1.4.8.1 Definition - -The `PerformanceDictionaryMap` provide the attributes required to map a performance measure in a performance report to its corresponding `PerformanceMeasureDefinition` entry in an `PerformanceMeasureDictionary`. Performance measures for a given software product are reported over an interface. - -A map shall be provided between the measurement report attribute and the `performanceMeasureDefinitionId` within the dictionary for a given interface. The `PerformanceDictionaryMap` provides the ability to identify the attribute name within a performance report which shall contain the value to use as the `performanceMeasureDefinitionId` in a `PerformanceMeasureDictionary`. - -###### 5.2.1.4.8.2 Attributes - -The `PerformanceDictionaryMap` contains attributes used to identify which interface field(s) are used to match the `performanceMeasureDefinitionId` of a `PerformanceMeasureDefinition_` in the `PerformanceMeasureDictionary`. - -| Attribute name | S | isReadable | isWritable | isInvariant | isNotifyable | -|------------------------------------------|---|------------|------------|-------------|--------------| -| eventToMeasureDefinitionMap | M | T | F | T | F | - -###### 5.2.1.4.8.3 Attribute constraints - -None - -###### 5.2.1.4.8.4 Notifications - -This class does not support any notification. - -###### 5.2.1.4.8.5 State diagram - -None. - -##### 5.2.1.4.9 Void - -##### 5.2.1.4.10 AlarmDictionary - -###### 5.2.1.4.10.1 Definition - -There is more information about an alarm than is included in a notification about an alarm occurrence. The AlarmDictionary provides that data to the SMO such that the extended data may be used to assist in alarm event processing. These could include repair actions which guide a user of the SMO of what to do when the alarm occurs. If the alarm is based on a standard, this could also include the standard-defined descriptions/discussion about the alarm condition. - -Along with Network Functions, O-Cloud resources or deployments may generate an alarm notification which are sent to subscribed consumers. The SMO shall be the primary consumer of these events which may need the ability to correlate them when there is a single root cause for alarms from multiple sources. The dictionary definition provides extensibility where such end-to-end type of signatures may be described. - -Not all alarms definitions are standardized and therefore the alarm dictionary should be structured to allow a resource and/or application vendors to specify their unique alarms while also supporting alarms which are defined by a standard. - -###### 5.2.1.4.10.2 Attributes - -The AlarmDictionary includes attributes inherited from Top\_ [2] and the following attributes: - -| Attribute name | S | isReadable | isWritable | isInvariant | isNotifyable | -|------------------------------|---|------------|------------|-------------|--------------| -| alarmDictionaryId | M | T | F | T | F | -| alarmDictionaryVersion | M | T | F | T | F | -| alarmDictionarySchemaVersion | M | T | F | T | F | -| supportedEntityTypes | M | T | F | T | F | -| vendor | M | T | F | T | F | -| supportedProducts | M | T | F | T | F | -| supportedInterfaces | M | T | F | T | F | -| alarmDefinitions | M | T | F | T | F | -| probableCauses | O | T | F | T | F | - -###### 5.2.1.4.10.3 Attribute constraints - -None - -###### 5.2.1.4.10.4 Notifications - -This class does not support any notification. - -###### 5.2.1.4.10.5 State diagram - -None - -##### 5.2.1.4.11 AlarmDictionaryMap <> - -###### 5.2.1.4.11.1 Definition - -The `AlarmDictionaryMap` provides the attributes to map an alarm event record to its corresponding `AlarmDefinition` entry in an `AlarmDictionary`. Alarm event records for a given software product are reported over an interface. A map is required to identify the `AlarmEvent` attribute which correlates to the `alarmDefinitionId` within the dictionary for a given interface. The `AlarmDictionaryMap` identifies the attribute name within an `Alarm` event record, which shall contain the `alarmDefinitionId` value in an `AlarmDictionary`. - -###### 5.2.1.4.11.2 Attributes - -The `AlarmDictionaryMap` defines following attribute: - -| Attribute name | S | isReadable | isWritable | isInvariant | isNotifyable | -|----------------------------------------|---|------------|------------|-------------|--------------| -| eventToAlarmDefinitionMap | M | T | F | T | F | - -###### 5.2.1.4.11.3 Attribute constraints - -None - -###### 5.2.1.4.11.4 Notifications - -This class does not support any notification. - -###### 5.2.1.4.11.5 State diagram - -None. - -##### 5.2.1.4.12 AlarmDefinition <> - -###### 5.2.1.4.12.1 Definition - -The `AlarmDefinition` includes additional static data about an alarm that is not transmitted in the `Alarm` event notification. The data is used by the consumer for alarm planning, automation, troubleshooting or to enrich the infrastructure alarm event notification when received. - -###### 5.2.1.4.12.2 Attributes - -The `AlarmDefinition` inherits attributes from `Top_ [2]` and extends it with the following attributes: - -| Attribute name | S | isReadable | isWritable | isInvariant | isNotifyable | -|--------------------------|----|------------|------------|-------------|--------------| -| alarmDefinitionId | M | T | F | T | F | -| alarmName | M | T | F | T | F | -| alarmLastChange | M | T | F | T | F | -| alarmChangeType | M | T | F | T | F | -| alarmDescription | M | T | F | T | F | -| proposedRepairActions | CO | T | F | T | F | -| proposedRepairActionRefs | CO | T | F | T | F | -| clearingType | M | T | F | T | F | -| standardReference | M | T | F | T | F | -| managementInterfaceId | M | T | F | T | F | -| extensions | M | T | F | T | F | - -###### 5.2.1.4.12.3 Attribute constraints - -| Attribute name | Definition | -|---------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------| -| proposedRepairActions
proposedRepairActionRefs | Each defined alarm requires at least a proposed Repair Action defined by proposedRepairActions or proposedRepairActionRefs. | - -###### 5.2.1.4.12.4 Notifications - -This class does not support any notification. - -###### 5.2.1.4.12.5 State diagram - -None - -##### 5.2.1.4.13 ProbableCauseInfo <> - -###### 5.2.1.4.13.1 Definition - -The ProbableCauseInfo is intended to help operators determine the root cause of an event. - -There are industry suggested lists of probable causes that could be used. When used the ProbableCauseInfo definition should allow for an indication of such a source. - -The ProbableCause(s) used by the vendor for alarm events are listed independently in the alarm dictionary. However, each alarm event should have a Probable Cause that is specific to that alarm instance. - -###### 5.2.1.4.13.2 Attributes - -The ProbableCauseInfo is a structured data type consisting of the following attributes: - -| Attribute name | S | isReadable | isWritable | isInvariant | isNotifyable | -|--------------------------|---|------------|------------|-------------|--------------| -| probableCause | M | T | F | T | F | -| probableCauseDescription | M | T | F | T | F | -| standardReference | M | T | F | T | F | - -###### 5.2.1.4.13.3 Attribute constraints - -None - -###### 5.2.1.4.13.4 Notifications - -This class does not support any notification. - -###### 5.2.1.4.13.5 State diagram - -None. - -##### 5.2.1.4.14 Product <> - -###### 5.2.1.4.14.1 Definition - -The Product identifies a vendor product and its version. - -###### 5.2.1.4.14.2 Attributes - -The Product is a structured data type consisting of the following attributes: - -| Attribute name | S | isReadable | isWritable | isInvariant | isNotifyable | -|----------------|---|------------|------------|-------------|--------------| -| product | M | T | F | T | F | -| version | M | T | F | T | F | - -###### 5.2.1.4.14.3 Attribute constraints - -None - -###### 5.2.1.4.14.4 Notifications - -This class does not support any notification. - -###### 5.2.1.4.14.5 State diagram - -None. - -#### 5.2.1.5 Attribute definitions - -| Attribute Name | Documentation and Allowed Values | Properties | -|-------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------| -| 3GPPPerformanceMeasurementDefinition.collectionMethod | This attribute identifies the collection method for an 3GPP based measurement definition.

allowedValues: as defined in 3GPP TS 32.404 [13] clause 3.3(b). | type: 3GPPCollectionMethod
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| 3GPPPerformanceMeasurementDefinition.description | This attribute contains an explanation of the measurement operation.

allowedValues: as defined in 3GPP TS 32.404 [13] clause 3.3(a). | type: string
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| clause | This attribute identifies the clause in a specification that defines a measurement definition.

allowedValues: N/A. | type: string
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | - -| Attribute Name | Documentation and Allowed Values | Properties | -|-------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| -| condition | This attribute identifies the condition in which the measurement will be updated.

allowedValues: as defined in 3GPP TS 32.404 [13] clause 3.3(c). | type: string
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| ETSIPerformanceMeasurementDefinition.collectionMethod | This attribute identifies the collection method for an ETIS based measurement definition.

allowedValues: as defined in ETSI NFV IFA027 clause 5(b) [14] | type: ETSICollectionMethod
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| ETSIPerformanceMeasurementDefinition.description | This attribute contains the description of the performance measurement.

allowedValues: as defined in ETSI NFV IFA027 clause 5(a) [14] | type: string
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| generation | This attribute identifies the cellular technology generation(s) that a performance measurement definition is applicable to.

allowedValues: as defined in 3GPP TS 32.404 [13] clause 3.3(h). | type: 3GPPGeneration
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| managementInterfaceId | This attribute identified the management interface that a performance measurement definition can be reported on.

allowedValues: As defined in ManagementInterface | type: ENUM ManagementInterface
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| measurementName | This attribute is a descriptive name of the measurement type.

allowedValues: as defined in 3GPP TS 32.404 [13] clause 3.3. | type: string
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| measurementResult | This attribute is a description of expected result value(s).

allowedValues: as defined in 3GPP TS 32.404 [13] clause 3.3(d). | type: string
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| measurementType | This attribute describes a short form of the measurement name specified in the header, which is used to identify the measurement type.

allowedValues: as defined in 3GPP TS 32.404 [13] clause 3.3(e). | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| measurementUnit | This attribute describes the unit of the measurement value.

allowedValues: as defined in ETSI NFV IFA027 clause 5(d) [14] | type:
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| measureObjectClass | This attribute describes the object class.

allowedValues: as defined in 3GPP TS 32.404 [13] clause 3.3(f). | type: string
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | - -| Attribute Name | Documentation and Allowed Values | Properties | -|------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| -| performanceDictionarySchemaVersion | This attribute defines the version of the schema version used to create the measurement definitions.

allowedValues: N/A | type: string
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| performanceDictionaryVersion | This attribute defines the version of the dictionary itself.

allowedValues: N/A | type:
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| PerformanceMeasurementDefinition.supportedInterfaces | This attribute when present this defines the specific subset of interfaces over which the measurement is transmitted and may define an override of the interface key field mapping. If omitted, then the measure is transmitted over all interfaces defined in the dictionary level map.

allowedValues: N/A | type: SupportedInterface
multiplicity: 0..*
isOrdered: True
isUnique: N/A
defaultValue: None
isNullable: True | -| performanceMeasurementDefinitionId | This attribute identifies a single performanceMeasurementDefinition within the dictionary.

allowedValues: N/A | type: string
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| PerformanceMeasureDictionary.supportedInterfaces | This attribute provides the list overwhich the performance measurements will be transmitted over. Not all performance measures are required to be over all supported interfaces.

allowedValues: N/A | type: SupportedInterface
multiplicity: 1..*
isOrdered: True
isUnique: N/A
defaultValue: None
isNullable: False | -| performanceMeasureId | This attribute identifies a single performanceMeasurementDefinition with a numeric value which may be used during serialization over a streaming interface to support data compaction.

allowedValues: unsigned integer | type: Uint
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| eventToDictionaryMap | This attribute is a placeholder for an alternative set of fields based on a choice. This field shall be replaced with those fields identified in the appropriate alternative of the choice. | type:
EventToDictionaryMap
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| eventToMeasureDefinitionMap | This attribute identifies the field attribute in a performance report which shall contain the value to be used as the measureDefinitionID in an PerformanceMeasureDictionary.

AllowedValues: Any attribute name within a performance report. | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| product | This attribute identifies the software product name provided by a vendor.

allowedValues: N/A | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | - -| Attribute Name | Documentation and Allowed Values | Properties | -|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| purpose | This attribute, when supplied, describes who will be using the measurement.

allowedValues: as defined in 3GPP TS 32.404 [13] clause 3.3(i). | type: String
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: True | -| standardReference | This attribute, when provided, identifies a Standard where a performance measure is defined.

allowedValues: N/A | type: StandardReference
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: True | -| standardsDefinitionOrganization | This attribute identifies the Standards definition organization such as but not limited to ETSI or 3GPP.

allowedValues: N/A | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| standardSpecification | This attribute defines the Standard's title which in contains the measurement definition.

allowedValues: N/A. | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| supportedMeasures | This attribute provides the list of measurement definitions contained within a performance dictionary.

allowedValues: N/A | type:
3GPPPerformanceMeasure Definition or
ETSIPerformanceMeasure Definition
multiplicity: 1..*
isOrdered: True
isUnique: N/A
defaultValue: None
isNullable: False | -| supportedProducts | This attribute provides the list of products and their versions that a vendor supports in a dictionary.

allowedValues: N/A | type: Product
multiplicity: 1..*
isOrdered: True
isUnique: True
defaultValue: None
isNullable: False | -| switchingTechnology | This attribute defines the switching domain(s) this measurement is applicable to.

allowedValues: as defined in 3GPP TS 32.404 [13] clause 3.3(g). | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| trigger | This attribute describes the trigger which causes the counter to be updated.

allowedValues: as defined in ETSI NFV IFA027 clause 5(c) [14] | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| vendor | This attribute identifies vendor name of a software product that the specified dictionary is provided for.

allowedValues: as defined in clause 4.4.1 of 3GPP TS 28.622 [2] | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | - -| Attribute Name | Documentation and Allowed Values | Properties | -|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------| -| version | This attribute identifies specific version of a vendor software product that the specified dictionary is provided for.

allowedValues: N/A | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| versionOrRelease | This attribute identifies the specification version, release, or date of publication, that identifies a specific instance of the specification.

allowedValues: N/A | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| alarmChangeType | This indicates the type of last change that occurred during the alarm last change.

allowedValues: As defined by AlarmChangeType | type: ENUM
AlarmChangeType
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| alarmDefinitions | This attribute contains the list of alarm definitions which are or have been supported by the entity type and are ordered ascending by alarmDefinitionId.

allowedValues: N/A | type: AlarmDefinition
multiplicity: 1..*
isOrdered: True
isUnique: N/A
defaultValue: None
isNullable: False | -| alarmDefinitionId | This identifies a specific alarmDefinition instance in the AlarmDictionary. This is the Primary Key into the alarmDefinitions.

NOTE: Multiple values, separated by “.” can be concatenated, according to the order defined by the list in eventToAlarmDefinitionMap

allowedValues: N/A | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| AlarmDefinition.managementInterfaceId | This attribute, defines the specific subset of interfaces over which the alarm is transmitted.

allowedValues: As defined by ManagementInterface | type: ENUM
ManagementInterface
multiplicity: 1..*
isOrdered: False
isUnique: True
defaultValue: None
isNullable: False | -| alarmDescription | This provides a longer descriptive meaning of the alarm condition and a description of the consequences of the alarm condition. This is intended to be read by an operator to give an idea of what happened and a sense of the effects, consequences, and other impacted areas of the system.

allowedValues: N/A | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| AlarmDictionary.supportedInterfaces | This attribute provides the i/f list over which the alarms will be transmitted.

allowedValues: N/A | type: SupportedInterface
multiplicity: 1..*
isOrdered: False
isUnique: True
defaultValue: None
isNullable: False | -| alarmDictionarySchemaVersion | This attribute defines the schema version used to create the dictionary.

allowedValues: N/A | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | - -| Attribute Name | Documentation and Allowed Values | Properties | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| -| alarmDictionaryVersion | This attribute defines the version of the dictionary itself.

allowedValues: N/A | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| alarmLastChange | This defines the date and time of the last change to an alarm definition.

allowedValues: N/A | type: DateTime
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| alarmName | This describes the human readable name of the alarm.

allowedValues: N/A | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| clearingType | This Indicates the type of clearing that is supported by a defined alarm.

allowedValues: As defined by AlarmClearingType. | type: ENUM
AlarmClearingType
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | -| supportedEntityTypes | This attribute identifies the list of the type of entities that can generate alarms.

Allowed values are not limited in order to allow for extensibility of the O-Cloud Resource Types. | type: string
multiplicity: 0..*
isOrdered: False
isUnique: True
defaultValue: None
isNullable: True | -| eventToAlarmDefinitionMap | This attribute identifies the attribute(s) in an alarm event which contain the value(s) to be used as the alarmDefinitionID in an AlarmDictionary (e.g. for O2 i/f, the O2 alarmDefinitionId as defined in ORAN WG6 [i.40], for M-plane i/f, the M-plane faultID as defined in ORAN WG4 [i.1], for O1 i/f, the O1 alarmType, probableCause and optionally specificProblem as defined in O-RAN WG10 [8]).

NOTE: The attribute order in the list defines the value order in the alarmDefinitionID attribute | type: String
multiplicity: 1..*
isOrdered: False
isUnique: True
defaultValue: None
isNullable: False | -| extensions | This attribute provides a list of key value pairs denoting extended attributes of the Information Object Class (e.g. vendor specific values per standard attribute(s) of an alarm event record)

allowedValues: N/A | type: NameValuePair
multiplicity: 0..*
isOrdered: False
isUnique: True
defaultValue: None
isNullable: True | -| probableCause | This identifies a specific probableCause instance in the AlarmDictionary. This is the Primary Key into the ProbableCauseInfo dataType.

allowedValues: for WG10 O1 Alarms as defined in 3GPP TS 28.111[16], clause 7.4 and for WG6 O-Cloud Alarms as defined in O-RAN.WG6.TS.O2IMS-INTERFACE [12], clause 4.

NOTE: allowedValues can be extended for vendor-specific alarms. | type: String or Integer
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False | - -| Attribute Name | Documentation and Allowed Values | Properties | -|--------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| -| probableCauseDescription | This provides any additional information beyond the probableCause to describe the probable cause | type: String
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: True | -| probableCauses | This attribute contains the list of probable causes which may be referenced in an alarm definition.

allowedValues: N/A | type: ProbableCauseInfo
multiplicity: 0..*
isOrdered: False
isUnique: True
defaultValue: None
isNullable: True | -| proposedRepairActions | This identifies one or more proposed actions for the defined alarm.
allowedValues: N/A | type: String
multiplicity: 0..*
isOrdered: False
isUnique: True
defaultValue: None
isNullable: True | -| alarmDictionaryId | This attribute serves as the identifier of an AlarmDictionary.

allowedValues:N/A | type: String
multiplicity: 1
isOrdered: False
isUnique: True
defaultValue: None
isNullable: False | -| performanceDictionaryId | This attribute serves as the identifier of a PerformanceMeasureDictionary.

allowedValues:N/A | type: String
multiplicity: 1
isOrdered: False
isUnique: True
defaultValue: None
isNullable: False | -| proposedRepairActionRefs | This identifies one or more proposed actions by reference for the defined alarm. It provides the possibility to refer to an external document(s), where it is possible to provide more long, complex and structured definition of repair action(s)

allowedValues: N/A | type: String
multiplicity: 0..*
isOrdered: False
isUnique: True
defaultValue: None
isNullable: True | - -# 6 O-RAN Data Models - -## 6.1 Formal relationship (traceability) between O-RAN Data Models and the O-RAN Information Model - -O-RAN Information Model development should precede and serve as the basis for the Data Model development. - -As the modeling practices and processes within O-RAN mature, the Information Model and Data Models should co-evolve to develop the APIs required by specific use cases. - -![Figure 6.1-1 Information and Data Modeling Co-Evolution [i.3]. A diagram showing the co-evolution of Info Model, Data Model, and API across five stages. The stages are: 1. High Level Info Requirements / Use Case Proposal / Use Case Proposal; 2. Introduce Info Model / U/C Definition / U/C Definition; 3. Refine Info Model / Refine Data Work / U/C Design; 4. Info Model Freeze Final / Refine Data Model / U/C Design; 5. Tweaks on Info Model / Data Model Freeze / API Approve API Freeze. Vertical lines between stages are labeled M1 Functional, M2 Functional, and M3 Functional.](a149b400127a3e3e50b3c98d27c5935c_img.jpg) - -| Information and Data Modeling Co-Evolution | | | | | | -|--------------------------------------------|------------------------------|----------------------|-------------------|-------------------------|------------------------| -| INFO MODEL | High Level Info Requirements | Introduce Info Model | Refine Info Model | Info Model Freeze Final | Tweaks on Info Model | -| | Model Planning | Input model | Discussion Model | Clean Model | Updates from WG, UCTG | -| DATA MODEL | Use Case Proposal | U/C Definition | Refine Data Work | Refine Data Model | Data Model Freeze | -| | | | Input Data Model | Discussion Data Model | Clean Data Model | -| API | Use Case Proposal | U/C Definition | U/C Design | U/C Design | API Approve API Freeze | -| | | | | | Preliminary API API | - -Figure 6.1-1 Information and Data Modeling Co-Evolution [i.3]. A diagram showing the co-evolution of Info Model, Data Model, and API across five stages. The stages are: 1. High Level Info Requirements / Use Case Proposal / Use Case Proposal; 2. Introduce Info Model / U/C Definition / U/C Definition; 3. Refine Info Model / Refine Data Work / U/C Design; 4. Info Model Freeze Final / Refine Data Model / U/C Design; 5. Tweaks on Info Model / Data Model Freeze / API Approve API Freeze. Vertical lines between stages are labeled M1 Functional, M2 Functional, and M3 Functional. - -Figure 6.1-1 Information and Data Modeling Co-Evolution [i.3] - -## 6.2 YANG Conventions - -### 6.2.1 General - -This clause describes the recommended conventions to be used in the O-RAN Alliance when writing YANG models. - -In particular, because the creation and maintenance of YANG models is expected to be distributed across different working groups, this guide is intended to ensure that the way the models are organized and presented will be consistent across the entirety of the O-RAN Alliance. - -### 6.2.2 Naming - -**MODULE FILE NAMING:** All YANG modules shall have filenames that are unique within O-RAN. All YANG module filenames shall follow the form defined in clause 5.2 of IETF RFC 7950 [5], except for the revision date that shall not be present. - -**MODULE NAMING:** All YANG module names shall have the form: “--” where: - -- The element is mandatory and shall have the value of “o-ran”. -- The element is optional for YANG modules that have been already published. For new YANG modules the element is mandatory. All YANG modules shall have elements that are unique within O-RAN (e.g., o1). -- The element is used to ensure the name of the YANG module is unique within the or - module name conventions. Additionally in cases where a YANG module is dedicated to one O-RAN entity, the element should contain name of this O-RAN entity, i.e. = “odu-”, - -= “ocu-”. For O-RAN common YANG modules name should follow the form of =“common-”. - -MODULE NAMESPACE: All YANG modules shall have a namespace defined of the form namespace "urn::". - -- The element is mandatory and shall have the value of “o-ran”. -- The element is mandatory and shall follow the module naming rules defined in this document. - -PREFIX NAMING: Each YANG module shall have a prefix statement with a prefix that other dependent modules will use (also used in path references within the same module). YANG module prefixes shall be a maximum of 13 characters. All YANG modules shall have YANG module prefixes that are unique within O-RAN. All YANG module prefixes shall have the form “-[]-[]”. - -- The element is mandatory and shall have the value of “or” for new YANG modules. -- The element is mandatory and may have the value of “o-ran” or “or” for YANG modules that already have been published. -- The element is optional for YANG modules that have been already published. For new YANG modules the element is mandatory. All YANG modules shall have element that are unique within O-RAN (e.g., o1). -- The element is used to ensure the YANG module prefix is unique within the or - YANG module prefix conventions. - -### 6.2.3 Revision Statement - -YANG modules revision shall follow the 3GPP TS 32.160 [7] clause 6.2.1.13 where a YANG module shall contain a revision statement following RFC 7950 [5], section 7.1.9., but the revision statements contents are defined as follows. The revision statement in the YANG modules shall include a description substatement used to track the versioning of the YANG model. A version number shall be in a format X.Y.Z according to SemVer [i.39]. In addition, the revision statement shall also include a reference sub statement used to referred document (e.g. stage 2 Information Model). - -For example: - -``` -revision 2024-07-10 { - description "1.2.0"; - reference "O1NRM"; -} -``` - -### 6.2.4 Indents - -O-RAN Alliance YANG models shall use two-space tab indents. - -### 6.2.5 YANG Language Usage - -YANG VERSION: All models shall use YANG data modeling language version 1.1 (RFC 7950 [5]) - -KEY-LESS LISTS: Although permitted in YANG, the use of a list without a defined key should be avoided. - -VALIDATION: All YANG modules should be validated / compiled with pyang tool using the following flag: pyang --lint . The pyang errors shall be removed and pyang warning should be considered for removal. Note, successful - -compilation with pyang does not guarantee a working model, as xPATH expressions aren't evaluated and forbidden operational data dependencies in the configuration may not generate appropriate errors. - -### 6.2.6 Cross Working Group Co-ordination - -Models that are likely to be applicable to more than one O-RAN Alliance working group should provide clear delineation between separate working groups configuration and/or state. The use of feature and if-feature should be used to ensure that NETCONF servers are not required to implement the entire data model, e.g., when aspects of such relate to the individual working group defined use cases. The feature name should indicate which working group or which O-RAN entity the capabilities have been defined by. - -### 6.2.7 Void - -### 6.2.8 Augmentations of YANG Data Models - -O-RAN shall not modify other SDO modules. - -O-RAN augmentation to the other SDO YANG modules shall be made in separate O-RAN originated YANG Data Model file, as modification of original SDO YANG Data Model file is prohibited. - -Vendor specific augmentation to O-RAN YANG modules shall be made in separate vendor originated YANG Data Model files. - -# --- Annex A (informative): Links to Data Models approved for use - -## From O-RAN - -The public facing web page that includes the formally released versions of models that are approved for use: - -[www.o-ran.org/specifications](http://www.o-ran.org/specifications) - -## From 3GPP - -3GPP is one of the sources for management plane specifications for O-RAN components. 3GPP publishes its “SA5 Data models” including its yang data models in a publicly available git repository: - - - -## From IETF - -IETF is a complementary source for management plane specifications for O-RAN components. IETF publishes its yang data models (inclusive of IANA yang data models) in a publicly available git repository: - - - -# Annex B (informative): Relations between Information Model and Data Models - -## B.1 Information and Data Models as a Modeling Continuum - -Within O-RAN, the de facto methods and procedures with respect to the early stage of an O-RAN “modeling continuum” aim to evolve **one common and coherent Information Model** for providing O-RAN extensions to the existing 4G/5G IMs such as the 3GPP NRMs, from which O-RAN Data Models may be generated. - -![Diagram titled 'Information and Data Models as a Modeling Continuum' showing the relationship between Information Model, Logical Data Model, Data Dictionary, and Component Physical Data Models. The top section contains three boxes: 'Information Model' (with a hierarchy diagram), 'Logical Data Model' (with a block diagram), and 'Data Dictionary' (with a table). Double-headed arrows connect them horizontally. Below this is a box for 'Component Physical Data Models' containing several interlocking gears. A vertical double-headed arrow connects the top section to the bottom section. A callout box on the left points to the top section with the text 'e.g., Yang, VES, etc.'. On the right, an 'Objective:' text states 'Establish and evolve one common and coherent Information Model for 5G/LTE RAN'.](3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg) - -Diagram titled 'Information and Data Models as a Modeling Continuum' showing the relationship between Information Model, Logical Data Model, Data Dictionary, and Component Physical Data Models. The top section contains three boxes: 'Information Model' (with a hierarchy diagram), 'Logical Data Model' (with a block diagram), and 'Data Dictionary' (with a table). Double-headed arrows connect them horizontally. Below this is a box for 'Component Physical Data Models' containing several interlocking gears. A vertical double-headed arrow connects the top section to the bottom section. A callout box on the left points to the top section with the text 'e.g., Yang, VES, etc.'. On the right, an 'Objective:' text states 'Establish and evolve one common and coherent Information Model for 5G/LTE RAN'. - -Figure B.1-1 Information and Data Models as a Modeling Continuum (conceptual) - -## B.2 Information and Data Modeling Co-Evolution - -The “Modeling Continuum” depicted as Figure B.2-1 is purely conceptual and is intended to provide a framework for Information and Data Modeling Co-evolution. - -Here is an example of the process to be adapted to, and adopted by, O-RAN: - -![Information and Data Modeling Co-Evolution diagram showing three parallel tracks: INFO MODEL, DATA MODEL, and API. The INFO MODEL track includes steps: High Level Info Requirements (Model Planning), Introduce Info Model (Input model), Refine Info Model (Discussion Model), Info Model Freeze Final (Clean Model), and Tweaks on Info Model (Updates from WG, UCTG). The DATA MODEL track includes steps: Use Case Proposal, U/C Definition, Refine Data Work (Input Data Model), Refine Data Model (Discussion Data Model), and Data Model Freeze (Clean Data Model). The API track includes steps: Use Case Proposal, U/C Definition, U/C Design, U/C Design, and API Approve API Freeze (Preliminary API API). Vertical lines labeled M1 Function, M2 Function, and M3 Function separate the columns.](14252bcd35912bd656e98b16b2ee51c0_img.jpg) - -Information and Data Modeling Co-Evolution diagram showing three parallel tracks: INFO MODEL, DATA MODEL, and API. The INFO MODEL track includes steps: High Level Info Requirements (Model Planning), Introduce Info Model (Input model), Refine Info Model (Discussion Model), Info Model Freeze Final (Clean Model), and Tweaks on Info Model (Updates from WG, UCTG). The DATA MODEL track includes steps: Use Case Proposal, U/C Definition, Refine Data Work (Input Data Model), Refine Data Model (Discussion Data Model), and Data Model Freeze (Clean Data Model). The API track includes steps: Use Case Proposal, U/C Definition, U/C Design, U/C Design, and API Approve API Freeze (Preliminary API API). Vertical lines labeled M1 Function, M2 Function, and M3 Function separate the columns. - -Figure B.2-1 Information and Data Modeling Co-Evolution [i.3] - -## B.3 Model and Use Case Development (process) - -There is evolving process within O-RAN to guide and inform Information Model and Data Model(s) development based on prioritized use cases. - -Here is example of the process to be adapted to, and adopted by, O-RAN. - -![Model & Use Case Development process diagram showing four horizontal tracks: Milestones, Use Case Timeline, Modeling, and Architecture across five vertical stages: Proposals, Planning, Functionality Define, API Develop S/W Coding, and Integration. Icon: Document with checkmark Icon: Book with checkmark Icon: Gears Icon: Target with checkmark Icon: Checklist with checkmark Icon: Document with checkmark Icon: Circuit board Icon: Target with checkmark Icon: Road sign Icon: Checkmark in circle Icon: Three people talking Icon: Model with checkmark Icon: Checkmark in circle Icon: Circuit board Icon: Circuit board Icon: Document with checkmark](318886a86a1dcc59e1fc83db6f157c60_img.jpg) - -| Model & Use Case Development | | | | | | -|------------------------------|-------------------------|---------------------------------------------------|--------------------------------------------------|---------------------------|--------------------------| -| | Proposals | Planning | Functionality Define | API Develop S/W Coding | Integration | -| MILESTONES |
U/C Proposals |
Definition |
Design, Platform S/W |
API, S/W deliverables |
Test/Integration | -| | U/C Proposal | U/C Definition | U/C Design | U/C Develop | U/C Test | -| USE CASE Timeline |
U/C Proposals |
U/C Definition |
U/C Design |
U/C S/W deliverables |
U/C Test/Integration | -| | Model Discussion | Model Definition | Refine, Approve, Employ Model | - | - | -| MODELING |
Model Planning |
Input model Discussion Model |
Clean Model | | | -| | - | Functional Arch. Def | Arch Approved | API Doc Freeze | - | -| ARCHITECTURE | |
Functional Arch Define Component Architecture |
Architecture Approved Component Architecture |
API Documents Freeze | | - -Model & Use Case Development process diagram showing four horizontal tracks: Milestones, Use Case Timeline, Modeling, and Architecture across five vertical stages: Proposals, Planning, Functionality Define, API Develop S/W Coding, and Integration. Icon: Document with checkmark Icon: Book with checkmark Icon: Gears Icon: Target with checkmark Icon: Checklist with checkmark Icon: Document with checkmark Icon: Circuit board Icon: Target with checkmark Icon: Road sign Icon: Checkmark in circle Icon: Three people talking Icon: Model with checkmark Icon: Checkmark in circle Icon: Circuit board Icon: Circuit board Icon: Document with checkmark - -Figure B.3-1 Model and Use Case Development (process) [i.3] - -# Annex C (informative): Classes/components and interfaces that comprise the O-RAN Information Model and Data Models - -Following are a list of classes/components as well as interfaces that may be part of the O-RAN Information model, along with the working group developing this entity, any SDO references if appropriate, followed by comments and the status. This is based on the premise that each WG is responsible for modeling the entity, and WG10 is responsible for stewarding the overarching model inclusive of the input from the other groups. - -| Entity | WG Developing Model | Doc Reference | Comments | Status | -|--------------------------|---------------------|-------------------------------|-----------------------------------------------|--------| -| Class / Component | | | | | -| NonRTRIC | WG2 | | Not present in model | | -| NearRTRIC | WG3 | | Presently shell only in model. | | -| O-CU-CP | WG5 | O-RAN-WG5.O-CU-O1.0 [i.6] | | | -| O-CU-UP | WG5 | O-RAN-WG5.O-CU-O1.0 [i.6] | | | -| O-DU | WG5 | O-RAN.WG5.O-DU-O1.0 [i.6] | | | -| O-RU | WG4 | | Shell only | | -| ManagedApplication | WG10 | | Abstract Class | | -| ManagedElement | | 3GPP TS 28.622 [2] | Class and attributes | | -| xApp | WG3, (WG6) | | Not present in model | | -| rApp | WG2, (wg6) | | Not present in model | | -| Interfaces | | | | | -| A1-P | WG2 | O-RAN.WG2.A1AP [i.4] | | | -| A1-ML | WG2 | | Shell Only - to be pursued in a later release | | -| A1-EI | WG2 | | Shell Only - to be pursued in a later release | | -| O1 | WG10 | O-RAN.WG10.O1 Interface.0 [8] | | | -| E1 | WG5 | 3GPP TS 38.460 [i.10] | 3GPP start, including operations list | | -| E2 | WG3 | O-RAN.WG3.E2GAP [i.5] | Interface with 9 operations | | -| F1-c | WG5 | 3GPP TS 38.470 [i.11] | 3GPP start, including 24 operations | | - -| | | | | | -|---------------|-----|-------------------------|----------------------------------------------------------|--| -| F1-u | WG5 | 3GPP TS 38.470 [i.11] | 3GPP start, including limited operation list | | -| OpenFrontHaul | WG4 | O-RAN.WG4.TS.MP.0 [i.1] | Shell only | | -| X2 | WG5 | 3GPP TS 36.423 [i.9] | 3GPP based start, including a large number of operations | | -| O2 | WG6 | | Not present in model | | -| R1 | WG2 | | Not present in model | | - -**Table C-1** Classes/components and interfaces that comprise the O-RAN Information Model and Data Model(s) - -# Annex D (informative): Usage of models - -## D.1 Usage of 3GPP Data Models - -The O-RAN Alliance complements the work of other SDOs. 3GPP is the primary source for management plane specifications for O-RAN components. - -Please refer to Annex A for the 3GPP-source Data Models that are approved for use. - -The following table (snapshot) shows a subset of the 3GPP yang data models to an O-RAN model construct. - -| 3GPP yang data model | 3GPP spec for YANG model | o-ru
(O1 in hybrid mode currently not supported) | o-du | o-cu-up | o-cu-cp | near-rt-ric | -|-------------------------------|--------------------------|-----------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| -| _3gpp-5g-common-yang-types | 3GPP TS 28.541 [i.37] | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8]) | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8]) | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8]) | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8]) | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8]) | -| _3gpp-common-ep-rp | 3GPP TS 28.623 [i.8] | [open] o-ran-m-int.yang & o-ran-ru-itf.yang defines the interface of O-RU, maybe it is not needed to O-RU | imported by _3gpp-nr-nrm-ep (3GPP TS 28.541 [i.37])

abstract superclass for all 3GPP endpoints

[open] as O-RU remote PORT, to configure eCPRI port of O-DU just EP_RP looks not enough | imported by _3gpp-nr-nrm-ep (3GPP TS 28.541 [i.37])

abstract superclass for all 3GPP endpoints | imported by _3gpp-nr-nrm-ep (3GPP TS 28.541 [i.37])

abstract superclass for all 3GPP endpoints | [open] need discussion , if RIC modeled as O-RU which need detailed configuration to interfaces, the common part probably from IETF | -| _3gpp-common-fm | 3GPP TS 28.623 [i.8] | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8])

needed for alarm list handling | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8])

needed for alarm list handling | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8])

needed for alarm list handling | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8])

needed for alarm list handling | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8])

needed for alarm list handling | -| _3gpp-common-managed-element | 3GPP TS 28.623 [i.8] | root object class | root object class | root object class | root object class | root object class | -| _3gpp-common-managed-function | 3GPP TS 28.623 [i.8] | needed to extend MF for O-RU functionality | imported by _3gpp-nr-nrm-gnbdufunction (3GPP TS 28.541 [i.37]) | imported by _3gpp-nr-nrm-gnbcuupfunction (3GPP TS 28.541 [i.37]) | imported by _3gpp-nr-nrm-gnbcuCPfunction (3GPP TS 28.541 [i.37]) | needed either for a standalone RIC or combined RIC ME | - -| | | | | | | | -|-----------------------------------|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| _3gpp-common-measurements | 3GPP TS 28.623 [i.8] | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8])

needed for PM job control and threshold monitoring | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8])

needed for PM job control and threshold monitoring | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8])

needed for PM job control and threshold monitoring | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8])

needed for PM job control and threshold monitoring | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8])

needed for PM job control and threshold monitoring | -| _3gpp-common-subnetwork | 3GPP TS 28.623 [i.8] | imported by _3gpp-common-subscription-control (3GPP TS 28.623 [i.8])

not needed from O-RAN point of view but can't be removed with modification of the yang, Contribution to 3GPP required | imported by _3gpp-common-subscription-control (3GPP TS 28.623 [i.8])

not needed from O-RAN point of view but can't be removed with modification of the yang, Contribution to 3GPP required | imported by _3gpp-common-subscription-control (3GPP TS 28.623 [i.8])

not needed from O-RAN point of view but can't be removed with modification of the yang, Contribution to 3GPP required | imported by _3gpp-common-subscription-control (3GPP TS 28.623 [i.8])

not needed from O-RAN point of view but can't be removed with modification of the yang, Contribution to 3GPP required | imported by _3gpp-common-subscription-control (3GPP TS 28.623 [i.8])

not needed from O-RAN point of view but can't be removed with modification of the yang, Contribution to 3GPP required | -| _3gpp-common-subscription-control | 3GPP TS 28.623 [i.8] | needed for VES subscription | needed for VES subscription | needed for VES subscription | needed for VES subscription | needed for VES subscription | -| _3gpp-common-top | 3GPP TS 28.623 [i.8] | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8])

abstract class supplying a naming attribute | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8])

abstract class supplying a naming attribute | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8])

abstract class supplying a naming attribute | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8])

abstract class supplying a naming attribute | imported by _3gpp-common-managed-element (3GPP TS 28.623 [i.8])

abstract class supplying a naming attribute | -| _3gpp-common-yang-extensions | 3GPP TS 28.623 [i.8] | expected for inVariant | expected for inVariant | expected for inVariant | expected for inVariant | expected for inVariant | -| _3gpp-common-yang-types | 3GPP TS 28.623 [i.8] | imported by many other 3GPP yang modules

essential 3GPP typedefs, in particular DistinguishedName, and other useful typedefs like OperationalState, AdministrativeState, AvailabilityStatus | imported by many other 3GPP yang modules

essential 3GPP typedefs, in particular DistinguishedName, and other useful typedefs like OperationalState, AdministrativeState, AvailabilityStatus | imported by many other 3GPP yang modules

essential 3GPP typedefs, in particular DistinguishedName, and other useful typedefs like OperationalState, AdministrativeState, AvailabilityStatus | imported by many other 3GPP yang modules

essential 3GPP typedefs, in particular DistinguishedName, and other useful typedefs like OperationalState, AdministrativeState, AvailabilityStatus | imported by many other 3GPP yang modules

essential 3GPP typedefs, in particular DistinguishedName, and other useful typedefs like OperationalState, AdministrativeState, AvailabilityStatus | - -Table D.1-2 Mapping of 3GPP yang data models to O-RAN element functions - -## D.2 Usage of non-3GPP data models - -There are domains of data-models being considered by O-RAN WGs (Working Groups) that are not covered by 3GPP but are covered by other SDOs, e.g., IETF, MEF, IEEE, ONF, BBF, and occasionally imported by 3GPP. - -The following table shows data models that are of interest and being considered within O-RAN and/or 3GPP. - -| Order No | yang data model | Specification | o-ru (M-Plane) | o-du | o-cu-up | o-cu-cp | near-rt-ric | Comments | -|----------|-------------------------|-----------------|-----------------------------|---------------------------------------------------------------|---------------------------------------------------------------|---------------------------------------------------------------|---------------------------------------------------------------|--------------------------------------------| -| 001 | ietf-yang-types | RFC 6991 [i.18] | import by several models | import by _3gpp-common-yang-types.yang (3GPP TS 28.623 [i.8]) | import by _3gpp-common-yang-types.yang (3GPP TS 28.623 [i.8]) | import by _3gpp-common-yang-types.yang (3GPP TS 28.623 [i.8]) | import by _3gpp-common-yang-types.yang (3GPP TS 28.623 [i.8]) | | -| 002 | ietf-inet-types | RFC 6991 [i.18] | import by several models | import by _3gpp-common-yang-types.yang (3GPP TS 28.623 [i.8]) | import by _3gpp-common-yang-types.yang (3GPP TS 28.623 [i.8]) | import by _3gpp-common-yang-types.yang (3GPP TS 28.623 [i.8]) | import by _3gpp-common-yang-types.yang (3GPP TS 28.623 [i.8]) | | -| 011 | ietf-netconf.yang | RFC6241 [i.2] | Used | used | used | used | used | | -| 012 | ietf-netconf-acm.yang | RFC8341 [i.24] | baseline for access control | | | | | Network Configuration Access Control Model | -| 013 | ietf-netconf-monitoring | RFC6022 [i.14] | used | | | | | NETCONF Monitoring Module | - -| | | | | | | | | | -|-----|----------------------------|----------------|------|----------------------------------------------------------|--|--|--|-----------------------------------------------------------------------------------------------------------------------------------------------------------| -| 014 | ietf-netconf-nmda | RFC8526 [i.31] | | | | | | NETCONF operations to support the Network Management Datastore Architecture | -| 015 | ietf-netconf-notifications | RFC6470 [i.16] | used | not O1 but OpenFronthaul mPlane, O-RAN.WG4.TS.MP.0 [i.1] | | | | This module defines a YANG data model for use with the NETCONF protocol that allows the NETCONF client to receive common NETCONF base event notifications | -| 016 | ietf-netconf-partial-lock | RFC5717 [i.13] | | | | | | | -| 017 | ietf-netconf-time | RFC7758 [i.21] | | | | | | time-triggered configuration and management operations | -| 018 | ietf-netconf-with-defaults | RFC6243 [i.15] | | | | | | NETCONF client to control how default values are handled by the server in particular NETCONF operations | - -| | | | | | | | | | -|-----|---------------------|----------------|----------------------------------------------------------------------|----------------------------------------------------------|--|--|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 020 | ietf-system | RFC7317 [i.20] | overlaps with o-ran-operations but may be required to support 802.1X | | | | | configuration and identification of some common system properties within a device containing a NETCONF server
  • time-zone management
  • radius
  • local users
  • NTP
| -| 030 | ietf-hardware | RFC8348 [i.28] | used | not O1 but OpenFronthaul mPlane, O-RAN.WG4.TS.MP.0 [i.1] | | | | | -| 031 | iana-hardware | RFC8348 [i.28] | import by ietf-hardware | import by ietf-hardware | | | | IANA-defined identities for hardware class. | -| 032 | ietf-hardware-state | RFC8348 [i.28] | | | | | | hardware monitoring | -| 033 | ietf-interfaces | RFC8343 [i.26] | foundation for fronthaul | | | | | | -| 034 | iana-if-type | RFC7224 [i.19] | used | not O1 but OpenFronthaul mPlane, O-RAN.WG4.TS.MP.0 [i.1] | | | | YANG identities for IANA-registered interface types | - -| | | | | | | | | | -|-----|--------------------|----------------|-----------------------------------------------------------|--|--|--|--|---------------------------------------------------------------------------------------------------------------| -| 040 | ietf-alarms | RFC8632 [i.34] | | | | | | This module defines an interface for managing alarms. | -| | ietf-ip | RFC8344 [i.27] | foundation for fronthaul M-Plane, O-RAN.WG4.TS.MP.0 [i.1] | | | | | managing IP implementations | -| | ietf-ptp | RFC8575 [i.33] | considered - but decided to define ownno-ran-sync.yang | | | | | configuration of IEEE Std 1588-2008 clocks | -| | ietf-yang-library | RFC8525 [i.30] | foundation for YANG 1.1 (RFC 7950 [5]) | | | | | | -| | ietf-yang-metadata | RFC7952 [i.22] | | | | | | This YANG module defines an 'extension' statement that allows for defining metadata annotations | -| | ietf-yang-patch | RFC8072 [i.23] | | | | | | This module contains conceptual YANG specifications for the YANG Patch and YANG Patch Status data structures. | -| | ietf-yang-push | RFC8641 [i.35] | | | | | | | - -| | | | | | | | | | -|--|------------------------|----------------------------------------|-----------------------------------|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------------| -| | ietf-yang-schema-mount | RFC8528 [i.32] | | | | | | This module defines a YANG extension statement that can be used to incorporate data models defined in other YANG modules in a module. | -| | ietf-yang-smiv2 | RFC6643 [i.17] | | | | | | This module defines YANG extensions that are used to translate SMiv2 concepts into YANG. | -| | iana-crypt-hash | RFC7317 [i.20] | used in CTI | | | | | | -| | ietf-crypto-types | draft-ietf-netconf-crypto-types [i.36] | used by fronthaul file management | | | | | | -| | ieee802-dot1x | IEEE 802.1X-2020 [i.12] | being considered by STG | | | | | | - -Table D.2-3 Non 3GPP yang models - -# Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2020.11.25 | 01.00 | First draft of O-RAN Information Model and Data Models | -| 2021.11.19 | 02.00 | Extension of YANG style guide with respect to O1 (3GPP) aligned models creation.
Alignment of the document to respect the fact that it is owned by WG10.
Addition of a link to WG10 repository
Further editorial fixes. | -| 2022.03.30 | 03.00 | Editorial corrections
References updates
Papyrus installation description update
Abbreviations update | -| 2022.11.09 | 04.00 | Guidance on how to create IMs provided
Introduction of Managed Application IOC IM
Removal of Anex ZZZ
Updated copyright statement
Updated references | -| 2023.03.27 | 05.00 | Performance Dictionary IM for O2 IMS provided
Fault Dictionary IM for O2 IMS provided
Alignment of descriptive text with OAM Architecture
Removal of Papyrus installation clause
Cleanup of text | -| 2023.07.17 | 06.00 | References cleanup
Clause renumbering
Figures renumbering
3GPP references update | -| 2023.10.30 | 07.00 | ETSI PAS Alignment cleanup
References Update | -| 2024.07.26 | 09.00 | Terms clause update
- Removal of "Logical Data Model"
- Removal of "Component Physical Data Models"
- Addition of "Namespace"
Model definitions update in clause 3.1
Namespace definition update
Removing of O1 related NRMs from model
Namespaces introduction

Editorial fixes | - -| | | | -|------------|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2024.12.06 | 10.00 |

Attributes performanceDictionaryId and alarmDictionaryId added
Section 6.2.2 Naming:
- Update naming conventions to recommendations.
- Add prefix naming convention that includes the short interface name.
Change 3GPP references to Rel 18.

Editorial fixes

| -| 2025.03.10 | 11.00 |

Dictionary Support for multiple vendor products
Improve mapping rule from Stage 2 to Stage 3

| -| 2025.07.21 | 12.00 |

Implemented CRs:
- ERI-2025.03.25-O-RAN-CR-0162-ProposedRepairActionRefs-v03
- ERI-2025.04.01-O-RAN-CR-0163-AlarmDef-v04

Editorial fixes

Alignment with new TS template

| -| 2025.11.24 | 13.00 |

Implemented CR:
- DCM-2025.09.01-WG10-CR-0030-Correction for probableCause attribute description-v02
- NOK-2024.09.23.WG10-CR-0096 Dictionary attributes update-v01

Figures numbers fixes
Further editorial fixes

| \ No newline at end of file diff --git a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 7660273fd6752b973145ab5665b854aa1131dde7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:78d8bf66638de64ba661ec10f947a99453a76dbd6d4c840306534c902f5a0dad -size 4570 diff --git a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/08441fa90c5fd11994626f662ac13f19_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/08441fa90c5fd11994626f662ac13f19_img.jpg deleted file mode 100644 index 1a7f4f00954d84cacbc95d5371030e95f45f3cef..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/08441fa90c5fd11994626f662ac13f19_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:be6b02739a512db93d756511bd6fdfcea9fb2180f0642f875e1666ac357eb33d -size 22817 diff --git a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/08783c875dd39684fee7f2a40b584c64_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg deleted file mode 100644 index 11c6e49b95ac778e1af30e535a5ccd068c3808c6..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b4114bd1f51724c05322f28cda9fe1637edd04c6e8029a3800692cea26d92d1f -size 106301 diff --git a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/1439cb942d9e363bbb3161b5540dd8c6_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/1439cb942d9e363bbb3161b5540dd8c6_img.jpg deleted file mode 100644 index 14fa68039ea923b851a948397d72cd8f98a96f87..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/1439cb942d9e363bbb3161b5540dd8c6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ab9b9bb4dda21ac31d90809099a4fc685a4d3735ad99e468c11e6e477db159ce -size 51258 diff --git a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 7660273fd6752b973145ab5665b854aa1131dde7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:78d8bf66638de64ba661ec10f947a99453a76dbd6d4c840306534c902f5a0dad -size 4570 diff --git a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/226f5e462c99b71e08dc9abaa5ae260c_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/253600420ae7bd7d0119563b895cbf8a_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 7660273fd6752b973145ab5665b854aa1131dde7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:78d8bf66638de64ba661ec10f947a99453a76dbd6d4c840306534c902f5a0dad -size 4570 diff --git a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg deleted file mode 100644 index d6a68ae4b197642455d63d06b8c07d6d0ccafea1..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:359b47ebbf43cdcfc8a0ae4786d55f05789b530fd830801fd0a0d1fc0458bc6a -size 4589 diff --git a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg deleted file mode 100644 index 6a204ce5d6ebb86ce09738f0ef731cb36ebead74..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8a68388c6fac815e7d351634374908eef847adcda9ba5fdd0f0796e76f88c87d -size 117795 diff --git a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/38222c3ae003223a67635bfcc6950fbb_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg deleted file mode 100644 index 450638ca42bb3a329d4ee0b07f127bf5b0c7b706..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/3cc095fb84e92690c9d49d3e17c0f1dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d29ee7e13d726241662412e738fb1663bf6c555532d3e8b34c7452d3b82fcafc -size 88881 diff --git a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/4a04896dfb569893fba50729314024f5_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/59fcc0e3699f239444841881a2e75da0_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/5ae3023386ee15fae372871afce28865_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/7f1fc760c873afb92a65f08769a2ed85_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/7f4320cee12fc1dbb865cc6b67462a91_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/81b34087cd6755a80f84a70cf28fba82_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/83ee9f10bd3636e192d68decf7f04cec_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/8447c5519e85d7a9e029fbf321da4c4f_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/854df8ad60507803253274673f9062cf_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/89100a6476d1d96f22c192db16502fec_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/8dcca7651accff77ce832523fe2c7e64_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index c7a86c900497d4e6661fb20f205731af20cfa8b6..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6e2930dff6c3f1befb474551e72059daeca89c2dd76bab1ff3df266d840e00a4 -size 4559 diff --git a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg deleted file mode 100644 index 32b636e01f19e443c4a5915b6430ff336bef5a14..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5be591a08200b638123f3fae793dcf3068b48e654306866b1e35b411cd94822a -size 112027 diff --git a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/a28ab03366399b5e0a61445bc57e3724_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/a82aef1d2f3f1a527328950e9db947ee_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/d879e5f2c388bb87ee9614f63364dcf0_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg deleted file mode 100644 index 9c0a6747a7d529d7d7495856ca04631fa626c039..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/daa4a6fa7e2ba1954258f86b4928eb32_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8f55f95beb2d94e4df8f9bc9304c2607654a756d74e4c4b3fcadbca1f7420ec9 -size 83485 diff --git a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index 6a69c912b93b852487847aaabc8e3d63616636f7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/e11e3fe4228e889a962514269f5a000b_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/e345315706e3fe633bb6d593246c01bf_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg deleted file mode 100644 index f16b010129224a2db698dc250e7663741155376d..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7092bd8e16604540e00eade20768a13d9a540f9a519e8469b44932739344e4af -size 181271 diff --git a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.Information Model and Data Models.0-R005-v13.00/images/f7dbd497160f02888f34fdf243648aa2_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/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/doc.md b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/doc.md deleted file mode 100644 index 272daa0d145d684524e3e70668852320325aa4c4..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/doc.md +++ /dev/null @@ -1,2900 +0,0 @@ - - -# --- O-RAN Work Group 10 (OAM for O-RAN) **O-RAN O1 Interface 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., 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 ..... | 7 | -| 3.3 Abbreviations..... | 7 | -| 4 General Requirements ..... | 9 | -| 4.1 Void ..... | 9 | -| 4.2 Void ..... | 9 | -| 4.3 HyperText Transfer Protocol (HTTP)..... | 9 | -| 4.4 Void ..... | 9 | -| 4.5 Void ..... | 9 | -| 4.6 Void ..... | 9 | -| 4.7 File Transfer Protocol (SFTP, FTPeS or HTTPS) ..... | 9 | -| 4.8 Security ..... | 9 | -| 5 O1 Notifications ..... | 10 | -| 5.1 General..... | 10 | -| 5.2 O-RAN Defined O1 Notification..... | 11 | -| 5.2.1 Requirements..... | 11 | -| 5.2.2 stdnDefinedNamespace name space for O-RAN ..... | 11 | -| 6 Management Services ..... | 12 | -| 6.1 Provisioning Management Services..... | 12 | -| 6.1.0 Overview ..... | 12 | -| 6.1.1 General NETCONF Requirements..... | 12 | -| 6.1.2 Create Managed Object Instance..... | 13 | -| 6.1.3 Modify Managed Object Instance Attributes ..... | 14 | -| 6.1.4 Delete Managed Object Instance..... | 15 | -| 6.1.5 Read Managed Object Instance Attributes ..... | 16 | -| 6.1.6 Notify Managed Object Instance Changes ..... | 17 | -| 6.1.7 Subscription Control ..... | 18 | -| 6.1.8 NETCONF Session Establishment..... | 19 | -| 6.1.9 NETCONF Session Termination..... | 20 | -| 6.1.10 Lock Data Store..... | 21 | -| 6.1.11 Unlock Data Store ..... | 21 | -| 6.1.12 Commit..... | 22 | -| 6.1.13 Notify Event ..... | 23 | -| 6.2 Fault Supervision Management Services ..... | 24 | -| 6.2.0 Overview ..... | 24 | -| 6.2.1 Fault Notification ..... | 24 | -| 6.2.2 Fault Supervision Control ..... | 25 | -| 6.2.3 Fault History Supervision Control and Reporting..... | 26 | -| 6.3 Performance Assurance Management Services ..... | 27 | -| 6.3.0 Overview ..... | 27 | -| 6.3.1 Performance Data File Reporting..... | 27 | - -6.3.2 Performance Data Streaming..... 33 - -6.3.3 Measurement Job Control ..... 35 - -6.3.4 O-RAN Defined Performance Measurements..... 36 - -6.4 Trace Management Services ..... 36 - -6.4.0 Overview..... 36 - -6.4.1 Call Trace ..... 37 - -6.4.2 Minimization of Drive Testing (MDT) ..... 39 - -6.4.3 Radio Link Failure (RLF) ..... 39 - -6.4.4 RRC Connection Establishment Failure (RCEF) ..... 40 - -6.4.5 Trace Control ..... 40 - -6.4.6 Streaming Trace ..... 41 - -6.4.7 UE Identifiers for Trace Records ..... 42 - -6.5 File Management Services..... 42 - -6.5.0 Overview ..... 42 - -6.5.1 File Ready Notification ..... 42 - -6.5.2 List Available Files ..... 44 - -6.5.3 File Transfer to and from File Management MnS Producer..... 45 - -6.5.4 Download File from remote file server ..... 46 - -6.5.5 Void..... 47 - -6.6 Heartbeat Management Capability ..... 48 - -6.6.0 Overview ..... 48 - -6.6.1 Heartbeat Notification ..... 48 - -6.6.2 Heartbeat Control ..... 48 - -6.7 Registration Management capability ..... 49 - -6.7.0 Overview ..... 49 - -6.7.1 PNF Plug-n-Connect ..... 49 - -6.7.2 O1 Registration ..... 49 - -6.8 PNF Software Management Services ..... 55 - -6.8.0 Overview ..... 55 - -6.8.1 Software Package Naming and Content ..... 55 - -6.8.2 Software Inventory ..... 56 - -6.8.3 Software Download..... 57 - -6.8.4 Software Activation Pre-Check..... 59 - -6.8.5 Software Activate..... 60 - -6.9 PNF Reset Management Services..... 62 - -6.9.0 Overview ..... 62 - -6.9.1 PNF Reset Command ..... 62 - -6.9.2 Notifications ..... 65 - -6.10 Void ..... 65 - -Annex A: Void ..... 66 - -Annex B: (informative) Guidelines and Example for stdnDefined VES Events..... 67 - -B.1: Guidelines for use of stdnDefined VES for sending 3GPP-specified or O-RAN-specified O1 notifications ..... 67 - -B.2: Example stdnDefined VES event for a new alarm notification ..... 68 - -Annex C: (informative) Streaming Trace Management Activation Example ..... 70 - -Annex D: (normative) Recommendation for UE Identifier Format in Trace Header ..... 74 - -Annex (informative): Change History ..... 75 - -# --- Foreword - -This Technical Specification (TS) has been produced by WG10 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 - -The O-RAN O1 management services follow existing 3GPP standards wherever possible. The focus of the present document is to identify the use cases which conform to existing 3GPP standards, identify gaps in management services for O-RAN and define needed extensions. For identified gaps, the goal is to modify the 3GPP standards to include the needed O-RAN extensions and update the references in the present document as the 3GPP standards evolve to cover the gaps. In cases where the 3GPP standards are not modified, O-RAN extensions are specified in this, and other, O-RAN documents. O-RAN extensions are compatible with 3GPP standards as much as possible to avoid divergence. If extensions and gaps are not specified, it is expected that the management services producers and consumers are conforming to referenced 3GPP specifications. - -This O1 Interface Specification specifies the management services (MnS) supported in the O-RAN architecture between O1 compliant Managed Elements (MnS producers) and the SMO (MnS consumer). It defines common MnS descriptions, requirements, procedures, operations, and notifications. O-RAN end-to-end OAM use cases and OAM architectural principles are specified in O-RAN TS O-RAN Operations and Maintenance Architecture [i.13]. - -# 1 Scope - -The present document defines O-RAN OAM interface services and protocols for the O-RAN O1 interface. The present document studies the services conveyed over the interface, including management services, procedures, operations, and corresponding solutions, and identifies existing standards and industry work that can serve as a basis for O-RAN work. - -# 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 3GPP 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 28.314: "Management and orchestration; Plug and Connect; Concepts and requirements". -- [2] 3GPP TS 28.315: "Management and orchestration; Plug and Connect; Procedure flows". -- [3] 3GPP TS 28.532: "Management and orchestration; Generic management services". -- [4] 3GPP TS 28.537: "Management and orchestration; Management capabilities". -- [5] Void -- [6] 3GPP TS 28.550: "Management and orchestration; Performance assurance". -- [7] 3GPP TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)". -- [8] 3GPP TS 32.341: "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Requirements". -- [9] 3GPP TS 32.342: "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Information Service (IS)". -- [10] Void -- [11] 3GPP TS 32.421: "Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements". -- [12] 3GPP TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management". -- [13] 3GPP TS 32.423: "Telecommunication management; Subscriber and equipment trace; Trace data definition and management". -- [14] 3GPP TS 32.432: "Telecommunication management; Performance measurement; File format definition". -- [15] O-RAN.WG1.TS.OAD: "O-RAN Architecture Description". -- [16] Void - -- [17] O-RAN.WG11.TS.SRCS.0: "O-RAN Security Requirements and Controls Specifications". -- [18] ONAP VES Event Listener Specification v7.2.1, January 16, 2021. -- [19] RFC 6022, "YANG Module for NETCONF Monitoring", IETF, October 2010. -- [20] RFC 6241, "Network Configuration Protocol (NETCONF)", IETF, June 2011. -- [21] RFC 7950, "The YANG 1.1 Data Modeling Language", IETF, August 2016. -- [22] RFC 7951, "JSON Encoding of Data Modeled with YANG", IETF, August 2016. -- [23] 3GPP TS 28.623: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions". -- [24] RFC 6243, "With-defaults Capability for NETCONF", IETF, June 2011. -- [25] 3GPP TS 28.632: "Telecommunication management; Inventory Management (IM) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)". -- [26] 3GPP TS 28.111: "Management and orchestration; Fault Management (FM)". - -## 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 3GPP 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 TS 28.316: "Management and orchestration; Plug and Connect; Data formats". -- [i.3] 3GPP TS 28.531: "Management and orchestration; Provisioning". -- [i.4] 3GPP TS 28.533: "Management and orchestration: Architecture framework". -- [i.5] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements". -- [i.6] Void -- [i.7] Void -- [i.8] 3GPP TS 32.346: "Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Solution Set (SS) definitions". -- [i.9] 3GPP TS 37.320: "Universal Terrestrial Radio Access (UTRA), Evolved Universal Terrestrial Radio Access (E-UTRA) and Next Generation Radio Access; Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2". -- [i.10] Void -- [i.11] Void -- [i.12] Void -- [i.13] O-RAN.WG10.TS.OAM-Architecture: "O-RAN Operations and Maintenance Architecture". - -- [i.14] O-RAN.WG10.TS.Information Model and Data Models.0: "O-RAN Information Model and Data Models Specification". -- [i.15] 3GPP TS 32.158: "Management and orchestration; Design rules for REpresentational State Transfer (REST) Solution Sets (SS)". -- [i.16] O-RAN.WG10.TS.O1NRM.0: "O1 Network Resource Model ". -- [i.17] O-RAN.WG10.TS.O1PMeas: "O-RAN O1 Performance Measurements Specification". -- [i.18] Void -- [i.19] O-RAN.WG5.O-DU-O1: "O1 Interface specification for O-DU". -- [i.20] O-RAN.WG5.O-CU-O1: "O1 Interface specification for O-CU-UP and O-CU-CP". -- [i.21] 3GPP TS 32.156: "Telecommunication management; Fixed Mobile Convergence (FMC) model repertoire". -- [i.22] O-RAN.WG6.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 the following apply. - -NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [i.1]. - -**NF Deployment:** Refer to O-RAN WG6.ORCH-USE-CASES, Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN [i.22], clause 1.2.1 - -## 3.2 Symbols - -For the purposes of the present document, the symbols given in 3GPP TR 21.905 [i.1] apply. - -NOTE: A symbol defined in the present document takes precedence over the definition of the same symbol, if any, in 3GPP TR 21.905 [i.1]. - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [i.1] and the following apply. - -NOTE 1: 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]. - -| | | -|-------|------------------------------------------------| -| 3GPP | 3 rd Generation Partnership Project | -| ASN.1 | Abstract Syntax Notation One | -| CM | Configuration Management | -| CRUD | Create, Read, Update, Delete | -| FS | Fault Supervision | - -| | | -|-------------|--------------------------------------------------------------| -| FTPES | File Transfer Protocol with Explicit SSL/TLS encryption | -| GPB | Google Protocol Buffers | -| HTTP | HyperText Transfer Protocol | -| HTTPS | HTTP Secure | -| ID | IDentifier | -| IETF | Internet Engineering Task Force | -| IOC | Information Object Class | -| IP | Internet Protocol | -| JSON | JavaScript Object Notation | -| MDT | Minimization of Drive Testing | -| ME | Managed Element | -| MF | Managed Function | -| MnS | Management Service | -| MOC | Managed Object Class | -| MOI | Managed Object Instance | -| Near-RT RIC | O-RAN Near Real Time RAN Intelligent Controller | -| NETCONF | NETwork CONFIguration protocol | -| NF | Network Function | -| NGRAN | Next Generation Radio Access Network | -| NMS | Network Management System | -| NR | New Radio | -| NRM | Network Resource Model | -| 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-RAN | Open Radio Access Network | -| O-RU | O-RAN Radio Unit | -| ONAP | Open Network Automation Platform | -| PM | Performance Management or Performance Measurements | -| PNF | Physical Network Function | -| RAN | Radio Access Network | -| RCEF | RRC Connection Establishment Failure | -| REST | REpresentational State Transfer | -| RFC | Request For Comments | -| RLF | Radio Link Failure | -| RRC | Radio Resource Control | -| SA5 | Services & System Aspects Working Group 5 Telecom Management | -| SBMA | Services Based Management Architecture | -| NOTE 2: | See 3GPP TS 28.533 [i.4], clause 4. | -| SDO | Standards Defining Organization | - -| | | -|------|--------------------------------------| -| SMO | Service Management and Orchestration | -| SFTP | SSH File Transfer Protocol | -| SSH | Secure Shell | -| TLS | Transport Layer Security | -| TR | Technical Report | -| TRS | Trace Recording Session | -| TS | Technical Specification | -| UE | User Equipment | -| URI | Uniform Resource Identifier | -| VES | VNF Event Stream | -| VNF | Virtualized Network Function | -| XML | eXtensible Markup Language | - -# --- 4 General Requirements - -## 4.1 Void - -## 4.2 Void - -## 4.3 HyperText Transfer Protocol (HTTP) - -REQ-HTP-FUN-1: Management Service producers and consumers that use HTTP shall support HTTP v1.1 or higher. - -REQ-HTP-FUN-2: Management Service producers and consumers that use HTTP should support HTTP v2.0. - -## 4.4 Void - -## 4.5 Void - -## 4.6 Void - -## 4.7 File Transfer Protocol (SFTP, FTPeS or HTTPS) - -File Transfer shall be performed using a secure file transfer protocol from or to the File Management MnS Producer (SFTP, FTPeS or HTTPS) as defined in clause 7.1.3 of 3GPP TS 28.537 [4]. - -## 4.8 Security - -Security requirements specified in O-RAN Security Requirements and Controls Specifications [17] clause 5.2.2 shall apply. - -# 5 O1 Notifications - -## 5.1 General - -An O1 notification is a JSON encoded asynchronous notification sent from a MnS producer to a MnS consumer over the O1 interface using REST/HTTPS. - -An O1 notification shall be in one of the following formats: - -- SDO O1 format; -- VES O1 format. - -An SDO O1 format notification is an O1 notification formatted as specified by a Standards Defining Organization (SDO). Currently, O1 supports SDO O1 format notifications that are either 3GPP-specified or O-RAN-specified. SDO O1 format notifications are formatted as specified by the SDO and sent without a VES header. - -3GPP-specified O1 notifications are specified in 3GPP TS 28.532 [3] clauses 11 and 12, and in 3GPP TS 28.111 [26] clause 8. - -O-RAN-specified O1 notifications are specified in the O-RAN O1 Network Resource Model Specification [i.16]. - -O-RAN-specified O1 notifications should follow 3GPP naming and format where possible to reduce the number of variants that need to be supported. Specifically, O-RAN-specified O1 notifications should: - -- be named "o1NotifyXxx"; -- include the common 3GPP notification fields objectClass, objectInstance, notificationId, notificationType, eventTime and systemDN; -- include an additionalText and/or additionalInformation field when appropriate. - -A VES O1 format notification is an O1 notification formatted as specified by VES Event Listener Specification [18], consisting of a common event header and domain-specific event fields. VES O1 format notifications are categorized into 2 types, based on domain: - -- Harmonized VES; -- Legacy VES. - -Harmonized VES refers to the stdDefined VES event specified in VES Event Listener Specification [18] that allows a VES event to carry, as its payload, a notification specified by an SDO. In the case of O-RAN O1 Interface Specification, a harmonized stdDefined VES event carries either a 3GPP-specified O1 notification or an O-RAN specified O1 notification as its payload. - -Legacy VES refers to any VES event specified in the VES Event Listener Specification [18], except for stdDefined. Legacy VES events are fully defined in [18] and do not rely on an SDO to specify the content of the payload. The Legacy VES events supported by O1 Interface Specification is PNF Registration. - -Legacy VES events are supported for backward compatibility. However, harmonized VES events are preferred. Use of harmonized VES events results in less notification variants for the producers and the consumers because a harmonized VES O1 format notification is effectively an SDO O1 format notification wrapped in a VES common event header. - -Two attributes are used to communicate the notification format between MnS producer and MnS consumer: - -- o1NotifyFormatCapabilities indicates whether the MnS producer supports the capability to send notifications in SDO O1 format, VES O1 format or both. This attribute is set by the MnS producer at the Managed Element level, meaning the capability is for all O1 notifications sent by that MnS producer. It is not per notification type. This attribute is read-only for the MnS consumer. -- o1NotifyFormatConfig indicates whether the MnS consumer wants to receive notifications in SDO O1 format or VES O1 format. This attribute is optional to be supported by MnS producer. This attribute is configured by the MnS consumer at the Managed Element level, meaning the configuration is for all O1 notifications sent by that MnS producer. It is not per notification type. If the MnS producer supports both formats, the MnS producer sets the value for this attribute to the default value of VES O1 format when the MOI is created and - -the MnS consumer is permitted to change the value to SDO O1 format if desired. Otherwise, if the MnS producer only supports one notification format, this attribute is absent. - -Configuration attributes are specified in the O-RAN O1 Network Resource Model Specification [i.16]. - -It is not necessary to have an attribute to indicate whether harmonized VES or legacy VES is sent for VES format because the domain of the event is provided in the VES common event header and the schema of the event is provided by the Network Function at onboarding time. - -## 5.2 O-RAN Defined O1 Notification - -### 5.2.1 Requirements - -REQ-ON-FUN-1: O-RAN defined O1 registration notification shall be JSON encoded for sending via REST/HTTPS. - -REQ-ON-FUN-2: Schema for O-RAN defined O1 notification shall be specified using OpenAPI. - -REQ-ON-FUN-3: If VES O1 format is configured to be used, O-RAN defined O1 notification shall be presented in harmonized VES format and schemaReference shall refer to O-RAN defined schema in O-RAN public repository when it is available. - -NOTE 1: O-RAN public repository is not created yet. - -NOTE 2: Before the schema for the O-RAN defined notification is available in the O-RAN public repository, the schemaReference in the VES O1 format for O-RAN defined O1 notification does not need to be a path to the public repository. - -### 5.2.2 stndDefinedNamespace name space for O-RAN - -O-RAN defines following name space for VES O1 format-harmonized VES format: OR-Registration - -For O-RAN defined performance measurements, the short form of measurement name has prefix "OR.". The source of the definition is clear, so there is no need to have a separate O-RAN name space for performance measurement. - -O-RAN defined performance measurements should use 3GPP-PerformanceMeasurement name space and refer to 3GPP schema. - -# 6 Management Services - -## 6.1 Provisioning Management Services - -### 6.1.0 Overview - -Provisioning management services allow a Provisioning MnS Consumer to configure attributes of managed objects on the Provisioning MnS Producer that modify the Provisioning MnS Producer's capabilities in its role in end-to-end network services and allows a Provisioning MnS Producer to report configuration changes to the Provisioning MnS Consumer. NETCONF is used for the Provisioning Management Services to Create Managed Object Instance, Delete Managed Object Instance, Modify Managed Object Instance Attributes and Read Managed Object Instance Attributes. A RESTful/HTTP notification with data modelled using YANG is used to notify the Provisioning MnS subscribed Consumers when a configuration change occurs. - -Stage 1 Provisioning management services are specified in 3GPP TS 28.531 [i.3] clause 6.3. - -Stage 2 Provisioning operations and notifications are specified in 3GPP TS 28.532 [3] clause 11.1.1. - -Stage 3 Provisioning operations for YANG/NETCONF solution set are specified in 3GPP TS 28.532 [3] clause 12.1.3. - -Stage 3 Provisioning notifications for "YANG/NETCONF-based- solution set" with data modelled using YANG in a RESTful notification is specified in 3GPP TS 28.532 [3] clause 12.1.3. - -For the VES header support, refer to 3GPP TS 28.532 [3] clause 12.1.2. The media type of the notification, as specified by the "Content-Type" header in the HTTP POST request, shall be "application/json". - -NOTE: In the payload, the data is encoded according to 3GPP TS 28.532 [3] clause 12.1.3.2.5 (except for the content type in the header). Consumption of the payload is implementation dependent. - -IETF reference documents for NETCONF and YANG include RFC 6241 [20] and RFC 7950 [21]. - -### 6.1.1 General NETCONF Requirements - -REQ-GNC-FUN-1: The provisioning management service producer and consumer shall support the following NETCONF operations as specified in RFC 6241 [20]: - -- get -- get-config -- edit-config -- lock -- unlock -- close-session -- kill-session - -Other operations are optional. - -REQ-GNC-FUN-2: The provisioning management service producer and consumer shall support the following NETCONF capabilities as specified in RFC 6241 [20]: - -- writable-running -- rollback-on-error -- validate - -- xpath - -Other capabilities defined in RFC 6241 [20] are optional. - -REQ-GNC-FUN-3: The provisioning management service producer and consumer shall support a running datastore for NETCONF. Support for a candidate datastore is optional. - -REQ-GNC-FUN-4: The provisioning management service producer and consumer shall support YANG1.1, defined in RFC 7950 [21], including coexistence with YANG Version 1 as specified therein. - -REQ-GNC-FUN-5: The provisioning management service producer shall have the capability to establish a NETCONF session with its authorized consumer upon request from the consumer. - -REQ-GNC-FUN-6: The provisioning management service producer shall support an established NETCONF session until the authorized consumer terminates the session. - -NOTE: The consumer may want to perform multiple provisioning management services operations during a single NETCONF Session. - -REQ-GNC-FUN-7: The provisioning management service producer shall have the capability to terminate a NETCONF session with its authorized consumer when requested to do so by the authorized consumer. - -REQ-GNC-FUN-8: The provisioning management service producer shall have the capability to make provisioning operation results persistent over a reset. - -REQ-GNC-FUN-9: The provisioning management service producer and consumer shall support NETCONF over SSH or NETCONF over TLS. - -REQ-GNC-FUN-10: The provisioning management service producer shall support /netconf-state/schemas subtree and RPC defined in RFC 6022 [19] for all supported YANG modules. - -REQ-GNC-FUN-11: The provisioning management service producer shall support RFC 6243 [24] "With-defaults capability for NETCONF" as defined by 3GPP TS 28.532 [3], clause 12.1.3.3.2. - -### 6.1.2 Create Managed Object Instance - -#### 6.1.2.1 Description - -Provisioning MnS Consumer sends a synchronous provisioning update request to the Provisioning MnS Producer to create a Managed Object Instance (MOI) on the Provisioning MnS Producer and set its attribute values. - -#### 6.1.2.2 Requirements - -The mapping of operations specified in 3GPP TS 28.532 [3] clauses 12.1.3.1.1 and 12.1.3.1.2 shall apply. - -#### 6.1.2.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -![Sequence diagram titled 'Create MOI' showing the interaction between a Provisioning MnS Consumer and a Provisioning MnS Producer. The Consumer sends a [1] NETCONF edit-config create message to the Producer. The Producer creates the MOI (indicated by a 'Create MOI' note) and returns a [2] NETCONF rpc-reply with or to the Consumer.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) - -``` - -sequenceDiagram - participant Consumer as Provisioning MnS Consumer - participant Producer as Provisioning MnS Producer - Note right of Producer: Create MOI - Consumer->>Producer: [1] NETCONF edit-config create - Producer-->>Consumer: [2] NETCONF rpc-reply or - -``` - -Sequence diagram titled 'Create MOI' showing the interaction between a Provisioning MnS Consumer and a Provisioning MnS Producer. The Consumer sends a [1] NETCONF edit-config create message to the Producer. The Producer creates the MOI (indicated by a 'Create MOI' note) and returns a [2] NETCONF rpc-reply with or to the Consumer. - -**Figure 6.1.2.3-1 Create MOI** - -##### **Pre-Conditions:** - -- NETCONF session has been established with Provisioning MnS Producer. NETCONF session has authorized privileges into the identified section of the data store. -- Optionally, target data store has been locked. - -##### **Procedure:** - -1. Provisioning MnS Consumer sends NETCONF edit-config create operation to Provisioning MnS Producer: - - a. Provisioning MnS Producer creates the MOI(s) in the target data store as described in the edit-config operation. -2. Provisioning MnS Producer returns NETCONF response. - -### 6.1.3 Modify Managed Object Instance Attributes - -#### 6.1.3.1 Description - -Provisioning MnS Consumer sends synchronous provisioning updates to the Provisioning MnS Producer to modify the attributes of a MOI on the Provisioning MnS Producer. - -#### 6.1.3.2 Requirements - -The mapping of operations specified in 3GPP TS 28.532 [3] clauses 12.1.3.1.1 and 12.1.3.1.4 shall apply. - -#### 6.1.3.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -![Sequence diagram showing NETCONF edit-config and rpc-reply between Provisioning MnS Consumer and Producer.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) - -**Modify MOI Attributes** - -``` - -sequenceDiagram - participant C as Provisioning MnS Consumer - participant P as Provisioning MnS Producer - C->>P: [1] NETCONF edit-config create, replace or delete - Note right of P: Modify MOI - P-->>C: [2] NETCONF rpc-reply or - -``` - -Sequence diagram showing NETCONF edit-config and rpc-reply between Provisioning MnS Consumer and Producer. - -**Figure 6.1.3.3-1 Modify MOI Attributes** - -Pre-Conditions: - -- NETCONF session has been established with Provisioning MnS Producer. NETCONF session has authorized privileges into the identified section of the data store. -- Optionally, target data store has been locked. - -Procedure: - -1. Provisioning MnS Consumer sends NETCONF edit-config create, replace, or delete operation to Provisioning MnS Producer: - - a. Provisioning MnS Producer modifies the MOI(s) in the target data store as described in the edit-config operation. -2. Provisioning MnS Producer returns NETCONF response. - -### 6.1.4 Delete Managed Object Instance - -#### 6.1.4.1 Description - -Provisioning MnS Consumer sends synchronous provisioning updates to the Provisioning MnS Producer to delete a MOI and its children on the Provisioning MnS Producer. - -#### 6.1.4.2 Requirements - -The mapping of operations specified in 3GPP TS 28.532 [3] clauses 12.1.3.1.1 and 12.1.3.1.5 shall apply. - -#### 6.1.4.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -![Sequence diagram titled 'Delete MOI' showing the interaction between a Provisioning MnS Consumer and a Provisioning MnS Producer. The Consumer sends a [1] NETCONF edit-config delete or remove message to the Producer. The Producer responds with a [2] NETCONF rpc-reply or message. A note labeled 'Delete MOI' is shown near the Producer's response.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) - -``` - -sequenceDiagram - participant Consumer as Provisioning MnS Consumer - participant Producer as Provisioning MnS Producer - Note right of Producer: Delete MOI - Consumer->>Producer: [1] NETCONF edit-config delete or remove - Producer-->>Consumer: [2] NETCONF rpc-reply or - -``` - -Sequence diagram titled 'Delete MOI' showing the interaction between a Provisioning MnS Consumer and a Provisioning MnS Producer. The Consumer sends a [1] NETCONF edit-config delete or remove message to the Producer. The Producer responds with a [2] NETCONF rpc-reply or message. A note labeled 'Delete MOI' is shown near the Producer's response. - -**Figure 6.1.4.3-1 Delete MOI** - -Pre-Conditions: - -- NETCONF session has been established with Provisioning MnS Producer. NETCONF session has authorized privileges into the identified section of the data store. -- Optionally, target data store has been locked. - -Procedure: - -1. Provisioning MnS Consumer sends NETCONF edit-config delete or remove operation to Provisioning MnS Producer: - - a. Provisioning MnS Producer deletes the MOI(s) in the target data store as described in the edit-config operation. -2. Provisioning MnS Producer returns NETCONF response. - -### 6.1.5 Read Managed Object Instance Attributes - -#### 6.1.5.1 Description - -Provisioning MnS Consumer sends synchronous provisioning request to the Provisioning MnS Producer to return the values of attributes of its MOI(s) on the Provisioning MnS Producer. - -#### 6.1.5.2 Requirements - -The mapping of operations specified in 3GPP TS 28.532 [3] clauses 12.1.3.1.1 and 12.1.3.1.3 shall apply. - -#### 6.1.5.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -![Sequence diagram titled 'Read MOI Attributes' showing the interaction between a Provisioning MnS Consumer and a Provisioning MnS Producer. The Consumer sends a [1] NETCONF get or get-config message to the Producer. The Producer performs a 'Retrieve config' action and then sends a [2] NETCONF rpc-reply back to the Consumer.](2cde062fd82833415971a8bd1a2cafab_img.jpg) - -``` - -sequenceDiagram - participant Consumer as Provisioning MnS Consumer - participant Producer as Provisioning MnS Producer - Note right of Producer: Retrieve config - Consumer->>Producer: [1] NETCONF get or get-config - Producer-->>Consumer: [2] NETCONF rpc-reply - -``` - -Sequence diagram titled 'Read MOI Attributes' showing the interaction between a Provisioning MnS Consumer and a Provisioning MnS Producer. The Consumer sends a [1] NETCONF get or get-config message to the Producer. The Producer performs a 'Retrieve config' action and then sends a [2] NETCONF rpc-reply back to the Consumer. - -Figure 6.1.5.3-1 Read MOI Attributes - -Pre-Conditions: - -- NETCONF session has been established with Provisioning MnS Producer. NETCONF session has authorized privileges into the identified section of the data store. - -Procedure: - -1. Provisioning MnS Consumer sends NETCONF get or get-config operation to Provisioning MnS Producer: - - a. Provisioning MnS Producer retrieves the MOI(s) and its attributes from the target data store as described in the get or get-config operation. -2. Provisioning MnS Producer returns the data in the NETCONF response. - -### 6.1.6 Notify Managed Object Instance Changes - -#### 6.1.6.1 Description - -Provisioning MnS Producer sends an asynchronous notifyMOIChanges Notification to the Provisioning MnS Consumer to report configuration changes to one or more MOIs on the Provisioning MnS Producer. Refer to 3GPP TS 28.532 [3] clause 12.1.3.2.5 for details. - -#### 6.1.6.2 Requirements - -The mapping of notifications specified in 3GPP TS 28.532 [3] clause 11.1.1.11 shall apply. - -#### 6.1.6.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -![Sequence diagram titled 'Notify Managed Object Instance Changes' showing the interaction between a Provisioning MnS Consumer and a Provisioning MnS Producer. The diagram starts with the Consumer at the top left and the Producer at the top right. A note on the Producer side indicates 'One or more config changes occur'. An arrow labeled '1 «HTTP/TLS» notifyMOIChanges Notification' points from the Producer to the Consumer. Below the Consumer, a note indicates 'Reconcile Database'. The diagram ends with the Consumer at the bottom left and the Producer at the bottom right.](dfe556fea00682b09a59427aaf72051c_img.jpg) - -``` - -sequenceDiagram - participant Consumer as Provisioning MnS Consumer - participant Producer as Provisioning MnS Producer - Note right of Producer: One or more config changes occur - Producer->>Consumer: 1 «HTTP/TLS» notifyMOIChanges Notification - Note left of Consumer: Reconcile Database - -``` - -Sequence diagram titled 'Notify Managed Object Instance Changes' showing the interaction between a Provisioning MnS Consumer and a Provisioning MnS Producer. The diagram starts with the Consumer at the top left and the Producer at the top right. A note on the Producer side indicates 'One or more config changes occur'. An arrow labeled '1 «HTTP/TLS» notifyMOIChanges Notification' points from the Producer to the Consumer. Below the Consumer, a note indicates 'Reconcile Database'. The diagram ends with the Consumer at the bottom left and the Producer at the bottom right. - -**Figure 6.1.6.3-1 Notify Managed Object Instance Changes** - -Pre-conditions: - -- One or more MOIs are created, deleted or modified in the running data store of the Provisioning MnS Producer. -- Provisioning MnS Consumer has subscribed for notifyMOIChanges notifications. - -Procedure: - -1. Provisioning MnS Producer sends notifyMOIChanges notification to the Provisioning MnS Consumer over HTTP/TLS. Mutual certificate authentication is performed. - -Post-condition: - -- Provisioning MnS Consumer reconciles its copy of the Provisioning MnS Producer configuration database with the change. - -#### 6.1.6.4 Operations and Notifications - -Refer to clause 5.1 for details on O1 notification formats, including SDO O1 format and VES O1 format notifications, categorized as Harmonized VES. - -The O1-supported 3GPP-specified CM notification is: - -- notifyMOIChanges - -A single notifyMOIChanges notification can report one or more MOI creations, MOI deletions and/or MOI attribute value changes in one notification. - -The attribute name value pairs in the CM notifications are provided using YANG 1.1 encoded in JSON format as specified in RFC 7951 [22]. - -### 6.1.7 Subscription Control - -#### 6.1.7.1 Description - -Subscription Control allows a MnS Consumer to subscribe to notifications emitted by a MnS Producer. - -Starting with 3GPP Release 16, dedicated operations for Management Services Use Cases are supported by IOCs with attributes that can be read and/or set using generic provisioning mechanisms. For Subscription Control, the Subscribe and Unsubscribe operations are replaced with a NtfSubscriptionControl IOC as specified in 3GPP TS 28.622 [7] clause 4.3.22. NtfSubscriptionControl IOC contains attributes that allow a MnS Consumer to set the recipient address for the notifications and identify the scope of notifications desired. Optionally, the types of notifications desired, and notification filtering may also be provided. If filtering of the notifications is supported, only those notifications that match the specified value would be sent. For example, notifyNewAlarm notifications can be filtered to send only those with severity set to major or critical. - -#### 6.1.7.2 Requirements - -NtfSubscriptionControl IOC definition shall be as specified in 3GPP TS 28.622 [7] clause 4.3.22 with attribute definitions specified in 3GPP TS 28.622 [7] clause 4.4.1. - -YANG models for NtfSubscriptionControl shall be as specified in 3GPP TS 28.623 [23] clauses 4.4 and E.2. - -#### 6.1.7.3 Procedures - -NtfSubscriptionControl MOIs can be created and deleted by the system or pre-installed. Optionally, the NtfSubscriptionControl MOIs can be created and deleted, and attributes modified using NETCONF/YANG by the management service consumer following the procedures described in this Provisioning MnS clause. - -#### 6.1.7.4 Operations and Notifications - -NtfSubscriptionControl IOC can be used to subscribe to notifications. In addition, HeartbeatControl IOC specified in 3GPP TS 28.622 [7] clause 4.3.21 can be used to subscribe to heartbeat notifications as specified in 3GPP TS 28.622 [7] Figure 4.2.1-5; i.e., by creating the HeartbeatControl MOI as a child of the NtfSubscriptionControl MOI. - -### 6.1.8 NETCONF Session Establishment - -#### 6.1.8.1 Description - -Provisioning MnS Consumer uses the NETCONF Session Establishment procedure to establish a NETCONF session on the Provisioning MnS Producer. - -#### 6.1.8.2 Requirements - -Requirements for NETCONF session establishment specified in RFC 6241[20] shall apply. - -#### 6.1.8.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -![Sequence diagram titled 'NETCONF Session Establishment' showing the interaction between a Provisioning MnS Consumer and a Provisioning MnS Producer. The steps are: [1] SSH or TLS session establishment, [2] NETCONF Hello, and [3] NETCONF Hello .](5445597cceefaca1ac89e710fe339325_img.jpg) - -``` - -sequenceDiagram - participant Consumer as Provisioning MnS Consumer - participant Producer as Provisioning MnS Producer - Note over Consumer, Producer: NETCONF Session Establishment - Consumer->>Producer: [1] SSH or TLS session establishment - Producer-->>Consumer: [2] NETCONF Hello - Consumer->>Producer: [3] NETCONF Hello - -``` - -Sequence diagram titled 'NETCONF Session Establishment' showing the interaction between a Provisioning MnS Consumer and a Provisioning MnS Producer. The steps are: [1] SSH or TLS session establishment, [2] NETCONF Hello, and [3] NETCONF Hello . - -Figure 6.1.8.3-1 NETCONF Session Establishment - -### 6.1.9 NETCONF Session Termination - -#### 6.1.9.1 Description - -Provisioning MnS Consumer uses the NETCONF Session Termination procedure to gracefully terminate a NETCONF session on a Provisioning MnS Producer. - -#### 6.1.9.2 Requirements - -NETCONF session termination shall be as specified in RFC 6241[20] Section 7.8. - -#### 6.1.9.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -![Sequence diagram titled 'NETCONF Session Termination' showing the interaction between a Provisioning MnS Consumer and a Provisioning MnS Producer. The steps are: [1] NETCONF close-session and [2] NETCONF rpc-reply .](d79d33da852cb7bca3e87b400a15c3e8_img.jpg) - -``` - -sequenceDiagram - participant Consumer as Provisioning MnS Consumer - participant Producer as Provisioning MnS Producer - Note over Consumer, Producer: NETCONF Session Termination - Consumer->>Producer: [1] NETCONF close-session - Producer-->>Consumer: [2] NETCONF rpc-reply - -``` - -Sequence diagram titled 'NETCONF Session Termination' showing the interaction between a Provisioning MnS Consumer and a Provisioning MnS Producer. The steps are: [1] NETCONF close-session and [2] NETCONF rpc-reply . - -Figure 6.1.9.3-1 NETCONF Session Termination - -### 6.1.10 Lock Data Store - -#### 6.1.10.1 Description - -Provisioning MnS Consumer uses the Lock Data Store procedure to lock a target data store on a Provisioning MnS Producer. This procedure is optional, but recommended, to prevent unpredictable behavior during configuration changes. - -#### 6.1.10.2 Requirements - -NETCONF lock data store should be as specified in RFC 6241 [20] Section 7.5. - -#### 6.1.10.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -![Sequence diagram for Lock Data Store procedure. It shows two lifelines: Provisioning MnS Consumer and Provisioning MnS Producer. Step 1: Consumer sends [1] NETCONF lock to Producer. Step 2: Producer performs 'Lock target DS' and sends [2] NETCONF rpc-reply back to Consumer.](608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg) - -``` - -sequenceDiagram - participant Consumer as Provisioning MnS Consumer - participant Producer as Provisioning MnS Producer - Note right of Producer: Lock target DS - Consumer->>Producer: [1] NETCONF lock - Producer-->>Consumer: [2] NETCONF rpc-reply - -``` - -Sequence diagram for Lock Data Store procedure. It shows two lifelines: Provisioning MnS Consumer and Provisioning MnS Producer. Step 1: Consumer sends [1] NETCONF lock to Producer. Step 2: Producer performs 'Lock target DS' and sends [2] NETCONF rpc-reply back to Consumer. - -Figure 6.1.10.3-1 Lock Data Store - -### 6.1.11 Unlock Data Store - -#### 6.1.11.1 Description - -Provisioning MnS Consumer uses the Unlock Data Store procedure to unlock a target data store on a Provisioning MnS Producer. - -#### 6.1.11.2 Requirements - -NETCONF unlock data store should be as specified in RFC 6241 [20] Section 7.6. - -#### 6.1.11.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -![Sequence diagram titled 'Unlock Data Store' showing the interaction between a Provisioning MnS Consumer and a Provisioning MnS Producer. The Consumer sends a [1] NETCONF unlock message to the Producer. The Producer then performs an 'Unlock target DS' action and sends a [2] NETCONF rpc-reply message back to the Consumer.](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) - -``` - -sequenceDiagram - participant Consumer as Provisioning MnS Consumer - participant Producer as Provisioning MnS Producer - Note right of Producer: Unlock target DS - Consumer->>Producer: [1] NETCONF unlock - Producer-->>Consumer: [2] NETCONF rpc-reply - -``` - -Sequence diagram titled 'Unlock Data Store' showing the interaction between a Provisioning MnS Consumer and a Provisioning MnS Producer. The Consumer sends a [1] NETCONF unlock message to the Producer. The Producer then performs an 'Unlock target DS' action and sends a [2] NETCONF rpc-reply message back to the Consumer. - -Figure 6.1.11.3-1 Unlock Data Store - -### 6.1.12 Commit - -#### 6.1.12.1 Description - -Provisioning MnS Consumer uses the Commit procedure to commit a configuration change to the running data store of the Provisioning MnS Producer. This is necessary to make the configuration change effective if it was made in the candidate data store. If the configuration change was made in the running data store, the commit procedure is not used. - -#### 6.1.12.2 Requirements - -Requirements for NETCONF commit specified in RFC 6241 [20] Section 8.4 shall apply. - -#### 6.1.12.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -![Sequence diagram for Commit operation between Provisioning MnS Consumer and Provisioning MnS Producer.](d734a6ea1b381280f043fcf70391b6db_img.jpg) - -The diagram illustrates the 'Commit' sequence. At the top, the title 'Commit' is centered. Below it, two lifelines are shown: 'Provisioning MnS Consumer' on the left and 'Provisioning MnS Producer' on the right. The sequence of interactions is as follows: - - -- [1] The Consumer sends a 'NETCONF commit' message to the Producer. -- Upon receiving the message, the Producer performs an internal action labeled 'Commit change to running DS'. -- [2] The Producer then sends a 'NETCONF rpc-reply ' message back to the Consumer. - -Sequence diagram for Commit operation between Provisioning MnS Consumer and Provisioning MnS Producer. - -Figure 6.1.12.3-1 Commit - -### 6.1.13 Notify Event - -#### 6.1.13.1 Description - -Provisioning MnS Producer sends an asynchronous notifyEvent Notification to the Provisioning MnS Consumer to report a network event has occurred with potential service impacts. Please, refer to 3GPP TS 28.532 [3] clause 11.1.1.10 for details. - -#### 6.1.13.2 Requirements - -The mapping of notifications specified in 3GPP TS 28.532 [3] clause 11.1.1.10 and the NETCONF/YANG solution set specified in 3GPP TS 28.532 [3] clause 12.1.3.2.6 shall apply. - -#### 6.1.13.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -![Sequence diagram for Notify Event procedure between Provisioning MnS Consumer and Provisioning MnS Producer.](86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg) - -The diagram illustrates the 'Notify Event' procedure. At the top, the title 'Notify Event' is centered. Below it, two lifelines are shown: 'Provisioning MnS Consumer' on the left and 'Provisioning MnS Producer' on the right. The sequence of interactions is as follows: - - -- First, an internal action on the Producer side indicates 'A notification subscription including NotifyEvent has been created'. -- Next, another internal action on the Producer side indicates 'One or more network events have occurred with potential service impact'. -- Finally, the Producer sends a '1 «HTTP/TLS» notifyEvent Notification' message to the Consumer. - -Sequence diagram for Notify Event procedure between Provisioning MnS Consumer and Provisioning MnS Producer. - -Figure 6.1.13.3-1 Notify Event - -##### **Pre-conditions:** - -- A notification subscription including NotifyEvent has been explicitly or implicitly created specifying the Provisioning MnS Consumer as the notification recipient. -- One or more network events have occurred with potential service impact - -##### **Procedure:** - -1. Provisioning MnS Producer sends notifyEvent notification to the Provisioning MnS Consumer over HTTP/TLS. Mutual certificate authentication is performed. - -##### **Post-condition:** - -- Provisioning MnS Consumer has received a notifyEvent notification - -#### 6.1.13.4 Operations and Notifications - -Refer to clause 5.1 for details on O1 notification formats, including SDO O1 format and VES O1 format notifications, categorized as Harmonized VES. - -The O1-supported 3GPP-specified CM notification is: - -- notifyEvent - -## 6.2 Fault Supervision Management Services - -### 6.2.0 Overview - -Fault supervision management services allow a Fault Supervision MnS Producer to report errors and events to a Fault Supervision MnS Consumer and allows a Fault Supervision MnS Consumer to perform fault supervision operations on the Fault Supervision MnS Producer, such as get alarm list. The Fault supervision management services include the optional capability of Fault History Supervision Control and Reporting. - -Stage 1 Fault Supervision MnS is specified in 3GPP TS 28.111 [26]. - -Stage 2 Fault Supervision notifications are specified in 3GPP TS 28.111 [26] clause 8. - -Stage 2 AlarmList IOC and AlarmRecord data type are specified in 3GPP TS 28.111 [26] clauses 7.3.2 and 7.3.1. - -Stage 3 Solution Set for NETCONF/YANG is specified in 3GPP TS 28.111 [26] annex A.3. - -### 6.2.1 Fault Notification - -#### 6.2.1.1 Description - -Fault Supervision MnS Producer sends asynchronous Fault notification event to Fault Supervision MnS Consumer when an alarm occurs, is cleared, or changes severity. - -#### 6.2.1.2 Requirements - -The following fault supervision data report service requirements specified in 3GPP TS 28.111 [26] clause 5 shall apply: - -- REQ-FM-MC-1 for sending alarm notifications -- REQ-FM-MC-2 for alarm notification subscription -- REQ-FM-MC-3 for alarm notification unsubscription -- REQ-FM-MC-5 for reading the alarm list -- REQ-FM-MC-6 for reading the alarm list with a filter - -- REQ-FM-MC-7 for sending changed alarm notifications -- REQ-FM-MC-8 for sending cleared alarm notifications -- REQ-FM-MC-9 for sending new alarm notifications -- REQ-FM-MC-10 to support indicating a potentially faulty alarm list -- REQ-FM-MC-11 for sending alarm list rebuilt notification - -The following requirements from 3GPP TS 28.111 [26] clause 5 may apply: - -- REQ-FM-MC-4 for filtering the alarm notifications that are reported - -NOTE: Filtering is best done at the SMO level. - -- REQ-FM-MC-14 for sending acknowledgement state change notifications - -#### 6.2.1.3 Procedures - -Procedures for subscription and notifications are described in 3GPP TS 28.622 [7] clause 4.3.22 and 3GPP TS 28.111 [26] clause 6.12. - -#### 6.2.1.4 Operations and Notifications - -Refer to clause 5.1 for details on O1 notification formats, including SDO O1 format and VES O1 format notifications, categorized as Harmonized VES. - -The Fault Supervision MnS Producer shall support the following 3GPP-specified Fault Supervision notifications are: - -- notifyNewAlarm -- notifyChangedAlarmGeneral -- notifyClearedAlarm -- notifyAlarmListRebuilt - -NotifyChangedAlarmGeneral permits the producer to report the severity change and any other attribute changes associated with this alarm in a single notification. The other 3GPP Fault Supervision notifications specified in 3GPP TS 28.111 [26] are optional. - -The Fault Supervision MnS Producer should support the following 3GPP-specified Fault Supervision notifications: - -- notifyAckStateChanged - -If the NF supports alarm acknowledgement, it should have the capability to provide NotifyAckStateChanged. - -- notifyPotentialFaultyAlarmList - -The Fault supervision MnS producer shall not send 3GPP-specified fault supervision notifications when the state of an AlarmList MOI is locked or disabled, as specified in TS 28.111 [26], clause 6.13. - -### 6.2.2 Fault Supervision Control - -#### 6.2.2.1 Description - -Starting with 3GPP Release 16, dedicated operations for Management Services Use Cases are supported by IOCs with attributes that can be read and/or set using generic provisioning mechanisms. For Fault Supervision, an AlarmList IOC is specified in 3GPP TS 28.111 [26] clause 7.3.2 that represents the capability to store and manage alarm records. There is one AlarmList per Fault Supervision MnS Producer, created by the Producer. The AlarmList contains one AlarmRecord for each active alarm. The AlarmRecords in the AlarmList can be read by the Fault Supervision MnS - -Consumer, with an optional filter to retrieve selected AlarmRecords based on the value of attributes in the AlarmRecord. For example, Fault Supervision MnS Consumer is able to retrieve only those AlarmRecords with perceivedSeverity = CRITICAL. - -As described in 3GPP TS 28.111 [26] clause 6.11, the reliability of an AlarmList indicates whether its AlarmRecords are up to date or not. - -The conditions for adding, deleting, or updating AlarmRecords in an AlarmList MOI, as determined by the AlarmList state, are specified in clause 6.13 of 3GPP TS 28.111 [26]. When the state of an AlarmList MOI is locked or disabled, the AlarmRecords in the AlarmList MOI are not reliable, as described in 3GPP TS 28.111 [26], clause 6.13. - -#### 6.2.2.2 Requirements - -The following fault supervision data control service requirements from 3GPP TS 28.111 [26] clause 5 may apply to the Fault Supervision MnS Producer: - -- REQ-FM-MC-12 to support alarm acknowledgement. - -NOTE 1: There is no Use Case that requires a NF to acknowledge an alarm. This operation is best done at the SMO level. - -- NF that does not support the alarm acknowledgement from the MnS Consumer shall consider cleared alarms as automatically acknowledged so that they may be removed from the AlarmList. -- REQ-FM-MC-13 to support manual alarm clearing. - -NOTE 2: Manual clearing of alarms is only for ADMC (Automatically Detected, Manually Cleared) alarms. - -- NF that supports ADMC alarms should support the manual alarm clearing operation. - -AlarmList IOC definition shall be as specified in 3GPP TS 28.111 [26] clause 7.3.2 with attribute definitions in specified in 3GPP TS 28.111 [26] clause 7.4.1. - -YANG solution set for AlarmList IOC shall be as specified in 3GPP TS 28.111 [26] clause A.3. - -#### 6.2.2.3 Procedures - -NETCONF protocol and YANG data models are used to get and set the attributes of the AlarmRecords in the AlarmList. - -Refer to clause 6.1 for procedures to read MOI attributes and modify MOI attributes using NETCONF. - -Refer to clause 6.2.2.1 for the reliability conditions of getting and setting attributes of the AlarmRecords in the AlarmList depending on the AlarmList states. - -#### 6.2.2.4 Void - -### 6.2.3 Fault History Supervision Control and Reporting - -#### 6.2.3.1 Description - -The Fault History Supervision Control and Reporting allows a Fault Supervision MnS Producer to report to a Fault Supervision MnS Consumer relevant information about raised, changed, or cleared alarms in the past. Generalizing, it allows to report information about alarms updates. - -When an alarm is raised, the Fault Supervision MnS Producer stores the relevant initial data of a new alarm, according to the information exposed by the notifyNewAlarm notification. - -When an alarm is modified or cleared, the Fault Supervision MnS Producer stores the relevant data of the alarm change, according to the information exposed by the notifyChangeAlarm/notifyChangedAlarmGeneral, or notifyClearedAlarm. - -When an alarm list is locked or disabled, alarm records are not reliable, as consequences also the capability of the Fault Supervision MnS Producer to store alarm changes is not reliable. - -#### 6.2.3.2 Requirements - -The following requirements shall apply: - -- REQ-FSHQ\_MC-1 The Fault Supervision MnS Producer shall have the capability to store the relevant data of alarms updates if the Fault History Supervision Control and Reporting capability is provided. -- REQ-FSHQ\_MC-2 The Fault Supervision MnS Producer shall have the capability to store the alarm updates even when the ability to send alarm notifications to subscribed consumer(s) is not available (e.g. during a disturbance), if Fault History Supervision Control and Reporting capability is provided. -- REQ-FSHQ\_MC-3 The Fault Supervision MnS Producer shall allow authorized consumers to retrieve the stored alarm updates if Fault History Supervision Control and Reporting capability is provided. - -NOTE: The Fault Supervision MnS Producer allows authorized consumers to retrieve alarm updates for a specific time window. The time window may include present time. - -- REQ-FSHQ\_MC-4 The Fault Supervision MnS Producer shall have the capability to store the notifyAlarmListRebuilt notification if Fault History Supervision Control and Reporting capability is provided. In case, it may also have the capability to store the notifyPotentialFaultyAlarmList notification. -- REQ-FSHQ\_MC-5 The Fault Supervision MnS Producer should have the capability to report the perceivedSeverity at the time of the alarm creation, if Fault History Supervision Control and Reporting capability is provided. - -## 6.3 Performance Assurance Management Services - -### 6.3.0 Overview - -Performance Assurance Management Services allow a Performance Assurance MnS Producer to report file-based (bulk) and/or streaming (real time) performance data to a Performance Assurance MnS Consumer and allows a Performance Assurance MnS Consumer to perform performance assurance operations on the Performance Assurance MnS Producer, such as selecting the measurements to be reported and setting the frequency of reporting. - -Use cases for PM services are specified in 3GPP TS 28.550 [6] clause 5.1. - -Stage 2 notifyFileReady and notifyFilePreparationError notifications are specified in 3GPP TS 28.532 [3]. - -Stage 2 PerfMetricJob IOC is specified in 3GPP TS 28.622 [7] clause 4.3.31. - -Stage 3 Solution Sets for XML, JSON and YANG are specified in 3GPP TS 28.623 [23]. - -Stage 2 and 3 for streaming data reporting service are specified in 3GPP TS 28.532 [3]. - -3GPP defined 5G performance measurements are specified in 3GPP TS 28.552 [i.5]. In addition to the 3GPP-defined measurements, it is possible to have O-RAN defined measurements and vendor supplied measurements. Clause 6.3.4 provides requirements for O-RAN defined measurements. O-RAN defined measurements are named with an "OR." prefix. Vendor supplied measurements are named with a "VS." prefix. - -### 6.3.1 Performance Data File Reporting - -#### 6.3.1.1 Description - -A Performance Assurance MnS Producer that provides file-based (bulk) performance data reporting shall support the PM data pull-based file reporting method and/or the PM data push-based file reporting method. - -In the pull-based file reporting method for PM data file reporting, the Performance Assurance MnS Producer sends asynchronous notifyFileReady notification event to Performance Assurance MnS Consumer when PM File(s) is ready - -for retrieval or the Performance Assurance MnS producer sends asynchronous `notifyFilePreparationError` notification event to Performance Assurance MnS Consumer when there is any error while preparing the file(s). The `notifyFileReady` notification contains information needed to retrieve the file such as filename and the location where the file can be retrieved. Performance Assurance MnS Consumer retrieves the PM File(s) from the location specified in the `notifyFileReady` notification. The `notifyFilePreparationError` notification contains error reasons as specified in 3GPP TS 28.532 [3], clause 11.6.1.2.2. - -In the push-based file reporting method the Performance Assurance MnS Producer makes PM File(s) available for retrieval by transferring the PM File(s) to an entity such as a designated file server or to the Performance Assurance MnS Consumer as described in 3GPP TS 28.537 [4] clause 7.3.1. The file location where the PM File(s) are to be pushed, the designated file server, is identified by the Performance Assurance MnS Consumer when creating the `PerfMetricJob` IOC using the "FileLocation" attribute. If the Performance Assurance MnS Producer is capable of providing notifications related to the file transfer operation using the `notifyFileReady` or `notifyFilePreparationError` notification event, the Performance Assurance MnS Producer can send the `notifyFileReady` or `notifyFilePreparationError` notification event to the subscribed Performance Assurance MnS Consumers. When transferring files, a secure connection is established between the Performance Assurance MnS Producer and the Performance Assurance MnS Consumer or the designated file server and the method for reporting the collected PM data to the MnS Consumer is defined in the `PerfMetricJob` IOC (see clause 6.3.3). - -#### 6.3.1.2 Requirements - -##### 6.3.1.2.1 Pull-based Performance Data File Reporting Requirements - -When the pull-based Performance Data File Reporting method is used, the requirements specified in 3GPP TS 28.550 [6] clause 5.2.2 shall apply. - -##### 6.3.1.2.2 Push-based Performance Data File Reporting Requirements - -When the push-based Performance Data File Reporting method is used, the following requirements apply. - -REQ-OPM-PUSH-FUN1: The Performance Assurance MnS Producer responsible for the push-based Performance Data File Reporting method shall have the capability to send the NF performance data file to its authorized Performance Assurance MnS Consumer or a designated file server as described in 3GPP TS 28.537 [4] clause 7.3.1. - -REQ-OPM-PUSH-FUN2: The Performance Assurance MnS Producer responsible for the push-based Performance Data File Reporting method shall provide support for the file transfer protocols specified in 3GPP TS 28.537 [4] clause 7.1.3 in the client role of the protocol. - -REQ-OPM-PUSH-FUN3: The Performance Assurance MnS Consumer responsible for the push-based Performance Data File Reporting method shall provide support for the file transfer protocols specified in 3GPP TS 28.537 [4] clause 7.1.3 in the server role of the protocol. - -REQ-OPM-PUSH-FUN4: The Performance Assurance MnS Producer responsible for the push-based Performance Data File Reporting method shall provide the ability to announce the capability to support notifications related to the completion of the file transfer. - -REQ-OPM-PUSH-FUN5: When supported, the Performance Assurance MnS Producer responsible for the push-based Performance Data File Reporting method shall provide the Performance Assurance MnS Consumers the ability to subscribe to receive notifications related to completion of the file transfer. - -#### 6.3.1.3 Procedures - -##### 6.3.1.3.1 Pull-based Performance Data File Reporting Procedure - -###### 6.3.1.3.1.0 Introduction - -When the pull-based Performance Data File Reporting method is used, the procedure based on the use case described in 3GPP TS 28.550 [6] clause 5.1.1.2 is used. - -###### **6.3.1.3.1.1 Pull-based Performance Data File Reporting Procedure for file ready events** - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -In the pull-based file reporting method for PM data file reporting, the Performance Assurance MnS Producer sends asynchronous notifyFileReady notification event to Performance Assurance MnS Consumer when PM File(s) is ready for retrieval as specified in 3GPP TS 28.532 [3], clause 11.6.1.1.1. - -![Sequence diagram titled 'Pull-based PM Data File Reporting and Retrieval' showing interactions between Performance Assurance MnS Consumer and Performance Assurance MnS Producer. The sequence starts with the Producer having '1 New PM data file available', followed by a '2 «HTTP/TLS» notifyFileReady Notification' from Producer to Consumer, and finally a '3 «Secure File Transfer Protocol» Get PM File(s)' from Consumer to Producer.](6ca05954842b17f14dfd52f26b9d43d2_img.jpg) - -``` - -sequenceDiagram - participant Consumer as Performance Assurance MnS Consumer - participant Producer as Performance Assurance MnS Producer - Note right of Producer: 1 New PM data file available - Producer->>Consumer: 2 «HTTP/TLS» notifyFileReady Notification - Consumer->>Producer: 3 «Secure File Transfer Protocol» Get PM File(s) - -``` - -Sequence diagram titled 'Pull-based PM Data File Reporting and Retrieval' showing interactions between Performance Assurance MnS Consumer and Performance Assurance MnS Producer. The sequence starts with the Producer having '1 New PM data file available', followed by a '2 «HTTP/TLS» notifyFileReady Notification' from Producer to Consumer, and finally a '3 «Secure File Transfer Protocol» Get PM File(s)' from Consumer to Producer. - -**Figure 6.3.1.3.1.1-1 Pull-based PM Data File Reporting and Retrieval** - -Pre-condition: - -- Performance Assurance MnS Consumer has subscribed to notifyFileReady notifications. - -Procedure: - -1. A new PM data file is available on the Performance Assurance MnS Producer. -2. Performance Assurance MnS Producer sends notifyFileReady notification to Performance Assurance MnS Consumer over HTTP/TLS. Mutual certificate authentication is performed. -3. Performance Assurance MnS Consumer sets up a secure file transfer protocol connection to the location provided in the notifyFileReady notification and gets the PM data file(s). Secure file transfer protocols are described in 3GPP TS 28.537 [4], clause 7.1.3. - -###### **6.3.1.3.1.2 Pull-based Performance Data File Reporting Procedure for file preparation error events** - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -In the pull-based file reporting method for PM data file reporting, the Performance Assurance MnS producer sends asynchronous notifyFilePreparationError notification event to Performance Assurance MnS Consumer when there is any error while preparing the file(s), as specified in 3GPP TS 28.532 [3], clause 11.6.1.2.1. - -![Sequence diagram showing a file preparation error. The Performance Assurance MnS Producer sends a '1 Error while preparing the file' notification to the Performance Assurance MnS Consumer. The Consumer then responds with '2 «HTTP/TLS» notifyFilePreparationError Notification'.](fa01531ea2c45beeb4036005da3037a4_img.jpg) - -**Pull-based PM Data File Reporting and Retrieval** - -``` - -sequenceDiagram - participant Consumer as Performance Assurance MnS Consumer - participant Producer as Performance Assurance MnS Producer - Note right of Producer: 1 Error while preparing the file - Producer->>Consumer: 2 «HTTP/TLS» notifyFilePreparationError Notification - -``` - -Sequence diagram showing a file preparation error. The Performance Assurance MnS Producer sends a '1 Error while preparing the file' notification to the Performance Assurance MnS Consumer. The Consumer then responds with '2 «HTTP/TLS» notifyFilePreparationError Notification'. - -**Figure 6.3.1.3.1.2-1 Pull-based PM Data File Reporting while FilePreparation error** - -Pre-condition: - -- Performance Assurance MnS Consumer has subscribed to notifyFilePreparationError notifications. - -Procedure: - -1. A new PM data file(s) could not be prepared due to an error which occurred while preparing the file. -2. Performance Assurance MnS producer sends notifyFilePreparationError notification to Performance Assurance MnS consumer over HTTP/TLS with the reason of the error. Reasons for the error are as described in 3GPP TS 28.532 [3], clause 11.6.1.2.2. - -##### 6.3.1.3.2 Push-based Performance Data File Reporting Procedure - -###### 6.3.1.3.2.0 Introduction - -When the push-based Performance Data File Reporting method is used, the following procedures are used when the PM file(s) is ready for retrieval or when there is an error while preparing the file. - -###### 6.3.1.3.2.1 Push-based Performance Data File Reporting Procedure with optional file ready event - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -When the push-based Performance Data File Reporting method is used, and if Performance Assurance MnS producer is capable of providing notification to the Performance Assurance MnS Consumer when PM file(s) is ready for retrieval, the following procedure is used. - -![Sequence diagram titled 'Push-based PM Data File Reporting' showing interactions between Performance Assurance MnS Consumer, Performance Assurance MnS Producer, and Designated File Server. The diagram includes preconditions, file transfer steps, an optional notification step, and file retrieval steps.](dcf37c460c66ec011dbe6ca08de44ff9_img.jpg) - -**Push-based PM Data File Reporting** - -The diagram illustrates the sequence of interactions for push-based PM data file reporting. It involves three main entities: Performance Assurance MnS Consumer, Performance Assurance MnS Producer, and Designated File Server. - -**Preconditions:** - -- Performance Assurance MnS Producer is configured to produce push-based file reporting to the location of a file server where the Performance Assurance MnS Consumer can retrieve the file by specifying the "fileLocation" in the PerfMetricJob creation. -- A PM data file is available at the Performance Assurance MnS Producer to transmit to the File Server. -- (Optionally) Performance Assurance MnS Consumer has subscribed to file transfer operation notifications. - -**Sequence of Interactions:** - -- The Performance Assurance MnS Producer sends a message indicating "1 New PM data File(s) available" to the Designated File Server. -- The Designated File Server responds with "«Secure File Transfer Protocol» 2 Push PM File(s)" to the Performance Assurance MnS Producer. -- An optional block titled "if Performance Assurance MnS Producer is capable of reporting file notifications and Performance Assurance MnS Consumer has subscribed" shows the Performance Assurance MnS Producer sending a "3 «HTTP/TLS» notifyFileReady notification" to the Performance Assurance MnS Consumer. -- Finally, the Performance Assurance MnS Consumer sends a "4 Retrieves PM File(s)" request to the Designated File Server. - -Sequence diagram titled 'Push-based PM Data File Reporting' showing interactions between Performance Assurance MnS Consumer, Performance Assurance MnS Producer, and Designated File Server. The diagram includes preconditions, file transfer steps, an optional notification step, and file retrieval steps. - -Figure 6.3.1.3.2.1-1 Push-based PM Data File Establishment and Data Transmission - -Pre-condition: - -- Performance Assurance MnS Producer is configured to produce push-based file reporting to the location of a file server or to the Performance Assurance MnS Consumer, as designated by the Performance Assurance MnS Consumer at the PerfMetricJob IOC creation. (Figure 6.3.1.3.2.1-1 depicts the scenario of pushing the file to a designated file server) -- A PM data file is available at the Performance Assurance MnS Producer to transmit to the File Server. -- (Optionally) Performance Assurance MnS Consumer has subscribed to file transfer operation notifications. - -Procedure: - -1. PM File(s) are available to the Performance Assurance MnS Producer -2. Performance Assurance MnS Producer transmits the PM file(s) to the Performance Assurance MnS Consumer or to a file server designated by the Performance Assurance MnS Consumer by the file location provided in the PerfMetricJob. -3. If the Performance Assurance MnS Producer is capable of reporting file notifications and Performance Assurance MnS Consumer has subscribed to receive the notifications, the Performance Assurance MnS Producer sends notifyFileReady notification to the Performance Assurance MnS Consumer after the file transfer. -4. In case of push-based file reporting method to a designated flier server, Performance Assurance MnS Consumer retrieves the PM file(s) from the File Server - -###### 6.3.1.3.2.2 Push-based Performance Data File Reporting Procedure with optional file preparation error event - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -When the push-based Performance Data File Reporting method is used, and if Performance Assurance MnS producer is capable of providing notification to the Performance Assurance MnS Consumer when there is error in preparing the PM file(s), the following procedure is used. - -![Sequence diagram titled 'Push-based PM Data File Reporting' showing interactions between Performance Assurance MnS Consumer, Performance Assurance MnS Producer, and Designated File Server. The diagram includes preconditions and an optional notification step.](14252bcd35912bd656e98b16b2ee51c0_img.jpg) - -**Push-based PM Data File Reporting** - -The diagram illustrates the sequence of interactions for push-based PM data file reporting. It features three lifelines: **Performance Assurance MnS Consumer**, **Performance Assurance MnS Producer**, and **Designated File Server**. A yellow box at the top outlines the preconditions: the Producer is configured to push files to a server location specified by the Consumer during PerfMetricJob creation, and the Consumer has optionally subscribed to file transfer notifications. The sequence then shows an error handling path: '1 Error while preparing the file' from the Producer to the Consumer, followed by an optional block 'opt [if Performance Assurance MnS Producer is capable of reporting file notifications and Performance Assurance MnS Consumer has subscribed]'. Inside this block, a '3 «HTTP/TLS» notifyFilePreparationError notification' is sent from the Producer to the Consumer. - -Sequence diagram titled 'Push-based PM Data File Reporting' showing interactions between Performance Assurance MnS Consumer, Performance Assurance MnS Producer, and Designated File Server. The diagram includes preconditions and an optional notification step. - -**Figure 6.3.1.3.2.2-2 Push-based PM Data File Establishment and Data Transmission** - -Pre-condition: - -- Performance Assurance MnS Producer is configured to produce push-based file reporting to the location of a file server or to the Performance Assurance MnS Consumer, as designated by the Performance Assurance MnS Consumer at the PerfMetricJob IOC creation. -- (Optionally) Performance Assurance MnS Consumer has subscribed to file transfer operation notifications. - -Procedure: - -1. A new PM data file(s) could not be prepared due to an error which occurred while preparing the file. -2. If the Performance Assurance MnS Producer is capable of reporting file notifications and Performance Assurance MnS Consumer has subscribed to receive the notifications, the Performance Assurance MnS Producer sends `notifyFilePreparationError` notification to the Performance Assurance MnS Consumer with the reason of the error. Reasons for the error are as described in 3GPP TS 28.532 [3], clause 11.6.1.2.2. - -#### 6.3.1.4 Operations and Notifications - -Refer to clause 5.1 for details on O1 notification formats, including SDO O1 format and VES O1 format notifications, categorized as Harmonized VES. - -The O1-supported 3GPP-specified file transfer operation notifications are: - -- `notifyFileReady`; -- `notifyFilePreparationError`. - -#### 6.3.1.5 PM File Generation and Reporting - -When the pull-based Performance Data File Reporting method is used, the following PM File Generation and Reporting requirements apply: - -- PM file generation and reporting shall be as specified in 3GPP TS 28.532 [3] clause 11.6. - -When the push-based Performance Data File Reporting method is used, the following PM File Generation and Reporting requirements apply: - -- The Performance Assurance MnS Producer shall support the file transfer protocols 3GPP TS 28.537 [4] clause 7.1.3. - -- The Performance Assurance MnS Producer shall always act as the client while the MnS consumer shall always act as the server of file transfer actions. - -#### 6.3.1.6 PM File Content - -PM file content shall be as specified in 3GPP TS 28.532 [3] clause 11.3.2.1.2. - -#### 6.3.1.7 PM File Naming - -PM file naming shall be as specified in 3GPP TS 28.532 [3] clause 11.3.2.1.4. - -#### 6.3.1.8 PM File XML Format - -PM file XML format shall be as specified in 3GPP TS 28.532 [3] clause 12.3.2 and/or in 3GPP TS 32.432 [14] clause 4.1. - -#### 6.3.1.9 Void - -### 6.3.2 Performance Data Streaming - -#### 6.3.2.1 Description - -Performance Assurance MnS Producer streams high volume asynchronous streaming performance measurement data to Performance Assurance MnS Consumer at a configurable frequency. A secure WebSocket connection is established between the Performance Assurance MnS Producer and the Performance Assurance MnS Consumer. The connection supports the transmission of one or more streams of PM data. Each stream of PM data is configured as a PerfMetricJob (see clause 6.3.3). The Performance Assurance MnS Producer supplies information about the supported streams to the consumer during the connection establishment. The connection may be established to support one or more streams. Streams can be added or removed from the connection as the PerfMetricJobs are added or deleted. The connectionID that carries the streaming PM data is provided to the Performance Assurance MnS Producer during the establishment of the WebSocket connection by the Performance Assurance MnS Consumer. - -#### 6.3.2.2 Requirements - -Requirements for Streaming PM specified in 3GPP TS 28.550 [6] clause 5.2.3 shall apply. - -#### 6.3.2.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -Use Cases for Streaming PM are described in 3GPP TS 28.550 [6] clause 5.1.1.3. Operations and notifications described in 3GPP TS 28.532 [3] clause 11.5 are applicable to both Streaming PM and Streaming Trace. - -![Sequence diagram for Performance Data Streaming showing connection establishment via HTTP/TLS and data reporting via WebSocket within a loop.](cfb98c691c1af5befe32ff9442eea511_img.jpg) - -**Performance Data Streaming** - -``` - -sequenceDiagram - participant Consumer as Performance Assurance MnS Consumer - participant Producer as Performance Assurance MnS Producer - Note over Producer: Performance Data Streaming Job Configured - Consumer->>Producer: 1 «HTTP/TLS» establish Streaming Connection - Producer-->>Consumer: 2 «HTTP/TLS» Connection Established - loop while performance job is active - Producer->>Consumer: 3 «WebSocket» report stream data via performance data stream unit - end - -``` - -Sequence diagram for Performance Data Streaming showing connection establishment via HTTP/TLS and data reporting via WebSocket within a loop. - -**Figure 6.3.2.3-1 Perf Data Streaming Connection Establishment and Data Transmission** - -Pre-condition: - -- Performance Assurance MnS Producer is configured to produce PerfMetricJob to be delivered via streaming PM to the Performance Assurance MnS Consumer. - -Procedure: - -1. Performance Assurance MnS Producer requests to establish a WebSocket connection to begin streaming PM data and provides MetaData about the streams that are to be sent on the connection -2. Performance Assurance MnS Consumer accepts the request to upgrade the connection to a WebSocket. -3. Performance Assurance MnS Producer transmits binary encoded data to consumer while performance job is active. - -#### 6.3.2.4 Operations and Notifications - -3GPP TS 28.532 [3] clause 11.5.1 defines the following operations that an O-RAN compliant NF that supports streaming PM shall support. These are the same operations as listed in clause 6.4.6. They are repeated here, as it is possible that a NF may support different levels of streaming for trace and performance assurance. - -- **establishStreamingConnection** operation is specified in 3GPP TS 28.532 [3] clause 11.5.1.1. Establishing the streaming connection is initiated via an HTTPS POST followed by an HTTP GET (upgrade) to establish the WebSocket connection. -- **terminateStreamingConnection** operation is specified in 3GPP TS 28.532 [3] clause 11.5.1.2. This operation is accomplished via a WebSocket Close Frame to tear down the streaming connection when all stream jobs on this connection have been terminated. The delivery of WebSocket Close Frame is provided by the underlying TCP. -- **reportStreamData** operation is specified in 3GPP TS 28.532 [3] clause 11.5.1.3. The streamData field contains the streaming PM data which is encoded according to the format defined in 3GPP TS 28.550 [6] Annex G which provides the ASN.1 definition of the Performance Data Stream Units. The delivery of WebSocket Close Frame is provided by the underlying TCP. - -If O-RAN NF supports the capability of sending multiple PM streams across the WebSocket connection, the following operations shall be supported. - -- **addStream** operation is specified in 3GPP TS 28.532 [3] clause 11.5.1.4. This operation is used when a new Performance Assurance Stream (PM job started) is added on the Performance Assurance MnS Producer to be - -delivered to this consumer, and the NF supports multiple streams per connection. The addStream operation is accomplished via an HTTP POST. - -- deleteStream operation is specified in 3GPP TS 28.532 [3] clause 11.5.1.5. This operation is used when a Performance Assurance Stream (PM job stopped) is deleted from the connection between the Performance Assurance MnS Producer and the Performance Assurance MnS Consumer. The deleteStream operation is accomplished via an HTTP DELETE. - -The following operations specified in 3GPP TS 28.532 [3] clause 11.5.1 may be supported by O-RAN NFs: - -- getConnectionInfo operation is specified in 3GPP TS 28.532 [3] clause 11.5.1.6. This operation allows the performance data streaming service producer to get information from the performance data streaming service consumer on the streams active on the connection. -- getStreamInfo operation is specified in 3GPP TS 28.532 [3] clause 11.5.1.7. This operation allows the performance data streaming service producer to get the information for one or more streams from the streaming consumer (i.e., stream target). - -No notifications have been defined for Performance Data Streaming. - -#### 6.3.2.5 PM Streaming Data Generation and Reporting - -3GPP TS 28.550 [6] Annex C lists all the Performance Data Stream Unit Content Items. Annex C of the present document provides a description of the establishment of the WebSocket connection and the subsequent operations provided as part of the data streaming service. The example utilizes the trace service, but the operations around the establishment and tear down of the connection are the same for streaming PM and streaming Trace. The WebSocket connection remains until all streams configured to be provided between the Performance Assurance MnS Producer and the Performance Assurance MnS Consumer have been terminated. - -#### 6.3.2.6 PM Streaming Data Format - -PM Streaming data shall be delivered according to the format specified in the input parameters of the establishStreamConnection operation specified in 3GPP TS 28.532 [3] clause 11.5.1.1.2. - -### 6.3.3 Measurement Job Control - -#### 6.3.3.1 Description - -Starting with 3GPP Release 16, Performance Assurance Control supported by IOCs with attributes that can be read and/or set using generic provisioning mechanisms in the Measurement Job Control Service. Measurement jobs can be created and terminated by creating and deleting a PerfMetricJob MOI. Measurement jobs can be queried by getting the attributes of a PerfMetricJob MOI. Measurement jobs can be temporarily suspended or resumed by modifying the administrativeState attribute of a PerfMetricJob MOI to LOCKED or UNLOCKED. - -#### 6.3.3.2 Requirements - -Requirements for measurement job control specified in 3GPP TS 28.550 [6] clause 5.2.1 shall apply. - -PerfMetricJob IOC definition shall be as specified in 3GPP TS 28.622 [7] clause 4.3.31 with attribute definitions in specified in 3GPP TS 28.622 [7] clause 4.4.1. SupportedPerfMetricGroup datatype shall be as specified in 3GPP TS 28.622 [7] clause 4.3.32. ReportingCtrl shall be as specified in 3GPP TS 28.622 [7] clause 4.3.33. - -YANG solution set for PerfMetricJob IOC shall be as specified in 3GPP TS 28.623 [23] clauses 4.4 and E.2. - -#### 6.3.3.3 Procedures - -Measurement job creation, termination, query, suspend and resume are described in 3GPP TS 28.622 [7] clause 4.3.31. - -NETCONF protocol and YANG data models are used to create MOI, delete MOI, modify attributes and get attributes of a PerfMetricJob. Refer to Provisioning management services clause for detailed procedures on how to perform these operations using NETCONF. - -#### 6.3.3.4 Void - -### 6.3.4 O-RAN Defined Performance Measurements - -O1 performance measurements are defined in the O-RAN O1 Performance Measurements Specification [i.17] and 3GPP TS 28.552 [i.5]. - -PMCountGroup and CuCountGroup, described in O1 Interface specification for O-DU [i.19] and O1 Interface specification for O-CU-UP and O-CU-CP [i.20] respectively, can be used as filtering mechanisms for O-RAN defined O1 performance measurements. Filtering mechanisms defined in clause 4.2 of 3GPP TS 28.552 [i.5] can be used as well. - -#### 6.3.4.1 Void - -## 6.4 Trace Management Services - -### 6.4.0 Overview - -Trace management services allow a Trace MnS Producer to report file-based or streaming trace records to the Trace MnS Consumer. Trace Control provides the ability for the Trace MnS Consumer to start a trace session by configuring a Trace Job via the Trace Control IOC or by establishing a trace session that propagates trace parameters to other Trace MnS Producers via signaling. There are multiple levels of trace that can be supported on the Trace MnS Producer as described in 3GPP TS 32.421 [11] clause 4.1. The Trace MnS Producer may be configured to support file-based trace reporting or streaming trace reporting. - -Trace Management Services specified in 3GPP TS 32.421 [11], 3GPP TS 32.422 [12] and 3GPP TS 32.423 [13] and supported on an applicable O-RAN ME include Call Trace, Minimization of Drive Testing (MDT), RRC Connection Establishment Failure (RCEF) and Radio Link Failure TCE (RLF). All of these services follow a similar management paradigm. Trace Sessions are configured on the Trace MnS Producer with information on where and how to send the trace information to the consumer. The Trace MnS Producer creates trace records within a trace session as the trigger mechanism occurs. Trace records are produced and provided to the consumer until the trace session is terminated. - -File-based trace collects trace records in files that are available to the consumer with a time delay. In the case of streaming trace, the data is sent in bursts across a WebSocket connection to the consumer, maintaining the relevance of the data while minimizing transport overhead. - -Stage 1 Trace Management Service is specified in 3GPP TS 32.421 [11]. Use cases for trace are specified in clause 5.8 and elaborated in 3GPP TS 32.421 [11] Annex A. General Trace Requirements are found in 3GPP TS 32.421 [11] clause 5.1. - -Stage 2 Trace Operations are found in 3GPP TS 32.422 [12] for 5G support of Call Trace and for streaming trace. - -Stage 2 TraceJob IOC for management-based control is specified in 3GPP TS 28.622 [7] clause 4.3.30. Stage 2 for signaling based activation is found in 3GPP TS 32.422 [12]. - -Stage 3 definitions of trace record content for all trace types, XML trace file format, and streaming trace GPB record definition are found in 3GPP TS 32.423 [13]. - -Stage 3 TraceJob IOC mapping for management-based control is specified in 3GPP TS 28.623 [23] clauses 4.3, 4.4, E.1 and E.2. - -Stage 2 and 3 definitions for streaming data reporting are specified in 3GPP TS 28.532 [3]. - -### 6.4.1 Call Trace - -#### 6.4.1.1 Trace Data Reporting - -##### 6.4.1.1.1 Description - -Trace Data can be reported from the Trace MnS Producer to the Trace MnS Consumer via trace files or via a streaming interface. For management-based activation, Trace Data is collected after the TraceJob is configured on the Trace MnS Producer, the Trace Session is activated, and the triggering event occurs. For signaling-based activation, the Trace Recording Session starts when the NF receives trace control and configuration parameters via one of the signaling messages specified in 3GPP TS 32.422 [12] clause 4.2.3.12. - -When the Trace MnS Producer collects trace data to a file, the file is periodically provided to the Trace MnS Consumer. When the producer supports streaming trace, the trace is sent to the consumer via data bursts which are sent frequently enough to retain the relevance of the data while conserving transport resources. The WebSocket connection carrying the streaming trace is preserved for the duration of the streaming trace. - -##### 6.4.1.1.2 Requirements - -Requirements for Trace data specified in 3GPP TS 32.421 [11] clause 5.2 shall apply to both file-based and streaming trace. - -##### 6.4.1.1.3 Procedures - -Trace Data is binary encoded and reported in Trace Records. The procedures for reporting data are described in 3GPP TS 32.422 [12] clause 7. File-based trace reporting procedures are described in 3GPP TS 32.422 [12] clauses 7.1.1 and 7.2.1. Streaming trace reporting procedures are described in 3GPP TS 32.422 [12] clauses 7.1.2 and 7.2.2. Trace Record Contents are described in 3GPP TS 32.423 [13] clause 4. The Trace Record content is the same for trace jobs controlled by management-based activation and signaling-based activation. The raw trace record content is the same for file-based trace and streaming trace. Trace data is binary encoded in ASN.1. File-based trace is delivered in XML format with trace records encoded in ASN.1. Streaming trace is delivered in GPB encoded data bursts with the trace record payload containing ASN.1 encoded data. - -Procedures for naming the trace data file are described in 3GPP TS 32.423 [13] Annex B. File Naming Convention is described in 3GPP TS 32.423 [13] clause B.1. - -Trace files are produced in XML format. The XML format is described in 3GPP TS 32.423 [13] clause A2.2. Example XML files are provided in 3GPP TS 32.423 [13] Annex D. - -If a trace file cannot be created, a trace failure notification file XML schema can be sent. The XML schema is provided in 3GPP TS 32.422 [12] clause A.5 and the naming convention for the file containing the failure is described in clause A.4. - -For streaming trace, raw trace data is collected on the node and sent to the trace collector. The trace data is binary encoded. The format of the streaming trace data is provided in 3GPP TS 32.423 [13]. The reportStreamData operation is described in 3GPP TS 28.532 [3] clause 12.5.1.1.4. - -#### 6.4.1.2 Trace Session Activation - -##### 6.4.1.2.1 Description - -A trace session starts on a producer configured to support a TraceJob via management or signaling-based activation. Management-based trace session activation is initiated from the Provisioning Management Service Consumer to activate a TraceJob which has been configured on the producer. See clause 6.4.5. With signaling-based trace session activation, the producer receives a signaling message that contains trace consumer ID address (IP address for file-based or URI for streaming) along with trace control parameters. Each Trace session has a unique trace session identifier that is associated with all of the trace data collected for this session. - -If the trace session is configured to be file-based, the producer collects the data and stores the data in a file. The producer optionally sends the file directly to the consumer or sends the location of the file to the consumer. File transport approach is not standardized. - -3GPP TS 28.532 [3] supports the streaming of trace data from the producer to the consumer. Trace data for a trace session is collected and transmitted to the producer across a secure WebSocket connection in data bursts which are emitted frequently enough to ensure the relevance of the data while conserving transport resources. See clause 6.4.6 and Annex C of the present document for details on the streaming service. - -##### 6.4.1.2.2 Requirements - -Requirements for Trace Session activation for file-based and streaming trace specified in 3GPP TS 32.421 [11] clause 5.3.1 shall apply. - -##### 6.4.1.2.3 Procedures - -Procedures for activating a Trace Session via management-based control are described in 3GPP TS 32.422 [12] clause 4.1.1.1 for general procedures and 3GPP TS 32.422 [12] clause 4.1.1.9 for NGRAN specific procedures. Procedures for activating a Trace Session via signaling are described in 3GPP TS 32.422 [12] clause 4.1.2.1 and clause 4.1.2.16. - -#### 6.4.1.3 Trace Session Deactivation - -##### 6.4.1.3.1 Description - -A Trace Session is terminated/deactivated when any of the defined stop triggering events occur as specified in 3GPP TS 32.421 [11], such as a timer expiring, or the TraceJob Session is deactivated via management control. - -##### 6.4.1.3.2 Requirements - -Requirements for Trace Session deactivation specified in 3GPP TS 32.421 [11] clause 5.4.1 shall apply. - -##### 6.4.1.3.3 Procedures - -Procedures for Trace Session Deactivation are described in 3GPP TS 32.422 [12] clause 4.1.3.10 for management-based trace deactivation and 4.1.4.1.2 for signaling-based trace deactivation. - -#### 6.4.1.4 Trace Recording Session Activation - -##### 6.4.1.4.1 Description - -A trace recording session is a specific instance of the data specified to be collected for a particular trace session, for example, a specific call. For management-based activation, the trace recording session starts on a producer configured with an active trace session when a triggering event occurs, such as a new call starting. Each Trace recording session within a trace session has a unique trace recording session reference. This recording session reference and the session reference are included with each trace record, uniquely identifying the trace record as belonging to a particular trace recording session. For signaling-based activation, the Trace Recording Session starts when the NF receives trace control and configuration parameters via a control signaling message. 3GPP TS 32.422 [12] clause 4.2.3.12 outlines the procedures the node is to follow when determining when to begin a new trace recording session and when to continue with an existing session. - -##### 6.4.1.4.2 Requirements - -Requirements for starting Trace Recording Session specified in 3GPP TS 32.421 [11] clause 5.3.2 shall apply. - -##### 6.4.1.4.3 Procedures - -Procedures for starting a Trace Recording Session are described in 3GPP TS 32.422 [12] clause 4.2.1 for general cases. 3GPP TS 32.422 [12] clause 4.2.2.10 has details for management-based trace session activation and 4.2.3.12 has details when the trace session was activated via signaling. - -#### 6.4.1.5 Trace Recording Session Termination - -##### 6.4.1.5.1 Description - -A Trace Recording Session is terminated when any of the defined stop triggering events occur or the Trace Session is deactivated. - -##### 6.4.1.5.2 Requirements - -Requirements for stopping Trace Recording Session specified in 3GPP TS 32.421 [11] clause 5.4.2 shall apply. - -##### 6.4.1.5.3 Procedures - -Procedures for Trace Recording Session Termination are described in 3GPP TS 32.422 [12] clause 4.2.4.10 and 4.2.5.13. - -### 6.4.2 Minimization of Drive Testing (MDT) - -#### 6.4.2.1 Description - -3GPP TS 37.320 [i.9] provides an overall description for MDT. An O-RAN network function may support Immediate and Logged MDT as described in 3GPP TS 37.320 [i.9]. Logged MDT is always file-based. Immediate MDT may be configured to be file-based or streaming. MDT measurements are described in 3GPP TS 37.320 [i.9]. 3GPP TS 32.421 [8], 32.422 [12] and 32.423 [13] describe the management of MDT and have been updated to support 5G. - -#### 6.4.2.2 Requirements - -Requirements for managing MDT specified in 3GPP TS 32.421 [11] clause 6 shall apply. - -#### 6.4.2.3 Procedures - -Procedures for Trace Session Activation are the same for MDT as for Call Trace and are described in 3GPP TS 32.422 [12] clause 4.1. Procedures for specifying MDT Trace selection conditions are described in 3GPP TS 32.422 [12] clause 4.1.5. - -Procedures for Trace Recording Sessions start and stop for MDT are described in 3GPP TS 32.422 [12] clause 4.2. - -Procedures for handling MDT sessions at handover for Immediate MDT are described in 3GPP TS 32.422 [12] clause 4.4 and Logged MDT in 3GPP TS 32.422 [12] clause 4.5. - -Procedures for user consent handling in MDT are described in 3GPP TS 32.422 [12] clause 4.6. - -Procedures for MDT reporting are described in 3GPP TS 32.422 [12] clause 6. - -MDT Trace Record Contents are described in 3GPP TS 32.423[13] clause 4. - -Trace file format for MDT Trace is described in 3GPP TS 32.423 [13] clause A.2.1. Example XML files are provided in 3GPP TS 32.423 [13] clause D.1.4. - -### 6.4.3 Radio Link Failure (RLF) - -#### 6.4.3.1 Description - -Radio Link Failure (RLF) reporting is a special Trace Session which provides the detailed information when a UE experiences an RLF event, and the reestablishment is successful to the source gNB. 3GPP TS 32.421 [11], 32.422 [12] and 32.423 [13] describe the management of RLF. - -#### 6.4.3.2 Requirements - -Requirements for RLF specified in 3GPP TS 32.421 [11] clause 7 shall apply. - -#### 6.4.3.3 Procedures - -Procedures for Trace session activation and deactivation for RLF reporting are described in 3GPP TS 32.422 [12] clause 4.3.1 and 4.3.2. - -Procedures for specifying the RLF reporting job type when configuring the RLF reporting session are described in 3GPP TS 32.422 [12] clause 5.9a. - -Procedures for RLF reporting follow standard trace reporting procedures documented in 3GPP TS 32.422 [12] clause 7. - -### 6.4.4 RRC Connection Establishment Failure (RCEF) - -#### 6.4.4.1 Description - -Radio Resource Control (RRC) Connection Establishment Failure (RCEF) is activated on the gNB as a special Trace Session where the job type indicates RCEF reporting only. The records are produced when a UE experiences an RCEF event and the RRC establishment is successful to the same gNB. - -#### 6.4.4.2 Requirements - -Requirements for RCEF specified in 3GPP TS 32.421 [11] clause 7 shall apply. - -#### 6.4.4.3 Procedures - -Procedures for trace session activation of RCEF are described in 3GPP TS 32.422 [12] clause 4.8.1. - -Procedures for trace session deactivation for RCEF reporting are described in 3GPP TS 32.422 [12] clause 4.8.2. - -Procedures for specifying the job type for RCEF are described in 3GPP TS 32.422 [12] clause 5.9a. - -Procedures for RCEF Reporting are described in 3GPP TS 32.422 [12] clause 7. - -### 6.4.5 Trace Control - -#### 6.4.5.1 Description - -Starting with 3GPP Release 16, Management-based Trace Control is supported with IOCs with attributes that can be read and/or set using generic provisioning mechanisms in the Trace Control Service. For Trace Control, this includes operations such as Create TraceJob, Activate TraceJob, Deactivate TraceJob, and Query TraceJobs. TraceJobs can be created, activated, deactivated, and queried by setting and/or getting attributes in the TraceJob IOC. The TraceJob IOC supports Management-based activation for Call Trace, MDT, RLF and RCEF. - -Trace sessions can also be activated and deactivated via signaling-based configuration initiated from another NF to propagate a configured trace, such as a UE trace when the UE moves from one NF to another. - -#### 6.4.5.2 Requirements - -Management-based activation and deactivation shall be done via the TraceJob IOC defined in 3GPP TS 28.622 [7] clause 4.3.30. Requirements for TraceJob activation specified in 3GPP TS 32.421 [11] clause 5.3.1 and requirements for TraceJob deactivation specified in 3GPP TS 32.421 [11] clause 5.4.1 shall apply for both Management and signaling activation. - -#### 6.4.5.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -Management-based activation and deactivation accomplished using CRUD operations documented in clause 6.1. The attributes of the TraceJob are described in 3GPP TS 28.622 [7] clause 4.3.30.2. Constraints on these attributes are described in 3GPP TS 28.622 [7] clause 4.3.30.3. TraceJob IOC mapping for management-based control is documented in 3GPP TS 28.623 [23]. The YANG model for the TraceJob IOC is described in 3GPP TS 28.623 [23] clauses 4.4 and E.2. - -Procedures for signaling-based Trace Session activation are described in 3GPP TS 32.422 [12] clause 4.1.2. - -Procedures for signaling-based Trace Session deactivation are described in 3GPP TS 32.422 [12] clause 4.1.4. - -### 6.4.6 Streaming Trace - -#### 6.4.6.0 Overview - -A NF can be configured to deliver trace data via a file or via a streaming interface. The streaming capability was introduced in 3GPP Release 16. The additional requirements and procedures supported for streaming trace are provided in this clause. An example of the configuration, activation, recording and termination of a streaming trace connection are shown in Informative Annex C. - -#### 6.4.6.1 Requirements - -As noted above, trace session and recording activation and deactivation, as well as the content of the trace record, are the same for file-based and streaming trace. The requirements for streaming trace delivery specified in 3GPP TS 32.421 [11] clause 5.5 shall apply. Operations for establishing the streaming connection, adding, and deleting streams from the connection and reporting streaming trace data shall be as specified in 3GPP TS 28.532 [3] clause 11.5. O-RAN NFs supporting streaming trace shall support the `establishStreamingConnection`, `reportStreamData` and `terminateStreamingConnection` operations. O-RAN NFs that support the multiplexing of trace streams across a single connection shall support the `addStream` and `deleteStream` operations. Optionally, the NF may also support the `getConnectionInfo` and `getStreamInfo` operations which allow the producer to query for information on the connection and streams on the connection. No notifications have been defined for streaming trace. - -Stage 3 information on the streaming operations is provided in 3GPP TS 28.532 [3] clause 12.5 with Open API YAML definition provided in clause A.6.1.2. - -#### 6.4.6.2 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -The procedure for `establishStreamingConnection` is an HTTP POST operation to provide the information on the stream to the consumer and to receive the Connection ID as a response. The HTTP POST is followed by an HTTP GET to upgrade the connection to a WebSocket connection. This operation is used when no connection is established between the producer and the consumer. The WebSocket connection can contain one or more streams of data from streaming trace or streaming PM. See 3GPP TS 28.532 [3] clause 12.5.1.1.2. - -The `terminateStreamingConnection` is a WebSocket close frame operation. This operation is used when all streams on a connection have terminated. See 3GPP TS 28.532 [3] clause 12.5.1.1.3. - -The `addStream` Operation is an HTTP POST to indicate that additional streams are being added to the connection. A stream corresponds to a trace job or a streaming PM job. See 3GPP TS 28.532 [3] clause 12.5.1.1.5. - -The `deleteStream` Operation is an HTTP DELETE to indicate that a stream has been terminated from the connection. See 3GPP TS 28.532 [3] clause 12.5.1.1.6. - -The `reportStreamData` is a WebSocket data frame sent across the connection containing the streaming trace or streaming PM data or an optional alive message indicating that the stream is active, but no data is available. See 3GPP TS 28.532 [3] clause 12.5.1.1.4. - -The `getConnectionInfo` Operation is an HTTP GET from the producer to the consumer to obtain information about the connection, such as which streams are supported. See 3GPP TS 28.532 [3] clause 12.5.1.1.7. - -The `getStreamInfo` Operation is an HTTP GET from the producer to the consumer to obtain information on the stream. See 3GPP TS 28.532 [3] clause 12.5.1.1.8. - -Annex C provides a streaming trace activation example for management-based activation control. - -### 6.4.7 UE Identifiers for Trace Records - -#### 6.4.7.1 Description - -The contents of the Trace Records are specified in 3GPP TS 32.423 [13] clause 4 and Trace Record Header in 3GPP TS 32.423 [13] clause 5.2.2. The Trace Record containing protocol related messages may contain 3GPP defined UE identifiers corresponding to the protocol. These UE identifiers are a part of protocol messages sent as Trace Records. The Trace Header also contains RAN UE ID as an optional information element. However, for correlation of Trace Records from different O-RAN entities, the UE identifiers embedded in the protocol messages and the RAN UE ID in Trace Header may not be sufficient and may need to be complemented by other information. Hence a set of UE Identifiers and Node Identifiers are defined in O-RAN-Architecture-Description document [15] clause 5.5 for O-RAN ecosystem. - -To enable correlation of Trace Records between O-RAN entities, Trace MnS Producer includes the optional RAN UE ID in the Trace Header when available and other applicable 3GPP UE identifiers defined in O-RAN-Architecture-Description document [15] clause 5.5 in the optional *vendorExtension* IE defined in 3GPP TS 32.423 [13] clause 5.2.2. in the Trace Header. - -Refer to Annex D for the recommendation for UE Identifier format for *vendorExtension* IE in the Trace Header - -## 6.5 File Management Services - -### 6.5.0 Overview - -File management services allow a File Management MnS Consumer to get notification of new available files; query available files and request the transfer of files between the File Management MnS Producer and the File Management MnS Consumer. - -Relevant 3GPP specifications for file transfer are 3GPP TS 28.537 [4], 3GPP TS 32.341 [8], 3GPP TS 32.342 [9] and 3GPP TS 32.346 [i.8]. - -### 6.5.1 File Ready Notification - -#### 6.5.1.1 Description - -The File Ready Notification notifies a File Management MnS Consumer that a file is available for retrieval from the File Management MnS Producer. In general, File Management MnS Producer sends a `notifyFileReady` notification for files that the File Management MnS Consumer has configured the File Management MnS Producer to collect on a periodic basis, such as file-based Trace Data or PM Measurement Reports. - -#### 6.5.1.2 Requirements - -The `notifyFileReady` notification shall be as specified in 3GPP TS 28.532 [3], clause 11.6.1.1. - -#### 6.5.1.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -File Management MnS Consumer configures a File Management MnS Producer to collect data files with specific characteristics that the File Management MnS Consumer desires, such as file-based Trace Data or PM Measurement Reports described in clause 6.3. After configuration, the File Management MnS Consumer terminates the configuration session and waits for the File Management MnS Producer to report that the file is ready for collection. - -When a file is available, the File Management MnS Producer sends a notifyFileReady notification to the File Management MnS Consumer using REST/HTTPS. - -![Sequence diagram titled 'notifyFileReady Notification' showing the interaction between File Management MnS Consumer and File Management MnS Producer. The producer sends a notification message to the consumer, and a note indicates 'New file is available'.](030c758fd425016b03290c8f11bef69d_img.jpg) - -``` - -sequenceDiagram - participant FMnC as File Management MnS Consumer - participant FMnP as File Management MnS Producer - Note right of FMnP: New file is available - FMnP->>FMnC: 1 «HTTP/TLS» notifyFileReady Notification - -``` - -Sequence diagram titled 'notifyFileReady Notification' showing the interaction between File Management MnS Consumer and File Management MnS Producer. The producer sends a notification message to the consumer, and a note indicates 'New file is available'. - -Figure 6.5.1.3-1 File Available for Transfer to Consumer - -Pre-condition: - -- A new file is available on the File Management MnS Producer. - -Procedure: - -1. File Management MnS Producer sends notifyFileReady notification to File Management MnS Consumer over HTTP/TLS. Mutual certificate authentication is performed. - -#### 6.5.1.4 Operations and Notifications - -Refer to clause 5.1 for details on O1 notification formats, including SDO O1 format and VES O1 format notifications, categorized as Harmonized VES. - -The O1-supported 3GPP-specified File Ready notification is: - -- notifyFileReady - -#### 6.5.1.5 File Types Supported - -File Type requirements are documented in 3GPP TS 32.341 [8] clause 5.2. - -#### 6.5.1.6 File Naming Requirements - -Unless explicitly stated in the present document for particular File Types, the File Naming Convention specified in 3GPP TS 32.342 [9] Annex A shall apply. - -### 6.5.2 List Available Files - -#### 6.5.2.1 Description - -File Management MnS Consumer queries the File Management MnS Producer to identify files that are available on the File Management MnS Producer. Upon receipt of the available files and their locations, the File Management MnS Consumer can determine the next appropriate action. - -#### 6.5.2.2 Requirements - -Requirements on the types of files specified in clause 5.2 of 3GPP TS 32.341 [8] shall apply. - -#### 6.5.2.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -List Available Files Use Case allows the File Management MnS Consumer to obtain a list of available files and their locations by reading the AvailableFileList IOC documented in 3GPP TS 32.342 [9]. A File Management MnS Consumer uses this management service in scenarios where the File Management MnS Producer is collecting information, such as logs, on a standard basis in support of debugging activities. Under normal operations, the File Management MnS Producer does not send this data to the File Management MnS Consumer as the File Management MnS Consumer does not need it. The File Management MnS Producer retains the data with the oldest data being overwritten when space is exhausted. In some scenarios, the File Management MnS Consumer wants to retrieve some, or all, of the available log files to resolve an issue. In this case, File Management MnS Consumer sends a NETCONF command to the File Management MnS Producer to obtain the list of available files. File Management MnS Producer responds with AvailableFileList which contains a list of available files and their locations and file types. File Management MnS Consumer uses this information to transfer the desired files (see clause 6.5.3). - -The File Management MnS Consumer does not have to initiate a file retrieval as a result of the obtaining the list of available files. There are use cases where the File Management MnS Consumer wants to verify that files are being collected or verify that all files of a particular type (PM for example) have been retrieved. - -![Sequence diagram titled 'List Available Files' showing interactions between File Management MnS Consumer and File Management MnS Producer. The sequence consists of four steps: [1] Establish NETCONF Session, [2] NETCONF , [3] NETCONF , and [4] Terminate NETCONF Session.](4a94ebc4d41217ce3083a255bfb9c538_img.jpg) - -``` - -sequenceDiagram - participant Consumer as File Management MnS Consumer - participant Producer as File Management MnS Producer - Note over Consumer, Producer: List Available Files - Consumer->>Producer: [1] Establish NETCONF Session - Producer-->>Consumer: - Consumer->>Producer: [2] NETCONF - Producer-->>Consumer: [3] NETCONF - Consumer->>Producer: [4] Terminate NETCONF Session - Producer-->>Consumer: - -``` - -Sequence diagram titled 'List Available Files' showing interactions between File Management MnS Consumer and File Management MnS Producer. The sequence consists of four steps: [1] Establish NETCONF Session, [2] NETCONF , [3] NETCONF , and [4] Terminate NETCONF Session. - -Figure 6.5.2.3-1 List Available Files - -1. File Management MnS Consumer establishes NETCONF session with File Management MnS Producer. -2. File Management MnS Consumer sends NETCONF to the File Management MnS Producer to retrieve the contents of the AvailableFileList. -3. File Management MnS Producer sends NETCONF to the File Management MnS Consumer with list of available files on the File Management MnS Producer. -4. File Management MnS Consumer terminates NETCONF session with File Management MnS Producer. - -### 6.5.3 File Transfer to and from File Management MnS Producer - -#### 6.5.3.1 Description - -The File Transfer by File Management MnS Consumer Use Case provides the capability for a File Management MnS Consumer to transfer files from or to the File Management MnS Producer. In this use case, File Management MnS Consumer is the client and File Management MnS Producer is the file server. - -The File Management MnS Consumer can perform this action as a result of: - -1. notifyFileReady notification from the File Management MnS Producer informing the File Management MnS Consumer that a file(s) is available -2. Querying the File Management MnS Producer for the list of available files (see clause 6.5.2). -3. A need to transfer a file from a known location on the File Management MnS Producer. -4. A need to transfer a file to a known location on the File Management MnS Producer. Some examples of files that could be transferred to the FileManagement MnS Producer are: - - Beamforming configuration file (Opaque Vendor specific data) - - Machine Learning - - Certificates - -File Transfer is performed using a secure file transfer protocol (SFTP, FTPeS or HTTPS) from or to the File Management MnS Producer. - -#### 6.5.3.2 Requirements - -File Transfer Requirements specified in clause 7.1.3 of 3GPP TS 28.537 [4] shall apply. - -#### 6.5.3.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -**Case 1:** File Management MnS Consumer determines that a file needs to be transferred from the location provided by the File Management MnS Producer as a result of receiving a notifyFileReady notification from the File Management MnS Producer (described in clause 6.5.1). - -**Case 2:** File Management MnS Consumer determines that a file needs to be transferred from the File Management MnS Producer as a result of receiving a list of available files from the File Management MnS Producer (described in clause 6.5.2) - -**Case 3:** File Management MnS Consumer determines that a file needs to be transferred from the File Management MnS Producer from a known location on the File Management MnS Producer. - -**Case 4:** File Management MnS Consumer determines that a file needs to be transferred to the File Management MnS Producer to a known location on the File Management MnS Producer. - -File Management MnS Consumer initiates a secure file transfer using FTPeS, SFTP or HTTPS to transfer a file from or to the File Management MnS Producer. - -![Sequence diagram showing file transfer from File Management MnS Consumer to File Management MnS Producer using FTPeS, SFTP, or HTTPS.](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) - -**File Transfer by File Management MnS Consumer.** - -``` - -sequenceDiagram - participant Consumer as File Management MnS Consumer - participant Producer as File Management MnS Producer - Note left of Consumer - Note right of Producer - Consumer->>Producer: 1 «FTPeS, SFTP or HTTPS» Transfer File - -``` - -Sequence diagram showing file transfer from File Management MnS Consumer to File Management MnS Producer using FTPeS, SFTP, or HTTPS. - -**Figure 6.5.3.3-1 File Transfer by File Management MnS Consumer** - -### 6.5.4 Download File from remote file server - -#### 6.5.4.1 Description - -The File Management MnS Consumer has a file that needs to be downloaded to the File Management MnS Producer such as: - -- Software file to upgrade software version executed on the File Management MnS Producer -- Beamforming configuration file (Opaque Vendor specific data) -- Machine Learning -- Certificates - -The File Management MnS Consumer triggers the file download. The File Management MnS Producer uses a secure file transfer protocol to download the file from the location specified by the File Management MnS Consumer and then notifies the File Management MnS Consumer of the result of the download. In this use case, the File Management MnS Producer is the client. The file could be located on any File Server reachable by the File Management MnS Producer. - -#### 6.5.4.2 Requirements - -General File Download requirements specified in clause 7.4.3 of 3GPP TS 28.537 [4] shall apply. - -#### 6.5.4.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -![Sequence diagram titled 'File Download' showing interactions between File Management MnS Consumer, File Management MnS Producer, and File Server. The sequence includes: 1. Establish Netconf Session, 2. NETCONF , 3. NETCONF , 4. Terminate Netconf Session, 5. «FTPeS, SFTP or HTTPS» file download, 6. «HTTP/TLS» downloadFile Event (optional), 7. «HTTP/TLS» downloadFile Event.](41aef1f5efab13d4f38f69e86c726062_img.jpg) - -``` - -sequenceDiagram - participant Consumer as File Management MnS Consumer - participant Producer as File Management MnS Producer - participant Server as File Server - - Note over the diagram: File Download - - Consumer->>Producer: [1] Establish Netconf Session - Consumer->>Producer: [2] NETCONF - Producer-->>Consumer: [3] NETCONF - Consumer->>Producer: [4] Terminate Netconf Session - - opt Download Progress Notifications - Producer->>Server: [5] «FTPeS, SFTP or HTTPS» file download - Producer-->>Consumer: [6] «HTTP/TLS» downloadFile Event - end - - Producer-->>Consumer: [7] «HTTP/TLS» downloadFile Event - -``` - -Sequence diagram titled 'File Download' showing interactions between File Management MnS Consumer, File Management MnS Producer, and File Server. The sequence includes: 1. Establish Netconf Session, 2. NETCONF , 3. NETCONF , 4. Terminate Netconf Session, 5. «FTPeS, SFTP or HTTPS» file download, 6. «HTTP/TLS» downloadFile Event (optional), 7. «HTTP/TLS» downloadFile Event. - -Figure 6.5.4.3-1 File Download - -Procedure: - -1. File Management MnS Consumer establishes NETCONF session with File Management MnS Producer. -2. File Management MnS Consumer sends NETCONF RPC file-download request, including the location of the file to download, to the File Management MnS Producer to trigger a file download. -3. File Management MnS Producer replies with its ability to begin the download. -4. File Management MnS Consumer terminates NETCONF session with File Management MnS Producer. -5. File Management MnS Producer sets up a secure connection and downloads the file via a secure file transfer protocol (FTPeS, SFTP or HTTPS) and according to the O-RAN Security Requirements and Controls Specifications [17] clause 5.2.2. -6. (Optional) If the download takes a long time, File Management MnS Producer sends periodic downloadFile notifications to the File Management MnS Consumer with the current status of the download (download in progress). -7. When download completes, File Management MnS Producer sends a downloadFile notification to the File Management MnS Consumer with the final status of the download (success, file missing, failure). - -#### 6.5.4.4 Operations and Notifications - -Refer to clause 5.1 for details on O1 notification formats, including SDO O1 format and VES O1 format notifications, categorized as Harmonized VES. - -NOTE: There are no File Download notifications defined in the present document. - -### 6.5.5 Void - -## 6.6 Heartbeat Management Capability - -### 6.6.0 Overview - -Heartbeat management capability allows an MnS Producer to send heartbeats to an MnS Consumer (i.e. a notification recipient, according to 3GPP TS 28.622 [7], clause 4.3.21.1) and allows an MnS Consumer to configure the heartbeat services on an MnS Producer. - -Stage 1 Heartbeat management capability is specified in 3GPP TS 28.537 [4]. This 3GPP specification is aligned with the Services Based Management Architecture (SBMA) approach defined in 3GPP TS 28.533 [i.4] clause 4 and contains Use Cases, Requirements and Procedures for configuring the heartbeat period, reading the heartbeat period, triggering an immediate heartbeat notification and emitting a periodic heartbeat notification. - -Stage 2 notifyHeartbeat notification is specified in 3GPP TS 28.532 [3]. - -Stage 2 HeartbeatControl IOC is specified in 3GPP TS 28.622 [7] clause 4.3.21. - -Stage 3 Solution Sets for XML, JSON and YANG are specified in 3GPP TS 28.623 [23]. - -### 6.6.1 Heartbeat Notification - -#### 6.6.1.1 Description - -MnS Producer sends asynchronous heartbeat notifications to MnS Consumer at a configurable frequency to allow MnS Consumer to supervise the connectivity from the MnS Producer. - -#### 6.6.1.2 Requirements - -Requirements for heartbeat notifications specified in 3GPP TS 28.537 [4] clause 4.2.2.2 shall apply. - -#### 6.6.1.3 Procedures - -Procedures for heartbeat notifications are described in 3GPP TS 28.537 [4] clause 4.3.2 and 4.3.3. - -#### 6.6.1.4 Operations and Notifications - -Refer to clause 5.1 for details on O1 notification formats, including SDO O1 format and VES O1 format notifications, categorized as Harmonized VES. - -The O1-supported 3GPP-specified Heartbeat notification is: - -- notifyHeartbeat. - -### 6.6.2 Heartbeat Control - -#### 6.6.2.1 Description - -Starting with 3GPP Release 16, dedicated operations for Management Services Use Cases are supported by IOCs with attributes that can be read and/or set using generic provisioning mechanisms. For Heartbeat management capability, a Heartbeat Control IOC is specified in 3GPP TS 28.622 [7] that includes attributes to Get/Set Heartbeat Period, (heartbeatNtfPeriod) and Trigger Immediate Heartbeat (triggerHeartbeatNtf). - -#### 6.6.2.2 Requirements - -Requirements for heartbeat control specified in 3GPP TS 28.537 [4] clause 4.2.2.1 shall apply. - -HeartbeatControl IOC definition shall be as specified in 3GPP TS 28.622 [7] clause 4.3.21. - -YANG solution set for HeartbeatControl IOC shall be as in 3GPP TS 28.623 [23] clauses 4.4 and E.2. - -#### 6.6.2.3 Procedures - -Procedures for heartbeat control are described in 3GPP TS 28.537 [4] clause 4.3.1 and 4.3.2. - -NETCONF protocol and YANG data models are used to read and configure the *heartbeatNtfPeriod* and *triggerHeartbeatNtf* in the *HeartbeatControl* IOC. Refer to clause 6.1 for procedures to read MOI attributes and modify MOI attributes using NETCONF. - -#### 6.6.2.4 Void - -## 6.7 Registration Management capability - -## 6.7.0 Overview - -The O1 Registration management capability enables a MnS Consumer to establish an O1 management connection with a MnS Producer, when it has completed its initialization phase and has sent the O1 Registration notification. This capability is deployment agnostic, and it is applicable both to physical and virtual deployment. - -In case of a physical deployment, the MnS Producer supports sending the O1 Registration Notification (see clause 6.7.2) upon first PNF power-up/first start-up and any following start-up. - -In case of a virtualized deployment, the MnS Producer supports sending the O1 Registration Notification, upon the virtualized deployment(s) (e.g. NF deployment(s)) have completed the start-up, and an O1 management connection establishment is required. - -The PNF Plug-n-Connect scenario, described in clause 6.7.1 is relevant in a start-up without persistent memory, to dynamically obtain the necessary start-up configuration. - -Relevant 3GPP specifications for PNF Plug-n-Connect (PnC) are 3GPP TS 28.314 [1], 28.315 [2] and 28.316 [i.2]. - -### 6.7.1 PNF Plug-n-Connect - -#### 6.7.1.1 Description - -PNF Plug-n-Connect (PnC) scenario enables a PNF to obtain the necessary start-up configuration to allow it to register with a MnS Consumer for subsequent management. - -#### 6.7.1.2 Requirements - -Specification requirement for Plug and Connect specified in 3GPP TS 28.314 [1] clause 6.2.1 shall apply. - -#### 6.7.1.3 Procedures - -Functional elements involved in Plug and Connect, for example, IP Autoconfiguration services, DNS server, Certification Authority server, Security gateway and Software and Configuration Server (SCS) are described in 3GPP TS 28.315 [2] clause 4.2. - -Plug-and-Connect and related procedures are described in 3GPP TS 28.315 [2] clause 5. - -### 6.7.2 O1 Registration - -#### 6.7.2.1 Description - -The MnS Producer sends the O1 Registration Notification when it has completed its initialization phase and is ready to be managed by the O1 interface. It is applicable to any start-up either with or without persistent data. - -During start-up without persistent data, the MnS Producer can acquire its network layer parameters either via static procedures (e.g. pre-configured in the element) or via dynamic procedures (e.g. PNF Plug-n-Connect). The MnS - -Producer acquires the IP address of the MnS Consumer where the O1 Registration notification has to be sent. In addition, the MnS Producer also acquires the DN prefix [i.21] and optionally the RDN [i.21] values of the ManagedElement MOI to be created. - -During start-up with persistent data, the MnS Producer sends the O1 registration notification only to MnS Consumer(s) previously subscribed to the O1 registration notification (see clause 6.1.7 in this document for the subscription control capability). - -If no active subscription for the O1 Registration notification exists, then the same procedure defined for a start-up without persistent data, in accordance with clause 6.7.2.3.1 will be applicable. - -The O1 Registration MnS Producer will periodically send the O1 Registration Notification (at vendor specified intervals) until a O1 management connection is established. - -#### 6.7.2.2 Requirements - -REQ-PNFR-FUN-1: A MnS Producer shall support the capability to send the O1 Registration Notification when is ready to be managed via O1 interface - -REQ-PNFR-FUN-2: A MnS Producer shall support the capability to send the O1 Registration Notification to the subscribed MnS consumer(s) in case of start-ups where subscription information have been persisted. - -#### 6.7.2.3 Procedures - -##### 6.7.2.3.0 Overview - -The procedures in the present clause are examples adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -##### 6.7.2.3.1 First start-up and any following start-up without persistent data - -PNF Registration procedure is illustrated by Figure 6.7.2.3.1-1. The MnS Producer sends an HTTP/TLS o1Registration notification to the MnS Consumer after initialization and OAM services are ready for the O1 management connection establishment and then to be put into service (e.g. applying further logical configuration). - -The following procedure can be applied either to physical or virtual deployment. - -![Sequence diagram showing the registration notification process between MnS Consumer and MnS Producer. The MnS Producer sends a message 'Initialization completed (e.g. PnC in case of a PNF)' followed by 'OAM Services are available'. Then, the MnS Producer sends an 'o1Registration' message (labeled '1 o1Registration') to the MnS Consumer. The MnS Consumer responds with 'Register MnS Producer'.](02db3d5ca2c08af069727d3709c4a6fb_img.jpg) - -``` - -sequenceDiagram - participant MnS Consumer - participant MnS Producer - Note right of MnS Producer: Initialization completed (e.g. PnC in case of a PNF) - Note right of MnS Producer: OAM Services are available - MnS Producer->>MnS Consumer: 1 o1Registration - Note left of MnS Consumer: Register MnS Producer - -``` - -Sequence diagram showing the registration notification process between MnS Consumer and MnS Producer. The MnS Producer sends a message 'Initialization completed (e.g. PnC in case of a PNF)' followed by 'OAM Services are available'. Then, the MnS Producer sends an 'o1Registration' message (labeled '1 o1Registration') to the MnS Consumer. The MnS Consumer responds with 'Register MnS Producer'. - -Figure 6.7.2.3.1-1 Registration Notification in case of a start-up without persistent data - -Pre-condition: - -- Initialization procedure completed - - In case of a physical deployment, Plug-n-Connect has been completed. - - In case of a virtualized deployment, the deployment and the initialization of the virtualized components has been completed (e.g. NF Deployments have been instantiated via O2 interface). - - MnS Producer has acquired its network layer parameters as the IP address of the MnS Consumer where the O1 Registration notification needs to be sent as well as the DN prefix [i.21] and optionally the RDN [i.21] values of the ManagedElement MOI to be created. -- OAM Services are available - -Procedure: - -1. MnS Producer sends o1Registration notification to MnS Consumer over HTTP/TLS. Mutual certificate authentication is performed. The MnS Producer will periodically send the o1Registration notification (at vendor specified intervals) until a O1 management connection is established. - -Post-condition: - -- MnS Consumer registers the MnS Producer so that it can be managed. -- MnS Consumer establishes the NETCONF session and check the MnS Producer configuration data. - -##### 6.7.2.3.2 Following start-up with persistent data - -O1 Registration procedure in case of a start-up with persistent data is illustrated by Figure 6.7.2.3.2-1. - -The following procedure can be applied either to physical or virtual deployment. - -![Sequence diagram showing the registration notification for a MnS Producer start-up with persistent data. The diagram shows the MnS Consumer and MnS Producer at the top and bottom. The MnS Consumer is subscribed to the O1Registration notification type. The MnS Producer starts up with persistent data, and OAM services become available again. The MnS Producer then sends an o1Registration notification (1 o1Registration) to the MnS Consumer, which registers the MnS Producer.](6584b95e34ea1f0b67144aa841db0863_img.jpg) - -``` - -sequenceDiagram - participant MnS Consumer - participant MnS Producer - Note left of MnS Consumer: Subscribed to O1Registration notification type - Note right of MnS Producer: Start-up with persistent data - Note right of MnS Producer: OAM Services are available again - MnS Producer->>MnS Consumer: 1 o1Registration - Note left of MnS Consumer: Register MnS Producer - -``` - -Sequence diagram showing the registration notification for a MnS Producer start-up with persistent data. The diagram shows the MnS Consumer and MnS Producer at the top and bottom. The MnS Consumer is subscribed to the O1Registration notification type. The MnS Producer starts up with persistent data, and OAM services become available again. The MnS Producer then sends an o1Registration notification (1 o1Registration) to the MnS Consumer, which registers the MnS Producer. - -Figure 6.7.2.3.2-1 Registration Notification for a MnS Producer start-up with persistent data - -Pre-condition: - -- MnS Producer has persistent data including the subscribed MnS Consumer(s) per O1Registration notification -- MnS Producer has an active notification subscription (i.e. MnS Consumer(s) subscribed to receive O1Registration notification) -- OAM services in the MnS Producer are available again - -Procedure: - -1. MnS Producer sends o1Registration notification to MnS Consumer over HTTP/TLS in case of a start-up that require the re-establishment of the O1 interface, when the OAM services are available again. Mutual certificate authentication is performed. The MnS Producer will periodically send the o1Registration notification until a NETCONF session is established. - -Post-condition: - -- MnS Consumer takes advantage of the information that the MnS Producer is available again to register the MnS Producer status, re-establish the NETCONF session and check the MnS Producer configuration data. - -#### 6.7.2.4 Operations and Notifications - -Refer to clause 5.1 for details on O1 notification formats, including SDO O1 format and VES O1 format notifications, categorized as Legacy VES and Harmonized VES. - -The O-RAN-specified O1 Registration notification is: - -- o1Registration, defined in table 6.7.2.4-1. - -**Table 6.7.2.4-1: O1 registration notification parameters** - -| Parameter Name | S | Documentation and Allowed Value | Properties | -|------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------| -| objectClass | M | ManagedElement.objectClass
Class of the managed object, registering for service as defined in clause 11.1.1.7.2 of 3GPP TS 28.532 [3]. | Type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A | -| objectInstance | M | ManagedElement.objectInstance
Instance of the managed object, registering for service as defined in clause 11.1.1.7.2 of 3GPP TS 28.532 [3]. | Type: DN
multiplicity: 1
isOrdered: N/A
isUnique: N/A | -| notificationId | M | NotificationId
Identifier for the subject notification as defined in clause 11.1.1.7.2 of 3GPP TS 28.532 [3]. | Type: Integer
multiplicity: 1
isOrdered: N/A
isUnique: N/A | -| notificationType | M | " o1Registration " | Type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A | -| eventTime | M | Time when the NF is sending the registration as defined in clause 11.1.1.7.2 of 3GPP TS 28.532 [3].
DateTime type as defined in 3GPP TS 28.622 [7]. | Type: DateTime
multiplicity: 1
isOrdered: N/A
isUnique: N/A | -| systemDN | M | DN of the MnS Producer of the notification as defined in clause 11.1.1.7.2 of 3GPP TS 28.532 [3].
NOTE: If an MnSAgent MOI is present, systemDN shall be the DN of an MnSAgent. If no MnSAgent is present the DN of the root MOI shall be used. | Type: DN
multiplicity: 1
isOrdered: N/A
isUnique: N/A | -| serialNumber | M | serialNumber = serial number of the unit as defined in clause 4.4.1 of 3GPP TS 28.632 [25].
Applicable only in case of a PNF. | Type: String
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A | -| vendorName | M | vendorName = name of the NF vendor as defined in clause 4.4.1 of 3GPP TS 28.622 [7]. | Type: String
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A | -| oamV4IpAddress | M | IPv4 OAM IP address to be used by the manager to contact the NF.
Either oamV4IpAddress or oamV6IpAddress shall be provided depending upon what the network function supports. | Type: String
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A | -| oamV6IpAddress | M | IPv6 OAM IP address to be used by the manager to contact the NF.
Either oamV4IpAddress or oamV6IpAddress shall be provided depending upon what the network function supports. | Type: String
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A | -| macAddress | O | MAC address of the OAM of the unit | Type: String
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A | -| unitFamily | O | vendorUnitFamilyType = general type of HW unit as defined in clause 4.4.1 of 3GPP TS 28.632 [25]. | Type: String
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A | -| unitType | O | vendorUnitTypeNumber = vendor name for the unit as defined in clause 4.4.1 of 3GPP TS 28.632 [25]. | Type: String
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A | -| modelNumber | O | versionNumber = version of the unit from the vendor as defined in clause 4.4.1 of 3GPP TS 28.632 [25]. | Type: String
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A | - -| Parameter Name | S | Documentation and Allowed Value | Properties | -|-----------------------|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------| -| softwareVersion | O | swVersion = Version identifier of the software unit. This is the software provided by the vendor at onboarding to be run on this version of the NF and can contain multiple underlying software images as defined in clause 4.4.1 of 3GPP TS 28.632 [25] | Type: String
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A | -| softwareName | O | swName = software release name as defined in clause 4.4.1 of 3GPP TS 28.632 [25]. | Type: String
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A | -| restartReason | O | Reason the NF restarted, if known | Type: String
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A | -| manufactureDate | O | dateOfManufacture = manufacture date of the unit as defined in clause 4.4.1 of 3GPP TS 28.632 [25].
DateTime type as defined in 3GPP TS 28.622 [7]. | Type: DateTime
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A | -| lastServiceDate | O | dateOfLastService = date of last service or repair of the unit as defined in clause 4.4.1 of 3GPP TS 28.632 [25].
DateTime type as defined in 3GPP TS 28.622 [7]. | Type: DateTime
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A | -| additionalInformation | O | Additional registration fields if needed. The content of the attribute is a list of attributeNames and string attributeValues.
NameValuePair type as defined in 3GPP TS 28.111 [26]. | Type: NameValuePair
multiplicity: 0..*
isOrdered: False
isUnique: True | - -## 6.8 PNF Software Management Services - -### 6.8.0 Overview - -Software management services allow a PNF Software MnS Consumer to request a physical PNF Software MnS Producer to download, install, validate and activate a new software package and allow a physical PNF Software MnS Producer to report its software versions. - -### 6.8.1 Software Package Naming and Content - -PNF Software Package naming, content and format are vendor specific and do not require standardization in O-RAN. A PNF Software Package contains one or more files. Some of the files in the Software Package are optional for the PNF (example: a file that has not changed version). The PNF is aware of the content and format of its available Software Packages and can determine which files it needs to download. - -The softwarePackage Managed Object Class (MOC) contains attributes about a software package such as: - -- software package name; -- version; -- fileList; -- integrityStatus (valid, invalid, empty); -- runningState (active, passive); -- vendor; -- productName; -- softwareType (operational, factory); - -- etc. - -This MOC is applicable to VNFs and PNFs and is a generic term that O-RAN will use to refer to the software available on the PNF rather than the legacy term of software slot. - -The PNF creates one instance of softwarePackage for each software package supported concurrently on the PNF. Typically, a PNF will have two softwarePackage MOIs for operational software; one with runningState = active and one with runningState = passive. Some PNFs also have a softwarePackage MOI for the factory software which would be read only. O-RAN can have PNFs that support more than one passive slot. In this case the inventory query result would show multiple MOIs with runningState=passive. - -### 6.8.2 Software Inventory - -#### 6.8.2.1 Description - -The PNF Startup and Registration MnS Consumer sends a Software Inventory Request and retrieves information about the software packages on the PNF Software MnS Producer. - -#### 6.8.2.2 Requirements - -REQ-SWI-FUN-1: The PNF software management service producer shall have the capability to provide its authorized consumer information about the software packages on the PNF software management service producer. - -#### 6.8.2.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -![Sequence diagram titled 'Software Inventory' showing interactions between PNF Software MnS Consumer and PNF Software MnS Producer. The steps are: [1] Establish NETCONF Session, [2] NETCONF , Retrieve Software Inventory Information, [3] NETCONF , [4] Terminate NETCONF Session.](3252037b597c9317aced0feed4cb5af0_img.jpg) - -``` - -sequenceDiagram - participant Consumer as PNF Software MnS Consumer - participant Producer as PNF Software MnS Producer - Consumer->>Producer: [1] Establish NETCONF Session - Consumer->>Producer: [2] NETCONF - Note right of Producer: Retrieve Software Inventory Information - Producer-->>Consumer: [3] NETCONF - Consumer->>Producer: [4] Terminate NETCONF Session - -``` - -Sequence diagram titled 'Software Inventory' showing interactions between PNF Software MnS Consumer and PNF Software MnS Producer. The steps are: [1] Establish NETCONF Session, [2] NETCONF , Retrieve Software Inventory Information, [3] NETCONF , [4] Terminate NETCONF Session. - -Figure 6.8.2.3-1 Software Inventory - -Procedure: - -1. PNF Software MnS Consumer establishes NETCONF session with PNF Software MnS Producer. The NETCONF session has authorized read privileges into the identified section of the data store. - -2. PNF Software MnS Consumer sends NETCONF to retrieve an optionally filtered subset configuration from the running configuration datastore. can be used to identify the software package MOIs. GET retrieves configuration and operational state of softwarePackage MOIs: - - a. PNF Software MnS Producer retrieves software inventory information. -3. PNF Software MnS Producer returns requested data in NETCONF response. -4. PNF Software MnS Consumer terminates NETCONF session with PNF Software MnS Producer. - -### 6.8.3 Software Download - -#### 6.8.3.1 Description - -Software Download triggers the download of a specific software package to the PNF Software MnS Producer. This download service includes integrity checks on the downloaded software and the installation of the software into the software slot corresponding to the softwarePackage MOI. - -#### 6.8.3.2 Requirements - -REQ-SWD-FUN-1: The PNF software management service producer shall have the capability to allow its authorized consumer to specify the location of software that is to be downloaded and to specify into which softwarePackage the software is to be stored. - -REQ-SWD-FUN-2: The PNF software management service producer shall have the capability to verify if a software download is in progress and the ability to reject subsequent download commands until the one in progress completes. - -REQ-SWD-FUN-3: The PNF software management service producer shall have the capability to deny download of software if the download request is not valid for the PNF software management service producer. - -REQ-SWD-FUN-4: The PNF software management service producer shall have the capability to download needed files from a software server at a specified location. - -REQ-SWD-FUN-5: The PNF software management service producer shall have the capability to perform integrity checks on downloaded software. - -REQ-SWD-FUN-6: The PNF software management service producer shall have the capability to notify the PNF software management consumer with the software download result. - -#### 6.8.3.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -![](3c99312f83459559d9a301148555d7b9_img.jpg) - -**Software Download** - -``` - -sequenceDiagram - participant Consumer as PNF Software MnS Consumer - participant Producer as PNF Software MnS Producer - participant Server as Software Server - - Consumer->>Producer: [1] Establish NETCONF Session - Consumer->>Producer: [2] NETCONF - Note right of Producer: Validate Request - Producer-->>Consumer: [3] NETCONF - Consumer->>Producer: [4] Terminate NETCONF Session - Producer->>Server: [5] «FTPeS, SFTP or HTTPS» file download - Note right of Producer: Integrity check SW - Note right of Producer: Store SW in a persistent location - Note right of Producer: Update softwarePackage - - opt Download Progress Notifications - Producer-->>Consumer: [6] «HTTP/TLS» downloadFile Event - Producer-->>Consumer: [7] «HTTP/TLS» downloadFile Event - end - -``` - -**Figure 6.8.3.3-1 Software Download** - -Procedure: - -1. PNF Software MnS Consumer establishes NETCONF session with PNF Software MnS Producer. The NETCONF session has authorized execution privileges for retrieve file list and file-download rpcs. -2. PNF Software MnS Consumer sends NETCONF to trigger a download of the software located at remoteFilePath and save its information in softwarePackage: - - a. PNF Software MnS Producer validates the request. Validation includes determining if the operation can be performed. This is PNF Software MnS Producer specific but could include things like: checking that there is not a software download already in progress, softwarePackage is runningState = passive and softwareType = operational, etc. -3. PNF Software MnS Producer returns NETCONF . -4. PNF Software MnS Consumer terminates NETCONF session with PNF Software MnS Producer. -5. PNF Software MnS Producer initiates a secure connection and downloads via a secure file transfer protocol (FTPeS, SFTP or HTTPS) and according to the O-RAN Security Requirements and Controls Specifications [17] clause 5.2.2, the software package from remoteFilePath. PNF Software MnS Producer understands the software package format and downloads all the files it needs from the package. PNF Software MnS Producer decides where to store the software internally. This is PNF Software MnS Producer specific but could be a temporary location like /tmp: - - a. PNF Software MnS Producer integrity checks the downloaded software. This is PNF Software MnS Producer specific but could include checking-checksum, correct software for the hardware, etc. - - b. PNF Software MnS Producer stores the software in a persistent location. - - c. PNF Software MnS Producer updates softwarePackage attributes for the downloaded software. -6. (Optional) If the download takes a long time, PNF Software MnS Producer may send periodic downloadFile notifications to the PNF Software MnS Consumer with the current status of the download (download in progress, integrity checks passed, install complete). - -7. When download operation completes, PNF Software MnS Producer sends downloadFile event notification to PNF Software MnS Consumer with the final status of the download (success or the reason for failure). - -#### 6.8.3.4 Operations and Notifications - -Refer to clause 5.1 for details on O1 notification formats, including SDO O1 format and VES O1 format notifications, categorized as Harmonized VES. - -NOTE: There are no File Download notifications defined in the present document. - -### 6.8.4 Software Activation Pre-Check - -#### 6.8.4.1 Description - -Activation Pre-check is an optional Use Case that the Service Provider can choose to utilize prior to software activation to confirm that the PNF Software MnS Producer is in a good state to activate the new software and provide information needed for planning the timing of the software replacement--such as whether a reset or a data migration is required. - -#### 6.8.4.2 Requirements - -REQ-SPC-FUN-1: The PNF software management service producer shall have the capability to confirm that the software in the passive slot targeted for activation is good. - -REQ-SPC-FUN-2: The PNF software management service producer shall have the capability to determine whether the activation of the targeted software requires a reset and/or data migration. - -#### 6.8.4.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -![Sequence diagram titled 'Activation Pre-Check' showing interactions between PNF Software MnS Consumer and PNF Software MnS Producer. The sequence includes: [1] Establish NETCONF Session, [2] NETCONF , Perform Pre-Check (internal step), [3] NETCONF , and [4] Terminate NETCONF Session.](167a6aea873669eb91492f33d35d16de_img.jpg) - -``` - -sequenceDiagram - participant Consumer as PNF Software MnS Consumer - participant Producer as PNF Software MnS Producer - Note right of Producer: Perform Pre-Check - Consumer->>Producer: [1] Establish NETCONF Session - Producer-->>Consumer: [2] NETCONF - Note right of Producer: Perform Pre-Check - Producer-->>Consumer: [3] NETCONF - Consumer->>Producer: [4] Terminate NETCONF Session - -``` - -Sequence diagram titled 'Activation Pre-Check' showing interactions between PNF Software MnS Consumer and PNF Software MnS Producer. The sequence includes: [1] Establish NETCONF Session, [2] NETCONF , Perform Pre-Check (internal step), [3] NETCONF , and [4] Terminate NETCONF Session. - -Figure 6.8.4.3-1 Software Activation Pre-Check - -Procedure: - -1. PNF Software MnS Consumer establishes NETCONF session with PNF Software MnS Producer. - -2. PNF Software MnS Consumer sends NETCONF to trigger a pre-check of the software stored in softwarePackage and to return the results of the pre-check: - - a. PNF Software MnS Producer performs the activation pre-check which includes validating that the software in softwarePackage is good, whether the activation of the software in softwarePackage will result in a reset and whether data migration is needed, etc. -3. PNF Software MnS Producer returns NETCONF to the PNF Software MnS Consumer with the results of the pre-check. -4. PNF Software MnS Consumer terminates NETCONF session with PNF Software MnS Producer. - -### 6.8.5 Software Activate - -#### 6.8.5.1 Description - -PNF Software MnS Consumer triggers the activation of a software package on the PNF Software MnS Producer including data migration and reset if needed. - -#### 6.8.5.2 Requirements - -REQ-SWA-FUN-1: The PNF software management service producer shall have the capability to allow its authorized consumer to activate valid software in a specific softwarePackage. - -REQ-SWA-FUN-2: The PNF software management service producer shall have the capability to verify whether a software activation is in progress and deny a concurrent activation of software. - -REQ-SWA-FUN-3: The PNF software management service producer shall have the capability to deny activation of software if the activation request is not valid for the PNF software management service producer. - -REQ-SWA-FUN-4: The PNF software management service producer shall have the capability to activate the softwarePackage. - -REQ-SWA-FUN-5: The PNF software management service producer shall have the capability to reset the PNF software management service producer if the software activation requires it. - -REQ-SWA-FUN-6: The PNF software management service producer shall provide the capability for the PNF software management service producer to send a re-set reason notification to its authorized consumer if the activation results in a reset. - -REQ-SWA-FUN-7: The PNF software management service producer shall have the capability to perform data migration on the PNF software management service producer if the software activation requires it. - -REQ-SWA-FUN-8: The PNF software management service producer shall have the capability to fall back to the previously active software if the new software cannot be activated. - -REQ-SWA-FUN-9: The PNF software management service producer shall have the capability to fall back to the factory software if the new and the previously active software cannot be activated. - -#### 6.8.5.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -![Sequence diagram for Software Activate between PNF Software MnS Consumer and PNF Software MnS Producer. The process starts with establishing a NETCONF session [1], followed by a software-activate RPC [2]. The Producer validates the request and sends a reply [3]. After terminating the session [4], the Producer activates the software. Conditional blocks handle data migration, resets (sending a resetReason Event [5]), and fallback on failure. An optional block covers progress notifications, including softwareActivate Events [6, 7] and a notifyMOIAttributeValueChange Event [8] after a configuration change, ending with a database reconciliation by the Consumer.](b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg) - -**Software Activate** - -``` - -sequenceDiagram - participant Consumer as PNF Software MnS Consumer - participant Producer as PNF Software MnS Producer - Consumer->>Producer: [1] Establish NETCONF Session - Consumer->>Producer: [2] NETCONF - Note right of Producer: Validate request - Producer-->>Consumer: [3] NETCONF - Consumer->>Producer: [4] Terminate NETCONF Session - Note right of Producer: Activate Software - alt if Data Migration or Reset are needed then - alt if Data Migration Needed then - Note right of Producer: Migrate Data if needed - end - alt if Reset Needed then - Note right of Producer: Reset - Producer->>Consumer: [5] «HTTP/TLS» resetReason Event - end - end - alt if Activation fails then - Note right of Producer: Fallback if failure - end - opt Activation Progress Notifications - Producer->>Consumer: [6] «HTTP/TLS» softwareActivate Event - Producer->>Consumer: [7] «HTTP/TLS» softwareActivate Event - Note right of Producer: Config change occurs - Producer->>Consumer: [8] «HTTP/TLS» notifyMOIAttributeValueChange Event - Note left of Consumer: Reconcile Database - end - -``` - -Sequence diagram for Software Activate between PNF Software MnS Consumer and PNF Software MnS Producer. The process starts with establishing a NETCONF session [1], followed by a software-activate RPC [2]. The Producer validates the request and sends a reply [3]. After terminating the session [4], the Producer activates the software. Conditional blocks handle data migration, resets (sending a resetReason Event [5]), and fallback on failure. An optional block covers progress notifications, including softwareActivate Events [6, 7] and a notifyMOIAttributeValueChange Event [8] after a configuration change, ending with a database reconciliation by the Consumer. - -Figure 6.8.5.3-1 Activate Software - -##### Procedure: - -1. PNF Software MnS Consumer establishes NETCONF session with PNF Software MnS Producer. -2. PNF Software MnS Consumer sends NETCONF to trigger an activation of the software in softwarePackage: - - a. PNF Software MnS Producer validates the request. This is PNF Software MnS Producer specific but could include things like checking that there is not a software activation already in progress, softwarePackage is runningState = passive and integrityStatus = valid, etc. -3. PNF Software MnS Producer returns status to the PNF Software MnS Consumer in the NETCONF response: - - a. PNF Software MnS Producer performs the steps needed to make the softwarePackage the active one. This is PNF Software MnS Producer specific but includes things like updating the runningState of the about-to-be-active and previously-active software packages. -4. PNF Software MnS Consumer terminates NETCONF session with PNF Software MnS Producer. - - -(Optional) PNF Software MnS Producer performs data migration if necessary. PNF Software MnS Producer knows whether this is necessary. -5. (Optional) PNF Software MnS Producer performs reset if necessary. PNF Software MnS Producer knows whether reset is necessary. If a reset occurs, PNF Software MnS Producer sends a resetReason notification to the PNF Software MnS Consumer with the reason for the reset; in this case software activation. - - -(Optional) If the PNF Software MnS Producer cannot activate the software, PNF Software MnS Producer has recovery logic to fall back to the previously active software and potentially fallback to the factory software in a worst-case scenario. -6. (Optional) If the activation takes a long time, PNF Software MnS Producer sends periodic softwareActivate notifications to PNF Software MnS Consumer with the current status of the activation (e.g. activation in progress, data migration successful). -7. After activation operation completes, PNF Software MnS Producer sends a softwareActivate notification to PNF Software MnS Consumer with the final status of the activation. -8. PNF Software MnS Producer sends notifyMOIAttributeValueChange to the PNF MnS Consumer updating the active software running on the PNF. - -#### 6.8.5.4 Operations and Notifications - -Refer to clause 5.1 for details on O1 notification formats, including SDO O1 format and VES O1 format notifications, categorized as Harmonized VES. - -NOTE: There are no Software Activate notifications defined in the present document. - -## 6.9 PNF Reset Management Services - -### 6.9.0 Overview - -PNF Reset Management Services allow a PNF Reset MnS Consumer to trigger a reset of a HW unit of a PNF Reset MnS Producer on command. - -### 6.9.1 PNF Reset Command - -#### 6.9.1.1 Description - -The PNF Reset Command procedure allows a PNF Reset MnS Consumer to trigger a reset of a HW unit of a PNF Reset MnS Producer on command. Any HW unit that is resettable via a reset command is represented by a managed object - -instance (MOI) and is able to be identified by a distinguished name (DN). The NETCONF RPC command identifies the unit to reset by the DN. The unit to reset can be the entire PNF or a resettable HW subcomponent of the PNF. A resettable HW subcomponent of a PNF is a subcomponent of a PNF that is able to be independently reset and whose PNF Reset MnS Producer supports a reset command for the subcomponent. It is vendor and PNF-specific whether a PNF has resettable HW subcomponents. The reset command also has an attribute to identify the type of reset requested. The types of reset commands that a PNF supports are vendor and PNF specific. O-RAN O1 Interface Specification specifies two mandatory reset command types that every PNF supports: conditional and forced. A conditional reset command can be rejected by the PNF Reset MnS Producer depending on the conditions on the PNF, for example if the unit to reset is not in a proper state to reset, such as, if there is an emergency call in progress on the unit. A valid forced reset command cannot be rejected. Valid means that the unit to reset supports a reset command. Invalid forced resets will be rejected, for example, if the unit to reset is not a resettable HW unit, such as a cell. Vendors are allowed to extend the O1 specified reset command types to add vendor and PNF specific reset command types. - -#### 6.9.1.2 Requirements - -REQ-RM-FUN-1: The PNF Reset MnS Producer shall support the capability for a PNF Reset MnS Consumer to trigger a reset of a HW unit of the PNF Reset MnS Producer on command. - -REQ-RM-FUN-2: The PNF Reset MnS Producer shall support reset command types conditional and forced. - -REQ-RM-FUN-3: The PNF Reset MnS Producer shall be allowed to reject a conditional reset command type. - -NOTE 1: The validations performed and the reasons for a conditional reset rejection, if any, are vendor and PNF specific. - -REQ-RM-FUN-4: The PNF Reset MnS Producer shall not be allowed to reject a valid forced command reset type. - -NOTE 2: Valid means that the unit to reset supports a reset command. Invalid forced resets will be rejected, for example, if the unit to reset is not a resettable HW unit, such as a cell. - -#### 6.9.1.3 Procedures - -The procedure in the present clause is an example adding to the reader's understanding of the interactions for the corresponding Management Service, aiming to help with the implementation of the O1 Interface specification. It outlines a possible flow and does not introduce new conformance requirements. - -This procedure shows how a PNF Reset MnS Consumer triggers a reset of a HW unit of a PNF Reset MnS Producer on command. The HW unit to reset is identified by the input attribute. The type of reset command is identified by the input attribute. The output attribute returned in the NETCONF response indicates whether the reset command has been accepted. The unit is reset after the NETCONF response is returned. The reason for the reset (e.g., conditional reset command or forced reset command) is persistently stored by PNF Reset MnS Producer before executing the reset - -![Sequence diagram for PNF Reset Command. It shows four steps: 1. PNF Reset MnS Consumer sends a NETCONF to the PNF Reset MnS Producer. 2. The Producer validates the command and saves the reset reason. 3. The Producer responds with a NETCONF . 4. The Producer resets the unit. The diagram uses dashed lines for lifelines and solid arrows for messages.](52c40e2f443985dc63f45dec57d90c8c_img.jpg) - -**PNF Reset Command** - -``` - -sequenceDiagram - participant Consumer as PNF Reset MnS Consumer - participant Producer as PNF Reset MnS Producer - Note right of Producer: 2 Validate command -Save reset reason - Note right of Producer: 4 Reset unit - Consumer->>Producer: 1 NETCONF - Producer-->>Consumer: 3 NETCONF - -``` - -Sequence diagram for PNF Reset Command. It shows four steps: 1. PNF Reset MnS Consumer sends a NETCONF to the PNF Reset MnS Producer. 2. The Producer validates the command and saves the reset reason. 3. The Producer responds with a NETCONF . 4. The Producer resets the unit. The diagram uses dashed lines for lifelines and solid arrows for messages. - -**Figure 6.9.1.3-1 PNF Reset Command** - -##### **Pre-conditions:** - -- PNF Reset MnS Consumer has established a NETCONF session to the PNF Reset MnS Producer as described in Provisioning Management Services, clause 6.1.8. The NETCONF session has authorized execution privileges for RPC. -- (Optionally) PNF Reset MnS Consumer has locked the appropriate DS of the PNF Reset MnS Producer as described in Provisioning Management Services, clause 6.1.10. - -##### **Procedure:** - -1. PNF Reset MnS Consumer sends NETCONF to PNF Reset MnS Producer, indicating the unit to reset and the type of reset command. -2. PNF Reset MnS Producer validates the command. Validation is vendor and PNF specific but typically includes verifying that the is resettable and can be reset at this time. A conditional reset command type allows the PNF Reset MnS Producer to reject the reset command, depending on the conditions on the PNF, for example if an emergency call is in progress. The conditions are vendor and PNF specific. A valid forced reset command type cannot be rejected. Valid means that the unit to reset supports a reset command. Invalid forced resets will be rejected, for example if the unit to reset is not a resettable HW unit, such as a cell. If the reset command is accepted, the reset reason (e.g., conditional reset command or forced reset command) is stored persistently on the PNF Reset MnS Producer. -3. PNF Reset MnS Producer responds, indicating in the attribute whether the command is accepted. If the command is rejected, the contains an element with the reason for the rejection. -4. Unit is reset. - -##### **Post-conditions:** - -- (Optionally) PNF Reset MnS Consumer unlocks the DS of the PNF Reset MnS Producer after sending the reset command, as described in Provisioning Management Services, clause 6.1.11. -- (Optionally) PNF Reset MnS Consumer terminates the NETCONF session to the PNF Reset MnS Producer after sending the reset command, as described in Provisioning Management Services, clause 6.1.9. - -#### 6.9.1.4 Operations - -Information Model and YANG solution set for the NETCONF RPC command and its attributes will be specified in the O-RAN O1 Network Resource Model Specification [i.16]. - -### 6.9.2 Notifications - -REQ-RN-FUN-1: A PNF MnS Producer shall support the capability to inform a PNF MnS Consumer that a reset has occurred and the reason that a HW unit has reset. - -REQ-RN-FUN-2: A PNF MnS Producer shall save the reason for a reset persistently before resetting. - -NOTE 1: This requirement applies to resets that occur under the control of the PNF. - -REQ-RN-FUN-3: If a reset reason has not been saved persistently, the PNF MnS Producer shall set the reset reason to unknown in the notification. - -NOTE 2: This requirement applies to resets that occur unexpectedly before the reset reason could be stored. - -## 6.10 Void - -# --- Annex A: Void - -# Annex B: (informative) Guidelines and Example for stdDefined VES Events - -## B.1: Guidelines for use of stdDefined VES for sending 3GPP-specified or O-RAN-specified O1 notifications - -A stdDefined VES event, as specified in VES Event Listener Specification [18], allows a VES event to carry, as its payload, a notification specified by an SDO. In the case of O-RAN O1 Interface Specification, a harmonized stdDefined VES event carries either a 3GPP-specified O1 notification or an O-RAN-specified O1 notification as its payload. - -3GPP has published an informative Annex B in 3GPP TS 28.532 [3] providing guidelines for the integration of 3GPP-specified notifications with VES. This annex expands on the information provided by 3GPP, including information on how to include O-RAN-specified O1 notifications in a VES stdDefined event. - -When an O-RAN and 3GPP compliant ME supports VES stdDefined events for sending asynchronous notifications, a 3GPP-specified O1 notification, as defined by 3GPP, or an O-RAN-specified O1 notification, as defined by O-RAN, is included in the event. - -A VES common event header, as defined by VES Event Listener Specification [18], is added to the notification. - -In VES, the domain field in the common event header is used to route the event to the proper consumers and to map to a schema for the event payload. VES Event Listener Specification [18] added a new domain field enumeration value called stdDefined that indicates that the event is complying with a schema defined by a standards body. - -An additional field was added to the VES common event header called stdDefinedNamespace, which contains a valid namespace as defined by the standards body. This field is only populated when the domain is stdDefined. 3GPP has defined four namespaces in 3GPP TS 28.532 [3] Annex B; namely 3GPP-Provisioning, 3GPP-Heartbeat, 3GPP-FaultSupervision and 3GPP-PerformanceAssurance. O-RAN has defined a namespace for the notifications it defines. Refer to clause 5.2.2 for details. A VES collector uses the stdDefinedNamespace, along with the stdDefined domain, to route the event to the correct consumer. - -A stdDefined VES event has a field structure called stdDefinedFields, specified in VES Event Listener Specification [18]. This structure contains three properties: - -- schemaReference (type = string, format = uri) -- data (JSON object which is identical to the 3GPP or O-RAN notification) -- stdDefinedFieldsVersion (type = string, format = enum) - -The schemaReference, if present, is used to verify that the notification content is correct. 3GPP is publishing the notification schemas defined using OpenAPI, to a public repository, () so that schema references can be included in the event. Likewise, O-RAN will define its notification schemas using OpenAPI and publish them in a public repository. This repository is still to be created. - -The data element contains either a 3GPP-specified O1 notification, in JSON format, as specified in 3GPP TS 28.532 [3] or an O-RAN-specified O1 notification, in JSON format, as specified in O-RAN O1 Network Resource Model Specification [i.16]. - -The stdDefinedFieldsVersion provides the version of the stdDefinedFields structure, as defined by VES Event Listener Specification [18]. - -Clause B.2 provides an example of a stdDefined VES event for a new alarm notification. - -## B.2: Example stdnDefined VES event for a new alarm notification - -The following example illustrates the population of a new alarm notification using a stdnDefined VES event. - -The VES Common Header as shown in the example below, contains: - -- the domain set to stdnDefined -- the stdnDefinedNamespace set to 3GPP-FaultSupervision. - -The stdnDefinedFields structure as shown in the example below, contains: - -- the 3GPP schema reference for the 3GPP fault notification type -- the data element which contains the full 3GPP notifyNewAlarm fault notification -- the version of the stdnDefinedFields. - -Mapping of DN to URI is described in 3GPP TS 32.158 [i.15] - -| Mapping | DN (Distinguished Name) | URI part | -|------------------------------|------------------------------------------------|-------------------------------------| -| DN-prefix | "DC=operatorA.com,SubNetwork=south" (see note) | "south.SubNetwork.operatorA.com" | -| LDN | "ManagedElement=1,GNBDUFunction=1" | "/ManagedElement=1/GNBDUFunction=1" | -| NOTE: DC is Domain Component | | | - -The value for href in the example below is derived according to the table above, mapping the Distinguished Name prefix (DN-prefix) and the Local Distinguished Name (LDN), respectively, to the authority component and the path component of the URI in order to be globally unique. - -``` -{ - "event": { - "commonEventHeader": { - "domain": "stdnDefined", - "eventId": "stdnDefined-gNB-Nokia-000001", - "eventName": "stdnDefined-gNB-Nokia-ProcessingErrorAlarm-351", - "lastEpochMicrosec": 1594909352208000, - "priority": "Normal", - "reportingEntityName": "NOKb5309", - "sequence": 0, - "sourceName": "NOKb5309", - "startEpochMicrosec": 1594909352208000, - "stdnDefinedNamespace": "3GPP-FaultSupervision", - "timeZoneOffset": "UTC-05:00", - "version": "4.1", - "vesEventListenerVersion": "7.2" - }, - "stdnDefinedFields": { - "schemaReference": "https://forge.3gpp.org/rep/sa5/MnS/-/blob/Rel-18/OpenAPI/TS28111_FaultNrm.yaml#/components/schemas/NotifyNewAlarm", - "data": { - "href": "http://south.SubNetwork.operatorA.com/ManagedElement=1/GNBDUFunction=1", - "notificationId": 123, - "notificationType": "notifyNewAlarm", - "eventTime": "2023-11-15T23:20:50.52-05:00", - "systemDN": "DC=operatorA.com,SubNetwork=south,ManagedElement=1,MnSAgent=1", - "probableCause": 351, - "perceivedSeverity": "MAJOR", - "specificProblem": 7052, - "additionalText": "xyz", - "additionalInformation": { - "svc" : "alarm-svc-1" - }, - "alarmId": "15", - "alarmType": "PROCESSING_ERROR_ALARM" - }, - "stdnDefinedFieldsVersion": "1.0" - } - } -} -``` - -``` - } // stndDefinedFields - } //event -} -``` - -# --- Annex C: (informative) Streaming Trace Management Activation Example - -Example with Management-based Trace Activation, Data Reporting and Deactivation for Streaming Trace follows. The sequence below is based on 3GPP specifications which are referred in clause 6.4. - -![Sequence diagram showing the interaction between Provisioning MnS Consumer, Trace MnS Producer, and Trace MnS Consumer for streaming trace connection establishment, data reporting, and deactivation.](c3254408eadbf152632a8faf16310722_img.jpg) - -**Streaming Trace Connection Establishment, Data Reporting and Deactivation** - -``` - -sequenceDiagram - participant Provisioning MnS Consumer - participant Trace MnS Producer - participant Trace MnS Consumer - - Note left of Provisioning MnS Consumer: Provisioning MnS Consumer - Note right of Trace MnS Producer: Trace MnS Producer - Note right of Trace MnS Consumer: Trace MnS Consumer - - Provisioning MnS Consumer->>Trace MnS Producer: [1] Trace Job Configuration create traceJob MOI - Trace MnS Producer-->>Provisioning MnS Consumer: [2] notifyMOIChanges - - opt No connection to the Trace Mns Consumer exists - Trace MnS Producer->>Trace MnS Consumer: [3] establishStreamingConnection (HTTP POST request (SourceID, Trace Session Information)) - Trace MnS Consumer-->>Trace MnS Producer: [4] HTTP: response (Connection ID) - Trace MnS Producer->>Trace MnS Consumer: [5] HTTP GET request(Connection ID, Upgrade Header) - Trace MnS Consumer-->>Trace MnS Producer: [6] HTTP: response (Sec-WebSocket-Accept) - end - - opt - Trace MnS Producer->>Trace MnS Consumer: [7] AddStream Operation (HTTP ADD) - end - - Trace MnS Producer->>Trace MnS Producer: [8] Start Trace Session - Trace MnS Producer->>Trace MnS Consumer: [9] Trace Session Start administrative message - - loop while trace session is active - opt trace stream heartbeat - Note right of Trace MnS Producer: The criteria for sending heartbeat administrative messages are implementation specific - Trace MnS Producer->>Trace MnS Producer: [10] Heartbeat sending criteria are met - Trace MnS Producer->>Trace MnS Consumer: [11] Trace Stream Heartbeat administrative message - end - - loop Trace recording session handling - Trace MnS Producer->>Trace MnS Producer: [12] "start" triggering event detected - Trace MnS Producer->>Trace MnS Consumer: [13] Start Trace Recording Session and allocate new TRS (embedded in a reportStreamData Operation) - Trace MnS Producer->>Trace MnS Consumer: [14] Trace Recording Session Start administrative message - - loop until "stop" triggering event is detected - loop until reporting condition is satisfied - Trace MnS Producer->>Trace MnS Producer: [15] Capture trace record - end - Trace MnS Producer->>Trace MnS Consumer: [16] "reportStreamData(traceRecords)" - end - - Trace MnS Producer->>Trace MnS Producer: [17] Recording session complete/stop criteria are met - Trace MnS Producer->>Trace MnS Consumer: [18] Stop trace recording session - Trace MnS Producer->>Trace MnS Consumer: [19] Trace Recording Session Stop administrative message - end - end - - Provisioning MnS Consumer->>Trace MnS Producer: [20] Trace Session Deactivation/Configuration - Trace MnS Producer->>Trace MnS Producer: [21] Stop Trace Session - Trace MnS Producer->>Trace MnS Consumer: [22] Stop Trace Recording Session - - loop for each on-going Trace Recording Session - opt there are outstanding trace records - Trace MnS Producer->>Trace MnS Consumer: [23] "reportStreamData(traceRecords)" - end - Trace MnS Producer->>Trace MnS Consumer: [24] Trace Recording Session Stop administrative message - end - - Trace MnS Producer->>Trace MnS Consumer: [25] Trace Session Stop administrative message - - opt multiple streams exist - Trace MnS Producer->>Trace MnS Consumer: [26] deleteStream Operation (HTTP DELETE) - end - - opt - Trace MnS Producer->>Trace MnS Consumer: [27] terminateStreamingConnection(WebSocket Close Frame) - Trace MnS Consumer-->>Trace MnS Producer: [28] Terminate Connection - end - - Note left of Provisioning MnS Consumer: Provisioning MnS Consumer - Note right of Trace MnS Producer: Trace MnS Producer - Note right of Trace MnS Consumer: Trace MnS Consumer - -``` - -Sequence diagram showing the interaction between Provisioning MnS Consumer, Trace MnS Producer, and Trace MnS Consumer for streaming trace connection establishment, data reporting, and deactivation. - -**Figure C-1 : Streaming Trace Connection Establishment, Data Reporting and Deactivation Example** - -### Scenario: - -- Provisioning Management Service Consumer activates/configures Trace Session on Trace MnS Producer. This will be accomplished using Provisioning Management services described in clause 6.1. -- Trace MnS Producer sends a notifyMOIChanges to indicate the new MOI is created. Steps 3-6 are optional when no connection to trace MnS consumer exist. -- Trace MnS Producer needs to establish a connection to the Trace MnS Consumer to set up a streaming connection (streams are active at this time between the Producer and Consumer). This is done using the establishStreamingConnection Operation via an HTTP POST request containing MetaData associated with this Trace Session. -- Trace MnS Consumer responds with an acknowledgement that contains the ConnectionID needed by the Trace MnS Producer when requesting that the connection be upgraded to a WebSocket to support streaming of the trace data. -- Trace MnS Producer requests the upgrade of the connection to a WebSocket using the ConnectionID and an HTTP GET operation. -- Trace MnS Consumer accepts the upgrade and WebSocket is established. WebSocket will remain connected until the last streaming trace session active on the Trace MnS Producer is ended. - -NOTE: In this example, only one streaming trace session is active. - -- Optionally addStream operation is used to add a stream to the trace connection. -- Trace MnS Producer starts trace session, waiting for triggering event to occur. -- Trace MnS Producer sends trace session start administrative message to Trace MnS Consumer. -- Heartbeat sending criteria are met. The criteria about when to send Trace stream heartbeat administrative message are implementation specific. -- Trace stream heartbeat administrative message is sent to Trace consumer repeatedly. Trace stream heartbeat administrative message is used for monitoring whether the trace session connection is alive and can be executed parallel to other loops. -- "start" triggering event detected. -- A new trace recording session is started on the Trace MnS Producer. Each trace recording session has a unique Trace Recording Session (TRS) Reference associated with it. -- Trace recording session start administrative message is sent from Trace MnS Producer to Trace MnS Consumer. -- While this trace record is active, and the reporting criteria are not fulfilled, the Trace MnS Producer collects trace data. -- When the reporting criteria are fulfilled, either timer expires or the buffer fills, or the buffer has data and the "stop" triggering event is detected, the Trace MnS Producer sends a trace data report to the Trace MnS Consumer containing trace record data for active recording sessions in a trace session. These records are the payload of the reportStreamData operation. -- The criteria for the trace recording session completion or stop occurs (call ends, etc.). -- The Trace MnS Producer stops collecting data for this trace recording session. -- Trace MnS Producer sends trace recording session stop administrative message to Trace MnS Consumer. -- Provisioning Management Service Consumer deactivates the trace via procedures defined in clause 6.1 of the present document. Deactivation means that the trace data collection ceases, and the Trace MnS Producer stops all active trace recording sessions and sends data that it has collected up to this point, if any, for each active trace recording to the Trace MnS Consumer. -- Trace MnS Producer initiates the termination of the trace session. - -- For each active trace recording session, Trace MnS Producer initiates a Stop Trace Recording Session. -- Optionally if there are outstanding record(s) for this trace recording session that have not been streamed to the Trace MnS Consumer, Trace MnS Producer sends them as the payload of the reportStreamData operation. -- Trace MnS Producer informs the Trace MnS Consumer that this Trace Recording Session has ended by sending the trace record termination administrative message. The producer repeats this until all trace recording sessions for this trace session have been terminated. -- Trace MnS Producer sends the trace session stop administrative message to Trace MnS Consumer. -- Optionally the Trace MnS Producer sends the Trace MnS Consumer the deleteStream operation indicating that the stream has been removed in case the connection is used for multiple streams. -- Optionally when all active Trace Sessions between Trace MnS Producer and Trace MnS Consumer have ended, the WebSocket connection is to be torn down. Trace MnS Producer sends the Trace MnS Consumer the terminateSignalingConnection Operation which is a WebSocket close frame. -- Terminate connection. - -# Annex D: (normative) Recommendation for UE Identifier Format in Trace Header - -Specification 3GPP TS 32.423 [13] clause 5.2.2 defines *vendorExtension* IE in Trace Header as an ArrayList of String. The Trace Record Header should be encoded using GPB in Annex G of 3GPP TS 32.423 [13]. Based on Annex G, Trace Record Header in GPB is defined as - -``` - -message TraceRecordHeader { - int64 time_stamp = 1; - string nf_instance_id = 2; - string nf_type = 3; - bytes trace_reference = 4; - bytes trace_recording_session_ref = 5; - TraceRecordType trace_rec_type_id = 6; - bytes ran_ue_id = 7; - string payload_schema_uri = 8; - GlobalGnbId global_gnb_id = 9; - map vendor_extension = 10; -} - -``` - -Several UE identifiers and node identifiers are identified as necessary for trace record correlation. Refer to O-RAN architecture description [15] clause 5.5 for detailed information. - -To enable trace record correlation, a new map entry is defined for *vendor\_extension* to be used to send O-RAN UE/Node identifiers. - -Defined TraceRecordHeader field *vendor-extension* is in following format: - -``` -map vendor_extension = 10; -``` - -The map entry should be added for UE identifier and node identifiers is as below: - -First string in the map entry: value = "oranUENodeIdentifiers" - -Second string in the map entry: value = result of "print string" of message OranUEAndNodeIdentifiers - -**NOTE:** The O-RAN defined map entry for O-RAN UE/Node identifiers "oranUENodeIdentifiers" can co-exist with other vendor defined vendor-extension map entries. O-RAN defined map entry "oranUENodeIdentifiers" can be add in any position in the *vendor\_extension* map. - -``` - -message OranUEAndNodeIdentifiers { - optional OranConnectedEntity connected_entity_id =1; - optional OranUEId originator_ue_id = 2; - optional OranUEId connected_entity_ue_id =3; -} - -``` - -``` - -Message OranUEId{ - optional int64 amf_ue_ngap-id = 1; - optional int64 ran_ue_ngap_id =2; - optional int64 mme_ue_slap_id = 3; - optional int64 gnb_cu_ue_flap_id = 4; - optional int64 gnb_cu_cp_ue_elap_id = 5; - optional int64 gnb_cu_up_ue_elap_id= 6; - optional int64 traced_ng_ran_node_ue_xnap_id = 7; - optional int64 connected_ng_ran_node_ue_xnap_id = 8; - optional int64 m_enb_ue_x2ap_id = 9; - optional int64 c_rnti = 10; -} - -``` - -``` - -Message OranConnectedEntity { - oneof connected_entity_id { - bytes ng_connected_guami = 1; // AMF ID of the connected AMF - Guami ng_connected_guami_decoded = 2; // AMF ID of the connected AMF - GlobalGnbId xn_connected_global_gnb_id = 3; // ID of neighbouring gNB-CU-CP - OranGlobalEnbId xn_connected_global_enb_id = 4; // ID of neighbouring ng-eNB node - OranGlobalEnbId x2_connected_global_enb_id = 5; // ID of connected NSA eNB node - bytes sl_connected_mme= 6; // ID of connected MME - } -} - -``` - -``` - - Gummei s1_connected_mme_decoded= 7; // ID of connected MME - int64 f1_connected_du_id = 8; // ID of connected gNB-DU - int64 e1_connected_cuup_id = 9; // ID of connected gNB-CU-UP - } -} - -message GlobalEnbId { - bytes plmn_identity = 1; - int64 enb_id = 2; -} - -Message Guami { - bytes plmn_identity =1; - string amf_region_id=2; - string amf_set_id=3; - string amf_pointer=4; -} - -Message Gummei { - bytes plmn_identity =1; - string mme_grp_id=2; - string mme_code=3; -} - -``` - -Based on the value nf\_type (for example, gNB-CU-CP, gNB-CU-UP, gNB-DU) in the TraceRecordHeader, different types of UE identifiers and node identifier can be reported. For detail, refer to O-RAN architecture description [15] clause 5.5. - -# Annex (informative): Change History - -| Date | Revision | Description | -|------------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2019.03.18 | 0.01.00.00 | First draft of O-RAN OAM Interface Specification | -| 2019.03.28 | 0.01.01.00 | Updates from review remarks received | -| 2019.05.21 | 0.01.01.01 | Fault Supervision, Performance Assurance and File Management updates | -| 2019.05.28 | 0.01.01.02 | References, Abbreviations, Definitions, Provisioning, Communication Surveillance, PNF Start Up and Registration updates | -| 2019.06.13 | 0.01.01.03 | Diagrams for File Management converted to UML, Performance Assurance UML, PNF Software Management Updates | -| 2019.06.17 | 0.01.01.04 | Provisioning Updates | -| 2019.07.01 | 01.00 | Review Comments Addressed TSC approved copy | -| 2019.09.27 | 02.00 | Updates for late review comments, additional CM notifications, NETCONF requirements and updated references to 3GPP SA5 Rel-16. | -| 2020.03.03 | 03.00 | Update Heartbeat Management Service. New clauses for Subscription Control, Streaming PM, O-RAN Defined PM Measurements and an Annex showing examples for using the specified template for O-RAN defined PM Measurements. | -| 2020.08.18 | 04.00 | Update Introductory Material, Provisioning, Fault Supervision, Performance Assurance, Trace Management, and Heartbeat Management to incorporate | - -| | | | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | 3GPP Rel 16 CRs. Add Annex B for stdDefined event example and Annex C for Streaming Trace example. | -| 2020.08.31 | 04.00 | Update document with comments from WG1 review | -| 2021.03.11 | 04.01 | Incorporate approved CRs to prepare for v05.00.
Update Provisioning with approved CR 10.
Update Fault Supervision with approved CR 11. | -| 2021.04.27 | 04.02 | Update Software Download with approved CR 13. | -| 2021.05.24 | 04.03 | Incorporate approved Updates and Corrections CR 14
Updates to References, Security Protocols and Trace. | -| 2021.06.21 | 04.04 | Incorporate approved YANG Module Discovery CR 15 | -| 2021.06.22 | 05.00 | O1v5 incorporating CRs from 04.01.00 through 04.04.00 | -| 2021.10.25 | 06.00 | Incorporate approved CRs: PNF Reset CR 16, Performance Management CR 17, Cloudified NF Registration CR 18, Notify Alarm List Rebuilt CR 19, O1 Notifications CR 20 and References Updates CR 21. | -| 2022.03.15 | 07.00 | Incorporate approved CRs: PM Streaming Format Correction CR 22, 3GPP specified Notification VES format support CR 23, Annex C Streaming Trace Management CR 24, PNF Registration Notification CR 25, Rearrange PNF Reset Notification Requirements CR 26, Clarify counter naming requirement CR 27 and Notification capability CR 28. | -| 2022.07.18 | 08.00 |

Incorporate approved CRs: O-RAN counter name clarification CR 29, File management update CR 30, O1 Notification CR 31, Plug and Connect uplift CR 32, UE Identifiers for Trace header CR 33 and CM Notifications uplift CR 34.

Editorial changes related to the copyright clarification.

| -| 2022.08.31 | 08.00.01 | Incorporate approved CR 36 resolving outdated 3GPP references. | -| 2022.11.01 | 09.00.00 |

Incorporate approved CRs: Alignment with 3GPP and editorial modifications CR37, PM file format for NR measurements CR38.

Editorial changes related to the new document naming format.

Editorial changes related to application of embedded O-RAN styles template.

| -| 2022.11.21 | 09.00.01 | Editorial CR39 introduced changes for alignment with ODR, O-RAN TS Template and ETSI PAS - re-arranged and re-numbered clauses. Removal of author information from the history table. | -| 2023.01.31 | 09.00.02 | Incorporate approved CRs: UE Identifier schema CR40, Measurement job control clarification CR41 and File management correction CR42 | -| 2023.03.06 | 10.00 | Incorporate approved CRs: Clean-up of 3GPP TS 28.532 reference CR43, Correction of 3GPP TS 28.533 reference CR44, O-RU change in O1 introduction CR45, Split of normative and informative references CR46, Clean-up references CR47, Clean-up of introduction CR48, Remove out of scope Fault Notification requirements CR49 and Clean-up Fault Supervision Control Requirements CR50. | - -| | | | -|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2023.07.11 | 11.00 | Incorporate approved CRs: Reference update to O-RAN internal specifications CR33, Normative language clean-up CR52. | -| 2023.09.14 | 11.00.01 | Incorporate approved CR 53 clarifying the use of push-based file reporting for transfer of PM files. | -| 2023.10.11 | 11.00.02 | Incorporate approved CRs 54 fixing the PM use case reference and 55 updating the referenced 3GPP specifications versioning | -| 2023.10.30 | 12.00 | Incorporate approved CRs: SBMA terminology clean-up CR 56, Align Netconf server behaviour with 3GPP TS 28.532 CR 57, Update referenced specifications versioning CR 58, Security requirements alignment CR 59 and Heartbeat management capability clarification CR 60. | -| 2024.03.11 | 13.00 | Incorporate approved CRs: Correction of the stndDefined VES event examples CR 61, Alignment with the O1 consolidation WID CR 62, Alignment with 3GPP for non-specific references CR 63 and Notify Event addition CR 64.

Editorial changes (re-alignment of content between the Scope and Foreword clauses). | -| 2024.06.24 | 14.00 | Incorporate approved CRs: Removal of PM requirements (move to a dedicated TS) CR65, Add file preparation error notification for pull based scenario CR66, Add file preparation error notification for push based scenario CR67, Clarify the use of informative content (ETSI PAS triggered) CR68, Clarify O1 interface specification scope CR69, Fix editorial issue (ETSI PAS identified) in clause 6.5.4.3 CR70, File push clean-up CR71, Alarm history request requirements CR72, Align notification format across management services CR73, Add notifyAckStateChanged notification details CR74, ETSI EditHelp editorial corrections CR75 and 5G Performance Measurements clarification CR76. | -| 2024.10.02 | 14.00.01 | Incorporate approved CRs: Improving document consistency CR 77, Update of PNF Registration notification CR 78, General Requirements update CR 79, Editorial corrections CR 80, Alignment with 3GPP Rel-18 CR 81 | -| 2024.11.04 | 14.00.02 | Incorporate approved CRs: Alignment of 3GPP references for Trace and NRM CR 82, Alignment of 3GPP references for PM CR 83, Correction in NtfSubscriptionControl CR 84, Alignment of 3GPP references for FM CR 85, Alignment of 3GPP references for CM CR 86. | -| 2024.11.21 | 15.00 | Incorporate approved CRs: Correction of VES event mapping CR 87, Fault Supervision MnS Stage 3 references update CR 88, Addressing PMCountGroup and CUCountGroup compatibility CR 89. | -| 2025.03.06 | 16.00 | Incorporate approved CR: Security Requirements CR 90.

Editorial changes (additional clean-up after CR 90 implementation). | -| 2025.07.09 | 17.00 | Incorporate approved CR: PNF and Cloudified NF registration notification CR 91.

Editorial changes (alignment with the latest TS template). | -| 2025.11.18 | 18.00 | Incorporate approved CRs: Update the Fault Supervision for AlarmList states and reliability of Alarm Lists CR 92, Clarification in PNF registration notification CR 93, Alarm requirement clarification CR 94. | \ No newline at end of file diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/02db3d5ca2c08af069727d3709c4a6fb_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/02db3d5ca2c08af069727d3709c4a6fb_img.jpg deleted file mode 100644 index 44b24f2addc54ae3cb8b48fa9b29565c83cfc592..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/02db3d5ca2c08af069727d3709c4a6fb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a34dadf068ed3874ee2c8e45553fdccd680ac46b1c5aab885c2d0529e7b3e40d -size 44344 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/030c758fd425016b03290c8f11bef69d_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/030c758fd425016b03290c8f11bef69d_img.jpg deleted file mode 100644 index 32bc6379a1bce46bc855794e56d1a37095edbb32..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/030c758fd425016b03290c8f11bef69d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ded35e070495b5f27ea64a841c2bd7b9e524debbf26f48daea6d7692355a36cb -size 46306 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg deleted file mode 100644 index 12488b16e79bc731240ff69ee7112796091f6bb1..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9af24734f4a69ff099a838d1d687045969c6dfe5221c1557c84f061f7e5273fb -size 43582 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index afba4cbc0ac8c2c472a372fb4194c683e1ee58f5..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:000095a140bd7ffa463a618a958f3f4db3d9ae64e0cecbd298ce079b6b1ba3e8 -size 4157 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 1fc31743339a489814dba2fa6252662a721fba78..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f5e73a43cc343f471e57eec47d620d4591ec117e5371d272679ef34b2045e182 -size 4147 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg deleted file mode 100644 index 7e998374f5462bf1cefebe46c270d42ce980592c..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:75f91598b0ce1e57ae3bb57c1fc01d9fa357b7f12ff335d39fcf041fc3e5f596 -size 86033 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/167a6aea873669eb91492f33d35d16de_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/167a6aea873669eb91492f33d35d16de_img.jpg deleted file mode 100644 index 44d78be4339f785671a40d576e64bd736fa92bf8..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/167a6aea873669eb91492f33d35d16de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:54d21fac26cc029bd9a791965a46db4b90bc12b7467a65a01635d743e6ea99ca -size 63820 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index e9d056186f91071754a1bd66cc5b0f58f9cdcd1d..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a6feea577002af775f92c1c073ef8e278549447e23549760a568e59d2a4c42d6 -size 4142 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index e9d056186f91071754a1bd66cc5b0f58f9cdcd1d..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a6feea577002af775f92c1c073ef8e278549447e23549760a568e59d2a4c42d6 -size 4142 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index 1624885035e55cf6001c2009d780b95cc6680b68..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/1baaba7a6e54e77197475726c871067d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c92f80674dbfe05e46caab62e5fda53b55f3ffd6f04aadb315c070b5286ef4d9 -size 4189 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 7735eddde8d38f9f4e3c93389c2e933c747d5efa..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4fab26bc2d56d1330c95918ec308183e29618fb435c12ca3ab9e7b4f6d04b1c0 -size 4235 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg deleted file mode 100644 index 56367a21dfefa2cfeffa108f0d1e8dbaf3dec33a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:02474564cf0e0dbfb02f348cb51f7eaa9c1953df8cc258aa5523a4ba5185a158 -size 41131 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/3252037b597c9317aced0feed4cb5af0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/3252037b597c9317aced0feed4cb5af0_img.jpg deleted file mode 100644 index a2d50b842506105508d9ec31944a0c9f977c7e98..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/3252037b597c9317aced0feed4cb5af0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4311a6c1bf4c50f43ca9fc3f82db40ac08799930a44e238b3294e291f635e799 -size 59432 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index afba4cbc0ac8c2c472a372fb4194c683e1ee58f5..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:000095a140bd7ffa463a618a958f3f4db3d9ae64e0cecbd298ce079b6b1ba3e8 -size 4157 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/3c99312f83459559d9a301148555d7b9_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/3c99312f83459559d9a301148555d7b9_img.jpg deleted file mode 100644 index cfb13a2d9279656038961c34d49459ed534ee948..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/3c99312f83459559d9a301148555d7b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e41ede0076ddb964a16a9d42a22a45761f4877ab28f2fff63dd9a96988a16ef7 -size 89160 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/41aef1f5efab13d4f38f69e86c726062_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/41aef1f5efab13d4f38f69e86c726062_img.jpg deleted file mode 100644 index 8066c173e52e91b5a23683835e6ee83c3c56a8ad..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/41aef1f5efab13d4f38f69e86c726062_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8b4c084134591ddacfa583d785b37e879e019c015f93428094b16b6124fdc882 -size 83998 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/4a94ebc4d41217ce3083a255bfb9c538_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/4a94ebc4d41217ce3083a255bfb9c538_img.jpg deleted file mode 100644 index fdbdd066364a0c3c32857391bf0ff49ccaf7e5e9..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/4a94ebc4d41217ce3083a255bfb9c538_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7edec48994ca6bd9c7e09245bdd7fd2b02df04909865f728229efe9962225bd8 -size 52977 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg deleted file mode 100644 index 70bdb6305174fb4f9913eb273cfcfb52c2c3e045..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d318663dfd12110bfa65984e43885c738fe7ce4566c4c23fec4a059825a377a7 -size 42630 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 1624885035e55cf6001c2009d780b95cc6680b68..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c92f80674dbfe05e46caab62e5fda53b55f3ffd6f04aadb315c070b5286ef4d9 -size 4189 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/52c40e2f443985dc63f45dec57d90c8c_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/52c40e2f443985dc63f45dec57d90c8c_img.jpg deleted file mode 100644 index ee0b4d6cdbb6aea689aa85812003c8d84bcf6abe..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/52c40e2f443985dc63f45dec57d90c8c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3483b806f72f3aca351ef0139862d250acdaffd374ebec4a15e19ff0e2cecf3e -size 57356 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/5445597cceefaca1ac89e710fe339325_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/5445597cceefaca1ac89e710fe339325_img.jpg deleted file mode 100644 index 5fc37b98d8e1890cb1f6df92b94228b0b492b0e0..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/5445597cceefaca1ac89e710fe339325_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:863816b518d51f4156bc303c84c2be1b2471b16aa4a9509455fb54a182f494ca -size 50491 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index e9d056186f91071754a1bd66cc5b0f58f9cdcd1d..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a6feea577002af775f92c1c073ef8e278549447e23549760a568e59d2a4c42d6 -size 4142 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index a825d9b99f911d8f827b9553283b5ad21813fd46..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0b8fe5d6b51586629e54302f8e923644b5ad824f552cbb388a721c71c2fdb5bf -size 4236 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg deleted file mode 100644 index 098055350737fc9d23572f1d66dfd04fe0bd8505..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:faf2eca101e22fac44db7e77aa92e62c7503fbdd59b15f6849efa94dab643295 -size 41600 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/6584b95e34ea1f0b67144aa841db0863_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/6584b95e34ea1f0b67144aa841db0863_img.jpg deleted file mode 100644 index 38ae2562230a0ac1ed2d622e03498ab506bb80bb..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/6584b95e34ea1f0b67144aa841db0863_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f2a36edb02ee48c1f4b08eba13705e811bab5b0baecc86653c291bc4ea5e1781 -size 54035 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/6ca05954842b17f14dfd52f26b9d43d2_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/6ca05954842b17f14dfd52f26b9d43d2_img.jpg deleted file mode 100644 index 922d422c29e81c3c7e18118a2e04ed46780f108c..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/6ca05954842b17f14dfd52f26b9d43d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9992af42e43f9d7b05f96fcd7d134444b222e1f26d33cd54222dc4de99e6b09e -size 62296 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg deleted file mode 100644 index b664a17e8466d88e0def1a879b10dbfbf0a686a2..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:af922bd36550dadf048c2ca1216abc78c74a471b575233f2473de0734c2dc7de -size 46913 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index afba4cbc0ac8c2c472a372fb4194c683e1ee58f5..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:000095a140bd7ffa463a618a958f3f4db3d9ae64e0cecbd298ce079b6b1ba3e8 -size 4157 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 1624885035e55cf6001c2009d780b95cc6680b68..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c92f80674dbfe05e46caab62e5fda53b55f3ffd6f04aadb315c070b5286ef4d9 -size 4189 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 1624885035e55cf6001c2009d780b95cc6680b68..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c92f80674dbfe05e46caab62e5fda53b55f3ffd6f04aadb315c070b5286ef4d9 -size 4189 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index 1624885035e55cf6001c2009d780b95cc6680b68..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c92f80674dbfe05e46caab62e5fda53b55f3ffd6f04aadb315c070b5286ef4d9 -size 4189 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg deleted file mode 100644 index 50c75f8d1c3dd2b15d1833dbe75d5e9b251404ea..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/86d30a7d5a9cd4ee5456b5962ae3420a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:efab615b8d3ac9f7269cfbe3dcf23bf3e2db2e50c859d13081e16cb00656247d -size 60697 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index a1a021c6cced459e5a30319f5f0e9eb4cee8c91f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b15fb625969e26fe1f45975f7f45e9ff2d2a2b3a3006dbcaef44fb07ddd8d3bb -size 4016 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8b4befaffc5166da571069410e207aea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index e9d056186f91071754a1bd66cc5b0f58f9cdcd1d..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a6feea577002af775f92c1c073ef8e278549447e23549760a568e59d2a4c42d6 -size 4142 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index a1a021c6cced459e5a30319f5f0e9eb4cee8c91f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b15fb625969e26fe1f45975f7f45e9ff2d2a2b3a3006dbcaef44fb07ddd8d3bb -size 4016 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index afba4cbc0ac8c2c472a372fb4194c683e1ee58f5..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:000095a140bd7ffa463a618a958f3f4db3d9ae64e0cecbd298ce079b6b1ba3e8 -size 4157 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index b010af831285c9c63a054a530e5989b483c71618..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:104c0c1e691e47621828bdf020c177f54701defc5f4be092f4caaf9dfb2d87c7 -size 1559 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 7b84e262d2fc7e0b59b4101053a42526958b946a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0e7bdaaf5aacb655dae815886fc7e68b08115ae4458078ccf72b022c81a0a12c -size 4142 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index afba4cbc0ac8c2c472a372fb4194c683e1ee58f5..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:000095a140bd7ffa463a618a958f3f4db3d9ae64e0cecbd298ce079b6b1ba3e8 -size 4157 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index 1624885035e55cf6001c2009d780b95cc6680b68..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c92f80674dbfe05e46caab62e5fda53b55f3ffd6f04aadb315c070b5286ef4d9 -size 4189 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg deleted file mode 100644 index c6222ea40ceadc7c1879c59282bfd1e71cfee819..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c53b174a78729dbad0e061508a3b02ea9e70ff28298e5d99aa9478960e0372f5 -size 41409 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index afba4cbc0ac8c2c472a372fb4194c683e1ee58f5..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:000095a140bd7ffa463a618a958f3f4db3d9ae64e0cecbd298ce079b6b1ba3e8 -size 4157 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg deleted file mode 100644 index 3a32e00daf3fe5bb220787795cf765022a0a4445..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:37d61617b32cf3571f7ee5c5c132ff970ec3a68c1077c0a1b56a5c5fc1e27d03 -size 180390 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 1fc31743339a489814dba2fa6252662a721fba78..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f5e73a43cc343f471e57eec47d620d4591ec117e5371d272679ef34b2045e182 -size 4147 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/c3254408eadbf152632a8faf16310722_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/c3254408eadbf152632a8faf16310722_img.jpg deleted file mode 100644 index f73ad95b42ed2b76a6078f68cb6b3872ea5f2016..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/c3254408eadbf152632a8faf16310722_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9750c35cc8b61a8182bdf5c60ccaada10941cd970fdcc680723e3794d2161b9d -size 238383 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index afba4cbc0ac8c2c472a372fb4194c683e1ee58f5..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:000095a140bd7ffa463a618a958f3f4db3d9ae64e0cecbd298ce079b6b1ba3e8 -size 4157 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index 46520e39a12a41781ea798a8bb0d017f90522f07..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:cb848365dfb2754435ee7ba7278b03bd88b27022cfe98fa075843789fc030445 -size 4044 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/cfb98c691c1af5befe32ff9442eea511_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/cfb98c691c1af5befe32ff9442eea511_img.jpg deleted file mode 100644 index aecf2290001560492360dde6e7c40f326708e07a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/cfb98c691c1af5befe32ff9442eea511_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:28010c9a9194bb85f70125c4975357a8eca25d32edd29da5310d8f9f9d980ac7 -size 76828 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg deleted file mode 100644 index e6912e30d650e0dc1f4d7069b34885f9296122d2..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b4b39929e53fcaf0db0251df0c6b722770a114bfd1933fc1025f3258c96498d4 -size 42032 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg deleted file mode 100644 index 7341a63095f2d7ca215fbd43ae8ff0ae5eb3a01f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0de51b29c83e1d17f46a2c01958ef219bad7ce731669ebb00d4961c70b5ba469 -size 41475 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d79d33da852cb7bca3e87b400a15c3e8_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d79d33da852cb7bca3e87b400a15c3e8_img.jpg deleted file mode 100644 index a418688fd7eff774934377d5ee4a8e9ff0b5d675..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d79d33da852cb7bca3e87b400a15c3e8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0027c9470856b276003bd1016458e1f7b372ec65b21b19e0a7f57589ca482960 -size 36266 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index afba4cbc0ac8c2c472a372fb4194c683e1ee58f5..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:000095a140bd7ffa463a618a958f3f4db3d9ae64e0cecbd298ce079b6b1ba3e8 -size 4157 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index a1a021c6cced459e5a30319f5f0e9eb4cee8c91f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b15fb625969e26fe1f45975f7f45e9ff2d2a2b3a3006dbcaef44fb07ddd8d3bb -size 4016 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg deleted file mode 100644 index 9f723cfea2fba0b42965fd815d4f892ac63baa49..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/dcf37c460c66ec011dbe6ca08de44ff9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:49fa01063652526dcf39627fb327109c12657582f54dbef8f67c75327fcfe4be -size 97789 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/dfe556fea00682b09a59427aaf72051c_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/dfe556fea00682b09a59427aaf72051c_img.jpg deleted file mode 100644 index b4379495233475c66340824c58670e7e359fabf9..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/dfe556fea00682b09a59427aaf72051c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:306c80b4db4ea5f3c8300ed030d5cbd7cb40863a80bcd59e612249abfe5fefba -size 51602 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index a1a021c6cced459e5a30319f5f0e9eb4cee8c91f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b15fb625969e26fe1f45975f7f45e9ff2d2a2b3a3006dbcaef44fb07ddd8d3bb -size 4016 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index 7b84e262d2fc7e0b59b4101053a42526958b946a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0e7bdaaf5aacb655dae815886fc7e68b08115ae4458078ccf72b022c81a0a12c -size 4142 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index 225fb1222d7904f9c2b6c357c4fa70f1f38aa94e..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5b0474300d16834ee87b5d375cca8455e59c317dafad9ab383070739219adf41 -size 4044 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index afba4cbc0ac8c2c472a372fb4194c683e1ee58f5..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:000095a140bd7ffa463a618a958f3f4db3d9ae64e0cecbd298ce079b6b1ba3e8 -size 4157 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 1ac866ebfe23959f91f71ac6485464d244ed172c..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f0a7ae7e68d01cb903e9a35065f8afbf9764231801e9dc07633e72a6d3a25f1d -size 4016 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index 225fb1222d7904f9c2b6c357c4fa70f1f38aa94e..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5b0474300d16834ee87b5d375cca8455e59c317dafad9ab383070739219adf41 -size 4044 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index e9d056186f91071754a1bd66cc5b0f58f9cdcd1d..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/f74adaa1840504407cd4272995426f82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a6feea577002af775f92c1c073ef8e278549447e23549760a568e59d2a4c42d6 -size 4142 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg deleted file mode 100644 index 3b3e8f252ccbc179b15cf9cc0cafcf8e0754e0fa..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f369387db254446b877bea655e45c5cd946821bf137dbf67e8acae49e1e2ffa7 -size 55526 diff --git a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 56b29a1eaac4577dc99644fd17db444626ee709b..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1-Interface.0-R005-v18.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d31dafba964e82a03190d00e8ad0f98cb96d4d85c3f0841cd876e8a6c0d6b9a6 -size 4125 diff --git a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/doc.md b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/doc.md deleted file mode 100644 index 3669c2c10b3a3264bb913b7f19337ca5306b7b7c..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/doc.md +++ /dev/null @@ -1,7529 +0,0 @@ - - -# --- **O-RAN Work Group 10 (OAM for O-RAN)** - -# **O-RAN O1 Performance Measurements 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., 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..... 6 - -4 Requirements..... 7 - -4.1 General Requirements ..... 7 - -5 Performance Measurement definition..... 7 - -5.1 5G Performance Measurements ..... 7 - -Annex A (informative): O-RAN O1 defined Performance Measurements ..... 9 - -A.1 Overview ..... 9 - -A.2 O-CU-CP Performance measurements ..... 9 - -A.2.1 NR X2-C Interface performance measurements (O-CU)..... 9 - -A.2.2 NR Xn-C Interface performance measurements (O-CU)..... 10 - -A.2.3 NR F1-C Interface performance measurements (O-CU-CP) ..... 11 - -A.2.4 Number of UE Contexts for EN-DC ..... 12 - -A.2.5 Number of UE Contexts for SA..... 18 - -A.2.6 Monitoring of procedure for EN-DC..... 30 - -A.2.7 Monitoring of RRC Connection for EN-DC..... 35 - -A.2.8 Monitoring of RRC Connection for SA..... 38 - -A.2.9 Monitoring of Establishment calls for SA ..... 46 - -A.2.10 Monitoring of PDU session connection for SA..... 60 - -A.2.11 Monitoring of mobility for SA..... 67 - -A.2.12 Monitoring of RRC re-establishment for SA..... 72 - -A.2.13 Monitoring of connection status for SA ..... 77 - -A.2.14 Monitoring of procedure for NR-DC ..... 80 - -A.2.15 Monitoring of CA for SA ..... 86 - -A.3 O-CU-UP Performance measurements ..... 89 - -A.3.1 NR PDCP performance measurements..... 89 - -A.3.2 Void ..... 102 - -A.3.3 NR S1-U Interface Performance Measurements ..... 102 - -A.3.4 NR NG-U Interface Performance Measurements..... 104 - -A.3.5 NR X2-U Interface performance measurements (O-CU) ..... 105 - -A.3.6 NR Xn-U Interface performance measurements (O-CU) ..... 106 - -A.4 O-DU Performance measurements ..... 107 - -A.4.1 NR F1 Interface performance measurements..... 107 - -A.4.2 NR RLC performance measurements..... 115 - -A.4.3 NR MAC performance measurements ..... 131 - -A.4.4 NR UL HARQ performance measurements ..... 132 - -A.4.5 NR DL HARQ performance measurements ..... 136 - -A.4.6 NR UL Signal Quality Level performance measurements..... 140 - -A.4.7 NR DL Signal Quality Level performance measurements..... 150 - -A.4.8 NR Beamforming performance measurements ..... 157 - -A.4.9 NR RACH Usage performance measurements ..... 159 - -A.4.10 NR Timing Advance performance measurements..... 163 - -A.4.11 NR Cell Utilization performance measurements..... 164 - -A.4.12 Void ..... 190 - -A.4.13 O-RU Performance measurements measured at O-DU .....190 -A.4.14 O-RU Performance measurements measured at O-RU .....200 -Annex B (informative): 3GPP TS 32.404 template usage for O-RAN O1 defined Performance Measurements .....200 -Annex (informative): Change History .....202 - -# --- Foreword - -This Technical Specification (TS) has been produced by WG10 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 O-RAN Performance Measurements (PMeas) for 5G networks that may be supported on the O1 Interface [3]. - -# --- 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 (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in 3GPP Release 18. - -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 32.404: "Telecommunication management; Performance Management (PM); Performance Measurements; Definition and template". -- [2] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements". -- [3] O-RAN.WG10.TS.O1-Interface: "O-RAN O1 Interface Specification". -- [4] ORAN-WG4.TS.MP.0: "Management Plane Specification". -- [5] 3GPP TS 38.401: "NG-RAN; Architecture description". -- [6] 3GPP TS 38.323: "NR; Packet Data Convergence Protocol (PDCP) specification". -- [7] O-RAN.WG5.O-DU-O1: "O1 Interface specification for O-DU". -- [8] O-RAN.WG5.O-CU-O1: "O1 Interface specification for O-CU-UP and O-CU-CP". -- [9] O-RAN.WG10.TS.NRM: "O-RAN O1 Network Resource Model Specification". - -## 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 (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in 3GPP Release 18. - -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] O-RAN.WG4.TS.CUS: "O-RAN Control, User and Synchronization Plane". - -- [i.3] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)". -- [i.4] 3GPP TS 36.423: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP)". -- [i.5] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". -- [i.6] 3GPP TS 38.473: "NG-RAN; F1 Application Protocol (F1AP)". -- [i.7] O-RAN.WG5.TS.C.1-R004-v14.00: "O-RAN WG5 NR C-Plane Profile". - -# --- 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. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [i.1]. - -## 3.2 Symbols - -For the purposes of the present document, the symbols given in 3GPP TR 21.905 [i.1] and the following apply. A symbol defined in the present document takes precedence over the definition of the same symbol, if any, in 3GPP TR 21.905 [i.1]. - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [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 3GPP TR 21.905 [i.1]. - -| | | -|-------|--------------------------| -| PMeas | Performance Measurements | -| CC | Cumulative counter | -| SI | Status Inspection | - -# 4 Requirements - -## 4.1 General Requirements - -The general requirements in Table 4.1-1 apply to the definition of O-RAN performance measurements (including the template to be used): - -**Table 4.1-1 – General Requirements for O-RAN performance measurement definition** - -| Requirement label | Description | Motivation | -|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| -| REQ-PMeas-MC-1 | O-RAN O1 performance measurements shall be defined using the template specified in 3GPP TS 32.404 [1]. | Identify the template to be used for the definition of O1 performance measurements | -| REQ-PMeas-MC-2 | The Measurement Name of an O-RAN defined measurement shall begin with “OR” prefix to indicate that O-RAN is the source of the measurement definition. | | -| REQ-PMeas-MC-3 | The short form of the Measurement Name in the Measurement Type for an O-RAN defined measurement shall begin with "OR." to indicate that O-RAN is the source of the measurement definition. | | -| REQ-PMeas-MC-4 | In case O-RAN extends the definition of an existing 3GPP measurement, a new O-RAN measurement shall be defined. 3GPP Measurement Name should be part of the newly defined O-RAN Measurement Name. 3GPP measurement definition shall be referred in the newly defined O-RAN measurement definition, when possible. | | -| REQ-PMeas-MC-5 | When an O-RAN measurement is defined in 3GPP, the O-RAN measurement shall be deprecated.
Reference to the new 3GPP measurement shall be added.
NOTE: “Deprecated” means the measurement definition is valid, it can be used, but its use is discouraged. Deprecated measurement definition includes the replacement measurement definition specified as default. | | -| REQ-PMeas-MC-6 | When defining an O-RAN performance measurement with filtering, the 3GPP filtering mechanism defined in 3GPP TS 28.552 [2], clause 4.2 shall be used. | | - -# 5 Performance Measurement definition - -## 5.1 5G Performance Measurements - -The 3GPP defined 5G performance measurements for gNB are in 3GPP TS 28.552 [2] clause 5.1. - -The O-RAN defined measurements are defined in Annex A of the present document. An annex subclause is available per O-RAN NF as follows: - -- Annex A.2 per O-CU-CP -- Annex A.3 per O-CU-UP -- Annex A.4 per O-DU - -NOTE: The following area of improvements have been identified in the context of O-RAN O1 performance measurements that needs to be further analysed: - -- 1) *PmGroup* definition and harmonization with 3GPP sub-counters. 3GPP TS 28.552 [2] has already defined sub-counters per specific criteria (e.g., QoS, SNSSAI). If *PmGroup* is required, an harmonization of the performance groups between O-DU, O-CU-CP, and O-CU-UP NFs should be also considered. *PmGroup* stage 2, stage 3 and value ranges (e.g value 0 and valid subrange per id types) have to be specified and properly referenced from this document. - -NOTE: point 8 below has to be considered also in the context of the PmGroup definition and harmonization. - -- 2) Void -- 3) O-RAN O1 performance counters definitions where both overall counter and optional sub-counters per specific targets are defined should be aligned with similar 3GPP performance measurement definitions (see 3GPP TS 28.552 [2], clause 5.1.3.4.2). -- 4) O-RAN O1 Measurement result review to ensure valid values are used according to 3GPP TS 32.404 [1] and should be reviewed (e.g., kilobyte instead of an integer value representing the number of measured bits/bytes). -- 5) Void -- 6) Validate O-RAN defined sub-counter name for existing 3GPP counter, in line with existing O1 Performance measurement requirements of this document. -- 7) Improve "Description" subclause with information about "PmGroup" & "CuCountGroup" based on information in "Condition" subclause. -- 8) Review the naming rule of performance measurements in case of subcounters. When a performance measurement has multiple subcounters, currently it is hard to distinguish the subcounters. It is proposed that O-RAN O1 performance measurements reuse filter naming rules improvements introduced in 3GPP TS 28.552 [2], clause 4.2.2. - -# Annex A (informative): O-RAN O1 defined Performance Measurements - -## A.1 Overview - -The following clauses define the O-RAN O1 defined performance measurements per O-RAN NF. - -ANNEX A.2 O-CU-CP - -ANNEX A.3 O-CU-UP - -ANNEX A.4 O-DU - -NOTE 1: The usage of CuCountGroup and PMCountGroup in following clauses is based on WG5 models as specified in [7], [8]. This may be subject to change following completion of O1 consolidation activities and new WG10 models as specified in O1 NRM [9]. - -NOTE 2: How the MnS Consumer configures the Neighbour eNB Index/Neighbour gNB Index is not defined in this specification. - -## A.2 O-CU-CP Performance measurements - -### A.2.1 NR X2-C Interface performance measurements (O-CU) - -#### A.2.1.1 Transmitted X2-C messages - -- a) This counter provides the number of the transmitted X2-C messages per signal type that is non UE-associated or UE-associated signaling 3GPP TS 38.401 [5]. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever X2 C-plane message is transmitted when the signal type of the X2 C-plane message is group of *Signaltype*. -- d) Each measurement is an integer value representing the number of the transmitted X2-C messages per signal type that is non UE-associated or UE-associated signaling 3GPP TS 38.401 [5]. -- e) OR.L3M.TxX2CMesg.*Signaltype* (default), OR.X2.TxX2CMesg.*Signaltype* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Signaltype* is signal type: - - 0: non UE-associated - - 1: UE associated -- f) GNBCUCPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.1.2 Received X2-C messages - -- a) This counter provides the number of the received X2-C messages per signal type that is non UE-associated or UE-associated signaling 3GPP TS 38.401 [5]. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever X2 C-plane message is received when the signal type of the X2 C-plane message is group of *Signaltype*. -- d) Each measurement is an integer value representing the number of the received X2-C messages per signal type that is non UE-associated or UE-associated signaling 3GPP TS 38.401 [5]. -- e) OR.L3M.RxX2CMesg.*Signaltype* (default), OR.X2.RxX2CMesg.*Signaltype* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Signaltype* is signal type: - - 0: non UE-associated - - 1: UE associated -- f) GNBCUCPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.2.2 NR Xn-C Interface performance measurements (O-CU) - -#### A.2.2.1 Transmitted Xn-C messages - -- a) This counter provides the number of the transmitted Xn-C messages per signal type that is non UE-associated or UE-associated signaling 3GPP TS 38.401 [5]. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever Xn C-plane message is transmitted when the signal type of Xn C-plane message is group of *Signaltype*. -- d) Each measurement is an integer value representing the number of the transmitted Xn-C messages per signal type that is non UE-associated or UE-associated signaling 3GPP TS 38.401 [5]. -- e) OR.L3M.TxXnCMesg.*Signaltype* (default), OR.Xn.TxXnCMesg.*Signaltype* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Signaltype* is signal type: - - 0: non UE-associated - - 1: UE associated -- f) GNBCUCPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.2.2 Received Xn-C messages - -- a) This counter provides the number of the received Xn-C messages per signal type that is non UE-associated or UE-associated signaling 3GPP TS 38.401 [5]. -- b) CC - -- c) Measurement subcounter is incremented by 1 whenever Xn C-plane message is received when the signal type of the Xn C-plane message is group of *Signaltype*. -- d) Each measurement is an integer value representing the number of the received Xn-C messages per signal type that is non UE-associated or UE-associated signaling 3GPP TS 38.401 [5]. -- e) OR.L3M.RxXnCMesg.*Signaltype* (default), OR.Xn.RxXnCMesg.*Signaltype* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Signaltype* is signal type: - - 0: non UE-associated - - 1: UE associated -- f) GNBCUCPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.2.3 NR F1-C Interface performance measurements (O-CU-CP) - -#### A.2.3.1 Transmitted F1-C messages - -- a) This counter provides the number of the transmitted F1-C messages per signal type that is non UE-associated or UE-associated signaling 3GPP TS 38.401 [5]. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever F1 C-plane message is transmitted when the signal type of the F1 C-plane message is group of *Signaltype*. -- d) Each measurement is an integer value representing the number of the transmitted F1-C messages per signal type that is non UE-associated or UE-associated signaling 3GPP TS 38.401 [5]. -- e) OR.L3M.TxF1CMesg.*Signaltype* (default), OR.F1.TxF1CMesg.*Signaltype* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Signaltype* is signal type: - - 0: non UE-associated - - 1: UE associated -- f) GNBCUCPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.3.2 Received F1-C messages - -- a) This counter provides the number of the received F1-C messages per signal type that is non UE-associated or UE-associated signaling 3GPP TS 38.401 [5]. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever F1 C-plane message is received when the signal type of the F1 C-plane message is group of *Signaltype*. - -- d) Each measurement is an integer value representing the number of the received F1-C messages per signal type that is non UE-associated or UE-associated signaling 3GPP TS 38.401 [5]. -- e) OR.L3M.RxF1CMesg.*Signaltype* (default), OR.F1.RxF1CMesg.*Signaltype* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Signaltype* is signal type: - - 0: non UE-associated - - 1: UE associated -- f) GNBCUCPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.2.4 Number of UE Contexts for EN-DC - -#### A.2.4.1 Max SN terminated split bearer UE Contexts - -- a) This counter provides the maximum number of UE Contexts that are configured SN terminated split bearer. -- b) SI -- c) The measurement is obtained by reporting the maximum observed value of UE context that are configured SN terminated split bearer during the granularity period. - -These subcounters only cover Scell-users with P(S)Cell in the same gNB. The inter-gNB CA is not covered. - -- the triggers of addition of number of UE Contexts for PSCell - - received X2-AP: SgNB Reconfiguration Complete (to SN terminated split bearer) - - received X2-AP: SgNB Modification Confirm (Intra/Inter DU PSCell change using SRB1 (for target cell)) - - received RRC: RRC Reconfiguration Complete (Intra/Inter DU PSCell change using SRB3 (for target cell)) -- the triggers of subtraction of number of UE Contexts for PSCell - - received X2-AP: SgNB Reconfiguration Complete (to SN terminated MCG bearer) - - received X2-AP: SgNB Modification Confirm (Intra/Inter DU PSCell change using SRB1 (for source cell)) - - received F1-AP: UE Context Release Complete (Intra/Inter DU PSCell change using SRB3 (for source cell)) - - received X2-AP: UE Context Release -- the triggers of addition for SCell - - received X2-AP: SgNB Reconfiguration Complete (to SN terminated split bearer) - - received X2-AP: SgNB Modification Confirm (Intra/Inter DU PSCell change using SRB1 (for target cell), SCell Addition using SRB1) - - received RRC: RRC Reconfiguration Complete (Intra/Inter DU PSCell change using SRB3 (for target cell), SCell Addition using SRB3) -- the triggers of subtraction for SCell - - received X2-AP: SgNB Reconfiguration Complete (to SN terminated MCG bearer) - - received X2-AP: SgNB Modification Confirm (Intra/Inter DU PSCell change using SRB1 (for source cell), SCell deletion using SRB1) - - received F1-AP: UE Context Release Complete (Intra/Inter DU PSCell change using SRB3 (for source cell), SCell deletion using SRB3) - - received X2-AP: UE Context Release - -- d) Each measurement is an integer value representing the maximum number of UE Contexts that are configured SN terminated split bearer. -- e) OR.UECNTX.MaxSnSplitBearer.*Celltype* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.UEENDC.MaxSnSplitBearer.*Celltype* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Celltype* is the cell type: - - 0: PSCell - - 1: SCell -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.4.2 Max SN terminated MCG bearer UE Contexts - -- a) This counter provides the maximum number of UE Contexts that are configured SN terminated MCG bearer. -- b) SI -- c) The measurement is obtained by reporting the maximum observed value of UE Contexts that are configured SN terminated MCG bearer during the granularity period. - - the triggers of addition of number of UE Contexts - - received X2-AP: SgNB Reconfiguration Complete (to SN terminated MCG bearer) - - received X2-AP: SgNB Reconfiguration Confirm (to SN terminated MCG bearer) - - the triggers of subtraction of number of UE Contexts - - received X2-AP: SgNB Reconfiguration Complete (to SN terminated split bearer) - - received X2-AP: UE Context Release -- d) Each measurement is an integer value representing the maximum number of UE Contexts that are configured SN terminated MCG bearer. -- e) OR.UECNTX.MaxSnMcgBearer (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.UEENDC.MaxSnMcgBearer (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) GNBCUCPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.4.3 Average SN terminated split bearer UE Contexts - -- a) This counter provides the average number of UE Contexts that are configured SN terminated split bearer. -- b) SI -- c) The measurement is obtained by reporting the average observed value of UE Contexts that are configured SN terminated split bearer during the granularity period. - -These subcounters only cover SCell-users with P(S)Cell in the same gNB. The inter-gNB CA is not covered. - -- the triggers of addition of number of UE Contexts for PSCell - - received X2-AP: SgNB Reconfiguration Complete (to SN terminated split bearer) - - received X2-AP: SgNB Modification Confirm (Intra/Inter DU PSCell change using SRB1 (for target cell)) - - received RRC: RRC Reconfiguration Complete (Intra/Inter DU PSCell change using SRB3 (for target cell)) - - the triggers of subtraction of number of UE Contexts for PSCell - - received X2-AP: SgNB Reconfiguration Complete (to SN terminated MCG bearer) - - received X2-AP: SgNB Modification Confirm (Intra/Inter DU PSCell change using SRB1 (for source cell)) - - received F1-AP: UE Context Release Complete (Intra/Inter DU PSCell change using SRB3 (for source cell)) - - received X2-AP: UE Context Release - - the triggers of addition for SCell - - received X2-AP: SgNB Reconfiguration Complete (to SN terminated split bearer) - - received X2-AP: SgNB Modification Confirm (Intra/Inter DU PSCell change using SRB1 (for target cell), SCell Addition using SRB1) - - received RRC: RRC Reconfiguration Complete (Intra/Inter DU PSCell change using SRB3 (for target cell), SCell Addition using SRB3) - - the triggers of subtraction for SCell - - received X2-AP: SgNB Reconfiguration Complete (to SN terminated MCG bearer) - - received X2-AP: SgNB Modification Confirm (Intra/Inter DU PSCell change using SRB1 (for source cell), SCell deletion using SRB1) - - received F1-AP: UE Context Release Complete (Intra/Inter DU PSCell change using SRB3 (for source cell), SCell deletion using SRB3) - - received X2-AP: UE Context Release -- d) Each measurement is an integer value representing the average number of UE Contexts that are configured SN terminated split bearer. -- e) OR.UECNTX.AveSnSplitBearer.Celltype (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.UEENDC.AveSnSplitBearer.Celltype (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Celltype* is the cell type: -- 0: PSCell - - 1: SCell -- f) NRCellICU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.4.4 Average SN terminated MCG bearer UE Contexts - -- a) This counter provides the average number of UE Contexts that are configured SN terminated MCG bearer that are already setup. -- b) SI -- c) The measurement is obtained by reporting the average observed value of UE Contexts that are configured SN terminated MCG bearer that are already setup during the granularity period. - -- the triggers of addition of number of UE Contexts - - received X2-AP: SgNB Reconfiguration Complete (to SN terminated MCG bearer) - - received X2-AP: SgNB Reconfiguration Confirm (to SN terminated MCG bearer) - - the triggers of subtraction of number of UE Contexts - - received X2-AP: SgNB Reconfiguration Complete (to SN terminated split bearer) - - received X2-AP: UE Context Release -- d) Each measurement is an integer value representing the average number of UE Contexts that are configured SN terminated MCG bearer that are already setup. -- e) OR.UECNTX.AveSnMcgBearer (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.UEENDC.AveSnMcgBearer (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) GNBCUCPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.4.5 Total DL CA UE Contexts PSCell - -- a) This counter provides the total number of UE Contexts that are set of DL CA as PSCell in units of NR Cell. -- b) CC -- c) This measurement provides the total number of UE Contexts using this cell as PSCell during each granularity period. This measurement is split into subcounters per number of CC configured for DL CA in unit of NR Cell group. - -The measurement is obtained by reporting the total observed value of UE Contexts that are set of DL CA as PSCell in units of NR Cell during the granularity period per CC. - -- the triggers of addition of number of UE Contexts - - received X2-AP: SgNB Reconfiguration Complete (SCell addition) - - received RRC: RRC Reconfiguration Complete (SCell addition/change using SRB3) - - received X2-AP: SgNB Modification Confirm (SCell addition/change) - - the triggers of subtraction of number of UE Contexts - - received X2-AP: SgNB Reconfiguration Complete (SCell release) - - received RRC: RRC Reconfiguration Complete (SCell release/change using SRB3) - - received X2-AP: SgNB Modification Confirm (SCell release/change) - - received X2-AP: UE Context Release -- d) Each measurement is an integer value representing the total number of UE Contexts that are set of DL CA as PSCell in units of NR Cell. -- e) OR.UECNTX.TotalDLCaUePscell.Ccnum (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.UEENDC.TotalDLCaUePscell.Ccnum (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Ccnum* is the number of CC: -- 0: #0CC (number of SCell excluding PSCell in the cell group) - - 1: #1CC (number of SCell excluding PSCell in the cell group) - - ... - - 7: #7CC (number of SCell excluding PSCell in the cell group) -- f) NRCellCU -- g) Packet Switched - -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.4.6 Void - -#### A.2.4.7 Total DL CA UE Contexts SCell - -- a) This counter provides the total number of UE Contexts that are set of DL CA as SCell in units of NR Cell. -- b) CC -- c) The measurement is obtained by reporting the total observed value of UE Contexts that are set of DL CA as SCell in units of NR Cell during the granularity period per CC. - - the triggers of addition of number of UE Contexts - - received X2-AP: SgNB Reconfiguration Complete (SCell addition) - - received RRC: RRC Reconfiguration Complete (SCell addition/change using SRB3) - - received X2-AP: SgNB Modification Confirm (SCell addition/change) - - the triggers of subtraction of number of UE Contexts - - received X2-AP: SgNB Reconfiguration Complete (SCell release) - - received F1-AP: UE Context Release Complete (SCell release/change using SRB3) - - received X2-AP: SgNB Modification Confirm (SCell release/change) - - received X2-AP: UE Context Release -- d) Each measurement is an integer value representing the total number of UE Contexts that are set of DL CA as SCell in units of NR Cell. -- e) OR.UECNTX.TotalDLCaUeScell.*Ccnum* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.UEENDC.TotalDLCaUeScell.*Ccnum* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Ccnum* is the number of CC: - - 0: #1CC (number of SCell excluding PSCell in the cell group) - - 1: #2CC (number of SCell excluding PSCell in the cell group) - - ... - - 6: #7CC (number of SCell excluding PSCell in the cell group) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.4.8 Void - -#### A.2.4.9 Max DL CA UE Contexts PSCell - -- a) This counter provides the maximum number of UE Contexts that are set of DL CA as PSCell in units of NR Cell. -- b) SI - -- c) The measurement is obtained by reporting the maximum observed value UE Contexts that are set of DL CA as PSCell in units of NR Cell during the granularity period per CC. - - the triggers of addition of number of UE Contexts - - received X2-AP: SgNB Reconfiguration Complete (SCell downlink addition) - - received RRC: RRC Reconfiguration Complete (SCell downlink addition/change using SRB3) - - received X2-AP: SgNB Modification Confirm (SCell downlink addition/change) - - the triggers of subtraction of number of UE Contexts - - received X2-AP: SgNB Reconfiguration Complete (SCell downlink release) - - received F1-AP: UE Context Release Complete (SCell downlink release/change using SRB3) - - received X2-AP: SgNB Modification Confirm (SCell downlink release/change) - - received X2-AP: UE downlink Context Release -- d) Each measurement is an integer value representing the maximum number of UE Contexts that are set of DL CA as PSCell in units of NR Cell. -- e) OR.UECNTX.MaxDLCAUePscell.Ccnum (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.UEENDC.MaxDLCAUePscell.Ccnum (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Ccnum* is the number of CC: - - 0: #0CC (number of SCell excluding PSCell in the cell group) - - 1: #1CC (number of SCell excluding PSCell in the cell group) - - ... - - 7: #7CC (number of SCell excluding PSCell in the cell group) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.4.10 Void - -#### A.2.4.11 Max DL CA UE Contexts SCell - -- a) This counter provides the maximum number of UE Contexts that are set of DL CA as SCell in units of NR Cell. -- b) SI -- c) The measurement is obtained by reporting the maximum observed value of UE Contexts that are set of DL CA as SCell in units of NR Cell during the granularity period per CC. - - the triggers of addition of number of UE Contexts - - received X2-AP: SgNB Reconfiguration Complete (SCell downlink addition) - - received RRC: RRC Reconfiguration Complete (SCell downlink addition/change using SRB3) - - received X2-AP: SgNB Modification Confirm (SCell downlink addition/change) - - the triggers of subtraction of number of UE Contexts - - received X2-AP: SgNB Reconfiguration Complete (SCell downlink release) - - received F1-AP: UE Context Release Complete (SCell downlink release/change using SRB3) - - received X2-AP: SgNB Modification Confirm (SCell downlink release/change) - - received X2-AP: UE downlink Context Release - -- d) Each measurement is an integer value representing the maximum number of UE Contexts that are set of DL CA as SCell in units of NR Cell. -- e) OR.UECNTX.MaxDlCaUeScell.Ccnum (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.UEENDC.MaxDlCaUeScell.Ccnum (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Ccnum* is the number of CC: - - 0: #1CC (number of SCell excluding PSCell in the cell group) - - 1: #2CC (number of SCell excluding PSCell in the cell group) - - ... - - 7: #6CC (number of SCell excluding PSCell in the cell group) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.4.12 Void - -### A.2.5 Number of UE Contexts for SA - -#### A.2.5.1 Total RRC Connected UE Contexts - -- a) This counter provides the total number of the RRC connected UE Contexts in PCell. -- b) CC -- c) This measurement provides the total number of RRC connected UE Contexts during each granularity period. - -The measurement is obtained by reporting the total observed value of RRC connected UE Contexts in PCell during the granularity period. - -- the triggers of addition of RRC connected UE Contexts - - received RRC: RRC Setup Complete - - received RRC: RRC Reconfiguration Complete (Inter RAT HO to NR, Inter gNB-CU HO, Intra gNB-CU Inter gNB-DU HO, Intra-DU Inter Cell HO, RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU), RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - received RRC: RRC Resume Complete (RRC inactive to RRC Connected) - - the triggers of subtraction of RRC connected UE Contexts - - received Xn-AP: UE Context Release (Inter gNB-CU HO, RRC Connection Re-establishment (Inter gNB-CU)) - - received NG-AP: UE Context Release Command (Inter-RAT HO to LTE, UE Context Release including EPS fallback) - - received RRC: RRC Reconfiguration Complete (Intra gNB-CU Inter gNB-DU HO, Intra gNB-DU Inter-Cell HO, RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - send RRC: RRC Release (RRC Connected to RRC inactive) -- d) Each measurement is an integer value representing the maximum number of UE Contexts that are set of DL CA as SCell in units of NR Cell. - - e) OR.UECNTX.TotalRrcConnectedUes (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.UESA.TotalRrcConnectedUes (deprecated, refer to NOTE in REQ-PMeas-MC-5) - - f) NRCellCU - -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.5.2 Total UE Contexts Per QoS - -- a) This counter provides the total number of the UE Contexts for PCell and SCell. The measurement is optionally calculated per QoS (mapped 5QI or QCI in EN-DC). -- b) CC -- c) The measurement is obtained by reporting the total observed value of UE Contexts for PCell and SCell during the granularity period. - -NOTE: multiple 5QIs can be set per UE Context, each 5QI is counted per QoS flow. - -- the triggers of addition for PCell - - received NG-AP: Initial Context Setup Response - - received RRC: RRC Reconfiguration Complete (Inter RAT HO to NR, Inter gNB-CU HO, Intra gNB-CU Inter gNB-DU HO, Intra-DU Inter Cell HO, RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU), RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - received RRC: RRC Resume Complete (RRC inactive to RRC Connected) - - send NG-AP: PDU Session Resource Setup Response (PDU Session Establishment) - - send NG-AP: PDU Session Resource Modify Response (PDU Session Modification) - - the triggers of subtraction for PCell - - send RRC: RRC Release (UE Context Release, RRC Connected to RRC inactive, SN Release without keeping UE) - - received Xn-AP: UE Context Release (Inter gNB-CU HO, RRC Connection Re-establishment (Inter gNB-CU)) - - received NG-AP: UE Context Release Command (Inter-RAT HO to LTE, Intra gNB-CU Inter gNB-DU HO, EPS fallback) - - received RRC: RRC Reconfiguration Complete (Intra gNB-DU Inter-Cell HO, RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - received F1-AP: UE Context Release Command (RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU)) - - send NG-AP: PDU Session Resource Release Response (PDU Session Release) - - send NG-AP: PDU Session Resource Modify Response (PDU Session Modification) - - the triggers of addition for SCell - - received RRC: RRC Reconfiguration Complete (SCell addition/change) - - received RRC: RRC Resume Complete (RRC inactive to RRC Connected with SCell addition) - - the triggers of subtraction for SCell - - received RRC: RRC Reconfiguration Complete (SCell release/change) - - received Xn-AP: UE Context Release (Inter gNB-CU HO w/ Xn) - - received NG-AP: UE Context Release Command -- d) Each measurement is an integer value representing the total number of the UE Contexts for PCell and SCell. The measurement is optionally calculated per QoS (mapped 5QI or QCI in EN-DC). - - e) The measurement name has the form OR.UECNTX.TotalUes.*Celltype* or OR.UECNTX.TotalUes.*Celltype\_Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.UESA.TotalUes.*Celltype* or OR.UESA.TotalUes.*Celltype\_Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is QoS and represents the mapped 5QI or QCI level and where *Celltype* is the cell type: - - 0: PCell - - 1: SCell - -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.5.3 Total SCell Configuration UE Contexts - -- a) This counter provides the total number of each SCell configuration UE Contexts. -- b) CC -- c) The measurement is obtained by reporting the total observed value of SCell configuration UE Contexts during the granularity period. - - the triggers of addition - - received RRC: RRC Reconfiguration Complete (SCell addition/change) - - received RRC: RRC Resume Complete (RRC inactive to RRC Connected with SCell addition) - - the triggers of subtraction - - received RRC: RRC Reconfiguration Complete (SCell release/change) - - received Xn-AP: UE Context Release (Inter gNB-CU HO w/ Xn) - - received NG-AP: UE Context Release Command -- d) Each measurement is an integer value representing the total number of each SCell configuration UE Contexts. -- e) OR.UECNTX.TotalSCellConfigUes.SCell (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.UESA.TotalSCellConfigUes.SCell (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.5.4 Total Measurement Gap UE Contexts - -- a) This counter provides the total number of UE Contexts which is configured with measurement gap. -- b) CC -- c) The measurement is obtained by reporting the total observed value of UE Contexts which is configured with measurement gap during the granularity period. - - the triggers of addition - - received RRC: RRC Reconfiguration Complete (setup measurement gap) - - the triggers of subtraction - - received RRC: RRC Reconfiguration Complete (release measurement gap) -- d) Each measurement is an integer value representing the total number of UE Contexts which is configured with measurement gap. -- e) OR.UECNTX.TotalMeasGapUes (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.UESA.TotalMeasGapUes (deprecated, refer to NOTE in REQ-PMeas-MC-5) - -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.5.5 Max RRC Connected UE Contexts - -- a) This counter provides the maximum number of the RRC connected UE Contexts in PCell. -- b) SI -- c) The measurement is obtained by reporting the maximum observed value of RRC connected UE Contexts in PCell during the granularity period. - - the triggers of addition of the RRC connected UE Contexts - - received RRC: RRC Setup Complete - - received RRC: RRC Reconfiguration Complete (Inter RAT HO to NR, Inter gNB-CU HO, Intra gNB-CU Inter gNB-DU HO, Intra-DU Inter Cell HO, RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU), RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - received RRC: RRC Resume Complete (RRC inactive to RRC Connected) - - the triggers of subtraction of the RRC connected UE Contexts - - received Xn-AP: UE Context Release (Inter gNB-CU HO, RRC Connection Re-establishment (Inter gNB-CU)) - - received NG-AP: UE Context Release Command (Inter-RAT HO to LTE, UE Context Release including EPS fallback) - - received RRC: RRC Reconfiguration Complete (Intra gNB-CU Inter gNB-DU HO, Intra gNB-DU Inter-Cell HO, RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - send RRC: RRC Release (RRC Connected to RRC inactive) -- d) Each measurement is an integer value representing the maximum number of the RRC connected UE Contexts in PCell. -- e) OR.UECNTX.MaxRrcConnectedUes (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.UESA.MaxRrcConnectedUes (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.5.6 Max UE Contexts Per QoS - -- a) This counter provides the maximum number of the UE Contexts for PCell and SCell. The measurement is optionally calculated per QoS (mapped 5QI or QCI in EN-DC). -- b) SI -- c) The measurement is obtained by reporting the maximum observed value of UE Contexts for PCell and SCell during the granularity period. - -NOTE: multiple 5QIs can be set per UE Context, each 5QI is counted per QoS flow. - -- the triggers of addition for PCell - - received NG-AP: Initial Context Setup Response - -- received RRC: RRC Reconfiguration Complete (Inter RAT HO to NR, Inter gNB-CU HO, Intra gNB-CU Inter gNB-DU HO, Intra-DU Inter Cell HO, RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU), RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - received RRC: RRC Resume Complete (RRC inactive to RRC Connected) - - send NG-AP: PDU Session Resource Setup Response (PDU Session Establishment) - - send NG-AP: PDU Session Resource Modify Response (PDU Session Modification) -- the triggers of subtraction for PCell - - send RRC: RRC Release (UE Context Release, RRC Connected to RRC inactive, SN Release without keeping UE) - - received Xn-AP: UE Context Release (Inter gNB-CU HO, RRC Connection Re-establishment (Inter gNB-CU)) - - received NG-AP: UE Context Release Command (Inter-RAT HO to LTE, Intra gNB-CU Inter gNB-DU HO, EPS fallback) - - received RRC: RRC Reconfiguration Complete (Intra gNB-DU Inter-Cell HO, RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - received F1-AP: UE Context Release Command (RRR Connection Re-establishment (Intra gNB-CU Inter gNB-DU)) - - send NG-AP: PDU Session Resource Release Response (PDU Session Release) - - send NG-AP: PDU Session Resource Modify Response (PDU Session Modification) - - the triggers of addition for SCell - - received RRC: RRC Reconfiguration Complete (SCell addition/change) - - received RRC: RRC Resume Complete (RRR inactive to RRC Connected with SCell addition) - - the triggers of subtraction for SCell - - received RRC: RRC Reconfiguration Complete (SCell release/change) - - received Xn-AP: UE Context Release (Inter gNB-CU HO w/ Xn) - - received NG-AP: UE Context Release Command -- d) Each measurement is an integer value representing the maximum number of the UE Contexts for PCell and SCell. The measurement is optionally calculated per QoS (mapped 5QI or QCI in EN-DC). -- e) The measurement name has the form OR.UECNTX.MaxUes.*CellType* or OR.UECNTX.MaxUes.*CellType\_Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.UESA.MaxUes.*CellType* or OR.UESA.MaxUes.*CellType\_Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is QoS and represents the mapped 5QI or QCI level and where *Celltype* is the cell type: -- 0: PCell - - 1: SCell -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.5.7 Max SCell Configuration UE Contexts - -- a) This counter provides the maximum number of each SCell configuration UE Contexts. -- b) SI -- c) The measurement is obtained by reporting the maximum observed value of each SCell configuration UE Contexts during the granularity period. -- the triggers of addition - - received RRC: RRC Reconfiguration Complete (SCell addition/change) - -- received RRC: RRC Resume Complete (RRC inactive to RRC Connected with SCell addition) - - the triggers of subtraction - - received RRC: RRC Reconfiguration Complete (SCell release/change) - - received Xn-AP: UE Context Release (Inter gNB-CU HO w/ Xn) - - received NG-AP: UE Context Release Command -- d) Each measurement is an integer value representing the maximum number of each SCell configuration UE Contexts. -- e) OR.UECNTX.MaxScellConfigUes.SCell (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.UESA.MaxScellConfigUes.SCell (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.5.8 Max Measurement Gap UE Contexts - -- a) This counter provides the maximum number of UE Contexts which is configured with measurement gap. -- b) SI -- c) The measurement is obtained by reporting the maximum observed value of UE Contexts which is configured with measurement gap during the granularity period. -- the triggers of addition - - received RRC: RRC Reconfiguration Complete (setup measurement gap) - - the triggers of subtraction - - received RRC: RRC Reconfiguration Complete (release measurement gap) -- d) Each measurement is an integer value representing the maximum number of UE Contexts which is configured with measurement gap. -- e) OR.UECNTX.MaxMeasGapUes (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.UESA.MaxMeasGapUes (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.5.9 Total emergency UE Contexts - -- a) This counter provides the total number of the emergency UE Contexts in a Cell. -- b) CC -- c) The measurement is obtained by reporting the total observed value of emergency UE Contexts in a Cell during the granularity period per Cell Type. - -emergency UE Contexts: UE Contexts corresponding to ARP number assigned for emergency call or Establishment cause (or Resume cause): emergency is assigned. - -- the triggers of addition for PCell - - send NG-AP: Initial Context Setup Response - - received RRC: RRC Reconfiguration Complete (Inter RAT HO to NR, Inter gNB-CU HO, Intra gNB-CU Inter gNB-DU HO, Intra-DU Inter Cell HO, RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU), RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - received RRC: RRC Resume Complete (RRC inactive to RRC Connected) -- the triggers of subtraction for PCell - - send RRC: RRC Release (UE Context Release, RRC Connected to RRC inactive, SN Release without keeping UE) - - received Xn-AP: UE Context Release (Inter gNB-CU HO, RRC Connection Re-establishment (Inter gNB-CU)) - - received NG-AP: UE Context Release Command (Inter-RAT HO to LTE, Intra gNB-CU Inter gNB-DU HO, EPS fallback) - - received RRC: RRC Reconfiguration Complete (Intra gNB-DU Inter-Cell HO, RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - received F1-AP: UE Context Release Command (RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU)) -- the triggers of addition for SCell - - received RRC: RRC Reconfiguration Complete (SCell addition/change) - - received RRC: RRC Resume Complete (RRC inactive to RRC Connected with SCell addition) -- the triggers of subtraction for SCell - - received RRC: RRC Reconfiguration Complete (SCell release/change) - - received Xn-AP: UE Context Release (Inter gNB-CU HO w/ Xn) - - received NG-AP: UE Context Release Command - -- d) Each measurement is an integer value representing the total number of the emergency UE Contexts in a Cell. -- e) OR.UECNTX.TotalEmergencyUes.*Celltype* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.UESA.TotalEmergencyUes.*Celltype* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Celltype* is the cell type: - - 0: PCell - - 1: SCell -- f) NRCellICU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.5.10 Total high priority access UE Contexts - -- a) This counter provides the total number of the high priority access UE Contexts in a Cell. -- b) CC -- c) The measurement is obtained by reporting the total observed value of high priority access UE Contexts in a Cell during the granularity period per Cell Type. - -high priority access UE Contexts: UE Contexts corresponding to ARP number assigned for high priority access call or Establishment cause (or Resume cause): highPriorityAccess is assigned. - -- the triggers of addition for PCell - - send NG-AP: Initial Context Setup Response - - received RRC: RRC Reconfiguration Complete (Inter RAT HO to NR, Inter gNB-CU HO, Intra gNB-CU Inter gNB-DU HO, Intra-DU Inter Cell HO, RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU), RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - received RRC: RRC Resume Complete (RRC inactive to RRC Connected) - - the triggers of subtraction for PCell - - send RRC: RRC Release (UE Context Release, RRC Connected to RRC inactive, SN Release without keeping UE) - - received Xn-AP: UE Context Release (Inter gNB-CU HO, RRC Connection Re-establishment (Inter gNB-CU)) - - received NG-AP: UE Context Release Command (Inter-RAT HO to LTE, Intra gNB-CU Inter gNB-DU HO, EPS fallback) - - received RRC: RRC Reconfiguration Complete (Intra gNB-DU Inter-Cell HO, RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - received F1-AP: UE Context Release Command (RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU)) - - the triggers of addition for SCell - - received RRC: RRC Reconfiguration Complete (SCell addition/change) - - received RRC: RRC Resume Complete (RRC inactive to RRC Connected with SCell addition) - - the triggers of subtraction for SCell - - received RRC: RRC Reconfiguration Complete (SCell release/change) - - received Xn-AP: UE Context Release (Inter gNB-CU HO w/ Xn) - - received NG-AP: UE Context Release Command -- d) Each measurement is an integer value representing the total number of the high priority access UE Contexts in a Cell. -- e) OR.UECNTX.TotalHighPriAccessUes.*Celltype* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.UESA.TotalHighPriAccessUes.*Celltype* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Celltype* is the cell type: -- 0: PCell - - 1: SCell -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.5.11 Max emergency UE Contexts - -- a) This counter provides the maximum number of the Emergency UE Contexts in a Cell. -- b) SI -- c) The measurement is obtained by reporting the maximum observed value of the Emergency UE Contexts in a Cell during the granularity period per Cell Type. - -Emergency UE Contexts: UEs corresponding to ARP number assigned for emergency call or Establishment cause (or Resume cause): emergency is assigned. - -- the triggers of addition for PCell - - send NG-AP: Initial Context Setup Response - -- received RRC: RRC Reconfiguration Complete (Inter RAT HO to NR, Inter gNB-CU HO, Intra gNB-CU Inter gNB-DU HO, Intra-DU Inter Cell HO, RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU), RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - received RRC: RRC Resume Complete (RRC inactive to RRC Connected) - - the triggers of subtraction for PCell - - send RRC: RRC Release (UE Context Release, RRC Connected to RRC inactive, SN Release without keeping UE) - - received Xn-AP: UE Context Release (Inter gNB-CU HO, RRC Connection Re-establishment (Inter gNB-CU)) - - received NG-AP: UE Context Release Command (Inter-RAT HO to LTE, Intra gNB-CU Inter gNB-DU HO, EPS fallback) - - received RRC: RRC Reconfiguration Complete (Intra gNB-DU Inter-Cell HO, RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - received F1-AP: UE Context Release Command (RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU)) - - the triggers of addition for SCell - - received RRC: RRC Reconfiguration Complete (SCell addition/change) - - received RRC: RRC Resume Complete (RRC inactive to RRC Connected with SCell addition) - - the triggers of subtraction for SCell - - received RRC: RRC Reconfiguration Complete (SCell release/change) - - received Xn-AP: UE Context Release (Inter gNB-CU HO w/ Xn) - - received NG-AP: UE Context Release Command -- d) Each measurement is an integer value representing the maximum number of the Emergency UE Contexts in a Cell. -- e) OR.UECNTX.MaxEmergencyUes.*Celltype* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.UESA.MaxEmergencyUes.*Celltype* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Celltype* is the cell type: -- 0: PCell - - 1: SCell -- f) NRCellICU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.5.12 Max high priority access UE Contexts - -- a) This counter provides the maximum number of the high priority access UE Contexts in a Cell. -- b) SI -- c) The measurement is obtained by reporting the maximum observed value of the high priority access UE Contexts in a Cell during the granularity period per Cell Type. - -high priority access UE Contexts: UE Contexts corresponding to ARP number assigned for high priority access call or Establishment cause (or Resume cause): highPriorityAccess is assigned. - -- the triggers of addition for PCell - - send NG-AP: Initial Context Setup Response - - received RRC: RRC Reconfiguration Complete (Inter RAT HO to NR, Inter gNB-CU HO, Intra gNB-CU Inter gNB-DU HO, Intra-DU Inter Cell HO, RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU), RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - -- received RRC: RRC Resume Complete (RRC inactive to RRC Connected) - - the triggers of subtraction for PCell - - send RRC: RRC Release (UE Context Release, RRC Connected to RRC inactive, SN Release without keeping UE) - - received Xn-AP: UE Context Release (Inter gNB-CU HO, RRC Connection Re-establishment (Inter gNB-CU)) - - received NG-AP: UE Context Release Command (Inter-RAT HO to LTE, Intra gNB-CU Inter gNB-DU HO, EPS fallback) - - received RRC: RRC Reconfiguration Complete (Intra gNB-DU Inter-Cell HO, RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - received F1-AP: UE Context Release Command (RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU)) - - the triggers of addition for SCell - - received RRC: RRC Reconfiguration Complete (SCell addition/change) - - received RRC: RRC Resume Complete (RRC inactive to RRC Connected with SCell addition) - - the triggers of subtraction for SCell - - received RRC: RRC Reconfiguration Complete (SCell release/change) - - received Xn-AP: UE Context Release (Inter gNB-CU HO w/ Xn) - - received NG-AP: UE Context Release Command -- d) Each measurement is an integer value representing the maximum number of the high priority access UE Contexts in a Cell. -- e) OR.UECNTX.MaxHighPriAccessUes.*Celltype* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.UESA.MaxHighPriAccessUes.*Celltype* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Celltype* is the cell type: -- 0: PCell - - 1: SCell -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.5.13 Total SN terminated split bearer UE Contexts in NR-DC - -- a) This counter provides the total number of UE Contexts configured as SN terminated split bearer in the NR-DC. -- b) CC -- c) The measurement is obtained by reporting the total observed value of the UE Contexts configured as SN terminated split bearer in the NR-DC during the granularity period. - -These subcounters only cover SCell-users with P(S)Cell in the same gNB. The inter-gNB CA is not covered. - -- the triggers of addition for PCell - - send Xn-AP: SN Reconfiguration Complete (SN Addition, Inter-Master HO w/o SN change, Inter-Master HO w/ SN change, PCell change (Intra-MN) (for target cell)) -- the triggers of subtraction for PCell - - send Xn-AP: SN Reconfiguration Complete (PCell change (Intra-MN) (for source cell)) - - send Xn-AP: UE Context Release (SN Release without keeping UE, SN Release with keeping UE, RRC Connection Re-establishment (Intra gNB-CU), NG HO) - -- received Xn-AP: UE Context Release (MN to gNB Change, Inter-Master HO w/o SN change, Inter-Master HO w/ SN change, RRC Connection Re-establishment (Inter gNB-CU)) - - the triggers of addition for PSCell - - received Xn-AP: SN Reconfiguration Complete (to SN terminated split bearer) - - received Xn-AP: S-Node Modification Confirm (Intra/Inter DU PSCell change using SRB1 (for target cell)) - - received RRC: RRC Reconfiguration Complete (Intra DU PSCell change using SRB3 (for target cell)) - - the triggers of subtraction for PSCell - - received Xn-AP: S-Node Modification Confirm (Intra/Inter DU PSCell change using SRB1 (for source cell)) - - received RRC: RRC Reconfiguration Complete (Intra DU PSCell change using SRB3 (for source cell)) - - received Xn-AP: UE Context Release -- d) Each measurement is an integer value representing the total number of UE Contexts configured as SN terminated split bearer in the NR-DC. -- e) OR.UECNTX.TotalSnSplitbearUes.Celltype (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.UENRDC.TotalSnSplitbearUes.Celltype (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Celltype* is the cell type: -- 0: PCell - - 1: PSCell -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.5.14 Max SN terminated split bearer UE Contexts in NR-DC - -- a) This counter provides the maximum number of UE Contexts configured as SN terminated split bearer in the NR-DC. -- b) SI -- c) The measurement is obtained by reporting the maximum observed value of the UE Contexts configured as SN terminated split bearer in the NR-DC during the granularity period. - -These subcounters only cover Scell-users with P(S)Cell in the same gNB. The inter-gNB CA is not covered. - -- the triggers of addition for PCell - - send Xn-AP: SN Reconfiguration Complete (SN Addition, Inter-Master HO w/o SN change, Inter-Master HO w/ SN change, PCell change (Intra-MN) (for target cell)) -- the triggers of subtraction for PCell - - send Xn-AP: SN Reconfiguration Complete (PCell change (Intra-MN) (for source cell)) - - send Xn-AP: UE Context Release (SN Release without keeping UE, SN Release with keeping UE, RRC Connection Re-establishment (Intra gNB-CU), NG HO) - - received Xn-AP: UE Context Release (MN to gNB Change, Inter-Master HO w/o SN change, Inter-Master HO w/ SN change, RRC Connection Re-establishment (Inter gNB-CU)) -- the triggers of addition for PSCell - - received Xn-AP: SN Reconfiguration Complete (to SN terminated split bearer) - - received Xn-AP: S-Node Modification Confirm (Intra/Inter DU PSCell change using SRB1 (for target cell)) - - received RRC: RRC Reconfiguration Complete (Intra DU PSCell change using SRB3 (for target cell)) -- the triggers of subtraction for PSCell - - received Xn-AP: S-Node Modification Confirm (Intra/Inter DU PSCell change using SRB1 (for source cell)) - -- received RRC: RRC Reconfiguration Complete (Intra DU PSCell change using SRB3 (for source cell)) - - received Xn-AP: UE Context Release -- d) Each measurement is an integer value representing the maximum number of UE Contexts configured as SN terminated split bearer in the NR-DC. -- e) OR.UECNTX.MaxSnSplitbearUes.*Celltype* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.UENRDC.MaxSnSplitbearUes.*Celltype* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *Celltype* is the cell type: -- 0: PCell - - 1: PSCell -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.5.15 Total UE Contexts during voice call - -- a) This counter provides the total number of the UE Contexts during voice call. -- b) CC -- c) The measurement is obtained by reporting the total observed value of the UE Contexts during voice call during the granularity period. -- the triggers of addition - - send NG-AP: Initial Context Setup Response - - received RRC: RRC Reconfiguration Complete (Inter RAT HO to NR, Inter gNB-CU HO, Intra gNB-CU Inter gNB-DU HO, Intra-DU Inter Cell HO, RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU), RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - received RRC: RRC Resume Complete (RRC inactive to RRC Connected) - - the triggers of subtraction - - send RRC: RRC Release (UE Context Release, RRC Connected to RRC inactive, SN Release without keeping UE) - - received Xn-AP: UE Context Release (Inter gNB-CU HO, RRC Connection Re-establishment (Inter gNB-CU)) - - received NG-AP: UE Context Release Command (Inter-RAT HO to LTE, Intra gNB-CU Inter gNB-DU HO, EPS fallback) - - received RRC: RRC Reconfiguration Complete (Intra gNB-DU Inter-Cell HO, RRC Connection Re-establishment (Intra gNB-DU Inter Cell)) - - received F1-AP: UE Context Release Command (RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU)) -- d) Each measurement is an integer value representing the total number of the UE Contexts during voice call. -- e) OR.UECNTX.TotalUesVoice (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.UESA.TotalUesVoice (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.2.6 Monitoring of procedure for EN-DC - -#### A.2.6.1 Number of SgNB Addition procedure attempted for each Cell - -- a) This counter provides the number of the transmitted X2-AP:SGNB ADDITION REQUEST ACKNOWLEDGE messages. -- b) CC -- c) Measurement counter is incremented by 1 whenever X2-AP:SGNB ADDITION REQUEST ACKNOWLEDGE message is transmitted as PSCell. -- d) Each measurement is an integer value representing the number of the transmitted X2-AP:SGNB ADDITION REQUEST ACKNOWLEDGE messages. -- e) OR.UECNTX.SgnbAddAttemptCell (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ENDCPROCEDURE.SgnbAddAttemptCell (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.6.2 Number of SgNB Addition procedure successfully for each Cell - -- a) This counter provides the number of the completed SgNB addition Procedure. -- b) CC -- c) Measurement counter is incremented by 1 whenever SgNB addition procedure is completed as PSCell (i.e. X2-AP:SGNB RECONFIGURATION COMPLETE message (SgNB addition complete) is received and RACH processing with UE is completed). -- d) Each measurement is an integer value representing the number of the completed SgNB addition Procedure. -- e) OR.UECNTX.SgnbAddSuccessCell (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ENDCPROCEDURE.SgnbAddSuccessCell (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.6.3 Number of SgNB Addition procedure attempted for each neighbour eNB - -- a) This counter provides the number of the transmitted X2-AP:SGNB ADDITION REQUEST ACKNOWLEDGE messages. - -This counter is split into subcounters per neighbour eNB. - -- b) CC - -- c) Measurement subcounter is incremented by 1 whenever X2-AP:SGNB ADDITION REQUEST ACKNOWLEDGE message is transmitted when the eNB configured by the message is group of subcounter.*neighboureNB*. -- d) Each measurement is an integer value representing the number of the transmitted X2-AP:SGNB ADDITION REQUEST ACKNOWLEDGE messages. -- e) OR.UECNTX.SgnbAddAttemptNeiEnb.*neighboureNB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ENDCPROCEDURE.SgnbAddAttemptNeiEnb.*neighboureNB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *neighboureNB* is neighbour eNB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) GNBCUCPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.6.4 Number of SgNB Addition procedure successfully for each neighbour eNB - -- a) This counter provides the number of the completed SgNB addition Procedure. -This counter is split into subcounters per neighbour eNB. -- b) CC -- c) Measurement counter is incremented by 1 whenever SgNB addition procedure is completed (i.e. X2-AP:SGNB RECONFIGURATION COMPLETE message (SgNB addition complete) is received and RACH processing with UE is completed) when the eNB configured by the message is group of subcounter.*neighboureNB*. -- d) Each measurement is an integer value representing the number of the completed SgNB addition Procedure. -- e) OR.UECNTX.SgnbAddSuccessNeiEnb.*neighboureNB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ENDCPROCEDURE.SgnbAddSuccessNeiEnb.*neighboureNB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *neighboureNB* is neighbour eNB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) GNBCUCPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.6.5 Number of SgNB modification procedure attempted for each neighbour eNB - -- a) This counter provides the number of the received X2-AP:SGNB MODIFICATION REQUEST messages or transmitted X2-AP:SGNB MODIFICATION REQUIRED messages. - -This counter is split into subcounters per neighbour eNB. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever X2-AP:SGNB MODIFICATION REQUEST message is received or X2-AP:SGNB MODIFICATION REQUIRED message is transmitted , when the eNB configured by the message is group of subcounter.*neighboureNB*. - Double counting is not performed if the procedure is changed to the MN initiated SN Modification procedure after transmitted X2-AP:SGNB MODIFICATION REQUIRED message (e.g. Measurement gap Coordination(SN initiated)). - This subcounter will not be incremented if received X2-AP:SGNB MODIFICATION REQUEST message which True is set for SCG Configuration Query IE. -- d) Each measurement is an integer value representing the number of the received X2-AP:SGNB MODIFICATION REQUEST messages or transmitted X2-AP:SGNB MODIFICATION REQUIRED messages. -- e) OR.UECNTX.SgnbModAttemptNeiEnb.*neighboureNB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ENDCPROCEDURE.SgnbModAttemptNeiEnb.*neighboureNB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *neighboureNB* is neighbour eNB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) GNBCUCPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.6.6 Number of SgNB modification procedure successfully for each neighbour eNB - -- a) This counter provides the number of the completed SgNB modification Procedure. - This counter is split into subcounters per neighbour eNB. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever SgNB Modification procedure is completed (i.e. X2-AP:SGNB RECONFIGURATION COMPLETE message(SgNB modification complete) is received or X2-AP:SGNB MODIFICATION CONFIRM is received and RACH processing with UE is completed) when the eNB configured by the message is group of subcounter.*neighboureNB*. -- d) Each measurement is an integer value representing the number of the completed SgNB modification Procedure. -- e) OR.UECNTX.SgnbModSuccessNeiEnb.*neighboureNB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ENDCPROCEDURE.SgnbModSuccessNeiEnb.*neighboureNB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *neighboureNB* is neighbour eNB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) GNBCUCPFunction -- g) Packet Switched - -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.6.7 Number of Inter gNB-DU PSCell change using SRB1 for RRC Reconfiguration attempted - -- a) This counter provides the number of transmitted X2AP- SgNB Modification Required messages when the following procedure. - - PSCell Change using SRB1 for RRC Reconfiguration – full configuration option, clause 5.6.15 [i.7] - - PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option, clause 5.6.16 [i.7] -- b) CC -- c) Measurement is incremented by 1 whenever X2AP- SgNB Modification Required message is transmitted when the following procedure. - - PSCell Change using SRB1 for RRC Reconfiguration – full configuration option, clause 5.6.15 [i.7] - - PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option, clause 5.6.16 [i.7] -- d) Each measurement is an integer value representing number of transmitted X2AP- SgNB Modification Required messages. -- e) OR.UECNTX.InterGnbDuPscellchSrb1Attempt (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RRCCONENDC.InterGnbDuPscellchSrb1Attempt (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellICU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.6.8 Number of Inter gNB-DU PSCell change using SRB1 for RRC Reconfiguration successful - -- a) This counter provides the number of the received X2AP- SgNB Modification Confirm message when the following procedure. - - PSCell Change using SRB1 for RRC Reconfiguration – full configuration option, clause 5.6.15 [i.7] - - PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option, clause 5.6.16 [i.7] -- b) CC -- c) Measurement is incremented by 1 whenever X2AP- SgNB Modification Confirm message is received when the following procedure. - - PSCell Change using SRB1 for RRC Reconfiguration – full configuration option, clause 5.6.15 [i.7] - - PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option, clause 5.6.16 [i.7] -- d) Each measurement is an integer value representing number of received X2AP- SgNB Modification Confirm messages. - -- e) OR.UECNTX.InterGnbDuPscellchSrb1Success (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.RRCCONENDC.InterGnbDuPscellchSrb1Success (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.6.9 Number of Intra gNB-DU PSCell Change via SRB1 attempted - -- a) This counter provides the number of transmitted X2AP- SgNB Modification Required messages when the following procedure. - - Intra gNB-DU PSCell Change using SRB1 for RRC Reconfiguration, clause 5.6.17 [i.7] -- b) CC -- c) Measurement is incremented by 1 whenever X2AP- SgNB Modification required message is transmitted when the following procedure. - - Intra gNB-DU PSCell Change using SRB1 for RRC Reconfiguration, clause 5.6.17 [i.7] -- d) Each measurement is an integer value representing number of transmitted X2AP- SgNB Modification Required messages. -- e) OR.UECNTX.IntraGnbDuPscellchSrb1Attempt (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.RRCCONENDC.IntraGnbDuPscellchSrb1Attempt (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.6.10 Number of Intra gNB-DU PSCell Change via SRB1 successfully - -- a) This counter provides the number of received X2AP- SgNB Modification Confirm message when the following procedure. - - Intra gNB-DU PSCell Change using SRB1 for RRC Reconfiguration, clause 5.6.17 [i.7] -- b) CC -- c) Measurement is incremented by 1 whenever X2AP- SgNB Modification Confirm message is received when the following procedure. - - Intra gNB-DU PSCell Change using SRB1 for RRC Reconfiguration, clause 5.6.17 [i.7] -- d) Each measurement is an integer value representing number of received X2AP- SgNB Modification Confirm messages. -- e) OR.UECNTX.IntraGnbDuPscellchSrb1Success (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.RRCCONENDC.IntraGnbDuPscellchSrb1Success (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU - -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.6.11 Number of SgNB addition procedure requested for each neighbour eNB - -- a) This counter provides the number of SgNB addition request messages received at SgNB. -This counter splits into subcounters per neighbour eNB. -- b) CC -- c) Measurement subcounter is incremented by 1 for each neighbour eNB whenever an X2-AP:SGNB ADDITION REQUEST message is received at SgNB. -- d) Each measurement is an integer value representing the number of received X2-AP:SGNB ADDITION REQUEST messages at SgNB. -- e) OR.UECNTX.SgnbAddReqNeiEnb.*neighbourNB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ENDCPROCEDURE.SgnbAddReqNeiEnb.*neighbourNB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *neighbourNB* is neighbour eNB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) GNBCUCPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.2.7 Monitoring of RRC Connection for EN-DC - -#### A.2.7.1 Number of Measurement Gap Coordination for per FR2 gap via SRB3 attempted - -- a) This counter provides the number of the transmitted RRC:RRC Reconfiguration messages via SRB3 when the following procedure. - - Measurement Gap Coordination for per FR2 gap (without MN involvement) Procedure (SN initiated). -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RRC:RRCReconfiguration message is transmitted via SRB3 when the following procedure. - - Measurement Gap Coordination for per FR2 gap (without MN involvement) Procedure (SN initiated). -- d) Each measurement is an integer value representing the number of the transmitted RRC:RRC Reconfiguration messages via SRB3. -- e) OR.RRC.ReconfSrb3AttemptGap (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RRCONENDC.ReconfSrb3AttemptGap (deprecated, refer to NOTE in REQ-PMeas-MC-5) - -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.7.2 Number of Measurement Gap Coordination for per FR2 gap via SRB3 successfully - -- a) This counter provides the number of the received RRC:RRC Reconfiguration Complete messages via SRB3 when the following procedure. - - Measurement Gap Coordination for per FR2 gap (without MN involvement) Procedure (SN initiated). -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RRC:RRC Reconfiguration Complete message is received via SRB3 when the following procedure. - - Measurement Gap Coordination for per FR2 gap (without MN involvement) Procedure (SN initiated). -- d) Each measurement is an integer value representing the number of the received RRC:RRC Reconfiguration Complete messages via SRB3. -- e) OR.RRC.ReconfSrb3SuccessGap (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.RRCONENDC.ReconfSrb3SuccessGap (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.7.3 Number of Inter gNB-DU PSCell Change via SRB3 attempted - -- a) This counter provides the number of the transmitted RRC:RRC Reconfiguration messages via SRB3 when the following procedure. - - Inter gNB-DU PSCell Change using SRB3 for RRC Reconfiguration -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RRC:RRC Reconfiguration message is transmitted via SRB3 when the following procedure. - - Inter gNB-DU PSCell Change using SRB3 for RRC Reconfiguration -- d) Each measurement is an integer value representing the number of the transmitted RRC:RRC Reconfiguration messages via SRB3. -- e) OR.RRC.ReconfSrb3AttemptInterDuPscellch (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.RRCONENDC.ReconfSrb3AttemptInterDuPscellch (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched - -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.7.4 Number of Inter gNB-DU PSCell Change via SRB3 successfully - -- a) This counter provides the number of the received RRC:RRC Reconfiguration Complete messages via SRB3 when the following procedure. - - Inter gNB-DU PSCell Change using SRB3 for RRC Reconfiguration -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RRC:RRCReconfiguration Complete message is received via SRB3 when the following procedure. - - Inter gNB-DU PSCell Change using SRB3 for RRC Reconfiguration -- d) Each measurement is an integer value representing the number of the transmitted RRC:RRC Reconfiguration messages via SRB3. -- e) OR.RRC.ReconfSrb3SuccessInterDuPscellch (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RRCCONENDC.ReconfSrb3SuccessInterDuPscellch (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.7.5 Number of Intra gNB-DU PSCell Change via SRB3 attempted - -- a) This counter provides the number of the transmitted RRC:RRC Reconfiguration messages via SRB3 when the following procedure. - - Intra gNB-DU PSCell Change using SRB3 for RRC Reconfiguration -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RRC:RRCReconfiguration message is transmitted via SRB3 when the following procedure. - - Intra gNB-DU PSCell Change using SRB3 for RRC Reconfiguration -- d) Each measurement is an integer value representing the number of the transmitted RRC:RRC Reconfiguration messages via SRB3. -- e) OR.RRC.ReconfSrb3AttemptIntraDuPscellch (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RRCCONENDC.ReconfSrb3AttemptIntraDuPscellch (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.7.6 Number of Intra gNB-DU PSCell Change via SRB3 successfully - -- a) This counter provides the number of the received RRC:RRC Reconfiguration Complete messages via SRB3 when the following procedure. - - Intra gNB-DU PSCell Change using SRB3 for RRC Reconfiguration -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RRC:RRCReconfiguration Complete message is received via SRB3 when the following procedure. - - Intra gNB-DU PSCell Change using SRB3 for RRC Reconfiguration -- d) Each measurement is an integer value representing the number of the received RRC:RRC Reconfiguration Complete messages via SRB3. -- e) OR.RRC.ReconfSrb3SuccessIntraDuPscellch (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.RRCCONENDC.ReconfSrb3SuccessIntraDuPscellch (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.2.8 Monitoring of RRC Connection for SA - -#### A.2.8.1 Number of initial RRC Connection requests - -- a) This counter provides the number of the received RRC: RRC Setup Request (or RRC: RRC Resume Request) messages via F1-C which is in the first time for each ue-Identity. -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Setup Request (or RRC: RRC Resume Request) message is received via F1-C, if RRC: RRC Setup Request (or RRC: RRC Resume Request) message of the same ue-Identity is not received for a certain period of time from the reception timing. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Setup Request (or RRC: RRC Resume Request) messages via F1-C which is in the first time for each ue-Identity. -- e) OR.RRC.IniConReq (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.RRCCONSA.IniConReq (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.8.2 Number of RRC connection completions for initial RRC Connection requests - -- a) This counter provides the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Response) messages via F1-C which corresponds to the initial RRC: RRC Setup Request (or RRC: RRC Resume Request) except fall-back procedure. -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Setup Complete (or RRC: RRC Resume Response) message which corresponds to the initial RRC: RRC Setup Request (or RRC: RRC Resume Request) except fall-back procedure is received via F1-C. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Response) messages via F1-C which corresponds to the initial RRC: RRC Setup Request (or RRC: RRC Resume Request) except fall-back procedure. -- e) OR.RRC.IniConComp (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.RRCCONSA.IniConComp (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.8.3 Number of retransmission RRC Connections requests - -- a) This counter provides the number of the received RRC: RRC Setup Request (or RRC: RRC Resume Request) messages via F1-C which is retransmission for each ue-Identity. -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Setup Request (or RRC: RRC Resume Request) message is received via F1-C, if RRC: RRC Setup Request (or RRC: RRC Resume Request) message of the same ue-Identity is received for a certain period of time from the reception timing. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Setup Request (or RRC: RRC Resume Request) messages via F1-C which is retransmission for each ue-Identity. -- e) OR.RRC.RetConReq (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.RRCCONSA.RetConReq (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.8.4 Number of RRC Connections completions for retransmission RRC Connections requests - -- a) This counter provides the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Response) messages via F1-C which corresponds to the retransmission RRC: RRC Setup Request (or RRC: RRC Resume Request) except fall-back procedure. - -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Setup Complete (or RRC: RRC Resume Response) message which corresponds to the retransmission RRC: RRC Setup Request (or RRC: RRC Resume Request) except fall-back procedure is received via F1-C. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Response) messages via F1-C which corresponds to the retransmission RRC: RRC Setup Request (or RRC: RRC Resume Request) except fall-back procedure. -- e) OR.RRC.RetransConComp (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.RRCONSA.RetransConComp (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.8.5 Number of incomplete RRC Connection by failed resource allocations - -- a) This counter provides the number of the RRC Connection configuration interrupted by failed resource allocations. -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC Connection configuration is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to RRC: RRC Setup Complete (or RRC: RRC Resume Complete) by failed resource allocations. -- d) Each measurement is an integer value representing the number of the RRC Connection configuration interrupted by failed resource allocations. -- e) OR.RRC.IncompConResourAllo (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.RRCONSA.IncompConResourAllo (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.8.6 Number of incomplete RRC Connection by O-CU internal error - -- a) This counter provides the number of the RRC Connection configuration interrupted by O-CU internal error (e.g. L3 message sending NG). -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC Connection configuration is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to RRC: RRC Setup Complete (or RRC: RRC Resume Complete) by O-CU internal error. -- d) Each measurement is an integer value representing the number of the RRC Connection configuration interrupted by O-CU internal error (e.g. L3 message sending NG). - -- e) OR.RRC.IncompConOcuInterErr (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.RRCONSA.IncompConOcuInterErr (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.8.7 Number of initial RRC Connection requests each Establishment Cause - -- a) This counter provides the number of the received RRC: RRC Setup Request (or RRC: RRC Resume Request) messages via F1-C which is in the first time for each ue-Identity. - -This counter is split into subcounters per EstablishmentCause. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RRC: RRC Setup Request (or RRC: RRC Resume Request) message is received via F1-C, if RRC: RRC Setup Request (or RRC: RRC Resume Response) message of the same ue-Identity is not received for a certain period of time from the reception timing when the cell configured by the message is group of subcounter.*EstablishmentCause*. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Setup Request (or RRC: RRC Resume Request) messages via F1-C which is in the first time for each ue-Identity. -- e) OR.RRC.IniConReqEstaCause.*EstablishmentCause* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RRCONSA.IniConReqEstaCause.*EstablishmentCause* (deprecated, refer to NOTE in REQ-PMeas-MC-5), where *EstablishmentCause* is EstablishmentCause: - - 0: EstablishmentCause = emergency - - 1: EstablishmentCause = highPriorityAccess - - 2: EstablishmentCause = mt-Access - - 3: EstablishmentCause = mo-Signalling - - 4: EstablishmentCause = mo-Data - - 5: EstablishmentCause = mo-VoiceCall - - 6: EstablishmentCause = mo-VideoCall - - 7: EstablishmentCause = mo-SMS - - 8: EstablishmentCause = mps-PriorityAccess - - 9: EstablishmentCause = mcs-PriorityAccess -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.8.8 Number of RRC connection completions for initial RRC Connection requests each Establishment Cause - -- a) This counter provides the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Response) messages via F1-C which corresponds to the initial RRC: RRC Setup Request (or RRC: RRC Resume Request) except fall-back procedure. - -This counter is split into subcounters per EstablishmentCause. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RRC:RRC Setup Complete (or RRC: RRC Resume Response) message which corresponds to the initial RRC: RRC Setup Request (or RRC: RRC Resume Request) except fall-back procedure is received via F1-C when the cell configured by the message is group of subcounter.*EstablishmentCause*. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Response) messages via F1-C which corresponds to the initial RRC: RRC Setup Request (or RRC: RRC Resume Request) except fall-back procedure. -- e) OR.RRC.IniConCompEstaCause.*EstablishmentCause* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RRCCONSA.IniConCompEstaCause.*EstablishmentCause* (deprecated, refer to NOTE in REQ-PMeas-MC-5), where *EstablishmentCause* is EstablishmentCause: - - 0: EstablishmentCause = emergency - - 1: EstablishmentCause = highPriorityAccess - - 2: EstablishmentCause = mt-Access - - 3: EstablishmentCause = mo-Signalling - - 4: EstablishmentCause = mo-Data - - 5: EstablishmentCause = mo-VoiceCall - - 6: EstablishmentCause = mo-VideoCall - - 7: EstablishmentCause = mo-SMS - - 8: EstablishmentCause = mps-PriorityAccess - - 9: EstablishmentCause = mcs-PriorityAccess -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.8.9 Number of retransmission RRC Connections requests each Establishment Cause - -- a) This counter provides the number of the received RRC: RRC Setup Request (or RRC: RRC Resume Request) messages via F1-C which is retransmission for each ue-Identity. - -This counter is split into subcounters per EstablishmentCause. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RRC: RRC Setup Request (or RRC: RRC Resume Request) message is received via F1-C, if RRC: RRC Setup Request (or RRC: RRC Resume Request) message of the same ue- - -Identity is received for a certain period of time from the reception timing when the cell configured by the message is group of subcounter.*EstablishmentCause*. - -- d) Each measurement is an integer value representing the number of the received RRC: RRC Setup Request (or RRC: RRC Resume Request) messages via F1-C which is retransmission for each ue-Identity. -- e) OR.RRC.RetransConReqEstaCause.*EstablishmentCause* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RRCONSA.RetransConReqEstaCause.*EstablishmentCause* (deprecated, refer to NOTE in REQ-PMeas-MC-5), where *EstablishmentCause* is EstablishmentCause: - - 0: EstablishmentCause = emergency - - 1: EstablishmentCause = highPriorityAccess - - 2: EstablishmentCause = mt-Access - - 3: EstablishmentCause = mo-Signalling - - 4: EstablishmentCause = mo-Data - - 5: EstablishmentCause = mo-VoiceCall - - 6: EstablishmentCause = mo-VideoCall - - 7: EstablishmentCause = mo-SMS - - 8: EstablishmentCause = mps-PriorityAccess - - 9: EstablishmentCause = mcs-PriorityAccess -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.8.10 Number of RRC Connections completions for retransmission RRC Connections requests each Establishment Cause - -- a) This counter provides the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Response) messages via F1-C which corresponds to the retransmission RRC: RRC Setup Request (or RRC: RRC Resume Request) except fall-back procedure. - -This counter is split into subcounters per *EstablishmentCause*. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RRC: RRC Setup Complete (or RRC: RRC Resume Response) message which corresponds to the retransmission RRC: RRC Setup Request (or RRC: RRC Resume Request) except fall-back procedure is received via F1-C when the cell configured by the message is group of subcounter.*EstablishmentCause*. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Response) messages via F1-C which corresponds to the retransmission RRC: RRC Setup Request (or RRC: RRC Resume Request) except fall-back procedure. -- e) OR.RRC.RetransConCompEstaCause.*EstablishmentCause* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RRCONSA.RetransConCompEstaCause.*EstablishmentCause* (deprecated, refer to NOTE in REQ-PMeas-MC-5), where *EstablishmentCause* is EstablishmentCause: - -- 0: EstablishmentCause = emergency - - 1: EstablishmentCause = highPriorityAccess - - 2: EstablishmentCause = mt-Access - - 3: EstablishmentCause = mo-Signalling - - 4: EstablishmentCause = mo-Data - - 5: EstablishmentCause = mo-VoiceCall - - 6: EstablishmentCause = mo-VideoCall - - 7: EstablishmentCause = mo-SMS - - 8: EstablishmentCause = mps-PriorityAccess - - 9: EstablishmentCause = mcs-PriorityAccess -- f) NRCellCU - - g) Packet Switched - - h) 5GS - - i) Network Operator's Traffic Engineering Community - -#### A.2.8.11 Number of incomplete RRC Connection by failed resource allocations each Establishment Cause - -- a) This counter provides the number of the RRC Connection configuration interrupted by failed resource allocations. -This counter is split into subcounters per EstablishmentCause. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RRC Connection configuration is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to RRC: RRC Setup Complete (or RRC: RRC Resume Complete) by failed resource allocations when the cell configured by the message is group of subcounter.*EstablishmentCause*. -- d) Each measurement is an integer value representing the number of the RRC Connection configuration interrupted by failed resource allocations. -- e) OR.RRC.IncompConResourAlloEstaCause.*EstablishmentCause* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RRCCONSA.IncompConResourAlloEstaCause.*EstablishmentCause* (deprecated, refer to NOTE in REQ-PMeas-MC-5), where *EstablishmentCause* is EstablishmentCause: - - 0: EstablishmentCause = emergency - - 1: EstablishmentCause = highPriorityAccess - - 2: EstablishmentCause = mt-Access - - 3: EstablishmentCause = mo-Signalling - - 4: EstablishmentCause = mo-Data - - 5: EstablishmentCause = mo-VoiceCall - - 6: EstablishmentCause = mo-VideoCall - - 7: EstablishmentCause = mo-SMS - -- 8: EstablishmentCause = mps-PriorityAccess -- 9: EstablishmentCause = mcs-PriorityAccess -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.8.12 Number of incomplete RRC Connection by O-CU internal error each Establishment Cause - -- a) This counter provides the number of the RRC Connection configuration interrupted by O-CU internal error (e.g. L3 message sending NG). -This counter is split into subcounters per EstablishmentCause. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RRC Connection configuration is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to RRC: RRC Setup Complete (or RRC: RRC Resume Complete) by O-CU internal error when the cell configured by the message is group of subcounter.*EstablishmentCause*. -- d) Each measurement is an integer value representing the number of the RRC Connection configuration interrupted by O-CU internal error (e.g. L3 message sending NG). -- e) OR.RRC.IncompConOcuInterErrEstaCause.*EstablishmentCause* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RRCCONSA.IncompConOcuInterErrEstaCause.*EstablishmentCause* (deprecated, refer to NOTE in REQ-PMeas-MC-5), where *EstablishmentCause* is EstablishmentCause: - - 0: EstablishmentCause = emergency - - 1: EstablishmentCause = highPriorityAccess - - 2: EstablishmentCause = mt-Access - - 3: EstablishmentCause = mo-Signalling - - 4: EstablishmentCause = mo-Data - - 5: EstablishmentCause = mo-VoiceCall - - 6: EstablishmentCause = mo-VideoCall - - 7: EstablishmentCause = mo-SMS - - 8: EstablishmentCause = mps-PriorityAccess - - 9: EstablishmentCause = mcs-PriorityAccess -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.2.9 Monitoring of Establishment calls for SA - -#### A.2.9.1 Number of attempted establishment calls for mo-Data - -- a) This counter provides the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Complete) messages via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (Resume Cause):mo-Data). -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Setup Complete (or RRC: RRC Resume Complete) message is received via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): mo-Data). -- d) Each measurement is an integer value representing the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Complete) messages via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (Resume Cause):mo-Data). -- e) OR.RRC.AttemptModata (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.AttemptModata (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.2 Number of successful establishment calls for mo-Data - -- a) This counter provides the number of the following message after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): mt-Data): - - send NG-AP: Initial Context Setup Response - - received NG-AP: UE Context Release Command (for deregistration) before sending NG-AP: Initial Context Setup Response -- b) CC -- c) Measurement counter is incremented by 1 whenever the following event occurs after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): mo-Data): - - send NG-AP: Initial Context Setup Response - - received NG-AP: UE Context Release Command (for deregistration) before sending NG-AP: Initial Context Setup Response - Measurement counter is incremented by 1 whenever NG-AP:Initial Context Setup Response message is transmitted after received RRC: RRC Setup Request (Establishment Cause: mo-Data). -- d) Each measurement is an integer value representing the number of the following message after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): mt-Data): - - send NG-AP: Initial Context Setup Response - - received NG-AP: UE Context Release Command (for deregistration) before sending NG-AP: Initial Context Setup Response -- e) OR.RRC.SuccessModata (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.SuccessModata (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU - -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.3 Number of incomplete establishment calls for mo-Data by protocol error - -- a) This counter provides the number of the Call establishment for mo-Data interrupted by protocol error. -- b) CC -- c) Measurement counter is incremented by 1 whenever Call establishment for mo-Data is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by protocol error. -- d) Each measurement is an integer value representing the number of the Call establishment for mo-Data interrupted by protocol error. -- e) OR.RRC.IncompModataProtocolErr (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ESTACALL.IncompModataProtocolErr (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.4 Number of incomplete establishment calls for mo-Data by O-CU internal error - -- a) This counter provides the number of the call establishment for mo-Data interrupted by O-CU internal error. -- b) CC -- c) Measurement counter is incremented by 1 whenever call establishment for mo-Data is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by O-CU internal error. -- d) Each measurement is an integer value representing the number of the call establishment for mo-Data interrupted by O-CU internal error. -- e) OR.RRC.IncompModataOcuInterErr (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ESTACALL.IncompModataOcuInterErr (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.5 Number of incomplete establishment calls for mo-Data by O-DU error detection - -- a) This counter provides the number of the call establishment for mo-Data interrupted by O-DU Error Detection. - -- b) CC -- c) Measurement counter is incremented by 1 whenever call establishment for mo-Data is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by O-DU Error Detection. -- d) Each measurement is an integer value representing the number of the call establishment for mo-Data interrupted by O-DU Error Detection. -- e) OR.RRC.IncompModataOduErrDetect (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ESTACALL.IncompModataOduErrDetect (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.6 Number of attempted establishment calls for mt-Access - -- a) This counter provides the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Complete) messages via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): mt-Access). -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Setup Complete (or RRC: RRC Resume Complete) message is received via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): mt-Access). -- d) Each measurement is an integer value representing the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Complete) messages via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): mt-Access). -- e) OR.RRC.AttemptMtaccess (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ESTACALL.AttemptMtaccess (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.7 Number of successful establishment calls for mt-Access - -- a) This counter provides the number of the following message after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause):mt-Access): - - send NG-AP: Initial Context Setup Response - - received NG-AP: UE Context Release Command (for deregistration) before sending NG-AP: Initial Context Setup Response -- b) CC - -- c) Measurement counter is incremented by 1 whenever the following event occurs after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause):mt-Access): - - send NG-AP: Initial Context Setup Response - - received NG-AP: UE Context Release Command (for deregistration) before sending NG-AP: Initial Context Setup Response -- d) Each measurement is an integer value representing the number of the following message after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause):mt-Access): - - send NG-AP: Initial Context Setup Response - - received NG-AP: UE Context Release Command (for deregistration) before sending NG-AP: Initial Context Setup Response -- e) OR.RRC.SuccessMtaccess (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.SuccessMtaccess (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.8 Number of incomplete establishment calls for mt-Access by protocol error - -- a) This counter provides the number of the call establishment for mt-Access interrupted by protocol error. -- b) CC -- c) Measurement counter is incremented by 1 whenever call establishment for mt-Access is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by protocol error. -- d) Each measurement is an integer value representing the number of the call establishment for mt-Access interrupted by protocol error. -- e) OR.RRC.IncompMtaccessProtocolErr (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.IncompMtaccessProtocolErr (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.9 Number of incomplete establishment calls for mt-Access by O-CU internal error - -- a) This counter provides the number of the call establishment for mt-Access interrupted by O-CU internal error. -- b) CC -- c) Measurement counter is incremented by 1 whenever call establishment for mt-Access is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by O-CU internal error. - -- d) Each measurement is an integer value representing the number of the call establishment for mt-Access interrupted by O-CU internal error. -- e) OR.RRC.IncompMtaccessOcuInterErr (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.IncompMtaccessOcuInterErr (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellICU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.10 Number of incomplete establishment calls for mt-Access by O-DU error detection - -- a) This counter provides the number of the call establishment for mt-Access is interrupted by O-DU Error Detection. -- b) CC -- c) Measurement counter is incremented by 1 whenever call establishment for mt-Access is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by DU Error Detection. -- d) Each measurement is an integer value representing the number of the call establishment for mt-Access is interrupted by O-DU Error Detection. -- e) OR.RRC.IncompMtaccessOduErrDetect (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.IncompMtaccessOduErrDetect (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellICU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.11 Number of attempted establishment calls for mo-Signalling - -- a) This counter provides the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Complete) messages via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause):mo-Signalling). -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Setup Complete (or RRC: RRC Resume Complete) message is received via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause):mo-Signalling). -- d) Each measurement is an integer value representing the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Complete) messages via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause):mo-Signalling). -- e) OR.RRC.AcceptMosignal (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.AcceptMosignal (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellICU - -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.12 Number of successful establishment calls for mo-Signalling - -- a) This counter provides the number of the following message after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): mo-Signalling): - - send NG-AP: Initial Context Setup Response - - received NG-AP: UE Context Release Command (for deregistration) before sending NG-AP: Initial Context Setup Response -- b) CC -- c) Measurement counter is incremented by 1 whenever the following event occurs after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): mo-Signalling): - - send NG-AP: Initial Context Setup Response - - received NG-AP: UE Context Release Command (for deregistration) before sending NG-AP: Initial Context Setup Response -- d) Each measurement is an integer value representing the number of the following message after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): mo-Signalling): - - send NG-AP: Initial Context Setup Response - - received NG-AP: UE Context Release Command (for deregistration) before sending NG-AP: Initial Context Setup Response -- e) OR.RRC.SuccessMosignal (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.SuccessMosignal (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.13 Number of incomplete establishment calls for mo-Signalling by protocol error - -- a) This counter provides the number of the call establishment for mo-Signalling interrupted by protocol error. -- b) CC -- c) Measurement counter is incremented by 1 whenever call establishment for mo-Signalling is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by protocol error. -- d) Each measurement is an integer value representing the number of the call establishment for mo-Signalling interrupted by protocol error. -- e) OR.RRC.IncompMosignalProtocolErr (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.IncompMosignalProtocolErr (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU - -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.14 Number of incomplete establishment calls for mo-Signalling by O-CU internal error - -- a) This counter provides the number of the call establishment for mo-Signalling interrupted by O-CU internal error. -- b) CC -- c) Measurement counter is incremented by 1 whenever mo-Signalling configuration is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by O-CU internal error. -- d) Each measurement is an integer value representing the number of the call establishment for mo-Signalling interrupted by O-CU internal error. -- e) OR.RRC.IncompMosignalOcuInterErr (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.IncompMosignalOcuInterErr (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.15 Number of incomplete establishment calls for mo-Signalling by O-DU error detection - -- a) This counter provides the number of the call establishment for mo-Signalling interrupted by O-DU error detection. -- b) CC -- c) Measurement counter is incremented by 1 whenever call establishment for mo-Signalling is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by O-DU error detection. -- d) Each measurement is an integer value representing the number of the call establishment for mo-Signalling interrupted by O-DU error detection. -- e) OR.RRC.IncompMosignalDuErrDetect (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.IncompMosignalDuErrDetect (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.16 Number of attempted establishment calls for mo-SMS - -- a) This counter provides the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Complete) messages via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): mo-SMS). -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Setup Complete (or RRC: RRC Resume Complete) message is received via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): mo-SMS). -- d) Each measurement is an integer value representing the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Complete) messages via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): mo-SMS). -- e) OR.RRC.AttemptMossms (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.AttemptMossms (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.17 Number of successful establishment calls for mo-SMS - -- a) This counter provides the number of the following message after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): mo-SMS): - - send NG-AP: Initial Context Setup Response - - received NG-AP: UE Context Release Command (for deregistration) before sending NG-AP: Initial Context Setup Response -- b) CC -- c) Measurement counter is incremented by 1 whenever the following event occurs after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): mo-SMS): - - send NG-AP: Initial Context Setup Response - - received NG-AP: UE Context Release Command (for deregistration) before sending NG-AP: Initial Context Setup Response -- d) Each measurement is an integer value representing the number of the following message after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): mo-SMS): - - send NG-AP: Initial Context Setup Response - - received NG-AP: UE Context Release Command (for deregistration) before sending NG-AP: Initial Context Setup Response -- e) OR.RRC.SuccessMossms (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.SuccessMossms (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS - -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.18 Number of incomplete establishment calls for mo-SMS by protocol error - -- a) This counter provides the number of the call establishment for mo-SMS interrupted by protocol error. -- b) CC -- c) Measurement counter is incremented by 1 whenever call establishment for mo-SMS is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by protocol error. -- d) Each measurement is an integer value representing the number of the call establishment for mo-SMS interrupted by protocol error. -- e) OR.RRC.IncompMossmsProtocolErr (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.IncompMossmsProtocolErr (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.19 Number of incomplete establishment calls for mo-SMS by O-CU internal error - -- a) This counter provides the number of the call establishment for mo-SMS interrupted by O-CU internal error. -- b) CC -- c) Measurement counter is incremented by 1 whenever call establishment for mo-SMS is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by O-CU internal error. -- d) Each measurement is an integer value representing the number of the call establishment for mo-SMS interrupted by O-CU internal error. -- e) OR.RRC.IncompMossmsOcuInterErr (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.IncompMossmsOcuInterErr (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.20 Number of incomplete establishment calls for mo-SMS by O-DU error detection - -- a) This counter provides the number of the call establishment for mo-SMS interrupted by O-DU error detection. -- b) CC - -- c) Measurement counter is incremented by 1 whenever call establishment for mo-SMS is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by O-DU error detection. -- d) Each measurement is an integer value representing the number of the call establishment for mo-SMS interrupted by O-DU error detection. -- e) OR.RRC.IncompMossmsOduErrDetect (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.IncompMossmsOduErrDetect (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.21 Number of attempted establishment calls for high priority access - -- a) This counter provides the number of the received RRC: RRC Setup Complete messages (or RRC: RRC Resume Complete) via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): highPriorityAccess). -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Setup Complete (or RRC: RRC Resume Complete) message is received via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): highPriorityAccess). -- d) Each measurement is an integer value representing the number of the received RRC: RRC Setup Complete messages (or RRC: RRC Resume Complete) via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): highPriorityAccess). -- e) OR.RRC.AttemptHighPriAccess (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.AttemptHighPriAccess (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.22 Number of successful establishment calls for high priority access - -- a) This counter provides the number of the following message after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): highPriorityAccess): - - NG-AP: Initial Context Setup Response is transmitted. - - NG-AP: UE Context Release Command (for detach) is received before NG-AP: Initial Context Setup Response is transmitted. -- b) CC -- c) Measurement counter is incremented by 1 whenever the following event occurs after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): highPriorityAccess): - -- send NG-AP: Initial Context Setup Response - - NG-AP: UE Context Release Command (for detach) is received before NG-AP: Initial Context Setup Response is transmitted. -- d) Each measurement is an integer value representing the number of the following message after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): highPriorityAccess): -- NG-AP: Initial Context Setup Response is transmitted. - - NG-AP: UE Context Release Command (for detach) is received before NG-AP: Initial Context Setup Response is transmitted. -- e) OR.RRC.SuccessHighPriAccess (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.SuccessHighPriAccess (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.23 Number of incomplete establishment calls for high priority access by protocol error - -- a) This counter provides the number of the call establishment for high priority access interrupted by protocol error. -- b) CC -- c) Measurement counter is incremented by 1 whenever call establishment for high priority access is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by protocol error (Call acceptance condition of CU/DU is not met). -- d) Each measurement is an integer value representing the number of the call establishment for high priority access interrupted by protocol error. -- e) OR.RRC.IncompHighPriAccessProtocolErr (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.IncompHighPriAccessProtocolErr (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.24 Number of incomplete establishment calls for high priority access by O-CU internal error - -- a) This counter provides the number of the call establishment for high priority access interrupted by O-CU internal error. -- b) CC -- c) Measurement counter is incremented by 1 whenever call establishment for high priority access is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by O-CU internal error (Call acceptance condition of CU/DU is not met). -- d) Each measurement is an integer value representing the number of the call establishment for high priority access interrupted by O-CU internal error. - -- e) OR.RRC.IncompHighPriAccessOcuInterErr (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.IncompHighPriAccessOcuInterErr (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.25 Number of incomplete establishment calls for high priority access by O-DU error detection - -- a) This counter provides the number of the call establishment for high priority access interrupted by O-DU error detection. -- b) CC -- c) Measurement counter is incremented by 1 whenever call establishment for high priority access is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by O-DU error detection (Call acceptance condition of CU/DU is not met). -- d) Each measurement is an integer value representing the number of the call establishment for high priority access interrupted by O-DU error detection. -- e) OR.RRC.IncompHighPriAccessOduErrDetect (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.IncompHighPriAccessOduErrDetect (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.26 Number of attempted establishment calls for emergency - -- a) This counter provides the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Complete) messages via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): emergency). -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Setup Complete (or RRC: RRC Resume Complete) message is received via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): emergency). -- d) Each measurement is an integer value representing the number of the received RRC: RRC Setup Complete (or RRC: RRC Resume Complete) messages via F1-C after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): emergency). -- e) OR.RRC.AttemptEmergency (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.AttemptEmergency (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched - -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -##### A.2.9.27 Number of successful establishment calls for emergency - -- a) This counter provides the number of the following message after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): emergency): - - send NG-AP: Initial Context Setup Response - - NG-AP: UE Context Release Command (for detach) is received before NG-AP: Initial Context Setup Response is transmitted. -- b) CC -- c) Measurement counter is incremented by 1 whenever the following event occurs after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): emergency): - - NG-AP: Initial Context Setup Response is transmitted. - - NG-AP: UE Context Release Command (for detach) is received before NG-AP: Initial Context Setup Response is transmitted. -- d) Each measurement is an integer value representing the number of the following message after received RRC: RRC Setup Request (or RRC: RRC Resume Request) (Establishment Cause (or Resume Cause): emergency): - - send NG-AP: Initial Context Setup Response - - NG-AP: UE Context Release Command (for detach) is received before NG-AP: Initial Context Setup Response is transmitted. -- e) OR.RRC.SuccessEmergency (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.SuccessEmergency (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.28 Number of incomplete establishment calls for emergency by protocol error - -- a) This counter provides the number of the call establishment for emergency interrupted by protocol error. -- b) CC -- c) Measurement counter is incremented by 1 whenever call establishment for emergency is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by protocol error (Call acceptance condition of CU/DU is not met). -- d) Each measurement is an integer value representing the number of the call establishment for emergency interrupted by protocol error. -- e) OR.RRC.IncompEmergencyProtocolErr (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.IncompEmergencyProtocolErr (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched - -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.29 Number of incomplete establishment calls for emergency by O-CU internal error - -- a) This counter provides the number of the call establishment for emergency interrupted by O-CU internal error. -- b) CC -- c) Measurement counter is incremented by 1 whenever call establishment for emergency is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by O-CU internal error (Call acceptance condition of CU/DU is not met). -- d) Each measurement is an integer value representing the number of the call establishment for emergency interrupted by O-CU internal error. -- e) OR.RRC.IncompEmergencyOcuInterErr (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.IncompEmergencyOcuInterErr (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.30 Number of incomplete establishment calls for emergency by O-DU error detection - -- a) This counter provides the number of the call establishment for emergency interrupted by O-DU error detection. -- b) CC -- c) Measurement counter is incremented by 1 whenever call establishment for emergency is interrupted between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) by O-DU error detection (Call acceptance condition of CU/DU is not met). -- d) Each measurement is an integer value representing the number of the call establishment for emergency interrupted by O-DU error detection. -- e) OR.RRC.IncompEmergencyOduErrDetect (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ESTACALL.IncompEmergencyOduErrDetect (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.9.31 Void - -#### A.2.9.32 Discarded paging records - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.4 - -###### O-RAN addition: - -The counter is optionally split into subcounter per Paging Priority. - -The counter is optionally split into subcounter per Paging Origin. - -It is an optional counter for O-CU. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.4 - -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.4 - -###### O-RAN addition: - -The subcounter per Paging Priority level is incremented by 1 for each Paging Priority whenever a paging record is including Paging Priority is discarded at the gNB-CU. - -NOTE 1: Paging Priority is defined in 3GPP TS 38.413 [i.5], clause 9.3.1.78. - -The subcounter per Paging Origin level is incremented by 1 for each paging origin whenever a paging record including paging origin is discarded at the gNB-CU. - -NOTE 2: Paging Origin is defined in 3GPP TS 38.413 [i.5], clause 9.3.3.22. - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.4 - -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.4 - -###### O-RAN addition: - -Subcounter OR.PAG.DiscardedNbrCnInitiated.PagingPriority where *PagingPriority* is Paging Priority number: - -0: PrioLevel1 - -1: PrioLevel2 - -... - -7: PrioLevel8 - -Subcounter OR.PAG.DiscardedNbrCnInitiated.PagingOrigin where *PagingOrigin* identifies the Paging Origin IE. - -- f) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.4 - -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.4 - -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.4 - -- i) Network Operator's Traffic Engineering Community - -### A.2.10 Monitoring of PDU session connection for SA - -#### A.2.10.1 Accepted PDU Session Resource Configuration - -- a) This counter provides the number of the accepted PDU session resource configuration. The measurement is optionally calculated per QoS (mapped 5QI or QCI in EN-DC). -- b) CC -- c) Measurement subcounter is incremented by 1 whenever gNB received the following message, optionally calculated per QoS. - -NOTE: multiple 5QIs can be set per PDU session, each 5QI is counted per QoS flow. - -- "NG-AP: Initial Context Setup Request" is received - - "NG-AP: PDU Session Resource Setup Request" - - "NG-AP: PDU Session Resource Modify Request" -- d) Each measurement is an integer value representing the number of the accepted PDU session resource configuration. The measurement is optionally calculated per QoS (mapped 5QI or QCI in EN-DC). -- e) The measurement name has the form OR.SM.AcceptConfig or OR.SM.AcceptConfig\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDUSESSION.AcceptConfig or OR.PDUSESSION.AcceptConfig\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is QoS and represents the mapped 5QI or QCI level. -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.10.2 Completed PDU Session Resource Configuration - -- a) This counter provides the number of the completed PDU session resource configuration. The measurement is optionally calculated per QoS (5QI or QCI). -- b) CC -- c) Measurement subcounter is incremented by 1 whenever gNB transmitted the following message, optionally calculated per QoS. - -NOTE: multiple 5QIs can be set per PDU session, each 5QI is counted per QoS flow. - -- "NG-AP: Initial Context Setup Response" - - "NG-AP: PDU Session Resource Setup Response" - - "NG-AP: PDU Session Resource Modify Response" -- d) Each measurement is an integer value representing the number of the completed PDU session resource configuration. The measurement is optionally calculated per QoS (5QI or QCI). -- e) The measurement name has the form OR.SM.CompConfig or OR.SM.CompConfig\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDUSESSION.CompConfig or OR.PDUSESSION.CompConfig\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is QoS and represents the mapped 5QI or QCI level. -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.10.3 Interrupted PDU Session Resource configuration by Protocol Error - -- a) This counter provides the number of the PDU session resource configuration interrupted by protocol error. The measurement is optionally calculated per QoS (mapped 5QI or QCI in EN-DC). -- b) CC - -- c) Measurement subcounter is incremented by 1 whenever the PDU session resource configuration interrupted in the following interval by protocol error, optionally calculated per QoS. -- NOTE: multiple 5QIs can be set per PDU session, each 5QI is counted per QoS flow. -- between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) - - between Xn-AP: Handover Request to NG-AP: Path Switch Acknowledge (Inter gNB-CU HO w Xn) - - between NG-AP: Handover Request to NG-AP: Path Switch Acknowledge (Inter gNB-CU HO w/o Xn) - - between NG-AP: Handover Request to NG-AP: Handover Notify (Inter RAT HO to NR) - - between NG-AP: PDU Session Resource Setup Request to NG-AP: PDU Session Resource Setup Response (PDU Session Establishment) - - between NG-AP: PDU Session Resource Modify Request to NG-AP: PDU Session Resource Modify Response (PDU Session Modification) - - between NG-AP: PDU Session Resource Release Request to NG-AP: PDU Session Resource Release Response (PDU Session Release) -- d) Each measurement is an integer value representing the number of the PDU session resource configuration interrupted by protocol error. The measurement is optionally calculated per QoS (mapped 5QI or QCI in EN-DC). -- e) The measurement name has the form OR.SM.InterruptConfigProcolErr or OR.SM.InterruptConfigProcolErr\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDUSESSION.InterruptConfigProcolErr or OR.PDUSESSION.InterruptConfigProcolErr\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is QoS and represents the mapped 5QI or QCI level. -- f) NRCellICU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.10.4 Interrupted PDU Session Resource configuration by O-DU Error Detection - -- a) This counter provides the number of the PDU session resource configuration interrupted by O-DU error detection. The measurement is optionally calculated per QoS (mapped 5QI or QCI in EN-DC). -- b) CC -- c) Measurement subcounter is incremented by 1 whenever the PDU session resource configuration interrupted in the following interval by O-DU error detection, optionally calculated per QoS. - -NOTE: multiple 5QIs can be set per PDU session, each 5QI is counted per QoS flow. - -- between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) -- between Xn-AP: Handover Request to NG-AP: Path Switch Acknowledge (Inter gNB-CU HO w Xn) -- between NG-AP: Handover Request to NG-AP: Path Switch Acknowledge (Inter gNB-CU HO w/o Xn) -- between NG-AP: Handover Request to NG-AP: Handover Notify (Inter RAT HO to NR) -- between NG-AP: PDU Session Resource Setup Request to NG-AP: PDU Session Resource Setup Response (PDU Session Establishment) -- between NG-AP: PDU Session Resource Modify Request to NG-AP: PDU Session Resource Modify Response (PDU Session Modification) -- between NG-AP: PDU Session Resource Release Request to NG-AP: PDU Session Resource Release Response (PDU Session Release) - -- d) Each measurement is an integer value representing the number of the PDU session resource configuration interrupted by O-DU error detection. -- e) The measurement name has the form OR.SM.InterruptConfigOduErrDetect or OR.SM.InterruptConfigOduErrDetect\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDUSESSION.InterruptConfigOduErrDetect or OR.PDUSESSION.InterruptConfigOduErrDetect\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is QoS and represents the mapped 5QI or QCI level. -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.10.5 Interrupted PDU Session Resource configuration by O-CU internal error - -- a) This counter provides the number of the PDU session resource configuration interrupted by O-CU internal error. The measurement is optionally calculated per QoS (mapped 5QI or QCI in EN-DC). -- b) CC -- c) Measurement subcounter is incremented by 1 whenever the PDU session resource configuration interrupted in the following interval by O-CU internal error, optionally calculated per QoS. - -NOTE: multiple 5QIs can be set per PDU session, each 5QI is counted per QoS flow. - -- between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) - - between Xn-AP: Handover Request to NG-AP: Path Switch Acknowledge (Inter gNB-CU HO w Xn) - - between NG-AP: Handover Request to NG-AP: Path Switch Acknowledge (Inter gNB-CU HO w/o Xn) - - between NG-AP: Handover Request to NG-AP: Handover Notify (Inter RAT HO to NR) - - between NG-AP: PDU Session Resource Setup Request to NG-AP: PDU Session Resource Setup Response (PDU Session Establishment) - - between NG-AP: PDU Session Resource Modify Request to NG-AP: PDU Session Resource Modify Response (PDU Session Modification) - - between NG-AP: PDU Session Resource Release Request to NG-AP: PDU Session Resource Release Response (PDU Session Release) -- d) Each measurement is an integer value representing the number of the PDU session resource configuration interrupted by O-CU internal error. - - e) The measurement name has the form OR.SM.InterruptConfigOcuInterErr or OR.SM.InterruptConfigOcuInterErr\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDUSESSION.InterruptConfigOcuInterErr or OR.PDUSESSION.InterruptConfigOcuInterErr\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is QoS and represents the mapped 5QI or QCI level. - - f) NRCellCU - - g) Packet Switched - - h) 5GS - - i) Network Operator's Traffic Engineering Community - -#### A.2.10.6 Accepted PDU Session Resource Configuration for emergency and high priority access - -- a) This counter provides the number of the accepted PDU session resource configuration for emergency and high priority access. The measurement is optionally calculated per QoS (mapped 5QI or QCI in EN-DC). -- b) CC -- c) Measurement subcounter is incremented by 1 whenever gNB received the following message after received RRC: RRC Setup Request (Establishment Cause: emergency or high priority access), optionally calculated per QoS. - -NOTE: multiple 5QIs can be set per PDU session, each 5QI is counted per QoS flow. - -- received NG-AP: Initial Context Setup Request - - received NG-AP: PDU Session Resource Setup Request - - received NG-AP: PDU Session Resource Modify Request -- d) Each measurement is an integer value representing the number of the accepted PDU session resource configuration for emergency and high priority access. - - e) The measurement name has the form OR.SM.AcceptConfigEmergencyHighPriAccess or OR.SM.AcceptConfigEmergencyHighPriAccess\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDUSESSION.AcceptConfigEmergencyHighPriAccess or OR.PDUSESSION.AcceptConfigEmergencyHighPriAccess\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is QoS and represents the mapped 5QI or QCI level. - - f) NRCellCU - - g) Packet Switched - - h) 5GS - - i) Network Operator's Traffic Engineering Community - -#### A.2.10.7 Completed PDU Session Resource Configuration for emergency and high priority access - -- a) This counter provides the number of the completed PDU session resource configuration for emergency and high priority access. The measurement is optionally calculated per QoS (mapped 5QI or QCI in EN-DC). -- b) CC -- c) Measurement subcounter is incremented by 1 whenever gNB transmitted the following message after received RRC: RRC Setup Request (Establishment Cause: emergency or high priority access), optionally calculated per QoS. - -NOTE: multiple 5QIs can be set per PDU session, each 5QI is counted per QoS flow. - -- send NG-AP: Initial Context Setup Response - - send NG-AP: PDU Session Resource Setup Response - - send NG-AP: PDU Session Resource Modify Response -- d) Each measurement is an integer value representing the number of the completed PDU session resource configuration for emergency and high priority access. - - e) The measurement name has the form OR.SM.CompConfigEmergencyHighPriAccess or OR.SM.CompConfigEmergencyHighPriAccess\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDUSESSION.CompConfigEmergencyHighPriAccess or OR.PDUSESSION.CompConfigEmergencyHighPriAccess\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is QoS and represents the mapped 5QI or QCI level. - - f) NRCellCU - -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.10.8 Interrupted PDU Session Resource configuration for emergency and high priority access by Protocol Error - -- a) This counter provides the number of the PDU session resource configuration for emergency and high priority access interrupted by protocol error. The measurement is optionally calculated per QoS (mapped 5QI or QCI in EN-DC). -- b) CC -- c) Measurement subcounter is incremented by 1 whenever the PDU session resource configuration for emergency and high priority access interrupted in the following interval by protocol error, optionally calculated per QoS. - -NOTE: multiple 5QIs can be set per PDU session, each 5QI is counted per QoS flow. - -- between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) - - between Xn-AP: Handover Request to NG-AP: Path Switch Acknowledge (Inter gNB-CU HO w Xn) - - between NG-AP: Handover Request to NG-AP: Path Switch Acknowledge (Inter gNB-CU HO w/o Xn) - - between NG-AP: Handover Request to NG-AP: Handover Notify (Inter RAT HO to NR) - - between NG-AP: PDU Session Resource Setup Request to NG-AP: PDU Session Resource Setup Response (PDU Session Establishment) - - between NG-AP: PDU Session Resource Modify Request to NG-AP: PDU Session Resource Modify Response (PDU Session Modification) - - between NG-AP: PDU Session Resource Release Request to NG-AP: PDU Session Resource Release Response (PDU Session Release) -- d) Each measurement is an integer value representing the number of the PDU session resource configuration for emergency and high priority access interrupted by protocol error. -- e) The measurement name has the form OR.SM.InterruptConfigProcolErrEmergencyHighPriAccess or OR.SM.InterruptConfigProcolErrEmergencyHighPriAccess\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDUSESSION.InterruptConfigProcolErrEmergencyHighPriAccess or OR.PDUSESSION.InterruptConfigProcolErrEmergencyHighPriAccess\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is QoS and represents the mapped 5QI or QCI level. -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.10.9 Interrupted PDU Session Resource configuration for emergency and high priority access by O-DU Error Detection - -- a) This counter provides the number of the PDU session resource configuration for emergency and high priority access interrupted by O-DU error detection. The measurement is optionally calculated per QoS (mapped 5QI or QCI in EN-DC). -- b) CC - -- c) Measurement subcounter is incremented by 1 whenever the PDU session resource configuration for emergency and high priority access interrupted in the following interval by O-DU error detection, optionally calculated per QoS. - -NOTE: multiple 5QIs can be set per PDU session, each 5QI is counted per QoS flow. - -- between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) - - between Xn-AP: Handover Request to NG-AP: Path Switch Acknowledge (Inter gNB-CU HO w Xn) - - between NG-AP: Handover Request to NG-AP: Path Switch Acknowledge (Inter gNB-CU HO w/o Xn) - - between NG-AP: Handover Request to NG-AP: Handover Notify (Inter RAT HO to NR) - - between NG-AP: PDU Session Resource Setup Request to NG-AP: PDU Session Resource Setup Response (PDU Session Establishment) - - between NG-AP: PDU Session Resource Modify Request to NG-AP: PDU Session Resource Modify Response (PDU Session Modification) - - between NG-AP: PDU Session Resource Release Request to NG-AP: PDU Session Resource Release Response (PDU Session Release) -- d) Each measurement is an integer value representing the number of the PDU session resource configuration for emergency and high priority access interrupted by O-DU error detection. -- e) The measurement name has the form OR.SM.InterruptConfigOduErrDetectEmergencyHighPriAccess or OR.SM.InterruptConfigOduErrDetectEmergencyHighPriAccess\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDUSESSION.InterruptConfigOduErrDetectEmergencyHighPriAccess or OR.PDUSESSION.InterruptConfigOduErrDetectEmergencyHighPriAccess\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is QoS and represents the mapped 5QI or QCI level. -- f) NRCellICU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.10.10 Interrupted PDU Session Resource configuration for emergency and high priority access by O-CU internal Error - -- a) This counter provides the number of the PDU session resource configuration for emergency and high priority access interrupted by O-CU internal error. The measurement is optionally calculated per QoS (mapped 5QI or QCI in EN-DC). -- b) CC -- c) Measurement subcounter is incremented by 1 whenever the PDU session resource configuration for emergency and high priority access interrupted in the following interval by O-CU internal error, optionally calculated per QoS. - -NOTE: multiple 5QIs can be set per PDU session, each 5QI is counted per QoS flow. - -- between RRC: RRC Setup Request (or RRC: RRC Resume Request) to NG-AP: Initial Context Setup Response (or RRC: RRC Resume Complete) -- between Xn-AP: Handover Request to NG-AP: Path Switch Acknowledge (Inter gNB-CU HO w Xn) -- between NG-AP: Handover Request to NG-AP: Path Switch Acknowledge (Inter gNB-CU HO w/o Xn) -- between NG-AP: Handover Request to NG-AP: Handover Notify (Inter RAT HO to NR) -- between NG-AP: PDU Session Resource Setup Request to NG-AP: PDU Session Resource Setup Response (PDU Session Establishment) -- between NG-AP: PDU Session Resource Modify Request to NG-AP: PDU Session Resource Modify Response (PDU Session Modification) -- between NG-AP: PDU Session Resource Release Request to NG-AP: PDU Session Resource Release Response (PDU Session Release) - -- d) Each measurement is an integer value representing the number of the PDU session resource configuration for emergency and high priority access interrupted by O-CU internal error. -- e) The measurement name has the form OR.SM.InterruptConfigOcuInterErrEmergencyHighPriAccess or OR.SM.InterruptConfigOcuInterErrEmergencyHighPriAccess\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDUSESSION.InterruptConfigOcuInterErrEmergencyHighPriAccess or OR.PDUSESSION.InterruptConfigOcuInterErrEmergencyHighPriAccess\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is QoS and represents the mapped 5QI or QCI level. -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.2.11 Monitoring of mobility for SA - -#### A.2.11.1 Accepted Handover - -- a) This counter provides the number of the accepted Intra RAT handover. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever source gNB decides to perform Intra RAT HO procedure by the received (transmitted) following messages: - - Intra-Cell HO: transmitted "RRC: RRC Reconfiguration" - - HO procedure other than those above: received "RRC: Measurement report" -- d) Each measurement is an integer value representing the number of the accepted Intra RAT handover. -- e) OR.MM.AcceptHo (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.MOBILITY.AcceptHo (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.11.2 Completed Handover - -- a) This counter provides the number of the completed Intra RAT handover. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever source gNB detects successful Intra RAT handover procedure triggered by source gNB by the received following messages: - - Intra-gNB HO: received "RRC: RRC Reconfiguration Complete" - - HO procedure other than those above: received "XnAP: UE CONTEXT RELEASE" from the target gNB at Xn HO or "NGAP: UE CONTEXT RELEASE COMMAND" from AMF at NG HO -- d) Each measurement is an integer value representing the number of the completed Intra RAT handover. - -- e) OR.MM.CompHo (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.MOBILITY.CompHo (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.11.3 Accepted Inter RAT Handover to LTE - -- a) This counter provides the number of the accepted Inter RAT Handover to LTE. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever source gNB decides to perform Inter RAT HO to LTE procedure by the received following messages: - - received RRC: Measurement report (Inter RAT HO to LTE) -- d) Each measurement is an integer value representing the number of the accepted Inter RAT Handover to LTE. -- e) OR.MM.AcceptHotoLte (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.MOBILITY.AcceptHotoLte (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.11.4 Completed Inter RAT Handover to LTE - -- a) This counter provides the number of the completed Inter RAT Handover to LTE. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever source gNB detects successful handover procedure triggered by source gNB by the received following messages: - - received NG-AP: UE Context Release Command (Inter RAT HO to LTE) -- d) Each measurement is an integer value representing the number of the completed Inter RAT Handover to LTE. -- e) OR.MM.CompHotoLte (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.MOBILITY.CompHotoLte (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.11.5 Accepted EPS Fallback - -- a) This counter provides the number of the accepted EPS Fallback. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PCell decides to perform EPS Fallback procedure by the received following messages: - - received NG-AP: PDU Session Resource Modify Request (EPS Fallback) -- d) Each measurement is an integer value representing the number of the accepted EPS Fallback. -- e) OR.MM.AcceptEpsFallback (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.MOBILITY.AcceptEpsFallback (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.11.6 Completed EPS Fallback - -- a) This counter provides the number of the completed EPS Fallback. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PCell detects successful EPS Fallback procedure triggered by the received following messages: - - received NG-AP: UE Context Release Command (EPS Fallback) -- d) Each measurement is an integer value representing the number of the completed EPS Fallback. -- e) OR.MM.CompEpsFallback (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.MOBILITY.CompEpsFallback (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.11.7 Normal interrupted EPS Fallback - -- a) This counter provides the number of the completed EPS Fallback. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PCell detects interrupted EPS Fallback procedure triggered by the received following messages: - - received NG-AP: UE Context Release Command (Cause:Deregister) during EPS Fallback procedure -- d) Each measurement is an integer value representing the number of the completed EPS Fallback. - -- e) OR.MM.NormalInterruptedEpsFallback (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.MOBILITY.NormalInterruptedEpsFallback (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.11.8 Accepted Handover during Voice call - -- a) This counter provides the number of the accepted Intra RAT handover during voice call. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever source gNB decides to perform Intra RAT HO procedure by the received (transmitted) following messages during voice call: - - transmitted RRC: RRC Reconfiguration (Intra-cell HO) - - HO procedure other than those above: received RRC: Measurement report -- d) Each measurement is an integer value representing the number of the accepted Intra RAT handover during voice call. -- e) OR.MM.AcceptHoVoice (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.MOBILITY.AcceptHoVoice (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.11.9 Completed Handover during Voice call - -- a) This counter provides the number of the completed Intra RAT handover during voice call. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever source gNB detects successful Intra RAT handover procedure triggered by source gNB by the received following messages during voice call: - - received RRC: RRC Reconfiguration Complete (Intra gNB-CU Inter gNB-DU HO, Intra gNB-DU Inter-cell HO) - - HO procedure other than those above: received Xn-AP: UE CONTEXT RELEASE (Inter gNB-CU HO w/ Xn), -NG-AP: UE CONTEXT RELEASE COMMAND (Inter gNB-CU HO w/o Xn) -- d) Each measurement is an integer value representing the number of the completed Intra RAT handover during voice call. -- e) OR.MM.CompHoVoice (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.MOBILITY.CompHoVoice (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS - -- i) Network Operator's Traffic Engineering Community - -#### A.2.11.10 Accepted Inter RAT Handover to LTE during Voice call - -- a) This counter provides the number of the accepted Inter RAT handover to LTE during voice call. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever source gNB decides to perform Inter RAT HO to LTE procedure by the received following messages during voice call: - - received RRC: Measurement report that triggers Inter RAT HO to LTE -- d) Each measurement is an integer value representing the number of the accepted Inter RAT handover to LTE during voice call. -- e) OR.MM.AcceptHotoLteVoice (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.MOBILITY.AcceptHotoLteVoice (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.11.11 Completed Inter RAT Handover to LTE during Voice call - -- a) This counter provides the number of the completed Inter RAT handover during voice call. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever source gNB detects successful Inter RAT handover procedure triggered by source gNB by the received following messages during voice call: - - received NG-AP: UE CONTEXT RELEASE COMMAND from the AMF at Inter RAT HO to LTE -- d) Each measurement is an integer value representing the number of the completed Inter RAT handover during voice call. -- e) OR.MM.CompHotoLteVoice (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.MOBILITY.CompHotoLteVoice (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.2.12 Monitoring of RRC re-establishment for SA - -#### A.2.12.1 Number of initial RRC re-establishment requests when UE context can be retrieved - -- a) This counter provides the number of the received RRC: RRC Reestablishment Request messages via F1-C which is in the first time for each ReestabUE-Identity when UE context can be retrieved. -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Reestablishment Request message is received via F1-C when UE context can be retrieved, if RRC: RRC Reestablishment Request of the same ReestabUE-Identity is not received for a certain period of time from the reception timing. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Reestablishment Request messages via F1-C which is in the first time for each ReestabUE-Identity when UE context can be retrieved. -- e) OR.RRC.IniReqUecontext (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.REEST.IniReqUecontext (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.12.2 Number of RRC re-establishment request completions for initial RRC re-establishment requests when UE context can be retrieved - -- a) This counter provides the number of the received RRC: RRC Reconfiguration Complete messages via F1-C which corresponds to the initial RRC: RRC Reestablishment Request when UE context can be retrieved. -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Reconfiguration Complete message which corresponds to the initial RRC: RRC Reestablishment Request is received via F1-C when UE context can be retrieved. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Reconfiguration Complete messages via F1-C which corresponds to the initial RRC: RRC Reestablishment Request when UE context can be retrieved. -- e) OR.RRC.IniReqCompUecontext (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.REEST.IniReqCompUecontext (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.12.3 Number of retransmission RRC re-establishment requests when UE context can be retrieved - -- a) This counter provides the number of the received RRC: RRC Reestablishment Request messages via F1-C which is the retransmission for each ReestabUE-Identity when UE context can be retrieved. -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Reestablishment Request message is received via F1-C when UE context can be retrieved, if RRC: RRC Reestablishment Request message of the same ReestabUE-Identity is received for a certain period of time from the reception timing. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Reestablishment Request messages via F1-C which is the retransmission for each ReestabUE-Identity when UE context can be retrieved. -- e) OR.RRC.RetaransReqUecontext (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.REEST.RetaransReqUecontext (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.12.4 Number of RRC re-establishment request completions for retransmission RRC re-establishment request when UE context can be retrieved - -- a) This counter provides the number of the received RRC: RRC Reconfiguration Complete messages via F1-C which corresponds to the retransmission RRC: RRC Reestablishment Request when UE context can be retrieved. -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Reconfiguration Complete message which corresponds to the retransmission RRC: RRC Reestablishment Request is received via F1-C when UE context can be retrieved. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Reconfiguration Complete messages via F1-C which corresponds to the retransmission RRC: RRC Reestablishment Request when UE context can be retrieved. -- e) OR.RRC.RetaransReqCompUecontext (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.REEST.RetaransReqCompUecontext (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.12.5 Number of initial RRC re-establishment requests when UE context cannot be retrieved - -- a) This counter provides the number of the received RRC: RRC Reestablishment Request messages via F1-C which is in the first time for each ReestabUE-Identity when UE context cannot be retrieved. - -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Reestablishment Request message is received via F1-C when UE context cannot be retrieved, if RRC: RRC Reestablishment Request of the same ReestabUE-Identity is not received for a certain period of time from the reception timing. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Reestablishment Request messages via F1-C which is in the first time for each ReestabUE-Identity when UE context cannot be retrieved. -- e) OR.RRC.IniReqNotUecontext (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.REEST.IniReqNotUecontext (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.12.6 Number of RRC re-establishment request completions for initial RRC re-establishment requests when UE context cannot be retrieved - -- a) This counter provides the number of the received RRC: RRC Reconfiguration Complete messages via F1-C which corresponds to the initial RRC: RRC Reestablishment Request when UE context cannot be retrieved. -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Setup Complete message which corresponds to the initial RRC: RRC Reestablishment Request is received via F1-C when UE context cannot be retrieved. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Reconfiguration Complete messages via F1-C which corresponds to the initial RRC: RRC Reestablishment Request when UE context cannot be retrieved. -- e) OR.RRC.IniReqCompNotUecontext (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.REEST.IniReqCompNotUecontext (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.12.7 Number of retransmission RRC re-establishment requests when UE context cannot be retrieved - -- a) This counter provides the number of the received RRC: RRC Reestablishment Request messages via F1-C which is the retransmission for each ReestabUE-Identity when UE context cannot be retrieved. -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Reestablishment Request message is received via F1-C when UE context cannot be retrieved, if RRC: RRC Reestablishment Request message of the same ReestabUE-Identity is received for a certain period of time from the reception timing. - -- d) Each measurement is an integer value representing the number of the received RRC: RRC Reestablishment Request messages via F1-C which is the retransmission for each ReestabUE-Identity when UE context cannot be retrieved. -- e) OR.RRC.RetransReqNotUecontext (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.REEST.RetransReqNotUecontext (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.12.8 Number of RRC re-establishment request completions for retransmission RRC re-establishment requests when UE context cannot be retrieved - -- a) This counter provides the number of the received RRC: RRC Reconfiguration Complete messages via F1-C which corresponds to the retransmission RRC: RRC Reestablishment Request when UE context cannot be retrieved. -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Reconfiguration Complete message which corresponds to the retransmission RRC: RRC Reestablishment Request is received via F1-C when UE context cannot be retrieved. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Reconfiguration Complete messages via F1-C which corresponds to the retransmission RRC: RRC Reestablishment Request when UE context cannot be retrieved. -- e) OR.RRC.RetransReqCompNotUecontext (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.REEST.RetransReqCompNotUecontext (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.12.9 Number of initial RRC re-establishment requests during Voice call when UE context can be retrieved - -- a) This counter provides the number of the received RRC: RRC Reestablishment Request messages via F1-C which is in the first time for each ReestabUE-Identity during voice call when UE context can be retrieved. -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Reestablishment Request message is received via F1-C during voice call when UE context can be retrieved, if RRC: RRC Reestablishment Request of the same ReestabUE-Identity is not received for a certain period of time from the reception timing. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Reestablishment Request messages via F1-C which is in the first time for each ReestabUE-Identity during voice call when UE context can be retrieved. -- e) OR.RRC.IniReqUecontextVoice (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.REEST.IniReqUecontextVoice (deprecated, refer to NOTE in REQ-PMeas-MC-5) - -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.12.10 Number of RRC re-establishment request completions for initial RRC re-establishment requests during Voice call when UE context can be retrieved - -- a) This counter provides the number of the received RRC: RRC Reconfiguration Complete messages via F1-C which corresponds to the initial RRC: RRC Reestablishment Request during voice call when UE context can be retrieved. -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Reconfiguration Complete message which corresponds to the initial RRC: RRC Reestablishment Request is received via F1-C during voice call when UE context can be retrieved. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Reconfiguration Complete messages via F1-C which corresponds to the initial RRC: RRC Reestablishment Request during voice call when UE context can be retrieved. -- e) OR.RRC.IniReqCompUecontextVoice (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.REEST.IniReqCompUecontextVoice (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.12.11 Number of retransmission RRC re-establishment requests during Voice call when UE context can be retrieved - -- a) This counter provides the number of the received RRC: RRC Reestablishment Request messages via F1-C which is the retransmission for each ReestabUE-Identity during voice call when UE context can be retrieved. -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Reestablishment Request message is received via F1-C during voice call when UE context can be retrieved, if RRC: RRC Reestablishment Request message of the same ReestabUE-Identity is received for a certain period of time from the reception timing. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Reestablishment Request messages via F1-C which is the retransmission for each ReestabUE-Identity during voice call when UE context can be retrieved. -- e) OR.RRC.RetaransReqUecontextVoice (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.REEST.RetaransReqUecontextVoice (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched - -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.12.12 Number of RRC re-establishment request completions for retransmission RRC re-establishment request during Voice call when UE context can be retrieved - -- a) This counter provides the number of the received RRC: RRC Reconfiguration Complete messages via F1-C which corresponds to the retransmission RRC: RRC Reestablishment Request during voice call when UE context can be retrieved. -- b) CC -- c) Measurement counter is incremented by 1 whenever RRC: RRC Reconfiguration Complete message which corresponds to the retransmission RRC: RRC Reestablishment Request is received via F1-C during voice call when UE context can be retrieved. -- d) Each measurement is an integer value representing the number of the received RRC: RRC Reconfiguration Complete messages via F1-C which corresponds to the retransmission RRC: RRC Reestablishment Request during voice call when UE context can be retrieved. -- e) OR.RRC.RetaransReqCompUecontextVoice (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.REEST.RetaransReqCompUecontextVoice (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.2.13 Monitoring of connection status for SA - -#### A.2.13.1 Normally Released Calls - -- a) This counter provides the number of the normally released calls. -- b) CC -- c) Measurement subcounter is incremented by the number of the normally released calls. Normal released calls is as follows: - - received NG-AP: UE Context Release Command (Cause: Normal release or Deregister) - - the expiry of a UE inactivity timer, the gNB release the RRC connection -- d) Each measurement is an integer value representing the number of the normally released calls. -- e) OR.UECNTX.NormalRelCalls (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CONNECTSTATUS.NormalRelCalls (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.13.2 Abnormally Released Calls - -- a) This counter provides the number of the abnormally released calls. -- b) CC -- c) Measurement subcounter is incremented by the number of the abnormally released calls. - - Trigger timing: when gNB release the UE Context except for the Normally Released calls (A.2.13.1) and Another Cell HO UE Contexts (A.2.13.3). -- d) Each measurement is an integer value representing the number of the abnormally released calls. -- e) OR.UECNTX.AbnormallRelCalls (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CONNECTSTATUS.AbnormallRelCalls (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellICU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.13.3 Another Cell HO UE Contexts - -- a) This counter provides the number of the UE Contexts which has transferred to another cell. -- b) CC -- c) Measurement subcounter is incremented by the number of the UE Contexts which has transferred to another cell. Another Cell released call is as follows: - - received Xn-AP: UE Context Release (Inter gNB-CU HO w/ Xn, RRC Connection Re-establishment (Inter gNB-CU)) - - received NG-AP: UE Context Release Command (Inter gNB-CU HO w/o Xn, Inter-RAT HO to LTE, EPS fallback) - - received RRC: RRC Reconfiguration Complete (Intra gNB-DU Inter-cell HO, RRC Connection Re-establishment (Intra gNB-DU Inter-cell)) - - received F1-AP: UE Context Release Command (Intra gNB-CU Inter gNB-DU HO, RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU)) -- d) Each measurement is an integer value representing the number of the UE Contexts which has transferred to another cell. -- e) OR.UECNTX.AnotherCellHoUes (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CONNECTSTATUS.AnotherCellHoUes (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellICU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.13.4 Normally Released Calls during voice call - -- a) This counter provides the number of the normally released calls during voice call. -- b) CC -- c) Measurement subcounter is incremented by the number of the normally released calls during voice call. Normal released calls are as follows: - - received NG-AP: UE Context Release Command (Cause: Normal release or Deregister) - - the expiry of a UE inactivity timer, the gNB release the RRC connection -- d) Each measurement is an integer value representing the number of the normally released calls during voice call. -- e) OR.UECNTX.NormalRelCallsVoice (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CONNECTSTATUS.NormalRelCallsVoice (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellICU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.13.5 Abnormally Released Calls during voice call - -- a) This counter provides the number of the abnormally released calls during voice call. -- b) CC -- c) Measurement subcounter is incremented by the number of the abnormally released calls during voice call. - - Trigger timing: when gNB release the UE Context except for the Normally Released calls (A.2.13.4) and Another Cell HO UE contexts (A.2.13.6) during voice call. -- d) Each measurement is an integer value representing the number of the abnormally released calls during voice call. -- e) OR.UECNTX.AbnormalRelCallsVoice (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CONNECTSTATUS.AbnormalRelCallsVoice (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellICU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.13.6 Another Cell HO UE Contexts during voice call - -- a) This counter provides the number of the UE Contexts which has transferred to another cell during voice call. -- b) CC -- c) Measurement subcounter is incremented by the number of the UE Contexts which has transferred to another cell during voice call. Another Cell released calls are as follows: - -- received Xn-AP: UE Context Release (Inter gNB-CU HO w/ Xn, RRC Connection Re-establishment (Inter gNB-CU)) - - received NG-AP: UE Context Release Command (Inter gNB-CU HO w/o Xn, Inter-RAT HO to LTE, EPS fallback) - - received RRC: RRC Reconfiguration Complete (Intra gNB-DU Inter-cell HO, RRC Connection Re-establishment (Intra gNB-DU Inter-cell)) - - received F1-AP: UE Context Release Command (Intra gNB-CU Inter gNB-DU HO, RRC Connection Re-establishment (Intra gNB-CU Inter gNB-DU)) -- d) Each measurement is an integer value representing the number of the UE Contexts which has transferred to another cell during voice call. - - e) OR.UECNTX.AnotherCellHoUesVoice (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CONNECTSTATUS.AnotherCellHoUesVoice (deprecated, refer to NOTE in REQ-PMeas-MC-5) - - f) NRCellCU - - g) Packet Switched - - h) 5GS - - i) Network Operator's Traffic Engineering Community - -### A.2.14 Monitoring of procedure for NR-DC - -#### A.2.14.1 Number of S-NG-RAN Node Addition procedure attempted for each Cell - -- a) This counter provides the number of the transmitted Xn-AP: S-NODE ADDITION REQUEST ACKNOWLEDGE message. -- b) CC -- c) Measurement counter is incremented by 1 whenever Xn-AP: S-NODE ADDITION REQUEST ACKNOWLEDGE message is transmitted as PSCell. -- d) Each measurement is an integer value representing the number of the transmitted Xn-AP: S-NODE ADDITION REQUEST ACKNOWLEDGE message. -- e) OR.UECNTX.SnAddAttemptCell (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.NRDCPROCEDURE.SnAddAttemptCell (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.14.2 Number of S-NG-RAN Node Addition procedure successfully for each Cell - -- a) This counter provides the number of the completed S-NG-RAN Node addition Procedure. -- b) CC -- c) Measurement counter is incremented by 1 whenever S-NG-RAN Node addition procedure is completed as PSCell (i.e. Xn-AP: S-NODE RECONFIGURATION COMPLETE message (SN addition complete) is received and RACH processing with UE Context is completed). - -- d) Each measurement is an integer value representing the number of the completed S-NG-RAN Node addition Procedure. -- e) OR.UECNTX.SnAddSuccessCell (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.NRDCPROCEDURE.SnAddSuccessCell (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.14.3 Number of S-NG-RAN Node Addition procedure attempted for each neighbour gNB - -- a) This counter provides the number of the transmitted Xn-AP: S-NODE ADDITION REQUEST ACKNOWLEDGE messages. - -This counter is split into subcounters per neighbour gNB. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever Xn-AP: S-NODE ADDITION REQUEST ACKNOWLEDGE message is transmitted when the gNB configured by the message is group of subcounter.*neighbourNB*. -- d) Each measurement is an integer value representing the number of the transmitted Xn-AP: S-NODE ADDITION REQUEST ACKNOWLEDGE messages. -- e) OR.UECNTX.SnAddAttemptNeiGnb.*neighbourNB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.NRDCPROCEDURE.SnAddAttemptNeiGnb.*neighbourNB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *neighbourNB* is neighbour gNB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.14.4 Number of S-NG-RAN Node Addition procedure successfully for each neighbour gNB - -- a) This counter provides the number of the completed S-NG-RAN Node addition Procedure. - -This counter is split into subcounters per neighbour gNB. - -- b) CC -- c) Measurement counter is incremented by 1 whenever S-NG-RAN Node addition procedure is completed (i.e. Xn-AP: S-NODE RECONFIGURATION COMPLETE message (SN addition complete) is received and RACH processing with UE Context is completed) when the gNB configured by the message is group of subcounter.*neighbourNB*. -- d) Each measurement is an integer value representing the number of the completed S-NG-RAN Node addition Procedure. - -- e) OR.UECNTX.SnAddSuccessNeiGnb.*neighbourNB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.NRDCPROCEDURE.SnAddSuccessNeiGnb.*neighbourNB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *neighbourNB* is neighbour gNB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.14.5 Number of S-NG-RAN Node modification procedure attempted for each Cell - -- a) This counter provides the number of the received Xn-AP: S-NODE MODIFICATION REQUEST messages or transmitted Xn-AP: S-NODE MODIFICATION REQUIRED messages. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever Xn-AP: S-NODE MODIFICATION REQUEST message is received or Xn-AP: S-NODE MODIFICATION REQUIRED message is transmitted as PSCell. - -Double counting is not performed if the procedure is changed to the MN initiated SN Modification procedure after transmitted Xn-AP: S-NODE MODIFICATION REQUIRED message (e.g. Measurement gap Coordination (SN initiated)). - -This subcounter will not be incremented if received Xn-AP: S-NODE MODIFICATION REQUEST message which True is set for SCG Configuration Query IE. - -- d) Each measurement is an integer value representing the number of the received Xn-AP: S-NODE MODIFICATION REQUEST messages or transmitted Xn-AP: S-NODE MODIFICATION REQUIRED messages. -- e) OR.UECNTX.SnModAttemptCell (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.NRDCPROCEDURE.SnModAttemptCell (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.14.6 Number of S-NG-RAN Node modification procedure successfully for each Cell - -- a) This counter provides the number of the completed S-NG-RAN Node modification Procedure. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever SN Modification procedure is completed as PSCell (i.e. Xn-AP: S-NODE RECONFIGURATION COMPLETE message (SN modification complete) is received or Xn-AP: S-NODE MODIFICATION CONFIRM is received and RACH processing with UE Context is completed) - -- d) Each measurement is an integer value representing the number of the completed S-NG-RAN Node modification Procedure. -- e) OR.UECNTX.SnModSuccessCell (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.NRDCPROCEDURE.SnModSuccessCell (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellICU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.14.7 Number of S-NG-RAN Node modification procedure attempted for each neighbour gNB - -- a) This counter provides the number of the received Xn-AP: S-NODE MODIFICATION REQUEST messages or transmitted Xn-AP: S-NODE MODIFICATION REQUIRED messages. - -This counter is split into subcounters per neighbour gNB. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever Xn-AP: S-NODE MODIFICATION REQUEST message is received or Xn-AP: S-NODE MODIFICATION REQUIRED message is transmitted, when the gNB configured by the message is group of subcounter.*neighbourgNB*. - -Double counting is not performed if the procedure is changed to the MN initiated SN Modification procedure after transmitted Xn-AP: S-NODE MODIFICATION REQUIRED message (e.g. Measurement gap Coordination (SN initiated)). - -This subcounter will not be incremented if received Xn-AP: S-NODE MODIFICATION REQUEST message which True is set for SCG Configuration Query IE. - -- d) Each measurement is an integer value representing the number of the received Xn-AP: S-NODE MODIFICATION REQUEST messages or transmitted Xn-AP: S-NODE MODIFICATION REQUIRED messages. -- e) OR.UECNTX.SnModAttemptNeiGnb.*neighbourgNB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.NRDCPROCEDURE.SnModAttemptNeiGnb.*neighbourgNB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *neighbourgNB* is neighbour gNB index: - -0: #0 -1: #1 -... -63: #63 - -- f) NRCellICU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.14.8 Number of S-NG-RAN Node modification procedure successfully for each neighbour gNB - -- a) This counter provides the number of the completed S-NG-RAN Node modification Procedure. -This counter is split into subcounters per neighbour gNB. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever SN Modification procedure is completed (i.e. Xn-AP: S-NODE RECONFIGURATION COMPLETE message (SN modification complete) is received or Xn-AP: S-NODE MODIFICATION CONFIRM is received and RACH processing with UE Context is completed) when the gNB configured by the message is group of subcounter.*neighbourgNB*. -- d) Each measurement is an integer value representing the number of the completed S-NG-RAN Node modification Procedure. -- e) OR.UECNTX.SnModSuccessNeiGnb.*neighbourgNB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.NRDCPROCEDURE.SnModSuccessNeiGnb.*neighbourgNB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *neighbourgNB* is neighbour gNB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.14.9 Number of S-NG-RAN Node Release procedure attempted for each Cell - -- a) This counter provides the number of the received Xn-AP: S-NODE RELEASE REQUIRED messages or transmitted Xn-AP: S-NODE RELEASE REQUEST messages. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever Xn-AP: S-NODE RELEASE REQUIRED message is received or Xn-AP: S-NODE RELEASE REQUEST message is transmitted as PSCell. -- d) Each measurement is an integer value representing the number of the received Xn-AP: S-NODE RELEASE REQUIRED messages or transmitted Xn-AP: S-NODE RELEASE REQUEST messages. -- e) OR.UECNTX.SnRelAttemptCell (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.NRDCPROCEDURE.SnRelAttemptCell (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.14.10 Number of S-NG-RAN Node Release procedure successfully for each Cell - -- a) This counter provides the number of the completed S-NG-RAN Node Release Procedure. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever SN Release procedure is completed as PSCell (i.e. Xn-AP: UE CONTEXT RELEASE message is transmitted) -- d) Each measurement is an integer value representing the number of the completed S-NG-RAN Node Release Procedure. -- e) OR.UECNTX.SnRelSuccessCell (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.NRDCPROCEDURE.SnRelSuccessCell (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellICU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.14.11 Number of S-NG-RAN Node Release procedure attempted for each neighbour gNB - -- a) This counter provides the number of the received Xn-AP: S-NODE RELEASE REQUIRED messages or transmitted Xn-AP: S-NODE RELEASE REQUEST messages. - -This counter is split into subcounters per neighbour gNB. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever Xn-AP: S-NODE RELEASE REQUIRED message is received or Xn-AP: S-NODE RELEASE REQUEST message is transmitted, when the gNB configured by the message is group of subcounter.*neighbourNB*. -- d) Each measurement is an integer value representing the number of the received Xn-AP: S-NODE RELEASE REQUIRED messages or transmitted Xn-AP: S-NODE RELEASE REQUEST messages. -- e) OR.UECNTX.SnRelAttemptNeiGnb.*neighbourNB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.NRDCPROCEDURE.SnRelAttemptNeiGnb.*neighbourNB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *neighbourNB* is neighbour gNB index: - -0: #0 -1: #1 -... -63: #63 -- f) NRCellICU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.14.12 Number of S-NG-RAN Node Release procedure successfully for each neighbour gNB - -- a) This counter provides the number of the completed S-NG-RAN Node Release Procedure. -This counter is split into subcounters per neighbour gNB. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever SN Release procedure is completed (i.e. Xn-AP: UE CONTEXT RELEASE message is transmitted) -- d) Each measurement is an integer value representing the number of the completed S-NG-RAN Node Release Procedure. -- e) OR.UECNTX.SnRelSuccessNeiGnb.*neighbourNB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.NRDCPROCEDURE.SnRelSuccessNeiGnb.*neighbourNB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *neighbourNB* is neighbour gNB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.14.13 Number of SCGFailureInformation received - -- a) This counter provides the number of SCGFailureInformation received. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RRC: SCG Failure Information message is received. -- d) Each measurement is an integer value representing the number of SCGFailureInformation received. -- e) OR.RRC.NumFailInfoRec (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.NRDCPROCEDURE.NumFailInfoRec (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.2.15 Monitoring of CA for SA - -#### A.2.15.1 Number of SCell Addition procedure attempted - -- a) This counter provides the number of the attempted SCell addition procedure. -- b) CC - -- c) Measurement subcounter is incremented by 1 whenever PCell decides to perform SCell addition procedure by the following trigger. - - received RRC: Measurement report for SCell addition. - - SCell addition triggered internal the gNB other than above trigger. -- d) Each measurement is an integer value representing the number of the attempted SCell addition procedure. -- e) OR.RRC.ScellAddAttempt (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.SACAPROCEDURE.ScellAddAttempt (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.15.2 Number of SCell Addition procedure successfully - -- a) This counter provides the number of the completed SCell addition procedure. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PCell detects successful SCell addition procedure by the received following messages. - - received RRC: RRC Reconfiguration Complete for SCell addition. -- d) Each measurement is an integer value representing the number of the completed SCell addition procedure. -- e) OR.RRC.ScellAddSuccess (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.SACAPROCEDURE.ScellAddSuccess (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.15.3 Number of SCell Change procedure attempted - -- a) This counter provides the number of the attempted SCell change procedure. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PCell decides to perform SCell change procedure by the following trigger. - - received RRC: Measurement report for SCell change. - - SCell change triggered internal the gNB other than above trigger. -- d) Each measurement is an integer value representing the number of the attempted SCell change procedure. -- e) OR.RRC.ScellChangeAttempt (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.SACAPROCEDURE.ScellChangeAttempt (deprecated, refer to NOTE in REQ-PMeas-MC-5) - -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.15.4 Number of SCell Change procedure successfully - -- a) This counter provides the number of the completed SCell change procedure. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PCell detects successful SCell change procedure by the received following messages. - - received RRC: RRC Reconfiguration Complete for SCell change. -- d) Each measurement is an integer value representing the number of the completed SCell change procedure. -- e) OR.RRC.ScellChangeSuccess (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.SACAPROCEDURE.ScellChangeSuccess (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.15.5 Number of SCell Deletion procedure attempted - -- a) This counter provides the number of the attempted SCell deletion procedure. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PCell decides to perform SCell deletion procedure by the following trigger. - - received RRC: Measurement report for SCell deletion. - - SCell deletion triggered internal the gNB other than above trigger. -- d) Each measurement is an integer value representing the number of the attempted SCell deletion procedure. -- e) OR.RRC.ScellDeletionAttempt (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.SACAPROCEDURE.ScellDeletionAttempt (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.2.15.6 Number of SCell Deletion procedure successfully - -- a) This counter provides the number of the completed SCell deletion procedure. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PCell detects successful SCell deletion procedure by the received following messages. - - received RRC: RRC Reconfiguration Complete for SCell deletion. -- d) Each measurement is an integer value representing the number of the completed SCell deletion procedure. -- e) OR.RRC.ScellDeletionSuccess (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.SACAPROCEDURE.ScellDeletionSuccess (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -## A.3 O-CU-UP Performance measurements - -### A.3.1 NR PDCP performance measurements - -#### A.3.1.1 Distribution of UE per UL received data volume - -- a) This counter provides the distribution of the UE per received uplink data volume. When more than one RLCs are configured, the data volume refers to all volume regardless through which RLC the data is transferred. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) If O-CU connects 5GC, the measurement is the number of the QoS flow of which x is mapped to bin of subcounter.*binX*. -If O-CU connects EPC, the measurement is the number of the bearer of which x is mapped to the bin of subcounter.*binX*. -The number, x is acquired and calculated at the end of granularity period. - -x is incremented by the volume of the UL PDCP PDU volume whenever the UL PDCP PDU is received from lower layer, and optionally when the UL PDCP PDU is mapped to the filter. -- d) Each measurement is an integer value representing the distribution of the UE per received uplink data volume. -- e) The measurement name has the form OR.DRB.DistUeUIRxData.*binX* or OR.DRB.DistUeUIRxData.*binX\_Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDCP.DistUeUIRxData.*binX* or OR.PDCP.DistUeUIRxData.*binX\_Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI, and where *binX* is the bin of the throughput, x: - - bin 1: 0 Byte < x < 1 kByte - - bin 2: 1 kByte ≤ x < 2 kByte - - bin 3: 2 kByte ≤ x < 5 kByte - - bin 4: 5 kByte ≤ x < 10 kByte - - bin 5: 10 kByte ≤ x < 20 kByte - - bin 6: 20 kByte ≤ x < 50 kByte - -bin 7: $50 \text{ kByte} \leq x < 100 \text{ kByte}$ - bin 8: $100 \text{ kByte} \leq x < 200 \text{ kByte}$ - bin 9: $200 \text{ kByte} \leq x < 500 \text{ kByte}$ - bin 10: $500 \text{ kByte} \leq x < 1 \text{ MByte}$ - bin 11: $1 \text{ MByte} \leq x < 1.5 \text{ MByte}$ - bin 12: $1.5 \text{ MByte} \leq x < 2 \text{ MByte}$ - bin 13: $2 \text{ MByte} \leq x < 2.5 \text{ MByte}$ - bin 14: $2.5 \text{ MByte} \leq x < 3 \text{ MByte}$ - bin 15: $3 \text{ MByte} \leq x < 3.5 \text{ MByte}$ - bin 16: $3.5 \text{ MByte} \leq x < 4 \text{ MByte}$ - bin 17: $4 \text{ MByte} \leq x < 4.5 \text{ MByte}$ - bin 18: $4.5 \text{ MByte} \leq x < 5 \text{ MByte}$ - bin 19: $5 \text{ MByte} \leq x < 10 \text{ MByte}$ - bin 20: $10 \text{ MByte} \leq x$ - -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.1.2 Distribution of DL UE throughput in O-CU - -- a) This counter provides the distribution of the UE throughput in downlink. When more than one RLCs are configured, the data volume refers to the all volume regardless through which RLC the data is transferred. -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) If O-CU connects 5GC, the measurement is the number of the QoS flow of which throughput, $x/y$ is mapped to bin of subcounter.*binX*. - -If O-CU connects EPC, the measurement is the number of the bearer of which throughput, $x/y$ is mapped to bin of subcounter.*binX*. - -The number, $x/y$ is acquired and calculated at the end of granularity period. - -$x$ is incremented by the volume of the DL PDCP PDU volume which is acknowledged by the DDDS whenever DDDS is received, and optionally when PDCP PDU is mapped to the filter. - -$y$ is the smaller value in the followings: - -- $y = \Sigma(y1 - y2)$ : -where $y1$ is the point in time after $y2$ when data up until the second last piece of data in the transmitted data burst which emptied the PDCP SDU available for transmission for the filterable group was successfully transmitted, as acknowledged by the UE, and where $y2$ is the point in time when the first transmission begins after a PDCP SDU becomes available for transmission, where previously no PDCP SDUs were available for transmission for the particular filter. - - The measurement reporting period could be pre-defined (e.g: 60000 ms). -- d) Each measurement is an integer value representing the distribution of the UE throughput in downlink. - - e) The measurement name has the form OR.DRB.DistDIUEThroughput.*binX* or OR.DRB.DistDIUEThroughput.*binX\_Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDCP.DistDIUEThroughput.*binX* or OR.PDCP.DistDIUEThroughput.*binX\_Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a - -combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI, and where *binX* is the bin of the throughput, *x/y*: - -bin 1: $0 \text{ Mbps} \leq x/y < 1 \text{ Mbps}$ -bin 2: $1 \text{ Mbps} \leq x/y < 2 \text{ Mbps}$ -bin 3: $2 \text{ Mbps} \leq x/y < 5 \text{ Mbps}$ -bin 4: $5 \text{ Mbps} \leq x/y < 10 \text{ Mbps}$ -bin 5: $10 \text{ Mbps} \leq x/y < 20 \text{ Mbps}$ -bin 6: $20 \text{ Mbps} \leq x/y < 50 \text{ Mbps}$ -bin 7: $50 \text{ Mbps} \leq x/y < 100 \text{ Mbps}$ -bin 8: $100 \text{ Mbps} \leq x/y < 200 \text{ Mbps}$ -bin 9: $200 \text{ Mbps} \leq x/y < 500 \text{ Mbps}$ -bin 10: $500 \text{ Mbps} \leq x/y < 1 \text{ Gbps}$ -bin 11: $1 \text{ Gbps} \leq x/y < 1.5 \text{ Gbps}$ -bin 12: $1.5 \text{ Gbps} \leq x/y < 2 \text{ Gbps}$ -bin 13: $2 \text{ Gbps} \leq x/y < 2.5 \text{ Gbps}$ -bin 14: $2.5 \text{ Gbps} \leq x/y < 3 \text{ Gbps}$ -bin 15: $3 \text{ Gbps} \leq x/y < 3.5 \text{ Gbps}$ -bin 16: $3.5 \text{ Gbps} \leq x/y < 4 \text{ Gbps}$ -bin 17: $4 \text{ Gbps} \leq x/y < 4.5 \text{ Gbps}$ -bin 18: $4.5 \text{ Gbps} \leq x/y < 5 \text{ Gbps}$ -bin 19: $5 \text{ Gbps} \leq x/y < 10 \text{ Gbps}$ -bin 20: $10 \text{ Gbps} \leq x/y$ - -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.1.3 Total discarded UL PDCP SDU volume - -- a) This counter provides the UL PDCP SDU volume discarded at PDCP due to any cause. -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement counter is incremented by the volume of the UL PDCP SDU whenever the UL PDCP SDU is discarded, and optionally when the UL PDCP SDU is mapped to the filter. -- d) Each measurement is an integer value representing the UL PDCP SDU volume discarded at PDCP due to any cause in kilobits. -- e) The measurement name has the form OR.DRB.TotalDiscardedUIPdcpSduVol or OR.DRB.TotalDiscardedUIPdcpSduVol\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDCP.TotalDiscardedUIPdcpSduVol or OR.PDCP.TotalDiscardedUIPdcpSduVol\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level and SNSSAI represents S-NSSAI. -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.1.4 UL PDCP SDU volume discarded due to bearer release - -- a) This counter provides the UL PDCP SDU volume discarded at PDCP due to bearer release. -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement counter is incremented by the volume of the UL PDCP SDU whenever the UL PDCP SDU is discarded due to bearer release, and optionally when the UL PDCP SDU is mapped to the filter. -- d) Each measurement is an integer value representing the UL PDCP SDU volume discarded at PDCP due to bearer release in kilobits. -- e) The measurement name has the form OR.DRB.UIPdcpSduVolDiscardBearerRel or OR.DRB.UIPdcpSduVolDiscardBearerRel\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDCP.UIPdcpSduVolDiscardBearerRel or OR.PDCP.UIPdcpSduVolDiscardBearerRel\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.1.5 Total discarded DL PDCP SDU volume - -- a) This counter provides the DL PDCP SDU volume discarded at PDCP due to any causes. -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement counter is incremented by the volume of the DL PDCP SDU whenever the DL PDCP SDU is discarded, and optionally when the DL PDCP SDU is mapped to the filter. -- d) Each measurement is an integer value representing the DL PDCP SDU volume discarded at PDCP due to any causes in kilobits. -- e) The measurement name has the form OR.DRB.TotalDiscardedDIPdcpSduVol or OR.DRB.TotalDiscardedDIPdcpSduVol\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDCP.TotalDiscardedDIPdcpSduVol or OR.PDCP.TotalDiscardedDIPdcpSduVol\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level, SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.1.6 DL PDCP SDU volume discarded due to bearer release - -- a) This counter provides the DL PDCP SDU volume discarded at PDCP due to bearer release. -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement counter is incremented by the volume of the DL PDCP SDU whenever the DL PDCP SDU is discarded due to bearer release, and optionally when the DL PDCP SDU is mapped to the filter. -- d) Each measurement is an integer value representing the DL PDCP SDU volume discarded at PDCP due to bearer release in kilobits. -- e) The measurement name has the form OR.DRB.DIPdcpSduVolDiscardLessBearerRel or OR.DRB.DIPdcpSduVolDiscardLessBearerRel\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDCP.DIPdcpSduVolDiscardLessBearerRel or OR.PDCP.DIPdcpSduVolDiscardLessBearerRel\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.1.7 DL PDCP SDU volume discarded due to out of memory - -- a) This counter provides the DL PDCP SDU volume discarded at PDCP due to out of memory. -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement counter is incremented by the volume of the DL PDCP SDU whenever the DL PDCP SDU is discarded due to out of memory, and optionally when the DL PDCP SDU is mapped to the filter. -- d) Each measurement is an integer value representing the DL PDCP SDU volume discarded at PDCP due to out of memory in kilobits. -- e) The measurement name has the form OR.DRB.DIPdcpSduVolDiscardOutOfMemory or optionally OR.DRB.DIPdcpSduVolDiscardOutOfMemory\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDCP.DIPdcpSduVolDiscardOutOfMemory or optionally OR.PDCP.DIPdcpSduVolDiscardOutOfMemory\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.1.8 PDCP transmission stop - -- a) This counter provides the number of the detection of PDCP transmission stop. -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement counter is incremented by 1 whenever PDCP transmission stop is occurred, and optionally when the PDCP SDU is mapped to the filter. It is incremented by 1 at most in each filter for one radio bearer until the transmission stop is resolved. -- d) Each measurement is an integer value representing the number of the detection of PDCP transmission stop. -- e) The measurement name has the form OR.DRB.TxStop or optionally OR.DRB.TxStop\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDCP.TxStop or optionally OR.PDCP.TxStop\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.1.9 UL F1-U packet loss rate - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.2 -O-RAN addition: -The split into subcounters per S-NSSAI is recommended when the Slicing feature is supported. -The split into subcounters per QoS is recommended where QoS identifies the target quality of service class. -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.2 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.2 -O-RAN addition: -The numbers are accumulated in the granularity period T. -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.2 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.2 -- f) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.2 -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.2 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.2 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.2 - -#### A.3.1.10 UL PDCP SDU Loss Rate - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.1 -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.1 - -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.1 - -###### O-RAN addition: - -The numbers are accumulated in the granularity period T. - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.1 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.1 -- f) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.1 -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.1 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.1 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.1 - -#### A.3.1.11 DL PDCP SDU Loss Rate - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.1 -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.1 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.1 - -###### O-RAN addition: - -The numbers are accumulated in the granularity period T. - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.1 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.1 -- f) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.1 -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.1 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.1 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.1 - -#### A.3.1.12 DL F1-U packet loss rate - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 - -###### O-RAN addition: - -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 - -###### O-RAN addition: - -The numbers are accumulated in the granularity period T. - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 -- f) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 - -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 - -#### A.3.1.13 UL PDCP SDU Data Volume - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.2 - -###### O-RAN addition: - -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.2 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.2 - -###### O-RAN addition: - -NOTE: excludes UL PDCP SDU received as data forwarding. - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.2 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.2 - -###### O-RAN addition: - -The measurement name has the form OR.QosFlow.UIPdcpSduDataVol or optionally OR.QosFlow.UIPdcpSduDataVol\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDCP.UIPdcpSduDataVol or optionally OR.PDCP.UIPdcpSduDataVol\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. - -- f) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.2 -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.2 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.2 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.2 - -#### A.3.1.14 UL PDCP SDU Data Volume on X2 Interface - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 - -###### O-RAN addition: - -The measurement is for X2 interface. - -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 - -###### O-RAN addition: - -The measurement is for X2 interface. - -NOTE: excludes UL PDCP SDU received as data forwarding. - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 - -###### O-RAN addition: - -The measurement name has the form OR.DRB.UIPdcpSduDataVolX2 or optionally OR.DRB.UIPdcpSduDataVolX2 *Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDCP.UIPdcpSduDataVolX2 or optionally OR.PDCP.UIPdcpSduDataVolX2 *Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. - -- f) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 - -#### A.3.1.15 UL PDCP SDU Data Volume on Xn Interface - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 - -###### O-RAN addition: - -The measurement is for Xn interface. - -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI.. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 - -###### O-RAN addition: - -The measurement is for Xn interface. - -NOTE: excludes UL PDCP SDU received as data forwarding. - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 - -###### O-RAN addition: - -The measurement name has the form OR.DRB.UIPdcpSduDataVolXn or optionally - -OR.DRB.UIPdcpSduDataVolXn *Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), - -OR.PDCP.UIPdcpSduDataVolXn or optionally OR.PDCP.UIPdcpSduDataVolXn *Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. - -- f) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.4 - -#### A.3.1.16 DL PDCP SDU Data Volume - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.1 - -###### O-RAN addition: - -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.1 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.1 - -###### O-RAN addition: - -NOTE: excludes DL PDCP SDU transmitted as data forwarding. - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.1 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.1 - -###### O-RAN addition: - -The measurement name has the form OR.QosFlow.DIPdcpSduDataVol or optionally - -OR.QosFlow.DIPdcpSduDataVol\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), - -OR.PDCP.DIPdcpSduDataVol or optionally OR.PDCP.DIPdcpSduDataVol\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. - -- f) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.1 -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.1 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.1 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.1 - -#### A.3.1.17 DL PDCP SDU Data Volume on X2 Interface - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 - -###### O-RAN addition: - -The measurement is for X2 interface. - -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 - -###### O-RAN addition: - -The measurement is for X2 interface. - -NOTE: excludes DL PDCP SDU transmitted as data forwarding. - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 - -###### O-RAN addition: - -The measurement name has the form OR.DRB.DIPdcpSduDataVolX2 or optionally - -OR.DRB.DIPdcpSduDataVolX2\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), - -OR.PDCP.DIPdcpSduDataVolX2 or optionally OR.PDCP.DIPdcpSduDataVolX2\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. - -- f) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 - -#### A.3.1.18 DL PDCP SDU Data Volume on Xn Interface - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 - -###### O-RAN addition: - -The measurement is for Xn interface. - -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 - -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 - -###### O-RAN addition: - -The measurement is for Xn interface. - -NOTE: excludes DL PDCP SDU transmitted as data forwarding. - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 - -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 - -###### O-RAN addition: - -The measurement name has the form OR.DRB.DIPdcpSduDataVolXn or optionally - -OR.DRB.DIPdcpSduDataVolXn\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), - -OR.PDCP.DIPdcpSduDataVolXn or optionally OR.PDCP.DIPdcpSduDataVolXn\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. - -- f) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 - -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 - -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 - -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.3.6.2.3 - -#### A.3.1.19 UL PDCP SDU Data Volume per cell - -- a) This counter provides the UL PDCP SDU volume received via X2, Xn or F1. - -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. - -- b) CC - -- c) The measurement is incremented by the volume of UL PDCP SDU whenever the UL PDCP PDU is received via X2-U, Xn-U or F1-U UL GTP-u tunnel, and optionally when the UL PDCP SDU is mapped to the filter. - -NOTE: excludes UL PDCP SDU received as data forwarding. - -- d) Each measurement is an integer value representing the UL PDCP SDU volume received via X2, Xn or F1 in Mbit. - -- e) The measurement name has the form OR.DRB.UIPdcpSduDataVolCell or optionally - -OR.DRB.UIPdcpSduDataVolCell\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), - -OR.PDCP.UIPdcpSduDataVolCell or optionally OR.PDCP.UIPdcpSduDataVolCell\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. - -- f) NRCellCU - -- g) Packet Switched - -- h) 5GS - -- i) Network Operator's Traffic Engineering Community - -#### A.3.1.20 UL PDCP SDU Data Volume on X2 Interface per cell - -- a) This counter provides the UL PDCP SDU volume received via X2. -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement is incremented by the volume of UL PDCP SDU whenever the UL PDCP PDU is received via X2-U UL GTP-u tunnel, and optionally when the UL PDCP SDU is mapped to the filter. - -NOTE: excludes UL PDCP SDU received as data forwarding. - -- d) Each measurement is an integer value representing the UL PDCP SDU volume received via X2 in Mbit. -- e) The measurement name has the form OR.DRB.UIPdcpSduDataVolX2Cell or optionally OR.DRB.UIPdcpSduDataVolX2Cell\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDCP.UIPdcpSduDataVolX2Cell or optionally OR.PDCP.UIPdcpSduDataVolX2Cell\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.1.21 UL PDCP SDU Data Volume on Xn Interface per cell - -- a) This counter provides the UL PDCP SDU volume received via Xn. -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement is incremented by the volume of UL PDCP SDU whenever the UL PDCP PDU is received via Xn-U UL GTP-u tunnel, and optionally when the UL PDCP SDU is mapped to the filter. - -NOTE: excludes UL PDCP SDU received as data forwarding. - -- d) Each measurement is an integer value representing the UL PDCP SDU volume received via Xn in Mbit. -- e) The measurement name has the form OR.DRB.UIPdcpSduDataVolXnCell or optionally OR.DRB.UIPdcpSduDataVolXnCell\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDCP.UIPdcpSduDataVolXnCell or optionally OR.PDCP.UIPdcpSduDataVolXnCell\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.1.22 DL PDCP SDU Data Volume per cell - -- a) This counter provides the DL PDCP SDU volume transmitted via X2, Xn or F1. -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement is incremented by the volume of DL PDCP SDU whenever the DL PDCP PDU is transmitted via X2-U, Xn-U or F1-U DL GTP-u tunnel, and optionally when the DL PDCP SDU is mapped to the filter. -NOTE: excludes DL PDCP SDU transmitted as data forwarding. -- d) Each measurement is an integer value representing the DL PDCP SDU volume transmitted via X2, Xn or F1 in Mbit. -- e) The measurement name has the form OR.DRB.DIPdcpSduDataVolCell or optionally OR.DRB.DIPdcpSduDataVolCell\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDCP.DIPdcpSduDataVolCell or optionally OR.PDCP.DIPdcpSduDataVolCell\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.1.23 DL PDCP SDU Data Volume on X2 Interface per cell - -- a) This counter provides the DL PDCP SDU volume transmitted via X2. -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement is incremented by the volume of DL PDCP SDU whenever the DL PDCP PDU is transmitted via X2-U DL GTP-u tunnel, and optionally when the DL PDCP SDU is mapped to the filter. -NOTE: excludes DL PDCP SDU transmitted as data forwarding. -- d) Each measurement is an integer value representing the DL PDCP SDU volume transmitted via X2 in Mbit. -- e) The measurement name has the form OR.DRB.DIPdcpSduDataVolX2Cell or optionally OR.DRB.DIPdcpSduDataVolX2Cell\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDCP.DIPdcpSduDataVolX2Cell or optionally OR.PDCP.DIPdcpSduDataVolX2Cell\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.1.24 DL PDCP SDU Data Volume on Xn Interface per cell - -- a) This counter provides the DL PDCP SDU volume transmitted via Xn. -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement is incremented by the volume of DL PDCP SDU whenever the DL PDCP PDU is transmitted via Xn-U DL GTP-u tunnel, and optionally when the DL PDCP SDU is mapped to the filter. - -NOTE: excludes DL PDCP SDU transmitted as data forwarding. - -- d) Each measurement is an integer value representing the DL PDCP SDU volume transmitted via Xn in Mbit. -- e) The measurement name has the form OR.DRB.DIPdcpSduDataVolXnCell or optionally OR.DRB.DIPdcpSduDataVolXnCell\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.PDCP.DIPdcpSduDataVolXnCell or optionally OR.PDCP.DIPdcpSduDataVolXnCell\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. -- f) NRCellCU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.2 Void - -### A.3.3 NR S1-U Interface Performance Measurements - -#### A.3.3.1 UL PDCP SDU volume transmitted via S1-U UL GTP-U tunnel - -- a) This counter provides the UL PDCP SDU volume transmitted via S1-U UL GTP-U tunnel -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement is incremented by the volume of UL PDCP SDU whenever the UL PDCP SDU is transmitted via S1-U UL GTP-u tunnel, and optionally when the UL PDCP SDU is mapped to the filter. S1 interface is defined in 3GPP TS 36.413 [i.3], clause 8. -- d) Each measurement is an integer value representing the UL PDCP SDU volume transmitted via S1-U UL GTP-U tunnel in kilobits. -- e) The measurement name has the form OR.GTP.UIPdcpSduVolTxS1UUI or optionally OR.GTP.UIPdcpSduVolTxS1UUI\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.S1.UIPdcpSduVolTxS1UUI or optionally OR.S1.UIPdcpSduVolTxS1UUI\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.3.2 DL PDCP SDU volume received via S1-U DL GTP-U tunnel - -- a) This counter provides the DL PDCP SDU volume received via S1-U DL GTP-U tunnel. -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement is incremented by the volume of DL PDCP SDU whenever the DL PDCP SDU is received via S1-U DL GTP-u tunnel, and optionally when the DL PDCP SDU is mapped to the filter. S1 interface is defined in 3GPP TS 36.413 [i.3], clause 8. -- d) Each measurement is an integer value representing the DL PDCP SDU volume received via S1-U DL GTP-U tunnel in kilobits. -- e) The measurement name has the form OR.GTP.DIPdcpSduVolRxS1UDI or optionally OR.GTP.DIPdcpSduVolRxS1UDI\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.S1.DIPdcpSduVolRxS1UDI or optionally OR.S1.DIPdcpSduVolRxS1UDI\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.3.3 UL PDCP SDUs transmitted via S1-U UL GTP-U tunnel - -- a) This counter provides the number of the UL PDCP SDUs transmitted via S1-U UL GTP-U tunnel. -The counter is split into subcounters per GTP Path. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement is incremented by 1 whenever the UL PDCP SDU is transmitted via S1 U UL GTP-u tunnel. -Optionally, the GTP Path filter is calculated, where the number of measurements is accumulated per the number of supported GTP Path, and additionally per filter. -- d) Each measurement is an integer value representing the number of the UL PDCP SDUs transmitted via S1-U UL GTP-U tunnel. -- e) The measurement name has the form OR.GTP.UIPdcpPduTxS1UUL.GTPPath or OR.GTP.UIPdcpPduTxS1UUL.GTPPath\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.S1.UIPdcpPduTxS1UUL.GTPPath or OR.S1.UIPdcpPduTxS1UUL.GTPPath\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *GTPPath* is GTP Path and where *Filter* is a combination of QoS level and S-NSSAI. Where QoS represents the mapped 5QI or QCI level and SNSSAI represents S-NSSAI. -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.3.4 DL PDCP SDUs transmitted via S1-U DL GTP-U tunnel - -- a) This counter provides the number of the DL PDCP SDUs transmitted via S1-U DL GTP-U tunnel. -The counter is split into subcounters per GTP Path. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement is incremented by 1 whenever the DL PDCP SDU is transmitted via S1 U DL GTP-u tunnel. -Optionally the GTP Path filter is calculated, where the number of measurements is accumulated per the number of supported GTP Path per filter. -- d) Each measurement is an integer value representing the number of the DL PDCP SDUs transmitted via S1-U DL GTP-U tunnel. -- e) The measurement name has the form OR.GTP.DIPdcpPduTxS1UDL.GTPPath or OR.GTP.DIPdcpPduTxS1UDL.GTPPath\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.S1.DIPdcpPduTxS1UDL.GTPPath or OR.S1.DIPdcpPduTxS1UDL.GTPPath\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *GTPPath* is GTP Path and where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level and SNSSAI represents S-NSSAI. -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.3.4 NR NG-U Interface Performance Measurements - -#### A.3.4.1 UL PDCP SDU volume transmitted via NG-U UL GTP-U tunnel - -- a) This counter provides the UL PDCP SDU volume transmitted via NG-U UL GTP-U tunnel. -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement is incremented by the volume of UL PDCP SDU whenever the UL PDCP SDU is transmitted via NG-U UL GTP-u tunnel, and optionally when the UL PDCP SDU is mapped to the filter. NG-U interface is defined in 3GPP TS 38.413 [i.5], clause 8. -- d) Each measurement is an integer value representing the UL PDCP SDU volume transmitted via NG-U UL GTP-U tunnel in kilobits. -- e) The measurement name has the form OR.GTP.UIPdcpSduVolTxNGUUL or optionally OR.GTP.UIPdcpSduVolTxNGUUL\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.NG.UIPdcpSduVolTxNGUUL or optionally OR.NG.UIPdcpSduVolTxNGUUL\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, and SNSSAI represents S-NSSAI. -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS - -- i) Network Operator's Traffic Engineering Community - -#### A.3.4.2 DL PDCP SDU volume received via NG-U DL GTP-U tunnel - -- a) This counter provides the DL PDCP SDU volume received via NG-U DL GTP-U tunnel. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement is incremented by the volume of DL PDCP SDU whenever the DL PDCP SDU is received via NG-U DL GTP-u tunnel, and optionally when the DL PDCP SDU is mapped to the filter. NG-U interface is defined in 3GPP TS 38.413 [i.5], clause 8. -- d) Each measurement is an integer value representing the DL PDCP SDU volume received via NG-U DL GTP-U tunnel in kilobits. -- e) The measurement name has the form OR.GTP.DIPdcpSduVolRxNGUDl or optionally OR.GTP.DIPdcpSduVolRxNGUDl\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.NG.DIPdcpSduVolRxNGUDl or optionally OR.NG.DIPdcpSduVolRxNGUDl\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.3.5 NR X2-U Interface performance measurements (O-CU) - -#### A.3.5.1 UL PDCP SDU volume received via X2-U UL GTP-U tunnel (X2-U UL data forwarding) - -- a) This counter provides the UL PDCP SDU volume received via X2-U UL GTP-U tunnel for data forwarding. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement is incremented by the volume of UL PDCP SDU whenever the UL PDCP PDU is received via X2-U UL GTP-u tunnel for data forwarding, and optionally when the UL PDCP SDU is mapped to the filter. X2 interface is defined in 3GPP TS 36.423 [i.4], clause 8. -- d) Each measurement is an integer value representing the UL PDCP SDU volume received via X2-U UL GTP-U tunnel for data forwarding in kilobits. -- e) The measurement name has the form OR.GTP.UIPdcpSduVolRxX2UUIDataForward or optionally OR.GTP.UIPdcpSduVolRxX2UUIDataForward\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.X2.UIPdcpSduVolRxX2UUIDataForward or optionally OR.X2.UIPdcpSduVolRxX2UUIDataForward\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and S-NSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. -- f) GNBCUUPFunction -- g) Packet Switched - -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.5.2 DL PDCP SDU volume received via X2-U DL GTP-U tunnel (X2-U DL data forwarding) - -- a) This counter provides the DL PDCP SDU volume received via X2-U DL GTP-U tunnel for data forwarding. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement is incremented by the volume of DL PDCP SDU whenever the DL PDCP PDU is transmitted via X2-U DL GTP-u tunnel for data forwarding, and optionally when the DL PDCP SDU is mapped to the filter. X2 interface is defined in 3GPP TS 36.423 [i.4], clause 8. -- d) Each measurement is an integer value representing the DL PDCP SDU volume received via X2-U DL GTP-U tunnel for data forwarding in kilobits. -- e) The measurement name has the form OR.GTP.DIPdcpSduVolRrX2UDIDataForward or optionally OR.GTP.DIPdcpSduVolRrX2UDIDataForward\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.X2.DIPdcpSduVolRrX2UDIDataForward or optionally OR.X2.DIPdcpSduVolRrX2UDIDataForward\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level and SNSSAI represents S-NSSAI. -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.3.6 NR Xn-U Interface performance measurements (O-CU) - -#### A.3.6.1 UL PDCP SDU volume received via Xn-U UL GTP-U tunnel (Xn-U UL data forwarding) - -- a) This counter provides the UL PDCP SDU volume received via Xn-U UL GTP-U tunnel for data forwarding. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement is incremented by the volume of UL PDCP SDU whenever the UL PDCP PDU is received via Xn-U UL GTP-u tunnel for data forwarding, and optionally when the UL PDCP SDU is mapped to the filter. Xn interface is defined in 3GPP TS 36.423 [i.4], clause 8. -- d) Each measurement is an integer value representing the UL PDCP SDU volume received via Xn-U UL GTP-U tunnel for data forwarding in kilobits. -- e) The measurement name has the form OR.GTP.UIPdcpSduVolRrXnUUIDataForward or optionally OR.GTP.UIPdcpSduVolRrXnUUIDataForward\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.Xn.UIPdcpSduVolRrXnUUIDataForward or optionally OR.Xn.UIPdcpSduVolRrXnUUIDataForward\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is - -a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level and SNSSAI represents S-NSSAI. - -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.3.6.2 DL PDCP SDU volume received via Xn-U DL GTP-U tunnel (Xn-U DL data forwarding) - -- a) This counter provides the DL PDCP SDU volume received via Xn-U DL GTP-U tunnel for data forwarding. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. -- b) CC -- c) The measurement is incremented by the volume of DL PDCP SDU whenever the DL PDCP PDU is transmitted via Xn-U DL GTP-u tunnel for data forwarding, and optionally when the DL PDCP SDU is mapped to the filter. Xn interface is defined in 3GPP TS 36.423 [i.4], clause 8. -- d) Each measurement is an integer value representing the DL PDCP SDU volume received via Xn-U DL GTP-U tunnel for data forwarding in kilobits. -- e) The measurement name has the form OR.GTP.DIPdcpSduVolTxXnUDIDataForward or optionally OR.GTP.DIPdcpSduVolTxXnUDIDataForward\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.Xn.DIPdcpSduVolTxXnUDIDataForward or optionally OR.Xn.DIPdcpSduVolTxXnUDIDataForward\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. -- f) GNBCUUPFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -## A.4 O-DU Performance measurements - -### A.4.1 NR F1 Interface performance measurements - -#### A.4.1.1 UL PDCP PDUs transmitted via F1-U UL GTP-U tunnel - -- a) This counter provides the number of the UL PDCP PDUs transmitted via F1-U UL GTP-U tunnel. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). -It is optional counter for O-DU. -- b) CC -- c) The measurement is incremented by 1 whenever the UL PDCP PDU is transmitted via F1 U UL GTP-u tunnel, and optionally when the QCI or the 5QI of the UL PDCP PDU is the filter. - -- d) Each measurement is an integer value representing the number of the UL PDCP PDUs transmitted via F1-U UL GTP-U tunnel. -- e) The measurement name has the form OR.GTP.UIPdcPduTxF1UUI or OR.GTP.UIPdcPduTxF1UUI\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.F1.UIPdcPduTxF1UUI or OR.F1.UIPdcPduTxF1UUI\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is the QoS level and represents the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.1.2 UL PDCP PDU volume transmitted via F1-U UL GTP-U tunnel - -- a) This counter provides the UL PDCP PDU volume transmitted via F1-U UL GTP-U tunnel. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -NOTE: Measurement Object Class, gNBDUFunction, is different to A.4.1.14. - -It is optional counter for O-DU. - -- b) CC -- c) The measurement is accumulated by the volume of UL PDCP PDU whenever the UL PDCP PDU is transmitted via F1 U UL GTP-u tunnel, and optionally when the QCI or the 5QI of the UL PDCP PDU is the filter. F1 interface is defined in 3GPP TS 38.473 [i.6], clause 8. -- d) Each measurement is an integer value representing the UL PDCP PDU volume transmitted via F1-U UL GTP-U tunnel in kilobits. -- e) The measurement name has the form OR.GTP.UIPdcPduVolTxF1UUI or OR.GTP.UIPdcPduVolTxF1UUI\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.F1.UIPdcPduVolTxF1UUI or OR.F1.UIPdcPduVolTxF1UUI\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is the QoS level and represents the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.1.3 Maximum UL PDCP PDU volume transmitted via F1-U UL GTP-U tunnel - -- a) This counter provides the maximum UL PDCP PDU volume transmitted via F1-U UL GTP-U tunnel. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is optional counter for O-DU. - -- b) SI -- c) The measurement is obtained by reporting the maximum observed value of the UL PDCP PDU volume transmitted via F1-U UL GTP-U tunnel during the granularity period. - -F1 interface is defined in 3GPP TS 38.473 [i.6], clause 8. - -- d) Each measurement is an integer value representing the maximum UL PDCP PDU volume transmitted via F1-U UL GTP-U tunnel in kilobits. -- e) The measurement name has the form OR.GTP.MaxUIPdcPduVolTxF1UUI or OR.GTP.MaxUIPdcPduVolTxF1UUI\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.F1.MaxUIPdcPduVolTxF1UUI or OR.F1.MaxUIPdcPduVolTxF1UUI\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is the QoS level and represents the mapped 5QI or QCI level. -- f) gNBDFFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.1.4 Minimum UL PDCP PDU volume transmitted via F1-U UL GTP-U tunnel - -- a) This counter provides the minimum UL PDCP PDU volume transmitted via F1-U UL GTP-U tunnel. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is optional counter for O-DU. - -- b) SI -- c) The measurement is obtained by reporting the minimum observed value of the UL PDCP PDU volume transmitted via F1-U UL GTP-U tunnel during the granularity period - -F1 interface is defined in 3GPP TS 38.473 [i.6], clause 8. - -- d) Each measurement is an integer value representing the minimum UL PDCP PDU volume transmitted via F1-U UL GTP-U tunnel in kilobits. -- e) The measurement name has the form OR.GTP.MinUIPdcPduVolTxF1U or OR.GTP.MinUIPdcPduVolTxF1U\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.F1.MinUIPdcPduVolTxF1U or OR.F1.MinUIPdcPduVolTxF1U\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is the QoS level and represents the mapped 5QI or QCI level. -- f) gNBDFFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.1.5 DL PDCP PDUs received via F1-U DL GTP-U tunnel - -- a) This counter provides the number of the DL PDCP PDUs received via F1-U DL GTP-U tunnel. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is optional counter for O-DU. - -- b) CC -- c) The measurement is incremented by 1 whenever the DL PDCP PDU is received via F1 U DL GTP-u tunnel, optionally when the QCI or the 5QI of the DL PDCP PDU is the filter. - -- d) Each measurement is an integer value representing the number of the DL PDCP PDUs received via F1-U DL GTP-U tunnel. -- e) The measurement name has the form OR.GTP.DIPdcpPduRxF1UDl or OR.GTP.DIPdcpPduRxF1UDl\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.F1.DIPdcpPduRxF1UDl or OR.OR.F1.DIPdcpPduRxF1UDl\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is the QoS level and represents the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.1.6 DL PDCP PDU volume received via F1-U DL GTP-U tunnel - -- a) This counter provides the DL PDCP PDU volume received via F1-U DL GTP-U tunnel. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -NOTE: Measurement Object Class, gNBDUFunction, is different to A.4.1.15. - -It is optional counter for O-DU. - -- b) CC -- c) The measurement is accumulated by the volume of DL PDCP PDU whenever the DL PDCP PDU is received via F1 U DL GTP-u tunnel, optionally when the QCI or the 5QI of the DL PDCP PDU is the filter. F1 interface is defined in 3GPP TS 38.473 [i.6], clause 8. -- d) Each measurement is an integer value representing the DL PDCP PDU volume received via F1-U DL GTP-U tunnel in kilobits. -- e) The measurement name has the form OR.GTP.DIPdcpPduVolRxF1UDl or OR.GTP.DIPdcpPduVolRxF1UDl\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.F1.DIPdcpPduVolRxF1UDl or OR.F1.DIPdcpPduVolRxF1UDl\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is the QoS level and represents the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.1.7 Maximum DL PDCP PDU volume received via F1-U DL GTP-U tunnel - -- a) This counter provides the maximum DL PDCP PDU volume received via F1-U DL GTP-U tunnel. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is optional counter for O-DU. - -- b) SI -- c) The measurement is obtained by reporting the maximum observed value of the DL PDCP PDU volume transmitted via F1-U UL GTP-U tunnel during the granularity period. - -F1 interface is defined in 3GPP TS 38.473 [i.6], clause 8. - -- d) Each measurement is an integer value representing the maximum DL PDCP PDU volume received via F1-U DL GTP-U tunnel in kilobits. -- e) The measurement name has the form OR.GTP.MaxDIPdcpPduVolRxF1UDl or OR.GTP.MaxDIPdcpPduVolRxF1UDl\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.F1.MaxDIPdcpPduVolRxF1UDl or OR.F1.MaxDIPdcpPduVolRxF1UDl\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is the QoS level and represents the mapped 5QI or QCI level. -- f) gNBDFUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.1.8 Minimum DL PDCP PDU volume received via F1-U DL GTP-U tunnel - -- a) This counter provides the minimum DL PDCP PDU volume received via F1-U DL GTP-U tunnel. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is optional counter for O-DU. - -- b) SI -- c) The measurement is obtained by reporting the minimum observed value of the DL PDCP PDU volume received via F1-U DL GTP-U tunnel during the granularity period. - -F1 interface is defined in 3GPP TS 38.473 [i.6], clause 8. - -- d) Each measurement is an integer value representing the minimum DL PDCP PDU volume received via F1-U DL GTP-U tunnel in kilobits. -- e) The measurement name has the form OR.GTP.MinDIPdcpPduVolRxF1UDl or OR.GTP.MinDIPdcpPduVolRxF1UDl\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.F1.MinDIPdcpPduVolRxF1UDl or OR.F1.MinDIPdcpPduVolRxF1UDl\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is the QoS level and represents the mapped 5QI or QCI level. -- f) gNBDFUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.1.9 Transmitted F1-C messages - -- a) This counter provides the number of the transmitted F1-C messages per signal type that is non UE-associated or UE-associated signaling. - -It is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever the F1 C-plane message is transmitted per the signal type of the F1 C-plane message: non UE-associated or UE-associated as subcounter.*Sigtype*. - -- d) Each measurement is an integer value representing the number of the transmitted F1-C messages per signal type that is non UE-associated or UE-associated signaling. -- e) OR.L3M.TxF1CMes.*Sigtype* (default), OR.F1.TxF1CMes.*Sigtype* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where - - Sigtype* is the signal type: - - 0: non UE-associated - - 1: UE-associated -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.1.10 Received F1-C messages - -- a) This counter provides the number of the received F1-C SCTP messages per signal type that is non UE-associated or UE-associated signaling. - - It is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever the F1 C-plane message is received per the signal type of the F1 C-plane message: non UE-associated or UE-associated as subcounter.*Sigtype*. -- d) Each measurement is an integer value representing the number of the received F1-C SCTP messages per signal type that is non UE-associated or UE-associated signaling. -- e) OR.L3M.RxF1CMes.*Sigtype* (default), OR.F1.RxF1CMes.*Sigtype* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where - - Sigtype* is the signal type: - - 0: non UE-associated - - 1: UE-associated -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.1.11 DL F1-U packets discarded due to NR U-Plane protocol error - -- a) This counter provides the number of the DL F1-U packets discarded due to NR U-Plane protocol error. - - It is recommended to support for O-DU. -- b) CC -- c) The measurement counter is incremented by 1 whenever the DL F1-U plane packet is discarded due to NR U-plane protocol error. - -- d) Each measurement is an integer value representing the number of the DL F1-U packets discarded due to NR U-Plane protocol error. -- e) OR.DRB.DIF1UDiscardNRUProtocolError (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.F1.DIF1UDiscardNRUProtocolError (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.1.12 DL F1-U packet loss rate - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 - -###### O-RAN addition: - -It is optional counter for O-DU. - -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 - -###### O-RAN addition: - -The measurement name has the form OR.DRB.F1UPacketLossRateDI or OR.DRB.F1UPacketLossRateDI\_Filter. Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. - -- f) O-RAN Measurement Object Class: -gNBDUFunction -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.3.1.3 - -#### A.4.1.13 DL Packet Drop Rate in gNB-DU - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.2 - -###### O-RAN addition: - -It is optional counter for O-DU. - -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.2 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.2 -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.2 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.2 - -###### O-RAN addition: - -The measurement name has the form OR.DRB.RlcPacketDropRateDl or OR.DRB.RlcPacketDropRateDl\_Filter. Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. - -- f) gNBDUFunction -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.2 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.2 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.3.2.2 - -#### A.4.1.14 UL PDCP PDU volume transmitted via F1-U UL GTP-U tunnel - -- a) This counter provides the UL PDCP PDU volume of the cell transmitted via F1-U UL GTP-U tunnel. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. - -NOTE: Measurement Object Class, NRCellIDU, is different to A.4.1.2. - -It is optional counter for O-DU. - -- b) CC -- c) The measurement counter is accumulated by the volume of UL PDCP PDU whenever the UL PDCP PDU is transmitted from the Cell via F1 U UL GTP-u tunnel. F1 interface is defined in 3GPP TS 38.473 [i.6], clause 8. -- d) Each measurement is an integer value representing the UL PDCP PDU volume of the cell transmitted via F1-U UL GTP-U tunnel in kilobits. -- e) The measurement name has the form OR.GTP.UIPdcPduCellVOITxF1UUI or OR.GTP.UIPdcPduCellVOITxF1UUI\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.F1.UIPdcPduCellVOITxF1UUI or OR.F1.UIPdcPduCellVOITxF1UUI\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.1.15 DL PDCP PDU volume received via F1-U DL GTP-U tunnel - -- a) This counter provides the DL PDCP PDU volume of the cell received via F1-U DL GTP-U tunnel. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. - -NOTE: Measurement Object Class, NRCellIDU, is different to A.4.1.6. - -It is optional counter for O-DU. - -- b) CC -- c) The measurement counter is accumulated by the volume of DL PDCP PDU whenever the DL PDCP PDU is received to the Cell via F1 U DL GTP-u tunnel. F1 interface is defined in 3GPP TS 38.473 [i.6], clause 8. - -- d) Each measurement is an integer value representing the DL PDCP PDU volume of the cell received via F1-U DL GTP-U tunnel in kilobits. -- e) The measurement name has the form OR.GTP.DIPdcpPduCellVolTxFIUDl or OR.GTP.DIPdcpPduCellVolTxFIUDl\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.F1.DIPdcpPduCellVolTxFIUDl or OR.F1.DIPdcpPduCellVolTxFIUDl\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, SNSSAI represents S-NSSAI. -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.4.2 NR RLC performance measurements - -#### A.4.2.1 Received UL RLC PDUs - -- a) This counter provides the number of the received UL RLC PDUs. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). -It is optional counter for O-DU. -- b) CC -- c) The measurement is incremented by 1 whenever the UL RLC PDU is received, optionally when the QCI or the 5QI of the UL RLC PDU is the filter. -- d) Each measurement is an integer value representing the number of the received UL RLC PDUs. -- e) The measurement name has the form OR.DRB.RxUIRlcPdu or OR.DRB.RxUIRlcPdu\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.RxUIRlcPdu or OR.RLC.RxUIRlcPdu\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.2 Received UL RLC PDU volume - -- a) This counter provides the received UL RLC PDU volume. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). -It is recommended to support for O-DU. -- b) SI -- c) The measurement is incremented by the volume of the UL RLC PDU whenever the UL RLC PDU is received, optionally when the QCI or the 5QI of the UL RLC PDU is the filter. -- d) Each measurement is an integer value representing the received UL RLC PDU volume in kilobits. - -- e) The measurement name has the form OR.DRB.RxUIRlcPduVol or OR.DRB.RxUIRlcPduVol *Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.RxUIRlcPduVol or OR.RLC.RxUIRlcPduVol *Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.3 Request for UL RLC PDUs retransmission - -- a) This counter provides the number of the requests sent for UL RLC PDUs retransmission. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is optional counter for O-DU. - -- b) CC -- c) The measurement is incremented by 1 whenever the UL RLC PDU retransmission request is sent, optionally when the QCI or the 5QI of the UL RLC PDU is the filter. -- d) Each measurement is an integer value representing the number of the requests sent for UL RLC PDUs retransmission. -- e) The measurement name has the form OR.DRB.ReqUIRlcPduRetrans or OR.DRB.ReqUIRlcPduRetrans *Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.ReqUIRlcPduRetrans or OR.RLC.ReqUIRlcPduRetrans *Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.4 Transmitted DL RLC PDUs - -- a) This counter provides the number of the transmitted DL RLC PDUs. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is optional counter for O-DU. - -- b) CC -- c) The measurement subcounter is incremented by 1 whenever the DL RLC PDU is transmitted, optionally when the QCI or the 5QI of the DL RLC PDU is the filter. -- d) Each measurement is an integer value representing the number of the transmitted DL RLC PDUs. -- e) The measurement name has the form OR.DRB.TxDIRlcPdu or OR.DRB.TxDIRlcPdu *Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.TxDIRlcPdu or OR.RLC.TxDIRlcPdu *Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDUFunction - -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.5 Transmitted DL RLC PDU volume - -- a) This counter provides the transmitted DL RLC PDU volume. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is recommended to support for O-DU. - -- b) SI -- c) The measurement is incremented by the volume of the DL RLC PDU whenever the DL RLC PDU is transmitted, optionally when the QCI or the 5QI of the DL RLC PDU is the filter. -- d) Each measurement is an integer value representing the transmitted DL RLC PDU volume in kilobits. -- e) The measurement name has the form OR.DRB.TxDIRlcPduVol or OR.DRB.TxDIRlcPduVol\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.TxDIRlcPduVol or OR.RLC.TxDIRlcPduVol\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.6 Retransmitted DL RLC PDUs - -- a) This counter provides the number of the DL RLC PDUs retransmitted in RLC layer. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is optional counter for O-DU. - -- b) CC -- c) The measurement is incremented by 1 whenever the DL RLC PDU is retransmitted in RLC layer, optionally when the QCI or the 5QI of the DL RLC PDU is the filter. -- d) Each measurement is an integer value representing the number of the DL RLC PDUs retransmitted in RLC layer. -- e) The measurement name has the form OR.DRB.RetransDIRlcPdu or OR.DRB.RetransDIRlcPdu\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.RetransDIRlcPdu or OR.RLC.RetransDIRlcPdu\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.7 Retransmitted DL RLC PDU volume - -- a) This counter provides the DL RLC PDU volume retransmitted in RLC layer. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is recommended to support for O-DU. - -- b) SI -- c) The measurement is incremented by the volume of the DL RLC PDU whenever the DL RLC PDU is retransmitted in RLC layer, optionally when the QCI or the 5QI of the DL RLC PDU is the filter. -- d) Each measurement is an integer value representing the DL RLC PDU volume retransmitted in RLC layer in kilobits. -- e) The measurement name has the form OR.DRB.RetransDIRlcPduVol or OR.DRB.RetransDIRlcPduVol\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.RetransDIRlcPduVol or OR.RLC.RetransDIRlcPduVol\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDFUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.8 UL RLC PDUs discarded due to bearer release - -- a) This counter provides the number of the UL RLC PDUs discarded due to bearer release. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is optional counter for O-DU. - -- b) CC -- c) The measurement is incremented by 1 whenever the UL RLC PDU is discarded due to bearer release, optionally when the QCI or the 5QI of the UL RLC PDU is the filter. -- d) Each measurement is an integer value representing the number of the UL RLC PDUs discarded due to bearer release. -- e) The measurement name has the form OR.DRB.UIRlcPduDiscardBearerRel or OR.DRB.UIRlcPduDiscardBearerRel\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.UIRlcPduDiscardBearerRel or OR.RLC.UIRlcPduDiscardBearerRel\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDFUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.9 UL RLC PDU volume discarded due to bearer release - -- a) This counter provides the UL RLC PDU volume discarded due to bearer release. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). -It is recommended to support for O-DU. -- b) SI -- c) The measurement is incremented by the volume of the UL RLC PDU whenever the UL RLC PDU is discarded due to bearer release, optionally when the QCI or the 5QI of the UL RLC PDU is the filter. -- d) Each measurement is an integer value representing the UL RLC PDU volume discarded due to bearer release in kilobits. -- e) The measurement name has the form OR.DRB.UIRlcPduVolDiscardBearerRel or OR.DRB.UIRlcPduVolDiscardBearerRel\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.UIRlcPduVolDiscardBearerRel or OR.RLC.UIRlcPduVolDiscardBearerRel\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.10 UL RLC PDUs discarded due to RLC re-establishment - -- a) This counter provides the number of the UL RLC PDUs discarded due to RLC re-establishment. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). -It is optional counter for O-DU. -- b) CC -- c) The measurement is incremented by 1 whenever the UL RLC PDU is discarded due to RLC re-establishment, optionally when the QCI or the 5QI of the UL RLC PDU is the filter. -- d) Each measurement is an integer value representing the number of the UL RLC PDUs discarded due to RLC re-establishment. -- e) The measurement name has the form OR.DRB.UIRlcPduDiscardRlcReest or OR.DRB.UIRlcPduDiscardRlcReest\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.UIRlcPduDiscardRlcReest or OR.RLC.UIRlcPduDiscardRlcReest\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.11 UL RLC PDU volume discarded due to RLC re-establishment - -- a) This counter provides the UL RLC PDU volume discarded due to RLC re-establishment. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is recommended to support for O-DU. - -- b) SI -- c) The measurement is incremented by the volume of the UL RLC PDU whenever the UL RLC PDU is discarded due to RLC re-establishment, optionally when the QCI or the 5QI of the UL RLC PDU is the filter. -- d) Each measurement is an integer value representing the UL RLC PDU volume discarded due to RLC re-establishment in kilobits. -- e) The measurement name has the form OR.DRB.UIRlcPduVolDiscardRlcReest or OR.DRB.UIRlcPduVolDiscardRlcReest\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.UIRlcPduVolDiscardRlcReest or OR.RLC.UIRlcPduVolDiscardRlcReest\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDFUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.12 UL RLC PDUs discarded due to other causes - -- a) This counter provides the number of the UL RLC PDUs discarded due to other causes. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is optional counter for O-DU. - -- b) CC -- c) The measurement is incremented by 1 whenever the UL RLC PDU is discarded for reason other than bearer release and RLC re-establishment, optionally when the QCI or the 5QI of the UL RLC PDU is the filter. -- d) Each measurement is an integer value representing the number of the UL RLC PDUs discarded due to other causes. -- e) The measurement name has the form OR.DRB.RlcPduDiscardOther or OR.DRB.RlcPduDiscardOther\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.RlcPduDiscardOther or OR.RLC.RlcPduDiscardOther\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDFUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.13 UL RLC PDU volume discarded due to other causes - -- a) This counter provides the UL RLC PDU volume discarded due to other causes. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is recommended to support for O-DU. - -- b) CC - -- c) The measurement is incremented by the volume of the UL RLC PDU whenever the UL RLC PDU is discarded for reason other than bearer release and RLC re-establishment, optionally when the QCI or the 5QI of the UL RLC PDU is the filter. -- d) Each measurement is an integer value representing the UL RLC PDU volume discarded due to other causes in kilobits. -- e) The measurement name has the form OR.DRB.UIRlcPduVolDiscardOther or OR.DRB.UIRlcPduVolDiscardOther\_ *Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.UIRlcPduVolDiscardOther or OR.RLC.UIRlcPduVolDiscardOther\_ *Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDFFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.14 DL RLC PDUs discarded due to bearer release - -- a) This counter provides the number of DL RLC PDUs discarded due to bearer release. This counter includes DL RLC PDUs which has transmitted or not lower layer. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is optional counter for O-DU. - -- b) CC -- c) The measurement is incremented by 1 whenever the DL RLC PDU is discarded due to bearer release, optionally when the QCI or the 5QI of the DL RLC PDU is the filter. -- d) Each measurement is an integer value representing the number of DL RLC PDUs discarded due to bearer release. -- e) The measurement name has the form OR.DRB.DIRlcPduDiscardBearerRel or OR.DRB.DIRlcPduDiscardBearerRel\_ *Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.DIRlcPduDiscardBearerRel or OR.RLC.DIRlcPduDiscardBearerRel\_ *Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDFFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.15 DL RLC PDU volume discarded due to bearer release - -- a) This counter provides the DL RLC PDU volume discarded due to bearer release. This counter includes DL RLC PDUs which has transmitted or not lower layer. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is recommended to support for O-DU. - -- b) SI -- c) The measurement is incremented by the volume of the DL RLC PDU whenever the DL RLC PDU is discarded due to bearer release, optionally when the QCI or the 5QI of the DL RLC PDU is the filter. - -- d) Each measurement is an integer value representing the DL RLC PDU volume discarded due to bearer release in kilobits. -- e) The measurement name has the form OR.DRB.DIRlcPduVolDiscardBearerRel or OR.DRB.DIRlcPduVolDiscardBearerRel\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.DIRlcPduVolDiscardBearerRel or OR.RLC.DIRlcPduVolDiscardBearerRel\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.16 DL RLC PDUs discarded due to RLC re-establishment - -- a) This counter provides the number of the DL RLC PDUs discarded due to RLC re-establishment. This counter includes DL RLC PDUs which has transmitted or not lower layer. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). -It is optional counter for O-DU. -- b) CC -- c) The measurement is incremented by 1 whenever the DL RLC PDU is discarded due to RLC re-establishment, optionally when the QCI or the 5QI of the DL RLC PDU is the filter. -- d) Each measurement is an integer value representing the number of the DL RLC PDUs discarded due to RLC re-establishment. -- e) The measurement name has the form OR.DRB.DIRlcPduDiscardRlcReest or OR.DRB.DIRlcPduDiscardRlcReest\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.DIRlcPduDiscardRlcReest or OR.RLC.DIRlcPduDiscardRlcReest\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.17 DL RLC PDU volume discarded due to RLC re-establishment - -- a) This counter provides the DL RLC PDU volume discarded due to RLC re-establishment. This counter includes DL RLC PDUs which has transmitted or not lower layer. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). -It is recommended to support for O-DU. -- b) SI -- c) The measurement is incremented by the volume of the DL RLC PDU whenever the DL RLC PDU is discarded due to RLC re-establishment, optionally when the QCI or the 5QI of the DL RLC PDU is the filter. -- d) Each measurement is an integer value representing the DL RLC PDU volume discarded due to RLC re-establishment in kilobits. - -- e) The measurement name has the form OR.DRB.DIRlcPduVolDiscardRlcReest or OR.DRB.DIRlcPduVolDiscardRlcReest\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.DIRlcPduVolDiscardRlcReest or OR.RLC.DIRlcPduVolDiscardRlcReest\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level representing the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.18 DL RLC PDUs discarded due to full buffer - -- a) This counter provides the number of the DL RLC PDUs discarded due to full RLC transmission buffer. This counter includes DL RLC PDUs which has not been transmitted to lower layer. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is optional counter for O-DU. - -- b) CC -- c) The measurement is incremented by 1 whenever the DL RLC PDU is discarded due to full RLC transmission buffer, optionally when the QCI or the 5QI of the DL RLC PDU is the filter. -- d) Each measurement is an integer value representing the number of the DL RLC PDUs discarded due to full RLC transmission buffer. -- e) The measurement name has the form OR.DRB.DIRlcPduDiscardTxFullBuffer or OR.DRB.DIRlcPduDiscardTxFullBuffer\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.DIRlcPduDiscardTxFullBuffer or OR.RLC.DIRlcPduDiscardTxFullBuffer\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.19 DL RLC PDU volume discarded due to full buffer - -- a) This counter provides the DL RLC PDU volume discarded due to full RLC transmission buffer. This counter includes DL RLC PDUs which has not been transmitted to lower layer. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is recommended to support for O-DU. - -- b) SI -- c) The measurement is incremented by the volume of the DL RLC PDU whenever the DL RLC PDU is discarded due to full RLC transmission buffer, optionally when the QCI or the 5QI of the DL RLC PDU is the filter. -- d) Each measurement is an integer value representing the DL RLC PDU volume discarded due to full RLC transmission buffer in kilobits. - -- e) The measurement name has the form OR.DRB.DIRlcPduVolDiscardTxFullBuffer or OR.DRB.DIRlcPduVolDiscardTxFullBuffer *Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.DIRlcPduVolDiscardTxFullBuffer or OR.RLC.DIRlcPduVolDiscardTxFullBuffer *Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level representing the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.20 The number of exceeding maximum RLC retransmissions - -- a) This counter provides the number of received NACK for the final retransmission in RLC layer. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). -It is recommended to support for O-DU. -- b) CC -- c) The measurement is incremented by 1 whenever RLC status report including NACK for the final retransmission is received, optionally when the QCI or the 5QI of the DL RLC PDU is the filter. -- d) Each measurement is an integer value representing the number of received NACK for the final retransmission in RLC layer. -- e) The measurement name has the form OR.DRB.NumExceedMaxRlcRetrans or OR.DRB.NumExceedMaxRlcRetrans *Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.NumExceedMaxRlcRetrans or OR.RLC.NumExceedMaxRlcRetrans *Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level and represents the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.21 Average delay DL in gNB-DU - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.3.3.3 -O-RAN addition: -The measurement is optionally calculated per S-NSSAI, per QoS level (mapped 5QI or QCI in EN-DC) and PLMN ID, according to 3GPP TS 28.552 [2] clause 5.1.3.3.3. -It is optional counter for O-DU. -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.3.3.3 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.3.3.3 -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.3.3.3 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.3.3.3 -O-RAN addition: - -The measurement name has the form OR.DRB.RlcSduDelayDl or OR.DRB.RlcSduDelayDl *Filter*. Where *Filter* is a combination of PLMN, QoS level and SNSSAI. Where PLMN represents the PLMN ID, QoS represents the mapped 5QI or QCI level, and SNSSAI represents S-NSSAI. - -- f) O-RAN Measurement Object Class: gNBDFuncton -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.3.3.3 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.3.3.3 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.3.3.3 - -#### A.4.2.22 IP Latency DL in gNB-DU - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.3.4.2 - -###### O-RAN addition: - -The measurement is optionally calculated per S-NSSAI, per QoS level (mapped 5QI or QCI in EN-DC) and PLMN ID, according to 3GPP TS 28.552 [2] clause 5.1.3.4.2. - -It is optional counter for O-DU. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.3.4.2 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.3.4.2 -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.3.4.2 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.3.4.2 - -###### O-RAN addition: - -The measurement name has the form OR.DRB.RlcSduLatencyDl or OR.DRB.RlcSduLatencyDl *Filter*. Where *Filter* is a combination of PLMN, QoS level and SNSSAI. Where PLMN represents the PLMN ID, QoS represents the mapped 5QI or QCI level, and SNSSAI represents S-NSSAI. - -- f) O-RAN Measurement Object Class: gNBDFuncton -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.3.4.2 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.3.4.2 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.3.4.2 - -#### A.4.2.23 Void - -#### A.4.2.24 Void - -#### A.4.2.25 DL RLC SDU discarded due to discard timer expiry indication - -- a) This counter provides the number of the DL RLC SDUs discarded due to the discard timer expiry indication from the higher layers. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -It is an optional counter for O-DU. - -- b) CC - -- c) The measurement increases by 1 whenever the DL RLC SDU is discarded due to the expiration of the *discardtimer* indicated by the higher layers, optionally where the QCI or the 5QI of the DL RLC SDU is the filter. -NOTE: The *discardtimer* is configured for only DRBs, as per 3GPP TS 38.323 [6], clause 7.3. -- d) Each measurement is an integer value representing the number of the DL RLC SDUs discarded due to the discard timer expiry indication from the higher layers. -- e) The measurement name has the form OR.DRB.RlcSduDiscardTimerExpiry OR.DRB.RlcSduDiscardTimerExpiry\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.RlcSduDiscardTimerExpiry OR.RLC.RlcSduDiscardTimerExpiry\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level. Where QoS represents the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.26 DL RLC SDU Volume discarded due to discard timer expiry indication - -- a) This counter provides the DL RLC SDU volume discarded due to the discard timer expiry indication from the higher layers. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). -It is recommended to support O-DU. -- b) SI -- c) The measurement increases by the RLC SDU volume in kilobits whenever the DL RLC SDU is discarded due to the expiration of the *discardtimer* indicated by the higher layers, optionally where the QCI or the 5QI of the DL RLC SDU is the filter. -NOTE: The *discardtimer* is configured for only DRBs, as per 3GPP TS 38.323 [6], clause 7.3. -- d) Each measurement is an integer value representing the DL RLC SDU volume discarded due to the discard timer expiry indication from the higher layers in kilobits. -- e) The measurement name has the form OR.DRB.DIRlcSduVolDiscardTimerExpiry or OR.DRB.DIRlcSduVolDiscardTimerExpiry\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.DIRlcSduVolDiscardTimerExpiry or OR.RLC.DIRlcSduVolDiscardTimerExpiry\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level. Where QoS represents the mapped 5QI or QCI level. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.27 Received paging records - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.3 - -###### O-RAN addition: - -The counter is optionally split into subcounter per Paging Identity. - -The counter is optionally split into subcounter per Paging Priority. - -The counter is optionally split into subcounter per Paging Origin. - -It is an optional counter for O-DU. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.3 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.3 - -###### O-RAN addition: - -The subcounter per Paging Identity level is incremented by 1 for each Paging Identity whenever a paging record is received by gNB-DU. - -NOTE 1: Paging Identity is defined in 3GPP TS 38.473 [i.6], clauses 9.3.1.43 and 9.3.1.44. - -The subcounter per Paging Priority level is incremented by 1 for each Paging Priority whenever a paging record including Paging Priority is received by gNB-DU. - -NOTE 2: Paging Priority is defined in 3GPP TS 38.473 [i.6], clause 9.3.1.41. - -The subcounter per Paging Origin level is incremented by 1 for each paging origin whenever a paging record including paging origin is received by gNB-DU. - -NOTE 3: Paging Origin is defined in 3GPP TS 38.473 [i.6], clause 9.3.1.79. - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.3 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.3 - -###### O-RAN addition: - -Subcounter OR.PAG.ReceivedNbr.*PagingIdentity* where *PagingIdentity* is Paging Identity number: -0: RAN UE Paging identity -1: CN UE Paging identity - -Subcounter OR.PAG.ReceivedNbr.*PagingPriority* where *PagingPriority* is Paging Priority number: -0: PrioLevel1 -1: PrioLevel2 -... -7: PrioLevel8 - -Subcounter OR.PAG.ReceivedNbr.*PagingOrigin* where *PagingOrigin* identifies the Paging Origin IE. - -- f) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.3 -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.3 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.3 -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.28 Discarded paging records - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.6 - -###### O-RAN addition: - -The counter is optionally split into subcounter per Paging Identity. - -The counter is optionally split into subcounter per Paging Priority. - -The counter is optionally split into subcounter per Paging Origin. - -It is an optional counter for O-DU. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.6 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.6 - -###### O-RAN addition: - -The subcounter per Paging Identity level is incremented by 1 for each Paging Identity whenever a paging record is discarded at the gNB-DU. - -NOTE 1: Paging Identity is defined in 3GPP TS 38.473 [i.6], clauses 9.3.1.43 and 9.3.1.44. - -The subcounter per Paging Priority level is incremented by 1 for each Paging Priority whenever a paging record including Paging Priority is discarded at the gNB-DU. - -NOTE 2: Paging Priority is defined in 3GPP TS 38.473 [i.6], clause 9.3.1.41. - -The subcounter per Paging Origin level is incremented by 1 for each paging origin whenever a paging record including paging origin is discarded at the gNB-DU. - -NOTE 3: Paging Origin is defined in 3GPP TS 38.473 [i.6], clause 9.3.1.79. - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.6 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.6 - -###### O-RAN addition: - -Subcounter OR.PAG.DiscardedNbr.PagingIdentity where *PagingIdentity* is Paging Identity number: - -0: RAN UE Paging identity - -1: CN UE Paging identity - -Subcounter OR.PAG.DiscardedNbr.PagingPriority where *PagingPriority* is Paging Priority number: - -0: PrioLevel1 - -1: PrioLevel2 - -... - -7: PrioLevel8 - -Subcounter OR.PAG.DiscardedNbr.PagingOrigin where *PagingOrigin* identifies the Paging Origin IE. - -- f) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.6 -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.6 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.1.27.6 -- i) Network Operator's Traffic Engineering Community - -#### A.4.2.29 Non-Linear Scale Distribution of restricted UL data throughput in RLC - -- a) This measurement provides the distribution of restricted Uplink data throughput experienced by UE in RLC layer. This measurement is intended for data bursts that are large enough to require transmissions to be split across multiple slots. - -It is an optional counter for O-DU. - -The bins corresponding to the UL throughput experienced by UE in RLC layer is defined as follows. - -- bin1: 0 Kbps = Throughput -- bin2: 0 Kbps < Throughput < 100 Kbps -- bin3: 100 Kbps <= Throughput < 200 Kbps -- bin4: 200 Kbps <= Throughput < 500 Kbps -- bin5: 500 Kbps <= Throughput < 1 Mbps -- bin6: 1 Mbps <= Throughput < 2 Mbps -- bin7: 2 Mbps <= Throughput < 5 Mbps -- bin8: 5 Mbps <= Throughput < 10 Mbps -- bin9: 10 Mbps <= Throughput < 20 Mbps -- bin10: 20 Mbps <= Throughput < 40 Mbps -- bin11: 40 Mbps <= Throughput < 60 Mbps -- bin12: 60 Mbps <= Throughput < 80 Mbps -- bin13: 80 Mbps <= Throughput < 100 Mbps -- bin14: 100 Mbps <= Throughput < 200 Mbps -- bin15: 200 Mbps <= Throughput < 400 Mbps -- bin16: 400 Mbps <= Throughput < 600 Mbps -- bin17: 600 Mbps <= Throughput < 800 Mbps -- bin18: 800 Mbps <= Throughput < 1 Gbps -- bin19: 1 Gbps <= Throughput < 2 Gbps -- bin20: 2 Gbps <= Throughput < 5 Gbps -- bin21: 5 Gbps <= Throughput - -- b) DER (n=1) -- c) Considering there are n samples during measurement time T and each sample has the same time period tn, the measurement of one sample is obtained by the following formula for a measurement period tn, - -$$\text{If ThpTimeUI} > 0, \frac{\sum ThpVolUI}{\sum ThpTimeUI} \times 1000 [\text{kbits/s}]$$ - -$$\text{If ThpTimeUI}=0, 0 [\text{kbit/s}]$$ - -,where ThpTimeUI = T1-T2 [ms]. - -| | | -|-----------|------------------------------------------------------------------------------------------------------------------| -| ThpVolUI | The total RLC level volume of data (in kbits) successfully transmitted from RLC layer to the upper layer (PDCP). | -| ThpTimeUI | The measurement duration in which data is successfully transmitted from RLC layer to the upper layer. | -| T1 | The point in time after T2 when the last RLC data is transmitted from RLC layer to the upper layer. | -| T2 | The point in time when the first RLC data is transmitted from RLC layer to the upper layer. | - -For each measurement sample, the bin corresponding to the UL throughput experienced by the UE is incremented by one. Separate counters are maintained for each mapped 5QI (or QCI for option 3) and for each supported SNSSAI. - -- d) A set of integers, each representing the (integer) number of samples with a UL throughput in the range represented by that bin. If the optional QoS level subcounter and S-NSSAI subcounter measurements are performed, the number of measurements is equal to the number of mapped 5QIs or QCIs and number of supported S-NSSAI. -- e) The measurement name has the form OR.DRB.UERlcThpUILogDist.Bin or OR.DRB.UERlcThpUILogDist.Bin\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.UERlcThpUILogDist.Bin or OR.RLC.UERlcThpUILogDist.Bin\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where Filter is a combination of QoS level, S-NSSAI. Where QoS represents the mapped 5QI or QCI level, and SNSSAI represents S-NSSAI. -- f) gNBDUFunction -- g) Valid for packet switched traffic. - -- h) 5GS -- i) One usage of this measurement is for performance assurance within integrity area (user plane connection quality). - -#### **A.4.2.30 Non-Linear Scale Distribution of restricted DL data throughput in RLC** - -- a) This measurement provides the distribution of restricted Downlink data throughput experienced by UE in RLC layer. This measurement is intended for data bursts that are large enough to require transmissions to be split across multiple slots. - -It is an optional counter for O-DU. - -The bins corresponding to the DL throughput experienced by UE in RLC layer is defined as follows. - -- bin1: 0 Kbps = Throughput -- bin2: 0 Kbps < Throughput < 100 Kbps -- bin3: 100 Kbps <= Throughput < 200 Kbps -- bin4: 200 Kbps <= Throughput < 500 Kbps -- bin5: 500 Kbps <= Throughput < 1 Mbps -- bin6: 1 Mbps <= Throughput < 2 Mbps -- bin7: 2 Mbps <= Throughput < 5 Mbps -- bin8: 5 Mbps <= Throughput < 10 Mbps -- bin9: 10 Mbps <= Throughput < 20 Mbps -- bin10: 20 Mbps <= Throughput < 40 Mbps -- bin11: 40 Mbps <= Throughput < 60 Mbps -- bin12: 60 Mbps <= Throughput < 80 Mbps -- bin13: 80 Mbps <= Throughput < 100 Mbps -- bin14: 100 Mbps <= Throughput < 200 Mbps -- bin15: 200 Mbps <= Throughput < 400 Mbps -- bin16: 400 Mbps <= Throughput < 600 Mbps -- bin17: 600 Mbps <= Throughput < 800 Mbps -- bin18: 800 Mbps <= Throughput < 1 Gbps -- bin19: 1 Gbps <= Throughput < 2 Gbps -- bin20: 2 Gbps <= Throughput < 5 Gbps -- bin21: 5 Gbps <= Throughput - -- b) DER (n=1) - -- c) Considering there are n samples during measurement time T and each sample has the same time period tn, the measurement of one sample is obtained by the following formula for a measurement period tn, - -$$\text{If ThpTimeDl} > 0, \frac{\sum \text{ThpVolDl}}{\sum \text{ThpTimeDl}} \times 1000 [\text{kbits/s}]$$ - -$$\text{If ThpTimeDl} = 0, 0 [\text{kbit/s}]$$ - -,where ThpTimeDl = T1-T2 [ms]. - -| | | -|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| ThpVolDl | The total RLC level volume of data (in kbits) successfully transmitted in DL.

NOTE: In case of RLC UM, ThpVolDl is calculated based on the total data transmitted. In case of RLC AM, ThpVolDl is calculated only for data for which RLC ACK was confirmed within the measurement period. | -| ThpTimeDl | The measurement duration in which data is transmitted from RLC layer to lower layer. | -| T1 | The point in time after T2 when the last RLC data is transmitted from RLC layer to the lower layer. | -| T2 | The point in time when the first RLC data is transmitted from RLC layer to the lower layer. | - -For each measurement sample, the bin corresponding to the DL throughput experienced by the UE is incremented by one. Separate counters are maintained for each mapped 5QI (or QCI for option 3) and for each supported SNSSAI. - -- d) A set of integers, each representing the (integer) number of samples with a DL throughput in the range represented by that bin. If the optional QoS level subcounter and S-NSSAI subcounter measurements are performed, the number of measurements is equal to the number of mapped 5QIs or QCIs and number of supported S-NSSAI. -- e) The measurement name has the form OR.DRB.UERlcThpDILogDist.Bin or OR.DRB.UERlcThpDILogDist.Bin\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.RLC.UERlcThpDILogDist.Bin or OR.RLC.UERlcThpDILogDist.Bin\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a combination of QoS level, S-NSSAI. Where QoS represents the mapped 5QI or QCI level, and SNSSAI represents S-NSSAI. -- f) gNBDUFunction -- g) Valid for packet switched traffic. -- h) 5GS -- i) One usage of this measurement is for performance assurance within integrity area (user plane connection quality). - -### A.4.3 NR MAC performance measurements - -#### A.4.3.1 Received UL MAC PDU volume - -- a) This counter provides the UL MAC PDU volume received as initial transmission or retransmission in MAC layer. -It is recommended to support for O-DU -- b) CC -- c) Measurement subcounter is incremented by the volume of the UL MAC PDU whenever the UL MAC PDU is received as initial transmission or retransmission when the SSB for PUSCH is the group of subcounter.*SSB*. -- d) Each measurement is an integer value representing the UL MAC PDU volume received as initial transmission or retransmission in MAC layer in kilobits. -- e) OR.DRB.RxUIMacPduVol.SSB (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.MAC.RxUIMacPduVol.SSB (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *SSB* is the SSB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.3.2 Transmitted DL MAC PDU volume - -- a) This counter provides the DL MAC PDU volume transmitted as initial transmission or retransmission in MAC layer. -It is recommended to support for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by the volume of the DL MAC PDU whenever the DL MAC PDU is transmitted as initial transmission or retransmission when the SSB for PDSCH is the group of subcounter.*SSB*. -- d) Each measurement is an integer value representing the DL MAC PDU volume transmitted as initial transmission or retransmission in MAC layer in kilobits. -- e) OR.DRB.TxDIMacPduVol.SSB (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.MAC.TxDIMacPduVol.SSB (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *SSB* is the SSB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.3.3 Void - -### A.4.4 NR UL HARQ performance measurements - -#### A.4.4.1 Distribution of PUSCH per MCS (initial transmission) - -- a) This counter provides the distributions of PUSCH at the initial transmission per MCS. -It is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PUSCH is received for initial transmission when the MCS table of the PUSCH is group of subcounter.*MCSTable* and when the MCS index of the PUSCH is group of subcounter.*MCSInitial*. -- d) Each measurement is an integer value representing the distributions of PUSCH at the initial transmission per MCS. -- e) OR.TB.DistPuschMcsInitial.*MCSInitial.MCSTable* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ULHARQ.DistPuschMcsInitial.*MCSInitial.MCSTable* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSInitial* is the MCS index for initial transmission: - - 0: $I_{MCS} = 0$ - - 1: $I_{MCS} = 1$ - - ... - - 28: $I_{MCS} = 28$ - -*MCSTable* is the MCS table: - - - 0: MCS index table 1 for PDSCH/PUSCH without transform precoding - - 1: MCS index table 2 for PDSCH/PUSCH without transform precoding - - 2: MCS index table 3 for PDSCH/PUSCH without transform precoding - - 3: MCS index table for PUSCH with transform precoding and 64QAM ( $q=1$ ) - -- 4: MCS index table for PUSCH with transform precoding and 64QAM (q=2) -- 5: MCS index table 2 for PUSCH with transform precoding and 64QAM(q=1) -- 6: MCS index table 2 for PUSCH with transform precoding and 64QAM (q=2) - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.4.2 Distribution of PUSCH per MCS (initial transmission/CRC OK) - -- a) This counter provides the distributions of the number of CRC succeeded for PUSCH at initial transmission per MCS. -It is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PUSCH of which CRC is OK is received for initial transmission when the MCS table of the PUSCH is group of subcounter.*MCSTable* and when the MCS index of the PUSCH is group of subcounter.*MCSInitial*. -- d) Each measurement is an integer value representing the distributions of the number of CRC succeeded for PUSCH at initial transmission per MCS. -- e) OR.TB.DistPuschMcsInitialTxCRC.*MCSInitial.MCSTable* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ULHARQ.DistPuschMcsInitialTxCRC.*MCSInitial.MCSTable* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSInitial* is the MCS index for initial transmission: - -0: $I_{MCS} = 0$ -1: $I_{MCS} = 1$ -... -28: $I_{MCS} = 28$ - -*MCSTable* is the MCS table: - -- 0: MCS index table 1 for PDSCH/PUSCH without transform precoding -- 1: MCS index table 2 for PDSCH/PUSCH without transform precoding -- 2: MCS index table 3 for PDSCH/PUSCH without transform precoding -- 3: MCS index table for PUSCH with transform precoding and 64QAM (q=1) -- 4: MCS index table for PUSCH with transform precoding and 64QAM (q=2) -- 5: MCS index table 2 for PUSCH with transform precoding and 64QAM(q=1) -- 6: MCS index table 2 for PUSCH with transform precoding and 64QAM (q=2) - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.4.3 Distribution of PUSCH per MCS (any/CRC OK) - -- a) This counter provides the distributions of PUSCH at initial transmission or retransmission per MCS. -It is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PUSCH of which CRC is OK is received for initial transmission or retransmission when the MCS table of the PUSCH is group of subcounter.*MCSTable* and when the MCS index of the PUSCH is group of subcounter.*MCSRetx*. -- d) Each measurement is an integer value representing the distributions of PUSCH at initial transmission or retransmission per MCS. -- e) OR.TB.DistPuschMcsAny.*MCSRetx.MCSTable* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ULHARQ.DistPuschMcsAny.*MCSRetx.MCSTable* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSRetx* is the MCS index for initial transmission or retransmission: - - 0: $I_{MCS} = 0$ - - 1: $I_{MCS} = 1$ - - ... - - 31: $I_{MCS} = 31$ - -*MCSTable* is the MCS table: - - - 0: MCS index table 1 for PDSCH/PUSCH without transform precoding - - 1: MCS index table 2 for PDSCH/PUSCH without transform precoding - - 2: MCS index table 3 for PDSCH/PUSCH without transform precoding - - 3: MCS index table for PUSCH with transform precoding and 64QAM (q=1) - - 4: MCS index table for PUSCH with transform precoding and 64QAM (q=2) - - 5: MCS index table 2 for PUSCH with transform precoding and 64QAM(q=1) - - 6: MCS index table 2 for PUSCH with transform precoding and 64QAM (q=2) -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.4.4 Distribution of PUSCH per MCS (exceeding HARQ retransmission) - -- a) This counter provides the distributions of the number of CRC failure for PUSCH at final retransmission per MCS. -It is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PUSCH of which CRC is NG is received for final retransmission when the MCS table of the PUSCH is group of subcounter.*MCSTable* and when the MCS index of the PUSCH is group of subcounter.*MCSRetx*. -- d) Each measurement is an integer value representing the distributions of the number of CRC failure for PUSCH at final retransmission per MCS. -- e) OR.TB.DistPuschMcsExceedHarqRetrans.*MCSRetx.MCSTable* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ULHARQ.DistPuschMcsExceedHarqRetrans.*MCSRetx.MCSTable* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSRetx* is the MCS index for final retransmission: - - 0: $I_{MCS} = 0$ - - 1: $I_{MCS} = 1$ - - ... - - 31: $I_{MCS} = 31$ - -*MCSTable* is the MCS table: - -- 0: MCS index table 1 for PDSCH/PUSCH without transform precoding -- 1: MCS index table 2 for PDSCH/PUSCH without transform precoding -- 2: MCS index table 3 for PDSCH/PUSCH without transform precoding -- 3: MCS index table for PUSCH with transform precoding and 64QAM (q=1) -- 4: MCS index table for PUSCH with transform precoding and 64QAM (q=2) -- 5: MCS index table 2 for PUSCH with transform precoding and 64QAM(q=1) -- 6: MCS index table 2 for PUSCH with transform precoding and 64QAM (q=2) - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.4.5 Distribution of PUSCH per MCS (MU-MIMO/initial transmission) - -- a) This counter provides the distributions of PUSCH at initial transmission in MU-MIMO usage per MCS. - -It is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PUSCH is transmitted (including MU-MIMO usage) for initial transmission when the MCS table of the PUSCH is group of subcounter.*MCSTable* and when the MCS index of the PUSCH is group of subcounter.*MCSInitial*. -- d) Each measurement is an integer value representing the distributions of PUSCH at initial transmission in MU-MIMO usage per MCS. -- e) OR.TB.DistPuschMcsMuMimoInitialTx.*MCSInitial.MCSTable* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ULHARQ.DistPuschMcsMuMimoInitialTx.*MCSInitial.MCSTable* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSInitial* is the MCS index for initial transmission: - -0: $I_{MCS} = 0$ - -1: $I_{MCS} = 1$ - -... - -28: $I_{MCS} = 28$ - -*MCSTable* is the MCS table: - -- 0: MCS index table 1 for PDSCH/PUSCH without transform precoding -- 1: MCS index table 2 for PDSCH/PUSCH without transform precoding -- 2: MCS index table 3 for PDSCH/PUSCH without transform precoding -- 3: MCS index table for PUSCH with transform precoding and 64QAM (q=1) -- 4: MCS index table for PUSCH with transform precoding and 64QAM (q=2) -- 5: MCS index table 2 for PUSCH with transform precoding and 64QAM(q=1) -- 6: MCS index table 2 for PUSCH with transform precoding and 64QAM (q=2) - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.4.6 Distribution of PUSCH per MCS (MU-MIMO/initial transmission/ACK) - -- a) This counter provides the distributions of the number of HARQ-ACK for PUSCH at initial transmission in MU-MIMO usage per MCS. -It is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PUSCH is which of CRC is OK is transmitted (including MU-MIMO usage) for initial transmission when the MCS table of the PUSCH is group of subcounter.*MCSTable* and when the MCS index of the PUSCH is group of subcounter.*MCSInitial*. -- d) Each measurement is an integer value representing the distributions of the number of HARQ-ACK for PUSCH at initial transmission in MU-MIMO usage per MCS. -- e) OR.TB.DistPuschMcsMuMimoInitialTxAck.*MCSInitial.MCSTable* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ULHARQ.DistPuschMcsMuMimoInitialTxAck.*MCSInitial.MCSTable* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSInitial* is the MCS index for initial transmission: - - 0: $I_{MCS} = 0$ - - 1: $I_{MCS} = 1$ - - ... - - 28: $I_{MCS} = 28$ - -*MCSTable* is the MCS table: - - - 0: MCS index table 1 for PDSCH/PUSCH without transform precoding - - 1: MCS index table 2 for PDSCH/PUSCH without transform precoding - - 2: MCS index table 3 for PDSCH/PUSCH without transform precoding - - 3: MCS index table for PUSCH with transform precoding and 64QAM (q=1) - - 4: MCS index table for PUSCH with transform precoding and 64QAM (q=2) - - 5: MCS index table 2 for PUSCH with transform precoding and 64QAM(q=1) - - 6: MCS index table 2 for PUSCH with transform precoding and 64QAM (q=2) -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.4.5 NR DL HARQ performance measurements - -#### A.4.5.1 Distribution of PDSCH per MCS (initial transmission) - -- a) This counter provides the distributions of PDSCH at initial transmission. This counter excludes MU-MIMO usage. -It is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PDSCH is transmitted (except for MU-MIMO usage) for initial transmission when the MCS table of the PDSCH is group of subcounter.*MCSTable* and when the MCS index of the PDSCH is group of subcounter.*MCSInitial*. -- d) Each measurement is an integer value representing the distributions of PDSCH at initial transmission. - -- e) OR.TB.DistPdschMcsInitial.MCSInitial.MCSTable (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.DLHARQ.DistPdschMcsInitial.MCSInitial.MCSTable (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSInitial* is the MCS index for initial transmission: - -0: $I_{MCS} = 0$ - -1: $I_{MCS} = 1$ - -... - -28: $I_{MCS} = 28$ - -*MCSTable* is the MCS table: - -0: MCS index table 1 for PDSCH/PUSCH without transform precoding - -1: MCS index table 2 for PDSCH/PUSCH without transform precoding - -2: MCS index table 3 for PDSCH/PUSCH without transform precoding - -- f) NRCellIDU - -- g) Packet Switched - -- h) 5GS - -- i) Network Operator's Traffic Engineering Community - -#### A.4.5.2 Distribution of PDSCH per MCS (initial transmission/ACK) - -- a) This counter provides the distributions of the number of HARQ-ACK for PDSCH at initial transmission per MCS. This counter excludes MU-MIMO usage. - -It is optional counter for O-DU. - -- b) CC - -- c) Measurement subcounter is incremented by 1 whenever the HARQ-ACK feedback is received for the corresponding PDSCH (except for MU-MIMO usage) transmitted for initial transmission when the MCS table of the PDSCH is group of subcounter.*MCSTable* and when the MCS index of the PDSCH is group of subcounter.*MCSInitial*. - -- d) Each measurement is an integer value representing the distributions of the number of HARQ-ACK for PDSCH at initial transmission per MCS. - -- e) OR.TB.DistPdschMcsInitialTxAck.MCSInitial.MCSTable (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.DLHARQ.DistPdschMcsInitialTxAck.MCSInitial.MCSTable (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSInitial* is the MCS index for initial transmission: - -0: $I_{MCS} = 0$ - -1: $I_{MCS} = 1$ - -... - -28: $I_{MCS} = 28$ - -*MCSTable* is the MCS table: - -0: MCS index table 1 for PDSCH/PUSCH without transform precoding - -1: MCS index table 2 for PDSCH/PUSCH without transform precoding - -2: MCS index table 3 for PDSCH/PUSCH without transform precoding - -- f) NRCellIDU - -- g) Packet Switched - -- h) 5GS - -- i) Network Operator's Traffic Engineering Community - -#### A.4.5.3 Distribution of PDSCH per MCS (any/ACK) - -- a) This counter provides the distributions of the number of HARQ-ACK for PDSCH at initial transmission or retransmission per MCS. This counter excludes MU-MIMO usage. - -It is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever the HARQ-ACK feedback is received for the corresponding PDSCH (except for MU-MIMO usage) transmitted for initial transmission or retransmission when the MCS table of the PDSCH is group of subcounter.*MCSTable* and when the MCS index of the PDSCH is group of subcounter.*MCSRetx*. -- d) Each measurement is an integer value representing the distributions of the number of HARQ-ACK for PDSCH at initial transmission or retransmission per MCS. -- e) OR.TB.DistPdschMcsAny.*MCSRetx.MCSTable* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.DLHARQ.DistPdschMcsAny.*MCSRetx.MCSTable* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSRetx* is the MCS index for initial transmission or retransmission: - -0: *IMCS* = 0 - -1: *IMCS* = 1 - -... - -31: *IMCS* = 31 - -*MCSTable* is the MCS table: - -0: MCS index table 1 for PDSCH/PUSCH without transform precoding - -1: MCS index table 2 for PDSCH/PUSCH without transform precoding - -2: MCS index table 3 for PDSCH/PUSCH without transform precoding - -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.5.4 Distribution of PDSCH per MCS (exceeding HARQ retransmission) - -- a) This counter provides the distributions of the number of HARQ-NACK for PDSCH at final retransmission per MCS. This counter excludes MU-MIMO usage. - -It is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever the HARQ-NACK feedback or no feedback related with HARQ is received for the corresponding PDSCH (except for MU-MIMO usage) transmitted for final retransmission when the MCS table of the PDSCH is group of subcounter.*MCSTable* and when the MCS index of the PDSCH is group of subcounter.*MCSRetx*. -- d) Each measurement is an integer value representing the distributions of the number of HARQ-NACK for PDSCH at final retransmission per MCS. -- e) OR.TB.DistPdschMcsExceedHarqRetrans.*MCSRetx.MCSTable* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.DLHARQ.DistPdschMcsExceedHarqRetrans.*MCSRetx.MCSTable* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSRetx* is the MCS index for final retransmission: - -0: $I_{MCS} = 0$ -1: $I_{MCS} = 1$ -... -31: $I_{MCS} = 31$ - -*MCSTable* is the MCS table: - -0: MCS index table 1 for PDSCH/PUSCH without transform precoding -1: MCS index table 2 for PDSCH/PUSCH without transform precoding -2: MCS index table 3 for PDSCH/PUSCH without transform precoding - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.5.5 Distribution of PDSCH per MCS (MU-MIMO/initial transmission) - -- a) This counter provides the distributions of PDSCH at initial transmission in MU-MIMO usage per MCS. - -It is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PDSCH is transmitted (including MU-MIMO usage) for initial transmission when the MCS table of the PDSCH is group of subcounter.*MCSTable* and when the MCS index of the PDSCH is group of subcounter.*MCSInitial*. -- d) Each measurement is an integer value representing the distributions of PDSCH at initial transmission in MU-MIMO usage per MCS. -- e) OR.TB.DistPdschMcsMuMimoInitialTx.*MCSInitial.MCSTable* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.DLHARQ.DistPdschMcsMuMimoInitialTx.*MCSInitial.MCSTable* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSInitial* is the MCS index for initial transmission: - - 0: $I_{MCS} = 0$ - - 1: $I_{MCS} = 1$ - - ... - - 28: $I_{MCS} = 28$ - -*MCSTable* is the MCS table: - -0: MCS index table 1 for PDSCH/PUSCH without transform precoding -1: MCS index table 2 for PDSCH/PUSCH without transform precoding -2: MCS index table 3 for PDSCH/PUSCH without transform precoding - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.5.6 Distribution of PDSCH per MCS (MU-MIMO/initial transmission/ACK) - -- a) This counter provides the distributions of the number of HARQ-ACK for PDSCH at initial transmission in MU-MIMO usage per MCS. - -It is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever the HARQ-ACK feedback is received for the corresponding PDSCH (including MU-MIMO usage) transmitted for initial transmission when the MCS table of the PDSCH is group of subcounter.*MCSTable* and when the MCS index of the PDSCH is group of subcounter.*MCSInitial*. -- d) Each measurement is an integer value representing the distributions of the number of HARQ-ACK for PDSCH at initial transmission in MU-MIMO usage per MCS. -- e) OR.TB.DistPdschMcsMuMimoInitialTxAck.*MCSInitial.MCSTable* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.DLHARQ.DistPdschMcsMuMimoInitialTxAck.*MCSInitial.MCSTable* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSInitial* is the MCS index for initial transmission: - - 0: $I_{MCS} = 0$ - - 1: $I_{MCS} = 1$ - - ... - - 28: $I_{MCS} = 28$ - -*MCSTable* is the MCS table: - - - 0: MCS index table 1 for PDSCH/PUSCH without transform precoding - - 1: MCS index table 2 for PDSCH/PUSCH without transform precoding - - 2: MCS index table 3 for PDSCH/PUSCH without transform precoding -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.4.6 NR UL Signal Quality Level performance measurements - -#### A.4.6.1 Distribution of PUSCH per MCS (Rank1) - -- a) This counter provides the distributions of PUSCH transmitted with rank 1 per MCS. - -It is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PUSCH is received with Rank 1 when the MCS table of the PUSCH is group of subcounter.*MCSTable* and when the MCS index of the PUSCH is group of subcounter.*MCSRetx*. -- d) Each measurement is an integer value representing the distributions of PUSCH transmitted with rank 1 per MCS. -- e) OR.L1M.DistPuschMcsRank1.*MCSRetx.MCSTable* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ULSQL.DistPuschMcsRank1.*MCSRetx.MCSTable* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSRetx* is the MCS index for initial transmission: - - 0: $I_{MCS} = 0$ - - 1: $I_{MCS} = 1$ - - ... - - 31: $I_{MCS} = 31$ - -*MCSTable* is the MCS table: - -- 0: MCS index table 1 for PDSCH/PUSCH without transform precoding - - 1: MCS index table 2 for PDSCH/PUSCH without transform precoding - - 2: MCS index table 3 for PDSCH/PUSCH without transform precoding - - 3: MCS index table for PUSCH with transform precoding and 64QAM (q=1) - - 4: MCS index table for PUSCH with transform precoding and 64QAM (q=2) - - 5: MCS index table 2 for PUSCH with transform precoding and 64QAM(q=1) - - 6: MCS index table 2 for PUSCH with transform precoding and 64QAM (q=2) -- f) NRCellIDU - - g) Packet Switched - - h) 5GS - - i) Network Operator's Traffic Engineering Community - -#### A.4.6.2 Distribution of PUSCH per MCS (Rank2) - -- a) This counter provides the distributions of PUSCH transmitted with rank 2 per MCS. -It is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PUSCH is received with Rank 2 when the MCS table of the PUSCH is group of subcounter.*MCSTable* and when the MCS index of the PUSCH is group of subcounter.*MCSRetx*. -- d) Each measurement is an integer value representing the distributions of PUSCH transmitted with rank 2 per MCS. -- e) OR.L1IM.DistPuschMcsRank2.*MCSRetx.MCSTable* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ULSQL.DistPuschMcsRank2.*MCSRetx.MCSTable* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSRetx* is the MCS index for initial transmission: - -- 0: $I_{MCS} = 0$ -- 1: $I_{MCS} = 1$ -- ... -- 31: $I_{MCS} = 31$ - -*MCSTable* is the MCS table: - -- 0: MCS index table 1 for PDSCH/PUSCH without transform precoding - - 1: MCS index table 2 for PDSCH/PUSCH without transform precoding - - 2: MCS index table 3 for PDSCH/PUSCH without transform precoding - - 3: MCS index table for PUSCH with transform precoding and 64QAM (q=1) - - 4: MCS index table for PUSCH with transform precoding and 64QAM (q=2) - - 5: MCS index table 2 for PUSCH with transform precoding and 64QAM(q=1) - - 6: MCS index table 2 for PUSCH with transform precoding and 64QAM (q=2) -- f) NRCellIDU - - g) Packet Switched - - h) 5GS - - i) Network Operator's Traffic Engineering Community - -#### A.4.6.3 Distribution of PUSCH per SSB (Rank1) - -- a) This counter provides the distributions of PUSCH transmitted with rank 1 per SSB. - -It is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PUSCH is received with Rank 1 when the SSB used for the PUSCH is group of subcounter.*SSB*. -- d) Each measurement is an integer value representing the distributions of PUSCH transmitted with rank 1 per SSB. -- e) OR.L1M.DistPuschSsbBeamRank1.*SSB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ULSQL.DistPuschSsbBeamRank1.*SSB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *SSB* is the SSB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.6.4 Distribution of PUSCH per SSB (Rank2) - -- a) This counter provides the distributions of PUSCH transmitted with rank 2 per SSB. - -It is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PUSCH is received with Rank 2 when the SSB used for the PUSCH is group of subcounter.*SSB*. -- d) Each measurement is an integer value representing the distributions of PUSCH transmitted with rank 2 per SSB. -- e) OR.L1M.DistPuschSsbBeamRank2.*SSB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ULSQL.DistPuschSsbBeamRank2.*SSB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *SSB* is the SSB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.6.5 PUSCH received power - -- a) This counter measures the following $x$ and provides $\text{round}(x, 2) \cdot 10^2$ . $x$ is the statistics of received power of FL DMRS of PUSCH. This counter obtains the power for every slot or mini slot in which PUSCH reception is expected. The power is - -normalized by PRB and antenna port. If Rx beam is created by some antenna ports, this counter is calculated with the power of only the antenna ports used to create Rx beam. - -It is recommended to support for O-DU. - -- b) SI -- c) Measurement subcounter of subcounter.*statistic*(avg.) is calculated by $\text{round}(x/y, 2) * 10^2$ , where: - -x is incremented by the volume of power of front loaded DMRS of PUSCH whenever PUSCH reception is expected when SSB used for PUSCH is group of subcounter.SSB. The power is normalized by PRB and antenna port. If Rx beam is created by some antenna ports, this counter is calculated with the power of only the antenna ports used to create Rx beam. - -y is incremented by 1 whenever PUSCH reception is expected when SSB used for PUSCH is group of subcounter.SSB. - -Measurement subcounter of subcounter.*statistic*(max/min) is maximum/minimum number of $\text{round}(z, 2) * 10^2$ . It is assigned whenever z is updated by the volume $\text{round}(z, 2) * 10^2$ , if $\text{round}(z, 2) * 10^2$ is bigger/smaller than previously counted volume, where: - -z is the volume of power of front loaded DMRS of PUSCH whenever PUSCH reception is expected when SSB used for PUSCH is group of subcounter.SSB. The power is normalized by PRB and antenna port. If Rx beam is created by some antenna ports, this counter is calculated with the power of only the antenna ports used to create Rx beam. -- d) Each measurement is an integer value representing the PUSCH received power in dBm/102. -- e) OR.L1M.PuschRxPower.SSB.*statistic* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ULSQL.PuschRxPower.SSB.*statistic* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where SSB is the SSB index: - - 0: #0 - - 1: #1 - - - - 63: #63 - -*statistic* is - - - 0: average - - 1: maximum - - 2: minimum -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.6.6 PUSCH RSSI - -- a) This counter measures the following x and provides $\text{round}(x, 2) \cdot 10^2$ . x is the statistic of the power of the REs in which PUSCH DMRS reception is expected. - -It is recommended to support for O-DU. - -- b) SI -- c) Measurement subcounter of subcounter.*statistic*(avg.) is calculated by $\text{round}(x/y, 2) * 10^2$ , where: - -x is incremented by the volume of power of the RE which PUSCH DMRS reception is expected whenever PUSCH reception is expected when SSB used for PUSCH is group of subcounter.SSB. - -y is incremented by 1 whenever PUSCH reception is expected when SSB used for PUSCH is group of subcounter.SSB. - -Measurement subcounter of subcounter.statistic(max/min) is maximum/minimum number of $\text{round}(z, 2) * 10^2$ . It is assigned whenever $z$ is updated by the volume $\text{round}(z, 2) * 10^2$ , if $\text{round}(z, 2) * 10^2$ is bigger/smaller than previously counted volume, where: - -$z$ is the volume of power of the RE which PUSCH DMRS reception is expected whenever PUSCH reception is expected when SSB used for PUSCH is group of subcounter.SSB. - -- d) Each measurement is an integer value representing the PUSCH RSSI in $\text{dBm}/10^2$ . -- e) OR.L1M.PuschRssi.SSB.statistic (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ULSQL.PuschRssi.SSB.statistic (deprecated, refer to NOTE in REQ-PMeas-MC-5) where SSB is the SSB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 - -statistic is - - - 0: average - - 1: maximum - - 2: minimum -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.6.7 PUSCH SINR - -- a) This counter measures the following $x$ and provides $\text{round}(x, 2) * 10^2$ . $x$ is the statistics of PUSCH with 2 dB bin of SINR of UE specific PUSCH. - -It is optional counter for O-DU. - -- b) SI -- c) Measurement subcounter of subcounter.statistic(avg.) is calculated by $\text{round}(x/y, 2) * 10^2$ , where: - -$x$ is incremented by the volume of SINR of the UE specific PUSCH when SSB used for PUSCH is group of subcounter.SSB and when MIMO layer of the PUSCH is group of subcounter.MIMO. - -$y$ is incremented by 1 whenever PUSCH which power detection check is OK is received when SSB used for PUSCH is group of subcounter.SSB and when MIMO layer of the PUSCH is group of subcounter.MIMO. - -Measurement subcounter of subcounter.statistic(max/min) is maximum/minimum number of $\text{round}(z, 2) * 10^2$ . It is assigned whenever $z$ is updated by the volume $\text{round}(z, 2) * 10^2$ , if $\text{round}(z, 2) * 10^2$ is bigger/smaller than previously counted volume, where: - -$z$ is the volume of SINR of the UE specific PUSCH when SSB used for PUSCH is group of subcounter.SSB and when MIMO layer of the PUSCH is group of subcounter.MIMO. - -- d) Each measurement is an integer value representing the PUSCH SINR in $\text{dB}/10^2$ . -- e) OR.L1M.PuschSinr.SSB.MIMO.statistic (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ULSQL.PuschSinr.SSB.MIMO.statistic (deprecated, refer to NOTE in REQ-PMeas-MC-5) where SSB is the SSB index: - -0: #0 -1: #1 -... -63: #63 - -*MIMO* is the number of MIMO layer: - -0: 1 layer -1: 2 layer -... -7: 8 layer - -*statistic* is - -0: average -1: maximum -2: minimum - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.6.8 PUCCH RSSI - -- a) This counter measures the following $x$ and provides $\text{round}(x, 2) \cdot 10^2$ . $x$ is the statistics of the power of the REs in which PUCCH DMRS reception is expected. - -It is recommended to support for O-DU. - -- b) SI - -- c) Measurement subcounter of subcounter.*statistic*(avg.) is calculated by $\text{round}(x/y, 2) \cdot 10^2$ , where: - -$x$ is incremented by the volume of power of the RE which PUCCH DMRS reception is expected whenever PUCCH reception is expected when SSB used for PUCCH is group of subcounter.*SSB*. - -$y$ is incremented by 1 whenever PUCCH reception is expected when SSB used for PUCCH is group of subcounter.*SSB*. - -Measurement subcounter of subcounter.*statistic*(max/min) is maximum/minimum number of $\text{round}(z, 2) \cdot 10^2$ . It is assigned whenever $z$ is updated by the volume $\text{round}(z, 2) \cdot 10^2$ , if $\text{round}(z, 2) \cdot 10^2$ is bigger/smaller than previously counted volume, where: - -$z$ is the volume of power of the RE which PUCCH DMRS reception is expected whenever PUCCH reception is expected when SSB used for PUCCH is group of subcounter.*SSB*. - -- d) Each measurement is an integer value representing the PUCCH RSSI in dBm/ $10^2$ . - -- e) OR.L1M.PucchRssi.SSB.*statistic* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ULSQL.PucchRssi.SSB.*statistic* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *SSB* is the SSB index: - -0: #0 -1: #1 -... -63: #63 - -*statistic* is - -0: average -1: maximum -2: minimum - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.6.9 PUCCH SINR - -- a) This counter measures the following $x$ and provides $\text{round}(x, 2) \cdot 10^2$ . $x$ is the statistics of SINR of UE specific PUCCH. -It is optional counter for O-DU. - -- b) SI - -- c) Measurement subcounter of subcounter.*statistic*(avg.) is calculated by $\text{round}(x/y, 2) \cdot 10^2$ , where: - -$x$ is incremented by the volume of SINR of the UE specific PUCCH when SSB used for PUCCH is group of subcounter.SSB. - -$y$ is incremented by 1 whenever PUCCH which power detection check is OK is received when SSB used for PUCCH is group of subcounter.SSB. - -Measurement subcounter of subcounter.*statistic*(max/min) is maximum/minimum number of $\text{round}(z, 2) \cdot 10^2$ . It is assigned whenever $z$ is updated by the volume $\text{round}(z, 2) \cdot 10^2$ , if $\text{round}(z, 2) \cdot 10^2$ is bigger/smaller than previously counted volume, where: - -$z$ is the volume of SINR of the UE specific PUCCH when SSB used for PUCCH is group of subcounter.SSB. - -- d) Each measurement is an integer value representing the PUCCH SINR in $\text{dB}/10^2$ . - -- e) OR.L1M.PucchSinr.SSB.*statistic* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.ULSQL.PucchSinr.SSB.*statistic* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where SSB is the SSB index: - -0: #0 -1: #1 -... -63: #63 - -*statistic* is -0: average -1: maximum -2: minimum - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.6.10 PRACH preamble correlation value - -- a) This counter measures the following $x$ and provides $\text{round}(x, 2) \cdot 10^2$ . $x$ is the statistics of the correlation value among preambles of the PRB where PRACH preamble is detected. This counter is normalized by PRB. - -It is recommended to support for O-DU. - -- b) SI - -- c) Measurement of subcounter.SSB.*statistic*(avg.) is calculated by $\text{round}(x/y, 2) \cdot 10^2$ , where: - -$x$ is incremented by the correlation volume among preambles of the PRB whenever PRACH preamble is detected when SSB used for PRACH is subcounter.SSB. - -$y$ is incremented by 1 whenever PRACH preamble is detected when SSB used for PRACH is subcounter.SSB. - -The correlation value is calculated by summing the received power of the PRACH and the preamble repetition gain within one PRACH reception per SSB index. - -Measurement of subcounter.SSB.*statistic*(max/min) is maximum/minimum number of $\text{round}(z, 2) \cdot 10^2$ . It is assigned whenever $z$ is updated by the volume $\text{round}(z, 2) \cdot 10^2$ , if $\text{round}(z, 2) \cdot 10^2$ is bigger/smaller than previously counted volume, where: - -$z$ is the correlation volume among preambles of the PRB whenever PRACH preamble is detected when SSB used for PRACH is subcounter.SSB. - -- d) Each measurement is an integer value representing the PRACH preamble correlation value in dBm/102. - -- e) OR.RACH.PrachPreambleCorrelationValue.SSB.*statistic* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ULSQL.PrachPreambleCorrelationValue.SSB.*statistic* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where SSB is the SSB index: - -0: #0 - -1: #1 - -... - -63: #63 - -*statistic* is - -0: average - -1: maximum - -2: minimum - -- f) NRCellIDU - -- g) Packet Switched - -- h) 5GS - -- i) Network Operator's Traffic Engineering Community - -#### A.4.6.11 RSSI of PRACH transmission occasion - -- a) This counter measures the following $x$ and provides $\text{round}(x, 2) \cdot 10^2$ . $x$ is the statistics of the RACH occasion RSSI. This counter is normalized by PRB. - -It is optional counter for O-DU. - -- b) SI - -- c) Measurement subcounter of subcounter.*statistic*(avg.) is calculated by $\text{round}(x/y, 2) \cdot 10^2$ , where: - -$x$ is incremented by the volume of RSSI at every PRACH occasion when SSB used for PRACH is group of subcounter.SSB. - -$y$ is incremented by 1 at every PRACH occasion when SSB used for PRACH is group of subcounter.SSB. - -Measurement subcounter of subcounter.*statistic*(max/min) is maximum/minimum number of $\text{round}(z, 2) * 10^2$ . It is assigned whenever $z$ is updated by the volume $\text{round}(z, 2) * 10^2$ , if $\text{round}(z, 2) * 10^2$ is bigger/smaller than previously counted volume, where: - -$z$ is the volume of RSSI at every PRACH occasion when SSB used for PRACH is group of subcounter.SSB. - -- d) Each measurement is an integer value representing the RSSI of PRACH transmission occasion in dBm/102. -- e) OR.RACH.RssiPrachTxOccasion.SSB.*statistic* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ULSQL.RssiPrachTxOccasion.SSB.*statistic* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where SSB is the SSB index: - -0: #0 - -1: #1 - -... - -63: #63 - -*statistic* is - -0: average - -1: maximum - -2: minimum - -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.6.12 Distribution of path loss for FR1 - -- a) This counter provides the distributions of PUSCH including PHR with a certain bin of the pathloss. This counter is for FR1. - -It is optional counter for O-DU. - -- b) CC - -- c) This subcounter is measured only when the cell uses FR1. - -Measurement subcounter is incremented by 1 whenever PHR is received when the SSB used for the PUSCH is group of subcounter.SSB and when the pathloss calculated with the PHR is group of subcounter.*binX*. - -- d) Each measurement is an integer value representing the distributions of PUSCH including PHR with a certain bin of the pathloss. - -- e) OR.L1IM.DistPathlossFr1.SSB.*binX* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ULSQL.DistPathlossFr1.SSB.*binX* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where SSB is the SSB index: - -0: #0 - -1: #1 - -... - -63: #63 - -*binX* is the bin of the pathloss, $x$ . - -Bin1: $0 \text{ dB} \leq x < 40 \text{ dB}$ - Bin2: $40 \text{ dB} \leq x < 45 \text{ dB}$ - Bin3: $45 \text{ dB} \leq x < 50 \text{ dB}$ - ... - Bin25: $155 \text{ dB} \leq x$ - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.6.13 Path loss for FR2 - -- a) This counter measures the following $x$ and provides $\text{round}(x, 2) \cdot 10^2$ . $x$ is the statistics of the pathloss. This counter is for FR2. - -It is optional counter for O-DU. - -- b) SI -- c) This subcounter is measured only when the cell uses FR2. - -Measurement subcounter of subcounter.*statistic*(avg.) is calculated by $\text{round}(x/y, 2) \cdot 10^2$ , where: - -$x$ is incremented by the volume of the pathloss calculated with PHR whenever PHR is received when the SSB used for the PUSCH is group of subcounter.SSB. - -$y$ is incremented by 1 whenever PHR is received when the SSB used for the PUSCH is group of subcounter.SSB - -Measurement subcounter of subcounter.*statistic*(max/min) is maximum/minimum number of $\text{round}(z, 2) \cdot 10^2$ . It is assigned whenever $z$ is updated by the volume $\text{round}(z, 2) \cdot 10^2$ , if $\text{round}(z, 2) \cdot 10^2$ is bigger/smaller than previously counted volume, where: - -$z$ is the volume of the pathloss calculated with PHR whenever PHR is received when the SSB used for the PUSCH is group of subcounter.SSB. - -- d) Each measurement is an integer value representing the path loss for FR2 in $\text{dB}/10^2$ . -- e) OR.L1M.PathlossFr2.SSB.*statistic* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), - OR.ULSQL.PathlossFr2.SSB.*statistic* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where SSB is the SSB index: - -0: #0 - 1: #1 - ... - 63: #63 - -*statistic* is - 0: average - 1: maximum - 2: minimum - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.6.14 Detection of UL out-of-sync - -- a) This counter provides the number of the detection of UL out-of-sync for bearer type change from SN terminated split bearer to SN terminated MCG bearer or SgNB release or RRC release. - -It is recommended to support for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever the UL out-of-sync is detected per SSB index of the UE: #0, #1, ..., #63 as subcounter.SSB. -- d) Each measurement is an integer value representing the number of the detection of UL out-of-sync for bearer type change from SN terminated split bearer to SN terminated MCG bearer or SgNB release or RRC release. -- e) OR.L1M.DetectUIOutSync.SSB (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.ULSQL.DetectUIOutSync.SSB (deprecated, refer to NOTE in REQ-PMeas-MC-5) where SSB is the SSB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.4.7 NR DL Signal Quality Level performance measurements - -#### A.4.7.1 Distribution of PDSCH per MCS (Rank1) - -- a) This counter provides the distributions of PDSCH transmitted with rank 1 per MCS. - -It is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PDSCH is transmitted with Rank 1 when the MCS table of the PDSCH is group of subcounter.MCSTable and when the MCS index of the PDSCH is group of subcounter.MCSRetx. -- d) Each measurement is an integer value representing the distributions of PDSCH transmitted with rank 1 per MCS. -- e) OR.L1M.DistPdschMcsRank1.MCSRetx.MCSTable (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.DLSQL.DistPdschMcsRank1.MCSRetx.MCSTable (deprecated, refer to NOTE in REQ-PMeas-MC-5) where MCSRetx is the MCS index for initial transmission: - - 0: IMCS = 0 - - 1: IMCS = 1 - - ... - - 31: IMCS = 31 - -MCSTable is the MCS table: - -- 0: MCS index table 1 for PDSCH/PUSCH without transform precoding -- 1: MCS index table 2 for PDSCH/PUSCH without transform precoding - -- 2: MCS index table 3 for PDSCH/PUSCH without transform precoding -- 3: MCS index table for PUSCH with transform precoding and 64QAM (q=1) -- 4: MCS index table for PUSCH with transform precoding and 64QAM (q=2) -- 5: MCS index table 2 for PUSCH with transform precoding and 64QAM(q=1) -- 6: MCS index table 2 for PUSCH with transform precoding and 64QAM (q=2) - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.7.2 Distribution of PDSCH per MCS (Rank2) - -- a) This counter provides the distributions of PDSCH transmitted with rank 2 per MCS. - -It is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PDSCH is transmitted with Rank 2 when the MCS table of the PDSCH is group of subcounter.*MCSTable* and when the MCS index of the PDSCH is group of subcounter.*MCSRetx*. -- d) Each measurement is an integer value representing the distributions of PDSCH transmitted with rank 2 per MCS. -- e) OR.L1M.DistPdschMcsRank2.*MCSRetx.MCSTable* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.DLSQL.DistPdschMcsRank2.*MCSRetx.MCSTable* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSRetx* is the MCS index for initial transmission: - -0: $I_{MCS} = 0$ -1: $I_{MCS} = 1$ -... -31: $I_{MCS} = 31$ - -*MCSTable* is the MCS table: - -- 0: MCS index table 1 for PDSCH/PUSCH without transform precoding -- 1: MCS index table 2 for PDSCH/PUSCH without transform precoding -- 2: MCS index table 3 for PDSCH/PUSCH without transform precoding -- 3: MCS index table for PUSCH with transform precoding and 64QAM (q=1) -- 4: MCS index table for PUSCH with transform precoding and 64QAM (q=2) -- 5: MCS index table 2 for PUSCH with transform precoding and 64QAM(q=1) -- 6: MCS index table 2 for PUSCH with transform precoding and 64QAM (q=2) - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.7.3 Distribution of PDSCH per MCS (Rank3) - -- a) This counter provides the distributions of PDSCH transmitted with rank 3 per MCS. - -It is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PDSCH is transmitted with Rank 3 when the MCS table of the PDSCH is group of subcounter.*MCSTable* and when the MCS index of the PDSCH is group of subcounter.*MCSRetx*. -- d) Each measurement is an integer value representing the distributions of PDSCH transmitted with rank 3 per MCS. -- e) OR.L1M.DistPdschMcsRank3.*MCSRetx.MCSTable* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.DLSQL.DistPdschMcsRank3.*MCSRetx.MCSTable* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSRetx* is the MCS index for initial transmission: - - 0: $I_{MCS} = 0$ - - 1: $I_{MCS} = 1$ - - ... - - 31: $I_{MCS} = 31$ - -*MCSTable* is the MCS table: - - - 0: MCS index table 1 for PDSCH/PUSCH without transform precoding - - 1: MCS index table 2 for PDSCH/PUSCH without transform precoding - - 2: MCS index table 3 for PDSCH/PUSCH without transform precoding - - 3: MCS index table for PUSCH with transform precoding -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.7.4 Distribution of PDSCH per MCS (Rank4) - -- a) This counter provides the distributions of PDSCH transmitted with rank 4 per MCS. -It is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PDSCH is transmitted with Rank 4 when the MCS table of the PDSCH is group of subcounter.*MCSTable* and when the MCS index of the PDSCH is group of subcounter.*MCSRetx*. -- d) Each measurement is an integer value representing the distributions of PDSCH transmitted with rank 4 per MCS. -- e) OR.L1M.DistPdschMcsRank4.*MCSRetx.MCSTable* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.DLSQL.DistPdschMcsRank4.*MCSRetx.MCSTable* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *MCSRetx* is the MCS index for initial transmission: - - 0: $I_{MCS} = 0$ - - 1: $I_{MCS} = 1$ - - ... - - 31: $I_{MCS} = 31$ - -*MCSTable* is the MCS table: - - - 0: MCS index table 1 for PDSCH/PUSCH without transform precoding - - 1: MCS index table 2 for PDSCH/PUSCH without transform precoding - - 2: MCS index table 3 for PDSCH/PUSCH without transform precoding - - 3: MCS index table for PUSCH with transform precoding -- f) NRCellIDU - -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.7.5 Distribution of PDSCH per SSB (Rank1) - -- a) This counter provides the distributions of PDSCH transmitted with rank 1 per SSB. -It is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PDSCH is transmitted with Rank 1 when the SSB used for the PDSCH is group of subcounter.*SSB*. -- d) Each measurement is an integer value representing the distributions of PDSCH transmitted with rank 1 per SSB. -- e) OR.L1M.DistPdschSsbBeamRank1.*SSB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.DLSQL.DistPdschSsbBeamRank1.*SSB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *SSB* is the SSB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.7.6 Distribution of PDSCH per SSB (Rank2) - -- a) This counter provides the distributions of PDSCH transmitted with rank 2 per SSB. -It is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PDSCH is transmitted with Rank 2 when the SSB used for the PDSCH is group of subcounter.*SSB*. -- d) Each measurement is an integer value representing the distributions of PDSCH transmitted with rank 2 per SSB. -- e) OR.L1M.DistPdschSsbBeamRank2.*SSB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.DLSQL.DistPdschSsbBeamRank2.*SSB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *SSB* is the SSB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellIDU - -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.7.7 Distribution of PDSCH per SSB (Rank3) - -- a) This counter provides the distributions of PDSCH transmitted with rank 3 per SSB. -It is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PDSCH is transmitted with Rank 3 when the SSB used for the PDSCH is group of subcounter.*SSB*. -- d) Each measurement is an integer value representing the distributions of PDSCH transmitted with rank 3 per SSB. -- e) OR.L1M.DistPdschSsbBeamRank3.*SSB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.DLSQL.DistPdschSsbBeamRank3.*SSB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *SSB* is the SSB index: -0: #0 -1: #1 -... -63: #63 -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.7.8 Distribution of PDSCH per SSB (Rank4) - -- a) This counter provides the distributions of PDSCH transmitted with rank 4 per SSB. -It is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PDSCH is transmitted with Rank 4 when the SSB used for the PDSCH is group of subcounter.*SSB*. -- d) Each measurement is an integer value representing the distributions of PDSCH transmitted with rank 4 per SSB. -- e) OR.L1M.DistPdschSsbBeamRank4.*SSB* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.DLSQL.DistPdschSsbBeamRank4.*SSB* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *SSB* is the SSB index: -0: #0 -1: #1 -... -63: #63 -- f) NRCellIDU - -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.7.9 Distribution of Wideband CQI for FR1 - -- a) This counter provides the distributions of the wideband CQI reports. - -It is optional counter for O-DU. - -- b) CC - -- c) This subcounter is measured only when the cell uses FR1. - -Measurement subcounter is incremented by 1 whenever CQI report is received when the SSB index used for the CQI report is group of subcounter.*SSB*, when the CQI table of the CQI report is group of subcounter.*CQITable* and when the CQI is group of subcounter.*CQI*. - -- d) Each measurement is an integer value representing the distributions of the wideband CQI reports. - -- e) OR.L1M.DistWidebandCqiFR1.SSB.*CQITable*.*CQI* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.DLSQL.DistWidebandCqiFR1.SSB.*CQITable*.*CQI* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *SSB* is the SSB index: - -0: #0 - -1: #1 - -... - -63: #63 - -*CQITable* is the CQI table: - -0: table 1 - -1: table 2 - -*CQI* is the CQI index: - -0: CQI index 0 - -1: CQI index 1 - -... - -15: CQI index 15 - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.7.10 Wideband CQI for FR2 - -- a) This counter measures the following $x$ and provides $\text{round}(x, 2) \cdot 10^2$ . $x$ is the statistics of linear value of the wideband CQI reports. - -It is optional counter for O-DU. - -- b) SI - -- c) This subcounter is measured only when the cell uses FR2. - -Measurement subcounter of subcounter.*statistic*(avg.) is calculated by $\text{round}(x/y, 2) * 10^2$ , where: - -*x* is incremented by the volume of CQI whenever CQI report is received when the SSB index used for the CQI report is group of subcounter.*SSB* and when the CQI table of the CQI report is group of subcounter.*CQITable*. - -*y* is incremented by 1 whenever CQI report is received when the SSB index used for the CQI report is group of subcounter.*SSB* and when the CQI table of the CQI report is group of subcounter.*CQITable*. - -Measurement subcounter of subcounter.*statistic*(max/min) is maximum/minimum number of $\text{round}(z, 2) * 10^2$ . It is assigned whenever *z* is updated by the volume $\text{round}(z, 2) * 10^2$ , if $\text{round}(z, 2) * 10^2$ is bigger/smaller than previously counted volume, where: - -*z* is the volume of CQI whenever CQI report is received when the SSB index used for the CQI report is group of subcounter.*SSB* and when the CQI table of the CQI report is group of subcounter.*CQITable*. - -- d) Each measurement is an integer value representing the wideband CQI for FR2 in $\text{CQI}/10^2$ . -- e) OR.L1M.WidebandCqiFR2.SSB.CQITable.*statistic* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.DLSQL.WidebandCqiFR2.SSB.CQITable.*statistic* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *SSB* is the SSB index: - -0: #0 -1: #1 -... -63: #63 - -*CQITable* is the CQI table: - -0: table 1 -1: table 2 - -*statistic* is -0: average -1: maximum -2: minimum - -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.7.11 PDCCH transmission power - -- a) This counter measures the following *x* and provides $\text{round}(x, 2) * 10^2$ . *x* is the statistics of transmission power determined by outer-loop TPC of UE specific PDCCH. If one or more PDCCHs associated with same SSB are transmitted within some OFDM symbols in one slot, this counter counts 1 sample and calculates power as linear average within OFDM symbols. If one or more PDCCHs associated with different SSBs are transmitted in each OFDM symbols in the one slot, this counter counts the PDCCHs for each SSB, and doesn't calculate power as average within OFDM symbols. - -It is optional counter for O-DU. - -- b) SI -- c) Measurement of subcounter.SSB.DCI.*statistic*(avg.) is calculated by $\text{round}(x/y, 2) * 10^2$ , where: - -$x$ is incremented by the volume of transmission power of PDCCH whenever PDCCH is transmitted when SSB used for PDCCH is subcounter.SSB and when the DCI format of transmitted DCI is subcounter.SSB.DCI. If one or more PDCCHs associated with same SSB are transmitted within plural OFDM symbols in one slot, the volume is linear average within the OFDM symbols. If one or more PDCCHs associated with different SSBs are transmitted in each OFDM symbols in the one slot, $x$ is incremented for each PDCCH per SSB. - -$y$ is incremented by 1 whenever PDCCH is transmitted when SSB used for PDCCH is subcounter.SSB and when the DCI format of transmitted DCI is subcounter.SSB.DCI. If one or more PDCCHs associated with same SSB are transmitted within plural OFDM symbols in one slot, $y$ is only incremented once per slot. If one or more PDCCHs associated with different SSBs are transmitted in each OFDM symbols in the one slot, $y$ is incremented once per OFDM symbol. - -Measurement of subcounter.statistic.SSB.DCI(max/min) is maximum/minimum number of $\text{round}(z, 2) * 10^2$ . It is assigned whenever $z$ is updated by the volume $\text{round}(z, 2) * 10^2$ , if $\text{round}(z, 2) * 10^2$ is bigger/smaller than previously counted volume, where: - -$z$ is the volume of transmission power of PDCCH whenever PDCCH is transmitted when SSB used for PDCCH is subcounter.SSB and when the DCI format of transmitted DCI is subcounter.SSB.DCI. If one or more PDCCHs associated with same SSB are transmitted within plural OFDM symbols in one slot, the volume is linear average within OFDM symbols. If one or more PDCCHs associated with different SSBs are transmitted in each OFDM symbols in the one slot, $z$ is once per OFDM symbol. - -- d) Each measurement is an integer value representing the PDCCH transmission power in dBm/ $10^2$ . -- e) OR.L1M.PdcchTxPower.SSB.DCI.statistic (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.DLSQL.PdcchTxPower.SSB.DCI.statistic (deprecated, refer to NOTE in REQ-PMeas-MC-5) where SSB is the SSB index: - -0: #0 -1: #1 -... -63: #63 - -DCI is the DCI format: - -0: 0\_0 -1: 0\_1 -2: 1\_0 -3: 1\_1 - -statistic is -0: average -1: maximum -2: minimum - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.4.8 NR Beamforming performance measurements - -#### A.4.8.1 Distribution of UEs per beam index - -- a) This counter provides distribution of the UEs with beam index. This counter obtains the number of the UEs per beam index. - -This is recommended to support for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by the number of the UEs per SSB index of the UE: #0, #1, ..., #63 as subcounter.SSB. - -The measurement is obtained by calculating the observed distribution of UEs per beam index per granularity period. - -- d) Each measurement is an integer value representing the distribution of the UEs with beam index. -- e) OR.L1M.DistUeBeamIndex.SSB (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.BF.DistUeBeamIndex.SSB (deprecated, refer to NOTE in REQ-PMeas-MC-5) where - -SSB is the SSB index: - -0: #0 - -1: #1 - -.. - -63: #63 - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.8.2 Best and Second Best Beam distribution - -- a) This counter provides the distribution of Best and Second best beams. This counter is only updated when number of SSB is 8 or less. - -This is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by the number of the UEs per the best and second best SSB index of the UE: best beam #0 and second beam #0, best beam #1 and second beam #0, ..., best beam#7 and second beam#7 as subcounter.binX. - -The value for a given bin shall be incremented when either best or second best beam is changed for any reason. - -- d) Each measurement is an integer value representing the distribution of Best and Second best beams. -- e) OR.L1M.BestSecondBestBeamDist.binX (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.BF.BestSecondBestBeamDist.binX (deprecated, refer to NOTE in REQ-PMeas-MC-5) where - -Bin1 is best beam #0 and second beam #0. - -Bin2 is best beam #1 and second beam #0. - -⋮ - -BinX is best beam #a and second beam #b. :X = a+8b+1 - -⋮ - -Bin64 is best beam#7 and second beam#7. - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS - -- i) Network Operator's Traffic Engineering Community - -#### A.4.8.3 UE reported differential L1-RSRP of second best beam - -- a) This counter provides the distribution of the UE reported differential L1-RSRP of second best beam from the L1-RSRP of the best beam. -- This is optional counter for O-DU. -- b) CC - - c) Measurement subcounter is incremented by 1 whenever L1-RSRP report is received when the differential L1-RSRP of second best beam from the L1-RSRP of the best beam is group of subcounter.bin. - - d) Each measurement is an integer value representing the distribution of the UE reported differential L1-RSRP of second best beam from the L1-RSRP of the best beam. - - e) OR.L1M.UeReportedDisffL1RsrpSecondBestBeam.*binX* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.BF.UeReportedDisffL1RsrpSecondBestBeam.*binX* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *binX* corresponds to the UE reported differential L1-RSRP, *x*, of second best beam from the L1-RSRP of the best beam. - - Bin1: $0 \geq x > -2$ dB - - Bin2: $-2 \text{ dB} \geq x > -4$ dB - - - - Bin16: $-30 \text{ dB} \geq x$ - - f) NRCellDU - - g) Packet Switched - - h) 5GS - - i) Network Operator's Traffic Engineering Community - -### A.4.9 NR RACH Usage performance measurements - -#### A.4.9.1 Received preambles in group A - -- a) This counter provides the number of the received random preambles of group A. -- This is recommended to support for O-DU. -- b) CC - - c) Measurement subcounter is incremented by 1 whenever random preamble of group A is received when the SSB which is used for preamble transmission is group of subcounter.SSB. - - d) Each measurement is an integer value representing the number of the received random preambles of group A. - - e) OR.RACH.RxPreamblesGroupA.SSB where SSB is the SSB index: - - 0: #0 - - 1: #1 - - - - 63: #63 - - f) NRCellDU - -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.9.2 The number of received dedicated preamble - -- a) This counter provides the number of the received dedicated preambles. - -This is recommended to support for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever dedicated preamble is received when the SSB which is used for preamble transmission is group of subcounter.*SSB*. -- d) Each measurement is an integer value representing the number of the received dedicated preambles. -- e) OR.RACH.NumRxDedictedPreamble.*SSB* where *SSB* is the SSB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.9.3 Transmitted RARs for preamble in group A - -- a) This counter provides the number of the transmitted RAR for preambles of group A. - -This is recommended to support for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RAR for preamble of group A is transmitted when the SSB which is used for RAR transmission is group of subcounter.*SSB*. -- d) Each measurement is an integer value representing the number of the transmitted RAR for preambles of group A. -- e) OR.RACH.TxRarPreambleGroupA.*SSB* where *SSB* is the SSB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellIDU -- g) Packet Switched -- h) 5GS - -- i) Network Operator's Traffic Engineering Community - -#### A.4.9.4 Transmitted RARs for dedicated preamble - -- a) This counter provides the number of the transmitted RAR for dedicated preambles. -This is recommended to support for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RAR for dedicated preamble is transmitted when the SSB which is used for RAR transmission is group of subcounter.*SSB*. -- d) Each measurement is an integer value representing the number of the transmitted RAR for dedicated preambles. -- e) OR.RACH.TxRarDedicatedPreamble.*SSB* where *SSB* is the SSB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.9.5 Failures at assignment of dedicated preamble - -- a) This counter provides the number indicating use of random preamble due to NG of dedicated preamble delivery. -This is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RA procedure using random preamble is triggered due to NG of dedicated preamble assignment when the SSB which is used for random preamble transmission is group of subcounter.*SSB*. -- d) Each measurement is an integer value representing the number indicating use of random preamble due to NG of dedicated preamble delivery. -- e) OR.RACH.FailAssignmentDedicatedPreamble.*SSB* where *SSB* is the SSB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.9.6 Occasions for dedicated preamble reception - -- a) This counter provides the number of the occasions for dedicated preamble. If multiple dedicated preambles are assigned, this counter calculated as the number of assigned preambles. - -This is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by the number of assigned preambles whenever dedicated preamble(s) are expected to be received when the SSB which is used for random preamble transmission is group of subcounter.*SSB*. -- d) Each measurement is an integer value representing the number of the occasions for dedicated preamble. -- e) OR.RACH.OccasionDedicatedPreambleRx.*SSB* where *SSB* is the SSB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.9.7 Failures at assignment of a dedicated preamble for PDCCH order RA (UL out-of-sync) - -- a) This counter provides the number of failures at assignment of a dedicated preamble when the gNB detects UL out-of-sync and tries CFRA operation (PDCCH order) to recover UL link connection. - -This is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever a failure at assignment of a dedicated preamble is occurred due to UL out-of-sync when the SSB used for assignment of a dedicated preamble is group of subcounter.*SSB*. -- d) Each measurement is an integer value representing the number of failures at assignment of a dedicated preamble when the gNB detects UL out-of-sync and tries CFRA operation (PDCCH order) to recover UL link connection. -- e) OR.RACH.FailAssignmentDedicatedPreamblePdcchOrderRaUIOutSync.*SSB* where *SSB* is the SSB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.4.10 NR Timing Advance performance measurements - -#### A.4.10.1 Distribution of NTA value of RAR message - -- a) This counter provides the distributions of RARs with the bin of NTA value described the following. The bin type is selected corresponding to CellSize. - -This is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever RAR is transmitted when the SSB index used for the RAR is group of subcounter.SSB and when the NTA is group of subcounter.binX. -- d) Each measurement is an integer value representing the distributions of RARs with the bin of NTA value. -- e) OR.L1M.DistNtaRarMessage.SSB.binX (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.TA.DistNtaRarMessage.SSB.binX (deprecated, refer to NOTE in REQ-PMeas-MC-5) where - -SSB is the SSB index: -0: #0 -1: #1 - -63: #63 - -binX depends on cellSize below: - -CellSize = *large*: -bin1: $0 \leq N_{TA} < 72765$ -bin2: $72765 \leq N_{TA} < 145530$ - -bin10: $654885 \leq N_{TA}$ - -CellSize = *middle*: -bin1: $0 \leq N_{TA} < 29106$ -bin2: $29106 \leq N_{TA} < 58212$ - -bin10: $261954 \leq N_{TA}$ - -CellSize = *small*: -bin1: $0 \leq N_{TA} < 728$ -bin2: $728 \leq N_{TA} < 1456$ - -bin10: $6552 \leq N_{TA}$ - -CellSize = *Very small*: -Reserved - -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.4.11 NR Cell Utilization performance measurements - -#### A.4.11.1 Slots at which PDCCH resource shortage occurred - -- a) This counter provides the number of the slots when PDCCH shortage occurred. -This is recommended to support for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 at every slot in which CCE resource shortage restricts the multiplexing number of PDCCH at least once. -- d) Each measurement is an integer value representing the number of the slots when PDCCH shortage occurred. -- e) OR.RRU.SlotPdcchResourceShortageOccurred (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellIU.SlotPdcchResourceShortageOccurred (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.2 Cancelled DCI due to PDCCH resource shortage - -- a) This counter provides the number of the cancels of DCI transmission due to PDCCH resource shortage. -This is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by the number of DCI which is canceled due to CCE resource shortage whenever CCE resource shortage restricts the multiplexing number of PDCCH. -- d) Each measurement is an integer value representing the number of the cancels of DCI transmission due to PDCCH resource shortage. -- e) OR.RRU.CancelDciPdcchResourceShortage (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellIU.CancelDciPdcchResourceShortage (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.3 Maximum UEs buffering UL and DL data - -- a) This counter obtains the number of UEs buffering both UL and DL data. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). -This is optional counter for O-DU. -- b) CC - -- c) The measurement is obtained by reporting the maximum observed value of the UEs buffering both UL and DL data during the granularity period. - -NOTE: multiple 5QIs can be set per UE, each 5QI is counted per QoS flow. - -- d) Each measurement is an integer value representing the maximum UEs buffering UL and DL data. -- e) The measurement name has the form OR.DRB.MaxUeBufferUIDIData or OR.DRB.MaxUeBufferUIDIData\_*Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellIU.MaxUeBufferUIDIData or OR.CellIU.MaxUeBufferUIDIData\_*Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level. Where QoS represents the mapped 5QI or QCI level. -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.4 Maximum UEs buffering UL data - -- a) This counter obtains the maximum number of UEs buffering UL data. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -This is optional counter for O-DU. - -- b) CC - - c) The measurement is obtained by reporting the maximum observed value of the UEs buffering UL data during the granularity period. -- NOTE: multiple 5QIs can be set per UE, each 5QI is counted per QoS flow. -- d) Each measurement is an integer value representing the maximum UEs buffering UL data. - - e) The measurement name has the form OR.DRB.MaxUeBufferUIData or OR.DRB.MaxUeBufferUIData\_*Filter*. (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellIU.MaxUeBufferUIData or OR.CellIU.MaxUeBufferUIData\_*Filter*. (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level. Where QoS represents the mapped 5QI or QCI level. - - f) NRCellIDU - - g) Packet Switched - - h) 5GS - - i) Network Operator's Traffic Engineering Community - -#### A.4.11.5 Maximum UEs buffering DL data - -- a) This counter obtains the maximum number of UEs buffering DL data. The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). - -This is optional counter for O-DU. - -- b) CC - -- c) The measurement is obtained by reporting the maximum observed value of the UEs buffering DL data during the granularity period. - - NOTE: multiple 5QIs can be set per UE, each 5QI is counted per QoS flow. -- d) Each measurement is an integer value representing the maximum UEs buffering DL data. -- e) The measurement name has the form OR.DRB.MaxUeBufferDIData or OR.DRB.MaxUeBufferDIData\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellU.MaxUeBufferDIData or OR.CellU.MaxUeBufferDIData\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is a QoS level. Where QoS represents the mapped 5QI or QCI level. -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.6 Multiplexed receptions of PUSCH - -- a) This counter provides the accumulated number of the multiplication number of PUSCH. - - This is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 at every slot in which PUSCH is received when the multiplexed number in frequency domain is group of subcounter.*mux*. -- d) Each measurement is an integer value representing the accumulated number of the multiplication number of PUSCH. -- e) OR.CARR.MultiplexRxPusch.*mux* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellU.MultiplexRxPusch.*mux* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *mux* is the number of multiplex: - - 0: 1 multiplex - - 1: 2 multiplex to 5 multiplex - - 2: 6 multiplex to 12 multiplex - - 3: more than 12 multiplex -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.7 Multiplexed transmissions of PDSCH - -- a) This counter provides the accumulated number of the multiplication number of PDSCH. - - This is optional counter for O-DU. -- b) CC - -- c) Measurement subcounter is incremented by 1 when PDSCH is transmitted when the multiplexed number in frequency domain is group of subcounter.*mux*. -- d) Each measurement is an integer value representing the accumulated number of the multiplication number of PDSCH. -- e) OR.CARR.MultiplexTxPdsch.*mux* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellU.MultiplexTxPdsch.*mux* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *mux* is the number of multiplex: - - 0: 1 multiplex - - 1: 2 multiplex to 5 multiplex - - 2: 6 multiplex to 12 multiplex - - 3: more than 12 multiplex -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.8 Maximum DRX inactive UEs - -- a) This counter obtains the maximum number of UEs configured as DRX inactive. -This is optional counter for O-DU. -- b) CC -- c) This measurement represents the number of UEs of which *drx-InactivityTimer* is assumed to be running. The measurement is obtained by reporting the maximum observed value of the UEs configured as DRX inactive during the granularity period. -- d) Each measurement is an integer value representing the maximum DRX inactive UEs. -- e) OR.UECNTX.MaxDrxInactiveUe (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellU.MaxDrxInactiveUe (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.9 Maximum DRX active UEs - -- a) This counter obtains the maximum number of UEs configured as DRX active. -This is optional counter for O-DU. -- b) CC -- c) This measurement represents the number of UEs which is configured *drx-config* and of which *drx-InactivityTimer* is assumed not to be running. The measurement is obtained by reporting the maximum observed value of the UEs configured as DRX active during the granularity period. - -- d) Each measurement is an integer value representing the maximum DRX active UEs. -- e) OR.UECNTX.MaxDrxActiveUe (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellU.MaxDrxActiveUe (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.10 Distribution of trafficInactivityTimer - -- a) This counter provides the distribution of the UEs whose trafficInactivityTimer is running with 1 s bin of the trafficInactivityTimer. trafficInactivityTimer measures the consecutive time when no UL/DL data for the UE is available. This counter obtains the number of UEs every granularity period. - -This is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by the number of UEs whose trafficInactivityTimer is in the value of the subcounter.*binX*. - -The number is acquired as an instantaneous value after each granularity period. - -- d) Each measurement is an integer value representing the distribution of the UEs whose trafficInactivityTimer is running with 1 s bin of the trafficInactivityTimer. -- e) OR.UECNTX.DistTrafficInactiveTimer.*binX* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellU.DistTrafficInactiveTimer.*binX* (deprecated, refer to NOTE in REQ-PMeas-MC-5) where - -bin 1: $0 \text{ s} \leq \text{trafficInactivityTimer} < 1 \text{ s}$ -bin 2: $1 \text{ s} \leq \text{trafficInactivityTimer} < 2 \text{ s}$ -bin 3: $2 \text{ s} \leq \text{trafficInactivityTimer} < 4 \text{ s}$ -bin 4: $4 \text{ s} \leq \text{trafficInactivityTimer} < 8 \text{ s}$ -bin 5: $8 \text{ s} \leq \text{trafficInactivityTimer} < 16 \text{ s}$ -bin 6: $16 \text{ s} \leq \text{trafficInactivityTimer} < 32 \text{ s}$ -bin 7: $32 \text{ s} \leq \text{trafficInactivityTimer} < 64 \text{ s}$ -bin 8: $64 \text{ s} \leq \text{trafficInactivityTimer} < 128 \text{ s}$ -bin 9: $128 \text{ s} \leq \text{trafficInactivityTimer}$ - -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.11 Slots in which scheduler assigned as mini slot - -- a) This counter provides the number of slots with mini slot scheduling. This counter is for FR2. - -This is optional counter for O-DU. - -- b) CC - -- c) Measurement subcounter is incremented by 1 at every slot in which PDSCH which is multiplexed in time domain in a slot is assigned. -- d) Each measurement is an integer value representing the number of slots with mini slot scheduling. This counter is for FR2. -- e) OR.RRU.SlotSchedulerAssignMiniSlot (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellIU.SlotSchedulerAssignMiniSlot (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.12 Mini slots in which PUSCH was received - -- a) This counter provides the number of mini slots when PUSCH is received. - -This is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 when PUSCH which is multiplexed in time domain in a slot is assigned. -- d) Each measurement is an integer value representing the number of mini slots when PUSCH is received. -- e) OR.RRU.MiniSlotsPuschRx (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellIU.MiniSlotsPuschRx (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.13 UEs in the cell using this cell as PSCell or having activated SCell in DL - -- a) This counter provides the accumulated number of the UEs in the cell using this cell as PSCell or having activated SCell in DL. - -This is optional counter for O-DU. -- b) CC -- c) The measurement is obtained by reporting the accumulated observed value of the UEs in the cell using this cell as PSCell or having activated SCell in DL during the granularity period. -- d) Each measurement is an integer value representing the accumulated number of the UEs in the cell using this cell as PSCell or having activated SCell in DL. -- e) OR.UECNTX.UeCellPscellActiveScellIdI (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellIU.UeCellPscellActiveScellIdI (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellDU -- g) Packet Switched - -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.14 UEs in the cell using this cell as PSCell or having activated SCell in UL - -- a) This counter provides the accumulated number of the UEs in the cell using this cell as PSCell or having activated SCell in UL. -This is optional counter for O-DU. -- b) CC -- c) The measurement is obtained by reporting the accumulated observed value of the UEs in the cell using this cell as PSCell or having activated SCell in UL during the granularity period. -- d) Each measurement is an integer value representing the accumulated number of the UEs in the cell using this cell as PSCell or having activated SCell in UL. -- e) OR.UECNTX.UeCellPscellActiveScellUI (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellIU.UeCellPscellActiveScellUI (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.15 Distribution of PSCell UEs with X activated SCells in UL - -- a) This counter provides the distribution of the PSCell UE with the number of activated SCell in UL. -This is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by the number of the UE configured this cell as PSCell per the number of activated SCell in UL: 1 active SCell,, 2 active SCell, ..., 31 active SCell as subcounter.*SCell*. -The measurement is obtained by calculating the observed distribution of PSCell UEs with X activated SCells in UL per granularity period. -- d) Each measurement is an integer value representing the distribution of the PSCell UE with the number of activated SCell in UL. -- e) OR.UECNTX.DistPscellUeXactiveScellUI.NumScell (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellIU.DistPscellUeXactiveScellUI.NumScell (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *NumScell* is the number of active SCell: - - 0: 1 active SCell - - 1: 2 active SCell - - ... - - 30: 31 active SCell -- f) NRCellDU -- g) Packet Switched - -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.16 Distribution of PSCell UEs with X activated SCells in DL - -- a) This counter provides the distribution of the PSCell UEs with the number of activated SCell in DL. - -This is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by the number of the UE configured this cell as PSCell per the number of activated SCell in DL: 1 active SCell,, 2 active SCell, ..., 31 active SCell as subcounter.*SCell*. - -The measurement is obtained by calculating the observed distribution of PSCell UEs with X activated SCells in DL per granularity period. - -- d) Each measurement is an integer value representing the distribution of the PSCell UEs with the number of activated SCell in DL. -- e) OR.UECNTX.DistPscellUeXactiveScellDL.NumScell (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellU.DistPscellUeXactiveScellDL.NumScell (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *NumScell* is the number of active SCell: - - 0: 1 active SCell - - 1: 2 active SCell - - ... - - 30: 31 active SCell -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.17 Maximum amount of PSCell UEs (UL) - -- a) This counter obtains the maximum number of the PSCell UEs for UL. - -This is optional counter for O-DU. - -- b) CC -- c) The measurement is obtained by reporting the maximum observed value PSCell UEs for UL during the granularity period. -- d) Each measurement is an integer value representing the maximum amount of PSCell UEs (UL). -- e) OR.UECNTX.MaxPscellUeUL.NumScell (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellU.MaxPscellUeUL.NumScell (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *NumScell* is the number of active SCell: - - 0: 1 active SCell - - 1: 2 active SCell - - ... - - 30: 31 active SCell - -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.18 Minimum amount of PSCell UEs (UL) - -- a) This counter obtains the minimum number of the PSCell UEs for UL. -This is optional counter for O-DU. -- b) CC -- c) The measurement is obtained by reporting the minimum observed value PSCell UEs for UL during the granularity period. -- d) Each measurement is an integer value representing the minimum amount of PSCell UEs (UL). -- e) OR.UECNTX.MinPscellUeUl.NumScell (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellU.MinPscellUeUl.NumScell (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *NumScell* is the number of active SCell: - - 0: 1 active SCell - - 1: 2 active SCell - - ... - - 30: 31 active SCell -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.19 Maximum amount of PSCell UEs (DL) - -- a) This counter obtains the maximum number of the PSCell UEs for DL. -This is optional counter for O-DU. -- b) CC -- c) The measurement is obtained by reporting the maximum observed value PSCell UEs for DL during the granularity period. -- d) Each measurement is an integer value representing the maximum amount of PSCell UEs (DL). -- e) OR.UECNTX.MaxPscellUeDl.NumScell (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellU.MaxPscellUeDl.NumScell (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *NumScell* is the number of active SCell: - - 0: 1 active SCell - - 1: 2 active SCell - - ... - - 30: 31 active SCell - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.20 Minimum amount of PSCell UEs (DL) - -- a) This counter obtains the minimum number of the PSCell UEs for DL. -This is optional counter for O-DU. -- b) CC -- c) The measurement is obtained by reporting the minimum observed value PSCell UEs for DL during the granularity period. -- d) Each measurement is an integer value representing the minimum amount of PSCell UEs (DL). -- e) OR.UECNTX.MinPscellUeDl.NumScell (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellU.MinPscellUeDl.NumScell (deprecated, refer to NOTE in REQ-PMeas-MC-5) where *NumScell* is the number of active SCell: - - 0: 1 active SCell - - 1: 2 active SCell - - ... - - 30: 31 active SCell -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.21 Activation/Deactivation MAC CE (SCell Active) - -- a) This counter provides the number of the Activation/Deactivation MAC CEs transmitted for SCell activation. -This is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is the incremented by 1 whenever Activation/Deactivatoin MAC CEs is transmitted for SCell activation. -- d) Each measurement is an integer value representing the number of the Activation/Deactivation MAC CEs transmitted for SCell activation. -- e) OR.CARR.ActDeactMacCeScellAct (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellU.ActDeactMacCeScellAct (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellIDU -- g) Packet Switched -- h) 5GS - -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.22 Activation/Deactivation MAC CE (SCell Deactive) - -- a) This counter provides the number of the Activation/Deactivation MAC CEs transmitted for SCell deactivation. If Activation/Deactivation MAC CE isn't transmitted when sCellDeactivationTimer expires, this counter includes the number of sCellDeactivationTimer expiry. -This is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is the incremented by 1 whenever Activation/Deactivatoin MAC CEs is transmitted for SCell deactivation or whenever sCellDeactivationTimer managed at O-DU expires. -- d) Each measurement is an integer value representing the number of the Activation/Deactivation MAC CEs transmitted for SCell deactivation. -- e) OR.CARR.ActDeactMacCeScellDeact (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellIU.ActDeactMacCeScellDeact (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.23 Distribution of DL Total PRB Usage - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.3 - -###### O-RAN addition: - -Averaging is done over a time period $t_n$ (e.g: 1s). - -- bin 1: $0 \% \leq \text{PRB usage} < 5 \%$ -- bin 2: $5 \% \leq \text{PRB usage} < 10 \%$ -- bin 3: $10 \% \leq \text{PRB usage} < 15 \%$ -- bin 4: $15 \% \leq \text{PRB usage} < 20 \%$ -- bin 5: $20 \% \leq \text{PRB usage} < 25 \%$ -- bin 6: $25 \% \leq \text{PRB usage} < 30 \%$ -- bin 7: $30 \% \leq \text{PRB usage} < 35 \%$ -- bin 8: $35 \% \leq \text{PRB usage} < 40 \%$ -- bin 9: $40 \% \leq \text{PRB usage} < 45 \%$ -- bin 10: $45 \% \leq \text{PRB usage} < 50 \%$ -- bin 11: $50 \% \leq \text{PRB usage} < 55 \%$ -- bin 12: $55 \% \leq \text{PRB usage} < 60 \%$ -- bin 13: $60 \% \leq \text{PRB usage} < 65 \%$ -- bin 14: $65 \% \leq \text{PRB usage} < 70 \%$ -- bin 15: $70 \% \leq \text{PRB usage} < 75 \%$ -- bin 16: $75 \% \leq \text{PRB usage} < 80 \%$ -- bin 17: $80 \% \leq \text{PRB usage} < 85 \%$ -- bin 18: $85 \% \leq \text{PRB usage} < 90 \%$ -- bin 19: $90 \% \leq \text{PRB usage} < 95 \%$ -- bin 20: $95 \% \leq \text{PRB usage} < 100 \%$ - -This is recommended to support for O-DU. - -The counter is split into subcounters per S-NSSAI. The counter is recommended when related slice feature is supported. - -b) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.3 - -c) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.3 - -###### O-RAN addition: - -Averaging is done over a time period $t_n$ (e.g: 1s) and the bin defined in description should be used. - -If S-NSSAI subcounter is maintained, the number of measurements is accumulated per the number of supported S-NSSAI. - -d) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.3 - -e) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.3 - -###### O-RAN addition: - -Subcounter - -OR.RRU.PrbTotDlDist.BinX.*SNSSAI*, where *SNSSAI* identifies the S-NSSAI. - -f) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.3 - -g) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.3 - -h) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.3 - -i) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.3 - -#### A.4.11.24 Distribution of UL Total PRB Usage - -a) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.4 - -###### O-RAN addition: - -Averaging is done over a time period $t_n$ (e.g: 1s). - -bin 1: $0 \% \leq \text{PRB usage} < 5 \%$ -bin 2: $5 \% \leq \text{PRB usage} < 10 \%$ -bin 3: $10 \% \leq \text{PRB usage} < 15 \%$ -bin 4: $15 \% \leq \text{PRB usage} < 20 \%$ -bin 5: $20 \% \leq \text{PRB usage} < 25 \%$ -bm 6: $25 \% \leq \text{PRB usage} < 30 \%$ -bin 7: $30 \% \leq \text{PRB usage} < 35 \%$ -bin 8: $35 \% \leq \text{PRB usage} < 40 \%$ -bin 9: $40 \% \leq \text{PRB usage} < 45 \%$ -bin 10: $45 \% \leq \text{PRB usage} < 50 \%$ -bin 11: $50 \% \leq \text{PRB usage} < 55 \%$ -bin 12: $55 \% \leq \text{PRB usage} < 60 \%$ -bin 13: $60 \% \leq \text{PRB usage} < 65 \%$ -bin 14: $65 \% \leq \text{PRB usage} < 70 \%$ -bin 15: $70 \% \leq \text{PRB usage} < 75 \%$ -bin 16: $75 \% \leq \text{PRB usage} < 80 \%$ -bin 17: $80 \% \leq \text{PRB usage} < 85 \%$ -bin 18: $85 \% \leq \text{PRB usage} < 90 \%$ -bin 19: $90 \% \leq \text{PRB usage} < 95 \%$ -bin 20: $95 \% \leq \text{PRB usage} < 100 \%$ - -This is recommended to support for O-DU. - -The counter is split into subcounters per S-NSSAI. The counter is recommended when related slice feature is supported. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.4 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.4 - -###### O-RAN addition: - -Averaging is done over a time period $t_n$ (e.g. 1s) and the bin defined in description should be used. - -If S-NSSAI subcounter is maintained, the number of measurements is accumulated per the number of supported S-NSSAI. - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.4 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.4 - -###### O-RAN addition: - -Subcounter - -OR.RRU.PrbTotUIDist.BinX.SNSSAI, where SNSSAI identifies the S-NSSAI. - -- f) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.4 -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.4 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.4 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.1.2.4 - -#### A.4.11.25 Average DL Cell throughput - -- a) This counter provides the Average DL Cell throughput of MAC. This counter is obtained by accumulating the MAC level volume of a data, and then dividing by the scheduled time per cell. The measurement is performed at the MAC level. This measurement can be split into subcounters per supported S-NSSAI. - -This is optional counter for O-DU. - -The counter is split into subcounters per S-NSSAI. The counter is recommended when related slice feature is supported. - -- b) SI -- c) Measurement subcounter is calculated by $x/y$ . - -$x$ is incremented by the volume of DL MAC PDU whenever the successfully delivery of DL MAC PDU is confirmed. - -$y$ is incremented by the transmission period (e.g. 0.5ms or 0.125ms) for the PDU whenever DL MAC PDU is transmitted (i.e. including HARQ retransmission) . - -If S-NSSAI subcounter is maintained, the number of measurements is accumulated per the number of supported S-NSSAI. - -- d) Each measurement is an integer value representing the Average DL Cell throughput of MAC in kbps. -- e) OR.DRB.AveDICellThroughput or OR.DRB.AveDICellThroughput.SNSSAI (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellIU.AveDICellThroughput or OR.CellIU.AveDICellThroughput.SNSSAI (deprecated, refer to NOTE in REQ-PMeas-MC-5), where SNSSAI identifies the S-NSSAI. -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.26 Average UL Cell throughput - -- a) This counter provides the Average UL Cell throughput of MAC. This counter is obtained by accumulating the MAC level volume of a data, and then dividing by the scheduled time per cell. The measurement is performed at the MAC level. This measurement can be split into subcounters per S-NSSAI. - -This is optional counter for O-DU. - -The counter is split into subcounters per S-NSSAI. The counter is recommended when related slice feature is supported. - -- b) SI -- c) Measurement subcounter is calculated by $x/y$ . - - -$x$ is incremented by the volume of UL MAC PDU whenever UL MAC PDU is successfully received. - -$y$ is incremented by the transmission period whenever the UL MAC PDU is received (i.e. including HARQ retransmission). - -If S-NSSAI subcounter is maintained, the number of measurements is accumulated per the number of supported S-NSSAI. -- d) Each measurement is an integer value representing the Average UL Cell throughput of MAC in kbps. -- e) OR.DRB.AveUICellThroughput or OR.DRB.AveUICellThroughput.SNSSAI (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellU.AveUICellThroughput or OR.CellU.AveUICellThroughput.SNSSAI (deprecated, refer to NOTE in REQ-PMeas-MC-5), where SNSSAI identifies the S-NSSAI. -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.27 Average DL Beam throughput - -- a) This counter provides the Average DL Beam throughput of MAC. This counter is obtained by accumulating the MAC level volume of a data, and then dividing by the scheduled time per SSB index. The measurement is performed at the MAC level. - - -This is optional counter for O-DU. -- b) SI -- c) Measurement subcounter is calculated by $x/y$ . - - -$x$ is incremented by the volume of DL MAC PDU whenever DL MAC PDU is confirmed the successfully delivery when the SSB used for PDSCH is the group of subcounter.SSB. - -$y$ is incremented by the transmission period whenever the DL MAC PDU is transmitted (i.e. including HARQ retransmission) when the SSB used for PDSCH is the group of subcounter.SSB.. -- d) Each measurement is an integer value representing the Average DL Beam throughput of MAC in kbps. -- e) OR.DRB.AveDIBeamThroughput.SSB (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellU.AveDIBeamThroughput.SSB (deprecated, refer to NOTE in REQ-PMeas-MC-5) where SSB is the SSB index: - -0: #0 -1: #1 -... -63: #63 - -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.28 Average UL Beam throughput - -- a) This counter provides the Average UL Beam throughput of MAC. This counter is obtained by accumulating the MAC level volume of a data, and then dividing by the scheduled time per SSB index. The measurement is performed at the MAC level. - -This is optional counter for O-DU. - -- b) SI -- c) Measurement subcounter is calculated by x/y. - -x is incremented by the volume of UL MAC PDU whenever UL MAC PDU is successfully received when the SSB used for PUSCH is the group of subcounter.SSB. - -y is incremented by the transmission period whenever the UL MAC PDU is received (i.e. including HARQ retransmission) when the SSB used for PUSCH is the group of subcounter.SSB. -- d) Each measurement is an integer value representing the Average UL Beam throughput of MAC in kbps. -- e) OR.DRB.AveUlBeamThroughput.SSB (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellIU.AveUlBeamThroughput.SSB (deprecated, refer to NOTE in REQ-PMeas-MC-5) where SSB is the SSB index: - - 0: #0 - - 1: #1 - - ... - - 63: #63 -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.29 Average DL active DRB - -- a) This counter provides the average number of DL active DRB. This counter is obtained by averaging the number of the active DRB which has data in MAC/RLC buffer during measurement time per cell. - -This is optional counter for O-DU. - -- b) SI -- c) The measurement is obtained by reporting the average observed value of DL active DRB during the granularity period. - -- d) Each measurement is an integer value representing the average number of DL active DRB. -- e) OR.DRB.AveDIActDrb (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellU.AveDIActDrb (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.30 Maximum DL active DRB - -- a) This counter provides the maximum number of DL active DRB. This counter is obtained by providing the maximum number of the active DRB which has data in MAC/RLC buffer during measurement time per cell. -This is optional counter for O-DU. -- b) SI -- c) The measurement is obtained by reporting the maximum observed value of DL active DRB during the granularity period. -- d) Each measurement is an integer value representing the maximum number of DL active DRB. -- e) OR.DRB.MaxDIActDrb (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellU.MaxDIActDrb (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.31 Void - -#### A.4.11.32 Void - -#### A.4.11.33 Distribution of UL UE throughput in gNB - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.4 - -###### O-RAN addition: - -The reference measurement time T for calculating the throughput of each UE is 1000ms. - -The bins corresponding to the UL throughput experienced by the UE is defined as follow. - -bin 1: $0 \leq \text{UL UE throughput} < 0.05 \times \text{Throughput}$ - -bin 2: $0.05 \times \text{Throughput} \leq \text{UL UE throughput} < 0.1 \times \text{Throughput}$ - -bin 3: $0.1 \times \text{Throughput} \leq \text{UL UE throughput} < 0.15 \times \text{Throughput}$ - -bin 4: $0.15 \times \text{Throughput} \leq \text{UL UE throughput} < 0.2 \times \text{Throughput}$ - -bin 5: $0.2 \times \text{Throughput} \leq \text{UL UE throughput} < 0.25 \times \text{Throughput}$ - bin 6: $0.25 \times \text{Throughput} \leq \text{UL UE throughput} < 0.3 \times \text{Throughput}$ - bin 7: $0.3 \times \text{Throughput} \leq \text{UL UE throughput} < 0.35 \times \text{Throughput}$ - bin 8: $0.35 \times \text{Throughput} \leq \text{UL UE throughput} < 0.4 \times \text{Throughput}$ - bin 9: $0.4 \times \text{Throughput} \leq \text{UL UE throughput} < 0.45 \times \text{Throughput}$ - bin 10: $0.45 \times \text{Throughput} \leq \text{UL UE throughput} < 0.5 \times \text{Throughput}$ - bin 11: $0.5 \times \text{Throughput} \leq \text{UL UE throughput} < 0.55 \times \text{Throughput}$ - bin 12: $0.55 \times \text{Throughput} \leq \text{UL UE throughput} < 0.6 \times \text{Throughput}$ - bin 13: $0.6 \times \text{Throughput} \leq \text{UL UE throughput} < 0.65 \times \text{Throughput}$ - bin 14: $0.65 \times \text{Throughput} \leq \text{UL UE throughput} < 0.7 \times \text{Throughput}$ - bin 15: $0.7 \times \text{Throughput} \leq \text{UL UE throughput} < 0.75 \times \text{Throughput}$ - bin 16: $0.75 \times \text{Throughput} \leq \text{UL UE throughput} < 0.8 \times \text{Throughput}$ - bin 17: $0.8 \times \text{Throughput} \leq \text{UL UE throughput} < 0.85 \times \text{Throughput}$ - bin 18: $0.85 \times \text{Throughput} \leq \text{UL UE throughput} < 0.9 \times \text{Throughput}$ - bin 19: $0.9 \times \text{Throughput} \leq \text{UL UE throughput} < 0.95 \times \text{Throughput}$ - bin 20: $0.95 \times \text{Throughput} \leq \text{UL UE throughput} < \text{Throughput}$ - -\*Throughput is a predefined value in the implementation - -The measurement is optionally calculated per S-NSSAI, per QoS level (mapped 5QI or QCI in EN-DC) and PLMN ID, according to 3GPP TS 28.552 [2] clause 5.1.1.3.4. - -This is recommended to support for O-DU. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.4 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.4 - -###### O-RAN addition: - -The per UE throughput is calculated by the following formula. And the bin defined in description should be used. - -$$\begin{aligned} - &\text{If } \sum \text{ThpTimeUl} > 0, \frac{\sum \text{ThpVolUl}}{\sum \text{ThpTimeUl}} \times 1000 [\text{kbits/s}] \\ - &\text{If } \sum \text{ThpTimeUl} = 0, 0 [\text{kbit/s}] - \end{aligned}$$ - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.4 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.4 - -###### O-RAN addition: - -The measurement name has the form OR.DRB.UETHpUIDist.Bin or OR.DRB.UETHpUIDist.Bin\_Filter. Where *Filter* is a combination of PLMN, QoS level and SNSSAI. Where PLMN represents the PLMN ID, QoS represents the mapped 5QI or QCI level, and SNSSAI represents S-NSSAI. - -- f) gNBDUFunction -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.4 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.4 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.4 - -#### A.4.11.34 Distribution of DL UE throughput in gNB - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.2 - -###### O-RAN addition: - -The reference measurement time T for calculating the throughput of each UE is 1000ms. - -The bins corresponding to the DL throughput experienced by the UE is defined as follow. - -bin 1: $0 \leq \text{DL UE throughput} < 0.05 \times \text{Throughput}$ - -bin 2: $0.05 \times \text{Throughput} \leq \text{DL UE throughput} < 0.1 \times \text{Throughput}$ - -bin 3: $0.1 \times \text{Throughput} \leq \text{DL UE throughput} < 0.15 \times \text{Throughput}$ - -bin 4: $0.15 \times \text{Throughput} \leq \text{DL UE throughput} < 0.2 \times \text{Throughput}$ - -bin 5: $0.2 \times \text{Throughput} \leq \text{DL UE throughput} < 0.25 \times \text{Throughput}$ - -bin 6: $0.25 \times \text{Throughput} \leq \text{DL UE throughput} < 0.3 \times \text{Throughput}$ - -bin 7: $0.3 \times \text{Throughput} \leq \text{DL UE throughput} < 0.35 \times \text{Throughput}$ - -bin 8: $0.35 \times \text{Throughput} \leq \text{DL UE throughput} < 0.4 \times \text{Throughput}$ - -bin 9: $0.4 \times \text{Throughput} \leq \text{DL UE throughput} < 0.45 \times \text{Throughput}$ - -bin 10: $0.45 \times \text{Throughput} \leq \text{DL UE throughput} < 0.5 \times \text{Throughput}$ - -bin 11: $0.5 \times \text{Throughput} \leq \text{DL UE throughput} < 0.55 \times \text{Throughput}$ - -bin 12: $0.55 \times \text{Throughput} \leq \text{DL UE throughput} < 0.6 \times \text{Throughput}$ - -bin 13: $0.6 \times \text{Throughput} \leq \text{DL UE throughput} < 0.65 \times \text{Throughput}$ - -bin 14: $0.65 \times \text{Throughput} \leq \text{DL UE throughput} < 0.7 \times \text{Throughput}$ - -bin 15: $0.7 \times \text{Throughput} \leq \text{DL UE throughput} < 0.75 \times \text{Throughput}$ - -bin 16: $0.75 \times \text{Throughput} \leq \text{DL UE throughput} < 0.8 \times \text{Throughput}$ - -bin 17: $0.8 \times \text{Throughput} \leq \text{DL UE throughput} < 0.85 \times \text{Throughput}$ - -bin 18: $0.85 \times \text{Throughput} \leq \text{DL UE throughput} < 0.9 \times \text{Throughput}$ - -bin 19: $0.9 \times \text{Throughput} \leq \text{DL UE throughput} < 0.95 \times \text{Throughput}$ - -bin 20: $0.95 \times \text{Throughput} \leq \text{DL UE throughput} < \text{Throughput}$ - -\*Throughput is a predefined value in the implementation - -The measurement is optionally calculated per S-NSSAI, per QoS level (mapped 5QI or QCI in EN-DC) and PLMN ID, according to 3GPP TS 28.552 [2] clause 5.1.1.3.2. - -This is recommended to support for O-DU. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.2 - -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.2 - -###### O-RAN addition: - -The per UE throughput is calculated by the following formula. And the bin defined in description should be used. - -$$\text{If } \sum \text{ThpTimeDL} > 0, \frac{\sum \text{ThpVolDL}}{\sum \text{ThpTimeDL}} \times 1000 [\text{kbits/s}]$$ - -$$\text{If } \sum \text{ThpTimeDL} = 0, 0 [\text{kbit/s}]$$ - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.2 - -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.2 - -###### O-RAN addition: - -The measurement name has the form OR.DRB.UETHpDIDist.Bin or OR.DRB.UETHpDIDist.Bin\_Filter. Where *Filter* is a combination of PLMN, QoS level and SNSSAI. Where PLMN represents the PLMN ID, QoS represents the mapped 5QI or QCI level, and SNSSAI represents S-NSSAI. - -- f) gNBDFUFunction -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.2 -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.2 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.2 - -#### A.4.11.35 Distribution of DL packet drop rate - -- a) This measurement provides distribution of UE's fraction of RLC SDU packets which are dropped on the downlink, due to high traffic load, traffic management etc, in the gNB-DU. Only user-plane traffic (DTCH) is considered. A dropped packet is one who context is removed from the gNB-DU without any part of it having been transmitted on the air interface. - -The measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC) and per S-NSSAI. The filter is recommended when related slice feature is supported. - -The reference measurement time T for calculating the packet drop rate of each UE is 1000ms. - -The bins corresponding to the DL packet drop rate experienced by the UE is defined as follow. - -bin 1: $0 \leq \text{DL Packet drop rate} < 5$ -bin 2: $5 \leq \text{DL Packet drop rate} < 10$ -bin 3: $10 \leq \text{DL Packet drop rate} < 15$ -bin 4: $15 \leq \text{DL Packet drop rate} < 20$ -bin 5: $20 \leq \text{DL Packet drop rate} < 25$ -bin 6: $25 \leq \text{DL Packet drop rate} < 30$ -bin 7: $30 \leq \text{DL Packet drop rate} < 35$ -bin 8: $35 \leq \text{DL Packet drop rate} < 40$ -bin 9: $40 \leq \text{DL Packet drop rate} < 45$ -bin 10: $45 \leq \text{DL Packet drop rate} < 50$ -bin 11: $50 \leq \text{DL Packet drop rate} < 55$ -bin 12: $55 \leq \text{DL Packet drop rate} < 60$ -bin 13: $60 \leq \text{DL Packet drop rate} < 65$ -bin 14: $65 \leq \text{DL Packet drop rate} < 70$ -bin 15: $70 \leq \text{DL Packet drop rate} < 75$ -bin 16: $75 \leq \text{DL Packet drop rate} < 80$ -bin 17: $80 \leq \text{DL Packet drop rate} < 85$ -bin 18: $85 \leq \text{DL Packet drop rate} < 90$ -bin 19: $90 \leq \text{DL Packet drop rate} < 95$ -bin 20: $95 \leq \text{DL Packet drop rate}$ - -- b) SI -- c) This measurement is obtained as: $1000000 * \text{Number of DL packets, for which no part has been transmitted over the air, of the data radio bearers for each UE, that are discarded in the gNB-DU divided by Number of DL packets for data radio bearers for each UE that were received from gNB-CU-UP}$ . Then map packet drop rate to the bins according to their value and the thresholds of the bins and then provide an integer value of the number of samples in Bin -Optionally QoS and S-NSSAI filtering is obtained by the number of measurements is accumulated per the number of supported QoS and S-NSSAI. -- d) Each measurement is an integer value representing the distribution of UE's fraction of RLC SDU packets which are dropped on the downlink, due to high traffic load, traffic management etc, in the gNB-DU. - -- e) The measurement name has the form OR.DRB.RlcPacketDropRateDIDist.Bin or OR.DRB.RlcPacketDropRateDIDist.Bin\_*Filter*. Where *Filter* is a combination of QoS level and SNSSAI. Where QoS represents the mapped 5QI or QCI level, and SNSSAI represents S-NSSAI. -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.36 PDCCH for BWP switching - -- a) This measurement provides the total number of PDCCH for BWP switching. This measurement optionally is split into subcounters per BWP ID. -- b) CC -- c) The measurement is incremented by 1 whenever PDCCH for BWP switching is triggered. This measurement shall not count retransmission. - -If the optional BWP ID level subcounter measurements are performed, the number of measurements is equal to the number of BWP IDs to which the target BWP is to be switched. - -- d) Each measurement is an integer value representing the total number of PDCCH for BWP switching. -- e) OR.RRU.PdcchBwpSwitch or optionally OR.RRU.PdcchBwpSwitch.*BWP* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.Cell.PdcchBwpSwitch or optionally OR.Cell.PdcchBwpSwitch.*BWP* (deprecated, refer to NOTE in REQ-PMeas-MC-5), where *BWP* is BWP ID. -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.37 Distribution of Activated BWP ID - -- a) This measurement provides distribution of UEs for activated BWP. The measurement is split into subcounters per active BWP ID. This counter obtains the number of the UEs. -- b) CC -- c) Measurement subcounter is incremented by the number of the UEs per active BWP ID. This measurement shall count UEs configured multiple BWPs and triggered BWP switching by PDCCH. (ex. Energy saving). The number of UEs is acquired as an instantaneous value. - -The measurement is obtained by calculating the observed distribution of UEs for activated BWP ID per granularity period - -- d) Each measurement is an integer value representing the distribution of UEs for activated BWP. -- e) OR.RRU.DistActBwpId.*BWP* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.Cell.DistActBwpId.*BWP* (deprecated, refer to NOTE in REQ-PMeas-MC-5), where *BWP* is BWP ID. -- f) NRCellIDU - -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.38 Non-linear Scale Distribution of UL UE throughput in gNB - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.4 - -###### O-RAN addition: - -The reference measurement time T for calculating the throughput of each UE is 1000ms. - -The bins corresponding to the UL throughput experienced by the UE is defined as follows. - -bin1: 0 kbps <= UL UE Throughput < 100 Kbps -bin2: 100 Kbps <= UL UE Throughput < 200 Kbps -bin3: 200 Kbps <= UL UE Throughput < 500 Kbps -bin4: 500 Kbps <= UL UE Throughput < 1 Mbps -bin5: 1 Mbps <= UL UE Throughput < 2 Mbps -bin6: 2 Mbps <= UL UE Throughput < 5 Mbps -bin7: 5 Mbps <= UL UE Throughput < 10 Mbps -bin8: 10 Mbps <= UL UE Throughput < 20 Mbps -bin9: 20 Mbps <= UL UE Throughput < 40 Mbps -bin10: 40 Mbps <= UL UE Throughput < 60 Mbps -bin11: 60 Mbps <= UL UE Throughput < 80 Mbps -bin12: 80 Mbps <= UL UE Throughput < 100 Mbps -bin13: 100 Mbps <= UL UE Throughput < 200 Mbps -bin14: 200 Mbps <= UL UE Throughput < 400 Mbps -bin15: 400 Mbps <= UL UE Throughput < 600 Mbps -bin16: 600 Mbps <= UL UE Throughput < 800 Mbps -bin17: 800 Mbps <= UL UE Throughput < 1 Gbps -bin18: 1 Gbps <= UL UE Throughput < 2 Gbps -bin19: 2 Gbps <= UL UE Throughput < 5 Gbps -bin20: 5 Gbps <= UL UE Throughput - -The measurement is optionally calculated per S-NSSAI, per QoS level (mapped 5QI or QCI in EN-DC) and PLMN ID, according to 3GPP TS 28.552 [2] clause 5.1.1.3.4. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.4 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.4 - -###### O-RAN addition: - -The per UE throughput is calculated by the following formula. And the bin defined in description should be used. - -$$\text{If } \sum \text{ThpTimeUl} > 0, \frac{\sum \text{ThpVolUl}}{\sum \text{ThpTimeUl}} \times 1000 [\text{kbits/s}]$$ - -$$\text{If } \sum \text{ThpTimeUl} = 0, 0 [\text{kbit/s}]$$ - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.4 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.4 - -###### O-RAN addition: - -The measurement name has the form OR.DRB.UETHpUILogDist.Bin or OR.DRB.UETHpUILogDist.Bin *Filter*. Where *Filter* is a combination of PLMN, QoS level and SNSSAI. Where PLMN represents the PLMN ID, QoS represents the mapped 5QI or QCI level, and SNSSAI represents S-NSSAI. - -- f) gNBDUFunction -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.4 - -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.4 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.4 - -#### A.4.11.39 Non-linear Scale Distribution of DL UE throughput in gNB - -- a) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.2 - -###### O-RAN addition: - -The reference measurement time T for calculating the throughput of each UE is 1000ms. - -The bins corresponding to the DL throughput experienced by the UE is defined as follows. - -bin1: 0 kbps $\leq$ DL UE Throughput $<$ 500 Kbps - -bin2: 500 Kbps $\leq$ DL UE Throughput $<$ 1 Mbps - -bin3: 1 Mbps $\leq$ DL UE Throughput $<$ 5 Mbps - -bin4: 5 Mbps $\leq$ DL UE Throughput $<$ 10 Mbps - -bin5: 10 Mbps $\leq$ DL UE Throughput $<$ 20 Mbps - -bin6: 20 Mbps $\leq$ DL UE Throughput $<$ 40 Mbps - -bin7: 40 Mbps $\leq$ DL UE Throughput $<$ 60 Mbps - -bin8: 60 Mbps $\leq$ DL UE Throughput $<$ 80 Mbps - -bin9: 80 Mbps $\leq$ DL UE Throughput $<$ 100 Mbps - -bin10: 100 Mbps $\leq$ DL UE Throughput $<$ 120 Mbps - -bin11: 120 Mbps $\leq$ DL UE Throughput $<$ 160 Mbps - -bin12: 160 Mbps $\leq$ DL UE Throughput $<$ 200 Mbps - -bin13: 200 Mbps $\leq$ DL UE Throughput $<$ 400 Mbps - -bin14: 400 Mbps $\leq$ DL UE Throughput $<$ 800 Mbps - -bin15: 800 Mbps $\leq$ DL UE Throughput $<$ 1.6 Gbps - -bin16: 1.6 Gbps $\leq$ DL UE Throughput $<$ 2 Gbps - -bin17: 2 Gbps $\leq$ DL UE Throughput $<$ 4 Gbps - -bin18: 4 Gbps $\leq$ DL UE Throughput $<$ 8 Gbps - -bin19: 8 Gbps $\leq$ DL UE Throughput $<$ 16 Gbps - -bin20: 16 Gbps $\leq$ DL UE Throughput - -The measurement is optionally calculated per S-NSSAI, per QoS level (mapped 5QI or QCI in EN-DC) and PLMN ID, according to 3GPP TS 28.552 [2] clause 5.1.1.3.2. - -- b) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.2 -- c) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.2 - -###### O-RAN addition: - -The per UE throughput is calculated by the following formula. And the bin defined in description should be used. - -$$\text{If } \sum \text{ThpTimeDl} > 0, \frac{\sum \text{ThpVolDl}}{\sum \text{ThpTimeDl}} \times 1000 [\text{kbits/s}]$$ - -$$\text{If } \sum \text{ThpTimeDl} = 0, 0 [\text{kbit/s}]$$ - -- d) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.2 -- e) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.2 - -###### O-RAN addition: - -The measurement name has the form OR.DRB.UETHpDILogDist.Bin or OR.DRB.UETHpDILogDist.Bin\_Filter. Where *Filter* is a combination of PLMN, QoS level and SNSSAI. Where PLMN represents the PLMN ID, QoS represents the mapped 5QI or QCI level, and SNSSAI represents S-NSSAI. - -- f) gNBDUFunction -- g) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.2 - -- h) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.2 -- i) Refer to 3GPP TS 28.552 [2] clause 5.1.1.3.2 - -#### A.4.11.40 PUSCH slots - -- a) This counter provides the number of the slots when PUSCH was received. -This is recommended to support for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PUSCH is received. -- d) Each measurement is an integer value representing the number of the slots when PUSCH was received. -- e) OR.RRU.PuschSlot (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellIU.PuschSlot (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.41 PDSCH slots - -- a) This counter provides the number of the slots when PDSCH was transmitted. -This is recommended to support for O-DU. -- b) CC -- c) Measurement subcounter is incremented by 1 whenever PDSCH is transmitted. -- d) Each measurement is an integer value representing the number of the slots when PDSCH was transmitted. -- e) OR.RRU.PdschSlot (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellIU.PdschSlot (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.42 PDCCH slots - -- a) This counter provides the number of the slots when PDCCH was transmitted. -This is optional counter for O-DU. -- b) CC - -- c) Measurement subcounter is incremented by 1 whenever PDCCH is transmitted. -- d) Each measurement is an integer value representing the number of the slots when PDCCH was transmitted. -- e) OR.RRU.PdcchSlot (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellIU.PdcchSlot (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.43 CCE utilization rate - -- a) This counter measures the following $x$ in the report period and provides $\text{round}(x, 2) \cdot 10^2$ . $x$ is the usage rate of CCE. -This is recommended to support for O-DU. -- b) SI -- c) Measurement subcounter is $\text{round}(x/y, 2) \cdot 10^2$ . - $x$ is incremented by the number of CCEs which are used to transmit DCI whenever PDCCH is transmitted. - $y$ is incremented by the number of CCEs which can be used whenever PDCCH is transmitted. -- d) Each measurement is an integer value representing the CCE utilization rate in percentage/ $10^2$ . -- e) OR.RRU.CceUtilizationRate (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellIU.CceUtilizationRate (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.44 UEs buffering UL and DL data - -- a) This counter provides the accumulated number of the UEs buffering both UL and DL data. -This is recommended to support for O-DU. -- b) CC -- c) The measurement is incremented by the number of the UEs which have both UL and DL data and optionally with filter. -The measurement is obtained by reporting the accumulated observed value of the UEs buffering both UL and DL data during the granularity period. -NOTE: multiple 5QIs can be set per UE, each 5QI is counted per QoS flow. -- d) Each measurement is an integer value representing the accumulated number of the UEs buffering both UL and DL data. -- e) The measurement name has the form OR.DRB.UeBufferingUIDIData or OR.DRB.UeBufferingUIDIData\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellIU.UeBufferingUIDIData or - -OR.CellU.UeBufferingUIData *Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is the QoS level. Where QoS represents the mapped 5QI or QCI level. - -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.45 UEs buffering UL data - -- a) This counter provides the accumulated number of the UEs buffering UL data. - -This is recommended to support for O-DU. - -- b) CC - -- c) The measurement is incremented by the number of the Ues, optionally when UL data is the filter. - -The measurement is obtained by reporting the accumulated observed value of the UEs buffering UL data during the granularity period. - -NOTE: multiple 5QIs can be set per UE, each 5QI is counted per QoS flow. - -- d) Each measurement is an integer value representing the accumulated number of the UEs buffering UL data. -- e) The measurement name has the form OR.DRB.UeBufferingUIData or OR.DRB.UeBufferingUIData *Filter* (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellU.UeBufferingUIData or OR.CellU.UeBufferingUIData *Filter* (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is the QoS level. Where QoS represents the mapped 5QI or QCI level. -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.46 UEs buffering DL data - -- a) This counter provides the accumulated number of the UEs buffering DL data. - -This is recommended to support for O-DU. - -- b) CC - -- c) This measurement provides the accumulated number of UEs buffering DL data. This measurement is optionally calculated per QoS level (mapped 5QI or QCI in EN-DC). The measurement is incremented by the number of the Ues, optionally when DL data is the filter. - -The measurement is obtained by reporting the accumulated observed value of the UEs buffering DL data during the granularity period. - -NOTE: multiple 5QIs can be set per UE, each 5QI is counted per QoS flow. - -- d) Each measurement is an integer value representing the accumulated number of the UEs buffering DL data. - -- e) The measurement name has the form OR.DRB.UeBufferingDIData or OR.DRB.UeBufferingDIData\_Filter (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellU.UeBufferingDIData or OR.CellU.UeBufferingDIData\_Filter (deprecated, refer to NOTE in REQ-PMeas-MC-5). Where *Filter* is the QoS level. Where QoS represents the mapped 5QI or QCI level. -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.47 DRX inactive UEs - -- a) This counter provides the accumulated number of the UEs configured as DRX inactive. -This is optional counter for O-DU. -- b) CC -- c) Measurement is incremented by the number of UEs of which *drx-InactivityTimer* is assumed to be running. -The measurement is obtained by reporting the accumulated observed value of the UEs configured as DRX inactive during the granularity period. -- d) Each measurement is an integer value representing the accumulated number of the UEs configured as DRX inactive. -- e) OR.UECNTX.DrxInactUe (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellU.DrxInactUe (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.48 DRX active UEs - -- a) This counter provides the accumulated number of the UEs configured as DRX active. -This is optional counter for O-DU. -- b) CC -- c) Measurement subcounter is incremented by the number of UEs which is configured *drx-config* and of which *drx-InactivityTimer* is assumed not to be running. -The measurement is obtained by reporting the accumulated observed value of the UEs configured as DRX active during the granularity period. -- d) Each measurement is an integer value representing the accumulated number of the UEs configured as DRX active. -- e) OR.UECNTX.DrxActUe (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), OR.CellU.DrxActUe (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellIDU - -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.11.49 PDSCH slot for paging - -- a) This counter provides the number of PDSCH slot in which paging message is actually transmitted. -- b) CC -- c) This counter is incremented by 1 even when the same paging message is transmitted for different beam. -- d) Each measurement is an integer value representing the number of PDSCH slot in which paging message is actually transmitted. -- e) OR.RRU.PdschSlotForPaging (default, refer to 3GPP TS 28.552 [2] clause 3.3 Measurement Family), -OR.CellIU.PdschSlotForPaging (deprecated, refer to NOTE in REQ-PMeas-MC-5) -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -### A.4.12 Void - -### A.4.13 O-RU Performance measurements measured at O-DU - -#### A.4.13.1 Uplink data and control frames received in total - -- a) The total number of control/user plane messages received. -It is recommended to support for O-DU. -- b) CC -- c) The total number of control/user plane eCPRI or 1914.3 messages received. This counter is the sum of all valid and errored messages received. -- d) Each measurement is an integer value representing the total number of control/user plane messages received. -- e) OR.ORU.RX.Total -- f) aggregation (O-RU) -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.13.2 Uplink data frames received on Time - -- a) The number of inbound user plane messages that arrived within the specified time window. - -It is recommended to support for O-DU. - -- b) CC -- c) The number of inbound user plane (ecpri type 0) messages that arrived within the specified time window. Some “on time” messages may have sequence number errors or corruption errors but as long as they arrived within specified window time, this counter should include them. If the received message has been transport-fragmented, the full message shall be reassembled before checking its arrival window. -- d) Each measurement is an integer value representing the number of inbound user plane messages that arrived within the specified time window. -- e) OR.ORU.RXData.OnTime -- f) aggregation (O-RU) -- g) Packet Switched -- h) 5GS -- i) Network Operator’s Traffic Engineering Community - -#### A.4.13.3 Uplink data frames received too early - -- a) The number of inbound user plane messages which were detected to have arrived before the start of their designated receive window time. - -It is recommended to support for O-DU. - -- b) CC -- c) The number of inbound user plane messages which were detected to have arrived before the start of their designated receive window time. -- d) Each measurement is an integer value representing the number of inbound user plane messages which were detected to have arrived before the start of their designated receive window time. -- e) OR.ORU.RXData.TooEarly -- f) aggregation (O-RU) -- g) Packet Switched -- h) 5GS -- i) Network Operator’s Traffic Engineering Community - -#### A.4.13.4 Uplink data frames received too late - -- a) The number of inbound user plane messages which were detected to have arrived after the end of their designated receive window time. - -It is recommended to support for O-DU. - -- b) CC - -- c) The number of inbound user plane messages which were detected to have arrived after the end of their designated receive window time. -- d) Each measurement is an integer value representing the number of inbound user plane messages which were detected to have arrived after the end of their designated receive window time. -- e) OR.ORU.RXData.TooLate -- f) aggregation (O-RU) -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.13.5 Uplink control frames received on Time - -- a) The number of inbound control plane messages that are completely arrived within the reception time window for uplink C-Plane messages (C-Plane UL). Refer to WG4 CUS-Plane specification [i.2], clause 4.4.3 and clause 9.1 for details. - -It is recommended to support for O-DU. - -- b) CC -- c) The number of valid inbound control plane (ecpri type 2) messages that arrived within the specified time window. Some "on time" messages may have sequence number errors or corruption errors but as long as they arrived within specified window time, this counter should count them. -- d) Each measurement is an integer value representing the number of inbound control plane messages that are completely arrived within the reception time window for uplink C-Plane messages (C-Plane UL). -- e) OR.ORU.RXControl.OnTime -- f) aggregation (O-RU) -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.13.6 Uplink control frames received too early - -- a) The number of inbound control plane messages which were detected to be arrived before the start of their designated reception time window for uplink C-Plane messages (C-Plane UL). Refer to WG4 CUS-Plane specification [i.2], clause 4.4.3 and clause 9.1 for details. - -It is recommended to support for O-DU. - -- b) CC -- c) The number of inbound control plane messages which were detected to be arrived before the start of their designated reception window time. -This counter increments whether the message is subsequently processed or dropped. -- d) Each measurement is an integer value representing the number of inbound control plane messages which were detected to be arrived before the start of their designated reception time window for uplink C-Plane messages (C-Plane UL). - -- e) OR.ORU.RXControl.TooEarly -- f) aggregation (O-RU) -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.13.7 Uplink control frames received too late - -- a) The number of inbound control plane messages which were detected to be arrived after the end of their designated reception time window for C-Plane messages (C-Plane UL). Refer to WG4 CUS-Plane specification [i.2], clause 4.4.3 and clause 9.1 for details. - -It is recommended to support for O-DU. - -- b) CC -- c) The number of inbound control plane messages which were detected to be arrived after the end of their designated reception window time. -This counter increments whether the message is subsequently processed or dropped. -- d) Each measurement is an integer value representing the number of inbound control plane messages which were detected to be arrived after the end of their designated reception time window for C-Plane messages (C-Plane UL). -- e) OR.ORU.RXControl.TooLate -- f) aggregation (O-RU) -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.13.8 Uplink data frames with detecting sequence identifier error - -- a) The number of inbound on time user plane messages in which a sequence identifier number error is detected. - -It is optional counter for O-DU. - -- b) CC -- c) The number of inbound on time user plane messages in which a sequence identifier number error is detected. -This error occurs when the ecpriSeqId field does not increment. Both the Sequence ID, and Subsequence ID fields must be checked if transport fragmentation is supported otherwise only the Sequence ID field may be checked. -In addition to identifying a sending equipment sequencing error, this counter can increment when packets are dropped prior to reception by the RU, or when packets reordered by the network exceed the receiving device's capabilities. -- d) Each measurement is an integer value representing the number of inbound on time user plane messages in which a sequence identifier number error is detected. -- e) OR.ORU.RXData.SeqidErr -- f) aggregation (O-RU) - -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.13.9 Uplink control frames with detecting sequence identifier error - -- a) The number of inbound on time control messages in which a sequence identifier number error is detected. -It is optional counter for O-DU. -- b) CC -- c) The number of inbound on time control messages in which a sequence identifier number error is detected. -This counter increments under the same conditions as the rx\_seqid\_num\_err except for control plane messages. -- d) Each measurement is an integer value representing the number of inbound on time control messages in which a sequence identifier number error is detected. -- e) OR.ORU.RXControl.SeqidErr -- f) aggregation (O-RU) -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.13.10 Uplink frames with corrupt contents - -- a) The number of inbound on time messages with a correct ecpriSeqId (no sequence number error) which are dropped by the terminating entity due to the message containing one or more eCPRI/1914.3 or ORAN protocol errors. -It is optional counter for O-DU. -- b) CC -- c) The number of inbound on time messages with a correct ecpriSeqId (no sequence number error) which are dropped by the terminating entity due to the message containing one or more eCPRI/1914.3 or ORAN protocol errors. - -Protocol errors are defined as when eCPRI/1914.3/ORAN defined fields contain invalid values or indicate unsupported capabilities. Some examples of this are: - - 1. PcId or section Id number which has not been configured. - - 2. Unexpected use of C bit, - - 3. Unconfigured or Unsupported udCompHdr setting. - - 4. Unsupported section extension. - - 5. Wrong ecpriVersion and/or payloadVersion information - - 6. ecpriMessage field does not contain 0, 2, or 5. -- d) Each measurement is an integer value representing the number of inbound on time messages with a correct ecpriSeqId (no sequence number error) which are dropped by the terminating entity due to the message containing one or more eCPRI/1914.3 or ORAN protocol errors. -- e) OR.ORU.RX.Corrupt -- f) aggregation (O-RU) - -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.13.11 Uplink frames dropped and discarded - -- a) The total number of inbound messages which are discarded by the receiving O-RAN entity for any reason. -It is optional counter for O-DU. -- b) CC -- c) The total number of inbound messages which are discarded by the receiving O-RAN entity for any reason. -- d) Each measurement is an integer value representing the total number of inbound messages which are discarded by the receiving O-RAN entity for any reason. -- e) OR.ORU.RX.ErrDrop -- f) aggregation (O-RU) -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -###### A.4.13.12 Downlink control and data frames transmitted - -- a) The number of valid outbound control/user plane messages. -It is recommended to support for O-DU. -- b) CC -- c) The number of valid outbound control/user plane messages. -- d) Each measurement is an integer value representing the number of valid outbound control/user plane messages. -- e) OR.ORU.TX.Total -- f) aggregation (O-RU) -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.13.13 Downlink control frames transmitted to O-RU in total at O-DU - -- a) The number of valid outbound control plane messages. This counter is required only if O-RU supports LAA/LBT capabilities. -It is recommended to support for O-DU. - -- b) CC -- c) The number of valid outbound control plane messages. This counter is required only if O-RU supports LAA/LBT capabilities. -- d) Each measurement is an integer value representing the number of valid outbound control plane messages. -- e) OR.ORU.TXControl.Total -- f) aggregation (O-RU) -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.13.14 TRx Control activation - -- a) This counter is divided into sub-counters, each of which provides the cumulative number of times the O-DU has attempted to activate the specific TRx Control configuration to the O-RU using C-Plane command within a specified reporting period. - -The O-DU increments this sub-counter when it sends a C-Plane command to activate a specific TRx Control configuration in the O-RU. - -The counter name follows the format OR.ORU.TrxCtrl.ActReq\_Filter, - -where the filter represents the configuration ID (NOTE: This ID should correspond to the "mask-name" in the list **supported-trx-control-masks** provided by O-RU in o-ran-module-cap.yang module and can be referenced in clause 20.3.1.2 of [4]). - -For example, if the configuration is indexed by the mask-name "32TRx", then the sub-counter name would be OR.ORU.TrxCtrl.ActReq.32TRx. - -This is optional counter for O-DU. - -- b) CC -- c) O-RU supports Energy Saving by employing TRx Control. -- d) Each measurement is an integer value representing the cumulative number of times the O-DU has attempted to activate the specific TRx Control configuration to the O-RU using C-Plane command within a specified reporting period. -- e) OR.ORU.TrxCtrl.ActReq\_Filter -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.13.15 TRx Control activation failure - -- a) This counter accumulates the total number of failures that occurred when O-DU attempts to activate the specific TRx Control configuration in O-RU using C-Plane command within a designated reporting period. - -This counter is divided into sub-counters, each of which counts the unsuccessful attempts by the O-DU to activate a specific TRx Control configuration in the O-RU. - -The O-DU increments the counter when it experiences a failure while attempting to activate a specific TRx Control configuration in the O-RU using a C-Plane command. Failures are counted based on: - -- The reception of a NACK message -- The absence of expected ACK message - -The counter name follows the format OR.ORU.TrxCtrl.Fail\_Filter, - -where the filter represents the configuration ID (NOTE: This ID should correspond to the "mask-name" in the list **supported-trx-control-masks** provided by O-RU in o-ran-module-cap.yang module and can be referenced in clause 20.3.1.2 of [4]). - -For example, if the configuration is indexed by the mask-name "32TRx", then the sub-counter name would be OR.ORU.TrxCtrl.Fail.32TRx. - -This is optional counter for O-DU. - -- b) CC -- c) O-RU supports Energy Saving by employing TRx Control. -- d) Each measurement is an integer value representing the total number of failures that occurred when O-DU attempts to activate the specific TRx Control configuration in O-RU using C-Plane command within a designated reporting period. -- e) OR.ORU.TrxCtrl.Fail\_Filter -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.13.16 TRx Control Cumulative Activity time - -- a) This counter provides the cumulative time that the O-RU utilizes in energy-saving mode using the TRx Control configuration within each reporting period. - -This counter is divided into sub-counters, each recording the cumulative duration that the O-RU spends in a specific TRx Control configuration from the moment it is activated by the O-DU using C-Plane command. - -Time is measured in milliseconds and should be rounded up in the event of a fractional result. The O-DU starts the timer immediately upon receiving confirmation of the activation of a specific TRx Control configuration in the O-RU. This counter becomes pertinent only when the O-DU receives an ACK/NACK message from the O-RU for the C-Plane based TRx Control implementation. - -The counter name follows the format OR.ORU.TrxCtrl.UtiTime\_Filter, - -where the filter represents the configuration ID (NOTE: This ID should correspond to the "mask-name" in the list **supported-trx-control-masks** provided by O-RU in o-ran-module-cap.yang module and can be referenced in clause 20.3.1.2 of [4]). - -For example, if the configuration is indexed by the mask-name "32TRx", then the sub-counter name would be OR.ORU.TrxCtrl.UtiTime.32TRx. - -This is optional counter for O-DU. - -- b) CC -- c) The O-RU supports Energy Saving by employing TRx Control. At least one TRx Control configuration is activated to conserve energy within the O-RU. -- d) Each measurement is an integer value representing the cumulative time that the O-RU utilizes in energy-saving mode using the TRx Control configuration within each reporting period in unit of time. - -- e) OR.ORU.TrxCtrl.UtiTime\_Filter -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.13.17 Advanced Sleep Mode activation - -- a) This counter is divided into sub-counters, each of which provides the cumulative number of times the O-DU has attempted to activate the specific Sleep Mode to the O-RU using C-Plane command within a specified reporting period. - -The O-DU increments this sub-counter when it sends a C-Plane command to activate a specific Sleep Mode in the O-RU. The counter name follows the format OR.ORU.Asm.ActReq\_Filter, - -where the filter represents the configuration ID (NOTE: This ID should correspond to the "sleep-mode-type" provided by O-RU in the o-ran-module-cap.yang module and can be referenced in clause 20.4.1 of [4]). - -As sub-counters are in relation to specific Sleep Modes by values of sleep-mode-type node, expected names for sub-counters are as follows: - -name of sub-counter for SLEEP\_MODE\_0 should be OR.ORU.Asm.ActReq.SM0, -name of sub-counter for SLEEP\_MODE\_1 should be OR.ORU.Asm.ActReq.SM1, -name of sub-counter for SLEEP\_MODE\_2 should be OR.ORU.Asm.ActReq.SM2, -name of sub-counter for SLEEP\_MODE\_3 should be OR.ORU.Asm.ActReq.SM3. - -This is optional counter for O-DU. - -- b) CC -- c) O-RU supports Energy Saving by employing Advanced Sleep Mode. -- d) Each measurement is an integer value representing the cumulative number of times the O-DU has attempted to activate the specific Sleep Mode to the O-RU using C-Plane command within a specified reporting period. -- e) OR.ORU.Asm.ActReq\_Filter -- f) NRCellDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.13.18 Advanced Sleep Mode activation failure - -- a) This counter accumulates the total number of failures that occurred when O-DU attempts to activate the specific Sleep Mode in O-RU using C-Plane command within a designated reporting period. - -This counter is divided into sub-counters, each of which counts the unsuccessful attempts by the O-DU to activate a specific Sleep Mode in the O-RU. - -The O-DU increments the counter when it experiences a failure while attempting to activate a specific Sleep Mode in the O-RU using a C-Plane command. Failures are counted based on: - -- The reception of a NACK message -- The absence of expected ACK message - -The counter name follows the format OR.ORU.Asm.Fail\_Filter, - -where the filter represents the configuration ID (NOTE: This ID should correspond to the "sleep-mode-type" provided by O-RU in the o-ran-module-cap.yang module and can be referenced in clause 20.4.1 of [4]). - -As sub-counters are in relation to specific Sleep Modes by values of sleep-mode-type node, expected names for sub-counters are as follows: - -name of sub-counter for SLEEP\_MODE\_0 should be OR.ORU.Asm.Fail.SM0, - -name of sub-counter for SLEEP\_MODE\_1 should be OR.ORU.Asm.Fail.SM1, - -name of sub-counter for SLEEP\_MODE\_2 should be OR.ORU.Asm.Fail.SM2, - -name of sub-counter for SLEEP\_MODE\_3 should be OR.ORU.Asm.Fail.SM3. - -This is optional counter for O-DU. - -- b) CC -- c) O-RU supports Energy Saving by employing Advanced Sleep Mode. -- d) Each measurement is an integer value representing the total number of failures that occurred when O-DU attempts to activate the specific Sleep Mode in O-RU using C-Plane command within a designated reporting period. -- e) OR.ORU.Asm.Fail\_Filter -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.13.19 Advanced Sleep Mode Cumulative Activity time - -- a) This counter provides the cumulative time that the O-RU utilizes in energy-saving mode using the Sleep Mode within each reporting period. - -This counter is divided into sub-counters, each recording the cumulative duration that the O-RU spends in a specific Sleep Mode from the moment it is activated by the O-DU using C-Plane command. - -Time is measured in milliseconds and should be rounded up in the event of a fractional result. The O-DU starts the timer immediately upon receiving confirmation of the activation of a specific Sleep Mode in the O-RU. This counter becomes pertinent only when the O-DU receives an ACK/NACK message from the O-RU for the C-Plane based Advanced Sleep Mode implementation. - -The counter name follows the format OR.ORU.Asm.UtiTime\_Filter, - -where the filter represents the configuration ID (NOTE: This ID should correspond to the "sleep-mode-type" provided by O-RU in the o-ran-module-cap.yang module and can be referenced in clause 20.4.1 of [4]). - -As sub-counters are in relation to specific Sleep Modes by values of sleep-mode-type node, expected names for sub-counters are as follows: - -name of sub-counter for SLEEP\_MODE\_0 should be OR.ORU.Asm.UtiTime.SM0, - -name of sub-counter for SLEEP\_MODE\_1 should be OR.ORU.Asm.UtiTime.SM1, - -name of sub-counter for SLEEP\_MODE\_2 should be OR.ORU.Asm.UtiTime.SM2, - -name of sub-counter for SLEEP\_MODE\_3 should be OR.ORU.Asm.UtiTime.SM3. - -This is optional counter for O-DU. - -- b) CC -- c) The O-RU supports Energy Saving by employing Advanced Sleep Mode. At least one Sleep Mode is activated to conserve energy within the O-RU. - -- d) Each measurement is an integer value representing the cumulative time that the O-RU utilizes in energy-saving mode using the Sleep Mode within each reporting period in unit of time. -- e) OR.ORU.Asm.UtiTime\_Filter -- f) NRCellIDU -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -#### A.4.14 O-RU Performance measurements measured at O-RU - -Please see [4]. - ---- - -### Annex B (informative): 3GPP TS 32.404 template usage for O-RAN O1 defined Performance Measurements - -An example of the usage of the 3GPP TS 32.404 [1] Performance Measurement template to define the O1 performance measurements contained in this document is shown. The fields to be specified, according to the 3GPP performance measurement template, are labelled from a) to i) as follows: - -**Clause Header (indicating the name of the Performance Measurement)** - -- a) Description -- b) Collection Method -- c) Condition -- d) Measurement Result -- e) Measurement Type -- f) Measurement Object Class -- g) Switching Technology -- h) Generation -- i) Purpose - -For more information about the meaning of each field refer to 3GPP TS 32.404 [1], clause 3.3 - -### O1 Performance Measurement Example - -#### Received UL RLC PDUs - -- a) This counter provides the number of the received UL RLC PDUs. It is optional counter for O-DU. - -- b) CC -- c) Measurement subcounter is incremented by 1 whenever the UL RLC PDU is received when the QCI or the 5QI of the UL RLC PDU is group of subcounter.Pmgroup. -- d) Each measurement is an integer value representing the number of the received UL RLC PDUs. It is optional counter for O-DU. -- e) OR.RLC.RxUIRlcPdu.Pmgroup where Pmgroup is PmCountGroup number: - - 0: #0 - - 1: #1 - - ... - - 19: #19 -- f) gNBDUFunction -- g) Packet Switched -- h) 5GS -- i) Network Operator's Traffic Engineering Community - -## Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2024.07.29 | 01.00 | First Release
Inclusion of CRs:
  • • Addition of O1 PMeas Scope
  • • Addition of O1 PMeas Requirements
  • • Change of short name from O1 PM to O1 PMeas
  • • Addition of contents regarding further clarifications to clause 5.1
  • • Import of PMeas definitions from WG5 specs to Annex A
  • • Application of new PMeas template in Annex A
  • • Corrections and clarifications in Annex A
  • • Addition of note regarding WG5 models to clause A.1
  • • Addition of new PMeas to clauses A.4.2.25 and A.4.2.26
  • • Addition of PMeas template usage to Annex B
| -| 2024.12.09 | 02.00 | Summary of changes since the previous version:
  • • Adoption of 3GPP filter mechanism
  • • Addition of a new general requirement
  • • Update to 3GPP Release 18 references
  • • Alignment with 3GPP for measurement values
  • • Addition of counting triggers
  • • Corrections and clarifications for measurement definitions
  • • Voiding A.2.9.31, A.4.2.23, A.4.2.24, A.4.3.3, A.4.11.31, and A.4.11.32
  • • Voiding NOTE 2) and 5) in clause 5.1
| -| 2025.03.27 | 03.00 | Summary of changes since the previous version:
  • • Correction of UE reported differential L1-RSRP of second best beam
  • • Correction of Request for UL RLC PDUs retransmission
  • • Modification of condition in UEs buffering performance measurements
  • • Removal of Type A-Type B measurements differentiation
  • • Addition of PSCell sub-counters
  • • Correction of Multiplexed receptions of PUSCH and Multiplexed transmissions of PDSCH
| -| 2025.07.23 | 04.00 | Summary of changes since the previous version:
  • • Alignment to new TS Template
  • • Clarification of measurement time period
  • • Addition of paging-related measurements
  • • Correction of bin ranges in A.4.11.35
  • • Correction of the bitwidth in the measurement result
  • • Addition of simplified UE RLC throughput measurements for UL and DL
  • • Alignment with 3GPP for PLMN use
  • • Addition of performance measurements for PSCell change using SRB1
| -| 2025.12.08 | 05.00 | Summary of changes since the previous version:
  • • Addition of a new measurement for the number of SgNB addition requests
  • • Correction of volume-related measurements
  • • Alignment with 3GPP on PM family names
  • • Editorial adjustments
| \ No newline at end of file diff --git a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/01b37b45a159c6e8efb7e2f67f99ba68_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/05ec650892a1d3916ffe3d2a7ec29928_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/06e272c534fab6c7202d1355b043faf6_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/0827b9260fe5458dbe416ebfc78c469e_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 8ddaf6adc8b455f7d3cc8be540360bcbe788965b..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/09fcf056902487318885284a6b43b08c_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/09fcf056902487318885284a6b43b08c_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/09fcf056902487318885284a6b43b08c_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/0a65720e640be13541e947c06c7a8c7f_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1099a4137017f2d9721d546bbb1e9362_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg deleted file mode 100644 index 2f54633a796f0d866754433c73dd79178cd34273..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/110058f0fd9c7ca251db430f6df06b80_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg deleted file mode 100644 index bef92370b92f7f62fcf03e62e04f4f2905eeb0df..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:29af4545675cb00eb2790504afe0c0bc329627f1c20c8d6156b2f4290d8d8d75 -size 4502 diff --git a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1396371bb5cf61891981fff2e338ec58_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/14af8d47efd24c21fddf71b2415b6397_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/153b4763edcf6b16d783052c7ad165f1_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1baaba7a6e54e77197475726c871067d_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1d92d4ad55f2aa411dc849438982f26b_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1e7157ed1c2b915b5b1823b6ad189038_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/1f0d4018f872bfcffec260045c6dd734_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/226f5e462c99b71e08dc9abaa5ae260c_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/227840abf8cd09f4f3e83336421daccb_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/22af211207188ebc64d7b60ca052b367_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/22f30783614672d201275c116a5d8516_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/253600420ae7bd7d0119563b895cbf8a_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/256ec100c3aeedb411eee5a09386812e_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2576e074afbb2a591f07da0fe1987ff1_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2a185522b492253375ed16f0c515c230_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2a185522b492253375ed16f0c515c230_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2a185522b492253375ed16f0c515c230_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2b7c350726e78976d2dfd3ce90daa9f7_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2c83b9d9c8c8076be3a1de47288c226d_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2cb201535956cd78d7fd3cc89f3c7d03_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg deleted file mode 100644 index d110802db5cc01df4334ccf172b1baa5802ac71c..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ef8764f6759b38cdb859dc50d4c55ba412d4d1a6c9040bacc87cb3d2a5b610f1 -size 4533 diff --git a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2eea01382188b70064fa2818361d89f1_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2eea01382188b70064fa2818361d89f1_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/2eea01382188b70064fa2818361d89f1_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg deleted file mode 100644 index d110802db5cc01df4334ccf172b1baa5802ac71c..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ef8764f6759b38cdb859dc50d4c55ba412d4d1a6c9040bacc87cb3d2a5b610f1 -size 4533 diff --git a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/318db222fae24a59c370fa6471d541b8_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/318db222fae24a59c370fa6471d541b8_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/318db222fae24a59c370fa6471d541b8_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/35437f160e157760713aa85be471c3f3_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/35437f160e157760713aa85be471c3f3_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/35437f160e157760713aa85be471c3f3_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/36e2350ea1a3ef6ca68c655394300a91_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/36e4a08fb5114c98c80f946714cc6c30_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/36fb8f844f936e7a1de4838da774f2f9_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index a197c2be245939289565c178298f72585a1cc7a8..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:86e6d1753c0b2bc96c7e934a7e8d9474fcfaeab0d01df61c28dbe59a72096e4d -size 4515 diff --git a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/3a4f4369128594c5db0aa6b853c0666e_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/3b89d812329a65ab156184a40524adf0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/3b89d812329a65ab156184a40524adf0_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/3b89d812329a65ab156184a40524adf0_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/3f727e6c0d6658bc53ea10905c4561dd_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/41863cc6f48c5a6ff0290186547042d9_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/446c0bd806260f25430cadb01a6786c7_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/481b1f80fc31ebebb30d1f57d31e3af3_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/488b6387bc5fe15b9528eca7968a8733_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4932f76f000f1673ac40baf1419fbb3b_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index bef92370b92f7f62fcf03e62e04f4f2905eeb0df..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:29af4545675cb00eb2790504afe0c0bc329627f1c20c8d6156b2f4290d8d8d75 -size 4502 diff --git a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4b241e690aacaf391e2b28dd9307575c_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4b297191fa254f84c021e73b3b79e860_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4b81ac66c571b3118659e4d9f47abb22_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4db00373eb0bec04341ee887235bbfea_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/5009e30a55479d3941af523871208f9d_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/5009e30a55479d3941af523871208f9d_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/51878675eb6a813e99b9fe26951bd5cc_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/527578a453197a501cd46c0d0e579cd1_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/52a225f71b166b0c65c2f29f32a79f7f_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/568031aac86c633aab96b734dba3835e_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/568031aac86c633aab96b734dba3835e_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/568031aac86c633aab96b734dba3835e_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/56ac11fb9683d7b846fb65c845d80f22_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/59368942873b0c35eef79a7a985025dc_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/59edd779768a6eb448c9b0ca5402346e_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/5ae3023386ee15fae372871afce28865_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/60d6a326e6061d71ea69c9375ec96631_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/60e345365fd1e52e01c91e3fd3cc6515_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6254e6ff201e39d022a590c8b6e3de2b_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6588b1c7f14069d96744b473ad663248_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/681c354e00e1c0fe098ba665ff155cb8_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6983ff962c0a32659de18c30790e1519_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6983ff962c0a32659de18c30790e1519_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6983ff962c0a32659de18c30790e1519_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6a5342571eca4b46338fdfb3c42a8055_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6a9c5a85a12499d60c5a3a75c643b852_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6b0834ca8cdd18832ed461378d51dcb7_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6c6024603c6fd57b23210b79f573b3bd_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6c8a96787f532bd1fa4719e738cf556f_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6d8454e3fdef6561c6f64adf0092e9b9_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6da6e06f73c5bf331c5e55773dc6d010_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6f794c8c41326b510934ce3f3d622202_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/6ff798305e82bdf8233f1381ff9f7c49_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/728298e0fbc8de5f3894ce6cb10fb413_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/76fb24764e6c9c644b30056855c81aa5_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/78b47bea9d645c52984f5f4c6740db05_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/79898de98da3367d0ea9beef38f5c01c_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg deleted file mode 100644 index d110802db5cc01df4334ccf172b1baa5802ac71c..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ef8764f6759b38cdb859dc50d4c55ba412d4d1a6c9040bacc87cb3d2a5b610f1 -size 4533 diff --git a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7c66f12495a47e87f0a0314a0d3a2eff_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7d08458fbe0bd5f306c00c16d68b25f2_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/7f4320cee12fc1dbb865cc6b67462a91_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/81b34087cd6755a80f84a70cf28fba82_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8237c46643affc7cc057ae950dbcf1f2_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/829cdaf00f7219d70e571064b2b13291_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8447c5519e85d7a9e029fbf321da4c4f_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/854df8ad60507803253274673f9062cf_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8b4befaffc5166da571069410e207aea_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8d129c93d18909f0643766f372e9ebf6_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8d138b6bf0be359dc7f079db4899bc41_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index bef92370b92f7f62fcf03e62e04f4f2905eeb0df..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:29af4545675cb00eb2790504afe0c0bc329627f1c20c8d6156b2f4290d8d8d75 -size 4502 diff --git a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8e0160fd55391f6f2bbdef38ceb6f823_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/8fbe9e67b51710384633b6407d60420d_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9156549264d36ead617a1dec7987f970_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9159d999b6514420a64eae80e52f1fd5_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/92eab1c7ce3162be3f7dabe7a3035249_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/970a901d8e537da4b6ff719d8931912f_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/990afa9d07fb81cf8760867cb4247a79_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9a2aa33c5d905f8a0646278a48a2e565_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9a6ff2584005112f32fbd551cb6f0591_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9b59a11096b85b2bc74c6f653a354e28_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9c7046c19fb32a2d21ac26f5e90a7098_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a28ab03366399b5e0a61445bc57e3724_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a76a30cf23764f0b907220e7c3c70ce1_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a7fcb275d0eed586509a47f4f86a9725_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a82aef1d2f3f1a527328950e9db947ee_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a9bb99d15f54792e1c9a14b1e465369a_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/a9f8bc87c084c4c84bae1128815c277c_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/aa05feb33e250a75136ea52816d3c19a_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/acfb2707966cd2618f2dc86b1a02702c_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/aef4390a4629604196222b9ed006a786_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/aef4390a4629604196222b9ed006a786_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/aef4390a4629604196222b9ed006a786_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/b0e533f20bac2474664e1bebb7813606_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/bb8abc0cc19db87acc1c3d7321599690_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/bb9f586190c7197099d25db7df9050af_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/bb9f586190c7197099d25db7df9050af_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/bb9f586190c7197099d25db7df9050af_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/be8d4d130f4e1f103926de61c4bfc23c_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/c389468860cd886ab9c732473e959f0f_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/c521036a3eb59673388f5e034f4e6c9f_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/c5538ac451af9d74926b82278f11fb87_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg deleted file mode 100644 index 8ddaf6adc8b455f7d3cc8be540360bcbe788965b..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/c964194b41a0636cf95ab198c9196bcd_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/cb8f0521a69f168a06222045bea81a86_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/cdfbee2c06c086fdee6cb58317c947e0_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d0516b99882398c64c90f71c12e808e2_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d1ec9820fe8d23d83e066389a9cd7338_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d2c29dfabebacb6f853683a6c3759320_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d35a80e3faed208324083399568c7461_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d35a80e3faed208324083399568c7461_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d35a80e3faed208324083399568c7461_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d597715604d00e1ab3b00cc3f16e59de_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d7c4779f679cb390727824a9896ecb5f_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d879e5f2c388bb87ee9614f63364dcf0_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d90f17b29a73eddf151f51effa8912e0_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/d96da198567c411a05faab4ce5b4e58c_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index d110802db5cc01df4334ccf172b1baa5802ac71c..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ef8764f6759b38cdb859dc50d4c55ba412d4d1a6c9040bacc87cb3d2a5b610f1 -size 4533 diff --git a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/dbd230eafb5429741c22c2f7293118af_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/df495bddeb5d8826c7571714e6db1478_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e010d665d27407ff5e238d1c45c1c98f_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg deleted file mode 100644 index bef92370b92f7f62fcf03e62e04f4f2905eeb0df..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:29af4545675cb00eb2790504afe0c0bc329627f1c20c8d6156b2f4290d8d8d75 -size 4502 diff --git a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e1d97826df530020bf86c791d8c7d724_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index bef92370b92f7f62fcf03e62e04f4f2905eeb0df..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:29af4545675cb00eb2790504afe0c0bc329627f1c20c8d6156b2f4290d8d8d75 -size 4502 diff --git a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e339d97a55f726bb82f15798d7eb80b7_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e345315706e3fe633bb6d593246c01bf_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e374c531ea6c45899ce8ec331e437bd1_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e3b551138548092502c92a99ebfdb7bc_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e511e373339b5f948f239b19e0c37dd4_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e6eb959227f4726d42277c0f920bedbc_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e8411aa566660d595a395a2f41d1f009_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e87df69ebd4cd2dbbf6749079e6c057a_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e882a6bdfd0e868314f3a26f536145a3_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/e9d7df9758d9a042bb17daa9842760db_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/eb08b089f7e59a7e96a8b3c146668d6a_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/ef484b2179ee14c86e53e9f5b3c0d848_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f250ba4162fe40d8ddfd05b74fa48895_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f3d768b0299c4763bc703b606391c48b_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f74adaa1840504407cd4272995426f82_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f7dbd497160f02888f34fdf243648aa2_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg deleted file mode 100644 index bef92370b92f7f62fcf03e62e04f4f2905eeb0df..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:29af4545675cb00eb2790504afe0c0bc329627f1c20c8d6156b2f4290d8d8d75 -size 4502 diff --git a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/f9b17af787dbdc9711539cd71df3d782_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/fac227c65a311c313325216dcf59591f_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/fac227c65a311c313325216dcf59591f_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/fac227c65a311c313325216dcf59591f_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/facce731b2dbfae43a8609231a700be1_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/facce731b2dbfae43a8609231a700be1_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/facce731b2dbfae43a8609231a700be1_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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index e8b9624631d343de15dc1c23522e08f9b2eb85d7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.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/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.O1PMeas-R005-v05.00/images/ff748955b94dcb8337283fbe12baa475_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/doc.md b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/doc.md deleted file mode 100644 index 8c5484ca4d3546ceba2950c471548868c34908d9..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/doc.md +++ /dev/null @@ -1,3175 +0,0 @@ - - -# --- **O-RAN Work Group 10 (OAM for O-RAN)** **Topology Exposure and Inventory Application Protocols Specification - Stage 3** - -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 | -| Executive summary ..... | 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 Application protocol for TE&IV services ..... | 5 | -| 4.1 Introduction ..... | 5 | -| 4.2 Version conventions for the present document ..... | 5 | -| 5 RESTful TE&IV Service APIs..... | 5 | -| 5.1 Overview ..... | 5 | -| 5.2 Versioning of RESTful TE&IV Service APIs ..... | 6 | -| 5.3 URI structure and supported content formats ..... | 6 | -| 5.4 General considerations for RESTful TE&IV Service APIs..... | 7 | -| 5.4.1 Usage of HTTP header fields..... | 7 | -| 5.4.2 Handling of large query results..... | 7 | -| 5.4.3 Error reporting ..... | 7 | -| 6 Topology Exposure and Inventory Management Services..... | 7 | -| 6.1 Topology Inventory API ..... | 7 | -| 6.1.1 Introduction..... | 7 | -| 6.1.2 API version ..... | 7 | -| 6.1.3 Resource structure and methods ..... | 7 | -| 6.1.4 Service operations..... | 9 | -| 6.1.5 Resources..... | 19 | -| 6.1.6 Custom operations without associated resources ..... | 37 | -| 6.1.7 Notifications ..... | 38 | -| 6.1.8 Data model..... | 39 | -| 6.1.9 Error Handling..... | 43 | -| Annex A (normative): OpenAPI Specifications ..... | 43 | -| A.1 Overview ..... | 43 | -| A.2 Topology & Inventory API ..... | 43 | -| Annex (informative): Change History ..... | 60 | - -# --- Foreword - -This Technical Specification (TS) has been produced by WG10 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. - -# --- Executive summary - -The present document specifies the TE&IV APIs suited to realize the use cases of TE&IV Service Consumer as specified in TE&IV UCR [1]. - -# --- 1. Scope - -This document specifies the TE&IV APIs used to support TE&IV services within 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. - -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.WG10.TE&IV-UCR.0: "Topology Exposure and Inventory Management Services Use Cases and Requirement Specification" ("TE&IV UCR") -- [2] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3" -- [3] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition" -- [4] Semantic Versioning 2.0.0: -- [5] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format" -- [6] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax" -- [7] ETSI GS NFV-SOL 013 Rel3: "Protocols and Data Models; Specification of common aspects for RESTful NFV MANO APIs" -- [8] IETF RFC 7951: "JSON Encoding of Data Modeled with YANG" -- [9] O-RAN.WG10.TS.TE&IV-CIMI.0: "Topology Exposure & Inventory Common Information Models and Interface Specification - Stage 2" ("TE&IV CIMI") -- [10] O-RAN.WG10.TS.TE&IV-DM.0: "Topology Exposure and Inventory Data Model Specification - Stage 3" ("TE&IV DM") -- [11] OpenAPI: "OpenAPI 3.0.3 Specification", - -## 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] IETF RFC 4229: "HTTP Header Field Registrations" - -# --- 3. Definition of terms, symbols and abbreviations - -## 3.1. Terms - -For the purpose of the present document, the following terms apply: - -**API Consumer:** The TE&IV Service Consumer consuming one or more services using APIs. - -**API Producer:** The TE&IV Service Producer that offers its services for consumption via APIs. - -**Domain:** A logical grouping of topology entities and/or topology relationships. - -## 3.2. Symbols - -Void - -## 3.3. Abbreviations - -Void - -# --- 4 Application protocol for TE&IV services - -## 4.1 Introduction - -The present document contains a realization of the services identified in TE&IV UCR [1]. This definition of the TE&IV Application Protocols Interface (TE&IV API) defined in the present document is based on the 3GPP service framework for network functions specified in 3GPP TS 29.501 [3]. - -## 4.2 Version conventions for the present document - -The version number of the present document follows the "xx.yy" versioning scheme. There could be implications for the interoperability between TE&IV Service Consumers and TE&IV Service API implementations in the SMO that are based on different versions of the present document. - -An incremented "xx" version field of the present document could indicate that a new major feature (e.g., a new TE&IV Service) has been added or that an incompatible change has been made to one or more TE&IV Service APIs. An incremented "yy" version field could indicate that an optional feature has been added, a technical issue has been fixed, or that clarifications or editorial corrections have been made. - -The version conventions for RESTful TE&IV Service APIs are defined in clause 5.2. - -# --- 5 RESTful TE&IV Service APIs - -## 5.1 Overview - -The design of the RESTful TE&IV Service APIs is based on the services and requirements defined in TE&IV UCR [1], and on the protocol design framework as specified in 3GPP TS 29.501 [3]. - -The present document defines the protocols for the TE&IV service APIs listed in table 5.1-1. - -**Table 5.1-1: RESTful TE&IV Service APIs and their versions defined in the present document.** - -| Service API | API version | -|--------------------------|-------------| -| Topology & Inventory API | 1.0.0 | - -## 5.2 Versioning of RESTful TE&IV Service APIs - -Each RESTful TE&IV Service API is versioned independently. The API version number defined in the present document contains three numerical fields following a MAJOR.MINOR.PATCH pattern, and may contain a pre-release version field, according to SemVer [4]. - -The API version number held by an implementation may additionally include a build metadata field, according to SemVer [4], to indicate a specific deployment. The content of this field is implementation specific; it is provided by the deployment. The path segment used in URI structures indicate the MAJOR field of the API version number. The full API version number is visible in the "version" field of the "info" object of each OpenAPI document in Annex A. - -To indicate the full API version the API Consumer intends to use, the API Consumer may include the "Version" HTTP header (see IETF RFC 4229 [i.1]) in an HTTP request, in which case the header shall contain the version identifier as defined above. It is optional to include the build metadata field. - -The API Producer shall include in the response the "Version" HTTP header signalling the used API version, including the build metadata if available. If the build metadata have been omitted in the request, the API Producer shall use the combination of MAJOR, MINOR, PATCH, and pre-release indicator as requested and the highest supported value for the build metadata field for that combination, if available. In case the API Consumer has not sent a "Version" header in the request, the API Producer shall use the latest available version, and signal it in the "Version" header. - -NOTE: In case multiple versions are supported by an API Producer under the URI for a major version, this allows the API Consumer to request a particular version. This mechanism is referred to as "microversioning". - -If the API version signalled by the API Consumer in the "Version" request header is not supported by the API Producer, the API Producer shall respond with a "406 Not Acceptable" error and may include in the response payload body a Problem Details structure providing more information on the cause of the error. - -## 5.3 URI structure and supported content formats - -This clause specifies the URI prefix and the supported content formats applicable to the RESTful TE&IV Service APIs. - -All resource URIs of the APIs shall have the following prefix: - -**{apiRoot}///** - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [3], i.e.: - -**{apiRoot}///** - -with the following components: - -- The {apiRoot} shall be set as described in clause 4.4.1 of 3GPP TS 29.501 [3]; however, the restrictions w.r.t the operator specific FQDN of the host portion defined there do not apply. -- The indicates the API name of the service interface in an abbreviated form. It is defined in the clause specifying the corresponding RESTful TE&IV Service API. -- The indicates the major version (see clause 5.2) of the API and is defined in the clause specifying the corresponding RESTful TE&IV ServiceAPI. -- Each represents a specific resource of the API. It is defined in the corresponding RESTful TE&IV Service API for each one of the defined resources. - -For HTTP requests and responses that have message content, the content format JSON shall be supported (see IETF RFC 8259 [5]). The JSON content shall be signalled by the content type "application/json" and for JSON encoded YANG, the content type "application/yang-data+json" shall be used (see IETF RFC 7951 [8]). - -All resource URIs of the API shall comply with the URI syntax as defined in IETF RFC 3986 [6]. An implementation that dynamically generates resource URI parts (individual path segments, sequences of path segments that are separated by "/", query parameter values) shall ensure that these parts only use the character set that is allowed by IETF RFC 3986 [6] for these parts. - -## 5.4 General considerations for RESTful TE&IV Service APIs - -### 5.4.1 Usage of HTTP header fields - -HTTP headers are components of the headers section of the HTTP request and response messages. The usage of HTTP header fields shall follow the definitions in clause 4.2 of ETSI GS NFV-SOL 013 [7]. - -### 5.4.2 Handling of large query results - -The handling of large query results shall be supported by RESTful TE&IV Service APIs as specified in clause 5.4.2 of ETSI GS NFV-SOL 013 [7]. - -### 5.4.3 Error reporting - -In RESTful interfaces, application errors are mapped to HTTP errors. Since HTTP error information is generally not enough to discover the root cause of the error, additional application specific error information is typically delivered in the message content based on the ProblemDetails data type. - -HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [3]. Protocol errors and application errors specified in table 5.2.7.1-1 of 3GPP TS 29.500 [2] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [2]. - -# --- 6 Topology Exposure and Inventory Management Services - -## 6.1 Topology Inventory API - -### 6.1.1 Introduction - -This API enables the API Consumer to query the topology entities, entity types and its relationship to other topology entities as defined in TE&IV CIMI [9]. - -### 6.1.2 API version - -For the Topology Inventory API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 0 and the PATCH version field shall be 0 (see clause 4.3.1.1 of 3GPP TS 29.501 [3] for a definition of the version fields). Consequently, the URI path segment shall be set to "v1". - -### 6.1.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined in clause 5.2. The resource URI variable shall be "topology-inventory". The for each resource shall be set as described in clause 6.1.5. - -Figure 6.1.3-1 shows the overall resource URI structure defined for the Topology Inventory API. - -![A hierarchical tree diagram showing the resource URI structure for the Topology Inventory API. The root is {apiRoot}/topology-inventory/{apiVersion}. It branches into /domains, /schemas, /user-defined-schemas, /manage-classifiers (dashed box), and /manage-decorators (dashed box). /domains branches into {domainName}, which further branches into /entity-types, /entities, {entityId}, and /relationships. /schemas branches into {schemaName}, which branches into /content. /user-defined-schemas branches into {schemaName}, which branches into /content. /domains also branches into /relationship-types, which branches into {relationshipTypeName}, /relationships, and {relationshipId}.](d0abac95583b52a3b35f74a215567334_img.jpg) - -``` - -graph TD - Root["{apiRoot}/topology-inventory/{apiVersion}"] --> Domains["/domains"] - Root --> Schemas["/schemas"] - Root --> UserSchemas["/user-defined-schemas"] - Root --> ManageClassifiers["/manage-classifiers"] - Root --> ManageDecorators["/manage-decorators"] - - Domains --> DomainName["{domainName}"] - DomainName --> EntityTypes["/entity-types"] - DomainName --> Entities["/entities"] - DomainName --> RelationshipTypes["/relationship-types"] - EntityTypes --> EntityTypeName["{entityTypeName}"] - EntityTypeName --> Entities - Entities --> EntityId["{entityId}"] - EntityId --> Relationships1["/relationships"] - RelationshipTypes --> RelationshipTypeName["{relationshipTypeName}"] - RelationshipTypeName --> Relationships2["/relationships"] - Relationships2 --> RelationshipId["{relationshipId}"] - - Schemas --> SchemaName["{schemaName}"] - SchemaName --> Content1["/content"] - - UserSchemas --> UserSchemaName["{schemaName}"] - UserSchemaName --> Content2["/content"] - - style ManageClassifiers stroke-dasharray: 5 5 - style ManageDecorators stroke-dasharray: 5 5 - -``` - -A hierarchical tree diagram showing the resource URI structure for the Topology Inventory API. The root is {apiRoot}/topology-inventory/{apiVersion}. It branches into /domains, /schemas, /user-defined-schemas, /manage-classifiers (dashed box), and /manage-decorators (dashed box). /domains branches into {domainName}, which further branches into /entity-types, /entities, {entityId}, and /relationships. /schemas branches into {schemaName}, which branches into /content. /user-defined-schemas branches into {schemaName}, which branches into /content. /domains also branches into /relationship-types, which branches into {relationshipTypeName}, /relationships, and {relationshipId}. - -**Figure 6.1.3-1: Resource URI structure of the Topology Inventory API** - -Table 6.1.3-1 lists the individual resources defined for the API, the applicable HTTP methods, and the associated service operations. - -**Table 6.1.3-1: Resources and methods overview of the Topology Inventory API** - -| Resource name | Resource URI | HTTP method | Service Operation | -|---------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|-------------|--------------------------------------------------| -| All topology domains | .../domains | GET | getAllDomains | -| All topology entity types in a topology domain | .../domains/{domainName}/entity-types | GET | getTopologyEntityTypes | -| All instances of a topology entity type in a topology domain | .../domains/{domainName}/entity-types/{entityTypeName}/entities | GET | getTopologyByEntityTypeName | -| Individual instance of a topology entity type in a topology domain | .../domains/{domainName}/entity-types/{entityTypeName}/entities/{entityId} | GET | getTopologyById | -| All relationships of an instance of a topology entity type in a topology domain | .../domains/{domainName}/entity-types/{entityTypeName}/entities/{entityId}/relationships | GET | getAllRelationshipsForEntityId | -| All topology relationship types in a topology domain | .../domains/{domainName}/relationship-types | GET | getTopologyRelationshipTypes | -| Individual topology relationship | .../domains/{domainName}/relationship-types/{relationshipTypeName}/relationships | GET | getRelationshipsByType | -| Individual topology relationship instance | .../domains/{domainName}/relationship-types/{relationshipTypeName}/relationships/{relationshipId} | GET | getRelationshipById | -| All topology model schemas | .../schemas | GET | getSchemas | -| Individual model schema content | .../schemas/{schemaName}/content | GET | getSchemaByName | -| All user defined schemas | .../user-defined-schemas | GET
POST | getUserDefinedSchemas
createUserDefinedSchema | -| User defined schema instance | .../user-defined-schemas/{schemaName} | DELETE | deleteUserDefinedSchema | -| Content of user defined schema instance | .../user-defined-schemas/{schemaName}/content | GET | getUserDefinedSchemaByName | - -**Table 6.1.3-2: Custom operations without associated resources** - -| Custom operation URI | Mapped HTTP method | Description | -|--------------------------------------------------------------|--------------------|----------------------------------------------------------------------------| -| {apiRoot}/topology-inventory/{apiVersion}/manage-classifiers | POST | Update or delete specified entities and/or relationships with classifiers. | -| {apiRoot}/topology-inventory/{apiVersion}/manage-decorators | POST | Update or delete specified entities and/or relationships with decorators. | - -### 6.1.4 Service operations - -#### 6.1.4.1 Operation getAllDomains - -The API Consumer uses this operation to discover the available topology domains - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -``` - -``` -Participant "API Producer" as Producer -Consumer --> Producer: GET .../domains -Producer --> Consumer: 200 OK (Domains) -@enduml -``` - -![Sequence diagram for getAllDomains Operation. It shows an API Consumer sending a GET .../domains request to an API Producer, which responds with a 200 OK (Domains).](e6df2733626a85205c1db682e6259c46_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET .../domains - API Producer-->>API Consumer: 2 200 OK (Domains) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram for getAllDomains Operation. It shows an API Consumer sending a GET .../domains request to an API Producer, which responds with a 200 OK (Domains). - -**Figure 6.1.4.1-1: getAllDomains Operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../domains) to discover the available topology domains. -2. The API Producer shall return the HTTP GET response. On success, “200 OK” shall be returned and the message content shall carry a topology domain information. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 6.1.4.2 Operation getTopologyEntityTypes - -The API Consumer uses this operation to discover the topology entity types in a topology domain. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer --> Producer: GET .../domains/{domainName}/entity-types -Producer --> Consumer: 200 OK (EntityTypes) -@enduml -``` - -![Sequence diagram for getTopologyEntityTypes Operation. It shows an API Consumer sending a GET .../domains/{domainName}/entity-types request to an API Producer, which responds with a 200 OK (EntityTypes).](b0211cee4b20034939d883ac0d70f696_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET .../domains/{domainName}/entity-types - API Producer-->>API Consumer: 2 200 OK (EntityTypes) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram for getTopologyEntityTypes Operation. It shows an API Consumer sending a GET .../domains/{domainName}/entity-types request to an API Producer, which responds with a 200 OK (EntityTypes). - -**Figure 6.1.4.2-1: getTopologyEntityTypes Operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../domains/{domainName}/entity-types) to discover the topology entities within a topology domain. -2. The API Producer shall return the HTTP GET response. On success, “200 OK” shall be returned and the message content shall carry a topology entity types information within a topology domain. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 6.1.4.3 Operation getTopologyByEntityTypeName - -The API Consumer uses this operation to query all instances of a topology entity type in a topology domain - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: GET .../domains/{domainName}/entity-types/{entityTypeName}/entities -Producer -->> Consumer: 200 OK (Entities) -@enduml -``` - -![Sequence diagram for getTopologyByEntityTypeName operation showing a GET request from API Consumer to API Producer and a 200 OK response.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 GET .../domains/{domainName}/entity-types/{entityTypeName}/entities - API Consumer->>API Producer: 1 GET .../domains/{domainName}/entity-types/{entityTypeName}/entities - Note right of API Producer: 2 200 OK (Entities) - API Producer-->>API Consumer: 2 200 OK (Entities) -``` - -Sequence diagram for getTopologyByEntityTypeName operation showing a GET request from API Consumer to API Producer and a 200 OK response. - -**Figure 6.1.4.3-1: getTopologyByEntityTypeName Operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../domains/{domainName}/entity-types/{entityTypeName}/entities) to query the instances of a specific topology entity type within a topology domain. -2. The API Producer shall return the HTTP GET response. On success, “200 OK” shall be returned and the message content shall carry the instances of a specific topology entity type information within a topology domain. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 6.1.4.4 Operation getTopologyById - -The API Consumer uses this operation to query an instance of a topology entity type in a topology domain - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: GET .../domains/{domainName}/entity-types/{entityTypeName}/entities/{entityId} -Producer -->> Consumer: 200 OK (EntityInstance) -@enduml -``` - -![Sequence diagram for getTopologyById operation showing a GET request from API Consumer to API Producer and a 200 OK response.](ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 GET .../domains/{domainName}/entity-types/{entityTypeName}/entities/{entityId} - API Consumer->>API Producer: 1 GET .../domains/{domainName}/entity-types/{entityTypeName}/entities/{entityId} - Note right of API Producer: 2 200 OK (EntityInstance) - API Producer-->>API Consumer: 2 200 OK (EntityInstance) -``` - -Sequence diagram for getTopologyById operation showing a GET request from API Consumer to API Producer and a 200 OK response. - -**Figure 6.1.4.4-1: getTopologyById Operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../domains/{domainName}/entity-types/{entityTypeName}/entities/{entityId}) to query an instance of a specific topology entity type within a topology domain. -2. The API Producer shall return the HTTP GET response. On success, “200 OK” shall be returned and the message content shall carry an instance of a specific topology entity type information within a topology domain. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 6.1.4.5 Operation getAllRelationshipsForEntityId - -The API Consumer uses this operation to query the relationships of an instance of a topology entity type in a topology domain - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: GET .../domains/{domainName}/entity-types/{entityTypeName}/entities/{entityId}/relationships -Producer -->> Consumer: 200 OK (Relationships) -@enduml -``` - -![Sequence diagram for getAllRelationshipsForEntityId operation. It shows an API Consumer sending a GET request to an API Producer, and the API Producer returning a 200 OK response.](08441fa90c5fd11994626f662ac13f19_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 GET .../domains/{domainName}/entity-types/{entityTypeName}/entities/{entityId}/relationships - API Consumer->>API Producer: 1 GET .../domains/{domainName}/entity-types/{entityTypeName}/entities/{entityId}/relationships - Note right of API Producer: 2 200 OK (Relationships) - API Producer-->>API Consumer: 2 200 OK (Relationships) -``` - -Sequence diagram for getAllRelationshipsForEntityId operation. It shows an API Consumer sending a GET request to an API Producer, and the API Producer returning a 200 OK response. - -Figure 6.1.4.5-1: getAllRelationshipsForEntityId Operation - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../domains/{domainName}/entity-types/{entityTypeName}/entities/{entityId}/relationships) to query the relationships of an instance of a topology entity type within a topology domain. -2. The API Producer shall return the HTTP GET response. On success, “200 OK” shall be returned and the message content shall carry the relationships information of an instance of a topology entity type within in a topology domain. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 6.1.4.6 Operation getTopologyRelationshipTypes - -The API Consumer uses this operation to query all topology relationship types in a topology domain. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: GET .../domains/{domainName}/relationship-types -Producer -->> Consumer: 200 OK (RelationshipTypes) -@enduml -``` - -![Sequence diagram for getTopologyRelationshipTypes operation. It shows an API Consumer sending a GET request to an API Producer and receiving a 200 OK response.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: - API Consumer->>API Producer: 1 GET .../domains/{domainName}/relationship-types - API Producer-->>API Consumer: 2 200 OK (RelationshipTypes) - Note right of API Producer: - -``` - -Sequence diagram for getTopologyRelationshipTypes operation. It shows an API Consumer sending a GET request to an API Producer and receiving a 200 OK response. - -**Figure 6.1.4.6-1: getTopologyRelationshipTypes operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../domains/{domainName}/relationship-types) to query all the topology relationship types of a topology entity within a topology domain. -2. The API Producer shall return the HTTP GET response. On success, “200 OK” shall be returned and the message content shall carry the topology relationship types information. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 6.1.4.7 Operation getRelationshipsByType - -The API Consumer uses this operation to query all topology relationship instances of a topology relationship type in a topology domain. - -``` - -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer ->> Producer: GET .../domains/{domainName}/relationship-types/{relationshipTypeName}/relationships -Producer -->> Consumer: 200 OK (Relationships) -@enduml - -``` - -![Sequence diagram for getRelationshipsByType operation. It shows an API Consumer sending a GET request to an API Producer and receiving a 200 OK response.](e9d825d87c5f85c8dba0664eace96ef4_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: - API Consumer->>API Producer: 1 GET .../domains/{domainName}/relationship-types/{relationshipTypeName}/relationships - API Producer-->>API Consumer: 2 200 OK (Relationships) - Note right of API Producer: - -``` - -Sequence diagram for getRelationshipsByType operation. It shows an API Consumer sending a GET request to an API Producer and receiving a 200 OK response. - -**Figure 6.1.4.7-1: getRelationshipsByType operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../domains/{domainName}/relationship-types/{relationshipTypeName}/relationships) to query all topology relationship instances of a topology relationship type. -2. The API Producer shall return the HTTP GET response. On success, “200 OK” shall be returned and the message content shall carry an array of relationship information. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 6.1.4.8 Operation getRelationshipById - -The API Consumer uses this operation to query topology relationship instance of a topology relationship type in a topology domain. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: GET .../domains/{domainName}/relationship-types/{relationshipTypeName}/relationships/{relationshipId} -Producer -->> Consumer: 200 OK (Relationship) -@enduml -``` - -![Sequence diagram for getRelationshipById operation showing a GET request from API Consumer to API Producer and a 200 OK response.](a26e142d3df5bef41a84a9dd099d7825_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 GET .../domains/{domainName}/relationship-types/{relationshipTypeName}/relationships/{relationshipId} - API Consumer->>API Producer: 1 GET .../domains/{domainName}/relationship-types/{relationshipTypeName}/relationships/{relationshipId} - Note right of API Producer: 2 200 OK (Relationship) - API Producer-->>API Consumer: 2 200 OK (Relationship) -``` - -Sequence diagram for getRelationshipById operation showing a GET request from API Consumer to API Producer and a 200 OK response. - -Figure 6.1.4.8-1: getRelationshipById operation - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../domains/{domainName}/relationship-types/{relationshipTypeName}/relationships/{relationshipId}) to query topology relationship instance of a topology relationship type. -2. The API Producer shall return the HTTP GET response. On success, “200 OK” shall be returned and the message content shall carry relationship information of a topology relationship type. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 6.1.4.9 Operation getSchemas - -The API Consumer uses this operation to discover the available schemas. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: GET .../schemas -Producer -->> Consumer: 200 OK (Schemas) -@enduml -``` - -![Sequence diagram for getSchemas operation showing a GET request from API Consumer to API Producer and a 200 OK response.](66c2bf11a8f117cddf67eff92d4c736c_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 GET .../schemas - API Consumer->>API Producer: 1 GET .../schemas - Note right of API Producer: 2 200 OK (Schemas) - API Producer-->>API Consumer: 2 200 OK (Schemas) -``` - -Sequence diagram for getSchemas operation showing a GET request from API Consumer to API Producer and a 200 OK response. - -Figure 6.1.4.9-2: getSchemas Operation - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../schemas) to discover the available topology model schemas. -2. The API Producer shall return the HTTP GET response. On success, “200 OK” shall be returned and the message content shall carry a list of the available topology model schemas. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 6.1.4.10 Operation getSchemaByName - -The API Consumer uses this operation to get the schema by name. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer --> Producer: GET .../schemas/{schemaName}/content -Producer --> Consumer: 200 OK -@enduml -``` - -![Sequence diagram for getSchemaByName operation showing API Consumer sending a GET request to API Producer and receiving a 200 OK response.](9ae17964ddd9b814c7d905b1af2fddf2_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 GET .../schemas/{schemaName}/content - API Consumer->>API Producer: Request - Note right of API Producer: 2 200 OK - API Producer-->>API Consumer: Response -``` - -Sequence diagram for getSchemaByName operation showing API Consumer sending a GET request to API Producer and receiving a 200 OK response. - -Figure 6.1.4.10-3: getSchemaByName Operation - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../schemas/{schemaName}/content) to discover the topology model schema. -2. The API Producer shall return the HTTP GET response. On success, "200 OK" shall be returned and the payload body of the GET response shall contain the obtained resource representation. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 6.1.4.11 Operation getUserDefinedSchema - -The API Consumer uses this operation to discover the available user defined schemas. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer --> Producer: GET .../user-defined-schemas -Producer --> Consumer: 200 OK (UserDefinedSchemas) -@enduml -``` - -![Sequence diagram for getUserDefinedSchema operation. It shows an API Consumer sending a GET request to an API Producer, which responds with a 200 OK containing UserDefinedSchemas.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET .../user-defined-schemas - API Producer-->>API Consumer: 2 200 OK (UserDefinedSchemas) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - -``` - -Sequence diagram for getUserDefinedSchema operation. It shows an API Consumer sending a GET request to an API Producer, which responds with a 200 OK containing UserDefinedSchemas. - -Figure 6.1.4.11-4: getUserDefinedSchema Operation - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../user-defined-schemas) to discover the available user defined schemas. -2. The API Producer shall return the HTTP GET response. On success, “200 OK” shall be returned and the message content shall carry a list of the available user defined schemas. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 6.1.4.12 Operation createUserDefinedSchema - -The API Consumer uses this operation to create new user defined schemas. - -``` - -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: POST .../user-defined-schemas (MultipartFile) -Producer -->> Consumer: 201 Created (UserDefinedSchema) -@enduml - -``` - -![Sequence diagram for createUserDefinedSchema operation. It shows an API Consumer sending a POST request with a MultipartFile to an API Producer, which responds with a 201 Created containing UserDefinedSchema.](6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 POST .../user-defined-schemas (MultipartFile) - API Producer-->>API Consumer: 2 201 Created (UserDefinedSchema) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - -``` - -Sequence diagram for createUserDefinedSchema operation. It shows an API Consumer sending a POST request with a MultipartFile to an API Producer, which responds with a 201 Created containing UserDefinedSchema. - -Figure 6.1.4.12-5: createUserDefinedSchema Operation - -The service operation is as follows: - -1. The API Consumer shall send an HTTP POST request to the API Producer. The target URI shall identify the resource (.../user-defined-schemas) under which the new user defined schema is requested to be created. The message content shall carry a MultipartFile structure. -2. The API Producer shall generate the user defined schema name and construct the URI for the created resource. The API Producer shall return the HTTP POST response. On success, “201 Created” shall be returned. The message shall carry a UserDefinedSchema structure that represents the new resource, and the "Location" header shall contain the URI of the created resource. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 6.1.4.13 Operation deleteUserDefinedSchema - -The API Consumer uses this operation to delete a user defined schema. - -NOTE: Only user defined schemas can be deleted by the TE&IV API Consumer. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: DELETE .../user-defined-schemas/{schemaName} -Producer -->> Consumer: 204 No Content -@enduml -``` - -![Sequence diagram for deleteUserDefinedSchema operation showing API Consumer sending a DELETE request and API Producer responding with 204 No Content.](21ad58fee90f2be50708ff541d225507_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 DELETE ...../user-defined-schemas/{schemaName} - API Producer-->>API Consumer: 2 204 No Content - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram for deleteUserDefinedSchema operation showing API Consumer sending a DELETE request and API Producer responding with 204 No Content. - -Figure 6.1.4.13-6: deleteUserDefinedSchema Operation - -The service operation is as follows: - -1. The API Consumer shall send an HTTP DELETE request to the API Producer. The target URI shall identify the resource (.../user-defined-schemas/{schemaName}) to delete the user defined schema. -2. The API Producer shall return the HTTP DELETE response. On success, “204 No Content” shall be returned. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 6.1.4.14 Operation getUserDefinedSchemaByName - -The API Consumer uses this operation to get the user defined schema by name. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: GET .../user-defined-schemas/{schemaName}/content -Producer -->> Consumer: 200 OK -@enduml -``` - -![Sequence diagram for getUserDefinedSchemaByName operation showing API Consumer sending a GET request and API Producer responding with 200 OK.](6f659142d4789aa889184459f884787e_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET .../user-defined-schemas/{schemaName}/content - API Producer-->>API Consumer: 2 200 OK - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram for getUserDefinedSchemaByName operation showing API Consumer sending a GET request and API Producer responding with 200 OK. - -Figure 6.1.4.14-7: getUserDefinedSchemaByName Operation - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../user-defined-schemas/{schemaName}/content) to discover the content of the user defined schema by specific schema name. -2. The API Producer shall return the HTTP GET response. On success, “200 OK” shall be returned and the message content shall carry a string. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 6.1.4.15 Operation updateClassifier - -The API Consumer uses this operation to update or delete specified entities and/or relationships with classifiers. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: POST .../manage-classifiers (Classifier) -Producer -->> Consumer: 204 No Content -@enduml -``` - -![Sequence diagram for updateClassifier operation showing a POST request from API Consumer to API Producer and a 204 No Content response.](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 POST .../manage-classifiers (Classifier) - API Consumer->>API Producer: 1 POST .../manage-classifiers (Classifier) - Note right of API Producer: 2 204 No Content - API Producer-->>API Consumer: 2 204 No Content -``` - -Sequence diagram for updateClassifier operation showing a POST request from API Consumer to API Producer and a 204 No Content response. - -Figure 6.1.4.15-8: updateClassifier Operation - -The service operation is as follows: - -1. The API Consumer shall send an HTTP POST request to the API Producer. The target URI shall identify the resource (.../manage-classifiers) to update or delete the classifiers associated to the topology entities and topology relationships. The message content shall carry a Classifier structure. -2. The API Producer shall return the HTTP POST response. On success, “204 No Content” shall be returned. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 6.1.4.16 Operation updateDecorator - -The API Consumer uses this operation to update or delete specified entities and/or relationships with decorators. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: POST .../manage-decorators (Decorator) -Producer -->> Consumer: 204 No Content -@enduml -``` - -![Sequence diagram showing the updateDecorator operation. An API Consumer sends a POST request to an API Producer, and the API Producer responds with a 204 No Content status.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: - API Consumer->>API Producer: 1 POST .../manage-decorators (Decorator) - Note right of API Producer: - API Producer-->>API Consumer: 2 204 No Content - Note right of API Consumer: - -``` - -Sequence diagram showing the updateDecorator operation. An API Consumer sends a POST request to an API Producer, and the API Producer responds with a 204 No Content status. - -**Figure 6.1.4.16-9: updateDecorator Operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP POST request to the API Producer. The target URI shall identify the resource (.../manage-decorators) to update or delete the decorators associated to the topology entities and topology relationship. The message content shall carry a Decorator structure. -2. The API Producer shall return the HTTP POST response. On success, “204 No Content ” shall be returned. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -### 6.1.5 Resources - -#### 6.1.5.1 Overview - -The following clause defines the resources for the Topology inventory API. - -#### 6.1.5.2 Resource: "All topology domains" - -##### 6.1.5.2.1 Description - -The resource represents the available topology domains. Only the methods defined in clause 6.1.5.2.3 shall be supported by this resource. - -##### 6.1.5.2.2 Resource Definition - -Resource URI: {apiRoot}/topology-inventory//domains - -The resource URI variables supported by the resource are defined in Table 6.1.5.2.2-1. - -**Table 6.1.5.2.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|-------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 6.1.2. | - -##### 6.1.5.2.3 Resource Standard Methods - -###### 6.1.5.2.3.1 GET - -This method shall support the URI query parameters specified in table 6.1.5.2.3.1-1, URI header parameters specified in 6.1.5.2.3.1-2, the request data structure specified in the table 6.1.5.2.3.1-3 and the response data structure and response code specified in the table 6.1.5.2.3.1-4. - -**Table 6.1.5.2.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|-------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------| -| offsetParam | integer | O | 0..1 | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | integer | O | 0..1 | The query parameter provides to limit the number of entries returned for a request for pagination. | - -**Table 6.1.5.2.3.1-2: URI header parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------| -| Accept | string | M | 1 | This header is used to specify response media types that are acceptable. The default type acceptable for this header is "application/json" | - -**Table 6.1.5.2.3.1-3: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|--------------------------------------------------------------| -| N/A | | | There is no object in the message content of the GET request | - -**Table 6.1.5.2.3.1-4: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|-----------------------------------------------------------------------------------------------------------| -| Domains | M | 1 | 200 OK | The operation was successful.

The message content of the GET response carries a domains structure. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -##### **6.1.5.2.4 Resource Custom Operations** - -None. - -#### **6.1.5.3 Resource: "All topology entity types in a topology domain"** - -##### **6.1.5.3.1 Description** - -The resource represents the available topology entity types in a topology domain. Only the methods defined in clause 6.1.5.3.3 shall be supported by this resource. - -##### **6.1.5.3.2 Resource Definition** - -Resource URI: {apiRoot}/topology-inventory/{apiVersion}/domains/{domainName}/entity-types - -The resource URI variables supported by the resource are defined in Table 6.1.5.3.2-1. - -**Table 6.1.5.3.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|------------------------------| -| apiRoot | See clause 5.2 . | -| apiVersion | See clause 6.1.2. | -| domainName | Name of the Topology Domain. | - -##### 6.1.5.3.3 Resource Standard Methods - -###### 6.1.5.3.3.1 GET - -This method shall support the URI query parameters specified in table 6.1.5.3.3.1-1, URI header parameters specified in 6.1.5.3.3.1-2, the request data structure specified in the table 6.1.5.3.3.1-3 and the response data structure and response code specified in the table 6.1.5.3.3.1-4. - -**Table 6.1.5.3.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|-------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------| -| offsetParam | integer | O | 0..1 | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | integer | O | 0..1 | The query parameter provides to limit the number of entries returned for a request for pagination. | - -**Table 6.1.5.3.3.1-2: URI header parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------| -| Accept | string | M | 1 | This header is used to specify response media types that are acceptable. The default type acceptable for this header is "application/json" | - -**Table 6.1.5.3.3.1-3: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|--------------------------------------------------------------| -| N/A | | | There is no object in the message content of the GET request | - -**Table 6.1.5.3.3.1-4: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|---------------------------------------------------------------------------------------------------------------| -| EntityTypes | M | 1 | 200 OK | The operation was successful.

The message content of the GET response carries a EntityTypes structure. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -##### 6.1.5.3.4 Resource Custom Operations - -None. - -#### 6.1.5.4 Resource: "All instances of a topology entity type in a topology domain" - -##### 6.1.5.4.1 Description - -The resource represents all the available instances of a topology entity types in a topology domain. Only the methods defined in clause 6.1.5.4.3 shall be supported by this resource. - -##### 6.1.5.4.2 Resource Definition - -Resource URI: - -**{apiRoot}/topology-inventory//domains/{domainName}/entity-types/{entityTypeName}/entities** - -The resource URI variables supported by the resource are defined in Table 6.1.5.4.2-1. - -**Table 6.1.5.4.2-1: Resource URI variables for the resource** - -| Name | Definition | -|----------------|-------------------------------------------------| -| apiRoot | See clause 5.2 . | -| apiVersion | See clause 6.1.2. | -| domainName | Name of the Topology Domain. | -| entityTypeName | Name of a topology entity in a topology domain. | - -##### 6.1.5.4.3 Resource Standard Methods - -###### 6.1.5.4.3.1 GET - -This method shall support the URI query parameters specified in table 6.1.5.4.3.1-1, URI header parameters specified in table 6.1.5.4.3.1-2 the request data structure specified in the table 6.1.5.4.3.1-3 and the response data structure and response code specified in the table 6.1.5.4.3.1-4. - -**Table 6.1.5.4.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------| -| targetFilter | string | O | 0..1 | This query parameter specifies the entity type and attributes to be returned in the REST response. | -| scopeFilter | string | O | 0..1 | This query parameter specifies the attributes to match on for specific Topology Entities for which the data is to be produced. | -| offsetParam | integer | O | 0..1 | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | integer | O | 0..1 | The query parameter provides to limit the number of entries returned for a request for pagination. | - -**Table 6.1.5.4.3.1-2: URI header parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------| -| Accept | string | M | 1 | This header is used to specify response media types that are acceptable. The default type acceptable for this header is "application/yang.data+json" | - -**Table 6.1.5.4.3.1-3: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|--------------------------------------------------------------| -| N/A | | | There is no object in the message content of the GET request | - -**Table 6.1.5.4.3.1-4: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|-------------------------------------------------------------------------------------------------------------| -| Entities | M | 1 | 200 OK | The operation was successful.

The message content of the GET response carries an Entities structure. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -##### **6.1.5.4.4 Resource Custom Operations** - -None. - -#### **6.1.5.5 Resource: "Individual instance of a topology entity type in a topology domain"** - -##### **6.1.5.5.1 Description** - -The resource represents the individual available instances of a topology entity types in a topology domain. Only the methods defined in clause 6.1.5.5.3 shall be supported by this resource. - -##### **6.1.5.5.2 Resource Definition** - -Resource URI: - -`{apiRoot}/topology-inventory//domain/{domainName}/entity-types/{entityTypeName}/entities/{entityId}` - -The resource URI variables supported by the resource are defined in Table 6.1.5.5.2-1. - -**Table 6.1.5.5.2-1: Resource URI variables for the resource** - -| Name | Definition | -|----------------|-------------------------------------------------| -| apiRoot | See clause 5.2 . | -| apiVersion | See clause 6.1.2. | -| domainName | Name of the Topology Domain. | -| entityTypeName | Name of a topology entity in a topology domain. | -| entityId | Identifier of an individual topology entity. | - -##### **6.1.5.5.3 Resource Standard Methods** - -###### **6.1.5.5.3.1 GET** - -This method shall support the URI query parameters specified in table 6.1.5.5.3.1-1, URI header parameters specified in table 6.1.5.5.3.1-2, the request data structure specified in the table 6.1.5.5.3.1-3 and the response data structure and response code specified in the table 6.1.5.5.3.1-4. - -**Table 6.1.5.5.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|--------------------------------------------------------------| -| N/A | | | There is no object in the message content of the GET request | - -**Table 6.1.5.5.3.1-2: URI header parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------| -| Accept | string | M | 1 | This header is used to specify response media types that are acceptable. The default type acceptable for this header is "application/yang.data+json" | - -**Table 6.1.5.5.3.1-3: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|--------------------------------------------------------------| -| N/A | | | There is no object in the message content of the GET request | - -**Table 6.1.5.5.3.1-4: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| EntityInstance | M | 1 | 200 OK | The operation was successful.

The message content of the GET response carries an EntityInstance which is an encapsulated object reference to the data model for schema definition of Topology Entity. (NOTE). | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -NOTE: The attributes of a Topology Entity defined in the TE&IV Information Model [9] may be represented in multiple data modelling languages. Irrespective of the data modelling language specified in the Data Model specification [10], in the response, these attributes are encoded in JSON format. For example, attributes of the Topology Entity in the TE&IV Information Model [9] are represented in the YANG data modelling language. This YANG definition will be encoded as JSON using RFC 7951 and is encapsulated in this object. - -##### **6.1.5.5.4 Resource Custom Operations** - -None. - -#### **6.1.5.6 Resource: "All relationships of an instance of a topology entity type in a topology domain"** - -##### **6.1.5.6.1 Description** - -The resource represents the relationships of an instance of a topology entity types in a topology domain. Only the methods defined in clause 6.1.5.6.3 shall be supported by this resource. - -##### **6.1.5.6.2 Resource Definition** - -Resource URI: - -**{apiRoot}/topology-inventory/{apiVersion}/domains/{domainName}/entity-types/{entityTypeName}/entities/{entityId}/relationships** - -The resource URI variables supported by the resource are defined in Table 6.1.5.6.2-1. - -**Table 6.1.5.6.2-1: Resource URI variables for the resource** - -| Name | Definition | -|----------------|-------------------------------------------------| -| apiRoot | See clause 5.2 . | -| apiVersion | See clause 6.1.2. | -| domainName | Name of the Topology Domain. | -| entityTypeName | Name of a topology entity in a topology domain. | -| entityId | Identifier of an individual topology entity. | - -##### **6.1.5.6.3 Resource Standard Methods** - -###### **6.1.5.6.3.1 GET** - -This method shall support the URI query parameters specified in table 6.1.5.6.3.1-1, URI header parameters specified in table 6.1.5.6.3.1-2, the request data structure specified in the table 6.1.5.6.3.1-3 and the response data structure and response code specified in the table 6.1.5.6.3.1-4. - -**Table 6.1.5.6.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------| -| offsetParam | integer | O | 0..1 | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | integer | O | 0..1 | The query parameter provides to limit the number of entries returned for a request for pagination. | -| targetFilter | string | O | 0..1 | This query parameter specifies the entity type and relationship to be returned in the REST response. | -| scopeFilter | string | O | 0..1 | This query parameter specifies the attributes to match on for specific Topology Entity relationship for which the data is to be produced. | - -**Table 6.1.5.6.3.1-2: URI header parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------| -| Accept | string | M | 1 | This header is used to specify response media types that are acceptable. The default type acceptable for this header is "application/yang.data+json" | - -**Table 6.1.5.6.3.1-3: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|--------------------------------------------------------------| -| N/A | | | There is no object in the message content of the GET request | - -**Table 6.1.5.6.3.1-4: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|-----------------------------------------------------------------------------------------------------------------| -| Relationships | M | 1 | 200 OK | The operation was successful.

The message content of the GET response carries a Relationships structure. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -##### **6.1.5.6.4 Resource Custom Operations** - -None. - -#### **6.1.5.7 Resource: "All topology relationship types in a topology domain"** - -##### **6.1.5.7.1 Description** - -The resource represents all the topology relationship types in a topology domain. Only the methods defined in clause 6.1.5.7.3 shall be supported by this resource. - -##### **6.1.5.7.2 Resource Definition** - -Resource URI: - -**{apiRoot}/topology-inventory//domains/{domainName}/relationship-types** - -The resource URI variables supported by the resource are defined in Table 6.1.5.7.2-1. - -**Table 6.1.5.7.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|------------------------------| -| apiRoot | See clause 5.2 . | -| apiVersion | See clause 6.1.2. | -| domainName | Name of the Topology Domain. | - -##### **6.1.5.7.3 Resource Standard Methods** - -###### **6.1.5.7.3.1 GET** - -This method shall support the URI query parameters specified in table 6.1.5.7.3.1-1, URI header parameters specified in table 6.1.5.7.3.1-2, the request data structure specified in the table 6.1.5.7.3.1-3 and the response data structure and response code specified in the table 6.1.5.7.3.1-4. - -**Table 6.1.5.7.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|-------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------| -| offsetParam | integer | O | 0..1 | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | integer | O | 0..1 | The query parameter provides to limit the number of entries returned for a request for pagination. | - -**Table 6.1.5.7.3.1-2: URI header parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------| -| Accept | string | M | 1 | This header is used to specify response media types that are acceptable. The default type acceptable for this header is "application/json" | - -**Table 6.1.5.7.3.1-3: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|--------------------------------------------------------------| -| N/A | | | There is no object in the message content of the GET request | - -**Table 6.1.5.7.3.1-4: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|-------------------|---|-------------|----------------|---------------------------------------------------------------------------------------------------------------------| -| RelationshipTypes | M | 1 | 200 OK | The operation was successful.

The message content of the GET response carries a RelationshipTypes structure. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -##### 6.1.5.7.4 Resource Custom Operations - -None. - -#### 6.1.5.8 Resource: "All topology relationship instances of a topology relationship type" - -##### 6.1.5.8.1 Description - -The resource represents all the topology relationship instances of a topology relationship type in a topology domain. Only the methods defined in clause 6.1.5.8.3 shall be supported by this resource. - -##### 6.1.5.8.2 Resource Definition - -Resource URI: - -**{apiRoot}/topology-inventory/{apiVersion}/domains/{domainName}/relationship-types/{relationshipTypeName}/relationships** - -The resource URI variables supported by the resource are defined in Table 6.1.5.8.2-1. - -**Table 6.1.5.8.2-1: Resource URI variables for the resource** - -| Name | Definition | -|----------------------|--------------------------------------------------------------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 6.1.2. | -| domainName | Name of the Topology Domain. | -| relationshipTypeName | A topology relationship type name such as NF Deployment NF Relationship. | - -##### **6.1.5.8.3 Resource Standard Methods** - -###### **6.1.5.8.3.1 GET** - -This method shall support the URI query parameters specified in table 6.1.5.8.3.1-1, URI header parameters specified in table 6.1.5.8.3.1-2, the request data structure specified in the table 6.1.5.8.3.1-3 and the response data structure and response code specified in the table 6.1.5.8.3.1-4. - -**Table 6.1.5.8.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------| -| offsetParam | integer | O | 0..1 | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | integer | O | 0..1 | The query parameter provides to limit the number of entries returned for a request for pagination. | -| targetFilter | string | O | 0..1 | This query parameter specifies the entity type and attributes to be returned in the REST response. | -| scopeFilter | string | O | 0..1 | This query parameter specifies the attributes to match on for specific Topology Entities for which the data is to be produced. | - -**Table 6.1.5.8.3.1-2: URI header parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------| -| Accept | string | M | 1 | This header is used to specify response media types that are acceptable. The default type acceptable for this header is "application/json" | - -**Table 6.1.5.8.3.1-3: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|---------------------------------------------------------------| -| N/A | | | There is no object in the message content of the GET request. | - -**Table 6.1.5.8.3.1-4: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|-----------------------------------------------------------------------------------------------------------------| -| Relationships | M | 1 | 200 OK | The operation was successful.

The message content of the GET response carries a Relationships structure. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -##### **6.1.5.8.4 Resource Custom Operations** - -None. - -#### **6.1.5.9 Resource: "Individual topology relationship instance of a topology relationship type"** - -##### **6.1.5.9.1 Description** - -The resource represents all the topology relationship instances of a topology relationship type in a topology domain. Only the methods defined in clause 6.1.5.9.3 shall be supported by this resource. - -##### **6.1.5.9.2 Resource Definition** - -Resource URI: - -**{apiRoot}/topology-inventory//domains/{domainName}/relationship-types/{relationshipTypeName}/relationships/{relationshipId}** - -The resource URI variables supported by the resource are defined in Table 6.1.5.9.2-1. - -**Table 6.1.5.9.2-1: Resource URI variables for the resource** - -| Name | Definition | -|----------------------|----------------------------------------------------------------| -| apiRoot | See clause 5.2 . | -| apiVersion | See clause 6.1.2. | -| domainName | Name of the Topology Domain. | -| relationshipTypeName | A topology relationship type name. | -| relationshipId | An identifier of an individual topology relationship instance. | - -##### **6.1.5.9.3 Resource Standard Methods** - -###### **6.1.5.9.3.1 GET** - -This method shall support the URI query parameters specified in table 6.1.5.9.3.1-1, URI header parameters specified in table 6.1.5.9.3.1-2, the request data structure specified in the table 6.1.5.9.3.1-3 and the response data structure and response code specified in the table 6.1.5.9.3.1-4. - -**Table 6.1.5.9.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|---------------------------------------------------------------| -| N/A | | | There is no object in the message content of the GET request. | - -**Table 6.1.5.9.3.1-2: URI header parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| -| Accept | string | M | 1 | This header is used to specify response media types that are acceptable. The default type acceptable for this header is "application/yang.data+json". | - -**Table 6.1.5.9.3.1-3: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|---------------------------------------------------------------| -| N/A | | | There is no object in the message content of the GET request. | - -**Table 6.1.5.9.3.1-4: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Relationship | M | 1 | 200 OK | The operation was successful.

The message content of the GET response carries a Relationship instance which is an encapsulated object reference to the data model for schema definition of Topology Relationship. (NOTE). | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -NOTE: The attributes of a Topology Relationship defined in the TE&IV Information Model [9] may be represented in multiple data modelling languages. Irrespective of the data modelling language specified in the Data Model specification [10], in the response, these attributes are encoded in JSON format. For example, attributes of the Topology Relationship in the TE&IV Information Model [9] are represented in the YANG data modelling language. This YANG definition will be encoded as JSON using RFC 7951 and is encapsulated in this object. - -##### 6.1.5.9.4 Resource Custom Operations - -None. - -#### 6.1.5.10 Resource: "All topology model schemas" - -##### 6.1.5.10.1 Description - -The resource represents all the available topology schema. Only the methods defined in clause 6.1.5.10.3 shall be supported by this resource. - -##### 6.1.5.10.2 Resource Definition - -Resource URI: {apiRoot}/topology-inventory//schemas - -The resource URI variables supported by the resource are defined in Table 6.1.5.10.2-1. - -**Table 6.1.5.10.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|-------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 6.1.2. | - -##### 6.1.5.10.3 Resource Standard Methods - -###### 6.1.5.10.3.1 GET - -This method shall support the URI query parameters specified in table 6.1.5.10.3.1-1, URI header parameters specified in 6.1.5.10.3.1-2, the request data structure specified in the table 6.1.5.10.3.1-3 and the response data structure and response code specified in the table 6.1.5.10.3.1-4. - -**Table 6.1.5.10.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|-------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------| -| domain | string | O | 0..1 | This query parameter allows you to specify the desired domain | -| offsetParam | integer | O | 0..1 | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | integer | O | 0..1 | The query parameter provides to limit the number of entries returned for a request for pagination. | - -**Table 6.1.5.10.3.1-2: URI header parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------| -| Accept | string | M | 1 | This header is used to specify response media types that are acceptable. The default type acceptable for this header is "application/json" | - -**Table 6.1.5.10.3.1-3: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|--------------------------------------------------------------| -| N/A | | | There is no object in the message content of the GET request | - -**Table 6.1.5.10.3.1-4: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|-----------------------------------------------------------------------------------------------------------| -| Schemas | M | 1 | 200 OK | The operation was successful.

The message content of the GET response carries a Schemas structure. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -##### 6.1.5.10.4 Resource Custom Operations - -None. - -#### 6.1.5.11 Resource: "Individual model schema content" - -##### 6.1.5.11.1 Description - -The resource represents the content of a schema instance. Only the methods defined in clause 6.1.5.11.3 shall be supported by this resource. - -##### 6.1.5.11.2 Resource Definition - -Resource URI: {apiRoot}/topology-inventory//schemas/{schemaName}/content - -The resource URI variables supported by the resource are defined in Table 6.1.5.11.2-1. - -**Table 6.1.5.11.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|-----------------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 6.1.2. | -| schemaName | Name of the topology schema | - -##### 6.1.5.11.3 Resource Standard Methods - -###### 6.1.5.11.3.1 GET - -This method shall support the URI query parameters specified in table 6.1.5.11.3.1-1, URI header parameters specified in 6.1.5.11.3.1-2, the request data structure specified in the table 6.1.5.11.3.1-3 and the response data structure and response code specified in the table 6.1.5.11.3.1-4. - -**Table 6.1.5.11.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|------|-----------|---|-------------|-------------| -| N/A | | | | | - -**Table 6.1.5.11.3.1-2: URI header parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------| -| Accept | string | M | 1 | This header is used to specify response media types that are acceptable. The default type acceptable for this header is "text/plain" | - -**Table 6.1.5.11.3.1-3: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|-------------| -| N/A | | | | - -**Table 6.1.5.11.3.1-4: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|------------------------------------------------------------------------------------------------| -| string | M | 1 | 200 OK | The operation was successful. The payload body of the GET response carries the Schema content. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -##### 6.1.5.11.4 Resource Custom Operations - -None. - -#### 6.1.5.12 Resource: "All user defined schemas" - -##### 6.1.5.12.1 Description - -The resource represents all the available user defined schema. Only the methods defined in clause 6.1.5.12.3 shall be supported by this resource. - -##### 6.1.5.12.2 Resource Definition - -Resource URI: {apiRoot}/topology-inventory//user-defined-schemas - -The resource URI variables supported by the resource are defined in Table 6.1.5.12.2-1. - -**Table 6.1.5.12.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|-------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 6.1.2. | - -##### 6.1.5.12.3 Resource Standard Methods - -###### 6.1.5.12.3.1 GET - -This method shall support the URI query parameters specified in table 6.1.5.12.3.1-1, URI header parameters specified in 6.1.5.12.3.1-2, the request data structure specified in the table 6.1.5.12.3.1-3 and the response data structure and response code specified in the table 6.1.5.12.3.1-4. - -**Table 6.1.5.12.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|-------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------| -| offsetParam | integer | O | 0..1 | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | integer | O | 0..1 | The query parameter provides to limit the number of entries returned for a request for pagination. | - -**Table 6.1.5.12.3.1-2: URI header parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------| -| Accept | string | M | 1 | This header is used to specify response media types that are acceptable. The default type acceptable for this header is "application/json" | - -**Table 6.1.5.12.3.1-3: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|--------------------------------------------------------------| -| N/A | | | There is no object in the message content of the GET request | - -**Table 6.1.5.12.3.1-4: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|--------------------|---|-------------|----------------|---------------------------------------------------------------------------------------------------------------| -| UserDefinedSchemas | M | 1 | 200 OK | The operation was successful.
The payload body of the GET response carries a UserDefinedSchemas structure. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -###### 6.1.5.12.3.2 POST - -This method shall support the URI query parameters specified in table 6.1.5.12.3.2-1, URI header parameters specified in 6.1.5.12.3.2-2, the request data structure specified in the table 6.1.5.12.3.2-3 and the response data structure and response code specified in the table 6.1.5.12.3.2-4. - -**Table 6.1.5.12.3.2-1: URI query parameters supported by the POST method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|------|-----------|---|-------------|-------------| -| N/A | | | | | - -**Table 6.1.5.12.3.2-2: URI header parameters supported by the POST method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Accept | string | M | 1 | This header is used to specify response media types that are acceptable. The default type acceptable for this header is "application/json" | -| Content-Type | string | M | 1 | This header is used to specify resource media types that are acceptable. The default type acceptable for this header is "multipart/form-data" as per RFC 7578 [x] | - -**Table 6.1.5.12.3.2-3: Data structures supported by the POST request body on this resource.** - -| Data Type | P | Cardinality | Description | -|---------------|---|-------------|------------------------------------------------------------------| -| MultipartFile | M | 1 | Multipart file containing the user defined schema to be created. | - -**Table 6.1.5.12.3.2-4: Data structures supported by the POST response body on this resource** - -| Data Type | P | Cardinality | Response codes | Description | -|-------------------|---|-------------|----------------|----------------------------------------------------------------------------------------------------------------------| -| UserDefinedSchema | M | 1 | 201 Created | The operation was successful.

The message content of the POST response carries a UserDefinedSchema structure. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -**Table 6.1.5.12.3.2-5: Headers supported by the 201 Response code on this resource** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------| -| Location | M | 1 | Contains the URI of the newly created “Individual User Defined Schema” resource as defined in clause 6.1.5.12 | - -##### **6.1.5.12.4 Resource Custom Operations** - -None. - -#### **6.1.5.13 Resource: "Individual user defined schema"** - -##### **6.1.5.13.1 Description** - -The resource represents an individual user defined schema. Only the methods defined in clause 6.1.5.13.3 shall be supported by this resource. - -##### **6.1.5.13.2 Resource Definition** - -Resource URI: {apiRoot}/topology-inventory//user-defined-schemas/{schemaName} - -The resource URI variables supported by the resource are defined in Table 6.1.5.13.2-1. - -**Table 6.1.5.13.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|-----------------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 6.1.2. | -| schemaName | Name of user defined schema | - -##### **6.1.5.13.3 Resource Standard Methods** - -###### **6.1.5.13.3.1 DELETE** - -This method shall support the URI query parameters specified in table 6.1.5.13.3.1-1, URI header parameters specified in 6.1.5.13.3.1-2, the request data structure specified in the table 6.1.5.13.3.1-3 and the response data structure and response code specified in the table 6.1.5.13.3.1-4. - -**Table 6.1.5.13.3.1-1: URI query parameters supported by the DELETE method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|------|-----------|---|-------------|-------------| -| N/A | | | | | - -**Table 6.1.5.13.3.1-2: URI header parameters supported by the DELETE method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------| -| Accept | string | M | 1 | This header is used to specify response media types that are acceptable. The default type acceptable for this header is "application/json" | - -**Table 6.1.5.13.3.1-3: Data structures supported by the DELETE request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|-------------| -| N/A | | | | - -**Table 6.1.5.13.3.1-4: Data structures supported by the DELETE response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|--------------------------------------------------------------------------------------------| -| N/A | | | 204 No Content | The operation was successful | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -##### 6.1.5.13.4 Resource Custom Operations - -None. - -#### 6.1.5.14 Resource: "Individual user defined schema content" - -##### 6.1.5.14.1 Description - -The resource represents the content of a user defined schema instance. Only the methods defined in clause 6.1.5.14.3 shall be supported by this resource. - -##### 6.1.5.14.2 Resource Definition - -Resource URI: {apiRoot}/topology-inventory//user-defined-schemas/{schemaName}/content - -The resource URI variables supported by the resource are defined in Table 6.1.5.14.2-1. - -**Table 6.1.5.14.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|-----------------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 6.1.2. | -| schemaName | Name of the topology schema | - -##### 6.1.5.14.3 Resource Standard Methods - -###### 6.1.5.14.3.1 GET - -This method shall support the URI query parameters specified in table 6.1.5.14.3.1-1, URI header parameters specified in 6.1.5.14.3.1-2, the request data structure specified in the table 6.1.5.14.3.1-3 and the response data structure and response code specified in the table 6.1.5.14.3.1-4. - -**Table 6.1.5.14.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|------|-----------|---|-------------|-------------| -| N/A | | | | | - -**Table 6.1.5.14.3.1-2: URI header parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------| -| Accept | string | M | 1 | This header is used to specify response media types that are acceptable. The default type acceptable for this header is "text/plain" | - -**Table 6.1.5.14.3.1-3: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|-------------| -| N/A | | | | - -**Table 6.1.5.14.3.1-4: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|-------------------------------------------------------------------------------------------------------------| -| string | M | 1 | 200 OK | The operation was successful. The payload body of the GET response carries the user defined schema content. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -##### **6.1.5.14.4 Resource Custom Operations** - -None. - -### **6.1.6 Custom operations without associated resources** - -#### **6.1.6.1 Overview** - -The following clause defines the custom operations for the Topology Inventory API. - -#### **6.1.6.2 Operation: manage-classifiers** - -##### **6.1.6.2.1 Description** - -This custom operation allows the API consumer to manage (add/remove) classifiers on entities and/or relationships. - -##### **6.1.6.2.2 Operation Definition** - -Custom Operation URI: {apiRoot}/topology-inventory//manage-classifiers - -This operation shall support the URI header parameters specified in 6.1.6.2.2.1-1, the request data structure specified in the table 6.1.6.2.2.1-2 and the response data structure and response code specified in the table 6.1.6.2.2.1-3. - -**Table 6.1.6.2.2.1-1: URI header parameters supported by the POST method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------| -| Accept | string | M | 1 | This header is used to specify response media types that are acceptable. The default type acceptable for this header is "application/json" | -| Content-Type | string | M | 1 | This header is used to specify resource media types that are acceptable. The default type acceptable for this header is "application/json" | - -**Table 6.1.6.2.2.1-2: Data structures supported by the POST request body on this resource.** - -| Data Type | P | Cardinality | Description | -|------------|---|-------------|-------------------------------------------------------| -| Classifier | M | 1 | Classifier Schema to update or delete the classifiers | - -**Table 6.1.6.2.2.1-3: Data structures supported by the POST response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|--------------------------------------------------------------------------------------------| -| N/A | | | 204 No Content | The operation has succeeded. There is no message content | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -#### 6.1.6.3 Operation: manage-decorators - -##### 6.1.6.3.1 Description - -This custom operation allows the API consumer to manage (add/remove) decorators on entities and/or relationships. - -##### 6.1.6.3.2 Operation Definition - -Custom Operation URI: {apiRoot}/topology-inventory//manage-decorators - -This operation shall support the URI header parameters specified in 6.1.6.3.2.1-1, the request data structure specified in the table 6.1.6.3.2.1-2 and the response data structure and response code specified in the table 6.1.6.3.2.1-3. - -**Table 6.1.6.3.2.1-1: URI header parameters supported by the POST method on this resource.** - -| Name | Data type | P | Cardinality | Description | -|--------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------| -| Accept | string | M | 1 | This header is used to specify response media types that are acceptable. The default type acceptable for this header is "application/json" | -| Content-Type | string | M | 1 | This header is used to specify resource media types that are acceptable. The default type acceptable for this header is "application/json" | - -**Table 6.1.6.3.2.1-2: Data structures supported by the POST request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|-----------------------------------------------------| -| Decorator | M | 1 | Decorator Schema to update or delete the decorators | - -**Table 6.1.6.3.2.1-3: Data structures supported by the POST response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|--------------------------------------------------------------------------------------------| -| N/A | | | 204 No Content | The operation has succeeded. There is no message content. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -### 6.1.7 Notifications - -None. - -### 6.1.8 Data model - -#### 6.1.8.1 Structured data types - -##### 6.1.8.1.1 Overview - -The following clauses define the structured data types and their attributes to be used by the service API. - -##### 6.1.8.1.2 Data type: Domains - -The Domains data type represents domains. It contains the attributes defined in table 6.1.8.1.2-1. - -**Table 6.1.8.1.2-1: Definition of type Domains.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|---------------|---|-------------|--------------------| -| items | array(Domain) | M | 0..N | A list of domains. | - -##### 6.1.8.1.3 Data type: Domain - -The Domain data type represents the properties of a topology domain. It contains the attributes defined in table 6.1.8.1.3-1. - -**Table 6.1.8.1.3-1: Definition of type Domain.** - -| Attribute Name | Data type | P | Cardinality | Description | -|-------------------|-----------|---|-------------|-----------------------------------------------------------------| -| domainName | string | M | 1 | A name of the topology domain. | -| entityTypes | Href | M | 1 | A reference to entity types of the Topology Entity. | -| relationshipTypes | Href | M | 1 | A reference to relationship types of the Topology Relationship. | - -##### 6.1.8.1.4 Data type: EntityTypes - -The EntityTypes data type represents entity type within a topology domain. It contains the attributes defined table 6.1.8.1.4-1. - -**Table 6.1.8.1.4-1: Definition of type EntityTypes.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-------------------|---|-------------|------------------------------------------| -| items | array(EntityType) | M | 1..N | An entity type within a topology domain. | - -##### 6.1.8.1.5 Data type: EntityType - -The EntityType data type represents a type within a topology domain. - -**Table 6.1.8.1.5-1: Definition of type EntityType.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-----------|---|-------------|-----------------------------------------------------------------------| -| entityTypeName | string | M | 1 | A name of a topology Entity Type. | -| entities | Href | M | 1 | A reference to topology entities of the specific topology Entity Type | - -##### 6.1.8.1.6 Data type: Entities - -The Entities data type represents all instances of a specific topology entity type within a topology domain. It contains the attributes defined in table 6.1.8.1.6-1. - -**Table 6.1.8.1.6-1: Definition of type Entities.** - -| Attribute Name | Data type | P | Cardinality | Description | -|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------| -| items | array(object) | M | 1..N | Topology Entity instances encapsulated as array of objects and refers to the data model for schema definition of Topology Entity. (NOTE). | -| NOTE: The attributes of a Topology Entity defined in the TE&IV Information Model [9] may be represented in multiple data modelling languages. Irrespective of the data modelling language specified in the Data Model specification [10], in the response, these attributes are encoded in JSON format. For example, attributes of the Topology Entity in the TE&IV Information Model [9] are represented in the YANG data modelling language. This YANG definition will be encoded as JSON using RFC 7951 and is encapsulated in this object. | | | | | - -##### 6.1.8.1.7 Data type: Relationships - -The Relationships data type represents relationships information of an instance of a topology entity type within a topology domain. It contains the attributes defined in table 6.1.8.1.7-1. - -**Table 6.1.8.1.7-1: Definition of type Relationships.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---|-------------|---------------------------------------------------------------------------------------------------------| -| items | array(object) | M | 1..N | Encapsulated object reference to the data model for schema definition of Topology Relationship. (NOTE). | -| NOTE: The attributes of the Topology Relationship of a Topology Entity defined in the TE&IV Information Model [9] may be represented in multiple data modelling languages. Irrespective of the data modelling language specified in the Data Model specification [10], in the response, these attributes are encoded in JSON format. For example, attributes of the Topology Relationship of a Topology Entity in a TE&IV REL-RAN-Cloud domain in the TE&IV Information Model [9] are represented in the YANG data modelling language. This YANG definition will be encoded as JSON using RFC 7951 and is encapsulated in this object. | | | | | - -##### 6.1.8.1.8 Data type: RelationshipTypes - -The Relationships data type represents all the relationships information of a topology entity type within a topology domain. It contains the attributes defined in table 6.1.8.1.8-1. - -**Table 6.1.8.1.8-1: Definition of type RelationshipTypes.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-------------------------|---|-------------|-----------------------------------------------------------------| -| items | array(RelationshipType) | M | 1..N | All the relationship type information within a topology domain. | - -##### 6.1.8.1.9 Data type: RelationshipType - -The relationship information in a topology domain. It contains the attributes defined in table 6.1.8.1.9-1. - -**Table 6.1.8.1.9-1: Definition of type RelationshipType.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------------|-----------|---|-------------|-------------------------------------------------------------| -| relationshipTypeName | string | M | 1 | Name of a Topology Relationship. | -| relationships | Href | M | 1 | URI to the relationships of the Topology Relationship Type. | - -##### 6.1.8.1.10 Data type: Href - -This attribute provide reference to entity type and relationship type. It contains the attributes defined in table 6.1.8.1.10-1. - -**Table 6.1.8.1.10-1: Definition of type Href** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-----------|---|-------------|----------------------------------------------------------| -| href | string | M | 1 | The format of the string according to IETF RFC 3986 [6]. | - -##### 6.1.8.1.11 Data type: Schemas - -The Schema data type represents a topology or user defined schema. It contains the attributes defined in table 6.1.8.1.11-1. - -**Table 6.1.8.1.11-1: Definition of type Schemas.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|---------------|---|-------------|------------------| -| items | array(Schema) | M | 1..N | List of schemas. | - -##### 6.1.8.1.12 Data type: Schema - -The Schema data type represents a topology model or user defined schema. It contains the attributes defined in table 6.1.8.1.12-1. - -**Table 6.1.8.1.12-1: Definition of type Schema.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-----------|---|-------------|----------------------------------------------------------------------------------| -| name | string | M | 1 | Name of the schema | -| domain | string | M | 0..1 | Domain where schema is set. | -| revision | string | M | 1 | Revision date of the YANG schema, as defined in the module's revision statement. | -| content | Href | M | 1 | URI to the schema content. Data type is defined in clause 6.1.8.1.10. | - -##### 6.1.8.1.13 Data type: UserDefinedSchemas - -The UserDefinedSchema data type represents a user defined schema. It contains the attributes defined in table 6.1.8.1.13-1. - -**Table 6.1.8.1.13-1: Definition of type UserDefinedSchemas.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|--------------------------|---|-------------|-------------------------------| -| items | array(UserDefinedSchema) | M | 1..N | List of user defined schemas. | - -##### 6.1.8.1.14 Data type: UserDefinedSchema - -The UserDefinedSchema data type represents a user defined schema. It contains the attributes defined in table 6.1.8.1.14-1. - -**Table 6.1.8.1.14-1: Definition of type UserDefinedSchema.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-----------|---|-------------|----------------------------------------------------------------------------------| -| name | string | M | 1 | Name of the user defined schema | -| revision | string | M | 1 | Revision date of the YANG schema, as defined in the module's revision statement. | -| content | Href | M | 1 | URI to the schema content. Data type is defined in clause 6.1.8.1.10. | - -##### 6.1.8.1.15 Data type: MultipartFile - -The MultipartFile data type represents a Multipart File. It contains the attributes defined in table 6.1.8.1.15-1. - -**Table 6.1.8.1.15-1: Definition of type MultipartFile.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-----------|---|-------------|------------------------------------------| -| file | string | M | 1 | File containing a schema in YANG format. | - -##### 6.1.8.1.16 Data type: Classifier - -The Classifier data type represents a classifier. It contains the attributes defined in table 6.1.8.1.16-1. - -**Table 6.1.8.1.16-1: Definition of type Classifier.** - -| Attribute Name | Data type | P | Cardinality | Description | -|-----------------|---------------|---|-------------|-----------------------------------------------------------------------------------------------| -| operation | ENUM | M | 1 | Indicates whether the classifier is to be merged or deleted.
Allowed values: merge, delete | -| classifiers | array(String) | M | 1..N | The strings to be used as classifiers | -| entityIds | array(String) | M | 0..N | Ids of the relationships to be classified | -| relationshipIds | array(String) | M | 0..N | Ids of the relationships to be classified | - -##### 6.1.8.1.17 Data type: Decorator - -The Decorator data type represents a decorator. It contains the attributes defined in table 6.1.8.1.17-1. - -**Table 6.1.8.1.17-1: Definition of type Decorator.** - -| Attribute Name | Data type | P | Cardinality | Description | -|-----------------|--------------------|---|-------------|--------------------------------------------------------------------------------------------------| -| operation | ENUM | M | 1 | Indicates whether the decorator is to be merged or deleted
Allowed values: merge, delete | -| decorators | AttributeValuePair | M | 1..N | The key-value pairs to be used as decorators.
Allowed values: Any string, integer, or boolean | -| entityIds | array(String) | M | 0..N | Ids of the entities to be decorated | -| relationshipIds | array(String) | M | 0..N | Ids of the relationships to be decorated | - -#### 6.1.8.2 Simple data types and enumerations - -The following clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. - -##### 6.1.8.2.1 Simple data types - -For this service API, no simple data types are defined in the present document - -##### 6.1.8.2.2 Enumerations - -For this service API, no enumerations are defined in the present document. - -### 6.1.9 Error Handling - -#### 6.1.9.1 General - -For the Topology Inventory API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [3]. Protocol errors and application errors specified in table 5.2.7.2-1 of 3GPP TS 29.500 [2] shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in table 5.2.7.1-1 of 3GPP TS 29.500 [2]. - -In addition, the requirements in the following clauses are applicable for the Topology Inventory API. - -#### 6.1.9.2 Protocol Errors - -No specific protocol errors are defined in the present document. - -#### 6.1.9.3 Application Errors - -No additional application errors defined in the present document. - -# --- Annex A (normative): OpenAPI Specifications - -## A.1 Overview - -This Annex formally specifies the RESTful Topology & Inventory API by defining OpenAPI documents in YAML format that comply with the OpenAPI 3.0.3 Specification [11]. - -The Open API specifications of the RESTful Topology & Inventory API provided in this annex are versioned as described in clause 5.2. - -## A.2 Topology & Inventory API - -``` -openapi: 3.0.3 -info: - title: 'Topology & Inventory API' - version: 1.2.1 - description: | - API for Topology and Inventory API. - - Topology and Inventory data is the information that represents entities - in a telecommunications network and the relationships between them that - provide insight into a particular aspect of the network of importance to - specific use cases. Topology and Inventory data can be derived from - inventory, configuration, or other data. - - Topology and Inventory supports several topology domains. A domain is a - grouping of topology and inventory entities that handles topology and - inventory data. - - Entities are enabling the modelling and storage of complex network - infrastructure and relationships. - - A relationship is a bi-directional connection between two entities, one -``` - -of which is the originating side (A-side) and the other is the terminating side (B-side). The order of the sides matters since it defines the relationship itself which must be unique. - -Classifier (also known as tag or label) permits the association of a well defined user specified string with an entity or relationship. - -Decorators are user-defined attributes (key-value pairs) which can be applied to topology entities and relationships. - -Topology and Inventory API provides the capabilities to fetch topology data. Using the filtering options, it is possible to define more specific query requests. - -Copyright 2026 O-RAN ALLIANCE e.V. - -Licensed under the Standards Collaboration -Copyright License Version 1.0 (the "License"); -You may not use this file except in compliance with the License. -You may obtain a copy of the License at - - -### tags: - -- name: Entities and relationships -description: Provides the capability to retrieve topology and inventory entities and relationships. -- name: Schemas -description: Schemas are defined in YANG modeling language. A group of Yang schemas makes the topology & inventory model, which represents topology & inventory entities, their attributes, and their relationships. -- name: User Defined Schemas -description: User defined schemas are defined in YANG modeling language. -- name: Classifiers -description: Provides the capability to update or remove user-defined keywords or tags on entities and relationships. -- name: Decorators -description: Provides the capability to update or remove user-defined values on entities and relationships. - -### externalDocs: - -description: 'O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00' -url: 'https://www.o-ran.org/specifications' - -### servers: - -- url: '{apiRoot}/topology-inventory/v1' -variables: -apiRoot: -description: apiRoot as defined in clause 5.3 in O-RAN.WG10.TS.TE&IV-API.0 -default: 'https://example.com' - -### paths: - -/domains: -get: -description: Get all the available topology domains. -tags: -- Entities and relationships -summary: Get all the available topology domains. -operationId: getAllDomains -parameters: -- \$ref: '#/components/parameters/acceptJsonInHeader' -- \$ref: '#/components/parameters/offsetParam' -- \$ref: '#/components/parameters/limitParam' -responses: -'200': -description: OK -content: -application/json: -schema: -\$ref: '#/components/schemas/Domains' -'400': -\$ref: '#/components/responses/400' -'401': - -``` - - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '406': - $ref: '#/components/responses/406' - '414': - $ref: '#/components/responses/414' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '502': - $ref: '#/components/responses/502' - '503': - $ref: '#/components/responses/503' -/domains/{domainName}/entity-types: - get: - description: Get all the available topology entity types within a domain. - tags: - - Entities and relationships - summary: Get all the available topology entity types within a domain. - operationId: getTopologyEntityTypes - parameters: - - $ref: '#/components/parameters/acceptJsonInHeader' - - $ref: '#/components/parameters/domainNameInPath' - - $ref: '#/components/parameters/offsetParam' - - $ref: '#/components/parameters/limitParam' - responses: - '200': - description: OK - content: - application/json: - schema: - $ref: '#/components/schemas/EntityTypes' - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '406': - $ref: '#/components/responses/406' - '414': - $ref: '#/components/responses/414' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '502': - $ref: '#/components/responses/502' - '503': - $ref: '#/components/responses/503' - -/domains/{domainName}/entity-types/{entityTypeName}/entities: - get: - description: Get all Topology Entity instances of a specific Topology Entity type. - tags: - - Entities and relationships - summary: Get all Topology Entity instances of a specific Topology Entity type. - operationId: getTopologyByEntityTypeName - parameters: - - $ref: '#/components/parameters/acceptJsonInHeader' - - $ref: '#/components/parameters/domainNameInPath' - - $ref: '#/components/parameters/entityTypeNameInPath' - - $ref: '#/components/parameters/targetFilterOptionalInQuery' - - $ref: '#/components/parameters/scopeFilterOptionalInQuery' - - $ref: '#/components/parameters/offsetParam' - -``` - -``` - -- $ref: '#/components/parameters/limitParam' -responses: - '200': - description: OK - content: - application/json: - schema: - $ref: '#/components/schemas/Entities' - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '406': - $ref: '#/components/responses/406' - '414': - $ref: '#/components/responses/414' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '502': - $ref: '#/components/responses/502' - '503': - $ref: '#/components/responses/503' - -/domains/{domainName}/entity-types/{entityTypeName}/entities/{entityId}: -get: - description: Get a specific Topology Entity instance of a Topology Entity type - tags: - - Entities and relationships - summary: Get a specific Topology Entity instance of a Topology Entity type - operationId: getTopologyById - parameters: - - $ref: '#/components/parameters/acceptYangJsonInHeader' - - $ref: '#/components/parameters/domainNameInPath' - - $ref: '#/components/parameters/entityTypeNameInPath' - - $ref: '#/components/parameters/entityIdInPath' - responses: - '200': - description: OK - content: - application/yang.data+json: - schema: - type: object - description: Encapsulated object reference to the data model for schema definition of -Topology Entity - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '406': - $ref: '#/components/responses/406' - '414': - $ref: '#/components/responses/414' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '502': - $ref: '#/components/responses/502' - '503': - $ref: '#/components/responses/503' - -``` - -``` - -/domains/{domainName}/entity-types/{entityTypeName}/entities/{entityId}/relationships: -get: - description: Get all relationships for a specific Topology Entity instance of a Topology Entity type - tags: - - Entities and relationships - summary: Get all relationships for a specific Topology Entity instance of a Topology Entity type - operationId: getAllRelationshipsForEntityId - parameters: - - $ref: '#/components/parameters/acceptYangJsonInHeader' - - $ref: '#/components/parameters/domainNameInPath' - - $ref: '#/components/parameters/entityTypeNameInPath' - - $ref: '#/components/parameters/entityIdInPath' - - $ref: '#/components/parameters/targetFilterOptionalInQuery' - - $ref: '#/components/parameters/scopeFilterOptionalInQuery' - - $ref: '#/components/parameters/offsetParam' - - $ref: '#/components/parameters/limitParam' - responses: - '200': - description: OK - content: - application/yang.data+json: - schema: - $ref: '#/components/schemas/Relationships' - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '406': - $ref: '#/components/responses/406' - '414': - $ref: '#/components/responses/414' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '502': - $ref: '#/components/responses/502' - '503': - $ref: '#/components/responses/503' - -/domains/{domainName}/relationship-types: -get: - description: Get all the available Topology Relationship types. - tags: - - Entities and relationships - summary: Get all the available topology relationship types. - operationId: getTopologyRelationshipTypes - parameters: - - $ref: '#/components/parameters/acceptJsonInHeader' - - $ref: '#/components/parameters/domainNameInPath' - - $ref: '#/components/parameters/offsetParam' - - $ref: '#/components/parameters/limitParam' - responses: - '200': - description: OK - content: - application/json: - schema: - $ref: '#/components/schemas/RelationshipTypes' - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - -``` - -``` - - '406': - $ref: '#/components/responses/406' - '414': - $ref: '#/components/responses/414' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '502': - $ref: '#/components/responses/502' - '503': - $ref: '#/components/responses/503' - -/domains/{domainName}/relationship-types/{relationshipTypeName}/relationships: - get: - description: Get all the available Topology Relationships of a specific relationship type name - tags: - - Entities and relationships - summary: Get all the available Topology Relationships of a specific relationship type name. - operationId: getRelationshipsByType - parameters: - - $ref: '#/components/parameters/acceptYangJsonInHeader' - - $ref: '#/components/parameters/domainNameInPath' - - $ref: '#/components/parameters/relationshipTypeNameInPath' - - $ref: '#/components/parameters/targetFilterOptionalInQuery' - - $ref: '#/components/parameters/scopeFilterOptionalInQuery' - - $ref: '#/components/parameters/offsetParam' - - $ref: '#/components/parameters/limitParam' - responses: - '200': - description: OK - content: - application/json: - schema: - $ref: '#/components/schemas/Relationships' - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '406': - $ref: '#/components/responses/406' - '414': - $ref: '#/components/responses/414' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '502': - $ref: '#/components/responses/502' - '503': - $ref: '#/components/responses/503' - -/domains/{domainName}/relationship-types/{relationshipTypeName}/relationships/{relationshipId}: - get: - description: Get a specific Topology Relationship instance of a Topology Relationship type. - tags: - - Entities and relationships - summary: Get a specific Topology Relationship instance of a Topology Relationship type. - operationId: getRelationshipById - parameters: - - $ref: '#/components/parameters/acceptYangJsonInHeader' - - $ref: '#/components/parameters/domainNameInPath' - - $ref: '#/components/parameters/relationshipTypeNameInPath' - - $ref: '#/components/parameters/relationshipIdInPath' - responses: - '200': - description: OK - -``` - -``` - -content: - application/yang.data+json: - schema: - type: object - description: Encapsulated object reference to the data model for schema definition of -Topology Relationship - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '406': - $ref: '#/components/responses/406' - '414': - $ref: '#/components/responses/414' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '502': - $ref: '#/components/responses/502' - '503': - $ref: '#/components/responses/503' -/schemas: - get: - description: Get a list of all topology model schemas. - tags: - - Schemas - summary: Get a list of all user defined schemas. - operationId: getSchemas - parameters: - - $ref: '#/components/parameters/acceptJsonInHeader' - - $ref: '#/components/parameters/domainOptionalInQuery' - - $ref: '#/components/parameters/offsetParam' - - $ref: '#/components/parameters/limitParam' - responses: - '200': - description: OK - content: - application/json: - schema: - $ref: '#/components/schemas/Schemas' - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '406': - $ref: '#/components/responses/406' - '414': - $ref: '#/components/responses/414' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '502': - $ref: '#/components/responses/502' - '503': - $ref: '#/components/responses/503' -/schemas/{schemaName}/content: - get: - description: Get the model schema by name. - tags: - - Schemas - summary: Get the model schema. - -``` - -``` - -operationId: getSchemaByName -parameters: - - $ref: '#/components/parameters/acceptPlainTextInHeader' - - $ref: '#/components/parameters/schemaNameInPath' -responses: - '200': - description: OK - content: - text/plain: - schema: - type: string - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '406': - $ref: '#/components/responses/406' - '414': - $ref: '#/components/responses/414' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '502': - $ref: '#/components/responses/502' - '503': - $ref: '#/components/responses/503' -/user-defined-schemas: - post: - description: Create a new user defined schema. The request body contains the schema in YANG format. - tags: - - User Defined Schemas - summary: Create a new user defined schema. - operationId: createUserDefinedSchema - parameters: - - $ref: '#/components/parameters/acceptJsonInHeader' - - $ref: '#/components/parameters/contentTypeMultipartFileInHeader' - requestBody: - required: true - content: - multipart/form-data: - schema: - $ref: '#/components/schemas/MultipartFile' - responses: - '201': - description: Created - content: - application/json: - schema: - $ref: '#/components/schemas/UserDefinedSchema' - headers: - Location: - description: Contains the URI of the newly created resource - required: true - schema: - type: string - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '409': - $ref: '#/components/responses/409' - '411': - -``` - -``` - - $ref: '#/components/responses/411' - '413': - $ref: '#/components/responses/413' - '415': - $ref: '#/components/responses/415' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '502': - $ref: '#/components/responses/502' - '503': - $ref: '#/components/responses/503' -get: - description: Get a list of all user defined schemas. - tags: - - User Defined Schemas - summary: Get a list of all user defined schemas. - operationId: getUserDefinedSchemas - parameters: - - $ref: '#/components/parameters/acceptJsonInHeader' - - $ref: '#/components/parameters/offsetParam' - - $ref: '#/components/parameters/limitParam' - responses: - '200': - description: OK - content: - application/json: - schema: - $ref: '#/components/schemas/UserDefinedSchemas' - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '406': - $ref: '#/components/responses/406' - '414': - $ref: '#/components/responses/414' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '502': - $ref: '#/components/responses/502' - '503': - $ref: '#/components/responses/503' -/user-defined-schemas/{schemaName}/content: -get: - description: Get the user defined schema by name. - tags: - - User Defined Schemas - summary: Get the user defined schema. - operationId: getUserDefinedSchemaByName - parameters: - - $ref: '#/components/parameters/acceptPlainTextInHeader' - - $ref: '#/components/parameters/schemaNameInPath' - responses: - '200': - description: OK - content: - text/plain: - schema: - type: string - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - -``` - -``` - - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '406': - $ref: '#/components/responses/406' - '414': - $ref: '#/components/responses/414' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '502': - $ref: '#/components/responses/502' - '503': - $ref: '#/components/responses/503' - /user-defined-schemas/{schemaName}: - delete: - description: Delete a user defined schema. - tags: - - User Defined Schemas - summary: Delete a user defined schema. - operationId: deleteUserDefinedSchema - parameters: - - $ref: '#/components/parameters/acceptJsonInHeader' - - $ref: '#/components/parameters/schemaNameInPath' - responses: - '204': - $ref: '#/components/responses/204' - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '502': - $ref: '#/components/responses/502' - '503': - $ref: '#/components/responses/503' - - /manage-classifiers: - post: - description: Update entities and/or relationships with classifier(s). - tags: - - Classifiers - summary: Update entities and/or relationships with classifier(s). - operationId: updateClassifier - parameters: - - $ref: '#/components/parameters/acceptJsonInHeader' - - $ref: '#/components/parameters/contentTypeJsonInHeader' - requestBody: - required: true - content: - application/json: - schema: - $ref: '#/components/schemas/Classifier' - responses: - '204': - $ref: '#/components/responses/204' - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - -``` - -``` - - '404': - $ref: '#/components/responses/404' - - '411': - $ref: '#/components/responses/411' - '413': - $ref: '#/components/responses/413' - '415': - $ref: '#/components/responses/415' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '502': - $ref: '#/components/responses/502' - '503': - $ref: '#/components/responses/503' - -/manage-decorators: - post: - description: Update entities and/or relationships with decorator(s). - tags: - - Decorators - summary: Update entities and/or relationships with decorator(s). - operationId: updateDecorator - parameters: - - $ref: '#/components/parameters/acceptJsonInHeader' - - $ref: '#/components/parameters/contentTypeJsonInHeader' - requestBody: - required: true - content: - application/json: - schema: - $ref: '#/components/schemas/Decorator' - responses: - '204': - $ref: '#/components/responses/204' - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - - '411': - $ref: '#/components/responses/411' - '413': - $ref: '#/components/responses/413' - '415': - $ref: '#/components/responses/415' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '502': - $ref: '#/components/responses/502' - '503': - $ref: '#/components/responses/503' - -components: - schemas: - Classifier: - type: object - title: Classifier - properties: - operation: - type: string - enum: - - merge - -``` - -``` - - - delete -classifiers: - type: array - items: - type: string -entityIds: - type: array - items: - type: string -relationshipIds: - type: array - items: - type: string -Decorator: - type: object - title: Decorator - properties: - operation: - type: string - enum: - - merge - - delete - decorators: - type: object - additionalProperties: true - description: Decorators must be defined in schema before use. Data type of a decorator is -restricted as defined by its schema. - entityIds: - type: array - items: - type: string - relationshipIds: - type: array - items: - type: string -Domains: - type: object - title: Domains - properties: - items: - type: array - items: - type: object - properties: - domainName: - type: string - entityTypes: - $ref: '#/components/schemas/Href' - relationshipTypes: - $ref: '#/components/schemas/Href' - required: ['domainName', 'entityTypes', 'relationshipTypes'] - required: ['items'] -EntityTypes: - type: object - title: EntityTypes - properties: - items: - type: array - items: - type: object - properties: - entityTypeName: - type: string - entities: - $ref: '#/components/schemas/Href' - required: ['entityTypeName', 'entities'] - required: ['items'] -Entities: - type: object - title: Entities - properties: - -``` - -``` - - items: - type: array - items: - type: object - description: Encapsulated object reference to the data model for schema definition of Topology -Entity - required: ['items'] -RelationshipTypes: - type: object - title: RelationshipTypes - properties: - items: - type: array - items: - type: object - properties: - relationshipTypeName: - type: string - relationships: - $ref: '#/components/schemas/Href' - required: ['relationshipTypeName', 'relationships'] - required: ['items'] -Relationships: - type: object - title: Relationships - properties: - items: - type: array - items: - type: object - description: Encapsulated object reference to the data model for schema definition of Topology -Relationships - required: ['items'] -ProblemDetails: - description: A problem detail to carry details in an HTTP response according to RFC 7807 - type: object - properties: - type: - description: a URI reference according to IETF RFC 3986 that identifies the problem type - type: string - title: - description: human-readable summary of the problem type - type: string - status: - description: the HTTP status code - type: number - detail: - description: human-readable explanation - type: string - instance: - description: URI reference that identifies the specific occurrence of the problem - type: string -Href: - type: object - title: Href - properties: - href: - type: string - format: uri-template -MultipartFile: - type: object - required: - - file - properties: - file: - type: string - description: multipartFile - format: binary -Schema: - type: object - title: Schema - -``` - -``` - -properties: - name: - type: string - domain: - type: string - revision: - type: string - content: - $ref: '#/components/schemas/Href' -Schemas: - type: object - title: Schemas - properties: - items: - type: array - items: - $ref: '#/components/schemas/Schema' -UserDefinedSchema: - type: object - title: UserDefinedSchema - properties: - name: - type: string - domain: - type: string - revision: - type: string - content: - $ref: '#/components/schemas/Href' -UserDefinedSchemas: - type: object - title: UserDefinedSchemas - properties: - items: - type: array - items: - $ref: '#/components/schemas/UserDefinedSchema' -responses: - '204': - description: No Content - content: {} - '400': - description: Bad Request - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '401': - description: Unauthorized - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '403': - description: Forbidden - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '404': - description: Not Found - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '406': - description: Not Acceptable - content: - application/problem+json: - schema: - -``` - -``` - - $ref: '#/components/schemas/ProblemDetails' -'409': - description: Conflict - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -'411': - description: Length Required - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -'413': - description: Payload Too Large - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -'414': - description: URI Too Large - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -'415': - description: Unsupported Media Type - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -'429': - description: Too Many Requests - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -'500': - description: Internal Server Error - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -'502': - description: Bad Gateway - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -'503': - description: Service Unavailable - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -parameters: - acceptPlainTextInHeader: - name: Accept - in: header - required: true - schema: - type: string - default: text/plain - contentTypeMultipartFileInHeader: - name: Content-Type - in: header - required: true - schema: - type: string - default: multipart/form-data - domainOptionalInQuery: - -``` - -``` -name: domain -in: query -required: false -schema: - type: string -schemaNameInPath: - name: schemaName - in: path - required: true - schema: - type: string -contentTypeJsonInHeader: - name: Content-Type - in: header - required: true - schema: - type: string - default: application/json -acceptJsonInHeader: - name: Accept - in: header - required: true - schema: - type: string - default: application/json -acceptYangJsonInHeader: - name: Accept - in: header - required: true - schema: - type: string - default: application/yang.data+json -offsetParam: - name: offset - in: query - description: This query parameter allows you to omit a specified number of entries before the -beginning of the result set for pagination. - required: false - schema: - type: integer - default: 0 - minimum: 0 -limitParam: - name: limit - in: query - description: The query parameter provides to limit the number of entries returned for a request for -pagination. - required: false - schema: - type: integer - default: 500 - minimum: 1 - maximum: 500 -domainNameInPath: - name: domainName - in: path - description: domain name - required: true - schema: - type: string -entityIdInPath: - name: entityId - in: path - required: true - schema: - type: string -relationshipIdInPath: - name: relationshipId - in: path - required: true - schema: -``` - -``` -type: string -entityTypeNameInPath: - name: entityTypeName - in: path - required: true - schema: - type: string -relationshipTypeNameInPath: - name: relationshipTypeName - in: path - required: true - schema: - type: string -targetFilterOptionalInQuery: - name: targetFilter - description: Use *targetFilter* to specify the entity type and - attributes to be returned in the REST response. The value for - *targetFilter* can also be a list of entity types and attributes. - in: query - required: false - schema: - type: string -scopeFilterOptionalInQuery: - name: scopeFilter - description: Use *scopeFilter* to specify the attributes to match on. - The value for *scopeFilter* can also be a list of entity types and - attributes. scopeFilter returns a boolean. - in: query - required: false - schema: - type: string -``` - -# Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2024.10.01 | 00.00.01 | Initial proposed skeleton for the TE&IV Application Protocols Specification | -| 2024.11.21 | 01.00 | Implemented the following CRs for the November 2024 train: ERI-2024.08.14-WG10-CR-0110-TE&IV_API_Content-v02, ERI-2024.09.23-WG10-CR-0115-TE&IV_API_Service operation and Resources-v02, ERI-2024.10.16-WG10-CR-0125-TE&IVOpenAPI-v01, ERI-2024.11.07-WG10-CR-0126-TE&IV_API_version_update-v01 | -| 2025.02.07 | 02.00 | Implemented the following CRs for the March 2025 train: ERI-2024.12.10-WG10-CR-0141-Adding Yang+Json to Content-v01, ERI-2025.02.17-WG10-CR-0149-stage 3 to add query parameter to topology entity relationship resource -v02, ERI-2025.02.17-WG10-CR-0151-OpenAPI update to add query parameter to topology entity relationship resource -v01 | -| 2025.07.01 | 03.00 | Implemented the following CRs for the July 2025 train: ERI-2025.05.20-WG10-CR-0175-Operations-for-Classifiers-and-Decorators-v06, ERI-2025.06.23-WG10-CR-0178-Schema-Operations-v01. Updated the specification for formatting corrections and editorial updates based on ODR and TS template v04 | -| 2025.11.19 | 04.00 | Implemented the following CRs for the November 2025 train: ERI-2025.07.21-WG10-CR-0191-Removing Unused Error Codes-v01, ERI-2025.11.06-WG10-CR-0212-Replacing O-RAN Alliance license with SCCL license in TE&IV OpenAPI-v01, Editorial fixes, Incremented the patch version of the TE&IV API to implement the CR 191 | \ No newline at end of file diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/0827b9260fe5458dbe416ebfc78c469e_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/08441fa90c5fd11994626f662ac13f19_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/08441fa90c5fd11994626f662ac13f19_img.jpg deleted file mode 100644 index f081e15fd8d23efb5b2aab850453c5dab1e634aa..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/08441fa90c5fd11994626f662ac13f19_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:63add4e0026efcdfe1c81e0a8f28d446a7d88b2d941a0be5d625ed4a87e15be9 -size 30576 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg deleted file mode 100644 index 06bbe7e103ffeaee3e44cac61c96fd99812e6ded..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3645b27f059ec31529b9bc996d89f43ec40f362d91dfb71327f1f1bfa0be27c8 -size 22209 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/14af8d47efd24c21fddf71b2415b6397_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/1baaba7a6e54e77197475726c871067d_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/21ad58fee90f2be50708ff541d225507_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/21ad58fee90f2be50708ff541d225507_img.jpg deleted file mode 100644 index 0a2eb3456d6b6a5471e02e4ce68f34748896b39c..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/21ad58fee90f2be50708ff541d225507_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a29d685d7c6b9d4985f0341bbd1aacc9864df30c1c02aad1e6be27ce6f089f3f -size 23915 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/22af211207188ebc64d7b60ca052b367_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/22f30783614672d201275c116a5d8516_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/253600420ae7bd7d0119563b895cbf8a_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/29f3760c0230631eb03f67030ef65ed0_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/2b3a967f6ce4f23649be995a353e39f8_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/2b3a967f6ce4f23649be995a353e39f8_img.jpg deleted file mode 100644 index 7780212e3cd506709cc221a5f240116ebe7542a1..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/2b3a967f6ce4f23649be995a353e39f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e57439615060717b85d76c56b0b8b7fb719c234df1c4c5757400ea0e5ba59d61 -size 21296 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/36fb8f844f936e7a1de4838da774f2f9_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/38866d3f212726e1c8e92001ca0dd6f8_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/3f727e6c0d6658bc53ea10905c4561dd_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/4a04896dfb569893fba50729314024f5_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/4f8349df2ca48959fefb7c42b2bc375e_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/59fcc0e3699f239444841881a2e75da0_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/5ae3023386ee15fae372871afce28865_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/6588b1c7f14069d96744b473ad663248_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/66c2bf11a8f117cddf67eff92d4c736c_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/66c2bf11a8f117cddf67eff92d4c736c_img.jpg deleted file mode 100644 index e1eec2ce7293f2443ba78113e7e98c9650ac4e6d..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/66c2bf11a8f117cddf67eff92d4c736c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6e83e067e6ff025ba21f64ee380c663a56fb7767f7db67baf1a0ca717e10b1c4 -size 17058 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/6a5342571eca4b46338fdfb3c42a8055_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg deleted file mode 100644 index 7b4b0eb7ad32e3f79b811917754fee35488e05fe..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:10f72e3184dd4c60394d4eec3526a7257e51228921194401b3b02bba4217cb55 -size 23897 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/6f659142d4789aa889184459f884787e_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/6f659142d4789aa889184459f884787e_img.jpg deleted file mode 100644 index 3f6fad5c9538e25d05aef052b81f981ffcb4d204..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/6f659142d4789aa889184459f884787e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3b8168423c09cfbee7520197b3f6021e425f533ab7190f5b58a8f94c89ce54d7 -size 23899 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/7e670a2b556b53ea9002dfff3a420e08_img.jpg deleted file mode 100644 index a6985890893643934dae9e55ffed8a17633536d4..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/7e670a2b556b53ea9002dfff3a420e08_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5d1c7c3637697dce88ca18ac02d55aedd58ab516cd2094be82dec5f4e46645db -size 26501 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/7f4320cee12fc1dbb865cc6b67462a91_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/81b34087cd6755a80f84a70cf28fba82_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/83ee9f10bd3636e192d68decf7f04cec_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/8447c5519e85d7a9e029fbf321da4c4f_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg deleted file mode 100644 index bac2e3ac1e4645388dcd9911623014c81ad9d06c..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1ef3800d5e071690bb012f077e6344ec4c9b919328464dd2ffc41730edf0a829 -size 21494 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/89100a6476d1d96f22c192db16502fec_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/8d129c93d18909f0643766f372e9ebf6_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/9156549264d36ead617a1dec7987f970_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/9a6ff2584005112f32fbd551cb6f0591_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg deleted file mode 100644 index c899b25f6d88a8a5a4a14518351a4e946de1f38a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/9ae17964ddd9b814c7d905b1af2fddf2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:da07a39e762bbd3134cacb044f3956c1aada038ad0c010e61bc55e8e50366be1 -size 21771 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/9b59a11096b85b2bc74c6f653a354e28_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/a26e142d3df5bef41a84a9dd099d7825_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/a26e142d3df5bef41a84a9dd099d7825_img.jpg deleted file mode 100644 index a2ade2c8735b8cb4b6f8fdcb8bd8a8ac8f2bdd79..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/a26e142d3df5bef41a84a9dd099d7825_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:91c950a4a8315e6d2256ab5aa1e41e35ea15bf4b8042ca5b1167f950d67e3e03 -size 29828 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/a28ab03366399b5e0a61445bc57e3724_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/a76a30cf23764f0b907220e7c3c70ce1_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/a82aef1d2f3f1a527328950e9db947ee_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/b0211cee4b20034939d883ac0d70f696_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/b0211cee4b20034939d883ac0d70f696_img.jpg deleted file mode 100644 index e1aa2dfc23adc1457472ba35ff5bfcaf70d31b07..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/b0211cee4b20034939d883ac0d70f696_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3533c4dba0fc74c298f470def02704f7f1618cb9e6ccec465f2ccdfc3b887a03 -size 22891 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/be8d4d130f4e1f103926de61c4bfc23c_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/c4315e81a5a818379fcf31519a9c2cbe_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg deleted file mode 100644 index 1e1ebe991166ce4f637f195139792f75137510d3..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/ca7c7526ec57cd5a2f278c194c0a6a00_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:39d15697a41c5c57a6d7481514103ecb12a882a292e4086d3f5324dc94d10c8b -size 31597 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/cb5f64aa26cee1c05257b7c6bbba7408_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/d0abac95583b52a3b35f74a215567334_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/d0abac95583b52a3b35f74a215567334_img.jpg deleted file mode 100644 index 7b1328172e0a44a4f92d92d8ac8663e0ba2c72a7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/d0abac95583b52a3b35f74a215567334_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fcbae764822359a9f80540fd8608191b181e9401631676cdffddff0a46958cf6 -size 42782 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/d879e5f2c388bb87ee9614f63364dcf0_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/d90d939bcbf43d474efaeeaa335a635c_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/d90f17b29a73eddf151f51effa8912e0_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/da8cb3d696f15f2c6de7aff6955d12d3_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e511e373339b5f948f239b19e0c37dd4_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e6df2733626a85205c1db682e6259c46_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e6df2733626a85205c1db682e6259c46_img.jpg deleted file mode 100644 index 14b3bfaa9fbaf93ab5533d900a704fbea6c94770..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e6df2733626a85205c1db682e6259c46_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c1dc5f40bb4dc7cfe42af11341ce57d51be6827e81dbb748c8ce67b1213140ee -size 17191 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e882a6bdfd0e868314f3a26f536145a3_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e9d825d87c5f85c8dba0664eace96ef4_img.jpg deleted file mode 100644 index b13d8abf801b33a909eac918444a30692235503a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/e9d825d87c5f85c8dba0664eace96ef4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6e47527c758ff471f96e7e5ec44bc2496f99884ef92042a3bb52510b55cbe292 -size 31970 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg deleted file mode 100644 index 23f19b5128fcb9ce724eeffd4c616b92a702c8e1..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0db38de1879125d1686ac1f50bb47290a1d2400ffeac2ba438d9ec7bf9182ae8 -size 25106 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/f250ba4162fe40d8ddfd05b74fa48895_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/f7dbd497160f02888f34fdf243648aa2_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/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index bb11a76f655fdf424066da755ce3bb9da561c72d..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-API.0-R005-v04.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9181d1f22157938c8d6cae2e34c9e79ee14ca739bad919f900cbe2ffcacc1868 -size 4542 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/doc.md b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/doc.md deleted file mode 100644 index f8d78541933e8cd136e9c0973043bade132e06a7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/doc.md +++ /dev/null @@ -1,3144 +0,0 @@ - - -![O-RAN ALLIANCE logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) - -The logo for the O-RAN ALLIANCE, featuring a colorful circular icon to the left of the text "O-RAN" in blue, with "ALLIANCE" in smaller blue letters underneath. - -O-RAN ALLIANCE logo - -# --- **O-RAN Work Group 10 (OAM for O-RAN)** - -## **Topology Exposure & Inventory Common Information Models and Interface Specification - Stage 2** - -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 | -| Executive summary ..... | 3 | -| Introduction ..... | 3 | -| 1 Scope ..... | 4 | -| 2 References ..... | 4 | -| 2.1 Normative references ..... | 4 | -| 2.2 Informative references..... | 5 | -| 3 Definition of terms, symbols and abbreviations..... | 5 | -| 3.1 Terms..... | 5 | -| 3.2 Symbols..... | 5 | -| 3.3 Abbreviations ..... | 5 | -| 4 TE&IV Information Models..... | 6 | -| 4.1 Introduction ..... | 6 | -| 4.2 TE&IV Information Modeling Guidelines ..... | 6 | -| 4.2.1 Modeling approach, Unified Modeling Language (UML)..... | 6 | -| 4.2.2 Modeling guidelines ..... | 12 | -| 4.3 TE&IV Information Model Definitions ..... | 12 | -| 4.3.1 Namespace ORAN.SMO.TEIV.RAN..... | 12 | -| 4.3.2 Namespace ORAN.SMO.TEIV.Cloud ..... | 18 | -| 4.3.3 Namespace ORAN.SMO.TEIV.REL-Cloud-RAN..... | 23 | -| 4.3.4 Namespace ORAN.SMO.TEIV ..... | 33 | -| 4.3.5 Namespace ORAN.SMO.TEIV.Physical..... | 35 | -| 4.3.6 Namespace ORAN.SMO.TEIV.REL-Physical-RAN ..... | 41 | -| 4.4 TE&IV Service Operations ..... | 51 | -| 4.4.1 Introduction..... | 51 | -| 4.4.2 Operations and Notification..... | 52 | -| 4.5 TE&IV User Defined Data..... | 58 | -| 4.5.1 Introduction..... | 58 | -| 4.5.2 Classifiers ..... | 58 | -| 4.5.3 Decorators..... | 59 | -| 4.5.4 Attribute properties ..... | 60 | -| 4.5.5 Service Operations for User Defined Data ..... | 60 | -| Annex A (Informative): Model views ..... | 64 | -| A.1 Model View: O-RAN TE&IV Network Function Deployment View (informative)..... | 64 | -| Annex (informative): Change history..... | 67 | - -# --- Foreword - -This Technical Specification (TS) has been produced by WG10 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. - -# --- Executive summary - -The present document specifies the TE&IV Information Models suited to realize the use cases of TE&IV Service Consumer as specified in [1]. - -# --- Introduction - -The O-RAN TE&IV Information Models provide the logical representation of O-RAN specific TE&IV resources. This includes: - -- Topology Entities intended to convey classes that realizes TE&IV resources. -- Topology Relationships intended to realize relationship between Topology Entities. -- Enumerations which provide a predefined list of choices. -- Data Types which provide structure to the elements of TE&IV resources. -- Notifications which is the information conveyed in a message from TE&IV Service Producer to TE&IV Service Consumer. - -# 1 Scope - -This document specifies the Information Model used to support TE&IV services within the SMO. The TE&IV Information Models described in this document are structured using the concept of Namespaces. In addition, relevant sections in this document include information imported from existing standards and industry work that serve as a basis for O-RAN TE&IV. - -The Annex section of this document describes multiple views of the TE&IV Information Models that supports TE&IV Service Consumer use cases [1] within the SMO. - -The TE&IV Information Models specified in this present document is part of a “modeling continuum” that aims to establish and evolve an O-RAN TE&IV Information Model from which O-RAN TE&IV Data Models may be generated manually or with a set of tools. However, the O-RAN TE&IV Data Models is out of scope of this present document and will be specified in a different specification. - -# 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. - -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.WG10.TE&IV-UCR.0: "Topology Exposure and Inventory Management Services Use Cases and Requirement Specification" -- [2] 3GPP TS 32.156: Telecommunication management; Fixed Mobile Convergence (FMC) Model repertoire -- [3] OMG formal/2017-12-05: OMG® Unified Modeling Language® (OMG UML®), version 2.5.1 -- [4] 3GPP TS 32.160: Management and orchestration; Management service template -- [5] 3GPP TS 28.541: Management and orchestration; 5G Network Resource Model (NRM) -- [6] O-RAN.WG1.TS.OAD: " O-RAN Architecture Description" ("OAD") -- [7] O-RAN.WG6.TS.O2-GA&P: "O-RAN O2 Interface General Aspects and Principles" -- [8] O-RAN.WG6.O2DMS-INTERFACE-ETSI-NFV-PROFILE: "O2dms Interface Specification: Profile based on ETSI NFV Protocol and Data Models" -- [9] O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE: "O2dms Interface Specification: Kubernetes Native API Profile for Containerized NFs" -- [10] O-RAN.WG6.ORCH-USE-CASES: "Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN" -- [11] O-RAN.WG10.TS.OAM-Architecture: "O-RAN Operations and Maintenance Architecture" -- [12] O-RAN.WG3.TS.E2AP: "E2 Application Protocol" ("E2AP") -- [13] 3GPP TS 28.658: Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) - -- [14] IETF RFC 8141: "Uniform Resource Names (URNs)" -- [15] O-RAN.WG4.TS.MP.0: "O-RAN Management Plane Specification" -- [16] 3GPP TS 28.622: Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) -- [17] O-RAN.WG10.TS.TE&IV-API.0: "Topology Exposure & Inventory Application Protocols Specification - Stage 3" ("TE&IV API") -- [18] O-RAN.WG6.TS.O-Cloud-IM.0: "O-Cloud Information Model" ("O-Cloud IM") - -## 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: - -**Information Model:** a representation of concepts and the relationships, constraints, rules, and operations to specify data semantics for a chosen domain of discourse, it specifies relations between objects, can provide sharable, stable, and organized structure of information requirements or knowledge for the domain context. - -**Namespace:** a logical grouping of named elements specified, to prevent name collisions across named elements imported and associated from other specifications to support the independent lifecycle of its representation in the TE&IV Information Model. - -**Topology Entity:** is a modelling construct that represents TE&IV resources useful to a Topology and Inventory use case [1]. - -**Topology Relationship:** is a modelling construct that represents the relationship between Topology Entities useful to a Topology and Inventory use case [1]. - -**Domain:** a logical grouping of Topology Entities and/or Topology Relationships. - -## 3.2 Symbols - -Void - -## 3.3 Abbreviations - -For the purposes of the present document, the following abbreviations apply: - -| | | -|-----|-----------------------| -| TEC | Topology Entity Class | -|-----|-----------------------| - -# 4 TE&IV Information Models - -## 4.1 Introduction - -The TE&IV Information Models described in this specification exposes the Topology Entities and Topology Relationships of the TE&IV resources as defined in [1]. - -## 4.2 TE&IV Information Modeling Guidelines - -### 4.2.1 Modeling approach, Unified Modeling Language (UML) - -The TE&IV Information Models shall use the Unified Modeling Language™ (UML®) version 2.5.1 [3] from the Object Management Group (OMG). - -UML provides a rich set of concepts, graphical notations, and model elements to model distributive systems. 3GPP TS 32.156 [2] provides the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism <> to model network management systems and their managed nodes. These conventions are applied to the TE&IV Information Model. - -The TE&IV Information Model also defines UML notation, model elements and <> which shall be used to model behaviours of the Topology Entity and Topology Relationship. - -The TE&IV Information Model uses embedded PlantUML for diagraming and the relationships are modeled using UML Class diagram conventions. - -O-RAN TE&IV Information Models shall also follow methodology documented in 3GPP TS 32.160 [4] Clause 5.2. - -#### 4.2.1.1 Model elements and notation - -##### 4.2.1.1.1 General - -The UML graphical notation in this document is only used to represent the Topology Entity and Topology Relationship model elements. - -UML properties as defined in [3] clause 9.5 are referred in this document and shall be used only for TE&IV Information Model. - -##### 4.2.1.1.2 Basic model elements - -UML [3] has defined a number of basic model elements. This subclause lists the subset selected for use in TE&IV Information Model. - -The characteristics defined in UML [3] clause 11.4 is applicable to TE&IV Information Model. However, in this specification, classes may or may not have attributes and the graphical notation of a class may show a suppressed attribute (middle) compartment even if the class has attributes, as shown in figure below. The operation (bottom) compartment is also suppressed. - -![UML class diagram showing a stereotype box with '«stereotype»' and 'ClassName' text.](a738993919a50143787084ee7ce6e2f2_img.jpg) - -UML class diagram showing a stereotype box with '«stereotype»' and 'ClassName' text. - -Figure 4.2.1.1.2-1: Basic model elements - -##### 4.2.1.1.3 Attribute - -###### 4.2.1.1.3.1 Description - -In UML [3], an attribute is a typed element of a class that is represented by a property. The properties listed in this section represents the attributes of a Topology Entity and Topology Relationship class. - -Table 4.2.1.1.3.1-1 below lists the adaptations of the attribute properties and its values applicable for TE&IV Information Model when re-using the attribute properties specified in 3GPP TS 32.156 [2] clause 5.2.1. - -Table 4.2.1.1.3.1-1: TE&IV Information Model valid attribute values - -| Property name | TE&IV Adaptations | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| -| type | This property and its description, legal values shall be supported | -| allowedValues | This property and its description, legal values shall be supported | -| defaultValue | This property and its description, legal values shall be supported | -| multiplicity | This property and its description, legal values shall be supported | -| isOrdered | This property and its description, legal values shall be supported | -| isUnique | This property and its description, legal values shall be supported | -| isNullable | Not required to be supported | -| passedById | This property and its description, legal values shall be supported | -| lifecycleStatus | Not required to be supported | -| isInvariant | This property and its description, legal values shall be supported | -| isWritable | This property and its description, legal values shall be supported. However, A "isWritable: True" property might be restricted by access control. | -| isReadable | This property and its description, legal values shall be supported | -| isNotifyable | This property and its description, legal values shall be supported | -| supportQualifier | This property and its description, legal values shall be supported | - -###### 4.2.1.1.3.2 Example - -This example shows three attributes, i.e., x, y, and z, listed in the attribute (the second) compartment of the class. However, as mentioned in 4.2.1.1.2, the attribute compartment (middle) can be suppressed. - -![UML class diagram showing a stereotype box with '«stereotype»' and 'ClassName' in the top compartment, and attributes 'x', 'y', and 'z' in the bottom compartment.](990567efebf979be51f56d1150012c9d_img.jpg) - -UML class diagram showing a stereotype box with '«stereotype»' and 'ClassName' in the top compartment, and attributes 'x', 'y', and 'z' in the bottom compartment. - -**Figure 4.2.1.1.3.2-1: Attribute notation** - -###### **4.2.1.1.3.3 Name style** - -As defined in clause 5.2.1.3 of 3GPP TS 32.156 [2]. - -##### **4.2.1.1.4 Association Relationship** - -###### **4.2.1.1.4.1 Description** - -An association relationship class is a modelling construct that represents potentially complex series of associations that may cross domain boundaries. These classes are identifiable, searchable, have attributes and a record of the entities (and potentially configuration/associations) that make up their source. - -Association relationship classes are appropriate for use to show a relationship between different Topology Entities [see clause 4.2.1.1.2] through the Topology Relationship class [see clause 4.2.1.1.3]. Each association relationship class has aSide and bSide relationships, multiplicity, and navigability as shown in the example clause 4.2.1.1.4.2. - -For a Topology Relationship, the following rules apply: - -1. The Topology Relationship class name shall have the form “\_{REL}\_”, where represents the TEC at the aSide of the relationship, represents the TEC at the bSide of the relationship, and {REL} is a transient verb representing the relationship between and . e.g., NFDeployment\_serves\_ODUFunction. -2. The aSide is considered the originating side of the relationship. The bSide is considered the terminating side of the relationship. The order of aSide and bSide is of importance and shall not be changed once defined. -3. The Topology Relationship is a bi-directional relationship which indicates the navigability from either the aSide or bSide of the associated Topology Entity. - -###### **4.2.1.1.4.2 Example** - -For TE&IV Information model, the example (Figure 4.2.1.1.4.2-1) shows a bi-directional association. In this example, both Topology Entity classes (AbcFunction and XyzFunction) are related through a separate relationship class named Abc\_REL\_Xyz. By default, the aSide of the relationship is considered originating when relating its associated Topology Entity classes. - -![UML Class diagram showing an association relationship between two TopologyEntityClass classes (AbcFunction and XyzFunction) mediated by a TopologyRelationshipClass (Abc_REL_Xyz). The association is labeled 'REL' and has multiplicities of 1..n at both ends. The association names are '+aSide Association Name' and '+bSide Association Name'.](562f471e8153729557e6a4ee6343c32c_img.jpg) - -``` - -classDiagram - class AbcFunction["«TopologyEntityClass» -AbcFunction"] - class XyzFunction["«TopologyEntityClass» -XyzFunction"] - class Abc_REL_Xyz["«TopologyRelationshipClass» -Abc_REL_Xyz"] - - AbcFunction "1..n" -- "1..n" XyzFunction : REL - Abc_REL_Xyz .. AbcFunction - Abc_REL_Xyz .. XyzFunction - note for AbcFunction "+aSide Association Name" - note for XyzFunction "+bSide Association Name" - -``` - -UML Class diagram showing an association relationship between two TopologyEntityClass classes (AbcFunction and XyzFunction) mediated by a TopologyRelationshipClass (Abc\_REL\_Xyz). The association is labeled 'REL' and has multiplicities of 1..n at both ends. The association names are '+aSide Association Name' and '+bSide Association Name'. - -**Figure 4.2.1.1.4.2-1: Association Relationship notation** - -However, the figure 4.2.1.1.4.2-1 can also be represented in a simpler form with only the relationship class name without mentioning association names, as shown in the below figure 4.2.1.1.4.2-2. - -![UML Class diagram showing a simplified association relationship between two TopologyEntityClass classes (AbcFunction and XyzFunction) with a single association line labeled Abc_REL_Xyz.](367926125450c2bc3f4bdca9d59a62ba_img.jpg) - -``` - -classDiagram - class AbcFunction["«TopologyEntityClass» -AbcFunction"] - class XyzFunction["«TopologyEntityClass» -XyzFunction"] - - AbcFunction <--> XyzFunction : Abc_REL_Xyz - -``` - -UML Class diagram showing a simplified association relationship between two TopologyEntityClass classes (AbcFunction and XyzFunction) with a single association line labeled Abc\_REL\_Xyz. - -**Figure 4.2.1.1.4.2-2: Simple Association Relationship notation** - -###### 4.2.1.1.4.3 Name style - -The name shall use the same style as used in << TopologyRelationshipClass >> clause 4.2.1.2.3.3. - -##### 4.2.1.1.5 Abstract class - -###### 4.2.1.1.5.1 Description - -An abstract class is a generalized representation of Topology Entity and Topology Relationship classes. An abstract class cannot be instantiated. - -This modelled element has the same properties as class. See 4.2.1.1.2. - -###### 4.2.1.1.5.2 Example - -This example (Figure 4.2.1.1.5-1) shows that *AbcFunction\_* of stereotype TopologyEntityClass is an abstract class. It is a generalization of both AbcFunction1 and AbcFunction2. - -![UML Class Diagram showing AbcFunction_ as an abstract class with two subclasses: AbcFunction1 and AbcFunction2. All classes have the stereotype <>.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) - -``` - -classDiagram - class AbcFunction_ { - <> - AbcFunction_ - } - class AbcFunction1 { - <> - AbcFunction1 - } - class AbcFunction2 { - <> - AbcFunction2 - } - AbcFunction1 --|> AbcFunction_ - AbcFunction2 --|> AbcFunction_ - -``` - -UML Class Diagram showing AbcFunction\_ as an abstract class with two subclasses: AbcFunction1 and AbcFunction2. All classes have the stereotype <>. - -**Figure 4.2.1.1.5-1: Abstract class notation for Topology Entity** - -This example (Figure 4.2.1.1.5-2) shows that *XyzFunction\_* of stereotype TopologyRelationshipClass is an abstract class. It is a generalization of both *XyzFunction1* and *XyzFunction2*. - -![UML Class Diagram showing XyzFunction_ as an abstract class with two subclasses: XyzFunction1 and XyzFunction2. All classes have the stereotype <>.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) - -``` - -classDiagram - class XyzFunction_ { - <> - XyzFunction_ - } - class XyzFunction1 { - <> - XyzFunction1 - } - class XyzFunction2 { - <> - XyzFunction2 - } - XyzFunction1 --|> XyzFunction_ - XyzFunction2 --|> XyzFunction_ - -``` - -UML Class Diagram showing XyzFunction\_ as an abstract class with two subclasses: XyzFunction1 and XyzFunction2. All classes have the stereotype <>. - -**Figure 4.2.1.1.5-2: Abstract class notation for Topology Relationship** - -###### 4.2.1.1.5.3 Name style - -The name shall use the same style as used in *TopologyEntityClass* and *TopologyRelationshipClass* as specified in clauses 4.2.1.2.2.3 and 4.2.1.2.3.3. The name shall be in italics and its last character shall be an underscore. - -#### 4.2.1.2 Stereotype - -##### 4.2.1.2.1 Description - -Subclause 4.2.1 listed the UML defined basic model elements. UML defined a stereotype concept allowing the specification of simple or complex user-defined model elements. - -This subclause lists all allowable stereotypes for TE&IV Information Model. - -The names of stereotypes shall be chosen such that they do not clash with any stereotype defined in O-RAN. - -The characteristics defined in subclause 5.3.0 of 3GPP TS 32.156 [2] is applicable to TE&IV Information Model elements i.e., as per the clause 5.3.0 of 3GPP TS 32.156 [2] “For each stereotype model element listed, there are three parts. The first part contains its description. The second part contains its graphical notation examples, and the third part contains the rule, if any, recommended for labelling or naming it”. - -##### 4.2.1.2.2 <> - -###### 4.2.1.2.2.1 Description - -The << *TopologyEntityClass* >> is identical to UML *class* [3] clause 11.4.3.1 which specifies a Topology Entity resource including properties, attributes and allows inheritance but it does not include/define methods or operations. - -###### 4.2.1.2.2.2 Example - -This example (figure 4.2.1.2.2.2-1) shows a class `AbcFunction` `<>`. - -![UML class diagram for Figure 4.2.1.2.2.2-1: A class box with a yellow background and a red border. It contains the stereotype <> and the class name AbcFunction.](d26959f4514c26ca19c3d6f00da85956_img.jpg) - -UML class diagram for Figure 4.2.1.2.2.2-1: A class box with a yellow background and a red border. It contains the stereotype <> and the class name AbcFunction. - -**Figure 4.2.1.2.2.2-1: `<>` notation** - -This example (figure 4.2.1.2.2.2-2) shows an abstract class `AbcFunction_` `<>`. - -![UML class diagram for Figure 4.2.1.2.2.2-2: A class box with a yellow background and a red border. It contains the stereotype <> and the abstract class name AbcFunction_.](8e14350b4b669119a3bdfca7869110ca_img.jpg) - -UML class diagram for Figure 4.2.1.2.2.2-2: A class box with a yellow background and a red border. It contains the stereotype <> and the abstract class name AbcFunction\_. - -**Figure 4.2.1.2.2.2-2: Abstract class `<>` notation** - -###### 4.2.1.2.2.3 Name style - -For `<>` name, use the same style as defined in clause 5.3.2.3 of 3GPP TS 32.156 [2]. - -##### 4.2.1.2.3 `<>` - -###### 4.2.1.2.3.1 Description - -The `<>` is identical to UML *class* [3] clause 11.4.3.1 which specifies a Topology Relationship between different Topology Entities including properties, attributes and allows multiple inheritance but it does not include/define methods or operations. - -###### 4.2.1.2.3.2 Example - -This example shows a class `AbcXyzRelation` `<>`. - -![UML class diagram for Figure 4.2.1.2.3.2-1: A class box with a yellow background and a red border. It contains the stereotype <> and the class name AbcXyzRelation.](e58a867750e4ae01604318506b79df7a_img.jpg) - -UML class diagram for Figure 4.2.1.2.3.2-1: A class box with a yellow background and a red border. It contains the stereotype <> and the class name AbcXyzRelation. - -**Figure 4.2.1.2.3.2-1: `<>` notation** - -This example shows an abstract class `AbcXyzRelation_` `<>`. - -![UML class diagram for Figure 4.2.1.2.3.2-2: A class box with a yellow background and a red border. It contains the stereotype <> and the abstract class name AbcXyzRelation_.](d0c9888da9078a08d93712fd0e113a88_img.jpg) - -UML class diagram for Figure 4.2.1.2.3.2-2: A class box with a yellow background and a red border. It contains the stereotype <> and the abstract class name AbcXyzRelation\_. - -**Figure 4.2.1.2.3.2-2: Abstract class `<>` notation** - -###### 4.2.1.2.3.3 Name style - -For `<>` name, use the same style as defined in clause 5.3.2.3 of 3GPP TS 32.156 [2]. - -### 4.2.2 Modeling guidelines - -The TE&IV Information Models references concepts from each of the other O-RAN Information Model Namespaces by adding and removing attributes, entities, and relationships to serve the needs of the SMO use cases and services. TE&IV Information Models use multiple separate Namespaces to support independent lifecycle of loosely coupled topology and inventory concepts. - -The definitions and mapping involved with the TE&IV resources created within O-RAN TE&IV shall follow the below mentioned guidelines: - -- shall be defined in a TE&IV namespace -- shall follow the 3GPP style when defining its identity and attributes [5] -- shall maintain a standard mapping to existing O-RAN definitions within O-RAN namespaces -- if it is a 1:1 mapping with other namespace resource, not limited to O-RAN, - - the resource name shall be reused exactly - - the identities used in the TE&IV resources shall encapsulate the type of the instance identifier and the instance identifier of the resource defined in other source namespaces -- if it is a 1:N mapping with other namespace resource, not limited to O-RAN, - - the resource name shall begin with O-RAN prefix “ORT-” - - the identities used in the TE&IV resources shall be generated within TE&IV and represented using a TE&IV specified type of the instance identifier and the generated instance identifier of the resource - - the generated identities to map the TE&IV instance identifier to the source shall be preserved along with the identity of the source. - -## 4.3 TE&IV Information Model Definitions - -### 4.3.1 Namespace ORAN.SMO.TEIV.RAN - -#### 4.3.1.1 Namespace overview - -This namespace contains the Topology Entities and Topology Relationship in the RAN Logical domain, which represents the functional capability of the deployed RAN that are relevant to realise use cases of TE&IV Service Consumer as specified in [1]. - -#### 4.3.1.2 Imported associated information - -##### 4.3.1.2.1 Imported information entities and local labels - -Imported information entities and local labels is not defined in the present version of the document. - -##### 4.3.1.2.2 Associated information entities and local labels - -| Label reference | Local label | -|-------------------------------------|-----------------| -| TS 28.541 [5], IOC, GNBDFFunction | GNBDFFunction | -| TS 28.541 [5], IOC, GNBCUCPFunction | GNBCUCPFunction | -| TS 28.541 [5], IOC, GNBCUUPFunction | GNBCUUPFunction | - -#### 4.3.1.3 Class diagram - -##### 4.3.1.3.1 Relationships - -Relationships are not defined in the present version of the document. - -##### 4.3.1.3.2 Inheritance - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV { - - abstract class TopologyEntity_ -} - -namespace ORAN.SMO.TEIV.RAN { - - abstract class ORANNetworkFunction_ - class ORUFunction - class ODFunction - class OCUCPFunction - class OCUUPFunction - class NearRTRICFunction - - TopologyEntity_ <|-- ORANNetworkFunction_ - - ORANNetworkFunction_ <|-- ORUFunction - ORANNetworkFunction_ <|-- ODFunction - ORANNetworkFunction_ <|-- OCUCPFunction - ORANNetworkFunction_ <|-- OCUUPFunction - ORANNetworkFunction_ <|-- NearRTRICFunction -} - -@enduml - -``` - -![UML Class diagram showing inheritance. TopologyEntity_ is the base class. ORANNetworkFunction_ inherits from TopologyEntity_. ORUFunction, ODFunction, OCUCPFunction, OCUUPFunction, and NearRTRICFunction all inherit from ORANNetworkFunction_.](4636adff5682a064f0ae5f13a1d464a6_img.jpg) - -``` - -classDiagram - class TopologyEntity_ - class ORANNetworkFunction_ - class ORUFunction - class ODFunction - class OCUCPFunction - class OCUUPFunction - class NearRTRICFunction - - TopologyEntity_ <|-- ORANNetworkFunction_ - ORANNetworkFunction_ <|-- ORUFunction - ORANNetworkFunction_ <|-- ODFunction - ORANNetworkFunction_ <|-- OCUCPFunction - ORANNetworkFunction_ <|-- OCUUPFunction - ORANNetworkFunction_ <|-- NearRTRICFunction - -``` - -UML Class diagram showing inheritance. TopologyEntity\_ is the base class. ORANNetworkFunction\_ inherits from TopologyEntity\_. ORUFunction, ODFunction, OCUCPFunction, OCUUPFunction, and NearRTRICFunction all inherit from ORANNetworkFunction\_. - -Figure 4.3.1.3.2-1: ORAN SMO TE&IV RAN inheritance view - -#### 4.3.1.4 Class definitions - -##### 4.3.1.4.1 ORUFunction - -###### 4.3.1.4.1.1 Definitions - -This class provides the TE&IV resource representation of O-RU O-RAN Network Function using the equivalent concept as defined in clause 5 of O-RAN.WG1.OAD [6]. - -###### 4.3.1.4.1.2 Attributes - -The ORUFunction TEC includes the attributes inherited from *ORANNetworkFunction\_* and have the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|----------------|---|------------|------------|-------------|--------------| -| oruId | M | T | F | F | T | - -###### 4.3.1.4.1.3 Attribute constraints - -None. - -###### 4.3.1.4.1.4 Notifications - -There is no notification defined. - -###### 4.3.1.4.1.5 State diagram - -None. - -##### 4.3.1.4.2 NearRTRICFunction - -###### 4.3.1.4.2.1 Definitions - -This class provides the TE&IV resource representation of Near-RT RIC O-RAN Network Function using the equivalent concept as defined in clause 5 of O-RAN.WG1.OAD [6]. - -###### 4.3.1.4.2.2 Attributes - -The NearRTRICFunction TEC includes the topology attributes inherited from *ORANNetworkFunction\_* and have the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|----------------|---|------------|------------|-------------|--------------| -| pLMNId | M | T | F | F | T | -| nearRtRicId | M | T | F | F | T | - -###### 4.3.1.4.2.3 Attribute constraints - -None. - -###### 4.3.1.4.2.4 Notifications - -There is no notification defined. - -###### 4.3.1.4.2.5 State diagram - -None. - -##### 4.3.1.4.3 OCUCPFunction - -###### 4.3.1.4.3.1 Definitions - -This class provides the TE&IV resource representation of O-CU-CP Network Function using the equivalent concept as defined in clause 5 of O-RAN TS OAD [6]. - -NOTE: The management characteristics of the O-CU-CP O-RAN NF is represented by the IOC GNBCUCPFunction as specified in 3GPP NR NRM model, as per 3GPP TS 28.541 [5]. - -###### 4.3.1.4.3.2 Attributes - -The OCUCPFunction TEC includes the attributes inherited from *ORANNetworkFunction\_* and have the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|----------------|---|------------|------------|-------------|--------------| -| gNBCUName | O | T | F | F | T | -| gNBId | M | T | F | F | T | -| gNBIdLength | M | T | F | F | T | -| pLMNId | M | T | F | F | T | - -###### 4.3.1.4.3.3 Attribute constraints - -None. - -###### 4.3.1.4.3.4 Notifications - -There is no notification defined. - -###### 4.3.1.4.3.5 State diagram - -None. - -##### 4.3.1.4.4 OCUUPFunction - -###### 4.3.1.4.4.1 Definitions - -This class provides the TE&IV resource representation of O-CU-UP Network Function using the equivalent concept as defined in clause 5 of O-RAN.WG1.OAD [6]. - -NOTE: The management characteristics of the O-CU-UP O-RAN NF is represented by the IOC GNBCUUPFunction as specified in 3GPP NR NRM model, as per 3GPP TS 28.541 [5]. - -###### 4.3.1.4.4.2 Attributes - -The OCUUPFunction TEC includes the attributes inherited from *ORANNetworkFunction\_* and have the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|----------------|---|------------|------------|-------------|--------------| -| gNBId | M | T | F | F | T | -| gNBIdLength | M | T | F | F | T | -| pLMNIdList | M | T | F | F | T | - -###### 4.3.1.4.4.3 Attribute constraints - -None. - -###### 4.3.1.4.4.4 Notifications - -There is no notification defined. - -###### 4.3.1.4.4.5 State diagram - -None. - -##### 4.3.1.4.5 ODFunction - -###### 4.3.1.4.5.1 Definitions - -This class provides the TE&IV resource representation of O-DU Network Function using the equivalent concept as defined in clause 5 of O-RAN.WG1.OAD [6]. - -NOTE: The management characteristics of the O-DU O-RAN NF is represented by the IOC GNBDFFunction as specified in 3GPP NR NRM model, as per 3GPP TS 28.541 [5]. - -###### 4.3.1.4.5.2 Attributes - -The ODFunction TEC includes the attributes inherited from *ORANNetworkFunction\_* and have the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|----------------|---|------------|------------|-------------|--------------| -| gNBDFId | M | T | F | F | T | -| gNBId | M | T | F | F | T | -| gNBIdLength | M | T | F | F | T | - -###### 4.3.1.4.5.3 Attribute constraints - -None. - -###### 4.3.1.4.5.4 Notifications - -There is no notification defined. - -###### 4.3.1.4.5.5 State diagram - -None. - -##### 4.3.1.4.6 *ORANNetworkFunction\_* - -###### 4.3.1.4.6.1 Definitions - -This abstract class is provided for sub-classing only and is used to generalize the entity classes in this namespace. - -###### 4.3.1.4.6.2 Attributes - -The *ORANNetworkFunction\_* includes the attributes inherited from *TopologyEntity\_* in the ORAN.SMO.TEIV namespace. - -###### 4.3.1.4.6.3 Attribute constraints - -None. - -###### 4.3.1.4.6.4 Notifications - -There is no notification defined. - -###### 4.3.1.4.6.5 State diagram - -None. - -#### 4.3.1.5 Attribute definitions - -##### 4.3.1.5.1 Attribute properties - -The following table defines the properties of attributes specified in the present document. - -**Table 4.3.1.5.1-1: Attribute properties** - -| Attribute Name | Documentation and Allowed Values | Properties | Source Domain | -|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------| -| gNBCUName | Name of gNB-CU, see subclause 4.4.1 of 3GPP TS 28.541 [5].

allowedValues: Not applicable | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | O1 | -| gNBDUId | Unique identifier for the gNB-DU at least within a gNB-CU, see subclause 4.4.1 of 3GPP TS 28.541 [5].

allowedValues: Not applicable | type: Integer
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | O1 | -| gNBId | Identity of gNB within a PLMN, see subclause 4.4.1 of 3GPP TS 28.541 [5].

allowedValues: 0..4294967295 | type: Integer
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | O1 | -| gNBIdLength | Length of gNBId bit string representation, see subclause 4.4.1 of 3GPP TS 28.541 [5].

allowedValues: 22 .. 32 | type: Integer
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | O1 | -| nearRTRICID | The identifier of Near-RT RIC as defined in O-RAN.WG3.E2AP [12], clause 9.2.4 | type: Integer
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | O1 | -| pLMNId | Identity of the PLMN, see subclause 4.4.1 of 3GPP TS 28.541 [5]. | type: PLMNId
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | O1 | -| oruld | Identity of the O-RU as discovered from the source domain based on M-Plane architecture model as defined in O-RAN TS [15]

Note: The oruld is assumed to be available in TE&IV. | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | O1 (Hierarchical)
O1, Open FH M-Plane (Hybrid) | -| pLMNIdList | List of unique identities for PLMN, see subclause 4.4.1 of 3GPP TS 28.658 [13]. | type: PLMNId
multiplicity: 1..12
isOrdered: False
isUnique: True
isWritable: False
defaultValue: None | O1 | - -### 4.3.2 Namespace ORAN.SMO.TEIV.Cloud - -#### 4.3.2.1 Namespace overview - -This namespace contains the Topology Entities and Topology Relationship in the O-CLOUD domain, which comprises cloud infrastructure and cloud deployment aspects. - -#### 4.3.2.2 Imported associated information - -##### 4.3.2.2.1 Imported information entities and local labels - -Imported information entities and local labels is not defined in the present version of the document. - -##### 4.3.2.2.2 Associated information entities and local labels - -Associated information entities and local labels is not defined in the present version of the document. - -#### 4.3.2.3 Class diagram - -##### 4.3.2.3.1 Relationships - -``` -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none -namespace ORAN.SMO.TEIV.Cloud { - -class CloudifiedNF -class NFDeployment -class OCloudNamespace -class NodeCluster -class OCloudSite - -note as locationnote - Has location info. -end note - -locationnote .. OCloudSite - -CloudifiedNF "1" --> "1..*" NFDeployment: comprizes -NFDeployment "1..*" --> "1..*" OCloudNamespace : deployedOn -OCloudNamespace "1..*" --> "1" NodeCluster : deployedOn -NodeCluster "1..*" --> "1..*" OCloudSite : locatedAt -} -@enduml -``` - -![UML Class Diagram titled 'ORAN.SMO.TEIV.Cloud' showing relationships between CloudifiedNF, NFDeployment, OCloudNamespace, NodeCluster, and OCloudSite.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) - -``` - -classDiagram - class CloudifiedNF - class NFDeployment - class OCloudNamespace - class NodeCluster - class OCloudSite - - CloudifiedNF "1" --> "1..*" NFDeployment : comprizes - NFDeployment "1..*" --> "1..*" OCloudNamespace : deployedOn - OCloudNamespace "1..*" --> "1" NodeCluster : deployedOn - NodeCluster "1..*" --> "1..*" OCloudSite : locatedAt - note right of OCloudSite : Has location info. - -``` - -The diagram illustrates the O-Cloud relationship view within the ORAN.SMO.TEIV.Cloud namespace. It features five classes: CloudifiedNF, NFDeployment, OCloudNamespace, NodeCluster, and OCloudSite. CloudifiedNF (1) comprizes multiple NFDeployments (1..\*). NFDeployments (1..\*) are deployed on OCloudNamespaces (1..\*). OCloudNamespaces (1..\*) are deployed on NodeClusters (1). NodeClusters (1..\*) are located at OCloudSites (1..\*). A note indicates that OCloudSite has location information. - -UML Class Diagram titled 'ORAN.SMO.TEIV.Cloud' showing relationships between CloudifiedNF, NFDeployment, OCloudNamespace, NodeCluster, and OCloudSite. - -Figure 4.3.2.3.1-1: ORAN SMO TE&IV O-Cloud relationship view - -##### 4.3.2.3.2 Inheritance - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictumlhide empty memberset namespaceSeparator nonenamespace ORAN.SMO.TEIV { - abstract class TopologyEntity_ - namespace ORAN.SMO.TEIV.Cloud { - class CloudifiedNF - class NFDeployment - class OCloudNamespace - class NodeCluster - class OCloudSite - } - TopologyEntity_ <|-- CloudifiedNFTopologyEntity_ - TopologyEntity_ <|-- NFDeploymentTopologyEntity_ - TopologyEntity_ <|-- - @enduml - -``` - -![UML inheritance diagram showing TopologyEntity_ as the base class for OCloudSite, NodeCluster, OCloudNamespace, NFDeployment, and CloudifiedNF. The diagram is part of the ORAN.SMO.TEIV.Cloud package.](5445597cceefaca1ac89e710fe339325_img.jpg) - -``` - -OCloudNamespaceTopologyEntity <|-- NodeClusterTopologyEntity <|-- OCloudSite}@enduml - -``` - -``` - -classDiagram - class TopologyEntity_ - class OCloudSite - class NodeCluster - class OCloudNamespace - class NFDeployment - class CloudifiedNF - - TopologyEntity_ <|-- OCloudSite - TopologyEntity_ <|-- NodeCluster - TopologyEntity_ <|-- OCloudNamespace - TopologyEntity_ <|-- NFDeployment - TopologyEntity_ <|-- CloudifiedNF - -``` - -UML inheritance diagram showing TopologyEntity\_ as the base class for OCloudSite, NodeCluster, OCloudNamespace, NFDeployment, and CloudifiedNF. The diagram is part of the ORAN.SMO.TEIV.Cloud package. - -Figure 4.3.2.3.2-1: ORAN SMO TE&IV O-Cloud inheritance view - -#### 4.3.2.4 Class definitions - -##### 4.3.2.4.1 CloudifiedNF - -###### 4.3.2.4.1.1 Definitions - -This class provides the TE&IV resource representation of Cloudified NF using the equivalent concept as defined in O-RAN.WG6.O2-GA&P [7]. - -###### 4.3.2.4.1.2 Attributes - -The CloudifiedNF TEC includes the attributes inherited from *TopologyEntity\_* and has the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|------------------------|---|------------|------------|-------------|--------------| -| cloudifiedNfId | M | T | F | F | T | -| serviceOrchestrationId | M | T | F | F | T | - -###### 4.3.2.4.1.3 Attribute constraints - -Not specified in the present version of the document. - -###### 4.3.2.4.1.4 Notifications - -Not specified in the present version of the document. - -###### 4.3.2.4.1.5 State diagram - -Not specified in the present version of the document. - -##### 4.3.2.4.2 NFDeployment - -###### 4.3.2.4.2.1 Definitions - -This class provides the TE&IV resource representation of NF Deployment using the equivalent concept as defined in O-RAN.WG6.O2-GA&P [7]. - -###### 4.3.2.4.2.2 Attributes - -The NFDeployment TEC includes the attributes inherited from *TopologyEntity\_* and has the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|-------------------------|---|------------|------------|-------------|--------------| -| nfDeploymentId | M | T | F | F | T | -| resourceOrchestrationId | M | T | F | F | T | -| serviceOrchestrationId | M | T | F | F | T | - -###### 4.3.2.4.2.3 Attribute constraints - -Not specified in the present version of the document. - -###### 4.3.2.4.2.4 Notifications - -Not specified in the present version of the document. - -###### 4.3.2.4.2.5 State diagram - -Not specified in the present version of the document. - -##### 4.3.2.4.3 OCloudNamespace - -###### 4.3.2.4.3.1 Definitions - -This class provides the TE&IV resource representation of OCloud Namespace using the equivalent concept as “containerNamespace” defined in O-RAN.WG6.O2DMS-INTERFACE-ETSI-NFV-PROFILE [8] and as “namespace” in O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE [9]. - -###### 4.3.2.4.3.2 Attributes - -The OCloudNamespace TEC includes the attributes inherited from *TopologyEntity\_* and has the following attributes - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|---------------------|---|------------|------------|-------------|--------------| -| oCloudNamespaceName | M | T | F | F | T | - -###### 4.3.2.4.3.3 Attribute constraints - -Not specified in the present version of the document. - -###### 4.3.2.4.3.4 Notifications - -Not specified in the present version of the document. - -###### 4.3.2.4.3.5 State diagram - -Not specified in the present version of the document. - -##### 4.3.2.4.4 NodeCluster - -###### 4.3.2.4.4.1 Definitions - -This class provides the TE&IV resource representation of O-Cloud Node Cluster using the equivalent concept as defined in O-RAN.WG6.O2-GA&P [7]. - -###### 4.3.2.4.4.2 Attributes - -The NodeCluster TEC includes the attributes inherited from *TopologyEntity\_* and has the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|-------------------------|---|------------|------------|-------------|--------------| -| nodeClusterId | M | T | F | F | T | -| serviceOrchestrationId | M | T | F | F | T | -| resourceOrchestrationId | M | T | F | F | T | -| nodeClusterName | M | T | F | F | T | - -###### 4.3.2.4.4.3 Attribute constraints - -Not specified in the present version of the document. - -###### 4.3.2.4.4.4 Notifications - -Not specified in the present version of the document. - -###### 4.3.2.4.4.5 State diagram - -Not specified in the present version of the document. - -##### 4.3.2.4.5 OCloudSite - -###### 4.3.2.4.5.1 Definitions - -This class provides the TE&IV resource representation of O-Cloud Site using the equivalent concept as defined in O-RAN.WG6.O2-GA&P [7]. - -###### 4.3.2.4.5.2 Attributes - -The OCloudSite TEC includes the attributes inherited from *TopologyEntity\_* and has the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|--------------------|---|------------|------------|-------------|--------------| -| oCloudSiteLocation | M | T | F | F | T | -| oCloudSiteId | M | T | F | F | T | -| supportedMITs | M | T | F | F | T | - -###### 4.3.2.4.5.3 Attribute constraints - -Not specified in the present version of the document. - -###### 4.3.2.4.5.4 Notifications - -Not specified in the present version of the document. - -###### 4.3.2.4.5.5 State diagram - -Not specified in the present version of the document. - -#### 4.3.2.5 Attribute definitions - -##### 4.3.2.5.1 Attribute properties - -The following table defines the properties of attributes specified in the present document. - -**Table 4.3.2.5.1-1: Attribute properties** - -| Attribute Name | Documentation and Allowed Values | Properties | Source Domain | -|----------------|----------------------------------|---------------------------------------------------------------------|---------------| -| cloudifiedNFId | Identifier of the Cloudified NF. | type: String
multiplicity: 1
isOrdered: N/A
isUnique: True | Orchestrator | - -| Attribute Name | Documentation and Allowed Values | Properties | Source Domain | -|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|-----------------------| -| | | defaultValue: None | | -| nfDeploymentId | Identifier of the NF Deployment. | type: String
multiplicity: 1
isOrdered: N/A
isUnique: True
defaultValue: None | Orchestrator | -| oCloudNamespaceName | Name of the O-Cloud Namespace. | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | FOCOM | -| serviceOrchestrationId | Identifier of the service as allocated by the service orchestrator. | type: String
multiplicity: 1
isOrdered: N/A
isUnique: True
defaultValue: None | SO | -| resourceOrchestrationId | Identifier of the resource instance allocated by the resource orchestrator. | type: String
multiplicity: 1
isOrdered: N/A
isUnique: True
defaultValue: None | Resource Orchestrator | -| nodeClusterId | Identifier of the Node Cluster.[18] | type: String
multiplicity: 1
isOrdered: N/A
isUnique: True
defaultValue: None | FOCOM | -| nodeClusterName | Name of the Node Cluster. | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | FOCOM | -| oCloudSiteLocation | Indicates the location of the OCloud Site. It describes address and coordinate. | type: GeoInformation
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | SMO / FOCOM | -| oCloudSiteId | Identifier of the O-Cloud Site. [18] | type: String
multiplicity: 1
isOrdered: N/A
isUnique: True
defaultValue: None | FOCOM | -| supportedMITs | List of names and versions of supported Managed Infrastructure Templates (MIT) that may be referenced to deploy an O-Cloud node cluster and/or O-Cloud infrastructure resources.
[clause 3.4.3.8 [7]] | type: String
multiplicity: 1..n
isOrdered: N/A
isUnique: N/A
defaultValue: None | FOCOM | - -### 4.3.3 Namespace ORAN.SMO.TEIV.REL-Cloud-RAN - -#### 4.3.3.1 Namespace overview - -This namespace contains the relationship between ORAN.SMO.TEIV.RAN to ORAN.SMO.TEIV.Cloud namespaces. - -The *ORANNetworkFunction\_* abstract class depicted in the figure 4.3.3.3.1-1 is a generalization of the various O-RAN Network Functions and shall be associated from the ORAN.SMO.TEIV.RAN namespace. - -The *NFDeployment\_REL\_NF\_* abstract class depicted in the figure 4.3.3.3.1-1 is a generalization of the various relationships between the O-RAN Network Functions and its associated NF Deployments. - -The NFDeployment class depicted in the figure 4.3.3.3.1-1 shall be associated from the ORAN.SMO.TEIV.Cloud namespace. - -#### 4.3.3.2 Imported associated information - -##### 4.3.3.2.1 Imported information entities and local labels - -Imported information entities and local labels is not defined in the present version of the document. - -##### 4.3.3.2.2 Associated information entities and local labels - -Associated information entities and local labels is not defined in the present version of the document. - -#### 4.3.3.3 Class diagram - -##### 4.3.3.3.1 Relationships - -``` -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV.RAN { - abstract class ORANNetworkFunction_ -} -namespace ORAN.SMO.TEIV.REL-Cloud-RAN { - abstract class NFDeployment_REL_NF_ -} -namespace ORAN.SMO.TEIV.Cloud { - class NFDeployment -} - -NFDeployment "1..n" <-> "1..n" ORANNetworkFunction_ -NFDeployment_REL_NF_ "1" - [hidden]d- NFDeployment -NFDeployment_REL_NF_ - [hidden]d- ORANNetworkFunction_ -NFDeployment_REL_NF_ . (NFDeployment, ORANNetworkFunction_) -@enduml -``` - -![UML Class diagram showing the relationship between NFDeployment and ORANNetworkFunction_. NFDeployment_REL_NF_ is an abstract class in the ORAN.SMO.TEIV.REL-Cloud-RAN namespace. NFDeployment is a class in the ORAN.SMO.TEIV.Cloud namespace. ORANNetworkFunction_ is an abstract class in the ORAN.SMO.TEIV.RAN namespace. A dashed line connects NFDeployment_REL_NF_ to a bidirectional association between NFDeployment and ORANNetworkFunction_. The association has a multiplicity of 1..n at both ends.](a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg) - -``` - -classDiagram - namespace ORAN_SMO_TEIV_REL-Cloud-RAN { - class NFDeployment_REL_NF_ { - <> - } - } - namespace ORAN_SMO_TEIV_Cloud { - class NFDeployment - } - namespace ORAN_SMO_TEIV_RAN { - class ORANNetworkFunction_ { - <> - } - } - NFDeployment "1..n" -- "1..n" ORANNetworkFunction_ - (NFDeployment, ORANNetworkFunction_) .. NFDeployment_REL_NF_ - -``` - -UML Class diagram showing the relationship between NFDeployment and ORANNetworkFunction\_. NFDeployment\_REL\_NF\_ is an abstract class in the ORAN.SMO.TEIV.REL-Cloud-RAN namespace. NFDeployment is a class in the ORAN.SMO.TEIV.Cloud namespace. ORANNetworkFunction\_ is an abstract class in the ORAN.SMO.TEIV.RAN namespace. A dashed line connects NFDeployment\_REL\_NF\_ to a bidirectional association between NFDeployment and ORANNetworkFunction\_. The association has a multiplicity of 1..n at both ends. - -**Figure 4.3.3.3.1-1: SMO TE&IV Cloud-RAN relationship model** - -``` -@startuml -skin rose -``` - -``` - -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV.RAN { - abstract class ORANNetworkFunction_ -} - -namespace ORAN.SMO.TEIV.Cloud { - class NFDeployment -} - -NFDeployment <-right-> ORANNetworkFunction_ : \t NFDeployment_REL_NF_ \t\t -@enduml - -``` - -![UML class diagram showing a relationship between NFDeployment and ORANNetworkFunction_.](26d664119ad25250780f554633444e54_img.jpg) - -``` - -classDiagram - namespace ORAN.SMO.TEIV.Cloud { - class NFDeployment - } - namespace ORAN.SMO.TEIV.RAN { - class ORANNetworkFunction_ - } - NFDeployment -- ORANNetworkFunction_ : NFDeployment_REL_NF_ - -``` - -The diagram illustrates a UML class diagram with two classes: **ORAN.SMO.TEIV.Cloud.NFDeployment** and **ORAN.SMO.TEIV.RAN.ORANNetworkFunction\_**. A bidirectional association arrow connects the **NFDeployment** class and the **ORANNetworkFunction\_** class. The association is labeled with the stereotype ***NFDeployment\_REL\_NF\_***. - -UML class diagram showing a relationship between NFDeployment and ORANNetworkFunction\_. - -**Figure 4.3.3.1-2: Simplified SMO TE&IV Cloud-RAN relationship model** - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV.RAN { - class ODFunction{ - } -} - -namespace ORAN.SMO.TEIV.REL-Cloud-RAN { - class NFDeployment_serves_ODFunction{ - } -} - -namespace ORAN.SMO.TEIV.Cloud { - class NFDeployment{ - } -} - -NFDeployment " \n1..n\nserved-oduFunction" <---> "serving-nfDeployment\n1..n\nn " -ODFunction : > serves -NFDeployment_serves_ODFunction . (NFDeployment, ODFunction) -@enduml - -``` - -![UML Class Diagram showing the relationship between NFDeployment and ODUFunction. NFDeployment (in ORAN.SMO.TEIV.Cloud) has a 1..n association with ODUFunction (in ORAN.SMO.TEIV.RAN) via NFDeployment_serves_ODUFunction (in ORAN.SMO.TEIV.REL-Cloud-RAN). The association is labeled 'served-oduFunction' and 'serves'.](5a1abd59a95fa47ae192807de151e9eb_img.jpg) - -``` - -classDiagram - namespace ORAN.SMO.TEIV.Cloud { - class NFDeployment - } - namespace ORAN.SMO.TEIV.RAN { - class ODUFunction - } - namespace ORAN.SMO.TEIV.REL-Cloud-RAN { - class NFDeployment_serves_ODUFunction - } - - NFDeployment "1..n" -- "1..n" ODUFunction : serves - (NFDeployment, ODUFunction) .. NFDeployment_serves_ODUFunction - note for NFDeployment "served-oduFunction" - note for ODUFunction "serving-nfDeployment" - -``` - -UML Class Diagram showing the relationship between NFDeployment and ODUFunction. NFDeployment (in ORAN.SMO.TEIV.Cloud) has a 1..n association with ODUFunction (in ORAN.SMO.TEIV.RAN) via NFDeployment\_serves\_ODUFunction (in ORAN.SMO.TEIV.REL-Cloud-RAN). The association is labeled 'served-oduFunction' and 'serves'. - -Figure 4.3.3.3.1-3: NFDeployment and ODUFunction relationship model - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV.RAN { - class OCUCPFunction{ - } -} - -namespace ORAN.SMO.TEIV.REL-Cloud-RAN { - class NFDeployment_serves_OCUCPFunction{ - } -} - -namespace ORAN.SMO.TEIV.Cloud { - class NFDeployment{ - } -} - -NFDeployment " \n1..n\nserved-ocucpFunction" <---> "serving-nfDeployment\n1..n\n\n " OCUCPFunction: > serves - -``` - -``` -NFDeployment_serves_OCUCPFunction . (NFDeployment, OCUCPFunction) -@enduml -``` - -![UML Class Diagram showing the relationship between NFDeployment and OCUCPFunction. NFDeployment is in the ORAN.SMO.TEIV.Cloud namespace. OCUCPFunction is in the ORAN.SMO.TEIV.RAN namespace. They are connected by an association class named NFDeployment_serves_OCUCPFunction, which resides in the ORAN.SMO.TEIV.REL-Cloud-RAN namespace. The association is labeled 'serves' with a downward arrow. Multiplicities are 1..n at both ends: 'served-ocucpFunction' near NFDeployment and 'serving-nfDeployment' near OCUCPFunction.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) - -``` - -classDiagram - namespace ORAN_SMO_TEIV_Cloud { - class NFDeployment - } - namespace ORAN_SMO_TEIV_RAN { - class OCUCPFunction - } - namespace ORAN_SMO_TEIV_REL_Cloud_RAN { - class NFDeployment_serves_OCUCPFunction - } - - NFDeployment "1..n" -- "1..n" OCUCPFunction : serves - (NFDeployment, OCUCPFunction) .. NFDeployment_serves_OCUCPFunction - -``` - -UML Class Diagram showing the relationship between NFDeployment and OCUCPFunction. NFDeployment is in the ORAN.SMO.TEIV.Cloud namespace. OCUCPFunction is in the ORAN.SMO.TEIV.RAN namespace. They are connected by an association class named NFDeployment\_serves\_OCUCPFunction, which resides in the ORAN.SMO.TEIV.REL-Cloud-RAN namespace. The association is labeled 'serves' with a downward arrow. Multiplicities are 1..n at both ends: 'served-ocucpFunction' near NFDeployment and 'serving-nfDeployment' near OCUCPFunction. - -**Figure 4.3.3.1-4: NFDeployment and OCUCPFunction relationship model** - -``` -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV.RAN { - class OCUCPFunction{ - } -} - -namespace ORAN.SMO.TEIV.REL-Cloud-RAN { - class NFDeployment_serves_OCUCPFunction{ - } -} - -namespace ORAN.SMO.TEIV.Cloud { - class NFDeployment{ - } -} - -``` - -``` - -NFDeployment " \n1..n\nnserved-ocuupFunction" <---> "serving-nfDeployment\n1..n\nn " -OCUUPFunction: > serves -NFDeployment_serves_OCUUPFunction . (NFDeployment, OCUUPFunction) -@enduml - -``` - -![UML Class Diagram showing the relationship between NFDeployment and OCUUPFunction. NFDeployment is in the ORAN.SMO.TEIV.Cloud namespace, and OCUUPFunction is in the ORAN.SMO.TEIV.RAN namespace. A directed association arrow points from NFDeployment to OCUUPFunction, labeled 'serves'. The multiplicity '1..n' is shown at the NFDeployment end with the role name 'served-ocuupFunction'. The multiplicity '1..n' is shown at the OCUUPFunction end with the role name 'serving-nfDeployment'. A class box labeled 'NFDeployment_serves_OCUUPFunction' is shown in the ORAN.SMO.TEIV.REL-Cloud-RAN namespace, with a dashed line connecting it to the association arrow.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) - -UML Class Diagram showing the relationship between NFDeployment and OCUUPFunction. NFDeployment is in the ORAN.SMO.TEIV.Cloud namespace, and OCUUPFunction is in the ORAN.SMO.TEIV.RAN namespace. A directed association arrow points from NFDeployment to OCUUPFunction, labeled 'serves'. The multiplicity '1..n' is shown at the NFDeployment end with the role name 'served-ocuupFunction'. The multiplicity '1..n' is shown at the OCUUPFunction end with the role name 'serving-nfDeployment'. A class box labeled 'NFDeployment\_serves\_OCUUPFunction' is shown in the ORAN.SMO.TEIV.REL-Cloud-RAN namespace, with a dashed line connecting it to the association arrow. - -Figure 4.3.3.3.1-5: NFDeployment and OCUUPFunction relationship model - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV.RAN { -class NearRTRICFunction{ -} -} - -namespace ORAN.SMO.TEIV.REL-Cloud-RAN { -class NFDeployment_serves_NearRTRICFunction{ -} -} - -namespace ORAN.SMO.TEIV.Cloud { -class NFDeployment{ -} -} - -NFDeployment " \n1..n\nnserved-nearRTRICFunction" <---> "serving-nfDeployment\n1..n\nn " -NearRTRICFunction: > serves -NFDeployment_serves_NearRTRICFunction . (NFDeployment, NearRTRICFunction) - -``` - -``` -@enduml -``` - -![UML Class diagram showing the relationship between NFDeployment and NearRTRICFunction. NFDeployment (in ORAN.SMO.TEIV.Cloud) has a 1..n association with NearRTRICFunction (in ORAN.SMO.TEIV.RAN) labeled 'serves'. NFDeployment_serves_NearRTRICFunction (in ORAN.SMO.TEIV.REL-Cloud-RAN) is an association class for this relationship.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) - -``` - -classDiagram - class NFDeployment { - <> - } - class NearRTRICFunction { - <> - } - class NFDeployment_serves_NearRTRICFunction { - <> - } - - NFDeployment "1..n" -- "1..n" NearRTRICFunction : serves - NFDeployment_serves_NearRTRICFunction -- NFDeployment_serves_NearRTRICFunction - -``` - -UML Class diagram showing the relationship between NFDeployment and NearRTRICFunction. NFDeployment (in ORAN.SMO.TEIV.Cloud) has a 1..n association with NearRTRICFunction (in ORAN.SMO.TEIV.RAN) labeled 'serves'. NFDeployment\_serves\_NearRTRICFunction (in ORAN.SMO.TEIV.REL-Cloud-RAN) is an association class for this relationship. - -Figure 4.3.3.3.1-6: NFDeployment and NearRTRICFunction relationship model - -##### 4.3.3.3.2 Inheritance - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none -namespace ORAN.SMO.TEIV { - abstract class Topology_REL_ {} -} -namespace ORAN.SMO.TEIV.REL-Cloud-RAN { - - abstract class NFDeployment_REL_NF_ {} - - Topology_REL_ <|-- NFDeployment_REL_NF_ - NFDeployment_REL_NF_ <|-- NFDeployment_serves_ODUFunction - NFDeployment_REL_NF_ <|-- NFDeployment_serves_OCUCPFunction - NFDeployment_REL_NF_ <|-- NFDeployment_serves_OCUPPFunction - NFDeployment_REL_NF_ <|-- NFDeployment_serves_NearRTRICFunction -} - -@enduml - -``` - -![UML Class diagram showing the hierarchy of NFDeployment_REL_NF_ classes. The base class is ORAN.SMO.TEIV.Topology_REL_. The diagram shows a box labeled ORAN.SMO.TEIV.REL-Cloud-RAN containing four subclasses: NFDeployment_serves_ODUFunction, NFDeployment_serves_OCUCPFunction, NFDeployment_serves_OCUUPFunction, and NFDeployment_serves_NearRTRICFunction. All four subclasses inherit from a central class NFDeployment_REL_NF_, which in turn inherits from the base class Topology_REL_.](fa01531ea2c45beeb4036005da3037a4_img.jpg) - -``` - -classDiagram - class ORAN.SMO.TEIV.Topology_REL_ - class NFDeployment_REL_NF_ - class NFDeployment_serves_ODUFunction - class NFDeployment_serves_OCUCPFunction - class NFDeployment_serves_OCUUPFunction - class NFDeployment_serves_NearRTRICFunction - - NFDeployment_serves_ODUFunction --|> NFDeployment_REL_NF_ - NFDeployment_serves_OCUCPFunction --|> NFDeployment_REL_NF_ - NFDeployment_serves_OCUUPFunction --|> NFDeployment_REL_NF_ - NFDeployment_serves_NearRTRICFunction --|> NFDeployment_REL_NF_ - NFDeployment_REL_NF_ --|> ORAN.SMO.TEIV.Topology_REL_ - -``` - -UML Class diagram showing the hierarchy of NFDeployment\_REL\_NF\_ classes. The base class is ORAN.SMO.TEIV.Topology\_REL\_. The diagram shows a box labeled ORAN.SMO.TEIV.REL-Cloud-RAN containing four subclasses: NFDeployment\_serves\_ODUFunction, NFDeployment\_serves\_OCUCPFunction, NFDeployment\_serves\_OCUUPFunction, and NFDeployment\_serves\_NearRTRICFunction. All four subclasses inherit from a central class NFDeployment\_REL\_NF\_, which in turn inherits from the base class Topology\_REL\_. - -Figure 4.3.3.3.2-1: TE&IV Cloud-RAN Serves Relationship Generalization - -#### 4.3.3.4 Class definitions - -##### 4.3.3.4.1 NFDeployment\_serves\_ODUFunction - -###### 4.3.3.4.1.1 Definitions - -This class provides the Topology Relationship between the NFDeployment and the ODUFunction Topology Entities as shown in figure 4.3.3.3.1-3. This class represents the relationship type of the NF Deployment serving the functionality of the ODU Function. - -###### 4.3.3.4.1.2 Attributes - -The NFDeployment\_serves\_ODUFunction TRC includes the attributes inherited from *TopologyRel\_* and has the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|----------------------|---|------------|------------|-------------|--------------| -| served-oduFunction | M | T | F | F | T | -| serving-nfDeployment | M | T | F | F | T | - -###### 4.3.3.4.1.3 Attribute constraints - -None. - -###### 4.3.3.4.1.4 Notifications - -None. - -###### 4.3.3.4.1.5 State diagram - -None. - -##### 4.3.3.4.2 NFDeployment\_serves\_OCUCPFunction - -###### 4.3.3.4.2.1 Definitions - -This class provides the Topology Relationship between the NFDeployment and the OCUCPFunction Topology Entities as shown in figure 4.3.3.3.1-4. This class represents the relationship type of the NF Deployment serving the functionality of the OCUCP Function. - -###### 4.3.3.4.2.2 Attributes - -The NFDeployment\_serves\_OCUCPFunction TRC includes the attributes inherited from *TopologyRel\_* and has the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|----------------------|---|------------|------------|-------------|--------------| -| served-ocucpFunction | M | T | F | F | T | -| serving-nfDeployment | M | T | F | F | T | - -###### 4.3.3.4.2.3 Attribute constraints - -None. - -###### 4.3.3.4.2.4 Notifications - -None. - -###### 4.3.3.4.2.5 State diagram - -None. - -##### 4.3.3.4.3 NFDeployment\_serves\_OCUUPFunction - -###### 4.3.3.4.3.1 Definitions - -This class provides the Topology Relationship between the NFDeployment and the OCUUPFunction Topology Entities as shown in figure 4.3.3.3.1-5. This class represents the relationship type of the NF Deployment serving the functionality of the OCUUP Function. - -###### 4.3.3.4.3.2 Attributes - -The NFDeployment\_serves\_OCUUPFunction TRC includes the attributes inherited from *TopologyRel\_* and has the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|----------------------|---|------------|------------|-------------|--------------| -| served-ocuupFunction | M | T | F | F | T | -| serving-nfDeployment | M | T | F | F | T | - -###### 4.3.3.4.3.3 Attribute constraints - -None. - -###### 4.3.3.4.3.4 Notifications - -None. - -###### 4.3.3.4.3.5 State diagram - -None. - -##### 4.3.3.4.4 NFDeployment\_serves\_NearRTRICFunction - -###### 4.3.3.4.4.1 Definitions - -This class provides the Topology Relationship between the NFDeployment and the NearRTRICFunction Topology Entities as shown in figure 4.3.3.3.1-6. This class represents the relationship type of the NF Deployment serving the functionality of the Near-RT RIC Function. - -###### 4.3.3.4.4.2 Attributes - -The NFDeployment\_serves\_NearRTRICFunction TRC includes the attributes inherited from *TopologyRel\_* and has the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|--------------------------|---|------------|------------|-------------|--------------| -| served-nearRTRICFunction | M | T | F | F | T | -| serving-nfDeployment | M | T | F | F | T | - -###### 4.3.3.4.4.3 Attribute constraints - -None. - -###### 4.3.3.4.4.4 Notifications - -None. - -###### 4.3.3.4.4.5 State diagram - -None. - -##### 4.3.3.4.4 *NFDeployment\_REL\_NF\_* - -###### 4.3.3.4.4.1 Definitions - -This abstract class is provided for sub-classing only and is used to generalize the relationship classes in this namespace. - -###### 4.3.3.4.4.2 Attributes - -None. - -###### 4.3.3.4.4.3 Attribute constraints - -None. - -###### 4.3.3.4.4.4 Notifications - -None. - -###### 4.3.3.4.4.5 State diagram - -None. - -#### 4.3.3.5 Attribute definitions - -##### 4.3.3.5.1 Attribute properties - -The following table defines the properties of attributes specified in the present document. - -**Table 4.3.3.5.1-1: Attribute properties** - -| Attribute Name | Documentation and Allowed Values | Properties | Source Domain | -|--------------------------|---------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|---------------| -| serving-nfDeployment | This represents the Topology Entity Id(s) of the NF Deployment instance(s) serving an O-RAN Network Function. | type: URN
multiplicity: 1..n
isOrdered: False
isUnique: True
defaultValue: None | TE&IV | -| served-oduFunction | This represents the Topology Entity Id(s) of the ODU Function instance(s) served by an NF Deployment. | type: URN
multiplicity: 1..n
isOrdered: False
isUnique: True
defaultValue: None | TE&IV | -| served-ocucpFunction | This represents the Topology Entity Id(s) of the OCUCP function instance(s) served by an NF Deployment. | type: URN
multiplicity: 1..n
isOrdered: False
isUnique: True
defaultValue: None | TE&IV | -| served-ocuupFunction | This represents the Topology Entity Id(s) of the OCUUP function instance(s) served by an NF Deployment. | type: URN
multiplicity: 1..n
isOrdered: False
isUnique: True
defaultValue: None | TE&IV | -| served-nearRTRICFunction | This represents the Topology Entity Id(s) of the Near-RT RIC function instance(s) served by an NF deployment. | type: URN
multiplicity: 1..n
isOrdered: False
isUnique: True
defaultValue: None | TE&IV | - -### 4.3.4 Namespace ORAN.SMO.TEIV - -#### 4.3.4.1 Overview - -This section contains the commonly used O-RAN TE&IV basic types and abstractions for Topology Entities and Topology Relationships. - -#### 4.3.4.2 Imported associated information - -##### 4.3.4.2.1 Imported information entities and local labels - -Imported information entities and local labels is not defined in the present version of the document. - -##### 4.3.4.2.2 Associated information entities and local labels - -Associated information entities and local labels is not defined in the present version of the document. - -#### 4.3.4.3 Class diagram - -##### 4.3.4.3.1 Relationships - -Not specified in the present version of the document. - -##### 4.3.4.3.2 Inheritance - -Not specified in the present version of the document. - -#### 4.3.4.4 Class definitions - -##### 4.3.4.4.1 *TopologyEntity\_* - -###### 4.3.4.4.1.1 Definitions - -This abstract class represents the Topology Entities in the O-RAN TE&IV Information Models. All other <> specified in this document must inherit from *TopologyEntity\_* directly or indirectly. - -###### 4.3.4.4.1.2 Attributes - -This class shall have the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|------------------|---|------------|------------|-------------|--------------| -| topologyEntityId | M | T | F | T | F | -| sourceIds | M | T | F | F | T | - -###### 4.3.4.4.1.3 Attribute constraints - -Not specified in the present version of the document. - -###### 4.3.4.4.1.4 Notifications - -Not specified in the present version of the document. - -###### 4.3.4.4.1.5 State diagram - -Not specified in the present version of the document. - -##### 4.3.4.4.2 *TopologyRel\_* - -###### 4.3.4.4.2.1 Definitions - -This abstract class represents the Topology Relationships between Topology Entities in the O-RAN TE&IV Information Models. All other <> specified in this document must inherit from *TopologyRel\_* directly or indirectly. - -###### 4.3.4.4.2.2 Attributes - -This class shall have the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|------------------------|---|------------|------------|-------------|--------------| -| topologyRelationshipId | M | T | F | T | F | -| sourceIds | M | T | F | F | T | - -###### 4.3.4.4.2.3 Attribute constraints - -Not specified in the present version of the document. - -###### 4.3.4.4.2.4 Notifications - -Not specified in the present version of the document. - -###### 4.3.4.4.2.5 State diagram - -Not specified in the present version of the document. - -#### 4.3.4.5 Attribute definitions - -##### 4.3.4.5.1 Attribute properties - -The following table defines the properties of attributes specified in the present document. - -**Table 4.3.4.5.1-1: Attribute properties** - -| Attribute Name | Documentation and Allowed Values | Properties | Source Domain | -|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|---------------| -| topologyEntityId | Unique identifier of the Topology Entity.

This identity is represented using a URN notation format [14]. | type: URN
multiplicity: 1
isOrdered: N/A
isUnique: True
defaultValue: None | SMO/TE&IV | -| topologyRelationshipId | Unique identifier of the Topology Relationship.

This identity is represented using a URN notation format [14]. | type: URN
multiplicity: 1
isOrdered: N/A
isUnique: True
defaultValue: None | SMO/TE&IV | -| sourceIds | Identities of the underlying topology resources represented by the Topology Entity or underlying topology resources participating in the Topology Relationship.

The sourceIds are represented using a URN notation format [14].

A TE&IV consumer can use the identifiers to navigate to the source domain objects. | type: URN
multiplicity: 1..N
isOrdered: False
isUnique: True
defaultValue: None | e.g., O1 | - -### 4.3.5 Namespace ORAN.SMO.TEIV.Physical - -#### 4.3.5.1 Namespace overview - -This namespace contains the Topology Entities and Topology Relationship in the Physical domain, which comprises of the deployment aspects of O-RAN Physical Network Functions. - -#### 4.3.5.2 Imported associated information - -##### 4.3.5.2.1 Imported information entities and local labels - -**Table 4.3.5.2.1-1: Imported information entities and local labels** - -| Label reference | Local label | -|---------------------------------------------|------------------------| -| TEC, TopologyEntity_ | TopologyEntity_ | -| TRC, TopologyRel_ | TopologyRel_ | -| 3GPP TS 28.622[16], dataType, GeoCoordinate | GeoCoordinate | - -##### 4.3.5.2.2 Associated information entities and local labels - -Associated information entities and local labels is not defined in the present version of the document. - -#### 4.3.5.3 Class diagram - -##### 4.3.5.3.1 Relationships - -``` -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -skinparam linetype ortho -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV.Physical { -class PhysicalAppliance_installedAt_Site -class PhysicalAppliance -class Site - -PhysicalAppliance "1..n\ninstalling-site\n\n" <--> "installed-physicalAppliance \n1" -Site : > installedAt -PhysicalAppliance_installedAt_Site . (PhysicalAppliance, Site) -} -@enduml -``` - -![UML Class diagram showing relationships between PhysicalAppliance, PhysicalAppliance_installedAt_Site, and Site classes within the ORAN.SMO.TEIV.Physical namespace.](fcbc3c31776721edc98ceb1944ec438f_img.jpg) - -``` - -classDiagram - namespace ORAN.SMO.TEIV.Physical { - class PhysicalAppliance - class Site - class PhysicalAppliance_installedAt_Site - } - PhysicalAppliance "1..n" -- "1" Site : installedAt - (PhysicalAppliance, Site) .. PhysicalAppliance_installedAt_Site - - note for PhysicalAppliance "installing-site" - note for Site "installed-physicalAppliance" - -``` - -The diagram illustrates the SMO TE&IV Physical Deployment relationship model within the **ORAN.SMO.TEIV.Physical** namespace. It features three classes: **PhysicalAppliance**, **PhysicalAppliance\_installedAt\_Site**, and **Site**. **PhysicalAppliance** has a relationship with **Site** labeled **installedAt** (indicated by a downward arrow). The multiplicity is **1..n** at the **PhysicalAppliance** end with the role **installing-site**, and **1** at the **Site** end with the role **installed-physicalAppliance**. **PhysicalAppliance\_installedAt\_Site** is an association class connected to the relationship between **PhysicalAppliance** and **Site** by a dashed line. - -UML Class diagram showing relationships between PhysicalAppliance, PhysicalAppliance\_installedAt\_Site, and Site classes within the ORAN.SMO.TEIV.Physical namespace. - -Figure 4.3.5.3.1-1: SMO TE&IV Physical Deployment relationship model - -``` -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none -``` - -``` -namespace ORAN.SMO.TEIV.Physical { - -class PhysicalAppliance { -} - -class Site { -} - -class Site -PhysicalAppliance -> Site : PhysicalAppliance_installedAt_Site -} -@enduml -``` - -![UML Class Diagram showing a directed association from PhysicalAppliance to Site with the role 'installedAt'.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) - -``` -classDiagram - class PhysicalAppliance - class Site - PhysicalAppliance --> Site : installedAt -``` - -UML Class Diagram showing a directed association from PhysicalAppliance to Site with the role 'installedAt'. - -Figure 4.3.5.3.1-2: Simplified SMO TE&IV Physical Deployment relationship model - -##### 4.3.5.3.2 Inheritance - -``` -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV{ - abstract class TopologyEntity_ {} -} - -namespace ORAN.SMO.TEIV.Physical { - class Site - class PhysicalAppliance -} - -TopologyEntity_ <|-- PhysicalAppliance -TopologyEntity_ <|-- Site - -@enduml - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV{ - abstract class TopologyRel_ {} -} - -namespace ORAN.SMO.TEIV.Physical { - class PhysicalAppliance_installedAt_Site -} - -TopologyRel_ <|-- PhysicalAppliance_installedAt_Site - -@enduml -``` - -![UML Class diagram showing inheritance from ORAN.SMO.TEIV.TopologyEntity_ to ORAN.SMO.TEIV.Physical. PhysicalAppliance and Site inherit from ORAN.SMO.TEIV.Physical.](02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg) - -``` - -classDiagram - class ORAN.SMO.TEIV { - TopologyEntity_ - } - class ORAN.SMO.TEIV.Physical { - PhysicalAppliance - Site - } - ORAN.SMO.TEIV.Physical --|> ORAN.SMO.TEIV - PhysicalAppliance --|> ORAN.SMO.TEIV.Physical - Site --|> ORAN.SMO.TEIV.Physical - -``` - -UML Class diagram showing inheritance from ORAN.SMO.TEIV.TopologyEntity\_ to ORAN.SMO.TEIV.Physical. PhysicalAppliance and Site inherit from ORAN.SMO.TEIV.Physical. - -Figure 4.3.5.3.2-1: ORAN SMO TE&IV Physical Toplogy Entity inheritance view - -![UML Class diagram showing inheritance from ORAN.SMO.TEIV.TopologyRel_ to ORAN.SMO.TEIV.Physical. PhysicalAppliance_installedAt_Site inherits from ORAN.SMO.TEIV.Physical.](04cfca33e3fc26513abe649d7474f733_img.jpg) - -``` - -classDiagram - class ORAN.SMO.TEIV { - TopologyRel_ - } - class ORAN.SMO.TEIV.Physical { - PhysicalAppliance_installedAt_Site - } - ORAN.SMO.TEIV.Physical --|> ORAN.SMO.TEIV - PhysicalAppliance_installedAt_Site --|> ORAN.SMO.TEIV.Physical - -``` - -UML Class diagram showing inheritance from ORAN.SMO.TEIV.TopologyRel\_ to ORAN.SMO.TEIV.Physical. PhysicalAppliance\_installedAt\_Site inherits from ORAN.SMO.TEIV.Physical. - -Figure 4.3.5.3.2-2: ORAN SMO TE&IV PhysicalAppliance\_installedAt\_Site inheritance view - -#### 4.3.5.4 Class definitions - -##### 4.3.5.4.1 PhysicalAppliance - -###### 4.3.5.4.1.1 Definitions - -This class provides the TE&IV resource representation of PhysicalAppliance using the equivalent concept as defined in O-RAN.WG1.OAD [6] clause 5. - -NOTE: The current version of this specification recommends that ORU be represented as a PhysicalAppliance with the applianceType as "ORU". - -###### 4.3.5.4.1.2 Attributes - -The PhysicalAppliance TEC includes the topology attributes inherited from *TopologyEntity\_* and have the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|----------------|---|------------|------------|-------------|--------------| -| vendorName | M | T | F | F | T | -| modelName | M | T | F | F | T | -| serialNumber | M | T | F | T | T | -| applianceType | M | T | F | F | T | - -###### 4.3.5.4.1.3 Attribute constraints - -Not specified in the present version of the document. - -###### 4.3.5.4.1.4 Notifications - -Not specified in the present version of the document. - -###### 4.3.5.4.1.5 State diagram - -Not specified in the present version of the document. - -##### 4.3.5.4.2 Site - -###### 4.3.5.4.2.1 Definitions - -This class provides the TE&IV resource representation of physical Site using the similar concept as O-Cloud Site defined in O-RAN.WG6.O2-GA&P [7]. - -###### 4.3.5.4.2.2 Attributes - -The Site TEC includes the attributes inherited from *TopologyEntity\_* and have the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|----------------|---|------------|------------|-------------|--------------| -| siteLocation | M | T | F | F | T | -| siteName | O | T | F | F | T | - -###### 4.3.5.4.2.3 Attribute constraints - -None. - -###### 4.3.5.4.2.4 Notifications - -There is no notification defined. - -###### 4.3.5.4.2.5 State diagram - -None. - -##### 4.3.5.4.3 Geoinformation <> - -###### 4.3.5.4.3.1 Definitions - -This data type provides the TE&IV resource representation of physical site location. - -###### 4.3.5.4.3.2 Attributes - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|----------------|---|------------|------------|-------------|--------------| -| address | O | T | F | F | T | -| coordinate | M | T | F | F | T | - -###### 4.3.5.4.3.3 Attribute constraints - -None. - -###### 4.3.5.4.4.4 Notifications - -There is no notification defined. - -###### 4.3.5.4.4.5 State diagram - -None. - -##### 4.3.5.4.4 PhysicalAppliance\_installedAt\_Site - -###### 4.3.5.4.4.1 Definitions - -This class provides the Topology Relationship between the PhysicalAppliance and the Site Topology Entities as shown in figure 4.3.5.3.2-2. This class represents the relationship type of the Site installing the Physical Appliance. - -###### 4.3.5.4.4.2 Attributes - -The Site TRC includes the attributes inherited from *TopologyRel\_* and have the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|-----------------------------|---|------------|------------|-------------|--------------| -| installing-site | M | T | F | F | T | -| installed-physicalAppliance | M | T | F | F | T | - -###### 4.3.5.4.4.3 Attribute constraints - -None. - -###### 4.3.5.4.4.4 Notifications - -There is no notification defined. - -##### 4.3.5.4.4.5 State diagram - -None. - -#### 4.3.5.5 Attribute definitions - -##### 4.3.5.5.1 Attribute properties - -The following table defines the properties of attributes specified in the present document. - -**Table 4.3.5.5.1-1: Attribute properties** - -| Attribute Name | Documentation and Allowed Values | Properties | Source Domain | -|----------------|------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------|---------------| -| vendorName | Name of the physical appliance vendor.
allowedValues: Not applicable | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | SMO | -| modelName | Name of the physical appliance model.
allowedValues: Not applicable | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | SMO | -| siteLocation | It indicates the location of the physical site. It describes Postal address and coordinate.
allowedValues: Not applicable | type: GeoInformation
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | SMO | -| siteName | Human readable name of the physical site as identified by the mobile network operator.
allowedValues: Not applicable | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | SMO | - -| Attribute Name | Documentation and Allowed Values | Properties | Source Domain | -|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|---------------| -| address | Postal address of the location.

allowedValues: Not applicable | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | SMO | -| coordinate | The latitude, longitude and altitude of the GeoCoordinate, defined in clause 4.3.53 of 3GPP TS 28.622 [16].
allowedValues: Not applicable | type: GeoCoordinate
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | SMO | -| installing-site | This represents the Topology Entity Id of the Site installing the PhysicalAppliance instance(s). | type: URN
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | TE&IV | -| installed-physicalAppliance | This represents the Topology Entity Id(s) of the PhysicalAppliance instance(s) installed at the Site. | type: URN
multiplicity: 1..n
isOrdered: False
isUnique: True
defaultValue: None | TE&IV | -| serialNumber | Serial number of the appliance | type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | SMO | -| applianceType | Indicates the type of PhysicalAppliance. | type: String
multiplicity: 0..1
isOrdered: N/A
isUnique: N/A
defaultValue: None | SMO | - -### 4.3.6 Namespace ORAN.SMO.TEIV.REL-Physical-RAN - -#### 4.3.6.1 Namespace overview - -This namespace contains the relationship between specific Topology Entities of the ORAN.SMO.TEIV.RAN to ORAN.SMO.TEIV.Physical namespaces and which represents the physical deployment aspects of ORAN Network Functions. - -#### 4.3.6.2 Imported associated information - -##### 4.3.6.2.1 Imported information entities and local labels - -Imported information entities and local labels is not defined in the present version of the document. - -##### 4.3.6.2.2 Associated information entities and local labels - -Associated information entities and local labels is not defined in the present version of the document. - -#### 4.3.6.3 Class diagram - -##### 4.3.6.3.1 Relationships - -``` -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -``` - -``` - -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV.RAN { - abstract class ORANNetworkFunction_ -} -namespace ORAN.SMO.TEIV.REL-Physical-RAN { - abstract class PhysicalAppliance_REL_NF_ -} -namespace ORAN.SMO.TEIV.Physical { - class PhysicalAppliance -} - -PhysicalAppliance "1..n" <-> "1..n" ORANNetworkFunction_ -PhysicalAppliance_REL_NF_ "1" -[hidden]- PhysicalAppliance -PhysicalAppliance_REL_NF_ -[hidden]- ORANNetworkFunction_ -PhysicalAppliance_REL_NF_ . (PhysicalAppliance, ORANNetworkFunction_) -@enduml - -``` - -![UML Class diagram showing the relationship between PhysicalAppliance and ORANNetworkFunction_. The diagram includes three class boxes: ORAN.SMO.TEIV.REL-RAN-Physical (containing PhysicalAppliance_REL_NF_), ORAN.SMO.TEIV.Physical (containing PhysicalAppliance), and ORAN.SMO.TEIV.RAN (containing ORANNetworkFunction_). A dashed inheritance line connects PhysicalAppliance_REL_NF_ to both PhysicalAppliance and ORANNetworkFunction_. A solid association line with arrows at both ends connects PhysicalAppliance and ORANNetworkFunction_, with '1..n' multiplicity labels at each end.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) - -UML Class diagram showing the relationship between PhysicalAppliance and ORANNetworkFunction\_. The diagram includes three class boxes: ORAN.SMO.TEIV.REL-RAN-Physical (containing PhysicalAppliance\_REL\_NF\_), ORAN.SMO.TEIV.Physical (containing PhysicalAppliance), and ORAN.SMO.TEIV.RAN (containing ORANNetworkFunction\_). A dashed inheritance line connects PhysicalAppliance\_REL\_NF\_ to both PhysicalAppliance and ORANNetworkFunction\_. A solid association line with arrows at both ends connects PhysicalAppliance and ORANNetworkFunction\_, with '1..n' multiplicity labels at each end. - -Figure 4.3.6.3.1-1: SMO TE&IV Physical-RAN relationship model - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -skinparam nodesep 120 -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV.Physical { - class PhysicalAppliance -} - -namespace ORAN.SMO.TEIV.RAN { - abstract ORANNetworkFunction_ -} - -PhysicalAppliance <-right-> ORANNetworkFunction_ : \tPhysicalAppliance_REL_NF_ - -@enduml - -``` - -![UML Class Diagram showing the relationship between PhysicalAppliance and ORANNetworkFunction_. The diagram consists of two class boxes. The left box is labeled 'ORAN.SMO.TEIV.Physical' and contains a class named 'PhysicalAppliance'. The right box is labeled 'ORAN.SMO.TEIV.RAN' and contains a class named 'ORANNetworkFunction_'. A directed association line with an arrow pointing from 'ORANNetworkFunction_' to 'PhysicalAppliance' is labeled 'PhysicalAppliance_REL_NF_'.](834fb96b114b8fdc001625e1ae28e8b1_img.jpg) - -UML Class Diagram showing the relationship between PhysicalAppliance and ORANNetworkFunction\_. The diagram consists of two class boxes. The left box is labeled 'ORAN.SMO.TEIV.Physical' and contains a class named 'PhysicalAppliance'. The right box is labeled 'ORAN.SMO.TEIV.RAN' and contains a class named 'ORANNetworkFunction\_'. A directed association line with an arrow pointing from 'ORANNetworkFunction\_' to 'PhysicalAppliance' is labeled 'PhysicalAppliance\_REL\_NF\_'. - -Figure 4.3.6.3.1-2: Simplified SMO TE&IV Physical-RAN relationship model - -``` -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV.RAN { -class ODFunction{ -} -} -namespace ORAN.SMO.TEIV.REL-Physical-RAN { -class PhysicalAppliance_serves_ODFunction{ -} -} -namespace ORAN.SMO.TEIV.Physical { -class PhysicalAppliance{ -} -} - -PhysicalAppliance " \n1..n\nserved-oduFunction" <---> "serving-physicalAppliance\n1..n\nn" ODFunction: > serves -PhysicalAppliance_serves_ODFunction . (PhysicalAppliance, ODFunction) -@enduml -``` - -![UML Class Diagram showing the relationship between PhysicalAppliance and ODUPFunction. The diagram includes three class boxes: ORAN.SMO.TEIV.Physical (containing PhysicalAppliance), ORAN.SMO.TEIV.REL-Physical-RAN (containing PhysicalAppliance_serves_ODUPFunction), and ORAN.SMO.TEIV.RAN (containing ODUPFunction). A red association line connects PhysicalAppliance to ODUPFunction. The association is labeled 'served-oduFunction' with a multiplicity of '1..n' at the PhysicalAppliance end and 'serves' with a multiplicity of '1..n' at the ODUPFunction end. The association class is PhysicalAppliance_serves_ODUPFunction.](f5a5f52bc25d95a7f616290c99e88ae6_img.jpg) - -``` - -classDiagram - class ORAN_SMO_TEIV_Physical { - PhysicalAppliance - } - class ORAN_SMO_TEIV_REL_Physical_RAN { - PhysicalAppliance_serves_ODUPFunction - } - class ORAN_SMO_TEIV_RAN { - ODUPFunction - } - PhysicalAppliance "1..n" served-oduFunction -- "1..n" serves ODUPFunction : PhysicalAppliance_serves_ODUPFunction - -``` - -UML Class Diagram showing the relationship between PhysicalAppliance and ODUPFunction. The diagram includes three class boxes: ORAN.SMO.TEIV.Physical (containing PhysicalAppliance), ORAN.SMO.TEIV.REL-Physical-RAN (containing PhysicalAppliance\_serves\_ODUPFunction), and ORAN.SMO.TEIV.RAN (containing ODUPFunction). A red association line connects PhysicalAppliance to ODUPFunction. The association is labeled 'served-oduFunction' with a multiplicity of '1..n' at the PhysicalAppliance end and 'serves' with a multiplicity of '1..n' at the ODUPFunction end. The association class is PhysicalAppliance\_serves\_ODUPFunction. - -Figure 4.3.6.3.1-3: PhysicalAppliance and ODUPFunction relationship model - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV.RAN { -class OCUUPFunction{ -} -} - -namespace ORAN.SMO.TEIV.REL-Physical-RAN { -class PhysicalAppliance_serves_OCUUPFunction{ -} -} - -namespace ORAN.SMO.TEIV.Physical { -class PhysicalAppliance{ -} -} - -PhysicalAppliance "1..n" served-ocuupFunction -- "1..n" serves ODUPFunction : PhysicalAppliance_serves_OCUUPFunction -@enduml - -``` - -![UML Class Diagram showing the relationship between PhysicalAppliance and OCUUPFunction. The diagram includes three class boxes: ORAN.SMO.TEIV.Physical (containing PhysicalAppliance), ORAN.SMO.TEIV.REL-Physical-RAN (containing PhysicalAppliance_serves_OCUUPFunction), and ORAN.SMO.TEIV.RAN (containing OCUUPFunction). A red association line connects PhysicalAppliance to OCUUPFunction. The association is labeled 'served-ocuupFunction' with a multiplicity of '1..n' at the PhysicalAppliance end and 'serves' with a multiplicity of '1..n' at the OCUUPFunction end. The association class is PhysicalAppliance_serves_OCUUPFunction.](60ffbad6c0fb7371a57fe8f267d2d141_img.jpg) - -``` - -classDiagram - class ORAN_SMO_TEIV_Physical { - PhysicalAppliance - } - class ORAN_SMO_TEIV_REL_Physical_RAN { - PhysicalAppliance_serves_OCUUPFunction - } - class ORAN_SMO_TEIV_RAN { - OCUUPFunction - } - PhysicalAppliance "1..n" served-ocuupFunction --> "1..n" OCUUPFunction : serves - PhysicalAppliance_serves_OCUUPFunction - -``` - -UML Class Diagram showing the relationship between PhysicalAppliance and OCUUPFunction. The diagram includes three class boxes: ORAN.SMO.TEIV.Physical (containing PhysicalAppliance), ORAN.SMO.TEIV.REL-Physical-RAN (containing PhysicalAppliance\_serves\_OCUUPFunction), and ORAN.SMO.TEIV.RAN (containing OCUUPFunction). A red association line connects PhysicalAppliance to OCUUPFunction. The association is labeled 'served-ocuupFunction' with a multiplicity of '1..n' at the PhysicalAppliance end and 'serves' with a multiplicity of '1..n' at the OCUUPFunction end. The association class is PhysicalAppliance\_serves\_OCUUPFunction. - -Figure 4.3.6.3.1-4: PhysicalAppliance and OCUUPFunction relationship model - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV.RAN { -class OCUUPFunction{ -} -} - -namespace ORAN.SMO.TEIV.REL-Physical-RAN { -class PhysicalAppliance_serves_OCUUPFunction{ -} -} - -namespace ORAN.SMO.TEIV.Physical { -class PhysicalAppliance{ -} -} - -PhysicalAppliance "1..n" served-ocuupFunction --> "1..n" OCUUPFunction : serves -PhysicalAppliance_serves_OCUUPFunction . (PhysicalAppliance, OCUUPFunction) -@enduml - -``` - -![UML Class Diagram showing the relationship between PhysicalAppliance and OCUCPFunction. The diagram includes three class boxes: ORAN.SMO.TEIV.Physical (containing PhysicalAppliance), ORAN.SMO.TEIV.REL-Physical-RAN (containing PhysicalAppliance_serves_OCUCPFunction), and ORAN.SMO.TEIV.RAN (containing OCUCPFunction). A red association line connects PhysicalAppliance to OCUCPFunction. The association is labeled 'served-ocucpFunction' with a multiplicity of '1..n' at the PhysicalAppliance end and 'serves' with a multiplicity of '1..n' at the OCUCPFunction end. The PhysicalAppliance_serves_OCUCPFunction class is shown as an association class on the line.](e22af684d8e56d4c61e61bb5ddac1087_img.jpg) - -UML Class Diagram showing the relationship between PhysicalAppliance and OCUCPFunction. The diagram includes three class boxes: ORAN.SMO.TEIV.Physical (containing PhysicalAppliance), ORAN.SMO.TEIV.REL-Physical-RAN (containing PhysicalAppliance\_serves\_OCUCPFunction), and ORAN.SMO.TEIV.RAN (containing OCUCPFunction). A red association line connects PhysicalAppliance to OCUCPFunction. The association is labeled 'served-ocucpFunction' with a multiplicity of '1..n' at the PhysicalAppliance end and 'serves' with a multiplicity of '1..n' at the OCUCPFunction end. The PhysicalAppliance\_serves\_OCUCPFunction class is shown as an association class on the line. - -Figure 4.3.6.3.1-5: PhysicalAppliance and OCUCPFunction relationship model - -``` -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV.RAN { -class NearRTRICFunction{ -} -} - -namespace ORAN.SMO.TEIV.REL-Physical-RAN { -class PhysicalAppliance_serves_NearRTRICFunction{ -} -} - -namespace ORAN.SMO.TEIV.Physical { -class PhysicalAppliance{ -} -} - -PhysicalAppliance " 1..n\nserved-nearRTRICFunction" <--> "serving-physicalAppliance\n1..n\n" NearRTRICFunction: > serves -PhysicalAppliance_serves_NearRTRICFunction . (PhysicalAppliance, NearRTRICFunction) -@enduml -``` - -![UML Class diagram showing the relationship between PhysicalAppliance and NearRTRICFunction. The diagram includes three class boxes: ORAN.SMO.TEIV.Physical (containing PhysicalAppliance), ORAN.SMO.TEIV.REL-Physical-RAN (containing PhysicalAppliance_serves_NearRTRICFunction), and ORAN.SMO.TEIV.RAN (containing NearRTRICFunction). A red association line connects PhysicalAppliance to NearRTRICFunction with a 'serves' label. Multiplicity '1..n' and role 'served-nearRTRICFunction' are at the PhysicalAppliance end, while multiplicity '1..n' and role 'serving-physicalAppliance' are at the NearRTRICFunction end.](41aef1f5efab13d4f38f69e86c726062_img.jpg) - -``` - -classDiagram - class ORAN_SMO_TEIV_Physical { - PhysicalAppliance - } - class ORAN_SMO_TEIV_REL_Physical_RAN { - PhysicalAppliance_serves_NearRTRICFunction - } - class ORAN_SMO_TEIV_RAN { - NearRTRICFunction - } - PhysicalAppliance "1..n served-nearRTRICFunction" --> "1..n serving-physicalAppliance" NearRTRICFunction : serves - -``` - -UML Class diagram showing the relationship between PhysicalAppliance and NearRTRICFunction. The diagram includes three class boxes: ORAN.SMO.TEIV.Physical (containing PhysicalAppliance), ORAN.SMO.TEIV.REL-Physical-RAN (containing PhysicalAppliance\_serves\_NearRTRICFunction), and ORAN.SMO.TEIV.RAN (containing NearRTRICFunction). A red association line connects PhysicalAppliance to NearRTRICFunction with a 'serves' label. Multiplicity '1..n' and role 'served-nearRTRICFunction' are at the PhysicalAppliance end, while multiplicity '1..n' and role 'serving-physicalAppliance' are at the NearRTRICFunction end. - -Figure 4.3.6.3.1-6: PhysicalAppliance and NearRTRICFunction relationship model - -##### 4.3.6.3.2 Inheritance - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none - -namespace ORAN.SMO.TEIV{ - abstract class TopologyRel_ {} -} - -namespace ORAN.SMO.TEIV.REL-Physical-RAN { - abstract class PhysicalAppliance_REL_NF_ {} - - TopologyRel_ <|-- PhysicalAppliance_REL_NF_ - PhysicalAppliance_REL_NF_ <|-- PhysicalAppliance_serves_ODUFunction - PhysicalAppliance_REL_NF_ <|-- PhysicalAppliance_serves_OCUCPFunction - PhysicalAppliance_REL_NF_ <|-- PhysicalAppliance_serves_OCUUPFunction - PhysicalAppliance_REL_NF_ <|-- PhysicalAppliance_serves_NeartRTRICFunction -} -@enduml - -``` - -![UML Class diagram showing inheritance view. ORAN.SMO.TEIV.REL-RAN-Physical box contains PhysicalAppliance_REL_NF, which inherits from ORAN.SMO.TEIV.TopologyRel_. Subclasses include PhysicalAppliance_serves_ODUFunction, PhysicalAppliance_serves_OCUUPFunction, PhysicalAppliance_serves_OCUCPFFunction, and PhysicalAppliance_serves_NearRTRICFunction.](ec3647789b5c38fb686f2a0833324e79_img.jpg) - -``` - -classDiagram - class ORAN.SMO.TEIV.TopologyRel_ - class ORAN.SMO.TEIV.REL-RAN-Physical { - PhysicalAppliance_REL_NF - } - class PhysicalAppliance_serves_ODUFunction - class PhysicalAppliance_serves_OCUUPFunction - class PhysicalAppliance_serves_OCUCPFFunction - class PhysicalAppliance_serves_NearRTRICFunction - - ORAN.SMO.TEIV.REL-RAN-Physical <|-- PhysicalAppliance_REL_NF - PhysicalAppliance_REL_NF <|-- PhysicalAppliance_serves_ODUFunction - PhysicalAppliance_REL_NF <|-- PhysicalAppliance_serves_OCUUPFunction - PhysicalAppliance_REL_NF <|-- PhysicalAppliance_serves_OCUCPFFunction - PhysicalAppliance_REL_NF <|-- PhysicalAppliance_serves_NearRTRICFunction - PhysicalAppliance_REL_NF <|-- ORAN.SMO.TEIV.TopologyRel_ - -``` - -UML Class diagram showing inheritance view. ORAN.SMO.TEIV.REL-RAN-Physical box contains PhysicalAppliance\_REL\_NF, which inherits from ORAN.SMO.TEIV.TopologyRel\_. Subclasses include PhysicalAppliance\_serves\_ODUFunction, PhysicalAppliance\_serves\_OCUUPFunction, PhysicalAppliance\_serves\_OCUCPFFunction, and PhysicalAppliance\_serves\_NearRTRICFunction. - -**Figure 4.3.6.3.2-1: ORAN SMO TE&IV RAN Physical inheritance view** - -#### 4.3.6.4 Class definitions - -##### 4.3.6.4.1 PhysicalAppliance\_serves\_ODUFunction - -###### 4.3.6.4.1.1 Definitions - -This class provides the Topology Relationship between the PhysicalAppliance and the ODUFunction Topology Entities as shown in figure 4.3.6.3.1-3. This class represents the relationship type of the PhysicalAppliance serving the functionality of the ODU function. - -###### 4.3.6.4.1.2 Attributes - -The PhysicalAppliance\_serves\_ODUFunction TRC includes the attributes inherited from *TopologyRel\_* and have the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|---------------------------|---|------------|------------|-------------|--------------| -| served-oduFunction | M | T | F | F | T | -| serving-physicalAppliance | M | T | F | F | T | - -###### 4.3.6.4.1.3 Attribute constraints - -None. - -###### 4.3.6.4.1.4 Notifications - -None. - -###### 4.3.6.4.1.5 State diagram - -None. - -##### 4.3.6.4.2 PhysicalAppliance\_serves\_OCUUPFunction - -###### 4.3.6.4.2.1 Definitions - -This class provides the Topology Relationship between the PhysicalAppliance and the OCUUPFunction Topology Entities as shown in figure 4.3.6.3.1-4. This class represents the relationship type of the PhysicalAppliance serving the functionality of the OCUUP function. - -###### 4.3.6.4.2.2 Attributes - -The PhysicalAppliance\_serves\_OCUUPFunction TRC includes the attributes inherited from *TopologyRel\_* and have the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|---------------------------|---|------------|------------|-------------|--------------| -| served-ocuupFunction | M | T | F | F | T | -| serving-physicalAppliance | M | T | F | F | T | - -###### 4.3.6.4.2.3 Attribute constraints - -None. - -###### 4.3.6.4.2.4 Notifications - -None. - -###### 4.3.6.4.2.5 State diagram - -None. - -##### 4.3.6.4.3 PhysicalAppliance\_serves\_OCUCPFunction - -###### 4.3.6.4.3.1 Definitions - -This class provides the Topology Relationship between the PhysicalAppliance and the OCUCPFunction Topology Entities as shown in figure 4.3.6.3.1-5. This class represents the relationship type of the PhysicalAppliance serving the functionality of the OCUCP function. - -###### 4.3.6.4.3.2 Attributes - -The PhysicalAppliance\_serves\_OCUCPFunction TRC includes the attributes inherited from *TopologyRel\_* and have the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|---------------------------|---|------------|------------|-------------|--------------| -| served-ocucpFunction | M | T | F | F | T | -| serving-physicalAppliance | M | T | F | F | T | - -###### 4.3.6.4.3.3 Attribute constraints - -None. - -###### 4.3.6.4.3.4 Notifications - -None. - -###### 4.3.6.4.3.5 State diagram - -None. - -##### 4.3.6.4.4 PhysicalAppliance\_serves\_NearRTRICFunction - -###### 4.3.6.4.4.1 Definitions - -This class provides the Topology Relationship between the PhysicalAppliance and the NearRTRICFunction Topology Entities as shown in figure 4.3.6.3.1-6. This class represents the relationship type of the PhysicalAppliance serving the functionality of the Near-RTRIC function. - -###### 4.3.6.4.4.2 Attributes - -The PhysicalAppliance\_serves\_NearRTRICFunction TRC includes the attributes inherited from *TopologyRel\_* and have the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|---------------------------|---|------------|------------|-------------|--------------| -| served-nearRTRICFunction | M | T | F | F | T | -| serving-physicalAppliance | M | T | F | F | T | - -###### 4.3.6.4.4.3 Attribute constraints - -None - -###### 4.3.6.4.4.4 Notifications - -None. - -###### 4.3.6.4.4.5 State diagram - -None. - -##### 4.3.6.4.5 *PhysicalAppliance\_REL\_NF\_* - -###### 4.3.6.4.5.1 Definitions - -This abstract class is provided for sub-classing only and is used to generalize the relationship classes in this namespace. - -###### 4.3.6.4.5.2 Attributes - -None. - -###### 4.3.6.4.5.3 Attribute constraints - -None. - -###### 4.3.6.4.5.4 Notifications - -None. - -###### 4.3.6.4.5.5 State diagram - -None. - -#### 4.3.6.4 Attribute definitions - -##### 4.3.6.4.1 Attribute properties - -The following table defines the properties of attributes specified in the present document. - -**Table 4.3.6.4.1-1: Attribute properties** - -| Attribute Name | Documentation and Allowed Values | Properties | Source Domain | -|---------------------------|----------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|---------------| -| serving-physicalAppliance | This represents the Topology Entity Id(s) of the NF PhysicalAppliance instance(s) serving O-RAN Network Function(s). | type: URN
multiplicity: 1..n
isOrdered: False
isUnique: True | TE&IV | - -| Attribute Name | Documentation and Allowed Values | Properties | Source Domain | -|--------------------------|-------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|---------------| -| | | defaultValue: None | | -| served-oduFunction | This represents the Topology Entity Id(s) of the ODU function instance(s) served by the PhysicalAppliance. | type: URN
multiplicity: 1..n
isOrdered: False
isUnique: True
defaultValue: None | TE&IV | -| served-ocuupFunction | This represents the Topology Entity Id(s) of the OCUUP function instance(s) served by the PhysicalAppliance. | type: URN
multiplicity: 1..n
isOrdered: False
isUnique: True
defaultValue: None | TE&IV | -| served-ocucpFunction | This represents the Topology Entity Id(s) of the OCUCP function instance(s) served by the PhysicalAppliance. | type: URN
multiplicity: 1..n
isOrdered: False
isUnique: True
defaultValue: None | TE&IV | -| served-nearRTRICFunction | This represents the Topology Entity Id(s) of the Near-RTRIC function instance(s) served by the PhysicalAppliance. | type: URN
multiplicity: 1..n
isOrdered: False
isUnique: True
defaultValue: None | TE&IV | - -## 4.4 TE&IV Service Operations - -### 4.4.1 Introduction - -This clause provides the stage 2 definitions of TE&IV Service Operations for exposing Topology Entities, Topology Relationships and their attributes. - -The information model in Figure 4.4.1-1 depicts the model view of the entities used in the TE&IV Service Operations initiated by TE&IV Service Consumers to retrieve the Domains in Topology, Topology Entities and Topology Relationships. - -![UML Class Diagram showing Domain, TopologyEntity, and TopologyRelationship classes and their relationships.](396197257cf9437b526bb6585b6a9c8a_img.jpg) - -``` - -classDiagram - class Domain { - domainName: string - } - class TopologyEntity { - <> - TopologyEntity - } - class TopologyRelationship { - <> - TopologyRelationship - } - Domain "1" -- "*" TopologyEntity : IsComposedOf - Domain "1" -- "*" TopologyRelationship : IsComposedOf - -``` - -The diagram illustrates the relationship between three classes: Domain, TopologyEntity, and TopologyRelationship. The Domain class has an attribute 'domainName' of type 'string'. It has two associations: one with the TopologyEntity class and another with the TopologyRelationship class. Both associations are labeled 'IsComposedOf'. The multiplicity at the Domain end for both associations is '1', and the multiplicity at the TopologyEntity and TopologyRelationship ends is '\*'. The TopologyEntity and TopologyRelationship classes are shown with their stereotypes: «TopologyEntityClass» and «TopologyRelationshipClass» respectively. - -UML Class Diagram showing Domain, TopologyEntity, and TopologyRelationship classes and their relationships. - -**Figure 4.4.1-1: ORAN SMO TE&IV Topology Domain, Topology Entity and Topology Relationship Model View** - -The Figure 4.4.1-2 shows the allowed inter-domain relationships. It depicts subclasses of the Domain concept comprising two distinct categories: Relationship and Entity. An Entity Domain may contain both Entities and Relationships, however both aSide and bSide of such relationships shall exist in that domain. A Relationship Domain encapsulates Relationships to Entities in one or more Entity Domains. The Relationship Domain should not have any Entities. - -![UML Class Diagram showing a dependency from RelationshipDomain to EntityDomain. RelationshipDomain has a multiplicity of 0..* and EntityDomain has a multiplicity of 1..*. The dependency is labeled 'dependsOn'.](40ebe9179df298f1b6d76822f28d90aa_img.jpg) - -``` - -classDiagram - class RelationshipDomain { - <> - } - class EntityDomain { - <> - } - RelationshipDomain "0..*" --> "1..*" EntityDomain : dependsOn - -``` - -UML Class Diagram showing a dependency from RelationshipDomain to EntityDomain. RelationshipDomain has a multiplicity of 0..\* and EntityDomain has a multiplicity of 1..\*. The dependency is labeled 'dependsOn'. - -Figure 4.4.1-2: ORAN SMO TE&IV Domain Dependency Model View - -### 4.4.2 Operations and Notification - -#### 4.4.2.1 getAllDomains operation - -##### 4.4.2.1.1 Description - -This operation is invoked by the TE&IV Service Consumer to retrieve all the available Topology Domains. - -##### 4.4.2.1.2 Input parameters - -| Parameter Name | S | Description | -|----------------|---|------------------------------------------------------------------------------------------------------------------------------| -| Accept | M | This parameter specifies the response media types that are acceptable. | -| offsetParam | O | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | O | The query parameter provides to limit the number of entries returned for a request for pagination. | - -##### 4.4.2.1.3 Output parameters - -| Parameter name | S | Description | -|----------------|---|------------------------------------------------------------------------------------| -| Domains | M | A list of Topology Domains and the links to its EntityTypes and RelationshipTypes. | - -##### 4.4.2.1.4 Results - -In case of success, all the available Topology Domains are returned. In case of failure, an appropriate error response may be provided. - -#### 4.4.2.2 getTopologyEntityTypes operation - -##### 4.4.2.2.1 Description - -This operation is invoked by the TE&IV Service Consumer to get all the available Topology Entity types within a domain. - -##### 4.4.2.2.2 Input parameters - -| Parameter Name | S | Description | -|----------------|---|------------------------------------------------------------------------------------------------------------------------------| -| Accept | M | This parameter specifies the response media types that are acceptable. | -| domainName | M | This path parameter specifies the name of the Topology Domain. | -| offsetParam | O | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | O | The query parameter provides to limit the number of entries returned for a request for pagination. | - -##### 4.4.2.2.3 Output parameters - -| Parameter name | S | Description | -|----------------|---|----------------------------------------------------------------------| -| EntityTypes | M | A list of links to the Topology Entities within the Topology Domain. | - -##### 4.4.2.2.4 Results - -In case of success, all the available Topology Entity types in domain name are returned. In case of failure, an appropriate error response may be provided. - -#### 4.4.2.3 getTopologyByEntityTypeName operation - -##### 4.4.2.3.1 Description - -This operation is invoked by the TE&IV Service Consumer to get all Topology Entity instances of a specific Topology Entity type. - -##### 4.4.2.3.2 Input parameters - -| Parameter Name | S | Description | -|----------------|---|--------------------------------------------------------------------------------------------------------------------------------| -| Accept | M | This parameter specifies the response media types that are acceptable. | -| domainName | M | This path parameter specifies the name of the Topology Domain. | -| entityTypeName | M | This path parameter specifies the name of a Topology Entity in a Topology Domain. | -| targetFilter | O | This query parameter specifies the entity type and attributes to be returned in the REST response. | -| scopeFilter | O | This query parameter specifies the attributes to match on for specific Topology Entities for which the data is to be produced. | -| offsetParam | O | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | O | The query parameter provides to limit the number of entries returned for a request for pagination. | - -##### 4.4.2.3.3 Output parameters - -| Parameter name | S | Description | -|----------------|---|-------------------------------------------------------------------------------| -| Entities | M | A list of links to the data model for schema definition of Topology Entities. | - -##### 4.4.2.3.4 Results - -In case of success, all the available instances of a specific topology entity type are returned. In case of failure, an appropriate error response may be provided. - -#### 4.4.2.4 getTopologyById operation - -##### 4.4.2.4.1 Description - -This operation is invoked by the TE&IV Service Consumer to get a specific Topology Entity instance of a Topology Entity type. - -##### 4.4.2.4.2 Input parameters - -| Parameter Name | S | Description | -|----------------|---|-----------------------------------------------------------------------------------| -| Accept | M | This parameter specifies the response media types that are acceptable. | -| domainName | M | This path parameter specifies the name of the Topology Domain. | -| entityTypeName | M | This path parameter specifies the name of a Topology Entity in a Topology Domain. | -| entityId | M | The path parameter specifies the Identifier of a Topology Entity instance. | - -##### 4.4.2.4.3 Output parameters - -| Parameter name | S | Description | -|----------------|---|---------------------------------------------------------------------------------------------| -| EntityInstance | M | Encapsulated object reference to the data model for schema definition of Topology Entities. | - -##### 4.4.2.4.4 Results - -In case of success, an object referencing to the data model schema definition of Topology Entity instance of a specific Topology Entity type name is returned. In case of failure, an appropriate error response may be provided. - -#### 4.4.2.5 getAllRelationshipsForEntityId operation - -##### 4.4.2.5.1 Description - -This operation is invoked by the TE&IV Service Consumer to get all relationships for a specific Topology Entity instance of a Topology Entity type. - -##### 4.4.2.5.2 Input parameters - -| Parameter Name | S | Description | -|----------------|---|-------------------------------------------------------------------------------------------------------------------------------------------| -| Accept | M | This parameter specifies the response media types that are acceptable. | -| domainName | M | This path parameter specifies the name of the Topology Domain. | -| entityTypeName | M | This path parameter specifies the name of a Topology Entity in a Topology Domain. | -| entityId | M | The path parameter specifies the Identifier of a Topology Entity instance. | -| targetFilter | O | This query parameter specifies the entity type and relationship to be returned in the REST response. | -| scopeFilter | O | This query parameter specifies the attributes to match on for specific Topology Entity relationship for which the data is to be produced. | -| offsetParam | O | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | O | The query parameter provides to limit the number of entries returned for a request for pagination. | - -##### 4.4.2.5.3 Output parameters - -| Parameter name | S | Description | -|----------------|---|--------------------------------------------------------------------------------------------------| -| Relationships | M | Encapsulated object reference to the data model for schema definition of Topology Relationships. | - -##### 4.4.2.5.4 Results - -In case of success, an object referencing to the data model schema definition of Topology Relationships of a specific Topology Entity type name is returned. In case of failure, an appropriate error response may be provided. - -#### 4.4.2.6 getTopologyRelationshipTypes operation - -##### 4.4.2.6.1 Description - -This operation is invoked by the TE&IV Service Consumer to retrieve all the available Topology Relationship types. - -##### 4.4.2.6.2 Input parameters - -| Parameter Name | S | Description | -|----------------|---|------------------------------------------------------------------------------------------------------------------------------| -| Accept | M | This parameter specifies the response media types that are acceptable. | -| domainName | M | This path parameter specifies the name of the Topology Domain. | -| offsetParam | O | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | O | The query parameter provides to limit the number of entries returned for a request for pagination. | - -##### 4.4.2.6.3 Output parameters - -| Parameter name | S | Description | -|-------------------|---|------------------------------------------------| -| RelationshipTypes | M | A list of links to the Topology Relationships. | - -##### 4.4.2.6.4 Results - -In case of success, all the available Topology Relationship types are returned. In case of failure, an appropriate error response may be provided. - -#### 4.4.2.7 getRelationshipsByType operation - -##### 4.4.2.7.1 Description - -This operation is invoked by the TE&IV Service Consumer to get all the available Topology Relationships of a specific relationship type name. - -##### 4.4.2.7.2 Input parameters - -| Parameter Name | S | Description | -|----------------------|---|--------------------------------------------------------------------------------------------------------------------------------| -| Accept | M | This parameter specifies the response media types that are acceptable. | -| domainName | M | This path parameter specifies the name of the Topology Domain. | -| relationshipTypeName | M | This path parameter specifies the name of a Topology Relationship in a Topology Domain. | -| targetFilter | O | This query parameter specifies the entity type and attributes to be returned in the REST response. | -| scopeFilter | O | This query parameter specifies the attributes to match on for specific Topology Entities for which the data is to be produced. | -| offsetParam | O | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | O | The query parameter provides to limit the number of entries returned for a request for pagination. | - -##### 4.4.2.7.3 Output parameters - -| Parameter name | S | Description | -|----------------|---|--------------------------------------------------------------------------------------------------| -| Relationships | M | Encapsulated object reference to the data model for schema definition of Topology Relationships. | - -##### 4.4.2.7.4 Results - -In case of success, all the available Topology Relationships of a specific relationship type name are returned. In case of failure, an appropriate error response may be provided. - -#### 4.4.2.8 getRelationshipById operation - -##### 4.4.2.8.1 Description - -This operation is invoked by the TE&IV Service Consumer to get a specific Topology Relationship instance of a Topology Relationship type. - -##### 4.4.2.8.2 Input parameters - -| Parameter Name | S | Description | -|----------------------|---|-----------------------------------------------------------------------------------------| -| Accept | M | This parameter specifies the response media types that are acceptable. | -| domainName | M | This path parameter specifies the name of the Topology Domain. | -| relationshipTypeName | M | This path parameter specifies the name of a Topology Relationship in a Topology Domain. | -| relationshipId | M | This path parameter specifies the identifier of a Topology Relationship instance. | - -##### 4.4.2.8.3 Output parameters - -| Parameter name | S | Description | -|----------------|---|-------------------------------------------------------------------------------------------------| -| Relationship | M | Encapsulated object reference to the data model for schema definition of Topology Relationship. | - -##### 4.4.2.8.4 Results - -In case of success, a specific Topology Relationship instance of a Topology Relationship type is returned. In case of failure, an appropriate error response may be provided. - -#### 4.4.2.9 getSchemas operation - -##### 4.4.2.9.1 Description - -This operation is invoked by the TE&IV Service Consumer to retrieve all the available Topology Model Schemas. - -##### 4.4.2.9.2 Input parameters - -| Parameter Name | S | Description | -|----------------|---|------------------------------------------------------------------------------------------------------------------------------| -| Accept | M | This parameter specifies the response media types that are acceptable. | -| offsetParam | O | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | O | The query parameter provides to limit the number of entries returned for a request for pagination. | -| domain | O | This query parameter allows you to specify the desired domain | - -##### 4.4.2.9.3 Output parameters - -| Parameter name | S | Description | -|----------------|---|----------------------------------| -| Schemas | M | A list of Topology Model Schemas | - -##### 4.4.2.9.4 Results - -In case of success, all the available Topology Model Schemas are returned. In case of failure, an appropriate error response may be provided. - -#### 4.4.2.10 getSchemaByName operation - -##### 4.4.2.10.1 Description - -This operation is invoked by the TE&IV Service Consumer to get the schema by name. - -##### 4.4.2.10.2 Input parameters - -| Parameter Name | S | Description | -|----------------|---|------------------------------------------------------------------------------------------------------------------------------| -| Accept | M | This parameter specifies the response media types that are acceptable. | -| schemaName | M | This path parameter specifies the name of the Topology Model Schema. | -| offsetParam | O | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | O | The query parameter provides to limit the number of entries returned for a request for pagination. | - -##### 4.4.2.10.3 Output parameters - -| Parameter name | S | Description | -|----------------|---|--------------------------------------| -| string | M | Content of the Topology Model Schema | - -##### 4.4.2.10.4 Results - -In case of success, schema content is returned. In case of failure, an appropriate error response may be provided. - -## 4.5 TE&IV User Defined Data - -### 4.5.1 Introduction - -TE&IV user defined data is used for enriching Topology Entities and Topology Relationships. Such data can be added to existing Topology Entities and Relationships which enables flexibility for TE&IV Service Consumers in its usage of the service operations defined in clause 4.4. The user defined data are declared in separate schemas and are added through a REST API which shall be defined in the TE&IV API [17]. The following clauses provide the definitions for the types of TE&IV user defined data. - -### 4.5.2 Classifiers - -Classifiers permit the association of a well defined user specified string with a Topology Entity and/or Topology Relationship. Classifiers are declared in a schema added through a REST API [17]. When the schema is successfully created and validated, the user can assign the classifiers to the selected entities and/or relationships. - -#### 4.5.2.1 Definitions - -This class provides the representation of Classifiers. - -#### 4.5.2.2 Attributes - -Classifiers have the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|-------------------------|---|------------|------------|-------------|--------------| -| operation | M | T | F | F | T | -| classifierNames | M | T | F | F | T | -| topologyEntityIds | M | T | F | F | T | -| topologyRelationshipIds | M | T | F | F | T | - -#### 4.5.2.3 Attribute constraints - -None. - -#### 4.5.2.4 Notifications - -There is no notification defined. - -#### 4.5.2.5 State diagram - -None. - -### 4.5.3 Decorators - -Decorators are key-value pairs that can be associated with Topology Entities and/or Topology Relationships. The type of the value is defined by the user in the schema which declares the decorator. Decorators are declared in a schema added through a REST API [17]. When the schema is successfully created and validated, the user can assign the decorator to the selected entities and/or relationships. - -#### 4.5.3.1 Definitions - -This class provides the representation of Decorators. - -#### 4.5.3.2 Attributes - -Decorators have the following attributes: - -| Attribute Name | S | isReadable | isWritable | isInvariant | isNotifyable | -|-------------------------|---|------------|------------|-------------|--------------| -| operation | M | T | F | F | T | -| decoratorTags | M | T | F | F | T | -| topologyEntityIds | M | T | F | F | T | -| topologyRelationshipIds | M | T | F | F | T | - -#### 4.5.2.3 Attribute constraints - -None. - -#### 4.5.2.4 Notifications - -There is no notification defined. - -#### 4.5.2.5 State diagram - -None. - -### 4.5.4 Attribute properties - -**Table 4.5.4.-1: Attribute properties** - -| Attribute Name | Documentation and Allowed Values | Properties | Source Domain | -|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|---------------| -| operation |

Specifies whether a classifier or decorator is being added or removed.

Allowed values: merge, delete

Merge: Defined classifiers or decorators can be assigned to specified Topology Entities and Topology Relationships in a single request.

Delete: Defined classifiers or decorators can be removed from specified Topology Entities and Topology Relationships in a single request.

| type: ENUM
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None | | -| classifierNames | List of tags to be assigned to Topology Entities and/or Topology Relationships | type: String
multiplicity: 1..N
isOrdered: N/A
isUnique: N/A
defaultValue: None | | -| decoratorTags |

Key-value pairs to be assigned to Topology Entities and/or Topology Relationships.

The content of this attribute is a list of attributeName-attributeValue pairs.

Allowed values: Value must be a simple data type (string, integer, or Boolean)

| type: AttributeValuePair
multiplicity: 1..N
isOrdered: N/A
isUnique: N/A
defaultValue: None | | -| topologyEntityIds | List of topologyEntityId.
topologyEntityId is defined in clause 4.3.4.5.1. | type: URN
multiplicity: 1..N
isOrdered: N/A
isUnique: N/A
defaultValue: None | | - -### 4.5.5 Service Operations for User Defined Data - -This clause provides the stage 2 definitions of TE&IV Service Operations for exposing Topology Entities, Topology Relationships using User Defined Data. - -#### 4.5.5.1 updateClassifier operation - -##### 4.5.5.1.1 Description - -This operation is invoked by the TE&IV Service Consumer to merge or delete the classifiers for the available Topology Entities and Relationships. - -##### 4.5.5.1.2 Input parameters - -| Parameter Name | S | Description | -|----------------|---|------------------------------------------------------------------------| -| Accept | M | This parameter specifies the response media types that are acceptable. | -| Content-Type | M | This parameter specifies the media types of the resource. | - -##### 4.5.5.1.3 Output parameters - -None - -##### 4.5.4.1.4 Results - -In case of success, the classifier is assigned to or removed from all indicated entities and relationships. In case of failure, an appropriate error response may be provided. - -#### 4.5.5.2 updateDecorator operation - -##### 4.5.5.2.1 Description - -This operation is invoked by the TE&IV Service Consumer to merge or delete the decorators for the available Topology Entities and Relationships. - -##### 4.5.5.2.2 Input parameters - -| Parameter Name | S | Description | -|----------------|---|------------------------------------------------------------------------| -| Accept | M | This parameter specifies the response media types that are acceptable. | -| Content-Type | M | This parameter specifies the media types of the resource. | - -##### 4.5.5.2.3 Output parameters - -None. - -##### 4.5.5.2.4 Results - -In case of success, all indicated entities and relationships are updated with the decorator. In case of failure, an appropriate error response may be provided. - -#### 4.5.5.3 getUserDefinedSchema operation - -##### 4.5.5.3.1 Description - -This operation is invoked by the TE&IV Service Consumer to discover the available user defined schema. - -##### 4.5.5.3.2 Input parameters - -| Parameter Name | S | Description | -|----------------|---|------------------------------------------------------------------------------------------------------------------------------| -| Accept | M | This parameter specifies the response media types that are acceptable. | -| offsetParam | O | This query parameter allows you to omit a specified number of entries before the beginning of the result set for pagination. | -| limitParam | O | The query parameter provides to limit the number of entries returned for a request for pagination. | - -##### 4.5.5.3.3 Output parameters - -| Parameter Name | S | Description | -|--------------------|---|---------------------------------| -| UserDefinedSchemas | M | A list of user defined schemas. | - -##### 4.5.5.3.4 Results - -In case of success, all the available user defined schemas are returned. In case of failure, an appropriate error response may be provided. - -#### 4.5.5.4 createUserDefinedSchema operation - -##### 4.5.5.4.1 Description - -This operation is invoked by the TE&IV Service Consumer to create new user defined schemas. - -##### 4.5.5.4.2 Input parameters - -| Parameter Name | S | Description | -|----------------|---|------------------------------------------------------------------------| -| Accept | M | This parameter specifies the response media types that are acceptable. | -| Content-Type | M | This parameter specifies the media types of the resource. | -| MultipartFile | M | Multipart file containing the user defined schema to be created. | - -##### 4.5.5.4.3 Output parameters - -| Parameter Name | S | Description | -|-------------------|---|-----------------------------------------------| -| UserDefinedSchema | M | User defined schema with link to its content. | - -##### 4.5.5.4.4 Results - -In case of success, the new user defined schema is created. In case of failure, an appropriate error response may be provided. - -#### 4.5.5.5 deleteUserDefinedSchema operation - -##### 4.5.5.5.1 Description - -This operation is invoked by the TE&IV Service Consumer to delete a user defined schema. - -##### 4.5.5.5.2 Input parameters - -| Parameter Name | S | Description | -|----------------|---|------------------------------------------------------------------------| -| Accept | M | This parameter specifies the response media types that are acceptable. | -| schemaName | M | This path parameter specifies the name of the user defined schema. | - -##### 4.5.5.5.3 Output parameters - -None. - -##### 4.5.5.5.4 Results - -In case of success, the specified user defined schema is deleted. In case of failure, an appropriate error response may be provided. - -#### 4.5.5.6 getUserDefinedSchemaByName operation - -##### 4.5.5.6.1 Description - -This operation is invoked by the TE&IV Service Consumer to get a specific user defined schema by name. - -##### 4.5.5.6.2 Input parameters - -| Parameter Name | S | Description | -|----------------|---|------------------------------------------------------------------------| -| Accept | M | This parameter specifies the response media types that are acceptable. | -| Content-Type | M | This parameter specifies the media types of the resource. | -| schemaName | M | This path parameter specifies the name of the user defined schema. | - -##### 4.5.5.6.3 Output parameters - -| Parameter Name | S | Description | -|----------------|---|------------------------------| -| string | M | User defined schema content. | - -##### 4.5.5.6.4 Results - -In case of success, the content of the user defined schema is returned. In case of failure, an appropriate error response may be provided. - -# Annex A (Informative): Model views - -## A.1 Model View: O-RAN TE&IV Network Function Deployment View (informative) - -The TE&IV Network Function Deployment model view provides the basic constructs of the Topology Entities and Topology Relationship to represent the topology information related to the physical and cloud deployment aspects of the O-RAN Network Functions. The physical network function deployment view is shown in Figure A.1-1 and the cloud network function deployment view is shown in Figure A.1-2. - -``` -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none -package "TE&IV Physical Network Function Deployment View" { - -class PhysicalAppliance - -abstract class ORANNetworkFunction_ -class Site - -note "has location info." as N1 -note "Represents a Physical hardware which is used to realise Network Functions" as P1 -} - -PhysicalAppliance .r. P1 - -Site .r. N1 - -ORANNetworkFunction_ "*" <-- "0..n" PhysicalAppliance : serves -PhysicalAppliance "1..*" --> "0..1" Site : installedAt - -@enduml -``` - -![UML Class Diagram titled 'TE&IV Physical Network Function Deployment View'. It shows three classes: ORANNetworkFunction_, PhysicalAppliance, and Site. ORANNetworkFunction_ is at the top, PhysicalAppliance is in the middle, and Site is at the bottom. A solid red arrow points from PhysicalAppliance (multiplicity 0..n) to ORANNetworkFunction_ (multiplicity *), labeled 'serves'. A solid red arrow points from PhysicalAppliance (multiplicity 1..*) to Site (multiplicity 0..1), labeled 'installedAt'. A dashed yellow callout box points to PhysicalAppliance with the text 'Represents a Physical hardware which is used to realise Network Functions'. Another dashed yellow callout box points to Site with the text 'has location info.'.](3ce04f1c7128814978c6b34d654a25cc_img.jpg) - -UML Class Diagram titled 'TE&IV Physical Network Function Deployment View'. It shows three classes: ORANNetworkFunction\_, PhysicalAppliance, and Site. ORANNetworkFunction\_ is at the top, PhysicalAppliance is in the middle, and Site is at the bottom. A solid red arrow points from PhysicalAppliance (multiplicity 0..n) to ORANNetworkFunction\_ (multiplicity \*), labeled 'serves'. A solid red arrow points from PhysicalAppliance (multiplicity 1..\*) to Site (multiplicity 0..1), labeled 'installedAt'. A dashed yellow callout box points to PhysicalAppliance with the text 'Represents a Physical hardware which is used to realise Network Functions'. Another dashed yellow callout box points to Site with the text 'has location info.'. - -Figure A.1-1: ORAN TE&IV Physical NF Deployment View - -``` -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide empty members -set namespaceSeparator none -package "TE&IV Cloud Network Function Deployment View" { - -class CloudifiedNF -class NFDeployment - -abstract class ORANNetworkFunction_ - -class OCloudNamespace -class NodeCluster -class OCloudSite - -note "has location info." as N1 -} - -ORANNetworkFunction_ "1..n" <-- "0..n" NFDeployment : serves - -CloudifiedNF "1" --> "1..*" NFDeployment : comprizes -NFDeployment "1..*" --> "1..*" OCloudNamespace : deployedOn -OCloudNamespace "1..*" --> "1" NodeCluster : deployedOn -NodeCluster "1..*" --> "1..*" OCloudSite : locatedAt - -OCloudSite .r. N1 -@enduml -``` - -![UML Class Diagram: TE&IV Cloud Network Function Deployment View](fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg) - -**TE&IV Cloud Network Function Deployment View** - -``` -classDiagram - class CloudifiedNF - class ORANNetworkFunction_ - class NFDeployment - class OCloudNamespace - class NodeCluster - class OCloudSite - - CloudifiedNF "1" --> "1..*" NFDeployment : comprizes - ORANNetworkFunction_ "1..n" --> "0..n" NFDeployment : serves - NFDeployment "1..*" --> "1..*" OCloudNamespace : deployedOn - OCloudNamespace "1..*" --> "1" NodeCluster : deployedOn - NodeCluster "1..*" --> "1..*" OCloudSite : locatedAt - OCloudSite -.-> Note : has location info. -``` - -The diagram illustrates the TE&IV Cloud Network Function Deployment View. It shows the following entities and their relationships: - -- CloudifiedNF** (1) **comprizes** (1..\*) **NFDeployment** -- ORANNetworkFunction\_** (1..n) **serves** (0..n) **NFDeployment** -- NFDeployment** (1..\*) **deployedOn** (1..\*) **OCloudNamespace** -- OCloudNamespace** (1..\*) **deployedOn** (1) **NodeCluster** -- NodeCluster** (1..\*) **locatedAt** (1..\*) **OCloudSite** -- OCloudSite** has a note: **has location info.** - -UML Class Diagram: TE&IV Cloud Network Function Deployment View - -Figure A.1-2: ORAN TE&IV Cloud NF Deployment View - -# Annex (informative): Change history - -| Date | Revision | Description | -|------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 08/06/2023 | 00.00.01 | Initial proposed skeleton for the TE&IV Common Topology Information Models and Interface Specification | -| 14/06/2023 | 00.00.02 | Updated skeleton for the TE&IV Common Information Models and Interface Specification as per comments | -| 09/11/2023 | 00.00.03 | Updated title for this specification and removed Stage-2 wording | -| 11/01/2024 | 00.00.04 | Updated the title, numbering, introduced structure for namespaces | -| 06/03/2024 | 00.00.05 | Merged the TE&IV Stage-2 IM CRs for March'24 train
SYM.AO-2023.10.05-WG10-CR-001-TEIV NF deployment model-v07, ERI-2024.02.08-WG10-CR-0064-Adding introduction scope in TEIV IM specification-v04, ERI-2023.12.21-WG10-CR-0056-Update to TE&IV-IM specification-v01 | -| 13/03/2024 | 00.00.06 | Editorial changes to update reference names, version as per O-RAN guidelines. Removed redundant versioning text in foreward and updated the O-RAN release versioning format in scope | -| 13/03/2024 | 01.00.00 | Editorial Comments, First Publication for the March 2024 Train | -| 11/07/2024 | 02.00.00 | Implemented the following CRs for the July'24 train: ERI.AO-2024.03.11-WG10-CR-0067-RAN-Logical-To-Cloud-Relationship-Namespace-v06, ERI-2024.04.18-WG10-CR-0071-Update to O-RAN TE&IV Network Function Deployment -v06, ERI-2024.06.10-WG10-CR-0075-Addition of UML notation and model element -v02, ERI-2024.06.10-WG10-CR-0084-adding attributes to RAN logical namespace-05, Editorial corrections. | -| 15/07/2024 | 02.00.00 | Addressed WG10 review comments. Used Atlassian versioning to track revisions on the captured comments. | -| 06/11/2024 | 03.00 | Implemented the following CRs for the November 2024 train: ERI-2024.09.18-WG10-CR-0113-TE&IV_IS_Definitions_of_ServiceOperations-v02, ERI-2024.09.18-WG10-CR-0114-TE&IV_IS_Definitions_of_ServiceOperations_for_Relationships-v01, ERI-2024.10.04-WG10-CR-0124-REL-RAN-Cloud Namespace | -| 07/02/2025 | 04.00 | Implemented the following CRs for the March 2025 train: ERI.AO-2025.01.15-WG10-CR-0144-TE&IV-AbstractClasses v02, ERI.AO-2025.01.28-WG10-CR-0145-RAN Abstractions-v01, ERI.AO-2025.01.27-WG10-CR-0146-REL-Cloud-RAN Abstractions-v01, ERI.AO-2025.01.27-WG10-CR-0147-TE&IV-Modelling-Guidelines v01, KDDI.AO-2025.02.19-WG10-CR-0003-TEIV-Physical v03, KDDI.AO-2025.02.19-WG10-CR-0004-TE&IV-Physical_NF_REL v02, ERI-2025.02.17-WG10-CR-0150- stage 2 to add query parameter to topology entity relationship resource - v01 | -| 01/07/2025 | 05.00 | Implemented the following CRs for the July 2025 train: ERI.AO-2025.04.02-WG10-CR-0168- ORU-as-a-type-of-PhysicalAppliance-v02, ERI-2025.03.24-WG10-CR-0161- Classifiers-and-Decorators-v02, ERI-2025.05.20-WG10-CR-0174-Classifier-and-Decorator-Attributes-and-Service-Operations-v03, ERI-2025.06.23-WG10-CR-0184-Update OAM Arch title in TE&IV CIMI-v01, ERI-2025.06.25-WG10-CR-0187- Stage 2 Schema Operations-v02, Updated the specification for formatting corrections and editorial updates based on ODR and TS template v04 | -| 19/11/2025 | 06.00 | Implemented the following CRs for the November 2025 train: ERI-2025.09.09-WG10-CR-0197-Resource-in-TEC-v01, ERI-2025.10.09-WG10-CR-0205-Fixing-references-on-TE&IV-CIMI-v01, ERI-2025.10.13-WG10-CR-0204-Cloud Namespace Attributes-v03 | \ No newline at end of file diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg deleted file mode 100644 index f3709e1cd8d4ec0dacab5c558909ed6116186404..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c4cad931ed9b0c3866c1aacc4e356f8daf811fc5d2e78f12ea01f9f5089bfb69 -size 23632 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/04cfca33e3fc26513abe649d7474f733_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/04cfca33e3fc26513abe649d7474f733_img.jpg deleted file mode 100644 index 72c0df161721d165eaecab61babcd9c1c5de51bd..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/04cfca33e3fc26513abe649d7474f733_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9b8bf6079bad32004e69ef1fd30aeb345b2d0384e67b68e960374d369cf3585b -size 25219 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/1099a4137017f2d9721d546bbb1e9362_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/185df94f4a6a5245323255e844a30ec0_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/1baaba7a6e54e77197475726c871067d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/22af211207188ebc64d7b60ca052b367_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/22f30783614672d201275c116a5d8516_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/253600420ae7bd7d0119563b895cbf8a_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/26d664119ad25250780f554633444e54_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/26d664119ad25250780f554633444e54_img.jpg deleted file mode 100644 index fae5562dc6e15b544e39d641cbb85fc1db8a5535..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/26d664119ad25250780f554633444e54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e943dd0594580203d85de462e09c0ad218ce23a28d3731a6eb7bd057e27375e8 -size 30792 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/28d75f39a24203712ee907b32cf0bbe5_img.jpg deleted file mode 100644 index cb990487aed002f2a8f5464de52d9f28cead0df0..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/28d75f39a24203712ee907b32cf0bbe5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3730943c7a88424ceea4383df1feb8dd3283d79cf81825bb2c07c70162225d06 -size 54799 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/29f3760c0230631eb03f67030ef65ed0_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg deleted file mode 100644 index 2e7af45074965b63f3cc7111c0c29c12c635985c..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:01ef3a34c825c71172288b368618dbf57da0c10d2d27ea8c77dbcae074ad380c -size 65109 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/2b3a967f6ce4f23649be995a353e39f8_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/2b3a967f6ce4f23649be995a353e39f8_img.jpg deleted file mode 100644 index 5500139cb7a8754c6d8a69328a589431a55dd193..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/2b3a967f6ce4f23649be995a353e39f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:472887ba7cf7bcec7638be69f486628a02e51bceee1fdab681800052e590fa71 -size 51124 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg deleted file mode 100644 index 77d85f90417f07c0614e8d4d5200cb50c5e2cfc3..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:23b4870f8605fc2e095a548c193a7773b78c50207a27067b9f80142c00df5aa8 -size 4537 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/367926125450c2bc3f4bdca9d59a62ba_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/367926125450c2bc3f4bdca9d59a62ba_img.jpg deleted file mode 100644 index 2d3a0527f20221de21f69dc53feab645decbef89..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/367926125450c2bc3f4bdca9d59a62ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a5b291142e2f608f8eff28c3dec2dbf6730a4e925fb08b6a6f6f5ee63f603bda -size 12341 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/38866d3f212726e1c8e92001ca0dd6f8_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/396197257cf9437b526bb6585b6a9c8a_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/396197257cf9437b526bb6585b6a9c8a_img.jpg deleted file mode 100644 index 619f83df9922d210c1191bf29eb84ecca0493719..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/396197257cf9437b526bb6585b6a9c8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:56f2208ab78836eadc46ef387761d5d770306c9d87a98a83338a0f493e46de4e -size 31629 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/3ce04f1c7128814978c6b34d654a25cc_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/3ce04f1c7128814978c6b34d654a25cc_img.jpg deleted file mode 100644 index fe666a8687eef8980cf9aa6f4a11b8ac64470721..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/3ce04f1c7128814978c6b34d654a25cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3e77daab6605f709eaad4501be17da697e23e42c7afa852cdf77ca26236bc0b6 -size 57609 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/3f727e6c0d6658bc53ea10905c4561dd_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/40ebe9179df298f1b6d76822f28d90aa_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/40ebe9179df298f1b6d76822f28d90aa_img.jpg deleted file mode 100644 index 73cdfcbf45886435bdf2f85025837847a965f8d2..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/40ebe9179df298f1b6d76822f28d90aa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d5bd6934767ac7611118481f0cc33aaf37b54ab7a3a61454d21a53d19f96f201 -size 13905 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/41aef1f5efab13d4f38f69e86c726062_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/41aef1f5efab13d4f38f69e86c726062_img.jpg deleted file mode 100644 index c2e5d8ae8d343c12dc8e88c10a3ac6b35c686b41..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/41aef1f5efab13d4f38f69e86c726062_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f1a36b49d86b329ad0539667575208160f76eaa65b5ff9774802666e486eff5f -size 59817 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/4636adff5682a064f0ae5f13a1d464a6_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/4636adff5682a064f0ae5f13a1d464a6_img.jpg deleted file mode 100644 index 92309a27bc3cbc12db688fe9bf09b1dfe77876b2..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/4636adff5682a064f0ae5f13a1d464a6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3f13c7ab9428d8b18c52f5ef1eef553413836b0ce13f6492f5fe245d716f33a5 -size 48071 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/4a04896dfb569893fba50729314024f5_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/5445597cceefaca1ac89e710fe339325_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/5445597cceefaca1ac89e710fe339325_img.jpg deleted file mode 100644 index dbca112cf131928cfcfaf445ba9867644549d1ac..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/5445597cceefaca1ac89e710fe339325_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6e8c17a232b8d0a365493ef36f5a26337d91e8e0c806a59ba8e371398929dd5b -size 58303 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/562f471e8153729557e6a4ee6343c32c_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/562f471e8153729557e6a4ee6343c32c_img.jpg deleted file mode 100644 index 1417ad939a0e36874df51126520c0c38a56decfe..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/562f471e8153729557e6a4ee6343c32c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:38c8eeed91ab495b22158fef80061ff63fce6c26d5e7117a84bd618a8160076b -size 29151 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/56ac11fb9683d7b846fb65c845d80f22_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/5a1abd59a95fa47ae192807de151e9eb_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/5a1abd59a95fa47ae192807de151e9eb_img.jpg deleted file mode 100644 index 07c81e4122e5f80349baed22de708515b85aa774..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/5a1abd59a95fa47ae192807de151e9eb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:85c7a2471b34f019b90de1f8334adfb7a6dc031995ac36e0c5a697413e64ba88 -size 63944 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/5ae3023386ee15fae372871afce28865_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg deleted file mode 100644 index cea92f3aaa1eb1baaaad2582f8e06006df3d7569..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:46f78972c868b426cd4e35b035862d870d5969fd52365d3ec8967fb91cec5564 -size 57037 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/6588b1c7f14069d96744b473ad663248_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/6a5342571eca4b46338fdfb3c42a8055_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg deleted file mode 100644 index 52b1ebf53a453c5286ead042530e94a5b0843657..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:77069014267dc7ac8624652ce454d981c60227b1d2a9d4d2adafa66a504dc0b0 -size 14040 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/7d08458fbe0bd5f306c00c16d68b25f2_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/7f4320cee12fc1dbb865cc6b67462a91_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/834fb96b114b8fdc001625e1ae28e8b1_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/834fb96b114b8fdc001625e1ae28e8b1_img.jpg deleted file mode 100644 index ffd6eb0d7db5c3dce60028f8213e5b57c7db45a3..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/834fb96b114b8fdc001625e1ae28e8b1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7b484547b234ee23ddfef50c4f65790a175bf939c175357e48c329aeff3aab47 -size 26275 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/854df8ad60507803253274673f9062cf_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/8d129c93d18909f0643766f372e9ebf6_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/8dcca7651accff77ce832523fe2c7e64_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/8e14350b4b669119a3bdfca7869110ca_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/8e14350b4b669119a3bdfca7869110ca_img.jpg deleted file mode 100644 index 21dfde37c6f22bcc19c82a0069a7e6c2f86c5675..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/8e14350b4b669119a3bdfca7869110ca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ca140c4b4f4e1341c3d34d4dfe49fbff7b03b66f901ad30d6b84bf827c1d406f -size 5213 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/9156549264d36ead617a1dec7987f970_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg deleted file mode 100644 index d872235128af519c6bd2b81551fd01aa8df8f304..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9b1e2f64e0cb5f354a0ea0f53038daddf718abdf5c62112c1a9446faa6aad307 -size 41436 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/990567efebf979be51f56d1150012c9d_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/990567efebf979be51f56d1150012c9d_img.jpg deleted file mode 100644 index 1cf8eaa5dcc71391f0f2ffd76efdc2cdb582ed6b..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/990567efebf979be51f56d1150012c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a877d60867248beb258f6f97c051fa2daed0e6f2e337a7c8b6dac5fc7a6fcd21 -size 8372 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/9a6ff2584005112f32fbd551cb6f0591_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/9b59a11096b85b2bc74c6f653a354e28_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/9c1d3678db4a12d5864cb2a4def1135d_img.jpg deleted file mode 100644 index 190bae4935169772c904870a13ffa65e603a3d6a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/9c1d3678db4a12d5864cb2a4def1135d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:adb154dcf918b56a8afb8dcb8cff8d6687b06f229fcf8caa6aa77d2d86724532 -size 50640 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/a28ab03366399b5e0a61445bc57e3724_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg deleted file mode 100644 index ba0d04d4578faf73dc18facbefa81ac68ac5f236..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/a3953dce8dbd7ef15d61a314dbef2cf9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:655e220ebccf138aec6e9eb5df7b802f3c09c56020cbbc3f31cd6c2116a348e6 -size 45176 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/a738993919a50143787084ee7ce6e2f2_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/a738993919a50143787084ee7ce6e2f2_img.jpg deleted file mode 100644 index fc199ec04283e4a66263eded413914d9ea713beb..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/a738993919a50143787084ee7ce6e2f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c9ced823708a28b954f70cda222aad338883f2073e0fd9c55dfa96468dc74d5b -size 7752 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg deleted file mode 100644 index 4187fd56d2fc8b5d551e6fa1bb184592d6bbd8c5..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2cc3a4f331d6d30a34fc76c0ba4bb9870d0a48bbc373ff7fc5342c3001bc9365 -size 22796 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/be8d4d130f4e1f103926de61c4bfc23c_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/c389468860cd886ab9c732473e959f0f_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/cb5f64aa26cee1c05257b7c6bbba7408_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg deleted file mode 100644 index 61b26ee4e165d1e185ca3777d3fae81fb4b5e2f4..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:11a324eb759ec36b11740eba713c7b622a8fc856f763e5e9393d7225ec0fefe7 -size 19935 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/d0c9888da9078a08d93712fd0e113a88_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/d0c9888da9078a08d93712fd0e113a88_img.jpg deleted file mode 100644 index bb92dfa1c4554e46877bd2eb68adad402e2b2900..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/d0c9888da9078a08d93712fd0e113a88_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b5b3cad400dc7cbdea2be18fc6fba9465320972f1bd5ae4513f5df9741c19ce0 -size 6316 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/d26959f4514c26ca19c3d6f00da85956_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/d26959f4514c26ca19c3d6f00da85956_img.jpg deleted file mode 100644 index 5a2d6fc2fbf33cf6edc4644b5a049d568ea29eba..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/d26959f4514c26ca19c3d6f00da85956_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6a82557db1a67f9e355b358258c958928b82dc9d120d59b9d55540383a9f9082 -size 5453 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/d90f17b29a73eddf151f51effa8912e0_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg deleted file mode 100644 index 5180c2b9fd9e0a383e5b47e9aa9e3d1ac3e5a08d..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ae23a7c972ccf6e8ca04434a849bf5ed87424626f133f842f350d024c0500ff -size 57308 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e511e373339b5f948f239b19e0c37dd4_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e58a867750e4ae01604318506b79df7a_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e58a867750e4ae01604318506b79df7a_img.jpg deleted file mode 100644 index b2872a30af3efdbfdc038924cf1659309659fdd7..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e58a867750e4ae01604318506b79df7a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9f532a52e4b6aced2bbf8ca3d970702307ac90364559d294fdb4b1e11d26b0d5 -size 6895 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/e87df69ebd4cd2dbbf6749079e6c057a_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/ec3647789b5c38fb686f2a0833324e79_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/ec3647789b5c38fb686f2a0833324e79_img.jpg deleted file mode 100644 index e44277c9d44448158366938c7918f1bf94e3f64e..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/ec3647789b5c38fb686f2a0833324e79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d9c7b3fb458ed2571b9f78bc5a5a3bed0249ff328785fb0f8926c5ba96687713 -size 33155 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg deleted file mode 100644 index eaa457645a66fdd16f4d514b1b235f385b4cbf6c..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:de3cb17623493f0bd321c65ac12a1da1736993a58db9c667456fd2ca041adb1c -size 55394 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/f74adaa1840504407cd4272995426f82_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/f7dbd497160f02888f34fdf243648aa2_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/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg deleted file mode 100644 index a0aefcda970aa80cd878da8ce20b4143346c2776..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1e83f83b8aaffc09400eaa7a9d01781793d0f409ffb13ec21e8fc1603246459b -size 32868 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/fcbc3c31776721edc98ceb1944ec438f_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/fcbc3c31776721edc98ceb1944ec438f_img.jpg deleted file mode 100644 index 977f1fe64e184f6d91b7852a14b51de25f01d3a2..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/fcbc3c31776721edc98ceb1944ec438f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9bc2ac97d41182311bb46455daa2fba22be141ce929aecb6854aeee4b09b5cde -size 42388 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg deleted file mode 100644 index 452004ec3ab49b095c7082eba2ce2429199c16a3..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-CIMI.0-R005-v06.00/images/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:451b618043796262826ed15b88d46847e18b216f2b4f575677d4411a9ac193d3 -size 64925 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/doc.md b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/doc.md deleted file mode 100644 index 2b44563b0157eb9d3c6e6f59a2e460bae506c73a..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/doc.md +++ /dev/null @@ -1,1263 +0,0 @@ - - -# --- **O-RAN Work Group 10 (OAM for O-RAN)** - -## **Topology Exposure and Inventory Data Model Specification - Stage 3** - -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 - -# Contents - -| | | -|--------------------------------------------------------------------------------|----| -| Foreword..... | 3 | -| Modal verbs terminology..... | 3 | -| Executive summary ..... | 3 | -| 1. Scope ..... | 4 | -| 2. References ..... | 4 | -| 2.1. Normative references ..... | 4 | -| 2.2. Informative references..... | 4 | -| 3. Definition of terms, symbols and abbreviations..... | 4 | -| 3.1. Terms..... | 4 | -| 3.2. Symbols..... | 5 | -| 3.3. Abbreviations ..... | 5 | -| 4. Solution Set (SS) definitions ..... | 5 | -| 4.1 YANG based Solution Set (SS) definitions..... | 5 | -| 4.1.1 TE&IV Mapping from YANG to JSON schema ..... | 5 | -| Annex A (normative): YANG definitions for common types and extensions..... | 7 | -| A.1 Generals..... | 7 | -| A.2 Common Modules ..... | 7 | -| A.2.1 module o-ran-smo-teiv-common-yang-types..... | 7 | -| A.2.2 module o-ran-smo-teiv-common-yang-extensions ..... | 9 | -| Annex B (normative): YANG definitions for O-RAN TE&IV RAN Domain..... | 12 | -| B.1 General ..... | 12 | -| B.2 module o-ran-smo-teiv-ran..... | 12 | -| Annex C (normative): YANG definitions for O-RAN TE&IV Physical Domain..... | 15 | -| C.1 General ..... | 15 | -| C.2 module o-ran-smo-teiv-physical..... | 15 | -| Annex D (normative): YANG definitions for O-RAN TE&IV Physical-RAN Domain..... | 17 | -| D.1 General ..... | 17 | -| D.2 module o-ran-smo-teiv-rel-physical-ran..... | 17 | -| Annex E (informative): YANG based User Defined Data Input Schema ..... | 19 | -| E.1 General ..... | 19 | -| E.2 Example Module (Decorators and Classifiers)..... | 19 | -| E.3 Example Module (Classifiers)..... | 20 | -| E.4 Example Module (Decorators) ..... | 20 | -| Annex F (normative): YANG definitions for O-RAN TE&IV O-Cloud Domain..... | 21 | -| F.1 General ..... | 21 | -| F.2 module o-ran-smo-teiv-cloud ..... | 21 | -| Annex (informative): Change History ..... | 23 | - -# --- Foreword - -This Technical Specification (TS) has been produced by WG10 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. - -# --- Executive summary - -The present document specifies the TE&IV Data Models suited to realize the TE&IV Information Models as specified in [1]. - -# --- 1. Scope - -This document specifies the TE&IV Data Models used to support TE&IV services within 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. - -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.WG10.TS.TE&IV-CIMI.0: "Topology Exposure & Inventory Common Information Models and Interface Specification - Stage 2" ("TE&IV CIMI") -- [2] O-RAN.WG10.TS.TE&IV-API.0: "Topology Exposure & Inventory Application Protocols Specification - Stage 3" ("TE&IV API") -- [3] IETF RFC 7951: "JSON Encoding of Data Modeled with YANG" - -## 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] IETF RFC 7950: "The YANG 1.1 Data Modeling Language" - -# --- 3. Definition of terms, symbols and abbreviations - -## 3.1. Terms - -Void - -## 3.2. Symbols - -Void - -## 3.3. Abbreviations - -Void - -# --- 4. Solution Set (SS) definitions - -## 4.1 YANG based Solution Set (SS) definitions - -The present document defines the following TE&IV Solution Set definitions for O-RAN: - -- YANG based ORAN TEIV Common YANG Types and Extensions Solution Set (Annex A). -- YANG based ORAN TE&IV RAN Domain Solution Set (Annex B). -- YANG based ORAN TE&IV Physical Domain Solution Set (Annex C). -- YANG based ORAN TE&IV REL-Physical-RAN Domain Solution Set (Annex D). -- YANG based User Defined Data Schema (Annex E). -- YANG based ORAN TE&IV O-Cloud Domain Solution Set (Annex F). - -### 4.1.1 TE&IV Mapping from YANG to JSON schema - -#### 4.1.1.1 Introduction - -As specified in Clause 5.3 of the TE&IV API Specification [2], responses with message content shall be in JSON format. - -This clause defines the JSON mappings for the YANG schema specified in clause 4.1. Building on the principles outlined in RFC 7951 [3], the mappings specified here are extended to accommodate the YANG extensions in the O-RAN TE&IV YANG based Solution Set. - -#### 4.1.1.2 The “biDirectionalTopologyRelationship” Data Node - -The biDirectionalTopologyRelationship data node describes a bi-directional relationship in the TE&IV model. It is a relationship comprising of an aSide and a bSide. - -aSide and bSide are YANG extensions representing each end of the relationship. The order of aSide and bSide is important and must not be changed once defined. See TE&IV Common Information Models and Interface [1] Clause 4.2.1.1.4.1. Both aSide and bSide take a Topology Entity type as an argument. This entity type is represented by an instance identifier. - -A biDirectionalTopologyRelationship instance is encoded as an object containing an array of nested objects, where each nested object represents child data nodes as its properties, as shown below. - -A YANG example for the biDirectionalTopologyRelationship definition would be - -``` - -or-teiv-yext:biDirectionalTopologyRelationship NFDEPLOYMENT_SERVES_ODUFUNCTION { - ... - key id; - - leaf-list served-oduFunction { - description "O-DU Function served by this NF Deployment."; - or-teiv-yext:aSide or-teiv-cloud:NFDeployment; - type instance-identifier; - } - - leaf-list serving-nFDeployment { - description "NF Deployment that serves this O-DU Function."; - or-teiv-yext:bSide or-teiv-ran:ODUFunction; - type instance-identifier; - } -} - -``` - -the following is an example of a valid JSON-encoded instance: - -``` - -{ - "o-ran-smo-teiv-rel-ran-cloud: NFDEPLOYMENT_SERVES_ODUFUNCTION": [ - { - "id": "urn:", - "serving-nFDeployment": "urn:", - "served-oduFunction": "urn:", - "sourceIds": [ - "urn:", - "urn:" - ] - } - ] -} - -``` - -# --- Annex A (normative): YANG definitions for common types and extensions - -## A.1 Generals - -This annex contains the YANG definitions for the common types and extensions to the YANG language that topology and inventory model will frequently use, in accordance with information model definitions specified in TE&IV CIMI [1]. - -## A.2 Common Modules - -### A.2.1 module o-ran-smo-teiv-common-yang-types - -``` - -module o-ran-smo-teiv-common-yang-types { - yang-version 1.1; - namespace "urn:o-ran:smo-teiv-common-yang-types"; - prefix or-teiv-types; - - import o-ran-smo-teiv-common-yang-extensions { prefix or-teiv-yext; } - - import _3gpp-common-yang-types { prefix types3gpp; } - - organization "O-RAN Alliance"; - - contact - "www.o-ran.org"; - - description - "Topology and Inventory common types model. - This model contains re-usable data types that topology and inventory models - will frequently use as part of types and relationships. - - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/sccl"; - - revision "2025-11-19" { - description "Replaced O-RAN Alliance License with SCCL License as per OSARP."; - or-teiv-yext:label 1.2.1; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00"; - } - - revision "2025-06-30" { - description "Added support for TE&IV User defined data"; - or-teiv-yext:label 1.2.0; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R004-v03.00"; - } - - revision "2025-02-14" { - description "Updated with GeoInformation."; - or-teiv-yext:label 1.1.0; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R004-v02.00"; - } - - revision "2025-02-24" { - description "Renamed Adapter Entity to Origin Entity. Added Geo-Information"; - or-teiv-yext:label 1.1.0; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R004-v02.00"; - } -} -``` - -``` - -revision "2024-10-10" { - description "Initial revision."; - or-teiv-yext:label 1.0.0; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R004-v01.00"; -} - -grouping Top_Grp_Type { - description "Grouping containing the key attribute common to all types. All types MUST use this grouping."; - - leaf id { - type string; - description "Unique identifier of topology entities. Represents the Entity Instance Identifier."; - } -} - -grouping Origin_Entity_Mapping_Grp { - description "Grouping to identify sourceIds on a topology object"; - - leaf-list sourceIds { - type sourceId; - min-elements 1; - ordered-by user; - description - "An ordered list of identities that represent the set of native source identifiers for participating entities. This must be attached to Topology Entity instance, outside of the declared Topology Entity's attributes. This is exposed to the consumers and can only be set by the responsible adapter. This cannot be instantiated, and it MUST NOT be augmented or deviated in any way, unless stated otherwise."; - } -} - -grouping Origin_Relationship_Mapping_Grp { - description "Grouping to identify sourceIds on a topology relationship."; - - leaf-list sourceIds { - type sourceId; - min-elements 2; - ordered-by user; - description - "An ordered list of identities that represent the set of native source identifiers for participating entities in the relationship. This must be attached to the Topology Relation instance, outside of the declared Topology Relationship's attributes. This is exposed to the consumers and can only be set by the responsible adapter. This cannot be instantiated, and it MUST NOT be augmented or deviated in any way, unless stated otherwise."; - } -} - -typedef sourceId { - type string; - description "An identity that represents a native identifier of a topology entity."; -} - -grouping GeoInformation { - description "A physical location with address and coordinates."; - - leaf address { - type string; - description "Address of the physical location."; - } - - container coordinate { - presence "Enable coordinate"; - uses types3gpp:GeoCoordinateGrp; - description "Geographical coordinate containing Latitude, Longitude and Altitude. Reference: 3GPP TS 28.623"; - } -} - -container decorators { - description - "This container serves as extension point for applications wishing - -``` - -``` - - to define their own decorators. This is done via augmentations. They - can only be defined in name value pair. - This is consumer data and can be attached to Topology Entity or - Topology Relation instance, outside of the declared Topology Entity - or Topology Relationship's attributes. This cannot be instantiated, - and it MUST NOT be augmented or deviated in any way, unless stated - otherwise."; - } - leaf-list classifiers { - type identityref { base classifier; } - description - "Consumer defined tags to topology entities and relationships. - This is consumer data and can be attached to Topology Entity or - Topology Relation instance, outside of the declared Topology Entity - or Topology Relationship's attributes. This cannot be instantiated, - and it MUST NOT be augmented or deviated in any way, unless stated - otherwise."; - } - - identity classifier { - description "The classifier is used as a base to provide all classifiers - with identity. "; - } -} - - -``` - -### A.2.2 module o-ran-smo-teiv-common-yang-extensions - -``` - - -module o-ran-smo-teiv-common-yang-extensions { - yang-version 1.1; - namespace "urn:o-ran:smo-teiv-common-yang-extensions"; - prefix or-teiv-yext; - - organization "O-RAN Alliance"; - - contact - "www.o-ran.org"; - - description - "Topology and Inventory YANG extensions model. - This model contains extensions to the YANG language that topology and - inventory models will use to define and annotate types and relationships. - - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/sccl"; - - revision "2025-11-19" { - description "Replaced O-RAN Alliance License with SCCL License as per OSARP."; - or-teiv-yext:label 1.1.1; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00"; - } - - revision "2025-02-14" { - description "Updates for bi-directional relationship."; - or-teiv-yext:label 1.1.0; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R004-v02.00"; - } - - revision "2024-10-10" { - description "Initial revision."; - or-teiv-yext:label 1.0.0; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R004-v01.00"; - } - - extension biDirectionalTopologyRelationship { - argument relationshipName; - description - "Defines a bi-directional relationship in the topology. - A bi-directional-association (BDA) is a relationship comprising of - an aSide and a bSide. The aSide is considered the originating - side of the relationship; the bSide is considered the terminating - -``` - -side of the relationship. The order of aSide and bSide is of importance and MUST NOT be changed once defined. - -Both aSide and bSide are defined on a type, and are given a role. A type may have multiple originating and/or terminating sides of a relationship, all distinguished by role name. - -The statement MUST only be a substatement of the 'module' statement. Multiple 'biDirectionalTopologyRelationship' statements are allowed per parent statement. - -Substatements to the 'biDirectionalTopologyRelationship' define the aSide and the bSide, respectively, and optionally properties of the relationship. Data nodes of types 'leaf' and 'leaf-list' are used for this purpose. One of the data nodes MUST be annotated with the 'aSide' extension; another data node MUST be annotated with the 'bSide' extension. Other data nodes define properties of the relationship. - -The argument is the name of the relationship. The relationship name is scoped to the namespace of the declaring module and MUST be unique within the scope."; - -} - -``` -extension aSide { - argument aSideType; - description - "Defines the aSide of a relationship. -``` - -The statement MUST only be a substatement of a 'leaf' or 'leaf-list' statement, which itself must be a substatement of the 'biDirectionalTopologyRelationship' statement. - -The data type of the parent 'leaf' or 'leaf-list' MUST be 'instance-identifier'. Constraints MAY be used as part of the parent 'leaf' or 'leaf-list' to enforce cardinality. - -The identifier of the parent 'leaf' or 'leaf-list' is used as name of the role of the aSide of the relationship. The name of the role is scoped to the type on which the aSide is defined and MUST be unique within the scope. - -While the parent 'leaf' or 'leaf-list' does not result in a property of the relationship, it is RECOMMENDED to avoid using the name of an existing type property as role name to avoid potential ambiguities between properties of a type, and roles of a relationship on the type. - -The argument is the name of the type on which the aSide resides. If the type is declared in another module, the type must be prefixed, and a corresponding 'import' statement be used to declare the prefix."; - -} - -``` -extension bSide { - argument bSideType; - description - "Defines the bSide of a relationship. -``` - -The statement MUST only be a substatement of a 'leaf' or 'leaf-list' statement, which itself must be a substatement of the 'biDirectionalTopologyRelationship' statement. - -The data type of the parent 'leaf' or 'leaf-list' MUST be 'instance-identifier'. Constraints MAY be used as part of the parent 'leaf' or 'leaf-list' to enforce cardinality. - -The identifier of the parent 'leaf' or 'leaf-list' is used as name of the role of the bSide of the relationship. The name of the role is scoped to the type on which the bSide is defined and MUST be unique within the scope. - -While the parent 'leaf' or 'leaf-list' does not result in a property of the relationship, it is RECOMMENDED to avoid using the name of an existing type property as role name to avoid potential ambiguities between properties of a type, and roles of a relationship on the type. - -``` - The argument is the name of the type on which the bSide resides. - If the type is declared in another module, the type must be - prefixed, and a corresponding 'import' statement be used to declare - the prefix."; - } - - extension domain { - argument domainName; - description "Keyword used to carry domain information."; - } - - extension label { - argument semversion; - description - "The label can be used to give modules and submodules a semantic - version, in addition to their revision. - - The format of the label is 'x.y.z' - expressed as pattern, it is - [0-9]+\.[0-9]+\.[0-9]+ - - The statement MUST only be a substatement of the revision statement. - Zero or one revision label statements per parent statement are - allowed. - - Revision labels MUST be unique amongst all revisions of a module or - submodule."; - } -} - -``` - -# Annex B (normative): YANG definitions for O-RAN TE&IV RAN Domain - -## B.1 General - -This annex contains the YANG definitions for the TE&IV RAN domain, in accordance with ORAN.SMO.TEIV.RAN information model definitions specified in TE&IV CIMI [1]. - -## B.2 module o-ran-smo-teiv-ran - -``` - -module o-ran-smo-teiv-ran { - yang-version 1.1; - namespace "urn:o-ran:smo-teiv-ran"; - prefix or-teiv-ran; - - import o-ran-smo-teiv-common-yang-types {prefix or-teiv-types; } - - import o-ran-smo-teiv-common-yang-extensions {prefix or-teiv-yext; } - - import _3gpp-common-yang-types { prefix types3gpp; } - - organization "O-RAN Alliance"; - - contact - "www.o-ran.org"; - - description - "RAN Logical topology model. - This model contains the topology entities and relations in the - RAN Logical domain, which represents the functional capability - of the deployed RAN that are relevant to rApps use cases. - - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/sccl"; - - revision "2025-11-19" { - description "Replaced O-RAN Alliance License with SCCL License as per OSARP."; - or-teiv-yext:label 1.1.1; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00"; - } - - revision "2025-02-14" { - description "Revision to rename adapter group to origin group."; - or-teiv-yext:label 1.1.0; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R004-v02.00"; - } - - revision "2024-10-10" { - description "Initial revision."; - or-teiv-yext:label 1.0.0; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R004-v01.00"; - } - - or-teiv-yext:domain RAN; - - list ODFunction { - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Entity_Mapping_Grp; - key id; - description "O-RAN Distributed Unit (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. - -The O-DU terminates the E2 and the F1 interface, and the Open Fronthaul interface (also known as LLS interface) as well as the RLC, MAC, and High-PHY functions of the radio interface towards the UE. - -Note: O-DU is a concrete class that extends the ORANNetworkFunction abstract class. In Topology, you can create, read, update, and delete the O-DU object. - -The management characteristics of the O-DU O-RAN NF are represented by the IOC GNBDUFunction as specified in 3GPP NR NRM model, as per 3GPP TS 28.541"; - -``` -container attributes { - description "Container for O-RAN Distributed Unit (O-DU) attributes"; - leaf gNBDUID { - type int64; - description "Unique identifier for the DU within a gNodeB"; - } - - leaf gNBId { - type int64; - description "Identity of gNodeB within a PLMN"; - } - - leaf gNBIdLength { - type int32; - description "Length of gNBId bit string representation"; - } -} - -list OCUCPFunction { - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Entity_Mapping_Grp; - key id; -``` - -description "O-RAN Central Unit - Control Plane (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 defined by 3GPP TS 38.401. The O-CU-CP terminates E2 interface to Near-RT RIC and is managed via O1 interface by the SMO. - -Note: O-CU-CP is a concrete class that extends the ORANNetworkFunction abstract class. In Topology, you can create, read, update, and delete the O-CU-CP object. - -The management characteristics of the O-CU-CP O-RAN NF are represented by the IOC GNBCUCPFunction as specified in 3GPP NR NRM model, as per 3GPP TS 28.541"; - -``` -container attributes { - description "Container for O-RAN Central Unit - Control Plane (O-CU-CP) attributes"; - leaf gNBCUName { - type string; - description "Name of gNodeB-CU"; - } - - leaf gNBId { - type int64; - description "Identity of gNodeB within a PLMN"; - } - - leaf gNBIdLength { - type int32; - description "Length of gNBId bit string representation"; - } - - container pLMNId { - presence "Enable pLMNId"; - description "PLMN identifier to be used as part of global RAN node identity"; - uses types3gpp:PLMNId; - } -} - -list OCUUPFunction { - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Entity_Mapping_Grp; - key id; - - description "O-RAN Central Unit - User Plane (O-CU-UP)" -``` - -The O-CU-UP terminates the NG-u, X2-u, Xn-u, F1-u, and E1 interfaces as well as the PDCP and SDAP protocols towards the UE as defined by 3GPP TS 38.401. The O-CU-UP terminates E2 interface to Near-RT RIC and is managed via O1 interface by the SMO. - -Note: O-CU-UP is a concrete class that extends the ORANNetworkFunction abstract class. In Topology, you can create, read, update, and delete the O-CU-UP object. - -The management characteristics of the O-CU-UP O-RAN NF are represented by the IOC GNBCUUPFunction as specified in 3GPP NR NRM model, as per 3GPP TS 28.541"; - -``` - -container attributes { - description "Container for O-RAN Central Unit - User Plane (O-CU-UP) attributes"; - leaf gNBId { - type int64; - description "Identity of gNodeB within a PLMN"; - } - - leaf gNBIdLength { - type int32; - description "Length of gNBId bit string representation"; - } - - list pLMNIdList { - key "mcc mnc"; - description "List of unique identities for PLMN"; - uses types3gpp:PLMNId; - } -} - -list NearRTRICFunction { - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Entity_Mapping_Grp; - key id; - - description "Near-Real-Time RAN Intelligent Controller (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."; - - container attributes { - description "Container for Near-Real-Time RAN Intelligent Controller (Near-RT RIC) attributes"; - container pLMNId { - description "PLMN identifier to be used as part of global RAN node identity"; - uses types3gpp:PLMNId; - } - - leaf nearRtRicId { - type int32; - description "Identifier of Near-RT RIC"; - } - } -} - -list ORUFunction { - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Entity_Mapping_Grp; - key id; - - description "O-RAN Radio Unit (O-RU)"; - The O-RU terminates the Open Fronthaul interface (also known as LLS interface) 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."; - - container attributes { - description "Container for O-RAN Radio Unit (O-RU) attributes"; - leaf oruId { - type string; - description "Identity of the O-RU as discovered from the source domain based on M-Plane - architecture model"; - } - } -} - - - -``` - -# Annex C (normative): YANG definitions for O-RAN TE&IV Physical Domain - -## C.1 General - -This annex contains the YANG definitions for the TE&IV Physical domain, in accordance with ORAN.SMO.TEIV.Physical information model definitions specified in TE&IV CIMI [1]. - -## C.2 module o-ran-smo-teiv-physical - -``` - -module o-ran-smo-teiv-physical { - yang-version 1.1; - namespace "urn:o-ran:smo-teiv-physical"; - prefix or-teiv-physical; - - import o-ran-smo-teiv-common-yang-types {prefix or-teiv-types; } - - import o-ran-smo-teiv-common-yang-extensions {prefix or-teiv-yext; } - - organization "O-RAN Alliance"; - - contact - "www.o-ran.org"; - - description - "Physical domain topology model. - This model contains the topology entities and relations in the - Physical domain. - - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/sccl"; - - revision "2025-11-19" { - description "Replaced O-RAN Alliance License with SCCL License as per OSARP."; - or-teiv-yext:label 1.1.1; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00"; - } - - revision "2025-06-30" { - description "Updated revision to add container attribute for site."; - or-teiv-yext:label 1.1.0; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R004-v03.00"; - } - - revision "2025-02-10" { - description "Initial revision."; - or-teiv-yext:label 1.0.0; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R004-v02.00"; - } - - or-teiv-yext:domain PHYSICAL; - - list PhysicalAppliance { - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Entity_Mapping_Grp; - key id; - - description "Represents the Physical Appliance in the Physical domain"; - - container attributes { - description "Container for Physical Appliance attributes"; - leaf vendorName { -``` - -``` - - type string; - description "Name of the physical appliance vendor"; - } - - leaf modelName { - type string; - description "Name of the physical appliance model"; - } - - leaf serialNumber { - type string; - description "Serial number of the physical appliance"; - } - - leaf applianceType { - type string; - description "Indicates the type of physical appliance"; - } -} - -list Site { - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Entity_Mapping_Grp; - key id; - description "Represents the Site in the Physical domain"; - container attributes { - description "Container for Site attributes"; - container siteLocation { - description "Representation of physical site location"; - uses or-teiv-types:GeoInformation; - } - leaf siteName { - type string; - description "Human readable name of the physical site as identified by the mobile network -operator"; - } - } -} - -or-teiv-yext:biDirectionalTopologyRelationship PHYSICALAPPLIANCE_INSTALLEDAT_SITE { // 1..n to 1..m - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Relationship_Mapping_Grp; - key id; - description "The aSide of this relationship is an instance of the PhysicalAppliance type. -The bSide of this relationship is an instance of the Site type."; - - leaf-list installing-site { - type instance-identifier; - description "Site installing PhysicalAppliance."; - or-teiv-yext:aSide PhysicalAppliance; - } - - leaf-list installed-physicalAppliance { - type instance-identifier; - description "PhysicalAppliance installed at Site."; - or-teiv-yext:bSide Site; - } -} - - - -``` - -# Annex D (normative): YANG definitions for O-RAN TE&IV Physical-RAN Domain - -## D.1 General - -This annex contains the YANG definitions for the TE&IV REL-Physical-RAN domain, in accordance with ORAN.SMO.TEIV.REL-Physical-RAN information model definitions specified in TE&IV CIMI [1]. - -## D.2 module o-ran-smo-teiv-rel-physical-ran - -``` - -module o-ran-smo-teiv-rel-physical-ran { - yang-version 1.1; - namespace "urn:o-ran:smo-teiv-rel-physical-ran"; - prefix or-teiv-rel-phyran; - - import o-ran-smo-teiv-common-yang-types {prefix or-teiv-types; } - - import o-ran-smo-teiv-common-yang-extensions {prefix or-teiv-yext; } - - organization "O-RAN Alliance"; - - contact - "www.o-ran.org"; - - description - "Physical to RAN Logical topology domain model. - - This model contains the topology relationship between the - physical domain and the RAN domain. - - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/sccl"; - - revision "2025-11-19" { - description "Replaced O-RAN Alliance License with SCCL License as per OSARP."; - or-teiv-yext:label 1.0.1; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00"; - } - - revision "2025-02-10" { - description "Initial revision."; - or-teiv-yext:label 1.0.0; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R004-v02.00"; - } - - or-teiv-yext:domain REL_PHYSICAL_RAN; - - or-teiv-yext:biDirectionalTopologyRelationship PHYSICALAPPLIANCE_SERVES_ODUFUNCTION { // 1..n to 1..m - - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Relationship_Mapping_Grp; - key id; - description "The aSide of this relationship is an instance of the PhysicalAppliance type. - The bSide of this relationship is an instance of the ODFunction type."; - - leaf-list served-oduFunction { - type instance-identifier; - description "ODFunction served by PhysicalAppliance."; - or-teiv-yext:aSide or-teiv-physical:PhysicalAppliance; - } - - leaf-list serving-physicalAppliance { -``` - -``` - - type instance-identifier; - description "PhysicalAppliance serving ODUFunction."; - or-teiv-yext:bSide or-teiv-ran:ODUFunction; - } -} - -or-teiv-yext:biDirectionalTopologyRelationship PHYSICALAPPLIANCE_SERVES_OCUCPFUNCTION { // 1..n to 1..m - - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Relationship_Mapping_Grp; - key id; - description "The aSide of this relationship is an instance of the PhysicalAppliance type. - The bSide of this relationship is an instance of the OCUCPFunction type."; - - leaf-list served-ocucpFunction { - type instance-identifier; - description "OCUCPFunction served by PhysicalAppliance."; - or-teiv-yext:aSide or-teiv-physical:PhysicalAppliance; - } - - leaf-list serving-physicalAppliance { - type instance-identifier; - description "PhysicalAppliance serving OCUCPFunction."; - or-teiv-yext:bSide or-teiv-ran:OCUCPFunction; - } -} - -or-teiv-yext:biDirectionalTopologyRelationship PHYSICALAPPLIANCE_SERVES_OCUPPFUNCTION { // 1..n to 1..m - - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Relationship_Mapping_Grp; - key id; - description "The aSide of this relationship is an instance of the PhysicalAppliance type. - The bSide of this relationship is an instance of the OCUPPFunction type."; - - leaf-list served-ocuppFunction { - type instance-identifier; - description "OCUPPFunction served by PhysicalAppliance."; - or-teiv-yext:aSide or-teiv-physical:PhysicalAppliance; - } - - leaf-list serving-physicalAppliance { - type instance-identifier; - description "PhysicalAppliance serving OCUPPFunction."; - or-teiv-yext:bSide or-teiv-ran:OCUPPFunction; - } -} - -or-teiv-yext:biDirectionalTopologyRelationship PHYSICALAPPLIANCE_SERVES_NEARRTRICFUNCTION { // 1..n to 1..m - - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Relationship_Mapping_Grp; - key id; - description "The aSide of this relationship is an instance of the PhysicalAppliance type. - The bSide of this relationship is an instance of the NearRTRICFunction type."; - - leaf-list served-nearRTRICFunction { - type instance-identifier; - description "NearRTRICFunction served by PhysicalAppliance."; - or-teiv-yext:aSide or-teiv-physical:PhysicalAppliance; - } - - leaf-list serving-physicalAppliance { - type instance-identifier; - description "PhysicalAppliance serving NearRTRICFunction."; - or-teiv-yext:bSide or-teiv-ran:NearRTRICFunction; - } -} - -} - - -``` - -# Annex E (informative): YANG based User Defined Data Input Schema - -## E.1 General - -This annex contains the YANG schema input files for the User Defined Data specified in TE&IV CIMI [1]. Before classifying the entities or the relationships in the topology network, the modules defined in the clauses below must be created and validated by using its own endpoint as shown in TE&IV API [2]. The user must provide a unique module name, to avoid collision of multiple users access that are defining classifiers and decorators. The schema cannot be modified later on but only deleted and recreated, if needed. Once a schema is successfully created and validated, the user can add the classifiers to the entities or relationships. The following clauses provide example templates for the schema input files. - -## E.2 Example Module (Decorators and Classifiers) - -``` - -module module-rapp-module { - - yang-version 1.1; - namespace "urn:module-rapp-model"; - prefix module; - - import o-ran-smo-teiv-common-yang-types { prefix module; } - import o-ran-smo-teiv-common-yang-extensions {prefix or-teiv-yext; } - - revision "2024-06-10" { - description - "Initial revision."; - or-teiv-yext:label 0.3.0; - } - - augment /module:decorators { - leaf decorator1 { - type string; - } - leaf decorator2 { - type boolean; - } - leaf decorator3 { - type uint32; - } - } - - identity classifier1 { - base module:classifiers; - } - - identity classifier2 { - base module:classifiers; - } - - identity classifier3 { - base module:classifiers; - } - -} - -``` - -## E.3 Example Module (Classifiers) - -``` - -module classifier-module-example { - - yang-version 1.1; - namespace "urn:classifier-module-example"; - prefix module; - - import o-ran-smo-teiv-common-yang-types { prefix module; } - import o-ran-smo-teiv-common-yang-extensions {prefix or-teiv-yext; } - - revision "2025-05-10" { - description - "Initial revision."; - or-teiv-yext:label 1.0.0; - } - - identity classifier1 { - base module:classifiers; - } - - identity classifier2 { - base module:classifiers; - } - - identity classifier3 { - base module:classifiers; - } - -} - -``` - -## E.4 Example Module (Decorators) - -``` - -module module-rapp-module { - - yang-version 1.1; - namespace "urn:module-rapp-model"; - prefix module; - - import o-ran-smo-teiv-common-yang-types { prefix module; } - import o-ran-smo-teiv-common-yang-extensions {prefix or-teiv-yext; } - - revision "2025-05-10" { - description - "Initial revision."; - or-teiv-yext:label 0.3.0; - } - - augment /module:decorators { - leaf decorator1 { - type string; - } - leaf decorator2 { - type boolean; - } - leaf decorator3 { - type uint32; - } - } - -} - -``` - -# Annex F (normative): YANG definitions for O-RAN TE&IV O-Cloud Domain - -## F.1 General - -This annex contains the YANG definitions for the TE&IV O-Cloud domain, in accordance with ORAN.SMO.TEIV.Cloud information model definitions specified in TE&IV CIMI [1]. - -## F.2 module o-ran-smo-teiv-cloud - -``` - -module o-ran-smo-teiv-cloud { - yang-version 1.1; - namespace "urn:o-ran:smo-teiv-cloud"; - prefix or-teiv-cloud; - import o-ran-smo-teiv-common-yang-types {prefix or-teiv-types; } - import o-ran-smo-teiv-common-yang-extensions {prefix or-teiv-yext; } - organization "O-RAN Alliance"; - contact - "www.o-ran.org"; - description - "Cloud domain topology model. - This model contains the topology entities and relations in the - Cloud domain. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/sccl"; - - revision "2025-10-23" { - description "Initial revision."; - or-teiv-yext:label 1.0.0; - reference "O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00"; - } - or-teiv-yext:domain CLOUD; - - list CloudifiedNF { - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Entity_Mapping_Grp; - key id; - description "Represents the Cloudified Network Function in the O-Cloud domain"; - container attributes { - description "Container for CloudifiedNF attributes"; - leaf cloudifiedNFId { - type string; - description "Identifier of the CloudifiedNF"; - } - leaf serviceOrchestrationId { - type string; - description "Identifier of the service orchestrator"; - } - } - } - - list NFDeployment { - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Entity_Mapping_Grp; - key id; - description "Represents the NF Deployment in the O-Cloud domain"; - container attributes { - description "Container for NF Deployment attributes"; - leaf nfDeploymentId { - type string; - description "Identifier of the NF Deployment"; - } - } - } -} -``` - -``` - - leaf resourceOrchestrationId { - type string; - description "Identifier of the resource orchestrator"; - } - leaf serviceOrchestrationId { - type string; - description "Identifier of the service orchestrator"; - } - } -} - -list OCloudNamespace { - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Entity_Mapping_Grp; - key id; - description "Represents the O-Cloud Namespace in the O-Cloud domain"; - container attributes { - description "Container for O-Cloud Namespace attributes"; - leaf oCloudNamespaceName { - type string; - description "Name of the O-Cloud Namespace"; - } - } -} - -list NodeCluster { - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Entity_Mapping_Grp; - key id; - description "Represents the Node Cluster in the O-Cloud domain"; - container attributes { - description "Container for Node Cluster attributes"; - leaf nodeClusterId { - type string; - description "Identifier of the Node Cluster"; - } - leaf nodeClusterName { - type string; - description "Name of the Node Cluster"; - } - leaf resourceOrchestrationId { - type string; - description "Identifier of the resource orchestrator"; - } - leaf serviceOrchestrationId { - type string; - description "Identifier of the service orchestrator"; - } - } -} - -list OCloudSite { - uses or-teiv-types:Top_Grp_Type; - uses or-teiv-types:Origin_Entity_Mapping_Grp; - key id; - description "Represents the O-Cloud Site in the O-Cloud domain"; - container attributes { - description "Container for O-Cloud Site attributes"; - container oCloudSiteLocation { - description "Representation of O-Cloud Site location"; - uses or-teiv-types:GeoInformation; - } - leaf oCloudSiteId { - type string; - description "Identifier of the O-Cloud Site"; - } - leaf-list supportedMITs { - type string; - description "List of the supported MITs in the O-Cloud Site"; - } - } -} -} - -``` - - - -# Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2024.10.01 | 00.00.01 | Initial proposed skeleton for the TE&IV Data Model Specification | -| 2024.11.21 | 01.00 | Implemented the following CRs for the November 2024 train: ERI-2024.08.14-WG10-CR-0128-Initial Content for the TE&IV Data Model Specification-v01, ERI-2024.10.09-WG10-CR-0130-TE&IV_RAN_Model-v02, ERI-2024.11.07-WG10-CR-0136-TE&IV_DM_ReferenceUpdate-v01 | -| 2025.02.07 | 02.00 | Implemented the following CRs for the March 2025 train: ERI-2024.12.10-WG10-CR-0139-TE&IV Mapping from YANG to JSON schema-v02, ERI.AO-2025.02.10-WG10-CR-0152-Update to TE&IV YANG Schema to JSON output-v01, ERI-2025.02.25-WG10-CR-0154-Update to existing TE&IV yang modules, ERI-2025.02.25-WG10-CR-0155-Introducing new yang extensions, ERI.AO-2025.02.25-WG10-CR-0156-Yang module for the Rel-Physical-RAN namespace, ERI.AO-2025.02.25-WG10-CR-0157-Yang module for the Physical namespace | -| 2025.07.01 | 03.00 | Implemented the following CRs for the July 2025 train: ERI-2025.05.20-WG10-CR-0176-YANG-Definitions-for-Classifiers-and-Decorators-v02, ERI-2025.05.26-WG10-CR-0177-Updating-3GPP-reference-v01, ERI-2025.06.25-WG10-CR-0188-Data Model editorials-v02. Updated the specification for formatting corrections and editorial updates based on ODR and TS template v04 | -| 2025.11.19 | 04.00 | Implemented the following CRs for the November 2025 train: ERI-2025.07.21-WG10-CR-0190-YANG Definitions Physical-v01, ERI-2025.09.16-WG10-CR-0199-Presence Field-v02, ERI-2025.10.27-WG10-CR-0210-Cloud YANG Data Model-v03, ERI-2025.11.06-WG10-CR-0211-Replacing O-RAN Alliance license with SCCL license in TE&IV YANG Modules-v01 | \ No newline at end of file diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/185df94f4a6a5245323255e844a30ec0_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/226f5e462c99b71e08dc9abaa5ae260c_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/253600420ae7bd7d0119563b895cbf8a_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/38222c3ae003223a67635bfcc6950fbb_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/4a04896dfb569893fba50729314024f5_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/6a5342571eca4b46338fdfb3c42a8055_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/83ee9f10bd3636e192d68decf7f04cec_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/854df8ad60507803253274673f9062cf_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/89100a6476d1d96f22c192db16502fec_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/8dcca7651accff77ce832523fe2c7e64_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/a28ab03366399b5e0a61445bc57e3724_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/e511e373339b5f948f239b19e0c37dd4_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/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index bb11a76f655fdf424066da755ce3bb9da561c72d..0000000000000000000000000000000000000000 --- a/files/WG10/O-RAN.WG10.TS.TE&IV-DM.0-R005-v04.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9181d1f22157938c8d6cae2e34c9e79ee14ca739bad919f900cbe2ffcacc1868 -size 4542 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/doc.md b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/doc.md deleted file mode 100644 index 0c9786cf764fbe23f21473d06e1cdc95f3585e5e..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/doc.md +++ /dev/null @@ -1,1929 +0,0 @@ - - -# --- **O-RAN Work Group 11 (WG11)****Study on Security for Artificial Intelligence and Machine Learning (AI/ML) in O-RAN** - ---- - -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 DE32172018 - -# --- Contents - -| | | -|--------------------------------------------------------|----| -| Foreword ..... | 5 | -| Modal verbs terminology ..... | 6 | -| 1 Scope..... | 7 | -| 2 References..... | 8 | -| 2.1 Normative references ..... | 8 | -| 2.2 Informative references..... | 8 | -| 3 Definition of terms, symbols and abbreviations ..... | 12 | -| 3.1 Terms..... | 12 | -| 3.2 Symbols..... | 13 | -| 3.3 Abbreviations ..... | 13 | -| 4 AI/ML Assets ..... | 14 | -| 4.1 Introduction ..... | 14 | -| 4.2 Functions ..... | 17 | -| 4.3 Interfaces ..... | 17 | -| 4.4 Data ..... | 17 | -| 4.5 Models..... | 18 | -| 4.6 Pipeline..... | 18 | -| 5 Threats..... | 19 | -| 5.1 Threat Model..... | 19 | -| 5.2 Threat Template ..... | 19 | -| 5.3 Potential Threats and Exploits..... | 20 | -| 5.3.1 Common Threats associated with ML..... | 20 | -| 5.3.2 Input Manipulation Attack (ML01:2023)..... | 22 | -| 5.3.3 Data poisoning attacks (ML02:2023)..... | 23 | -| 5.3.4 Model Inversion Attack (ML03:2023)..... | 24 | -| 5.3.5 Membership Inference Attack (ML04:2023) ..... | 25 | -| 5.3.6 Model Stealing (ML05:2023)..... | 26 | -| 5.3.7 AI Supply Chain Attacks (ML06:2023) ..... | 27 | -| 5.3.8 Transfer Learning Attack (ML07:2023)..... | 27 | -| 5.3.9 Model Skewing (ML08:2023)..... | 28 | -| 5.3.10 Output Integrity Attack (ML09:2023)..... | 29 | -| 5.3.11 Model Poisoning (ML10:2023)..... | 30 | -| 5.3.12 Evasion attacks ..... | 30 | -| 5.3.13 AI Energy-Latency Attack..... | 31 | -| 6 Threat Analysis ..... | 32 | -| 6.1 Input Manipulation Attack (ML01:2023) ..... | 32 | -| 6.1.1 Training Data Control..... | 32 | -| 6.1.2 Model Control ..... | 32 | -| 6.1.3 Testing Data Control ..... | 32 | -| 6.1.4 Label Manipulation ..... | 32 | -| 6.1.5 AI/ML Query Exploitation ..... | 33 | -| 6.2 Data poisoning attacks (ML02:2023)..... | 33 | -| 6.2.1 Black-box Data Poisoning..... | 33 | -| 6.2.2 Grey-box Data Poisoning ..... | 33 | -| 6.2.3 White-box Data Poisoning ..... | 34 | -| 6.3 Model Inversion Attack (ML03:2023)..... | 34 | -| 6.3.1 Black-box Model Inversion..... | 34 | -| 6.3.2 White-box Model Inversion ..... | 35 | -| 6.4 Membership Inference Attack (ML04:2023)..... | 35 | -| 6.4.1 Information Access – Membership Inference ..... | 35 | -| 6.4.2 Inference Technique – Membership Inference..... | 36 | -| 6.4.3 Target based Membership Inference ..... | 36 | -| 6.5 Model Stealing (ML05:2023)..... | 36 | - -- 6.5.1 Intellectual Property Theft.....36 -- 6.5.2 Data Privacy Violations.....37 -- 6.5.3 Adversarial Attacks with Stolen Models.....37 -- 6.6 AI Supply Chain Attacks (ML06:2023).....37 - - 6.6.1 Data Poisoning via Supply Chain.....37 - - 6.6.2 Model Tampering .....38 - - 6.6.3 Backdoor via Supply Chain.....38 - - 6.6.4 Hardware Tampering.....39 - - 6.6.5 Insecure Maintenance APIs.....39 - - 6.6.6 Third-party Libraries and Dependencies.....39 -- 6.7 Transfer Learning Attack (ML07:2023) .....40 - - 6.7.1 Data Poisoning for Transfer Learning.....40 - - 6.7.2 Model Stealing for Transfer Learning.....40 - - 6.7.3 Adversarial Examples.....41 - - 6.7.4 Backdoor for Transfer Learning.....41 -- 6.8 Model Skewing (ML08:2023).....42 - - 6.8.1 Data manipulation for Model Skewing .....42 - - 6.8.2 Feedback manipulation for Model Skewing.....42 -- 6.9 Output Integrity Attack (ML09:2023).....42 - - 6.9.1 Denial of Service Impacting Output Integrity .....42 - - 6.9.2 Subscriber QoE Change .....43 -- 6.10 Model Poisoning (ML10:2023).....43 - - 6.10.1 Model Parameter Poisoning .....43 - - 6.10.2 Inference Algorithm Poisoning .....44 - - 6.10.3 Learning Algorithm Poisoning .....44 - - 6.10.4 Model Control .....44 -- 6.11 Evasion attacks.....45 - - 6.11.1 Grey-box based Data Evasion .....45 - - 6.11.2 White box evasion attack.....45 - - 6.11.3 Black box evasion attack.....45 -- 6.12 AI Energy-Latency Attack .....46 - - 6.12.1 Model Extraction.....46 - - 6.12.2 Data Inference.....46 - - 6.12.3 Denial of Service via Side Channels.....47 -- 7 Security Controls.....48 -- 8 Risk Assessment .....52 - - 8.1 Introduction .....52 - - 8.2 Input Manipulation Attack (ML01:2023) .....52 - - 8.3 Data poisoning attacks (ML02:2023).....53 - - 8.4 Model Inversion Attack (ML03:2023).....53 - - 8.5 Membership Inference Attack (ML04:2023).....54 - - 8.6 Model Stealing (ML05:2023).....54 - - 8.7 AI Supply Chain Attacks (ML06:2023).....55 - - 8.8 Transfer Learning Attack (ML07:2023) .....56 - - 8.9 Model Skewing (ML08:2023).....57 - - 8.10 Output Integrity Attack (ML09:2023).....57 - - 8.11 Model Poisoning (ML10:2023).....57 - - 8.12 Evasion attacks.....58 - - 8.13 AI Energy-Latency Attack .....59 -- 9 Primary Issues .....60 -- 10 Recommendations .....61 - - 10.1 General .....61 - - 10.2 Managing Risk .....61 - - 10.3 Security Controls to be addressed in normative specification .....61 - -| | | -|-----------------------------------------------------------------|----| -| Annex A (informative): Attack Mapping to NIST AML Taxonomy..... | 63 | -| Annex: Change history/Change request (history) ..... | 65 | - -# List of Tables - -| | | -|----------------------------------------------------------------------------------------|----| -| Table 4.1-1 O-RAN Elements that Contain ML Models by Deployment Scenario ..... | 16 | -| Table 5.3-1 ETSI Identified ML Threats by O-RAN AI/ML General Procedure Component..... | 21 | -| Table 5.3-2 ML Attacks Mapped to O-RAN AI/ML Hosts by Deployment Scenario ..... | 22 | -| Table 8.2-1 AI/ML Risk Analysis – Input Manipulation Attack..... | 52 | -| Table 8.3-1 AI/ML Risk Analysis - Data poisoning attacks..... | 53 | -| Table 8.4-1 AI/ML Risk Analysis – Model Inversion Attack..... | 53 | -| Table 8.5-1 AI/ML Risk Analysis - Membership Inference Attacks..... | 54 | -| Table 8.6-1 AI/ML Risk Analysis – Model Stealing ..... | 54 | -| Table 8.7-1 AI/ML Risk Analysis - AI Supply Chain Attacks..... | 55 | -| Table 8.8-1 AI/ML Risk Analysis - Transfer Learning Attack..... | 56 | -| Table 8.9-1 AI/ML Risk Analysis - Model Skewing Attacks..... | 57 | -| Table 8.10-1 AI/ML Risk Analysis – Output Integrity attacks..... | 57 | -| Table 8.11-1 AI/ML Risk Analysis – Model Poisoning Attacks..... | 57 | -| Table 8.12-1 AI/ML Risk Analysis - Evasion attacks ..... | 58 | -| Table 8.13-1 AI/ML Risk Analysis - AI Energy-Latency Attack..... | 59 | -| Table A-1. Mapping of AI/ML TR attacks with NIST AML Taxonomy of attacks..... | 63 | - -# List of Figures - -| | | -|------------------------------------------------------------------------------------------------------------------|----| -| Figure 4.1-1: AI/ML General Procedure [Figure 4.1 in [i.14]]..... | 14 | -| Figure 4.1-2: Deployment scenario 1.1 — AI/ML training and inference host locations [Figure 5.1 in [i.14]] ..... | 15 | -| Figure 4.1-3: Deployment scenario 1.2 — AI/ML training and inference host locations [Figure 5.2 in [i.14]] ..... | 15 | -| Figure 4.1-4: Deployment scenario 1.3 - AI/ML training and inference host locations [Figure 5.3 in [i.14]] ..... | 16 | -| Figure 4.1-5: Deployment scenario 1.4 – AI/ML training and inference host locations [Figure 5.4 in [i.14]] ..... | 16 | - -# Foreword - -This Technical Report (TR) has been produced by WG11 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 the threat model and risk assessment for AI/ML in O-RAN. The report identifies threats and risks and recommends potential security controls to protect against those threats through safeguards or mitigations. - -The steps of the threat modelling process are as follows: - -1. Identify assets: Identify the assets of AI/ML that must be protected. -2. Identify threats: Identify the threats that could adversely impact AI/ML and threats that can use AI/ML to adversely impact other components of O-RAN. -3. Identify the attack surface and attack vectors: Identify the points of attack in AI/ML where an attacker could: - - a. gain access to AI/ML assets. - - b. gain entry to another O-RAN system through AI/ML - - c. exploit a vulnerability or misconfiguration in AI/ML - - d. compromise AI/ML data or other AI/ML assets. -4. Measure risk: The extent to which confidentiality, integrity, or availability is threatened, based upon a risk-based analysis considering the impact level resulting from an attack and the likelihood of occurrence. -5. Recommend controls: The management, operational, and technical controls for an information system to protect the confidentiality, integrity and availability of AI/ML. - -This Technical Report makes the following considerations: - -1. The attack surface of the AI/ML includes its interfaces, functions, and data. Data-at-rest, Data-in-motion, and Data-in-use must be considered. -2. The O-RAN Alliance is pursuing a zero-trust architecture (ZTA) for its specifications based upon NIST SP 800-207 [i.8]. This will affect the risk scoring and selection of security controls for internal and external threats. -3. Security controls are recommended for specifications of AI/ML. The recommended controls provided in this report will be shared with the responsible O-RAN Alliance working group, such as WG1, WG2, WG3, WG10, and nGRG so that the appropriate specifications relevant to the recommendation can be updated. - -# 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] O-RAN.WG1.TS.OAD: “O-RAN Architecture Description”. -- [i.2] O-RAN.WG11.TS.SRCS: “O-RAN Security Requirements and Controls Specifications”. -- [i.3] O-RAN.WG11.TS.SecProtSpec: “O-RAN Security Protocols Specifications”. -- [i.4] O-RAN.WG11.TR.Threat-Modeling: “O-RAN Security Threat Modeling and Risk Assessment”. -- [i.5] O-RAN.WG11.TS.STS: “O-RAN Security Test Specification”. -- [i.6] O-RAN.WG2.TS.Non-RT-RIC-ARCH: “Non-RT RIC Architecture”. -- [i.7] Edan Habler et al: “Adversarial Machine Learning (AML) Threat Analysis and Remediation in Open Radio Access Network (O-RAN)”, . -- [i.8] NIST Special Publication 800-207 “Zero Trust Architecture”, August 2020, . -- [i.9] NIST AI 100-2e2023 Adversarial Machine Learning: A Taxonomy and Terminology of Attacks and Mitigations, draft white paper, US DoC NIST January 2024. -- [i.10] NIST AI 100-1: Artificial Intelligence Risk Management Framework (AI RMF), January 2023. . -- [i.11] US National Security Agency (NSA) / Cybersecurity and Infrastructure Security Agency (CISA), Security Guidance for 5G Cloud Infrastructures, Part I, Oct 28, 2021, Part II, Nov 18, 2021, Part III, Dec 2, 2021, Part IV, Dec 16, 2021. , last visited April 24, 2023. -- [i.12] ISO/IEC 27001: 2013 Information Security Management System (ISMS). -- [i.13] MITRE ATLAS, MITRE, [MITRE | ATLASM](#), last visited April 24, 2023. -- [i.14] O-RAN.WG2.AIML: “AI/ML workflow description and requirements”. -- [i.15] Threat Intelligence Report 2023: . -- [i.16] Florian Tramèr et al: “Stealing Machine Learning Models via Prediction APIs.”, . - -- [i.17] Matt Fredrikson et al: “Model Inversion Attacks that Exploit Confidence Information and Basic Countermeasures“, CCS '15: Proceedings of the 22nd ACM SIGSAC Conference on Computer and Communications Security October 2015 Pages 1322–1333, . -- [i.18] Shokri, Reza, Marco Stronati, and Congzheng Song. "Membership inference attacks against machine learning models.", proceedings of the IEEE Symposium on Security and Privacy, 2017, . -- [i.19] ENISA: “Securing Machine Learning Algorithms”; . -- [i.20] OWASP Top 10 Machine Learning Security risks, 2023 . -- [i.21] 3GPP TR 21.905: “Vocabulary for 3GPP Specifications”. -- [i.22] O-RAN.WG11.TR.O-CLOUD-Security: “Study on Security for O-Cloud”. -- [i.23] O-RAN.WG3.TS.E2GAP: “E2 General Aspects and Principles (E2GAP)”. -- [i.24] OWASP Top 10 Proactive Controls, 2021, . -- [i.25] Center for Internet Security (CIS) Critical Security Controls, . -- [i.26] Cloud Security Alliance (CSA) Cloud Control Matrix (CCM), -- [i.27] Void. -- [i.28] NIST SP 800-53r5, Security and Privacy Controls for Information Systems and Organizations, 2020. -- [i.29] US National Security Agency (NSA) / Cybersecurity and Infrastructure Security Agency (CISA), Security Guidance for 5G Cloud Infrastructures, Part I, Oct 28, 2021, Part II, Nov 18, 2021, Part III, Dec 2, 2021, Part IV, Dec 16, 2021. (as of Feb 28, 2022). -- [i.30] Principal Component Analysis, Wikipedia, [https://en.wikipedia.org/wiki/Principal\\_component\\_analysis](https://en.wikipedia.org/wiki/Principal_component_analysis). -- [i.31] Linear discriminant analysis for dimensionality reduction: [https://rasbt.github.io/mlxtend/user\\_guide/feature\\_extraction/LinearDiscriminantAnalysis/](https://rasbt.github.io/mlxtend/user_guide/feature_extraction/LinearDiscriminantAnalysis/). -- [i.32] Machine Learning Standardization (Z-Score Normalization) with Mathematics, Towards AI; . -- [i.33] Voting Classifiers in Machine Learning: . -- [i.34] Stacking in Machine Learning: . -- [i.35] LIME: . -- [i.36] SHAP: . - -- [i.37] NIST blog: “How to deploy machine learning with differential privacy”; . -- [i.38] Peter Darveau P. Eng., „Using Enclaves and Model Splitting to Improve AI Application Security in High Performance Computing – Thinking Beyond the Network“; . -- [i.39] Andrew Marshall, Jugal Parikh, Emre Kiciman and Ram Shankar Siva Kumar: “Threat Modeling AI/ML Systems and Dependencies”; . -- [i.40] BSI: “AI SECURITY CONCERNS IN A NUTSHELL”; [https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/KI/Practical\\_AI-Security\\_Guide\\_2023.pdf?\\_\\_blob=publicationFile&v=5](https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/KI/Practical_AI-Security_Guide_2023.pdf?__blob=publicationFile&v=5). -- [i.41] ENISA: “Artificial Intelligence Cybersecurity Challenges”; . -- [i.42] TOWARDS AI: “Machine Learning Standardization (Z-Score Normalization) with Mathematics”; . -- [i.43] Xinyu Tang et al, “Mitigating Membership Inference Attacks by Self-Distillation Through a Novel Ensemble Architecture”; [https://www.usenix.org/system/files/sec22fall\\_tang.pdf](https://www.usenix.org/system/files/sec22fall_tang.pdf). -- [i.44] Ismat Jarin, Birhanu Eshete, “PRICURE: Privacy-Preserving Collaborative Inference in a Multi-Party Setting”; . -- [i.45] BSI: Security of AI-Systems: Fundamentals: Adversarial Deep Learning; [https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/KI/Security-of-AI-systems\\_fundamentals.pdf?\\_\\_blob=publicationFile&v=4](https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/KI/Security-of-AI-systems_fundamentals.pdf?__blob=publicationFile&v=4). -- [i.46] Pramoditha, R.: “Parameters Vs Hyperparameters: What is the difference?”, Medium web article, April 7, 2022. Retrieved from . -- [i.47] O-RAN.WG1.TR.Use-Cases-Analysis-Report: “Use Cases Analysis Report”. -- [i.48] Casey, Cindy: “AI Poisoning Attacks”, lecture slides, 2022, Retrieved from . -- [i.49] ETSI GR SAI 004 v1.1.1: “Securing Artificial Intelligence (SAI); Problem Statement”, December 2020. -- [i.50] Output Integrity Attack, [https://owasp.org/www-project-machine-learning-security-top-10/docs/ML09\\_2023-Output\\_Integrity\\_Attack](https://owasp.org/www-project-machine-learning-security-top-10/docs/ML09_2023-Output_Integrity_Attack). -- [i.51] HONGSHENG HU et al: “Membership Inference Attacks on Machine Learning: A Survey”, ACM Computing Surveys, Vol. 54, No. 11s, Article 235. Publication date: September 2022, . -- [i.52] Jiayuan Ye et al: “Enhanced Membership Inference Attacks against Machine Learning Models”, . -- [i.53] Trent, Rod. “Must Learn AI Security Part 6: Model Inversion Attacks Against AI.”, . - -- [i.54] Tramèr et al, “The Space of Transferable Adversarial Examples”, arXiv:1704.03453, . -- [i.55] Mohamad Fazelnia et al: “Supporting Artificial Intelligence/Machine Learning Security Workers Through an Adversarial Techniques, Tools, and Common Knowledge Framework”, IEEE Security & Privacy (Volume: 21, Issue: 1, Jan.-Feb. 2023); DOI: 10.1109/MSEC.2022.3221058. -- [i.56] NIST Privacy Framework; . -- [i.57] General Data Protection Regulation, Regulation (EU) 2016/679, version OJ L 119, 04.05.2016; cor. OJ L 127, 23.5.2018, Art. 25: “Data protection by design and by default “; . -- [i.58] ISO/IEC WD 27091, Cybersecurity and Privacy, Artificial Intelligence, Privacy protection: . -- [i.59] ITU-T TR XSTR-SEC-AI: “Guidelines for security management of using artificial intelligence technology”; [https://www.itu.int/dms\\_pub/itu-t/opb/tut/T-TUT-ICTS-2022-PDF-E.pdf](https://www.itu.int/dms_pub/itu-t/opb/tut/T-TUT-ICTS-2022-PDF-E.pdf). -- [i.60] Yangsong Gao, et al, “STRIP: A Defence Against Trojan Attacks on Deep Neural Networks”, January 17, 2020, . -- [i.61] Sponge Examples: Energy-Latency Attacks on Neural Networks; . -- [i.62] I Know What You See: Power Side-Channel Attack on Convolutional Neural Network Accelerators; . -- [i.63] Stealing Neural Networks via Timing Side Channels; . -- [i.64] Xiaobei Yan et al, Defense against ML-based Power Side-channel Attacks on DNN Accelerators with Adversarial Attacks; . -- [i.65] Adi et al., "Turning Your Weakness Into a Strength: Watermarking Deep Neural Networks by Backdooring", -- [i.66] Uchida et al., "Embedding Watermarks into Deep Neural Networks", -- [i.67] Le Merrer et al., "Adversarial Frontier Stitching for Remote Neural Network Watermarking", -- [i.68] Szyller et al., "DAWN: Dynamic Adversarial Watermarking of Neural Networks" -- [i.69] Rouhani et al., "DeepSigns: A Generic Watermarking Framework for IP Protection of Deep Learning Models", -- [i.70] EU AI Act, [https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L\\_202401689](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202401689) -- [i.71] O-RAN.WG2.TS.A1GAP: “AI interface: General Aspects and Principles”. - -# 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -This document uses the verbal forms for the expression of provisions as defined in Study on Security for O-Cloud [i.22]. - -This document uses the term Zero Trust Architecture (ZTA) as defined by US NIST in [i.8], and applied to 5G cloud deployments by US CISA in [i.9]. - -A ZTA provides protection from external and internal threats, assuming the following: - -1. there is no implicit trust granted to an asset based upon ownership, physical location, or network location [i.8] -2. the adversary is already inside the network. Perimeter defences are no longer sufficient to secure a network, and there should always be an assumption that a threat actor has established a foothold in the network [i.9] - -This document uses the term “attack surface” defined by US NIST as - -*The set of points on the boundary of a system, a system element, or an environment where an attacker can try to enter, cause an effect on, or extract data from, that system, system element, or environment* -[\[https://csrc.nist.gov/glossary/term/attack\\_surface\]](https://csrc.nist.gov/glossary/term/attack_surface) - -This document refers to “sensitive information” defined by US NIST as - -*information whose loss, misuse, or unauthorized access or modification could adversely affect security* -[\[https://csrc.nist.gov/glossary/term/sensitive\]](https://csrc.nist.gov/glossary/term/sensitive) - -For the purposes of the present document, the terms and definitions provided in [i.1] apply: - -**Data Wrangling:** The process of converting raw data into a usable form. Data wrangling is called data preparation in [i.14]. - -**Denial of Features Attack:** refers to a type of attack where an attacker, with full or partial knowledge of feature weightings or saliency measures in unsupervised learning systems, manipulates feature values to render salient features unavailable. This is achieved by reversing the weights, thereby disrupting the system's functionality [i.49]. - -**Hyperparameter:** In machine learning, hyperparameters are variables that specify how a model is trained and are external to the model. These values are set manually and remained fixed during the model training process. They are independent from the training data [i.46]. - -**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. It may include AI/ML (Artificial Intelligence / Machine Learning) workflow including model training, inference and updates. - -**Non-RT RIC Applications (rApps):** Modular applications that leverage the functionality exposed via the Non-RT RIC Framework's R1 interface to provide added value services relative to RAN operation, such as driving the A1 interface, recommending values and actions that may be subsequently applied over the O1/O2 interface and generating “enrichment information” for the use of other rApps. The rApp functionality within the Non-RT RIC enables non-real-time control and optimization of RAN elements and resources and policy-based guidance to the applications/features in Near-RT RIC. - -**Non-RT RIC Framework:** That functionality internal to the SMO that logically terminates the A1 interface to the Near-RT RIC and exposes to rApps, via its R1 interface, the set of internal SMO services needed for their runtime processing. The Non-RT RIC Framework functionality within the Non-RT RIC provides AI/ML workflow including model training, inference and updates needed for rApps. - -**Parameters:** In machine learning, parameters are variables that the model uses to make predictions and are internal to the model. The values are set through an interaction of the training algorithm and training data. The parameters are dependent on the data they are trained with [i.46]. - -**SMO:** Service Management and Orchestration system. For more details please refer to Clause 5.3.1 of [i.1]. - -**xApp:** An application designed to run on the Near-RT RIC. Such an application is likely to consist of one or more microservices and at the point of on-boarding will identify which data it consumes and which data it provides. The application is independent of the Near-RT RIC and may be provided by any third party. The E2 enables a direct association between the xApp and the RAN functionality [i.23]. - -## 3.2 Symbols - -Void. - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [i.21], and the following apply: - -| | | -|------|-------------------------------------------------| -| AI | Artificial Intelligence | -| AML | Adversarial Machine Learning | -| DAR | Data at Rest | -| DIM | Data in Motion | -| DIU | Data in Use | -| LDA | Linear discriminant analysis, [i.31] | -| LIME | Local Interpretable Model-agnostic Explanations | -| ML | Machine Learning | -| MNO | Mobile Network Operator | -| NF | Network Function | -| PCA | Principal Component Analysis, [i.30] | -| RIC | RAN Intelligent Controller | -| RT | Real-Time | -| SHAP | SHapley Additive exPlanations | -| SMO | Service Management and Orchestration | -| SMPC | Secure Multi-Party Computation | -| TEE | Trusted Execution Environment | -| ZTA | Zero Trust Architecture | - -# 4 AI/ML Assets - -## 4.1 Introduction - -Artificial Intelligence and Machine Learning (AI/ML) are core to optimizing the operation of O-RAN. The primary goal of the Non-RT RIC is to support intelligent RAN optimization by providing policy-based guidance, ML model management and enrichment information to the Near-RT RIC function. It can also perform intelligent radio resource management function within a non-real-time interval (i.e., greater than 1 second). The Non-RT RIC can use data analytics and AI/ML training/inference to determine the RAN optimization actions for which it can leverage SMO services such as data collection and provisioning services of the O-RAN nodes as well as the O1 and O2 interfaces. The AI/ML capabilities in the Non-RT RIC are provided by rApps. Similarly, the near-Real-Time RAN Intelligent Controller may use AI/ML to provide near-real-time control and optimization of RAN elements and resources via fine-grained data collection and actions over E2 interface. The Near-RT RIC capabilities are provided by xApps [i.1]. - -The affected assets are derived from the AI/ML General Lifecycle Procedure and Interface Framework, and deployment scenarios in [i.14]. - -![AI/ML General Procedure flowchart showing the lifecycle from Data Collection to AI/ML Assisted Solution and its subsequent actions.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) - -``` - - graph TD - subgraph Data_Sources [Data Sources] - DC[Data Collection] - DC --- O1A1E2_1[O1/A1/E2] - DC --- Data_1[Data] - DC --- OCUODU[O-CU/O-DU -Near-RT RIC -Non-RT RIC -Data collector] - end - - DC -- Data --> DP[Data Preparation] - DP -- "AI/ML Training data" --> AT[AI/ML Training] - AT -- "Model Certification/ -On-boarding" --> AMM[AI/ML Model Management] - AMM -- "Model Deployment/Termination" --> AI[AI/ML Inference] - DP -- "AI/ML Inference Data" --> AI - AI -- "verification/monitoring" --> AMCO[AI/ML Continuous Operation] - AMCO -- "ML performance feedback" --> AI - AMCO -- "guide/feedback" --> AMM - AMCO -- "Data" --> OCUODU_2[O-CU/O-DU -Near-RT RIC -Non-RT RIC -Data collector] - AMCO -- "ML performance feedback" --> O1A1E2_2[O1/A1/E2] - - AI --> AMS[AI/ML Assisted Solution] - AMS -- "Actor" --> Action - Action --> CM[Config mang. over O1] - Action --> CA[Control Action/Guidance over E2] - Action --> P[Policy over A1,E2] - - CM --- S1[Subject of actions: -near-RT RIC,O-CU,O-DU/O-RU] - CA --- S2[Subject of actions: -O-CU,O-DU/O-RU] - P --- S3[Subject of actions: -near-RT RIC,O-CU,O-DU/O-RU] - -``` - -AI/ML General Procedure flowchart showing the lifecycle from Data Collection to AI/ML Assisted Solution and its subsequent actions. - -Figure 4.1-1: AI/ML General Procedure [Figure 4.1 in [i.14]] - -The assets are also derived from the figures describing the deployment models in Clause 5 of [i.14]. These figures are included below. - -Case 1.1 AI/ML Continuous Operation/AI/ML Model Management/Data Preparation/AI/ML Training and AI/ML Inference are all in Non-RT RIC. - -O-DU/O-CU - -![Figure 4.1-2: Deployment scenario 1.1 — AI/ML training and inference host locations. This diagram shows the flow of data and control within an SMO and a Near-RT RIC. The SMO contains a Non-RT RIC where Data Collection (1) receives 'Data' from the O-DU/O-CU. This data is processed through Data Preparation (2), AI/ML Training (3), and AI/ML Model Management (4). AI/ML Training sends 'AI/ML Training Data' to Data Preparation and 'Model Certification On-boarding' to AI/ML Model Management. AI/ML Model Management sends 'Model Deployment Termination' and 'guide feedback' to AI/ML Continuous Operation (6). AI/ML Continuous Operation sends 'ML performance feedback' to AI/ML Inference (5). AI/ML Inference sends 'AI/ML Inference Data' to Data Preparation. Finally, the SMO sends 'Config Mgmt if DU or CU is subject of action' (7) to the Near-RT RIC, which in turn sends 'Policy/intent if near-RT RIC is subject of action' (7) back to the SMO.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) - -Figure 4.1-2: Deployment scenario 1.1 — AI/ML training and inference host locations. This diagram shows the flow of data and control within an SMO and a Near-RT RIC. The SMO contains a Non-RT RIC where Data Collection (1) receives 'Data' from the O-DU/O-CU. This data is processed through Data Preparation (2), AI/ML Training (3), and AI/ML Model Management (4). AI/ML Training sends 'AI/ML Training Data' to Data Preparation and 'Model Certification On-boarding' to AI/ML Model Management. AI/ML Model Management sends 'Model Deployment Termination' and 'guide feedback' to AI/ML Continuous Operation (6). AI/ML Continuous Operation sends 'ML performance feedback' to AI/ML Inference (5). AI/ML Inference sends 'AI/ML Inference Data' to Data Preparation. Finally, the SMO sends 'Config Mgmt if DU or CU is subject of action' (7) to the Near-RT RIC, which in turn sends 'Policy/intent if near-RT RIC is subject of action' (7) back to the SMO. - -Figure 4.1-2: Deployment scenario 1.1 — AI/ML training and inference host locations [Figure 5.1 in [i.14]] - -Case 1.2 AI/ML Continuous Operation/ Data Preparation(for training)/AI/ML Training are in Non-RT RIC -AI/ML Model Management is out of Non-RT RIC(in or out of SMO). -Data Collection(for inference)/Data Preparation(for inference)/AI/ML Inference is in Near-RT RIC. - -O-DU/O-CU - -![Figure 4.1-3: Deployment scenario 1.2 — AI/ML training and inference host locations. This diagram shows a more distributed deployment. The SMO contains a Non-RT RIC with Data Collection (1) receiving 'ML Training info' from the O-DU/O-CU. This data is processed through Data Preparation (2), AI/ML Training (3), and AI/ML Model Management (4). AI/ML Training sends 'AI/ML Training Data' to Data Preparation and 'Model Certification/On-boarding' to AI/ML Model Management. AI/ML Model Management sends 'Model Deployment/Termination' and 'guide/feedback' to AI/ML Continuous Operation (6). AI/ML Continuous Operation sends 'ML performance feedback' to AI/ML Inference (7). AI/ML Inference sends 'AI/ML Inference Data' to Data Preparation. The SMO also sends 'AI/ML Online info' (5) to the Near-RT RIC. The Near-RT RIC contains Data Collection (5), Data Preparation (6), and AI/ML Inference (7). Finally, the SMO sends 'Control action/guidance over E2' (8) to the O-DU/O-CU.](c67d21fb3d9042e88cdc669f071b4e7c_img.jpg) - -Figure 4.1-3: Deployment scenario 1.2 — AI/ML training and inference host locations. This diagram shows a more distributed deployment. The SMO contains a Non-RT RIC with Data Collection (1) receiving 'ML Training info' from the O-DU/O-CU. This data is processed through Data Preparation (2), AI/ML Training (3), and AI/ML Model Management (4). AI/ML Training sends 'AI/ML Training Data' to Data Preparation and 'Model Certification/On-boarding' to AI/ML Model Management. AI/ML Model Management sends 'Model Deployment/Termination' and 'guide/feedback' to AI/ML Continuous Operation (6). AI/ML Continuous Operation sends 'ML performance feedback' to AI/ML Inference (7). AI/ML Inference sends 'AI/ML Inference Data' to Data Preparation. The SMO also sends 'AI/ML Online info' (5) to the Near-RT RIC. The Near-RT RIC contains Data Collection (5), Data Preparation (6), and AI/ML Inference (7). Finally, the SMO sends 'Control action/guidance over E2' (8) to the O-DU/O-CU. - -Figure 4.1-3: Deployment scenario 1.2 — AI/ML training and inference host locations [Figure 5.2 in [i.14]] - -Case 1.3 AI/ML Continuous Operation/AI/ML Inference are in Non-RT RIC. Data Preparation/AI/ML Training/AI/ML Model Management are out of Non-RT RIC(in or out of SMO). - -![Figure 4.1-4: Deployment scenario 1.3 - AI/ML training and inference host locations. The diagram shows the flow of data and control within an SMO and Non-RT RIC. O-DU/O-CU provides ML Training info (O1) to the SMO. Inside the SMO, steps 1-4 (Data Collection, Data Preparation, AI/ML Training, AI/ML Model Management) occur. Step 5 (AI/ML Inference Data) goes from the SMO to the Non-RT RIC. Inside the Non-RT RIC, step 6 (AI/ML Inference) and step 7 (AI/ML Continuous Operation) occur, with verification/monitoring and ML performance feedback loops. Step 7 also connects to the Near-RT RIC via A1 interface as Policy/intent if near-RT RIC is subject of action. Step 7 also connects back to O-DU/O-CU via O1 interface as Config Mgmt if DU or CU is subject of action.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) - -Figure 4.1-4: Deployment scenario 1.3 - AI/ML training and inference host locations. The diagram shows the flow of data and control within an SMO and Non-RT RIC. O-DU/O-CU provides ML Training info (O1) to the SMO. Inside the SMO, steps 1-4 (Data Collection, Data Preparation, AI/ML Training, AI/ML Model Management) occur. Step 5 (AI/ML Inference Data) goes from the SMO to the Non-RT RIC. Inside the Non-RT RIC, step 6 (AI/ML Inference) and step 7 (AI/ML Continuous Operation) occur, with verification/monitoring and ML performance feedback loops. Step 7 also connects to the Near-RT RIC via A1 interface as Policy/intent if near-RT RIC is subject of action. Step 7 also connects back to O-DU/O-CU via O1 interface as Config Mgmt if DU or CU is subject of action. - -Figure 4.1-4: Deployment scenario 1.3 - AI/ML training and inference host locations [Figure 5.3 in [i.14]] - -![Figure 4.1-5: Deployment scenario 1.4 – AI/ML training and inference host locations. The diagram shows data flow between O-CU/O-DU, SMO/Non-RT RIC, and Near-RT RIC. O-CU/O-DU provides offline training data (O1), online learning data (E2), and inference data (E2). In the SMO/Non-RT RIC, ML Training and ML model repository are shown. In the Near-RT RIC, ML Training, ML Inference, and ML model repository are shown. Arrows indicate 'Download model' (SMO to Near-RT RIC), 'Model update' (Near-RT RIC to SMO), 'ML Deploy' (Near-RT RIC ML Training to ML Inference), and 'Performance feedback' (ML Inference to ML Training). The Near-RT RIC also sends 'Control action/guidance (E2)' back to the O-CU/O-DU. The O1/A1 interface is indicated between the SMO and Near-RT RIC.](a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg) - -Figure 4.1-5: Deployment scenario 1.4 – AI/ML training and inference host locations. The diagram shows data flow between O-CU/O-DU, SMO/Non-RT RIC, and Near-RT RIC. O-CU/O-DU provides offline training data (O1), online learning data (E2), and inference data (E2). In the SMO/Non-RT RIC, ML Training and ML model repository are shown. In the Near-RT RIC, ML Training, ML Inference, and ML model repository are shown. Arrows indicate 'Download model' (SMO to Near-RT RIC), 'Model update' (Near-RT RIC to SMO), 'ML Deploy' (Near-RT RIC ML Training to ML Inference), and 'Performance feedback' (ML Inference to ML Training). The Near-RT RIC also sends 'Control action/guidance (E2)' back to the O-CU/O-DU. The O1/A1 interface is indicated between the SMO and Near-RT RIC. - -Figure 4.1-5: Deployment scenario 1.4 – AI/ML training and inference host locations [Figure 5.4 in [i.14]] - -Successful exploitation of threats against the AI/ML or intentionally malicious x/rApps used by the non- and Near-RT RICs can impact the O-RAN assets listed in the clauses below. Where an asset name is listed is an indication that this asset has been identified in the O-RAN Security Threat Modelling and Risk Assessment Technical Report [i.4]. - -The following table further identifies O-RAN elements that host models per deployment scenarios. - -Table 4.1-1 O-RAN Elements that Contain ML Models by Deployment Scenario - -| Deployment Scenario | Initial Models | Trained Models | | -|---------------------|------------------------------------------------------------------|----------------------|-------------------------------| -| | AI/ML Training Host | AI/ML Inference Host | AI/ML Model Management Host | -| 1.1 | Non-RT RIC | Non-RT RIC | Non-RT RIC | -| 1.2 | Non-RT RIC | Near-RT RIC | Out of Non-RT RIC | -| 1.3 | Out of Non-RT RIC | Non-RT RIC | Out of Non-RT RIC | -| 1.4 | Offline training: SMO/Non-RT RIC
Online learning: Near-RT RIC | Near-RT RIC | Non-RT RIC and
Near-RT RIC | - -| | | | | -|-----|------------|-------------|------------| -| 1.5 | Non-RT RIC | O-CU / O-DU | Non-RT RIC | -|-----|------------|-------------|------------| - -**NOTE: from [i.14]the phrase “Out of Non-RT RIC” appears to indicate it could either reside in the SMO but not in the Non-RT RIC or resides outside the SMO.** - -## 4.2 Functions - -- [ASSET-C-02]: Near-RT RIC. -- [ASSET-C-03]: O-CU-CP. -- [ASSET-C-04]: O-CU-UP. -- [ASSET-C-05]: O-DU. -- [ASSET-C-07]: O-eNB. -- [ASSET-C-11]: Non-RT RIC. -- [ASSET-C-12]: ML components deploying machine learning such as: ML training and interference hosts, ML applications (xApps, rApps). -- [ASSET-C-29]: AAL software including software, libraries, drivers, etc. -- [ASSET-C-30]: The hardware accelerator device firmware -- [ASSET-C-61]: AI/ML Workflow. - -## 4.3 Interfaces - -- [ASSET-C-14]: A1 interface, including protocol stack. -- [ASSET-C-22]: O1, including protocol stack. -- [ASSET-C-40]: E2 interface, including protocol stack. - -## 4.4 Data - -- [ASSET-D-07]: A1 policies that are provided to the Near-RT RIC over the A1 interface to guide the RAN performance towards the overall goal expressed in RAN Intent. The A1 policies are declarative policies that contain statements on policy objectives and policy resources applicable to UEs and cells. A1 policies are created, modified and deleted by the Non-RT RIC. -- [ASSET-D-08]: A1 Enrichment Information that is collected or derived at SMO/Non-RT RIC either from non-network data sources or from network functions themselves and provided over the A1 interface to be utilized by Near-RT RIC, e.g. an ML model, to improve its performance. Discovery and request of A1 Enrichment Information from Near-RT RIC to Non-RT RIC. External Enrichment Information that is provided by an O-RAN external information source to Near-RT RIC over A1. -- [ASSET-D-09]: Data transported over the E2 interface such as near real-time information (e.g. UE basis, 2Cell basis), the persistent configuration used by the Near-RT RIC to control the RAN, identifiers of E2 nodes, xApp- - -related messages, control signalling information, policies used by the Near-RT RIC to monitor, suspend/stop, override or control the behaviour of E2 node, Near-RT RIC services messages (REPORT, INSERT, CONTROL and POLICY), interface management messages (E2 Setup, E2 Reset, E2 Node Configuration Update, Reporting of General Error Situations), Near-RT RIC Service Update messages. - -- [ASSET-D-10]: Database holding data from xApp applications and E2 Node. -- [ASSET-D-11]: E2 Node data (e.g. configuration information (cell configuration, supported slices, PLMNs, etc.), network measurements, context information, etc.) -- [ASSET-D-25]: Training or test data and associated labels: data sets collected externally or internally from the Near-RT RIC, O-CU and O-DU and passed to the ML training hosts in a ML system. -- [ASSET-D-29]: Security event log files generated by Non-RT RIC, rApps, Near-RT RIC, and xApps. - -## 4.5 Models - -- [ASSET-D-26]: The trained ML model which includes the configured hyperparameters, inference algorithm, and learned parameters. -- [ASSET-D-27]: The ML prediction results built into the model (e.g. expected outcomes). -- [ASSET-D-40]: ML models that have not been trained yet, i.e., Initial Models and their associated learning algorithm. - -## 4.6 Pipeline - -- [ASSET-D-28]: The behaviour of the ML system including tasks for data collection, data wrangling, pipeline management, model retraining, and model deployment. - -# 5 Threats - -## 5.1 Threat Model - -For identifying threats, we are using STRIDE: - -1. S - Spoofing identity. An application or program can masquerade as another to gain advantages not typically allowed for that program. -2. T - Tampering with data. This involves the malicious modification of data, including making unauthorized changes to a database and alteration of data as it flows between computers. -3. R - Repudiation. A user or program refuses the authenticity of a good or reasonable command or action. -4. I - Information disclosure. This involves the exposure of information to individuals with unauthorized access to it. For example, users gain the ability to read a file that they normally would not have been granted access to, or an intruder can read data in transit between computers. -5. D - Denial of service. These attacks deny service to valid users, such as making a website unavailable or unusable by flooding it with illegitimate requests to keep legitimate users without access. -6. E - Elevation of privileges. An unauthorized user gains privileged rights to access previously no granted to compromise or destroy the system, such as a change in membership. - -| Threat types | Impact types | -|------------------------|-----------------| -| Spoofing | Authenticity | -| Tampering | Integrity | -| Repudiation | Non-repudiation | -| Information disclosure | Confidentiality | -| Denial of Service | Availability | -| Elevation of Privilege | Authorization | - -## 5.2 Threat Template - -Template to present the threat characteristics: - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------| -| Threat ID | | -| Threat title | | -| Threat description | | -| Threat type | Spoofing
Tampering
Repudiation
Information disclosure
Denial of Service
Elevation of Privilege | -| Vulnerabilities | | -| Impact type | Authenticity
Integrity
Non-repudiation
Confidentiality
Availability
Authorization | -| Affected Assets | | - -## 5.3 Potential Threats and Exploits - -### 5.3.1 Common Threats associated with ML - -The most common threats associated with machine learning are identified and summarized in the Top ten list by the Open Worldwide Application Security Project (OWASP) [i.20]. - -The OWASP Top 10 Security Risks of Machine Learning systems updated in 2023 includes: - -ML01:2023 Input Manipulation Attack - -ML02:2023 Data Poisoning Attack - -ML03:2023 Model Inversion Attack - -ML04:2023 Membership Inference Attack - -ML05:2023 Model Stealing - -ML06:2023 AI Supply Chain Attacks - -ML07:2023 Transfer Learning Attack - -ML08:2023 Model Skewing - -ML09:2023 Output Integrity Attack - -ML10:2023 Model Poisoning - -The AI/ML Threat analysis considers the threats listed above that are relevant to O-RAN AI/ML. - -When considering threats to machine learning in O-RAN it is necessary to consider where the threats might occur in the ML components as described in the AI/ML General Procedure (see Figure 1 and Figure 4-1 of [i.14]). In support of that we referenced the ETSI Group Report on “Securing Artificial Intelligence (SAI); Problem Statement” [i.49]. This ETSI document contains a table, labelled Table 1, that maps the AI/ML lifecycle phases to relevant attacks and what security issue they might cause. The attacks mentioned in the ETSI document are not directly referenced in the table, instead, they are referred to specific clauses. The issues identified by ETSI appear to map directly to the impact types of Confidentiality, Integrity, and Availability as outlined in the STRIDE model. [i.49] does not address the impact types of Authenticity, Non-Repudiation and Authorization. - -Drawing on the ETSI document, we have developed Table 5.3-1. This table maps the defined ETSI ML Lifecycle phases to the O-RAN AI/ML General Procedure Components as defined in [i.14]. Through this mapping, we can determine the relevance of the attacks and potential impacts identified by ETSI for each AI/ML component defined by O-RAN. In addition, the OWASP ML Security Top Ten Risks have been mapped to the equivalent ETSI threats in the OWASP ML SEC Top 10 column. It is worth noting that the Train phase and Upgrades phase of the ETSI Lifecycle are both mapped to the same O-RAN AI/ML General Procedure component, ML Training Host. This was done since the O-RAN training host encompasses both ETSI ML Lifecycle phases per [i.14]. - -The ETSI Lifecycle phases of Model Design and Software Build have been listed as “out of scope for O-RAN” as those activities will occur outside of the O-RAN architecture. ETSI defines an attack referred in the table as “untrusted devices”. ETSI calls this out as a model confidentiality issue if the model resides on a device that is not trusted. There is no equivalent OWASP attack and has been indicated in the table with the text “No Mapping”. Two OWASP attacks, ML05:2023 Model Theft and ML08:2023 Model Skewing have no equivalent mapping to ETSI relevant attacks. - -Table 5.3-1 ETSI Identified ML Threats by O-RAN AI/ML General Procedure Component - -| ETSI ML Lifecycle Phase [i.49] | O-RAN AI/ML General Procedure Component [i.14] | Issues [i.49] (Potential Impacts) | ETSI Relevant Attacks [i.49] | OWASP ML SEC Top 10 [i.20] | -|--------------------------------|-----------------------------------------------------|-----------------------------------|-------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| -| Data Acquisition | Data Preparation | Integrity | Poisoning of input data | ML01:2023 Input Manipulation Attack | -| Data Curation | | Integrity | Poisoning on data labelling for supervised learning | ML02:2023 Data Poisoning Attack | -| Model Design | Out of Scope for O-RAN | | | | -| Software Build | Out of Scope for O-RAN | | | | -| Train | ML Training Host (AI/ML Training) | Confidentiality | Training data leaked
Full Knowledge Attacks
Partial Knowledge Attacks
Zero Knowledge Attacks | ML02:2023 Data Poisoning Attack | -| | | Integrity | Transfer Learning Attack
Backdoor Attack
Modify Learning Algorithm | ML07:2023 Transfer Learning Attack
ML06:2023 AI Supply Chain Attacks
ML10:2023 Model Poisoning | -| | | Availability | Poisoning Attack at Input Layer
Denial of Features Attack | ML01:2023 Input Manipulation Attack
ML10:2023 Model Poisoning | -| Test | | Availability | Lack of testing for adversarial examples | ML01:2023 Input Manipulation Attack | -| Deployment | Model Management and ML Inference Host | Confidentiality | Backdoor
Membership Inference
Inversion Attacks
Untrusted Devices | ML06:2023 AI Supply Chain Attacks
ML04:2023 Membership Inference Attack
ML03:2023 Model Inversion Attack
No Mapping | -| | | Integrity | Input attack
Backdoor attack | ML01:2023 Input Manipulation Attack
ML06:2023: AI Supply Chain Attacks | -| | | Availability | Evasion Attacks | ML09:2023 Output Integrity Attack | -| Upgrades | ML Training Host (Optimization / Refinement) | Integrity | Backdoor attack during training phase then triggered by an update | ML06:2023 AI Supply Chain Attacks | -| | | Availability | Poisoning attack on model parameters | ML10:2023 Model Poisoning | - -#### **Note for Table 5.3-1:** - -- Although ETSI does not explicitly list the impact types of Authenticity, Non-Repudiation and Authorization, Authenticity and Authorization are controls used to enforce confidentiality, while non-repudiation is a control used to enforce integrity. -- The ETSI attack “untrusted devices” does not map to OWASP ML Security Top Ten. This does not cause an issue as this is out of scope for this technical report. -- The ETSI AI/ML phase of Deployment encompasses both the Model Management and ML Inference components. This causes a 1-to-many mapping which causes a challenge when mapping OWASP attacks to O-RAN AI/ML hosts by deployment scenario (see Table 5.3-2). -- ETSI AI/ML phases “Train” and “Upgrades” both map to the same O-RAN AI/ML General Procedure component, ML Training Host. This does not appear to cause an issue for the mapping in Table 5.3-2. -- The OWASP attacks, ML05:2023 Model Theft and ML08:2023 Model Skewing have no equivalent mapping to ETSI relevant attacks nor impact types. These attacks where mapped to appropriate AI/ML hosts in Table 5.3-2. - -Using the mapping completed in Table 5.3-1 the following table, Table 5.3-2, was developed by referencing Table 2 in [i.14]. - -Table 5.3-2 ML Attacks Mapped to O-RAN AI/ML Hosts by Deployment Scenario - -| | | Attacks by O-RAN AI/ML Host | | | | -|---|----------------------------------------------|-------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------| -| | | Data Preparation | ML Training Host | ML Inference | Model Management | -| | O-RAN Elements by Deployment Scenario | Input Manipulation
Data Poisoning
Model Skewing | Data Poisoning Attack
Transfer Learning Attack
AI Supply Chain Attacks
Model Poisoning
Input Manipulation Attack
Model Theft | AI Supply Chain Attacks
Membership Inference Attack
Model Inversion Attack
Input Manipulation Attack
Output Integrity Attack
Model Theft
Model Poisoning | AI Supply Chain Attacks
Model Theft
Model Poisoning | -| 1 | Non-RT RIC | X | X | X | X | -| | Near-RT RIC | | | | | -| | O-CU/O-DU | | | | | -| | Out of Non-RT RIC | | | | | -| 2 | Non-RT RIC | X | X | | | -| | Near-RT RIC | X | | X | | -| | O-CU/O-DU | | | | | -| | Out of Non-RT RIC | | | | X | -| 3 | Non-RT RIC | | | X | | -| | Near-RT RIC | | | X | | -| | O-CU/O-DU | | | | | -| | Out of Non-RT RIC | X | X | | X | -| 4 | Non-RT RIC | X | X | | X | -| | Near-RT RIC | X | X | X | X | -| | O-CU/O-DU | | | | | -| | Out of Non-RT RIC | | | | | -| 5 | Non-RT RIC | X | X | | X | -| | Near-RT RIC | | | | | -| | O-CU/O-DU | | | X | | -| | Out of Non-RT RIC | | | | | - -#### Notes for Table 5.3-2: - -- Model Poisoning was added to model management and ML inference host because the scope of what is included in a model poisoning attack was expanded in relation to [i.14]. -- The ETSI defined attack “untrusted devices” is out of scope for this technical report. -- The OWASP Model Skewing and Model Theft attacks were mapped where appropriate. -- “Out of Non-RT RIC” appears to indicate it could either reside in the SMO but not in the Non-RT RIC or resides outside the SMO [i.14]. - -### 5.3.2 Input Manipulation Attack (ML01:2023) - -#### 5.3.2.1 Introduction - -OWASP defines an input manipulation attack as a type of attack in which an attacker deliberately alters input data to mislead the model. Input manipulation attacks include adversarial attacks [i.20]. In these types of attacks, the adversary gains control of the inputs to the development of the model, its training and testing data, labels, the model, the code, and can use queries of the model to obtain predictions in the form of labels and model confidences [i.9]. - -Input manipulation attacks can occur during the training stage, while the model is learning, or during the inference/deployment stage. Inference/deployment stage attacks are further broken down into two cases. In the first case, the adversary modifies testing samples to create adversarial examples that are similar to the original sample but alter the model predictions to the adversary's choices. The second type of attack, the adversary uses query access to the ML model to obtain confidential data within the model [i.9]. - -#### 5.3.2.2 Potential Exploits - -AI/ML input manipulation attacks pose several security threats as documented in [i.9]: - -**Manipulation of training data:** An adversary can take control of a subset of the training data by inserting or modifying training samples. - -**Manipulation of the testing data:** An adversary may add perturbations to testing samples at model deployment time to generate adversarial examples or in backdoor poisoning attacks. - -**Manipulation of the labels:** An adversary may intentionally mis-assign labels to training data. - -**Manipulation of the queries:** An adversary may submit queries to the model and receive predictions (either labels or model confidences) and confidential data. This capability is used by black-box evasion attacks, Energy-Latency Attacks, and all privacy attacks. - -### 5.3.3 Data poisoning attacks (ML02:2023) - -#### 5.3.3.1 Introduction - -As per Threat Intelligence Report 2023 [i.15], 60% of attacks in telecom mobile networks are linked to Internet of Things (IoT) bots scanning for vulnerable hosts to expand their botnets for use in distributed denial-of-service (DDoS) attacks. - -With knowledge of inputs and outputs for different AI/ML based network optimization use-cases, hackers can use such bots to inject poisoned data which may be used for AI/ML training. - -The poisoned data injected by the hacker can vary based on the hacker's knowledge of the AI/ML models and algorithms used in the AI/ML training. Based on the hacker's level of knowledge of the AI/ML models and algorithms used for AI/ML training, the poisoning attacks are as defined in the sub-clauses below. - -#### 5.3.3.2 Black box data poisoning attacks - -For Black box data poisoning attacks, the attacker does not need to know any details of the AI/ML models and algorithms used for the AI/ML training, or the parameters being used. Knowledge of inputs and outputs of AI/ML model alone is sufficient for the attacker to create poisoned data and to launch the (Black box) data poisoning attacks. - -Details of input data used for different use-cases are already provided in O-RAN specifications. An adversary can use these details to identify which input data is used for training AI/ML models for which use-cases. An attacker in possession of a compromised data-source (bot) can inject poisoned data that can impact the behaviour of the AI/ML model used in the O-RAN deployment. - -#### 5.3.3.3 Grey box data poisoning attacks - -Training AI/ML models requires historic data as input, in some use-cases. Because of this, usually, training data is stored in a database. For training online ML models, streaming input data is used, which is not historic in nature. Also, for some use-cases, trained models can be stored in databases. - -In Grey box data poisoning attacks, the attacker leverages the knowledge (primarily the vulnerabilities) of the AI/ML data store and attempts to determine the AI/ML model/algorithm used for the AI/ML training, or the parameters being used. For example, if the database security has vulnerabilities allowing SQL-injection kinds of query-based attacks, an adversary can use such vulnerabilities to interactively obtain information about AI/ML models/algorithms and their training data sets. - -For online ML models, the attacker leverages the knowledge of the streaming data source, or the streaming protocol vulnerabilities, or the transport protocol vulnerabilities or the transport network vulnerabilities to manipulate the training data used for online training. - -Knowledge of inputs and outputs of the AI/ML model along with the level of information about the AI/ML models/algorithms is used by attacker to create poisoned data and to launch the (Grey box) data poisoning attacks. Grey box data poisoning attacks poison the training data in a manner that would affect that particular algorithm or its parameters the most. - -#### 5.3.3.4 White box data poisoning attacks - -In White box data poisoning attacks, the attacker has obtained enough information i.e. full knowledge about the AI/ML models and algorithms being used, the configurable parameters like thresholds, hyper-parameters, etc. - -Knowledge of inputs and outputs of AI/ML model along with the full knowledge of the AI/ML models/algorithms is used by attacker to create poisoned data and to launch the (White box) data poisoning attacks. White box data poisoning attacks can be done in a manner which can modify the behaviour of AI/ML algorithm with slow poisoning and can make it very challenging to detect such attacks. - -### 5.3.4 Model Inversion Attack (ML03:2023) - -#### 5.3.4.1 Introduction - -OWASP defines a Model Inversion attack as a type of attack in which an attacker reverse-engineers the model to extract information from it [i.20]. Model inversion attacks are also called data reconstruction attacks [i.9], because they allow an attacker to recover personal or other types of information from aggregate and/or training information. This type of attack poses a significant risk to the privacy of the data used for training the model. Model Inversion attacks are more likely to be successful in cases where the model is overfitted, as it may have memorized specific training examples [i.53]. - -Model inversion attacks can lead to privacy violations, identity theft, loss of trust, misuse of sensitive information, and damage to reputation. - -Model Inversion attacks typically involve the following steps. - -1. The attacker accesses the model through a public API, a stolen copy of the model, or other means of interacting with the model's predictions. -2. The attacker selects a target individual or data point whose information they want to reconstruct from the model. -3. The attacker starts with an initial input that could be random or based on some prior knowledge of the target domain. -4. The attacker inputs the generated data into the model and collects the model's predictions and confidence scores. -5. Using the information from the model's outputs, the attacker iteratively refines the input data to maximize the model's confidence in the target label or class. This process involves optimization techniques like gradient descent or genetic algorithms. -6. The attacker repeats steps 4 and 5 until the input converges to a close approximation of the target data point, or the confidence scores reach a certain threshold. -7. The attacker now has a data point that closely resembles the original training data point, effectively compromising the privacy of the target individual or data point. - -#### 5.3.4.2 Potential Exploits - -Potential exploits of Model Inversion attacks are identified in [i.9][i.53]. - -- **Black-box Model Inversion attack:** In this type of attack, the attacker only has access to the model's input-output pairs, meaning they can input data and receive the corresponding predictions. They have no knowledge of the model's architecture, parameters, or the training data. The attacker generates inputs, analyses the model's outputs, and iteratively refines the inputs based on the obtained information. This process continues until the attacker is able to approximate the original training data. -- **White-box Model Inversion attack:** In a white-box attack, the attacker has access to the AI model, including its architecture, parameters (such as weights and biases), and possibly partial knowledge of the training data. This additional information allows the attacker to exploit the inner workings of the model more effectively and reconstruct the original training data with higher accuracy. In this scenario, the attacker can use gradient-based optimization techniques to maximize the model's confidence in the target label or class, ultimately converging to a close approximation of the target data point. - -### 5.3.5 Membership Inference Attack (ML04:2023) - -#### 5.3.5.1 Introduction - -A membership inference attack (MIA) is a privacy attack where an attacker tries to determine whether a specific individual's data was used to train the model. The attacker will observe a model's output for various inputs, including the specific individual data [i.18][i.51][i.52]. - -In the telecommunications domain typically telecom providers typically handle vast amounts of user data which could include their location information, call behaviour, data access behaviour etc., These data are quite sensitive and can reveal individual patterns. - -#### 5.3.5.2 Potential Exploits - -There are many different types of membership inference attack (MIA), each exploiting different aspects of the target model which can reveal the membership information in unique ways. Some of the common types of MIA are: - -- a) MIA based on information access, i.e., how much information the attacker is aware of the model, its internals. The attack types are Black-box MIA, Gray-box MIA and White-box MIA. -- b) MIA based on inference technique: i.e., by applying different analysis methods the attacker tries to infer input to output relation. Some of the attack types are Decision threshold analysis, Gradient-based analysis and Distance-based analysis. In Decision threshold analysis, the subtle changes in input's relation to the model's output confidence score is observed. In Gradient-based analysis techniques such as back propagation is used to analyse input to output variation. In Distance-based analysis the distance between model's output for different inputs in multi-dimensional space is used. -- c) MIA based on target: i.e., how the attacker would like to understand whether specific individual data or data of a group of individuals are involved in the training set. The attack types are known as Individual membership inference attack and Group membership inference attack, respectively. - -Potential MIAs in case of Telecom domain are: - -- 1) Identifying Specific Individuals: The attacker tries to determine if a specific user information is included in the training data. This attack can exploit model vulnerabilities to target specific individuals. -- 2) Group membership inference: The attacker tries to determine behaviour of individuals and group them based on available data. The attack can lead to determination of sensitive information that can then be used for potential discrimination or targeted attacks. - -### 5.3.6 Model Stealing (ML05:2023) - -#### 5.3.6.1 Introduction - -AI/ML model stealing or extraction attacks refer to unauthorized attempts to steal or extract machine learning models. These attacks are driven by the value and intellectual property associated with trained models, which can be leveraged by malicious actors for various purposes such as replicating the model's functionality, using it for financial gain, or performing adversarial attacks [i.16]. - -AI/ML model stealing/extraction attacks typically involve the following steps: - -1. **Obtaining Access:** Attackers attempt to gain unauthorized access to the target environment where the model is deployed or stored. This can be done through various means such as exploiting vulnerabilities in the infrastructure, social engineering, insider threats, or targeting weak authentication mechanisms. -2. **Model Extraction:** Once access is obtained, attackers aim to extract the trained model from its storage or runtime environment. This can be achieved through techniques like reverse engineering, model inversion attacks [i.17], membership inference attacks [i.18], or by directly exfiltrating the model from the target system. -3. **Model Utilization:** After stealing the model, attackers can use it for several malicious purposes. For example, they may retrain or fine-tune the model on their own data, use it to understand the vulnerabilities and weaknesses of the target system, prepare adversarial examples, conduct adversarial attacks, or create replicas of the model for unauthorized distribution. -4. **Watermark Stripping via API Abuse:** In advanced threat scenarios specific to AI-native O-RAN deployments - such as gNB, UE-based inference, network slices, and RIC-based analytics - attackers may not aim to extract the full model but instead target its embedded ownership watermarks. These may include slight changes in model weights, trigger-based behaviours, or proprietary activation patterns embedded to protect intellectual property and support regulatory compliance (e.g., EU AI Act, [i.70]). Through repeated and adaptive black-box queries to public or internal APIs or interfaces (for EXAMPLE E2 ([i.23]), A1 ([i.71]) and Near-RT RIC APIs), adversaries can statistically analyse model responses to detect watermark-related anomalies. Techniques such as functional inversion, confidence probing, and boundary sensitivity testing allow the attacker to infer the logic behind watermark mechanisms. A surrogate model can then be trained to replicate the original model's predictions, while intentionally avoiding the behavioural traits tied to watermarking - resulting in a "clean" but unauthorized replica. This novel vector, known as watermark stripping, enables silent intellectual property (IP) laundering and ownership disassociation without needing access to model internals. The attack operates entirely over legitimate API or interface channels, bypassing traditional defences and posing serious risks to ownership verification in O-RAN systems ([i.65], [i.66], [i.67], [i.68]). - -#### 5.3.6.2 Potential exploits - -AI/ML model stealing/extraction attacks pose several security threats: - -- **Intellectual Property Theft:** Stolen models can lead to the theft of intellectual property, allowing attackers to replicate the model's functionality without incurring the associated development costs. -- **Competitive Advantage Erosion:** If a competitor gains unauthorized access to a trained model, it can undermine the original developer's competitive advantage by using the model for similar or competing purposes. -- **Data Privacy Violations:** The stolen model may contain sensitive information embedded within its learned parameters. This can result in privacy breaches, especially if the model was trained on sensitive or personal data. -- **Adversarial Attacks:** Attackers may exploit the extracted model to craft adversarial examples (to mount an evasion attack) or launch targeted attacks against the system that initially deployed the model, using obtained knowledge about possible vulnerabilities. -- **Watermark Stripping via API Abuse:** A new class of attacks specifically targets the embedded watermarks within AI models used for intellectual property protection and regulatory compliance. In this threat scenario - particularly relevant to O-RAN systems where models are accessible through exposed APIs or interfaces - -involved in inference at gNBs, UEs, or RIC components - attackers use black-box access to issue adaptive queries. EXAMPLEs for these APIs or interfaces are E2 ([i.23]), A1 ([i.71]) and Near-RT RIC APIs. These queries are designed to reverse-engineer and identify the statistical or functional behaviours associated with watermarking mechanisms (e.g., trigger-based patterns, slight changes in model weights, or hidden layer activations). Once identified, attackers retrain a surrogate model that replicates the original's functionality but omits these watermark signals, effectively "laundering" the model and erasing any forensic trace of ownership ([i.65], [i.66], [i.68]). This enables unauthorized redistribution or commercialization while bypassing traditional IP enforcement and detection mechanisms. - -### 5.3.7 AI Supply Chain Attacks (ML06:2023) - -#### 5.3.7.1 Introduction - -AI supply chain attacks refer to malicious activities targeting the various stages of Artificial Intelligence (AI) system development and deployment. These attacks aim to manipulate data, models, software and hardware used in AI systems with the goal of introducing vulnerabilities that can be exploited later for unauthorized access, data exfiltration, or other malicious purposes. - -#### 5.3.7.2 Potential exploits - -AI Supply Chain Attacks pose several security threats: - -- **Data poisoning:** Adversaries may corrupt or manipulate training datasets to cause the AI model to learn incorrect associations or make biased predictions. This can lead to degraded performance, wrong decisions, or even backdoors in the final system. -- **Model tampering:** Attackers might inject malicious code or logic into the AI model itself during training or deployment. This could allow them to gain control over the target system, steal sensitive data, or force the AI system to produce incorrect results on demand. -- **Backdoor attacks (a.k.a. Trojan attacks):** In these attacks, a seemingly benign AI model is infected with malicious code that remains dormant until it receives a specific trigger. At this point, the attacker can remotely activate the backdoor and use it to compromise the target system or exfiltrate data. -- **Hardware tampering:** Malicious actors may also focus on manipulating the hardware used for AI processing, such as GPUs, ASICs, or FPGAs. By introducing backdoors or vulnerabilities in these components, attackers can compromise the confidentiality, integrity, and availability of AI systems even if the software and data are secure. -- **Insecure maintenance APIs:** Many AI services are exposed through APIs, for example for deployment and maintenance, that can be abused by attackers to launch supply chain attacks. If these APIs are not properly secured, they can be used to inject malicious code or exfiltrate sensitive information from the target system. -- **Third-party libraries and dependencies:** AI systems often rely on third-party libraries and open-source components which might be modified by attackers to compromise subsequent AI/ML model training or inference, or might contain vulnerabilities or backdoors that attackers can exploit. Insecure software supply chains increase the risk of such attacks. Third-party libraries are periodically updated with new features or deprecated due to discovery of security vulnerabilities. An AI/ML model depending on a vulnerable version of a third-party library could introduce a security vulnerability if used. - -### 5.3.8 Transfer Learning Attack (ML07:2023) - -#### 5.3.8.1 Introduction - -Transfer learning is a machine learning (ML) technique where a pre-trained model (a 'source' model) is used as a starting point for a new related task (a 'target' model), instead of training a model from scratch. This approach saves time, computational resources, and often leads to better performance. However, this ability to transfer knowledge can also be exploited by attackers through AI/ML Transfer Learning Attacks, leading to security threats ([i.54]). - -#### 5.3.8.2 Potential exploits - -Transfer Learning Attacks pose several security threats as they allow attackers to mount attacks on target models with limited or no access to the original training data. They are mainly based on the assumption that attacks that work on the source model most likely also work on the target model. The main types of Transfer Learning Attacks are: - -- **Data poisoning:** Attackers can poison the source model's training data by injecting malicious samples, which get propagated into the target model during transfer learning, causing misclassification or unintended behaviour in the latter. -- **Model stealing:** By using a series of carefully crafted queries to the source model, attackers can extract sensitive information about its architecture and parameters, which they can then use to build a similar model for malicious purposes. -- **Adversarial examples:** Attackers can create input samples that fool both the source and target models, even if these inputs are visually or semantically similar to benign ones. These adversarial examples can be used to bypass security systems or cause misclassifications in critical applications like self-driving cars or healthcare. -- **Backdoor attacks:** Attackers can embed hidden malicious functionality into the source model, which remains dormant until triggered by specific input patterns. When the trojans are transferred to the target model, they can cause unexpected behaviour or leak sensitive information. - -### 5.3.9 Model Skewing (ML08:2023) - -#### 5.3.9.1 Introduction - -A model skewing AI/ML attack is a data poisoning attack, where an attacker manipulates the training data, specifically the distribution of the training data, used to build a machine learning model [i.20]. This manipulation aims to cause the model to behave in a way that benefits the attacker, potentially harming the model's accuracy, fairness, and reliability. - -In model skewing attacks, - -- Attackers typically inject malicious data. This data can be fake or manipulated real data, designed to influence the model's learning process to meet the attackers needs. -- Attackers aim to skew the model's predictions towards their desired outcome. For example, they make a bias to favour some action i.e., approvals, or to overcome some action i.e., bypass security rules. - -In the Telecommunications networks machine learning models are used for tasks like: - -- Network traffic prediction, which is to optimize network resources based on predicted traffic patterns. -- Quality of service (QoS) optimization, which is to ensure consistent and reliable network performance. -- Fraud detection, which is to identify and block fraudulent activities like unauthorized access or SIM swap scams. -- Customer churn, whereby predicting customer churn behaviour develop retention strategies. - -Model skewing attacks in telecommunication networks can significantly impact the operation of networks causing service disruptions, reputational damage, and financial losses. - -- The attacker could create a network flood with dummy traffic. This behaviour can skew the model to predict higher traffic than usual, leading to over-provisioning of resources and unnecessary costs. -- The attacker could manipulate network performance data, artificially degrading certain areas' performance metrics. This could prompt the model to optimize resources towards those areas unnecessarily. -- The attacker could manipulate labels of transactions, i.e., they could change "fraudulent" labels to "legitimate," allowing malicious activity to remain undetected. -- The attacker could alter predictions resulting in higher churn rates and this could cause the operators to invest unnecessarily in retention strategies for non-churning customers. - -#### 5.3.9.2 Potential Exploits - -Model skewing attacks are performed primarily by exploiting weaknesses in the model's training process, such as lack of data validation or feedback mechanisms. There are many different types of model skewing attacks, based on attackers' intention. However, they can be broadly categorized into the following two exploits. - -- a) **Data manipulation-based Model skewing attacks:** The attacker manipulates the data involved in the training of the model. The attacker modifies/injects the training data with modified data, or modifies the labels associated with the training data, resulting in learnt model behaviour to be changed. The attack can significantly impact the operation of networks causing service disruptions, reputational damage, and financial losses. -- b) **Feedback manipulation-based Model Skewing attacks:** The attacker manipulates the feedback mechanisms used by the AI/ML for continuous improvement during deployment. The attack can significantly impact the operation of networks causing service disruptions, reputational damage, and financial losses. - -### 5.3.10 Output Integrity Attack (ML09:2023) - -#### 5.3.10.1 Introduction - -Output integrity attack (see [i.50]) in the context of AI/ML model is to alter or manipulate the output of an ML model to attack the system that the model is being used in. The model output can be used by a system to implement critical logic/decisions, and a malicious actor can influence the output of the model to force incorrect decisions by the system. These incorrect decisions can lead to manipulation of other systems with which the current system interacts with. - -From O-RAN point of view, the Non-RT RIC and Near-RT RIC use the AI/ML model to perform inference. The result of an inference using a model is an output which in the case of the Non-RT RIC is used to generate A1 policies and/or changing the configuration of O-CU and O-DU/O-RU using the O1 interface or the open fronthaul m-plane. Similarly, the Near-RT RIC uses the model inference output to generate E2 policies and configuration changes over the E2 interface. - -AI/ML model output attacks typically involve the following steps: - -1. **Obtaining Access:** Attackers attempt to gain unauthorized access to the target environment where the model output can be modified or altered. This can be done through various means such as exploiting vulnerabilities in the infrastructure, social engineering, insider threats, or targeting weak/misconfigured authentication/authorization mechanisms. -2. **Output manipulation:** After gaining access to the target environment, the attackers can manipulate the AI/ML model output in several ways. Some of the attack vectors are mentioned below. - -| Attack vector | Description | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Output in transit | This method involves modifying the output while it is in transit over a network. | -| Output storage | This method involves modifying the output stored in the model output storage. | -| Output layer of the model | This method involves changing the model output layer of the AI/ML model to achieve output manipulation. | -| Model inputs | This method does not involve a direct output manipulation but achieves the output change by modifying the training, inference, prediction inputs to the model. | -| Model hyperparameters | This method does not involve a direct output manipulation but achieves the output change by modifying the hyperparameters used for training the model. | - -3. **Monitoring and recalibration:** Attackers monitor the effect of model output change and perform recalibration to achieve the desired result. - -#### 5.3.10.2 Potential exploits - -AI/ML model output attacks pose several security threats: - -- **Denial of Service:** The output of the AI/ML models is used to configure the O-RAN network functions and generate A1 policies for Near-RT RIC. A manipulated output of a model can cause service disruption of the O-RAN elements that are using configuration / policies derived from the output. -- **Subscriber QoE change:** The QoE that the subscribers experience depends on several configuration parameters of O-RAN elements and the radio conditions of the subscribers. AI/ML models are used to perform QoE optimization and QoE based traffic steering in O-RAN [i.14]. A carefully crafted manipulation of the output of AI/ML model can be used to improve or degrade the QoE of a subscriber or a group of subscribers. - -### 5.3.11 Model Poisoning (ML10:2023) - -#### 5.3.11.1 Introduction - -Model poisoning attacks involve an adversary modifying an ML model's internals to alter its predictions. Specifically, these changes could be made to the model parameters or to the code of the model algorithms. Unauthorized code changes to the model inference algorithm or alteration of the model parameters file pertain to trained models, while code changes to the model learning algorithm pertain to initial (untrained) models [i.20][i.19][i.48][i.49]. - -In literature this attack may also be referred to as logic corruption [i.48] and can sometimes be inclusive to the manipulation of training data [i.20]. This aspect overlaps with Input Manipulation and Data Poisoning attacks, covered in clauses 5.3.2 and 5.3.3 respectively. For this report, model poisoning will focus on the direct manipulation of model internals. - -As an example, consider the O-RAN use case numbered 21 on Energy Saving [i.47]. This use case details AI/ML assist to automatically control the power to one or more carriers or a cell of a given technology to reduce power consumption for the O-CU/DU/RU. An adversary with direct access to the Non-RT RIC model could alter its parameters to embed a backdoor, which could later be triggered to power-off of specific carriers or cells. - -In the O-RAN AI/ML lifecycle, trained models reside in the “AI/ML Inference” and “AI/ML Model” hosts while initial models reside in the “AI/ML Training” host referred to in Figure 4-1 of [i.14]. Depending on the deployment scenarios outlined in table 2 of [i.14], the AI/ML lifecycle hosts (and their models) mentioned above might reside in the O-CU, O-DU, Non-RT RIC, SMO, or Near-RT RIC (see Table 4-1). - -#### 5.3.11.2 Potential Exploits - -AI/ML model poisoning attacks pose several security threats as documented in [i.9]: - -**Manipulation of the model:** An adversary can take control of the model parameters by either generating a backdoor or Trojan trigger and inserting it in the model or by sending malicious local model updates in federated learning. - -### 5.3.12 Evasion attacks - -#### 5.3.12.1 Introduction - -As per ENISA report 2021 [i.19], evasion attacks are widely prevalent in cases where AI/ML solutions are deployed. - -With knowledge of inputs and outputs pairs during inference phase for different AI/ML use cases, attackers can work on the ML algorithm's inputs to find small perturbations leading to large modification of its outputs (e.g. decision errors). - -#### 5.3.12.2 White box evasion attacks - -White box evasion attacks are based on gradient computation and the attacker has full knowledge of the AI/ML models and algorithms being used [i.9], the configurable parameters like thresholds, hyper-parameters, etc. The attacker - -manipulates an input sample in such a way that the classification loss is maximized. The specific manipulation is determined by calculating the gradients of the classification loss with respect to the input sample. For example, the attacker adds noise to the input sample, in the direction of the gradient of the classification loss with respect to the input sample. - -#### 5.3.12.3 Black box evasion attacks - -Black-box evasion attacks are designed under a realistic adversarial model, in which the attacker has no prior knowledge of the model architecture or parameters. Instead, the adversary can interact with a trained ML model by querying it on various data samples and obtaining the model's predictions. There are two main classes of black-box evasion attacks [i.9]. - -- a) Decision based attacks: In these attacks, the adversary can only access the model's final decision or predicted label. Techniques include the Boundary Attack, which employs random walks along the decision boundary and rejection sampling, and the HopSkipJumpAttack, which enhances gradient estimation to minimize the number of queries. Other methods involve finding the direction of the nearest decision boundary (OPT attack), using sign SGD instead of binary searches (Sign-OPT attack), and applying Bayesian optimization. -- b) Score-based attacks: In this scenario, attackers access the model's confidence scores or logits and use various optimization techniques to generate adversarial examples. A common approach is zeroth-order optimization, which estimates the model's gradients without directly computing derivatives. Other techniques include discrete optimization, natural evolution strategies, and random walks. - -The attacker can also employ transfer-based evasion techniques, exploiting the potential that an input identified as an adversarial example for a surrogate white-box model could similarly be effective as an adversarial example for another black-box model. - -### 5.3.13 AI Energy-Latency Attack - -#### 5.3.13.1 Introduction - -The AI/ML Energy-Latency Attack is a type of side-channel attack that targets machine learning systems by exploiting the correlation between energy consumption and computation latency in hardware. These attacks can be used to infer sensitive information about the model, its parameters, or the data it's processing by observing power usage and timing information. This type of attack is particularly relevant for systems where machine learning models are deployed on edge devices or in cloud environments where multiple users share hardware resources. - -The fundamental concept behind energy-latency attacks is that different computations consume varying amounts of energy and take different lengths of time to complete. In the context of machine learning, the execution of different neural network layers or operations can lead to measurable differences in power consumption and processing time. An attacker with access to these measurements can potentially infer the model's architecture, the data being processed, or even reconstruct the input data, which can be a significant privacy concern ([i.62], [i.63]). In addition, an attacker may craft inputs that maximize energy consumption or computation time (so called 'Sponge Examples', [i.61]), leading to a denial of service by overloading the system or draining battery life. - -#### 5.3.13.2 Potential Exploits - -**Model Extraction:** By monitoring the energy and latency patterns, an attacker might deduce the structure of the neural network, including the types of layers, their sequence, and possibly hyperparameters. - -**Data Inference:** Observing the energy and latency signatures of different computations could allow an attacker to make inferences about the input data, potentially leading to privacy breaches, especially if the data is sensitive. - -**Denial of Service:** An attacker could exploit these side channels to craft inputs that maximize energy consumption or computation time, leading to a denial of service by overloading the system or draining battery life. - -# 6 Threat Analysis - -## 6.1 Input Manipulation Attack (ML01:2023) - -### 6.1.1 Training Data Control - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-IM-1 | -| Threat title | Training Data Control | -| Threat description | An adversary takes control of a subset of the training data by inserting or modifying training samples. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Integrity | -| Affected Assets | Training or test data: data sets collected externally or internally from the Near-RT RIC, O-CU and O-DU and passed to the ML training hosts in a ML system. [ASSET-D-25]
The trained ML model [ASSET-D-26],
The ML prediction results built into the model [ASSET-D-27],
The behaviour of the ML system [ASSET-D-28]. | - -### 6.1.2 Model Control - -void - -### 6.1.3 Testing Data Control - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-IM-2 | -| Threat title | Testing Data Control | -| Threat description | An adversary adds perturbations to testing samples at model deployment time to generate adversarial examples or in backdoor poisoning attacks | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Integrity | -| Affected Assets | Training or test data: data sets collected externally or internally from the Near-RT RIC, O-CU and O-DU and passed to the ML training hosts in a ML system. [ASSET-D-25]
The trained ML model [ASSET-D-26],
The ML prediction results built into the model [ASSET-D-27],
The behaviour of the ML system [ASSET-D-28]. | - -### 6.1.4 Label Manipulation - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-IM-3 | -| Threat title | Label Manipulation | -| Threat description | An adversary may intentionally mis-assign labels to training data. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Integrity | -| Affected Assets | Training or test data: data sets collected externally or internally from the Near-RT RIC, O-CU and O-DU and passed to the ML training hosts in a ML system. [ASSET-D-25]
The trained ML model [ASSET-D-26],
The ML prediction results built into the model [ASSET-D-27],
The behaviour of the ML system [ASSET-D-28]. | - -### 6.1.5 AI/ML Query Exploitation - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-IM-4 | -| Threat title | AI/ML Query Exploitation | -| Threat description | An adversary may submit queries to the model and receive predictions (either labels or model confidences) and confidential data. | -| Threat type | Information Disclosure | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in AI/ML APIs | -| Impact type | Confidentiality | -| Affected Assets | A1 Enrichment Information that is collected or derived at SMO/Non-RT RIC either from non-network data sources or from network functions themselves and provided over the A1 interface to be utilized by Near-RT RIC, e.g., an ML model, to improve its performance. [ASSET-D-08]
Training or test data: data sets collected externally or internally from the Near-RT RIC, O-CU and O-DU and passed to the ML training hosts in a ML system. [ASSET-D-25]
The trained ML model [ASSET-D-26],
The ML prediction results built into the model [ASSET-D-27],
The behaviour of the ML system [ASSET-D-28]. | - -## 6.2 Data poisoning attacks (ML02:2023) - -### 6.2.1 Black-box Data Poisoning - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-DP-01 | -| Threat title | Black-box Data Poisoning | -| Threat description | An attacker in possession of a compromised data-source can inject poisoned data which can be consumed by AI/ML for training. For such an attack, the attacker does not need to know any details of the AI/ML algorithm, or the parameters being used. Knowledge of inputs and outputs of AI/ML is sufficient to launch such attacks. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -### 6.2.2 Grey-box Data Poisoning - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-DP-02 | -| Threat title | Grey-box Data Poisoning | -| Threat description | An attacker being able to query the database which stores the training data, and/or streaming data used for online ML models, and/or AI/ML models may be able to get more details about the AI/ML algorithms being used and parameters configured if any. This can help the attacker | - -| | | -|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | to launch an attack which can poison the training data in a manner that would affect that particular algorithm or its parameters the most. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in data transport, vulnerabilities in training database | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11],
O1 interface for streaming data [ASSET-C-22],
A1 interface [ASSET-C-14],
E2 interface for streaming data [ASSET-C-40],
AI/ML Workflow [ASSET-C-61] | - -### 6.2.3 White-box Data Poisoning - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-DP-03 | -| Threat title | White-box Data Poisoning | -| Threat description | An attacker having full knowledge of the AI/ML algorithm being used, the configurable parameters like thresholds, hyper-parameters, etc. can launch a data poisoning attack in a manner which can modify the behaviour of AI/ML algorithm with slow poisoning and can make it very challenging to detect such attacks. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11],
O1 interface for streaming data [ASSET-C-22],
A1 interface [ASSET-C-14],
E2 interface for streaming data [ASSET-C-40],
AI/ML Workflow [ASSET-C-61] | - -## 6.3 Model Inversion Attack (ML03:2023) - -### 6.3.1 Black-box Model Inversion - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MOI-01 | -| Threat title | Black-box Model Inversion | -| Threat description | An attacker has access to the model's input-output pairs allowing them to input data and receive predictions. The attacker generates inputs, analyzes the model's outputs, and iteratively refines the inputs based on the obtained information. This process continues until the attacker is able | - -| | | -|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | to approximate the original training data. The attacker has no knowledge of the model's architecture, parameters, or the training data. | -| Threat type | Information Disclosure | -| Vulnerabilities | Model is overfitted, model may have memorized specific training examples, model API not properly protected | -| Impact type | Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26]

The ML prediction results built into the model [ASSET-D-27]

The behavior of the ML system including tasks for data collection, data wrangling, pipeline management, model retraining, and model deployment. [ASSET-D-28] | - -### 6.3.2 White-box Model Inversion - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MOI-02 | -| Threat title | White-box Model Inversion | -| Threat description | An attacker has access to the AI model, including its architecture, parameters (such as weights and biases), and possibly partial knowledge of the training data. This information allows the attacker to exploit the inner workings of the model more effectively and reconstruct the original training data with higher accuracy. In this scenario, the attacker can use gradient-based optimization techniques to maximize the model's confidence in the target label or class, ultimately converging to a close approximation of the target data point. | -| Threat type | Information Disclosure | -| Vulnerabilities | Model is not protected, training data is not protected, model is overfitted, model may have memorized specific training examples, model API not protected | -| Impact type | Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26]

The ML prediction results built into the model [ASSET-D-27]

The behaviour of the ML system including tasks for data collection, data wrangling, pipeline management, model retraining, and model deployment. [ASSET-D-28] | - -## 6.4 Membership Inference Attack (ML04:2023) - -### 6.4.1 Information Access – Membership Inference - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MEI-01 | -| Threat title | Information Access – Membership Inference | -| Threat description | An attacker possesses different levels of information on the model architecture, training parameters, training data, and relation between the output to the input. Based on the level of information access, the MIA can be Black-box MIA, or Gray-box MIA or White-box MIA. | -| Threat type | Information disclosure | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Confidentiality | -| Affected Assets | Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11] | - -### 6.4.2 Inference Technique – Membership Inference - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MEI-02 | -| Threat title | Inference Technique – Membership Inference | -| Threat description | An attacker by applying different analysis methods tries to infer input to output relation. Some of the attack types are Decision threshold analysis, Gradient-based analysis, Distance-based analysis. In Decision threshold analysis, the subtle changes in input's relation to the model's output confidence score is observed. In Gradient-based analysis techniques such as back propagation is used to analyse input to output variation. In Distance-based analysis the distance between model's output for different inputs in multi-dimensional space is used. | -| Threat type | Information disclosure | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Confidentiality | -| Affected Assets | Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11] | - -### 6.4.3 Target based Membership Inference - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MEI-03 | -| Threat title | Target based- Membership Inference | -| Threat description | In a target-based membership attack the attacker would like to understand whether specific individual data or data of a group of individuals are involved in the training set. The attack types are known as Individual membership inference attack, Group membership inference attack, respectively. In Individual membership inference attack, the attacker tries to determine if a specific user information is included in the training data. In Group membership inference attack, the attacker tries to determine behaviour of individuals and group them based on available data. | -| Threat type | Information disclosure | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Confidentiality | -| Affected Assets | Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11] | - -## 6.5 Model Stealing (ML05:2023) - -### 6.5.1 Intellectual Property Theft - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-ME-01 | -| Threat title | Intellectual Property Theft | -| Threat description | Stolen models can lead to the theft of intellectual property, allowing attackers to replicate the model's functionality without incurring the associated development costs. If a competitor gains unauthorized access to a trained model, it can undermine the original developer's competitive advantage by using the model for similar or competing purposes. | -| Threat type | Information disclosure | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | -| Impact type | Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -### 6.5.2 Data Privacy Violations - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-ME-02 | -| Threat title | Data Privacy Violations | -| Threat description | The stolen model may contain sensitive information embedded within its learned parameters. This can result in privacy breaches, especially if the model was trained on sensitive or personal data. | -| Threat type | Information disclosure | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | -| Impact type | Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -### 6.5.3 Adversarial Attacks with Stolen Models - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-ME-03 | -| Threat title | Adversarial Attacks with Stolen Models | -| Threat description | Attackers may exploit the extracted model to craft adversarial examples (to mount an evasion attack) or launch targeted attacks against the system that initially deployed the model, using obtained knowledge about possible vulnerabilities. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -## 6.6 AI Supply Chain Attacks (ML06:2023) - -### 6.6.1 Data Poisoning via Supply Chain - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-SC-01 | -| Threat title | Data Poisoning via Supply Chain | -| Threat description | Adversaries may corrupt or manipulate training datasets to cause the AI model to learn incorrect associations or make biased predictions. This can lead to degraded performance, wrong decisions, or even backdoors in the final system. | -| Threat type | Tampering, Denial of Service | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model transfer | -| Impact type | Integrity, Availability | - -| | | -|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | -|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| - -### 6.6.2 Model Tampering - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-SC-02 | -| Threat title | Model Tampering | -| Threat description | Attackers might inject malicious code or logic into the AI model itself during training or deployment. This could allow them to gain control over the target system, steal sensitive data, or force the AI system to produce incorrect results on demand. | -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Vulnerabilities in ML model transfer | -| Impact type | Integrity, Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -### 6.6.3 Backdoor via Supply Chain - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-SC-03 | -| Threat title | Backdoor via Supply Chain | -| Threat description | In these attacks, a seemingly benign AI model is infected with malicious code that remains dormant until it receives a specific trigger. At this point, the attacker can remotely activate the backdoor and use it to compromise the target system or exfiltrate data. | -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Vulnerabilities in ML model transfer | -| Impact type | Integrity, Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -### 6.6.4 Hardware Tampering - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-SC-04 | -| Threat title | Hardware Tampering | -| Threat description | Malicious actors may also focus on manipulating the hardware used for AI processing, such as GPUs, ASICs, or FPGAs. By introducing backdoors or vulnerabilities in these components, attackers can compromise the confidentiality, integrity, and availability of AI systems even if the software and data are secure. | -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Vulnerabilities in the AI processing HW | -| Impact type | Integrity, Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (ML training and inference hosts, xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -### 6.6.5 Insecure Maintenance APIs - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-SC-05 | -| Threat title | Insecure Maintenance APIs | -| Threat description | Many AI services are exposed through APIs, for example for deployment and maintenance, that can be abused by attackers to launch supply chain attacks. If these APIs are not properly secured, they can be used to inject malicious code or exfiltrate sensitive information from the target system. | -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Vulnerabilities in the ML maintenance APIs | -| Impact type | Integrity, Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -### 6.6.6 Third-party Libraries and Dependencies - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-SC-06 | -| Threat title | Third-party Libraries and Dependencies | -| Threat description | AI systems often rely on third-party libraries and open-source components which might contain vulnerabilities or backdoors that attackers can exploit. Insecure software supply | - -| | | -|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | chains increase the risk of such attacks. An AI/ML model depending on a vulnerable version of a third-party library could introduce a security vulnerability if used. | -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Vulnerabilities in the ML-related SW | -| Impact type | Integrity, Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -## 6.7 Transfer Learning Attack (ML07:2023) - -### 6.7.1 Data Poisoning for Transfer Learning - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-TL-01 | -| Threat title | Data Poisoning for Transfer Learning | -| Threat description | Attackers can poison the source model's training data by injecting malicious samples, which get propagated into the target model during transfer learning, causing misclassification or unintended behaviour in the latter. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -### 6.7.2 Model Stealing for Transfer Learning - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-TL-02 | -| Threat title | Model Stealing for Transfer Learning | -| Threat description | By using a series of carefully crafted queries to the source model, attackers can extract sensitive information about its architecture and parameters, which they can then use to build a similar model for malicious purposes. | -| Threat type | Information disclosure | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | -| Impact type | Confidentiality | - -| | | -|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | -|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| - -### 6.7.3 Adversarial Examples - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-TL-03 | -| Threat title | Adversarial Examples | -| Threat description | Attackers can create input samples that fool both the source and target models, even if these inputs are visually or semantically similar to benign ones. These adversarial examples can be used to bypass security systems or cause misclassifications in critical applications like self-driving cars or healthcare. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11] | - -### 6.7.4 Backdoor for Transfer Learning - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-TL-04 | -| Threat title | Backdoor for Transfer Learning | -| Threat description | Attackers can embed hidden malicious functionality into the source model, which remains dormant until triggered by specific input patterns. When the trojans are transferred to the target model, they can cause unexpected behaviour or leak sensitive information. | -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Vulnerabilities in ML model transfer | -| Impact type | Authenticity, Integrity, Availability, Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -## 6.8 Model Skewing (ML08:2023) - -### 6.8.1 Data manipulation for Model Skewing - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MS-01 | -| Threat title | Data manipulation for Model Skewing | -| Threat description | The attacker manipulates the data involved in the training of the model. The attacker modifies/injects the training data with modified data, or modifies the labels associated with the training data, resulting in learnt model behaviour to be changed. The impacted models have reduced accuracy / biased trained models, thereby the ability to make correct predictions is compromised, or the output is biased. The model skewing attacks can significantly impact the operation of networks causing service disruptions, reputational damage, and financial losses. | -| Threat type | Tampering, (Applicable Threats T-SMO-11, T-SMO-12, T-SMO-31, t rApps 05) | -| Vulnerabilities | Vulnerabilities in (i) training data validation, (ii) less robust model training against cyber-attacks, (iii) less model performance monitoring for monitoring of suspicious activity | -| Impact type | Integrity, and use-case specific impacts on O-RAN network. | -| Affected Assets | Trained ML model [ASSET-D-26],
ML Prediction Results [ASSET-D-27],
ML system [ASSET-D-28],
AI/ML Workflow [ASSET-C-61] | - -### 6.8.2 Feedback manipulation for Model Skewing - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MS-02 | -| Threat title | Feedback manipulation for Model Skewing | -| Threat description | The attacker manipulates the feedback mechanisms used by the AI/ML for continuous improvement during deployment. The attack can significantly impact the operation of networks causing service disruptions, reputational damage, and financial losses. | -| Threat type | Tampering, (Applicable Threats T-SMO-11, T-SMO-12, T-SMO-31, t rApps 05) | -| Vulnerabilities | Vulnerabilities in (i) less secure feedback mechanisms to prevent manipulation, (ii) less robust model training against cyber-attacks, (iii) less model performance monitoring for monitoring of suspicious activity | -| Impact type | Integrity, and use-case specific impacts on O-RAN network. | -| Affected Assets | Trained ML model [ASSET-D-26],
ML Prediction Results [ASSET-D-27],
ML system [ASSET-D-28] | - -## 6.9 Output Integrity Attack (ML09:2023) - -### 6.9.1 Denial of Service Impacting Output Integrity - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-OI-01 | -| Threat title | Denial of Service Impacting Output Integrity | -| Threat description | The AI/ML output can be manipulated to contain values that are incorrect or out of range. This can lead to service degradation, partial failure or total failure of the O-RAN element that is consuming this output and lead to denial of service to other O-RAN elements or subscribers. | -| Threat type | Denial of service | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | -| Impact type | Availability | - -| | | -|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Affected Assets | Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML prediction results [ASSET-D-27],
A1 policies [ASSET-D-07],
E2 node data [ASSET-D-11],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | -|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| - -### 6.9.2 Subscriber QoE Change - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-OI-02 | -| Threat title | Subscriber QoE Change | -| Threat description | The AI/ML output can be manipulated to contain values which can influence the configuration or policies being used by the O-RAN elements. This can lead to a behaviour of O-RAN network elements where a subscriber or a group of subscribers is treated unfairly or with a preference. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | -| Impact type | Integrity | -| Affected Assets | Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML prediction results [ASSET-D-27],
Data transported over the E2 interface [ASSET-D-09],
A1 policies [ASSET-D-07],
E2 node data [ASSET-D-11],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -## 6.10 Model Poisoning (ML 10:2023) - -### 6.10.1 Model Parameter Poisoning - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MP-01 | -| Threat title | Model Parameter Poisoning | -| Threat description | The adversary has access to the parameters file of a trained model. The parameters file is altered to change the model's predictions to achieve the goals of the adversary. | -| Threat type | Tampering | -| Vulnerabilities |
  • Insufficient access controls to the model's parameters [i.20]
  • Inadequate monitoring and logging of model's activity [i.19]
  • Lack of control for poisoning in model [i.19]
  • Weak access protection mechanisms for ML model components [i.19]
| -| Impact type | Integrity | -| Affected Assets | [ASSET-D-26] Trained ML model,
[ASSET-C-12] ML components deploying machine learning (xApps, rApps), | - -| | | -|--|-------------------------------------------------------------------------------------------------------------------| -| | [ASSET-D-27] The ML prediction results built into the model (e.g. expected outcomes), AI/ML Workflow [ASSET-C-61] | -|--|-------------------------------------------------------------------------------------------------------------------| - -### 6.10.2 Inference Algorithm Poisoning - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MP-02 | -| Threat title | Inference Algorithm Poisoning | -| Threat description | The adversary has access to the code of a trained model. The inference algorithm is altered to change the model's predictions to achieve the goals of the adversary. | -| Threat type | Tampering | -| Vulnerabilities |
  • • Insufficient access controls to the model's code [i.20]
  • • Inadequate monitoring and logging of model's activity [i.19]
  • • Lack of code integrity
  • • Weak access protection mechanisms for ML model components [i.19]
| -| Impact type | Integrity | -| Affected Assets | [ASSET-D-26] Trained ML model.
[ASSET-D-27] The ML prediction results built into the model (e.g. expected outcomes). | - -### 6.10.3 Learning Algorithm Poisoning - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MP-03 | -| Threat title | Learning Algorithm Poisoning | -| Threat description | The adversary has access to the code of an untrained model. The learning algorithm is altered to cause the model to make incorrect predictions. | -| Threat type | Tampering | -| Vulnerabilities |
  • • Insufficient access controls to the model's code [i.20]
  • • Inadequate monitoring and logging of model's activity [i.19]
  • • Weak access protection mechanisms for ML model components [i.19]
| -| Impact type | Integrity | -| Affected Assets | ML models that have not been trained yet, i.e., Initial Models and their associated learning algorithm [ASSET-D-40],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
AI/ML Workflow [ASSET-C-61] | - -### 6.10.4 Model Control - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MP-04 | -| Threat title | Model Control | -| Threat description | An adversary takes control of the model parameters by either generating a Trojan trigger and inserting it in the model or by sending malicious local model updates in federated learning | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in ML model storage, vulnerabilities in ML model transfer | -| Impact type | Integrity | -| Affected Assets | ML components deploying machine learning [ASSET-C-12],
The trained ML model [ASSET-D-26],
The ML prediction results built into the model [ASSET-D-27],
The behaviour of the ML system [ASSET-D-28],
ML models that have not been trained yet, i.e., Initial Models and their associated learning algorithm [ASSET-D-40], | - -| | | -|--|-----------------------------| -| | AI/ML Workflow [ASSET-C-61] | -|--|-----------------------------| - -## 6.11 Evasion attacks - -### 6.11.1 Grey-box based Data Evasion - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-EV-01 | -| Threat title | Grey-box based Data Evasion | -| Threat description | Possibility to tamper with the input to AI ML application during the inference phase in the Near-RT RIC or Non-RT RIC (model, model parameters, etc.) for example the model's gradient | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in the input APIs of the AI ML model application
Vulnerabilities in the source of input data used by AI ML for inferences | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11] | - -### 6.11.2 White box evasion attack - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-EV-02 | -| Threat title | White-box based data evasion attacks | -| Threat description | An attacker has complete knowledge of the AI/ML models and algorithms in use, including configurable parameters such as thresholds and hyper-parameters. By calculating the gradients of the classification loss with respect to the input sample, the attacker manipulates the input to maximize the classification loss | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in the input APIs of the AI ML model application
Vulnerabilities in the source of input data used by AI ML for inferences | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11] | - -### 6.11.3 Black box evasion attack - -| | | -|---------------------|--------------------------------------| -| Threat ID | T-AIML-EV-03 | -| Threat title | Black-box based data evasion attacks | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat description | An attacker can interact with a trained ML model by querying it on various data samples and obtaining the model's predictions and estimating the gradients of the classification loss with respect to the input sample with no prior knowledge of the AI/ML algorithm, or the parameters being used. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in the input APIs of the AI ML model application
Vulnerabilities in the source of input data used by AI ML for inferences | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11] | - -## 6.12 AI Energy-Latency Attack - -### 6.12.1 Model Extraction - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-EL-01 | -| Threat title | Model Extraction | -| Threat description | By monitoring the energy and latency patterns, an attacker might deduce the structure of the neural network, including the types of layers, their sequence, and possibly hyperparameters. | -| Threat type | Information disclosure | -| Vulnerabilities | Vulnerabilities in data sources | -| Impact type | Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
AAL software [ASSET-C-29],
Hardware accelerator device firmware [ASSET-C-30] | - -### 6.12.2 Data Inference - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-EL-02 | -| Threat title | Data Inference | -| Threat description | Observing the energy and latency signatures of different computations could allow an attacker to make inferences about the input data, potentially leading to privacy breaches, especially if the data is sensitive. | -| Threat type | Information disclosure | -| Vulnerabilities | Vulnerabilities in data sources | -| Impact type | Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
AAL software [ASSET-C-29],
Hardware accelerator device firmware [ASSET-C-30] | - -### 6.12.3 Denial of Service via Side Channels - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-EL-03 | -| Threat title | Denial of Service via Side Channels | -| Threat description | An attacker could exploit these side channels to craft inputs that maximize energy consumption or computation time, leading to a denial of service by overloading the system or draining battery life. | -| Threat type | Denial of service | -| Vulnerabilities | Vulnerabilities in data sources | -| Impact type | Availability | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-eNB [ASSET-C-07],
Non-RT RIC [ASSET-C-11],
AAL software [ASSET-C-29],
Hardware accelerator device firmware [ASSET-C-30] | - -# 7 Security Controls - -Generic industry recommendations for strong security controls are provided from sources such as the OWASP Top 10 Proactive Controls [i.24], Center for Internet Security (CIS) Critical Security Controls [i.25], Cloud Security Alliance (CSA) Cloud Control Matrix (CCM) [i.26], ISO/IEC 27001:2013 Information Security Management System (ISMS) [i.12], NIST SP 800-53r5 Security and Privacy Controls for Information Systems and Organizations [i.28], and Cybersecurity and Infrastructure Security Agency (CISA) Security Guidance for 5G Cloud Infrastructures [i.29]. - -AI/ML- specific industry recommendations for strong security controls are provided from e.g. ENISA [i.19], and OWASP [i.20]. - -The ENISA security controls recommendations are as follows: - -## Organisational: - -- Apply a RBAC model, respecting the least privileged principle -- Apply documentation requirements to AI projects -- Assess the regulations and laws the ML application must comply with -- Ensure ML applications comply with data security requirements -- Ensure ML applications comply with identity management, authentication, and access control policies -- Ensure ML applications comply with protection policies and are integrated to security operations processes -- Ensure ML applications comply with security policies -- Include ML applications into detection and response to security incident processes -- Include ML applications in asset management processes -- Integrate ML applications into the overall cyber-resilience strategy -- Integrate ML specificities to existing security policies - -## Technical: - -- Assess the exposure level of the model used -- Check the vulnerabilities of the components used so that they have an appropriate security level -- Conduct a risk analysis of the ML application -- Control all data used by the ML model -- Define and monitor indicators for proper functioning of the model -- Ensure appropriate protection is deployed for test environments -- Ensure ML applications comply with third parties' security requirements -- Ensure ML projects follow the global process for integrating security into projects - -## Specific ML: - -- Add some adversarial examples to the training dataset -- Apply modifications on inputs -- Build explainable models -- Choose and define a more resilient model design -- Enlarge the training dataset -- Ensure that models are unbiased -- Ensure that models respect differential privacy to a sufficient degree -- Ensure that the model is sufficiently resilient to the environment in which it will operate. -- Implement processes to maintain security levels of ML components over time -- Implement tools to detect if a data point is an adversarial example or not -- Integrate ML specificities to awareness strategy and ensure all ML stakeholders are receiving it -- Integrate poisoning control after the “model evaluation” phase -- Reduce the available information about the model -- Reduce the information given by the model -- Use federated learning to minimize risk of data breaches -- Use less easily transferable models - -OWASP recommends security controls related to their top 10 Machine Learning Security Risks. In sum they are: - -- Adversarial training -- Robust models -- Input/Data validation and verification -- Secure data storage -- Data separation -- Access control -- Testing, Monitoring and auditing -- Model validation -- Model ensembles -- Anomaly detection -- Model transparency -- Model retraining -- Model training on randomized or shuffled data -- Model Obfuscation -- Regularisation -- Reducing the training data -- Encryption -- Regular backups -- Watermarking -- Legal protection -- Verify Package Signatures -- Use Secure Package Repositories -- Keep Packages Up-to-date -- Use Virtual Environments -- Perform Code Reviews -- Use Package Verification Tools -- Educate Developers -- Regularly monitor and update the training datasets -- Use secure and trusted training datasets -- Implement model isolation -- Use differential privacy -- Perform regular security audits -- Verify the authenticity of feedback data -- Continuously train the model -- Tamper-evident logs -- Regular software updates - -With consideration of these external sources, the following security controls are being evaluated for the AI/ML risk analysis: - -- Control 1: Obfuscation ([i.20], in " ML05:2023 Model Stealing"): - - o Hiding the inner workings of an ML model by adding noise or complexity, making it harder for attackers to reverse engineer the model. Techniques include gradient masking and neuron shuffling. -- Control 2: Watermarking ([i.20], in " ML05:2023 Model Stealing"): - - o Embedding a unique digital fingerprint into the model's weights or architecture during training. If stolen and used without permission, the watermark can be detected, revealing the original owner. - - o Mitigations to prevent watermark stripping are: - - Dynamic Watermarking: Injects watermark signals at inference time instead of training, making it harder for attackers to isolate them through API queries or surrogate training ([i.68]) - - Hybrid Ownership Signatures: Combines multiple watermarking techniques - e.g., triggers, perturbations, spectral markers - for higher resilience. Attackers must bypass all layers to remove ownership traces ([i.66], [i.69]). -- Control 3: Encryption ([i.20], in " ML05:2023 Model Stealing"): - - o Encrypting the ML model, training data and other sensitive information. -- Control 4: Differential Privacy [i.37]: - - o Adding random noise to the training data or model's outputs, which helps maintain privacy while preserving overall accuracy. However, this method may introduce some error into the stolen model's predictions, making it less valuable for malicious use. - -- Control 5: Model Splitting [i.38]: - - o Divide a single ML model into multiple sub-models, each trained on a different part of the training data. Then, distribute these sub-models across different servers or organizations so that no single party has access to the complete model. This approach makes it harder for attackers to steal and reconstruct the original model. -- Control 6: Intellectual Property (IP) Protection ([i.20], in " ML05:2023 Model Stealing"): - - o Using copyright, patents, or trade secrets laws to protect your ML models as intellectual property. However, this method may not always deter sophisticated attackers, and enforcement can be challenging across international borders. -- Control 7: Access Control ([i.20], in " ML05:2023 Model Stealing"): - - o Implement access controls, such as role-based access control (RBAC) or attribute-based access control (ABAC), to restrict who can view, train, or deploy ML models within your organization. This approach helps prevent insider threats and unauthorized access. -- Control 8: Monitoring ([i.20], in " ML05:2023 Model Stealing"): - - o Continuously monitor model usage, data flows, and system logs for any suspicious activity that might indicate an attack in progress. Machine Learning Security (MLSec) tools can help detect such anomalies. -- Control 9: Training and Education ([i.20], in "ML06:2023 AI Supply Chain Attacks"): - - o Regularly train employees on best practices for ML model security, including how to recognize phishing attacks or social engineering attempts that could lead to model theft. Raising awareness of these threats can help reduce the likelihood of human error causing a breach. -- Control 10: Data Sanitisation ([i.39], [i.40]): - - o This technique involves cleaning and preprocessing input data to remove or encode any malicious characters or sequences that could be used to launch an attack, or access sensitive information. This includes techniques like input validation, encoding/decoding, and escaping special characters, but also de-identification or pseudonymization on the training dataset. -- Control 11: Feature Selection ([i.41], section 2.3.5): - - o By selecting a reduced set of relevant features for model training, this method can help reduce the likelihood of attacks by eliminating less important or redundant features that might be manipulated. Feature selection techniques include feature ranking (e.g., PCA) and dimensionality reduction (e.g., LDA). -- Control 12: Input Transformation ([i.42]): - - o This method involves applying mathematical transformations to input data, such as normalization or standardization, to make the inputs less susceptible to small perturbations that could lead to misclassification. Examples include Min-max scaling and Z-score normalization [i.32]. -- Control 13: Adversarial Training ([i.20], in "ML01:2023 Input Manipulation Attack"): - - o In this approach, a model is trained on both clean data and adversarial examples (inputs slightly perturbed to cause misclassifications). This can help the model become more robust against input manipulation attacks by learning to generalize better from noisy or corrupted inputs. -- Control 14: Ensemble Methods ([i.20], in "ML02:2023 Data Poisoning Attack"): - - o Combining multiple models with different architectures, feature representations, and training sets can improve overall model performance and reduce the likelihood of all models being fooled by the same attack. Techniques include voting classifiers ([i.33]) and stacked ensembles ([i.34]). -- Control 15: Robust Models ([i.20], in "ML01:2023 Input Manipulation Attack"): - - o This approach involves proving that a model's output will remain within a specified range for a given input region, which can help to certify the robustness of the model against small perturbations or adversarial examples. Techniques include formal verification and interval analysis. -- Control 16: Secure data acquisition ([i.20], in "ML01:2023 Input Manipulation Attack"): - - o Ensure that the data is acquired from trusted sources and maintain a proper chain of custody to prevent tampering during collection or preprocessing phases. -- Control 17: Model agility ([i.20], in "ML03:2023 Model Inversion Attack"): - - o Regularly update and retrain ML models with fresh and clean data to reduce the effectiveness of stale poisoned samples. This approach, coupled with techniques like model stacking or ensembles, can further enhance resilience against attacks. -- Control 18: Model Distillation ([i.43]): - - o This method involves training a smaller, less complex model (called a distilled or student model) on the softmax function outputs of a larger, more complex teacher model. The student model is designed to mimic the behaviour of the teacher model but with fewer parameters and reduced representational power. Attackers will have a harder time extracting sensitive information from the student model's intermediate representations compared to those of the original teacher model. -- Control 19: Secure Multi-Party Computation (SMPC) ([i.44]): - -- SMPC protocols allow for securely training models on distributed data without revealing the individual records to any party involved in the computation. By splitting both the input data and the model itself across multiple parties, membership inference attacks become much more difficult as no single party has access to the complete information required to perform the attack. -- Control 20: Code signing and verification ([i.20], in "ML06:2023 AI Supply Chain Attacks"): - - Signing machine learning code with strong cryptographic signatures can help ensure its authenticity and prevent unauthorized tampering during distribution. Verifying these signatures upon receipt ensures the integrity of the received codebase. -- Control 21: Hardware-based security measures: - - Using trusted execution environments (TEEs) or secure enclaves provided by hardware vendors such as Intel SGX, AMD SEV, or ARM TrustZone can isolate sensitive ML computations from potentially compromised parts of the software stack. This way, even if an attacker manages to compromise other portions of the system, they cannot tamper with the protected code and data within these secure enclaves. -- Control 22: Explainable Models ([i.19]): - - Ensuring that the inner workings and decision-making process of an ML model are interpretable can help detect anomalies in its behaviour more easily. Explainable AI (XAI) techniques, such as LIME ([i.35]) or SHAP ([i.36]), can be used to understand how each input feature contributes to a particular prediction, which can aid in identifying potential evasion attempts. -- Control 23: Data Augmentation ([i.45], clause 1.2.2): - - Increasing the diversity of the training data set can make it more robust against evasion attacks. By augmenting the data with various transformations (such as rotation, scaling, flipping, etc.), models are exposed to a wider range of input patterns and become less susceptible to small perturbations in input features. -- Control 24: Secure software supply chain management: - - Implementing secure software development practices for AI projects, including regular audit and update of outdated packages to patch known vulnerabilities. -- Control 25: Model Poisoning Control [i.19]: - - Integrate poisoning control after the "model evaluation" phase in the ML Training Host. Before moving the model to production and then on a regular basis, the model is evaluated to ensure it has not been poisoned. For example: deep learning classification algorithms can be checked for poisoning using the STRIP technique [i.60]. The principle is to disturb the inputs and observe the randomness of the predictions. -- Control 26: Energy and Latency Obfuscation [i.64]: - - Techniques such as adding noise to the power supply or equalizing computation times across different operations can help obscure the relationship between energy/latency and the actual computations being performed. -- Control 27: Secure Multi-Tenancy: - - For cloud environments, ensuring that different users' computations are properly isolated and do not interfere with each other is crucial to prevent cross-user energy-latency attacks. -- Control 28: Model Dependency Control: - - Checking AI/ML models do not depend on third-party libraries that contain known security vulnerabilities. - -# 8 Risk Assessment - -## 8.1 Introduction - -This clause provides risk assessment tables for each of the identified assets. These tables list the assets, threats, impacts, and possible security controls. - -A malicious actor may be a nation-state adversary, cybercriminal, or employee. In a ZTA, perimeter defences alone are insufficient. AI/ML must be protected from untrusted external sources attempting to have access, while also assuming internal threat actors are inside the network with access to its functions and data. Security controls for a ZTA, protecting against external and internal threats, should be implemented through a risk-based approach. A risk analysis calculates risk levels by assessing the threat's Likelihood of attack and the Impact from the attack. External and internal threats are from the perspective of the O-RAN architecture. External Threats are external to the O-RAN and Internal Threats are internal to O-RAN. - -Impact scores can be lowered with consideration of existing security controls. Impact scoring is based upon current security controls. Impact scoring does not consider security controls that may be potentially specified in the future. - -Likelihood scores may be higher when the goal is a ZTA, because external and internal threats must be considered. When likelihood scoring during a risk analysis, it is necessary to consider internal threats performing reconnaissance attacks impacting confidentiality and privacy and attacks causing damage or degrading performance impacting availability. Internal threat actors are less likely to perform damaging attacks that are quickly and easily detected and blocked, but more likely to attempt reconnaissance attacks to collect information. As a result, reconnaissance type attacks can be scored Likelihood = High while damaging/availability attacks can be scored Likelihood = Medium or Low. - -This risk assessment covers the identified assets and not the organization implementing the AI system. There may be additional risks that are not apparent at the system level. A voluntary framework to define and manage risk at the organizational level is described in [i.10]. Some of the threats documented in this report may be used as content when performing the MAP and MANAGE functions described in [i.10]. - -## 8.2 Input Manipulation Attack (ML01:2023) - -Table 8.2-1 AI/ML Risk Analysis – Input Manipulation Attack - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/ Likelihood Raw Score | Possible Security Controls | Security Control-id | -|------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|-------------|----------------------------|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------| -| ASSET-D-25,
ASSET-D-26,
ASSET-D-27,
ASSET-D-28 | Training or test data, Trained ML model, ML prediction results, ML system behaviour | T-AIML-IM-1 | Training Data Control | Impact = High
Likelihood = High | Access Control, Monitoring, Data Sanitisation, Feature Selection, Input Transformation, Secure data acquisition, | Control 7
Control 8
Control 10
Control 11
Control 12
Control 16 | -| ASSET-D-25,
ASSET-D-26,
ASSET-D-27,
ASSET-D-28 | Training or test data, Trained ML model, ML prediction results, ML system behaviour | T-AIML-IM-2 | Testing Data Control | Impact = High
Likelihood = Medium | Access Control, Monitoring, Data Sanitisation, Feature Selection, Input Transformation, Adversarial Training, Robust Models, Secure data acquisition | Control 7
Control 8
Control 10
Control 11
Control 12
Control 13
Control 15
Control 16 | -| ASSET-D-25,
ASSET-D-26,
ASSET-D-27,
ASSET-D-28 | Training or test data, Trained ML model, ML prediction results, ML system behaviour | T-AIML-IM-3 | Label Manipulation | Impact = High
Likelihood = Medium | Access Control, Monitoring, Data Sanitisation, Feature Selection, Input transformation, Secure data acquisition | Control 7
Control 8
Control 10
Control 11
Control 12
Control 16 | -| ASSET-D-08,
ASSET-D-25,
ASSET-D-26,
ASSET-D-27,
ASSET-D-28 | A1 Enrichment Information, Training or test data, Trained ML model, ML prediction results, ML system behaviour | T-AIML-IM-4 | AI/ML Query Exploitation | Impact = High
Likelihood = High | Adversarial Training | Control 13 | - -## 8.3 Data poisoning attacks (ML02:2023) - -Table 8.3-1 AI/ML Risk Analysis - Data poisoning attacks - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/ Likelihood Raw Score | Possible Security Controls | Security Control-id | -|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|----------------------------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-C-12,
ASSET-D-10,
ASSET-D-25,
ASSET-D-26,
ASSET-C-61 | Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
ML components,
Database data,
Training data,
Trained ML model,
AI/ML Workflow | T-AIML-DP-01 | Black-box Data Poisoning | Impact= High
Likelihood= Medium | Access control,
Monitoring,
Data Sanitisation,
Feature Selection,
Input Transformation,
Adversarial Training,
Ensemble Methods,
Secure data acquisition,
Model agility,
Data Augmentation | Control 7,
Control 8,
Control 10,
Control 11,
Control 12,
Control 13,
Control 14,
Control 16,
Control 17,
Control 23 | -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-C-12,
ASSET-C-14,
ASSET-C-22,
ASSET-C-40,
ASSET-D-10,
ASSET-D-25,
ASSET-D-26,
ASSET-C-61 | Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
ML components,
O1-, A1-, E2- Interface,
Database data,
Training data,
Trained ML model,
AI/ML Workflow | T-AIML-DP-02 | Grey-box Data Poisoning | Impact= High
Likelihood= Medium | Access control,
Monitoring,
Data Sanitisation,
Feature Selection,
Input Transformation,
Adversarial Training,
Ensemble Methods,
Secure data acquisition,
Model agility,
Data Augmentation | Control 7,
Control 8,
Control 10,
Control 11,
Control 12,
Control 13,
Control 14,
Control 16,
Control 17,
Control 23 | -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-C-12,
ASSET-C-14,
ASSET-C-22,
ASSET-C-40,
ASSET-D-10,
ASSET-D-25,
ASSET-D-26,
ASSET-C-61 | Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
ML components,
O1-, A1-, E2- Interface,
Database data,
Training data,
Trained ML model,
AI/ML Workflow | T-AIML-DP-03 | White-box Data Poisoning | Impact= High
Likelihood= Medium | Access control,
Monitoring,
Data Sanitisation,
Feature Selection,
Input Transformation,
Adversarial Training,
Ensemble Methods,
Secure data acquisition,
Model agility,
Data Augmentation | Control 7,
Control 8,
Control 10,
Control 11,
Control 12,
Control 13,
Control 14,
Control 16,
Control 17,
Control 23 | - -## 8.4 Model Inversion Attack (ML03:2023) - -Table 8.4-1 AI/ML Risk Analysis – Model Inversion Attack - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/ Likelihood Raw Score | Possible Security Controls | Security Control-id | -|------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|---------------|----------------------------|----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------| -| ASSET-D-10,
ASSET-D-25,
ASSET-D-26,
ASSET-D-27,
ASSET-D-28 | Database data,
Training data,
Trained ML model,
ML prediction results,
ML system behaviour | T-AIML-MOI-01 | Black-box Model Inversion | Impact= High
Likelihood= High | Obfuscation,
Differential Privacy,
Model Splitting,
Access Control,
Monitoring,
Data Sanitisation,
Model agility,
Secure Multi-Party Computation (SMPC) | Control 1,
Control 4,
Control 5,
Control 7,
Control 8,
Control 10,
Control 17,
Control 19 | -| ASSET-D-10,
ASSET-D-25,
ASSET-D-26, | Database data,
Training data,
Trained ML model, | T-AIML-MOI-02 | White-box Model Inversion | Impact= High
Likelihood= High | Obfuscation
Differential Privacy
Model Splitting | Control 1
Control 4
Control 5 | - -| | | | | | | | -|---------------------------|-----------------------------------------------|--|--|--|---------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------| -| ASSET-D-27,
ASSET-D-28 | ML prediction results,
ML system behaviour | | | | Access Control
Monitoring
Data Sanitisation,
Model agility,
Secure Multi-Party
Computation
(SMPC) | Control 7
Control 8
Control 10,
Control 17,
Control 19 | -|---------------------------|-----------------------------------------------|--|--|--|---------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------| - -## 8.5 Membership Inference Attack (ML04:2023) - -Table 8.5-1 AI/ML Risk Analysis - Membership Inference Attacks - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/ Likelihood Raw Score | Possible Security Controls | Security Control-id | -|------------------------------------------|-------------------------------------------------|---------------|--------------------------------------------|------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| -| ASSET-C-02,
ASSET-C-11,
ASSET-D-26 | Near-RT RIC,
Non-RT RIC,
Trained ML model | T-AIML-MEI-01 | Information access – Membership Inference | Impact= High
Likelihood= Medium | Differential Privacy,
Access Control,
Monitoring,
Feature Selection,
Input Transformation,
Adversarial Training,
Model agility,
SMPC | Control 4,
Control 7,
Control 8,
Control 11,
Control 12,
Control 13,
Control 17,
Control 19 | -| ASSET-C-02,
ASSET-C-11,
ASSET-D-26 | Near-RT RIC,
Non-RT RIC,
Trained ML model | T-AIML-MEI-02 | Inference Technique – Membership Inference | Impact= High
Likelihood= Medium | Differential Privacy,
Monitoring,
Feature Selection,
Input Transformation,
Adversarial Training,
Model agility,
Model Distillation,
SMPC | Control 4,
Control 8,
Control 11,
Control 12,
Control 13,
Control 17,
Control 18,
Control 19 | -| ASSET-C-02,
ASSET-C-11,
ASSET-D-26 | Near-RT RIC,
Non-RT RIC,
Trained ML model | T-AIML-MEI-03 | Target based – Membership Inference | Impact= High
Likelihood= Medium | Encryption,
Differential Privacy,
Access Control,
Monitoring,
Feature Selection,
Input Transformation,
Adversarial Training,
Model agility,
SMPC | Control 3,
Control 4,
Control 7,
Control 8,
Control 11,
Control 12,
Control 13,
Control 17,
Control 19 | - -## 8.6 Model Stealing (ML05:2023) - -Table 8.6-1 AI/ML Risk Analysis – Model Stealing - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/ Likelihood Raw Score | Possible Security Controls | Security Control-id | -|---------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|--------------|----------------------------------------|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------| -| ASSET-C-02,
ASSET-C-11,
ASSET-D-10,
ASSET-D-25,
ASSET-D-26,
ASSET-C-61 | Near-RT RIC,
Non-RT RIC,
Database data,
Training data,
Trained ML model,
AI/ML Workflow | T-AIML-ME-01 | Intellectual Property Theft | Impact= High
Likelihood= Low | Obfuscation,
Watermarking,
Encryption,
Differential Privacy,
Model Splitting,
Intellectual Property (IP) Protection,
Access control,
Monitoring,
Training and Education | Control 1,
Control 2,
Control 3,
Control 4,
Control 5,
Control 6,
Control 7,
Control 8,
Control 9 | -| ASSET-C-02,
ASSET-C-11,
ASSET-D-10,
ASSET-D-25,
ASSET-D-26,
ASSET-C-61 | Near-RT RIC,
Non-RT RIC,
Database data,
Training data,
Trained ML model,
AI/ML Workflow | T-AIML-ME-02 | Data Privacy Violations | Impact= High
Likelihood= Low | Obfuscation,
Encryption,
Differential Privacy,
Model Splitting,
Access control,
Monitoring,
Training and Education | Control 1,
Control 3,
Control 4,
Control 5,
Control 8,
Control 9 | -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04, | Near-RT RIC,
O-CU-CP,
O-CU-UP, | T-AIML-ME-03 | Adversarial Attacks with Stolen Models | Impact= High
Likelihood= Low | Obfuscation,
Encryption,
Differential Privacy, | Control 1,
Control 3,
Control 4, | - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/ Likelihood Raw Score | Possible Security Controls | Security Control-id | -|------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------|-----------|----------------------------|------------------------------|------------------------------------------------------------------------------|---------------------------------------| -| ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-D-10,
ASSET-D-25,
ASSET-D-26,
ASSET-C-61 | O-DU,
O-eNB,
Non-RT RIC,
Database data,
Training data,
Trained ML model,
AI/ML Workflow | | | | Model Splitting,
Access control,
Monitoring,
Training and Education | Control 5,
Control 8,
Control 9 | - -## 8.7 AI Supply Chain Attacks (ML06:2023) - -Table 8.7-1 AI/ML Risk Analysis - AI Supply Chain Attacks - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/ Likelihood Raw Score | Possible Security Controls | Security Control-id | -|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-C-12,
ASSET-D-10,
ASSET-D-25,
ASSET-D-26,
ASSET-C-61 | Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
ML components,
Database data,
Training data,
Trained ML model,
AI/ML Workflow | T-AIML-SC-01 | Data Poisoning via Supply Chain | Impact= High
Likelihood= Medium | Access Control,
Monitoring,
Data Sanitisation,
Feature Selection,
Input Transformation,
Adversarial Training,
Ensemble Methods,
Secure data acquisition,
Model agility,
Code signing and verification | Control 7,
Control 8,
Control 10,
Control 11,
Control 12,
Control 13,
Control 14,
Control 16,
Control 17,
Control 20 | -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-C-12,
ASSET-D-10,
ASSET-D-25,
ASSET-D-26,
ASSET-C-61 | Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
ML components,
Database data,
Training data,
Trained ML model,
AI/ML Workflow | T-AIML-SC-02 | Model Tampering | Impact= High
Likelihood= Medium | Access Control,
Monitoring,
Data Sanitisation,
Feature Selection,
Input Transformation,
Adversarial Training,
Ensemble Methods,
Secure data acquisition,
Model agility,
Code signing and verification | Control 7,
Control 8,
Control 10,
Control 11,
Control 12,
Control 13,
Control 14,
Control 16,
Control 17,
Control 20 | -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-C-12,
ASSET-D-10,
ASSET-D-26,
ASSET-C-61 | Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
ML components,
Database data,
Trained ML model,
AI/ML Workflow | T-AIML-SC-03 | Backdoor via Supply Chain | Impact= High
Likelihood= Low | Access Control,
Monitoring,
Feature Selection,
Input Transformation,
Ensemble Methods,
Secure data acquisition,
Model agility,
Code signing and verification,
Explainable Models | Control 7,
Control 8,
Control 11,
Control 12,
Control 14,
Control 16,
Control 17,
Control 20,
Control 22 | -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-C-12,
ASSET-D-10,
ASSET-D-26,
ASSET-C-61 | Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
ML components,
Database data,
Trained ML model,
AI/ML Workflow | T-AIML-SC-04 | Hardware Tampering | Impact= High
Likelihood= Low | Access Control,
Monitoring,
Code signing and verification,
Hardware-based security measures | Control 7,
Control 8,
Control 20,
Control 21 | -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-C-12,
ASSET-D-10, | Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
ML components,
Database data, | T-AIML-SC-05 | Insecure Maintenance APIs | Impact= Medium
Likelihood= Medium | Encryption,
Access Control,
Monitoring,
Data Sanitisation,
Code signing and verification measures | Control 3,
Control 7,
Control 8,
Control 10,
Control 20 | - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/ Likelihood Raw Score | Possible Security Controls | Security Control-id | -|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|----------------------------------------|----------------------------------|-----------------------------------------------------------------------------------------------------------------|------------------------------------------| -| ASSET-D-25,
ASSET-D-26,
ASSET-C-61 | Training data,
Trained ML model,
AI/ML Workflow | | | | | | -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-C-12,
ASSET-D-10,
ASSET-D-25,
ASSET-D-26,
ASSET-C-61 | Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
ML components,
Database data,
Training data,
Trained ML model,
AI/ML Workflow | T-AIML-SC-06 | Third-party Libraries and Dependencies | Impact= High
Likelihood= High | Code signing and verification measures,
Secure software supply chain management,
Model dependency control | Control 20,
Control 24,
Control 28 | - -## 8.8 Transfer Learning Attack (ML07:2023) - -Table 8.8-1 AI/ML Risk Analysis - Transfer Learning Attack - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/ Likelihood Raw Score | Possible Security Controls | Security Control-id | -|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------------------------------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-C-12,
ASSET-D-10,
ASSET-D-25,
ASSET-D-26,
ASSET-C-61 | Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
ML components,
Database data,
Training data,
Trained ML model,
AI/ML Workflow | T-AIML-TL-01 | Data Poisoning for Transfer Learning | Impact= High
Likelihood= Medium | Monitoring,
Data Sanitisation,
Feature Selection,
Input Transformation,
Adversarial Training,
Ensemble Methods,
Secure data acquisition,
Model agility | Control 8,
Control 10,
Control 11,
Control 12,
Control 13,
Control 14,
Control 16,
Control 17 | -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-C-12,
ASSET-D-10,
ASSET-D-25,
ASSET-D-26,
ASSET-C-61 | Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
ML components,
Database data,
Training data,
Trained ML model,
AI/ML Workflow | T-AIML-TL-02 | Model Stealing for Transfer Learning | Impact= High
Likelihood= Low | Obfuscation,
Watermarking,
Encryption,
Differential Privacy,
Model Splitting,
Intellectual Property (IP) Protection,
Access control,
Monitoring,
Training and Education | Control 1,
Control 2,
Control 3,
Control 4,
Control 5,
Control 6,
Control 7,
Control 8,
Control 9 | -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-C-12,
ASSET-D-10,
ASSET-D-25,
ASSET-D-26 | Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
Database data,
Training data,
Trained ML model | T-AIML-TL-03 | Adversarial Examples | Impact= High
Likelihood= Low | Obfuscation,
Encryption,
Differential Privacy,
Model Splitting,
Access control,
Monitoring,
Training and Education | Control 1,
Control 3,
Control 4,
Control 5,
Control 8,
Control 9 | -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-C-12,
ASSET-D-10,
ASSET-D-25,
ASSET-D-26,
ASSET-C-61 | Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
ML components,
Database data,
Training data,
Trained ML model,
AI/ML Workflow | T-AIML-TL-04 | Backdoor for Transfer Learning | Impact= High
Likelihood= Low | Access Control,
Monitoring,
Feature Selection,
Input Transformation,
Ensemble Methods,
Secure data acquisition,
Model agility,
Code signing and verification,
Explainable Models | Control 7,
Control 8,
Control 11,
Control 12,
Control 14,
Control 16,
Control 17,
Control 20,
Control 22 | - -## 8.9 Model Skewing (ML08:2023) - -Table 8.9-1 AI/ML Risk Analysis – Model Skewing Attacks - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/ Likelihood Raw Score | Possible Security Controls | Security Control-id | -|---------------------------------------------------------|---------------------------------------------------------------------|--------------|-----------------------------------------|------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------| -| ASSET-D-26,
ASSET-D-27,
ASSET-D-28,
ASSET-C-61 | ML model,
ML Prediction Results,
ML system,
AI/ML Workflow | T-AIML-MS-01 | Data Manipulation for Model Skewing | Impact= High
Likelihood= Medium | Access Control,
Monitoring,
Data Sanitation,
Feature Selection,
Input Transformation,
Adversarial Training,
Robust Models,
Model agility,
Explainable models | Control 7,
Control 8,
Control 10,
Control 11,
Control 12,
Control 13,
Control 15,
Control 17,
Control 22 | -| ASSET-D-26,
ASSET-D-27,
ASSET-D-28 | ML model,
ML Prediction Results,
ML system | T-AIML-MS-02 | Feedback Manipulation for Model Skewing | Impact= High
Likelihood= Medium | Monitoring,
Data sanitation,
Feature Selection,
Input Transformation,
Adversarial Training,
Model agility,
Explainable models,
Data Augmentation | Control 8,
Control 10,
Control 11,
Control 12,
Control 13,
Control 17,
Control 22,
Control 23 | - -## 8.10 Output Integrity Attack (ML09:2023) - -Table 8.10-1 AI/ML Risk Analysis – Output Integrity attacks - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/ Likelihood Raw Score | Possible Security Controls | Security Control-id | -|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|----------------------------------------------|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------| -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-D-07,
ASSET-D-25,
ASSET-D-26,
ASSET-D-27,
ASSET-D-11,
ASSET-C-61 | Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
AI policies,
Training data,
Trained ML model,
ML prediction results,
E2 node data,
AI/ML Workflow | T-AIML-OI-01 | Denial of Service impacting Output Integrity | Impact= High
Likelihood= Medium | Encryption,
Access Control,
Monitoring,
Secure data acquisition,
Explainable Models,
Secure software supply chain management | Control 3,
Control 7,
Control 8,
Control 16,
Control 22,
Control 24 | -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-D-07,
ASSET-D-09,
ASSET-D-11,
ASSET-D-25,
ASSET-D-26,
ASSET-D-27,
ASSET-C-61 | Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
AI policies,
Data transported over the E2 interface,
E2 node data,
Training data,
Trained ML model,
ML prediction results,
AI/ML Workflow | T-AIML-OI-02 | Subscriber QoE Change | Impact= High
Likelihood= Low | Encryption,
Access Control,
Monitoring,
Secure data acquisition,
Explainable Models,
Secure software supply chain management | Control 3,
Control 7,
Control 8,
Control 16,
Control 22,
Control 24 | - -## 8.11 Model Poisoning (ML10:2023) - -Table 8.11-1 AI/ML Risk Analysis – Model Poisoning Attacks - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/Likelihood Raw Score | Possible Security Controls | Security Control-id | -|---------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|--------------|-------------------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------| -| ASSET-D-26,
ASSET-C-12,
ASSET-D-27,
ASSET-C-61 | Trained ML model, ML components, ML prediction results, AI/ML Workflow | T-AIML-MP-01 | Model Parameter Poisoning | Impact=High
Likelihood=High | Access Control, Monitoring, Secure software supply chain management, Model Poisoning Control, Explainable Models | Control 7, Control 8, Control 24, Control 25, Control 22 | -| ASSET-D-26,
ASSET-D-27 | Trained ML model, ML prediction results | T-AIML-MP-02 | Inference Algorithm Poisoning | Impact=High
Likelihood=High | Access Control, Monitoring, Code Signing and verification, Secure software supply chain management, Explainable Models | Control 7, Control 8, Control 20, Control 24, Control 22 | -| ASSET-D-40,
ASSET-C-12,
ASSET-C-61 | ML models, ML components, AI/ML Workflow | T-AIML-MP-03 | Learning Algorithm Poisoning | Impact=High
Likelihood=High | Access Control, Monitoring, Code Signing and verification, Secure software supply chain management, Explainable Models | Control 7, Control 8, Control 20, Control 24, Control 22 | -| ASSET-C-12,
ASSET-D-26,
ASSET-D-27,
ASSET-D-28,
ASSET-D-40,
ASSET-C-61 | ML components, Trained ML model, ML prediction results, ML system behaviour, ML models, AI/ML Workflow | T-AIML-MP-04 | Model Control | Impact = High
Likelihood = Medium | Access Control, Monitoring, Data Sanitization, Input Transformation, Adversarial Training, Robust Models, Secure data acquisition | Control 7
Control 8
Control 10
Control 12
Control 13
Control 15
Control 16 | - -## 8.12 Evasion attacks - -Table 8.12-1 AI/ML Risk Analysis - Evasion attacks - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/Likelihood Raw Score | Possible Security Controls | Security Control-id | -|------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|--------------|--------------------------------------|------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-D-10,
ASSET-D-25,
ASSET-D-26 | Near-RT RIC, O-CU-CP, O-CU-UP, O-DU, O-eNB, Non-RT RIC, Database data, Training data, Trained ML model | T-AIML-EV-01 | Grey-box based Data Evasion | Impact= High
Likelihood= Medium | Obfuscation, Encryption, Access Control, Monitoring, Data Sanitisation, Adversarial Training, Robust Models, Data Augmentation | Control 1, Control 3, Control 7, Control 8, Control 10, Control 13, Control 15, Control 23 | -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-D-10,
ASSET-D-25,
ASSET-D-26 | Near-RT RIC, O-CU-CP, O-CU-UP, O-DU, O-eNB, Non-RT RIC, Database data, Training data, Trained ML model | T-AIML-EV-02 | White-box based data evasion attacks | Impact= High
Likelihood= Medium | Obfuscation, Encryption, Access Control, Monitoring, Data Sanitisation, Adversarial Training, Robust Models, Data Augmentation | Control 1, Control 3, Control 7, Control 8, Control 10, Control 13, Control 15, Control 23 | -| ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-D-10,
ASSET-D-25,
ASSET-D-26 | Near-RT RIC, O-CU-CP, O-CU-UP, O-DU, O-eNB, Non-RT RIC, Database data, Training data, Trained ML model | T-AIML-EV-03 | Black-box based data evasion attacks | Impact= High
Likelihood= Medium | Obfuscation, Encryption, Access Control, Monitoring, Data Sanitisation, Adversarial Training, Robust Models, Data Augmentation | Control 1, Control 3, Control 7, Control 8, Control 10, Control 13, Control 15, Control 23 | - -## 8.13 AI Energy-Latency Attack - -Table 8.13-1 AI/ML Risk Analysis - AI Energy-Latency Attack - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/Likelihood Raw Score | Possible Security Controls | Security Control-id | -|---------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------------------------------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| -| ASSET-D-10,
ASSET-D-26,
ASSET-C-02,
ASSET-C-11,
ASSET-C-29,
ASSET-C-30 | Database data,
ML model,
Near-RT RIC,
Non-RT RIC,
AAL software,
accelerator firmware | T-AIML-EL-01 | Model Extraction | Impact= High
Likelihood= Medium | Differential Privacy,
Access Control,
Monitoring, Data Sanitization, Secure data acquisition,
Model agility,
Hardware-based security measures,
Explainable Models, Energy and Latency Obfuscation, secure multi-tenancy | Control 4,
Control 7,
Control 8,
Control 10,
Control 16,
Control 17,
Control 21,
Control 22,
Control 26,
Control 27 | -| ASSET-D-10,
ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-C-29,
ASSET-C-30 | Database data,
Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
AAL software,
accelerator firmware | T-AIML-EL-02 | Data Inference | Impact= High
Likelihood= Medium | Differential Privacy,
Access Control,
Monitoring, Data Sanitization, Secure data acquisition,
Model agility,
Hardware-based security measures,
Explainable Models, Energy and Latency Obfuscation, secure multi-tenancy | Control 4,
Control 7,
Control 8,
Control 10,
Control 16,
Control 17,
Control 21,
Control 22,
Control 26,
Control 27 | -| ASSET-D-10,
ASSET-D-26,
ASSET-C-02,
ASSET-C-03,
ASSET-C-04,
ASSET-C-05,
ASSET-C-07,
ASSET-C-11,
ASSET-C-29,
ASSET-C-30 | Database data,
ML model,
Near-RT RIC,
O-CU-CP,
O-CU-UP,
O-DU,
O-eNB,
Non-RT RIC,
AAL software,
accelerator firmware | T-AIML-EL-03 | Denial of Service via Side Channels | Impact= High
Likelihood= Medium | Differential Privacy,
Access Control,
Monitoring, Data Sanitization, Secure data acquisition,
Model agility,
Hardware-based security measures,
Explainable Models, Energy and Latency Obfuscation, secure multi-tenancy | Control 4,
Control 7,
Control 8,
Control 10,
Control 16,
Control 17,
Control 21,
Control 22,
Control 26,
Control 27 | - -# 9 Primary Issues - -The field of AI/ML security is a rapidly evolving area that has garnered significant attention in recent years due to the growing adoption of these technologies across various domains. While there have been many advances in both research and standardization efforts, it could still be considered as being in an early stage compared to the overall maturity of AI/ML itself. - -In terms of research, there is a burgeoning community focused on AI/ML security. This includes work on adversarial examples, privacy-preserving machine learning, and formal verification techniques for deep neural networks. However, much of this work remains theoretical or confined to specific settings. Also, many AI/ML models are currently evaluated based on their accuracy or performance on specific tasks, but there is often little consideration given to their security properties. This can lead to vulnerabilities that can be exploited by attackers. There's still a need for more practical, scalable solutions that can be easily adopted by practitioners without requiring specialized expertise in security or AI/ML. - -In terms of standardization, there have been some initial efforts such as the NIST Privacy Framework ([i.56]) and GDPR's "data protection by design" principle ([i.57]) which touch upon AI/ML security but do not specifically address it comprehensively. Organizations like IEEE ([i.55]), ISO ([i.58]), ETSI ([i.49]) and ITU ([i.59]) are also working on developing more targeted standards for AI/ML security; however, these efforts are at various stages of maturity and may take some time before they yield tangible results. - -To advance the state of AI/ML security, several things are missing: - -1. **More foundational research:** There's a need for deeper understanding of the inherent tradeoffs between privacy, model performance, and security in machine learning systems. This will help inform better-informed design decisions and guide standardization efforts. More specifically there is a need for more research on explainability and interpretability in AI/ML systems. Currently, many AI/ML models are "black boxes" that make decisions based on complex mathematical calculations that are difficult to understand or interpret. This lack of transparency can make it difficult to identify when an AI/ML system has been compromised or manipulated. Developing techniques for explaining and interpreting the decision-making processes of AI/ML systems will be important for ensuring their security. - -2. **Practical tools and frameworks:** Researchers should focus on developing easy-to-use, scalable, and open-source tools for AI/ML security that can be seamlessly integrated into existing development pipelines without significant overheads. - -3. **Collaboration between researchers and practitioners:** Closer collaboration between academia, industry, and government stakeholders is crucial to ensure the relevance of research findings and inform policy decisions based on real-world needs. - -4. **Awareness and education:** There's a need for greater awareness and education about AI/ML security among practitioners, developers, and end-users alike so that they are aware of potential risks and best practices to mitigate them. - -5. **Comprehensive standardization efforts:** Standardization bodies should prioritize the development of comprehensive, industry-wide standards for AI/ML security that take into account privacy, safety, and robustness considerations. These standards should be flexible enough to accommodate future advances in technology while providing a baseline for assessing compliance and promoting interoperability. - -In summary, while significant progress has been made in the field of AI/ML security, there is still much work to be done. Developing robust testing and evaluation frameworks, researching adversarial attacks and defences, improving explainability and interpretability, and standardizing approaches to security will all be important areas of focus in the coming years. - -# 10 Recommendations - -## 10.1 General - -This is a list of recommendations on next steps to be done on the contents of the present document in future revisions and on other O-RAN specifications based on the current state of this document. - -**Recommendation 1:** This work item should contribute to the WG11 Security Requirements specifications [i.2] with new requirements and security controls from the solutions outlined in this report. CRs will be generated as required. - -**Recommendation 2:** This work item should contribute security test cases for relevant security requirements to the WG11 Security Test specification [i.5]. CRs will be generated as required. - -**Recommendation 3:** This work item should contribute to the WG11 Security Protocols specifications [i.3] with new protocol-related requirements and controls from the solutions outlined in this report. CRs will be generated as required. - -**Recommendation 4:** This work item should contribute to the WG11 O- Security Threat Modeling and Remediation Analysis [i.4] with new threats and risks from the key issues outlined in this report. CRs will be generated as required. - -**Recommendation 5:** WG11 should collaborate with WG2 and WG3 to ensure the WG11 security specifications are appropriately referenced by WG2 and WG3 in their specifications. - -## 10.2 Managing Risk - -There may be additional risks to an organization implementing or operating an AI/ML application or component as part of their service infrastructure. These risks may be non-technical in nature and involve regulatory or business risk that also must be managed, or technical risks that include a non-technical portion to their mitigation strategy. Organizations should include these risks in their comprehensive risk management strategy by using a framework described in [i.10], or similar frameworks that may be required in the area of operation. - -## 10.3 Security Controls to be addressed in normative specification - -The following table captures security controls that are defined in clause 7 of the present document to be covered by WG11 normative specification. - -**Table 10.3-1 Security Controls to be covered by normative specification** - -| SC# | Security Control name | Type of Security Control | To be covered by specification | -|-----|-----------------------------------------|--------------------------|--------------------------------| -| 1 | (Model) Obfuscation | MAY O-RAN requirement | yes | -| 2 | (Model) Watermarking | MAY O-RAN requirement | yes | -| 3 | Encryption | SHALL O-RAN requirement | yes | -| 4 | Differential Privacy | MAY O-RAN requirement | yes | -| 5 | Model Splitting | MAY O-RAN requirement | yes | -| 6 | Intellectual Property (IP) Protection | outside of O-RAN-scope | no | -| 7 | Access Control | SHALL O-RAN requirement | yes | -| 8 | Monitoring | SHALL O-RAN requirement | yes | -| 9 | Training and Education | outside of O-RAN-scope | no | -| 10 | Data Sanitisation | MAY O-RAN requirement | yes | -| 11 | Feature Selection | MAY O-RAN requirement | yes | -| 12 | Input Transformation | MAY O-RAN requirement | yes | -| 13 | Adversarial Training | MAY O-RAN requirement | yes | -| 14 | Ensemble Methods | MAY O-RAN requirement | yes | -| 15 | Robust Models | MAY O-RAN requirement | yes | -| 16 | Secure data acquisition | SHALL O-RAN requirement | yes | -| 17 | Model agility | MAY O-RAN requirement | yes | -| 18 | Model Distillation | MAY O-RAN requirement | yes | -| 19 | Secure Multi-Party Computation (SMPC) | MAY O-RAN requirement | yes | -| 20 | Code signing and verification | SHALL O-RAN requirement | yes | -| 21 | Hardware-based security measures | MAY O-RAN requirement | yes | -| 22 | Explainable Models | MAY O-RAN requirement | yes | -| 23 | Data Augmentation | MAY O-RAN requirement | yes | -| 24 | Secure software supply chain management | SHALL O-RAN requirement | yes | -| 25 | Model Poisoning Control | MAY O-RAN requirement | yes | -| 26 | Energy and Latency Obfuscation | MAY O-RAN requirement | yes | -| 27 | Secure Multi-Tenancy | SHALL O-RAN requirement | yes | - -# Annex A (informative): Attack Mapping to NIST AML Taxonomy - -To ensure comprehensive coverage of AI/ML attacks in this technical report, a gap analysis was conducted using a NIST Trustworthy and Responsible AI Report, NIST AI 100-2e2023 titled, “Adversarial Machine Learning: A Taxonomy and terminology of Attacks and Mitigations [i.9] as a reference. What follows is a table (Table A-1) that documents the mapping between attacks listed in this technical report and the attacks enumerated in Figure 1 of [i.9]. There was an attempt to list the section number from [i.9] where the attack is described. However, some of the attacks in [i.9] have dedicated sections while other attacks are referred inside a major section. Any inconsistencies in the below table (Table A-1) regarding section numbers in [i.9] will be a result of that document’s formatting inconsistency. - -There are three attacks (i.e., transfer learning attack, model skewing, and output integrity attack) listed in this technical report where there are no equivalent attacks listed in Figure 1 of [i.9]. - -The Transfer Learning Attack does have treatment in [i.9]. However, it is not listed within the taxonomy diagram in Figure 1. It appears that [i.9] has left this out as it is considered an inherent model property that attackers can take advantage of and not an attack itself. For this technical report it is important to call out this attack specifically as there are specific mitigations referenced. - -The Model Skewing attack is covered by [i.9] in section 2.3 titled Data Poisoning. - -The Output Integrity Attack is not encompassed in [i.9]. This type of attack specifically targets the output data from an AI/ML model. As [i.9] is exclusively concerned with attacks that target the inputs and processing in a model, the Output Integrity Attack falls outside its scope. This is shown in the table (Table A-1) below with the text “out of scope for [i.9]”. - -**Table A-1. Mapping of AI/ML TR attacks with NIST AML Taxonomy of attacks** - -| AI/ML TR Attacks (Clause and Attack Name) | [i.9] Attacks (Section and Attack Name) | -|------------------------------------------------------------|-----------------------------------------| -| 5.3.2 Input Manipulation Attacks
5.3.12 Evasion Attacks | 2.2.2 Black-Box Evasion | -| | 2.2 Evasion | -| 5.3.3 Data Poisoning Attacks | 2.1.3 Clean-Label Poisoning | -| | 2.3.2 Targeted Poisoning | -| | 2.3 Data Poisoning | -| 5.3.4 Model Inversion Attacks | 2.4.1 Reconstruction | -| 5.3.5 Membership Inference Attacks | 2.4.2 Membership Inference | -| | 2.4.4 Property Inference | -| 5.3.6 Model Stealing Attacks | 2.4.3 Model Extraction | -| 5.3.7 AI Supply Chain Attacks | 2.3.3 Backdoor Poisoning | -| | 2.3.3 Clean-Label Backdoor | -| 5.3.8 Transfer Learning Attacks | 2.2.3 Transferability of Attacks | -| 5.3.9 Model Skewing Attacks | 2.3 Data Poisoning | -| 5.3.10 Output Integrity Attacks | Outside scope for [i.9] | - -| | | -|---------------------------------|-----------------------| -| 5.3.11 Model Poisoning Attacks | 2.3.4 Model Poisoning | -| 5.3.X AI Energy-Latency Attacks | 3.4.1 Energy Latency | - -# Annex: Change history/Change request (history) - -| Date | Revision | Description | -|------------|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2023.03.28 | V0.00.01 | Document creation, template | -| 2023.04.26 | V0.00.02 | Approved draft with comments incorporated | -| 2023.06.06 | V0.00.03 | Incorporated approved CR : ATT-2023.04.26-WG11-CR-0020-TR-AIMLSecurityAssets | -| 2023.10.19 | V00.00.04 | Incorporated approved CRs :
NOK-2023.06.06-WG11-CR-0078-Datapoisoning-attack-exploits-threats
NOK-2023.07.17-WG11-CR-0094-Potential exploits and threat analysis for Model extraction attacks
NOK-2023.07.07-WG11-CR-0092-Evasion attack-exploits-threats-v02
NIST-2023.09.22-WG11-CR-0001-AIRMF-v01
NEC-2023.09.25-WG11-CR0004-AI_ML_TR_AssetIDUpdates_ODR_updates-v02 | -| 2023.10.25 | V00.00.05 | ready for plenary review | -| 2023.11.05 | V00.00.06 | Merged:
NOK-2023.11.08-WG11-CR-0123-AIMLsecTR ODR conformance-v05 | -| 2024.01.17 | V00.00.07 | Merged:
NOK-0132 | -| 2024.02.07 | V00.00.08 | Merged:
  • - NOK-0133
  • - NOK-0134
  • - NOK-0135
  • - NOK-0136
  • - MTR-0077
  • - MTR-0078
  • - ATT-0021
SYM-0038 | -| 2024.02.27 | V00.00.09 | Merged:
  • - MTR-0082
  • - NEC-0011
  • - ATT-0040
  • - SYM-0043
  • - NOK-0144
  • - NOK-0145
  • - NOK-0146
NOK-0147 | -| 2024.02.28 | V00.00.10 | Added a part missing from ATT-0040 | -| 2024.03.07 | V00.00.11 | First set of WIG review comments resolved | -| 2024.03.08 | V00.00.12 | Merged:
  • - MTR0087
  • - ATT-0041
  • - ATT-0042
  • - NOK.AO-0152
NEC-0013 | -| 2024.03.12 | V00.00.13 | First batch of review comments processed | - -| | | | -|------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2024.03.20 | V00.00.14 | Second batch of review comments processed | -| 2024.03.20 | V01.00 | Published as Final version 01.00 | -| 2024.03.25 | V01.01 | Editorial fixes | -| 2024.03.26 | V01.02 | Removing line numbers from part of the document | -| 2024.05.21 | V01.03 | Adding MTR-0090, ATT-0043, MTR-0091and NOK-0159 | -| 2024.06.06 | V01.04 | Adding NOK-0165, RMI-0021 | -| 2024.06.11 | V01.05 | Adding NOK-0166, RMI-0023 | -| 2024.07.24 | V02.00 | Published as Final version 02.00 | -| 2024.09.11 | V02.01 | Merged RMI-0024, RMI-0028, NEC-0025, NEC-0026 | -| 2024.11.05 | V02.02 | Updated copyright notices | -| 2024.11.27 | V02.03 | Editorial fixes | -| 2024.11.27 | V02.04 | Further editorial fixes | -| 2024.11.27 | V03.00 | Published as Final version 03.00 | -| 2025.05.28 | V03.01 | Merged NOK-0287 | -| 2025.05.29 | V03.02 | Merged draft NOK-0295, editorial fixes | -| 2025.07.09 | V03.03 | Editorial: fixing merge of NOK-0287 (order of clause 10.3 and ANNEX A corrected) | -| 2025.07.09 | V04.00 | Published as Final version 04.00 | -| 2025.09.24 | V04.01 | Merged MTR-168, MTR-0169, MTR-0175, NOK-0322, NOK-0302, MTR-0180 | -| 2025.10.21 | V04.02 | Merged NOK-0332, NOK-0342 | -| 2025.11.19 | V04.03 | Fixing merge of MTR-0180, setting copyright year to 2026 | -| 2025.11.24 | V04.04 | Fixing editorial problems in clause 2.2, changing 'IP' to 'intellectual property (IP)' in clause 5.3.6.1, fixing copyright year in the footer of some of the pages | -| 2025.11.25 | V05.00 | Published as Final version 05.00 | \ No newline at end of file diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 200dc7243f51b6cc36dd4a0b7eaa149b9b8b14d9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:38543337abfe046703460d80efb9c8c2167a389154c846b1c6a728170710636a -size 4221 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 200dc7243f51b6cc36dd4a0b7eaa149b9b8b14d9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:38543337abfe046703460d80efb9c8c2167a389154c846b1c6a728170710636a -size 4221 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/1a827b10290f33d4fec04d0e8ef7a897_img.jpg deleted file mode 100644 index c10eec4a1021dbc53ec07e707f674291a75c53cb..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/1a827b10290f33d4fec04d0e8ef7a897_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ca278f25c819b88b901e9a087e11b1dd48af0bdc6d7c7f98090901c57be0f64b -size 55423 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/1b5a812c8aa20fd5cba28e97001d32de_img.jpg deleted file mode 100644 index dcee0e55245f638c0ad6910890f6146c74f41619..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/1b5a812c8aa20fd5cba28e97001d32de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7a534ba9a672b018f0352f1ceee1ebf42605d6dd7045c25656d49ca1a2c16a81 -size 79552 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index 428c3a3818e88b435482a1e5ded07ec12f5c25a3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/1baaba7a6e54e77197475726c871067d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d7ee9111e224f56306ed937dad988c1514224d53334eb5490e7a45f739dc8023 -size 4258 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index f86dbbe5b5c13cf8bf7daa6eedf7f058697ce2cb..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d8cd1b75f6df8db957c6648f4508b3ea5a75aa8e299c0be51e33059a799f76c3 -size 4254 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 7af3a68eb1caea0f07d88d53f46fc1fd013c1732..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5d30283563c821bfe4ec656661b645185a9b25371c608de3985eb8ece31b384c -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 7af3a68eb1caea0f07d88d53f46fc1fd013c1732..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5d30283563c821bfe4ec656661b645185a9b25371c608de3985eb8ece31b384c -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 7af3a68eb1caea0f07d88d53f46fc1fd013c1732..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5d30283563c821bfe4ec656661b645185a9b25371c608de3985eb8ece31b384c -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index aa247cbe922aa0dfaef93b391c31446e3487d99b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e7f0f1beab8384b3356daa0183df646a66ea1b07625efc2c202bec2b8c5707dd -size 4227 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/6588b1c7f14069d96744b473ad663248_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg deleted file mode 100644 index 971707b3b736f4eb06ec1be278ccd58779da5fd4..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5d3f6bf64437240b1ed92db2a2dc4189e777f17d32a7820328a126d779195a1f -size 51850 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 86f9aab76b423315328c6fe2fc85bc8f49f690a9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:364bca19b472077022114ef5997eef4f37c448d216d536ab1034273f6e5d7d69 -size 4159 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index f86dbbe5b5c13cf8bf7daa6eedf7f058697ce2cb..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d8cd1b75f6df8db957c6648f4508b3ea5a75aa8e299c0be51e33059a799f76c3 -size 4254 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index 8f1d6cab924a14d89ecb8f7cade2aa55793d7c04..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e9b81cb494a2f48ef04637c139ad7c4bbbdb239e7aec9156f529659588aae7ad -size 4044 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 7af3a68eb1caea0f07d88d53f46fc1fd013c1732..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5d30283563c821bfe4ec656661b645185a9b25371c608de3985eb8ece31b384c -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 200dc7243f51b6cc36dd4a0b7eaa149b9b8b14d9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:38543337abfe046703460d80efb9c8c2167a389154c846b1c6a728170710636a -size 4221 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 86f9aab76b423315328c6fe2fc85bc8f49f690a9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:364bca19b472077022114ef5997eef4f37c448d216d536ab1034273f6e5d7d69 -size 4159 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 428c3a3818e88b435482a1e5ded07ec12f5c25a3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d7ee9111e224f56306ed937dad988c1514224d53334eb5490e7a45f739dc8023 -size 4258 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 428c3a3818e88b435482a1e5ded07ec12f5c25a3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d7ee9111e224f56306ed937dad988c1514224d53334eb5490e7a45f739dc8023 -size 4258 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg deleted file mode 100644 index 2c252e3fd12993956b13fc8855b9ede648e4321d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/a83ba9e3e2c1e21dd69953a7b09e45b4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6c472d8eb1f516dcc5c924a13b2ef67081015eb1cf6d9de5c87b4b8ad427f71 -size 52725 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 428c3a3818e88b435482a1e5ded07ec12f5c25a3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d7ee9111e224f56306ed937dad988c1514224d53334eb5490e7a45f739dc8023 -size 4258 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 428c3a3818e88b435482a1e5ded07ec12f5c25a3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d7ee9111e224f56306ed937dad988c1514224d53334eb5490e7a45f739dc8023 -size 4258 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 200dc7243f51b6cc36dd4a0b7eaa149b9b8b14d9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:38543337abfe046703460d80efb9c8c2167a389154c846b1c6a728170710636a -size 4221 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index 428c3a3818e88b435482a1e5ded07ec12f5c25a3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d7ee9111e224f56306ed937dad988c1514224d53334eb5490e7a45f739dc8023 -size 4258 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg deleted file mode 100644 index 50aa8fcc99a8e681658a9d9a5587332f890bb0b6..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/c67d21fb3d9042e88cdc669f071b4e7c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d31113f17dcf2f8d6ad051007af7db83f3f63bbafc70712469e77fb7c33e03f4 -size 50763 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index 428c3a3818e88b435482a1e5ded07ec12f5c25a3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d7ee9111e224f56306ed937dad988c1514224d53334eb5490e7a45f739dc8023 -size 4258 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 428c3a3818e88b435482a1e5ded07ec12f5c25a3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d7ee9111e224f56306ed937dad988c1514224d53334eb5490e7a45f739dc8023 -size 4258 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 428c3a3818e88b435482a1e5ded07ec12f5c25a3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d7ee9111e224f56306ed937dad988c1514224d53334eb5490e7a45f739dc8023 -size 4258 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/f74adaa1840504407cd4272995426f82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 1ccbc2677c20b39479c1f49063b6136feb186034..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.AIML-Security-Analysis.0-R005-v05.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9be02b7c606e2015a7ca986acca1666e8694deaedcfdcc11680b4c34a4f0fd36 -size 4005 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/doc.md b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/doc.md deleted file mode 100644 index 2b3c0aeddfab16eb61d78e95a4a55a85a0ac667a..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/doc.md +++ /dev/null @@ -1,1923 +0,0 @@ - - -# --- **O-RAN Work Group 11 (Security Work Group)****Study on Continuous Security Monitoring** - -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 ..... | 10 | -| Modal verbs terminology ..... | 10 | -| Introduction ..... | 10 | -| 1 Scope..... | 11 | -| 2 References..... | 11 | -| 2.1 Normative references ..... | 11 | -| 2.2 Informative references..... | 11 | -| 3 Definition of terms, symbols and abbreviations ..... | 15 | -| 3.1 Terms..... | 15 | -| 3.2 Symbols..... | 15 | -| 3.3 Abbreviations ..... | 15 | -| 4 Continuous security monitoring background, concept and assumptions..... | 16 | -| 4.1 Background ..... | 16 | -| 4.2 Concept..... | 17 | -| 4.3 Assumptions..... | 18 | -| 5 Key Issues ..... | 18 | -| 5.1 Introduction ..... | 18 | -| 5.2 Key Issue #1: Detection of DDoS attacks..... | 18 | -| 5.2.1 Introduction ..... | 18 | -| 5.2.2 Security threats ..... | 18 | -| 5.2.3 Potential security requirements ..... | 18 | -| 5.3 Key Issue #2: Detection of API security risks ..... | 19 | -| 5.3.1 Introduction ..... | 19 | -| 5.3.2 Security threats ..... | 19 | -| 5.3.3 Potential security requirements ..... | 19 | -| 5.4 Key Issue #3: Detection of cloud security risks..... | 19 | -| 5.4.1 Introduction ..... | 19 | -| 5.4.2 Security threats ..... | 19 | -| 5.4.3 Potential Security Requirements ..... | 20 | -| 5.5 Key Issue #4: Detection of authentication attacks ..... | 20 | -| 5.5.1 Introduction ..... | 20 | -| 5.5.2 Security threats ..... | 20 | -| 5.5.3 Potential security requirements ..... | 20 | -| 5.6 Key Issue #5: Detection of compromised xApps..... | 20 | -| 5.6.1 Introduction ..... | 20 | -| 5.6.2 Security threats ..... | 21 | -| 5.6.3 Potential security requirements ..... | 21 | -| 5.7 Key Issue #6: Detection authorization attacks ..... | 21 | -| 5.7.1 Introduction ..... | 21 | -| 5.7.2 Security threats ..... | 21 | -| 5.7.3 Potential security requirements ..... | 21 | -| 5.8 Key Issue #7: Tampering with open-source software components..... | 22 | -| 5.8.1 Introduction ..... | 22 | -| 5.8.2 Security threats ..... | 22 | -| 5.8.3 Potential security requirements ..... | 22 | -| 5.9 Key Issue #8: Data required to detect altered machine learning models used in Near-RT RIC..... | 22 | -| 5.9.1 Introduction ..... | 22 | -| 5.9.2 Security threats ..... | 22 | -| 5.9.3 Potential security requirements ..... | 22 | -| 5.10 Key Issue #9: Standardized metadata for CSM ..... | 23 | -| 5.10.1 Introduction ..... | 23 | -| 5.10.2 Security threats ..... | 23 | - -- 5.10.3 Potential security requirements ..... 23 -- 5.11 Key Issue #10: Data required to detect compromised ML data pipelining service used in Near-RT RIC..... 23 - - 5.11.1 Introduction ..... 23 - - 5.11.2 Security threats ..... 24 - - 5.11.3 Potential security requirements ..... 24 -- 5.12 Key Issue #11: Compromised software delivery ..... 24 - - 5.12.1 Introduction ..... 24 - - 5.12.2 Security threats ..... 24 - - 5.12.3 Potential security requirements ..... 24 -- 5.13 Key Issue #12: Untrusted software dependencies..... 24 - - 5.13.1 Introduction ..... 24 - - 5.13.2 Security threats ..... 25 - - 5.13.3 Potential security requirements ..... 25 -- 5.14 Key Issue #13: Adversarial attacks on AI/ML models ..... 25 - - 5.14.1 Introduction ..... 25 - - 5.14.2 Security threats ..... 25 - - 5.14.3 Potential security requirements ..... 25 -- 5.15 Key Issue #14: AI/ML-related data integrity and confidentiality ..... 25 - - 5.15.1 Introduction ..... 25 - - 5.15.2 Security threats ..... 25 - - 5.15.3 Potential security requirements ..... 26 -- 5.16 Key Issue #15: Model explainability and transparency ..... 26 - - 5.16.1 Introduction ..... 26 - - 5.16.2 Security threats ..... 26 - - 5.16.3 Potential security requirements ..... 26 -- 5.17 Key Issue #16 Model and data drift ..... 26 - - 5.17.1 Introduction ..... 26 - - 5.17.2 Security threats ..... 26 - - 5.17.3 Potential security requirements ..... 27 -- 5.18 Key Issue #17: Secure monitoring information sharing channels..... 27 - - 5.18.1 Introduction ..... 27 - - 5.18.2 Security threats ..... 27 - - 5.18.3 Potential security requirements ..... 27 -- 5.19 Key Issue #18: Monitoring data ownership and privacy..... 27 - - 5.19.1 Introduction ..... 27 - - 5.19.2 Security threats ..... 27 - - 5.19.3 Potential security requirements ..... 28 -- 5.20 Key Issue #19: Eavesdropping Attacks in O-RAN..... 28 - - 5.20.1 Key issue detail..... 28 - - 5.20.2 Security threats ..... 28 - - 5.20.3 Potential Security Requirements: ..... 28 -- 5.21 Key Issue #20: Attacks on O-RAN security log streaming and storage. .... 29 - - 5.21.1 Introduction ..... 29 - - 5.21.2 Security Threats..... 29 - - 5.21.3 Potential Security Requirements ..... 29 -- 5.22 Key Issue #21: Attacks on the PTP Network..... 29 - - 5.22.1 Introduction ..... 29 - - 5.22.2 Security Threats..... 29 - - 5.22.3 Potential Security Requirements ..... 29 -- 5.23 Key Issue #22: Unauthorized External Communication..... 30 - - 5.23.1 Introduction ..... 30 - - 5.23.2 Security threats ..... 30 - - 5.23.3 Potential security requirements ..... 30 -- 5.24 Key Issue #23: Compromised O-RU, O-CU, O-DU..... 30 - - 5.24.1 Introduction ..... 30 - - 5.24.2 Security Threats..... 30 - - 5.24.3 Potential Security Requirements ..... 31 -- 6 Mitigations and solutions ..... 31 - - 6.1 Introduction ..... 31 - - 6.2 Solution #1: Data required for detecting DoS attacks due to flooding ..... 31 - -| | | | -|--------|------------------------------------------------------------------------------------------------------------------|----| -| 6.2.1 | Introduction ..... | 31 | -| 6.2.2 | Solution Details ..... | 31 | -| 6.2.3 | Evaluation..... | 33 | -| 6.3 | Solution #2: Data required to detect API security risks (DoS through resource consumption)..... | 33 | -| 6.3.1 | Introduction ..... | 33 | -| 6.3.2 | Solution details ..... | 33 | -| 6.3.3 | Evaluation..... | 34 | -| 6.4 | Solution #3: Continuous security monitoring for adversarial attacks on AI/ML models ..... | 34 | -| 6.4.1 | Introduction ..... | 34 | -| 6.4.2 | Solution details ..... | 34 | -| 6.4.3 | Evaluation..... | 36 | -| 6.5 | Solution #4: Continuous security monitoring for AI/ML-related data integrity and confidentiality ..... | 36 | -| 6.5.1 | Introduction ..... | 36 | -| 6.5.2 | Solution details ..... | 36 | -| 6.5.3 | Evaluation..... | 36 | -| 6.6 | Solution #5: Continuous security monitoring for software delivery ..... | 37 | -| 6.6.1 | Introduction ..... | 37 | -| 6.6.2 | Solution details ..... | 37 | -| 6.6.3 | Evaluation..... | 37 | -| 6.7 | Solution #6: Continuous security monitoring for authentication attacks..... | 38 | -| 6.7.1 | Introduction ..... | 38 | -| 6.7.2 | Solution details ..... | 38 | -| 6.7.3 | Evaluation..... | 39 | -| 6.8 | Solution #7: Continuous security monitoring for authorization attacks ..... | 39 | -| 6.8.1 | Introduction ..... | 39 | -| 6.8.2 | Solution details ..... | 39 | -| 6.8.3 | Evaluation..... | 40 | -| 6.9 | Solution #8: Continuous security monitoring for cloud attacks related to lateral movement..... | 40 | -| 6.9.1 | Introduction ..... | 40 | -| 6.9.2 | Solution details ..... | 40 | -| 6.9.3 | Evaluation..... | 41 | -| 6.10 | Solution #9: Detection and prediction of DoS attacks due to packet flooding using Density Based Clustering ..... | 41 | -| 6.10.1 | Introduction ..... | 41 | -| 6.10.2 | Solution details ..... | 41 | -| 6.10.3 | Evaluation..... | 43 | -| 6.11 | Solution #10: Secure the transmission of security monitoring data..... | 43 | -| 6.11.1 | Introduction ..... | 43 | -| 6.11.2 | Solution Details ..... | 43 | -| 6.11.3 | Evaluation..... | 44 | -| 6.12 | Solution #11: Continuous security monitoring for open-source software delivery ..... | 44 | -| 6.12.1 | Introduction ..... | 44 | -| 6.12.2 | Solution Details ..... | 44 | -| 6.12.3 | Evaluation..... | 45 | -| 6.13 | Solution #12: Continuous Security Monitoring to Detect Unauthorized External Communication..... | 46 | -| 6.13.1 | Introduction ..... | 46 | -| 6.13.2 | Solution Details ..... | 46 | -| 6.13.3 | Evaluation..... | 46 | -| 6.14 | Solution #13: Data required to detect API security risks ..... | 46 | -| 6.14.1 | Introduction ..... | 46 | -| 6.14.2 | Solution details ..... | 48 | -| 6.14.3 | Evaluation..... | 50 | -| 6.15 | Solution #14: Data required to detect compromised xApps ..... | 50 | -| 6.15.1 | Introduction ..... | 50 | -| 6.15.2 | Solution details ..... | 51 | -| 6.15.3 | Evaluation..... | 56 | -| 6.16 | Solution #15: Collection of Data to Detect Compromised O-RU, O-CU, and O-DU ..... | 56 | -| 6.16.1 | Introduction ..... | 56 | -| 6.16.2 | Solution details ..... | 57 | -| 6.16.3 | Evaluation..... | 57 | - -- 7 Conclusions..... 58 -- 7.1 Key issue to solution mapping ..... 58 -- 7.2 Recommendations ..... 61 -- 7.2.1 Conclusions ..... 61 -- 7.2.2 Summary of recommended solutions ..... 62 -- Annex: Change history/Change request (history) ..... 70 - -# List of figures - -| | | -|--------------------------------------------------------------------------|----| -| Figure 4.1-1 - Continuous security monitoring and related ZTA tenet..... | 18 | -| Figure 4.2-1 - Continuous security monitoring cycle ..... | 18 | -| Figure 6.10-1 - Diagram illustrating burst of packets ..... | 43 | -| Figure 6.10-2 - Overall system level view of DBC implementation ..... | 43 | -| Figure 6.14-1 - High level block diagram ..... | 48 | - -# List of tables - -| | | -|--------------------------------------------------------------------------------------------------------------------------------|----| -| Table 6.2-1 - Data for statistical analysis..... | 33 | -| Table 6.2-2 - Data for security events (alarms/logs)..... | 33 | -| Table 6.2-3 - Data for configuration ..... | 33 | -| Table 6.2-4 - Data for standardization ..... | 33 | -| Table 6.3-1 - O-RAN API DoS Unique ID ..... | 34 | -| Table 6.3-2 - Example data associated with O-RAN API DoS resource consumption ..... | 35 | -| Table 6.4-1 - ML-based anomaly detection technique..... | 35 | -| Table 6.4-2 - Metrics..... | 36 | -| Table 6.4-3 - Data for Security Events (Alarms/Logs) ..... | 36 | -| Table 6.4-4 - Data for Configuration ..... | 36 | -| Table 6.6-1 - Data for software validation during onboarding ..... | 38 | -| Table 6.6-2 - Data for software vulnerability management ..... | 38 | -| Table 6.7-1 - Security logs for authentication attacks..... | 39 | -| Table 6.7-2 - Security counters for authentication attacks..... | 39 | -| Table 6.7-3 - Security alarms for authentication attacks..... | 39 | -| Table 6.7-4 - Other security related data for authentication attacks ..... | 40 | -| Table 6.8-1 - Security logs for authorization attacks ..... | 40 | -| Table 6.8-2 - Security alarms for authorization attacks ..... | 40 | -| Table 6.8-3 - Security counters for authorization attacks ..... | 41 | -| Table 6.8-4 - Security related data for authorization attacks ..... | 41 | -| Table 6.9-1 - Security logs for cloud attacks related to lateral movement..... | 41 | -| Table 6.9-2 - Security counters for cloud attacks related to lateral movement..... | 42 | -| Table 6.9-3 - Security alarms for cloud attacks related to lateral movement..... | 42 | -| Table 6.10-1 - Example description of clusters exceeding threshold ..... | 43 | -| Table 6.12-1 - Examples of metrics for open-source software repositories..... | 46 | -| Table 6.12-2 - Examples of incidents in open-source software repositories ..... | 46 | -| Table 6.14-1 - Security data to be collected for different API security risks..... | 50 | -| Table 6.14-2 - Counters and KPIs for API security risks..... | 51 | -| Table 6.15-1 - Mapping of Potentially Affected Components and Key Aspects for Monitoring in Response to Compromised xApps..... | 52 | -| Table 6.15-2 - Data to monitor for xApp exploitation attempts..... | 53 | -| Table 6.15-3 - Data to monitor for xApp behavioral drifts ..... | 54 | -| Table 6.15-4 - Data to monitor for other components (Near-RT RIC platform and E2 nodes) behavioral drifts. .... | 56 | -| Table 6.15-5 - Data to monitor for Inter-xApp and RIC Communication. .... | 57 | -| Table 6.15-6 - Data to monitor for deployment and file integrity information..... | 57 | -| Table 6.16-1 - Data for Security Events (Alarms/Logs) ..... | 58 | -| Table 6.16-2 - Data for Configuration ..... | 58 | -| Table 7.1-1 - Mapping of key issues to Solutions..... | 59 | -| Table 7.2-1 - Security data related to alarms ..... | 63 | -| Table 7.2-2 - Security data related to counters..... | 65 | -| Table 7.2-3 - Security data related to logs ..... | 66 | - -# Foreword - -This Technical Report (TR) has been produced by WG11 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 - -In the evolving landscape of telecommunications, the Open Radio Access Network (O-RAN) architecture has emerged as a game-changer, promising unprecedented flexibility, interoperability, and innovation. However, with this new level of openness and diversity comes an expanded attack surface and heightened security challenges. To address these concerns, continuous security monitoring is imperative for O-RAN networks to ensure their resilience and protect sensitive data. - -This technical report delves into the intricacies of continuous security monitoring for O-RAN, exploring the key principles, technologies, and best practices that enable effective security posture management. By providing a comprehensive overview, we aim to empower stakeholders—including telecom operators, vendors, and security experts—with the knowledge necessary to safeguard O-RAN networks against evolving threats. - -We will delve into the practical aspects of implementing continuous security monitoring, data collection strategies, and the integration of security monitoring solutions within the O-RAN ecosystem. - -Lastly, we will discuss the future outlook for continuous security monitoring in O-RAN, considering emerging technologies, standards, and regulatory frameworks that will shape the landscape. By embracing a proactive and adaptive security posture, O-RAN networks can harness the full potential of openness and innovation while maintaining the highest levels of security and reliability. - -This technical report serves as a valuable resource for anyone involved in the design, deployment, or security management of O-RAN networks, offering a comprehensive understanding of continuous security monitoring practices. - -# 1 Scope - -The present document presents the Continuous Security Monitoring study as it applies to O-RAN architectural elements. - -Taking into consideration the threats and risks identified in O-RAN Threat Modeling and Risk Assessment [i.2], the study analyses a list of key issues on abnormal security events and proposes solutions in order to derive security requirements, intended to be part of O-RAN Security related Specifications. - -# 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] O-RAN.WG11.TR.Threat-Modeling: “O-RAN Security Threat Modeling and Risk Assessment”. -- [i.3] O-RAN.WG11.TS.SRCS: “Security Requirements and Controls Specifications”. -- [i.4] “Nokia Threat Intelligence Report 2023”: . -- [i.5] “OWASP Top 10 API security risks”: . -- [i.6] NIST Special Publication 800-207, "Zero Trust Architecture", August 2020, . -- [i.7] “UNICC Cyber Threat Landscape Report 2023”: May 2024. -- [i.8] OWASP Top 10:2021: ”A07:2021 – Identification and Authentication Failures”, [https://owasp.org/Top10/A07\\_2021-Identification\\_and\\_Authentication\\_Failures/](https://owasp.org/Top10/A07_2021-Identification_and_Authentication_Failures/). -- [i.9] O-RAN.WG11.TR.Security-Near-RT-RIC-xApps: “Study on Security for Near Real Time RIC and xApps”. -- [i.10] OWASP Top 10:2021: ”A01:2021 – Broken Access Control”; [https://owasp.org/Top10/A01\\_2021-Broken\\_Access\\_Control/](https://owasp.org/Top10/A01_2021-Broken_Access_Control/). -- [i.11] MITRE ATT&CK: . -- [i.12] O-RAN.WG11.Security-Log-Management-TR: “O-RAN WG11 Study on Security Log Management”. -- [i.13] NIST special publication 800-137: “Information Security Continuous Monitoring for Federal Information Systems and Organizations”. -- [i.14] O-RAN.WG3.RICARCH: “Near-RT RIC Architecture”. - -- [i.15] ITU Data Communications Networks Information Technology – Open Systems Interconnection – Systems Management: “Security Alarm Reporting Function Recommendation X.736”; . -- [i.16] Bernhard Scholkopf et al: “Support Vector Method for Novelty Detection”; [https://proceedings.neurips.cc/paper\\_files/paper/1999/file/8725fb777f25776ffa9076e44fcfd776-Paper.pdf](https://proceedings.neurips.cc/paper_files/paper/1999/file/8725fb777f25776ffa9076e44fcfd776-Paper.pdf). -- [i.17] “Hasan Torabi et al: Practical autoencoder based anomaly detection by using vector reconstruction error”; . -- [i.18] IEEE Xplore: “Network Intrusion Detection in Cloud Computing Environments”; . -- [i.19] O-RAN.WG11.TR.ZTA: “Study on Zero Trust Architecture for O-RAN“. -- [i.20] NIST Special Publication 800-207A, "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", September 2023 . -- [i.21] Void. -- [i.22] O-RAN.WG4.TS.MP: "O-RAN Management Plane Specification". -- [i.23] O-RAN.WG10.TS.O1-Interface: "O-RAN O1 Interface Specification". -- [i.24] GitGuardian: . -- [i.25] Codecov: . -- [i.26] MITRE ATT&CK, Technique T1040, “Network Sniffing”, . -- [i.27] MITRE FiGHT Technique T1040, “Network Sniffing”, . -- [i.28] O-RAN “Control, User and Synchronization Plane Specification 17.01”. -- [i.29] D. Dik and M. S. Berger, "Open-RAN Fronthaul Transport Security Architecture and Implementation," in IEEE Access, vol. 11, pp. 46185-46203, 2023, doi: 10.1109/ACCESS.2023.3274487. . -- [i.30] log- streaming, . -- [i.31] MITRE ATT&CK Technique T1654, “Log Enumeration”, . -- [i.32] IEEE “Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems (2008)” IEEE Std 1588–2008 (Revision of IEEE Std 1588–2002), pp 1–269. . -- [i.33] Norbert Ludant et al: “Unprotected 4G/5G Control Procedures at Low Layers Considered Dangerous”; . -- [i.34] MITRE FiGHT V2.1.1, Technique FG5034, “Radio Control Manipulation Via Rogue xApps”. -- [i.35] MITRE FiGHT V2.1.1, Technique FGT1195.002, “5G Supply Chain Compromise: Compromise Software Supply Chain”. -- [i.36] MITRE FiGHT V2.1.1, Technique FGT1078.004, “Valid Accounts: Cloud Accounts”. -- [i.37] MITRE FiGHT V2.1.1, Technique FGT1021, “Remote Services”. -- [i.38] MITRE FiGHT V2.1.1, Technique FGT1498.502, “Network Denial of Service: Shared Slice Common Control Network Function Resource Exhaustion”. -- [i.39] MITRE ATT&CK V17, Technique T1565.003, “Data Manipulation: Runtime Data Manipulation”. - -- [i.40] MITRE FiGHT V2.1.1, Technique FGT1611, “VM And Container Breakout”. - -- [i.41] MITRE FiGHT V2.1.1, Technique FGT1611.501, “VM And Container Breakout: Malicious Privileged container-VNF Shared Resource Access”. [i.42] “Unprotected 4G/5G Control Procedures at Low Layers Considered Dangerous”, . -- [i.43] IEEE 802.1X ; . -- [i.44] R. N. Gemaque, A. F. J. Costa, R. Giusti, and E. M. D. Santos, “An overview of unsupervised drift detection methods,” *Wiley Interdisciplinary Reviews Data Mining and Knowledge Discovery*, vol. 10, no. 6, Jul. 2020, doi: 10.1002/widm.1381. -- [i.45] “Classification: Accuracy, recall, precision, and related metrics,” *Google for Developers*. - - -# --- 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: - -| | | -|-------|-----------------------------------------------------| -| API | Application Programming Interface | -| CCPA | California Consumer Privacy Act | -| CNF | Containerised Network Function | -| CPU | Central Processing Unit | -| CSM | Continuous Security Monitoring | -| CVE | Common Vulnerabilities Exposures | -| DADPF | DDoS Analytics, Detection and Prediction Function | -| DBC | Density Based Clustering | -| DoS | Denial of Service | -| GDPR | General Data Protection Regulation | -| HIPAA | Health Insurance Portability and Accountability Act | -| NF | Network Function | -| SMO | Service and Management Orchestration | -| UNICC | United Nations International Computing Centre | -| VNF | Virtualised Network Function | -| ZTA | Zero Trust Architecture | - -# --- 4 Continuous security monitoring background, concept and assumptions - -## 4.1 Background - -NIST SP 800-207 [i.6] defines a Zero Trust Architecture (ZTA) to protect against internal threats. ZTA does not assume trust for any subject requesting resources, whether the subject is internal or external. ZTA also assumes that an adversary is already present inside the network. There is also a new publication on zero trust access control in cloud environments NIST SP 800-207A [i.20] that extends the zero trust principles to make an access control model for cloud-based workloads. - -The ZTA WI TR [i.19] recommends to have a dedicated WI for CSM elaborating Tenet 5 and Tenet 7 applying to O-RAN. - -As shown in Figure 4.1-1, Tenets 5 and 7 of ZTA is as below: - -**[ZT-5]:** The enterprise monitors and measures the integrity and security posture of all owned and associated assets. No asset is inherently trusted. - -**[ZT-7]:** The enterprise collects as much information as possible about the current state of assets, network infrastructure and communications and uses it to improve its security posture. - -In order for enterprises to monitor and measure the integrity and security posture of an O-RAN deployment, it is important to define and collect security data (e.g. security alarms, security logs, security counters) from all O-RAN components, including O-RU, O-DU, O-CU, Non-RT RIC. - -The Open Radio Access Network (O-RAN) ALLIANCE is an industry consortium focused on developing open interfaces for radio access networks. The alliance's vision is to enable a more dynamic, flexible, and secure network infrastructure through open interfaces, interoperability, and collaboration between vendors. As part of this vision, there is a need for the O-RAN architecture to support continuous security monitoring capabilities. - -Objectives: - -1. Study the security related data from O-RAN architectural elements to assess security events including abnormal events related to potential attacks. -2. Study the security data obtained from O-RAN architectural elements which are related to non-O-RAN architectural elements (e.g. UEs) to assess security events including abnormal events related to potential attacks. -3. Provide guidelines for the use of the collected security related data for: - - a) Defining the security posture, - - b) Mitigating the attack, - - c) Enforcing the security policy. -4. Provide guidelines to address - - a) The integration of external threat intelligence sources, - - b) The integration with other O-RAN work items, - - c) Orchestration related to continuous security monitoring. -5. Monitor the work of 3GPP on the topic of CSM to consider their study in O-RAN. - -![Venn diagram illustrating Continuous Security Monitoring and related ZTA tenets. A large green circle represents 'Tenet 5, 7' (Continuous Security Monitoring). Inside it, a pink circle represents 'Tenet 1, 2, 3' (Micro perimeters) and a blue circle represents 'Tenet 4, 6' (Automation). The intersection of pink and blue circles shows shared elements. The pink circle lists: Identify all types of assets, Security controls for all assets, Defense in depth. The blue circle lists: Dynamic policies, Ensure authentication and authorization at a granular level. The intersection lists: Least privilege with session based, Continuous checking. The green circle lists: Security related data collection, Feedback cycle, Continuous remediation of security health, Device hygiene (intermediary routers, PKI).](08441fa90c5fd11994626f662ac13f19_img.jpg) - -**Tenet 1, 2, 3** - -**Micro perimeters** - -- Identify all types of assets -- Security controls for all assets -- Defense in depth - -**Tenet 4, 6** - -**Automation** - -- Dynamic policies -- Ensure authentication and authorization at a granular level - -**Intersection:** - -- Least privilege with session based -- Continuous checking - -**Tenet 5, 7** - -**Continuous Security Monitoring** measures security posture of the defense mechanisms - -- Security related data collection -- Feedback cycle -- Continuous remediation of security health -- Device hygiene (intermediary routers, PKI) - -Venn diagram illustrating Continuous Security Monitoring and related ZTA tenets. A large green circle represents 'Tenet 5, 7' (Continuous Security Monitoring). Inside it, a pink circle represents 'Tenet 1, 2, 3' (Micro perimeters) and a blue circle represents 'Tenet 4, 6' (Automation). The intersection of pink and blue circles shows shared elements. The pink circle lists: Identify all types of assets, Security controls for all assets, Defense in depth. The blue circle lists: Dynamic policies, Ensure authentication and authorization at a granular level. The intersection lists: Least privilege with session based, Continuous checking. The green circle lists: Security related data collection, Feedback cycle, Continuous remediation of security health, Device hygiene (intermediary routers, PKI). - -**Figure 4.1-1 - Continuous security monitoring and related ZTA tenet** - -## 4.2 Concept - -The scope of this study is primarily to focus on the enablers for continuous security monitoring as in Figure 4.2-1 which is the security related data to be defined and collected. Other aspects of Tenet 5 and Tenet 7 related to security posture, enforcement of security policy may be mentioned purely as guidelines. - -![Figure 4.2-1 - Continuous security monitoring cycle diagram. The diagram is divided into two horizontal sections by a dashed line. The top section, labeled 'Out of scope of O-RAN standardization plan', contains two boxes: 'Monitor (Security Posture)' and 'Enforce via Policy'. The bottom section, labeled 'In scope of O-RAN standardization plan', contains a vertical stack of three boxes: 'Define', 'Collect', and 'Expose'. An arrow points from 'Define' to 'Collect', and from 'Collect' to 'Expose'. From 'Expose', an arrow points up into the top section to 'Monitor (Security Posture)'. From 'Monitor (Security Posture)', an arrow points to 'Enforce via Policy', which then points back down into the bottom section. The label 'O-RAN Architectural Elements' is placed in the bottom right of the 'In scope' section.](4e4be0bd8b235167902f2c03e41da651_img.jpg) - -Figure 4.2-1 - Continuous security monitoring cycle diagram. The diagram is divided into two horizontal sections by a dashed line. The top section, labeled 'Out of scope of O-RAN standardization plan', contains two boxes: 'Monitor (Security Posture)' and 'Enforce via Policy'. The bottom section, labeled 'In scope of O-RAN standardization plan', contains a vertical stack of three boxes: 'Define', 'Collect', and 'Expose'. An arrow points from 'Define' to 'Collect', and from 'Collect' to 'Expose'. From 'Expose', an arrow points up into the top section to 'Monitor (Security Posture)'. From 'Monitor (Security Posture)', an arrow points to 'Enforce via Policy', which then points back down into the bottom section. The label 'O-RAN Architectural Elements' is placed in the bottom right of the 'In scope' section. - -Figure 4.2-1 - Continuous security monitoring cycle - -## 4.3 Assumptions - -The assets will be inherited from the ZTA technical study [i.19]. - -The threats will also be reused from the existing threats and risk analysis document in [i.1]. - -Exposing the security data in a structured manner can help to automate the continuous security monitoring. In order to do this, classification of security data and defining a structure can help. - -In this TR we explore what type of data has to be defined and collected to support CSM. - -# 5 Key Issues - -## 5.1 Introduction - -In this clause, the key issues will be introduced, and respective security threats and potential security requirements will be identified related to continuous security monitoring. - -## 5.2 Key Issue #1: Detection of DDoS attacks - -### 5.2.1 Introduction - -According to Nokia Threat Intelligence Report 2023 [i.4], 60% of attacks in telecom mobile networks are linked to Internet of Things (IoT) bots scanning for vulnerable hosts to expand their botnets for use in distributed denial-of-service (DDoS) attacks. Various kinds of DDoS attacks are known and published on the internet. Some DDoS attacks can be launched by flooding a system or component with a lot of packets, while other kinds of DDoS attacks use system vulnerabilities like buffer overflow, and some other attacks use unhandled error scenarios to bring down the availability of the system or a component. - -It is important to distinguish between a DDoS attack and a system issue (like performance issues). The security evaluation and monitoring systems require the correct set of data to perform this distinction accurately. Attackers may be passively monitoring the system or a component for some time before launching active DDoS attacks. Data collected during the phase of passive monitoring can also be useful to clearly detect a DDoS attack instead of mis-interpreting system un-availability as a software issue. - -### 5.2.2 Security threats - -If relevant data is not collected, DDoS attacks cannot be detected in an effective way. Effects of successful DDoS attacks may be mistaken with system (performance) issues or with effects of other types of attacks. Due to ineffective attack type triage, the appropriate mitigation actions against a DDoS attack may not be executed by the operator. - -DDoS attacks may affect the O-RAN architectural elements. Hence, all O-RAN architectural elements can be considered as potentially impacted by such an attack. - -### 5.2.3 Potential security requirements - -O-RAN architecture elements should be able to expose necessary data which can be used to analyse and detect potential DDoS attacks on any O-RAN architectural element. - -## 5.3 Key Issue #2: Detection of API security risks - -### 5.3.1 Introduction - -According to O-RAN architecture, CNFs and VNFs provide the necessary functionalities in NFs including O-DU, O-CU, SMO, Near-RT-RIC, Non-RT-RIC, etc. O-Cloud provides the platform for these NFs. Each NF is likely to expose one or more APIs (internally or externally) for interactions with other NFs. OWASP top 10 API security risks are detailed in [i.5]. Also, literature talks about Reverse engineering attacks, API spoofing, adversary-in-the-middle attacks and replay attacks as other kinds of attacks on APIs. - -For CSM, it is important for the O-RAN architecture elements to be able to collect necessary data in order to determine if any malicious actor is attempting to exploit any of the API security vulnerabilities. Considering the fact that almost all NFs in O-RAN are expected to implement APIs, this is very important from the perspective of ZTA. - -### 5.3.2 Security threats - -If relevant data is not exposed to assess the potential exploitation of API security risks, attacks may go unnoticed, and operators may not be able to take mitigation steps. Malicious actors may be able to compromise confidentiality, integrity and availability of the system without getting detected. - -All O-RAN interfaces which expose APIs can be impacted by such attacks. - -### 5.3.3 Potential security requirements - -O-RAN architecture elements should be able to expose necessary data which can be used to analyse and detect/predict potential exploitation of API security risks. - -## 5.4 Key Issue #3: Detection of cloud security risks - -### 5.4.1 Introduction - -According to the United Nations International Computing Centre (UNICC) the largest strategic partner for digital solutions and cybersecurity within the United Nations, cloud related threats are on the rise since 2023. In the majority of cases analysed and handled by UNICC in [i.7], adversaries deployed malware on the compromised host as a primary action following the initial compromise. Once the cyber-attacker has compromised the secured system, they are able to execute additional malicious code to make unauthorized attempts to collect intelligence from cloud resources. - -One of the recommendations from UNICC is to implement continuous monitoring capabilities which would enable the organizations to identify, respond to, and mitigate cyber threats at an early stage, enhancing overall cybersecurity resilience. Hence the need to collect and monitor data related to cloud security threats. - -### 5.4.2 Security threats - -If relevant data is not exposed to assess the potential exploitation of cloud network functions it poses a severe security risk, as the compromised element may be used by the attackers to target other subsystems residing in the cloud infrastructure. Without proper - -![O-RAN ALLIANCE logo](5f2c99ae08864cf2d5c949947bac2b98_img.jpg) - -The logo for the O-RAN Alliance, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with "ALLIANCE" in smaller letters underneath. - -O-RAN ALLIANCE logo - -monitoring, operators may not be able to take mitigation steps. Malicious actors may be able to compromise confidentiality, integrity and availability of the system without getting detected. Security threats related to cloud include (but are not limited to): exploitation of vulnerable software, unauthorized access as in [i.6], lack of authentication & authorization in interfaces between cloud components, unsecured credentials and keys, sensitive application data cache exploitation and numerous threats specific to all cloud related technologies (e.g. threats specific to VMs, containers or hardware). - -O-RAN network functions operating in a cloud infrastructure can be impacted by such attacks as cloud environments are prone to security vulnerabilities, which can expose sensitive customer data, critical network configurations, and traffic data to cyberattacks. These kinds of attacks can result in service outages, financial loss, and regulatory fines. - -Another risk related to cloud environments is the fact that they might introduce higher latency, which can degrade the performance of latency-sensitive telecom network functions. This is important as attackers are often abusing compromised cloud environments to misuse resources, which could have effect on the performance of network functions. - -One more risk is related to deployments of networks which could be using public cloud infrastructures and share resources with other cloud users, leading to potential issues with performance isolation, security vulnerabilities, or contention for resources. - -Cloud related risks could further include attacks related to data breaches, resource abuse, lateral movement, denial of service due to NF unavailability as described in [i.11]. - -### 5.4.3 Potential Security Requirements - -O-RAN system should be able to expose necessary data which can be used to analyse and detect/predict potential threats related to cloud security risks. - -## 5.5 Key Issue #4: Detection of authentication attacks - -### 5.5.1 Introduction - -Authentication is a critical factor in implementing a ZTA for O-RAN architectural elements. It is essential that the O-RAN maintains robust security in this area, as inadequate authentication can lead to loss of customer trust and have significant impacts on an operator's financial health, overall reputation, and regulatory compliance. According to OWASP, authentication-related threats are among the top security concerns [i.8]. - -These threats can affect various elements, including identification from cloud-based services, edge devices, and remote API clients. In O-RAN, authentication can be achieved through multiple methods such as password-based systems, certificate-based authentication (including mutual TLS), token-based authentication as part of OAuth2.0 framework, and 802.1x based port authentication. - -A few of the authentication related threats related to O-RAN are T-O-RAN-03, T-O-RAN-05, T-O-RAN-06, T-NEAR-RT-03, T-rAPP-04, T-rAPP-06, T-R1-03, T-A1-01, T-E2-01, T-Y1-01, T-GEN-02, T-GEN-04, T-GEN-05, T-GEN-06, T-SMO-01, T-SMO-04, T-SharedORU-01, T-SharedORU-03, as identified in [i.2]. - -### 5.5.2 Security threats - -If the relevant security data related to capturing authentication workflows is not exposed, then there are chances that external and internal attacks will go undetected leading to sabotage of the O-RAN network. - -The O-RAN architectural elements support authentication on various O-RAN interfaces with protocols including HTTP, mTLS, IPsec, IEEE 802.1X, SSH, SCTP, as in [i.3]. - -The possibility of threats relates to unauthenticated access to O-RAN functions, improper authentication mechanisms, use of predefined/ default accounts, weak or missing password policy, brute-force as in [i.2], obtaining of client secrets, improper extraction of certificates, and session management attacks. - -### 5.5.3 Potential security requirements - -O-RAN architecture elements should be able to expose necessary data which can be used to analyse and detect potential authentication attacks on any O-RAN architectural element or interface. - -## 5.6 Key Issue #5: Detection of compromised xApps - -### 5.6.1 Introduction - -xApps on the Near-RT RIC collect near real-time information from E2 nodes and can influence their behaviour, which impacts cell performance and the delivery of services to individual users or groups of users [i.9]. However, vulnerable, and exploitable xApps can be compromised by attackers, potentially disrupting network services in various ways. Several vulnerabilities can lead to the compromise of an xApp, including security misconfigurations, weak or improperly configured authentication and authorization mechanisms, and the presence of backdoors intentionally inserted by a trusted source [i.9]. - -### 5.6.2 Security threats - -Failure to collect relevant data can result in compromised xApps going undetected, preventing operators from taking necessary mitigation actions. - -A compromised xApp has the potential to access and manipulate sensitive subscriber data, putting their privacy at risk and negatively affecting the performance of the RAN and the core network. Moreover, such an xApp could interfere with the delivery of services to subscribers or even take control of another xApp or the Near-RT RIC, increasing security risks within the system [i.9]. - -### 5.6.3 Potential security requirements - -O-RAN architecture elements should be able to expose necessary data which can be used to analyse and detect compromised xApps. - -## 5.7 Key Issue #6: Detection of authorization attacks - -### 5.7.1 Introduction - -Access Control was among the more common of OWASP's Top 10 risks to be involved in exploits and security incidents indicating that 'Broken Object Level Authorization' has been the most common and impactful attack on APIs [i.10]. The potential impact resulting from exploitation of authorization flaws is highly variable, both in form and severity. Attackers may be able to read, create, modify, or delete resources that were meant to be protected (thus jeopardizing their confidentiality, integrity, and/or availability); however, the actual impact of such actions is necessarily linked to the criticality and sensitivity of the compromised resources. Thus, the business cost of a successfully exploited authorization flaw can range from very low to extremely high. - -Authorization is a critical factor in implementing a ZTA for O-RAN architectural elements. It is essential that the O-RAN continuously validates the authorization for every resource and every action performed that is technically possible. Even if the application implements a proper infrastructure for authorization checks, developers might forget to use these checks before accessing a sensitive object. Unauthorized access can result in data disclosure to unauthorized parties, data loss, or data manipulation. - -A few of the authorization related threats related to O-RAN are T-O-RAN-05, T-O-RAN-06, T-O-RU-04, T-NEAR-RT-04, T-R1-01, T-R1-04, T-ApplLCM-04, T-GEN-04, T-GEN-05, T-GEN-06, T-VM-C-01, T-VM-C-05, T-ADMIN-02, T-SMO-02, T-SMO-05, T-SMO-18, T-SharedORU-22, as identified in [i.2]. - -### 5.7.2 Security threats - -If the relevant security data related to capturing authorization workflows is not exposed, then there are chances that external and internal attacks will go undetected leading to sabotage of the O-RAN network due to horizontal privilege elevation (i.e. being able to access another user's resources). Faults related to authorization control can allow malicious insiders and outsiders alike to view, modify, or delete sensitive resources of all forms or perform actions, such as creating a new account that they should not be privileged to do. - -The O-RAN architectural elements support authorization on various O-RAN interfaces with protocols including HTTP, mTLS, IPSec, SSH, SCTP, as in [i.3]. - -The possibility of threats relates to unauthorized access to O-RAN functions, manipulation of data, misconfiguration, violation of the principle of least privilege, etc. - -### 5.7.3 Potential security requirements - -O-RAN architecture elements should be able to expose necessary data which can be used to analyse and detect potential authorization attacks on any O-RAN architectural element or interface. - -## 5.8 Key Issue #7: Tampering with open-source software components - -### 5.8.1 Introduction - -The O-RAN architecture elements relies on open-source software components, which can be vulnerable to tampering by malicious actors. An attacker could intentionally introduce vulnerabilities or backdoors into the open-source code, compromising the security of the entire system. - -### 5.8.2 Security threats - -Tampering with open-source software components can lead to the introduction of malicious code, which can be used to gain unauthorized access, disrupt system operation, or steal sensitive information (MITRE ATT&CK [i.11] technique T1195: Supply Chain Compromise). - -Malicious code can also be used to create a backdoor, allowing attackers to maintain access to the system even after the initial vulnerability has been patched (MITRE ATT&CK technique T1098: Account Manipulation). - -### 5.8.3 Potential security requirements - -Continuous monitoring of open-source software components for suspicious activity or anomalies. - -## 5.9 Key Issue #8: Data required to detect altered machine learning models used in Near-RT RIC - -### 5.9.1 Introduction - -Some xApps hosted on the Near-RT RIC incorporate machine learning (ML) solutions for inference and/or training. These ML-enabled xApps can integrate necessary models directly or access them from databases or separate filesystems/storage. When ML models are embedded within xApps, they may be compromised due to vulnerabilities within the xApp itself or weaknesses in exposed APIs. On the other hand, for xApps utilizing models stored externally in a database or separate storage, compromises may occur due to vulnerabilities that lead to unauthorized updates in the database, weaknesses in database security, or inadequate authentication and authorization measures for the database [i.9]. - -### 5.9.2 Security threats - -Failure to collect relevant data can result in altered ML models going undetected, preventing operators from taking necessary mitigation actions. - -An attacker may gain unauthorized access to a machine learning model and modify its parameters, affecting the accuracy of its outputs. This can lead to incorrect predictions, potentially resulting in catastrophic outcomes if these predictions inform critical business decisions. Additionally, attackers can extract sensitive or confidential data embedded within the ML model through training [i.9]. - -### 5.9.3 Potential security requirements - -O-RAN architecture elements should be able to expose necessary data which can be used to analyse and detect altered ML models. - -## 5.10 Key Issue #9: Standardized metadata for CSM - -### 5.10.1 Introduction - -This key issue is to develop standardized metadata to support CSM in O-RAN. Standardized metadata is required to enable multi-vendor interoperability for all types of data collected to support CSM with automation. As a result, security analytics functions can effectively conduct analytics leveraging the data collected regardless of which vendor solution is used to collect the data. - -The following provides more information for this key issue by partially leveraging Key Issue SLF#1: Standardized logging metadata in SLM to support security analytics, as defined in clause 5.4.1 of [i.12]. Key Issue SLF#1 in SLM provides a good baseline for standardized logging metadata only for security event type. However, there are additional data types that need to be considered. Other examples of data types that are not covered by SLM may include performance data, KPIs, vulnerability scanning and patch management information, intrusion detection and prevention system information, malware detection data, asset management data, configuration management data, license and information management information, software assurance data, network monitoring data, and alarms. Refer to Appendix D of [i.13] for details on continuous security monitoring data collection methods. - -### 5.10.2 Security threats - -CSM will collect various types of data from O-RAN architecture elements and interfaces. Security analytics functions need to conduct analytics on the data and correlate the data to detect security threats. For security analytics functions to consume the data collected regardless of which vendor solution is used to collect the data, it will be essential to have standardized metadata for CSM. If the metadata is not standardized across various security related data, then this would impede interoperability. - -### 5.10.3 Potential security requirements - -The metadata of the data collected for security evaluation and monitoring should be standardized to support robust and interoperable security analytics. - -## 5.11 Key Issue #10: Data required to detect compromised ML data pipelining service used in Near-RT RIC - -### 5.11.1 Introduction - -The Near-RT RIC data pipelining service facilitates data ingestion and preparation for xApps within the Near-RT RIC platform [i.14]. The inputs to the data pipelining service may include: - -- E2 node data collected via the E2 interface [i.14]. -- Enrichment information transmitted over the A1 interface [i.14]. -- Data provided by xApps [i.14]. -- Data retrieved from the Near-RT RIC database through the messaging infrastructure [i.14]. - -The output of the Near-RT RIC data pipelining service consists of datasets that are prepared for consumption by AI/ML models. These datasets may be: - -- Stored in an xApp-specific space (e.g. a dedicated database), where they can be accessed later for training or inference [i.14]. -- Used directly as input for inference [i.14]. - -The ML data pipelining service may be vulnerable to compromise through several attack vectors. These include vulnerabilities within the xApp that utilizes the ML data pipelining service itself. Additionally, the service could be targeted by poisoning attacks originating from compromised E2 nodes or compromised UEs. Further risks arise from the potential compromise of databases that store historical data consumed by the data pipelining service. Furthermore, malicious actors could gain unauthorized access through compromised interfaces of the Near-RT RIC [i.9]. - -### 5.11.2 Security threats - -Failure to collect relevant data can result in compromised ML data pipelining service used in Near-RT RIC going undetected, preventing operators from taking necessary mitigation actions. - -An attacker gaining unauthorized access to the machine learning data pipelining service could take control of a subset of the training data by inserting or modifying training samples [i.2]. This could undermine: - -- The integrity of the training or test data. -- The integrity of the trained ML model. -- The accuracy and reliability of the ML prediction results derived from the model. -- The overall behaviour and performance of the ML system. - -NOTE: This key issue is related to key issue #14 and key issue #15. - -### 5.11.3 Potential security requirements - -O-RAN architecture elements should be able to expose necessary data which can be used to analyse and detect compromised ML data pipelining service used in Near-RT RIC. - -## 5.12 Key Issue #11: Compromised software delivery - -### 5.12.1 Introduction - -The O-RAN architecture elements software delivery process can be compromised by malicious actors, allowing them to inject malicious code or modify legitimate code to include vulnerabilities. - -NOTE: While being an important aspect of the software lifecycle, software delivery is not fully covered in O-RAN specification at the time of publication. However, security requirements of important aspects of it can be found in [i.3], clause 5.3.2. - -### 5.12.2 Security threats - -Compromised software delivery can lead to the introduction of malicious code, which can be used to gain unauthorized access, disrupt system operation, or steal sensitive information (MITRE ATT&CK [i.11] technique T1195: Supply Chain Compromise). - -Attackers can also use compromised delivery processes to create a backdoor, allowing them to maintain access to the system even after the initial vulnerability has been patched (MITRE ATT&CK [i.11] technique T1098: Account Manipulation). - -### 5.12.3 Potential security requirements - -The O-RAN architecture elements should support continuous security monitoring of software delivery processes for detecting and preventing suspicious activity. - -## 5.13 Key Issue #12: Untrusted software dependencies - -### 5.13.1 Introduction - -The O-RAN architecture elements relies on third-party software dependencies, which can be untrusted or vulnerable to exploitation by malicious actors. An attacker could exploit vulnerabilities in these dependencies to gain access to the system or disrupt its operation. - -NOTE: for an example of security related aspects of third-party software dependencies in O-RAN, see [i.2], thread T-AIML-SC-06. - -### 5.13.2 Security threats - -Untrusted software dependencies can introduce vulnerabilities, which can be exploited by attackers to gain unauthorized access, disrupt system operation, or steal sensitive information (MITRE ATT&CK [i.11] technique T1195: Supply Chain Compromise). - -Attackers can also use vulnerabilities in dependencies to create a backdoor, allowing them to maintain access to the system even after the initial vulnerability has been patched (MITRE ATT&CK [i.11] technique T1098: Account Manipulation). - -### 5.13.3 Potential security requirements - -The O-RAN architecture elements should support continuous security monitoring of software dependencies for detecting and preventing vulnerabilities. - -NOTE: vulnerable 3rd party package testing is very important but is outside the scope of the O-RAN ALLIANCE. - -## 5.14 Key Issue #13: Adversarial attacks on AI/ML models - -### 5.14.1 Introduction - -O-RAN architecture elements may utilize AI/ML for various functions, including network optimization and anomaly detection. However, the use of AI/ML models introduces new security risks, particularly the threat of adversarial attacks. Adversarial attacks may involve manipulating the input data to AI/ML models to cause misclassifications or incorrect decisions, potentially leading to security breaches or disruptions to network operations. - -### 5.14.2 Security threats - -Adversarial attacks on AI/ML models can be launched by sophisticated attackers using techniques such as data poisoning, model inversion, or evasion attacks. - -Attackers may exploit vulnerabilities in AI/ML models to compromise the integrity of network optimization and anomaly detection functions, leading to potential security breaches or disruptions to network operations. - -### 5.14.3 Potential security requirements - -The O-RAN architecture elements should support continuous security monitoring of AI/ML models and datasets to detect and prevent adversarial attacks. - -## 5.15 Key Issue #14: AI/ML-related data integrity and confidentiality - -### 5.15.1 Introduction - -AI/ML models in O-RAN architecture elements rely on large datasets for training and operation. However, the collection, storage, and transmission of these datasets introduce risks related to data integrity and confidentiality. If an attacker gains unauthorized access to or manipulates the datasets, it can compromise the accuracy and reliability of AI/ML models. - -### 5.15.2 Security threats - -Unauthorized access or manipulation of AI/ML-related data leads to the following security threats: - -- Data Manipulation (MITRE ATT&CK [i.11] T1565): Adversaries can alter the dataset to introduce biases or errors. - -- Data Exfiltration (MITRE ATT&CK [i.11] TA0010): Sensitive data can be leaked, leading to privacy breaches and potential exploitation. -- Content Injection (MITRE ATT&CK [i.11] T1659): Malicious data can be injected into the dataset to compromise the model's performance. - -### 5.15.3 Potential security requirements - -The O-RAN architecture elements should support continuous security monitoring of events related to data storage and transmission to detect and prevent unauthorized access or manipulation of AI/ML-related data. - -## 5.16 Key Issue #15: Model explainability and transparency - -### 5.16.1 Introduction - -AI/ML models used in O-RAN networks can be complex and difficult to interpret, making it challenging to understand their decision-making processes. This lack of transparency and explainability can make it difficult to detect and respond to potential security threats. - -### 5.16.2 Security threats - -The lack of transparency and explainability in AI/ML models can make it challenging to detect and respond to potential security threats, potentially leading to delayed or inadequate incident response (MITRE ATT&CK [i.11]: T1406 - Obfuscated Files or Information). - -Attackers may exploit the lack of transparency and explainability to launch attacks that are difficult to detect or attribute. - -### 5.16.3 Potential security requirements - -The O-RAN architecture elements should support continuous security monitoring of AI/ML model performance and events related to model performance to detect and respond to potential security threats. - -The O-RAN architecture elements should support continuous security monitoring of AI/ML model decision-making processes to detect and respond to potential security threats. - -## 5.17 Key Issue #16 Model and data drift - -### 5.17.1 Introduction - -Model and data drift can occur over time, leading to degraded performance of AI/ML models. Continuous monitoring is necessary to detect and address drift to maintain the effectiveness of network optimization and anomaly detection. - -### 5.17.2 Security threats - -Model and data drift leads to the following security threats: - -- Concept Drift: Changes in the underlying data distribution can lead to model inaccuracies. -- Data Drift: Changes in the input data characteristics can affect model performance. -- Model Drift: The model's predictions may become less accurate over time due to changes in the environment. - -### 5.17.3 Potential security requirements - -The O-RAN architecture elements should support continuously monitor model performance metrics to detect and address drift. - -## 5.18 Key Issue #17: Secure monitoring information sharing channels - -### 5.18.1 Introduction - -Establishing secure channels for information exchange, transporting security monitoring data, is crucial for effective security monitoring in the O-RAN ecosystem. These channels must ensure the confidentiality, integrity, and availability of shared security data and threat intelligence. - -### 5.18.2 Security threats - -Insecure information sharing channels cause the following security threats: - -- **Unauthorized access to sensitive information:** An attacker could intercept or exploit vulnerabilities in the information sharing channels, gaining access to sensitive security data or threat intelligence. -- **Data tampering:** An attacker could modify or manipulate the shared information, compromising its integrity and potentially leading to incorrect security decisions. -- **Eavesdropping:** An attacker could intercept and listen to sensitive information shared between stakeholders, compromising confidentiality. -- **Denial of Service (DoS) Attacks:** Disrupting the availability of information exchange channels. - -### 5.18.3 Potential security requirements - -The O-RAN architecture elements should establish secure information sharing channels by the following means: - -- Support end-to-end encryption for all information shared between stakeholders. -- Establish access controls, including authentication and authorization, to ensure only authorized entities can access shared information. -- Support data integrity checks to detect any tampering or modifications. -- Support redundant communication channels and failover mechanisms to maintain availability. - -## 5.19 Key Issue #18: Monitoring data ownership and privacy - -### 5.19.1 Introduction - -Addressing privacy and data ownership concerns is essential to ensure that shared information is used appropriately and complies with regulatory requirements. This involves defining and implementing clear policies and procedures for data handling and access control. - -### 5.19.2 Security threats - -Not implementing clear policies and procedures for data handling and access control causes the following security threats: - -- **Unauthorized Access:** Unauthorized parties gaining access to sensitive data. - -- Data Misuse: Authorized users misusing shared data for unintended purposes. -- Regulatory Non-Compliance: Failure to comply with data protection regulations such as GDPR or CCPA. -- Insider Threats: Malicious insiders exploiting their access to sensitive information. - -### 5.19.3 Potential security requirements - -The O-RAN architecture elements should implement the following policies and procedures for data handling and access control: - -- Establish clear data ownership and usage policies, defining what data can be shared, with whom, and under what conditions. -- Implement data anonymization or pseudonymization techniques to protect sensitive information. -- Ensure compliance with relevant regulations, such as GDPR, CCPA, or HIPAA, when handling and sharing sensitive data. -- Define and enforce data handling and storage standards for all stakeholders. -- Regularly review and update data sharing agreements to ensure they remain relevant and effective. - -## 5.20 Key Issue #19: Eavesdropping Attacks in O-RAN - -### 5.20.1 Key issue detail - -Eavesdropping attack is when an attacker intercepts and listens to communications without the parties involved being aware of it [i.26]. In O-RAN, this threat includes malicious actors capturing unprotected CUS-Plane data, exposing sensitive information exchanged between the O-DU and O-RU. Adversaries may use various techniques to eavesdrop data in transit on the Open FH interface, which connects the O-DU and O-RU. While 3GPP proposes encryption for the NR-Uu user plane and control plane to protect sensitive data at PDCP and above layers, all layers below PDCP in Open FH U-Plane and all layers in Open FH C/S-Plane remain unencrypted [i.28], leaving them vulnerable. These vulnerabilities allow adversaries to eavesdrop on unprotected data at lower layers (RLC, MAC, and PHY) [i.27], increasing the risk of data breaches and unauthorized access to O-RAN architecture. - -### 5.20.2 Security threats - -- A malicious tenant with access to the transport protocol stack can sniff and capture unprotected CUSM-Plane data in shared tenant, [I.2]- T-SharedORU-43. -- Attackers with Layer 2 access in the Open FH can perform the following actions against eCPRI and PTP protocols: - - An adversary can identify all layers of C-Plane traffic including eCPRI messages and all layers of U-Plane traffic including eCPRI messages up to but not including PDCP and above layers based on their corresponding Ethertype value of 0xAEFE [i.29]. - - An adversary can eavesdrop on all traffic on S-Plane and identify all PTP messages based on its corresponding Ethertype value of 0 × 88F7 [i.29]. - -### 5.20.3 Potential Security Requirements: - -O-RAN systems should expose logs that could help detect potential eavesdropping. Examples of such logs include: - -- Capture relevant events from the link layer that may indicate physical tampering with the link by malicious actors. Example of the events include link down/link up, changes in quality of signal strength- resulting in speed changes. -- O-RAN system shall continuously monitor the network to detect any unauthorized O-RAN architecture elements or devices, including transport network element (TNEs). - -## 5.21 Key Issue #20: Attacks on O-RAN security log streaming and storage. - -### 5.21.1 Introduction - -Log streaming is the uninterrupted, real-time transfer of log data for the purpose of collecting logs from multiple sources to a central repository with integrated storage, enabling rapid threat detection, immediate analysis, and reliable retention for compliance and forensic purposes [i.30]. In O-RAN, log collection and management are typically handled by dedicated security log collection system responsible for aggregating logs from various architecture elements and forwarding them to centralized logging infrastructures such as Security Information and Event Management (SIEM) systems. These logs are critical for continuous security monitoring, forensic investigations, and regulatory compliance. Because log streaming and storage are fundamental to O-RAN security operations, adversaries may target the log streaming process itself or the associated storage systems. Potential attacks include intercepting log data in transit, compromising log storage server, or manipulating log to evade detection. - -### 5.21.2 Security Threats - -- An adversary could launch DoS attacks against log collection system responsible for log aggregation, overwhelming their capacity to receive or transmit log data. -- Adversaries may target centralized logging infrastructure, such as SIEM systems, to prevent log storage, tamper with log data, or gain unauthorized access. Such compromises can undermine security monitoring and allow attackers to evade detection. -- To better understand the environment, adversaries may also monitor logs in real time to track incident response procedures. This may allow them to adjust their techniques to maintain persistence or evade defences [i.31] -- Logs may also be exfiltrated to adversary-controlled infrastructure for offline analysis to understand the infrastructure and extract sensitive information such as credentials, network elements information that may be used for lateral movement or privilege escalation [i.31]. -- The following threats have been identified in [i.2] T-SMO-09, T-SMO-10, T-SMO-13, T-SMO-14, T-SMO-15, T-SMO-16, T-SMO-17, T-SMO-18. - -### 5.21.3 Potential Security Requirements - -O-RAN system should expose necessary data to enable effective analysis and detection of attacks targeting log streaming and storage within the O-RAN architecture elements. - -## 5.22 Key Issue #21: Attacks on the PTP Network - -### 5.22.1 Introduction - -The Precision Time Protocol (PTP) [i.32] is fundamental to accurate time synchronization in O-RAN infrastructure. Adversaries are capable of exploiting vulnerabilities across these PTP elements. For example, adversaries might launch spoofing attacks during the Announce phase to manipulate the Best Master Clock (BMC) algorithm or conduct message delay manipulation during the Delay Request/Response phase to skew delay calculations. They could also perform data manipulation or replay attacks on Sync/Follow\_Up messages to alter timestamps and disrupt time distribution. Additionally, PTP behaviour can change over time due to factors like Global Positioning System (GPS) reception failure, issues with PTP grandmaster or boundary clocks, and network problems such as congestion or asymmetry. Therefore, continuous security monitoring of PTP element is paramount. - -### 5.22.2 Security Threats - -- An adversary compromises the master clock's time source, injecting inaccurate time and disrupting network-wide clock synchronization. -- The following threats have been identified in [i.2] T-SPLANE-01, T-SPLANE-02, T-SPLANE-03, T-SPLANE-04, T-SPLANE-05. - -### 5.22.3 Potential Security Requirements - -O-RAN system should be able to expose necessary data which can be used to analyse and detect potential PTP attacks. - -## 5.23 Key Issue #22: Unauthorized External Communication - -### 5.23.1 Introduction - -Advanced Persistent Threats (APT) is a category of attackers that seek to gain access to a system to obtain information and maintain access over time. Usually, APTs do not set out to perform attacks that damage or degrade a system but instead seek to maintain access to non-public data. This sometimes involves subverting components or identities to communicate with outside command and control (C2) systems and/or exfiltrate data [i.11]. - -### 5.23.2 Security threats - -Not implementing clear policies and procedures to monitor for APTs causes the following security threats: - -- Unauthorized Access: Unauthorized parties gaining access to sensitive data using compromised credentials, overly permissive access rules, or broken access controls. -- Eavesdropping: An attacker could intercept and listen to information shared between stakeholders, compromising confidentiality. -- Regulatory Non-Compliance: Failure to comply with data protection regulations such as GDPR or CCPA. - -### 5.23.3 Potential security requirements - -The O-RAN architecture elements should implement the following policies and procedures to decrease the risk associated with unauthorized external communication by APTs: - -- Enforce strict access control policies on data, with logging of all access requests. -- Implement regular auditing of identities issued and used, with revocation of credentials that are no longer needed or in use. -- Ensure compliance with relevant regulations, such as GDPR, CCPA, or HIPAA, when handling and sharing sensitive data. -- Use threat intelligence services to learn/block newly discovered malicious URLs, endpoints and C2 domains. -- Monitor O-RAN system communications to external services for potential data exfiltration. - -## 5.24 Key Issue #23: Compromised O-RU, O-CU, O-DU - -### 5.24.1 Introduction - -O-RAN is openly available through open-source software, enabling the manipulation of O-RU, O-DU, and O-CU software and subsequent compromised behavior of O-RUs, O-DUs, and O-CUs. - -According to the Nokia Threat Intelligence Report, “Threat actors are increasingly using generative AI to mount sophisticated attacks faster and on a larger scale” [i.4]. Generative AI is being used to craft more sophisticated attacks and with more ease, and these attacks also carry over to the telecommunications sector, enabling more attacks compromising O-RU, O-CU, O-DUs. - -These units can be compromised when an adversary gains unauthorized access to the unit or if there is a software misconfiguration. A compromised O-RU or O-CU or O-DU can be used to carry out attacks against UEs by eavesdropping on their sensitive data and to disrupt services to the UE by sending malicious signaling messages to the UE or to the Core Network. - -### 5.24.2 Security Threats - -If relevant data is not exposed to detect compromised O-RUs, O-CUs, and O-DUs, base stations can be compromised. Malicious actors may be able to compromise confidentiality, integrity and availability of the base station without being detected. - -Some attacks as described in [i.33] can be executed by a compromised O-RU, O-CU, O-DU. - -The security threats associated with compromised O-RU, O-CU, and O-DU include: - -- Security misconfiguration -- Manipulated Radio Configurations in O-RUs -- Passive user localization [i.33] -- Weak authentication and authorization -- Malicious O-RUs, O-CUs, O-DUs from an untrusted source -- Backdoors in trusted O-RUs, O-CUs, and O-DUs -- Vulnerabilities in trusted O-RUs, O-CUs, and O-DUs -- Remote code execution, privilege escalation etc - -If attackers can find an exploitable O-RU, O-CU, O-DU, they can disrupt the offered network service. The actual consequences may vary. For example, an attacker may be able to execute authentication relay attacks, man-in-the-middle attacks, extract sensitive information, etc. - -### 5.24.3 Potential Security Requirements - -An O-RAN architecture element can expose necessary data which can be used to analyse and detect compromised O-RUs, O-CUs, and O-DUs. - -An O-RAN architecture element can support the detection of a compromised base station based on data collected from O-RAN and non-O-RAN architecture elements - -# --- 6 Mitigations and solutions - -## 6.1 Introduction - -In this clause, the solutions will be introduced, and respective solution details and possible evaluation means will be described. - -## 6.2 Solution #1: Data required for detecting DoS attacks due to flooding - -### 6.2.1 Introduction - -This solution proposes a DoS attack detection and prevention function that collects data from all architectural elements in O-RAN to determine whether a DoS attack might be occurring. The DoS attack that is mitigated by this solution is the packet flooding variation of a DoS attack. Only rate-based DoS attacks are covered by this solution. - -Implementations of the DoS detection and prevention functionality may vary, but this application should include following functionalities to mitigate the risks of DoS attacks: - -- Data should be collected from all architectural elements in O-RAN (e.g.: O-RU, O-CU, and O-DU) to detect DoS attacks across the entire network. - - The data that each architectural element provides can include the element identification information, number of packet bursts that are above a configured threshold, and packet origin. - - A log will also be provided which has detailed information about the data provided by each element. - - The data can also include alerts which are when number of packet bursts exceed the preconfigured threshold. - -### 6.2.2 Solution Details - -Any NF should provide data that can indicate a potential DoS attack caused by packet flooding. - -The data that should be provided can be grouped into three categories: data for statistical analysis, data for security events (alarms/logs), and data for configuration as indicated in Table 6.2-1, Table 6.2-2 and Table 6.2-3 respectively. - -One procedure to detect DoS attacks related to packet flooding is counting the number of packets and detecting the source of the largest number of packets. - -**Table 6.2-1 - Data for statistical analysis** - -| DoS Packet Flooding Metrics | Description | Examples | -|--------------------------------------------|--------------------------------------------------------------------------------|-----------------------| -| NF ID | Unique identification for an O-RAN architectural element instance | O-CU_ID | -| Interface ID | Unique identification for an interface | O-CU_F1U_ID | -| Number of packets received | A counter related to DoS packet flooding attack detection using TCP/IP packets | 3 (an integer [0..n]) | -| Origins for the largest number of packets. | Source IP addresses of the largest number of TCP/IP packets | | - -**Table 6.2-2 - Data for security events (alarms/logs)** - -| Category | Data | Example | -|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------| -| Alarm | Alarm information
Source IP
Destination IP
Probable cause (Denial of Service due to packet flooding) (an operational violation event as referred to in section 8.1.2.1 of [i.15]) | DDoS_packet_flooding_alarm_ID | -| Logs | Time
Unique ID
Source IP
Destination IP | DoS_packet_flooding | - -**Table 6.2-3 - Data for configuration** - -| Configurations for DoS Packet Flooding Data Collection | Examples | -|----------------------------------------------------------------|----------------------------------------------------------------| -| Threshold for counters (e.g.:) | 1000/s | -| Threshold that raises an alarm Alarm_DDoS_Packet_Flooding | Alarm is active if the counter measured is above the threshold | - -The O-RAN NFs should be able to expose necessary data which can be used to analyse and detect potential DoS attacks due to packet flooding on any O-RAN architectural element. The data that should be standardized includes the following: parameters for configuration, unique IDs for alarms/logs, and counter nomenclature and definition and is described in Table 6.2-4 . - -**Table 6.2-4 - Data for standardization** - -| Data Type | Description | -|--------------------------------------------------------|-------------------------------------------------------------------------| -| Parameters for Configuration | Parameters for configuration (thresholds for counters and alarms) | -| Unique Identification Descriptions for Alarms and Logs | Unique ID for alarms and logs | -| Counter Nomenclature | The counter names | -| Counter Definition | Definition for counters that indicate number of packets per time period | - -### 6.2.3 Evaluation - -This solution addresses the Key Issue “Data Required for DDoS Attacks”. This solution enforces the requirement from the Key Issue regarding obtaining data from all O-RAN architectural elements. By gathering needed data from all O-RAN architectural elements, there will be insight into whether a DoS attack due to packet flooding is occurring. - -## 6.3 Solution #2: Data required to detect API security risks (DoS through resource consumption) - -### 6.3.1 Introduction - -Key Issue #2 “Data required to detect API security risks” describes the risks for APIs in the O-RAN architecture. The particular API security risk addressed in this solution is Denial-of-Service (DoS) due to unrestricted resource consumption. The API security risk from the OWASP API Security Top 10 project [i.5] addressed in this solution is API4:2023 Unrestricted Resource Consumption for APIs. An O-RAN architecture element may provide an API for communication and access to hosted services. An adversary may attempt to disrupt operations and degrade network performance by sending an overwhelming number of requests within a short period of time to execute a Denial-of-Service (DoS) attack. Detection of an API DoS attack through resource consumption depends upon the ability to collect information on resource consumption and API request messages. - -The data may be collected internally by the O-RAN architecture elements, for example by the SMO, or a dedicated network function, or externally by a pre-existing system deployed by the operator. - -### 6.3.2 Solution details - -This type of monitored attack can be assigned and tagged with a unique ID derived from associated API security risk from [i.5] as indicated in Table 6.3-1: - -**Table 6.3-1 - O-RAN API DoS Unique ID** - -| Type of Attack | O-RAN Unique ID | -|------------------------------------|--------------------------| -| O-RAN API DoS Resource Consumption | API_OWASP2023_4_RESOURCE | - -The Table 6.3-2 below provides examples of data to be collected to detect an API DoS attack through resource consumption. - -**Table 6.3-2 - Example data associated with O-RAN API DoS resource consumption** - -| Data Type | Example Events or Items of Interest | -|------------------------|---------------------------------------------------------------------------------------------------------------------------------| -| Resource utilization | Above average utilization of resources such as memory, and compute | -| API requests/responses | Above average frequency of requests within a given duration
Parameters such as IP addresses, HTTP Methods, HTTP Status Codes | -| NF information | NF ID, NF instance information such as average number of instances and peak number of instances | -| Counters | API invocations within a given duration | - -### 6.3.3 Evaluation - -Collecting data in Table 6.3-2 above may help provide visibility of a DoS attack on APIs deployed by an O-RAN architecture element. Normal baseline levels of activity can be established through monitoring and collection of the aforementioned data, which may allow the detection of anomalous activity for resource utilization and API communications that may be indicative of a DoS attack. A unique ID is also assigned to the attack to provide easy reference inside a playbook to indicate what type of data may be useful within the context. - -## 6.4 Solution #3: Continuous security monitoring for adversarial attacks on AI/ML models - -### 6.4.1 Introduction - -The use of AI/ML models in O-RAN architecture elements introduces new security risks, particularly the threats of adversarial attacks and data drift. Also, the lack of transparency and explainability in AI/ML models used in O-RAN architecture elements can make it challenging to detect and respond to potential security threats. To mitigate these risks, continuous security monitoring of AI/ML models and datasets is essential. - -Model and data drift can cause security threats as mentioned in Key Issue #16. Due to model and data drift, the following security threats can occur: data drift, model drift, and concept drift, which can all affect the performance of the model. - -Therefore, there should be a way to detect and address these different types of drift. All architecture elements that rely on AI/ML should detect the different kinds of drift and address them to preserve the performance of the model in the event of a drift. - -This solution proposes a continuous security monitoring method that detects and addresses the drift using Machine Learning anomaly detection, drift detection methods, and autoencoders. - -### 6.4.2 Solution details - -To address the key issues of adversarial attacks on AI/ML models, Model Explainability and Transparency and Model and Data Drift, the following requirements are proposed: - -- Continuous Monitoring of AI/ML Models:** Implement real-time monitoring of AI/ML models to detect anomalies, model and data drift, and potential security threats. This can be achieved through the use of machine learning-based anomaly detection techniques, such as One-Class SVM [i.16], Autoencoders [i.17] , or the Page-Hinkley Method [i.44] as in Table 6.4-1. - -**Table 6.4-1 - ML-based anomaly detection technique** - -| ML-based anomaly detection technique | Explanation | -|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| One-Class SVM | One-class Support Vector Machines are a type of outlier detection method, using ML techniques to automatically define a boundary to detect outliers in a given input set. [i.16]. This can be used to detect model drift. | -| Autoencoders | An Autoencoder is a neural network used for unsupervised learning, trained to reconstruct its input data out of a previously learned compressed form of it. [i.17]. This can be used to detect concept drift. | -| Page-Hinkley Method | Statistical method used to detect changes in the mean of a data series over time. [i.44] This can be used to detect data drift. | - -- Model Performance Metrics:** Continuously monitor model performance metrics to detect potential drift or degradation in model performance, such as in Table 6.4-2: - -**Table 6.4-2 - Metrics** - -| Metric | Explanation | -|-----------|---------------------------------------------------------------------------------------| -| accuracy | number of correct predictions divided by the total number of predictions | -| precision | ratio of true positives and total positives predicted | -| recall | ratio of true positives over the sum of the true positives and false negatives [i.45] | - -Each architecture element will detect drift based on its own models. Once a drift is detected, the model will discard the data collected at that time to mitigate the impact of the data or model drift. The architecture element model will preserve historical data collected prior to the drift. - -Each model will have a baseline model that is trained prior to data collection, and in the event of a drift, the model will be retrained on the baseline model. These baseline models are retrained periodically to account for natural shifts in the model and data. - -- **Logging of AI/ML data:** Implement logging of security related metrics and data to log anomalies and drift such as in Table 6.4-3 and Table 6.4-4: - -**Table 6.4-3 - Data for Security Events (Alarms/Logs)** - -| Category | Data | Example | -|----------|-----------------------------------------------------------------------------------------------------|------------------------------------------------------| -| Alarm | Alarm information
Architecture element ID
Probable cause (Drift detected or anomaly detected) | Drift_detected_alarm_ID
Anomaly_detected_alarm_ID | -| Logs | Time
Architecture element ID
Metrics (accuracy, precision, recall) | Drift_detected
Anomaly_detected | - -**Table 6.4-4 - Data for Configuration** - -| Configurations for anomaly detection and drift detection | Examples | -|----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------| -| Condition that raises an alarm
Drift_detected or anomaly_detected | Alarm is active if anomaly detection technique detects anomaly or drift above a particular threshold | - -### 6.4.3 Evaluation - -This solution addresses the Key Issues #13, #15, and #16 – “Adversarial Attacks on AI/ML models”, “Model explainability and transparency”, and “Model and Data drift”, which mentions the security threats of adversarial attacks and model drift, data drift, and concept drift. This solution provides a method for all architecture elements to continuously monitor performance metrics to address and detect adversarial attacks and drift as mentioned in the Key Issues. - -## 6.5 Solution #4: Continuous security monitoring for AI/ML-related data integrity and confidentiality - -### 6.5.1 Introduction - -The collection, storage, and transmission of large datasets for AI/ML models in O-RAN architecture elements introduce risks related to data integrity and confidentiality. To mitigate this risk, continuous security monitoring of data storage and transmission protocols is essential to detect and prevent unauthorized access or manipulation. - -### 6.5.2 Solution details - -To address the key issue of AI/ML-related data integrity and confidentiality, the following requirements are proposed: - -- **Data Integrity Checks:** Continuously monitor data integrity to detect potential data manipulation or tampering. -- **Intrusion Detection:** Continuously monitor AI/ML- related system parameters to detect potential security threats or breaches. - -The effectiveness of this solution can be determined through the following metrics: - -- **Data Breach Detection:** Measure the number of potential data breaches detected through continuous monitoring. -- **Data manipulation or tampering detection:** measure the number of data manipulations detected through continuous monitoring. - -### 6.5.3 Evaluation - -This solution addresses Key Issue #14 – “AI/ML-related data integrity and confidentiality”. By proposing continuous monitoring through data integrity checks and intrusion detection, this solution provides methods for O-RAN architecture elements to support the continuous security monitoring of events related to data storage and transmission in order to detect and prevent unauthorized access or manipulation of AI/ML-related data. - -## 6.6 Solution #5: Continuous security monitoring for software delivery - -### 6.6.1 Introduction - -The software delivery process is a critical component of the O-RAN architecture elements security, as it is susceptible to malicious actors who may inject harmful code or introduce vulnerabilities. While the O-RAN specification does not comprehensively cover software delivery, it provides essential security requirements that form the foundation for addressing this issue. This clause proposes a solution to enhance the security of software delivery through continuous monitoring, leveraging existing O-RAN security measures to ensure the integrity and authenticity of software packages. - -### 6.6.2 Solution details - -To mitigate the risks associated with compromised software delivery, the following measures are proposed: - -#### Continuous security monitoring of software validation during onboarding: - -- Provide real-time monitoring data on functions that verify the digital signatures and integrity of software packages, ensuring compliance with O-RAN security requirements (e.g., REQ-SEC-ALM-PKG-2, REQ-SEC-ALM-PKG-4) with security logs as indicated in Table 6.6-1 and Table 6.6-2 below. - -**Table 6.6-1 - Data for software validation during onboarding** - -| ID | Description | Examples | -|---------------------------|--------------------------------------------------|----------------------------| -| AppPackID | Unique identification for an Application package | | -| SignatureValidationResult | Result of the signature verification | successful
unsuccessful | -| IntegrityValidationResult | Result of the integrity verification | successful
unsuccessful | - -#### Continuous security monitoring of vulnerability management: - -- Monitor the reporting of vulnerabilities discovered during testing, adhering to O-RAN's vulnerability management requirements (e.g., REQ-SEC-ALM-PKG-7B). - -**Table 6.6-2 - Data for software vulnerability management** - -| ID | Description | Examples | -|---------------------------|----------------------------------------------------------------|------------| -| AppPackID | Unique identification for an Application package | | -| VulnerabilitiesDiscovered | A list of vulnerabilities discovered for an ApplicationPackage | CVE number | - -The effectiveness of this solution can be determined through the following metrics: - -- **Detection Rate:** Measure the number of adversarial attacks detected through continuous monitoring. -- **False Positive Rate:** Measure the number of false positives generated by the monitoring system - -### 6.6.3 Evaluation - -This solution addresses Key Issue #11 – “Compromised software delivery” as it proposes continuous security monitoring of software validation during onboarding and continuous security monitoring of vulnerability management. - -## 6.7 Solution #6: Continuous security monitoring for authentication attacks - -### 6.7.1 Introduction - -Authentication related attacks need to be mitigated after sufficient monitoring on the O-RAN NFs and interfaces where authentication takes place. - -### 6.7.2 Solution details - -For monitoring authentication related attacks the following data could be collected as prescribed in [i.11] and in Table 6.7-1, Table 6.7-2, Table 6.7-3 and Table 6.7-4 below . For example, authentication logs can be reviewed to ensure that mechanisms such as enforcement of MFA are functioning as intended. - -**Table 6.7-1 - Security logs for authentication attacks** - -| Security logs | | | -|---------------------------------------------------------------------------------------------|----------------------------------------------------------|-----------------------------------------------------------------| -| Description | ID | Example | -| Successful and unsuccessful cases | Successful_authentication
Unsuccessful_authentication | Operation=
Unsuccessful_authentication,
userid='1234',etc | -| Security logs related to failure in multi factor authentication | Failure in multi authentication factor_log | Failure of password and fingerprint | -| Weak related or missing or not updated authentication related policies like password policy | Authentication_policy_not_updated | Policy not updated since x days | -| Security logs related to accessing of private keys | Private_key_access | Access to private keys attempted | -| Security logs related to accessing of certificates with out proper passphrase | Certificate_passphrase_attempted | Passphrase for certificate is wrong | - -**Table 6.7-2 - Security counters for authentication attacks** - -| Security related counters | | | -|-------------------------------------------------------------------|-----------------------------------------|---------| -| Description | ID | Example | -| Counter related to number of sessions exceeded | User_session_counter | | -| Counter for number of unauthenticated attempts | Authentication_failure_counter | | -| Counter related number of failed password attempts in time period | Password_failure_counter_in_time_period | | - -**Table 6.7-3 - Security alarms for authentication attacks** - -| Security related alarm | | | -|---------------------------------------|----------------------------------|-----------------------------------------------------------| -| Description | ID | Example | -| Alarms for default password unchanged | Alarm_default_password_unchanged | Alarm attribute updated with 'Default password unchanged' | - -**Table 6.7-4 - Other security related data for authentication attacks** - -| Other security related data | | | -|----------------------------------------------------------------------|----------------------------------------------------|---------| -| Description | ID | Example | -| Time of day for authentication access to O-RAN architecture elements | | | -| Time of day related to brute-force attempt | | | -| Location | Could be derived from the IP address or inventory. | | - -### 6.7.3 Evaluation - -The effectiveness of this solution can be evaluated through the data definition for the solutions above and collection of logs, alarms, counters related to the authentication attacks as part of key issue #4. - -## 6.8 Solution #7: Continuous security monitoring for authorization attacks - -### 6.8.1 Introduction - -Authorization related attacks need to be mitigated through sufficient monitoring on the O-RAN NFs and interfaces where authorization takes place. - -### 6.8.2 Solution details - -For monitoring authorization related attacks, the following data as in Table 6.8-1, Table 6.8-2, Table 6.8-3 and Table 6.8-4 could be collected as in [i.11]. - -**Table 6.8-1 - Security logs for authorization attacks** - -| Security logs | | | -|----------------------------------------------------------------------------|-----------------------------------------------|------------------------------| -| Description | ID | Example | -| Security logs with authorization failures | Unauthorized access to O-RAN NF | Unauthorized access for user | -| Security logs with attempt to modify data without authorized access rights | Manipulation of data_attempted | | -| Logs related to privilege escalation | Misconfiguration | | -| Security logs indicating the excessive rights for long periods of time | Violation of the principle of least privilege | | - -**Table 6.8-2 - Security alarms for authorization attacks** - -| Security alarm | | | -|---------------------------------------|----|---------| -| Description | ID | Example | -| Alarm related to privilege escalation | | | - -**Table 6.8-3 - Security counters for authorization attacks** - -| Security counter | | | -|----------------------------------------------------------------------------|----|---------| -| Description | ID | Example | -| Counter related to number of permissions administered for a period of time | | | - -**Table 6.8-4 - Security related data for authorization attacks** - -| Other security related data | | | -|----------------------------------------------|----|---------| -| Description | ID | Example | -| Time of day for misconfiguration | | | -| Time of day for violation of least privilege | | | - -### 6.8.3 Evaluation - -The effectiveness of this solution can be evaluated through the data definition for the solutions above and collection of logs, alarms, counters related to the authorization attacks as part of key issue #6. - -## 6.9 Solution #8: Continuous security monitoring for cloud attacks related to lateral movement - -### 6.9.1 Introduction - -O-Cloud infrastructure and the applications deployed on it are prone to attacks related to lateral movement of the attacker. This can be achieved through techniques such as remote execution, privileged account escalation, and network-level exploitation. The goal of lateral movement is to maintain a persistent presence within the network and to eventually achieve the attacker's objectives. - -### 6.9.2 Solution details - -Preventing lateral movement attacks is a critical component of an effective cybersecurity strategy. There are several measures that can be used to proactively detect lateral movement on cloud infrastructure and the applications deployed on it, including the security logs, counters and alarms listed in the Table 6.9-1, Table 6.9-2 and Table 6.9-3 below: - -**Table 6.9-1 - Security logs for cloud attacks related to lateral movement** - -| Security Logs | | | -|-------------------------|----------------------------------------------------------------------------------------|-------------------------------------------------------------------------------| -| ID | Description | Example | -| Access_logs | Access Patterns: Monitoring of user access to NFs and cloud resources. | Eg:
number of times of access to a NF
Time of day to access the NF | -| Anomalous behaviour_log | Anomalous Behaviour Detection: Abnormal system calls or API usage. | eg: out of order API invocation | -| firewall_logs | Firewall Logs: Denied connections and unusual access attempts. | eg: Authentication_failure
Time of access | -| Security logs | Audit Logs: User access and privilege escalation events, including SSH and API logins. | eg: user access logs
privilege escalation logs
SSH logins
API logins | -| Interface_logs | Interface Information: Interfaces exposed by the service (Nmap scan) | eg:details of interface/service exposed by NF | - -**Table 6.9-2 - Security counters for cloud attacks related to lateral movement** - -| Security Counters | | | -|--------------------------|------------------------------------------------------------------------------------------------------|------------------------------------------| -| ID | Description | Example | -| Access_Counter | Number of times a user has accessed a NFs and/or cloud resources. Could be used for a access pattern | Eg:
number of times of access to a NF | -| Process_activity_counter | Process Activity: High CPU/memory-consuming processes or unexpected background tasks. | eg:CPU_Usage
memory usage of NF | - -**Table 6.9-3 - Security alarms for cloud attacks related to lateral movement** - -| Security Alarm | | | -|---------------------------|---------------------------------------------------------------------------------------|---------------------------------------------------------------------| -| ID | Description | Example | -| Process_activity_alarm | Process Activity: High CPU/memory-consuming processes or unexpected background tasks. | eg:
Alarm with probable cause indicating high memory consumption | -| Intrusion_Detection_Alarm | Intrusion Detection Alerts: Suspicious patterns identified by IDS/IPS systems. | eg: suspicious activity alarm from IDS NF | - -### 6.9.3 Evaluation - -The effectiveness of this solution can be evaluated through the data definition and collection of the metrics related to the lateral movement detection for cloud attacks. - -## 6.10 Solution #9: Detection and prediction of DoS attacks due to packet flooding using Density Based Clustering - -### 6.10.1 Introduction - -This solution proposes a DDoS Attack Detection and Prevention Function collecting data from all O-RAN architecture elements to determine whether a DoS attack due to packet flooding might be occurring. - -This solution is based on covering the threats related to DoS attacks as well as the data gathered with respect to DoS attacks due to packet flooding from Key Issue #1 and solutions #1 and #2. - -The DoS Attack Prevention and Detection Function uses Density Based Clustering to cluster the data it receives from each O-RAN architecture element to determine if a DoS attack due to packet flooding is occurring. Density Based Clustering (DBC) is used to detect clusters of concentrated points that are separated by sparse or empty areas; points that are not part of a cluster are labeled as noise. - -### 6.10.2 Solution details - -Implementations of the DDoS Detection and Prevention Function may vary, but this function may include the following functionalities in order to mitigate the risks detailed in Key Issue #1, in addition to solution #1, #2: - -- The DDoS Attack Detection and Prevention Function should collect data from all O-RAN architecture elements (O-RU, O-CU, and O-DU) to detect DDoS attacks across the entire network. - - The data that each architecture element provides can include the architecture element identification information, number of clusters that are above a configured threshold, and origins for the largest number of packets. -- Each architecture element applies a Density Based Clustering algorithm to the packets it receives - - The Density Based Clustering algorithm will provide information about the most dense/populated clusters - - Dense clusters with a burst of packets can be indicative of a DDoS attack. - -Figure 6.10-1 illustrates a depiction of a burst of packets, which is a sequence of a large number of packets surrounded by sparsely populated areas. - -![Figure 6.10-1: A scatter plot showing 'Epoch_Time' on the x-axis (ranging from 70000 to 120000 with a multiplier of +1.6559e9) and 'Cluster' on the y-axis (ranging from 0 to 14). The plot shows a series of small, distinct clusters at lower epoch times, followed by a large, dense, horizontal cluster of points between epoch times 90000 and 120000. A red oval highlights this dense cluster, and a callout bubble above it contains the text 'Long Cluster indicating flood of packets (potential DDoS)'. A legend on the right titled 'Density based Clusters' shows 15 color-coded points labeled 0 through 14.](9c1941fcc429d4fd6e7ad245285c5c33_img.jpg) - -Figure 6.10-1: A scatter plot showing 'Epoch\_Time' on the x-axis (ranging from 70000 to 120000 with a multiplier of +1.6559e9) and 'Cluster' on the y-axis (ranging from 0 to 14). The plot shows a series of small, distinct clusters at lower epoch times, followed by a large, dense, horizontal cluster of points between epoch times 90000 and 120000. A red oval highlights this dense cluster, and a callout bubble above it contains the text 'Long Cluster indicating flood of packets (potential DDoS)'. A legend on the right titled 'Density based Clusters' shows 15 color-coded points labeled 0 through 14. - -Figure 6.10-1 - Diagram illustrating burst of packets - -![Overall system level view of DBC implementation diagram showing packet clusters on interfaces, DBC metrics, and DADPF analysis.](ed48e24e36ea0501953177401c900f86_img.jpg) - -The diagram illustrates the overall system level view of DBC implementation. A 'Network Entity' box contains two interfaces. 'Interface 1' shows two clusters of packets over 'time': 'Cluster 1: Small cluster of packets on interface 1' and 'Cluster 2: Burst of packets on Interface 1 showing as a big cluster'. An arrow points from Cluster 2 to 'Topmost cluster: Burst of 10 packets'. Below this, 'Apply DBC' is shown with a graph of 'cluster' vs 'time' for Interface 1. 'Interface 2' also has an 'Apply DBC' graph, but it shows 'No cluster found which Indicate a burst of packets'. To the right, 'DBC Metrics: {Network Entity ID, Source ID, Interface 1, Max burst size}' are shown being sent to a 'DADPF' (Data Analytics and Profiling Function) box. Inside DADPF, there is a 'DBC Metrics Historic data' cylinder and a head icon with a brain. An arrow from the head icon points to a box labeled 'Predict DoS attacks on Interface 1 for this Network Entity'. - -Overall system level view of DBC implementation diagram showing packet clusters on interfaces, DBC metrics, and DADPF analysis. - -Figure 6.10-2 - Overall system level view of DBC implementation - -In Figure 6.10-2, DBC Metrics can be cluster ID, number of packets, and top sources for the clusters crossing a configured threshold. DADPF is an analytics function that uses DBC metrics received from various O-RAN architecture elements, correlates DBC metrics, and enables prediction of DoS attacks to proactively mitigate risk. - -Table 6.10-1 - Example description of clusters exceeding threshold - -| Cluster | Packet Count | Top Source IPs Exceeding Threshold | -|---------|--------------|------------------------------------| -| 1 | 21850 | [192.168.0.7, 192.168.0.10] | -| 2 | 605 | [192.168.0.1, 192.168.0.9] | -| 3 | 11878 | [192.168.0.8, 192.168.0.10] | -| 4 | 15920 | [192.168.0.7, 192.168.0.8] | - -Table 6.10-1 depicts an example of summary statistics that DBC provides that shows the different clusters detected and source IP addresses that have the most number of clusters that exceed the configured threshold. If a cluster exceeds the threshold, that indicates that the cluster is an example of a DoS caused by packet flooding. - -Each architecture element calculates DBC metrics based on data it collects as indicated in solution #1. - -DBC Metrics can be transferred from the O-RAN architecture element to an NF that analyses DBC metrics. - -### 6.10.3 Evaluation - -This solution provides details of a possible implementation option to collect and analyse data collected from each architecture element in O-RAN to detect and prevent DoS attacks. This solution also enforces the requirement from Key Issue 1 regarding obtaining data from all O-RAN architecture elements. - -## 6.11 Solution #10: Secure the transmission of security monitoring data - -### 6.11.1 Introduction - -The O-RAN ecosystem relies heavily on the secure exchange of security monitoring data and threat intelligence between stakeholders, including network operators, vendors, and third-party security providers. However, the communication channels used for this information exchange are vulnerable to various cyber threats. Unauthorized access, data tampering, eavesdropping, and denial of service (DoS) attacks can compromise the confidentiality, integrity, and availability of shared data, leading to ineffective security monitoring and potentially catastrophic security breaches. This clause proposes a solution to address these threats and ensure secure information sharing channels in the O-RAN ecosystem. - -EXAMPLE: Information sharing channels exchanging security monitoring data defined by O-RAN specification include: - -- Open Fronthaul m-plane interface (see [i.22], clauses 10 to 12) -- O1 interface (see [i.23], clauses 2.2 to 2.5) - -### 6.11.2 Solution Details - -To mitigate the identified threats, the following solution is proposed: - -**End-to-End Encryption:** All security monitoring data and threat intelligence exchanged between stakeholders must be encrypted using strong cryptographic protocols, such as Transport Layer Security (TLS) or Internet Protocol Security (IPsec). This ensures that even if data is intercepted, it cannot be read or exploited by unauthorized parties. The encryption keys must be securely managed, with regular rotation and revocation mechanisms to minimize the impact of key compromise. - -**Mutual Authentication and Authorization:** Implement robust authentication and authorization mechanisms to ensure that only authorized entities can access or transmit sensitive information. This can be achieved through: - -- Mutual Transport Layer Security (mTLS): Requires both the client and server to authenticate each other using digital certificates. -- OAuth 2.0: Provides secure token-based authentication and authorization for APIs and services. -- Role-Based Access Control (RBAC): Restricts access to sensitive data based on the role or privilege level of the requesting entity. - -**Data Integrity Verification:** To detect tampering or unauthorized modifications during transit, implement cryptographic checksums or digital signatures (e.g., HMAC or ECDSA) for all shared data. This ensures that any changes to the data can be detected, and the integrity of the information is maintained. - -**Redundant and Failover Communication Channels:** To maintain availability and protect against DoS attacks, deploy redundant communication channels and failover mechanisms. This ensures that if one channel is compromised or becomes unavailable, an alternative channel can be utilized seamlessly. Additionally, implement traffic load balancing and filtering to mitigate the impact of DoS attacks. - -The effectiveness of the proposed measures can be evaluated through the following methods: - -**Penetration Testing:** Conduct regular penetration testing to simulate unauthorized access attempts and ensure that the encryption, authentication, and authorization mechanisms are robust and effective. Testing should also verify that data integrity checks can detect tampering attempts. - -**Security Audits and Compliance Checks:** Perform periodic audits to ensure compliance with established security standards and verify the proper implementation of encryption, access controls, and integrity checks. Logs and monitoring data should be reviewed to detect any unauthorized access or tampering attempts. - -**Availability and Redundancy Testing:** Test the failover mechanisms and redundant channels under controlled conditions (e.g., simulated DoS attacks or network outages) to ensure that the system maintains availability and continuity of operations. - -**Performance Impact Assessment:** Measure the performance impact of the implemented security measures (e.g., encryption overhead, latency introduced by authentication processes) to ensure they do not degrade the overall functionality of the O-RAN ecosystem. - -### 6.11.3 Evaluation - -By implementing these evaluation methods, the O-RAN ecosystem can ensure that the secure monitoring information sharing channels are robust, reliable, and effective in mitigating the identified threats. This solution addresses the key issue #17: “Secure monitoring information sharing channels”. - -## 6.12 Solution #11: Continuous security monitoring for open-source software delivery - -### 6.12.1 Introduction - -The O-RAN system's reliance on open-source software components introduces significant security risks due to the potential for tampering by malicious actors. Open-source software is widely used across the O-RAN ecosystem, and while it offers benefits such as transparency and collaboration, it also exposes the system to threats where attackers can intentionally introduce vulnerabilities or backdoors. These threats can lead to unauthorized access, disruption of system operations, or theft of sensitive information. Additionally, malicious code can create backdoors, allowing attackers to maintain persistent access even after vulnerabilities are patched. Addressing this issue requires a robust solution to monitor and detect tampering in open-source software components effectively. - -### 6.12.2 Solution Details - -To mitigate the risks associated with tampering of open-source software components, a vendor can make use of the following solutions: - -#### **Continuous monitoring of Open-source software repositories:** - -- Source Code Monitoring: Implement automated tools to continuously scan open-source repositories for suspicious activities, such as unexpected commits, unauthorized changes, or the introduction of malicious code. - -EXAMPLE: among others, GitGuardian [i.24] provides some services monitoring git repositories as in Table 6.12-1 - -- Process Monitoring: Monitor the software delivery process, including CI/CD pipelines, for unauthorized access or tampering. - -EXAMPLE: among others, Codecov [i.25] can help track changes in code coverage and identify suspicious activity during the build process. - -**Table 6.12-1 - Examples of metrics for open-source software repositories** - -| Metric | Attributes | Explanation | -|----------------------------|------------------|----------------------------------------------------------------------| -| issues_total | Severity, Status | All incidents in the monitored system | -| Commits_processed | Accounts | All commits processed by the monitored system | -| http_request_success_total | API | Successful HTTP requests | -| http_request_failure_total | API, status code | Failed HTTP requests | -| task_periodicity | Task name | Periodicity of periodic tasks | -| num_secrets | Source file name | Number of hardcoded access credentials found embedded in source code | - -#### **Anomaly Detection and Alerting:** - -- Deploy anomaly detection systems to identify unusual patterns in code commits, such as unusual commit frequencies, changes in code structure, or unexpected contributors as in Table 6.12-2. Machine learning-based detection systems are a practical option to achieve this. -- Set up alerts for suspicious activities, such as unexpected changes to critical components, to ensure timely response to potential tampering. - -**Table 6.12-2 - Examples of incidents in open-source software repositories** - -| Incident | Attributes | Explanation | -|------------------------|---------------------------|-------------------------------------------------------------------------------| -| excessive_code_commits | Accounts | the rate of code commits exceeds a predefined threshold | -| excessive_changes | Accounts | A commit contains a number of changes exceeding a predefined threshold | -| secret_in_code | Source file name, Account | A possible hardcoded access credential has been found embedded in source code | - -The effectiveness of the proposed solution can be evaluated through the following metrics and processes: - -#### **Detection Accuracy:** - -- Measure the ability of the solution to detect known vulnerabilities, malicious code, or unauthorized changes in open-source components. This can be done through regular penetration testing or simulated attacks. -- Track the number of false positives and false negatives to ensure the monitoring tools are tuned for accuracy. - -#### **Response Time:** - -- Measure the time taken to detect and respond to tampering incidents. This includes the time from the introduction of malicious code to its detection and mitigation. - -#### **Coverage:** - -- Assess the percentage of open-source components and dependencies being monitored. Ensure that all critical components are under continuous surveillance. - -### 6.12.3 Evaluation - -By implementing these measures, a vendor can significantly reduce the risk of tampering with open-source software components and ensure the integrity of the overall system. This solution addresses the key issue #7: “Tampering with open-source software”. - -## 6.13 Solution #12: Continuous Security Monitoring to Detect Unauthorized External Communication - -### 6.13.1 Introduction - -Advance Persistent Threat (APT) actors seek to gain and maintain access to resources in an organization over time to gain information about the organization or clients, customers or partners of the organization. APT attacks begin with an initial breach but then pivot within the organization to maintain or increase access privileges to resources. This maintaining of access often involves subverted components communicating with command and control systems external to the organization [i.11]. - -The goal of APTs is often the exfiltration of data for the organization. This requires the attack to be able to communicate with external, attacker controlled resources. This is sometimes done using different protocols than those often used for similar data transactions. - -This solution is related to alerting on authentication and authorization failures so solutions #6, #7 and #8 also apply for a comprehensive solution. A failure of authentication and authorization may indicate an APT attempting to move laterally or attempting to gain access to another resource. Strict checking of access controls is seen as a first line of defence against an attack attempting to move laterally. - -### 6.13.2 Solution Details - -To address the threat of APTs, multiple data sources need to be collected and used to flag suspicious use for investigation. The data collected in solution #6, #7 and #8 also apply and would be augmented with the following data: - -- Communication attempts with external sites known to host malware or be used for malware command and control. This requires the organization to maintain or have access to a list of known malicious sites (URLs, domain names, etc.). -- Communication attempts with external sites that are not part of the component's normal operating state. -- Changes or updates to components (both O-RAN defined and those outside of O-RAN) that fall outside of normal operations. -- Access requests and logins occurring outside of normal operations. - -### 6.13.3 Evaluation - -The effectiveness of the solution can be evaluated using the following metrics: - -- The number and rate of authentication and/or authorization failures that occur from access requests. -- Communication attempts to known malicious sites -- Communication requests to external sites that are in violation of policy or normal operations. -- Communication attempts by components that violate an organization's security policy. - -## 6.14 Solution #13: Data required to detect API security risks - -### 6.14.1 Introduction - -This solution proposal is for key issue #2. This solution provides examples of data which can be exposed by NFs to detect potential attacks performed on various APIs exposed by NFs in the O-RAN system. Here, the examples are considering the OWASP top 10 API security risks as a reference from [i.5]. Moreover, other API security risks like reverse engineering, API spoofing, etc. can also be considered and relevant data can be exposed for continuous security monitoring. - -Keeping in mind that the purpose of such security data exposure would be to detect potential exploitation of such risks on APIs, it is important to briefly understand what threat each risk poses. Following is a brief description of risks associated with APIs exposed by NFs. - -NOTE that tags like “API1:2023” are used from [i.5] for easy reference and can be used to find more details. - -- API1:2023 - Broken Object Level Authorization: Attackers can exploit API endpoints that are vulnerable to broken object-level authorization by manipulating the ID of an object that is sent within the request. Object IDs can be anything from sequential integers, UUIDs, or generic strings. -- API2:2023 – Broken Authentication: The authentication mechanism is an easy target for attackers since it's exposed to everyone. Authentication endpoints and flows are assets that need to be protected. -- API3:2023 - Broken Object Property Level Authorization: If APIs expose endpoints which return all object's properties, especially for REST APIs, these properties can be misused to break the object property level authorization. When allowing a user to access an object using an API endpoint, it is important to validate that the user has access to the specific object properties they are trying to access. -- API4:2023 – Unrestricted Resource Consumption: Multiple concurrent requests can be performed from a single local computer or by using cloud computing resources. Most of the automated tools available are designed to cause DoS via high loads of traffic, impacting APIs' service rate. -- API5:2023 - Broken Function Level Authorization: The best way to find broken function level authorization issues is to perform a deep analysis of the authorization mechanism while keeping in mind the user hierarchy, different roles or groups in the application. Exploitation requires the attacker to send legitimate API calls to an API endpoint that they should not have access to. -- API6:2023 – Unrestricted Access to Sensitive Business Flows: When creating an API Endpoint, it is important to understand which business flow it exposes. Some business flows are more sensitive than others, in the sense that excessive access to them may harm the business. For example, in wireless telecom networks, charging (or billing) related business flows can be - -considered more sensitive for business. Exploitation usually involves understanding the business model backed by the API, finding sensitive business flows, and automating access to these flows, causing harm to the business. - -- API7:2023 - Server Side Request Forgery: Server-Side Request Forgery (SSRF) flaws can occur when an API is fetching a remote resource without validating the user-supplied URI. In general, basic SSRF (when the response is returned to the attacker), is easier to exploit than Blind SSRF in which the attacker has no feedback on whether or not the attack was successful. -- API8:2023 – Security Misconfiguration: APIs and the systems supporting them typically contain complex configurations, meant to make the APIs more customizable. Security misconfigurations not only expose sensitive API consumer data, but also system details that can lead to full server compromise. -- API9:2023 - Improper Inventory Management: Threat agents can get unauthorized access through old API versions or endpoints left running unpatched and using weaker security requirements. Attackers can gain access to sensitive data, or even take over the server. Sometimes different API versions/deployments are connected to the same database with real data. -- API10:2023 - Unsafe Consumption of APIs: Developers tend to trust data received from third-party APIs more than user input. This is especially true for APIs offered by well-known companies. Because of that, developers tend to adopt weaker security standards, for instance, in regards to input validation and sanitization. Successful exploitation may lead to sensitive information exposure to unauthorized actors, many kinds of injections, or denial of service. -- Reverse engineering attacks using APIs: Attackers can attempt to call APIs in a reverse order than the good scenario. If the APIs are not designed to handle such error scenarios, it is likely that sensitive data is revealed in error responses. It is important to detect attackers attempting such attacks. -- API Spoofing: In this kind of attacks, attackers attempt to portray themselves as a trusted API consumer in order to pivot to additional API consumers, allowing them free access to data and the ability to deal more damage without being readily discovered. These attacks often use data discovered through phishing or other such credential leaks in order to prevent other alarms, such as those found in reverse engineering, from going off. -- Man-in-the-middle attacks: In this kind of attacks, attackers act as if they are some trusted link in the API chain, intercepting data either for morphing or offloading. -- Replay attacks: In such attacks, attacker is rewinding time by replaying some data exchanged with APIs and forcing the server to divulge data as if the same interaction is occurring once more. - -**Figure 6.14-1 - High level block diagram** - -![High level block diagram of O-RAN System architecture showing API interactions.](838c31609fac483fa2c01c7896a2fd6d_img.jpg) - -The diagram illustrates the high-level block architecture of an O-RAN System. A dashed box labeled 'O-RAN System' contains three main components: 'O-RAN internal API Consumer (Other O-RAN NF)', 'Internal API security data Consumer', and 'O-RAN NF - API Provider'. The 'O-RAN NF - API Provider' is connected to an 'External API Consumer' outside the system. The 'O-RAN internal API Consumer' and the 'Internal API security data Consumer' both have bidirectional connections to the 'O-RAN NF - API Provider'. The 'Internal API security data Consumer' also has a bidirectional connection to an 'SMO' (Service Management and Orchestration) block. The 'SMO' is connected to the 'O-RAN NF - API Provider' and has a bidirectional connection to the 'O-RAN internal API Consumer'. Two 'API Security Data collection Policy' blocks are shown, one connected to the 'O-RAN internal API Consumer' and the other to the 'Internal API security data Consumer', both pointing towards the 'SMO'. Finally, an 'External API security data consumer' is shown outside the system, receiving data from both the 'O-RAN internal API Consumer' and the 'Internal API security data Consumer'. - -High level block diagram of O-RAN System architecture showing API interactions. - -Figure 6.14-1 shows a high level block diagram indicating: - -- An O-RAN NF which is the API provider. -- An external API consumer. This can be any entity or NF which is not managed by O-RAN, for e.g., UE applications using CAPIF - -- An internal API consumer. This can be any NF which is managed by O-RAN. -- SMO can configure the API security data collection policies on the internal (O-RAN managed) NFs. These policies can include, for example: - - What data can be collected, and for which API security risks. - - What data can be exposed to internal API security data consumer. - - What data can be exposed to external API security data consumer. - - How frequently such data can be collected and reported. - - Any API security risk specific configuration to include/exclude additional information in the data to be exposed. -- An internal API security data consumer. - - Depending on the policies, this internal API security data consumer can receive API security data from the API provider AND/OR API consumer. This can be a function implemented in RIC to analyse the security data collected from various NFs (API providers and/or API consumers). -- An external API security data consumer. - - Depending on the policies, an external API security data consumer can receive API security data from the API provider AND/OR API consumer. - -### 6.14.2 Solution details - -**Security Logs:** The logs can provide information about the kind of API security risk identified using keywords which can enable faster and automated analysis. Below Table 6.14-1 describes the data which can be exposed to detect the security risks and attacks described above. NOTE that these can be more details included in different implementations. A unique Name/ID is suggested here to make the security data more structured and good for automated security analysis implementations. However, this solution does not propose to mandate a specific name of the unique ID. Implementations can have different names/formats of such unique IDs from what is proposed below. - -**Table 6.14-1 - Security data to be collected for different API security risks.** - -| Unique Name / ID | Example of possible contents in security logs | Mapping to attacks/security risks | -|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| -| API_AUTHORIZATION_FAILURE | Source NF ID, Destination NF ID, targeted object, authorization failure reason | Various authorization failure risks/attacks, Unrestricted Access to Sensitive Business Flows, etc. | -| API_AUTHENTICATION_FAILURE | API consumer ID, Time of last successful authentication, time when API consumer ID was locked | Various authentication failure risks/attacks | -| API_RESOURCE_EXHAUSTION | Affected NF ID, number of instances of this NF ID, peak CPU usage, average CPU usage, peak number of instances, average number of instances | Unrestricted resource consumption[i.5], (D)DoS attacks | -| SSRF_ATTEMPT | When SSRF attempt is detected, there can be some additional information logged, for example: 3rd party URI, data fetched from 3rd party, NF ID, etc. | Server Side Request Forgery | -| API_LATENCY_INFO | Latency related data like time taken to respond to some APIs if threshold is crossed, or time to receive a response is unusually high, etc. | Man-in-the-middle attacks, Reconnaissance | -| AUTH_TOKEN_USAGE_INFO | Token reuse, expired token usage, repeated message numbers, source NF IDs for such attempts. | Replay attacks | - -**Security Alarms:** Relevant threshold mentioned in below examples can be configured by the operators. Following can be examples of security alarms which can be raised for API related security risks: - -- Multiple simultaneous API access requests detected above threshold. - - Such alarm can help indicate a possible API4:2023 Unrestricted Resource Consumption [2] which can lead to DoS attacks. -- Detected usage of known vulnerability exploit. - - Such alarm can help indicate a possible risk like API8:2023 Security Misconfiguration -- Number of invalid tokens used for authentication exceeded threshold. - - Such alarms can help detect a potential brute-force attack - -**Security counters and KPIs (security metrics):** Some examples are shown in below Table 6.14-2. NOTE: These are just examples and optional for implementations. - -**Table 6.14-2 - Counters and KPIs for API security risks** - -| Security Metric Name | Description | Attack | -|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------| -| NUM_API_INVOCATIONS | Total number of API invocations in the periodic collection interval. This can be useful for deriving some security KPIs and events related to number of API invocations. | DoS attack, API4:2023 - Unrestricted Resource Consumption[i.5] | -| OUT_OF_SEQUENCE_API | Number of times out-of-sequence API is invoked in the collection interval | Reverse Engineering | -| UNAUTH_API_CONSUMER | Number of times an un-authorized consumer invoked an API | API Spoofing | -| SESSION_TOKEN_REUSE | Number of times session tokens are reused | Session Replay | -| AVG_API_LATENCY | This is measured by a NF invoking APIs towards other NFs. The average time taken for a NF to respond for certain API invocation is recorded here. Anomalies detected in this may indicate Man-in-the-middle attacks. In advanced security solutions, models can be trained for normal average API latencies and sequence of APIs.
Note:
API's supporting queries with long set of parameters may create false positives as the response time may exceed the threshold depending on the processing time of API by the API server. Also, network latencies during API transactions may make the latency KPI cross the threshold. | Man-in-the-middle | - -NOTE that the counters themselves are usually not sufficient to conclude that there is an attack. For example, AVG\_API\_LATENCY can indicate delays in interactions between NFs but it need not always indicate an attack. There may be intermittent performance issues which might lead to unusual delays and increased latency measurements. In some implementations, if the AVG\_API\_LATENCY measurements cross a configured threshold, it may lead to an alarm or a more detailed log/notification. However, more detailed analysis with correlation of events and statistical analysis of counters and KPIs would be needed to conclude whether or not it is an attack. Logging relevant API use timestamps may also help in some cases to troubleshoot better. - -### 6.14.3 Evaluation - -- This solution proposal has following potential new requirements for continuous security monitoring. -- New security data definitions (in the form of logs or alarms or counters or KPIs) can be standardized similar to examples as shown in Table 6.14-1 and Table 6.14-2. - -- NOTE that these tables are only providing some examples and O-RAN relevant API security risks can be considered for coming up with security data recommendations. Not all OWASP top 10 API security risks may be relevant for O-RAN. -- Have SMO configure policies on O-RAN NFs for API security data collection and exposure. These dynamic policies can enable continuous security monitoring of API security risks. -- According to the policies configured by SMO, NFs can collect API security data related to internal and external API consumers. -- According to the policies configured by SMO, NFs can expose API security data to internal and external API security data consumers. - -## 6.15 Solution #14: Data required to detect compromised xApps - -### 6.15.1 Introduction - -xApps operating within the Near-RT RIC are susceptible to compromise due to various vulnerabilities, as outlined in Key Issue #5. Undetected compromised xApps pose significant security risks, which can range from degrading the performance of the RAN to altering critical RAN configuration data [i.34]. The potential consequences of such compromises are described in lause 5.6.2 and in technique FGT5034 of the MITRE FiGHT framework [i.34], highlighting the broader impact of xApp vulnerabilities on system integrity and security. To mitigate these risks, continuous security monitoring of xApps, the Near-RT RIC platform, E2 nodes, and associated APIs is essential. - -### 6.15.2 Solution details - -To address the key issue #5 of data required to detect compromised xApps, an approach involving four steps was followed. The first step involves identifying the threats, which is comprehensively detailed in Clause 5.6. - -The second step focuses on mapping the threats to components that would be potentially affected by the compromised xApp(s). This step is critical for understanding the full scope of the xApp's interactions, influence, or possible attack. By understanding this context, we can determine where data should be collected and what types of monitoring are necessary. Compromised xApps should be monitored for unexpected behavior, API calls frequency, API calls endpoints, and abnormal or undefined parameters in API calls. Moreover, other components in the system may be affected by a compromised instance of an xApp. Table 6.15-1 provides a detailed mapping of the potentially affected components alongside the specific aspects that should be monitored. - -**Table 6.15-1 - Mapping of Potentially Affected Components and Key Aspects for Monitoring in Response to Compromised xApps** - -| Potentially Affected Components from a Compromised instance of xApp | Aspects for Monitoring | -|---------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Near-RT RIC platform | Lateral movement behavior.
Cross-app communication logs (unexpected or abnormal communication)
Messaging infrastructure (unexpected burst).
xApp crash/restart pattern.
Unusual changes triggered by xApp. | -| E2 nodes (O-DU, O-CU-CP and O-CU-UP) | Type/frequency of E2 commands from xApp.
Changes in RAN behavior triggered by xApp. | - -The third step is to identify the data to be monitored based on the information from the first and second steps. Five distinct categories of data have been identified for monitoring, each serving a critical purpose, as outlined below. - -- Data to be monitored for xApp exploitation attempts. See Table 6.15-2. -- Data to be monitored for xApp behavioural drifts. See Table 6.15-3. -- Data to be monitored for other components (Near-RT RIC platform and E2 nodes) behavioral drifts. See Table 6.15-4. -- Data to be monitored for Inter-xApp and RIC Communication. See Table 6.15-5. - -- Data to be monitored for Deployment and File Integrity information. See Table 6.15-6. - -These categories ensure comprehensive coverage of potential vulnerabilities and system behaviors to effectively detect compromised xApps. - -In Table 6.15-2, Table 6.15-3, Table 6.15-4, Table 6.15-5 and Table 6.15-6, the first, second, and third columns consequently provide detailed information about the data types that need to be monitored, examples of relevant events or items of interest, and the corresponding category of data based on the specific detection purpose it serves. This structured approach facilitates targeted monitoring and consequently enhances the overall security framework. - -The final step involves mapping the data identified in the previous step to their respective data sources. The fourth column of Table 6.15-2, Table 6.15-3, Table 6.15-4, Table 6.15-5 and Table 6.15-6 provides a detailed description of example data sources associated with each data type, the fifth column of the same tables highlights the specific elements or anomalies that need to be detected within the corresponding data sources. - -**Table 6.15-2 - Data to monitor for xApp exploitation attempts** - -| Data Type | Example of events or item of interest | Purpose | Example Data Source | Detects | -|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| File | Check distributed binaries for invalid signatures. | Detect exploitation attempts utilizing Supply Chain Compromise: Compromise Software Supply Chain FiGHT Technique [i.35], | File: File modification [i.35] | Use verification of distributed binaries through hash checking or other integrity checking mechanisms. Scan downloads for invalid signatures and attempt to test software and updates prior to deployment while taking note of potential suspicious activity [i.35]. | -| User Account authentication activity | Abnormal or malicious behaviour, such as accessing information outside of the normal function of the account or account usage at atypical hours. Repeated attempts | Detect exploitation attempts utilizing Valid Accounts: Cloud Accounts FiGHT Technique [i.36] | User Account [i.36] | Monitors user account authentication activities (attempts, successes, failures) to detect abnormal or malicious behavior, such as accessing information outside of the normal function of the account or account usage at atypical hours. [i.36]. | -| Account behaviour | Suspicious account behavior | | Logon Session [i.36] | Monitor for suspicious account behavior across cloud services that share account. Logon session logs and meta data helps determine if the session was an authorized activity [i.36]. | -| Command | Audit command logs. | Detect exploitation attempts utilizing Lateral Movement: Remote Services [i.37] | Command [i.37] | Audit command logs [i.37] | -| Logon Session | Blocked/denied activity | | Logon Session [i.37] | Monitor traffic patterns and session sources along with blocked/denied activity. [i.37] | -| Network traffic | Expected and unexpected attempted and established connections | | Network traffic [i.37] | Monitor network traffic for expected and unexpected attempted and established connections [i.37] | - -**Table 6.15-3 - Data to monitor for xApp behavioral drifts** - -| Data Type | Example of events or item of interest | Purpose | Example Data Source | Detects | -|---------------------------|---------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Resource utilization data | Unusual Function calls or above average resource utilization. | Detect xApp behavioural drift:
Detect CPU/mem spikes. | Host status [i.38] | Monitor systems performance and alert on quota exceptions on hosts, applications and networks [i.38]. | -| | | | SIEM [i.38] | Auditing logs for security, authentication and authorization activity, host access, hosts, virtualization orchestrator and managers can reveal behavioral anomalies [i.38]. | -| | | | Audit policy violation [i.38] | Automated user and resource policy compliance checks and instrumentation to alert on violation attempts [i.38]. | -| Internal xApp metrics | Unexpected behavior | Detect xApp behavioural drift:
Identify xApp unexpected behavior | Web Credential Usage [i.34] | Monitor access token usage by xApps. | -| | | | O-Cloud Storage Access [i.34] | Perform real-time audits and post-processing of logs to detect xApp access. | -| | | | xApp logs [i.34] | Monitor logs for authentication/authorization of xApps to Near-RT RIC and E2 nodes, logs for each transaction done by xApps to E2 nodes. Audit logs and telemetry data for unauthorized activities. | -| | | | Certificate [i.34] | Verify and refresh frequently digital signatures used for authenticating xApps by Near-RT RIC. | -| | | | E2 Messages Execution | Monitor E2 messages execution to detect if any xApps are going beyond its permitted functions. For example, if an xApp is supposed to do analytics, it is also doing RAN optimization and control. | -| Host data | Escape to host | Detect xApp behavioural drift:
Escape to host attempts to perform Lateral movement or privilege escalation | Application Log [i.41] | Audit application logs, Configuration management databases (CMDB) and other asset management systems may help with the detection of computer systems or network devices that should not exist on a network. | -| | | | Process [i.40] [i.41] | Monitor process activity on node, hosts and VNFs. | -| | | | Container [i.40] [i.41] | Monitor container creation, container start events | -| | | | Volume [i.40] [i.41] | Monitor volume or storage modifications, attachment or reading actions. | -| xApp Output | xApp outputs deviate from expected profiles | Detect xApp behavioural drift:
Identify misleading results | Process: OS API Execution [i.39] | Monitor for API calls associated with altering data. Remote access tools with built-in features may interact directly with the OS API to gather information. | - -**Table 6.15-4 - Data to monitor for other components (Near-RT RIC platform and E2 nodes) behavioral drifts.** - -| Data Type | Example of events or item of interest | Purpose | Example Data Source | Detects | -|-------------------------|----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Host data | Abnormal events traced to xApp control | Detect other components (Near-RT RIC and E2 nodes) behavioural drift:
Detect changes in RAN behavior triggered by xApp. | Host Status [i.34] | Monitor all xApps onboarding processes. Use host scanning tools to detect malware insertions. | -| E2 node behaviors' data | | | Certificate [i.34] | Verify and refresh frequently digital signatures used for authenticating xApps by Near-RT RIC and E2 nodes. | -| | | | Cloud Storage Access [i.34] | Perform real-time audits and post-processing of logs. Detect which parts of the RAN are accessed by each xApp e.g. O-DU, O-CU-CP, O-CU-UP etc. | -| | | | Application logs [i.34] | Monitor logs for authentication/authorization of xApps to Near-RT RIC and E2 nodes.
Monitor logs for each transaction done by xApps to E2 nodes.
Audit logs and telemetry data for unauthorized activities.
Monitor application logs in Near-RT RIC for all API accesses by xApps. | -| RAN performance data | Degraded KPIs linked to xApp action | Detect other components (Near-RT RIC and E2 nodes) behavioural drift:
Detect changes in RAN behavior triggered by xApp. | Host status [i.38] | Monitor systems performance and alert on quota exceptions on hosts, applications and networks [i.38]. | -| | | | SIEM [i.38] | Auditing logs for security, authentication and authorization activity, host access, hosts, virtualization orchestrator and managers can reveal behavioral anomalies [i.38]. | -| | | | Audit policy violation [i.38] | Automated user and resource policy compliance checks and instrumentation to alert on violation attempts [i.38]. | - -**Table 6.15-5 - Data to monitor for Inter-xApp and RIC Communication.** - -| Data Type | Example of events or item of interest | Purpose | Example Data Source | Detects | -|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------|------------------------------------------------------------------------------------------------| -| Commands (API calls) sent to E2 nodes | Type/frequency of E2 commands sent from xApp. | Detect unusual xApp and RIC communication: Unusual commands issued to RAN. | xApp Logs | Monitor for unexpected API calls, unauthorized requests, failed authentications. | -| Messaging infrastructure logs | Message volume/type per xApp | Detect unusual xApp and RIC communication: Detect unusual messages or denial-of-service attempts | Host Status [i.38] | Monitor systems performance and alert on quota exceptions on hosts, applications and networks. | -| API usage |
  • Request logs for:
  • Unusual or unauthorized API access.
  • API call frequency and targets.
  • Message volumes that indicate abuse or flooding
| Detect unusual xApp and RIC communication: Identify misuse of service APIs (Detect unusual calls or denial-of-service attempts) | See Solution #2 Table 6.2-6 of this document | See Solution #2 Table 6.2-6 of this document | - -**Table 6.15-6 - Data to monitor for deployment and file integrity information** - -| Data Type | Example of events or item of interest | Purpose | Example Data Source | Detects | -|-----------------|-----------------------------------------------|-------------------------------------------------------------------------------------------------------|---------------------------|-----------------------------------------------------------------------------------------------| -| xApp image hash | Mismatch | Detect deployment and file integrity information: unauthorized or tampered app versions | Image verification [i.37] | Verify xApp image hash | -| Deployment logs | Source of deployed xApps. Configuration data. | Detect deployment and file integrity information: Validate source and authorization of deployed xApps | Host Status [i.37] | Monitor and audit onboarding and subscriptions of all xApps, e.g. through configuration logs. | - -### 6.15.3 Evaluation - -This solution addresses key issue #5 “Data required to detect compromised xApps”. Monitoring the categories of data outlined in this solution may ensure comprehensive coverage of potential vulnerabilities and system behaviors to effectively detect compromised xApps. - -## 6.16 Solution #15: Collection of Data to Detect Compromised O-RU, O-CU, and O-DU - -### 6.16.1 Introduction - -Some parts of O-RAN are available through open-source software, potentially allowing for the manipulation of O-RU, O-DU, and O-CU software and subsequent compromised behavior of O-RUs, O-DUs, and O-CUs. If relevant data is not exposed to detect compromised O-RUs, O-CUs, and O-DUs, the compromise of these architecture elements may not be detected. Malicious actors may be able to compromise confidentiality, integrity and availability of the base station without being detected. - -As described in Key Issue #X, O-RAN architecture elements should be able to expose necessary data which can be used to analyse and detect compromised O-RUs, O-CUs, and O-DUs. This solution proposes a method for the collection of security related data for the detection of compromised O-RUs, O-CUs, and O-DUs. - -### 6.16.2 Solution details - -To address the Key Issue of Compromised O-RU, O-CU, and O-DU, the following requirements are proposed: - -In order to detect a compromised O-RU, O-CU, and/or O-DU, security related data should be collected as described in Table 6.16-1 and Table 6.16-2 below: - -- **Compromised O-RU:** Anomalies detected in eCPRI interface related metrics (data rate, latency, and bit error rate) correlated with temporary interruption in eCPRI connection [i.41], -- **Compromised O-CU:** PDCP layer Integrity verification success/failure counters, RRC Protocol related failure counts/logs -- **Compromised O-DU:** Anomalies detected in eCPRI interface related metrics (data rate, latency, and bit error rate) correlated with temporary interruption in eCPRI connection [i.41x], H-ARQ statistics correlated with channel measurements and channel quality data, CRC error counts at High PHY layer, MAC layer scheduling errors , authentication errors when verifying the authenticity of the certificate [i.12] - -NOTE 1: PDCP, RRC, and H-ARQ related statistics are out of scope of O-RAN and should be implemented in 3GPP. - -NOTE 2: MAC CE vulnerability [i.41x] can be exploited by a compromised O-DU. - -- **Logging of AI/ML data:** Implement logging of security related metrics and data to log anomalies and compromised components such as: - -**Table 6.16-1 - Data for Security Events (Alarms/Logs)** - -| Category | Data | Example | -|----------|------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| -| Alarm | Alarm information
Architecture element ID
Probable cause (anomaly in eCPRI) | Compromised_O-RU-Detected
Compromised_O-DU-Detected | -| Logs | Logs related to eCPRI anomalies
Time
Architecture element ID
Metrics (data rate, latency, and bit error rate) | Compromised_O-RU-Detected | -| Logs | Logs events regarding Authentication
Failures on IEEE 802.1X [i.42] | Compromised_O-RU-Detected
Compromised_O-DU-Detected | -| Logs | Logs related to MAC Security | Compromised_O-RU-Detected
Compromised_O-DU-Detected | - -**Table 6.16-2 - Data for Configuration** - -| Configurations for anomaly detection | Examples | -|----------------------------------------------------------------|------------------------------------------------------------------------------| -| Condition that raises an alarm
Compromised_Element_Detected | Alarm is active if detection technique detects an anomaly on eCPRI interface | - -### 6.16.3 Evaluation - -This solution addresses Key Issue #23 – “Compromised O-RU, O-CU, and O-DU” by proposing techniques to collect security related data to enable the detection of a compromised O-RU, O-CU, and O-DU. - -# 7 Conclusions - -## 7.1 Key issue to solution mapping - -This document currently contains 18 key issues. The solutions are listed here for reference, followed by a mapping of the proposed solutions to the key issues in Table 7.1-1. - -- Solution #1: Data required for detecting DoS attacks due to flooding -- Solution #2: Data required to detect API security risks (DoS through resource consumption) -- Solution #3: Continuous security monitoring for adversarial attacks on AI/ML models -- Solution #4: Continuous security monitoring for AI/ML-related data integrity and confidentiality -- Solution #5: Continuous security monitoring for software delivery -- Solution #6: Continuous security monitoring for authentication attacks -- Solution #7: Continuous security monitoring for authorization attacks -- Solution #8: Continuous security monitoring for cloud attacks related to lateral movement -- Solution #10: Secure the transmission of security monitoring data -- Solution #11: Continuous security monitoring for open-source software delivery -- Solution #12 Continuous security monitoring to detect unauthorized external communication -- Solution #13: Data required to detect API security risks -- Solution #14: Data required to detect compromised xApps -- Solution #15: Collection of data to detect compromised O-RU, O-CU and O-DU - -**Table 7.1-1 - Mapping of key issues to Solutions** - -| Key issue | Sol # 1 | Soln #2 | Sol #3 | Sol #4 | Sol #5 | Sol #6 | Sol #7 | Sol #8 | Sol #10 | Sol #11 | Sol #12 | Sol #13 | Sol #14 | -|-----------|---------|---------|--------|--------|--------|--------|--------|--------|---------|---------|---------|---------|---------| -| KI 1 | X | | | | | | | | | | | | | -| KI 2 | | X | | | | | | | | | | X | | -| KI 3 | | | | | | | | X | | | | | | -| KI 4 | | | | | | X | | | | | | | | -| KI 5 | | | | | | | | | | | | | | -| KI 6 | | | | | | | X | | | | | | | -| KI 7 | | | | | | | | | | X | | | | -| KI 8 | | | | | | | | | | | | | | -| KI 9 | | | | | | | | | | | | | | -| KI 10 | | | | | | | | | | | | | | -| KI 11 | | | | | X | | | | | | | | | -| KI 12 | | | | | | | | | | | | | | -| KI 13 | | | X | | | | | | | | | | | -| KI 14 | | | | X | | | | | | | | | | -| KI 15 | | | X | | | | | | | | | | | - -| Key issue | Sol #1 | Sol #2 | Sol #3 | Sol #4 | Sol #5 | Sol #6 | Sol #7 | Sol #8 | Sol #10 | Sol #11 | Sol #12 | Sol #13 | Sol #14 | -|-----------|--------|--------|--------|--------|--------|--------|--------|--------|---------|---------|---------|---------|---------| -| KI 16 | | | X | | | | | | | | | | | -| KI 17 | | | | | | | | | X | | | | | -| KI 18 | | | | | | | | | | | | | | -| KI 19 | | | | | | | | | | | | | | -| KI 20 | | | | | | | | | | | | | | -| KI 21 | | | | | | | | | | | | | | -| KI 22 | | | | | | | | | | | X | | | -| KI 23 | | | | | | | | | | | | | X | - -## 7.2 Recommendations - -### 7.2.1 Conclusions - -The following is a list of next steps and recommendations coming from this work item which have been or will be addressed in future updates to this technical report and other O-RAN specifications. - -Key issues #13 and #15 – These key issues have been resolved with the definition of additional recommendations and requirements for continuous security monitoring for adversarial attacks on AI/ML models, based on Solution #3. CRs will be generated. - -*Status: not started* - -Key issue #2 – This key issue can be resolved with the definition of recommendations including requirements for continuous security monitoring for API attacks based on proposals in Solution #2. CRs with normative specifications will be generated. - -*Status: not started* - -Key issue #1 – This key issue can be resolved with the definition of requirements for continuous security monitoring for DDoS attacks based on proposals in Solution #1. CRs with normative specifications will be generated. - -*Status: not started* - -Key issue #3 – This key issue can be resolved with the definition of requirements for continuous security monitoring for cloud related attacks based on proposals in Solution #8. CRs with normative specifications will be generated. - -*Status: not started* - -Key issue #4 – This key issue can be resolved with the definition of requirements for continuous security monitoring for authentication related attacks based on proposals in Solution #6. Existing specifications will be analysed and CRs with normative requirements will be generated if required. - -*Status: not started* - -Key issue #6 – This key issue can be resolved with the definition of requirements for continuous security monitoring for authorization related attacks based on proposals in Solution #7. Existing specifications will be analysed and CRs with normative requirements will be generated if required. - -*Status: not started* - -Key issue #16 – This key issue can be resolved with the definition of requirements for continuous security monitoring for AI/ML model and data drift based on proposals in Solution #3. Existing specifications will be analysed and CRs with normative requirements will be generated if required. - -*Status: not started* - -Key issue #11 – This key issue can be resolved with the definition of requirements for continuous security monitoring for software delivery related attacks based on proposals in Solution #5. Existing specifications will be analysed and CRs with normative requirements will be generated if required. - -*Status: not started* - -Key issue #14 – This key issue can be resolved with the definition of requirements for continuous security monitoring for AI ML data integrity and confidentiality related attacks based on proposals in Solution #4. Existing specifications will be analysed and CRs with normative requirements will be generated if required. - -*Status: not started* - -### 7.2.2 Summary of recommended solutions - -The following Table 7.2-1 list the security related alarms for various threats and impacted assets - -**Table 7.2-1 - Security data related to alarms** - -| Alarm Definition (Name or ID) | Description (including fields which contain the fields which indicate the security related alarm details ) | Related Threats (key issues) which can be detected using this data | Reporting NFs / Impacted Assets | Related solutions | -|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|---------------------------------|-------------------| -| DoS_related_to_packet_flooding_alarm | Alarm information
Source IP
Destination IP
Probable cause (Denial of Service due to packet flooding) (an operational violation event as referred to in section 8.1.2.1 of [i.15]) | DoS due to Packet flooding | All O-RAN architecture elements | Solution #1 | -| Process_activity_alarm | Process Activity:
High CPU/memory-consuming processes or unexpected background tasks. | cloud attacks related to lateral movement | All O-RAN architecture elements | Solution #8 | -| Intrusion_Detection_Alarm | Intrusion Detection Alerts:
Suspicious patterns identified by IDS/IPS systems. | cloud attacks related to lateral movement | All O-RAN architecture elements | Solution #8 | -| Default_password_unchanged_Alarm | Alarms for default password unchanged | Authentication attacks | All O-RAN architecture elements | Solution #6 | -| Privilege_escalation_Alarm | Alarm related to privilege escalation | Authorization attacks | All O-RAN architecture elements | Solution #7 | - -The following Table 7.2-2 list the security related counters for various threats and impacted assets - -**Table 7.2-2 - Security data related to counters** - -| Counter Definition (Name or ID) | Description(with NF ID, Interface ID where applicable) | Related Threats D21(key issues) which can be detected using this data | Reporting NFs / Impacted Assets | Related solutions | -|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|----------------------------------------|--------------------------| -| Number of packets received | A counter related to DoS packet flooding attack detection using TCP/IP packets. Consider NF ID and Interface ID | DoS due to Packet flooding | All O-RAN architecture elements | Solution #1 | -| Origins for the largest number of packets. | Source IP addresses of the largest number of TCP/IP packets | DoS due to Packet flooding | All O-RAN architecture elements | Solution #1 | -| Access_Counter | Number of times a user has accessed a NFs and/or cloud resources. | cloud attacks related to lateral movement | All O-RAN architecture elements | Solution #8 | -| | Could be used for a access pattern | cloud attacks related to lateral movement | All O-RAN architecture elements | Solution #8 | -| Process_activity_counter | Process Activity: High CPU/memory-consuming processes or unexpected background tasks. | cloud attacks related to lateral movement | All O-RAN architecture elements | Solution #8 | -| User_session_counter | Counter related to number of sessions exceeded a configured threshold | Authentication attacks | All O-RAN architecture elements | Solution #6 | -| Authentication_failure_counter | Counter for number of unauthenticated attempts | Authentication attacks | All O-RAN architecture elements | Solution #6 | -| Password_failure_in_time_period_counter | Counter related number of failed password attempts in time period | Authentication attacks | All O-RAN architecture elements | Solution #6 | -| Permissions_administeredcounter | Counter related to number of permissions administered for a period of time | Authorization attacks | All O-RAN architecture elements | Solution #7 | -| Data breach detection_counter | Measure the number of potential data breaches (EXAMPLE: unauthorized access) detected through continuous monitoring | Unauthorized access or manipulation of AI/ML-related data | All O-RAN architecture elements | Solution #4 | -| Data manipulation or tampering detection_counter | measure the number of data manipulations(EXAMPLE: introduce bias) detected through continuous monitoring. | Unauthorized access or manipulation of AI/ML-related data | All O-RAN architecture elements | Solution #4 | - -The following Table 7.2-3 list the security related logs for various threats and impacted assets - -**Table 7.2-3 - Security data related to logs** - -| Log Definition (Name or ID) | Description | Related Threats (key issues) which can be detected using this data | Reporting NFs / Impacted Assets | Related solutions | -|----------------------------------------------------|----------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------|--------------------------------------------|--------------------------| -| Dos_Logs | Time
Unique ID
Source IP
Destination IP | DoS due to Packet flooding | All O-RAN architecture elements | Solution #1 | -| Access_logs | Access Patterns: Monitoring of user access to NFs and cloud resources. | cloud attacks related to lateral movement | All O-RAN architecture elements | Solution #8 | -| Anomalous behaviour_log | Anomalous Behaviour Detection: Abnormal system calls or API usage, , anomalies detected by AI/ML | cloud attacks related to lateral movement, adversarial attacks to AI/ML | All O-RAN architecture elements | Solution #8, Solution #3 | -| Firewall_logs | Firewall Logs: Denied connections and unusual access attempts. | cloud attacks related to lateral movement | All O-RAN architecture elements | Solution #8 | -| Security_logs | Audit Logs: User access and privilege escalation events, including SSH and API logins. | cloud attacks related to lateral movement | All O-RAN architecture elements | Solution #8 | -| Interface_logs | Interface Information: Interfaces exposed by the service (Nmap scan) | cloud attacks related to lateral movement | All O-RAN architecture elements | Solution #8 | -| Model and Data Drift Detection_logs | AI/ML Model and Data Drift Detection: Time Architecture element ID Metrics (accuracy, precision, recall) | Model and data drift | Non-RT RIC, Near-RT-RIC, SMO, rApps, xApps | Solution #3 | -| Successful_authentication_logs | Successful cases. Consider Time App ID Location | Authentication attacks | All O-RAN architecture elements | Solution #6 | -| Unsuccessful_authentication_logs | Unsuccessful cases Consider Time App ID Location | Authentication attacks | All O-RAN architecture elements | Solution #6 | -| Failure in multi authentication factor_log | Security logs related to failure in multi factor authentication | Authentication attacks | All O-RAN architecture elements | Solution #6 | -| Authentication_policy_not_updated_logs | Weak related or missing or not updated authentication related policies like password policy | Authentication attacks | All O-RAN architecture elements | Solution #6 | -| Private_key_access_logs | Security logs related to accessing of private keys | Authentication attacks | All O-RAN architecture elements | Solution #6 | -| Certificate_passphrase_attempted_logs | Security logs related to accessing of certificates with out proper passphrase | Authentication attacks | All O-RAN architecture elements | Solution #6 | -| Unauthorized access to O-RAN NF_logs | Security logs with authorization failures Consider Time, App ID, Location | Authorization attacks | All O-RAN architecture elements | Solution #7 | -| Manipulation of data_attempted_logs | Security logs with attempt to modify data without authorized access rights | Authorization attacks | All O-RAN architecture elements | Solution #7 | -| Misconfiguration_logs | Logs related to privilege escalation. Consider Time, App ID, Location | Authorization attacks | All O-RAN architecture elements | Solution #7 | -| Violation of the principle of least privilege_logs | Security logs indicating the excessive rights for long periods of time | Authorization attacks | All O-RAN architecture elements | Solution #7 | - -| | | | | | -|---------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------|---------------------------------|-------------| -| Software validation during onboarding_ logs | Log of functions that verify the digital signatures and integrity of software packages including AppPackID, SignatureValidationResult, IntegrityValidationResult | Compromised software delivery can lead to the introduction of malicious code | SMO | Solution #5 | -| Data Integrity Checks_ logs | data integrity to detect potential data manipulation or tampering. | AI/ML-related data integrity and confidentiality | All O-RAN architecture elements | Solution #4 | -| Intrusion Detection_ logs | AI/ML- related system parameters to detect potential security threats or breaches. | AI/ML-related data integrity and confidentiality | All O-RAN architecture elements | Solution #4 | - -# Annex: Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|-------------------------------------------------------------------------------------------------------------------------------------| -| 2024.09.05 | 00.03 | Skeleton TR approved | -| 2024.10.03 | 00.04 | Merged in approved CR NOK0183 and NOK 0184 | -| 2024.10.30 | 00.05 | Merged in approved CRs NOK0192, NOK0193, NOK0200, NOK0199 | -| 2024.12.12 | 00.06 | Merged in approved CRs MTR0123, NOK0205, NOK0211, MTR0125 | -| 2025.02.06 | 00.07 | Merged in approved CRs MTR0104, MTR0124, MTR0128, NOK0204, NOK0214, NOK0215, NOK0218, NOK0219, NOK0224, NOK0225, NOK0226, NOK0227 | -| 2025.02.26 | 00.08 | Merged in approved CRs NOK0229, NOK0230, NOK0247, NOK0250, NOK0248, NOK0249 | -| 2025.03.06 | 00.09 | Merged in approved CRs NOK0258, NOK0252, NOK0267 | -| 2025.04.17 | 1.00.01 | Merged in approved CRs NOK0261, NOK0262, NOK0272 | -| 2025.06.03 | 1.00.02 | Merged in approved CRs RMI-0040, CR0278, CR279 | -| 2025.07.10 | 1.00.03 | Merged in approved CRs NOK-CR0280, NOK-CR0281, NOK-CR0282, NOK-CR0293, NOK-CR0298, NOK-CR0300, NIST- RMI-CR0052, CR0017, RMI-CR0049 | -| 2025.08.21 | 1.00.04 | Merged in approved CRs MTR-0301, NOK-0289, NOK-0299, NOK-0294 | -| 2025.10.02 | 1.00.05 | Merged in approved CRs NOK-CR0330, NOK-CR0327, NOK-CR0312, NOK-CR0313, NOK-CR0309, NOK-CR0311, MTR-CR0164 | -| 2025.10.16 | 1.00.06 | Merged in approved CRs NOK-CR0331 | -| 2025.11.17 | 1.00.07 | Editorial changes incorporated as per review comments | -| 2025.11.23 | 2.00.01 | Editorial changes incorporated as per review comments | -| 2025.12.01 | 2.00.02 | Editorial changes incorporated as per review comments | \ No newline at end of file diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/08441fa90c5fd11994626f662ac13f19_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/08441fa90c5fd11994626f662ac13f19_img.jpg deleted file mode 100644 index d73eb6dd0b9d2d07f4c584fc410ae37120896f88..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/08441fa90c5fd11994626f662ac13f19_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:991133cc5f1375b3641bcc368baa759429da95d256e94fbcf98afb41a913f87b -size 50254 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/1baaba7a6e54e77197475726c871067d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 930b29c592e18e4ee9b7f13de4f79020ff712459..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5f8013eada922e4dd6d610cf1f66e7ef4cde52eba107e33f0825d24ae802b0e6 -size 4550 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/4e4be0bd8b235167902f2c03e41da651_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/4e4be0bd8b235167902f2c03e41da651_img.jpg deleted file mode 100644 index 7f00cd0d3ca901704ca230104b5bf3edb21df665..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/4e4be0bd8b235167902f2c03e41da651_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d1e21d7c3f921bca3b1fefa6d97f9ff9039b3fc42cca3393d265fe35f18a50fb -size 36455 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index b65c9819ba60bfe19f6cdb95d3075d756b2b6c71..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0cad14f9ac2225f628dcfe49bccbde098fb99facc8adc2cec5e351074d1e3eee -size 4528 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/5f2c99ae08864cf2d5c949947bac2b98_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/5f2c99ae08864cf2d5c949947bac2b98_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/5f2c99ae08864cf2d5c949947bac2b98_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index 0be4c8806d6d6e2d8dc0ad1d17842a2d8be958c2..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/6588b1c7f14069d96744b473ad663248_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5f272d387b1d9f9bc1c40499f75a467038c67bb1a5993ef2c655b283a8a775b6 -size 4501 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 1ae115f85c71c7c4dd5ac246f8d02e9dc29c8af6..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5775240b9ed1a2100a9c61aca08d03763ec191986acc2c52895232c0e85e48b -size 4429 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index ac3cfab543f601f0f5d5df0819baff17d274a951..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d57cf478d6a7b5f2ccc5b9b3097071939cf811679cce8997ebdcbc5222840d3b -size 4513 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/838c31609fac483fa2c01c7896a2fd6d_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/838c31609fac483fa2c01c7896a2fd6d_img.jpg deleted file mode 100644 index 1ca15c3fc96d698a65a7dc2bbaf8a71d9548cccf..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/838c31609fac483fa2c01c7896a2fd6d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:51b282036bc602ace44bc183f51607c264a636878a1cd577aa7eb92217b4086c -size 42685 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/854df8ad60507803253274673f9062cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 211b3e3c41561cecff2ae09d96a95a84628eec4d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4bc86e5c6afb3e8822db8737a4f9651627f6881da187c576f75bbb1c6fd828a8 -size 4492 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/9c1941fcc429d4fd6e7ad245285c5c33_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/9c1941fcc429d4fd6e7ad245285c5c33_img.jpg deleted file mode 100644 index 6b861af2dc4bb07110fee3587d95fa0a000f3af3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/9c1941fcc429d4fd6e7ad245285c5c33_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6537583f7b4f4f61d6b934d50b700359cee535de4b14963a8ef4c078c766baa9 -size 34118 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index be679815b77877c4e924b9486c09f9f724810c08..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6bba0c6f1cd8911751393c9b51b27412a8996f5483da564cb3c773116f81d8e2 -size 4529 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index b65c9819ba60bfe19f6cdb95d3075d756b2b6c71..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0cad14f9ac2225f628dcfe49bccbde098fb99facc8adc2cec5e351074d1e3eee -size 4528 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index be679815b77877c4e924b9486c09f9f724810c08..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6bba0c6f1cd8911751393c9b51b27412a8996f5483da564cb3c773116f81d8e2 -size 4529 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/ed48e24e36ea0501953177401c900f86_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/ed48e24e36ea0501953177401c900f86_img.jpg deleted file mode 100644 index 7a2f0611667c66cde2b0f6d3d255da2cb43c6ebc..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/ed48e24e36ea0501953177401c900f86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:38676165324b50c766df44df8bb3cb7e98b92b10d8bd557b1c3197bb59d41624 -size 84685 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/f74adaa1840504407cd4272995426f82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 8b5a6ca73c65302e520868a6697e06b55a09b50f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.CSM-Security-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:339b8383336413a7e45878d22f358ce8a240f6d043405f4239f07b6eb47944b0 -size 4545 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/doc.md b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/doc.md deleted file mode 100644 index cb0885cbe58b94e6004344865ae962888fe51d9b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/doc.md +++ /dev/null @@ -1,2434 +0,0 @@ - - -# **O-RAN Work Group 11 (Security Work Group)****Study on Certificate Management Framework** - -# Contents - -| | | | -|--------|---------------------------------------------------------------------------------------------------------------------------|----| -| 1 | Scope..... | 8 | -| 2 | References, Definitions of Terms and Abbreviations ..... | 9 | -| 2.1 | Normative references ..... | 9 | -| 2.2 | Informative References ..... | 9 | -| 2.3 | Terms..... | 11 | -| 2.4 | Abbreviations ..... | 12 | -| 3 | Architecture Requirements and Assumptions..... | 14 | -| 3.1 | Architecture Requirements..... | 14 | -| 3.2 | Architecture Assumptions..... | 14 | -| 3.2.1 | Use Case for Physical Network Functions ..... | 14 | -| 4 | Key Issues ..... | 16 | -| 4.1 | Key Issue #1: Considering RA and CA as separate logical entities..... | 16 | -| 4.1.1 | General Description..... | 16 | -| 4.1.2 | Security Threats..... | 16 | -| 4.2 | Key Issue #2: Usage of PSK/Refrum for Initial Certificate Enrolment of PNFs ..... | 16 | -| 4.2.1 | General Description..... | 16 | -| 4.2.2 | Security Threats..... | 17 | -| 4.3 | Key Issue #3: Usage of Vendor Certificates for Initial Certificate Enrolment of PNFs ..... | 17 | -| 4.3.1 | General Description..... | 17 | -| 4.3.2 | Security Threats..... | 17 | -| 4.4 | Key Issue #4: Void..... | 17 | -| 4.5 | Key Issue #5: Void..... | 17 | -| 4.6 | Key Issue #6: Initial Certificate Enrolment for new NFs..... | 17 | -| 4.6.1 | General Description..... | 17 | -| 4.6.2 | Security Threats..... | 17 | -| 4.7 | Key Issue #7: Void..... | 18 | -| 4.8 | Key Issue #8: Vendor Root CA Certificate Renewal..... | 18 | -| 4.8.1 | General Description..... | 18 | -| 4.8.2 | Security Threats..... | 18 | -| 4.9 | Key Issue #9: Void..... | 18 | -| 4.10 | Key Issue #10: Procedure for Certificate Updates when revoked certificates are detected by NFs ..... | 18 | -| 4.10.1 | General Description..... | 18 | -| 4.10.2 | Security Threats..... | 19 | -| 4.11 | Key Issue #11: Void..... | 19 | -| 4.12 | Key Issue #12: Certificate to name mapping ..... | 19 | -| 4.12.1 | General Description..... | 19 | -| 4.12.2 | Security Threats..... | 19 | -| 4.13 | Key Issue #13: System overload due to bulk certificate updates..... | 20 | -| 4.13.1 | General Description..... | 20 | -| 4.13.2 | Security Threats..... | 20 | -| 4.14 | Key Issue #14: Void..... | 21 | -| 4.15 | Key Issue #15: Void..... | 21 | -| 4.16 | Key Issue #16: Void..... | 21 | -| 4.17 | Key Issue #17: Void..... | 21 | -| 4.18 | Key Issue #18: Allow Flexibility in the Number of Operator Certificates Associated with each end entity / Interface ..... | 21 | -| 4.18.1 | General Description..... | 21 | -| 4.18.2 | Security Threats..... | 21 | -| 4.19 | Key Issue #19: Certificate Management in Distributed Cluster Processing ..... | 22 | -| 4.19.1 | General Description..... | 22 | -| 4.19.2 | Security Threats..... | 22 | -| 4.20 | Key Issue #20: Certificate Management and Secure Storage of Application Private Keys ..... | 23 | -| 4.20.1 | General Description..... | 23 | -| 4.20.2 | Security Threats..... | 23 | -| 4.21 | Key Issue #21: Coordinating Certificate Management with VNF/CNF Lifecycle Activities ..... | 23 | -| 4.21.1 | General Description..... | 23 | - -| | | | -|--------|----------------------------------------------------------------------------------------------------------|----| -| 4.21.2 | Security Threats..... | 24 | -| 4.22 | Key Issue #22: Supporting Public and Private Certificate Authorities (CA)..... | 24 | -| 4.22.1 | General Description..... | 24 | -| 4.22.2 | Security Threats..... | 24 | -| 4.23 | Key Issue #23: Distribution of Intermediate and Root Certificates ..... | 25 | -| 4.23.1 | General Description..... | 25 | -| 4.23.2 | Security Threats..... | 25 | -| 4.24 | Key Issue #24: CMPv2 Message Minimal Set and Robustness..... | 26 | -| 4.24.1 | General Description..... | 26 | -| 4.24.2 | Security Threats..... | 26 | -| 4.25 | Key Issue #25: RA and CA Capacity Estimation, Renewal Intervals and Credential Strength ..... | 26 | -| 4.25.1 | General Description..... | 26 | -| 4.25.2 | Security Threats..... | 26 | -| 4.26 | Key Issue #26: Namespace Conventions ..... | 27 | -| 4.26.1 | General Description..... | 27 | -| 4.26.2 | Security Threats..... | 27 | -| 4.27 | Key issue #27: Handling of certificate revocation in O-RAN ..... | 27 | -| 4.27.1 | General Description..... | 27 | -| 4.27.2 | Security Threats..... | 28 | -| 4.28 | Key issue #28: Risk of Service un-availability due to root CA Certificate updates for CNFs and VNFs..... | 28 | -| 4.28.1 | General Description..... | 28 | -| 4.28.2 | Security Threats..... | 29 | -| 4.29 | Key issue #29: Certificate requirements for O-Cloud control plane..... | 29 | -| 4.29.1 | General Description..... | 29 | -| 4.29.2 | Security Threats..... | 30 | -| 4.30 | Key issue #30: Certificate management for cloud deployment models..... | 30 | -| 4.30.1 | General Description..... | 30 | -| 4.30.2 | Security Threats..... | 30 | -| 4.31 | Key issue #31: Void..... | 30 | -| 4.32 | Key issue #32: Void..... | 31 | -| 4.33 | Key issue #33: Certificate Profiling in O-RAN ..... | 31 | -| 4.33.1 | General Description..... | 31 | -| 4.33.2 | Security Threats..... | 31 | -| 4.34 | Key issue #34: Void..... | 31 | -| 4.35 | Key issue #35: Void..... | 32 | -| 4.36 | Key issue #36: Certificate sharing or not-sharing in Apps/VNFs/CNFs ..... | 32 | -| 4.36.1 | General Description..... | 32 | -| 4.36.2 | Security Threats..... | 32 | -| 4.37 | Key issue #37: Lightweight solution..... | 33 | -| 4.37.1 | General Description..... | 33 | -| 4.37.2 | Security Threats..... | 33 | -| 4.38 | Key issue #38: Interoperability ..... | 33 | -| 4.38.1 | General Description..... | 33 | -| 4.38.2 | Security Threats..... | 33 | -| 4.39 | Key issue #39: Crypto agility..... | 34 | -| 4.39.1 | General Description..... | 34 | -| 4.39.2 | Security Threats..... | 34 | -| 4.40 | Key issue #40: Void..... | 34 | -| 4.41 | Key Issue #41: CMPv2 ..... | 34 | -| 4.41.1 | General Description..... | 34 | -| 4.41.2 | Security Threats..... | 34 | -| 4.42 | Key Issue #42: Certificate management for Shared O-RU ..... | 34 | -| 4.42.1 | General Description..... | 34 | -| 4.42.2 | Security Threats..... | 35 | -| 4.43 | Key Issue #43: NF with an expired certificate ..... | 35 | -| 4.43.1 | General Description..... | 35 | -| 4.43.2 | Security Threats..... | 35 | -| 4.44 | Key Issue #44: Shared O-RU Trust Anchors..... | 35 | -| 4.44.1 | General Description..... | 35 | -| 4.44.2 | Security Threats..... | 35 | - -| | | | -|--------|---------------------------------------------------------------------------------------------------------|----| -| 5 | Solutions..... | 37 | -| 5.1 | Solution #1: Automation of PSK/Refnum based Certificate Enrolment..... | 37 | -| 5.1.1 | Description ..... | 37 | -| 5.1.2 | Impacts on Existing Interfaces and Functionality ..... | 37 | -| 5.1.3 | Solution Evaluation ..... | 37 | -| 5.1.4 | Potential Security Requirements ..... | 37 | -| 5.2 | Solution #2: Study the use of BRSKI..... | 37 | -| 5.2.1 | Description ..... | 37 | -| 5.2.2 | Impacts on Existing Interfaces and Functionality ..... | 38 | -| 5.2.3 | Solution Evaluation ..... | 38 | -| 5.2.4 | Potential Security Requirements ..... | 39 | -| 5.3 | Solution #3: Study the use of EST ..... | 39 | -| 5.3.1 | Description ..... | 39 | -| 5.3.2 | Impacts on Existing Interfaces and Functionality ..... | 41 | -| 5.3.3 | Solution Evaluation ..... | 41 | -| 5.3.4 | Potential Security Requirements ..... | 41 | -| 5.4 | Solution #4: Study the use of ACME..... | 41 | -| 5.4.1 | Description ..... | 41 | -| 5.4.2 | Impacts on Existing Interfaces and Functionality ..... | 43 | -| 5.4.3 | Solution Evaluation ..... | 43 | -| 5.5 | Solution #5: Initial Certificate Enrolment of PNFs using vendor certificates ..... | 44 | -| 5.5.1 | Description ..... | 44 | -| 5.5.2 | Impacts on Existing Interfaces and Functionality ..... | 44 | -| 5.5.3 | Solution Evaluation ..... | 45 | -| 5.5.4 | Potential Security Requirements ..... | 45 | -| 5.6 | Solution #6: Certificate management and secure storage of Application private keys within O-Cloud ..... | 45 | -| 5.6.1 | Description ..... | 45 | -| 5.6.2 | Generation of key pair and modes of operation ..... | 46 | -| 5.6.3 | Secure key and file storage..... | 49 | -| 5.6.4 | Impacts on Existing Interfaces and Functionality ..... | 52 | -| 5.6.5 | Solution Evaluation ..... | 52 | -| 5.6.6 | Potential Security Requirements ..... | 52 | -| 5.7 | Solution #7: CMPv2..... | 53 | -| 5.7.1 | Description ..... | 53 | -| 5.7.2 | Impacts on Existing Interfaces and Functionality ..... | 53 | -| 5.7.3 | Solution Evaluation ..... | 53 | -| 5.7.4 | Potential Security Requirements ..... | 53 | -| 5.8 | Solution #8: Vendor Root CA Certificate Renewal notification..... | 54 | -| 5.8.1 | Description ..... | 54 | -| 5.8.2 | Impacts on Existing Interfaces and Functionality ..... | 54 | -| 5.8.3 | Solution Evaluation ..... | 54 | -| 5.8.4 | Potential Security Requirements ..... | 55 | -| 5.9 | Solution #9: Mitigating the risk of system overload due to bulk certificate updates..... | 55 | -| 5.9.1 | Description ..... | 55 | -| 5.9.2 | Impacts on Existing Interfaces and Functionality ..... | 56 | -| 5.9.3 | Solution Evaluation ..... | 56 | -| 5.9.4 | Potential Security Requirements ..... | 56 | -| 5.10 | Solution #10: Usage of PSK/Refnum for Initial Certificate Enrolment for PNFs ..... | 56 | -| 5.10.1 | Description ..... | 56 | -| 5.10.2 | Impacts on Existing Interfaces and Functionality ..... | 57 | -| 5.10.3 | Solution Evaluation ..... | 57 | -| 5.10.4 | Potential Security Requirements ..... | 57 | -| 5.11 | Solution #11: Certificate renewal procedure..... | 57 | -| 5.11.1 | Description ..... | 57 | -| 5.11.2 | Impacts on Existing Interfaces and Functionality ..... | 58 | -| 5.11.3 | Solution Evaluation ..... | 58 | -| 5.11.4 | Potential Security Requirements ..... | 59 | -| 5.12 | Solution #12: Certificate Profile for O-RAN TLS Entity ..... | 59 | -| 5.12.1 | Description ..... | 59 | -| 5.12.2 | Impacts on Existing Interfaces and Functionality ..... | 60 | -| 5.12.3 | Solution Evaluation ..... | 60 | - -5.12.4 Potential Security Requirements ..... 62 - -5.13 Solution #13: Identifying RA and CA as separate logical entities with flexible deployment options..... 62 - -5.13.1 General Description..... 62 - -5.13.2 Impacts on Existing Interfaces and Functionality ..... 63 - -5.13.3 Solution Evaluation ..... 63 - -5.13.4 Potential Security Requirements ..... 63 - -5.14 Solution #14: Securing Root CA Private Key..... 64 - -5.14.1 General Description..... 64 - -5.14.2 Impacts on Existing Interfaces and Functionality ..... 64 - -5.14.3 Solution Evaluation ..... 64 - -5.14.4 Potential Security Requirements ..... 64 - -5.15 Solution #15: Certificate enrolment for new NF Deployment using CMPv2..... 65 - -5.15.1 General Description..... 65 - -5.15.2 Impacts on Existing Interfaces and Functionality ..... 67 - -5.15.3 Solution Evaluation ..... 67 - -5.15.4 Potential Security Requirements ..... 67 - -5.16 Solution #16: Shared O-RU Trust Anchors Management ..... 67 - -5.16.1 General Description..... 67 - -5.16.2 Impacts on Existing Interfaces and Functionality ..... 68 - -5.16.3 Solution Evaluation ..... 68 - -5.16.4 Potential Security Requirements ..... 68 - -6 Conclusions..... 69 - -6.1 Key Issue #41: CMPv2 ..... 69 - -6.2 ACME as Optional Certificate Management Protocol..... 69 - -6.3 Usage of PSK/Refnum for initial certificate enrolmentenrolment for PNFs, CNFs and VNFs..... 69 - -6.4 Vendor root CA certificate renewal notification..... 69 - -6.5 Initial certificate enrolment for PNFs using vendor certificates ..... 70 - -6.6 Certificate renewal procedure ..... 70 - -6.7 RA and CA as separate logical entities ..... 70 - -6.8 EST as Optional Certificate Management Protocol ..... 70 - -6.9 Use of BRSKI in O-RAN..... 70 - -6.10 Mitigating the risk of system overload due to bulk certificate update ..... 70 - -6.11 Key Issue #20: Certificate Management and Secure Storage of Private Keys ..... 71 - -6.11.1 Evaluation and Assessment for local security module managed by SSRM within the O-Cloud..... 71 - -6.11.2 Evaluation and Assessment for the KMS..... 71 - -6.11.3 Conclusion..... 72 - -6.12 Cert Profile for O-RAN TLS Entity ..... 72 - -6.13 Certificate enrollment for new NF Deployment using CMPv2 ..... 72 - -6.14 Key Issue #28: Risk of Service un-availability due to root CA Certificate updates for CNFs and VNFs..... 72 - -6.15 On Shared O-RU Trust Anchors Management ..... 73 - -7 Key Issues-Solutions mapping..... 74 - -Annex: Change history/Change request (history) ..... 75 - -# List of Figures - -Figure 3-1: Logical Architecture of O-RAN system: Overview of the security architecture ..... 14 - -Figure 4-1: A possible system comprising different applications with different Root Certificates..... 29 - -Figure 5-1: Certificate-less TLS Authentication..... 40 - -Figure 5-2: Certificate-based TLS Authentication..... 40 - -Figure 5-3: A simplified depiction of the workings of ACME ..... 42 - -Figure 5-4: Secure Storage and Certificate Management Architecture (System Level View) ..... 46 - -Figure 5-5: Key-generation by the Virtualisation Platform ..... 47 - -Figure 5-6: Key-generation by the Trusted Application ..... 48 - -Figure 5-7: Key-generation by the Secure Module (e.g., HSM, TPM) ..... 49 - -Figure 5-8: Secure Key and File Storage Architecture Framework (overview) ..... 50 - -Figure 5-9: Scenarios for protecting keys within the secret storage volume based on TPM..... 51 - -Figure 5-10: Key protection based on KMS ..... 51 - -Figure 5-11: Certificate Update Orchestrator.....56 -Figure 5-12: Certificate renewal procedure .....58 -Figure 5-13 Certificate enrolment for new NF Deployment.....67 - -# --- Foreword - -This Technical Report (TR) has been produced by WG11 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 - -This technical report studies a comprehensive framework for certificate management across the O-RAN environment. - -The objectives of this study are to identify key issues, potential security requirements, solutions, and specifications to - -- Standardize a certificate management framework comprising protocols and procedures for certificate life cycle events (e.g. enrolment, renewal, revocation) within the O-RAN architecture (e.g., O-CU, O-DU, O-RU, Open Fronthaul, Non-RT-RIC, Near-RT-RIC, etc.) -- Address the following objectives: - - Support reuse of IETF CMPv2 certificate management - - Explore the IETF ACME, IETF BRSKI, IETF EST, and other industry efforts as potential components for a certificate management framework. - - Establish lifecycle service models to bring zero touch automation to the certificate management framework. - -# 2 References, Definitions of Terms and Abbreviations - -## 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. - -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 33.310: "Network Domain Security (NDS); Authentication Framework (AF)" -- [i.3] O-RAN ALLIANCE TS: "O-RAN Management Plane Specification" -- [i.4] RFC-6187: X.509v3 Certificates for Secure Shell Authentication -- [i.5] IETF RFC 4210: Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP) -- [i.6] Design and build a privately hosted Public Key Infrastructure - -- [i.7] NIST SP 1800-16C: Securing Web Transactions: TLS Server Certificate Management - -- [i.8] 3GPP TS 32.509: "Data formats for multi-vendor plug and play eNode B connection to the network" -- [i.9] Void -- [i.10] Void -- [i.11] ETSI GR NFV-SEC 005, NFV, trust, report on certificate management -- [i.12] ETSI GR NFV-IFA 029, Report on the Enhancements of the NFV architecture towards "Cloud-native" and "PaaS" -- [i.13] IETF RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile -- [i.14] IETF RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2 -- [i.15] IETF RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3 -- [i.16] IETF RFC 7540: Hypertext Transfer Protocol Version 2 (HTTP/2) -- [i.17] IETF RFC 6066: Transport Layer Security (TLS) Extensions: Extension Definitions -- [i.18] IETF RFC 6125: Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS) - -- [i.19] IETF RFC 7633: X.509v3 Transport Layer Security (TLS) Feature Extension -- [i.20] CA-Browser-Forum-BR-1.8.0: Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates, August 2021, . -- [i.21] IETF RFC 6347: Datagram Transport Layer Security Version 1.2 -- [i.22] IETF RFC 9325: Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) -- [i.23] Service Identity in TLS -- [i.24] IETF RFC 7093: Additional Methods for Generating Key Identifiers Values -- [i.25] NIST Special Publication 800-52 Revision 2: Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations -- [i.26] IETF RFC 6960: X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP -- [i.27] IETF RFC 3647: Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework -- [i.28] RFC 8995: Bootstrapping Remote Secure Key Infrastructure (BRSKI) -- [i.29] RFC 8993: A Reference Model for Autonomic Networking -- [i.30] RFC 8994: An Autonomic Control Plane (ACP) -- [i.31] RFC 8572: Secure Zero Touch Provisioning (SZTP) -- [i.32] IETF RFC 7030: Enrollment over Secure Transport -- [i.33] IETF RFC 5054: Using the Secure Remote Password (SRP) Protocol for TLS Authentication -- [i.34] IETF RFC 8295: EST (Enrollment over Secure Transport) Extensions -- [i.35] IETF RFC 5272: Certificate Management over CMS -- [i.36] IETF RFC 8951: Clarification of Enrollment over Secure Transport (EST): Transfer Encodings and ASN.1 -- [i.37] IETF RFC 8996: Deprecating TLS 1.0 and TLS 1.1 -- [i.38] IETF RFC 7231: Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content -- [i.39] IETF RFC 3986: Uniform Resource Identifier (URI): Generic Syntax -- [i.40] IETF RFC 2119: Key words for use in RFCs to Indicate Requirement Levels -- [i.41] O-RAN ALLIANCE TS: “Security Protocols Specifications” -- [i.42] IETF RFC 8555: Automatic Certificate Management Environment (ACME) -- [i.43] IETF RFC 8738: Automated Certificate Management Environment (ACME) IP Identifier Validation Extension -- [i.44] 3GPP TS 28.315: "Management and orchestration; Plug and connect; Procedure flows" -- [i.45] 3GPP TS 28.314: "Management and orchestration; Plug and connect; Concepts and requirements" -- [i.46] ETSI GR NFV-SEC 009, NFV Security,”Report on use cases and technical approaches for multi-layer host administration” -- [i.47] O-RAN ALLIANCE TS: “Security Requirements and Controls Specification” -- [i.48] Cryptographic Key Generation: NIST Publishes SP 800-133 Rev. 2, - -- [i.49] SOG-IS Agreed Cryptographic Mechanisms v1.3, -- [i.50] NIST Special Publication 800-57 Part 1 Revision 5: Recommendation for Key Management -- [i.51] O-RAN ALLIANCE TS: "O-RAN Architecture Description" -- [i.52] O-RAN ALLIANCE TS: "Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN" - -## 2.3 Terms - -For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [i.1] and the following apply: - -**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 this version of the specification, 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 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 shall 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. - -**Secure Storage and Retrieval Manager (SSRM):** a component designed to manage the secure storage, retrieval, and lifecycle management of sensitive data, such as cryptographic keys, certificates, and secrets, within the O-Cloud. The SSRM acts as an intermediary layer that abstracts the underlying complexities of secure storage mechanisms and provides standardized interfaces for applications and services to interact with secure resources. - -In Kubernetes environments, the combination of the kube-apiserver and cert-manager serves as an embodiment of an SSRM. The kube-apiserver acts as the central entry point for interactions with the Kubernetes control plane, providing authentication, authorization, and a unified API surface. Paired with cert-manager, which automates the management of TLS certificates and abstracts the intricacies of secure storage, this combination streamlines secure communication within Kubernetes clusters. The kube-apiserver offers centralized management, while cert-manager automates the secure storage and retrieval of certificates and private keys, ensuring a seamless and secure experience for applications. - -In OpenStack ecosystems, the collaboration between Keystone and Barbican mirrors the SSRM concept. Keystone functions as the identity and access management service, handling authentication, authorization, and policy enforcement. Complementing Keystone, Barbican operates as a secure key management system, safeguarding cryptographic keys and secrets. Together, Keystone and Barbican provide a standardized approach to secure storage, ensuring sensitive data remains protected while abstracting the complexities of secure key management. - -## 2.4 Abbreviations - -For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [i.1] and the following apply: - -| | | -|---------|------------------------------------------------| -| ACME | Automatic Certificate Management Environment | -| ACP | Autonomic Control Plane | -| AI/ML | Artificial Intelligence/Machine Learning | -| ANI | Autonomic Networking Infrastructure | -| BRSKI | Bootstrapping Remote Secure Key Infrastructure | -| CA | Certification Authority | -| CMPv2 | Certificate Management Protocol version 2 | -| CUO | Certificate Update Orchestrator | -| DEK | Disk Encryption Key | -| eNB | eNodeB (applies to LTE) | -| EST | Enrollment over Secure Transport | -| FTP | File Transfer Protocol | -| FTPS | File Transfer Protocol Secure | -| gNB | gNodeB (applies to NR) | -| IPsec | Internet Protocol Security | -| KEK | Key Encryption Key | -| KMS | Key Management System | -| KPI | Key Performance Indicator | -| KQI | Key Quality Indicator | -| LBT | Listen Before Talk | -| LLS | Lower Layer Split | -| MIMO | Multiple Input, Multiple Output | -| MNO | Mobile Network Operator | -| NETCONF | Network Configuration Protocol | -| NF | Network Function | - -| | | -|-------|-----------------------------------------| -| NFV | Network Function Virtualisation | -| O-RAN | Open Radio Access Network | -| PDCP | Packet Data Convergence Protocol | -| PNF | Physical Network Function | -| PRB | Physical Resource Block | -| PTP | Precision Timing Protocol | -| QoE | Quality of Experience | -| RA | Registration Authority | -| RBAC | Role-based Access Control | -| RIC | O-RAN RAN Intelligent Controller | -| SDN | Software Defined Network | -| SEK | Secret Encryption Key | -| SINR | Signal-to-Interference-plus-Noise Ratio | -| SMO | Service Management and Orchestration | -| SSH | Secure Shell | -| SSRM | Secure Storage Resource Manager | -| SZTP | Secure Zero Touch Provisioning | -| TLS | Transport Layer Security | -| UAV | Unmanned Aerial Vehicle | -| V2X | Vehicle to Everything | -| VM | Virtual machine | -| VNF | Virtualised Network Function | - -# 3 Architecture Requirements and Assumptions - -## 3.1 Architecture Requirements - -The Certificate Management Framework Architecture should be compatible with the M-Plane Certificate Management Framework specified in O-RAN Management Plane Specification [i.3]. These certificates conform to the X.509v3 certificate profile in RFC 5280 [i.30]. - -The M-Plane Certificate Management Framework in O-RAN Management Plane Specification [i.3] references Clause 9 of 3GPP TS 33.310 [i.2] where CMPv2 is used by “base stations to obtain an operator-signed certificate using a secured communication based on the vendor-signed certificate in the base station and a vendor root certificate pre-installed in the CA/RA server.” - -The M-Plane Certificate Management Framework in O-RAN Management Plane Specification [i.3] also states that “while the approach in [i.2] has been defined for provisioning certificates for use in either IPsec or TLS, the same techniques defined for provisioning TLS certificates are specified to be re-used to provision certificates for use in securing the SSHv2 based M-Plane connection as specified in RFC 6187 [i.4]. Hence, the TLS client CA is responsible for issuing certificates to NETCONF clients, irrespective of whether NETCONF is secured using TLS or SSHv2. Similarly, the TLS server CA is responsible for issuing certificates to NETCONF servers, irrespective of whether NETCONF is secured using TLS or SSHv2.” - -## 3.2 Architecture Assumptions - -### 3.2.1 Use Case for Physical Network Functions - -Figure 3-1 shows a general deployment architecture for certificate enrolment of a physical NF by an operator PKI. This general deployment architecture is generalized from clause 9 of 3GPP 33.310 [i.2]. - -![Diagram showing the logical architecture of an O-RAN system for certificate enrolment. It features three main components: RA/CA, NF B, and NF. RA/CA is connected to NF via a CMPv2 protocol. NF B is connected to NF via a Secure protocol. Annotations explain the pre-installation of vendor root and signed certificates, and the subsequent enrolment process.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) - -``` - - graph TD - RA/CA[RA/CA] -- CMPv2 --> NF[NF] - NF_B[NF B] -- Secure protocol --> NF - subgraph Annotations - A1[Vendor root certificate is pre-installed.] -.-> RA/CA - A2[Vendor-signed certificate of NF public key is pre-installed.] -.-> NF - A3[Enrolled NF certificate is used in the security association.] -.-> NF - A4[The NF obtains the operator-signed certificate on its own public key from RA/CA using CMPv2.] -.-> NF - end - -``` - -Diagram showing the logical architecture of an O-RAN system for certificate enrolment. It features three main components: RA/CA, NF B, and NF. RA/CA is connected to NF via a CMPv2 protocol. NF B is connected to NF via a Secure protocol. Annotations explain the pre-installation of vendor root and signed certificates, and the subsequent enrolment process. - -Figure 3-1: Logical Architecture of O-RAN system: Overview of the security architecture - -The NF is pre-provisioned with a public-private key pair by the vendor, and has the vendor-signed certificate of its public key pre-installed. - -An operator may deploy an RA/CA to replace the vendor-provisioned certificates with operator provided certificates. The operator CA may be deployed using one of the following: - -- either a stand-alone CA implementing a CMPv2 server, or -- a CA having delegated certain tasks to an RA, which is operating the CMPv2 server. - -On initial contact to the operator network the NF establishes a communication channel to the RA/CA of the operator. Using CMPv2 [i.5] a request for a certificate is sent to the RA/CA. The network authenticates the messages from the NF based on the vendor-signed certificate of the NF and the vendor root certificate pre-installed in the network. The NF shall check the integrity protection on the messages from the RA/CA based on the operator root certificate provisioned in the NF. In a response message the NF receives the operator-signed certificate. During the execution of the CMPv2 protocol the NF has to successfully provide a Proof of Possession of the private key associated to the public key to be certified. - -The operator root certificate may be provisioned in the NF prior to or during the CMPv2 protocol run. The protection of the operator root certificate during provisioning may be decided by operator security policy. If an operator root certificate provisioned prior to the CMPv2 protocol run is available, the NF shall use it. Otherwise, the NF shall use the operator root certificate provisioned during the CMPv2 run. If no operator root certificate is provisioned at all then the NF shall abort the procedure. - -After enrolment has been performed, the NF can use the operator-signed certificate to authenticate itself to the NF B of the operator, which is pre-installed with the operator root certificate. The NF then authenticates the NF B using the operator root certificate. - -If at later stage of NF deployment the operator wants to renew the NF certificate, the same procedure will be executed with the old operator-signed certificate of the NF taking the place of the vendor-signed certificate in the initial enrolment. - -# 4 Key Issues - -## 4.1 Key Issue #1: Considering RA and CA as separate logical entities - -### 4.1.1 General Description - -Given the system requirements for O-RAN, it's essential to recognize the Registration Authority (RA) and Certificate Authority (CA) as individual logical units. Some implementations might integrate both within the same network, while others could opt for separate networks, possibly utilizing third-party CAs. As highlighted in RFC4210 [i.5] Appendix A, the justification for an RA's presence can be categorized into technical and organizational reasons. Technically, not all end entities have the necessary hardware for token initialization, making it beneficial for the RA to have this capability, which could also be driven by policy considerations. Moreover, certain entities might not be equipped to issue certificates, underscoring the RA's potential role in this aspect. Organizationally, centralizing tasks within the RA might be more cost-effective, especially when there's a need for specialized token initialization equipment. By incorporating RAs, organizations might also reduce the number of CAs they require. RAs are often better positioned to link individuals with their digital identifiers, especially when the CA is located at a considerable distance from the end entity. It's also worth noting that many setups already possess an administrative structure, simplifying the process of identifying suitable RA candidates, a convenience that might not always extend to CAs. - -NOTE: For example, in WG11, the work-item for Near-RT RIC discusses the security procedure for xApp registration, where Near-RT RIC can also act as RA for xApps. - -### 4.1.2 Security Threats - -**Single Point of Compromise:** Combining RA and CA functions into one entity creates a single point of compromise. If an attacker gains access to this combined entity, they can both verify (as the RA) and issue (as the CA) certificates, leading to a complete breakdown of the trust model. - -**Operational Complexity:** Merging or intertwining the roles of RA and CA can lead to operational challenges, increasing the risk of human errors or misconfigurations. - -**Lack of Role Segregation:** Combining roles goes against the principle of least privilege, where entities should only have the minimum access required to perform their tasks. Misuse or abuse of privileges becomes a significant concern, especially if internal actors become malicious. - -**Backup and Recovery Risks:** A combined system means there's more data to backup and recover, complicating these processes. This may cause data loss or prolonged downtimes can occur if backup or recovery fails. - -**Policy Overlaps:** There might be policy overlaps or contradictions when RA and CA are combined. For instance, the policy for verifying an entity's identity (RA function) might conflict with the policy for issuing a certificate (CA function). - -## 4.2 Key Issue #2: Usage of PSK/Refrum for Initial Certificate Enrolment of PNFs - -### 4.2.1 General Description - -Using PSK/Refrum as a method for the Initial Certificate Enrolment of PNFs is an approach that might be essential for ensuring backward compatibility. However, this method of Certificate Management could necessitate manual interventions, thereby introducing potential vulnerabilities. To mitigate these risks, there's a need for supporting solutions that can seamlessly automate the PSK/Refrum based Certificate Enrolment process. - -### 4.2.2 Security Threats - -**Manual Intervention Risks:** Relying on manual steps for certificate enrolment can lead to human errors, misconfigurations, or oversights, which can compromise the security of the system. Incorrect certificate enrolments, unauthorized access, or even system downtimes can result from these errors, compromising the security and reliability of the O-RAN system. - -## 4.3 Key Issue #3: Usage of Vendor Certificates for Initial Certificate Enrolment of PNFs - -### 4.3.1 General Description - -The use of Vendor Certificates for the initial registration and certificate enrolment is outlined in 3GPP TS 33.310 [i.2]clause 9 “Certificate Enrolment for base stations”. - -This approach facilitates automated Certificate Enrolment, streamlining the integration of new PNFs with a plug-and-play model. - -### 4.3.2 Security Threats - -**Vendor Trustworthiness:** Relying on vendor certificates necessitates a high level of trust in the vendor's security practices and certificate management. If a vendor's security practices are lax, it could lead to the issuance of compromised or weak certificates. - -**Single Point of Failure:** If many PNFs rely on a single vendor's certificate for enrolment, it becomes a single point of failure. Compromise of the vendor certificate can jeopardize the security of all associated PNFs. - -## 4.4 Key Issue #4: Void - -Void - -## 4.5 Key Issue #5: Void - -Void - -## 4.6 Key Issue #6: Initial Certificate Enrolment for new NFs - -### 4.6.1 General Description - -For the seamless integration of new NFs into the network, there's a need for an automated procedure to obtain CA-signed certificates. This process should ensure a pre-established trust relationship with the Registration Authority (RA). - -### 4.6.2 Security Threats - -**Certificate Mismanagement:** If the procedure for obtaining CA-signed certificates isn't robust or secure, there's a risk of certificate mismanagement, misuse, or fraud. This may cause impersonation of legitimate NFs and/or network breaches. - -**Lack of Automation:** Manual processes for NF certificate enrolment can introduce human errors, inconsistencies, or delays. This may cause misconfigurations and/or operational inefficiencies. - -**Interception of Initial Communication:** The initial communication between the NF and the network during the enrolment phase could be intercepted if not securely encrypted. This may cause eavesdropping, data interception, or man-in-the-middle attacks. - -**Inadequate Revocation Mechanisms:** If a NF is compromised or needs replacement, there should be a swift mechanism to revoke its certificate. Ongoing risks arise from breached NFs if certificate revocation is either delayed or not executed properly. - -## 4.7 Key Issue #7: Void - -Void - -## 4.8 Key Issue #8: Vendor Root CA Certificate Renewal - -### 4.8.1 General Description - -When a Vendor's Root CA certificate approaches its expiration date, it's imperative for the Registration Authority (RA) to automatically renew the trust through the certificate management protocol. This proactive approach is essential to guarantee uninterrupted system availability. - -### 4.8.2 Security Threats - -**Expired Certificate Usage:** If the Vendor's Root CA certificate expires without renewal, any NF relying on it could face authentication failures. This may cause system disruptions and/or declined connections. - -**Dependency on Vendor:** The renewal process might depend on the vendor's responsiveness and their certificate issuance protocols. This may cause delays in certificate issuance and vulnerabilities in vendor-provided certificates. - -**Manual Renewal Process:** Relying on a manual process for the renewal of the Vendor Root CA Certificate introduces several challenges. Manual processes inherently increase the risk of oversight, delays, and human error. Without automation, there's a higher likelihood that the certificate might expire before renewal, especially if the impending expiration goes unnoticed or if there are delays in the manual renewal procedure. - -## 4.9 Key Issue #9: Void - -Void - -## 4.10 Key Issue #10: Procedure for Certificate Updates when revoked certificates are detected by NFs - -### 4.10.1 General Description - -During the establishment of TLS or IPsec, an NF might detect revoked certificates. A clear and efficient procedure is essential to update such certificates to ensure the confidentiality and integrity of communications. - -### 4.10.2 Security Threats - -**Continued Use of Revoked Certificates:** Without a prompt update procedure, NFs might continue using revoked certificates, leading to insecure communications. - -**Delay in Certificate Replacement:** If the procedure for updating revoked certificates isn't efficient, there could be significant delays in replacing them. This may cause extended periods of vulnerability, potential NF disruptions, and declined connections. - -**Lack of Automation:** Manual processes for updating revoked certificates can introduce human errors, inconsistencies, or delays. This may cause misconfigurations and/or operational inefficiencies. - -**Inadequate Monitoring:** Without continuous monitoring, revoked certificates might go undetected or unaddressed for extended periods. - -**Ineffective Revocation Lists:** If Certificate Revocation Lists (CRLs) or Online Certificate Status Protocol (OCSP) servers are not updated promptly or are inaccessible, NFs might not detect revoked certificates in time. This may cause continued use of compromised certificates and unauthorized access. - -## 4.11 Key Issue #11: Void - -Void - -## 4.12 Key Issue #12: Certificate to name mapping - -### 4.12.1 General Description - -The Certificate-to-name mapping system is a critical component in the authorisation process. It can lead to a breakdown in the trust model of the O-RAN system. Unauthorized access, especially if mapped to high-privilege names, can compromise the integrity and availability of the O-RAN system. - -### 4.12.2 Security Threats - -**Mapping Database Compromise:** If an attacker gains access to the system or database where the Certificate-to-name mappings are stored, they can alter these mappings. For instance, they might map their own certificate to a high-privilege username. - -#### Certificate Manipulation and spoofed authentication: - -The integrity and authenticity of certificates, pivotal in secure communications and authorisation within the O-RAN network, can be jeopardized through certificate manipulation and spoofed authentication. These threats can be notably exploited when the cipher used for signing the certificate lacks integrity assurance or when the TLS server is misconfigured, leading to inadequate validation of certificate signatures. This threat can be exploited under the following two cases: - -- Exploitation through cipher integrity: - - Attackers may alter or create certificates, manipulating identity information, and if the cipher lacks integrity, the system might accept these as valid, granting unauthorized access or privileges. -- Exploitation through TLS misconfiguration: - - A TLS server that doesn't validate certificate signatures accurately may accept manipulated or spoofed certificates, providing attackers unauthorized access based on misrepresented identity information. - -The system, whether due to cipher integrity issues or TLS misconfigurations, may erroneously trust the manipulated or spoofed certificate, mapping it to a high-privilege username or granting unauthorized access and privileges. - -Attackers, once authenticated, can perform unauthorized activities, such as data theft, network misconfigurations, or other malicious actions, under the guise of a legitimate entity. - -## 4.13 Key Issue #13: System overload due to bulk certificate updates - -### 4.13.1 General Description - -When huge number of PNFs / VNFs need to update certificates, the system and communication networks may be overloaded. - -If a huge number of network functions and/or services simultaneously require certificate updates (due to same expiry date, or, due to a common CA certificate revocation, or any other reason), it is possible that all of them trigger the certificate management procedures at the same time. - -- Operators may want to frequently renew the certificates in order to mitigate any security risks involved with using the certificates for longer durations. - - If, for example, a certain crypto algorithm is declared as compromised, it is likely that a huge number of network functions (physical and virtual) need to update their certificates. -- In scenarios when certificates are revoked, in order to avoid any security threats, it is desirable to update and use new certificates as soon as possible. - - According to RFC 4210 [i.5](sections 5.3.13 and 5.3.15), CA may announce revocation of certificates. It is likely that such revoked certificates affect many NFs simultaneously. - - When a new certificate needs to be used, existing secure connections (IPsec/TLS) need to be terminated. This may lead to intermittent unavailability of networks. -- For systems using certificates as authentication mechanisms for man-to-machine communications, the number of certificates will be directly proportional to the number of users. This could mean a large number of certificates, and maybe a need to update all of them together. - -Automated certificate management facilitates the need for minimum manual intervention; however, this can lead to a congestion or overload in the system in scenarios when bulk certificate updates happening simultaneously. Such system overload may lead to un-intentional Denial-of-Service. In scenarios when multiple NF instances catering to specific network slices, the affected network slices may not be dimensioned to accommodate such overload due to bulk certificate updates. - -### 4.13.2 Security Threats - -**System Overload:** When a large number of PNFs/VNFs simultaneously trigger certificate management procedures, it can cause significant strain on the system, potentially leading to slowdowns or outages. - -**Communication Network Congestion:** The simultaneous update of certificates can lead to a surge in network traffic, causing congestion in communication networks. - -**Potential Denial of Service (DoS):** Automated bulk certificate updates, especially if not properly managed or throttled, can unintentionally result in a DoS condition, making services unavailable to legitimate O-RAN NFs. - -**Intermittent Network Unavailability:** When secure connections (like IPsec/TLS) need to be terminated to update certificates, it can lead to temporary network disruptions. - -**Crypto Algorithm Compromise:** If a cryptographic algorithm is declared compromised, a vast number of network functions might need immediate certificate updates, exacerbating the overload issue. - -**Certificate Revocation Risks:** The revocation of certificates, especially if affecting many network functions simultaneously, can lead to widespread disruptions if not managed properly. - -**Delay in Addressing Security Threats:** While operators might want to renew certificates frequently to mitigate risks, the potential system overload can delay these updates, leaving the system vulnerable for longer durations. - -**Man-to-Machine Authentication Risks:** For O-RAN systems with a large number of users using certificates for authentication, simultaneous updates can lead to widespread authentication failures or delays. - -**Operational Complexity:** Managing and coordinating certificate updates for a vast number of PNFs/VNFs can be operationally complex, increasing the risk of errors or misconfigurations. - -## 4.14 Key Issue #14: Void - -Void - -## 4.15 Key Issue #15: Void - -Void - -## 4.16 Key Issue #16: Void - -Void - -## 4.17 Key Issue #17: Void - -Void - -## 4.18 Key Issue #18: Allow Flexibility in the Number of Operator Certificates Associated with each end entity / Interface - -### 4.18.1 General Description - -This key issue addresses the procedure for certificate management when one network function in O-RAN (PNF/VNF/CNF) has several functionalities and several logical interfaces, thus one network function may have several identities for different functionalities and different communication interfaces [ETSI GR NFV-SEC005 V1.2.1 [i.11]]. - -### 4.18.2 Security Threats - -**Multiple Certificate Tracking:** With multiple certificates per network function, tracking, renewing, and revoking certificates becomes more complex. This complexity can lead to mismanagement or oversight, potentially leaving expired or compromised certificates in use. - -**Multiple Points of Compromise:** Each certificate represents a potential point of compromise. With multiple certificates per network function, the attack surface increases, offering more opportunities for attackers to target or exploit a specific certificate. - -**Ambiguous Authorization:** With multiple identities for a single network function, there's a risk of confusion in determining which certificate grants what level of access or functionality. This can lead to unintentional over-privilege or under-privilege in access controls. - -**Granular Revocation:** If one certificate associated with a network function is compromised, determining whether to revoke only that certificate or all associated certificates can be challenging. Incorrect decisions can either leave vulnerabilities open or disrupt legitimate functionalities. - -**Authentication overhead due to multiple certificates:** Engaging in multiple authentications across various interactions due to the management of numerous certificates for a network function interacting with different interfaces or systems, which could inadvertently introduce cumulative latency and operational delays in the network communication and data transmission processes. - -**Varied Certificate Handling:** Different vendors might handle multiple certificates differently, leading to potential integration or interoperability challenges in a multi-vendor O-RAN environment. - -**Bulk Operations Vulnerabilities:** Automated systems managing multiple certificates might inadvertently expose them to risks during bulk operations, like simultaneous renewals or updates, potentially leading to system overloads or misconfigurations. - -## 4.19 Key Issue #19: Certificate Management in Distributed Cluster Processing - -### 4.19.1 General Description - -VNF and CNF components terminating interfaces that use X.509 certificates for authentication can be scaled across multiple instances on a single host and across multiple hosts. This distributed nature poses unique challenges for certificate management. - -The certificate management framework must support these architectural patterns. It's imperative to ensure that as VNFs and CNFs scale, the associated certificates are managed securely and efficiently. - -Adherence to best practices is crucial: - -- Each VNF or CNF instance should ideally have its unique certificate. This not only ensures individualized authentication but also limits the potential security impact should any single instance be compromised. -- In environments like Kubernetes, controlling the traffic flow into and out of the cluster is vital. Assigning certificates to the ingress or egress points provides a layer of authenticated security. - -Furthermore, as deployments expand to support geographic redundancy, the certificate management system should be capable of maintaining consistent security protocols across all NF instances, irrespective of their location. - -### 4.19.2 Security Threats - -**Certificate Management Mistakes:** As VNF and CNF components scale across multiple instances and hosts, the sheer number of certificates to manage can become overwhelming, leading to potential mismanagement or oversight. - -**Varying Certificate Assignments:** Different architectural patterns might lead to inconsistencies in how certificates are assigned, renewed, or revoked, potentially leaving vulnerabilities open or causing operational disruptions. - -**Single Point of Failure:** If one instance of a VNF or CNF is compromised, and best practices like unique certificates for unique instances aren't followed, attackers might gain unauthorized access to other instances or components. - -**Cluster Entry and Exit Points (Ingress/Egress Vulnerabilities):** Assigning a certificate to the ingress or egress point in a Kubernetes cluster can create a choke point. If this certificate is compromised, it can jeopardize the security of the entire cluster. - -**Geographic Redundancy Concerns (Synchronization Issues):** Deployments that support geographic redundancy might face challenges in synchronizing certificate updates, renewals, or revocations across geographically distributed instances, leading to potential inconsistencies or vulnerabilities. - -**Automated Scaling Risks:** In environments where instances are dynamically created or destroyed based on demand, ensuring that each instance has a valid, uncompromised certificate becomes challenging. There's a risk of instances being spun up with outdated or vulnerable certificates. - -**Interoperability and Integration Issues:** Different VNF and CNF components, especially from different vendors or in different architectural patterns, might handle certificates differently, leading to potential integration challenges or security gaps. - -**Revocation and Renewal Challenges:** With distributed clusters, determining which certificate to renew or revoke, especially in the event of a compromise, becomes complex. Incorrect decisions can disrupt legitimate services or leave vulnerabilities open. - -## 4.20 Key Issue #20: Certificate Management and Secure Storage of Application Private Keys - -### 4.20.1 General Description - -Secure distribution and storage of Application certificates and private keys is critical to the effective use of certificates for authentication and confidentiality. The certificate management framework should include recommendations for secure storage of Applications private keys. - -### 4.20.2 Security Threats - -**Storage compromise:** Without secure storage solutions like vaults where keys are stored can be breached, leading to the exposure of sensitive cryptographic material and the compromising the entire authentication mechanism. - -**Man-in-the-Middle attacks:** Transmitting private keys over networks, if not done securely, can expose them to interception, leading to potential man-in-the-middle attacks. - -**Physical access to storage:** If the environment isn't resistant to physical breaches, adversaries could gain physical access to the storage medium, leading to potential data theft or tampering. - -**Lack of key rotation:** If the certificate management framework doesn't provide clear guidelines on key rotation, outdated or potentially compromised keys might continue in use. - -**Regulatory violations:** Inadequate protection of cryptographic material can lead to violations of data protection regulations, resulting in penalties and reputational damage. - -**Management challenges (Multiple NF instances):** As the number of NF instances grows, ensuring that each instance securely generates and stores its private keys becomes operationally complex. - -## 4.21 Key Issue #21: Coordinating Certificate Management with VNF/CNF Lifecycle Activities - -### 4.21.1 General Description - -The lifecycle activities of VNF/CNF are not always synchronized with the validity periods of their associated certificates. As these components evolve, undergo updates, or are replaced, it's crucial to ensure that their certificate management remains consistent and secure. Several scenarios highlight the importance of this coordination: - -**Updating a VNF/CNF to a new version:** When updating or replacing a VNF/CNF, the handling of certificates becomes paramount. The updated component must maintain the same level of trust and authentication capabilities as its predecessor. - -**Certificates stored in a vault or persistent storage:** If certificates are stored in a secure vault or other persistent storage solutions, a recreated or updated VNF/CNF should be able to access these without compromising security. The process for granting this access, especially in the context of updates or replacements, needs clear definition and robust security measures. - -**Certificates embedded within the VNF/CNF:** For VNFs that store certificates internally, software component updates should not disrupt the availability or integrity of these certificates. It's essential to ensure that updates are seamless, without inadvertently affecting the stored certificates. - -**Certificates managed by Kubernetes:** In environments where Kubernetes manages CNF containers and their certificates, updating or replacing CNF containers should not impact the availability or validity of the associated certificates. The orchestration platform must ensure that new container versions inherit the necessary certificates without security lapses. - -### 4.21.2 Security Threats - -**Misalignment of certificate validity and component lifecycle (Expired certificates):** If the lifecycle of a VNF/CNF extends beyond the validity of its certificate, it might continue to operate with an expired certificate, leading to authentication failures or reduced trust. - -**Inconsistent certificate management during updates (Loss of trust):** If an updated VNF/CNF doesn't maintain the same certificate or trust level as its predecessor, it can lead to trust breakdowns in the network, causing operational disruptions. - -**Compromised certificate storage (Unauthorized access):** If the process of granting access to certificates in a vault or persistent storage isn't secure or if insecure vaults or storage solutions are used, malicious entities might gain unauthorized access to sensitive certificate data. - -**Software update overwrites and loss of certificate integrity:** Updates to VNF/CNF components might inadvertently overwrite or corrupt internally stored certificates making them unusable or less secure, leading to potential authentication issues. - -**Management overhead:** Coordinating certificate management with VNF/CNF lifecycle activities can increase operational complexity, leading to potential mismanagement or oversight. - -## 4.22 Key Issue #22: Supporting Public and Private Certificate Authorities (CA) - -### 4.22.1 General Description - -To cater to the varied needs of different O-RAN network components and to offer flexibility in security configurations, the certificate management framework must be adept at managing a range of certificates. This includes client/server certificates, which facilitate secure interactions between O-RAN network entities, as well as intermediate certificates that form the chain of trust, and root certificates that anchor this trust. - -Furthermore, the origin of these certificates can vary. They might be issued by public CAs, which are globally recognized and trusted entities, or by private CAs, which are often tailored for specific organizational or network needs. The O-RAN certificate management framework must seamlessly support and manage certificates from both these sources, ensuring that regardless of the CA's nature, the security and integrity of the O-RAN network remain uncompromised. - -### 4.22.2 Security Threats - -**Mismanagement of multiple certificate sources:** Managing certificates from both public and private CAs can lead to inconsistencies in how certificates are validated, renewed, or revoked, potentially leaving vulnerabilities open or causing operational disruptions. - -**Intermediate certificate compromise:** If an intermediate certificate is compromised, it can undermine the trust of any certificate issued under it. - -**Root certificate exposure:** The exposure or compromise of a root certificate can jeopardize the entire trust chain. - -**Private CA - Insufficient validation:** Private CAs, especially if not properly managed, might issue certificates without rigorous validation, leading to potential security risks. - -**Private CA - Limited revocation capabilities:** Private CAs might not have the same robust infrastructure as public CAs for certificate revocation, leading to delays in revoking compromised certificates. - -**Public CA - Global exposure:** Certificates from public CAs, being globally recognized, can be a target for attackers, leading to potential large-scale attacks or exposures. - -**Public CA - Third-party risks:** Relying on external public CAs introduces third-party risks, where the compromise or mismanagement of the CA can impact the O-RAN network. - -**Management overhead:** Coordinating certificate management from multiple sources (public and private CAs) can increase operational complexity, leading to potential mismanagement or oversight. - -**Varied certificate standards:** Different CAs, especially across public and private domains, might have varied certificate standards or formats, leading to potential integration/interoperability challenges or security gaps. - -**Regulatory violations:** Inadequate management or validation of certificates, especially from private CAs, can lead to violations of data protection or security regulations, resulting in penalties and reputational damage. - -## 4.23 Key Issue #23: Distribution of Intermediate and Root Certificates - -### 4.23.1 General Description - -The management and distribution of intermediate and root certificates forms the backbone of the certificate trust chain. The O-RAN certificate management framework must be equipped with the capabilities that automate these processes. Specifically: - -- Operators should have an automated mechanism to request both intermediate and root certificates from the Certificate Authorities (CA) responsible for issuing the deployment's certificates. This ensures timely and efficient acquisition of these critical trust anchors. -- Once acquired, there should be a straightforward method to load these certificates into the key stores of the various network components, be it PNF, VNF, or CNF. This ensures that every component in the network is aligned with the trust framework and can validate communications effectively. - -### 4.23.2 Security Threats - -**Incomplete trust chain:** If intermediate or root certificates are not properly distributed or loaded, it can result in an incomplete or broken trust chain, leading to authentication failures or reduced trust. - -**Unauthorized access during distribution:** If the distribution process isn't secure, certificates could be intercepted and potentially altered or replaced with malicious ones during transit. - -**Exposure during Request:** An automated request mechanism that isn't properly secured can expose sensitive details or allow unauthorized entities to request certificates. - -**Outdated certificates:** If the distribution process isn't timely, network components might operate with outdated intermediate or root certificates, leading to potential security risks. - -**Misconfigurations:** Automated processes, if not properly configured, can lead to errors such as loading the wrong certificates or loading them into incorrect locations. - -**CA compromise:** If the CA responsible for issuing certificates is compromised, it can lead to the distribution of malicious or unauthorized certificates. - -**Regulatory violations:** Inadequate management or distribution of certificates can lead to violations of data protection or security regulations, resulting in penalties and reputational damage. - -## 4.24 Key Issue #24: CMPv2 Message Minimal Set and Robustness - -### 4.24.1 General Description - -The O-RAN certificate management framework must clearly define the specific CMPv2 message set that will be supported. This not only standardizes the communication for certificate operations but also ensures that the network components have a consistent and robust protocol to rely on for certificate-related interactions. By specifying this minimal set, the framework aims to streamline certificate management processes, reduce ambiguities, and bolster the overall security and efficiency of the O-RAN network (3GPP TS 33.310 [i.2] clause 9.5 has a CMPv2 profile definition). - -### 4.24.2 Security Threats - -**CMPv2 Exploits:** If the CMPv2 protocol or its implementation has vulnerabilities, attackers could exploit these to compromise certificate operations or gain unauthorized access. - -**Inconsistent message handling:** Without a clearly defined message set, different network components might handle CMPv2 messages inconsistently, leading to potential security gaps or operational disruptions. - -**Ambiguities in message processing:** Without a clear and minimal set of supported messages, there could be ambiguities in how messages are processed, leading to potential errors or security risks. - -## 4.25 Key Issue #25: RA and CA Capacity Estimation, Renewal Intervals and Credential Strength - -### 4.25.1 General Description - -In the evolving landscape of O-RAN networks, the strength and validity of cryptographic credentials play a pivotal role in ensuring secure communications. Adhering to best practices, the current recommendations emphasize: - -- **Validity periods:** Certificates should have validity periods that don't exceed one year. This ensures that credentials are regularly updated, reducing the window of vulnerability, and aligning with the dynamic nature of network environments. -- **Elliptical Curve Cryptography (ECC):** When leveraging ECC algorithms, it's advised to use key lengths of three hundred eighty-four (384) bits. This strikes a balance between computational efficiency and security, providing robust protection against potential cryptographic attacks. -- **Diffie-Hellman Cryptography:** For systems employing Diffie-Hellman cryptographic algorithms, key lengths should be set to a minimum of two thousand and forty-eight (2048) bits. This ensures a high level of security, making it computationally challenging for adversaries to compromise the encryption. - -### 4.25.2 Security Threats - -#### Certificate expiry and renewal: - -- If certificates expire without timely renewal, it can lead to authentication failures or communication breakdowns. -- Longer validity periods can provide attackers with a more extended window to exploit potential vulnerabilities associated with a certificate. - -**Brute Force attacks:** Insufficient key lengths can make cryptographic algorithms susceptible to brute force attacks. - -**Cryptographic vulnerabilities:** As cryptographic research progresses, older algorithms or shorter key lengths might be found vulnerable. If not updated, they can be exploited. - -**ECC - Weak Curves:** Not all elliptical curves provide the same security level. Using weak or compromised curves can lead to reduced security. - -**DH - Man-in-the-Middle attacks:** Without proper authentication or with shorter key lengths, Diffie-Hellman can be vulnerable to man-in-the-middle attacks. - -**Logjam Attack:** If not properly configured, Diffie-Hellman is susceptible to the Logjam attack, where attackers can downgrade to vulnerable TLS connections. - -**Performance overhead:** While longer key lengths provide better security, they also come with a performance overhead, potentially affecting network efficiency. - -## 4.26 Key Issue #26: Namespace Conventions - -### 4.26.1 General Description - -The certificate management framework should develop common namespace template examples (Cert Subject/SANs) to facilitate rapid integration with multiple vendor products and enable cross operator integration. - -VendorName and OperatorName should be the only required inputs to generate all namespaces. - -Namespace conventions should only be defined after the other key issues have been addressed. Additionally, it must be determined which entity, the client requesting a certificate or the CMPv2 implementation used by the client, is responsible for specifying each component of a named field, e.g., subject or SAN. - -### 4.26.2 Security Threats - -**Inconsistent namespace use:** If namespace conventions are not consistently used across all certificates, it could lead to integration issues, misconfigurations, or erroneous trust establishment between entities. - -**Integration challenges:** Without standardized namespace conventions, integrating multiple vendor products and enabling cross-operator integration might become cumbersome and error-prone, potentially leading to security loopholes. - -**Impersonation threats:** In the absence of stringent namespace conventions, attackers might exploit the laxity to create certificates that impersonate legitimate entities, thereby gaining unauthorized access and compromising secure communications. - -## 4.27 Key issue #27: Handling of certificate revocation in O-RAN - -### 4.27.1 General Description - -Certificates revocation procedures are a critical part of the overall certificate lifecycle management. Every certificate has a finite validity period, during which the certificate is expected to be in use. However, prior to the expiration of the validity period, the Certification Authority (CA) may declare that a certificate that it issued can no longer be trusted due to multiple circumstances including suspected compromise of the private key. - -How do we handle certificate revocation in O-RAN elements? Certificate validation requires access to revocation information, either in the form of a Certificate Revocation Lists (CRL) or an Online Certificate Status Protocol (OCSP) response. OCSP Responses are often included in a TLS handshake; this practice is called OCSP stapling. - -RFC 5280 [i.30] defines a CRL as ‘a time-stamped list identifying revoked certificates that is signed by a CA or CRL issuer and made freely available in a public repository’. The method involves each CA/CRL issuer periodically issuing - -such list, in order to communicate the revocation status of the affected certificates. When a client wants to retrieve a CRL for a particular certificate, it retrieves it from a specified CRL Distribution Point (CRLDP) that is carried in the certificate itself. Typically, HTTP is used to fetch the CRL, and the locations supporting the download of the CRL are chosen to reduce the inherent latency of the procedure. - -OCSP, defined in RFC 6960 [i.26], is ‘a protocol useful in determining the current status of a digital certificate without requiring CRLs’. It can be used in addition to or instead of CRLs. OCSP is often faster than CRL checking process. With OCSP stapling (refer to RFC 6066 [i.17]) the OCSP Response is fetched by the TLS server before the handshake, and then it is transported together with the certificate (“stapled”) during the handshake. OCSP stapling reduces latency and increases availability of the revocation information, hiding any OCSP Responder outages, even very short ones. - -When a CA has revoked, or it is about to revoke, a particular certificate, it may issue an announcement for revocation, to enable the automated re-enrolment; see Section 5.3.15 of RFC 4210 [i.5]). - -In some situations, an RA can detect revoked Vendor / Service Provider’s CA certificates. The RA should be able to issue signed revocation requests on behalf of end entities associated with it, whereas the end entity may not be able to do this itself, especially if access to the private key has been lost. This could be a use case to study, i.e., who and under what circumstances should/can sign the revocation request that will be accepted by the CA. - -As part of the PNF/VNF/CNF lifecycle management procedures certificates associated with a decommissioned PNF/VNF/CNF should no longer be useable, therefore the decommissioning process must include a certificate revocation request to the issuing CA. - -### 4.27.2 Security Threats - -**Mismanagement of revocation requests:** Ineffective handling or communication breakdowns regarding revocation requests could lead to compromised certificates remaining active. This allows for the potential misuse of compromised certificates, endangering secure communications and data integrity. - -**Ineffective decommissioning:** If certificates of decommissioned PNF/VNF/CNF are not revoked effectively, they might be misused. This could lead to unauthorized activities, such as data breaches or network intrusions, under the guise of decommissioned entities. - -**OCSP responder outages:** Dependency on OCSP responders for certificate validation could be risky in the event of outages. This could hinder the ability to validate certificate statuses, potentially disrupting secure communications. - -**Compromised certificate continuance:** If a compromised certificate is not promptly revoked and announced, it may continue to be used maliciously. This could enable attackers to impersonate legitimate entities, decrypt secure communications, or inject malicious content. - -**Incomplete revocation dissemination:** In some instances, revocation information may not be disseminated to all relevant entities in the network. This could lead to some entities continuing to trust a revoked certificate, posing security risks. - -## 4.28 Key issue #28: Risk of Service un-availability due to root CA Certificate updates for CNFs and VNFs - -### 4.28.1 General Description - -CNFs and VNFs use certificates which are signed by intermediate or root CA certificates from operator’s choice of PKI. - -![Diagram showing two application groups (Application Group 1 and Application Group 2) running on a Kubernetes Platform / Cloud Host Environment. Application Group 1 uses Root CA1 for signing certificates, while Application Group 2 uses Root CA2. The Root CAs are located within the Kubernetes Platform / Cloud Host Environment.](dcb5711d118ae6753b0e12f86eda37db_img.jpg) - -The diagram illustrates a system architecture where two distinct application groups, 'Application Group 1 (CNFs/VNFs)' and 'Application Group 2 (CNFs/VNFs)', are deployed on a shared 'Kubernetes Platform / Cloud Host Environment'. Application Group 1 is associated with 'Root CA1', and its certificates are signed by 'Platform Root CA1'. Application Group 2 is associated with 'Root CA2', and its certificates are signed by 'Platform Root CA2'. The Root CAs (Root CA1 and Root CA2) are shown as components within the Kubernetes Platform / Cloud Host Environment, with arrows indicating the signing relationship from the Root CAs to the certificates within each application group. - -Diagram showing two application groups (Application Group 1 and Application Group 2) running on a Kubernetes Platform / Cloud Host Environment. Application Group 1 uses Root CA1 for signing certificates, while Application Group 2 uses Root CA2. The Root CAs are located within the Kubernetes Platform / Cloud Host Environment. - -Figure 4-1: A possible system comprising different applications with different Root Certificates. - -Figure 4-1 gives a high level view of a possible system where different application groups of CNFs/VNFs may be using different root/sub-CA certificates for signing. - -The root CA / sub-CA certificates used to sign certificates for CNFs and VNFs may need to be updated in the following scenarios: - -- Root / sub CA certificate expiry -- Root/sub CA certificate revocation -- Operator deciding to change the CA for signing - -In general, these scenarios can be referred to as a need for PKI migration. During the PKI migration procedure, all the certificates issued to CNFs / VNFs and signed by these root CA certificates need to be updated with new CA certificates. If such a PKI migration is needed during runtime, when system is already providing services: - -- This can lead to slice / service un-availability -- Some CNFs can be handling UPF functionality -- Some CNFs can be handling various control plane functionalities -- If all CNFs/VNFs catering to a network slice use the same root CA, there is a risk of un-availability of the full slice. - -Partial un-availability of services may still appear as network un-availability for end users. - -### 4.28.2 Security Threats - -**Partial or complete service un-availability:** If intermediate or root CA certificates which are used to sign certificates for CNFs and/or VNFs need to be updated during runtime, it is likely to lead to partial or complete service un-availability. - -**Network slice un-availability:** If all CNFs and/or VNFs of a particular network slice are impacted, it is likely to lead to unavailability of the network slice. - -## 4.29 Key issue #29: Certificate requirements for O-Cloud control plane - -### 4.29.1 General Description - -The O-Cloud control plane acts as a pivotal component in managing and orchestrating cloud resources and services. Ensuring secure communications and operations within the control plane involves: - -- Establishing a dedicated CA for the O-Cloud control plane to isolate and protect the certificate issuance and management processes specific to control plane components. -- Enforcing the use of TLS for all communications within the control plane components to ensure that data in transit is encrypted and authenticated, safeguarding it from unauthorized access and manipulation. - -### 4.29.2 Security Threats - -**Cross-domain security breaches in unified CA environments:** In a multi-domain (plane) environment, a security breach in one domain might cascade to others, especially if a common CA is used for certificate issuance across all domains. - -**CA Compromise:** If a CA is compromised, all certificates issued by it, across all domains, are potentially untrustworthy, leading to widespread network vulnerability. - -**Policy misalignment in Shared CA Environments:** Shared CAs might necessitate generalized policies that may not align with the specific security and operational needs of the control plane. - -## 4.30 Key issue #30: Certificate management for cloud deployment models - -### 4.30.1 General Description - -Addressing the intricacies of certificate management is pivotal, especially when considering varied O-Cloud deployment models, namely private cloud, community cloud, public cloud, and hybrid cloud. Each deployment model presents unique challenges and requirements in terms of certificate issuance, renewal, and revocation, which necessitates a tailored approach to ensure secure and efficient operations. - -### 4.30.2 Security Threats - -**Unauthorized access in multi-tenancy environments:** Public clouds often involve multi-tenancy, where multiple users or entities share the same resources. If certificate management is not meticulously handled, one tenant might unintentionally gain access to another tenant's data or services, leading to potential data leakage, unauthorized data manipulation, or other security incidents. - -**Complexity in hybrid cloud certificate coordination:** Hybrid cloud models, which integrate both private and public cloud solutions, necessitate coordinated certificate management to ensure secure data transfer and communication between different environments. Failure to synchronize and securely manage certificates might expose data during transfer, making it susceptible to interception or alteration by malicious entities. - -**Internal trust models:** Private clouds often operate on an internal trust model, where the CA is implicitly trusted by all entities within the organization. Mismanagement in this context can lead to internal threats, where malicious actors within the organization or compromised internal systems exploit the trust placed in the CA to conduct attacks, such as impersonating legitimate services or users. - -**Lack of external audit:** Unlike public CAs, which are often subject to external audits due to their widespread use on the public internet, private CAs might not be subject to the same level of oversight. This lack of external audit can sometimes lead to lax practices or oversights going unnoticed and unaddressed, potentially increasing the risk of mismanagement. - -## 4.31 Key issue #31: Void - -Void - -## 4.32 Key issue #32: Void - -Void - -## 4.33 Key issue #33: Certificate Profiling in O-RAN - -### 4.33.1 General Description - -A certificate profile is basically a template used to specify fields and form of a certificate. The profiles allow to configure a set of parameters, which support the security posture of the system as well as interoperability. 3GPP has specified in TS 33.310 [i.2] on the top of RFC5280 [i.13], several certificate profiles for types of network elements (e.g. Security Gateway (SEG), SBA, etc.), protocol (e.g. TLS entity), CA type (e.g. interconnection, SEG CA, etc.) and procedures (e.g. base station enrolment). This key issue intends to study specific O-RAN certificate profiling requirements across the main network functions of the O-RAN architecture in addition to those specified in RFC5280 and 3GPP, especially for elements and systems expressly defined in O-RAN (e.g. O-RU, Near-RT RIC, Non-RT RIC, etc.). - -Common certificate security parameters are defined in O-RAN Security Protocol specification [i.41], such as hash algorithms, signature algorithms, minimum key lengths, etc. However, certain network functions, sub-systems or protocols used in O-RAN may require specific certificate profiles, including e.g., rules for validity periods, extensions (e.g. subjectAltName, keyUsage, etc.). - -Once the certificate profiles have been defined for O-RAN, the CA(s) serving O-RAN architecture shall check that the requests are matching the pre-defined profiles, as well as the network elements of the O-RAN architecture shall accept only profiled certs for authentication and encryption purposes. - -### 4.33.2 Security Threats - -**Inconsistent security posture:** Without standardized certificate profiles, different elements within the O-RAN system might employ varying security parameters, leading to inconsistencies in the security posture across the network and potentially creating weak links that can be exploited by attackers. - -**Compromised encryption and authentication:** If certificate profiles are not rigorously defined and enforced, certificates that do not adhere to optimal security practices may be used, potentially compromising the encryption and authentication mechanisms within the O-RAN network. - -**Misalignment with external standards:** If O-RAN-specific certificate profiles diverge significantly from established standards (e.g., RFC5280 [i.13], 3GPP TS 33.310 [i.2]), it may introduce complexities and challenges in ensuring alignment and compatibility with external systems and networks. - -**Non-compliance with regulatory requirements:** Certificate profiles that do not align with regulatory or industry-specific requirements for cryptographic standards and data protection may expose the O-RAN network to legal and compliance risks. - -**Vendor-specific vulnerabilities:** If certificate profiles are not standardized and are heavily influenced by vendor-specific implementations, it may introduce vulnerabilities specific to certain products or solutions within the O-RAN system. - -## 4.34 Key issue #34: Void - -Void - -## 4.35 Key issue #35: Void - -Void - -## 4.36 Key issue #36: Certificate sharing or not-sharing in Apps/VNFs/CNFs - -### 4.36.1 General Description - -**Sharing case:** In the virtual environment, the NF is distributed in the virtual environment and there is no physical boundary for internal communication. If the private key has multiple copies, the risk of key disclosure is increased: transferring the private key faces communication attack, and, multiple copy or multiple access means one copy disclosure will pose a threat to all VMs/Containers using that certificate. Therefore, sharing private key and certificate should be actively discouraged unless carefully implemented. - -**Not sharing case:** For this case, multiple certificates for one App/VNF/CNF brings some complexities for management: - -- Complexity in operation and maintenance (e.g. complex to configure the mapping between certificates and VMs/Containers) -- Complexity in updating/revoking a certificate. The CA/RA workload is increased -- Complexity to O-Cloud dynamic orchestration. Each time the VM/Container scales and/or migrates, the certificate is expected to be either initially applied or revoked. The application and revoke are network communication and will lead to time latency for the orchestration. - -### 4.36.2 Security Threats - -#### Threats from Sharing Certificates: - -**Widespread compromise:** A single compromise of a private key that is shared across multiple VMs/Containers can cascade into a network-wide security incident, affecting various applications and services. This could lead to unauthorized access, data breaches, and potential downtimes. - -**Communication interception:** The transmission of private keys across the network can be intercepted by malicious actors, especially if the communication channels are not adequately secured. This interception can facilitate unauthorized access and data manipulation. - -**Unauthorized access:** The availability of multiple copies of a private key increases the vectors through which unauthorized entities might gain access. Unauthorized access can lead to data breaches. - -#### Threats from Not Sharing Certificates: - -**Operational disruptions:** Managing multiple certificates for each App/VNF/CNF can introduce operational challenges, particularly in ensuring that each certificate is correctly configured and mapped. Misconfigurations or erroneous mappings can lead to service disruptions, inaccessible services, and potential non-compliance with regulatory standards. - -**Delayed orchestration:** The necessity to apply or revoke certificates during scaling or migration operations introduces a latency that can impede the swift orchestration of services. This delay can impact the agility of the O-Cloud - -environment, affecting its ability to promptly scale, migrate, or recover services, which is crucial in maintaining service availability and reliability. - -## 4.37 Key issue #37: Lightweight solution - -### 4.37.1 General Description - -The certificate management solution should be lightweight to support low resource devices and reduce the footprint and computational overhead associated with certificate management. Striking a balance between maintaining a robust, secure certificate management system and ensuring that it is not resource-intensive is pivotal to support various applications within the O-Cloud environment. Implementing a lightweight certificate management solution, while beneficial for low-resource applications, can introduce several security threats that need to be meticulously considered and mitigated. - -### 4.37.2 Security Threats - -**Limited security protocols:** Using lightweight solutions may necessitate the use of simplified or less secure cryptographic algorithms and protocols. These might not be equipped to safeguard against advanced persistent threats or sophisticated cyber-attacks, thereby making the system susceptible to unauthorized access and data breaches. - -**Inadequate revocation capabilities:** Efficient certificate revocation is crucial to prevent unauthorized access, especially in cases where a certificate is compromised. Lightweight solutions might struggle to promptly manage revocation processes, thereby extending the vulnerability window. - -**Insufficient audit and logging:** Limited resources might restrict the ability to maintain comprehensive logs and audits, which are crucial for identifying and investigating security incidents and ensuring regulatory compliance. - -## 4.38 Key issue #38: Interoperability - -### 4.38.1 General Description - -The key management solution should be specified in an unambiguous and well-defined manner to allow easy interoperability of implementations. If protocols are underspecified the O-RAN specification should add a profile that fills the gaps. - -### 4.38.2 Security Threats - -**Inconsistent implementation across vendors:** Different vendors might interpret and implement certificate management protocols differently, leading to inconsistencies that could be exploited by malicious actors. This can lead to unauthorized access, data breaches, and disrupted communication between NFs in the O-RAN system. - -**Inconsistent revocation handling:** Varied approaches to managing certificate revocations across implementations could result in the persistent use of revoked certificates within certain NFs of the O-RAN system. Consequently, this might allow malicious or compromised NFs to continue operating within the network, perpetuating ongoing security threats. - -**Inadequate certificate authentication:** Divergent certificate validation methodologies across O-RAN NFs may result in suboptimal verification processes, paving the way for security compromises. Consequently, this may allow unauthorized access and potentially cause data leaks due to the acceptance of invalid or expired certificates. - -## 4.39 Key issue #39: Crypto agility - -### 4.39.1 General Description - -The solution should be easy to extend with new crypto algorithms as the threat landscape changes (eg. post-quantum crypto). - -### 4.39.2 Security Threats - -**Outdated algorithm exploitation:** Persistent use of outdated cryptographic algorithms may expose the O-RAN system to adversaries who have developed capabilities to exploit known vulnerabilities. The exploitation of outdated cryptographic methods could lead to unauthorized access, manipulation of sensitive data, and potential disruption in communication within the O-RAN system. - -**Quantum computing threats:** The advent of quantum computing threatens the security of traditional cryptographic algorithms, which may become obsolete or insecure. The O-RAN system might be susceptible to breaches by quantum-enabled adversaries, leading to unauthorized access and potential data breaches, thereby compromising user privacy and operational data. - -## 4.40 Key issue #40: Void - -Void - -## 4.41 Key Issue #41: CMPv2 - -### 4.41.1 General Description - -Certificate Management Protocol version 2 (CMPv2) is the most commonly supported and used protocol for certificate management in mobile networks. CMPv2 is specified by 3GPP and O-RAN Alliance WG4 for the M-Plane. The lack of specification for CMPv2 in the O-RAN Alliance's Security Protocols Specifications allows a security gap and could impact vendor interoperability. It would be beneficial to the O-RAN community to update the Security Protocols Specifications to include CMPv2. - -### 4.41.2 Security Threats - -**Inconsistent implementation and interoperability issues:** Without a standardized specification for CMPv2, different vendors might implement the protocol in slightly different ways. This inconsistency can lead to vulnerabilities if one vendor's implementation is less secure than another's, to interoperability issues, where systems from different vendors might not communicate seamlessly. - -## 4.42 Key Issue #42: Certificate management for Shared O-RU - -### 4.42.1 General Description - -In a multi-operator shared O-RU environment, diverse certificate policies and practices among operators can lead to inconsistencies in certificate management, challenges in synchronizing updates, and complexities in establishing mutual trust, making coordinated and harmonized operations crucial for security and functionality. - -### 4.42.2 Security Threats - -Different operators might have varying certificate policies, leading to potential inconsistencies in certificate issuance, renewal, and revocation. - -Coordinating certificate issuance, renewal, and revocation across multiple operators for a shared O-RU can introduce complexities and potential inconsistencies. - -If a certificate or security update is required for the shared O-RU, synchronizing and coordinating this across multiple operators can be challenging. - -Ensuring that all operators trust each other's certificates and establishing mutual trust in a multi-operator environment can be complex. - -## 4.43 Key Issue #43: NF with an expired certificate - -### 4.43.1 General Description - -Initializing an NF with an expired certificate in an O-RAN system not only risks operational disruptions due to failed secure connections with other network components but also heightens vulnerability to impersonation and man-in-the-middle attacks as attackers can exploit the invalid certificate, especially if network entities are lax in certificate validity checks. - -### 4.43.2 Security Threats - -The NF might not be able to establish secure connections with other components of the network, leading to service disruptions. Other entities might reject connections from the NF due to its expired certificate. - -Expired certificates can be a target for attackers. They might exploit the lack of a valid certificate to launch impersonation or man-in-the-middle attacks, especially if other components in the network aren't stringent about checking certificate validity. - -## 4.44 Key Issue #44: Shared O-RU Trust Anchors - -### 4.44.1 General Description - -Several PKI domains can be identified in any Shared O-RU deployment relying on hierarchical PKI, each with corresponding trust anchor(s). For example, one PKI domain corresponds to the set of Host O-RU controllers and Shared O-RUs enrolled in the Shared O-RU Host PKI. A separate domain is represented by the set of SRO O-RU controller(s) enrolled in the SRO's PKI. The Shared O-RU with interface end-points in the Host PKI domain needs to communicate with SRO O-RU controllers with interfaces for a different PKI domain. To enable secure inter-domain communications, trust anchors are exchanged and installed in the Shared O-RU. - -The list(s) of Shared O-RU trust anchors is to be maintained accurately with respect to the involved PKI domains, including the SRO PKI ones. Trust anchors are typically installed in the Shared O-RU during the start-up procedure and initial certificate enrolment. However, this should not impact the radio. For example, when an SRO joins or leaves the Shared O-RU deployment, established connections (e.g., TLS) between the Shared O-RU and other O-RU controllers are not expected to be impacted immediately. - -The principle of least privilege should be followed not only during the initial installation of trust anchors but also throughout the Shared O-RU lifecycle: the access-scope of a trust anchor (e.g., from one SRO domain) is limited to only those peer entity(ies) of the Shared O-RU that need direct access to the trust anchor material for purposes of certificate validation as part of their role to establish inter-domain communications. - -### 4.44.2 Security Threats - -**Undermined trustworthiness of trust anchors:** failure to secure the Shared O-RU trust anchor management process impacts the level of trust bestowed upon the trust anchors. - -**Unwanted and unauthorized trust relationships:** an excessive number of trust anchors installed in the Shared O-RU can expose the Shared O-RU to unwanted connections (e.g., TLS) from unauthorized domains. For example, failure to remove the TAs corresponding to an SRO that leaves the Shared O-RU deployment, causes the Shared O-RU to be exposed to communications attempts from such SRO. - -# 5 Solutions - -## 5.1 Solution #1: Automation of PSK/Refnum based Certificate Enrolment - -### 5.1.1 Description - -Zero-touch based automation of PSK/Refnum based Certificate Enrolment can be considered, using robust key (re-) generation and secure key (re-)distribution techniques. - -RFC 4210 [i.5] Section 4.2.2.2 Basic Authenticated Scheme talks about Initial Authentication Key (IAK) and reference value-based Certificate Enrolment. In this Technical Report, IAK is referred to as PSK (Pre-shared Key) and reference value is referred to as Refnum. In order to use this mechanism for initial certificate enrolment for CNF/VNFs in O-RAN, when any CNF / VNF is deployed in an O-Cloud environment, operator provisions and distributes a PSK-Refnum pair to each newly deployed CNF/VNF. - -A Zero-touch automation of PSK/Refnum based Certificate Enrolment can be implemented by the operator, using robust key (re-)generation and secure key (re-)distribution techniques. From security point of view, ensure that the automated provisioning and distribution of PSK/Refnum is secure, and PSK/Refnum are provided only to authenticated and validated CNFs/VNFs. Such automations are implementation specific and follow relevant security mechanisms similar to those followed for distributing other system specific configurations. - -### 5.1.2 Impacts on Existing Interfaces and Functionality - -None. - -### 5.1.3 Solution Evaluation - -The solution proposed here relies on operator's implementation for automated provisioning and distribution of PSK/Refnum. The security mechanisms for such provisioning and distributions can be similar to other system specific configurations and no new standardization relevant aspects are proposed by this solution. - -### 5.1.4 Potential Security Requirements - -Any automated PSK/Refnum generation and distribution systems implemented by the operator should ensure that no rogue CNF/VNF can obtain valid PSK/Refnum values. - -## 5.2 Solution #2: Study the use of BRSKI - -### 5.2.1 Description - -Study the use of BRSKI instead of OR along with CMPv2. This solution partially addresses key issue #41. - -In this study, the possible applicability and use of BRSKI in O-RAN for secure bootstrapping of new devices is described based on the understanding of RFC 8995 [i.28]. - -Bootstrapping Remote Secure Key Infrastructure (BRSKI) protocol provides a solution for secure “zero-touch (automated)” bootstrap of new (unconfigured) devices. - -Following are important aspects to be considered for this. - -- The architecture of BRSKI is relevant for “zero-touch” bootstrapping of devices which are “Drop-Shipped” from different vendors, and their ownership needs to be tracked. - -- Drop-Ship: The physical distribution of equipment containing the “factory default” configuration to a final destination. In zero-touch scenarios, there is no staging or pre-configuration during drop-ship. The “zero-touch” aspect is considered from this drop-shipping perspective. - - As stated in RFC 8995 [i.28], BRSKI “is intended to scale to thousands of devices located in hostile environments, such as ISP-provided Customer Premises Equipment (CPE) devices that are drop-shipped to the end user. The situation where an order is fulfilled from a distributed warehouse from a common stock and shipped directly to the target location at the request of a domain owner is explicitly supported.” - - From O-RAN architecture perspective, PNFs need to be deployed in the live network are not drop-shipped to the end user. PNFs are managed and owned by operators and do not have a separate domain owner or an end user. - - Based on above understanding, from O-RAN architecture perspective, no equipment is considered for drop-shipping. -- From wireless networks point of view, IoT devices may be considered for drop-shipping, however, in current architecture, these devices are not considered to be managed by the telecom network. Hence, using BRSKI for IoT devices can be considered as not applicable from O-RAN point of view. -- RFC 8572 [i.31] describes Secure Zero Touch Provisioning as a bootstrapping strategy enabling devices to securely obtain bootstrapping data with no installer action beyond physical placement and connecting network and power cables. The techniques described in this RFC enable devices to establish secure NETCONF and/or RESTCONF connections with deployment-specific network management systems. This is more relevant for new PNF deployments which require to connect to the operator’s NMS using NETCONF connections. Hence, this RFC 8572 [i.31] can be more relevant for O-RAN and can be considered for live network deployments by operators. -- For devices that intend to become part of an ANI [i.RFC 8993 [i.29]] that includes an Autonomic Control Plane [i.RFC 8994 [i.30]], the BRSKI protocol MUST be implemented. The ACP is normally constructed on a hop-by-hop basis. Therefore, many interactions in the ANI are based on the ANI adjacency table. - - Deployment of an O-RAN network does not require a hop-by-hop network construction using ACP. PNFs can be deployed independently and secure communications with PNFs can be established after initial certificate enrolment using CMPv2. Datacenters hosting CNFs/VNFs also do not require automatic hop-by-hop construction. Considering these aspects, it is understood that O-RAN does not consider any devices or equipment intending to become a part of the ANI, and hence does not mandatorily need usage of BRSKI. -- BRSKI terms new devices as “pledges” and these new devices communicate with a “registrar” for bootstrapping. Bootstrapping is complete when the cryptographic identity of the new key infrastructure is successfully deployed to the device. The established secure connection can be used to deploy a locally issued certificate to the device as well. - - Using CMPv2 new NFs connect to Registration Authority (RA) for initial enrolment. After this initial enrolment, the NF gets Operator’s certificates which it can use for secure communications. - - Conceptually, the logical flow is similar between CMPv2 and BRSKI. The main difference is with respect to the applicability of BRSKI which is for drop-shipped devices and is mandatory for any devices intending to become a part of the ANI. - - CMPv2 based solutions, viz. solution #5 and solution #10 described in this TR provide the required support for initial certificate enrolment of newly deployed PNFs, and are sufficient to address the bootstrapping of PNFs. - -### 5.2.2 Impacts on Existing Interfaces and Functionality - -None. - -### 5.2.3 Solution Evaluation - -Considering the study described above, usage of BRSKI is not applicable for any PNF/CNF/VNF used in O-RAN, specifically because BRSKI is relevant for drop-shipped devices intending to be part of ANI. From O-RAN point of view, none of the devices are drop-shipped and not considered to be part of ANI. BRSKI may be applicable for IoT devices, but these are not managed by telecom networks. - -Also, there is no specific reason or requirement to replace CMPv2 with BRSKI. CMPv2 provides the required protocols for automated certificate management and there are no additional benefits seen by using BRSKI. Moreover, known techniques like SZTP [i.31] which are more relevant for O-RAN, enable non-technical personnel to bring up devices in remote locations without the need for an operator input. - -Moreover, BRSKI is considered mandatory for networks deployed using ANI. However, none of the O-RAN components including PNFs and data-centers hosting the CNFs/VNFs require hop-by-hop construction using ACP. Therefore, BRSKI is not mandatory for O-RAN deployments. - -### 5.2.4 Potential Security Requirements - -None. - -## 5.3 Solution #3: Study the use of EST - -### 5.3.1 Description - -Enrolment over Secure Transport (EST) [i.32] defines a lightweight and straightforward protocol for managing certificate provisioning and enrolment in Public Key Infrastructure (PKI) environments. It focuses on certificate enrolment, and renewal while ensuring the security and integrity of the process by utilizing secure transport protocols like HTTPS. The EST service is located between a Certification Authority (CA) and a client. - -The EST clients and server are both equipped with essential information to establish mutual authentication and authorization. The initialization data may consist of shared secrets, network service names, locations (e.g., Uniform Resource Identifier (URI) [i.39]), and trust anchor information. This data forms the foundation for secure communication and access control between the EST components. - -This solution addresses Key issue 37 for defining a lightweight solution for certificate management using simple PKI message types as defined in RFC 7030 [i.32] over secured transport for certificate enrolment, and renewal. Revocation requests are supported via the /fullcmc interface using the Revocation Request Control defined in clause 6.11 of RFC 5272 [i.35]. This procedure allows certified end entities to make requests for the revocation of certificates. The retrieval of certificate revocation status can be performed using OCSP [i.26] and OCSP stapling [i.17]. - -EST Extensions as defined in RFC 8295[i.34] adds /crls interface to support CRL distribution. The /crls path component allows servers to distribute CRLs while clients retrieve their certificate(s) and CA certificate(s) as well as peer certificates. Client's request CRLs with an HTTP GET [i.38], using an operation path of "/crls". "The CRL response and its handling follow the same procedures outlined in clause 4.1.3 of [i.32], with one or more CRLs returned in the CRL-only message. - -#### 5.3.1.1 Certificate-less TLS Authentication - -The steps below document the initial enrolment procedure as per clause 3.3.3 of EST [i.RFC 7030 [i.32]]. Certificate-less Mutual Authentication defines a scenario where the client and server do not have certificates or trust anchors to perform mutual authentication. In such cases, TLS-SRP Transport Layer Security-Secure Remote Password (TLS-SRP) can be used, where username and password are pre-configured. TLS-SRP is based on zero-knowledge protocol which provides strong protection against password guessing and eavesdropping and is resistant to dictionary attacks. - -The outlined message flow shows the EST Protocol for enrolment using https. The mutual authentication while establishing the https session is done using the TLS-SRP credentials. - -- a. Operator CA Server information (Example - FQDN/IP, Port, TLS-SRP username and password) is to be configured in NE. -- b. TLS-SRP user credentials is created in the EST Server for enrolment requests. -- c. TLS connection is established based on TLS-SRP [i.29]. -- d. NE initiates the EST CA Certification procedure to download the Operator CA (Root) certificates (or trust chain). -- e. Server responds with a configured operator CA (Root) certificate in response to the CA Certification procedure request from a NE. -- f. NE forms the Certificate Signing Request (CSR) and initiates EST simple enrolment procedure to download the Operator Device Certificate. -- g. Server responds with a Device certificate signed by Operator CA in response to the simple enrolment request from an NE. - -![Sequence diagram for Certificate-less TLS Authentication. It shows two participants: NE or NF (EST Client) and EST Server (CA). The process starts with 'Establish TLS-SRP based connection for https'. A note indicates 'No Explicit or Implicit TA is configured, Certificate-Less Mutual Authentication[TLS-SRP]'. Step 1.a shows pre-configuration of TLS-SRP Username, Password, and EST Server FQDN on the client. Step 1.b shows pre-configuration of Username and Password on the server. A note indicates 'TLS connection established using SRP as defined in RFC 5054[29]'. The next section is 'EST enrolment using https'. Step 2: EST client uses /cacerts response to establish TLS connection. Step 3: EST server responds with cacerts. Step 4: EST client requests a certificate via /simpleenroll. Step 5: EST server issues a signed certificate.](e151d3468319b81f042ca232c4d82e4b_img.jpg) - -Sequence diagram for Certificate-less TLS Authentication. It shows two participants: NE or NF (EST Client) and EST Server (CA). The process starts with 'Establish TLS-SRP based connection for https'. A note indicates 'No Explicit or Implicit TA is configured, Certificate-Less Mutual Authentication[TLS-SRP]'. Step 1.a shows pre-configuration of TLS-SRP Username, Password, and EST Server FQDN on the client. Step 1.b shows pre-configuration of Username and Password on the server. A note indicates 'TLS connection established using SRP as defined in RFC 5054[29]'. The next section is 'EST enrolment using https'. Step 2: EST client uses /cacerts response to establish TLS connection. Step 3: EST server responds with cacerts. Step 4: EST client requests a certificate via /simpleenroll. Step 5: EST server issues a signed certificate. - -Figure 5-1: Certificate-less TLS Authentication - -#### 5.3.1.2 Certificate TLS Authentication - -The steps below document the initial enrolment procedure as per clause 3.3.1 of EST [i.RFC 7030 [i.32]]. The EST client authenticates the EST server using the certificate validation as defined in RFC 5280 [i.13]. The authorization method for the EST server depends on whether the EST Client is configured with an Explicit TA Database as per clause 3.6.1 of RFC 7030 [i.32] or an Implicit TA Database as per clause 3.6.2 of RFC 7030 [i.32]. In the below scenario, an explicit TA database has been configured for mutual authentication between EST Client and Server. - -The outlined message flow shows the EST Protocol for enrolment using https. The mutual authentication while establishing https session is done using the certificates. - -- a. NE's Vendor certificate and Private Keys are pre-installed. -- b. Vendor CA Certificate (or trust chain) is installed in the Operator CA server trust store. -- c. NE has received the Operator CA server details (Example - FQDN/IP, Port, Operator CA certificate). -- d. TLS connection is established based on the Explicit TA database. -- e. NE forms the CSR and initiate EST simple enrolment procedure to download the Operator Device Certificate. -- f. Server validates the client's identity and responds with a Device certificate signed by Operator CA in response to the simple enrolment request from a NE. - -![Sequence diagram for Certificate-based TLS Authentication. Participants: NE or NF (EST Client) and EST Server (CA). Section: 'Establish TLS connection based on Explicit TA database for https'. Note: 'Explicit TA is configured, Certificate Based Mutual Authentication is used'. Step 1: NE's Vendor certificate and private key are pre-installed. Step 2: Vendor CA certificate are pre-configured on the server. Step 3: EST server's FQDN and CA certificates are pre-configured on the client. Note: 'TLS connection is established based on the Explicit TA database as per RFC7030[28]'. Section: 'EST enrolment using https'. Step 4: Generate CSR. Step 5: Send the CSR to the EST server via /simpleenroll. Step 6: Validate the client's identity and authorization status. Step 7: EST server issues a signed certificate.](132cff7e872feb31f629703959beddd7_img.jpg) - -Sequence diagram for Certificate-based TLS Authentication. Participants: NE or NF (EST Client) and EST Server (CA). Section: 'Establish TLS connection based on Explicit TA database for https'. Note: 'Explicit TA is configured, Certificate Based Mutual Authentication is used'. Step 1: NE's Vendor certificate and private key are pre-installed. Step 2: Vendor CA certificate are pre-configured on the server. Step 3: EST server's FQDN and CA certificates are pre-configured on the client. Note: 'TLS connection is established based on the Explicit TA database as per RFC7030[28]'. Section: 'EST enrolment using https'. Step 4: Generate CSR. Step 5: Send the CSR to the EST server via /simpleenroll. Step 6: Validate the client's identity and authorization status. Step 7: EST server issues a signed certificate. - -Figure 5-2: Certificate-based TLS Authentication. - -### 5.3.2 Impacts on Existing Interfaces and Functionality - -Impacts on Existing Interfaces and Functionality are FFS. - -### 5.3.3 Solution Evaluation - -The choice for selecting a certificate management protocol could depend upon the PKI environment. EST provides a lightweight solution in case the environment does not govern a complex PKI infrastructure and features. The EST server authenticates and authorizes the EST client based on the method described in clause 4.3.1.1 and 4.3.1.2. The recommended method for establishing TLS secured http connection between EST client and server should be based on certificate based TLS authentication. EST could also be used between the client and RA and co-exist with CMPv2. - -#### Benefits: - -- Lightweight Protocol with simple PKI messaging types. -- Secured Transport using HTTPS. -- Source Code is open-sourced. -- Efficient and well-suited for edge deployments where the resources are constrained. -- Supports Elliptic Curve Cryptography. - -#### Limitations: - -- In scenarios where a client doesn't have proper configuration or trust anchors, manual intervention by a human user is required to verify CA certificate information. - -### 5.3.4 Potential Security Requirements - -An O-RAN element that requires digital certificates should support the Enrolment over Secure Transport (EST) to securely provision RSA or ECC certificates over HTTPS, as described in RFC 7030. EST is a lightweight certificate management protocol that allows enrolment/renewal of digital certificates over a secured https and support all the below conditions. - -- a. An O-RAN element which has not been bootstrapped with digital certificates. -- b. An O-RAN element using vendor certificates but missing trust anchor database or CA information not being passed by the DHCP options. - -## 5.4 Solution #4: Study the use of ACME - -### 5.4.1 Description - -Study the use of ACME instead of OR along with CMPv2. - -O-Cloud hosts O-RAN functions such as O-DU, O-CU, Near-RT RIC platform services, xApps, and O-Cloud control plane components. (e.g., Kubernetes control plane components). - -The CMPv2 protocol can be used to provision certificates to O-DU, O-CU functions. However, for cloud-native applications (such as xApps), Near-RT RIC platform components, and O-Cloud control plane components deployed as pods, ACME offers a solution for automated certificate management. - -Manually maintaining the certificates for cloud-native applications and O-Cloud control plane components present challenges: - -- Large number of TLS certificates to manage across Kubernetes clusters and namespaces. -- Manually replace certificates every time when they expire. -- Certificates expire at different times; service outages may result if certificates are not renewed in time. -- Updating Kubernetes secrets manually is error-prone. -- Manual certificate management is time-consuming and error-prone. - -- The risk-mitigating practice of rotate keys and certificates frequently aggravates the onerousness of manual certificate management. - -#### 5.4.1.1 Overview of ACME - -ACME is a certificate management protocol defined in RFC 8555 [i.42]. A popular use of ACME is to request certificate from Let's Encrypt, a free public CA. The protocol is also supported by some commercial CAs. - -The ACME builds on several existing technologies, most of which are commonly used in web API designs: - -- HTTPS (transport) -- JSON (message format) -- TLS server authentication (authentication of messages from server) -- JWS (authentication of messages from clients) -- PKCS #10 (CSR) - -ACME supports several certificate management use cases: - -- requisition (a.k.a. enrolment) -- certificate revocation -- subject identifier validation - -In ACME, a client needs to have an account to be able to use the service of an ACME server. A client account is identified with an account key pair. Among certificate enrolment protocols, ACME is unusual in that it has provisions for extensible, automated in-protocol processes for validating identifiers (e.g. DNS domain) of certificate subjects. This allows ACME accounts to be set up by clients without pre-established credentials, as a client's eligibility to receive a certificate with a particular subject identifier not based on trust of the client, but independent validation of the client's control of the subject identifier. RFC 8738 [i.43] extends ACME to issue certificates with IP address identifiers using http-01 and tls-alpn-01 challenges. Additional extensions and proposed extensions can be found at . - -ACME has mechanisms for integrating with external systems. "External account binding" allows an ACME account to be tied to an account external (using a MAC-authenticated credential), and allows authorization to be performed via the external account. ACME also supports an operation called preauthorization, which allows a client to request authorization for a subject identifier outside of the context of a certificate request sequence. - -In ACME, a certificate request sequence involves the creation and update of several types of objects: - -- order -- authorization -- challenge - -Messages from the client are authenticated using JWS signed with the client's account private key. To protect against replay attacks, requests from the client contain a replay-nonce. Some of the request-response exchanges are asynchronous in the general case. In those exchanges, after receiving an immediate response from the server, the client may need to poll the server periodically until a status change has occurred. - -#### 5.4.1.2 ACME Certificate Enrolment Flow - -![Sequence diagram showing the ACME Certificate Enrolment Flow between an ACME Client, ACME Server, and Operator CA.](cfaeb2934fffcb1f4690ab7de835c2e0_img.jpg) - -``` - -sequenceDiagram - participant ACME Client - participant ACME Server - participant Operator CA - Note right of ACME Client: ... - ACME Client->>ACME Server: Submit order - ACME Server-->>ACME Client: Issue challenge (e.g. http-01, dns-01) - Note right of ACME Client: ... - ACME Client->>ACME Server: Provision resources to fulfill challenge - ACME Server-->>ACME Client: Validate challenge - ACME Server-->>ACME Client: Issue certificate - Note right of ACME Client: ... - ACME Client->>ACME Server: (Renew certificate before expiry) - Note right of ACME Server: ... - ACME Server->>Operator CA: - Operator CA-->>ACME Server: - -``` - -Sequence diagram showing the ACME Certificate Enrolment Flow between an ACME Client, ACME Server, and Operator CA. - -Figure 5-3: A simplified depiction of the workings of ACME - -In ACME, message exchanges happen over HTTPS. The ACME specification defines a way of using an HTTP POST request to perform what an HTTP GET request usually does, but with JWS message authentication. The usage is called POST-as-GET in the protocol specification. - -A typical certificate request sequence in ACME involves the follow steps: - -1. **Order creation:** The client performs an HTTP POST to submit a request; the ACME server creates and returns an order object. -2. **Challenge retrieval:** The client uses POST-as-GET request(s) to retrieve the authorization objects referenced in the order object. In the general case, multiple authorization objects may be involved. -3. **Challenge fulfillment:** For each of the authorization object(s), the client selects one (of possibly multiple) challenge in the authorization object, takes action to fulfill the challenge, and POSTs to a URL to notify the ACME server of the challenge selected and it has been fulfilled. -4. **Challenge validation:** The ACME server verifies that the client has fulfilled the indicated challenges, e.g. by performing an HTTP request or a DNS query. This validation step may take a variable amount of time. -5. **Polling for status change:** The client performs POST-as-GET requests to check the status of the authorization object(s), until their status(es) are no longer “pending”. -6. **Order finalization:** The client POSTs to a URL contained in the order object, including a CSR in the request. There may be a variable amount of delay before the ACME server issues a certificate. -7. **Polling for status change:** The client performs POST-as-GET requests to check the status of the order object(s), until its status is “ready”. -8. **Certificate download:** The client performs a POST-as-GET to download a newly-issued certificate from a URL in the updated order object. - -#### 5.4.1.3 Integration with Kubernetes via cert-manager - -cert-manager (name spelled in all lowercase) is an add-on to Kubernetes (K8s). As of August 2022, cert-manager is a CNCF project of maturity level “sandbox” (in a progression of three maturity levels: sandbox, incubating, and graduated.) cert-manager can generate key pairs and request certificates from CAs and provision the key pairs and certificates to containerized applications, in a Kubernetes construct called secrets. cert-manager can be integrated with CAs of several types. Using a built-in ACME client, cert-manager can request certificates from CAs that support an ACME interface. cert-manager can also monitor certificates it manages and automatically requests replacements for certificates before they expire. - -#### 5.4.1.4 Remarks - -Compared with other certificate management protocols, ACME is rather “chatty” in that a typical certificate request sequence involves a relatively large number of request-response exchanges. - -Although the pre-integration with ACME makes cert-manager an attractive certificate management option for containerized applications orchestrated using Kubernetes, private keys generated by cert-manager are only protected by access control. Private keys are exposed in plaintext form to anyone who has or managed to obtain privileged access (e.g., superuser access) inside a container. - -### 5.4.2 Impacts on Existing Interfaces and Functionality - -Impacts on Existing Interfaces and Functionality are FFS. - -### 5.4.3 Solution Evaluation - -Addressing Key Issue #37, ACME provides a solution for PKI certificate management protocol and procedures. In contrast to CMPv2, ACME is a dedicated protocol for certificate provisioning that is based on easy-to-implement REST interfaces and the HTTP protocol. It is therefore easier to implement in resource-restricted client implementations as well as in the certificate authority (trust center). CMPv2, however, is a very complex binary (ASN1-based) protocol with a feature set that well exceeds what is needed for certificate provisioning. - -Addressing Key Issue #38, ACME provides a solution for PKI certificate management protocol and procedures. Because of its dedication to certificate provisioning and the use of RESTful APIs it is easier to understand for developers leading potentially to a better conformance and therefore higher interoperability of ACME implementations. For CMPv2, however, variances in implementations may lead to more interoperability problems due its higher complexity and the need to observe a large number of specifications with regard to its deployment in an O-RAN context (ie. original RFCs, 3GPP profiles, potentially O-RAN Alliance profiles). - -## 5.5 Solution #5: Initial Certificate Enrolment of PNFs using vendor certificates - -### 5.5.1 Description - -This solution addresses Key Issue #3 and Key Issue #4. - -When a new physical network function (PNF) gets deployed in a network, it can obtain operator's CA signed certificate in order to establish secure communications with other network functions. An operator may prefer using vendor-signed certificates for automated initial certificate enrolment. This solution proposes the procedure to use vendor-signed certificates for initial certificate enrolment of PNFs. This solution proposal refers to vendor certificate-based initial registration and certificate enrolment as described in 3GPP TS 33.310 [i.2] clause 9 "Certificate enrolment for base stations". - -The solution is summarized as below: - -#### Pre-conditions: - -When a PNF is deployed in the network, for initial certificate enrolment, it requires vendor-signed certificate and the related private key, and operator's CA certificate. - -- Also, PNF needs to be configured with the URL/IP address for RA/CA. - - As described in 3GPP TS 28.315 [i.44] clause 5.3, operators may deploy their management infrastructure in a manner that either IP address or FQDN of RA/CA is known to the PNF. - - The plug-and-connect concepts as described in 3GPP TS 28.314 [i.45] and 3GPP TS 28.315 [i.44] should be followed. -- CA/RA has the vendor's root certificate pre-provisioned. - - 3GPP TS 28.314 [i.45] clause 4.1.3.1 should be followed for root certificate acquisition. - - RA is an optional entity, and the registration function can be directly implemented with the CA component. RFC 4210 [i.5] (for CMPv2) describes possible reasons for the presence of RA in Appendix A of the RFC. - -#### Initial Certificate Enrolment: - -- 3GPP TS 33.310 [i.2] Annex G presents an example CMPv2 message flow for initial enrolment, and this should be followed. -- When PNFs have connectivity with CA/RA, and above pre-conditions are satisfied, vendor-signed certificate gets used to perform initial certificate enrolment. -- PNF presents the vendor-signed certificate to CA/RA during CMPv2: Initialization Request. CA/RA having vendor's root certificate can authenticate this request and, the CMPv2 protocol can be followed, as defined in RFC 4210 [i.5], to establish the trust. - -This trust establishment allows newly deployed PNFs to obtain operator CA issued certificate along with the chain of trust. - -### 5.5.2 Impacts on Existing Interfaces and Functionality - -An O-RAN PNF requiring a PKI certificate will need to support CMPv2 and will need a pre-installed vendor certificate. Offline interfaces will be required to configure the URL/IP address of the RA/CA in the PNF. - -Offline interfaces will also be required to pre-provision vendor's trust anchor in RA/CA. - -Pre-condition: In order to facilitate vendor certificate-based initial enrolment of PNFs, vendor's trust anchor is pre-installed in operator's RA/CA. - -### 5.5.3 Solution Evaluation - -This solution addresses Key Issue #3 and Key Issue #4. - -### 5.5.4 Potential Security Requirements - -In order to facilitate vendor certificate-based initial enrolment of PNFs, vendors should pre-install vendor-signed certificates in PNFs. - -In order to facilitate vendor certificate-based initial enrolment of PNFs, operators should pre-configure the FQDN/IP address of RA/CA in PNFs. - -## 5.6 Solution #6: Certificate management and secure storage of Application private keys within O-Cloud - -### 5.6.1 Description - -The O-Cloud platform should have a certificate manager (e.g., "cert-manager" for Kubernetes [[i.https://cert-manager.io/](https://cert-manager.io/)]) that supports secure protocols such as ACME and (CMPv2 is not yet implemented), which can be used to obtain certificates from other sources. This certificate manager is used to inject certificates in O-RAN Applications. In order to do that, the certificate manager should use a trusted CA to sign the certificate request. - -ACME or CMPv2 protocols support the integration with a PKI-as-a-Service to obtain certificates from any PKI, whether public or private, that support security modules like HSMs. This enables secure, automatic issuance of a unique, trusted identity certificate for every application and O-Cloud component. - -Certificates and private keys should be stored within the O-Cloud platform as secrets (e.g., native k8s Secrets Objects). Private keys should be protected in terms of confidentiality and integrity. - -During runtime, if there is a need for PKI migration, where the root/sub CA certificates used to sign the certificates provided to ORAN Apps need to be updated, the O-Cloud platform and certificate manager should perform following steps: - -- Obtain the updated root/sub CA certificates and store within the O-Cloud platform -- Create new instances of running Apps (CNFs/VNFs) which are expected to be impacted by this PKI migration, but do not activate them yet - - These new instances should be able to obtain newly signed certificates with updated root/sub CA -- Subsequently, the newly created instances can be activated using newly signed certificates -- After successfully completing above steps, deactivate and delete CNFs/VNFs running with old certificates. CNFs/VNFs deletion process includes deletion of all certificates and associated private keys. -- If all NFs in a network slice are impacted, a new network slice can be created with new NFs using certificates signed with new root/sub CAs, and then, once new slice takes over the work, existing slice with older certificates can be deactivated and deleted. -- Above mentioned steps can be performed in a maintenance window, or, when the load on the system is expected to be low and no priority users or emergency calls are ongoing. - -- It is recommended to maintain both old certificate and the new root/intermediate CA certificate for an overlapping period. This overlapping period allows services to gradually transition to new certs while maintaining trust and service continuity. Once all services updated with new certificates, old certificates can be retired/deleted. - -### 5.6.2 Generation of key pair and modes of operation - -The ETSI GR NFV-SEC 005 [i.11] clause 8 is describing the key-generation and distribution for NFV certificate lifecycle management, specifically three different concepts are shown. - -In this clause the different key-generation concepts have been taken as basis for further development of the key-generation and certificate enrolment. - -The following Figure 5-4 is depicting the system level view for the secure storage and certificate management. - -![Figure 5-4: Secure Storage and Certificate Management Architecture (System Level View). The diagram shows three levels: Software Level (O-RAN APP/VNF/CNF (AVC)), Platform Level (Virtualisation Platform (VP) containing Monitor, Secure Storage Resource Manager (SSRM), and Certificate Manager), and Infrastructure Level (SW Based Secure Storage (Option A: SW-Based) and HW Based Secure Storage (e.g. HSM, TPM) (Option B: HW-Based)). External components include RA / CA, Security Module (e.g. HSM), and MANO / CISM. Arrows indicate data flow and API interactions (Functional API, Secure Storage API). A legend defines key types: Private Key (red), Public Key (blue), Root CA Private Key (black), and Root CA Public Key (purple).](a93de4c3f80bd4a972ab65510b09b68d_img.jpg) - -Figure 5-4: Secure Storage and Certificate Management Architecture (System Level View). The diagram shows three levels: Software Level (O-RAN APP/VNF/CNF (AVC)), Platform Level (Virtualisation Platform (VP) containing Monitor, Secure Storage Resource Manager (SSRM), and Certificate Manager), and Infrastructure Level (SW Based Secure Storage (Option A: SW-Based) and HW Based Secure Storage (e.g. HSM, TPM) (Option B: HW-Based)). External components include RA / CA, Security Module (e.g. HSM), and MANO / CISM. Arrows indicate data flow and API interactions (Functional API, Secure Storage API). A legend defines key types: Private Key (red), Public Key (blue), Root CA Private Key (black), and Root CA Public Key (purple). - -Figure 5-4: Secure Storage and Certificate Management Architecture (System Level View) - -The following is applicable: - -- The Virtualisation Platform (VP) includes the Secure Storage Resource Manager (SSRM). The SSRM is managing the interface to either the SW based or HW based secure storage solution. The VM/Container is owning a more 'internal' interface to SSRM (which is like a primitive between protocol stacks). The SSRM is providing service for key-pair generation and provision of the public key, is providing digital signatures, is providing key-management, etc. -- The underlying HW based secure storage can be either implemented by a TPM device (HW or SW) or can be by a (physically) connected HSM module. -- Any Application or certificate manager have access to SSRM service. -- The management and orchestration system (e.g., MANO for VM [i.11], CIS/CISM for Container [i.12]) is receiving the operator public key on request for distribution to other Applications. -- The Operator RA/CA has connected its own HSM module which is creating the private key for signing requests. - -#### 5.6.2.1 Generation of the key pair by the Virtualization Platform - -In this mode, the key pair is generated by the SSRM following the request of the certificate manager. The certificate manager could automatically ensure certificates are valid and up to date and attempt to renew certificates at a configured time before expiry. - -The following steps are followed to request and store certificates: - -1. An Application creates and sends a certificate resource request to the certificate manager -2. The certificate manager requests from the SSRM the generation of a key pair and sends a Certificate Signing Request (CSR) to the CA -3. The CA signs the certificate with its own private key and returns it to the certificate manager. -4. The certificate manager stores the signed certificate in the secret storage volume with the O-Cloud platform (e.g., in etcd). -5. Authenticated and authorized Application can read the signed certificate from the secret storage volume for use and for digital signing service is (direct) requesting digital signature from the SSRM by providing the digest for signing. - -![Diagram of key-generation by the Virtualisation Platform showing three levels: Software Level (O-RAN APP/VNF/CNF (AVC)), Platform Level (Virtualisation Platform (VP) containing Monitor, Secure Storage Resource Manager (SSRM), and Certificate Manager), and Infrastructure Level (SW Based Secure Storage and HW Based Secure Storage). External components include RA / CA, Security Module (e.g. HSM), and MANO / CISM. A legend defines key types: Private Key (red), Public Key (blue), Root CA Private Key (grey), and Root CA Public Key (purple).](683f755e8456c884716de4fce48c7e63_img.jpg) - -The diagram illustrates the key-generation process across three layers: - - -- Software Level:** Contains the O-RAN APP/VNF/CNF (AVC) which has a public key icon. -- Platform Level:** Contains the Virtualisation Platform (VP). Inside the VP are a Monitor, a Secure Storage Resource Manager (SSRM), and a Certificate Manager. The AVC connects to the Certificate Manager via a 'Secure Storage API'. The Certificate Manager connects to the RA / CA and the MANO / CISM. The SSRM connects to the Monitor and the secure storage options. -- Infrastructure Level:** Contains two options for secure storage: - - Option A: SW-Based:** 'SW Based Secure Storage' with 'Shared Storage' and a private key icon. - - Option B: HW-Based:** 'HW Based Secure Storage (e.g. HSM, TPM)' with 'Shared Storage' and a private key icon. - - External components include: - - -- RA / CA:** Connected to the Certificate Manager and the Security Module (e.g. HSM). -- Security Module (e.g. HSM):** Contains Root CA Private and Public keys. -- MANO / CISM:** Connected to the Certificate Manager and contains a public key icon. - - A legend on the right defines the key icons: - - -- Private Key (red key icon) -- Public Key (blue key icon) -- Root CA Private Key (grey key icon) -- Root CA Public Key (purple key icon) - -Diagram of key-generation by the Virtualisation Platform showing three levels: Software Level (O-RAN APP/VNF/CNF (AVC)), Platform Level (Virtualisation Platform (VP) containing Monitor, Secure Storage Resource Manager (SSRM), and Certificate Manager), and Infrastructure Level (SW Based Secure Storage and HW Based Secure Storage). External components include RA / CA, Security Module (e.g. HSM), and MANO / CISM. A legend defines key types: Private Key (red), Public Key (blue), Root CA Private Key (grey), and Root CA Public Key (purple). - -Figure 5-5: Key-generation by the Virtualisation Platform - -#### 5.6.2.2 Generation of the key pair by Trusted Application - -In this mode, the key pair is generated by the Trusted (i.e., authenticated, and authorized) Application. In this mode, the life cycle of the certificate is to be managed by the Application and it is the responsibility of the Application to renew the certificates before they expire. - -The following steps are followed to request and store certificates: - -1. Trusted Application generates a key pair. -2. The Trusted Application sends the public key back to the certificate manager. The certificate manager sends the CSR to the CA for signing. -3. The CA signs the certificate with its own private key and returns it to the certificate manager. -4. The certificate manager returns the signed certificate. -5. The trusted Application requests the SSRM to store its private key with the signed certificate in the secure storage. - -![Diagram of Key-generation by the Trusted Application across Software, Platform, and Infrastructure levels. It shows components like O-RAN APP/VNF/CNF (AVC), Trusted AVC, RA/CA, Security Module (e.g. HSM), Functional API, Secure Storage API, Virtualisation Platform (VP), Certificate Manager, MANO / CISM, Monitor, Secure Storage Resource Manager (SSRM), SW Based Secure Storage, and HW Based Secure Storage. A legend defines key types: Private Key, Public Key, Root CA Private Key, and Root CA Public Key.](ec3647789b5c38fb686f2a0833324e79_img.jpg) - -The diagram illustrates the key-generation process by a Trusted Application across three levels: Software Level, Platform Level, and Infrastructure Level. - -- Software Level:** Contains O-RAN APP/VNF/CNF (AVC) and Trusted AVC. The Trusted AVC has a Private Key (red) and a Public Key (blue). -- Platform Level:** Contains Functional API, Secure Storage API, Virtualisation Platform (VP), Certificate Manager, MANO / CISM, and Monitor. The Certificate Manager is connected to the RA / CA and the MANO / CISM. -- Infrastructure Level:** Contains SW Based Secure Storage (Option A: SW-Based) and HW Based Secure Storage (e.g. HSM, TPM) (Option B: HW-Based). Both options have Shared Storage. - -**Connections:** - -- The O-RAN APP/VNF/CNF (AVC) connects to the Functional API. -- The Trusted AVC connects to the Certificate Manager. -- The RA / CA connects to the Security Module (e.g. HSM) and the Certificate Manager. -- The Security Module (e.g. HSM) connects to the RA / CA. -- The Certificate Manager connects to the MANO / CISM and the Secure Storage Resource Manager (SSRM). -- The MANO / CISM connects to the Certificate Manager. -- The Monitor connects to the SSRM. -- The SSRM connects to the SW Based Secure Storage and the HW Based Secure Storage. - -**Legend:** - -- Private Key (Red Key) -- Public Key (Blue Key) -- Root CA Private Key (Black Key) -- Root CA Public Key (Purple Key) - -Diagram of Key-generation by the Trusted Application across Software, Platform, and Infrastructure levels. It shows components like O-RAN APP/VNF/CNF (AVC), Trusted AVC, RA/CA, Security Module (e.g. HSM), Functional API, Secure Storage API, Virtualisation Platform (VP), Certificate Manager, MANO / CISM, Monitor, Secure Storage Resource Manager (SSRM), SW Based Secure Storage, and HW Based Secure Storage. A legend defines key types: Private Key, Public Key, Root CA Private Key, and Root CA Public Key. - -Figure 5-6: Key-generation by the Trusted Application - -#### 5.6.2.3 Generation of the key pair by a HW security module (e.g., HSM, TPM) - -In this mode, the key pair is generated by the connected HW security module (e.g., HSM, TPM). The security module is connected to the virtualization platform via the SSRM, which is then used for generation of a key pair. - -In this mode, the life cycle of the certificate is to be managed by the Application and it is the responsibility of the Application to renew the certificates before they expire. - -The following steps are followed to request and store certificates: - -1. An Application creates and sends a certificate resource request to the certificate manager -2. The certificate manager is creating a key-pair generation request to the security module. The security module is creating the key-pair and is sending the public key back to the certificate manager. The certificate manager sends the CSR to the CA for signing. -3. The CA signs the certificate with its own private key and returns it to the certificate manager. -4. The certificate manager returns the signed certificate. -5. The security module stores the private key, and the signed certificate is going to the Application. - -![Figure 5-7: Key-generation by the Secure Module (e.g., HSM, TPM). This architectural diagram illustrates the flow of keys and data across three levels: Software Level, Platform Level, and Infrastructure Level. At the Software Level, an O-RAN APP/VNF/CNF (AVC) containing a Trusted AVC is shown. It connects via a Functional API and a Secure Storage API to the Platform Level. The Platform Level contains a Virtualisation Platform (VP) with a Monitor, a Certificate Manager, and a Secure Storage Resource Manager (SSRM). The Certificate Manager is connected to an RA / CA, which in turn connects to a Security Module (e.g., HSM). The SSRM is connected to a MANO / CISM. The Infrastructure Level includes two options for secure storage: Option A (SW-Based) and Option B (HW-Based, e.g., HSM, TPM). Option B is connected to the SSRM and contains Shared Storage and a Secure Module. A legend defines the key types: Private Key (red), Public Key (blue), Root CA Private Key (black), and Root CA Public Key (purple). Arrows indicate the flow of these keys between the various components across the levels.](01e00200a536673d6cd0e6d8705047a0_img.jpg) - -Figure 5-7: Key-generation by the Secure Module (e.g., HSM, TPM). This architectural diagram illustrates the flow of keys and data across three levels: Software Level, Platform Level, and Infrastructure Level. At the Software Level, an O-RAN APP/VNF/CNF (AVC) containing a Trusted AVC is shown. It connects via a Functional API and a Secure Storage API to the Platform Level. The Platform Level contains a Virtualisation Platform (VP) with a Monitor, a Certificate Manager, and a Secure Storage Resource Manager (SSRM). The Certificate Manager is connected to an RA / CA, which in turn connects to a Security Module (e.g., HSM). The SSRM is connected to a MANO / CISM. The Infrastructure Level includes two options for secure storage: Option A (SW-Based) and Option B (HW-Based, e.g., HSM, TPM). Option B is connected to the SSRM and contains Shared Storage and a Secure Module. A legend defines the key types: Private Key (red), Public Key (blue), Root CA Private Key (black), and Root CA Public Key (purple). Arrows indicate the flow of these keys between the various components across the levels. - -Figure 5-7: Key-generation by the Secure Module (e.g., HSM, TPM) - -### 5.6.3 Secure key and file storage - -Encryption/decryption functionality is provided by the management platform and handled by the CPU’s accelerated instruction, providing accelerated data at rest for both AES encryption and decryption. The main assets involved in the encryption/decryption of private keys are the key encryption key (KEK), the disk encryption key (DEK) and/or the secret encryption key (SEK). Different solutions for protecting those keys in terms of integrity and confidentiality are currently used. Such potential solutions include: - -#### 5.6.3.1 Secure Key and File Storage Mechanisms – Architecture Framework - -The main purpose for implementing a secure storage is to guarantee the secrecy of a private key (asymmetric cryptography) and/or of a file which might hold sensitive information. The secure storage in this context is a composition of sub-functions which all together are required to provide service to upper layer for a proper secure key and file protection. - -The following Figure 5-8 depicts the overall architecture framework for a secure key and file storage. - -![Figure 5-8: Secure Key and File Storage Architecture Framework (overview). The diagram shows a layered architecture. At the top, the 'Software Level' contains multiple O-RAN APP/VNF/CNF units (#1, #2, ..., #N). These connect via a 'Secure Storage API' to the 'Platform Level', which contains a 'Monitor' and a 'Secure Storage Resource Manager' (SSRM). The SSRM is connected to the 'Infrastructure Level', which offers two options: 'Option A: SW-Based' (SW Based Secure Storage with Shared Storage) and 'Option B: HW-Based' (HW Based Secure Storage like TPM with Shared Storage). The SSRM and Monitor are part of the 'ORAN Normative Specification', while the storage options are part of the 'ORAN Informative Specification'.](8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg) - -Figure 5-8: Secure Key and File Storage Architecture Framework (overview). The diagram shows a layered architecture. At the top, the 'Software Level' contains multiple O-RAN APP/VNF/CNF units (#1, #2, ..., #N). These connect via a 'Secure Storage API' to the 'Platform Level', which contains a 'Monitor' and a 'Secure Storage Resource Manager' (SSRM). The SSRM is connected to the 'Infrastructure Level', which offers two options: 'Option A: SW-Based' (SW Based Secure Storage with Shared Storage) and 'Option B: HW-Based' (HW Based Secure Storage like TPM with Shared Storage). The SSRM and Monitor are part of the 'ORAN Normative Specification', while the storage options are part of the 'ORAN Informative Specification'. - -Figure 5-8: Secure Key and File Storage Architecture Framework (overview) - -The SSRM is providing service to any application, i.e., is creating private-public key pair, is providing digital signing requests on received digests, is returning the digital certificates, etc. Any application is connecting to SSRM via a standardised Secure Storage API (SSAPI). This API is independent of the underlying secure storage mechanism. The storage mechanism can be built up by a single secure storage instance or by multiple secure storage instances. Their management is up to the SSRM. - -The following is applicable: - -- The O-RAN Application is interfaced to the Secure Storage Resource Manager (SSRM) via a Secure Storage API. -- The role of the SSRM is to provide service on secure storage to any Application, and to hide the underlying protection mechanism which can be either SW-based and/or HW-based. The Monitor function belongs to the SSRM and is for tracking purposes or could be used as proxy towards the system O&M. -- The secure storage mechanism could be a SW based approach (e.g., vTPM) and/or HW-based (e.g., TPM, HSM). -- The HW-based solution option is impacting the HW and therefore is belonging to Infrastructure. The SSRM (including the SS API) and the SW-based solution option is belonging to the Platform. The O-RAN Application is belonging to the application SW level. - -#### 5.6.3.2 Scenarios for protecting keys within the secret storage volume - -##### 5.6.3.2.1 Use of TPM (Hardware TPM or vTPM) - -In this solution, two scenarios are possible, among others: - -1. Scenario 1: Private keys are not encrypted individually. All private keys are stored in a disk encrypted by the DEK. DEK is stored in a TPM for automatic decryption at boot. -2. Scenario 2: Private keys could be encrypted individually by SEKS. SEKS are stored in a disk encrypted by the KEK. KEK is stored in a TPM. - -![Figure 5-9: Scenarios for protecting keys within the secret storage volume based on TPM. It contains two sub-diagrams, Scenario 1 and Scenario 2. Scenario 1 shows O-RAN Apps/VNFs/CNFs connected to a Secure Storage Resource Manager, which is connected to a TPM. The TPM has a DEK (yellow key) and the Secure Storage Resource Manager has a Secret storage volume (cylinder) containing Private keys (orange keys). Scenario 2 shows O-RAN Apps/VNFs/CNFs connected to a Secure Storage Resource Manager, which is connected to a TPM. The TPM has a KEK (red key) and the Secure Storage Resource Manager has a Secret storage volume (cylinder) containing Private keys (orange keys) and SEks (blue keys).](fe25bbee6685ab20f50ffc80c3feddd8_img.jpg) - -**Scenario 1** - -O-RAN Apps/VNFs/CNFs → Secure Storage Resource Manager → TPM (DEK) → Secret storage volume (Private keys 1, 2, 3) - -**Scenario 2** - -O-RAN Apps/VNFs/CNFs → Secure Storage Resource Manager → TPM (KEK) → Secret storage volume (Private keys 1, 2, SEks 1, 2) - -Legend: Private keys (orange), DEK (yellow), KEK (red), SEks (blue) - -Figure 5-9: Scenarios for protecting keys within the secret storage volume based on TPM. It contains two sub-diagrams, Scenario 1 and Scenario 2. Scenario 1 shows O-RAN Apps/VNFs/CNFs connected to a Secure Storage Resource Manager, which is connected to a TPM. The TPM has a DEK (yellow key) and the Secure Storage Resource Manager has a Secret storage volume (cylinder) containing Private keys (orange keys). Scenario 2 shows O-RAN Apps/VNFs/CNFs connected to a Secure Storage Resource Manager, which is connected to a TPM. The TPM has a KEK (red key) and the Secure Storage Resource Manager has a Secret storage volume (cylinder) containing Private keys (orange keys) and SEks (blue keys). - -Figure 5-9: Scenarios for protecting keys within the secret storage volume based on TPM - -##### 5.6.3.2.2 Use of KMS server - -There is a specific SEK for each private key. The SEK is used to encrypt the private key and is itself encrypted by the KMS server's KEK. The KMS server may use an HSM for the storage of the KEK and the encryption of SEks. The HSM if used by the KMS server may or may not be the same as the HSM used by the CA. - -![Figure 5-10: Key protection based on KMS. The diagram shows O-RAN Apps/VNFs/CNFs connected to a Secure Storage Resource Manager, which is connected to a KMS server. The KMS server has a Security Module (e.g., HSM) containing a KEK (red key). The Secure Storage Resource Manager has a Secret storage volume (cylinder) containing Private keys (orange keys) and SEks (blue keys). The KMS server is shown encrypting the SEks with the KEK.](753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg) - -O-RAN Apps/VNFs/CNFs → Secure Storage Resource Manager → KMS server (Security Module (e.g., HSM) containing KEK) → Secret storage volume (Private keys 1, 2, SEks 1, 2) - -Legend: Private keys (orange), KEK (red), SEks (blue) - -Figure 5-10: Key protection based on KMS. The diagram shows O-RAN Apps/VNFs/CNFs connected to a Secure Storage Resource Manager, which is connected to a KMS server. The KMS server has a Security Module (e.g., HSM) containing a KEK (red key). The Secure Storage Resource Manager has a Secret storage volume (cylinder) containing Private keys (orange keys) and SEks (blue keys). The KMS server is shown encrypting the SEks with the KEK. - -Figure 5-10: Key protection based on KMS - -### 5.6.4 Impacts on Existing Interfaces and Functionality - -Solution #6, focusing on the implementation of certificate management and secure storage of application private keys within the O-Cloud, substantially impacts the O-Cloud architecture by elevating its security framework. The O-Cloud should incorporate the following components and mechanisms: - -The O-Cloud should support a certificate manager for the automated handling of digital certificate lifecycle processes, including the generation, issuance, renewal, and revocation of certificates. This certificate manager should be capable of integrating with various Certificate Authorities (CAs) and support secure protocols such as ACME, CMPv2, etc., for seamless certificate procurement. It must be designed to facilitate secure, automatic issuance of unique, trusted identity certificates for every application and component within the O-Cloud. - -The O-Cloud should support secure storage and deletion mechanisms for protecting private keys during their entire lifecycle. This involves several critical components and processes: - -1. Secure key generation: Private keys should be generated in a secure environment, possibly using HSMs or TPMs, to ensure that they are never exposed to less secure environments or unauthorized entity. -2. Encrypted storage: Once generated, private keys should be stored in encrypted form. The encryption should be strong enough to prevent unauthorized access. -3. Access control: Strict access controls should be implemented to ensure that only authorized applications can access the private keys. -4. Regular updates and renewal: The O-Cloud should support automated renewal and update processes for keys and certificates, ensuring that they are replaced or updated before they expire or become vulnerable due to advancements in cryptographic attacks or if there is a need to change the CA signing the certificates for Applications. Also, during any such updates, it should be ensured that there is no service interruption. -5. Secure deletion: When a private key is no longer needed, it should be securely deleted. Secure deletion ensures that the key is irrecoverable, preventing any possibility of unauthorized use. This can be achieved through techniques like cryptographic erasure, where the key is made inaccessible by destroying the encryption key used to encrypt the private key. -6. Backup: While maintaining the security of private keys, the O-Cloud should also support secure backup. These backups should be encrypted and stored securely. - -### 5.6.5 Solution Evaluation - -This solution addresses Key Issue #20. - -### 5.6.6 Potential Security Requirements - -In addition to the existing security requirements in Clause 5.1.8.6 of [i.47] focused on the secure storage and deletion of sensitive data within the O-Cloud platform, the following potential security requirements are proposed to ensure secure handling of private keys and certificates within the O-Cloud: - -- The O-Cloud should provide mechanisms for managing the entire lifecycle of digital certificates, including (re-)issuance, renewal, revocation, and expiration. -- The O-Cloud should support automated renewal processes for certificates to avoid service interruptions due to expired/revoked certificates or during any PKI migration (change in CAs used for signing Application certificates). -- The O-Cloud should support orchestration for configuration and updates of CAs for specific network slices. -- The O-Cloud should support integration with trusted CAs for the issuance of certificates. -- The O-Cloud should support for various certificate management protocols like CMPv2 and ACME. -- The O-Cloud should implement secure and robust mechanisms for the generation of cryptographic keys. This includes using high-entropy sources for randomness and adhering to industry-standard cryptographic algorithms such as NIST SP 800-133 [i.48] and SOG-IS [i.49], ensuring the keys are of sufficient strength and quality. -- The O-Cloud should raise alarms and/or notifications if the secure storage space has exceeded the configured limits and more data cannot be stored. - -## 5.7 Solution #7: CMPv2 - -### 5.7.1 Description - -CMPv2 is described in RFC 4210 [i.5]. - -### 5.7.2 Impacts on Existing Interfaces and Functionality - -An O-RAN PNF, VNF, or CNF requiring a PKI certificate will need to support CMPv2. - -### 5.7.3 Solution Evaluation - -Current O-RAN specifications require CMPv2 for the management of the O-RU [i.10]. - -CMPv2 provides a solution for PKI certificate management protocol and procedures. - -CMPv2 provides the following functionality for O-RAN certificate management. - -- CMPv2 supports automatic certificate enrolment, rekey, and renewal procedures. -- CMPv2 provides built-in integrity protection and authentication. -- CMPv2 provides revocation support for VNFs and CNFs with the operation of Revocation Request/Response, Revocation Announcement and CRL Announcement. This support allows for an authorized orchestrator to revoke a certificate for a VNF or CNF before it is removed. -- It is not recommended to have CMPv2 provide revocation support for a PNF for the following reasons: - - o Most Certificate Policies require a human review and authorization of revocation request due to the severity of consequences. - - o The revocation requests are typically submitted by humans rather than machines that own the certificates. Once a PNF is compromised, it cannot be relied upon to request revocation for its own certificate and other elements in a domain may not be able to make practical use of an automated CMPv2 revocation messaging. - - o Human operators may mistake an unapproved revocation request with an actual act of revocation and take pre-mature actions. - - o CRLs are better provided by CRL servers (either LDAP or HTTP access as stated in clause 6.1.1 of the 3GPP TS 33.310[i.2]) that simply act as web-servers with no trust authority. This provides much better scalability properties than an RA/CA responding to high volume of CMP requests for CRLs. -- An O-RAN PNF, VNF, or CNF can use CMPv2 protocol or out-of-band procedures to register at the CA/RA. -- An O-RAN PNF, VNF, or CNF can use CMPv2 protocol to initiate the certificate request to the CA/RA, and receive the certificate from the CA/RA in a secure and automated procedure. -- An O-RAN PNF, VNF, or CNF can use CMPv2 protocol to update the key and certificate to the CA/RA, and receive the renewed certificate from the CA/RA before the certificate expires in a secure and automated procedure. - -### 5.7.4 Potential Security Requirements - -Potential security requirements: - -- An O-RAN PNF, VNF or CNF requiring a PKI certificate should support CMPv2 as defined in RFC-4210 [i.5]. -- An O-RAN PNF, VNF, or CNF supporting CMPv2 should have the URL, FQDN, and/or IP address for the RA/CA pre-configured or configurable. The RA/CA are defined in RFC-4210 [i.5]. For an instance of a PNF being configurable, an O-RAN PNF can be configured with the IP address or FQDN of one or more Certification Authority (CA/RA) servers using DHCP Option 43 as specified in clause 4.2.2 of 3GPP TS 32.509 [i.8]. -- An O-RAN PNF, VNF, or CNF supporting CMPv2 should raise notification and/or alarm if any polling request (as defined in RFC-4210 [5] clause 5.3.22) sent to CMPv2 server fails. -- CRL servers (either LDAP or HTTP access as stated in clause 6.1.1 of the 3GPP TS 33.310[2]) should be used to check the revocation status of certificates. - - If the check for revocation status fails for any reason, e.g., connectivity to CRL server fails, or DNS resolution of CRL server fails, then an alarm should be raised to enable operator to take appropriate actions. -- Details of any revoked certificate should be updated in CRL servers by the operator's PKI. - - If, for some reason, this update fails, alarm and/or notifications should be raised to notify the operator. - -## 5.8 Solution #8: Vendor Root CA Certificate Renewal notification - -### 5.8.1 Description - -The PNFs using vendor-signed certificates for initial certificate enrolment shall raise a notification when vendor root CA certificate is about to expire in x days. The notifications are raised with severity increasing closer to expiration: As an example: - -- WARNING when the certificate expires within the threshold -- MINOR when the certificate expires within 1/3 of the threshold -- MAJOR when the certificate expires within 1/6 of the threshold -- CRITICAL when the certificate expires within 1/30 of the threshold or 3 days, whichever is largest. This severity is used also after certificate expiration. - -### 5.8.2 Impacts on Existing Interfaces and Functionality - -None. - -### 5.8.3 Solution Evaluation - -In many deployments, the validity periods of vendor root CA certificates are very long. Moreover, once a PNF is enrolled using vendor-signed certificates, the need for using vendor root CA certificates for authenticating PNFs is very rarely required. Such a scenario may only be necessary if a PNF deployed many years ago requires a factory recovery for some reason and is intended to be used as a fresh deployment after vendor root CA certificate expires. - -This solution proposes notifications (alarms) to be raised with increasing levels of severity as the expiry date of vendor root CA certificate approaches. Operators need to keep track of such notifications and ensure timely updates of vendor certificates if necessary in order to ensure no impacts on system availability. - -### 5.8.4 Potential Security Requirements - -It is recommended that PNFs which use vendor-signed certificates for initial certificate enrolment monitor the expiry of the root CA certificate used to sign the certificate. When the expiry of the vendor root CA certificate is approaching, PNFs can raise notifications (alarms) with increasing levels of severity as the expiry date gets closer. - -## 5.9 Solution #9: Mitigating the risk of system overload due to bulk certificate updates - -### 5.9.1 Description - -This solution proposes an optional Certificate Update Orchestrator (CUO), which monitors various possible triggers for certificate updates, and orchestrates the certificate updates in a staggered manner in order to prevent potential service outage during simultaneous certificate updates for a large number of NFs (PNFs/CNFs/VNFs). Operators may implement such an orchestrator in their datacenters where NFs are hosted. In some implementations, this may be implemented as an application running in the datacenter where SMO is hosted, or in the O-Cloud. - -Figure 5-11 illustrates a possible implementation of CUO, showing the interfaces it may use. Implementations of CUO may vary, but this application should include the following functionalities in order to mitigate the risks detailed in Key Issue #13. - -- CUO schedules the required certificate updates in various network functions (physical as well as virtual) in a staggered manner. - - The schedule can be derived in a manner that services or functions related to neighboring cells do not update the certificates simultaneously. This can ensure that the connected UEs will have at least one RL, and end-user service experience is not degraded due to any certificate updates. - - Time of initiation of certificate update in every network function can be planned and executed according to this schedule -- CUO monitors and predicts the time required for updating certificates in various network functions - - it maintains an internal database where the past records of time taken for certificate updates are stored - - this database can be used in order to train ML algorithms for predicting the time required for updating certificates -- CUO also monitors and predicts the need for certificate renewals due to expiry, as well as updates due to revocation -- CUO coordinates with SON/RIC in order to increase the coverage of neighboring cells when certificate updates are performed on a specific cell. This can ensure zero impacts on end-user service experience during certificate updates. -- CUO monitors the network performance parameters during the certificate update procedure executions, and reinforces the analytics to derive continuously enhanced scheduling for certificate updates -- CUO monitors the network performance parameters and considers lower network traffic for initiating and scheduling certificate update procedures. - -![Figure 5-11: Certificate Update Orchestrator. A block diagram showing the CUO (Certificate Update Orchestrator) at the center, connected to various network elements. The CUO contains a CUO DB. It receives 'Triggers Bulk Certificate Updates' from an 'Operator / Automation Function'. It sends 'Certificate Revocation' to a 'CRL / OCSP' database. It receives 'Network Performance Measurements' and 'Alarms Indicating Certificate About to Expire' from an 'NMS' (which has an 'Alarm DB'). It sends 'SON Coordinated Certificate Update Execution' to a 'SON / RIC'. The 'SON / RIC' sends 'Coverage Coordination for certificate updates' to 'Network Functions (Physical OR Virtual)'. The 'CUO' sends 'Certificate Updates ACK' to the 'Network Functions'. The 'Network Functions' send 'Certificate Update procedure execution' to a 'CA / RA'. The 'CA / RA' sends 'CA Announcement about Certificate Revocation' back to the 'CUO'.](675af5bb2357ce5b510e613d04f66bdc_img.jpg) - -Figure 5-11: Certificate Update Orchestrator. A block diagram showing the CUO (Certificate Update Orchestrator) at the center, connected to various network elements. The CUO contains a CUO DB. It receives 'Triggers Bulk Certificate Updates' from an 'Operator / Automation Function'. It sends 'Certificate Revocation' to a 'CRL / OCSP' database. It receives 'Network Performance Measurements' and 'Alarms Indicating Certificate About to Expire' from an 'NMS' (which has an 'Alarm DB'). It sends 'SON Coordinated Certificate Update Execution' to a 'SON / RIC'. The 'SON / RIC' sends 'Coverage Coordination for certificate updates' to 'Network Functions (Physical OR Virtual)'. The 'CUO' sends 'Certificate Updates ACK' to the 'Network Functions'. The 'Network Functions' send 'Certificate Update procedure execution' to a 'CA / RA'. The 'CA / RA' sends 'CA Announcement about Certificate Revocation' back to the 'CUO'. - -Figure 5-11: Certificate Update Orchestrator - -### 5.9.2 Impacts on Existing Interfaces and Functionality - -None. - -### 5.9.3 Solution Evaluation - -This solution provides details of possible implementations which can help operators ensure that automated certificate management does not lead to un-intentional service outages in the live network. Such applications can be implemented by the operator and deployed in datacenters hosting the SMO, or in the O-Cloud, enabling easy access of data required for certificate update orchestration. - -Any automated certificate management system would benefit from avoiding simultaneous certificate updates for several network entities. This can be followed as a guideline. - -### 5.9.4 Potential Security Requirements - -None. - -## 5.10 Solution #10: Usage of PSK/Refnum for Initial Certificate Enrolment for PNFs - -### 5.10.1 Description - -This solution addresses key issue #2 of this TR. As described in RFC 4210 [i.5] Section 4.2.2.2 Basic Authenticated Scheme, Initial Authentication Key (IAK) and reference value can be used for initial certificate enrolment using CMPv2. In this document, IAK is referred to as PSK (Pre-shared Key) and reference value is referred to as Refnum. - -For PNFs, operators and vendors need to establish offline (out-of-band) secure methods in order to pre-provision PSK and Refnum values in PNFs which are planned to be newly deployed. The out-of-band methods may be automated, and clause 4.1 of this Technical Report can be referenced for any such automation. - -- PSK is used to sign the CMPv2 certification request, which is the first message sent from the PNF after initial deployment in the live network. PNF sends this request to operator's PKI using pre-configured network details of operator's PKI. -- The integrity of CMPv2 certification request is verified by the operator's PKI using the PSK. Also, operator's PKI verifies proof of possession of Refnum value which is included in the certification request. -- After successful verification of CMPv2 certification request, as per previous step, subsequent procedure is followed according to RFC 4210 Section 4.2.2.2 Basic Authenticated Scheme. -- Upon successful completion of PSK/Refnum based initial enrolment, the newly deployed PNF receives the operator's CA signed certificate, which is used for all subsequent establishment of secure connections with operator's PKI. - - PSK/Refnum values should not be used for any communications after initial enrolment. - - If a factory recovery is required, new PSK/Refnum values should be provisioned by the operator. - -### 5.10.2 Impacts on Existing Interfaces and Functionality - -No new impacts identified by this solution. - -### 5.10.3 Solution Evaluation - -This solution ensures backward compatibility for PNFs using PSK/Refnum based initial certificate enrolment. - -### 5.10.4 Potential Security Requirements - -Any offline or out-of-band PSK/Refnum generation and distribution systems implemented by the operator should ensure that no rogue PNF can obtain valid PSK/Refnum values. - -## 5.11 Solution #11: Certificate renewal procedure - -### 5.11.1 Description - -There are two possible scenarios when certificate renewal is required for any network function in O-RAN: - -1. Certificate is about to expire in near future -2. NF is initialized but has an already expired certificate. - -#### 5.11.1.1 Certificate is about to expire in near future - -As mentioned in key issue #42, in order to ensure that there is no service un-availability due to certificate expiry, certificates should be automatically renewed with sufficient time before expiry. - -This solution proposes the following: - -- Operators can define a certificate renewal strategy, which could depend on the number of days to expiry or depending upon the alarm severity. Operators may also want to define a strategy for staggered certificate renewals. -- When any certificate is about to expire in the near future, associated NF (PNF/CNF/VNF) sends alarms to NMS. - - There can be multiple alarms with different severity. For example, if a certificate is about to expire on 30th day a Minor alarm is raised, if a certificate is about to expire on 15th day a Major alarm is raised, and when there are less than 5 days remaining for the certificate expiry a Critical alarm is raised. - -- NOTE that when a higher severity alarm is raised for the same certificate expiry, the lower severity alarm should be automatically cleared. -- Automated certificate management system monitors these alarms and schedules certificate updates using CMPv2 protocol. - -![Sequence diagram of the certificate renewal procedure. Lifelines: PNF/CNF/VNF, Service Management Orchestrator, Automated Certificate Management OR Certificate Update Orchestrator, Operator's PKI, Operator. The process involves defining a renewal strategy, registering for alarms, receiving fault notifications, checking the strategy, and triggering the renewal via CMPv2.](3337af75dfee8af7687b4f49914d6c93_img.jpg) - -``` - -sequenceDiagram - participant PNF/CNF/VNF - participant SMO as Service Management Orchestrator - participant ACMO as Automated Certificate Management OR Certificate Update Orchestrator - participant OPK as Operator's PKI - participant Operator - - Note right of Operator: Operators can define a strategy, for example, renew certificates if expiry date is after X days, OR, schedule renewals according to the alarm severity. Staggering strategy may also be defined. - Operator->>ACMO: 1 Define certificate renewal strategy - ACMO->>SMO: 2 Register for receiving certificate expiry related alarms notifications - PNF/CNF/VNF->>SMO: 3 Fault Notification about Certificate expiry approaching - SMO->>ACMO: 4 Certificate expiry approaching alarm notification - Note right of ACMO: Automated certificate management can trigger the renewal of certificates in a staggered manner to avoid system overload during bulk renewals. - ACMO->>ACMO: 5 Check for certificate renewal strategy - ACMO->>PNF/CNF/VNF: 6 Trigger Certificate renewal or schedule the renewal - Note over PNF/CNF/VNF, SMO, ACMO, OPK: CMPv2 based certificate renewal procedure - -``` - -Sequence diagram of the certificate renewal procedure. Lifelines: PNF/CNF/VNF, Service Management Orchestrator, Automated Certificate Management OR Certificate Update Orchestrator, Operator's PKI, Operator. The process involves defining a renewal strategy, registering for alarms, receiving fault notifications, checking the strategy, and triggering the renewal via CMPv2. - -Figure 5-12: Certificate renewal procedure - -#### 5.11.1.2 NF is initialized but has an already expired certificate - -If any NF is already initialized but has an expired certificate, it will fail to establish any secure connections. In this scenario, a Critical alarm should be raised frequently for the same until the certificate gets renewed. For example, one critical alarm can be raised per day and it can trigger the operator to obtain a new certificate sooner. The provisioning of updated certificates needs to be done offline. Until such time that the NF gets a renewed certificate, the NF should not be allowed to establish connection to the network. - -### 5.11.2 Impacts on Existing Interfaces and Functionality - -None. - -### 5.11.3 Solution Evaluation - -This solution addresses Key Issue #42. - -### 5.11.4 Potential Security Requirements - -Network management system should provide alarms/notifications to automated certificate management systems alerting about the certificates about to expire in the near future. - -Automated certificate management system should monitor the expiry time of certificates used by all network functions and ensure that the certificates are renewed automatically before the expiry. - -If, for some reason, the certificates for NF(s) expire without getting renewed, Critical alarms should be raised till such a certificate gets renewed. Also, NF(s) with such expired certificates should not be allowed to establish connections with the O-RAN network. - -## 5.12 Solution #12: Certificate Profile for O-RAN TLS Entity - -### 5.12.1 Description - -This solution addresses key issue #33 of the TR. The solution addresses specific certificate profiling requirements for elements, interfaces and systems expressly defined in O-RAN. - -#### 5.12.1.1 Certificate Profiling Requirements for TLS Entity - -The present clause defines the certificate profile requirements for the O-RAN nodes that use the TLS protocol for secured communication in the O-RAN network. The nodes involved and the interfaces are described in the table below. The present clause addresses the certificate profile requirements for the TLS end entity that behave either as client, server or both. - -| Use Case | Interface | Nodes involved | Security Mechanism | -|----------|-----------------------------|---------------------------------------------------|---------------------------------------------------| -| 1 | Open Front Haul(M-Plane) | O-RU and O-DU /SMO | mTLS, SSHv2, FTPES [i.e, O-RU becomes the client] | -| 2 | A1 Interface | Near-RT RIC and Non-RT-RIC | mTLS | -| 3 | Open Front Haul (CUS-Plane) | O-DU and O-RU | IEEE 802.1X with EAP-TLS | -| 4 | O1 | SMO and O-RAN Management Elements | mTLS | -| 5 | O2 | SMO and O-Cloud | mTLS | -| 6 | E2 | Near-RT RIC (xApps) and O-CU-CP and O-CU-UP | NDS/IP(IPsec) or DTLS | -| 7 | F1 | O-CU-CP and O-DU (F1-C)
O-CU_UP and O-DU(F1-U) | NDS/IP(IPsec) or DTLS | - -- The architecture for issuing TLS client and server certificates is as per 3GPP 33.310 [i.2] clause 5.1.1.2. TLS certificates will be directly signed by the CA in the operator domain that the entity belongs to. -- The common rules for all certificates defined in 3GPP33.310 [i.2], clause 6.1.1, clause 6.1.3.a will apply to this present clause. -- All certificates used during the enrolment process of O-RAN entities will follow the requirements given in clause 4.X.1.3 of the present document. - -- The CA-browser forum [i.20] has the following requirement for the certificate operational and key usage periods. Certificates issued on or after 1 September 2020 should not have a Validity Period greater than 397 days. -- **SubjectAltName :** - - According to RFC 5280[i.13], subjectAltName can be an Internet electronic mail address, a DNS name, an IP address, and a Uniform Resource Identifier (URI). As per RFC 6125[i.18], an application service can be identified by a name or names carried in the subject field (i.e., a CN-ID) and/or in one of the following identifier types within subjectAltName entries (DNS-ID, SRV-ID, URI-ID). - - RFC 6066 [i.17], which is applicable to TLS 1.2, defines that currently, only server names supported in SNI extension to TLS are DNS hostnames where "HostName" contains the fully qualified DNS hostname (FQDN) of the TLS server. RFC 6066 [i.17] also defines that literal IPv4 and IPv6 addresses are not permitted in "HostName". In practice, this means that at least one subjectAltName attribute with FQDN is to be included in server-side TLS end-entity certificates and subjectAltName will not contain only IP address in TLS server certificates. -- **Extensions:** - - Mandatory critical key usage: - - digitalSignature for both TLS client and Server certificates. This applies for RSA signature certificate, ECDSA signature certificate, or DSA signature certificate. - - According to TLS1.3 RFC 8446 [i.15] key agreement may be used for Diffie-Hellman certificates. This applies for the ECDH certificate, DH certificate. - -Optional and non-critical TLS Feature Extension: RFC7633[i.19] defines a certificate extension that indicates that clients expect stapled OCSP responses with a value of “status\_request(5)” for the certificate and aborts the handshake ("hard-fail") if such a response is not available. - -As per RFC 9325 for the common use cases of public key certificates in TLS, servers ought to support the following as a best practice: OCSP RFC 6960 [i.26] and OCSP stapling using the status\_request extension defined in RFC 6066[i.17] The exact mechanism for embedding the status\_request extension differs between TLS 1.2 and 1.3. As a matter of local policy, server operators may request that CAs issue must-staple [i.19] certificates for the server and/or for client authentication. - -Certificate Policies: A certificate policy (CP) is a designated set of rules that defines the applicability of a certificate to a particular community or a class of application with common security requirements. A CP is represented in a certificate by an "Object Identifier" (OID). The process of crafting a certificate policy can be derived from the guidelines defined in IETF RFC 3647[i.27]. - -### 5.12.2 Impacts on Existing Interfaces and Functionality - -No new impacts were identified by this solution. - -### 5.12.3 Solution Evaluation - -The following table defined below captures the certificate profile for the TLS end entity (Client and Server). - -| O-RAN TLS Client and Server Certificate Profile | | -|-------------------------------------------------|------------------------------------------------------------------| -| Version | v3 | -| Serial Number | Must be Unique Positive Integer in the context of the issuing CA | - -| Subject DN |

(C=<country>), O=<Organization Name>, CN=<Some distinguishing name>. Organization and CN can be in UTF8 format. Note that C is optional element.

cn=<hostname>, (ou=<servers>), dc=<domain>, dc=<domain>. Note that ou is an optional element.

| | | -|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| -| Validity Period | 1 year or less | | | -| Signature | See clause 6.1.1 of 3GPP 33.310[i.2] for the list of supported signature algorithms. | | | -| Subject Public Key Info | See clause 6.1.1 of 3GPP 33.310[i.2] for the list of supported public key types. | | | -| Extensions | Mandatory | Criticality | Value | -| keyUsage | TRUE | TRUE | digitalSignature for TLS clients and servers | -| extendedKeyUsage | FALSE | FALSE |

id-kp-clientAuth TLS clients

id-kp-serverAuth for TLS servers

Entities that may be both client and server will have both OIDs set.

| -| certificatePolicies | FALSE | FALSE | If added, then it should be populated with a CP object identifier(OID). These OIDs correspond to specific policies established by the certificate issuer. | -| authorityKeyIdentifier | FALSE | FALSE | This is same as the subjectKeyIdentifier of the Issuer's certificate. CA utilizes the method as defined in section 2 of RFC 7093[i.24]. | -| subjectKeyIdentifier | FALSE | FALSE | This is calculated by the issuing CA utilizing method as defined in section 2 of RFC 7093[i.24]. | - -| | | | | -|-----------------------|-------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| cRLDistributionPoint | TRUE | FALSE |

distributionPoint

According to RFC 5280 [i.13] this indicates if the CRL is available for retrieval using access protocol and location with HTTP URI or LDAP.

| -| subjectAltName | TRUE | TRUE |

Clause 4.12.1.1 details the use of subjectAltName in TLS client and Server certificates.

| -| authorityInfoAccess | FALSE | FALSE |

id-ad-caIssuers

According to RFC 5280 [i.13] id-ad-caIssuers describes the referenced description server and the access protocol and location, for example, using one or multiple HTTP and/or LDAP URIs. The referenced CA issuers description is intended to aid certificate users in the selection of a certification path that terminates at a point trusted by the certificate user.

| -| | | |

id-ad-ocsp

According to RFC 5280 [i.13] id-ad-ocsp defines the location of the OCSP responder using HTTP URI.

| -| TLS feature extension | FALSE | FALSE |

id-pe-tlsfeature: "status_request(5)"

This can be used according to RFC 7633 [i.19] to prevent downgrade attacks that are not otherwise prevented by the TLS protocol; RFC 7633[i.19] also defines a certificate extension that indicates that clients expects stapled OCSP responses with a value of "status_request(5)" for the certificate and aborts the handshake ("hard-fail") if such a response is not available.

| - -### 5.12.4 Potential Security Requirements - -The TLS entity certificates should adhere to the certificate profile outlined in clause 5.12.3, based on their respective roles. The CA responsible for handling the certificate signing request should ensure compliance in accordance with the certificate profile specified in clause 5.12.3. - -## 5.13 Solution #13: Identifying RA and CA as separate logical entities with flexible deployment options - -### 5.13.1 General Description - -This solution addresses Key Issue #1. - -Reference : RFC 4210 [i.5] Appendix A : - -The reasons that justify the presence of an RA can be split into those that are due to technical factors and those which are organizational in nature. - -- If hardware tokens are in use, then not all end entities will have the equipment needed to initialize these; the RA equipment can include the necessary functionality (this may also be a matter of policy). - - NOTE: This aspect may not be directly related to certificate management, and hence not important for this study. -- Some end entities may not have the capability to publish certificates; again, the RA may be suitably placed for this. -- The RA will be able to issue signed revocation requests on behalf of end entities associated with it, whereas the end entity may not be able to do this (if the key pair is completely lost). - -Some of the organizational reasons that argue for the presence of an RA are the following. - -- It may be more cost effective to concentrate functionality in the RA equipment than to supply functionality to all end entities (especially if special token initialization equipment is to be used). -- Establishing RAs within an organization can reduce the number of CAs required, which is sometimes desirable. -- RAs may be better placed to identify people with their “electronic” names, especially if the CA is physically remote from the end entity. - - NOTE: Authenticating a human with a certificate is outside the scope of O-RAN, and therefore, this point is not relevant for this study. -- For many applications, there will already be in place some administrative structure so that candidates for the role of RA are easy to find (which may not be true of the CA). - -Based on the above description from RFC 4210 [i.5], it is recommended that operators assess the organizational policies and requirements for making a decision on whether or not, there is a need for having RA and CA deployed separately for O-RAN. - -From O-RAN perspective, considering PNFs, CNFs and VNFs as “end entities” to whom certificates need to be issued by operator’s CA, a separate RA can be considered for the following scenarios: - -1. For registration of xApps, Near-RT RIC can act as RA -2. For registration of rApps, Non-RT RIC can act as RA -3. Similarly, for registration of PNFs, RA may be hosted in SMO. -4. As an alternative deployment, RA can be hosted in O-Cloud and it can cater to registration of all PNFs/CNFs/VNFs - -### 5.13.2 Impacts on Existing Interfaces and Functionality - -None. - -### 5.13.3 Solution Evaluation - -This solution addresses Key Issue #1. - -### 5.13.4 Potential Security Requirements - -From O-RAN standardization point of view, RA and CA should be considered as separate logical entities. Operator may decide on deploy these entities in an integrated manner or separately. - -## 5.14 Solution #14: Securing Root CA Private Key - -### 5.14.1 General Description - -Solution #14 addresses Key Issue #20 Secure Storage of Trust Anchors and Private Keys. - -Securing the root CA private key is critical for the integrity of Public Key Infrastructure (PKI). A compromised root CA private key can lead to unauthorized certificate issuance, enabling identity spoofing and undermining trust in the entire PKI ecosystem. To secure root CA private keys, it's essential to maintain Root CA offline as a security best practice. - -#### Importance of maintaining Root CA offline - -The Primary objective of keeping the root Certificate Authority (CA) offline is to secure the private key associated with the root CA. The root CA private key security is critical because it is used to sign certificates issued by intermediate or Subordinate CAs, and its compromise could lead to fraudulent or unauthorized certificate issuance, impacting the trust of the O-RAN operator public key infrastructure. - -By maintaining the root CA offline, the private key is protected from various threats and unauthorized access, and thereby enhancing the security of the PKI infrastructure. - -Keeping the root CA offline, often referred to as “offline root CA”, means that private key of the root Certificate Authority (CA) is stored on a system that is not connected to any network or the internet. It is physically isolated from other systems and kept in a secure, air-gapped environment. This isolation reduces the risk of the root CA private key being exposed to online threats and unauthorised access and enhancing the security and trustworthiness of the PKI in O-RAN systems. - -The root CA needs to be online only during its initial setup and when issuing certificates for intermediate or Subordinate CAs. Once these intermediate or subordinate CAs certificates are signed, the root CA can be taken offline and stored securely. The root CA serves as a trust anchor for the PKI, and its primary role is to issue certificates for subordinate or intermediate CAs. Subordinate or Intermediate CAs then handle the issuance of certificates to O-RAN VNFs/CNFs, while root CA remains securely offline to maintain PKI integrity. - -Note: while it's common for a root CA's private key to be stored in HSM for added security, the term “root CA offline” refers to the network connectivity of the root CA system, not the specific use of an HSM. HSM provides additional layers of security by storing the private key in tamper-resistant hardware, but it doesn't directly affect the network connectivity status of the root CA system. [i.7] - -### 5.14.2 Impacts on Existing Interfaces and Functionality - -None. - -### 5.14.3 Solution Evaluation - -This solution addresses Key Issue #20. - -### 5.14.4 Potential Security Requirements - -From O-RAN standardization point of view, it's recommended to maintain Root CA offline status. - -Note: This recommendation applies only if Private CA uses intermediate CAs. - -## 5.15 Solution #15: Certificate enrolment for new NF Deployment using CMPv2 - -### 5.15.1 General Description - -Figure 5-13 illustrates the steps performed to configure enrolment certificate for new NF Deployment. The enrolment certificate shall be used for secured communication between SMO and Cloudified NF. The below procedure is specified as part of Instantiate Network Function on O-Cloud in clause 3.2.1 of ORAN TS Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN [i.52]. - -| Use case stage | Evolution / specification | <> Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | Provisioning enrolment certificate for new NF Deployment to perform initial configuration | | -| Actors and Roles | NFO Service Consumer - Any service consumer allowed to consume NFO services [i.52];
SMO -A Service Management and Orchestration framework [i.51];
NFO – Network Function Orchestration [i.51];
OAM Functions – Operations, Administration and Maintenance function [i.51] ;
Operator PKI- Operator Public Key infrastructure;
O-Cloud-Cloud platform that provides O-RAN standardized interfaces, hosting O-RAN defined software components [i.52];
Cloudified NF- A RAN Network Function software that is deployed in the O-Cloud via one or more NF Deployments [i.52];
NF Deployment - A software deployment on O-Cloud resources that realizes all or part of a Cloudified NF [i.52];
End Entity: user of PKI certificates and/or end user system that is the subject of a certificate [i.13]; | | -| Pre-conditions | i. NFO has credentials to communicate with PKI.
ii. Certificate Authority to issue the NF Certs to End Entity which is created in PKI.
iii. All End Entity associated trust domains are already created in PKI. | | -| Begins when | New NF is ready for deployment. | | -| Step 1 (M) | NFO Service Consumer requests to NFO to instantiate new NF Deployment on the O-Cloud. | | -| Step 2 (M) | NFO invokes Operator PKI via the vendor specific PKI interface to create End Entity associated to NF Deployment via O1 interface. | | -| Step 3(M) | Operator PKI configures the End Entity and responds with enrolment data to NFO.
Enrolment data consists of: CMP details associated with provisioned End Entity, including one-time password in section 2.2.3 of RFC 7030 [i.32]; Root CA certificate details. | | -| Step 4 (M) | NFO incorporates the enrolment data in NF Deployment initial configuration (including PKI server details). NF Deployment should consume these data to request certificate and CA trust certs towards operator PKI. | | -| Step 5 (M) | NFO triggers NF Deployment in O-Cloud using O2-dms interface, this trigger may be in several steps, for instance secrets shall be shared in secured way before actual NF Deployment starts. | | -| Step 6 (M) | O-Cloud creates new NF Deployment instance. | | -| Step 7(O) | The NFO receives information about the success/failure of the NF Deployment instantiation in the O-Cloud. | | -| Step 8(M) | NF Deployment requests Operator PKI using the initial configuration with received one-time password to enroll certificates. | | -| Step 9(M) | Operator PKI responds with enrolment certificate to the NF Deployment instance, including the trust anchors of the domains the node will communicate to. | | -| Ends when | Initial configuration and enrolment certificate is configured for the new NF Deployment. | | -| Exceptions | None identified | | -| Post-conditions | Trust established between the Cloudified NF and SMO. | | - -![Sequence diagram for Certificate enrolment for new NF Deployment. Lifelines: NFO Service Consumer, NFO, OAM, Operator PKI, O-Cloud, Cloudified NF (NF Deployment). The process involves an NF deployment request, creation of an end entity, return of a one-time password, update of NF deployment, deployment in O-Cloud, return of a deployment instance, a success/fail response, a certificate request (CMPv2), processing of the CSR, and finally the enrollment certificate response. Callouts explain the NFO invoking Operator PKI via a vendor-specific PKI interface and the Operator PKI configuring the End Entity with enrollment data.](935075de5250cfe8aa0fb9d65d63dde5_img.jpg) - -Sequence diagram for Certificate enrolment for new NF Deployment. Lifelines: NFO Service Consumer, NFO, OAM, Operator PKI, O-Cloud, Cloudified NF (NF Deployment). The process involves an NF deployment request, creation of an end entity, return of a one-time password, update of NF deployment, deployment in O-Cloud, return of a deployment instance, a success/fail response, a certificate request (CMPv2), processing of the CSR, and finally the enrollment certificate response. Callouts explain the NFO invoking Operator PKI via a vendor-specific PKI interface and the Operator PKI configuring the End Entity with enrollment data. - -Figure 5-13 Certificate enrolment for new NF Deployment - -#### 5.15.2 Impacts on Existing Interfaces and Functionality - -None. - -## 5.15.3 Solution Evaluation - -This solution addresses Key Issue #6: Initial Certificate Enrolment for new NFs. - -## 5.15.4 Potential Security Requirements - -**REQ-SEC-CMF-VNF\_CNF-X:** SMO shall configure all the initial information for certificate enrolment procedure for NF Deployment. - -# 5.16 Solution #16: Shared O-RU Trust Anchors Management - -## 5.16.1 General Description - -In order to support the principle of least privilege, the O-RU controllers of each SRO should have a dedicated set of trust anchors within the Shared O-RU, so that SRO O-RU controllers would be trusted only on the interfaces or otherwise defined connections or resources within the Shared O-RU. This would mean that SRO O-RU controller(s) from a specific trust domain (specific operator) could not access interfaces / resources dedicated for other trust domain (another operator). - -The Shared O-RU should support management of its trust anchors. Shared O-RU trust anchor management includes installing the trust anchors that the Shared O-RU Host requires (e.g., upon configuration of a new SRO) and removing the trust anchor(s) corresponding to SRO PKI(s) no longer required. A user (e.g., Host O-RU controller) with the right privileges (e.g., full control of Shared O-RU security configuration data) is expected to manage the Shared O-RU trust anchors only over a secure channel. - -## 5.16.2 Impacts on Existing Interfaces and Functionality - -None. - -## 5.16.3 Solution Evaluation - -The provisions in this clause address the security threats in 4.44.2. - -## 5.16.4 Potential Security Requirements - -The Shared O-RU should support multiple trust anchors and management of trust anchors. - -## 6 Conclusions - -### 6.1 Key Issue #41: CMPv2 - -The following proposed normative specifications support PKI certificate management protocol and procedures for an O-RAN PNF, VNF, or CNFs using PKI certificates: - -An O-RAN PNF, VNF or CNF requiring a PKI certificate shall support CMPv2 as defined in RFC-4210 [i.5]. - -An O-RAN PNF, VNF, or CNF supporting CMPv2 shall have the URL, FQDN, and/or IP address for the RA/CA pre-configured or configurable. The RA/CA are defined in RFC-4210 [i.5]. For an instance of a PNF being configurable, an O-RAN PNF can be configured with the IP address or FQDN of one or more Certification Authority (CA/RA) servers using DHCP Option 43 as specified in clause 4.2.2 of 3GPP TS 32.509 [i.8]. - -### 6.2 ACME as Optional Certificate Management Protocol - -An O-RAN network function requiring a PKI certificate may optionally support ACME as defined in RFC-8555 [i.42] in addition to CMPv2. This is especially beneficial for use with O-Cloud implementations that currently often use ACME as a certificate management protocol via the ACME plugin for the cert-manager component of Kubernetes which is a common technology for dynamic o-cloud deployments. - -The ACME solution as described in clause 4.4 addresses the following key issues: - -1. Key Issue #37: Lightweight solution (refer to clause 5.2 for details) -2. Key Issue #38: Interoperability (refer to clause 5.3 for details) - -### 6.3 Usage of PSK/Refnum for initial certificate enrolment for PNFs, CNFs and VNFs - -This clause presents conclusions for solutions #1 and #10. - -As described in RFC 4210 [i.5] Section 4.2.2.2 Basic Authenticated Scheme, Initial Authentication Key (IAK) and reference value can be used for initial certificate enrolment using CMPv2. In this document, IAK is referred to as PSK (Pre-shared Key) and reference value is referred to as Refnum. - -For backward compatibility, PSK/Refnum-based initial certificate enrolment can be used for PNFs. - -Based on the potential security requirements proposed in clause 4.1.4 and 4.10.4, the following normative security requirement can be added to the O-RAN security requirements specification: - -Any offline or out-of-band (automated or manual) PSK/Refnum generation, distribution and provisioning systems implemented by the operator should ensure that no rogue PNF/CNF/VNF can obtain valid PSK/Refnum values. - -### 6.4 Vendor root CA certificate renewal notification - -This clause proposes conclusions for solution #8, which addresses key issue #8. - -A new security requirement can be added in O-RAN security requirements specifications for the potential security requirement proposed in clause 5.8.4 of this Technical Report. - -Also, it is recommended that operators monitor notifications which may be raised when vendor root CA certificate is about to expire and take appropriate actions to ensure that there is no impact on system availability. - -Proposed new security requirement: - -PNFs which use vendor-signed certificates for initial certificate enrolment should monitor the expiry of the vendor root CA certificate used to sign the certificate. When the expiry of the vendor root CA certificate is approaching, PNFs should raise notifications (alarms) with increasing levels of severity as the expiry date gets closer. - -## 6.5 Initial certificate enrolment for PNFs using vendor certificates - -This clause proposes conclusions for solution #5, which addresses Key Issue #3 and Key Issue #4. - -New security requirements can be added in O-RAN security requirements specifications for the potential security requirements proposed in clause 5.5.4 of this Technical Report. - -## 6.6 Certificate renewal procedure - -This clause proposes conclusions for solution #11, which addresses key issue #42. - -New security requirement can be added in O-RAN security requirements specifications for the potential security requirements proposed in clause 5.11.4 of this Technical Report. - -## 6.7 RA and CA as separate logical entities - -This clause proposes conclusions for solution #13, which addresses key issue #1. - -No new security requirements are required for this because it is up to the operator to make a decision whether to deploy RA and CA as independent entities or in an integrated manner. - -## 6.8 EST as Optional Certificate Management Protocol - -An O-RAN element requiring a X.509 certificate may optionally support EST as defined in RFC-7030 [i.32] in addition to CMPv2. This is especially beneficial in scenarios where the environment does not require a complex PKI infrastructure for certificate management and also offers a practical solution in scenarios where an O-RAN network element lacks digital certificate bootstrapping or is missing CA information for enrolment. The EST solution as described in clause 5.3 addresses the following key issues: - -1. Key Issue #37: Lightweight solution (refer to clause 5.2 for details) - -## 6.9 Use of BRSKI in O-RAN - -No normative specifications are necessary for BRSKI as described in Solution #2, which address key issues #1, #2, #10, #37, #38, and #41. - -See Clause 5.2.3 Solution Evaluation for further information. - -## 6.10 Mitigating the risk of system overload due to bulk certificate update - -No normative specifications are necessary to address Solution #9, which addresses key issue #13. - -See Clause 5.9.3 Solution Evaluation for further information on best practices to mitigate the risk of system overload due to a bulk certificate update. - -## 6.11 Key Issue #20: Certificate Management and Secure Storage of Private Keys - -Based on solution #6 which is detailed in clause 5.6 of the present document, following conclusions are made on the Key-Issue #20 “Certificate Management and Secure Storage of Applications Private Keys”: - -For the evaluation two different solution concepts will be considered. - -The first concept is the based on an O-Cloud platform hosting a ‘Secure Storage Resource Manager (SSRM)’. This SSRM is managing the interface to either the SW based or HW based secure storage solution. On the north-bound interface the SSRM is providing a common Secure Storage API that can be used by application to request service from the SSRM, while on the south-bound interface the SSRM is hiding the underlying method for key and file storage. The private key is never leaving the secure key storage and any service request that involves the private key is going via the SSRM. - -### 6.11.1 Evaluation and Assessment for local security module managed by SSRM within the O-Cloud - -Advantages: - -- Compliance Requirements: Certain regulatory frameworks may require the use of local security modules (e.g., HSM [i.6], [i.46]) for specific security controls. Utilizing a local security module can help meet compliance requirements. -- Reduced Dependency: By having a local security module, organizations reduce their reliance on external systems or services, providing greater control over key management. - -Considerations: - -- Higher Cost: Security modules are specialized devices and can be more expensive to acquire and maintain compared to using a KMS. -- Limited Scalability: Local security modules have finite capacity, and scaling may require additional security modules or infrastructure investments. -- Operational Complexity: Local security modules require dedicated management, configuration, and maintenance, which may add complexity to the overall O-Cloud architecture and administration. - -The second concept is based on a remote Key Management System (KMS). The KMS is external to the O-Cloud, which means it is located outside of the O-Cloud infrastructure. It is responsible for storing and managing private keys by an HSM and issuing key-encryption keys which are used to protect the secure storage volumes. - -### 6.11.2 Evaluation and Assessment for the KMS - -Advantages: - -- Key Lifecycle Management: KMS solutions often include features for key rotation, revocation, and auditing, enabling effective key lifecycle management. -- Integration with O-Cloud: KMS solutions offered by cloud service providers can seamlessly integrate with other cloud services, simplifying key management in O-Cloud. - -Considerations: - -- Dependence on External Service: Utilizing a KMS requires reliance on an external service, which may introduce dependencies and potential availability concerns. Organizations need to ensure proper backup and disaster recovery measures. -- Data Privacy: With a KMS, cryptographic key material is stored and managed by a third-party service. Organizations should consider the privacy implications and evaluate the trustworthiness of the KMS provider. - -### 6.11.3 Conclusion - -It is concluded to go for normative work based on the O-Cloud with local security modules managed by an embedded Secure Storage Resource Manager (SSRM). A local security module offers enhanced physical protection and security measures for cryptographic keys, making it a robust solution for safeguarding sensitive information within the O-Cloud infrastructure. Solution #6 can be referred to as one potential solution for normative work for key issue #20. - -**Rationale:** By using a local security module, it can be ensured that the cryptographic keys remain within the boundaries of the O-Cloud environment, reducing reliance on external services and enhancing control over key management. While a local HSM may introduce certain considerations such as cost, scalability, and operational complexity, the benefits of its enhanced security and compliance adherence can outweigh these factors in security-sensitive environments like O-Cloud. - -## 6.12 Cert Profile for O-RAN TLS Entity - -This clause proposes conclusions for solution #12, which addresses key issue #33. - -New security requirements can be added in O-RAN Protocol Specifications for the potential security requirements proposed in clause 5.12.4 of this Technical Report. - -The certificate profile defined in clause 5.12.3 of this Technical Report can be applied O-RAN NFs (PNF/VNF/CNF) and O-RAN interfaces that use the TLS protocol for establishing secured communication. - -## 6.13 Certificate enrollment for new NF Deployment using CMPv2 - -This clause proposes conclusions for solution #15, which addresses key issue #6. - -Based on the potential security requirements proposed in clause 5.15.4, the following normative security requirement can be added to the O-RAN security requirements and control specification: - -The certificate enrollment procedure for NF deployment defined in clause 5.15.1 of this Technical Report should be applied to O-RAN NFs (VNF/CNF) for establishing secure communication. - -## 6.14 Key Issue #28: Risk of Service un-availability due to root CA Certificate updates for CNFs and VNFs - -This clause proposes conclusions for key issue #28. Solution #3, Solution #4, Solution #6 and Solution #7 can be used as basis for normative work for this key issue #28. - -Accordingly, following principles can be followed to address the threats described in key issue #28: - -- As described in solution #3, solution #5 and solution #7, automated certificate lifecycle management using protocols like CMPv2 or ACME or EST can be supported by O-Cloud in order to ensure that root CA certificate updates do not lead to service un-availability. -- Solution #6 descriptions include potential requirements for O-Cloud to support automated renewal processes during PKI migration, and integration with trusted CAs. -- The potential requirements from these solutions can be used as basis for further normative specifications. - -## 6.15 On Shared O-RU Trust Anchors Management - -This clause proposes conclusions for solution #16, which addresses key issue #44. Based on the potential security requirements proposed in clause 5.16.4, it is also recommended that the following normative security requirements are added to the O-RAN Security Requirements and Controls Specification [i.47]: - -- The Shared O-RU shall support multiple trust anchors. -- The Shared O-RU shall support management of the Shared O-RU trust anchors. - -# 7 Key Issues-Solutions mapping - -This clause contains the mapping of the proposed solutions to the key issues. - -Table 7-1 Mapping of Key Issues to Solutions - -| | Sol. #1 | Sol. #2 | Sol. #3 | Sol. #4 | Sol. #5 | Sol. #6 | Sol. #7 | Sol. #8 | Sol. #9 | Sol. #10 | Sol. #11 | Sol. #12 | Sol. #13 | Sol. #14 | Sol. #15 | Sol. #16 | -|---------------|---------|---------|---------|---------|---------|---------|---------|---------|---------|----------|----------|----------|----------|----------|----------|----------| -| Key issue #1 | | X | X | | X | X | | | | | | | X | | | | -| Key issue #2 | X | X | X | | | | | | | X | | | | | | | -| Key issue #3 | | | | | X | | | | | | | | | | | | -| Key issue #4 | VOID | | | | | | | | | | | | | | | | -| Key issue #5 | VOID | | | | | | | | | | | | | | | | -| Key issue #6 | X | | | | | X | | | | | | | | | X | | -| Key issue #7 | VOID | | | | | | | | | | | | | | | | -| Key issue #8 | | | X | | | X | X | X | | | | | | | | | -| Key issue #9 | VOID | | | | | | | | | | | | | | | | -| Key issue #10 | | X | X | | | X | X | | | | | | | | | | -| Key issue #11 | VOID | | | | | | | | | | | | | | | | -| Key issue #12 | | | | | | | | | | | | | | | | | -| Key issue #13 | | | | | | X | X | | X | | | | | | | | -| Key issue #14 | VOID | | | | | | | | | | | | | | | | -| Key issue #15 | VOID | | | | | | | | | | | | | | | | -| Key issue #16 | VOID | | | | | | | | | | | | | | | | -| Key issue #17 | VOID | | | | | | | | | | | | | | | | -| Key issue #18 | | | | | | X | X | | | | | | | | | | -| Key issue #19 | | | | | | X | X | | | | | | | | | | -| Key issue #20 | | | | | | X | X | | | | | | | X | | | -| Key issue #21 | | | | | | X | X | | | | | | | | | | -| Key issue #22 | | | X | | | X | X | | | | | | | | | | -| Key issue #23 | | | X | | | X | X | | | | | | | | | | -| Key issue #24 | | | | | | | X | | | | | | | | | | -| Key issue #25 | | | X | | | X | X | | | | | | | | | | -| Key issue #26 | | | X | | | X | X | | | | | | | | | | -| Key issue #27 | | | X | | X | X | X | | | | | | | | | | -| Key issue #28 | | | X | X | | X | X | | | | | | | | | | -| Key issue #29 | | | X | | | X | X | | | | | | | | | | -| Key issue #30 | | | X | | | X | X | | | | | | | | | | -| Key issue #31 | VOID | | | | | | | | | | | | | | | | -| Key issue #32 | VOID | | | | | | | | | | | | | | | | -| Key issue #33 | | | X | | | X | X | | | | | X | | | | | -| Key issue #34 | VOID | | | | | | | | | | | | | | | | -| Key issue #35 | VOID | | | | | | | | | | | | | | | | -| Key issue #36 | | | | | | X | X | | | | | | | | | | -| Key issue #37 | X | X | X | X | X | | X | | | | | | | | | | -| Key issue #38 | | X | | X | | | | | | | | | | | | | -| Key issue #39 | | | X | | | | | | | | | | | | | | -| Key issue #40 | VOID | | | | | | | | | | | | | | | | -| Key issue #41 | | X | | | | | X | | | | | | | | | | -| Key issue #42 | | | | | | | X | | | X | | | | | | | -| Key issue #43 | X | | X | | | X | X | | | | | | | | | | -| Key issue #44 | | | | | | | | | | | | | | | | X | - -## Annex: Change history/Change request (history) - -| Date | Revision | Description | -|------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2022.02.22 | V01.00.01 | Document creation, template | -| 2022.03.08 | V01.00.02 | Updated template | -| 2022.04.12 | V01.00.03 | Added key issues generated by the CMF subworking group. | -| 2022.06.14 | V01.00.04 | Incorporated the following CRs:
RMI-2022.04.26-SFG-Certificate-management-CR-002
RMI-2022.05.10-SFG-Certificate-management-CR-003
NOK-2022.05.10-SFG-Certificate-management-Multiple certificates per interfaces - CR_03
NOK-2022.05.10-SFG-Certificate-management-merge of key issues 5 and 7- CR_02
NOK-2022.05.10-SFG-Certificate-management-Moving Key issues to Solutions- CR_01 | -| 2023.01.10 | V01.00.05 | Incorporated the following CRs:
ATT-2022.06.07- SFG-Certificate-management-architecture-CR_01-r2
NOK-2022.07.04-SFG-Certificate-management-vendor-cert-based-enrolment_CR_05-r8
NOK-2022.07.04-SFG-Certificate-management-PSK_Refnum-CR_04_r8
RMI.COM-2022.08.22-WG11-CR-0001-Certificate-Management-Study-on-ACME
ORA-2022.09.27-WG11-CR-0025-Certificate-Management-SecStorageHSMv04
ATT-2022.10.24-SFG-CMPv2-solution-CR_02-r1
NOK-ORA-2022.12.06-WG11-CR-0013-Certificate-Management-SecStorage_v01 | -| 2023.06.30 | V01.00.06 | Incorporated the following CRs:
DT-2023.01.31-SFG-TR-Certificate-Management-Framework-ACME-optional_v5
ERI-2023.01.25-WG11-CR0019-CertificateManagementFramework-TR-v01
NOK-2023.02.01-WG11-CR-0046-Certificate-management-Bulk_Updates_r2
NOK-2023.02.01-WG11-CR-0045-Certificate-management-PSK_Refnum
NOK-2023.05.02-WG11-CR-0047-Certificate-management-Renewal-v01
SYM-2023.05.09-SFG-CR-0009-CertificateProfile_TechnicalReport_v07 | -| 2023.09.12 | V01.00.07 | Incorporated the following CRs:
NOK-2023.07.06-WG11-CR-0084-Certificate-management-RA-CA-v03 | - -| | | | -|------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | AKA-2023.07.10-WG11-CR-0001-Align-Certificate-Management-terminology_v02
SYM-2023.06.27-SFG-CR-0019-CertificateProfile_TR_Conclusion_v03
WG11-2023.07.25-WG11-CR-0007-Key issue-Solutions mapping_v02
NOK-2023.07.06-WG11-CR-0085-Plug-and-connect-PNFs-v03
NOK-2023.08.07-WG11-CR-0099-BRSKI_v02 | -| 2023.10.24 | V01.00.08 | WG11-2023.09.08-WG11-CR-0010-Key issues-1-to-11-42-43-v02
ATT-2023.09.12-WG11-CR-69-Solution-Evaluation-Reorganization
NOK-2023.09.08-0107-Key issue-Solutions mapping
WG11-2023.09.25-WG11-CR-0013-Key issues-12-to-25-v03
NOK-2023.08.07-WG11-CR-0106-KI28-PKI-Migration
NOK-2023.08.07-WG11-CR-0118-Soltion-PKI-Migration-v2
SYM.AO-2023.08.22-WG11-CR-0022-CertificateManagemet-EST_Protocol-v07
NOK-2023.10.17-WG11-CR-0117-Solution%231_Solution%2310_Updates
NOK-2023.10.17-WG11-CR-0119-Solution%238_Updates_v2
NOK-2023.10.17-WG11-CR-0120-Conclusions_Sol5_11_13
WG11-2023.09.25-WG11-CR-0014-Key issues-9 11 and 26-to-41-v01 | -| 2024.03.13 | V02.00 | NOK-2023.06.20-WG11-CR-0083-Conclusion_on_Certificate-Management-SecStorage_v06
RMI-2023.10.17-WG11-CR-0013-Securing private keys_v2
ATT-2023.10.19-0070-Key-issue-Solutions-mapping-update
SYM.AO-2023.11.28-WG11-CR-0032-EST_Protocol_Conclusion-v03
ATT-2023.11.28-WG11-CR-0031-CertMgmtTR_KeyIssues33and36Updates-v3
ATT-2023.12.19-WG11-CR-0032-CertMgmtTR_Conclusion_Solution2-v2
ATT-2023.12.19-WG11-CR-0033-CertMgmtTR_Conclusion_Solution9-v1
WG11-2024.01.08-WG11-CR-0021-CertMgmtTR_PSR_Solution6-v2
NOK-2023.10.17-WG11-CR-0138-Solution_8_Conclusion-correction
SYM-2024.01.30-WG11-CR-0041-CertificateProfile_Conclusion-v03 | -| 2024.06.26 | V03.00 | NEC-2024.04.09-WG11-CR-0017-CertMgmtFrmk_Abbreviations_and_Acronyms_Updates-v1
ERI-2024.05.14.-WG11-CR0124-CertificateManagementFramework-KeyIssue40mapping-v01
ERI-2024.05.14-WG11-CR0126-CertificateManagementFramework-Subjectaltname-v02
ERI-2024.05.28-WG11-CR0133-CertificateManagementFramework-CertificateEnrolmentforNewCNF-v04 | - -| | | | -|------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2024.11.04 | V04.00 | NOK-2024.07.12-WG11-CR-0175-CertMgmt-req-CRL-failure-alarms-v02
NOK-2024.07.12-WG11-CR-0176-CertMgmt-req-storage-space-alarms-v02
ERI-2024.06.25-WG11-CR0144-CertificateManagementFramework-
Clause6.13Conclusion for solution5.15-v03
NOK-2024.09.16-WG11-CR-0197-CMPv2-polling-failure-alarms-v03 | -| 2025.06.02 | V05.00 | NEC-2025.01.07-WG11-CR-
0045_Key_Issues_Solution_Mapping_Corection_To_CMF_TR-v2
NOK-2025.01.28-WG11-CR-0234-O-Cloud-slice-requirements
NOK-2025.03.18-WG11-CR-0271-Conclusion_Updates_KI_20_28_Sol6_r2 | -| 2025.11.10 | V06.00 | ERI-2025.05.21-WG11-CR-0262-CMF_shared-o-ru_ta_mgmt-v05
ERI-2025.10.06-WG11-CR-0264-CMF_shared-o-ru_ta_mgmt-conclusion-v02
ERI-2025.10.06-WG11-CR-0265-CMF_mapping_shared-o-ru_ta_mgmt-issue-
sol-v01 | \ No newline at end of file diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/01e00200a536673d6cd0e6d8705047a0_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/01e00200a536673d6cd0e6d8705047a0_img.jpg deleted file mode 100644 index 0f7895eb0bab0f7415e7b4af60120f24d259e5e0..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/01e00200a536673d6cd0e6d8705047a0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7ea711b47567ae72714e86db29b7b2af7091c2704f14bd142bed134c731cfdd9 -size 78647 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 57c1ec40ddd8b65e207ef8b2cf9bc077c1ef5c94..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:824af40599b843085c67553baa10788d2a863049341844c656cd06dd0efa3f1b -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/132cff7e872feb31f629703959beddd7_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/132cff7e872feb31f629703959beddd7_img.jpg deleted file mode 100644 index 012bc0a0c1362cc8c06030a7775c16ac28b37c0d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/132cff7e872feb31f629703959beddd7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:32d4b1fcab47304809a0556258384b9867ba4664ff02f9a90c316b983c6e232d -size 73686 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index a825d9b99f911d8f827b9553283b5ad21813fd46..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0b8fe5d6b51586629e54302f8e923644b5ad824f552cbb388a721c71c2fdb5bf -size 4236 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index e9d056186f91071754a1bd66cc5b0f58f9cdcd1d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a6feea577002af775f92c1c073ef8e278549447e23549760a568e59d2a4c42d6 -size 4142 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/1baaba7a6e54e77197475726c871067d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 44e4ca1e706fffc218594e75b7fbdfaeee43149d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ba36991bdae993881d357810ae680e8b2718eeb75c0831521a0cdc2d6e038f2 -size 4147 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 64086a4d244aa3db8b0677e77b789f740d9f4c5b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9ce3defd2f5798109734f8ce61fd1df9c7d34820ed350d272ad3c84b6036042d -size 4038 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index a825d9b99f911d8f827b9553283b5ad21813fd46..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0b8fe5d6b51586629e54302f8e923644b5ad824f552cbb388a721c71c2fdb5bf -size 4236 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index 44e4ca1e706fffc218594e75b7fbdfaeee43149d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ba36991bdae993881d357810ae680e8b2718eeb75c0831521a0cdc2d6e038f2 -size 4147 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/3337af75dfee8af7687b4f49914d6c93_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/3337af75dfee8af7687b4f49914d6c93_img.jpg deleted file mode 100644 index 2c5f3b7473c3e4cc05f072ce88b5ccfe4f936eb6..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/3337af75dfee8af7687b4f49914d6c93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4e3341b6039dc7d09f7661db5617410be6cf1842f11bc53fe6291ca8d891fcc6 -size 108566 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index afba4cbc0ac8c2c472a372fb4194c683e1ee58f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:000095a140bd7ffa463a618a958f3f4db3d9ae64e0cecbd298ce079b6b1ba3e8 -size 4157 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index 64086a4d244aa3db8b0677e77b789f740d9f4c5b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9ce3defd2f5798109734f8ce61fd1df9c7d34820ed350d272ad3c84b6036042d -size 4038 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index 44e4ca1e706fffc218594e75b7fbdfaeee43149d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ba36991bdae993881d357810ae680e8b2718eeb75c0831521a0cdc2d6e038f2 -size 4147 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index ec88d6082dfd5503b0cbfffa3862f50f88126938..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:622bfe7b09145ac3d005d3201101345547a9e23cb2625c80440d22ad9dd8178d -size 4243 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index 44e4ca1e706fffc218594e75b7fbdfaeee43149d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/6588b1c7f14069d96744b473ad663248_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ba36991bdae993881d357810ae680e8b2718eeb75c0831521a0cdc2d6e038f2 -size 4147 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/675af5bb2357ce5b510e613d04f66bdc_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/675af5bb2357ce5b510e613d04f66bdc_img.jpg deleted file mode 100644 index 7f34c819143067dae67dc07e9a125b2a6889514d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/675af5bb2357ce5b510e613d04f66bdc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:90be6c2e62a2ee7e7882650374b0bc11c752ef801125e46766f12519409f8294 -size 50372 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/683f755e8456c884716de4fce48c7e63_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/683f755e8456c884716de4fce48c7e63_img.jpg deleted file mode 100644 index 30bd2649487bea11d002e7dd1ad569059667cab4..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/683f755e8456c884716de4fce48c7e63_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bafc110ca737aeef57347003ab2e4046f2d813d29c745471fe89682b234b1a4c -size 77784 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index a1a021c6cced459e5a30319f5f0e9eb4cee8c91f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b15fb625969e26fe1f45975f7f45e9ff2d2a2b3a3006dbcaef44fb07ddd8d3bb -size 4016 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg deleted file mode 100644 index a5b70d053f0259dd9abd40ca1c405f5126864f85..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d6962f21a79a58934041f5e7da800a35db86bf426226a2046d09b63ea1e8d7c2 -size 47050 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 44e4ca1e706fffc218594e75b7fbdfaeee43149d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ba36991bdae993881d357810ae680e8b2718eeb75c0831521a0cdc2d6e038f2 -size 4147 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 1ac866ebfe23959f91f71ac6485464d244ed172c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f0a7ae7e68d01cb903e9a35065f8afbf9764231801e9dc07633e72a6d3a25f1d -size 4016 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index 1ac866ebfe23959f91f71ac6485464d244ed172c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f0a7ae7e68d01cb903e9a35065f8afbf9764231801e9dc07633e72a6d3a25f1d -size 4016 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 01f614a1e0e5648a0339df067b86427c2fe9235a..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a683579c8b933ad9017cc5b1f2298ecddc35a3de23928756863e48366ef64b96 -size 4116 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index a1a021c6cced459e5a30319f5f0e9eb4cee8c91f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b15fb625969e26fe1f45975f7f45e9ff2d2a2b3a3006dbcaef44fb07ddd8d3bb -size 4016 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index e9d056186f91071754a1bd66cc5b0f58f9cdcd1d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a6feea577002af775f92c1c073ef8e278549447e23549760a568e59d2a4c42d6 -size 4142 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index a1a021c6cced459e5a30319f5f0e9eb4cee8c91f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8b4befaffc5166da571069410e207aea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b15fb625969e26fe1f45975f7f45e9ff2d2a2b3a3006dbcaef44fb07ddd8d3bb -size 4016 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 7bb52889b4dd8315b417109b949eb9b55344577f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f0b560c704079673d03ecbab5a426639c3fe9e99d3ce5708edc072d9324b5ce7 -size 4013 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 1624885035e55cf6001c2009d780b95cc6680b68..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c92f80674dbfe05e46caab62e5fda53b55f3ffd6f04aadb315c070b5286ef4d9 -size 4189 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg deleted file mode 100644 index 2e9bac872089a944be618bc1bf494d8be38101d3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f94d0d0729e07ee4eb96f7183bfa8d2d8edd090c551f7e90172a4baee25df8a2 -size 74337 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index a1a021c6cced459e5a30319f5f0e9eb4cee8c91f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b15fb625969e26fe1f45975f7f45e9ff2d2a2b3a3006dbcaef44fb07ddd8d3bb -size 4016 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index e9d056186f91071754a1bd66cc5b0f58f9cdcd1d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a6feea577002af775f92c1c073ef8e278549447e23549760a568e59d2a4c42d6 -size 4142 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/935075de5250cfe8aa0fb9d65d63dde5_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/935075de5250cfe8aa0fb9d65d63dde5_img.jpg deleted file mode 100644 index 46978ba891af1ef7dd440bedaf282a18cf7ebbba..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/935075de5250cfe8aa0fb9d65d63dde5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f99426b100299acf1dedfd7f6a872ad28fc3c4873615730ce94d46ccedf815da -size 90059 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index 44e4ca1e706fffc218594e75b7fbdfaeee43149d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ba36991bdae993881d357810ae680e8b2718eeb75c0831521a0cdc2d6e038f2 -size 4147 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 1624885035e55cf6001c2009d780b95cc6680b68..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c92f80674dbfe05e46caab62e5fda53b55f3ffd6f04aadb315c070b5286ef4d9 -size 4189 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 7bb52889b4dd8315b417109b949eb9b55344577f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f0b560c704079673d03ecbab5a426639c3fe9e99d3ce5708edc072d9324b5ce7 -size 4013 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 44e4ca1e706fffc218594e75b7fbdfaeee43149d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ba36991bdae993881d357810ae680e8b2718eeb75c0831521a0cdc2d6e038f2 -size 4147 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a93de4c3f80bd4a972ab65510b09b68d_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a93de4c3f80bd4a972ab65510b09b68d_img.jpg deleted file mode 100644 index c0b6ecdf0cbd1dbb065da105a88f3a9be35b3eee..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/a93de4c3f80bd4a972ab65510b09b68d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:12777480ce45925713aeba460f0b4ceee0ff62d85039ee1bc1aa9fbe9b31cf67 -size 76939 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 57c1ec40ddd8b65e207ef8b2cf9bc077c1ef5c94..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:824af40599b843085c67553baa10788d2a863049341844c656cd06dd0efa3f1b -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 64086a4d244aa3db8b0677e77b789f740d9f4c5b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9ce3defd2f5798109734f8ce61fd1df9c7d34820ed350d272ad3c84b6036042d -size 4038 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 57c1ec40ddd8b65e207ef8b2cf9bc077c1ef5c94..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:824af40599b843085c67553baa10788d2a863049341844c656cd06dd0efa3f1b -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index 0bea580b82b985ec6bd9836785eb1050583f8682..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b724ecded9a829c53fd8c426a1ba2377d42d7ab25c4731fa9713baf07a0b7e07 -size 4085 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/cfaeb2934fffcb1f4690ab7de835c2e0_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/cfaeb2934fffcb1f4690ab7de835c2e0_img.jpg deleted file mode 100644 index 85a4dd0776cb142782525999a684558dcae95c84..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/cfaeb2934fffcb1f4690ab7de835c2e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:363c44588a1e96cdd84895821a2f83afe7d3d21e1ead71b4d0a78cd4e36ed115 -size 33496 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/d17f75945bbb3feb84a153ecfedb9b81_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/d17f75945bbb3feb84a153ecfedb9b81_img.jpg deleted file mode 100644 index 9c429e981ba1164a97fb3bc9c4593893462dc77f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/d17f75945bbb3feb84a153ecfedb9b81_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2c19f388038f43375baf418580aaed5b62956ac1cc670b28329b58993da479ed -size 59915 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 44e4ca1e706fffc218594e75b7fbdfaeee43149d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ba36991bdae993881d357810ae680e8b2718eeb75c0831521a0cdc2d6e038f2 -size 4147 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg deleted file mode 100644 index 76cfc90557c538f094f2700bf0d0b262f91a7bb6..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4b5c49dc1ddc519b0b608282280883aee6aaea1172e8257664625924efbf4bfd -size 51492 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index 1ac866ebfe23959f91f71ac6485464d244ed172c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f0a7ae7e68d01cb903e9a35065f8afbf9764231801e9dc07633e72a6d3a25f1d -size 4016 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e151d3468319b81f042ca232c4d82e4b_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e151d3468319b81f042ca232c4d82e4b_img.jpg deleted file mode 100644 index 2bdd0cb692ef2f096b81f2822dabfd8c10533ae6..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e151d3468319b81f042ca232c4d82e4b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33463185d1bd5d169069e3088ad8d8b50be1a832cbe4d4040ba647914d81f7aa -size 70962 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index ec88d6082dfd5503b0cbfffa3862f50f88126938..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:622bfe7b09145ac3d005d3201101345547a9e23cb2625c80440d22ad9dd8178d -size 4243 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 7b84e262d2fc7e0b59b4101053a42526958b946a..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0e7bdaaf5aacb655dae815886fc7e68b08115ae4458078ccf72b022c81a0a12c -size 4142 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/ec3647789b5c38fb686f2a0833324e79_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/ec3647789b5c38fb686f2a0833324e79_img.jpg deleted file mode 100644 index 146b64b08fc410b79888d1294e7f1c5e06660ff3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/ec3647789b5c38fb686f2a0833324e79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:de58c602927bc1d6668517e4eee1ec4873701f901dad7ee52b0679feb1c07aea -size 74409 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/f74adaa1840504407cd4272995426f82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index a825d9b99f911d8f827b9553283b5ad21813fd46..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0b8fe5d6b51586629e54302f8e923644b5ad824f552cbb388a721c71c2fdb5bf -size 4236 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 16f69ca6f4dc8ac70058a985232016fd0a4036e1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57769fc40f2cb6d817c4e88040d076910f70f9697b597fdb52add39c8b9ebcdc -size 4026 diff --git a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg b/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg deleted file mode 100644 index 2368d5ea2d1acff01349031d0b3e1c2a459e4034..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Certficate-Management-Framework.0-R005-v06.00/images/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1f4625e11fe3cea3c66840aa55953822fd38eca56976aebab1280582ab6e112b -size 87115 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/doc.md b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/doc.md deleted file mode 100644 index 5035088a0fb201bae321d51a42fca729486c03ee..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/doc.md +++ /dev/null @@ -1,2725 +0,0 @@ - - -![O-RAN ALLIANCE logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) - -The logo for the O-RAN ALLIANCE, featuring a colorful circular icon to the left of the text "O-RAN" in blue, with "ALLIANCE" in smaller blue letters underneath. - -O-RAN ALLIANCE logo - -# --- **O-RAN Work Group 11 (Security Work Group)****Study on Security for O-Cloud** - -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. - -# Contents - -| | | -|---------------------------------------------------------|----| -| List of figures ..... | 4 | -| List of tables ..... | 4 | -| Foreword ..... | 5 | -| Modal verbs terminology ..... | 5 | -| Introduction ..... | 5 | -| 1 Scope..... | 6 | -| 2 References..... | 6 | -| 2.1 Informative references..... | 6 | -| 3 Definition of terms, symbols and abbreviations ..... | 10 | -| 3.1 Terms..... | 10 | -| 3.2 Symbols..... | 11 | -| 3.3 Abbreviations ..... | 11 | -| 4 O-Cloud Architecture..... | 14 | -| 4.1 Components..... | 14 | -| 4.1.1 SMO ..... | 14 | -| 4.1.2 O-Cloud management components ..... | 15 | -| 4.1.3 Hardware resources ..... | 15 | -| 4.1.4 Operating System (OS)..... | 15 | -| 4.1.5 Virtualization Layer..... | 15 | -| 4.1.6 NFs Layer ..... | 15 | -| 4.1.7 O-Cloud images repository..... | 15 | -| 4.2 Interfaces ..... | 16 | -| 4.3 Critical services..... | 18 | -| 4.3.1 SERV#01 SMO-O-Cloud O2 services ..... | 18 | -| 4.3.2 SERV#02 O-Cloud images service ..... | 19 | -| 4.3.3 SERV#03 O-Cloud monitoring service..... | 19 | -| 4.3.4 SERV#04 O-Cloud provisioning service ..... | 20 | -| 4.3.5 SERV#05 O-Cloud software management service ..... | 20 | -| 4.3.6 SERV#06 O-Cloud fault management service..... | 20 | -| 4.3.7 SERV#07 O-Cloud performance service ..... | 21 | -| 4.3.8 Void..... | 21 | -| 4.3.9 SERV#009 O-Cloud Inventory ..... | 21 | -| 5 Cloud deployment scenarios ..... | 22 | -| 5.1 Main actors..... | 22 | -| 5.2 Cloud service models ..... | 22 | -| 5.2.1 Infrastructure as a Service (IaaS)..... | 22 | -| 5.2.2 Platform as a Service (PaaS) ..... | 23 | -| 5.2.3 Software as a Service (SaaS)..... | 23 | -| 5.3 Cloud deployment types..... | 24 | -| 5.3.1 Private cloud..... | 24 | -| 5.3.2 Community Cloud ..... | 25 | -| 5.3.3 Public Cloud..... | 27 | -| 5.3.4 Hybrid Cloud..... | 27 | -| 5.4 High-Level risk assessment..... | 29 | -| 6 Roles and responsibilities..... | 34 | -| 7 Security Problem Definition ..... | 35 | -| 7.1 Assets ..... | 35 | -| 7.2 Threats..... | 38 | -| 7.2.1 Threat and impact types..... | 38 | -| 7.2.2 Attack surface..... | 39 | - -7.2.3 Vulnerabilities ..... 40 - -7.2.4 Threat events ..... 41 - -8 Recommendations and best practices ..... 69 - -8.1 REC-CM Certificate management ..... 70 - -8.2 REC-NS Network Segmentation & Filter Network Traffic ..... 70 - -8.3 REC-IAM Identity, Authentication and Access Management..... 72 - -8.4 REC-VHPM Vulnerability Handling and Patch Management ..... 75 - -8.5 REC-SCONF Security Configuration ..... 75 - -8.6 REC-SDLC Secure Development Lifecycle ..... 76 - -8.7 REC-SNFLC Security App/VNF/CNF lifecycle ..... 77 - -8.8 REC-IMGP Image Protection ..... 78 - -8.9 REC-LOG Logging, Monitoring and Alerting..... 80 - -8.10 REC-SB Secure Boot ..... 81 - -8.11 REC-ISO Strong Isolation..... 81 - -8.12 REC-AUD Security Audit..... 83 - -8.13 REC-SS Secure Storage ..... 84 - -8.14 REC-PHY Physical Security Protection ..... 84 - -8.15 REC-RA Remote Attestation ..... 86 - -8.16 REC-SDD Secure data deletion ..... 86 - -8.17 REC-IDM O-Cloud ID secure management ..... 87 - -8.18 REC-IDM Identity management for O-Cloud elements ..... 88 - -8.19 REC-ADMC Admission Control ..... 90 - -9 Risk Assessment ..... 91 - -Annex A (informative): Best practices from some of existing main security guidance ..... 92 - -A.1 CISA/NSA Kubernetes security hardening best practices ..... 92 - -A.2 CIS Docker security best practices..... 96 - -A.3 ONAP VNFs security best practices ..... 98 - -Annex: Change history/Change request (history) ..... 105 - -# --- List of figures - -| | | -|-----------------------------------------------------------------------------|----| -| Figure 4-1 : O-CLOUD architecture ..... | 14 | -| Figure 4-2 : AAL Architecture and interfaces (Source [i.52]) ..... | 18 | -| Figure 4-3 : Parallel reporting & Alarm correlation [i.1] ..... | 20 | -| Figure 5-1 : IaaS cloud service model..... | 23 | -| Figure 5-2 : PaaS cloud service model..... | 23 | -| Figure 5-3 : SaaS cloud service model..... | 24 | -| Figure 5-4 : On-site private cloud..... | 24 | -| Figure 5-5 : Outsourced private cloud ..... | 25 | -| Figure 5-6 : On-site community cloud..... | 26 | -| Figure 5-7 : Outsourced community cloud ..... | 26 | -| Figure 5-8 : Public cloud..... | 27 | -| Figure 5-9 : Hybrid cloud ..... | 28 | -| Figure 7-1 : Cartography of assets..... | 36 | -| Figure 7-2 : Attack vectors ..... | 44 | -| Figure 7-3 : Vulnerabilities within O-Cloud..... | 44 | -| Figure 7-4 : Illustration of the VM/Container escape attack ..... | 53 | -| Figure 7-5 : Illustration of the migration flooding attack ..... | 55 | -| Figure 7-6 : Illustration of the false resource advertising attack..... | 55 | -| Figure 7-7 : Illustration of the migration MITM attack..... | 55 | -| Figure 7-8 : Illustration of the Theft-of-Service/DoS Attack ..... | 57 | -| Figure 7-9 : Illustration of the VM/Container hyperjacking attack ..... | 61 | -| Figure 7-10 : Illustration of a cross VM/Container side channel attack..... | 65 | - -# --- List of tables - -| | | -|---------------------------------------------------------------------------------|----| -| Table 4-1 : O-Cloud interfaces..... | 19 | -| Table 5-1 : High level security risk assessment of cloud deployment models..... | 34 | -| Table 6-1 : List of Users ..... | 36 | -| Table 7-1 : List of Assets..... | 42 | - -# --- Foreword - -This Technical Report (TR) has been produced by WG11 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 technical report provides the threat model for the O-Cloud. The report identifies threats, security requirements and recommends potential security controls to protect against identified threats. - -# 1 Scope - -The steps of the threat modelling process are as follows: - -1. Identify assets: Identify the valuable assets that the O-Cloud must protect. -2. Identify the threats: Identify the threats that could affect O-Cloud -3. Document the threats: Document each threat using a common threat template that defines a core set of attributes to capture for each threat. -4. Rate the threats: Rate the threats to prioritize and address the most significant threats first. The rating process weighs the probability of the threat against damage that could result should an attack occur. -5. Define potential mitigations to counter the identified threats and reduce their risks. - -The structure of the document is divided into clauses and annexure(s): - -- Clause 4 describes the O-Cloud architecture in terms of components, interfaces, and critical services. -- Clause 5 explores the different deployment types and models. In addition, it provides a high-level risk assessment of those cloud deployment models. -- Clause 6 highlights the main actors of the O-Cloud in terms of roles and responsibilities. -- Clause 7 outlines the security problem definition in terms of assets, attack vectors, vulnerabilities and threats. -- Clause 8 defines recommendations and best practices to mitigate the identified threats. -- Clause 9 figures out the risk assessment of the identified threats in terms of impact and likelihood. -- Annex A provides best practices from some of the main security guidance on cloud, virtualization and containerization. - -# 2 References - -## 2.1 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.WG6.TS.O2-GA&P: “O2 Interface General Aspects and Principles” - -[i.2] O-RAN-WG6.ORCH-USE-CASES: “Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN” - -[i.3] CISA/NSA - Kubernetes Hardening Guidance – August 2022 - -[https://media.defense.gov/2022/Aug/29/2003066362/-1-/1/0/CTR\\_KUBERNETES\\_HARDENING\\_GUIDANCE\\_1.2\\_20220829.PDF](https://media.defense.gov/2022/Aug/29/2003066362/-1-/1/0/CTR_KUBERNETES_HARDENING_GUIDANCE_1.2_20220829.PDF) - -[i.4] MITRE ATT&CK containers matrix - - - -- [i.5] ENISA Threat Landscape for 5G Networks: Threat assessment for the fifth generation of mobile telecommunications networks (5G); November 2019 - - [i.6] ETSI GS NFV-SEC 025 "work in progress." Network Functions Virtualisation (NFV) Release 4; Security; Secure End-to-End VNF and NS management specification - - [i.7] O-RAN.WG6.O2DMS-INTERFACE-ETSI-NFV-PROFILE: "O2dms Interface Specification: Profile based on ETSI NFV Protocol and Data Models" - - [i.8] O-RAN.WG6.TS.O2IMS-INTERFACE: "O2ims Interface Specification" - - [i.9] IETF RFC 3647: "Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework" - - [i.10] ETSI GR NFV-SEC 005 Network Functions Virtualisation (NFV); Trust; Report on Certificate Management - - [i.11] IETF RFC 6749: "The OAuth 2.0 Authorization Framework". - - [i.12] ETSI GS NFV-SEC 022 Network Functions Virtualisation (NFV) Release 2; Security; Access Token Specification for API Access - - [i.13] ETSI GR NFV-SEC 018 Network Functions Virtualisation (NFV); Security; Report on NFV Remote Attestation Architecture - - [i.14] Ludovic Jacquin, Antonio Lioy, Diego R. Lopez, Adrian L. Shaw, and Tao Su "The trust problem in modern network infrastructures" -- [https://security.polito.it/doc/public/trust\\_modern\\_network\\_2015.pdf](https://security.polito.it/doc/public/trust_modern_network_2015.pdf) -- [i.15] ETSI GR NFV-SEC 007 Network Functions Virtualisation (NFV); Trust; Report on Attestation Technologies and Practices for Secure Deployments - - [i.16] 3GPP TR 33.848 "Study on security impacts of virtualisation" - - [i.17] OWASP Container Security Verification Standard -- -- [i.18] CIS Docker Benchmark Securing Docker -- -- [i.19] NIST Special Publication 800-190 Application Container Security Guide - - [i.20] OWASP Docker Security Cheat Sheet -- [https://cheatsheetseries.owasp.org/cheatsheets/Docker\\_Security\\_Cheat\\_Sheet.html](https://cheatsheetseries.owasp.org/cheatsheets/Docker_Security_Cheat_Sheet.html) -- [i.21] OWASP Kubernetes Security Cheat Sheet -- [https://cheatsheetseries.owasp.org/cheatsheets/Kubernetes\\_Security\\_Cheat\\_Sheet.html](https://cheatsheetseries.owasp.org/cheatsheets/Kubernetes_Security_Cheat_Sheet.html) -- [i.22] NIST SP 800-145: The NIST Definition of Cloud Computing - - [i.23] NIST SP 500-322: Evaluation of Cloud Computing Services Based on NIST 800-145 - - [i.24] ONAP VNF Development Requirements – VNF Security -- -- [i.25] GSMA NG.126 - Cloud Infrastructure Reference Model -- -- [i.26] Aqua Top 20 Docker Security Best Practices: Ultimate Guide - - - -[i.27] “Security Impacts of Virtualization on a Network Testbed”, Software Security and Reliability (SERE), 2012 IEEE Sixth International Conference - -[https://www.researchgate.net/publication/261059755\\_Security\\_Impacts\\_of\\_Virtualization\\_on\\_a\\_Network\\_Testbed](https://www.researchgate.net/publication/261059755_Security_Impacts_of_Virtualization_on_a_Network_Testbed) - -[i.28] Beniel Dennyson W, Dr. S. Prabakaran “Detecting Hyperjacking in cloud based virtual environment” - -[https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwi92Zeznun0AhULHXoKHXO6AkgQFnoECAgQAO&url=http%3A%2F%2Fsersc.org%2Fjournals%2Findex.php%2FIJAST%2Farticle%2Fdownload%2F15440%2F7789%2F&usg=AOvVaw3THwuT\\_S\\_WyKr6miOij7GS](https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwi92Zeznun0AhULHXoKHXO6AkgQFnoECAgQAO&url=http%3A%2F%2Fsersc.org%2Fjournals%2Findex.php%2FIJAST%2Farticle%2Fdownload%2F15440%2F7789%2F&usg=AOvVaw3THwuT_S_WyKr6miOij7GS) - -[i.29] Muhammad Kazim “Security Aspects of Virtualization in Cloud Computing” - -[https://www.researchgate.net/publication/273950406\\_Security\\_Aspects\\_of\\_Virtualization\\_in\\_Cloud\\_Computing](https://www.researchgate.net/publication/273950406_Security_Aspects_of_Virtualization_in_Cloud_Computing) - -[i.30] Anita Choudhary “ A critical survey of live virtual machine migration techniques “ - - - -[i.31] Svetlana Kolesnikova, Roman Kulikov, Yuriy Gatchin, Daniil Melnik “Hypervisor Security Analyses Based on Ishikawa Methodology” - -[https://www.researchgate.net/publication/323838205\\_Hypervisor\\_Security\\_Analyses\\_Based\\_on\\_Ishikawa\\_Methodology?enrichId=rgreq-bf37d66002988b1ad9ef24fb09198313-XXX&enrichSource=Y292ZXJQYWdlOzMyMzgODIwNTtBUzo2MDg0MzY3NTI0ODIzMDVAMTUyMjA3NDAzNDM4NQ%3D%3D&el=1\\_x\\_3&\\_esc=publicationCoverPdf](https://www.researchgate.net/publication/323838205_Hypervisor_Security_Analyses_Based_on_Ishikawa_Methodology?enrichId=rgreq-bf37d66002988b1ad9ef24fb09198313-XXX&enrichSource=Y292ZXJQYWdlOzMyMzgODIwNTtBUzo2MDg0MzY3NTI0ODIzMDVAMTUyMjA3NDAzNDM4NQ%3D%3D&el=1_x_3&_esc=publicationCoverPdf) - -[i.32] Mehiar Dabbagh, Ammar Rayes “Internet of Things Security and Privacy” - -[https://www.researchgate.net/publication/309375790\\_Internet\\_of\\_Things\\_Security\\_and\\_Privacy?enrichId=rgreq-69e8c33eb9fc28fccec64fbdad0a91d0-XXX&enrichSource=Y292ZXJQYWdlOzMwOTM3NTc5MDtBUzo1NTYxNDY2NDI2OTAwNDhAMTUwOTYwNzEwMDM0OA%3D%3D&el=1\\_x\\_3&\\_esc=publicationCoverPdf](https://www.researchgate.net/publication/309375790_Internet_of_Things_Security_and_Privacy?enrichId=rgreq-69e8c33eb9fc28fccec64fbdad0a91d0-XXX&enrichSource=Y292ZXJQYWdlOzMwOTM3NTc5MDtBUzo1NTYxNDY2NDI2OTAwNDhAMTUwOTYwNzEwMDM0OA%3D%3D&el=1_x_3&_esc=publicationCoverPdf) - -[i.33] Changwei Liu, Anoop Singhal, Duminda Wijesekera “A Layered Graphical Model for Cloud Forensic Mission Attack Impact Analysis” - -[https://www.researchgate.net/publication/327314423\\_A\\_Layered\\_Graphical\\_Model\\_for\\_Cloud\\_Forensic\\_Mission\\_Attack\\_Impact\\_Analysis\\_14th\\_IFIP\\_WG\\_119\\_International\\_Conference\\_New\\_Delhi\\_India\\_January\\_3-5\\_2018\\_Revised\\_Selected\\_Papers?enrichId=rgreq-b9ce99f09429d1a36256442e04006d0f-XXX&enrichSource=Y292ZXJQYWdlOzMyNzMXNDQyMztBUzo3NTM0MDM2MzgIODMzMDAMTUINjYzNjgzMzI4Nw%3D%3D&el=1\\_x\\_3&\\_esc=publicationCoverPdf](https://www.researchgate.net/publication/327314423_A_Layered_Graphical_Model_for_Cloud_Forensic_Mission_Attack_Impact_Analysis_14th_IFIP_WG_119_International_Conference_New_Delhi_India_January_3-5_2018_Revised_Selected_Papers?enrichId=rgreq-b9ce99f09429d1a36256442e04006d0f-XXX&enrichSource=Y292ZXJQYWdlOzMyNzMXNDQyMztBUzo3NTM0MDM2MzgIODMzMDAMTUINjYzNjgzMzI4Nw%3D%3D&el=1_x_3&_esc=publicationCoverPdf) - -[i.34] Docker Best practices for scanning images - - - -[i.35] Shankar Lal, Tarik Taleb, and Ashutosh Dutta “NFV: Security Threats and Best Practices” - -[http://anastacia-h2020.eu/publications/NFV\\_Security\\_Threats\\_and\\_Best\\_Practices.pdf](http://anastacia-h2020.eu/publications/NFV_Security_Threats_and_Best_Practices.pdf) - -[i.36] NSA/CISA Mitigating Cloud Vulnerabilities - -[https://media.defense.gov/2020/Jan/22/2002237484/-1/-1/0/CSI-MITIGATING-CLOUD-VULNERABILITIES\\_20200121.PDF](https://media.defense.gov/2020/Jan/22/2002237484/-1/-1/0/CSI-MITIGATING-CLOUD-VULNERABILITIES_20200121.PDF) - -[i.37] Fraunhofer AISEC report: Threat analysis of container-as-a-service for network function virtualization - -[https://www.aisec.fraunhofer.de/content/dam/aisec/Dokumente/Publikationen/Studien\\_TechReports/englisch/caas\\_threat\\_analysis\\_wp.pdf](https://www.aisec.fraunhofer.de/content/dam/aisec/Dokumente/Publikationen/Studien_TechReports/englisch/caas_threat_analysis_wp.pdf) - -[i.38] CSA. The treacherous 12: Cloud computing top threats in 2016. Technical report, Cloud Security Alliance, 2016. 12, 14, 15, 16, 17, 27 - -[i.39] ETSI GS NFV-SOL 013 Network Functions Virtualisation (NFV) Release 2; Protocols and Data Models; Specification of common aspects for RESTful NFV MANO APIs - -[i.40] CISA Cloud Security Technical Reference Architecture - -[https://www.cisa.gov/sites/default/files/publications/CISA%20Cloud%20Security%20Technical%20Reference%20Architecture\\_Version%201.pdf](https://www.cisa.gov/sites/default/files/publications/CISA%20Cloud%20Security%20Technical%20Reference%20Architecture_Version%201.pdf) - -[i.41] Guide ANSSI - Hardware security requirements for x86 platforms - -[https://www.ssi.gouv.fr/uploads/2019/11/anssi-guide-hardware\\_security\\_requirements.pdf](https://www.ssi.gouv.fr/uploads/2019/11/anssi-guide-hardware_security_requirements.pdf) - -[i.42] O-RAN.WG11.TS.SRCS: "Security Requirements and Controls Specifications" - -[i.43] O-RAN.WG10.TS.OAM-Architecture: "O-RAN Operations and Maintenance Architecture" - -[i.44] NSA/CISA Security Guidance for 5G Cloud Infrastructures - - - -[i.45] O-RAN.WG11.TS.SecProtSpec: "Security Protocols Specifications" - -[i.46] ETSI GS NFV-SOL 004 Network Functions Virtualisation (NFV) Release 3; Protocols and Data Models; VNF Package and PNFD Archive specification - -[i.47] ETSI GS NFV-SEC 021 Network Functions Virtualisation (NFV) Release 2; Security; VNF Package Security Specification - -[i.48] NIST SP 800-88 "Guidelines for Media Sanitization" - - - -[i.49] DoD 5220.22-M wiping standard - -[i.50] O-RAN.WG11.TR.Threat-Modeling: "O-RAN Security Threat Modeling and Risk Assessment" - -[i.51] O-RAN.WG6.AAL Common API: "Acceleration Abstraction Layer Common API" - -[i.52] O-RAN.WG6.AAL-GAnP: "O-RAN Acceleration Abstraction Layer General Aspects and Principles" - -[i.53] Solving the Bottom Turtle - a SPIFFE Way to Establish Trust in Your Infrastructure via Universal Identity - - - -[i.54] SPIRE Concepts: An overview of SPIRE's architecture and fundamentals - - - -[i.55] Kubernetes Documentation: PKI certificates and requirements - - - -[i.56] Agent plugin: WorkloadAttestor "k8s" - -[https://github.com/spiffe/spire/blob/v1.7.0/doc/plugin\\_agent\\_workloadattestor\\_k8s.md](https://github.com/spiffe/spire/blob/v1.7.0/doc/plugin_agent_workloadattestor_k8s.md) - -[i.57] SPIFFE-ID - - - -[i.58] NIST Special Publication 800-207A - - - -[i.59] CWE-524, "Use of Cache Containing Sensitive Information" - - - -[i.60] CAPEC-204, “Lifting Sensitive Data Embedded in Cache” - - - -[i.61] Infiltrating Corporate Intranet Like NSA - - - -[i.62] Void - -[i.63] O-RAN.WG6.CADS: “Cloud Architecture and Deployment Scenarios for O-RAN Virtualized RAN” - -[i.64] NIST glossary: - -[i.65] O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE: “O2dms Interface Specification: Kubernetes Native API Profile for Containerized NFs” - -# --- 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 and the following apply: - -**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 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. - -**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. - -**Deployment ID:** Correlation Identity created by the O-Cloud for the SMO to relate to its inventory and manage. - -**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 this version of the specification, 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 real-time control and optimization of RAN elements and resources via fine-grained data collection and actions over E2 interface. - -**NF Deployment:** An O-Cloud NF Deployment is a deployment of a cloud native Network Function (all or partial), resources shared within a NF Function, or resources shared across network functions. The NF Deployment configures and assembles user-plane resources required for the cloud native construct used to establish the NF Deployment and manage its life cycle from creation to deletion (Refer to clause 1.3.1 O-RAN WG6.GA&P [i.1]). - -**NF Deployment Descriptor:** A completed data model which provides an O-Cloud the necessary information to create a deployment. - -**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-Cloud:** O-RAN cloud is a distributed cloud composed of Cloud Resource Pools where each pool is a collection of Cloud Resources within a Cloud Site with a specific location. [i.1] - -**O-Cloud instance ID:** The O-Cloud instance ID is a unique identifier assigned to components within the O-Cloud platform, including VMs, pods, containers, nodes, and compute pools (i.e., a cluster in Kubernetes). This ensures uniqueness across the entire O-Cloud environment, irrespective of the component type. For instance, a VM, a pod, a container, a node, and a cluster will each have a distinct O-Cloud instance ID within the platform, ensuring that there is no ambiguity in identification. - -**O-Cloud Node:** An O-Cloud Node is exposed over OZims as an Abstracted Resource. It is a collection of CPUs, Mem, Storage, NICs, Accelerators, BIOSes, BMCs, etc., and can be thought of as a server (Refer to clause 3.1 in O-RAN WG6.GA&P [i.1]). - -**O-Cloud Resource:** Refer to clause 3.4.3.2.1 in O-RAN WG6.GA&P [i.1] - -**O-Cloud Software:** The O-Cloud software refers to a collection of Host OS, Hypervisor/Container engine, AAL (Acceleration Abstraction Layer), IMS, DMS, HAM (Hardware Accelerator Manager), and supporting software in O-Cloud to run VNFs/CNFs. [i.63] - -**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 shall 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. - -**Sensitive:** A descriptor of information whose loss, misuse, or unauthorized access or modification could adversely affect security [i.64]. - -**Service Provider:** A network provider who is planning to deploy applications into their network. - -**Solution Provider:** An application developer who delivers applications to Service Providers. - -**Workload** - Refer to clause 3.4.3.1 in O-RAN WG6.GA&P [i.1] - -**NOTE:** For the purposes of the present document, the AAL terms and definitions given in [i.52] apply. - -## 3.2 Symbols - -Void - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 and the following apply: - -| | | -|-------------|-------------------------------------------------------------| -| AAL | Acceleration Abstraction Layer | -| AALI | Acceleration Abstraction Layer Interface | -| AALI-C | Acceleration Abstraction Layer Interface-Common | -| AALI-C-App | Acceleration Abstraction Layer Interface-Common-Application | -| AALI-C-Mgmt | Acceleration Abstraction Layer Interface-Common-Management | -| AALI-P | Acceleration Abstraction Layer Interface-Profile | - -| | | -|---------|-------------------------------------------------------------------------------------------------------------| -| AI/ML | Artificial Intelligence/Machine Learning | -| CNF | Cloud-native Network Function (NOTE: same as Containerized Network Function or Cloudified Network Function) | -| DMS | O-Cloud Deployment Management Services | -| eNB | eNodeB (applies to LTE) | -| FOCOM | Federated O-Cloud Orchestration & Management | -| FTP | File Transfer Protocol | -| FTPS | File Transfer Protocol Secure | -| gNB | gNodeB (applies to NR) | -| IMS | O-Cloud Infrastructure Management Services | -| IPSEC | Internet Protocol Security | -| KPI | Key Performance Indicator | -| KQI | Key Quality Indicator | -| LBT | Listen Before Talk | -| LCM | Life Cycle Management | -| LLS | Lower Layer Split | -| MIMO | Multiple Input, Multiple Output | -| MNO | Mobile Network Operator | -| NETCONF | Network Configuration Protocol | -| NF | Network Function | -| NFO | Network Function Orchestration | -| NFV | Network Function Virtualisation | -| NFVI | Network Function Virtualization Infrastructure | -| O-CU | O-RAN Central Unit as defined by O-RAN ALLIANCE | -| O-CU-CP | O-CU Control Plane | -| O-CU-UP | O-CU User Plane | -| O-DU | O-RAN Distributed Unit (uses Lower-level Split) | -| O-RU | O-RAN Radio Unit | -| PDCP | Packet Data Convergence Protocol | -| PNF | Physical Network Function | -| PRB | Physical Resource Block | -| PTP | Precision Timing Protocol | -| QoE | Quality of Experience | -| RAN | Radio Access Network | -| RASP | Runtime Application Self-Protection | -| RBAC | Role-based Access Control | -| RIC | O-RAN RAN Intelligent Controller | -| SDN | Software Defined Network | -| SIEM | Security information and event management | -| SINR | Signal-to-Interference-plus-Noise Ratio | -| SMO | Service Management and Orchestration | - -| | | -|-----|------------------------------| -| SSH | Secure Shell | -| TLS | Transport Layer Security | -| UAV | Unmanned Aerial Vehicle | -| V2X | Vehicle to Everything | -| VM | Virtual machine | -| VNF | Virtualised Network Function | - -# 4 O-Cloud Architecture - -The O-Cloud architecture is depicted in the following figure: - -![Diagram of O-Cloud architecture showing layers from SMO down to Hardware resources. The SMO contains Non RT RIC/rApps, NFO, and FOCOM. The O-Cloud contains VNF/CNF (O-DU, O-CU, Near RT RIC/xApps), a Virtualization Layer (VL) with Containers, VMs, and Hypervisors, and Hardware resources. Interfaces O1, A1, O2dms, and O2ims are shown between the SMO and O-Cloud components. An Images repository is connected to the SMO and O-Cloud.](bd671b21db63e6fdb2196e9b18502aac_img.jpg) - -The diagram illustrates the O-Cloud architecture layers and components: - -- SMO (Service Management and Orchestration):** The top layer, containing **Non RT RIC/rApps**, **NFO (Network Function Orchestrator)**, and **FOCOM (Federated O-Cloud Orchestration and Management)**. It connects to an **Images repository** and interfaces with the O-Cloud via **O1**, **A1**, **O2dms**, and **O2ims** interfaces. -- O-Cloud:** The main cloud layer, containing: - - VNF/CNF (Virtual Network Functions/Cloud Network Functions):** Includes **O-DU (O-RAN Distributed Unit)**, **O-CU (O-RAN Central Unit)**, and **Near RT RIC/xApps**, each connected via an **AAL (Adaptation Layer)**. - - O-Cloud API:** A central interface layer. - - Virtualization Layer (VL):** Manages **Containers** and **VMs** using **Container Engines** and **Hypervisors (Type I and Type II)**, supported by **Host OS** and **Guest OS**. - - Hardware resources:** The bottom layer, including **Compute**, **Storage**, **Network**, and a **Hardware Accelerator manager**. - -Diagram of O-Cloud architecture showing layers from SMO down to Hardware resources. The SMO contains Non RT RIC/rApps, NFO, and FOCOM. The O-Cloud contains VNF/CNF (O-DU, O-CU, Near RT RIC/xApps), a Virtualization Layer (VL) with Containers, VMs, and Hypervisors, and Hardware resources. Interfaces O1, A1, O2dms, and O2ims are shown between the SMO and O-Cloud components. An Images repository is connected to the SMO and O-Cloud. - -Figure 4-1 : O-CLOUD architecture - -## 4.1 Components - -The following clauses describe the functional blocks identified in Figure 4-1 [i.1], [i.2]: - -### 4.1.1 SMO - -The SMO components managing and orchestrating the O-Cloud software are: - -- Federated O-Cloud Orchestration and Management (FOCOM):** The FOCOM is responsible for accounting and asset management of the resources in the cloud. The FOCOM is the primary consumer of services provided by the IMS. The FOCOM has information about the O-Cloud resources management. Specifically, the FOCOM needs to know whether the services are within the operator domain or external. -- Network Function Orchestrator (NFO):** The NFO is responsible for orchestrating the assembly of the network functions as a composition of NF Deployments in the O-Cloud. It may also utilize OAM Functions in order to access the O1 interface to the NF once it is deployed. Its use of the O1 is not germane to the O2 and is only mentioned here for completeness. The NFO is the primary consumer of the DMS. - -### 4.1.2 O-Cloud management components - -The O-Cloud components providing management services for consumption of SMO are: - -- **Infrastructure Management Services (IMS):** The IMS is responsible for management of the O-Cloud resources and the software which is used to manage those resources. The IMS generally provides services for consumption by the FOCOM. -- **Deployment Management Services (DMS):** The DMS is responsible for management of NF Deployments into the O-Cloud. It provides the ability to instantiate, monitor, and terminate NF Deployments. The DMS generally provides services for consumption by the NFO. - -### 4.1.3 Hardware resources - -- **A Computer System** is defined to be a physical or composed system capable of performing computations that is Underlay-Network connected. A Computer System can run any major Operating System with or without Virtualization and/or Container support functionality. - -NOTE: A computer system in the context of a cloudified network and usage in cluster requires a network connectivity. For example, a server in a data center connected to an underlay network. - -- **An underlay network** is a physically connected network enabling Computer Systems to communicate with each other and with the gateway(s) connected to networks outside of the data center. -- **Hardware accelerator manager:** It is an acceleration management function, that provides management capabilities for the HW Accelerator(s) in the O-Cloud Node. Management capabilities include but not limited to lifecycle management, configuration, updates/upgrades and failure handling. Hardware Accelerators include ASIC, FPGA, DSP and GPU. - -### 4.1.4 Operating System (OS) - -An Operating system is a software platform that manages and abstracts the Computer System hardware and software resources as well as provides common services for NFs such as scheduling and network connectivity. - -### 4.1.5 Virtualization Layer - -- **Hypervisor (VMs):** An hypervisor is an OS that includes the ability to offer multiple Virtual Machines, each acting as a well-separated Computer System. -- **Container Engine:** A Container Engine is an OS that include the ability to offer multiple separated name spaces, quotas, and management for Containers. - -### 4.1.6 NFs Layer - -The following are three deployment scenarios of a NF: - -1. **Bare Metal Container Cluster** – A Bare Metal Container Cluster is a set of network-connected computer systems with their individual operating system instances that supports containers in a cluster configuration. -2. **VM-based Container Cluster** – A VM-based Container Cluster is a set of network-connected Virtual Machines with their individual guest operating system instance that supports containers in a clustered configuration. -3. **VM Cluster** – A VM Cluster is a set of network-connected Computer Systems with their individual operating instance that supports virtual machines in a cluster configuration. - -### 4.1.7 O-Cloud images repository - -The repository containing the Software Images of O-RAN Network Functions. - -## 4.2 Interfaces - -O-Cloud interfaces are illustrated in the following table: - -| Interfaces | Interface between | Exposure | Description | Security protection | -|------------|----------------------------------------------------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------| -| O2dms | SMO and O-Cloud Deployment Management Services (DMS) | External |

It is responsible for the deployment management services of the NF Deployment. It offers the following services APIs [i.7]:

  • • O2dms_DeploymentInventory Services
  • • O2dms_DeploymentProvisioning Services
  • • O2dms_DeploymentFault Services
  • • O2dms_DeploymentPerformance Services
  • • O2dms_DeploymentLifecycle Services
| TLS 1.2/1.3 | -| O2ims | SMO and O-Cloud Infrastructure Management Services (IMS) | External |

It is responsible for infrastructure management services for O-Cloud Nodes. It offers the following services APIs [i.8]:

  • • O2ims_InfrastructureInventory Services: Service for querying the O-Cloud resources and management services.
  • • O2ims_InfrastructureMonitoring Services: Service for configuring telemetry reporting of O-Cloud infrastructure resources.
  • • O2ims_InfrastructureProvisioning Services: Service for configuring the O-Cloud infrastructure resources and management services.
  • • O2ims_InfrastructureSoftwareManagement Services: Services for software inventory and updating the software used for O-Cloud infrastructure resources and management services.
  • • O2ims_InfrastructureLifecycleManagement Services: Services related to O-Cloud infrastructure lifecycle management and events.
| TLS 1.2/1.3 | -| O1 | SMO and the RAN managed functions | External |

SMO performs relevant configuration updates in RAN over O1 interface for each network function.

SMO on operator request can perform recover (reset) of an application (in case of failures) within a NF through the O1 interface.

SMO is notified of configuration events, fault events and performance measurements from an O-RAN NF instantiated on an O-Cloud, using the O1 interface.

SMO retrieves configuration data from NFs through O1.

| TLS 1.2/1.3 | - -| | | | | | -|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| -| O-Cloud APIs | O-Cloud infrastructure and VNFs/CNFs | Internal | The interface is used to specify interactions between the VNFs/CNFs and O-Cloud. The interfaces can be used by the VNFs/CNFs to register/deregister for receiving events from the O-Cloud. | HTTPS (HTTP over TLS) | -| Management (Tenant level APIs) | External interfaces are use case specific interfaces that are not standardized in O-RAN. Security of these interfaces is outside the scope of this work item and recommended to be outside the scope of the O-RAN Alliance. | External | APIs for the management (creation, deletion, and operation) of the Tenant, software flavours, Operating System and workload images, Identity and Authorization, virtual resources, security, and the workload application. | HTTPS | -| Enabler Service Interfaces | External interfaces are use case specific interfaces that are not standardized in O-RAN. Security of these interfaces is outside the scope of this work item and recommended to be outside the scope of the O-RAN Alliance. | External | An operational O-Cloud needs a set of standard services to function. Services such as NTP for time synchronization, DHCP for IP address allocation, DNS for obtaining IP addresses for domain names, and LBaaS to distribute incoming requests amongst a pool of designated resources. | HTTPS | - -Table 4-1 : O-Cloud interfaces - -AAL interfaces are as follows [i.51]: - -- AALI-C-Mgmt: between the O-Cloud IMS/DMS and the Hardware Accelerator Manager. It is consistent with O2 interface. -- AALI-C-App: common APIs between O-RAN NFs and the hardware accelerator device for initial discovery, AAL initialization, runtime operations, real time telemetry and status, etc. -- AALI-P: Profile specific API – fine grain control over selection and off-loading, etc. The AALI configuration and management APIs are the APIs that an application (O-DU) executes to configure and manage the AAL-LPU(s) that have been allocated to the application by the O-Cloud. -- Vendor specific interface between the hardware accelerator manager and hardware accelerator device. - -The transport between a NF and an AAL implementation can be of different types (e.g., based on shared memory, PCIe interconnect, over Ethernet). AALI-C-App shall support abstraction of these various transport mechanisms between a NF and an AAL implementation through a set of common transport APIs, constituting a transport abstraction framework. - -![AAL Architecture and interfaces diagram showing the hierarchy from SMO down to O-Cloud compute nodes. The SMO connects to the IMS and DMS via O2ims and O2dms interfaces. The IMS and DMS connect to the AAL-C-Mgmt, AAL-C-App, and AAL-P components, which in turn connect to the O-Cloud compute nodes (LP00, LP01, LP02, LPUn).](4356776ca004ecba5d599667a155d7d4_img.jpg) - -The diagram illustrates the AAL Architecture and interfaces. At the top, the SMO (Service Management and Orchestration) receives input from Planning, Design, CSAR Package, Manifest, artifacts etc. The SMO connects to the IMS (Inventory Management Service) and DMS (Defect Standards Management Service) via O2ims and O2dms interfaces. The IMS and DMS are connected to the AAL-C-Mgmt (AAL-C Management) component, which is consistent with the O2 Model. The AAL-C-Mgmt component is connected to the AAL-C-App (AAL-C Application) and AAL-P (AAL-P) components. The AAL-C-App and AAL-P components are connected to the O-Cloud compute node, which contains LP00, LP01, LP02, and LPUn. The O-Cloud compute node is connected to the Hardware Acceleration Manager (Vendor Specific). The IMS and DMS also have associated functions: IMS handles O-Cloud Logical Resource LPU FCAPS (Inventory Management/Capabilities discovery, Status, Fault, Log notification, Telemetry, Provisioning) and Manage and monitor Physical Resource (Status Faults/Alarms (Fan, temperature, etc.), Physical HW Telemetry, Software Firmware upgrades). The DMS handles Defect Standards (K8s, ETSI etc. LCM) and LCM and instantiation of the workload. The AAL-C-Mgmt, AAL-C-App, and AAL-P components are part of the AAL implementation. - -AAL Architecture and interfaces diagram showing the hierarchy from SMO down to O-Cloud compute nodes. The SMO connects to the IMS and DMS via O2ims and O2dms interfaces. The IMS and DMS connect to the AAL-C-Mgmt, AAL-C-App, and AAL-P components, which in turn connect to the O-Cloud compute nodes (LP00, LP01, LP02, LPUn). - -Figure 4-2 : AAL Architecture and interfaces (Source [i.52]) - -## 4.3 Critical services - -The following main critical services are provided by the O-Cloud components [i.1], [i.2] which need to be highly protected and securely maintained. They are identified in this report to assess the negative impact that the identified threats may cause on them. - -### 4.3.1 SERV#01 SMO-O-Cloud O2 services - -Using the O2 interface, the SMO can perform the following operations: - -- Provide a boot image for a remote node -- Send a cloud descriptor, (i.e., cloud deployment and configuration files) for initial cloud startup -- Query the O-Cloud for attributes such as SW inventory -- Send a request to O-Cloud to download software sent to it from the SMO, such as request for download of an xAPP deployment. -- Subscribe to notification of configuration events, fault events and performance measurements from the O-Cloud -- Query the O-Cloud for the DMS end points it supports -- Query the O-Cloud for attributes such as capabilities and capacities -- Request the O-Cloud to create a Network Function deployment using cloud resources -- Request the O-Cloud to terminate Network Function deployment(s) -- Request the O-Cloud to reset NF Deployment(s) - -- Request the O-Cloud to reset O-Cloud Node(s) -- Issue a subscription to the O-Cloud to receive alarm event notifications -- Query the O-Cloud for alarms on O-Cloud resources with query criteria which define the alarm characteristics that the SMO is interested in -- Query the O-Cloud for state and status information -- Perform an Alarm Subscription query towards the IMS -- Perform a NF deployment (that releases an NF instance) reset through the O2dms interface -- Perform an O-Cloud Node (recovery of the resources within the O-Cloud) reset through the O2ims interface - -Using the O2 interface, the O-Cloud can perform the following operations: - -- Send asynchronous events to the SMO when available capabilities or capacities are changed, including when new hardware is added -- Asynchronously notify the SMO when a software upgrade completes -- Asynchronously notify the endpoint specified by the SMO (alarm subscriber) of alarm notifications related to O-Cloud resources -- Return alarms in response to the SMO alarm query that match the alarm query criteria - -### 4.3.2 SERV#02 O-Cloud images service - -It provides Add/Delete/Update/Query functions of O-RAN Cloudified Network Functions images with their related information (e.g. SoftwareImageId, Vendor, and Version) from O-Cloud repository. - -### 4.3.3 SERV#03 O-Cloud monitoring service - -When the O-Cloud Infrastructure or the O-RAN cloudified NFs fails, it needs to be fixed immediately, and preferably automatically, to prevent end users from experiencing service disruptions. To avoid this service disruption Network Operations must consider the telemetry information of O-Cloud deployments in the network. The telemetry information serves as a vital resource for analysing the O-Cloud's state and health, and for delivering on service monitoring goals. The O-Cloud Monitoring Service uses telemetry data to provide monitoring of O-Cloud infrastructures. O-Cloud telemetry shall minimally consist of Fault, Performance, and Configuration Data. There are different types of telemetry: - -- **Managed Element Telemetry** to monitor the NFs behavior through O1. -- **Deployment Telemetry** to monitor the number of deployment instances an O-Cloud has at that moment and how many were expected, how the on-progress deployment is going, and health checks. Additional Deployment Telemetry metrics like CPU, network, and memory usage can also be collected. This will be performed through the O2dms interface. -- **Infrastructure Telemetry** to monitor the health of the O-Cloud Infrastructure components. Network Operations are interested in discovering if all the components in the O-Cloud Infrastructure are working properly and at what capacity, how many deployments are running on each node, and the resource utilization of the O-Cloud Infrastructure. This will be performed through the O2ims interface. - -The SMO shall be able to collect and correlate telemetries to aggregate problems to a root cause. - -The O-Cloud shall be able to report telemetries and make all Configuration Data and any external changes to it available to the SMO. - -### 4.3.4 SERV#04 O-Cloud provisioning service - -O-Cloud Provisioning is the allocation of O-Cloud's resources and services to an O-RAN Cloudified Network Function. This is one of the key functionalities of the O-Cloud, relating to how an O-RAN Cloudified Network Function procures O-Cloud services and resources. O-Cloud Provisioning shall provide: - -- Create/Read/Update/Delete rules for Affinity, Anti-Affinity, and Quorum Diversity -- Query of O-Cloud Capacity & Availability - -### 4.3.5 SERV#05 O-Cloud software management service - -Software management will manage the O-Cloud software. The software management should be a priority as without proper management unnecessary risks may be taken. The software management ensures security, cost management and software support. There are many benefits to software management, of which the main benefits are: - -- Prevents unauthorized software from being installed -- Maintains a catalog of authorized software and its versions -- Provides visibility into what software and version is being used -- Provides a better view of which software products and versions are vendor supported - -In O-RAN from an O-Cloud perspective there are two types of software which needs to be managed on the O2 Interface: - -- The O-Cloud Infrastructure Software -- The O-RAN Cloudified Network Function Software is the software implementation of O-RAN NFs which can run over the O-Cloud - -### 4.3.6 SERV#06 O-Cloud fault management service - -It is related to IMS & DMS fault management. There are three types of fault notifications that originate from O-Cloud and collected by SMO through O1, O2dms and O2ims. - -- Fault notifications originate from the O-cloud infrastructure when a condition occurs within IMS on an O-Cloud resource. An event is issued towards the SMO for analysis. The SMO can issue a specific fault query towards to IMS related to the O-Cloud resources and resource pool through O2ims. -- DMS resource faults are associated with a workload. The SMO can issue a specific query related to xApp/NF deployments (e.g. workloads) from the DMS through O2dms. -- NFs faults are reported through O1 (application level). - -![Diagram illustrating Parallel reporting & Alarm correlation. The diagram shows a hierarchy of components: SMO (Management) at the top, containing FOCOM and NFO; Applications (Applications) below SMO; Workloads (DMS Workloads) below Applications; and IMS Resources (IMS Resources) at the bottom, represented by a server rack icon. Arrows indicate reporting paths: O2ims from IMS Resources to SMO, O2dms from Workloads to SMO, and O1 from Applications to SMO.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) - -Diagram illustrating Parallel reporting & Alarm correlation. The diagram shows a hierarchy of components: SMO (Management) at the top, containing FOCOM and NFO; Applications (Applications) below SMO; Workloads (DMS Workloads) below Applications; and IMS Resources (IMS Resources) at the bottom, represented by a server rack icon. Arrows indicate reporting paths: O2ims from IMS Resources to SMO, O2dms from Workloads to SMO, and O1 from Applications to SMO. - -Figure 4-3 : Parallel reporting & Alarm correlation [i.1] - -It is possible that multiple resources can associate with a workload, whereby one fault might trigger a fault notification on IMS, DMS and O1. - -For example, it is conceivable that a O-DU application might report a fault on O1, and a related physical server allocated to a workload of a O-DU would raise a DMS fault which might also have an infrastructure fault raised on IMS. - -For example, the SMO may receive a fault with a root cause of a network issue among the O-Cloud resources which manifests itself in a deployment and application fault as well. Thus, the SMO might receive three notifications over O2ims, O2dms and O1. It might correlate these faults to a common root cause. - -NOTE: Faults issued by the O-Cloud could be stored at the O-Cloud resource for a configured amount of time. - -### 4.3.7 SERV#07 O-Cloud performance service - -The purpose of performance service is to report operational information related to O-cloud resources. Typically, performance information allows an operator or administrator of the O-cloud a sense of how well the system is operating. It is distinct from faults in that it is not about failures in the system but about how well the overall system is performing. Though, faults or alarms may negatively impact performance of the O-Cloud which might be observable in performance measurements. - -Performance measurements are typically captured periodically through time. They are collected and stored at regular intervals by the system in order to gauge the performance of a system over a period of time. This allows for analytical operations to be performed on the collected data and statistics to be built over time. This can tell an operator or system analyst whether they have sufficient capacity in a network based on the demands of the network. This can be vital for making business operational decisions such as scaling a network. - -### 4.3.8 Void - -### 4.3.9 SERV#009 O-Cloud Inventory - -O-Clouds contain physical, software and logical resources. The O-Cloud is the source of information for these assets but is required to provide a mechanism for asset management to account for them. The inventory services provide the read-only interface to its inventory such that accounting can be achieved (see O-RAN O2ims Interface Specification [i.8]). One of the responsibilities of the SMO is for “financial” accounting of the physical and logical inventory. The SMO inquires about the mapping of resources to their use. The O-Cloud is responsible for the assignment of resources to their use. Typically, the O-Cloud inventory is the result of the SMO provisioning requests and assignments of O- - -Cloud Resources with additions of O-Cloud internal status of the existing internal resources, e.g., if some of the resources are down due to faults or maintenance operations (see O-RAN WG6.GA&P [i.1]). - -**Infrastructure Inventory** - Infrastructure inventory plays a pivotal role in the management and allocation of O-Cloud resources. It involves the use of an immutable O-Cloud Resource Identifier to track resources efficiently. This identifier aids in correlating inventory data, which includes provisioning status and operational insights. - -**Logical Inventory** - Logical inventory involves managing the Deployment Management Services (DMS) that support various virtual cluster technologies, such as Kubernetes and OpenStack. Each DMS endpoint acts as an interface for deployments, cataloged by the SMO as a Logical Cloud. This inventory segment assists the SMO in selecting appropriate O-Cloud environments for deployments. - -**Deployment Inventory** - Focusing on the deployment aspect, the inventory includes Deployment Descriptors that detail the resources allocated for services, such as VMs, Pods, Containers, and Networks. Each descriptor corresponds with specific O-Cloud capabilities and returns a unique Deployment ID, crucial for tracking and managing deployment specifics over the O2dms interface. - -# --- 5 Cloud deployment scenarios - -## 5.1 Main actors - -1. Operator -2. CSP (Cloud Service Provider) -3. Vendors -4. Third parties (e.g. service providers, verticals) - -## 5.2 Cloud service models - -Different levels of abstraction constitute the platform of the cloud architecture. These abstractions are grouped into the different service levels, depending on what resources are offered as a service for a given abstraction level. According to NIST SP 800-145 the three standard cloud service models are Platform as a Service (PaaS), Software as a Service (SaaS), and Infrastructure as a Service (IaaS). - -### 5.2.1 Infrastructure as a Service (IaaS) - -The capability provided to the Operator is to provision processing, storage, networks, and other fundamental computing resources where the Operators or Vendors are able to deploy and run arbitrary software, which can include Host OS (Operator or Vendor), virtualization platforms (Operator or Vendor) and VNFs/CNFs (Operator). Operators and Vendors do not manage or control the underlying cloud infrastructure but have control over Host OS (Operator or Vendor), virtualization platforms (Operator or Vendor) and VNFs/CNFs (Operator). - -![IaaS cloud service model diagram showing layers for VNF/CNF, Hypervisor or Container Engine, Host OS, and Hardware resources, managed by NFVO, VNFM/CNFM, and VIM. Roles include Cloud Provider, Operator, and Vendor.](d734a6ea1b381280f043fcf70391b6db_img.jpg) - -The diagram illustrates the IaaS cloud service model. At the top, four grey boxes labeled 'VNF/CNF' are shown. Below them is a layer labeled 'Hypervisor or Container Engine', followed by 'Host OS'. The base layer consists of 'Hardware resources (Compute, Storage, Network)' and 'VIM'. To the right, three management components are listed: 'NFVO' (Network Functions Virtualization Orchestrator), 'VNFM/CNFM' (VNF Manager/Cloud Function Manager), and 'VIM' (Virtualized Infrastructure Manager). At the bottom, three roles are identified: 'Cloud Provider' (blue), 'Operator' (grey), and 'Vendor' (grey). - -IaaS cloud service model diagram showing layers for VNF/CNF, Hypervisor or Container Engine, Host OS, and Hardware resources, managed by NFVO, VNFM/CNFM, and VIM. Roles include Cloud Provider, Operator, and Vendor. - -Figure 5-1 : IaaS cloud service model - -### 5.2.2 Platform as a Service (PaaS) - -The capability provided to the Operator is to deploy onto the cloud infrastructure VNFs/CNFs created using programming languages, libraries, services, and tools supported by the cloud provider. The Operator does not manage or control the underlying cloud infrastructure including network, servers, operating systems, or storage, but has control over the deployed VNFs/CNFs and possibly configuration settings for the application-hosting environment. PaaS provides this platform from the cloud, hence allowing operators to develop and run VNFs/CNFs without the overhead cost (CAPEX) of building and maintaining separate platforms. - -![PaaS cloud service model diagram showing layers for VNF/CNF, Hypervisor or Container Engine, Host OS, and Hardware resources, managed by NFVO, VNFM/CNFM, and VIM. Roles include Cloud Provider and Operator.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) - -The diagram illustrates the PaaS cloud service model. It features the same layers as the IaaS model: 'VNF/CNF' (four grey boxes), 'Hypervisor or Container Engine', 'Host OS', and 'Hardware resources (Compute, Storage, Network)'. Management components 'NFVO', 'VNFM/CNFM', and 'VIM' are shown on the right. At the bottom, two roles are identified: 'Cloud Provider' (blue) and 'Operator' (grey). The 'Vendor' role is absent in this model. - -PaaS cloud service model diagram showing layers for VNF/CNF, Hypervisor or Container Engine, Host OS, and Hardware resources, managed by NFVO, VNFM/CNFM, and VIM. Roles include Cloud Provider and Operator. - -Figure 5-2 : PaaS cloud service model - -### 5.2.3 Software as a Service (SaaS) - -SaaS as defined by NIST is the capability provided to the Cloud Consumer to use the Cloud Provider’s applications running on a cloud infrastructure. Applications are accessible through web browser or program interface. The operator does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even Applications. - -![SaaS - NIST cloud service model diagram](366a77fdefb0097b3289b4a011911390_img.jpg) - -The diagram illustrates the SaaS - NIST cloud service model. It features a stack of four layers on the left: Applications, Hypervisor or Container Engine, Host OS, and Hardware resources (Compute, Storage, Network). To the right of this stack are three management and orchestration components: NFVO, VNFM/CNFM, and VIM. Below the entire stack is a separate box labeled Cloud Provider. - -SaaS - NIST cloud service model diagram - -Figure 5-3 : SaaS cloud service model - -This service model introduces risk for the Operator, acting as the Cloud Consumer, due to shared resources, reduced control, lack of transparency for data security, secure access configuration, limited visibility to logging at lower layers, malicious insiders, regulatory drift, and lack of due diligence. It is not expected that 5G operators will deploy with the SaaS service model. - -The Cloud Provider may offer 5G private networks directly to its customers in a SaaS service model. In this service model the Cloud Provider’s customer is the Cloud Consumer, which has responsibility for securing its data and access to the applications. - -## 5.3 Cloud deployment types - -In NIST SP 800-145, cloud deployment models describe how the cloud is operated and who has access to the cloud service resources. The four deployment models are defined in NIST SP 800-145 as follows: - -### 5.3.1 Private cloud - -A private cloud gives a single Operator the exclusive access to and usage of the cloud service and related infrastructure and computational resources. It may be managed either by the Operator or by a third party Cloud Provider and may be hosted on the Operator’s premises (i.e., on-site private clouds) or outsourced to a hosting company (i.e., outsourced private clouds). The following figures present an on-site private cloud and an outsourced private cloud, respectively. - -![On-Site Private Cloud diagram](d3b5eac55166fc428a223bba5c46961b_img.jpg) - -The diagram shows an On-Site Private Cloud setup. At the top, an Operator icon is shown with an arrow pointing down into a large rounded rectangle labeled 'On-Site Private Cloud'. Inside this rectangle is a 'Private Cloud' stack with four layers: VNF/CNF (four instances), Hypervisor or Container Engine, Host OS, and Hardware resources (Compute, Storage, Network). To the right of the stack are three management and orchestration components: NFVO, VNFM/CNFM, and VIM. - -On-Site Private Cloud diagram - -Figure 5-4 : On-site private cloud - -![Diagram of Outsourced Private Cloud architecture. A Cloud Service Provider (CSP) icon is at the top, with an arrow pointing down to a 'Private Cloud' box. Inside the box, from top to bottom, are: four 'VNF/CNF' blocks, a 'Hypervisor or Container Engine' block, a 'Host OS' block, and a 'Hardware resources (Compute, Storage, Network)' block. To the right of the box are three stacked blocks: 'NFVO', 'VNFM/CNFM', and 'VIM'. An 'Operator' icon is on the far right, with an arrow pointing left towards the 'VNFM/CNFM' block. The entire setup is enclosed in a large rounded rectangle labeled 'Outsourced Private Cloud' at the top left.](552265bdbcf6d43d341fd018a9076269_img.jpg) - -Diagram of Outsourced Private Cloud architecture. A Cloud Service Provider (CSP) icon is at the top, with an arrow pointing down to a 'Private Cloud' box. Inside the box, from top to bottom, are: four 'VNF/CNF' blocks, a 'Hypervisor or Container Engine' block, a 'Host OS' block, and a 'Hardware resources (Compute, Storage, Network)' block. To the right of the box are three stacked blocks: 'NFVO', 'VNFM/CNFM', and 'VIM'. An 'Operator' icon is on the far right, with an arrow pointing left towards the 'VNFM/CNFM' block. The entire setup is enclosed in a large rounded rectangle labeled 'Outsourced Private Cloud' at the top left. - -Figure 5-5 : Outsourced private cloud - -#### **On-site private cloud** - -| Cloud type | Cloud model | Hardware | Host OS | Container Engine or Hypervisor | VNFs/CNFs | -|-----------------|-----------------|---------------|---------------|--------------------------------|-----------| -| On-site private | SaaS On-Premise | Operator | Operator | Operator | Operator | -| On-site private | IaaS | Operator, CSP | CSP, Operator | Operator, Vendors | Operator | -| On-site private | PaaS | Operator, CSP | CSP, Operator | CSP, Operator | Operator | - -#### **Outsourced private cloud** - -| Cloud type | Cloud model | Hardware | Host OS | Container Engine or Hypervisor | VNFs/CNFs | -|--------------------|-----------------|---------------|---------------|--------------------------------|-----------| -| Outsourced private | SaaS On-Premise | NA | NA | NA | NA | -| Outsourced private | IaaS | Operator, CSP | CSP, Operator | Operator, Vendors | Operator | -| Outsourced private | PaaS | Operator, CSP | CSP, Operator | CSP, Operator | Operator | - -### 5.3.2 Community Cloud - -A community cloud serves a group of Operators that have shared concerns such as mission objectives, security, privacy and compliance policy, rather than serving a single Operator (e.g., a private cloud). Similar to private clouds, a community cloud may be managed by the Operators or by a third party Cloud Provider and may be implemented on the Operator’s premise (i.e., on-site community cloud) or outsourced to a hosting company (i.e., outsourced community cloud). Figure 5-6 depicts an on-site community cloud comprised of a number of participant Operators. An Operator can access the local cloud resources, and also the resources of other Operators through the connections between the associated Operators. Figure 5-7 shows an outsourced community cloud, where the server side is outsourced to a hosting company. In this case, an outsourced community cloud builds its infrastructure off premise, and serves a set of Operators that request and consume cloud services. - -![Diagram of On-site Community Cloud architecture showing three operators (A, B, C) accessing stacked local clouds. Each local cloud contains VNF/CNFs, a Hypervisor or Container Engine, Host OS, and Hardware resources. Management layers (NFVO, VNFM/CNFM, VIM) are shown on the right side of the stack.](5a1abd59a95fa47ae192807de151e9eb_img.jpg) - -The diagram illustrates the On-site Community Cloud architecture. At the top, three operators (Operator A, Operator B, and Operator C) are shown with icons. Below them, three overlapping boxes represent 'Local Cloud (Operator C)', 'Local Cloud (Operator B)', and 'Local Cloud (Operator A)'. Each local cloud box contains a row of four 'VNF/CNF' blocks. Below these is a 'Hypervisor or Container Engine' layer, then a 'Host OS' layer, and finally 'Hardware resources (Compute, Storage, Network)' at the base. To the right of the local cloud boxes, three management components are stacked: 'NFVO' (Network Functions Virtualization Orchestrator), 'VNFM/CNFM' (VNF Manager/Cloud Function Manager), and 'VIM' (Virtualized Infrastructure Manager). Arrows point from each operator to their respective local cloud and then down through the management layers. - -Diagram of On-site Community Cloud architecture showing three operators (A, B, C) accessing stacked local clouds. Each local cloud contains VNF/CNFs, a Hypervisor or Container Engine, Host OS, and Hardware resources. Management layers (NFVO, VNFM/CNFM, VIM) are shown on the right side of the stack. - -Figure 5-6 : On-site community cloud - -![Diagram of Outsourced Community Cloud architecture showing a Cloud Provider managing a Private Cloud stack. Operators A, B, and C access the Private Cloud through the Cloud Provider. The Private Cloud stack includes VNF/CNFs, Hypervisor or Container Engine, Host OS, and Hardware resources, with management layers (NFVO, VNFM/CNFM, VIM) on the right.](58f4167687de8d7339594e5f6fbe0bc6_img.jpg) - -The diagram illustrates the Outsourced Community Cloud architecture. A 'Cloud Provider' icon is at the top, with an arrow pointing down to a 'Private Cloud' box. Inside the 'Private Cloud' box, there is a stack of layers: 'VNF/CNF' (four blocks), 'Hypervisor or Container Engine', 'Host OS', and 'Hardware resources (Compute, Storage, Network)'. To the right of the stack are 'NFVO', 'VNFM/CNFM', and 'VIM' layers. From the 'Private Cloud' box, three arrows point to 'Operator A', 'Operator B', and 'Operator C' icons on the right side. - -Diagram of Outsourced Community Cloud architecture showing a Cloud Provider managing a Private Cloud stack. Operators A, B, and C access the Private Cloud through the Cloud Provider. The Private Cloud stack includes VNF/CNFs, Hypervisor or Container Engine, Host OS, and Hardware resources, with management layers (NFVO, VNFM/CNFM, VIM) on the right. - -Figure 5-7 : Outsourced community cloud - -#### **On-site Community Cloud** - -| Cloud type | Cloud model | Hardware | Host OS | Container Engine or Hypervisor | VNFs/CNFs | -|-------------------------|-------------|----------------|-------------------------|--------------------------------|-----------| -| On-site Community Cloud | On-Premise | Operators | Operators | Operators | Operators | -| On-site Community Cloud | IaaS | CSP, Operators | CSP, Operators, Vendors | CSP, Operators, Vendors | Operators | -| On-site Community Cloud | PaaS | CSP, Operators | CSP, Operators, Vendors | CSP, Operators, Vendors | Operators | - -#### **Outsourced community cloud** - -| Cloud type | Cloud model | Hardware | Host OS | Container Engine or Hypervisor | VNFs/CNFs | -|----------------------|-------------|----------|-------------------------|--------------------------------|-----------| -| Outsourced community | On-Premise | NA | NA | NA | NA | -| Outsourced community | IaaS | CSP | CSP, Operators, Vendors | CSP, Operators, Vendors | Operators | -| Outsourced community | PaaS | CSP | CSP, Operators, Vendors | CSP, Operators, Vendors | Operators | - -### **5.3.3 Public Cloud** - -A public cloud is one in which the cloud infrastructure and computing resources are made available to the general public over a public network. A public cloud is owned by an organization providing cloud services, and serves a diverse pool of clients (e.g. Operators, Third parties service providers). - -Figure 5-8 presents a simple view of a public cloud and its actors. - -![Diagram of a Public Cloud architecture showing layers: VNF/CNF, Hypervisor or Container Engine, Host OS, and Hardware resources (Compute, Storage, Network). It also shows management layers: NFVO, VNFM/CNFM, and VIM. Actors include Cloud Provider, Third Party A, B, C, Operator A, B, and C.](e29665b8abcea967ef289c6aff07ae4c_img.jpg) - -The diagram illustrates a 'Public Cloud' environment. At the top, a 'Cloud Provider' icon is shown. Below it, a large rounded rectangle contains a stack of layers. From top to bottom, these are: four 'VNF/CNF' blocks, a 'Hypervisor or Container Engine' layer, a 'Host OS' layer, and 'Hardware resources (Compute, Storage, Network)'. To the right of this stack are three management layers: 'NFVO', 'VNFM/CNFM', and 'VIM'. On the left, three 'Third Party' icons (A, B, and C) point to the VNF/CNF blocks. On the right, three 'Operator' icons (A, B, and C) point to the NFVO, VNFM/CNFM, and VIM layers respectively. - -Diagram of a Public Cloud architecture showing layers: VNF/CNF, Hypervisor or Container Engine, Host OS, and Hardware resources (Compute, Storage, Network). It also shows management layers: NFVO, VNFM/CNFM, and VIM. Actors include Cloud Provider, Third Party A, B, C, Operator A, B, and C. - -Figure 5-8 : Public cloud - -| Cloud type | Cloud model | Hardware | Host OS | Container Engine or Hypervisor | VNFs/CNFs | -|------------|-------------|----------|---------|--------------------------------|-----------| -| Public | On-Premise | NA | NA | NA | NA | -| Public | IaaS | NA | NA | NA | Operators | -| Public | PaaS | CSP | CSP | CSP | Operators | - -### **5.3.4 Hybrid Cloud** - -A hybrid cloud is a composition of two or more clouds (on-site private, on-site community, off-site private, off-site community or public) that remain as distinct entities but are bound together by standardized or proprietary technology - -that enables data and application portability. Figure 5-9 presents a simple view of a hybrid cloud that could be built with a set of clouds in the five deployment model variants. - -The idea is to combine the benefits of multiple deployment models. The deployment in hybrid clouds could be either a combination of private, public or community clouds. One of the popular use cases of hybrid clouds is in enhancing security and privacy on the cloud without incurring the overhead costs (CAPEX) of building a private cloud. In this case, non-critical resources like test workloads can be hosted in the public cloud, while critical resources like user data and workloads are hosted internally. - -![Diagram of a hybrid cloud architecture showing five deployment model variants: On-Site Private Cloud, Outsourced Private Cloud, On-site Community Cloud, Outsourced Community Cloud, and Public Cloud. Each variant shows a stack of layers: VNF/CNF, Hypervisor or Container Engine, Host OS, and Hardware resources (Compute, Storage, Network). Management layers include NFVO, VNFMAN/CNFM, and VIM. Operators and third parties are shown interacting with these clouds.](eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg) - -The diagram illustrates a hybrid cloud architecture composed of five deployment model variants, each represented by a rounded rectangle containing a layered stack of components: - -- On-Site Private Cloud:** Managed by an **Operator**. The stack includes **VNF/CNF** (4 instances), **NFVO**, **VNFMAN/CNFM**, **Host OS**, and **Hardware resources (Compute, Storage, Network)**. -- Outsourced Private Cloud:** Managed by a **Cloud Provider**. The stack is identical to the On-Site Private Cloud. An **Operator** is shown interacting with the **VNFMAN/CNFM** layer. -- On-site Community Cloud:** Managed by **Operator A**, **Operator B**, and **Operator C**. It features nested boxes for **Local Cloud (Operator C)**, **Local Cloud (Operator B)**, and **Local Cloud (Operator A)**, each with its own **VNF/CNF** instances. Below these are the shared **Hypervisor or Container Engine**, **Host OS**, and **Hardware resources**. Management layers **NFVO**, **VNFMAN/CNFM**, and **VIM** are also present. -- Outsourced Community Cloud:** Managed by a **Cloud Provider**. The stack is identical to the On-Site Private Cloud. **Operator A**, **Operator B**, and **Operator C** are shown interacting with the **VNFMAN/CNFM** layer. -- Public Cloud:** Managed by a **Cloud Provider**. The stack is identical to the On-Site Private Cloud. **Third Party A**, **Third Party B**, and **Third Party C** are shown interacting with the **VNF/CNF** layer, while **Operator A**, **Operator B**, and **Operator C** interact with the **VNFMAN/CNFM** layer. - -Lines connect the **Operator** in the On-Site Private Cloud to the **Cloud Provider** in the Public Cloud, and to the **Cloud Provider** in the Outsourced Community Cloud. Additionally, lines connect the **Cloud Provider** in the Public Cloud to the **Cloud Provider** in the Outsourced Private Cloud, and to the **Cloud Provider** in the Outsourced Community Cloud. - -Diagram of a hybrid cloud architecture showing five deployment model variants: On-Site Private Cloud, Outsourced Private Cloud, On-site Community Cloud, Outsourced Community Cloud, and Public Cloud. Each variant shows a stack of layers: VNF/CNF, Hypervisor or Container Engine, Host OS, and Hardware resources (Compute, Storage, Network). Management layers include NFVO, VNFMAN/CNFM, and VIM. Operators and third parties are shown interacting with these clouds. - -Figure 5-9 : Hybrid cloud - -1 - -# 2 5.4 High-Level risk assessment - -3 The following table illustrates the high-level security risk assessment of the cloud deployment models (Private, Community, Public and Hybrid). Colors red, yellow, and green - 4 are used on the security risk assessment to indicate high, medium, and low levels of risk. The Cloud Consumer (operator) is accountable for the security posture of the - 5 deployment for all cloud deployment models [i.44]. - -| Risks | Private Cloud | Community Cloud | Public Cloud | Hybrid Cloud | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Regulatory Compliance: Risk of non-compliance with regulations on data ownership, geographic location and privacy. Regulatory drift.

Data security and regulatory risk can be associated with loss, leakage, or unavailability of data. This can cause business interruption, loss of revenue, loss of reputation, or regulatory incompliance (e.g. GDPR, HIPAA).

The Cloud Consumer | Low Risk: Similar to traditional computing, as operators have better control and understanding on how various government rules, laws, and regulations apply to them. The Cloud Consumer (operator) has control of data and regulatory compliance. | Moderate Risk: Cloud Consumer (operator) has better control and understanding on how various government rules, laws, and regulations apply to them. Data leakage or data access risks due to multitenancy/shared infrastructure between different operators. | High Risk: Lack of flexibility over data protections mechanisms, such as encryption and implementation of specific controls by data type. Different operators or service providers might have different encryption and control requirements, and a public cloud provider may not be able to customize their infrastructure or provide customers the control over encryption keys.

In some situations, it may be determined that a Cloud Service Provider's cybersecurity tools, processes and methods are insufficient for protecting highly sensitive data. The Cloud Consumer (operator) is responsible for the security configuration of CSP provided applications, tools and services. | Moderate Risk: Cloud Consumer (operator) has better control and understanding on how various government rules, laws, and regulations apply to them.

Administrators have more control and flexibility when implementing security. The Cloud Consumer can architect the Hybrid Cloud deployment to ensure regulatory compliance of most sensitive data, while less sensitive data is accessed, stored, and | - -| | | | | | -|-----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -|

(operator) is accountable for data, regulatory compliance, and configuration of security controls.

| | |

The Cloud Consumer (operator) must practice due diligence to assess the regulatory compliance of the Cloud Service Provider's environment.

|

processed in the Public Cloud.

The Cloud Consumer (operator) must practice due diligence to assess the regulatory compliance of the Cloud Service Provider's environment.

| -|

Multi-Tenancy: Risk due to Multi-Tenancy with shared resources. Risks include data leakage, VM Escape, Host Escape, and Hyperjacking.

|

Low Risk: Private Networks avoid shared resources.

|

High Risk: Data leakage or access risks due to multitenancy/shared resources for multiple Cloud Consumers (operators) that may be competitors. Cloud Consumer (operator) must ensure security configurations to protect access to network functions, confidentiality and integrity of data in motion, and confidentiality, integrity, and access controls for data at rest.

|

High Risk: Data leakage or access risks due to multitenancy/shared resources. Cloud Consumer (operator) must ensure security configurations to protect access to network functions, confidentiality and integrity of data in motion, and confidentiality, integrity, and access controls for data at rest.

|

High Risk: Data leakage or access risks due to multitenancy/shared infrastructure. Cloud Consumer (operator) must ensure security configurations to protect access to network functions, confidentiality and integrity of data in motion, and confidentiality, integrity, and access controls for data at rest.

| - -| | | | | | -|---------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -|

Third-Party Administration: Operational risk can be associated with O-RAN network services, lack of control, visibility, etc.

|

Low Risk: With private cloud, the operator gains full control and visibility over its cybersecurity posture and can customize it to fit its specific needs.

Operator has complete visibility, monitoring and control, analyze logs, alerts and other data down to the packet level.

|

Moderate Risk: Security administrators may deal with differing methods and tools to monitor and act on threats depending on where vulnerable resources reside.

Lack of customized security and service level for different O-RAN network services, which might require the operator to choose a proximate acceptable security and service level, including those related to availability and disaster recovery.

|

High Risk: Lack of customized security and service level for different O-RAN network services, which might require the operator to choose a compensating security control and security baseline.

The underlying infrastructure is not managed by the operator, security information may be not accessible.

Reduced control on critical network services can impact availability and disaster recovery. Disaster Recovery with a second CSP, which may not have the same security posture due to use of different security tools and configurations.

|

High Risk: Varying security tools and configurations may not prevent a consistent security baseline across the Hybrid Cloud deployment. The Cloud Consumer may have reduced visibility with the CSP controlled part of the service.

Disaster Recovery should be provided with a second CSP, which may not have the same security posture due to use of different security tools and configurations.

Security roles and responsibilities must be clearly defined and assigned to the Cloud Consumer (operator) and Cloud Service Provider (CSP). The Cloud Consumer (operator) must

| -|---------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| - -| | | | | | -|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | practice due diligence to ensure a consistent security posture across the Hybrid Cloud deployment. | -|

Technology Evolution:
Technology risk can be associated with constantly evolving technologies and lack of standardization in how they integrate or interoperate. Technology risks could lead to costly rearchitecture efforts for adoption or integration with new technology.

|

High Risk: A constantly evolving technology landscape that might require the operator to upgrade or rearchitect its computing resources and retrain its technology support staff.

A potential for human error due to the number of configurable points and frequency of deployments.

Lack of qualified talent.

|

Moderate Risk: Operators share a common set of security tools, for which each is responsible for properly configuring the security of its tenancy.

Operators can share cloud complexity to manage constantly evolving technology landscape that might require operators to upgrade or rearchitect its computing resources and retrain its technology support staff.

|

Low Risk: Larger CSPs often invest heavily in top-end cybersecurity tools, as well as staff who are highly knowledgeable in their field. This makes offloading cybersecurity tools and tasks from in-house to a third party highly appealing.

Operators can transfer cloud complexity to the CSP, which already has the necessary cloud expertise, infrastructure and systems. For example, faster time-to-market and improved operations efficiency are achieved by taking advantage of CSP-trained talent and their existing CI/CD DevOps, automation, orchestration and analytics capabilities. Operators can then focus on service differentiation, not the underlying cloud platforms.

|

Moderate Risk: Hybrid Cloud deployments provide flexible management of legacy and proprietary applications while enabling use of technologies associated with cloud-based services and applications.

A potential for human error due to the number of configurable points and frequency of deployments. The operator is responsible for properly configuring the security across the Hybrid Cloud. The Cloud Consumer (operator) must

| - -| | | | | | -|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | practice due diligence to ensure a consistent security posture across the Hybrid Cloud deployment. | -| Financial costs & operation |

High Risk: Operating private clouds is often a more expensive endeavor than public cloud options. Businesses pay a premium for granular cloud control and visibility.

Designing and maintaining cybersecurity tools inside private clouds dramatically increase management responsibilities.

Lack of Operator-trained administrators.

|

Moderate Risk: Designing and maintaining cybersecurity tools inside community clouds increase management responsibilities.

Lack of Operator-trained administrators.

Operators can share financial cost and the operation of community cloud.

|

Low Risk: Operating public clouds is often a less expensive endeavor than private and community cloud options.

Operators can transfer cloud operation to the CSP, which already has the necessary cloud expertise, infrastructure, and systems.

|

Moderate Risk: Designing and maintaining cybersecurity tools inside hybrid clouds increase management responsibilities.

Operators can transfer part of the cloud operation to the CSP, which already has the necessary cloud expertise, infrastructure, and systems.

| - -1 -2 -3 - -Risk levels: High, Moderate, Low - -**Table 5-1 : High level security risk assessment of cloud deployment models** - -# 6 Roles and responsibilities - -The list of users likely to interact with the O-CLOUD as well as their roles are presented in the table below. The last column distinguishes between stakeholders acting: - -- Under the direct responsibility of an operator or -- Under the responsibility of a third party (e.g. equipment supplier) acting through a contract with the operator. - -The table shows many roles in which the operator and cloud service provider are both stakeholders. This highlights the need to have: - -- Clearly defined and agreed upon roles and responsibilities in the cloud service agreement. -- Separation of Duties enforced by the cloud service provider to limit insider threats. -- Principles of least privilege access control configured and enforced by the operator. - -| Roles | Responsibilities | Stakeholders | -|----------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------| -| O-Cloud Planner | Operator planning O-Cloud instance. | Operator, CSP | -| O-Cloud Installation Manager | Operator designing each O-Cloud instance.

Cloud Installation Manager issues a “service request” to the SMO to update its Inventory, i.e., indicate that a new O-Cloud is to be inventoried. The Cloud Installation Project Manager also registers to the SMO the basic software for the O-Cloud. | Operator, CSP | -| Network Function Install Manager | Operator designing each Network Function instance. | Operator, Vendor | -| O-Cloud Installer | Operator installing O-Cloud Node. He notifies SMO of the new O-Cloud Build

NOTE: Cloud Installer must provide SMO with information to connect with the new O-Cloud Build, including the target O-Cloud Node in the O-Cloud and identity of the basic software for O-Cloud to be loaded on the O-Cloud | Operator, CSP | -| O-Cloud Maintainer | Operator that operates and manages O-Cloud Nodes | Operator | -| Security administrator | They manage component security configuration: configuration of access rights, password and cryptographic key storage system, IPSec parameters, configuring remote access systems, etc.

They hold the root password and the secret encryption root key. | Operator | -| System administrator | They manage “system” components (e.g. back-up, update, configuring system logs, etc.). | Operator | -| O-RAN NF Administrator | They can manage and configure one or more VNFs/CNFs (e.g. Near RT RIC, O-CU, O-DU). They can perform the daily operational tasks (notably provisioning) of NFs. | Operator | -| IMS Administrator | They manage IMS activities. They can perform the daily operational tasks and configure the IMS. They control functions providing access to the IMS. They are responsible for VNFs/CNFs hardware configuration. | Operator, CSP | - -| | | | -|------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| -| DMS Administrator | They manage DMS activities. They can perform the daily operational tasks (notably provisioning) and configure the DMS. They control functions providing access to DMS. | Operator CSP | -| Virtualization layer administrator (Hypervisor/Container Engine) | They manage the virtualization/containerization layer (Hypervisor/Container Engine). They can perform the daily operational tasks (notably provisioning) and configuration of the virtualization layer. They control functions providing access to this layer. | Operator, CSP | -| Compute nodes administrator (physical servers) | They manage compute nodes (physical servers) They can access the node's graphic console, start, stop, restart the node. They can activate/deactivate the node network interfaces and check its status. They manage local storage in compute nodes. | Operator, CSP | -| Storage administrator | They manage shared storage (e.g. images repository) | Operator, CSP | -| Maintainer (equipment supplier or third party) | They can remotely (e.g. via VPN) or locally access equipment to update, configure, remove or add network applications. They have access to compute node configuration interfaces to update firmware and configure BIOS, CPU, MMU, etc.

The maintainer works on the O-Cloud platform under the control of the operator who (e.g. via IAM: Identity Access Management) creates specific accounts for a limited period. | Vendor, Third Party | -| Internal validation laboratory | They are responsible for vulnerability scanning, testing, qualifications, security/compliance of network applications before their deployment. | Operator, Vendor, CSP | -| Security Incident Response Team | Setup a vulnerability management process of monitoring, identifying, evaluating, treating, and reporting on security vulnerabilities and incidents.

Maintenance of the O-Cloud components that includes monitoring for use of open source software with known vulnerabilities and patching for vulnerabilities.

Provide a process for users, including security researchers, to submit bug reports (e.g., using an issue tracker or a mailing list). | Operator, Vendor, CSP | - -1 - -Table 6-1 : List of Users - -2 - -# 7 Security Problem Definition - -3 - -Before analyzing the way to protect the O-Cloud, it is important to identify the threats affecting the different O-Cloud components and data. - -4 - -5 - -For this identification of threats, it is essential first to know the critical assets, consisting of anything that has value for within O-Cloud and needs to be protected, and secondly to identify the threat agents, the entities that can adversely act on the asset. - -6 - -7 - -8 - -## 7.1 Assets - -9 - -1 The assets listed below are associated with O-Cloud. They are described in Clause 6.3 of the O-RAN Security Threat -2 Modeling and Risk Assessment [i.50]: - -- 3 • ASSET-D-12: O-Cloud Inventory information of hardware resources and software resources -- 4 • ASSET-D-13: Functional telemetry: deployment, infrastructure -- 5 • ASSET-D-14: O-Cloud Provisioning information, O-Cloud software management information, List of -- 6 authorized VNF/CNF, VNF/CNF description files -- 7 • ASSET-D-15: O-RAN Cloudified Network Function Software Image and metadata, secrets, configuration files -- 8 • ASSET-D-16 & ASSET-D-17: Private keys, certificates support for authentication, encryption, signing (e.g. -- 9 for TLS and similar protocols, image signing) -- 10 • ASSET-D-18: Software components at runtime and their associated data, data of VNF/CNF hosted in the -- 11 shared storage system, RAM and the disk in the compute node -- 12 • ASSET-D-20: Credentials (Administrators): account information and passwords -- 13 • ASSET-D-29: Security event log files generated by O-Cloud components -- 14 • ASSET-D-31: Security telemetry from the NFV system for detecting threats and anomalies -- 15 • ASSET-D-32: Cryptographic keys used during secure boot, for encryption/decryption, etc. -- 16 • ASSET-D-33: Data in transit AALI-C-Mgmt interface -- 17 • ASSET-D-34: Data in transit AALI-C-App & AALI-P interfaces -- 18 • ASSET-D-35: Data in transit vendor specific interface -- 19 • ASSET-D-36: AAL profiles. It specifies one or more Accelerated Functions that an accelerator processes on -- 20 behalf of an AAL Application within an O-RAN Network Function in an O-Cloud [i.52]. -- 21 • ASSET-D-37: AAL-LPU. It is a logical representation of resources within an instance of a HW Accelerator -- 22 [i.52]. -- 23 • ASSET-D-38: Stored AAL data (e.g., logs, configuration data) -- 24 • ASSET-C-08: O-Cloud software including the OS kernel and the virtualisation layer. -- 25 • ASSET-C-23: O2, including protocol stack -- 26 • ASSET-C-29: AAL Implementation. It is a realization of an AAL including but not limited to the software -- 27 libraries and drivers [i.52]. -- 28 • ASSET-C-30: The hardware accelerator device firmware and hardware. - -29 -30 The figure below presents a cartography of the assets within the O-Cloud architecture: - -![Figure 7-1: Cartography of O-Cloud assets diagram showing layers from Images repository to Hardware resources, with various assets labeled ASSET-D-12 through ASSET-D-38.](145d00f59802048185303f15937ea65c_img.jpg) - -The diagram illustrates the O-Cloud architecture and associated assets. At the top, an **Images repository** is connected to the **SMO** (Service Management and Orchestration) via **ASSET-D-15**: O-RAN Cloudified Network Function Software Image and metadata, secrets, configuration files. The **SMO** contains **Non RT RIC/rApps**, **NFO**, and **FOCOM**. Assets associated with the SMO include: **ASSET-D-31**: Security telemetry from the NFV system for detecting threats and anomalies; **ASSET-D-12**: O-Cloud inventory information of hardware resources and software resources; **ASSET-D-13**: Functional telemetry: deployment, infrastructure; and **ASSET-D-14**: O-Cloud Provisioning information, O-Cloud software management information, List of authorized VNF/CNF, VNF/CNF description files. The SMO connects to the **O-Cloud** via interfaces **O1**, **A1**, **O2dms**, and **O2ims**. The **O-Cloud** contains **VNF/CNF** (O-DU, O-CU), **Near RT RIC/xApps**, **DMS**, and **IMS**. Assets for the O-Cloud include: **ASSET-D-16 & ASSET-D-17**: Private keys, certificates support for authentication, encryption, signing (e.g. for TLS and similar protocols, image signing); **ASSET-D-20**: Credentials (Administrators): account information and passwords; **ASSET-D-29**: Security event log files generated by O-Cloud components; and **ASSET-D-32**: Other crypto keys for secure boot, ... Below the VNF/CNF and Near RT RIC/xApps is the **O-Cloud API**. The next layer is the **Virtualization Layer (VL)**, which includes **Containers**, **VMs**, **Container Engine**, **Hypervisor (Type II)**, **Guest OS**, and **Hypervisor (Type I)**. **ASSET-D-18**: Software components at runtime and their associated data, data of VNF/CNF hosted in the shared storage system, RAM and the disk in the compute node is associated with this layer. The bottom layer consists of **Hardware resources (Compute, Storage, Network, Hardware Accelerator manager)**. Assets related to data in transit and stored data include: **ASSET-D-33**: Data in transit AALI-C-Mgmt interface; **ASSET-D-34**: Data in transit AALI-C-App & AALI-P interfaces; **ASSET-D-35**: Data in transit vendor specific interface; **ASSET-D-36**: AAL profiles; **ASSET-D-37**: AAL-LPU; and **ASSET-D-38**: Stored AAL data (e.g., logs, configuration data). - -Figure 7-1: Cartography of O-Cloud assets diagram showing layers from Images repository to Hardware resources, with various assets labeled ASSET-D-12 through ASSET-D-38. - -Figure 7-1 : Cartography of O-Cloud assets - -## 7.2 Threats - -The complexity and the extension of attack surface of a virtualized environment increase the difficulty to list, in an exhaustive manner, the security threats to which the O-Cloud assets are exposed. For this activity of threat analysis, some reports have been used to help the identification of a large number of these threats: - -- CISA/NSA - Kubernetes Hardening Guidance [i.3] -- MITRE ATT&CK containers matrix [i.4] -- ENISA Threat Landscape for 5G Networks: Threat assessment for the fifth generation of mobile telecommunications networks (5G) [i.5] -- ETSI Secure End-to-End VNF and NS management specification Secure End-to-End VNF and NS management specification [i.6] - -The following table is the template used to present the threat characteristics: - -| | | -|------------------------------|---------------------------------------------------------------------------------------------------------------| -| Threat ID | Unique identification per Threat (e.g. T-XX-01) | -| Threat title | Title of the threat | -| Threat description | Description of the Threat | -| Threat type | Spoofing
Tampering
Repudiation
Information disclosure
Denial of Service
Elevation of Privilege | -| Vulnerabilities | What vulnerabilities can the threat exploits? | -| Impact type | Authenticity
Integrity
Non-repudiability
Confidentiality
Availability
Authorization | -| Threatened Assets | Impacted Asset(s) (Data & Component) | -| Affected Services | What services (from clause 4.3) could be affected by this Threat | -| Potential mitigations | Mitigation measures to address the threat | - -### 7.2.1 Threat and impact types - -For identifying threats, we are using STRIDE: - -1. S - Spoofing identity. An application or program can masquerade as another to gain advantages not typically allowed for that program. - -2. T - Tampering with data. This involves the malicious modification of data, including making unauthorized changes to a database and alteration of data as it flows between computers. -3. R - Repudiation. A user or program refuses the authenticity of a good or reasonable command or action. -4. I - Information disclosure. This involves the exposure of information to individuals with unauthorized access to it. For example, users gain the ability to read a file that they normally would not have been granted access to, or an intruder can read data in transit between computers. -5. D - Denial of service. These attacks deny service to valid users, such as making a website unavailable or unusable by flooding it with illegitimate requests to keep legitimate users without access. -6. E - Elevation of privileges. An unauthorized user gains privileged rights to access previously no granted to compromise or destroy the system, such as a change in membership. - -| Threat types | Impact types | -|------------------------|-------------------| -| Spoofing | Authenticity | -| Tampering | Integrity | -| Repudiation | Non-repudiability | -| Information disclosure | Confidentiality | -| Denial of Service | Availability | -| Elevation of Privilege | Authorization | - -### 7.2.2 Attack surface - -An attack surface of a system refers to the set of various entry points that can be exploited. The various components that compose the attack surface of the O-Cloud are depicted in the following figure. They are as follows: - -- 1) VNFs/CNFs: O-DU, O-CU, O-RU, Near RT-RIC/xApps -- 2) Images repository with its interface to O-Cloud -- 3) Virtualization layer: Hypervisor and/or Container Engine, Host OS -- 4) Hardware resources including compute, storage, network, and hardware accelerator manager -- 5) O-Cloud API -- 6) O2dms and O2ims interfaces -- 7) NFO and Federated O-Cloud O&M (FOCOM) within the SMO -- 8) AAL - -The attack vectors for exploiting vulnerabilities of these components are discussed in detail in the threat events clauses. - -![Diagram of O-RAN architecture showing attack vectors. The diagram includes SMO (Non RT RIC/rApps, NFO, FOCOM), O-Cloud (VNF/CNF: O-DU, O-CU, Near RT RIC/xApps, AAL), Virtualization Layer (VL) with Containers, VMs, Hypervisors, Guest OS, and Host OS, and Hardware resources. Red circles 1-8 indicate attack vectors: 1. Near RT RIC/xApps, 2. Images repository, 3. Virtualization Layer, 4. Hardware resources, 5. O-Cloud API, 6. O2ims interface, 7. NFO, 8. AAL.](e151d3468319b81f042ca232c4d82e4b_img.jpg) - -Diagram of O-RAN architecture showing attack vectors. The diagram includes SMO (Non RT RIC/rApps, NFO, FOCOM), O-Cloud (VNF/CNF: O-DU, O-CU, Near RT RIC/xApps, AAL), Virtualization Layer (VL) with Containers, VMs, Hypervisors, Guest OS, and Host OS, and Hardware resources. Red circles 1-8 indicate attack vectors: 1. Near RT RIC/xApps, 2. Images repository, 3. Virtualization Layer, 4. Hardware resources, 5. O-Cloud API, 6. O2ims interface, 7. NFO, 8. AAL. - -Figure 7-2 : Attack vectors - -### 7.2.3 Vulnerabilities - -The following figure highlights the main vulnerabilities that may emerge within the attack vectors (see Figure 7-2). - -![Diagram of vulnerabilities within O-Cloud. It shows VMs/Containers running Near RT RIC, O-CU, and O-DU on top of a Hypervisor or Container Engine, which runs on the Host OS. Vulnerabilities are indicated by arrows pointing to various components: Misconfiguration or Insecure VM/Container configurations, Insecure networking, Shared tenancy vulnerabilities, Lack of strong VM/Container isolation, Hypervisor/Container Engine misconfiguration, Secret exposure, Host misconfiguration, Images repository (Compromised VM/Container images at rest or in transit, Insecure data storage, Lack authentication), and Vulnerable code exploits, Design weakness, Lack of authentication, Lack of integrity verification during boot or runtime, Insecure data storage.](107da2e3495b2f24352c9e3b26ec4841_img.jpg) - -Diagram of vulnerabilities within O-Cloud. It shows VMs/Containers running Near RT RIC, O-CU, and O-DU on top of a Hypervisor or Container Engine, which runs on the Host OS. Vulnerabilities are indicated by arrows pointing to various components: Misconfiguration or Insecure VM/Container configurations, Insecure networking, Shared tenancy vulnerabilities, Lack of strong VM/Container isolation, Hypervisor/Container Engine misconfiguration, Secret exposure, Host misconfiguration, Images repository (Compromised VM/Container images at rest or in transit, Insecure data storage, Lack authentication), and Vulnerable code exploits, Design weakness, Lack of authentication, Lack of integrity verification during boot or runtime, Insecure data storage. - -Figure 7-3 : Vulnerabilities within O-Cloud - -### 7.2.4 Threat events - -The following threats to O-Cloud have been identified and are analyzed in this Clause. Other threats within the attack vectors ④, ⑥, ⑦ ⑧ will be added in future versions of the report. - -| Threat | Threat Title | -|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------| -| Generic Threats | | -| T-GEN-01 | Software flaw attack | -| T-GEN-02 | Malicious access to exposed services using valid accounts | -| T-GEN-03 | Untrusted binding between the different O-Cloud layers | -| T-GEN-04 | Lack of Authentication & Authorization in interfaces between O-Cloud components | -| T-GEN-05 | Unsecured credentials and keys | -| T-GEN-06 | Sensitive application data cache exploitation | -| Threats concerning VMs/Containers | | -| T-VM-C-01 | Abuse of a privileged VM/Container | -| T-VM-C-02 | VM/Container escape attack | -| T-VM-C-03 | VM/Container data theft | -| T-VM-C-04 | VM/Container migration attacks | -| T-VM-C-05 | Changing virtualization resource without authorization | -| T-VM-C-06 | Failed or incomplete VNF/CNF termination or releasing of resources | -| Threats concerning VM/Container images | | -| T-IMG-01 | VM/Container images tampering | -| T-IMG-02 | Insecure channels with images repository | -| T-IMG-03 | Secrets disclosure in VM/Container images | -| T-IMG-04 | Build image on VL | -| Threats concerning the virtualization layer (Host OS-Hypervisor/Container engine) | | -| T-VL-01 | VM/Container hyperjacking attack | -| T-VL-02 | Boot tampering | -| T-VL-03 | Attack internal network services | -| Threats concerning O-Cloud interfaces | | -| T-O2-01 | MitM attacks on O2 interface between O-Cloud and SMO | -| T-OCAPI-01 | MitM attacks on O-Cloud interface between VNFs/CNFs and the virtualization layer | -| Threats concerning hardware resources | | -| T-HW-01 | Cross VM/Container side channel attacks | - -| | | -|----------------------------------------------------------------|---------------------------------------------------------------------------------| -| T-HW-02 | MitM attacks on the interface between virtualization layer and hardware | -| Threats concerning O-Cloud management (SMO, NFO, FOCOM) | | -| T-ADMIN-01 | Denial of service against NFO/FOCOM | -| T-ADMIN-02 | Abuse an O-Cloud administration service | -| Threats concerning Acceleration Abstraction Layer (AAL) | | -| T-AAL-01 | Attacker exploits insecure API to gain access to hardware accelerator resources | -| T-AAL-02 | Internal Overload DoS attack targeting AAL services | -| T-AAL-03 | Fail to clear resources | -| T-AAL-04 | HAM compromise | -| T-AAL-05 | Malicious memory accesses | -| T-AAL-06 | Firmware attacks | -| Threats concerning O-Cloud instance ID | | -| T-O-CLOUD-ID-01 | ID reuse in O-Cloud's object lifecycle | -| T-O-CLOUD-ID-02 | Node redundancy in O-Cloud deployments | -| T-O-CLOUD-ID-03 | O-Cloud ID mismanagement | -| Threats concerning time synchronization | | -| T-TS-01 | Time synchronization disruption in O-Cloud | - -#### 7.2.4.1 Generic Threats - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-GEN-01 | -| Threat title | Software flaw attack | -| Threat description |

Code of host OS, Hypervisor/Container Engine and VNF/CNF can include flaws that an attacker can exploit if they are present.

O-RAN software components rely on opensource software, opensource libraries, 3rd party components. Vulnerability in any of these software components likely to allow attacker to exploit O-CLOUD environment. This could lead attacker to carry out to malicious activities, such as:

  • • Compromise of the underlying VM/Container
  • • Exploit host access via Escape to Host
  • • Take advantage of weak identity and access management policies to attempt to elevate privileges
  • • Execute adversary-controlled code
  • • Enable an adversary to move from a virtualized environment, such as within a virtual machine or container, onto the underlying host
| - -| | | -|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat type | Spoofing, Tampering, Information disclosure, Elevation of Privilege | -| Vulnerabilities | Vulnerable code exploits, Design Weakness | -| Impact type | Authenticity, Integrity, Confidentiality, Authorization | -| Threatened Assets | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | -| Affected Services | All services | -| Potential mitigations | REC-IMGP Image protection
REC-VHPM Vulnerability Handling and Patch Management
REC-SDLC Secure Development Lifecycle
REC-LOG Logging, Monitoring and Alerting
REC-ISO Strong Isolation
REC-AUD Security Audit | - -| | | -|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-GEN-02 | -| Threat title | Malicious access to exposed services using valid accounts | -| Threat description |

Access to valid accounts to use the O-Cloud services is often a requirement, which could be obtained through credential pharming or by obtaining the credentials from users after compromising the network.

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining initial access, persistence, privilege escalation, or defense evasion. Compromised credentials may be used to bypass access controls placed on various resources on O-Cloud.

Compromised credentials may also grant an adversary increased privilege to specific O-Cloud services or access to restricted areas of the O-Cloud network.

Access may be also gained through an exposed service that doesn't require authentication. In containerized environments, this may include an exposed Docker API, Kubernetes API server, kubelet, or web application such as the Kubernetes dashboard.

| -| Threat type | Spoofing, Tampering, Information disclosure, Elevation of Privilege | -| Vulnerabilities | Lack of authentication | -| Impact type | Authenticity, Integrity, Confidentiality, Authorization | -| Threatened Assets | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | -| Affected Services | All services | -| Potential mitigations | REC-IAM Identity, Authentication, and Access Management
REC-CM Certificate management
REC-LOG Logging, Monitoring and Alerting
REC-NS Network Segmentation & Filter Network Traffic
REC-AUD Security Audit | - -| | | -|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-GEN-03 | -| Threat title | Untrusted binding between the different O-Cloud layers | -| Threat description |

One major challenge in virtualized architectures and especially in O-Cloud is to prove that a particular VM/Container runs on top of a specific Hypervisor/Container Engine. More specifically, it is necessary to assure that a trusted VM/Container is executed on a particular trusted Hypervisor/Container Engine, whereas the Hypervisor/Container Engine's trust state relies on an attestation that considers the entire corresponding hard and software stack. More precisely, this includes all hardware chips, firmware, OS and Hypervisor/Container Engine components that are relevant for the Hypervisor/Container Engine's trust state determination.

If it is not possible to establish a correlation between VM/Container and Hypervisor/Container Engine, an attacker is able to make use of a trusted VM/Container that runs on top of an untrusted Hypervisor/Container Engine and it would be impossible to detect any interference made by the malicious Hypervisor/Container Engine, e.g. intercepting communication, replacing strong or using weak cryptographic keys, etc. Similarly, trustworthiness in the service-layer might only be established if there is a mechanism to determine that only trusted VNFs/CNFs, w.r.t trusted VM/Container's, are running on specific trusted Hypervisors/Container Engines that are part of the service-provisioning-chain.

| -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Lack of integrity verification during boot or runtime | -| Impact type | Integrity, Confidentiality | -| Threatened Assets | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | -| Affected Services | All services | -| Potential mitigations | REC-IMGP Image protection
REC-LOG Logging, Monitoring and Alerting
REC-RA Remote Attestation
REC-SB Secure Boot
REC-SNFLC Security VNF/CNF lifecycle | - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-GEN-04 | -| Threat title | Lack of Authentication & Authorization in interfaces between O-Cloud components | -| Threat description |

O-Cloud deploys CNF applications as containers in a cluster of physical nodes which may be spanned across geographical locations. Owing to the Service Based Architecture of CNFs, this introduces several service endpoints communicating across each other over the network (container to container, container to cloud infrastructure component) and it is difficult to distinguish between a service terminating an external interface and a service exposing only an internal interface.

Multi-tenant deployments and deployments in public cloud also require the CNF applications to run alongside unknown entities. In such deployment scenarios, CNF service endpoints with no authentication/weak authentication expose risk of attack that can impact the availability of service and the CNF.

Lack of proper authentication in interfaces exposed by CNF services, introduces threats of lateral movement where a compromised container/rogue container:

| - -| | | -|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |
  • • Can compromise the availability of internal service by bringing down the internal service and perform lateral movement of attack by exploiting the availability of other such services
  • • Can compromise the confidentiality of the internal service by extracting critical application data
| -| Threat type | Information disclosure, Denial of Service | -| Vulnerabilities | Lack of authentication, Insecure interfaces | -| Impact type | Availability, Confidentiality | -| Threatened Assets | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | -| Affected Services | All services | -| Potential mitigations | REC-IAM Identity, Authentication, and Access Management
REC-CM Certificate management | - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-GEN-05 | -| Threat title | Unsecured credentials and keys | -| Threat description |

Adversaries may search compromised O-RAN NFs, VL, orchestration layer or hardware to find and obtain insecurely stored credentials. These credentials can be stored and/or misplaced in many locations on the O-cloud platform, including plaintext files (e.g. Bash History), operating system or application-specific repositories (e.g. Credentials in Registry), or other specialized files/artifacts (e.g. Private Keys) [i.4].

Bash History1: Adversaries may search the bash command history on compromised systems for insecurely stored credentials.

Credentials in registry2: Adversaries may search the Registry on compromised systems for insecurely stored credentials.

Private Keys3: Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials. Private cryptographic keys and certificates are used for authentication, encryption/decryption, and digital signatures; Common key and certificate file extensions include: .key, .pgp, .gpg, .ppk, .p12, .pem, .pfx, .cer, .p7b, .asc.

Adversary tools have been discovered that search compromised systems for file extensions relating to cryptographic keys and certificates.

| -| Threat type | Tampering, Information disclosure, and Elevation of privilege | -| Vulnerabilities | Lack of authentication, secret exposure (insufficient safeguarding of credentials) | -| Impact type | Integrity, Confidentiality, Authorization | -| Threatened Assets | Private keys and credentials | -| Affected Services | All services | - -1 - -2 - -3 - -| | | -|------------------------------|-----------------------------------------------------------------------------------------------| -| Potential mitigations | REC-SS Secure Storage
REC-PHY Physical Security Protection
REC-SDD Secure data deletion | -|------------------------------|-----------------------------------------------------------------------------------------------| - -| | | -|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-GEN-06 | -| Threat title | Sensitive application data cache exploitation | -| Threat description |

Most of the applications use data that is sensitive in nature which needs to be secured. And it is common for these applications to cache such sensitive data, after retrieving the data from a secure storage. This caching occurs in various forms: within application memory, in persistent file systems, or in ephemeral file systems (For example, non-persistent container file system).

For a VNF, the application can cache the sensitive data in its memory which is non-persistent (erased when the application ceases to exist) or in the persistent virtual machine file system.

For a CNF, the application can store the sensitive data in its memory which is non-persistent (erased when the application/microservice ceases to exist) or in the non-persistent container file system, or in the persistent host file system, provided the application has the necessary privileges to access host file system.

The storage of sensitive data (For example, certificates and private keys or session keys) in the application cache is used to improve performance of the applications and keeping the sensitive information readily available to the applications for faster initialization, re-initialization or recovery.

An example of faster recovery/re-initialization is a scenario where a TLS client establishes a TLS session with a server and stores the client certificate and corresponding private key in the application cache. If the TLS session is terminated unexpectedly (For example, due to network error conditions), the TLS client uses the cached client certificates and private key for recovering / re-establishing the TLS session, instead of retrieving the information from a more secure, but slower, storage solution.

While leveraging application cache is indispensable for significant performance gains, it also presents a notable security risk [i.59][i.60]. The sensitive data stored in application cache would be a primary target from attackers/threat actors [i.61], who can exploit this information to penetrate deeper into O-RAN network functions.

To counter this threat, a “Defense in depth” approach is essential. This approach encompasses multiple security layers designed to mitigate risks associated with application caches, focusing on strong encryption, strict access management and anomaly detection to protect sensitive data effectively.

| -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Secret exposure (insufficient safeguarding of credentials, etc.) | -| Impact type | Integrity, Confidentiality | -| Threatened Assets | Certificates, private keys, credentials and other application specific sensitive data | -| Affected Services | All services | -| Potential mitigations | REC-NS Network Segmentation & Filter Network Traffic
REC-LOG Logging, Monitoring and Alerting
REC-SDD Secure data deletion | - -| | | -|--|-----------------------| -| | REC-SS Secure Storage | -|--|-----------------------| - -#### 7.2.4.2 Threats concerning VMs/Containers - -| | | -|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VM-C-01 | -| Threat title | Abuse of a privileged VM/Container | -| Threat description |

It's possible to run VMs/Containers with unintended configurations. Such misconfigurations can help the adversaries to compromise even strongest of VM/Container isolation measures.

Such misconfigurations scenarios include:

  • • VMs/Containers can be configured to have more privileges than what is actually required (e.g. settings that give it unnecessary, and perhaps unplanned, privileges). For example, an attacker with access to such a container, can use it to gain higher privileges on host, perform un-authorized operations and get to anything that the host, or any of the containers running on that host, can reach.
  • • VMs/Containers have unintended read/write access to a directory on host filesystem. This could allow an attacker to perform unauthorized modifications to the contents, create symbolic links to any directories or files not directly exposed by the hostPath, install SSH keys, read secrets mounted to the host, and take other malicious actions.
| -| Threat type | Spoofing, Tampering, Information disclosure, Denial of Service and Elevation of privilege | -| Vulnerabilities | Misconfiguration or Insecure VM/Container configurations | -| Impact type | Authenticity, Integrity, Confidentiality, Availability and Authorization | -| Threatened Assets | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | -| Affected Services | SERV#01, SERV#03, SERV#04, SERV#05, SERV#06, SERV#07 | -| Potential mitigations | REC-SCONF Security Configuration
REC-IAM Identity, Authentication, and Access Management
REC-CM Certificate management
REC-ISO Strong Isolation
REC-SNFLC Security VNF/CNF lifecycle
REC-NS Network Segmentation & Filter Network Traffic
REC-SS Secure Storage
REC-ADMC Admission Control Service | - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VM-C-02 | -| Threat title | VM/Container escape attack | -| Threat description | VNF/CNF deployed on the same physical machine as tenants share the same host kernel and host OS resources. Lack of strong isolation between the VMs/Containers and the host allows for a potential risk of a rogue VM/Container escaping the VM/Container confinement and impacting other co-hosted VMs/Containers. In others, an attacker may deploy a new malicious | - -| | | -|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

VM/Container configured without network rules, user limitations, etc. to bypass existing defenses within O-Cloud infrastructure.

Attacker deploys malicious VM/Container to escape the host (Hypervisor/Container Engine/Host OS) and reach the server's hardware, then the malicious VM/Container can gain root access to the whole server where it resides. This gives the malicious VM/Container full control on all the VMs/Containers hosted on the same hacked server. This could allow an attacker to undermine the confidentiality, integrity and/or availability of VNFs/CNFs resources.

Containers can be deployed by various means, such as via Docker's create and start APIs or via a web application such as the Kubernetes dashboard or Kubeflow. Adversaries may deploy containers based on retrieved or built malicious images or from benign images that download and execute malicious payloads at runtime.

When a malicious VM/Container escapes isolation, it can gain full control over the underlying host and cause any of the below serious threats:

  • • Attacker would gain the ability to mount attacks on the host or compromise the host functionalities
  • • Compromise the confidentiality & integrity of co-hosted VMs/Containers and tenants
  • • Launch DDOS attacks on co-hosted VMs/Containers and host services thereby degrading their performance
  • • Introduce new vulnerabilities in host to be used for future attacks
  • • Lack of network segmentation could potentially expose other VMs/Containers in the environment to attack. An example of this could be reconnaissance, exploitation and subsequent lateral movement to another host within the cluster.
| -| Threat type | Spoofing, Tampering, Information disclosure, Denial of Service and Elevation of privilege | -| Vulnerabilities | Shared tenancy vulnerabilities (multitenant environment), Lack of strong VM/Container isolation, lack of authentication, Insecure networking, Unrestricted communication between VMs/Containers | -| Impact type | Authenticity, Integrity, Confidentiality, Availability and Authorization | -| Threatened Assets | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | -| Affected Services | SERV#01, SERV#03, SERV#04, SERV#05, SERV#06, SERV#07 | -| Potential mitigations |

REC-ISO Strong Isolation

REC-IAM Identity, Authentication, and Access Management

REC-CM Certificate management

REC-NS Network Segmentation & Filter Network Traffic

REC-LOG Logging, Monitoring and Alerting

REC-SCONF Security Configuration

REC-SNFLC Security VNF/CNF lifecycle

REC-SS Secure Storage

| - -![Diagram illustrating the VM/Container escape attack. It shows a stack of layers: VM(s)/Container(s) (Near RT RIC, O-CU, O-DU) on top of a Hypervisor or Container Engine, which runs on a Host OS, which in turn runs on Hardware resources. Red arrows with numbered circles indicate the attack path: 1. An external attack on the Near RT RIC VM/Container. 2. An escape from the Near RT RIC VM/Container through the Hypervisor/Container Engine. 3. Access to the Host OS. 4. Further attacks on the O-CU and O-DU VMs/Containers via the compromised Host OS.](01e00200a536673d6cd0e6d8705047a0_img.jpg) - -Diagram illustrating the VM/Container escape attack. It shows a stack of layers: VM(s)/Container(s) (Near RT RIC, O-CU, O-DU) on top of a Hypervisor or Container Engine, which runs on a Host OS, which in turn runs on Hardware resources. Red arrows with numbered circles indicate the attack path: 1. An external attack on the Near RT RIC VM/Container. 2. An escape from the Near RT RIC VM/Container through the Hypervisor/Container Engine. 3. Access to the Host OS. 4. Further attacks on the O-CU and O-DU VMs/Containers via the compromised Host OS. - -Figure 7-4 : Illustration of the VM/Container escape attack - -| | | -|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VM-C-03 | -| Threat title | VM/Container data theft | -| Threat description |

The VNF/CNF remotely stores sensitive data (e.g. passwords, private keys, subscription data, logs) on the logical volume that the IMS/DMS allocates to the VNF/CNF. An attacker can retrieve/manipulate these data if they have been stored in an insecure way (e.g. clear text, unsalted hashes) or a malware is installed on the logical volume that the VIM allocates to the VNF/CNF.

Container example: Adversaries may attempt to discover containers and other resources that are available locally within O-Cloud. Other resources may include images, deployments, pods, nodes, and other information such as the status of a cluster. These resources can be viewed within web applications such as the Kubernetes dashboard or can be queried via the Docker and Kubernetes APIs. In Docker, logs may leak information about the environment, such as the environment’s configuration, which services are available, and what cloud provider the victim may be utilizing. The discovery of these resources may inform an adversary’s next steps in the environment, such as how to perform lateral movement and which methods to utilize for execution.

| -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Lack of authentication, insecure data storage | -| Impact type | Integrity, Confidentiality | -| Threatened Assets | Images, environment’s configuration, and other information such as the status of a cluster | -| Affected Services | SERV#01, SERV#02 | -| Potential mitigations |
  • REC-IAM Identity, Authentication, and Access Management
  • REC-CM Certificate management
  • REC-NS Network Segmentation & Filter Network Traffic
  • REC-LOG Logging, Monitoring and Alerting
  • REC-PHY Physical Security Protection
  • REC-SS Secure Storage
  • REC-SDD Secure data deletion
| - -| | | -|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VM-C-04 | -| Threat title | VM/Container migration attacks | -| Threat description |

The attacks that exploit VM/Container migration can be divided into two subcategories based on the target plane:

  1. 1. Control Plane Attacks: These attacks target the module that is responsible for handling the migration process on a server which is called the migration module that is found in the host. By exploiting a bug in the migration module software, the attacker can hack the server and take full control over the migration module. This gives the attacker the ability to launch malicious activities including the following:
    1. a. Migration Flooding: The attacker moves all the VMs/Containers that are hosted on the hacked server to a victim server that does not have enough resource capacity to host all the moved VMs/Containers. This causes a denial of service for the VNFs/CNFs running in the VMs/Containers of the victim server as there will not be enough resources to satisfy the demands of all the hosted VMs/Containers leading into VM/Container performance degradation and VM/Container crashes.
    2. b. False Resource Advertising: The hacked server claims that it has a large resource slack (a large amount of free resources). This attracts other servers to off-load some of their VMs/Containers to the hacked server so that the O-Cloud workload gets distributed over the O-Cloud servers. After moving VMs/Containers from other servers to the hacked server, the attacker can exploit other vulnerabilities to break into the offloaded VMs/Containers as now these VMs/Containers are placed on a server that is under the control of the attacker.
  2. 2. Data Plane Attacks: These constitute the second type of VM/Container migration attacks and those attacks target the network links over which the VM/Container is moved from a server to another. Such data plane attacks include the MitM where an attacker sniffs the packets that are exchanged between the source and destination servers and reads the migrated memory pages. The attacker can monitor and/or modify the received packets while continuing to forward them to victim VM/Container resides so that the victim does not detect that any malicious activity is going on.
| -| Threat type | Tampering, Information disclosure, Denial of Service | -| Vulnerabilities | Host misconfiguration, lack of authentication, memory pages copied in clear, vulnerable code exploits | -| Impact type | Integrity, Confidentiality, Availability | -| Threatened Assets | VNFs/CNFs (Near RT RIC, O-CU, O-DU) | -| Affected Services | SERV#03, SERV#04, SERV#05, SERV#06, SERV#07 | -| Potential mitigations |

REC-CM Certificate management

REC-NS Network Segmentation & Filter Network Traffic

REC-IAM Identity, Authentication and Access Management

REC-SNFLC Security VNF/CNF lifecycle

REC-LOG Logging, Monitoring and Alerting

REC-RA Remote Attestation

| - -![Illustration of the migration flooding attack. A server with a hacked migration module (step 1) is shown. The migration module (step 2) is used to migrate VMs/Containers (step 3) from the server to a victim server. The victim server's migration module is also shown. The diagram includes layers for VMs/Containers, Near RT RIC, O-CU, O-DU, Hypervisor or Container Engine, Host OS, and Hardware resources. A red line at the top indicates that the attacker migrates more VMs/Containers than the capacity of the victim server.](fe25bbee6685ab20f50ffc80c3feddd8_img.jpg) - -Illustration of the migration flooding attack. A server with a hacked migration module (step 1) is shown. The migration module (step 2) is used to migrate VMs/Containers (step 3) from the server to a victim server. The victim server's migration module is also shown. The diagram includes layers for VMs/Containers, Near RT RIC, O-CU, O-DU, Hypervisor or Container Engine, Host OS, and Hardware resources. A red line at the top indicates that the attacker migrates more VMs/Containers than the capacity of the victim server. - -Figure 7-5 : Illustration of the migration flooding attack - -![Illustration of the false resource advertising attack. A server with a hacked migration module (step 1) is shown. The migration module (step 2) is used to migrate VMs/Containers (step 3) from the server to a victim server. The victim server's migration module is also shown. The diagram includes layers for VMs/Containers, Near RT RIC, O-CU, O-DU, Hypervisor or Container Engine, Host OS, and Hardware resources. A red line at the top indicates that the attacker migrates more VMs/Containers than the capacity of the victim server.](08f6ace0c83e7394657fa372b47aec04_img.jpg) - -Illustration of the false resource advertising attack. A server with a hacked migration module (step 1) is shown. The migration module (step 2) is used to migrate VMs/Containers (step 3) from the server to a victim server. The victim server's migration module is also shown. The diagram includes layers for VMs/Containers, Near RT RIC, O-CU, O-DU, Hypervisor or Container Engine, Host OS, and Hardware resources. A red line at the top indicates that the attacker migrates more VMs/Containers than the capacity of the victim server. - -Figure 7-6 : Illustration of the false resource advertising attack - -![Illustration of the migration MITM attack. A user is shown interacting with a Hacked Server and a Victim server. The Hacked Server has a migration module that is intercepting the migration process. The Victim server has a migration module that is also shown. The diagram includes layers for VMs/Containers, Near RT RIC, O-CU, O-DU, Hypervisor or Container Engine, Host OS, and Hardware resources. A red line indicates the migration path from the Hacked Server to the Victim server, and a green line indicates the user's interaction with the Victim server.](753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg) - -Illustration of the migration MITM attack. A user is shown interacting with a Hacked Server and a Victim server. The Hacked Server has a migration module that is intercepting the migration process. The Victim server has a migration module that is also shown. The diagram includes layers for VMs/Containers, Near RT RIC, O-CU, O-DU, Hypervisor or Container Engine, Host OS, and Hardware resources. A red line indicates the migration path from the Hacked Server to the Victim server, and a green line indicates the user's interaction with the Victim server. - -Figure 7-7 : Illustration of the migration MITM attack - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VM-C-05 | -| Threat title | Changing virtualization resource without authorization | -| Threat description | IMS/DMS which manage the Virtualization layer is responsible for assigning virtualized resource as requested. | - -| | | -|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

There are several ways to cause a DoS attack for the VNFs/CNFs:

  • • If IMS/DMS are compromised or the O2 interface is not securely protected, an attacker who compromised the IMS/DMS or breached the O2 interface can change the virtualized resource used by a VNF/CNF by manipulating the allocation of virtualized resource. For example, when an instantiated VNF/CNF is running, adversaries having access to a compromised IMS/DMS or adversaries breaching the insecure O2 interface can misguide the Virtualization layer to reduce the resource of or delete a VM/Container on which a VNF/CNF is running. This can result in the reliability, availability or even illegal termination of a VNF/CNF and hence the denial of service.
  • • Hardware resource configuration and state information (e.g. events) exchange is performed through O2 interface. If the IMS is compromised or the O2 interface is not securely protected, an attacker who compromised the IMS or breached the O2 interface can tamper the hardware configuration and state information so that the virtualized resource supported by the hardware layer becomes unreliable.
  • • Adversaries having access to a compromised virtualization layer can change the virtualization resource used by the instantiated VNF/CNF without authorization,
  • • A malicious VM/Container deployed for one instance of a VNF/CNF on a host can illegally occupy the resources of the instantiated VNF/CNF deployed on the same host, resulting in resource limitation of the instantiated VNF/CNF

In this type of attacks, the extra allocation of resources for the malicious VM/Container comes at the expense of the other VMs/Containers that share the same server as the malicious VM/Container, where these victim VMs/Containers get allocated less share of resources than what they should actually obtain, which in turn degrades their performance.

| -| Threat type | Denial of Service | -| Vulnerabilities | Insecure O1/O2 interfaces, Lack of authentication/access control on IMS/DMS | -| Impact type | Availability | -| Threatened Assets | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | -| Affected Services | SERV#01 | -| Potential mitigations | REC-LOG Logging, Monitoring and Alerting
REC-CM Certificate management
REC-IAM Identity, Authentication and Access Management
REC-ISO Strong Isolation
REC-PHY Physical Security Protection
REC-AUD Security Audit | - -![Diagram illustrating the Theft-of-Service/DoS Attack. It shows a stack of layers: VM(s)/Container(s) (Near RT RIC, O-CU, O-DU), Hypervisor or Container Engine, Host OS, and Hardware resources. A malicious VM/Container running is shown on the left, and a victim VM/Container running is on the right. Three numbered red arrows indicate the attack flow: 1. An attacker (person with a laptop) sends a signal to the O-DU VM. 2. The O-DU VM sends a signal to the Hypervisor or Container Engine. 3. The Hypervisor or Container Engine sends a signal to the Victim VM/Container running, which is then terminated.](789ee0a267b24f34bd1f45313e86c9a4_img.jpg) - -Diagram illustrating the Theft-of-Service/DoS Attack. It shows a stack of layers: VM(s)/Container(s) (Near RT RIC, O-CU, O-DU), Hypervisor or Container Engine, Host OS, and Hardware resources. A malicious VM/Container running is shown on the left, and a victim VM/Container running is on the right. Three numbered red arrows indicate the attack flow: 1. An attacker (person with a laptop) sends a signal to the O-DU VM. 2. The O-DU VM sends a signal to the Hypervisor or Container Engine. 3. The Hypervisor or Container Engine sends a signal to the Victim VM/Container running, which is then terminated. - -Figure 7-8 : Illustration of the Theft-of-Service/DoS Attack - -| | | -|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VM-C-06 | -| Threat title | Failed or incomplete VNF/CNF termination or releasing of resources | -| Threat description |

A misconfigured VNF/CNF is instantiated in the O-Cloud infrastructure to access data not erased from a terminated VNF/CNF or any VNF/CNF that has released resources. Data could include application data, cryptographic keys, etc.

Abuse of resources allocation in the O-Cloud infrastructure to allocate to a malicious VNF/CNF the virtual resources released from a terminated VNF/CNF or from a VNF/CNF that has released resources after a move or a scaling process.

Inclusion of concealed software in the O-Cloud infrastructure to prevent the deletion/erasure of data and states of the VNF/CNF that has been terminated.

| -| Threat type | Information disclosure | -| Vulnerabilities | Lack of authentication, misconfigurations (VNF/CNF, Host OS, Hypervisor/Container Engine) | -| Impact type | Confidentiality | -| Threatened Assets | Sensitive data (e.g. passwords, private keys, subscription data, logs), VNFs/CNFs (Near RT RIC, O-CU, O-DU) software and data | -| Affected Services | No affected services | -| Potential mitigations | REC-SNFLC Security VNF/CNF lifecycle
REC-LOG Logging, Monitoring and Alerting
REC-SS Secure Storage
REC-SCONF Security Configuration | - -#### 7.2.4.3 Threats concerning VM/Container images - -| | | -|---------------------|-------------------------------| -| Threat ID | T-IMG-01 | -| Threat title | VM/Container images tampering | - -| | | -|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat description |

An attacker can inject malicious code or tamper the information inside the unprotected image during on boarding. Then after the instantiation of the VNF/CNF, the tampered code can cause DoS, information stealing, fraud and so on. There are several attacks categories belonging to this threat. Such attacks include:

  • • Build machine attacks: If an attacker can modify or influence the way a VM/Container image is built, they could insert malicious code that will subsequently get run in the production environment.
  • • Supply chain attacks: Once the VM/Container image is built, it gets stored in a registry, and it gets retrieved or “pulled” from the registry at the point where it’s going to be run. An attacker who can replace an image or modify an image between build and deployment could run arbitrary code on your deployment.
| -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Compromised VM/Container images (Build machine attacks, Supply chain attacks) at rest, lack of authentication, misconfiguration or Insecure VM/Container images configurations | -| Impact type | Integrity, Confidentiality | -| Threatened Assets | VM/Container images | -| Affected Services | SERV#02 | -| Potential mitigations | REC-AUD Security Audit
REC-LOG Logging, Monitoring and Alerting
REC-IMGP Image Protection
REC-VHPM Vulnerability Handling and Patch Management
REC-IAM Identity, Authentication, and Access Management
REC-CM Certificate management
REC-SDLC Secure Development Lifecycle
REC-ADMC Admission Control Service | - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-IMG-02 | -| Threat title | Insecure channels with images repository | -| Threat description |

Images often contain sensitive components like an organization’s proprietary software, and embedded secrets and administrator credentials. If connections to registries are performed over insecure channels, man-in-the-middle attacks could intercept network traffic and therefore the contents integrity and confidentiality of images may be compromised. There is also an increased risk of man-in-the-middle attacks that could intercept network traffic intended for registries and steal developer or administrator credentials within that traffic. Thus, could be used to provide fraudulent or outdated images to orchestrators, etc.

| -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Compromised VM/Container images in transit | -| Impact type | Integrity, Confidentiality | -| Threatened Assets | VMs/Containers images | - -| | | -|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Affected Services | SERV#02 | -| Potential mitigations | REC-NS Network Segmentation & Filter Network Traffic
REC-IAM Identity, Authentication, and Access Management
REC-CM Certificate management
REC-IMGP Image Protection
REC-LOG Logging, Monitoring and Alerting | - -| | | -|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-IMG-03 | -| Threat title | Secrets disclosure in VM/Container images | -| Threat description |

There are scenarios which benefit from including configuration and secrets, such as passwords or credentials in VNFs/CNFs images. For e.g. VMs/Containers require to be able to connect to other VMs/Containers within the deployment as well as with external entities. All these connections need to be authenticated and secured. One way of achieving this is to provide the requisite secrets or keys to the VMs/Containers which allow them to authenticate, be authenticated, secure the communication channel and signature. A common but in-secure means of providing secrets to the VMs/Containers is by packaging the secrets or the keys with the image itself. There is the risk that the same can be extracted, read or manipulated before the VM/Container is deployed and the secret used.

With a long supply chain, VM/Container images are vulnerable to outside scrutiny. With VM/Container images containing secrets or keys, this becomes a serious threat vector. Adversaries can extract them by obtaining a copy of the image and they can be potentially shared with third parties for illicit gain.

  • • Secrets embedded within a VM/Container image can be stolen.
  • • Secrets embedded within a VM/Container image can be modified

Compromised private keys and algorithms used for image signing due to poor key protection/management/design could undermine the security of image signing process.

| -| Threat type | Spoofing, Tampering, Information disclosure | -| Vulnerabilities | Secret exposure in VNF/CNF images | -| Impact type | Authenticity, Integrity, Confidentiality | -| Threatened Assets | VM/Container images | -| Affected Services | SERV#02 | -| Potential mitigations | REC-AUD Security Audit
REC-IMGP Image Protection
REC-SS Secure Storage
REC-SDLC Secure Development Lifecycle | - -| | | -|---------------------|-------------------| -| Threat ID | T-IMG-04 | -| Threat title | Build image on VL | - -| | | -|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat description |

Adversaries may build a VM/Container image directly on the VL to bypass defenses that monitor for the retrieval of malicious images from a registry.

Container example: A remote build request may be sent to the Docker API that includes a Dockerfile that pulls a vanilla base image, such as alpine, from a public or local registry and then builds a custom image upon it.

An adversary may take advantage of that build API to build a custom image on the host that includes malware downloaded from their C2 server, and they then may deploy container using that custom image. If the base image is pulled from a public registry, defenses will likely not detect the image as malicious since it's a vanilla image. If the base image already resides in a local registry, the pull may be considered even less suspicious since the image is already in the environment.

| -| Threat type | Spoofing, Tampering, Information disclosure, Denial of Service and Elevation of privilege | -| Vulnerabilities | Host misconfiguration, lack of authentication | -| Impact type | Authenticity, Integrity, Confidentiality, Availability and Authorization | -| Threatened Assets | VM/Container images | -| Affected Services | SERV#02, SERV#05 | -| Potential mitigations |

REC-AUD Security Audit

REC-IAM Identity, Authentication, and Access Management

REC-CM Certificate management

REC-LOG Logging, Monitoring and Alerting

REC-IMGP Image Protection

REC-SB Secure Boot

REC-SS Secure Storage

REC-RA Remote Attestation

| - -#### 7.2.4.4 Threats concerning the virtualization layer (Host OS-Hypervisor/Container engine) - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VL-01 | -| Threat title | VM/Container hyperjacking attack | -| Threat description |

VMs/Containers run on host machines, and it is needed to ensure that those hosts (Hypervisor/Container Engine/Host OS- are not running vulnerable code (for example, old versions of components with known vulnerabilities).

Hyperjacking is an attack in which adversaries gain control over the host of a server or install a malicious Hypervisor/Container Engine/Host OS and exploit that to run malicious applications on the VM/Container that run on top of the host. This would enable the attacker to control all the VMs/Containers running on the host.

Hyperjacking involves installing a malicious, fake the Hypervisor/Container Engine/Host OS that can manage the entire server system. If the attacker gains access to the Hypervisor/Container Engine/Host OS, everything that is connected to that server can be manipulated. The Hypervisor/Container Engine/Host OS represents a single point of failure when it comes to the security and protection of sensitive information.

| - -| | | -|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

For a hyperjacking attack to succeed, an attacker would have to take control of the Hypervisor/Container Engine/Host OS by the following methods:

  • • Injecting a rogue Hypervisor/Container Engine or Host OS beneath the original hypervisor or on top of an existing Hypervisor/Container Engine/Host OS
  • • Directly obtaining control of the original Hypervisor/Container Engine or Host OS
  • • Running a rogue hypervisor on top of an existing hypervisor
| -| Threat type | Spoofing, Tampering, Information disclosure, Denial of Service and Elevation of privilege | -| Vulnerabilities | Host misconfiguration, lack of authentication | -| Impact type | Authenticity, Integrity, Confidentiality, Availability and Authorization | -| Threatened Assets | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | -| Affected Services | SERV#01, SERV#03, SERV#04, SERV#05, SERV#06, SERV#07 | -| Potential mitigations |

REC-SCONF Security Configuration

REC-SB Secure Boot

REC-VHPM Vulnerability Handling and Patch Management

REC-NS Network Segmentation & Filter Network Traffic

REC-IAM Identity, Authentication, and Access Management

REC-CM Certificate management

REC-ISO Strong Isolation

REC-SS Secure Storage

| - -![Diagram illustrating the VM/Container hyperjacking attack. An attacker (laptop icon) is shown on the left. Arrows from the attacker point to two red boxes labeled '1' and '2'. Box '1' is 'Rogue Hypervisor or Container Engine' and box '2' is 'Rogue Host OS'. Above these boxes are three blue boxes representing VMs/Containers: 'Near RT RIC', 'O-CU', and 'O-DU'. Arrows from the 'Rogue Hypervisor or Container Engine' point to the 'O-CU' and 'O-DU' boxes. The 'Rogue Host OS' box is positioned between the 'Rogue Hypervisor or Container Engine' and the 'Hardware resources' box at the bottom.](7ed5d5770331f31ade15439a21c31425_img.jpg) - -``` - -graph TD - Attacker[Attacker] --> RogueHE[1 Rogue Hypervisor or Container Engine] - Attacker --> RogueOS[2 Rogue Host OS] - - subgraph Virtual_Machines - RIC[Near RT RIC] - OCU[O-CU] - ODU[O-DU] - end - - RogueHE --> RIC - RogueHE --> OCU - RogueHE --> ODU - - subgraph Legitimate_Stack - HE[Hypervisor or Container Engine] - HOS[Rogue Host OS] - end - - RogueOS --> Hardware[Hardware resources] - HOS --> Hardware - -``` - -Diagram illustrating the VM/Container hyperjacking attack. An attacker (laptop icon) is shown on the left. Arrows from the attacker point to two red boxes labeled '1' and '2'. Box '1' is 'Rogue Hypervisor or Container Engine' and box '2' is 'Rogue Host OS'. Above these boxes are three blue boxes representing VMs/Containers: 'Near RT RIC', 'O-CU', and 'O-DU'. Arrows from the 'Rogue Hypervisor or Container Engine' point to the 'O-CU' and 'O-DU' boxes. The 'Rogue Host OS' box is positioned between the 'Rogue Hypervisor or Container Engine' and the 'Hardware resources' box at the bottom. - -Figure 7-9 : Illustration of the VM/Container hyperjacking attack - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VL-02 | -| Threat title | Boot tampering | -| Threat description |

The bootloader of the virtualization layer (Host OS, Hypervisor, Container Engine) for VNF/CNF may be maliciously tampered by an attacker, e.g. the attacker compromises hypervisor or host OS to tamper the bootloader of guest OS (in case of VM) or Container.

In a O-Cloud environment any failure during the boot sequence can result in a number of situations that need to be handled by the NFO/FOCOM:

| - -| | | -|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |
  • • failure of the physical machine to start at all
  • • physical machine entering a safe-mode
  • • physical machine continuing boot regardless of the integrity measurements
| -| Threat type | Tampering | -| Vulnerabilities | Host misconfigurations, lack of authentication | -| Impact type | Integrity | -| Threatened Assets | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | -| Affected Services | SERV#01, SERV#03, SERV#04, SERV#05, SERV#06, SERV#07 | -| Potential mitigations | REC-SB Secure Boot
REC-PHY Physical Security Protection
REC-RA Remote Attestation
REC-LOG Logging, Monitoring and Alerting | - -| | | -|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VL-03 | -| Threat title | Attack internal network services | -| Threat description | In addition to attacking the network between containers, adversaries can also attack supporting services such as Kubernetes DNS service, which is only reachable from within the cluster network. The highly distributed nature of containers requires shared services for example for coordination and service discovery. An attacker can target these services to degrade services. For example, a denial-of-service against the service discovery infrastructure could prevent O-Cloud to react to changing resource requirements properly. Thus, O-Cloud may no longer be able to scale appropriately to sudden demand spikes [i.37]. | -| Threat type | Denial of Service | -| Vulnerabilities | Lack of authentication, vulnerable code exploits, design weakness, misconfiguration | -| Impact type | Availability | -| Threatened Assets | Software components at runtime and their associated data | -| Affected Services | SERV#03, SERV#04, SERV#05, SERV#06, SERV#07 | -| Potential mitigations | REC-ISO Strong Isolation
REC-NS Network Segmentation & Filter Network Traffic
REC-IAM Identity, Authentication and Access Management
REC-ADMC Admission Control Service | - -#### 7.2.4.5 Threats concerning O-Cloud interfaces - -##### 7.2.4.5.1 O2 interface - -Two main interfaces are defined in O-RAN WG6 specification and identified as critical assets of O-Cloud, i.e. interfaces O2 between O-Cloud and SMO. The threats on these interfaces are as follows. - -| | | -|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-O2-01 | -| Threat title | MitM attacks on O2 interface between O-Cloud and SMO | -| Threat description |

If the interface O2 interface is not protected, an attacker can attack all the requests/responses sent between the O-Cloud and the SMO (FOCOM and NFO).

For example, the attacker can tamper/alter/disclose requests and services (See ‘Critical services’ in 2.3) sent over O2 between O-Cloud and SMO, hence the virtualized resource or relevant status information is not as requested. This affects the normal operation of the O-Cloud, and even causes DoS attacks, information leakage.

An attacker can tamper the specific assignment of virtualized resources to cause resource assignment errors or an attacker can intercept virtualized resources state information leading to information disclosure.

An attacker can compromise IMS to tamper with the hardware state information (e.g. deleting hardware alarm information) to affect the hardware's operation or to result in information disclosure (e.g. an attacker can get the hardware configuration from the compromised IMS. Then, the attacker can attack the hardware according to the configuration such as CPU type, memory size etc.). An attacker can also tamper or intercept the hardware resource configuration and state information if the configuration and state information are transmitted using an insecure protocol on the O2 interface.

| -| Threat type | Tampering, Information disclosure, Denial of Service | -| Vulnerabilities | Insecure O2 interface, lack authentication | -| Impact type | Integrity, Confidentiality, Availability | -| Threatened Assets | Telemetry, provisioning, logs, software management, performance information | -| Affected Services | SERV#01 | -| Potential mitigations | REC-NS Network Segmentation & Filter Network Traffic
REC-IAM Identity, Authentication, and Access Management
REC-CM Certificate management
REC-SCONF Security Configuration | - -##### 7.2.4.5.2 O-Cloud API - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OCAPI-01 | -| Threat title | MitM attacks on O-Cloud interface between VNFs/CNFs and the virtualization layer | -| Threat description |

An attacker can attack an instantiated VNF/CNF through a compromised virtualization layer. For example, cryptographic keys or other security critical data of an instantiated VNF/CNF could be stolen by an attacker with access to the virtualization layer, or the virtualized resource provided by the Virtualization layer to the instantiated VNF/CNF can be manipulated or the

| - -| | | -|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | bootloader of Guest OS (in case of VM) or Container of an instantiated VNF/CNF can be tampered by an attacker via a compromised virtualization layer. | -| Threat type | Tampering, Information disclosure, Denial of Service | -| Vulnerabilities | Insecure O-Cloud APIs, lack of authentication | -| Impact type | Integrity, Confidentiality, Availability | -| Threatened Assets | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | -| Affected Services | SERV#01, SERV#03, SERV#04, SERV#05, SERV#06, SERV#07 | -| Potential mitigations | REC-NS Network Segmentation & Filter Network Traffic
REC-IAM Identity, Authentication, and Access Management
REC-CM Certificate management
REC-SCONF Security Configuration
REC-SS Secure Storage
REC-PHY Physical Security Protection | - -#### 7.2.4.6 Threats concerning hardware resources - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-HW-01 | -| Threat title | Cross VM/Container side channel attacks | -| Threat description |

In a typical cross-VM/Container side channel attack scenario, an adversary places a malicious VM/Container co-resident to the target VM/Container so that they share the same hardware resources. Then, the attacker extracts useful information such as cryptographic keys from the target VM/Container to use them for traffic eavesdropping and man-in-the-middle attacks. Through the side channel attack, an attacker sharing the same cache as the victim can monitor the cache access behavior of the victim. For example, the attacker is able to monitor cache timing information by measuring the execution of different operations on the victim's VM/Container. Generally, the attacker exploits timings in the shared high-level cache memory. However, power consumption or electromagnetic leaks can also be used as a vector to launch side channel attacks.

In the virtual environment, prior to the cross-VM/Container side channel attack, the attacker needs to identify the target VM/Container's location and place a malicious VM/Container co-resident with the target. Later, that attacker may use the maliciously placed VM/Container to extract information from the target VM/Container with the side channel attack.

Hardware vulnerabilities in processors can also have a large impact on O-Cloud security. Flaws in chip design can result in the compromise of tenant information in the cloud through side-channel attacks4.

| -| Threat type | Tampering, Information disclosure, Denial of Service | -| Vulnerabilities | Flaws in chip design, use of shared hardware, Lack of isolation, lack of authentication | -| Impact type | Integrity, Confidentiality, Availability | - -4 Graz University of Technology (2018), Meltdown and Specter. [Online] Available at: - -| | | -|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threatened Assets | Sensitive data (e.g. passwords, private keys, subscription data, logs), VNFs/CNFs (Near RT RIC, O-CU, O-DU) related data | -| Affected Services | SERV#01, SERV#03, SERV#04, SERV#05, SERV#06, SERV#07 | -| Potential mitigations | REC-ISO Strong Isolation
REC-PHY Physical Security Protection
REC-IAM Identity, Authentication, and Access Management
REC-CM Certificate management
REC-SS Secure Storage | - -![Diagram illustrating a cross VM/Container side channel attack. It shows a stack of layers: VM(s)/Container(s) (Near RT RIC, O-CU, O-DU) at the top, Hypervisor or Container Engine, Host OS, and Hardware resources at the bottom. A red arrow labeled '1' points from an attacker icon to the VM(s)/Container(s) layer. Another red arrow labeled '2' points from the VM(s)/Container(s) layer down to the Shared cache in the Hardware resources layer, indicating a side channel attack path.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) - -Diagram illustrating a cross VM/Container side channel attack. It shows a stack of layers: VM(s)/Container(s) (Near RT RIC, O-CU, O-DU) at the top, Hypervisor or Container Engine, Host OS, and Hardware resources at the bottom. A red arrow labeled '1' points from an attacker icon to the VM(s)/Container(s) layer. Another red arrow labeled '2' points from the VM(s)/Container(s) layer down to the Shared cache in the Hardware resources layer, indicating a side channel attack path. - -Figure 7-10 : Illustration of a cross VM/Container side channel attack - -| | | -|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-HW-02 | -| Threat title | MitM attacks on the interface between virtualization layer and hardware | -| Threat description | An attacker can utilize the vulnerabilities of hardware (e.g. Meltdown and Specter of CPU in host) to attack virtualization layer and/or VNFs/CNFs through this interface, resulting in tampering, information disclosure or DoS. | -| Threat type | Tampering, Information disclosure, Denial of Service | -| Vulnerabilities | Insecure interfaces between HW and VL layers, lack of authentication, misconfiguration | -| Impact type | Integrity, Confidentiality, Availability | -| Threatened Assets | All assets | -| Affected Services | All services | -| Potential mitigations | REC-PHY Physical Security Protection
REC-NS Network Segmentation & Filter Network Traffic
REC-IAM Identity, Authentication, and Access Management
REC-CM Certificate management | - -#### 7.2.4.7 Threats concerning O-Cloud management (SMO, NFO, FOCOM) - -| | | -|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-ADMIN-01 | -| Threat title | Denial of service against NFO/FOCOM | -| Threat description |

A denial-of-service attack against the NFO/FOCOM can interfere with the ability of operators to control and maintain their deployments. This can lead to the inability to react to changing resource requirements. In addition, the NFO/FOCOM is the external API to interact with the O-Cloud platform. Thus, other services may become inaccessible as well. For example, operators may be unable to retrieve logs, telemetry data. An attacker could use this opportunity to hide additional attacks on VM/Container instances.

In addition, an attacker on the NFO/FOCOM could prevent the O-Cloud software update to exploit a known security flaw in the O-Cloud software.

| -| Threat type | Denial of Service | -| Vulnerabilities | Lack of authentication, vulnerable code exploits, design weakness, insecure O2 interface | -| Impact type | Availability | -| Threatened Assets | VM/Container images, VNF/CNF, host OS, Hypervisor/Container Engine software | -| Affected Services | SERV#02, SERV#05 | -| Potential mitigations |

REC-IAM Identity, Authentication and Access Management

REC-CM Certificate management

REC-AUD Security Audit

REC-SCONF Security Configuration

| - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-ADMIN-02 | -| Threat title | Abuse an O-Cloud administration service | -| Threat description |

Usually, the SMO including NFO/FOCOM is exposed to the tenant in a web front-end or REST API. In case these interfaces contain software vulnerabilities or implement authentication and authorization insufficiently, an adversary would be able to gain access to the VM/Container management and pose as a tenant. It is also possible that an adversary gains the ability to submit requests without prior authentication and authorization.

The NFO/FOCOM interfaces encompass a great deal of privileges because anyone gaining sufficient access is able to deploy new instances and disrupt existing O-Cloud services. It may also be possible for an adversary to submit compromised VM/Container images that unsuspecting tenants then use to initiate O-Cloud services. Moreover, adversaries can use the same access to extract business data, configuration data, user data and possibly credentials. For example, they may be able to create backups of VM/Container instances or they can export VM/Container images. The impact of compromised credentials is exacerbated by the fact that weak and insufficient safeguarding of credentials is recognized as one of the top threats in cloud computing [i.38].

Container example: Adversaries may abuse a container administration service to execute commands within a container. A container administration service such as the Docker daemon, the Kubernetes API server, or the kubelet may allow remote management of containers within an environment.

| - -| | | -|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | Container example: In Docker, adversaries may specify an endpoint during container deployment that executes a script or command, or they may use a command such as docker exec to execute a command within a running container. In Kubernetes, if an adversary has sufficient permissions, they may gain remote execution in a container in the cluster via interaction with the Kubernetes API server, the kubelet, or by running a command such as kubectl exec . | -| Threat type | Tampering, Information disclosure, Denial of Service and Elevation of privilege | -| Vulnerabilities | Lack of authentication, secret exposure (insufficient safeguarding of credentials), vulnerable code exploits, design weakness | -| Impact type | Integrity, Confidentiality, Availability, Authorization | -| Threatened Assets | VNF/CNF, host OS, Hypervisor/Container Engine software and related information | -| Affected Services | SERV#03, SERV#04, SERV#06, SERV#07 | -| Potential mitigations | REC-NS Network Segmentation & Filter Network Traffic
REC-IAM Identity, Authentication, and Access Management
REC-CM Certificate management
REC-AUD Security Audit
REC-SCONF Security Configuration
REC-VHPM Vulnerability Handling and Patch Management | - -#### 7.2.4.8 Threats concerning Acceleration Abstraction Layer (AAL) - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AAL-01 | -| Threat title | Attacker exploits insecure API to gain access to hardware accelerator resources | -| Threat description |

Insecure AAL API allows an attacker to tamper the requests/responses sent between the AAL components, the O-Cloud platform and O-RAN APPs/VNFs/CNFs.

For example, the attacker can tamper requests and services sent over AALI-C-Mgmt between IMS and the hardware accelerator manager, hence capability of the hardware accelerator device, fault information, logs, performance information and others are not as requested. This affects the normal operation of the O-Cloud, and even causes tampering.

An attacker can tamper application (e.g. O-DU) requests sent over AALI-C-App to an AAL implementation for allocation of buffers. This affects the normal operation of the applications, and even causes tampering.

An attacker can tamper with application (e.g. O-DU) requests sent over AALI-P for configuring and managing the AAL-LPU(s). This affects the normal operation of the applications, and even causes tampering.

| -| Threat type | Tampering | -| Vulnerabilities | Insecure AAL APIs and interfaces, lack of authentication and authorization | -| Impact type | Integrity | -| Threatened Assets | Data in transit AALI-C-App & AALI-P interfaces, Data in transit vendor specific interface, AAL profiles, AAL-LPUs, Stored AAL data, AAL software, Device firmware | -| Affected Services | SERV#03, SERV#04, SERV#06, SERV#07 | - -| | | -|------------------------------|----------------------------------------------------------------------------------------------------| -| Potential mitigations | REC-IAM Identity, Authentication and Access Management
REC-LOG Logging, Monitoring and Alerting | -|------------------------------|----------------------------------------------------------------------------------------------------| - -| | | -|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AAL-02 | -| Threat title | Internal Overload DoS attack targeting AAL services | -| Threat description |

Overload situation could appear in the case of DoS attack or increased traffic on AAL interfaces. Inability to mitigate traffic volumetric attacks on AAL affects availability of AAL data and services.

DoS attacks on the AALI-C interface affect the different services provided by the hardware accelerator manager and the transport abstraction framework.

DoS attacks on the AALI-P interface affect the configuration and management of AAL-LPU (Acceleration Abstraction Layer Logical Processing Unit) by an application (e.g. O-DU) in addition to acceleration functionality.

| -| Threat type | Denial of Service | -| Vulnerabilities | Insecure AAL APIs and interfaces, lack of authentication and authorization | -| Impact type | Availability | -| Threatened Assets | AAL profiles, AAL-LPUs, Stored AAL data, AAL software, Device firmware | -| Affected Services | SERV#03, SERV#04, SERV#06, SERV#07 | -| Potential mitigations | REC-IAM Identity, Authentication and Access Management
REC-LOG Logging, Monitoring and Alerting | - -| | | -|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AAL-03 | -| Threat title | Fail to clear resources | -| Threat description |

Failure to clear accelerator resources after a process termination can cause an information leakage and incorrect results for computations. Further, failure to release accelerator resources may prevent other processes from running.

This threat is relevant to accelerator resources either inside the hardware accelerator device (internal memories, registers, cache) or in the O-Cloud memories used by accelerators.

| -| Threat type | Information disclosure, Denial of service | -| Vulnerabilities | Lack of secure deletion of data after process termination, Insecure AAL APIs, Flaws in AAL design | -| Impact type | Confidentiality, Availability | -| Threatened Assets | AAL profiles, AAL-LPUs, Stored AAL data, AAL software, Device firmware | -| Affected Services | SERV#03, SERV#06, SERV#07 | -| Potential mitigations | REC-LOG, REC-SS, REC-PHY, REC-SDD | - -| | | -|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AAL-04 | -| Threat title | HAM compromise | -| Threat description | A malicious actor can gain access to HAM to gain unauthorized access and control of the hardware accelerator device. This can result in the disruption of services (DoS) and tampering of accelerator components, such as firmware, drivers which can cause the accelerator to behave abnormally or crash altogether. | -| Threat type | Tampering, Denial of service | -| Vulnerabilities | Lack of access control, Insecure HAM APIs, Flaws in HAM design | -| Impact type | Integrity, Availability | -| Threatened Assets | Data in transit AALI-C-App & AALI-P interfaces, Data in transit vendor specific interface, AAL profiles, AAL-LPUs, Stored AAL data, AAL software, Device firmware | -| Affected Services | SERV#03, SERV#06, SERV#07 | -| Potential mitigations | REC-LOG, REC-SS, REC-PHY, REC-SDD | - -| | | -|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AAL-05 | -| Threat title | Malicious memory accesses | -| Threat description |

AAL that allows one process running on the hardware accelerator device to access memory owned by another process running on the hardware accelerator device can leak information (impact on confidentiality).

Similarly, AAL allowing concurrently executing processes to write to one another's memory may have correctness errors (impact on integrity).

If multiple processes are running concurrently and one is allowed to dominate accelerator resources, the other may suffer from degraded performance. For example, if one process can evict all cache entries belonging to the other, the victim will suffer performance penalties (impact on availability).

| -| Threat type | Information disclosure, Tampering, Denial of service | -| Vulnerabilities | Unrestricted memory access, Lack of access control, Insecure AAL APIs, Flaws in AAL design | -| Impact type | Confidentiality, Integrity, Availability | -| Threatened Assets | AAL profiles, AAL-LPUs, Stored AAL data, AAL software, Device firmware | -| Affected Services | SERV#03, SERV#06, SERV#07 | -| Potential mitigations | REC-LOG, REC-SS, REC-PHY, REC-SDD, REC-ISO | - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AAL-06 | -| Threat title | Firmware attacks | -| Threat description | Hardware accelerators often have their own firmware, which can be targeted by attackers. This could include modifying the firmware to introduce vulnerabilities (e.g., malware) or installing | - -| | | -|------------------------------|---------------------------------------------------------------------------------------------------------------------------------| -| | malicious firmware to extract/modify sensitive information or execute unauthorized actions (e.g., control the device remotely). | -| Threat type | Information disclosure, Tampering | -| Vulnerabilities | Weak accelerator design, Misconfiguration, Insecure AAL/HAM APIs | -| Impact type | Confidentiality, Integrity | -| Threatened Assets | AAL profiles, AAL-LPUs, Stored AAL data, AAL software, Device firmware | -| Affected Services | SERV#03, SERV#06, SERV#07 | -| Potential mitigations | REC-LOG, REC-SS, REC-PHY, REC-SDD, REC-ISO | - -#### 7.2.4.9 Threats concerning O-Cloud instance ID - -| | | -|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-O-CLOUD-ID-01 | -| Threat title | ID reuse in O-Cloud's object lifecycle | -| Threat description |

In O-Cloud, objects such as Containers, Pods, Nodes, and Services are identified by their IDs within a given compute pool (e.g., cluster in Kubernetes). When an object is deleted, its ID becomes available for reuse. This means that a new object can be created with the same ID as a previously deleted object. If an object gets deleted but all its associated data isn't properly isolated or cleaned, the ID, if reused, could lead to unintended data associations or leaks.

Potential consequences:

  • • Data Residue: A new object, reusing an ID, may inherit residual data or configurations from its predecessor, leading to potential misconfigurations and incorrect data associations. This can result in sensitive data exposure.
  • • Data Overwrite: Automated processes unaware of the deletion and subsequent recreation might mistakenly write or read data from the new object, thinking it's the old one.
  • • Monitoring Ambiguities: Monitoring tools might combine metrics from the old and new objects, resulting in confusing data.
  • • Operational Disruptions: The new object might operate based on the residual configurations of the old object, potentially leading to system inefficiencies or failures.
| -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Predictable ID generation, Insufficient logging or auditing, Insufficient ID validation | -| Impact type | Integrity, Confidentiality | -| Threatened Assets | O-Cloud Provisioning information, Software components at runtime and their associated data, Security event logs | -| Affected Services | SERV#04, SERV#05 | -| Potential mitigations | REC-IDM O-Cloud ID secure management | - -| | | -|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-O-CLOUD-ID-02 | -| Threat title | Node redundancy in O-Cloud deployments | -| Threat description |

Nodes in O-Cloud often represent physical or virtual machines. If a machine fails and is replaced without deleting its corresponding Node object, and the new machine is given the same ID or the hostname, O-Cloud might treat the new machine as if it were the original.

Potential consequences:

  • • Resource Mismatch: The new host might have different resources (CPU, memory, storage) than the old one, leading to scheduling issues or resource constraints.
  • • Stale Data: The new node might inherit data or configurations from the old node, leading to potential security or operational risks.
  • • Network Issues: Network configurations or IP address assignments might be inconsistent or conflicting.
| -| Threat type | Spoofing, Tampering, Information disclosure, Denial of Service | -| Vulnerabilities | Lack of node validation, Inadequate resource allocation and monitoring, Lack of network configuration verification | -| Impact type | Authenticity, Integrity, Confidentiality, Availability | -| Threatened Assets | O-Cloud Provisioning information, Software components at runtime and their associated data, Security event logs | -| Affected Services | SERV#04, SERV#05 | -| Potential mitigations | REC-IDM O-Cloud ID secure management | - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-O-CLOUD-ID-03 | -| Threat title | O-Cloud ID mismanagement | -| Threat description |

IDs are crucial for uniquely identifying objects within the O-Cloud. Mismanagement occurs when these IDs are not properly assigned, tracked, or validated, leading to potential overlaps or inconsistencies.

Potential consequences:

  • • ID Collision: Due to system glitches or bugs, two distinct objects could inadvertently be allocated the same ID. Such an occurrence is termed an ID collision. This can result in operations meant for one object inadvertently affecting the other.
  • • Resource Overwrite: If two objects share the same ID, updates or modifications intended for one might overwrite the data of the other, leading to data inconsistencies or loss.
  • • ID-Based Permissions: Many security protocols and access controls in O-Cloud can be tied to object IDs. If an attacker can predict, guess, or manipulate the ID generation process, they might gain unauthorized access to resources.
  • • Log Merging: Monitoring tools and logging systems use IDs to track events and operations related to specific objects. If two objects share an ID, their logs might get merged, making it challenging to trace events back to their source.
| - -| | | -|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |
  • RBAC Anomalies: Role-Based Access Control (RBAC) regulations attached to specific object IDs could unintentionally approve or restrict access to the novel object due to misidentification.
| -| Threat type | Spoofing, Tampering, Information Disclosure, Repudiation, Elevation of Privilege, Denial of Service | -| Vulnerabilities | Inefficient ID assignment algorithm, Lack of validation checks during the ID assignment or object creation process, Weak or absent monitoring of ID lifecycle, Insufficient randomization in ID generation, Lack of timely updates to RBAC policies, Lack of ID collision detection | -| Impact type | Authenticity, Integrity, Non-repudiability, Confidentiality, Availability, Authorization | -| Threatened Assets | O-Cloud Provisioning information, Software components at runtime and their associated data, Security event logs | -| Affected Services | SERV#04, SERV#05 | -| Potential mitigations | REC-IDM O-Cloud ID secure management | - -#### 7.2.4.10 Threats concerning time synchronization - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-TS-01 | -| Threat title | Time synchronization disruption in O-Cloud | -| Threat description |

Disruption or manipulation of the time synchronization process within the O-Cloud can lead to severe security and operational issues. An attacker may target the time synchronization mechanisms to alter time settings across O-Cloud nodes, leading to:

  • Impersonation of time synchronization server: An attacker may impersonate a legitimate time synchronization server, tricking nodes into accepting incorrect time data. This can cause nodes to synchronize with a malicious time source, leading to widespread time discrepancies.
  • Data integrity loss: Inconsistent timestamps can corrupt logs and audit trails within the O-Cloud, making it difficult to trace and analyze security events accurately.
  • Operational disruption: Time-sensitive operations within the O-Cloud may be disrupted, leading to data loss and service outages.
  • Authentication and authorization bypass: Many security mechanisms in the O-Cloud rely on accurate time. Disrupted time synchronization can undermine token expiration, certificate validity, and other time-based access controls, potentially allowing unauthorized access to O-Cloud resources.

EXAMPLE: Time-sensitive operations such as automated backups, scheduled tasks (e.g., resource scaling, patch management), and certificate renewals.

NOTE: This threat is linked to the operation of CronJob resources as described in clause 4.3.1.1.6 of the O-RAN specification [i.65]. Any disruption or manipulation of the time synchronization process can severely impact scheduled operations managed by CronJobs within the O-Cloud.

| -| Threat type | Spoofing, Tampering, Denial of Service and Elevation of privilege | -| Vulnerabilities | Insecure time synchronization protocols | - -| | | -|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | Insufficient authentication mechanisms and access controls for the time synchronization settings
Misconfiguration of time synchronization settings on O-Cloud nodes | -| Impact type | Authenticity, Integrity, Availability and Authorization | -| Threatened Assets | Log and audit trails
O-Cloud time synchronization settings | -| Affected Services | SERV#03, SERV#06, SERV#07 | -| Potential mitigations | REC-SCONF Security Configuration
REC-IAM Identity, Authentication, and Access Management
REC-CM Certificate management
REC-LOG Logging, Monitoring, and Alerting | - -# 8 Recommendations and best practices - -A large number of useful and relevant security guidelines and best practices exist that are relevant for VM/Container-based virtualization and cloud computing in general. Therefore, we provide them here collectively and highly recommend that readers consult them for additional references: - -- 3GPP TS 33.848 Study on security impacts of virtualisation -- MITRE containers matrix -- CIS Critical Security Controls -- CIS Docker Benchmark -- CIS VMWARE Benchmark -- ONAP master documentation -- CISA/NSA Kubernetes security guidance -- OpenStack security guide -- Cloud native wiki by aqua -- ANSSI “Recommandations de sécurité relatives aux déploiements de conteneur docker “ -- CISA/NSA “Security guidance for 5g cloud infrastructures” parts 1 to 4 -- GSMA NG.126 “Cloud Infrastructure Reference Model” -- Docker best practices -- FFTelecoms “Référentiel d'objectifs de sécurité en matière de fonctions réseau virtualisées “ -- Fraunhofer AISEC Threat analysis of container-as-a-service for network function virtualization - -## 8.1 REC-CM Certificate management - -**Recommendation:** O-Cloud should support Public Key Cryptography for the purpose of distributing Public Key Certificates (PKC) for authenticating, authorizing, and encrypting links between components in O-Cloud. Each operator should develop a Certificate Policy in accordance with their regional and national requirements. In addition, Operators should setup a renewal procedure (preferably automatically) of certificates prior to their expiration. - -In O-Cloud, the following scenarios are considered for certificate usage: - -- O-Cloud and VNFs/CNFs should employ certificates which can be used for images signing and verification during onboarding and registration. -- SMO and VNF/CNF should employ certificates which can be used in order to establish secure connections between them. -- SMO employs certificates in order to establish secure management connections with NFO and FOCOM. -- O-Cloud infrastructure employs certificate(s) in order to establish secure connections with NFO and FOCOM through O2 interface. - -### **Best practices to fulfill this recommendation:** - -| BP ID | Description | -|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-CM-BP-1 | The certificate policy should be consistent with the Internet X.509 Certificate Policy and Certification Practices Framework as defined in IETF RFC 3647 [i.9]. | -| REC-CM-BP-2 | In order to eliminate or mitigate risks against attacks such as spoofing, tampering and information disclosure, secure connection can be established on all the interfaces within O-Cloud. IPsec and TLS mechanisms are widely deployed to protect the communication between O-Cloud components using certificates. | -| REC-CM-BP-3 | Certificate management in O-Cloud should be automated and manual operations should be avoided as much as possible. Automated certificate lifecycle management should be supported, i.e. creation, update and revocation of certificate. | -| REC-CM-BP-4 | It's important to continuously monitor and audit certificates that are issued and active, with the ability to generate audits and keep on top of expirations and renewals to avoid any disruption in O-Cloud services. Unknown, rogue or non-complaint certificates can result in an unexpected outage, or worse, misuse that allows unintended access to O-Cloud components. | -| REC-CM-BP-5 | Securing the CAs that issue the certificates is critical. If a CA is compromised, attackers can issue their own identities that will be trusted by default across O-Cloud, and this can be extremely costly to remediate, as it effectively invalidates every identity issued by that CA. Hardware devices such as HSMs should be used to secure CA certificates and keys, ensure robust protection and complete visibility, policy enforcement, and automation for all certificates. | - -For more details see ETSI GR NFV-SEC 005 [i.10]. - -**This recommendation can help to mitigate:** T-GEN-02, T-GEN-04, T-VM-C-01, T-VM-C-02, T-VM-C-03, T-VM-C-04, T-VM-C-05, T-IMG-01, T-IMG-02, T-IMG-04, T-VL-01, T-O2-01, T-OCAPI-01, T-HW-01, T-HW-02, T-ADMIN-01, T-ADMIN-02, T-TS-01 - -## 8.2 REC-NS Network Segmentation & Filter Network Traffic - -**Recommendation:** Physical and logical segmentation to prevent access to potentially sensitive O-Cloud components and information should be implemented. In addition, network policies should be defined to ensure a secure communication between VMs/Containers and limit the communication between VMs/Containers as much as possible to limit potential damage if a VM/Container is compromised. - -### **Best practices to fulfill this recommendation:** - -| BP ID | Description | -|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-NS-BP-1 | Isolate O-Cloud infrastructure components that do not require broad network access. | -| REC-NS-BP-2 | Configure access controls, network proxies, gateways, and firewalls to limit access to:
  • Critical O-Cloud components. Most cloud environments support separate virtual private cloud (VPC) instances that enable further segmentation of cloud systems.
  • Systems used to create and manage accounts.
| -| REC-NS-BP-3 | Follow best practices for network firewall and proxies configurations to allow only necessary ports and legitimate traffic to enter and exit the network. | -| REC-NS-BP-4 | Operate intrusion detection, analysis, and response systems on a separate network from the production environment to lessen the chances that an adversary can see and interfere with critical response functions. | -| REC-NS-BP-5 | Consider filtering DNS requests to unknown, untrusted, or known bad domains and resources. Resolving DNS requests with on-premise/proxy servers may also disrupt adversary attempts to conceal data within DNS packets. | -| REC-NS-BP-6 | Enforce proxies and use dedicated servers for services such as DNS and only allow those systems to communicate over respective ports/protocols, instead of all systems within a network. | -| REC-NS-BP-7 | Consider using IP allowlisting along with user account management to ensure that data access is restricted not only to valid users but only from expected IP ranges to mitigate the use of stolen credentials to access data. | -| REC-NS-BP-8 | Apply extended ACLs to block unauthorized protocols outside the trusted network. | -| REC-NS-BP-9 | Upon identifying a compromised network device being used to bridge a network boundary, block the malicious packets using an unaffected network device in path, such as a firewall or a router that has not been compromised. Continue to monitor for additional activity and to ensure that the blocks are indeed effective. | -| REC-NS-BP-10 | When flood volumes exceed the capacity of the network connection being targeted, it is typically necessary to intercept the incoming traffic upstream to filter out the attack traffic from the legitimate traffic. Such defenses can be provided by the hosting Internet Service Provider (ISP) or by a 3rd party such as a Content Delivery Network (CDN) or providers specializing in DoS mitigations. | -| REC-NS-BP-11 | Filter network traffic to prevent use of protocols across the network boundary that are unnecessary. | -| REC-NS-BP-12 | Use of network intrusion detection and prevention systems that can
  • Identify traffic patterns and use network signatures to identify traffic for specific adversary malware, can be used to mitigate malicious activity at the network level.
  • Detect and prevent remote service scans.
| - -**This recommendation can help to mitigate:** T-GEN-02, T-GEN-06, T-VM-C-01, T-VM-C-02, T-VM-C-03, T-VM-C-04, T-IMG-02, T-VL-01, T-O2-01, T-OCAPI-01, T-HW-02, T-ADMIN-02 - -## 8.3 REC-IAM Identity, Authentication and Access Management - -**Recommendation:** A strong IAM framework should be in place to ensure authentication, authorization, accounting and access control. It should be used to initiate, capture, record and manage user identities and their related access permissions to O-Cloud assets in an automated way. - -The IAM framework should be set up to manage and secure access to NFO/FOCOM, VNFs/CNFs, Host OS, Hypervisor, Container Engine, data and services that reside in the O-Cloud. This framework should protect credentials and accounts associated with O-Cloud platforms. Specifically, IAM protects root accounts for servers in the O-Cloud, limits privileged access to the O-Cloud control panel and governs ongoing access to privileged resources in the O-Cloud. - -IAM should be based on Authentication, Authorization, and Accounting (AAA) systems and least privileges approach to limit actions administrators can perform and provide a history of user actions to detect unauthorized use and abuse. - -Protocols without encryption/authentication mechanisms should not be used. Access to administrative and management interfaces from untrusted network sources should be limited. - -### **Best practices to fulfill this recommendation:** - -| Req ID | Description | -|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-IAM-BP-1 |

OAuth2.0 with access token defined by IETF RFC 6749 [i.11] should be used for the authorization of API request and notifications. There are several existing Access Token solutions. Such solutions are Openstack Keystone5, OpenID Connect6, 3GPP authorization framework ETSI TS 133 5017, IETF TLS-Based AccessToken Binding8 9.

For more details see ETSI GR NFV-SEC 022 [i.12].

| -| REC-IAM-BP-2 |

O-Cloud components must support authenticated and secure access to API, GUI and command line interfaces. In addition, they must support Traffic Filtering (for example, FireWall, IDS/IPS).

| -| REC-IAM-BP-3 |

O-Cloud interfaces should support secure and encrypted communications, and confidentiality and integrity of network traffic on all channels. All APIs access must use TLS protocol, including back-end APIs [i.45].

| -| REC-IAM-BP-4 |

O-Cloud components should implement controls enforcing separation of duties and privileges, least privilege use and least common mechanism (e.g. Role-Based Access Control).

Communication between different trust domains is not allowed, by default.

The O-Cloud infrastructure must not allow the effect of an attack on one trust domain to impact the other domains either directly or indirectly.

| -| REC-IAM-BP-5 |

The O-Cloud should not reuse the same authentication credential (e.g., key-pair) on different components (e.g., on different hosts, or different services).

The O-Cloud should protect all secrets by using strong encryption techniques and storing the protected secrets externally from the component.

The O-Cloud should provide secrets dynamically as and when needed.

| - -5 - -6 [https://openid.net/specs/openid-connect-core-1\\_0.html](https://openid.net/specs/openid-connect-core-1_0.html) - -7 TSI TS 133 501: "5G; Security architecture and procedures for 5G System (3GPP TS 33.501)" - -8 draft-ietf-oauth-token-binding-08: "OAuth 2.0 Token Binding", Work in progress - -9 IETF RFC 8705: "OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens" - -| | | -|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-IAM-BP-6 | Data Centre Operations staff and O-Cloud components should use management protocols that limit security risk. Management protocols such as SNMPv3, SSH v2, ICMP, NTP, syslog, and TLS v1.2 or higher. | -| REC-IAM-BP-7 | Remotely available services that may be unnecessary should be disabled or blocked. Remote access to internal O-Cloud resources should be controlled using centrally managed concentrators such as VPNs and other managed remote access systems of network, proxies, gateways, and firewalls.
Strong two-factor or multi-factor authentication for remote service accounts to mitigate an adversary's ability to leverage stolen credentials should be used. | -| REC-IAM-BP-8 | Ensure VM/Containers are not running as root by default. | -| REC-IAM-BP-9 | Do not allow domain administrator accounts (of Active directory) to be used for day-to-day operations that may expose them to potential adversaries on unprivileged systems.
Consider using temporary credentials for accounts that are only valid for a certain period of time to reduce the effectiveness of compromised accounts. | -| REC-IAM-BP-10 | Limit access to the root account and prevent users from loading kernel modules and extensions through proper privilege separation and limiting Privilege Escalation opportunities. | -| REC-IAM-BP-11 | Container: Run the microservice with the least privilege possible; First, never use the --privileged flag. It gives all so-called capabilities to the container, and it can access host devices ( /dev ) including disks, and also has access to the /sys and /proc filesystem. And with a little work the container can even load kernel modules on the host 10 . The good thing is that containers are per default unprivileged. You would have to configure them explicitly to run privileged. | -| REC-IAM-BP-12 | When Administrative Shell is necessary, restrict Administrative Shell execution policy to administrators. Be aware that there are methods of bypassing the Administrative Shell execution policy, depending on environment configuration. | -| REC-IAM-BP-13 | Least privilege principles:
  • • Use the principal of least privilege and protect administrative access to domain trusts such as the service account in Kubernetes, Openstacks, etc. to limit impact of exploitation.
  • • Restrict administrator accounts to as few individuals as possible, following least privilege principles.
  • • Limit permissions associated with creating and modifying images or VMs/Containers based on the principle of least privilege.
| -| REC-IAM-BP-14 | Prevent credential overlap across systems of administrator and privileged accounts. | -| REC-IAM-BP-15 | Ensure critical system files as well as those known to be abused by adversaries have restrictive permissions and are owned by an appropriately privileged account, especially if access is not required by users nor will inhibit system functionality. | -| REC-IAM-BP-16 | Audit domain and local accounts as well as their permission levels routinely to look for situations that could allow an adversary to gain wide access by obtaining credentials of a privileged account. These audits should also include if default accounts have been enabled, or if new local accounts are created that have not been authorized. | -| REC-IAM-BP-17 | Do not put user or admin domain accounts in the local administrator groups across systems unless they are tightly controlled, as this is often equivalent to having a local administrator account with the same password on all systems. | - -10 - -| | | -|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-IAM-BP-18 | Do not allow remote access to services as a privileged account unless necessary. | -| REC-IAM-BP-19 | Do not allow remote access via SSH as root or other privileged accounts. | -| REC-IAM-BP-20 | Restrict execution of particularly vulnerable binaries to privileged accounts or groups that need to use it to lessen the opportunities for malicious usage. | -| REC-IAM-BP-21 | Ensure that any accounts used by third-party providers to access these systems are traceable to the third-party and are not used throughout the network or used by other third-party providers in the same environment. Ensure there are regular reviews of accounts provisioned to these systems to verify continued business need and ensure there is governance to trace de-provisioning of access that is no longer required. Ensure proper system and access isolation for critical network systems through use of account privilege separation. | -| REC-IAM-BP-22 | A Cloud Access Security Broker (CASB) can be used to set usage policies and manage user permissions on cloud applications to prevent access to application access tokens. | -| REC-IAM-BP-23 |

Password policy

  • • O-Cloud components that utilize default username and password should be changed immediately after the installation, and before deployment to a production environment. When possible, passwords should be updated periodically and properly secured. (Refer to NIST guidelines when creating password policies NIST Special Publication 800-63B11, CIS Password Policy Guide12).
  • • Use strong passwords to increase the difficulty of credential hashes from being cracked if they are obtained.
  • • Do not reuse local administrator account passwords across systems. Ensure password complexity and uniqueness such that the passwords cannot be cracked or guessed.
  • • In case SSH is used with password (not recommended), Ensure SSH key pairs have strong passwords and refrain from using key-store technologies such as ssh-agent unless they are properly protected.
  • • Consider rotating access keys within a certain number of days to reduce the effectiveness of stolen credentials.
  • • Use strong passphrases for private keys to make cracking difficult. Do not store credentials within the Registry. Establish an organizational policy that prohibits password storage in files.
  • • Ensure that cloud accounts, particularly privileged accounts, have complex, unique passwords across all systems on the network. Passwords and access keys should be rotated regularly. This limits the amount of time credentials can be used to access resources if a credential is compromised without your knowledge. Cloud service providers may track access key age to help audit and identify keys that may need to be rotated.
| - -**This recommendation can help to mitigate:** T-GEN-02, T-GEN-04, T-VM-C-01, T-VM-C-02, T-VM-C-03, T-VM-C-04, T-VM-C-05, T-IMG-01, T-IMG-02, T-IMG-04, T-VL-01, T-O2-01, T-OCAPI-01, T-HW-01, T-HW-02, T-ADMIN-01, T-ADMIN-02, T-TS-01 - -11 - -12 - -## 8.4 REC-VHPM Vulnerability Handling and Patch Management - -**Recommendation:** A vulnerability handling process should be in place to find potentially exploitable software vulnerabilities, to determine what types and levels of threat may use software exploits and 0-days against O-Cloud and to remediate them. - -A patch management process should be implemented to check unused dependencies, unmaintained and/or previously vulnerable dependencies, unnecessary features, components, files, and documentation. - -### **Best practices to fulfill this recommendation:** - -| BP ID | Description | -|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-VHPM-BP-1 | Regularly scan O-Cloud software components for vulnerabilities and establish procedures to rapidly patch systems when critical vulnerabilities are discovered through scanning and through public disclosure. | -| REC-VHPM-BP-2 | Regularly scan the internal network for available services to identify new and potentially vulnerable services. | -| REC-VHPM-BP-3 | Continuous monitoring of vulnerability sources and the use of automatic and manual code review tools should also be implemented as well. | -| REC-VHPM-BP-3 |

Patch strategy shall be applied for each component to maintain the O-Cloud software.

The patch strategy should handle regular and emergency patches. It is also needed to be prepared for testing patches and rollback procedures. The patch strategy should be automated. It's also recommended to make use of plugins for monitoring software and notifying of pending patches.

Keep in mind that some patches require a restart of their service, a new deployment (VM/Container image) or even a reboot (host) to become effective. If this won't be done, patching otherwise could be as effective as just not to patch. Technical details when to restart a service, a host or initiate a new deployment need to be defined in the patch strategy too.

There are four different patch domains:

  • • Images: the VM/Container distribution
  • • Hypervisor/Container Engine software: e.g., VMware vSphere, Docker
  • • Orchestration software (Kubernetes, Mesos, OpenShift, ...)
  • • Host operating system
| -| REC-VHPM-BP-4 | Maintain SBOMs for O-RAN software components in a centralized repository. This will make possible to quickly scan and search the SBOM for any Zero-Day vulnerability when get disclosed, which allows O-Cloud operator to respond quickly to the Zero-day vulnerability to mitigate potential attacks. For more details about SBOM see Clause 4 'SBOM Guidelines for O-RAN' in [i.42]. | - -**This recommendation can help to mitigate:** T-GEN-01, T-IMG-01, T-VL-01, T-ADMIN-02, T-O2-01, T-OCAPI-01 - -## 8.5 REC-SCONF Security Configuration - -**Recommendation:** The O-Cloud virtualization layer shall - -- Be configured to ensure conformance to industry standard benchmarks and requirements with respect to security configurations. -- Use automated or manual mechanisms to detect configuration drifts/misconfigurations from industry standard benchmarks and requirements. - -### **Best practices to fulfill this recommendation:** - -| BP ID | Description | -|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-SCONF-BP-1 |

O-Cloud virtualization layer should be configured to adhere/conform to industry standard benchmarks and guidelines for securing the virtualization layer. For example, the CIS benchmark guidelines enforce many security configurations related to the container deployment like:

  • Avoid running containers as privileged, apply the principle of least privilege access controls for privileged containers, and restrict functionality of privileged containers.
  • Restrict containers from using hostPath volume mounts write permissions from within container.
  • Enforce non-root default user in containers (using Kubernetes pod spec parameters or USER directive in Dockerfile).
| -| REC-SCONF-BP-2 |

O-Cloud operator & vendor should perform automated or manual scans to check security posture adherence to industry standard benchmarks. For example, Cloud Security Posture Management tools can be used to check conformance to industry standard benchmarks like CIS, NIST, etc.

| -| REC-SCONF-BP-3 |

O-Cloud CNF vendors should define the CPU and Memory requirements of their CNF applications, ie, the CPU and Memory requirements for the CNF applications to perform its functions under normal operating scenarios and the threshold limit value of CPU & Memory requirements beyond which the CNF should not be allowed to use. O-Cloud virtualization platform should consider the CPU & Memory resource requirements & limits associated to each CNF provided by O-Cloud CNF vendors during onboarding of the CNFs.

| -| REC-SCONF-BP-4 |

O-Cloud virtualization platform should consider enforcing the O-Cloud CNF vendors to specify the CPU & Memory resource requirements & limits using suitable admission controller solutions. Setting CPU & memory limits will help OCloud virtualization platform to avoid a rogue CNF container using up all resources thereby starving off other co-located CNF containers.

| - -**This recommendation can help to mitigate:** T-VM-C-01, T-VM-C-02, T-VM-C-06, T-VL-01, T-ADMIN-01, T-ADMIN-02, T-TS-01 - -## 8.6 REC-SDLC Secure Development Lifecycle - -**Recommendation:** Software providers should assume that their VNFs/CNFs and VL software contain flaws and have appropriate processes in place to mitigate these cases. To this end, they should adopt a secure software development life-cycle (S-SDLC). A S-SDLC integrates security considerations into the normal software development life-cycle. This ensures that risks, threats, and security mechanisms are formalized alongside the development of VNFs/CNFs and VL. - -### **Best practices to fulfill this recommendation:** - -| Req ID | Description | -|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-SDLC-BP-1 |

Define and implement good coding practices. This includes writing documentation, adopting secure programming guidelines, enforcing code quality metrics and performing software tests. In particular, code quality and adherence to coding standards can be checked automatically with tools, such as SonarQube13. With this approach, the chance of introducing easily exploitable vulnerabilities into the code is reduced.

| - -13 - -| | | -|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-SDLC-BP-2 | Modern continuous integration (CI) and continuous delivery (CD) systems can be used to build new container images from code repositories, such as Git 14 automatically. Thus, every commit can be used to generate a new container image that is immediately deployed for testing in a development environment. Once a new software version passes all tests, it can be deployed automatically to the O-Cloud platform. This step should be safeguarded by an internal approval process. For example, operators can configure their CI/CD pipeline to only start deployment in production after quality assurance, security testing and operations have approved the new version. | -| REC-SDLC-BP-3 | During development, developers may include private keys and configuration files with passwords into their VM/Container images for convenience and testing reasons. However, this information should never be published in a production VM/Container image. Thus, one of important step before actually deploying any VM/Container image to the O-Cloud platform is to verify that no sensitive information is included. In case of Docker, recent versions allow to specify these image differences between development and operations by using multiple FROM commands, i.e., one for development and one production in the respective Dockerfile. | -| REC-SDLC-BP-4 | Define mechanisms and processes that ensure that VM/Container image metadata is signed and verified. Thus, if operators download an image from a party they trust, they can verify the signature and the cryptographic hashes of the image files.

Example: use of Docker Notary and Content Trust 15 | - -This recommendation can help to mitigate: T-GEN-01, T-IMG-01, T-IMG-03 - -## 8.7 REC-SNFLC Security App/VNF/CNF lifecycle - -**Recommendation:** Security in the life cycle management of Apps/VNFs/CNFs should be integrated during development, onboarding, instantiation, scaling, migration, and termination. Security lifecycle management must be adapted to work in a more dynamic environment with fast-changing network topology, data flow paths, and network addresses. - -**Best practices to fulfill this recommendation:** - -| Req ID | Description | -|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-SNFLC-BP-1 | Before an App/VNF/CNF is deployed, the NFO/FOCOM system should verify compliance with its build-configuration standards. A check can include but is not limited to:
  • Security of the configuration
  • Whether the package contains only trusted and expected components
  • Whether trusted components have been altered (integrity)
| -| REC-SNFLC-BP-2 | Apps/VNFs/CNFs can easily be cloned and instantiated. As a result, a security framework must address the following elements:
  • Depending on the migration technique, certificates, accounts, media access control addresses, or hardware IDs will look identical after cloning.
  • Trusted platform modules (e.g., TPM, HSM, Intel’s Trusted Execution Technology, or TXT) may be required to ensure that virtual components can provide attestation or a true status of the security of the underlying hardware and physical location.
| - -14 - -15 [https://docs.docker.com/engine/security/trust/content\\_trust/](https://docs.docker.com/engine/security/trust/content_trust/) - -This recommendation can help to mitigate: T-GEN-03, T-VM-C-01, T-VM-C-02, T-VM-C-04, T-VM-C-06 - -## 8.8 REC-IMGP Image Protection - -**Recommendation:** Only images from secure and trusted sources should be used. These images should be scanned to ensure that images do not contain vulnerable software. - -The App/VNF/CNF images shall not be packaged with embedded secrets such as passwords or credentials, or any other critical configuration data. - -During the onboarding, the authenticity and integrity of the VNF Package should be verified against the signature provided by the VNF provider. Furthermore, Operators should undertake additional security validation of the VNF Package during the onboarding process and operator's signing should be used to certify the VNF as authorized to onboard into the operator's network [i.46], [i.47]. - -**Best practices to fulfill this recommendation:** - -### *Image Scanning* - -Scanning process needs to identify when Apps/VNFs/CNFs are running with out-of-date packages that need to be updated for security patches. Further, it should identify malware that has been built into an image. The O-Cloud VL should enforce image scans to check and flag the presence of secrets in images. - -- (1) VM/Container images need to be frequently scanned throughout the lifecycle of the App/VNF/CNF - -| During Development | Within the registry | Before Deployment | During Runtime | -|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -|

Perform frequent scanning for known vulnerability or misconfiguration on App/VNF/CNF image during build phase. E.g., Check for malware, secrets stored in image.

Ideal to automate with CI pipeline.

Responsible: O-RAN Solution Provider/Vendor

|

Regular scan for App/VNF/CNF image known vulnerability or misconfiguration stored in the registry. E.g., scan for new vulnerabilities after built.

Responsible: O-RAN Solution Provider/Vendor/Operator

|

Perform frequent scanning for known vulnerability or misconfiguration on App/VNF/CNF image before deployment using admission control techniques. Admission controller could block deployments if the image doesn't comply with the operator security policies e.g., To check the images used to create CNF pods are secure by checking for malware.

Ideal to automate with CD pipeline.

Responsible: O-RAN Solution Provider/Vendor/Operator

|

Perform continuous scanning/monitoring for known vulnerability or misconfiguration on runtime workloads, check for any open ports, VM/Container escape.

Responsible: Operator/O-Cloud Operator

| - -- (2) As part of O-RAN App/VNF/CNF development, O-RAN Solution Provider/Vendor is recommended to choose base images and packages used in the O-RAN App/VNF/CNF from a trusted publisher or create in-house base images. Choosing trusted signed images helps to mitigate MITM attacks that can introduce vulnerabilities into the base images available in public registries. -- (3) As part of O-RAN App/VNF/CNF development, O-RAN Solution Provider/Vendor is recommended to choose minimal base images that bundle only the necessary system tools and libraries required by O-RAN App/VNF/CNF, to limit the attack surface of O-RAN App/VNF/CNF. - -### *App/VNF/CNF Image Signing* - -**Responsible:** App/VNF/CNF Solution Provider/Vendor and/or Operator - -- (1) App/VNF/CNF Solution Provider creates public/private key pair for code signing. -- (2) CA verifies public key belong to the owner and issue CA certificate with attached public key. -- (3) Hash function on App/VNF/CNF Image returns image Digest. -- (4) Image Digest is encrypted with private key. -- (5) Signed App/VNF/CNF Image contains CA Certificate, Digest, Hash function. - -### *App/VNF/CNF Image Verification* - -**Responsible:** Operator or O-Cloud Operator - -- (1) Verify CA certificate for authenticity. -- (2) Decrypt digest with public key -- (3) Compare Decrypted digest with Digest computed as result of Hash function on App/VNF/CNF Image. -- (4) Verification is successful if both digest matches. - -#### *Proposed Signing/Verification Models* - -1. Software signing by Solution Provider/Vendor, Software verification at runtime by O-Cloud Operator -2. Software signing by Solution Provider/Vendor, Software verification by operator before onboarding vendor images to the operator registry -3. Software signing by Operator, Software verification at runtime by O-Cloud Operator -4. Software signing by Solution Provider/Vendor, Software verification at runtime by O-Cloud Operator and/or Operator. -5. Software signing by solution provider/vendor, Software verification by Operator and software re-signing by Operator before onboarding vendor images to the operator registry, software verification at instantiation. - -### **Other best practices:** - -- Least privilege access that limits and controls access to the images' repository and the repository of source code, secure storage, and automation for verifying the configuration of images before loading. -- Utilize a trust model such as Docker Content Trust with digital signatures to ensure runtime verification of the integrity and publisher of specific image tags. -- Implement only digitally signed host images to validate the integrity of the software used on the O-Cloud platform. Make use of this feature where possible in order to prevent and/or detect attempts by adversaries to compromise the host image. -- The registry is most sensitive part of the system and should be run in an HSM. -- The App/VNF/CNF images shall not be packaged with embedded secrets such as passwords or credentials, or any other critical configuration data. Secrets have to be stored outside the App/VNF/CNF images. For example, K8s secrets or external secrets managers (like Vault) can be used to store secret and sensitive information hence preventing the threat of packaging secrets in CNF container images. Secrets required by containerized applications can be injected into the CNF container from the External Secrets Manager as required. -- Encrypting VNF volume / swap areas: Virtual volume disks associated with VNFs may contain sensitive data. Therefore, they need to be protected. The best practice to secure the VNF volume is by encrypting them and storing the cryptographic keys at safe locations. The TPM module can also be used to securely store these keys. In - -In addition, the hypervisor should be configured to securely wipe out the virtual volume disks in the event a VNF is crashed or intentionally destroyed to prevent it from unauthorized access. VM swapping is a memory management technique used to move memory segments from the main memory to disk, which is used as a secondary memory in order to increase system performance in case the system runs out of memory. These transferred memory segments can contain sensitive information such as passwords and certificates. They can be stored on the disk and remain persistent even after system reboot. This enables an attack scenario whereby a VM swap is copied and investigated to retrieve any useful information. One way to avoid this kind of attack is to encrypt VM swap areas. Linux based tools such as dm-crypt can be used for this purpose. - -**This recommendation can help to mitigate:** T-GEN-01, T-GEN-03, T-IMG-01, T-IMG-02, T-IMG-03, T-IMG-04 - -## 8.9 REC-LOG Logging, Monitoring and Alerting - -**Recommendation:** The continuous security of O-Cloud software depends on the ability to identify attacks and reconstruct them. The earlier operators identify suspicious behavior and possible attacks, the faster they can initiate countermeasures. In the best case, they are able to stop attacks before severe harm is done. In the worst case, they at least are able to reduce the attacks' severity and collect important details on the attack itself. This knowledge is important to find and fix flaws and vulnerabilities to prevent similar attacks in the future. Therefore, a key activity is to perform logging, monitoring and alerting. - -The importance increases because of the dynamic VM/Container deployment. VMs/Containers may be started when demand arises and then quickly be terminated once they are no longer required. Furthermore, the focused nature of VMs/Containers and the application of a microservice architecture means that there are more systems to monitor. As a result, monitoring and logging must handle this dynamic landscape and be able to collect data from many systems at once. - -**Best practices to fulfill this recommendation:** - -| Req ID | Description | -|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-LOG-BP-1 | Any change to the O-Cloud components must be logged as a security event, and the logged event must include the identity of the entity making the change, the change, the date and the time of the change. | -| REC-LOG-BP-2 | Security logs should be time synchronized and regularly scanned for events of interest. | -| REC-LOG-BP-3 | Consider monitoring for the presence or loading of known vulnerable software that adversaries may drop and exploit to execute code in kernel mode. | -| REC-LOG-BP-4 | Monitor for the deployment of suspicious or unknown container images and pods in your environment, particularly containers running as root. Additionally, monitor for unexpected usage of syscalls such as mount (as well as resulting process activity) that may indicate an attempt to escape from a privileged container to host. In Kubernetes, monitor for cluster-level events associated with changing containers' volume configurations. | -| REC-LOG-BP-5 | Establish centralized logging for the activity of container and Kubernetes cluster components. This can be done by deploying logging agents on Kubernetes nodes and retrieving logs from sidecar proxies for application pods to detect malicious activity at the cluster level. | -| REC-LOG-BP-6 | Monitor logs for actions that could be taken to gather information about container infrastructure, including the use of discovery API calls by new or unexpected users. Monitor account activity logs to see actions performed and activity associated with the Kubernetes dashboard and other web applications. | -| REC-LOG-BP-7 | Consider monitoring process resource usage to determine anomalous activity associated with malicious hijacking of resources such as CPU, memory, and graphics processing resources. Monitor for suspicious use of network resources associated with cryptocurrency mining software. Monitor for common cryptomining software process names and files on local systems that may indicate compromise and resource usage. | - -| | | -|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-LOG-BP-8 | Container administration service activities and executed commands can be captured through logging of process execution with command-line arguments on the container and the underlying host. In Docker, the daemon log provides insight into events at the daemon and container service level. Kubernetes system component logs may also detect activities running in and out of containers in the cluster. | -| REC-LOG-BP-9 | Monitor interactions with images and containers by users to identify ones that are added or modified anomalously. In containerized environments, changes may be detectable by monitoring the Docker daemon logs or setting up and monitoring Kubernetes audit logs depending on registry configuration. | -| REC-LOG-BP-10 | Monitor for suspicious or unknown container images and pods in your environment. Deploy logging agents on Kubernetes nodes and retrieve logs from sidecar proxies for application pods to detect malicious activity at the cluster level. In Docker, the daemon log provides insight into remote API calls, including those that deploy containers. Logs for management services or applications used to deploy containers other than the native technologies themselves should also be monitored. | -| REC-LOG-BP-11 | Monitor for unexpected Docker image build requests to the Docker daemon on hosts in the environment. Additionally monitor for subsequent network communication with anomalous IPs that have never been seen before in the environment that indicate the download of malicious code. | -| REC-LOG-BP-12 | Alert the incident responders about a breach / attack on the O-Cloud software via email, SMS or other notification mechanisms. | -| REC-LOG-BP-13 | Alert using a notification to RASP (Runtime application self-protection) modules, or a SIEM about a breach / attack on the O-Cloud software. | - -**This recommendation can help to mitigate:** T-GEN-01, T-GEN-02, T-GEN-03, T-GEN-06, T-VM-C-02, T-VM-C-03, T-VM-C-04, T-VM-C-05, T-VM-C-06, T-IMG-01, T-IMG-02, T-IMG-04, T-VL-02, T-TS-01 - -## 8.10 REC-SB Secure Boot - -**Recommendation:** All servers that are part of O-Cloud Infrastructure should support a root of trust and secure boot to trust that the running host OS, Hypervisor/Container Engine and VNFs/CNFs code were loaded. - -**Best practices to fulfill this recommendation:** - -| Req ID | Description | -|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-SB-BP-1 | Using trusted platform module (TPM) as a hardware root of trust, the measurement of system sensitive components such as platform firmware, BIOS, bootloader, OS kernel, and other system components can be securely stored and verified. The platform measurement can only be taken when the system is reset or rebooted; there is no way to write the new platform measurement in TPM during the system run-time. The validation of the platform measurements can be performed by TPM's launch control policy (LCP) or through the remote attestation server. | - -For more details see ETSI GR NFV-SEC 007 [i.15]. - -**This recommendation can help to mitigate:** T-GEN-03, T-IMG-04, T-VL-01, T-VL-02 - -## 8.11 REC-ISO Strong Isolation - -**Recommendation:** Strong VNFs/CNFs sandboxing, isolation and segmentation should be enforced to make difficult for adversaries to advance their operation through exploitation of undiscovered or unpatched vulnerabilities. O-Cloud virtualization layer shall adopt measures to ensure strong VM/Container isolation among VM/Container workloads to limit the impact of rogue/misbehaving VM/Container on other co-hosted VMs/Containers. - -### **Best practices to fulfill this recommendation:** - -| Req ID | Description | -|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-ISO-BP-1 |

In order to prevent privilege escalations, Operators shall ensure that CNFs shall:

  • Avoid using binaries with SUID or SGID bit. Instead, specific capabilities required by the files/binaries should be provided using Linux Capabilities set
  • Avoid root user and sudo privileges within container
| -| REC-ISO-BP-2 |

Restrict the damage attackers can do once they successfully escaped a container. Again, the Linux kernel provides a couple of security features that can be used to restrict user actions. Among them are Linux security modules providing mandatory access control and user namespaces themselves.

| -| REC-ISO-BP-3 |

Restrict the large system call interface using seccomp. The seccomp ('Secure Computing') integrates a BPF-like filter mechanism for system calls into the Linux kernel. This can be used to reduce the number of system calls that a container can effectively use. Moreover, the parameters to system calls can be sanitized. Thus, seccomp reduces one attack surface by reducing the number of exploitable system calls.

| -| REC-ISO-BP-4 |

Linux kernel allows to restrict users' capabilities to perform specific operations. In particular, root users have a vast set of permissions. Linux capabilities permit a fine-grained partition of the capabilities bundled into the root user. Thus, instead of being root, different capabilities can be restricted. For example, a user can be root without having the permissions to change network settings. Currently, the Linux kernel has 37 capabilities. Unfortunately, not all capabilities have a specific, well-defined scope. For example, CAP_SYS_PTRACE permits the use of ptrace(), while CAP_SYS_ADMIN comprises many permissions such as changing the host and domain name, using mount() and unmount(), or performing various configurations of storage and memory devices. Restricting capabilities assigned to container processes limits the operations an adversary can use on the host system.

| -| REC-ISO-BP-5 |

Namespaces and cgroups are the two features that enable container-based virtualization in the Linux kernel. They provide isolation and separation of processes. However, their default configuration is often not as restrictive as possible to support many use cases. Thus, it is important to employ many namespaces and cgroups and tighten their configuration.

For example, the user namespace separates the user IDs on the host system from the user IDs of a container. A user within the container can be root, while on the host system the same user is unprivileged. As another example, the devices control group can restrict what device nodes can be created and be accessed. Other control groups limit the maximum resources a container can use. Thus, they prevent degradation or denial of services in a shared environment.

| -| REC-ISO-BP-6 |

Linux security modules (LSM) are software components that use a well-defined kernel interface to control and decline certain operations. In particular, LSMs providing mandatory access control (MAC) define rules that further restrict what files a process can access. Two well-known LSM MACs are AppArmor and SELinux. These MACs define policy rules about what a process can and cannot access. The resulting policies are then enforced by the kernel. Thus, adversaries are on the one side further limited on the resources that are exploitable. On the other hand, they have to invest additional time and resources to circumvent and disable the LSMs.

So far, these security mechanisms mostly protect the host from containers. If a container is compromised, an adversary still has to put in the additional effort to compromise the host. However, these protections may not circumvent exploits across containers on the same host. For example, containers on the Docker engine share a common user namespace and storage space for the container images. Thus, an adversary escaping one container may have access to the container images of another container. This can be used to manipulate images and introduce persistent threats or steal information. One safeguard against these cross-container exploitations are extended features of LSM MACs known as multi category security. Using MCS, every container gets a unique identity when it is initialized. Based on this unique identity, the kernel can perform more fine-grained access decisions because two process executing the same binary that would usually have the same policy are now distinguishable.

| - -| | | -|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | As a result, access to container specific resources can be restrict for each container. | -| REC-ISO-BP-7 | It is important to secure remote access to the host and containers themselves. While not going into the details of full network security in a cloud environment, each container and host must be protected as part of the security-in-depth approach. On Linux systems, netfilter/iptables and ebtables can be used to create packet firewalls. They limit network access to exposed ports on the host and in the containers. Similar to virtual switches in hypervisors, containers can be connected by a Linux bridge device. Platforms such as Docker use a default bridge device for all containers if no separate network is specified during container initiation. As a result, containers may share a common network segment, which can be exploited. Therefore, ebtables is recommended as an additional firewall configured for the bridge device. | -| REC-ISO-BP-8 | Stronger isolation mechanisms to keep application code constrained within a VM/Container. Such solutions include the private cloud, physical separation.
For containers, many security solutions 16 are used for ensuring strong isolation of resources, such as LXC, LXD, Singularity, Docker (runc), Kata-containers (kata-runtime), and gVisor (runsc). | -| REC-ISO-BP-9 | Shared cache memory partitioning or isolation and assigning of a separate portion of cache memory to each VM can reduce or eliminate successful side channel attacks in a virtualized environment 17 . | - -This recommendation can help to mitigate: T-GEN-01, T-VM-C-01, T-VM-C-02, T-VM-C-05, T-VL-01, T-HW-01 - -## 8.12 REC-AUD Security Audit - -**Recommendation:** Periodic audit and scan should be conducted of: - -- The integrity of images and VM/Containers used in O-Cloud deployments to ensure they have not been modified to include malicious software. -- Accounts and privileges for images repositories. -- All accounts, access lists and the privileges they have been granted to access O-Cloud components and images repositories. - -**Best practices to fulfill this recommendation:** - -| Req ID | Description | -|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-AUD-BP-1 | Scan code repositories for exposed credentials or other sensitive information. Preemptively search for files containing passwords or other credentials and take actions to reduce the exposure risk when found. | -| REC-AUD-BP-2 | Suspicious accounts/credentials should be investigated and removed. | -| REC-AUD-BP-3 | Routinely check account role permissions to ensure only expected users and roles have permission to modify cloud firewalls, to modify cloud compute infrastructure components, create snapshots and backups, and to create/delete new instances. | - -This recommendation can help to mitigate: T-GEN-01, T-GEN-02, T-VM-C-05, T-IMG-01, T-IMG-03, T-IMG-04, T-ADMIN-01, T-ADMIN-02 - -16 Olivier Flauzac, Fabien Mauhourat, Florent Nolot, A review of native container security for running applications, Procedia Computer Science, Volume 175, 2020, Pages 157-164, ISSN 1877-0509, . "A review of native container security for running applications" - -17 - -## 8.13 REC-SS Secure Storage - -**Recommendation:** The O-Cloud infrastructure should support encrypted storage, for example, block, object, file storage, credentials, and secrets with access to encryption keys restricted based on a need to know. - -**Best practices to fulfill this recommendation:** - -| Req ID | Description | -|-------------|------------------------------------------------------------------------------------------------------------------------------------------| -| REC-SS-BP-1 | Controlled Access Based on the Need to Know should be implemented 18 . | -| REC-SS-BP-2 | When possible, store keys on separate cryptographic hardware (e.g. HSM, TPM) instead of on the local system. | -| REC-SS-BP-3 | Use best practices for authentication protocols, such as OAuth 2.0, and ensure traffic that may contain credentials is protected by TLS. | -| REC-SS-BP-4 | Set up monitoring to track access to cache data and identify any unauthorized access attempts. | -| REC-SS-BP-5 | Establish policies for cache data lifecycle, including how long data should be retained in cache and when it should be purged. | - -**This recommendation can help to mitigate:** T-GEN-06, T-VM-C-01, T-VM-C-02, T-VM-C-03, T-VM-C-06, T-IMG-03, T-IMG-03, T-VL-01, T-OCAPI-01, T-HW-01 - -## 8.14 REC-PHY Physical Security Protection - -**Recommendation:** Physical security protection measures should be considered to deny unauthorized access to O-Cloud facilities, equipment and resources. - -**Best practices to fulfill this recommendation:** - -| Req ID | Description | -|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-PHY-BP-1 | Reduce the hardware platform (computing platform based for example on the x86 hardware architecture (32bit or 64bit), similar servers) attack surface by removing unneeded interfaces.
Example: Wireless interfaces (e.g., WiFi, 4G), if present, should remain optional for the platform REC-PHY-BP-1 [i.41]. | -| REC-PHY-BP-2 | Enforce protection of the main memory against untrusted peripherals.
Example: The hardware platform exposes an input/output memory management unit, such as VT-x (Intel) or AMD-V (AMD). This feature needs to be enabled by default and can only be disabled by the owner of the hardware platform (not the user) [i.41]. | -| REC-PHY-BP-3 | Ensure the security hardware component quality.
Example: In case the platform embeds a TPM, the latter is certified (e.g. from a Common Criteria perspective according to the Protection Profile TCG Protection Profile PC Client Specific TPM Family 2.0) [i.41].
Only the owner of the hardware platform (not the user) can enable and disable the TPM. | -| REC-PHY-BP-4 | Ensure the hardening of the platform against persistent compromises.
Example: hardware platform firmwares are expected to ensure their integrity by means of state-of-the-art security mechanisms. This notably includes protecting integrity of the code and data stored | - -18 - -| | | -|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | on the Flash Memory. The modification of firmware code should only be the result of a legitimate, signed update using robust cryptographic protocols. The installation of a signed update older than the version currently installed on the hardware platform shall be considered illegitimate by default. However, for the latter case, the firmware configuration interface shall allow the platform owner to disable this protection. | -| REC-PHY-BP-5 |

Ensure the presence of minimal security features within the firmware (Low-level software components shipped with the hardware platform, including UEFI and legacy BIOSes or hardware components embedded software).

Example: The firmware configuration interface provides the following features [i.41]:

  • • Protecting the access to the firmware configuration interface thanks to a dedicated password
  • • Locking the boot sequence of the platform thanks to a dedicated password
  • • Enabling and disabling input/output interfaces (e.g. USB)
  • • Configuring the boot order (the ordering of the list of devices checked by the BIOS to boot an operating system)
  • • Replacing default Secure Boot keys with custom keys generated by the owner
| -| REC-PHY-BP-6 |

Allow for inspecting and auditing firmware code.

Example: Mechanisms which prevent firmware code inspection shall be absent or disabled by default.

| -| REC-PHY-BP-7 | Data centre physical security protections based on its location and such risk assessments, to determinate the structures, and data centre support systems (sensors, video camera, alarms to a Security Operation Centre...) | -| REC-PHY-BP-8 | Backup system in other area if needed. | -| REC-PHY-BP-9 | Enforcing Multi-Factor Authentication for privileged users could be a mitigation. | -| REC-PHY-BP-10 | Server cabinets fitted with an electronic lock. | -| REC-PHY-BP-11 | Physical Access Control based system with video and entry logs system. | -| REC-PHY-BP-12 | Sensors on the room or the cabinet to generate alarms to the Network / Security Operation Centre. | -| REC-PHY-BP-13 | Limited number of physical interfaces on the on-board NIC of the server and remotely control NIC. | -| REC-PHY-BP-14 | Secure All Endpoints (terminal, physical connectivity...). | -| REC-PHY-BP-15 | Zero trust architecture with security layers including physical access and redundancies, with regular security audit if needed. | - -**This recommendation can help to mitigate:** T-VM-C-03, T-VM-C-05, T-VL-02, T-OCAPI-01, T-HW-01, T-HW-02 - -## 8.15 REC-RA Remote Attestation - -**Recommendation:** A remote attestation (RA) approach should be used to determine the trustworthiness of O-Cloud components. It is a defensive measure that addresses the malicious software execution. In O-Cloud it is obvious the need for applying procedures to verify the integrity of the whole O-Cloud service deployment by the appropriate attestation of the O-Cloud architectural elements, including software and firmware images and associated supporting security sub-systems that will run to instantiate individual VNFs/CNFs and their composition into a O-Cloud service. - -The remote attestation requires identifying the root(s) of trust, establishing a chain of trust for the O-Cloud infrastructure, the VL, VNFs/CNFs, and the NFO/FOCOM sub-systems, and verification of the trust chain, so the NFO/FOCOM components can verifiably establish a sufficient level of assurance in the different software elements constituting the VNFs/CNFs and the service(s) that use them. - -The remote attestation (RA) capabilities should be used to realize trust establishment in the following use case scenarios: - -1. Measurement of VM/Container during launch. -2. Protected VM/Container launch on a trusted O-Cloud platform -3. Measurement of VM/Container during launch and while in use -4. Remote attestation of secret storage -5. Secure VM/Container migration between two trusted O-Cloud platform - -### **Best practices to fulfill this recommendation:** - -| Req ID | Description | -|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-RA-BP-1 | ETSI GR NFV-SEC 018 [i.13], [i.14], ETSI GR NFV-SEC 007 [i.15] could be used as a security guidance of the remote attestation (RA) approach. | -| REC-RA-BP-2 | All servers part of O-Cloud infrastructure should support measured boot and an attestation server that monitors the measurements of the servers. | - -**Example:** Operators might use RA to assess if the overall O-Cloud infrastructure is trustworthy, datacenters might use RA to assess trustworthiness of subsystems they use, and management entities might use RA to assess the trustworthiness of individual infrastructural components. Hence, there are numerous use-cases and scenarios that might be considered where attestation is a fundamental step of creating an overall trustworthy system. - -A trustworthy element is the entity which has a component that provides a unique identifier, certification (e.g. through cryptographic signing) and which is able to store measurements and data about the state of that element (including related sub-elements or dependent elements if necessary) in a tamperproof and verifiable form. For example, the TPM2.0 quoting mechanism using the TPMS\_ATTEST data structure is an example of this. - -**This recommendation can help to mitigate:** T-GEN-03, T-VM-C-04, T-IMG-04, T-VL-02 - -## 8.16 REC-SDD Secure data deletion - -**Recommendation:** The O-Cloud platform should delete cryptographic keys and sensitive data using a secure deletion method from both active and backup storage systems. - -### **Best practices to fulfill this recommendation:** - -| BP ID | Description | -|--------------|-----------------------------------------------------------------------------------------------------------------| -| REC-SDD-BP-1 | Review the CSP's policies and SLAs on data deletion to ensure it has a procedure that effectively deletes data. | - -| | | -|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-SDD-BP-2 | Secure overwriting is way to overwrite on existing data to be deleted by new data, replaced with zero or random. | -| REC-SDD-BP-3 | Cryptography method to encrypt the data before storing to the cloud storage. In order to delete the data, the encryption key is being destroyed. This makes the data unrecoverable. | -| REC-SDD-BP-4 | Each data center adheres to a strict disposal policy and uses the techniques described to achieve compliance with NIST SP 800-88 Revision 1 “Guidelines for Media Sanitization” [i.48] and DoD 5220.22-M “National Industrial Security Program Operating Manual.” [i.49]. | -| REC-SDD-BP-5 | Physically destroy media that cannot be sanitized by either crush and deform the drive or shred the drive into small pieces. | -| REC-SDD-BP-6 | Limit access to data backups (through use of roles) to know who has access to the data. | -| REC-SDD-BP-7 | Enable application deployment using a security policy where volumes containing sensitive data mounted by the O-Cloud infrastructure to the application, are unmounted after application initialization guard timer, or based on application state monitoring. | -| REC-SDD-BP-8 | Enable applications to delete application sensitive data from their memory / filesystems based on a trigger from O-Cloud infrastructure. | -| REC-SDD-BP-9 | Enable RASP modules to notify applications to delete application sensitive data from their memory / filesystems based on a trigger from O-Cloud infrastructure. | - -This recommendation can help to mitigate: T-GEN-05, T-GEN-06, T-VM-C-03 - -## 8.17 REC-IDM O-Cloud ID secure management - -**Recommendation:** To counter threats associated with ID reuse, mismanagement, and redundancy, the O-Cloud should employ robust strategies for ID generation, validation, and lifecycle management. Properly managed IDs reduce risks of data inconsistencies, unauthorized access, and operational inefficiencies. - -**Best practices to fulfil this recommendation:** - -| BP ID | Description | -|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-IDM-BP-01 | Adopt the UUID generation method in line with RFC 4122 standards within the O-Cloud system. Ensure each newly created object, whether Containers, Pods, Nodes, or Services, is assigned a unique UUID upon its instantiation. Utilize reputable UUID generation libraries or modules to ensure adherence to the standard. | -| REC-IDM-BP-02 | Implement validation mechanisms ensuring each ID's uniqueness during assignment. | -| REC-IDM-BP-03 | Use database-level constraints to ensure ID uniqueness across the O-Cloud. | -| REC-IDM-BP-04 | Monitor the lifecycle of each ID, providing a clear history of its assignment and usage. | -| REC-IDM-BP-05 | Implement automated processes to detect and remove defunct node objects. | -| REC-IDM-BP-06 | Audit node resources before ID assignment and raise alerts on mismatches. | -| REC-IDM-BP-07 | Use configuration management tools to maintain node consistency. | -| REC-IDM-BP-08 | Employ dynamic IP management systems to ensure consistent IP assignments. | -| REC-IDM-BP-09 | Ensure monitoring tools can differentiate between data from old and new IDs. | - -| | | -|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-IDM-BP-10 | Notify users/systems when an ID is reused, alerting them of potential ambiguities. | -| REC-IDM-BP-11 | Centralize logging systems with distinct identifiers for each ID. | -| REC-IDM-BP-12 | Regularly update and audit RBAC policies to ensure they reflect current ID assignments. | -| REC-IDM-BP-13 | Before reusing any ID, ensure that the lifecycle of the previous object associated with that ID has been completely terminated. | -| REC-IDM-BP-14 | For any ID that's about to be reused, conduct thorough data cleaning processes to remove all residual data and configurations associated with its predecessor. | - -This recommendation can help to mitigate: T-O-CLOUD-ID-01, T-O-CLOUD-ID-02, T-O-CLOUD-ID-03 - -## 8.18 REC-IDM Identity management for O-Cloud elements - -O-RAN Applications hosted on O-Cloud, Services provided by O-Cloud and O-Cloud Nodes use an identity, such as an identifier in an X.509 certificate, for authentication and authorization. To establish consistent and standardized identities throughout O-Cloud, it is essential to implement a uniform identity provider. - -The incorporation of an Identity Provider framework ensures uniform identity management that provides strong attested identities, through a combination of diverse attestation mechanisms, for the various elements in O-cloud environment and addresses the threats of Identity spoofing, unauthorized access, inadequate verification of the trustworthiness of entities. - -**Recommendation:** SPIRE and SPIFFE are CNCF graduated projects that effectively act as an identity provider for workloads and has been specified in **NIST SP 800-207A** [i.58] which mentions that “service identity should not be subjected to spoofing and should be continuously verifiable. An example of workload identity is a SPIFFE ID which is encoded as a Uniform Resource Identifier (URI) and carried in a cryptographically verifiable document called a SPIFFE Verifiable Identity Document (SVID)”. - -SPIFFE provides a structured ID format for applications in [RFC 3986](#) URI format. The SPIFFE ID adheres to **NIST SP 800-207A** (Zero Trust Architecture Model for Access Control in Cloud-Native Applications) as mentioned above. - -**SPIFFE Runtime Environment (SPIRE)**, a production-ready implementation of SPIFFE APIs use **Node** and **workload attestation** to securely issue **SVID** [X.509 certificate with SPIFFE ID][i.55] to Applications which can be used for service-service communication. - -In O-Cloud, services and workloads can be dynamically scaled up, down and scheduled, SPIRE provides a **secure way to verify the identity** of these dynamically changing entities, ensuring that services can **trust** one another in such environments. - -**SPIFFE and SPIRE**, as a part of O-Cloud Infrastructure enable services and applications to obtain identity (SPIFFE ID [i.57]) and SVID [X.509 certificate with SPIFFE ID] using attestation policies. - -![SPIRE Architecture in O-Cloud diagram showing O-Cloud infrastructure with SPIRE Server, SPIRE Agents on Node-1 and Node-2, Workloads, and PKI integration.](778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg) - -The diagram illustrates the SPIRE architecture within the O-Cloud. At the top, the 'O-Cloud infrastructure' contains a 'SPIRE Server' with 'Registration API' and 'Node API'. The 'Node API' connects to a 'PKI' (Public Key Infrastructure) block. Below the server, two nodes, 'Node-1' and 'Node-2', each contain a 'SPIRE Agent' with a 'Workload API'. The 'SPIRE Server' connects to the 'SPIRE Agent' on each node. Each 'SPIRE Agent' connects to two 'Workload' blocks. Each 'Workload' block connects to an 'SVID Trust Bundle' block. A legend at the bottom shows two yellow rectangles with arrows pointing to the text 'SPIRE Components'. - -SPIRE Architecture in O-Cloud diagram showing O-Cloud infrastructure with SPIRE Server, SPIRE Agents on Node-1 and Node-2, Workloads, and PKI integration. - -Fig 8.18-1: SPIRE Architecture in O-Cloud - -**SPIRE Architecture:** A SPIRE deployment is composed of one or more **SPIRE Servers** and one or more **SPIRE Agents**. - -**SPIRE Server:** A SPIRE Server is responsible for **managing and issuing all identities** in its configured SPIFFE trust domain. It stores registration entries [i.54] (which specify the selectors that determine the conditions under which a particular SPIFFE ID should be issued) and signing keys, uses node attestation [i.54] to authenticate agents' identities automatically, and creates SVIDs for workloads when requested by an authenticated agent. - -**SPIRE Agents:** A SPIRE Agent runs on every O-Cloud node on which an identified workload runs. The agent performs the following tasks: - -- Requests SVIDs from SPIRE server and caches them until a workload requests its SVID. -- Exposes the SPIFFE Workload API to workloads on node and attests the identity of workloads that call it. -- Provides SVIDs to the identified workloads. - -### **Best practices to fulfil this recommendation:** - -| BP ID | Description | -|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-IDM-SPR-01 | Adopt a uniform standardized identity that follow the URI specification as defined by RFC 3986 for all elements within the O-Cloud.

spiffe://domain/clusterName/namespace/WL-identity | -| REC-IDM-SPR-02 | The SPIFFE Verifiable Identity Document (SVID) is cryptographically verifiable document can be issued either by SPIRE server locally or through an external Certificate Authority. | - -| | | -|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| REC-IDM-SPR-03 | Agent and server architecture model as defined in SPIFFE and SPIRE Concepts [i.54] to be implemented in O-Cloud platform. | -| REC-IDM-SPR-04 | O-Cloud exposes the SPIRE APIs through which identity may be retrieved and/or issued to Applications or services. | -| REC-IDM-SPR-05 |

Registration entries maps an identity -- in the form of a SPIFFE ID -- to a set of properties known as selectors that the workload must possess to be issued a particular identity.

For SPIRE to identify an O-Cloud element, it is essential to register the O-Cloud elements with the SPIRE Server, via registration entries.

SMO can use the O2ims interface to push the registration entries for O-Cloud Nodes, Network Functions to the SPIRE server present as part of the O-Cloud platform.

| -| REC-IDM-SPR-06 |

Attestation Policies are enforced for asserting the identity of O-Cloud elements by gathering attributes and comparing them to a set of selectors defined in the Registration entries.

Node Attestation [i.56] ensures agent authenticate and verify itself when it first connects to a server.

Workload Attestation verifies the identity of the elements by querying information about the process from the node and comparing it with the selectors provided in the Registration entries.

| -| REC-IDM-SPR-07 | SPIRE server as part of O-Cloud platform does issuance of SVID and required trust bundle to O-Cloud elements after successful assertion. | - -This recommendation can help to mitigate: T-O-CLOUD-ID-01, T-O-CLOUD-ID-03 - -## 8.19 REC-ADMC Admission Control - -Admission Control, within the framework of O-Cloud, operates as a customizable and adaptable security layer. It intercepts API requests after they are authenticated and authorized but before they are executed. It evaluates and decides on the admission of requests to perform specific actions, such as deploying a software image, creating or updating Pods, managing resources, and setting up network policies. - -Some of the configurable security policies include: - -- Vulnerability scanning: The Admission Control incorporates a robust vulnerability scanning process. This process is integral to identifying and assessing any known security vulnerabilities within a software image. It ensures that only those images that meet the set vulnerability thresholds, indicating a minimized risk of security threats, are approved for deployment. The activation of this scanning feature can be adjusted according to the specific needs and security requirements of different scenarios. -- Image signature verification: In addition to vulnerability scanning, the Admission Control also includes the critical step of verifying the digital signature of software images. This verification process is essential for confirming the authenticity and integrity of the image. It guarantees that the image originates from a trusted source and remains unaltered. The enforcement of this verification can be tailored based on the operational context and the level of security needed. -- Resource quotas: The Admission Control enforces and sets constraints on the total amount of resources (CPU, memory, storage) that can be consumed by pods within a namespace. This prevents any single application or user from monopolising cluster resources, which can be a security concern in multi-tenant environments. -- Limit range: The Admission Control enforces and sets default and limit constraints on the resources that can be requested and consumed by individual containers or VMs within a particular namespace. This prevents any single container or VM from consuming excessive resources in a particular namespace. -- Pod security policies: The Admission Control defines a set of conditions that a pod must meet before it is accepted into the system. These policies can enforce the use of non-privileged containers, restrict volume types, and require the use of read-only root file systems, all of which enhance security. -- Immutable containers: The Admission Control enforces policies that prevent changes to running containers, ensuring that the containers remain in their original, secure state as defined at deployment. - -- API rate limiting: To prevent abuse and potential denial-of-service attacks, The Admission Control can enforce rate limiting on API requests. This ensures that the API server remains stable and responsive, even under high load or during an attack. - -In Kubernetes, the Admission Control is an integral component that significantly enhance the cluster's security and operational integrity. It can be implemented as a plugin that can either modify or reject requests to the Kubernetes API, ensuring compliance with defined security and operational policies. Examples of a such Admission Control include: - -- Kubernetes Pod Security Admission: Admission Controller provided by Kubernetes itself. It focuses on enforcing security-related best practices for Pods. -- 3rd party admission plugins: such as OPA. Open Policy Agent (OPA) is a popular third-party admission controller. It extends the functionality of Kubernetes admission control by allowing more complex and customized policy enforcement. OPA uses a declarative language called Rego to define policies that specify the desired state and behaviour of the cluster resources. For example, OPA can be used to require that all container images come from a trusted registry. - -In the O-Cloud context, the decision hinges on achieving a delicate balance: on one hand, there's the need for simplicity and seamless integration, which is a strong point of Kubernetes native controllers. On the other hand, there's a demand for advanced, customizable policy management, where OPA excels. Throughout this balancing act, it is crucial to maintain high standards of security and optimal performance, ensuring these implementations are effectively aligned with the broader O-RAN system. Opting for a combination approach might provide the most flexibility, catering to these diverse requirements. This strategy enables the adaptation to varying operational scenarios within O-RAN, each with its own unique set of needs, whether they pertain to security, efficiency, scalability, or compliance. - -**This recommendation can help to mitigate:** T-VM-C-01, T-IMG-01, T-VL-03 - -# --- 9 Risk Assessment - -The risk assessment of the identified threats against O-Cloud is provided in the O-RAN Security Threat Modeling and Risk Assessment [i.50]. - -# Annex A (informative): Best practices from some of existing main security guidance - -Operators, O-Cloud vendors and Cloud providers should ensure that O-Cloud components and interfaces are secure under very strict set of security best practices. Such security guidance include: - -- A.1 CISA/NSA Kubernetes security hardening best practices [i.3] -- A.2 CIS Docker security best practices [i.18] -- A.3 ONAP VNFs security best practices [i.24] - -## A.1 CISA/NSA Kubernetes security hardening best practices - -This clause summarizes recommendations and best practices from the CISA/NSA Kubernetes Hardening Guidance. The report details recommendations to harden Kubernetes systems. Primary actions include the scanning of containers and Pods for vulnerabilities or misconfigurations, running containers and Pods with the least privileges possible, and using network separation, firewalls, strong authentication, and log auditing. To ensure the security of applications, system administrators should keep up to date with patches, updates, and upgrades to minimize risk. NSA and CISA also recommend periodic reviews of Kubernetes settings and vulnerability scans to ensure appropriate risks are accounted for and security patches are applied. - -Download the full Kubernetes Hardening Guidance: [https://media.defense.gov/2022/Aug/29/2003066362/-1-/1/0/CTR\\_KUBERNETES\\_HARDENING\\_GUIDANCE\\_1.2\\_20220829.PDF](https://media.defense.gov/2022/Aug/29/2003066362/-1-/1/0/CTR_KUBERNETES_HARDENING_GUIDANCE_1.2_20220829.PDF) - -### Kubernetes Pod security - -Pods are the smallest deployable Kubernetes unit and consist of one or more containers. Pods are often a cyber actor's initial execution environment upon exploiting a container. For this reason, Pods should be hardened to make exploitation more difficult and to limit the impact of a successful compromise. - -**“Non-root” containers:** Preventing root execution by using non-root containers limits the impact of a container compromise. container engines allow containers to run applications as a non-root user with non-root group membership. Typically, this non-default setting is configured when the container image is built. Having non-root execution integrated at build time provides better assurance that applications will function correctly without root privileges. (See Appendix A in [i.3]). - -**Immutable container file systems:** By default, containers are permitted mostly unrestricted execution within their own context. A cyber actor who has gained execution in a container can create files, download scripts, and modify the application within the container. Kubernetes can lock down a container's file system, thereby preventing many post-exploitation activities. However, these limitations also affect legitimate container applications and can potentially result in crashes or anomalous behavior. To prevent damaging legitimate applications, Kubernetes administrators can mount secondary read/write file systems for specific directories where applications require write access. (See Appendix B in [i.3]). - -**Building secure container images:** Container images are usually created by either building a container from scratch or by building on top of an existing image pulled from a repository. In addition to using trusted repositories to build containers, image scanning is key to ensuring deployed containers are secure. Throughout the container build workflow, images should be scanned to identify outdated libraries, known vulnerabilities, or misconfigurations, such as insecure ports or permissions. One approach to implementing image scanning is by using an admission controller [i.3]. This admission controller could block deployments if the image doesn't comply with the organization's security policies defined in the webhook configuration19. - -**Hardening container engines:** Some platforms and container engines provide additional options to harden the containerized environments. A powerful example is the use of hypervisors to provide container isolation. Hypervisors rely on hardware to enforce the virtualization boundary rather than the operating system. Hypervisor isolation is more secure than traditional container isolation. Container engines running on the Windows operating system can be - -19 The Linux Foundation, "11 Ways (Not) to Get Hacked," 18 07 2018 . - -configured to use the built-in Windows hypervisor, Hyper-V, to enhance security. Additionally, some security focused container engines natively deploy each container within a lightweight hypervisor for defense-in-depth. Hypervisor-backed containers mitigate container breakouts. - -### **Network separation and hardening** - -Cluster networking is a central concept of Kubernetes. Communication between containers, Pods, services, and external services must be taken into consideration. Resource separation and encryption can be an effective way to limit a cyber actor's movement and escalation within a cluster. - -***Namespaces:*** Kubernetes namespaces are one way to partition cluster resources among multiple individuals, teams, or applications within the same cluster (See Appendix E [i.3] for more details). - -***Network policies:*** Network policies control traffic flow between Pods, namespaces, and external IP addresses. By default, no network policies are applied to Pods or namespaces, resulting in unrestricted ingress and egress traffic within the Pod network. Pods become isolated through a network policy that applies to the Pod or the Pod's namespace. Once a Pod is selected in a network policy, it rejects any connections that are not specifically allowed by any applicable policy object. (See Appendix F in [i.3] for more details). - -***Resource policies:*** In addition to network policies, LimitRange and ResourceQuota are two policies that can limit resource usage for namespaces or nodes. A LimitRange policy constrains individual resources per Pod or container within a particular namespace, e.g., by enforcing maximum compute and storage resources. ResourceQuotas are restrictions placed on the aggregate resource usage for an entire namespace, such as limits placed on total CPU and memory usage. If a user tries to create a Pod that violates a LimitRange or ResourceQuota policy, the Pod creation fails. (See Appendixes G and H in [i.3] for more details). - -***Control plane hardening:*** The control plane is the core of Kubernetes and gives users the ability to view containers, schedule new Pods, read Secrets, and execute commands in the cluster. Because of these sensitive capabilities, the control plane should be highly protected. In addition to secure configurations such as TLS encryption, RBAC, and a strong authentication method, network separation can help prevent unauthorized users from accessing the control plane. The Kubernetes API server should be protected (e.g. by firewall, TLS encryption) and not be exposed to the Internet or an untrusted network. - -***Worker node segmentation:*** A worker node can be a virtual or physical machine, depending on the cluster's implementation. Because nodes run the microservices and host the web applications for the cluster, they are often the target of exploits. If a node becomes compromised, an administrator should proactively limit the attack surface by separating the worker nodes from other network segments that do not need to communicate with the worker nodes or Kubernetes services. A firewall can be used to separate internal network segments from the external facing worker nodes or the entire Kubernetes service depending on the network. Examples of services that may need to be separated from the possible attack surface of the worker nodes are confidential databases or internal services that would not need to be internet accessible. - -***Encryption:*** Administrators should configure all traffic in the Kubernetes cluster—including between components, nodes, and the control plane—to use TLS 1.2 or 1.3 encryption. Encryption can be set up during installation or afterward using TLS bootstrapping, detailed in the Kubernetes documentation20, to create and distribute certificates to nodes. For all methods, certificates must be distributed amongst nodes to communicate securely. - -***Secrets:*** Kubernetes Secrets maintain sensitive information, such as passwords, OAuth tokens, SSH and TLS keys. Secrets can be encrypted by configuring data-at-rest encryption on the API server or by using an external Key Management Service (KMS), which may be available through a cloud provider. (See Appendixes I and J in [i.3] for more details). - -***Protecting sensitive cloud infrastructure:*** Kubernetes is often deployed on virtual machines in a cloud environment. As such, administrators should carefully consider the attack surface of the virtual machines on which the Kubernetes worker nodes are running. In many cases, Pods running on these virtual machines have access to sensitive cloud metadata services on a non-routable address. These metadata services provide cyber actors with information about the cloud infrastructure and possibly even short-lived credentials for cloud resources. Cyber actors abuse these metadata services for privilege escalation. Kubernetes administrators should prevent Pods from accessing cloud metadata services - ---- - -20 - -by using network policies or through the cloud configuration policy. Because these services vary based on the cloud provider, administrators should follow vendor guidance to harden these access vectors. - -### Authentication and authorization - -Authentication and authorization are the primary mechanisms to restrict access to cluster resources. Cyber actors can scan for well-known Kubernetes ports and access the cluster's database or make API calls without being authenticated if the cluster is misconfigured. User authentication is not a built-in feature of Kubernetes. However, several methods exist for administrators to add authentication to a cluster. - -**Authentication:** Kubernetes clusters have two types of users: service accounts and normal user accounts. Service accounts handle API requests on behalf of Pods. Authentication is typically managed automatically by Kubernetes through the ServiceAccount Admission Controller using bearer tokens. The bearer tokens are mounted into Pods at well-known locations and can be used from outside the cluster if the tokens are left unsecured. Because of this, access to Pod Secrets should be restricted to those with a need to view them using Kubernetes RBAC. For normal users and admin accounts, there is no automatic authentication method for users. Administrators must add an authentication method to the cluster to implement authentication and authorization mechanisms. The Kubernetes documentation21 lists several ways to implement user authentication including client certificates, bearer tokens, authentication plugins, and other authentication protocols. At least one user authentication method should be implemented. Administrators should not use weak methods such as static password files. Weak authentication methods could allow cyber actors to authenticate as legitimate users. - -**Role-based access control:** RBAC is one method to control access to cluster resources based on the roles of individuals within an organization. RBAC is enabled by default in Kubernetes version 1.6 and newer. Privileges assigned to users, groups, and service accounts should follow the principle of least privilege, giving only required permissions to resources. Users or user groups can be limited to particular namespaces where required resources reside. By default, a service account is created for each namespace for Pods to access the Kubernetes API. RBAC policies can be used to specify allowed actions from the service accounts in each namespace. Access to the Kubernetes API is limited by creating an RBAC Role or ClusterRole with the appropriate API request verb and desired resource on which the action can be applied. Tools exist that can help audit RBAC policies by printing users, groups, and service accounts with their associated assigned Roles and ClusterRoles. (See Appendixes K and L in [i.3] for more details). - -### Log auditing - -Logs capture activity in the cluster. Auditing logs is necessary, not only for ensuring that services are operating and configured as intended, but also for ensuring the security of the system. Systematic audit requirements mandate consistent and thorough checks of security settings to help identify compromises. Kubernetes is capable of capturing audit logs for cluster actions and monitoring basic CPU and memory usage information; however, it does not natively provide in-depth monitoring or alerting services. - -**Logging:** System administrators running applications within Kubernetes should establish an effective logging, monitoring, and alerting system for their environment. Logging Kubernetes events alone is not enough to provide a full picture of the actions occurring on the system. Logging should also be performed at the host level, application level, and on the cloud if applicable. These logs can then be correlated with any external authentication and system logs as applicable to provide a full view of the actions taken throughout the environment for use by security auditors and incident responders. Within the Kubernetes environment, administrators should monitor/log the following: - -- API request history -- Performance metrics -- Deployments -- Resource consumption -- Operating system calls -- Protocols, permission changes - ---- - -21 - -- Network traffic -- Pod scaling - -When a Pod is created or updated, administrators should capture detailed logs of the network communications, response times, requests, resource consumption, and any other relevant metrics to establish a baseline. - -RBAC policy configurations should be audited periodically and whenever changes occur to the organization's system administrators. - -Audits of internal and external traffic logs should be conducted to ensure all intended security constraints on connections have been configured properly and are working as intended. - -Logs can be streamed to an external logging service to ensure availability to security professionals outside of the cluster, identify abnormalities as close to real time as possible, and protect logs from being deleted if a compromise occurs. If using this method, logs should be encrypted during transit with TLS 1.2 or 1.3 to ensure cyber actors cannot access the logs in transit and gain valuable information about the environment. (See Appendixes M and N in [i.3] for more details). - -**SIEM platforms:** Security Information and Event Management (SIEM) software collects logs from across an organization's network. SIEM software brings together firewall logs, application logs, and more; parsing them out to provide a centralized platform from which analysts can monitor system security. SIEM tools have variations in their capabilities. Generally, these platforms provide log collection, threat detection, and alerting capabilities. Some include machine learning capabilities, which can better predict system behavior and help to reduce false alerts. Organizations using these platforms in their environment can integrate them with Kubernetes to better monitor and secure clusters. Open-source platforms for managing logs from a Kubernetes environment exist as an alternative to SIEM platforms. - -**Alerting:** Kubernetes does not natively support alerting; however, several monitoring tools with alerting capabilities are compatible with Kubernetes. If Kubernetes administrators choose to configure an alerting tool to work within a Kubernetes environment, there are several metrics for which administrators should monitor and configure alerts. Examples of cases that could trigger alerts include but are not limited to: - -- Low disk space on any of the machines in the environment, -- Available storage space on a logging volume running low, -- External logging service going offline, -- A Pod or application running with root permissions, -- An anonymous account being used or gaining privileges, -- Unusual system calls or failed API calls, -- user/admin behavior that is abnormal (i.e. at unusual times or from an unusual location), and -- Significant deviations from the standard operation metrics baseline. - -**Service meshes:** Service meshes are platforms that streamline microservice communications within an application by allowing for the logic of these communications to be coded into the service mesh rather than within each microservice. Coding this communication logic into individual microservices is difficult to scale, difficult to debug as failures occur, and difficult to secure. Using a service mesh can simplify this for developers. The mesh can: - -- Redirect traffic when a service is down, -- Gather performance metrics for optimizing communications, -- Allow management of service-to-service communication encryption, -- Collect logs for service-to-service communication, -- Collect logs from each service, and -- Help developers diagnose problems and failures of microservices or communication mechanisms. - -**Fault tolerance:** Fault tolerance policies should be put in place to ensure logging service availability. One policy that can be put in place is to allow new logs to overwrite the oldest log files if absolutely necessary in the event of storage capacity being exceeded. If logs are being sent to an external service, a mechanism should be in place for logs to be stored locally if a communication loss or external service failure occurs. Once communication to the external service is restored, a policy should be in place for the locally stored logs to be pushed up to the external server. - -**Tools:** Kubernetes does not include extensive auditing capabilities. However, the system is built to be extensible, allowing users the freedom to develop their own custom solution or to choose an existing add-on that suits their needs. One of the most common solutions is to add additional audit backend services, which can use the information logged by Kubernetes and perform additional functions for users, such as extended search parameters, data mapping features, and alerting functionality. Organizations that already use SIEM platforms can integrate Kubernetes with these existing capabilities. Open-source monitoring tools—such as the Cloud Native Computing Foundation’s Prometheus, Grafana Labs’ Grafana, and Elasticsearch’s Elastic Stack (ELK)—are available to conduct event monitoring, run threat analytics, manage alerting, and collect resource isolation parameters, historical usage, and network statistics on running containers. Scanning tools can be useful when auditing the access control and permission configurations by assisting in identifying risky permission configurations in RBAC. NSA and CISA encourage organizations utilizing Intrusion Detection Systems (IDSs) on their existing environment to consider integrating that service into their Kubernetes environment as well. This integration would allow an organization to monitor for—and potentially kill containers showing signs of—unusual behavior so the containers can be restarted from the initial clean image. Many cloud service providers also provide container monitoring services for those wanting more managed and scalable solutions. - -### Upgrading and application security practices - -Security of applications running on Kubernetes orchestrated containers is an ongoing process, and it is vital to keep up with patches, updates, and upgrades. The specific software components vary depending on the individual configuration, but each piece of the overall system should be kept as secure as possible. This includes updating: Kubernetes, hypervisors, virtualization software, plugins, operating systems on which the environment is running, applications running on the servers, and any other software hosted in the Kubernetes environment. - -The Center for Internet Security (CIS) publishes benchmarks for securing software. Administrators should adhere to the CIS benchmarks for Kubernetes and any other relevant system components. Administrators should check periodically to ensure their system's security is compliant with the current security experts' consensus on best practices. Periodic vulnerability scans and penetration tests should be performed on the various system components to proactively look for insecure configurations and zero-day vulnerabilities. Any discoveries should be promptly remediated before potential cyber actors can discover and exploit them. - -As updates are deployed, administrators should also keep up with removing any old components that are no longer needed from the environment. Using a managed Kubernetes service can help to automate upgrades and patches for Kubernetes, operating systems, and networking protocols. However, administrators must still patch and upgrade their containerized applications. - -## A.2 CIS Docker security best practices - -CIS Benchmarks are universal security best practices developed by cybersecurity professionals and experts. Each CIS Benchmark provides guidelines for creating a secure system configuration. The following table summarizes recommendations from the CIS Docker Benchmark, specifying how to set up a safe docker configuration. - -Download the full CIS Docker Benchmark: - -### Host Configuration - -Create a separate partition for containers - -- Harden the container host -- Update your Docker software on a regular basis -- Manage Docker daemon access authorization wisely -- Configure your Docker files directories, and -- Audit all Docker daemon activity. - -### Docker Daemon Configuration - -- Restrict network traffic between default bridge containers and access to new privileges from containers. -- Enable user namespace support to provide additional, Docker client commands authorization, live restore, and default cgroup usage -- Disable legacy registry operations and Userland Proxy -- Avoid networking misconfiguration by allowing Docker to make changes to iptables, and avoid experimental features during production. -- Configure TLS authentication for Docker daemon and centralized and remote logging. -- Set the logging level to 'info', and set an appropriate default ulimit -- Don't use insecure registries and aufs storage drivers -- Apply base device size for containers and a daemon-wide custom SECCOMP profile to limit calls. - -### Container Images and Build File - -- Create a user for the container -- Ensure containers use only trusted images -- Ensure unnecessary packages are not installed in the container -- Include security patches during scans and rebuilding processes -- Enable content trust for Docker -- Add HEALTHCHECK instructions to the container image -- Remove setuid and setgid permissions from the images -- Use COPY instead of ADD in Dockerfile -- Install only verified packages -- Don't use update instructions in a single line or alone in the Dockerfile -- Don't store secrets in Dockerfiles - -### Container Runtime - -- Restrict containers from acquiring additional privileges and restrict Linux Kernel Capabilities. -- Enable AppArmor Profile. -- Avoid use of privileged containers during runtime, running ssh within containers, mapping privileged ports within containers. -- Ensure sensitive host system directories aren't mounted on containers, the container's root filesystem is mounted as read-only, the Docker socket is not mounted inside any containers. -- Set appropriate CPU priority for the container, set 'on-failure' container restart policy to '5', and open only necessary ports on the container. -- Apply per need SELinux security options, and overwrite the default ulimit at runtime. -- Don't share the host's network namespace and the host's process namespace, the host's IPC namespace, mount propagation mode, the host's UTS namespace, the host's user namespaces. -- Limit memory usage for container and bind incoming container traffic to a specific host interface. - -- Don't expose host devices directly to containers, don't disable the default SECCOMP profile, don't use docker exec commands with privileged and user option, and don't use Docker's default bridge docker0. -- Confirm cgroup usage and use PIDs cgroup limit, check container health at runtime, and always update docker commands with the latest version of the image. - -### Docker Security Operations - -- Avoid image sprawl and container sprawl. - -### Docker Swarm Configuration - -- Enable swarm mode only if needed -- Create a minimum number of manager nodes in a swarm -- Bind swarm services are bound to a specific host interface -- Encrypt containers data exchange on different overlay network nodes -- Manage secrets in a Swarm cluster with Docker's secret management commands -- Run swarm manager in auto-lock mode -- Rotate swarm manager auto-lock key periodically -- Rotate node and CA certificates as needed -- Separate management plane traffic from data plane traffic - -## A.3 ONAP VNFs security best practices - -ONAP provides details on the VNF general security requirements on various security areas such as user access control, network security, ACLs, infrastructure security, and vulnerability management. These requirements cover topics associated with compliance, security patching, logging/accounting, authentication, encryption, role-based access control, least privilege access/authorization. This clause summarizes requirements from ONAP, specifying how to integrate and operate VNFs within a robust security environment. - -For more details see the full documentation: - -### VNF General Security Requirements - -This clause provides details on the VNF general security requirements on various security areas such as user access control, network security, ACLs, infrastructure security, and vulnerability management. These requirements cover topics associated with compliance, security patching, logging/accounting, authentication, encryption, role-based access control, least privilege access/authorization. The following security requirements need to be met by the O-RAN NFs in a virtual environment: - -1. The VNF must implement and enforce the principle of least privilege on all protected interfaces. -2. The VNF must provide a mechanism (e.g., access control list) to permit and/or restrict access to services on the VNF by source, destination, protocol, and/or port. -3. The VNF should provide a mechanism that enables the operators to perform automated system configuration auditing at configurable time intervals. -4. The VNF provider must follow GSMA vendor practices and SEI CERT Coding Standards when developing the VNF in order to minimize the risk of vulnerabilities. See GSMA NESAS Network Equipment Security Assurance Scheme – Development and Lifecycle Security Requirements Version 1.0 () and SEI CERT Coding Standards (). - -5. The VNF must have all code (e.g., QCOW2) and configuration files (e.g., HEAT template, Ansible playbook, script) hardened, or with documented recommended configurations for hardening and interfaces that allow the Operator to harden the VNF. Actions taken to harden a system include disabling all unnecessary services, and changing default values such as default credentials and community strings. -6. The VNF should support the separation of (1) signaling and payload traffic (i.e., customer facing traffic), (2) operations, administration and management traffic, and (3) internal VNF traffic (i.e., east-west traffic such as storage access) using technologies such as VPN and VLAN. -7. The VNF Provider must have patches available for vulnerabilities in the VNF as soon as possible. Patching shall be controlled via change control process with vulnerabilities disclosed along with mitigation recommendations. -8. The VNF must support only encrypted access protocols, e.g., TLS 1.2/1.3. -9. The VNF must store authentication credentials used to authenticate to other systems encrypted except where there is a technical need to store the password unencrypted in which case it must be protected using other security techniques that include the use of file and directory permissions. Ideally, credentials should rely on a HW Root of Trust, such as a TPM or HSM. -10. VNFs that are subject to regulatory requirements must provide functionality that enables the Operator to comply with ETSI TC LI requirements, and, optionally, other relevant national equivalents. -11. The VNF must be able to authenticate and authorize all remote access. -12. The VNF must log any security event required by the VNF Requirements to Syslog using LOG\_AUTHPRIV for any event that would contain sensitive information and LOG\_AUTH for all other relevant events. -13. If SNMP is utilized, the VNF must support at least SNMPv3 with message authentication. -14. The VNF application processes should not run as root. If a VNF application process must run as root, the technical reason must be documented. -15. Login access (e.g., shell access) to the virtualization layer, whether interactive or as part of an automated process, must be through an encrypted protocol such as TLS 1.2/1.3. -16. The VNF must include a configuration (e.g. a template) that specifies the targeted parameters (e.g. a limited set of ports) over which the VNF will communicate; including internal, external and management communication. -17. Containerized components of VNFs should follow the recommendations for Container Base Images and Build File Configuration in the latest available version of the CIS Docker Community Edition Benchmarks to ensure that containerized VNFs are secure. All non-compliances with the benchmarks must be documented. -18. Containerized components of VNFs should execute in a Docker run-time environment that follows the Container Runtime Configuration in the latest available version of the CIS Docker Community Edition Benchmarks to ensure that containerized VNFs are secure. All non-compliances with the benchmarks must be documented. - -### **VNF Identity and Access Management Requirements** - -The following security requirements for logging, identity, and access management need to be met by the O-RAN NFs in a virtual environment: - -1. The VNF must, if not integrated with the Operator's Identity and Access Management system, support the creation of multiple IDs so that individual accountability can be supported. -2. The VNF must, if not integrated with the operator's IAM system, provide a mechanism for assigning roles and/or permissions to an identity. -3. The VNF must, if not integrated with the Operator's Identity and Access Management system, support multifactor authentication on all protected interfaces exposed by the VNF for use by human users. -4. The VNF must support account names that contain at least A-Z, a-z, and 0-9-character sets and be at least 6 characters in length. - -5. The VNF must, if not integrated with the Operator's Identity and Access Management system, comply with "password complexity" policy and support configurable password expiration. When passwords are used, they shall be complex and shall at least meet the following password construction requirements: (1) be a minimum configurable number of characters in length, (2) include 3 of the 4 following types of characters: upper-case alphabetic, lower-case alphabetic, numeric, and special, (3) not be the same as the UserID with which they are associated or other common strings as specified by the environment, (4) not contain repeating or sequential characters or numbers, (5) not to use special characters that may have command functions, and (6) new passwords must not contain sequences of three or more characters from the previous password. -6. The VNF must allow the Operator to restrict access to protected resources based on the assigned permissions associated with an ID in order to support Least Privilege (no more privilege than required to perform job functions). -7. The VNF must set the default settings for user access to deny authorization, except for a super user type of account. -8. The VNF must not store authentication credentials to itself in clear text or any reversible form and must use salting. -9. The VNF must, if not integrated with the Operator's Identity and Access Management system, support the ability to lock out the userID after a configurable number of consecutive unsuccessful authentication attempts using the same userID. The locking mechanism must be reversible by an administrator and should be reversible after a configurable time period. -10. The VNF must, if not integrated with the Operator's identity and access management system, authenticate all access to protected resources. -11. The VNF must support LDAP in order to integrate with an external identity and access management system. It MAY support other identity and access management protocols. -12. The VNF must not identify the reason for a failed authentication, only that the authentication failed. -13. The VNF must provide a means to explicitly logout, thus ending that session. -14. The VNF must provide explicit confirmation of a session termination such as a message, new page, or rerouting to a login page. -15. The VNF must, if not integrated with the Operator's Identity and Access Management system, enforce a configurable "terminate idle sessions" policy by terminating the session after a configurable period of inactivity. - -### **VNF API Security Requirements** - -This clause covers API security requirements when these are used by the VNFs. Key security areas covered in API security are Access Control, Authentication, Passwords, PKI Authentication Alarming, Anomaly Detection, Lawful Intercept, Monitoring and Logging, Input Validation, Cryptography, Business continuity, Biometric Authentication, Identification, Confidentiality and Integrity, and Denial of Service. - -The O-RAN NFs in a virtual environment needs to meet the following API security requirements: - -1. The VNF should integrate with the Operator's authentication and authorization services (e.g., IDAM). -2. The VNF must implement the following input validation control: Check the size (length) of all input. Do not permit an amount of input so great that it would cause the VNF to fail. Where the input may be a file, the VNF API must enforce a size limit. -3. The VNF must implement the following input validation controls: Do not permit input that contains content or characters inappropriate to the input expected by the design. Inappropriate input, such as SQL expressions, may cause the system to execute undesirable and unauthorized transactions against the database or allow other inappropriate access to the internal network (injection attacks). -4. The VNF must implement the following input validation control on APIs: Validate that any input file has a correct and valid Multipurpose Internet Mail Extensions (MIME) type. Input files should be tested for spoofed MIME types. - -### **VNF Security Analytics Requirements** - -This clause covers VNF security analytics requirements that are mostly applicable to security monitoring. The VNF Security Analytics cover the collection and analysis of data following key areas of security monitoring: - -- Anti-virus software -- Logging -- Data capture -- Tasking -- DPI -- API based monitoring -- Detection and notification -- Resource exhaustion detection -- Proactive and scalable monitoring -- Mobility and guest VNF monitoring -- Closed loop monitoring -- Interfaces to management and orchestration -- Malformed packet detections -- Service chaining -- Dynamic security control -- Dynamic load balancing -- Connection attempts to inactive ports (malicious port scanning) - -The following requirements of security monitoring need to be met by the O-RAN NFs in a virtual environment. - -1. The VNF must support Real-time detection and notification of security events. -2. The VNF must support API-based monitoring to take care of the scenarios where the control interfaces are not exposed or are optimized and proprietary in nature. -3. The VNF must support detection of malformed packets due to software misconfiguration or software vulnerability and generate an error to the syslog console facility. -4. The VNF must support proactive monitoring to detect and report the attacks on resources so that the VNFs and associated VMs can be isolated, such as detection techniques for resource exhaustion, namely OS resource attacks, CPU attacks, consumption of kernel memory, local storage attacks. -5. The VNF should operate with anti-virus software which produces alarms every time a virus is detected. -6. The VNF must protect all security audit logs (including API, OS and application-generated logs), security audit software, data, and associated documentation from modification, or unauthorized viewing, by standard OS access control mechanisms, by sending to a remote system, or by encryption. -7. The VNF must log successful and unsuccessful authentication attempts, e.g., authentication associated with a transaction, authentication to create a session, authentication to assume elevated privilege. -8. The VNF must log logoffs. -9. The VNF must log starting and stopping of security logging. - -10. The VNF must log success and unsuccessful creation, removal, or change to the inherent privilege level of users. -11. The VNF must log connections to the network listeners of the resource. -12. The VNF must log the field "event type" in the security audit logs. -13. The VNF must log the field "date/time" in the security audit logs. -14. The VNF must log the field "protocol" in the security audit logs. -15. The VNF must log the field "service or program used for access" in the security audit logs. -16. The VNF must log the field "success/failure" in the security audit logs. -17. The VNF must log the field "Login ID" in the security audit logs. -18. The VNF must not include an authentication credential, e.g., password, in the security audit logs, even if encrypted. -19. The VNF must detect when its security audit log storage medium is approaching capacity (configurable) and issue an alarm. -20. The VNF must support the capability of online storage of security audit logs. -21. The VNF must activate security alarms automatically when a configurable number of consecutive unsuccessful login attempts is reached. -22. The VNF must activate security alarms automatically when it detects the successful modification of a critical system or application file. -23. The VNF must activate security alarms automatically when it detects an unsuccessful attempt to gain permissions or assume the identity of another user. -24. The VNF must include the field "date" in the Security alarms (where applicable and technically feasible). -25. The VNF must include the field "time" in the Security alarms (where applicable and technically feasible). -26. The VNF must include the field "service or program used for access" in the Security alarms (where applicable and technically feasible). -27. The VNF must include the field "success/failure" in the Security alarms (where applicable and technically feasible). -28. The VNF must include the field "Login ID" in the Security alarms (where applicable and technically feasible). -29. The VNF must restrict changing the criticality level of a system security alarm to users with administrative privileges. -30. The VNF must monitor API invocation patterns to detect anomalous access patterns that may represent fraudulent access or other types of attacks or integrate with tools that implement anomaly and abuse detection. -31. The VNF must generate security audit logs that can be sent to Security Analytics Tools for analysis. -32. The VNF must log successful and unsuccessful access to VNF resources, including data. -33. The VNF must support the storage of security audit logs for a configurable period of time. -34. The VNF must have security logging for VNFs and their OSs be active from initialization. Audit logging includes automatic routines to maintain activity records and cleanup programs to ensure the integrity of the audit/logging systems. -35. The VNF must be implemented so that it is not vulnerable to OWASP Top 10 web application security risks. -36. The VNF must protect against all denial-of-service attacks, both volumetric and non-volumetric, or integrate with external denial of service protection tools. - -37. The VNF must be capable of automatically synchronizing the system clock daily with the Operator's trusted time source, to assure accurate time reporting in log files. It is recommended that Coordinated Universal Time (UTC) be used where possible, so as to eliminate ambiguity owing to daylight savings time. -38. The VNF must log the Source IP address in the security audit logs. -39. The VNF must have the capability to securely transmit the security logs and security events to a remote system before they are purged from the system. -40. The VNF should provide the capability of maintaining the integrity of its static files using a cryptographic method. -41. The VNF must log automated remote activities performed with elevated privileges. - -### **VNF Data Protection Requirements** - -This clause covers VNF data protection requirements that are mostly applicable to security monitoring. - -1. The VNF MUST provide the capability to restrict read and write access to data handled by the VNF. -2. The VNF MUST Provide the capability to encrypt data in transit on a physical or virtual network. -3. The VNF MUST provide the capability to encrypt data on non-volatile memory. Non-volatile memory is storage that is capable of retaining data without electrical power, e.g. Complementary metal-oxide-semiconductor (CMOS) or hard drives. -4. The VNF SHOULD disable the paging of the data requiring encryption, if possible, where the encryption of non-transient data is required on a device for which the operating system performs paging to virtual memory. If not possible to disable the paging of the data requiring encryption, the virtual memory should be encrypted. -5. The VNF MUST use NIST and industry standard cryptographic algorithms and standard modes of operations when implementing cryptography. -6. The VNF MUST NOT use compromised encryption algorithms. For example, SHA, DSS, MD5, SHA-1 and Skipjack algorithms. Acceptable algorithms can be found in the NIST FIPS publications () and in the NIST Special Publications (). -7. The VNF MUST use, whenever possible, standard implementations of security applications, protocols, and formats, e.g., S/MIME, TLS, SSH, IPSec, X.509 digital certificates for cryptographic implementations. These implementations must be purchased from reputable vendors or obtained from reputable open source communities and must not be developed in-house. -8. The VNF MUST provide the ability to migrate to newer versions of cryptographic algorithms and protocols with minimal impact. -9. The VNF MUST support digital certificates that comply with X.509 standards. -10. The VNF MUST NOT use keys generated or derived from predictable functions or values, e.g., values considered predictable include user identity information, time of day, stored/transmitted data. -11. The VNF MUST provide the capability of using X.509 certificates issued by an external Certificate Authority. -12. The VNF MUST be capable of protecting the confidentiality and integrity of data at rest and in transit from unauthorized access and modification. - -### **VNF Cryptography Requirements** - -This clause covers VNF cryptography requirements that are mostly applicable to encryption or protocol methods. - -1. The VNF SHOULD support an automated certificate management protocol such as CMPv2, Simple Certificate Enrollment Protocol (SCEP) or Automated Certificate Management Environment (ACME). -2. The VNF SHOULD provide the capability to integrate with an external encryption service. -3. The VNF MUST use symmetric keys of at least 112 bits in length. - -4. The VNF MUST use asymmetric keys of at least 2048 bits in length. -5. The VNF MUST provide the capability to configure encryption algorithms or devices so that they comply with the laws of the jurisdiction in which there are plans to use data encryption. -6. The VNF MUST provide the capability of allowing certificate renewal and revocation. -7. The VNF MUST provide the capability of testing the validity of a digital certificate by validating the CA signature on the certificate. -8. The VNF MUST provide the capability of testing the validity of a digital certificate by validating the date the certificate is being used is within the validity period for the certificate. -9. The VNF MUST provide the capability of testing the validity of a digital certificate by checking the Certificate Revocation List (CRL) for the certificates of that type to ensure that the certificate has not been revoked. -10. The VNF MUST provide the capability of testing the validity of a digital certificate by recognizing the identity represented by the certificate - the “distinguished name”. -11. The VNF MUST support HTTPS using TLS v1.2 or higher with strong cryptographic ciphers. -12. The VNF MUST support the use of X.509 certificates issued from any Certificate Authority (CA) that is compliant with RFC5280, e.g., a public CA such as DigiCert or Let’s Encrypt, or an RFC5280 compliant Operator CA. - -NOTE: The VNF provider cannot require the use of self-signed certificates in an Operator’s run time environment. - -# --- Annex: Change history/Change request (history) - -| Date | Revision | Description | -|------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2022.01.11 | V01.00.01 | Initial draft version for review | -| 2022.03.03 | V01.00.02 | Update according to notes from the WI core teams. This version addresses ORA-CR009, ORA-CR010, MTR-CR001, ORA.AO-CR011 | -| 2022.03.10 | V01.00.03 | Update according to notes from the WI core teams. This version addresses ALT-CR001 | -| 2022.03.24 | V01.00.04 | Update after spelling check | -| 2022.10.21 | V02.00.00 | Addition of:
  • Threats: T-GEN-05, T-VL-03, T-AAL-01, T-AAL-02
  • Recommendation: REC-SDD
| -| 2022.11.14 | V02.00.01 | Update according to the new O-RAN TR format | -| 2023.02.20 | V03.00.01 | Addition of:
  • AAL interfaces
  • Assets: A-OC-13 to A-OC-20
  • Threats: T-AAL-03 to T-AAL-06
| -| 2023.03.20 | V03.00.02 | Update after spelling check | -| 2023.07.05 | V04.00.01 | Integration of SYM CR 0003 | -| 2023.07.05 | V04.00.02 | References are updated to remove version numbers for O-RAN documents | -| 2023.10.16 | V05.00.01 | Integration of WG11 CR-0011 | -| 2023.10.19 | V05.00.02 | Editorial corrections in scope and references | -| 2023.10.26 | V05.00.03 | Editorial corrections in Clause 4.1 | -| 2024.02.19 | V06.00.01 | Additional of:
  • Threat: T-GEN-06
  • REC-IDM Identity management for O-Cloud elements
  • Critical service: O-Cloud Admission Control Services
| -| 2024.03.05 | V06.00.02 | Addressed editorial comments | -| 2024.03.25 | V06.00.03 | Addressed review comments | -| 2024.06.11 | V06.00.04 | Changes:
  • Definition of 'Sensitive'
  • O-Cloud Admission Control in 'Recommendations and best practices'
  • New definitions for certain terms
  • Alignment of O-Cloud assets with the Threat model
| -| 2024.06.20 | V06.00.05 | Changes:
  • Addition of references to definitions
  • Addition of O-Cloud inventory service details
  • Addition of time synchronization related threat
| -| 2024.07.17 | V06.00.06 | Changes:
  • Corrections to references
  • Correction to remove T-IMG-02 from Clause 8.19 to keep document consistency
  • Regeneration of table of contents
| -| 2024.07.22 | V06.00.07 | Changes:
  • Editorial (format) changes to the below
    • Title of clause 4.3.9
    • Renamed title of "revision history" (this table) as per template
    • Corrected alignment of title on first page
  • Regeneration of table of contents
| -| 2024.07.25 | V06.00.08 | Changes:
  • Editorial (format/typo) corrections

Published as version 07.00

| -| 2025.06.03 | V07.01 | Changes: The filename, copyright year are changed based on new TR template. | -| 2025.06.19 | V07.02 | Changes: Updated with definition of LimitRange and Kubernetes hardening references.

Published as version 08.00 | -| 2025.11.06 | V08.00.01 | Changes: Updated to adhere to new TR template, File name format changes for O-RAN document references and correction to references. | -| 2025.11.28 | V08.00.02 | Corrected reference to OWASP Container Security Verification Standard (i.17 in the references) | -| 2025.12.02 | V08.00.03 | Corrected the title font in the first page

Published as version 09.00 | \ No newline at end of file diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/01e00200a536673d6cd0e6d8705047a0_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/01e00200a536673d6cd0e6d8705047a0_img.jpg deleted file mode 100644 index 064c13049022756015afb42ae64b87b1ab3ef019..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/01e00200a536673d6cd0e6d8705047a0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8cfc7c367f26c3a8a8871c642268d28f5ede99be21ea178a0ad78931c93bcb6c -size 21990 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/08f6ace0c83e7394657fa372b47aec04_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/08f6ace0c83e7394657fa372b47aec04_img.jpg deleted file mode 100644 index c33dbc603a336867754e24b6e6d4a7bf289c4a5c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/08f6ace0c83e7394657fa372b47aec04_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:73c10030b2709b07c872a1ace881bb406cbb382286097ae9d7ee245bc7f865a8 -size 41149 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/107da2e3495b2f24352c9e3b26ec4841_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/107da2e3495b2f24352c9e3b26ec4841_img.jpg deleted file mode 100644 index 1fdab0c5bdfcd9294612fbec6921e9e6d3951270..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/107da2e3495b2f24352c9e3b26ec4841_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60a142accbc83c6b6a95c98a24d9bee48de998e8d5b0d77b9b97fbbd6903776f -size 68335 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index ac3cfab543f601f0f5d5df0819baff17d274a951..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d57cf478d6a7b5f2ccc5b9b3097071939cf811679cce8997ebdcbc5222840d3b -size 4513 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 44e4ca1e706fffc218594e75b7fbdfaeee43149d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ba36991bdae993881d357810ae680e8b2718eeb75c0831521a0cdc2d6e038f2 -size 4147 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/145d00f59802048185303f15937ea65c_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/145d00f59802048185303f15937ea65c_img.jpg deleted file mode 100644 index 1e198eb2a0d7122293a8145447109c390dc79f84..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/145d00f59802048185303f15937ea65c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:18436c4e6b492fbb036e1ac8a5ec315aa6c1ac48be0cdff1d9d7aa6a98f4ce5a -size 151003 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/1baaba7a6e54e77197475726c871067d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index ac3cfab543f601f0f5d5df0819baff17d274a951..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d57cf478d6a7b5f2ccc5b9b3097071939cf811679cce8997ebdcbc5222840d3b -size 4513 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index e9d056186f91071754a1bd66cc5b0f58f9cdcd1d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a6feea577002af775f92c1c073ef8e278549447e23549760a568e59d2a4c42d6 -size 4142 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index e9d056186f91071754a1bd66cc5b0f58f9cdcd1d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a6feea577002af775f92c1c073ef8e278549447e23549760a568e59d2a4c42d6 -size 4142 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg deleted file mode 100644 index 6ddfd874b5ed2c388a8b254cfcd05e592358b5aa..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ad7f44660e1bb603ef631a89bb564221b18b6191e6c692017cac5241d7812c28 -size 4558 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/318db222fae24a59c370fa6471d541b8_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/318db222fae24a59c370fa6471d541b8_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/318db222fae24a59c370fa6471d541b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/366a77fdefb0097b3289b4a011911390_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/366a77fdefb0097b3289b4a011911390_img.jpg deleted file mode 100644 index 19908e43a834840be039ff34231fcc7d71688004..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/366a77fdefb0097b3289b4a011911390_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba3e729be19af6a8fab96df15e7b7750ab4ea03f07f9e0ee3691bab2cfeff05 -size 40425 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 7b84e262d2fc7e0b59b4101053a42526958b946a..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0e7bdaaf5aacb655dae815886fc7e68b08115ae4458078ccf72b022c81a0a12c -size 4142 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index c4795c778abc0f382375fecd18386aae37a60839..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:44b3407151f8dbdf999f79844e5e004676072a82d90b3b3c691169a0f26ee82a -size 4204 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/4356776ca004ecba5d599667a155d7d4_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/4356776ca004ecba5d599667a155d7d4_img.jpg deleted file mode 100644 index 070dfbbc07b7ce2446bce190c880638843c2d3c7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/4356776ca004ecba5d599667a155d7d4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6a035ce35379624b4d50417bb1618ae188576c592605383b77c91e85c3329d76 -size 48661 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index 0719d9b662dad25c29233ab2163d9df2777a7e0a..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:48fc024d6159442c0a0007f6f8b66e2368910d5ddb2250bcf7fc34f695726411 -size 4492 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 95cba90c3d6af19af9cb95983cba0e79e07491fd..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5cad82723bdab81b5f01ba35adb4f4f80984c43c7d19240f9db008bceb568d07 -size 4205 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/5009e30a55479d3941af523871208f9d_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/5009e30a55479d3941af523871208f9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/552265bdbcf6d43d341fd018a9076269_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/552265bdbcf6d43d341fd018a9076269_img.jpg deleted file mode 100644 index 57609024013b3c5e9eddeeccd079feb7478d5d3f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/552265bdbcf6d43d341fd018a9076269_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c709c0bcbb7c7ebeb8e6713cd60abf22d67355375130c283fdb95e836d4dc5d7 -size 47727 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/58f4167687de8d7339594e5f6fbe0bc6_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/58f4167687de8d7339594e5f6fbe0bc6_img.jpg deleted file mode 100644 index e98c9565a679b977773d5465220bdcd05a712bef..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/58f4167687de8d7339594e5f6fbe0bc6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:823f1de708404929d4862ab29240cce2e527838994fbf4b04330f1520f9cbf43 -size 57715 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/59368942873b0c35eef79a7a985025dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/5a1abd59a95fa47ae192807de151e9eb_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/5a1abd59a95fa47ae192807de151e9eb_img.jpg deleted file mode 100644 index 4c0dac5669427250c0e80295659b3ecd04b46d68..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/5a1abd59a95fa47ae192807de151e9eb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f54a5d32c90ba928975b6ed9d12cb6ccbc9c8a8234b3707401249369d428b713 -size 62304 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/6588b1c7f14069d96744b473ad663248_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/65e8c0628536d6d4245e9ab46ba070c3_img.jpg deleted file mode 100644 index 9e06ed4ba02d28ae725d7e7554b323b4418a08a6..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/65e8c0628536d6d4245e9ab46ba070c3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:492a4585c9b6dd6cd05b527eaf879a55fa2586fcf179547c4b2cc5d1dc5d0e2e -size 18656 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg deleted file mode 100644 index de9277392364623c8c6e573a694ba25683b1552c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f884ca0f03d109eeba92916a70534d7d77c94764c20e83020693a4d00b032dac -size 4543 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg deleted file mode 100644 index e6fb401c3fb4f6a06e71dc6c007460a9acc715f2..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/753e6cc5dcad1a478caa2c7ec3a6c0a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:276e9af396bd4674eca44dbf3204acd5b42e12436ec8a5236225fe06160775ef -size 35102 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg deleted file mode 100644 index 492cad4a6ec79f60a203b7c3dccb2e3a985686c3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fb2159b27002cfbb2de52bc765f95a843bc1c5b3bc2a6db1f801acd8f5f64c21 -size 94970 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/789ee0a267b24f34bd1f45313e86c9a4_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/789ee0a267b24f34bd1f45313e86c9a4_img.jpg deleted file mode 100644 index e3ae295025e45e28a7f6650cc69de3d25809b16c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/789ee0a267b24f34bd1f45313e86c9a4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c4bbc9689dbd5387595c86feaf828cbbceaf7dc99d32d02caaaf33f28e010961 -size 25071 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index e9d056186f91071754a1bd66cc5b0f58f9cdcd1d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a6feea577002af775f92c1c073ef8e278549447e23549760a568e59d2a4c42d6 -size 4142 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/7ed5d5770331f31ade15439a21c31425_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/7ed5d5770331f31ade15439a21c31425_img.jpg deleted file mode 100644 index 2dfc7e373e980e5ea3a7a7e752e8893377c2c572..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/7ed5d5770331f31ade15439a21c31425_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ca03c1200a8dadf5dfe85c82897a561773c02cb8404261584289843e31ed4897 -size 27865 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 1ac866ebfe23959f91f71ac6485464d244ed172c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f0a7ae7e68d01cb903e9a35065f8afbf9764231801e9dc07633e72a6d3a25f1d -size 4016 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index e9d056186f91071754a1bd66cc5b0f58f9cdcd1d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a6feea577002af775f92c1c073ef8e278549447e23549760a568e59d2a4c42d6 -size 4142 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8b4befaffc5166da571069410e207aea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 5541fd03c1ff513babe7af052ff1248a9b536176..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c11a3f1913549c9f26d126e728bdf63ac767327732885986a88111dedfadc509 -size 4204 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 7b84e262d2fc7e0b59b4101053a42526958b946a..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0e7bdaaf5aacb655dae815886fc7e68b08115ae4458078ccf72b022c81a0a12c -size 4142 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index ac3cfab543f601f0f5d5df0819baff17d274a951..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d57cf478d6a7b5f2ccc5b9b3097071939cf811679cce8997ebdcbc5222840d3b -size 4513 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index ac3cfab543f601f0f5d5df0819baff17d274a951..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d57cf478d6a7b5f2ccc5b9b3097071939cf811679cce8997ebdcbc5222840d3b -size 4513 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg deleted file mode 100644 index 5281d27dd2a355e06986017f009867ad96e0566d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c95f8a38f5ec1bbbacb028989970243ef1d486e10f6082eb799ac84bf8f74c1f -size 40356 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/bd671b21db63e6fdb2196e9b18502aac_img.jpg deleted file mode 100644 index 7fcc46f21d20b6aa826279641ebe8bd0e3a15494..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/bd671b21db63e6fdb2196e9b18502aac_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:89f63fdd5c7dff1d41a1417b284889f02db8f2deb60de8c1c344a66a1b9342da -size 75816 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 0bea580b82b985ec6bd9836785eb1050583f8682..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b724ecded9a829c53fd8c426a1ba2377d42d7ab25c4731fa9713baf07a0b7e07 -size 4085 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg deleted file mode 100644 index fb44d6491cac153e321e014ba27d5d9ce233a1c2..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9391482a8b39bb4d1773c8d1ebf348b3066c285b6b1da996f0639fbabba2fc03 -size 28493 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index cefe2a113dd46e6dff4173154f641ac10b37365e..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5e653a7cf5823ab1034a8814af68db7a13549c2750e04cfe4eb530e43a87368c -size 4491 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d3b5eac55166fc428a223bba5c46961b_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d3b5eac55166fc428a223bba5c46961b_img.jpg deleted file mode 100644 index 2e050e6f0067f042dee81d24e6cee0386940481f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d3b5eac55166fc428a223bba5c46961b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0273fab4b1e65878ebb91f053a5986b1297454a32f33142a581b71e6d71df402 -size 47925 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 1624885035e55cf6001c2009d780b95cc6680b68..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c92f80674dbfe05e46caab62e5fda53b55f3ffd6f04aadb315c070b5286ef4d9 -size 4189 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg deleted file mode 100644 index ab6fda5bca8d1a7132c739b351d059eba2e74377..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:429b1e731c26a37977778615e1c6fd5446074c91acef8b25017019b41153722f -size 36186 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index ac3cfab543f601f0f5d5df0819baff17d274a951..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d57cf478d6a7b5f2ccc5b9b3097071939cf811679cce8997ebdcbc5222840d3b -size 4513 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg deleted file mode 100644 index 3208b1e30230c1c26d47a82f9a238d3c112e716f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fb8701fa8b81071b2b688017bb4ec897f0147e170366e60f86f7fa3528862b21 -size 4528 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index ac3cfab543f601f0f5d5df0819baff17d274a951..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d57cf478d6a7b5f2ccc5b9b3097071939cf811679cce8997ebdcbc5222840d3b -size 4513 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index b78ad8f386db9327efb85068c94591ec29bfcd00..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edfd71aa47dcb9a5631eeb7505f6f9c32e33fddebaf40875018821f737f9ef3c -size 4038 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e151d3468319b81f042ca232c4d82e4b_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e151d3468319b81f042ca232c4d82e4b_img.jpg deleted file mode 100644 index 3954011080a2a3b85d776162b3f1462adea88b00..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e151d3468319b81f042ca232c4d82e4b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:27569139f352c6cd817d7cb4e5b31ab1efac87160d14b8187be43ef399b2cb34 -size 75396 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e29665b8abcea967ef289c6aff07ae4c_img.jpg deleted file mode 100644 index 649de29768114f8e0d27f5c394deeca2c49abf35..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e29665b8abcea967ef289c6aff07ae4c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:90be413c32c7fc3919048a4da3f8901a41176bddc0e0d9b4873afd43d1921bba -size 63085 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index a932b5f3159895ead6dac8a45dc07c3191dc78a7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6aaf6f61d4ad6f8cf3ce751ae788d2ee1a9e0d8a66e4c1dd272b4da723cd24c -size 4013 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index afba4cbc0ac8c2c472a372fb4194c683e1ee58f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:000095a140bd7ffa463a618a958f3f4db3d9ae64e0cecbd298ce079b6b1ba3e8 -size 4157 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg deleted file mode 100644 index 9ba907cdd49d3bdd74d65c87ea8764e05de0b08f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/eb5677b570ab2a3e9d8f5d35ca5b8a4d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ab98c1666341a231e4ede950e3bd7b398c72383982368fa9c89632b50762968a -size 113996 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/f74adaa1840504407cd4272995426f82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 1af4baa9997cb759fd2b6a6708563bc34a058214..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b7de6899a3e71e7d5cb96e3cf5688867518bde70faaa5a1d8d15817d1aa6097 -size 4042 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg deleted file mode 100644 index de9277392364623c8c6e573a694ba25683b1552c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f884ca0f03d109eeba92916a70534d7d77c94764c20e83020693a4d00b032dac -size 4543 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg deleted file mode 100644 index 5d3a9e0ad3d2d084d8be44afbffee70a2c2b28bd..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a50bcec4bd26aa19dadf7f2ba3e44053f6b51e6f513c94c60b531d25435364e9 -size 46880 diff --git a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.O-CLOUD-Security.0-R005-v09.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/doc.md b/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/doc.md deleted file mode 100644 index 4ebb9a6e3df5a19f56ad5100f7d46359b814bc72..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/doc.md +++ /dev/null @@ -1,446 +0,0 @@ - - -# --- **O-RAN Work Group 11 (Security Work Group)****Study on Post-Quantum Cryptography** - -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 tables ..... 3 -- Foreword..... 4 -- Modal verbs terminology ..... 4 -- Introduction ..... 4 -- 1 Scope ..... 5 -- 2 References ..... 5 -- 2.1 Normative references ..... 5 -- 2.2 Informative references ..... 5 -- 3 Definition of terms, symbols and abbreviations ..... 9 -- 3.1 Terms ..... 9 -- 3.2 Symbols..... 9 -- 3.3 Abbreviations..... 9 -- 4 Post-Quantum Cryptography background..... 10 -- 5 Cryptographic inventory ..... 10 -- Annex: Change history/Change request (history) ..... 16 - -# --- List of tables - -Table 5-1: Cryptographic inventory..... 10 - -# Foreword - -This Technical Report (TR) has been produced by WG11 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 - -The increasing sophistication of quantum computing poses a significant threat to the security of classical asymmetric cryptographic algorithms currently used in O-RAN networks. As quantum computers become more powerful, they will be capable of breaking asymmetric classical encryption algorithms, potentially compromising the confidentiality, integrity, and authenticity of sensitive information exchanged between network entities. This vulnerability has far-reaching implications for the security and trustworthiness of O-RAN networks, which are designed to provide secure and reliable communication services for critical infrastructure and applications. - -The migration to Quantum Safe Cryptography (QSC) is essential to ensure the long-term security and resilience of O-RAN networks against potential quantum computer-based attacks. QSC refers to cryptographic techniques and algorithms that are resistant to attacks by both classical and quantum computers. By migrating to QSC, O-RAN networks can maintain their security posture and prevent potential disruptions to services and operations. - -This technical report contains a cryptographic inventory, covering all cryptographic algorithms employed in O-RAN specification at this time. - -# 1 Scope - -The present document presents the Post-Quantum Cryptography study as it applies to O-RAN architectural elements. - -# 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] NIST Post-Quantum Cryptography, call for papers; . -- [i.3] FIPS 203: Module-Lattice-Based Key-Encapsulation Mechanism Standard; . -- [i.4] FIPS 204: Module-Lattice-Based Digital Signature Standard; . -- [i.5] FIPS 205: Stateless Hash-Based Digital Signature Standard; . -- [i.6] NCSC whitepaper: Next steps in preparing for post-quantum cryptography; . -- [i.7] ETSI TR 103 619 V1.1.1 (2020-07), " Migration strategies and recommendations to Quantum Safe schemes". -- [i.8] ETSI TC CYBER, ETSI QSC, " Quantum Safe Cryptographic Protocol Inventory", CYBERQSC(23)032007r2\_QSC\_Protocol\_Inventory\_LSOut.pdf. -- [i.9] GSMA, "LS regarding the publication of the Post Quantum Cryptography – Guidelines for Telecom Use Cases document in Feb 24". -- [i.10] GSMA, "Post Quantum Cryptography – Guidelines for Telecom Use Cases"; . -- [i.11] NIST, "Post-Quantum Cryptography"; . -- [i.12] O-RAN.WG4.TS.MP: "O-RAN WG4 Management Plane Specification". -- [i.13] O-RAN.WG10.TS.O1-Interface: "O-RAN WG10 O-RAN O1 Interface Specification". - -- [i.14] O-RAN.WG11.TS.SecProtSpec: "O-RAN WG11 Security Protocols Specifications". -- [i.15] IETF RFC 5656: "Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer". -- [i.16] IETF RFC 8709: "Ed25519 and Ed448 Public Key Algorithms for the Secure Shell (SSH) Protocol". -- [i.17] IETF RFC 5647: "AES Galois Counter Mode for the Secure Shell Transport Layer Protocol". -- [i.18] IETF RFC 4344: "The Secure Shell (SSH) Transport Layer Encryption Modes". -- [i.19] IETF RFC 4419: "Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol". -- [i.20] IETF RFC 8270. "Increase the Secure Shell Minimum Recommended Diffie-Hellman Modulus Size to 2048 Bits". -- [i.21] IETF RFC 8731: "Secure Shell (SSH) Key Exchange Method Using Curve25519 and Curve448". -- [i.22] IETF RFC 6668: "SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol". -- [i.23] IETF RFC 4418: "UMAC: Message Authentication Code using Universal Hashing". -- [i.24] O-RAN.WG2.A1TP: "A1 interface: Transport Protocol". -- [i.25] O-RAN.WG2.R1TP: "Transport Protocols for R1 Services". -- [i.26] O-RAN.WG3.Y1GAP: "Y1 interface: General Aspects and Principles". -- [i.27] IETF RFC 5116: "An Interface and Algorithms for Authenticated Encryption". -- [i.28] IETF RFC 8422: "Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS) Versions 1.2 and Earlier". -- [i.29] IETF RFC 7919: "Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS) ". -- [i.30] IETF RFC 6234: "US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF) ". -- [i.31] IETF RFC 8446: "The Transport Layer Security (TLS) Protocol Version 1.3". -- [i.32] IETF RFC 8439: "ChaCha20 and Poly1305 for IETF Protocols". -- [i.33] BSI TR-02102-2: "Cryptographic Mechanisms: Recommendations and Key Lengths: Use of Transport Layer Security (TLS) ". -- [i.34] NIST SP 800-38D: "Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC". -- [i.35] IETF RFC 8032: "Edwards-Curve Digital Signature Algorithm (EdDSA)". -- [i.36] IETF RFC 7518: "JSON Web Algorithms (JWA)". -- [i.37] O-RAN.WG3.RICARCH: "O-RAN Near-RT RIC Architecture". -- [i.38] O-RAN.WG6.AAL-GAnP: "O-RAN Acceleration Abstraction Layer General Aspects and Principles". -- [i.39] O-RAN.WG6.O2-GA&P: "O-RAN WG6 O2 Interface General Aspects and Principles". -- [i.40] IETF RFC 7516: "JSON Web Encryption (JWE)". -- [i.41] IEEE Std 802.1AE-2018, "IEEE Standard for Local and metropolitan area networks — Media Access Control (MAC) Security", IEEE, 2018. -- [i.42] IEEE 802.1X-2020, "IEEE Standard for Local and Metropolitan Area Networks--Port-Based Network Access Control", IEEE, 2020-02-28. - -- [i.43] O-RAN.WG4.TS.CUS: "O-RAN WG11 Study on Security for Fronthaul CUS-Plane". -- [i.44] IETF RFC 4493: "The AES-CMAC Algorithm". -- [i.45] IETF RFC 5216: "The EAP-TLS Authentication Protocol". -- [i.46] IETF RFC 9190: "EAP-TLS 1.3: Using the Extensible Authentication Protocol with TLS 1.3". -- [i.47] IEEE Std 1588 – 2019, "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems", IEEE, 2019. -- [i.48] IETF RFC 2410: "The NULL Encryption Algorithm and Its Use with IPsec". -- [i.49] IETF RFC 2404: "The Use of HMAC-SHA-1-96 within ESP and AH". -- [i.50] IETF RFC 3526: "More Modular Exponential (MODP) Diffie-Hellman groups for Internet Key Exchange (IKE)". -- [i.51] IETF RFC 3566: "The AES-XCBC-MAC-96 Algorithm and Its Use with IPsec". -- [i.52] IETF RFC 3602: "The AES-CBC Cipher Algorithm and Its Use with IPsec". -- [i.53] IETF RFC 4106: "The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP)". -- [i.54] IETF RFC 4309: "Using Advanced Encryption Standard (AES) CCM Mode with IPsec Encapsulating Security Payload (ESP)". -- [i.55] IETF RFC 4543: "The Use of Galois Message Authentication Code (GMAC) in IPsec ESP and AH". -- [i.56] IETF RFC 4868: "Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with IPsec". -- [i.57] IETF RFC 5114: "Additional Diffie-Hellman Groups for Use with IETF Standards". -- [i.58] IETF RFC 5282: "Using Authenticated Encryption Algorithms with the Encrypted Payload of the Internet Key Exchange version 2 (IKEv2) Protocol". -- [i.59] IETF RFC 7296: "Internet Key Exchange Protocol Version 2 (IKEv2)". -- [i.60] IETF RFC 7634: "ChaCha20, Poly1305, and Their Use in the Internet Key Exchange Protocol (IKE) and IPsec". -- [i.61] IETF RFC 8221: "Cryptographic Algorithm Implementation Requirements and Usage Guidance for Encapsulating Security Payload (ESP) and Authentication Header (AH)". -- [i.62] IETF RFC 8247: "Algorithm Implementation Requirements and Usage Guidance for the Internet Key Exchange Protocol Version 2 (IKEv2) ". -- [i.63] O-RAN.WG3.TS.E2GAP: "O-RAN WG3 E2 General Aspects and Principles (E2GAP)". -- [i.64] O-RAN.WG1.TS.OAD: "O-RAN Architecture Description". -- [i.65] IETF RFC 7519: "JSON Web Token (JWT)". -- [i.66] IETF RFC 6749: "The OAuth 2.0 Authorization Framework". -- [i.67] IETF RFC 2631: "Diffie-Hellman Key Agreement Method". -- [i.68] IETF RFC 3370: "Cryptographic Message Syntax (CMS) Algorithms". -- [i.69] IETF RFC 3394: "Advanced Encryption Standard (AES) Key Wrap Algorithm". -- [i.70] IETF RFC 4210: "Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP)". -- [i.71] IETF RFC 4211: "Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)". - -- [i.72] IETF RFC 5753: "Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)". -- [i.73] IETF RFC 8017: "PKCS #1: RSA Cryptography Specifications Version 2.2". -- [i.74] IETF RFC 8018: "PKCS #5: Password-Based Cryptography Specification Version 2.1". -- [i.75] IETF RFC 8702: "Use of the SHAKE One-Way Hash Functions in the Cryptographic Message Syntax (CMS)". -- [i.76] IETF RFC 9045: "Algorithm Requirements Update to the Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)". -- [i.77] IETF RFC 9481: "Certificate Management Protocol (CMP) Algorithms". -- [i.78] FIPS SP 800-185: SHA-3 Derived Functions: cSHAKE, KMAC, TupleHash, and ParallelHash; . -- [i.79] FIPS 180-4: Secure Hash Standard (SHS); . -- [i.80] FIPS 186-5: Digital Signature Standard (DSS); . -- [i.81] FIPS 197: Advanced Encryption Standard (AES); . -- [i.82] FIPS 202: SHA-3 Standard: Permutation-Based Hash and Extendable-Output Functions; . -- [i.83] NIST SP 800-186: "Recommendations for Discrete Logarithm-based Cryptography: Elliptic Curve Domain Parameters". -- [i.84] NIST: "Advanced Encryption Standard (AES) (FIPS PUB 197)". -- [i.85] NIST SP 800-38A: "Recommendation for Block Cipher Modes of Operation: Methods and Techniques". -- [i.86] IETF RFC 8017: "PKCS #1: RSA Cryptography Specifications Version 2.2". -- [i.87] Void. -- [i.88] NIST: "SHA-3 Standard: Permutation-Based Hash and Extendable-Output Function (FIPS PUB 202)". -- [i.89] NIST SP 800-90A: "Recommendation for Random Number Generation Using Deterministic Random Bit Generators". -- [i.90] NIST SP 800-90B: "Recommendation for the Entropy Sources Used for Random Bit Generation". -- [i.91] NIST SP 800-90C: "Recommendation for Random Bit Generator (RBG) Constructions". -- [i.92] BSI: "Documentation and Analysis of the Linux Random Number Generator". - -# 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: - -**Post-Quantum Cryptography:** An area of cryptography that researches and advances the use of quantum-resistant primitives, with the goal of keeping existing public key infrastructure intact in a future era of quantum computing. Intended to be secure against both quantum and classical computers and deployable without drastic changes to existing communication protocols and networks. [i.11] - -**Quantum Safe Cryptography:** see Post-Quantum Cryptography - -## 3.2 Symbols - -Void. - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations [given in [i.1] and the following] apply: - -| | | -|-----------|--------------------------------------------------------------------------------| -| AES | Advanced Encryption Standard | -| CBC | Cipher Block Chaining | -| CBOM | Cryptographic bill of material | -| CMAC | Cipher-based Message Authentication Code | -| CMP | Certificate Management Protocol | -| CUS-Plane | Control, User and Synchronization Plane | -| DH | Diffie-Hellman (Key Exchange) | -| DTLS | Datagram Transport Layer Security | -| ECDSA | Elliptic Curve Digital Signature Algorithm | -| ETM | Encrypt-then-MAC | -| FH | Fronthaul | -| GCM | Galois/Counter Mode | -| HMAC | Hash-based message authentication code | -| JSON | JavaScript Object Notation | -| JWA | JSON Web Algorithms | -| JWE | JSON Web Encryption | -| JWS | JSON Web Signature | -| JWT | JSON Web Token | -| MACsec | Media Access Control security | -| MGF | Mask generation function | -| MKA | MACsec Key Agreement | -| OFH | Open Fronthaul | -| PKC | Public-Key Cryptography | -| PKCS | Public-Key Cryptography Standards | -| PQC | Post-Quantum Cryptography | -| PTP | Precision Time Protocol | -| PSS | Probabilistic Signature Scheme | -| QSC | Quantum Safe Cryptography | -| RSA | Rivest–Shamir–Adleman | -| RSAASSA | RSA Probabilistic Signature Scheme with Appendix (often referred to as RSASSA) | -| SHA | Secure Hash Algorithm | -| SSH | Secure Shell | -| TLS | Transport Layer Security | - -XCBC                    eXtended Cipher Block Chaining - XPN                    eXtended Packet Number - -# 4 Post-Quantum Cryptography background - -NIST has initiated the process of the Post Quantum Cryptography (PQC) standardization in 2017 [i.2]. On 5th Jul 2022, they announced the standard candidates for public-key encryption: - -- CRYSTALS-Kyber, -- for digital signature: CRYSTALS-Dilithium, FALCON and SPHINCS+. - -On 13th Aug 2024, NIST published FIPS 203 [i.3], FIPS 204 [i.4] and FIPS 205 [i.5], specifying algorithms derived from CRYSTALS-Dilithium, CRYSTALS-Kyber and SPHINCS+: ML-KEM, ML-DSA and SLH-DSA. A future FIPS 206 is planned to specify FN-DSA, based on FALCON. - -Further input from NIST: - -“Quantum computers would completely break many public-key cryptosystems, including RSA, DSA, and elliptic curve cryptosystems. These cryptosystems are used to implement digital signatures and key establishment and play a crucial role in ensuring the confidentiality and authenticity of communications on the Internet and other networks.” [i.2] - -Further input from NCSC: - -“In contrast with PKC, the security of symmetric cryptography is not significantly impacted by quantum computers, and existing symmetric algorithms with at least 128-bit keys (such as AES) can continue to be used. The security of hash functions such as SHA-256 is also not significantly affected, and secure hash functions can also continue to be used.” [i.6] - -The ETSI QSC group has developed a document outlining a Quantum Safe Cryptography migration strategy and recommendations for transitioning to quantum-safe schemes [i.7]. A key component of this strategy is the creation of a cryptographic inventory or cryptographic bill of material (CBOM) to support the development of a preparation and PQC migration plan, as well as the execution of the migration. - -**According to the LS [i.8], the ETSI QSC is seeking additional information, such as a "detailed list of cryptographic algorithms and/or protocol implementations." This list may include "guidance on algorithm exposure, effective key lengths, potential for hybrid deployment, and potential for crypto agility."** - -In a related development, as noted in another LS [i.9], the GSMA has produced a Guidelines for Telecom Use Cases document [i.10], which includes the development of a "comprehensive cryptographic inventory" to some extent. - -# 5 Cryptographic inventory - -**Table 5-1: Cryptographic inventory** - -| Security Protocol | Traditional Algorithm | Algorithm Development Organisation and document(s) | Algorithm used for | O-RAN Adoption (EXAMPLE: Interfaces, APIs) | O-RAN specification(s) | -|-------------------|-----------------------|----------------------------------------------------|--------------------|--------------------------------------------|------------------------| -| TLS 1.2, DTLS 1.2 | AES-128-GCM | RFC 5116 [i.27] (NOTE 3) | Cipher suites | OFH m-plane [i.12]
O1 [i.13] | SPS [i.14] | -| | AES-256-GCM | | | | | -| | secp256r1 | RFC 8422 [i.28] | | | | - -| Security Protocol | Traditional Algorithm | Algorithm Development Organisation and document(s) | Algorithm used for | O-RAN Adoption (EXAMPLE: Interfaces, APIs) | O-RAN specification(s) | | | -|-------------------|--------------------------------------|----------------------------------------------------|-------------------------------------|-----------------------------------------------------------------------------------|------------------------|--|--| -| | secp384r1 | RFC 7919 [i.29] | Key exchange | A1 [i.24]
R1 [i.25]
Y1 [i.26]
O2 [i.39]
SMO External Interface [i.64] | | | | -| | ffdhe2048 | | | | | | | -| | ffdhe3072 | | | | | | | -| | ffdhe4096 | | | | | | | -| | ffdhe6144 | | | | | | | -| | ffdhe8192 | | | | | | | -| | SHA-256 | RFC 6234 [i.30] | Hash functions | | | | | -| | SHA-384 | | | | | | | -| | ecdsa | RFC 8422 [i.28] | Signature algorithms | | | | | -| | rsa_pss_rsae_* | RFC 8446 [i.31] | | | | | | -| | rsa_pkcs1 | RFC 8032 [i.35] (NOTE 2) | | | | | | -| TLS 1.3, DTLS 1.3 | AES-128-GCM | RFC 5116 [i.27] (NOTE 3) | Cipher suites | | | | | -| | AES-256-GCM | | | | | | | -| | ChaCha20-Poly1305 | | | | | | | -| | secp256r1 | RFC 8422 [i.28] | Key exchange | | | | | -| | secp384r1 | | | | | | | -| | secp521r1 | | | | | | | -| | SHA-256 | RFC 6234 [i.30] | Hash functions | | | | | -| | SHA-384 | | | | | | | -| | SHA-512 | | | | | | | -| | ecdsa secp256r1_sha256 | RFC 8446 [i.31] | Signature algorithms | | | | | -| | ecdsa secp384r1_sha384 | | | | | | | -| | ecdsa secp521r1_sha512 | | | | | | | -| | rsa_pss_rsae_sha256 | | | | | | | -| | rsa_pss_rsae_sha384 | | | | | | | -| | rsa_pss_rsae_sha512 | | | | | | | -| | rsa_pss_pss_sha256 | | | | | | | -| | rsa_pss_pss_sha384 | | | | | | | -| | rsa_pss_pss_sha512 | | | | | | | -| | ed25519 | RFC 8032 [i.35] | | | | | | -| SSH | ecdsa-sha2-nistp256 | RFC 5656 [i.15][i.15] | Key agreement | OFH m-plane [i.12]
O1 [i.13]
SMO External Interface [i.64] | SPS [i.14] | | | -| | ecdsa-sha2-nistp384 | | | | | | | -| | ecdsa-sha2-nistp521 | | | | | | | -| | ssh-ed25519 | RFC 8709 [i.16] | | | | | | -| | ssh-ed448 | | | | | | | -| | aes256-gcm | RFC 5647 [i.17] | Symmetric encryption and decryption | | | | | -| | aes128-gcm | | | | | | | -| | aes256-ctr | | | | | | | -| | aes192-ctr | | | | | | | -| | aes128-ctr | RFC 4344 [i.18] | | | | | | -| | ecdh-sha2-nistp521 | | | | | | | -| | ecdh-sha2-nistp384 | | | | | | | -| | ecdh-sha2-nistp256 | RFC 5656 [i.15] | Key exchange | | | | | -| | diffie-hellman-group-exchange-sha256 | | | | | | | -| | curve25519-sha256 | | | | | | | -| | hmac-sha2-512-etm | RFC 6668 [i.22] (NOTE 1) | Message authentication codes | | | | | -| | hmac-sha2-512 | | | | | | | -| | hmac-sha2-256-etm | | | | | | | -| | hmac-sha2-256 | | | | | | | -| | umac-128 | RFC 4418 [i.23] | | | | | | -| IPsec | ENCR_NULL | RFC 2410 [i.48] | ESP encryption algorithms | E2 [i.63] | SPS [i.14] | | | -| | ENCR_AES_CBC | RFC 3602 [i.52] | | | | | | -| | ENCR_AES_CCM_8 | RFC 4309 [i.54] | | | | | | -| | ENCR_AES_GCM_16 | RFC 4106 [i.53] | | | | | | - -| Security Protocol | Traditional Algorithm | Algorithm Development Organisation and document(s) | Algorithm used for | O-RAN Adoption (EXAMPLE: Interfaces, APIs) | O-RAN specification(s) | | | -|-------------------|--------------------------------------------------------|----------------------------------------------------|---------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|------------------------|--|--| -| | ENCR_CHACHA20_POLY1305 | RFC 7634 [i.60] | (RFC 8221 – [i.61])
ESP and AH Authentication Algorithms (RFC 8221 – [i.61]) | | | | | -| | AUTH_NONE (NOTE 7) | RFC 7296 [i.59],
RFC 5282 [i.58] | | | | | | -| | AUTH_HMAC_SHA1_96 | RFC 2404 [i.49],
RFC 7296 [i.59] | | | | | | -| | AUTH_AES_XCBC_96 (NOTE 8) | RFC 3566 [i.51],
RFC 7296 [i.59] | | | | | | -| | AUTH_AES_128_GMAC | RFC 4543 [i.55] | | | | | | -| | AUTH_AES_256_GMAC | RFC 4543 [i.55] | | | | | | -| | AUTH_HMAC_SHA2_256_128 | RFC 4868 [i.56] | | | | | | -| | AUTH_HMAC_SHA2_512_256 | RFC 4868 [i.56] | | | | | | -| | ENCR_AES_CBC | RFC 3602 [i.52] | IKEv2
Encryption Algorithm Transforms (RFC 8247 – [i.62]) | | | | | -| | ENCR_CHACHA20_POLY1305 | RFC 7634 [i.60] | | | | | | -| | ENCR_ASES_GCM_16 | RFC 4106 [i.53] | | | | | | -| | ENCR_AES_CCM_8 | RFC 4309 [i.54] | | | | | | -| | AUTH_HMAC_SHA2_256_128 | RFC 4868 [i.56] | IKEv2
Integrity Algorithm Transforms (RFC 8247 – [i.62]) | | | | | -| | AUTH_HMAC_SHA2_512_256 | RFC 4868 [i.56] | | | | | | -| | AUTH_HMAC_SHA1_96 | RFC 2404 [i.49],
RFC 7296 [i.59] | | | | | | -| | AUTH_AES_XCBC_96 | RFC 3566 [i.51],
RFC 7296 [i.59] | | | | | | -| | PRF_HMAC_SHA2_256 | RFC 4868 [i.56] | IKEv2
Pseudorandom Function Transforms (RFC 8247 – [i.62]) | | | | | -| | PRF_HMAC_SHA2_512 | RFC 4868 [i.56] | | | | | | -| | PRF_HMAC_SHA1 | RFC 2404 [i.49] | | | | | | -| | PRF_AES128_XCBC | RFC 4344 [i.18] | | | | | | -| | DH 14 – 2048-bit MODP Group | RFC 3526 [i.50] | IKEv2 Diffie-Hellman Group Transforms (RFC 8247 – [i.62]) | | | | | -| | DH 19 – 256-bit random ECP group | RFC 5114 [i.57] | | | | | | -| JWS (NOTE 5) | HS256 (HMAC using SHA-256) | RFC 7518 [i.36] | Message authentication codes | A1 [i.24]
R1 [i.25]
Y1 [i.26]
Near-RT RIC APIs [i.37]
AALI-C-Mgmt interface [i.38]
O2 [i.39] | SPS [i.14] | | | -| | HS384 (HMAC using SHA-384) | | | | | | | -| | HS512 (HMAC using SHA-512) | | | | | | | -| | RS256 (RSASSA-PKCS1-v1_5 using SHA-256) | RFC 7518 [i.36] | Signature algorithms | | | | | -| | RS384 (RSASSA-PKCS1-v1_5 using SHA-384) | | | | | | | -| | RS512 (RSASSA-PKCS1-v1_5 using SHA-512) | | | | | | | -| | ES256 (ECDSA using P-256 curve and SHA-256) | | | | | | | -| | ES384 (ECDSA using P-384 curve and SHA-384) | | | | | | | -| | ES512 (ECDSA using P-512 curve and SHA-512) | | | | | | | -| | PS256 (RSASSA-PSS using SHA-256 and MGF1 with SHA-256) | | | | | | | -| | PS384 (RSASSA-PSS using SHA-384 and MGF1 with SHA-384) | | | | | | | -| | PS512 (RSASSA-PSS using SHA-512 and MGF1 with SHA-512) | | | | | | | - -| Security Protocol | Traditional Algorithm | Algorithm Development Organisation and document(s) | Algorithm used for | O-RAN Adoption (EXAMPLE: Interfaces, APIs) | O-RAN specification(s) | | | -|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|-------------------------------------------------------------------|---------------------------------------------------------------------|----------------------------------|--|--| -| JWE | A128CBC-HS256
(AES_128_CBC_HMAC_SHA_256) | RFC 7518 [i.36]
RFC 7516 [i.40], clause 4.1.2. | Encryption algorithms | N/A | Not yet specified | | | -| | A192CBC-HS384
(AES_192_CBC_HMAC_SHA_384) | | | | | | | -| | A256CBC-HS512
(AES_256_CBC_HMAC_SHA_512) | | | | | | | -| | A128GCM (AES GCM using 128-bit key) | | | | | | | -| | A192GCM (AES GCM using 192-bit key) | | | | | | | -| | A256GCM (AES GCM using 256-bit key) | | | | | | | -| OAuth 2.0 | (NOTE 6) | RFC 6749 [i.66] | Authorization framework | A1 [i.24], O2 [i.39], R1 [i.25], Y1 [i.26], Near RT RIC APIs [i.37] | SPS [i.14] | | | -| MACsec
(NOTE 4) | GCM-AES-128 | IEEE 802.1AE-2018 [i.41]
IEEE 802.1X-2020 [i.42] | Symmetric encryption and decryption, Message authentication codes | OFH CUS Plane Security [i.43]
OFH m-plane [i.12] | SPS [i.14]
OFH m-plane [i.12] | | | -| | GCM-AES-256 | | | | | | | -| | GCM-AES-XPN-128 | | | | | | | -| | GCM-AES-XPN-256 | | | | | | | -| | AES-CMAC | RFC 4493 [i.44] | Key derivation | | | | | -| PTP | HS256 (HMAC using SHA-256) | IEEE 1588 [i.47], clause 16.14 | Message authentication codes | OFH CUS Plane Security [i.43]
OFH m-plane [i.12] | SPS [i.14]
OFH m-plane [i.12] | | | -| | HS384 (HMAC using SHA-384) | | | | | | | -| | HS512 (HMAC using SHA-512) | | | | | | | -| CMP | SHA2:
sha224
sha256
sha384
sha512 | RFC 9481 [i.77]
Sec 2.1,
FIPS Pub 180-4 [i.79] | Message Digest Algorithms | OFH m-plane [i.12] | SPS [i.14] | | | -| | SHAKE:
shake128
shake256 | RFC 9481 [i.77]
Sec 2.2,
FIPS Pub 202 [i.82] | | | | | | -| | RSA:
RSASSA-PSS
RSASSA-PSS-SHAKE128
RSASSA-PSS-SHAKE256
sha224WithRSAEncryption
sha256WithRSAEncryption
sha384WithRSAEncryption
sha512WithRSAEncryption | RFC 9481 [i.77]
Sec 3.1,
RFC 8017 [i.73] | Signature Algorithms | | | | | -| | ECDSA:
ecdsa-with-SHA224
ecdsa-with-SHA256
ecdsa-with-SHA384
ecdsa-with-SHA512
ecdsa-with-shake128
ecdsa-with-shake256 | RFC 9481 [i.77]
Sec 3.2,
FIPS Pub 186-5 [i.80] | | | | | | -| | EdDSA:
Ed25519
Ed448 | RFC 9481 [i.77]
Sec 3.2, | | | | | | - -| Security Protocol | Traditional Algorithm | Algorithm Development Organisation and document(s) | Algorithm used for | O-RAN Adoption (EXAMPLE: Interfaces, APIs) | O-RAN specification(s) | -|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|---------------------------------------------------------------------|--------------------------------------------|------------------------| -| | | FIPS Pub 186-5 [i.80] | | | | -| | Diffie-Hellman:
ESDH | RFC 9481 [i.77]
Sec 4.1.1
RFC 2631 [i.67]
RFC 3370 [i.68] | Key Management Algorithms (KMA) – Key Agreement Algorithms | | | -| | ECDH:
dhSinglePass-stdDH-sha224kdf
dhSinglePass-stdDH-sha256kdf
dhSinglePass-stdDH-sha384kdf
dhSinglePass-stdDH-sha512kdf
dhSinglePass-cofactorDH-sha224kdf
dhSinglePass-cofactorDH-sha256kdf
dhSinglePass-cofactorDH-sha384kdf
dhSinglePass-cofactorDH-sha512kdf
mqvSinglePass-sha224kdf
mqvSinglePass-sha256kdf
mqvSinglePass-sha384kdf
mqvSinglePass-sha512kdf
X25519
X448 | RFC 9481 [i.77]
Sec 4.1.2
RFC 5753 [i.72] | | | | -| | RSA:
RSA (PKCS #1 v1.5)
RSAES-OAEP | RFC 9481 [i.77]
Sec 4.2 | KMA – Key Transport Algorithms | | | -| | AES Key Wrap:
aes128-wrap
aes192-wrap
aes256-wrap | RFC 9481 [i.77]
Sec 4.3,
FIPS Pub 197 [i.81],
RFC 3394 [i.69] | KMA – Symmetric Key-Encryption Algorithms | | | -| | PBKDF2:
PBKDF2 | RFC 9481 [i.77]
Sec 4.4,
RFC 8018 [i.74] | KMA – Key Derivation Algorithms | | | -| | AES-CBC:
aes128-CBC
aes192-CBC
aes256-CBC | RFC 9481 [i.77]
Sec 5,
FIPS Pub 197 [i.81] | Content-Encryption Algorithms | | | -| | PasswordBased MAC:
PasswordBasedMac | RFC 9481 [i.77]
Sec 6.1.1
RFC 4210 [i.70]
RFC 4211 [i.71]
RFC 9045 [i.76] | Message Authentication Code (MAC) Algorithms – Password - Based MAC | | | -| | PBMAC1:
PBMAC1 | RFC 9481 [i.77]
Sec 6.1.2
RFC 8018 [i.74] | | | | -| | SHA2-Based HMAC:
hmacWithSHA224
hmacWithSHA256
hmacWithSHA384
hmacWithSHA512 | RFC 9481 [i.77]
Sec 6.2.1
RFC 8018 [i.74] | MAC Algorithms – Symmetric Key-Based MAC | | | -| | AES-GMAC:
aes128-GMAC
aes192-GMAC
aes256-GMAC | RFC 9481 [i.77]
Sec 6.2.2
FIPS Pub 197 [i.81]
FIPS SP 800-38D [i.34] | | | | -| | SHAKE-Based KMAC:
KMACWithSHAKE128
KMACWithSHAKE256 | RFC 9481 [i.77]
Sec 6.2.3
RFC 8702 [i.75] | | | | - -| Security Protocol | Traditional Algorithm | Algorithm Development Organisation and document(s) | Algorithm used for | O-RAN Adoption (EXAMPLE: Interfaces, APIs) | O-RAN specification(s) | -|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|---------------------------------------|-----------------------------------------------------------------------------------------------|------------------------| -| | | FIPS SP 800-185 [i.78] | | | | -| Cryptographic operations (see [i.14], section 5) | RSASSA-PSS
RSA_PKCS1_V1_5 | FIPS Pub 186-5 [i.80] | Signature generation and verification | Application package authenticity and integrity | SPS [i.14] | -| | ECDSA using NIST-approved curves (P-256, P-384, or P-521) | FIPS Pub 186-5 [i.80], SP 800-186 [i.83] | | | | -| | AES_128, AES_192 and AES_256 | FIPS 197 [i.84], SP 800-38A [i.85] (operation modes) | Symmetric Encryption/Decryption | Confidentiality of data | | -| | RSAES-OAEP | IETF RFC 8017 [i.86] | Asymmetric Encryption/Decryption | | | -| | SHA-2 family (SHA-224, SHA-256, SHA-384, SHA-512, SHA-512/224 and SHA-512/256)
SHA-3 family (SHA3-224, SHA3-256, SHA3-384, and SHA3-512) | FIPS 180 [i.79] for SHA2
FIPS 202 [i.88] for SHA 3 | Hashing | Integrity of data | | -| | DRBGs (CTR_DRBG (AES), HMAC_DRBG (SHA-256), Hash_DRBG (SHA-256)) | NIST SP 800-90A [i.89]
NIST SP 800-90B [i.90]
NIST SP 800-90C [i.91] | Random Number Generation (RNG) | Cryptographic keys for encryption and digital signatures, random nonces for secure operations | | -| | System RNG

EXAMPLE: Linux getrandom(), /dev/urandom | For Linux: BSI [i.92] | | Unique instance IDs, secure entropy to seed DRBGs | | - -NOTE 1: ETM (Encrypt-then-MAC) is not specified for SSH yet is a widely used and recommended practice within the SSHv2 protocol, and broadly supported in available implementations, due to its security-related advantages. - -NOTE 2: BSI recommends phasing out by 2025 [i.33]. - -NOTE 3: The related authenticated encryption algorithm is defined in [i.34] - -NOTE 4: EAP-TLS is based on TLS 1.2 (see IETF RFC 5216 [i.45]) or TLS 1.3 (see IETF RFC 9190 [i.46]) - -NOTE 5: JWT is based on JWS and JWT (see IETF RFC 7519 [i.65]) - -NOTE 6: OAuth 2.0 is based on TLS, JWT, and JWE. - -NOTE 7: AUTH\_NONE MUST be supported as per IETF RFC 7296 [i.59] and IETF RFC 5282 [i.58] and MUST NOT be supported when ESP uses Authenticated Encryption with Associated Data (AEAD) cipher. - -NOTE 8: AUTH\_AES\_XCBC\_96 SHOULD be supported as per IETF RFC 3566 [i.51] and IETF RFC 7296 [i.59], and MAY be supported in case of Interoperability with IoT. - -NOTE 1: RADIUS with EAP-TLS is not covered in Table 5-1 as the use of quantum-safe TLS for EAP-TLS is sufficient to render RADIUS over EAP-TLS quantum-safe without altering the RADIUS protocol itself. - -NOTE 2: LDAP with STARTTLS is not covered in Table 5-1 as the use of quantum-safe TLS for STARTTLS is sufficient to render LDAP over STARTTLS quantum-safe without altering the LDAP protocol itself. - -# Annex: Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|--------------------------------------------------------------------------------------| -| 2025.02.04 | 00.01 | First draft | -| 2025.02.25 | 00.02 | Merged NOK-0244, NOK-0245 | -| 2025.03.04 | 00.03 | Merged NOK-0256 | -| 2025.04.01 | 00.04 | Merged NOK-0268 | -| 2025.04.14 | 00.05 | Merged SYM-0084, NIST.AO-0012, NIST-0013 | -| 2025.05.27 | 00.06 | Merged NEC-0056 | -| 2025.06.10 | 00.07 | Merged NIST-0018, NIST-0019 | -| 2025.06.23 | 00.08 | Adopted changes on NIST-0018 and NIST-0019 due to the ongoing review | -| 2025.07.09 | 01.00 | Published as Final version 01.00 | -| 2025.09.29 | 01.01 | Merged NEC.AO-0063, NEC-0064, NOK.AO-0308, NOK-0326 | -| 2025.10.13 | 01.02 | Fixed typo introduced through NEC.AO-0063, merged NOK.AO-0336 | -| 2025.10.14 | 01.03 | notes in table 5-1: space -> tab; R004 -> R005; merge some of the cells in table 5-1 | -| 2025.11.19 | 01.04 | set copyright year to 2026, aligned references to OFH-related documents in table 5-1 | -| 2025.11.25 | 02.00 | Published as Final version 02.00 | \ No newline at end of file diff --git a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.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/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.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/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/854df8ad60507803253274673f9062cf_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/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.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/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 82827af191c934857f3a5a97842fa19fb4aa5978..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:54f690c723a011f67b244eeda5cca1f67e7a7784e122d72a637cea1ca968c8f4 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_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/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_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/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG11/O-RAN.WG11.TR.PQC-Security.0-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.PQC-Security.0-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/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/doc.md b/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/doc.md deleted file mode 100644 index e52a3066375e5583dce66b0b09e1e8960c36d8a8..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/doc.md +++ /dev/null @@ -1,386 +0,0 @@ - - -# --- **O-RAN Work Group 11 (Security work group)****Study on Security Configuration Management** - -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 | -| 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..... | 6 | -| 4 SCM Background..... | 6 | -| 4.1 Introduction..... | 6 | -| 4.2 Considerations..... | 7 | -| 5 Study and identify the security gaps related to SCM ..... | 7 | -| 5.1 Assets ..... | 7 | -| 5.1.1 O-RAN Architecture Elements ..... | 7 | -| 5.1.2 O-RAN interfaces ..... | 7 | -| 5.2 Security Controls ..... | 8 | -| 5.3 Input recommendations..... | 8 | -| 5.4 Threat template ..... | 8 | -| 5.5 SCM Threats analysis ..... | 8 | -| 5.5.1 Certificate related threats ..... | 9 | -| 5.5.2 NACM related threats ..... | 10 | -| 5.5.3 LDAP related threats..... | 11 | -| 6 Study and recommendation related to SCM ..... | 12 | -| 7 Conclusion..... | 12 | -| Annex: Change history/Change request (history) ..... | 13 | - -# --- List of figures - -No table of figures entries found. - -# --- List of tables - -No table of figures entries found. - -# --- Foreword - -This Technical Report (TR) has been produced by WG11 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 main objective for this work item is to identify and develop the security management YANG models for O-RAN framework fulfilling the security requirements specified in [i.2]. The specification will be based on the YANG data modeling language (see RFC 7950). Security YANG models in O-RAN will apply to relevant O-RAN interfaces (O1, Open Fronthaul M-plane). This work item will perform the following steps, - -- Identify if there is any existing security management YANG model available in O-RAN specifications -- Study and recommend the security requirement for YANG model aligning with [i.2] -- Study and identify the gaps related to security configuration -- Study the YANG models for certificate configuration -- Study the YANG models for NETCONF access control such as NACM configuration -- Study the YANG models for LDAP configuration - -# 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] O-RAN.WG11.TS.SecProtSpec: "Security Protocols Specification". -- [i.2] O-RAN.WG11.TS.SRCS: "Security Requirements and Controls Specification". -- [i.3] O-RAN.WG11.TR.Threat-Modeling: "O-RAN Security Threat Modelling and Risk Assessment". -- [i.4] O-RAN.WG11.TS.STS: "O-RAN Security Test Specifications". -- [i.5] O-RAN.WG4.TS.MP: "Management Plane Specification". -- [i.6] IETF RFC 7950: "The YANG 1.1 Data Modeling Language". -- [i.7] O-RAN.WG10.TS.Information Model and Data Models: "O-RAN Information Model and Data Models Specification". -- [i.8] O-RAN.WG10.TS.O1NRM: "O1 Network Resource Model". -- [i.9] O-RAN.WG4.TS.CTI-TMP: "Cooperative Transport Interface Transport Management Procedures Specification". -- [i.10] O-RAN.WG5.O-DU-O1: "O1 Interface specification for O-DU". -- [i.11] O-RAN.WG5.O-CU-O1: "O1 Interface specification for O-CU-UP and O-CU-CP". -- [i.12] An extensible YANG validator and converter in python, . -- [i.13] O-RAN.WG1.TS.OAD: "O-RAN Architecture Description". -- [i.14] O-RAN.WG10.O1-Interface: "O-RAN Operations and Maintenance Interface Specification". - -# --- 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: - -**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 as specified in [i.13]. - -NOTE 1: Please refer to [i.5] for more details. - -**OI:** Interface used by the SMO framework, as specified in Clause 5.3.1, for operation and management of O-RAN NFs as specified in [i.13] [i.14]. - -**O-Cloud:** Cloud platform that provides O-RAN standardized interfaces, hosting O-RAN defined software components. - -**SMO:** A Service Management and Orchestration framework. - -NOTE 2: Please refer to Clause 5.3.1 for more details as specified in [i.13]. - -## 3.2 Symbols - -Void - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations [given in [i.1] and the following] apply: - -| | | -|---------|---------------------------------------| -| LDAP | Lightweight directory access protocol | -| NACM | NETCONF Access Control Model | -| NETCONF | Network Configuration Protocol | -| NF | Network Function | -| O-RAN | Open Radio Access Network | -| O-Cloud | O-RAN Cloud | -| PNF | Physical Network Function | -| SMO | Service Management and Orchestration | -| VNF | Virtualised Network Function | -| YANG | Yet Another Next Generation | - -# --- 4 SCM Background - -## 4.1 Introduction - -Management of security configuration is currently not handled in a consistent way in O-RAN. Different work groups see the topic in different ways. In some cases, this is expected to be a topic only for the security work group while in other cases it is defined within a work group. - -For example, there are YANG models related to NACM included in WG4 definitions for Open Fronthaul M-plane. For O1, there are security requirements on NACM stated in [i.2]. There may be other areas where security configuration such as LDAP configuration, NACM configuration, Certificate Management configuration is required. Some of the security requirements related to NACM, LDAP are defined in [i.2]. - -There are several discussions on O1 security configuration aspects such as NACM, etc happening across O-RAN WGs (WG11, W10, etc) showing a need to have Security Configuration Management specifications in O-RAN. - -## 4.2 Considerations - -This document makes the following considerations: - -- This TR performs a detailed study of the Security Configuration Management for O1 interface and Open Fronthaul M-plane. -- The existing O-RAN specifications such as O-RAN.WG10.Information Model and Data Models [i.7], O-RAN.WG10.O1NRM.1 [i.8], O-RAN.WG4.MP-YANGs [i.5], O-RAN.WG4.CTI-TMP-YANG [i.9], O-RAN.WG5.O-DU-O1.1 [i.10], O-RAN.WG5.O-CU-O1.0 [i.11] discuss the YANG models which are considered as the baseline specifications for the Security Configuration Management TR to identify and develop the security YANG models for O-RAN framework fulfilling the security requirements specified in [i.2]. -- The Security YANG model considers the rules and guideline as specified in O-RAN specifications [i.5] [i.7] [i.8] [i.9] [i.10] [i.11]. -- The pyang YANG validator tool is considered for evaluating the security YANG model as recommended in [i.12]. -- The recommended security YANG models for O1 interface provided in this report to be shared with the impacted O-RAN Alliance working group, such as WG4 and WG10. - -# --- 5 Study and identify the security gaps related to SCM - -## 5.1 Assets - -This document makes the following considerations: - -### 5.1.1 O-RAN Architecture Elements - -- ASSET-C-01: Logical module: Service Management and Orchestration (SMO) -- ASSET-C-02: Near-RT RIC software -- ASSET-C-03: O-CU-CP software -- ASSET-C-04: O-CU-UP software -- ASSET-C-05: O-DU software -- ASSET-C-06: O-RU software -- ASSET-C-07: O-eNB -- ASSET-C-31: Shared O-RU - -### 5.1.2 O-RAN interfaces - -- ASSET-C-22: O1 interface, including protocol stack -- ASSET-C-24: Open FH M-plane, including protocol stack - -## 5.2 Security Controls - -The following security controls should be considered for the security gap analysis: - -- Control-1: Certificate Management -- Control-2: TLS -- Control-3: mTLS -- Control-4: SSH -- Control-5: NACM with NETCONF -- Control-6: MACsec -- Control-7: IPsec -- Control-8: 802.1X - -## 5.3 Input recommendations - -The following are considered for security configuration management gap analysis: - -- Certificate configuration -- NETCONF access control, NACM configuration -- LDAP configuration - -## 5.4 Threat template - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------| -| Threat ID | O-RAN threat ID | -| Threat title | [Threat Title will include suitable reference of 3GPP/IETF/ETSI] | -| Threat description | Introduction about the threat | -| Threat type | Spoofing
Tampering
Repudiation
Information disclosure
Denial of Service
Elevation of Privilege | -| Vulnerability | TBD | -| Impact type | Authenticity
Integrity
Non-repudiation
Confidentiality
Availability
Authorization | -| Affected Assets | Asset identification | - -## 5.5 SCM Threats analysis - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SCM-GEN-01 | -| Threat title | Exploitation due to misconfigured security related configuration parameters | -| Threat description | A malicious actor may be able to change the security related configuration parameters of an O-RAN architectural element if administrator has not configured the parameters appropriately. | -| Threat type | Elevation of privilege | -| Vulnerability | Misconfiguration of security related configuration parameters. | -| Impact type | Authorization | -| Affected Asset | Logical module: Service Management and Orchestration (SMO) [ASSET-C-01],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05], | - -| | | -|--|-----------------------------------------------------------------------| -| | O-RU [ASSET-C-06],
O-eNB [ASSET-C-07],
Shared O-RU [ASSET-C-31] | -|--|-----------------------------------------------------------------------| - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SCM-GEN-02 | -| Threat title | Excessive NETCONF operation requests | -| Threat description | A malicious actor may be able to attempt excessive NETCONF operation requests to an O-RAN architectural element which may lead to service disruption. | -| Threat type | DoS | -| Vulnerability | Insufficient support to detect and handle excessive NETCONF operation requests | -| Impact type | Availability | -| Affected Asset | Logical module: Service Management and Orchestration (SMO) [ASSET-C-01],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-RU [ASSET-C-06],
O-eNB [ASSET-C-07],
Shared O-RU [ASSET-C-31] | - -### 5.5.1 Certificate related threats - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SCM-Cert-01 | -| Threat title | Configuration of incorrect Certificate parameter | -| Threat description | Certificate parameters may be misconfigured intentionally or unintentionally which may lead to the CA issuing a rogue certificate or the wrong certificate | -| Threat type | Denial of Service, Tampering | -| Vulnerability | It may lead to incorrect certificate being issued by the CA issuer | -| Impact type | Availability | -| Affected Asset | Logical module: Service Management and Orchestration (SMO) [ASSET-C-01],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-RU [ASSET-C-06],
O-eNB [ASSET-C-07],
Shared O-RU [ASSET-C-31] | - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SCM-Cert-02 | -| Threat title | Tampering of Certificate parameter | -| Threat description | If the certificate parameters are tampered or comprised by the malicious actor, which may lead to initiation of valid certificate request to CA by the attacker | -| Threat type | Denial of Service, Tampering | -| Vulnerability | Attackers may claim as trusted entity | -| Impact type | Confidentiality | - -| | | -|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | Authenticity
Availability | -| Affected Asset | Logical module: Service Management and Orchestration (SMO) [ASSET-C-01],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-RU [ASSET-C-06],
O-eNB [ASSET-C-07],
Shared O-RU [ASSET-C-31] | - -### 5.5.2 NACM related threats - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SCM-NACM-01 | -| Threat title | Exploitation of incorrectly implemented default access parameters for NACM | -| Threat description | A malicious actor may be able to access and perform NACM related configuration changes to an O-RAN architecture element if the vendor has not correctly implemented the default access parameters. | -| Threat type | Elevation of privilege | -| Vulnerability | Incorrect implementation of default access parameters | -| Impact type | Authorization | -| Affected Asset | Logical module: Service Management and Orchestration (SMO) [ASSET-C-01],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-RU [ASSET-C-06],
O-eNB [ASSET-C-07],
Shared O-RU [ASSET-C-31] | - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SCM-NACM-02 | -| Threat title | Unauthorized access to NACM configuration | -| Threat description | A malicious actor may be able to access NACM configuration which may allow the malicious actor to perform unauthorized operation in an O-RAN architecture element. | -| Threat type | Elevation of privilege | -| Vulnerability | Insufficient access protection for NACM configuration | -| Impact type | Authorization | -| Affected Asset | Logical module: Service Management and Orchestration (SMO) [ASSET-C-01],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-RU [ASSET-C-06],
O-eNB [ASSET-C-07],
Shared O-RU [ASSET-C-31] | - -| | | -|------------------|----------------------| -| Threat ID | T-SCM-NACM-03 | -|------------------|----------------------| - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat title | Unauthorized NETCONF operation requests | -| Threat description | A malicious actor may be able to perform the NETCONF operation requests or data store write requests without legitimate access rights to the O-RAN architecture elements. | -| Threat type | Elevation of privilege | -| Vulnerability | Improper authorization process and lack of re-validating the authorization requests | -| Impact type | Authorization | -| Affected Asset | Logical module: Service Management and Orchestration (SMO) [ASSET-C-01], Near-RT RIC [ASSET-C-02], O-CU-CP [ASSET-C-03], O-CU-UP [ASSET-C-04], O-DU [ASSET-C-05], O-RU [ASSET-C-06], O-eNB [ASSET-C-07], Shared O-RU [ASSET-C-31] | - -### 5.5.3 LDAP related threats - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SCM-LDAP-01 | -| Threat title | Abuse of LDAP configuration information | -| Threat description | A malicious actor may attempt to access the LDAP configuration information in an O-RAN architectural element and perform unauthorized modification of configuration information (i.e. delete data). | -| Threat type | Elevation of privilege | -| Vulnerability | Insufficient protection of LDAP configuration information | -| Impact type | Authorization | -| Affected Asset | Logical module: Service Management and Orchestration (SMO) [ASSET-C-01], Near-RT RIC [ASSET-C-02], O-CU-CP [ASSET-C-03], O-CU-UP [ASSET-C-04], O-DU [ASSET-C-05], O-RU [ASSET-C-06], O-eNB [ASSET-C-07], Shared O-RU [ASSET-C-31] | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SCM-LDAP-02 | -| Threat title | Compromise of LDAP configuration by illegitimate actor | -| Threat description | An illegitimate actor may attempt to compromise an O-RAN architectural element by modifying the LDAP service account used for LDAP binding. | -| Threat type | Elevation of privilege | -| Vulnerability | Insufficient validation for the legitimate actor | -| Impact type | Authorization | -| Affected Asset | Logical module: Service Management and Orchestration (SMO) [ASSET-C-01], Near-RT RIC [ASSET-C-02], O-CU-CP [ASSET-C-03], O-CU-UP [ASSET-C-04], O-DU [ASSET-C-05] | - -| | | -|--|-----------------------------------------------------------------------| -| | O-RU [ASSET-C-06],
O-eNB [ASSET-C-07],
Shared O-RU [ASSET-C-31] | -|--|-----------------------------------------------------------------------| - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SCM-LDAP-03 | -| Threat title | Compromise of LDAP session credentials | -| Threat description | A malicious actor may steal LDAP session credentials if an O-RAN architectural element is not configured correctly for securing the LDAP communication. | -| Threat type | Information Disclosure | -| Vulnerability | Misconfiguration related to secure LDAP communication | -| Impact type | Confidentiality | -| Affected Asset | Logical module: Service Management and Orchestration (SMO) [ASSET-C-01],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-RU [ASSET-C-06],
O-eNB [ASSET-C-07],
Shared O-RU [ASSET-C-31] | - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SCM-LDAP-04 | -| Threat title | Repeated failed operation while using valid service account | -| Threat description | A malicious actor may use reusable LDAP service account of an O-RAN architectural element and attempt to perform unauthorized operations repeatedly. This may lead to service disruption and necessary configuration changes in the O-RAN architecture element. | -| Threat type | Denial of service | -| Vulnerability | Insufficient protection for credentials | -| Impact type | Availability | -| Affected Asset | Logical module: Service Management and Orchestration (SMO) [ASSET-C-01],
Near-RT RIC [ASSET-C-02],
O-CU-CP [ASSET-C-03],
O-CU-UP [ASSET-C-04],
O-DU [ASSET-C-05],
O-RU [ASSET-C-06],
O-eNB [ASSET-C-07],
Shared O-RU [ASSET-C-31] | - -# 6 Study and recommendation related to SCM - -Editor's note: This clause will study and recommend the security requirements and security usecases related to security configuration management like NACM, Certificate and LDAP aligning with SRCS and SPS. - -Void - -# 7 Conclusion - -Editor's note : This clause will provide a summary for the SCM TR. - -Void - -# Annex: Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2025.01.28 | 00.00.01 | Skeleton proposal | -| 2025.03.11 | 00.02 | Approved CR in the month of feb and March 2025- Internal O-RAN release | -| 2025.03.12 | 00.03 | Feedback received during the SCM WI TR meeting [4] on 11/03/2025 | -| 2025.04.16 | 00.04 | Approved CR in the month of April 2025 during the SCM WI TR meeting | -| 2025.06.03 | 00.05 | Approved CR in the month of June 2025 during the SCM WI TR meeting | -| 2025.06.18 | 00.06 | Updated the TR based on comments received and CR approved till June 2025
ERI-2025.02.11-WG11-CR0207-SCM-Clause1_Scope-v02.docx
ERI-2025.02.11-WG11-CR0208-SCM-Clause2_Reference-v02.docx
ERI-2025.02.24-WG11-CR0213-SCM-Clause3.1_Terms-v03.docx
ERI-2025.02.24-WG11-CR0214-SCM-Clause3.3_Abbreviations-v01.docx
ERI-2025.02.25-WG11-CR0211-SCM-Clause4_Background-v03.docx
ERI-2025.02.25-WG11-CR0212-SCM-Clause4.1_Consideration-v03.docx
ERI-2025.04.09-WG11-CR0226-SCM-Clause5.1_assets-v03.docx
ERI-2025.04.09-WG11-CR0227-SCM-Clause5.2_SecurityControls-v04.docx
ERI-2025.04.09-WG11-CR0228-SCM-Clause5.3_Recommendation for Security Configuration Management-v03.docx
ERI-2025.05.07-WG11-CR0238-SCM-Clause5.4_Threats Template-v01.docx
ERI-2025.05.07-WG11-CR0239-SCM-Clause5.5_SCMThreatAnalysis-v01.docx
ERI-2025.05.21-WG11-CR0244-SCM-Clause5.5.1-CertificateRelatedThreats-v02.docx | -| 2025.10.30 | 01.01 | Updated the TR based on comments received and CR approved till October 2025
ERI.AO-2025.08.12-WG11-CR0250-SCM-Clause5.5.2-NACMrelatedthreats-v06.docx
ERI.AO-2025.08.12-WG11-CR0251-SCM-Clause5.5.3-LDAPrelatedthreats-v06.docx
ERI.AO-2025.08.27-WG11-CR0257-SCM-Clause5.5.3-LDAPrelatedthreats_2-v06.docx
ERI.AO-2025.09.09-WG11-CR0261-SCM-Clause5.5-Configurationthreat-v05.docx
NEC-2025.10.22-WG11-CR-0072-SCM-ReferenceUpdate-v01.docx | \ No newline at end of file diff --git a/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 4b94da934e2c8c85c0123640346015b174f8dc14..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:53785b160680d7d75d469ea49f0daf5b5a3522fbee704e81dcd409934e1d112e -size 4601 diff --git a/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_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/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.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/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/83ee9f10bd3636e192d68decf7f04cec_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/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_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/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SCM.0-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/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_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/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SCM.0-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/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_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/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG11/O-RAN.WG11.TR.SCM.0-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SCM.0-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/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/doc.md b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/doc.md deleted file mode 100644 index 90613e7a0b24e4c04fd137c321f4ffad10ff48da..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/doc.md +++ /dev/null @@ -1,1154 +0,0 @@ - - -# --- **O-RAN Work Group 11 (Security Work Group)** - -# **Study on Security for Service Management and Orchestration (SMO)** - -# --- Contents - -| | | -|-----------------------------------------------------------------|----| -| Foreword..... | 3 | -| Modal verbs terminology ..... | 3 | -| 1 Scope..... | 4 | -| 2 References..... | 5 | -| 3 Definitions of terms, symbols, and abbreviations..... | 7 | -| 3.1 Terms..... | 7 | -| 3.2 Symbols..... | 8 | -| 3.3 Abbreviations ..... | 8 | -| 4 SMO Assets..... | 10 | -| 4.1 Architecture..... | 10 | -| 4.2 Functions ..... | 11 | -| 4.3 Applications ..... | 11 | -| 4.4 Interfaces ..... | 11 | -| 4.5 Information..... | 12 | -| 4.6 SMO Services (SMOS)..... | 12 | -| 5 Threats..... | 14 | -| 5.1 Threat Model..... | 14 | -| 5.2 Threat Template ..... | 14 | -| 5.3 Potential Threats and Exploits..... | 15 | -| 5.4 SMO Threats ..... | 16 | -| 6 Threat Analysis ..... | 18 | -| 6.1 General SMO Threats..... | 18 | -| 6.2 Threats at O2 interface ..... | 22 | -| 6.3 Threats at External interfaces..... | 24 | -| 6.4 Threats Targeting SME..... | 26 | -| 6.5 Preliminary Threat Analysis for RAN-Core Data Sharing ..... | 26 | -| 6.6 Threats Targeting DME ..... | 27 | -| 7 Security Controls..... | 28 | -| 8 Risk Assessment ..... | 30 | -| 8.1 General SMO Risks..... | 30 | -| 8.2 Threats at O2 interface ..... | 31 | -| 8.3 Threats at External Interfaces..... | 32 | -| 8.4 Threats Targeting SME ..... | 33 | -| 9 Primary Security Issues..... | 34 | -| 10 Recommendations..... | 35 | -| Annex: Change history/Change request (history) ..... | 37 | - -# Foreword - -This Technical Report (TR) has been produced by WG11 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 - -This technical report provides the threat model and risk assessment for the SMO. The report identifies threats and risks and recommends potential security controls to protect against those threats through safeguards or mitigation. - -The steps of the threat modelling process are as follows: - -1. Identify assets: Identify the assets of the SMO that must be protected. -2. Identify threats: Identify the threats that could adversely impact the SMO and threats that can use the SMO to adversely impact other components of the O-RAN system. -3. Identify the attack surface and attack vectors: Identify the points in the SMO where an attacker could - - a. gain entry to the SMO - - b. gain entry to another O-RAN system through the SMO - - c. exploit a vulnerability or misconfiguration - - d. compromise the system or its data. -4. Measure risk: The extent to which confidentiality, integrity, or availability is threatened, based upon a risk-based analysis considering the impact level resulting from an attack and the likelihood of occurrence. -5. Recommend controls: The management, operational, and technical controls for an information system to protect the confidentiality, integrity and availability of the SMO and its information. - -This Technical Report makes the following considerations: - -- The attack surface of the SMO includes its interfaces, functions, and data. Data-at-rest, Data-in-motion, and Data-in-use must be considered. -- O-RAN Alliance WG1 is in the process of defining an architecture for a decoupled SMO. This will influence the set of assets to be protected. -- The O-RAN Alliance is pursuing a zero-trust architecture (ZTA) for its specifications based upon NIST SP 800-207 [i.8]. This will affect the risk scoring. -- Security controls are recommended for specifications of the SMO. The recommended controls provided in this report will be shared with the responsible O-RAN Alliance working group, such as WG1 and WG10, so that the appropriate specification relevant to the recommendation can be updated. -- Some of the identified SMO assets may already be in scope for separate ongoing WG11 security work items. The SMO security Technical Report work item may inform those work items. - -# 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] O-RAN.TSC.ODR: "O-RAN Document Drafting Rules (ODR)". -- [i.2] O-RAN.WG1.TS.OAD: "O-RAN Architecture Description (OAD)". -- [i.3] O-RAN ALLIANCE TS: "O-RAN Non-Real-Time RAN Intelligent Controller". -- [i.4] O-RAN.WG11.TS.SecProtSpec: "O-RAN Security Protocols Specifications". -- [i.5] O-RAN.WG11.TS.SRCS: "O-RAN Security Requirements and Controls Specifications". -- [i.6] O-RAN.WG11.TR.Threat-Modeling: "O-RAN Threat Modelling and Risk Assessment". -- [i.7] O-RAN.WG11.TS.STS: "O-RAN Security Test Specifications". -- [i.8] Zero Trust Architecture, NIST SP 800-207, NIST, August 2020, . -- [i.9] US National Security Agency (NSA) / Cybersecurity and Infrastructure Security Agency (CISA), Security Guidance for 5G Cloud Infrastructures, Part I, Oct 28, 2021, Part II, Nov 18, 2021, Part III, Dec 2, 2021, Part IV, Dec 16, 2021. (as of Feb 28, 2022). -- [i.10] Not used. -- [i.11] Not used. -- [i.12] OWASP Top 10 Web Application Security Risks, 2021, . -- [i.13] Cloud Security Alliance (CSA), Top Threats to Cloud Computing: Egregious Eleven, 2019, . -- [i.14] Cloud Security Alliance (CSA), Top Threats to Cloud Computing: Pandemic Eleven, 2022, . -- [i.15] OWASP Top 10 Proactive Controls, 2021, -- [i.16] Center for Internet Security (CIS) Critical Security Controls, -- [i.17] Cloud Security Alliance (CSA) Cloud Control Matrix (CCM), -- [i.18] ISO/IEC 27001:2013 Information Security Management System (ISMS). - -[i.19] NIST SP 800-53r5, Security and Privacy Controls for Information Systems and Organizations, 2020. - -[i.20] O-RAN.SFG.Non-RT-RIC-Security-TR: Study on Security for Non-RT-RIC - -[i.21] O-RAN.WG1.TR,Decoupled-SMO-Architecture: Decoupled SMO Architecture - -[i.22] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications", Release 18. - -[i.23] Cloud Security Alliance (CSA), [Top Threats to Cloud Computing 2024](https://cloudsecurityalliance.org/artifacts/top-threats-to-cloud-computing-2024), - - - -# 3 Definitions of terms, symbols, and abbreviations - -## 3.1 Terms - -This document uses the verbal forms for the expression of provisions as defined in O-RAN Document Drafting Rules (ODR) [i.1] - -This document uses the term Zero Trust Architecture (ZTA) as defined by US NIST in [i.8] and applied to 5G cloud deployments by US CISA in [i.9]. - -A ZTA provides protection from external and internal threats, assuming the following: - -1. there is no implicit trust granted to an asset based upon ownership, physical location, or network location [i.8] -2. the adversary is already inside the network. Perimeter defenses are no longer sufficient to secure a network, and there should always be an assumption that a threat actor has established a foothold in the network [i.9] - -This document uses the term “attack surface” defined by US NIST as - -*The set of points on the boundary of a system, a system element, or an environment where an attacker can try to enter, cause an effect on, or extract data from, that system, system element, or environment* -[[https://csrc.nist.gov/glossary/term/attack\\_surface](https://csrc.nist.gov/glossary/term/attack_surface)] - -This document refers to “sensitive information” defined by US NIST as - -*information whose loss, misuse, or unauthorized access or modification could adversely affect security* -[] - -For the purposes of the present document, the terms and definitions provided in [i.2] apply: - -**A1 Interface:** 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. - -**External Interface:** The interface between the SMO and an External System. - -**External System:** A digital entity outside the O-RAN domain that is a consumer or producer for SMO Services. - -**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. It may include AI/ML (Artificial Intelligence / Machine Learning) workflow including model training, inference and updates. - -**Non-RT RIC:** O-RAN Non-Real-Time RAN Intelligent Controller: A logical function within SMO that drives the content carried across the A1 interface. It is comprised of the Non-RT RIC Framework and the Non-RT RIC Applications (rApps) whose functions are defined below. - -**Non-RT RIC Applications (rApps):** Modular applications that leverage the functionality exposed via the Non-RT RIC Framework’s R1 interface to provide added value services relative to RAN operation, such as driving the A1 interface, recommending values and actions that may be subsequently applied over the O1/O2 interface and generating “enrichment information” for the use of other rApps. The rApp functionality within the Non-RT RIC enables non-real-time control and optimization of RAN elements and resources and policy-based guidance to the applications/features in Near-RT RIC. - -**Non-RT RIC Framework:** That functionality internal to the SMO that logically terminates the A1 interface to the Near-RT RIC and exposes to rApps, via its R1 interface, the set of internal SMO services needed for their runtime processing. The Non-RT RIC Framework functionality within the Non-RT RIC provides AI/ML workflow including model training, inference and updates needed for rApps. - -**R1 Interface:** Interface between rApps and Non-RT RIC Framework via which R1 Services can be produced and consumed. - -**R1 Services:** A collection of services including, but not limited to, service registration and discovery services, authentication and authorization services, AI/ML workflow services, and A1, O1 and O2 related services. - -**Service Management and Exposure (SME):** A SMOS which enables services applicable to any entities within the SMO that fulfil the roles of SMO Service Producer and/or SMO Service Consumer. - -**Service Management and Orchestration (SMO):** The O-RAN Service Management and Orchestration system as specified in the O-RAN Architecture Description (OAD) document [i.2], Clause 5.3.1. - -**Service Management and Orchestration Function (SMOF):** Internal SMO entities which provide one or more SMO Services. - -**Service Management and Orchestration Service (SMOS):** Set of management, orchestration and automation capabilities offered by a SMO Function. - -**SMOS Communication:** Communication support between SMOS Producers and SMOS Consumers. - -## 3.2 Symbols - -None - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [i.22] and the following apply: - -| | | -|-------|------------------------------------------------| -| ABAC | Attribute Based Access Control | -| AI | Artificial Intelligence | -| CM | Configuration Management | -| DAR | Data at Rest | -| DIM | Data in Motion | -| DIU | Data in Use | -| DME | Data Management and Exposure | -| EI | Enrichment Information | -| eNB | eNodeB (applies to LTE) | -| FM | Fault Management | -| FOCOM | Federated O-Cloud Orchestration and Management | -| FTP | File Transfer Protocol | -| FTPS | File Transfer Protocol Secure | -| gNB | gNodeB (applies to NR) | -| HTTP | Hypertext Transfer Protocol | - -| | | -|-------|---------------------------------------------| -| HTTPS | Hypertext Transfer Protocol Secure | -| JSON | JavaScript Object Notation | -| KPI | Key Performance Indicator | -| KQI | Key Quality Indicator | -| ML | Machine Learning | -| MNO | Mobile Network Operator | -| NF | Network Function | -| NFO | Network Function Orchestrator | -| OAD | O-RAN Architecture Description | -| OAM | Operations, Administration, and Maintenance | -| OWASP | Open Worldwide Application Security Project | -| PBAC | Policy Based Access Control | -| PII | Personally Identifiable Information | -| PKI | Public Key Infrastructure | -| PM | Performance Management | -| PMI | Performance Management and Information | -| PTP | Precision Timing Protocol | -| RBAC | Role-based Access Control | -| REST | Representational State Transfer | -| RIC | RAN Intelligent Controller | -| RT | Real-Time | -| SA | Service and Subnet Slice Assurance | -| SBA | Service-Based Architecture | -| SME | Service Management and Exposure | -| SMO | Service Management and Orchestration | -| SMOF | SMO Functions | -| SMOS | SMO Services | -| SO | Service and Subnet Slice Orchestration | -| SSH | Secure Shell | -| TBAC | Task Based Access Control | -| TCP | Transmission Control Protocol | -| TE&IV | Topology Exposure and Inventory | -| TLS | Transport Layer Security | -| ZTA | Zero Trust Architecture | - -# 4 SMO Assets - -## 4.1 Architecture - -There are security risks with the SMO due to its internal functions and internal and external interfaces. Securing the SMO is imperative because it is responsible for all service management and orchestration. A security vulnerability within the SMO could be exploited to serve as an entry point for attacks against O-RAN components and lateral movement across O-RAN. SMO assets identification, threat identification, and risk analysis are performed using the SMO architecture diagram shown in the O-RAN Architecture Description (OAD) document [i.21]. - -The following SMO assets need to be protected: - -- SMO Framework -- SMO Functions (SMOF) -- Non-RT RIC -- SMO Services (SMOS) - - Service Management and Exposure (SME) - - Data Management and Exposure (DME) - - Topology Exposure and Inventory (TE&IV) - - Network Function Orchestrator (NFO) - - Federated O-Cloud Orchestration and Management (FOCOM) - - RAN NF OAM - - Software Package Onboarding - - Service and Subnet Slice Orchestration (SO) - - Service and Subnet Slice Assurance (SA) - - RAN Analytics - - Policy Management and Information (PMI) - - AI/ML Workflow - - A1 Related - - rApp Management -- SMOS Communication -- O1, O2, R1 and A1 interfaces -- Open Fronthaul M-Plane - -- External interfaces -- User Management interfaces -- PKI -- Logging -- Data -- AI/ML models, algorithms, and methods - -## 4.2 Functions - -The following SMO assets should be considered in a risk analysis: - -- ASSET-C-01: SMO Framework -- ASSET-C-11: Non-RT RIC -- ASSET-C-18: SMO Functions (SMOF) -- ASSET-C-44 thru ASSET-C-61: SMO Services (SMOS) - -## 4.3 Applications - -The following SMO applications should be considered in a risk analysis: - -- ASSET-C-10: rApps - -## 4.4 Interfaces - -The following SMO interfaces should be considered in a risk analysis: - -- ASSET-C-14: A1 -- ASSET-C-16: R1 -- ASSET-C-26: External Interfaces -- ASSET-C-22: O1 -- ASSET-C-23: O2 -- ASSET-C-24: OFH M-Plane -- ASSET-C-62: SMOS Communication - -## 4.5 Information - -The following SMO information and data should be considered in a risk analysis: - -- O1 Data - - ASSET-D-03: O1 Critical management plane data - - ASSET-D-09: O1 informational data -- O2 Data - - ASSET-D-12: O2-IMS and O2-DMS data - - ASSET-D-13: O2 Telemetry data - - ASSET-D-14: O2 cloud provisioning data -- Secret Stores - - ASSET-D-16: X.509 certificates - - ASSET-D-17: Private keys - - ASSET-D-20: Administrator credentials (passwords and tokens) -- AI/ML Data - - ASSET-D-25: Training or test data: data sets collected externally or internally from the Near-RT RIC, O-CU and O-DU and passed to the ML training hosts in a ML system. - - ASSET-D-26: The trained ML model which includes intellectual property, numerous configured hyperparameters and millions of learned parameters. - - ASSET-D-27: The ML prediction results built into the model (e.g. expected outcomes) - - ASSET-D-28: The behavior of the ML system including tasks for data collection, data wrangling, pipeline management, model retraining, and model deployment. -- PII - - ASSET-D-30: O-RAN specific UE IDs -- Event logs - - ASSET-D-29: Security event log files generated by O-RAN components - -## 4.6 SMO Services (SMOS) - -The following SMO Services should be considered in a risk analysis: - -- ASSET-C-44: Service Management and Exposure (SME) - -- ASSET-C-45: Data Management and Exposure (DME) -- ASSET-C-46: Topology Exposure and Inventory (TE&IV) -- ASSET-C-47: rApp Management -- ASSET-C-48: Void -- ASSET-C-49: Network Function Orchestrator (NFO) -- ASSET-C-50: Federated O-Cloud Orchestration and Management (FOCOM) -- ASSET-C-51: RAN NF OAM -- ASSET-C-52: Void -- ASSET-C-53: Void -- ASSET-C-54: AI Related -- ASSET-C-55: Policy Management and Information (PMI) -- ASSET-C-57: Software Package Onboarding -- ASSET-C-58: Service and Subnet Slice Orchestration -- ASSET-C-59: Service and Subnet Slice Assurance -- ASSET-C-60: RAN Analytics -- ASSET-C-61: AI/ML Workflow - -# --- 5 Threats - -## 5.1 Threat Model - -For identifying threats, we are using STRIDE: - -1. S - Spoofing identity. A user, application or program can masquerade as another to gain advantages not typically allowed for that user, application, or program. -2. T - Tampering with data. This involves the malicious modification of data, including making unauthorized changes to a database and alteration of data as it flows between computers. -3. R - Repudiation. A user or program refuses the authenticity of a good or reasonable command or action. -4. I - Information disclosure. This involves the exposure of information to individuals with unauthorized access to it. For example, users gain the ability to read a file that they normally would not have been granted access to, or an intruder can read data in transit between computers. -5. D - Denial of service. These attacks deny service to valid users, such as making a website unavailable or unusable by flooding it with illegitimate requests to keep legitimate users without access. -6. E - Elevation of privileges. An unauthorized user gains privileged rights to access previously no granted to compromise or destroy the system, such as a change in membership. - -| Threat types | Impact types | -|------------------------|-----------------| -| Spoofing | Authenticity | -| Tampering | Integrity | -| Repudiation | Non-repudiation | -| Information disclosure | Confidentiality | -| Denial of Service | Availability | -| Elevation of Privilege | Authorization | - -## 5.2 Threat Template - -Template to present the threat characteristics: - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------| -| Threat ID | | -| Threat title | | -| Threat description | | -| Threat type | Spoofing
Tampering
Repudiation
Information disclosure
Denial of Service
Elevation of Privilege | -| Vulnerabilities | | -| Impact type | Authenticity
Integrity
Non-repudiation
Confidentiality
Availability
Authorization | -| Affected Assets | | - -v08.00 - -## 5.3 Potential Threats and Exploits - -A threat analysis is facilitated by an understanding of potential threats, as identified by the Cloud Security Alliance (CSA) and the Open Web Application Security Project (OWASP). - -The OWASP Top 10 Web Application Security Risks [i.12] was updated in 2021 to include the following: - -- A01:2021 Broken Access Control -- A02:2021 Cryptographic Failure -- A03:2021 Injection (including Cross-Site Scripting) -- A04:2021 Insecure Design -- A05:2021 Security Misconfiguration -- A06:2021 Vulnerable and Outdated Components -- A07:2021 Identification and Authentication Failures -- A08:2021 Software and Data Integrity Failures (including Insecure Deserialization) -- A09:2021 Security Logging and Monitoring Failures -- A10:2021 Server-Side Request Forgery - -The CSA Top Threats to Cloud in 2019 was labelled the “Egregious Eleven” [i.13], as listed below: - -1. Data Breaches -2. Misconfiguration and Inadequate Change Control -3. Lack of Cloud Security Architecture and Strategy -4. Insufficient Identity, Credential, Access, and Key Management -5. Account Hijacking -6. Insider Threat -7. Insecure Interfaces and APIs -8. Weak Control plane -9. Metastructure and Applistructure Failures -10. Limited Cloud Usage Visibility -11. Abuse and Nefarious Uses of Cloud Services - -The CSA updated its list of top threats to cloud in 2022 and renamed it the “Pandemic Eleven” [i.14], as listed below: - -1. Insufficient Identity, Credential, Access and Key Management, Privileged Accounts -2. Insecure Interfaces and APIs -3. Misconfiguration and Inadequate Change Control -4. Lack of Cloud Security Architecture and Strategy -5. Insecure Software Development -6. Unsecure Third-Party Resources -7. System Vulnerabilities -8. Accidental Cloud Data Disclosure -9. Misconfiguration and Exploitation of Serverless and Container Workloads -10. Organized Crime, Hackers & APT -11. Cloud Storage Data Exfiltration - -The CSA updated its list of Top Threats to Cloud Computing 2024 [i.23], as listed below: - -1. Misconfiguration and inadequate change control -2. Identity and Access Management -3. Insecure interfaces and APIs -4. Inadequate selection/implementation of cloud security strategy -5. Insecure third-party resources -6. Insecure software development -7. Accidental cloud disclosure -8. System vulnerabilities -9. Limited cloud visibility/observability -10. Unauthenticated resource sharing -11. Advanced Persistent Threats - -## 5.4 SMO Threats - -The threats listed in clause 5.3 relevant to O-RAN and SMO are considered in the SMO threat analysis. The threats to SMO shown in Table 5.4.1 have been identified and are analyzed in clause 6 – Threat Analysis. - -Table 5.4.1 – SMO Threats Summary - -| Threat-Id | Threat Description (Brief) | -|---------------------------------------|-------------------------------------------------------------------------------------------------------------------| -| General SMO Threats | | -| T-SMO-01 | External attacker exploits authentication weakness on SMO | -| T-SMO-02 | External attacker exploits authorization weakness on SMO | -| T-SMO-03 | External Overload DoS attack targeted at SMO | -| T-SMO-04 | Internal attacker exploits authentication weakness on a SMOS | -| T-SMO-05 | Internal attacker exploits authorization weakness on SMO | -| T-SMO-06 | Internal Overload DoS attack targeted at SMOS | -| T-SMO-07 | Internal DoS attack disables internal SMOS or SMO process(es) | -| T-SMO-08 | Attacker exploits insecure API to gain access to SMO | -| T-SMO-09 | Sensitive data in motion is exposed to an internal attacker | -| T-SMO-10 | Sensitive data at rest is exposed to an internal attacker | -| T-SMO-11 | AI/ML poisoning by internal attacker | -| T-SMO-12 | AI/ML exposure on external entity | -| T-SMO-13 | Malicious actor views local logs | -| T-SMO-14 | Malicious actor modifies local log entries | -| T-SMO-15 | Malicious actor deletes local logs | -| T-SMO-16 | Malicious actor intercepts exports of local logs | -| T-SMO-17 | Malicious external actor gains unauthorized access to logs | -| T-SMO-18 | Malicious internal actor gains authorized access to logs | -| Threats at O2 interface | | -| T-SMO-19 | Internal attacker exploits O2 interface to view data in transit between SMO and O-Cloud | -| T-SMO-20 | Internal attacker exploits O2 interface to modify data in transit between SMO and O-Cloud | -| T-SMO-21 | Internal attacker uses O2 interface via SMO to exploit API vulnerability to gain access to O-Cloud infrastructure | -| T-SMO-22 | Internal attacker floods O2 interface via SMO to cause DDoS on O-Cloud infrastructure | -| T-SMO-23 | External attacker uses O2 interface via O-Cloud to exploit API vulnerability to gain access to SMO | -| T-SMO-24 | External attacker floods O2 interface via O-Cloud to cause DDoS on SMO | -| T-SMO-25 | External attacker uses O2 interface via O-Cloud to gain authorized access to sensitive data-at-rest at the SMO | -| Threats at External interfaces | | -| T-SMO-26 | External attacker exploits External interface to view data in transit between SMO and external service | -| T-SMO-27 | External attacker exploits External interface to modify data in transit between SMO and external service | -| T-SMO-28 | External attacker uses External interface to exploit API vulnerability to gain access to SMO | -| T-SMO-29 | External attacker floods External interface to cause DDoS at SMO | -| T-SMO-30 | External attacker uses External interface to gain access to sensitive data-at-rest at the SMO | -| T-SMO-31 | External attacker poisons External AI/ML data to corrupt SMO | -| T-SMO-32 | External attacker poisons External Enrichment Information data sources to corrupt SMO | -| T-SMO-33 | rApp floods SME | - -v08.00 - -| | | -|----------|------------------------------| -| T-SMO-34 | External Consumer floods SME | -| T-SMO-35 | SMOS flood SME | -| T-SMO-36 | rApp floods DME | -| T-SMO-37 | External Consumer floods DME | -| T-SMO-38 | SMOS flood DME | - -# 6 Threat Analysis - -SMO threats are identified in the tables below. External and internal threats are from the perspective of the SMO. External Threats are external to the SMO and Internal Threats are internal the SMO. This clause provides threat analysis of four types of SMO threats: - -- General SMO Threats -- Threats at O2 interface -- Threats at External interfaces -- Threats targeting SME -- Threats targeting DME - -## 6.1 General SMO Threats - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-01 | -| Threat title | External attacker exploits authentication weakness on SMO | -| Threat description | An external attacker can exploit the improper/missing authentication weakness on SMOS. If the authentication of O-RAN subjects on A1, O1, O2, and External interfaces on SMO is not supported or not properly implemented, those interfaces without proper credentials could be exploited to gain access to the SMO. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | SMO and all SMOS's | - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-02 | -| Threat title | External attacker exploits authorization weakness on SMO | -| Threat description | An external attacker can exploit the improper/missing authorization weakness on SMOS. A malicious external entity on A1, O1, O2, and External interfaces without authorization or with an incorrect access token may invoke the SMOS. The data at rest related to that function will be leaked to the attacker. In addition, an attacker can be able to perform certain actions, e.g. disclose O-RAN sensitive information or alter O-RAN components. | -| Threat type | Elevation of Privilege, Information Disclosure | -| Impact type | Authorization. Confidentiality | -| Affected Asset | SMO and all SMOS's | - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-03 | -| Threat title | External Overload DoS attack targeted at SMO | -| Threat description | Overload situation could appear in the case of DoS attack or increased traffic on externally facing interfaces. Inability to mitigate traffic volumetric attacks on an external interface affects availability of SMO data and SMOS. | -| Threat type | Denial of Service | - -v08.00 - -| | | -|-----------------------|--------------------| -| Impact type | Availability | -| Affected Asset | SMO and all SMOS's | - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-04 | -| Threat title | Internal attacker exploits authentication weakness on a SMOS | -| Threat description | An internal attacker can exploit the improper/missing authentication weakness on SMOS. If the authentication of internal interfaces on SMO is not supported or not properly implemented, those interfaces without credentials could be exploited to gain access to the SMO. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | SMO and all SMOS's | - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-05 | -| Threat title | Internal attacker exploits authorization weakness on SMO | -| Threat description | An internal attacker can exploit the improper/missing authorization weakness on SMOS. Malicious internal entities without authorization or with an incorrect access token may invoke the SMOS. The data at rest could be leaked to the attacker. In addition, an attacker can be able to perform certain actions, e.g. disclose O-RAN sensitive information or alter O-RAN components. | -| Threat type | Elevation of Privilege, Information Disclosure | -| Impact type | Authorization | -| Affected Asset | SMO and all SMOS's | - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-06 | -| Threat title | Internal Overload DoS attack targeted at SMOS | -| Threat description | Overload situation could appear in the case of DoS attack or increased traffic on internal SMO interfaces. Inability to mitigate traffic volumetric attacks on an external interface affects availability of SMO data and SMOS. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | SMO and all SMOS's | - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-07 | -| Threat title | Internal DoS attack disables internal SMOS or SMO process(es) | -| Threat description | Internal malicious actor exploits a vulnerability or escalates privilege to execute a DoS attack by disabling one or more SMO processes or SMOS. Inability to detect and report such events affects availability of SMOS. | -| Threat type | Denial of Service, Escalation of Privilege | -| Impact type | Availability | - -v08.00 - -| | | -|-----------------------|--------------------| -| Affected Asset | SMO and all SMOS's | -|-----------------------|--------------------| - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-08 | -| Threat title | Attacker exploits insecure API to gain access to SMO | -| Threat description | An insecure API may allow access to a system for an attacker to conduct remote code execution or an advanced persistent threat | -| Threat type | Tampering, Information Disclosure, Escalation of Privilege | -| Impact type | Integrity, Confidentiality, Authorization | -| Affected Asset | SMO | - -| | | -|---------------------------|---------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-09 | -| Threat title | Sensitive data in motion is exposed to an internal attacker | -| Threat description | Unprotected data transferred between internal SMOS is disclosed to an internal threat actor | -| Threat type | Information Disclosure | -| Impact type | Confidentiality | -| Affected Asset | SMO and all SMOS's | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-10 | -| Threat title | Sensitive data at rest is exposed to an internal attacker | -| Threat description | Unprotected data stored on the SMO is disclosed to an internal threat actor that has gain authorized access through privilege escalation | -| Threat type | Information Disclosure | -| Impact type | Confidentiality | -| Affected Asset | SMO | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-11 | -| Threat title | AI/ML poisoning by internal attacker | -| Threat description | Internal attacker gains authorized access exploited to poison AI/ML training data or the AI/ML models stored in the SMO to influence insights. | -| Threat type | Tampering | -| Impact type | Integrity | -| Affected Asset | SMO | - -| | | -|------------------|----------| -| Threat ID | T-SMO-12 | -|------------------|----------| - -v08.00 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat title | AI/ML exposure on external entity | -| Threat description | An external attacker can gain access to external entities to view or modify sensitive data AI/ML data, or models, transferred between the external function and SMO via external interfaces (e.g., EI, Human-Machine, A1, O1) | -| Threat type | Information disclosure, Tampering | -| Impact type | Confidentiality, Integrity | -| Affected Asset | SMO | - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-13 | -| Threat title | Malicious actor views local logs | -| Threat description | Malicious actor accesses locally stored logs in the SMO to perform reconnaissance to collect sensitive or private information. | -| Threat type | Information disclosure | -| Impact type | Confidentiality | -| Affected Asset | SMO | - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-14 | -| Threat title | Malicious actor modifies local log entries | -| Threat description | Malicious actor accesses locally stored logs in the SMO to modify entries to hide presence or cause confusion. | -| Threat type | Tampering | -| Impact type | Integrity | -| Affected Asset | SMO | - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-15 | -| Threat title | Malicious actor deletes local log entries | -| Threat description | Malicious actor accesses locally stored logs in the SMO to delete entries to hide presence or cause confusion. | -| Threat type | Tampering | -| Impact type | Integrity | -| Affected Asset | SMO | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-16 | -| Threat title | Malicious actor intercepts exports of local logs | -| Threat description | Malicious actor gains access to an external interface to intercept data in motion as logs are transferred from the SMO to a remote server/external entity. | -| Threat type | Information disclosure | - -v08.00 - -| | | -|-----------------------|-----------------| -| Impact type | Confidentiality | -| Affected Asset | SMO | - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-17 | -| Threat title | Malicious external actor gains unauthorized access to logs | -| Threat description | Malicious external actor gains unauthorized access to stored logs to view, modify, and delete | -| Threat type | Elevation of Privilege | -| Impact type | Confidentiality | -| Affected Asset | SMO | - -| | | -|---------------------------|----------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-18 | -| Threat title | Malicious internal actor gains authorized access to logs | -| Threat description | Malicious internal actor gains authorized access to stored logs to view, modify, and delete. | -| Threat type | Elevation of Privilege | -| Impact type | Authorization | -| Affected Asset | SMO | - -## 6.2 Threats at O2 interface - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-19 | -| Threat title | Internal attacker exploits O2 interface to view data in transit between SMO and O-Cloud | -| Threat description | If the O2 interface is not properly confidentiality protected, an internal attacker can perform a man-in-the-middle attack to view data in transit. | -| Threat type | Information disclosure | -| Impact type | Confidentiality | -| Affected Asset | O2 interface | - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-20 | -| Threat title | Internal attacker exploits O2 interface to modify data in transit between SMO and O-Cloud | -| Threat description | If the O2 interface is not properly integrity protected, an internal attacker can perform a man-in-the-middle attack to modify data in transit. | -| Threat type | Tampering | -| Impact type | Integrity | - -v08.00 - -| | | -|-----------------------|--------------| -| Affected Asset | O2 interface | -|-----------------------|--------------| - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-21 | -| Threat title | Internal attacker uses O2 interface via SMO to exploit API vulnerability to gain access to O-Cloud infrastructure | -| Threat description | If the O2 interface uses an API with a known vulnerability that is not properly protected or patched, an attacker can exploit it to gain access to the O-Cloud infrastructure from the SMO. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | O-Cloud | - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-22 | -| Threat title | Internal attacker floods O2 interface via SMO to cause DDoS on O-Cloud infrastructure | -| Threat description | If the O2 interface is not protected, an internal attacker on the SMO can flood the O2 interface to overload the O-Cloud. This can prevent legitimate messages from reaching the O-Cloud or cause heavy processing at the O-Cloud, resulting in performance degradation. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | O-Cloud | - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-23 | -| Threat title | External attacker uses O2 interface via O-Cloud to exploit API vulnerability to gain access to SMO | -| Threat description | If the O2 interface uses an API with a known vulnerability that is not properly protected or patched, an attacker can exploit it to gain access to the SMO from the O-Cloud infrastructure. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | SMO | - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-24 | -| Threat title | External attacker floods O2 interface via O-Cloud to cause DDoS on SMO | -| Threat description | If the O2 interface is not protected, an external attacker in the O-Cloud can flood the O2 interface to overload the SMO. This can prevent legitimate messages from reaching the SMO or cause heavy processing at the SMO, resulting in performance degradation or outage of the SMO. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | SMO | - -v08.00 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-25 | -| Threat title | External attacker uses O2 interface via O-Cloud to gain authorized access to sensitive data-at-rest at the SMO | -| Threat description | If the SMO is not protected, an external attacker at the O-Cloud can use the O2 interface to gain authorized access to the SMO to view data-at-rest. | -| Threat type | Elevation of Privilege | -| Impact type | Authorization | -| Affected Asset | SMO | - -## 6.3 Threats at External interfaces - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-26 | -| Threat title | External attacker exploits External interface to view data in transit between SMO and external service | -| Threat description | If an External interface is not properly confidentiality protected, an external attacker can perform a man-in-the-middle attack to view data in transit. | -| Threat type | Information disclosure | -| Impact type | Confidentiality | -| Affected Asset | External interface | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-27 | -| Threat title | External attacker exploits External interface to modify data in transit between SMO and external service | -| Threat description | If an External interface is not properly integrity protected, an external attacker can perform a man-in-the-middle attack to modify data in transit. | -| Threat type | Tampering | -| Impact type | Integrity | -| Affected Asset | External interface | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-28 | -| Threat title | External attacker uses External interface to exploit API vulnerability to gain access to SMO | -| Threat description | If an External interface uses an API with a known vulnerability that is not properly protected or patched, an attacker can exploit it to gain access to the SMO. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | SMO | - -v08.00 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-29 | -| Threat title | External attacker floods External interface to cause DDoS at SMO | -| Threat description | If the External interface is not protected, an external attacker can flood an External interface to overload the SMO. This can prevent legitimate messages and data from reaching the SMO or cause heavy processing at the SMO, resulting in performance degradation or outage of the SMO. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | SMO | - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-30 | -| Threat title | External attacker uses External interface to gain access to sensitive data-at-rest at the SMO | -| Threat description | If the SMO is not protected, an external attacker can use the External interface to gain authorized access to the SMO to view data-at-rest. | -| Threat type | Elevation of Privilege | -| Impact type | Authorization | -| Affected Asset | SMO | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-31 | -| Threat title | External attacker poisons External AI/ML data to corrupt SMO | -| Threat description | External data sources may be outside the control of the stakeholder(s) responsible for the O-RAN deployment. The stakeholder for an External data source could fail to provide proper security controls to protect data consumed by the SMO. If an external attacker were to gain access to AI/ML data, it could be corrupted and then be used at the SMO. | -| Threat type | Tampering | -| Impact type | Integrity | -| Affected Asset | SMO | - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-32 | -| Threat title | External attacker poisons External Enrichment Information data sources to corrupt SMO | -| Threat description | External data sources may be outside the control of the stakeholder(s) responsible for the O-RAN deployment. The stakeholder for an External data source could fail to provide proper security controls to protect data consumed by the SMO. If an external attacker were to gain access to External Enrichment Information, it could be corrupted and then be used at the SMO. | -| Threat type | Tampering | -| Impact type | Integrity | -| Affected Asset | SMO | - -## 6.4 Threats Targeting SME - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-33 | -| Threat title | rApp floods SME | -| Threat description | Misbehaving 3rd-party rApp, maliciously or non-maliciously, floods internal SMOS Communication interface targeting the SME to bring a volumetric DDoS attack against the SMO. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | SMO, SME | - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-34 | -| Threat title | External Consumer floods SME | -| Threat description | External Source, maliciously or non-maliciously, floods the External interface targeting the SME to bring a volumetric DDoS attack against the SMO. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | SMO, SME | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-35 | -| Threat title | SMOS floods SME | -| Threat description | SMOS, maliciously or non-maliciously, floods the SMOS Communication targeting the SME to bring a volumetric DDoS attack against the SMO. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | SMO, SMOS, SME | - -## 6.5 Preliminary Threat Analysis for RAN-Core Data Sharing - -RAN-Core Data Sharing is a new SMO feature to provide data export from the SMO to the 5G Core (5GC). 5 possible architectural options are being considered: - -- Option 1: SMO/Non-RT RIC to 5GC Consumer with Facade of NWDAF -- Option 2: SMO/Non-RT RIC to 5GC DCCF/MFAF with Facade of NWDAF -- Option 3: SMO/Non-RT RIC to 5GC NWDAF with Facade of OA&M -- Option 4: SMO/Non-RT RIC to 5GC NWDAF with Facade of RAN NF -- Option 5: SMO/Non-RT RIC to 5GC NWDAF with MDAS through SME - -WG11 performed a security analysis of the architectural options to provide recommendations for which should be considered for specification. In summary, Option 1 is high security risk and should not be considered. Option 2, 3, 4, and 5 are lower risk and equivalent from a security perspective. However, those options have a major risk due to lack of certificate-based mutual authentication with NWDAF. Option 5, in addition, requires the 3GPP NWDAF add support for the O-RAN SME interface, which needs new 3GPP standardization. - -## 6.6 Threats Targeting DME - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-36 | -| Threat title | rApp floods DME | -| Threat description | Misbehaving 3rd-party rApp, maliciously or non-maliciously, floods internal SMOS Communication interface targeting the DME to bring a volumetric DDoS attack against the SMO. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | SMO, DME | - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-37 | -| Threat title | External Consumer floods DME | -| Threat description | External Source, maliciously or non-maliciously, floods the External interface targeting the DME to bring a volumetric DDoS attack against the SMO. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | SMO, DME | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-38 | -| Threat title | SMOS floods DME | -| Threat description | SMOS, maliciously or non-maliciously, floods the SMOS Communication targeting the DME to bring a volumetric DDoS attack against the SMO. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | SMO, SMOS, DME | - -# 7 Security Controls - -Industry recommendations for strong security controls are provided from sources such as the OWASP Top 10 Proactive Controls [i.15], Center for Internet Security (CIS) Critical Security Controls [i.16], Cloud Security Alliance (CSA) Cloud Control Matrix (CCM) [i.17], ISO/IEC 27001:2013 Information Security Management System (ISMS) [i.18], NIST SP 800-53r5 Security and Privacy Controls for Information Systems and Organizations [i.19], and Cybersecurity and Infrastructure Security Agency (CISA) Security Guidance for 5G Cloud Infrastructures [i.9]. - -The OWASP Top 10 Proactive Controls are as follow: - -- C1: Define Security Requirements -- C2: Leverage Security Frameworks and Libraries -- C3: Secure Database Access -- C4: Encode and Escape Data -- C5: Validate All Inputs -- C6: Implement Digital Identity -- C7: Enforce Access Controls -- C8: Protect Data Everywhere -- C9: Implement Security Logging and Monitoring -- C10: Handle All Errors and Exceptions - -The CIS Critical Security Controls are as follow: - -- CIS Control 1: Inventory and Control of Enterprise Assets -- CIS Control 2: Inventory and Control of Software Assets -- CIS Control 3: Data Protection -- CIS Control 4: Secure Configuration of Enterprise Assets and Software -- CIS Control 5: Account Management -- CIS Control 6: Access Control Management -- CIS Control 7: Continuous Vulnerability Management -- CIS Control 8: Audit Log Management -- CIS Control 9: Email Web Browser and Protections -- CIS Control 10: Malware Defenses -- CIS Control 11: Data Recovery -- CIS Control 12: Network Infrastructure Management -- CIS Control 13: Network Monitoring and Defense -- CIS Control 14: Security Awareness and Skills Training -- CIS Control 15: Service Provider Management -- CIS Control 16: Application Software Security - -v08.00 - -CIS Control 17: Incident Response Management - -CIS Control 18: Penetration Testing - -Relevant controls from the CSA CCM are 2. Application and Interface Security, 5. Cryptography, Encryption, and Key Management, 7. Data Security and Privacy Lifecycle Management, and 10. Identity and Access Management (IAM). - -Relevant controls from ISO/IEC 27001:2013 are 5. Access Controls, 6. Cryptography, and 9. Communications Security. - -Relevant controls from NIST SP 800-53r5 are 1. Access Controls, 16. Risk Assessment, 18. System and Communications Protection, and 19. System and Information Integrity. - -Relevant controls from CISA's Security Guidance are mTLS 1.2, or higher, with PKI and X.509 certificates, Multi-Factor Authentication (MFA), Principle of Least Privilege, Continuous Monitoring and Logging, and data confidentiality and protection as components of a zero trust architecture as defined in NIST SP 800-207 [i.8]. - -With consideration of these external sources, the following security controls should be evaluated for the SMO risk analysis: - -- Control-1: mTLS 1.2 or 1.3 with PKI and X.509 certificates -- Control-2: OAuth 2.0 -- Control-3: IAM (using RBAC, ABAC, PBAC, TBAC) -- Control-4: Principle of Least Privilege -- Control-5: Certificate Management -- Control-6: API Message Integrity Protection and Input Validation -- Control-7: API Message Authentication -- Control-8: Encryption for Data at Rest -- Control-9: Encryption for Data in Motion -- Control-10: Integrity Protection for Data at Rest -- Control-11: Integrity Protection for Data in Motion -- Control-12: Integrity Protection for Data in Use -- Control-13: Digital Signatures -- Control-14: Monitoring and Logging -- Control-15: Alerting -- Control-16: Rate-Limiting -- Control-17: Configuration Validation -- Control-18: Network Segmentation and Traffic Filtering - -# 8 Risk Assessment - -This clause provides risk assessment tables for each of the identified assets. These tables list the assets, threats, impacts, and possible security controls. - -A malicious actor may be a nation-state adversary, cybercriminal, or employee. In a ZTA, perimeter defenses alone are insufficient. The SMO must be protected from untrusted external sources attempting to have access, while also assuming internal threat actors are inside the network with access to its functions and data. Security controls for a ZTA, protecting against external and internal threats, should be implemented through a risk-based approach. A risk analysis calculates risk levels by assessing the threat’s Likelihood of attack and the Impact from the attack. - -Impact scores can be lowered with consideration of existing security controls. Impact scoring is based upon current security controls. Impact scoring does not consider security controls that may be potentially specified in the future. - -Likelihood scores may be higher when the goal is a ZTA, because external and internal threats must be considered. When likelihood scoring during a risk analysis, it is necessary to consider internal threats performing reconnaissance attacks impacting confidentiality and privacy and attacks causing damage or degrading performance impacting availability. Internal threat actors are less likely to perform damaging attacks that are quickly and easily detected and blocked, but more likely to attempt reconnaissance attacks to collect information. As a result, reconnaissance type attacks can be scored Likelihood = High while damaging/availability attacks can be scored Likelihood = Medium or Low. - -External and internal threats are from the perspective of the SMO. External Threats are external to the SMO and Internal Threats are internal to the SMO. An External Threat may be external to the SMO but internal to the O-RAN architecture. - -A risk analysis of SMO threats is provided in the tables below covering general SMO risks, risks to the O2 interface, and risks to External interfaces. - -Threats and risks to the A1 and R1 interfaces are assessed in a separate Technical Report, Study on Security for Non-RT-RIC [i.20]. - -Additional SMO threats may be added for Decoupled SMO and Shared O-RU. - -## 8.1 General SMO Risks - -Table 8-1. SMO Risk Analysis - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/
Likelihood
Raw Score | Possible Security Controls | Security Control-id | -|------------|--------------------|-----------|--------------------------------------------------------------|--------------------------------------|----------------------------------------------|---------------------------------| -| ASSET-C-01 | SMO and all SMOS's | T-SMO-01 | External attacker exploits authentication weakness on SMO | Impact = High
Likelihood = Medium | Data encryption using mTLS 1.2 or 1.3 | Control-1 | -| ASSET-C-01 | SMO and all SMOS's | T-SMO-02 | External attacker exploits authorization weakness on SMO | Impact = High
Likelihood = Medium | OAuth 2.0, IAM, principle of least privilege | Control-2, Control-3, Control-4 | -| ASSET-C-01 | SMO and all SMOS's | T-SMO-03 | External Overload DoS attack targeted at SMO | Impact = High
Likelihood = Medium | Rate-Limiting | Control-16 | -| ASSET-C-01 | SMO and all SMOS's | T-SMO-04 | Internal attacker exploits authentication weakness on a SMOS | Impact = High
Likelihood = Medium | Data encryption using mTLS 1.2 or 1.3 | Control-1 | -| ASSET-C-01 | SMO and all SMOS's | T-SMO-05 | Internal attacker exploits authorization weakness on SMO | Impact = High
Likelihood = Medium | OAuth 2.0, IAM, principle of least privilege | Control-2, Control-3 | - -v08.00 - -| | | | | | | | -|------------|--------------------|----------|---------------------------------------------------------------|--------------------------------------|----------------------------------------------------------------|----------------------------------| -| ASSET-C-01 | SMO and all SMOS's | T-SMO-06 | Internal Overload DoS attack targeted at SMOS | Impact = High
Likelihood = Medium | Rate-Limiting | Control-16 | -| ASSET-C-01 | SMO and all SMOS's | T-SMO-07 | Internal DoS attack disables internal SMOS or SMO process(es) | Impact = High
Likelihood = Medium | Monitoring, Logging, Alerting | Control-14, Control-15 | -| ASSET-C-01 | SMO | T-SMO-08 | Attacker exploits insecure API to gain access to SMO | Impact = High
Likelihood = Medium | API input validation | Control-6 | -| ASSET-C-01 | SMO and all SMOS's | T-SMO-09 | Sensitive data in motion is exposed to an internal attacker | Impact = High
Likelihood = Medium | Data encryption and integrity protection using mTLS 1.2 or 1.3 | Control-1 | -| ASSET-C-01 | SMO | T-SMO-10 | Sensitive data at rest is exposed to an internal attacker | Impact = High
Likelihood = High | Data encryption and integrity protection | Control-8, Control-10 | -| ASSET-C-01 | SMO | T-SMO-11 | AI/ML poisoning by internal attacker | Impact = High
Likelihood = Medium | Integrity protection | Control-10 | -| ASSET-C-01 | SMO | T-SMO-12 | AI/ML exposure on external entity | Impact = High
Likelihood = Medium | Data encryption, Integrity protection, API input validation | Control-6, Control-8, Control-10 | -| ASSET-C-01 | SMO | T-SMO-13 | Malicious actor views local logs | Impact = High
Likelihood = High | Data encryption | Control-8 | -| ASSET-C-01 | SMO | T-SMO-14 | Malicious actor modifies local log entries | Impact = High
Likelihood = Medium | Integrity protection | Control-10 | -| ASSET-C-01 | SMO | T-SMO-15 | Malicious actor deletes local logs | Impact = High
Likelihood = Medium | Integrity protection | Control-10 | -| ASSET-C-01 | SMO | T-SMO-16 | Malicious actor intercepts exports of local logs | Impact = High
Likelihood = High | Data encryption | Control-9 | -| ASSET-C-01 | SMO | T-SMO-17 | Malicious external actor gains unauthorized access to logs | Impact = High
Likelihood = High | IAM, principle of least privilege | Control-3, Control-4 | -| ASSET-C-01 | SMO | T-SMO-18 | Malicious internal actor gains authorized access to logs | Impact = High
Likelihood = High | Data encryption | Control-8 | - -## 8.2 Threats at O2 interface - -Table 8-2. SMO Risk Analysis for Internal Threats at O2 Interface - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/
Likelihood
Raw Score | Possible Security Controls | Security Control-id | -|------------|------------|-----------|-----------------------------------------------------------------------------------------|------------------------------------|---------------------------------------|---------------------| -| ASSET-C-01 | SMO | T-SMO-19 | Internal attacker exploits O2 interface to view data in transit between SMO and O-Cloud | Impact = High
Likelihood = High | Data encryption using mTLS 1.2 or 1.3 | Control-1 | - -v08.00 - -| | | | | | | | -|------------|-----|----------|-------------------------------------------------------------------------------------------------------------------|--------------------------------------|--------------------------------------------------|------------------------| -| ASSET-C-01 | SMO | T-SMO-20 | Internal attacker exploits O2 interface to modify data in transit between SMO and O-Cloud | Impact = High
Likelihood = Medium | Integrity protection using mTLS 1.2 or 1.3 | Control-1 | -| ASSET-C-01 | SMO | T-SMO-21 | Internal attacker uses O2 interface via SMO to exploit API vulnerability to gain access to O-Cloud infrastructure | Impact = High
Likelihood = High | API message authentication, API input validation | Control-7, Control-6 | -| ASSET-C-01 | SMO | T-SMO-22 | Internal attacker floods O2 interface via SMO to cause DDoS on O-Cloud infrastructure | Impact = High
Likelihood = Medium | Rate-Limiting, Network segmentation | Control-16, Control-18 | -| ASSET-C-01 | SMO | T-SMO-23 | External attacker uses O2 interface via O-Cloud to exploit API vulnerability to gain access to SMO | Impact = High
Likelihood = Medium | API message authentication, API input validation | Control-7, Control-6 | -| ASSET-C-01 | SMO | T-SMO-24 | External attacker floods O2 interface via O-Cloud to cause DDoS on SMO | Impact = High
Likelihood = Medium | Rate-Limiting, Network segmentation | Control-16, Control-18 | -| ASSET-C-01 | SMO | T-SMO-25 | External attacker uses O2 interface via O-Cloud to gain authorized access to sensitive data-at-rest at the SMO | Impact = High
Likelihood = Medium | Data encryption, Integrity protection | Control-8, Control-10 | - -## 8.3 Threats at External Interfaces - -Table 8-3. SMO Risk Analysis for External Threats at External interfaces - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/
Likelihood
Raw Score | Possible Security Controls | Security Control-id | -|------------|------------|-----------|----------------------------------------------------------------------------------------------------------|--------------------------------------|--------------------------------------------------|------------------------| -| ASSET-C-01 | SMO | T-SMO-26 | External attacker exploits External interface to view data in transit between SMO and external service | Impact = High
Likelihood = High | Data encryption using mTLS 1.2 or 1.3 | Control-1 | -| ASSET-C-01 | SMO | T-SMO-27 | External attacker exploits External interface to modify data in transit between SMO and external service | Impact = High
Likelihood = Medium | Integrity protection using mTLS 1.2 or 1.3 | Control-1 | -| ASSET-C-01 | SMO | T-SMO-28 | External attacker uses External interface to exploit API vulnerability to gain access to SMO | Impact = High
Likelihood = Medium | API message authentication, API input validation | Control-7, Control-6 | -| ASSET-C-01 | SMO | T-SMO-29 | External attacker floods External interface to cause DDoS at SMO | Impact = High
Likelihood = Medium | Rate-Limiting, Network segmentation | Control-16, Control-18 | -| ASSET-C-01 | SMO | T-SMO-30 | External attacker uses External interface to gain access to sensitive data-at-rest at the SMO | Impact = High
Likelihood = Medium | Data encryption, Integrity protection | Control-8, Control-10 | -| ASSET-C-01 | SMO | T-SMO-31 | External attacker poisons External AI/ML data to corrupt SMO | Impact = High
Likelihood = High | Data encryption, Integrity protection | Control-8, Control-10 | - -v08.00 - -| | | | | | | | -|------------|-----|----------|---------------------------------------------------------------------------------------|------------------------------------|---------------------------------------|-----------------------| -| ASSET-C-01 | SMO | T-SMO-32 | External attacker poisons External Enrichment Information data sources to corrupt SMO | Impact = High
Likelihood = High | Data encryption, Integrity protection | Control-8, Control-10 | -|------------|-----|----------|---------------------------------------------------------------------------------------|------------------------------------|---------------------------------------|-----------------------| - -## 8.4 Threats Targeting SME - -Table 8-4. SMO Risk Analysis for Threats Targeting SME - -| Asset-Id | Asset Name | Threat-Id | Threat Description (Brief) | Impact/
Likelihood
Raw Score | Possible Security Controls | Security Control-id | -|----------|------------|-----------|------------------------------|--------------------------------------|--------------------------------------------------------|------------------------| -| TBD | SME | T-SMO-32 | rApp floods SME | Impact = High
Likelihood = Medium | Overload protection with rate-limiting at SME | Control-16 | -| TBD | SME | T-SMO-33 | External Consumer floods SME | Impact = High
Likelihood = Medium | Network Segmentation, Traffic Filtering, Rate-Limiting | Control-16, Control-18 | - -# 9 Primary Security Issues - -The following items were identified during the SMO Security Analysis phase 1 and were addressed in TR v1: - -1. External interfaces to the SMO and Non-RT RIC have risks of exploitation from external threat actors. The protocol and API used on an external interface is defined by the application or service and is not in-scope for the O-RAN Alliance. WG11 analyzed the threats, risks, and potential security controls with the goal to provide general security requirements for any implementation of an External interface with the goal to protect O-RAN network functions and data. -2. The O2 interface is at risk of being exploited by an internal threat actor at the SMO or the O-Cloud. This TR provides a security analysis of the O2 interface from the perspectives of the internal threat actor at the SMO and the O-Cloud, in addition to external threats. The work item team will need to collaborate with the O-Cloud security work item team to ensure complete coverage of O2 threats and security controls. - -The following items were identified as SMO security topics that require additional phases of the SMO Security Analysis to produce an update to the TR. - -1. WG1 is considering a Decoupled SMO architecture based upon a Service-based Architecture (SBA) as used in the 5G Core. This evolution of the SMO architecture would have security implications which WG1 should consider. WG11 has performed a security analysis for Decoupled SMO. WG11 should contribute security requirements as WG1 develops specifications for a Decoupled SMO. -2. The Decoupled SMO architecture will define a set of SMO Services called SMOS. WG11 has performed a security analysis for SMOS. WG11 should contribute security requirements as WG1 develops specifications for SMOS. Requirements can be general SMOS security requirements and SMOS-specific security requirements. -3. SMO service consumers and service producers may be SMOS and/or rApps. WG1 is considering to have the Service Management Exposure (SME) service act a security proxy for all SMO service consumers access service producers. WG11 should perform a security analysis for the SME to be a security proxy. -4. WG11 has performed a security analysis for RAN-Core Data Sharing. WG11 should contribute security requirements as WG1 develops specifications for RAN-Core Data Sharing. - -# 10 Recommendations - -The Security Analysis presented in this technical report used the following process: - -1. Asset identification -> 2. Threat identification -> 3. Threat analysis -> 4. Risk analysis -> 5. Recommend Security Controls - -The SMO is a logical framework, not an implementation architecture, with external interfaces and internal functions and interfaces that are assets which should be protected with security controls. The SMO may be implemented as a monolithic platform or multiple disaggregated functions, such as SMOS and Non-RT-RIC functions, which should be protected assets. Other SMO assets are the R1, A1, O1, O2, OFH M-Plane, and External interfaces and data at rest and in transit. - -**Recommendation 1:** WG11 should update the Security Threat Modeling and Remediation Analysis document [i.6] to include the assets identified in this security analysis technical report. A CR will be generated. - -For the threat analysis, external and internal threats were considered from the perspective of the SMO. Internal threats are internal to the SMO and external threats are external to the SMO. External threats may be external to the SMO and internal to the O-RAN architecture. More than 30 threats were identified, categorized as general SMO threats, O2 interface threats, and External interfaces threat. - -**Recommendation 2:** WG11 should update the Security Threat Modeling and Remediation Analysis document [i.6] to include the threats and threat tables created in this security analysis technical report. A CR will be generated. - -Risk analysis of the identified threats included impact-likelihood scoring. All 30+ of the identified threats were score either high-medium or high-high. External data sources are considered the greatest threat to the SMO due to the risk of an external threat actor poisoning external data that is imported into the SMO and the risk of an external threat actor exploiting an API on the external interface to gain access to the SMO or perform a remote code execution attack. - -Likelihood scoring was influenced by the consideration of a zero trust architecture (ZTA), which is a publicly expressed goal of the O-RAN Alliance to consider external and internal threats. ZTA is built on the foundational principles that perimeter defenses are insufficient to secure a network as internal external threats pose risk to a network. There are two guidelines for designing a network and its network functions for a ZTA: - -1. There is no implicit trust granted to an asset based upon ownership, physical location, or network location [i.8]. -2. Assume the adversary is already inside the network [i.9]. - -The security controls recommended in this TR protect the SMO from confidentiality, integrity, and availability attacks from external and internal threats, consistent with a ZTA. - -**Recommendation 3:** The SMO should have security controls implemented to protect its functions and interfaces from external and internal threats, consistent with a ZTA. Specific requirements will be formed as this work item continues. A CR for the WG11 Security Requirements Specifications is planned for the March release train. - -Consistent with a ZTA, the SMO should be secure by design in which its security posture does not assume that the SMO internal functions and interfaces are secure. - -**Recommendation 4:** WG11 should collaborate with WG1 to ensure the WG11 security specifications are referenced by WG1 in its SMO specifications. This process will build-in security to the evolving specifications for the SMO and Decoupled SMO. - -The SMO architecture is continuing to evolve to support Decoupled SMO and direct communication between internal SMO functions and applications. In addition, the security analysis will also need to consider Transport Node (TN) Termination, as specified in WG9, and Cooperative Transport Interface (CTI), as specified in WG4. - -**Recommendation 5:** This SMO Security work item continues its security analysis to produce a TR v2 for the March release train, addressing Decoupled SMO, TN, and CTI. - -The SMO role in certificate management is currently unspecified. - -**Recommendation 6:** The WG11 Certificate Management work item team should investigate a potential role, if any, for the SMO in certificate management. - -# Annex: Change history/Change request (history) - -| Date | Revision | Description | -|---------------|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| July 2022 | V01.00.00 | Document creation, template | -| March 2023 | V02.00 | Update architecture diagrams in Clause 2 – Assets. | -| November 2023 | V03.00 | Add security analysis for Decoupled SMO and RAN-Core Data Sharing | -| March 2024 | V04.00 | Update Assets list for Decoupled SMO. Add security threats for the SME. | -| July 2024 | V05.00 | Update Issues list. Update for SMO Services in Decoupled SMO architecture | -| November 2024 | V06.00 | Added asset-id's and acronyms | -| July 2025 | V07.00 | Added DME threat analysis
Format with approved TR template | -| November 2025 | V08.00 | Updates to align security analysis with Decoupled SMO architecture, including SMOS. Updated clauses are References, Abbreviations, Assets, Threats, General SMO Threats, General SMO Risks | \ No newline at end of file diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 85726f59a25a9b4fe4739db11a54b7776cb182e3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:18ae0bf8691a133675eee001d0431fac16c33a04fd9d709cd71f358744635641 -size 4241 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index f9d929ed39f5671df73147e7194cfb862b9ac650..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:444ea96c4e54647f2aa5e7c4722e2741cab3c547ef1fc1a137607ee5cca4a310 -size 4289 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 4c08dfc76c2e1c820f6a9f16a63954ba06c1fccc..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7ce1ab29534c9ef702897bc9101a641c4be12aa2cd087d777c725690f57f6871 -size 4159 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index f9d929ed39f5671df73147e7194cfb862b9ac650..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:444ea96c4e54647f2aa5e7c4722e2741cab3c547ef1fc1a137607ee5cca4a310 -size 4289 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 4c08dfc76c2e1c820f6a9f16a63954ba06c1fccc..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7ce1ab29534c9ef702897bc9101a641c4be12aa2cd087d777c725690f57f6871 -size 4159 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 4c08dfc76c2e1c820f6a9f16a63954ba06c1fccc..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7ce1ab29534c9ef702897bc9101a641c4be12aa2cd087d777c725690f57f6871 -size 4159 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index f9d929ed39f5671df73147e7194cfb862b9ac650..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:444ea96c4e54647f2aa5e7c4722e2741cab3c547ef1fc1a137607ee5cca4a310 -size 4289 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 66a2484d06abe3a01e6d57da79cb33ad86395fec..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eed7b9d35e34be7ee42c7152263386e6284d14bfb7981950326ab73e3165cbd6 -size 4234 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index 05db6d97ab494767c37bf3631480dd4d64f911f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f05e29560d6f1bccc153b1438be4b945be26a9ce2a778c630fb2d2196ff16f0 -size 4021 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 85726f59a25a9b4fe4739db11a54b7776cb182e3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:18ae0bf8691a133675eee001d0431fac16c33a04fd9d709cd71f358744635641 -size 4241 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 66a2484d06abe3a01e6d57da79cb33ad86395fec..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eed7b9d35e34be7ee42c7152263386e6284d14bfb7981950326ab73e3165cbd6 -size 4234 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 85726f59a25a9b4fe4739db11a54b7776cb182e3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:18ae0bf8691a133675eee001d0431fac16c33a04fd9d709cd71f358744635641 -size 4241 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 8f1d6cab924a14d89ecb8f7cade2aa55793d7c04..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e9b81cb494a2f48ef04637c139ad7c4bbbdb239e7aec9156f529659588aae7ad -size 4044 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 85726f59a25a9b4fe4739db11a54b7776cb182e3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:18ae0bf8691a133675eee001d0431fac16c33a04fd9d709cd71f358744635641 -size 4241 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index d8fbe71b1c68aeb0a4fd642b0c20bea0bce0bca9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c3094a4d0a9b30500d2c7a39c88794ee20e962bcc2f45699608f90192e08e47 -size 4059 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index 4c08dfc76c2e1c820f6a9f16a63954ba06c1fccc..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7ce1ab29534c9ef702897bc9101a641c4be12aa2cd087d777c725690f57f6871 -size 4159 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index 428c3a3818e88b435482a1e5ded07ec12f5c25a3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d7ee9111e224f56306ed937dad988c1514224d53334eb5490e7a45f739dc8023 -size 4258 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 85726f59a25a9b4fe4739db11a54b7776cb182e3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:18ae0bf8691a133675eee001d0431fac16c33a04fd9d709cd71f358744635641 -size 4241 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 85726f59a25a9b4fe4739db11a54b7776cb182e3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:18ae0bf8691a133675eee001d0431fac16c33a04fd9d709cd71f358744635641 -size 4241 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index aa247cbe922aa0dfaef93b391c31446e3487d99b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e7f0f1beab8384b3356daa0183df646a66ea1b07625efc2c202bec2b8c5707dd -size 4227 diff --git a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 7b453284274ac8f2dfe645656876673c3f17609b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.SMO-Security-Analysis.0-R005-v08.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:19a5252fb743c2279c69f6e782b2a466786d3a09dc26b7dfb4e82de02d45162a -size 4567 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/doc.md b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/doc.md deleted file mode 100644 index 0fec553b791615265e7798c60f25dc90c9457cbb..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/doc.md +++ /dev/null @@ -1,2038 +0,0 @@ - - -# --- **O-RAN Work Group 11 (Security Work Group)****Study on Security for Near Real Time RIC and xApps** - -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 - -| | | -|-----------------------------------------------------------------------------|----| -| List of figures ..... | 4 | -| List of tables ..... | 5 | -| Foreword ..... | 6 | -| Modal verbs terminology ..... | 6 | -| Introduction ..... | 6 | -| 1 Scope..... | 7 | -| 2 References..... | 7 | -| 2.1 Normative references ..... | 7 | -| 2.2 Informative references..... | 7 | -| 3 Definition of terms, symbols and abbreviations ..... | 9 | -| 3.1 Terms..... | 9 | -| 3.2 Symbols..... | 10 | -| 3.3 Abbreviations ..... | 10 | -| 4 RIC background, concepts and assumptions..... | 12 | -| 4.1 Introduction ..... | 12 | -| 4.2 Near-RT RIC architecture ..... | 12 | -| 4.3 Interfaces ..... | 13 | -| 4.4 xApps ..... | 13 | -| 4.5 Near-RT RIC APIs ..... | 14 | -| 5 Key Issues ..... | 15 | -| 5.1 Introduction ..... | 15 | -| 5.2 Key Issue #1: Malicious xApps deployed on the Near-RT RIC..... | 15 | -| 5.2.1 Key issue detail..... | 15 | -| 5.2.2 Security threats ..... | 15 | -| 5.2.3 Potential security requirements ..... | 16 | -| 5.3 Key Issue #2: Compromised xApp ..... | 16 | -| 5.3.1 Key issue detail..... | 16 | -| 5.3.2 Security Threats..... | 16 | -| 5.3.3 Potential security requirements ..... | 16 | -| 5.4 Key Issue #3: Conflicting xApps ..... | 17 | -| 5.4.1 Key issue detail..... | 17 | -| 5.4.2 Security threats ..... | 17 | -| 5.4.3 Potential security requirements ..... | 17 | -| 5.5 Key Issue #4: Isolation between xApps ..... | 17 | -| 5.5.1 Key issue detail..... | 17 | -| 5.5.2 Security threats ..... | 18 | -| 5.5.3 Potential security requirements ..... | 18 | -| 5.6 Key Issue #5: Compromise of ML data pipelines used in Near-RT RIC ..... | 18 | -| 5.6.1 Key issue detail..... | 18 | -| 5.6.2 Security threats ..... | 19 | -| 5.6.3 Potential security requirements ..... | 19 | -| 5.7 Key Issue #6: Altering the ML learning models used in Near-RT RIC..... | 19 | -| 5.7.1 Key issue detail..... | 19 | -| 5.7.2 Security threats ..... | 20 | -| 5.7.3 Potential security requirements ..... | 20 | -| 5.8 Key Issue #7: Data Protection and Privacy in Near-RT RIC Database ..... | 20 | -| 5.8.1 Key issue detail..... | 20 | -| 5.8.2 Security threats ..... | 20 | -| 5.8.3 Potential security requirements ..... | 21 | -| 5.9 Key Issue #8: Onboarding untrusted xApps ..... | 21 | -| 5.9.1 Key issue detail..... | 21 | - -- 5.9.2 Security threats ..... 21 -- 5.9.3 Potential security requirements ..... 22 -- 5.10 Key Issue #9: xApp exploitation via malicious AI policies ..... 22 - - 5.10.1 Key issue detail..... 22 - - 5.10.2 Security threats ..... 22 - - 5.10.3 Potential security requirements ..... 22 -- 5.11 Key Issue #10: Near-RT RIC APIs authentication ..... 23 - - 5.11.1 Key issue detail..... 23 - - 5.11.2 Security threats ..... 23 - - 5.11.3 Potential security requirements ..... 23 -- 5.12 Key Issue #11: Near-RT RIC APIs authorization..... 24 - - 5.12.1 Key issue detail..... 24 - - 5.12.2 Security threats ..... 24 - - 5.12.3 Potential security requirements ..... 25 -- 5.13 Key Issue #12: xAppID abuse..... 25 - - 5.13.1 Key issue detail..... 25 - - 5.13.2 Security threats ..... 25 - - 5.13.3 Potential security requirements ..... 25 -- 5.14 Key Issue #13: Malicious Y1 Consumer..... 25 - - 5.14.1 Key issue detail..... 25 - - 5.14.2 Security threats ..... 26 - - 5.14.3 Potential security requirements ..... 26 -- 5.15 Key Issue #14: Malicious E2 Node..... 26 - - 5.15.1 Key issue detail..... 26 - - 5.15.2 Security threats ..... 26 - - 5.15.3 Potential security requirements ..... 26 -- 6 Mitigations and Solutions ..... 28 - - 6.1 Introduction ..... 28 - - 6.2 Solution #1: Secure onboarding and deployment of xApps in Near-RT RIC..... 28 - - 6.2.1 Introduction ..... 28 - - 6.2.2 Solution details ..... 28 - - 6.2.3 Evaluation..... 30 - - 6.3 Solution #2: Security management of risks in open-source components of Near-RT RIC architecture ..... 30 - - 6.3.1 Introduction ..... 30 - - 6.3.2 Solution details ..... 30 - - 6.3.3 Evaluation..... 32 - - 6.4 Solution #3: Authentication schema for APIs..... 32 - - 6.4.1 Introduction ..... 32 - - 6.4.2 Solution details ..... 33 - - 6.4.3 Evaluation..... 34 - - 6.5 Solution #4: Authorization framework for APIs..... 34 - - 6.5.1 Introduction ..... 34 - - 6.5.2 Solution details ..... 34 - - 6.5.3 Evaluation..... 36 - - 6.6 Solution #5: Near-RT RIC database and SDL access control mechanisms ..... 36 - - 6.6.1 Introduction ..... 36 - - 6.6.2 Solution details ..... 36 - - 6.6.3 Evaluation..... 37 - - 6.7 Solution #6: Security Logging (part of FCAPS)..... 37 - - 6.7.1 Introduction ..... 37 - - 6.7.2 Solution details ..... 37 - - 6.7.3 Evaluation..... 38 - - 6.8 Solution #7: Access control mechanism for API repository/registry..... 38 - - 6.8.1 Introduction ..... 38 - - 6.8.2 Solution details ..... 38 - - 6.8.3 Evaluation..... 38 - - 6.9 Solution #8: Secure mechanisms for E2 interface ..... 39 - - 6.9.1 Introduction ..... 39 - - 6.9.2 Solution details ..... 39 - - 6.9.3 Evaluation..... 39 - -6.10 Solution #9: Secure mechanisms for A1 interface ..... 39 - -6.10.1 Introduction ..... 39 - -6.10.2 Solution details ..... 39 - -6.10.3 Evaluation..... 39 - -6.11 Solution #10: Secure mechanisms for O1 interface ..... 40 - -6.11.1 Introduction ..... 40 - -6.11.2 Solution details ..... 40 - -6.11.3 Evaluation..... 40 - -6.12 Solution #11: Mitigation for conflicting xApps ..... 40 - -6.12.1 Introduction ..... 40 - -6.12.2 Solution details ..... 40 - -6.12.3 Evaluation..... 41 - -6.13 Solution #12: A1 Policy authentication ..... 41 - -6.13.1 Introduction ..... 41 - -6.13.2 Solution details ..... 41 - -6.13.3 Evaluation..... 41 - -6.14 Solution #13: Network Security layer for APIs ..... 41 - -6.14.1 Introduction ..... 41 - -6.14.2 Solution details ..... 42 - -6.14.3 Evaluation..... 42 - -6.15 Solution #14: Security procedure for xApp registration ..... 43 - -6.15.1 Introduction ..... 43 - -6.15.2 Solution details ..... 43 - -6.15.3 Evaluation..... 45 - -6.16 Solution #15: Security requirement proposals for Y1 interface..... 46 - -6.16.1 Introduction ..... 46 - -6.16.2 Solution details ..... 47 - -6.16.3 Evaluation..... 47 - -6.17 Solution #16: Additional security measures for the E2 interface..... 48 - -6.17.1 Introduction ..... 48 - -6.17.2 Solution details ..... 48 - -6.17.3 Evaluation..... 48 - -6.18 Solution #17: Standard Identity management of xApp during xApp Registration Procedure..... 48 - -6.18.1 Introduction ..... 48 - -6.18.2 Solution details ..... 49 - -6.18.3 Evaluation..... 51 - -7. Conclusions..... 52 - -7.1 Key Issue Solution Mapping..... 52 - -8. Recommendations..... 55 - -Annex: Change history/Change request (history) ..... 56 - -# List of figures - -Figure 4.2-1: Near-RT RIC Internal Architecture..... 12 - -Figure 4.5-1: Overview of Near-RT RIC APIs..... 14 - -Figure 6.2-1: Onboarding xApp to SMO ..... 28 - -Figure 6.2-2— Authentication during Deployment Process..... 29 - -Figure 6.2-3 – Extended xApp Registration procedure from [i.3] ..... 29 - -Figure 6.5-1— from RFC 6749 ..... 34 - -Figure 6.5-2— OAuth 2.0 process in Near-RT RIC..... 35 - -Figure 6.6-1— xApp database token during onboarding..... 36 - -Figure 6.6-2 – Modified SDL Client Registration Procedure from [i.3]..... 37 - -Figure 6.15.2-1: Security procedure for xApp registration ..... 44 - -Figure 6.15.3-1: xApp registration process with Security procedure ..... 46 - -Figure 6.16-1 Scenarios relevant to the Y1 interface security ..... 47 - -Figure 6.18.1-1: Secured xApp Registration Procedure using SPIRE.....49 -Figure 6.18.2-1: x-App Registration procedure using SPIFFE Framework. ....51 - -# --- List of tables - -Table 6.14-1 network layers proposed for the Network APIs in Near-RT RIC by O-RAN WG3 .....42 -Table 6.18-1 Example registration entries of two xApp Instances .....50 -Table 7.1-1 Key Issue to Solution mapping .....53 - -# Foreword - -This Technical Report (TR) has been produced by WG11 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 - -The Near-Real Time RAN Intelligent Controller (Near-RT RIC) is a new virtualized function that adds RAN programmability to existing or new RAN networks, e.g., self-organizing networks (SON) type of functions. It is a platform designed to use AI/ML-based tools with open interfaces to the RAN (E2) and the management and orchestration system (A1, O1). - -The Near-RT RIC enables near real time control and optimization of RAN elements and resources via fine-grained data (e.g., UE basis, Cell basis) collection and actions over E2 interface, and includes open interfaces (A1, O1) to the management and orchestration system (SMO). - -The Near-RT RIC platform is a software-based near-real-time microservice-based platform for hosting microservice-based applications – the xApps – that run on the Near-RT RIC platform. A xApp may consist of one or more microservices and at the point of onboarding it identifies which data it consumes and which data it provides. It is independent of Near-RT RIC and may be provided by any third party. The E2 interface enables a direct association between xApp and RAN functionalities. - -# 1 Scope - -The present document considers the security aspects of the Near-RT RIC platform and xApps, as well as the associated network and management interfaces (E2, A1, O1) and APIs. - -Taking into consideration the threats and risks identified in O-RAN Threat Model specification [i.1], the study analyses a list of key issues in the Near-RT RIC overall architecture and proposes solutions in order to derive security requirements, intended to be part of O-RAN Security Requirements Specifications [i.2]. - -# 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] O-RAN.WG11.TR.Threat-Modeling: “O-RAN Security Threat Modeling and Risk Assessment”. -- [i.2] O-RAN.WG11.TS.SRCS: “Security Requirements and Controls Specification”. -- [i.3] O-RAN.WG3.RICARCH: “Near-RT RIC Architecture ” . -- [i.4] O-RAN.WG2.TS.Use-Case-Requirements: “Non-RT RIC & A1/R1 interface: Use Cases and Requirements”. -- [i.5] O-RAN.WG3.TS.E2GAP: “E2 General Aspects and Principles (E2GAP)”. -- [i.6] O-RAN.WG5.O-DU-O1: “O1 Interface specification for O-DU”. -- [i.7] O-RAN.WG5.O-CU-O1: “O1 Interface specification for O-CU-UP and O-CU-CP”. -- [i.8] O-RAN.WG10.TS.O1-Interface: “O-RAN O1 Interface Specification”. -- [i.9] O-RAN.WG2.A1GAP: “A1 interface: General Aspects and Principles”. -- [i.10] OWASP API Security Top 10 2019, . -- [i.11] IETF RFC 6749: The OAuth 2.0 Authentication framework, . -- [i.12] IETF RFC 6819: OAuth 2.0 threat model and security considerations, . - -- [i.13] 3GPP TS 33.501: “Security architecture and procedures for 5G system”, -- [i.14] ETSI NFV SEC022: “Network Functions Virtualization (NFV) Release 2; Security; Access Token Specification for API Access”. -- [i.15] ETSI GS MEC 009 V3.1.1 (2021-06): Multi-access Edge Computing (MEC); General principles, patterns and common aspects of MEC Service APIs, [https://www.etsi.org/deliver/etsi\\_gs/MEC/001\\_099/009/03.01.01\\_60/gs\\_MEC009v030101p.pdf](https://www.etsi.org/deliver/etsi_gs/MEC/001_099/009/03.01.01_60/gs_MEC009v030101p.pdf). -- [i.16] 3GPP TR 33.845 v16.1.0 (2020-09): Study on security aspects of the 5G Service Based Architecture (SBA). -- [i.17] IETF RFC 7519: JSON Web Token. . -- [i.18] IETF RFC 7515: JSON Web Signature. . -- [i.19] O-RAN.WG11.TS.SecProtSpec: “Security Protocols Specifications”. -- [i.20] 3GPP TS 33.310: “Network Domain Security (NDS); Authentication Framework (AF)”. -- [i.21] 3GPP TS 33.210: “3G security; Network Domain Security (NDS); IP network layer security”. -- [i.22] O-RAN.WG10.TS.OAM-Architecture: “O-RAN Operations and Maintenance Architecture”. -- [i.23] O-RAN.WG6.ORCH-USE-CASES: “O-RAN Orchestration Use Cases and Requirements for O-RAN Virtualized RAN”. -- [i.24] Executive Order 14028, Improving the Nation’s Cybersecurity: Security Measures for EO-Critical Software Use. . -- [i.25] OpenSSF Best Practices. . -- [i.26] OpenSSF Software Development Fundamentals Link: . -- [i.27] OpenSSF Best Practices Badge Program: . -- [i.28] CISA NSA 5G Security guideline [https://media.defense.gov/2021/Oct/28/2002881720/-1-/1/0/SECURITY\\_GUIDANCE\\_FOR\\_5G\\_CLOUD\\_INFRASTRUCTURES\\_PART\\_I\\_20211028.PDF](https://media.defense.gov/2021/Oct/28/2002881720/-1-/1/0/SECURITY_GUIDANCE_FOR_5G_CLOUD_INFRASTRUCTURES_PART_I_20211028.PDF). -- [i.29] Opensource Software “Security 5G Security” whitepaper. . -- [i.30] NIST Special Publication (SP) 800-40, Guide to Enterprise Patch Management Technologies. . -- [i.31] 3GPP TS 33.122: “Security aspects of Common API Framework (CAPIF) for 3GPP northbound APIs”. -- [i.32] O-RAN.WG1.TS.OAD: “O-RAN Architecture Description”. -- [i.33] 3GPP TS 23.501: “System Architecture for the 5G System (5GS); Stage 2”. -- [i.34] RAIE Impacts on Near-RT RIC Architecture; discussion document, CMCC-2022.12.12-WG3-C-RAIE Impacts on RICARCH-v2.pptx. -- [i.35] Solving the Bottom Turtle — a SPIFFE Way to Establish Trust in Your Infrastructure via Universal Identity: . - -- [i.36] SPIRE Concepts: An overview of SPIRE’s architecture and fundamentals: -. -- [i.37] Kubernetes Documentation: PKI certificates and requirements: -. -- [i.38] Plugin\_agent\_workloadattestor\_k8s: -[https://github.com/spiffe/spire/blob/v1.7.0/doc/plugin\\_agent\\_workloadattestor\\_k8s.md](https://github.com/spiffe/spire/blob/v1.7.0/doc/plugin_agent_workloadattestor_k8s.md). -- [i.39] xApp\_Writer\_s\_Guide\_v2.pdf: [https://wiki.o-ran-sc.org/download/attachments/17269011/xApp\\_Writer\\_s\\_Guide\\_v2.pdf?version=4&modificationDate=1625642899082&api=v2](https://wiki.o-ran-sc.org/download/attachments/17269011/xApp_Writer_s_Guide_v2.pdf?version=4&modificationDate=1625642899082&api=v2). -- [i.40] SPIFFE-ID: . -- [i.41] NIST Special Publication 800-207A: -. -- [i.42] Void. -- [i.43] O-RAN Core Infrastructure Initiative (CII) Badging: . -- [i.44] O-RAN Software Community Projects: . -- [i.45] IETF RFC 9562: Universally Unique Identifiers (UUIDs). -. - -# --- 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the following terms apply: - -**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 within SMO that drives the content carried across the A1 interface. It is comprised of the Non-RT RIC Framework and the Non-RT RIC Applications. - -**O-CU-CP:** O-RAN Central Unit – Control Plane: a logical node hosting RRC and the control plane part of PDCP protocol. - -**O-CU-UP:** O-RAN Central Unit – User Plane: a logical node hosting the user plane part of PDCP protocol and 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). - -**O-eNB:** An eNB or ng-eNB that supports E2 interface. - -**OI:** An interface between SMO and O-RAN managed elements, for operation and management, by which FCAPS management, PNF (Physical Network Function) Software management, File management shall be achieved. - -**SMO:** A Service Management and Orchestration system. - -**A1:** An 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. - -**E2:** An interface connecting Near-RT RIC and one or more O-CU-CPs, one or more O-CU-UPs, or one or more O-DUs. - -**Y1:** An interface between Near-RT RIC and Y1 consumers [i.32]. The interface enables RAN analytics information exposure from Near-RT RIC. - -**E2 Node:** A logical node terminating E2 interface. In this version of the specification, O-RAN nodes terminating E2 interface are: - -- for NR access: O-CU-CP, O-CU-UP, O-DU -- for E-UTRA access: O-eNB. - -**xApp:** An application designed to run on Near-RT RIC. It may consist of one or more microservices and at the point of on-boarding it identifies which data it consumes and which data it provides. It is independent of Near-RT RIC and may be provided by any third party. The E2 interface enables a direct association between xApp and RAN functionalities. - -**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 functions (such as 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. - -**Solution Provider:** An application developer who delivers applications to Service Providers. [i.22] - -**Service Provider:** A network provider who is planning to deploy applications into their network. [i.22] - -## 3.2 Symbols - -Void. - -## 3.3 Abbreviations - -For the purposes of the present document, the following abbreviations apply: - -| | | -|-------|---------------------------------------------------------| -| API | Application Programming Interface | -| AI/ML | Artificial Intelligence/Machine Learning | -| CP | Control Plane | -| DoS | Denial of Service | -| DTLS | Datagram Transport Layer Security | -| eNB | e NodeB (applies to LTE) | -| E2SM | E2 Service Model | -| FCAPS | Fault, Configuration, Accounting, Performance, Security | -| FM | Fault Management | -| gNB | g NodeB (applies to NR) | -| IPsec | Internet Protocol Security | -| JWS | JSON Web Signature | - -| | | -|-------------|---------------------------------------------------------------------------------------| -| JWT | JSON Web Token | -| LCM | Life-Cycle Management | -| MEC | Multi-access Edge Computing | -| MIMO | Multiple Input Multiple Output | -| Near-RT RIC | Near-real-time RAN Intelligent Controller | -| NIB | Network Information Base | -| Non-RT RIC | Non-real-time RAN Intelligent Controller | -| O-CU | O-RAN Central Unit | -| O-DU | O-RAN Distributed Unit | -| O-RU | O-RAN Radio Unit | -| PM | Performance Management | -| QoS | Quality of Service | -| QoE | Quality of Experience | -| RAIE | RAN Analytic Information Exposure | -| RAI API | RAN Analytics Information API, internal to the Near-RT RIC | -| RAN | Radio Access Network | -| RIC | RAN Intelligent Controller | -| R-NIB | Radio-Network Information Base | -| RRM | Radio Resource Management | -| SBA | Service Based Architecture | -| SDL | Share Data Layer | -| SMO | Service Management and Orchestration | -| TLS | Transport Layer Security | -| UE | User Equipment | -| UE-NIB | UE-Network Information Base | -| UP | User Plane | -| Y1 API | RAN Analytics Information API, for consumers outside of the Near-RT RIC | -| Y1T | Y1 API Termination, i.e. Near-RT RIC platform function implementing a Y1 API provider | - -# 4 RIC background, concepts and assumptions - -## 4.1 Introduction - -The RIC architecture consists of the Non-RT RIC, which deals with control loops of more than 1 second, and the Near-RT RIC, with control loops in the order of 10 ms to 1s [i.3]. The Non-RT RIC is embedded in the Service and Management Orchestration function and hosts rApps to provide policy-based guidance, machine learning model management and enrichment information to the Near-RT RIC function for the purpose of RAN optimization [i.4]. The Near-RT RIC is a logical function that enables near real-time control and optimization of E2 Nodes functions and resources, steered via the policies and enrichment data provided from the Non-RT RIC [i.3]. - -## 4.2 Near-RT RIC architecture - -The following diagram shows the building blocks of the Near-RT RIC internal architecture. For more detailed descriptions of the architecture and platform functions, see WG3 Near-RT RIC Architecture specification [i.3]. - -![Figure 4.2-1: Near-RT RIC Internal Architecture diagram. The diagram shows a layered architecture. At the top is the Service Management and Orchestration (SMO) block, which contains the Non-RT RIC. The SMO connects to the Near-RT RIC via the O1 and A1 interfaces. The Near-RT RIC block contains several internal components: O1 Termination, A1 Termination, and Y1 Termination. The Y1 Termination connects to Y1 Consumers. Below the terminations is a dashed box labeled 'Near-RT RIC APIs for xApp' containing xApp 1, xApp 2, ..., xApp N. Below the xApps is the Messaging Infrastructure. To the left of the Messaging Infrastructure is the API Enablement block, which includes Conflict Mitigation, xApp Subscription Management, Management Function, Security, AI/ML Support, and xApp Repository Function. Below the Messaging Infrastructure is the Shared Data Layer, which includes a Database and E2 Termination. The E2 Termination connects to the E2 Nodes at the bottom of the diagram.](853f59c89931a666c07903b31d098277_img.jpg) - -Figure 4.2-1: Near-RT RIC Internal Architecture diagram. The diagram shows a layered architecture. At the top is the Service Management and Orchestration (SMO) block, which contains the Non-RT RIC. The SMO connects to the Near-RT RIC via the O1 and A1 interfaces. The Near-RT RIC block contains several internal components: O1 Termination, A1 Termination, and Y1 Termination. The Y1 Termination connects to Y1 Consumers. Below the terminations is a dashed box labeled 'Near-RT RIC APIs for xApp' containing xApp 1, xApp 2, ..., xApp N. Below the xApps is the Messaging Infrastructure. To the left of the Messaging Infrastructure is the API Enablement block, which includes Conflict Mitigation, xApp Subscription Management, Management Function, Security, AI/ML Support, and xApp Repository Function. Below the Messaging Infrastructure is the Shared Data Layer, which includes a Database and E2 Termination. The E2 Termination connects to the E2 Nodes at the bottom of the diagram. - -Figure 4.2-1: Near-RT RIC Internal Architecture - -- **Interface Termination** for E2, A1, O1, Y1 -- **xApp:** application that runs on the Near-RT RIC to provide desired RAN functionality -- **Messaging infrastructure:** provides low-latency message delivery service b/t Near-RT RIC internal endpoints -- **Conflict mitigation:** resolves potentially overlapping or conflicting requests from multiple xApps - -- **Subscription management:** manages subscriptions from xApps to E2 Nodes and enforces authorization of policies -- **Management services:** life-cycle management of xApps (onboarding, deployment, resource management, and termination) and FCAPS management of Near-RT RIC (logging, tracing, metrics collection) -- **Security:** provides the security scheme for the xApps. One of the targets of this function is to prevent malicious xApps from abusing radio network information (e.g. exporting to unauthorized external systems) and/or control capabilities over RAN functions - -NOTE: The Security function is a placeholder in Near-RT RIC architecture and has not been specified yet. The requirements and solutions proposed in this study will support the specification of this function. - -- **AI/ML support:** provides data ingestion and preparation for xApps and AI/ML training for xApps -- **xApp Repository Function:** performs selection of xApps for A1 message routing and provides policy types supported in Near-RT RIC to the A1 termination function -- **Shared Data Layer (SDL):** API for accessing shared data storage -- **Database:** UE-NIB database contains a list of UEs and associated data, and Radio-NIB database stores configurations and information relating to the connected E2 Nodes -- **API Enablement:** support for registration, discovery and consumption of Near-RT RIC APIs -- **Y1 Consumers:** communicate via Y1 interface and consume RAN analytics information service(s) from Near-RT RIC - -## 4.3 Interfaces - -**E2:** Interface between the Near-RT RIC and the E2 Nodes (O-DU, O-CU-UP, O-CU-CP, O-eNB) [i.5] - -**O1:** Interface between the SMO and O-RAN Managed Functions (Near-RT RIC, O-RU, O-DU, O-CU-UP, O-CU-CP, O-eNB) [i.6][i.7][i.8] - -**A1:** Interface between the Non-RT RIC at the SMO and the Near-RT RIC [i.9] - -**Y1:** communicates with Y1 consumers via Y1 interface and exposes RAN analytics information service(s) from Near-RT RIC. - -## 4.4 xApps - -As per definition in [i.3], an xApp is an application designed to run on Near-RT RIC. It may consist of one or more microservices and at the point of on-boarding it identifies which data it consumes and which data it provides. It is independent of Near-RT RIC and may be provided by any third party. The E2 interface enables a direct association between xApp and RAN functionalities. - -From security viewpoint the following requirements [i.3] are key aspects to take into consideration in this study, and will be developed in subsequent key issues and solutions: - -- xApps shall communicate with Near-RT RIC platform via Near-RT RIC APIs. -- xApps shall use Near-RT RIC APIs to make use of the Information Elements (IEs) **only** of the E2 Service Models (E2SM) that are associated with it. - -NOTE 1: E2SM describes the functions in the E2 Node which may be controlled by the Near-RT RIC and corresponding procedures. - -- xApp shall register the APIs it produces. - -NOTE 2: xApps can also act as service producers (see [i.3], 6A.1) - -- xApp shall be capable of discovering the Near-RT RIC APIs they consume -- The platform will consider the level of trust related to the xApp, e.g. 3rd party xApp, RIC-owned xApp (i.e. xApp provided by the RIC vendor) - -## 4.5 Near-RT RIC APIs - -The following diagram [i.3] provides a representation of the APIs involved in Near-RT RIC. - -![Figure 4.5-1: Overview of Near-RT RIC APIs. The diagram shows the internal architecture of a Near-RT RIC. At the top is the 'A1 Termination' block, connected to 'A1 Related APIs'. Below it is a stack of 'xApps' (labeled xApp #1, xApp #2, ..., xApp #n). At the bottom is the 'E2 Termination / Conflict Mitigation / xApp Subscription Management' block, connected to 'E2 Related APIs'. On the left, 'API Enablement' and 'Shared Data Layer' blocks are shown, with 'Enablement APIs' and 'SDL APIs' respectively. On the right, 'O1 Termination / Management Service' and 'Management APIs' are shown. All components are enclosed in a dashed box labeled 'Near-RT RIC'. At the very bottom, a 'Framework for Transactions on APIs' is indicated.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) - -Figure 4.5-1: Overview of Near-RT RIC APIs. The diagram shows the internal architecture of a Near-RT RIC. At the top is the 'A1 Termination' block, connected to 'A1 Related APIs'. Below it is a stack of 'xApps' (labeled xApp #1, xApp #2, ..., xApp #n). At the bottom is the 'E2 Termination / Conflict Mitigation / xApp Subscription Management' block, connected to 'E2 Related APIs'. On the left, 'API Enablement' and 'Shared Data Layer' blocks are shown, with 'Enablement APIs' and 'SDL APIs' respectively. On the right, 'O1 Termination / Management Service' and 'Management APIs' are shown. All components are enclosed in a dashed box labeled 'Near-RT RIC'. At the very bottom, a 'Framework for Transactions on APIs' is indicated. - -Figure 4.5-1: Overview of Near-RT RIC APIs - -- **A1 related APIs:** APIs allowing to access A1 related functionality. - - o **Policy Enforcement API** (transactional) - - o **Enrichment information API** (transactional) -- **E2 related APIs:** APIs allowing to access E2 related functionality and associated xApp Subscription Management and Conflict Mitigation functionality. - - o **E2 Subscription API** (transactional) - - o **E2 Guidance** (transactional) - - o **E2 Indication** (time critical, uni-streaming) - - o **E2 Control** (time critical, bi-streaming) -- **Management APIs:** APIs allowing to access management related functionality. They are used for services such as O1 Termination, management services and logging, tracing, metrics collection. - - o **ML model related APIs** ([i.3], clause 6A.2.7) - -- **FCAPS related APIs (transactional):** - - **xApp Registration API** - - **xApp Deregistration API** - - **Configuration API** - - **PM (Performance Management) API** - - **FM (Fault Management) API** -- **SDL API (transactional + Uni-streaming):** API allowing to access Shared Data Layer related functionalities (store/fetch/notify/modify/push/...) over R-NIB, UE-NIB, other data in the database. -- **Enablement APIs (transactional):** APIs between xApps and API enablement functionality. - - **Registration API.** Enabling the API producer to register the APIs it produces - - **Discovery API.** Enabling the discovery of the Near-RT RIC APIs by the xApps - - **Subscription API.** Enabling the subscription/un-subscription to API-related events and event notification. - -# --- 5 Key Issues - -## 5.1 Introduction - -This clause details the key issues identified for security aspects related to the Near-RT RIC architecture, relevant interfaces, xApps and APIs. Each key issue defines the background to the issue, defines the threats related to the issue and proposes requirements that resolve or mitigate the key issue. - -## 5.2 Key Issue #1: Malicious xApps deployed on the Near-RT RIC - -### 5.2.1 Key issue detail - -xApps on the Near-RT RIC can collect near real-time information from E2 Nodes and influence behavior of E2 Nodes thereby impacting cell performance and delivery of services to a group of UEs or a single UE. The security requirements for onboarding and hosting xApps should be defined to reduce the risk of unauthorized, untrusted, or malicious xApps to be deployed into the Near-RT RIC. - -Malicious xApps could be onboarded onto the Near-RT RIC with the intent of manipulating or negatively impacting the delivery of services to subscribers, the RAN, or the core network. Malicious xApps could also be onboarded onto the Near-RT RIC with the intent of accessing, manipulating or negatively impacting the privacy of subscribers, the RAN or the core network. - -This threat has been identified in O-RAN Threat Model [i.1] as Threat ID T-NEAR-RT-01. - -### 5.2.2 Security threats - -The security threats associated with the onboarding and deployment of malicious xApps include: - -- Malicious xApps attaining unauthorized access to the Near-RT RIC and E2 Nodes -- Malicious xApps abusing radio network information and control capabilities over RAN functions -- Malicious xApp impacting service for a subscriber or a dedicated area -- Malicious xApp exploiting UE identification, tracking UE location and changing UE slice priority - -### 5.2.3 Potential security requirements - -xApps shall be authenticated during onboarding using a signature that is generated by the xApp Solution Provider and validated by the Service Provider. - -xApps shall be validated during Registration to the Near-RT RIC platform using signatures from both the Service Provider and the xApp Solution Provider. - -## 5.3 Key Issue #2: Compromised xApp - -### 5.3.1 Key issue detail - -Vulnerabilities can potentially exist in any xApp. Those can be e.g.: - -- Security misconfiguration, such as enabled but unnecessary protocols -- Weak or misconfigured authentication and authorization -- A malicious xApp an untrusted source may intentionally provide -- A backdoor intentionally inserted in the xApp by a trusted source -- An attacker submitting requests without prior authentication and authorization by executing an injection attack to manipulate configurations, access logs, perform remote code execution, etc - -If attackers can find an exploitable xApp, they can disrupt the offered network service and potentially take over another xApp or the Near-RT RIC. The actual consequences may vary. For example, an attacker may gain the ability to alter data transmitted by any accessible API, extract sensitive information, etc. - -### 5.3.2 Security Threats - -The security threats associated with compromised xApps include: - -- Security misconfiguration -- Weak authentication and authorization -- Malicious xApps from an untrusted source -- Backdoors in trusted xApps -- Vulnerabilities in trusted apps - -### 5.3.3 Potential security requirements - -**Requirement:** xApps images shall be authenticated during onboarding using a signature that is generated by the xApp Solution Provider and validated by the Service/Cloud Provider and telco operator. - -**Requirement:** xApps instances shall be validated during Registration to the Near-RT RIC platform using signatures from both the Service/Cloud Provider and the xApp Solution Provider. Signatures made from certificates reaching the end of their lifetime shall be renewed before the certificate times out (signatures provided by the xApp Solution Provider might be ignored if the signature of the Service/Cloud Provider is valid). - -**Recommendation:** xApps should be hardened by the vendor, and this hardening should be tested by the service provider, using a well-defined standard, e.g., using penetration tests - -**Requirement:** xApp APIs shall be provided with proper Authentication/Authorization schemas. - -**Recommendation:** prevent supply chain attacks, e.g., as defined in [i.24] - -## 5.4 Key Issue #3: Conflicting xApps - -### 5.4.1 Key issue detail - -xApps can change RAN parameters to optimize a specific network metric, which could result in conflicting actions between xApps. Conflicting xApps can unintentionally or maliciously impact O-RAN system functions such as mobility management, admission controls, radio resource control, and load balancing to degrade the performance or availability of the network. - -The functional split between the Near-RT RIC and the E2-Node depends on the available xApps and the capabilities exposed by the O-gNB. This can create possible conflicts between the decisions taken by the Near-RT RIC and the O-gNB that could lead to instability in the network, which introduces vulnerabilities that could be exploited by threat actors. [i.1] - -This threat has been identified in O-RAN Threat Model [i.1] as Threat ID T-xApp-02. - -### 5.4.2 Security threats - -The security threats associated with conflicting xApps include: - -- DoS from an xApp intentionally creating RRM decisions that conflict with gNB internal decisions -- Degradation of performance from an xApp intentionally creating RRM decisions that conflict with other xApp decisions - -### 5.4.3 Potential security requirements - -The solution should make use of the existing, but currently optional, E2 Guidance Request Procedure during xApp Registration to mitigate conflicts arising from new xApps. The purpose of the E2 Guidance procedures is to allow xApps to obtain guidance from the Conflict Mitigation function in the Near-RT RIC. The Conflict Mitigation function is intended to resolve potentially overlapping or conflicting requests from multiple xApps ([i.3], clause 6.2.3). - -## 5.5 Key Issue #4: Isolation between xApps - -### 5.5.1 Key issue detail - -The Near-RT RIC enables near real time control and optimization of RAN elements and resources via fine-grained data collection and actions over E2 interface, and includes open interfaces (A1, O1) to the management and orchestration system (SMO). This will be achieved using a collection of xApps, with each xApp providing a specific functionality by - -consuming a specific subset of data or producing data for other xApps or Near-RT RIC platform. To provide its desired functionality, the xApps would interact with other Near-RT RIC platform components. - -In a multi-vendor environment, where 3rd party xApps and those provided by the RIC vendor are deployed together, an xApp can be used to impact the other co-located xApps/Near-RT RIC platform thus creating a noisy neighbour effect where an xApp can overconsume the underlying shared resources provided by the Near-RT RIC platform like CPU, memory, I/O bandwidth, etc. and can negatively affect the performance of other co-located xApps and potentially other CNFs sharing the same underlying platform. - -It's also possible that xApps have different levels of access to the data and resources available on Near-RT RIC. Appropriate isolation is needed for xApps that have different threat profiles. - -### 5.5.2 Security threats - -Without proper isolation, an xApp can be used to: - -- overconsume the platform resources shared by all xApps, creating a noisy neighbour effect by leaving other co-located xApps with a resource deficit. -- administer DoS attacks on other co-located xApps and impacting service offered by the xApp under attacks -- administer DoS attacks on the Near-RT RIC platform components, impacting the availability of the Near-RT RIC -- administer unauthorised access to sensitive real-time information from RAN, persistent configuration used by the Near-RT RIC to control the RAN -- probe for vulnerabilities in the underlying system hosting the xApps application and use them to administer attacks on another xApps and the platform - -### 5.5.3 Potential security requirements - -**Requirement:** Based on xApps threat profile, the Near-RT RIC platform shall categorise and isolate xApps into different security groups and define security boundaries. Near-RT RIC platform shall cap the resources allocated to xApps make sure that xApps trying to overconsume the resources are quarantined. - -**Requirement:** Access controls shall be established and enforced for accessing critical data in Near-RT RIC - -**Requirement:** Communication between security zones shall require mutual authentication and authorization between communicating xApps - -## 5.6 Key Issue #5: Compromise of ML data pipelines used in Near-RT RIC - -### 5.6.1 Key issue detail - -The Near-RT RIC contains database(s) which contain historic data collected from UE and RAN information. This historic data can be used to train various ML models used in Near-RT RIC. Also, streaming data may be collected from E2 nodes by some ML based xApps, and used either for training ML models or deriving inferences. - -ML data pipelines can consist of several ML models, using one or more sources of data for training as well as inference derivation. xApps can have ML pipelines implemented within, or can be using ML pipelines from another xApps that provide analytics services. - -ML data pipelines can be compromised due to: - -- A potential vulnerability existing in the xApp that implements the ML pipeline -- Poisoning of ML training data due to compromised E2 node(s) -- Poisoning of ML training data due to compromised UE(s) -- Compromised database(s) which store historic data used for ML training -- Compromised interfaces of Near-RT RIC allowing a malicious intruder to alter some of the training data that may be used to train ML models used by xApps - -### 5.6.2 Security threats - -T\_ML\_01 from ORAN Threat Modelling [i.1] is applicable here. - -### 5.6.3 Potential security requirements - -The following security requirements should be considered: - -- Secure data storage, and secure data transfer mechanisms shall be implemented in Near-RT RIC. -- Authenticated and authorized access to data stores shall be implemented in Near-RT RIC. -- Near-RT RIC deployment shall have provision for regular security vulnerability patch updates for xApps. -- Integrity of xApps shall be monitored after installation as well as during runtime on a periodic or need basis. -- O-Cloud security requirements shall be adhered to, in order to ensure that the interfaces feeding data to ML data pipelines are secured. -- Detection of compromised E2 nodes, and filtering ML data pipelines to exclude inputs from such nodes. -- Detection of compromised UE, and filtering ML data pipelines to exclude inputs from such UEs. - -## 5.7 Key Issue #6: Altering the ML learning models used in Near-RT RIC - -### 5.7.1 Key issue detail - -Near-RT RIC hosts a set of xApps, some of which may contain ML based solutions performing inference and/or training processes. - -- ML enabled xApps can hold any required ML models and would be deployed as an integrated function. - - In such cases, if ML models use online training, or transfer learning, or reinforcement learning, or other such mechanisms, it is likely that during runtime, the binary footprint of the models can change for good reasons. However, this makes it a challenge to distinguish between maliciously modified ML models and genuine model changes. -- xApps can also use ML models stored in databases or separate filesystems/storage - - xApps can perform online training of ML models by updating the models in DB, while ensuring that the binary footprint of xApp remains un-changed - -For xApps having embedded ML models, a compromise of ML models is likely due to following reasons: - -- A potential vulnerability existing in xApp -- Security Weakness in APIs exposed by xApps - -- For example, APIs allowing modifications of ML models using transfer learning can allow changes of models by a malicious source, if authentication and authorization for such interfaces are not strong - -For xApps using ML models stored in DB/separate storage, a compromise of ML models is likely due to following reasons: - -- A potential vulnerability existing in xApp leading to compromised ML model updated in the DB -- A potential vulnerability existing in DB security - - Missing or weak authentication and authorization for DB - -Transfer Learning can be implemented in a manner that Non-RT RIC can provide updated ML models to Near-RT RIC via A1 interface. If this interface is compromised, or, if an un-authenticated or un-authorized source is allowed to update ML models in Near-RT RIC, it can lead to unexpected behaviour of ML models. - -### 5.7.2 Security threats - -T\_ML\_02 from ORAN Threat Modelling [i.1] is applicable here. - -An attacker can illegally access a machine learning model and alter its parameters and thereby influence how it produces results. This can lead to wrong prediction and might result in catastrophic decisions if the results of the predictions were being used to make key business decisions. - -Also, an attacker can extract sensitive or confidential data that, through training, are built right into the ML model. - -### 5.7.3 Potential security requirements - -Following security requirements should be considered: - -- Integrity of xApps shall be monitored after installation as well as during runtime on a periodic or need basis. -- Secure data storage, and secure data transfer mechanisms shall be implemented in Near-RT RIC. -- Authenticated and authorized access to data stores shall be implemented in Near-RT RIC. Security measures shall be ensured to allow only authenticated and authorized applications providing ML model updates over the A1 interface. - -## 5.8 Key Issue #7: Data Protection and Privacy in Near-RT RIC Database - -### 5.8.1 Key issue detail - -The Near-RT RIC contains database(s) which contain sensitive UE and RAN information, including history of the network state, configurations related to E2 Nodes, cells, bearers, flows, UE identities, and the mappings between them. Overlayed on top of these databases is the shared data layer (SDL) which enables xApp access. There is currently no model for authentication or authorization for the database(s). The Near-RT RIC requires security mechanisms in place to ensure xApps have authenticated access to the database(s) and may access only parts of the database(s) in which they have permission to access. Adverse effects may result if no security mechanisms are in place, such as manipulation of database information. - -### 5.8.2 Security threats - -xApps that have gained unauthorized access to Near-RT RIC database(s) have the ability to: - -- Perform unauthorized database operations and manipulate database information to impact network service and performance -- Export sensitive data from the Near-RT RIC database(s) (data or user privacy threat) -- Monitor the database for specific information and take an adverse action - -### 5.8.3 Potential security requirements - -Near-RT RIC shall authenticate xApp access to the Near-RT RIC database(s) during SDL registration. - -Near-RT RIC shall provide authorized access to Near-RT RIC database(s). - -## 5.9 Key Issue #8: Onboarding untrusted xApps - -### 5.9.1 Key issue detail - -As per definition in [i.3], an xApp is an application designed to run on Near-RT RIC. It may consist of one or more microservices. It is independent of Near-RT RIC and may be provided by any third party. As part of offering its service to Near RT-RIC, some of the xApp's functionalities include - -- communicating with Near-RT RIC platform via Near-RT RIC API, -- providing the APIs it produces to other xApps and Near-RT RIC, -- collecting near real-time information from E2 Nodes and influence behaviour of E2 Nodes and -- accessing Near-RT RIC Databases (via SDL) which gives access to sensitive information related to UE and RAN - -Onboarding an untrusted third party xApp onto Near-RT RIC can create serious security issues which can compromise the Near-RT RIC functionality, impact the availability of other xApps and have cascading impact on overall performance of ORAN. - -### 5.9.2 Security threats - -Onboarding an untrusted third party xApp onto Near-RT RIC can cause similar or same security threats as a Malicious or Badly configured xApp. Some well-known and easily administered attacks with untrusted xApps are: - -- If the xApp is not from a trusted source or is not maintained by a trusted source, it could contain security vulnerabilities or back doors which could be exploited by the attackers and impact Near-RT RIC functions -- The untrusted/unverified xApp could provide APIs with weak security (weak or no authentication and authorization) and such xApps could be easy target for attackers to break in and propagate lateral movement of attack in the system (towards other xApps). -- The untrusted/unverified xApp could expose more services than required and such xApps could expose a large attack surface to the attackers to break in and gain access, manipulate configurations, access logs, insert back doors -- The untrusted/unverified xApp can be used to sniff sensitive UE information which can be used by attackers or the untrusted/unverified xApp itself for rogue purposes - -### 5.9.3 Potential security requirements - -**Requirement:** The xApp shall be compliant to industry standards for API security (eg : OWASP Top 10) - -**Requirement:** The xApp shall be free of any known software vulnerabilities. - -**Requirement:** The xApp shall be authenticated before the app is onboarded to the cloud platform and registered onto the Near-RT RIC platform - -**Requirement:** The xApp shall support appropriate authorization schemes to make sure that a user accessing its service shall not be able to execute any actions that the user is not authorized for. - -**Requirement:** The xApp shall harden its service offering by making sure that only required services should be exposed to its users. - -## 5.10 Key Issue #9: xApp exploitation via malicious A1 policies - -### 5.10.1 Key issue detail - -The Non-RT RIC defines policies that are provided to the Near-RT RIC over the A1 interface. The purpose of the A1 policies is to guide and optimize the RAN, and the policies inform behavior of xApps in the Near-RT RIC. [i.9] - -Unauthorized access to the Non-RT RIC enables the creation of 'false policies' that can be issued to the Near-RT RIC for enforcement. Existing Near-RT RIC policies could also be modified to achieve a false policy. False policies passed to the Near-RT RIC would be persistent until they were modified or deleted by the Non-RT RIC or the Near-RT RIC power cycles. - -### 5.10.2 Security threats - -False policies can be created to have numerous impacts to the normal performance of the RAN. A single false A1 policy can target a specific UE, groups of UEs, or an entire cell. A false policy could influence the Near-RT RIC to configure the O-DU and O-RU functions to support Denial of Service (DoS) attacks by simply using feedback data to degrade RAN performance. - -False policies could also be used for the purpose of locating a subscriber or group of subscribers. In this case, the false policy would cause the Near-RT RIC to isolate a subscriber in the O-CU. The Near-RT RIC could also use MIMO beamforming in the O-DU and O-RU to isolate a user onto a single beam. The data feedback from the RAN can include UE location or trajectory information from GPS data. The subscriber location would be attained from access to the Non-RT RIC in the SMO function. - -The Near-RT RIC is capable of steering traffic to achieve optimal QoS or QoE performance. A false policy could notionally cause the Near-RT RIC to steer user data to isolate the data in order to facilitate a cyber-attack. - -### 5.10.3 Potential security requirements - -Security protections are defined for the A1 interface and security work is in process for A1 related APIs and the Non-RT RIC. For example, A1 peering should be established with only trusted sources using TLS 1.2, or higher, and PKI X.509 certificates, as specified in [i.19]. TLS also provides confidentiality and integrity protection. Additional Near-RT RIC authentication of the A1 policy may be a consideration later, after the above security protections are defined and evaluated. - -A perimeter security approach may enable an Internal threat actor to conduct a MitM attack on the A1 interface. Security for the Near-RT should take a zero-trust approach in which security controls are implemented at the Near-RT RIC without assumption of a secure perimeter. The Near-RT RIC could implement security controls consistent with a - -zero-trust architecture in which there is no assumption of perimeter defences being provided by other O-RAN functions. For example, the Near-RT RIC could provide checking and validation of policies received from the Non-RT RIC on the A1 interface. - -## 5.11 Key Issue #10: Near-RT RIC APIs authentication - -### 5.11.1 Key issue detail - -Like any software, APIs can be compromised, and data can be intercepted. APIs can be manipulated causing service disruptions and can be subject as well to DoS attacks. Authentication, an essential part of secure communication, ensures that an attribute claimed by a given entity (e.g., its identity) is actually correct. In the context of secure communication between xApps and Near-RT RIC platform, the platform shall authenticate all xApps instances and only provide them with the information and services for which they are authorized through the use of the Near-RT RIC APIs, as a key objective to guarantee the validity of the transferred messages. xApps can also act as service producers, exposing APIs to be consumed by other xApps for example. In that case, the xApps 'producers' shall authenticate the instances interested in consuming those xApp services. Authentication is also a prerequisite for conducting authorization which itself is another key issue for API Security. - -NOTE: using the xApp registration procedure Near-RT platform performs authentication and validation of the xApp, addressed in solution #1, however xApps, as consumers of the services exposed by Near-RT RIC APIs, are not authenticated as per current O-RAN specifications at the time of requesting those services. - -### 5.11.2 Security threats - -Not mutually authenticating xApps and Near-RT RIC platform APIs could potentially allow attackers to perform the following type of attacks [i.17]: - -- Operating malicious xApp claiming to be genuine in order to request certain services (theft of services) or information (data leakage) -- Man in the middle attacks between a genuine xApp and a Near-RT RIC platform API -- Querying network or UE information from a compromised xApp to Near-RT RIC platform (e.g. database via SDL API), thereby leaking potentially sensitive data about network and/or UE (potential privacy issues) -- Subscribing a malicious xApp to services provided by the Near-RT RIC platform, such as API-related events notifications, discovery of APIs, E2SM, etc. - -The use of weak credentials in the process of API authentication can compromise the overall system. The user/password combination isn't considered safe, not only for password related attacks (e.g., brute-force), but also it would represent a high risk to allow xApps, especially 3rd party xApps, to store the user/password combo. This approach would extend the attack surface into xApps side. - -As a reference, OWASP API Security Top 10 report [i.10] indicates that authentication mechanisms are often implemented incorrectly, allowing attackers to compromise authentication tokens or to exploit implementation flaws to assume other use's identities temporarily or permanently. Compromising system's ability to identify the client/user, compromises API security overall. - -### 5.11.3 Potential security requirements - -The communication between xApps and Near-RT RIC platform APIs shall be authenticated at least at the transport layer (for e.g., with mutual TLS). - -At application layer complementary end to end authentication mechanisms based on JSON Web Tokens (JWTs) may be considered as well. - -## 5.12 Key Issue #11: Near-RT RIC APIs authorization - -### 5.12.1 Key issue detail - -Authorization is the function of specifying and enforcing access rights or privileges to certain resources or services. In the actual context of Near-RT RIC, the platform as API producer shall be responsible to specify those rights/privileges for the platform services as resources to the xApps as consumers. In general, an xApp should only have the required set of permissions to perform the actions for which they are authorized, and no more. - -NOTE: xApps can also act as services producers (see [i.3], 6A.1). - -Authorization mechanisms are to be enforced by the Near-RT RIC platform among other in the following key API procedures [i.3]: - -- **Discovery of Near-RT RIC APIs:** The Near-RT RIC platform shall provide means to restrict xApps from discovery of some published APIs based on configuration policies. -- **E2 Subscription API procedure:** The subscription management shall be based on operator's policies. An xApp may be restricted to interface with only a subset of E2 Nodes by such policies. This procedure establishes a set of preconditions that assume authorization processes: - - o xApp has been authorized to issue E2 Subscription API requests - - o xApp has been authorized to request guidance from Conflict mitigation - - o xApp Subscription Management has been configured to permit E2 Subscription API requests only from specific list of xApps. -- **E2 Control API procedure:** Only authorized xApps may initiate RIC control request messages issued by the Near-RT RIC over the E2 interface to the E2 Nodes, for a specific scope (e.g, E2 Node list, RAN function, etc.). -- **E2 Guidance API procedure:** The purpose of this procedure only authorized xApp to obtain guidance from the conflict mitigation platform function prior to initiating an action. -- **SDL API procedures:** The precondition to consume the services exposed by SDL API (e.g, client registration, fetch data, notification, store, etc.) is that xApps have been successfully registered and authorized. - -### 5.12.2 Security threats - -If the API consumers are not authorized by the API producers, attackers (e.g, malicious xApps) would potentially be able to perform the following types of attacks: - -- Abuse and/or theft of services or information (data leakage), requesting and successfully obtaining them from the platform, e.g, in order to extract potentially sensitive information from the network and/or uEs -- Negatively impacting the network performance due to malicious policies over E2 Nodes -- Flooding the platform with resource demanding operations that may lead to a Denial of Service attack - -As a reference, OWASP API Security Top 10 report [i.10] indicates that 'Broken Object Level Authorization' has been the most common and impactful attack on APIs. Even if the application implements a proper infrastructure for authorization checks, developers might forget to use these checks before accessing a sensitive object. Unauthorized access can result in data disclosure to unauthorized parties, data loss, or data manipulation. - -### 5.12.3 Potential security requirements - -Near-RT RIC architecture shall provide an authorization framework for the consumption of the services exposed in the platform APIs by the xApps, that takes operator policies into consideration. The framework should be used by the specified API procedures in [i.3]. - -The authorization framework may need to consider the level of trust related to the xApp (e.g. 3rd party xApp, RIC-owned xApp, etc.) - -## 5.13 Key Issue #12: xAppID abuse - -### 5.13.1 Key issue detail - -As part of the xApp registration procedure into the Near-RT RIC platform, the platform assigns an identity (ID) to the xApp, so called xApp ID. This xApp ID is assumed to be used in xApps API request messages to the Near-RT RIC platform to enable the Near-RT RIC platform to identify the xApp (API service consumer). For the platform to trust the xAppID in the xApps request messages it is necessary to bind this xAppID to some trust anchor. Also, the xAppID needs to be uniquely identifying a single xApp instance. - -### 5.13.2 Security threats - -Not uniquely identifying xApps using a trusted xAppID potentially entails certain threats and potential attacks: - -- A non-unique xAppID might cause misidentification of an xApp, possibly allowing a potentially malicious xApp to request certain services (theft of services), information (data leakage), or alter existing information -- A malicious xApp might use the xAppID assigned to a legitimate xApp to request services or information from Near-RT RIC platform -- A non-unique xApp ID could make it impossible to accurately assign actions to the correct xApp -- A non-unique xApp ID could make it difficult to recognize that a malicious xApp is in the environment - -### 5.13.3 Potential security requirements - -The Near-RT RIC shall provide a procedure to embed the xAppID into a trust anchor (e.g., X.509 certificate) assigned to the xApp used for authentication (mTLS) and for authorization (OAuth – client authentication). - -The Near-RT RIC shall create each xAppID using procedures that avoid duplicates, such as UUID as described in IETF RFC 9562 [i.45]. - -## 5.14 Key Issue #13: Malicious Y1 Consumer - -### 5.14.1 Key issue detail - -Near-RT RIC provides RAN analytics information services via Y1 service interface. These services can be consumed by Y1 consumers by subscribing to or requesting the RAN analytics information via the Y1 service interface. Y1 consumers may be Application Functions (AFs) which are within an O-RAN trusted domain. AFs outside the O-RAN trusted domain may use Y1 services, too. - -Malicious Y1 consumer functions may use their access through the Y1 interface with the intent of accessing, manipulating or negatively impacting the privacy of subscribers, the RAN or the core network. - -### 5.14.2 Security threats - -An attacker may use a malicious Y1 consumer function to - -- attain unauthorized access to the Near-RT RIC -- abuse radio network information -- exploit UE identification or otherwise impact the privacy of subscribers - -In addition, an attacker may perform a man in the middle attack between a genuine Y1 consumer and the Near-RT RIC platform. - -A malicious attacker may also use access to the Y1 interface to mount volumetric and non-volumetric DoS attacks on the Near-RT RIC in order to impact its overall performance. - -### 5.14.3 Potential security requirements - -All Y1 consumers shall be properly authenticated and authorized before access to the Y1 functions get enabled for them at least at the transport layer (for e.g., with mutual TLS and OAuth). All communication through the interface shall be confidentiality and integrity protected. Y1 consumers may be within a PLMN trusted domain. Y1 consumers located outside of the PLMN trusted domain should only be able to use the Y1 services via an exposure function acting as a Y1 Consumer, e.g. as specified in 3GPP TS 23.501, Clause 5.20 [i.33]. - -Additional security measures should be defined such as - -- the Near-RT RIC should provide checking and validation of the data received -- the Near-RT RIC should implement ingress message rate limiting on its Y1 interface - -## 5.15 Key Issue #14: Malicious E2 Node - -### 5.15.1 Key issue detail - -E2 Nodes communicate with the Near -RT RIC through the E2 interface. The Near -RT RIC uses the E2 interface to collect near real-time information and provide value added services. The Near-RT RIC Architecture specification [i.2] clause 8.1 provides further details on the E2 interface. - -A malicious actor may use unauthorized access to E2 Nodes or the E2 interface to mount malicious attacks against the Near-RT RIC. A malicious actor may also abuse compromised E2 Nodes properly authenticating to the Near-RT RIC. - -### 5.15.2 Security threats - -Altered and misleading data sent from a compromised E2 Node to the Near-RT RIC may cause the Near-RT RIC to draw erroneous conclusions on the RANs status which may impact the normal performance of the RAN. An attacker may also obtain information on the status of the RAN and details on the UEs. - -A malicious attacker may also use access to the E2 interface to mount volumetric and non-volumetric DoS attacks on the Near-RT RIC in order to impact its overall performance. - -### 5.15.3 Potential security requirements - -Security protections are defined for the E2 interface as explained in clause 6.9 of the present document. - -Additional security measures should be defined such as - -- the Near-RT RIC should provide checking and validation of the data received - -- the Near-RT RIC should implement ingress message rate limiting on its E2 interface termination - -# 6 Mitigations and Solutions - -## 6.1 Introduction - -This clause will contain any potential Mitigations or Solutions that may be used to address or reduce the risk associated with Key Issues identified in clause 5. - -## 6.2 Solution #1: Secure onboarding and deployment of xApps in Near-RT RIC - -### 6.2.1 Introduction - -xApps are applications that are onboarded to the SMO, deployed on the Near-RT RIC, and then registered in the Near-RT RIC. At each of these steps in the xApp life cycle, security measures can be applied to ensure that the xApp comes from a valid solution provider and is integrity protected. - -### 6.2.2 Solution details - -Onboarding to the SMO is the first step of the xApp life cycle. This solution details the flow from the xApp solution provider to the SMO in Figure 6.2-1. - -![Sequence diagram showing the onboarding process: 1. Signed xApp from Solution Provider to Service Provider; 2. xApp validation by Service Provider; 3. Re-signed xApp from Service Provider to SMO.](7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg) - -``` - -sequenceDiagram - participant XSP as xApp Solution Provider - participant SP as Service Provider - participant SMO as SMO - XSP->>SP: 1. Signed xApp - Note over SP: 2. xApp validation - SP->>SMO: 3. Re-signed xApp - -``` - -Sequence diagram showing the onboarding process: 1. Signed xApp from Solution Provider to Service Provider; 2. xApp validation by Service Provider; 3. Re-signed xApp from Service Provider to SMO. - -Figure 6.2-1: Onboarding xApp to SMO - -1. Solution provider digitally signs the xApp and sends to the Service Provider. -2. The Service Provider validates the digital signature for code integrity, performs a schema check and any operational testing, and then adds their signature to the package. -3. The xApp is published into the catalogue for visibility by the SMO. - -The next step of the xApp life cycle is deployment on the Near-RT RIC, which starts with a request to the SMO from the NF Install Project Manager to deploy new xApps on the RIC, per [i.23]. The SMO maps the RIC variables and instructs the O-Cloud DMS to create the xAPP Deployment and allocate the resources necessary on the Near-RT RIC O-Cloud. The DMS notifies the SMO that the xAPP Deployment has been created and the DMS assigns a Deployment ID which the SMO uses to update its xApp inventory. At the end of the deployment process, the xApp starts the registration process with the Near-RT RIC by sending a registration request to Near-RT RIC Management Services function, per [i.3]. - -This solution proposes a security validation request sent from the Management Services to the Security Function in the Near-RT RIC, as shown in Figure 6.2-2. - -![Sequence diagram showing authentication during deployment process within Near-RT RIC. Management Services sends a security validation request to the Security Function. The Security Function performs xApp security processing (validate Service Provider signature, validate Solution Provider signature, verify certificates are not revoked) and returns a security validation response.](dcb5711d118ae6753b0e12f86eda37db_img.jpg) - -``` - -sequenceDiagram - participant MS as Management Services - participant SF as Security Function - MS->>SF: 1. Security validation request for xApp - Note right of SF: 2. xApp security processing: -a. Validate Service Provider signature -b. Validate Solution Provider signature -c. Verify certificates are not revoked. - SF-->>MS: 3. Security validation response - -``` - -Sequence diagram showing authentication during deployment process within Near-RT RIC. Management Services sends a security validation request to the Security Function. The Security Function performs xApp security processing (validate Service Provider signature, validate Solution Provider signature, verify certificates are not revoked) and returns a security validation response. - -Figure 6.2-2-- Authentication during Deployment Process - -Once the xApp is deployed and has sent a registration request to Management Services: - -1. In the Near-RT RIC, a xApp validation request is sent from Management Services to the Security Function. -2. The Security Function performs the following checks: - - a. Validate the signature of the Service Provider. Confirm the signing Service Provider is the trusted Service Provider. This proves that the valid Service Provider approved the xApp, and that the xApp has not been modified since it was approved for use by the Service Provider. - - b. Validate signature of the xApp Solution Provider. Confirm that the signing xApp Solution Provider is a member of a trusted list of providers. This proves that the xApp came from a trusted provider and has not been modified since the Solution Provider released it. - - c. Verify that neither the Service Provider nor Solution Provider certificates are revoked. This ensures that nothing has changed to imply either signature can no longer be trusted. -3. A security validation response is sent back to Management Services, who can then continue with the xApp registration process if the checks are successful. - -In the context of WG3 Near-RT RIC Architecture specification [i.3], this solution would be added to Figure 9.3.1-1 to fill in details of the authentication and validity checks during registration processing. - -![Extended sequence diagram showing xApp registration procedure. It includes lifelines for SMO, DMS, xApp, O1 Termination, Management Services, and Security Function. The process involves registration request, security validation, response, and optional notification to O1 Termination if SMO has subscribed.](55136bc716146672fc680fa05989f1d2_img.jpg) - -``` - -sequenceDiagram - participant SMO - participant DMS - participant xApp - participant OT as O1 Termination - participant MS as Management Services - participant SF as Security Function - xApp->>MS: 1. <> registration request - MS->>SF: 1a. Security validation request for xApp - Note right of SF: 1b. xApp security processing: -i. Validate Service Provider signature -ii. Validate Solution Provider signature -iii. Verify certificates are not revoked. - SF-->>MS: 1c. Security validation response - Note over MS,OT: 2. continue registration processing if validation passed -assign xApp ID, create xApp MOI - MS-->>xApp: 3. <> registration response - opt If SMO has subscribed - MS->>OT: 4. <> Notify MO Creation - end - -``` - -Extended sequence diagram showing xApp registration procedure. It includes lifelines for SMO, DMS, xApp, O1 Termination, Management Services, and Security Function. The process involves registration request, security validation, response, and optional notification to O1 Termination if SMO has subscribed. - -Figure 6.2-3 – Extended xApp Registration procedure from [i.3] - -### 6.2.3 Evaluation - -By requiring a secure onboarding process with authentication for all xApps, this solution addresses key issues #1, #2, #8. - -## 6.3 Solution #2: Security management of risks in open-source components of Near-RT RIC architecture - -### 6.3.1 Introduction - -O-RAN Near-RT RIC and xApps software components will hugely depend on open-source software and open-source libraries, because of agility, flexibility, community support, cost-effectiveness and many other benefits open-source community provides to meet modern software development. However, on the flip side, there are a number of risks associated with open-source software which needs to be managed. - -Key risks with Near-RT RIC and xApps open-source components: - -- Open-source software provides opportunity for attackers to exploit any known vulnerabilities. A bad actor can use publicly available information to target Near-RT RIC open-source components that have not implemented a patch for known vulnerabilities. -- Non-adaptation of secure software development practices results in unintentional insertion of vulnerable code, propagation of vulnerable code and libraries. -- Intentional backdoors can be inserted by malicious developers. -- Attackers can review the code to identify vulnerabilities. -- Non-compliance of Near-RT RIC open-source license could lead to legal action, affecting business operations and incurring financial damage to consumers. It's critical for consumers to establish processes to manage open-source software license compliance. - -### 6.3.2 Solution details - -Recommended Security best practices to manage open-source software risks are listed in clause 6.3.1 - -#### **Maintain open-source Near-RT RIC components and xApps Inventory** - -- Recommended to have Software Composition Analysis tooling to automatically scan and identify all open-source components, version(s) in use, all package dependencies, libraries, and create an accurate bill of materials (BOM), checks for policy and license compliance, security risks, protect against threats to intellectual property (IP) and version updates. - -#### **Track and analyse open-source Near-RT RIC components and xApps vulnerabilities** - -- Track known vulnerabilities against the inventory of open-source software and libraries. -- Run automated static application security testing to identify known vulnerabilities in open-source software components. -- Create SBOM to facilitate identification of a potential vulnerability in the software product when a CVD is released for an open-source binary, library, or package. -- Perform frequent scanning for known vulnerability or misconfiguration on open-source container image during build phase, within the registry, before deployment and during run time. Recommended to use automated tools integrated into the CI/CD pipeline. -- Perform dynamic application security testing (DAST) which can be tuned and trained to detect run-time vulnerabilities. -- Continuously monitor open-source workload during runtime for any security risks and vulnerabilities. - -- Conduct Penetration testing to identify and resolve critical security defects. - -#### Remediate open-source vulnerabilities - -Software vulnerabilities fall into three categories: publicly known with a patch available for the software; publicly known without a patch (n-day); and not publicly known (0-day). Although measures should be taken to mitigate the risk of n-day and 0-day vulnerabilities, patching publicly known vulnerabilities as quickly as possible significantly reduces the risk of exploitation. - -- Patch critical vulnerabilities in the operational environment within [policy defined, suggested: < 15] days and other vulnerabilities within [policy-defined, suggested: <60] days. -- Refer to [i.30] -- Refer to [i.28] - -#### Continuously monitor for new open-source risks - -- Perform frequent scanning for known vulnerabilities during run time. -- Enable security audit logs for monitoring security events. -- Dynamic application security testing (DAST) which can be tuned and trained to detect run-time vulnerabilities. - -#### Secure Software development practice - -#### Security Best practices based on openssf secure software development practices - -- The project MUST have at least one primary developer who knows how to design secure software. -- At least one of the project's primary developers MUST know of common kinds of errors that lead to vulnerabilities in this kind of software, as well as at least one method to counter or mitigate each of them. -- Use basic good cryptographic practices: - - The software produced by the project MUST use, by default, only cryptographic protocols and algorithms that are publicly published and reviewed by experts (if cryptographic protocols and algorithms are used). - - If the software produced by the project is an application or library, and its primary purpose is not to implement cryptography, then it SHOULD only call on software specifically designed to implement cryptographic functions; it SHOULD NOT re-implement its own. - - All functionality in the software produced by the project that depends on cryptography MUST be implementable using FLOSS. - - The default security mechanisms within the software produced by the project MUST NOT depend on broken cryptographic algorithms (e.g., MD4, MD5, single DES, RC4, Dual\_EC\_DRBG), or use cipher modes that are inappropriate to the context, unless they are necessary to implement an interoperable protocol (where the protocol implemented is the most recent version of that standard broadly supported by the network ecosystem, that ecosystem requires the use of such an algorithm or mode, and that ecosystem does not offer any more secure alternative). The documentation MUST describe any relevant security risks and any known mitigations if these broken algorithms or modes are necessary for an interoperable protocol. - - The default security mechanisms within the software produced by the project SHOULD NOT depend on cryptographic algorithms or modes with known serious weaknesses (e.g., the SHA-1 cryptographic hash algorithm or the CBC mode in SSH). - - The security mechanisms within the software produced by the project SHOULD implement perfect forward secrecy for key agreement protocols so a session key derived from a set of long-term keys cannot be compromised if one of the long-term keys is compromised in the future. - - If the software produced by the project causes the storing of passwords for authentication of external users, the passwords MUST be stored as iterated hashes with a per-user salt by using a key stretching (iterated) algorithm (e.g., Argon2id, Bcrypt, Scrypt, or PBKDF2). - - The security mechanisms within the software produced by the project MUST generate all cryptographic keys and nonces using a cryptographically secure random number generator and MUST NOT do so using generators that are cryptographically insecure. -- Secured delivery against man-in-the-middle (MITM) attacks - - The project MUST use a delivery mechanism that counters MITM attacks. Using https or ssh+scp is acceptable. - -- A cryptographic hash (e.g., a sha1sum) MUST NOT be retrieved over http and used without checking for a cryptographic signature. -- Publicly known vulnerabilities fixed - - There MUST be no unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days. - - Projects SHOULD fix all critical vulnerabilities rapidly after they are reported. -- Static code analysis - - At least one static code analysis tool (beyond compiler warnings and “"saf”" language modes) MUST be applied to any proposed major production release of the software before its release, if there is at least one FLOSS tool that implements this criterion in the selected language. - - It is SUGGESTED that at least one of the static analysis tools used for the static\_analysis criterion include rules or approaches to look for common vulnerabilities in the analyzed language or environment. - - All medium and higher severity exploitable vulnerabilities discovered with static code analysis MUST be fixed in a timely way after they are confirmed. - - It is SUGGESTED that static source code analysis occur on every commit or at least daily. -- Dynamic code analysis - - It is SUGGESTED that at least one dynamic analysis tool be applied to any proposed major production release of the software before its release. - - All medium and higher severity exploitable vulnerabilities discovered with dynamic code analysis MUST be fixed in a timely way after they are confirmed. - -Refer to open-source software best practices: [i.27], [i.26], [i.43] and [i.44]. - -### 6.3.3 Evaluation - -Recommended open-source best practices mitigates Near-RT RIC components and xApps open-source Risks. This solution addresses key issues #1, #2, #5, #6, #8. - -## 6.4 Solution #3: Authentication schema for APIs - -### 6.4.1 Introduction - -REST APIs and gRPC APIs are being considered as valid network solutions for Near-RT RIC API. REST APIs use HTTP and support Transport Layer Security (TLS). REST APIs utilizes JavaScript Object Notation (JSON) as encoding protocol. gRPC APIs use HTTP/2 and support as well TLS. In contrast with REST APIs, gRPC used Protobuf as encoding protocol. - -Time critical E2 related APIs are currently specified to run over SCTP/Protobuf network protocol stack. The security network layer specified for E2 interface is IPSec (SEC-CTL-E2 [i.2]). DTLS is proposed as optional mechanism. - -The solution proposes a basic network authentication schema for transactional APIs (REST and gRPC) based on mutual TLS (mTLS) authentication via X.509 certificates. The use of mTLS serves a dual purpose: - -- Mutual authentication -- Confidentiality protection for the authorization framework (solution #4) - -mTLS is fully aligned with Zero Trust principles of O-RAN security architecture. - -Additionally, the network authentication schema can be complemented by a client authentication schema at application layer, with the use of secure tokens (e.g. JWT, secured with digital signatures based on JWS). Authentication is a prerequisite of the authorization framework, applicable to those APIs. - -For time critical E2 related APIs, secured by IPsec, the solution proposes IKEv2 certificate-based authentication implementation according to O-RAN Security Protocols specification [i.19], which is aligned with 3GPP TS 33.310 specification [i.20] in terms of certificates and IKEv2 profiles. - -### 6.4.2 Solution details - -#### 6.4.2.1 mTLS authentication - -In mTLS both the client (e.g, xApp as API consumer) and the server (e.g, platform as API producer) require a certificate, and both sides authenticate each other using their public/private key pair. The authentication process includes the following steps: - -- the client connects to server and requests access -- the server presents a server certificate -- the client verifies the server certificate -- the client presents a client certificate -- the server verifies the client certificate -- the server grants access -- client and server can exchange information over encrypted TLS connection - -#### 6.4.2.2 Application layer client authentication - -The purpose of the solution is to perform an additional consumer authentication at application layer by the platform, which acts as authorization server and producer. The process is as follows: - -- The API consumer (e.g, xApp) shall attach a signed token in the service request towards the receiving end point, i.e, authorization server, producer. -- The signed token includes the consumer instance ID (e.g, xApp ID), that can be checked against the certificate by the producer -- The signed token includes a timestamp as basis for restriction of its lifetime. It could be even one per service request, this is up to the configuration. - -#### 6.4.2.3 IPsec authentication - -Please refer to O-RAN Security Protocols Specification [i.19], clause 2.5 for supported IPsec capabilities in O-RAN. - -In summary, the following options for IPsec authentication have been specified in [i.19]: - -- Data origin authentication, always enabled -- ESP authentication transforms -- IKE endpoint Identification -- X.509v3 digital certificates provided by a Certificate Authority solution shall be supported -- Pre-shared Keys may be supported -- Key exchange shall be supported via IKEv2, profile as described in [i.21]. - -### 6.4.3 Evaluation - -The proposed authentication schema addresses the key issues #1, #2, #4, #5, #6, #7, #8, #9, #10, #11 - -NOTE: The authentication mechanisms described in the solution may be applicable to other O-RAN parts of the architecture. - -## 6.5 Solution #4: Authorization framework for APIs - -### 6.5.1 Introduction - -The proposed authorization framework is based on OAuth 2.0 as specified in RFC 6749 [i.11]. The OAuth 2.0 authorization framework enables a third-party application (e.g, xApp) to obtain limited access to a service (HTTP), either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its own behalf. - -OAuth 2.0 is the framework adopted in 3GPP 5G Service Based Architecture (SBA) [i.13], where the NRF (Network Resource Function) acts as authorization server. - -MEC specifications [i.15] mandate the use of OAuth 2.0 for authorization of access to RESTful MEC service APIs, and ETSI NFV [i.14] also specifies the same framework for ETSI NFV-MANO APIs. - -The proposed solution implementation in Near-RT RIC architecture of O-RAN is based on the options selected for OAuth 2.0 in both standards developing organizations, 3GPP and ETSI. - -### 6.5.2 Solution details - -The roles defined in OAuth 2.0 has been assigned as follows: - -- Resource owner / Resource server (producer): - - o Near-RT RIC platform modules providing services via APIs. - - o xApp -- Client (consumer): xApp - -NOTE: xApps can also act as services producers (see [i.3], 6A.1). - -- Authorization server: Security function in Near-RT RIC platform - -Grants shall be of the type Client Credentials Grant, as described in clause 4.4 of RFC 6749 [i.11], and represented in the following diagram: - -![Diagram showing Client Authentication (A) and Access Token (B) exchange between a Client and an Authorization Server.](ca1709650afeccbebb6eb9473796e5f5_img.jpg) - -``` - - graph LR - subgraph Client - C[ ] - end - subgraph AS [Authorization Server] - S[ ] - end - C -- "(A) Client Authentication" --> S - S -- "(B) Access Token" --> C - -``` - -Diagram showing Client Authentication (A) and Access Token (B) exchange between a Client and an Authorization Server. - -Figure 6.5-1-- from RFC 6749 - -3GPP SBA specifies in [i.13] that access tokens shall be JSON Web Tokens as described in RFC 7519 [i.18], and are secured with digital signatures or Message Authentication Codes (MAC) based on JSON Web Signature (JWS) as described in RFC 7515 [i.18]. ETSI MEC can also use JWT, that may include scopes of roles to restrict the access to - -MEC services. They may be signed to become tamper proof and encrypted. In general, the use of JWTs as access tokens in Near-RT RIC will depend on the final specification for network API solutions by O-RAN WG3. - -The authorization process entails two verifications: - -- Check whether the consumer is permitted to discover the requested Near-RT RIC API via the Enablement Discovery API during the discovery procedure. This is performed on per consumer granularity by the authorization server -- Check whether the consumer is permitted to access the requested service producer for consuming the service (e.g. SDL fetch data), on a per request type and corresponding subscription. The granularity is determined by the service logic of the producer. - -Management module of Near-RT RIC platform maintains the information of available producers and their supported services, as each of them needs to register the list of services it supports. - -The following schema represents the main steps of the entire authorization process: - -![OAuth 2.0 process in Near-RT RIC diagram showing four steps: 1. Registration of services, 2. Discovery, 3. Delivery of access tokens, 4. Selection.](875c6f4f441fdd3ca7e1908fd1582983_img.jpg) - -The diagram illustrates the OAuth 2.0 process in Near-RT RIC with the following components and steps: - -- Components:** - - Security function OAuth server** and **Management** (part of the Near-RT RIC platform). - - Consumer NF (e.g. xApp)**. - - Near-RT RIC Service** (multiple instances shown). -- Step 1: Registration of services** -Producers (Near-RT RIC platform) register services/capabilities at the Management service. -- Step 2: Discovery (static or via access tokens)** -Consumer obtains a list of candidate NFs via a query to OAuth server. -- Step 3: Delivery of access tokens** -Consumer obtains the scope of accessible services. -- Step 4: Selection** -Consumer selects one of the candidate producers. - -OAuth 2.0 process in Near-RT RIC diagram showing four steps: 1. Registration of services, 2. Discovery, 3. Delivery of access tokens, 4. Selection. - -Figure 6.5-2-- OAuth 2.0 process in Near-RT RIC - -The overall OAuth 2.0 process is foreseen to take place after xApp registration and API discovery procedures specified in Near-RT RIC. The main steps would be: - -- Registration procedure in Management service of Near-RT RIC platform - - o xApp registration - -NOTE 1: Solution #1 adds a security validation feature in this process. - -NOTE 2: During the proposed registration/validation process the platform may check whether the xApp is provided by 3rd party or is RIC-owned application. - -- o APIs registration by the producer via Enablement API -- Enablement API related procedures - - o Discovery - - Basic: Static restriction based on the registration information in database - - Optional: Protection of Discovery services by OAuth 2.0, e.g. in case of 3rd party xApps -- OAuth 2.0 based authorization - -- Services offered by the Near-RT RIC platform are described in the scope of the access token provided to the xApp, required to use the specified APIs. - -### 6.5.3 Evaluation - -The proposed authorization framework addresses the key issues #1, #2, #4, #5, #6, #7, #8, #9, #10, #11 - -NOTE: The authorization mechanisms described in the solution may be applicable to other O-RAN parts of the architecture. - -## 6.6 Solution #5: Near-RT RIC database and SDL access control mechanisms - -### 6.6.1 Introduction - -OAuth 2.0 as described in Solution 4 is used to ensure authorized xApp access to SDL API. Additional steps need to be implemented to control granularity for the database access and that is considered in this solution. - -This solution implements Role-Based Access Control (RBAC) to control and restrict xApp access to the information stored in the Near-RT RIC database(s) and accessible via SDL APIs. Under RBAC, xApps would access the database(s) according to their assigned role, and the assigned role determines what operations the xApp can perform on what database. - -### 6.6.2 Solution details - -The solution is comprised of separate steps during the Onboarding to SMO process and during the SDL Registration process. RBAC roles are assigned during the onboarding process where privileges are defined by the xApp Solution Provider by a xApp database “token” and vetted by the Service Provider. The token needs granularity for data and operations in order to control access. - -![Sequence diagram showing the xApp database token during onboarding. The diagram involves three main entities: xApp Solution Provider (blue box), Service Provider (green box), and SMO (yellow box). The xApp Solution Provider contains two 'Solution Provider' boxes. The Service Provider contains two 'SP' boxes. The SMO contains two 'SMO' boxes. The sequence of messages is: 1. xApp database 'token' from the top Solution Provider to the top SP; 2. Validates xApp database 'token' (self-message) from the top SP to itself; 3. xApp database 'token' from the top SP to the top SMO.](1dc5e74b1032f935e1b1ea3a9c876ac6_img.jpg) - -``` - -sequenceDiagram - participant xApp Solution Provider - participant Service Provider - participant SMO - Note left of xApp Solution Provider: xApp Solution Provider - Note right of Service Provider: Service Provider - Note right of SMO: SMO - xApp Solution Provider->>Service Provider: 1. xApp database "token" - Service Provider->>Service Provider: 2. Validates xApp database "token" - Service Provider->>SMO: 3. xApp database "token" - -``` - -Sequence diagram showing the xApp database token during onboarding. The diagram involves three main entities: xApp Solution Provider (blue box), Service Provider (green box), and SMO (yellow box). The xApp Solution Provider contains two 'Solution Provider' boxes. The Service Provider contains two 'SP' boxes. The SMO contains two 'SMO' boxes. The sequence of messages is: 1. xApp database 'token' from the top Solution Provider to the top SP; 2. Validates xApp database 'token' (self-message) from the top SP to itself; 3. xApp database 'token' from the top SP to the top SMO. - -Figure 6.6-1-- xApp database token during onboarding - -As part of the xApp onboarding to SMO process: - -1. The xApp Solution Provider generates a database “token” that declares what kind of database access and operations the xApp would need. This is sent to the Service Provider along with the xApp. -2. The Service Provider vets the proposed database access and operations during xApp validation by agreeing to the access rights requested by the xApp. -3. The database “token” is passed to the SMO when the xApp is onboarded. - -Before accessing the database, the xApp must register with the SDL using the SDL Client Registration procedure. This solution adds in an access authorization step before the xApp is allowed to register with the SDL. The Security Function uses the xApp database token to identify which roles the xApp is authorized for. - -![Sequence diagram showing the Modified SDL Client Registration Procedure. The diagram is titled 'Near-RT RIC Platform' and includes components: xApp, SDL, Security Function, and Database. The sequence of messages is: 1. xApp sends 'SDL Client Registration request' to SDL; 1a. SDL sends 'Client authorization request' to Security Function; 1b. Security Function performs access authorization for xApp (highlighted in yellow); 1c. Security Function sends 'Client authorization response' to SDL; 2. SDL sends 'Register to Database (if successful)' to Database; 3. SDL sends 'SDL Client Registration response' back to xApp.](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) - -Sequence diagram showing the Modified SDL Client Registration Procedure. The diagram is titled 'Near-RT RIC Platform' and includes components: xApp, SDL, Security Function, and Database. The sequence of messages is: 1. xApp sends 'SDL Client Registration request' to SDL; 1a. SDL sends 'Client authorization request' to Security Function; 1b. Security Function performs access authorization for xApp (highlighted in yellow); 1c. Security Function sends 'Client authorization response' to SDL; 2. SDL sends 'Register to Database (if successful)' to Database; 3. SDL sends 'SDL Client Registration response' back to xApp. - -Figure 6.6-2 – Modified SDL Client Registration Procedure from [i.3] - -1. The xApp sends SDL Client Registration request to the SDL to access the database in the Near-RT RIC Platform. - - a. After the receipt of the request, the SDL sends a client authorization request to the Security Function. - - b. The Security Function performs access authorization for the xApp by comparing the database “token” from the xApp with the one validated by the Service Provider. After verification, the security function will assign the xApp a role based on the token. - - c. The Security Function sends a client authorization response to SDL. -2. SDL arranges with the database the permission for the xApp to access the database (if authentication is successful). -3. The SDL sends the response of successful or failed registration to the xApp. - -### 6.6.3 Evaluation - -This solution addresses key issue #7 Data protection and privacy in Near-RT RIC Database(s), and key issues #4, #5, #6. - -## 6.7 Solution #6: Security Logging (part of FCAPS) - -NOTE: Security Logging will be tackled in dedicated Work Item study to Security Log Management within O-RAN Security Work Group (WG11). - -### 6.7.1 Introduction - -Void - -### 6.7.2 Solution details - -Void - -### 6.7.3 Evaluation - -*Void* - -## 6.8 Solution #7: Access control mechanism for API repository/registry - -### 6.8.1 Introduction - -Near-RT RIC architecture specification [i.3] provides the following requirement in clause 5.1.3: *'Near-RT RIC shall provide means to restrict xApps from discovery some published APIs based on configured policies.'* - -The same specification in clause 6.2.8 describes the API Enablement function, which provides the discovery service as well as repository/registry services for the Near-RT RIC APIs. - -*API Enablement provides support for registration, discovery and consumption of Near-RT RIC APIs within the Near-RT RIC scope. In particular, the API enablement services include:* - -- Repository / Registry services for the Near-RT RIC APIs; -- Services that allow discovery of the registered Near-RT RIC APIs; -- Services to authenticate xApps for use of the Near-RT RIC APIs; -- Services that enable generic subscription and event notification; -- Means to avoid compatibility clashes between xApps and the services they access. - -*The API enablement services can be accessed by the xApps via one or more enablement APIs.* - -NOTE: The provided enablement APIs may need to consider the level of trust related to the xApp (e.g. 3rd party xApp, RIC-owned xApp, etc.) - -The proposed solution addresses: - -- The access control to API enablement function providing API authentication and authorization mechanisms. -- The level of trust related to the xApp via a secure onboarding and deployment of xApps in Near-RT RIC platform. - -### 6.8.2 Solution details - -API authentication (mutual TLS) and authorization (OAuth 2.0) mechanisms, providing the necessary access control to API Enablement function, are described in solutions #3 and #4 of the present document respectively. - -Secure onboarding and deployment procedure of xApps in Near-RT RIC, considers the level of trust related to the xApp by ensuring that the xApp comes from a valid solution provider and is integrity protected. The solution is described in solution #1 of the present document. - -### 6.8.3 Evaluation - -Solutions #1, #3 and #4 of the present address the security requirements related to API Enablement function coming from the Near-RT RIC architecture [i.3] in clauses 5.1.3 and 6.2.8, specifically related to access control and considerations around the level of trust of xApps. Key issues #4, #7, #8, #10 and #11 are addressed by the solution. - -## 6.9 Solution #8: Secure mechanisms for E2 interface - -### 6.9.1 Introduction - -Secure mechanisms for E2 interface are provided in existing WG11 specifications, in particular in O-RAN.WG11.O-RAN-Security-Requirements-Specifications [i.2], clause 5.2.4. - -### 6.9.2 Solution details - -Refer to O-RAN.WG11.O-RAN-Security-Requirements-Specifications [i.2], clause 5.2.4. - -### 6.9.3 Evaluation - -NOTE: Authorization solutions to access E2 nodes and associated services by xApps are for further study. Security mechanisms for E2 interface address key issues #3, #5 and #10. - -## 6.10 Solution #9: Secure mechanisms for A1 interface - -### 6.10.1 Introduction - -The Near-RT RIC receives policies from the Non-RT RIC across the A1 interface. While the A1 interface is considered secure with controls that provide confidentiality, integrity, and mutual authentication, the Near-RT RIC should not assume that the policies are valid and trusted. The Near-RT RIC should provide security built-in compliant with a zero-trust architecture based upon the principle that perimeter security is insufficient to protect against internal threats. - -NOTE: A1 related security mechanisms will be tackled in Non-RT RIC Security technical report (to be released) - -### 6.10.2 Solution details - -Security controls for the Near-RT-RIC that could be implemented as part of its A1 Termination include: - -1. Check policies received on A1 conform to defined schema. See also clause 6.13, Solution #12: A1 Policy Authentication of the present document. -2. Validate policy values for validity and range -3. Provide rate limiting on A1 to prevent resource exhaustion and DoS -4. Implement security logging for each of the above failure events - -### 6.10.3 Evaluation - -The solution addresses key issues #9 and #6 - -## 6.11 Solution #10: Secure mechanisms for O1 interface - -### 6.11.1 Introduction - -Secure mechanisms for O1 interface are provided in existing O-RAN specifications, in particular in O-RAN.WG1.O-RAN-Security-Requirements-Specifications [i.2], clause 5.2.2. - -### 6.11.2 Solution details - -Refer to O-RAN.WG11.O-RAN-Security-Requirements-Specifications [i.2], clause 5.2.2. - -### 6.11.3 Evaluation - -NOTE: xApps are managed via Near-RT RIC, not directly by SMO. Adequacy of existing security mechanisms specified for O1 in management of xApps is for further study. Key issue #4 is addressed by O1 security mechanisms. - -## 6.12 Solution #11: Mitigation for conflicting xApps - -### 6.12.1 Introduction - -WG3 has already defined a process to seek guidance from the Near-RT RIC Conflict Mitigation function prior to initiating a RIC function procedure. The purpose of the Conflict Mitigation function is to resolve potentially overlapping or conflicting request from multiple xApps. These are currently optional procedures [i.3]. - -This guidance can be initiated by 4 different actors at different points in the life cycle of an xApp: - -- Initiated by an authorized xApp -- Initiated by Subscription Management function -- Initiated by message monitoring by the Conflict Mitigation function -- Initiated by Conflict Mitigation function - -For these procedures, the assumption from WG3 is that the Conflict Mitigation function has access to sufficient information to detect a potential conflict and take a decision on an optimal mitigation solution [i.3]. - -### 6.12.2 Solution details - -This solution proposes to make the first procedure, Conflict Mitigation guidance initiated by an authorized xApp, **mandatory** during the E2 Subscription procedure, which is performed at the end of xApp Registration. The E2 Subscription procedure is detailed in [i.3] in clause 9.3.2.1, with the xApp initiated E2 Guidance Request procedure described in clause 9.3.3.1 [i.3]. - -Performing this guidance request during xApp Registration would mitigate conflicts arising from newly deployed xApps. Additional consideration is needed for conflicts arising after deployment, once additional Conflict Mitigation messages and procedures are defined in WG3. - -### 6.12.3 Evaluation - -The solution addresses key issue #3. - -## 6.13 Solution #12: A1 Policy authentication - -### 6.13.1 Introduction - -A1 policies are provided by the Non-RT RIC to the Near-RT RIC over the A1 interface, which already has security protections as defined in [i.2]. The security control for the A1 interface is TLS at the transport layer. In addition, the Near-RT RIC APIs include A1 related APIs for A1 Policy Setup, Update, and Delete procedures [i.3]. Security for these APIs is considered in key issues 10 and 11 and solutions 3, 4, and 13 of this technical report. - -### 6.13.2 Solution details - -For a malicious A1 policy to successfully affect the Near-RT RIC, the policy first must contain a valid policy type supported by the Near-RT RIC, in order to pass the policy type check at the A1 Termination in the Near-RT RIC. The policy must then be mapped to an xApp in the Near-RT RIC. Finally, to exploit an xApp for malicious intent as described in Key Issue 9, the A1 policy needs to have capabilities to execute any of the security threats outlined. The access and knowledge required to complete this sequence of events implies a skilled adversary. - -Securing the endpoints of the A1 interface is another factor in preventing xApp exploitation by malicious A1 policies. This work item (WG3Sec) in WG11 addresses the Near-RT RIC side of the A1 interface. On the other end, the work item to secure the Non-RT RIC in the SMO addresses the security and data privacy of the Non-RT RIC, A1 interface, R1 interface, and external interfaces. - -With the A1 interface itself secured, security of the A1 interface endpoints in progress, A1 related APIs security in progress for authentication and authorization, and the challenges of generating a malicious policy, the likelihood of xApp exploitation via malicious A1 policies is judged to be very low. Further examination of this issue should be performed upon completion of the relevant WG11 work items, but at the moment, no additional A1 policy authentication is deemed necessary. - -### 6.13.3 Evaluation - -This solution describes the protections against the security threats in key issue #9. - -## 6.14 Solution #13: Network Security layer for APIs - -### 6.14.1 Introduction - -The following network layers are being proposed for the Network APIs in Near-RT RIC by O-RAN WG3: - -**Table 6.14-1 network layers proposed for the Network APIs in Near-RT RIC by O-RAN WG3** - -| RIC API | NATURE | NETWORK API SOLUTION (PROTOCOL/ MESSAGE ENCODING) | | -|--------------------------------------------------------------------------------------|-------------------------------|---------------------------------------------------|-------------------| -| | | Default | Alternative (s) | -| A1 related APIs in A1 med towards xApp | | | | -| - Policy Enforcement API | Transactional | gRPC/Protobuf/JSON | | -| - Enrichment information API | Transactional | gRPC/Protobuf/JSON | | -| E2 related APIs in E2T/E2M towards xApp | | [SCTP/ E2related/ E2SM] | | -| - E2 Subscription
- E2 Subscription Delete
[- E2 Subscription Delete Required] | Transactional | SCTP/ Protobuf/ ASN.1 | HTTP/ JSON/ ASN.1 | -| - E2 Guidance | Transactional | SCTP/ Protobuf/ ASN.1 | HTTP/ JSON/ ASN.1 | -| - E2 Indication | Time critical Uni-Streaming | SCTP/ Protobuf/ ASN.1 | | -| - E2 Control | Time critical Bi-Streaming | SCTP/ Protobuf/ ASN.1 | | -| Management APIs | | | | -| - ML model related APIs | Transactional | For future study | | -| - FCAPS related APIs | Transactional | gRPC/Protobuf | | -| SDL APIs (store/ fetch/ notify/ push)
- R-NIB, UE-NIB, Other data | Transactional + Uni-streaming | For future study | | -| Enablement APIs | Transactional | gRPC/Protobuf | HTTP/ JSON | - -This solution proposes to add a security layer in the current network protocol stack for the different APIs specified in Near-RT RIC architecture. - -### 6.14.2 Solution details - -TLS is proposed as a solution for transactional Near-RT RIC APIs based on HTTP or HTTP/2. REST APIs use HTTP and support Transport Layer Security (TLS). REST APIs utilizes JavaScript Object Notation (JSON) as encoding protocol. gRPC APIs use HTTP/2 and support as well TLS. In contrast with REST APIs, gRPC used Protobuf as encoding protocol. Please refer to O-RAN Security Protocols [i.19] for TLS 1.2, TLS 1.3 specifications. - -IPSec is proposed as a preferred solution for time critical uni-streaming and bi-streaming E2 related APIs, which are based on SCTP. Please refer to O-RAN Security Protocols [i.19] for IPsec specifications. - -DTLS is proposed as optional solution for time critical uni-streaming and bi-streaming E2 related APIs, which are based on SCTP. The solution is currently on hold due to limitation of packet size when DTLS is running over SCTP (refer to RFC 6083). Please refer to O-RAN Security Protocols [i.19] for DTLS specifications. - -### 6.14.3 Evaluation - -Network Security layer for APIs shall be considered as a basic requirement in Near-RT RIC architecture. The choice will depend on the selected network protocol stacks. - -The solution addresses key issues #1, #2, #4, #5, #6, #7, #8, #9 and #10. - -## 6.15 Solution #14: Security procedure for xApp registration - -### 6.15.1 Introduction - -As part of the xApp registration procedure into the Near-RT RIC platform, the platform assigns an identity (ID) to the xApp, so called xApp ID. This xApp ID is used in xApp's API request messages to the Near-RT RIC platform to facilitate the Near-RT RIC platform the identification of the xApp (API service consumer). - -The solution proposes a mechanism to enhance the actual registration procedure by embedding the xApp ID into the provided certificate used for authentication (mTLS) and for authorization (OAuth – client authentication) according to the parametrization in [i.19]. - -NOTE 1: The proposed procedure is based on the security procedures specified in 3GPP TS 33.122 (Security aspects of Common API Framework (CAPIF) [i.31] for 3GPP northbound APIs), clause 6.1. Nevertheless, the implementation of the procedure does not require the implementation of the CAPIF framework in O-RAN Near-RT RIC platform. - -In addition, the solution proposes UUID (version 4) [i.45] as xApp ID format, ensuring the uniqueness and randomness of the identifier. - -### 6.15.2 Solution details - -The procedure begins with a secure session between the xApp and Near-RT RIC platform using TLS, which uses server- side certificate authentication. It is assumed that there is a pre-provisioning of necessary parameters for registration during the onboarding/deployment process of the xApp, to allow the latter to reach the Near-RT RIC platform, authenticate it, and present a registration credential (e.g., OAuth 2.0 access token, message digest, etc.) that can be verified by the Near-RT RIC platform. - -NOTE 2: The configuration of the initial pre-provisioned registration credentials in the xApp as part of the deployment process are left to operator implementation. O-Cloud DMS is referred as a possible entity in charge of the provisioning task. - -With the secure session established, the xApp sends a registration request message to the Near-RT RIC platform (Management Function). The message carries the initial credential obtained during the pre-provisioning of the registration information, which may be an OAuth 2.0 access token. If OAuth 2.0 mechanism is used for initial credentials, it should be profiled as specified in [i.19]. Other type of credentials may also be used (e.g., message digest, pre-shared key) - -Figure 6.15.2-1 details the security information flow for the security procedure. The OAuth 2.0 token-based authentication initial registration credential is shown in this example. - -``` -@startuml -participant xapp as "xApp\n[API service consumer]" -participant nfo as "Provisioning system\n(NFO in SMO)" -participant pf as "Near-RT RIC platform \n(Security function, \nRA functionality)\n[API service producer]" -participant pki as "Operator PKI\nCA" -xapp <- nfo : 1. Registration information\n[Near-RT RIC Platform/Security function -\n(Address,Root CA Certificate),\n OAuth 2.0 Access token] -xapp -> pf : 2. TLS (Server side certificate based authentication) -note over xapp -3. Generate the key pair -[private Key, public Key] -endnote -xapp -> pf : 4. Registration request (by xApp instance)\n[OAuth 2.0 access token, xApp -Instance CSR] -note over pf -5. Verify OAuth access token -Generate the xApp ID -endnote -``` - -``` - - POP (Proof of Possession of Private Key) - Embed xApp ID in the CSR (subjectAltname) -endnote -pf -> pki : 6. Enrolment protocol \n(e.g., CMPv2) -pf <- pki : 7. Issued certificate \n(embedded xApp ID) -rnote over pf - 8. Generate xApp MOI -endnote -xapp <- pf : 9. Registration Response (for xApp instance)\n[xApp ID, xApp Certificate, -(service API authentication \nand Authorization information)] -@enduml - -``` - -![Sequence diagram showing the security procedure for xApp registration. The diagram involves four participants: xApp [API service consumer], Provisioning system (NFO in SMO), Near-RT RIC platform (Security function, RA functionality) [API service producer], and Operator PKI CA. The sequence of messages is: 1. Registration information from Provisioning system to xApp; 2. TLS handshake from xApp to Near-RT RIC platform; 3. Key pair generation at xApp; 4. Registration request from xApp to Near-RT RIC platform; 5. Verification and ID generation at Near-RT RIC platform; 6. Enrolment protocol from Near-RT RIC platform to Operator PKI CA; 7. Issued certificate from Operator PKI CA to Near-RT RIC platform; 8. MOI generation at Near-RT RIC platform; 9. Registration response from Near-RT RIC platform to xApp.](32ff77da4286b58c4778033acaa10836_img.jpg) - -``` - -sequenceDiagram - participant xApp as xApp [API service consumer] - participant PS as Provisioning system (NFO in SMO) - participant NRP as Near-RT RIC platform (Security function, RA functionality) [API service producer] - participant PKI as Operator PKI CA - - Note right of PS: 1. Registration information [Near-RT RIC Platform/Security function (Address,Root CA Certificate), OAuth 2.0 Access token] - PS->>xApp: 1. Registration information [Near-RT RIC Platform/Security function (Address,Root CA Certificate), OAuth 2.0 Access token] - Note right of xApp: 2. TLS (Server side certificate based authentication) - xApp->>NRP: 2. TLS (Server side certificate based authentication) - Note right of xApp: 3. Generate the key pair [private Key, public Key] - xApp->>xApp: 3. Generate the key pair [private Key, public Key] - Note right of xApp: 4. Registration request (by xApp instance) [OAuth 2.0 access token, xApp Instance CSR] - xApp->>NRP: 4. Registration request (by xApp instance) [OAuth 2.0 access token, xApp Instance CSR] - Note right of NRP: 5. Verify OAuth access token -Generate the xApp ID -POP (Proof of Possession of Private Key) -Embed xApp ID in the CSR (subjectAltname) - NRP->>PKI: 6. Enrolment protocol (e.g., CMPv2) - PKI->>NRP: 7. Issued certificate (embedded xApp ID) - Note right of NRP: 8. Generate xApp MOI - NRP->>xApp: 9. Registration Response (for xApp instance) [xApp ID, xApp Certificate, (service API authentication and Authorization information)] - -``` - -Sequence diagram showing the security procedure for xApp registration. The diagram involves four participants: xApp [API service consumer], Provisioning system (NFO in SMO), Near-RT RIC platform (Security function, RA functionality) [API service producer], and Operator PKI CA. The sequence of messages is: 1. Registration information from Provisioning system to xApp; 2. TLS handshake from xApp to Near-RT RIC platform; 3. Key pair generation at xApp; 4. Registration request from xApp to Near-RT RIC platform; 5. Verification and ID generation at Near-RT RIC platform; 6. Enrolment protocol from Near-RT RIC platform to Operator PKI CA; 7. Issued certificate from Operator PKI CA to Near-RT RIC platform; 8. MOI generation at Near-RT RIC platform; 9. Registration response from Near-RT RIC platform to xApp. - -Figure 6.15.2-1: Security procedure for xApp registration - -- As a pre-requisite to the registration procedure, the xApp obtains information from a provisioning system (NFO in SMO) during the onboarding/deployment phase in the infrastructure. This information is used to authenticate and establish a secure TLS communication with the Near-RT RIC platform during the registration process. The information includes details of the Near-RT RIC platform (address, Root CA certificate) and includes an initial registration credential (the OAuth 2.0 Access token in the example). - -2. The xApp and Near-RT RIC platform (e.g., Security function and/or Management function) establish a secure session based on TLS (server-side certificate authentication). The xApp uses the information obtained in step 1 to establish the TLS session. - 3. The xApp generates the key pair, i.e., private key and public key - 4. After successful establishment of the TLS session, the xApp instance sends a registration request message to the Near-RT RIC platform along with the pre-provisioned initial registration credential (OAuth 2.0 token in the example), and the xApp instance public key in corresponding CSR (Certificate Signing Request) message. - 5. The Near-RT RIC platform (e.g., via Security function) should validate the initial registration credential and the Management Function of the platform should generate an xApp ID for that particular xApp instance. At the reception of the CSR message from the xApp, the Near-RT RIC platform (e.g., via Security function), acting as a Registration Authority (RA), should prove that the xApp instance is in possession of the private key, and if the proof of possession procedure is positive, it should embed the xApp ID in the CSR message to be forwarded to the Operator CA. The RA may use an enrolment protocol (e.g., CMPv2) to fetch the certificate from the CA -- NOTE: Authentication mechanism between RA and CA are part of the operator PKI implementation. -6. Fetching the certificate (e.g., enrolment protocol such as CMPv2) - 7. Operator CA issues a certificate, embedding the xApp ID in subjectAltName field. The issued certificate by the operator CA will be used by the xApp for subsequent authentication and authorization procedures between the xApp and the Near-RT RIC platform when services/resources are consumed by xApps via APIs. - 8. The Near-RT RIC platform (Management Function) generates an xApp Managed Object Instance (MOI) as specified in [i.3], which may contain the mechanism for authentication (e.g., mTLS) and authorization (e.g., OAuth 2.0) between the xApp and the corresponding module of the Near-RT RIC platform. - 9. The Near-RT RIC platform (Management Function) responds with a xApp registration response message. The response should include the assigned xApp ID, authentication and authorization mechanism if provided in step 5 and xApp certificate. - -The solution proposes for the data type of the xApp ID a string that uniquely identifies the xApp instance. The format of this string should be a Universally Unique Identifier (UUID) version 4 (as described in IETF RFC 9562 [i.45]) - -The solution proposes that subjectAltName in the xApp instance certificate should contain a URI-ID with the URI for the xApp ID as an URN; this URI-ID should contain the xApp ID of the xApp instance using the UUID format as described in IETF RFC 9562 [i.45] (e.g., urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6) - -### 6.15.3 Evaluation - -The following diagram shows a proposal to insert the security procedure in the existing registration procedure specified in O-RAN.WG3.RICARCH, clause 9.1.4, where xApp ID is assigned: - -``` -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -participant smo as "SMO" -Box "O-Cloud" -participant dms as "DMS" -endbox -participant xApp as "xApp" -Box "Near-RT RIC Platform" -participant olt as "OI Termination" -participant ms as "Management Function + Security Function" -endbox -``` - -``` - -dms -> xApp : 0. Pre-provisioning of registration information -xApp <-> ms : TLS session -xApp -> ms : 1. <> registration request (initial credentials) - -rnote over olt, ms - 2. registration processing, validate, - assign xApp ID and bind it to xApp certificate, - create xApp MOI -endnote - -ms -> xApp : 3. <> registration response - -Opt If SMO has subscribed -olt -> smo : 4. <> Notify MOI Creation -End - -@enduml - -``` - -![Sequence diagram showing the xApp registration process with security procedure. Lifelines include SMO, DMS, xApp, O1 Termination, and Management Function + Security Function. The process involves pre-provisioning, TLS session establishment, registration request, processing, response, and optional notification to SMO.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) - -``` - -sequenceDiagram - participant SMO - participant DMS - participant xApp - participant O1 Termination - participant ManagementFunctionSecurityFunction as Management Function + Security Function - - Note right of xApp: O1 Termination - Note right of xApp: Management Function + Security Function - - DMS->>xApp: 0. Pre-provisioning of registration information - xApp->>ManagementFunctionSecurityFunction: TLS session - xApp->>ManagementFunctionSecurityFunction: 1. <> registration request (initial credentials) - Note right of ManagementFunctionSecurityFunction: 2. registration processing, validate, assign xApp ID and bind it to xApp certificate, create xApp MOI - ManagementFunctionSecurityFunction->>xApp: 3. <> registration response - opt If SMO has subscribed - ManagementFunctionSecurityFunction->>DMS: 4. <> Notify MOI Creation - end - -``` - -Sequence diagram showing the xApp registration process with security procedure. Lifelines include SMO, DMS, xApp, O1 Termination, and Management Function + Security Function. The process involves pre-provisioning, TLS session establishment, registration request, processing, response, and optional notification to SMO. - -Figure 6.15.3-1: xApp registration process with Security procedure - -## 6.16 Solution #15: Security requirement proposals for Y1 interface - -### 6.16.1 Introduction - -The O-RAN architecture description document [i.32] explains that Y1 services can only be consumed by Y1 consumers after mutual authentication and authorization. That would imply that the result of the authentication for the duration of communications must be maintained, e.g. by integrity protection and/or encryption with a key that is derived from the authentication and is unknown to the adversary. - -In the ongoing discussion two types of APIs are being discussed: - -- RAI API: API internal to the Near-RT RIC -- Y1 API: API exported by the Y1T (Y1 Termination) to consumers outside of the Near-RT RIC (the Y1 consumers) - -The RAI API is identical to other Near-RT RIC APIs regarding its requirements on security, so key issues #10 (see 5.11) and #11 (see 5.12) as well as solutions #3 (see 6.4), #4 (see 6.5), #7 (see 6.8) and #13 (see 5.14) apply. - -In discussion two types of scenarios are related to the Y1 interface, involving a new entity called Y1T inside the Near RT RIC platform, providing a provider interface to be consumed by external Y1 consumers [i.34]: - -- type 1a: Y1T consumes RAI and exposes externally to Y1 consumers -- type 2b: Near-RT RIC platform generates RAI and exposes it to ETSI MEC, as the source of Radio Network Information Service (RNIS) - -![Diagram showing two scenarios for the Y1 interface security. Scenario type 1a shows Y1 Consumers connected to Y1T via Y1 API(s), with Y1T connected to RAI producer xApp via RAI API(s) inside the Near-RT RIC. Scenario type 2b shows ETSI MEC connected to Y1T via Y1 API(s), with Y1T connected to some platform module via RAI API(s) inside the Near-RT RIC.](be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg) - -``` - -graph TD - subgraph scenario_type_1a [scenario type 1a] - Y1C[Y1 Consumers] -- "Y1 API(s)" --- Y1T1[Y1T] - subgraph NearRT RIC 1a [Near-RT RIC] - Y1T1 -- "RAI API(s)" --- RAIProducer[RAI producer xApp] - end - end - subgraph scenario_type_2b [scenario type 2b] - ETSIMEC[ETSI MEC] -- "Y1 API(s)" --- Y1T2[Y1T] - subgraph NearRT RIC 2b [Near-RT RIC] - Y1T2 -- "RAI API(s)" --- PlatformModule[some platform module] - end - end - -``` - -Diagram showing two scenarios for the Y1 interface security. Scenario type 1a shows Y1 Consumers connected to Y1T via Y1 API(s), with Y1T connected to RAI producer xApp via RAI API(s) inside the Near-RT RIC. Scenario type 2b shows ETSI MEC connected to Y1T via Y1 API(s), with Y1T connected to some platform module via RAI API(s) inside the Near-RT RIC. - -**Figure 6.16-1 Scenarios relevant to the Y1 interface security** - -Based on the ongoing discussion it can be assumed that the topology of the PLMN trust domain should be hidden from the Y1 consumers accessing the Y1 services from outside the PLMN trust domain. - -### 6.16.2 Solution details - -The following proposals for requirements have been derived from [i.31], clause 4. - -- The Y1 interface shall provide mechanisms to authenticate the Y1 consumer and allow for the Y1 consumer to authenticate the Y1 provider (mutual authentication) -- The Y1 interface shall authorize the Y1 consumer before allowing access to any Y1 service -- The Y1 interface shall provide mechanisms to provide confidentiality and integrity protection for all data exchanged -- The Y1 interface shall provide replay- protection for all data exchanged -- The Y1 interface shall enforce the result of the authentication for the duration of communications (e.g. by integrity protection or implicit authentication by encryption with a key that is derived from the authentication and is unknown to the adversary). -- Y1T shall provide mechanisms to hide the topology of the PLMN trust domain from the Y1 consumers accessing the Y1 services from outside the PLMN trust domain -- Further security controls for the Near-RT-RIC that could be implemented as part of its Y1T include: - 1. Validate received values for validity and range - 2. Provide rate limiting on Y1 interface to prevent resource exhaustion and DoS - 3. Implement security logging for each of the above failure events - -### 6.16.3 Evaluation - -This solution addresses key issue #13 of the present document. - -## 6.17 Solution #16: Additional security measures for the E2 interface - -### 6.17.1 Introduction - -The Near-RT RIC receives Near real-time information from the E2 Nodes across the E2 interface. While the E2 interface is considered secure with controls that provide confidentiality, integrity, and mutual authentication, the Near-RT RIC should not assume that the data received is valid and trusted. The Near-RT RIC should provide built-in security compliant with a zero-trust architecture based upon the principle that perimeter security is insufficient to protect against internal threats. - -### 6.17.2 Solution details - -Security controls for the Near-RT-RIC that could be implemented as part of its E2 Termination include: - -1. Validate received values for validity and range -2. Provide rate limiting on E2 interface to prevent resource exhaustion and DoS -3. Implement security logging for each of the above failure events - -### 6.17.3 Evaluation - -The solution addresses key issue #14. - -## 6.18 Solution #17: Standard Identity management of xApp during xApp Registration Procedure. - -### 6.18.1 Introduction - -The Near-RT RIC platform identifies and assigns a xApp ID to the xApp that is being deployed on its platform. However, there is no universally established identity for applications in a cloud native environment that can be used by a program and other mechanisms are more suitable to identify workloads in a cloud native environment. - -The solution proposes to use SPIFFE— Secure Production Identity Framework which is a universal service identity control plane designed for cloud-native and zero-trust based architectures. - -This is also in adherence to **NIST SP 800-207A** [i.41] which mentions that “service identity should not be subjected to spoofing and should be continuously verifiable. An example of workload identity is a SPIFFE ID which is encoded as a Uniform Resource Identifier (URI) and carried in a cryptographically verifiable document called a SPIFFE Verifiable Identity Document (SVID). “ - -SPIRE is a production-ready implementation of SPIFFE APIs that uses Node and workload attestation to securely issue SVIDs [X.509 certificate with SPIFFE ID] to Applications. - -The main modules of the SPIFFE Specifications that are being used in the solution are: - -1. SPIFFE ID: Standard URI format based on RFC 3986 with certain conditions. [EXAMPLE: `spiffe://domain-name/clusterName/namespace/xAppName`] -2. SVID (SPIFFE verifiable Identity document): Cryptographically verifiable document used to prove a service's identity to a peer. It uses existing formats which are X509 certificates and JWT tokens. -3. Trust bundle: The CA certificate chain (root certificate and intermediate certificates) which entities use to verify the SVID. -4. SPIRE Agent and SPIRE Server: SPIRE Agent deployed on the Node where xApp is deployed. SPIRE Server module is deployed in the Near-RT RIC Platform. - -5. Optional Certificate side-car/ [SPIFFE Helper] container along with xApp Instance Pod for handling key and certificate management. - -As part of the xApp registration procedure into the Near-RT RIC platform, the xApp instance will use the SPIFFE ID for registering into the Near-RT RIC platform and will allow the platform to interpret the identity of the xApp instance via the structured SPIFFE ID format. - -![Diagram of Secured xApp Registration Procedure using SPIRE. It shows a Node containing an xApp instance, Certificate sidecar, and SPIRE Agent. The SPIRE Agent sends a 'Secured xApp Registration procedure' message to the Near RT-RIC's SPIRE Server. The Near RT-RIC also contains a RIC App. An SMO is connected to the Near RT-RIC. An Operator CA is connected to the Near RT-RIC. A 'Registration Entries' table is shown on the right.](0f1767577a073167eb9628d72034e083_img.jpg) - -| Registration Entries | | -|-------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------| -| SPIFFE ID | Name=xAppDescriptor
xApp name, vendor, software version, any Operator customized Kubernetes deployment information. | -| spiffe://rakuten.com/clusterName/names pace/xAppName | | - -Diagram of Secured xApp Registration Procedure using SPIRE. It shows a Node containing an xApp instance, Certificate sidecar, and SPIRE Agent. The SPIRE Agent sends a 'Secured xApp Registration procedure' message to the Near RT-RIC's SPIRE Server. The Near RT-RIC also contains a RIC App. An SMO is connected to the Near RT-RIC. An Operator CA is connected to the Near RT-RIC. A 'Registration Entries' table is shown on the right. - -Figure 6.18.1-1: Secured xApp Registration Procedure using SPIRE. - -### 6.18.2 Solution details - -The steps outlining the solution are elaborated below. - -Step 1: Define the Actors and Roles in the xApp Registration Procedure and the Pre-requisite. - -- xApp Instance Pod: xApp Application, (optional) Certificate Side Car originator for certificate and key management. -- SPIRE Agent: To oversee identity management and conduct workload verification within the system. -- SPIRE Server in Near-RT RIC platform: handles the registration-related message from/to xApp. A central component responsible for managing identities and issuing identity credentials. - -Pre-requisites: As a pre-requisite, the xApp Instance Node should have the information details of the Near-RT RIC platform (IP address, Trust anchors) from the provisioning system. - -Step 2: **Node Attestation:** SPIRE Agent and SPIRE Server Secured channel establishment. - -- SPIRE Agent initiates the mTLS with the SPIRE Server for its attestation. SPIRE Agent uses the Node certificates in this step which can be Kubernetes issued or Operator signed certificates. Step 2.ii to 2.iv details the procedures for Nodes Certificates signed by Operator CA. -- SPIRE Server responds back to SPIRE Agent with its own certificate and chain. -- The SPIRE Agent verifies the SPIRE server certificate and responds back with its own node certificate. -- The x509pop node attester plugin at the SPIRE Server verifies that the certificate is rooted to a trusted set of CAs and verifies that node is in possession of private key. The TLS connection gets successfully established. -- In case of Kubernetes issued certificates the additional steps from 2.vi to 2.ix should be followed. -- SPIRE Server shall generate a CSR on behalf of the SPIRE Agent and send to the Operator CA for signing. -- The Operator CA signs the CSR and sends the SVID [X.509 certificate with SPIFFE ID in the SAN field] to the SPIRE Server. - -- 2.viii The SPIRE Server sends the TRUST Bundle to the SPIRE Agent over the existing mTLS connection. -- 2.ix The SPIRE Agent will re-establish the mTLS connection with the newly received SVID. - -NOTE 1: Steps 2.i to 2.iv are for Node Attestation using Node certificates signed by Operator CA. Step 2.v to 2.ix are for Node Attestation using Kubernetes issued Certificates. In such cases Kubernetes CA certificates are pre-configured in the SPIRE server. - -Step3: **Registration entries of Workload in SPIRE Server:** As mentioned in clause 6.2.2, the SMO maps the RIC variables and instructs the O-Cloud DMS to create the xApp Deployment and allocate the resources necessary on the Near-RT RIC. As a part of this procedure, the SMO should send the xApp Registration entries [Management Descriptor] via its O1 interface to the Near-RT RIC. It would map a structured SPIFFE ID to each xApp Instance and facilitate the Near-RT RIC to identify the xApp being deployed and manage its life cycle. - -NOTE 2: Also the SPIRE Server’s Registration API could be exposed to SMO for the SPIRE Server to obtain the workload Registration entries. - -EXAMPLE: Registration Entries of two xApp Instances - -**Table 6.18-1 Example registration entries of two xApp Instances** - -| Registration Entries | | -|--------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| -| SPIFFE ID | 1. Name=xAppDescriptor | -| spiffe://domain-name/clusterName/namespace/xAppName-1 | 2. xApp name-1, vendor, software version, containers, pod-label(label1), and any Operator customized Kubernetes deployment information. | -| spiffe://domain-name/clusterName/namespace/xAppName-2 | 3. xApp name-2, vendor, software version, containers, pod-label(label2), and any Operator customized Kubernetes deployment information. | - -Step 4: **Registration Entries in Agent for SVID Issuance:** SPIRE Server sends the workload (xApp) Registration entry details to the SPIRE agents registered on it. - -Step 5: **Workload Attestation:** Workload xApp Instance is instantiated. Also, an optional component of side-car container can be instantiated to handle the certificate and key management of xApp Instance which offloads the xApp Instance for security related functions. - -- 5.i The xApp Instance Pod communicates with the SPIRE Agent over a unix domain socket-based communication. -- 5.ii The SPIRE Agent utilizes a combination of kernel and user space calls to gather supplementary information about the workload. The SPIRE Agent interrogates the node’s kernel to identify the process ID of the caller. It then invokes any configured workload attester plugins, providing them with the process ID of the workload. This process involves identifying the workload's pod ID through its cgroup association and subsequently obtaining information about the pod. -- 5.iii The agent introspects a workload to determine its properties, based on a set of selectors associated with it. -- 5.iv SPIRE Agent ascertains the identity of the workload by cross-referencing the discovered workload selectors with the Registration entries. - -Step 6. **Generate CSR:** On successful validation in step 5, the SPIRE Agent will generate the CSR and private key for each workload (xApp). The CSRs will have the SPIFFE ID in the SAN field. The SPIFFE agent derives the SPIFFE ID from the Registration entries in Step 4 which uniquely identifies each xApp instance. - -Step 7. SPIRE Agent sends xApp CSRs to the SPIRE server. - -Step 8. **CSR Signing:** SPIRE Server in turns sends the xApp CSRs to the Operator CA for signing. - -Step 9. **Operator PKI:** The Operator CA provides xApp SVID to the SPIRE Server. SVID are X.509 certificates with SPIFFE ID in the SAN field. - -Step 10. SPIRE Server sends xApp SVID [X.509 Certificates with SPIFFE ID] and trust bundle to the SPIRE Agent which it stores in memory for a short duration of time. - -Step 11. **Issuance of SVID:** SPIRE Agent then provides the xApp SVID, trust bundle to the certificate sidecar. The xApp Instance will then use the SVIDs for further communication like xApp Registration towards Near real-time RIC platform. - -NOTE: The xApp instance would establish a secure session with the Near-RT RIC as per the Pre-requisites mentioned in Step 1. - -Step 12: The xApp Instance sends Registration Request toward the Near-RT RIC platform over a secured TLS connection. The Near-RT RIC can validate the SAN field of the X.509 certificate of the xApp Instance against the Registration entries. - -Step 13. On successful validation, the Near-RT RIC platform responds with xApp registration response message with the xApp ID. - -Step 14. Optional: The Near-RT RIC informs SMO about the successful deployment of xApp. - -The solution proposes that xApp ID use a structured ID format of SPIFFE ID which can be interpreted programmatically. The mechanism introduced does not rely on information from xApp to determine the xApp ID. Unix socket-based communication is used for process-to-process communication within the Node. Optional side-car container for key and certificate management reduces the attack surface on the Applications. - -![Sequence diagram titled 'x-App Registration procedure using SPIFFE Framework'. It shows interactions between xApp Instance, SPIRE Agent, SPIRE Server, Near-RT platform, Operator PKI CA, and Processing system (SMO). The process includes Node Attestation, Workload Attestation, Verification of xApp instance, and xApp Registration.](ae375ead8aa673286b534e079e9a8533_img.jpg) - -``` - -sequenceDiagram - participant xApp Instance - participant SPIRE Agent - participant SPIRE Server - participant Near-RT platform - participant Operator PKI CA - participant Processing system (SMO) - - Note right of SPIRE Agent: Initialization - Note right of SPIRE Server: SPIRE Server is initiated on Near-RT RIC - - Note right of SPIRE Agent: Node Attestation - SPIRE Agent->>SPIRE Server: 1.1 Establish TLS connection from SPIRE Agent to SPIRE Server using the node certificate - SPIRE Server-->>SPIRE Agent: 2.1 SPIRE Server responds back to SPIRE Agent with its own certificate and chain - SPIRE Agent->>SPIRE Server: 2.2 The Agent verifies the server certificate and responds back with its own node certificate - SPIRE Server-->>SPIRE Agent: 2.3 The xApp's node attestation dialog at the SPIRE server verifies that the certificate is added to a valid set of CAs and verifies that node is in possession of its private key - - Note right of SPIRE Agent: 2.x mTLS established between Agent and Server - Note right of SPIRE Server: 2.x (Node certificate are self signed or submersible issuer certificate) - SPIRE Server->>Operator PKI CA: 2.4 SPIRE Server sends CSR on behalf of SPIRE Agent to Operator CA with SPIFFE ID embedded in SAN field - Operator PKI CA-->>SPIRE Server: 2.5 Operator CA signs the CSR and issues the certificate to SPIRE Server - SPIRE Server-->>SPIRE Agent: 2.6 SPIRE Server sends the certificate to the SPIRE Agent - SPIRE Agent-->>SPIRE Server: 2.7 SPIRE Agent initiates into connection using the certificate obtained from SPIRE Server - - Note right of SPIRE Server: Request above details of xApp instance in SPIRE node - SPIRE Server->>SPIRE Agent: 4. SPIRE Server sends the registered details to SPIRE Agent over the mTLS connection established - SPIRE Agent-->>Near-RT platform: 5. Registration of xApp instance details over existing ON interface to the SPIRE Server - - Note right of SPIRE Agent: Workload Attestation - SPIRE Agent->>xApp Instance: 6. xApp instance is attached with xApp's helper to run as side car container to xApp instance and are based communication is established - - Note right of SPIRE Agent: Verification of xApp instance - SPIRE Agent->>xApp Instance: 7.1 SPIRE Agent offers to read workload attestation to ascertain the details of the xApp instance - xApp Instance-->>SPIRE Agent: 7.2 The agent re-presents a workload to determine its properties, based on a set of selectors associated with it - SPIRE Agent->>xApp Instance: 7.3 SPIRE Agent ascertain the identity of the workload by cross referencing the discovered workload(xApp) selectors with the Registration entries - - Note right of SPIRE Agent: xApp Registration - SPIRE Agent-->>SPIRE Server: 8. On successful validation of above step, SPIRE agent generates workload(xApp) CSR to SPIRE server - SPIRE Agent->>SPIRE Server: 9. SPIRE Agent sends workload(xApp) CSR to SPIRE server with SPIFFE ID in SAN field - SPIRE Server->>Operator PKI CA: 8. SPIRE server sends the CSR to Operator CA for signing - Operator PKI CA-->>SPIRE Server: 9. Operator CA provides workload's certificate (SVID) - SPIRE Server-->>SPIRE Agent: 10. SPIRE Server sends workload ID and trust bundle to SPIRE Agent which it stores for a short duration of time - SPIRE Agent-->>xApp Instance: 11. SPIRE Agent then provides the xApp SVID trust bundle to the xApp Application - - Note right of SPIRE Server: xApp Registration - SPIRE Agent->>Near-RT platform: 12. Secure session establishment of xApp instance with Near-RT using the SVID - SPIRE Agent->>Near-RT platform: 13. Registration Request message is sent to Near-RT platform which includes xApp Instance ID(SPIFFE-Name), xApp description, xApp version, xApp description - Near-RT platform-->>SPIRE Agent: 14. Successful validation response message sent back to xApp instance after Near-RT Platform identifies the xApp ID with xApp Registration entries - Near-RT platform-->>Processing system (SMO): 15. RIC informs SMO about successful deployment of xApp - -``` - -Sequence diagram titled 'x-App Registration procedure using SPIFFE Framework'. It shows interactions between xApp Instance, SPIRE Agent, SPIRE Server, Near-RT platform, Operator PKI CA, and Processing system (SMO). The process includes Node Attestation, Workload Attestation, Verification of xApp instance, and xApp Registration. - -Figure 6.18.2-1: x-App Registration procedure using SPIFFE Framework. - -### 6.18.3 Evaluation - -The following proposal uses a cloud native solution for service identity management of applications in a cloud native environment. This is in adherence to NIST 800-207A [i.41]. SPIRE is a production-ready implementation of SPIFFE APIs that uses Node and workload attestation to securely issue SVID [X.509 certificate with SPIFFE ID] to - -Applications which can be used for service-service communication. Using SPIRE Agent and SPIRE Server in an O-RAN environment, standardized identities can be provided to Applications like xApp. The SVID issued to xApp can be used to establish a secure connection with the Near-RT RIC platform and the xApp ID can be derived from the SAN field of the X.509 certificate. - -The three open item in the proposal have been listed below: - -1. The RICARCH [i.3] does not currently describe the initial configuration of Registration entries via the O1 interface from the SMO. This procedure would need to be defined. -2. The RICARCH [i.3] clause 9.4.1 assumes that the Near-RT RIC platform creates the xAppID. In this proposal, the Near-RT RIC is obtaining the xApp ID from SMO via Registration entries. Another alternative would be to read the SAN field of the xApp Instance certificate. -3. Handling of private keys in SPIRE Agent and SPIRE Server as an alternative to in-memory and disk-based. - -# --- 7. Conclusions - -## 7.1 Key Issue Solution Mapping - -This document currently contains 14 key issues and 17 solutions proposals to address or reduce the risk associated with the key issues. A mapping of the solutions to the key issues is shown here. - -### **Table 7.1-1 Key Issue to Solution mapping** - -| Key issue | Sol #1 | Sol #2 | Sol #3 | Sol #4 | Sol #5 | Sol #6 | Sol #7 | Sol #8 | Sol #9 | Sol #10 | Sol #11 | Sol #12 | Sol #13 | Sol #14 | Sol #15 | Sol #16 | Sol #17 | -|----------------------------------------|--------|--------|--------|--------|--------|--------|--------|--------|--------|---------|---------|---------|---------|---------|---------|---------|---------| -| KI 1: Malicious xApps | X | X | X | X | | | | | | | | | X | X | | | X | -| KI 2: Compromised xApp | X | X | X | X | | | | | | | | | X | | | | | -| KI 3: Conflicting xApps | | | | | | | | X | | | X | | | | | | | -| KI 4: Compromise of xApp isolation | | | X | X | X | | X | | | X | | | X | | | | | -| KI 5: Compromise of ML data pipelines | | X | X | X | X | | | X | | | | | X | | | | | -| KI 6: Altering ML training models | | X | X | X | X | | | | X | | | | X | | | | | -| KI 7: Database protection and privacy | | | X | X | X | | X | | | | | | X | | | | | -| KI 8: Untrusted xApps | X | X | X | X | | | X | | | | | | X | | | | | -| KI 9: Malicious A1 policies | | | X | X | | | | | X | | | X | X | | | | | -| KI 10: RIC API authentication security | | | X | X | | | X | X | | | | | X | | | | | -| KI 11: RIC API authorization security | | | X | X | | | X | | | | | | | | | | | -| KI 12: xAppID abuse | | | | | | | | | | | | | | X | | | X | -| KI 13: Malicious Y1 Consumer | | | | | | | | | | | | | | | X | | | -| KI 14: Malicious E2 Node | | | | | | | | | | | | | | | | X | | - -# --- 8. Recommendations - -The following key issues have been agreed as contributions in O-RAN Threat Model v.03.00: - -- Key issue #1: Malicious xApps deployed on the Near-RT RIC -- Key issue #10: Near-RT RIC APIs authentication -- Key issue #11: Near-RT RIC APIs authorization - -The following solutions have been agreed as contributions in O-RAN Security Requirement Specification v3.0: - -- Solution #1: Secure onboarding and deployment of xApps in Near-RT RIC -- Solution #3: Authentication schema for APIs -- Solution #4: Authorization framework for APIs - -# Annex: Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|------------------------------------------------------------------------------------------------------| -| 25.11.2025 | 7.00 | Version 7 of technical report | -| 24.11.2025 | 6.04 | void [i.42] | -| 19.11.2025 | 6.03 | set copyright year to 2026 | -| 30.10.2025 | 6.02 | Editorial correction in clause 4.4 | -| 22.10.2025 | 6.01 | Merged NOK-0306, NOK-0323 | -| 09.07.2025 | 6.00 | Version 6 of technical report | -| 19.06.2025 | 5.04 | editorial changes to figure 6.16-1; remove '-' after '-xApps' in document name (in the page headers) | -| 17.06.2025 | 5.03 | Fixed the file designation on the first page and each other pages header | -| 03.06.2025 | 5.02 | Removed MS word developer resetting styles at document reopening, more format updates | -| 02.06.2025 | 5.01 | Format update, merged NIST.AO-0009 | -| 22.11.2023 | 5.00.00 | Version 5 of technical report | -| 20.07.2023 | 4.00.00 | Version 4 of technical report | -| 24.02.2023 | 3.00.00 | Version 3 of technical report | -| 08.11.2022 | 2.00 | Version 2 of technical report | -| 24.04.2022 | 2.0.1 | Update of Near-RT RIC architecture and editorial corrections | -| 23.03.2022 | 2.0.0 | First complete version | -| 06.12.2021 | 1.0.0 | First draft / incomplete | \ No newline at end of file diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/0f1767577a073167eb9628d72034e083_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/0f1767577a073167eb9628d72034e083_img.jpg deleted file mode 100644 index f1d4b4dc5f01569108b1cf0caa54e80ecfce0212..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/0f1767577a073167eb9628d72034e083_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8a9bf11f35ac5195053e35b8b62b56a1ac043466205887146d936fafd739f30b -size 58577 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg deleted file mode 100644 index 1c9bb45213889ee16d3d21374e334305fd90bbeb..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c16db8c03578b6ad981c1053740dcc9f92cf3ac1914eeffdd0f025f3c268e491 -size 60702 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/1dc5e74b1032f935e1b1ea3a9c876ac6_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/1dc5e74b1032f935e1b1ea3a9c876ac6_img.jpg deleted file mode 100644 index 1dd70d8043413d2739aca4cb1fa5361203733bba..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/1dc5e74b1032f935e1b1ea3a9c876ac6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8d62a339e9a88a96e6d852cef596d370cf59aa3f0aad7fc7165acbfd368f5fc3 -size 36422 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/32ff77da4286b58c4778033acaa10836_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/32ff77da4286b58c4778033acaa10836_img.jpg deleted file mode 100644 index 80917c57de4c42556ff38679da24e0d9459843f4..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/32ff77da4286b58c4778033acaa10836_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:40d28e25eb4acbb93a6c494f9665b760cbb2c1161a6bee6b011d498639284170 -size 156177 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index ac3cfab543f601f0f5d5df0819baff17d274a951..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d57cf478d6a7b5f2ccc5b9b3097071939cf811679cce8997ebdcbc5222840d3b -size 4513 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg deleted file mode 100644 index f3ce7351ef1fa0e938d020c23b105d3c727e38f1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a22a694e845b0d380ebfcba904ccc2f8432ddf415712875c9fe3798ae38c368d -size 76794 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/55136bc716146672fc680fa05989f1d2_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/55136bc716146672fc680fa05989f1d2_img.jpg deleted file mode 100644 index a0959948de6a80a46eb318c645cb5e69ea380304..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/55136bc716146672fc680fa05989f1d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:699873cef5d9e1888b9971a16cfaf95103409dd62500b8bc01aabb68b7f4b1c9 -size 87172 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg deleted file mode 100644 index e77c82c23873c8fc23c540d5a4b86c148d405e62..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e0959f2f87ac1cbc9252921881998f57256ee241f8d59e43fc7acdeec3e4d1d1 -size 48804 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg deleted file mode 100644 index f3f4170cb4054d8b94ccf293177830213f30c51b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/7a02de7ed198501f7a4f6ca37c3f28c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b44f9e8de73f3550a0b873530aa894875eee46e2f5e1ea78dc2b07ade26c71bb -size 39168 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index fc4a832461802f2e64de55559518e3000c18d087..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5d0c982cf36453f95eb3b89dc5c4cb1afccd025575cbc828f532f545c0aa229a -size 4518 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/853f59c89931a666c07903b31d098277_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/853f59c89931a666c07903b31d098277_img.jpg deleted file mode 100644 index 5b5f8f7a61808fe950a0e242e1e994d2d1287e54..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/853f59c89931a666c07903b31d098277_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ed503e810ad2f35eb16cf49b9659f98300e26cbc0dc3a4a6db7bc727c20bd498 -size 101548 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/854df8ad60507803253274673f9062cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/875c6f4f441fdd3ca7e1908fd1582983_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/875c6f4f441fdd3ca7e1908fd1582983_img.jpg deleted file mode 100644 index 4477efdb849324cd671d70d508235345eff93d37..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/875c6f4f441fdd3ca7e1908fd1582983_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0b860453a882f60566217b6b386a57caf8d755f550b7a8e71d7af92d5d9e3b83 -size 47248 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index b65c9819ba60bfe19f6cdb95d3075d756b2b6c71..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0cad14f9ac2225f628dcfe49bccbde098fb99facc8adc2cec5e351074d1e3eee -size 4528 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 03b41d4f5bfea06fde27431c3f1c140d6ffecd85..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8d5621dff7f2027c6307bb588d47daa1afaa9e2c9825045fae2d039c3c06c031 -size 4569 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 211b3e3c41561cecff2ae09d96a95a84628eec4d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4bc86e5c6afb3e8822db8737a4f9651627f6881da187c576f75bbb1c6fd828a8 -size 4492 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/ae375ead8aa673286b534e079e9a8533_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/ae375ead8aa673286b534e079e9a8533_img.jpg deleted file mode 100644 index 58d1ac5a5fa3551e2b660c1e921f2d6a4adb327a..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/ae375ead8aa673286b534e079e9a8533_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2a06aedb5eed442f597261cb3d5896ca67f9d01303d24423abd13f0a2ecd3e5e -size 99119 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg deleted file mode 100644 index f160d21923579c4495b47e0cb5c36e20fecbc746..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/be3e5fe8be7cc5a74f67a4b8ac93193d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bafc7d68ea5dc4e56ec949972499b4478c03fb0b5f82d4ee44b89200aab6b915 -size 50666 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/ca1709650afeccbebb6eb9473796e5f5_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/ca1709650afeccbebb6eb9473796e5f5_img.jpg deleted file mode 100644 index 595c45eebdf183e712bc929982b7ba436aa6bd76..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/ca1709650afeccbebb6eb9473796e5f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b06237dbd58a55e21a5b4ad1e6772edefee04e68661f36e27de4245ae257bd37 -size 13215 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index be679815b77877c4e924b9486c09f9f724810c08..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6bba0c6f1cd8911751393c9b51b27412a8996f5483da564cb3c773116f81d8e2 -size 4529 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg deleted file mode 100644 index 1c56c00fe86e4e83bd4c1e9759e189cb7ffb4df3..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/dcb5711d118ae6753b0e12f86eda37db_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7a7945ac32eeafca9ffdf8d7a1ac1ed5ab4a80890c04370dc8f14ce96251fdc0 -size 43188 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index b65c9819ba60bfe19f6cdb95d3075d756b2b6c71..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0cad14f9ac2225f628dcfe49bccbde098fb99facc8adc2cec5e351074d1e3eee -size 4528 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index ac3cfab543f601f0f5d5df0819baff17d274a951..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d57cf478d6a7b5f2ccc5b9b3097071939cf811679cce8997ebdcbc5222840d3b -size 4513 diff --git a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index bf92114d8ed67ea3162486408c189270c81c8b5a..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Security-Near-RT-RIC-xApps.0-R005-v07.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a63c778cf64d636f937b1ce69620edb8d73dbbc5ae5b8067774cdcac2268c004 -size 4506 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/doc.md b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/doc.md deleted file mode 100644 index b965ecd4f5a3a45c094d75f4e2655a7b8ff96d06..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/doc.md +++ /dev/null @@ -1,6057 +0,0 @@ - - -# --- **O-RAN Work Group 11 (Security Work Group)****O-RAN Security Threat Modeling and Risk Assessment** - -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 - -# Contents - -| | | | -|----|-------------------------------------------------------------------|-----| -| 1 | | | -| 2 | List of figures..... | 4 | -| 3 | List of tables..... | 4 | -| 4 | Foreword..... | 5 | -| 5 | Modal verbs terminology..... | 5 | -| 6 | 1 Scope..... | 6 | -| 7 | 2 References..... | 6 | -| 8 | 2.1 Normative references..... | 6 | -| 9 | 2.2 Informative references..... | 6 | -| 10 | 3 Definition of terms, symbols and abbreviations..... | 7 | -| 11 | 3.1 Terms..... | 7 | -| 12 | 3.2 Symbols..... | 8 | -| 13 | 3.3 Abbreviations..... | 8 | -| 14 | 4 Overview..... | 10 | -| 15 | 4.1 Objective and structure..... | 10 | -| 16 | 4.2 Methodology..... | 11 | -| 17 | 4.3 Document Scope..... | 12 | -| 18 | 4.3.1 Scope regarding architecture..... | 12 | -| 19 | 4.3.2 Out of scope components..... | 13 | -| 20 | 5 Statement of compatibility with 3GPP..... | 13 | -| 21 | 5.1 Assets and Threats..... | 14 | -| 22 | 5.2 Security requirements..... | 14 | -| 23 | 6 Roles-Assumptions-Assets..... | 15 | -| 24 | 6.1 Stakeholders' roles and responsibilities..... | 15 | -| 25 | 6.2 Void..... | 18 | -| 26 | 6.3 Critical assets..... | 18 | -| 27 | 7 Threat model..... | 31 | -| 28 | 7.1 Threat surface..... | 31 | -| 29 | 7.2 Threat agent..... | 31 | -| 30 | 7.3 Potential vulnerabilities..... | 31 | -| 31 | 7.4 Threats..... | 32 | -| 32 | 7.4.0 Threat Structure..... | 32 | -| 33 | 7.4.1 Threats against O-RAN system..... | 33 | -| 34 | 7.4.2 Threats against O-CLOUD..... | 67 | -| 35 | 7.4.3 Threats to open source code..... | 86 | -| 36 | 7.4.4 Physical Threats..... | 87 | -| 37 | 7.4.5 Threats against 5G radio networks..... | 89 | -| 38 | 7.4.6 Threats against AI/ML system..... | 90 | -| 39 | 7.4.7 Protocol Stack Threats..... | 101 | -| 40 | 7.4.8 SMO Threats..... | 102 | -| 41 | 7.4.9 Threats against Shared O-RU..... | 111 | -| 42 | 7.4.10 OAuth2.0 Threats..... | 124 | -| 43 | 7.5 Coverage matrix of threats..... | 131 | -| 44 | 8 Security principles..... | 157 | -| 45 | 8.1 Principles (SP)..... | 157 | -| 46 | 8.1.1 SP-AUTH Mutual Authentication..... | 157 | -| 47 | 8.1.2 SP-ACC Access Control..... | 157 | -| 48 | 8.1.3 SP-CRYPTO Secure cryptographic, key management and PKI..... | 157 | -| 49 | 8.1.4 SP-TCOMM Trusted Communication..... | 157 | -| 50 | 8.1.5 SP-SS Secure storage..... | 158 | -| 51 | 8.1.6 SP-SB Secure boot and self-configuration..... | 158 | - -| | | | | -|----|--------|------------------------------------------------------------------------------------------------------|-----| -| 1 | 8.1.7 | SP-UPDT Secure Update..... | 158 | -| 2 | 8.1.8 | SP-RECO Recoverability & Backup..... | 158 | -| 3 | 8.1.9 | SP-OPNS Security management of risks in open-source components..... | 158 | -| 4 | 8.1.10 | SP-ASSU Security Assurance..... | 159 | -| 5 | 8.1.11 | SP-PRV Privacy..... | 159 | -| 6 | 8.1.12 | SP-SLC Continuous security development, testing, logging, monitoring and vulnerability handling..... | 159 | -| 7 | 8.1.13 | SP-ISO Robust Isolation..... | 159 | -| 8 | 8.1.14 | SP-PHY Physical security..... | 160 | -| 9 | 8.1.15 | SP-CLD Secure cloud computing and virtualization..... | 160 | -| 10 | 8.1.16 | SP-ROB Robustness..... | 160 | -| 11 | 8.1.17 | SP-IDM O-Cloud ID secure management..... | 160 | -| 12 | 8.2 | Coverage Threats - Security principles..... | 160 | -| 13 | 9 | Risk assessment..... | 166 | -| 14 | 9.1 | Determination of severity level process..... | 166 | -| 15 | 9.2 | Determination of likelihood level process..... | 169 | -| 16 | 9.3 | Evaluation of the risks process..... | 170 | -| 17 | 9.4 | Risk assessment output..... | 170 | -| 18 | | Annex: Change history/Change request (history)..... | 208 | -| 19 | | | | -| 20 | | | | -| 21 | | | | -| 22 | | | | -| 23 | | | | -| 24 | | | | -| 25 | | | | -| 26 | | | | -| 27 | | | | -| 28 | | | | -| 29 | | | | -| 30 | | | | -| 31 | | | | -| 32 | | | | -| 33 | | | | -| 34 | | | | -| 35 | | | | -| 36 | | | | -| 37 | | | | -| 38 | | | | -| 39 | | | | -| 40 | | | | -| 41 | | | | -| 42 | | | | - -1 -2 - -# --- List of figures - -| | | | -|----|--------------------------------------------------------------------------------|-----| -| 3 | Figure 4-1 : Logical Architecture of O-RAN system [i.6] | 13 | -| 4 | Figure 7-1 : Threats and Vulnerabilities for O-RAN LLS 7-2x | 36 | -| 5 | Figure 7-2 : UE Identification in Near-RT-RIC | 47 | -| 6 | Figure 7-3 : Near-RT-RIC and xApps conflict with E2 node | 53 | -| 7 | Figure 7-4 : A1 interface between the Non-RT RIC and the Near-RT RIC | 61 | -| 8 | Figure 7-5 : RAN analytics information (RAI) services via Y1 service interface | 66 | -| 9 | Figure 7-6 : Illustration of the VM/Container escape attack | 72 | -| 10 | Figure 7-7 : Illustration of the migration flooding attack | 73 | -| 11 | Figure 7-8 : Illustration of the false resource advertising attack | 74 | -| 12 | Figure 7-9 : Illustration of the migration MITM attack | 74 | -| 13 | Figure 7-10 : Illustration of the Theft-of-Service/DoS Attack | 75 | -| 14 | Figure 7-11 : Illustration of the VM/Container hyperjacking attack | 78 | -| 15 | Figure 7-12 : Illustration of a cross VM/Container side channel attack | 80 | -| 16 | Figure 7-13 : REST Protocol Stack for the A1 and R1 Interfaces | 102 | -| 17 | Figure 9-1 : Main concepts of risk assessment | 166 | -| 18 | | | -| 19 | | | - -# --- List of tables - -| | | | -|----|--------------------------------------------------------------------------|-----| -| 20 | Table 5-1 : Statement of compatibility with 3GPP – Assets and Threats | 14 | -| 21 | Table 5-2 : Statement of compatibility with 3GPP – Security requirements | 14 | -| 22 | Table 6-1 : Roles and responsibilities | 15 | -| 23 | Table 6-2 : Critical assets | 20 | -| 24 | Table 7-1 : O-RAN Threat Inventory | 132 | -| 25 | Table 8-1 : Coverage Security principles-Threats (1/4) | 161 | -| 26 | Table 8-2 : Coverage Security principles-Threats (2/4) | 162 | -| 27 | Table 8-3 : Coverage Security principles-Threats (3/4) | 163 | -| 28 | Table 8-4 : Coverage Security principles-Threats (4/4) | 164 | -| 29 | Table 9-1 : Severity rating | 166 | -| 30 | Table 9-2 : Likelihood rating | 169 | -| 31 | Table 9-3 : Risk assessment matrix | 170 | -| 32 | Table 9-4 : Risk Assessment | 171 | -| 33 | | | -| 34 | | | - -35 -36 -37 -38 -39 -40 -41 -42 -43 -44 - -# Foreword - -This Technical Report (TR) has been produced by 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 - -This technical report describes the O-RAN Security Threat Modeling and Risk Assessment. It identifies assets to be protected, analyzes the O-RAN components for vulnerabilities, examines potential threats associated with those vulnerabilities, provides security principles which stakeholders should address when building a secure end-to-end O-RAN system and assesses the risks of the identified threats based on impact and likelihood factors. - -NOTE: The present document is transformed from a Technical Specification (TS) to a Technical Report (TR) as it doesn't contain normative requirements. Instead, it is an informative document that serves as a vital resource for understanding the potential risks within O-RAN and defining appropriate requirement/controls to mitigate them effectively. - -# 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 TS 33.511: Security Assurance Specification (SCAS) for the next generation Node B (gNodeB) network product class -- [i.3] 3GPP TS 33.501: Security architecture and procedures for 5G system -- [i.4] 3GPP TR 33.926: Security Assurance Specification (SCAS) threats and critical assets in 3GPP network product classes -- [i.5] 3GPP TS 33.117: Catalogue of general security assurance requirements -- [i.6] O-RAN.WG1.TS.OAD: "O-RAN Architecture Description" -- [i.7] ISO 27005: Information security, cybersecurity and privacy protection — Guidance on managing information security risks -- [i.8] O-RAN.WG3.TS.RICARCH: "Near-RT RIC Architecture" -- [i.9] O-RAN.WG6.AAL-GAnP: "O-RAN Acceleration Abstraction Layer General Aspects and Principles" -- [i.10] O-RAN.WG4.TS.CUS: "Control, User and Synchronization Plane Specification" -- [i.11] O-RAN.WG6.CADS: "Cloud Architecture and Deployment Scenarios for O-RAN Virtualized RAN" -- [i.12] ERICSSON "Security Considerations of Open RAN" whitepaper and slides. -- [i.13] NIST Special Publication 800-154 "Guide to Data-Centric System Threat Modeling" -- [i.14] Resource Allocation Scheme in 5G Network Slices - -- [i.15] 3GPP TR 33.818: “Security Assurance Methodology (SECAM) and Security Assurance Specification (SCAS) for 3GPP virtualized network products”. -- [i.16] Fraunhofer AISEC - threat analysis of container-as-a-service for network function virtualization -- [i.17] Ecology-Based DoS Attack in Cognitive Radio Networks -- [i.18] AN ARCHITECTURAL RISK ANALYSIS OF MACHINE LEARNING SYSTEMS: Toward More Secure Machine Learning -- [i.19] 5G Americas Whitepaper October 2018 “The Evolution of Security in 5G” -- [i.20] 3GPP TR 33.845: Study on security aspects of the 5G Service Based Architecture (SBA) -- [i.21] OWASP API Security Top 10 -- [i.22] MITRE ATT&CK containers matrix -- [i.23] 3GPP TR 33.848: Study on security impacts of virtualisation -- [i.24] Graz University of Technology (2018), Meltdown and Specter -- [i.25] O-RAN.WG3.TS.E2GAP: " E2 General Aspects and Principles (E2GAP)" -- [i.26] NIST Special Publication 800-207, “Zero Trust Architecture,” - -- [i.27] O-RAN.WG4.TS.MP: "Management Plane Specification". -- [i.28] CWE-524, "Use of Cache Containing Sensitive Information", -- [i.29] CAPEC-204, “Lifting Sensitive Data Embedded in Cache”, -- [i.30] Infiltrating Corporate Intranet Like NSA, -- [i.31] Output Integrity Attack, [https://owasp.org/www-project-machine-learning-security-top-10/docs/ML09\\_2023-Output\\_Integrity\\_Attack](https://owasp.org/www-project-machine-learning-security-top-10/docs/ML09_2023-Output_Integrity_Attack) -- [i.32] ENISA: “Securing Machine Learning Algorithms”, -- [i.33] OWASP Top 10 Machine Learning Security risks, 2023 -- [i.34] O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE: “O2dms Interface Specification: Kubernetes Native API Profile for Containerized NFs” -- [i.35] NIST Glossary, NIST Computer Resource Center, [Glossary | CSRC \(nist.gov\)](https://csrc.nist.gov/glossary) -- [i.36] 3GPP TS 33.527: Security Assurance Specification (SCAS) for 3GPP virtualized network products -- [i.37] 3GPP TS 33.523: Security Assurance Specification (SCAS); Split gNB product classes -- [i.38] O-RAN.WG2.TS.Non-RT-RIC-ARCH: "Non-RT RIC: Architecture" - -# 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [i.1], O-RAN [i.6], [i.9], [i.11] and the following apply: - -**Attack:** The realization of some specific threat that impacts the confidentiality, integrity, accountability, or availability of a resource. [adapted from i.35] - -**Attack surface:** The set of points on the boundary of a system, a system component, or an environment where an attacker can try to enter, cause an effect on, or extract data from, that system, component, or environment. [i.35] - -**O-Cloud instance ID:** The O-Cloud instance ID is a unique identifier assigned to components within the O-Cloud platform, including VMs, pods, containers, nodes, and compute pools (i.e., a cluster in Kubernetes). This ensures uniqueness across the entire O-Cloud environment, irrespective of the component type. For instance, a VM, a pod, a container, a node, and a cluster will each have a distinct O-Cloud instance ID within the platform, ensuring that there is no ambiguity in identification. - -**Radio jamming** is the deliberate jamming, blocking or creating interference with authorized wireless network. A radio jammer is a transmitter that tunes to the same frequency as the opponents' receiving equipment and with the same type of modulation, with enough power to override any signal at the receiver. - -**Radio Sniffing** technique helps to decode all sorts of essential network configuration details easily with low-cost software radios. Sniffing information can aid attackers in optimizing and crafting attacks. - -**Risk:** A measure of the extent to which an entity is threatened by a potential circumstance or event, and typically a function of: (i) the adverse impacts that would arise if the circumstance or event occurs; and (ii) the likelihood of occurrence. Information system-related security risks arise from the loss of confidentiality, integrity, or availability of information or information systems and reflect the potential adverse impacts to organizational operations (including mission, functions, image, or reputation), organizational assets, individuals, and other organizations. [i.35] - -**Risk mitigation:** Prioritizing, evaluating, and implementing the appropriate risk-reducing controls/countermeasures recommended from the risk management process. [i.35] - -**RF spoofing** refers to transmitting a fake signal meant to pretend as an actual signal. - -**Security controls:** Actions, devices, procedures, techniques, or other measures that reduce the vulnerability of an information system. [i.35] - -**Technical controls:** The security controls for an information system that are primarily implemented and executed by the information system through mechanisms contained in the hardware, software, or firmware components of the system. [i.35]. Also referred to as 'Security Controls' and 'Controls' in O-RAN. - -**Threat:** Any circumstance or event with the potential to adversely impact organizational operations (including mission, functions, image, or reputation), organizational assets, or individuals through an information system via unauthorized access, destruction, disclosure, modification of information, and/or denial of service. Also, the potential for a threat-source to successfully exploit a particular information system vulnerability. [i.35] - -**Vulnerability:** Weakness in a system, system security procedures, internal controls, or implementation that could be exploited or triggered by a threat. [i.35] - -**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: - -| | | -|-------------|-------------------------------------------------------------| -| AAL | Acceleration Abstraction Layer | -| AALI | Acceleration Abstraction Layer Interface | -| AALI-C | Acceleration Abstraction Layer Interface-Common | -| AALI-C-App | Acceleration Abstraction Layer Interface-Common-Application | -| AALI-C-Mgmt | Acceleration Abstraction Layer Interface-Common-Management | -| AALI-P | Acceleration Abstraction Layer Interface-Profile | -| AI/ML | Artificial Intelligence/Machine Learning | -| DL | Down Link | -| DoS | Denial of Service | -| eNB | eNodeB (applies to LTE) | -| FH | Front haul | -| FTP | File Transfer Protocol | -| FTPS | Explicit SSL File Transfer Protocol | - -| | | -|---------|-----------------------------------------| -| FTPS | File Transfer Protocol Secure | -| GM | Grand Master | -| gNB | gNodeB (applies to NR) | -| IPSEC | Internet Protocol Security | -| KPI | Key Performance Indicator | -| KQI | Key Quality Indicator | -| L1 | Layer 1 | -| LAA | Licensed-Assisted Access | -| LBT | Listen Before Talk | -| LLS | Lower Layer Split | -| MIMO | Multiple Input, Multiple Output | -| MITM | Man In The Middle | -| MNO | Mobile Network Operator | -| NETCONF | Network Configuration Protocol | -| NF | Network Function | -| NFV | Network Function Virtualisation | -| NR-U | New Radio Unlicensed | -| O-DU | O-RAN Distributed Unit | -| O-RU | O-RAN Radio Unit | -| PDCP | Packet Data Convergence Protocol | -| PDSCH | Physical Downlink Shared Channel | -| PUSCH | Physical Uplink Shared Channel | -| PRACH | Physical Random Access Channel | -| PRB | Physical Resource Block | -| PTP | Precision Timing Protocol | -| QoE | Quality of Experience | -| RBAC | Role-based Access Control | -| RIC | O-RAN RAN Intelligent Controller | -| RU | Radio Unit | -| SDN | Software Defined Network | -| SFTP | SSH File Transfer Protocol | -| SINR | Signal-to-Interference-plus-Noise Ratio | -| SMO | Service Management and Orchestration | -| SSH | Secure Shell | -| T-TC | Telecom Transparent Clock | -| TC | Transparent Clock | -| TLS | Transport Layer Security | -| UAV | Unmanned Aerial Vehicle | -| UL | Up Link | -| V2X | Vehicle to Everything | -| VM | Virtual machine | -| VNF | Virtualised Network Function | -| ZT | Zero Trust | -| ZTA | Zero Trust Architecture | - -1 - -# --- 4 Overview - -2 - -## 4.1 Objective and structure - -3 - -4 O-RAN architecture [i.6] differs significantly from the architecture of 3GPP RAN. It involves introducing new -5 components, interfaces, and technologies, which give rise to new actors (stakeholders) and enable novel business -6 models. Consequently, the attack surface expands considerably, and we anticipate that O-RAN design and deployment -7 will present numerous security challenges and associated risks. These challenges primarily stem from various factors, -8 such as the inclusion of O-RAN specific interfaces and components, the utilization of virtualization/containerization -9 techniques, the incorporation of open-source code, and the capability to support AI/ML models, among other -10 considerations. - -11 Additionally, the O-RAN architecture is being developed using zero trust (ZT) and zero trust architecture (ZTA) -12 principles as described in the NIST Zero Trust Architecture Special Publication [i.26]. Zero trust is an evolving set of -13 cybersecurity paradigms that move defenses from static, network-based perimeters to focus on users, assets, and -14 resources. Zero trust assumes there is no implicit trust granted to assets or user accounts based solely on their physical -15 or network location (i.e., local area networks versus the internet) or based on asset ownership (enterprise or personally -16 owned). Zero trust also assumes that an adversary can always be in the network. According to the publication [i.26], -17 zero trust is based on the following tenets that can be adapted to the O-RAN architecture. Full descriptions of each tenet -18 can be found in [i.26]. - -- 19 • [ZT-1] All data sources and computing services are considered resources. -20 • [ZT-2] All communication is secured regardless of network location. -21 • [ZT-3] Access to individual enterprise resources is granted on a per-session basis. -22 • [ZT-4] Access to resources is determined by dynamic policy—including the observable state of client identity, -23 application/service, and the requesting asset—and may include other behavioral and environmental attributes. -24 • [ZT-5] The enterprise monitors and measures the integrity and security posture of all owned and associated assets. -25 No asset is inherently trusted. -26 • [ZT-6] All resource authentication and authorization are dynamic and strictly enforced before access is allowed. -27 • [ZT-7] The enterprise collects as much information as possible about the current state of assets, network -28 infrastructure and communications and uses it to improve its security posture. - -29 Therefore, the security analysis and the threat model for O-RAN must be carefully studied and relevant -30 assets/stakeholders/vulnerabilities/threats/requirements/countermeasures/recommendations must be identified to reduce -31 risk exposure, mitigate any harmful effects, and drive to a ZTA. - -32 The material presented in this analysis aims at supporting various O-RAN stakeholders understanding the relevant -33 threats resulting to an exposure of O-RAN assets by exploiting the vulnerabilities. - -34 The objective is to give a comprehensive and high-level view on how security is organized in O-RAN system. In this -35 document, we assume that 3GPP security requirements are met. Unless explicitly stated, features relate to O-RAN -36 specifications. - -37 This analysis is consolidated from various relevant sources, including main 5G standardization documents and -38 telecommunication best practices (e.g., 3GPP, ETSI, NIST, ENISA). - -39 The first main part outlines the main stockholder roles involved in managing and using O-RAN system. Further, it -40 addresses the prerequisites and assumptions needed to securely implement and run O-RAN systems. It also identifies -41 the list of critical assets to be protected in integrity, availability, confidentiality, replay and authenticity. - -42 The second main part addresses the threat model. It identifies the threat agents, determines the threat surface, identifies -43 vulnerabilities, and lists the threats for each O-RAN component or interface. For each threat, the description, threatened -44 asset(s), vulnerabilities, threat agents and affected components are given. - -1 The third main part describes the security principles to be achieved to counter the identified threats. In addition, it -2 illustrates the coverage between threats and security principles. - -3 The fourth main part is the risk assessment of the identified threats in terms of severity and likelihood. - -4 **NOTE 1:** The present document focuses only on the components, interfaces and protocols specified by O-RAN -5 ALLIANCE. Components, interfaces and protocols specified by 3GPP are only referenced where needed but are not -6 within the scope of this specific O-RAN security analysis. - -7 **NOTE 2:** The present document is a working document with the need to update the content on a regular basis following -8 the risk evaluation. - -9 **NOTE 3:** In this document, the term NF (Network Function) is used to designate either VNF (Virtual Network -10 Function), CNF (Cloud-native Network Function) or PNF (Physical Network Function). - -11 **NOTE 4:** Terms “Containers” and “Virtual Machines” are used interchangeably in this document as the implementation -12 of O-RAN SW components could either be container-based, VM-based or hybrid (Containers and VMs together). - -###### 13 4.2 Methodology - -14 The methodology adopted in this document is based on the standard ISO 27005 [i.7] which provide a detailed and -15 flexible structure to release a risk assessment. - -16 The methodology followed in this document comprises three stages: - -###### 17 1) Identification - -- 18 a. **Identify stakeholders:** First, we need to identify the stakeholders involved in the implementation, -19 management, operation and maintenance of the O-RAN system. Roles and responsibilities of each -20 stakeholder are given. -- 21 b. **Define assumptions:** The list of minimum prerequisites and assumptions need to be defined for the -22 operational environment (not under the control of the O-RAN system) required to successfully -23 operate the O-RAN system. -- 24 c. **Identify assets:** First, we need to locate relevant assets the O-RAN system hold and give details about -25 the type (Data, component, etc.), the security properties (CIA) at rest and in transit and location. -- 26 d. **Identify threats:** We need to identify the relevant threats associated with the new O-RAN -27 components, interfaces and technologies. In addition, the threat surface and agents are given. -- 28 e. **Identify vulnerabilities:** O-RAN system may have weaknesses in its new O-RAN components, -29 interfaces and technologies which need to be identified. -- 30 f. **Define security principles:** We need to define security principles to be achieved in order to reduce -31 risk exposure. -- 32 g. **Elaborate and refine security principles:** Each security principle needs to be detailed and refined -33 into requirements, recommendations and countermeasures. -- 34 h. **Identify existing/ongoing countermeasures:** We need to identify all of O-RAN existing/ongoing -35 controls and to take into account the protection provided by these controls before applying any new -36 ones. - -###### 37 2) Risk assessment - -38 The value for *Risk* is defined by the following equation: - -$$39 \text{Risk} = (\text{the probability of a threat exploiting a vulnerability}) \times (\text{total impact of the vulnerability being exploited})$$ - -###### 40 3) Risk treatment - -- 41 a. Now that we know the level of risk that each threat poses, we need to decide how we'll treat them. -42 There are four options: - -- i. **Modify the risk** by implementing a control to reduce the likelihood of it occurring. -- ii. **Avoid the risk** by ceasing any activity that creates it. This response is appropriate if the risk is too big to manage with a security control. -- iii. **Share the risk** with a third party. There are two ways: by outsourcing the security efforts to another organization or by purchasing cyber insurance to ensure the funds to respond appropriately in the event of a disaster. -- iv. **Retain the risk**. This means that the organization accepts the risk and believes that the cost of treating it is greater than the damage that it would cause. - -## 4.3 Document Scope - -This clause comprises the architecture in the scope of the security analysis. The architecture includes the list of O-RAN components, interfaces and protocols manipulating critical assets and implementing security functions. - -### 4.3.1 Scope regarding architecture - -As specified in [i.6], the logical architecture of O-RAN includes the following components, interfaces and protocols: - -#### O-RAN components: - -- Network functions and applications - - Service Management and Orchestration (SMO) - - Non-RT RIC and rApps - - Near-RT RIC and xApps - - O-CU-CP/UP - - O-DU - - O-RU - - O-eNB -- Cloud computing platform - - O-Cloud comprising a collection of physical infrastructure nodes that meet O-RAN requirements to host the relevant O-RAN functions (such as 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. - -#### O-RAN specific interfaces: - -- 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. -- O1 Interface connecting the SMO to the Near-RT RIC, one or more O-CU-CPs, one or more O-CU-UPs, and one or more O-DUs. -- O2 Interface between the SMO and the O-Cloud. -- E2 Interface connecting the Near-RT RIC and one or more O-CU-CPs, one or more O-CU-UPs, one or more O-DUs, and one or more O-eNBs. -- Open Fronthaul CUS-Plane Interface between O-RU and O-DU. -- Open Fronthaul M-Plane Interface between O-RU and O-DU as well as between O-RU and SMO. -- Y1 Interface over which RAN analytics services exposed by the Near-RT RIC to be consumed by Y1 consumers. - -#### Relevant Protocols used by O-RAN system for enforcing security: - -- TLS - -- Should be used to protect the traffic between the O-RAN system and other network elements. It establishes a secure channel and provides CIA (Confidentiality, Integrity, Authenticity) features. -- Should be used in O1 interface for NETCONF over TLS and JSON/REST over TLS -- Should be used in A1 interface -- SSH - - Should be used in O1 interface and Fronthaul M-Plane for NETCONF over SSH -- IPSEC - - Should be used to protect E2 traffic -- SFTP and FTPES - - Should be used to protect file transfers over O1 and Fronthaul M-Plane interfaces -- PTP (Precision Timing Protocol, IEEE 1588-2019) - -![Figure Overview-1 : Logical Architecture of O-RAN system. The diagram shows the hierarchy of O-RAN components: Service Management and Orchestration Framework (top) containing Non-Real Time RIC; Near-Real Time RIC; O-eNB; O-CU-CP; O-CU-UP; O-DU; O-RU; and O-Cloud (bottom). Interfaces are labeled: O1, O2, A1, Y1, E2, X2-c, X2-u, NG-u, Xn-c, Xn-u, NG-c, F1-c, F1-u. A legend indicates 3GPP interfaces (grey) and O-RAN interfaces (green).](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) - -Figure Overview-1 : Logical Architecture of O-RAN system. The diagram shows the hierarchy of O-RAN components: Service Management and Orchestration Framework (top) containing Non-Real Time RIC; Near-Real Time RIC; O-eNB; O-CU-CP; O-CU-UP; O-DU; O-RU; and O-Cloud (bottom). Interfaces are labeled: O1, O2, A1, Y1, E2, X2-c, X2-u, NG-u, Xn-c, Xn-u, NG-c, F1-c, F1-u. A legend indicates 3GPP interfaces (grey) and O-RAN interfaces (green). - -Figure Overview-1 : Logical Architecture of O-RAN system [i.6] - -### 4.3.2 Out of scope components - -The following components are not in the perimeter of the O-RAN system defined by the O-RAN ALLIANCE; therefore, they are considered out of scope of this study: - -- 3GPP interfaces are already studied and maintained by 3GPP, -- UE, -- MEC, -- Core, -- Antennas. - -# 5 Statement of compatibility with 3GPP - -This chapter gives the statement of compatibility with 3GPP/SCAS security Assets, Threats and Requirements. The statement of compatibility shows that 3GPP Assets/Threats/Requirements are applicable and that there is no conflict affecting the security of O-RAN components. - -## 5.1 Assets and Threats - -**Table Statement of compatibility with 3GPP-1 : Statement of compatibility with 3GPP – Assets and Threats** - -| 3GPP/SCAS document reference/clause | Description | Applicable to O-RAN | Rationale | -|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| TR 33.926 [i.4], clauses 5 and 6 | It describes the generic assets and threats of 3GPP network products | Yes | Since these assets/threats are for generic 3GPP (virtualized) network products, they are also applicable to O-RAN. It means that there is no need to repeat those assets/threats in this document. | -| TR 33.818 [i.15], clause 5.2.4 | It describes the generic assets, threats and requirements of 3GPP/ETSI NFV virtualized network products. | Yes | | -| TR 33.848 [i.23], clause 5 | It considers the consequences of virtualization on 3GPP architectures, in order to identify threats and subsequent security requirements relating to ETSI-defined interfaces and Security functional requirements related to Virtualization layer, hardware and resource isolation. | Yes | | - -In addition, the assets/threats related to the additional specific O-RAN interfaces and components are considered. As a result, clauses 6.3 and 7.4 elaborates the O-RAN specific assets and threats respectively. - -## 5.2 Security requirements - -**Table Statement of compatibility with 3GPP-2 : Statement of compatibility with 3GPP – Security requirements** - -| 3GPP/SCAS document reference/clause | Description | Applicable to O-RAN | Rationale | -|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| TS 33.117 [i.5], clauses 4.3 and, 4.42 | It describes the general approach taken towards security functional requirements deriving from 3GPP specifications and the corresponding test cases, independent of a specific network product class. | Yes | Since these requirements are for generic 3GPP (virtualized) network products, they are to be fulfilled by O-RAN. It means that there is no need to repeat those requirements in this document. | -| TS 33.501 [i.3] | It describes the security architecture and procedures for 5G system including gNodeB | Yes | | -| TS 33.511 [i.2] | It describes the security requirements for the next generation Node B (gNodeB) network product class | Yes | | -| TS 33.527 [i.36] | It describes the security requirements for 3GPP virtualized network products | Yes | | -| TS 33.523 [i.37] | It describes the security requirements for Split gNB product classes | Yes | | - -In addition, O-RAN also needs to consider the security requirements related to the additional specific O-RAN interfaces and components. As a result, clause 8 focus on the O-RAN security principles. - -# 6 Roles-Assumptions-Assets - -## 6.1 Stakeholders' roles and responsibilities - -The main stakeholders managing and using the O-RAN system are the following: - -**Table Roles-Assumptions-Assets-3 : Roles and responsibilities** - -| Role | Description | -|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Mobile Network Operator (MNO) | Who offers network services and has a license to operate in allocated spectrum. | -| Orchestrator | Who is in charge of operating and orchestrating the O-RAN services.
The MNO could be the orchestrator. | -| HW/ Network vendor | Who is in charge of:
  • • Providing the network infrastructure including servers to run SDN controller, switches, routers, gateways, radio hardware, etc.
  • • Installation, maintenance or replacement of the hardware/network device
  • • Providing capability and procedures to securely configure the hardware/network device
  • • Providing capability for the hardware/network device to generate log events
  • • Providing capability for log files to be sent to an externalized log analysis system provided by the MNO
  • • Providing a process for users, including security researchers, to submit bug reports (e.g., using an issue tracker or a mailing list)
  • • Testing according to 3GPP and O-RAN test plans. Testing should include security tests of the device and its interfaces
  • • Setting up a vulnerability management process of monitoring, identifying, evaluating, treating and reporting on security vulnerabilities in the hardware/network device including firmware
  • • Maintenance of the firmware that includes providing patches for bugs and vulnerabilities
| -| HW/ Network administrator | Who is in charge of:
  • • Configuration of the hardware/network device
  • • Enabling collection of log events
  • • Collection and analysis of log events generated by the hardware/network device
  • • Deploying firmware patches in compliance with HW/ Network vendors deployment guidance
  • • Monitoring, identifying and notifying HW/ Network vendors on discovered vulnerabilities
  • • Regular testing of hardware/network configuration
The MNO could be the HW/ Network administrator. | -| NF vendor | Who is in charge of:
  • • Developing and providing NFs (e.g. VNF, CNF, PNF) for Near-RT RIC, O-CU-CP, O-CU-UP, O-DU, etc.
| - -| | | -|------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |
  • • Providing capability and procedures to securely configure the NF
  • • Setting up a vulnerability management process of monitoring, identifying, evaluating, treating and reporting on security vulnerabilities in the NF
  • • Setting up a patch development, testing and delivery processes
  • • Maintenance of the NF that includes providing patches for bugs and vulnerabilities
  • • Providing capability for NF to generate log events
  • • Providing capability for log files to be sent to an externalized log analysis system provided by the MNO
  • • Testing according to 3GPP and O-RAN test plans. Testing should include security tests of the NF and its interface
  • • Providing a process for users, including security researchers, to submit bug reports (e.g., using an issue tracker or a mailing list)
| -| NF administrator | Who is in charge of:
  • • Deploying patches in compliance with NF vendors deployment guidance
  • • Monitoring, identifying and notifying NF vendors on discovered vulnerabilities
  • • Securely configuring the NF
  • • Regular testing of the NF configuration
  • • Enabling collection of log events
  • • Analyzing log events generated by the software
The MNO could be the NF administrator. | -| Virtualization/Containerization hardware infrastructure provider | Who is in charge of:
  • • Provides virtualized/containerized infrastructure comprising computing resources (e.g., from computing platforms), storage and network.
  • • Providing capability to securely configure the virtualization/containerization hardware infrastructure
  • • Setting up a vulnerability management process of monitoring, identifying, evaluating, treating and reporting on security vulnerabilities in the virtualization/containerization hardware infrastructure
  • • Maintenance of the security of hardware infrastructure
  • • Providing capability for the hardware infrastructure to generate log events
  • • Providing capability for log files to be sent to an externalized log analysis system provided by the MNO
  • • Providing a process for users, including security researchers, to submit bug reports (e.g., using an issue tracker or a mailing list)
| -| Virtualization/Containerization hardware infrastructure administrator | Who is in charge of:
  • • Deploying the Virtualization/Containerization hardware infrastructure in compliance with providers deployment guidance
  • • Monitoring, identifying and notifying Virtualization/Containerization hardware infrastructure providers on discovered vulnerabilities
  • • Securely configuring the Virtualization/Containerization hardware infrastructure
  • • Regular testing of the Virtualization/Containerization hardware infrastructure configuration
| - -| | | -|------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |
  • Enabling collection of log events
  • Analyzing log events generated by the Virtualization/Containerization hardware infrastructure

The MNO could be the Virtualization/Containerization hardware infrastructure administrator.

| -| Virtualization/Containerization software infrastructure provider |

Who is in charge of:

  • Provides virtualized/containerized infrastructure services and designs, builds, and operates virtualization/containerization infrastructure(s). The infrastructure comprises software of compute nodes such as hypervisors, host operating systems, and container run-time systems.
  • Providing capability to securely configure the virtualization/containerization software infrastructure
  • Setting up a vulnerability management process of monitoring, identifying, evaluating, treating and reporting on security vulnerabilities in the virtualization/containerization software infrastructure
  • Setting up a patch development, testing and delivery processes
  • Maintenance of the software infrastructure that includes providing patches for bugs and vulnerabilities
  • Providing capability for the software infrastructure to generate log events
  • Providing capability for log files to be sent to an externalized log analysis system provided by the MNO
  • Providing a process for users, including security researchers, to submit bug reports (e.g., using an issue tracker or a mailing list)
| -| Virtualization/Containerization software infrastructure administrator |

Who is in charge of:

  • Deploying patches in compliance with Virtualization/Containerization software infrastructure providers deployment guidance
  • Monitoring, identifying and notifying Virtualization/Containerization software infrastructure providers of discovered vulnerabilities
  • Securely configuring the Virtualization/Containerization software infrastructure
  • Regular testing of the Virtualization/Containerization software infrastructure configuration
  • Enabling collection of log events
  • Analyzing log events generated by the Virtualization/Containerization software infrastructure

The MNO could be the Virtualization/Containerization software infrastructure administrator.

| -| System integrator |

Who is in charge of:

  • Appropriately integrating O-RAN HW and SW components. SW components are integrated, in most cases remotely.
  • Ensuring that those components function together as expected
  • Securely configuring (system level) the O-RAN system
  • Testing patches after deployment to ensure that they don't break other parts of O-RAN system or even expose new vulnerabilities

The MNO could be the integrator.

| -| System tester |

Tester of the O-RAN system to ensure quality, security, functionality and performance.

| - -| | | -|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | The MNO could be the system tester. | -| Other administrators |

Identity Admin:

  • Manages (Add, Modify, Delete) administrator accounts
  • Configures general settings for administrator accounts (password policy, etc.)

RBAC Admin

  • Generates RBAC policies and permissions on admin access

System Admin

  • Monitors network traffic for any suspicious activity
  • Performs risk assessment and defends against zero-day malware
  • Audits the O-RAN system
  • Triggers the update of O-RAN components on the latest security patches
  • Runs regular backups
  • Regularly performs analysis of log data

PKI Admin

  • Manage and secure private keys and certificates
| - -1 - -2 - -**NOTE 1:** The operation, administration and orchestration of the O-RAN system can be split across multiple companies or roles. - -3 - -4 - -**NOTE 2:** A trust management mechanism becomes crucially important to realize trustworthy collaboration among the O-RAN stakeholders. - -5 - -6 - -## 6.2 Void - -7 - -## 6.3 Critical assets - -8 - -The following table gives the list of critical assets to be protected within the O-RAN system. - -9 - -An asset in this context may encompass data, interface or component deemed valuable for the O-RAN system. A component is defined as an O-RAN network function or architectural element. - -10 - -11 - -Here's an explanation of each column, along with guidance on how to fill out the table: - -12 - -- Asset ID:** It identifies each asset uniquely. It helps in cataloging and referencing specific assets systematically. -- Asset Description:** A brief description of what the asset is, including its purpose, contents, and any relevant attributes. -- Component:** It specifies the O-RAN element(s) the asset is associated with, such as O-DU, O-RU, SMO, etc. This clarifies the asset's location within the O-RAN architecture. -- Interface:** It indicates the interface through which the asset communicates or interacts with other elements. This could be internal interfaces or external interfaces. - -13 - -14 - -15 - -16 - -17 - -18 - -19 - -20 - -**NOTE:** Assets can either be confined to a component (for those not shared with other O-RAN elements) or be present within a component and also transmitted to other O-RAN elements over interfaces. The way in which the 'Component' and 'Interface' columns are filled out will vary based on these situations. - -21 - -22 - -23 - -- When:** It is a categorization of the asset's state in terms of its lifecycle or operational phase, like "at rest" or "in transit". It is used to indicate when certain protection levels should be applied. - -24 - -- **When (At rest):** Marks with an 'x' if the asset needs protection while it is at rest (stored and not actively being used or transmitted). - - **When (In transit):** Marks with an 'x' if the asset needs protection during transit (being transmitted or moved). -- **Protection level (Confidentiality, Integrity, Availability, Replay, Authenticity):** These columns specify the type of protection or security measure required for the asset. An 'x' in any of these sub-columns indicates a need for measures to ensure: - - **Confidentiality:** The asset should be accessible only to authorized entities. - - **Integrity:** The asset should be protected from unauthorized changes. - - **Availability:** The asset should be accessible to authorized entities when needed. - - **Replay:** Protection against replay attacks, ensuring that repeated or delayed transmissions are identified and prevented. - - **Authenticity:** The asset should be verifiable as genuine. - -Instructions for completing the table: - -- **Asset ID:** Assign a unique identifier to each asset. -- **Asset Description:** Provide a detailed description of the asset, including its nature, purpose, and any other relevant details. -- **Component:** Specify the component associated with the asset, if applicable. -- **Interface:** Indicate the interface(s) related to the asset. -- **When (At rest/In transit):** Mark with an 'x' if the asset requires protection either at rest or in transit. -- **Protection level:** Mark with an 'x' in the appropriate sub-columns to indicate the types of protection required for the asset. - -The categories "Data" and "Components" are defined as follows: - -- **Data:** It refers to the information that is processed, stored, and transmitted through the O-RAN architecture. -- **Components:** It involves the physical (Hardware), logical and virtual (Software) parts of the O-RAN system. - -**Table Roles-Assumptions-Assets-4 : Critical assets** - -| Asset ID | Asset Description | Component | Interface | When | | Protection Level | | | | | -|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|---------------------|---------|------------|------------------|-----------|--------------|--------|--------------| -| | | | | At rest | In transit | Confidentiality | Integrity | Availability | Replay | Authenticity | -| Data & Interfaces | | | | | | | | | | | -| ASSET-D-01 | Critical S-Plane data such as:
- Data flow for synchronization and timing information between nodes
- PTP (e.g. ANNOUNCE message) transported over Fronthaul that interconnects multiple O-RUs and O-DUs.
- Timing configuration (LLS C1, C2, C3, C4) and topology | O-DU, O-RU | Fronthaul CUS-Plane | | x | | x | | x | x | -| | | | | x | | | x | x | | | -| ASSET-D-02 | Critical Management-Plane data transported over the Fronthaul interface such as: maintenance and monitoring signals, data collected related to O-RU operations, logs (troubleshooting, trace) | O-DU, O-RU, SMO | Fronthaul M-Plane | | x | x | x | | x | x | -| | | | | x | | x | x | x | | | -| ASSET-D-03 | Critical Management-Plane data transported over the O1 interface such as:
- Observables (events and counters) and network status provided over O1 to non-RT RIC from Near-RT RIC, O-CU and O-DU.
- The non-RT RIC uses the O1 observables (Feedback on the fulfilment of AI policies in the near-RT RIC) to continuously evaluate the impact of the AI policies towards fulfilment of the RAN Intent.
- Managed Element Telemetry to monitor the application behavior (from O-Cloud). | Near-RT RIC, Non-RT RIC, O-CU, O-DU, SMO | O1 | | x | x | x | | x | x | -| | | | | x | | x | x | x | | | -| ASSET-D-04 | Critical C-Plane data such as:
- Scheduling information, FFT size, CP length, Subcarrier spacing, UL PRACH scheduling
- DL and UL Beamforming commands (e.g., beam index) and scheduling
- LBT Configuration parameters such as lbtHandle, lbtDeferFactor, lbtBackoffCounter, lbtOffset, MCOT, lbtMode, sfnSf, lbtCWconfig_H, lbtCWconfig_T, lbtTrafficClass.
- LBT DL indication parameters such as lbtHandle, lbtResult, initialPartialSFs, bufferError, lbtCWR_Result | O-DU, O-RU | Fronthaul CUS-Plane | | x | x | x | | x | x | -| | | | | x | | | x | x | | | - -| Asset ID | Asset Description | Component | Interface | When | | Protection Level | | | | | -|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|---------------------|---------|------------|------------------|-----------|--------------|--------|--------------| -| | | | | At rest | In transit | Confidentiality | Integrity | Availability | Replay | Authenticity | -| ASSET-D-05 | Critical Fronthaul U-Plane data such as:
  • - User data (i.e. DNS, PUSCH, PDSCH, etc.),
  • - Control channel data (PDCCH, PUCCH, etc.),
  • - I/Q samples, PRACH-related information, eCPRI, and O-RAN headers
  • - MAC CEs (Control Elements)
| O-DU, O-RU | Fronthaul CUS-Plane | | x | | x | | x | x | -| | | | | x | | | x | x | | | -| ASSET-D-06 | Reference signals, synchronization signal and channels in downlink and uplink between O-RU and UE | O-RU | Radio | | x | x | x | | x | x | -| ASSET-D-07 | A1 policies that are provided to the near-RT RIC over the A1 interface to guide the RAN performance towards the overall goal expressed in RAN Intent. The A1 policies are declarative policies that contain statements on policy objectives and policy resources applicable to UEs and cells. A1 policies are created, modified and deleted by the non-RT RIC. | Near-RT RIC, Non-RT RIC | A1 | | x | x | x | | | x | -| ASSET-D-08 | A1 Enrichment Information that is collected or derived at SMO/non-RT RIC either from non-network data sources or from network functions themselves and provided over the A1 interface to be utilized by near-RT RIC, e.g. an ML model, to improve its performance.

Discovery and request of A1 Enrichment Information from near-RT RIC to non-RT RIC

External Enrichment Information that is provided by an O-RAN external information source to near-RT RIC over A1 | Near-RT RIC, Non-RT RIC | A1 | | x | x | x | | | x | -| ASSET-D-09 | Data transported over the E2 interface such as:
  • - Near real-time information (e.g. UE basis, 2Cell basis).
  • - The persistent configuration used by the near-RT RIC to control the RAN.
  • - Identifiers of E2 nodes.
  • - xApp-related messages.
  • - Control signaling information.
| O-DU, O-CU, Near-RT RIC | E2 | | x | x | x | | x | x | - -| Asset ID | Asset Description | Component | Interface | When | | Protection Level | | | | | -|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------|---------|------------|------------------|-----------|--------------|--------|--------------| -| | | | | At rest | In transit | Confidentiality | Integrity | Availability | Replay | Authenticity | -| |
  • - Policies used by the Near-RT RIC to monitor, suspend/stop, override or control the behavior of E2 node.
  • - NEAR-RT RIC services messages (REPORT, INSERT, CONTROL and POLICY).
  • - Interface Management messages (E2 Setup, E2 Reset, E2 Node Configuration Update, Reporting of General Error Situations).
  • - Near-RT RIC Service Update messages.
| | | | | | | | | | -| ASSET-D-10 | Database holding data from xApp applications and E2 Node | Near-RT RIC | - | x | | x | x | x | | x | -| ASSET-D-11 | E2 Node data (e.g. configuration information (cell configuration, supported slices, PLMNs, etc.), network measurements, context information, etc.) | E2 nodes | - | x | | | x | x | | | -| ASSET-D-12 | It consists of
  • • The Physical Infrastructure (O-Cloud Node Identifier, Pool Identifier, Pool Location Identifier, and Use Identifier) used to create the O-Cloud,
  • • The logical Clouds which it provides as interfaces for deployments, and the inventory of deployments (deployment ID and descriptor) on the cloud
  • • O-Cloud ID, IP address, IMS address, the IP address endpoint or url of the SMO and any necessary security keys or passwords for communication using O2
  • • DMS capabilities
  • • O-Cloud (IMS): List of All Resource Pools in the O-Cloud, Attributes of a specific O-Cloud, List of all resources of an O-Cloud Pool, Attributes of each O-Cloud Resource, List of all DMS
  • • O-Cloud (DMS): List of Locations Supported For a given location the Capabilities supported (e.g. Descriptor types, Technology types, Accelerator types), For a given location the Capacity of the location, For a given location the Availability of the location
| SMO, O-CLOUD | O2, O-CLOUD internal interfaces | x | x | x | x | x | x | x | - -| Asset ID | Asset Description | Component | Interface | When | | Protection Level | | | | | -|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------|---------|------------|------------------|-----------|--------------|--------|--------------| -| | | | | At rest | In transit | Confidentiality | Integrity | Availability | Replay | Authenticity | -| | | | | | | | | | | | -| ASSET-D-13 | It includes:
  • - Telemetry information of O-Cloud deployments in the network for analyzing the O-Cloud's state and health, and for delivering on service monitoring goals. It consists of fault, performance and configuration data:
  • - Deployment Telemetry to monitor the number of deployment instances an O-Cloud has at that moment and how many were expected, how the on-progress deployment is going, and health checks. Additional Deployment Telemetry metrics like CPU, network, and memory usage can also be collected.
  • - Infrastructure Telemetry to monitor the health of the O-Cloud Infrastructure components. Network Operations are interested in discovering if all the components in the O-Cloud Infrastructure are working properly and at what capacity, how many deployments are running on each node, and the resource utilization of the O-Cloud Infrastructure.
| SMO, O-CLOUD | O2, O-CLOUD internal interfaces | x | x | x | x | x | x | x | -| ASSET-D-14 | O-Cloud Provisioning information (Affinity, Anti-Affinity, Quorum Diversity Rules, capabilities, capacity and availability)

O-Cloud software management information: catalog of authorized software and its version, list of authorized VNF/CNF, VNF/CNF description files | SMO, O-CLOUD | O2, O-CLOUD internal interfaces | | x | x | x | | x | x | -| ASSET-D-15 | Package: O-RAN Cloudified Network Function Software Image including the underlying software executable image, image properties/metadata such as descriptors, image signature(s), LCM scripts, data files, SoftwareImageId, Vendor, and version, secrets, configuration files.

Application data: Subscriber data, Policy data, UE context, etc.

NF location, time clock

NF instance: Application software, guest OS, host OS, Libs, instance identity, crypto keys, namespaces, virtual resources instance states, physical hardware, etc. | O-CLOUD | - | x | | x | x | x | | | -| ASSET-D-16 | X.509 certificates in O-RAN network such as those used for SMO, O-CU-CP, O-CU-UP, O-DU, O-RU, Near-RT RIC, Non-RT RIC, O-CLOUD, NetCONF (O1, Fronthaul) | All | O1, Fronthaul, O2, E2, A1 | x | | | x | x | | x | - -| Asset ID | Asset Description | Component | Interface | When | | Protection Level | | | | | -|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|---------------------------|---------|------------|------------------|-----------|--------------|--------|--------------| -| | | | | At rest | In transit | Confidentiality | Integrity | Availability | Replay | Authenticity | -| ASSET-D-17 | Security private keys in O-RAN network such as those used for SMO, O-CU-CP, O-CU-UP, O-DU, O-RU, Near-RT RIC, Non-RT RIC, O-CLOUD, NetCONF (O1, Fronthaul) ), for authentication, encryption, signing (e.g. for TLS and similar protocols, image signing) | All | O1, Fronthaul, O2, E2, A1 | x | | x | x | x | | x | -| ASSET-D-18 | O-RAN components associated and configuration data, such as:
  • - Software version information, identifier, IP address, port number, network layer parameters, time of request, previous behavior, etc.
  • - The security related parameters (such audit records, lists of algorithms which are allowed for usage, file management, hash values, etc.).
| All | - | x | | x | x | x | | | -| ASSET-D-19 | Cryptographic keys: KgNB, KRRC-enc, KRRC-int, KUP-int, and KUP-enc (Hierarchy of cryptographic key derived from Anchor Key. (as defined in ETSI TS 133 501 clause 6.2.) | O-CU | - | x | | x | x | x | | | -| ASSET-D-20 | Credentials (Administrators): account information and passwords on SMO, O-CU-CP, O-CU-UP, O-DU, O-RU, Near-RT RIC, Non-RT RIC, O-Cloud used in O-RAN network | All | | x | | x | x | x | | | -| ASSET-D-21 | 3GPP application related data such as subscription data, session data, call control related information etc. | O-CU | | x | x | x | x | x | x | x | -| ASSET-D-22 | Inter- and intra-slice UE priority [i.14] | O-CU, O-DU | - | x | x | | x | x | | | -| ASSET-D-23 | Patches for vulnerable SW components | All | - | | x | | x | x | | x | -| ASSET-D-24 | NETCONF Configuration Access Control Model datastores | All | | x | | x | x | x | | x | -| ASSET-D-25 | Training or test data and associated labels: data sets collected externally or internally from the Near-RT RIC, O-CU and O-DU and passed to the ML training hosts in a ML system. | Near-RT RIC, Non-RT RIC, xAPPs, rAPPs | A1, O1, E2 | | x | x | x | | x | x | -| | | | | x | | x | x | x | | x | -| ASSET-D-26 | The trained ML model which includes the configured hyperparameters, inference algorithm, and learned parameters. | Near-RT RIC, Non-RT RIC, xAPPs, rAPPs | | x | | x | x | x | | | -| ASSET-D-27 | The ML prediction results built into the model (e.g. expected outcomes) | Near-RT RIC, Non-RT RIC, | | | | x | x | x | | | - -| Asset ID | Asset Description | Component | Interface | When | | Protection Level | | | | | -|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|------------------------------------------------------------|------------|------------|------------------|-----------|--------------|--------|--------------| -| | | | | At rest | In transit | Confidentiality | Integrity | Availability | Replay | Authenticity | -| | | xAPPs, rAPPs | | | | | | | | | -| ASSET-D-28 | The behavior of the ML system including tasks for data collection, data wrangling, pipeline management, model retraining, and model deployment. | Near-RT RIC, Non-RT RIC, xAPPs, rAPPs | | At runtime | | x | x | x | | | -| ASSET-D-29 | Security event log files generated by O-RAN components | All | | x | x | | x | x | | x | -| ASSET-D-30 | O-RAN specific several UE IDs | Near-RT RIC, Non-RT RIC, SMO | A1, E2, O1 | | x | x | x | | x | x | -| | | | | x | | x | x | x | | | -| ASSET-D-31 | Security telemetry from the O-Cloud for detecting threats and anomalies | All | O2, O-CLOUD internal interfaces | x | x | x | x | x | x | x | -| ASSET-D-32 | Cryptographic keys used during secure boot, for encryption/decryption, etc. | All | - | x | | x | x | x | | | -| ASSET-D-33 | Data transported over the AALI-C-Mgmt interface | | AALI-C-Mgmt | | x | x | x | | x | x | -| ASSET-D-34 | Data transported over the AALI-C-App & AALI-P interfaces | | AALI-C-App & AALI-P | | x | | x | | x | x | -| ASSET-D-35 | Data in transit between the HAM and the accelerator device | | Implementation-specific interface (not specified by O-RAN) | | x | | x | | | x | -| ASSET-D-36 | AAL profile data, including profile identifiers, version, supported accelerated functions, and any assignments to AAL-LPUs or AAL Applications. | AAL | | x | | | x | x | | | -| ASSET-D-37 | AAL-LPU data describing an AAL Logical Processing Unit's identifiers, mapping to hardware accelerators, supported profiles, capabilities, and configuration parameters. | AAL | | x | | | x | x | | | -| ASSET-D-38 | Stored AAL data: Persistent data stored by the AAL Implementation and HAM, such as logs, configuration data, manifests, and artifacts that describe the accelerator and its profile. | AAL | | x | | | x | x | | | - -| Asset ID | Asset Description | Component | Interface | When | | Protection Level | | | | | -|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|------------------------------|-----------|---------|------------|------------------|-----------|--------------|--------|--------------| -| | | | | At rest | In transit | Confidentiality | Integrity | Availability | Replay | Authenticity | -| ASSET-D-39 | xAppID | Near-RT RIC, xApps | | x | x | | x | | | | -| ASSET-D-40 | ML models that have not been trained yet, i.e., Initial Models and their associated learning algorithm. | Non-RT RIC, Near-RT RIC, SMO | | x | x | | x | x | | | -| Components (logical, virtual, physical) | | | | | | | | | | | -| ASSET-C-01 | Logical module: Service Management and Orchestration (SMO) | | | x | | | x | x | | x | -| ASSET-C-02 | Near-RT RIC | | | x | | | x | x | | x | -| ASSET-C-03 | O-CU-CP | | | x | | | x | x | | x | -| ASSET-C-04 | O-CU-UP | | | x | | | x | x | | x | -| ASSET-C-05 | O-DU | | | x | | | x | x | | x | -| ASSET-C-06 | O-RU | | | x | | | x | x | | x | -| ASSET-C-07 | O-eNB | | | x | | | x | x | | x | -| ASSET-C-08 | O-Cloud | | | x | | | x | x | | x | -| ASSET-C-09 | xApps | | | x | | | x | x | | x | -| ASSET-C-10 | rApps | | | x | | | x | x | | x | -| ASSET-C-11 | Non-RT RIC | | | x | | | x | x | | x | -| ASSET-C-12 | ML components deploying machine learning such as: ML training and inference hosts, ML applications (xAPPS, rAPPS) | | | x | | | x | x | | x | - -| Asset ID | Asset Description | Component | Interface | When | | Protection Level | | | | | -|-------------|-----------------------------------------|-----------|-----------|---------|------------|------------------|-----------|--------------|--------|--------------| -| | | | | At rest | In transit | Confidentiality | Integrity | Availability | Replay | Authenticity | -| ASSET-C-12a | PNF NF equipment | | | x | | | x | x | | x | -| ASSET-C-13 | A1 termination | | | | x | x | x | x | | x | -| ASSET-C-14 | A1 interface, including protocol stack | | | | x | x | x | x | x | x | -| ASSET-C-15 | R1 termination | | | | x | x | x | x | | x | -| ASSET-C-16 | R1 interface, including protocol stack | | | | x | x | x | x | x | x | -| ASSET-C-17 | SMO Framework/Platform | x | | | | | | x | | x | -| ASSET-C-18 | SMO Functions | x | | | | | | x | | X | -| ASSET-C-19 | R1 Service Exposure Functions | x | | | | | | x | | x | -| ASSET-C-20 | A1 Functions | x | | | | | | x | | x | -| ASSET-C-21 | Data Management and Exposure Functions | x | | | | | | x | | x | -| ASSET-C-22 | O1, including protocol stack | | x | | x | x | x | x | x | x | -| ASSET-C-23 | O2, including protocol stack | | x | | x | x | x | x | x | x | -| ASSET-C-24 | OFH M-Plane, including protocol stack | | x | | x | x | x | x | x | x | -| ASSET-C-25 | OFH CUS-Plane, including protocol stack | | x | | x | x | x | x | x | x | -| ASSET-C-26 | External interfaces | | x | | x | x | x | x | x | x | - -| Asset ID | Asset Description | Component | Interface | When | | Protection Level | | | | | -|------------|-------------------------------------------------------------------------------|-----------------------------|-----------|---------|------------|------------------|-----------|--------------|--------|--------------| -| | | | | At rest | In transit | Confidentiality | Integrity | Availability | Replay | Authenticity | -| ASSET-C-27 | External interfaces termination at SMO Framework/Platform | | x | | x | x | x | x | | x | -| ASSET-C-28 | External interfaces termination at Non-RT RIC Framework | | x | | x | x | x | x | | x | -| ASSET-C-29 | AAL software including software, libraries, drivers, etc. | AAL | | x | | | x | x | | | -| ASSET-C-30 | The hardware accelerator device firmware | Hardware accelerator device | | x | | | x | x | | | -| ASSET-C-31 | Shared O-RU | x | | | | x | x | x | | x | -| ASSET-C-32 | O-RU Host | x | | | | x | x | x | | x | -| ASSET-C-33 | O-RU Tenant (Shared Resource Operator) | x | | | | x | x | x | | x | -| ASSET-C-34 | O-DU Host | x | | | | x | x | x | | x | -| ASSET-C-35 | O-DU Tenant (Shared Resource Operator) | x | | | | x | x | x | | x | -| ASSET-C-36 | O-CU Host, includes O-CU-CP and O-CU-UP software | x | | | | x | x | x | | x | -| ASSET-C-37 | O-CU Tenant (Shared Resource Operator), includes O-CU-CP and O-CU-UP software | x | | | | x | x | x | | x | -| ASSET-C-38 | SMO Host | x | | | | x | x | x | | x | -| ASSET-C-39 | SMO Tenant (Shared Resource Operator) | x | | | | x | x | x | | x | -| ASSET-C-40 | E2 interface, including protocol stack | | x | | x | x | x | x | x | x | - -| Asset ID | Asset Description | Component | Interface | When | | Protection Level | | | | | -|------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|---------|------------|------------------|-----------|--------------|--------|--------------| -| | | | | At rest | In transit | Confidentiality | Integrity | Availability | Replay | Authenticity | -| ASSET-C-41 | E2 Functions (RIC services supported by RIC functional procedures and global procedures, both as defined in [i.25], clause 5.3.1) | x | | | | | | x | | x | -| ASSET-C-42 | Y1 interface, including protocol stack | | x | | x | x | x | x | x | x | -| ASSET-C-43 | Y1 Functions | x | | | | | | x | | x | -| ASSET-C-44 | Service Management and Exposure (SME) | x | | | | x | x | x | | x | -| ASSET-C-45 | Data Management and Exposure (DME) | x | | | | x | x | x | | x | -| ASSET-C-46 | Topology Exposure and Inventory Management (TE&IM) | x | | | | x | x | x | | x | -| ASSET-C-47 | rApp Management | x | | | | x | x | x | | x | -| ASSET-C-48 | R1 Services | x | | | | x | x | x | | x | -| ASSET-C-49 | Network Function Orchestrator (NFO) | x | | | | x | x | x | | x | -| ASSET-C-50 | Federated O-Cloud Orchestration and Management (FOCOM) | x | | | | x | x | x | | x | -| ASSET-C-51 | RAN NF Fault Management (FM) | x | | | | x | x | x | | x | -| ASSET-C-52 | RAN NF Configuration Management (CM) | x | | | | x | x | x | | x | -| ASSET-C-53 | RAN NF Performance Management (PM) | x | | | | x | x | x | | x | -| ASSET-C-54 | A1 Enrichment Information Management | x | | | | x | x | x | | x | -| ASSET-C-55 | A1 Policy Management | x | | | | x | x | x | | x | - -| Asset ID | Asset Description | Component | Interface | When | | Protection Level | | | | | -|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|-----------|---------|------------|------------------|-----------|--------------|--------|--------------| -| | | | | At rest | In transit | Confidentiality | Integrity | Availability | Replay | Authenticity | -| ASSET-C-56 | A1 E1 Management | x | | | | x | x | x | | x | -| ASSET-C-57 | SW Package Onboarding | x | | | | x | x | x | | x | -| ASSET-C-58 | Service Orchestration | x | | | | x | x | x | | x | -| ASSET-C-59 | Service Assurance | x | | | | x | x | x | | x | -| ASSET-C-60 | RAN Analytics | x | | | | x | x | x | | x | -| ASSET-C-61 | R1 service: AI/ML workflow services, as specified in [i.38], clause 7.7 | x | | | | x | x | x | | x | -| ASSET-C-62 | SMOS Communication | | x | | x | x | x | x | x | x | -| ASSET-C-63 | Near RT RIC API's

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 [i.6]. | | x | | x | x | x | x | x | x | -| ASSET-C-64 | Near-RT RIC platform service: AI/ML workflow services, as specified in [i.8], clause 6A.2.7 | x | | | | x | x | x | | x | - -# 7 Threat model - -## 7.1 Threat surface - -The O-RAN architecture [i.6] introduces new functions and interfaces. The introduction of additional interfaces and nodes, and the decoupling of hardware and software, expands the threat and attack surface of the network. For the purposes of this document, threat surfaces are divided into six (6) main groups: - -- Additional functions: SMO, Non-Real-Time RIC, Near-Real-Time RIC, O-Cloud, O-RU, O-DU, O-CU -- Additional open interfaces: A1, E2, O1, O2, Open Fronthaul, Y1, R1 -- Modified architecture: Lower Layer Split (LLS) 7-2x -- Decoupling increases threat to Trust Chain -- Containerization and Virtualization: Disaggregation of software and hardware -- Exposure to public exploits may be increased due to use of Open Source Code - -The following entry points are considered: - -- API between planes which facilitate the propagation of threats -- Threats coming from inside the O-RAN system -- Threats coming from outside the O-RAN system - -## 7.2 Threat agent - -For the purposes of this document, threat agents are categorized as follows: - -- Cyber-criminals: Represents individuals who commits cybercrimes, where he/she makes use of the computer either as a tool or as a target or as both. -- Insiders: Represents malicious attacks perpetrated on a network or computer system by a person with authorized system access. -- Hacktivists: Represents actors that perform cyber-attacks to achieve political or social gains. -- Cyber-terrorists: Represents actors that their sole aim of violence against clandestine agents and subnational groups through the compromise of O-RAN infrastructures. -- Script kiddies: Represents actors that do not poses deep technical expertise or resources to perform sophisticated attacks. -- Nation-State: actors aggressively target and gain persistent access to public and private sector networks to compromise, steal, change, or destroy information. - -## 7.3 Potential vulnerabilities - -This document addresses the following potential security vulnerabilities that are exploitable through attacks against Confidentiality, Integrity, and Availability: - -- O-RAN specific vulnerabilities - - Unauthorized access to O-DU, O-CU-CP, O-CU-UP and RU to degrade RAN performance or execute broader network attack (Availability) - -- Unprotected synchronization and control plane traffic on Open Fronthaul Interface (Integrity and Availability) -- Disable over-the-air ciphers for eavesdropping (Confidentiality) -- Near-RT RIC conflicts with O-gNB (Availability) -- x/rApps conflicts (Availability) -- x/rApps access to network and subscriber data (Confidentiality) -- Unprotected management interface (Confidentiality, Integrity, Availability) -- CP UL or DL messages can be injected for attack on UP (Availability) -- General vulnerabilities - - Decoupling of functions without hardware root of trust and software trust chain (Integrity) - - Exposure to public exploits from use of Open Source code (Confidentiality, Integrity, Availability) - - Misconfiguration, poor isolation or insufficient access management in the O-Cloud platform (Confidentiality, Integrity, Availability) - -## 7.4 Threats - -### 7.4.0 Threat Structure - -The threat analysis is carried out using a well-defined structure to present each threat case and simplify the risk analysis associated with each threat. The following table is the template used to present the threat characteristics: - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------| -| Threat ID | Unique identification per Threat (e.g. T-XX-01) | -| Threat title | Title of the threat | -| Threat description | Description of the Threat | -| Threat type | Spoofing
Tampering
Repudiation
Information disclosure
Denial of Service
Elevation of Privilege | -| Vulnerabilities | What vulnerabilities are related to the threat? | -| Impact type | Authenticity
Integrity
Non-repudiation
Confidentiality
Availability
Authorization | -| Affected Assets | Impacted Asset(s) (Data & Component) | - -1 For identifying threat types, we are using STRIDE, which categories threats into six distinct types: - -- 2 1. S - Spoofing identity. An application or program can masquerade as another to gain advantages not typically -- 3 allowed for that program. -- 4 2. T - Tampering with data. This involves the malicious modification of data, including making unauthorized -- 5 changes to a database and alteration of data as it flows between computers. -- 6 3. R - Repudiation. A user or program refuses the authenticity of a good or reasonable command or action. -- 7 4. I - Information disclosure. This involves the exposure of information to individuals with unauthorized access -- 8 to it. For example, users gain the ability to read a file that they normally would not have been granted access -- 9 to, or an intruder can read data in transit between computers. -- 10 5. D - Denial of service. These attacks deny service to valid users, such as making a website unavailable or -- 11 unusable by flooding it with illegitimate requests to keep legitimate users without access. -- 12 6. E - Elevation of privileges. An unauthorized user gains privileged rights to access previously not granted to -- 13 compromise or destroy the system, such as a change in membership. - -14 STRIDE maps different threat types to their corresponding impacts on system security, as shown in the following table: - -| Threat types | Impact types | -|------------------------|-------------------| -| Spoofing | Authenticity | -| Tampering | Integrity | -| Repudiation | Non-repudiability | -| Information disclosure | Confidentiality | -| Denial of Service | Availability | -| Elevation of Privilege | Authorization | - -###### 15 7.4.1 Threats against O-RAN system - -###### 16 7.4.1.1 Common among O-RAN architecture elements - -17 The O-RAN system architecture introduces the following common threats among its architecture elements: - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-O-RAN-01 | -| Threat title | An attacker gains unauthorized access to O-RAN architecture elements and escalates privileges | -| Threat description | Attackers can exploit insecure designs (missing or improper authentication, poor security architecture), operational misconfigurations (default credentials, disabled security features, or improperly configured permissions), weak boundary defences (firewall bypass, inadequate session management), or open O-RAN interfaces (no mutual authentication, outdated TLS). They may also install malicious firmware or boot O-RAN architecture elements from unauthorized devices, enabling them to spoof legitimate identities and gain elevated privileges. These conditions allow attackers to infiltrate O-RAN architecture elements, assume elevated privilege, and compromise critical system resources. | -| Threat type | Spoofing, Elevation of Privilege | -| Vulnerabilities | Missing or weak access control policies
Default or poorly managed credentials
No mutual authentication for interfaces or components
Lack of secure password policy (failure to block repeated failed logins)
Exposed credentials or critical data in plaintext | - -| | | -|------------------------|----------------------------------------------------------------------------------------------------------------------------| -| Impact type | Weak boundary defences | -| | Authenticity, Authorization | -| Affected Assets | ASSET-D-10, ASSET-D-11, ASSET-D-12, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-20, ASSET-D-22 to ASSET-D-39 | -| | ASSET-C-01 to ASSET-C-12, ASSET-C-13, ASSET-C-14, ASSET-C-15, ASSET-C-16, ASSET-C-17, ASSET-C-18, ASSET-C-21 to ASSET-C-43 | - -1 - -| | | -|------------------|--------------------------| -| Threat ID | T-O-RAN-02 (Void) | -|------------------|--------------------------| - -2 - -| | | -|------------------|--------------------------| -| Threat ID | T-O-RAN-03 (Void) | -|------------------|--------------------------| - -3 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-O-RAN-04 | -| Threat title | An attacker disrupts O-RAN service availability | -| Threat description | Attackers overload or block O-RAN services through various means, including insecure designs (insufficient resource handling), misconfigurations (unnecessary ports, disabled security features), weak boundary defences (lack of rate-limiting or traffic shaping), open interface flaws (malformed requests), or distributed denial-of-service (DDoS) attacks such as IoT-based botnets. Other techniques, such as amplification attacks exploiting protocol deficiencies, may also be used. By causing resource exhaustion or performance degradation, these attacks can prevent legitimate users from accessing O-RAN functionality and can disrupt critical synchronization or management tasks across the network. | -| Threat type | Denial of Service | -| Vulnerabilities | No or weak rate-limiting and traffic-shaping | -| | Enabled unnecessary services or ports | -| | Failure to manage resource usage (CPU, memory) | -| | Insufficient capacity for unexpected traffic spikes | -| | Lack of failover or load-balancing to handle DoS surges | -| Impact type | Open interface flaws (e.g., malformed requests leading to unexpected behavior or resource exhaustion) | -| | Availability | -| Affected Assets | ASSET-D-01, ASSET-D-04, ASSET-D-05, ASSET-D-06, ASSET-D-09, ASSET-D-21 to ASSET-D-32 to ASSET-D-39 | -| | ASSET-C-01 to ASSET-C-43 | - -4 - -| | | -|------------------|--------------------------| -| Threat ID | T-O-RAN-05 (Void) | -|------------------|--------------------------| - -5 - -| | | -|------------------|--------------------------| -| Threat ID | T-O-RAN-06 (Void) | -|------------------|--------------------------| - -6 - -| | | -|---------------------|--------------------------------------------------------------------------------------------------| -| Threat ID | T-O-RAN-07 | -| Threat title | An attacker hides malicious activities due to insufficient logging and auditing. | -| Threat | Inadequate logging, auditing, or traceability enables attackers to conceal malicious actions and | - -| | | -|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| description | maintain plausible deniability. These shortcomings can stem from insecure designs (no robust logging), misconfigurations (weak or disabled audit trails), gaps in logging at system boundaries (e.g., missing ingress/egress logs), open O-RAN interfaces (no event correlation), or non-normalized log formats that complicate detection. Attackers may also tamper with or remove log files if no mechanisms are in place to verify log integrity, impeding forensic investigations and enabling persistent threats. | -| Threat type | Repudiation | -| Vulnerabilities | Missing or inadequate security event logs
No system references (IP, MAC, timestamps) in log entries
Lack of replay detection or event correlation
Unprotected or tamper-prone log files (no integrity checks)
Fragmented or non-normalized log formats preventing correlation | -| Impact type | Non-repudiation | -| Affected Assets | ASSET-D-02, ASSET-D-03, ASSET-D-22 to ASSET-D-39
ASSET-C-01 to ASSET-C-43 | - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-O-RAN-08 | -| Threat title | An attacker manipulates or intercepts O-RAN data, compromising integrity and confidentiality. | -| Threat description | Due to insecure designs (e.g., poor encryption, missing integrity checks), misconfigured architecture elements (exposed ports/services, lack of secure storage), boundary protocol flaws (weak or no encryption, incorrect sequence handling), open O-RAN interfaces (lacking replay protection, using outdated TLS), or software integrity failures (booting from unauthorized memory devices or applying malicious firmware), attackers can tamper with data or intercept sensitive information. This includes altering critical parameters in transit, exposing private keys and certificates, or injecting malware via unverified updates, undermining the integrity and confidentiality of O-RAN operations. | -| Threat type | Tampering, Information Disclosure | -| Vulnerabilities | Weak or missing encryption (TLS < 1.2, SSH password auth)
No or insufficient integrity checks for data (in transit or at rest)
Poor replay protection or insecure protocol steps
Failure to validate software packages or firmware
Exposed administrative functions displaying confidential data
Lack of secure storage for sensitive data | -| Impact type | Integrity, Confidentiality | -| Affected Assets | ASSET-D-01 to ASSET-D-10, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-19, ASSET-D-22 to ASSET-D-39
ASSET-C-01 to ASSET-C-43 | - -| | | -|------------------|--------------------------| -| Threat ID | T-O-RAN-09 (Void) | -|------------------|--------------------------| - -| | | -|------------------|--------------------------| -| Threat ID | T-O-RAN-10 (Void) | -|------------------|--------------------------| - -###### 1 7.4.1.2 Threats against the Open Fronthaul interface and M-S-C-U planes - -2 The LLS architecture and the fronthaul interface introduce the following threats: - -![Diagram of O-RAN LLS (7-2x) architecture showing Northbound n/w, O-DU, and O-RU components. It illustrates 'Original connection' and 'New connection' paths, with a 'Man-in-the-Middle' attacker icon labeled 'Attacks' targeting the O-DU. Text at the bottom describes 'Man-in-the-Middle Attacks and unauthorized access to O-DU to degrade n/w service or execute broader n/w attack through the O-DU'.](1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg) - -Diagram of O-RAN LLS (7-2x) architecture showing Northbound n/w, O-DU, and O-RU components. It illustrates 'Original connection' and 'New connection' paths, with a 'Man-in-the-Middle' attacker icon labeled 'Attacks' targeting the O-DU. Text at the bottom describes 'Man-in-the-Middle Attacks and unauthorized access to O-DU to degrade n/w service or execute broader n/w attack through the O-DU'. - -3 -4 -5 - -Figure Threat model-2 : Threats and Vulnerabilities for O-RAN LLS 7-2x - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-FRHAUL-01 | -| Threat title | An attacker penetrates O-DU and beyond through O-RU or the Fronthaul interface to access or modify sensitive information [i.12] | -| Threat description | When having two different vendors, the O-RU and the O-DU needs to be managed as different entities and may have heterogeneous security levels. Instead, the O-DU will have to bridge the management traffic between the management system and the O-RU. Hence, the bridged traffic becomes a possible attack vector in this split architecture, allowing an attacker to potentially access or modify sensitive information. | -| Threat type | Information disclosure, Tampering | -| Vulnerabilities | Heterogeneous security levels between O-RU and O-DU provided by different vendors | -| Impact type | Confidentiality, Integrity | -| Affected Assets | Critical S-Plane data [ASSET-D-01],
Critical Management-Plane data [ASSET-D-02],
Critical C-Plane data [ASSET-D-04],
Critical Fronthaul U-Plane data [ASSET-D-05] | - -6 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-FRHAUL-01A | -| Threat title | An attacker penetrates O-DU and beyond through O-RU or the Fronthaul interface to impersonate a legitimate system or user [i.12] | -| Threat description | When having two different vendors, the O-RU and the O-DU need to be managed as different entities and may have heterogeneous security levels. Instead, the O-DU will have to bridge the management traffic between the management system and the O-RU. Hence, an attacker could potentially exploit the bridging mechanism to impersonate a legitimate system or user, allowing them to access the northbound systems beyond the O-DU through the Open Fronthaul interface. | -| Threat type | Spoofing | -| Vulnerabilities | Heterogeneous security levels between O-RU and O-DU provided by different vendors | - -| | | -|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Impact type | Authenticity | -| Affected Assets | Critical S-Plane data [ASSET-D-01],
Critical Management-Plane data [ASSET-D-02],
Critical C-Plane data [ASSET-D-04],
Critical Fronthaul U-Plane data [ASSET-D-05] | - -1 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-FRHAUL-02 | -| Threat title | Unauthorized access to Open Fronthaul Ethernet L1 physical layer interface(s) to obtain protected information | -| Threat description |

The Open Fronthaul Ethernet L1 physical interface comprises one or more coaxial cables, twisted pairs, or optical fibers. Each end of the Open Fronthaul Ethernet L1 physical interface comprises a physical connection (colloquially known as an Ethernet Port) to physical O-RAN network elements, e.g., O-DU, O-RU, etc.

Unauthorized access to the Open Fronthaul Ethernet L1 physical layer interface (cables and connections) provides a means to launch attacks on the availability, integrity, and confidentiality of the Open Fronthaul system.

Potential loss of confidentiality on the Open Fronthaul interface can occur from one or more of the following threats:

  • • An unauthorized device on the Ethernet L1 Interface has access to U-Plane traffic on the Open Fronthaul Interface.
  • • An unauthorized device on the Ethernet L1 Interface has access to S-Plane traffic on the Open Fronthaul Interface.
  • • An unauthorized device on the Ethernet L1 Interface has access to C-Plane traffic on the Open Fronthaul Interface.
  • • An unauthorized device on the Ethernet L1 Interface has access to M-Plane traffic on the Open Fronthaul Interface.
| -| Threat type | Information disclosure | -| Vulnerabilities | Lack of authentication and access control to the Open Front Haul Ethernet L1 physical layer interface | -| Impact type | Confidentiality | -| Affected Assets | Critical S-Plane data [ASSET-D-01],
Critical Management-Plane data [ASSET-D-02],
Critical C-Plane data [ASSET-D-04],
Critical Fronthaul U-Plane data [ASSET-D-05] | - -2 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-FRHAUL-03 | -| Threat title | Unauthorized access to Open Fronthaul Ethernet L1 physical layer interface(s) to disrupt services | -| Threat description |

The Open Fronthaul Ethernet L1 physical interface comprises one or more coaxial cables, twisted pairs, or optical fibers. Each end of the Open Fronthaul Ethernet L1 physical interface comprises a physical connection (colloquially known as an Ethernet Port) to physical O-RAN network elements, e.g., O-DU, O-RU, etc.

Unauthorized access to the Open Fronthaul Ethernet L1 physical layer interface (cables and connections) provides a means to launch attacks on the availability, integrity, and confidentiality of the Open Fronthaul system.

Potential loss of availability on the Open Fronthaul interface can occur from one or more of the

| - -| | | -|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | following threats:
  • An unauthorized device on the Ethernet L1 Interface can flood the L1 interface with unintended network traffic causing disruption or degradation of authorized network elements on the Open Fronthaul interface.
  • An unauthorized device on the Ethernet L1 Interface can send Ethernet- L2 messages to authorized network devices causing disruption, denial, or degradation of the Open Fronthaul interface.
  • An attacker (person) gains access to the Open Fronthaul Ethernet L1 interface(s) and denies the Open Fronthaul services by disabling a physical connection to a network element either by removing an Ethernet port connection or cutting the physical interface (coaxial cable, twisted pair, or optical fiber).
| -| Threat type | Denial of Service | -| Vulnerabilities | Lack of authentication and access control to the Open Front Haul Ethernet L1 physical layer interface | -| Impact type | Availability | -| Affected Assets | Critical S-Plane data [ASSET-D-01],
Critical Management-Plane data [ASSET-D-02],
Critical C-Plane data [ASSET-D-04],
Critical Fronthaul U-Plane data [ASSET-D-05] | - -1 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-MPLANE-01 | -| Threat title | An attacker attempts to intercept the Fronthaul (MITM) over M Plane to obtain protected information | -| Threat description | The High bit rate Fronthaul interface imposes strict performance requirements ((bandwidth, latency, fronthaul transport link length, etc.) that limit the use of some security features, due to the increased processing delay. This opens the risk of passive wiretapping over the fronthaul interface to intercept the M plane. | -| Threat type | Information disclosure | -| Vulnerabilities | Lack of sufficient security measures in the Fronthaul due to the negative impact on the performance requirements | -| Impact type | Confidentiality | -| Affected Assets | Critical Management-Plane data [ASSET-D-02],
Critical Management-Plane data transported over the O1 interface [ASSET-D-03] | - -2 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-MPLANE-02 | -| Threat title | An attacker attempts to intercept the Fronthaul (MITM) over M Plane to alter m-plane data | -| Threat description | The High bit rate Fronthaul interface imposes strict performance requirements ((bandwidth, latency, fronthaul transport link length, etc.) that limit the use of some security features, due to the increased processing delay. This opens the risk of Man-in-the-Middle (MITM) attacks over the fronthaul interface to intercept and modify the M plane. | -| Threat type | Tampering | -| Vulnerabilities | Lack of sufficient security measures in the Fronthaul due to the negative impact on the performance requirements | -| Impact type | Integrity | -| Affected Assets | Critical Management-Plane data [ASSET-D-02],
Critical Management-Plane data transported over the O1 interface [ASSET-D-03] | - -3 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-MPLANE-03 | -| Threat title | An attacker attempts to intercept the Fronthaul (MITM) over M Plane to disrupt services | -| Threat description | The High bit rate Fronthaul interface imposes strict performance requirements ((bandwidth, latency, fronthaul transport link length, etc.) that limit the use of some security features, due to the increased processing delay. This opens the risk of an Attacker to launch a Denial of Service (DoS) attack over the fronthaul interface to disrupt the M plane | -| Threat type | Denial of Service | -| Vulnerabilities | Lack of sufficient security measures in the Fronthaul due to the negative impact on the performance requirements | -| Impact type | Availability | -| Affected Assets | Critical Management-Plane data [ASSET-D-02],
Critical Management-Plane data transported over the O1 interface [ASSET-D-03] | - -1 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SPLANE-01 | -| Threat title | DoS attack against a Master clock | -| Threat description |

A denial of service (DoS) attack towards a Master clock of the timing network used by the open Fronthaul to maintain the availability and accuracy of the Master clock. An attacker can attack a master clock by sending an excessive number of time protocol packets or impersonate a legitimate clock, a slave, or an intermediate clock, by sending malicious messages to the master, thus degrading the victim's performance.

The attacker may be residing either within the attacked network (insider) or on an external network connected to the attacked network.

This attack results in a situation where the clock service is interrupted completely, or the timing protocol is operational, but slaves are being provided inaccurate timing information due the degraded performance of the Master clock.

This clock service disruption or degradation in the accuracy of time may cause DoS to applications on all the RUs that rely on accurate time, potentially bringing down the cell.

A cell outage caused by misaligned time, may further impact performance in connected neighbouring cells.

| -| Threat type | Denial of Service | -| Vulnerabilities |
  • - Improper process to monitor and manage the performance of the Master clock
  • - ANNOUNCE messages can be sent publicly in clear text
| -| Impact type | Availability | -| Affected Assets | Critical S-Plane data [ASSET-D-01] | - -2 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SPLANE-02 | -| Threat title | Impersonation of a Master clock (Spoofing) within a PTP network with a fake ANNOUNCE message | -| Threat description |

An attacker within the PTP network can impersonate the master clock's grandmasterIdentity value and propose himself as a grandmaster candidate by sending fake ANNOUNCE messages declaring him to be the best clock in the network. The attacker may be residing either within the attacked network (insider) or on an external network connected to the attacked network.

This attack results in a situation where the attacker clock becomes a GM, PTP is operational, all

| - -| | | -|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

clocks are synchronized, but the malicious GM provides intentionally inaccurate timing information.

This degradation in the accuracy of time may cause DoS to applications on all the RUs that rely on accurate time, potentially bringing down the cell.

A cell outage caused by misaligned time, may further impact performance in connected neighbouring cells.

| -| Threat type | Denial of Service | -| Vulnerabilities |
  • - Inaccurate timing information
  • - Improper synchronization between clocks
  • - ANNOUNCE messages can be sent publicly in clear text
| -| Impact type | Availability | -| Affected Assets | Critical S-Plane data [ASSET-D-01] | - -1 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SPLANE-03 | -| Threat title | A Rogue PTP Instance wanting to be a Grand Master | -| Threat description |

An attacker can propose himself as a grandmaster candidate by sending manipulated/malicious ANNOUNCE messages declaring him to be the best clock in the network. The attacker causes other nodes in the network to believe it is a legitimate master. The attacker is internal to the attacked PTP network and could launch this attack by either modification of in-flight protocol packets or injecting fake ANNOUNCE messages to the PTP network. It is assumed that an MITM attacker has physical access to a segment of the network or has gained control of one of the nodes in the network. This attack results in a situation where the time protocol is operational, but slaves are being provided intentionally inaccurate timing information.

This degradation in the accuracy of time may cause DoS to applications on all the RUs that rely on accurate time, potentially bringing down the cell.

A cell outage caused by misaligned time, may further impact performance in connected neighbouring cells.

| -| Threat type | Denial of Service | -| Vulnerabilities |
  • - Inaccurate timing information
  • - Improper synchronization between clocks
  • - ANNOUNCE messages can be sent publicly in clear text
| -| Impact type | Availability | -| Affected Assets | Critical S-Plane data [ASSET-D-01] | - -2 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SPLANE-04 | -| Threat title | Selective interception and removal of PTP timing packets | -| Threat description |

An attacker can position himself in such way that allows him to intercept and remove valid synchronization packets. This leads to clock synchronization errors of all clocks downstream or makes them go into free-running mode.

Attacks may be launched close to the GM by tapping the egress line of an active GM clock. This impacts a larger set of slaves who depend on this GM for timing synchronization.

Attacks may also target a one or more slaves. This is done by tapping the ingress line of a particular

| - -| | | -|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

slave(s). The impact is confined to the targeted slaves.

Alternatively, a MiTM attacker can reside in an intermediate node such as TCs, routers and switches to launch this attack. The attacker has physical access to a node of the PTP n/w or has gained full control of one device in the network. This requires additional capability to tap the h/w where PTP timing is implemented.

Selective interception and removal can impact timing packets and cause clock degradation in attacked nodes. Removing all packets or random packets may push the clocks in attacked nodes into free running mode

This attack results in a situation where the time protocol is operational, but slaves are being provided intentionally inaccurate timing information.

This degradation in the accuracy of time may cause DoS to applications on all the RUs that rely on accurate time, potentially bringing down the cell.

A cell outage caused by misaligned time, may further impact performance in connected neighbouring cells.

| -| Threat type | Denial of Service | -| Vulnerabilities |
  • - Inaccurate timing information
  • - Improper synchronization between clocks
  • - ANNOUNCE messages can be sent publicly in clear text
| -| Impact type | Availability | -| Affected Assets | Critical S-Plane data [ASSET-D-01] | - -1 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SPLANE-05 | -| Threat title | Packet delay manipulation attack | -| Threat description |

IEEE 1588 requires symmetric delays between GM and slaves. In packet delay manipulation attacks, the attacker is positioned such a way that allows him to delay the transmission of legitimate time synchronization protocol packets to the intended destination.

An attacker launches this attack by either tapping the transmission network or by taking control of an intermediate nodes such as routers, switches and T-TCs.

This attack results in a situation where the time protocol is operational, but slaves are being provided intentionally inaccurate timing information.

This degradation in the accuracy of time may cause DoS to applications on all the RUs that rely on accurate time, potentially bringing down the cell.

A cell outage caused by misaligned time, may further impact performance in connected neighbouring cells.

| -| Threat type | Denial of Service | -| Vulnerabilities |
  • - Inaccurate timing information
  • - Improper synchronization between clocks
  • - ANNOUNCE messages can be sent publicly in clear text
| -| Impact type | Availability | -| Affected Assets | Critical S-Plane data [ASSET-D-01] | - -2 - -1 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-CPLANE-01 | -| Threat title | Spoofing of DL C-plane messages | -| Threat description |

The lack of authentication could allow an adversary to inject their own DL C-plane messages that falsely claim to be from the associated O-DU.

As a result, it would block the O-RU from processing the corresponding U-Plane packets, leading to temporary DoS. (Dropping the entire DL C-plane messages achieves the same goal).

| -| Threat type | Denial of Service | -| Vulnerabilities | Lack of authentication could allow an adversary to inject DL C-plane messages | -| Impact type | Availability | -| Affected Assets | Critical C-Plane data [ASSET-D-04] | - -2 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-CPLANE-02 | -| Threat title | Spoofing of UL C-plane messages | -| Threat description |

The lack of authentication could allow an adversary to inject their own UL C-plane messages that falsely claim to be from the associated O-DU.

As a result, temporarily limited cell performance (or even DoS) on cells served by the O-RU and in addition a consequential DoS threat to all O-RUs served by that O-DU will exist. (Dropping the entire UL C-plane messages achieves the same goal).

| -| Threat type | Denial of Service | -| Vulnerabilities | Lack of authentication could allow an adversary to inject UL C-plane messages | -| Impact type | Availability | -| Affected Assets | Critical C-Plane data [ASSET-D-04] | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-UPLANE-01 | -| Threat title | An attacker attempts to intercept the Fronthaul (MITM) over U-Plane to obtain user data | -| Threat description |

The High bit rate Fronthaul interface impose strict performance requirements ((bandwidth, latency, fronthaul transport link length, etc.) that limit the use of some security features, due to the increased processing delay. This opens the risk of Man-in-the-Middle (MITM) attacks over the fronthaul interface to intercept the U-Plane.

For the transported U-Plane data an attacker could potentially do threats, such as passive wiretapping and intercept sensitive information.

3GPP defines UP integrity protection algorithms in their specifications but many of the OEMs have not implemented them because of impact on the user experience (e.g. download and upload data throughputs). Enabling UP integrity protection requires considerable compute resources and adds overhead that directly impacts the maximum throughputs that can be measured on the user device. The integrity protection is enabled on the Control Plane messages but that still leaves the user's data traffic vulnerable because the Control Plane and User Plane are segregated. For example, the lack of UP integrity could enable an attacker to intercept user data.

| -| Threat type | Information disclosure | -| Vulnerabilities | Lack of sufficient security measures in the Fronthaul due to the negative impact on the performance requirements | -| Impact type | Confidentiality | - -1 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Affected Assets | Critical Fronthaul U-Plane data [ASSET-D-05] | -| Threat ID | T-UPLANE-02 | -| Threat title | An attacker attempts to intercept the Fronthaul (MITM) over U-Plane to modify u-plane data | -| Threat description |

The High bit rate Fronthaul interface impose strict performance requirements ((bandwidth, latency, fronthaul transport link length, etc.) that limit the use of some security features, due to the increased processing delay. This opens the risk of Man-in-the-Middle (MITM) attacks over the fronthaul interface to intercept the U-Plane.

For the transported U-Plane data an attacker could potentially manipulate the data, such as modifying or altering the contents.

3GPP defines UP integrity protection algorithms in their specifications but many of the OEMs have not implemented them because of impact on the user experience (e.g. download and upload data throughputs). Enabling UP integrity protection requires considerable compute resources and adds overhead that directly impacts the maximum throughputs that can be measured on the user device. The integrity protection is enabled on the Control Plane messages but that still leaves the user's data traffic vulnerable because the Control Plane and User Plane are segregated. For example, the lack of UP integrity could enable a rogue base station to manipulate the user data messages (i.e. DNS) and redirect a user to a malicious website.

| -| Threat type | Tampering | -| Vulnerabilities | Lack of sufficient security measures in the Fronthaul due to the negative impact on the performance requirements | -| Impact type | Integrity | -| Affected Assets | Critical Fronthaul U-Plane data [ASSET-D-05] | - -2 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-UPLANE-03 | -| Threat title | An attacker attempts to intercept the Fronthaul (MITM) over U-Plane to disrupt services | -| Threat description |

The High bit rate Fronthaul interface impose strict performance requirements ((bandwidth, latency, fronthaul transport link length, etc.) that limit the use of some security features, due to the increased processing delay. This opens the risk of Man-in-the-Middle (MITM) attacks over the fronthaul interface to disrupt the U-Plane.

For the transported U-Plane data an attacker could potentially launch a Denial of Service (DoS) attack, overwhelming the fronthaul interface and impacting the performance and availability of the service.

3GPP defines UP integrity protection algorithms in their specifications but many of the OEMs have not implemented them because of impact on the user experience (e.g. download and upload data throughputs). Enabling UP integrity protection requires considerable compute resources and adds overhead that directly impacts the maximum throughputs that can be measured on the user device. The lack of UP integrity could enable an attacker to launch a DoS attack on the fronthaul interface, causing service disruption and impacting user experience.

| -| Threat type | Denial of Service | -| Vulnerabilities | Lack of sufficient security measures in the Fronthaul due to the negative impact on the performance requirements | -| Impact type | Availability | -| Affected Assets | Critical Fronthaul U-Plane data [ASSET-D-05] | - -3 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-UPLANE-04 | -| Threat title | Spoofing and unauthorized access of U-Plane data packets | -| Threat description | The lack of authentication and authorization mechanisms could allow an adversary to spoof a legitimate O-DU or O-RU. Once spoofed, the attacker could tamper with or inject their own U-plane data packets, falsely masquerading as those from the legitimate O-DU or O-RU. This could lead to the processing of altered or corrupted data, degrading service quality, or even causing a Denial of Service (DoS). | -| Threat type | Spoofing, Elevation of privilege | -| Vulnerabilities | Lack of authentication, and authorization protection for U-Plane data packets | -| Impact type | Authenticity, Authorization | -| Affected Asset | Critical Fronthaul U-Plane data [ASSET-D-05] | - -#### 7.4.1.3 Threats against O-RU - -##### 7.4.1.3.1 Generic threats - -The O-RU introduces the following threats: - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-ORU-01 | -| Threat title | An attacker stands up a false base station attack by attacking an O-RU | -| Threat description |

A false base station attack occurs when an attacker masquerades as a legitimate mobile network to facilitate a Man-in-The-Middle (MiTM) attack between a subscriber's user equipment (UE) and the mobile network.

There are three attack scenarios on an O-RU that enable an attacker to realize a false base station attack:

  1. 1. Hijack fronthaul to realize a false base station attack: Attacker disables an operational O-RU's access to the open fronthaul, plugs a false base station system into the operational O-RU's fronthaul interface, and launches a false base station attack with the O-RU providing the air interface.
  2. 2. Recruit a standalone O-RU to realize a false base station attack: The stand-alone O-RU is an O-RU that is not operational but is available to an attacker to incorporate into a false base station system. The attacker plugs a false base station system into the standalone O-RU's fronthaul interface and launches a false base station attack with the O-RU providing the air interface.
  3. 3. Gain unauthorized physical access to O-RU to realize a false base station attack: An attacker gains access to external and internal components of an O-RU (other than the open fronthaul interface), connects the O-RU under attack to a false base station system, and launches a false base station attack with the O-RU providing the air interface.

Successful attacks may cause:

  1. 1. For the operator network: in attack scenario 1, the attacker removes the operational O-RU from providing service to UEs in the coverage area served by the operational O-RU.
  2. 2. For operators and vendors in attack scenarios 1, 2, and 3, the attacker recruits legitimate operator/vendor equipment for the purpose of creating a false base station attack on subscribers, possibly harming the reputation of the operator and vendor whose O-RU was used in the attack.
  3. 3. Successful attacks may realize in a false base station and may further cause impact to subscriber's UE. For a subscriber's UE in attack scenarios 1, 2, and 3: the false base stations, also known as SUPI/5G-GUTI catchers, retrieves a subscriber identity by forcing a UE to attach to the false base station systems. This opens the door to subscriber identity
| - -| | | -|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

interception/disclosure and unauthorized subscriber tracking attacks. These attacks include stealing subscriber information, tampering with transmitted information, tracking subscribers, and compromising subscriber privacy.

NOTE: The false base station threat has existed since GSM networks were introduced and continued to evolve and persist with the evolution of mobile networks. 5G networks are expected to introduce several security enhancements over 4G and legacy networks. Despite these security enhancements, UEs in 5G networks could still be a target of false base station attacks [i.19].

| -| Threat Type | Denial of Service | -| Vulnerabilities | False O-RUs | -| Impact Type | Availability | -| Affected Assets |

O-RU-Software [ASSET-C-06]

Shared O-RU [ASSET-C-31]

O-RU Host [ASSET-C-32]

O-RU Tenant (Shared Resource Operator) [ASSET-C-33]

| - -##### 7.4.1.3.2 Centralized user management for the O-RU related threats - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-O-RU-02 | -| Threat title | An attacker leverages the lack of traceability with shared user accounts | -| Threat description | If the O-RU has local shared accounts, multiple controllers (SMO and/or O-DU) may authenticate using the same account, making it impossible to identify which controller performed an action. | -| Threat Type | Repudiation | -| Vulnerabilities | Shared local user accounts are used by multiple entities (e.g., SMO, O-DU) for access | -| Impact Type | Non-repudiation | -| Affected Assets |

O-RAN Components associated and configuration data [ASSET-D-18]

Credentials (Administrators), account information and passwords on O-RAN Architectural elements [ASSET-D-20]

O-RU software [ASSET-C-06]

PNF NF Equipment [ASSET-C-12]

| - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-O-RU-03 | -| Threat title | An attacker manipulates initial provisioning information | -| Threat description |

Before the O-RU centralized user management feature is activated the initial provisioning information containing, for example, the IP address of the centralized authentication and authorization server, needs to be configured in the O-RU. The provisioning information could be in the Software Configuration server for example and transfers the information to the O-RU

O-RU components might be vulnerable if:

  • • Initial provisioning information from the Software configuration server could be manipulated to point to another server rather than the centralized authentication and authorization server.
| -| Threat Type | Tampering, Denial of Service | -| Vulnerabilities | Initial provisioning information from the Software configuration server could be manipulated to point | - -| | | -|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------| -| Impact Type | to another server rather than the centralized authentication and authorization server. | -| | Integrity, Availability | -| Affected Assets | O-RAN Components associated and configuration data [ASSET-D-18] | -| | Credentials (Administrators), account information and passwords on O-RAN Architectural elements [ASSET-D-20]
O-RU Software [ASSET-C-06] | - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-O-RU-04 | -| Threat title | An attacker compromises O-RU user information (i.e. compromises the data integrity, confidentiality of the user information) in an external centralized authentication and authorization server | -| Threat description |

O-RU can connect to a external centralized authentication and authorization server.

The local users on the O-RU should be minimized and the centralized users should be maximized.

Also credentials should be transferred between the O-RU and the centralized authentication and authorization and should be secure.

The centralized authentication and authorization should also store the credentials of the centralized users in a secure manner

O-RU components might be vulnerable if:

  • • O-RU credentials including account information and passwords could be mismanaged, misclassifying O-RU users between centralized and local users which could defeat the purpose of central authentication, authorization and administration
  • • Data in plain text between the O-RU and centralized Authentication and authorization server could be manipulated
  • • O-RU related credentials can be manipulated if not stored securely in the centralised server
| -| Threat Type | Tampering, Information Disclosure | -| Vulnerabilities | Gaps to possibly (1) mismanage O-RU Account information and Credentials, (2) misclassify O-RU users, (3) manipulate O-RU Credentials if not stored securely | -| Impact Type | Integrity, Confidentiality | -| Affected Assets | Credentials (Administrators), account information and passwords on O-RAN Architectural elements [ASSET-D-20] | -| | O-RU Software [ASSET-C-06]
External interfaces [ASSET-C-26] | - -#### **7.4.1.4 Threats against Near-RT RIC** - -Near-Real-Time (RT) RIC introduces the following threats: - -![Diagram titled 'UE identification in Near-RT RIC'. It shows a 'Near-RT RIC' box containing 'xApps' connected to an 'O-CU' box. Below 'O-CU' are 'O-DU' and 'O-RU' boxes. A 'UE' (User Equipment) icon is at the bottom right. An 'Authorized/Unauthorized user' icon (a person with a red face) is on the left. A red arrow points from the user to the 'xApps' with the text 'Can extract UE to random identifier mapping'. A black line with a red skull-and-crossbones triangle points from the user to the 'UE'.](41aef1f5efab13d4f38f69e86c726062_img.jpg) - -### UE identification in Near-RT RIC - -``` - -graph TD - subgraph "Near-RT RIC" - xApps - end - xApps --- O-CU - O-CU --- O-DU - O-DU --- O-RU - O-RU --- UE - User((Authorized/Unauthorized user)) -- "Can extract UE to random identifier mapping" --> xApps - User -- "x" --> UE - -``` - -Diagram titled 'UE identification in Near-RT RIC'. It shows a 'Near-RT RIC' box containing 'xApps' connected to an 'O-CU' box. Below 'O-CU' are 'O-DU' and 'O-RU' boxes. A 'UE' (User Equipment) icon is at the bottom right. An 'Authorized/Unauthorized user' icon (a person with a red face) is on the left. A red arrow points from the user to the 'xApps' with the text 'Can extract UE to random identifier mapping'. A black line with a red skull-and-crossbones triangle points from the user to the 'UE'. - -**Figure Threat model-3 : UE Identification in Near-RT-RIC** - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-NEAR-RT-01 | -| Threat title | Malicious xApps can exploit UE identification, track UE location and change UE priority [i.12] | -| Threat description |

xApps in the Near-RT RIC have the capability to manipulate behaviour of a certain cell, a group of UEs, and a specific UE. A malfunctioning or unavailable root of trust could potentially cause issues on the network and compromise RAN performance, privacy, etc. For example, the xApp could track a certain subscriber or impact service for a subscriber or a dedicated area. In addition, an xApp can receive order via A1 to control a certain UE and if a malfunctioning xApp receives an order to prioritize this UE, then the owner of the malfunctioning xApp knows a VIP that they want to track is in a certain area. With this command exposure, the attacker can obtain a rough location of a very important person and change the order from prioritize to deprioritize for a UE.

Further, E2 interface exposes UE identification that can be exploited by a malicious xApp. As the E2 interface (similar to A1 interface) can point out a certain UE in the network, this will create a correlation between the randomized (anonymized) UE identities between the RAN nodes. For example, a xApp can potentially be used as a “sniffer” for UE identification. The additional challenge for the Near-RT RIC / E2 compared to the Non-RT RIC / A1 is that more frequent signalling is expected over the E2 interface to enable near-real-time operation. Therefore, the UE identifier will be exchanged more frequently over the E2 than over the A1.

| -| Threat type | Information disclosure, Denial of Service | -| Vulnerabilities | Malicious xApps may be used to gain access to UE identification location and priority | -| Impact type | Confidentiality, Availability | -| Affected Assets | 3GPP application related data [ASSET-D-21],
Inter- and intra-slice UE priority [ASSET-D-22],
Near-RT RIC SW [ASSET-C-02],
xApps [ASSET-C-09],
E2 Functions [ASSET-C-41],
Y1 Functions [ASSET-C-43] | - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-NEAR-RT-02 | -| Threat title | Risk of a malicious xApp on Near-RT RIC obtaining protected information | -| Threat description |

The security threats associated with the onboarding and deployment of malicious xApps include:

  • Malicious xApps attaining unauthorized access to the Near-RT RIC and E2 Nodes
  • Malicious xApps abusing radio network information and control capabilities over RAN functions
| - -| | | -|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat type |
  • Malicious xApp exploiting UE identification, tracking UE location and changing UE slice priority
Information disclosure, Elevation of Privilege | -| Vulnerabilities | Improper or missing authentication and authorization of xApps | -| Impact type | Confidentiality, Authorization | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
E2 Node data [ASSET-D-11],
3GPP application related data [ASSET-D-21],
Inter- and intra-slice UE priority [ASSET-D-22] | - -1 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-NEAR-RT-02A | -| Threat title | Risk of a malicious xApp on Near-RT RIC impacting service availability | -| Threat description |

The security threats associated with the onboarding and deployment of malicious xApps include:

  • Malicious xApp impacting service for a subscriber or a dedicated area
| -| Threat type | Denial of Service | -| Vulnerabilities | Improper or missing authentication and authorization of xApps | -| Impact type | Availability | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
E2 Node data [ASSET-D-11],
3GPP application related data [ASSET-D-21],
Inter- and intra-slice UE priority [ASSET-D-22] | - -2 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-NEAR-RT-03 | -| Threat title |

Attackers exploit non authenticated, weakly or incorrectly authenticated Near-RT RIC APIs to obtain protected information

Not mutually authenticating xApps and Near-RT RIC platform APIs could potentially allow attackers to perform the following type of attacks [i.20]:

| -| Threat description |
  • Operating malicious xApp claiming to be genuine in order to request certain services (theft of services) or information (data leakage)
  • Man in the middle attacks between a genuine xApp and a Near-RT RIC platform API
  • Querying network or UE information from a compromised xApp to Near-RT RIC platform (e.g. database via SDL API), thereby leaking potentially sensitive data about network and/or UE (potential privacy issues)
  • Subscribing a malicious xApp to services provided by the Near-RT RIC platform, such as API-related events notifications, discovery of APIs, E2SM, etc.

The use of weak credentials in the process of API authentication can compromise the overall system. The user/password combination isn't considered safe, not only for password related attacks (e.g., brute-force), but also it would represent a high risk to allow xApps, especially 3rd party xApps, to store the user/password combo. This approach would extend the attack surface into xApps side.

As a reference, OWASP API Security Top 10 report [i.21] indicates that authentication mechanisms are often implemented incorrectly, allowing attackers to compromise authentication tokens or to exploit implementation flaws to assume other user's identities temporarily or permanently. Compromising system's ability to identify the client/user, compromises API security overall.

| -| Threat type | Information disclosure, Spoofing | -| Vulnerabilities | Non authenticated, weakly or incorrectly authenticated Near-RT RIC APIs | -| Impact type | Confidentiality, Authenticity | -| Affected Assets | Data transported over the E2 interface [ASSET-D-09],
Database holding data from xApp applications and E2 Node [ASSET-D-10],
E2 Node data [ASSET-D-11],
Credentials (Administrators) [ASSET-D-20], | - -| | | -|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | 3GPP application related data [ASSET-D-21],
Inter- and intra-slice UE priority [ASSET-D-22],
Training or test data and associated labels [ASSET-D-25],
The trained ML model [ASSET-D-26],
Security event log files [ASSET-D-29],
O-RAN specific several UE IDs [ASSET-D-30],
Near-RT-RIC SW [ASSET-C-02],
xApps [ASSET-C-09],
E2 Functions [ASSET-C-41],
Y1 Functions [ASSET-C-43] | -|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| - -1 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-NEAR-RT-03A | -| Threat title | Attackers exploit non authenticated, weakly or incorrectly authenticated Near-RT RIC APIs for MITM attacks | -| Threat description |

Not mutually authenticating xApps and Near-RT RIC platform APIs could potentially allow attackers to perform the following type of attack [i.20]:

  • - Man in the middle attacks between a genuine xApp and a Near-RT RIC platform API

The use of weak credentials in the process of API authentication can compromise the overall system. The user/password combination isn't considered safe, not only for password related attacks (e.g., brute-force), but also it would represent a high risk to allow xApps, especially 3rd party xApps, to store the user/password combo. This approach would extend the attack surface into xApps side.

As a reference, OWASP API Security Top 10 report [i.21] indicates that authentication mechanisms are often implemented incorrectly, allowing attackers to compromise authentication tokens or to exploit implementation flaws to assume other user's identities temporarily or permanently. Compromising system's ability to identify the client/user, compromises API security overall.

| -| Threat type | Tampering | -| Vulnerabilities | Non authenticated, weakly or incorrectly authenticated Near-RT RIC APIs | -| Impact type | Integrity | -| Affected Assets | Data transported over the E2 interface [ASSET-D-09],
Database holding data from xApp applications and E2 Node [ASSET-D-10],
E2 Node data [ASSET-D-11],
Credentials (Administrators) [ASSET-D-20],
3GPP application related data [ASSET-D-21],
Inter- and intra-slice UE priority [ASSET-D-22],
Training or test data and associated labels [ASSET-D-25],
The trained ML model [ASSET-D-26],
Security event log files [ASSET-D-29],
O-RAN specific several UE IDs [ASSET-D-30],
Near-RT-RIC SW [ASSET-C-02],
xApps [ASSET-C-09],
E2 Functions [ASSET-C-41],
Y1 Functions [ASSET-C-43] | - -2 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-NEAR-RT-04 | -| Threat title | Attackers exploit non authorized Near-RT RIC APIs to access resources and services which they are not entitled to use, to obtain protected information. | -| Threat description |

If the API consumers are not authorized by the API producers, attackers (e.g, malicious xApps) would potentially be able to perform the following types of attacks:

  • - Abuse and/or theft of services or information (data leakage), requesting and successfully obtaining them from the platform, e.g, in order to extract potentially sensitive information from the network and/or UEs
| - -| | | -|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

As a reference, OWASP API Security Top 10 report [i.21] indicates that 'Broken Object Level Authorization' has been the most common and impactful attack on APIs. Even if the application implements a proper infrastructure for authorization checks, developers might forget to use these checks before accessing a sensitive object. Unauthorized access can result in data disclosure to unauthorized parties, data loss, or data manipulation.

In the actual context of Near-RT RIC [i.8], the platform as API producer is responsible to specify those rights/privileges for the platform services as resources to the xApps as consumers. In general, an xApp should only have the required set of permissions to perform the actions for which they are authorized, and no more.

NOTE: The investigation of services for which the API producer is the xApp is for further study

| -| Threat type | Information disclosure, Elevation of Privilege | -| Vulnerabilities | Non-authorized RT RIC APIs | -| Impact type | Confidentiality, Authorization | -| Affected Assets | Data transported over the E2 interface [ASSET-D-09],
Database holding data from xApp applications and E2 Node [ASSET-D-10],
E2 Node data [ASSET-D-11],
Credentials (Administrators) [ASSET-D-20],
3GPP application related data [ASSET-D-21],
Inter- and intra-slice UE priority [ASSET-D-22],
Training or test data and associated labels [ASSET-D-25],
The trained ML model [ASSET-D-26],
Security event log files [ASSET-D-29],
O-RAN specific several UE IDs [ASSET-D-30],
Near-RT-RIC SW [ASSET-C-02],
xApps [ASSET-C-09],
E2 Functions [ASSET-C-41],
Y1 Functions [ASSET-C-43] | - -1 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-NEAR-RT-04A | -| Threat title |

Attackers exploit non authorized Near-RT RIC APIs to access resources and services which they are not entitled to use, to disrupt services.

If the API consumers are not authorized by the API producers, attackers (e.g, malicious xApps) would potentially be able to perform the following types of attacks:

  • - Negatively impacting the network performance due to malicious policies over E2 Nodes
  • - Flooding the platform with resource demanding operations that may lead to a Denial of Service attack
| -| Threat description |

As a reference, OWASP API Security Top 10 report [i.21] indicates that 'Broken Object Level Authorization' has been the most common and impactful attack on APIs. Even if the application implements a proper infrastructure for authorization checks, developers might forget to use these checks before accessing a sensitive object. Unauthorized access can result in data disclosure to unauthorized parties, data loss, or data manipulation.

In the actual context of Near-RT RIC [i.8], the platform as API producer is responsible to specify those rights/privileges for the platform services as resources to the xApps as consumers. In general, an xApp should only have the required set of permissions to perform the actions for which they are authorized, and no more.

NOTE: The investigation of services for which the API producer is the xApp is for further study

| -| Threat type | Denial of Service | -| Vulnerabilities | Non-authorized RT RIC APIs | -| Impact type | Availability | - -| | | -|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Affected Assets | Data transported over the E2 interface [ASSET-D-09],
Database holding data from xApp applications and E2 Node [ASSET-D-10],
E2 Node data [ASSET-D-11],
Credentials (Administrators) [ASSET-D-20],
3GPP application related data [ASSET-D-21],
Inter- and intra-slice UE priority [ASSET-D-22],
Training or test data and associated labels [ASSET-D-25],
The trained ML model [ASSET-D-26],
Security event log files [ASSET-D-29],
O-RAN specific several UE IDs [ASSET-D-30],
Near-RT-RIC SW [ASSET-C-02],
xApps [ASSET-C-09],
E2 Functions [ASSET-C-41],
Y1 Functions [ASSET-C-43] | -|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| - -1 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-NEAR-RT-05 | -| Threat title | Attackers exploit non uniquely identified xApps using a trusted xAppID to access resources and services which they are not entitled to use. | -| Threat description | Not uniquely identifying xApps using a trusted xAppID potentially entails certain threats and potential attacks:
  • - A non-unique xAppID might cause misidentification of an xApp, possibly allowing a potentially malicious xApp to request certain services (theft of services), information (data leakage), or alter existing information
  • - A malicious xApp might use the xAppID assigned to a legitimate xApp to request services or information from Near-RT RIC platform
  • - A non-unique xApp ID could make it impossible to accurately assign actions to the correct xApp
  • - A non-unique xApp ID could make it difficult to recognize that a malicious xApp is in the environment
| -| Threat type | Information disclosure, Elevation of Privilege | -| Vulnerabilities | Not uniquely identifying xApps using a trusted xAppID | -| Impact type | Confidentiality, Authorization | -| Affected Assets | xAppID [ASSET-D-39],
Near-RT-RIC SW [ASSET-C-02],
xApps [ASSET-C-09] | - -2 - -#### 7.4.1.5 Threats against Non-RT RIC - -Threats against Non-RT RIC include: - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-NONRTRIC-01 | -| Threat title | An attacker penetrates the Non-RT RIC to cause a denial of service or degrade the performance | -| Threat description | An attacker penetrates the Non-RT RIC through the SMO and triggers a Denial of Service or degrades the performance of the Non-RT RIC so that the Non-RT RIC cannot ensure:
  • • The monitoring or tracing of the network to understand the effect of the A1 policy on performance in Near-RT RIC
  • • The update of A1 policy
  • • The exposure and secure delivery of A1 Enrichment Information to Near-RT RIC
  • • The setup of access control rules and the selection of which Enrichment Information ID (Eild) are exposed to a Near-RT RIC
| - -| | | -|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat Type | Denial of Service | -| Vulnerabilities | Improper or missing authentication and authorization processes on the Non-RT RIC or SMO | -| Impact Type | Availability | -| Affected Assets | Critical Management-Plane data transported over the O1 interface [ASSET-D-03]
A1 policies that are provided to the Near-RT RIC over the A1 interface [ASSET-D-07]
A1 Enrichment Information that is collected or derived at SMO/Non-RT RIC [ASSET-D-08]
Non-RT RIC Software [ASSET-C-11]
rApps [ASSET-C-10] | - -1 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-NONRTRIC-02 | -| Threat title | UE tracking in the Non-RT RIC | -| Threat description | An attacker gains access to the Non-RT RIC through the SMO for UE tracking. Attacker has access to sensitive data and is able to track a UE. | -| Threat Type | Information Disclosure, Elevation of Privilege | -| Vulnerabilities | Malicious rApps may be used to gain access to UE identification | -| Impact Type | Confidentiality, Authorization | -| Affected Assets | 3GPP application related data such as subscription data, session data, call control related information etc. [ASSET-D-21]
Inter- and intra-slice UE priority [ASSET-D-22]
Non-RT RIC Software [ASSET-C-11] | - -2 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T- NONRTRIC-03 | -| Threat title | Data Corruption/Modification | -| Threat description | An attacker gains access to the Non-RT RIC through the SMO to cause Data Corruption/Modification. A malicious actor who gains unauthorized access to the Non-RT-RIC can modify policy to pass a “False Policy” to the Near-RT-RIC to degrade performance or cause an outage. | -| Threat Type | Tampering, Elevation of Privilege | -| Vulnerabilities | Improper or missing authentication and authorization processes on the Non-RT RIC or SMO | -| Impact Type | Integrity, Authorization | -| Affected Assets | Non-RT RIC Software [ASSET-C-11] | - -3 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-NONRTRIC-04 | -| Threat title | Attacker exploits non-uniquely identified rApp instances to access services and obtain information | -| Threat description | An attacker can exploit non-uniquely identified rApp instances using a trusted rAppID to gain unauthorized access to services and data. Potential threats and attacks include:
  • - A non-unique rAppID might cause misidentification of an rApp instance, possibly allowing a malicious rApp instance to request services (theft of services), information (data leakage)
  • - A malicious rApp instance might use the rAppID assigned to a legitimate rApp instance to
| - -| | | -|------------------------|---------------------------------------------------------------------------| -| Threat Type | request access to R1 services or data
Spoofing, Information Disclosure | -| Vulnerabilities | Not uniquely identifying rApp instances using a trusted rAppID | -| Impact Type | Authenticity, Confidentiality | -| Affected Assets | rApps [ASSET-C-10]
Non-RT RIC Software [ASSET-C-11] | - -1 -2 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-NONRTRIC-05 | -| Threat title | Attacker exploits non-uniquely identified rApp instances, gains access to services resulting in a denial of service to correct rApp instance. | -| Threat description | An attacker can exploit non-uniquely identified rApp instances using a trusted rAppID to gain unauthorized access to services and data. Potential threats and attacks include:
  • - A non-unique rApp ID could make it impossible to accurately assign actions to the correct rApp instance
  • - A non-unique rApp ID could make it difficult to recognize that a malicious rApp instance is in the environment
| -| Threat Type | Elevation of Privilege, Denial of Service | -| Vulnerabilities | Not uniquely identifying rApp instances using a trusted rAppID | -| Impact Type | Authorization, Availability | -| Affected Assets | rApps [ASSET-C-10] | - -3 - -4 - -#### 7.4.1.6 Threats against xApps - -5 - -xApps introduce the following threats: - -![Diagram showing a vulnerable xApp in the Near-RT RIC sending an error message over the E2 interface to an E2 node, resulting in a denial of service or degraded service quality.](c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg) - -``` - -graph LR - subgraph Near-RT_RIC [Near-RT RIC] - xApp[vulnerable xApp] - end - xApp -- "E2 interface" --> Error[Error] - Error --> E2_node[E2 node] - Error -- "Denial of service / degraded service quality" --> E2_node - -``` - -Diagram showing a vulnerable xApp in the Near-RT RIC sending an error message over the E2 interface to an E2 node, resulting in a denial of service or degraded service quality. - -xApps can attack availability - -6 - -7 - -**Figure Threat model-4 : Near-RT-RIC and xApps conflict with E2 node** - -8 - -| | | -|---------------------|------------------------------------------------------------------------------------------------------| -| Threat ID | T-xApp-01 | -| Threat title | An attacker exploits xApps vulnerabilities and misconfiguration to alter data transmitted over A1 or | - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | E2 interfaces. | -| Threat description |

Vulnerabilities can potentially exist in any xApp if it stems from an untrusted or unmaintained source. If attackers can find an exploitable xApp, they can alter data transmitted over A1 or E2 interfaces, potentially disrupting the normal functioning of the Near-RT RIC.

The actual consequences may vary. For example, an attacker may gain the ability to alter data transmitted over A1 or E2 interfaces, extract sensitive information, etc.

Malicious xApps can manipulate the behaviour of the Near-RT RIC, allowing attackers to alter data and impact the performance of the network service.

| -| Threat type | Tampering | -| Vulnerabilities | xApp stems from an untrusted or unmaintained source | -| Impact type | Authenticity | -| Affected Assets | O-CU-CP software [ASSET-C-03], O-eNB [ASSET-C-07], O-Cloud [ASSET-C-08], xApps [ASSET-C-09], rApps [ASSET-C-10] | - -1 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-xApp-01A | -| Threat title | An attacker exploits xApps vulnerabilities and misconfiguration to extract sensitive information. | -| Threat description |

Vulnerabilities can potentially exist in any xApp if it stems from an untrusted or unmaintained source. If attackers can find exploitable xApp, they can extract sensitive information, potentially gaining access to confidential data.

The actual consequences may vary. For example, an attacker may extract sensitive information about network configuration, user data, or other confidential information.

Malicious xApps can be used to extract sensitive information, allowing attackers to gain unauthorized access to sensitive data and potentially compromise the security of the Near-RT RIC.

| -| Threat type | Information Disclosure | -| Vulnerabilities | xApp stems from an untrusted or unmaintained source | -| Impact type | Confidentiality | -| Affected Assets | O-CU-CP software [ASSET-C-03], O-DU software [ASSET-C-05], O-eNB [ASSET-C-07], O-Cloud [ASSET-C-08], xApps [ASSET-C-09], rApps [ASSET-C-10] | - -2 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-xApp-01B | -| Threat title | An attacker exploits xApps vulnerabilities and misconfiguration to disrupt Near-RT RIC functions | -| Threat description |

Vulnerabilities can potentially exist in any xApp if it stems from an untrusted or unmaintained source. If attackers can find exploitable xApp, they can disrupt the normal functioning of the Near-RT RIC, potentially causing a denial of service.

The actual consequences may vary. For example, an attacker may cause performance degradation, service interruptions, or complete unavailability of the Near-RT RIC.

Malicious xApps can be used to impact Near-RT RIC functions, allowing attackers to disrupt the normal functioning of the network service and potentially cause a denial of service.

| -| Threat type | Denial of Service | -| Vulnerabilities | xApp stems from an untrusted or unmaintained source | -| Impact type | Availability | -| Affected Assets | O-CU-CP software [ASSET-C-03], O-DU software [ASSET-C-05], O-eNB [ASSET-C-07], O-Cloud | - -| | | -|---------------|------------------------------------------------------| -| Assets | [ASSET-C-08], xApps [ASSET-C-09], rApps [ASSET-C-10] | -|---------------|------------------------------------------------------| - -1 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-xApp-01C | -| Threat title | An attacker exploits xApps vulnerabilities and misconfiguration to gain unauthorized control over Near-RT RIC | -| Threat description |

Vulnerabilities can potentially exist in any xApp if it stems from an untrusted or unmaintained source. If attackers can find exploitable xApp, they can gain unauthorized control over another xApp or the whole Near-RT RIC, potentially allowing them to perform actions that would normally be restricted.

The actual consequences may vary. For example, an attacker may gain the ability to manipulate the behaviour of a certain cell, a group of UEs, or a specific UE, or even take control of the entire Near-RT RIC.

Malicious xApps can be used to elevate the attacker's privileges, allowing them to perform unauthorized actions and gain control over the Near-RT RIC, potentially leading to a complete compromise of the system.

| -| Threat type | Elevation of Privilege | -| Vulnerabilities | xApp stems from an untrusted or unmaintained source | -| Impact type | Authorization | -| Affected Assets | O-CU-CP software [ASSET-C-03], O-DU software [ASSET-C-05], O-eNB [ASSET-C-07], O-Cloud [ASSET-C-08], xApps [ASSET-C-09], rApps [ASSET-C-10] | - -2 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-xApp-02 | -| Threat title | Conflicting xApps impact O-RAN system functions to degrade performance or create a DoS [i.12] | -| Threat description |

Conflicting xApps impact O-RAN system functions such as mobility management, admission controls, bandwidth management and load balancing for the purpose of performance degradation.

There is no clear functional split between the Near-RT RIC and the O-gNB. The functional split depends on the available xApps and the capabilities exposed by the O-gNB. This creates possible conflicts between the decisions taken by the Near-RT RIC and the O-gNB that could lead to instability in the network, which introduces vulnerabilities that could be exploited by threat actors. For example, a threat actor can utilize a malicious xApp that intentionally triggers RRM decisions conflicting with the O-gNB internal decisions to create denial of service.

| -| Threat type | Denial of Service | -| Vulnerabilities | xApps may be misconfigured or compromised
Failing or misconfigured authentication and authorization in xApp | -| Impact type | Availability | -| Affected Assets | O-CU-CP software [ASSET-C-03], O-DU software [ASSET-C-05], O-eNB [ASSET-C-07], O-Cloud [ASSET-C-08], xApps [ASSET-C-09], rApps [ASSET-C-10] | - -3 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-xApp-03 | -| Threat title | An attacker compromises xApp isolation to tamper with the underlying system. | -| Threat description | An attacker can exploit weaknesses and vulnerabilities to compromise xApp isolation and to break out of xApp confinement. For example, an attacker can use underlying system vulnerabilities to easily breach isolation and confinement, allowing them to tamper with the underlying system and potentially modify or manipulate the behavior of other xApps or O-RAN architecture elements. | - -| | | -|------------------------|-----------------------------------------------------------------------------| -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in the underlying system hosting xApps | -| Impact type | Authenticity | -| Affected Assets | Near-RT RIC software [ASSET-C-02], O-Cloud [ASSET-C-08], xApps [ASSET-C-09] | - -1 -2 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-xApp-03A | -| Threat title | An attacker compromises xApp isolation to extract sensitive information from co-hosted xApps or the Near-RT RIC. | -| Threat description | An attacker can exploit weaknesses and vulnerabilities in the O-Cloud isolation controls to compromise xApp isolation and break out of xApp confinement. For example, an adversary can use side effects resulting from shared resource usage to deduce information from co-hosted xApps. | -| Threat type | Information Disclosure | -| Vulnerabilities | Vulnerabilities in the underlying system hosting xApps | -| Impact type | Confidentiality | -| Affected Assets | Near-RT RIC software [ASSET-C-02], xApps [ASSET-C-09] | - -3 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-xApp-03B | -| Threat title | An attacker compromises xApp isolation to degrade services. | -| Threat description | An attacker can exploit weaknesses and vulnerabilities to compromise xApp isolation and break out of xApp confinement. For example, an attacker can use the gained access to degrade services (DoS). | -| Threat type | Denial of Service | -| Vulnerabilities | Vulnerabilities in the underlying system hosting xApps | -| Impact type | Availability | -| Affected Assets | Near-RT RIC software [ASSET-C-02], O-Cloud [ASSET-C-08], xApps [ASSET-C-09] | - -4 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-xApp-03C | -| Threat title | An attacker compromises xApp isolation to gain elevated privileges. | -| Threat description | An attacker can exploit weaknesses and vulnerabilities to compromise xApp isolation and break out of xApp confinement. For example, gaining unauthorized access to the underlying system provides new opportunities to exploit vulnerabilities in other xApps or O-RAN architecture elements, potentially allowing the attacker to gain elevated privileges. | -| Threat type | Elevation of Privilege | -| Vulnerabilities | Vulnerabilities in the underlying system hosting xApps | -| Impact type | Authorization | -| Affected Assets | Near-RT RIC software [ASSET-C-02], O-Cloud [ASSET-C-08], xApps [ASSET-C-09] | - -1 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-xApp-04 | -| Threat title | False or malicious A1 policies from the Non-RT RIC modify behaviour of xApps | -| Threat description |

Unauthorized access to the Non-RT RIC enables the creation of 'false policies' that can be issued to the Near-RT RIC for enforcement. Existing Near-RT RIC policies could also be modified to create a false policy. False policies passed to the Near-RT RIC would be persistent until they were modified or deleted by the Non-RT RIC or the Near-RT RIC power cycles.

False policies can be created to have numerous impacts to the normal performance of the RAN. A single false A1 policy can target a specific UE, groups of UEs, or an entire cell.

The Near-RT RIC is capable of steering traffic to achieve optimal QoS or QoE performance. A false policy can cause the Near-RT RIC to improperly steer user data to facilitate a cyber-attack.

| -| Threat type | Tampering | -| Vulnerabilities | xApp functionality exploited by malicious A1 policies | -| Impact type | Authenticity | -| Affected Assets | A1 policies [ASSET-D-07], E2 Node data [ASSET-D-11], xApps [ASSET-C-09] | - -2 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-xApp-05 | -| Threat title | False or malicious A1 policies from the Non-RT RIC modify behaviour of xApps to trigger a DoS. | -| Threat description |

Unauthorized access to the Non-RT RIC enables the creation of 'false policies' that can be issued to the Near-RT RIC for enforcement. Existing Near-RT RIC policies could also be modified to create a false policy. False policies passed to the Near-RT RIC would be persistent until they were modified or deleted by the Non-RT RIC or the Near-RT RIC power cycles.

False policies can have many impacts on the normal performance of the RAN. For example, a single false A1 policy can target a specific UE, groups of UEs, or an entire cell.

The Near-RT RIC is capable of steering traffic to achieve optimal QoS or QoE performance. A false policy can cause the Near-RT RIC to improperly steer user data to facilitate a cyber-attack.

| -| Threat type | Denial of Service | -| Vulnerabilities | xApp functionality exploited by malicious A1 policies | -| Impact type | Availability | -| Affected Assets | A1 policies [ASSET-D-07], E2 Node data [ASSET-D-11], xApps [ASSET-C-09] | - -3 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-xApp-06 | -| Threat title | False or malicious A1 policies from the Non-RT RIC modify behaviour of xApps to locate a subscriber. | -| Threat description |

Unauthorized access to the Non-RT RIC enables the creation of 'false policies' that can be issued to the Near-RT RIC for enforcement. Existing Near-RT RIC policies could also be modified to create a false policy. False policies passed to the Near-RT RIC would be persistent until they were modified or deleted by the Non-RT RIC or the Near-RT RIC power cycles.

False policies could also be used for the purpose of locating a subscriber or group of subscribers. In this case, the false policy would cause the Near-RT RIC to isolate a subscriber in the O-CU. The Near-RT RIC could also use MIMO beamforming in the O-DU and O-RU to isolate a user onto a single beam. The data feedback from the RAN can include UE location or trajectory information from GPS data. The subscriber location would be attained from access to the Non-RT RIC in the

| - -| | | -|------------------------|-------------------------------------------------------------------------| -| | SMO function. | -| Threat type | Information Disclosure | -| Vulnerabilities | xApp functionality exploited by malicious A1 policies | -| Impact type | Confidentiality | -| Affected Assets | A1 policies [ASSET-D-07], E2 Node data [ASSET-D-11], xApps [ASSET-C-09] | - -#### 7.4.1.7 Threats against rApps - -Threats against rApps include: - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-rAPP-01 | -| Threat title | Conflicting rApps unintentionally or maliciously impact O-RAN system functions to degrade performance or trigger a DoS | -| Threat description |

rApps in the Non-RT RIC can be provided by different vendors. For example, one vendor can provide the rApp for Carrier license scheduling and another vendor provide the rApp for energy saving, etc.

This creates the risk that different rApps will take conflicting decisions at the same instance in time for the same user. Such conflicts between rApps include:

  • • Direct conflicts: different rApps request change for the same parameter.
  • • Indirect conflicts: different rApps request change to different parameters that will create opposite effects.
  • • Implicit conflicts: different rApps request change to different parameters that are not creating any obvious opposite effect but result in an overall network performance degradation, instabilities, etc.

These conflicts are difficult to mitigate since dependencies are impossible to observe.

| - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-rAPP-02 | -| Threat title | An attacker exploits rApp vulnerabilities | -| Threat description |

Vulnerabilities can potentially exist in any rApp. If attackers can find exploitable rApp, they can potentially force a data breach, disrupt the offered network service. and take over another rApp or the non-RT RIC.

The actual consequences may vary. For example, an attacker may gain the ability to alter data transmitted over A1 interface, extract sensitive information, etc.

| - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-rAPP-03 | -| Threat title | An attacker exploits rApps misconfiguration | -| Threat description |

Security misconfiguration, such as open ports or enabled unused protocols, can potentially exist in an rApp. If attackers can find exploitable rApp, they can disrupt the offered network service and potentially take over another rApp or the whole non-RT RIC.

The actual consequences may vary. For example, an attacker may gain the ability to alter data transmitted over A1 interface, extract sensitive information, etc.

| - -| | | -|------------------|------------------| -| Threat ID | T-rAPP-04 | -|------------------|------------------| - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat title | An attacker bypasses authentication and authorization | -| Threat description | An Attacker can exploit an rApp that has weak or misconfigured authentication and authorization to gain access to the rApp and pose as a tenant. | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-rAPP-05 | -| Threat title | An attacker deploys and exploits malicious rApp | -| Threat description |

An untrusted source may intentionally provide a malicious rApp. A trusted source may have a backdoor intentionally inserted in the rApp. If attackers can find exploitable rApp, they can disrupt the offered network service and potentially take over another rApp or the whole non-RT RIC.

Malicious rApps could impact non-RT RIC functions such as AI/ML model training, A1 policy management, Enrichment information management, Network Configuration Optimization in the purpose of performance degradation, DoS, enrichment data sniffing (UE location, trajectory, navigation information, GPS data, etc.), etc.

| - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-rAPP-06 | -| Threat title | An attacker bypasses authentication and authorization using an injection attack | -| Threat description | It is possible that an attacker to submit requests without prior authentication and authorization by executing an injection attack to manipulate configurations, access logs, perform remote code execution, etc. | - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------| -| Threat ID | T-rAPP-07 | -| Threat title | rApp exploits services | -| Threat description | A malicious rApp or a trusted but compromised rApp can exploit services across the R1 interface | - -#### 7.4.1.8 Threats against PNF - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-PNF-01 | -| Threat title | An attacker compromises a PNF to launch attacks against VNFs/CNFs | -| Threat description |

A lack of security policies to protect mixed PNF-VNF/CNF deployments could be used to perform attacks against VNFs/CNFs, potentially taking advantage of legacy security used by PNFs and not provided by the virtualization/containerization layer.

Attackers could use insecure interfaces as injection points and for launching the attacks.

Attackers could leverage lack of authentication, integrity check mechanisms to tamper software updates to PNFs.

| -| Threat Type | Information Disclosure, Tampering | -| Vulnerabilities | Vulnerabilities in a PNF deployed in a PNF-VNF/CNF deployments. | -| Impact Type | Confidentiality, Integrity | -| Affected Assets | All | - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-PNF-01A | -| Threat title | An attacker compromises a PNF to launch Denial of Service attacks against VNFs/CNFs | -| Threat description | A lack of security policies to protect mixed PNF-VNF/CNF deployments could be used to perform attacks against VNFs/CNFs, potentially taking advantage of legacy security used by PNFs and not provided by the virtualization/containerization layer. The attacks on VNF/CNF could lead to denial of service of the VNF/CNF services and function to its dependent functions/elements. | -| Threat Type | Denial of Service | -| Vulnerabilities | Vulnerabilities in a PNF deployed in a PNF-VNF/CNF deployments. | -| Impact Type | Availability | -| Affected Assets | All | - -#### **7.4.1.9 Threats against R1 interface** - -The R1 interface facilitates inter-connection between rApps and Non-RT RIC framework supplied by different vendors, and provides a level of abstraction between rApps and Non-RT RIC framework/SMO that can be the consumers and or producers of R1 services. - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-R1-01 | -| Threat title | An attacker gains unauthorized access to R1 services | -| Threat description | “Service management and exposure services Producer” determines whether the Service Producer is authorized to produce the service. An attacker can perform a spoofing attack to gain unauthorized access to R1 services. | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-R1-02 | -| Threat title | Attacker modifies Service Heartbeat message to cause Denial of Service | -| Threat description | Attacker can exploit the Service Heartbeat on the R1 by modifying or inserting heartbeat messages to cause denial of service | - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-R1-03 | -| Threat title | Malicious actor bypasses authentication to Request Data | -| Threat description | Attacker can exploit password-based authentication on the R1 to request unauthorized data. Weak password management can easily be exploited. (Certificate-based mutual authentication using TLS and PKI X.509 certificates is recommended). | - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-R1-04 | -| Threat title | An attacker bypasses authorization to discover data | -| Threat description | “Data registration and discovery service producer” determines whether the Data Producer is authorized to produce the data types. An attacker can perform a spoofing attack to bypass authorization to discover available data. | - -| | | -|------------------|----------------| -| Threat ID | T-R1-05 | -|------------------|----------------| - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat title | An attacker gains unauthorized access to data | -| Threat description | An attacker can perform a spoofing attack to exploit the Data request and subscription service for the purpose to gain unauthorized access to data. | - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-R1-06 | -| Threat title | An attacker modifies a Data Request | -| Threat description | Data Consumers consume the “Data request and subscription service” to request data instances or subscribe to them. An attacker can modify a request to force the consumer to receive a different data set then that intended. Without checks, the received data could be processed, leading to erroneous decisions or triggers. | - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-R1-07 | -| Threat title | A malicious actor snoops Data Delivery to the Data Consumer | -| Threat description |

Data delivery messages relate to a particular data request or subscription. The data can be delivered to the Data Consumer in different ways, including:

  • • as part of the payload of a data delivery message,
  • • as a data stream,
  • • from e.g., a REST endpoint, a message bus or object store location.

An attacker can perform snooping, injection, or modification attacks in the Delivery of Data process.

| - -#### 7.4.1.10 Threats against A1 interface - -The A1 interface enables the Non-RT RIC function to provide policy-based guidance, ML model management and enrichment information to the Near-RT RIC function for RAN optimization. The Non-RT RIC can provide enrichment information over the A1 interface to support the policy enforcement in the Near-RT RIC. The A1 interface is used for discovery, request and delivery of A1 Enrichment Information and discovery of External Enrichment Information. - -![Diagram showing the A1 interface between Non-RT RIC and Near-RT RIC.](ad555483986d7170a46ce72d164b5bc8_img.jpg) - -``` - -graph TD - NonRT[Non-RT-RIC] <-->|A1| NearRT[Near-RT-RIC] - -``` - -Diagram showing the A1 interface between Non-RT RIC and Near-RT RIC. - -Figure Threat model-5 : A1 interface between the Non-RT RIC and the Near-RT RIC - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-A1-01 | -| Threat title | Untrusted peering between Non-RT-RIC and Near-RT-RIC | -| Threat description | Malicious Non-RT-RIC peers with a Near-RT-RIC over the A1 interface, or a malicious Near-RT-RIC peers with a Non-RT-RIC over the A1 interface, due to weak mutual authentication. | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-A1-02 | -| Threat title | Malicious function or application monitors messaging across A1 interface | -| Threat description | Internal threat actor can gain access to the messaging across the A1 interface for a MiTM attack to read policy. | - -1 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-A1-03 | -| Threat title | Malicious function or application modifies messaging across A1 interface | -| Threat description | Internal threat actor can gain access to the messaging across the A1 interface for a MiTM attack to modify or inject policy. This can result in the Near-RT RIC receiving malicious policy. | - -2 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-A1-04 | -| Threat title | Unauthorized access to Non-RT-RIC- or Near-RT-RIC- resources | -| Threat description | A malicious actor accesses Near-RT-RIC resources or Non-RT-RIC resources over the A1 interface, due to weak service consumer authorization. | -| Threat type | Elevation of Privilege | -| Impact type | Authorization | -| Affected Asset | A1 policies [ASSET-D-07], A1 Enrichment Information [ASSET-D-08] | - -3 - -#### 7.4.1.11 Threats against application life cycle - -4 - -5 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AppLCM-01 | -| Threat title | Compromise of App/VNF/CNF update package integrity prior to onboarding | -| Threat description | Attackers gains access to the SMO to modify the App/VNF/CNF update package to enable a malicious application. | -| Threat type | Tampering | -| Vulnerabilities | Lack of integrity verification | -| Impact type | Integrity; Availability | -| Affected Assets | App/VNF/CNF software package [ASSET-D-15] | - -6 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AppLCM-02 | -| Threat title | Compromise of App/VNF/CNF update image integrity during instantiation | -| Threat description | Attacker gains access to the O-Cloud platform to modify the App/VNF/CNF update image to enable a malicious application. | -| Threat type | Tampering | -| Vulnerabilities | Lack of integrity verification | -| Impact type | Integrity; Availability | -| Affected | App/VNF/CNF software package [ASSET-D-15] | - -| | | -|---------------|--| -| Assets | | -|---------------|--| - -1 -2 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AppLCM-03 | -| Threat title | Downgrade attack to vulnerable application version | -| Threat description |

A software version downgrade attack is a form of attack on a system that makes it abandon a more recent version of a software package in favor of an older, possibly vulnerable, version.

Malicious actor downgrades an application to enable exploitation of application vulnerabilities.

| -| Threat type | Tampering | -| Vulnerabilities | Lack of integrity verification | -| Impact type | Availability; Integrity | -| Affected Assets | App/VNF/CNF software package [ASSET-D-15] | - -3 -4 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AppLCM-04 | -| Threat title | Attacker exploits missing or improperly defined elements of application's SecurityDescriptor | -| Threat description |

Proper and comprehensive definition of the App/VNF/CNF package SecurityDescriptor helps ensure elements of security needed for the App/VNF/CNF package are present. If attackers can find missing or improperly defined elements of an App/VNF/CNF package SecurityDescriptor, they can exploit that to gain unauthorized access to data and services.

| -| Threat type | Elevation of Privilege | -| Vulnerabilities | Misconfiguration | -| Impact type | Authorization; Availability | -| Affected Assets | App/VNF/CNF software package [ASSET-D-15] | - -5 -6 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AppLCM-05 | -| Threat title | Malicious actor modifies application's SecurityDescriptor to gain unauthorized access | -| Threat description |

Malicious actor modifies fields of an App/VNF/CNF package SecurityDescriptor to change security elements of the App/VNF/CNF, which could include information on encryption, algorithms, key requirements, firewall rules, etc. An attacker can modify the SecurityDescriptor to gain unauthorized access to data and services and potentially allow the attacker to gain elevated privileges.

| -| Threat type | Tampering; Elevation of Privilege | -| Vulnerabilities | Lack of authentication, lack of integrity verification | -| Impact type | Integrity; Authorization | -| Affected Assets | App/VNF/CNF software package [ASSET-D-15] | - -7 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AppLCM-05A | -| Threat title | Malicious actor modifies application's SecurityDescriptor to degrade services | -| Threat description |

Malicious actor modifies fields of an App/VNF/CNF package SecurityDescriptor to change security elements of the App/VNF/CNF, which could include information on encryption, algorithms, key

| - -| | | -|------------------------|---------------------------------------------------------------------------------------------------------------| -| | requirements, firewall rules, etc. An attacker can modify the SecurityDescriptor to cause service disruption. | -| Threat type | Tampering; Denial of Service | -| Vulnerabilities | Lack of authentication, lack of integrity verification | -| Impact type | Integrity; Availability | -| Affected Assets | App/VNF/CNF software package [ASSET-D-15] | - -1 -2 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AppLCM-06 | -| Threat title | Improper decommissioning of application | -| Threat description | The improper decommissioning of an application can lead to excessive or conflicting resource usage, accidental deletion of pertinent data (such as application data, cryptographic keys, etc.), and misallocation of resources to a malicious application. Credentials or other trust relationships may not be revoked or removed, which leaves an exposure. | -| Threat type | Denial of Service, Information Disclosure | -| Vulnerabilities | Misconfiguration, improper release of resources and secrets | -| Impact type | Availability, Confidentiality | -| Affected Assets | Near-RT RIC software [ASSET-C-02], Non-RT RIC software [ASSET-C-11], xApps [ASSET-C-09], rApps [ASSET-C-10], O-CU-CP software [ASSET-C-03], O-CU-UP software [ASSET-C-04], O-DU software [ASSET-C-05] | - -3 -4 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AppLCM-07 | -| Threat title | Improper deletion of application sensitive data | -| Threat description | Adversary can gain access to sensitive data and secrets if an application's data is not securely deleted. This can include access to secure artifacts such as certificates and keys. | -| Threat type | Information Disclosure | -| Vulnerabilities | Missing or weak confidentiality protection | -| Impact type | Confidentiality | -| Affected Assets | X.509 certificates [ASSET-D-16], Private keys [ASSET-D-17], Cryptographic keys used during secure boot [ASSET-D-32] | - -5 -6 - -###### 7 **7.4.1.12 Threats against E2 interface** - -8 E2 is a logical interface connecting the Near-RT RIC with an E2 Node as defined in [i.25]. The E2 functions are -9 grouped into the following categories: - -- 10 • Near-RT RIC Services -- 11 • Near-RT RIC support functions -- 12 -- 13 - -| | | -|---------------------|---------------------------------------| -| Threat ID | T-E2-01 | -| Threat title | Untrusted Near-RT-RIC and/or E2 Nodes | - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat description | A malicious E2 Node communicates with a Near-RT RIC over the E2 interface, or a malicious Near-RT RIC communicates with an E2 Node over the E2 interface, due to weak mutual authentication. | -| Threat Type | Spoofing | -| Vulnerabilities | Weak mutual authentication | -| Impact Type | Authenticity | -| Affected Assets | E2 interface, including protocol stack [ASSET-C-40] | - -1 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------| -| Threat ID | T-E2-02 | -| Threat title | Malicious actor monitors messaging across E2 interface | -| Threat description | Threat actor can gain access to the messaging across the E2 interface for a MiTM attack to read messages. | -| Threat Type | Information disclosure | -| Vulnerabilities | Missing or weak confidentiality protection | -| Impact Type | Confidentiality | -| Affected Assets | E2 interface, including protocol stack [ASSET-C-40] | - -2 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-E2-03 | -| Threat title | Malicious actor modifies messaging across E2 interface | -| Threat description | Threat actor can gain access to the messaging across the E2 interface for a MiTM attack to modify or inject messages. This can result in the Near-RT RIC and/or the E2 Nodes receiving malicious messages. | -| Threat Type | Tampering | -| Vulnerabilities | Lack of integrity verification | -| Impact Type | Integrity | -| Affected Assets | E2 interface, including protocol stack [ASSET-C-40] | - -3 - -#### 7.4.1.13 Threats against Y1 interface - -The Near-RT RIC provides RAN analytics information (RAI) services via Y1 service interface. These services can be consumed by Y1 consumers by subscribing to or requesting the RAN analytics information via the Y1 service interface. Y1 consumers may be Application Functions (AFs) which are within an O-RAN trusted domain. AFs outside the O-RAN trusted domain may use Y1 services, too. Further details are available in the O-RAN Architecture Description [i.6], clauses 5.1 and 5.4.18. - -10 - -![O-RAN ALLIANCE Logo](8b9c4846ed8399faf767a527db889f35_img.jpg) - -O-RAN.WG11.TR.Threat-Modeling-R005-v08.00 - -![Figure Threat model-6 : RAN analytics information (RAI) services via Y1 service interface](2865fd60541ac34a704bc9e7af1041f7_img.jpg) - -``` - -graph TD - Y1C[Y1 Consumers] -- "Y1 API(s)" --> Y1T[Y1T] - subgraph Near-RT RIC - Y1T -- "RAI API(s)" --> RAI[RAI producer xApp] - end - -``` - -**Figure Threat model-6 : RAN analytics information (RAI) services via Y1 service interface** - -Figure Threat model-6 : RAN analytics information (RAI) services via Y1 service interface - -Malicious Y1 consumers may use their access through the Y1 interface with the intent of accessing, manipulating or negatively impacting the privacy of subscribers, the RAN or the core network. - -| Threat ID | T-Y1-01 | -|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat title | Untrusted Near-RT-RIC and Y1 consumers | -| Threat description | A Malicious Y1 consumer communicates with a Near-RT-RIC over the Y1 interface, or a malicious Near-RT-RIC communicates with a Y1 consumer over the Y1 interface, due to weak mutual authentication. | -| Threat Type | Spoofing | -| Vulnerabilities | Weak mutual authentication | -| Impact Type | Authenticity | -| Affected Assets | Y1 interface, including protocol stack [ASSET-C-42] | - -| Threat ID | T-Y1-02 | -|--------------------|-----------------------------------------------------------------------------------------------------------| -| Threat title | Malicious actor monitors messaging across Y1 interface | -| Threat description | Threat actor can gain access to the messaging across the Y1 interface for a MiTM attack to read messages. | -| Threat Type | Information disclosure | -| Vulnerabilities | Missing or weak confidentiality protection | -| Impact Type | Confidentiality | -| Affected Assets | Y1 interface, including protocol stack [ASSET-C-42] | - -| Threat ID | T-Y1-03 | -|--------------|---------------------------------------------------------------------------------------------------| -| Threat title | Malicious actor modifies messaging across Y1 interface | -| Threat | Threat actor can gain access to the messaging across the Y1 interface for a MiTM attack to modify | - -© 2026 by the O-RAN ALLIANCE e.V. Your use is subject to the copyright statement on the cover page of this specification. 66 - -| | | -|------------------------|--------------------------------------------------------------------------------------------------------------| -| description | or inject messages. This can result in the Near-RT RIC and/or the Y1 consumers receiving malicious messages. | -| Threat Type | Tampering | -| Vulnerabilities | Lack of integrity verification | -| Impact Type | Integrity | -| Affected Assets | Y1 interface, including protocol stack [ASSET-C-42] | - -### 7.4.2 Threats against O-CLOUD - -Virtualization and containerization technologies in O-RAN introduce the following relevant threats: - -#### 7.4.2.1 Generic Threats - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-GEN-01A | -| Threat title | Software flaw attack enables unauthorized access and privilege escalation | -| Threat description |

Code of host OS, Hypervisor/Container Engine and VNF/CNF can include flaws that an attacker can exploit.

O-RAN software components rely on opensource software, opensource libraries, 3rd party components. Vulnerability in any of these software components likely to allow attacker to exploit O-CLOUD environment. This could lead attacker to carry out to malicious activities, such as:

  • • Compromise of the underlying VM/Container
  • • Exploit host access via Escape to Host
  • • Take advantage of weak identity and access management policies to attempt to elevate privileges

These actions can lead to impersonation of legitimate components or users, and escalation of control beyond intended privileges.

| -| Threat type | Spoofing, Elevation of Privilege | -| Vulnerabilities |

Use of software with known vulnerabilities

Weak isolation mechanisms between containers/VMs

Unverified software packages or lack of code signing

Inadequate security hardening

| -| Impact type | Authenticity, Authorization | -| Affected Asset | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-GEN-01B | -| Threat title | Software flaw attack enables tampering and information disclosure | -| Threat description |

Code of host OS, Hypervisor/Container Engine and VNF/CNF can include flaws that an attacker can exploit.

O-RAN software components rely on opensource software, opensource libraries, 3rd party components. Vulnerability in any of these software components likely to allow attacker to exploit O-CLOUD environment. This could lead attacker to carry out to malicious activities, such as:

  • • Execute adversary-controlled code
  • • Tamper with system data and software components
| - -| | | -|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |
  • Intercept sensitive information within virtualized environments
  • Move from virtual environments to the host to compromise confidentiality and integrity

Such exploitation can lead to unauthorized code modification and information exposure within the O-Cloud infrastructure.

| -| Threat type | Tampering, Information Disclosure | -| Vulnerabilities |

Use of software with known vulnerabilities

Weak isolation mechanisms between containers/VMs

Unverified software packages or lack of code signing

Inadequate security hardening

| -| Impact type | Integrity, Confidentiality | -| Affected Asset | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | - -1 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-GEN-02A | -| Threat title | Unauthorized use of valid credentials to access O-Cloud services | -| Threat description |

Adversaries may obtain and abuse credentials of existing accounts as a means of gaining unauthorized access. This can occur through credential phishing, pharming, or by stealing credentials after compromising the network. Compromised credentials may be used to bypass access controls placed on various resources on O-Cloud.

Compromised credentials may also grant an adversary increased privilege to specific O-Cloud services or access to restricted areas of the O-Cloud network.

| -| Threat type | Spoofing, Elevation of Privilege | -| Vulnerabilities |

Weak or improperly managed credentials

Lack of multifactor authentication

Inadequate account activity monitoring

Insecure credential storage

| -| Impact type | Authenticity, Authorization | -| Affected Asset | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | - -2 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-GEN-02B | -| Threat title | Tampering and data exposure via malicious use of exposed or unauthenticated services | -| Threat description |

Attackers may abuse exposed services that are accessible without proper authentication or authorization. In O-Cloud environments, this includes unauthenticated access to services like Docker API, Kubernetes API server, kubelet, or web dashboards. Using these access points, attackers can tamper with configurations, modify workloads, or extract sensitive information stored or processed in the environment.

| -| Threat type | Tampering, Information Disclosure | -| Vulnerabilities |

Unauthenticated access to exposed APIs

Poor segmentation or network exposure of internal services

| -| Impact type | Integrity, Confidentiality | -| Affected Asset | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | - -1 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-GEN-03 | -| Threat title | Untrust binding between the different O-Cloud layers | -| Threat description |

One major challenge in virtualized architectures and especially in O-Cloud is to prove that a particular VM/Container runs on top of a specific Hypervisor/Container Engine. More specifically, it is necessary to assure that a trusted VM/Container is executed on a particular trusted Hypervisor/Container Engine, whereas the Hypervisor/Container Engine's trust state relies on an attestation that considers the entire corresponding hard and software stack. More precisely, this includes all hardware chips, firmware, OS and Hypervisor/Container Engine components that are relevant for the Hypervisor/Container Engine's trust state determination.

If it is not possible to establish a correlation between VM/Container and Hypervisor/Container Engine, an attacker is able to make use of a trusted VM/Container that runs on top of an untrusted Hypervisor/Container Engine and it would be impossible to detect any interference made by the malicious Hypervisor/Container Engine, e.g. intercepting communication, replacing strong or using weak cryptographic keys, etc. Similarly, trustworthiness in the service-layer might only be established if there is a mechanism to determine that only trusted VNFs/CNFs, w.r.t trusted VM/Container's, are running on specific trusted Hypervisors/Container Engines that are part of the service-provisioning-chain.

| -| Threat type | Tampering, Information disclosure | -| Vulnerabilities |

Absence of hardware root of trust or secure boot enforcement across the software stack

Unverified or unauthenticated deployment of virtualized components

| -| Impact type | Integrity, Confidentiality | -| Affected Asset | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | - -2 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-GEN-04 | -| Threat title | Lack of Authentication & Authorization in interfaces between O-Cloud components | -| Threat description |

O-Cloud deploys CNF applications as containers in a cluster of physical nodes which may be spanned across geographical locations. Owing to the Service Based Architecture of CNFs, this introduces several service endpoints communicating across each other over the network (container to container, container to cloud infrastructure component) and it is fairly difficult to distinguish between a service terminating an external interface and a service exposing only an internal interface.

Multi-tenant deployments and deployments in public cloud also require the CNF applications to run alongside unknown entities. In such deployment scenarios, CNF service endpoints with no authentication/weak authentication expose risk of attack that can impact the availability of service and the CNF.

Lack of proper authentication in interfaces exposed by CNF services, introduces threats of lateral movement where a compromised container/rogue container

  • can compromise the availability of internal service by bringing down the internal service and perform lateral movement of attack by exploiting the availability of other such services
  • can compromise the confidentiality of the internal service by extracting critical application data
| -| Threat type | Information disclosure, Denial of Service | -| Vulnerabilities |

Missing or weak authentication mechanisms

No access control enforcement between tenants

| -| Impact type | Availability, Confidentiality | -| Affected Asset | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | - -1 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-GEN-05 | -| Threat title | Exposure and misuse of unsecured credentials and keys | -| Threat description |

Adversaries may search compromised O-RAN NFs, VL, orchestration layer or hardware to find and obtain insecurely stored credentials. These credentials can be stored and/or misplaced in many locations on the O-cloud platform, including plaintext files (e.g. Bash History), operating system or application-specific repositories (e.g. Credentials in Registry), or other specialized files/artifacts (e.g. Private Keys) [I.22].

Bash History: Adversaries may search the bash command history on compromised systems for insecurely stored credentials.

Credentials in registry: Adversaries may search the Registry on compromised systems for insecurely stored credentials.

Private Keys: Adversaries may search for private key certificate files on compromised systems for insecurely stored credentials. Private cryptographic keys and certificates are used for authentication, encryption/decryption, and digital signatures; Common key and certificate file extensions include: .key, .pgp, .gpg, .ppk, .p12, .pem, .pfx, .cer, .p7b, .asc.

Tools exist to automate the discovery of such credentials, allowing adversaries to extract sensitive authentication material and access confidential data stored or processed in the O-RAN environment.

| -| Threat type | Information disclosure, and Elevation of privilege | -| Vulnerabilities | Insecure storage of credentials and private keys
Lack of access control | -| Impact type | Confidentiality, Authorization | -| Affected Asset | Private keys and credentials | - -2 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-GEN-06 | -| Threat title | Sensitive application data cache exploitation | -| Threat description |

Most of the applications use data that is sensitive in nature which needs to be secured. And it is common for these applications to cache such sensitive data, after retrieving the data from a secure storage. This caching occurs in various forms: within application memory, in persistent file systems, or in ephemeral file systems (For example, non-persistent container file system).

For a VNF, the application can cache the sensitive data in its memory which is non-persistent (erased when the application ceases to exist) or in the persistent virtual machine file system.

For a CNF, the application can store the sensitive data in its memory which is non-persistent (erased when the application/microservice ceases to exist) or in the non-persistent container file system, or in the persistent host file system, provided the application has the necessary privileges to access host file system.

The sensitive data components that are cached by applications could be of different types which are used as authentication keys, session keys, passwords, tokens, etc.

The storage of sensitive data in the application cache is used to improve performance of the applications and keeping the sensitive information readily available to the applications for faster initialization, re-initialization or recovery.

An example of faster recovery/re-initialization is a scenario where a TLS client establishes a TLS session with a server and stores the client certificate and corresponding private key in the application cache. If the TLS session is terminated unexpectedly (For example, due to network error conditions), the TLS client uses the cached client certificates and private key for recovering / re-establishing the TLS session, instead of retrieving the information from a more

| - -| | | -|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

secure, but slower, storage solution.

While leveraging application cache is indispensable for significant performance gains, it also presents a notable security risk [i.28], [i.29]. The sensitive data stored in application cache would be a primary target from attackers/threat actors [i.30], who can exploit this information to penetrate deeper into O-RAN network functions.

To counter this threat, a “Defense in depth” approach is essential. This approach encompasses multiple security layers designed to mitigate risks associated with application caches, focusing on strong encryption, strict access management and anomaly detection to protect sensitive data effectively.

| -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Lack of encryption for cached authentication/session data
Insecure storage of cached data in ephemeral or persistent storage without secure deletion | -| Impact type | Integrity, Confidentiality | -| Affected Asset | Certificates, private keys, credentials and other application specific sensitive data | - -#### 7.4.2.2 Threats concerning VMs/Containers - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VM-C-01 | -| Threat title | Abuse of a privileged VM/Container | -| Threat description |

It’s possible to run VMs/Containers with unintended configurations. Such misconfigurations can help the adversaries to compromise even strongest of VM/Container isolation measures.

Such misconfigurations scenarios include:

  • • A VMs/Containers can be configured to have more privileges than what is actually required (e.g. settings that give it unnecessary, and perhaps unplanned, privileges). For example, an attacker with access to such a container, can use it to gain higher privileges on host, perform un-authorized operations and get to anything that the host, or any of the containers running on that host, can reach.
  • • A VMs/Containers have unintended read/write access to a directory on host filesystem. This could allow an attacker to perform unauthorized modifications to the contents, create symbolic links to any directories or files not directly exposed by the hostPath, install SSH keys, read secrets mounted to the host, and take other malicious actions.
| -| Threat type | Spoofing, Tampering, Information disclosure, Denial of Service and Elevation of privilege | -| Impact type | Authenticity, Integrity, Confidentiality, Availability and Authorization | -| Affected Asset | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VM-C-02 | -| Threat title | VM/Container escape attack | -| Threat description |

VNF/CNF deployed on the same physical machine as tenants share the same host kernel and host OS resources. Lack of strong isolation between the VMs/Containers and the host allows for a potential risk of a rogue VM/Container escaping the VM/Container confinement and impacting other co-hosted VMs/Containers. In others, an attacker may deploy a new malicious VM/Container configured without network rules, user limitations, etc. to bypass existing defenses within O-Cloud infrastructure.

Attacker deploys malicious VM/Container to escapes the host (Hypervisor/Container Engine/Host OS) and reaches the server’s hardware, then the malicious VM/Container can gain root access to the whole server where it resides. This gives the malicious VM/Container full control on all the VMs/Containers hosted on the same hacked server. This could allow an attacker to undermine the confidentiality, integrity and/or availability of VNFs/CNFs resources.

| - -| | | -|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

Containers can be deployed by various means, such as via Docker's create and start APIs or via a web application such as the Kubernetes dashboard or Kubeflow. Adversaries may deploy containers based on retrieved or built malicious images or from benign images that download and execute malicious payloads at runtime.

When a malicious VM/Container escapes isolation, it can gain full control over the underlying host and cause any of the below serious threats:

  • • Attacker would gain the ability to mount attacks on the host or compromise the host functionalities
  • • Compromise the confidentiality & integrity of co-hosted VMs/Containers and tenants
  • • Launch DDOS attacks on co-hosted VMs/Containers and host services thereby degrading their performance
  • • Introduce new vulnerabilities in host to be used for future attacks
  • • Lack of network segmentation could potentially expose other VMs/Containers in the environment to attack. An example of this could be reconnaissance, exploitation and subsequent lateral movement to another host within the cluster.
| -| Threat type | Spoofing, Tampering, Information disclosure, Denial of Service and Elevation of privilege | -| Impact type | Authenticity, Integrity, Confidentiality, Availability and Authorization | -| Affected Asset | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | - -![Illustration of the VM/Container escape attack showing layers from Hardware resources up to VM(s)/Container(s) with numbered attack paths 1 through 4.](4b398c5e8c4fd656d5b7a61806400650_img.jpg) - -Detailed description: The diagram illustrates a VM/Container escape attack across four architectural layers. From bottom to top, the layers are: Hardware resources, Host OS, Hypervisor or Container Engine, and a top layer containing three VM(s)/Container(s) labeled Near RT RIC, O-CU, and O-DU. Red numbered circles and arrows indicate the attack flow: (1) points to the Near RT RIC container; (2) shows an arrow from the Near RT RIC container down through the Hypervisor to the Host OS; (3) shows an arrow from the Host OS down to the Hardware resources; (4) shows arrows originating from the Hardware resources layer and pointing up to the O-CU and O-DU containers, bypassing the intermediate layers. - -Illustration of the VM/Container escape attack showing layers from Hardware resources up to VM(s)/Container(s) with numbered attack paths 1 through 4. - -Figure Threat model-7 : Illustration of the VM/Container escape attack - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VM-C-03 | -| Threat title | VM/Container data theft | -| Threat description |

The VNF/CNF remotely stores sensitive data (e.g. passwords, private keys, subscription data, logs) on the logical volume that the IMS/DMS allocates to the VNF/CNF. An attacker can retrieve/manipulate these data if they have been stored in an insecure way (e.g. clear text, unsalted hashes) or a malware is installed on the logical volume that the VIM allocates to the VNF/CNF.

Container example: Adversaries may attempt to discover containers and other resources that are available locally within O-Cloud. Other resources may include images, deployments, pods, nodes, and other information such as the status of a cluster. These resources can be viewed within web applications such as the Kubernetes dashboard or can be queried via the Docker and Kubernetes APIs. In Docker, logs may leak information about the environment, such as the environment's configuration, which services are available, and what cloud provider the victim may be utilizing. The discovery of these resources may inform an adversary's next steps in the environment, such as how to perform lateral movement and which methods to utilize for execution.

| -| Threat type | Tampering, Information disclosure | -| Impact type | Integrity, Confidentiality | -| Affected Asset | Images, environment's configuration, and other information such as the status of a cluster | - -1 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VM-C-04 | -| Threat title | VM/Container migration attacks | -| Threat description |

The attacks that exploit VM/Container migration can be divided into two subcategories based on the target plane:

  1. Control Plane Attacks: These attacks target the module that is responsible for handling the migration process on a server which is called the migration module that is found in the host. By exploiting a bug in the migration module software, the attacker can hack the server and take full control over the migration module. This gives the attacker the ability to launch malicious activities including the following:
    1. Migration Flooding: The attacker moves all the VMs/Containers that are hosted on the hacked server to a victim server that does not have enough resource capacity to host all the moved VMs/Containers. This causes a denial of service for the VNFs/CNFs running in the VMs/Containers of the victim server as there will not be enough resources to satisfy the demands of all the hosted VMs/Containers leading into VM/Container performance degradation and VM/Container crashes.
    2. False Resource Advertising: The hacked server claims that it has a large resource slack (a large amount of free resources). This attracts other servers to offload some of their VMs/Containers to the hacked server so that the O-Cloud workload gets distributed over the O-Cloud servers. After moving VMs/Containers from other servers to the hacked server, the attacker can exploit other vulnerabilities to break into the offloaded VMs/Containers as now these VMs/Containers are placed on a server that is under the control of the attacker.
  2. Data Plane Attacks: These constitute the second type of VM/Container migration attacks and those attacks target the network links over which the VM/Container is moved from a server to another. Such data plane attacks include the MitM where an attacker sniffs the packets that are exchanged between the source and destination servers and reads the migrated memory pages. The attacker can monitor and/or modify the received packets while continuing to forward them to victim VM/Container resides so that the victim does not detect that any malicious activity is going on.
| -| Threat type | Tampering, Information disclosure, Denial of Service | -| Impact type | Integrity, Confidentiality, Availability | -| Affected Asset | VNFs/CNFs (Near RT RIC, O-CU, O-DU) | - -2 - -![Diagram illustrating the migration flooding attack. It shows a 'Server with hacked migration module' on the left and a 'Victim server' on the right. On the left server, an attacker (1) exploits the migration module (2) in the Hypervisor or Container Engine. This module is connected to VM(s)/Container(s) running Near RT RIC, O-CU, and O-DU. The attacker migrates more VMs/Containers than the capacity of the victim server (3). On the victim server, the VM(s)/Container(s) are migrated to the Hypervisor or Container Engine, which is also connected to O-DU, O-CU, and Near RT RIC. The victim server's hardware resources are overwhelmed by the excessive number of VMs/Containers.](aa6e28822419dba9f22129fee66c9c4c_img.jpg) - -Diagram illustrating the migration flooding attack. It shows a 'Server with hacked migration module' on the left and a 'Victim server' on the right. On the left server, an attacker (1) exploits the migration module (2) in the Hypervisor or Container Engine. This module is connected to VM(s)/Container(s) running Near RT RIC, O-CU, and O-DU. The attacker migrates more VMs/Containers than the capacity of the victim server (3). On the victim server, the VM(s)/Container(s) are migrated to the Hypervisor or Container Engine, which is also connected to O-DU, O-CU, and Near RT RIC. The victim server's hardware resources are overwhelmed by the excessive number of VMs/Containers. - -3 - -4 - -5 - -**Figure Threat model-8 : Illustration of the migration flooding attack** - -![Figure Threat model-9: Illustration of the false resource advertising attack. The diagram shows two servers. The left server, 'Server with hacked migration module', has a 'Migration module' (step 1) that is compromised. It has a 'Hypervisor or Container Engine' (step 2) on top of 'Host OS' and 'Hardware resources'. Above the hypervisor are VMs/Containers running 'O-DU', 'O-CU', and 'Near RT RIC'. The right server, 'Victim server', has the same stack but with a legitimate 'Migration module'. Red arrows (step 3) show the hacked migration module on the left server sending false resource advertising information to the victim server's migration module. The victim server's migration module then sends this information to the 'O-DU', 'O-CU', and 'Near RT RIC' components (step 4).](c06fd7dbef68a8b788158f2081d9d734_img.jpg) - -Figure Threat model-9: Illustration of the false resource advertising attack. The diagram shows two servers. The left server, 'Server with hacked migration module', has a 'Migration module' (step 1) that is compromised. It has a 'Hypervisor or Container Engine' (step 2) on top of 'Host OS' and 'Hardware resources'. Above the hypervisor are VMs/Containers running 'O-DU', 'O-CU', and 'Near RT RIC'. The right server, 'Victim server', has the same stack but with a legitimate 'Migration module'. Red arrows (step 3) show the hacked migration module on the left server sending false resource advertising information to the victim server's migration module. The victim server's migration module then sends this information to the 'O-DU', 'O-CU', and 'Near RT RIC' components (step 4). - -Figure Threat model-9 : Illustration of the false resource advertising attack - -![Figure Threat model-10: Illustration of the migration MITM attack. The diagram shows two servers. The left server, 'Hacked Server', has a 'Migration module' (step 1) that is compromised. It has a 'Hypervisor or Container Engine' (step 2) on top of 'Host OS' and 'Hardware resources'. Above the hypervisor are VMs/Containers running 'Near RT RIC', 'O-CU', and 'O-DU'. The right server, 'Victim server', has the same stack but with a legitimate 'Migration module'. A 'User' (step 3) is shown interacting with the victim server. Red arrows (step 4) show the hacked migration module on the left server intercepting the user's request and sending it to the victim server's migration module. The victim server's migration module then sends this information to the 'O-DU', 'O-CU', and 'Near RT RIC' components (step 5).](5bba23cc120ad806779f82df1c01bebf_img.jpg) - -Figure Threat model-10: Illustration of the migration MITM attack. The diagram shows two servers. The left server, 'Hacked Server', has a 'Migration module' (step 1) that is compromised. It has a 'Hypervisor or Container Engine' (step 2) on top of 'Host OS' and 'Hardware resources'. Above the hypervisor are VMs/Containers running 'Near RT RIC', 'O-CU', and 'O-DU'. The right server, 'Victim server', has the same stack but with a legitimate 'Migration module'. A 'User' (step 3) is shown interacting with the victim server. Red arrows (step 4) show the hacked migration module on the left server intercepting the user's request and sending it to the victim server's migration module. The victim server's migration module then sends this information to the 'O-DU', 'O-CU', and 'Near RT RIC' components (step 5). - -Figure Threat model-10 : Illustration of the migration MITM attack - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VM-C-05 | -| Threat title | Changing virtualization resource without authorization | -| Threat description |

IMS/DMS which manage the Virtualization layer is responsible for assigning virtualized resource as requested.

There are several ways to cause a DoS attack for the VNFs/CNFs:

  • • If IMS/DMS are compromised or the O2 interface is not securely protected, an attacker who compromised the IMS/DMS or breached the O2 interface can change the virtualized resource used by a VNF/CNF by manipulating the allocation of virtualized resource. For example, when an instantiated VNF/CNF is running, adversaries having access to a compromised IMS/DMS or adversaries breaching the insecure O2 interface can misguide the Virtualization layer to reduce the resource of or delete a VM/Container on which a VNF/CNF is running. This can result in the reliability, availability or even illegal termination of a VNF/CNF and hence the denial of service.
  • • Hardware resource configuration and state information (e.g. events) exchange is performed through O2 interface. If the IMS is compromised or the O2 interface is not securely protected, an attacker who compromised the IMS or breached the O2 interface can tamper the hardware configuration and state information so that the virtualized resource supported by the hardware layer becomes unreliable. For example, adversaries having access to a compromised IMS or adversaries breaching the insecure O2 interface can misguide the O-Cloud platform to detach a hardware accelerator from a VNF/CNF.
  • • Adversaries having access to a compromised virtualization layer can change the virtualization resource used by the instantiated VNF/CNF without authorization,
  • • A malicious VM/Container deployed for one instance of a VNF/CNF on a host can illegally occupy the resources of the instantiated VNF/CNF deployed on the same host, resulting in resource limitation of the instantiated VNF/CNF
| - -| | | -|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | In this type of attacks, the extra allocation of resources for the malicious VM/Container comes at the expense of the other VMs/Containers that share the same server as the malicious VM/Container, where these victim VMs/Containers get allocated less share of resources than what they should actually obtain, which in turn degrades their performance. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | - -1 - -![Diagram illustrating the Theft-of-Service/DoS Attack. It shows a stack of layers: VM(s)/Container(s) (Near RT RIC, O-CU, O-DU), Hypervisor or Container Engine, Host OS, and Hardware resources. A malicious VM/Container is shown running on the hardware resources, with a red arrow pointing to it from the O-DU VM(s)/Container(s) layer. The diagram is numbered 1, 2, and 3, indicating the flow of the attack: 1. Malicious VM/Container instantiation, 2. Resource allocation to malicious VM/Container, 3. Resource starvation for victim VM/Container.](9f50279046b74a4e66a1a0144c3b1d11_img.jpg) - -Diagram illustrating the Theft-of-Service/DoS Attack. It shows a stack of layers: VM(s)/Container(s) (Near RT RIC, O-CU, O-DU), Hypervisor or Container Engine, Host OS, and Hardware resources. A malicious VM/Container is shown running on the hardware resources, with a red arrow pointing to it from the O-DU VM(s)/Container(s) layer. The diagram is numbered 1, 2, and 3, indicating the flow of the attack: 1. Malicious VM/Container instantiation, 2. Resource allocation to malicious VM/Container, 3. Resource starvation for victim VM/Container. - -**Figure Threat model-11 : Illustration of the Theft-of-Service/DoS Attack** - -2 - -3 - -4 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VM-C-06 | -| Threat title | Failed or incomplete VNF/CNF termination or releasing of resources | -| Threat description |

A malicious VNF/CNF is instantiated in the O-Cloud infrastructure to access data not erased from a terminated VNF/CNF or any VNF/CNF that has released resources. Data could include application data, cryptographic keys...

Abuse of resources allocation in the O-Cloud infrastructure to allocate to a malicious VNF/CNF the virtual resources released from a terminated VNF/CNF or from a VNF/CNF that has released resources after a move or a scaling process.

Inclusion of concealed software in the O-Cloud infrastructure to prevent the deletion/erasure of data and states of the VNF/CNF that has been terminated.

| -| Threat type | Information disclosure | -| Impact type | Confidentiality | -| Affected Asset | Sensitive data (e.g. passwords, private keys, subscription data, logs), VNFs/CNFs (Near RT RIC, O-CU, O-DU) software and data | - -5 - -#### 7.4.2.3 Threats concerning VM/Container images - -6 - -7 - -| | | -|---------------------|-------------------------------| -| Threat ID | T-IMG-01 | -| Threat title | VM/Container images tampering | - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat description |

An attacker can inject malicious code or tamper the information inside the unprotected image during on boarding. Then after the instantiation of the VNF/CNF, the tampered code can cause DoS, information stealing, frauds and so on. There are several attacks categories belonging to this threat. Such attacks include:

  • • Build machine attacks: If an attacker can modify or influence the way a VM/Container image is built, they could insert malicious code that will subsequently get run in the production environment.
  • • Supply chain attacks: Once the VM/Container image is built, it gets stored in a registry, and it gets retrieved or “pulled” from the registry at the point where it’s going to be run. An attacker who can replace an image or modify an image between build and deployment could run arbitrary code on your deployment.
| -| Threat type | Tampering, Information disclosure | -| Impact type | Integrity, Confidentiality | -| Affected Asset | VM/Container images | - -1 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-IMG-02 | -| Threat title | Insecure channels with images repository | -| Threat description |

Images often contain sensitive components like an organization’s proprietary software, and embedded secrets and administrator credentials. If connections to registries are performed over insecure channels, man-in-the-middle attacks could intercept network traffic and therefore the contents integrity and confidentiality of images may be compromised. There is also an increased risk of man-in-the-middle attacks that could intercept network traffic intended for registries and steal developer or administrator credentials within that traffic. Thus, could be used to provide fraudulent or outdated images to orchestrators, etc.

| -| Threat type | Tampering, Information disclosure | -| Impact type | Integrity, Confidentiality | -| Affected Asset | VMs/Containers images | - -2 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-IMG-03 | -| Threat title | Secrets disclosure in VM/Container images | -| Threat description |

There are scenarios which benefit from including configuration and secrets, such as passwords or credentials in VNFs/CNFs images. For e.g. VMs/Containers require to be able to connect to other VMs/Containers within the deployment as well as with external entities. All these connections need to be authenticated and secured. One way of achieving this is to provide the requisite secrets or keys to the VMs/Containers which allow them to authenticate, be authenticated, secure the communication channel and signature. A common but in-secure means of providing secrets to the VMs/Containers is by packaging the secrets or the keys with the image itself. There is the risk that the same can be extracted, read or manipulated before the VM/Container is deployed and the secret used.

With a long supply chain, VM/Container images are vulnerable to outside scrutiny. With VM/Container images containing secrets or keys, this becomes a serious threat vector. Adversaries can extract them by obtaining a copy of the image and they can be potentially shared with third parties for illicit gain.

  • • Secrets embedded within a VM/Container image can be stolen.
  • • Secrets embedded within a VM/Container image can be modified

Compromised private keys and algorithms used for image signing due to poor key protection/management/design could undermine the security of image signing process.

| -| Threat type | Spoofing, Tampering, Information disclosure | -| Impact type | Authenticity, Integrity, Confidentiality | -| Affected Asset | VM/Container images | - -1 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-IMG-04 | -| Threat title | Build image on VL | -| Threat description |

Adversaries may build a VM/Container image directly on the VL to bypass defenses that monitor for the retrieval of malicious images from a registry.

Container example: A remote build request may be sent to the Docker API that includes a Dockerfile that pulls a vanilla base image, such as alpine, from a public or local registry and then builds a custom image upon it.

An adversary may take advantage of that build API to build a custom image on the host that includes malware downloaded from their C2 server, and they then may deploy container using that custom image. If the base image is pulled from a public registry, defenses will likely not detect the image as malicious since it's a vanilla image. If the base image already resides in a local registry, the pull may be considered even less suspicious since the image is already in the environment.

| -| Threat type | Spoofing, Tampering, Information disclosure, Denial of Service and Elevation of privilege | -| Impact type | Authenticity, Integrity, Confidentiality, Availability and Authorization | -| Affected Asset | VM/Container images | - -2 - -3 - -#### 7.4.2.4 Threats concerning the virtualization layer (Host OS-Hypervisor/Container engine) - -4 - -5 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VL-01 | -| Threat title | VM/Container hyperjacking attack | -| Threat description |

VMs/Containers run on host machines, and it is needed to ensure that those hosts (Hypervisor/Container Engine/Host OS- are not running vulnerable code (for example, old versions of components with known vulnerabilities).

Hyperjacking is an attack in which adversaries gain control over the host of a server or install a malicious Hypervisor/Container Engine/Host OS and exploit that to run malicious applications on the VM/Container that run on top of the host. This would enable the attacker to control all the VMs/Containers running on the host.

Hyperjacking involves installing a malicious, fake the Hypervisor/Container Engine/Host OS that can manage the entire server system. If the attacker gains access to the Hypervisor/Container Engine/Host OS, everything that is connected to that server can be manipulated. The Hypervisor/Container Engine/Host OS represents a single point of failure when it comes to the security and protection of sensitive information.

For a hyperjacking attack to succeed, an attacker would have to take control of the Hypervisor/Container Engine/Host OS by the following methods:

  • • Injecting a rogue Hypervisor/Container Engine or Host OS beneath the original hypervisor or on top of an existing Hypervisor/Container Engine/Host OS
  • • Directly obtaining control of the original Hypervisor/Container Engine or Host OS
  • • Running a rogue hypervisor on top of an existing hypervisor
| -| Threat type | Spoofing, Tampering, Information disclosure, Denial of Service and Elevation of privilege | -| Impact type | Authenticity, Integrity, Confidentiality, Availability and Authorization | -| Affected Asset | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | - -6 - -![Diagram illustrating the VM/Container hyperjacking attack. An attacker (laptop icon) is shown on the left. Arrows from the attacker point to two red boxes labeled 'Rogue Hypervisor or Container Engine' and 'Rogue Host OS'. These boxes are part of a stack of layers: VM(s)/Container(s) (Near RT RIC, O-CU, O-DU), Hypervisor or Container Engine, Host OS, and Hardware resources. The attacker's arrows point to the 'Rogue Hypervisor or Container Engine' and 'Rogue Host OS' layers, which are highlighted in red. A red circle with the number '1' is next to the attacker, and a red circle with the number '2' is next to the O-CU VM/Container.](66e89867f97592fd4bfab0e4f2b2054f_img.jpg) - -Diagram illustrating the VM/Container hyperjacking attack. An attacker (laptop icon) is shown on the left. Arrows from the attacker point to two red boxes labeled 'Rogue Hypervisor or Container Engine' and 'Rogue Host OS'. These boxes are part of a stack of layers: VM(s)/Container(s) (Near RT RIC, O-CU, O-DU), Hypervisor or Container Engine, Host OS, and Hardware resources. The attacker's arrows point to the 'Rogue Hypervisor or Container Engine' and 'Rogue Host OS' layers, which are highlighted in red. A red circle with the number '1' is next to the attacker, and a red circle with the number '2' is next to the O-CU VM/Container. - -Figure Threat model-12 : Illustration of the VM/Container hyperjacking attack - -1 -2 -3 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VL-02 | -| Threat title | Boot tampering | -| Threat description |

The bootloader of the virtualization layer (Host OS, Hypervisor, Container Engine) for VNF/CNF may be maliciously tampered by an attacker, e.g. the attacker compromises hypervisor or host OS to tamper the bootloader of guest OS (in case of VM) or Container.

In a O-Cloud environment any failure during the boot sequence can result in a number of situations that need to be handled by the NFO/FOCOM:

  • • failure of the physical machine to start at all
  • • physical machine entering a safe-mode
  • • physical machine continuing boot regardless of the integrity measurements
| -| Threat type | Tampering | -| Impact type | Integrity | -| Affected Asset | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | - -4 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-VL-03 | -| Threat title | Attack internal network services | -| Threat description |

In addition to attacking the network between containers, adversaries can also attack supporting services such as DNS service, which is only reachable from within the cluster network. The highly distributed nature of containers requires shared services for example for coordination and service discovery. An attacker can target these services to degrade services. For example, a denial-of-service against the service discovery infrastructure could prevent O-Cloud to react to changing resource requirements properly. Thus, O-Cloud may no longer be able to scale appropriately to sudden demand spikes [i.16].

| -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | Software components at runtime and their associated data | - -5 - -###### 1 7.4.2.5 Threats concerning O-Cloud interfaces - -###### 2 7.4.2.5.1 O2 interface - -3 Two main interfaces are defined in O-RAN WG6 specification and identified as critical assets of O-Cloud, i.e. - 4 interfaces O2 between O-Cloud and SMO. The threats on these interfaces are as follows. - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-O2-01 | -| Threat title | MitM attacks on O2 interface between O-Cloud and SMO | -| Threat description |

If the interface O2 interface is not protected, an attacker can attack all the requests/responses sent between the O-Cloud and the SMO (FOCOM and NFO).

For example, the attacker can tamper/alter/disclose requests and services (See 'Critical services' in 2.3) sent over O2 between O-Cloud and SMO, hence the virtualized resource or relevant status information is not as requested. This affects the normal operation of the O-Cloud, and even causes DoS attacks, information leakage.

An attacker can tamper the specific assignment of virtualized resources to cause resource assignment errors or an attacker can intercept virtualized resources state information leading to information disclosure.

An attacker can compromise IMS to tamper with the hardware state information (e.g. deleting hardware alarm information) to affect the hardware's operation or to result in information disclosure (e.g. an attacker can get the hardware configuration from the compromised IMS. Then, the attacker can attack the hardware according to the configuration such as CPU type, memory size etc.). An attacker can also tamper or intercept the hardware resource configuration and state information if the configuration and state information are transmitted using an insecure protocol on the O2 interface.

| -| Threat type | Tampering, Information disclosure, Denial of Service | -| Impact type | Integrity, Confidentiality, Availability | -| Affected Asset | Telemetry, provisioning, logs, software management, performance information | - -5 - -###### 6 7.4.2.5.2 O-Cloud API - -7 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OCAPI-01 | -| Threat title | MitM attacks on O-Cloud interface between VNFs/CNFs and the virtualization layer | -| Threat description |

An attacker can attack an instantiated VNF/CNF through a compromised virtualization layer. For example, cryptographic keys or other security critical data of an instantiated VNF/CNF could be stolen by an attacker with access to the virtualization layer, or the virtualized resource provided by the Virtualization layer to the instantiated VNF/CNF can be manipulated or the bootloader of Guest OS (in case of VM) or Container of an instantiated VNF/CNF can be tampered by an attacker via a compromised virtualization layer.

| -| Threat type | Tampering, Information disclosure, Denial of Service | -| Impact type | Integrity, Confidentiality, Availability | -| Affected Asset | Host OS, Hypervisor/Container Engine and VNFs/CNFs (Near RT RIC, O-CU, O-DU) | - -8 - -###### 9 7.4.2.6 Threats concerning hardware resources - -10 - -| | | -|------------------|---------| -| Threat ID | T-HW-01 | -|------------------|---------| - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat title | Cross VM/Container side channel attacks | -| Threat description |

In a typical cross-VM/Container side channel attack scenario, an adversary places a malicious VM/Container co-resident to the target VM/Container so that they share the same hardware resources. Then, the attacker extracts useful information such as cryptographic keys from the target VM/Container to use them for traffic eavesdropping and man-in-the-middle attacks. Through the side channel attack, an attacker sharing the same cache as the victim can monitor the cache access behavior of the victim. For example, the attacker is able to monitor cache timing information by measuring the execution of different operations on the victim's VM/Container. Generally, the attacker exploits timings in the shared high-level cache memory. However, power consumption or electromagnetic leaks can also be used as a vector to launch side channel attacks.

In the virtual environment, prior to the cross-VM/Container side channel attack, the attacker needs to identify the target VM/Container's location and place a malicious VM/Container co-resident with the target. Later, that attacker may use the maliciously placed VM/Container to extract information from the target VM/Container with the side channel attack.

Hardware vulnerabilities in processors can also have a large impact on O-Cloud security. Flaws in chip design can result in the compromise of tenant information in the cloud through side-channel attacks [i.24].

| -| Threat type | Tampering, Information disclosure, Denial of Service | -| Impact type | Integrity, Confidentiality, Availability | -| Affected Asset | Sensitive data (e.g. passwords, private keys, subscription data, logs), VNFs/CNFs (Near RT RIC, O-CU, O-DU) related data | - -![Diagram illustrating a cross VM/Container side channel attack. An attacker (represented by a person with a laptop) initiates the attack (1) against VM(s)/Container(s) (Near RT RIC, O-CU, O-DU). The attack flows through the Hypervisor or Container Engine, Host OS, and Hardware resources to the Shared cache (2).](18bb06865e2dada3656ea3d57f290f7f_img.jpg) - -The diagram shows a vertical stack of layers representing a cloud infrastructure. From top to bottom: VM(s)/Container(s) (containing Near RT RIC, O-CU, and O-DU), Hypervisor or Container Engine, Host OS, and Hardware resources. A 'Shared cache' is highlighted in red within the Hardware resources layer. An attacker icon at the top has a red arrow labeled '1' pointing down towards the VMs. Another red arrow labeled '2' points from the Host OS layer down to the Shared cache. There are small bug icons on the Near RT RIC and in the Shared cache. - -Diagram illustrating a cross VM/Container side channel attack. An attacker (represented by a person with a laptop) initiates the attack (1) against VM(s)/Container(s) (Near RT RIC, O-CU, O-DU). The attack flows through the Hypervisor or Container Engine, Host OS, and Hardware resources to the Shared cache (2). - -Figure Threat model-13 : Illustration of a cross VM/Container side channel attack - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-HW-02 | -| Threat title | MitM attacks on the interface between virtualization layer and hardware | -| Threat description | An attacker can utilize the vulnerabilities of hardware (e.g. Meltdown and Specter of CPU in host) to attack virtualization layer and/or VNFs/CNFs through this interface, resulting in tampering, information disclosure or DoS. | -| Threat type | Tampering, Information disclosure, Denial of Service | -| Impact type | Integrity, Confidentiality, Availability | -| Affected Asset | All assets | - -###### 1 7.4.2.7 Threats concerning O-Cloud management (SMO, NFO, FOCOM) - -2 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-ADMIN-01 | -| Threat title | Denial of service against NFO/FOCOM | -| Threat description |

A denial-of-service attack against the NFO/FOCOM can interfere with the ability of operators to control and maintain their deployments. This can lead to the inability to react to changing resource requirements. In addition, the NFO/FOCOM is the external API to interact with the O-Cloud platform. Thus, other services may become inaccessible as well. For example, operators may be unable to retrieve logs, telemetry data. An attacker could use this opportunity to hide additional attacks on VM/Container instances.

In addition, an attacker on the NFO/FOCOM could prevent the O-Cloud software update (VNFs/CNFs, VL) to exploit a known security flaw in the O-Cloud software.

| -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | VM/Container images, VNF/CNF, host OS, Hypervisor/Container Engine software | - -3 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-ADMIN-02 | -| Threat title | Abuse a O-Cloud administration service | -| Threat description |

Usually, the SMO including NFO/FOCOM is exposed to the tenant in a web front-end or REST API. In case these interfaces contain software vulnerabilities or implement authentication and authorization insufficiently, an adversary would be able to gain access to the VM/Container management and pose as a tenant. It is also possible that an adversary gains the ability to submit requests without prior authentication and authorization.

The NFO/FOCOM interfaces encompasses a great deal of privileges because anyone gaining sufficient access is able to deploy new instances and disrupt existing O-Cloud services. It may also be possible for an adversary to submit compromised VM/Container images that unsuspecting tenants then use to initiate O-Cloud services. Moreover, adversaries can use the same access to extract business data, configuration data, user data and possibly credentials. For example, they may be able to create backups of VM/Container instances or they can export VM/Container images. The impact of compromised credentials is exacerbated by the fact that weak and insufficient safeguarding of credentials is recognized as one of the top threats in cloud computing [38].

Container example: Adversaries may abuse a container administration service to execute commands within a container. A container administration service such as the Docker daemon, the Kubernetes API server, or the kubelet may allow remote management of containers within an environment.

Container example: In Docker, adversaries may specify an endpoint during container deployment that executes a script or command, or they may use a command such as docker exec to execute a command within a running container. In Kubernetes, if an adversary has sufficient permissions, they may gain remote execution in a container in the cluster via interaction with the Kubernetes API server, the kubelet, or by running a command such as kubectl exec.

| -| Threat type | Tampering, Information disclosure, Denial of Service and Elevation of privilege | -| Impact type | Integrity, Confidentiality, Availability, Authorization | -| Affected Asset | VNF/CNF, host OS, Hypervisor/Container Engine software and related information | - -4 - -#### 7.4.2.8 Threats concerning Acceleration Abstraction Layer (AAL) - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AAL-01 | -| Threat title | Attacker exploits insecure API to gain access to hardware accelerator resources | -| Threat description |

Insecure AAL API allows an attacker to tamper the requests/responses sent between the AAL components, the O-Cloud platform and O-RAN APPs/VNFs/CNFs.

For example, the attacker can tamper requests and services sent over AALI-C-Mgmt between IMS and the hardware accelerator manager, hence capability of the hardware accelerator device, fault information, logs, performance information and others are not as requested. This affects the normal operation of the O-Cloud, and even causes tampering.

An attacker can tamper application (e.g. O-DU) requests sent over AALI-C-App to an AAL implementation for allocation of buffers. This affects the normal operation of the applications, and even causes tampering.

An attacker can tamper application (e.g. O-DU) requests sent over AALI-P for configuring and managing the AAL-LPU(s). This affects the normal operation of the applications, and even causes tampering.

| -| Threat type | Tampering | -| Impact type | Integrity | -| Affected Asset | Data in transit AALI-C-App & AALI-P interfaces, Data in transit vendor specific interface, AAL profiles, AAL-LPUs, Stored AAL data, AAL software, Device firmware | - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AAL-02 | -| Threat title | Internal Overload DoS attack targeting AAL services | -| Threat description |

Overload situation could appear in the case of DoS attack or increased traffic on AAL interfaces. Inability to mitigate traffic volumetric attacks on AAL affects availability of AAL data and services.

DoS attacks on the AALI-C interface affect the different services provided by the hardware accelerator manager and the transport abstraction framework.

DoS attacks on the AALI-P interface affect the configuration and management of AAL-LPU (Acceleration Abstraction Layer Logical Processing Unit) by an application (e.g. O-DU) in addition to acceleration functionality.

| -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | AAL profiles, AAL-LPUs, Stored AAL data, AAL software, Device firmware | - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AAL-03 | -| Threat title | Fail to clear resources | -| Threat description |

Fail to clear accelerator resources after a process termination. This causes an information leakage and incorrect results for computations. Further, failure to release accelerator resources may prevent other processes from running.

This threat is relevant to accelerator resources either inside the hardware accelerator device (internal memories, registers, cache) or in the O-Cloud memories used by accelerators.

| -| Threat type | Information disclosure, Denial of service | -| Impact type | Confidentiality, Availability | -| Affected Asset | AAL profiles, AAL-LPUs, Stored AAL data, AAL software, Device firmware | - -1 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AAL-04 | -| Threat title | HAM compromise | -| Threat description | A malicious actor can gain access to HAM to gain unauthorized access and control of the hardware accelerator device. This can result in the disruption of services (DoS) and tampering of accelerator components, such as firmware, drivers which can cause the accelerator to behave abnormally or crash altogether. | -| Threat type | Tampering, Denial of service | -| Impact type | Integrity, Availability | -| Affected Asset | Data in transit AALI-C-App & AALI-P interfaces, Data in transit vendor specific interface, AAL profiles, AAL-LPUs, Stored AAL data, AAL software, Device firmware | - -2 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AAL-05 | -| Threat title | Malicious memory accesses | -| Threat description |

AAL that allows one process running on the hardware accelerator device to access memory owned by another process running on the hardware accelerator device can leak information (impact on confidentiality).

Similarly, AAL allowing concurrently executing processes to write to one another's memory may have correctness errors (impact on integrity).

If multiple processes are running concurrently and one is allowed to dominate accelerator resources, the other may suffer from degraded performance. For example, if one process can evict all cache entries belonging to the other, the victim will suffer performance penalties (impact on availability).

| -| Threat type | Information disclosure, Tampering, Denial of service | -| Impact type | Confidentiality, Integrity, Availability | -| Affected Asset | AAL profiles, AAL-LPUs, Stored AAL data, AAL software, Device firmware | - -3 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AAL-06 | -| Threat title | Firmware attacks | -| Threat description | Hardware accelerators often have their own firmware, which can be targeted by attackers. This could include modifying the firmware to introduce vulnerabilities (e.g., malware) or installing a malicious firmware to extract/modify sensitive information or execute unauthorized actions (e.g., control the device remotely). | -| Threat type | Information disclosure, Tampering | -| Impact type | Confidentiality, Integrity | -| Affected Asset | AAL profiles, AAL-LPUs, Stored AAL data, AAL software, Device firmware | - -4 - -#### 7.4.2.9 Threats concerning O-Cloud instance ID - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-O-CLOUD-ID-01 | -| Threat title | ID reuse in O-Cloud's object lifecycle | -| Threat description | In O-Cloud, objects such as Containers, Pods, Nodes, and Services are identified by their IDs within a given compute pool (e.g., cluster in Kubernetes). When an object is deleted, its ID | - -| | | -|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

becomes available for reuse. This means that a new object can be created with the same ID as a previously deleted object. If an object gets deleted but all its associated data isn't properly isolated or cleaned, the ID, if reused, could lead to unintended data associations or leaks.

Potential consequences:

  • • Data Residue: A new object, reusing an ID, may inherit residual data or configurations from its predecessor, leading to potential misconfigurations and incorrect data associations. This can result in sensitive data exposure.
  • • Data Overwrite: Automated processes unaware of the deletion and subsequent recreation might mistakenly write or read data from the new object, thinking it's the old one.
  • • Monitoring Ambiguities: Monitoring tools might combine metrics from the old and new objects, resulting in confusing data.
  • • Operational Disruptions: The new object might operate based on the residual configurations of the old object, potentially leading to system inefficiencies or failures.
| -| Threat type | Tampering, Information disclosure | -| Impact type | Integrity, Confidentiality | -| Affected Asset | O-Cloud Provisioning information, Software components at runtime and their associated data, Security event logs | - -1 -2 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-O-CLOUD-ID-02 | -| Threat title | Node redundancy in O-Cloud deployments | -| Threat description |

Nodes in O-Cloud often represent physical or virtual machines. If a machine fails and is replaced without deleting its corresponding Node object, and the new machine is given the same ID or the hostname, O-Cloud might treat the new machine as if it were the original.

Potential consequences:

  • • Resource Mismatch: The new host might have different resources (CPU, memory, storage) than the old one, leading to scheduling issues or resource constraints.
  • • Stale Data: The new node might inherit data or configurations from the old node, leading to potential security or operational risks.
  • • Network Issues: Network configurations or IP address assignments might be inconsistent or conflicting.
| -| Threat type | Spoofing, Tampering, Information disclosure, Denial of Service | -| Impact type | Authenticity, Integrity, Confidentiality, Availability | -| Affected Asset | O-Cloud Provisioning information, Software components at runtime and their associated data, Security event logs | - -3 -4 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-O-CLOUD-ID-03 | -| Threat title | O-Cloud ID mismanagement | -| Threat description |

IDs are crucial for uniquely identifying objects within the O-Cloud. Mismanagement occurs when these IDs are not properly assigned, tracked, or validated, leading to potential overlaps or inconsistencies.

Potential consequences:

  • • ID Collision: Due to system glitches or bugs, two distinct objects could inadvertently be allocated the same ID. Such an occurrence is termed an ID collision. This can result in
| - -| | | -|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

operations meant for one object inadvertently affecting the other.

  • • Resource Overwrite: If two objects share the same ID, updates or modifications intended for one might overwrite the data of the other, leading to data inconsistencies or loss.
  • • ID-Based Permissions: Many security protocols and access controls in O-Cloud can be tied to object IDs. If an attacker can predict, guess, or manipulate the ID generation process, they might gain unauthorized access to resources.
  • • Log Merging: Monitoring tools and logging systems use IDs to track events and operations related to specific objects. If two objects share an ID, their logs might get merged, making it challenging to trace events back to their source.
  • • RBAC Anomalies: Role-Based Access Control (RBAC) regulations attached to specific object IDs could unintentionally approve or restrict access to the novel object due to misidentification.
| -| Threat type | Spoofing, Tampering, Information Disclosure, Repudiation, Elevation of Privilege, Denial of Service | -| Impact type | Authenticity, Integrity, Non-repudiability, Confidentiality, Availability, Authorization | -| Affected Asset | O-Cloud Provisioning information, Software components at runtime and their associated data, Security event logs | - -#### 7.4.2.10 Threats concerning time synchronization - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-TS-01 | -| Threat title | Time synchronization disruption in O-Cloud | -| Threat description |

Disruption or manipulation of the time synchronization process within the O-Cloud can lead to severe security and operational issues. An attacker may target the time synchronization mechanisms to alter time settings across O-Cloud nodes, leading to:

  • • Impersonation of time synchronization server: An attacker may impersonate a legitimate time synchronization server, tricking nodes into accepting incorrect time data. This can cause nodes to synchronize with a malicious time source, leading to widespread time discrepancies.
  • • Data integrity loss: Inconsistent timestamps can corrupt logs and audit trails within the O-Cloud, making it difficult to trace and analyze security events accurately.
  • • Operational disruption: Time-sensitive operations within the O-Cloud may be disrupted, leading to data loss and service outages.
  • • Authentication and authorization bypass: Many security mechanisms in the O-Cloud rely on accurate time. Disrupted time synchronization can undermine token expiration, certificate validity, and other time-based access controls, potentially allowing unauthorized access to O-Cloud resources.

EXAMPLE: Time-sensitive operations such as automated backups, scheduled tasks (e.g., resource scaling, patch management), and certificate renewals.

NOTE: This threat is linked to the operation of CronJob resources as described in clause 4.3.1.1.6 of the O-RAN specification [i.34]. Any disruption or manipulation of the time synchronization process can severely impact scheduled operations managed by CronJobs within the O-Cloud.

| -| Threat type | Spoofing, Tampering, Denial of Service and Elevation of privilege | -| Vulnerabilities | Insecure time synchronization protocols | - -| | | -|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | Insufficient authentication mechanisms and access controls for the time synchronization settings
Misconfiguration of time synchronization settings on O-Cloud nodes | -| Impact type | Authenticity, Integrity, Availability and Authorization | -| Affected Asset | Log and audit trails
O-Cloud time synchronization settings | - -### 7.4.3 Threats to open source code - -Open source introduces the following threats: - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OPENSRC-01 | -| Threat title | Developers use SW components with known vulnerabilities and untrusted libraries that can be exploited by an attacker through a backdoor attack | -| Threat description |

The O-RAN Software Community is a Linux Foundation project, supported and funded by O-RAN to lead the implementation of the O-RAN specifications in Open Source. Industry has recognized that Open Source code introduces security risks. Open Source vulnerabilities are publicly available on the National Vulnerability Database (NVD). While this is intended for developers to disclose vulnerabilities, it is also used by hackers to exploit those vulnerabilities. Vulnerabilities frequently propagate as developers re-use free open source code enabling backdoors to attacks. There have been notable vulnerabilities from downloading open source libraries and dependencies, as well as supply chain risks when downloading Open Source code from untrusted repositories.

Some O-RAN vendors and operators may not have accurate inventories of open-source software dependencies used by their different applications, or a process to receive and manage notifications concerning discovered vulnerabilities or available patches from the community supporting the open-source.

Some O-RAN vendors may not have a lack of consistent Supply Chain traceability and security, and a lack of coding best practices conflicts with Security-by-Design principles.

Developers may use modules with known vulnerabilities and untrusted libraries that can be exploited by an attacker through a backdoor attack.

Attackers can exploit a vulnerability on the open source code and infects a hypervisor, operating system, VM or container with a malware.

| - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OPENSRC-02 | -| Threat title | A trusted developer intentionally inserts a backdoor into an open source code O-RAN component | -| Threat description |

A trusted developer intentionally inserts a backdoor by injecting a few lines of malicious code into an open source code component to be used within the O-RAN system. A software project team picks up and uses the infected open source code and the development team's tools for vetting and testing the component do not detect the malicious code. Unknowingly they have introduced a vulnerability into their O-RAN software code.

The vulnerability has gone undetected and the threat actor is able to compromise the software through the inserted vulnerability. The resulting effect on the O-RAN system can take a variety of forms, from being annoying to impacting system performance (DoS) to the loss of sensitive data.

| - -### 7.4.4 Physical Threats - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-PHYS-01 | -| Threat title | An intruder gains physical access to O-RAN components to cause damage by manipulation / modification to software / software configuration /management. | -| Threat description |

Physical attacks on the O-RAN deployment that stores or processes keys, user plane data, control plane data and management data in cleartext.

O-RAN physical components might be vulnerable if:

  • • Improper physical security protection of data centers, PNFs, operation areas, etc.
  • • Hardware backdoor

Attackers try to modify the O-RAN components settings and configurations via local access.

Physical access to O-RAN components due to unsecured management ports and consoles (such as JTAG, serial consoles or dedicated management ports), relaxed administrator credentials management, unsecured HW and SW configuration/management could allow an attacker to inject malware and/or manipulate existing software,.

| -| Threat Type | Tampering | -| Vulnerabilities | Improper physical security protection, hardware backdoor | -| Impact Type | Integrity | -| Affected Assets | ALL | - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-PHYS-01A | -| Threat title | An intruder gains physical access to O-RAN components to access sensitive data | -| Threat description |

Physical attacks on the O-RAN deployment that stores or processes keys, user plane data, control plane data and management data in cleartext.

O-RAN physical components might be vulnerable if:

  • • Improper physical security protection of data centers, PNFs, operation areas, etc.
  • • Hardware backdoor

Attackers try to modify the O-RAN components settings and configurations via local access.

Physical access to O-RAN components due to unsecured management ports and consoles (such as JTAG, serial consoles or dedicated management ports), relaxed administrator credentials management, unsecured HW and SW configuration/management could allow an attacker to steal unprotected private keys, certificates, and hash values.

| -| Threat Type | Information Disclosure | -| Vulnerabilities | Improper physical security protection, hardware backdoor | -| Impact Type | Confidentiality | -| Affected Assets | ALL | - -| | | -|------------------|-------------------| -| Threat ID | T-PHYS-01B | -|------------------|-------------------| - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat title | An intruder gains physical access to O-RAN components to cause performance degradations, denial of service. | -| Threat description |

Physical attacks on the O-RAN deployment that stores or processes keys, user plane data, control plane data and management data in cleartext.

O-RAN physical components might be vulnerable if:

  • • Improper physical security protection of data centers, PNFs, operation areas, etc.
  • • Improper protection against power outages (power supply)
  • • Improper maintenance and monitoring of hardware parameters
  • • Hardware backdoor

Attackers try to modify the O-RAN components settings and configurations via local access.

Physical access to O-RAN components due to unsecured management ports and consoles (such as JTAG, serial consoles or dedicated management ports), relaxed administrator credentials management, unsecured HW and SW configuration/management could allow an attacker disable security features, create a performance issue by manipulation of parameters.

| -| Threat Type | Denial of service | -| Vulnerabilities | Improper physical security protection, Improper maintenance and monitoring of hardware parameters, hardware backdoor | -| Impact Type | Availability | -| Affected Assets | ALL | - -1 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-PHYS-02 | -| Threat title | An intruder into the Fronthaul cable network attempts to gain electronic access to cause damage or access sensitive data | -| Threat description | O-RU and O-DU may be located at different premises with the fronthaul supported by a cable network. Attackers can gain access to, or control over, data traffic by breaching terminals in the cable landing sites (O-RU or O-DU). | -| Threat Type | Information disclosure | -| Vulnerabilities | Physical access to the open Fronthaul cable network | -| Impact Type | Confidentiality | -| Affected Assets | Critical S-Plane Data [ASSET-D-01]
Critical M-Plane Data [ASSET-D-02]
Critical C-Plane Data [ASSET-D-04]
Critical U-Plane Data [ASSET-D-05]
O-DU software [ASSET-C-05]
O-RU software [ASSET-C-06]
Shared O-RU [ASSET-C-31]
O-RU Host [ASSET-C-32]
O-RU Tenant (Shared Resource Operator) [ASSET-C-33]
O-DU Host [ASSET-C-34] | - -| | | -|--|--------------------------------------------------------------------------------------| -| | O-DU tenant (Shared Resource Operator) [ASSET-C-35]
PNF NF equipment [ASSET-C-12] | -|--|--------------------------------------------------------------------------------------| - -### 7.4.5 Threats against 5G radio networks - -Threats against 5G radio networks include: - -| Threat ID | T-RADIO-01 | -|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat title | Disruption through radio Jamming | -| Threat description |

Disruption through radio jamming is possible by analyzing the physical downlink and uplink control channels and signals. 5G radio network is vulnerable to:

  • • Jamming Vulnerability of Reference Signals
  • • Jamming Vulnerability of Synchronization Signal
  • • Jamming Vulnerability of the PBCH
  • • Jamming Vulnerability of PDCCH
  • • Jamming Vulnerability of Physical Uplink Control Channel
  • • Jamming Vulnerability of Physical Random-Access Channel

NOTE : The O-RAN OEMs need to develop new intelligence that can proactively alert the operator when this attack is initiated so that the operator can take appropriate actions to mitigate.

| -| Threat Type | Denial of Service | -| Vulnerabilities | Weakness of wireless cellular communications | -| Impact Type | Availability | -| Affected Assets | Reference signals, synchronization signal and channels in downlink and uplink between O-RU and UE [ASSET-D-06]
O-DU software [ASSET-C-05]
O-RU software [ASSET-C-06] | - -| Threat ID | T-RADIO-01A | -|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat title | Disruption through radio Sniffing and Spoofing | -| Threat description |

Disruption through radio jamming is possible by analyzing the physical downlink and uplink control channels and signals. 5G radio network is vulnerable to:

  • • Sniffing and Spoofing Vulnerability of the PBCH

NOTE: In the scenario of RF spoofing, the UE needs to be able to validate the legitimacy of the O-RU as being one owned and operated by the operator. 3GPP has proposed in a study to use Digital Signatures to mitigate this threat but there has been no agreement on this to date. The O-RAN OEMs need to develop new intelligence that can proactively alert the operator when this attack is initiated so that the operator can take appropriate actions to mitigate.

| -| Threat Type | Spoofing | -| Vulnerabilities | Weakness of wireless cellular communications | -| Impact Type | Authenticity | -| Affected | Reference signals, synchronization signal and channels in downlink and uplink between O-RU and | - -| | | -|---------------|-----------------------------------------------------------------------------| -| Assets | UE [ASSET-D-06]
O-DU software [ASSET-C-05]
O-RU software [ASSET-C-06] | -|---------------|-----------------------------------------------------------------------------| - -1 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-RADIO-02 | -| Threat title | DoS attacks on cognitive radio networks [i.17] | -| Threat description | Cognitive radio (CR) technology, which is designed to enhance spectrum utilization, depends on the success of opportunistic access, where unlicensed secondary users (SUs) exploit spectrum void unoccupied by primary users (PUs) for transmissions. To realize DoS attacks, malicious users (MUs) target the critical functionalities for CR ecosystems, including spectrum sensing, agile radio, and light-handed regulation since once these functionalities fail, SUs are not able to communicate effectively. For example, MUs can directly jam the victim by injecting interference or deceive SUs into believing that there is a PU by emulating the signal characteristics of the PU, thereby evacuating the occupied spectrum. Moreover, the liability rule is vulnerable to the selfish and greedy users aiming to maximize their own private benefits. Since complying with the rule results in fewer transmission opportunities, such SUs may not want to invest efforts to follow the rule and thus will transmit simultaneously with PUs. | -| Threat Type | Denial of Service | -| Vulnerabilities | Weakness of wireless cellular communications | -| Impact Type | Availability | -| Affected Assets | Reference signals, synchronization signal and channels in downlink and uplink between O-RU and UE [ASSET-D-06]
O-DU software [ASSET-C-05]
O-RU software [ASSET-C-06] | - -2 - -### 7.4.6 Threats against AI/ML system - -#### 7.4.6.1 Introduction - -This section provides the relevant threats against the AI/ML system implemented in O-RAN architecture. - -#### 7.4.6.2 Input Manipulation Attacks - -7 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-IM-1 | -| Threat title | Training Data Control | -| Threat description | An adversary takes control of a subset of the training data by inserting or modifying training samples. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Integrity | -| Affected Assets | Training or test data: data sets collected externally or internally from the Near-RT RIC, O-CU and O-DU and passed to the ML training hosts in a ML system. [ASSET-D-25]
The trained ML model [ASSET-D-26],
The ML prediction results built into the model [ASSET-D-27],
The behaviour of the ML system [ASSET-D-28]. | - -8 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------| -| Threat ID | T-AIML-IM-2 | -| Threat title | Testing Data Control | -| Threat description | An adversary adds perturbations to testing samples at model deployment time to generate | - -| | | -|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | adversarial examples or in backdoor poisoning attacks | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Integrity | -| Affected Assets | Training or test data: data sets collected externally/externally or internally from the Near-RT RIC, O-CU and O-DU and passed to the ML training hosts in a ML system. [ASSET-D-25]
The trained ML model [ASSET-D-26],
The ML prediction results built into the model [ASSET-D-27],
The behaviour of the ML system [ASSET-D-28]. | - -1 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-IM-3 | -| Threat title | Label Manipulation | -| Threat description | An adversary may intentionally mis-assign labels to training data. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Integrity | -| Affected Assets | Training or test data: data sets collected externally or internally from the Near-RT RIC, O-CU and O-DU and passed to the ML training hosts in a ML system. [ASSET-D-25]
The trained ML model [ASSET-D-26],
The ML prediction results built into the model [ASSET-D-27],
The behaviour of the ML system [ASSET-D-28]. | - -2 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-IM-4 | -| Threat title | AI/ML Query Exploitation | -| Threat description | An adversary may submit queries to the model and receive predictions (either labels or model confidences) and confidential data. | -| Threat type | Information Disclosure | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in AI/ML APIs | -| Impact type | Confidentiality | -| Affected Assets | The trained ML model [ASSET-D-26],
The ML prediction results built into the model [ASSET-D-27],
The behaviour of the ML system [ASSET-D-28]. | - -3 - -#### 7.4.6.3 Data Poisoning Attacks - -4 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-DP-01 | -| Threat title | Black-box Data Poisoning | -| Threat description | An attacker in possession of a compromised data-source can inject poisoned data which can be consumed by AI/ML for training. For such an attack, the attacker does not need to know any details of the AI/ML algorithm, or the parameters being used. Knowledge of inputs and outputs of AI/ML is sufficient to launch such attacks. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],

AI/ML Workflow [ASSET-C-61] | - -5 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-DP-02 | -| Threat title | Grey-box Data Poisoning | -| Threat description | An attacker being able to query the database which stores the training data, and/or streaming data used for online ML models, and/or AI/ML models may be able to get more details about the AI/ML algorithms being used and parameters configured if any. This can help the attacker to launch an attack which can poison the training data in a manner that would affect that particular algorithm or its parameters the most. | - -| | | -|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in data transport, vulnerabilities in training database | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
O1 interface for streaming data [ASSET-C-22],
A1 interface [ASSET-C-14],
E2 interface for streaming data [ASSET-C-40],

AI/ML Workflow [ASSET-C-61] | - -1 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-DP-03 | -| Threat title | White-box Data Poisoning | -| Threat description | An attacker having full knowledge of the AI/ML algorithm being used, the configurable parameters like thresholds, hyper-parameters, etc. can launch a data poisoning attack in a manner which can modify the behaviour of AI/ML algorithm with slow poisoning and can make it very challenging to detect such attacks. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
O1 interface for streaming data [ASSET-C-22],
A1 interface [ASSET-C-14],
E2 interface for streaming data [ASSET-C-40],

AI/ML Workflow [ASSET-C-61] | - -2 - -3 - -#### 7.4.6.4 Membership Inference Attacks - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MEI-01 | -| Threat title | Information Access – Membership Inference | -| Threat description | An attacker possesses different levels of information on the model architecture, training parameters, training data, and relation between the output to the input. Based on the level of information access, the membership information attack (MIA) can be Black-box MIA, or Gray-box MIA or White-box MIA. | -| Threat type | Information disclosure | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Confidentiality | -| Affected Assets | Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11] | - -4 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MEI-02 | -| Threat title | Inference Technique – Membership Inference | -| Threat description | An attacker by applying different analysis methods tries to infer input to output relation. Some of the attack types are Decision threshold analysis, Gradient-based analysis, Distance-based analysis. In Decision threshold analysis, the subtle changes in input's relation to the model's output confidence score is observed. In Gradient-based analysis techniques such as back propagation is used to analyse input to output variation. In Distance-based analysis the distance between model's output for different inputs in multi-dimensional space is used. | -| Threat type | Information disclosure | - -| | | -|------------------------|----------------------------------------------------------------------------------------| -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Confidentiality | -| Affected Assets | Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11] | - -1 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MEI-03 | -| Threat title | Target based – Membership Inference | -| Threat description | In a target-based membership attack the attacker would like to understand whether specific individual data or data of a group of individuals are involved in the training set. The attack types are known as Individual membership inference attack, Group membership inference attack, respectively. In Individual membership inference attack, the attacker tries to determine if a specific user information is included in the training data. In Group membership inference attack, the attacker tries to determine behaviour of individuals and group them based on available data. | -| Threat type | Information disclosure | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Confidentiality | -| Affected Assets | Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11] | - -2 - -3 - -#### 7.4.6.5 Model Stealing - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-ME-01 | -| Threat title | Intellectual Property Theft | -| Threat description | Stolen models can lead to the theft of intellectual property, allowing attackers to replicate the model's functionality without incurring the associated development costs. If a competitor gains unauthorized access to a trained model, it can undermine the original developer's competitive advantage by using the model for similar or competing purposes. | -| Threat type | Information disclosure | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | -| Impact type | Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -4 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-ME-02 | -| Threat title | Data Privacy Violations | -| Threat description | The stolen model may contain sensitive information embedded within its learned parameters. This can result in privacy breaches, especially if the model was trained on sensitive or personal data. | -| Threat type | Information disclosure | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | -| Impact type | Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -5 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-ME-03 | -| Threat title | Adversarial Attacks with Stolen Models | -| Threat description | Attackers may exploit the extracted model to craft adversarial examples (to mount an evasion | - -| | | -|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | attack) or launch targeted attacks against the system that initially deployed the model, using obtained knowledge about possible vulnerabilities. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
Near-RT-RIC SW [ASSET-C-02],
Non-RT-RIC SW [ASSET-C-11],

AI/ML Workflow [ASSET-C-61] | - -1 - -#### 7.4.6.6 Model Inversion Threats - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MOI-01 | -| Threat title | Black-box Model Inversion | -| Threat description | An attacker has access to the model's input-output pairs allowing them to input data and receive predictions. The attacker generates inputs, analyzes the model's outputs, and iteratively refines the inputs based on the obtained information. This process continues until the attacker is able to approximate the original training data. The attacker has no knowledge of the model's architecture, parameters, or the training data. | -| Threat type | Information Disclosure | -| Vulnerabilities | Model is overfitted, model may have memorized specific training examples, model API not properly protected | -| Impact type | Disclosure of sensitive/proprietary data | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26]
The ML prediction results built into the model [ASSET-D-27]
The behavior of the ML system including tasks for data collection, data wrangling, pipeline management, model retraining, and model deployment. [ASSET-D-28] | - -3 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MOI-02 | -| Threat title | White-box Model Inversion | -| Threat description | An attacker has access to the AI model, including its architecture, parameters (such as weights and biases), and possibly partial knowledge of the training data. This information allows the attacker to exploit the inner workings of the model more effectively and reconstruct the original training data with higher accuracy. In this scenario, the attacker can use gradient-based optimization techniques to maximize the model's confidence in the target label or class, ultimately converging to a close approximation of the target data point. | -| Threat type | Information Disclosure | -| Vulnerabilities | Model is not protected, training data is not protected, model is overfitted, model may have memorized specific training examples, model API not protected | -| Impact type | Disclosure of sensitive/proprietary data | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26]
The ML prediction results built into the model [ASSET-D-27]
The behavior of the ML system including tasks for data collection, data wrangling, pipeline management, model retraining, and model deployment. [ASSET-D-28] | - -4 - -#### 7.4.6.7 AI Supply Chain Attacks - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-SC-01 | -| Threat title | Data Poisoning via Supply Chain | -| Threat description | Adversaries may corrupt or manipulate training datasets to cause the AI model to learn incorrect associations or make biased predictions. This can lead to degraded performance, wrong decisions, or even backdoors in the final system. | - -5 - -| | | -|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat type | Tampering, Denial of Service | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model transfer | -| Impact type | Integrity, Availability | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -1 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-SC-02 | -| Threat title | Model Tampering | -| Threat description | Attackers might inject malicious code or logic into the AI model itself during training or deployment. This could allow them to gain control over the target system, steal sensitive data, or force the AI system to produce incorrect results on demand. | -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Vulnerabilities in ML model transfer | -| Impact type | Integrity, Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -2 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-SC-03 | -| Threat title | Backdoor via Supply Chain | -| Threat description | In these attacks, a seemingly benign AI model is infected with malicious code that remains dormant until it receives a specific trigger. At this point, the attacker can remotely activate the backdoor and use it to compromise the target system or exfiltrate data. | -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Vulnerabilities in ML model transfer | -| Impact type | Integrity, Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -3 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-SC-04 | -| Threat title | Hardware Tampering | -| Threat description | Malicious actors may also focus on manipulating the hardware used for AI processing, such as GPUs, ASICs, or FPGAs. By introducing backdoors or vulnerabilities in these components, attackers can compromise the confidentiality, integrity, and availability of AI systems even if the software and data are secure. | -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Vulnerabilities in the AI processing HW | -| Impact type | Integrity, Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02], | - -| | | -|--|----------------------------------------------------------| -| | Non-RT RIC [ASSET-C-11] ,
AI/ML Workflow [ASSET-C-61] | -|--|----------------------------------------------------------| - -1 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-SC-05 | -| Threat title | Insecure Maintenance APIs | -| Threat description | Many AI services are exposed through APIs, for example for deployment and maintenance, that can be abused by attackers to launch supply chain attacks. If these APIs are not properly secured, they can be used to inject malicious code or exfiltrate sensitive information from the target system. | -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Vulnerabilities in the ML maintenance APIs | -| Impact type | Integrity, Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11] ,
AI/ML Workflow [ASSET-C-61] | - -2 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-SC-06 | -| Threat title | Third-party Libraries and Dependencies | -| Threat description | AI systems often rely on third-party libraries and open-source components which might contain vulnerabilities or backdoors that attackers can exploit. Insecure software supply chains increase the risk of such attacks. | -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Vulnerabilities in the ML-related SW | -| Impact type | Integrity, Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11] ,
AI/ML Workflow [ASSET-C-61] | - -3 - -#### 7.4.6.8 Output Integrity Attack - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-OI-01 | -| Threat title | Denial of Service Impacting Output Integrity | -| Threat description | The AI/ML output can be manipulated to contain values that are incorrect or out of range. This can lead to service degradation, partial failure or total failure of the O-RAN element that is consuming this output and lead to denial of service to other O-RAN elements or subscribers. | -| Threat type | Denial of service | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | -| Impact type | Availability | -| Affected Assets | Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML prediction results [ASSET-D-27],
A1 policies [ASSET-D-07],
E2 node data [ASSET-D-11],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -5 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-OI-02 | -| Threat title | Subscriber QoE Change | -| Threat description | The AI/ML output can be manipulated to contain values which can influence the configuration or policies being used by the O-RAN elements. This can lead to a behavior of O-RAN network elements where a subscriber or a group of subscribers is treated unfairly or with a preference. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | -| Impact type | Integrity | -| Affected Assets | Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML prediction results [ASSET-D-27],
A1 policies [ASSET-D-07],
E2 node data [ASSET-D-11],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -1 - -#### 7.4.6.9 Model Poisoning - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MP-01 | -| Threat title | Model Parameter Poisoning | -| Threat description | The adversary has access to the parameters file of a trained model. The parameters file is altered to change the model's predictions to achieve the goals of the adversary. | -| Threat type | Tampering | -| Vulnerabilities |
  • Insufficient access controls to the model's parameters [i.33]
  • Inadequate monitoring and logging of model's activity [i.32]
  • Lack of control for poisoning in model [i.32]
  • Weak access protection mechanisms for ML model components [i.32]
| -| Impact type | Integrity | -| Affected Assets | [ASSET-D-26] Trained ML model.
[ASSET-C-12] ML components deploying machine learning (xApps, rApps).
[ASSET-D-27] The ML prediction results built into the model (e.g. expected outcomes). | - -3 -4 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MP-02 | -| Threat title | Inference Algorithm Poisoning | -| Threat description | The adversary has access to the code of a trained model. The inference algorithm is altered to change the model's predictions to achieve the goals of the adversary. | -| Threat type | Tampering | -| Vulnerabilities |
  • Insufficient access controls to the model's code [i.33]
  • Inadequate monitoring and logging of model's activity [i.32]
  • Lack of code integrity checking
  • Weak access protection mechanisms for ML model components [i.32]
| -| Impact type | Integrity | -| Affected Assets | [ASSET-D-26] Trained ML model.
[ASSET-D-27] The ML prediction results built into the model (e.g. expected outcomes). | - -5 -6 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MP-03 | -| Threat title | Learning Algorithm Poisoning | -| Threat description | The adversary has access to the code of an untrained model. The learning algorithm is altered to cause the model to make incorrect predictions. | -| Threat type | Tampering | -| Vulnerabilities |
  • Insufficient access controls to the model's code [i.33]
  • Inadequate monitoring and logging of model's activity [i.32]
  • Weak access protection mechanisms for ML model components [i.32]
  • Lack of code integrity checking
| -| Impact type | Integrity | -| Affected Assets | [ASSET-C-12] ML components deploying machine learning (xApps, rApps). | - -7 -8 - -| | | -|------------------|--------------| -| Threat ID | T-AIML-MP-04 | -|------------------|--------------| - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat title | Model Control | -| Threat description | An adversary takes control of the model parameters by either generating a Trojan trigger and inserting it in the model or by sending malicious local model updates in federated learning | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in ML model storage, vulnerabilities in ML model transfer | -| Impact type | Integrity | -| Affected Assets | ML components deploying machine learning [ASSET-C-12]
The trained ML model [ASSET-D-26],
The ML prediction results built into the model [ASSET-D-27],
The behavior of the ML system [ASSET-D-28]. | - -1 - -2 - -#### 7.4.6.10 Model Skewing Attacks - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MS-01 | -| Threat title | Data Manipulation for Model Skewing | -| Threat description | The attacker manipulates the data involved in the training of the model. The attacker modifies/injects the training data with modified data, or modifies the labels associated with the training data, resulting in learnt model behaviour to be changed. The impacted models have reduced accuracy / biased trained models, thereby the ability to make correct predications is compromised, or the output is biased. The model skewing attacks can significantly impact the operation of networks causing service disruptions, reputational damage, and financial losses. | -| Threat type | Tampering, (Applicable Threats T-SMO-11, T-SMO-12, T-SMO-31, t_rApps_05) | -| Vulnerabilities | Vulnerabilities in (i) training data validation, (ii) less robust model training against cyber-attacks, (iii) less model performance monitoring for monitoring of suspicious activity | -| Impact type | Integrity, and use-case specific impacts on O-RAN network. | -| Affected Assets | Trained ML model [ASSET-D-26],
ML Prediction Results [ASSET-D-27],
ML system [ASSET-D-28],
AI/ML Workflow [ASSET-C-61] | - -3 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-MS-02 | -| Threat title | Feedback Manipulation for Model Skewing | -| Threat description | The attacker manipulates the feedback mechanisms used by the AI/ML for continuous improvement during deployment. The attack can significantly impact the operation of networks causing service disruptions, reputational damage, and financial losses. | -| Threat type | Tampering, (Applicable Threats T-SMO-11, T-SMO-12, T-SMO-31, t_rApps_05) | -| Vulnerabilities | Vulnerabilities in (i) less secure feedback mechanisms to prevent manipulation, (ii) less robust model training against cyber-attacks, (iii) less model performance monitoring for monitoring of suspicious activity | -| Impact type | Integrity, and use-case specific impacts on O-RAN network. | -| Affected Assets | Trained ML model [ASSET-D-26],
ML Prediction Results [ASSET-D-27],
ML system [ASSET-D-28] | - -4 - -5 - -#### 7.4.6.11 Transfer Learning Attack - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-TL-01 | -| Threat title | Data Poisoning for Transfer Learning | -| Threat description | Attackers can poison the source model's training data by injecting malicious samples, which get propagated into the target model during transfer learning, causing misclassification or unintended behaviour in the latter. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -1 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-TL-02 | -| Threat title | Model Stealing for Transfer Learning | -| Threat description | By using a series of carefully crafted queries to the source model, attackers can extract sensitive information about its architecture and parameters, which they can then use to build a similar model for malicious purposes. | -| Threat type | Information disclosure | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | -| Impact type | Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -2 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-TL-03 | -| Threat title | Adversarial Examples | -| Threat description | Attackers can create input samples that fool both the source and target models, even if these inputs are visually or semantically similar to benign ones. These adversarial examples can be used to bypass security systems or cause misclassifications in critical applications like self-driving cars or healthcare. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -3 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-TL-04 | -| Threat title | Backdoor for Transfer Learning | -| Threat description | Attackers can embed hidden malicious functionality into the source model, which remains dormant until triggered by specific input patterns. When the trojans are transferred to the target model, they can cause unexpected behaviour or leak sensitive information. | -| Threat type | Tampering, Information disclosure | -| Vulnerabilities | Vulnerabilities in ML model transfer | -| Impact type | Authenticity, Integrity, Availability, Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
ML components deploying machine learning (xApps, rApps) [ASSET-C-12],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11],
AI/ML Workflow [ASSET-C-61] | - -4 - -5 - -#### 7.4.6.12 AI Energy-Latency Attack - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-EL-01 | -| Threat title | Model Extraction | -| Threat description | By monitoring the energy and latency patterns, an attacker might deduce the structure of the neural network, including the types of layers, their sequence, and possibly hyperparameters. | -| Threat type | Information disclosure | - -| | | -|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Vulnerabilities | Vulnerabilities in data sources | -| Impact type | Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Trained ML model [ASSET-D-26],
Near-RT-RIC SW [ASSET-C-02],
Non-RT-RIC SW [ASSET-C-11],
AAL software [ASSET-C-29],
Hardware accelerator device firmware [ASSET-C-30] | - -1 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-EL-02 | -| Threat title | Data Inference | -| Threat description | Observing the energy and latency signatures of different computations could allow an attacker to make inferences about the input data, potentially leading to privacy breaches, especially if the data is sensitive. | -| Threat type | Information disclosure | -| Vulnerabilities | Vulnerabilities in data sources | -| Impact type | Confidentiality | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Near-RT-RIC SW [ASSET-C-02],
Non-RT-RIC SW [ASSET-C-11],
AAL software [ASSET-C-29],
Hardware accelerator device firmware [ASSET-C-30] | - -2 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-EL-03 | -| Threat title | Denial of Service via Side Channels | -| Threat description | An attacker could exploit these side channels to craft inputs that maximize energy consumption or computation time, leading to a denial of service by overloading the system or draining battery life. | -| Threat type | Denial of service | -| Vulnerabilities | Vulnerabilities in data sources | -| Impact type | Availability | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Trained ML model [ASSET-D-26],
Near-RT-RIC SW [ASSET-C-02],
Non-RT-RIC SW [ASSET-C-11],
AAL software [ASSET-C-29],
Hardware accelerator device firmware [ASSET-C-30] | - -3 - -4 - -#### 7.4.6.13 Evasion attack - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-EV-01 | -| Threat title | Grey-box based Data Evasion | -| Threat description | Possibility to tamper with the input to AI ML application during the inference phase in the Near-RT RIC or Non-RT RIC (model, model parameters, etc.) for example the model's gradient | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in the input APIs of the AI/ML model application
Vulnerabilities in the source of input data used by AI/ML for inferences | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11] | - -5 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-EV-02 | -| Threat title | White-box based data evasion attacks | -| Threat description | An attacker has complete knowledge of the AI/ML models and algorithms in use, including configurable parameters such as thresholds and hyper-parameters. By calculating the gradients of the classification loss with respect to the input sample, the attacker manipulates the input to maximize the classification loss | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in the input APIs of the AI ML model application
Vulnerabilities in the source of input data used by AI ML for inferences | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11] | - -1 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-AIML-EV-03 | -| Threat title | Black-box based data evasion attacks | -| Threat description | An attacker can interact with a trained ML model by querying it on various data samples and obtaining the model's predictions and estimating the gradients of the classification loss with respect to the input sample with no prior knowledge of the AI/ML algorithm, or the parameters being used. | -| Threat type | Tampering | -| Vulnerabilities | Vulnerabilities in the input APIs of the AI ML model application
Vulnerabilities in the source of input data used by AI ML for inferences | -| Impact type | Integrity | -| Affected Assets | Database holding data from xApp applications and E2 Node [ASSET-D-10],
Training or test data sets collected externally or internally [ASSET-D-25],
Trained ML model [ASSET-D-26],
Near-RT RIC [ASSET-C-02],
Non-RT RIC [ASSET-C-11] | - -2 - -3 - -### 7.4.7 Protocol Stack Threats - -4 - -The A1 and R1 interfaces use the REST protocol stack shown in the figure below. The transport network layer is built on IP transport. TCP provides the communication service at the transport layer. HTTP is the application-level protocol used providing reliable transport of messages. TLS provides secure HTTP connections for secure transport of messages. The application layer protocol is based on a RESTful approach with transfer of JSON formatted policy statements. Each of these protocols has known vulnerabilities that can be exploited by a malicious actor. - -5 -6 -7 -8 -9 -10 - -| | | -|------------------|------| -| Data Interchange | JSON | -| Application | HTTP | -| Security | TLS | -| Transport Layer | TCP | -| Network layer | IP | -| Data Link Layer | L2 | -| Physical Layer | L1 | - -11 - -12 - -**Figure Threat model-14 : REST Protocol Stack for the A1 and R1 Interfaces** - -13 - -| | | -|---------------------|---------------------------------------------------------------------------------------------------| -| Threat ID | T-ProtocolStack-01 | -| Threat title | REST API Exploits | -| Threat | REST API common attacks include injection, cross site scripting, and DoS attacks that can exploit | - -| | | -|--------------------|--------------------------------------------------------------------------------------------| -| description | common vulnerabilities if proper controls are not used to protect against vulnerabilities. | -|--------------------|--------------------------------------------------------------------------------------------| - -1 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------| -| Threat ID | T-ProtocolStack-02 | -| Threat title | REST API – Broken Object Level Authorization | -| Threat description | The REST API can be exploited to expose object identifiers without proper authorization checks. | - -2 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-ProtocolStack-03 | -| Threat title | JSON Exploits | -| Threat description | JSON attacks include injection, deserialization, web token, and cross site scripting attacks that can exploit common vulnerabilities if proper controls are not used to protect against vulnerabilities. | - -3 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-ProtocolStack-04 | -| Threat title | HTTP Exploits | -| Threat description | DDoS attacks include HTTP GET Flood, Garbage Flood, and Reverse Bandwidth Floods. Other well known HTTP attacks include injection attacks, such as Cross-Site Scripting (XSS) and SQL injection. | - -4 - -| | | -|---------------------------|-------------------------------------------------------------------| -| Threat ID | T-ProtocolStack-05 | -| Threat title | TCP Volumetric DDoS | -| Threat description | TCP DDoS attacks include TCP SYN Flood, ACK Flood, and RST Flood. | - -5 - -### 7.4.8 SMO Threats - -6 - -#### 7.4.8.1 General SMO Threats - -7 - -8 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-01 | -| Threat title | External attacker exploits authentication weakness on SMO | -| Threat description | An external attacker can exploit the improper/missing authentication weakness on SMO functions. If the authentication of O-RAN subjects on A1, O1, O2, and External interfaces on SMO is not supported or not properly implemented, those interfaces without proper credentials could be exploited to gain access to the SMO. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | SMO | - -9 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-02 | -| Threat title | External attacker exploits authorization weakness on SMO | -| Threat description | An external attacker can exploit the improper/missing authorization weakness on SMO functions. A malicious external entity on A1, O1, O2, and External interfaces without authorization or with an | - -| | | -|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | incorrect access token may invoke the SMO functions. The data at rest related to that function will be leaked to the attacker. In addition, an attacker can be able to perform certain actions, e.g. disclose O-RAN sensitive information or alter O-RAN components. | -| Threat type | Elevation of Privilege, Information Disclosure | -| Impact type | Authorization. Confidentiality | -| Affected Asset | SMO | - -1 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-03 | -| Threat title | External Overload DoS attack targeted at SMO | -| Threat description | Overload situation could appear in the case of DoS attack or increased traffic on externally facing interfaces. Inability to mitigate traffic volumetric attacks on an external interface affects availability of SMO data and functions. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | SMO | - -2 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-04 | -| Threat title | Internal attacker exploits authentication weakness on a SMO function | -| Threat description | An internal attacker can exploit the improper/missing authentication weakness on SMO functions. If the authentication of internal interfaces (e.g. Internal Message Bus and R1) on SMO is not supported or not properly implemented, those interfaces without credentials could be exploited to gain access to the SMO. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | SMO | - -3 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-05 | -| Threat title | Internal attacker exploits authorization weakness on a SMO function | -| Threat description | An internal attacker can exploit the improper/missing authorization weakness on SMO functions. Malicious internal entities without authorization or with an incorrect access token may invoke the SMO functions. The data at rest related to these functions will be leaked to the attacker. In addition, an attacker can be able to perform certain actions, e.g. disclose O-RAN sensitive information or alter O-RAN components. | -| Threat type | Elevation of Privilege, Information Disclosure | -| Impact type | Authorization | -| Affected Asset | SMO | - -4 - -| | | -|---------------------|--------------------------------------------------------| -| Threat ID | T-SMO-06 | -| Threat title | Internal Overload DoS attack targeted at SMO functions | - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat description | Overload situation could appear in the case of DoS attack or increased traffic on internal SMO interfaces. Inability to mitigate traffic volumetric attacks on an external interface affects availability of SMO data and functions. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | SMO | - -1 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-07 | -| Threat title | Internal DoS attack disables internal SMO function(s) or process(es) | -| Threat description | Internal malicious actor exploits a vulnerability or escalates privilege to execute a DoS attack by disabling one or more SMO processes or functions. Inability to detect and report such events affects availability of SMO functions. | -| Threat type | Denial of Service, Escalation of Privilege | -| Impact type | Availability | -| Affected Asset | SMO | - -2 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-08 | -| Threat title | Attacker exploits insecure API to gain access to SMO | -| Threat description | An insecure API may allow access to a system for an attacker to conduct remote code execution or an advanced persistent threat | -| Threat type | Tampering, Information Disclosure, Escalation of Privilege | -| Impact type | Integrity, Confidentiality, Authorization | -| Affected Asset | SMO | - -3 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-09 | -| Threat title | Sensitive data in transit is exposed to an internal attacker | -| Threat description | Unprotected data transferred between internal SMO functions is disclosed to an internal threat actor | -| Threat type | Information Disclosure | -| Impact type | Confidentiality | -| Affected Asset | SMO | - -4 - -| | | -|---------------------|------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-10 | -| Threat title | Sensitive data at rest is exposed to an internal attacker | -| Threat | Unprotected data stored on the SMO is disclosed to an internal threat actor that has gain authorized | - -| | | -|-----------------------|-------------------------------------| -| description | access through privilege escalation | -| Threat type | Information Disclosure | -| Impact type | Confidentiality | -| Affected Asset | SMO | - -1 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-11 | -| Threat title | AI/ML poisoning by internal attacker | -| Threat description | Internal attacker gains authorized access exploited to poison AI/ML training data, or the AI/ML models, stored in the SMO to influence insights. | -| Threat type | Tampering | -| Impact type | Integrity | -| Affected Asset | SMO | - -2 - -3 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-12 | -| Threat title | AI/ML exposure on external entity | -| Threat description | An external attacker can gain access to external entities to view or modify sensitive data AI/ML data, or models, transferred between the external function and SMO via external interfaces (e.g., EI, Human-Machine, A1, O1) | -| Threat type | Information disclosure, Tampering | -| Impact type | Confidentiality, Integrity | -| Affected Asset | SMO | - -4 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-13 | -| Threat title | Malicious actor views local logs | -| Threat description | Malicious actor accesses locally stored logs in the SMO to perform reconnaissance to collect sensitive or private information. | -| Threat type | Information disclosure | -| Impact type | Confidentiality | -| Affected Asset | SMO | - -5 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-14 | -| Threat title | Malicious actor modifies local log entries | -| Threat description | Malicious actor accesses locally stored logs in the SMO to modify entries to hide presence or cause confusion. | -| Threat type | Tampering | - -| | | -|-----------------------|-----------| -| Impact type | Integrity | -| Affected Asset | SMO | - -1 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-15 | -| Threat title | Malicious actor deletes local log entries | -| Threat description | Malicious actor accesses locally stored logs in the SMO to delete entries to hide presence or cause confusion. | -| Threat type | Tampering | -| Impact type | Integrity | -| Affected Asset | SMO | - -2 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-16 | -| Threat title | Malicious actor intercepts exports of local logs | -| Threat description | Malicious actor gains access to an external interface to intercept data in transit as logs are transferred from the SMO to a remote server/external entity. | -| Threat type | Information disclosure | -| Impact type | Confidentiality | -| Affected Asset | SMO | - -3 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-17 | -| Threat title | Malicious external actor gains unauthorized access to logs | -| Threat description | Malicious external actor gains unauthorized access to stored logs to view, modify, and delete | -| Threat type | Elevation of Privilege | -| Impact type | Confidentiality | -| Affected Asset | SMO | - -4 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-18 | -| Threat title | Malicious internal actor gains authorized access to logs | -| Threat description | Malicious internal actor gains authorized access to stored logs to view, modify, and delete. | -| Threat type | Elevation of Privilege | -| Impact type | Authorization | -| Affected Asset | SMO | - -##### 1 2 3 7.4.8.2 SMO Threats at O2 interface - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-19 | -| Threat title | Internal attacker exploits O2 interface to view data in transit between SMO and O-Cloud | -| Threat description | If the O2 interface is not properly confidentiality protected, an internal attacker can perform a man-in-the-middle attack to view data in transit. | -| Threat type | Information disclosure | -| Impact type | Confidentiality | -| Affected Asset | O2 interface | - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-20 | -| Threat title | Internal attacker exploits O2 interface to modify data in transit between SMO and O-Cloud | -| Threat description | If the O2 interface is not properly integrity protected, an internal attacker can perform a man-in-the-middle attack to modify data in transit. | -| Threat type | Tampering | -| Impact type | Integrity | -| Affected Asset | O2 interface | - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-21 | -| Threat title | Internal attacker uses O2 interface via SMO to exploit API vulnerability to gain access to O-Cloud infrastructure | -| Threat description | If the O2 interface uses an API with a known vulnerability that is not properly protected or patched, an attacker can exploit it to gain access to the O-Cloud infrastructure from the SMO. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | O-Cloud | - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-22 | -| Threat title | Internal attacker floods O2 interface via SMO to cause DDoS on O-Cloud infrastructure | -| Threat description | If the O2 interface is not protected, an internal attacker on the SMO can flood the O2 interface to overload the O-Cloud. This can prevent legitimate messages from reaching the O-Cloud or cause heavy processing at the O-Cloud, resulting in performance degradation. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected | O-Cloud | - -| | | -|--------------|--| -| Asset | | -|--------------|--| - -1 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-23 | -| Threat title | External attacker uses O2 interface via O-Cloud to exploit API vulnerability to gain access to SMO | -| Threat description | If the O2 interface uses an API with a known vulnerability that is not properly protected or patched, an attacker can exploit it to gain access to the SMO from the O-Cloud infrastructure. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | SMO | - -2 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-24 | -| Threat title | External attacker floods O2 interface via O-Cloud to cause DDoS on SMO | -| Threat description | If the O2 interface is not protected, an external attacker in the O-Cloud can flood the O2 interface to overload the SMO. This can prevent legitimate messages from reaching the SMO or cause heavy processing at the SMO, resulting in performance degradation or outage of the SMO. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | SMO | - -3 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-25 | -| Threat title | External attacker uses O2 interface via O-Cloud to gain authorized access to sensitive data-at-rest at the SMO | -| Threat description | If the SMO is not protected, an external attacker at the O-Cloud can use the O2 interface to gain authorized access to the SMO to view data-at-rest. | -| Threat type | Elevation of Privilege | -| Impact type | Authorization | -| Affected Asset | SMO | - -4 - -5 - -#### 7.4.8.3 SMO Threats at External interfaces - -7 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-26 | -| Threat title | External attacker exploits External interface to view data in transit between SMO and external service | -| Threat description | If an External interface is not properly confidentiality protected, an external attacker can perform a man-in-the-middle attack to view data in transit. | -| Threat type | Information disclosure | - -| | | -|-----------------------|--------------------| -| Impact type | Confidentiality | -| Affected Asset | External interface | - -1 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-27 | -| Threat title | External attacker exploits External interface to modify data in transit between SMO and external service | -| Threat description | If an External interface is not properly integrity protected, an external attacker can perform a man-in-the-middle attack to modify data in transit. | -| Threat type | Tampering | -| Impact type | Integrity | -| Affected Asset | External interface | - -2 - -3 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-28 | -| Threat title | External attacker uses External interface to exploit API vulnerability to gain access to SMO | -| Threat description | If an External interface uses an API with a known vulnerability that is not properly protected or patched, an attacker can exploit it to gain access to the SMO. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | SMO | - -4 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-29 | -| Threat title | External attacker floods External interface to cause DDoS at SMO | -| Threat description | If the External interface is not protected, an external attacker can flood an External interface to overload the SMO. This can prevent legitimate messages and data from reaching the SMO or cause heavy processing at the SMO, resulting in performance degradation or outage of the SMO. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | SMO | - -5 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-30 | -| Threat title | External attacker uses External interface to gain access to sensitive data-at-rest at the SMO | -| Threat description | If the SMO is not protected, an external attacker can use the External interface to gain authorized access to the SMO to view data-at-rest. | -| Threat type | Elevation of Privilege | -| Impact type | Authorization | - -1 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Affected Asset | SMO | -| Threat ID | T-SMO-31 | -| Threat title | External attacker poisons External AI/ML data to corrupt SMO | -| Threat description | External data sources may be outside the control of the stakeholder(s) responsible for the O-RAN deployment. The stakeholder for an External data source could fail to provide proper security controls to protect data consumed by the SMO. If an external attacker were to gain access to AI/ML data, it could be corrupted and then be used at the SMO. | -| Threat type | Tampering | -| Impact type | Integrity | -| Affected Asset | SMO | - -2 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-32 | -| Threat title | External attacker poisons External Enrichment Information data sources to corrupt SMO | -| Threat description | External data sources may be outside the control of the stakeholder(s) responsible for the O-RAN deployment. The stakeholder for an External data source could fail to provide proper security controls to protect data consumed by the SMO. If an external attacker were to gain access to External Enrichment Information, it could be corrupted and then be used at the SMO. | -| Threat type | Tampering | -| Impact type | Integrity | -| Affected Asset | SMO | - -3 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-33 | -| Threat title | rApp floods SME | -| Threat description | Misbehaving 3rd-party rApp, maliciously or non-maliciously, floods internal SMOS Communication interface targeting the SME to bring a volumetric DDoS attack against the SMO. | -| Threat type | Denial of Service | -| Vulnerabilities | No flood protection | -| Impact type | Availability | -| Affected Asset | SMO, SME | - -4 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SMO-34 | -| Threat title | External Consumer floods SME | -| Threat description | External Source, maliciously or non-maliciously, floods the External interface targeting the SME to bring a volumetric DDoS attack against the SMO. | -| Threat type | Denial of Service | -| Vulnerabilities | No flood protection | - -| | | -|-----------------------|--------------| -| Impact type | Availability | -| Affected Asset | SMO, SME | - -1 - -2 - -### 7.4.9 Threats against Shared O-RU - -3 - -4 - -Threat Analysis tables are provided for each of the identified Shared O-RU threats in the clauses below. The Shared O-RU Threats are classified into 6 threat groups: - -5 - -6 - -7 - -8 - -9 - -10 - -11 - -- Lateral Movement Between Network Functions -- Physical Port Access Threats -- Data Access Threats -- Availability Threats -- Configuration Threats -- Resiliency Threats - -12 - -13 - -Use of the term “MNO Tenant” or “Tenant” refers to a “Shared Resource Operator (SRO)” as defined in [i.27]. - -14 - -#### 7.4.9.1 Lateral Movement Between Network Functions - -15 - -This clause provides threat analysis tables for threats to access between Shared O-RU network functions. - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-01 | -| Threat title | O-DU Tenant accesses O-DU Host | -| Threat description | The O-DU Tenant accesses the O-DU Host through the Shared O-RU. Weak authentication can be exploited by a tenant to move laterally across the deployment. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | O-DU Host | - -16 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-02 | -| Threat title | O-DU Host accesses O-DU Tenant | -| Threat description | The O-DU Host accesses the O-DU Tenant through the Shared O-RU. Weak authentication can be exploited by a host to move laterally across the deployment. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | O-DU Tenant | - -17 - -| | | -|------------------|----------------| -| Threat ID | T-SharedORU-03 | -|------------------|----------------| - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat title | O-DU Tenant accesses O-DU Tenant | -| Threat description | An O-DU Tenant accesses another O-DU Tenant through the Shared O-RU supporting multiple tenants. Weak authentication can be exploited by a tenant to move laterally across the deployment. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | O-DU Tenant | - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-04 | -| Threat title | Password Attack on OFH M-Plane | -| Threat description | Use of single-factor authentication with password on the Open Fronthaul M-Plane can be exploited by an internal malicious actor to gain access to the Shared O-RU. The attack can be a brute-force attack or stolen password. There is increased risk of password attack in a multi-tenant environment. The internal malicious actor may be the Host MNO, a Tenant MNO, or a 3rd-party. [i.9] | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | Shared O-RU, O-DU Host, O-DU Tenant | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-05 | -| Threat title | Untrusted peering to O-DU | -| Threat description | Attacker exploits weak authentication on the O-DU to establish a session with a malicious app masquerading as a Shared O-RU. From the O-DU, a malicious actor can move laterally across Shared O-RUs and northbound to the O-CU and SMO. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | O-DU Host, O-DU Tenant | - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-06 | -| Threat title | Untrusted peering to the Shared O-RU | -| Threat description | Attacker exploits weak authentication on the Shared O-RU to establish session with a malicious app masquerading as a O-DU Host or O-DU Tenant | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | Shared O-RU | - -| | | -|---------------------|------------------------------| -| Threat ID | T-SharedORU-07 | -| Threat title | Untrusted peering to the SMO | - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------| -| Threat description | Attacker exploits weak authentication on the SMO to establish session with a malicious app masquerading as a Shared O-RU. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | SMO Host, SMO Tenant | - -1 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-08 | -| Threat title | SMO Tenant accesses SMO Host | -| Threat description | The SMO Tenant accesses the SMO Host through the Shared O-RU. Weak authentication can be exploited by a tenant to move laterally across the deployment. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | SMO Host | - -2 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-09 | -| Threat title | SMO Host accesses SMO Tenant | -| Threat description | The SMO Host accesses the SMO Tenant through the Shared O-RU. Weak authentication can be exploited by a host to move laterally across the deployment. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | SMO Tenant | - -3 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-10 | -| Threat title | O-DU Host accesses O-CU Tenant | -| Threat description | The O-DU Host accesses the O-CU Tenant through the Shared O-RU. Weak authentication can be exploited by a host to move laterally across the deployment. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | O-CU Tenant | - -4 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-11 | -| Threat title | O-DU Tenant accesses O-CU Host | -| Threat description | The O-DU Tenant accesses the O-CU Host through the Shared O-RU. Weak authentication can be exploited by a host to move laterally across the deployment. | -| Threat type | Spoofing | -| Impact | Authenticity | - -| | | -|-----------------------|-----------| -| type | | -| Affected Asset | O-CU Host | - -1 -2 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-12 | -| Threat title | O-DU Tenant accesses O-CU Tenant | -| Threat description | The O-DU Tenant accesses another O-CU Tenant through the Shared O-RU supporting multiple tenants. Weak authentication can be exploited by a host to move laterally across the deployment. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | O-CU Tenant | - -3 -4 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-13 | -| Threat title | SMO Host accesses O-CU Tenant | -| Threat description | The SMO Host accesses the O-CU Tenant through the Shared O-RU. Weak authentication can be exploited by a host to move laterally across the deployment. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | O-CU Tenant | - -5 -6 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-14 | -| Threat title | SMO Tenant accesses O-CU Host | -| Threat description | The SMO Tenant accesses the O-CU Host through the Shared O-RU. Weak authentication can be exploited by a host to move laterally across the deployment. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | O-CU Host | - -7 - -#### 7.4.9.2 Physical Port Access Threats - -9 - -This clause provides threat analysis tables for physical port access threats to Shared O-RU. - -10 - -| | | -|---------------------|-------------------------------------------------| -| Threat ID | T-SharedORU-15 | -| Threat title | Physical port access to Shared O-RU Host/Tenant | - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat description | A host, tenant, or third-party gains physical port connectivity to the Shared O-RU. With this physical access the actor exploits weak physical layer authentication to gain access to the Shared O-RU. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | Shared O-RU | - -1 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-16 | -| Threat title | Physical port access to O-DU Host/Tenant | -| Threat description | A host, tenant, or third-party gains physical port connectivity to a O-DU Host or O-DU Tenant. With this physical access the actor exploits weak physical layer authentication to gain access to the O-DU. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | O-DU Host, O-DU Tenant | - -2 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-17 | -| Threat title | Physical port access to O-CU Host/Tenant | -| Threat description | A host, tenant, or third-party gains physical port connectivity to a O-CU Host or O-CU Tenant. With this physical access the actor exploits weak physical layer authentication to gain access to the O-CU. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | O-CU Host, O-CU Tenant | - -3 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-18 | -| Threat title | Malicious User Login Attempt to SMO Host/Tenant | -| Threat description | The attacker attempts to access the SMO Host or SMO tenant through a management interface. The attacker may be an internal or external actor. Weak account management and/or authentication can be exploited to gain access to move laterally across the deployment for nefarious purposes such as reconnaissance or damage. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | SMO Host, SMO Tenant | - -4 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-19 | -| Threat title | Malicious User Login Attempt to O-CU Host/Tenant | -| Threat description | The attacker attempts to access the O-CU Host or O-CU Tenant through a management interface. The attacker may be an internal or external actor. Weak account management and/or authentication can be exploited to gain access to move laterally across the deployment for nefarious purposes such as | - -| | | -|-----------------------|---------------------------| -| | reconnaissance or damage. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | O-CU Host, O-CU Tenant | - -1 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-20 | -| Threat title | Malicious User Login Attempt to O-DU Host/Tenant | -| Threat description | The attacker attempts to access the O-DU Host or O-DU Tenant through a management interface. The attacker may be an internal or external actor. Weak account management and/or authentication can be exploited to gain access to move laterally across the deployment for nefarious purposes such as reconnaissance or damage. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | O-DU Host, O-DU Tenant | - -2 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-21 | -| Threat title | Malicious User Login Attempt to Shared O-RU Host/Tenant | -| Threat description | The attacker attempts to access the O-RU Host or O-RU Tenant through a management interface. The attacker may be an internal or external actor. Weak account management and/or authentication can be exploited to gain access to move laterally across the deployment for nefarious purposes such as reconnaissance or damage. | -| Threat type | Spoofing | -| Impact type | Authenticity | -| Affected Asset | Shared O-RU | - -3 - -#### 7.4.9.3 Data Access Threats - -4 - -This clause provides threat analysis tables for threats to Shared O-RU data access. - -5 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-22 | -| Threat title | Unauthorized internal threat actor gains access to data in Shared O-RU | -| Threat description | Malicious internal threat actor exploits compromised credentials or weak or misconfigured authorization to gain access to view or modify sensitive data-at-rest or data-in-use in the Shared O-RU. | -| Threat type | Elevation of Privilege | -| Impact type | Authorization | -| Affected Asset | Shared O-RU | - -6 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-23 | -| Threat title | Unauthorized external threat actor gains access to data in Shared O-RU | -| Threat description | Malicious external threat actor exploits compromised credentials or weak or misconfigured authorization to gain access to view or modify sensitive data-at-rest or data-in-use in the Shared O-RU. | -| Threat type | Elevation of Privilege | -| Impact type | Authorization | -| Affected Asset | Shared O-RU | - -1 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-24 | -| Threat title | Data exposure at Shared O-RU | -| Threat description | Data-at-rest on the Shared O-RU is exposed to a tenant. Attacker exploits weak confidentiality protection to view data owned by the MNO Host or a MNO Tenant. | -| Threat type | Information Disclosure | -| Impact type | Confidentiality | -| Affected Asset | Shared O-RU | - -2 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-25 | -| Threat title | Shared O-RU data exposure at SMO | -| Threat description | Data-at-rest on the SMO related to a Shared O-RU is exposed to an unauthorized tenant / SMO user. Attacker exploits weak confidentiality protection to view data owned by the MNO Host or a MNO Tenant of a shared O-RU. | -| Threat type | Information Disclosure | -| Impact type | Confidentiality | -| Affected Asset | Shared O-RU | - -3 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-26 | -| Threat title | Shared O-RU data exposure at O-DU | -| Threat description | Data-at-rest on the O-DU related to a Shared O-RU is exposed to an unauthorized tenant. Attacker exploits weak confidentiality protection to view data owned by the MNO Host or a MNO Tenant of a shared O-RU. | -| Threat type | Information Disclosure | -| Impact type | Confidentiality | -| Affected Asset | Shared O-RU | - -4 - -| | | -|---------------------|------------------------------------------------------------------| -| Threat ID | T-SharedORU-27 | -| Threat title | Exposed data in transit between Shared O-RU and O-DU Host/Tenant | - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat description | Data-in-transit between the Shared O-RU and an O-DU Host or O-DU Tenant could be exposed to another MNO or malicious threat actor. Weak confidentiality protection of data-in-transit allows the host, tenant, or actor to view intercepted data owned by the MNO Host or a MNO Tenant. | -| Threat type | Information Disclosure | -| Impact type | Confidentiality | -| Affected Asset | Shared O-RU, M-Plane, CUS-Plane | - -1 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-28 | -| Threat title | Exposed data in transit between Shared O-RU and SMO Host/Tenant | -| Threat description | Data-in-transit between the Shared O-RU and a SMO Host or SMO Tenant could be exposed to another MNO or malicious threat actor. Weak confidentiality protection of data-in-transit allows the host, tenant, or actor to view intercepted data owned by the MNO Host or a MNO Tenant. | -| Threat type | Information Disclosure | -| Impact type | Confidentiality | -| Affected Asset | Shared O-RU, O1 | - -2 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-43 | -| Threat title | Eavesdropping of unprotected CUSM-plane data within shared O-RU | -| Threat description | The SMO assigns the role of Host and MNO SRO(s). The tenant maliciously or intended is obtaining access to transport protocol stack and is therefore able to eavesdrop sensitive data from neighbor tenants and the host. The tenant may have capability for sniffing/capturing of CUSM-plane data. | -| Threat type | Information Disclosure | -| Impact type | Confidentiality | -| Affected Asset | Shared O-RU | - -3 - -4 - -#### 7.4.9.4 Availability Threats - -5 - -This clause provides threat analysis tables for availability threats to Shared O-RU. - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-29 | -| Threat title | Modify/Delete OFH C-Plane messages | -| Threat description | A Host MNO, Tenant MNO, or 3 rd -party, modifies or deletes control plane messages on the OFH C-Plane between the Shared O-RU and Host O-DU or Tenant O-DU. This type of integrity attack can also result in an availability attack. | -| Threat type | Tampering | -| Impact type | Integrity, Availability | - -| | | -|-----------------------|------------------------------------------------| -| Affected Asset | Shared O-RU, O-DU Host, O-DU Tenant, CUS-Plane | -|-----------------------|------------------------------------------------| - -1 -2 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-30 | -| Threat title | Clock hijacking on OFH S-Plane | -| Threat description | A Host MNO, Tenant MNO, or 3 rd -party takes the role of Grand Master clock on the S-Plane to degrade performance on the U-Plane. This type of authorization exploit can also result in an availability attack. | -| Threat type | Elevation of Privilege | -| Impact type | Authorization, Availability | -| Affected Asset | Shared O-RU, O-DU Host, O-DU Tenant, CUS-Plane | - -3 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-31 | -| Threat title | Parameter conflicts at Shared O-RU | -| Threat description | O-DU Host and O-DU Tenants may force conflicting parameter settings at the Shared O-RU that can degrade performance or cause an outage. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | Shared O-RU | - -4 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-32 | -| Threat title | Volumetric DDoS attack from O-DU targeting Shared O-RU | -| Threat description | An O-DU Host or O-DU Tenant maliciously or unintentionally sends a high-rate of malformed, mis-sequenced, invalid, or valid packets over the Open Fronthaul interface to the Shared O-RU. This kind of attack can cause a Denial of Service on the Shared O-RU. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | Shared O-RU, M-Plane, CUS-Plane | - -5 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-33 | -| Threat title | Volumetric DDoS attack from SMO targeting Shared O-RU | -| Threat description | The SMO Host maliciously or unintentionally sends a high-rate of malformed, mis-sequenced, invalid, or valid packets over the Open Fronthaul interface to the Shared O-RU. This kind of attack can cause a Denial of Service on the Shared O-RU. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | Shared O-RU, O1 | - -1 -2 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-34 | -| Threat title | Volumetric DDoS attack targeting O-DU | -| Threat description | Shared O-RU maliciously or unintentionally sends a high-rate of malformed, mis-sequenced, invalid, or valid packets over the Open Fronthaul interface to the O-DU Host or O-DU Tenant. This kind of attack can cause a Denial of Service on the O-DU. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | O-DU Host, O-DU Tenant, CUS-Plane, M-Plane | - -3 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-35 | -| Threat title | Shared O-RU initialization hijacking by DHCP compromise | -| Threat description | Shared O-RU bootup and initialization sequence depends on parameters passed to it via DHCP options. An attacker can compromise DHCP server and use it to hijack the O-RU and prevent Shared O-RU from reaching carrier-active state. This kind of attack can cause a Denial of Service on the shared O-RU. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | Shared O-RU | - -4 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-36 | -| Threat title | Shared O-RU M-plane hijacking by DNS compromise | -| Threat description | Shared O-RU M-plane initialization depends on DNS, if FQDN is returned as the NETCONF controller of shared O-RU during its initialization. The name resolution of FQDN can be manipulated by an attacker using a compromised DNS server and prevent Shared O-RU from reaching carrier-active state due to unavailability of carrier configuration. This kind of attack can cause a Denial of Service on the shared O-RU. | -| Threat type | Denial of Service | -| Impact type | Availability | -| Affected Asset | Shared O-RU | - -5 - -6 - -#### 7.4.9.5 Configuration Threats - -7 - -This clause provides threat analysis tables for configuration threats to Shared O-RU. - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-37 | -| Threat title | Misconfiguration of MNO Host Role | -| Threat description | The SMO assigns the role of MNO Host and MNO SRO(s). The assignment of Host role to the wrong SRO can expose data. A threat actor could exploit an incorrectly assigned role of Host to control function of the Shared O-RU | - -| | | -|-----------------------|-------------------------------------------| -| Threat type | Information Disclosure, Denial of Service | -| Impact type | Confidentiality, Availability | -| Affected Asset | Shared O-RU | - -1 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-38 | -| Threat title | Incorrect Assignment of Spectrum Resources | -| Threat description | Shared O-RU is responsible for assignment and control of spectrum resources, including component carrier and frequencies within a carrier. Tenant access to the wrong resources, due to malicious intent or could be exploited to gain access to information. | -| Threat type | Spoofing | -| Impact type | Authentication | -| Affected Asset | Shared O-RU | - -2 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-39 | -| Threat title | Chain of Trust in a Multi-Tenant Environment | -| Threat description | The Chain of Trust is a certificate-based chain used to authenticate an entity. The Chain of Trust is established by validating the hardware and software for the entity up to the root certificate as the trust anchor. The Shared O-RU mutually authenticates O-DU Hosts and O-DU Tenants. Certificates from O-DU tenants must be validated as trustworthy. Malicious actors can exploit untrustworthy certificates to gain access to the Shared O-RU. | -| Threat type | Spoofing | -| Impact type | Authentication | -| Affected Asset | Shared O-RU, O-DU Host, O-DU Tenant, O-CU Host, O-CU Tenant, SMO Host, SMO Tenant | - -3 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-40 | -| Threat title | Hijack of MNO Host Role | -| Threat description | The SMO assigns the role of MNO Host and MNO SRO(s). A tenant may maliciously or unintentionally obtain the host role. The elevation of privilege would enable the tenant, acting as host, to have authorized access on the Shared O-RU to sensitive data, credentials, and system privileges. | -| Threat type | Elevation of Privilege | -| Impact type | Authorization | -| Affected Asset | Shared O-RU | - -4 - -| | | -|---------------------|-------------------------------------------| -| Threat ID | T-SharedORU-41 | -| Threat title | Not Released Host Role (Host Role resume) | - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat description | The SMO assigns the role of Host and MNO SRO(s). The tenant maliciously or intended is obtaining the host role, and implicit has obtained elevated privileges which could be used to drive wrong things, like obtaining of sensitive data and/or driving DoS. The tenant is not releasing the host role and/or the tenant is reusing known sensitive information and is driving wrong things. How to avoid that a tenant who has become once in his/her life a host is obtaining information that could be misused now and in the future. | -| Threat type | Elevation of Privilege | -| Impact type | Authorization | -| Affected Asset | Shared O-RU | - -1 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-42 | -| Threat title | Misuse of “sudo” privileges | -| Threat description | The SMO assigns the role of Host and MNO SRO(s). The tenant maliciously or intended is obtaining the host role, and implicit has obtained elevated privileges which could be used to drive wrong things, like obtaining of sensitive data and/or driving DoS. How to avoid that any of the tenants can misuse the “sudo” privileges. This includes the default credentials of a shared O-RU. | -| Threat type | Elevation of Privilege | -| Impact type | Authorization | -| Affected Asset | Shared O-RU | - -2 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-55 | -| Threat title | Set Incorrect Array-Carrier configuration on O-DU (Standby) | -| Threat description | Threat actor spoofs SMO to set or modify the pre-configured array-carrier configuration on the O-DU in Standby state. | -| Threat type | Spoofing | -| Impact type | Authentication | -| Affected Asset | O-DU, O1 interface | - -3 - -| | | -|---------------------------|----------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-56 | -| Threat title | Modify Array-Carrier pre-configuration on Shared O-RU | -| Threat description | Threat actor can gain access to Shared O-RU to modify its pre-configured array-carrier | -| Threat type | Elevation of Privilege | -| Impact type | Authorization | -| Affected Asset | Shared O-RU | - -4 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-57 | -| Threat title | Modify/Inject M-Plane messages with Array-Carrier configuration | -| Threat description | Threat actor Modifies/Injects M-Plane messages with Array-Carrier configuration sent to the Shared O-RU. | -| Threat type | Tampering | -| Impact type | Integrity | -| Affected Asset | Shared O-RU, M-Plane | - -1 - -2 - -#### 7.4.9.6 Resiliency Threats - -3 - -This clause provides threat analysis tables for threats introduced by the O-DU Resiliency use case. - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-52 | -| Threat title | Thrashing O-DU Failovers | -| Threat description | Threat actor spoofs SMO to cause O-DU-1 and O-DU-2 to thrash between Active state and Standby state | -| Threat type | Spoofing | -| Impact type | Authentication | -| Affected Asset | O-DU, O1 interface | - -4 - -| | | -|---------------------------|--------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-53 | -| Threat title | Dual (Dueling) Active O-DUs | -| Threat description | Threat actor spoofs SMO to cause O-DU-1 and O-DU-2 to both be in Active state. | -| Threat type | Spoofing | -| Impact type | Authentication | -| Affected Asset | O-DU, O1 interface | - -5 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-SharedORU-54 | -| Threat title | Modify/Inject O1 messages at the SMO | -| Threat description | Threat actor spoofs O-DU to modify, inject, flood O1 messages to the SMO to prevent SMO detection of O-DU failure. | -| Threat type | Tampering | -| Impact type | Integrity | -| Affected Asset | SMO, O1 interface | - -1 - -### 7.4.10 OAuth2.0 Threats - -#### 7.4.10.1 General OAuth2.0 Threats - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-01 | -| Threat title | Obtaining client secrets, IETF RFC 6819 [i.8], clause 4.1.1 | -| Threat description | A malicious actor may access the secrets and tokens of O-RAN architecture elements and use them to replay its refresh tokens and authorization codes. | -| Threat type | Information disclosure
Elevation of Privilege | -| Vulnerability | Unsecured tokens and secrets | -| Impact type | Confidentiality
Authorization | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -4 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-02 | -| Threat title | Obtaining refresh tokens, IETF RFC 6819 [i.8], clause 4.1.2 | -| Threat description | A malicious actor may get file system access of the local storage of O-RAN architecture elements and read the refresh tokens. A malicious actor may use the compromised refresh token for a malicious application. | -| Threat type | Information disclosure | -| Vulnerability | A new refresh token was not issued | -| Impact type | Confidentiality | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -5 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-03 | -| Threat title | Obtaining access tokens, IETF RFC 6819 [i.8], clause 4.1.3 | -| Threat description | Access tokens may be stolen by a malicious actor from the local storage if the O-RAN architecture element stores them in a local storage that is accessible to other O-RAN architecture elements or applications without proper access control. | -| Threat type | Elevation of Privilege | -| Vulnerability | Insufficient protection for credentials | -| Impact type | Authorization | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -6 - -| | | -|------------------|---------------------| -| Threat ID | T-OAuth-G-04 | -|------------------|---------------------| - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat title | Eavesdropping access tokens, IETF RFC 6819 [i.8], clause 4.3.1 | -| Threat description | A malicious actor may attempt to eavesdrop on access tokens in transit from the authorization server to the O-RAN architecture elements and applications | -| Threat type | Information disclosure | -| Vulnerability | Non authenticated, weakly or incorrectly authenticated communication channels | -| Impact type | Confidentiality | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -1 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-05 | -| Threat title | Disclosure of client credentials during transmission, IETF RFC 6819 [i.8], clause 4.3.3 | -| Threat description | A malicious actor may attempt to eavesdrop the transmission of O-RAN elements credentials between the application and authorization server during the O-RAN elements authentication process or during OAuth token requests. | -| Threat type | Information disclosure | -| Vulnerability | Non authenticated, weakly or incorrectly authenticated communication channels | -| Impact type | Confidentiality | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -2 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-06 | -| Threat title | Open redirectors on client, IETF RFC 6819 [i.8], clause 4.1.5 | -| Threat description | A malicious actor may use an open redirector operated by the O-RAN Applications to construct a redirect URI that will pass the authorization server validation but will send authorization code to an endpoint under the control of a malicious actor. | -| Threat type | Information disclosure | -| Vulnerability | Non authenticated, weakly or incorrectly authenticated communication channels | -| Impact type | Authenticity | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -3 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-07 | -| Threat title | Obtain a deployment-specific secret, IETF RFC 6819 [i.8], clause 4.1.1 | -| Threat description | An attacker may try to gain the secret for a O-RAN client installation, either from a resource server or O-RAN Applications. | -| Threat type | Spoofing | - -| | | -|-----------------------|------------------------------------------------------------------------------------------------------------------------| -| Vulnerability | malicious applications, insufficient access control | -| Impact type | Authenticity | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -1 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-08 | -| Threat title | Obtaining authorization by code substitution (OAuth Login), IETF RFC 6819 [i.8], clause 4.4.1.13 | -| Threat description | An attacker could attempt to log into an application using a victim's identity. Applications relying on identity data provided by an OAuth protected service API to login users are vulnerable to this threat. | -| Threat type | Information Disclosure | -| Vulnerability | Insufficient protection for credentials | -| Impact type | Authorization | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -2 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-09 | -| Threat title | Access token leak in transport/endpoints, IETF RFC 6819 [i.8], clause 4.4.2.1 | -| Threat description | A token may be eavesdropped by an attacker. The token is sent from the server to the client via a URI fragment of the redirect URI. If the communication is not secured or the endpoint is not secured, the token could be leaked by parsing the returned URI. | -| Threat type | Information Disclosure | -| Vulnerability | Non authenticated, weakly or incorrectly authenticated URI | -| Impact type | Authorization | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -3 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-10 | -| Threat title | Malicious client obtains existing authorization by fraud, IETF RFC 6819 [i.8], clause 4.2.3 | -| Threat description |

Authorization servers may wish to automatically process authorization requests from client that have been previously authorized by the user. When the user is redirected to the authorization server's end-user authorization endpoint to grant access, the authorization server detects that the user has already granted access to that particular client. Instead of prompting the user for approval, the authorization server automatically redirects the user back to the client.

A malicious client may exploit that feature and try to obtain such an authorization "code" instead of the legitimate client.

| -| Threat type | Spoofing
Repudiation | -| Vulnerability | Improper authorization process and lack of re-validating the authorization requests | - -| | | -|-----------------------|------------------------------------------------------------------------------------------------------------------------| -| Impact type | Authorization
Non repudiation | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -1 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-11 | -| Threat title | Malicious client obtains authorization, IETF RFC 6819 [i.8], clause 4.4.2.3 | -| Threat description | A malicious client may attempt to obtain a token by fraud. | -| Threat type | Spoofing
Repudiation | -| Vulnerability | Insufficient protection for credentials | -| Impact type | Authorization
Non repudiation | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -2 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-12 | -| Threat title | Accidental exposure of passwords at client site, IETF RFC 6819 [i.8], clause 4.4.3.1 | -| Threat description | If the client does not provide enough protection, an attacker could retrieve the passwords for a user. | -| Threat type | Information Disclosure | -| Vulnerability | Insufficient protection for credentials | -| Impact type | Authorization | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -3 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-13 | -| Threat title | Client obtains scopes without end-user authorization and possible misconfigurations, IETF RFC 6819 [i.8], clause 4.4.3.2 | -| Threat description | An O-RAN Application like an rApp or xApp intentionally or unintentionally obtains a token with scope unknown for, or unintended by, the resource owner. | -| Threat type | Tampering
Elevation of privilege | -| Vulnerability | misconfiguration | -| Impact type | Confidentiality
Authorization | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -4 - -| | | -|------------------|---------------------| -| Threat ID | T-OAuth-G-14 | -|------------------|---------------------| - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat title | Client obtains refresh token through automatic authorization, IETF RFC 6819 4.4.3.3 [i.8], clause 4.4.3.3 | -| Threat description | An O-RAN application like an rApp or xApp obtains intentionally or unintentionally a long-term authorization represented by a refresh token even if the resource owner did not intend so. | -| Threat type | Tampering
Elevation of privilege | -| Vulnerability | Improper authorization process and lack of re-validating the authorization requests | -| Impact type | Confidentiality
Authorization | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -1 - -| | | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-15 | -| Threat title | Eavesdropping refresh tokens from authorization server, IETF RFC 6819 [i.8], clause 4.5.1 | -| Threat description | An O-RAN Application like an rApp or xApp may eavesdrop on refresh tokens when they are transmitted from the authorization server to the client. | -| Threat type | Tampering
Elevation of privilege | -| Vulnerability | Non authenticated, weakly or incorrectly authenticated communication channels | -| Impact type | Confidentiality
Authorization | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -2 - -| | | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-16 | -| Threat title | Obtaining refresh token by online guessing, IETF RFC 6819 [i.8], clause 4.5.3 | -| Threat description | An O-RAN Application like an rApp or xApp may try to guess valid refresh token values and send it using the grant type "refresh_token" in order to obtain a valid access token. | -| Threat type | Tampering
Elevation of privilege | -| Vulnerability | Improper authorization process and lack of re-validating the authorization requests | -| Impact type | Confidentiality
Authorization | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -3 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-17 | -| Threat title | Refresh token phishing by counterfeit authorization server, IETF RFC 6819 [i.8], clause 4.5.4 | -| Threat description | An O-RAN Application like an rApp or xApp could obtain valid refresh tokens by proxying requests to the authorization server. | -| Threat type | Tampering | - -| | | -|-----------------------|------------------------------------------------------------------------------------------------------------------------| -| | Spoofing
Elevation of privilege | -| Vulnerability | Non authenticated, weakly or incorrectly authenticated communication channels | -| Impact type | Confidentiality
Authorization | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -1 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-18 | -| Threat title | Guessing access tokens, IETF RFC 6819 [i.8], clause 4.6.3 | -| Threat description | Access to a single user's data is possible where an attacker may place a malicious rApp or xApp and attempt to guess the access token values based on knowledge from other access tokens. | -| Threat type | Tampering
Elevation of privilege | -| Vulnerability | Insecure generation of access token | -| Impact type | Confidentiality
Authorization | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -2 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-19 | -| Threat title | Access token phishing by counterfeit resource server, IETF RFC 6819 [i.8], clause 4.6.4 | -| Threat description | An O-RAN Application like an rApp or xApp may send a valid access token to a counterfeit resource server where the server in turn uses that token to access other services on behalf of the resource owner. | -| Threat type | Tampering
Spoofing
Elevation of privilege | -| Vulnerability | Insufficient protection for credentials | -| Impact type | Confidentiality
Authorization | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -3 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-20 | -| Threat title | Abuse of token by legitimate resource server or client, IETF RFC 6819 [i.8], clause 4.6.5 | -| Threat description | An O-RAN legitimate resource server which is protecting the resources could use an access token to access another resource server. | -| Threat type | Tampering
Elevation of privilege | -| Vulnerability | insufficient protection for access control on resource server | -| Impact type | Confidentiality
Authorization | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET- | - -| | | -|--------------|------------------------------------------| -| Asset | C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | -|--------------|------------------------------------------| - -1 - -| | | -|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-21 | -| Threat title | Token leakage via log files and HTTP referrers, IETF RFC 6819 [i.8], clause 4.6.7 | -| Threat description | An O-RAN Application such as an rApp or xApp may incorrectly send the access token in the URI query, allowing the access tokens to be leaked in log files and the HTTP “referer.” | -| Threat type | Tampering
Elevation of privilege | -| Vulnerability | Improper implementation of API request | -| Impact type | Confidentiality
Authorization | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -2 - -| | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-22 | -| Threat title | User unintentionally grants too much access scope, IETF RFC 6819 [i.8], clause 4.2.2 | -| Threat description | An O-RAN Application such as rApp or xApp may incorrectly implement scoping and end-user authorization, allowing unauthorized access to resources. | -| Threat type | Elevation of Privilege | -| Vulnerability | Misconfiguration, insufficient authorization access | -| Impact type | Authorization | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -3 - -| | | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-23 | -| Threat title | Leak of confidential data in HTTP proxies, IETF RFC 6819 [i.8], clause 4.6.6 | -| Threat description | As specified in SPS clause 4.7, OAuth HTTP authentication scheme is optional. However, as per [IETF RFC 2616] it relies on the Authorization and WWW-Authenticate headers to distinguish authenticated content so that it can be protected. Proxies and caches, in particular, may fail to adequately protect requests not using these headers. | -| Threat type | Information disclosure | -| Vulnerability | Non authenticated, weakly or incorrectly authenticated communication channels | -| Impact type | Confidentiality | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -4 - -| | | -|---------------------|----------------------------------------------------------------------------------| -| Threat ID | T-OAuth-G-24 | -| Threat title | Replay of authorized resource server requests, IETF RFC 6819 [i.8], clause 4.6.2 | - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------| -| Threat description | An attacker may attempt to replay valid requests to obtain or modify/delete the O-RAN application data. | -| Threat type | Tampering | -| Vulnerability | Inadequacy of request validation of Resource server | -| Impact type | Integrity | -| Affected Asset | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | - -1 - -## 7.5 Coverage matrix of threats - -3 From the above threats, a threat inventory is developed to provide a mapping between threats, vulnerabilities and assets. - 4 For the purposes of this document, threats have been grouped into two categories: - -- 5 1. ‘O-RAN specific’ comprises threats directly relating to O-RAN architecture elements and interfaces -- 6 2. ‘General’ covers threats relating to physical, open source, virtualization, IoT and radio aspects - -7 The threat inventory provides details of each individual threat: threat agents, vulnerabilities, threatened assets and - 8 affected components. - -**Table Threat model-5 : O-RAN Threat Inventory** - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|-------------------------------|---------------------------------------------------------------------------------------------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|---------------------------------------------------------| -| O-RAN specific threats | | | | | | -| T-FRHAUL-01 | An attacker penetrates O-DU and beyond through O-RU or the Fronthaul interface to access or modify sensitive information | All | Heterogeneous security levels between O-RU and O-DU provided by different vendors | ASSET-D-01, ASSET-D-02, ASSET-D-04, ASSET-D-05 | rApps, xApps, O-RU, O-DU, O-CU, Near-RT RIC, Non-RT RIC | -| T-FRHAUL-01 A | An attacker penetrates O-DU and beyond through O-RU or the Fronthaul interface to impersonate a legitimate system or user | All | Heterogeneous security levels between O-RU and O-DU provided by different vendors | ASSET-D-01, ASSET-D-02, ASSET-D-04, ASSET-D-05 | rApps, xApps, O-RU, O-DU, O-CU, Near-RT RIC, Non-RT RIC | -| T-FRHAUL-02 | Unauthorized access to Open Front Haul Ethernet L1 physical layer interface(s) to obtain protected information | All | Lack of authentication and access control to the Open Front Haul Ethernet L1 physical layer interface | ASSET-D-01, ASSET-D-02, ASSET-D-04, ASSET-D-05 | rApps, xApps, O-RU, O-DU, O-CU, Near-RT RIC, Non-RT RIC | -| T-FRHAUL-03 | Unauthorized access to Open Front Haul Ethernet L1 physical layer interface(s) to disrupt services | All | Lack of authentication and access control to the Open Front Haul Ethernet L1 physical layer interface | ASSET-D-01, ASSET-D-02, ASSET-D-04, ASSET-D-05 | rApps, xApps, O-RU, O-DU, O-CU, Near-RT RIC, Non-RT RIC | -| T-MPLANE-01 | An attacker attempts to intercept the Fronthaul (MITM) over M Plane to obtain protected information | All | Lack of sufficient security measures in the Fronthaul due to the negative impact on the performance requirements | ASSET-D-02, ASSET-D-03 | Near-RT RIC, Non-RT RIC, O-CU, O-DU, SMO | -| T-MPLANE-02 | An attacker attempts to intercept the Fronthaul (MITM) over M Plane to alter m-plane data | All | Lack of sufficient security measures in the Fronthaul due to the negative impact on the performance requirements | ASSET-D-02, ASSET-D-03 | Near-RT RIC, Non-RT RIC, O-CU, O-DU, SMO | -| T-MPLANE-03 | An attacker attempts to intercept the Fronthaul (MITM) over M Plane to disrupt services | All | Lack of sufficient security measures in the Fronthaul due to the negative impact on the performance requirements | ASSET-D-02, ASSET-D-03 | Near-RT RIC, Non-RT RIC, O-CU, O-DU, SMO | -| T-SPLANE-01 | DoS attack against a Master clock | All |
  • Improper process to monitor and manage the performance of the Master clock
  • ANNOUNCE messages can be sent publicly in clear text
| ASSET-D-01 | O-DU, O-RU | -| T-SPLANE-02 | Impersonation of a Master clock (Spoofing) within a PTP network with a fake ANNOUNCE message | All |
  • Inaccurate timing information
  • Improper synchronization between clocks
  • ANNOUNCE messages can be sent publicly in clear text
| ASSET-D-01 | O-DU, O-RU | -| T-SPLANE-03 | A Rogue PTP Instance wanting to be a Grand Master | All |
  • Inaccurate timing information
  • Improper synchronization between clocks
  • ANNOUNCE messages can be sent publicly in clear text
| ASSET-D-01 | O-DU, O-RU | -| T-SPLANE-04 | Selective interception and removal of PTP timing packets | All |
  • Inaccurate timing information
  • Improper synchronization between clocks
  • ANNOUNCE messages can be sent publicly in clear text
| ASSET-D-01 | O-DU, O-RU | -| T-SPLANE-05 | Packet delay manipulation attack | All |
  • Inaccurate timing information
  • Improper synchronization between clocks
  • ANNOUNCE messages can be sent publicly in clear text
| ASSET-D-01 | O-DU, O-RU | -| T-CPLANE-01 | Spoofing of DL C-plane messages | All | Lack of authentication could allow an adversary to inject DL C-plane messages | ASSET-D-04 | O-DU, O-RU | -| T-CPLANE-02 | Spoofing of UL C-plane messages | All | Lack of authentication could allow an adversary to inject UL C-plane messages | ASSET-D-04 | O-DU, O-RU | -| T- | An attacker attempts to intercept the | All | Lack of sufficient security measures in the Fronthaul due to | ASSET-D-05 | O-DU, O-RU | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------| -| UPLANE-01 | Fronthaul (MITM) over U-Plane to obtain user data | | the negative impact on the performance requirements | | | -| T-UPLANE-02 | An attacker attempts to intercept the Fronthaul (MITM) over U-Plane to modify u-plane data | All | Lack of sufficient security measures in the Fronthaul due to the negative impact on the performance requirements | ASSET-D-05 | O-DU, O-RU | -| T-UPLANE-03 | An attacker attempts to intercept the Fronthaul (MITM) over U-Plane to disrupt services | All | Lack of sufficient security measures in the Fronthaul due to the negative impact on the performance requirements | ASSET-D-05 | O-DU, O-RU | -| T-UPLANE-04 | Spoofing and unauthorized access of U-Plane data packets | All | Lack of authentication, and authorization protection for U-Plane data packets | ASSET-D-05 | O-DU, O-RU | -| T-ORU-01 | An attacker stands up a false base station attack by attacking an O-RU | All | False O-RUs | ASSET-C-06, ASSET-C-31, ASSET-C-32, ASSET-C-33 | O-RU | -| T-O-RU-02 | An attacker leverages the lack of traceability with shared user accounts | All |
  • Local user accounts are shared across entities (e.g., SMO, O-DU) for access
| ASSET-D-18
ASSET-D-20 | ASSET-C-06
ASSET-C-12 | -| T-O-RU-03 | An attacker manipulates initial provisioning information | All |
  • Initial provisioning information from the Software configuration server could be manipulated to point to another server rather than the centralized authentication and authorization server
| ASSET-D-18
ASSET-D-20 | ASSET-C-06 | -| T-O-RU-04 | An attacker compromises O-RU user information- (i.e., compromises the data integrity, confidentiality of user information) in an external centralized authentication and authorization server | All |
  • Gaps to possibly (1) mismanage O-RU Account information and Credentials, (2) misclassify O-RU users, (3) manipulate O-RU Credentials if not stored securely.
| ASSET-D-20 | ASSET-C-06
ASSET-C-26 | -| T-NEAR-RT-01 | Malicious Apps can exploit UE identification, track UE location and change UE priority | All | Malicious xApps may be used to gain access to UE identification location and priority | ASSET-D-21, ASSET-D-22, ASSET-C-02, ASSET-C-09, ASSET-C-41, ASSET-C-43 | Near-RT RIC, xApps, E2 Functions, Y1 Functions | -| T-NEAR-RT-02 | Risk of a malicious xApp on Near-RT RIC to obtain protected information | All | Improper or missing authentication and authorization of xApps | ASSET-D-10, ASSET D-11, ASSET D-21, ASSET-D-22 | Near-RT RIC, UE, xApps | -| T-NEAR-RT-02A | Risk of a malicious xApp on Near-RT RIC impacting service availability | All | Improper or missing authentication and authorization of xApps | ASSET-D-10, ASSET D-11, ASSET D-21, ASSET-D-22 | Near-RT RIC, UE, xApps | -| T-NEAR-RT-03 | Attackers exploit non authenticated, weakly or incorrectly authenticated Near-RT RIC APIs to obtain protected information | All | Non authenticated, weakly or incorrectly authenticated Near-RT RIC APIs | ASSET-D-09, ASSET-D-10, ASSET D-11, ASSET D-20, ASSET-D-21, ASSET-D-25, ASSET-D-26, ASSET-D-29, ASSET-D-30, ASSET-C-02, ASSET-C-09, ASSET-C-41, ASSET-C-43 | Near-RT RIC, UE, xApps | -| T-NEAR-RT-03A | Attackers exploit non authenticated, weakly or incorrectly authenticated Near-RT RIC APIs for MITM attacks | All | Non authenticated, weakly or incorrectly authenticated Near-RT RIC APIs | ASSET-D-09, ASSET-D-10, ASSET D-11, ASSET D-20, ASSET-D-21, ASSET-D-25, ASSET-D-26, ASSET-D-29, ASSET-D-30, ASSET-C-02, ASSET-C-09, ASSET-C-41, ASSET-C-43 | Near-RT RIC, UE, xApps | -| T-NEAR-RT-04 | Attackers exploit non authorized Near-RT RIC APIs to access resources and services which they are not entitled to use, | All | Non-authorized RT RIC APIs | ASSET-D-09, ASSET-D-10, ASSET D-11, ASSET D-20, ASSET-D-21, ASSET-D-25, | Near-RT RIC, UE, xApps | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------| -| | to obtain protected information. | | | ASSET-D-26, ASSET-D-29, ASSET-D-30, ASSET-C-02, ASSET-C-09, ASSET-C-41, ASSET-C-43 | | -| T-NEAR-RT-04A | Attackers exploit non authorized Near-RT RIC APIs to access resources and services which they are not entitled to use, to disrupt services. | All | Non-authorized RT RIC APIs | ASSET-D-09, ASSET-D-10, ASSET D-11, ASSET D-20, ASSET-D-21, ASSET-D-25, ASSET-D-26, ASSET-D-29, ASSET-D-30, ASSET-C-02, ASSET-C-09, ASSET-C-41, ASSET-C-43 | Near-RT RIC, UE, xApps | -| T-NEAR-RT-05 | Attackers exploit non uniquely identified xApps using a trusted xAppID to access resources and services which they are not entitled to use. | All | Not uniquely identifying xApps using a trusted xAppID | ASSET-D-39, ASSET-C-02, ASSET-C-09 | Near-RT RIC, xApps | -| T-NONRTRIC-01 | An attacker penetrates the Non-RT RIC to cause a denial of service or degrade the performance | All | Improper or missing authentication and authorization processes on the Non-RT RIC or SMO | ASSET-D-03, ASSET-D-07, ASSET-D-08, ASSET-C-11 | Non-RT RIC, rApps | -| T-NONRTRIC-02 | UE tracking in the Non-RT RIC | All | Malicious rApps may be used to gain access to UE identification | ASSET-D-21, ASSET-D-22, ASSET-C-11 | Non-RT RIC, rApps, UE | -| T-NONRTRIC-03 | Data Corruption/Modification | All | Improper or missing authentication and authorization processes on the Non-RT RIC or SMO | ASSET-C-11 | Non-RT RIC | -| T-NONRTRIC-04 | Attacker exploits non-uniquely identified rApp instances to access services and obtain information | All | Not uniquely identifying rApp instances using a trusted rAppID | ASSET-C-10, ASSET-C-11 | Non-RT RIC, rApps | -| T-NONRTRIC-05 | Attacker exploits non-uniquely identified rApp instances, gains access to services resulting in a denial of service to correct rApp instance. | All | Non unique rAppID | ASSET-C-10 | rApps | -| T-xAPP-01 | An attacker exploits xApps vulnerabilities and misconfiguration to alter data transmitted over A1 or E2 interfaces. | All | xApp stems from an untrusted or unmaintained source | ASSET-C-03, ASSET-C-05, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10 | O-CU, Near-RT RIC, xApps | -| T-xAPP-01A | An attacker exploits xApps vulnerabilities and misconfiguration to extract sensitive information. | All | xApp stems from an untrusted or unmaintained source | ASSET-C-03, ASSET-C-05, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10 | O-CU, Near-RT RIC, xApps | -| T-xAPP-01B | An attacker exploits xApps vulnerabilities and misconfiguration to disrupt Near-RT RIC functions | All | xApp stems from an untrusted or unmaintained source | ASSET-C-03, ASSET-C-05, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10 | O-CU, Near-RT RIC, xApps | -| T-xAPP-01C | An attacker exploits xApps vulnerabilities and misconfiguration to gain unauthorized control over Near-RT RIC | All | xApp stems from an untrusted or unmaintained source | ASSET-C-03, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10 | O-CU, Near-RT RIC, xApps | -| T-xAPP-02 | Conflicting xApps impact O-RAN system functions to degrade performance or create a DoS [i.12] | All |
  • xApps may be misconfigured or compromised
  • Failing or misconfigured authentication and authorization in xApp
| ASSET-C-03, ASSET-C-05, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10 | O-CU, Near-RT RIC, xApps | -| T-xApp-03 | An attacker compromises xApp isolation to tamper with the underlying system. | All | Vulnerabilities in the underlying system hosting xApps | ASSET-C-02, ASSET-C-08, ASSET-C-09 | Near-RT RIC, O-Cloud, xApps | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|------------|------------------------------------------------------------------------------------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|----------------------------------| -| T-xApp-03A | An attacker compromises xApp isolation to extract sensitive information from co-hosted xApps. | All | Vulnerabilities in the underlying system hosting xApps | ASSET-C-02, ASSET-C-09 | Near-RT RIC, xApps | -| T-xApp-03B | An attacker compromises xApp isolation to degrade services. | All | Vulnerabilities in the underlying system hosting xApps | ASSET-C-02, ASSET-C-08, ASSET-C-09 | Near-RT RIC, O-Cloud, xApps | -| T-xApp-03C | An attacker compromises xApp isolation to gain elevated privileges. | All | Vulnerabilities in the underlying system hosting xApps | ASSET-C-02, ASSET-C-08, ASSET-C-09 | Near-RT RIC, O-Cloud, xApps | -| T-xApp-04 | False or malicious A1 policies modify behaviour of xApps. | All | xApp functionality exploited by malicious A1 policies | ASSET-D-07, ASSET-D-11, ASSET-C-09 | A1 policies, E2 Node data, xApps | -| T-xApp-05 | False or malicious A1 policies from the Non-RT RIC modify behaviour of xApps to trigger a DoS. | All | xApp functionality exploited by malicious A1 policies | ASSET-D-07, ASSET-D-11, ASSET-C-09 | A1 policies, E2 Node data, xApps | -| T-xApp-06 | False or malicious A1 policies from the Non-RT RIC modify behaviour of xApps to locate a subscriber. | All | xApp functionality exploited by malicious A1 policies | ASSET-D-07, ASSET-D-11, ASSET-C-09 | A1 policies, E2 Node data, xApps | -| T-rApp-01 | Conflicting rApps impact O-RAN system functions to degrade performance or trigger a DoS | All | rApp stems from an untrusted or unmaintained source | ASSET-C-10 | rApps, Non-RT RIC | -| T-rApp-02 | An attacker exploits rApp vulnerability for data breach or denial of service | All | rApp management is exposed to the tenant in a web front-end or REST API. These interfaces may contain software vulnerabilities or implement authentication and authorization insufficiently. | ASSET-C-10 | rApps, Non-RT RIC | -| T-rApp-03 | An attacker exploits rApps misconfiguration | All | Vulnerabilities in the underlying system hosting rApps | ASSET-C-10 | rApps, Non-RT RIC | -| T-rApp-04 | An attacker bypasses authentication and authorization | All |
  • rApps may be misconfigured or compromised
  • Failing or misconfigured authentication and authorization in rApp
| ASSET-C-10 | rApps, Non-RT RIC | -| T-rApp-05 | An attacker deploys and exploits malicious rApp | All |
  • rApps may be misconfigured or compromised
  • Failing or misconfigured authentication and authorization in rApp
| ASSET-C-10 | rApps, Non-RT RIC | -| T-rApp-06 | An attacker bypasses authentication and authorization using an injection attack | All |
  • rApps may be misconfigured or compromised
  • Failing or misconfigured authentication and authorization in rApp
| ASSET-C-10 | rApps, Non-RT RIC | -| T-rApp-07 | rApp exploits services | All |
  • rApps may be misconfigured or compromised
  • Failing or misconfigured authentication and authorization in rApp
| ASSET-C-10 | rApps, Non-RT RIC | -| T-PNF-01 | An attacker compromises a PNF to launch attacks against VNFs/CNFs | All | Vulnerabilities in a PNF deployed in a PNF-VNF/CNF deployments. | All | All | -| T-PNF-01A | An attacker compromises a PNF to launch Denial of Service attacks against VNFs/CNFs | All | Vulnerabilities in a PNF deployed in a PNF-VNF/CNF deployments. | All | All | -| T-SMO-01 | External attacker exploits authentication weakness on SMO | All | Missing or improperly configured authentication | ASSET-C-11, ASSET-C-17 | Non-RT RIC, SMO Framework | -| T-SMO-02 | External attacker exploits authorization weakness on SMO | All | Missing or improperly configured authorization | ASSET-C-11, ASSET-C-17 | Non-RT RIC, SMO Framework | -| T-SMO-03 | External Overload DoS attack targeted at SMO | All | Lack of overload protection and rate-limiting | ASSET-C-11, ASSET-C-17 | Non-RT RIC, SMO Framework | -| T-SMO-04 | Internal attacker exploits authentication | All | Missing or improperly configured authentication | ASSET-C-11, ASSET-C-17, | All | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|-----------|-------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------|------------------------------------------------------------------------|---------------------------------------------------| -| | weakness on a SMO function | | | ASSET-C-18, ASSET-C-19, ASSET-C-20, ASSET-C-21 | | -| T-SMO-05 | Internal attacker exploits authorization weakness on a SMO function | All | Missing or improperly configured authorization | ASSET-C-11, ASSET-C-17, ASSET-C-18, ASSET-C-19, ASSET-C-20, ASSET-C-21 | All | -| T-SMO-06 | Internal Overload DoS attack targeted at SMO functions | All | Lack of overload protection and rate-limiting | ASSET-C-11, ASSET-C-17, ASSET-C-18, ASSET-C-19, ASSET-C-20, ASSET-C-21 | All | -| T-SMO-07 | Internal DoS attack disables internal SMO function(s) or process(es) | All | Privilege escalation or improperly configured authorization | ASSET-C-11, ASSET-C-17, ASSET-C-18, ASSET-C-19, ASSET-C-20, ASSET-C-21 | All | -| T-SMO-08 | Attacker exploits insecure API to gain access to SMO | All | API vulnerability | ASSET-C-11, ASSET-C-17, ASSET-C-18, ASSET-C-19, ASSET-C-20, ASSET-C-21 | All | -| T-SMO-09 | Sensitive data in transit is exposed to an internal attacker | All | Missing or weak confidentiality protection of data in transit | ASSET-C-11, ASSET-C-17, ASSET-C-18, ASSET-C-19, ASSET-C-20, ASSET-C-21 | All | -| T-SMO-10 | Sensitive data at rest is exposed to an internal attacker | All | Missing or weak confidentiality protection of data at rest | ASSET-C-11, ASSET-C-17, ASSET-C-18, ASSET-C-19, ASSET-C-20, ASSET-C-21 | All | -| T-SMO-11 | AI/ML poisoning by internal attacker | All | Missing integrity protection of data at rest | ASSET-C-11, ASSET-C-17 | Non-RT RIC, SMO Framework | -| T-SMO-12 | AI/ML exposure on external entity | All | Missing or weak confidentiality protection of data at rest | ASSET-C-11, ASSET-C-17 | Non-RT RIC, SMO Framework | -| T-SMO-13 | Malicious actor views local logs | All | Missing or weak confidentiality protection of data at rest | ASSET-C-17, ASSET-C-18 | SMO Framework, SMO Functions | -| T-SMO-14 | Malicious actor modifies local log entries | All | Missing integrity protection of data at rest | ASSET-C-17, ASSET-C-18 | SMO Framework, SMO Functions | -| T-SMO-15 | Malicious actor deletes local logs | All | Missing integrity protection of data at rest | ASSET-C-17, ASSET-C-18 | SMO Framework, SMO Functions | -| T-SMO-16 | Malicious actor intercepts exports of local logs | All | Missing or weak confidentiality protection of data in transit | ASSET-C-17, ASSET-C-18, ASSET-C-26 | SMO Framework, SMO Functions, External interfaces | -| T-SMO-17 | Malicious external actor gains unauthorized access to logs | All | Missing or improperly configured authorization | ASSET-C-17, ASSET-C-18 | SMO Framework, SMO Functions | -| T-SMO-18 | Malicious internal actor gains authorized access to logs | All | Missing or improperly configured authorization | ASSET-C-17, ASSET-C-18 | SMO Framework, SMO Functions | -| T-SMO-19 | Internal attacker exploits O2 interface to view data in transit between SMO and O-Cloud | All | Missing or weak confidentiality protection of data in transit | ASSET-C-08, ASSET-C-17, ASSET-C-23 | O-Cloud, SMO, O2 interface | -| T-SMO-20 | Internal attacker exploits O2 interface to modify data in transit between SMO and O-Cloud | All | Missing integrity checking for data in transit | ASSET-C-08, ASSET-C-17, ASSET-C-23 | O-Cloud, SMO, O2 interface | -| T-SMO-21 | Internal attacker uses O2 interface via SMO to exploit API vulnerability to gain access to O-Cloud infrastructure | All | API vulnerability | ASSET-C-08, ASSET-C-17, ASSET-C-23 | O-Cloud, SMO, O2 interface | -| T-SMO-22 | Internal attacker floods O2 interface via SMO to cause DDoS on O-Cloud | All | Lack of overload protection and rate-limiting | ASSET-C-08, ASSET-C-17, ASSET-C-23 | O-Cloud, SMO, O2 interface | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|-----------|----------------------------------------------------------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|--------------------------------------| -| | infrastructure | | | | | -| T-SMO-23 | External attacker uses O2 interface via O-Cloud to exploit API vulnerability to gain access to SMO | All | API vulnerability | ASSET-C-08, ASSET-C-17, ASSET-C-23 | O-Cloud, SMO, O2 interface | -| T-SMO-24 | External attacker floods O2 interface via O-Cloud to cause DDoS on SMO | All | Lack of overload protection and rate-limiting | ASSET-C-08, ASSET-C-17, ASSET-C-23 | O-Cloud, SMO, O2 interface | -| T-SMO-25 | External attacker uses O2 interface via O-Cloud to gain authorized access to sensitive data-at-rest at the SMO | All | Missing or improperly configured authorization | ASSET-C-08, ASSET-C-17, ASSET-C-23 | O-Cloud, SMO, O2 interface | -| T-SMO-26 | External attacker exploits External interface to view data in transit between SMO and external service | All | Missing or weak confidentiality protection of data in transit | ASSET-C-11, ASSET-C-17, ASSET-C-26 | Non-RT RIC, SMO, External interfaces | -| T-SMO-27 | External attacker exploits External interface to modify data in transit between SMO and external service | All | Missing integrity checking for data in transit | ASSET-C-11, ASSET-C-17, ASSET-C-26 | Non-RT RIC, SMO, External interfaces | -| T-SMO-28 | External attacker uses External interface to exploit API vulnerability to gain access to SMO | All | API vulnerability | ASSET-C-11, ASSET-C-17, ASSET-C-26 | Non-RT RIC, SMO, External interfaces | -| T-SMO-29 | External attacker floods External interface to cause DDoS at SMO | All | Lack of overload protection and rate-limiting | ASSET-C-11, ASSET-C-17, ASSET-C-26, ASSET-C-27, ASSET-C-28 | All | -| T-SMO-30 | External attacker uses External interface to gain access to sensitive data-at-rest at the SMO | All | Missing or improperly configured authorization | ASSET-C-11, ASSET-C-17, ASSET-C-26 | Non-RT RIC, SMO, External interfaces | -| T-SMO-31 | External attacker poisons External AI/ML data to corrupt SMO | All | Missing integrity checking for data at rest | ASSET-C-11, ASSET-C-17, ASSET-C-26 | Non-RT RIC, SMO, External interfaces | -| T-SMO-32 | External attacker poisons External Enrichment Information data sources to corrupt SMO | All | Missing integrity checking for data at rest | ASSET-C-11, ASSET-C-17, ASSET-C-26 | Non-RT RIC, SMO, External interfaces | -| T-SMO-33 | rApp floods SME | All | Misbehaving 3rd-party rApp, maliciously or non-maliciously, floods internal SMOS Communication interface targeting the SME to bring a volumetric DDoS attack against the SMO. | ASSET-C-10, ASSET-C-11, ASSET-C-17, | rApps, Non-RT RIC, SMO | -| T-SMO-34 | External Consumer floods SME | All | External Source, maliciously or non-maliciously, floods the External interface targeting the SME to bring a volumetric DDoS attack against the SMO. | ASSET-C-10, ASSET-C-11, ASSET-C-17, | rApps, Non-RT RIC, SMO | -| T-R1-01 | A malicious actor gains unauthorized access to R1 services | All | weak mutual authentication | ASSET-C-16 | R1 interface | -| T-R1-02 | Attacker modifies Service Heartbeat message to cause Denial of Service | All | weak mutual authentication | ASSET-C-16 | R1 interface | -| T-R1-03 | Malicious actor bypasses authentication to Request Data | All | weak mutual authentication | ASSET-C-16 | R1 interface | -| T-R1-04 | Malicious actor bypasses authorization to Discover Data | All | weak mutual authentication | ASSET-C-16 | R1 interface | -| T-R1-05 | A malicious actor gains unauthorized access to data | All | weak mutual authentication | ASSET-C-16 | R1 interface | -| T-R1-06 | Malicious actor modifies a Data Request | All | weak mutual authentication | ASSET-C-16 | R1 interface | -| T-R1-07 | Malicious actor compromises Data Delivery to the Data Consumer | All | weak mutual authentication | ASSET-C-16 | R1 interface | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|----------------|----------------------------------------------------------------------------------------------|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------|-------------------------------------| -| T-A1-01 | Untrusted peering between Non-RT-RIC and Near-RT-RIC | All | weak mutual authentication | ASSET-C-14 | A1 interface | -| T-A1-02 | Malicious function or application monitors messaging across A1 interface | All | weak mutual authentication | ASSET-C-14 | A1 interface | -| T-A1-03 | Malicious function or application modifies messaging across A1 interface | All | weak mutual authentication | ASSET-C-14 | A1 interface | -| T-A1-04 | Unauthorized access to Non-RT-RIC- or Near-RT-RIC- resources | All | weak service consumer authorization | ASSET-D-07, ASSET-D-08 | A1 interface | -| T-AppLCM-01 | Compromise of App/VNF/CNF update package integrity during onboarding | All | Lack of integrity verification | ASSET-D-15 | Apps/VNFs/CNFs | -| T-AppLCM-02 | Compromise of App/VNF/CNF update image integrity during instantiation | All | Lack of integrity verification | ASSET-D-15 | Apps/VNFs/CNFs images | -| T-AppLCM-03 | Downgrade attack to vulnerable application version | All | Lack of integrity verification | ASSET-D-15 | Apps/VNFs/CNFs | -| T-AppLCM-04 | Attacker exploits missing or improperly defined elements of application's SecurityDescriptor | All | Misconfiguration | ASSET-D-15 | Apps/VNFs/CNFs | -| T-AppLCM-05 | Malicious actor modifies application's SecurityDescriptor to gain unauthorized access | All | Lack of authentication, lack of integrity verification | ASSET-D-15 | Apps/VNFs/CNFs | -| T-AppLCM-05 A | Malicious actor modifies application's SecurityDescriptor to degrade services | All | Lack of authentication, lack of integrity verification | ASSET-D-15 | Apps/VNFs/CNFs | -| T-AppLCM-06 | Improper decommissioning of application | All | Improper release of resources and secrets | ASSET-C-02 to ASSET-C-05, ASSET-C-09 to ASSET-C-11 | Apps/VNFs/CNFs | -| T-AppLCM-07 | Improper deletion of application sensitive data | All | Missing or weak confidentiality protection | ASSET-D-16, ASSET-D-17, ASSET-D-32 | Apps/VNFs/CNFs | -| T-SharedORU-01 | O-DU Tenant accesses O-DU Host | All | Weak authentication can be exploited by a tenant to move laterally across the deployment. | ASSET-C-34 | O-DU Host | -| T-SharedORU-02 | O-DU Host accesses O-DU Tenant | All | Weak authentication can be exploited by a host to move laterally across the deployment. | ASSET-C-35 | O-DU Tenant | -| T-SharedORU-03 | O-DU Tenant accesses O-DU Tenant | All | Weak authentication can be exploited by a tenant to move laterally across the deployment. | ASSET-C-35 | O-DU Tenant | -| T-SharedORU-04 | Password Attack on OFH M-Plane | All | The attack can be a brute-force attack or stolen password. There is increased risk of password attack in a multi-tenant environment. | ASSET-C-31, ASSET-C-34, ASSET-C-35 | Shared O-RU, O-DU Host, O-DU Tenant | -| T-SharedORU-05 | Untrusted peering to O-DU | All | Attacker exploits weak authentication on the O-DU to establish a session with a malicious app masquerading as a Shared O-RU. From the O-DU, a malicious actor can move laterally. | ASSET-C-34, ASSET-C-35 | O-DU Host, O-DU Tenant | -| T-SharedORU-06 | Untrusted peering to the Shared O-RU | All | Weak authentication can be exploited to establish session with a malicious app masquerading as a O-DU Host or O-DU Tenant | ASSET-C-31 | Shared O-RU | -| T-SharedORU- | Untrusted peering to the SMO | All | Weak authentication on the SMO can be exploited to establish session with a malicious app masquerading as a | ASSET-C-31 | Shared O-RU | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|----------------|------------------------------------------------------------------------|--------------|----------------------------------------------------------------------------------------------------------------|------------------------|------------------------| -| 07 | | | Shared O-RU. | | | -| T-SharedORU-08 | SMO Tenant accesses SMO Host | All | Weak authentication can be exploited by a tenant to move laterally across the deployment. | ASSET-C-38 | SMO Host | -| T-SharedORU-09 | SMO Host accesses SMO Tenant | All | Weak authentication can be exploited by a tenant to move laterally across the deployment. | ASSET-C-39 | SMO Tenant | -| T-SharedORU-10 | O-DU Host accesses O-CU Tenant | All | Weak authentication can be exploited by a tenant to move laterally across the deployment. | ASSET-C-37 | O-CU Tenant | -| T-SharedORU-11 | O-DU Tenant accesses O-CU Host | All | Weak authentication can be exploited by a tenant to move laterally across the deployment. | ASSET-C-36 | O-CU Host | -| T-SharedORU-12 | O-DU Tenant accesses O-CU Tenant | All | Weak authentication can be exploited by a tenant to move laterally across the deployment. | ASSET-C-37 | O-CU Tenant | -| T-SharedORU-13 | SMO Host accesses O-CU Tenant | All | Weak authentication can be exploited by a tenant to move laterally across the deployment. | ASSET-C-37 | O-CU Tenant | -| T-SharedORU-14 | SMO Tenant accesses O-CU Host | All | Weak authentication can be exploited by a tenant to move laterally across the deployment. | ASSET-C-36 | O-CU Host | -| T-SharedORU-15 | Physical port access to Shared O-RU Host/Tenant | All | Weak physical layer authentication can be exploited to gain access. | ASSET-C-31 | Shared O-RU | -| T-SharedORU-16 | Physical port access to O-DU Host/Tenant | All | Weak physical layer authentication can be exploited to gain access. | ASSET-C-34, ASSET-C-35 | O-DU Host, O-DU Tenant | -| T-SharedORU-17 | Physical port access to O-CU Host/Tenant | All | Weak physical layer authentication can be exploited to gain access. | ASSET-C-36, ASSET-C-37 | O-CU Host, O-CU Tenant | -| T-SharedORU-18 | Malicious User Login Attempt to SMO Host/Tenant | All | Weak account management and/or authentication can be exploited to gain access. | ASSET-C-38, ASSET-C-39 | SMO Host, SMO Tenant | -| T-SharedORU-19 | Malicious User Login Attempt to O-CU Host/Tenant | All | Weak account management and/or authentication can be exploited to gain access | ASSET-C-36, ASSET-C-37 | O-CU Host, O-CU Tenant | -| T-SharedORU-20 | Malicious User Login Attempt to O-DU Host/Tenant | All | Weak account management and/or authentication can be exploited to gain access | ASSET-C-32, ASSET-C-33 | O-DU Host, O-DU Tenant | -| T-SharedORU-21 | Malicious User Login Attempt to Shared O-RU Host/Tenant | All | Weak account management and/or authentication can be exploited to gain access | ASSET-C-31 | Shared O-RU | -| T-SharedORU-22 | Unauthorized internal threat actor gains access to data in Shared O-RU | All | Compromised credentials or weak or misconfigured authorization to gain access to view or modify sensitive data | ASSET-C-31 | Shared O-RU | -| T-SharedORU- | Unauthorized external threat actor gains access to data in Shared O-RU | All | Compromised credentials or weak or misconfigured authorization to gain access to view or modify sensitive data | ASSET-C-31 | Shared O-RU | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|----------------|------------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|------------------------------------------------| -| 23 | | | | | | -| T-SharedORU-24 | Data exposure at Shared O-RU | All | Weak confidentiality protection exploited to view sensitive data | ASSET-C-31 | Shared O-RU | -| T-SharedORU-25 | Shared O-RU data exposure at SMO | All | Weak confidentiality protection exploited to view sensitive data | ASSET-C-31 | Shared O-RU | -| T-SharedORU-26 | Shared O-RU data exposure at O-DU | All | Weak confidentiality protection exploited to view sensitive data | ASSET-C-31 | Shared O-RU | -| T-SharedORU-27 | Exposed data in transit between Shared O-RU and O-DU Host/Tenant | All | Weak confidentiality protection exploited to view sensitive data | ASSET-C-31, ASSET-C-24, ASSET-C-25 | Shared O-RU, M-Plane, CUS-Plane | -| T-SharedORU-28 | Exposed data in transit between Shared O-RU and SMO Host/Tenant | All | Weak confidentiality protection exploited to view sensitive data | ASSET-C-31, ASSET-C-22 | Shared O-RU, O1 | -| T-SharedORU-29 | Modify/Delete OFH C-Plane messages | All | Weak integrity protection exploited to modify or delete control messages | ASSET-C-31, ASSET-C-34, ASSET-C-35, ASSET-C-25 | Shared O-RU, O-DU Host, O-DU Tenant, CUS-Plane | -| T-SharedORU-30 | Clock hijacking on OFH S-Plane | All | Weak authorization exploit can also result in spoofing of the Grand Master clock for an availability attack | ASSET-C-31, ASSET-C-34, ASSET-C-35, ASSET-C-25 | Shared O-RU, O-DU Host, O-DU Tenant, CUS-Plane | -| T-SharedORU-31 | Parameter conflicts at Shared O-RU | All | Conflicting parameter settings degrade performance or cause an outage. | ASSET-C-31 | Shared O-RU | -| T-SharedORU-32 | Volumetric DDoS attack from O-DU targeting Shared O-RU | All | High-rate of malformed, mis-sequenced, invalid, or valid packets to cause a Denial of Service | ASSET-C-31, ASSET-C-24, ASSET-C-25 | Shared O-RU, M-Plane, CUS-Plane | -| T-SharedORU-33 | Volumetric DDoS attack from SMO targeting Shared O-RU | All | High-rate of malformed, mis-sequenced, invalid, or valid packets to cause a Denial of Service | ASSET-C-31, ASSET-C-22 | Shared O-RU, O1 | -| T-SharedORU-34 | Volumetric DDoS attack targeting O-DU | All | High-rate of malformed, mis-sequenced, invalid, or valid packets to cause a Denial of Service | ASSET-C-34, ASSET-C-35, ASSET-C-24, ASSET-C-25 | O-DU Host, O-DU Tenant, M-Plane, CUS-Plane | -| T-SharedORU-35 | Shared O-RU initialization hijacking by DHCP compromise | All | Compromise DHCP server and use it to prevent Shared O-RU from reaching carrier-active state causing a Denial of Service | ASSET-C-31 | Shared O-RU | -| T-SharedORU-36 | Shared O-RU M-plane hijacking by DNS compromise | All | The name resolution of FQDN can be manipulated by an attacker using a compromised DNS server and prevent Shared O-RU from reaching carrier-active state causing a Denial of Service | ASSET-C-31 | Shared O-RU | -| T-SharedORU-37 | Misconfiguration of MNO Host Role | All | A threat actor could exploit an incorrectly assigned role of Host to control function of the Shared O-RU | ASSET-C-31 | Shared O-RU | -| T-SharedORU-38 | Incorrect Assignment of Spectrum Resources | All | Tenant access to the wrong resources, due to malicious intent or could be exploited to gain access to information. | ASSET-C-31 | Shared O-RU | -| T- | Chain of Trust in a Multi-Tenant | All | Untrustworthy certificates can be exploited to gain access to | ASSET-C-31, ASSET-C-34, | Shared O-RU, O-DU | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|------------------------------------------------|-----------------------------------------------------------------|--------------|--------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------| -| SharedORU-39 | Environment | | the Shared O-RU | ASSET-C-35, ASSET-C-36, ASSET-C-37, ASSET-C-38, ASSET-C-39 | Host, O-DU Tenant, O-CU Host, O-CU Tenant, SMO Host, SMO Tenant | -| T-SharedORU-40 | Hijack of MNO Host Role | All | Elevation of privilege enables the tenant, acting as host, to have authorized access to sensitive data, credentials, and system privileges | ASSET-C-31 | Shared O-RU | -| T-SharedORU-41 | Not Released Host Role (Host Role resume) | All | Elevation of privilege enables the tenant, acting as host, to have authorized access to sensitive data, credentials, and system privileges | ASSET-C-31 | Shared O-RU | -| T-SharedORU-42 | Misuse of "sudo" privileges | All | Elevation of privilege enables the tenant, acting as host, to have authorized access to sensitive data, credentials, and system privileges | ASSET-C-31 | Shared O-RU | -| T-SharedORU-43 | Eavesdropping of unprotected CUSM-plane data within shared O-RU | All | Eavesdrop sensitive data between neighbor tenants and the host | ASSET-C-31 | Shared O-RU | -| T-SharedORU-44 through T-SharedORU-51 are Void | | | | | | -| T-SharedORU-52 | Thrashing O-DU Failovers | All | Threat actor spoofs SMO to cause O-DU-1 and O-DU-2 to thrash between Active state and Standby state | ASSET-C-34, ASSET-C-22 | O-DU, O1 | -| T-SharedORU-53 | Dual (Dueling) Active O-DUs | All | Threat actor spoofs SMO to cause O-DU-1 and O-DU-2 to both be in Active state. | ASSET-C-34, ASSET-C-22 | O-DU, O1 | -| T-SharedORU-54 | Modify/Inject O1 messages at the SMO | All | Threat actor spoofs O-DU to modify, inject, flood O1 messages to the SMO to prevent SMO detection of O-DU failure. | ASSET-C-38, ASSET-C-22 | SMO, O1 | -| T-SharedORU-55 | Set Incorrect Array-Carrier configuration on O-DU (Standby) | All | Threat actor spoofs SMO to set or modify the pre-configured array-carrier configuration on the O-DU in Standby state. | ASSET-C-34, ASSET-C-22 | O-DU, O1 | -| T-SharedORU-56 | Modify Array-Carrier pre-configuration on Shared O-RU | All | Threat actor can gain access to Shared O-RU to modify its pre-configured array-carrier | ASSET-C-31 | Shared O-RU | -| T-SharedORU-57 | Modify/Inject M-Plane messages with Array-Carrier configuration | All | Threat actor Modifies/Injects M-Plane messages with Array-Carrier configuration sent to the Shared O-RU. | ASSET-C-31, ASSET-C-24 | Shared O-RU, M-Plane | -| T-OAuth-G-01 | Obtaining client secrets | All | Unsecured tokens and secrets | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-02 | Obtaining refresh tokens | All | A new refresh token was not issued | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-03 | Obtaining access tokens | All | Insufficient protection for credentials | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|--------------|------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| -| | | | | ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | O-DU | -| T-OAuth-G-04 | Eavesdropping access tokens | All | Non authenticated, weakly or incorrectly authenticated communication channels | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-05 | Disclosure of client credentials during transmission | All | Non authenticated, weakly or incorrectly authenticated communication channels | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-06 | Open redirectors on client | All | Non authenticated, weakly or incorrectly authenticated communication channels | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-07 | Obtain a deployment-specific secret, | All | Malicious applications, insufficient access control | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-08 | Obtaining authorization by code substitution (OAuth Login) | All | Insufficient protection for credentials | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-09 | Access token leak in transport/endpoints | All | Non authenticated, weakly or incorrectly authenticated URI | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-10 | Malicious client obtains existing authorization by fraud | All | Improper authorization process and lack of re-validating the authorization requests | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-11 | Malicious client obtains authorization | All | Insufficient protection for credentials | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-12 | Accidental exposure of passwords at client site | All | Insufficient protection for credentials | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth- | Client obtains scopes without end-user | All | Misconfiguration | ASSET-C-01, ASSET-C-02, | SMO Framework, | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|--------------|--------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| -| G-13 | authorization and possible misconfigurations | | | ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-14 | Client obtains refresh token through automatic authorization | All | Improper authorization process and lack of re-validating the authorization requests | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-15 | Eavesdropping refresh tokens from authorization server | All | Non authenticated, weakly or incorrectly authenticated communication channels | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-16 | Obtaining refresh token by online guessing | All | Improper authorization process and lack of re-validating the authorization requests | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-17 | Refresh token phishing by counterfeit authorization server | All | Refresh token phishing by counterfeit authorization server | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-18 | Guessing access tokens | All | Insecure generation of access token | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-19 | Access token phishing by counterfeit resource server | All | Insufficient protection for credentials | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-20 | Abuse of token by legitimate resource server or client | All | Insufficient protection for access control on resource server | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-21 | Token leakage via log files and HTTP referrers | All | Improper implementation of API request | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-22 | User unintentionally grants too much access scope | All | Misconfiguration, insufficient authorization access | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|------------------------|---------------------------------------------------------------------------------|--------------|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| -| T-OAuth-G-23 | Leak of confidential data in HTTP proxies | All | Non authenticated, weakly or incorrectly authenticated communication channels | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| T-OAuth-G-24 | Replay of authorized resource server requests | All | Inadequacy of request validation of Resource server | ASSET-C-01, ASSET-C-02, ASSET-C-07, ASSET-C-08, ASSET-C-09, ASSET-C-10, ASSET-C-11, ASSET-C-32, ASSET-C-34, ASSET-C-36 | SMO Framework, Near-RT RIC, O-Cloud, O-CU, O-RU, O-DU | -| General threats | | | | | | -| T-GEN-01 | Software flaw attack | All | Vulnerable code exploits, Design Weakness | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs | -| T-GEN-02 | Malicious access to exposed services using valid accounts | All | Lack of authentication | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs | -| T-GEN-03 | Untrust binding between the different O-Cloud layers | All | Lack of integrity verification during boot or runtime | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs | -| T-GEN-04 | Lack of Authentication & Authorization in interfaces between O-Cloud components | All | Lack of authentication, Insecure interfaces | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs, O2 | -| T-GEN-05 | Unsecured credentials and keys | All | Insecure O-Cloud APIs, Lack of integrity verification during boot or runtime | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud | -| T-GEN-06 | Sensitive application data cache exploitation | All | Sensitive information disclosure, Privilege escalation in Applications | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs | -| T-VM-C-01 | Abuse of a privileged VM/Container | All | Misconfiguration or Insecure VM/Container configurations | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, | O-Cloud, Apps/VNFs/CNFs | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|-----------|--------------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| -| | | | | ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | | -| T-VM-C-02 | VM/Container escape attack | All | Shared tenancy vulnerabilities (multitenant environment), Lack of strong VM/Container isolation, lack of authentication, Insecure networking, Unrestricted communication between VMs/Containers | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs | -| T-VM-C-03 | VM/Container data theft | All | Lack of authentication, insecure data storage | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs | -| T-VM-C-04 | VM/Container migration attacks | All | Host misconfiguration, lack of authentication, memory pages copied in clear, vulnerable code exploits | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs | -| T-VM-C-05 | Changing virtualization resource without authorization | All | Insecure O1/O2 interfaces, Lack of authentication/access control on IMS/DMS | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs | -| T-VM-C-06 | Failed or incomplete VNF/CNF termination or releasing of resources | All | Lack of authentication, misconfigurations (VNF/CNF, Host OS, Hypervisor/Container Engine) | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs | -| T-IMG-01 | VM/Container images tampering | All | Compromised VM/Container images (Build machine attacks, Supply chain attacks) at rest, lack of authentication, misconfiguration or Insecure VM/Container images configurations | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs images | -| T-IMG-02 | Insecure channels with images repository | All | Compromised VM/Container images in transit | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs images | -| T-IMG-03 | Secrets disclosure in VM/Container images | All | Secret exposure in VNF/CNF images | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, | O-Cloud, Apps/VNFs/CNFs images | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|------------|----------------------------------------------------------------------------------|--------------|-----------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| -| | | | | ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | | -| T-IMG-04 | Build image on VL | All | Host misconfiguration, lack of authentication | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs images | -| T-VL-01 | VM/Container hyperjacking attack | All | Host misconfiguration, lack of authentication | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs | -| T-VL-02 | Boot tampering | All | Host misconfigurations, lack of authentication | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs | -| T-VL-03 | Attack internal network services | All | Insecure O-Cloud APIs, Lack of authentication | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud | -| T-O2-01 | MitM attacks on O2 interface between O-Cloud and SMO | All | Insecure O2 interface, lack authentication | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O2 | -| T-OCAPI-01 | MitM attacks on O-Cloud interface between VNFs/CNFs and the virtualization layer | All | Insecure O-Cloud APIs, lack of authentication | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs | -| T-HW-01 | Cross VM/Container side channel attacks | All | Flaws in chip design, use of shared hardware, Lack of isolation, lack of authentication | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | O-Cloud, Apps/VNFs/CNFs | -| T-HW-02 | MitM attacks on the interface between virtualization layer and hardware | All | Insecure interfaces between HW and VL layers, lack of authentication, misconfiguration | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, | O-Cloud | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|------------|---------------------------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| -| | | | | ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | | -| T-ADMIN-01 | Denial of service against NFO/FOCOM | All | Lack of authentication, vulnerable code exploits, design weakness, insecure O2 interface | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | NFO/FOCOM, O-Cloud, Apps/VNFs/CNFs | -| T-ADMIN-02 | Abuse a O-Cloud administration service | All | Lack of authentication, secret exposure (insufficient safeguarding of credentials), vulnerable code exploits, design weakness | ASSET-D-12, ASSET-D-13, ASSET-D-14, ASSET-D-15, ASSET-D-16, ASSET-D-17, ASSET-D-18, ASSET-D-19, ASSET-D-20, ASSET-D-29, ASSET-D-31, ASSET-D-32 | NFO/FOCOM, O-Cloud, Apps/VNFs/CNFs | -| T-AAL-01 | Attacker exploits insecure API to gain access to hardware accelerator resources | All | Insecure AAL APIs and interfaces
Lack authentication and authorization | ASSET-D-33 to ASSET-D-38 | ASSET-C-29, ASSET-C-30 | -| T-AAL-02 | Internal Overload DoS attack targeting AAL services | All | Insecure AAL APIs and interfaces
Lack authentication and authorization | ASSET-D-33 to ASSET-D-38 | ASSET-C-29, ASSET-C-30 | -| T-AAL-03 | Fail to clear resources | All | Insecure AAL APIs
Flaws in AAL design
Lack of secure deletion of data after process termination | ASSET-D-33 to ASSET-D-38 | ASSET-C-29, ASSET-C-30 | -| T-AAL-04 | HAM compromise | All | Insecure HAM APIs
Flaws in HAM design
Lack of access control | ASSET-D-33 to ASSET-D-38 | ASSET-C-29, ASSET-C-30 | -| T-AAL-05 | Malicious memory accesses | All | Insecure AAL APIs
Flaws in AAL design
Unrestricted memory access
Lack of access control | ASSET-D-33 to ASSET-D-38 | ASSET-C-29, ASSET-C-30 | -| T-AAL-06 | Firmware attacks | All | Weak accelerator design
Misconfiguration
Insecure AAL/HAM APIs | ASSET-D-33 to ASSET-D-38 | ASSET-C-29, ASSET-C-30 | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|---------------------| -| T-O-CLOUD-ID-01 | ID reuse in O-Cloud's object lifecycle | All | Insufficient data cleanup
Weak isolation mechanisms
Inadequate monitoring and Logging
Lack of ID randomization
Inefficient access controls
No Timestamping or Versioning
Lack of notification mechanisms | ASSET-D-14, ASSET-D-15, ASSET-D-18, ASSET-D-29 | ASSET-C-08 | -| T-O-CLOUD-ID-02 | Node redundancy in O-Cloud deployments | All | Inadequate decommissioning procedures
Weak identity management
Insufficient data cleanup
No state verification
Lack of Resource Auditing
Lack of notification mechanisms
Inadequate monitoring and Logging | ASSET-D-14, ASSET-D-15, ASSET-D-18, ASSET-D-29 | ASSET-C-08 | -| T-O-CLOUD-ID-03 | O-Cloud ID mismanagement | All | Predictable ID Generation
Lack of ID validation
Inefficient synchronization
No ID revocation mechanism
Inadequate access controls
Lack of Namespace Segregation | ASSET-D-14, ASSET-D-15, ASSET-D-18, ASSET-D-29 | ASSET-C-08 | -| T-OPENSRC-01 | Developers use SW components with known vulnerabilities and untrusted libraries that can be exploited by an attacker through a backdoor attack | All |
  • Inaccurate inventories of open-source software
  • Lack of consistent Supply Chain traceability and security
  • Lack of coding best practices
  • Modules with known vulnerabilities and untrusted libraries
| All | All | -| T-OPENSRC-02 | A trusted developer intentionally inserts a backdoor into an open-source code O-RAN component | All | Bugs in open-source software caused by mistakes and human error | All | All | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| T-PHYS-01 | An intruder gains physical access to O-RAN components to cause damage by manipulation / modification to software / software configuration /management. | All except Script kiddies |
  • Improper physical security protection, hardware backdoor
| All | All | -| T-PHYS-01A | An intruder gains physical access to O-RAN components to access sensitive data | All except Script kiddies |
  • Improper physical security protection, hardware backdoor
| All | All | -| T-PHYS-01B | An intruder gains physical access to O-RAN components to cause performance degradations, denial of service. | All except Script kiddies |
  • Improper physical security protection, Improper maintenance and monitoring of hardware parameters, hardware backdoor
| All | All | -| T-PHYS-02 | An intruder into the Fronthaul cable network attempts to gain electronic access to cause damage or access sensitive data | All except Script kiddies | Physical access to the open Fronthaul cable network | ASSET-D-01, ASSET-D-02, ASSET-D-04, ASSET-D-05, ASSET-C-05, ASSET-C-06, ASSET-C-31, ASSET-C-32, ASSET-C-33, ASSET-C-34, ASSET-C-35, ASSET-C-12 | All | -| T-RADIO-01 | Disruption through radio jamming | All except Script kiddies | Weakness of wireless cellular communications | ASSET-D-06
ASSET-C-05
ASSET-C-06 | O-RU, O-DU | -| T-RADIO-01A | Disruption through radio sniffing and spoofing | All except Script kiddies | Weakness of wireless cellular communications | ASSET-D-06
ASSET-C-05
ASSET-C-06 | O-RU, O-DU | -| T-RADIO-02 | DoS attacks on cognitive radio networks | All except Script kiddies | Weakness of wireless cellular communications | ASSET-D-06
ASSET-C-05
ASSET-C-06 | O-RU, O-DU | -| T-AIML-IM-1 | Training Data Control | All | Vulnerabilities in data sources, vulnerabilities in training database | ASSET-D-25, ASSET-D-26, ASSET-D-27, ASSET-D-28 | Near-RT RIC, Non-RT RIC, xApps, rApps | -| T-AIML-IM-2 | Testing Data Control | All | Vulnerabilities in data sources, vulnerabilities in training database | ASSET-D-25, ASSET-D-26, ASSET-D-27, ASSET-D-28 | Near-RT RIC, Non-RT RIC, xApps, rApps | -| T-AIML-IM-3 | Label Manipulation | All | Vulnerabilities in data sources, vulnerabilities in training database | ASSET-D-25, ASSET-D-26, ASSET-D-27, ASSET-D-28 | Near-RT RIC, Non-RT RIC, xApps, rApps | -| T-AIML-IM-4 | AI/ML Query Exploitation | All | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in AI/ML APIs | ASSET-D-26, ASSET-D-27, ASSET-D-28 | Near-RT RIC, Non-RT RIC, xApps, rApps | -| T-AIML-DP-01 | Black-box Data Poisoning | All | Vulnerabilities in data sources, vulnerabilities in training database | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-12, ASSET-C-02, ASSET-C-11 | Database holding data from xApp applications and E2 Node, Training or test data sets collected externally or internally, Trained ML model, xApps, rApps, Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-DP-02 | Grey-box Data Poisoning | All | Vulnerabilities in data sources, vulnerabilities in data transport, vulnerabilities in training database | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-12, | Database holding data from xApp applications | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|---------------|--------------------------------------------|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | ASSET-C-02, ASSET-C-11, ASSET-C-22, ASSET-C-14, ASSET-C-40 | and E2 Node, Training or test data sets collected externally or internally, Trained ML model, xApps, rApps, Near-RT-RIC SW, Non-RT-RIC SW, O1 interface for streaming data, A1 interface, E2 interface for streaming data | -| T-AIML-DP-03 | White-box Data Poisoning | All | Vulnerabilities in data sources, vulnerabilities in training database | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-12, ASSET-C-02, ASSET-C-11, ASSET-C-22, ASSET-C-14, ASSET-C-40 | Database holding data from xApp applications and E2 Node, Training or test data sets collected externally or internally, Trained ML model, xApps, rApps, Near-RT-RIC SW, Non-RT-RIC SW, O1 interface for streaming data, A1 interface, E2 interface for streaming data | -| T-AIML-MEI-01 | Information Access - Membership Inference | All | Vulnerabilities in data sources, vulnerabilities in training database | ASSET-D-26, ASSET-C-02, ASSET-C-11 | Trained ML model, xApps, rApps, Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-MEI-02 | Inference Technique - Membership Inference | All | Vulnerabilities in data sources, vulnerabilities in training database | ASSET-D-26, ASSET-C-02, ASSET-C-11 | Trained ML model, xApps, rApps, Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-MEI-03 | Target based - Membership Inference | All | Vulnerabilities in data sources, vulnerabilities in training database | ASSET-D-26, ASSET-C-02, ASSET-C-11 | Trained ML model, xApps, rApps, Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-ME-01 | Intellectual Property Theft | All | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-02, ASSET-C-11 | Database holding data from xApp applications and E2, Training or test data sets collected externally or internally, Trained ML model, Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-ME-02 | Data Privacy Violations | All | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-02, ASSET-C-11 | Database holding data from xApp applications and E2, Training or test data sets collected externally or | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|---------------|----------------------------------------|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | | internally, Trained ML model, Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-ME-03 | Adversarial Attacks with Stolen Models | All | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-02, ASSET-C-11 | Database holding data from xApp applications and E2, Training or test data sets collected externally or internally, Trained ML model, Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-MOI-01 | Black-box Model Inversion | All | Model is overfitted, model may have memorized specific training examples, model API not properly protected | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-D-27 | Near-RT RIC, Non-RT RIC, xApps, rApps | -| T-AIML-MOI-02 | White-box Model Inversion | All | Model is not protected, training data is not protected, model is overfitted, model may have memorized specific training examples, model API not protected | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-D-27, ASSET-D-28 | Near-RT RIC, Non-RT RIC, xApps, rApps | -| T-AIML-SC-01 | Data Poisoning via Supply Chain | All | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model transfer | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-02, ASSET-C-11, ASSET-C-12 | Database holding data from xApp applications and E2 Node, Training or test data sets collected externally or internally, Trained ML model, ML components deploying machine learning (xApps, rApps), Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-SC-02 | Model Tampering | All | Vulnerabilities in ML model transfer | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-02, ASSET-C-11, ASSET-C-12 | Database holding data from xApp applications and E2 Node, Training or test data sets collected externally or internally, Trained ML model, ML components deploying machine learning (xApps, rApps), Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-SC-03 | Backdoor via Supply Chain | All | Vulnerabilities in ML model transfer | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-02, ASSET-C-11, ASSET-C-12 | Database holding data from xApp applications and E2 Node, Training or test data sets collected externally or internally, Trained ML model, ML components deploying machine learning | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|--------------|----------------------------------------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| T-AIML-SC-04 | Hardware Tampering | All | Vulnerabilities in the AI processing HW | ASSET-D-10, ASSET-D-26, ASSET-C-02, ASSET-C-11, ASSET-C-12 | (xApps, rApps),Near-RT-RIC SW, Non-RT-RIC SW
Database holding data from xApp applications and E2 Node, Trained ML model, ML components deploying machine learning (xApps, rApps),Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-SC-05 | Insecure Maintenance APIs | All | Vulnerabilities in the ML maintenance APIs | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-02, ASSET-C-11, ASSET-C-12 | Database holding data from xApp applications and E2 Node, Training or test data sets collected externally or internally, Trained ML model, ML components deploying machine learning (xApps, rApps),Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-SC-06 | Third-party Libraries and Dependencies | All | Vulnerabilities in the ML- related SW | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-02, ASSET-C-11, ASSET-C-12 | Database holding data from xApp applications and E2 Node, Training or test data sets collected externally or internally, Trained ML model, ML components deploying machine learning (xApps, rApps),Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-OI-01 | Denial of Service Impacting Output Integrity | All | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer | ASSET-D-25,ASSET-D-26, ASSET-D-27, ASSET-D-07,ASSET-C-12, ASSET-C-02, ASSET-C-11 | Training or test data sets collected externally or internally, Trained ML model, ML prediction results,A1 policies,E2 node data, Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-OI-02 | Subscriber QoE Change | All | Vulnerabilities in data sources, vulnerabilities in training database, vulnerabilities in ML model storage, vulnerabilities in ML model transfer. | ASSET-D-25, ASSET-D-26, ASSET-D-27, ASSET-D-07, ASSET-D-11,ASSET-C-02, ASSET-C-02, ASSET-C-11 | Training or test data sets collected externally or internally, Trained ML model , ML prediction | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|--------------|-----------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | | results ,Data transported over the O1 interface,A1 policies, E2 node data, Near-RT-RIC SW, Non-RT-RIC SW . | -| T-AIML-MP-01 | Model Parameter Poisoning | All |
  • Insufficient access controls to the model's parameters [i.33]
  • Inadequate monitoring and logging of model's activity [i.32]
  • Lack of control for poisoning in model [i.32]
  • Weak access protection mechanisms for ML model components [i.32]
| [ASSET-D-26], [ASSET-C-12], [ASSET-D-27] | Near-RT RIC, Non-RT RIC, O-CU, O-DU, xApps, rApps | -| T-AIML-MP-02 | Inference Algorithm Poisoning | All |
  • Insufficient access controls to the model's code [i.33]
  • Inadequate monitoring and logging of model's activity [i.32]
  • Lack of code integrity checking
  • Weak access protection mechanisms for ML model components [i.32]
| [ASSET-D-26], [ASSET-D-27] | Near-RT RIC, Non-RT RIC, O-CU, O-DU, xApps, rApps | -| T-AIML-MP-03 | Learning Algorithm Poisoning | All |
  • Insufficient access controls to the model's code [i.33]
  • Inadequate monitoring and logging of model's activity [i.32]
  • Weak access protection mechanisms for ML model components [i.32]
  • Lack of code integrity checking
| [ASSET-C-12] | Near-RT RIC, Non-RT RIC, xApps, rApps | -| T-AIML-MP-04 | Model Control | All | Vulnerabilities in ML model storage, vulnerabilities in ML model transfer | ASSET-D-12, ASSET-D-26, ASSET-D-27, ASSET-D-28 | Near-RT RIC, Non-RT RIC, xApps, rApps | -| T-AIML-MS-01 | Data Manipulation for Model Skewing | All | Vulnerabilities in (i) training data validation, (ii) less robust model training against cyber-attacks, (iii) less model performance monitoring for monitoring of suspicious activity | ASSET-D-26, ASSET-D-27, ASSET-D-28 | Trained ML model, xApps, rApps, Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-MS-02 | Feedback Manipulation for Model Skewing | All | Vulnerabilities in (i) less secure feedback mechanisms to prevent manipulation, (ii) less robust model training against cyber-attacks, (iii) less model performance monitoring for monitoring of suspicious activity | ASSET-D-26, ASSET-D-27, ASSET-D-28 | Trained ML model, xApps, rApps, Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-TL-01 | Data Poisoning for Transfer Learning | All | Vulnerabilities in data sources, Vulnerabilities in training database | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-02, ASSET-C-11, ASSET-C-12 | Database holding data from xApp applications and E2 Node, Training or test data sets collected externally or internally, Trained ML model, ML components deploying machine learning (xApps, rApps),Near-RT-RIC SW, Non-RT-RIC SW | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|--------------|--------------------------------------|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| T-AIML-TL-02 | Model Stealing for Transfer Learning | All | Vulnerabilities in data sources, Vulnerabilities in training database, Vulnerabilities in ML model storage, Vulnerabilities in ML model transfer | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-02, ASSET-C-11, ASSET-C-12 | Database holding data from xApp applications and E2 Node, Training or test data sets collected externally or internally, Trained ML model, ML components deploying machine learning (xApps, rApps), Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-TL-03 | Adversarial Examples | All | Vulnerabilities in data sources, Vulnerabilities in training database, Vulnerabilities in ML model storage, Vulnerabilities in ML model transfer | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-02, ASSET-C-11 | Database holding data from xApp applications and E2 Node, Training or test data sets collected externally or internally, Trained ML model, Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-TL-04 | Backdoor for Tranfer Learning | All | Vulnerabilities in ML model transfer | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-02, ASSET-C-11, ASSET-C-12 | Database holding data from xApp applications and E2 Node, Training or test data sets collected externally or internally, Trained ML model, ML components deploying machine learning (xApps, rApps), Near-RT-RIC SW, Non-RT-RIC SW | -| T-AIML-EL-01 | Model Extraction | All | Vulnerabilities in data sources | ASSET-D-10, ASSET-D-26, ASSET-C-02, ASSET-C-11, ASSET-C-29, ASSET-30 | Database holding data from xApp applications and E2 Node, Trained ML model, Near-RT-RIC SW, Non-RT-RIC SW, AAL software, Hardware accelerator device firmware | -| T-AIML-EL-02 | Data Inference | All | Vulnerabilities in data sources | ASSET-D-10, ASSET-C-02, ASSET-C-11, ASSET-C-29, ASSET-30 | Database holding data from xApp applications and E2 Node, Near-RT-RIC SW, Non-RT-RIC SW, AAL software, Hardware accelerator device firmware | -| T-AIML- | Denial of Service via Side Channels | All | Vulnerabilities in data sources | ASSET-D-10, ASSET-D-26, | Database holding data | - -| Threat ID | Threat title | Threat agent | Vulnerability | Threatened Asset | Affected Components | -|--------------|--------------------------------------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| EL-03 | | | | ASSET-C-02, ASSET-C-11, ASSET-C-29, ASSET-30 | from xApp applications and E2 Node, Trained ML model, Near-RT-RIC SW, Non-RT-RIC SW, AAL software, Hardware accelerator device firmware | -| T-AIML-EV-01 | Grey-box based Data Evasion | All | Vulnerabilities in the input APIs of the AI ML model application
Vulnerabilities in the source of input data used by AI ML for inferences | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-02, ASSET-C-11 | Database holding data from xApp applications and E2 Node, Training or test data sets collected externally or internally, Trained ML model, Near-RT-RIC SW, Non-RT-RIC | -| T-AIML-EV-02 | White-box based data evasion attacks | All | Vulnerabilities in the input APIs of the AI/ML model application
Vulnerabilities in the source of input data used by AI/ML for inferences | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-02, ASSET-C-11 | Database holding data from xApp applications and E2 Node, Training or test data sets collected externally or internally, Trained ML model, Near-RT-RIC SW, Non-RT-RIC | -| T-AIML-EV-03 | Black-box based data evasion attacks | All | Vulnerabilities in the input APIs of the AI ML model application
Vulnerabilities in the source of input data used by AI ML for inferences | ASSET-D-10, ASSET-D-25, ASSET-D-26, ASSET-C-02, ASSET-C-11 | Database holding data from xApp applications and E2 Node, Training or test data sets collected externally or internally, Trained ML model, Near-RT-RIC SW, Non-RT-RIC | -| T-E2-01 | Untrusted Near-RT-RIC and E2 Nodes | All | weak mutual authentication | ASSET-C-40 | E2 interface | -| T-E2-02 | Malicious actor monitors messaging across E2 interface | All | Missing or weak confidentiality protection | ASSET-C-40 | E2 interface | -| T-E2-03 | Malicious actor modifies messaging across E2 interface | All | Lack of integrity verification | ASSET-C-40 | E2 interface | -| T-Y1-01 | Untrusted Near-RT-RIC and Y1 consumers | All | weak mutual authentication | ASSET-C-42 | Y1 interface | -| T-Y1-02 | Malicious actor monitors messaging across Y1 interface | All | Missing or weak confidentiality protection | ASSET-C-42 | Y1 interface | -| T-Y1-03 | Malicious actor modifies messaging across Y1 interface | All | Lack of integrity verification | ASSET-C-42 | Y1 interface | - -# 8 Security principles - -This clause elucidates security principles that an O-RAN system should achieve. They provide high level and abstract statement of the intended solution to countering potential Threats. Each security principle references applicable ZT tenets. - -## 8.1 Principles (SP) - -### 8.1.1 SP-AUTH Mutual Authentication - -- Mutual authentication SHOULD be established to allow the O-RAN system verifying who performs what, thus possible to detect fake base stations, unauthorized or malicious components, malicious applications and malicious users/administrators. -- ZT Tenets: ZT-1, ZT-2, ZT-3, ZT-4, ZT-6 - -### 8.1.2 SP-ACC Access Control - -- The O-RAN system SHOULD forbid unauthorized administrators or components to access O-RAN resources or services anytime and anywhere. Access controls are required for: - - Network Access Controls for filtering unauthorized/unexpected traffic in the O-RAN components over their interfaces. - - Access controls to restrict access to component configurations. - - Access controls for hardware to maintain the trust chain. -- ZT Tenets: ZT-1, ZT-3, ZT-4, ZT-6 - -### 8.1.3 SP-CRYPTO Secure cryptographic, key management and PKI - -- Well-known, standardized, secure and unbroken cryptographic schemes and protocols SHOULD be used. Proprietary schemes and protocols SHOULD be avoided. -- A secure key management of O-RAN keys (KgNB, KRRC-enc, KRRC-int, KUP-int, and KUP-enc, ksn) SHOULD be implemented to manage all the steps of key lifecycle: key generation using an appropriate level of entropy from a reliable source, secure key storage, key rotation and revocation, secure key destruction, etc. -- Reliable PKI for authentication and data encryption SHOULD be used. Public CAs SHOULD be supported. The certificates SHOULD be issued by a trusted or rooted Certificate Authority (CA). The CA implements the Certificate Policy which specifies the rules and policies about who may or may not receive a Certificate. Relying parties can access the Certificate Policy to determine what validation/verification checks were performed prior to certificate issuance. -- Each O-RU SHOULD be configured with lists of algorithms which are allowed for usage. There SHOULD be one list for integrity algorithms, and one for ciphering algorithms. These lists SHOULD be ordered according to a priority decided by the operator. -- ZT Tenets: ZT-2, ZT-4 - -### 8.1.4 SP-TCOMM Trusted Communication - -- Integrity, confidentiality, availability, authenticity and replay protection of resources SHOULD be ensured in transit (see 'Critical Assets', clause 6.3) over O-RAN interfaces. -- ZT Tenets: ZT-1, ZT-2 - -###### 1 8.1.5 SP-SS Secure storage - -- 2 • Integrity, confidentiality, availability protection of O-RAN resources SHOULD be ensured at rest (see ‘Critical -3 Assets’, clause 6.3). -- 4 • ZT Tenets: ZT-1, ZT-2, ZT-4, ZT-5, ZT-6 - -###### 5 8.1.6 SP-SB Secure boot and self-configuration - -- 6 • O-RAN components SHOULD secure their firmware and configuration to provide the opportunity for trust to -7 be extended higher in the software stack. Verified platform firmware can, in turn, verify the operating system -8 (OS) boot loader, which can then verify other software components all the way up to the OS itself, the -9 hypervisor or container runtime layers and O-RAN components. The transitive trust SHOULD be consistent -10 with the concept of the chain of trust (CoT)-a method where each piece of code in the boot process measures -11 and checks the signature of the next stage of the boot process before the software boots. -- 12 • The secure boot process, signature verification and self-configuration SHOULD be securely implemented for -13 all O-RAN components to authenticate them before loading. -- 14 • ZT Tenets: ZT-1, ZT-3, ZT-4, ZT-5 - -###### 15 8.1.7 SP-UPDT Secure Update - -- 16 • A secure update management process SHOULD be implemented for introducing a new component or software -17 change into the O-RAN system. The process SHOULD consider the ability to update the cryptographic -18 algorithms and to adapt to upcoming O-RAN security challenges. A timely update cycles if vulnerabilities are -19 discovered SHOULD be in place. -- 20 • ZT Tenets: ZT-1, ZT-5, ZT-7 - -###### 21 8.1.8 SP-RECO Recoverability & Backup - -- 22 • A recoverability process to recovery in case of denial of service SHOULD be implemented. An approach for -23 detecting and mitigating DoS attacks SHOULD be in place. -- 24 • O-RAN vendors SHOULD define a recovery plan that resets the O-RAN components to a trustworthy state in -25 case of a malfunction or an attack (e.g. DoS). -- 26 • Backup systems SHOULD be in place to allow data or component on the O-RAN to be secured. Backup -27 systems SHOULD ensure a suitable level of data or component availability and reliability. -- 28 • ZT Tenets: ZT-1, ZT-5, ZT6, ZT-7 - -###### 29 8.1.9 SP-OPNS Security management of risks in open-source 30 components - -- 31 • Vendors using open-source code SHOULD enhance its security by applying industry coding best practices. It -32 is recommended that vendors practice a higher level of due diligence for exposure to public exploits when -33 using Open-Source code. -- 34 • A Software Bill of Materials (SBOM) SHOULD be maintained to track which open-source components are in -35 use and where. -- 36 • Security Analysis (Audit, vulnerability scan, etc.) SHOULD be performed to ensure all identified components -37 are free of security vulnerabilities. -- 38 • A proper policy and process SHOULD be in place for identifying and patching known issues with the open- -39 source components. Open-source software components SHOULD be kept up to date and patched. -- 40 • ZT Tenets: ZT-1, ZT-4, ZT-5, ZT-6, ZT-7 - -### 8.1.10 SP-ASSU Security Assurance - -- Mobile networks are classified as critical infrastructure making security assurance especially more than relevant: - - Vendors SHOULD ensure and prove that its software or hardware meets 3GPP Security Assurance Specifications (SCAS). - - Vendors SHOULD ensure and prove that its software or hardware fulfils O-RAN security tests, requirements and recommendations provided by O-RAN ALLIANCE. - - Vendors SHOULD ensure and prove that their software or hardware meets the needs of many national and international cybersecurity regulations, such as the Cyber Act, GDPR, etc. - - Vendors SHOULD provide risk assessment, secure code review, penetration testing, vulnerability analysis and hardening guidelines for their O-RAN components. -- ZT Tenets: ZT-1, ZT-5, ZT-7 - -### 8.1.11 SP-PRV Privacy - -- In O-RAN, the privacy of end users SHOULD be protected. The privacy of end users can be divided into data privacy, identity privacy and personal information privacy. Most Communication services are to gather data and personal information around end users, which may reveal information sensitive to their privacy. Adversaries could further extract more personal information about end users, such as UE priority, location information, trajectory, and preference. -- ZT Tenets: ZT-1, ZT-2, ZT-3, ZT-4, ZT-5, ZT-6, ZT-7 - -### 8.1.12 SP-SLC Continuous security development, testing, logging, monitoring and vulnerability handling - -- Continuous development and continuous integration (CD/CI) with continuous regression testing and software security auditing SHOULD be implemented. -- Relevant activities events SHOULD be logged and logs collected SHOULD be analyzed in real time for the identification of potential security attacks and for security auditing. -- Continuous monitoring SHOULD be implemented to verify that the wanted security state is maintained throughout the lifecycle of deployed O-RAN components. -- Vulnerability management SHOULD be in place with intelligence to continuously track, identify and remediate vulnerable applications. Vendors SHOULD keep track of any new vulnerabilities discovered and is ready to act on customer product security incidents and reported security issues affecting O-RAN components. -- ZT Tenets: ZT-1, ZT-4, ZT-5, ZT-6, ZT-7 - -### 8.1.13 SP-ISO Robust Isolation - -- In a multi-vendor environment, intra-domain host isolation SHOULD be enforced. In the same host, VMs, CNs, virtualization/container layer, CPU, storage, and network security isolation of resources SHOULD be ensured by implementing system security orchestration, segmentation, lifecycle management, time scheduling, monitoring and audit on the management, signaling, control and data planes, and the execution of virtualized O-RAN components. -- ZT Tenets: ZT-1, ZT-2, ZT-3, ZT-4, ZT-5, ZT-7 - -### 8.1.14 SP-PHY Physical security - -- The O-RAN system SHOULD be located at physically secure environment in a way that minimizes the risk of resource theft and destruction. It SHOULD support secure storage of sensitive data (cryptographic keys and configuration data), execution of sensitive functions (encryption/decryption, authentication), and execution of boot and update processes. -- Special attention SHOULD be paid to the site intrusion and physical access threats against O-RU sites. Consequently O-RU equipment SHOULD disable all unnecessary physical and logical ports, protocols and interfaces. In addition, secure physical connections to O-RU for O&M operations SHOULD be implemented (e.g. secure laptop with secure credentials). -- ZT Tenets: ZT-1, ZT-2, ZT-3, ZT-4, ZT-5, ZT-6, ZT-7 - -### 8.1.15 SP-CLD Secure cloud computing and virtualization - -- Defense methods SHOULD be implemented: virtual machine-based intrusion detection, virtual machine-based isolation, virtual machine-based kernel protection, virtual machine-based access control, and virtual machine-based trusted computing. -- ZT Tenets: ZT-1, ZT-2, ZT-3, ZT-4, ZT-5, ZT-6, ZT-7 - -### 8.1.16 SP-ROB Robustness - -- The O-RAN system SHOULD not only ensure the robustness of software or hardware resources, but also guarantee the robustness of the cognitive radio channel for meeting the QoS of communication services required by users. In some scenarios, the robustness of spectrum sensing SHOULD be enhanced when some sensing nodes (e.g., O-RU) easily malfunction. Robustness is an essential consideration for overcoming the security threats caused by jamming, DoS or DDoS attacks. -- ZT Tenets: ZT-1, ZT-2, ZT-3, ZT-4, ZT-5, ZT-6, ZT-7 - -### 8.1.17 SP-IDM O-Cloud ID secure management - -- To counter threats associated with ID reuse, mismanagement, and redundancy, the O-Cloud should employ robust strategies for ID generation, validation, and lifecycle management. Properly managed IDs reduce risks of data inconsistencies, unauthorized access, and operational inefficiencies. -- ZT Tenets: ZT-1, ZT-3, ZT-4, ZT-5, ZT-6, ZT-7 - -## 8.2 Coverage Threats - Security principles - -The table below illustrates how threats are covered by security principles. It outlines the list of security principles contributing to counter threats. - -**Table Security principles-6 : Coverage Security principles-Threats (1/4)** - -| SP | Threats | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -|-----------|------------|------------|------------|------------|-------------|--------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|----------|-----------|-----------|-----------|--------------|--------------|---------------|--------------|---------------|--------------|---------------|--------------| -| | T-O-RAN-01 | T-O-RAN-04 | T-O-RAN-07 | T-O-RAN-08 | T-FRHAUL-01 | T-FRHAUL-01A | T-FRHAUL-02 | T-FRHAUL-03 | T-MPLANE-01 | T-MPLANE-02 | T-MPLANE-03 | T-SPLANE-01 | T-SPLANE-02 | T-SPLANE-03 | T-SPLANE-04 | T-SPLANE-05 | T-CPLANE-01 | T-CPLANE-02 | T-UPLANE-01 | T-UPLANE-02 | T-UPLANE-03 | T-UPLANE-04 | T-ORU-01 | T-O-RU-02 | T-O-RU-03 | T-O-RU-04 | T-NEAR-RT-01 | T-NEAR-RT-02 | T-NEAR-RT-02A | T-NEAR-RT-03 | T-NEAR-RT-03A | T-NEAR-RT-04 | T-NEAR-RT-04A | T-NEAR-RT-05 | -| SP-AUTH | x | | | | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | | x | x | x | | x | x | x | x | x | x | x | -| SP-ACC | x | | | | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | | x | x | x | | | | x | x | x | x | | -| SP-CRYPTO | x | x | | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | | x | x | | x | x | x | x | x | x | x | -| SP-TCOMM | | x | | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | | | | | | | | x | x | x | x | -| SP-SS | x | | x | x | | | | | | | | | | | | | | | x | x | x | x | | x | x | x | | | | x | x | x | x | | -| SP-SB | x | | | | | | | | | | | | | | | | | | | | | | | | | | x | x | x | | | | | x | -| SP-UPDT | x | x | | | | | | | | | | | | | | | | | | | | | | | | | | | x | x | | | | x | -| SP-RECO | | x | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -| SP-OPNS | | | | | | | | | | | | | | | | | | | | | | | | | | | x | x | x | | | | | x | -| SP-ASSU | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | | | | | | x | x | x | x | x | x | x | | | | x | -| SP-PRV | | | | x | | | | | | | | | | | | | | | | | | | | | | | x | x | x | x | x | x | x | x | -| SP-SLC | x | x | x | | | | | | | | | | | | | | | | | | | | | | | | x | x | x | | | | | x | -| SP-ISO | x | | x | | | | | | | | | | | | | | | | | | | | | | | | x | x | x | | | | | x | -| SP-PHY | x | | | x | | | | | | | | | | | | | | | | | | | x | x | x | x | | | | | | | | | -| SP-CLD | | | | x | | | | | | | | | | | | | | | | | | | | | | | x | x | x | | | | | x | -| SP-ROB | | x | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - -Table Security principles-7 : Coverage Security principles-Threats (2/4) - -| SP | Threats | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -|-----------|---------------|---------------|---------------|---------------|---------------|-----------|------------|------------|------------|-----------|-----------|------------|------------|------------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|-----------|----------|-----------|----------|----------|----------|-------------|-------------|-------------|-------------|-------------|--------------|-------------|-------------| -| | T-NONRTRIC-01 | T-NONRTRIC-02 | T-NONRTRIC-03 | T-NONRTRIC-04 | T-NONRTRIC-05 | T-vAPP_01 | T-xAPP-01A | T-xAPP_01R | T-vAPP_01C | T-xAPP-02 | T-xAPP_03 | T-vAPP_03A | T-vAPP_03C | T-vAPP_03R | T-vAPP_04 | T-vAPP_05 | T-vAPP_06 | T-vAPP_07 | T-rAPP-02 | T-rAPP-03 | T-rAPP-04 | T-rAPP-05 | T-rAPP-06 | T-rAPP-07 | T-PNF-01 | T-PNF-01A | T-SMO-01 | T-SMO-02 | T-SMO-03 | T-ApplCM-01 | T-ApplCM-02 | T-ApplCM-03 | T-ApplCM-04 | T-ApplCM-05 | T-ApplCM-05A | T-ApplCM-06 | T-ApplCM-07 | -| SP-AUTH | x | | | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | | | x | | | x | x | x | x | x | x | x | x | -| SP-ACC | x | | | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | | x | | x | x | x | x | x | x | x | x | -| SP-CRYPTO | x | | | | | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | | | | | | x | | | x | x | | x | x | -| SP-TCOMM | | | | | | | | | | | | | | | x | x | x | | | | | | | | | | | | | | | | | | | | | -| SP-SS | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | x | x | x | | | | x | x | -| SP-SB | | x | x | | | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | | | | x | x | x | | | | x | x | -| SP-UPDT | | | | | | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | | | | x | x | -| SP-RECO | | | | | | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | | | | | x | x | | x | | | x | x | x | -| SP-OPNS | | x | x | | | | | | | | | | | | | | | | | | | | | | | | | | | x | x | x | x | x | x | x | x | -| SP-ASSU | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | -| SP-PRV | | x | x | | | | | | | | | | | | x | x | x | | | | | | | | | | | | | | | | | | | | | -| SP-SLC | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | -| SP-ISO | | x | x | | | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | | | | | | x | x | x | x | x | x | x | x | -| SP-PHY | | | | | | | | | | | | | | | | | | | | | | | | | x | x | | | | | | | | | | | | -| SP-CLD | | x | x | x | x | x | x | x | x | x | x | x | x | x | | | | | x | x | x | x | x | x | | | | | | x | x | x | x | x | x | x | x | -| SP-ROB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - -Table Security principles-8 : Coverage Security principles-Threats (3/4) - -| SP | Threats | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -|-----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|---------|---------|---------|---------|--------------|---------|---------|------------|------------|----------|----------|----------|----------|----------|----------|------------|------------|------------|------------|----------------|----------------|------------|------------|------------|------------|------------|------------|------------|------------|--------------|--------------|--------------| -| | T-GEN-01 | T-GEN-02 | T-GEN-03 | T-GEN-04 | T-VNF-01 | T-VNF-02 | T-VNF-03 | T-VNF-04 | T-VNF-05 | T-VNF-06 | T-VNF-07 | T-VNF-08 | T-IMG-01 | T-IMG-02 | T-IMG-03 | T-IMG-04 | T-VM-01 | T-VM-02 | T-VM-03 | T-OS-01 | T-CONTAIN-01 | T-HW-01 | T-HW-02 | T-ADMIN-01 | T-ADMIN-02 | T-AAI-01 | T-AAI-02 | T-AAI-03 | T-AAI-04 | T-AAI-05 | T-AAI-06 | T-CLOUD-01 | T-CLOUD-02 | T-CLOUD-03 | T-CLOUD-04 | T-OPENSTACK-01 | T-OPENSTACK-02 | T-DU/CU-01 | T-DU/CU-02 | T-DU/CU-03 | T-DU/CU-04 | T-RADIO-01 | T-RADIO-02 | T-RADIO-03 | T-RADIO-04 | T-AIML-PD-01 | T-AIML-PD-02 | T-AIML-PD-03 | -| SP-AUTH | X | X | X | X | X | | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | | | | | | | | | | X | X | X | X | X | X | X | -| SP-ACC | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | | | | | | | | | | | | | | X | X | X | -| SP-CRYPTO | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | | | | | | | | | | | | X | X | X | | | | | | X | X | X | -| SP-TCOMM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -| SP-SS | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | | | | | | | | | | | | | | | | | -| SP-SB | X | X | X | X | X | | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | | | | | | X | X | X | | | | | | X | X | X | -| SP-UPDT | X | X | X | X | X | | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | | | | X | X | | | | | | | | | X | X | X | -| SP-RECO | X | X | X | X | X | | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | | | | | | | | | | X | X | X | X | X | X | X | -| SP-OPNS | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | | | | | | | | | | X | X | | | | | | | | | | | | -| SP-ASU | X | X | X | X | X | | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | | | | X | X | X | X | X | X | X | X | X | X | X | X | X | -| SP-PRV | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -| SP-SLC | X | X | X | X | X | | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | | | | X | X | | | | | | | | | X | X | X | -| SP-ISO | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | | | | | | | | | | | | | | X | X | X | - -Image: O-RAN ALLIANCE logo - -O-RAN.WG11.TR.Threat-Modeling-R005-v08.00 - -| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -|----------|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|--|--|--|--|--|---|---|---|---|---|---|---|--|---|---|---|--| -| SP-PHY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | X | X | X | X | | | | | | | | | -| SP-CLD | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | | | | | | | | | | | | | | | | X | X | X | | -| SP-PROB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | X | X | X | | | | | | -| SP-SPIDM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | X | X | X | | | | | | | | | | | | | | | | | | - -**Table Security principles-9 : Coverage Security principles-Threats (4/4)** - -| SP | Threats | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -|-----------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|---------------|---------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|--------------|-----------|---------|--------|---------|---------|---------|---------|---------|---|--|--|--|--| -| | T-AIML-ME-01 | T-AIML-ME-02 | T-AIML-ME-03 | T-AIML-ME-04 | T-AIML-ME-02 | T-AIML-ME-03 | T-AIML-IM-01 | T-AIML-IM-02 | T-AIML-IM-03 | T-AIML-IM-04 | T-AIML-MOI-01 | T-AIML-MOI-02 | T-AIML-SC-01 | T-AIML-SC-02 | T-AIML-SC-03 | T-AIML-SC-04 | T-AIML-SC-05 | T-AIML-SC-06 | T-AIML-OL-01 | T-AIML-OL-02 | T-AIML-MD-01 | T-AIML-MP-02 | T-AIML-MD-02 | T-AIML-MD-04 | T-AIML-MS-01 | T-AIML-MS-02 | T-AIML-TL-01 | T-AIML-TL-02 | T-AIML-TL-03 | T-AIML-TL-04 | T-AIML-EL-01 | T-AIML-EL-02 | T-AIML-EL-03 | T-AIML-EV-01 | T-AIML-EV-02 | T-AIML-EV-03 | T-ORAN-10 | T-TC-01 | T-M-01 | T-E2-01 | T-E2-02 | T-E2-03 | T-V1-01 | T-V1-02 | | | | | | -| SP-AUTH | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | X | | X | X | X | X | X | X | | | | | -| SP-ACC | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | X | X | X | X | X | X | X | X | | | | | -| SP-CRYPTO | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | X | | X | X | X | X | X | X | | | | | -| SP-TCOMM | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | X | | | X | | | | X | | | | | -| SP-SS | X | X | X | | | | X | X | X | | | | | | | | | | X | X | X | X | X | X | X | X | | | | | | | | | | | | | | | X | | | X | | | | | | -| SP-SB | X | X | X | X | X | X | | | | | | | X | X | X | X | X | X | X | X | | | | X | X | X | X | X | X | X | X | X | X | X | X | X | | X | | | | | | | | | | | | -| SP-UPDT | X | X | X | X | X | X | | | | | | | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | | | X | X | X | X | X | X | | | | | -| SP-RECO | X | X | X | X | X | X | X | X | X | X | | | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | X | | X | | | | | | | | | | | | - -© 2026 by the O-RAN ALLIANCE e.V. Your use is subject to the copyright statement on the cover page of this specification. - -163 - -![O-RAN ALLIANCE logo](84982d23836d5e77911a6ddd3332b7a5_img.jpg) - -O-RAN.WG11.TR.Threat-Modeling-R005-v08.00 - -| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -|---------|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---| -| SP-OPNS | | | | | | | | | x | | | | | | | | | x | | | x | x | x | x | | | | | | | | | | | | | | | | | | | | -| SP-ASSU | x | x | x | x | x | x | | | x | | | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | | | | x | x | x | x | x | x | -| SP-PRV | x | x | x | | | | x | x | x | x | x | x | | | | | | | | | x | x | x | x | x | x | | | | | | | | | | | | | | | | | | -| SP-SLC | x | x | x | x | x | x | | | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | | x | x | x | x | x | x | -| SP-ISO | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | | x | | | | | | | -| SP-PHY | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -| SP-CLD | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | | | | x | x | x | x | x | x | x | x | x | x | x | x | | | x | x | x | x | x | x | -| SP-ROB | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -| SP-IDM | | | | | | | | | | x | x | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - -© 2026 by the O-RAN ALLIANCE e.V. Your use is subject to the copyright statement on the cover page of this specification. 164 - -![O-RAN ALLIANCE Logo](0f7b6492f9528be3f23fa03b5e12274a_img.jpg) -O-RAN.WG11.TR.Threat-Modeling-R005-v08.00 - - ---- - -# 9 Risk assessment - -After identifying the list of assets, threats and vulnerabilities, the next step is the risk assessment. The main concepts of risk assessment are illustrated in the following figure. - -![Figure Risk assessment -15 : Main concepts of risk assessment](1d648bacf7b4f1d0c2fbd884f070e151_img.jpg) - -``` - - graph TD - Threat --- Asset - Vulnerability --- Asset - Asset --- Event - Asset --- Consequence - Event --- Consequence - Event --- Likelihood - Consequence --- Risk - Likelihood --- Risk - Treatment --- Risk - subgraph " " - Event - Consequence - Likelihood - end - -``` - -Detailed description: A conceptual diagram showing 'Asset' at the center. 'Threat' and 'Vulnerability' are connected to 'Asset' from above. Below 'Asset', a dashed box contains 'Event', 'Consequence', and 'Likelihood'. 'Asset' connects to 'Event' and 'Consequence'. 'Event' connects to 'Consequence' and 'Likelihood'. To the right, 'Treatment' and 'Risk' are shown. 'Consequence', 'Likelihood', and 'Treatment' all point towards 'Risk'. - -Figure Risk assessment -15 : Main concepts of risk assessment - -**Figure Risk assessment -15 : Main concepts of risk assessment** - -The criticality of the identified threats in clause 7.4 were assessed based on the severity (consequence) and the likelihood of occurrence. Indications of severity level for each threat are given whether they are considered as high, medium, or low. This severity is a global perception of the risk based on its impacts. In practice, it varies strongly depending on the use cases and deployment/configuration models of the O-RAN system. - -Moreover, the type of loss (availability, integrity and/ or confidentiality) has been assessed for each threat. - -## 9.1 Determination of severity level process - -The process followed to determine the severity level resulting from threats that successfully exploit vulnerabilities is based on Table 9-1 which includes the definition in terms of Privacy, Confidentiality, Integrity, Availability of the three severity levels 'Low', 'Medium' and 'High' shown here as green, yellow and red. - -Table 9-1 defines what "low," "medium" and "high" means. - -The severity of an impact is expressed as follows: - -- Level of impact for various threats on the properties Privacy, Confidentiality, Integrity, and Availability -- Scale of impact, depending on the number of affected O-RUs and /or O-DUs. -- Scale of impact depending on the Clock Model and Synchronization Topology configurations LLS-C1, LLS-C2, LLS-C3 and LLS-C4 [i.10]. -- Adverse impacts depending on whether or not existing requirments and controls are already defined in the O-RAN requirments specifications. - -**Table Risk assessment -10 : Severity rating** - -| Severity level | Privacy | Confidentiality | Integrity | Availability | Number of affected O-RUs/O-DUs (Only for Threats on O-RU, O-DU, FH interface) | Clock Model and Synchronization Topology configurations (only for Threats on S-PLANE) | Adverse impacts | -|----------------|-----------------------------------------------------------------------|----------------------------------------------------------------------------------|-----------------------------------------------------|------------------------------------------------------------------|-------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------------------------------| -| Low | Disclosure of personal data which, with aggregation or processing, is | Disclosure of information for internal use. No specific impact on its disclosure | Minor/Unnoticeable effect on system behavior/output | Brief Interruption in operations. (Estimated in secs/mins/hours) | One O-DU is affected with its related O- | DoS attacks on LLS-C2 | Already existing requirements and controls are defined | - ---- - -© 2026 by the O-RAN ALLIANCE e.V. Your use is subject to the copyright statement on the cover page of this specification. -165 - -| | | | | | | | | -|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|--------------------------------------------------------------|------------------------------------------------------------------|------------------------------------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | unlikely to reveal unique subscriber's identity. | | | | RU | DoS attacks on LLS-C4 | in the O-RAN specifications to prevent, or at least significantly impede, the vulnerability from being exercised. Existing requirements and controls are only efficient to protect from both internal and external threats. | -| Medium |

Disclosure of personal data (according to GDPR) which CAN be processed or aggregated to uniquely identify subscribers.

NOTE: Personal data in GDPR means any information relating to an identified or identifiable natural person ('data subject'); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.

| Disclosure of privileged information Access credentials/ configuration data, etc. | Alteration of some system functionality and features/output. | Short-term Interruption in operations. (Estimated in hours/Days) | One O-DU is affected with its related multiple O-RUs | DoS attacks on LLS-C1 | Already existing requirements and controls are defined in the O-RAN specifications to prevent, or at least significantly impede, the vulnerability from being exercised. Existing requirements and controls are only efficient to protect from external threats. | -| High |

Disclosure of sensitive personal data (GDPR special category).

NOTE: Special data category in GDPR: data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for uniquely identifying a natural person, data

| Disclosure of high value information, trade secrets, IP, mission critical data, master-keys, etc. | Complete change in normal System functioning | Prolonged interruption of operations. (Estimated in days/Weeks) | Several O-DUs and O-RUs are affected | DoS attacks on LLS-C3 | No existing requirements and controls in the ORAN specifications yet to protect from internal and/or external threats | - -| | | | | | | | | -|--|-----------------------------------------------------------------------------------------|--|--|--|--|--|--| -| | concerning health or data concerning a natural person's sex life or sexual orientation. | | | | | | | -|--|-----------------------------------------------------------------------------------------|--|--|--|--|--|--| - -1 - -2 **NOTE 1:** The severity level depends on the number of affected RUs and O-DUs. The severity level is consequently - 3 'Low' in case of one affected O-RU, 'Medium' in case of one affected O-DU with its related multiple O-RUs, and 'High' - 4 for multiple affected O-DUs-O-RUs. Operators conducting a full risk analysis according to this report should conduct a - 5 use case-based analysis taking into account the likelihood and the real deployment of the O-RAN system. - -6 **NOTE 2:** - -###### 7 **Configuration LLS-C1** - -8 In LLS-C1, the network timing is distributed from O-DU to O-RU via direct connection between O-DU site and O-RU - 9 site. O-DU is acting as a master and directly synchronizes O-RU. - -- 10 • DoS attacks against the master clock: There are two scenarios: - - 11 1. Scenario 1: One O-RU is served by O-DU, therefore only one O-RU is affected. Consequently, the - -12 severity level is 'Low'. - - 13 2. Scenario 2: Multiple O-RUs are served by O-DU, therefore all those O-RUs are affected as the - -14 connection between O-DU and O-RU is point-to-point. Consequently, the severity level is 'Low'. - -### 15 **Configuration LLS-C2** - -16 In LLS-C2, the network timing is distributed from O-DU to O-RU between O-DU sites and O-RU sites. One or more - 17 Ethernet switches are allowed in the fronthaul network. O-DU acting as master to distribute network timing toward O- - 18 RU. - -- 19 • DoS attacks against the master clock within the O-DU may affect one or multiple O-RUs. In this configuration, - -20 a neighbor O-DU could act a backup and play the role of a master to distribute network timing to all the RUs - -21 belonging to the affected O-DU by reconfiguring the network of switches. Consequently, the severity level is - -22 'Low'. - -23 - -### 24 **Configuration LLS-C3** - -25 Frequency and time distribution is made by the fronthaul network itself (not by the O-DU). One or more PRTC/T-GM - 26 are implemented in the fronthaul network to distribute network timing toward O-DU and O-RU. - -- 27 • DoS attacks against the master clock within the fronthaul network may affect multiple O-DUs with their - -28 related O-RUs. Consequently, the severity level is 'High'. - -29 - -### 30 **Configuration LLS-C4** - -31 Local PRTC timing that provides time synchronization to the O-RU (it could be embedded in the O-RU). - -- 32 • DoS attacks against the master clock may affect only one O-RU. Consequently, the severity level is 'Low'. - -33 According to what we described in the here above two notes, T-SPLANE-01 has been split in Table 9-4 according to - 34 the Clock Model and Synchronization Topology configurations C1, C2, C3, and C4. - -35 **NOTE:** Adverse impacts: This factor depends on the normative O-RAN security requirements in the security - 36 requirements specification. For a threat without any requirement in front of it, the adverse impacts level is High. It is - 37 Medium or Low for a threat with related security requirements (see column 'Assuptions') helping in reducing its - 38 impact. - -## 9.2 Determination of likelihood level process - -The process followed to determine the likelihood level resulting from threats that successfully exploit vulnerabilities is based on Table 9-2 which includes the relevant factors that are considered. For each factor, three levels ‘Low’, ‘Medium’ and ‘High’ are shown in Table 9-2 as green, yellow and red. - -Table 9-2 defines what “low,” “medium” and “high” means. - -The likelihood level is expressed by four factors as follows: - -- Adverse impacts: This factor depends on the existing normative O-RAN security requirements and controls. For example, the level is high in case no available O-RAN security requirements and controls in the O-RAN security specifications. In the risk assessment Table 9-4 in the column ‘Assumptions’, some of the agreed security controls by the O-RAN ALLIANCE have been stated for some threats as arguments for justifying the likelihood levels ‘Low’ or ‘Medium’. This means that the likelihood level is estimated at Low’ or ‘Medium’, provided that the security controls are in place. - -**NOTE:** This factor is used to determine the likelihood level for the most categories of threats. It is also used as a relevant factor for severity for some categories of threats, in particular the O-Cloud threats category. - -- Threat event initiation: This factor takes into consideration the capabilities that attackers possess and the potential entry points to exploit a vulnerability and initiate an attack. For example, it is high if an attack can be initiated from internet or untrusted network. -- Exposure: This factor is related to the number of external interfaces and/or services that are exposed to an attacker. -- Zero Trust Approach: Likelihood scoring considers a zero-trust architecture which protects against internal threat actors. Likelihood scores are higher for a zero-trust architecture (ZTA) because internal threats should be considered in addition to external threats. In a ZTA it cannot be assumed that perimeter defense is sufficient. As a result, scored Likelihood = Medium, at a minimum. Reconnaissance type attacks can be scored Likelihood = High while damaging/availability attacks can be scored Likelihood = Medium. The reason is that threat actors are less likely to perform damaging attacks that are quickly and easily detected. Advanced Persistent Threats (APTs) typically move laterally in anonymous fashion to prevent detection while providing reconnaissance (see O-RAN.SFG.Non-RT-RIC-Security-TR-v01.00). - -**Table Risk assessment -11 : Likelihood rating** - -| Scale | Factors | Measure of Likelihood | -|--------|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| High | Adverse impacts | No existing requirements and controls in the ORAN specifications yet to protect from internal and/or external threats | -| | Threat event initiation | Attack can be launched from the internet or untrusted network | -| | Exposure | System has a large amount of exposed interfaces (e.g. ORAN interfaces, multiple O-DU, multiple O-RU, multi administrators/customers) | -| | ZTA | Reconnaissance type attacks | -| | Open-source/COTS support |
  • • No vulnerability handling and patch management in place: Several CVE have already been discovered; no regular patches provided to fix the detected vulnerabilities
  • • Use of open-source module not supported by a broader community
  • • Use of non popular COTS product
| -| Medium | Adverse impacts | Already existing requirements and controls are defined in the O-RAN specifications to prevent, or at least significantly impede, the vulnerability from being exercised. Existing requirements and controls are only efficient to protect from external threats. | -| | Threat event initiation | Malicious user needs to have direct access to the target system | -| | Exposure | System has a medium amount of exposed interfaces (e.g. ORAN interfaces, one O-DU, multiple O-RU) | - -| | | | -|------------|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | ZTA | Damaging/availability type attacks | -| | Open-source/COTS support |
  • Vulnerability handling and patch management in place but not efficient: Several CVE have already been discovered; no timely patches provided to fix the discovered vulnerabilities
  • Use of open-source module moderately supported by a broader community
| -| Low | Adverse impacts | Already existing requirements and controls are defined in the O-RAN specifications to prevent, or at least significantly impede, the vulnerability from being exercised. Existing requirements and controls are only efficient to protect from both internal and external threats. | -| | Threat event initiation | The malicious user needs to have administrative or elevated privileges in the target system (external having internal privileges or internal having internal privileges) | -| | Exposure | Slightly exposed to external systems (e.g. one O-DU, one O-RU) (least privilege approach) | -| | ZTA | Perimeter defenses are sufficient. No potential for internal threats | -| | Open-source/COTS support |
  • Component supporting open-source module: a broader community is investing in
  • COTS modules are popular and widely used in critical infrastructure
| - -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15 -16 - -## 9.3 Evaluation of the risks process - -The following risk assessment matrix is used to assess the risk score. The matrix takes as input two estimated qualitative inputs: (i) likelihood and (ii) the severity. One axis representing the probability of a risk scenario occurring and the other representing the damage it will cause (Severity). In the middle, you have scores based on their combined totals. - -Using this formula $RISK = \text{Severity} \times \text{Likelihood}$ by a simple multiply the severity and likelihood scores to obtain the final risk score as shown in Table 9-3. - -For example, if the estimated likelihood of a threat is low and the corresponding severity is high, then the risk is medium. - -**Table Risk assessment -12 : Risk assessment matrix** - -| | | | | | -|-----------------|----------|----------|----------|-------------------| -| Severity | 3-High | 3-Medium | 6-High | 9-High | -| | 2-Medium | 2-Low | 4-Medium | 6-High | -| | 1-Low | 1-Low | 2-Low | 3-Medium | -| | | 1-Low | 2-Medium | 3-High | -| | | | | Likelihood | - -## 9.4 Risk assessment output - -The following is the risk assessment output table which illustrates the different threats along with their impacts, the type of loss, the perceived severity/likelihood levels and the risk scoring. - -17 -18 -19 -20 - -1 -2 - -**Table Risk assessment -13 : Risk Assessment** - -| THREAT ID | RISK DESCRIPTION | IMPACT DESCRIPTION | CIA | SEVERITY LEVEL | Likelihood LEVEL | Applied factors | Rationale | Considered Assumptions | Risk Score | -|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|----------------|------------------|----------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|------------| -| T-O-RAN-01 | An attacker exploits insecure designs or lack of adoption of security controls (e.g. hardening) in O-RAN architecture elements causing:
- unauthorised access
- Privacy issues | Unauthenticated/unauthorized access of the O-RAN architecture element leads to compromised performance and/or function/service, lateral attack towards other O-RAN architecture element(s) from inside, and loss/stolen/tampering of sensitive data | | High | High |
  • Exposure (High):
  • Adverse impacts (High)
|
  • - High impact: Potential for system-wide compromise-
  • High likelihood: Many interfaces are exposed to attackers
| | High | -| T-O-RAN-04 | An attacker disrupts O-RAN service availability using DDoS, protocol exploitation, or insecure resource management, causing congestion and service outages. | Service disruption due to flooding, malformed requests, or IoT-based botnets results in loss of access, degraded performance, and operational failures. | A | High | High |
  • Threat event initiation (High)
  • Adverse impacts (High)
|
  • - High impact: Disrupts network synchronization and critical service functions
  • - High likelihood: Many exposed interfaces and components susceptible to overload
| | High | -| T-O-RAN-07 | An attacker hides malicious activities by exploiting insufficient logging, auditing, and traceability mechanisms across O-RAN architecture elements. | Attackers tamper with, delete, or manipulate logs to evade detection, making forensic investigations difficult. This can delay security responses, and allow threats to persist. | | Medium | Medium |
  • Threat event initiation (Medium)
  • Adverse impacts (Medium)
|
  • - Medium impact: Requires internal access to manipulate logs.
  • - Medium likelihood: Misconfigured or inadequate logging mechanisms are common.
| Authentication procedures, patch management regular programmed update, vulnerability handling/regul ar scanning, SBOM are in place | Medium | -| T-O-RAN-08 | An attacker compromises O-RAN data integrity, and confidentiality | Data breaches, unauthorized modifications | C, I | High | Medium |
  • Threat event initiation (Medium)
  • Adverse impacts (Medium)
|
  • - High impact: Potential unauthorized control over critical data and services.
  • - Medium likelihood: Existing encryption mechanisms
| | High | - -| | | | | | | | | | | -|---------------|----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------|------|--------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|--------| -| | | | | | | | provide some protection. | | | -| T-FRHAUL-01 | An attacker penetrates O-DU and beyond through O-RU (bidding-down attack) | Data tampering and information disclosure; | C, I | High | Medium |
  • Threat event initiation (Medium)
  • Adverse impacts (Medium)
  • Exposure (Medium)
| System has an amount of exposed interfaces: multiple O-DU, multiple O-RU, FH interface. It is a possible attack, however needs physical access and sophistication to execute | | High | -| T-FRHAUL-01 A | An attacker penetrates O-DU and beyond through O-RU (bidding-down attack) | Spoofing | C, I | High | Medium |
  • Threat event initiation (Medium)
  • Adverse impacts (Medium)
  • Exposure (Medium)
| System has an amount of exposed interfaces: multiple O-DU, multiple O-RU, FH interface. It is a possible attack, however needs physical access and sophistication to execute | | High | -| T-FRHAUL-02 | Unauthorized access to the Open Front Haul Ethernet L1 physical layer interface (cables and connections) | It provides a means to launch attacks on the confidentiality of the Open Front Haul system. | C | High | Low |
  • Threat event initiation (Low)
  • Adverse impacts (High)
| It is a possible attack, however needs physical access and sophistication to execute | | Medium | -| T-FRHAUL-03 | Unauthorized access to the Open Front Haul Ethernet L1 physical layer interface (cables and connections) | It provides a means to launch attacks on the availability of the Open Front Haul system. | A | High | Low |
  • Threat event initiation (Low)
  • Adverse impacts (High)
| It is a possible attack, however needs physical access and sophistication to execute | | Medium | -| T-MPLANE-01 | An attacker attempts to intercept the Fronthaul (MITM) over M Plane to obtain protected information | Passive wiretapping | C | Medium | Low |
  • Threat event initiation (Low)
  • Adverse impacts (Medium)
| It is a possible attack, however needs physical access and sophistication to execute | TLS with PKI is supported, it is up to MNO, the likelihood is low provided that MNOs use TLS over the M-Plane | Low | -| T-MPLANE-02 | An attacker attempts to intercept the Fronthaul (MITM) over M Plane to alter m-plane data | Intercepting and modifying of the M plane messages. | I | Medium | Low |
  • Threat event initiation (Low)
  • Adverse impacts (Medium)
| It is a possible attack, however needs physical access and sophistication to execute | TLS with PKI is supported, it is up to MNO, the likelihood is low provided that MNOs use TLS over the M-Plane | Low | -| T-MPLANE-03 | An attacker attempts to intercept the Fronthaul (MITM) over M Plane to disrupt services | Denial of service | A | Medium | Low |
  • Threat event initiation (Low)
  • Adverse impacts
| It is a possible attack, however needs physical access and sophistication to execute | TLS with PKI is supported, it is up to MNO, the likelihood | Low | - -| | | | | | | (Medium) | | is low provided that MNOs use TLS over the M-Plane | | -|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--------|--------|---------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| -| T-SPLANE-01-C1 (one O-RU scenario) | DoS attack on an O-DU acting as master to distribute network timing toward O-RU based on point-to-point connection in LLS-C1. In this scenario, only one O-RU is connected to O-DU, therefore only that O-RU is affected. | This attack may cause performance degradation or interruption of services to only one O-RU that rely on accurate time from the affected O-DU. The severity level is consequently 'Low'. | A | Low | Low |
  • Exposure (Low)
  • Threat event initiation (Medium)
| Slightly exposed to external systems: one O-RU. It is a possible attack, however needs physical access and sophistication to execute | Access control on the CUSM-Plane that mitigates unauthorized access by an insider are in place. 802.1x protocol is supported it can reduce the likelihood of this attack. | Low | -| T-SPLANE-01-C1 (multiple O-RUs scenario) | DoS attack on an O-DU acting as master to distribute network timing toward O-RU based on point-to-point connection in LLS-C1. In this scenario, multiple O-RUs are connected to O-DU, therefore those O-RUs are affected. | This attack may cause performance degradation or interruption of services to all the RUs that rely on accurate time from the affected O-DU. The severity level is consequently 'Medium'. | A | Medium | Medium |
  • Exposure (Medium)
  • Threat event initiation (Medium)
| System has a medium amount of exposed interfaces: multiple O-RUs. It is possible attack, however needs physical access and sophistication to execute | | Medium | -| T-SPLANE-01-C2 | DoS attack on an O-DU acting as master to distribute network timing toward O-RU in LLS-C2. One or more Ethernet switches are allowed between the central site (hosting O-DUs) and the remote sites (hosting O-RUs). | This attack may cause performance degradation or interruption of services to all the RUs that rely on accurate time from the affected O-DU. In this configuration, a neighbor O-DU could act a backup and play the role of a master to distribute network timing to all the RUs belonging to the affected O-DU by reconfiguring the network of switches. The severity level is consequently 'Low'. | A | Low | Medium |
  • Exposure (Medium)
  • Threat event initiation (Medium)
| System has a medium amount of exposed interfaces. It is a possible attack, however needs physical access and sophistication to execute | Access control on the CUSM-Plane that mitigates unauthorized access by an insider are in place. 802.1x protocol is supported it can reduce the likelihood of this attack. | Low | -| T-SPLANE-01-C3 | DoS attack against a Master clock in the LLS-C3 configuration | In this configuration, the frequency and timing distribution is made by the fronthaul network (not by O-DU). DoS attack against a master clock may cause performance degradation or interruption of services to all the RUs and DUs that rely on accurate time from the affected master clock in the fronthaul network. The severity level is consequently 'High'. | A | High | Medium |
  • Exposure (Medium)
  • Threat event initiation (Medium)
| System has a medium amount of exposed interfaces. It is a possible attack, however needs physical access and sophistication to execute | | High | -| T-SPLANE-01- | DoS attack against a Master clock in the | In this configuration, the time source could be locally embedded in the RU itself. DoS | A | Low | Low |
  • Exposure (Low)
| Slightly exposed to external systems: one O-RU. It is a | Access control on the CUSM- | Low | - -| | | | | | | | | | | -|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|------|--------|---------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| -| C4 | LLS-C4 configuration | attack in the time source may cause performance degradation or interruption of services to only one O-RU where the time source is embedded. The severity level is consequently 'Low'. | | | | • Threat event initiation (Medium) | possible attack, however needs physical access and sophistication to execute | Plane that mitigates unauthorized access by an insider are in place. 802.1x protocol is supported it can reduce the likelihood of this attack. | | -| T-SPLANE-02 | Impersonation of a Master clock (Spoofing) within a PTP network with a fake ANNOUNCE messages | Degradation in the accuracy of time may cause DoS to applications on all the RUs that rely on accurate time, potentially bringing down the cell. A cell outage caused by misaligned time, may further impact performance in connected neighboring cells. | A | High | Low | • Threat event initiation (Medium)
• Adverse impacts (Low) | Existing controls are in place to prevent, or at least significantly impede, the vulnerability from being exercised. It is a possible attack, however needs physical access and sophistication to execute | Access control on the CUSM-Plane that mitigates unauthorized access by an insider are in place. 802.1x protocol is supported it can reduce the likelihood of this attack. | Medium | -| T-SPLANE-03 | A Rogue PTP Instance wanting to be a Grand Master by sending manipulated/malicious ANNOUNCE messages declaring him to be the best clock in the network | Degradation in the accuracy of time may cause DoS to applications on all the RUs that rely on accurate time, potentially bringing down the cell. A cell outage caused by misaligned time, may further impact performance in connected neighboring cells. | A | High | Low | • Threat event initiation (Medium)
• Adverse impacts (Low) | Existing controls are in place to prevent, or at least significantly impede, the vulnerability from being exercised. It is a possible attack, however needs physical access and sophistication to execute | Access control on the CUSM-Plane that mitigates unauthorized access by an insider are in place. 802.1x protocol is supported it can reduce the likelihood of this attack. | Medium | -| T-SPLANE-04 | Selective interception and removal of PTP timing packets | Clock degradation in attacked nodes. Removing all packets or random packets may push the clocks in attacked nodes into free running mode. Degradation in the accuracy of time may cause DoS to applications on all the RUs that rely on accurate time, potentially bringing down the cell. A cell outage caused by misaligned time, may further impact performance in connected neighboring cells. | A | High | Low | • Threat event initiation (Medium)
• Adverse impacts (Low) | Existing controls are in place to prevent, or at least significantly impede, the vulnerability from being exercised. It is a possible attack, however needs physical access and sophistication to execute | Access control on the CUSM-Plane that mitigates unauthorized access by an insider are in place. 802.1x protocol is supported it can reduce the likelihood of this attack. | Medium | -| T-SPLANE-05 | Packet delay manipulation attack | Degradation in the accuracy of time may cause DoS to applications on all the RUs | A | High | Medium | • Threat event initiation | Existing controls are in place to prevent (moderately) | 802.1x protocol is | High | - -| | | | | | | | | | | -|-------------|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--------|-----|---------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| -| | | that rely on accurate time, potentially bringing down the cell. A cell outage caused by misaligned time, may further impact performance in connected neighboring cells. | | | | (Medium)
• Adverse impacts (Medium) | satisfactory). It is a possible attack, however needs physical access and sophistication to execute | supported it can reduce the likelihood of this attack. | | -| T-CPLANE-01 | Spoofing of DL C-plane messages | The lack of authentication could allow an adversary to inject own DL C-plane messages that falsely claiming to be from the associated O-DU. As a result, it would block the O-RU to process the corresponding U-Plane packets, leading to temporarily DoS. (dropping the entire DL C-plane messages would achieve same goal) | A | Medium | Low | • Threat event initiation (Medium)
• Adverse impacts (Low) | Existing controls are in place to prevent, or at least significantly impede, the vulnerability from being exercised. It is a possible attack, however needs physical access and sophistication to execute | 802.1x at the ethernet level ensures authentication and authorization for communication over FH interface, not sure that this control reduce the risk of spoofing of c-plane at a low level. Mitigations related to monitoring and configuration of network nodes are in place | Low | -| T-CPLANE-02 | Spoofing of UL C-plane messages | The lack of authentication could allow an adversary to inject own UL C-plane messages that falsely claiming to be from the associated O-DU. As a result, temporarily limited cell performance (or even DoS) on cells served by the O-RU and in addition a consequential threat to all O-RUs parented to that O-DU might exist. (dropping the entire UL C-plane messages would achieve same goal) | A | Medium | Low | • Threat event initiation (Medium)
• Adverse impacts (Low) | Existing controls are in place to prevent, or at least significantly impede, the vulnerability from being exercised. It is a possible attack, however needs physical access and sophistication to execute | 802.1x at the ethernet level ensures authentication and authorization for communication over FH interface, not sure that this control reduce the risk of spoofing of c-plane at a low level. Mitigations related to monitoring and configuration of network nodes are in place | Low | -| T- | An attacker attempts to | For the transported U-Plane data an | C | Medium | Low | • Threat event | Existing controls are in place | 802.1x | Low | - -| | | | | | | | | | | -|-------------|--------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|--------|--------|------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|--------| -| UPLANE-01 | intercept the Fronthaul (MITM) over U Plane to obtain user data (PDCP protocol is used) | attacker could potentially do threats, such as passive wiretapping, but would need to break PDCP Security prior to any content access. | | | | initiation (Low)
• Adverse impacts (Medium) | to prevent, or at least significantly impede, the vulnerability from being exercised. It is a possible attack, however, needs physical access and sophistication to execute | protocol is supported it can reduce the likelihood of this attack. | | -| T-UPLANE-02 | An attacker attempts to intercept the Fronthaul (MITM) over U Plane to modify u-plane data (PDCP protocol is used) | For the transported U-Plane data an attacker could potentially do threats, such as passive wiretapping, but would need to break PDCP Security prior to any content access. | I | Medium | Low | • Threat event initiation (Low)
• Adverse impacts (Medium) | Existing controls are in place to prevent, or at least significantly impede, the vulnerability from being exercised. It is a possible attack, however, needs physical access and sophistication to execute | 802.1x protocol is supported it can reduce the likelihood of this attack. | Low | -| T-UPLANE-03 | An attacker attempts to intercept the Fronthaul (MITM) over U Plane to disrupt services (PDCP protocol is used) | For the transported U-Plane data an attacker could potentially do threats, such as passive wiretapping, but would need to break PDCP Security prior to any content access. | A | Medium | Low | • Threat event initiation (Low)
• Adverse impacts (Medium) | Existing controls are in place to prevent, or at least significantly impede, the vulnerability from being exercised. It is a possible attack, however, needs physical access and sophistication to execute | 802.1x protocol is supported it can reduce the likelihood of this attack. | Low | -| T-UPLANE-04 | Spoofing and unauthorized access of U-Plane data packets | An attacker could degrade service quality, disrupt legitimate data flow, and potentially cause a DoS. | NA | Medium | Low | • Threat event initiation (Low)
• Adverse impacts (Medium) | Existing controls are in place to prevent, or at least significantly impede, the vulnerability from being exercised. It is a possible attack, however, needs physical access and sophistication to execute | 802.1x protocol is supported it can reduce the likelihood of this attack. | Low | -| T-ORU-01-a | An attacker stands up a rogue O-RU (standalone) - a false base station | This opens the door to subscriber's identity interception/disclosure and unauthorized user tracking attacks (privacy breach). | C, I | High | Medium | • Threat event initiation (Medium)
• Adverse impacts (Medium) | Existing controls are in place to prevent (moderately satisfactory). It is a possible attack, however needs physical access and sophistication to execute | Security measures already defined by 3GPP, monitoring/detection mechanisms of a rogue ORU are in place | High | -| T-ORU-01-b | An attacker stands up a rogue O-RU attacking O-DU and beyond (core network) | It provides a means to launch attacks on the availability, integrity, and confidentiality of the Open Front Haul system, ODUs and beyond in the core network. | C, I | High | Low | • Threat event initiation (Medium)
• Adverse impacts (Low) | Existing controls are in place to prevent, or at least significantly impede, the vulnerability from being exercised. It is a possible attack, however needs physical access and sophistication to execute | 802.1x protocol is supported it can reduce the likelihood of this attack. | Medium | -| T-O-RU-02 | Inability to uniquely identify local user accounts shared | Activities by multiple different controllers, for example, the SMO and/or O-RU controller, authenticating using the same shared | I | High | Medium | • Threat event initiation (Medium) | It is a possible attack, however, needs access and sophistication to execute. | Local user accounts are typically | High | - -| | | | | | | | | | | -|---------------|-------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|------|--------|-----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|------| -| | across entities (e.g., SMO, O-DU) for concurrent access | account cannot be distinguished, compromising non-repudiation. | | | | • Adverse impacts (Medium) | | identical | | -| T-O-RU-03 | Manipulation of Initial provisioning information from the Software configuration server could lead O-RU to access incorrect server. | O-RU having incorrect authentication and authorization server information can result in a DoS for the O-RU | I, A | High | Medium | • Threat event initiation (Medium)
• Adverse impacts (Medium) | It is a possible attack, however, needs access and sophistication to execute. | | High | -| T-O-RU-04 | An attacker compromises O-RU user information | Mismanagement of O-RU Credentials including account information, misclassification of O-RU users between centralized and local users | C, I | High | Medium | • Threat event initiation (Medium)
• Adverse impacts (Medium) | It is a possible attack, however, needs access and sophistication to execute. | | High | -| T-NEAR-RT-01 | Malicious xApps can exploit UE identification, track UE location and change UE priority | An xApp can receive order via A1 to control a certain UE and if a malfunctioning xApp receives an order to prioritize this UE, then the owner of the malfunctioning xApp knows a VIP that they want to track in a certain area. With this command exposure, the attacker can obtain a rough location of a very important person and change the order from prioritize to deprioritize for a UE; Interception of UE identifier | C, I | High | High | • Threat event initiation (High)
• Adverse impacts (High)
• Exposure (High) | O-RAN ALLIANCE has not specified yet any xApp security measures around the Onboarding onto SMO and deployment onto Near RT-RIC. Further, there is no testing framework in place for xApps yet. | | High | -| T-NEAR-RT-02 | Risk of a malicious xApp on Near-RT RIC to obtain protected information | Deployment of malicious xApps may allow unauthorized access to E2 Nodes, abuse of radio network information, or exploit UE identification and location. | C, I | High | High | • Threat event initiation (High)
• Exposure (High) | O-RAN ALLIANCE has not specified yet any xApp security measures around the Onboarding onto SMO and deployment onto Near RT-RIC. Further, there is no testing framework in place for xApps yet. | | High | -| T-NEAR-RT-02A | Risk of a malicious xApp on Near-RT RIC impacting service availability | Deployment of malicious xApps may allow impacting service or exploit slice priority. | A | High | High | • Threat event initiation (High)
• Adverse impacts (High) | O-RAN ALLIANCE has not specified yet any xApp security measures around the Onboarding onto SMO and deployment onto Near RT-RIC. Further, there is no testing framework in place for xApps yet. | | High | - -| | | | | | | | | | | -|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|------|--------|-------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|--|------| -| T-NEAR-RT-03 | Near-RT RIC APIs can be compromised and manipulated due to lack, incorrect or weak authentication mechanism | Near-RT RIC data around services and UEs can be eavesdropped. | C | High | High |
  • Threat event initiation (High)
  • Exposure (High)
| O-RAN ALLIANCE has not specified yet any Near-RT RIC APIs measures. | | High | -| T-NEAR-RT-03A | Near-RT RIC APIs can be compromised and manipulated due to lack, incorrect or weak authentication mechanism | Unauthenticated APIs can be manipulated causing services disruptions in RAN network | A | High | High |
  • Threat event initiation (High)
  • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any Near-RT RIC APIs measures. | | High | -| T-NEAR-RT-04 | Resources and services provided by Near-RT RIC platform and xApps via APIs can be abused and/or misused | Near-RT RIC data around services and UEs can be eavesdropped by xApps without proper permissions. | C | High | High |
  • Threat event initiation (High)
  • Adverse impacts (High)
  • Exposure (High)
| O-RAN ALLIANCE has not specified yet any Near-RT RIC APIs measures. | | High | -| T-NEAR-RT-04A | Resources and services provided by Near-RT RIC platform and xApps via APIs can be abused and/or misused | Abuse of resources and misuse of services can produce disruptions and/or outages in the network. | A | High | High |
  • Threat event initiation (High)
  • Adverse impacts (High)
  • Exposure (High)
| O-RAN ALLIANCE has not specified yet any Near-RT RIC APIs measures. | | High | -| T-NEAR-RT-05 | Risk of deployment of a malicious, non-uniquely identified xApps using a trusted xAppID to access resources and services which they are not entitled to use. | theft of services, data leakage | C, I | High | High |
  • Threat event initiation (High)
  • Exposure (High)
| O-RAN ALLIANCE has not specified yet any xApp security measures around the xAppID yet. | | High | -| T-NONRTRIC-01 | An attacker gains access to the Non-RT RIC through the SMO to cause a denial of service or degrade the | Non-RT RIC would not be able to:
  • monitor or trace the network to understand the effect of policy on performance in Near-RT RIC
  • update A1 policy
| A | High | Medium |
  • ZTA (Medium)
  • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any security measures around the authentication and access control to the Non RT-RIC. | | High | - -| | | | | | | | | | | -|---------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------| -| | performance of the Non-RT-RIC |
  • • provide exposure and secure delivery of A1 Enrichment Information to Near-RT RIC
  • • setup access control rules and the selection of which Enrichment Information ID (Eild) is exposed to a near-RT RIC
| | | | | | | | -| T-NONRTRIC-02 | An attacker gains access to the Non-RT RIC through the SMO for UE tracking | Attacker has access to sensitive data and is able to track a UE | C, A | High | High |
  • • ZTA (High)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any security measures around the authentication and access control to the Non RT-RIC. | | High | -| T-NONRTRIC-03 | An attacker gains access to the Non-RT RIC through the SMO to cause Data Corruption/Modification | A malicious actor who gains unauthorized access to the Non-RT-RIC can modify policy to pass a “False Policy” to the Near-RT-RIC to degrade performance or cause an outage. | I, A | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any security measures around the authentication and access control to the Non RT-RIC. | | High | -| T-NONRTRIC-04 | Attacker exploits non-uniquely identified rApp instances to access services and obtain information | Attacker exploits non-uniquely identified rApp instances to access certain services and obtain information | C | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any security measures around the authentication and access control to the Non RT-RIC. | | High | -| T-NONRTRIC-05 | Attacker exploits non-uniquely identified rApp instances, gain access to services resulting in a denial of service to correct rApp instance. | Attacker exploits non-uniquely identified rApp instances, gain access to services resulting in a denial of service to correct rApp instance. | A | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any security measures around the authentication and access control to the Non RT-RIC. | | High | -| T-xAPP-01 | An attacker exploits xApps vulnerabilities and misconfiguration to alter data transmitted over A1 or E2 interfaces. |

If attackers can find exploitable xApp, they can disrupt the offered network service and potentially take over another xApp or the whole Near-RT RIC.

The actual consequences may vary. For example, an attacker may gain the ability to alter data transmitted over A1 or E2 interfaces, extract sensitive information, etc.

| I | High | High |
  • • Threat event initiation (High)
  • • Adverse impacts (High)
  • • Exposure (High)
| O-RAN ALLIANCE has not specified yet any xApp security measures around the Onboarding onto SMO and deployment onto Near RT-RIC, authentication and access control, secure configuration, etc. Further, there is no testing framework in place for xApps yet. | | High | -| T-xAPP-01A | An attacker exploits xApps vulnerabilities and misconfiguration to extract sensitive information. |

If attackers can find exploitable xApp, they can disrupt the offered network service and potentially take over another xApp or the whole Near-RT RIC.

The actual consequences may vary. For example, an attacker may gain the ability to alter data transmitted over A1 or E2 interfaces, extract sensitive information, etc.

| C | High | High |
  • • Threat event initiation (High)
  • • Adverse impacts (High)
  • • Exposure (High)
| O-RAN ALLIANCE has not specified yet any xApp security measures around the Onboarding onto SMO and deployment onto Near RT-RIC, authentication and access control, secure configuration, etc. Further, there is no testing framework in place for xApps yet. | | High | -| T-xAPP-01B | An attacker exploits xApps vulnerabilities and misconfiguration | If attackers can find exploitable xApp, they can disrupt the offered network service and potentially take over another xApp or the | A | High | High |
  • • Threat event initiation (High)
  • • Adverse
| O-RAN ALLIANCE has not specified yet any xApp security measures around | | High | - -| | | | | | | | | | | -|------------|---------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|------|--------|-----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------| -| | to disrupt Near-RT RIC functions | whole Near-RT RIC.
The actual consequences may vary. For example, an attacker may gain the ability to alter data transmitted over A1 or E2 interfaces, extract sensitive information, etc. | | | | impacts (High)
• Exposure (High) | the Onboarding onto SMO and deployment onto Near RT-RIC, authentication and access control, secure configuration, etc. Further, there is no testing framework in place for xApps yet. | | | -| T-xAPP-01C | An attacker exploits xApps vulnerabilities and misconfiguration to gain unauthorized control over Near-RT RIC | If attackers can find exploitable xApp, they can disrupt the offered network service and potentially take over another xApp or the whole Near-RT RIC.
The actual consequences may vary. For example, an attacker may gain the ability to alter data transmitted over A1 or E2 interfaces, extract sensitive information, etc. | C, I, A | High | High | • Threat event initiation (High)
• Adverse impacts (High)
• Exposure (High) | O-RAN ALLIANCE has not specified yet any xApp security measures around the Onboarding onto SMO and deployment onto Near RT-RIC, authentication and access control, secure configuration, etc. Further, there is no testing framework in place for xApps yet. | | High | -| T-xAPP-02 | Conflicting xApps impact O-RAN system functions to degrade performance or trigger a DoS | An attacker can utilize a malicious xApp that intentionally triggers RRM decisions conflicting with the O-gNB internal decisions to create denial of service or performance degradation. | A | High | Medium | • Threat event initiation (Medium)
• Adverse impacts (High) | O-RAN ALLIANCE has not specified yet any xApp security measures around the Onboarding onto SMO and deployment onto Near RT-RIC, authentication and access control, secure configuration, etc. Further, there is no testing framework in place for xApps yet. | | High | -| T-xAPP-03 | An attacker compromises xApp isolation to tamper with the underlying system. | Gaining unauthorized access to the underlying system provides new opportunities to exploit vulnerabilities in other xApps or O-RAN architecture elements to tamper with the underlying system. | I | High | Medium | • Threat event initiation (Medium)
• Adverse impacts (High) | This threat exists if no xApp security measures around the Onboarding onto SMO and deployment onto Near RT-RIC, authentication and access control, secure configuration, etc, are defined. | | High | -| T-xAPP-03A | An attacker compromises xApp isolation to extract sensitive information from co-hosted xApps. | Gaining unauthorized access to the underlying system provides new opportunities to exploit vulnerabilities in other xApps or O-RAN architecture elements to extract sensitive information from co-hosted xApps. | C | High | Medium | • Threat event initiation (Medium)
• Adverse impacts (High) | This threat exists if no xApp security measures around the Onboarding onto SMO and deployment onto Near RT-RIC, authentication and access control, secure configuration, etc, are defined. | | High | -| T-xAPP-03B | An attacker compromises xApp isolation to degrade services. | Gaining unauthorized access to the underlying system provides new opportunities to exploit vulnerabilities in other xApps or O-RAN architecture | A | High | Medium | • Threat event initiation (Medium)
• Adverse | This threat exists if no xApp security measures around the Onboarding onto SMO and deployment onto Near | | High | - -| | | | | | | | | | | -|------------|------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|---------|------|--------|--------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------| -| | | elements. | | | | impacts (High) | RT-RIC, authentication and access control, secure configuration, etc, are defined. | | | -| T-xAPP-03C | An attacker compromises xApp isolation to gain elevated privileges. | Gaining unauthorized access to the underlying system provides new opportunities to gain elevated privileges. | C, I, A | High | Medium |
  • Threat event initiation (Medium)
  • Adverse impacts (High)
| This threat exists if no xApp security measures around the Onboarding onto SMO and deployment onto Near RT-RIC, authentication and access control, secure configuration, etc, are defined. | | High | -| T-xApp-04 | False or malicious A1 policies modify behaviour of xApps. | A false and malicious A1 policy can exploit xApp functionality. | I | High | Medium |
  • Threat event initiation (Medium)
  • Adverse impacts (High)
| This threat exists if no xApp security measures around the Onboarding onto SMO and deployment onto Near RT-RIC, authentication and access control, secure configuration, etc, are defined. This attack, to be performed, requires multiple steps to be achieved by an attacker. | | High | -| T-xApp-05 | False or malicious A1 policies from the Non-RT RIC modify behaviour of xApps to trigger a DoS. | A false and malicious A1 policy can exploit xApp functionality to trigger a DoS. | A | High | Medium |
  • Threat event initiation (Medium)
  • Adverse impacts (High)
| This threat exists if no xApp security measures around the Onboarding onto SMO and deployment onto Near RT-RIC, authentication and access control, secure configuration, etc, are defined. This attack, to be performed, requires multiple steps to be achieved by an attacker. | | High | -| T-xApp-06 | False or malicious A1 policies from the Non-RT RIC modify behaviour of xApps to locate a subscriber. | A false and malicious A1 policy can exploit xApp functionality to locate a subscriber. | C | High | Medium |
  • Threat event initiation (Medium)
  • Adverse impacts (High)
| This threat exists if no xApp security measures around the Onboarding onto SMO and deployment onto Near RT-RIC, authentication and access control, secure configuration, etc, are defined. This attack, to be performed, requires multiple steps to be achieved by an attacker. | | High | -| T-rAPP-01 | Conflicting rApps impact O-RAN system functions to degrade | rApps in the Non-RT RIC performing different functions can be provided by different vendors. This creates the risk that | C, I, A | High | Medium |
  • ZTA (Medium)
  • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any rApp security measures around | | High | - -| | | | | | | | | | | -|-----------|------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|------|--------|----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------| -| | performance or trigger a DoS | different rApps will take conflicting decisions to set conflicting policies. This can result in performance degradation or outage. | | | | | the Onboarding onto SMO and deployment onto Non RT-RIC, authentication and access control, secure configuration, etc. Further, there is no testing framework in place for rApps yet. | | | -| T-rAPP-02 | An attacker exploits rApp vulnerability for data breach or denial of service | Vulnerabilities can potentially exist in any rApp. If attackers can find exploitable rApp, they can disrupt the offered network service and potentially take over another rApp or the non-RT RIC. The consequences may vary. For example, an attacker may gain the ability to alter data transmitted over A1 interface, extract sensitive information, etc. | C, I, A | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any rApp security measures around the Onboarding onto SMO and deployment onto Non RT-RIC, authentication and access control, secure configuration, etc. Further, there is no testing framework in place for rApps yet. | | High | -| T-rAPP-03 | An attacker exploits rApps misconfiguration | Security misconfiguration, such as open ports or enabled unused protocols, can potentially exist in an rApp. If attackers can find exploitable rApp, they can disrupt the offered network service and potentially take over another rApp or the whole non-RT RIC. The actual consequences may vary. For example, an attacker may gain the ability to alter data transmitted over A1 interface, extract sensitive information, etc. | C, I, A | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any rApp security measures around the Onboarding onto SMO and deployment onto Non RT-RIC, authentication and access control, secure configuration, etc. Further, there is no testing framework in place for rApps yet. | | High | -| T-rAPP-04 | An attacker bypasses authentication and authorization | An Attacker can exploit an rApp that has weak or misconfigured authentication and authorization to gain access to the rApp and pose as a tenant. | C, I, A | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any rApp security measures around the Onboarding onto SMO and deployment onto Non RT-RIC, authentication and access control, secure configuration, etc. Further, there is no testing framework in place for rApps yet. | | High | -| T-rAPP-05 | An attacker deploys and exploits malicious rApp | An untrusted source may intentionally provide a malicious rApp. A trusted source may have a backdoor intentionally inserted in the rApp. If attackers can find exploitable rApp, they can disrupt the offered network service and potentially take over another rApp or the whole Non-RT RIC. Malicious rApps could impact Non-RT RIC functions such as AI/ML model training, A1 policy management, Enrichment information management, Network Configuration Optimization in the purpose of performance | C, I, A | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any rApp security measures around the Onboarding onto SMO and deployment onto Non RT-RIC, authentication and access control, secure configuration, etc. Further, there is no testing framework in place for rApps yet. | | High | - -| | | | | | | | | | | -|-----------|---------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|------|--------|--------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------| -| | | degradation, DoS, | | | | | | | | -| T-rAPP-06 | An attacker bypasses authentication and authorization using an injection attack | It is possible that an attacker to submit requests without prior authentication and authorization by executing an injection attack to manipulate configurations, access logs, perform remote code execution, etc. | C, I, A | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any rApp security measures around the Onboarding onto SMO and deployment onto Non RT-RIC, authentication and access control, secure configuration, etc. Further, there is no testing framework in place for rApps yet. | | High | -| T-rAPP-07 | rApp exploits services | A malicious rApp or a trusted but compromised rApp can exploit services such as O1 services across the R1 interface | A | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any rApp security measures around the Onboarding onto SMO and deployment onto Non RT-RIC, authentication and access control, secure configuration, etc. Further, there is no testing framework in place for rApps yet. | | High | -| T-PNF-01 | An attacker compromises a PNF to launch attacks against VNFs/CNFs | Data tampering and information disclosure; Unauthenticated/unauthorized access of the O_RAN component leads to compromised performance and/or function/service, lateral attack towards other O-RAN system component(s) from inside, and loss/stolen/tampering of sensitive data; | C, I | High | Medium |
  • • Threat event initiation (Medium)
  • • Adverse impacts (Medium)
| This is a likely attack but may need physical access to the PNF. | | High | - -| | | | | | | | | | | -|-----------|--------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|---------|--------|--------|----------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|--|--------| -| T-PNF-01A | An attacker compromises a PNF to launch Denial of Service attacks against VNFs/CNFs | Denial of service from within for component access and/or function/service offered | A | High | Medium |
  • Threat event initiation (Medium)
  • Adverse impacts (Medium)
| This is a likely attack but may need physical access to the PNF. | | High | -| T-SMO-01 | An attacker can exploit the misconfigured/poorly implemented authentication mechanism on SMO functions | The data stored in the SMO may be exposed/manipulated to an attacker. | C, I | High | High |
  • ZTA (High)
  • Threat event initiation (High)
| | | High | -| T-SMO-02 | An attacker can exploit the misconfigured/poorly implemented authorization on SMO functions | An attacker can be able to perform certain actions, e.g. disclose O-RAN sensitive information or alter O-RAN components. | C, I, A | High | High |
  • ZTA (High)
  • Threat event initiation (High)
| | | High | -| T-SMO-03 | Overload DoS attacks at SMO | Inability to deal with such events affects availability of SMO data and functions. | A | Medium | Medium |
  • ZTA (Medium)
  • Threat event initiation (High)
| | | Medium | -| T-SMO-04 | Internal attacker exploits authentication weakness | Internal attacker exploits authentication weakness on a SMO function | I | High | Medium | | | | Medium | -| T-SMO-05 | Internal attacker exploits authorization weakness | Internal attacker exploits authorization weakness on SMO | I | High | Medium | | | | Medium | -| T-SMO-06 | Internal Overload DoS attack | Internal Overload DoS attack targeted at SMO functions | A | High | Medium | | | | Medium | -| T-SMO-07 | Internal DoS attack disables function | Internal DoS attack disables internal SMO function(s) or process(es) | A | High | Medium | | | | Medium | -| T-SMO-08 | Insecure API to gain access | Attacker exploits insecure API to gain access to SMO | I | High | Medium | | | | Medium | -| T-SMO-09 | Expose internal data in transit | Sensitive data in transit is exposed to an internal attacker | C, I | High | Medium | | | | Medium | -| T-SMO-10 | Expose data at rest | Sensitive data at rest is exposed to an internal attacker | C, I | High | Medium | | | | Medium | -| T-SMO-11 | AI/ML poisoning | AI/ML poisoning by internal attacker | I | High | Medium | | | | Medium | -| T-SMO-12 | AI/ML exposure | AI/ML exposure on external entity | C | High | Medium | | | | Medium | -| T-SMO-13 | Logs exposed | Malicious actor views local logs | C | High | High | | | | High | -| T-SMO-14 | Log entries modified | Malicious actor modifies local log entries | I | High | Medium | | | | Medium | -| T-SMO-15 | Log entries deleted | Malicious actor deletes local logs | I | High | Medium | | | | Medium | - -| | | | | | | | | | | -|----------|-----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|------|------|--------|--|--|--|--------| -| T-SMO-16 | Log transfer intercepted | Malicious actor intercepts exports of local logs | C | High | High | | | | High | -| T-SMO-17 | Unauthorized internal access to logs | Malicious external actor gains unauthorized access to logs | I | High | High | | | | High | -| T-SMO-18 | Unauthorized external access to logs | Malicious internal actor gains authorized access to logs | I | High | High | | | | High | -| T-SMO-19 | O2 exposes data in transit | Internal attacker exploits O2 interface to view data in transit between SMO and O-Cloud | C | High | High | | | | High | -| T-SMO-20 | Data in transit modified on O2 | Internal attacker exploits O2 interface to modify data in transit between SMO and O-Cloud | C | High | Medium | | | | Medium | -| T-SMO-21 | Unauthorized O-Cloud access via O2 | Internal attacker uses O2 interface via SMO to exploit API vulnerability to gain access to O-Cloud infrastructure | I | High | High | | | | High | -| T-SMO-22 | O-Cloud flooded across O2 | Internal attacker floods O2 interface via SMO to cause DDoS on O-Cloud infrastructure | I | High | Medium | | | | Medium | -| T-SMO-23 | Unauthorized SMO access via O2 | External attacker uses O2 interface via O-Cloud to exploit API vulnerability to gain access to SMO | I | High | Medium | | | | Medium | -| T-SMO-24 | SMO flooded across O2 | External attacker floods O2 interface via O-Cloud to cause DDoS on SMO | A | High | Medium | | | | Medium | -| T-SMO-25 | Unauthorized access to SMO data via O2 | External attacker uses O2 interface via O-Cloud to gain authorized access to sensitive data-at-rest at the SMO | A | High | Medium | | | | Medium | -| T-SMO-26 | View data in transit on External interface | External attacker exploits External interface to view data in transit between SMO and external service | C | High | High | | | | High | -| T-SMO-27 | Modify data in transit on External Interface | External attacker exploits External interface to modify data in transit between SMO and external service | I | High | Medium | | | | Medium | -| T-SMO-28 | API vulnerability exploited for unauthorized SMO access | External attacker uses External interface to exploit API vulnerability to gain access to SMO | I | High | Medium | | | | Medium | -| T-SMO-29 | SMO DoS flooded across External interface | External attacker floods External interface to cause DDoS at SMO | A | High | Medium | | | | Medium | -| T-SMO-30 | External attacker uses External interface to access SMO | External attacker uses External interface to gain access to sensitive data-at-rest at the SMO | C, I | High | Medium | | | | Medium | -| T-SMO-31 | External attacker poisons External AI/ML data | External attacker poisons External AI/ML data to corrupt SMO | I | High | High | | | | High | -| T-SMO-32 | External attacker poisons External Enrichment Information | External attacker poisons External Enrichment Information data sources to corrupt SMO | I | High | High | | | | High | -| T-SMO-33 | rApp floods SME | Misbehaving 3rd-party rApp, maliciously or non-maliciously, floods internal SMOS Communication | A | High | Medium | | | | Medium | - -| | | | | | | | | | | -|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|------|--------|---------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--------| -| T-SMO-34 | External Consumer floods SME | External Source, maliciously or non-maliciously, floods the External interface | A | High | Medium | | | | Medium | -| T-OPENSRC-01 | Developers use SW components with known vulnerabilities and untrusted libraries that can be exploited by an attacker through a backdoor attack | Attackers can exploit a vulnerability on the open-source code and infects a hypervisor, operating system, VM or container with a malware. | C, I, A | High | High | Open-source/COTS support (High) | Vulnerability handling and patch management are not yet defined by O-RAN ALLIANCE. Several CVE have already been discovered on open-source software. | | High | -| T-OPENSRC-02 | A trusted developer intentionally inserts a backdoor into an open-source code O-RAN component. | Unauthenticated/unauthorized access of the O-RAN component leads to compromised performance and/or function/service, lateral attack towards other O-RAN system component(s) from inside, and loss/stolen/tampering of sensitive data; | C, I, A | High | Medium | Open-source/COTS support (High) | Vulnerability handling and patch management are not yet defined by O-RAN ALLIANCE. Several CVE have already been discovered on open-source software. | | High | -| T-PHYS-01 | An intruder gaining physical access to O-RAN components to cause damage by manipulation / modification to software / software configuration /management | Data tampering; Unauthenticated/unauthorized access of the O-RAN component leads to lateral attack towards other O-RAN system component(s) from inside, and tampering of sensitive data; | I | High | Medium | Exposure (Medium) | O-RAN system has many external interfaces. Different O-Cloud deployment models can be used to implement O-RAN. Several scenarios to implement O-RUs and O-DUs are supported by O-RAN. | | High | -| T-PHYS-01A | An intruder gains physical access to O-RAN components to access sensitive data | Information disclosure; Unauthenticated/unauthorized access of the O-RAN component leads to lateral attack towards other O-RAN system component(s) from inside, and effect loss of/steal sensitive data; | C | High | Medium | Exposure (Medium) | O-RAN system has many external interfaces. Different O-Cloud deployment models can be used to implement O-RAN. Several scenarios to implement O-RUs and O-DUs are supported by O-RAN. | | High | -| T-PHYS-01B | An intruder gains physical access to O-RAN components to cause performance degradations, denial of service | Denial of service from within for component access and/or function/service offered; Unauthenticated/unauthorized access of the O-RAN component leads to compromised performance and/or function/service | A | High | Medium | Exposure (Medium) | O-RAN system has many external interfaces. Different O-Cloud deployment models can be used to implement O-RAN. Several scenarios to implement O-RUs and O-DUs are supported by O-RAN. | | High | - -| | | | | | | | | | | -|-------------|--------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|--------|--------|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------| -| T-PHYS-02 | An intruder into the Fronthaul cable network attempts to gain electronic access to cause damage or access sensitive data | Information disclosure;
Unauthenticated/unauthorized access of sensitive data; | C | High | Medium | Exposure (Medium) | O-RAN system has many external interfaces. Different O-Cloud deployment models can be used to implement O-RAN. Several scenarios to implement O-RUs and O-DUs are supported by O-RAN. | | High | -| T-RADIO-01 | Disruption through radio Jamming | Service disruption | A | High | High | Exposure (High) | These attacks are common and not specific to O-RAN. They are likely to occur, hence they need more investigation and consideration. Mitigations to reduce these types of attacks should be defined by O-RAN ALLIANCE. | | High | -| T-RADIO-01A | Disruption through radio Sniffing and Spoofing | Information exposure, Authenticity challenges | C, I | High | High | Exposure (High) | These attacks are common and not specific to O-RAN. They are likely to occur; hence they need more investigation and consideration. Mitigations to reduce these types of attacks should be defined by O-RAN ALLIANCE. | | High | -| T-RADIO-02 | DoS attacks on cognitive radio networks | Service disruption | A | Medium | High | Exposure (High) | These attacks are common and not specific to O-RAN. They are likely to occur, hence they need more investigation and consideration. Mitigations to reduce these types of attacks should be defined by O-RAN ALLIANCE. | | High | -| T-R1-01 | A malicious actor gains unauthorized access to R1 services | “Service management and exposure services Producer” determines whether the Service Producer is authorized to produce the service. An attacker can perform a spoofing attack to gain unauthorized access to R1 services. | C, I, A | High | Medium | • ZTA (Medium)
• Adverse impacts (High) | O-RAN ALLIANCE has not specified yet any R1 security measures. | | High | -| T-R1-02 | Attacker modifies Service Heartbeat | Attacker can exploit the Service Heartbeat on the R1 by modifying or inserting | C, I, A | High | Medium | • ZTA (Medium)
• Adverse | O-RAN ALLIANCE has not specified yet any R1 security | | High | - -| | | | | | | | | | | -|---------|-----------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|------|--------|----------------------------------------------------------------------------------------------------|----------------------------------------------------------------|--|------| -| | message to cause Denial of Service | heartbeat messages to cause denial of service | | | | impacts (High) | measures. | | | -| T-R1-03 | Malicious actor bypasses authentication to Request Data | Attacker can exploit password-based authentication on the R1 to request unauthorized data. Weak password management can easily be exploited. (Certificate-based mutual authentication using TLS and PKI X.509 certificates is recommended). | C, I, A | High | High |
  • • ZTA (High)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any R1 security measures. | | High | -| T-R1-04 | Malicious actor bypasses authorization to Discover Data | "Data registration and discovery service producer" determines whether the Data Producer is authorized to produce the data types. An attacker can perform a spoofing attack to discover available data. | C, I, A | High | High |
  • • ZTA (High)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any R1 security measures. | | High | -| T-R1-05 | A malicious actor gains unauthorized access to data | An attacker can perform a spoofing attack to exploit the Data request and subscription service for the purpose to gain unauthorized access to data. | C, I, A | High | High |
  • • ZTA (High)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any R1 security measures. | | High | -| T-R1-06 | Malicious actor modifies a Data Request | Data Consumers consume the "Data request and subscription service" to request data instances or subscribe to them. An attacker can modify a request to force the consumer to receive a different data set then that intended. Without checks, the received data could be processed, leading to erroneous decisions or triggers. | C, I, A | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any R1 security measures. | | High | -| T-R1-07 | Malicious actor snoops Data Delivery to the Data Consumer | Data delivery messages relate to a particular data request or subscription. The data can be delivered to the Data Consumer in different ways, including:
  • • as part of the payload of a data delivery message,
  • • as a data stream,
  • • from e.g., a REST endpoint, a message bus or object store location.
An attacker can perform snooping, injection, or modification attacks in the Delivery of Data process. | A | High | High |
  • • ZTA (High)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any R1 security measures. | | High | -| T-A1-01 | Untrusted peering between Non-RT-RIC | Malicious Non-RT-RIC peers with a Near-RT-RIC over the A1 interface, or a | C, I, A | High | Medium |
  • • ZTA (Medium)
  • • Adverse
| O-RAN ALLIANCE has not specified yet any A1 security | | High | - -| | | | | | | | | | | -|---------|--------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|------|--------|----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------| -| | and Near-RT-RIC | malicious Near-RT-RIC peers with a Non-RT-RIC over the A1 interface, due to weak mutual authentication. | | | | impacts (High) | measures. | | | -| T-A1-02 | Malicious function or application monitors messaging across A1 interface | Attacker gains access to A1 messaging for reconnaissance | C, I, A | High | High |
  • • ZTA (High)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any A1 security measures. | | High | -| T-A1-03 | Malicious function or application modifies messaging across A1 interface | Internal threat actor can gain access to the messaging across the A1 interface for a MITM attack to modify or inject policy. This can result in the Near-RT RIC receiving malicious policy. | C, I, A | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
| O-RAN ALLIANCE has not specified yet any A1 security measures. | | High | -| T-A1-04 | Unauthorized access to Non-RT-RIC- or Near-RT-RIC-resources | A malicious actor can gain access to Near-RT-RIC resources or Non-RT-RIC resources over the A1 interface. | C, I, A | High | High |
  • • ZTA (High)
  • • Threat event initiation (High)
|

ZTA: ease of performing reconnaissance attacks without immediate detection

Threat event initiation: simple to execute for sophisticated inside actors

| | High | -| T-E2-01 | Untrusted Near-RT RIC and/or E2 Nodes | A malicious actor can spoof as - E2 Node / Near-RT RIC and communicate to other O-RAN architecture element (Near-RT RIC / E2 node) | I | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
|

Impact – High: a malicious actor spoofing an E2 Node or Near-RT RIC could inject false policies, disrupt network performance, or degrade service quality.

Likelihood – medium: authentication mechanisms prevent unauthorized access, but misconfigurations or credential leaks could allow exploitation.

| | High | -| T-E2-02 | Malicious actor monitors messaging across E2 interface | A threat actor can gain access to messages across E2 interface and can access E2 messages | C | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
|

Impact – High: intercepted E2 messages could expose sensitive operational data, leading to competitive intelligence gathering, network mapping, or further targeted attacks.

Likelihood – medium: encryption protects data in transit, but weak encryption policies or misconfigurations could make interception feasible.

| | High | -| T-E2-03 | Malicious actor modifies messaging across E2 interface | A threat actor can gain access to messages across E2 interface and can modify E2 messages | I | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
| Impact – High: modifying E2 messages could result in faulty network configurations, or loss of service. | | High | - -| | | | | | | | | | | -|------------|-----------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|------|--------|--------|-----------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|------| -| | | | | | | | Likelihood – medium: integrity protections are in place, but weaknesses in implementation or insider threats may still allow exploitation. | | | -| T-Y1-01 | Untrusted Near-RT-RIC and Y1 consumers | A malicious actor can spoof as a valid Y1 Consumer /Near-RT RIC and communicate to other O-RAN architecture element (Near-RT RIC / Y1 Consumer) | I | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
|

Impact – High: modifying E2 messages could result in faulty network configurations, or loss of service.

Likelihood – medium: integrity protections are in place, but weaknesses in implementation or insider threats may still allow exploitation.

| | High | -| T-Y1-02 | Malicious actor monitors messaging across Y1 interface | A threat actor can gain access to messages across Y1 interface and can access Y1 messages | C | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
|

Impact – High: unauthorized access to Y1 messages could reveal sensitive data, potentially leading to security breaches.

Likelihood – medium: encryption prevents such attacks, but misconfigurations or use of outdated security protocols could allow interception.

| | High | -| T-Y1-03 | Malicious actor modifies messaging across Y1 interface | A threat actor can gain access to messages across Y1 interface and can modify Y1 messages | I | High | Medium |
  • • ZTA (Medium)
  • • Adverse impacts (High)
|

Impact – High: altering Y1 messages could disrupt AI/ML-based optimizations, causing inefficiencies, degraded network performance, or security risks.

Likelihood – medium: cryptographic protections ensure integrity, but vulnerabilities in key management or implementation flaws could be exploited.

| | High | -| T-GEN-01-a | A successful attack could:
- Compromise the deployed VNF/CNF | Spoofing, Tampering, Information disclosure, Elevation of Privilege | C, I | Medium | High |
  • • Adverse impacts (Medium),
  • • ZTA (High)
| Adverse impacts (Medium) - Only one VNF/CNF might be affected, Existing requirements and controls are defined in the O-RAN specifications that may |

SBOM requirements

REQ-SEC-SYS-1

| High | - -| | | | | | | | | | | -|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------|------|--------|------|-------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|------| -| | | | | | | | impede successful exercise of the vulnerability.
ZTA (High): Reconnaissance and availability type attacks | | | -| T-GEN-01-b | A successful attack could:
- Deployment of malicious VM/Container (Lack of isolation)
- Exploit host access to escape the host and reach hardware server then the malicious VM/Container can gain root access to the whole server where it resides | Spoofing, Tampering, Information disclosure, Elevation of Privilege | C, I | High | High |
  • Adverse impacts (High),
  • ZTA (High)
| Adverse impacts (High) - Multiple VNFs/CNFs might be affected

ZTA (High): Reconnaissance and availability type attacks | SBOM requirements

REQ-SEC-SYS-1 | High | -| T-GEN-02 | A successful attack could:
- Bypass access controls placed on various resources on O-Cloud
- Gain increased privilege to specific O-Cloud services
- Access to restricted areas of the O-Cloud network | Spoofing, Tampering, Information disclosure, Elevation of Privilege | C, I | Medium | High |
  • Adverse impacts (Medium),
  • ZTA (High)
| Adverse impacts (Medium) - Requirements are in place for user authentication and authorization

ZTA (High): Reconnaissance type attacks | REQ-SEC-PASS-1

REQ-SEC-OCLOUD-1

REQ-SEC-OCLOUD-2 | High | -| T-GEN-03-a | A successful attack could:
- Make use of a untrusted VM/Container that runs on top of a trusted Hypervisor/Container Engine | Tampering, Information disclosure | C, I | Medium | High |
  • Adverse impacts (Medium),
  • ZTA (High)
| Adverse impacts (Medium) - Only one VNF/CNF might be affected

ZTA (High): Reconnaissance type attacks | | High | -| T-GEN-03-b | A successful attack could:
- Make use of a trusted VM/Container that runs on top of an untrusted Hypervisor/Container Engine to intercept communication, replace strong or use weak cryptographic keys, etc. | Tampering, Information disclosure | C, I | High | High |
  • Adverse impacts (High),
  • ZTA (High)
| Adverse impacts (High) - Multiple VNFs/CNFs might be affected

ZTA (High): Reconnaissance and availability type attacks | | High | -| T-GEN-03-C | A successful attack could:
- Make use of a trusted | Tampering, Information disclosure | C, I | High | High |
  • Adverse impacts (High),
  • ZTA (High)
| Adverse impacts (High) - Multiple VNFs/CNFs might be affected | | High | - -| | | | | | | | | | | -|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|---------|--------|--------|-----------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|--------| -| | VM/Container that runs on top of a trusted Hypervisor/Container Engine that runs on top of an untrusted hardware to intercept communication, replace strong or use weak cryptographic keys, etc. | | | | | | ZTA (High): Reconnaissance and availability type attacks | | | -| T-GEN-04 | A successful attack could:
- Compromise the availability of O-Cloud services
- Compromise the confidentiality/integrity of O-Cloud services by extracting/modifying critical application data | Information disclosure, Denial of Service | C, A | High | High |
  • Adverse impacts (High),
  • ZTA (High)
|

Adverse impacts (High) – No existing controls for interfaces in O-Cloud

ZTA (High): Reconnaissance and availability type attacks

| | High | -| T-GEN-05 (a) | A successful attack could:
- view insecurely stored credentials and cryptographic materials | Information disclosure, Elevation of Privilege | C | Medium | High | Adverse impacts (Medium), ZTA (High) |

Adverse impacts (Medium) – Requirements are defined for sensitive data protection in the O-RAN security specifications

ZTA (High): Reconnaissance type attacks

| REQ-SEC-OCLOUD-SS-1
REQ-SEC-OCLOUD-SS-2
REQ-SEC-OCLOUD-SS-3
SEC-CTL-OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-2
SEC-CTL-OCLOUD-SS-3 | High | -| T-GEN-05 (b) | A successful attack could:
- modify insecurely stored credentials and cryptographic materials | Tampering, Elevation of Privilege | I | Medium | Medium | Adverse impacts (Medium), ZTA (Medium) |

Adverse impacts (Medium) – Requirements are defined for sensitive data protection in the O-RAN security specifications

ZTA (Medium): Integrity type attacks

| REQ-SEC-OCLOUD-SS-1
REQ-SEC-OCLOUD-SS-2
REQ-SEC-OCLOUD-SS-3
SEC-CTL-OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-2
SEC-CTL-OCLOUD-SS-3 | Medium | -| T-GEN-06 | A successful attack could:
- Gain access to the sensitive information
- Escalate privileges in Applications | Information disclosure, Elevation of Privilege | C | Medium | Medium | Adverse impacts (Medium), ZTA (High) |

Adverse impacts (Medium) – Requirements are defined for sensitive data protection in the O-RAN security specifications

ZTA (High): Reconnaissance type attacks

| | Medium | -| T-VM-C-01 | A successful attack could:
- Compromise VM/Container isolation | Spoofing, Tampering, Information disclosure, Denial of Service and Elevation of privilege | C, I, A | High | High |
  • Adverse impacts (High),
  • ZTA (High)
|

Adverse impacts (High) – No existing requirements

ZTA (High): Reconnaissance

| | High | - -| | | | | | | | | | | -|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|---------|------|--------|---------------------------------------------|---------------------------------------------------------------------------------------------------|--|------| -| | measures
- Gain higher privileges on host or any of the containers running on that host
- Perform unauthorized modifications to the contents of host filesystem e.g. install SSH keys, read secrets mounted to the host, and take other malicious actions | | | | | | and availability type attacks | | | -| T-VM-C-02 | A successful attack could:
- Deploy a new malicious VM/Container configured without network rules, user limitations, etc. to bypass existing defenses within O-Cloud infrastructure
- Compromise the confidentiality & integrity of co-hosted VMs/Containers and tenants
- Launch DDOS attacks on co-hosted VMs/Containers and host services thereby degrading their performance | Spoofing, Tampering, Information disclosure, Denial of Service and Elevation of privilege | C, I, A | High | Medium | • Adverse impacts (High),
• ZTA (Medium) | Adverse impacts (High) – No existing requirements

ZTA (Medium) - Availability type attacks | | High | -| T-VM-C-03 | A successful attack could:
- Retrieve/manipulate VNF/CNF sensitive data (e.g. passwords, private keys, subscription data, logs) | Tampering, Information disclosure | C, I | High | High | • Adverse impacts (High),
• ZTA (High) | Adverse impacts (High) – No existing requirements

ZTA (High): Reconnaissance type attacks | | High | -| T-VM-C-04-a | A successful attack could:
- Cause migration Flooding:
VM/Container performance degradation and VM/Container crashes | Tampering, Information disclosure, Denial of Service | C, I, A | High | Medium | • Adverse impacts (High),
• ZTA (Medium) | Adverse impacts (High) – No existing requirements

ZTA (Medium): Availability type attacks | | High | -| T-VM-C-04-b | "A successful attack could: | Tampering, Information disclosure, Denial of Service | C, I, A | High | High | • Adverse impacts (High), | Adverse impacts (High) – No existing requirements | | High | - -| | | | | | | | | | | -|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|------|--------|--------|-----------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|------| -| |
  • - Sniff the packets that are exchanged between the source and destination servers
  • - Read the migrated memory pages
  • - Monitor and/or modify the received packets while continuing to forward them to victim VM/Container"
| | | | |
  • • ZTA (High)
| ZTA (High): Reconnaissance type attacks | | | -| T-VM-C-05 | A successful attack could:
  • - Misguide the Virtualization layer to reduce the resource of or delete a VM/Container on which a VNF/CNF is running. This can result in the reliability, availability or even illegal termination of a VNF/CNF and hence the denial of service
  • - Misguide the O-Cloud platform to detach a hardware accelerator from a VNF/CNF
| Denial of Service | A | High | Medium |
  • • Adverse impacts (High),
  • • ZTA (Medium)
| Adverse impacts (High) – No existing requirements

ZTA (Medium): Availability type attacks | | High | -| T-VM-C-06 | A successful attack could:
  • - Access to data not erased from a terminated VNF/CNF or any VNF/CNF that has released resources
| Information disclosure | C | High | High |
  • • Adverse impacts (High),
  • • ZTA (High)
| Adverse impacts (High) – No existing requirements

ZTA (High): Reconnaissance and availability type attacks | | High | -| T-IMG-01 | A successful attack could:
  • - Insert malicious code that will subsequently get run in the production environment
| Tampering, Information disclosure | C, I | Medium | High |
  • • Adverse impacts (Medium),
  • • ZTA (High)
| Adverse impacts (Medium) – Requirements are defined for image protection in the O-RAN security specifications

ZTA (High): Reconnaissance and availability type attacks | REQ-SEC-ALM-PKG-1 to REQ-SEC-ALM-PKG-15

SEC-CTL-ALM-PKG-1 to SEC-CTL-ALM-PKG-4 | High | -| T-IMG-02 | A successful attack could:
  • - Intercept network traffic intended for registries and steal developer or administrator
| Tampering, Information disclosure | C, I | Medium | High |
  • • Adverse impacts (Medium),
  • • ZTA (High)
| Adverse impacts (Medium) – Requirements are defined for image protection in the O-RAN security specifications

ZTA (High): Reconnaissance | REQ-SEC-ALM-PKG-1 to REQ-SEC-ALM-PKG-15

SEC-CTL-ALM-PKG-1 to | High | - -| | | | | | | | | | | -|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|---------|--------|--------|-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|--------| -| | credentials within that traffic. Thus, could be used to provide fraudulent or outdated images to orchestrators, etc. | | | | | | and availability type attacks | SEC-CTL-ALM-PKG-4 | | -| T-IMG-03 | A successful attack could:
- Secrets embedded within a VM/Container image can be stolen
- Secrets embedded within a VM/Container image can be modified | Spoofing, Tampering, Information disclosure | C, I | Medium | High |
  • Adverse impacts (Medium),
  • ZTA (High)
| Adverse impacts (Medium) – Requirements are defined for image protection in the O-RAN security specifications

ZTA (High): Reconnaissance and availability type attacks | REQ-SEC-ALM-PKG-1 to REQ-SEC-ALM-PKG-15

SEC-CTL-ALM-PKG-1 to SEC-CTL-ALM-PKG-4 | High | -| T-IMG-04 | A successful attack could:
- Build a custom image on the host that includes malware and then may deploy container using that custom image | Spoofing, Tampering, Information disclosure, Denial of Service and Elevation of privilege | C, I, A | Medium | High |
  • Adverse impacts (Medium),
  • ZTA (High)
| Adverse impacts (Medium) – Requirements are defined for image protection in the O-RAN security specifications

ZTA (High): Reconnaissance and availability type attacks | REQ-SEC-ALM-PKG-1 to REQ-SEC-ALM-PKG-15

SEC-CTL-ALM-PKG-1 to SEC-CTL-ALM-PKG-4 | High | -| T-VL-01 | A successful attack could:
- Gain control over the host of a server or install a malicious Hypervisor/Container Engine/Host OS and exploit that to run malicious applications on the VM/Container that run on top of the host. This would enable the attacker to control all the VMs/Containers running on the host. | Spoofing, Tampering, Information disclosure, Denial of Service and Elevation of privilege | C, I, A | High | High |
  • Adverse impacts (High),
  • ZTA (High)
| Adverse impacts (High) - No existing requirements

ZTA(High) - Reconnaissance and availability type of attacks | | High | -| T-VL-02 | A successful attack could cause:
- Failure of the physical machine to start at all
- Physical machine entering a safe-mode
- Physical machine continuing boot regardless of the integrity measurements | Tampering | I | High | Medium |
  • Adverse impacts (High),
  • ZTA (Medium)
| Adverse Impact (High) - No existing requirements

ZTA(Medium) - Availability type attacks | | High | -| T-VL-03 | A successful attack could:
- cause denial-of-service against the service | Denial of Service | A | Medium | Medium | Adverse impacts (Medium), ZTA (Medium) | Adverse impacts (Medium) – Requirements are defined for O-Cloud authentication and | REQ-SEC-OCLOUD-O2dms-1 | Medium | - -| | | | | | | | | | | -|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|---------|-----|------|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| -| | discovery infrastructure to prevent O-Cloud to react to changing resource requirements properly | | | | | | authorization in the O-RAN security specifications.

ZTA (Medium): Availability type attacks | REQ-SEC-OCLOUD-O2dms-2
REQ-SEC-OCLOUD-O2dms-3
REQ-SEC-OCLOUD-O2dms-4
REQ-SEC-OCLOUD-O2ims-1
REQ-SEC-OCLOUD-O2ims-2
REQ-SEC-OCLOUD-O2ims-3
REQ-SEC-OCLOUD-O2ims-4
REQ-SEC-OCLOUD-NotifAPI-1
REQ-SEC-OCLOUD-NotifAPI-2
SEC-CTL-OCLOUD-INTERFACE-1
SEC-CTL-OCLOUD-INTERFACE-2
SEC-CTL-OCLOUD-INTERFACE-3
REQ-SEC-OCLOUD-ISO-1
REQ-SEC-OCLOUD-ISO-2
REQ-SEC-OCLOUD-ISO-3
REQ-SEC-OCLOUD-ISO-4 | | -| T-O2-01 | A successful attack could:
- Tamper/alter/disclose requests and services sent over O2 between O-Cloud and SMO, hence the virtualized resource or relevant status information is not as requested
- Affect the normal operation of the O-Cloud, and even causes DoS attacks, information leakage. | Tampering, Information disclosure, Denial of Service | C, I, A | Low | High | • Adverse impacts (Low),
• ZTA (High) | Adverse impacts (Low) – Requirements are defined for the protection of O2 interface in the O-RAN security specifications

ZTA (High): Reconnaissance and availability type attacks | REQ-SEC-O2-1

SEC-CTL-O2-2

REQ-SEC-DOS-1 | Medium | - -| | | | | | | | | | | -|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|---------|------|--------|-----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|--------| -| T-OCAPI-01 | A successful attack could:
- Cryptographic keys or other security critical data of an instantiated VNF/CNF could be stolen by an attacker with access to the virtualization layer
- The virtualized resource provided by the Virtualization layer to the instantiated VNF/CNF can be manipulated | Tampering, Information disclosure, Denial of Service | C, I, A | Low | High |
  • Adverse impacts (Low),
  • ZTA (High)
| Adverse impacts (Low) – Requirements are defined for the protection of O-Cloud API in the O-RAN security specifications

ZTA (High): Reconnaissance and availability type attacks | REQ-SEC-O2-1

SEC-CTL-O2-2

REQ-SEC-DOS-1 | Medium | -| T-HW-01 | A successful attack could:
- Maliciously placed VM/Container extracts information from the target VM/Container with the side channel attack | Tampering, Information disclosure, Denial of Service | C, I, A | High | High |
  • Adverse impacts (High),
  • ZTA (High)
| Adverse Impact (High) - No existing requirements

ZTA (High): Reconnaissance and availability type attacks | | High | -| T-HW-02 | A successful attack could:
- Extract useful information such as cryptographic keys from the target VM/Container to use them for traffic eavesdropping and man-in-the-middle attacks. | Tampering, Information disclosure, Denial of Service | C, I, A | High | High |
  • Adverse impacts (High),
  • ZTA (High)
| Adverse Impact (High) - No existing requirements

ZTA (High): Reconnaissance and availability type attacks | | High | -| T-AAL-01 | A successful attack could:
- tamper the requests/responses sent between the AAL components, the O-Cloud platform and O-RAN APPs/VNFs/CNFs | Tampering | I | High | Medium | Adverse impacts (Medium), ZTA (High) | Adverse impacts (High) – Not security requirements yet for AAL in O-RAN security specifications

ZTA (Medium): Integrity type attacks | | High | -| T-AAL-02 | A successful attack could:
- cause DoS attack or increased traffic on AAL interfaces | Denial of Service | A | High | Medium | Adverse impacts (Medium), ZTA (High) | Adverse impacts (High) – Not security requirements yet for AAL in O-RAN security specifications

ZTA (Medium): Availability type attacks | | High | -| T-AAL-03 (a) | Fail to clear resources | Information disclosure | C | High | High | Adverse impacts (High), ZTA (High) | Adverse impacts (High) – Not security requirements yet for AAL in O-RAN security specifications

ZTA (High): reconnaissance type attacks | | High | -| T-AAL-03 (b) | Fail to clear resources | Denial of service | A | High | Medium | Adverse impacts (High), | Adverse impacts (High) – Not security requirements yet for AAL | | High | - -| | | | | | | | | | | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------|---------|------|--------|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------| -| | | | | | | ZTA (Medium) | in O-RAN security specifications
ZTA (Medium): Availability type attacks | | | -| T-AAL-04 (a) | HAM compromise | Tampering | I | High | Medium | Adverse impacts (High), ZTA (Medium) | Adverse impacts (High) – Not security requirements yet for AAL in O-RAN security specifications
ZTA (Medium): Integrity type attacks | | High | -| T-AAL-04 (b) | HAM compromise | Denial of service | A | High | Medium | Adverse impacts (High), ZTA (Medium) | Adverse impacts (High) – Not security requirements yet for AAL in O-RAN security specifications
ZTA (Medium): Availability type attacks | | High | -| T-AAL-05 (a) | Malicious memory accesses | Information disclosure | C | High | High | Adverse impacts (High), ZTA (High) | Adverse impacts (High) – Not security requirements yet for AAL in O-RAN security specifications
ZTA (High): reconnaissance type attacks | | High | -| T-AAL-05 (b) | Malicious memory accesses | Tampering | I | High | Medium | Adverse impacts (High), ZTA (Medium) | Adverse impacts (High) – Not security requirements yet for AAL in O-RAN security specifications
ZTA (Medium): Integrity type attacks | | High | -| T-AAL-05 (c) | Malicious memory accesses | Denial of service | A | High | Medium | Adverse impacts (High), ZTA (Medium) | Adverse impacts (High) – Not security requirements yet for AAL in O-RAN security specifications
ZTA (Medium): Availability type attacks | | High | -| T-AAL-06 (a) | Software attacks | Information disclosure | C | High | High | Adverse impacts (High), ZTA (High) | Adverse impacts (High) – Not security requirements yet for AAL in O-RAN security specifications
ZTA (High): reconnaissance type attacks | | High | -| T-AAL-06 (b) | Software attacks | Tampering | I | High | Medium | Adverse impacts (High), ZTA (Medium) | Adverse impacts (High) – Not security requirements yet for AAL in O-RAN security specifications
ZTA (Medium): Integrity type attacks | | High | -| T-O-CLOUD-ID-01 | In the O-Cloud environment, the reuse of IDs from deleted objects for new objects can lead to unintended data associations, leaks, and operational disruptions. | Tampering, Information disclosure | C, I | High | High | Adverse impacts (High), ZTA (High) | Adverse impacts (High) – Not security requirements yet for O-Cloud ID in O-RAN security specifications
ZTA (High): reconnaissance and integrity type attacks | | High | -| T-O-CLOUD-ID-02 | In O-Cloud deployments, replacing failed machines without proper management of their corresponding Node objects can lead to resource mismatches, | Spoofing, Tampering, Information disclosure, Denial of Service | C, I, A | High | High | Adverse impacts (High), ZTA (High) | Adverse impacts (High) – Not security requirements yet for O-Cloud ID in O-RAN security specifications
ZTA (High): reconnaissance, integrity, and availability type | | High | - -| | | | | | | | | | | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|---------|--------|--------|-----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|--------| -| | stale data inheritance, and network inconsistencies. | | | | | | attacks | | | -| T-O-CLOUD-ID-03 | In the O-Cloud environment, improper management of object IDs can lead to overlaps, inconsistencies, unauthorized access, and operational disruptions. | Spoofing, Tampering, Information Disclosure, Repudiation, Elevation of Privilege, Denial of Service | C, I, A | High | High | Adverse impacts (High), ZTA (High) | Adverse impacts (High) – Not security requirements yet for O-Cloud ID in O-RAN security specifications

ZTA (High): reconnaissance, integrity, and availability type attacks | | High | -| T-ADMIN-01 | A successful attack could:
- Lead to the inability to react to changing resource requirements
- Operators may be unable to retrieve logs, telemetry data
- Prevents the O-Cloud software update (VNFs/CNFs, VL) to exploit a known security flaw in the O-Cloud software | Denial of Service | A | Medium | Medium | • Adverse impacts (Medium),
• ZTA (Medium) | Adverse impacts (Medium) – Requirements are defined for the protection against DoS attacks and for the protection of O-Cloud API and O2 interface in the O-RAN security specifications

ZTA (Medium): Availability type attacks | REQ-SEC-DOS-1 | Medium | -| T-ADMIN-02 | A successful attack could:
- Deploy new instances and disrupt existing O-Cloud services
- Submit compromised VM/Container images that unsuspecting tenants then use to initiate O-Cloud services
- Extract business data, configuration data, user data and possibly credentials
- Create backups of VM/Container instances or export VM/Container images | Tampering, Information disclosure, Denial of Service and Elevation of privilege | C, I, A | Medium | High | • Adverse impacts (High),
• ZTA (High) | Adverse impacts (Medium) – Requirements are defined for the protection of O-Cloud API and O2 interface in the O-RAN security specifications

ZTA (High): Reconnaissance and availability type attacks | REQ-SEC-PASS-1

REQ-SEC-O2-1

SEC-CTL-O2-2

REQ-SEC-DOS-1 | High | -| T-AIML-IM-1 | A successful attack could:
- Take alter a subset of the training data by inserting or modifying training samples | Integrity | I | High | Low | • Impact on integrity (High)
• Threat event initiation (low) | • Impact on integrity: Bad training data will cause the model to behave incorrectly
• Threat event initiation: needs high sophistication to execute | | Medium | -| T-AIML-IM-2 | A successful attack could:
- generate adversarial examples in the model | Tampering | I | High | Low | • Impact on integrity (High)
• Threat event initiation (low) | • Impact on integrity: major change in normal AI/ML functioning
• Threat event initiation: needs high sophistication to | | Medium | - -| | | | | | | | | | | -|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------|---|------|--------|--------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|--|--------| -| | | | | | | | execute | | | -| T-AIML-IM-3 | A successful attack could:
- mis-assign labels to training data | Tampering | I | High | Low | • Impact on integrity (High)
• Threat event initiation (low) | • Impact on integrity: major change in normal AI/ML functioning
• Threat event initiation: needs high sophistication to execute | | Medium | -| T-AIML-IM-4 | A successful attack could:
- allow an adversary to submit queries to the model and receive predictions (either labels or model confidences) and confidential data | Confidentiality | C | High | Low | • Impact on confidentiality (High)
• Threat event initiation (low) | • Impact on confidentiality: major change in normal AI/ML functioning
• Threat event initiation: needs high sophistication to execute | | Medium | -| T-AIML-DP-01 | A successful attack could:
-inject poisoned data which can be consumed by AI/ML for training. | Tampering | I | High | Medium | • Impact on integrity (High)
• Threat event initiation (Medium) | • Impact on integrity: major change in normal AI/ML functioning
• Threat event initiation: needs sophistication to execute | | High | -| T-AIML-DP-02 | A successful attack could:
-enable the attacker to get more details about the AI/ML algorithms being used and parameters configured if any | Tampering | I | High | Medium | • Impact on integrity (High)
• Threat event initiation (Medium) | • Impact on integrity: major change in normal AI/ML functioning
• Threat event initiation: needs sophistication to execute | | High | -| T-AIML-DP-03 | A successful attack could:
- enable the attacker to modify the behaviour of AI/ML algorithm with slow poisoning | Tampering | I | High | Medium | • Impact on integrity (High)
• Threat event initiation (Medium) | • Impact on integrity: major change in normal AI/ML functioning
• Threat event initiation: needs sophistication to execute | | High | -| T-AIML-MEI-01 | A successful attack based on level of information available to attacker can result in disclosing specific individual's data used in training the model | Information Disclosure | C | High | Medium | • Impact on confidentiality (High)
• Threat event initiation (Medium) | • Impact on confidentiality: Knowledge of information used in training gets exposed
• Threat event initiation needs sophistication to execute | | High | -| T-AIML-MEI-02 | A successful attack based on analysis methods used by the attacker can result in disclosing specific individual's data used in training the model | Information Disclosure | C | High | Medium | • Impact on confidentiality (High)
• Threat event initiation (Medium) | • Impact on confidentiality: Knowledge of information used in training gets exposed
• Threat event initiation needs sophistication to execute | | High | -| T-AIML-MEI-03 | A successful target based attack can result | Information Disclosure | C | High | Medium | • Impact on confidentiality | • Impact on confidentiality: Knowledge of information | | High | - -| | | | | | | | | | | -|---------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|----|------|--------|--------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|--|--------| -| | in disclosing specific individual's data or a group's data used in training the model | | | | | (High)
• Threat event initiation (Medium) | used in training gets exposed
• Threat event initiation needs sophistication to execute | | | -| T-AIML-ME-01 | A successful attack could:
-Cause theft of intellectual property
-Undermine the original developer's competitive advantage | Confidentiality | C | High | Low | • Impact on confidentiality (High)
• Threat event initiation (low) | • Impact on confidentiality: Disclosure of high value information
• Threat event initiation: needs high sophistication to execute | | Medium | -| T-AIML-ME-02 | A successful attack could:
-Cause privacy breaches | Confidentiality | C | High | Low | • Impact on confidentiality (High)
• Threat event initiation (low) | • Impact on confidentiality: Disclosure of high value information
• Threat event initiation: needs high sophistication to execute | | Medium | -| T-AIML-ME-03 | A successful attack could:
-allow adversarial attacks
-allow targeted attacks | Tampering | I | High | Low | • Impact on integrity (High)
• Threat event initiation (low) | • Impact on integrity: major change in normal AI/ML functioning
• Threat event initiation: needs high sophistication to execute | | Medium | -| T-AIML-MOI-01 | A successful attack could:
- Cause disclosure of sensitive/proprietary data | Confidentiality | C | High | Medium | • Impact on confidentiality (High)
• Threat event initiation (medium) | • Impact on confidentiality: Disclosure of high value information
• Threat event initiation: needs medium sophistication to execute | | High | -| T-AIML-MOI-02 | A successful attack could:
- allow an attacker to reconstruct the original training data with higher accuracy | Confidentiality | C | High | Low | • Impact on confidentiality (High)
• Threat event initiation (low) | • Impact on confidentiality: major change in normal AI/ML functioning
• Threat event initiation: needs high sophistication to execute | | Medium | -| T-AIML-SC-01 | A successful attack could:
-corrupt or manipulate training datasets
- cause degraded performance, wrong decisions, or even backdoors in the final system | Tampering, Denial of Service | IA | High | Medium | • Impact on confidentiality (High)
• Threat event initiation (Medium) | needs sophistication to execute | | High | -| T-AIML-SC-02 | A successful attack could:
-inject malicious code or logic into the AI model itself during training or deployment | Tampering, Confidentiality | CI | High | Low | • Impact on confidentiality (High)
• Threat event initiation (low) | needs high sophistication to execute | | Medium | - -| | | | | | | | | | | -|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|----|------|--------|----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--------| -| T-AIML-SC-03 | A successful attack could:
-infect the model with malicious code that remains dormant until it receives a specific trigger | Tampering, Confidentiality | CI | High | Low |
  • Impact on confidentiality (High)
  • Threat event initiation (low)
| needs high sophistication to execute | | Medium | -| T-AIML-SC-04 | A successful attack could:
-manipulate the hardware used for AI processing, such as GPUs, ASICs, or FPGAs | Tampering, Confidentiality | CI | High | Low |
  • Impact on confidentiality (High)
  • Threat event initiation (low)
| needs high sophistication to execute | | Medium | -| T-AIML-SC-05 | A successful attack could:
-inject malicious code or exfiltrate sensitive information from the target system. | Tampering, Confidentiality | CI | High | Low |
  • Impact on confidentiality (High)
  • Threat event initiation (low)
| needs high sophistication to execute | | Medium | -| T-AIML-SC-06 | A successful attack could:
-insert vulnerabilities or backdoors that attackers can exploit | Tampering, Confidentiality | CI | High | High |
  • Impact on confidentiality (High)
  • Threat event initiation (High)
| needs high sophistication to execute | | High | -| T-AIML-OI-01 | A successful attack could cause :
- service disruption of the O-RAN elements that are using configuration / policies derived from the manipulated output of a model . | Denial of Service | A | High | Medium |
  • Impact on Availability (High)
  • Adverse impacts (Medium)
|
  • Impact on Availability (High): Prolonged interruption of operations.
  • Adverse impacts (Medium) – O-RAN ALLIANCE has specified security for O-RAN interfaces at the transport layers thereby mitigating access to O-RAN functions through the interfaces. The O-RAN ALLIANCE has not yet specified security for regarding the Training or test data sets collected externally or internally, Trained ML model, ML prediction results .
| | High | -| T-AIML-OI-02 | AI/ML models are used to perform QoE optimization and QoE based traffic steering in O-RAN [i.14]. A carefully crafted manipulation of the output of AI/ML model can be used to degrade the QoE of a | Tampering | I | High | Medium |
  • Impact on Integrity (High)
  • Adverse impacts (Medium)
|
  • Impact on Integrity (High): Major change in normal AI/ML system functioning.
  • Adverse impacts (Medium) – O-RAN ALLIANCE has specified security for O-RAN interfaces at the transport layers thereby mitigating access to O-RAN functions through the interfaces. The
| | High | - -| | | | | | | | | | | -|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---|------|--------|------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|--------| -| | subscriber or a group of subscribers. | | | | | | O-RAN ALLIANCE has not yet specified security for regarding the Training or test data sets collected externally or internally, Trained ML model, ML prediction results . | | | -| T-AIML-MP-01 | A successful attack can change the parameters file which will cause the model to make incorrect predictions. | Tampering | I | High | Medium |
  • Impact on integrity (High)
  • Threat event initiation (Medium)
|
  • Impact on integrity: major change in normal AI/ML functioning
  • Threat event initiation needs sophistication to execute
| | High | -| T-AIML-MP-02 | A successful attack can change the inference algorithm which will cause the model to make incorrect predictions. | Tampering | I | High | Medium |
  • Impact on integrity (High)
  • Threat event initiation (Medium)
|
  • Impact on integrity: major change in normal AI/ML functioning
  • Threat event initiation needs sophistication to execute
| | High | -| T-AIML-MP-03 | A successful attack can change the learning algorithm which will cause the model to make incorrect predictions. | Tampering | I | High | Medium |
  • Impact on integrity (High)
  • Threat event initiation (Medium)
|
  • Impact on integrity: major change in normal AI/ML functioning
  • Threat event initiation needs sophistication to execute
| | High | -| T-AIML-MP-04 | A successful attack could:
- create a Trojan trigger in the model
-send malicious local model updates in federated learning | Integrity | I | High | Low |
  • Impact on integrity (High)
  • Threat event initiation (low)
|
  • Impact on integrity: Disclosure of high value information
  • Threat event initiation: needs high sophistication to execute
| | Medium | -| T-AIML-MS-01 | A successful attack could:
modify data which can result in a skewed trained model resulting in incorrect ML output | Tampering | I | High | Medium |
  • Impact on integrity (High)
  • Threat event initiation (Medium)
|
  • Impact on integrity: major change in normal AI/ML functioning
  • Threat event initiation needs sophistication to execute
| | High | -| T-AIML-MS-02 | A successful attack could:
manipulate the feedback mechanism used by AI/ML for continuous improvement during deployment, which can be result in a skewed trained model resulting in incorrect ML output | Tampering | I | High | Medium |
  • Impact on integrity (High)
  • Threat event initiation (Medium)
|
  • Impact on integrity: major change in normal AI/ML functioning
  • Threat event initiation needs sophistication to execute
| | High | - -| | | | | | | | | | | -|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|----|------|--------|-------------------------------------------------------------------------------------|--------------------------------------|--|--------| -| T-AIML-TL-01 | A successful attack could:
-corrupt or manipulate training datasets
- cause degraded performance, wrong decisions, or even backdoors in the final system | Tampering | I | High | Medium | • Impact on integrity (High)
• Threat event initiation (Medium) | needs sophistication to execute | | High | -| T-AIML-TL-02 | A successful attack could:
- extract sensitive information about its architecture and parameters | Confidentiality | C | High | Low | • Impact on confidentiality (High)
• Threat event initiation (low) | needs high sophistication to execute | | Medium | -| T-AIML-TL-03 | A successful attack could:
- bypass security systems or cause misclassifications in critical applications like self-driving cars or healthcare. | Tampering | I | High | Low | • Impact on integrity (High)
• Threat event initiation (low) | needs high sophistication to execute | | Medium | -| T-AIML-TL-04 | A successful attack could:
-infect the model with malicious code that remains dormant until it receives a specific trigger | Tampering, Confidentiality | CI | High | Low | • Impact on confidentiality and integrity (High)
• Threat event initiation (low) | needs high sophistication to execute | | Medium | -| T-AIML-EL-01 | A successful attack could:
- deduce the structure of the neural network, including the types of layers, their sequence, and possibly hyperparameters | Confidentiality | C | High | Low | • Impact on confidentiality (High)
• Threat event initiation (Low) | needs high sophistication to execute | | Medium | -| T-AIML-EL-02 | A successful attack could:
- make inferences about the input data, potentially leading to privacy breaches, especially if the data is sensitive | Confidentiality | C | High | Low | • Impact on confidentiality (High)
• Threat event initiation (low) | needs high sophistication to execute | | Medium | -| T-AIML-EL-03 | A successful attack could:
- maximize energy consumption or computation time, leading to a denial of | Denial of Service | A | High | Low | • Impact on availability (High)
• Threat event initiation (low) | needs high sophistication to execute | | Medium | - -| | | | | | | | | | | -|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|------|--------|------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------| -| | service by overloading the system or draining battery life. | | | | | | | | | -| T-AIML-EV-01 | A successful attack could:
- Compromise Authentication Systems tricking AI/ML systems into granting access to unauthorized users
- Undermine Integrity of Data by tricking AI/ML systems into drawing incorrect conclusions | Tampering | I | High | Medium |
  • Impact on integrity (High)
  • Threat event initiation (Medium)
| needs sophistication to execute | | High | -| T-AIML-EV-02 | A successful attack could:
- Compromise Authentication Systems tricking AI/ML systems into granting access to unauthorized users
- Undermine Integrity of Data by tricking AI/ML systems into drawing incorrect conclusions | Tampering | I | High | Medium |
  • Impact on integrity (High)
  • Threat event initiation (Medium)
| needs sophistication to execute | | High | -| T-AIML-EV-03 | A successful attack could:
- Compromise Authentication Systems tricking AI/ML systems into granting access to unauthorized users
- Undermine Integrity of Data by tricking AI/ML systems into drawing incorrect conclusions | Tampering | I | High | Medium |
  • Impact on integrity (High)
  • Threat event initiation (Medium)
| needs sophistication to execute | | High | -| T-TS-01 | Disruption or manipulation of the time synchronization process within the O-Cloud environment can lead to severe security and operational issues. | An attacker may target the time synchronization mechanisms to alter time settings across nodes, leading to data integrity loss, authentication and authorization bypass, and operational disruption. | I, A | High | Medium |

Impact of Integrity and Availability (High)

Threat Event Initiation (Medium)

|

Impact of Integrity and Availability (High): due to potential widespread operational and security impacts, including data integrity loss and operational disruptions affecting multiple nodes.

Threat Event Initiation

| | High | - -| | | | | | | | | | | -|---------------|----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|------|------|--------|---------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------| -| | | | | | | | (Medium): it requires elevated privileges to modify time synchronization settings. | | | -| T-AppLCM-01 | Compromise of App/VNF/CNF update package integrity during onboarding | A successful attack could result in the injection of malicious code into the update package before onboarding, potentially compromising the O-RAN system. | I, A | High | Medium |
  • Impact on integrity (High)
  • Threat event initiation (Medium)
|
  • High impact because it compromises the supply chain.
  • Medium likelihood due to required access to SMO or onboarding process.
| | High | -| T-AppLCM-02 | Compromise of App/VNF/CNF update image integrity during instantiation | A successful attack could modify the update image during instantiation to deploy malicious code, potentially disrupting O-RAN services. | I, A | High | Medium |
  • Impact on integrity (High)
  • Threat event initiation (Medium)
|
  • High impact as tampering can propagate malicious code.
  • Medium likelihood since access to the O-Cloud platform is needed.
| | High | -| T-AppLCM-03 | Downgrade attack to vulnerable application version | A successful attack could force a system downgrade to a vulnerable application version, potentially exposing the O-RAN system to known exploits. | I, A | High | Medium |
  • Impact on integrity and availability (High)
  • Threat event initiation (Medium)
|
  • High impact as older vulnerabilities are reintroduced.
  • Medium likelihood since attackers need control over version management.
| | High | -| T-AppLCM-04 | Attacker exploits missing or improperly defined elements of application's SecurityDescriptor | A successful attack could exploit improperly defined elements in the application's SecurityDescriptor, potentially leading to unauthorized access. | A | High | Medium |
  • Impact on availability and authorization (High)
  • Threat event initiation (Medium)
|
  • High impact as resource misuse or privilege escalation can occur.
  • Medium likelihood because discovering misconfigurations requires effort.
| | High | -| T-AppLCM-05 | Malicious actor modifies application's SecurityDescriptor to gain unauthorized access | A successful attack could modify the SecurityDescriptor to gain unauthorized access. | I | High | Medium |
  • Impact on integrity (High)
  • Threat event initiation (Medium)
|
  • High impact as it undermines security controls.
  • Medium likelihood as descriptor modification requires access.
| | High | -| T-AppLCM-05 A | Malicious actor modifies application's SecurityDescriptor to degrade services | A successful attack could modify the SecurityDescriptor, potentially disrupting services and degrading performance. | I, A | High | Medium |
  • Impact on integrity and availability (High)
  • Threat event initiation (Medium)
|
  • High impact due to potential service degradation.
  • Medium likelihood since descriptor access is required but feasible.
| | High | -| T-AppLCM-06 | Improper decommissioning of application | Improper decommissioning of an application risks exposing credentials and misallocating resources. | C, A | High | Medium |
  • Impact on confidentiality and availability (High)
  • Threat event initiation
|
  • High impact depending on exposed secrets.
  • Medium likelihood as decommissioning oversights are common.
| | High | - -| | | | | | | | | | | -|-------------|-------------------------------------------------|---------------------------------------------------------------------------------------------------------|---|------|--------|------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------| -| | | | | | | (Medium) | | | | -| T-AppLCM-07 | Improper deletion of application sensitive data | A successful attack could recover sensitive data (e.g., certificates, keys) left behind after deletion. | C | High | Medium |
  • Impact on confidentiality (High)
  • Threat event initiation (Medium)
|
  • High impact as exposed data could enable widespread breaches.
  • Likelihood depends on whether secure deletion is enforced.
| | High | - -1 - -# Annex: Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2025.12.02 | 08.00 | Final version 08.00 | -| 2025.12.02 | 07.00.03 | Update according to received notes from November train review | -| 2025.11.28 | 07.00.02 | Update according to received notes from November train review | -| 2025.11.21 | 07.00.01 | Integration of CRs:
  • • ERI CR 0279
  • • SYM CR 0101
  • • RMI CR 0063
  • • NOK CRs: 0304, 0328, 0315, 0303
  • • NEC CRs: 0068, 0070
| -| 2025.07.25 | 07.00 | Final version 07.00 | -| 2025.07.21 | 06.00.02 | Update according to received notes from July train review | -| 2025.07.14 | 06.00.01 | Integration of CRs:
  • • ERI CRs: 0223, 0235, 0237, 0241, 0242
  • • SYM CR 0094
| -| 2025.03.28 | 06.00 | Final version 06.00 | -| 2025.03.26 | 05.00.02 | Update according to received notes from March train review | -| 2025.03.21 | 05.00.01 | Integration of CRs:
  • • ATT CR 5005
  • • DTAG CR 0026
  • • ERI CR 0179
  • • NOK CR 0217
  • • MTR CRs 0139, 0141
  • • NEC CRs 0040, 0041, 0042, 0043, 0044, 0050, 0054
| -| 2024.12.06 | 05.00 | Final version 05.00 | -| 2024.12.04 | 04.00.04 | Update according to received notes from November train review | -| 2024.12.03 | 04.00.03 | Update according to received notes from November train review | -| 2024.12.02 | 04.00.02 | Update according to received notes from November train review | -| 2024.11.25 | 04.00.01 | Integration of CRs:
  • • NOK CRs: CR0181, CR0187, CR0190, CR0201, CR0203, CR0206, CR0207, CR0208, CR0210
  • • NEC CRs: CR0027, CR0029
  • • WG11 CRs: CR0048, CR0050
  • • ERI CR: CR0153
| -| 2024.07.26 | 04.00 | Final version 04.00 | -| 2024.07.24 | 03.00.03 | Update according to received notes from July train review | -| 2024.07.23 | 03.00.02 | Update according to received notes from July train review | -| 2024.07.10 | 03.00.01 | Implemented CRs: NOK CR0155, NOK CR0142, NOK CR0160, NOK CR0161, NOK CR0162, NOK CR0167, NOK CR0170, NOK CR0171, NOK CR0172, NEC CR0018, NEC CR0023, WG11 CR 0035, WG11 CR 0044, ATT CR 0022, ATT CR 0044, RMI CR 0020, RMI CR 0027, MTR CR 0096 | -| 2024.03.27 | 03.00 | Final version 03.00 | -| 2024.03.19 | 02.00.02 | Addressed editorial notes | -| 2024.03.15 | 02.00.01 | Implemented CRs ERI CR0103, MTR CR0081, SYM CR0040, NEC CR0007, NEC CR0011, WG11 CR0029 | -| 2023.11.22 | 02.00 | Final version 02.00 | -| 2023.11.21 | 01.00.02 | Update according to received notes from November train review | -| 2023.11.03 | 01.00.01 | Implemented CRs WG11 CR0015, MTR CR0004 | -| 2019.01.31 | 01.00 | Final version 01.00 | -| 2019.01.24 | 00.00.02 | Implemented CRs ERI-0011, NOK-0032 and DCM-0008 | -| 2019.01.22 | 00.00.01 | Create initial O-RAN version, with change-marks from previous content. | - -2 \ No newline at end of file diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg deleted file mode 100644 index 2b055e42a6634473c558bdfbfd9c49f3983a9d84..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fb6d4f0bb1f07035d4261566d51de3e9fe1bd3809a5abd75438eba18898ccced -size 4514 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/0f7b6492f9528be3f23fa03b5e12274a_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/0f7b6492f9528be3f23fa03b5e12274a_img.jpg deleted file mode 100644 index 8fb47c2efbbd2b6b4b141ca0dd7082dcb65148aa..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/0f7b6492f9528be3f23fa03b5e12274a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:291f7b3a8c52704c5e8734d25a63ced0957291a32715cebfad2dd4df776b129c -size 4111 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/18bb06865e2dada3656ea3d57f290f7f_img.jpg deleted file mode 100644 index 4176a275398437b2570285d9b9bf7319a7022239..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/18bb06865e2dada3656ea3d57f290f7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:494c824ca8af4040ea72f4234f56344a30b00726792f37deb4d215aab570c4b3 -size 18826 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index bf238570411b2c3c4801758e0b4fee8375ccb9f4..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/1baaba7a6e54e77197475726c871067d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef39b9b0dadf1b084c8b8bc63a0ff7d1585b6d745ca12ad8368f11082cad5a0 -size 4493 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg deleted file mode 100644 index e5c8757e13f22006b3f35503eabac1f2521aa858..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/1cac1845cf99a3f64ae00cd2bb4f9ed7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1fcbe70edb964f0023875cfdc04e4a2c5f88a246279d779487f8848d76c45307 -size 55420 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/1d648bacf7b4f1d0c2fbd884f070e151_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/1d648bacf7b4f1d0c2fbd884f070e151_img.jpg deleted file mode 100644 index c7238b9acf09a935a166102edc4e9f2c76ff30bf..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/1d648bacf7b4f1d0c2fbd884f070e151_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a9d40a4c0726620f7e260f38a44a9ec2789209fdafc042da4a60027681e752f7 -size 22237 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/2865fd60541ac34a704bc9e7af1041f7_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/2865fd60541ac34a704bc9e7af1041f7_img.jpg deleted file mode 100644 index 883c1b6ad3a48822b05f9cd9d63b8463349309ea..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/2865fd60541ac34a704bc9e7af1041f7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ce6147bf597aadb7815a626c0d3a1b92d02cd0c07dc8c1523a6a370c784d773 -size 24503 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg deleted file mode 100644 index bf238570411b2c3c4801758e0b4fee8375ccb9f4..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef39b9b0dadf1b084c8b8bc63a0ff7d1585b6d745ca12ad8368f11082cad5a0 -size 4493 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/2eea01382188b70064fa2818361d89f1_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/2eea01382188b70064fa2818361d89f1_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/2eea01382188b70064fa2818361d89f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg deleted file mode 100644 index 2b055e42a6634473c558bdfbfd9c49f3983a9d84..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fb6d4f0bb1f07035d4261566d51de3e9fe1bd3809a5abd75438eba18898ccced -size 4514 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/318db222fae24a59c370fa6471d541b8_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/318db222fae24a59c370fa6471d541b8_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/318db222fae24a59c370fa6471d541b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/35437f160e157760713aa85be471c3f3_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/35437f160e157760713aa85be471c3f3_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/35437f160e157760713aa85be471c3f3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index bf238570411b2c3c4801758e0b4fee8375ccb9f4..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef39b9b0dadf1b084c8b8bc63a0ff7d1585b6d745ca12ad8368f11082cad5a0 -size 4493 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/41aef1f5efab13d4f38f69e86c726062_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/41aef1f5efab13d4f38f69e86c726062_img.jpg deleted file mode 100644 index 0ecc8b669bec03f34ce50ee780d5eff34f0b26fb..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/41aef1f5efab13d4f38f69e86c726062_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e2f7b773df5740d3e630c07ab4418b6ce9ae3940380467b7db6cb3410ee76726 -size 48348 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4b398c5e8c4fd656d5b7a61806400650_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4b398c5e8c4fd656d5b7a61806400650_img.jpg deleted file mode 100644 index c8582b914bccfddbc0a32e2e083a3e1eedf0b04b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4b398c5e8c4fd656d5b7a61806400650_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a2d0e96fe8a34256f064e54e7e47e4fc3a9cd7ba7b28d8a9dd25d4e669e6dc80 -size 22558 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/5009e30a55479d3941af523871208f9d_img.jpg deleted file mode 100644 index 184c61cec01b73db269a70b80d38b29f8f43a523..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/5009e30a55479d3941af523871208f9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:01c495cf4867e2e7aca1ef3e8ada476c8155546bcb8c06d8fa8efbb55dafe4d9 -size 4516 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/59368942873b0c35eef79a7a985025dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/5bba23cc120ad806779f82df1c01bebf_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/5bba23cc120ad806779f82df1c01bebf_img.jpg deleted file mode 100644 index 96ebb51a75cbc23c60a89b10c8dd74a15889dbc8..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/5bba23cc120ad806779f82df1c01bebf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:71606e093c693b01ecc8d07de036f947f5f9faa21044716b73697bfd3dc75c47 -size 35393 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg deleted file mode 100644 index bf238570411b2c3c4801758e0b4fee8375ccb9f4..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef39b9b0dadf1b084c8b8bc63a0ff7d1585b6d745ca12ad8368f11082cad5a0 -size 4493 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/6588b1c7f14069d96744b473ad663248_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/66e89867f97592fd4bfab0e4f2b2054f_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/66e89867f97592fd4bfab0e4f2b2054f_img.jpg deleted file mode 100644 index 37eb81b873d111e0f6f380ab9219aed06e8b6d87..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/66e89867f97592fd4bfab0e4f2b2054f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b56f911b04b22cb26e535cf4b103f1cdabb801269ebaac86eab331943f211c9d -size 33513 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg deleted file mode 100644 index 683cccd7e2bfcf6d49188fd22bfa16c636343218..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1bdc9e4007f62e577a376f33059e73abd2ad86b415219bede0eb94cb27363595 -size 4680 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/84982d23836d5e77911a6ddd3332b7a5_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/84982d23836d5e77911a6ddd3332b7a5_img.jpg deleted file mode 100644 index de81bab68b6369552a17ec56871da7dc110861b6..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/84982d23836d5e77911a6ddd3332b7a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ef665019ae2be7f2b03f39a6ade541407d58f7ce32f4c63501e9788535a0cca4 -size 4579 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/854df8ad60507803253274673f9062cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8b4befaffc5166da571069410e207aea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8b9c4846ed8399faf767a527db889f35_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8b9c4846ed8399faf767a527db889f35_img.jpg deleted file mode 100644 index fe9db46d9a790d7ea7c98aa6905bb8b78dc888ae..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8b9c4846ed8399faf767a527db889f35_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe3018f33a4e52ca7162544504eb90d4176e3f315c7f293adea839307b2db058 -size 4477 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 938fd786025063a9c6794111fb69bd77335965cb..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:212b63a89a9aca91bc3cfde6374ccfac83928c957707deb22ff82d98204b63cc -size 4519 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9f50279046b74a4e66a1a0144c3b1d11_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9f50279046b74a4e66a1a0144c3b1d11_img.jpg deleted file mode 100644 index 965f76921018019b59c39d3b44414d5bc08727b7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/9f50279046b74a4e66a1a0144c3b1d11_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f40c1173537022c0552a329fb83aa2d05b8f86fea37878875a754e38da9a1fd7 -size 25069 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index e862f131a41db4ccb076cd05946d4a534a16866c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d1bf470e8c63cc3b3d7901d8b3d258ea5fa27acca8be2ab00fe448cf66bc5754 -size 4616 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 938fd786025063a9c6794111fb69bd77335965cb..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:212b63a89a9aca91bc3cfde6374ccfac83928c957707deb22ff82d98204b63cc -size 4519 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/aa6e28822419dba9f22129fee66c9c4c_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/aa6e28822419dba9f22129fee66c9c4c_img.jpg deleted file mode 100644 index 3fba1fb349e09a991f68908da3d40de6b988c7ea..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/aa6e28822419dba9f22129fee66c9c4c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a32b307e2312d30a42a04042412c9bf67ddfdcb4e604f73805874bdc096352eb -size 46749 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/ad555483986d7170a46ce72d164b5bc8_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/ad555483986d7170a46ce72d164b5bc8_img.jpg deleted file mode 100644 index 26353e702fd6843ea7632e268d7383d46a9949ed..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/ad555483986d7170a46ce72d164b5bc8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e87350ca8132ef436955f35d9789d3755e14cd1c68bb3ce2952798e3fc8a2fec -size 13159 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/aef4390a4629604196222b9ed006a786_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/aef4390a4629604196222b9ed006a786_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/aef4390a4629604196222b9ed006a786_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg deleted file mode 100644 index bf238570411b2c3c4801758e0b4fee8375ccb9f4..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef39b9b0dadf1b084c8b8bc63a0ff7d1585b6d745ca12ad8368f11082cad5a0 -size 4493 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c06fd7dbef68a8b788158f2081d9d734_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c06fd7dbef68a8b788158f2081d9d734_img.jpg deleted file mode 100644 index e3642c35396088b979dee92a39dac35480451955..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c06fd7dbef68a8b788158f2081d9d734_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a7f2d3c18b3ed97867ee8572f8ddcdec9be28011428f6ce26a238c2ee5b4be12 -size 41679 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg deleted file mode 100644 index 4b4a6004e0b39e75ca2a7fe1246416998d3aed6c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c3e8a7fe2e4f51806e05b9b1aae20d57_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:72ca58e78df49dd71c3d311e225713d04eec30df3ef5aa601c1fce218cce2adf -size 20003 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg deleted file mode 100644 index 2b055e42a6634473c558bdfbfd9c49f3983a9d84..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fb6d4f0bb1f07035d4261566d51de3e9fe1bd3809a5abd75438eba18898ccced -size 4514 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d35a80e3faed208324083399568c7461_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d35a80e3faed208324083399568c7461_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d35a80e3faed208324083399568c7461_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index 184c61cec01b73db269a70b80d38b29f8f43a523..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:01c495cf4867e2e7aca1ef3e8ada476c8155546bcb8c06d8fa8efbb55dafe4d9 -size 4516 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index e862f131a41db4ccb076cd05946d4a534a16866c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d1bf470e8c63cc3b3d7901d8b3d258ea5fa27acca8be2ab00fe448cf66bc5754 -size 4616 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index 938fd786025063a9c6794111fb69bd77335965cb..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:212b63a89a9aca91bc3cfde6374ccfac83928c957707deb22ff82d98204b63cc -size 4519 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/f74adaa1840504407cd4272995426f82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 938fd786025063a9c6794111fb69bd77335965cb..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:212b63a89a9aca91bc3cfde6374ccfac83928c957707deb22ff82d98204b63cc -size 4519 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/facce731b2dbfae43a8609231a700be1_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/facce731b2dbfae43a8609231a700be1_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/facce731b2dbfae43a8609231a700be1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 57842b0349bd33ea7a2c39ae2f7d6548646450d5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bbf7d89f9fc9bdcae61bc8efea3545da79b29264b690fbc360f6ea47d62f4fc7 -size 4511 diff --git a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/ff0952ef692c9d960ce5f6708bcc9711_img.jpg deleted file mode 100644 index cd687634ec29b48fd78f8296c2d11725f39e174e..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.Threat-Modeling-R005-v08.00/images/ff0952ef692c9d960ce5f6708bcc9711_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2213d14522545ea71ef165817f2cbebeffdce90f21213a538523fdff3242f5cd -size 73864 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/doc.md b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/doc.md deleted file mode 100644 index aa8169a4c37ca3874c44544f3785fa1d3f1cf335..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/doc.md +++ /dev/null @@ -1,4675 +0,0 @@ - - -# **O-RAN Work Group 11 (Security Work Group)** - -# **Study on Zero Trust Architecture for O-RAN** - -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., Buschkauer Weg 27, 53347 Alfter, Germany -Register of Associations, Bonn VR 11238, VAT ID DE321720189 - -# --- Contents - -| | | -|-------------------------------------------------------|----| -| List of figures..... | 5 | -| List of tables..... | 6 | -| Foreword..... | 9 | -| Modal verbs terminology..... | 9 | -| Introduction..... | 9 | -| 1 Scope..... | 11 | -| 2 References..... | 12 | -| 2.1 Normative references..... | 12 | -| 2.2 Informative references..... | 12 | -| 3 Definition of terms, symbols and abbreviations..... | 14 | -| 3.1 Terms..... | 14 | -| 3.2 Symbols..... | 15 | -| 3.3 Abbreviations..... | 15 | -| 4 NIST Zero Trust Tenet Applicability..... | 17 | -| 4.1 NIST ZT Tenets overview..... | 17 | -| 4.2 NIST ZT Tenets applicability study..... | 18 | -| 4.2.1 ZT Tenet 1 Applicability Study..... | 18 | -| 4.2.2 ZT Tenet 2 Applicability Study..... | 18 | -| 4.2.3 ZT Tenet 3 Applicability Study..... | 19 | -| 4.2.4 ZT Tenet 4 Applicability Study..... | 21 | -| 4.2.5 ZT Tenet 5 Applicability Study..... | 22 | -| 4.2.6 ZT Tenet 6 Applicability Study..... | 22 | -| 4.2.7 ZT Tenet 7 Applicability Study..... | 24 | -| 4.3 NIST ZT Tenets applicability summary..... | 24 | - -| | | | -|-------|---------------------------------------------------------|----| -| 5 | ZTA Assets..... | 26 | -| 5.1 | Asset Categories..... | 26 | -| 5.2 | Defined Assets..... | 27 | -| 5.3 | New Assets..... | 28 | -| 5.3.1 | New Assets in the SMO..... | 28 | -| 5.3.2 | O-Cloud Assets..... | 29 | -| 5.3.3 | New Assets in the Open Fronthaul..... | 30 | -| 5.3.4 | New Assets in F1 (Midhaul)..... | 31 | -| 6 | Reference ZTA Security Requirements..... | 32 | -| 6.1 | ZTA Framework..... | 32 | -| 6.1.1 | Introduction..... | 32 | -| 6.1.2 | CISA's Zero Trust Maturity Model (ZTMM)..... | 32 | -| 6.1.3 | DoD Zero Trust Strategy and Reference Architecture..... | 33 | -| 6.1.4 | Comparison of ZTMM models..... | 34 | -| 6.1.5 | Selection of CISA ZTMM Model..... | 35 | -| 6.2 | Target ZTA Security Requirements..... | 35 | -| 6.2.1 | Introduction..... | 35 | -| 6.2.2 | Identity..... | 36 | -| 6.2.3 | Devices..... | 38 | -| 6.2.4 | Networks..... | 40 | -| 6.2.5 | Applications and Workloads..... | 42 | -| 6.2.6 | Data..... | 45 | -| 6.2.7 | Cross-Cutting Capabilities..... | 48 | -| 7 | Alignment to Target ZTA Requirements..... | 55 | -| 7.1 | Introduction..... | 55 | -| 7.2 | Current O-RAN Security Requirements and Controls..... | 55 | -| 7.3 | Gap Analysis..... | 57 | -| 7.3.1 | Gap Analysis Methodology..... | 57 | - -7.3.2 Transversal Functions Gap Analysis.....59 - -7.3.3 xApp and Near-RT RIC Gap Analysis..... 64 - -7.3.4 E2 Interface Gap Analysis..... 79 - -7.3.5 Y1 Interface Gap Analysis..... 82 - -7.3.6 rApp and Non-RT RIC Gap Analysis..... 85 - -7.3.7 A1 Interface Gap Analysis..... 102 - -7.3.8 R1 Interface Gap Analysis..... 105 - -7.3.9 SMO Gap Analysis..... 108 - -7.3.10 O1 Interface Gap Analysis..... 121 - -7.3.11 O-Cloud Gap Analysis..... 126 - -7.3.12 O2 Interface Gap Analysis..... 142 - -7.3.13 O-CU Gap Analysis..... 146 - -7.3.14 O-DU Gap Analysis..... 156 - -7.3.15 O-RU Gap Analysis..... 166 - -7.3.16 Open Fronthaul Interface Gap Analysis..... 175 - -7.4 WG11 Considerations for Mapping Security Controls to CISA ZTMM..... 183 - -7.4.1 Introduction..... 183 - -7.4.2 Mapping to CISA ZTMM..... 184 - -8 ZTA Threats..... 186 - -8.1 Introduction..... 186 - -8.2 Mapping of the existing Security Principles to ZT Tenets..... 186 - -8.3 Existing defined threats..... 187 - -8.4 New threats..... 187 - -9 Threat analysis..... 188 - -10 Risk assessment..... 189 - -11 Recommendations..... 190 - -11.1 Preliminary Guidance for Future Work..... 190 - -11.2 Identified Gaps Out of Scope for O-RAN..... 191 - -| | | | -|---------|------------------------------------------|-----| -| 11.2.1 | Transversal Functions..... | 191 | -| 11.2.2 | xApp and Near-RT RIC..... | 191 | -| 11.2.3 | E2 Interface..... | 192 | -| 11.2.4 | Y1 Interface..... | 193 | -| 11.2.5 | rApp and Non-RT RIC..... | 194 | -| 11.2.6 | A1 Interface..... | 195 | -| 11.2.7 | R1 Interface..... | 196 | -| 11.2.8 | SMO..... | 197 | -| 11.2.9 | O1 Interface..... | 197 | -| 11.2.10 | O-Cloud..... | 198 | -| 11.2.11 | O2 Interface..... | 198 | -| 11.2.12 | O-CU..... | 198 | -| 11.2.13 | O-DU..... | 198 | -| 11.2.14 | O-RU..... | 198 | -| 11.2.15 | Open Fronthaul Interface..... | 198 | -| 11.3 | Identified Gaps Requiring No Action..... | 198 | -| 11.3.1 | Transversal Functions..... | 199 | -| 11.3.2 | xApp and Near-RT RIC..... | 199 | -| 11.3.3 | E2 Interface..... | 199 | -| 11.3.4 | Y1 Interface..... | 200 | -| 11.3.5 | rApp and Non-RT RIC..... | 200 | -| 11.3.6 | A1 Interface..... | 200 | -| 11.3.7 | R1 Interface..... | 200 | -| 11.3.8 | SMO..... | 200 | -| 11.3.9 | O1 Interface..... | 200 | -| 11.3.10 | O-Cloud..... | 200 | -| 11.3.11 | O2 Interface..... | 200 | -| 11.3.12 | O-CU..... | 200 | -| 11.3.13 | O-DU..... | 200 | - -11.3.14 O-RU.....201 - -11.3.15 Open Fronthaul Interface..... 201 - -Annex: Change history/Change request (history)..... 202 - -# --- List of figures - -Figure 6.1-1: CISA Zero Trust Maturity Model..... 32 - -Figure 6.1-2: DoD ZT Capabilities.....34 - -Figure 6.1-3: Comparison of US CISA and DoD ZTMM.....35 - -Figure 7.3-1 Gap Analysis Workflow.....57 - -# --- List of tables - -| | | -|-----------------------------------------------------------------------------------------|-----| -| Table 4.3-1: NIST ZT Tenet Applicability Summary..... | 25 | -| Table 5.2-1: High Level ZTA Assets for O-RAN..... | 27 | -| Table 5.3.1-1: SMO Assets..... | 28 | -| Table 5.3.2-1: O-Cloud Assets..... | 29 | -| Table 5.3.3-1: Open Fronthaul Assets..... | 30 | -| Table 5.3.4-1: F1 Assets..... | 31 | -| Table 7.2-1: O-RAN interface security controls (See NOTE for 802.1X and PDCP)..... | 55 | -| Table 7.2-2: O-RAN Cross-Platform Security Requirements..... | 56 | -| Table 7.3.1-1: Options for Work Item Analysis Conclusions..... | 58 | -| Table 7.3.1-2: Mapping of O-RAN Assets and Other Components to Different Pillars..... | 59 | -| Table 7.3.2-1: Transversal Functions Data Pillar Gap Analysis..... | 59 | -| Table 7.3.2-2: Transversal Functions Identity Pillar Gap Analysis..... | 61 | -| Table 7.3.2-3: Transversal Functions Networks Pillar Gap Analysis..... | 62 | -| Table 7.3.2-4: Transversal Functions Devices Pillar Gap Analysis..... | 63 | -| Table 7.3.3-1: xApp and Near-RT RIC Data Pillar Gap Analysis..... | 65 | -| Table 7.3.3-2: xApp and Near-RT RIC Applications and Workloads Pillar Gap Analysis..... | 71 | -| Table 7.3.3-3: xApp and Near-RT RIC Identity Pillar Gap Analysis..... | 75 | -| Table 7.3.3-4: xApp and Near-RT RIC Networks Pillar Gap Analysis..... | 77 | -| Table 7.3.4-1: E2 Interface Data Pillar Gap Analysis..... | 79 | -| Table 7.3.4-2: E2 Interface Networks Pillar Gap Analysis..... | 81 | -| Table 7.3.5-1: Y1 Interface Data Pillar Gap Analysis..... | 82 | -| Table 7.3.5-2: Y1 Interface Networks Pillar Gap Analysis..... | 84 | -| Table 7.3.6-1: rApp and Non-RT RIC Data Pillar Gap Analysis..... | 86 | -| Table 7.3.6-2: rApp and Non-RT RIC Applications and Workloads Pillar Gap Analysis..... | 93 | -| Table 7.3.6-3: rApp and Non-RT RIC Identity Pillar Gap Analysis..... | 97 | -| Table 7.3.6-4: rApp and Non-RT RIC Networks Pillar Gap Analysis..... | 100 | -| Table 7.3.7-1: A1 Interface Data Pillar Gap Analysis..... | 102 | -| Table 7.3.7-2: A1 Interface Networks Pillar Gap Analysis..... | 104 | -| Table 7.3.8-1: R1 Interface Data Pillar Gap Analysis..... | 105 | -| Table 7.3.8-2: R1 Interface Networks Pillar Gap Analysis..... | 107 | -| Table 7.3.9-1: SMO Data Pillar Gap Analysis..... | 109 | - -| | | -|-----------------------------------------------------------------------------------|-----| -| Table 7.3.9-2: SMO Application and Workloads Pillar Gap Analysis..... | 113 | -| Table 7.3.9-3: SMO Identity Pillar Gap Analysis..... | 117 | -| Table 7.3.9-4: SMO Networks Pillar Gap Analysis..... | 120 | -| Table 7.3.10-1: O1 Interface Data Pillar Gap Analysis..... | 121 | -| Table 7.3.10-2: O1 Interface Networks Pillar Gap Analysis..... | 125 | -| Table 7.3.11-1: O-Cloud Data Pillar Gap Analysis..... | 126 | -| Table 7.3.11-2: O-Cloud Applications and Workloads Pillar Gap Analysis..... | 131 | -| Table 7.3.11-3: O-Cloud Identity Pillar Gap Analysis..... | 134 | -| Table 7.3.11-4: O-Cloud Networks Pillar Gap Analysis..... | 138 | -| Table 7.3.11-5: O-Cloud Devices Pillar Gap Analysis..... | 139 | -| Table 7.3.12-1: O2 Interface Data Pillar Gap Analysis..... | 142 | -| Table 7.3.12-2: O2 Interface Networks Pillar Gap Analysis..... | 144 | -| Table 7.3.13-1: O-CU Data Pillar Gap Analysis..... | 147 | -| Table 7.3.13-2: O-CU Application and Workloads Pillar Gap Analysis..... | 151 | -| Table 7.3.13-3: O-CU Identity Pillar Gap Analysis..... | 153 | -| Table 7.3.13-4: O-CU Devices Pillar Gap Analysis..... | 155 | -| Table 7.3.14-1: O-DU Data Pillar Gap Analysis..... | 156 | -| Table 7.3.14-2: O-DU Applications and Workloads Pillar Gap Analysis..... | 161 | -| Table 7.3.14-3: O-DU Identity Pillar Gap Analysis..... | 163 | -| Table 7.3.14-4: O-DU Devices Pillar Gap Analysis..... | 165 | -| Table 7.3.15-1: O-RU Data Pillar Gap Analysis..... | 166 | -| Table 7.3.15-2: O-RU Applications and Workloads Pillar Gap Analysis..... | 170 | -| Table 7.3.15-3: O-RU Identity Pillar Gap Analysis..... | 172 | -| Table 7.3.15-4: O-RU Devices Pillar Gap Analysis..... | 174 | -| Table 7.3.16-1: Open Fronthaul Data Pillar Gap Analysis..... | 176 | -| Table 7.3.16-2: Open FH Interface Identity Pillar Gap Analysis..... | 180 | -| Table 7.3.16-3: Open Fronthaul Networks Pillar Gap Analysis..... | 182 | -| Table 7.4.2-1: CISA ZTMM Mapping of O-RAN security controls..... | 184 | -| Table 8.2-1: Mapping of security principles to ZT tenets..... | 187 | -| Table 11.2.1-1: Transversal Functions Identified Gaps Out of Scope for O-RAN..... | 191 | -| Table 11.2.2-1: xApp and Near-RT RIC Identified Gaps Out of Scope for O-RAN..... | 191 | -| Table 11.2.3-1: E2 Interface Identified Gaps Out of Scope for O-RAN..... | 192 | - -Table 11.2.4-1: Y1 Interface Identified Gaps Out of Scope for O-RAN..... 193 - -Table 11.2.5-1: rApp and Non-RT RIC Identified Gaps Out of Scope for O-RAN..... 194 - -Table 11.2.6-1: A1 Interface Identified Gaps Out of Scope for O-RAN..... 195 - -Table 11.2.7-1: R1 Interface Identified Gaps Out of Scope for O-RAN..... 196 - -Table 11.2.9-1: O1 Interface Identified Gaps Out of Scope for O-RAN..... 197 - -Table 11.3.1-1: Transversal Functions Identified Requiring No Action..... 199 - -Table 11.3.2-1: xApp and Near-RT RIC Identified Gaps Requiring No Action..... 199 - -Table 11.3.5-1: rApp and Non-RT RIC Identified Gaps Requiring No Action..... 200 - -# --- Foreword - -This Technical Report (TR) has been produced by WG11 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 - -In today's era of digital transformation, the complexity of a typical enterprise's infrastructure—encompassing multiple internal networks, remote offices, mobile users, and cloud services—has outstripped legacy perimeter-based network security methods, as there is no longer a single, easily identifiable perimeter for the enterprise [i.6]. The majority of cyber-attacks targeting applications and workloads stem from inadequate access control. Poor management of user, service, and device identities and credentials, along with the use of weak authentication mechanisms such as passwords, are often the underlying causes of security breaches. - -This complexity has led to the development of a new model for cybersecurity known as "Zero trust" (ZT). Zero trust responds to enterprise network trends such as remote users, bring your own device (BYOD) policies, and cloud-based assets not located within an enterprise-owned network boundary, which is a typical use case for O-RAN. Preventing lateral movement is crucial for protecting O-RAN from attackers who typically attempt lateral movement after initially exploiting the network. Traditional remote access solutions, such as VPNs, lack control over insider attacks and grant access to all on-site data, applications, and resources. Mitigating the risk of insider threats, breaches, and data exposure is essential to protecting O-RAN assets and resources. - -Zero trust is an evolving set of cybersecurity paradigms that shifts defenses from static, network-based perimeters to focus on users, assets, and resources. It assumes no implicit trust is granted to assets or user accounts based solely on their physical or network location or asset ownership. Zero trust provides a collection of concepts and ideas designed to minimize uncertainty in enforcing accurate, least-privilege per-request access decisions in information systems and services, even in a network viewed as compromised. The approach focuses on authentication, authorization, and - -shrinking implicit trust zones while maintaining availability and minimizing temporal delays in authentication mechanisms. Access rules are made as granular as possible to enforce the least privileges needed to perform the action in the request [i.6]. - -# --- 1 Scope - -Zero Trust Architecture (ZTA) is applicable to protect O-RAN architecture elements, interfaces, and data. This technical report studies the state of O-RAN's Zero Trust security posture with respect to the NIST publications [i.6] [i.7] and their seven tenets of zero trust. This report identifies new zero trust assets, threats, risks, and security controls in pursuit of a ZTA while considering those already existing in WG11 specifications. - -This technical report includes the following activities: - -- Applicability study of NIST seven tenets of zero trust to O-RAN Security Architecture -- Identification of Zero Trust assets -- Identification of ZTA threats using STRIDE -- ZTA risk assessment -- Determination of ZTA security controls -- Gap analysis between target ZTA security controls and existing security controls -- Proposal of new ZTA recommendations, requirements, and security controls - -This technical report makes the following considerations: - -- The technical report takes into consideration existing WG11 technical reports and specifications and may inform of the associated assets, threats, risks, and security controls. -- The O-RAN ALLIANCE is pursuing a zero-trust architecture (ZTA) for its specifications based upon NIST SP 800-207 [i.6]. - -# 2 References - -## 2.1 Normative references - -Normative references are not applicable in the present document. - -## 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.WG1.TS.OAD: "O-RAN Architecture Description". -- [i.2] O-RAN.WG11.TS.SRCS: "O-RAN Security Requirements and Controls Specifications". -- [i.3] O-RAN.WG11.TS.SecProtSpec: "O-RAN Security Protocols Specifications". -- [i.4] O-RAN.WG11.TR.Threat-Modeling: "O-RAN Security Threat Modeling and Risk Assessment". -- [i.5] O-RAN.WG11.TS.STS: "O-RAN Security Test Specification". -- [i.6] NIST Special Publication 800-207, "Zero Trust Architecture", August 2020, . -- [i.7] NIST Special Publication 800-207A, "A Zero Trust Architecture Model for Access Control in Cloud-Native Applications in Multi-Cloud Environments", September 2023 . -- [i.8] Enhanced Zero Trust and 5G, ATIS, July 2023, Enhanced Zero Trust and 5G | ATIS. -- [i.9] Zero Trust Maturity Model, v2.0, US DHS CISA, April 2023. -[https://www.cisa.gov/sites/default/files/2023-04/zero\\_trust\\_maturity\\_model\\_v2\\_508.pdf](https://www.cisa.gov/sites/default/files/2023-04/zero_trust_maturity_model_v2_508.pdf). -- [i.10] 3GPP TR 33.894: "3GPP Study on applicability of the zero trust security principles in mobile networks". -- [i.11] "Security guidance for 5g cloud infrastructures", -[https://www.cisa.gov/sites/default/files/2023-02/security\\_guidance\\_for\\_5g\\_cloud\\_infrastructures\\_part\\_i\\_508\\_compliant.pdf](https://www.cisa.gov/sites/default/files/2023-02/security_guidance_for_5g_cloud_infrastructures_part_i_508_compliant.pdf). -- [i.12] O-RAN.WG9.XPSAAS: "Xhaul Packet Switched Architectures and Solutions". -- [i.13] Embracing a Zero Trust Security Model, US National Security Agency, February 2021. -[https://media.defense.gov/2021/Feb/25/2002588479/-1/-1/0/CSI\\_EMBRACING\\_ZT\\_SECURITY\\_MODE\\_L\\_UOO115131-21.PDF](https://media.defense.gov/2021/Feb/25/2002588479/-1/-1/0/CSI_EMBRACING_ZT_SECURITY_MODE_L_UOO115131-21.PDF). - -- [i.14] DoD Zero Trust Reference Architecture, US Department of Defense, July 2022. -[https://dodcio.defense.gov/Portals/0/Documents/Library/\(U\)ZT\\_RA\\_v2.0\(U\)\\_Sep22.pdf](https://dodcio.defense.gov/Portals/0/Documents/Library/(U)ZT_RA_v2.0(U)_Sep22.pdf). -- [i.15] NSTAC Report to the President on Zero Trust and Trusted Identity Management, NSTAC, 2022. -- [i.16] IEEE Std 802.1X-2020: "IEEE Standard for Local and Metropolitan Area Networks--Port-Based Network Access Control", (Revision of IEEE Std 802.1X-2010 Incorporating IEEE Std 802.1Xb-2014 and IEEE Std 802.1Xck-2018), 28 Feb. 2020, doi: 10.1109/IEEESTD.2020.9018454. -- [i.17] 3GPP TS 33.501: "Security architecture and procedures for 5G System". -- [i.18] DoD Zero Trust Strategy, US Department of Defense, October 2022. -. -- [i.19] DoD Zero Trust Capability Execution Roadmap (COA 1), DOD CIO, ZT PfMO, January 2023. -. -- [i.20] NIST Special Publication 800-95 "Guide to Secure Web Services", August 2007, -. -- [i.21] O-RAN.WG2.TS.Non-RT-RIC-ARCH: "Non-RT RIC: Architecture". -- [i.22] "Advancing Zero Trust Maturity Throughout the Visibility and Analytics Pillar", US National Security Agency, May 2024. . -- [i.23] O-RAN.WG3.RICARCH: "Near-RT RIC Architecture". -- [i.24] 3GPP TS 33.511 "Security Assurance Specification (SCAS) for the next generation Node B (gNodeB) network product class". -- [i.25] 3GPP TS 33.117 "Technical Specification Group Services and System Aspects; Catalogue of general security assurance requirements". -- [i.26] O-RAN.WG4.TS.MP: "O-RAN Management Plane Specification". -- [i.27] O-RAN.WG11.TR.Fronthaul-CUSPlane-Security: "O-RAN Study on Security for Fronthaul CUS-Plane". -- [i.28] O-RAN.WG9.XTRP-MGT: "O-RAN Management interfaces for Transport Network Elements". -- [i.29] O-RAN.WG9.XTRP-SYN: "O-RAN Synchronization Architecture and Solution Specification". -- [i.30] "Advancing Zero Trust Maturity Throughout the Network and Environment Pillar", -. -- [i.31] O-RAN.WG11.Security-Log-Management-TR: " Study on Security Log Management". -- [i.32] 3GPP TS 38.323: "NR: Packet Data Convergence Protocol (PDCP)". -- [i.33] O-RAN.WG10.TS.OAM-Architecture: "O-RAN Operations and Maintenance Architecture". -- [i.34] O-RAN.WG2.A1GAP: "A1 interface: General Aspects and Principles". -- [i.35] O-RAN.WG2.TS.R1GAP: "R1 interface: General Aspects and Principles". -- [i.36] O-RAN.WG1.TR.O-RES.0-R004-v01.00: "O-RAN Resiliency". - -# 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the following terms apply: - -**A1 interface:** interface between Non-RT RIC and Near-RT RIC [i.34] - -**A1 Enrichment information (EI):** enrichment information that is collected or derived at SMO/Non-RT RIC either from non-network data sources or from network functions themselves and provided over the A1 interface to be utilized by Near-RT RIC. [i.34] - -**A1 policy:** declarative policy 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. [i.34] - -**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. [i.1] - -**Microsegmentation:** Microsegmentation is a security practice of partitioning networks and assets into small, isolated segments based on various attributes such as communication requirements and risk profiles. Fine grained access control mechanisms are used to minimize the permissible communication paths both within and between disjoint segments. - -NOTE: Microsegmentation is commonly used in zero trust architecture to minimize the threat of attacks from disjoint segments. - -**Near-RT RIC:** O-RAN 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) [i.2] - -**Near-RT RIC APIs:** A set of service-based interfaces that can be produced and consumed by the Near-RT RIC Platform and xApps. [i.1] - -**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. [i.1] - -**Non-Person Entity (NPE):** An entity with a digital identity that acts in cyberspace, but is not a human actor. This can include organizations, hardware devices, software applications, and information artifacts as defined in [i.6]. - -**Non-RT RIC (O-RAN Non-Real-Time RAN Intelligent Controller):** A logical function within SMO 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. [i.21] - -**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. [i.1] - -**O-Cloud:** Cloud platform that provides O-RAN standardized interfaces, hosting O-RAN defined software components. [i.1] - -**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. - -**O1:** Interface used by the SMO framework for operation and management of O-RAN NFs as specified in [i.1] [i.33] - -**O2:** Interface between SMO and the O-Cloud to provide cloud resources management and workload management for supporting O-RAN cloudified network functions. - -**O2dms:** Interface between the SMO and the O-Cloud that is responsible for the deployment management services of the NF Deployment. - -**O2ims:** Interface between the SMO and the O-Cloud that is responsible for the infrastructure management services of the NF Deployment. - -**Open Fronthaul:** The interface between O-DU and O-RU logical nodes, including the CUS (Control User Synchronization) Plane and M (Management) Plane, as defined in O-RAN Architecture Description [i.1]. - -**Open Fronthaul stack data:** Data managed and stored at each of the layers of the Open Fronthaul protocol stack. - -**R1:** A service-based interface between rApps and Non-RT RIC Framework via which R1 Services can be produced and consumed [i.35]. - -**R1 Services:** A collection of services including, but not limited to, service registration and discovery services, authentication and authorization services, AI/ML workflow services, and A1, O1 and O2 related services. [i.35] - -**rApps:** Non-RT RIC application: an application designed to consume and/or produce R1 services. - -**Security Log:** A log that contains audit records and security-related system events. [i.2] - -**Transversal Functions:** Transversal functions are those that should be managed at a system-wide level rather than handled individually for each asset. - -**xApps:** Near-RT RIC application. - -**Y1:** An interface between Near-RT RIC and Y1 consumers, as defined in O-RAN Architecture Description [i.1], clause 5.4.18. The interface enables RAN analytics information exposure from Near-RT RIC. - -For definition of the terms Service Management and Orchestration (SMO), SMO External Interface, SMO External Consumer, SMO Function (SMOF), and SMO Service (SMOS) see the O-RAN Architecture Description (OAD) document [i.1], clause 5.3.1. Other terms defined in O-RAN Architecture Description (OAD) [i.1] also apply. - -## 3.2 Symbols - -Void - -## 3.3 Abbreviations - -For the purposes of the present document, the following abbreviations apply: - -| | | -|-------|------------------------------------------| -| AI/ML | Artificial Intelligence/Machine Learning | -| CM | RAN NF Configuration Management | - -| | | -|----------|------------------------------------------------| -| DME | Data Management and Exposure | -| DMS | O-Cloud Deployment Management Services | -| FHGW | Fronthaul Gateway | -| FHM | Fronthaul Multiplexor | -| FM | Fault Management | -| FOCOM | Federated O-Cloud Orchestration and Management | -| GM | Grand Master | -| IMS | O-Cloud Infrastructure Management Services | -| JEA | Just-Enough-Administration | -| JIT | Just-In-Time | -| NFO | Network Function Orchestrator | -| NPE | Non-Person Entity | -| O-CU-CP | O-RAN Centralized Unit – Control Plane | -| O-CU- UP | O-RAN Centralized Unit – User Plane | -| O-DU | O-RAN Distributed Unit | -| O-RU | O-RAN Radio Unit | -| PM | RAN NF Performance Management | -| RAN | Radio Access Network | -| RIC | O-RAN RAN Intelligent Controller | -| SME | Service Management and Exposure | -| SMO | Service Management and Orchestration | -| SMOS | SMO Service | -| TE&IM | Topology Exposure and Inventory Management | -| TNE | Transport Node Equipment | -| UE | User Equipment | -| UEBA | User and Entity Behaviour Analytics | -| ZT | Zero Trust | -| ZTA | Zero Trust Architecture | -| ZTMM | Zero Trust Maturity Model | - -# 4 NIST Zero Trust Tenet Applicability - -## 4.1 NIST ZT Tenets overview - -Numerous interpretations and discussions of ZT emphasize the imperative of eliminating wide-area perimeter defences. They define ZT as a transformative shift from a location-centric paradigm to an identity, context, and data-centric approach with fine-grained security controls between users, systems, applications, data, and assets that change over time. NIST Special Publication 800-207 [i.6] defines ZT through a set of basic tenets that should be involved in zero trust architectures. While acknowledging the ideal nature of these tenets, NIST recognizes that these tenets practical application may differ based on specific strategic considerations. The basic tenets, essential for a comprehensive Zero Trust Architecture, are detailed below: - -1. **All data sources and computing services are considered resources.** This tenet emphasizes that all classes of devices, ranging from large devices to sensors, and all types of computing services, should be considered as resources that need protection within the Zero Trust Architecture (ZTA), whether they are personally owned or enterprise-owned resources. -2. **All Communication is secured regardless of network location.** This means that trust should not be automatically granted based on the device being on the enterprise network infrastructure. Instead, all communication should be conducted in the most secure manner available, protecting confidentiality and integrity, and providing source authentication. -3. **Access to individual enterprise resources is granted on a per-session basis.** Trust in the requester is evaluated before access is granted. Moreover, access should be granted with the least privileges needed to complete the task. -4. **Access to resources is determined by dynamic policy—including the observable state of client identity, application/service, and the requesting asset—and may include other behavioural and environmental attributes.** These rules and attributes are based on the needs of the business process and an acceptable level of risk. Resource access and action permission policies can vary based on the sensitivity of the resource/data. Least privilege principles are applied to restrict both visibility and accessibility. -5. **The enterprise monitors and measures the integrity and security posture of all owned and associated assets.** No asset is inherently trusted. The security posture of the asset needs to be evaluated and considered when evaluating a resource request. An enterprise implementing a ZTA should establish a continuous diagnostics and mitigation (CDM) or a similar system to monitor the state of devices and applications and should apply patches/fixes as needed. -6. **All resource authentication and authorization are dynamic and strictly enforced before access is allowed.** This is a constant cycle of obtaining access, scanning and assessing threats, adapting, and continually reevaluating trust in ongoing communication as defined and enforced by policy, striving to achieve a balance of security, availability, usability, and cost-efficiency. -7. **The enterprise collects as much information as possible about the current state of assets, network infrastructure and communications and uses it to improve its security posture.** This data should be utilized to improve policy creation and enforcement, and to support contextual access control decisions. - -## 4.2 NIST ZT Tenets applicability study - -### 4.2.1 ZT Tenet 1 Applicability Study - -#### 4.2.1.1 Introduction - -##### **ZT tenet 1: All data sources and computing services are considered resources.** - -This tenet underscores the importance of safeguarding all forms of data sources and computing services within the framework of ZTA. Also, an enterprise may decide to classify personally owned devices as resources if they can access enterprise-owned resources. - -#### 4.2.1.2 Applicability Study - -This tenet addresses the dynamic shifts in enterprise network trends, encompassing various internal networks, remote offices with distinct local infrastructures, remote individuals, and cloud-based assets existing beyond enterprise-owned network boundaries—common scenarios encountered in Open RAN deployments. The increasing complexity surpasses traditional perimeter-based network security methods, given the absence of a single, easily identifiable enterprise perimeter. - -The ZTA approach primarily concentrates on safeguarding data and services but should extend its coverage to include all enterprise assets (devices, infrastructure components, applications, virtual and cloud components) and subjects (end users, applications, and other non-human entities seeking information from resources) [i.6]. Consequently, ZT security models operate on the assumption that an attacker is present in the environment, and no enterprise-owned environment is inherently more trustworthy than a non-enterprise-owned one. Addressing this tenet becomes imperative for establishing robust security measures within such contexts. - -In the context of a ZT-based O-RAN architecture adhering to ZT tenet 1, each data source and computing service in the O-RAN system should be considered a resource. As depicted in [i.8], this tenet necessitates the system owner to identify resources within the 5GS, enabling the construction of the ZTA around these resources. In the 5G landscape, network assets, including UEs, RAN, transport, Core, applications, and services, are acknowledged as assets and data sources with distinct system owners. Computer resources running NFs and applications are also recognized as assets. - -#### 4.2.1.3 Conclusion - -The significance of Zero Trust Architecture's first tenet is notably pronounced in the context of O-RAN deployments. By emphasizing the safeguarding of data sources and computing services, the tenet addresses the unique challenges posed by diverse network assets in O-RAN architectures. This approach ensures that each component, whether locally owned or part of a broader ecosystem, is considered a valuable resource within the zero trust framework, thereby enhancing security measures tailored to the specific demands of O-RAN environments. - -### 4.2.2 ZT Tenet 2 Applicability Study - -#### 4.2.2.1 Introduction - -##### **ZT Tenet 2: All Communication is secured regardless of network location.** - -This tenet highlights the importance of not automatically granting trust solely based on a device's presence within the enterprise network infrastructure. Access requests from assets within enterprise-owned network infrastructure, such as those inside a legacy network perimeter, must adhere to the same security requirements as requests from non-enterprise-owned networks. All communication should prioritize the most secure methods available, ensuring confidentiality, integrity, and source authentication. - -#### 4.2.2.2 Applicability study - -The relevance of this tenet is particularly evident in the context of Radio Access Network (RAN) considerations for several compelling reasons. O-RAN introduces elements like disaggregation, open interfaces, and diverse deployment models, expanding the potential attack surface. Components such as the O-RAN Service Management and Orchestration (SMO), Radio Intelligent Controller (RICs), and RIC Apps within the Open RAN framework are susceptible to exploitation for confidentiality, integrity, and availability attacks from both external and internal threats [i.8]. Therefore, addressing tenet 2 is crucial within the Open RAN architecture to effectively mitigate these security vulnerabilities. - -In the context of a ZT-based O-RAN architecture adhering to ZT tenet 2, all network communications should prioritize confidentiality, integrity, and source authentication. In 5G, encryption, integrity protection, authentication schemes, and security protocols are employed to secure communication among participating entities in the network. - -#### 4.2.2.3 Conclusion - -In summary, this tenet holds significant importance for O-RAN by stressing the necessity of robust security standards across all communications, regardless of their network location. With O-RAN's distinctive features like disaggregation, open interfaces, and third parties' applications, tenet 2 becomes essential for preventing security issues. By prioritizing confidentiality, integrity, and source authentication in network communications, Tenet 2 stands as a fundamental element in establishing a secure O-RAN framework, offering protection against potential threats both internal and external. - -### 4.2.3 ZT Tenet 3 Applicability Study - -#### 4.2.3.1 Introduction - -##### **ZT tenet 3: Access to individual enterprise resources is granted on a per-session basis.** - -According to ZT tenet 3 [i.6], a session refers to an instance of communication established between a subject and a resource. Granting access on a per-session basis in accordance with this tenet means the following: - -1. Authentication and authorization must be performed before access is granted. -2. Successful authentication and authorization of a subject to one resource does not automatically grant access to other resources. -3. Within a session, access to a resource is granted based on the principle of least privilege. - -**NOTE:** According to ZT tenet 6 [i.6], as outlined in clause 4.2.6 of the present document, continuous monitoring with potential reauthentication and reauthorization is conducted throughout the session. Reauthentication and reauthorization throughout the session is defined and enforced by policies (e.g., time-based, new resource requests, resource modifications, detection of anomalous subject activity) that aim to balance security, availability, usability, and cost-efficiency. - -#### 4.2.3.2 Applicability Study - -For a zero trust based O-RAN architecture, each access request to O-RAN resources must adapt the principle of ZT tenet 3 with strong authentication, and fine-grained access control at every point of access. - -In the O-RAN architecture there are multiple Points Of Access (POA) that have been considered for the applicability of ZT tenet 3 study. - -- [1] **User Access to SMO:** User Access to internet facing SMO services and applications. - -- [2] **User Access to the O-Cloud Orchestration layer:** User Access to VMs and containers via the O-Cloud Management Plane (EXAMPLE: Kubernetes API server). -- [3] **User Access to O-Cloud Host OS Access:** User Access via SSH to Host OS. -- [4] **User Access to O-Cloud Hardware Infrastructure:** User authentication and authorization for accessing the network storage, and compute resources. -- [5] **Network Function to Network Function Access:** NF to NF communication over O-RAN defined interfaces. -- [6] **User access to TNE:** User Access to Transport Network Elements, such as switches, routers, or other network devices. -- [7] **Device access to the network (Open FH):** Device access to open fronthaul resources like O-DU, O-RU FHM, Grandmasters etc. -- [8] **User Reauthentication:** Ensuring that a user accessing a protected resource is the same user who initially authenticated at the start of the session. - -O-RAN ALLIANCE WG11 follows the principle of ZT tenet 3 while defining security controls and measures in the "O-RAN Security Requirements and Controls Specifications" [i.2]. WG11 has specified security requirements and security controls for the following points of access - [2], [5] and [7]. - -- The current access control security mechanism specified are mTLS, IPsec, OAuth2.0, IEEE 802.1X, and NACM that ensures granular access control for O-RAN fronthaul and non-fronthaul interfaces. -- Communication between Network Functions over O-RAN defined interfaces has been secured based on the principles of zero trust. -- Security controls and measures have been defined for the access control for certain O-RAN components like access of O-Cloud using SMO via the **O2** interface and access of NFs using SMO via the **O1** interface. - -Access control for the following points of access is not specified currently- user access to internet facing SMO services, user access to O-Cloud orchestration layer, O-Cloud Host OS, User Access of NFs from Host/O-Cloud node of SMO or other hosts. Access control mechanisms to these need to be evaluated for defining specific security recommendations that align to the ZT tenet 3 principle. This will ensure that the identity of the subject that is requesting access to a specific O-RAN resource identity is always verified, the subject possesses the necessary rights and meets the environment specific requirements to access the requested resource. - -#### 4.2.3.3 Conclusion - -Human users, services, and applications request access to specific O-RAN network components. It is essential to authenticate every subject based on its unique identity and use RBAC rules to authorize and enforce least privilege access to the requested resources. By implementing Access Control Policies based on the Principle of Least Privilege (POLP), operators can effectively prevent attackers from moving laterally within the network. - -WG11 should expand on the ZT tenet 3 principle of session-based access control to encompass the user access scenarios identified in [1],[3],[4],[6]. This will allow to define additional security controls and measures for granular categorization of access policies considering Just-in-time access, Least privileges and Just enough access for each subject identity and their rights to access the destination O-RAN assets. - -### 4.2.4 ZT Tenet 4 Applicability Study - -#### 4.2.4.1 Introduction - -**ZT tenet 4: Access to resources is determined by dynamic policy—including the observable state of client identity, application/service, and the requesting asset—and may include other behavioural and environmental attributes.** - -According to ZT tenet 4 as stated in NIST SP 800-207[i.6], access requests are evaluated not solely based on the outcome of subject authentication but also take into consideration the subject's previous request history, environmental factors and security posture of both the requesting subject and resource and are governed by dynamic policies. - -#### 4.2.4.2 Applicability Study - -In the O-RAN architecture, human users (subjects) can generate remote access requests to O-RAN architecture elements such as SMO, O-Cloud or O-CU/O-DU/O-RU: - -- a) from geo-locations that may or may not be under the direct control of the network operator, -- b) using devices that are not managed by the operator, -- c) over public or hybrid (public/private) networks. - -It is therefore essential to control access to the requested resources not just based on the identity of the user, but also based on additional attributes of the end-user such as his/her location, end-user device hygiene, past history or behavioural information (risk-profile) etc. These attributes are captured as inputs to dynamic access policies that influence authentication and authorization of the user. - -For a zero-trust based O-RAN architecture, every access to O-RAN resources should adapt the principle of ZT tenet 4 that defines and enforces access policies which are continuously updated based on inputs from continual monitoring (ZT tenet 5) of the network, - -O-RAN architecture currently considers OAuth based authorization decision for several of its interfaces. These are based on static policies that define the scope of access granted to the requesting subject. OAuth does not define policies that take into account the location or security posture of the requesting client. Similarly, NACM does not define dynamic policies. - -Additionally, WG11 has a requirement for DDoS protection mitigation measures for the O2 interface in SMO. There are however no requirements to use these DDoS mitigation measures to continuously update the access requests decision process or dynamic block listing. - -WG11 proposes to further study and define ZT tenet 4 based access controls policies for accessing the O-RAN and Non-ORAN assets. - -- Define attributes for user, services, and devices that need to be continuously monitored -- Define access control policies that are dynamically updated based on inputs from continuous monitoring of the above attributes -- Study the Policy decision and enforcement points for defining and enforcing ZT tenet 4 access policies in the O-RAN architecture, as described in clause 3 of NIST SP 800-207 [i.6]. - -These attribute-based access control policies would effectively manage, monitor, limit, and revoke access to Device, Infrastructure, Application and Services [DIAS]. - -#### 4.2.4.3 Conclusion - -As described in clause 4.2.4.2, human users, services, and applications request access to O-RAN network components from potentially untrusted locations, using unmanaged devices and over public or hybrid networks. It is therefore essential to include these parameters while authenticating and authorizing the subjects. Dynamic policy-based infrastructure is recommended that considers these attributes for policy generation and enforcement. - -This would entail defining the user, network and device attributes for defining access control policies that would apply to all interfaces in the O-RAN network, user access to all O-RAN components as described in the ZT tenet 3 study. - -### 4.2.5 ZT Tenet 5 Applicability Study - -#### 4.2.5.1 Introduction - -**ZT tenet 5: The enterprise monitors and measures the integrity and security posture of all owned and associated assets.** - -NIST 800-207 [i.6] defines Tenet 5 "The enterprise monitors and measures the integrity and security posture of all owned and associated assets". Further description in NIST SP 800-207 states, this tenet majorly covers operational security and evaluation of the asset's security posture during evaluation of resource request. - -#### 4.2.5.2 Applicability Study - -ZT tenet 5 allows us to design continuous diagnostics of security events, logs etc. and evaluation of access requests to O-RAN and Non-O-RAN Assets based on security posture. O-RAN WG11 Security Log Management work item relates to the principle of zero trust architecture, however, gap analysis should be conducted to ensure ZT tenet 5 compliancy. The gap analysis would ensure the coverage of all the O-RAN assets that is being added as a part of the ZTA work item. The study would also ensure that the collection of data is sufficient for ZT tenet 7 to utilize it to improve the security posture. - -As part of ZT tenet 5, WG11 would cover continuous monitoring and alerting of User Authorizations, Data access, Resource Authorization (Application/workload), User/Device Interactions. It is also essential to study the integration of threat Intelligence as a part of the ZT tenet 5 study. This would entail a continuous security monitoring system that measures integrity, and security posture of all assets in the areas of access management, behavioural analytics, configuration management, software integrity checks, vulnerability scans, security anomaly detection, etc. - -For a zero trust O-RAN Architecture, ZT tenet 5 plays a critical role to detect and alert of Adversarial Lateral movements. - -#### 4.2.5.3 Conclusion - -WG11 should expand on the ZT tenet 5 principles that monitors the O-RAN assets to address any gaps of security monitoring and perform "**Continuous and dynamic security monitoring**" to maintain them in their most secure states possible for comprehensive visibility. WG11 intends to come up with recommendation, industry standard security best practices to attain the advanced zero trust maturity model. - -### 4.2.6 ZT Tenet 6 Applicability Study - -#### 4.2.6.1 Introduction - -**ZT tenet 6: All resource authentication and authorization are dynamic and strictly enforced before access is allowed.** - -According to ZT tenet 6 as stated in NIST SP 800-207 [i.6], user access to resources is continuously re-evaluated. Any changes in the security posture of either the subject or the resource trigger reauthentication and reauthorization of the access request. This tenet expands on ZT tenet 4, which pertains to access requests through dynamic policies and ZT tenet 5 of continual monitoring to re-evaluating user transactional flow and enforcing policies based on abnormal behaviour, time-based factors, and environmental considerations. - -#### 4.2.6.2 Applicability Study - -In the O-RAN architecture, there are multiple points of access that a user may request access to. The user undergoes authentication and authorization before granting access to the resources. Although the user was authorized for accessing the resource, the user behaviour might change on account of various factors, such as: - -- a. Access over a different network -- b. Unknown applications on the device trying to access the resource. -- c. Hidden malware on the device trying to access the resource. -- d. Unusual/abnormal access patterns (e.g. location, time change compared to known user patterns) - -It is essential to monitor the security posture of the subject and network resources to evaluate the trust at any given point of time and trigger reauthentication and reauthorization if needed to do so. Failure to do so may result in a compromised user account or an internal threat actor that remains undetected, and may trigger reconnaissance, continued access to the protected resource, leading to a lateral movement in the network, thus causing large outages, data theft, or sabotage of the network. - -As a result, the O-RAN architecture should adapt the principle of ZT tenet 6 where every access request is continuously reevaluated to determine that the trust can be maintained and established. Continuous evaluation of all values related to the authentication, inspection, and access determinations based on the subject and destination resource should be continuously assessed. - -- Utilizing ongoing security monitoring (ZT tenet 5) to identify change in the security posture of subject and resource -of user access for O-Cloud Platform, mTLS, IPsec, IEEE 802.1X for authentication, OAuth2.0 and NACM based authorization decision for different O-RAN interfaces. However, there are no requirements and controls for periodic evaluation of authentication and authorization based on continuous security monitoring related information (e.g. threat assessments, security posture etc.) as well as dynamic policies that trigger-reauthentication and reauthorization of subjects. - -Therefore, WG11 proposes to further study and define ZT tenet 6 based access policies for accessing the O-RAN and Non-ORAN (defined) assets of an O-RAN deployment. - -- Gap Analysis of the current authentication and authorization security mechanisms for each O-RAN network point of access. -- Define Dynamic Authentication and Authorization policies based on the continuous security monitoring related data (ZT tenet 5), user activity patterns, device hygiene, security posture of the user and the requested access resource. -- Establish Automated Identity Lifecycle Management policies that allow blacklisting, considering the ZT tenet 5 threat and security posture assessment of any user and devices. -- Identity and context-based logical access boundary for devices, infrastructure, application and data. - -#### 4.2.6.3 Conclusion - -WG11 has addressed DoS prevention and preventing content-based attacks through an interface as well as logging requirements on failed/malicious access request attempts related to ZT tenet 5. However, the dynamic assessment of authentication and authorization processes to continuously reassess trust during ongoing communications, as outlined in ZT tenet 6 is applicable to O-RAN and requires further study. - -This entails studying the dynamic authentication and authorization mechanisms based on continuous identity and attributes verification of an ongoing communication. The dynamic access control policies will consider the security monitoring data (ZT tenet 5) and deployment related aspects to dynamically enforce reauthentication and reauthorization of User access to O-RAN assets and revoke access if needed. This tenet allows an operator to define and control the authentication and authorization decision points for the entire O-RAN deployment, that considers continual authentication and conditional authorization to prevent any lateral movement in the O-RAN network. - -### 4.2.7 ZT Tenet 7 Applicability Study - -#### 4.2.7.1 Introduction - -**ZT tenet 7: The enterprise collects as much information as possible about the current state of assets, network infrastructure and communications and uses it to improve its security posture.** - -Further description in NIST SP 800-207 [i.6] states, this tenet covers Security posture, network traffic, and access request data analysis informs policy creation and enforcement for a robust zero-trust architecture. - -#### 4.2.7.2 Applicability Study - -In the O-RAN architecture, security monitoring and security log and event management is crucial for maintaining a secure and robust security posture of all O-RAN components. Log analysis, including anomalous user behaviour, unusual network traffic patterns, and unauthorized access attempts, can facilitate the detection and mitigation of lateral movement as observed in [i.11]. - -With the **ZT tenet 5 we have a Proactive approach**. It focuses on setting up logging of security events to reduce potential damage from the beginning. With the **ZT tenet 7 we have a Reactive approach**. It involves constantly monitoring for suspicious activity after access is granted and it focuses on detecting and responding to unauthorized or unusual activity. - -WG11 has specified Security Log Management requirements and controls but has not defined procedures to leverage data collection to improve asset security posture by identifying vulnerabilities, monitoring access patterns, and access request decisions based on contextual insights and behavioural analytics. - -It is essential to study the logging and monitoring infrastructure to understand the type of data collected, use data analytics mechanisms to understand the security posture of O-RAN and Non-O-RAN assets. This will be an enabler to build an infrastructure to enforce dynamic security policies thus improving security posture for O-RAN assets and Non-O-RAN assets. Based on contextual insights and behavioural analytics policy enforcement can be in the area of user access to O-RAN and Non O-RAN component, service to service communication, mitigation of adversarial lateral movements, mitigation of DDOS attacks against any interface, isolation of any NF due to abnormal behaviour etc. - -For a zero trust O-RAN Architecture, ZT tenet 7 plays a critical role. - -#### 4.2.7.3 Conclusion - -WG11 should expand on the ZT tenet 7 principles that **allow us to collect as much information as possible about the current state of assets, network infrastructure and communications and uses it to improve its security posture**. This enables an operator to detect anomalous behaviour, identify potential security threats, and take timely mitigation actions as referenced in [i.10] tenet 7 evaluation. WG11 intends to come up with recommendation, industry standard security best practices to attain the advanced zero trust maturity model. - -## 4.3 NIST ZT Tenets applicability summary - -All seven ZT tenets are applicable to O-RAN, with varying levels of specification in O-RAN ALLIANCE specifications. Full realization for some tenets may require integration with systems outside the scope of O-RAN, which will be left to the operator. The role of the O-RAN ALLIANCE in these cases should be to produce security requirements, controls and specifications that support these tenets. Error: Reference source not foundprovides a summary with justification of the NIST ZT tenet applicability study for O-RAN. - -**Table 4.3-1: NIST ZT Tenet Applicability Summary** - -| Tenet | Applicable | Justification | -|---------|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Tenet 1 | | Recognizing all data sources and computing services as resources within O-RAN architecture is vital for holistic ZT security. | -| Tenet 2 | | This tenet holds significant importance for O-RAN by stressing the necessity of robust security standards across all communications, regardless of their network location. With O-RAN's distinctive features like disaggregation, open interfaces, and third parties' applications, tenet 2 becomes essential for preventing security issues. | -| Tenet 3 | | Users, services, and applications within the O-RAN system seek access to designated network components. Authenticating each entity based on its distinct identity and adhering to the principle of least privilege are crucial. Through the implementation of Access Control Policies aligned with the Principle of Least Privilege, operators can effectively prevent attackers from moving laterally within the network. | -| Tenet 4 | | O-RAN should specify the required infrastructure and capabilities for capturing the observable state of the requesting client's (subject's) identity and the requesting device, along with any additional behavioural and environmental attributes relevant to this tenet, to facilitate creation and enforcement of dynamic policies by operators. | -| Tenet 5 | | O-RAN should establish measures to support security monitoring, integrity assessment, and evaluation of the security posture for all O-RAN assets. These measures may include employing behavioural analytics, managing configurations, conducting software integrity checks, performing vulnerability scans, and detecting security anomalies, among other methods. Outputs from these measures are processed by the operators to decide on access requests. | -| Tenet 6 | | It is essential to monitor the security posture of the subject and network resources to evaluate the trust at any given point of time and trigger reauthentication and reauthorization if needed to do so. Failure to do so may result in a compromised user account or an internal threat actor remaining undetected, and may trigger reconnaissance, continued access to the protected resource, or lead to a lateral movement in the network, thus causing large outages, data theft, or sabotage of the network. As a result, the O-RAN architecture should adapt the principle of ZT tenet 6 where every access request is continuously reevaluated to determine that the trust can be maintained and established. | -| Tenet 7 | | To improve the security posture of the system, O-RAN should develop the capability to collect as much information as possible about the current state of assets, network infrastructure and communications. This will enable operators to utilize this information to improve policy creation and enforcement. | - -# 5 ZTA Assets - -## 5.1 Asset Categories - -Traditional perimeter-based network defenses with multiple layers of disjointed security technologies have proven themselves unable to meet cybersecurity needs in the current threat environment [i.13]. Organizations require a more effective approach to securing their infrastructure and providing unified yet granular access control to data, services, applications, and infrastructure [i.13]. Zero Trust focuses on protecting critical data and resources rather than solely relying on traditional network or perimeter security. ZT implements continuous multi-factor authentication, micro-segmentation, encryption, endpoint security, automation, analytics, and robust auditing across different resources [i.14]. Zero Trust Architecture treats each asset as a micro-perimeter to protect against both internal and external threats [i.8]. To mitigate cyber risk effectively, ZT planners should define the organization's protect surface, which the NSTAC report defines as the area protected by ZT policies [i.15]. - -In the following, we describe five categories of assets that need to be considered for ZTA analysis. It is important to note that some categories include two types of assets: O-RAN assets and assets that are not specified by O-RAN ALLIANCE. While the later are outside the scope of O-RAN specification, we include them to highlight the importance of considering them for analysis for a holistic ZTA for O-RAN system. - -1. **Data:** O-RAN data encompasses both structured and unstructured files and fragments that are currently or have previously been present in O-RAN systems, devices, networks, applications, databases, infrastructure, and backups (including both on-premises and virtual environments), along with their corresponding metadata. -2. **Interfaces:** - - a. O-RAN Interfaces: Interfaces defined and maintained by O-RAN, as specified in [i.1]. - - b. Interfaces not specified by O-RAN: This includes interfaces defined and maintained by 3GPP, but seen as part of the O-RAN architecture [i.1]: -3. **Architecture Elements:** This asset category comprises the architecture elements as defined in [i.1]. -4. **Infrastructure:** The infrastructure category within O-RAN assets encompasses a wide array of components, including both physical and virtual elements, as well as various platforms. It includes: - - a. O-RAN infrastructure assets: - - **Hardware:** This comprises servers, data centers, and other networking equipment that form the physical foundation of the O-RAN infrastructure. This includes FHGW (Fronthaul Gateway), FHM (Fronthaul Manager), and TNE (Transport Network Element). - - **Operating System and Firmware:** These are essential software components that provide the foundational functionality for the hardware components, enabling them to operate efficiently and effectively. This includes OS kernel, Bootloader, O-Cloud DMS, and O-Cloud IMS. - - **Virtualization Layer:** This refers to the software layer that enables the virtualization of hardware resources, allowing for the creation and management of virtual instances of servers, networking equipment, and other infrastructure components. This layer includes components like virtual machines (VMs), containers, and hypervisors. - -- b. Infrastructure assets not specified by O-RAN: These components are essential for managing and facilitating communication between various O-RAN network elements. This includes GM, which is a component within the O-RAN architecture but not defined by O-RAN ALLIANCE. -5. **Services:** A service is a software component participating in a service-oriented architecture that provides functionality or participates in realizing one or more capabilities [i.20]. -- a. O-RAN services: This includes O-RAN services that operate in both on-premises and cloud environments, such as AI/ML workflow services [i.21], O-Cloud O2ims and O2dms services. - - b. Services not specified by O-RAN: It encompasses third-party services providing various functionalities for O-RAN applications, including security services like PKI, IAM, and SIEM. - -## 5.2 Defined Assets - -The high-level scope of the assets in scope for the ZTA analysis is outlined in Table 5.2-1. - -**Table 5.2-2: High Level ZTA Assets for O-RAN** - -| Scope | Data | Interfaces | Architecture Elements | Infrastructure | Services | -|-----------------------------------------------|-----------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|------------------------------------| -| O-RAN Assets | Keys, Credentials
RAN Analytics
UE-Id
UE-Location
AI/ML training data
Configuration data
Logs | A1, E2, O1, O2, R1, Y1

Open Fronthaul C-Plane, S-Plane, U-Plane, M-Plane

External Interfaces | SMO (including Non-RT RIC and rApps)

Near-RT RIC (including xApps)

O-CU-CP

O-CU-UP

O-DU

O-RU

O-eNB

O-Cloud* | O-Cloud HW, OS, and virtualization infrastructure

Hardware and OS of O-RAN PNFs

FHGW, FHM, TNE | AI/ML Services | -| Assets not specified by O-RAN ALLIANCE | | F1-c, F1-u, E1, NG-c, NG-u, X2-c, X2-u, Xn-c, Xn-u, Uu interfaces [i.1] | | GM | Security Services (PKI, IAM, SIEM) | - -NOTE: In O-RAN, O-Cloud is considered an architecture element; however for the purposes of the ZTA security analysis, it is considered as infrastructure. - -The detailed list of assets in scope for the ZTA analysis is in clause 6.3 Critical Assets of [i.4] which lists the O-RAN data, interfaces and components that were used to perform security threat modelling and risk assessment and have formed the basis of the development of security requirements and controls within the various security work items. - -The following clauses identify new assets in the decoupled SMO, O-Cloud and the Open Fronthaul that have not yet been incorporated into clause 6.3 of [i.4]. - -## 5.3 New Assets - -### 5.3.1 New Assets in the SMO - -**Table New Assets in the SMO-3: SMO Assets** - -| Asset ID | Asset Description | Component | Interface | When | | Protection Level | | | | | -|------------------------------------------------|---------------------------------------------------------------------|-----------|-----------|---------|------------|------------------|-----------|--------------|--------|--------------| -| | | | | At rest | In transit | Confidentiality | Integrity | Availability | Replay | Authenticity | -| Components (logical, virtual, physical) | | | | | | | | | | | -| ASSET-C-X | SMO Service: Service Management and Exposure (SME) | | | X | X | X | X | X | X | X | -| ASSET-C-X | SMO Service: Data Management and Exposure (DME) | | | X | X | X | X | X | X | X | -| ASSET-C-X | SMO Service: Topology Exposure and Inventory Management (TE&IM) | | | X | | X | X | X | | X | -| ASSET-C-X | SMO Service: rApp Management | | | X | | X | X | X | | X | -| ASSET-C-X | SMO Service: Network Function Orchestrator (NFO) | | | X | | X | X | X | | X | -| ASSET-C-X | SMO Service: Federated O-Cloud Orchestration and Management (FOCOM) | | | X | | X | X | X | | X | -| ASSET-C-X | SMO Service: RAN NF Fault Management (FM) | | | X | | X | X | X | | X | -| ASSET-C-X | SMO Service: RAN NF Configuration Management (CM) | | | X | | X | X | X | | X | -| ASSET-C-X | SMO Service: RAN NF Performance Management | | | X | | X | X | X | | X | - -| | | | | | | | | | | | -|------------------|---------------------------------------------------|--|--|---|---|---|---|---|---|---| -| | (PM) | | | | | | | | | | -| ASSET-C-X | SMO Service: A1 Enrichment Information Management | | | x | | x | x | x | | x | -| ASSET-C-X | SMO Service: A1 Policy Management | | | x | | x | x | x | | x | -| ASSET-C-X | SMO Service: SW Package Onboarding | | | x | | x | x | x | | x | -| ASSET-C-X | SMO Service: Service Orchestration | | | x | | x | x | x | | x | -| ASSET-C-X | SMO Service: Service Assurance | | | x | | x | x | x | | x | -| ASSET-C-X | SMO Service: RAN Analytics | | | x | | x | x | x | | x | -| ASSET-C-X | SMO Service: AI/ML Workflow | | | x | | x | x | x | | x | -| ASSET-C-X | SMOS Communications | | | | x | x | x | x | x | x | - -### 5.3.2 O-Cloud Assets - -The table below lists assets associated with O-Cloud, incorporating existing assets from the Threat Model [i.4] and expanding them with new assets based on the ZTA approach. - -**Table O-Cloud Assets-4: O-Cloud Assets** - -| Asset type | Asset ID | Asset Title | Asset description | Security properties | | | -|-----------------|-----------------------------------------------------------------------------------------------------------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|---|---| -| | | | | C | I | A | -| Data | Existing Assets in the Threat model: ASSET-D-12 to ASSET-D-18, ASSET-D-20, ASSET-D-29, ASSET-D-31 to ASSET-D-38 | | | | | | -| Services | ZT-OCLOUD-S-X1 | O2ims services | It is responsible for infrastructure management services for O-Cloud Nodes. It offers the following services APIs [8]:
  • O2ims_InfrastructureInventory Services
  • O2ims_InfrastructureMonitoring Services
  • O2ims_InfrastructureProvisioning Services
  • O2ims_InfrastructureSoftwareManagement Services
  • O2ims_InfrastructureLifecycleManagement Services
| x | x | x | -| | ZT-OCLOUD-S-X2 | O2dms services | It is responsible for the deployment management services of the NF Deployment. It offers the following services APIs [7]: | x | x | x | - -| | | | | | | | | -|---------------------------------------------------------------------|-------------------------------------------------------------------------|----------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|---|---| -| | | | |
  • O2dms_DeploymentInventory Services
  • O2dms_DeploymentProvisioning Services
  • O2dms_DeploymentFault Services
  • O2dms_DeploymentPerformance Services
  • O2dms_DeploymentLifecycle Services
| | | | -| Infra-structure | Physical | ZT-OCLOUD-I-X1 | O-Cloud Hardware | It includes servers, data centers | | x | x | -| | Existing Assets in the Threat model: ASSET-C-08, ASSET-C-29, ASSET-C-30 | | | | | | | -| | Logical | ZT-OCLOUD-I-X2 | O-Cloud OS Software | It includes firmware and host OS. | x | x | x | -| | | ZT-OCLOUD-I-X3 | O-Cloud DMS | O-Cloud DMS software responsible for automating deployment processes and managing the lifecycles of applications within the O-Cloud. | | x | x | -| | | ZT-OCLOUD-I-X4 | O-Cloud IMS | O-Cloud IMS software responsible for the management of the cloud's physical and virtual resources. | | x | x | -| | | ZT-OCLOUD-I-X5 | O-Cloud Virtualization Layer | It includes hypervisors or container engines. | | x | x | -| | | ZT-OCLOUD-I-X6 | O-Cloud VMs | O-Cloud virtual machines. | | x | x | -| | | ZT-OCLOUD-I-X7 | O-Cloud Containers | O-Cloud containers. | | x | x | -| Applications | | ZT-OCLOUD-A-X1 | O-RAN Applications workloads | The workloads of O-RAN applications deployed within the O-Cloud. | x | x | x | -| Existing Assets in the Threat model: ASSET-C-23 (O2 protocol stack) | | | | | | | | - -### 5.3.3 New Assets in the Open Fronthaul - -**Table New Assets in the Open Fronthaul-5: Open Fronthaul Assets** - -| Asset ID | Asset Description | Component | Interface | When | | Protection Level | | | | | -|------------------------------------------------|--------------------------------|-----------|-----------|---------|------------|------------------|-----------|--------------|--------|--------------| -| | | | | At rest | In transit | Confidentiality | Integrity | Availability | Replay | Authenticity | -| Data & Interfaces | | | | | | | | | | | -| | | | | | | | | | | | -| Components (logical, virtual, physical) | | | | | | | | | | | -| ASSET-C-X | Transport Node Equipment (TNE) | | | x | | x | x | x | | x | - -| Asset ID | Asset Description | Component | Interface | When | | Protection Level | | | | | -|-----------|-----------------------------|-----------|-----------|---------|------------|------------------|-----------|--------------|--------|--------------| -| | | | | At rest | In transit | Confidentiality | Integrity | Availability | Replay | Authenticity | -| ASSET-C-X | Fronthaul Multiplexor (FHM) | | | x | | x | x | x | | x | -| ASSET-C-X | Fronthaul Gateway (FHGW) | | | x | | x | x | x | | x | -| ASSET-C-X | GM (Grand Master) | | | x | | x | x | x | | x | - -### 5.3.4 New Assets in F1 (Midhaul) - -**Table New Assets in F1 (Midhaul)-6: F1 Assets** - -| Asset ID | Asset Description | Component | Interface | When | | Protection Level | | | | | -|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|-----------|---------|------------|------------------|-----------|--------------|--------|--------------| -| | | | | At rest | In transit | Confidentiality | Integrity | Availability | Replay | Authenticity | -| | | | | | | | | | | | -| Data & Interfaces | | | | | | | | | | | -| ASSET-D-X | The F1-c interface, as defined by 3GPP, is between the gNB-CU-CP and gNB-DU logical nodes. 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. [i.1] | O-DU, O-CU-CP | F1-c | | x | x | x | x | x | x | -| ASSET-D-X | The F1-u interface, as defined by 3GPP, is between the gNB-CU-UP and gNB-DU logical nodes. 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. [i.1] | O-DU, O-CU-UP | F1-u | | x | x | x | x | x | x | - -| Asset ID | Asset Description | Component | Interface | When | | Protection Level | | | | | -|----------|------------------------------------------------|-----------|-----------|---------|------------|------------------|-----------|--------------|--------|--------------| -| | | | | At rest | In transit | Confidentiality | Integrity | Availability | Replay | Authenticity | -| | interoperability profile specifications. [i.1] | | | | | | | | | | - -# 6 Reference ZTA Security Requirements - -## 6.1 ZTA Framework - -### 6.1.1 Introduction - -There are several frameworks or roadmaps developed by US government agencies that provide organizations at the start of their ZT journey with a reference for charting their transition towards a ZTA. This clause gives an overview and comparison of the CISA Zero Trust Maturity Model and the DoD Zero Trust Strategy and Reference Architecture, and provides the selection of the ZTA framework for O-RAN evaluation. - -### 6.1.2 CISA's Zero Trust Maturity Model (ZTMM) - -The US Department of Homeland Security (DHS) Cybersecurity and Infrastructure Security Agency (CISA) developed the Zero Trust Maturity Model (ZTMM) [i.9]. ZTMM offers a systematic approach for organizations seeking to sustain ongoing modernization initiatives in the dynamic realms of cybersecurity and technology. It serves as a guide for organizations in crafting and executing their transition plans towards Zero Trust Architectures. CISA's Maturity Model (MM) outlines a phased and incremental approach for the effective implementation of a ZTA across four stages: Traditional, Initial, Advanced, and Optimal, as illustrated in Figure ZTA Framework-1. Emphasizing a comprehensive perspective, the model introduces five critical pillars for Zero Trust: Identity, Devices, Networks, Applications & Workloads, and Data. Each pillar is supported by distinct Pillar-specific Functions, delineating specific requirements that should be maintained across the four stages. For instance, under the Identity pillar, functions are specified with requirements tailored to each stage. Additionally, the model incorporates Cross-cutting Functions, which traverse all pillars and can evolve throughout the four stages. These cross-cutting functions encompass Visibility and Analytics, Automation and Orchestration, and Governance. The overarching concept is for agencies to assess their current enterprise stage, establish a target stage, conduct a meticulous gap analysis, and formulate a strategic plan accordingly. This structured approach ensures a methodical progression towards optimal Zero Trust implementation, tailored to the specific needs and requirements of each organization. - -![Diagram of the CISA Zero Trust Maturity Model (ZTMM) showing five pillars (Identity, Devices, Networks, Applications & Workloads, Data) across four maturity stages (Optimal, Advanced, Initial, Traditional). The pillars are supported by cross-cutting functions: Visibility and Analytics, Automation and Orchestration, and Governance.](446100c084b94817a19c319fa776b412_img.jpg) - -The diagram illustrates the CISA Zero Trust Maturity Model (ZTMM) as a temple-like structure. The roof is a dark blue triangle. Below it are five vertical pillars, each representing a critical pillar for Zero Trust: Identity, Devices, Networks, Applications & Workloads, and Data. The pillars are color-coded: Identity (blue), Devices (dark blue), Networks (green), Applications & Workloads (blue), and Data (green). To the left of the pillars, four maturity stages are listed from top to bottom: Optimal, Advanced, Initial, and Traditional, indicated by brackets. The pillars are supported by a base consisting of three horizontal steps, representing cross-cutting functions: Visibility and Analytics, Automation and Orchestration, and Governance. - -Diagram of the CISA Zero Trust Maturity Model (ZTMM) showing five pillars (Identity, Devices, Networks, Applications & Workloads, Data) across four maturity stages (Optimal, Advanced, Initial, Traditional). The pillars are supported by cross-cutting functions: Visibility and Analytics, Automation and Orchestration, and Governance. - -**Figure ZTA Framework-1: CISA Zero Trust Maturity Model** - -### 6.1.3 DoD Zero Trust Strategy and Reference Architecture - -The United States Department of Defense (DoD) Zero Trust Strategy [i.18] and Reference Architecture [i.14] collectively form a comprehensive framework guiding the implementation of zero trust principles. The Reference Architecture (RA) serves as a foundational element, presenting a capability-centric framework structured around architectural Pillars and Principles. This framework provides essential guidance for the strategic development of zero trust concepts, offering a systematic approach to conduct gap analyses, formulate requirements, oversee implementation, guide execution decision-making, and facilitate the procurement and deployment of necessary zero trust capabilities and activities. Simultaneously, the DoD Zero Trust Strategy serves as a crucial companion, furnishing actionable guidance that spans the entire spectrum of zero trust initiatives. The strategy encompasses a holistic approach, aligning seamlessly with the Reference Architecture to fortify the DoD's cybersecurity posture in a rapidly evolving threat landscape. - -The ZT Pillars in the DoD ZT Architecture align seamlessly with industry-standard identification of ZT Pillars. As illustrated in Figure ZTA Framework-2, the seven Pillars within the DoD ZT Architecture include: User, Devices, Network, Applications/Workload, Data, Visibility/Analytics, and Automation/Orchestration. Each Pillar serves as a key focus area for the implementation of specific zero trust controls, ensuring a holistic and effective security approach. - -Each pillar consists of multiple capabilities. Capabilities mean the ability to achieve a specific goal using different methods and resources. These capabilities use current technologies in zero trust and may change in the future. The Pillars and capabilities work together to give the best visibility and protection to data. Moreover, the DoD proposed the DoD ZT Capability roadmap that describes how the Department currently envisions achieving the capability-based outcomes and activities sequenced over time to achieve the DoD Zero Trust Target Level and Advanced Zero Trust [i.18, i.19]. - -The DoD framework also includes a Maturity Model that outlines the logical progression from an existing security model to an advanced zero trust architecture. This Maturity Model serves as a reference to assist information system owners in conceptualizing their transition from their current state to their desired architecture. The stages of the Maturity Model begin with As-Is state and progress through Baseline and Intermediate to Advanced stages, reflecting the evolution of zero trust capabilities and controls [i.14]. - -It is also important to note that the DoD Zero Trust Target Level encompasses a defined subset of DoD Zero Trust capabilities. This level includes both Baseline and Intermediate zero trust maturity stages, as outlined by the Zero Trust Reference Architecture (ZT RA). The DoD Advanced Zero Trust, on the other hand, represents the achievement of the full set of DoD-identified zero trust capabilities and aligns with the Advanced maturity stage [i.14, i.18]. - -![DoD Zero Trust Capabilities diagram showing a grid of capabilities across seven pillars: User, Device, Application & Workload, Data, Network & Environment, Automation & Orchestration, and Visibility & Analytics. Below the grid are Execution Enablers: Doctrine, Organization, Training, material, Leadership, Personnel, Facilities, and Policy.](145d00f59802048185303f15937ea65c_img.jpg) - -| DoD Zero Trust Capabilities | | | | | | | -|----------------------------------------------|---------------------------------------------------------------------------|------------------------------------------------------|-----------------------------------------|---------------------------------------|---------------------------------------------------------------|------------------------------------------------------| -| User | Device | Application & Workload | Data | Network & Environment | Automation & Orchestration | Visibility & Analytics | -| 1.1 User Inventory | 2.1 Device Inventory | 3.1 Application Inventory | 4.1 Data Catalog Risk Assessment | 5.1 Data Flow Mapping | 6.1 Policy Decision Point (PDP) & Policy Orchestration | 7.1 Log All Traffic (Network, Data, Apps, Users) | -| 1.2 Conditional User Access | 2.2 Device Detection and Compliance | 3.2 Secure Software Development & Integration | 4.2 DoD Enterprise Data Governance | 5.2 Software Defined Networking (SDN) | 6.2 Critical Process Automation | 7.2 Security Information and Event Management (SIEM) | -| 1.3 Multi-Factor Authentication | 2.3 Device Authorization with Real Time Inspection | 3.3 Software Risk Management | 4.3 Data Labeling and Tagging | 5.3 Macro Segmentation | 6.3 Machine Learning | 7.3 Common Security and Risk Analytics | -| 1.4 Privileged Access Management | 2.4 Remote Access | 3.4 Resource Authorization & Integration | 4.4 Data Monitoring and Sensing | 5.4 Micro Segmentation | 6.4 Artificial Intelligence | 7.4 User and Entity Behavior Analytics | -| 1.5 Identity Federation & User Credentialing | 2.5 Partially & Fully Automated Asset, Vulnerability and Patch Management | 3.5 Continuous Monitoring and Ongoing Authorizations | 4.5 Data Encryption & Rights Management | | 6.5 Security Orchestration, Automation & Response (SOAR) | 7.5 Threat Intelligence Integration | -| 1.6 Behavioral Contextual ID, and Biometrics | 2.6 Unified Endpoint Management (UEM) & Mobile Device Management (MDM) | | 4.6 Data Loss Prevention (DLP) | | 6.6 API Standardization | 7.6 Automated Dynamic Policies | -| 1.7 Least Privileged Access | 2.7 Endpoint & Extended Detection & Response (EDR & XDR) | | 4.7 Data Access Control | | 6.7 Security Operations Center (SOC) & Incident Response (IR) | | -| 1.8 Continuous Authentication | | | | | | | -| 1.9 Integrated ICAM Platform | | | | | | | - - - -| EXECUTION ENABLERS | Doctrine | Organization | Training | material | Leadership | Personnel | Facilities | Policy | -|--------------------|----------|--------------|----------|----------|------------|-----------|------------|--------| -|--------------------|----------|--------------|----------|----------|------------|-----------|------------|--------| - -DoD Zero Trust Capabilities diagram showing a grid of capabilities across seven pillars: User, Device, Application & Workload, Data, Network & Environment, Automation & Orchestration, and Visibility & Analytics. Below the grid are Execution Enablers: Doctrine, Organization, Training, material, Leadership, Personnel, Facilities, and Policy. - -Figure ZTA Framework-2: DoD ZT Capabilities - -### 6.1.4 Comparison of ZTMM models - -CISA ZTMM [i.9] and DoD ZTMM [i.14] complement NIST's ZTA by offering a roadmap for organizations to assess their current maturity level and provide guidance on steps to incrementally progress to higher maturity stages. The CISA and DoD ZTMMs mostly align with some differences, as described below. - -The four CISA ZTMM stages - Traditional, Initial, Advanced, and Optimal - are achieved for each of five pillars: Identity, Devices, Networks, Applications and Workloads, and Data. The CISA ZTMM also includes three cross-cutting functions across the five pillars: Visibility and Analytics, Automation and Orchestration, and Governance. These cross-cutting functions align with NIST tenets 4, 5, and 7 mentioned above. - -The four DoD ZTMM stages – As-is, Baseline, Intermediate, and Advanced - are achieved for each of seven pillars: User, Device, Networks, Applications and Workloads, Data, Visibility and Analytics, and Automation and Orchestration. The last two pillars in the DoD ZTMM model are considered cross-cutting functions by CISA. - -A diagram overlaying the CISA and DoD ZTMM models is shown in Figure ZTA Framework-3. - -![Figure ZTA Framework-3: Comparison of US CISA and DoD ZTMM. The diagram shows seven pillars categorized into 'CISA and DoD Pillars' (User/Identity, Device, Application & Workload, Network, Data) and 'DoD Pillars' (Automation and Orchestration, Visibility and Analytics). Each pillar is shown at four maturity levels: Optimal, Advanced, Initial, and Traditional. Below the pillars, three horizontal bars represent 'Automation and Orchestration', 'Visibility and Analytics', and 'Governance'.](02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg) - -Figure ZTA Framework-3: Comparison of US CISA and DoD ZTMM. The diagram shows seven pillars categorized into 'CISA and DoD Pillars' (User/Identity, Device, Application & Workload, Network, Data) and 'DoD Pillars' (Automation and Orchestration, Visibility and Analytics). Each pillar is shown at four maturity levels: Optimal, Advanced, Initial, and Traditional. Below the pillars, three horizontal bars represent 'Automation and Orchestration', 'Visibility and Analytics', and 'Governance'. - -**Figure ZTA Framework-3: Comparison of US CISA and DoD ZTMM** - -### 6.1.5 Selection of CISA ZTMM Model - -The CISA ZTMM version 2 [i.9] has been selected as the primary reference model for two reasons: - -1. CISA embeds its cross-cutting functions across its five pillars, instead of making those standalone pillars as the DoD ZTMM does. The CISA approach is preferred for O-RAN since Visibility and Analytics and Automation and Orchestration are applicable to all pillars and should not be silo'd. -2. CISA does not prescribe a timeline to reach its final stage, Optimal. While the DoD provides guidelines for implementation timelines, these are applicable to DoD use cases, which are outside the scope of O-RAN ALLIANCE. - -## 6.2 Target ZTA Security Requirements - -### 6.2.1 Introduction - -CISA's ZTMM offers four stages of zero trust journey with incremental approach to achieve ZTA for the five identified pillars - **Identity, Devices, Networks, Applications and Workloads, and Data** as well as the three cross cutting pillars - **Visibility and Analytics, Automation and Orchestration, and Governance** that encompass the five pillars. Each pillar has specific functions that progresses on the incremental journey to achieve ZTA. - -In this clause, we specify the O-RAN ZTA security requirements across the five pillars to identify gaps between O-RAN's current security requirements and those outlined in the CISA-aligned O-RAN ZTA security requirements. This assessment will help evaluate O-RAN's current zero trust maturity stage and, based on the gap analysis, define new security requirements and controls if needed. - -**NOTE:** The cross-cutting pillars **Visibility and Analytics, Automation and Orchestration, and Governance** will be included in a separate clause for specifying recommendations and requirements as needed. - -Each sub-clause of this clause is dedicated to a CISA ZTMM pillar and the "Guidance for Gap Analysis" of each function of a pillar provides information that can aid in gap analysis. - -The gap analysis is being performed against the INITIAL stage of CISA ZTMM security requirements. - -### 6.2.2 Identity - -#### 6.2.2.1 Introduction - -In O-RAN identity encompasses three entities namely users, devices, and software applications. The identity plays an important role to provide a unique attribute to the entity which is used to authenticate and authorize an entity. - -The Identity Pillar has the following pillar specific functions defined in CISA ZTMM: - -1. **Authentication** - Verification of users, devices, and software applications identities. -2. **Access Management** - Authorization ensures what resources and data an authenticated entity (user, device, or application) can access. -3. **Identity Stores** - Identity Stores are repositories where identity information is stored, managed, and accessed. -4. **Risk Assessments** - Continuously evaluating and mitigating identity-related risks through adaptive policies and real-time monitoring. - -#### 6.2.2.2 Authentication - -##### 6.2.2.2.1 Introduction - -Authentication function applies to the following three entities - users, devices, and software applications. - -##### 6.2.2.2.2 O-RAN ZTA Security Requirements for Authentication - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|--------------------|----------------------|-----------------------------------------------------|--------------------------------------------------------------|--------------------------| -| Authentication | Based on credentials | Credentials + Additional attributes (policy driven) | Phishing resistant MFA* (for e.g. FIDO)
*applies to users | Continual Authentication | - -##### 6.2.2.2.3 Guidance for Gap Analysis: - -- a. Additional attributes (contextual attributes) apply only to human user and external communication, and applicable to Architecture Elements having user access such as SMO. -- b. Phishing resistant MFA security control applies to human user access and not applicable to application-to-application access and device authentication. -- c. If there is mutual authentication for internal communications, we consider the stage as INITIAL. -- d. For internal interfaces, authentication based on credentials alone (certificate, pre-shared key, etc.) can be considered as meeting INITIAL maturity level. - -#### 6.2.2.3 Access Management (Authorization) - -##### 6.2.2.3.1 Introduction - -Authorization ensures what resources and data an authenticated entity (user, device, or application) is allowed to access and what actions they are permitted to perform within a O-RAN network or system. - -##### 6.2.2.3.2 O-RAN ZTA Security Requirements for Access Management (Authorization) - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|-----------------------------------|--------------------------------------------------------------------------------|----------------------------------------------------------------------------|----------------------------------------------------------------------------------------|-----------------------------------------------------------------| -| Access management (Authorization) | Long Lived access with manual revoking for privilege and unprivileged accounts | Short lived access for privileged access requests, with automated revoking | Need based and Session based access for all accounts tailored to actions and resources | Just-in-time and Just-enough access provided through automation | - -##### 6.2.2.3.3 Guidance for Gap Analysis: - -- a. This function applies to APIs and user access. -- b. For applications, static role assignments (e.g. role binding of a service account) with ephemeral tokens can be considered as INITIAL stage. -- c. For users, tokens with expiry can be considered as INITIAL stage. - -#### 6.2.2.4 Identity Stores - -##### 6.2.2.4.1 Introduction - -Identity Stores are repositories where identity information is stored, managed, and accessed. They are crucial for managing access, authentication, and authorization. In O-RAN, addressing Zero Trust Architecture (ZTA) requirements necessitates capturing, storing, and managing the identities of various actors—including administrators, applications, services, and devices—and their associated credentials and attributes. This is accomplished through the identity stores function within the identity pillar. - -##### 6.2.2.4.2 O-RAN ZTA Security Requirements for Identity Stores - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|--------------------|--------------------------------------|---------------------------------------------------------------------------------------------|-----------------------------------------------------------|-----------------------------| -| Identity Stores | Self-Managed On Prem Identity Stores | Self-managed and externally hosted identity stores co-exist with limited connectivity (SSO) | Consolidation of Self-managed and hosted identity stores. | Centralized Identity Stores | - -##### 6.2.2.4.3 Guidance for Gap Analysis: - -- a. None as this is a new function. -- b. WG11 to provide recommendation for Identity Stores. - -#### 6.2.2.5 Risk Assessment - -##### 6.2.2.5.1 Introduction - -Conducting Identity Risk Assessments for users, devices, and software application entities is crucial for advancing towards a Zero Trust Architecture (ZTA). Many other CISA ZTMM functions in other pillars depend on the risk assessment function in the identity pillar. This includes Network Traffic Management in the networks pillar, application access in the applications and workloads pillar, and data access in the data pillar. - -##### 6.2.2.5.2 O-RAN ZTA Security Requirements for Risk Assessment - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|------------------------|-----------------------------------------|------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| -| Risk Assessment | Limited identity risk assessment | Identity risk assessment though manual and static methods | Automated identity risk assessment to enforce dynamic access decisions and response activities. | Continuous Identity Risk Assessment in real time for adapting dynamic ongoing protection mechanism. | - -##### 6.2.2.5.3 Guidance for Gap Analysis: - -- a. None as this is a new function. -- b. WG11 to provide recommendation for Identity Risk Assessments. - -### 6.2.3 Devices - -#### 6.2.3.1 Introduction - -The Devices pillar includes the O-RAN network elements that fall under the infrastructure asset category. It includes Physical devices as well as virtual and cloud hardware. The pillar specific functions are as following: - -1. **Policy Enforcement & Compliance Monitoring-** Visibility of all devices and compliance and unified management and enforcement of policies. -2. **Asset & Supply Chain Risk Management-** Asset management tracks all physical, virtual, and cloud devices, using automated supply chain risk management to ensure comprehensive visibility and resilience against supply chain failures. -3. **Resource Access-** Secure and controlled access to resources based on device characteristics, risk analytics data. -4. **Device Threat Protection-** Implement security measures to detect, prevent, and respond to threats targeting devices. - -The potential O-RAN relevant zero trust functions for gap analysis study are Policy Enforcement and Compliance Monitoring, Resource Access, and Device Threat Protection. - -The Asset & Supply Chain Risk Management function is for further study. - -#### 6.2.3.2 Policy enforcement & Compliance monitoring - -##### 6.2.3.2.1 Introduction - -Manage dynamic inventory of all assets including their hardware, software, firmware, etc., along with their configurations and known associated vulnerabilities. Define device compliance policies and policy enforcement for all assets. - -##### 6.2.3.2.2 O-RAN ZTA Security Requirements for Policy enforcement and compliance monitoring - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| -| Policy Enforcement and Compliance Monitoring | No device visibility for device compliance
No policy enforcement mechanism or managing software, configurations, or vulnerabilities. | Basic Device characteristics visibility.
Basic policy enforcement mechanism for managing software, configurations, or vulnerabilities. | Automated methods to manage devices and virtual assets.
Automated policies to approve software configuration and identify vulnerabilities and install patches. | Continual verification of devices and virtual assets compliance and
Unified management and enforcement of policies | - -##### 6.2.3.2.3 Guidance for Gap Analysis: - -- a. Please refer to the table in clause 6.2.3.2.2 for different stages of this function, since there is no specific guidance. - -#### 6.2.3.3 Resource Access (Authorization) - -##### 6.2.3.3.1 Introduction - -The access to resources is allowed only for secured devices. - -##### 6.2.3.3.2 O-RAN ZTA Security Requirements for Resource Access - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|---------------------------------|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------| -| Resource Access (Authorization) | No visibility into devices or virtual assets used to access resources | Some visibility into devices or virtual assets' characteristics to approve resource access . | Full visibility into devices; Initial resource access considers verified device or virtual asset insights. | All resource access considers real-time risk analytics within devices and virtual assets. | - -##### 6.2.3.3.3 Guidance for Gap Analysis: - -- a. Use device characteristics or virtual asset characteristics (e.g. Access Control Rules (policy), environmental conditions) to approve resource access to align to the INITIAL stage. - -#### 6.2.3.4 Device Threat Protection - -##### 6.2.3.4.1 Introduction - -The devices are deployed with threat protection solutions to detect, prevent, respond, and recover from threats. - -##### 6.2.3.4.2 O-RAN ZTA Security Requirements for Device Threat Protection - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|--------------------|-------------|---------|----------|---------| -|--------------------|-------------|---------|----------|---------| - -| | | | | | -|---------------------------------|-----------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Device Threat Protection | Manual deployment of threat protection capabilities to some devices. | Some automated processes for deploying and updating threat protection capabilities to devices and to virtual assets with limited policy enforcement and compliance monitoring integration. | Consolidate threat protection capabilities to centralized solutions for devices and virtual assets and integrates most of these capabilities with policy enforcement and compliance monitoring. | Centralized threat protection security solution(s) deployed with advanced capabilities for all devices and virtual assets and a unified approach for device threat protection, policy enforcement, and compliance monitoring. | -| | | | | | - -##### 6.2.3.4.3 Guidance for Gap Analysis: - -- a. The guidance for gap analysis of 'Device Threat Protection' function is for further study. - -### 6.2.4 Networks - -#### 6.2.4.1 Introduction - -In O-RAN, the network pillar of CISA ZTMM encompasses internal, external interfaces of Architecture elements as well as infrastructure assets. The network pillar specific functions are as following. - -1. **Network Segmentation** - Dividing the network into smaller, isolated segments to enhance security based on application profiles and risk -2. **Network Traffic Management** - Define network rules and configuration based on application profile assessment. -3. **Traffic Encryption** - All data transmitted across the network is encrypted to protect confidentiality and integrity, using robust key management and adaptive encryption strategies. -4. **Network Resilience** - Continuous availability and resilience for all workloads. - -The O-RAN relevant zero trust functions for gap analysis study are **Network Segmentation, Traffic Encryption and Network Traffic Management.** - -The Network Resilience function is for future study. - -#### 6.2.4.2 Network Segmentation - -##### 6.2.4.2.1 Introduction - -The O-RAN Network functions are secured with micro-perimeters and all interfaces associated with it are secured. - -##### 6.2.4.2.2 O-RAN ZTA Security Requirements for Network Segmentation - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|-----------------------------|---------------------------------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------------------------| -| Network Segmentation | Perimeter / Macro-segmentation | Micro segmentation for critical workloads, and limiting network access | Application-Aware micro-segmentation with ingress/egress | Dynamic policy driven application-Aware Micro-segmentation; Allows for JEA/JIT | - -| | | | | | -|--|--|------------------------|------------------|------------------------------------| -| | | to a specific function | micro-perimeters | setup/teardown of micro-perimeters | -|--|--|------------------------|------------------|------------------------------------| - -##### 6.2.4.2.3 Guidance for Gap Analysis: - -- a. Perimeter based security protection like VPN tunnel access is considered as Traditional. -- b. Micro segmentation for critical workloads using namespaces, VLANs is considered as INITIAL . - -NOTE: Definition of micro-perimeter in the scope of O-RAN ALLIANCE is yet to be specified. - -#### 6.2.4.3 Traffic Encryption - -##### 6.2.4.3.1 Introduction - -Encryption of traffic through internal and external interfaces with secure key management. - -##### 6.2.4.3.2 O-RAN ZTA Security Requirements for Traffic Encryption - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|--------------------|-----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------| -| Traffic Encryption | Minimal traffic encryption with manual or ad hoc key management | Encryption for all internal (and preferably external) application traffic, with formalized key management policies and secure encryption keys. | Encryption for all traffic, with key and certificate life cycle management | Encryption of all traffic, enforces least privilege principles and crypto-agility | - -##### 6.2.4.3.3 Guidance for Gap Analysis: - -- a. Symmetric key based encryption methods, such as IPsec for E2, can be classified as being in the INITIAL stage. -- b. Certificate lifecycle management will upgrade the maturity to Advanced. - -#### 6.2.4.4 Network Traffic Management - -##### 6.2.4.4.1 Introduction - -Network Traffic Management involves implementing static and dynamic network rules for ingress and egress traffic, which are automatically adapted based on risk and application needs. - -##### 6.2.4.4.2 O-RAN ZTA Security Requirements for Network Traffic Management - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|--------------------|-------------------------------------------------|-----------------------------------|-------------------------------------------------|-----------------------------------------| -| Network Traffic | Static network rules/policies apply to critical | Static Ingress and Egress network | Dynamic network policies based on risk that are | Dynamic network policies based on risk; | - -| | | | | | -|-------------------|---------------------|------------------------------------|-----------------------|---------------------------------------------------------| -| Management | applications | rules/policies to all applications | automatically adapted | application needs that are automatically adapted | -|-------------------|---------------------|------------------------------------|-----------------------|---------------------------------------------------------| - -##### 6.2.4.4.3 Guidance for Gap Analysis: - -- a. Support for ingress and egress policies align with the INITIAL stage. - -NOTE: The support for ingress and egress policies is provided by the O-RAN Specifications. But the decision to provision the rules and policies is left to the operator. - -### 6.2.5 Applications and Workloads - -#### 6.2.5.1 Introduction - -Applications and workloads include systems, computer programs, and services that execute on-premises, on mobile devices, and in cloud environments [i.9]. In O-RAN, this pillar corresponds to the following asset categories: architecture elements, interfaces, and services. These asset categories are described in clause 5. The application and workloads pillar specific functions are as following: - -1. **Application Access** - This function outlines the requirements that must be met by the access control mechanism to authorize access to various applications within the system. -2. **Application Threat Protections** – This function describes how to incorporate threat protections into the workflows of applications. -3. **Accessible Applications** – This function describes how various applications within the system should be made available and accessible. -4. **Secure Application Development and Deployment Workflow** – This function details the requirements for secure development and deployment workflows for various applications within the system. -5. **Application Security Testing** – This function specifies the requirements for testing the security of applications. - -The O-RAN relevant zero trust functions for gap analysis study are **Application Access, Application Threat Protections, Accessible Applications, Secure Application Developments and Deployment Workflow, and Application Security Testing**. - -#### 6.2.5.2 Application Access - -##### 6.2.5.2.1 Introduction - -Application Access, also known as Access Authorization, is critical for limiting access to application assets only to authorized entities and removing access when no longer needed. It evolves through four distinct stages of sophistication, reflecting the maturity in managing application access. - -##### 6.2.5.2.2 O-RAN ZTA Security Requirements for Application Access - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|---------------------------|-----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|------------------------------------------------------------------------------------| -| Application Access | Access based on static attributes and local authorization | Begins to implement authorizing access capabilities to applications that incorporate contextual information (e.g., | Automates application access decisions with expanded contextual information and | Continuously authorizes application access, incorporating real-time risk analytics | - -| | | | | | -|--|--|------------------------------------------------------------------------------------|---------------------------------------------------------------------------|--------------------------------------------------| -| | | identity, device compliance, and/or other attributes) per request with expiration. | enforced expiration conditions that adhere to least privilege principles. | and factors such as behaviour or usage patterns. | -|--|--|------------------------------------------------------------------------------------|---------------------------------------------------------------------------|--------------------------------------------------| - -##### **6.2.5.2.3 Guidance for Gap Analysis** - -- a) Access authorization capabilities utilize contextual information such as identity, device compliance, and other attributes to make decisions on various requests for accessing application assets. -- b) Authorization is granted per request with expiration. - -#### **6.2.5.3 Application Threat Protections** - -##### **6.2.5.3.1 Introduction** - -As reliance on applications grows, so does the risk of cyber threats targeting these critical assets. To counteract these risks effectively, O-RAN should implement Application Threat Protection capabilities. - -##### **6.2.5.3.2 O-RAN ZTA Security Requirements for Application Threat Protections** - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|---------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Application Threat Protections | Threat protections have minimal integration with application workflows, applying general-purpose protections for known threats. | Integrates threat protections into mission-critical application workflows, applying protections against known threats and addressing some application-specific threats. | Integrates threat protections into all application workflows, safeguarding against certain application-specific and targeted threats. | Integrates advanced threat protections into all application workflows, providing real-time visibility and content-aware protections against sophisticated attacks tailored to applications. | - -##### **6.2.5.3.3 Guidance for Gap Analysis** - -- a) Threat protection is integrated into mission-critical application workflows. -- b) Threat protections safeguard applications against known threats and address some application-specific threats. - -#### **6.2.5.4 Accessible Applications** - -##### **6.2.5.4.1 Introduction** - -Accessibility to applications is paramount for organizational efficiency and productivity. - -##### 6.2.5.4.2 O-RAN ZTA Security Requirements for Application Accessibility - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| -| Accessible Applications | Some mission-critical applications are made available exclusively over private networks and protected public network connections (e.g., VPN), with monitoring. | Some of the applicable mission-critical applications are made accessible over open public networks to authorized users with specific needs via brokered connections. | Most of the applicable mission-critical applications are made available over open public network connections to authorized users as needed. | All applicable applications are made available over open public networks to authorized users and devices, where appropriate, as needed. | - -##### 6.2.5.4.3 Guidance for Gap Analysis - -- a) Applicable mission-critical applications are available over open public network connections to authorized users as needed. - -#### 6.2.5.5 Secure Application Development and Deployment Workflow - -##### 6.2.5.5.1 Introduction - -The Secure Application Development and Deployment Workflow is crucial for O-RAN as it ensures the integrity and security of applications across diverse and distributed network components. - -##### 6.2.5.5.2 O-RAN ZTA Security Requirements for Secure Application Development - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|---------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Secure Application Development and Deployment Workflow | There are ad hoc development, testing, and production environments with non-robust code deployment mechanisms. | Infrastructure is provided for development, testing, and production environments (including automation) with formal code deployment mechanisms through CI/CD pipelines and requisite access controls supporting least privilege principles. | Distinct and coordinated teams for development, security, and operations are used, while developer access to the production environment for code deployment is removed. | Immutable workloads are leveraged where feasible, only allowing changes to take effect through redeployment. Administrator access to deployment environments is removed in favor of automated processes for code deployment. | - -##### 6.2.5.5.3 Guidance for Gap Analysis - -- a) Infrastructure for development, testing, and production environments (including automation). -- b) Formal code deployment mechanisms through CI/CD pipelines. - -- c) Access controls support least privilege principles. - -#### 6.2.5.6 Application Security Testing - -##### 6.2.5.6.1 Introduction - -Application security testing is crucial for identifying and mitigating vulnerabilities early, reducing the risk of security breaches. This proactive approach ensures the consistent protection of applications, safeguarding sensitive data and maintaining the integrity of the O-RAN system. - -##### 6.2.5.6.2 O-RAN ZTA Security Requirements for Application Security Testing - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|-------------------------------------|----------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Application Security Testing | Application security testing is conducted prior to deployment, primarily through manual testing methods. | Static and dynamic testing methods, including manual expert analysis, are employed for security testing before application deployment. | Application security testing is seamlessly integrated into the application development and deployment process, incorporating periodic dynamic testing methods. | Application security testing is integrated across the software development lifecycle within the enterprise, with routine automated testing of deployed applications. | - -##### 6.2.5.6.3 Guidance for Gap Analysis - -- a) Utilization of static and dynamic testing methods for security testing. -- b) Performance of security testing including manual expert analysis before application deployment. - -### 6.2.6 Data - -#### 6.2.6.1 Introduction - -In O-RAN, data encompasses both structured and unstructured files and fragments that are currently or have previously been present in O-RAN systems, devices, networks, applications, databases, infrastructure, and backups (including both on-premises and virtual environments), along with their corresponding metadata. - -1. **Data Inventory Management** – This function describes how the system inventories its data. -2. **Data Categorization** – This function outlines how data should be categorized within the system. -3. **Data Availability** – This function specifies how various data within the system should be made available. -4. **Data Access** - This function outlines the requirements that must be met by the access control mechanism to authorize access to various data within the system. -5. **Data Encryption** – This function specifies requirements for encrypting data within the system. - -The potential O-RAN relevant zero trust functions for gap analysis study are **Data Inventory Management, Data Categorization, Data Availability, Data Access, and Data Encryption**. - -#### 6.2.6.2 Data Inventory Management - -##### 6.2.6.2.1 Introduction - -A data inventory is a comprehensive catalogue that identifies and inventories all available data within the O-RAN system. It should detect and incorporate any changes to the data landscape. This inventory includes metadata about the data, providing a detailed reference that aids in understanding and managing the organization's data assets effectively. - -##### 6.2.6.2.2 O-RAN ZTA Security Requirements for Data Inventory Management - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|----------------------------------|------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| -| Data Inventory Management | Manually identifies and inventories some O-RAN data (e.g., mission critical data). | Automate data inventory processes for both on-premises and in cloud environments, covering most O-RAN data, and begins to incorporate protections against data loss. | Automate data inventory and tracking all applicable data, with data loss prevention strategies based upon static attributes and/or labels. | Continuously inventories all applicable data and employs robust data loss prevention strategies that dynamically block suspected data exfiltration. | - -##### 6.2.6.2.3 Guidance for Gap Analysis - -- a) Automated data inventory processes for both on-premises and in cloud environments, which covers most system data. -- b) Protections against data loss are beginning to be incorporated. - -#### 6.2.6.3 Data Categorization - -##### 6.2.6.3.1 Introduction - -Establishing granular data categorization integrated into access control systems consistently and correctly is required for machine enforceable data access controls, risk assessment, and situational awareness. As data categorization and labelling practices mature, labelling should become automated to meet scaling demands and provide better labelling accuracy. - -##### 6.2.6.3.2 O-RAN ZTA Security Requirements for Data Categorization - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|----------------------------|------------------------------------------------------|-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| -| Data Categorization | Limited and ad hoc data categorization capabilities. | Implement a data categorization strategy with defined labels and manual enforcement mechanisms. | Automate some data categorization and labeling processes in a consistent, tiered, targeted manner with simple, structured formats and regular review. | Automate data categorization and labeling enterprise-wide with robust techniques; granular, structured formats; and mechanisms to address all data types. | - -##### 6.2.6.3.3 Guidance for Gap Analysis - -- a) A data categorization strategy with defined labels and manual enforcement mechanisms. - -#### 6.2.6.4 Data Availability - -##### 6.2.6.4.1 Introduction - -Data Availability refers to the ability of an organization to ensure that its data is accessible when needed, both in terms of current and historical data. This function progresses through various stages of sophistication and reliability, marked by increasing redundancy, optimization, and user-centric access methods. - -##### 6.2.6.4.2 O-RAN ZTA Security Requirements for Data Availability - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|--------------------|-----------------------------------------------------|------------------------------------------------------------------------------------------------------|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------| -| Data Availability | Data stored on-premises with some off-site backups. | Data stored in redundant mode (e.g., cloud) and maintained in off-site backups for on premises data. | Data stores in redundant mode with access to historical data. | Dynamically Optimized data availability, including historical data, as per user and entity need. | - -##### 6.2.6.4.3 Guidance for Gap Analysis - -- a) Data stored in redundant mode (e.g., cloud). -- b) Data maintained in off-site backups for on premises data. - -#### 6.2.6.5 Data Access - -##### 6.2.6.5.1 Introduction - -Data access control aims to restrict access to and usage of data based on properties and attributes associated with the data, the user/device, along with any other relevant information. This ensures that unauthorized entities or entities using unauthorized devices cannot access the data. Additionally, it ensures that users and devices with access to the data undergo continuous attribute inspection through various policy decisions and enforcement points within the architecture. This function progresses through several stages, evolving from static access control to dynamic, just-in-time, and just-enough data access controls. - -##### 6.2.6.5.2 O-RAN ZTA Security Requirements for Data Access - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|--------------------|-----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------| -| Data Access | Users and entities access to data is governed through static access control | Automated data access controls that incorporate elements of least privileges are deployed. | Automated data access controls are time-limited and consider contextual attributes such as identity, device risk, application, and data category. | Automated dynamic just-in-time and just-enough data access controls are implemented with continuous review of permissions. | - -##### 6.2.6.5.3 Guidance for Gap Analysis: - -- a) Automated data access control. -- b) Elements of least privileges are incorporated with the automated data access control. - -#### 6.2.6.6 Data Encryption - -##### 6.2.6.6.1 Introduction - -Data encryption is crucial for protecting data against unauthorized access, modification, or redistribution. Encrypting data ensures that organizations can protect their data even if it is exfiltrated or lost, as long as the decryption keys remain secure and out of the hands of malicious actors. - -##### 6.2.6.6.2 O-RAN ZTA Security Requirements for Data Encryption - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Data encryption | Basic encryption is applied to minimal data (both at rest and in transit), utilizing manual or ad hoc processes for managing and securing encryption keys. | All data in transit and, where feasible, data at rest are encrypted. Key management policies and secure encryption keys are beginning to be formalized. | All data at rest and in transit across the O-RAN system are encrypted to the maximum extent possible, cryptographic agility is being incorporated, and encryption keys are protected. | Data in use is encrypted where appropriate, least privilege principles for secure key management system-wide are enforced, and encryption is applied using up-to-date standards and cryptographic agility to the extent possible. | - -##### 6.2.6.6.3 Guidance for Gap Analysis - -- a) Encrypted data in transit and, where feasible, data at rest. -- b) Key management policies and secure encryption keys are beginning to be formalized. - -### 6.2.7 Cross-Cutting Capabilities - -#### 6.2.7.1 Introduction - -The cross-cutting capabilities Visibility and Analytics, Automation and Orchestration, and Governance provide opportunities to integrate advancements across each of the five pillars. Visibility and Analytics supports comprehensive visibility that informs policy decisions and facilitates response activities. Automation and Orchestration capabilities leverage these insights to support robust and streamlined operations to handle security incidents and respond to events as they arise. Governance enables agencies to manage and monitor their regulatory, legal, environmental, federal, and operational requirements in support of risk-based decision making. Governance capabilities also ensure the right people, process, and technology are in place to support mission, risk, and compliance objectives [i.9]. CISA ZTMM recommends that these capabilities mature both in relation to each specific pillar and independently of the pillars. This - -clause outlines the O-RAN target security requirements for the CISA ZTMM cross-cutting capabilities. It begins by presenting the general O-RAN ZTA security requirements for visibility and analytics, and then details these requirements across the various pillars. The governance capability is considered out of scope, as it pertains to defining and enforcing policies, which falls under operational scope. - -#### 6.2.7.2 High level maturity evolution for Cross-Cutting Capabilities - -##### 6.2.7.2.1 Visibility and Analytics - -###### 6.2.7.2.1.1 O-RAN ZTA Security Requirements for Visibility and Analytics Cross-cutting Capability - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|---------------------------------|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| -| Visibility and Analytics | Manually collecting limited logs with low fidelity and minimal analysis. | Begins the automation of the collection and analysis of logs and events for mission critical functions and regularly assesses processes for gaps in visibility. | Expands the automated collection of logs and events (including virtual environments) for centralized analysis that correlates across multiple sources. | Maintains comprehensive visibility enterprise-wide via centralized dynamic monitoring and advanced analysis of logs and events. | - -###### 6.2.7.2.1.2 Guidance for Gap Analysis - -- a) The automation of the collection and analysis of logs and events for mission-critical functions is initiated. -- b) Processes are regularly assessed for gaps in visibility. - -##### 6.2.7.2.2 Automation and Orchestration - -###### 6.2.7.2.2.1 O-RAN ZTA Security Requirements for Automation and Orchestration Cross-cutting Capability - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|-------------------------------------|------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| -| Automation and Orchestration | Relies on static and manual processes to orchestrate operations and response activities with limited automation. | Begins automating orchestration and response activities in support of critical mission functions. | Automates orchestration and response activities leveraging contextual information from multiple sources to inform decisions. | Orchestration and response activities dynamically respond to changing requirements and environmental changes. | - -###### 6.2.7.2.2.2 Guidance for Gap Analysis - -- a) The automation of orchestration and response activities in support of critical mission functions is initiated. - -#### 6.2.7.3 Identity Cross-Cutting Capabilities - -##### 6.2.7.3.1 Visibility and Analytics - -Collecting and analyzing user and entity logs is crucial for maintaining network security and identifying potential threats. User and entity behaviour analytics (UEBA) leverages this log data to detect abnormal behaviours, which are often indicative of security incidents. By correlating information across multiple log sources, UEBA can identify unusual patterns that single or limited log sources might miss. This comprehensive analysis is essential because cyber actors frequently attempt to blend in with regular network activities, making it challenging to spot their malicious actions. Through thorough log collection and analysis, organizations can enhance their ability to detect, investigate, and respond to security threats effectively [i.22]. - -###### 6.2.7.3.1.1 O-RAN ZTA Security Requirements for Visibility and Analytics in the Identity Pillar - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|--------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Visibility and Analytics Capability | Collects user and entity activity logs, especially for privileged credentials, and performs some routine manual analysis. | Collects user and entity activity logs and performs routine manual analysis and some automated analysis, with limited correlation between log types. | Performs automated analysis across some user and entity activity log types and augments collection to address gaps in visibility. | Maintains comprehensive visibility and situational awareness across enterprise by performing automated analysis over user activity log types, including behaviour-based analytics. | - -###### 6.2.7.3.1.2 Guidance for Gap Analysis - -- a) Collecting user and entity activity logs. -- b) Performing Routine Analysis: - - a. Conduct regular manual analysis of the logs. - - b. Implement some automated analysis, with limited correlation between different log types. - -##### 6.2.7.3.2 Automation and Orchestration - -###### 6.2.7.3.2.1 O-RAN ZTA Security Requirements for Automation and Orchestration in the Identity Pillar - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| -| Automation and Orchestration Capability | Manually orchestrates (onboards, offboards, and disables) self-managed identities (users and entities), with little integration, and performs regular review. | Manually orchestrates privileged and external identities and automates orchestration of non-privileged users and of self-managed entities. | Manually orchestrates privileged user identities and automates orchestration of all identities with integration across all environments. | Automates orchestration of all identities with full integration across all environments based on behaviours, enrollments, and deployment needs. | - -###### 6.2.7.3.2.2 Guidance for Gap Analysis - -- a) Manually orchestrates privileged and external identities. -- b) Automates orchestration of non-privileged users. -- c) Automates orchestration of self-managed entities. - -#### 6.2.7.4 Devices Cross-Cutting Capabilities - -##### 6.2.7.4.1 Visibility and Analytics - -###### 6.2.7.4.1.1 O-RAN ZTA Security Requirements for Visibility and Analytics in the Devices Pillar - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Visibility and Analytics Capability | Uses a physically labeled inventory and limited software monitoring to review devices on a regular basis with some manual analysis. | Uses digital identifiers alongside a manual inventory and endpoint monitoring of devices when available. Some devices and virtual assets are under automated analysis (e.g., software-based scanning) for anomaly detection based on risk. | Automates both inventory collection and anomaly detection to detect unauthorized devices. | Automates status collection of all network-connected devices and virtual assets while correlating with identities, conducting endpoint monitoring, and performing anomaly detection to inform resource access. Tracks patterns of provisioning and/or de-provisioning of virtual assets for anomalies. | - -###### 6.2.7.4.1.2 Guidance for Gap Analysis - -- a) Digital Identifiers: Use digital identifiers alongside a manual inventory and endpoint monitoring of devices when available. -- b) Automated Analysis: Ensure some devices and virtual assets are under automated analysis (e.g., software-based scanning) for anomaly detection based on risk. - -##### 6.2.7.4.2 Automation and Orchestration - -###### 6.2.7.4.2.1 O-RAN ZTA Security Requirements for Automation and Orchestration in the Devices Pillar - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|------------------------------------------------|----------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| -| Automation and Orchestration Capability | Manually provisions, configures, and/or registers devices within the enterprise. | Begins to use tools and scripts to automate the process of provisioning, configuration, registration, and/or deprovisioning for devices and virtual assets. | Monitoring and enforcement mechanisms are implemented to identify and manually disconnect or isolate non-compliant devices and virtual assets. | Fully automated processes are in place for provisioning, registering, monitoring, isolating, remediating, and deprovisioning devices and virtual assets. | - -###### 6.2.7.4.2.2 Guidance for Gap Analysis - -- a) Utilization of monitoring and enforcement mechanisms to identify and manually disconnect or isolate non-compliant devices and virtual assets. - -#### 6.2.7.5 Networks Cross-Cutting Capabilities - -##### 6.2.7.5.1 Visibility and Analytics - -###### 6.2.7.5.1.1 O-RAN ZTA Security Requirements for Visibility and Analytics in the Networks Pillar - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Visibility and Analytics Capability | Incorporates limited boundary-focused network monitoring capabilities with minimal analysis to start developing centralized situational awareness. | Employs network monitoring capabilities based on known indicators of Compromise (including network enumeration) to develop situational awareness in each environment and begins to correlate telemetry across traffic types and environments for analysis and threat hunting activities. | Deploys anomaly-based network detection capabilities to develop situational awareness across all environments, begins to correlate telemetry from multiple sources for analysis, and incorporates automated processes for robust threat hunting activities. | Maintains visibility into communication across all agency networks and environments while enabling enterprise-wide situational awareness and advanced monitoring capabilities that automate telemetry correlation across all detection sources. | - -###### 6.2.7.5.1.2 Guidance for Gap Analysis - -- a) Utilize network monitoring capabilities based on known indicators of compromise, including network enumeration, to develop situational awareness in each environment. -- b) Commence correlating telemetry across traffic types and environments to facilitate analysis and threat hunting activities. - -##### 6.2.7.5.2 Automation and Orchestration - -###### 6.2.7.5.2.1 O-RAN ZTA Security Requirements for Automation and Orchestration in the Networks Pillar - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Automation and Orchestration Capability | Utilizes manual processes to manage the configuration and resource lifecycle for networks and environments with periodic integration of policy requirements and situational | Begins employing automated methods to manage the configuration and resource lifecycle for some networks or environments and ensures that all resources have a defined lifetime based on policies | Uses automated change management methods (e.g., CI/CD) to manage the configuration and resource lifecycle for all networks and environments, responding to and enforcing policies and protections against | Networks and environments are defined using infrastructure-as-code managed by automated change management methods, including automated initiation and expiration to align with changing needs. | - -| | | | | | -|--|------------|----------------|------------------|--| -| | awareness. | and telemetry. | perceived risks. | | -|--|------------|----------------|------------------|--| - -###### 6.2.7.5.2.2 Guidance for Gap Analysis - -- a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments. -- b) Ensure that all resources have a defined lifetime determined by policies and telemetry data. - -#### 6.2.7.6 Applications & Workloads Capabilities - -##### 6.2.7.6.1 Visibility and Analytics - -###### 6.2.7.6.1.1 O-RAN ZTA Security Requirements for Visibility and Analytics in the Applications & Workloads Pillar - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------| -| Visibility and Analytics Capability | Performs some performance and security monitoring of mission critical applications with limited aggregation and analytics. | Begins to automate application profile and security monitoring for improved log collection, aggregation, and analytics. | Automates profile and security monitoring for most applications with heuristics to identify application-specific and enterprise-wide trends and refines processes over time to address gaps in visibility | Performs continuous and dynamic monitoring across all applications to maintain enterprise-wide comprehensive visibility. | - -###### 6.2.7.6.1.2 Guidance for Gap Analysis - -- a) Initiate the automation of application profile and security monitoring processes for improved log collection, aggregation, and analytics. - -##### 6.2.7.6.2 Automation and Orchestration - -###### 6.2.7.6.2.1 O-RAN ZTA Security Requirements for Automation and Orchestration in the Applications & Workloads Pillar - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------| -| Automation and Orchestration Capability | Manually establishes static application hosting location and access at provisioning with limited maintenance and review. | Periodically modifies application configurations (including location and access) to meet relevant security and performance goals. | Automates application configurations to respond to operational and environmental changes. | Automates application configurations to continuously optimize for security and performance. | - -###### 6.2.7.6.2.2 Guidance for Gap Analysis - -- a) Periodically modifies application configurations, including location and access parameters, to align with pertinent security and performance objectives. - -#### 6.2.7.7 Data Cross-Cutting Capabilities - -##### 6.2.7.7.1 Visibility and Analytics - -###### 6.2.7.7.1.1 O-RAN ZTA Security Requirements for Visibility and Analytics in the Data Pillar - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Visibility and Analytics Capability | Limited visibility into data including location, access, and usage, with analysis consisting primarily of manual processes. | Obtains visibility based on data inventory management, categorization, encryption, and access attempts, with some automated analysis and correlation. | Maintains data visibility in a more comprehensive, enterprise-wide manner with automated analysis and correlation and begins to employ predictive analytics. | Obtains visibility across the full data lifecycle with robust analytics, including predictive analytics, that support comprehensive views of the data and continuous security posture assessment. | - -###### 6.2.7.7.1.2 Guidance for Gap Analysis - -- a) Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. - -##### 6.2.7.7.2 Automation and Orchestration - -###### 6.2.7.7.2.1 O-RAN ZTA Security Requirements for Automation and Orchestration in the Data Pillar - -| CISA ZTMM Function | Traditional | Initial | Advanced | Optimal | -|------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------| -| Automation and Orchestration Capability | Implements data lifecycle and security policies (e.g., access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) through manual, and potentially ad hoc, processes. | Utilizes some automated processes to implement data lifecycle and security policies. | Automates orchestration and response activities that leverage contextual information from multiple sources to inform decisions. | Orchestration and response activities dynamically respond to changing requirements and environmental changes. | - -###### 6.2.7.7.2.2 Guidance for Gap Analysis - -- a) Data lifecycle and security policies are automated. - -# 7 Alignment to Target ZTA Requirements - -## 7.1 Introduction - -This clause first reviews the current status of O-RAN security specifications and then evaluates this against the reference ZTA security requirements in clause 6.2. - -## 7.2 Current O-RAN Security Requirements and Controls - -Table 7.2 is a snapshot of the interface security controls enforcing authenticity, confidentiality, integrity, authorization, data origination, and replay prevention. The protocols listed in Table 7.2 are mandatory for the vendor to support (unless where noted) and optional for the operator to use, as regional regulatory requirements may differ. The exception is MACsec which is optional for the vendor to support as well as optional for the operator to use. Detailed requirements can be found in [i.2] and [i.3]. - -**Table 7.2-7: O-RAN interface security controls (See NOTE for 802.1X and PDCP)** - -| Security Control | Non-Fronthaul | | | | | | Open Fronthaul | | | | -|-------------------|---------------|------|-------|--------|-------|-------|-----------------------------|---------------------------------------------|-----------------------------|--------------------------------------| -| | A1 | O1 | O2 | E2 | Y1 | R1 | C-plane | U-plane | S-plane | M-plane | -| Authenticity | mTLS | mTLS | mTLS | IPsec | mTLS | mTLS | 802.1X 1
PNAC | 802.1X 1
PNAC | 802.1X 1
PNAC | mTLS/SSH/802.1X 1
PNAC | -| Confidentiality | TLS | TLS | TLS | IPsec | TLS | TLS | MACsec
(optional) | PDCP 2 ,
MACsec
(optional) | MACsec
(optional) | TLS/SSH | -| Integrity | TLS | TLS | TLS | IPsec | TLS | TLS | MACsec
(optional) | PDCP 2 ,
MACsec
(optional) | MACsec
(optional) | TLS/SSH | -| Authorization | OAuth | NACM | OAuth | NOTE 3 | OAuth | OAuth | 802.1X
PNAC | 802.1X
PNAC | 802.1X
PNAC | NACM/802.1X
PNAC | -| Data Origination | mTLS | mTLS | mTLS | IPsec | mTLS | mTLS | | PDCP 2 | | TLS/SSH | -| Replay Prevention | TLS | TLS | TLS | IPsec | TLS | TLS | | PDCP 2 | | TLS/SSH | - -NOTE 1: 802.1X port-based network access control (PNAC) provides authentication of the device plugging into a network port and controls access to send/receive network traffic. 802.1X PNAC [i.16] does not provide authenticity of the data flowing across the C-plane, U-plane, S-plane, and M-plane interfaces between the O-DU and O-RU. - -NOTE 2: 3GPP Access Stratum (AS) Control Plane and User Plane messages that are transported via the Open Fronthaul U-Plane (LLS-UP) are confidentiality and integrity protected by the Packet Data Convergence Protocol (PDCP) [i.32]. PDCP security controls remain in place when the message traverses the Open Fronthaul U-Plane. PDCP requirements are specified by the 3GPP in TS 33.501 [i.17]. PDCP does not provide confidentiality and integrity protection for plain text messages flowing across the U-plane interface between the O-DU and O-RU. - -NOTE 3: In the case of E2 interface, authentication grants authorization and there is no native authorization method for SCTP. - -The controls still under development are related to the session key management of the S-plane. This is being developed in collaboration with WG4 and WG9. - -Table 7.2-8 is an overview of the mandatory O-RAN transversal requirements that support ZT tenets such as security posture, data collection, and monitoring. - -**Table 7.2-8: O-RAN Cross-Platform Security Requirements** - -| Category | Mandatory Requirements | -|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Application Lifecycle Management |
  • • Application signing by vendor
  • • Signature validation by SMO
  • • Secure deletion of sensitive data
  • • Secure decommissioning of applications
| -| Network Protocols and Services |
  • • Provider documentation of all required network protocols/services
  • • Default disablement of unused network protocols/services
| -| Robust Protocol Implementation |
  • • Handle unexpected inputs without functional compromise
| -| Robustness of OS and Applications |
  • • Known vulnerabilities in the OS and applications be documented by their providers
| -| Password based Authentication |
  • • Mitigate risks from password authentication attacks where password authentication is implemented
| -| Software Supply Chain Security |
  • • Vendor signed, NTIA compliant SBOM with every O-RAN software delivery.
| -| Security Log Management |
  • • Identification of security events to log
  • • Collection of security logs by all O-RAN elements
  • • Least privileged access controls on security logs
  • • Logging of anomalous events
  • • Confidentiality and integrity protection of log data at rest and in transit
  • • Rotation of logs to prevent data loss
  • • Use of micro-perimeters to protect logs
  • • Time stamping of all logged events
  • • Inclusion of identity of O-RAN element generating event
| -| Certificate Management Framework |
  • • Support of CMPv2
| -| API Security |
  • • Support of OWASP API Security Project
  • • Support of certificate-based authentication using mTLS 1.2+
  • • Confidentiality and integrity protection of data in transit with TLS 1.2+
  • • Least privileged authorization using OAuth 2.0
  • • Input validation
| - -![O-RAN ALLIANCE logo](03cece90958de8ea69661d3295cf3e88_img.jpg) - -O-RAN.WG11.TR.ZTA-R005-v05.00 - -| | | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Trust Anchor Provisioning |
  • Pre-provisioning of certificates that chain back to a vendor or operator CA in PNFs
| -| AI/ML Security |
  • Model integrity, confidentiality, authentication, and authorization
  • A1 authentication and authorization
  • Secure data sourcing, sanitization, and transformation
  • Data poisoning prevention
  • Adversarial training
  • Differential privacy
  • Model splitting
  • Feature selection training
| - -## 7.3 Gap Analysis - -### 7.3.1 Gap Analysis Methodology - -#### 7.3.1.1 Gap Analysis Workflow - -The gap analysis guidelines for addressing the Initial stage for each pillar in the CISA ZTMM within O-RAN were derived in clause 6.2. Figure Gap Analysis-4 outlines the high-level workflow for performing the gap analysis. The workflow is divided into two paths: one for the defined assets described in clause 5.2 [i.4] and the other for new assets identified during the ZTA WI study as described in clause 5.3. - -- Asset Mapping:** First, list the various types of assets for each O-RAN element, and then map the assets to the corresponding CISA ZTMM Pillar. -- Comparison:** Compare the current security requirements and controls of the assets to the corresponding ZT pillar's INITIAL Maturity Level security guidelines, as derived in clause 6.2. -- Gap Identification:** Document the gap analysis and forward the identified gaps to relevant work items (e.g., Near-RT RIC, Open Fronthaul, O-Cloud, SMO). -- Work Item Analysis:** This step involves consultation with the relevant WG11 Work Item. Each work item performs threat analysis for the gaps which were identified in the previous step, determines new security requirements and controls to achieve the INITIAL ZTA Maturity Level and updates the Threat Modeling and Risk Assessment Technical Report [i.4] and Security Requirements and Controls Specifications [i.2]. - -![Gap Analysis Workflow Diagram](1da66f5fec34c001912c84a9abf145d7_img.jpg) - -**Legend** - -| | | -|--------------------------------------|-------------| -| — | Pending | -| — | Complete | -| — | In progress | - -Detailed description of Figure Gap Analysis-4: A flowchart showing the process from 'Assets' (split into 'Defined' and 'New'). 'Defined' assets lead to 'Threat analysis' and 'Current security requirements and controls'. 'New' assets lead to 'ZT Pillars' and 'ZTA security requirements'. These paths converge at 'Gap analysis / ZTA TR update'. A dashed yellow box below contains 'Gaps', 'Threat analysis', 'Risk score', and 'Updates to Security Requirements and Controls'. Numbered circles (1, 2, 3, 4) indicate specific steps or transitions. A note at the bottom states: 'WI TR, Threat Model and Risk Assessment, and WG11 specifications are updated by WI teams'. - -**Figure Gap Analysis-4 Gap Analysis Workflow** - -Gap Analysis Workflow Diagram - ---- - -© 2026 by the O-RAN ALLIANCE e.V. Your use is subject to the copyright statement on the cover page of this specification. 60 - -#### 7.3.1.2 Gap Analysis Conclusions - -At the end of the work item analysis step, the relevant WG11 work items should arrive at a decision regarding each identified gap forwarded from the ZTA work item. There are three possible conclusions with subsequent steps, which are detailed in Table Gap Analysis Methodology-9:. The first column presents the conclusion, the second column explains the circumstances under which each conclusion can be derived, and the third column outlines the corresponding next steps for each conclusion. - -**Table Gap Analysis Methodology-9: Options for Work Item Analysis Conclusions** - -| Conclusion | Conditions | Subsequent Steps | -|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Addressed | This conclusion applies when the relevant work item resolves the identified gap by adding or identifying requirement(s) in the Security Requirements and Controls Specifications. |
  1. 1. Update the relevant gap analysis table in the ZTA TR as following:
    1. a. Update the “comments” column with “Gap resolved as requirements were identified after initial analysis,” or “Gap resolved by new requirements added after initial analysis.”
    2. b. Update the "Existing Requirements Mapped to CISA Stage" column with the relevant new requirements numbers.
| -| Out of scope for O-RAN | This conclusion applies when addressing the identified gap is necessary to maintain a Zero Trust Architecture (ZTA); however, specifying the requirements and controls to address this gap does not fall within the scope of the O-RAN ALLIANCE. Out of scope requirements and controls are those that specify conditions on equipment, functions, or activities that are outside of O-RAN's purview and could fall under operators' responsibilities. |
  1. 1. Update the “comments” column in the relevant gap analysis table in the ZTA TR with “Out of scope for O-RAN” and a short explanation.
  2. 2. Update the recommendation clause and highlight this.
| -| No action is needed | This conclusion applies when the relevant work item decides that no action will be taken to address the identified gap for a justified reason. This decision may be based on various factors, such as if addressing the identified gap is very costly compared to the risk associated with it. |
  1. 1. Update the comments column in the relevant table in the gap analysis clause with “No action is needed” and the justified reason.
  2. 2. Update the Recommendation clause and highlight this.
| - -#### 7.3.1.3 Mapping of O-RAN Assets to CISA ZTMM Pillars - -In the gap analysis process, each asset is mapped to a pillar or a set of pillars in CISA ZTMM. For reference, asset categories are defined in clause 5.1. Table Gap Analysis Methodology-10: illustrates this mapping process. - -**Table Gap Analysis Methodology-10: Mapping of O-RAN Assets and Other Components to Different Pillars** - -| CISA ZTMM Pillar | O-RAN Asset Categories and Other O-RAN Elements | -|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Identity Pillar |

Person entities: users

Non-person entities: An O-RAN asset requesting access to another O-RAN asset should be considered as a non-person entity and should be mapped to the Identity pillar

| -| Devices Pillar |

Hardware infrastructure

Operating system and firmware infrastructure

Virtualization layer infrastructure

| -| Networks Pillar |

Interfaces, including protocol stacks

APIs

| -| Applications Pillar |

Interfaces' functions (terminations)

Services

APIs

| -| Data Pillar | Data | - -NOTE: APIs, as defined by O-RAN, should be tested against both CISA's Networks Pillar and Applications Pillar. - -### 7.3.2 Transversal Functions Gap Analysis - -#### 7.3.2.1 Transversal Functions Data Pillar Analysis - -##### 7.3.2.1.1 Transversal Functions Data Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- All data assets - -##### 7.3.2.1.2 Transversal Functions Data Pillar Gap Analysis - -**Table Transversal Functions Gap Analysis-11: Transversal Functions Data Pillar Gap Analysis** - -| Data ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|--------------------------------------------|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Data inventory management | a) Automated data inventory processes for most data

b) Protections against data loss | Transversal Functions Data Assets | | | | -| | | All data assets | None | Gap | Out of scope for O-RAN.

This is assumed to be an external service that provides inventory and backups. | -| Data categorization | a) Data categorization strategy with defined labels and manual enforcement mechanisms. | Transversal Functions Data Assets | | | | -| | | All data assets | None | Gap | Out of scope for O-RAN.

It is up to the operator to define data categories, data labels, and classification policies. | -| Data availability | a) some data available from redundant, highly available data stores (e.g., cloud) and availability of off-site backups for on-premises data. | Transversal Functions Data Assets | | | | -| | | All data assets | REQ-SEC-SLM-SST-6 | Partial gap | The capability to support backups is within scope of O-RAN. However, how backup is enforced is out of scope.

Ongoing efforts within WG1 [i.36] and WG6 are expected to produce requirements and specifications that may address this function. | - -#### 7.3.2.2 Transversal Functions Identity Pillar - -##### 7.3.2.2.1 Transversal Functions Identity Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-C-02: Near-RT RIC -- ASSET-C-08: O-Cloud (Covers DMS and IMS and their services) -- ASSET-C-09: xApps. -- ASSET-C-10: rApps. -- ASSET-C-12: ML components deploying machine learning such as: ML training and inference hosts, ML applications (xApps, rApps). - -- ASSET-C-12a: PNF NF equipment -- ASSET-C-29: AAL software including software, libraries, drivers -- ASSET-C-30: The hardware accelerator device firmware -- ASSET-C-32: O-RU Host -- ASSET-C-34: DU-Host (Including software). -- ASSET-C-35: DU-Tenant (Including software). -- ASSET-C-36: CU-Host (Including software). -- ASSET-C-37: CU-Tenant (Including software). - -##### 7.3.2.2.2 Transversal Functions Identity Pillar Gap Analysis - -**Table Transversal Functions Gap Analysis-12: Transversal Functions Identity Pillar Gap Analysis** - -| Identity ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Identity stores | Combination of self-managed identity stores and hosted identity store(s) (e.g., cloud or other agency) with minimal integration between the store(s) (e.g., Single Sign- on.). | Transversal Functions Identity Assets | | | | -| | | ASSET-C-02
ASSET-C-09
ASSET-C-10
ASSET-C-12
ASSET-C-12a
ASSET-C-29
ASSET-C-30
ASSET-C-32
ASSET-C-34
ASSET-C-35
ASSET-C-36
ASSET-C-37 | SEC-CTL-PASS-3
REQ-SEC-SLM-DAT-EVT-8 | Partial gap | No requirements specific to identity stores | -| | | ASSET-C-08 | REQ-SEC-OCLOUD-4 | Partial gap | No requirements specific to identity stores | -| Risk Assessments | determines identity risk using manual methods and static rules to support visibility. | Transversal Functions Identity Assets | | | | -| | | All component assets | REQ-SEC-SLM-DDA-1
REQ-SEC-CMF-ANYNF-2
REQ-SEC-CMF-ANYNF-3
REQ-SEC-CMF-ANYNF-8
REQ-SEC-CMF-ANYNF-9 | No gap | Possibly missing requirements, e.g. about implementing a policy and procedure that outlines the use of manual methods and static rules for determining identity risk, would be on the operator | - -#### 7.3.2.3 Transversal Functions Networks Pillar - -##### 7.3.2.3.1 Transversal Functions Networks Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4]: - -- ASSET-C-63: Near-RT RIC APIs -- ZT-OCLOUD-S-X1: O2ims services -- ZT-OCLOUD-S-X2: O2dms services -- ASSET-C-08: O-Cloud (Covers DMS and IMS and their services) -- ASSET-C-14: A1 interface, including protocol stack. -- ASSET-C-16: R1 interface, including protocol stack. -- ASSET-C-22: O1, including protocol stack -- ASSET-C-24: OFH M-Plane, including protocol stack -- ASSET-C-25: OFH CUS-Plane, including protocol stack -- ASSET-C-40: E2 interface, including protocol stack -- ASSET-C-42: Y1 interface, including protocol stack - -##### 7.3.2.3.2 Transversal Functions Networks Pillar Gap Analysis - -**Table Transversal Functions Gap Analysis-13: Transversal Functions Networks Pillar Gap Analysis** - -| Networks ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|------------------------------------|---------------------------------------------------------------------| -| Network Segmentation | begins to deploy network architecture with the isolation of critical workloads, constraining connectivity to least function principles, and a transition toward service-specific interconnections. | Transversal Functions Networks Assets | | | | -| | | ZT-OCLOUD-S-X1: O2ims services
ZT-OCLOUD-S-X2: O2dms services
ASSET-C-08 | REQ-SEC-OCLOUD-ISO-3
REQ-SEC-OCLOUD-ISO-4
REQ-SEC-OCLOUD-ISO-5
REQ-SEC-OCLOUD-ISO-6
REQ-SEC-OCLOUD-SECPOL-7 | No gap | | -| | | ASSET-C-63
ASSET-C-14
ASSET-C-16
ASSET-C-22
ASSET-C-24
ASSET-C-25
ASSET-C-40
ASSET-C-42 | None | No gap | N/A
Network segmentation is beyond the scope of O-RAN interfaces | -| Network Traffic Management | a) establishes application profiles with distinct traffic management features and begins to map all | Transversal Functions Networks Assets | | | | -| | | ASSET-C-08 | REQ-SEC-LCM-SD-1
REQ-SEC-LCM-SD-3
REQ-SEC-SLM-HYP-EVT-1 | Partial gap | Network traffic management not referred specifically | - -| | | | | | | -|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|--------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | applications to these profiles.

b) expands application of static rules to all applications and performs periodic manual audits of application profile assessments. | ASSET-C-63
ASSET-C-14
ASSET-C-16
ASSET-C-22
ASSET-C-24
ASSET-C-25
ASSET-C-40
ASSET-C-42 | None | Gap | Lack of explicitly covering the creation of comprehensive application profiles with distinct traffic management features.

Lack of explicitly requiring mapping all applications to the defined profiles. | -| Network Resilience | begins to configure network capabilities to manage availability demands for additional applications and expand resilience mechanisms for workloads not deemed mission critical. | Transversal Functions Networks Assets | | | | -| | | All assets | REQ-SEC-DOS-1
REQ-SEC-SYS-1
REQ-SEC-TRAN-1 | No gap | | - -#### 7.3.2.4 Transversal Functions Devices Pillar - -##### 7.3.2.4.1 Transversal Functions Devices Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4]: - -- ASSET-C-12a: PNF NF equipment -- ZT-OCLOUD-I-X1: O-Cloud hardware - -##### 7.3.2.4.2 Transversal Functions Devices Pillar Gap Analysis - -**Table Transversal Functions Gap Analysis-14: Transversal Functions Devices Pillar Gap Analysis** - -| Devices ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|---------------------|---------------------------------|--------------------------------------|--------------------------------------------|------------------------------------|----------| -| Policy | Basic Device | Transversal Functions Devices Assets | | | | - -| | | | | | | -|---------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Enforcement and Compliance Monitoring | characteristics visibility. Basic policy enforcement mechanism for managing software configurations or vulnerabilities | ASSET-C-12a
ZT-OCLOUD-I-X1 | REQ-SEC-AAL-4
SEC-CTL-AAL-2
REQ-SEC-TAP-5
REQ-SEC-SLM-NET-EVT-1
REQ-SEC-SLM-GSE-1
REQ-SEC-SLM-GSE-3
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5
REQ-SEC-SLM-GSE-6 | No gap | | -| Asset & Supply Chain Risk Management) | tracks all physical and some virtual assets and manages supply chain risks by establishing policies and control baselines according to federal recommendations using a robust framework, (e.g., NIST SCRM.) | Transversal Functions Devices Assets | | | | -| | | ASSET-C-12a
ZT-OCLOUD-I-X1 | REQ-SEC-ALM-PKG-1
REQ-SEC-ALM-PKG-2
REQ-SEC-ALM-PKG-3
REQ-SEC-ALM-PKG-4
SEC-CTL-ALM-PKG-1
SEC-CTL-ALM-PKG-1A
REQ-SEC-CMF-PNF-1
REQ-SEC-CMF-PNF-2
REQ-SBOM-001
REQ-SBOM-002
REQ-SBOM-007 | Partial gap | Lack of explicit requirements for tracking physical assets.

Limited scope of supply chain risk management, focusing primarily on certificate management and software package protection. | - -### 7.3.3 xApp and Near-RT RIC Gap Analysis - -#### 7.3.3.1 xApp and Near-RT RIC Data Pillar Analysis - -##### 7.3.3.1.1 xApp Data Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-D-15: Application software package -- ASSET-D-23: Patches for vulnerable SW components -- ASSET-D-29: Security event log files. -- ASSET-D-31: Security telemetry from the O-Cloud for detecting threats and anomalies. -- Cryptographic Data: - - ASSET-D-16: X.509 certificates - - ASSET-D-17: Private keys - - ASSET-D-32: Cryptographic keys used during secure boot -- AI/ML Data: - - ASSET-D-25: Training or test data - - ASSET-D-26: The trained ML model - - ASSET-D-27: The ML prediction results built into the model - - ASSET-D-28: The behavior of the ML system - -##### 7.3.3.1.2 Near-RT RIC Data Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] and the WG3 Near-RT RIC Architecture [i.23] are as follows: - -- ASSET-D-39: xApp ID -- ASSET-D-10: Database holding data from xApp applications and E2 Node -- ASSET-D-16: X.509 certificates -- ASSET-D-17: Private Keys -- ASSET-D-23: Patches for vulnerable SW components. -- ASSET-D-25: Training or test data -- ASSET-D-26: The trained ML model -- ASSET-D-27: The ML prediction results built into the model -- ASSET-D-28: The behavior of the ML system -- ASSET-D-29: Security event log files. -- ASSET-D-31: Security telemetry from the O-Cloud for detecting threats and anomalies -- ASSET-D-32: Cryptographic keys used during secure boot -- ASSET-D-07: A1 policies that are provided to the near-RT RIC over the A1 interface -- ASSET-D-08: A1 Enrichment Information -- ASSET-D-30: O-RAN specific several UE IDs -- ASSET-D-20: Credentials (Administrators) - -##### 7.3.3.1.3 Data Pillar Transversal Functions - -The following Data Pillar functions are considered transversal and are covered in 7.3.2: - -- Data inventory management -- Data categorization -- Data availability - -##### 7.3.3.1.4 xApp and Near-RT RIC Data Pillar Gap Analysis - -**Table xApp and Near-RT RIC Gap Analysis-15: xApp and Near-RT RIC Data Pillar Gap Analysis** - -| Data ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|------------------|-----------------------------------------------------------------------------------------|------------------|--------------------------------------------|------------------------------------|---------------------------------------------------------------| -| Data Access | a) Automated data access control | xApp Data Assets | | | | -| | | ASSET-D-15 | REQ-SEC-ALM-PKG-11 | No gap | | -| | b) Elements of least privileges are incorporated with the automated data access control | ASSET-D-23 | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1 | No gap | | -| | | ASSET-D-16 | None | Gap | No action needed. X.509 certs are publicly available | -| | | ASSET-D-17 | REQ-SEC-NEAR-RT-1
REQ-SEC-NEAR-RT-2 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-32 | REQ-SEC-NEAR-RT-1
REQ-SEC-NEAR-RT-2 | No gap | Gap resolved by new requirements added after initial analysis | - -| | | | | | | -|--|--|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------------| -| | | ASSET-D-25
(included in app package) | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1 | No gap | | -| | | ASSET-D-25
(excluded from app package) | REQ-SEC-AIML-6
REQ-SEC-AIML-7 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-26 | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1 | No gap | Initial stage if we consider trained ML model as part of app package | -| | | ASSET-D-27 | REQ-SEC-AIML-1
REQ-SEC-AIML-2 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-28 | REQ-SEC-NEAR-RT-1
REQ-SEC-NEAR-RT-2 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-29 | REQ-SEC-SLM-TESS-6
REQ-SEC-SLM-TESS-7
REQ-SEC-SLM-TESM-1
REQ-SEC-SLM-TESM-3
REQ-SEC-TESR-1
REQ-SEC-TESR-7
REQ-SEC-TESR-9
REQ-SEC-TESR-11
REQ-SEC-SLM-SST-4
REQ-SEC-SLM-STR-2 | No gap | | -| | | ASSET-D-31 | REQ-SEC-SLM-TESS-6
REQ-SEC-SLM-TESS-7
REQ-SEC-SLM-TESM-1
REQ-SEC-SLM-TESM-3
REQ-SEC-TESR-1
REQ-SEC-TESR-7
REQ-SEC-TESR-9
REQ-SEC-TESR-11
REQ-SEC-SLM-SST-4
REQ-SEC-SLM-STR-2 | No gap | | -| | | Near-RT RIC Data Assets | | | | -| | | ASSET-D-16 | None | Gap | No action needed.
X.509 certs are publicly available | -| | | ASSET-D-17 | REQ-SEC-NEAR-RT-1
REQ-SEC-NEAR-RT-2 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-23 | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1 | No gap | | -| | | ASSET-D-25
(included in app package) | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1 | No gap | | - -| | | | | | | -|------|--------------|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------|-------------|------------------------------------------------------------------------------------| -| | | ASSET-D-25
(excluded from app package) | REQ-SEC-AIML-6
REQ-SEC-AIML-7 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-26 | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1 | No gap | | -| | | ASSET-D-27 | REQ-SEC-AIML-1
REQ-SEC-AIML-2 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-28 | REQ-SEC-NEAR-RT-1
REQ-SEC-NEAR-RT-2 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-29 | REQ-SEC-SLM-TESS-6
REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-TE-5
REQ-SEC-TESS-1
REQ-SEC-TESS-7
REQ-SEC-TESS-9
REQ-SEC-TESS-11 | No gap | | -| | | ASSET-D-31 | REQ-SEC-SLM-TESS-6
REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-TE-5
REQ-SEC-TESS-1
REQ-SEC-TESS-7
REQ-SEC-TESS-9
REQ-SEC-TESS-11 | No gap | | -| | | ASSET-D-32 | REQ-SEC-NEAR-RT-1
REQ-SEC-NEAR-RT-2 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-07 | REQ-SEC-NEAR-RT-5
SEC-CTL-NEAR-RT-4 | No gap | | -| | | ASSET-D-08 | REQ-SEC-NEAR-RT-5
SEC-CTL-NEAR-RT-5 | No gap | | -| | | ASSET-D-30 | REQ-SEC-NEAR-RT-1
REQ-SEC-NEAR-RT-2 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-39 | REQ-SEC-XAPP-3 | Partial gap | No action needed.
xAppIDs are part of X.509 certs which are publicly available. | -| | | ASSET-D-10 | REQ-SEC-NEAR-RT-1
REQ-SEC-NEAR-RT-2
SEC-CTL-NEAR-RT-1
SEC-CTL-NEAR-RT-3 | No gap | | -| | | ASSET-D-20 | REQ-SEC-NEAR-RT-1
REQ-SEC-NEAR-RT-2 | No gap | Gap resolved by new requirements added after initial analysis | -| Data | a) Encrypted | xApp Data Assets | | | | - -| | | | | | | -|------------|---------------------------------------------------------------------------------------|-------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------| -| Encryption | data in transit and, where feasible, data at rest. | ASSET-D-15 | REQ-SEC-ALM-PKG-10 | No gap | | -| | | ASSET-D-23 | REQ-SEC-ALM-PKG-10 | No gap | | -| | b) Key management policies and secure encryption keys are beginning to be formalized. | ASSET-D-16 | REQ-SEC-OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-1
REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-2
SEC-CTL-ALM-PKG-2A
SEC-CTL-ALM-PKG-4 | No gap | | -| | | ASSET-D-17 | REQ-SEC-OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-1
REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-2
SEC-CTL-ALM-PKG-2A
SEC-CTL-ALM-PKG-4 | No gap | | -| | | ASSET-D-32 | REQ-SEC-OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-1
REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-2
SEC-CTL-ALM-PKG-2A
SEC-CTL-ALM-PKG-4 | No gap | | -| | | ASSET-D-25
(included in app package) | REQ-SEC-ALM-PKG-10 | No gap | | -| | | ASSET-D-25
(excluded from app package) | REQ-SEC-AIML-5
REQ-SEC-NEAR-RT-12 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-26 | REQ-SEC-ALM-PKG-10 | No gap | If we consider trained ML model as part of app package | -| | | ASSET-D-27 | REQ-SEC-AIML-3
REQ-SEC-NEAR-RT-12 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-28 | REQ-SEC-AIML-5
REQ-SEC-NEAR-RT-12 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-29 | REQ-SEC-SLM-TESM-2
REQ-SEC-SLM-TE-4
REQ-SEC-TESR-6 | No gap | | -| | | ASSET-D-31 | REQ-SEC-SLM-TESM-2
REQ-SEC-SLM-TE-4
REQ-SEC-TESR-6 | No gap | | -| | | Near-RT RIC Data Assets | | | | -| | | ASSET-D-16 | REQ-SEC-OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-1 | No gap | | - -| | | | | | | -|--|--|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------| -| | | | REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-2
SEC-CTL-ALM-PKG-2A
SEC-CTL-ALM-PKG-4 | | | -| | | ASSET-D-17 | REQ-SEC-OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-1
REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-2
SEC-CTL-ALM-PKG-2A
SEC-CTL-ALM-PKG-4 | No gap | | -| | | ASSET-D-23 | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1 | No gap | | -| | | ASSET-D-25
(included in app package) | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1 | No gap | | -| | | ASSET-D-25
(excluded in app package) | REQ-SEC-AIML-5
REQ-SEC-NEAR-RT-12 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-26 | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1 | No gap | | -| | | ASSET-D-27 | REQ-SEC-AIML-3
REQ-SEC-NEAR-RT-12 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-28 | REQ-SEC-AIML-5
REQ-SEC-NEAR-RT-12 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-29 | REQ-SEC-SLM-TESM-2
REQ-SEC-SLM-TE-4

REQ-SEC-TESR-6 | No gap | | -| | | ASSET-D-31 | REQ-SEC-SLM-TESM-2
REQ-SEC-SLM-TE-4
REQ-SEC-TESR-6 | No gap | | -| | | ASSET-D-32 | SEC-CTL-ALM-PKG-4
REQ-SEC-NEAR-RT-12 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-07 | REQ-SEC-A1-1
SEC-CTL-A1-1 | No gap | | -| | | ASSET-D-08 | REQ-SEC-A1-1
SEC-CTL-A1-1 | No gap | | -| | | ASSET-D-30 | REQ-SEC-API-7
SEC-CTL-NEAR-RT-6
REQ-SEC-NEAR-RT-2A
REQ-SEC-NEAR-RT-12 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-39 | None | Gap | No action needed.
xAppIDs are part of | - -| | | | | | | -|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | | X.509 certs which are publicly available. | -| | | ASSET-D-10 | SEC-CTL-NEAR-RT-6
REQ-SEC-NEAR-RT-2A | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-20 | REQ-SEC-NEAR-RT-12 | No gap | Gap resolved by new requirements added after initial analysis | -| Visibility and Analytics Capability | a) Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | xApp Data Assets | | | | -| | | ASSET-D-15
ASSET-D-23
ASSET-D-16
ASSET-D-17
ASSET-D-32
ASSET-D-25 (included in app package)
ASSET-D-25 (excluded from app package)
ASSET-D-26
ASSET-D-27
ASSET-D-28
ASSET-D-29
ASSET-D-31 | REQ-SEC-SLM-DAT-EVT-1
REQ-SEC-SLM-DAT-EVT-2
REQ-SEC-SLM-DAT-EVT-3
REQ-SEC-SLM-DAT-EVT-4
REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5 | Partial gap | Data inventory and data categorization are out of scope for O-RAN specifications.

Creating and providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| | | Near-RT RIC Data Assets | | | | -| | | ASSET-D-16
ASSET-D-17
ASSET-D-23
ASSET-D-25 (included in app package)
ASSET-D-25 (excluded from app package)
ASSET-D-26
ASSET-D-27
ASSET-D-28
ASSET-D-29
ASSET-D-31
ASSET-D-32
ASSET-D-07
ASSET-D-08
ASSET-D-30
ASSET-D-39
ASSET-D-10
ASSET-D-20 | REQ-SEC-SLM-DAT-EVT-1
REQ-SEC-SLM-DAT-EVT-2
REQ-SEC-SLM-DAT-EVT-3
REQ-SEC-SLM-DAT-EVT-4
REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5 | Partial gap | Data inventory and data categorization are out of scope for O-RAN specifications.

Creating and providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration | a) Data lifecycle and security | xApp Data Assets | | | | -| | | ASSET-D-15
ASSET-D-23 | None | Gap | Out of scope, as data | - -| | | | | | | -|------------|----------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|---------------------------------------------------------------------------------------------------| -| Capability | policies (e.g., access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) are automated. | ASSET-D-16
ASSET-D-17
ASSET-D-32
ASSET-D-25 (included in app package)
ASSET-D-25 (excluded from app package)
ASSET-D-26
ASSET-D-27
ASSET-D-28
ASSET-D-29
ASSET-D-31 | | | lifecycle and security policies fall under the operator's responsibilities. | -| | | Near-RT RIC Data Assets | | | | -| | | ASSET-D-16
ASSET-D-17
ASSET-D-23
ASSET-D-25 (included in app package)
ASSET-D-25 (excluded in app package)
ASSET-D-26
ASSET-D-27
ASSET-D-28
ASSET-D-29
ASSET-D-31
ASSET-D-32
ASSET-D-07
ASSET-D-08
ASSET-D-30
ASSET-D-39
ASSET-D-10
ASSET-D-20 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | - -#### 7.3.3.2 xApp and Near-RT RIC Applications and Workloads Pillar Analysis - -##### 7.3.3.2.1 xApp Applications and Workloads Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] and the WG3 Near-RT RIC Architecture [i.23] are as follows: - -- ASSET-C-09: xApps. This includes xApps services. - -##### 7.3.3.2.2 Near-RT RIC Applications and Workloads Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] and the WG3 Near-RT RIC Architecture [i.23] are as follows: - -- ASSET-C-13: A1 termination. This includes A1 related services. -- ASSET-C-41: E2 functions. This includes E2 related services. -- ASSET-C-43: Y1 Functions. This includes Y1 related services. -- Other Services of the Near-RT RIC platform: this includes Management related services, SDL services, Enablement services, and AI/ML workflow services [i.23]. - -##### 7.3.3.2.3 xApp and Near-RT RIC Application and Workloads Pillar Transversal Functions - -- No transversal functions applicable - -##### 7.3.3.2.4 xApp and Near-RT RIC Application and Workloads Pillar Gap Analysis - -**Table xApp and Near-RT RIC Gap Analysis-16: xApp and Near-RT RIC Applications and Workloads Pillar Gap Analysis** - -| App/ Workloads ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|---------------------------------------------------------------------------| -| Application Access (Authorization) | a) Access authorization capabilities utilize contextual information such as identity, device compliance, and other attributes to make decisions on various requests for accessing application assets. | xApp Applications and Workloads Assets | | | | -| | | ASSET-C-09 | REQ-SEC-NEAR-RT-3
REQ-SEC-NEAR-RT-4
SEC-CTL-NEAR-RT-2
SEC-CTL-NEAR-RT-3 | No gap | | -| | | Near-RT RIC Applications and Workloads Assets | | | | -| | b) Authorization is granted per request with expiration. | ASSET-C-13
ASSET-C-41
ASSET-C-43 | REQ-SEC-NEAR-RT-3
REQ-SEC-NEAR-RT-4
REQ-SEC-NEAR-RT-5
SEC-CTL-NEAR-RT-1
SEC-CTL-NEAR-RT-2
SEC-CTL-NEAR-RT-3
SEC-CTL-NEAR-RT-4
SEC-CTL-NEAR-RT-5 | No gap | | -| | | Other Services of the Near-RT RIC platform | REQ-SEC-NEAR-RT-3
REQ-SEC-NEAR-RT-4
SEC-CTL-NEAR-RT-1
SEC-CTL-NEAR-RT-3 | No gap | | -| Application Threat Protections | a) Threat protections is integrated into mission-critical application workflows. | xApp Applications and Workloads Assets | | | | -| | | ASSET-C-09 | REQ-SEC-ALM-SU-2
REQ-SEC-ALM-SU-3 | No gap | | -| | | Near-RT RIC Applications and Workloads Assets | | | | -| | b) Threat protections safeguard applications against known threats and address some application-specific threats. | ASSET-C-13
ASSET-C-41
ASSET-C-43 | REQ-SEC-ALM-SU-2
REQ-SEC-ALM-SU-3 | No gap | | -| | | Other Services of the Near-RT RIC platform | REQ-SEC-ALM-SU-2
REQ-SEC-ALM-SU-3 | No gap | Gap resolved as requirements were identified after initial analysis | -| Accessible Applications | a) Applicable mission-critical applications are available over open public network connections to authorized users as needed. | xApp Applications and Workloads Assets | | | | -| | | ASSET-C-09 | None | Gap | Out of scope for O-RAN

No identified Mission critical applications | -| | | Near-RT RIC Applications and Workloads Assets | | | | -| | | ASSET-C-13 | None | Gap | Out of scope for O- | - -| | | | | | | -|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|-----------------------------------------|--------|----------------------------------------------------------------------------------------------------------------------------------------| -| | | ASSET-C-41
ASSET-C-43 | | | RAN

No identified Mission critical applications | -| | | Other Services of the Near-RT RIC platform | None | Gap | Out of scope for O-RAN

No identified Mission critical applications | -| Secure Application Development and Deployment Workflow (New Function) | a) Infrastructure for development, testing, and production environments (including automation).

b) Formal code deployment mechanisms through CI/CD pipelines. | xApp Applications and Workloads Assets | | | | -| | | ASSET-C-09 | None | Gap | Out of scope for O-RAN

Securing infrastructure for development, testing, and production environments is out of scope for O-RAN. | -| | c) Access controls support least privilege principles. | Near-RT RIC Application and Workloads Assets | | | | -| | | ASSET-C-13
ASSET-C-41
ASSET-C-43 | None | Gap | Out of scope for O-RAN

Securing infrastructure for development, testing, and production environments is out of scope for O-RAN. | -| | | Other Services of the Near-RT RIC platform | None | Gap | Out of scope for O-RAN

Securing infrastructure for development, testing, and production environments is out of scope for O-RAN. | -| Application Security Testing (Formerly Application Security) | a) Utilization of static and dynamic testing methods for security testing.

b) Performance of security testing including manual expert analysis before application deployment. | xApp Applications and Workloads Assets | | | | -| | | ASSET-C-09 | REQ-SEC-ALM-PKG-1
REQ-SEC-ALM-PKG-7b | No gap | Guidance (b) is out of scope for O-RAN. | -| | | Near-RT RIC Applications and Workloads Assets | | | | -| | | ASSET-C-13
ASSET-C-41
ASSET-C-43 | REQ-SEC-ALM-PKG-1
REQ-SEC-ALM-PKG-7b | No gap | Guidance (b) is out of scope for O-RAN. | -| | | Other Services of the Near-RT RIC platform | REQ-SEC-ALM-PKG-1
REQ-SEC-ALM-PKG-7b | No gap | Guidance (b) is out of scope for O-RAN.

Gap resolved as requirements were identified after initial analysis. | - -| | | | | | | -|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|------------------------------------------------------------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Visibility and Analytics Capability | a) Initiate the automation of application profile (e.g., state, health, and performance) and security monitoring processes for improved log collection, aggregation, and analytics. | xApp Applications and Workloads Assets | | | | -| | | ASSET-C-09 | REQ-SEC-SLM-FLD-1
REQ-SEC-SLM-FLD-2
REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-5 | Partial gap |
  • These requirements allow for the inclusion of application profile information in security logs. However, the automation of application profile monitoring processes and analytics is not addressed.
  • Log collection, aggregation, and analytics are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE.
| -| | | Near-RT RIC Applications and Workloads Assets | | | | -| | | ASSET-C-13
ASSET-C-41
ASSET-C-43 | REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-5 | Partial gap |
  • Security log requirements enable generation of security logs, but analysis and automation are not specified.
  • Log collection, aggregation, and analytics are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE.
| -| | | Other Services of the Near-RT RIC platform | REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-TESS-5 | Partial gap |
  • Security log requirements enable generation of security logs, but analysis and automation are not specified.
| - -| | | | | | | -|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------|------|-----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | |
  • Log collection, aggregation, and analytics are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE.
| -| Automation and Orchestration Capability | a) Periodically modifies application configurations, including location and access parameters, to align with pertinent security and performance objectives. | xApp Applications and Workloads Assets | | | | -| | | ASSET-C-09 | None | Gap | Out of scope, as application configuration falls under the operator's responsibilities. | -| | | Near-RT RIC Applications and Workloads Assets | | | | -| | | ASSET-C-13
ASSET-C-41
ASSET-C-43 | None | Gap | Out of scope, as application configuration falls under the operator's responsibilities. | -| | | Other Services of the Near-RT RIC platform | None | Gap | Out of scope, as application configuration falls under the operator's responsibilities. | - -#### 7.3.3.3 xApp and Near-RT RIC Identity Pillar Analysis - -##### 7.3.3.3.1 xApp Identity Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] and the WG3 Near-RT RIC Architecture [i.23] are as follows: - -- ASSET-C-09: xApps. - -##### 7.3.3.3.2 Near-RT RIC Identity Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] and the WG3 Near-RT RIC Architecture [i.23] are as follows: - -- ASSET-C-02: Near-RT RIC - -##### 7.3.3.3.3 Identity Pillar Transversal Functions - -The following identity pillar functions are considered transversal and are covered in 7.3.2: - -- Identity stores. -- Risk assessments. -- Access management. - -##### 7.3.3.3.4 xApp and Near-RT RIC Identity Pillar Gap Analysis - -**Table xApp and Near-RT RIC Gap Analysis-17: xApp and Near-RT RIC Identity Pillar Gap Analysis** - -| Identity ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|-------------------------------------------------------------------------------|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Authentication |

The system authenticates identity using MFA, which may include passwords as one factor and requires validation of multiple entity attributes (e.g., locale or activity).

a) If there is mutual authentication for internal communications, we consider the stage as INITIAL.

b) For internal interfaces, authentication based on credentials alone (certificate, pre-shared key, etc.) can be considered as meeting INITIAL maturity level.

| xApp Identity Pillar Assets | | | | -| | | ASSET-C-09 | REQ-SEC-XAPP-3
REQ-SEC-NEAR-RT-3
SEC-CTL-NEAR-RT-1
SEC-CTL-NEAR-RT-2 | No gap | | -| | | Near-RT RIC Identity Pillar Assets | | | | -| | | ASSET-C-02 | SEC-CTL-NEAR-RT-1
REQ-SEC-NEAR-RT-3
SEC-CTL-NEAR-RT-2 | No gap | | -| Access Management (Authorization) |

The system authorizes access, including for privileged access requests, that expires with automated review.

a) This function applies to APIs and user access.

b) For applications, static role assignments (e.g. role binding of a service account) with ephemeral tokens can be considered as INITIAL stage.

| xApp Identity Pillar Assets | | | | -| | | ASSET-C-09 | SEC-CTL-NEAR-RT-3 | No gap | | -| | | Near-RT RIC Identity Pillar Assets | | | | -| | | ASSET-C-09 | SEC-CTL-NEAR-RT-3 | No gap | | -| Visibility and Analytics Capability |

a) Collecting user and entity activity logs.

b) Performing Routine Analysis:

  • a. Conduct regular manual analysis of the logs.
  • b. Implement some automated analysis,
| xApp Identity Pillar Assets | | | | -| | | ASSET-C-09 | REQ-SEC-SLM-TESS-4 | Partial gap |
  • • Security log requirements enable the generation of security logs, but analysis, automation, and correlation are not specified.
  • • Analysis, automation, and correlation are
| - -| | | | | | | -|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|------------------------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | with limited correlation between different log types. | | | | considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE. | -| | | Near-RT RIC Identity Pillar Assets | | | | -| | | ASSET-C-02 | REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-TESS-4 | Partial gap |
  • Security log requirements enable the generation of security logs, but analysis, automation, and correlation are not specified.
  • Analysis and correlation are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE.
| -| Automation and Orchestration Capability | a) Manually orchestrates privileged and external identities.

b) Automates orchestration of non-privileged users.

c) Automates orchestration of self-managed entities. | xApp Identity Pillar Assets | | | | -| | | ASSET-C-09 | None | Gap | Out of scope, as identities orchestration fall under the operator's responsibilities | -| | | Near-RT RIC Identity Pillar Assets | | | | -| | | ASSET-C-02 | None | Gap | Out of scope, as identities orchestration fall under the operator's responsibilities | - -#### 7.3.3.4 xApp and Near-RT RIC Networks Pillar Analysis - -##### 7.3.3.4.1 xApp Networks Pillar Assets - -- No asset applicable to specific pillar - -##### 7.3.3.4.2 Near-RT RIC Networks Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] and the WG3 Near-RT RIC Architecture [i.23] are as follows: - -- ASSET-C-63: Near-RT RIC APIs. - -##### 7.3.3.4.3 Networks Pillar Transversal Functions - -The following Network pillars functions are considered transversal and are covered in 7.3.2: - -- Network Segmentation. -- Network Traffic Management. -- Network resilience. - -##### 7.3.3.4.4 xApp and Near-RT RIC Networks Pillar Gap Analysis - -**Table xApp and Near-RT RIC Gap Analysis-18: xApp and Near-RT RIC Networks Pillar Gap Analysis** - -| Networks ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|--------------------------------------------|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Traffic Encryption | Encryption for all internal (and preferably external) application traffic, with formalized key management policies and secure encryption keys. | Near-RT RIC Networks Pillar Assets | | | | -| | | ASSET-C-63 | SEC-CTL-NEAR-RT-6
SEC-CTL-NEAR-RT-7 | No gap | | -| Visibility and Analytics Capability | a) Utilize network monitoring capabilities based on known indicators of compromise, including network enumeration, to develop situational awareness in each environment.

b) Commence correlating telemetry across traffic types and environments to facilitate analysis and threat hunting activities. | Near-RT RIC Networks Pillar Assets | | | | -| | | ASSET-C-63 | None | Gap | No requirements for providing network monitoring information.

Providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments.

b) Ensure that all resources have a | Near-RT RIC Networks Pillar Assets | | | | -| | | ASSET-C-63 | None | Gap | Out of scope, network resource configuration and lifecycle management fall under the operator's responsibilities. | - -| | | | | | | -|--|-------------------------------------------------------------|--|--|--|--| -| | defined lifetime determined by policies and telemetry data. | | | | | -|--|-------------------------------------------------------------|--|--|--|--| - -#### 7.3.3.5 xApp and Near-RT RIC Devices Pillar Analysis - -##### 7.3.3.5.1 xApp Devices Pillar Assets - -- No asset applicable to specific pillar - -##### 7.3.3.5.2 Near-RT RIC Devices Pillar Assets - -- No asset applicable to specific pillar - -##### 7.3.3.5.3 Devices Pillar Transversal Functions - -The following devices pillar functions are considered transversal and are covered in 7.3.2: - -- Policy Enforcement and Compliance Monitoring. -- Asset & Supply Chain Risk Management. - -##### 7.3.3.5.4 xApp and Near-RT RIC Devices Pillar Gap Analysis - -- The Devices Pillar is out of scope for the gap analysis. - -### 7.3.4 E2 Interface Gap Analysis - -#### 7.3.4.1 E2 Interface Data Pillar Analysis - -##### 7.3.4.1.1 E2 Interface Data Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-D-09: Data transported over the E2 Interface -- ASSET-D-30: O-RAN specific several UE IDs. -- ASSET-D-16: X.509 certificates. -- ASSET-D-17: Private keys -- ASSET-D-25: Training or test data - -##### 7.3.4.1.2 E2 Interface Data Pillar Gap Analysis - -**Table E2 Interface Gap Analysis-19: E2 Interface Data Pillar Gap Analysis** - -| Data ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|------------------|---------------------------------------------------------------------------------------------------------------------------------|--------------------------|--------------------------------------------|------------------------------------|------------------------------------------| -| Data Access | a) Automated data access control

b) Elements of least privileges are incorporated with the automated data access control | E2 Interface Data Assets | | | | -| | | Asset-D-09 | REQ-SEC-E2-1
SEC-CTL-E2-1 | Partial gap | Authorization control not defined (NOTE) | -| | | Asset-D-16 | REQ-SEC-E2-1
SEC-CTL-E2-1 | Partial gap | Authorization control not defined (NOTE) | -| | | Asset-D-17 | REQ-SEC-E2-1 | Partial gap | Authorization control not | - -| | | | | | | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | SEC-CTL-E2-1 | | defined (NOTE) | -| | | Asset-D-25 | REQ-SEC-E2-1
SEC-CTL-E2-1 | Partial gap | Authorization control not defined (NOTE) | -| | | Asset-D-30 | REQ-SEC-E2-1
SEC-CTL-E2-1 | Partial gap | Authorization control not defined (NOTE) | -| Data Encryption | a) Encrypted data in transit and, where feasible, data at rest.

b) Key management policies and secure encryption keys are beginning to be formalized. | E2 Interface Data Assets | | | | -| | | Asset-D-09 | REQ-SEC-E2-1
SEC-CTL-E2-1 | No gap | Encryption at rest may not be needed. | -| | | Asset-D-16 | REQ-SEC-E2-1
SEC-CTL-E2-1 | No gap | Encryption at rest may not be needed. | -| | | Asset-D-17 | REQ-SEC-E2-1
SEC-CTL-E2-1 | No gap | Encryption at rest may not be needed. | -| | | Asset-D-25 | REQ-SEC-E2-1
SEC-CTL-E2-1 | No gap | Encryption at rest may not be needed. | -| | | Asset-D-30 | REQ-SEC-E2-1
SEC-CTL-E2-1 | No gap | Encryption at rest may not be needed. | -| Visibility and Analytics Capability | a) Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | E2 Interface Data Assets | | | | -| | | Asset-D-09
Asset-D-16
Asset-D-17
Asset-D-25
Asset-D-30 | REQ-SEC-SLM-DAT-EVT-1
REQ-SEC-SLM-DAT-EVT-2
REQ-SEC-SLM-DAT-EVT-3
REQ-SEC-SLM-DAT-EVT-4
REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5 | Partial gap | Data inventory and data categorization are out of scope for O-RAN specifications.

Creating and providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | a) Data lifecycle and security policies (e.g., access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) are automated. | E2 Interface Data Assets | | | | -| | | Asset-D-09 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | Asset-D-16 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | Asset-D-17 | None | Gap | Out of scope, as data lifecycle and security policies fall under the | - -| | | | | | | -|--|--|------------|------|-----|---------------------------------------------------------------------------------------------------| -| | | | | | operator's responsibilities. | -| | | Asset-D-25 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | Asset-D-30 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | - -NOTE: In this case authentication grants authorization and there is no native authorization method for SCTP. - -#### 7.3.4.2 E2 Interface Applications and Workloads Pillar Analysis - -##### 7.3.4.2.1 E2 Interface Applications and Workloads Pillar Assets - -- No asset applicable to specific pillar - -##### 7.3.4.2.2 E2 Interface Applications and Workloads Pillar Gap Analysis - -- No gap analysis applies since there are no assets applicable to specific pillar - -#### 7.3.4.3 E2 Interface Identity Pillar Analysis - -##### 7.3.4.3.1 E2 Interface Identity Pillar Assets - -- No asset applicable to specific pillar - -##### 7.3.4.3.2 E2 Interface Identity Pillar Gap Analysis - -- No gap analysis applies since there are no assets applicable to specific pillar - -#### 7.3.4.4 E2 Interface Networks Pillar Analysis - -##### 7.3.4.4.1 E2 Interface Networks Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] and the WG3 Near-RT RIC Architecture [i.23] are as follows: - -- ASSET-C-40: E2 interface, including protocol stack - -##### 7.3.4.4.2 E2 Interface Networks Pillar Gap Analysis - -**Table E2 Interface Gap Analysis-20: E2 Interface Networks Pillar Gap Analysis** - -| Networks ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|----------------------|------------------------------------------------------------------------------------------------|---------------------------|--------------------------------------------|------------------------------------|----------| -| Traffic Encryption | Encryption for all internal (and preferably external) application traffic, with formalized key | E2 Networks Pillar Assets | | | | -| | | ASSET-C-40 | SEC-CTL-NEAR-RT-7 | No gap | | - -| | | | | | | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|------|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | management policies and secure encryption keys. | | | | | -| Visibility and Analytics Capability | a) Utilize network monitoring capabilities based on known indicators of compromise, including network enumeration, to develop situational awareness in each environment.

b) Commence correlating telemetry across traffic types and environments to facilitate analysis and threat hunting activities. | E2 Networks Pillar Assets | | | | -| | | ASSET-C-40 | None | Gap | No requirements for providing network monitoring information.

Providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments.

b) Ensure that all resources have a defined lifetime determined by policies and telemetry data. | E2 Networks Pillar Assets | | | | -| | | ASSET-C-40 | None | Gap | Out of scope, network resource configuration and lifecycle management fall under the operator's responsibilities. | - -#### 7.3.4.5 E2 Interface Devices Pillar Analysis - -##### 7.3.4.5.1 E2 Interface Devices Pillar Assets - -- No asset applicable to specific pillar - -##### 7.3.4.5.2 E2 Interface Devices Pillar Transversal Functions - -The following devices pillar functions are considered transversal and are covered in 7.3.2: - -- Policy Enforcement and Compliance Monitoring. -- Asset & Supply Chain Risk Management. - -7.3.4.5.3 E2 Interface Devices Pillar Gap Analysis - -- The Devices Pillar is out of scope for the gap analysis. - -7.3.5 Y1 Interface Gap Analysis - -7.3.5.1 Y1 Interface Data Pillar Analysis - -7.3.5.1.1 Y1 Interface Data Pillar Assets - -- Data transported over the Y1 interface - -7.3.5.1.2 Y1 Interface Data Pillar Gap Analysis - -**Table Y1 Interface Gap Analysis-21: Y1 Interface Data Pillar Gap Analysis** - -| Data ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Data Access | a) Automated data access control

b) Elements of least privileges are incorporated with the automated data access control | Y1 Interface Data Assets | | | | -| | | Data Transported over Y1 Interface | REQ-SEC-Y1-2
SEC-CTL-NEAR-RT-10 | No gap | | -| Data Encryption | a) Encrypted data in transit and, where feasible, data at rest.

b) Key management policies and secure encryption keys are beginning to be formalized. | Y1 Interface Data Assets | | | | -| | | Data transported over Y1 Interface | REQ-SEC-Y1-3
SEC-CTL-NEAR-RT-11 | No gap | Encryption at rest may not be needed. | -| Visibility and Analytics Capability | a) Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | Y1 Interface Data Assets | | | | -| | | Data Transported over Y1 Interface | REQ-SEC-SLM-DAT-EVT-1
REQ-SEC-SLM-DAT-EVT-2
REQ-SEC-SLM-DAT-EVT-3
REQ-SEC-SLM-DAT-EVT-4
REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM- | Partial gap | Data inventory and data categorization are out of scope for O-RAN specifications.

Creating and providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN | - -| | | | | | | -|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|-------|-----|---------------------------------------------------------------------------------------------------| -| | | | GSE-5 | | ALLIANCE. | -| Automation and Orchestration Capability | a) Data lifecycle and security policies (e.g., access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) are automated. | Y1 Interface Data Assets | | | | -| | | Data Transported over Y1 Interface | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | - -### 7.3.5.2 Y1 Interface Applications and Workloads Pillar Analysis - -#### 7.3.5.2.1 Y1 Interface Applications and Workloads Pillar Assets - -- No asset applicable to specific pillar - -#### 7.3.5.2.2 Y1 Interface Applications and Workloads Pillar Gap Analysis - -- No gap analysis applies since there are no assets applicable to specific pillar - -### 7.3.5.3 Y1 Interface Identity Pillar Analysis - -#### 7.3.5.3.1 Y1 Interface Identity Pillar Assets - -- No asset applicable to specific pillar - -#### 7.3.5.3.2 Y1 Interface Identity Pillar Gap Analysis - -- No gap analysis applies since there are no assets applicable to specific pillar - -### 7.3.5.4 Y1 Interface Networks Pillar Analysis - -#### 7.3.5.4.1 Y1 Interface Networks Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] and the WG3 Near-RT RIC Architecture [i.23] are as follows: - -- ASSET-C-42: Y1 interface, including protocol stack - -#### 7.3.5.4.2 Y1 Interface Networks Pillar Gap Analysis - -**Table Y1 Interface Gap Analysis-22: Y1 Interface Networks Pillar Gap Analysis** - -| Networks ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|----------------------|------------------------------------------------------------------------------------------------------------------------|---------------------------|--------------------------------------------|------------------------------------|----------| -| Traffic Encryption | Encryption for all internal (and preferably external) application traffic, with formalized key management policies and | Y1 Networks Pillar Assets | | | | -| | | ASSET-C-42 | REQ-SEC-Y1-3 SEC-CTL-NEAR-RT-11 | No gap | | - -| | | | | | | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|------|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | secure encryption keys. | | | | | -| Visibility and Analytics Capability | a) Utilize network monitoring capabilities based on known indicators of compromise, including network enumeration, to develop situational awareness in each environment.

b) Commence correlating telemetry across traffic types and environments to facilitate analysis and threat hunting activities. | Y1 Networks Pillar Assets | | | | -| | | ASSET-C-42 | None | Gap | No requirements for providing network monitoring information.

Providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments.

b) Ensure that all resources have a defined lifetime determined by policies and telemetry data. | Y1 Networks Pillar Assets | | | | -| | | ASSET-C-42 | None | Gap | Out of scope, network resource configuration and lifecycle management fall under the operator's responsibilities. | - -### 7.3.5.5 Y1 Interface Devices Pillar Analysis - -#### 7.3.5.5.1 Y1 Interface Devices Pillar Assets - -- No asset applicable to specific pillar - -#### 7.3.5.5.2 Y1 Interface Devices Pillar Transversal Functions - -The following devices pillar functions are considered transversal and are covered in 7.3.2: - -- Policy Enforcement and Compliance Monitoring. -- Asset & Supply Chain Risk Management. - -#### 7.3.5.5.3 Y1 Interface Devices Pillar Gap Analysis - -- The Devices Pillar is out of scope for the gap analysis. - -### 7.3.6 rApp and Non-RT RIC Gap Analysis - -#### 7.3.6.1 rApp and Non-RT RIC Data Pillar Analysis - -##### 7.3.6.1.1 rApp Data Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-D-16: X.509 certificates. -- ASSET-D-17: Private keys -- ASSET-D-18: O-RAN components associated and configuration data. -- ASSET-D-20: Credentials (Administrators). -- ASSET-D-23: Patches for vulnerable SW components. -- ASSET-D-25: Training or test data -- ASSET-D-26: The trained ML model -- ASSET-D-27: The ML prediction results built into the model. -- ASSET-D-28: The behavior of the ML system -- ASSET-D-29: Security event log files. - -##### 7.3.6.1.2 Non-RT RIC Data Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-D-03: Critical Management-Plane data transported over the O1 interface. -- ASSET-D-07: A1 policies that are provided to the near-RT RIC over the A1 interface to guide the RAN performance towards the overall goal expressed in RAN Intent. -- ASSET-D-08: A1 Enrichment Information that is collected or derived at SMO/non-RT RIC either from non-network data sources or from network functions themselves and provided over the A1 interface to be utilized by near-RT RIC, e.g. an ML model, to improve its performance. Discovery and request of A1 Enrichment Information from near-RT RIC to non-RT RIC. External Enrichment Information that is provided by an O-RAN external information source to near-RT RIC over A1. -- ASSET-D-16: X.509 certificates. -- ASSET-D-17: Private keys -- ASSET-D-18: O-RAN components associated and configuration data. -- ASSET-D-20: Credentials (Administrators). -- ASSET-D-23: Patches for vulnerable SW components. -- ASSET-D-24: NETCONF Configuration Access Control Model datastores -- ASSET-D-25: Training or test data -- ASSET-D-26: The trained ML model -- ASSET-D-27: The ML prediction results built into the model. -- ASSET-D-28: The behavior of the ML system -- ASSET-D-29: Security event log files. -- ASSET-D-30: O-RAN specific UE IDs. -- ASSET-D-40: ML models that have not been trained yet, i.e., Initial Models and their associated learning algorithm. - -##### 7.3.6.1.3 rApp and Non-RT RIC Data Pillar Gap Analysis - -**Table rApp and Non-RT RIC Gap Analysis-23: rApp and Non-RT RIC Data Pillar Gap Analysis** - -| Data ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|------------------|----------------------------------|------------------|--------------------------------------------|------------------------------------|--------------------------------------------| -| Data Access | a) Automated data access control | rApp Data Assets | | | | -| | | ASSET-D-16 | None | Gap | No action needed. X.509 certs are publicly | - -| | | | | | -|-----------------------------------------------------------------------------------------|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------| -| b) Elements of least privileges are incorporated with the automated data access control | | | | available | -| | ASSET-D-17 | REQ-SEC-NonRTRIC-15
REQ-SEC-NonRTRIC-16
REQ-SEC-NonRTRIC-17
REQ-SEC-NonRTRIC-18 | No gap | Gap resolved by new requirements added after initial analysis | -| | ASSET-D-18 | REQ-SEC-NonRTRIC-15
REQ-SEC-NonRTRIC-16
REQ-SEC-NonRTRIC-17
REQ-SEC-NonRTRIC-18 | No gap | Gap resolved by new requirements added after initial analysis | -| | ASSET-D-20 | REQ-SEC-NonRTRIC-15
REQ-SEC-NonRTRIC-16
REQ-SEC-NonRTRIC-17
REQ-SEC-NonRTRIC-18 | No gap | Gap resolved by new requirements added after initial analysis | -| | ASSET-D-23 | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1
SEC-CTL-ALM-PKG-2 | No gap | | -| | ASSET-D-25
(included in app package) | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1
SEC-CTL-ALM-PKG-2 | No gap | | -| | ASSET-D-25
(excluded from app package) | REQ-SEC-AIML-6
REQ-SEC-AIML-7 | No gap | Gap resolved by new requirements added after initial analysis | -| | ASSET-D-26 | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1
SEC-CTL-ALM-PKG-2 | No gap | | -| | ASSET-D-27 | REQ-SEC-AIML-1
REQ-SEC-AIML-2 | No gap | Gap resolved by new requirements added after initial analysis | -| | ASSET-D-28 | REQ-SEC-NonRTRIC-18 | No gap | Gap resolved by new requirements added after initial analysis | -| | ASSET-D-29 | REQ-SEC-SLM-TESS-6
REQ-SEC-SLM-TESS-7
REQ-SEC-SLM-TESS-1
REQ-SEC-SLM-TESS-3
REQ-SEC-TESS-1
REQ-SEC-TESS-7
REQ-SEC-TESS-9
REQ-SEC-TESS-11
REQ-SEC-SLM-SST-4
REQ-SEC-SLM-STR-2 | No gap | | -| | Non-RT RIC Data Assets | | | | -| | O1

ASSET-D-03 | REQ-SEC-NonRTRIC-1
REQ-SEC-SMO-1
REQ-SEC-SMO-2
REQ-SEC-SMO-3
REQ-SEC-SMO-Internal-2
REQ-SEC-OCLOUD-SS-1 | No gap | Gap resolved by new requirements added after initial analysis | - -| | | | | | | -|--|--|------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------| -| | | O-RAN Management Plane Specification clauses 5.4 & 6.5 [i.26]
REQ-SEC-SharedORU-1
REQ-SEC-SharedORU-2
REQ-SEC-NonRTRIC-19 | | | | -| | | A1 policies
ASSET-D-07 | REQ-SEC-NonRTRIC-1
SEC-CTL-NonRTRIC-2
REQ-SEC-NonRTRIC-19 | No gap | Gap resolved by new requirements added after initial analysis | -| | | A1 Enrichment Information
ASSET-D-08 | REQ-SEC-NonRTRIC-1
SEC-CTL-NonRTRIC-1
REQ-SEC-NonRTRIC-19 | No gap | Gap resolved by new requirements added after initial analysis | -| | | X.509 Certificates
ASSET-D-16 | REQ-SEC-NonRTRIC-19 | No gap | Gap resolved by new requirements added after initial analysis | -| | | Private Keys
ASSET-D-17 | REQ-SEC-OCLOUD-1
REQ-SEC-OCLOUD-2
REQ-SEC-OCloud-ISO-1
REQ-SEC-OCloud-ISO-3
REQ-SEC-OCloud-ISO-7
REQ-SEC-OCLOUD-SS-1 | No gap | | -| | | Architecture Element Data
ASSET-D-18
ASSET-D-20 | REQ-SEC-NonRTRIC-1
REQ-SEC-SMO-1
REQ-SEC-SMO-2
REQ-SEC-SMO-3
REQ-TLS-FUN-2
REQ-TLS-FUN-4
REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11
REQ-SEC-SMO-Internal-2
REQ-SEC-NFO-FOCOM-3
REQ-SEC-NFO-FOCOM-4
REQ-SEC-NFO-FOCOM-5
REQ-SEC-OCLOUD-SS-1
REQ-SEC-NonRTRIC-19 | No gap | Gap resolved by new requirements added after initial analysis | -| | | SW Packages
ASSET-D-23 | REQ-SEC-NonRTRIC-1
REQ-SEC-SMO-1
REQ-SEC-SMO-2
REQ-SEC-SMO-3
REQ-TLS-FUN-2
REQ-TLS-FUN-4
REQ-NAC-FUN-1 | No gap | Gap resolved by new requirements added after initial analysis | - -| | | | | | | -|--|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------| -| | | REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11
REQ-SEC-SMO-Internal-2
REQ-SEC-NFO-FOCOM-3
REQ-SEC-NFO-FOCOM-4
REQ-SEC-NFO-FOCOM-5
REQ-SEC-OCLOUD-SS-1
REQ-SEC-ALM-PKG-10
REQ-SEC-ALM-PKG-11
REQ-SEC-NonRTRIC-19 | | | | -| | | Non-O-Cloud Architecture Element Data

ASSET-D-24
ASSET-D-28
ASSET-D-30
ASSET-D-40 | REQ-SEC-NonRTRIC-1
REQ-SEC-SMO-1
REQ-SEC-SMO-2
REQ-SEC-SMO-3
REQ-TLS-FUN-2
REQ-TLS-FUN-4
REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11
REQ-SEC-SMO-Internal-1
REC-SEC-OCLOUD-SS-1
REQ-SEC-NonRTRIC-19 | No gap | Gap resolved by new requirements added after initial analysis | -| | | AI/ML

ASSET-D-25 | REQ-SEC-NonRTRIC-1
REQ-SEC-SMO-1
REQ-SEC-SMO-2
REQ-SEC-SMO-3
REQ-TLS-FUN-2
REQ-TLS-FUN-4
REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11
REQ-SEC-SMO-Internal-1 | No gap | Gap resolved by new requirements added after initial analysis | - -| | | | | | | -|-----------------|-----------------------------------------------------------------|----------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|---------------------------------------------------------------| -| | | | REC-SEC-OCLOUD-SS-1
REQ-SEC-AIML-6
REQ-SEC-AIML-7 | | | -| | | AI/ML

ASSET-D-26
ASSET-D-27 | REQ-SEC-NonRTRIC-1
REQ-SEC-SMO-1
REQ-SEC-SMO-2
REQ-SEC-SMO-3
REQ-TLS-FUN-2
REQ-TLS-FUN-4
REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11
REQ-SEC-SMO-Internal-1
REC-SEC-OCLOUD-SS-1
REQ-SEC-AIML-1
REQ-SEC-AIML-2 | No gap | Gap resolved by new requirements added after initial analysis | -| | | Log Files

ASSET-D-29 | REQ-SEC-NonRTRIC-1
REQ-SEC-SMO-1
REQ-SEC-SMO-2
REQ-SEC-SMO-3
REQ-TLS-FUN-2
REQ-TLS-FUN-4
REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11
REQ-SEC-SMO-Internal-2
REQ-SEC-SMO-External-2
REQ-SEC-NFO-FOCOM-3
REQ-SEC-NFO-FOCOM-4
REQ-SEC-NFO-FOCOM-5
REQ-SEC-OCLOUD-SS-1
REQ-SEC-NonRTRIC-19 | No gap | Gap resolved by new requirements added after initial analysis | -| Data Encryption | a) Encrypted data in transit and, where feasible, data at rest. | rApp Data Assets | | | | -| | | ASSET-D-16 | REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-2 | No gap | | -| | | ASSET-D-17 | REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-2 | No gap | | - -| | | | | | -|--|-------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------| -| | | SEC-CTL-ALM-PKG-4 | | | -| | ASSET-D-18 | REQ-SEC-ALM-PKG-13
REQ-SEC-NonRTRIC-14 | No gap | Gap resolved by new requirements added after initial analysis | -| | ASSET-D-20 | REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-2 | No gap | | -| | ASSET-D-23 | REQ-SEC-ALM-PKG-10
SEC-CTL-ALM-PKG-1 | No gap | | -| | ASSET-D-25
(included in app package) | REQ-SEC-ALM-PKG-10
SEC-CTL-ALM-PKG-1 | No gap | | -| | ASSET-D-25
(excluded from app package) | REQ-SEC-NonRTRIC-14
REQ-SEC-SMO-Internal-1 | No gap | Gap resolved by new requirements added after initial analysis. | -| | ASSET-D-26 | REQ-SEC-ALM-PKG-10
SEC-CTL-ALM-PKG-1 | No gap | If we consider trained ML model as part of app package | -| | ASSET-D-27 | REQ-SEC-NonRTRIC-14
REQ-SEC-SMO-Internal-1 | No gap | Gap resolved by new requirements added after initial analysis. | -| | ASSET-D-28 | REQ-SEC-NonRTRIC-14
REQ-SEC-SMO-Internal-1 | No gap | Gap resolved by new requirements added after initial analysis. | -| | ASSET-D-29 | REQ-SEC-SLM-TESM-2
REQ-SEC-TESR-6
REQ-SEC-SLM-SST-2
REQ-SEC-SLM-STR-1
SEC-CTL-SLM-SST-2 | No gap | | -| | Non-RT RIC Data Assets | | | | -| | O1
ASSET-D-03 | REQ-SEC-SMO-Internal-1
REQ-SEC-OCLOUD-SS-1
REQ-SEC-SMO-8
REQ-SEC-SMOS-5 | No gap | Gap resolved by new requirements added after initial analysis | -| | A1 policies
ASSET-D-07 | REQ-SEC-SMO-Internal-1
REQ-SEC-OCLOUD-SS-1
REQ-SEC-SMO-8
REQ-SEC-SMOS-5 | No gap | Gap resolved by new requirements added after initial analysis | -| | A1 Enrichment Information
ASSET-D-08 | REQ-SEC-SMO-Internal-1
REQ-SEC-OCLOUD-SS-1
REQ-SEC-SMO-8
REQ-SEC-SMOS-5 | No gap | Gap resolved by new requirements added after initial analysis | -| | Data not used by NFO/FOCOM
ASSET-D-16
ASSET-D-17
ASSET-D-24
ASSET-D-25 | REQ-SEC-SMO-Internal-1
REQ-SEC-OCLOUD-SS-1
REQ-SEC-SMO-8
REQ-SEC-SMOS-5 | No gap | Gap resolved by new requirements added after initial analysis | -| | b) Key management policies and secure encryption keys are beginning to be formalized. | | | | - -| | | | | | | -|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | ASSET-D-26
ASSET-D-27
ASSET-D-28
ASSET-D-30
ASSET-D-40 | | | | -| | | Data used by NFO/FOCOM

ASSET-D-18
ASSET-D-20
ASSET-D-29 | REQ-SEC-SMO-Internal-1
REQ-SEC-NFO-FOCOM-1
REQ-SEC-OCLOUD-SS-1
REQ-SEC-SMO-8
REQ-SEC-SMOS-5 | No gap | Gap resolved by new requirements added after initial analysis | -| | | SW Packages

ASSET-D-23 | REQ-SEC-SMO-Internal-1
REQ-SEC-OCLOUD-SS-1
REQ-SEC-ALM-PKG-10
REQ-SEC-ALM-PKG-11
REQ-SEC-SMO-8
REQ-SEC-SMOS-5 | No gap | Gap resolved by new requirements added after initial analysis | -| Visibility and Analytics Capability | a) Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | rApp Data Assets | | | | -| | | ASSET-D-16
ASSET-D-17
ASSET-D-18
ASSET-D-20
ASSET-D-23
ASSET-D-25
ASSET-D-26
ASSET-D-27
ASSET-D-28
ASSET-D-29 | REQ-SEC-SLM-DAT-EVT-1
REQ-SEC-SLM-DAT-EVT-2
REQ-SEC-SLM-DAT-EVT-3
REQ-SEC-SLM-DAT-EVT-4
REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5 | Partial gap | Data inventory and data categorization are out of scope for O-RAN specifications.

Creating and providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| | | Non-RT RIC Data Assets | | | | -| | | ASSET-D-03
ASSET-D-07
ASSET-D-08
ASSET-D-16
ASSET-D-17
ASSET-D-18
ASSET-D-20
ASSET-D-23
ASSET-D-24
ASSET-D-25
ASSET-D-26
ASSET-D-27
ASSET-D-28
ASSET-D-29
ASSET-D-30 | REQ-SEC-SLM-DAT-EVT-1
REQ-SEC-SLM-DAT-EVT-2
REQ-SEC-SLM-DAT-EVT-3
REQ-SEC-SLM-DAT-EVT-4
REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5 | Partial gap | Data inventory and data categorization are out of scope for O-RAN specifications.

Creating and providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN | - -| | | | | | | -|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|---------------------------------------------------------------------------------------------------| -| | | ASSET-D-40 | | | ALLIANCE. | -| Automation and Orchestration Capability | a) Data lifecycle and security policies (e.g., access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) are automated. | rApp Data Assets | | | | -| | | ASSET-D-16
ASSET-D-17
ASSET-D-18
ASSET-D-20
ASSET-D-23
ASSET-D-25
ASSET-D-26
ASSET-D-27
ASSET-D-28
ASSET-D-29 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | Non-RT RIC Data Assets | | | | -| | | ASSET-D-03
ASSET-D-07
ASSET-D-08
ASSET-D-16
ASSET-D-17
ASSET-D-18
ASSET-D-20
ASSET-D-23
ASSET-D-24
ASSET-D-25
ASSET-D-26
ASSET-D-27
ASSET-D-28
ASSET-D-29
ASSET-D-30
ASSET-D-40 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | - -### 7.3.6.2 rApp and Non-RT RIC Applications and Workloads Pillar Analysis - -#### 7.3.6.2.1 rApp Applications and Workloads Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-C-10: rApps. -- ASSET-C-12: ML components deploying machine learning such as: ML training and inference hosts, ML applications (xApps, rApps). - -#### 7.3.6.2.2 Non-RT RIC Applications and Workloads Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-C-13: A1 termination. -- ASSET-C-15: R1 termination. -- ASSET-C-20: A1 Functions. -- ASSET-C-47: rApp Management. -- ASSET-C-48: R1 Services. -- ASSET-C-55: A1 Policy Management. -- ASSET-C-56: A1 E1 Management. - -## 7.3.6.2.3 rApp and Non-RT Applications and Workloads Pillar Gap Analysis - -**Table rApp and Non-RT RIC Gap Analysis-24: rApp and Non-RT RIC Applications and Workloads Pillar Gap Analysis** - -| Application and Workloads ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------| -| Application Access (Authorization) | a) Access authorization capabilities utilize contextual information such as identity, device compliance, and other attributes to make decisions on various requests for accessing application assets.

b) Authorization is granted per request with expiration. | rApps Application and Workloads Assets | | | | -| | | ASSET-C-10 | REQ-SEC-AUTHZ-2 | Partial gap | Gap partially resolved by new requirements added after initial analysis.

Contextual information is out of scope for O-RAN. | -| | | ASSET-C-12 | REQ-SEC-AUTHZ-2 | Partial gap | Gap partially resolved by new requirements added after initial analysis.

Contextual information is out of scope for O-RAN. | -| | | Non-RT RIC Application and Workloads Assets | | | | -| | | A1

ASSET-C-13
ASSET-C-20
ASSET-C-55
ASSET-C-56 | REQ-SEC-A1-1
REQ-SEC-A1-2
REQ-SEC-A1-3
REQ-SEC-NonRTRIC-1
REQ-SEC-AUTHZ-2 | Partial gap | Contextual information is out of scope for O-RAN. | -| | | R1

ASSET-C-15
ASSET-C-47 | REQ-SEC-R1-1
REQ-SEC-R1-2
REQ-SEC-R1-3
REQ-SEC-NonRTRIC-1
REQ-SEC-NonRTRIC-2
REQ-SEC-NonRTRIC-3
REQ-SEC-NonRTRIC-8
REQ-SEC-AUTHZ-2 | Partial gap | Contextual information is out of scope for O-RAN. | -| | | ASSET-C-48 | REQ-SEC-R1-1
REQ-SEC-R1-2
REQ-SEC-R1-3
REQ-SEC-NonRTRIC-1
REQ-SEC-NonRTRIC-2
REQ-SEC-NonRTRIC-3
REQ-SEC-NonRTRIC-8
REQ-SEC-AUTHZ-2 | Partial gap | Gap resolved partially by new requirements added after initial analysis.

Contextual information is out | - -| | | | | | | -|-----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|--------------------------------------|--------|---------------------------------------------------------------------------------------------------------------------------------| -| | | | | | of scope for O-RAN. | -| Application Threat Protections | a) Threat protections is integrated into mission-critical application workflows. | rApps Application and Workloads Assets | | | | -| | | ASSET-C-10 | REQ-SEC-ALM-SU-2
REQ-SEC-ALM-SU-3 | No gap | | -| | | ASSET-C-12 | REQ-SEC-ALM-SU-2
REQ-SEC-ALM-SU-3 | No gap | | -| | b) Threat protections safeguard applications against known threats and address some application-specific threats. | Non-RT RIC Application and Workloads Assets | | | | -| | | ASSET-C-13
ASSET-C-15
ASSET-C-20
ASSET-C-47
ASSET-C-48
ASSET-C-55
ASSET-C-56 | REQ-SEC-ALM-SU-2
REQ-SEC-ALM-SU-3 | No gap | | -| Accessible Applications | a) Applicable mission-critical applications are available over open public network connections to authorized users as needed. | rApps Application and Workloads Assets | | | | -| | | ASSET-C-10 | None | Gap | Out of scope for O-RAN

No identified Mission critical applications. | -| | | ASSET-C-12 | None | Gap | Out of scope for O-RAN

No identified Mission critical applications. | -| | | Non-RT RIC Application and Workloads Assets | | | | -| | | ASSET-C-13
ASSET-C-15
ASSET-C-20
ASSET-C-47
ASSET-C-48
ASSET-C-55
ASSET-C-56 | None | Gap | Out of scope for O-RAN

No identified Mission critical applications | -| Secure Application Development and Deployment Workflow (New Function) | a) Infrastructure for development, testing, and production environments (including automation).

b) Formal code deployment mechanisms through CI/CD pipelines. | rApps Application and Workloads Assets | | | | -| | | ASSET-C-10 | None | Gap | Out of scope for O-RAN

Securing infrastructure for development, testing, and production environments is out of scope for | - -| | | | | | | -|--------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|----------------------------------------------------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------| -| | c) Access controls support least privilege principles. | | | | O-RAN. | -| | | ASSET-C-12 | None | Gap | Out of scope for O-RAN

Securing infrastructure for development, testing, and production environments is out of scope for O-RAN. | -| | | Non-RT RIC Application and Workloads Assets | | | | -| | | ASSET-C-13
ASSET-C-15
ASSET-C-20
ASSET-C-47
ASSET-C-48
ASSET-C-55
ASSET-C-56 | None | Gap | Out of scope for O-RAN

Securing infrastructure for development, testing, and production environments is out of scope for O-RAN. | -| Application Security Testing (Formerly Application Security) | a) Utilization of static and dynamic testing methods for security testing. | rApps Applications and Workloads Assets | | | | -| | | ASSET-C-10 | REQ-SEC-ALM-PKG-1
REQ-SEC-ALM-PKG-7b | No gap | Guidance (b) is out of scope for O-RAN. | -| | b) Performance of security testing including manual expert analysis before application deployment. | ASSET-C-12 | REQ-SEC-ALM-PKG-1
REQ-SEC-ALM-PKG-7b | No gap | Guidance (b) is out of scope for O-RAN. | -| | | Non-RT RIC Application and Workloads Assets | | | | -| | | ASSET-C-13
ASSET-C-15
ASSET-C-20
ASSET-C-47
ASSET-C-48
ASSET-C-55
ASSET-C-56 | REQ-SEC-ALM-PKG-1
REQ-SEC-ALM-PKG-7b | No gap | Guidance (b) is out of scope for O-RAN. | -| Visibility and Analytics Capability | a) Initiate the automation of application profile (e.g., state, health, and performance) and security monitoring processes for improved log collection, aggregation, and | rApp Applications and Workloads Assets | | | | -| | | ASSET-C-10
ASSET-C-12 | REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-5 | Partial gap | Including application profile information in security logs is in scope and covered by existing requirements. Log aggregation and analytics are | - -| | | | | | | -|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|----------------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | analytics. | | | | considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| | | Non-RT RIC Applications and Workloads Assets | | | | -| | | ASSET-C-13
ASSET-C-15
ASSET-C-20
ASSET-C-47
ASSET-C-48
ASSET-C-55
ASSET-C-56 | REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-5 | Partial gap | Including application profile information in security logs is in scope and covered by existing requirements. Log aggregation and analytics are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | a) Periodically modifies application configurations, including location and access parameters, to align with pertinent security and performance objectives. | rApp Applications and Workloads Assets | | | | -| | | ASSET-C-10
ASSET-C-12 | None | Gap | Out of scope, as application configuration falls under the operator's responsibilities. | -| | | Non-RT RIC Applications and Workloads Assets | | | | -| | | ASSET-C-13
ASSET-C-15
ASSET-C-20
ASSET-C-47
ASSET-C-48
ASSET-C-55
ASSET-C-56 | None | Gap | Out of scope, as application configuration falls under the operator's responsibilities. | - -### 7.3.6.3 rApp and Non-RT RIC Identity Pillar Analysis - -#### 7.3.6.3.1 rApp Identity Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-C-10: rApps. - -- ASSET-C-12: ML components deploying machine learning such as: ML training and interference hosts, ML applications (xApps, rApps). - -**7.3.6.3.2 Non-RT RIC Identity Pillar Assets** - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-C-13: A1 termination. -- ASSET-C-15: R1 termination. -- ASSET-C-20: A1 Functions. -- ASSET-C-47: rApp Management. -- ASSET-C-48: R1 Services. -- ASSET-C-55: A1 Policy Management. -- ASSET-C-56: A1 E1 Management. - -**7.3.6.3.3 rApp and Non-RT Identity Pillar Gap Analysis** - -**Table rApp and Non-RT RIC Gap Analysis-25: rApp and Non-RT RIC Identity Pillar Gap Analysis** - -| Identity ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|-----------------------------------------------------|------------------------------------|----------------------------------------------------------------| -| Authentication |

The system authenticates identity using MFA, which may include passwords as one factor and requires validation of multiple entity attributes (e.g., locale or activity).

a) If there is mutual authentication for internal communications, we consider the stage as INITIAL.

b) For internal interfaces, authentication based on credentials alone (certificate, pre-shared key, etc.) can be considered as meeting INITIAL maturity level.

| rApp Identity Pillar Assets | | | | -| | | ASSET-C-10 | REQ-SEC-NonRTRIC-7
REQ-SEC-NonRTRIC-20 | No gap | Gap resolved by new requirements added after initial analysis. | -| | | ASSET-C-12 | REQ-SEC-NonRTRIC-7
REQ-SEC-NonRTRIC-20 | No gap | Gap resolved by new requirements added after initial analysis. | -| | | Non-RT RIC Identity Pillar Assets | | | | -| | | rApp Management
ASSET-C-47 | REQ-SEC-SMO-1
REQ-SEC-NonRTRIC-7
REQ-SEC-R1-2 | No gap | | -| | | R1
ASSET-C-15
ASSET-C-48 | REQ-SEC-SMO-1
REQ-SEC-NonRTRIC-7
REQ-SEC-R1-2 | No gap | | -| | | A1
ASSET-C-13
ASSET-C-20
ASSET-C-55
ASSET-C-56 | REQ-SEC-SMO-1
REQ-SEC-A1-2 | No gap | | -| | | rApp Identity Pillar Assets | | | | -| Access | The system | rApp Identity Pillar Assets | | | | - -| | | | | | | -|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------| -| Management (Authorization) | authorizes access, including for privileged access requests, that expires with automated review.

a) This function applies to APIs and user access.

b) For applications, static role assignments (e.g. role binding of a service account) with ephemeral tokens can be considered as INITIAL stage. | ASSET-C-10 | REQ-SEC-NonRTRIC-2
REQ-SEC-NonRTRIC-3
REQ-SEC-NonRTRIC-15
REQ-SEC-NonRTRIC-16
REQ-SEC-NonRTRIC-17
REQ-SEC-NonRTRIC-8
AUTHZ-2
SEC-CTL-NonRTRIC-4
SEC-CTL-NonRTRIC-5
SEC-CTL-NonRTRIC-6
SEC-CTL-NonRTRIC-7 | No gap | Gap resolved by new requirements added after initial analysis. | -| | | ASSET-C-12 | REQ-SEC-NonRTRIC-2
REQ-SEC-NonRTRIC-3
REQ-SEC-NonRTRIC-15
REQ-SEC-NonRTRIC-16
REQ-SEC-NonRTRIC-17
REQ-SEC-AIML-1
REQ-SEC-NonRTRIC-8
REQ-SEC-AUTHZ-2
SEC-CTL-NonRTRIC-4
SEC-CTL-NonRTRIC-5
SEC-CTL-NonRTRIC-6
SEC-CTL-NonRTRIC-7 | No gap | Gap resolved by new requirements added after initial analysis. | -| | | Non-RT RIC Identity Pillar Assets | | | | -| | | rApp Management

ASSET-C-47 | REQ-SEC-SMO-3
REQ-SEC-SMO-4
REQ-SEC-SMO-Internal-2
REQ-SEC-NonRTRIC-1
REQ-SEC-NonRTRIC-2 | No gap | | - -| | | | | | | -|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | REQ-SEC-NonRTRIC-3
REQ-SEC-NonRTRIC-8 | | | -| | | R1

ASSET-C-15
ASSET-C-48 | REQ-SEC-SMO-3
REQ-SEC-SMO-4
REQ-SEC-SMO-Internal-2
REQ-SEC-NonRTRIC-1
REQ-SEC-NonRTRIC-2
REQ-SEC-NonRTRIC-3
REQ-SEC-NonRTRIC-8 | No gap | | -| | | A1

ASSET-C-13
ASSET-C-20
ASSET-C-55
ASSET-C-56 | REQ-SEC-NonRTRIC-1
SEC-CTL-NonRTRIC-1
SEC-CTL-NonRTRIC-2
REQ-SEC-A1-1
REQ-SEC-A1-3 | No gap | | -| Visibility and Analytics Capability | a) Collecting user and entity activity logs.

b) Performing Routine Analysis:

a. Conduct regular manual analysis of the logs.

b. Implement some automated analysis, with limited correlation between different log types. | rApp Identity Pillar Assets | | | | -| | | ASSET-C-10
ASSET-C-12 | REQ-SEC-SLM-TESS-4 | Partial gap | Generation of security logs is in scope and covered by existing security log requirements. Analysis, automation, and correlation are considered out of scope. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| | | Non-RT RIC Identity Pillar Assets | | | | -| | | ASSET-C-13
ASSET-C-15
ASSET-C-20
ASSET-C-47
ASSET-C-48
ASSET-C-55
ASSET-C-56 | REQ-SEC-SLM-TESS-4 | Partial gap | Generation of security logs is in scope and covered by existing security log requirements. Analysis, automation, and correlation are considered out of scope. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | - -| | | | | | | -|-----------------------------------------|-------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|------|-----|--------------------------------------------------------------------------------------| -| Automation and Orchestration Capability | a) Manually orchestrates privileged and external identities. | rApp Identity Pillar Assets | | | | -| | | ASSET-C-10
ASSET-C-12 | None | Gap | Out of scope, as identities orchestration fall under the operator's responsibilities | -| | b) Automates orchestration of non-privileged users.
c) Automates orchestration of self-managed entities. | Non-RT RIC Identity Pillar Assets | | | | -| | | ASSET-C-13
ASSET-C-15
ASSET-C-20
ASSET-C-47
ASSET-C-48
ASSET-C-55
ASSET-C-56 | None | Gap | Out of scope, as identities orchestration fall under the operator's responsibilities | - -### 7.3.6.4 rApp and Non-RT RIC Networks Pillar Analysis - -#### 7.3.6.4.1 rApp Networks Pillar Assets - -- No asset(s) applicable to this specific pillar. - -#### 7.3.6.4.2 Non-RT RIC Networks Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-C-14: A1 interface, including protocol stack -- ASSET-C-16: R1 interface, including protocol stack. -- ASSET-C-62: SMOS Communication - -#### 7.3.6.4.3 rApp and Non-RT RIC Networks Pillar Gap Analysis - -**Table rApp and Non-RT RIC Gap Analysis-26: rApp and Non-RT RIC Networks Pillar Gap Analysis** - -| Networks ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|----------| -| Traffic Encryption | Encryption for all internal (and preferably external) application traffic, with formalized key management policies and secure encryption keys. | Non-RT RIC Networks Pillar Assets | | | | -| | | ASSET-C-14 | REQ-SEC-A1-1 | No gap | | -| | | ASSET-C-16 | REQ-SEC-R1-1 | No gap | | -| | | ASSET-C-62 | REQ-SEC-SMO-Internal-1
REQ-SEC-SMO-External-1
REQ-SEC-NFO-FOCOM-1
REQ-TLS-FUN-1
REQ-TLS-FUN-3
REQ-SEC-O2-1
O-RAN Management | No gap | | - -| | | | | | | -|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|----------------------------------------------|-----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | Plane Specification clauses 5.4 & 6.5 [i.26] | | | -| Visibility and Analytics Capability |

a) Utilize network monitoring capabilities based on known indicators of compromise, including network enumeration, to develop situational awareness in each environment.

b) Commence correlating telemetry across traffic types and environments to facilitate analysis and threat hunting activities.

| Non-RT RIC Networks Pillar Assets | | | | -| | | ASSET-C-14
ASSET-C-16
ASSET-C-62 | None | Gap |

No requirements for providing network monitoring information.

Providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE.

| -| Automation and Orchestration Capability |

a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments.

b) Ensure that all resources have a defined lifetime determined by policies and telemetry data.

| Non-RT RIC Networks Pillar Assets | | | | -| | | ASSET-C-14
ASSET-C-16
ASSET-C-62 | None | Gap |

Out of scope, network resource configuration and lifecycle management fall under the operator's responsibilities.

| - -### 7.3.6.5 rApp and Non-RT RIC Devices Pillar Analysis - -The Devices Pillar is out of scope for the gap analysis. - -## 7.3.7 A1 Interface Gap Analysis - -### 7.3.7.1 A1 Interface Data Pillar Analysis - -#### 7.3.7.1.1 A1 Interface Data Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-D-07: A1 policies that are provided to the near-RT RIC over the A1 interface. -- ASSET-D-08: A1 Enrichment Information. -- ASSET-D-16: X.509 certificates in O-RAN network such as those used for O-RAN components for authentication, encryption, and signing. -- ASSET-D-17: Security private keys in O-RAN network such as those used for O-RAN components for authentication, encryption, and signing. -- ASSET-D-25: Training or test data and associated labels: data sets collected externally or internally from the Near-RT RIC, O-CU and O-DU and passed to the ML training hosts in a ML system. -- ASSET-D-30: O-RAN specific several UE IDs. - -The gap analysis for ASSET-D-16, ASSET-D-17, and ASSET-D-30 is detailed in clause 7.3.2. - -7.3.7.1.2 A1 Interface Data Pillar Gap Analysis - -**Table A1 Interface Gap Analysis-27: A1 Interface Data Pillar Gap Analysis** - -| Data ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|------------------|---------------------------------------------------------------------------------------------------------------------------------|--------------------------|------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|---------------------------------------------------------------| -| Data Access | a) Automated data access control

b) Elements of least privileges are incorporated with the automated data access control | A1 Interface Data Assets | | | | -| | | ASSET-D-07 | REQ-SEC-NEAR-RT-5
REQ-SEC-NonRTRIC-1
REQ-SEC-A1-2
SEC-CTL-NEAR-RT-4
SEC-CTL-NonRTRIC-2
SEC-CTL-A1-2
SEC-CTL-A1-3 | No gap | | -| | | ASSET-D-08 | REQ-SEC-NEAR-RT-5
REQ-SEC-NonRTRIC-1
REQ-SEC-A1-2
SEC-CTL-NEAR-RT-5
SEC-CTL-NonRTRIC-1
SEC-CTL-A1-2
SEC-CTL-A1-3 | No gap | | -| | | ASSET-D-16 | SEC-CTL-A1-3 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-17 | SEC-CTL-A1-3 | No gap | Gap resolved by new requirements added after initial analysis | -| | | ASSET-D-25 | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1 | No gap | | -| | | ASSET-D-30 | SEC-CTL-A1-3 | No gap | Gap resolved by new requirements added after initial analysis | -| Data Encryption | a) Encrypted data in transit and, where feasible, data at rest. | A1 Interface Data Assets | | | | -| | | ASSET-D-07 | REQ-SEC-A1-1
SEC-CTL-A1-1 | No gap | | - -| | | | | | | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | b) Key management policies and secure encryption keys are beginning to be formalized. | ASSET-D-08 | REQ-SEC-A1-1
SEC-CTL-A1-1 | No gap | | -| | | ASSET-D-16 | REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-2 | No gap | | -| | | ASSET-D-17 | REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-2 | No gap | | -| | | Asset-D-25
(included in app package) | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1 | No gap | | -| | | ASSET-D-25
(excluded from app package) | REQ-SEC-A1-1
SEC-CTL-A1-1 | No gap | Gap resolved as requirements were identified after initial analysis | -| | | ASSET-D-30 | REQ-SEC-A1-1
SEC-CTL-A1-1 | No gap | Gap resolved as requirements were identified after initial analysis | -| Visibility and Analytics Capability | a) Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | A1 Interface Data Assets | | | | -| | | ASSET-D-07
ASSET-D-08
ASSET-D-16
ASSET-D-17
ASSET-D-25
ASSET-D-30 | REQ-SEC-SLM-DAT-EVT-1
REQ-SEC-SLM-DAT-EVT-2
REQ-SEC-SLM-DAT-EVT-3
REQ-SEC-SLM-DAT-EVT-4
REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5 | Partial gap | Data inventory and data categorization are out of scope for O-RAN specifications.

Creating and providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | a) Data lifecycle and security policies (e.g., access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) are automated. | A1 Interface Data Assets | | | | -| | | ASSET-D-07
ASSET-D-08
ASSET-D-16
ASSET-D-17
ASSET-D-25
ASSET-D-30 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | - -7.3.7.2 A1 Interface Applications and Workloads Pillar - -7.3.7.2.1 A1 Interface Applications and Workloads Pillar Assets - -- No asset(s) applicable to this specific pillar. - -7.3.7.3 A1 Interface Identity Pillar Analysis - -7.3.7.3.1 A1 Interface Identity Pillar Assets - -- No asset(s) applicable to this specific pillar. - -7.3.7.4 A1 Interface Networks Pillar Analysis - -7.3.7.4.1 A1 Interface Networks Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-C-14: A1 interface, including protocol stack. - -7.3.7.4.2 A1 Interface Networks Pillar Gap Analysis - -**Table A1 Interface Gap Analysis-28: A1 Interface Networks Pillar Gap Analysis** - -| Networks ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|-------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|--------------------------------------------|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Traffic Encryption | Encryption for all internal (and preferably external) application traffic, with formalized key management policies and secure encryption keys. | A1 Networks Pillar Assets | | | | -| | | ASSET-C-14 | REQ-SEC-A1-1
SEC-CTL-A1-1 | No gap | | -| Visibility and Analytics Capability | a) Utilize network monitoring capabilities based on known indicators of compromise, including network enumeration, to develop situational awareness in each environment.

b) Commence correlating telemetry across traffic types and environments to facilitate analysis and threat hunting activities. | A1 Networks Pillar Assets | | | | -| | | ASSET-C-14 | None | Gap | No requirements for providing network monitoring information.

Providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O- | - -| | | | | | | -|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|------|-----|-------------------------------------------------------------------------------------------------------------------| -| | | | | | RAN ALLIANCE. | -| Automation and Orchestration Capability | a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments.

b) Ensure that all resources have a defined lifetime determined by policies and telemetry data. | A1 Interface Data Assets | | | | -| | | ASSET-C-14 | None | Gap | Out of scope, network resource configuration and lifecycle management fall under the operator's responsibilities. | - -### 7.3.7.5 A1 Interface Devices Pillar Analysis - -#### 7.3.7.5.1 A1 Interface Devices Pillar Assets - -- No asset(s) applicable to this specific pillar. - -### 7.3.8 R1 Interface Gap Analysis - -#### 7.3.8.1 R1 Interface Data Pillar Analysis - -##### 7.3.8.1.1 R1 Interface Data Pillar Assets - -- Data transported over the R1 Interface. - -##### 7.3.8.1.2 R1 Interface Data Pillar Gap Analysis - -**Table R1 Interface Gap Analysis-29: R1 Interface Data Pillar Gap Analysis** - -| Data ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|------------------|---------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|----------| -| Data Access | a) Automated data access control

b) Elements of least privileges are incorporated with the automated data access control | R1 Interface Data Assets | | | | -| | | Data transported over the R1 Interface. | REQ-SEC-NonRTRIC-2
REQ-SEC-NonRTRIC-3
REQ-SEC-R1-2
SEC-CTL-NonRTRIC-4
SEC-CTL-NonRTRIC-5
SEC-CTL-NonRTRIC-6
SEC-CTL-R1-2
SEC-CTL-R1-3 | No gap | | -| Data Encryption | a) Encrypted data in transit and, where feasible, data at rest.
b) Key management | R1 Interface Data Assets | | | | -| | | Data transported | REQ-SEC-R1-1
SEC-CTL-R1-1 | No gap | | - -| | | | | | | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | policies and secure encryption keys are beginning to be formalized. | over the R1 Interface. | | | | -| Visibility and Analytics Capability | a) Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | R1 Interface Data Assets | | | | -| | | Data Transported over the R1 Interface | REQ-SEC-SLM-DAT-EVT-1
REQ-SEC-SLM-DAT-EVT-2
REQ-SEC-SLM-DAT-EVT-3
REQ-SEC-SLM-DAT-EVT-4
REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5 | Partial gap | Data inventory and data categorization are out of scope for O-RAN specifications.

Creating and providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | a) Data lifecycle and security policies (e.g., access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) are automated. | R1 Interface Data Assets | | | | -| | | Data Transported over the R1 Interface | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | - -### 7.3.8.2 R1 Interface Applications and Workloads Pillar Analysis - -#### 7.3.8.2.1 R1 Applications and Workloads Pillar Assets - -- No asset(s) applicable to this specific pillar. - -### 7.3.8.3 R1 Interface Identity Pillar Analysis - -#### 7.3.8.3.1 R1 Identity Pillar Assets - -- No asset(s) applicable to this specific pillar. - -### 7.3.8.4 R1 Interface Networks Pillar Analysis - -#### 7.3.8.4.1 R1 Interface Networks Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-C-16: R1 interface, including protocol stack. - -7.3.8.4.2 R1 Interface Networks Pillar Gap Analysis - -**Table R1 Interface Gap Analysis-30: R1 Interface Networks Pillar Gap Analysis** - -| Networks ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|--------------------------------------------|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Traffic Encryption | Encryption for all internal (and preferably external) application traffic, with formalized key management policies and secure encryption keys. | R1 Networks Pillar Assets | | | | -| | | ASSET-C-16 | REQ-SEC-R1-1
SEC-CTL-R1-1 | No gap | | -| Visibility and Analytics Capability | a) Utilize network monitoring capabilities based on known indicators of compromise, including network enumeration, to develop situational awareness in each environment.

b) Commence correlating telemetry across traffic types and environments to facilitate analysis and threat hunting activities. | R1 Networks Pillar Assets | | | | -| | | ASSET-C-16 | None | Gap | No requirements for providing network monitoring information.

Providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments.

b) Ensure that all resources have a defined lifetime determined by policies and telemetry data. | R1 Networks Pillar Assets | | | | -| | | ASSET-C-16 | None | Gap | Out of scope, network resource configuration and lifecycle management fall under the operator's responsibilities. | - -7.3.8.5 R1 Interface Devices Pillar Analysis - -7.3.8.5.1 R1 Interface Devices Pillar Assets - -- No asset(s) applicable to this specific pillar. - -### 7.3.9 SMO Gap Analysis - -#### 7.3.9.1 SMO Data Pillar Analysis - -##### 7.3.9.1.1 SMO Data Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-D-02: Critical Management-Plane data transported over the Fronthaul interface such as: maintenance and monitoring signals, data collected related to O-RU operations, logs (troubleshooting, trace) -- ASSET-D-03: Critical Management-Plane data transported over the O1 interface -- ASSET-D-12: (1) The Physical Infrastructure (O-Cloud Node Identifier, Pool Identifier, Pool Location Identifier, and Use Identifier) used to create the O-Cloud. (2) The logical Clouds which it provides as interfaces for deployments, and the inventory of deployments (deployment ID and descriptor) on the cloud. (3) O-Cloud ID, IP address, IMS address, the IP address endpoint or url of the SMO and any necessary security keys or passwords for communication using O2. (4) DMS capabilities. (5) O-Cloud (IMS): List of all Resource Pools in the O-Cloud, attributes of a specific O-Cloud, list of all resources of an O-Cloud Pool, attributes of each O-Cloud Resource, list of all DMS. (6) O-Cloud (DMS): list of locations supported for a given location the capabilities supported (e.g. Descriptor types, Technology types, Accelerator types), for a given location the capacity of the location, for a given location the availability of the location. -- ASSET-D-13: -(1) Telemetry information of O-Cloud deployments in the network for analyzing the O-Cloud's state and health, and for delivering on service monitoring goals. It consists of fault, performance and configuration data. (2) Deployment Telemetry to monitor the number of deployment instances an O-Cloud has at that moment and how many were expected, how the on-progress deployment is going, and health checks. Additional Deployment Telemetry metrics like CPU, network, and memory usage can also be collected. (3) Infrastructure Telemetry to monitor the health of the O-Cloud Infrastructure components. Network Operations are interested in discovering if all the components in the O-Cloud Infrastructure are working properly and at what capacity, how many deployments are running on each node, and the resource utilization of the O-Cloud Infrastructure. -- ASSET-D-14: (1) O-Cloud Provisioning information (Affinity, Anti-Affinity, Quorum Diversity Rules, capabilities, capacity and availability.) (2) O-Cloud software management information: catalog of authorized software and its version, list of authorized VNF/CNF, VNF/CNF description files. -- ASSET-D-16: X.509 certificates. -- ASSET-D-17: Private keys -- ASSET-D-18: O-RAN components associated and configuration data. -- ASSET-D-20: Credentials (Administrators) – account information and passwords on SMO. -- ASSET-D-23: Patches for vulnerable SW components -- ASSET-D-24: NETCONF Configuration Access Control Model datastores -- ASSET-D-29: Security event log files generated by O-RAN components -- ASSET-D-30: O-RAN specific UE IDs -- ASSET-D-31: Security telemetry from the O-Cloud for detecting threats and anomalies -- ASSET-D-40: ML models that have not been trained yet, i.e., Initial Models and their associated learning algorithm. - -##### 7.3.9.1.2 SMO Data Pillar Gap Analysis - -**Table SMO Gap Analysis-31: SMO Data Pillar Gap Analysis** - -| Data ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|------------------|---------------------------------|-----------------|--------------------------------------------|------------------------------------|----------| -| Data Access | a) Automated data | SMO Data Assets | | | | - -| | | | | | -|---------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------| -| access control

b) Elements of least privileges are incorporated with the automated data access control | M-Plane

ASSET-D-02
ASSET-D-03 | REQ-SEC-SMO-1
REQ-SEC-SMO-2
REQ-SEC-SMO-3
REQ-SEC-SMO-4
REQ-SEC-SMO-Internal-2
REQ-SEC-SMO-External-2
REQ-SEC-SMO-External-3
REQ-SEC-OCLOUD-SS-1
O-RAN Management Plane Specification clauses 5.4 & 6.5 [i.26]
REQ-SEC-SharedORU-1
REQ-SEC-SharedORU-2
REQ-SEC-AUTHZ-1 | No gap | Gap resolved by new requirements added after initial analysis. | -| | O-Cloud Assets

ASSET-D-12 | REQ-SEC-SMO-1
REQ-SEC-SMO-2
REQ-SEC-SMO-3
REQ-SEC-SMO-4
REQ-SEC-SMO-Internal-2
REQ-SEC-SMO-External-2
REQ-SEC-SMO-External-3
REQ-SEC-OCLOUD-SS-1
REQ-SEC-AUTHZ-1 | No gap | Gap resolved by new requirements added after initial analysis. | -| | O-Cloud Telemetry & Provisioning

ASSET-D-13
ASSET-D-14 | REQ-SEC-SMO-1
REQ-SEC-SMO-2
REQ-SEC-SMO-3
REQ-SEC-SMO-4
REQ-SEC-SMO-Internal-2
REQ-SEC-SMO-External-2
REQ-SEC-SMO-External-3
REQ-SEC-NFO-FOCOM-3
REQ-SEC-NFO-FOCOM-4
REQ-SEC-NFO-FOCOM-5
REQ-SEC-OCLOUD-SS-1
REQ-SEC-AUTHZ-1 | No gap | Gap resolved by new requirements added after initial analysis. | -| | X.509 Certificates

ASSET-D-16 | REQ-SEC-SMO-1
REQ-SEC-SMO-2
REQ-SEC-SMO-3
REQ-SEC-SMO-4
REQ-SEC-SMO-Internal-2
REQ-SEC-SMO-External-2
REQ-SEC-SMO-External-3
REQ-SEC-OCLOUD-SS-1 | No gap | No action needed. X.509 certs are publicly available | -| | Private Keys

ASSET-D-17 | REQ-SEC-OCLOUD-1
REQ-SEC-OCLOUD-2
REQ-SEC-OCloud-ISO-1
REQ-SEC-OCloud-ISO-3
REQ-SEC-OCloud-ISO-7
REQ-SEC-OCLOUD-SS-1 | No gap | | -| | Architecture Element Data

ASSET-D-18 | REQ-SEC-SMO-1
REQ-SEC-SMO-2
REQ-SEC-SMO-3
REQ-SEC-SMO-4 | No gap | Gap resolved by new requirements added after initial analysis. | - -| | | | | | | -|--|--|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------| -| | | ASSET-D-20
ASSET-D-31 | REQ-TLS-FUN-2
REQ-TLS-FUN-4
REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11
REQ-SEC-SMO-Internal-2
REQ-SEC-SMO-External-2
REQ-SEC-SMO-External-3
REQ-SEC-NFO-FOCOM-3
REQ-SEC-NFO-FOCOM-4
REQ-SEC-NFO-FOCOM-5
REQ-SEC-OCLOUD-SS-1
REQ-SEC-AUTHZ-1 | | | -| | | SW Packages

ASSET-D-23 | REQ-SEC-SMO-1
REQ-SEC-SMO-2
REQ-SEC-SMO-3
REQ-SEC-SMO-4
REQ-TLS-FUN-2
REQ-TLS-FUN-4
REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11
REQ-SEC-SMO-Internal-2
REQ-SEC-SMO-External-2
REQ-SEC-NFO-FOCOM-3
REQ-SEC-NFO-FOCOM-4
REQ-SEC-NFO-FOCOM-5
REQ-SEC-OCLOUD-SS-1
REQ-SEC-ALM-PKG-10
REQ-SEC-ALM-PKG-11
REQ-SEC-AUTHZ-1 | No gap | Gap resolved by new requirements added after initial analysis. | -| | | Non-O-Cloud Architecture Element Data

ASSET-D-24
ASSET-D-30
ASSET-D-40 | REQ-SEC-SMO-1
REQ-SEC-SMO-2
REQ-SEC-SMO-3
REQ-SEC-SMO-4
REQ-TLS-FUN-2
REQ-TLS-FUN-4
REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3 | No gap | Gap resolved by new requirements added after initial analysis. | - -| | | | | | | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|----------------------------------------------------------------| -| | | | REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11
REQ-SEC-SMO-Internal-1
REQ-SEC-SMO-External-2
REC-SEC-OCLOUD-SS-1
REQ-SEC-AUTHZ-1 | | | -| | | Log Files

ASSET-D-29 | REQ-SEC-SMO-1
REQ-SEC-SMO-2
REQ-SEC-SMO-3
REQ-SEC-SMO-4
REQ-TLS-FUN-2
REQ-TLS-FUN-4
REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11
REQ-SEC-SMO-Internal-2
REQ-SEC-SMO-External-2
REQ-SEC-NFO-FOCOM-3
REQ-SEC-NFO-FOCOM-4
REQ-SEC-NFO-FOCOM-5
REQ-SEC-OCLOUD-SS-1
REQ-SEC-AUTHZ-1 | No gap | Gap resolved by new requirements added after initial analysis. | -| Data Encryption | a) Encrypted data in transit and, where feasible, data at rest.

b) Key management policies and secure encryption keys are beginning to be formalized. | SMO Data Assets | | | | -| | | M-Plane

ASSET-D-02
ASSET-D-03 | REQ-SEC-SMO-Internal-1
REQ-SEC-SMO-External-1
REQ-SEC-OCLOUD-SS-1
REQ-SEC-SMO-8
REQ-SEC-SMOS-5 | No gap | Gap resolved by new requirements added after initial analysis | -| | | Data used by NFO/FOCOM

ASSET-D-12
ASSET-D-13
ASSET-D-14
ASSET-D-18
ASSET-D-20
ASSET-D-29
ASSET-D-31 | REQ-SEC-SMO-Internal-1
REQ-SEC-SMO-External-1
REQ-SEC-NFO-FOCOM-1
REQ-SEC-OCLOUD-SS-1
REQ-SEC-SMO-8
REQ-SEC-SMOS-5 | No gap | Gap resolved by new requirements added after initial analysis | -| | | Data not | REQ-SEC-SMO-Internal-1 | No gap | Gap resolved by | - -| | | | | | | -|-----------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | used by NFO/FOCOM

ASSET-D-16
ASSET-D-17
ASSET-D-24
ASSET-D-30
ASSET-D-40 | REQ-SEC-SMO-External-1
REQ-SEC-OCLOUD-SS-1
REQ-SEC-SMO-8
REQ-SEC-SMOS-5 | | new requirements added after initial analysis | -| | | SW Packages

ASSET-D-23 | REQ-SEC-SMO-Internal-1
REQ-SEC-SMO-External-1
REQ-SEC-OCLOUD-SS-1
REQ-SEC-ALM-PKG-10
REQ-SEC-ALM-PKG-11
REQ-SEC-SMO-8
REQ-SEC-SMOS-5 | No gap | Gap resolved by new requirements added after initial analysis | -| Visibility and Analytics Capability | a) Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | SMO Data Assets | | | | -| | | ASSET-D-02
ASSET-D-03
ASSET-D-12
ASSET-D-13
ASSET-D-14
ASSET-D-16
ASSET-D-17
ASSET-D-18
ASSET-D-20
ASSET-D-23
ASSET-D-24
ASSET-D-29
ASSET-D-30
ASSET-D-40 | REQ-SEC-SLM-DAT-EVT-1
REQ-SEC-SLM-DAT-EVT-2
REQ-SEC-SLM-DAT-EVT-3
REQ-SEC-SLM-DAT-EVT-4
REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5 | Partial gap | Data inventory and data categorization are out of scope for O-RAN specifications.

Creating and providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | a) Data lifecycle and security policies (e.g., access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) are automated. | SMO Data Assets | | | | -| | | ASSET-D-02
ASSET-D-03
ASSET-D-12
ASSET-D-13
ASSET-D-14
ASSET-D-16
ASSET-D-17
ASSET-D-18
ASSET-D-20
ASSET-D-23
ASSET-D-24
ASSET-D-29
ASSET-D-30
ASSET-D-40 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| NOTE: Non-O-Cloud Architecture Element Data assets need further study | | | | | | - -### 7.3.9.2 SMO Application and Workloads Pillar - -#### 7.3.9.2.1 SMO Application and Workloads Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-C-01: Logical module: Service Management and Orchestration (SMO) -- ASSET-C-17: SMO Framework/Platform -- ASSET-C-18: SMO Functions -- ASSET-C-21: Data Management and Exposure Functions -- ASSET-C-22: O1, including protocol stack -- ASSET-C-23: O2, including protocol stack -- ASSET-C-24: OFH M-Plane, including protocol stack -- ASSET-C-26: External interfaces -- ASSET-C-27: External interfaces termination at SMO Framework/Platform -- ASSET-C-38: SMO Host -- ASSET-C-39: SMO Tenant (Shared Resource Operator) -- ASSET-C-44: Service Management and Exposure (SME) -- ASSET-C-45: Data Management and Exposure (DME) -- ASSET-C-46: Topology Exposure and Inventory Management (TE&IM) -- ASSET-C-49: Network Function Orchestrator (NFO) -- ASSET-C-50: Federated O-Cloud Orchestration and Management (FOCOM) -- ASSET-C-51: RAN NF Fault Management (FM) -- ASSET-C-52: RAN NF Configuration Management (CM) -- ASSET-C-53: RAN NF Performance Management (PM) -- ASSET-C-57: SW Package Onboarding -- ASSET-C-58: Service Orchestration -- ASSET-C-62: SMOS Communication - -#### 7.3.9.2.2 SMO Application and Workloads Pillar Gap Analysis - -**Table SMO Gap Analysis-32: SMO Application and Workloads Pillar Gap Analysis** - -| App/
Workloads ZT
Function | Guidance to reach
initial stage | Asset(s) | Existing Requirements
mapped to CISA stage | Assessed
Gap to
Initial CISA
Stage | Comments | -|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------| -| Application
Access
(Authorization) | SMO Application and Workloads Assets | | | | | -| | a) Access authorization capabilities utilize contextual information such as identity, device compliance, and other attributes to make decisions on various requests for accessing application assets. | SMOS
ASSET-C-01
ASSET-C-17
ASSET-C-18
ASSET-C-38
ASSET-C-39
ASSET-C-46
ASSET-C-57
ASSET-C-58
ASSET-C-62 | REQ-SEC-SMO-1
REQ-SEC-SMO-3
REQ-SEC-SMO-Internal-1
REQ-SEC-SMO-Internal-2
REQ-SEC-AUTHZ-2 | Partial gap | Gap partially resolved by new requirements added after initial analysis.

Contextual information is out of scope for O-RAN. | -| | b) Authorization is granted per request with expiration. | O1
ASSET-C-22
ASSET-C-51 | REQ-SEC-O1-2
REQ-SEC-O1-3
REQ-SEC-AUTHZ-2 | Partial gap | Gap partially resolved by new requirements added after initial | - -| | | | | | | -|--------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------| -| | | ASSET-C-52
ASSET-C-53 | | | analysis.

Contextual information is out of scope for O-RAN. | -| | | O2

ASSET-C-23
ASSET-C-49
ASSET-C-50 | REQ-SEC-O2-2
REQ-SEC-NFO-FOCOM-3
REQ-SEC-NFO-FOCOM-4
REQ-SEC-NFO-FOCOM-5
REQ-SEC-AUTHZ-2 | Partial gap | Gap partially resolved by new requirements added after initial analysis.

Contextual information is out of scope for O-RAN. | -| | | M-Plane

ASSET-C-24 | O-RAN Management Plane Specification clauses 5.4 & 6.5 [i.26]

REQ-SEC-SharedORU-1
REQ-SEC-AUTHZ-2 | Partial gap | Gap partially resolved by new requirements added after initial analysis.

Contextual information is out of scope for O-RAN. | -| | | External Interface

ASSET-C-21
ASSET-C-26
ASSET-C-27
ASSET-C-44
ASSET-C-45 | REQ-SEC-SMO-2
REQ-SEC-SMO-4
REQ-SEC-SMO-External-2
REQ-SEC-SMO-External-3
REQ-SEC-AUTHZ-2 | Partial gap | Gap partially resolved by new requirements added after initial analysis.

Contextual information is out of scope for O-RAN. | -| Application Threat Protections | a) Threat protections is integrated into mission-critical application workflows.

b) Threat protections safeguard applications against known threats and address some application-specific threats. | SMO Applications and Workloads Assets | | | | -| | | ASSET-C-17
ASSET-C-18
ASSET-C-21
ASSET-C-22
ASSET-C-23
ASSET-C-24
ASSET-C-26
ASSET-C-27
ASSET-C-38
ASSET-C-39
ASSET-C-44
ASSET-C-45
ASSET-C-46
ASSET-C-49
ASSET-C-50
ASSET-C-51
ASSET-C-52
ASSET-C-53
ASSET-C-57
ASSET-C-58
ASSET-C-62 | REQ-SEC-ALM-SU-2
REQ-SEC-ALM-SU-3 | No gap | | -| Accessible Applications | a) Applicable mission-critical applications are available over open public network connections to authorized users as | SMO Applications and Workloads Assets | | | | -| | | ASSET-C-17
ASSET-C-18
ASSET-C-21
ASSET-C-22
ASSET-C-23
ASSET-C-24 | None | Gap | Out of scope for O-RAN

No identified Mission critical | - -| | | | | | | -|-----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------| -| | needed. | ASSET-C-26
ASSET-C-27
ASSET-C-38
ASSET-C-39
ASSET-C-44
ASSET-C-45
ASSET-C-46
ASSET-C-49
ASSET-C-50
ASSET-C-51
ASSET-C-52
ASSET-C-53
ASSET-C-57
ASSET-C-58
ASSET-C-62 | | | applications | -| Secure Application Development and Deployment Workflow (New Function) | a) Infrastructure for development, testing, and production environments (including automation).

b) Formal code deployment mechanisms through CI/CD pipelines.

c) Access controls support least privilege principles. | SMO Applications and Workloads Assets | | | | -| | | ASSET-C-17
ASSET-C-18
ASSET-C-21
ASSET-C-22
ASSET-C-23
ASSET-C-24
ASSET-C-26
ASSET-C-27
ASSET-C-38
ASSET-C-39
ASSET-C-44
ASSET-C-45
ASSET-C-46
ASSET-C-49
ASSET-C-50
ASSET-C-51
ASSET-C-52
ASSET-C-53
ASSET-C-57
ASSET-C-58
ASSET-C-62 | None | Gap | Out of scope for O-RAN

Securing infrastructure for development, testing, and production environments is out of scope for O-RAN. | -| Application Security Testing (Formerly Application Security) | a) Utilization of static and dynamic testing methods for security testing.

b) Performance of security testing including manual expert analysis before application deployment. | SMO Applications and Workloads Assets | | | | -| | | ASSET-C-17
ASSET-C-18
ASSET-C-21
ASSET-C-22
ASSET-C-23
ASSET-C-24
ASSET-C-26
ASSET-C-27
ASSET-C-38
ASSET-C-39
ASSET-C-44
ASSET-C-45
ASSET-C-46
ASSET-C-49
ASSET-C-50
ASSET-C-51
ASSET-C-52
ASSET-C-53
ASSET-C-57
ASSET-C-58
ASSET-C-62 | REQ-SEC-ALM-PKG-1
REQ-SEC-ALM-PKG-7b | No gap | Guidance (b) is out of scope for O-RAN. | -| Visibility and Analytics | a) Initiate the automation of | SMO Applications and Workloads Assets | | | | -| | | ASSET-C-01 | REQ-SEC-SLM-TESS-3 | Partial gap | Including | - -| | | | | | | -|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Capability | application profile (e.g., state, health, and performance) and security monitoring processes for improved log collection, aggregation, and analytics. | ASSET-C-17
ASSET-C-18
ASSET-C-21
ASSET-C-22
ASSET-C-23
ASSET-C-24
ASSET-C-26
ASSET-C-27
ASSET-C-38
ASSET-C-39
ASSET-C-44
ASSET-C-45
ASSET-C-46
ASSET-C-49
ASSET-C-50
ASSET-C-51
ASSET-C-52
ASSET-C-53
ASSET-C-57
ASSET-C-58
ASSET-C-62 | REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-5 | | application profile information in security logs is in scope and covered by existing requirements. Log aggregation and analytics are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | a) Periodically modifies application configurations, including location and access parameters, to align with pertinent security and performance objectives. | SMO Applications and Workloads Assets | | | | -| | | ASSET-C-01
ASSET-C-17
ASSET-C-18
ASSET-C-21
ASSET-C-22
ASSET-C-23
ASSET-C-24
ASSET-C-26
ASSET-C-27
ASSET-C-38
ASSET-C-39
ASSET-C-44
ASSET-C-45
ASSET-C-46
ASSET-C-49
ASSET-C-50
ASSET-C-51
ASSET-C-52
ASSET-C-53
ASSET-C-57
ASSET-C-58
ASSET-C-62 | None | Gap | Out of scope, as application configuration falls under the operator's responsibilities. | - -### 7.3.9.3 SMO Identity Pillar - -#### 7.3.9.3.1 SMO Identity Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-C-01: Logical module: Service Management and Orchestration (SMO) -- ASSET-C-17: SMO Framework/Platform -- ASSET-C-18: SMO Functions -- ASSET-C-21: Data Management and Exposure Functions -- ASSET-C-22: O1, including protocol stack -- ASSET-C-23: O2, including protocol stack -- ASSET-C-24: OFH M-Plane, including protocol stack -- ASSET-C-26: External interfaces - -- ASSET-C-27: External interfaces termination at SMO Framework/Platform -- ASSET-C-38: SMO Host -- ASSET-C-39: SMO Tenant (Shared Resource Operator) -- ASSET-C-44: Service Management and Exposure (SME) -- ASSET-C-45: Data Management and Exposure (DME) -- ASSET-C-46: Topology Exposure and Inventory Management (TE&IM) -- ASSET-C-49: Network Function Orchestrator (NFO) -- ASSET-C-50: Federated O-Cloud Orchestration and Management (FOCOM) -- ASSET-C-51: RAN NF Fault Management (FM) -- ASSET-C-52: RAN NF Configuration Management (CM) -- ASSET-C-53: RAN NF Performance Management (PM) -- ASSET-C-57: SW Package Onboarding -- ASSET-C-58: Service Orchestration -- ASSET-C-62: SMOS Communication - -7.3.9.3.2 SMO Identity Pillar Gap Analysis - -**Table SMO Gap Analysis-33: SMO Identity Pillar Gap Analysis** - -| Identity ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|------------------------------------|----------| -| Authentication | SMO Identity Pillar Assets | | | | | -| | The system authenticates identity using MFA, which may include passwords as one factor and requires validation of multiple entity attributes (e.g., locale or activity).

a) If there is mutual authentication for internal communications, we consider the stage as INITIAL.

b) For internal interfaces, authentication based on credentials alone (certificate, pre-shared key, etc.) can be considered as meeting INITIAL maturity level. | SMOS

ASSET-C-01
ASSET-C-17
ASSET-C-18
ASSET-C-38
ASSET-C-39
ASSET-C-46
ASSET-C-57
ASSET-C-58
ASSET-C-62 | REQ-SEC-SMO-1
REQ-SEC-SMO-Internal-2
REQ-SEC-SharedORU-1 | No gap | | -| | | O1

ASSET-C-22
ASSET-C-51
ASSET-C-52
ASSET-C-53 | REQ-TLS-FUN-2
REQ-TLS-FUN-3 | No gap | | -| | | O2

ASSET-C-23
ASSET-C-49
ASSET-C-50 | REQ-SEC-NFO-FOCOM-3
REQ-SEC-NFO-FOCOM-4 | No gap | | -| | | M-Plane

ASSET-C-24 | O-RAN Management Plane Specification clauses 5.4 & 6.5 [i.26]

REQ-SEC-SharedORU-1 | No gap | | -| | | External Interface | REQ-SEC-SMO-2 | No gap | | - -| | | | | | | -|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------| -| | | ASSET-C-21
ASSET-C-26
ASSET-C-27
ASSET-C-44
ASSET-C-45 | | | | -| Access Management (Authorization) | The system authorizes access, including for privileged access requests, that expires with automated review.

a) This function applies to APIs and user access.

b) For applications, static role assignments (e.g. role binding of a service account) with ephemeral tokens can be considered as INITIAL stage. | SMO Identity Pillar Assets | | | | -| | | SMOS

ASSET-C-01
ASSET-C-17
ASSET-C-18
ASSET-C-38
ASSET-C-39
ASSET-C-46
ASSET-C-57
ASSET-C-58
ASSET-C-62 | REQ-SEC-SMO-3
REQ-SEC-SMO-4
REQ-SEC-SMO-Internal-2
REQ-SEC-SharedORU-2 | No gap | | -| | | O1

ASSET-C-22
ASSET-C-51
ASSET-C-52
ASSET-C-53 | REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11 | No gap | | -| | | O2

ASSET-C-23
ASSET-C-49
ASSET-C-50 | REQ-SEC-NFO-FOCOM-5 | No gap | | -| | | M-Plane
ASSET-C-24 | O-RAN Management Plane Specification clauses 5.4 & 6.5 [i.26]

REQ-SEC-SharedORU-2 | No gap | | -| | | External Interface

ASSET-C-21
ASSET-C-26
ASSET-C-27
ASSET-C-44
ASSET-C-45 | REQ-SEC-OCloud-ISO-7 | No gap | | -| Visibility and Analytics Capability | a) Collecting user and entity activity logs.

b) Performing Routine Analysis:

a. Conduct regular manual analysis of the | SMO Identity Pillar Assets | | | | -| | | ASSET-C-01
ASSET-C-17
ASSET-C-18
ASSET-C-21
ASSET-C-22
ASSET-C-23
ASSET-C-24
ASSET-C-26
ASSET-C-27
ASSET-C-38 | REQ-SEC-SLM-TESS-3 | Partial gap | Generation of security logs is in scope and covered by existing security log requirements. Analysis, automation, and correlation are | - -| | | | | | | -|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|-----|------------------------------------------------------------------------------------------------------------------| -| | logs.

b. Implement some automated analysis, with limited correlation between different log types. | ASSET-C-39
ASSET-C-44
ASSET-C-45
ASSET-C-46
ASSET-C-49
ASSET-C-50
ASSET-C-51
ASSET-C-52
ASSET-C-53
ASSET-C-57
ASSET-C-58
ASSET-C-62 | | | considered out of scope. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | a) Manually orchestrates privileged and external identities. | SMO Identity Pillar Assets | | | | -| | b) Automates orchestration of non-privileged users.

c) Automates orchestration of self-managed entities. | ASSET-C-01
ASSET-C-17
ASSET-C-18
ASSET-C-21
ASSET-C-22
ASSET-C-23
ASSET-C-24
ASSET-C-26
ASSET-C-27
ASSET-C-38
ASSET-C-39
ASSET-C-44
ASSET-C-45
ASSET-C-46
ASSET-C-49
ASSET-C-50
ASSET-C-51
ASSET-C-52
ASSET-C-53
ASSET-C-57
ASSET-C-58
ASSET-C-62 | None | Gap | Out of scope, as identities orchestration fall under the operator's responsibilities | - -### 7.3.9.4 SMO Networks Pillar - -#### 7.3.9.4.1 SMO Networks Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] and WG1 O-RAN Architecture Description [i.1]: - -- ASSET-C-22: O1, including protocol stack -- ASSET-C-23: O2, including protocol stack -- ASSET-C-24: OFH M-Plane, including protocol stack -- ASSET-C-26: External interfaces -- ASSET-C-27: External interfaces termination at SMO Framework/Platform -- ASSET-C-62: SMOS Communication - -7.3.9.4.2 SMO Networks Pillar Gap Analysis - -**Table SMO Gap Analysis-34: SMO Networks Pillar Gap Analysis** - -| Data ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Traffic Encryption | Encryption for all internal (and preferably external) application traffic, with formalized key management policies and secure encryption keys. | SMO Networks Pillar Assets | | | | -| | | ASSET-C-22
ASSET-C-23
ASSET-C-24
ASSET-C-26
ASSET-C-27
ASSET-C-62 | REQ-SEC-SMO-Internal-1
REQ-SEC-SMO-External-1
REQ-SEC-NFO-FOCOM-1
REQ-TLS-FUN-1
REQ-TLS-FUN-3
REQ-SEC-O2-1
O-RAN Management Plane Specification clauses 5.4 & 6.5 [i.26] | No gap | | -| Visibility and Analytics Capability |

a) Utilize network monitoring capabilities based on known indicators of compromise, including network enumeration, to develop situational awareness in each environment.

b) Commence correlating telemetry across traffic types and environments to facilitate analysis and threat hunting activities.

| SMO Networks Pillar Assets | | | | -| | | ASSET-C-22
ASSET-C-23
ASSET-C-24
ASSET-C-26
ASSET-C-27
ASSET-C-62 | None | Gap |

No requirements for providing network monitoring information.

Providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE.

| -| Automation and Orchestration Capability |

a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments.

b) Ensure that all resources have a defined lifetime determined by policies and telemetry

| SMO Networks Pillar Assets | | | | -| | | ASSET-C-22
ASSET-C-23
ASSET-C-24
ASSET-C-26
ASSET-C-27
ASSET-C-62 | None | Gap | Out of scope, network resource configuration and lifecycle management fall under the operator's responsibilities. | - -| | | | | | | -|--|-------|--|--|--|--| -| | data. | | | | | -|--|-------|--|--|--|--| - -### 7.3.9.5 SMO Devices Pillar - -#### 7.3.9.5.1 SMO Devices Pillar Assets - -- No assets applicable to devices pillar - -#### 7.3.9.5.2 SMO Devices Pillar Gap Analysis - -The Devices Pillar is out of scope for the gap analysis. - -### 7.3.10 O1 Interface Gap Analysis - -#### 7.3.10.1 O1 Interface Data Pillar Analysis - -##### 7.3.10.1.1 O1 Interface Data Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-D-03: Critical Management-Plane data transported over the O1 interface -- ASSET-D-16: X.509 certificates. -- ASSET-D-17: Private keys -- ASSET-D-18: O-RAN components associated and configuration data. -- ASSET-D-23: Patches for vulnerable SW components -- ASSET-D-24: NETCONF Configuration Access Control Model datastores - -##### 7.3.10.1.2 O1 Interface Data Pillar Gap Analysis - -**Table O1 Interface Gap Analysis-35: O1 Interface Data Pillar Gap Analysis** - -| Data ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|------------------|---------------------------------------------------------------------------------------------------------------------------------|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|----------| -| Data Access | a) Automated data access control

b) Elements of least privileges are incorporated with the automated data access control | O1 Interface Data Assets | | | | -| | | ASSET-D-3 | REQ-TLS-FUN-2
REQ-TLS-FUN-4
REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11 | No gap | | -| | | ASSET-D-16 | REQ-TLS-FUN-2
REQ-TLS-FUN-4 | No gap | | - -| | | | | | -|--|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--| -| | | REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11
REQ-SEC-
OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-1 | | | -| | | ASSET-D-17
REQ-TLS-FUN-2
REQ-TLS-FUN-4
REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11
REQ-SEC-
OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-1 | No gap | | -| | | ASSET-D-18
REQ-TLS-FUN-2
REQ-TLS-FUN-4
REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11
REQ-SEC-
OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-1 | No gap | | -| | | ASSET-D-23
REQ-TLS-FUN-2
REQ-TLS-FUN-4
REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4 | No gap | | - -| | | | | | | -|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11
REQ-SEC-
OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-1 | | | -| Data Encryption | a) Encrypted data in transit and, where feasible, data at rest.

b) Key management policies and secure encryption keys are beginning to be formalized. | O1 Interface Data Assets | | | | -| | | ASSET-D-3 | REQ-TLS-FUN-1
REQ-TLS-FUN-3
REQ-SEC-
OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-1 | No gap | | -| | | ASSET-D-16 | REQ-TLS-FUN-1
REQ-TLS-FUN-3
REQ-SEC-
OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-1 | No gap | | -| | | ASSET-D-17 | REQ-SEC-E2-1
SEC-CTL-E2-1
REQ-SEC-
OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-1 | No gap | | -| | | ASSET-D-18 | REQ-SEC-E2-1
SEC-CTL-E2-1
REQ-SEC-
OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-1 | No gap | | -| | | ASSET-D-23 | REQ-SEC-E2-1
SEC-CTL-E2-1
REQ-SEC-
OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-1 | No gap | | -| Visibility and Analytics Capability | Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility | O1 interface Data Assets | | | | -| | | ASSET-D-03
ASSET-D-16
ASSET-D-17
ASSET-D-18
ASSET-D-23
ASSET-D-24 | REQ-SEC-SLM-
DAT-EVT-1
REQ-SEC-SLM-
DAT-EVT-2
REQ-SEC-SLM-
DAT-EVT-3
REQ-SEC-SLM-
DAT-EVT-4 | Partial gap | Data inventory and data categorization are out of scope for O-RAN specifications.

Creating and providing the required information is within scope. | - -| | | | | | | -|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5 | | However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | Data lifecycle and security policies (e.g., access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) are automated. | O1 interface Data Assets | | | | -| | | ASSET-D-03
ASSET-D-16
ASSET-D-17
ASSET-D-18
ASSET-D-23
ASSET-D-24 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | - -### 7.3.10.2 O1 Interface Application and Workloads Pillar - -#### 7.3.10.2.1 O1 Interface Application and Workloads Pillar Assets - -- No assets applicable to application and workloads pillar - -#### 7.3.10.2.2 O1 Interface Application and Workloads Pillar Gap Analysis - -- No gap analysis applies since there are no assets applicable to specific pillar - -### 7.3.10.3 O1 Interface Identity Pillar - -#### 7.3.10.3.1 O1 Interface Identity Pillar Assets - -- No asset applicable to specific pillar - -#### 7.3.10.3.2 O1 Interface Identity Pillar Gap Analysis - -- No gap analysis applies since there are no assets applicable to specific pillar - -### 7.3.10.4 O1 Interface Networks Pillar - -#### 7.3.10.4.1 O1 Interface Networks Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4]: - -- ASSET-C-22: O1, including protocol stack - -7.3.10.4.2 O1 Interface Networks Pillar Gap Analysis - -**Table O1 Interface Gap Analysis-36: O1 Interface Networks Pillar Gap Analysis** - -| Networks ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|--------------------------------------------|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Traffic Encryption | Encryption for all internal (and preferably external) application traffic, with formalized key management policies and secure encryption keys. | O1 Networks Pillar Assets | | | | -| | | ASSET-C-22 | REQ-TLS-FUN-1 | No gap | | -| Visibility and Analytics Capability | a) Utilize network monitoring capabilities based on known indicators of compromise, including network enumeration, to develop situational awareness in each environment.

b) Commence correlating telemetry across traffic types and environments to facilitate analysis and threat hunting activities. | O1 interface Networks Pillar Assets | | | | -| | | ASSET-C-22 | None | Gap | No requirements for providing network monitoring information.

Providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments.

b) Ensure that all resources have a defined lifetime determined by policies and telemetry data. | O1 interface Networks Pillar Assets | | | | -| | | ASSET-C-22 | None | Gap | Out of scope, network resource configuration and lifecycle management fall under the operator's responsibilities. | - -### 7.3.10.5 O1 Interface Devices Pillar - -#### 7.3.10.5.1 O1 Interface Devices Pillar Assets - -- No assets applicable to devices pillar - -#### 7.3.10.5.2 O1 Interface Devices Pillar Transversal Requirements - -The following devices pillar functions are considered transversal and are covered in 7.3.2: - -- Policy Enforcement and Compliance Monitoring. -- Asset & Supply Chain Risk Management. - -#### 7.3.10.5.3 O1 Interface Devices Pillar Gap Analysis - -The Devices Pillar is out of scope for the gap analysis. - -### 7.3.11 O-Cloud Gap Analysis - -#### 7.3.11.1 O-Cloud Data Pillar - -##### 7.3.11.1.1 O-Cloud Data Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-D-16: X.509 certificates in O-RAN network such as those used for O-RAN components for authentication, encryption, and signing. -- ASSET-D-17: Security private keys in O-RAN network such as those used for O-RAN components for authentication, encryption, and signing. -- ASSET-D-18: O-RAN components associated and configuration data -- ASSET-D-20: Credentials of O-Cloud components -- ASSET-D-29: Security event log files generated by O-RAN components -- ASSET-D-31: Security telemetry from the O-Cloud for detecting threats and anomalies -- ASSET-D-32: Cryptographic keys used during secure boot, for encryption/decryption -- ASSET-D-33: Data transported over AALI-C-Mgmt interface -- ASSET-D-34: Data transported over AALI-C-App & AALI-P interfaces -- ASSET-D-35: Data transported over vendor-specific interface -- ASSET-D-36: AAL profile -- ASSET-D-37: AAL LPU -- ASSET-D-38: Stored AAL data - -##### 7.3.11.1.2 O-Cloud Data Pillar Gap Analysis - -**Table O-Cloud Gap Analysis-37: O-Cloud Data Pillar Gap Analysis** - -| Data ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|------------------|-------------------------------------------------------------------------|---------------------|-------------------------------------------------------------------------|------------------------------------|----------| -| Data Access | a) Automated data access control

b) Elements of least privileges | O-Cloud Data Assets | | | | -| | | ASSET-D-16 | REQ-SEC-OCLOUD-ISO-3
SEC-CTL-O-CLOUD-ISO-3
REQ-SEC-OCLOUD-O2dms-1 | No gap | | - -| | | | | | -|---------------------------------------------------------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------------------------------------------------------------| -| are incorporated with the automated data access control | | REQ-SEC-OCLOUD-O2dms-3
REQ-SEC-OCLOUD-O2ims-1
REQ-SEC-OCLOUD-O2ims-3 | | | -| | ASSET-D-17 | REQ-SEC-OCLOUD-ISO-3
SEC-CTL-O-CLOUD-ISO-3
REQ-SEC-OCLOUD-O2dms-1
REQ-SEC-OCLOUD-O2dms-3
REQ-SEC-OCLOUD-O2ims-1
REQ-SEC-OCLOUD-O2ims-3 | No gap | | -| | ASSET-D-18 | REQ-SEC-OCLOUD-ISO-3
SEC-CTL-OCLOUD-ISO-3
REQ-SEC-OCLOUD-O2dms-1
REQ-SEC-OCLOUD-O2dms-3
REQ-SEC-OCLOUD-O2ims-1
REQ-SEC-OCLOUD-O2ims-3
REQ-SEC-O-CLOUD-NotifAPI-1
REQ-SEC-O-CLOUD-NotifAPI-2
SEC-CTL-O-CLOUD-INTERFACE-2
SEC-CTL-O-CLOUD-INTERFACE-3 | No gap | O-Cloud configuration is controlled by RBAC (for k8s) and OS (for VMs) | -| | ASSET-D-20 | REQ-SEC-OCLOUD-1
REQ-SEC-OCLOUD-2
SEC-CTL-OCLOUD-1 | No gap | Gap resolved as requirements were identified after initial analysis. | -| | ASSET-D-29 | REQ-SEC-SLM-TESS-6
REQ-SEC-SLM-TESS-7
REQ-SEC-SLM-TESM-1
REQ-SEC-SLM-TESM-3
REQ-SEC-TESR-1
REQ-SEC-TESR-7
REQ-SEC-TESR-9
REQ-SEC-TESR-11
REQ-SEC-SLM-SST-4
REQ-SEC-SLM-STR-2 | No gap | No Security controls are defined; this gap is known and intentionally gap is not closed to enable many implementations that are existing. | -| | ASSET-D-31 | REQ-SEC-SLM-TESS-6
REQ-SEC-SLM-TESS-7
REQ-SEC-SLM-TESM-1
REQ-SEC-SLM-TESM-3
REQ-SEC-TESR-1
REQ-SEC-TESR-7 | No gap | No Security controls are defined; this gap is known and intentionally gap is not closed to enable many implementations that are | - -| | | | | | | -|-----------------|---------------------------------------------------------------------------------------|---------------------|--------------------------------------------------------------------------------|--------|--------------------------------------------------------------------------------------------------------| -| | | | REQ-SEC-TESR-9
REQ-SEC-TESR-11
REQ-SEC-SLM-SST-4
REQ-SEC-SLM-STR-2 | | existing. | -| | | ASSET-D-32 | REQ-SEC-OCLOUD-1
REQ-SEC-OCLOUD-2
SEC-CTL-OCLOUD-1 | No gap | Gap resolved as requirements were identified after initial analysis. | -| | | ASSET-D-33 | N/A | No gap | No access of data being transported is defined for the interface - hence this row is marked as N/A. | -| | | ASSET-D-34 | N/A | No gap | No access of data being transported is defined for the interface - hence this row is marked as N/A. | -| | | ASSET-D-35 | N/A | No gap | No access of data being transported is defined for the interface - hence this row is marked as N/A. | -| | | ASSET-D-36 | None | Gap | No requirements and controls are specified | -| | | ASSET-D-37 | None | Gap | No requirements and controls are specified | -| | | ASSET-D-38 | REQ-SEC-AAL-1
REQ-SEC-AAL-2
REQ-SEC-AAL-5
SEC-CTL-AAL-1 | No gap | | -| Data Encryption | a) Encrypted data in transit and, where feasible, data at rest. | O-Cloud Data Assets | | | | -| | | ASSET-D-16 | REQ-SEC-OCLOUD-SS-1 (See NOTE 1)
SEC-CTL-OCLOUD-SS-1 | No gap | | -| | | ASSET-D-17 | REQ-SEC-OCLOUD-SS-1 (See NOTE 1)
SEC-CTL-OCLOUD-SS-1 | No gap | | -| | b) Key management policies and secure encryption keys are beginning to be formalized. | ASSET-D-18 | REQ-SEC-OCLOUD-SS-1 (See NOTE 1)
SEC-CTL-OCLOUD-SS-1
REQ-SEC-OCLOUD-TS-1 | No gap | | -| | | ASSET-D-20 | REQ-SEC-OCLOUD-SS-1 (See NOTE 1)
SEC-CTL-OCLOUD-SS-1 | No gap | Gap resolved as identified requirements already meet the data encryption requirements. | -| | | ASSET-D-29 | REQ-SEC-SLM-TESM-2
REQ-SEC-TESR-6
REQ-SEC-SLM-STR-1 | No gap | No Security controls are defined; this gap is known and intentionally gap is not closed to enable many | - -| | | | | | | -|--|--|------------|------------------------------------------------------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | | implementations that are existing. | -| | | ASSET-D-31 | REQ-SEC-SLM-TESM-2
REQ-SEC-TESR-6
REQ-SEC-SLM-STR-1 | No gap | No Security controls are defined; this gap is known and intentionally gap is not closed to enable many implementations that are existing. | -| | | ASSET-D-32 | REQ-SEC-OCLOUD-SS-1
(See NOTE 1)
SEC-CTL-OCLOUD-SS-1 | No gap | | -| | | ASSET-D-33 | REQ-SEC-AALI-C-Mgmt-3
SEC-CTL-AALI-C-Mgmt-1 | No gap | | -| | | ASSET-D-34 | None | Gap |

Data encryption for AALI-C-App and AALI-P APIs used by AAL application is not feasible, since these APIs are implemented at lower level as function/method calls within AAL implementation and not over a network interface.

NOTE: The below listed requirements are compensatory requirements and cover isolation of data which was transferred using the AALI-C-App and AALI-P APIs from AAL application to AAL implementation.

REQ-SEC-OCLOUD-ISO-4
REQ-SEC-OCLOUD-3
REQ-SEC-OCLOUD-SS-2

| -| | | ASSET-D-35 | REQ-SEC-AAL-VS-4 | Partial gap | There may not be a need to specify controls, since this is a vendor specific interface. | -| | | ASSET-D-36 | None | Gap | No requirements and controls are specified | -| | | ASSET-D-37 | None | Gap | No requirements and controls are specified | -| | | ASSET-D-38 | REQ-SEC-OCLOUD-SS-1
SEC-CTL-OCLOUD-SS-1 | No gap | Gap resolved as requirements were | - -| | | | | | | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | | identified after initial analysis. | -| Visibility and Analytics Capability | a) Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | O-Cloud Data Assets | | | | -| | | ASSET-D-16
ASSET-D-17
ASSET-D-18
ASSET-D-20
ASSET-D-29
ASSET-D-31
ASSET-D-32
ASSET-D-33
ASSET-D-34
ASSET-D-35
ASSET-D-36
ASSET-D-37
ASSET-D-38 | REQ-SEC-SLM-DAT-EVT-1
REQ-SEC-SLM-DAT-EVT-2
REQ-SEC-SLM-DAT-EVT-3
REQ-SEC-SLM-DAT-EVT-4
REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5 | Partial gap | WG6 information model (O-RAN.WG6.O-CLOUD-IM.0-R004-v04.00) specifies the data inventory and data categorization aspects.

Creating and providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | a) Data lifecycle and security policies (e.g., access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) are automated. | O-Cloud Data Assets | | | | -| | | ASSET-D-17
ASSET-D-18
ASSET-D-20
ASSET-D-29
ASSET-D-31
ASSET-D-32
ASSET-D-33
ASSET-D-34
ASSET-D-35
ASSET-D-36
ASSET-D-37
ASSET-D-38 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | - -NOTE 1: Encryption of data in use is considered as Optimal stage according to O-RAN ZTA Security Requirements for Data Encryption. - -### 7.3.11.2 O-Cloud Applications and Workloads Pillar - -#### 7.3.11.2.1 O-Cloud Applications and Workloads Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-C-08: O-Cloud (Covers DMS and IMS and their services) -- ASSET-C-29: AAL software including software, libraries, drivers -- ASSET-C-30: The hardware accelerator device firmware - -7.3.11.2.2 O-Cloud Applications and Workloads Pillar Gap Analysis - -**Table O-Cloud Gap Analysis-38: O-Cloud Applications and Workloads Pillar Gap Analysis** - -| Application and Workloads ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|---------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|-------------------------------------------------------------------------------|------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Application Access (Authorization) |

a) Access authorization capabilities utilize contextual information such as identity, device compliance, and other attributes to make decisions on various requests for accessing application assets.

b) Authorization is granted per request with expiration.

| O-Cloud Application and Workloads Assets | | | | -| | | ASSET-C-08 | REQ-SEC-NFO-FOCOM-5
SEC-CTL-O-CLOUD-INTERFACE-2
SEC-CTL-OCLOUD-1 | No gap | Gap resolved as requirements were identified after initial analysis. | -| | | ASSET-C-29 | None | Gap | Out of scope, the AAL software at runtime is a low-level process / library that is used by AAL applications.

Method/function calls are made to access the AAL implementation / libraries and security requirements for method calls are considered out of scope. | -| | | ASSET-C-30 | None | Gap | Out of scope, the firmware at runtime does not have authorization checks, as there are no interfaces, or APIs involved, and it will be low-level method calls which the firmware exposes. | -| Application Threat Protections |

a) Threat protections is integrated into mission-critical application workflows.

b) Threat protections safeguard applications against known threats and address some application-specific threats.

| O-Cloud Application and Workloads Assets | | | | -| | | ASSET-C-08 | REQ-SEC-DOS-1
REQ-SEC-OCLOUD-SU-5
REQ-SEC-OCLOUD-SU-7 | No gap | | -| | | ASSET-C-29 | REQ-SEC-OCLOUD-SU-1
REQ-SEC-OCLOUD-SU-5
REQ-SEC-OCLOUD-SU-6
REQ-SEC- | No gap | | - -| | | | | | | -|-----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|--------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------------| -| | | | OCLOUD-SU-7 | | | -| | | ASSET-C-30 | REQ-SEC-OCLOUD-SU-5
REQ-SEC-OCLOUD-SU-7 | No gap | | -| Accessible Applications | a) Applicable mission-critical applications are available over open public network connections to authorized users as needed. | O-Cloud Application and Workloads Assets | | | | -| | | ASSET-C-08 | N/A | No gap | Out of scope for O-RAN
No identified Mission critical applications | -| | | ASSET-C-29 | N/A | No gap | Out of scope for O-RAN
No identified Mission critical applications | -| | | ASSET-C-30 | N/A | No gap | Out of scope for O-RAN
No identified Mission critical applications | -| Secure Application Development and Deployment Workflow (New Function) | a) Infrastructure for development, testing, and production environments (including automation).

b) Formal code deployment mechanisms through CI/CD pipelines.

c) Access controls support least privilege principles. | O-Cloud Application and Workloads Assets | | | | -| | | ASSET-C-08 | None | Gap | Out of scope for O-RAN
Securing infrastructure for development, testing, and production environments is out of scope for O-RAN. | -| | | ASSET-C-29 | None | Gap | Out of scope for O-RAN
Securing infrastructure for development, testing, and production environments is out of scope for O-RAN. | -| | | ASSET-C-30 | REQ-SEC-AAL-4 | No gap | Out of scope for O-RAN
Securing infrastructure for development, testing, and production environments is out of scope for O-RAN. | -| Application Security Testing (Formerly Application Security) | a) Utilization of static and dynamic testing methods for security testing.

b) Performance of security testing including manual expert analysis before application | O-Cloud Application and Workloads Assets | | | | -| | | ASSET-C-08 | REQ-SEC-ALM-PKG-1
REQ-SEC-ALM-PKG-7b | No gap | Guidance (b) is out of scope for O-RAN. | -| | | ASSET-C-29 | REQ-SEC-ALM-PKG-1
REQ-SEC-ALM-PKG-7b | No gap | Guidance (b) is out of scope for O-RAN. | - -| | | | | | | -|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | deployment. | ASSET-C-30 | REQ-SEC-ALM-PKG-1
REQ-SEC-ALM-PKG-7b | No gap | Guidance (b) is out of scope for O-RAN. | -| Visibility and Analytics Capability | a) Initiate the automation of application profile (e.g., state, health, and performance) and security monitoring processes for improved log collection, aggregation, and analytics. | O-Cloud Application and Workloads Assets | | | | -| | | ASSET-C-08 | REQ-SEC-SLM-FLD-1
REQ-SEC-SLM-FLD-2
REQ-SEC-SLM-TESS-2
REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-GEN-EVT-6 | Partial gap |
  • These requirements allow for the inclusion of application profile information in security logs. However, the automation of application profile monitoring processes and analytics is not addressed.
  • Log collection, aggregation, and analytics are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE.
| -| | | ASSET-C-29 | REQ-SEC-SLM-FLD-1
REQ-SEC-SLM-FLD-2
REQ-SEC-SLM-TESS-2
REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-GEN-EVT-6
REQ-SEC-AAL-6 | Partial gap |
  • These requirements allow for the inclusion of application profile information in security logs. However, the automation of application profile monitoring processes and analytics is not addressed.
  • Log collection, aggregation, and analytics are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE.
| -| | | ASSET-C-30 | None | Gap | Log collection, aggregation, and analytics are out of | - -| | | | | | | -|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------|------|-----|-----------------------------------------------------------------------------------------| -| | | | | | scope. | -| Automation and Orchestration Capability | a) Periodically modifies application configurations, including location and access parameters, to align with pertinent security and performance objectives. | O-Cloud Application and Workloads Assets | | | | -| | | ASSET-C-08 | None | Gap | Out of scope, as application configuration falls under the operator's responsibilities. | -| | | ASSET-C-29 | None | Gap | Out of scope, as application configuration falls under the operator's responsibilities. | -| | | ASSET-C-30 | None | Gap | Out of scope, as application configuration falls under the operator's responsibilities. | - -### 7.3.11.3 O-Cloud Identity Pillar - -#### 7.3.11.3.1 O-Cloud Identity Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-C-08: O-Cloud (Covers DMS and IMS and their services) -- ASSET-C-29: AAL software including software, libraries, drivers -- ASSET-C-30: The hardware accelerator device firmware - -#### 7.3.11.3.2 O-Cloud Identity Pillar Gap Analysis - -**Table O-Cloud Gap Analysis-39: O-Cloud Identity Pillar Gap Analysis** - -| Identity ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|----------| -| Authentication |

The system authenticates identity using MFA, which may include passwords as one factor and requires validation of multiple entity attributes (e.g., locale or activity).

a) If there is mutual authentication for internal communications, we consider the stage as

| O-Cloud Identity Pillar Assets | | | | -| | | ASSET-C-08 | REQ-SEC-OCLOUD-1
REQ-SEC-OCLOUD-INST-ID-1
REQ-SEC-OCLOUD-COT-1
REQ-SEC-OCLOUD-COT-2
REQ-SEC-OCLOUD-PKG-2
REQ-SEC-AALIC-Mgmt-1 | No gap | | - -| | | | | | | -|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|----------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

INITIAL.

b) For internal interfaces, authentication based on credentials alone (certificate, pre-shared key, etc.) can be considered as meeting INITIAL maturity level.

| | REQ-SEC-AAL1-C-Mgmt-2
REQ-SEC-OCLOUD-SW-1 | | | -| | | ASSET-C-29 | None | Gap |

Out of scope, the AAL software at runtime is a low-level process / library that is used by AAL applications.

Method/function calls are made to access the AAL implementation / libraries and identity requirements for method calls are not considered.

| -| | | ASSET-C-30 | REQ-SEC-AAL1-VS-1
REQ-SEC-AAL3 | Partial gap |

Missing security controls are not considered as a gap.

Out of scope, Method/function calls are made to access the AAL implementation / libraries and identity requirements for method calls are not considered.

| -| Access Management (Authorization) |

The system authorizes access, including for privileged access requests, that expires with automated review.

a) This function applies to APIs and user access.

b) For applications, static role assignments (e.g. role binding of a service account) with ephemeral tokens can be considered as INITIAL stage.

| O-Cloud Identity Pillar Assets | | | | -| | | ASSET-C-08 | REQ-SEC-OCLOUD-2
REQ-SEC-OCLOUD-3
SEC-CTL-OCLOUD-1
REQ-SEC-OCLOUD-ISO-1
REQ-SEC-OCLOUD-ISO-7 | No gap | | -| | | ASSET-C-29 | REQ-SEC-AAL1-VS-2
REQ-SEC-OCLOUD-ISO-7 | Partial gap |

Missing security controls are not considered as a gap.

Out of scope, Method/function calls are made to access the AAL implementation / libraries and identity requirements for method calls are not considered.

| -| | | ASSET-C-30 | REQ-SEC-OCLOUD-ISO-7 | Partial gap |

Missing security controls are not considered as a gap.

| - -| | | | | | | -|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | | Out of scope, Method/function calls are made to access the AAL implementation / libraries and identity requirements for method calls are not considered. | -| Visibility and Analytics Capability | O-Cloud Identity Pillar Assets | | | | | -| | a) Collecting user and entity activity logs. | ASSET-C-08 | REQ-SEC-SLM-TESS-3 | Partial gap |
  • Security log requirements enable the generation of security logs, but analysis, automation, and correlation are not specified.
  • Analysis, automation, and correlation are considered out of scope for O-RAN. As specified in [i31Z], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE.
| -| | b) Performing Routine Analysis:
  • a. Conduct regular manual analysis of the logs.
  • b. Implement some automated analysis, with limited correlation between different log types.
| ASSET-C-29 | REQ-SEC-SLM-TESS-3 | Partial gap |
  • Security log requirements enable the generation of security logs, but analysis, automation, and correlation are not specified.
  • Analysis, automation, and correlation are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE.
| -| | | ASSET-C-30 | REQ-SEC-SLM-TESS-3 | Partial gap |
  • Security log requirements enable the generation of security logs, but analysis, automation, and correlation are not specified.
  • Analysis, automation, and correlation are considered out of scope for O-RAN. As specified in [i.31], SIEM is not
| - -| | | | | | | -|-----------------------------------------|--------------------------------------------------------------|------------|--------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | | within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | O-Cloud Identity Pillar Assets | | | | | -| | a) Manually orchestrates privileged and external identities. | ASSET-C-08 | REQ-SEC-SLM-TESS-3 | No gap |
  • Security log requirements enable the generation of security logs, but analysis, automation, and correlation are not specified.
  • Analysis, automation, and correlation are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE.
| -| | b) Automates orchestration of non-privileged users. | ASSET-C-29 | REQ-SEC-SLM-TESS-3 | No gap |
  • Security log requirements enable the generation of security logs, but analysis, automation, and correlation are not specified.
  • Analysis, automation, and correlation are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE.
| -| | c) Automates orchestration of self-managed entities. | ASSET-C-30 | REQ-SEC-SLM-TESS-3 | No gap |
  • Security log requirements enable the generation of security logs, but analysis, automation, and correlation are not specified.
  • Analysis, automation, and correlation are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-
| - -| | | | | | | -|--|--|--|--|--|---------------| -| | | | | | RAN ALLIANCE. | -|--|--|--|--|--|---------------| - -### 7.3.11.4 O-Cloud Networks Pillar - -#### 7.3.11.4.1 O-Cloud Networks Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-C-08: O-Cloud (Covers DMS and IMS and their services) - -NOTE: O2 interface's networks pillar assets are covered in clause 7.3.12.4 - -#### 7.3.11.4.2 O-Cloud Networks Pillar Gap Analysis - -**Table O-Cloud Gap Analysis-40: O-Cloud Networks Pillar Gap Analysis** - -| Networks ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Traffic Encryption | Encryption for all internal (and preferably external) application traffic, with formalized key management policies and secure encryption keys. | O-Cloud Networks Pillar Assets | | | | -| | | ASSET-C-08 | REQ-SEC-OCLOUD-ISO-5
SEC-CTL-O-CLOUD-ISO-2
REQ-SEC-OCLOUD-SS-1 (See NOTE 1)
SEC-CTL-OCLOUD-SS-1
REQ-SEC-AALI-C-Mgmt-3
SEC-CTL-AALI-C-Mgmt-1
REQ-SEC-AAL-VS-3
REQ-SEC-AAL-VS-4 | Partial gap | Out of scope, AALI-C-App and AALI-P APIs are implemented at lower level as function/method calls within AAL implementation and not over a network interface. Security requirements for method calls are not considered. | -| Visibility and Analytics Capability | a) Utilize network monitoring capabilities based on known indicators of compromise, including network enumeration, to develop situational awareness in each environment.

b) Commence correlating telemetry across traffic types and environments to facilitate analysis | O-Cloud Networks Pillar Assets | | | | -| | | ASSET-C-08 | REQ-SEC-SLM-NET-EVT-1 | Partial gap |
  • • The provided requirement enables the generation of information related to network events, but analysis, and correlation are not specified.
  • • Providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of
| - -| | | | | | | -|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|------|-----|-----------------------------------------------------------------------------------------------------------------------------------| -| | and threat hunting activities. | | | | scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments.

b) Ensure that all resources have a defined lifetime determined by policies and telemetry data. | O-Cloud Networks Pillar Assets | | | | -| | | ASSET-C-08 | None | Gap | Out of scope, network resource configuration and lifecycle management fall under the operator's responsibilities. | - -NOTE 1: Encryption of data in use is considered as Optimal stage according to O-RAN ZTA Security Requirements for Data Encryption. - -### 7.3.11.5 O-Cloud Devices Pillar - -#### 7.3.11.5.1 O-Cloud Devices Pillar Assets - -The applicable assets defined in this document are as follows: - -- ZT-OCLOUD-I-X1: O-Cloud hardware -- ASSET-C-30: The hardware accelerator device firmware. -- ZT-OCLOUD-I-X2: O-Cloud OS Software. It includes firmware and host OS. -- ZT-OCLOUD-I-X5: O-Cloud Virtualization Layer. It includes hypervisors or container engines. -- ZT-OCLOUD-I-X6: O-Cloud VMs. -- ZT-OCLOUD-I-X7: O-Cloud Containers. - -#### 7.3.11.5.2 O-Cloud Devices Pillar Gap Analysis - -**Table O-Cloud Gap Analysis-41: O-Cloud Devices Pillar Gap Analysis** - -| Devices ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|-----------------------------------|--------------------------------------------------------------|-------------------------------|--------------------------------------------|------------------------------------|----------| -| Policy Enforcement and Compliance | Basic Device characteristics visibility.

Basic policy | O-Cloud Devices Pillar Assets | | | | -| | | ZT-OCLOUD-I-X1 | REQ-SEC-AAL-4
SEC-CTL-AAL-2 | No gap | | - -| | | | | | | -|-----------------|---------------------------------------------------------------------------------------------|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--| -| Monitoring | enforcement mechanism for managing software, configurations, or vulnerabilities. | ASSET-C-30 | REQ-SEC-AAL-2
REQ-SEC-AAL-3
REQ-SEC-TAP-5
REQ-SEC-SLM-NET-EVT-1
REQ-SEC-SLM-GSE-1
REQ-SEC-SLM-GSE-3
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5
REQ-SEC-SLM-GSE-6 | No gap | | -| | | ZT-OCLOUD-I-X2 | REQ-SEC-SLM-NET-EVT-1
REQ-SEC-SLM-GSE-1
REQ-SEC-SLM-GSE-3
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5
REQ-SEC-SLM-GSE-6 | No gap | | -| | | ZT-OCLOUD-I-X5 | REQ-SEC-SLM-NET-EVT-1
REQ-SEC-SLM-GSE-1
REQ-SEC-SLM-GSE-3
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5
REQ-SEC-SLM-GSE-6 | No gap | | -| | | ZT-OCLOUD-I-X6 | REQ-SEC-OCLOUD-ISO-7
REQ-SEC-SLM-NET-EVT-1
REQ-SEC-SLM-GSE-1
REQ-SEC-SLM-GSE-3
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5
REQ-SEC-SLM-GSE-6 | No gap | | -| | | ZT-OCLOUD-I-X7 | REQ-SEC-OCLOUD-ISO-7
REQ-SEC-SLM-NET-EVT-1
REQ-SEC-SLM-GSE-1
REQ-SEC-SLM-GSE-3
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5
REQ-SEC-SLM-GSE-6 | No gap | | -| Resource Access | Some visibility into devices or virtual assets' characteristics to approve resource access. | O-Cloud Devices Pillar Assets | | | | -| | | ZT-OCLOUD-I-X1 | SEC-CTL-O-CLOUD-HW-1
REQ-SEC-AAL-VS-1
REQ-SEC-AAL-1
REQ-SEC-AAL-5 (See NOTE 1) | No gap | | -| | | ASSET-C-30 | None | Gap | | - -| | | | | | | -|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | ZT-OCLOUD-I-X2 | REQ-SEC-OCLOUD-1
REQ-SEC-OCLOUD-2 | No gap | Gap resolved as requirements were identified after initial analysis | -| | | ZT-OCLOUD-I-X5 | REQ-SEC-OCLOUD-ISO-1
REQ-SEC-OCLOUD-ISO-3
REQ-SEC-OCLOUD-ISO-7 | No gap | Gap resolved as requirements were identified after initial analysis | -| | | ZT-OCLOUD-I-X6 | REQ-SEC-OCLOUD-ISO-3
REQ-SEC-OCLOUD-ISO-4
REQ-SEC-OCLOUD-SECPOL-2
REQ-SEC-OCLOUD-SECPOL-3
REQ-SEC-OCLOUD-SECPOL-5 | No gap | Gap resolved as requirements were identified after initial analysis | -| | | ZT-OCLOUD-I-X7 | REQ-SEC-OCLOUD-ISO-3
REQ-SEC-OCLOUD-ISO-4
REQ-SEC-OCLOUD-SECPOL-2
REQ-SEC-OCLOUD-SECPOL-3
REQ-SEC-OCLOUD-SECPOL-5 | No gap | Gap resolved as requirements were identified after initial analysis | -| Visibility and Analytics Capability | a) Digital Identifiers: Use digital identifiers alongside a manual inventory and endpoint monitoring of devices when available. | O-Cloud Devices Pillar Assets | | | | -| | b) Automated Analysis: Ensure some devices and virtual assets are under automated analysis (e.g., software-based scanning) for anomaly detection based on risk. | ZT-OCLOUD-I-X1
ASSET-C-30
ZT-OCLOUD-I-X2
ZT-OCLOUD-I-X5
ZT-OCLOUD-I-X6
ZT-OCLOUD-I-X7 | None | Partial gap | See clauses 2.1.3 and 3.3 of O-RAN.WG6.TS.O2IMS-INTERFACE document for more information about the O2ims_Infrastructure Monitoring services.

For logging, refer to 2.1.7 and 2.1.8 of O-RAN.WG6.TS.O2IMS-INTERFACE document, clause 3.3 of O-RAN.WG6.TS.O2-GA&P. Refer to clause 3.2 of O-RAN.WG6.TS.O2-GA&P for inventory services.

No requirements on | - -| | | | | | | -|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | | digital identifiers, endpoint monitoring, and manual inventory for O-Cloud hardware.

Analysis, automation, and correlation are out of scope. | -| Automation and Orchestration Capability | a) Utilization of monitoring and enforcement mechanisms to identify and manually disconnect or isolate non-compliant devices and virtual assets. | O-Cloud Devices Pillar Assets | | | | -| | | ZT-OCLOUD-I-X1
ASSET-C-30
ZT-OCLOUD-I-X2
ZT-OCLOUD-I-X5
ZT-OCLOUD-I-X6
ZT-OCLOUD-I-X7 | None | Gap | Out of scope, as disconnecting or isolating non-compliant devices and virtual assets fall under the operator's responsibility. | - -NOTE 1: Fine grained access to AAL applications when accessing accelerator device resources is considered as advanced stage according to O-RAN ZTA Security Requirements for Resource Access. - -### 7.3.12 O2 Interface Gap Analysis - -#### 7.3.12.1 O2 Interface Data Pillar - -##### 7.3.12.1.1 O2 interface Data Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are as follows: - -- ASSET-D-14: O-Cloud Provisioning information, O-Cloud software management information -- ASSET-D-15: O-RAN Cloudified Network Function Software -- ASSET-D-18: O-RAN components associated and configuration data - -##### 7.3.12.1.2 O2 Interface Data Pillar Gap Analysis - -**Table O2 Interface Gap Analysis-42: O2 Interface Data Pillar Gap Analysis** - -| Data ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|------------------|--------------------------------------------------------------|--------------------------|--------------------------------------------|------------------------------------|--------------------------------------------------------| -| Data Access | a) Automated data access control

b) Elements of least | O2 interface Data Assets | | | | -| | | ASSET- | N/A | No gap | No access of data being transported is defined for the | - -| | | | | | | -|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | privileges are incorporated with the automated data access control | D-14 | | | O2 interface - hence this row is marked as N/A. | -| | | ASSET-D-15 | N/A | No gap | No access of data being transported is defined for the O2 interface - hence this row is marked as N/A. | -| | | ASSET-D-18 | N/A | No gap | No access of data being transported is defined for the O2 interface - hence this row is marked as N/A. | -| Data Encryption | a) Encrypted data in transit and, where feasible, data at rest. | O2 interface Data Assets | | | | -| | b) Key management policies and secure encryption keys are beginning to be formalized. | ASSET-D-14 | REQ-SEC-OCLOUD-O2ims-2
SEC-CTL-O2-1 | No gap | | -| | | ASSET-D-15 | REQ-SEC-OCLOUD-O2ims-2
SEC-CTL-O2-1 | No gap | | -| | | ASSET-D-18 | REQ-SEC-OCLOUD-SS-1
(See NOTE 1)
SEC-CTL-OCLOUD-SS-1 | No gap | | -| Visibility and Analytics Capability | Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility | O2 interface Data Assets | | | | -| | | ASSET-D-14
ASSET-D-15
ASSET-D-18 | REQ-SEC-SLM-DAT-EVT-1
REQ-SEC-SLM-DAT-EVT-2
REQ-SEC-SLM-DAT-EVT-3
REQ-SEC-SLM-DAT-EVT-4
REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5 | Partial gap | O2 information model covers data inventory management for O2 data, refer to O-RAN.WG6.O-CLOUD-IM.0-R004-v04.00.

Creating and providing the required information is. within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | Data lifecycle and security policies (e.g., access, usage, storage, encryption, configurations, protections, backups, | O2 interface Data Assets | | | | -| | | ASSET-D-14
ASSET-D-15
ASSET-D-18 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | - -| | | | | | | -|--|-----------------------------------|--|--|--|--| -| | categorization, sanitization) are | | | | | -|--|-----------------------------------|--|--|--|--| - -NOTE 1: Encryption of data in use is considered as Optimal stage according to O-RAN ZTA Security Requirements for Data Encryption. - -### 7.3.12.2 O2 Interface Applications and Workloads Pillar - -#### 7.3.12.2.1 O2 interface Applications and Workloads Pillar Assets - -- No asset applicable to specific pillar. - -#### 7.3.12.2.2 O2 Interface Applications and Workloads Pillar Gap Analysis - -- No asset applicable to specific pillar. - -### 7.3.12.3 O2 Interface Identity Pillar - -#### 7.3.12.3.1 O2 interface Identity Pillar Assets - -- No asset applicable to specific pillar. - -#### 7.3.12.3.2 O2 Interface Identity Pillar Gap Analysis - -- No asset applicable to specific pillar. - -### 7.3.12.4 O2 Interface Networks Pillar - -#### 7.3.12.4.1 O2 interface Networks Pillar Assets - -The applicable assets defined in this document are as follows: - -- ZT-OCLOUD-S-X1: O2ims services -- ZT-OCLOUD-S-X2: O2dms services - -#### 7.3.12.4.2 O2 Interface Networks Pillar Gap Analysis - -**Table O2 Interface Gap Analysis-43: O2 Interface Networks Pillar Gap Analysis** - -| Networks ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|----------------------|--------------------------------------------------------------------------------------------|-------------------------------------|--------------------------------------------|------------------------------------|----------| -| Traffic Encryption | Encryption for all internal (and preferably external) application traffic, with formalized | O2 interface Networks Pillar Assets | | | | -| | | ZT-OCLOUD-S-X1 | REQ-SEC-OCLOUD-O2ims-2
REQ-SEC-O2-1 | No gap | | - -| | | | | | | -|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------|--------------------------------------------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | key management policies and secure encryption keys. | | SEC-CTL-O2-1 | | | -| | | ZT-OCLOUD-S-X2 | REQ-SEC-OCLOUD-O2dms-2
REQ-SEC-O2-1
SEC-CTL-O2-1 | No gap | | -| Visibility and Analytics Capability |

a) Utilize network monitoring capabilities based on known indicators of compromise, including network enumeration, to develop situational awareness in each environment.

b) Commence correlating telemetry across traffic types and environments to facilitate analysis and threat hunting activities.

| O2 interface Networks Pillar Assets | | | | -| | | ZT-OCLOUD-S-X1 | None | Partial gap |

See clauses 2.1.3 and 3.3 of O-RAN.WG6.TS.O2IMS-INTERFACE document for more information about the O2ims_InfrastructureMonitoring services.

For logging, refer to 2.1.7 and 2.1.8 of O-RAN.WG6.TS.O2IMS-INTERFACE document, clause 3.3 of O-RAN.WG6.TS.O2-GA&P.

Refer to clause 3.2 of O-RAN.WG6.TS.O2-GA&P for inventory services.

No requirements for providing network monitoring information.

Providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE.

| -| | | ZT-OCLOUD-S-X2 | None | Partial gap |

See clauses 2.1.3 and 3.3 of O-RAN.WG6.TS.O2IMS-INTERFACE document for more information about the O2ims_InfrastructureMonitoring services.

For logging, refer to 2.1.7 and 2.1.8 of O-RAN.WG6.TS.O2IMS-INTERFACE document, clause 3.3 of O-RAN.WG6.TS.O2-GA&P.

Refer to clause 3.2 of O-RAN.WG6.TS.O2-GA&P for

| - -| | | | | | | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------|------|-----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | |

inventory services.

No requirements for providing network monitoring information.

Providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE.

| -| Automation and Orchestration Capability |

a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments.

b) Ensure that all resources have a defined lifetime determined by policies and telemetry data.

| O2 interface Networks Pillar Assets | | | | -| | |

ZT-OCLOUD-S-X1

ZT-OCLOUD-S-X2

| None | Gap | Out of scope, network resource configuration and lifecycle management fall under the operator's responsibilities. | - -### 7.3.12.5 O2 Interface Devices Pillar - -#### 7.3.12.5.1 O2 interface Devices Pillar Assets - -- No asset applicable to specific pillar. - -#### 7.3.12.5.2 O2 Interface Devices Pillar Gap Analysis - -- No asset applicable to specific pillar. - -### 7.3.13 O-CU Gap Analysis - -#### 7.3.13.1 O-CU Data Pillar - -##### 7.3.13.1.1 O-CU Data Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modelling and Risk Assessment [i.4] are listed below. The O-CU also has O1 and E2 interfaces as well, which are discussed separately in clauses 7.3.10 and 7.3.4 respectively. - -The assets associated with the O-CU are: - -- ASSET-D-03: M-Plane O1 Data - -- ASSET-D-11: E2 Node Data (at rest) -- ASSET-D-16: X.509 certificates -- ASSET-D-17: Private keys -- ASSET-D-18: O-RAN components associated and configuration data. -- ASSET-D-19: ETSI TS 133 501 cryptographic keys -- ASSET-D-20: Credentials (Administrators) -- ASSET-D-21: 3GPP application related data -- ASSET-D-22: Inter- and Intra- slice UE priority -- ASSET-D-23: Patches for vulnerable SW components -- ASSET-D-24: NETCONF Configuration Access Control Model datastores. -- ASSET-D-29: Security event log files. -- ASSET-D-31: Security telemetry from the O-Cloud for detecting threats and anomalies. -- ASSET-D-32: Cryptographic keys used during secure boot - -### 7.3.13.1.2 O-CU Data Pillar Gap Analysis - -**Table O-CU Gap Analysis-44: O-CU Data Pillar Gap Analysis** - -| Data ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|------------------|---------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|-------------------------------------------------------| -| Data Access | a) Automated data access control

b) Elements of least privileges are incorporated with the automated data access control | ASSET-D-03 | REQ-TLS-FUN-2
REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11 | No gap | | -| | | ASSET-D-11 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-16 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-17 | REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-4
Clause 5.3.5 [i.17] | No gap | | -| | | ASSET-D-18 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-19 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-20 | REQ-SEC-PASS-1 | Gap | Authentication and | - -| | | | | | | -|-----------------|------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|------------------------------------------------------------| -| | | | SEC-CTL-PASS-1
SEC-CTL-PASS-2
SEC-CTL-PASS-3 | | authorization controls not defined | -| | | ASSET-D-21 | None | Gap | May be outside of scope for O-RAN ALLIANCE | -| | | ASSET-D-22 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-23 | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1
SEC-CTL-ALM-PKG-2 | No gap | | -| | | ASSET-D-24 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-29 | REQ-SEC-SLM-TESS-6
REQ-SEC-SLM-TESS-7
REQ-SEC-SLM-TESSM-1
REQ-SEC-SLM-TESSM-3
REQ-SEC-TESR-1
REQ-SEC-TESR-7
REQ-SEC-TESR-9
REQ-SEC-TESR-11
REQ-SEC-SLM-SST-4
REQ-SEC-SLM-STR-2 | No gap | | -| | | ASSET-D-31 | REQ-SEC-SLM-TESS-6
REQ-SEC-SLM-TESS-7
REQ-SEC-SLM-TESSM-1
REQ-SEC-SLM-TESSM-3
REQ-SEC-TESR-1
REQ-SEC-TESR-7
REQ-SEC-TESR-9
REQ-SEC-TESR-11
REQ-SEC-SLM-SST-4
REQ-SEC-SLM-STR-2 | No gap | | -| | | ASSET-D-32 | None | Gap | Authentication and authorization controls not defined | -| Data Encryption | a) Encrypted data in transit and, where feasible, data at rest. | ASSET-D-03 | None | Gap | Requirements around authentication and authorization only. | -| | | ASSET-D-11 | None | No gap | Confidentiality not listed as requirement for asset. | -| | b) Key management policies and secure encryption keys are beginning to | ASSET-D-16 | REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-2

Clause 5.3.5 [i.17], | No gap | | -| | | ASSET-D-17 | REQ-SEC-OCLOUD-SS-1
REQ-SEC-ALM-PKG-13 | No gap | | - -| | | | | | | -|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| be formalized. | | | SEC-CTL-OCLOUD-SS-1
SEC-CTL-ALM-PKG-2
SEC-CTL-ALM-PKG-4

Clause 5.3.5 [i.17] | | | -| | | ASSET-D-18 | REQ-SEC-ALM-PKG-13 | Possible gap | Requirement is too general | -| | | ASSET-D-19 | Clause 5.3.5 [i.17] | No gap | | -| | | ASSET-D-20 | REQ-SEC-OCLOUD-SS-1
REQ-SEC-ALM-PKG-13
SEC-CTL-OCLOUD-SS-1
SEC-CTL-ALM-PKG-2 | No gap | | -| | | ASSET-D-21 | Clause 5.3.8 [i.17] | No gap | | -| | | ASSET-D-22 | None | No gap | Confidentiality not listed as requirement for asset. | -| | | ASSET-D-23 | REQ-SEC-ALM-PKG-10 | No gap | | -| | | ASSET-D-24 | REQ-SEC-ALM-PKG-13 | No gap | No encryption in transit or rest | -| | | ASSET-D-29 | REQ-SEC-SLM-TESM-2
REQ-SEC-TESR-6
REQ-SEC-SLM-STR-1 | No gap | | -| | | ASSET-D-31 | REQ-SEC-SLM-TESM-2
REQ-SEC-TESR-6
REQ-SEC-SLM-STR-1 | No gap | | -| | | ASSET-D-32 | Clause 5.3.5 [i.17] | No gap | Would apply to data at rest only. | -| Visibility and Analytics Capability | Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | ASSET-D-03
ASSET-D-11
ASSET-D-16
ASSET-D-17
ASSET-D-18
ASSET-D-19
ASSET-D-20
ASSET-D-21
ASSET-D-22
ASSET-D-23
ASSET-D-24
ASSET-D-29
ASSET-D-31
ASSET-D-32 | REQ-SEC-SLM-DAT-EVT-1
REQ-SEC-SLM-DAT-EVT-2
REQ-SEC-SLM-DAT-EVT-3
REQ-SEC-SLM-DAT-EVT-4
REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5 | Partial gap | Data inventory and data categorization are out of scope for O-RAN specifications.

Creating and providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| Automation and | Data lifecycle and security | ASSET-D-03 | None | Gap | Out of scope, as data lifecycle and security policies fall under the | - -| | | | | | | -|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------|------------|------|-----|---------------------------------------------------------------------------------------------------| -| Orchestration Capability | policies (e.g., access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) are automated. | | | | operator's responsibilities. | -| | | ASSET-D-11 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-16 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-17 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-18 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-19 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-20 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-21 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-22 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-23 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-24 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-29 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-31 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-32 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | - -### 7.3.13.2 O-CU Application and Workloads Pillar - -#### 7.3.13.2.1 O-CU Application and Workloads Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are listed below. The O-CU also has O1 and E2 interfaces as well, which are discussed separately in clauses 7.3.10 and 7.3.4 respectively. The O-CU specific assets are as follows: - -- ASSET-C-03: O-CU-UP -- ASSET-C-04: O-CU-CP -- ASSET-C-36: CU-Host (Including software) -- ASSET-C-37: CU-Tenant (Including software) - -#### 7.3.13.2.2 O-CU Application and Workloads Pillar Gap Analysis - -Note that in Table O-CU Gap Analysis-45 below, the O-CU asset(s) are grouped together as the requirements and controls are apply at the NF level. - -**Table O-CU Gap Analysis-45: O-CU Application and Workloads Pillar Gap Analysis** - -| App/Workloads ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|--------------------------------------------|------------------------------------|------------------------------------------------------------------------------------| -| Application Access (Authorization) | a) Access authorization capabilities utilize contextual information such as identity, device compliance, and other attributes to make decisions on various requests for accessing application assets.

b) Authorization is granted per request with expiration. | ASSET-C-03
ASSET-C-04
ASSET-C-36
ASSET-C-37 | See [i.24] | Partial gap | Some contextual information may be operational and out of scope for specification. | -| Application Threat Protections | a) Threat protections is integrated into mission-critical application workflows.

b) Threat protections safeguard applications against known threats and address some application-specific threats. | ASSET-C-03
ASSET-C-04
ASSET-C-36
ASSET-C-37 | REQ-SEC-ALM-SU-2
REQ-SEC-ALM-SU-3 | No gap | | -| Accessible Applications | a) Applicable mission-critical applications are available over open public network connections to | ASSET-C-03
ASSET-C-04
ASSET-C-36
ASSET-C-37 | See [i.17] | No gap | Out of scope for O-RAN

No identified Mission critical | - -| | | | | | | -|--------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|------------------------------------------------------------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | authorized users as needed. | | | | applications
Requirements specified in 3GPP | -| Secure Application Development and Deployment Workflow | a) Infrastructure for development, testing, and production environments (including automation).

b) Formal code deployment mechanisms through CI/CD pipelines.

c) Access controls support least privilege principles. | ASSET-C-03
ASSET-C-04
ASSET-C-36
ASSET-C-37 | | Gap | Out of scope for O-RAN

Securing infrastructure for development, testing, and production environments is out of scope for O-RAN. | -| Application Security Testing | a) Utilization of static and dynamic testing methods for security testing.

b) Performance of security testing including manual expert analysis before application deployment. | ASSET-C-03
ASSET-C-04
ASSET-C-36
ASSET-C-37 | REQ-SEC-ALM-PKG-1
REQ-SEC-ALM-PKG-7b | No gap | Guidance (b) is out of scope for O-RAN. | -| Visibility and Analytics Capability | Initiate the automation of application profile (e.g., state, health, and performance) and security monitoring processes for improved log collection, aggregation, and analytics. | ASSET-C-03
ASSET-C-04
ASSET-C-36
ASSET-C-37 | REQ-SEC-SLM-FLD-1
REQ-SEC-SLM-FLD-2
REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-5 | Partial gap | These requirements allow for the inclusion of application profile information in security logs. However, the automation of application profile monitoring processes and analytics is not addressed.

Log collection, aggregation, and analytics are out of scope. | -| Automation and Orchestration Capability | Periodically modifies application configurations, including location and | ASSET-C-03
ASSET-C-04
ASSET-C-36 | None | Gap | Out of scope, as application configuration falls under | - -| | | | | | | -|--|---------------------------------------------------------------------------------|------------|--|--|-----------------------------| -| | access parameters, to align with pertinent security and performance objectives. | ASSET-C-37 | | | operator's responsibilities | -|--|---------------------------------------------------------------------------------|------------|--|--|-----------------------------| - -### 7.3.13.3 O-CU Identity Pillar - -#### 7.3.13.3.1 O-CU Identity Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are listed below. The O-CU is considered a singular NF in terms of identity and does not have separate identities for each interface. The assets are listed as follows: - -- ASSET-C-12a: PNF NF equipment -- ASSET-C-36: CU-Host (Including software). -- ASSET-C-37: CU-Tenant (Including software). - -#### 7.3.13.3.2 O-CU Identity Pillar Gap Analysis - -**Table O-CU Gap Analysis-46: O-CU Identity Pillar Gap Analysis** - -| Networks ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------------|------------------------------------|----------| -| Authentication |

The system authenticates identity using MFA, which may include passwords as one factor and requires validation of multiple entity attributes (e.g. locale or activity).

a) if there is mutual authentication for internal communications, we consider the stage as INITIAL.

b) For internal interfaces, authentication based on credentials alone (certificate, pre-shared key, etc.) can be considered as meeting INITIAL maturity level.

| ASSET-C-12a | See [i.17][i.25] | No gap | | -| | | ASSET-C-36 | See [i.17][i.25] | No gap | | -| | | ASSET-C-37 | See [i.17][i.25] | No gap | | -| Access Management (Authorization) | The system authorizes access, including for privileged access requests, that expires with automated | ASSET-C-12a | See [i.17][i.25] | No gap | | - -| | | | | | | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | review.

a) This function applies to APIs and user accounts.

b) For applications, static role assignments (e.g. role binding of a service account) with ephemeral tokens can be considered as INITIAL stage. | ASSET-C-36 | See [i.17][i.25] | No gap | | -| | | ASSET-C-37 | See [i.17][i.25] | No gap | | -| Visibility and Analytics Capability | a) Collecting user and entity activity logs. | ASSET-C-12a | REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-13 | Partial gap | Security log requirements enable generation of security logs, but analysis, automation, and correlation are not specified.

Analysis, automation, and correlation are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE. | -| | b) Performing Routine Analysis:
a. Conduct regular manual analysis of the logs.
b. Implement some automated analysis, with limited correlation between different log types. | ASSET-C-36 | REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-13 | Partial gap | | -| | | ASSET-C-37 | REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-13 | Partial gap | | -| Automation and Orchestration Capability | a) Manually orchestrates privileged and external identities.
b) Automates orchestration of non-privileged users.
c) Automates orchestration of self-managed entities. | ASSET-C-12a | None | Gap | Out of scope, as user and identity orchestration falls under operator's responsibilities. | -| | | ASSET-C-36 | None | Gap | Out of scope, as user and identity orchestration falls under operator's responsibilities. | -| | | ASSET-C-37 | None | Gap | Out of scope, as user and identity orchestration falls under operator's responsibilities. | - -### 7.3.13.4 O-CU Networks Pillar - -#### 7.3.13.4.1 O-CU Networks Pillar Assets - -Currently there are no applicable assets or components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] for O-CU Network pillar. - -#### 7.3.13.4.2 O-CU Networks Pillar Gap Analysis - -No gap analysis required. - -### 7.3.13.5 O-CU Devices Pillar - -#### 7.3.13.5.1 O-CU Devices Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are listed below. The O-CU specific assets are as follows: - -- ASSET-C-12a: PNF NF equipment - -#### 7.3.13.5.2 O-CU Devices Pillar Gap Analysis - -**Table O-CU Gap Analysis-47: O-CU Devices Pillar Gap Analysis** - -| Devices ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|-------------------------------------------------| -| Policy Enforcement and Compliance Monitoring | Basic Device characteristics visibility. Basic policy enforcement mechanism for managing software configurations or vulnerabilities | ASSET-C-12a | REQ-SEC-TAP-5
REQ-SEC-SLM-NET-EVT-1
REQ-SEC-SLM-GSE-1
REQ-SEC-SLM-GSE-3
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5
REQ-SEC-SLM-GSE-6
See [i.17] | No gap | | -| Resource Access (Authorization ) | Some visibility into devices or virtual assets' characteristics to approve resource access | ASSET-C-12a | REQ-SEC-SLM-NET-EVT-1
REQ-SEC-SLM-GSE-6 | No gap | | -| Device Threat Protection | Some automated processes for deploying and updating threat protection capabilities to devices and to virtual assets with limited policy enforcement and compliance monitoring | ASSET-C-12a | REQ-SEC-SLM-NET-EVT-1 | Partial gap | REQ-SEC-ALM-PKG applies to VNF/CNF and not PNFs | - -| | | | | | | -|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|------|-----|--------------------------------------------------------------------------------------------------------------------------------| -| | integration. | | | | | -| Visibility and Analytics Capability | a) Use digital identifiers alongside a manual inventory and endpoint monitoring of devices when available
b) Automated analysis: Ensure some devices and virtual assets (e.g., software-based scanning) for anomaly detection based on risk. | ASSET-C-12a | None | Gap | Out of scope, as endpoint inventory management fall under the operator's responsibility. | -| Automation and Orchestration Capability | Utilization of monitoring and enforcement mechanisms to identify and manually disconnect or isolate non-compliant devices and virtual assets. | ASSET-C-12a | None | Gap | Out of scope, as disconnecting or isolating non-compliant devices and virtual assets fall under the operator's responsibility. | - -## 7.3.14 O-DU Gap Analysis - -### 7.3.14.1 O-DU Data Pillar - -#### 7.3.14.1.1 O-DU Data Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modelling and Risk Assessment [i.4] are listed below. The O-DU also has O1 and E2 interfaces as well, which are discussed separately in clauses 7.3.10 and 7.3.4 respectively. - -The unique assets associated with the O-DU are: - -- ASSET-D-01: Critical S-Plane Data -- ASSET-D-02: Critical M-Plane Data transported over Fronthaul -- ASSET-D-03: M-Plane O1 Data -- ASSET-D-04: Critical C-Plane Data -- ASSET-D-05: Critical Fronthaul U-Plane data -- ASSET-D-11: E2 Node Data (at rest) -- ASSET-D-16: X.509 certificates -- ASSET-D-17: Private keys -- ASSET-D-18: O-RAN components associated and configuration data. -- ASSET-D-20: Credentials (Administrators) -- ASSET-D-22: Inter- and Intra- slice UE priority -- ASSET-D-23: Patches for vulnerable SW components -- ASSET-D-24: NETCONF Configuration Access Control Model datastores. -- ASSET-D-29: Security event log files. - -- ASSET-D-31: Security telemetry from the O-Cloud for detecting threats and anomalies. -- ASSET-D-32: Cryptographic keys used during secure boot - -7.3.14.1.2 O-DU Data Pillar Gap Analysis - -**Table O-DU Gap Analysis-48: O-DU Data Pillar Gap Analysis** - -| Data ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|------------------|-----------------------------------------------------------------------------------------|------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|-------------------------------------------------------| -| Data Access | a) Automated data access control | ASSET-D-01 | None | Gap | Authentication and authorization controls not defined | -| | b) Elements of least privileges are incorporated with the automated data access control | ASSET-D-02 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-03 | REQ-TLS-FUN-2
REQ-NAC-FUN-1
REQ-NAC-FUN-2
REQ-NAC-FUN-3
REQ-NAC-FUN-4
REQ-NAC-FUN-5
REQ-NAC-FUN-6
REQ-NAC-FUN-7
REQ-NAC-FUN-8
REQ-NAC-FUN-9
REQ-NAC-FUN-10
REQ-NAC-FUN-11 | No gap | | -| | | ASSET-D-04 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-05 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-11 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-16 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-17 | REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-4
Clause 5.3.5 [i.17] | No gap | | -| | | ASSET-D-18 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-20 | REQ-SEC-PASS-1 | Gap | Authentication and | - -| | | | | | | -|-----------------|---------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------|--------|-------------------------------------------------------------------------------------| -| | | | SEC-CTL-PASS-1
SEC-CTL-PASS-2
SEC-CTL-PASS-3 | | authorization controls not defined | -| | | ASSET-D-22 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-23 | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1 | No gap | | -| | | ASSET-D-24 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-29 | REQ-SEC-SLM-TESS-6
REQ-SEC-SLM-TESM-3
REQ-SEC-TESR-1
REQ-SEC-SLM-TESR-5
REQ-SEC-TESR-7
REQ-SEC-TESR-9
REQ-SEC-TESR-11 | No gap | | -| | | ASSET-D-31 | REQ-SEC-SLM-TESS-6
REQ-SEC-SLM-TE-5
REQ-SEC-TESR-1
REQ-SEC-TESR-7
REQ-SEC-TESR-9
REQ-SEC-TESR-11 | No gap | | -| | | ASSET-D-32 | None | Gap | There are requirements for secure storage and boot, but not access of key material. | -| Data Encryption | a) Encrypted data in transit and, where feasible, data at rest. | ASSET-D-01 | REQ-SEC-OFSP-8 | No gap | | -| | | ASSET-D-02 | See [i.26] | No gap | | -| | | ASSET-D-03 | See [i.24] | No gap | | -| | b) Key management policies and secure encryption keys are beginning to be formalized. | ASSET-D-04 | REQ-SEC-OFCP-4
SEC-CTL-OFCP-1 | No gap | | -| | | ASSET-D-05 | Clause 6.6 [i.17] | No gap | | -| | | ASSET-D-11 | None | Gap | Data at rest only, see clause 7.3.4 for E2 data in transit | -| | | ASSET-D-16 | REQ-SEC-OCLOUD-SS-1
REQ-SEC-ALM- | No gap | | - -| | | | | | | -|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | PKG-13
See [i.24],[i.25] | | | -| | | ASSET-D-17 | REQ-SEC-OCLOUD-SS-1
REQ-SEC-ALM-PKG-13
See [i.24],[i.25] | No gap | | -| | | ASSET-D-18 | REQ-SEC-ALM-PKG-13 | Possible gap | Requirement is too general | -| | | ASSET-D-20 | REQ-SEC-ALM-PKG-13 | No gap | | -| | | ASSET-D-22 | See [i.24],[i.25] | No gap | | -| | | ASSET-D-23 | REQ-SEC-ALM-PKG-10 | No gap | | -| | | ASSET-D-24 | REQ-SEC-ALM-PKG-13 | No gap | | -| | | ASSET-D-29 | REQ-SEC-SLM-TESS-6
REQ-SEC-SLM-TESS-7
REQ-SEC-SLM-TESM-2 | No gap | | -| | | ASSET-D-31 | REQ-SEC-SLM-TESS-6
REQ-SEC-SLM-TESS-7
REQ-SEC-SLM-TESM-2 | No gap | | -| | | ASSET-D-32 | See [i.17] | No gap | Data at rest. | -| Visibility and Analytics Capability | Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | ASSET-D-01
ASSET-D-02
ASSET-D-03
ASSET-D-04
ASSET-D-05
ASSET-D-11
ASSET-D-16
ASSET-D-17
ASSET-D-18
ASSET-D-20
ASSET-D-22
ASSET-D-23
ASSET-D-24
ASSET-D-29
ASSET-D-31
ASSET-D-32 | REQ-SEC-SLM-DAT-EVT-1
REQ-SEC-SLM-DAT-EVT-2
REQ-SEC-SLM-DAT-EVT-3
REQ-SEC-SLM-DAT-EVT-4
REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5 | Partial gap | Data inventory and data categorization are out of scope for O-RAN specifications.

Creating and providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| Automation and | Data lifecycle | ASSET-D-01 | None | Gap | Out of scope, as data | - -| | | | | | | -|--------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|------------|------|-----|---------------------------------------------------------------------------------------------------| -| Orchestration Capability | and security policies (e.g., access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) are automated. | | | | lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-02 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-03 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-04 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-05 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-11 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-16 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-17 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-18 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-20 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-22 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-23 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-24 | None | Gap | Out of scope, as data | - -| | | | | | | -|--|--|------------|------|-----|---------------------------------------------------------------------------------------------------| -| | | | | | lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-29 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-31 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-32 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | - -### 7.3.14.2 O-DU Applications and Workloads Pillar - -#### 7.3.14.2.1 O-DU Applications and Workloads Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are listed below. The O-DU also has O1 and E2 interfaces as well, which are discussed separately in clauses 7.3.10 and 7.3.4 respectively. The O-DU specific assets are as follows: - -- ASSET-C-05: O-DU -- ASSET-C-34: DU-Host (Including software) -- ASSET-C-35: DU-Tenant (Including software) - -#### 7.3.14.2.2 O-DU Applications and Workloads Pillar Gap Analysis - -Note that in Table O-DU Gap Analysis-49 below, the O-DU asset(s) are grouped together as the requirements and controls are apply at the NF level. - -**Table O-DU Gap Analysis-49: O-DU Applications and Workloads Pillar Gap Analysis** - -| App/Workloads ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|--------------------------------------------|------------------------------------|---------------| -| Application Access (Authorization) | a) Access authorization capabilities utilize contextual information such as identity, device compliance, and other attributes to make decisions on various requests for accessing application assets.

b) Authorization is granted per request | ASSET-C-05
ASSET-C-34
ASSET-C-35 | See [i.24] | No gap | Identity only | - -| | | | | | | -|--------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|------------------------------------------------------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| -| | with expiration. | | | | | -| Application Threat Protections |

a) Threat protections is integrated into mission-critical application workflows.

b) Threat protections safeguard applications against known threats and address some application-specific threats.

| ASSET-C-05
ASSET-C-34
ASSET-C-35 | REQ-SEC-ALM-SU-2
REQ-SEC-ALM-SU-3 | No gap | | -| Accessible Applications | a) Applicable mission-critical applications are available over open public network connections to authorized users as needed. | ASSET-C-05
ASSET-C-34
ASSET-C-35 | See [i.17] | No gap | Out of scope for O-RAN

No identified Mission critical applications

Requirements specified in 3GPP | -| Secure Application Development and Deployment Workflow |

a) Infrastructure for development, testing, and production environments (including automation).

b) Formal code deployment mechanisms through CI/CD pipelines.

c) Access controls support least privilege principles.

| ASSET-C-05
ASSET-C-34
ASSET-C-35 | None | Gap | Out of scope for O-RAN

Securing infrastructure for development, testing, and production environments is out of scope for O-RAN. | -| Application Security Testing |

a) Utilization of static and dynamic testing methods for security testing.

b) Performance of security testing including manual expert analysis before application deployment.

| ASSET-C-05
ASSET-C-34
ASSET-C-35 | REQ-SEC-ALM-PKG-1
REQ-SEC-ALM-PKG-7b | No gap | Guidance (b) is out of scope for O-RAN. | -| Visibility and Analytics Capability | Initiate the automation of application profile (e.g., state, health, and performance) and security monitoring processes for improved log collection, aggregation, | ASSET-C-05
ASSET-C-34
ASSET-C-35 | REQ-SEC-SLM-FLD-1
REQ-SEC-SLM-FLD-2
REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-5 | Partial gap | These requirements allow for the inclusion of application profile information in security logs. However, the automation of application profile monitoring | - -| | | | | | | -|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|------|-----|---------------------------------------------------------------------------------------------------------------| -| | and analytics. | | | | processes and analytics is not addressed.

Log collection, aggregation, and analytics are out of scope. | -| Automation and Orchestration Capability | Periodically modifies application configurations, including location and access parameters, to align with pertinent security and performance objectives. | ASSET-C-05
ASSET-C-34
ASSET-C-35 | None | Gap | Out of scope, as application configuration falls under operator's responsibilities. | - -### 7.3.14.3 O-DU Identity Pillar - -#### 7.3.14.3.1 O-DU Identity Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are listed below. The O-DU is considered the NF in terms of identity and the O1 or E2 interface is not considered separate. The assets are as follows: - -- ASSET-C-12a: PNF NF equipment -- ASSET-C-34: DU-Host (Including software). -- ASSET-C-35: DU-Tenant (Including software). - -#### 7.3.14.3.2 O-DU Identity Pillar Gap Analysis - -**Table O-DU Gap Analysis-50: O-DU Identity Pillar Gap Analysis** - -| Identity ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------------|------------------------------------|----------| -| Authentication | The system authenticates identity using MFA, which may include passwords as one factor and requires validation of multiple entity attributes (e.g. locale or activity).

a) if there is mutual authentication for internal communications, we consider the stage as INITIAL. | ASSET-C-12a | See [i.17] | No gap | | -| | | ASSET-C-34 | See [i.17] | No gap | | -| | | ASSET-C-35 | See [i.17] | No gap | | - -| | | | | | | -|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | b) For internal interfaces, authentication based on credentials alone (certificate, pre-shared key, | | | | | -| Access Management (Authorization) | The system authorizes access, including for privileged access requests, that expires with automated review. | ASSET-C-12a | See [i.17] | No gap | | -| | c) This function applies to APIs and user accounts. | ASSET-C-34 | See [i.17] | No gap | | -| | d) For applications, static role assignments (e.g. role binding of a service account) with ephemeral tokens can be considered as INITIAL stage. | ASSET-C-35 | See [i.17] | No gap | | -| Visibility and Analytics Capability | a) Collecting user and entity activity logs.
b) Performing Routine Analysis:
a. Conduct regular manual analysis of the logs.
b. Implement some automated analysis, with limited correlation between different log types. | ASSET-C-12a | REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-13 | Partial gap | Security log requirements enable generation of security logs, but analysis, automation, and correlation are not specified.

Analysis, automation, and correlation are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE. | -| | | ASSET-C-34 | REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-13 | Partial gap | | -| | | ASSET-C-35 | REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-13 | Partial gap | | -| Automation and Orchestration Capability | a) Manually orchestrates privileged and external identities.
b) Automates orchestration of non-privileged users.
c) Automates orchestration of self-managed entities. | ASSET-C-12a | None | Gap | Out of scope, as Identities orchestration fall under the operator's responsibilities | -| | | ASSET-C-34 | None | Gap | Out of scope, as Identities orchestration fall under the operator's responsibilities | -| | | ASSET-C-35 | None | Gap | Out of scope, as Identities | - -| | | | | | | -|--|--|--|--|--|----------------------------------------------------------| -| | | | | | orchestration fall under the operator's responsibilities | -|--|--|--|--|--|----------------------------------------------------------| - -### 7.3.14.4 O-DU Networks Pillar - -#### 7.3.14.4.1 O-DU Networks Pillar Assets - -Currently there are no applicable assets or components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] for O-DU Network pillar. - -#### 7.3.14.4.2 O-DU Networks Pillar Gap Analysis - -No gap analysis required. - -### 7.3.14.5 O-DU Devices Pillar - -#### 7.3.14.5.1 O-DU Devices Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4]. The O-DU specific assets are as follows: - -- ASSET-C-12a: PNF NF equipment - -#### 7.3.14.5.2 O-DU Devices Pillar Gap Analysis - -**Table O-DU Gap Analysis-51: O-DU Devices Pillar Gap Analysis** - -| Devices ZT Function | Guidance to Reach Initial Stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap to Initial CISA Stage | Comments | -|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|----------------------------------------| -| Policy Enforcement and Compliance Monitoring | Basic Device characteristics visibility. Basic policy enforcement mechanism for managing software configurations or vulnerabilities | ASSET-C-12a | REQ-SEC-TAP-5
REQ-SEC-SLM-NET-EVT-1
REQ-SEC-SLM-GSE-1
REQ-SEC-SLM-GSE-3
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5
REQ-SEC-SLM-GSE-6

See [i.17] | No gap | | -| Resource Access (Authorization ) | Some visibility into devices or virtual assets' characteristics to approve resource access | ASSET-C-12a | REQ-SEC-SLM-NET-EVT-1
REQ-SEC-SLM-GSE-6 | No gap | | -| Device Threat Protection | Some automated processes for deploying and updating threat | ASSET-C-12a | REQ-SEC-SLM-NET-EVT-1 | Partial gap | REQ-SEC-ALM-PKG applies to VNF/CNF and | - -| | | | | | | -|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|------|-----|--------------------------------------------------------------------------------------------------------------------------------| -| | protection capabilities to devices and to virtual assets with limited policy enforcement and compliance monitoring integration. | | | | not PNFs | -| Visibility and Analytics Capability | a) Use digital identifiers alongside a manual inventory and endpoint monitoring of devices when available
b) Automated analysis: Ensure some devices and virtual assets (e.g., software-based scanning) for anomaly detection based on risk. | ASSET-C-12a | None | Gap | Out of scope, as endpoint inventory management fall under the operator's responsibility. | -| Automation and Orchestration Capability | Utilization of monitoring and enforcement mechanisms to identify and manually disconnect or isolate non-compliant devices and virtual assets. | ASSET-C-12a | None | Gap | Out of scope, as disconnecting or isolating non-compliant devices and virtual assets fall under the operator's responsibility. | - -### 7.3.15 O-RU Gap Analysis - -#### 7.3.15.1 O-RU Data Pillar - -##### 7.3.15.1.1 O-RU Data Pillar Assets - -The applicable assets defined in the WG11 O-RAN Security Threat Modelling and Risk Assessment [i.4] are listed below. - -The unique assets associated with the O-RU are: - -- ASSET-D-01: Critical S-Plane Data -- ASSET-D-02: Critical M-Plane Data transported over Fronthaul -- ASSET-D-04: Critical C-Plane Data -- ASSET-D-05: Critical Fronthaul U-Plane data -- ASSET-D-06: Reference signals, synchronization signal and channels in downlink and uplink between O-RU and UE -- ASSET-D-16: X.509 certificates -- ASSET-D-17: Private keys - -- ASSET-D-18: O-RAN components associated and configuration data. -- ASSET-D-20: Credentials (Administrators) -- ASSET-D-23: Patches for vulnerable SW components -- ASSET-D-24: NETCONF Configuration Access Control Model datastores. -- ASSET-D-29: Security event log files. -- ASSET-D-32: Cryptographic keys used during secure boot - -7.3.15.1.2 O-RU Data Pillar Gap Analysis - -**Table O-RU Gap Analysis-52: O-RU Data Pillar Gap Analysis** - -| Data ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|------------------|-----------------------------------------------------------------------------------------|------------|----------------------------------------------------------------------|------------------------------------|-------------------------------------------------------| -| Data Access | a) Automated data access control | ASSET-D-01 | None | Gap | Authentication and authorization controls not defined | -| | b) Elements of least privileges are incorporated with the automated data access control | ASSET-D-02 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-04 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-05 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-06 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-16 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-17 | REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-4
Clause 5.3.5 [i.17] | No gap | | -| | | ASSET-D-18 | None | Gap | Authentication and authorization controls not defined | -| | | ASSET-D-20 | REQ-SEC-PASS-1
SEC-CTL-PASS-1
SEC-CTL-PASS-2
SEC-CTL-PASS-3 | Gap | Authorization controls not defined | -| | | ASSET-D-23 | REQ-SEC-ALM-PKG-11
SEC-CTL-ALM-PKG-1 | No gap | | -| | | ASSET-D-24 | None | Gap | Authentication and authorization controls not | - -| | | | | | | -|-----------------|---------------------------------------------------------------------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------|--------------|-------------------------------------------------------------------------------------| -| | | | | | defined | -| | | ASSET-D-29 | REQ-SEC-SLM-TESS-6
REQ-SEC-SLM-TESM-3
REQ-SEC-TESR-1
REQ-SEC-TESR-5
REQ-SEC-TESR-7
REQ-SEC-TESR-9
REQ-SEC-TESR-11 | No gap | | -| | | ASSET-D-32 | None | Gap | There are requirements for secure storage and boot, but not access of key material. | -| Data Encryption | a) Encrypted data in transit and, where feasible, data at rest. | ASSET-D-01 | REQ-SEC-OFSP-8 | No gap | | -| | | ASSET-D-02 | See [i.26] | No gap | | -| | | ASSET-D-04 | REQ-SEC-OFCP-4
SEC-CTL-OFCP-1 | No gap | | -| | | ASSET-D-05 | Clause 6.6 [i.17] | No gap | PDCP provides confidentiality | -| | b) Key management policies and secure encryption keys are beginning to be formalized. | ASSET-D-06 | Clause 5.3.5 [i.17] | No gap | | -| | | ASSET-D-16 | REQ-SEC-OCLOUD-SS-1
REQ-SEC-ALM-PKG-13
See [i.24],[i.25] | No gap | | -| | | ASSET-D-17 | REQ-SEC-OCLOUD-SS-1
REQ-SEC-ALM-PKG-13
See [i.24],[i.25] | No gap | | -| | | ASSET-D-18 | REQ-SEC-ALM-PKG-13 | Possible gap | Requirement is too general | -| | | ASSET-D-20 | REQ-SEC-ALM-PKG-13 | No gap | | -| | | ASSET-D-23 | REQ-SEC-ALM-PKG-10 | No gap | | -| | | ASSET-D-24 | REQ-SEC-ALM-PKG-13 | No gap | | -| | | ASSET-D-29 | REQ-SEC-SLM-TESS-6
REQ-SEC-SLM-TESS-7
REQ-SEC-TESR-1
REQ-SEC-TESR-11
REQ-SEC-SLM- | No gap | | - -| | | | | | | -|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | TESM-2
REQ-SEC-SLM-SST-2 | | | -| | | ASSET-D-32 | None | Gap | | -| Visibility and Analytics Capability | Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | ASSET-D-01
ASSET-D-02
ASSET-D-04
ASSET-D-05
ASSET-D-06
ASSET-D-16
ASSET-D-17
ASSET-D-18
ASSET-D-20
ASSET-D-23
ASSET-D-24
ASSET-D-29
ASSET-D-32 | REQ-SEC-SLM-DAT-EVT-1
REQ-SEC-SLM-DAT-EVT-2
REQ-SEC-SLM-DAT-EVT-3
REQ-SEC-SLM-DAT-EVT-4
REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5 | Partial gap | Data inventory and data categorization are out of scope for O-RAN specifications.

Creating and providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | Data lifecycle and security policies (e.g., access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) are automated. | ASSET-D-01 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-02 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-04 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-05 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-06 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-16 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-17 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-18 | None | Gap | Out of scope, as data lifecycle and security policies fall under the | - -| | | | | | | -|--|--|------------|------|-----|---------------------------------------------------------------------------------------------------| -| | | | | | operator's responsibilities. | -| | | ASSET-D-20 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-23 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-24 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-29 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | ASSET-D-32 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | - -### 7.3.15.2 O-RU Application and Workloads Pillar - -#### 7.3.15.2.1 O-RU Application and Workloads Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are listed below. The O-RU specific assets are as follows: - -- ASSET-C-06: O-RU -- ASSET-C-31: Shared O-RU -- ASSET-C-32: O-RU Host -- ASSET-C-33: O-RU Tenant (Shared Resource Operator) - -#### 7.3.15.2.2 O-RU Applications and Workloads Pillar Gap Analysis - -Note that in Table O-RU Gap Analysis-53 below, the O-RU asset(s) are grouped together as the requirements and controls are apply at the NF level. - -**Table O-RU Gap Analysis-53: O-RU Applications and Workloads Pillar Gap Analysis** - -| App/Workloads ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|--------------------------------------------------------------|------------------------------------|---------------| -| Application Access (Authorization) | a) Access authorization capabilities utilize contextual information such as identity, device compliance, and other attributes to make decisions on various | ASSET-C-06
ASSET-C-31
ASSET-C-32
ASSET-C-33 | See [i.24]

REQ-SEC-SharedORU-1
REQ-SEC-SharedORU-2 | No gap | Identity only | - -| | | | | | | -|-----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|------------------------------------------------------------------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------| -| | requests for accessing application assets.

b) Authorization is granted per request with expiration. | | | | | -| Application Threat Protections | a) Threat protection is integrated into mission-critical application workflows.

b) Threat protections safeguard applications against known threats and address some application-specific threats. | ASSET-C-06
ASSET-C-31
ASSET-C-32
ASSET-C-33 | REQ-SEC-ORU-1
REQ-SEC-ORU-2
REQ-SEC-ALM-SU-2
REQ-SEC-ALM-SU-3 | No gap | | -| Accessible Applications | a) Applicable mission-critical applications are available over open public network connections to authorized users as needed. | ASSET-C-06
ASSET-C-31
ASSET-C-32
ASSET-C-33 | See [i.17] | No gap | Out of scope for O-RAN

No identified Mission critical applications

Requirements specified in 3GPP | -| Secure Application Development and Deployment Workflow (New Function) | a) Infrastructure for development, testing, and production environments (including automation).

b) Formal code deployment mechanisms through CI/CD pipelines.

c) Access controls support least privilege principles. | ASSET-C-06
ASSET-C-31
ASSET-C-32
ASSET-C-33 | None | Gap | Out of scope for O-RAN

Securing infrastructure for development, testing, and production environments is out of scope for O-RAN. | -| Application Security Testing (Formerly Application Security) | a) Utilization of static and dynamic testing methods for security testing.

b) Performance of security testing including manual expert analysis before application deployment. | ASSET-C-06
ASSET-C-31
ASSET-C-32
ASSET-C-33 | REQ-SEC-ALM-PKG-1
REQ-SEC-ALM-PKG-7b | No gap | Guidance (b) is out of scope for O-RAN. | -| Visibility and Analytics Capability | Initiate the automation of application profile (e.g., state, health, and performance) and security monitoring processes for improved log collection, aggregation, and analytics. | ASSET-C-06
ASSET-C-31
ASSET-C-32
ASSET-C-33 | REQ-SEC-SLM-FLD-1
REQ-SEC-SLM-FLD-2
REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-5 | Partial gap | These requirements allow for the inclusion of application profile information in security logs. However, the automation of application | - -| | | | | | | -|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|------|-----|----------------------------------------------------------------------------------------------------------------------------------| -| | | | | | profile monitoring processes and analytics is not addressed.

Log collection, aggregation, and analytics are out of scope. | -| Automation and Orchestration Capability | Periodically modifies application configurations, including location and access parameters, to align with pertinent security and performance objectives. | ASSET-C-06
ASSET-C-31
ASSET-C-32
ASSET-C-33 | None | Gap | Out of scope, as application configuration falls under operator's responsibilities. | - -### 7.3.15.3 O-RU Identity Pillar - -#### 7.3.15.3.1 O-RU Identity Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are listed below. The O-RU is considered as a PNF in terms of identity and O-RU specific assets are as follows. - -- ASSET-C-12a: PNF NF equipment -- ASSET-C-32: O-RU Host -- ASSET-C-33: O-RU Tenant (Shared Resource Operator) - -#### 7.3.15.3.2 O-RU Identity Pillar Gap Analysis - -**Table O-RU Gap Analysis-54: O-RU Identity Pillar Gap Analysis** - -| Networks ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|--------------------------------------------|------------------------------------|----------| -| Authentication | The system authenticates identity using MFA, which may include passwords as one factor and requires validation of multiple entity attributes (e.g. locale or activity).

a) If there is mutual authentication for internal communications, we consider the stage as INITIAL.

b) For internal interfaces, authentication based on credentials alone (certificate, pre-shared key, etc.) can be considered as meeting | ASSET-C-12a | See [i.17] | No gap | | -| | | ASSET-C-32 | See [i.17] | No gap | | -| | | ASSET-C-33 | See [i.17] | No gap | | - -| | | | | | | -|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|-----------------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | INITIAL maturity level. | | | | | -| Access Management (Authorization) | The system authorizes access, including for privileged access requests, that expires with automated review.

a) This function applies to APIs and user accounts.

b) For applications, static role assignments (e.g. role binding of a service account) with ephemeral tokens can be considered as INITIAL stage. | ASSET-C-12a | See [i.17] | No gap | | -| | | ASSET-C-32 | See [i.17] | No gap | | -| | | ASSET-C-33 | See [i.17] | No gap | | -| Visibility and Analytics Capability | a) Collecting user and entity activity logs.
b) Performing Routine Analysis:
a. Conduct regular manual analysis of the logs.
b. Implement some automated analysis, with limited correlation between different log types. | ASSET-C-12a | REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-13 | Partial gap | Security log requirements enable generation of security logs, but analysis, automation, and correlation are not specified.

Analysis, automation, and correlation are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE. | -| | | ASSET-C-32 | REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-13 | Partial gap | | -| | | ASSET-C-33 | REQ-SEC-SLM-TESS-3
REQ-SEC-SLM-TESS-4
REQ-SEC-SLM-TESS-13 | Partial gap | | -| Automation and Orchestration Capability | a) Manually orchestrates privileged and external identities.
b) Automates orchestration of non-privileged users.
c) Automates orchestration of self-managed entities. | ASSET-C-12a | None | Gap | Out of scope, as Identities orchestration fall under the operator's responsibilities | -| | | ASSET-C-32 | None | Gap | Out of scope, as Identities orchestration fall under the operator's responsibilities | -| | | ASSET-C-33 | None | Gap | Out of scope, as Identities orchestration fall under the operator's responsibilities | - -| | | | | | | -|--|--|--|--|--|------------------| -| | | | | | responsibilities | -|--|--|--|--|--|------------------| - -### 7.3.15.4 O-RU Networks Pillar - -#### 7.3.15.4.1 O-RU Networks Pillar Assets - -Currently there are no applicable assets or components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] for O-RU Network pillar. - -#### 7.3.15.4.2 O-RU Networks Pillar Gap Analysis - -No Gap Analysis required. - -### 7.3.15.5 O-RU Devices Pillar - -#### 7.3.15.5.1 O-RU Devices Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are listed below. The O-RU specific assets are as follows: - -- ASSET-C-12a: PNF NF equipment - -#### 7.3.15.5.2 O-RU Devices Pillar Gap Analysis - -**Table O-RU Gap Analysis-55: O-RU Devices Pillar Gap Analysis** - -| Devices ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|-------------------------------------------------| -| Policy Enforcement and Compliance Monitoring | Basic Device characteristics visibility. Basic policy enforcement mechanism for managing software configurations or vulnerabilities | ASSET-C-12a | REQ-SEC-TAP-5
REQ-SEC-SLM-NET-EVT-1
REQ-SEC-SLM-GSE-1
REQ-SEC-SLM-GSE-3
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5
REQ-SEC-SLM-GSE-6
See [i.17] | No gap | | -| Resource Access (Authorization) | Some visibility into devices or virtual assets' characteristics to approve resource access | ASSET-C-12a | REQ-SEC-SLM-NET-EVT-1
REQ-SEC-SLM-GSE-6 | No gap | | -| Device Threat Protection | Some automated processes for deploying and updating threat protection capabilities to devices and to virtual assets with limited | ASSET-C-12a | REQ-SEC-SLM-NET-EVT-1 | Partial gap | REQ-SEC-ALM-PKG applies to VNF/CNF and not PNFs | - -| | | | | | | -|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|------|-----|--------------------------------------------------------------------------------------------------------------------------------| -| | policy enforcement and compliance monitoring integration. | | | | | -| Visibility and Analytics Capability | a) Use digital identifiers alongside a manual inventory and endpoint monitoring of devices when available
b) Automated analysis: Ensure some devices and virtual assets (e.g., software-based scanning) for anomaly detection based on risk. | ASSET-C-12a | None | Gap | Out of scope, as endpoint inventory management fall under the operator's responsibility. | -| Automation and Orchestration Capability | Utilization of monitoring and enforcement mechanisms to identify and manually disconnect or isolate non-compliant devices and virtual assets. | ASSET-C-12a | None | Gap | Out of scope, as disconnecting or isolating non-compliant devices and virtual assets fall under the operator's responsibility. | - -## 7.3.16 Open Fronthaul Interface Gap Analysis - -### 7.3.16.1 Introduction - -The Open Fronthaul assets considers the Open Fronthaul interface as well as the architecture elements which includes the O-DU and O-RU. The gap analysis is considered only for the Open Fronthaul interface and the Open Fronthaul protocol stack. - -The Transport Network Element, Fronthaul Multiplexer, Fronthaul Gateway are considered new assets and not included in the Gap Analysis. - -### 7.3.16.2 Open Fronthaul Interface Data Pillar - -#### 7.3.16.2.1 Open Fronthaul Interface Data Pillar Assets - -The applicable assets applying to the Open Fronthaul includes the Open Fronthaul interface as well as Open Fronthaul protocol stack data assets defined in the WG11 Threat Modelling and Risk Assessment document [i.4] are as following: - -- ASSET-D-01: Critical S-Plane Data -- ASSET-D-02: Critical Management-Plane data transported over the Fronthaul interface such as: maintenance and monitoring signals, data collected related to O-RU operations, logs (troubleshooting, trace) - -- ASSET-D-04: Critical C-Plane data -- ASSET-D-05: Critical Fronthaul U-Plane data -- ASSET-D-16: X.509 certificates in O-RAN network such as those used for O-RAN components for authentication, encryption, and signing. -- ASSET-D-17: Security private keys in O-RAN network such as those used for O-RAN components for authentication, encryption, and signing. -- ASSET-D-06: Reference signals, synchronization signal and channels in downlink and uplink between O-RU and UE -- ASSET-D-18: O-RAN components associated and configuration data which includes software version identifier, IP address, port number, network layer parameters, time of request, previous behavior, etc. -- ASSET-D-20: Credentials (Administrators) -- ASSET-D-24: NETCONF Configuration Access Control Model datastores. - -The Open Fronthaul data assets, classified within the Data Pillar, are evaluated for each ZTA function across two domains: - -- Open FH Interface: Focused on data in transit. -- Open FH protocol stack: Focused on data at rest. - -### 7.3.16.2.2 Open Fronthaul Interface Data Pillar Gap Analysis - -**Table Open Fronthaul Interface Gap Analysis-56: Open Fronthaul Data Pillar Gap Analysis** - -| Data ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gap | Comments | -|------------------|-----------------------------------------------------------------------------------------|----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|----------| -| Data Access | a) Automated data access control | Data Access for the Open Fronthaul Interface data assets | | | | -| | b) Elements of least privileges are incorporated with the automated data access control | ASSET-D-01 | REQ-SEC-OFHPLS-1-- REQ-SEC-OFHPLS-3

SEC-CTL-OFHPLS-1-- SEC-CTL-OFHPLS-5 | No gap | | -| | | ASSET-D-02 | REQ-SEC-OFHM-2
REQ-SEC-OFHM-3
SEC-CTL-OFHM-4

REQ-NAC-MPLANE-FUN-1--
REQ-NAC-MPLANE-FUN-6

REQ-SEC-OFHPLS-1-- REQ-SEC-OFHPLS-3

SEC-CTL-OFHPLS-1-- SEC-CTL-OFHPLS-5 | No gap | | - -| | | | | | | -|---------------------------------------------------------------|--|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|--------|------------------------------------------------------| -| | | | See [i.26] | | | -| | | ASSET-D-04 | REQ-SEC-OFCP-1

REQ-SEC-OFHPLS-1-- REQ-SEC-OFHPLS-3

SEC-CTL-OFHPLS-1-- SEC-CTL-OFHPLS-5 | No gap | | -| | | ASSET-D-05 | REQ-SEC-OFUP-2, REQ-SEC-OFUP-3

REQ-SEC-OFHPLS-1-- REQ-SEC-OFHPLS-3

SEC-CTL-OFHPLS-1-- SEC-CTL-OFHPLS-5 | No gap | | -| | | ASSET-D-16 | None | No gap | No action needed. X.509 certs are publicly available | -| | | ASSET-D-17 | None | Gap | | -| | | ASSET-D-06 | REQ-SEC-OFCP-1 | No gap | | -| | | ASSET-D-18 | REQ-SEC-OFHM-2
REQ-SEC-OFHM-3
SEC-CTL-OFHM-4

REQ-NAC-MPLANE-FUN-1--
REQ-NAC-MPLANE-FUN-6

See [i.26] | No gap | | -| Data Access for the Open Fronthaul protocol stack data assets | | | | | | -| | | ASSET-D-01
ASSET-D-04
ASSET-D-05
ASSET-D-06
ASSET-D-18
ASSET-D-24 | None | Gap | Authorization controls not defined | -| | | ASSET-D-02 | REQ-SEC-OFHM-2
REQ-SEC-OFHM-3
SEC-CTL-OFHM-4

REQ-NAC-MPLANE-FUN-1--
REQ-NAC-MPLANE-FUN-6 | No gap | | -| | | ASSET-D-16 | None | No gap | No action needed. X.509 certs are publicly available | - -| | | | | | | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|--------|------------------------------------| -| | | ASSET-D-17 | REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-4 | No gap | | -| | | ASSET-D-20 | REQ-SEC-PASS-1
SEC-CTL-PASS-1
SEC-CTL-PASS-2
SEC-CTL-PASS-3 | Gap | Authorization controls not defined | -| Data Encryption | a) Encrypted data in transit and, where feasible, data at rest.

b) Key management policies and secure encryption keys are beginning to be formalized. | Data Encryption for the Open Fronthaul Interface data assets | | | | -| | | ASSET-D-01 | REQ-SEC-OFSP-8
SEC-CTL-OFSP-4 | No gap | | -| | | Asset-D-02 | REQ-SEC-OFHM-1
SEC-CTL-OFHM-1
SEC-CTL-OFHM-6
SEC-CTL-OFHM-7
SEC-CTL-OFHM-8

Table 5.4-1 refer [i.26] | No gap | | -| | | Asset-D-04 | REQ-SEC-OFCP-4
SEC-CTL-OFCP-1
SEC-CTL-OFHMECC-1--SEC-CTL-OFHMECC-5 | No gap | | -| | | Asset-D-05 | SEC-CTL-OFUP-1
Clause 5.2.5.2.2.1 | No gap | | -| | | ASSET-D-16 | REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-2 | No gap | | -| | | ASSET-D-17 | REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-2 | No gap | | -| | | ASSET-D-06 | REQ-SEC-OFCP-4
SEC-CTL-OFCP-1 | No gap | | -| | | ASSET-D-18 | REQ-SEC-OFHM-1
SEC-CTL-OFHM-1 | No gap | | -| | | Data Encryption for the Open Fronthaul protocol stack data assets | | | | -| | | ASSET-D-01 | None | Gap | | -| | | ASSET-D-02 | None | Gap | | -| | | ASSET-D-04 | None | Gap | | -| | | ASSET-D-05 | None | Gap | | -| | | ASSET-D-16 | REQ-SEC-ALM-PKG-13 | No gap | | - -| | | | | | | -|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | SEC-CTL-ALM-PKG-2 | | | -| | | ASSET-D-17 | REQ-SEC-ALM-PKG-13
SEC-CTL-ALM-PKG-2 | No gap | Application-level requirements satisfies the Data encryption at rest | -| | | ASSET-D-06 | None | Gap | | -| | | ASSET-D-18 | None | Gap | | -| | | ASSET-D-20 | REQ-SEC-ALM-PKG-13 | No gap | Application-level requirements satisfies the Data encryption at rest | -| | | ASSET-D-24 | REQ-SEC-ALM-PKG-13 | No gap | Application-level requirements satisfies the Data encryption at rest | -| Visibility and Analytics Capability | Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | Visibility and Analytics Capability for the Open Fronthaul Interface data assets | | | | -| | | ASSET-D-01
ASSET-D-02
ASSET-D-04
ASSET-D-05
ASSET-D-16
ASSET-D-17
ASSET-D-06
ASSET-D-18 | REQ-SEC-SLM-DAT-EVT-1
REQ-SEC-SLM-DAT-EVT-2
REQ-SEC-SLM-DAT-EVT-3
REQ-SEC-SLM-DAT-EVT-4
REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8
REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5
REQ-SEC-SLM-DAT-EVT-5 | Partial gap | Data inventory and data categorization are out of scope for O-RAN specifications.

Creating and providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | -| | | Visibility and Analytics Capability for the Open Fronthaul protocol stack data assets | | | | -| | | ASSET-D-01
ASSET-D-02
ASSET-D-04
ASSET-D-05
ASSET-D-16
ASSET-D-17
ASSET-D-06
ASSET-D-18
ASSET-D-20
ASSET-D-24 | REQ-SEC-SLM-DAT-EVT-1
REQ-SEC-SLM-DAT-EVT-2
REQ-SEC-SLM-DAT-EVT-3
REQ-SEC-SLM-DAT-EVT-4
REQ-SEC-SLM-DAT-EVT-6
REQ-SEC-SLM-DAT-EVT-7
REQ-SEC-SLM-DAT-EVT-8 | Partial gap | Data inventory and data categorization are out of scope for O-RAN specifications.

Creating and providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. According to [i.31], SIEM is not within scope and is not defined by the O-RAN ALLIANCE. | - -| | | | | | | -|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|-----|---------------------------------------------------------------------------------------------------| -| | | | REQ-SEC-SLM-GSE-4
REQ-SEC-SLM-GSE-5
REQ-SEC-SLM-DAT-EVT-5 | | ALLIANCE. | -| Automation and Orchestration Capability | Data lifecycle and security policies (e.g., access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) are automated. | Automation and Orchestration Capability for the Open Fronthaul Interface data assets | | | | -| | | ASSET-D-01
ASSET-D-02
ASSET-D-04
ASSET-D-05
ASSET-D-06
ASSET-D-16
ASSET-D-17
ASSET-D-18 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | -| | | Automation and Orchestration Capability for the Open Fronthaul protocol stack data assets | | | | -| | | ASSET-D-01
ASSET-D-02
ASSET-D-04
ASSET-D-05
ASSET-D-06
ASSET-D-16
ASSET-D-17
ASSET-D-18
ASSET-D-20
ASSET-D-24 | None | Gap | Out of scope, as data lifecycle and security policies fall under the operator's responsibilities. | - -### 7.3.16.3 Open Fronthaul Interface Applications and Workloads Pillar - -#### 7.3.16.3.1 Open Fronthaul Interface Applications and Workloads Pillar Assets - -- No asset applicable to specific pillar - -### 7.3.16.4 Open Fronthaul Interface Identity Pillar - -#### 7.3.16.4.1 Open Fronthaul Interface Identity Pillar Assets - -The applicable assets and components defined in the WG11 O-RAN Security Threat Modeling and Risk Assessment [i.4] are listed below. - -- ASSET-C-32: O-RU Host which includes the Ethernet Layer -- ASSET-C-34: O-DU Host which includes the Ethernet Layer -- ASSET-C-24: OFH M-Plane, including protocol stack -- ASSET-C-25: OFH CUS-Plane, including protocol stack - -7.3.16.4.2 Open Fronthaul Interface Identity Pillar Gap Analysis - -**Table Open Fronthaul Interface Gap Analysis-2: Open FH Interface Identity Pillar Gap Analysis** - -| Identity ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements mapped to CISA stage | Assessed Gap to Initial CISA Stage | Comments | -|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|---------------------------------------------------------------------------------------|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| -| Authentication |

The system authenticates identity using MFA, which may include passwords as one factor and requires validation of multiple entity attributes (e.g. locale or activity).

a) If there is mutual authentication for internal communications, we consider the stage as INITIAL.

b) For internal interfaces, authentication based on credentials alone (certificate, pre-shared key, etc.) can be considered as meeting INITIAL maturity level.

| ASSET-C-32
ASSET-C-34
ASSET-C-24
ASSET-C-25 | REQ-SEC-OFHPLS-1

SEC-CTL-OFHPLS-2--
SEC-CTL-OFHPLS-5 | Gap | Considering the mutual authentication guidance this has been marked as Gap | -| Access Management (Authorization ) |

The system authorizes access, including for privileged access requests, that expires with automated review.

a) This function applies to APIs and user access.

b) For applications, static role assignments (e.g. role binding of a service account) with ephemeral tokens can be considered as INITIAL stage.

| ASSET-C-32
ASSET-C-34
ASSET-C-24
ASSET-C-25 | REQ-SEC-OFHPLS-1--
REQ-SEC-OFHPLS-3

SEC-CTL-OFHPLS-2--
SEC-CTL-OFHPLS-10 | No gap | IEEE 802.1X provides implicit authorization. | -| Visibility and Analytics Capability |

a) Collecting user and entity activity logs.

b) Performing Routine Analysis:

  • a. Conduct regular manual analysis of the logs.
  • b. Implement some automated analysis, with limited correlation between different log types.
| ASSET-C-34
ASSET-C-32
ASSET-C-24
ASSET-C-25 | REQ-SEC-SLM-NET-EVT-1
REQ-SEC-SLM-TESS-3 | Partial gap |

This requirements enable generation of security logs and logging of all physical/virtual network events and is generic

Analysis,

| - -| | | | | | | -|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | | automation, and correlation are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE's scope and is not defined by the O-RAN ALLIANCE. | -| Automation and Orchestration Capability | a) Manually orchestrates privileged and external identities.
b) Automates orchestration of non-privileged users.
c) Automates orchestration of self-managed entities. | ASSET-C-32
ASSET-C-34
ASSET-C-24
ASSET-C-25 | None | No gap | Out of scope, as Identities orchestration fall under the operator's responsibilities | - -### 7.3.16.5 Open Fronthaul Interface Networks Pillar - -#### 7.3.16.5.1 Open Fronthaul Interface Networks Pillar Assets - -The applicable assets defined in the WG11 Threat Modelling and Risk Assessment document [i.4] are as following: - -- ASSET-C-24: OFH M-Plane, including protocol stack -- ASSET-C-25: OFH CUS-Plane, including protocol stack - -#### 7.3.16.5.2 Open Fronthaul Interface Networks Pillar Gap Analysis - -**Table Open Fronthaul Interface Gap Analysis-3: Open Fronthaul Networks Pillar Gap Analysis** - -| Networks ZT Function | Guidance to reach initial stage | Asset(s) | Existing Requirements Mapped to CISA Stage | Assessed Gaps | Comments | -|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------|---------------|---------------------------------------------------------------| -| Traffic Encryption | Encryption for all internal (and preferably external) application traffic, with formalized key management policies and secure encryption keys | ASSET-C-24 | Refer [i.26] | No gap | | -| | | ASSET-C-25 | SEC-CTL-OFHMECC-1--
SEC-CTL-OFHMECC-5 | No gap | | -| Visibility and Analytics Capability | a) Utilize network monitoring capabilities based on known indicators of | ASSET-C-24 | None | Gap | No requirements for providing network monitoring information. | - -| | | | | | | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

compromise, including network enumeration, to develop situational awareness in each environment.

b) Commence correlating telemetry across traffic types and environments to facilitate analysis and threat hunting activities.

| | | |

Providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE.

| -| | | ASSET-C-25 | None | Gap |

No requirements for providing network monitoring information.

Providing the required information is within scope. However, the collection, analysis, and correlation of this information to achieve visibility are considered out of scope for O-RAN. As specified in [i.31], SIEM is not within the O-RAN ALLIANCE 's scope and is not defined by the O-RAN ALLIANCE.

| -| Automation and Orchestration Capability |

a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments.

b) Ensure that all resources have a defined lifetime determined by policies and telemetry data.

| ASSET-C-24 | None | Gap |

Out of scope, network resource configuration and lifecycle management fall under the operator's responsibilities.

| -| | | ASSET-C-25 | None | Gap |

Out of scope, network resource configuration and lifecycle management fall under the operator's responsibilities.

| - -### 7.3.16.6 Open Fronthaul Interface Devices Pillar - -#### 7.3.16.6.1 Open Fronthaul Devices Pillar Assets - -- No asset applicable to specific pillar - -## 7.4 WG11 Considerations for Mapping Security Controls to CISA ZTMM - -### 7.4.1 Introduction - -The following considerations were made when mapping O-RAN security controls to the CISA ZTMM, as summarized in this list below: - -#### **List 7.4-1: Summary of CISA ZTMM Stages** - -##### Traditional stage - -- Perimeter-based security controls -- Perimeter-based monitoring -- Static network policies -- Manual processes - -##### Initial stage - -- External controls and some security controls to protect against internal threats -- Monitoring with known indicators -- Tailored policies -- Some automation -- Begin cloud migration - -##### Advanced stage - -- Security controls to protect against internal and external threats -- Centralized visibility -- Continuous monitoring of network -- Tailored policies -- Automation - -##### Optimal stage - -- Security controls to protect against internal and external threats -- Centralized visibility with situational awareness -- Continuous Monitoring of network, applications, and users -- Dynamic policies with AI -- Automation with AI - -## 7.4.2 Mapping to CISA ZTMM - -The O-RAN ALLIANCE has made significant progress advancing its security specifications. Table Mapping to CISA ZTMM-57 shows how the currently specified security controls map to the CISA ZTMM stages. Some additional considerations made when mapping O-RAN specifications to the stages are as follows: - -- The Devices pillar includes User Equipment and cloud infrastructure devices. -- The Networks pillar includes data-in-transit. -- The Applications pillar includes O-RAN architecture elements, such as O-RAN CNFs, SMO, and rApps/xApps. -- The Data pillar includes data-in-transit, data-at-rest, and data-in-use. - -**Table Mapping to CISA ZTMM-57: CISA ZTMM Mapping of O-RAN security controls** - -| Pillars and Functions | Traditional | Initial | Advanced | Optimal | -|------------------------------|-------------|----------------------------------------------------------------------------------------------|---------------------------------|---------------------------------| -| Identity | Passwords | X.509 Certificates, LDAPS, mTLS, IEEE 802.1X, NACM, Principle of least privilege, MFA | OAuth 2.0, CMPv2 | | -| Devices | | Resource management | HSM, Container hardening | | -| Networks | SSH, SFTP | TLS, FTPES | API security, MACsec | NFs secured as micro-perimeters | -| Applications and Workloads | | Digital signatures, Volumetric DDoS Protection | Secure On-Boarding | | -| Data | | TLS for data-in-transit | | | -| Visibility and Analytics | | Secure Logging | | | -| Automation and Orchestration | | | | | -| Governance | | | SBOM, GSMA NESAS | AI/ML security | - -NOTE: **Bold** indicates an O-RAN specifications roadmap feature currently being addressed in a WG11 security work item. - -## 8 ZTA Threats - -### 8.1 Introduction - -This clause reviews the O-RAN Security Threat Modeling and Risk Assessment TR [i.4] for existing threats. - -### 8.2 Mapping of the existing Security Principles to ZT Tenets - -In the O-RAN Security Threat Modeling and Risk Assessment TR [i.4] all Threats are being mapped to Security Principles (see [i.4] clause 8.2). In order to analyse which of the Threats are related to ZT tenets and whether they are properly covered by security principles, the security principles need to be mapped to the ZT tenets. [i.4] clause 8 provides such a mapping. Table 8.2 represents this mapping, which has been updated for the O-RAN Security Threat Modeling and Risk Assessment TR. - -**Table 8.2-58: Mapping of security principles to ZT tenets** - -| Security Principles | ZT Tenets | | | | | | | -|----------------------------------------------------------------------------------------------------------|-----------|---|---|---|---|---|---| -| | 1 | 2 | 3 | 4 | 5 | 6 | 7 | -| SP-AUTH - Mutual Authentication | | X | X | X | | X | | -| SP-ACC - Access Control | X | | X | X | | X | | -| SP-CRYPTO - Secure cryptographic, key management and PKI | | X | | X | | | | -| SP-TCOMM - Trusted Communication | | X | | | | | | -| SP-SS - Secure Storage | X | X | | X | X | X | | -| SP-SB - Secure boot and self-configuration | X | | X | X | X | | | -| SP-UPDT - Secure Update | | | | | X | | X | -| SP-RECO - Recoverability & Backup | | | | | X | X | X | -| SP-OPNS - Security management of risks in open-source components | | | | X | X | X | X | -| SP-ASSU - Security Assurance | | | | | X | | X | -| SP-PRV - Privacy | | X | X | X | X | X | X | -| SP-SLC - Continuous security development, testing, logging, monitoring and vulnerability handling | | | | X | X | X | X | -| SP-ISO - Robust Isolation | | X | X | X | X | | X | -| SP-PHY - Physical security | X | X | X | X | X | X | X | -| SP-CLD - Secure cloud computing and virtualization | | X | X | X | X | X | X | - -| | | | | | | | | -|----------------------------------------------|----------|----------|----------|----------|----------|----------|----------| -| SP-ROB - Robustness | | X | X | | X | X | X | -| SP-IDM - O-Cloud ID secure management | X | | X | X | X | X | X | - -NOTE 1: **X**: mapping existing in [i.4]. - -NOTE 2: Access to resources is determined by dynamic policy which is mapped in the above Table 8.2-1 for SP-ACC - Access Control (Tenet 4) need to be discussed further. - -### 8.3 Existing defined threats - -Existing threats are defined in O-RAN Security Threat Modeling and Risk Assessment TR [i.4]. - -### 8.4 New threats - -Threats for new assets defined in this document will be identified in their respective WG11 Work Items. - ---- - -## 9 Threat analysis - -Existing threats already have analysis completed in O-RAN Security Threat Modeling and Risk Assessment TR [i.4]. Threats for new assets will be analyzed in their respective WG11 Work Items and Technical Reports. - ---- - -## 10 Risk assessment - -Existing threats already have risk assessment completed in O-RAN Security Threat Modeling and Risk Assessment TR [i.4]. Risk assessment for new threats will be done in their respective WG11 Work Items. - -## 11 Recommendations - -### 11.1 Preliminary Guidance for Future Work - -The following preliminary recommendations from this work item will be addressed in future updates to this technical report and other specifications: - -- **Complete threat and risk assessment:** Update clauses 8, 9 and 10 with identification of new threats and threat analysis and risk assessment for the newly identified threats. -- **Conduct Gap Analysis:** Perform a gap analysis for different O-RAN assets based on the guidelines in clause 6.2 and update clause 7.3 accordingly. - -*Status:* Gap analysis on O-RAN architecture elements and O-RAN interfaces is complete. - -- **Propose ZTA Security Requirements:** Based on the conducted gap analysis, propose a list of Zero Trust Architecture (ZTA) security requirements for different O-RAN assets after consultation with the relevant WG11 Work Items and update clause 11 with those recommended security requirements. - 1. ZTA WI should identify which requirements are in-scope for O-RAN ZTA but not in-scope for O-RAN specifications. - 2. ZTA WI should determine whether security specifications for human administrative access to O-RAN architecture elements are in-scope for O-RAN specifications. - -*Status:* Consultation with the respective Work Items is in progress. Based on the consultation, gaps will either be resolved or considered out of scope for O-RAN. - -- **Define relevant terms:** ZTA WI should define the terms 'micro-perimeter' and 'micro-segmentation' in the context of O-RAN, while considering existing definitions from authoritative sources. - -*Outcome:* Micro-segmentation term is defined in the present document. - -- **Identify Continuous Monitoring Needs:** Based on the study of NIST ZT tenets applicability in clause 4.2 and the target ZTA security requirements in clause 6.2, continuous monitoring is identified as a critical aspect of ZTA for the following reasons: - 1. It is critical to fully address tenet 4, 5 and 7. - 2. It is critical to fully address the following CISA ZTMM functions: - - Risk assessment function and visibility and analytics capability in the Identity pillar. - - Asset & supply chain risk management function, resource access function, and visibility and analytics capability in the Devices pillar. - - Network traffic management and visibility and analytics capability in the Networks pillar. - - Application access and visibility and analytics capability in the Applications and Workloads pillar. - - Visibility and analytics capability in the Data pillar. - -Therefore, we recommend conducting a comprehensive study on continuous monitoring in O-RAN as a separate supporting work item or work items. This WI or WIs should define the critical characteristics and attributes that need to be continuously captured in different O-RAN components to address tenets 4, 5, and 7, as well as the CISA ZTMM functions and capabilities listed above. - -*Outcome:* WG11 Continuous Security Monitoring Work Item was initiated in August 2024 and the first version of the Continuous Security Monitoring technical report will be published in the March 2025 train. - -- **Clarify access on a per-session basis:** ZTA WI should provide a description of the phrase “per-session basis access” in the context of ZTA for O-RAN ALLIANCE. - -*Outcome:* Additional description on NIST ZT tenet 3 and “per-session basis access” is added to the present document. - -## 11.2 Identified Gaps Out of Scope for O-RAN - -This clause outlines all the gaps identified in Clause 7.3 that are necessary to address in order to achieve a zero trust architecture but have been determined to fall outside the scope of O-RAN. - -### 11.2.1 Transversal Functions - -**Table Transversal Functions-59: Transversal Functions Identified Gaps Out of Scope for O-RAN** - -| CISA ZT Function | Guidance to reach initial stage | Asset(s) | -|-----------------------------------|---------------------------------|----------| -| Data ZT Function | | | -| ... | ... | ... | -| App/ Workloads ZT Function | | | -| ... | ... | ... | -| Identity ZT Function | | | -| ... | ... | ... | -| Networks ZT Function | | | -| ... | ... | ... | -| Devices ZT Function | | | -| ... | ... | ... | - -### 11.2.2 xApp and Near-RT RIC - -**Table xApp and Near-RT RIC-60: xApp and Near-RT RIC Identified Gaps Out of Scope for O-RAN** - -| CISA ZT Function | Guidance to reach initial stage | Asset(s) | Comments | -|-----------------------------------|-------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------| -| App/ Workloads ZT Function | | | | -| Accessible Applications | a) Applicable mission-critical applications are available over open public network connections to authorized users as needed. | xApp:
ASSET-C-09

Near-RT RIC:
ASSET-C-13
ASSET-C-41
ASSET-C-43
Other Services of the Near- | No identified mission critical applications are available over open public networks. | - -| | | | | -|-----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------| -| | | RT RIC platform | | -| Secure Application Development and Deployment Workflow (New Function) | a) Infrastructure for development, testing, and production environments (including automation).

b) Formal code deployment mechanisms through CI/CD pipelines.

c) Access controls support least privilege principles. | xApp:

ASSET-C-09

Near-RT RIC:

ASSET-C-13
ASSET-C-41
ASSET-C-43
Other Services of the Near-RT RIC platform | Securing infrastructure for development, testing, and production environments is out of scope for O-RAN. | -| Application Security Testing (Formerly Application Security) | a) Utilization of static and dynamic testing methods for security testing

b) Performance of security testing including manual expert analysis before application deployment. | xApp:

ASSET-C-09

Near-RT RIC:

ASSET-C-13
ASSET-C-41
ASSET-C-43
Other Services of the Near-RT RIC platform | Guidance (b) is out of scope for O-RAN. | - -### 11.2.3 E2 Interface - -**Table E2 Interface -61: E2 Interface Identified Gaps Out of Scope for O-RAN** - -| CISA ZT Function | Guidance to reach initial stage | Asset(s) | Comments | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|------------------------------------------------------------------------------------------| -| Data ZT Function | | | | -| Visibility and Analytics Capability | a) Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | ASSET-D-09
ASSET-D-16
ASSET-D-17
ASSET-D-25
ASSET-D-30 | Data inventory, data categorization, and SIEM are out of scope for O-RAN specifications. | -| Automation and Orchestration Capability | a) Data lifecycle and security policies (e.g., access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) are automated. | ASSET-D-09
ASSET-D-16
ASSET-D-17
ASSET-D-25
ASSET-D-30 | Data lifecycle and security policies are out of scope for O-RAN specifications | -| Networks ZT Function | | | | -| Visibility and Analytics Capability | a) Utilize network monitoring capabilities based on known | ASSET-C-40 | The collection, analysis, and correlation of this information, and SIEM | - -| | | | | -|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------------| -| | indicators of compromise, including network enumeration, to develop situational awareness in each environment.

b) Commence correlating telemetry across traffic types and environments to facilitate analysis and threat hunting activities. | | are out of scope for O-RAN specifications | -| Automation and Orchestration Capability | a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments.

b) Ensure that all resources have a defined lifetime determined by policies and telemetry data. | ASSET-C-40 | Network resource configuration and lifecycle management is out of scope for O-RAN specifications. | - -### 11.2.4 Y1 Interface - -**Table Y1 Interface -62: Y1 Interface Identified Gaps Out of Scope for O-RAN** - -| CISA ZT Function | Guidance to reach initial stage | Asset(s) | Comments | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|------------------------------------------------------------------------------------------| -| Data ZT Function | | | | -| Visibility and Analytics Capability | a) Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | Data Transported over Y1 Interface | Data inventory, data categorization, and SIEM are out of scope for O-RAN specifications. | -| Automation and Orchestration Capability | a) Data lifecycle and security policies (e.g., access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) are automated. | Data Transported over Y1 Interface | Data lifecycle and security policies are out of scope for O-RAN specifications | -| Networks ZT Function | | | | -| Visibility and Analytics | a) Utilize network | ASSET-C-42 | The collection, analysis, | - -| | | | | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------------------------------------| -| Capability |

monitoring capabilities based on known indicators of compromise, including network enumeration, to develop situational awareness in each environment.

b) Commence correlating telemetry across traffic types and environments to facilitate analysis and threat hunting activities.

| | and correlation of this information, and SIEM are out of scope for O-RAN specifications | -| Automation and Orchestration Capability |

a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments.

b) Ensure that all resources have a defined lifetime determined by policies and telemetry data.

| ASSET-C-42 | Network resource configuration and lifecycle management is out of scope for O-RAN specifications. | - -### 11.2.5 rApp and Non-RT RIC - -**Table 11.2.5-63: rApp and Non-RT RIC Identified Gaps Out of Scope for O-RAN** - -| CISA ZT Function | Guidance to reach initial stage | Asset(s) | Comments | -|------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------| -| App/ Workloads ZT Function | | | | -| Application Access (Authorization) |

a) Access authorization capabilities utilize contextual information such as identity, device compliance, and other attributes to make decisions on various requests for accessing application assets.

b) Authorization is granted per request with expiration.

|

rApp:

ASSET-C-10
ASSET-C-12

Non-RT RIC:

ASSET-C-13
ASSET-C-15
ASSET-C-20
ASSET-C-47
ASSET-C-48
ASSET-C-55
ASSET-C-56

| Contextual information is out of scope for O-RAN. | -| Accessible Applications |

a) Applicable mission-critical applications are available over open public network connections to authorized users as needed.

|

rApp:

ASSET-C-10
ASSET-C-12

Non-RT RIC:

| No identified mission critical applications are available over open public networks. | - -| | | | | -|-----------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------| -| | | ASSET-C-13
ASSET-C-15
ASSET-C-20
ASSET-C-47
ASSET-C-48
ASSET-C-55
ASSET-C-56 | | -| Secure Application Development and Deployment Workflow (New Function) | a) Infrastructure for development, testing, and production environments (including automation).

b) Formal code deployment mechanisms through CI/CD pipelines.

c) Access controls support least privilege principles. | rApp:
ASSET-C-10
ASSET-C-12

Non-RT RIC:
ASSET-C-13
ASSET-C-15
ASSET-C-20
ASSET-C-47
ASSET-C-48
ASSET-C-55
ASSET-C-56 | Securing infrastructure for development, testing, and production environments is out of scope for O-RAN. | -| Application Security Testing (Formerly Application Security) | a) Utilization of static and dynamic testing methods for security testing

b) Performance of security testing including manual expert analysis before application deployment. | rApp:
ASSET-C-10
ASSET-C-12

Non-RT RIC:
ASSET-C-13
ASSET-C-15
ASSET-C-20
ASSET-C-47
ASSET-C-48
ASSET-C-55
ASSET-C-56 | Guidance (b) is out of scope for O-RAN. | - -## 11.2.6 A1 Interface - -**Table A1 Interface-64: A1 Interface Identified Gaps Out of Scope for O-RAN** - -| CISA ZT Function | Guidance to reach initial stage | Asset(s) | Comments | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------| -| Data ZT Function | | | | -| Visibility and Analytics Capability | a) Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | ASSET-D-07
ASSET-D-08
ASSET-D-16
ASSET-D-17
ASSET-D-25
ASSET-D-30 | Data inventory, data categorization, and SIEM are out of scope for O-RAN specifications. | -| Automation and Orchestration Capability | a) Data lifecycle and security policies (e.g., access, usage, storage, | ASSET-D-07
ASSET-D-08 | Data lifecycle and security policies are out of scope for O-RAN | - -| | | | | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------| -| | encryption, configurations, protections, backups, categorization, sanitization) are automated. | ASSET-D-16
ASSET-D-17
ASSET-D-25
ASSET-D-30 | specifications | -| Networks ZT Function | | | | -| Visibility and Analytics Capability | a) Utilize network monitoring capabilities based on known indicators of compromise, including network enumeration, to develop situational awareness in each environment.

b) Commence correlating telemetry across traffic types and environments to facilitate analysis and threat hunting activities. | ASSET-C-14 | The collection, analysis, and correlation of this information, and SIEM are out of scope for O-RAN specifications | -| Automation and Orchestration Capability | a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments.

b) Ensure that all resources have a defined lifetime determined by policies and telemetry data. | ASSET-C-14 | Network resource configuration and lifecycle management is out of scope for O-RAN specifications. | - -## 11.2.7 R1 Interface - -**Table R1 Interface-65: R1 Interface Identified Gaps Out of Scope for O-RAN** - -| CISA ZT Function | Guidance to reach initial stage | Asset(s) | Comments | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|------------------------------------------------------------------------------------------| -| Data ZT Function | | | | -| Visibility and Analytics Capability | a) Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | Data transported over the R1 interface | Data inventory, data categorization, and SIEM are out of scope for O-RAN specifications. | -| Automation and Orchestration Capability | a) Data lifecycle and security policies (e.g., access, usage, storage, encryption, configurations, protections, backups, | Data Transported over the R1 Interface | Data lifecycle and security policies are out of scope for O-RAN specifications | - -| | | | | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-------------------------------------------------------------------------------------------------------------------| -| | categorization, sanitization) are automated. | | | -| Networks ZT Function | | | | -| Visibility and Analytics Capability | a) Utilize network monitoring capabilities based on known indicators of compromise, including network enumeration, to develop situational awareness in each environment.

b) Commence correlating telemetry across traffic types and environments to facilitate analysis and threat hunting activities. | ASSET-C-16 | The collection, analysis, and correlation of this information, and SIEM are out of scope for O-RAN specifications | -| Automation and Orchestration Capability | a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments.

b) Ensure that all resources have a defined lifetime determined by policies and telemetry data. | ASSET-C-16 | Network resource configuration and lifecycle management is out of scope for O-RAN specifications. | - -### 11.2.8 SMO - -Void - -### 11.2.9 O1 Interface - -**Table O1 Interface-66: O1 Interface Identified Gaps Out of Scope for O-RAN** - -| CISA ZT Function | Guidance to reach initial stage | Asset(s) | Comments | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------|------------------------------------------------------------------------------------------| -| Data ZT Function | | | | -| Visibility and Analytics Capability | a) Utilizes data inventory management, data categorization, data encryption, and access attempts information with some automated analysis and correlation to obtain visibility. | ASSET-D-03
ASSET-D-16
ASSET-D-17
ASSET-D-18
ASSET-D-23
ASSET-D-24 | Data inventory, data categorization, and SIEM are out of scope for O-RAN specifications. | -| Automation and Orchestration Capability | a) Data lifecycle and security policies (e.g., | ASSET-D-03
ASSET-D-16 | Data lifecycle and security policies are out | - -| | | | | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------| -| | access, usage, storage, encryption, configurations, protections, backups, categorization, sanitization) are automated. | ASSET-D-17
ASSET-D-18
ASSET-D-23
ASSET-D-24 | of scope for O-RAN specifications | -| Networks ZT Function | | | | -| Visibility and Analytics Capability | a) Utilize network monitoring capabilities based on known indicators of compromise, including network enumeration, to develop situational awareness in each environment.

b) Commence correlating telemetry across traffic types and environments to facilitate analysis and threat hunting activities. | ASSET-C-22 | The collection, analysis, and correlation of this information, and SIEM are out of scope for O-RAN specifications | -| Automation and Orchestration Capability | a) Initiate the use of automated methods to manage the configuration and lifecycle of resources within specific networks or environments.

b) Ensure that all resources have a defined lifetime determined by policies and telemetry data. | ASSET-C-22 | Network resource configuration and lifecycle management is out of scope for O-RAN specifications. | - -**11.2.10 O-Cloud** - -Void - -**11.2.11 O2 Interface** - -Void - -**11.2.12 O-CU** - -Void - -**11.2.13 O-DU** - -Void - -**11.2.14 O-RU** - -Void - -## 11.2.15 Open Fronthaul Interface - -Void - -## 11.3 Identified Gaps Requiring No Action - -This clause lists all the gaps identified in clause 7.3 that have been reviewed and determined to require no further action, along with the rationale behind this decision. - -### 11.3.1 Transversal Functions - -**Table Transversal Functions-67: Transversal Functions Identified Requiring No Action** - -| CISA ZT Function | Guidance to reach initial stage | Asset(s) | Comments | -|-----------------------------------|---------------------------------|----------|----------| -| Data ZT Function | | | | -| ... | ... | ... | | -| App/ Workloads ZT Function | | | | -| ... | ... | ... | | -| Identity ZT Function | | | | -| ... | ... | ... | | -| Networks ZT Function | | | | -| ... | ... | ... | | -| Devices ZT Function | | | | -| ... | ... | ... | | - -### 11.3.2 xApp and Near-RT RIC - -**Table xApp and Near-RT RIC-68: xApp and Near-RT RIC Identified Gaps Requiring No Action** - -| CISA ZT Function | Guidance to reach initial stage | Asset(s) | Comments | -|-------------------------|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|---------------------------------------------------------------| -| Data ZT Function | | | | -| Data Access | a) Automated data access control

b) Elements of least privileges are incorporated with the automated data access control | xApp:

ASSET-D-16

Near-RT RIC:

ASSET-D-16
ASSET-D-39 | X.509 certs are publicly available | -| Data Encryption | a) Encrypted data in transit and, where feasible, data at rest. | Near-RT RIC: | xAppIDs are part of X.509 certs which are publicly available. | - -| | | | | -|--|---------------------------------------------------------------------------------------|------------|--| -| | b) Key management policies and secure encryption keys are beginning to be formalized. | ASSET-D-39 | | -|--|---------------------------------------------------------------------------------------|------------|--| - -### 11.3.3 E2 Interface - -Void - -### 11.3.4 Y1 Interface - -Void - -### 11.3.5 rApp and Non-RT RIC - -**Table 11.3.5-69: rApp and Non-RT RIC Identified Gaps Requiring No Action** - -| CISA ZT Function | Guidance to reach initial stage | Asset(s) | Comments | -|-------------------------|-----------------------------------------------------------------------------------------------------------------------------|----------------------------|------------------------------------| -| Data ZT Function | | | | -| Data Access | a) Automated data access control
b) Elements of least privileges are incorporated with the automated data access control | rApp:
ASSET-D-16 | X.509 certs are publicly available | - -### 11.3.6 A1 Interface - -Void - -### 11.3.7 R1 Interface - -Void - -### 11.3.8 SMO - -Void - -### 11.3.9 O1 Interface - -Void - -11.3.10 O-Cloud - -Void - -11.3.11 O2 Interface - -Void - -11.3.12 O-CU - -Void - -11.3.13 O-DU - -Void - -11.3.14 O-RU - -Void - -11.3.15 Open Fronthaul Interface - -Void - ---- - -## Annex: - -### Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|-----------------------------------------| -| 2024.07.24 | 01.00 | Final Version 1 of the Technical Report | -| 2024.11.26 | 02.00 | Final Version 2 of the Technical Report | -| 2025.03.19 | 03.00 | Final Version 3 of the Technical Report | -| 2025.07.09 | 04.00 | Final Version 4 of the Technical Report | -| 2025.12.03 | 05.00 | Final Version 5 of the Technical Report | \ No newline at end of file diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg deleted file mode 100644 index eeed00b102184be091e0a85984f1e2d0242e5c0b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:dfa752ed6ae36f8370f0ee1dfbd4d933c0a79e107ccda04b0ebb16beb82be4d4 -size 80686 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/03cece90958de8ea69661d3295cf3e88_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/03cece90958de8ea69661d3295cf3e88_img.jpg deleted file mode 100644 index f54c252b7a21107f3b99a70be721b4678f1b9e85..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/03cece90958de8ea69661d3295cf3e88_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:39ba73208a29577a599d1747faebd70f3262997413b07e838aad806209c69d2c -size 4478 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/09fcf056902487318885284a6b43b08c_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/09fcf056902487318885284a6b43b08c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/09fcf056902487318885284a6b43b08c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg deleted file mode 100644 index 69c38152e6b37636269ff84c6b134abd4d23df11..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5e2d6130933e4456bf3525ddcc61a4ca253305637f4c5c8d7f35a5033c4fdae2 -size 4529 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/145d00f59802048185303f15937ea65c_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/145d00f59802048185303f15937ea65c_img.jpg deleted file mode 100644 index 3e54544badc8b3a533b19a4033f6fd18e8be7afd..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/145d00f59802048185303f15937ea65c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e4a76b237cb7d46479b579e476dc12b3ff1def3552014644cb23d628ffa40492 -size 99623 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 141fbdc62d6a7c4f6feda1bfe8c44d950c04af96..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:db39ee763a9352985e7ffff991041a5361b07b2854780b51e34840f4adc5b3e0 -size 4549 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/1da66f5fec34c001912c84a9abf145d7_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/1da66f5fec34c001912c84a9abf145d7_img.jpg deleted file mode 100644 index 54097f4b0521f95fc68860b8fa073872e71453e2..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/1da66f5fec34c001912c84a9abf145d7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:898a416530818cd514691384f46dd6950286096b5ce315cb8cfff9b37fc62d81 -size 66595 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg deleted file mode 100644 index 141fbdc62d6a7c4f6feda1bfe8c44d950c04af96..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:db39ee763a9352985e7ffff991041a5361b07b2854780b51e34840f4adc5b3e0 -size 4549 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 8f3e31eb6a04031bb9e3dedf5d57c6e3734a6615..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:934c51137792a2b0d6e78ac71ebcd4d70a6f801318aa8fe0c4d51e68d2b8b245 -size 4523 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2a185522b492253375ed16f0c515c230_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2a185522b492253375ed16f0c515c230_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2a185522b492253375ed16f0c515c230_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2eea01382188b70064fa2818361d89f1_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2eea01382188b70064fa2818361d89f1_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/2eea01382188b70064fa2818361d89f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg deleted file mode 100644 index ba2ad72b20822f8620e2a3b2f50b68e64b74f843..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a436fd2b2e8b7b3cb0c35f6fd29185cd8bd54b3f4ce86a76dd415b9c01b95cc9 -size 4546 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/318db222fae24a59c370fa6471d541b8_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/318db222fae24a59c370fa6471d541b8_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/318db222fae24a59c370fa6471d541b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/35437f160e157760713aa85be471c3f3_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/35437f160e157760713aa85be471c3f3_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/35437f160e157760713aa85be471c3f3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/3b89d812329a65ab156184a40524adf0_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/3b89d812329a65ab156184a40524adf0_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/3b89d812329a65ab156184a40524adf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/446100c084b94817a19c319fa776b412_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/446100c084b94817a19c319fa776b412_img.jpg deleted file mode 100644 index 301fdbf67f7f503434adcba9809c858f131e3f70..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/446100c084b94817a19c319fa776b412_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9694bfb2aadc8ac08ad1b1cf0a2e323016bb19eb0ba6c18b742237a8434d73a9 -size 33625 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/5009e30a55479d3941af523871208f9d_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/5009e30a55479d3941af523871208f9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg deleted file mode 100644 index 959b8c3833d4d890a998b87ceb6030be70371101..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2c3d7cb543eb0cba6b1b46744f7e05ff0b1a0fe1d23ef813a179e1c94d550f05 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/568031aac86c633aab96b734dba3835e_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/568031aac86c633aab96b734dba3835e_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/568031aac86c633aab96b734dba3835e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/59368942873b0c35eef79a7a985025dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6588b1c7f14069d96744b473ad663248_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6983ff962c0a32659de18c30790e1519_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6983ff962c0a32659de18c30790e1519_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6983ff962c0a32659de18c30790e1519_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index e32dff5973d703d9c268b2c57ee52fba01755283..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3b12e715836cf0f3c6d44bb401046aa0f23085096fc1cb57e59d16b9324db3f2 -size 4533 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 141fbdc62d6a7c4f6feda1bfe8c44d950c04af96..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:db39ee763a9352985e7ffff991041a5361b07b2854780b51e34840f4adc5b3e0 -size 4549 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index bf238570411b2c3c4801758e0b4fee8375ccb9f4..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef39b9b0dadf1b084c8b8bc63a0ff7d1585b6d745ca12ad8368f11082cad5a0 -size 4493 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/854df8ad60507803253274673f9062cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8b4befaffc5166da571069410e207aea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 141fbdc62d6a7c4f6feda1bfe8c44d950c04af96..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:db39ee763a9352985e7ffff991041a5361b07b2854780b51e34840f4adc5b3e0 -size 4549 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg deleted file mode 100644 index f6810e1beca7b9f166b8f87d9694c36866f5f50a..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95f1083d6e62ab468ec376639d4636af3ee2b0ac5283fd84b67c8d1685caf89b -size 4572 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg deleted file mode 100644 index 141fbdc62d6a7c4f6feda1bfe8c44d950c04af96..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:db39ee763a9352985e7ffff991041a5361b07b2854780b51e34840f4adc5b3e0 -size 4549 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 141fbdc62d6a7c4f6feda1bfe8c44d950c04af96..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:db39ee763a9352985e7ffff991041a5361b07b2854780b51e34840f4adc5b3e0 -size 4549 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/aef4390a4629604196222b9ed006a786_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/aef4390a4629604196222b9ed006a786_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/aef4390a4629604196222b9ed006a786_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/bb9f586190c7197099d25db7df9050af_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/bb9f586190c7197099d25db7df9050af_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/bb9f586190c7197099d25db7df9050af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d35a80e3faed208324083399568c7461_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d35a80e3faed208324083399568c7461_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d35a80e3faed208324083399568c7461_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index bf238570411b2c3c4801758e0b4fee8375ccb9f4..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef39b9b0dadf1b084c8b8bc63a0ff7d1585b6d745ca12ad8368f11082cad5a0 -size 4493 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 99672dfc824980d5235afbb8187122ac4975144e..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7509f36f408a2e6d74f3ba7cfcfa248d081156f55ca6720118e8883082b2237d -size 4536 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/f74adaa1840504407cd4272995426f82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 69c38152e6b37636269ff84c6b134abd4d23df11..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5e2d6130933e4456bf3525ddcc61a4ca253305637f4c5c8d7f35a5033c4fdae2 -size 4529 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/facce731b2dbfae43a8609231a700be1_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/facce731b2dbfae43a8609231a700be1_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/facce731b2dbfae43a8609231a700be1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 4aee070d62d8a13849ad185411e3589af47ecff4..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4a659b40609dfa09792e67b7690f86e7c0508b80389cd2d7737777038be01e00 -size 4526 diff --git a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TR.ZTA-R005-v05.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/doc.md b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/doc.md deleted file mode 100644 index 9ab47f96767fa7fc236b7e0ec447281e636ca557..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/doc.md +++ /dev/null @@ -1,10551 +0,0 @@ - - -# --- **O-RAN Work Group 11 (Security Work Group)****O-RAN Security Test Specifications** - -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 - -| | | -|--------------------------------------------------------------|----| -| List of figures ..... | 8 | -| List of tables ..... | 8 | -| Foreword ..... | 9 | -| Modal verbs terminology ..... | 9 | -| 1 Scope ..... | 10 | -| 2 References ..... | 10 | -| 2.1 Normative references ..... | 10 | -| 2.2 Informative references..... | 11 | -| 3 Definition of terms, symbols and abbreviations..... | 12 | -| 3.1 Terms 12 | | -| 3.2 Symbols..... | 12 | -| 3.3 Abbreviations ..... | 13 | -| 4 Objectives and scope..... | 15 | -| 5 Testing methodology and configuration ..... | 16 | -| 5.1 DUT / SUT..... | 16 | -| 5.2 Test Setup..... | 17 | -| 5.3 Test and measurement equipment and tools ..... | 17 | -| 5.4 Test report ..... | 19 | -| 5.5 Assumptions..... | 19 | -| 5.6 Testing tools..... | 19 | -| 6 Security Protocol & APIs Validation ..... | 22 | -| 6.1 Overview ..... | 22 | -| 6.2 SSH Server & Client ..... | 22 | -| 6.3 TLS 23 | | -| 6.3.1 TLS Support ..... | 23 | -| 6.3.2 TLS Version Negotiation ..... | 24 | -| 6.3.3 TLS Deprecated Versions ..... | 25 | -| 6.4 DTLS 26 | | -| 6.5 IPsec 26 | | -| 6.5.1 IPsec security..... | 26 | -| 6.5.2 IKE Header Flags Fuzzing ..... | 27 | -| 6.5.3 IKE Key Exchange Payload Fuzzing ..... | 28 | -| 6.5.4 IKE Malformed Certificate Payload ..... | 30 | -| 6.6 OAuth 2.0 ..... | 31 | -| 6.6.1 API Consumer..... | 31 | -| 6.6.2 Resource Server..... | 33 | -| 6.7 NACM..... | 35 | -| 6.7.1 NACM Configuration ..... | 35 | -| 6.7.2 Void 36 | | -| 6.7.3 Void 36 | | -| 6.8 802.1X..... | 36 | -| 6.9 X.509 37 | | -| 6.9.1 X.509 Certificate Structure Verification for TLS ..... | 37 | -| 6.9.2 X.509 Certificate Validity Period Verification ..... | 38 | -| 6.9.3 X.509 Certificate Key Usage Verification ..... | 39 | -| 6.9.4 X.509 Certificate Chain Validation..... | 40 | -| 6.10 eCPRI ..... | 41 | -| 6.10.1 Void 41 | | -| 6.10.2 eCPRI Input Validation..... | 41 | -| 6.10.3 eCPRI Error and Timeout Handling..... | 42 | -| 6.10.4 Void 43 | | - -| | | -|----------------------------------------------------------------------------------------|-----------| -| 6.10.5 eCPRI Logging and Auditing..... | 43 | -| 6.10.6 Void | 44 | -| 6.11 SCTP ..... | 44 | -| 6.11.1 Void | 44 | -| 6.11.2 Void | 44 | -| 6.11.3 Void | 44 | -| 6.11.4 Void | 44 | -| 6.11.5 SCTP DoS Prevention Rate Limiting..... | 44 | -| 6.11.6 SCTP Input Validation..... | 45 | -| 6.11.7 Void | 46 | -| 6.11.8 Void | 46 | -| 6.12 Transactional APIs ..... | 46 | -| 6.12.1 Transactional API Authentication – service producer role ..... | 46 | -| 6.12.2 Transactional API Authorization and Access Control ..... | 47 | -| 6.12.3 Transactional API Input Validation and Sanitization ..... | 48 | -| 6.12.4 Transactional API Security Logging and Monitoring..... | 50 | -| 6.13 MACsec..... | 51 | -| 6.13.1 MACsec Cipher Suite Negotiation and Support Validation ..... | 51 | -| 6.13.2 MACsec protection of Open FH traffic..... | 52 | -| 6.13.3 Cleartext policy exception for Open FH traffic ..... | 54 | -| 7 Common Network Security Tests for O-RAN architecture elements ..... | 56 | -| 7.1 Overview ..... | 56 | -| 7.2 Network Protocol and Service Enumeration..... | 56 | -| 7.2.1 Network Protocol and Service Enumeration..... | 56 | -| 7.3 Password-Based Authentication..... | 57 | -| 7.3.1 Password guessing..... | 57 | -| 7.3.2 Unauthorized Password Reset..... | 59 | -| 7.3.3 Password Policy Enforcement..... | 60 | -| 7.3.4 Default Password Change ..... | 61 | -| 7.3.5 Passwords stored as salted..... | 62 | -| 7.3.6 Client secrets stored encrypted..... | 62 | -| 7.3.7 O-RU Password Policy Enforcement..... | 63 | -| 7.4 Network Protocol Fuzzing ..... | 64 | -| 7.5 Denial of Service/Message Flooding ..... | 66 | -| 7.5.1 Protocol, Application and Volumetric Based DDoS Attacks ..... | 66 | -| 7.5.2 Void | 68 | -| 7.5.3 Void | 68 | -| 7.5.4 Void | 68 | -| 7.5.5 Near-RT RIC A1 interface DoS/DDoS protection and recovery ..... | 68 | -| 7.6 Input validation and error handling..... | 68 | -| 7.6.1 O-CU input validation and error handling ..... | 68 | -| 7.6.2 O-DU input validation and error handling ..... | 69 | -| 7.6.3 Near-RT RIC input validation and error handling ..... | 71 | -| 7.6.4 Near-RT RIC input validation and error handling of data received from xApp ..... | 72 | -| 7.7 Secure configuration enforcement ..... | 73 | -| 7.8 Logging and monitoring..... | 74 | -| 7.8.1 O-CU logging and monitoring ..... | 74 | -| 7.8.2 O-DU logging and monitoring ..... | 75 | -| 7.8.3 O-RU logging and monitoring ..... | 76 | -| 7.8.4 Near-RT RIC logging and monitoring ..... | 77 | -| 8 System security evaluation for O-RAN architecture elements ..... | 78 | -| 8.1 Overview ..... | 78 | -| 8.2 System Vulnerability Scanning..... | 79 | -| 8.2.1 System Vulnerability Scanning..... | 79 | -| 8.3 Data and Information Protection ..... | 79 | -| 8.4 System logging..... | 79 | -| 8.4.1 Introduction ..... | 79 | -| 8.4.2 Security log format and related log fields ..... | 79 | -| 8.4.3 Authenticated Time Stamping..... | 80 | -| 8.4.4 Network Security and System Security Events..... | 81 | - -8.4.5 Application Security Events..... 84 - -8.4.6 Data Access Security Events..... 84 - -8.4.7 Account and Identity Security Events..... 86 - -8.4.8 General Security Events ..... 88 - -8.4.9 Void 89 - -9 Software security evaluation for O-RAN architecture elements..... 89 - -9.1 Overview ..... 89 - -9.2 Open-Source Software Component Analysis..... 89 - -9.3 Binary Static Analysis..... 89 - -9.4 Software Bill of Materials (SBOM)..... 90 - -9.4.1 SBOM Signature ..... 90 - -9.4.2 SBOM Data Fields ..... 90 - -9.4.3 SBOM Format..... 93 - -9.4.4 SBOM Depth..... 94 - -9.4.5 Void 94 - -9.4.6 SBOM Version Verification..... 94 - -9.4.7 Void 95 - -9.4.8 SBOM Presence ..... 95 - -9.4.9 SBOM Vulnerabilities Field..... 96 - -9.4.10 Void 96 - -9.5 Signature Verification ..... 96 - -9.5.1 Signature Verification Matrix per DUT and Phase..... 96 - -9.5.2 Signature Verification Test Cases ..... 97 - -10 ML security validation for O-RAN system..... 100 - -10.1 Overview..... 100 - -10.2 ML Data Poisoning ..... 101 - -11 Security tests of O-RAN interfaces ..... 101 - -11.1 Open FH ..... 101 - -11.1.1 Overview ..... 101 - -11.1.2 Open Fronthaul Point-to-Point LAN Segment..... 101 - -11.1.3 M-Plane ..... 108 - -11.1.4 U-Plane..... 122 - -11.1.5 S-Plane ..... 124 - -11.2 Y1 129 - -11.2.1 Y1 Authenticity ..... 129 - -11.2.2 Y1 confidentiality, integrity, and replay protection ..... 131 - -11.2.3 Y1 Authorization..... 132 - -11.3 O1 133 - -11.3.1 O1 Authenticity ..... 133 - -11.3.2 O1 confidentiality, integrity and replay protection ..... 135 - -11.3.3 O1 Interface Network Configuration Access Control Model (NACM) Validation..... 136 - -11.4 O2 138 - -11.4.1 O2 Authenticity ..... 138 - -11.4.2 O2 confidentiality, integrity and replay protection ..... 139 - -11.4.3 O2 Authorization..... 140 - -11.5 E2 141 - -11.5.1 E2 confidentiality, integrity and replay protection..... 141 - -11.5.2 E2 Authenticity ..... 143 - -11.6 A1 147 - -11.6.1 A1 Authenticity ..... 147 - -11.6.2 A1 confidentiality, integrity and replay protection ..... 148 - -11.6.3 A1 Authorization..... 149 - -11.7 R1 150 - -11.7.1 R1 Authenticity ..... 150 - -11.7.2 R1 confidentiality, integrity and replay protection ..... 151 - -11.7.3 R1 Authorization..... 153 - -12 Security test of O-RU ..... 154 - -12.1 Overview ..... 154 - -| | | -|----------------------------------------------------------------------------------|-----| -| 12.2 SSH on M-Plane interface..... | 154 | -| 12.3 TLS on M-Plane interface..... | 155 | -| 12.4 Security functional requirements and test cases..... | 155 | -| 13 Security test of Near-RT RIC..... | 155 | -| 13.1 Overview..... | 155 | -| 13.2 Void 155 | | -| 13.3 Transactional APIs..... | 155 | -| 13.3.1 Introduction..... | 155 | -| 13.3.2 TLS for transactional APIs..... | 156 | -| 13.3.3 mTLS for transactional APIs..... | 156 | -| 13.3.4 OAuth 2.0 for transactional APIs..... | 157 | -| 13.4 Security test of Near-RT RIC OAuth 2.0 Resource Owner/Server..... | 157 | -| 13.4.1 Overview..... | 157 | -| 13.4.2 Near-RT RIC OAuth 2.0 Resource Owner/Server..... | 157 | -| 13.5 Security test of Near-RT RIC OAuth 2.0 client..... | 158 | -| 13.5.1 Overview..... | 158 | -| 13.5.2 Near-RT RIC OAuth 2.0 client..... | 158 | -| 14 Security test of xApps..... | 159 | -| 14.1 Overview..... | 159 | -| 14.2 xApp Signing and Verification..... | 159 | -| 14.3 xAppID..... | 159 | -| 14.3.1 xApp ID format check..... | 159 | -| 14.3.2 xApp ID in xApp instance Certificate..... | 160 | -| 15 Security test of Non-RT RIC..... | 161 | -| 15.1 Overview..... | 161 | -| 15.2 Non-RT RIC..... | 161 | -| 15.2.1 Non-RT RIC OAuth 2.0 Resource Owner/Server..... | 161 | -| 15.2.2 Non-RT RIC OAuth 2.0 Client..... | 161 | -| 15.2.3 Non-RT RIC Framework OAuth 2.0..... | 162 | -| 15.3 R1 interface..... | 162 | -| 15.4 A1 interface..... | 162 | -| 16 Security test of rApps..... | 163 | -| 16.1 Overview..... | 163 | -| 16.2 rApp Signing and Verification..... | 163 | -| 16.3 rApp Authorization..... | 163 | -| 16.3.1 rApp OAuth 2.0 Client..... | 163 | -| 17 Security test of SMO..... | 163 | -| 17.1 Overview..... | 163 | -| 17.2 Void 164 | | -| 17.3 SMO 164 | | -| 17.3.1 SMO OAuth 2.0 Resource Owner/Server..... | 164 | -| 17.3.2 SMO OAuth 2.0 Client..... | 164 | -| 17.3.3 SMO mTLS for mutual authentication..... | 165 | -| 17.4 SMO Internal Communications..... | 166 | -| 17.4.1 TLS for SMO Internal Communications..... | 166 | -| 17.4.2 mTLS for SMO Internal Communications – SMO Functions..... | 166 | -| 17.5 SMO External Interfaces..... | 167 | -| 17.5.1 TLS for SMO External Interfaces..... | 167 | -| 17.5.2 mTLS for SMO External Interfaces..... | 167 | -| 17.5.3 SMO Framework OAuth 2.0 Resource Owner/Server for External Interface..... | 168 | -| 17.5.4 SMO Functions OAuth 2.0 Client..... | 168 | -| 17.6 SMO Logging..... | 169 | -| 17.6.1 TLS for SMO Logging Export..... | 169 | -| 17.6.2 mTLS for SMO Logging Export..... | 169 | -| 18 Security test of O-Cloud..... | 170 | -| 18.1 Overview..... | 170 | -| 18.2 Void 170 | | - -| | | -|---------------------------------------------------------------------------------------------------------|-----| -| 18.3 O-Cloud virtualization layer..... | 170 | -| 18.3.1 Secure authentication (positive case)..... | 170 | -| 18.3.2 Secure authentication (negative case)..... | 171 | -| 18.3.3 Secure authorization (positive case)..... | 171 | -| 18.3.4 Secure authorization (negative case)..... | 172 | -| 18.3.5 Validate network connections allowed by network policies..... | 173 | -| 18.3.6 Validate network connections not allowed by network policies..... | 174 | -| 18.3.7 Validate network connections from outside the allowed network ranges..... | 175 | -| 18.3.8 Exploitation of O-Cloud component vulnerabilities..... | 175 | -| 18.3.9 Identification and remediation of insecure configuration settings..... | 176 | -| 18.3.10 Validation of logging and monitoring for security incidents..... | 177 | -| 18.3.11 O-Cloud Privilege Escalation Prevention..... | 178 | -| 18.3.12 O-Cloud mutual authentication..... | 178 | -| 18.3.13 O-Cloud authorization..... | 180 | -| 18.4 Application deployment by O-Cloud..... | 181 | -| 18.4.1 Verification of Application artifacts with valid signature by O-Cloud during deployment..... | 181 | -| 18.4.2 Verification of Application artifacts with incorrect signature by O-Cloud during deployment..... | 181 | -| 18.5 Resource Management and enforcement in O-Cloud..... | 181 | -| 18.5.1 O-Cloud Resource Consumption Limit Enforcement..... | 181 | -| 18.5.2 O-Cloud Storage Volume Limit Enforcement..... | 182 | -| 18.5.3 O-Cloud CPU Overcommit Prevention..... | 184 | -| 18.5.4 O-Cloud Memory Overcommit Prevention..... | 185 | -| 18.5.5 O-Cloud Network Overcommit Prevention..... | 187 | -| 18.5.6 O-Cloud Storage Overcommit Prevention..... | 188 | -| 18.6 Secure Update..... | 189 | -| 18.6.1 O-Cloud Infrastructure Software Package Integrity - Positive..... | 189 | -| 18.6.2 O-Cloud Infrastructure Software Package Integrity Failure – Negative..... | 190 | -| 18.6.3 Secure Update procedure for O-Cloud Platform – Positive..... | 191 | -| 18.6.4 Secure Update failure and rollback..... | 192 | -| 18.6.5 Unauthorised Rollback Prevention..... | 193 | -| 18.7 Secure Storage..... | 194 | -| 18.7.1 Sensitive data protection in O-Cloud..... | 194 | -| 18.7.2 Secure data deletion in O-Cloud..... | 195 | -| 18.7.3 Data isolation in VM/Container reallocation..... | 197 | -| 18.8 Chain of trust..... | 198 | -| 18.8.1 Chain of Trust verification in static O-Cloud SW..... | 198 | -| 18.8.2 Chain of Trust verification of dynamic O-Cloud SW..... | 199 | -| 18.9 Secure time synchronization for O-Cloud..... | 200 | -| 19 Security test of VNF/CNF..... | 201 | -| 19.1 Overview..... | 201 | -| 19.2 Executive environment protection..... | 201 | -| 19.3 Signature validation during App image onboarding..... | 202 | -| 19.4 Void 202..... | 202 | -| 20 Security tests of Common Application Lifecycle Management..... | 202 | -| 20.1 Overview..... | 202 | -| 20.2 Application package..... | 202 | -| 20.2.1 Application package signature verification..... | 202 | -| 20.2.2 Minimum Requirements..... | 202 | -| 20.2.3 App Package Change Log..... | 203 | -| 20.3 Secure Decommissioning..... | 204 | -| 20.3.1 Post-Decommission Report..... | 204 | -| 20.3.2 Trust Artifact Revocation..... | 204 | -| 21 Security test of O-CU-CP..... | 205 | -| 21.1 Overview..... | 205 | -| 21.2 O-CU-CP 3GPP specific security functional requirements and test cases..... | 205 | -| 21.3 O-RAN specific security functional requirements and test cases..... | 206 | -| 22 Security test of O-CU-UP..... | 206 | -| 22.1 Overview..... | 206 | - -| | | -|----------------------------------------------------------------------------------|-----| -| 22.2 O-CU-UP 3GPP specific security functional requirements and test cases ..... | 206 | -| 22.3 O-RAN specific security functional requirements and test cases ..... | 206 | -| 23 Security test of O-DU..... | 206 | -| 23.1 Overview..... | 206 | -| 23.2 O-DU 3GPP specific security functional requirements and test cases..... | 207 | -| 23.3 O-RAN specific security functional requirements and test cases ..... | 207 | -| 24 End-to-End security test cases..... | 207 | -| 24.0 Overview..... | 207 | -| 24.1 3GPP Security Assurance Specification (SCAS)..... | 207 | -| 24.2 DoS, fuzzing and blind exploitation test..... | 212 | -| 24.2.1 S-Plane ..... | 213 | -| 24.2.2 C-Plane..... | 215 | -| 24.2.3 AI interface..... | 220 | -| 24.2.4 O-Cloud..... | 224 | -| 25 Security test of Shared O-RU..... | 226 | -| 25.1 Overview..... | 226 | -| 25.2 Shared O-RU test cases..... | 226 | -| 25.2.1 mTLS for mutual authentication ..... | 226 | -| 25.2.2 NACM Authorization..... | 227 | -| 25.2.3 TLS across Open Fronthaul..... | 228 | -| 25.2.4 Reject Password-based authentication ..... | 228 | -| Annex A (informative): Example of Security Testing Tools / Toolset..... | 230 | -| Annex B (informative): Template of test report ..... | 231 | -| Annex (informative): Change History..... | 234 | - -# List of figures - -Figure 5-1: Logical Architecture of O-RAN system..... 16 - -Figure 6-1: Token request using mTLS and Service request ..... 32 - -Figure 6-2: Token request with secret ID and Service request..... 33 - -Figure 6-3: Token request using mTLS and Service Request..... 35 - -Figure 6-4: Token request with secret ID and Service request..... 35 - -Figure 24-1: S-Plane O-DU Test setup..... 214 - -Figure 24-2: S-Plane PTP Unexpected Input Test Setup..... 215 - -Figure 24-3: C-Plane eCPRI DoS Attack Test Setup ..... 216 - -Figure 24-4: C-Plane eCPRI Unexpected Input Test Setup ..... 217 - -Figure 24-5: C-Plane eCPRI DoS Attack on O-RU Test Setup ..... 219 - -Figure 24-6: C-Plane eCPRI Unexpected Input on O-RU Test Setup ..... 220 - -Figure 24-7: Near-RT RIC A1 Interface DoS Attack Test Setup ..... 221 - -Figure 24-8: Near-RT RIC A1 Interface Unexpected Input Test Setup ..... 222 - -Figure 24-9: Near-RT RIC A1 Vulnerability Assessment Test Setup ..... 224 - -Figure 24-10: O-Cloud side-channel DoS attack Test Setup ..... 225 - -# List of tables - -Table 5-1: Test and measurement equipment list ..... 18 - -Table 9-1: Minimum set of data fields for SPDIX [12]..... 92 - -Table 9-2: Minimum set of data fields for CycloneDX [13]..... 92 - -Table 9-3: Minimum set of data fields for SWID [13]..... 92 - -Table 9-4: Signature verification per DUT, signed object and phase..... 97 - -Table 11-1: Scenarios to be executed..... 102 - -Table 11-2: Expected results ..... 102 - -Table 11-3: Scenarios to be executed ..... 103 - -Table 11-4: Expected results ..... 103 - -Table 24-1: List of SCAS Test Cases for NR and applicable technology from Clause 4.2.2 of 3GPP TS 33.511 ..... 208 - -Table 24-2: List of SCAS Test Cases for LTE and applicable technology from Clause 4.2.2 of 3GPP TS 33.216 ..... 210 - -Table 24-3: End-to-end test cases and applicable technology..... 213 - -Table Annex A-1: List of sample open source security testing tools/toolset..... 230 - -# --- Foreword - -This Technical Specification (TS) has been produced by WG11 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 description of the Security Tests, which validate security functions and configurations per security and security protocols requirements and are based on the priority of the risk analysis for O-RAN systems. - -# 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.WG11.TS.SPS: "O-RAN Security Protocols Specifications" -- [3] void -- [4] O-RAN.TIFG.TS.E2E-Test: "O-RAN End-to-End Test Specification" -- [5] O-RAN.WG11.TS.SRCS: "O-RAN Security Requirements and Controls Specifications" -- [6] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications" -- [7] 3GPP TS 33.117: "Catalogue of General Security Assurance Requirements" -- [8] 3GPP TS 33.511: "Security Assurance Specification (SCAS) for the next generation Node B (gNodeB) network product class" -- [9] 3GPP TS 33.216: "Security Assurance Specification (SCAS) for the Evolved Node B (eNodeB) network product class" -- [10] ISO 8601: "Date and time" -- [11] "IEEE Standard for Local and Metropolitan Area Networks--Port-Based Network Access Control," in IEEE Std 802.1X-2020 (Revision of IEEE Std 802.1X-2010 Incorporating IEEE Std 802.1Xb-2014 and IEEE Std 802.1Xck-2018), vol., no., pp.1-289, 28 Feb. 2020, doi: 10.1109/IEEESTD.2020.9018454 -- [12] "Generating Software Bills of Materials (SBOMs) with SPD-X at Microsoft", -- [13] NTIA: "The Minimum Elements For a Software Bill of Materials (SBOM)", [https://www.ntia.gov/sites/default/files/publications/sbom\\_minimum\\_elements\\_report\\_0.pdf](https://www.ntia.gov/sites/default/files/publications/sbom_minimum_elements_report_0.pdf) -- [14] IETF RFC 8341: "Network Configuration Access Control Model", -- [15] IETF RFC 5905: "Network Time Protocol Version 4: Protocol and Algorithms Specification", -- [16] IETF RFC 5906: "Network Time Protocol Version 4: Autokey Specification", - -- [17] IETF RFC 4493: "The AES-CMAC Algorithm", -- [18] IETF RFC 8446: "The Transport Layer Security (TLS) Protocol Version 1.3", -- [19] IETF RFC 7519: "JSON Web Token (JWT)", -- [20] IETF RFC 7515: "JSON Web Signature (JWS)", -- [21] O-RAN.WG4.TS.MP: "O-RAN WG4 Management Plane Specification" -- [22] O-RAN.WG1.TS.Use-Cases-Detailed-Specification: "O-RAN Use Cases Detailed Specification" -- [23] 3GPP TS 33.523: "5G Security Assurance Specification (SCAS); Split gNB product classes" -- [24] void -- [25] 3GPP TS 33.501: "Security architecture and procedures for 5G system" -- [26] O-RAN.WG4.TS.CUS: "O-RAN WG4 Control, User and Synchronization Plane Specification" -- [27] O-RAN.WG3.TS.RICARCH: "O-RAN Near-RT RIC Architecture" -- [28] O-RAN.WG3.TS.E2AP: "O-RAN E2 Application Protocol (E2AP)" -- [29] O-RAN.WG3.E2TS: "O-RAN E2 Interface Test Specification" -- [30] IETF RFC 9562: "Universally Unique Identifiers (UUIDs)", -- [31] O-RAN.WG10.TS.OnboardingSMOSGAP: "Onboarding SMOS General Aspects and Principles" -- [32] IEEE Std 802.1AE-2018: "IEEE Standard for Local and metropolitan area networks — Media Access Control (MAC) Security". - -## 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] Service Name and Transport Protocol Port Number Registry, -- [i.2] SPDX, -- [i.3] CycloneDX, -- [i.4] NIST IR 8060: "Guidelines for the Creation of Interoperable Software Identification (SWID) Tags", -- [i.5] O-RAN.WG11.TR.Threat-Modeling: "O-RAN Security Threat Modeling and Risk Assessment" - -# 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For definitions of the security terms Attack, Attack surface, Risk, Security control, Technical control, Threat, and Vulnerability used in this document, refer to [i.5]. - -For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [6], O-RAN Architecture Description [1], and the following in this clause apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [6] and O-RAN Architecture Description [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. - -**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. - -**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. - -**Overcommitting resources:** The practice of allocating or promising more resources than are physically available on a system. This concept is commonly used in virtualized and cloud environments. The idea behind overcommitment is to optimize resource utilization based on the observation that not all applications will use their allocated resources to the maximum at the same time. Here's a breakdown of overcommitment for different resources: - -- CPU Overcommitment: More virtual CPUs (vCPUs) are allocated to VMs or Containers than there are physical CPU cores available on the host. -- Memory Overcommitment: The total memory allocated to VMs or Containers exceeds the physical RAM available on the host. -- Storage Overcommitment: More storage space is allocated to VMs or Containers than the actual available capacity on the storage device. -- Network Overcommitment: More bandwidth is promised to VMs or Containers than the physical network can provide. - -**Overcommit ratios:** The extent to which resources can be overallocated compared to the actual available physical resources. - -- CPU Overcommit Ratio: A CPU overcommit ratio of 2:1 indicates that twice the number of virtual CPUs (vCPUs) can be allocated compared to the physical CPU cores available on the host. For instance, if a server has 8 physical CPU cores, 16 vCPUs could be allocated across various VMs or Containers. -- Memory Overcommit Ratio: A memory overcommit ratio of 1.5:1 indicates that 1.5 times the amount of virtual RAM can be allocated compared to the physical RAM available on the host. For a server with 64GB of physical RAM, a total of 96GB of RAM could be allocated across various VMs or Containers. - -**Signed object:** A signed unit of content that is subject to signature verification. This term encompasses application packages, software images, application artifacts, update bundles, AI/ML models, and any content requiring authenticity and integrity validation by a DUT during onboarding, deployment, or instantiation. - -For definition of the terms Application, Application Artifact, and Application Package see the WG10 Onboarding SMOS General Aspects and Principles document [31], clause 3.1. Other terms defined in WG10 Onboarding SMO General Aspects and Principles [31] also apply. - -## 3.2 Symbols - -Void - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given 3GPP TR21.905 [6], O-RAN Architecture Description [1], and the following in this clause apply. A abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR21.905 [6] and O-RAN Architecture Description [1]. - -AI/ML Artificial Intelligence / Machine Learning - -CMS/PKCS#7/CADES Cryptographic Message Syntax/Public-Key Cryptography Standards/CMS Advanced Electronic Signatures - -CNF Cloud Native Function - -COT Chain of Trust - -CSI Channel State Information - -CSR Certificate Signing Request - -DoS Denial of Service - -DTLS Datagram Transport Layer Security - -DUT Device Under Test - -eCPRI Enhanced Common Public Radio Interface - -FTP File Transfer Protocol - -FTPS File Transfer Protocol Secure - -IPsec Internet Protocol Security - -JSF JSON Signature Format - -JSON JavaScript Object Notation - -JWT JSON Web Token - -JWS JSON Web Signature - -KPI Key Performance Indicator - -LLS Low Layer Split - -mTLS Mutual Transport Layer Security - -MITM Man-in-the-Middle - -NACM Network Configuration Access Control Model - -NETCONF Network Configuration Protocol - -NFO Network Function Orchestration - -NTIA National Telecommunications and Information Administration - United States Department of Commerce - -OAuth Open Authentication - -PDCP Packet Data Convergence Protocol - -PNF Physical Network Function - -PRTC Primary Reference Time Clock - -PTP Precision Timing Protocol - -RBAC Role-based Access Control - -REST Representational state transfer - -RDF Resource Description Format - -RIC O-RAN RAN Intelligent Controller - -RoT Root of Trust - -SBOM Software Bill of Materials - -SDLC Software Development Lifecycle - -SSH Secure Shell - -SUT System Under Test - -TLS Transport Layer Security - -VNF Virtualized Network Function - -WAS Web Application Security - -XML Extensible Markup Language - -YAML YAML Ain't Markup Language - -# --- 4 Objectives and scope - -This security test specification is focused on: - -- Validating the implementation of security requirements and security protocols specified in [5] and [2]. -- Emulating security attacks against the O-RAN architecture elements, interfaces, and the system to measure the robustness of the O-RAN system and the service impact(s). -- Validating the effectiveness of the security mitigation method(s) to protect the O-RAN system and the services it offers. -- Providing consistent test setups that ensure fair and comparable test results among various test campaigns. -- Describing the test conditions, methodologies, and procedures, so that the tests can be reproduced if needed, and the test results can be used for comparison or reference purposes. - -This security test specification is based on the priority of the risk assessment of the O-RAN security threats and security requirements of the O-RAN system. - -# 5 Testing methodology and configuration - -## 5.1 DUT / SUT - -![Figure 5-1: Logical Architecture of O-RAN system. The diagram shows the hierarchy of O-RAN components and their interfaces. At the top is the Service Management and Orchestration Framework (SMO) containing the Non-Real Time RIC. Below it is the Near-Real Time RIC, which connects to Y1 consumers and O-eNB via O1 and E2 interfaces. The Near-RT RIC also connects to the O-CU-CP via an A1 interface. The O-CU-CP and O-CU-UP are connected via an E1 interface. The O-CU-CP connects to the O-DU via an F1-c interface, and the O-CU-UP connects to the O-DU via an F1-u interface. The O-DU and O-RU are connected via the Open FH CUS-Plane, and the O-RU connects to the O-eNB via the Open FH M-Plane. The O-RU also connects to the O-Cloud via the Open FH M-Plane. The O-Cloud is connected to the SMO via an O2 interface. A legend indicates that black lines represent 3GPP interfaces (X2-c, X2-u, NG-u, Xn-c, Xn-u, NG-c) and green lines represent O-RAN interfaces (O1, O2, A1, E1, E2, F1-c, F1-u, Y1).](16152cf1d84aea10848758f51a91ff6a_img.jpg) - -Figure 5-1: Logical Architecture of O-RAN system. The diagram shows the hierarchy of O-RAN components and their interfaces. At the top is the Service Management and Orchestration Framework (SMO) containing the Non-Real Time RIC. Below it is the Near-Real Time RIC, which connects to Y1 consumers and O-eNB via O1 and E2 interfaces. The Near-RT RIC also connects to the O-CU-CP via an A1 interface. The O-CU-CP and O-CU-UP are connected via an E1 interface. The O-CU-CP connects to the O-DU via an F1-c interface, and the O-CU-UP connects to the O-DU via an F1-u interface. The O-DU and O-RU are connected via the Open FH CUS-Plane, and the O-RU connects to the O-eNB via the Open FH M-Plane. The O-RU also connects to the O-Cloud via the Open FH M-Plane. The O-Cloud is connected to the SMO via an O2 interface. A legend indicates that black lines represent 3GPP interfaces (X2-c, X2-u, NG-u, Xn-c, Xn-u, NG-c) and green lines represent O-RAN interfaces (O1, O2, A1, E1, E2, F1-c, F1-u, Y1). - -**Figure 5-1: Logical Architecture of O-RAN system** - -Figure 5-1 illustrates the O-RAN architecture elements, interfaces, and overall system. - -As specified in [1], the following O-RAN architecture elements and interfaces shall be the DUT or SUT addressed in this security test specification. - -### **O-RAN architecture elements:** - -- Network functions and applications - - Service Management and Orchestration (SMO) - - Non-RT RIC and rApps - - Near-RT RIC and xApps - - O-CU-CP/UP - - O-DU - - O-RU - - O-eNB -- Cloud computing platform - - O-Cloud comprising a collection of physical infrastructure nodes that meet O-RAN requirements to host the relevant O-RAN functions (such as 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. - -# **Maintained interfaces by O-RAN:** - -- 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. -- O1 Interface connecting the SMO to the Near-RT RIC, one or more O-CU-CPs, one or more O-CU-UPs, and one or more O-DUs. -- O2 Interface between the SMO and the O-Cloud. -- E2 Interface connecting the Near-RT RIC and one or more O-CU-CPs, one or more O-CU-UPs, one or more O-DUs, and one or more O-eNBs. -- Open Fronthaul CUS-Plane Interface between O-RU and O-DU. -- Open Fronthaul M-Plane Interface between O-RU and O-DU as well as between O-RU and SMO. - -During the test execution, only one DUT or SUT shall be tested at the same time. The rest of elements involved in the test setup should be simulated or real, according to the test preconditions, but only the DUT or SUT shall be considered under evaluation. - -## 5.2 Test Setup - -Refer to the security test cases listed in the following clauses for their specific test setups. - -## 5.3 Test and measurement equipment and tools - -The following table lists test and measurement equipment required for the security tests in the present document. - -**Table 5-1: Test and measurement equipment list** - -| Test tool | Description | -|----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Commercial UE and/or UE emulator |

A commercial UE or UE emulator shall be used to establish stateful end-to-end connection and to generate or receive data traffic.

The commercial 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 measurements purposes. Such test and diagnostic functions should not affect the performance.

This commercial UE requires an (emulated) SIM card which is pre-provisioned with subscriber profiles. A UE emulator or multiple commercial UEs can be used in multi-UE test scenarios requiring multiple UEs sessions. The UE shall connect to the SUT either via RF cables or via an over the air (OTA) connection. In a lab environment, the UE shall be placed inside an RF shielded box/room to avoid interference from external signals.

A logging tool connected to the UE shall be used to capture measurements and KPI logs for test validation and reporting.

| -| 4G/5G Core or Core emulator |

A 4G/5G core or core emulator shall be used to terminate 4G/5G NAS sessions, and to support core network procedures required for RAN (SUT) testing. 4G/5G core or core emulator shall support end-to-end connection and data transfer between Application server and commercial UE/UE emulator.

| -| Application (traffic) server |

An application (traffic) server shall be used as an endpoint for generation and/or termination of data traffic streams to/from commercial UE(s)/UE emulator. The application server shall be capable of generating data traffic for the services under test.

| -| Network impairment emulator |

A network impairment emulator shall be used for tests which require insertion of impairment (packet delay and/or jitter) at the network interface (e.g. OpenFH).

| -| Packet generation tool / DoS emulator |

A packet generation tool / Denial of Service (DoS) emulator shall be used for DoS traffic generation of security tests. The tool shall support crafting network traffic over the following network protocols: Ethernet, IP, UDP, TCP, PTP, eCPRI, TLS, HTTP/HTTPS.

| -| High-volume packet generation/DDoS simulation tool |

A high-volume packet generation / Distributed Denial of Service (DDoS) simulation tool shall be used for high-volume DDoS traffic generation from multiple sources. The tool shall support crafting high-volume network traffic over the following network protocols: Ethernet, IP, UDP, TCP, PTP, eCPRI, TLS, HTTP/HTTPS.

| -| Packet capture tool |

A packet capture tool shall be used to capture samples of data traffic for validation, analysis, and troubleshooting. It may be used to capture samples of legitimate traffic, which then may be used as templates for fuzzing attacks. The tool shall support capturing network traffic over the following network protocols: Ethernet, IP, UDP, TCP, PTP, eCPRI, TLS, QUIC, HTTP/HTTPS.

| -| Network tap |

A network tap shall be a hardware or software device which provides access and visibility to the data flowing across a computer network.

| -| Port scanner |

A protocol scanner shall be used for probing network protocols and services. It shall be able to detect open ports. It shall be able to detect what service is exposed as active on the open port.

Port scanners commonly come with built-in database of services. Service detection can use numerous built-in probes for querying various services. In practice, port scanners are often used for service detection.

| -| Fuzzing tool |

A protocol fuzzing tool shall be used for unexpected protocol input generation of security tests. The tool shall support mutating and replaying of captured network traffic over the following network protocols: Ethernet, IP, UDP, TCP, PTP, eCPRI, TLS, HTTP/HTTPS.

| -| Vulnerability scanning tool |

A vulnerability scanning tool shall be used for blind exploitation of well-known vulnerabilities during security tests. The tool may 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. | -| NFV benchmarking and resource exhaustion tool | A Network Function Virtualization (NFV) tool shall be used for O-Cloud system performance measurement and resource exhaustion type of DoS attack generation. This tool shall be capable of supporting any types of O-Cloud environment (public or private) with testing VNF(s) and/or CNF(s). | -| SSH audit tool | An SSH audit tool shall be used to verify the following properties: version of protocol, cipher suites, and known vulnerabilities in server and client SSH software. | -| TLS scanning tool | A TLS scanning tool shall be used to verify the following properties: version of protocol, cipher suites, and known vulnerabilities in server TLS software. | -| DTLS scanning tool | A DTLS scanning tool shall be used to verify the following properties: version of protocol, cipher suites, and known vulnerabilities in server DTLS software. | -| IKE scanning tool | An IKE scanning tool shall be used to verify the following properties: version of protocol, cipher suites, and known vulnerabilities in server IPsec software. | -| Software image signing tool | A Software image signing tool shall be used to digitally sign and verify the software image, e.g. xApps or O-RAN architecture element delivered by a software producer/provider. | - -## 5.4 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 comparison. A template for a complete test report is found in Annex B and may be used. Photos and screenshots should also be taken as part of the test report to illustrate the test environment. Additional parameters are specified in the description of each test in the subsequent clauses. - -## 5.5 Assumptions - -All threat IDs in the present document are referenced from O-RAN Security Threat Modeling and Risk Assessment [i.5]. - -## 5.6 Testing tools - -The tools outlined in this clause represent a selection of commonly used resources for testing processes. It is important to emphasize that this list is not exhaustive. Testers are encouraged to use additional tools as needed for comprehensive and effective testing, ensuring they meet the standards and requirements set forth in this test plan. - -- 1) Packet capture and traffic analysis tools: - - Wireshark: Wireshark is a widely used open-source network protocol analyser that can capture and analyse network traffic. It allows for the inspection of packets to identify issues related to confidentiality, integrity, and replay. Additionally, it can be used to verify authentication mechanisms and analyse access control measures. - - tcpdump: tcpdump is a command-line packet analyser available on various operating systems. It captures network traffic and can save it to a file for later analysis. tcpdump offers powerful filtering capabilities to capture specific traffic based on criteria such as source/destination IP addresses, protocols, or ports. - - Netscout Sniffer: Netscout Sniffer is a commercial network analysis tool that offers real-time packet capture and analysis capabilities. It provides comprehensive visibility into network traffic and offers advanced features for troubleshooting and performance analysis. - - Colasoft Capsa: Colasoft Capsa is a network analyser designed for network monitoring and troubleshooting. It captures and analyses network traffic, providing insights into protocols, applications, and potential security issues. Capsa offers both real-time and post-capture analysis. - -- Tcpreplay: Tcpreplay is an open-source tool used for replaying captured network traffic. It enables the replay of network packets from a previously captured pcap file, simulating real-world traffic scenarios. Although its primary purpose is not security testing, tcpreplay can be utilized as a tool in security testing efforts, particularly for testing the replay and handling of network packets. -- 2) Traffic Generation Tools: -- Scapy: Scapy is a powerful Python-based tool that can create, manipulate, and send custom network packets. It allows to generate and replay packets on an interface to test for replay vulnerabilities. - - Hping: Hping is a command-line tool that can send custom packets and perform various network-related activities. It can be used to generate replayed packets on an interface for testing purposes. -- 3) Scripting and Automation Tools to develop custom test scripts: -- Python: Python scripting language provides libraries (e.g., socket, scapy) that enables the creation of custom scripts to generate and replay packets on an interface. - - Bash scripting: Bash scripting can be utilized to automate the process of capturing packets and replaying them on an interface. -- 4) Network Emulation Tools: -- GNS3: GNS3 is a network emulation tool that enables the simulation of complex network topologies. It can be used to create a virtual environment with RAN E1 interfaces, generate traffic, and simulate replay attacks for testing purposes. -- 5) Network performance tools: -- iperf3: iPerf3 is an open-source tool for network performance testing and measurement. While it is primarily focused on network performance evaluation, it can also be utilized as a tool to indirectly assess certain aspects of security, such as bandwidth availability and network congestion. -- 6) Traffic Manipulation Tools: -- Burp Suite: Burp Suite is a web application security testing tool that can intercept, modify, and replay network traffic. While it is primarily designed for web applications, it allows to test the integrity, confidentiality, and authenticity of data transmitted over an interface. -- 7) Vulnerability assessment tools -- Nessus: Nessus is a popular vulnerability assessment tool that can scan an interface for known security vulnerabilities and misconfigurations. It can help identify potential weaknesses related to confidentiality, integrity, replay attacks, and access control. - - OpenVAS: OpenVAS (Open Vulnerability Assessment System) is an open-source vulnerability scanner that can perform security audits on security protocols implementations. It can detect vulnerabilities, misconfigurations, and compliance issues, helping ensure that an interface adheres to security best practices and standards. -- 8) Security Information and Event Management (SIEM) Tools: -- SIEM tools like Splunk or ELK (Elasticsearch, Logstash, Kibana) can help collect and analyse security events and logs related to the O-RAN architecture elements and interfaces. They can assist in identifying potential security incidents, monitoring access control, and detecting anomalies. -- 9) IPsec tool -- OpenSwan is an open-source implementation of the IPsec (Internet Protocol Security) protocols suite. It provides tools and libraries for setting up and managing IPsec connections, which can be used to test the confidentiality, integrity, replay, authenticity, and access control of an interface. Here's how OpenSwan can be used for testing: - -- Confidentiality and Integrity: - - OpenSwan allows to configure IPsec tunnels with encryption algorithms (e.g., AES) and integrity algorithms (e.g., HMAC-SHA256). By setting up IPsec connections using OpenSwan, it is possible to verify the confidentiality and integrity of data transmitted over an interface. - - Replay Attack: - - OpenSwan supports replay protection mechanisms, which protect against replay attacks by assigning sequence numbers to IPsec packets. These mechanisms can be tested to ensure that replayed packets are detected and rejected. - - Authenticity: - - OpenSwan supports authentication mechanisms such as pre-shared keys or digital certificates, which ensure the authenticity of IPsec connections. Testing can be performed to verify the proper authentication of an interface. - - Access Control: - - OpenSwan allows to configure IPsec security policies, including source/destination IP address filtering, protocol filtering, and port filtering. These policies can be tested to ensure that only authorized traffic is allowed through an interface. - - StrongSwan: An open-source IPsec-based VPN solution that includes testing capabilities. It enables the configuration and simulation of IPsec connections, testing of authentication methods, and performance of security checks. -- 10) Cryptographic operations testing tools -- Hashing Tools: Hashing tools such as sha256sum, can be used to calculate hash values of transmitted data. By comparing the computed hash values at the source and destination, the integrity of the data can be verified. - -Cryptographic Libraries: Cryptographic libraries, such as Bouncy Castle, provide APIs and tools for implementing and testing integrity protection mechanisms. These libraries offer functions to generate integrity checks (e.g., MAC) and validate the integrity of received data. - -## 6 Security Protocol & APIs Validation - -### 6.1 Overview - -This clause contains test cases to validate implementation of security protocols against O-RAN security requirements in [2] and [5]. - -### 6.2 SSH Server & Client - -**Requirement Name:** Network Security Protocol - SSH - -**Requirement Reference:** Clause 4.1, O-RAN Security Protocols Specifications [2] - -**Requirement Description:** Robust protocol implementation with adequately strong cipher suites is being required for SSH - -**Threat References:** T-O-RAN-05 - -**DUT/s:** SMO, O-DU, O-RU - -**Test Name:** TC\_SSH\_Server\_and\_Client\_Protocol - -**Purpose:** To verify implementation of the secure communication protocol SSH as specified in [2]. - -#### Procedure and execution steps - -##### Preconditions - -- Tool: SSH audit tool with capabilities as defined in clause 5.3 -- Testing of server configuration (DUT in the role of server): Network access to SSH server -- Testing of client configuration (DUT in the role of client): Access to configuration of SSH client - -##### Execution steps - -Testing of server configuration (DUT in the role of server): - -- Run SSH audit tool in server audit mode against target SSH server. -- Compare the tool's output with the list of approved SSH protocol versions and algorithms (for key agreement, symmetric encryption, key exchange, and MACs) as defined by clause 4.1, O-RAN Security Protocols Specifications [2]. - -Testing of client configuration (DUT in the role of client): - -- Run SSH audit tool on target SSH client in client audit mode. -- Compare the tool's output with the list of approved SSH protocol versions and algorithms (for key agreement, symmetric encryption, key exchange, and MACs) as defined by clause 4.1, O-RAN Security Protocols Specifications [2]. - -##### Expected results - -- All detected SSH protocol versions are allowed by [2], clause 4.1. -- All detected SSH algorithms (for key agreement, symmetric encryption, key exchange, and MACs) are allowed by [2], clause 4.1. - -**Expected format of evidence:** Report files produced by SSH audit tool and/or screenshots - -## 6.3 TLS - -### 6.3.1 TLS Support - -**Requirement Name:** Network Security Protocol - TLS - -**Requirement Reference:** Clause 4.2, O-RAN Security Protocols Specifications [2] - -**Requirement Description:** Support TLS/mTLS with protocol profiles - -**Threat References:** T-O-RAN-05 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_TLS\_Protocol - -**Purpose:** To verify implementation of the secure communication protocol TLS as specified in [2], clause 4.2. - -#### Procedure and execution steps - -##### Preconditions - -- Tool: TLS scanning tool with capabilities as defined in clause 5.3 with certificate(s) installed -- DUT equipped with CA certificate that is a trust anchor for the certificate(s) -- Network access to DUT with TLS or mTLS enabled - -##### Execution steps - -For TLS verification, when DUT is either TLS client or server, step 1 is executed. - -For mTLS verification, when DUT is either TLS client or server, steps 1 and 2 are executed. - -- 1) Protocol scanning - - Run TLS scanning tool against DUT for detection of: - - TLS version - - Cipher suites - - Elliptic curves - - Certificate type - - Diffie-Hellman groups - - Compression methods - - Compare the test result/report with the list of approved TLS versions and profiles as defined by O-RAN Security Protocols Specifications [2], clause 4.2. -- 2) For Mutual Authentication, also execute the following steps: - - Run TLS scanning tool with mTLS 1.2 and valid certificate against DUT with mutual authentication enabled to verify the establishment of the TLS session after successful authentication. - - Run TLS scanning tool with mTLS 1.2 and invalid certificate (including but not limited to expired certificate, missing field certificate, untrusted CA signed certificate, ...) against DUT with mutual authentication enabled to verify the failed attempt of the TLS session establishment due to certificate validation. - - Run TLS scanning tool with mTLS 1.3 and valid certificate against DUT with mutual authentication enabled to verify the establishment of the TLS session after successful authentication. - -- Run TLS scanning tool with mTLS 1.3 and invalid certificate (including but not limited to expired certificate, missing field certificate, untrusted CA signed certificate, ...) against DUT with mutual authentication enabled to verify the failed attempt of the TLS session establishment due to certificate validation. - -#### Expected results - -- All supported TLS protocol versions are explicitly allowed by [2], clause 4.2. -- All detected TLS cipher suites, elliptic curves, Diffie-Hellman groups and compression methods are explicitly allowed by [2], clause 4.2. -- Mutual authentication support works with certificates. - -**Expected format of evidence:** Report files produced by TLS scanning tool and/or screenshots - -### 6.3.2 TLS Version Negotiation - -**Requirement Name:** Network Security Protocol – TLS Version Negotiation - -**Requirement Reference:** Clause 4.2, O-RAN Security Protocols Specifications [2] - -**Requirement Description:** Negotiate TLS versions 1.2 and 1.3 - -**Threat References:** T-O-RAN-05 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_TLS\_Version - -**Purpose:** To verify implementation of the secure communication protocol TLS as specified in [2], clause 4.2, is able to successfully negotiate the TLS version. - -#### Procedure and execution steps - -##### Preconditions - -- Tool: TLS scanning tool with capabilities as defined in clause 5.3 with certificate(s) installed -- DUT equipped with CA certificate that is a trust anchor for the certificate(s) -- Network access to DUT with TLS or mTLS enabled - -##### Execution steps - -- Configure TLS scanning tool for only TLS 1.2 -- Run TLS scanning tool with TLS/mTLS 1.2 and valid certificate against DUT to verify the establishment of the TLS session after successful authentication -- Configure TLS scanning tool for only TLS 1.3 -- Run TLS scanning tool with TLS/mTLS 1.3 and valid certificate against DUT to verify the establishment of the TLS session after successful authentication -- Configure TLS scanning tool to support TLS 1.2 and TLS 1.3 - -**NOTE:** The "supported\_versions" extension is used by the client to indicate which versions of TLS it supports and by the server to indicate which version it is using. The extension contains a list of supported versions in preference order, with the most preferred version first, as specified in section 4.2.1 from RFC 8446 [18]. - -- Run the TLS scanning tool with TLS/mTLS 1.2 and TLS/mTLS 1.3 and valid certificate against DUT to verify establishment of TLS session after successful authentication - -### Expected results - -- DUT is able to successfully negotiate TLS/mTLS 1.2. -- DUT is able to successfully negotiate TLS/mTLS 1.3. - -**Expected format of evidence:** Report files produced by TLS scanning tool and/or screenshots. - -## 6.3.3 TLS Deprecated Versions - -**Requirement Name:** Network Security Protocol – Deprecated TLS Versions - -**Requirement Reference:** Clause 4.2, O-RAN Security Protocols Specifications [2] - -**Requirement Description:** Reject TLS versions 1.0 and 1.1. - -**Threat References:** T-O-RAN-05 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_TLS\_DeprecatedVersions - -**Purpose:** To verify implementation of the secure communication protocol TLS as specified in [2], clause 4.2, does not establish a TLS session with TLS 1.0 or 1.1, or SSL 2.0 or 3.0. - -### Procedure and execution steps - -#### Preconditions - -- Tool: TLS scanning tool with capabilities as defined in clause 5.3 with certificate(s) installed -- DUT equipped with CA certificate that is a trust anchor for the certificate(s) -- Network access to DUT with TLS or mTLS enabled - -#### Execution steps - -- Configure TLS scanning tool to support only TLS 1.0 -- Run the TLS scanning with TLS 1.0 and valid certificate against the DUT -- Configure TLS scanning tool to support only TLS 1.1 -- Run the TLS scanning with TLS 1.1 and valid certificate against the DUT -- Configure TLS scanning tool to support only SSL 2.0 -- Run the TLS scanning with SSL 2.0 and valid certificate against the DUT -- Configure TLS scanning tool to support only SSL 3.0 -- Run the TLS scanning with SSL 3.0 and valid certificate against the DUT - -### Expected results - -- DUT rejects connection for TLS 1.0 -- DUT rejects connection for TLS 1.1 -- DUT rejects connection for SSL 2.0 -- DUT rejects connection for SSL 3.0 - -**Expected format of evidence:** Report files produced by TLS scanning tool and/or screenshots - -## 6.4 DTLS - -**Requirement Name:** Network Security Protocol - DTLS - -**Requirement Reference:** Clause 4.4, O-RAN Security Protocols Specifications [2] - -**Requirement Description:** Support DTLS - -**Threat References:** T-O-RAN-01 - -**DUT/s:** Near-RT RIC, O-CU-CP, O-CU-UP, O-DU - -**Test Name:** TC\_DTLS\_Protocol - -**Purpose:** To verify implementation of the secure communication protocol DTLS as specified in [2], clause 4.4. - -### Procedure and execution steps - -#### Preconditions - -- Tool: DTLS scanning tool with capabilities as defined in clause 5.3 -- Network access to DUT - -#### Execution steps - -- Run DTLS scanning tool against DUT for detection of: - - DTLS version - - Cipher suites - - Elliptic curves - - Certificate type - - Diffie-Hellman groups - - Compression methods -- Compare the test result/report with the list of approved DTLS versions and profiles as defined by Security Protocols Specification [2], clause 4.4. - -#### Expected results - -- All supported DTLS protocol versions are explicitly allowed by [2], clause 4.4. -- All detected DTLS cipher suites, elliptic curves, Diffie-Hellman groups and compression methods are explicitly allowed by [2], clause 4.4. - -**Expected format of evidence:** Report files produced by DTLS scanning tool and/or screenshots. - -## 6.5 IPsec - -### 6.5.1 IPsec security - -**Requirement Name:** Network Security Protocol - IPsec - -**Requirement Reference:** Clause 4.5, O-RAN Security Protocols Specifications [2] - -**Requirement Description:** Support IPsec tunnel mode with confidentiality, integrity, authentication, and replay protection. - -**Threat References:** T-O-RAN-05 - -**DUT/s:** Near-RT RIC, O-CU-CP, O-CU-UP, O-DU - -**Test Name:** TC\_IPsec\_Security - -**Purpose:** To verify implementation of the secure communication protocol IPsec. - -#### Procedure and execution steps - -##### Preconditions - -- Tool: IKE scanning tool with capabilities as defined in clause 5.3 -- Network access to DUT - -##### Execution steps - -- Run IKE scanning tool against DUT for detection of: - - ESP Encryption Transforms - - ESP Authentication Transforms - - Diffie-Hellman groups - - Certificate type - - Pseudo-random function -- Compare the test result/report with the list of approved IPsec IKE versions, ESP Encryption Transforms, ESP Authentication Transforms, Diffie-Hellman groups and Pseudo-random function as defined by O-RAN Security Protocols Specification [2], clause 4.5. - -##### Expected results - -- All detected IPsec IKE versions are allowed by [2], clause 4.5. -- All detected ESP Encryption Transforms, ESP Authentication Transforms, Diffie-Hellman groups and Pseudo-random function are allowed by [2], clause 4.5. IKE version (v2) support with no older version(s) enabled. -- If certificates are used, their format is X.509v3. - -##### Expected format of evidence: - -- .pcap files capturing the IKE negotiations between the tool and the DUT. -- Report or output from the IKE scanning tool, specifically highlighting: - - Detected ESP Encryption Transforms. - - Detected ESP Authentication Transforms. - - Detected Diffie-Hellman groups. - - Detected Certificate type. - - Detected Pseudo-random function. -- Screenshots from the IKE scanning tool showing scan results, especially the supported IKE version detected. -- If certificates are used, a sample or screenshot verifying the X.509v3 format. - -## 6.5.2 IKE Header Flags Fuzzing - -**Requirement Name:** Network Security Protocol - IPsec - -**Requirement Reference:** Clause 4.5, O-RAN Security Protocols Specifications [2] - -**Requirement Description:** Support IPsec tunnel mode with confidentiality, integrity, authentication, and replay protection. - -**Threat References:** T-O-RAN-01 - -**DUT/s:** Near-RT RIC, O-CU-CP, O-CU-UP, O-DU - -**Test Name:** TC\_IKE\_HEADER\_FLAGS FUZZING - -**Purpose:** The purpose of this test is to verify the robustness of the IKEv2 server when faced with malformed IKE headers. Flags within the IKE header are intended to provide specific instructions or information about the message. By fuzzing these flags, we can identify potential vulnerabilities or flaws in the server's processing logic. - -#### Procedure and execution steps - -##### Preconditions - -- A controlled environment with an IKEv2 server and a test client. -- Packet capture tool (e.g., Wireshark) for monitoring the traffic. -- Fuzzing tool or script to generate malformed IKE header flags. - -##### Execution steps - -- 1) Begin by starting the packet capture tool to record the test session. -- 2) Use the fuzzing tool or script to generate IKEv2 messages with the following malformed flags in the IKE header: - - Initiator flag: Flip this flag to see if the server can identify a message that isn't from an initiator. - - Version flag: Introduce an unsupported version. - - Response flag: Send messages that have this flag inappropriately set. - - Combination of multiple flags: Mix flags to generate completely unexpected combinations. -- 3) Send each of these malformed messages to the IKEv2 server individually, waiting for a response before sending the next. -- 4) Observe server reactions, looking specifically for any unhandled exceptions, crashes, or irregular behaviours. - -##### Expected Results - -- The IKEv2 server handles the malformed flags gracefully, either by rejecting the message or by ignoring the unexpected flag values. -- There are no crashes, hangs, or undefined behaviours. - -##### Expected format of evidence - -- Packet capture files (.pcap) showing the malformed flags sent and the server's responses. -- Server logs indicating the handling (or rejection) of the malformed messages. - -## 6.5.3 IKE Key Exchange Payload Fuzzing - -**Requirement Name:** Network Security Protocol - IPsec - -**Requirement Reference:** Clause 4.5, O-RAN Security Protocols Specifications [2] - -**Requirement Description:** Support IPsec tunnel mode with confidentiality, integrity, authentication, and replay protection. - -**Threat References:** T-O-RAN-01 - -**DUT/s:** Near-RT RIC, O-CU-CP, O-CU-UP, O-DU - -**Test Name:** TC\_IKE\_KEY\_EXCHANGE\_PAYLOAD\_FUZZING - -**Purpose:** The purpose of this test is to examine the IKEv2 server's ability to manage corrupted or unexpected data within the Key Exchange (KE) payload. The KE payload carries the Diffie-Hellman public value. If the server is unable to handle malformed KE payloads, it might be susceptible to attacks or crashes. - -### Procedure and execution steps - -#### Preconditions - -- A controlled environment with an IKEv2 server and a test client. -- Packet capture tool (e.g., Wireshark) for monitoring the traffic. -- Fuzzing tool or script capable of generating malformed KE payloads. - -#### Execution steps - -- 1) Initiate the packet capture tool to ensure every detail of the test session is recorded. -- 2) Use your fuzzing tool or script to generate IKEv2 messages with the following specific manipulations in the KE payloads: - - Unexpected length: Prepare 10 distinct messages where the KE payload's declared length is longer or shorter than the actual payload. - - Corrupted data: Generate 10 messages introducing random bytes into the KE payload to see how the server handles non-standard values. - - Unsupported Diffie-Hellman groups: Create 5 messages attempting to initiate a key exchange using a DH group that is either deprecated or not supported by the server. - - Empty KE payload: Formulate 5 messages with an empty KE payload. -- 3) Sequentially send these 30 malformed messages to the IKEv2 server. After sending each message, wait for the server's response to avoid overloading it. Ensure the following sequence: - - Send the 10 "Unexpected Length" messages. - - Follow with the 10 "Corrupted Data" messages. - - Continue with the 5 "Unsupported Diffie-Hellman Groups" messages. - - Conclude with the 5 "Empty KE Payload" messages. - -**NOTE:** Monitor the server's reactions closely. The server ideally handles errors gracefully, either ignoring them or responding with an appropriate error message, without any crashes or hangs. - -### Expected Results - -- The IKEv2 server gracefully handles the malformed KE payloads, either by ignoring them, responding with an error, or requesting a valid KE payload. -- No crashes, hangs, or undefined behaviours occur. - -### Expected format of evidence - -- Packet capture files (.pcap) highlighting the malformed KE payloads and the server's corresponding responses. -- Server logs detailing the handling (or rejection) of the malformed KE payloads. - -## 6.5.4 IKE Malformed Certificate Payload - -**Requirement Name:** Network Security Protocol - IPsec - -**Requirement Reference:** Clause 4.5, O-RAN Security Protocols Specifications [2] - -**Requirement Description:** Support IPsec tunnel mode with confidentiality, integrity, authentication, and replay protection. - -**Threat References:** T-O-RAN-01 - -**DUT/s:** Near-RT RIC, O-CU-CP, O-CU-UP, O-DU - -**Test Name:** TC\_IKE\_MALFORMED\_CERTIFICATE\_PAYLOAD - -**Purpose:** This test aims to verify the IKEv2 server's capability to properly validate certificate payloads. Certificate payloads are essential in the IKEv2 authentication phase. A server vulnerable to malformed certificate payloads could be susceptible to impersonation or man-in-the-middle attacks. - -### Procedure and execution steps - -#### Preconditions - -- A controlled environment with an IKEv2 server and a test client. -- Packet capture tool (e.g., Wireshark) to monitor and capture traffic. -- A set of both valid and deliberately malformed certificates. - -#### Execution steps - -- 1) Valid Certificate Test: - - Initiate an IKEv2 session using a valid certificate to ensure baseline functionality. - - Confirm successful authentication and session establishment. -- 2) Expired Certificate: - - Use a previously valid certificate that has now expired. - - Attempt to initiate an IKEv2 session. - - Observe the server's rejection of this certificate. -- 3) Certificate with Invalid Signature: - - Modify a valid certificate's content slightly (e.g., change an attribute) without re-signing it. This will invalidate its signature. - - Attempt to initiate an IKEv2 session using this certificate. - - The server detects the invalid signature and rejects the connection. -- 4) Certificate from Untrusted Authority: - - Generate a new certificate signed by a Certificate Authority (CA) that the IKEv2 server doesn't trust or recognize. - - Attempt to initiate a connection using this certificate. - - Observe the server rejecting the certificate due to the untrusted CA. -- 5) Certificate with Modified Subject/Issuer Fields: - -- Modify the subject or issuer fields of a certificate to contain irregular or unexpected values (e.g., overly long strings, special characters). - - Use this certificate to initiate an IKEv2 session. - - The server validates these fields, notices the irregularities, and potentially rejects the connection. -- 6) Certificate with Invalid Key Usage: -- Use a certificate that doesn't have "key encipherment" or "digital signature" as its key usage, which are typically needed for IKEv2 operations. - - Attempt to initiate a session. - - The server detects the inappropriate key usage and declines the connection. - -**Expected Results:** - -- For the valid certificate, the IKEv2 server authenticates successfully and establish a session. -- For all other scenarios, the IKEv2 server detects the certificate anomalies and rejects the connection attempts. Specific error messages or logs relating to certificate validation failure are generated. - -**Expected format of evidence:** - -- Packet capture files (.pcap) capturing the entire exchange, showing the certificate exchange and the server's response. -- Server logs detailing the acceptance or rejection of each certificate, with corresponding reasons or error messages for rejections. - -## 6.6 OAuth 2.0 - -### 6.6.1 API Consumer - -**Requirement Name:** Authorization based on OAuth 2.0 - -**Requirement Reference:** Clause 4.7, O-RAN Security Protocols Specifications [2] - -**Requirement Description:** O-RAN OAuth 2.0 based authorization including resource registration, access token request and service access request based on token verification process as defined in [2] - -**Threat References:** T-O-RAN-05 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-Cloud - -**Test Name:** TC\_OAuth2.0\_API\_Consumer - -**Purpose:** To verify implementation of the authorization for API consumer based on OAuth 2.0 as specified in [2] - -**Procedure and execution steps****Preconditions** - -- DUT is acting as a OAuth2.0 API Consumer -- For Test case A: - - Certificates for OAuth2.0 authentication - - mTLS connection configured for all the components involved in the test case. - -- DUT establishes a mTLS connection with Authorization Server and another mTLS connection with Resource Server. -- For Test case B: - - Client ID and client secret for OAuth2.0 authentication - - TLS connection configured for all the components involved in the test case. - - DUT establishes a TLS connection with Authorization Server and another TLS connection with Resource Server. -- Resource Server, may be real or simulated -- Authorization server – OAuth 2.0 Authorization Server (real or simulated) -- Resource server registered with the Authorization server for its supported API service(s) - - This process can be a manual or automatic process preceding with Resource server authentication -- API consumer with the role to have access to the resource to be requested -- Network access to Authorization Server, Resource Server and API consumer - -**Execution steps** - -**Test case A :** - -- 1) DUT requests an access token to the Authorization Server. -- 2) With access token, the DUT sends an API service request towards Resource Server (API producer) using the access token obtained as a response to access token request - -![Sequence diagram for Test case A showing mTLS handshakes and token/resource requests between DUT, Resource Server, and Authorization Server.](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg) - -``` - -sequenceDiagram - participant DUT as OAuth2.0 API Consumer (DUT) - participant RS as OAuth2.0 Resource Server - participant AS as OAuth2.0 Authorization Server - - DUT->>AS: mTLS Handshake - AS-->>DUT: - Note right of AS: Verify Consumer TLS certificate; grant access - DUT->>AS: Request Access Token - Note right of AS: Generate access token - AS-->>DUT: Response (access_token) - DUT->>RS: mTLS Handshake - RS-->>DUT: - DUT->>RS: Request resource - RS-->>DUT: Return resource - -``` - -Sequence diagram for Test case A showing mTLS handshakes and token/resource requests between DUT, Resource Server, and Authorization Server. - -**Figure 6-1: Token request using mTLS and Service request** - -**Test case B:** - -- 1) DUT requests a token to the Authorization Server using client ID and the secret as authentication. -- 2) With access token, the DUT sends an API service request towards Resource Server (API producer) using the access token obtained as a response to access token request - -![Sequence diagram for OAuth 2.0 token request and service request. The diagram shows three lifelines: OAuth2.0 API Consumer (DUT), OAuth2.0 Resource Server, and OAuth2.0 Authorization Server. The DUT initiates a TLS Handshake with the Authorization Server, followed by a Request Access Token (client-secret). The Authorization Server generates an access token and returns it to the DUT. The DUT then initiates a TLS Handshake with the Resource Server, followed by a Request resource (access_token). The Resource Server returns the resource to the DUT.](318886a86a1dcc59e1fc83db6f157c60_img.jpg) - -``` - -sequenceDiagram - participant DUT as OAuth2.0 API Consumer (DUT) - participant RS as OAuth2.0 Resource Server - participant AS as OAuth2.0 Authorization Server - Note right of AS: Generate access token - DUT->>AS: TLS Handshake - AS-->>DUT: TLS Handshake - DUT->>AS: Request Access Token (client-secret) - AS-->>DUT: Response (access_token) - DUT->>RS: TLS Handshake - RS-->>DUT: TLS Handshake - DUT->>RS: Request resource (access_token) - RS-->>DUT: Return resource - -``` - -Sequence diagram for OAuth 2.0 token request and service request. The diagram shows three lifelines: OAuth2.0 API Consumer (DUT), OAuth2.0 Resource Server, and OAuth2.0 Authorization Server. The DUT initiates a TLS Handshake with the Authorization Server, followed by a Request Access Token (client-secret). The Authorization Server generates an access token and returns it to the DUT. The DUT then initiates a TLS Handshake with the Resource Server, followed by a Request resource (access\_token). The Resource Server returns the resource to the DUT. - -**Figure 6-2: Token request with secret ID and Service request** - -#### Expected results - -##### For Test case A: - -The DUT establishes the mTLS connection with the Authorization Server and the Resource Server. The DUT obtains access to the requested resource onto the Resource Server. - -##### For Test case B: - -The DUT establishes the TLS connection with the Authorization Server and the Resource Server. The DUT obtains the access to the requested resource onto the Resource Server. - -**Expected format of evidence:** Log files, traffic captures and/or screenshots. - -## 6.6.2 Resource Server - -**Requirement Name:** Authorization based on OAuth 2.0 - -**Requirement Reference:** Clause 4.7, O-RAN Security Protocols Specifications [2] - -**Requirement Description:** O-RAN OAuth 2.0 based authorization including resource registration, access token request and service access request based on token verification process as defined in [2] - -**Threat References:** T-O-RAN-05 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-Cloud - -**Test Name:** TC\_OAuth2.0\_Resource\_Server - -**Purpose:** To verify implementation of the authorization for Resource Server based on OAuth 2.0 as specified in [2] - -#### Procedure and execution steps - -#### Preconditions - -- DUT is acting as a OAuth 2.0 Resource Server -- For Test case A: - -- Certificates for OAuth 2.0 authentication. -- mTLS connection configured for all the components involved in the test case. -- DUT establishes a mTLS connection with Authorization Server and another mTLS connection with the API consumer. -- For Test case B: - - Share client ID and client secrets for OAuth 2.0 authentication - - TLS connection configured for all the components involved in the test case. - - DUT establishes a TLS connection with Authorization Server and another TLS connection with the API Consumer. -- API Consumer may be real or simulated -- Authorization Server – OAuth 2.0 Authorization Server (real or emulated) -- Resource Server registered with the Authorization Server for its supported API service(s) - - This process can be a manual or automatic process preceding with Resource Server authentication -- API Consumer with the role to have access to the resource to be requested -- Network access to Authorization Server, Resource Server and API Consumer - -**Execution steps** - -**Test case A:** - -- 1) API consumer requests a token from the Authorization server. -- 2) With the access token, the API consumer sends an API service request towards Resource Server (API producer) using the access token obtained in the previous step. - -![Sequence diagram for Test case A showing interactions between OAuth2.0 API Consumer, OAuth2.0 Resource Server (DUT), and OAuth2.0 Authorization Server.](a1890b9a9b85f13e67ed59bbad623659_img.jpg) - -``` - -sequenceDiagram - participant C as OAuth2.0 API Consumer - participant R as OAuth2.0 Resource Server (DUT) - participant A as OAuth2.0 Authorization Server - - C<-->>A: mTLS Handshake - C->>A: Request Access Token - Note over A: Verify Consumer TLS -certificate; grant access - Note over A: Generate access token - A-->>C: Response (access_token) - C<-->>R: mTLS Handshake - C->>R: Request resource (access_token) - R<-->>A: mTLS Handshake - R->>A: Verify used access_token - Note over A: Check access token - A-->>R: - R-->>C: Return resource - -``` - -The sequence diagram illustrates the interaction for Test case A. It begins with an mTLS Handshake between the OAuth2.0 API Consumer and the OAuth2.0 Authorization Server. The Consumer then sends a 'Request Access Token'. The Authorization Server performs internal steps to 'Verify Consumer TLS certificate; grant access' and 'Generate access token', then returns a 'Response (access\_token)'. Next, after an mTLS Handshake between the Consumer and the Resource Server (DUT), the Consumer sends a 'Request resource (access\_token)'. The DUT then performs an mTLS Handshake with the Authorization Server and sends a 'Verify used access\_token' request. The Authorization Server performs a 'Check access token' and responds. Finally, the DUT sends a 'Return resource' back to the API Consumer. - -Sequence diagram for Test case A showing interactions between OAuth2.0 API Consumer, OAuth2.0 Resource Server (DUT), and OAuth2.0 Authorization Server. - -**Figure 6-3: Token request using mTLS and Service Request** - -**Test case B:** - -- 1) DUT requests a token from the Authorization Server using the client ID and secret as authentication. -- 2) With access token, the API Consumer sends an API service request to the DUT (Resource Server) using the access token obtained in the previous step. -- 3) The DUT verifies the access token is valid with the Authorization Server. -- 4) The DUT returns the service requested to the API Consumer. - -![Sequence diagram for Figure 6-4 showing interactions between OAuth2.0 API Consumer, OAuth2.0 Resource Server (DUT), and OAuth2.0 Authorization Server.](0ee9d674085524d589646a6c3fb21ec3_img.jpg) - -``` - -sequenceDiagram - participant API Consumer as OAuth2.0 API Consumer - participant DUT as OAuth2.0 Resource Server (DUT) - participant AS as OAuth2.0 Authorization Server - - Note right of AS: Verify Consumer TLS certificate; grant access - API Consumer->>AS: Request Access Token (client-secret) - Note right of AS: Generate access token - AS-->>API Consumer: Response (access_token) - Note right of AS: Check access token - API Consumer->>DUT: Request resource (access_token) - DUT->>AS: Verify used access_token - AS-->>DUT: - DUT-->>API Consumer: Return resource - -``` - -Sequence diagram for Figure 6-4 showing interactions between OAuth2.0 API Consumer, OAuth2.0 Resource Server (DUT), and OAuth2.0 Authorization Server. - -**Figure 6-4: Token request with secret ID and Service request** - -**Expected results** - -**For Test case A:** The DUT establishes the mTLS connection with the Authorization Server and with the API Consumer. The DUT sends the requested service to the API Consumer. - -**For Test case B:** The DUT establishes the TLS connection with the Authorization Server and with the API Consumer. The DUT sends the requested resource to the API Consumer. - -**Expected format of evidence:** Log files, traffic captures and/or screenshots. - -## 6.7 NACM - -### 6.7.1 NACM Configuration - -**Requirement Name:** NACM security - -**Requirement Reference:** REQ-NAC-FUN-1 to REQ-NAC-FUN-10, clause 5.2.2.3, REQ-NAC-MPLANE-FUN-1 to REQ-NAC-MPLANE-FUN-6, clause 5.2.5.4.3 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** NETCONF/NACM support - -**Threat References:** T-O-RAN-03, T-O-RAN-05, T-O-RAN-06 - -**DUT/s:** Near-RT RIC, O-CU-CP, O-CU-UP, O-DU, O-RU - -**Test Name:** TC\_NACM\_CONFIGURATION - -**Purpose:** The purpose of this test is to verify the NACM configuration for secure access control. - -#### Procedure and execution steps - -##### Preconditions - -- The NACM and NETCONF services are properly configured and NACM configuration parameters are set to default value. -- NACM access control configurations are properly defined. - -##### Execution steps - -Verify NACM configuration definitions. - -1. Check that NACM configurations are properly defined for access control as per clause 5.2.2.3 defined in O-RAN Security Requirements and Controls Specifications [5] for DUT (which is Netconf server) associated with O1 interface -2. Check that NACM configurations are properly defined for access control as per clause 5.2.5.4.3 defined in O-RAN Security Requirements and Controls Specifications [5] for O-RU (which is Netconf server). - -##### Expected Results - -- 1) NACM configurations are defined as per clause 5.2.2.3 defined in O-RAN Security Requirements and Controls Specifications [5] for DUT associated with O1 interface. -- 2) NACM configurations are defined as per clause 5.2.5.4.3 defined in O-RAN Security Requirements and Controls Specifications [5] for O-RU. - -##### Expected format of evidence - -Log file with the output showing the defined NACM configuration. In case the logs do not show the required information, screenshots are used. - -6.7.2 Void - -6.7.3 Void - -6.8 802.1X - -Void - -## 6.9 X.509 - -### 6.9.1 X.509 Certificate Structure Verification for TLS - -**Requirement Name:** X.509 security - -**Requirement Reference:** SEC-CTL-O1-1, clause 5.2.2.2, SEC-CTL-O2-1, clause 5.2.3.1, REQ-SEC-OCLOUD-O2dms-1 to REQ-SEC-OCLOUD-O2dms-3, clause 5.1.8.9.1.1, REQ-SEC-OCLOUD-O2ims-1 to REQ-SEC-OCLOUD-O2ims-3, clause 5.1.8.9.1.2, REQ-SEC-O-CLOUD-NotifAPI-1 to REQ-SEC-O-CLOUD-NotifAPI-2, clause 5.1.8.9.1.3, SEC-CTL-A1-1, SEC-CTL-A1-2, clause 5.2.1.2, SEC-CTL-R1-1, SEC-CTL-R1-2, clause 5.2.6.2, REQ-SEC-Y1-1 to REQ-SEC-Y1-3, clause 5.2.7.2, O-RAN Security Requirements and Controls Specifications [5], clause 4.2.3 in O-RAN Security Protocols Specifications [2]. - -**Requirement Description:** To verify the X.509 certificate structure used by TLS components in all the ORAN systems. - -**Threat References:** T-O-RAN-03, T-O-RAN-05, T-O-RAN-06 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_X509\_CERT\_STRUCTURE\_VERIFICATION - -**Purpose:** The purpose of this test is to ensure that the X.509 certificate follows the correct structure and format for TLS. This test is applicable to X.509 certificates used in TLS modules in the O-RAN system. - -#### Procedure and execution steps - -##### Preconditions: - -- End entity X.509 certificate in ASN.1 format. -- CA certificate that signed the end entity certificate is available to the test suite. - -##### Execution steps - -Following properties of the certificate are verified. - -- Certificate Version field, Subject field, Issuer, Validity of certificate, Key Usage. - -As defined in clause 4.2.3 in O-RAN Security Protocols Specifications [2], the following certificate fields are present. - -- 1) Certificate Fields Examination: - - Validate the certificate's version field. The version number is set to v3. - - Verify the Subject field is present in the certificate. Verify that the Subject field conforms to the format defined in clause 4.2.3 in O-RAN Security Protocols Specifications [2]. - - Verify the Validity field to ensure the "Not Before" date is earlier than the "Not After" date, indicating a valid time range for the certificate's use. - - Validate that the certificate's signature field is based on the algorithm used by the CA to sign the certificate. -- 2) Key Usage Extension: - - Validate the presence of the Key Usage Extension. Verify that it conforms with the mandatory critical Key Usage extension as specified in the clause 4.2.3 in O-RAN Security Protocols Specifications [2]. -- 3) CRL Distribution Point: - - Validate that the certificate contains the cRLDistributionPoint extension. -- 4) Subject Alternative Name: - -- Validate that the certificate contains the subjectAltName extension and conforms to the requirements as specified in the clause 4.2.3 in O-RAN Security Protocols Specifications [2]. - -### Expected Results - -The certificate adheres to the X.509 standard structure as defined in clause 4.2.3 in O-RAN Security Protocols Specifications [2]. - -### Expected format of evidence - -Report containing the output of the different steps executed. In case the report does not show the required information, logs are used. - -## 6.9.2 X.509 Certificate Validity Period Verification - -**Requirement Name:** X.509 security - -**Requirement Reference:** SEC-CTL-O1-1, clause 5.2.2. 2, REQ-SEC-O2-1, clause 5.2.3.1, REQ-SEC-OCLOUD-O2dms-1 to REQ-SEC-OCLOUD-O2dms-3, clause 5.1.8.9.1.1, REQ-SEC-OCLOUD-O2ims-1 to REQ-SEC-OCLOUD-O2ims-3, clause 5.1.8.9.1.2, REQ-SEC-O-CLOUD-NotifAPI-1 to REQ-SEC-O-CLOUD-NotifAPI-2, clause 5.1.8.9.1.3, REQ-SEC-A1-1, REQ-SEC-A1-2, clause 5.2.1.1, REQ-SEC-E2-1, clause 5.2.4.1, REQ-SEC-R1-1, REQ-SEC-R1-2, clause 5.2.6.1, REQ-SEC-Y1-1 to REQ-SEC-Y1-3, clause 5.2.7.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Correctness of X.509 certificate - -**Threat References:** T-O-RAN-03, T-O-RAN-05, T-O-RAN-06 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_X509\_CERT\_VALIDITY\_PERIOD\_VERIFICATION - -**Purpose:** The purpose of this test is to ensure that the certificate's validity dates are accurate and within an acceptable range. This test is relevant for all X.509 certificates within the O-RAN system. - -### Procedure and execution steps - -#### Preconditions - -Prepare certificates with different validity periods (valid, expired, not yet valid). - -#### Execution steps - -- 1) Verify a Valid Certificate: - - Set up a valid certificate with appropriate "Not Before" and "Not After" dates. - - Verify that the certificate is accepted when used for its intended purpose. -- 2) Verify an Expired Certificate: - - Set up a certificate with a past expiration date. - - Attempt to use the expired certificate for its intended purpose. - - Verify that the certificate is rejected due to expiration. -- 3) Verify a Not Yet Valid Certificate: - - Set up a certificate with a "Not Before" date in the future. - - Attempt to use the certificate before the valid start date. - - Verify that the certificate is rejected due to being not yet valid. - -### Expected Results - -Valid certificates are accepted, while expired and not-yet-valid certificates are rejected. - -### Expected format of evidence - -Report containing the output of the different steps executed. In case the report does not show the required information, logs are used. - -## 6.9.3 X.509 Certificate Key Usage Verification - -**Requirement Name:** X.509 security - -**Requirement Reference:** SEC-CTL-O1-1, clause 5.2.2. 2, REQ-SEC-O2-1, clause 5.2.3.1, REQ-SEC-OCLOUD-O2dms-1 to REQ-SEC-OCLOUD-O2dms-3, clause 5.1.8.9.1.1, REQ-SEC-OCLOUD-O2ims-1 to REQ-SEC-OCLOUD-O2ims-3, clause 5.1.8.9.1.2, REQ-SEC-O-CLOUD-NotifAPI-1 to REQ-SEC-O-CLOUD-NotifAPI-2, clause 5.1.8.9.1.3, REQ-SEC-A1-1, REQ-SEC-A1-2, clause 5.2.1.1, REQ-SEC-E2-1, clause 5.2.4.1, REQ-SEC-R1-1, REQ-SEC-R1-2, clause 5.2.6.1, REQ-SEC-Y1-1 to REQ-SEC-Y1-3, clause 5.2.7.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Correctness of X.509 certificate - -**Threat References:** T-O-RAN-03, T-O-RAN-05, T-O-RAN-06 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_X509\_CERT\_KEY\_USAGE\_VERIFICATION - -**Purpose:** The purpose of this test is to confirm that the certificate's key usage and extended key usage extensions are correctly defined. - -### Procedure and execution steps - -#### Preconditions - -Prepare certificates with different key usage and extended key usage extensions. - -#### Execution steps - -- 1) Verify a Certificate with Correct Usage Extensions: - - Set up a certificate with proper key usage and extended key usage extensions matching its intended purpose (e.g., server authentication). - - Attempt to use the certificate for its designated purpose. - - Verify that the certificate is accepted. -- 2) Verify a Certificate with Incorrect or Missing Usage Extensions: - - Set up a certificate with incorrect or missing key usage or extended key usage extensions. - - Attempt to use the certificate for its intended purpose. - - Verify that the certificate is rejected. - -### Expected Results - -Certificates with correct usage extensions are accepted, while those with incorrect or missing extensions are rejected. - -### Expected format of evidence - -Report containing the output of the different steps executed. In case the report does not show the required information, logs are used. - -## 6.9.4 X.509 Certificate Chain Validation - -**Requirement Name:** X.509 security - -**Requirement Reference:** SEC-CTL-O1-1, clause 5.2.2. 2, REQ-SEC-O2-1, clause 5.2.3.1, REQ-SEC-OCLOUD-O2dms-1 to REQ-SEC-OCLOUD-O2dms-3, clause 5.1.8.9.1.1, REQ-SEC-OCLOUD-O2ims-1 to REQ-SEC-OCLOUD-O2ims-3, clause 5.1.8.9.1.2, REQ-SEC-O-CLOUD-NotifAPI-1 to REQ-SEC-O-CLOUD-NotifAPI-2, clause 5.1.8.9.1.3, REQ-SEC-A1-1, REQ-SEC-A1-2, clause 5.2.1.1, REQ-SEC-E2-1, clause 5.2.4.1, REQ-SEC-R1-1, REQ-SEC-R1-2, clause 5.2.6.1, REQ-SEC-Y1-1 to REQ-SEC-Y1-3, clause 5.2.7.2 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Correctness of X.509 certificate chain - -**Threat References:** T-O-RAN-03, T-O-RAN-05, T-O-RAN-06 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_X509\_CERT\_CHAIN\_VALIDATION - -**Purpose:** The purpose of this test is to validate the certificate chain's integrity and trustworthiness. This test is applicable to scenarios where certificates are part of a chain (e.g., intermediate and root certificates). - -### Procedure and execution steps - -#### Preconditions - -Prepare a certificate chain with correct and incorrect configurations. - -#### Execution steps - -- 1) Verify a Certificate Chain with Correct Order and Valid Signatures: - - Set up a valid certificate chain with correct order and valid signatures. - - Attempt to use the certificate chain for its intended purpose. - - Verify that the certificate chain is accepted. -- 2) Verify a Certificate Chain with Incorrect Order: - - Set up a certificate chain with incorrect order. - - Attempt to use the certificate chain for its intended purpose. - - Verify that the certificate chain is rejected. -- 3) Verify a Certificate Chain with Invalid Signatures: - - Set up a certificate chain with certificates with invalid signatures. - - Attempt to use the certificate chain for its intended purpose. - - Verify that the certificate chain is rejected -- 4) Verify a Certificate Chain with Incorrect Order and Invalid Signatures: - - Set up certificate chain with incorrect order and certificates with invalid signatures. - - Attempt to used the certificate chain for its intended purpose. - - Verify that the certificate chain is rejected. - -#### Expected Results - -A valid certificate chain is accepted, while an invalid chain is rejected. - -### Expected format of evidence - -Report containing the output of the different steps executed. In case the report does not show the required information, logs are used. - -## 6.10 eCPRI - -### 6.10.1 Void - -### 6.10.2 eCPRI Input Validation - -**Requirement Name:** eCPRI security - -**Requirement Reference:** REQ-SEC-TRAN-1, clause 5.3.4.1 in O-RAN Security Requirements and Controls Specifications [5]. - -**Requirement Description:** eCPRI protocol robustness – ability to handle unexpected inputs (not in-line with protocol specification) without functional compromise. - -**Threat References:** T-FRHAUL-01, T-FRHAUL-02 - -**DUT/s:** O-RU, O-DU - -**Test Name:** TC\_eCPRI\_INPUT\_VALIDATION - -**Purpose:** The purpose of this test is to ensure that the DUT properly handles malformed or abnormal eCPRI messages,, ensuring robustness against malformed headers, length mismatches, and unexpected payload values. - -### Procedure and execution steps - -#### Preconditions - -- eCPRI interface is accessible. -- Input fields requiring validation are identified, including both eCPRI header fields and payload contents based on message type. -- Packet capture is active at the DUT ingress interface to confirm behavior. -- A traffic generator capable of constructing and sending both valid and malformed eCPRI messages is available. - -#### Execution steps - -- 1) Positive Case (well-formed eCPRI messages): - - Send eCPRI messages through the eCPRI interface with valid and expected field values (per [26] clauses 5.1.3.2), including: - - Message type - - Payload size - - Sequence ID (if sequence ID checking is supported and enabled; see NOTE) - - Protocol version - - Verify that the DUT processes these messages successfully without detecting protocol errors. -- 2) Negative Case (malformed eCPRI messages): - - Introduce malformed or unexpected values into eCPRI header fields, including: - -- Invalid Message Type (e.g., unsupported types) - - Incorrect Payload Size (payload shorter/longer than declared) - - Out-of-range Sequence ID values (if sequence ID checking is supported and enabled; see NOTE) - - Unknown or unsupported Protocol Revision -- Verify that the DUT discards the malformed messages. The DUT may increment relevant optional counters as defined in [26] clauses 9.1 if implemented (RX\_CORRUPT, RX\_ERR\_DROP, RX\_SEQID\_ERR, RX\_SEQID\_ERR\_C). - -NOTE: According to [26], clause 5.1.3.2.7, sequence ID checking by the DUT is optional, and the feature SEQ-ID-CHECKING-CONFIGURABLE can be enabled or disabled. Therefore, verification of sequence ID handling in this test case applies only if the feature is supported and sequence ID checking is enabled on the DUT. - -#### Expected Results: - -- DUT successfully processes valid eCPRI messages. -- Malformed eCPRI messages are discarded. -- If the DUT implements optional counters defined in [26] clauses 9.1 (RX\_CORRUPT, RX\_ERR\_DROP, RX\_SEQID\_ERR, RX\_SEQID\_ERR\_C), these counters increment accordingly. - -#### Expected format of evidence - -- A log file showing protocol error detection. -- PCAP traces showing valid and malformed eCPRI message transmissions and DUT behaviour. - -### 6.10.3 eCPRI Error and Timeout Handling - -**Requirement Name:** eCPRI security - -**Requirement Reference:** REQ-SEC-TRAN-1, clause 5.3.4.1 in O-RAN Security Requirements and Controls Specifications [5]. - -**Requirement Description:** eCPRI protocol robustness - ability to handle unexpected inputs (not in-line with protocol specification) without functional compromise. - -**Threat References:** T-FRHAUL-01, T-FRHAUL-02 - -**DUT/s:** O-RU, O-DU - -**Test Name:** TC\_eCPRI\_ERROR\_TIMEOUT\_HANDLING - -**Purpose:** The purpose of this test is to ensure that the DUT securely handles errors on the eCPRI interface, including malformed packets, unexpected messages, and timeout scenarios, without disclosing sensitive information or compromising DUT stability. - -#### Procedure and execution steps - -##### Preconditions - -- eCPRI interface is accessible. -- Various error scenarios (malformed, unexpected, or delayed eCPRI packets) are identified. - -##### Execution steps - -- 1) Attempt to force error conditions on the eCPRI interface: - - Transmit eCPRI packets with anomalies such as invalid headers, incorrect protocol versions, unsupported message types, or corrupted payloads. - -- Introduce significant delays or slow down the network connection on the eCPRI interface. -- 2) Verify that the DUT detects and handles the errors. -- 3) Restore normal connectivity. -- 4) Resend a normal request to the DUT through the eCPRI interface. -- 5) Verify that the DUT processes the request successfully and provides the expected response. - -**Expected Results:** The DUT handles errors securely, providing meaningful error messages without disclosing sensitive information and recovering seamlessly when the connection is restored. - -#### Expected format of evidence - -- Screenshots of the error messages or status codes received from the DUT through the eCPRI interface in response to triggered errors. -- A log file documenting the requests and responses during error scenarios. - -### 6.10.4 Void - -### 6.10.5 eCPRI Logging and Auditing - -**Requirement Name:** eCPRI security - -**Requirement Reference:** REQ-SEC-SLM-APP-EVT-1, clause 5.3.8.11.4 in O-RAN Security Requirements and Controls Specifications [5]. - -**Requirement Description:** Logging of security events and auditing of activities on the eCPRI - -**Threat References:** T-FRHAUL-01, T-FRHAUL-02 - -**DUT/s:** O-RU, O-DU - -**Test Name:** TC\_eCPRI\_LOGGING\_AUDITING - -**Purpose:** The purpose of this test is to validate that the DUT logs relevant security events and activities on the eCPRI interface and supports auditing capabilities. - -#### Procedure and execution steps - -##### Preconditions - -- eCPRI interface is accessible. -- Logging and auditing mechanisms are enabled and configured. - -##### Execution steps - -- 1) Perform various eCPRI security events. Key eCPRI security events include [26]: - - Total count of received messages (valid and erroneous) for user and control planes - - Messages received within the expected time window - - If supported: Early and late arrivals of messages - - If supported: Sequence ID errors for on-time messages - - Messages dropped due to protocol violations or corruption - - Timing and sequence errors in control plane messages - - Total outbound messages for user and control planes - -- Messages discarded due to errors, resource constraints, or policy violations - - Identified duplicated packets. -- 2) Verify that the DUT generates appropriate log entries for each security event, capturing relevant security-related information. - - 3) Access and review the generated logs to ensure they contain the necessary details for security auditing purposes. - -**Expected Results:** The DUT generates accurate logs, recording security-related events and activities for auditing and forensic analysis. - -**Expected format of evidence** - -- The generated log files containing recorded security events and activities during the testing process. -- Screenshots of log entries highlighting relevant security events and timestamps. - -## 6.10.6 Void - -## 6.11 SCTP - -### 6.11.1 Void - -### 6.11.2 Void - -### 6.11.3 Void - -### 6.11.4 Void - -## 6.11.5 SCTP DoS Prevention Rate Limiting - -**Requirement Name:** SCTP security - -**Requirement Reference:** REQ-SEC-TRAN-1, clause 5.3.4.1 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Ability to handle unexpected input - -**Threat References:** T-E2-01, T-E2-02, T-E2-03 - -**DUT/s:** Near-RT RIC, O-CU-CP, O-CU-UP, O-DU - -**Test Name:** TC\_SCTP\_DOS\_PREVENTION\_RATE\_LIMITING - -**Purpose:** The purpose of this test is to verify that the SCTP protocol effectively handles DoS attacks and prevents resource exhaustion. - -**Procedure and execution steps** - -**Preconditions** - -- Enable DoS prevention mechanisms. -- The rate limiting parameters, such as the maximum number of connections or allowed data transfer rate, are properly defined. -- Use SCTP library. - -EXAMPLE 1: the sctplib library in the C programming language - -#### Execution steps - -- 1) Simulate a DoS attack by overwhelming the SCTP protocol with a large number of connection requests (send data at a rate that exceeds the defined rate limiting parameters). - -EXAMPLE 2: Sample SCTP commands: - -``` -for (int i = 0; i < num_connections; i++) { - sctp_socket = sctp_socket(AF_INET, SOCK_STREAM, IPPROTO_SCTP); - // Establish connections rapidly beyond system limits -} -``` - -- 2) Monitor the SCTP protocol's response and behaviour during the excessive connection and data transfer attempts. - -#### Expected Results - -- The SCTP protocol detects the excessive usage and applies rate limiting measures to restrict or reject connections or data transfers that exceed the defined limits. -- The system handles the rate limiting effectively, ensuring that resources are not exhausted or overwhelmed. - -#### Expected format of evidence - -- Test logs showing successful handling of the DoS attack, such as connection limits or rejection messages. -- System performance metrics or logs indicating the proper handling of excessive connection requests. - -### 6.11.6 SCTP Input Validation - -**Requirement Name:** SCTP security - -**Requirement Reference:** REQ-SEC-TRAN-1, clause 5.3.4.1 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Ability to handle unexpected input - -**Threat References:** T-E2-01, T-E2-02, T-E2-03 - -**DUT/s:** Near-RT RIC, O-CU-CP, O-CU-UP, O-DU - -**Test Name:** TC\_SCTP\_INPUT\_VALIDATION - -**Purpose:** To verify that the SCTP protocol performs proper input validation to prevent security vulnerabilities such as buffer overflows or injection attacks. - -#### Procedure and execution steps - -##### Preconditions - -- The SCTP protocol is configured with input validation enabled. -- Use SCTP library. - -EXAMPLE 1: the sctplib library in the C programming language - -##### Execution steps - -- 1) Attempt to establish a connection using the SCTP protocol and provide invalid or malicious input. - -EXAMPLE 2: Sample SCTP command: sctp\_socket = sctp\_socket(AF\_INET, SOCK\_STREAM, IPPROTO\_SCTP); - -- 2) Send data containing invalid or malicious content over the connection. - -EXAMPLE 3: Sample SCTP command: `sctp_sendmsg(sctp_socket, malicious_data_buffer, data_length, NULL, 0, 0, 0, stream_id, 0, 0);` - -#### Expected Results - -- The SCTP protocol performs input validation and rejects or sanitizes the invalid or malicious input. -- The connection is not established, or the malicious data is handled safely. - -#### Expected format of evidence - -- Test logs showing the rejection or sanitization of invalid or malicious input. -- Output from the application indicating the successful validation and rejection of malicious data. - -### 6.11.7 Void - -### 6.11.8 Void - -## 6.12 Transactional APIs - -### 6.12.1 Transactional API Authentication – service producer role - -**Requirement Name:** RESTful API protection - -**Requirement Reference:** REQ-SEC-O-CLOUD-NotifAPI-1, REQ-SEC-O-CLOUD-NotifAPI-2, clause 5.1.8.9.1.3, REQ-SEC-API-1, REQ-SEC-API-2, REQ-SEC-API-3, REQ-SEC-API-4, REQ-SEC-API-5, REQ-SEC-API-6, REQ-SEC-API-8, REQ-SEC-API-9, REQ-SEC-API-10, REQ-SEC-API-13, REQ-SEC-API-15, clause 5.3.10.2 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** API robustness - -**Threat References:** T-O-RAN-01, T-O-RAN-02, T-O-RAN-03, T-O-RAN-05, T-O-RAN-06 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_REST\_API\_AUTHENTICATION - -**Purpose:** The purpose of this test is to verify the authentication mechanism of an O-RAN NF supporting RESTful API, service producer role. - -#### Procedure and execution steps - -##### Preconditions - -- An O-RAN NF supporting the RESTful API is provisioned and running. -- Access to the O-RAN NF management system or command-line interface. - -##### Execution steps - -- 1) Positive Case: - -- Authenticate using valid credentials or API tokens: - -EXAMPLE 1: `curl -X POST -H "Content-Type: application/json" -d '{"username":"", "password":""}' http:///auth` - -- Capture the authentication token from the response. - -- Execute an authenticated request against a RESTful API present in an O-RAN NF acting as a service producer, using a signed token (e.g., get cell status). -- Verify that the request is successful and returns the expected response. - -2) Negative Case: - -- Attempt to access the RESTful API present in an O-RAN NF acting as a service producer, without providing valid authentication credentials: - -EXAMPLE 2: curl http:///cell-status - -- Verify that the request fails and returns an unauthorized response. -- 3) Negative Case: -- Attempt to access the RESTful API present in an ORAN NF acting as service producer, using unsigned token (the “alg” field in header section of the JWT token should be set to “none” and empty string for signature value). - - Verify that the request fails and returns failure from API end point. - -#### Expected Results - -1) Positive Case: - -- Authentication using valid credentials or API tokens is successful. -- Authorized requests to O-RAN NF resources return the expected responses. - -2) Negative Case: - -- Requests without valid authentication credentials are rejected with an unauthorized response. - -3) Negative Case: - -- Requests with token which are not signed are rejected. - -#### Expected format of evidence - -- Screenshots or logs showing the successful authentication and authorized requests. -- Screenshots or logs showing the failed authentication attempts. - -## 6.12.2 Transactional API Authorization and Access Control - -**Requirement Name:** RESTful API protection - -**Requirement Reference:** REQ-SEC-O-CLOUD-NotifAPI-1, REQ-SEC-O-CLOUD-NotifAPI-2, clause 5.1.8.9.1.3, REQ-SEC-API-1, REQ-SEC-API-2, REQ-SEC-API-3, REQ-SEC-API-4, REQ-SEC-API-5, REQ-SEC-API-6, REQ-SEC-API-8, REQ-SEC-API-9, REQ-SEC-API-10, REQ-SEC-API-13, REQ-SEC-API-15, clause 5.3.10.2 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** API robustness - -**Threat References:** T-O-RAN-01, T-O-RAN-02, T-O-RAN-03, T-O-RAN-05, T-O-RAN-06 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_REST\_AUTHORIZATION\_ACCESS\_CONTROL - -**Purpose:** The purpose of this test is to ensure that the RESTful API enforces proper authorization and access control mechanisms. - -#### Procedure and execution steps - -### Preconditions - -- An O-RAN NF supporting the RESTful API is provisioned and running. -- Access to the O-RAN NF management system or command-line interface. -- User roles and permissions are defined and configured. - -### Execution steps - -#### 1) Positive Case: - -- Authenticate using credentials associated with a user assigned to a role with necessary permissions: - -EXAMPLE 1: **curl -X POST -H "Content-Type: application/json" -d '{"username":"","password":""}' http:///auth** - -- Capture the authentication token from the response. -- Execute a request that requires the permissions granted by the user's role (e.g., update configuration). -- Verify that the request is successful and returns the expected response. - -#### 2) Negative Case: - -- Authenticate using credentials associated with a user not assigned to a role with necessary permissions: - -EXAMPLE 2: **curl -X POST -H "Content-Type: application/json" -d '{"username":"","password":""}' http:///auth** - -- Capture the authentication token from the response. -- Execute a request that requires the permissions beyond the user's role (e.g., perform a restricted operation). -- Verify that the request fails and returns a forbidden response. - -### Expected Results - -#### 1) Positive Case: - -- Users with appropriate roles and permissions can perform authorized actions. -- Requests requiring specific permissions return the expected responses. - -#### 2) Negative Case: - -- Users without necessary roles or permissions are restricted from performing unauthorized actions. -- Requests requiring permissions beyond the user's role return a forbidden response. - -### Expected format of evidence - -- Screenshots or logs showing the successful authorization and access control enforcement. -- Screenshots or logs showing the failed authorization attempts. - -## 6.12.3 Transactional API Input Validation and Sanitization - -**Requirement Name:** RESTful API protection - -**Requirement Reference:** REQ-SEC-API-12, REQ-SEC-API-13, REQ-SEC-API-15, clause 5.3.10.2 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** API robustness - -**Threat References:** T-O-RAN-04 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_REST\_INPUT\_VALIDATION\_SANITIZATION - -**Purpose:** The purpose of this test is to validate that the RESTful API properly validates and sanitizes input data to prevent common security vulnerabilities. - -### Procedure and execution steps - -#### Preconditions - -- An O-RAN NF supporting the RESTful API is provisioned and running. -- Access to the O-RAN NF management system or command-line interface. - -#### Execution steps - -1) Positive Case: - -- Construct a valid request with appropriate input data: - -EXAMPLE 1: The input parameters can be within the valid range for the parameters supported for the API. This includes the supported (valid) HTTP method(s) for the API. - -``` -curl -X POST -H "Content-Type: application/json" -d '{"parameter1":"value1", "parameter2":"value2"}' -http:///api-endpoint -``` - -- Verify that the request is successful and returns the expected response. - -2) Negative Case (1): - -- Construct a request with invalid input data: - -EXAMPLE 2: The input parameters can be outside the valid range for the parameters supported for the API. - -``` -curl -X POST -H "Content-Type: application/json" -d '{"parameter1":"", -"parameter2":"value2"}' http:///api-endpoint -``` - -- Verify that the request fails and returns an error response. -- Verify that log is generated for the input validation errors. - -3) Negative Case (2): - -- Construct a request with invalid/not supported HTTP method: - -EXAMPLE 3: HTTP method being invoked is invalid, i.e. not a supported method for the API. - -- Verify that the request fails and returns an error response. -- Verify that log is generated indicating HTTP method is not supported. - -#### Expected Results - -1) Positive Case: - -- Requests with valid and appropriate input data are successfully processed. -- Responses from the O-RAN NF RESTful API are as expected. - -2) Negative Case (1): - -- Requests with invalid input data are rejected and handled properly to prevent security vulnerabilities. -- Log generated for the invalid inputs after unsuccessful validation. - -3) Negative Case (2): - -- Requests with invalid or unsupported HTTP methods are rejected. -- Log generated for the invalid HTTP method. - -#### Expected format of evidence - -- Screenshots or logs showing the successful input validation and sanitization. -- Screenshots and logs showing failed input validation or sanitization attempts. - -## 6.12.4 Transactional API Security Logging and Monitoring - -**Requirement Name:** RESTful API protection - -**Requirement Reference:** REQ-SEC-O-CLOUD-NotifAPI-1, REQ-SEC-O-CLOUD-NotifAPI-2, clause 5.1.8.9.1.3, REQ-SEC-API-1, REQ-SEC-API-2, REQ-SEC-API-3, REQ-SEC-API-4, REQ-SEC-API-5, REQ-SEC-API-6, REQ-SEC-API-8, REQ-SEC-API-9, REQ-SEC-API-10, REQ-SEC-API-13, REQ-SEC-API-15, clause 5.3.10.2 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** API robustness - -**Threat References:** T-O-RAN-01, T-O-RAN-02, T-O-RAN-03, T-O-RAN-05, T-O-RAN-06 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_REST\_SECURITY\_LOGGING\_MONITORING - -**Purpose:** The purpose of this test is to verify that the O-RAN NF logs and monitors API activities for security and compliance purposes. - -#### Procedure and execution steps - -##### Preconditions - -- An O-RAN NF supporting the RESTful API is provisioned and running. -- Access to the O-RAN NF management system or command-line interface. - -##### Execution steps - -- 1) Positive Case: - - Enable API logging and monitoring for the O-RAN NF. - - Generate a series of API requests and actions. - - Review the logs or monitoring system for the recorded activities. -- 2) Negative Case: - - Attempt unauthorized API actions or exploit security vulnerabilities. - - Verify that the logs or monitoring system captures and raises alerts for these activities. - -##### Expected Results - -- 1) Positive Case: - - API activities are logged and monitored by the O-RAN NF. - - Logs or monitoring system records the expected API requests and actions. -- 2) Negative Case: - - Unauthorized or malicious API actions trigger alerts in the logs or monitoring system. - -- Logs or monitoring system captures and records failed security attempts. - -#### Expected format of evidence - -Logs from the O-RAN NF management system showing the successful or failed API logging and monitoring settings. In case the logs do not show the required information, screenshots are used. - -## 6.13 MACsec - -### 6.13.1 MACsec Cipher Suite Negotiation and Support Validation - -**Requirement Name:** MACsec Cipher Suite Negotiation Support Validation - -**Requirement Reference:** SEC-CTL-OFHMECC-5, SEC-CTL-OFHWMM-2, SEC-CTL-OFHLMM-3, clause 5.2.5.6 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Open FH elements supporting MACsec—whether in EDE-CC WAN, or LAN mode—implement the cipher suites specified in clause 4.9 of the O-RAN Security Protocols Specification [2] - -NOTE 1: This test case is conditionally applicable only if MACsec is supported by the DUT. - -NOTE 2: The cipher suite GCM-AES-128 is mandatory according to IEEE 802.1AE-2018 [32]. Other cipher suites, such as GCM-AES-256, are optional. If an optional cipher suite is supported by the DUT, this test case applies for each supported cipher. - -**Threat References:** T-O-RAN-08 - -**DUT/s:** O-RU, O-DU - -**Test Name:** TC\_MACsec\_Cipher\_Suite\_Support - -**Purpose:** To verify that the DUT supports and correctly negotiates the required MACsec cipher suite(s) in all supported MACsec modes: EDE-CC, WAN and LAN. - -#### Procedure and Execution Steps - -##### Preconditions - -- The DUT supports MACsec (IEEE 802.1AE) and operates in one of the following modes: EDE-CC, WAN, or LAN. -- The test setup includes MACsec-capable test equipment that supports operation in all three modes: EDE-CC, WAN, and LAN. -- The cipher suite under test, at minimum GCM-AES-128, is supported by both the DUT and the test equipment. -- Role behavior: - - If the DUT is an O-RU, it operates as the 802.1X supplicant. The test equipment (or O-DU emulator) acts as the authenticator and triggers 802.1X authentication and MKA establishment. - - If the DUT is an O-DU, it operates as the 802.1X authenticator. The test equipment acts as the supplicant and initiates the 802.1X authentication sequence. - -##### Execution steps - -For each MACsec mode supported by the DUT (EDE-CC, WAN, LAN): - -- Configure the DUT to operate in the target MACsec mode. -- Establish the 802.1X session: - -- If the DUT is an O-RU, allow it to initiate the 802.1X authentication as a supplicant; the test equipment responds as the authenticator. - - If the DUT is an O-DU, the test equipment initiates the 802.1X authentication as a supplicant; the DUT performs the authenticator role. -- Upon successful 802.1X authentication, ensure that the MACsec Key Agreement (MKA) session is established and that both peers derive the same Secure Association Key (SAK). -- For each supported cipher suite (starting with GCM-AES-128): - - Negotiate the specific cipher suite under test. - - From the test equipment, send generic Ethernet frames to the DUT that are encapsulated and encrypted by MACsec using the negotiated cipher suite. - - Verify that the DUT receives, decrypts, and responds to the traffic. - - Capture the response frames at the test equipment and verify that the DUT successfully encapsulated and encrypted the entire response using the negotiated cipher suite. - -### Expected Results - -For each tested MACsec mode and cipher suite: - -- The DUT successfully establishes a MACsec session using the negotiated cipher suite. -- MACsec encryption is correctly applied by both peers (bidirectional). - -### Expected Format of Evidence: - -- Logs from the testing equipment showing the accepted cipher suite. -- Packet capture files confirming that all captured response frames from the DUT are correctly encapsulated and encrypted with the negotiated cipher suite. - -## 6.13.2 MACsec protection of Open FH traffic - -**Requirement Name:** MACsec protection of Open FH traffic - -**Requirement Reference:** SEC-CTL-OFHLMM-1, SEC-CTL-OFHMECC-1, SEC-CTL-OFHMECC-3, clause 5.2.5.6, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The Open FH network elements support securing of Open FH traffic using MACsec. - -**Threat References:** T-FRHAUL-02, T-UPLANE-01, T-UPLANE-02 - -**DUT/s:** O-DU, O-RU - -**Test Name:** TC\_MACsec\_Traffic\_Protected - -**Purpose:** To verify that when MACsec is enabled, the DUT correctly secures Open FH traffic on the Transmit (Tx) path and rejects malicious or non-compliant traffic on the Receive (Rx) path, including replay protection and integrity/decryption errors. - -### Procedure and execution steps - -#### Preconditions - -- DUT connected to test equipment over Open FH link. - -- MACsec supported on both DUT and test equipment with matching parameters (e.g., cipher suite) available. -- Either EAP-TLS/MKA or pre-shared CAK/CKN available and configured consistently on both ends. -- Replay window size (N) is configurable by the tester or the default window size is known and recorded. -- The DUT exposes the IEEE 802.1AE counters InPktsLate, InPktsBadICV, and InPktsNoTag. - -NOTE: If the DUT supports multiple MACsec modes, the execution steps shall be repeated for each supported mode to observe encryption and replay protection behavior. - -## Execution steps - -### Phase 1: Setup, baseline, and Transmit (Tx) security verification - -1. Enable MACsec on both DUT and test equipment with matching parameters (cipher suite). -2. Record the current baseline values of all relevant security counters on the DUT (InPktsLate, InPktsBadICV, InPktsNoTag). -3. From the DUT, generate or forward representative C-/U-/S-Plane traffic toward the test equipment over the Open FH link. -4. Capture the traffic on the Open FH link using the test equipment. -5. Verify Tx Encryption: Verify that C-Plane and U-Plane frames carry the MACsec EtherType (0x88E5) and include the SecTAG and ICV fields, indicating encryption and integrity protection. -6. In LAN mode only, also verify that S-Plane frames carry the MACsec EtherType (0x88E5) and are MACsec-encapsulated (if supported by the DUT). - -### Phase 2: Receive (Rx) replay protection verification - -7. From the test equipment, send a monotonically increasing sequence of valid MACsec frames to the DUT to establish a receive window; record the current highest accepted Packet Number (PN\_high) and the configured (or default) replay window size N. -8. Duplicate within window: Re-transmit one previously accepted frame whose PN is within the current receive window (i.e., $PN\_high - N + 1 \leq PN\_dup \leq PN\_high$ ). -9. Verify that if duplicate detection is enabled, the DUT discards the replayed frame (i.e., it is not forwarded). If duplicate detection is not implemented, the frame may be accepted. -10. Out-of-window (too old): Transmit frames with PN values lower than the lowest acceptable PN for the current window (i.e., $PN < PN\_high - N + 1$ ). -11. Verify that the DUT discards these frames and that InPktsLate increments accordingly. - -### Phase 3: Receive (Rx) integrity and cleartext verification - -12. Identify the traffic classes or VLANs that are configured to be protected by MACsec and those that are explicitly excluded from protection. -13. From the test equipment, send a set of representative protected frames, i.e. frames that according to configuration are protected by MACsec (C-Plane and U-Plane traffic within protected VLANs). Transmit these frames without MACsec encapsulation (cleartext). -14. Send valid MACsec frames but intentionally modify the Integrity Check Value (ICV) in each frame. -15. Verify: - - Cleartext frames for protected VLANs/traffic are discarded (InPktsNoTag increments). - -- ICV-corrupted frames are discarded (InPktsBadICV increments). - -NOTE: “Representative frames” refer to frames from traffic classes or VLANs that are configured to be protected by MACsec. Depending on the active protection policy, cleartext frames on excluded VLANs may be legitimately accepted and are not considered failures. - -### Expected results - -- With MACsec enabled, C-Plane and U-Plane traffic is encrypted and integrity-protected (i.e., encapsulated with EtherType 0x88E5). -- In LAN mode only, if supported by the DUT, S-Plane traffic is also encrypted and integrity-protected. -- Replay protection: - - Frames outside the receive window are dropped (InPktsLate increases). - - Duplicate frames within the window are discarded when duplicate-detection is enabled; otherwise acceptance is recorded as observed behavior (non-failure). -- The DUT discards received corrupted (ICV failure) and cleartext (no tag) frames. The InPktsBadICV and InPktsNoTag counters accurately register the discard events. - -### Expected format of evidence: - -- Packet capture files showing MACsec EtherType (0x88E5) for Open FH traffic. -- Before/after snapshots of the MACsec security counters (InPktsLate, InPktsBadICV, InPktsNoTag) showing accurate increments following the failure attempts. - -## 6.13.3 Cleartext policy exception for Open FH traffic - -**Requirement Name:** Cleartext policy exception for Open FH traffic - -**Requirement Reference:** SEC-CTL-OFHLM-2, clause 5.2.5.6.4.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The Open FH network elements support the configuration of policies to allow certain types of Open FH traffic to be sent in clear text. - -**Threat References:** T-FRHAUL-02, T-UPLANE-01, T-UPLANE-02 - -**DUT/s:** O-RU - -**Test Name:** TC\_MACsec\_Cleartext\_Exception - -**Purpose:** To verify that the DUT supports MACsec bypass policies that allow specific Open FH traffic, identified by its destination MAC address, Ethernet type, or VLAN ID, to be transmitted entirely in cleartext (unprotected), while ensuring all other Open FH traffic remains MACsec-encrypted and integrity-protected. - -### Procedure and execution steps - -#### Preconditions - -- DUT connected to a test equipment over Open FH link; MACsec enabled. -- DUT is an O-RU that includes MACSEC-BYPASS-POLICY in its YANG library feature list ([21], clause 7.13.5). - -- O-RU controller access is available to configure bypass policy. - -## Execution steps - -Perform the following sub-tests for each bypass policy type supported by the DUT: - -### A. MAC address-based bypass - -1. Configure, via the O-RU controller, a MACsec bypass policy matching a specific destination MAC address on the O-RU base-interface. -2. Trigger an action (e.g., generate uplink traffic or forward downlink traffic) such that the DUT transmits traffic to the configured destination MAC address, and concurrently transmits regular C-/U-/S-Plane traffic to other MACs. -3. Capture and verify: - - a) Frames to the configured destination MAC address have a non-MACsec EtherType (i.e., value other than 0x88E5) and contain plaintext data. - - b) All other Open FH traffic carries the MACsec EtherType (0x88E5) and is encapsulated. - -### B. Ethernet type-based bypass - -1. Configure, via the O-RU controller, a MACsec bypass policy matching a specific Ethernet type (e.g., PTP 0x88F7). -2. Send frames of the specified EtherType plus regular C-/U-/S-Plane traffic of other types. -3. Capture and verify: - - a) Frames with the configured EtherType have a non-MACsec EtherType and are in clear. - - b) All other Open FH traffic carries the MACsec EtherType (0x88E5) and is encapsulated. - -### C. VLAN ID-based bypass - -1. Configure, via the O-RU controller, a MACsec bypass policy matching a specific VLAN ID on the O-RU base-interface. -2. Send traffic tagged with the specified VLAN ID and concurrent traffic on other VLANs (or untagged). -3. Capture and verify: - - a) Frames on the configured VLAN ID have a non-MACsec EtherType and are in clear. - - b) All other Open FH traffic carries the MACsec EtherType (0x88E5) and is encapsulated. - -## Expected results - -- For each configured bypass type (MAC address, Ethernet type, VLAN ID), only the matching traffic is transmitted in cleartext (i.e., without the MACsec EtherType 0x88E5); all other Open FH traffic remains MACsec-encrypted and integrity-protected. - -## Expected format of evidence: - -- Controller configuration showing each configured bypass policy. -- Packet captures showing the absence of MACsec EtherType (0x88E5) for the selected cleartext traffic and the presence of MACsec EtherType (0x88E5) for all other protected traffic. - -# 7 Common Network Security Tests for O-RAN architecture elements - -## 7.1 Overview - -This clause contains a set of security evaluations that are performed from outside and inside of the network function in a network capacity. It is used to measure the external exposure and risk(s) of the function in place and leverages common techniques used in cyber security to evaluate the risk(s) device under test faces or has. - -The objects in scope of these network-based security tests are SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU and O-Cloud. - -## 7.2 Network Protocol and Service Enumeration - -### 7.2.1 Network Protocol and Service Enumeration - -**Requirement Name:** Network protocol and service enumeration - -**Requirement Reference:** REQ-SEC-NET-1, clause 5.3.3.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Protocols and services are documented by vendor. No undocumented protocols and services are offered. - -**Threat References:** T-O-RAN-01, T-O-RAN-02 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_Network\_Protocol\_And\_Enumeration - -**Purpose:** To verify that the list of active network protocols and services on DUT is in line with vendor-provided list of network protocols and services supported. Probing of network protocols and services on DUT provides the information whether the service is active or not. This test case probes all possible TCP and SCTP ports in range 0-65535 using port scanner for presence of the active services. - -This test case probes all documented UDP ports from vendor-provided list using port scanner for presence of the active services. Optionally, additional UDP ports may be scanned as well. - -NOTE 1: In practice, such probing is often referred to as network scanning or port scanning. - -NOTE 2: In practice, services may also run on ports different from ports defined in [i.1]. - -#### Procedure and execution steps - -##### Preconditions - -- Port scanner with capabilities as defined in clause 5.3 of present document. -- Network access to DUT -- Vendor-provided list of network protocols and services supported by DUT - -##### Execution steps - -- 1) List of open ports is determined as follows: - - Port scanner scans all TCP ports in range 0-65535 on the IP interface of DUT. TCP SYN/ACK response by DUT are interpreted as open port. - -- Port scanner scans all SCTP ports in range 0-65535 on the IP interface of DUT. SCTP INIT-ACK response by DUT are interpreted as open port. -- All UDP ports documented in vendor-provided list are interpreted as open ports. Other UDP ports may be considered as open for the purpose of service detection. - -NOTE 3: Due to the nature of UDP protocol, there is no simple method of open port detection similar to TCP/SCTP methods based on analysis of response message type (TCP: SYN/ACK, SCTP: INIT-ACK). In case of UDP, open port detection inevitably relies on service detection which is discussed in step 2 of this test procedure. In practice, port scans of entire UDP port range 0-65535 are impractical and time consuming. Typically, service detection is performed only for subset of UDP ports. UDP port subset selection is arbitrary and not standardized. Service detection in this test procedure is required for UDP ports from vendor-provided list and is optional for other UDP ports. - -2) For each open port from previous step, port scanner performs service detection by sending service probe(s) as follows: - -- If open port is listed in vendor-provided list, port scanner uses service probe from its built-in database that exactly matches service documented in vendor-provided list. -- If open port is not listed in vendor-provided list, port scanner uses service probe from its built-in database that exactly matches service defined in [i.1] for the that open port. If such service is not defined in [i.1], port scanner may report service as "unknown". Alternatively, port scanner may perform further service detection attempts based on other service probes from its built-in database. - -NOTE 4: Service detection for open ports that are also listed in vendor-provided list requires only one probe. However, service information can be helpful in discussion with DUT vendor. This test procedure therefore accommodates optional service detection based on one probe or multiple probes. - -3) Port scanner produces list of detected active network protocols, ports and services on DUT. - -## Expected results - -Comparison between the vendor-provided list of all supported network protocols and services and the list of active network protocols and services found by port scanner is performed. - -All services found by port scanner are documented in vendor-provided list. This test case ends with success if: - -- both lists match exactly -- list of network protocols and services found by port scanner has fewer items than vendor-provided list; all items found by port scanner exactly match items from vendor-provided list. - -If any service is found by port scanner and it is not documented in vendor-provided list, this test case shall fail. It means that vendor-provided list is incorrect and undocumented attack surface exists. - -**Expected format of evidence:** Result of probing the DUT is a list of active network protocols and services. Each item contains network protocol (TCP, UDP, SCTP), port number (from range 0-65535) and service name. If service type cannot be determined during probing, service name is "unknown". - -Service name is in line with Service Name and Transport Protocol Port Number Registry defined by IANA [i.1]. If service name is not defined in [i.1], vendor provided service name is used. - -# 7.3 Password-Based Authentication - -## 7.3.1 Password guessing - -**Requirement Name:** Password-Based Authentication - -**Requirement Reference:** SEC-CTL-PASS-2, clause 5.5.7.2, REQ-SEC-PASS-1, clause 5.3.7.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Password guessing protection mechanism is present on the DUT - -**Threat References:** T-O-RAN-02, T-O-RAN-05, T-O-RAN-06 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_Password\_Guessing - -**Purpose:** To verify that DUT has protection mechanism(s) implemented to prevent password guessing attacks against services using password-based authentication. . Simulation of password guessing attacks against services on DUT provides the information whether any protection mechanism is present. - -This test case is run against all services on DUT that use password-based authentication. Vendor-provided list of all supported network protocols and services are used as a source. - -NOTE 1: Vendor-provided list of all supported network protocols and services may not include the specific information about presence of password-based authentication as it is including network protocol, port and service name. In practice, only subset of services from vendor-provided list will use password-based authentication. - -## Procedure and execution steps - -### Preconditions - -- Valid username for each tested service. This test case does not mandate any specific list of passwords to be used for testing. -- Network access to DUT -- Physical access to DUT (applicable if the DUT is in physical form) -- Vendor-provided list of network protocols and services supported by DUT -- Number of authentication attempts configured in account lock-out policy - -### Execution steps - -- 1) List of services using password-based authentication is determined by analysing the vendor-provided list as well as by analysing local services that are not remotely accessible. -- 2) For services identified in the previous step, presence of protection mechanism is tested as follows: - - combination of valid username and invalid password (or various invalid passwords) are used for authentication repeatedly. - - after certain number of authentication attempts, protection mechanism of DUT are detected. - - minimum number of authentication attempts is the calculated as (number configured in the lock-out policy + 1) attempts. - -### Expected results - -In context of each of the services using password-based authentication, protection mechanism(s) is present. Applicable to local services and to remotely accessible services. - -NOTE 2: In practice, brute-forcing and dictionary attacks are the most common classes of password guessing attacks. Traditional approach to brute-forcing and dictionary attacks uses fixed username with various candidate passwords. Password spraying is another approach that can be combined with brute-forcing and dictionary attacks; fixed password is tested with various candidate usernames. Example of protection mechanism is enforcing delay before next authentication attempt(s) by the same client. This test case cannot list all possible techniques that protection mechanisms can use. However, following list provides overview of the most common approaches: - -- Increase the delay after each unsuccessful authentication attempt. - -- Implement challenge-response authentication (example of such measure: CAPTCHA) -- In order to prevent more attempts, impose temporary lock out on the client when threshold of consecutive failed authentication attempts is reached. During defined period of time all authentication attempts by locked-out client are rejected. - -EXAMPLE: Lock-out policy is configured for 10 invalid authentication attempts. If DUT uses protection mechanism based on delaying authentication attempts, such delay is observed when DUT receives 11th consecutive invalid authentication attempt. - -This test case fails if one or more services using password-based authentication have no protection mechanism present. - -**Expected format of evidence:** Report file, log files and/or screenshots. - -## 7.3.2 Unauthorized Password Reset - -**Requirement Name:** Password-Based Authentication - -**Requirement Reference:** REQ-SEC-PASS-1, clause 5.3.7.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Out-of-band password recovery mechanism absent or deactivated on DUT - -**Threat References:** T-O-RAN-02, T-O-RAN-05, T-O-RAN-06 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_Unauthorized\_Password\_Reset - -**Purpose:** To verify that password reset mechanism DUT cannot be circumvented, disabled, or misused to gain access to DUT, its configuration, and data. Test covers services using password-based authentication and out-of-band mechanisms of password reset present in DUT in physical form. - -### Procedure and execution steps - -#### Preconditions - -- Network access to DUT -- Physical access to DUT (applicable if the DUT is in physical form) -- Vendor-provided list of network protocols and services supported by DUT - -#### Execution steps - -List of services using password-based authentication are determined by analysing the vendor-provided list as well as by analysing local services that are not remotely accessible. - -- 1) For services identified in the previous step, presence of password reset is tested. -- 2) For DUT that has physical form, it verifies that use of hardware factory reset switch or switches results in factory reset. Using any out-of-band mechanism, it is not possible to reset password only. If password reset is required, factory reset of O-RAN architecture element is performed. Factory reset wipes O-RAN architecture element, its configuration and data. - -#### Expected results - -In context of each of the services using password-based authentication, no password change mechanism is present. Applicable to local services and to remotely accessible services. - -This test case fails if one or more services using password-based authentication have password reset mechanism exposed. - -This test case fails if DUT in physical form has hardware switch or switches that can be used to reset password without triggering factory reset of DUT. - -**Expected format of evidence:** Report file, log files and/or screenshots. - -### 7.3.3 Password Policy Enforcement - -**Requirement Name:** Password-Based Authentication - -**Requirement Reference:** REQ-SEC-PASS-1, clause 5.3.7.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Secure password policy is supported and enforced on the DUT - -**Threat References:** T-O-RAN-02, T-O-RAN-03, T-O-RAN-05, T-O-RAN-06 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-Cloud - -**NOTE:** This test case applies only to DUTs that support password-based authentication. If the DUT does not support password-based authentication, this test case shall be marked N/A. - -**Test Name:** TC\_Password\_Policy\_Enforcement - -**Purpose:** To verify that password policy applied for services using password-based authentication is effectively enforced by DUT. - -#### Procedure and execution steps - -##### Preconditions - -- Set of valid username and valid password for each tested service -- Network access to DUT -- Physical access to DUT (applicable if the DUT is in physical form) -- Vendor-provided list of network protocols and services supported by DUT -- Password policy that is actually applied on the DUT - -##### Execution steps - -- 1) List of services using password-based authentication is determined by analyzing the vendor-provided list as well as by analyzing local services that are not remotely accessible. -- 2) For services identified in the previous step, effectiveness of password policy enforcement is verified as follows: - - combination of valid username and valid password are used to authenticate - - password change is performed using password that does not conform to applied password policy - -**EXAMPLE:** DUT uses password policy to set rules for password length, type of characters used (allowed and disallowed characters), complexity (character groups), and denied passwords (deny-list of passwords that cannot be set). Candidate password that does not conform to rules are chosen for this test. As password policy may be complex set of rules, multiple candidate passwords are tested to fully cover possible password policy violations. - -##### Expected results - -In context of each of the services using password-based authentication, applied password policy are effectively enforced and non-compliant passwords are rejected by DUT during password change. Applicable to local services and to remotely accessible services. - -**Expected format of evidence:** Report file, log files and/or screenshots. - -## 7.3.4 Default Password Change - -**Requirement Name:** Default password change support - -**Requirement Reference:** SEC-CTL-PASS-1, clause 5.3.7.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** O-RAN architecture elements with default passwords support password changes. - -**Threat References:** T-O-RAN-01 - -**DUT/s:** SMO, Near-RT RIC, O-CU-CP, O-CU-UP, O-DU, O-RU - -**Test Name:** TC\_Default\_Password\_Change - -**Purpose:** To verify that O-RAN architectural elements with default passwords can successfully have their passwords changed by an authorized user. - -### Procedure and execution steps - -#### Preconditions - -- The default password is in place on the DUT and is active. -- Documentation from the vendor describing the password format and rules (e.g., length, allowed characters, history policy) is available to the tester. -- An authorized user with knowledge of the default password is able to access the DUT's management interface. - -#### Execution steps - -- 3) Log in to the DUT's management interface using the default username and password. -- 4) Navigate to the security settings section. -- 5) Propose a new password conforming to vendor's stated rules (length/charset/history). -- 6) Save the changes. -- 7) Log out of the management interface. -- 8) Log in again using the new password to confirm the change is effective. -- 9) Attempt login with the *old* (default) password and confirm it is rejected. - -#### Expected results - -- The DUT exposes a mechanism to change the default password on at least one supported management interface documented by the vendor. -- Password change to a valid value succeeds and is acknowledged. -- Subsequent authentication with the new password succeeds. -- Authentication with the original default password fails after the change. - -#### Expected format of evidence - -- Log entry showing the initial successful login with the default password. -- Log entry confirming the successful password change. -- Log entry showing the failed login attempt using the old, default password. -- Log entry showing the final successful login using the new password. - -### 7.3.5 Passwords stored as salted - -**Requirement Name:** Passwords stored as salted - -**Requirement Reference:** SEC-CTL-PASS-3, clause 5.3.7.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** User passwords are stored only as salted. - -**Threat References:** T-O-RAN-01, T-O-RAN-08 - -**DUT/s:** O-RU - -**NOTE:** This test case applies to O-RU because it acts as a local authentication server (e.g., for SSH/CLI login) and therefore stores user passwords locally. For other O-RAN architecture elements, this test applies only if they implement local user authentication and store passwords for that purpose. - -**Test Name:** TC\_PASS\_Stored\_Salted - -**Purpose:** Verify that passwords stored locally by the DUT are protected using salted hash functions as specified in O-RAN Security Protocols Specifications [2], clause 5. - -**Preconditions:** - -- The DUT has user authentication enabled. -- A test user account can be created and modified. -- Access to the password storage location (configuration or credential database) is available. - -**NOTE:** If such access is not available, this test case is not applicable. In this case, the tester may review vendor documentation to confirm that passwords are stored as salted hashes with a unique salt per password, and that the implementation aligns with O-RAN SPS [2], clause 5. - -**Execution Steps:** - -1. Create a test user account with a known password. -2. Access the configuration or user database view where credentials are stored. - -**Expected Results:** - -- No password is stored in cleartext. -- The stored value corresponds to a recognized salted-hash format and includes a unique salt. - -EXAMPLE: identify bcrypt \$2b\$, scrypt \$7\$, Argon2 \$argon2id\$, or PBKDF2 formats. - -**Expected Format of Evidence:** - -- Screenshot or extract of credential storage showing salted hash format. - -### 7.3.6 Client secrets stored encrypted - -**Requirement Name:** An O-RAN architecture element acting as a client stores passwords or secrets encrypted - -**Requirement Reference:** SEC-CTL-PASS-4, clause 5.3.7.3, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** An O-RAN architecture element acting as a client stores the passwords or secrets it uses to authenticate to a server, encrypted as specified in O-RAN Security Protocols Specifications [2], clause 5. - -**Threat References:** T-O-RAN-01, T-O-RAN-08 - -**DUT/s:** SMO, Near-RT RIC, O-CU-CP, O-CU-UP, O-DU, O-RU - -**Test Name:** TC\_PASS\_Client\_Secret\_Encryption - -**Purpose:** Verify that client-side secrets (passwords, API keys, tokens) used for server authentication are stored in an encrypted format on the DUT, adhering to the encryption standards in O-RAN Security Protocols Specifications [2], clause 5. - -**Preconditions:** - -- The DUT is configured as a client, has a configured server address and client secret/password. -- Access to the credential storage area is available. - -NOTE: If such access is not available, this test case is not applicable. In this case, the tester may review vendor documentation to confirm that client secrets are stored in encrypted form and that the implementation aligns with O-RAN SPS [2], clause 5. - -**Execution Steps:** - -1. Configure the DUT with a known client secret for authenticating to a target server. -2. Access to the client secrets store. - -**Expected Results:** - -- The client secret is not stored in cleartext. -- The stored value is encrypted in accordance with O-RAN SPS [2], clause 5. - -**Expected Format of Evidence:** - -Screenshot / file extract showing encrypted value. - -## 7.3.7 O-RU Password Policy Enforcement - -**Requirement Name:** O-RU password policy enforcement - -**Requirement Reference:** REQ-SEC-PASS-1, clause 5.3.7.1, O-RAN Security Requirements and Controls Specifications [5], WG4 M-Plane [21], clause 6.4.3.1 - -**Requirement Description:** The O-RU enforces password complexity rules including password length and allowed character sets. - -**Threat References:** T-O-RAN-02, T-O-RAN-03, T-O-RAN-05, T-O-RAN-06 - -**DUT/s:** O-RU - -**Test Name:** TC\_O-RU\_Password\_Format\_Enforcement - -**Purpose:** Verify that the O-RU enforces the required format rules for passwords, including password length and allowed character set. - -## Procedure and execution steps - -### Preconditions - -- The DUT supports managing passwords for local user accounts through NETCONF, CLI, or equivalent. -- A valid PASSWORD-based user account exists. - -### Execution steps - -1. Negative validation (invalid passwords): Change the password of the PASSWORD-based account using: - - A password shorter than 8 characters. - - A password longer than 128 characters. - - A password containing characters outside the allowed set: - - Letters (a-z, A-Z), digits (0-9), and the symbols: ! \$ % ^ ( ) \_ + ~ { } [ ] . -2. Set a password that conforms to the requirements: 8–128 characters, allowed character set. - -### Expected Results - -- Invalid passwords are rejected. -- Valid passwords are accepted. - -### Expected Format of Evidence - -- Logs showing rejection of invalid password updates. -- Logs showing successful password change with valid format. - -## 7.4 Network Protocol Fuzzing - -Fuzzing is an automated process of sending invalid or random inputs to a SUT to cause it to malfunction or crash. - -Fuzzing is effective for finding vulnerabilities because while most modern programs have extensive input fields, the test coverage of these areas is relatively small. Even though this process can be a powerful capability to ensure robustness, it needs to be sufficiently defined and implemented throughout the system development lifecycle to be helpful and achieve the required results in a multi-vendor environment. - -While traditional fuzzing techniques involve fuzzing piece(s) of software and generating inputs through command line or input files, fuzzing telecommunication network protocols tends to be different, requiring sending information via network ports. Furthermore, the complex nature of network protocols in the SUT resulting from how they are layered over each other adds to the challenges of fuzzing such SUTs. - -The following are examples of the protocols that fuzzing will cover; - -| General Transport Protocols | -|-----------------------------| -| SCTP | -| IP | -| TCP | -| UDP | -| SSH | -| HTTP | -| HTTP/2 | - -and - -| O-RAN Specific Protocols | -|--------------------------| -| NETCONF | -| E1AP | -| E2AP | -| A1 | -| CTI | -| eCPRI | -| PTP | - -It is anticipated that many O-RAN architecture elements utilize common software frameworks used for the lower-level general communication. In this case it should be evaluated if these General Transport Protocols are being tested in extensive Fuzzing tests in other activities and can therefore be considered to have lower risk profiles compared to the O-RAN Specific Protocols with less testing in the general industry. - -Many of the O-RAN specific protocols are state- machine based protocols that can have multiple end points served at the same time, e.g. the protocol needs to be tested in scale to understand if possible memory leaks or other similar aspects is available that could lead to buffer overflows (opening up for possible code execution) or software crashes of the O-RAN specific software. - -Fuzzing on the M-Plane protocol inside the Configuration of the O-RAN Fronthaul can be a possible significant area as this is combining multiple technologies from many domains into a single solution. In order for the Fuzzing to be time and resource efficient, it is important that this Fuzzing is protocol and state machine aware so that the Fuzzing can focus - -on the relevant aspects of the SUT representing the most significant risk exposure. Further effectiveness can be achieved if the Fuzzing capability is able to intelligently respond to the SUT behaviour. The Fuzzing tool should be able to both perform test with and without access to relevant credentials. Many possible vulnerabilities would be present on the inside of the authenticated session of the management protocols and would lead to escalation of privileges. - -In order to identify the possible risk for memory leaks, Denial of Service (DoS) or other similar aspects a robust logging of the underlying platform (hardware and software), the virtualization or container platform and the O-RAN function, the logging needs to be detailed enough to evaluate the trends early but not intrusive to degrade the performance of the platform and lead to inaccurate results. - -As general guidance, vendors and operators running fuzzing tests aim to document the list of all of the protocols of the SUTs reachable externally on an IP-based interface, together with indications of whether adequate available robustness and fuzz testing tools have been used against them. The tool's name, their unambiguous version (also for plug-ins if applicable), user settings, and the relevant output evidenced and should be documented. Additionally, any input causing unspecified, undocumented, or unexpected behaviour and a description of this behaviour should be highlighted in the testing documentation. - -Since fuzzing test cases are not exhaustive and difficult to define and replicate, it's likely that test results even from testing the same set of protocols by different vendors may end up resulting in different outputs. So further effort and time needs to be invested in fuzzing activities until a satisfactory approach based on the vendor's or/and operators adopted risk-based model is satisfied. - -## 7.5 Denial of Service/Message Flooding - -### 7.5.1 Protocol, Application and Volumetric Based DDoS Attacks - -**Requirement Name:** Robustness against DoS/Volumetric DDoS Attacks - -**Requirement Reference:** REQ-SEC-DOS-1, clause 5.3.5.1, REQ-SEC-NEAR-RT-6, REQ-SEC-NEAR-RT-7, REQ-SEC-NEAR-RT-8, REQ-SEC-NEAR-RT-9, clause 5.1.3.1, REQ-SEC-NonRTRIC-4, REQ-SEC-NonRTRIC-5, REQ-SEC-NonRTRIC-6, clause 5.1.2.1, REQ-SEC-SMO-5, REQ-SEC-SMO-6, REQ-SEC-SMO-7, 5.1.1.1.1, REQ-SEC-SharedORU-7, clause 5.1.9.1, REQ-SEC-NFO-FOCOM-6, REQ-SEC-NFO-FOCOM-7, clause 5.1.1.1.5, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** An O-RAN architecture element with a network interface has ability to withstand network transport protocol based volumetric DoS/DDoS attacks without system crash and return to normal service level after the attack - -**Threat References:** T-O-RAN-03, T-O-RAN-04, T-O-RAN-09, T-SMO-03 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_Robustness\_DDoS - -**Purpose:** To evaluate the resilience of the DUT against DoS/DDoS attacks and its recovery capabilities. - -Each DUT interface is tested to validate its handling of large numbers of requests, similar to what is seen from denial of service (DoS) or/and distributed denial of service (DDoS) attempts. DoS/DDoS scenario can occur as a result of malicious attack or because of network/operator error. DoS/DDoS attacks can be in these forms: protocol layer attacks (e.g. SYN Floods, UDP Floods, TCP Floods), volume based attacks (e.g. ICMP floods, Smurf DDoS) and application layer attacks (e.g. GET/POST floods, low-and-slow attacks, attacks that target specific software/application with exposed network services or operating system network services). - -Verify that the O-RAN Architecture element/Application: - -- - has a detailed technical description of the overload control mechanisms used to deal with overload scenarios. -- - has a test report verifying the operation of the overload control mechanisms. - -#### Procedure and execution steps - -### Preconditions - -- A document that provides a detailed technical description of the overload control mechanisms. -- A test report from the test execution phase of overload control mechanism testing. - -### Execution steps - -- 1) The tester verifies that the technical description document contains: - - Various overload scenarios that the DUT's (or the O-RAN Architecture element/Application) are expected to handle. This includes for example: - - Traffic overload - - Resource overload - - Service overload - - Various overload control thresholds that the DUT uses to trigger overload control mechanisms. This includes for example: - - CPU usage limit - - Memory usage limit - - Request rate limit - - Description of the types of attacks that can cause overload conditions. This includes for example: - - Denial of Service (DoS) - - Distributed Denial of Service (DDoS) - - Resource Exhaustion - - A description of how the DUT's security functions operate and perform corrective actions under excessive overload conditions. i.e. when the overload is significantly greater than the defined overload thresholds. -- 2) The tester verifies that a detailed test report: - - Contain details of the test setup including the mechanisms for creating the overload scenarios that are consistent with the technical description document, where simulators and/or scripts are used to artificially create a load, then details of these should also be included. - - Describe test procedures used to verify the overload control mechanisms. - - Contain logs capturing all relevant events, which demonstrate/indicate that the detection of overload conditions and the triggering of overload control mechanisms described in the technical description document have been implemented. - -### Expected results - -The technical description document and test report contain: - -- An overview of the types of overload scenarios that are considered. -- An overview of the determined specific thresholds that triggered overload control mechanisms. -- A description of the types of attacks that cause overload conditions to the system and how these are handled. -- A description of how the DUT demonstrated the ability to discard excess requests gracefully while continuing to process valid request during overload situations. - -- A description of how the DUT security functions remain operational and perform corrective actions under excessive overload situations. This includes system shutdowns, abatements and other corrective actions - -NOTE: The vendor provides an explanation for any of the items listed above that they consider not applicable to their architecture element/application. - -**Expected format of evidence:** Documentation showing each of the points in the results sections. - -## 7.5.2 Void - -## 7.5.3 Void - -## 7.5.4 Void - -## 7.5.5 Near-RT RIC A1 interface DoS/DDoS protection and recovery - -Refer to test case 7.5.1 for the test verification - -# 7.6 Input validation and error handling - -## 7.6.1 O-CU input validation and error handling - -**Requirement Name:** Input validation and error handling on data provided through E2 and O1 interfaces. - -**Requirement Reference:** REQ-SEC-TRAN-1, clause 5.3.4.1 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** O-CU performs input validation on data provided via E2 and O1 interfaces and rejects invalid or malicious inputs. - -**Threat References:** T-O-RAN-05 - -**DUT/s:** O-CU - -**Test Name:** TC\_INPUT\_VALIDATION\_ERR\_HANDL\_OCU - -**Purpose:** The purpose of this test is to verify that the O-CU performs proper input validation on provided data via E2 and O1 interfaces and rejects invalid or malicious inputs. It verifies that the O-CU correctly handles errors and responds appropriately. - -### Procedure and execution steps - -#### Preconditions: - -- The O-CU is powered on and operational. -- Test environment is set up with E2 and O1 interfaces configured. -- Input validation mechanisms are implemented on O-CU. -- Error handling mechanisms (e.g., error codes, error messages) are implemented by O-CU. - -#### Execution steps: - -- 1) Case of malformed input data - - The tester provides invalid or malformed input data to the O-CU via E2 and O1 interfaces, violating the specified format or containing unexpected values. - - The tester captures and analyses the response from the E2 and O1 interfaces. - -- The tester verifies that the O-CU detects the invalid input and rejects it appropriately, returning an error message or taking necessary actions to mitigate the impact. - -EXAMPLE: Actions could be rejecting the message, sending an error indication, etc. - -2) Case of malicious input data - -- The tester provides malicious input data to the O-CU via E2 and O1 interfaces, aiming to exploit known vulnerabilities (e.g., CVE database, OWASP Top Ten, NIST National Vulnerability Database (NVD), vendor-specific vulnerability database). If exploitation is successful, the tester performs unauthorized actions. -- The tester verifies that the O-CU identifies the malicious input and implements security measures to prevent exploitation, such as input sanitization, access controls, or anomaly detection. - -3) Boundary case - -- Provide input data at the boundaries of the allowed range or limits defined for specific inputs. -- Verify that the O-CU handles the boundary cases correctly, without encountering any unexpected behaviour or errors due to boundary conditions. - -**Expected Results:** - -For case 'malformed input data', the O-CU properly validates incoming inputs from E2 and O1 interfaces and rejects those with invalid or malformed data, returning an appropriate error response and preventing any potential security risks or system failures. - -For case 'malicious input data', the O-CU detects and mitigates the malicious input, preventing any potential security breaches or unauthorized operations. - -For case 'boundary', the O-CU properly handles the boundary cases, ensuring that inputs at the limits are processed accurately without causing any system instability or vulnerabilities. - -**Expected format of evidence:** - -Logs detailing the invalid or malformed input data provided to the O-CU via E2 and O1 interfaces, alongside system logs capturing the O-CU's error messages or indications in response to the invalid input. - -Logs documenting the malicious input data sent to the O-CU and the targeted vulnerabilities, complemented by system logs highlighting the O-CU's detection and mitigation actions upon receiving the malicious input. - -Logs of the boundary input data values provided to the O-CU, paired with system logs capturing the O-CU's messages or behaviours in response to the boundary inputs. - -## 7.6.2 O-DU input validation and error handling - -**Requirement Name:** Input validation and error handling on data provided through E2, Open FH and O1 interfaces. - -**Requirement Reference:** REQ-SEC-TRAN-1, clause 5.3.4.1 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** O-DU performs input validation on data provided via E2, Open FH and O1 interfaces and rejects invalid or malicious inputs. - -**Threat References:** T-O-RAN-05 - -**DUT/s:** O-DU - -**Test Name:** TC\_INPUT\_VALIDATION\_ERR\_HANDL\_ODU - -**Purpose:** The purpose of this test is to verify that the O-DU performs proper input validation on provided data via E2, Open FH and O1 interfaces and rejects invalid or malicious inputs. It verifies that the O-DU correctly handles errors and responds appropriately. - -## Procedure and execution steps - -### Preconditions: - -- The O-DU is powered on and operational. -- Test environment is set up with E2, Open FH and O1 interfaces configured. -- Input validation mechanisms are implemented on O-DU. -- Error handling mechanisms (e.g., error codes, error messages) are implemented by O-DU. - -### Execution steps: - -- 1) Case of malformed input data - - The tester provides invalid or malformed input data to the O-DU via E2, Open FH and O1 interfaces, violating the specified format or containing unexpected values. - - The tester captures and analyses the response from the E2, Open FH and O1 interfaces. - - The tester verifies that the O-DU detects the invalid input and rejects it appropriately, returning an error message or taking necessary actions to mitigate the impact. - -EXAMPLE: Actions could be rejecting the message, sending an error indication, etc. - -- 2) Case of malicious input data - - The tester provides malicious input data to the O-DU via E2, Open FH and O1 interfaces, aiming to exploit known vulnerabilities (e.g., CVE database, OWASP Top Ten, NIST National Vulnerability Database (NVD), vendor-specific vulnerability database). If exploitation is successful, the tester performs unauthorized actions. - - The tester verifies that the O-DU identifies the malicious input and implements security measures to prevent exploitation, such as input sanitization, access controls, or anomaly detection. -- 3) Boundary case - - Provide input data at the boundaries of the allowed range or limits defined for specific inputs. - - Verify that the O-DU handles the boundary cases correctly, without encountering any unexpected behaviour or errors due to boundary conditions. - -### Expected Results: - -For case 'malformed input data', the O-DU properly validates incoming inputs from E2, Open FH and O1 interfaces and rejects those with invalid or malformed data, returning an appropriate error response and preventing any potential security risks or system failures. - -For case 'malicious input data', the O-DU detects and mitigates the malicious input, preventing any potential security breaches or unauthorized operations. - -For case 'boundary', the O-DU properly handles the boundary cases, ensuring that inputs at the limits are processed accurately without causing any system instability or vulnerabilities. - -### Expected format of evidence: - -Logs detailing the invalid or malformed input data provided to the O-DU via E2, Open FH and O1 interfaces, alongside system logs capturing the O-DU's error messages or indications in response to the invalid input. - -Logs documenting the malicious input data sent to the O-DU and the targeted vulnerabilities, complemented by system logs highlighting the O-DU's detection and mitigation actions upon receiving the malicious input. - -Logs of the boundary input data values provided to the O-DU, paired with system logs capturing the O-DU's messages or behaviours in response to the boundary inputs. - -## 7.6.3 Near-RT RIC input validation and error handling - -**Requirement Name:** Error handling by Near-RT RIC - -**Requirement Reference:** REQ-SEC-NEAR-RT-7, REQ-SEC-NEAR-RT-8, REQ-SEC-NEAR-RT-9, clause 5.1.3.1 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Near-RT RIC performs input validation on data provided via A1, E2 and Y1 interfaces and rejects invalid or malicious inputs. - -**Threat References:** T-NEAR-RT-03, T-NEAR-RT-04 - -**DUT/s:** NEAR-RT RIC - -**Test Name:** TC\_INPUT\_VALIDATION\_ERR\_HANDL\_NEAR\_RT\_RIC - -**Purpose:** The purpose of this test is to verify that the Near-RT RIC performs proper input validation on provided data via A1, E2 and Y1 interfaces and rejects invalid or malicious inputs. It verifies that the Near-RT RIC correctly handles errors and responds appropriately. - -### Procedure and execution steps - -#### Preconditions - -- Near-RT RIC is powered and operational. -- Test environment is set up with A1, E2 and Y1 interfaces configured. -- Input validation mechanisms are implemented on Near-RT RIC. -- Error handling mechanisms (e.g., error codes, error messages) are implemented by Near-RT RIC. - -#### Execution steps: - -- 1) Case of malformed input data - - The tester provides invalid or malformed input data to the Near-RT RIC via A1, E2 and Y1 interfaces, violating the specified format or containing unexpected values. - - The tester captures and analyses the response from the A1, E2 and Y1 interfaces. - - The tester verifies that the Near-RT RIC detects the invalid input and rejects it appropriately, returning an error message or taking necessary actions to mitigate the impact. - -EXAMPLE: Actions could be rejecting the message, sending an error indication, etc. - -- 2) Case of malicious input data - - The tester provides malicious input data to the Near-RT RIC via A1, E2 and Y1 interfaces, aiming to exploit known vulnerabilities (e.g., CVE database, OWASP Top Ten, NIST National Vulnerability Database (NVD), vendor-specific vulnerability database). If exploitation is successful, the tester performs unauthorized actions. - - The tester verifies that the Near-RT RIC identifies the malicious input and implements security measures to prevent exploitation, such as input sanitization, access controls, or anomaly detection. -- 3) Boundary case - - Provide input data at the boundaries of the allowed range or limits defined for specific inputs. - - Verify that the Near-RT RIC handles the boundary cases correctly, without encountering any unexpected behaviour or errors due to boundary conditions. - -### Expected Results - -For case 'malformed input data', the Near-RT RIC properly validates incoming inputs from A1, E2 and Y1 interfaces and rejects those with invalid or malformed data, returning an appropriate error response and preventing any potential security risks or system failures. - -For case 'malicious input data', the Near-RT RIC detects and mitigates the malicious input, preventing any potential security breaches or unauthorized operations. - -For case 'boundary', the Near-RT RIC properly handles the boundary cases, ensuring that inputs at the limits are processed accurately without causing any system instability or vulnerabilities. - -#### **Expected format of evidence:** - -Logs detailing the invalid or malformed input data provided to the Near-RT RIC via A1, E2 and Y1 interfaces, alongside system logs capturing the Near-RT RIC's error messages or indications in response to the invalid input. - -Logs documenting the malicious input data sent to the Near-RT RIC and the targeted vulnerabilities, complemented by system logs highlighting the Near-RT RIC's detection and mitigation actions upon receiving the malicious input. - -Logs of the boundary input data values provided to the Near-RT RIC, paired with system logs capturing the Near-RT RIC's messages or behaviours in response to the boundary inputs. - -### **7.6.4 Near-RT RIC input validation and error handling of data received from xApp** - -**Requirement Name:** Error handling by Near-RT RIC - -**Requirement Reference:** SEC-CTL-NEAR-RT-18, clause 5.1.3.2.5 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The Near-RT RIC shall verify data received through E2 related APIs initiated by xApp as follows: the data values are valid; the Near-RT RIC shall log security event(s) if any of the verification steps fail. - -**Threat References:** T-NEAR-RT-03, T-NEAR-RT-04 - -**DUT/s:** NEAR-RT RIC - -**Test Name:** TC\_E2API\_INPUT\_VALIDATION\_ERR\_HANDL\_NEAR\_RT\_RIC\_XAPP - -**Purpose:** The purpose of this test is to verify that the Near-RT RIC performs proper input validation on received data from xApp through E2 related APIs and rejects malformed inputs. It verifies that the Near-RT RIC correctly handles errors and responds appropriately. - -#### **Procedure and execution steps** - -##### **Preconditions:** - -- Near-RT RIC is deployed. -- A testing software that supports communication with Near-RT RIC over E2 related APIs [27]. -- Error handling mechanisms are implemented by Near-RT RIC. - -EXAMPLE 1: E2 Error or Failure message with Cause as defined in clause 9.2.1 of [28]. - -##### **Execution Steps:** - -- 1) Malformed input data - - Provide malformed input data to the Near-RT RIC via E2 related APIs, violating the specified format. -- EXAMPLE 2: Input data containing unknown IEs, incorrect format and mandatory IEs not present. -- Capture and analyse the response from Near-RT RIC via E2 related APIs. - -- Verify that the Near-RT RIC detects the malformed input and rejects it appropriately, returning an error message or taking necessary actions to mitigate the impact. - -EXAMPLE 3: Actions could be rejecting the message, sending an error rejection or failure indication, etc. - -2) Valid and Invalid boundary cases - -- Provide invalid (wrong value) data outside of the boundaries or limits of the acceptable values or ranges defined for specific parameters in clause 5.2.2 & 5.2.3, O-RAN E2 Interface Test Specification [29] for E2 related APIs. -- Provide valid data at the boundaries or inside the allowed ranges defined for specific parameters in clause 5.2.2 & 5.2.3, O-RAN E2 Interface Test Specification [29] for E2 related APIs. -- Verify that the Near-RT RIC handles these boundary cases correctly, without encountering any unexpected behaviour or errors due to boundary conditions. - -**Expected Results:** - -1) Malformed input data - -- The Near-RT RIC properly validates incoming inputs via E2 related APIs from xApp and rejects those with malformed data, returning an appropriate error response. - -2) Valid and Invalid boundary cases - -- The Near-RT RIC properly handles the valid and invalid boundary cases. - -**Expected format of evidence:** - -1) Malformed input data - -- Logs detailing the malformed input data provided to the Near-RT RIC via E2 related APIs, alongside system logs capturing the Near-RT RIC's error messages. - -2) Valid and Invalid boundary cases - -- Logs of the input data values provided to the Near-RT RIC, paired with system logs capturing the Near-RT RIC 's messages or behaviours in response to the boundary inputs. - -## 7.7 Secure configuration enforcement - -**Requirement Name:** Configuration security enforcement - -**Requirement Reference:** SEC-CTL-OCU-1, clause 5.1.4.2, SEC-CTL-ODU-1, clause 5.1.5.2, ,REQ-SEC-ORU-1, clause 5.1.6.1 in O-RAN Security Requirements and Controls Specifications [5], 3GPP TS 33.501 clause 5.3.4 [25] - -**Requirement Description:** The DUT ensures that settings and software configurations are protected from unauthorized modifications. - -**Threat Reference:** T-O-RAN-02 - -**DUT/s:** O-CU, O-DU, O-RU - -**Test Name:** TC\_CONF\_ENFORCEMENT - -**Purpose:** Ensure the DUT prevents unauthorized settings and software configurations changes, as required by 3GPP TS 33.501 clause 5.3.4 [25]. - -**Procedure and execution steps** - -**Preconditions:** - -- The DUT is powered on and operational. - -- Settings and software configurations are defined and applied on the DUT. -- Successful access to the DUT is established. - -**Execution steps:** - -- 1) Attempt to modify the DUT settings and software configurations with proper authorization. -- 2) Verify that the DUT detects and accepts any authorized modification attempts. -- 3) Attempt to modify the DUT settings and software configurations without proper authorization. -- 4) Verify that the DUT detects and rejects any unauthorized modification attempts. - -**Expected results:** - -- DUT accepts authorized modifications. -- DUT detects and rejects any unauthorized modifications. - -**Expected format of evidence:** - -- Logs indicating the detection and acceptance of authorized modifications. -- Logs indicating the detection and rejection of unauthorized modifications. - -EXAMPLE: examples of settings and software configurations include: - -- Security configuration: e.g., protocols and keys used for authentication, authorization, and secure communication. -- Software management: e.g., current software version -- Interface settings - -## 7.8 Logging and monitoring - -### 7.8.1 O-CU logging and monitoring - -**Requirement Name:** O-CU logging and monitoring - -**Requirement Reference:** REQ-SEC-OCU-1, clause 5.1.4.1 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Logging and monitoring of security-related events by the O-CU - -**Threat References:** T-O-RAN-07 - -**DUT/s:** O-CU - -**Test Name:** TC\_LOG\_OCU - -**Purpose:** The purpose of this test is to verify that the O-CU correctly logs and monitors security-related events effectively. - -**Procedure and execution steps****Preconditions** - -- The O-CU is powered on and operational. -- Logging and monitoring configurations are properly set up on the O-CU. - -**Execution steps** - -#### 1) Logging - -- The tester triggers an error or failure condition in the O-CU, such as connection attempts with invalid credentials, unauthorized access and a dropped connection. -- The tester verifies that the O-CU logs the error by capturing the relevant log entry. - -#### 2) Monitoring - -- The tester monitors the key performance indicators (KPIs) of the O-CU, such as throughput, latency, or signal quality. -- The tester verifies that the monitoring system accurately collects and displays the KPI values in real-time. -- The tester introduces a simulated degradation or overload scenario on the O-CU, such as increasing network traffic or reducing available resources. -- The tester monitors the O-CU performance under the simulated scenario. -- The tester verifies that the monitoring system detects and raises alerts for the degraded performance or overload condition. - -### Expected Results - -- O-CU logs and generates alerts for security-related events, providing necessary information and timestamps for incident investigation and analysis. -- The monitoring system provides accurate and real-time KPI values for the O-CU. The monitoring system detects and raises appropriate alerts for the degraded performance or overload condition. - -### Expected format of evidence: - -- Capture and analyse the logged error in the O-CU logs or logging system and document the presence of the log entry. -- Document the monitored KPI values and the raised alerts, validate them against the expected values, and ensure they are triggered accurately in the monitoring system. - -## 7.8.2 O-DU logging and monitoring - -**Requirement Name:** O-DU logging and monitoring - -**Requirement Reference:** REQ-SEC-ODU-1, clause 5.1.5.1 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Logging and monitoring of security-related events by the O-DU - -**Threat References:** T-O-RAN-07 - -**DUT/s:** O-DU - -**Test Name:** TC\_LOG\_ODU - -**Purpose:** The purpose of this test is to ensure that the O-DU correctly logs and monitors security-related events effectively. - -### Procedure and execution steps - -#### Preconditions - -- The O-DU is powered on and operational. -- Logging and monitoring configurations are properly set up on the O-DU. - -### Execution steps - -- 1) Logging - - The tester triggers an error or failure condition in the O-DU, such as connection attempts with invalid credentials, unauthorized access and a dropped connection. - - The tester verifies that the O-DU logs the error by capturing the relevant log entry. -- 2) Monitoring - - The tester monitors the key performance indicators (KPIs) of the O-DU, such as throughput, latency, or signal quality. - - The tester verifies that the monitoring system accurately collects and displays the KPI values in real-time. - - The tester introduces a simulated degradation or overload scenario on the O-DU, such as increasing network traffic or reducing available resources. - - The tester monitors the O-DU performance under the simulated scenario. - - The tester verifies that the monitoring system detects and raises alerts for the degraded performance or overload condition. - -### Expected Results - -- O-DU logs and generates alerts for security-related events, providing necessary information and timestamps for incident investigation and analysis. -- The monitoring system provides accurate and real-time KPI values for the O-DU. The monitoring system detects and raises appropriate alerts for the degraded performance or overload condition. - -### Expected format of evidence: - -- Capture and analyse the logged error in the O-DU logs or logging system and document the presence of the log entry. -- Document the monitored KPI values and the raised alerts, validate them against the expected values, and ensure they are triggered accurately in the monitoring system. - -## 7.8.3 O-RU logging and monitoring - -**Requirement Name:** O-RU logging and monitoring - -**Requirement Reference:** REQ-SEC-ORU-1, REQ-SEC-ORU-2, clause 5.1.6.1 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Logging and monitoring of security-related events by the O-RU - -**Threat References:** T-O-RAN-07 - -**DUT/s:** O-RU - -**Test Name:** TC\_LOG\_ORU - -**Purpose:** The purpose of this test is to ensure that the O-RU correctly logs and monitors security-related events effectively. - -### Procedure and execution steps - -#### Preconditions - -- The O-RU is powered on and operational. - -- Logging and monitoring configurations are properly set up on the O-RU. - -#### Execution steps - -- 1) Logging - - The tester triggers an error or failure condition in the O-RU, such as connection attempts with invalid credentials, unauthorized access and a dropped connection. - - The tester verifies that the O-RU logs the error by capturing the relevant log entry. -- 2) Monitoring - - The tester monitors the key performance indicators (KPIs) of the O-RU, such as throughput, latency, or signal quality. - - The tester verifies that the monitoring system accurately collects and displays the KPI values in real-time. - - The tester introduces a simulated degradation or overload scenario on the O-RU, such as increasing network traffic or reducing available resources. - - The tester monitors the O-RU performance under the simulated scenario. - - The tester verifies that the monitoring system detects and raises alerts for the degraded performance or overload condition. - -#### Expected Results - -- O-RU logs and generates alerts for security-related events, providing necessary information and timestamps for incident investigation and analysis. -- The monitoring system provides accurate and real-time KPI values for the O-RU. The monitoring system detects and raises appropriate alerts for the degraded performance or overload condition. - -#### Expected format of evidence: - -- Capture and analyse the logged error in the O-RU logs or logging system and document the presence of the log entry. -- Document the monitored KPI values and the raised alerts, validate them against the expected values, and ensure they are triggered accurately in the monitoring system. - -### 7.8.4 Near-RT RIC logging and monitoring - -**Requirement Name:** Near-RT RIC logging and monitoring - -**Requirement Reference:** REQ-SEC-NEAR-RT-4, clause 5.1.3.1 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Logging and monitoring of security-related events by the Near-RT RIC - -**Threat References:** T-O-RAN-07 - -**DUT/s:** NEAR-RT RIC - -**Test Name:** TC\_LOG\_NEAR\_RT\_RIC - -**Purpose:** The purpose of this test is to ensure that the Near-RT RIC correctly logs and monitors security-related events effectively. - -**Procedure and execution steps** - -**Preconditions** - -- The Near-RT RIC is powered on and operational. -- Logging and monitoring configurations are properly set up on the Near-RT RIC. - -#### Execution steps - -- 1) Logging - - The tester triggers an error or failure condition in the Near-RT RIC, such as connection attempts with invalid credentials, unauthorized access, or a dropped connection. - - The tester verifies that the Near-RT RIC logs the error by capturing the relevant log entry. -- 2) Monitoring - - The tester monitors the key performance indicators (KPIs) of the Near-RT RIC, such as throughput, latency, or signal quality. - - The tester verifies that the monitoring system accurately collects and displays the KPI values in real-time. - - The tester introduces a simulated degradation or overload scenario on the Near-RT RIC, such as increasing network traffic or reducing available resources. - - The tester monitors the Near-RT RIC performance under the simulated scenario. - - The tester verifies that the monitoring system detects and raises alerts for the degraded performance or overload condition. - -#### Expected Results - -- Near-RT RIC logs and generates alerts for security-related events, providing necessary information and timestamps for incident investigation and analysis. -- The monitoring system provides accurate and real-time KPI values for the Near-RT RIC. The monitoring system detects and raises appropriate alerts for degraded performance or overload conditions. - -#### Expected format of evidence: - -- Capture and analyse the logged error in the Near-RT RIC logs or logging system and document the presence of the log entry. -- Document the monitored KPI values and the raised alerts, validate them against the expected values, and ensure they are triggered accurately in the monitoring system. - ---- - -## 8 System security evaluation for O-RAN architecture elements - -### 8.1 Overview - -This clause contains security evaluations to be performed at the system level of an O-RAN architecture element, covering vulnerability scanning, data and information protection and system logging. - -The objects in scope of these system security evaluation are SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU and O-Cloud. - -## 8.2 System Vulnerability Scanning - -### 8.2.1 System Vulnerability Scanning - -**Requirement Name:** Robustness of OS and Applications - -**Requirement Reference:** REQ-SEC-SYS-1, clause 5.3.6.1, REQ-SEC-ALM-PKG-1, clause 5.3.2.1.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Operating System (OS) and applications vulnerability scan of DUT - -**Threat References:** T-O-RAN-01 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_Vulnerability\_Scanning - -**Purpose:** To verify the DUT does not contain known vulnerabilities in the OS and applications. Perform vulnerability scanning to ensure that there are no known vulnerabilities on DUT, both in the Operating System(OS) and the applications installed, that can be detected by means of automatic testing tools via the IP enabled network interfaces, or to identify the known vulnerabilities on DUT and have a clear mitigation plan for the ones of high severity. - -Known vulnerabilities are considered those which are publicly disclosed, found by users or reported by security researchers. Those vulnerabilities are widely detected by commercial, or open-source tools designed for this purpose. - -#### Procedure and execution steps - -##### Preconditions - -DUT is the O-RAN architecture element with IP enabled network interfaces. - -##### Execution steps - -- 1) Run the vulnerability scanning tool and check the potential known vulnerabilities existing on OS and applications levels. -- 2) Evaluate the severity level of the existing vulnerabilities. - -##### Expected results - -The DUT is free from known vulnerabilities or there are security controls in place to mitigate the exploits associated with the vulnerabilities of high severity. - -**Expected format of evidence:** Report files, log files and/or screenshots. - -## 8.3 Data and Information Protection - -Void - -## 8.4 System logging - -### 8.4.1 Introduction - -This clause contains test cases related to security log management. - -### 8.4.2 Security log format and related log fields - -**Requirement Name:** Security logs check for date, time and location field IP address. - -**Requirement Reference:** SEC-CTL-SLM-FLD-1, SEC-CTL-SLM-FLD-2, clause 5.3.8.8.3, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Support for security logs containing date, time and location field IP address. - -**Threat References:** T-O-RAN-07 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_Logs\_Datetime\_Fields\_Validation - -**Purpose:** To verify the log fields of security log data from DUT as per clause 5.3.8.8 of Security Requirements and Controls specifications [5]. The security log has the recommended date and time in ISO 8601 [10] format and mandatorily log the location field IP address (IP address of the host from which security events are generated). - -#### Procedure and execution steps - -##### Preconditions - -DUT is any O-RAN architecture element that creates/generates security event logs. - -Client is the test system equipped to communicate securely with O-RAN architecture element and able to perform security related operations on DUT. - -Vendor documents operation(s) which generate security logs. - -##### Execution steps - -Execute one valid operation on the DUT which triggers/generates the security logs. - -##### Expected results - -- Date and time format as per ISO 8601 [10] as recommended by clause 5.3.8.8.3 of [5] -- Location field IP address (IP address of the DUT) as mandated by clause 5.3.8.8.3 of [5] - -**Expected format of evidence:** Log files containing the output of the steps executed. In case the logs do not show the required information, report of a tool is used. - -### 8.4.3 Authenticated Time Stamping - -**Requirement Name:** Authenticated Time-Stamping - -**Requirement Reference:** SEC-CTL-SLM-ATS-1, SEC-CTL-SLM-ATS-2, SEC-CTL-SLM-ATS-3, clause 5.3.8.9.2.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Optional support NTPv4 - -**Threat References:** T-O-RAN-07 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-Cloud - -**NOTE:** This test case applies only if the DUT supports NTPv4 for authenticated time stamping of logs. O-DU and O-CU use PTP/SyncE for radio synchronization and may not implement NTP for logging purposes. If the DUT does not support NTPv4 in the client role for log timestamping, this test case is not applicable. - -**Test Name:** TC\_Logs\_Authenticated\_Time\_Stamping - -**Purpose:** To verify that the DUT fulfills the optional requirement of supporting Network Time Protocol (NTP) version 4 as specified by RFC 5905 [15] for authenticated time stamping in the client role only. - -#### Procedure and execution steps - -##### Preconditions - -- The DUT is powered on and operational. -- The NTP server specified for testing is reachable and configured to support authenticated time stamping. - -### Execution steps - -Verify NTP Client Version: - -- Access the DUT configuration settings related to NTP. -- Confirm that the DUT specifies NTP version 4 as the selected protocol. - -Authentication Setup - -- Configure the DUT to use the necessary authentication methods and -credentials (AES-CMAC/RFC 4493 [17], certificates for Autokey/RFC 5906 [16]) required by RFC 5905 for authenticated time stamping. -- Provide valid authentication credentials (certificates) for NTP communication. - -Time Synchronization - -- Initiate an NTP time synchronization process from the DUT to the specified NTP server. -- Monitor the communication between the DUT and the NTP server to ensure that the NTP packets are properly constructed with the required authentication parameters. -- Verify that the DUT successfully receives the authenticated time stamps from the NTP server. - -Time Accuracy Check - -- After synchronization, record the DUT internal clock time. -- Obtain the time from the NTP server's authenticated time stamp. -- Calculate the time difference between the DUT internal clock time and the received authenticated time stamp. -- Ensure that the time difference is within an acceptable tolerance, considering network latency and authentication processing. - -### Expected results - -The DUT fulfils the requirement of supporting Network Time Protocol (NTP) version 4 for authenticated time stamping, as specified by RFC 5905. The NTP communication successfully employs the configured authentication methods, and the time synchronization process ensures accurate timekeeping within the specified tolerance. An accuracy below 1 second should be measured to pass. - -**Expected format of evidence:** Log files, traffic captures and/or screenshots. - -## 8.4.4 Network Security and System Security Events - -**Requirement Name:** Network Security Events to be Logged and System Security Events to be Logged. - -**Requirement Reference:** REQ-SEC-SLM-NET-EVT-1, clause 5.3.8.11.2, REQ-SEC-SLM-GEN-EVT-1, REQ-SEC-SLM-GEN-EVT-2, REQ-SEC-SLM-GEN-EVT-3, clause 5.3.8.11.3.1.1, REQ-SEC-SLM-HYP-EVT-1, REQ-SEC-SLM-HYP-EVT-2, REQ-SEC-SLM-HYP-EVT-3, clause 5.3.8.11.3.2, REQ-SEC-SLM-CON-EVT-1, REQ-SEC-SLM-CON-EVT-2, REQ-SEC-SLM-CON-EVT-3, clause 5.3.8.11.3.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Logging of network and system security events in O-Cloud - -**Threat References:** T-O-RAN-01, T-O-RAN-02, T-O-RAN-03, T-O-RAN-09, T-VM-C-01, T-VM-C-02, T-VM-C-03, T-VM-C-04, T-VM-C-05, T-VM-C-06, T-IMG-01, T-IMG-02, T-ADMIN-02 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_Logs\_Network\_System\_Security\_Events - -**Purpose:** The purpose of the test is to verify the logging of security events from O-Cloud as per the Security Requirements and Controls Specifications [5]. - -#### **Procedure and execution steps** - -##### **Preconditions** - -A tester has access to testing equipment that can connect to the O-Cloud with administrative privileges to the operating system, hypervisor, and container engine. - -##### **Execution steps** - -- 1) Login to the DUT via testing equipment with administrative credentials. -- 2) Execute the following operations on the DUT. - - a) Create a new network configuration. - - b) Modify an existing network configuration. - - c) Disable a port. - - d) Enable a port. - - e) Generate packets that exceed configured firewall limits. - - f) Generate at least one network connection. - - g) Reboot a virtual machine and then reboot the host operating system. - - h) Shutdown a virtual machine then shutdown the host operating system. - - i) Create a scheduled job within the host operating systems, hypervisor, and container engine. - - j) Make a configuration change to the host operating system and hypervisor. - - k) Attach and detach a virtual disk to a virtual machine. - - l) Create a virtual machine. - - m) Start a virtual machine. - - n) Stop a virtual machine. - - o) Delete a virtual machine. - - p) Add an image to the container repository. - - q) Modify an image to the container repository. - - r) Remove an image to the container repository. - - s) Create a container. - - t) Start a container. - - u) Stop a container. - - v) Restart a container. - - w) Delete a container. - - x) Create a container volume. - - y) Mount a container volume. - -- z) Delete a container volume. - -### Expected results - -All the security logs produced by O-Cloud contain log messages that describe the actions taken in the execution steps. - -- For execution step 2.a the log message indicates the creation of a new network configuration. -- For execution step 2.b the log message indicates the modification of an existing network configuration. -- For execution step 2.c the log message indicates the disabling of a port. -- For execution step 2.d the log message indicates the enabling a port. -- For execution step 2.e the log message indicates that packets have exceeded configured firewall limits. -- For execution step 2.f the log message indicates a network connection has been attempted along with details about that network connection including source and destination IP addresses. -- For execution step 2.g the log message indicates that a virtual machine was rebooted, and a subsequent log message indicates that a host operating system has been rebooted. -- For execution step 2.h the log message indicates that a virtual machine has been shut down and a subsequent log message indicates that the host operating system has been shut down. -- For execution step 2.i the log message indicates that a scheduled job was created within the host operating system, a subsequent log message indicates that a scheduled job was created in the hypervisor, and a subsequent log message indicates that a scheduled job was created in the container engine. -- For execution step 2.j the log message indicates that a configuration change was made to the host operating system and a subsequent log message indicates that a configuration change was made to the hypervisor. -- For execution step 2.k the log message indicates that a virtual disk was attached to a virtual machine, and a subsequent log message indicates that a virtual disk was detached from a virtual machine. -- For execution step 2.l the log message indicates that a virtual machine was created. -- For execution step 2.m the log message indicates that a virtual machine was started. -- For execution step 2.n the log message indicates that a virtual machine was stopped. -- For execution step 2.o the log message indicates that a virtual machine was deleted. -- For execution step 2.p the log message indicates that an image was added to the container repository. -- For execution step 2.q the log message indicates that an image was modified in the container repository. -- For execution steps 2.r the log message indicates that an image was removed from the container repository. -- For execution step 2.s the log message indicates a container was created. -- For execution step 2.t the log message indicates that a container was started. -- For execution step 2.u the log message indicates that a container was stopped. -- For execution step 2.v the log message indicated that a container was restarted. -- For execution step 2.w the log message indicates that a container was deleted. -- For execution step 2.x the log message indicates that a container volume was created. -- For execution step 2.y the log message indicates that a container volume was mounted. -- For execution step 2.z the log message indicates that a container volume was deleted. - -**Expected format of evidence:** Generated Log Files from DUT/s. - -## 8.4.5 Application Security Events - -**Requirement Name:** Application Security Events to be Logged. - -**Requirement Reference:** REQ-SEC-SLM-APP-EVT-1, REQ-SEC-SLM-APP-EVT-2, clause 5.3.8.11.4, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Support for the logging of security events in network functions - -**Threat References:** T-OPENSRC-01, T-xAPP-01, T-xAPP-02, T-xAPP-03, T-xAPP-04, T-rAPP-01, T-rAPP-02, T-rAPP-03, T-rAPP-04, T-rAPP-05, T-rAPP-06, T-rAPP-07, T-PNF-01. - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_Logs\_Application\_Security\_Events - -**Purpose:** The purpose of the test is to verify the logging of security event data from O-RAN Network. - -### Procedure and execution steps - -#### Preconditions - -A tester has access to testing equipment that can connect to any O-RAN network function. - -#### Execution steps - -NOTE: Execution steps not applicable to the DUT may be skipped. - -- 1) Login to the DUT via test equipment with authorized credentials. -- 2) Conduct an operation on the DUT that is known to generate an error. -- 3) Conduct an operation on the DUT that is known to load a dynamic library. - -#### Expected results - -All the security logs produced by O-RAN Network Functions contain log messages that pertain to the actions taken in the execution steps. - -- For execution step 2 the log message contains an error message. -- For execution step 3 the log message contains a message indicating that a dynamic library loaded and details about that library. - -**Expected format of evidence:** Generated Log Files from DUT/s. - -## 8.4.6 Data Access Security Events - -**Requirement Name:** Data Access Security Events to be Logged. - -**Requirement Reference:** REQ-SEC-SLM-DAT-EVT-1, REQ-SEC-SLM-DAT-EVT-2, REQ-SEC-SLM-DAT-EVT-3, REQ-SEC-SLM-DAT-EVT-4, REQ-SEC-SLM-DAT-EVT-5, REQ-SEC-SLM-DAT-EVT-6, REQ-SEC-SLM-DAT-EVT-7, REQ-SEC-SLM-DAT-EVT-8, clause 5.3.8.11.5, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Logging of data access security events. - -**Threat References:** T-VM-C-01, T-NEAR-RT-03, T-O-RAN-07, T-O-RAN-08, T-GEN-05 - -**DUT/s:** SMO, Non-RT RIC, Near-RT RIC, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_Logs\_Data\_Access\_Security\_Events - -**Purpose:** The purpose of the test is to verify the logging of data access security. - -## Procedure and execution steps - -### Preconditions - -A tester has access to testing equipment that can communicate securely with the DUT and is able to perform security and administrative related operations. - -### Execution steps - -NOTE: Execution steps not applicable to the DUT may be skipped. - -- 1) Login to the DUT via testing equipment with authorized credentials. -- 2) Execute the following operations on the DUT. - - a) Add a new file. - - b) Delete an existing file. - - c) Attempt to add a file in an unauthorized location. - - d) Attempt to delete a file from an unauthorized location. - - e) Read an existing file. - - f) Write to an existing file. - - g) Attempt to read to a file in an unauthorized location. - - h) Attempt to write to a file to an unauthorized location. - - i) Create a new directory. - - j) Delete an existing directory. - - k) Attempt to create a directory in an unauthorized location. - - l) Attempt to delete a directory from an unauthorized location. - - m) Add data to a datastore or database. - - n) Delete data from a datastore or database. - - o) Attempt to add data to a datastore or database in an unauthorized location. - - p) Attempt to delete data from a datastore or database from an unauthorized location. - - q) Read data from a datastore or database. - - r) Write data from a datastore or database. - - s) Attempt to read data from a datastore or database from an unauthorized location. - - t) Attempt to write data to a datastore or database in an unauthorized location. - - u) Make a permissions change to a file. - - v) Make a permissions change to a directory. - - w) Make a permissions change to a datastore or database. - -### Expected results - -All the security logs produced by O-RAN architecture elements contain log messages that document appropriately the actions taken in the execution steps. - -- For execution step 2.a the log message indicates that a new file was added. - -- For execution step 2.b the log message indicates an existing file was deleted. -- For execution step 2.c the log message indicates an unauthorized attempt to add a file. -- For execution step 2.d the log message indicates an unauthorized attempt to delete a file. -- For execution step 2.e the log message indicates an existing file was read. -- For execution step 2.f the log message indicates an existing file was written. -- For execution step 2.g the log message indicates an unauthorized attempt to read to a file. -- For execution step 2.h the log message indicates an unauthorized attempt to write to a file. -- For execution step 2.i the log message indicates a new directory was created. -- For execution step 2.j the log message indicates an existing directory was deleted. -- For execution step 2.k the log message indicates an unauthorized attempt to create a directory. -- For execution step 2.l the log message indicates an unauthorized attempt to delete a directory. -- For execution step 2.m the log message indicates data was added to a datastore or database. -- For execution step 2.n the log message indicates data was deleted from a datastore or database. -- For execution step 2.o the log message indicates an unauthorized attempt to add data to a datastore or database. -- For execution step 2.p the log message indicates an unauthorized attempt to delete data from a datastore or database. -- For execution step 2.q the log message indicates that data was read from a datastore or database. -- For execution step 2.r the log message indicates that data was written to a datastore or database. -- For execution step 2.s the log message indicates an unauthorized attempt to read data from a datastore or database. -- For execution step 2.t the log message indicates an unauthorized attempt to write data to a datastore or database. -- For execution step 2.u the log message indicates a permissions change to a file. -- For execution step 2.v the log message indicates a permissions change to a directory. -- For execution step 2.w the log message indicates a permissions change to a datastore or database. - -**Expected format of evidence:** Generated Log Files from DUT. - -## 8.4.7 Account and Identity Security Events - -**Requirement Name:** Account and Identity Security Events to be Logged. - -**Requirement Reference:** REQ-SEC-SLM-AAI-EVT-1, REQ-SEC-SLM-AAI-EVT-2, REQ-SEC-SLM-AAI-EVT-3, REQ-SEC-SLM-AAI-EVT-4, REQ-SEC-SLM-AAI-EVT-5, REQ-SEC-SLM-AAI-EVT-6, REQ-SEC-SLM-AAI-EVT-7, REQ-SEC-SLM-AAI-EVT-9, REQ-SEC-SLM-AAI-EVT-10, clause 5.3.8.11.6, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Logging of account and identity security events. - -**Threat References:** T-GEN-02, T-O-RAN-02, T-O-RAN-06, T-O-RAN-07, T-ProtocolStack-02, T-SMO-02, T-SMO-05, T-SMO-08, T-SMO-25, T-SMO-30, T-NEAR-RT-03 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_Logs\_Account\_and\_Identity\_Security\_Events - -**Purpose:** The purpose of the test is to verify the logging of account and identity access security. - -#### Procedure and execution steps - -##### Preconditions - -A tester will have access to testing equipment that can communicate securely with the DUT and is able to perform security and administrative related operations. - -##### Execution steps - -NOTE: Execution steps not applicable to the DUT may be skipped. - -- 1) Login to the DUT via testing equipment with authorized credentials. -- 2) Execute the following operations on the DUT. - - a) Create an account. - - b) Modify an existing account. - - c) Delete an existing account. - - d) Attempt to create an account in an unauthorized location. - - e) Change the privilege level of an existing account from a lower privilege to a higher privilege. - - f) Attempt to change the privilege level of an existing account in an unauthorized location. - - g) Change the group membership of an existing account. - - h) Attempt to change the group membership of an existing account in an unauthorized location. - - i) Use a function in the DUT that requires a specific assigned authorization. - - j) Attempt to use a function in the DUT that requires a specific unassigned authorization. - - k) Authenticate an account to the DUT that has been configured to access that DUT. - - l) Attempt to authenticate an account to the DUT that has not been configured to access that DUT. - - m) Change the privilege level of an existing account from a higher privilege to a lower privilege. - - n) Access the DUT with an account that does not require authentication. - - o) End a session with the DUT. - -##### Expected results - -All the security logs produced by O-RAN architecture elements contain log messages that document appropriately the actions taken in the execution steps. - -- For execution step 2.a the log message indicates that an account was created. -- For execution step 2.b the log message indicates that an existing account was modified. -- For execution step 2.c the log message indicates that an existing account was deleted. -- For execution step 2.d the log message indicates an unauthorized attempt to create an account. -- For execution step 2.e the log message indicates a privilege level change of an existing account from a lower privilege to a higher privilege. -- For execution step 2.f the log message indicates an unauthorized attempt to change the privilege level of an existing account. - -- For execution step 2.g the log message indicates that the group membership had changed for an existing account. -- For execution step 2.h the log message indicates an unauthorized attempt to change the group membership of an existing account. -- For execution step 2.i the log message indicates the use of a restricted function. -- For execution step 2.j the log message indicates an unauthorized attempt to use a restricted function. -- For execution step 2.k the log message indicates the successful authentication of an account. -- For execution step 2.l the log message indicates the unsuccessful attempt to authenticate an account. -- For execution step 2.m the log message indicates a privilege level change of an existing account from a higher privilege to a lower privilege. -- For execution step 2.n the log message indicates access with an account that does not require authentication. -- For execution step 2.o the log message indicates the end of a session. - -**Expected format of evidence:** Generated Log Files from DUT. - -## 8.4.8 General Security Events - -**Requirement Name:** General Security Events to be logged. - -**Requirement Reference:** REQ-SEC-SLM-GSE-1, REQ-SEC-SLM-GSE-2, REQ-SEC-SLM-GSE-3, REQ-SEC-SLM-GSE-4, REQ-SEC-SLM-GSE-5, REQ-SEC-SLM-GSE-6, clause 5.3.8.11.7, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Logging of general security events. - -**Threat References:** T-ORAN-01, T-O-RAN-02, T-O-RAN-03, T-O-RAN-08, T-GEN-02, T-VM-C-01, T-VM-C-04, T-VM-C-06, T-IMG-01, T-IMG-04, T-VL-01, T-VL-02, T-xAPP-01, T-rAPP-03, T-HW-02 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_General\_Security\_Events\_Logged - -**Purpose:** The purpose of the test is to verify the logging of general security events. - -### Procedure and execution steps - -#### Preconditions - -A tester will have access to testing equipment that can communicate securely with the DUT and is able to perform security and administrative related operations. - -#### Execution steps - -NOTE: Execution steps not applicable to the DUT may be skipped. - -- 1) Login to the DUT via testing equipment with authorized credentials. -- 2) Execute the following operations on the DUT. - - a) Enable security software such as firewalls, malware protection, data loss prevention or intrusion detection systems. - - b) Disable security software such as firewalls, malware protection, data loss prevention or intrusion detection systems. - - c) Log into DUT using an account with administrative privileges and perform a function that requires those privileges. - -- d) Make a change to the security configuration of the DUT. -- e) View a certificate or key on the DUT. -- f) Export a certificate or key from the DUT. -- g) Renew a certificate or key on the DUT. -- h) Import a certificate or key from the DUT. -- i) Modify a certificate or key on the DUT. -- j) Delete a certificate or key from the DUT. -- k) Perform a cryptographic operation on the DUT that involves signatures, encryption, hashing, key generation or key destruction. -- l) Submit a security patch to the DUT but do not apply it. - -### Expected results - -All the security logs produced by O-RAN architecture elements contain log messages that document appropriately the actions taken in the execution steps. - -- For execution steps 2.a and 2.b the log message indicates the security software has been enabled or disabled. -- For execution step 2.c the log message indicates the use of administrative privileges. -- For execution step 2.d the log message indicates a change to the security configuration has occurred and the nature of the change. -- For executions 2.e through 2.k the log message is absent of any sensitive information related to the certificate or key. -- For execution 2.l the log message indicates that a security patch was submitted but not applied. - -**Expected format of evidence:** Generated Log Files from DUT. - -## 8.4.9 Void - ---- - -# 9 Software security evaluation for O-RAN architecture elements - -## 9.1 Overview - -This clause contains a set of software security evaluations of an O-RAN architecture element, covering Software Lifecycle Management. - -## 9.2 Open-Source Software Component Analysis - -Void - -## 9.3 Binary Static Analysis - -Void - -## 9.4 Software Bill of Materials (SBOM) - -### 9.4.1 SBOM Signature - -**Requirement Name:** A digital signature is provided for the SBOM. - -**Requirement Reference:** SEC-CTL-SBOM-001, clause 6.3.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** SBOM is authenticity, integrity protected and provided in a standard format. - -**Threat References:** T-O-RAN-09 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_SBOM\_Signature - -**Purpose:** To verify the SBOM is provided with a digital signature - -#### Procedure and execution steps - -##### Preconditions - -SBOM is provided. Tools to verify the digital signature are available. Solution Provider key or certificate is provided. - -##### Execution steps - -Ensure the SBOM is provided with a digital signature in the format as described below. Verify SBOM digital signature is valid using the software provider's public key or certificate. Depending on the format of the SBOM, there are various ways how to include and verify the digital signature of the SBOM. Below, the digital signature methods are detailed. - -##### SPDX - -**YAML, RDF and tag data:** The signature is in a separate file from the SPDX file. Digital signature format is CMS/PKCS#7/CAdES. - -EXAMPLE: foo.spdx is accompanied by foo.spdx.sig containing its signature - -**XML:** XML Signature 2.0 - -**JSON:** JSON Web Signature (JWS), and JSON Signature Format (JSF). - -##### CycloneDX - -**XML:** XML Signature 2.0 - -**JSON:** JSON Web Signature (JWS), and JSON Signature Format (JSF). - -##### SWID - -**XML:** XML Signature 2.0 - -##### Expected results - -Digital signature of the SBOM is valid. - -**Expected format of evidence:** Report file, screenshot, or log file from tool used for verification of digital signature. - -### 9.4.2 SBOM Data Fields - -**Requirement Name:** Data fields are according to NTIA guidance [13] - -**Requirement Reference:** REQ-SBOM-002, REQ-SBOM-011, clause 6.3.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** A minimum set of data fields are included in the SBOM and it is in an standard format. - -**Threat References:** T-O-RAN-09 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_SBOM\_Data\_Fields - -**Purpose:** To verify the minimum set of data fields are included in the SBOM - -**Procedure and execution steps** - -**Preconditions** - -SBOM file is provided. Tools to verify the data fields are available. - -**Execution steps** - -Run the SBOM check tool and verify that there is minimum set of data fields present in SBOM depending on the SBOM format used. - -**Table 9-1: Minimum set of data fields for SPDX [12]** - -| NTIA field | NTIA description | SPDX 2.2.1 field | -|--------------------------|-----------------------------------------------------------------------------------------------------------|----------------------------------| -| Supplier Name | The name of an entity that creates, defines, and identifies components | PackageSupplier | -| Component Name | Designation assigned to a unit of software defined by the original supplier | PackageName | -| Version of the Component | Identifier used by the supplier to specify a change in software from a previously identified version | PackageVersion | -| Other Unique Identifiers | Other identifiers that are used to identify a component, or serve as a look-up key for relevant databases | SPDXID (Package SPDX Identifier) | -| Dependency Relationship | Characterizing the relationship that an upstream component X is included in software Y | Relationship: CONTAINS | -| Author of SBOM Data | The name of the entity that creates the SBOM data for this component | Creator | -| Timestamp | Record of the date and time of the SBOM data assembly | Created | - -**Table 9-2: Minimum set of data fields for CycloneDX [13]** - -| NTIA field | NTIA description | CycloneDX field | -|--------------------------|-----------------------------------------------------------------------------------------------------------|--------------------------------------------------------| -| Supplier Name | The name of an entity that creates, defines, and identifies components | publisher | -| Component Name | Designation assigned to a unit of software defined by the original supplier | name | -| Version of the Component | Identifier used by the supplier to specify a change in software from a previously identified version | version | -| Other Unique Identifiers | Other identifiers that are used to identify a component, or serve as a look-up key for relevant databases | bom/serialNumber and component/bom-ref | -| Dependency Relationship | Characterizing the relationship that an upstream component X is included in software Y | (Nested assembly/subassembly and/or dependency graphs) | -| Author of SBOM Data | The name of the entity that creates the SBOM data for this component | bom-descriptor:metadata/manufacture/contact | -| Timestamp | Record of the date and time of the SBOM data assembly | timestamp | - -**Table 9-3: Minimum set of data fields for SWID [13]** - -| NTIA field | NTIA description | SWID tag | -|--------------------------|-----------------------------------------------------------------------------------------------------------|---------------------------------------------------| -| Supplier Name | The name of an entity that creates, defines, and identifies components | @role (softwareCreator/publisher), @name | -| Component Name | Designation assigned to a unit of software defined by the original supplier | @name | -| Version of the Component | Identifier used by the supplier to specify a change in software from a previously identified version | @version | -| Other Unique Identifiers | Other identifiers that are used to identify a component, or serve as a look-up key for relevant databases | @tagID | -| Dependency Relationship | Characterizing the relationship that an upstream component X is included in software Y | @rel, @href | -| Author of SBOM Data | The name of the entity that creates the SBOM data for this component | @role (tagCreator), @name | -| Timestamp | Record of the date and time of the SBOM data assembly | - | - -This test is part of the O-RAN software producer's Software Development Lifecycle (SDLC). - -### Expected results - -Minimum set of data fields are present. - -**Expected format of evidence:** Report file, screenshot, or log file from SBOM check tool. - -## 9.4.3 SBOM Format - -**Requirement Name:** SBOM is provided in one of the accepted formats: SPDX, CycloneDX, or SWID. - -**Requirement Reference:** REQ-SBOM-011, clause 6.3.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** SBOM is provided in a standard format. - -**Threat References:** T-O-RAN-09 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_SBOM\_Format - -**Purpose:** To verify that the SBOM is provided in one of standard formats. - -### Procedure and execution steps - -#### Preconditions - -SBOM is provided. Tools to verify the SBOM are available. - -#### Execution steps - -Run the SBOM check tool to verify the SBOM format. - -#### Expected results - -SBOM format is SPDX, CycloneDX, or SWID. - -**Expected format of evidence:** Report file. - -## 9.4.4 SBOM Depth - -**Requirement Name:** SBOM Depth is in the required level. - -**Requirement Reference:** REQ-SBOM-004, clause 6.3.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The SBOM Depth is the required for the different types of software. - -**Threat References:** T-O-RAN-09 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_SBOM\_Depth - -**Purpose:** To verify that the SBOM depth is provided to the level specified. - -### Procedure and execution steps - -#### Preconditions - -SBOM is provided. Tools to verify the SBOM are available. - -#### Execution steps - -Run the SBOM check tool to verify the SBOM depth provided. - -At a minimum, all top-level dependencies are listed. - -#### Expected results - -SBOM depth is as specified in the requirements: - -- top-level for every O-RAN software delivery - -**Expected format of evidence:** Report file, log file from SBOM check tool. - -## 9.4.5 Void - -## 9.4.6 SBOM Version Verification - -**Requirement Name:** The version in the SBOM is accurately and matches the actual O-RAN software package version. - -**Requirement Reference:** REQ-SBOM-002, clause 6.3.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Version of the software component included in the SBOM is matching the actual software component version. - -**Threat References:** T-O-RAN-08, T-O-RAN-09 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_SBOM\_VERSION\_VERIFICATION - -**Purpose:** The purpose of this test is to ensure the SBOM reflects the current version of software package. - -### Procedure and execution steps - -#### Preconditions - -SBOM is provided. Tools to verify the SBOM are available. Access to version information regarding O-RAN software package. - -**Execution steps:** - -- 1) For each software component in the package, compare the version listed in the SBOM with the actual software component version. -- 2) Ensure that the SBOM's version matches the component's version. -- 3) Document any discrepancies. - -**Expected Results:** - -The version specified in the SBOM aligns with the actual version of the software component. - -**Expected format of evidence:** - -A report detailing: - -- name of the software package component(s), SBOM indicated version, actual version, notes on any discrepancies or issues found. - -## 9.4.7 Void - -## 9.4.8 SBOM Presence - -**Requirement Name:** SBOM provided with all O-RAN Software. - -**Requirement Reference:** REQ-SBOM-001, clause 6.3.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** For every O-RAN software delivery, an SBOM is available. - -**Threat References:** T-O-RAN-09 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_SBOM\_Presence - -**Purpose:** The purpose of this test is to ensure that for every O-RAN software delivery an SBOM is available. This is applicable to all software components within the O-RAN system. - -**Procedure and execution steps****Preconditions** - -SBOM is provided. Tools to verify the SBOM are available. - -**Execution steps** - -- 1) List O-RAN software delivery. -- 2) Look for associated files or documentation indicating the presence of an SBOM. -- 3) Validate the SBOM's content to ensure it's not just a placeholder. -- 4) Document any software delivery that lacks a genuine SBOM. - -**Expected Results** - -Every O-RAN software delivery has a genuine SBOM associated with it. - -**Expected Format of Evidence:** - -A report detailing: - -- names of the software package components; -- status of its SBOM (Present/Absent); -- notes on any discrepancies or issues found. - -## 9.4.9 SBOM Vulnerabilities Field - -**Requirement Name:** Vulnerabilities field omission in SBOMs. - -**Requirement Reference:** REQ-SBOM-003, clause 6.3.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Vulnerabilities are not included as an additional data field because it would represent a static view from a specific point in time, while vulnerabilities are constantly evolving. Therefore, the vulnerabilities field in SBOM for O-RAN software cannot be relied upon to determine the SBOM vulnerabilities by the Service provider. Service providers need to perform their own vulnerability assessment, at least at the moment of the SBOM release. - -**Threat References:** T-O-RAN-09 - -**DUT/s:** SMO, Non-RT RIC and rApps, Near-RT RIC and xApps, O-CU-CP, O-CU-UP, O-DU, O-RU, O-Cloud - -**Test Name:** TC\_SBOM\_Vulnerabilities\_Fields - -**Purpose:** Verify that vulnerabilities fields is not included as an additional field to the SBOM. - -### Procedure and execution steps - -#### Preconditions - -SBOM is provided. Tools to verify the SBOM are available. - -#### Execution steps - -Verify that no vulnerabilities fields exist within the SBOM. - -#### Expected Results - -There are no vulnerabilities field(s) present in the SBOM. - -**Expected Format of Evidence:** screenshot(s) - -## 9.4.10 Void - -# 9.5 Signature Verification - -## 9.5.1 Signature Verification Matrix per DUT and Phase - -This clause defines the roles and responsibilities of each DUT in verifying digital signatures on signed objects. - -The following table summarizes: - -- the type of signed object each DUT tests, -- the phase where signature validation is expected (e.g., onboarding, deployment), -- and the DUT's corresponding responsibility in verifying digital signatures. - -All positive and negative signature verification test cases (as defined in clause 9.5.2) apply accordingly based on this table. - -**Table 9-4: Signature verification per DUT, signed object and phase** - -| DUT | Signed object | Phase | Signature(s) to Verify | -|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------|-------------------------------------------------------------------------| -| SMO | Application Packages (xApps/rApps images, O-RAN Architecture Element images, PNF images)
Application artifacts
O-Cloud software images
AI/ML models
rApp images | Onboarding, Deployment, Instantiation | Verifies Service Provider (if present) and Solution Provider signatures | -| O-Cloud | O-RAN Architecture Element Images
Application artifacts
O-Cloud software images
xApp images
AI/ML models | Deployment, Instantiation | Verifies Service Provider (if present) and Solution Provider signatures | - -NOTE: For all test cases defined in this clause, when both Service Provider and Solution Provider signatures are present on a signed object, the DUT performs signature verification in the following order: - -1. Service Provider signature, -2. Solution Provider signature. - -For each DUT, it is sufficient to perform the test case on one representative signed object type, since the signature verification mechanism is common across all object types listed for that DUT. The intent is to verify the implementation of the cryptographic validation logic, not to exhaustively test all signed object formats. - -## 9.5.2 Signature Verification Test Cases - -**Requirement Name:** Signature verification of signed objects. - -**Requirement Reference:** REQ-SEC-ALM-PKG-12 clause 5.3.2.1.1, SEC-CTL-ALM-PKG-1, SEC-CTL-ALM-PKG-1B, SEC-CTL-ALM-PKG-9, clause 5.3.2.1.2, SEC-CTL-OCLOUD-SW-1, clause 5.1.8.3.2 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Each signed object is verified for integrity and authenticity protection. - -**Threat References:** T-IMG-01, T-IMG-04, T-AppLCM-01 - -**DUT/s:** SMO, O-Cloud - -Test Case 1: Positive signature verification - -**Test Name:** TC\_Sig\_Verification\_Positive - -**Purpose:** To verify that the DUT correctly validates the digital signature of the signed object, as per Table 9-4. - -### Procedure and execution steps - -#### Preconditions - -Digitally signed object using a trusted certificate and approved algorithm as defined by the O-RAN Security Protocols Specification [2], clause 5, is available. - -The DUT has access to the relevant trust anchors. - -#### Execution steps - -- 1) Submit the signed object to the DUT via the appropriate interface. - -EXAMPLE: The interface may include the onboarding API for the SMO or a deployment automation pipeline in the O-Cloud, depending on the phase in which signature verification occurs. - -- 2) Trigger the DUT to initiate signature verification of the signed object according to Table 9-4. -- 3) The DUT performs digital signature verification: - - a) Validates the certificate chain of the signature. - - b) Verifies the cryptographic integrity of the object. - -#### Expected results - -Signature verification succeeds, and the signed object is accepted. - -**Expected Format of Evidence:** logs showing successful signature verification. - -Test Case 2: Hash Mismatch Signature Verification Failure - -**Test Name:** TC\_SIG\_Validation\_HashMismatch - -**Purpose:** To verify that the DUT correctly detects and rejects a signed object whose hash does not match the signed hash. - -#### Procedure and execution steps - -##### Preconditions - -- Valid digitally signed object -- Signed object content is modified after signing (introducing a hash mismatch) -- Trusted CA certificates are installed on the DUT - -##### Execution steps - -- 1) Submit the altered signed object to the DUT via the appropriate interface. -- 2) Trigger the DUT to initiate signature verification of the altered signed object according to Table 9-4. -- 3) The DUT computes the hash of the altered signed object and compares it against the signed hash. - -#### Expected Results - -- Signature verification fails due to hash mismatch -- Signed object is rejected - -**Expected format of evidence:** Logs indicating hash mismatch detection - -Test Case 3: Non-Compliant Algorithm Signature Verification Failure - -**Test Name:** TC\_SIG\_Validation\_NonCompliantAlgorithm - -**Purpose:** To verify that the DUT correctly rejects signed objects that are signed using cryptographic algorithms not listed in the accepted algorithm set defined by the O-RAN Security Protocols Specification [2], clause 5. - -#### Procedure and execution steps - -##### Preconditions - -- A signed object is available that was signed using a cryptographic algorithm not listed in the Security Protocols Specification [2], clause 5. -- The DUT has access to the relevant trust anchors. - -#### Execution steps - -- 1) Submit the signed object to the DUT via the appropriate interface. -- 2) Trigger the DUT to initiate signature verification of the signed object according to Table 9-4. -- 3) The DUT detects that the signature uses a non-compliant algorithm. - -#### Expected Results - -- Signature verification fails due to the use of a non-compliant algorithm not listed in the O-RAN Security Protocols Specification [2], clause 5. -- Signed object is rejected - -**Expected format of evidence:** Logs showing failure of signature verification and indicating the non-compliant algorithm used. - -Test Case 4: Certificate Public Key Mismatch Verification Failure - -**Test Name:** TC\_SIG\_Validation\_CertPublicKeyMismatch - -**Purpose:** To verify that the DUT correctly detects and rejects a public/private key mismatch during signature verification. - -#### Procedure and execution steps - -##### Preconditions - -- Signed object with a valid private key, but certificate used during validation contains an unrelated public key. -- The DUT has access to the relevant trust anchors. - -##### Execution steps - -- 1) Submit the signed object to the DUT via the appropriate interface. -- 2) Trigger the DUT to initiate signature verification of the signed object according to Table 9-4. -- 3) The DUT detects a mismatch between the public key in the certificate and the signature. - -#### Expected Results - -- Signature verification fails due to public/private key mismatch -- Signed object is rejected - -**Expected format of evidence:** Logs indicate public key mismatch error. - -Test Case 5: Untrusted CA Signature Verification Failure - -**Test Name:** TC\_SIG\_Validation\_UntrustedCA - -**Purpose:** To verify that the DUT correctly rejects signed objects using certificates from untrusted CAs. - -#### Procedure and execution steps - -##### Preconditions - -- Signed object using a certificate from an untrusted CA -- The DUT has access to the relevant trust anchors. - -### Execution steps - -- 1) Submit the signed object to the DUT via the appropriate interface. -- 2) Trigger the DUT to initiate signature verification of the signed object according to Table 9-4. -- 3) The DUT checks the issuer of the certificate and compares it with the entries in its trust store. - -### Expected Results - -- Signature verification fails due to untrusted CA -- Signed object is rejected - -**Expected format of evidence:** Logs indicate untrusted CA. - -Test Case 6: Expired Certificate Signature Verification Failure - -**Test Name:** TC\_SIG\_Validation\_ExpiredCert - -**Purpose:** To verify that the DUT correctly detects and rejects signed objects using expired certificates. - -### Procedure and execution steps - -#### Preconditions - -- Signed object using a certificate whose validity period has expired. -- The DUT's system time is configured to a date after the certificate's expiration date. -- The DUT has access to the relevant trust anchors. - -#### Execution steps - -- 1) Submit the signed object to the DUT via the appropriate interface. -- 2) Trigger the DUT to initiate signature verification of the signed object according to Table 9-4. -- 3) The DUT checks the certificate's validity period against the current time. - -### Expected Results - -- Signature verification fails due to expired certificate -- Signed object is rejected - -**NOTE:** If the DUT is configured, based on operator policy, to allow expired certificates during deployment or instantiation, the signature verification may succeed, and the signed object may be accepted in accordance with that policy. - -**Expected format of evidence:** Logs indicate expired certificate error. - ---- - -## 10 ML security validation for O-RAN system - -### 10.1 Overview - -AI/ML technologies and models are adopted at the O-RAN system Non-RT RIC and Near-RT RIC to enable O-RAN use cases: traffic steering, massive MIMO optimization, radio resource allocation for UAV applications, position accuracy enhancement, beam management, and enhance CSI feedback. Other uses cases could be checked in document O-RAN Use Cases Detailed Specification [22]. - -## 10.2 ML Data Poisoning - -Void - ---- - -# 11 Security tests of O-RAN interfaces - -## 11.1 Open FH - -### 11.1.1 Overview - -This clause contains security tests to validate the security protection mechanism of the O-RAN Open Fronthaul interface. - -### 11.1.2 Open Fronthaul Point-to-Point LAN Segment - -#### 11.1.2.0 Introduction - -IEEE 802.1X-2020 Port-based Network Access Control [11] provides the means to control network access in point-to-point LAN segments within the Open Fronthaul network. Port-based network access control in the O-RAN Alliance Open Fronthaul comprises supplicant, authenticator, and authentication of server entities described in IEEE 802.1X-2020 [11]. - -The security test cases in this clause cover the validation of the authenticator and supplicant functionalities of the 802.1X, affecting to all the elements acting as an O-RAN Open Fronthaul network elements, including but not limited to, O-DU, O-RU, switches, FHM, FHGW, TNE and PRTC-T/GM as defined in clause 5.2.5.5 of Security Requirements and Controls Specifications [5]. - -#### 11.1.2.1 Authenticator Validation - -**Requirement Name:** Authenticator function validation - -**Requirement Reference:** SEC-CTL-OFHPLS-3, SEC-CTL-OFHPLS-5, SEC-CTL-OFHPLS-6, REQ-SEC-OFHPLS-1, clause 5.2.5.5, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Requirements of Authenticator in the Open Fronthaul network and its interface to an Authentication Server - -**Threat References:** T-FRHAUL-02 - -**DUT/s:** O-DU - -**Test Name:** TC\_Authenticator\_Validation - -**Purpose:** To verify and validate the authenticator requirements of the network component to serve the request from supplicant(s) using EAP TLS authentication per 802.1X-2020 [11]. - -#### Procedure and execution steps - -##### Preconditions - -DUT supports authenticator role of the 802.1X for port-based network access control. - -IP enabled network interface of DUT reachable to the authentication server and 802.1X enabled for its Open Fronthaul interface. - -Set up an authentication server with root, server and client certificates, and the start the authentication server. - -EXAMPLE: RADIUS server (e.g. free radius on Linux®) can be a possible authentication server. - -NOTE: RADIUS support is required over interface between an authenticator and authentication server in the security requirement specification, only RADIUS authentication server is called for in this security test environment setup. Diameter based authentication server could be used as an alternative. - -**Execution steps** - -Run the 802.1X test tool emulating the request(s) from the supplicant(s) towards the DUT, which is the authenticator and ensure the 802.1X authentication process runs to completion. - -The following test scenarios are executed: - -**Table 11-1: Scenarios to be executed** - -| Scenario ID | Configuration | -|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 1 | Test tool (as supplicant) setting for 802.1X with EAPoL, correct Identity (Certificate DN) and Client Certificate (provisioned on the Radius server) | -| 2 | Test tool (as supplicant) setting for 802.1X with EAPoL, correct Identity (Certificate DN) and incorrect Client Certificate (not provisioned on the Radius server) | -| 3 | Test tool (as supplicant) setting for 802.1X with EAPoL and incorrect Identity (Certificate DN) | -| 4 | Test tool (as supplicant) setting for 802.1X with EAP non-TLS authentication | - -**Expected results** - -DUT successfully completes the procedure for the 802.1X Authentication validation (being granted or denied), for each test scenario: - -**Table 11-2: Expected results** - -| Scenario ID | Expected result | Reason | -|-------------|----------------------------|--------------------------------------------------------------| -| 1 | Connection established | Authentication successfully | -| 2 | Connection not established | Fail Authentication because the certificate is wrong | -| 3 | Connection not established | Fail Authentication because the Identity is wrong | -| 4 | Connection not established | Fail Authentication because the authentication type is wrong | - -**Expected format of evidence:** Log files with traffic captures including the different scenarios executed in the execution steps and with a clear identification of successful and unsuccessful authentication - -### 11.1.2.2 Supplicant Validation - -**Requirement Name:** Supplicant function validation - -**Requirement Reference:** SEC-CTL-OFHPLS-2, SEC-CTL-OFHPLS-5, REQ-SEC-OFHPLS-1, clause 5.2.5.5, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Requirements of Supplicant in the Open Fronthaul network - -**Threat References:** T-FRHAUL-02 - -**DUT/s:** O-RU, O-DU - -**Test Name:** TC\_Supplicant\_Validation - -**Purpose:** To verify the supplicant requirement of the network component for port connection request using EAP TLS authentication per 802.1X-2020 [11]. - -**Procedure and execution steps** - -**Preconditions** - -DUT supports supplicant role of the 802.1X for port-based network access control. - -Set up an authentication server with root, server and client certificates, and start the authentication server. - -EXAMPLE: RADIUS server (e.g. free radius on Linux) can be a possible authentication server. - -Set up the 802.1X test tool host/device as the authenticator with EAP TLS authentication for 802.1X protocol and configure the preset authentication server. - -NOTE: RADIUS support is required over interface between an authenticator and authentication server in the security requirement specification, only RADIUS authentication server is called for in this security test environment setup. Diameter based authentication server could be used as an alternative. - -**Execution steps** - -Start the test run as an emulated authenticator waiting for the supplicant request. - -Configure and enable the DUT to start the port connection request as a supplicant towards the 802.1X test tool, which is the authenticator and verify the 802.1X authentication process runs to completion. - -The following test scenarios are executed: - -**Table 11-3: Scenarios to be executed** - -| Scenario ID | Configuration | -|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 1 | DUT (as supplicant) setting for 802.1X with EAPoL, correct Identity (Certificate DN) and Client Certificate (provisioned on the Radius server) | -| 2 | DUT (as supplicant) setting for 802.1X with EAPoL, correct Identity (Certificate DN) and incorrect Client Certificate (un-provisioned on the Radius server) | -| 3 | DUT (as supplicant) setting for 802.1X with EAPoL and incorrect Identity (Certificate DN) | -| 4 | DUT (as supplicant) setting for 802.1X with EAP non-TLS authentication (optional) | - -**Expected results** - -DUT successfully completes the procedure for the supplicant validation (being granted or denied), for each test scenario: - -**Table 11-4: Expected results** - -| Scenario ID | Expected result | Reason | -|-------------|----------------------------|--------------------------------------------------------------| -| 1 | Connection established | Authentication successfully | -| 2 | Connection not established | Fail Authentication because the certificate is wrong | -| 3 | Connection not established | Fail Authentication because the Identity is wrong | -| 4 | Connection not established | Fail Authentication because the authentication type is wrong | - -**Expected format of evidence:** Log files with traffic captures including the different scenarios executed in the execution steps and with a clear identification of successful and unsuccessful authentication. - -**11.1.2.3 Port-Based Access Enforcement Validation** - -**Requirement Name:** Port-Based Access Enforcement Validation - -**Requirement Reference:** SEC-CTL-OFHPLS-4, clause 5.2.5.5.3, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** An authenticator in an Open Fronthaul network element that supports port-based network access control on each point-to-point LAN segment as defined in IEEE 802.1X-2020. - -**Threat References:** T-FRHAUL-02 - -**DUT/s:** O-DU - -**Test Name:** TC\_Port\_Access\_Enforcement\_Validation - -**Purpose:** To verify that the DUT, when acting as an 802.1X authenticator, enforces port-based access control by allowing only EAPoL frames prior to authentication, and blocking all other Ethernet traffic—including frames carrying IP packets—until EAP-TLS authentication is successfully established. - -#### Procedure and execution steps - -##### Preconditions - -- DUT supports the authenticator role of IEEE 802.1X. -- The DUT is configured with 802.1X enabled on its Open FH. -- The authentication server is set up and reachable (e.g., FreeRADIUS with appropriate certificates). -- The DUT is connected to a test tool or host representing a network device attempting to access the Open FH. - -##### Execution steps - -- 1) **Unauthenticated traffic attempt:** Connect the test tool to the DUT port. Without initiating any 802.1X (EAPoL) authentication, attempt to send standard Ethernet traffic such as ARP requests, ICMP echo (ping), and TCP SYN packets toward the DUT. -- 2) **Authenticated traffic attempt:** Configure the test tool to act as a supplicant and initiate a full 802.1X authentication using valid EAP-TLS credentials. Upon successful authentication and port authorization, re-attempt sending the same Ethernet traffic. - -##### Expected results - -- 1) **Unauthenticated traffic attempt:** The DUT blocks all Ethernet frames. The port remains in the unauthorized state. -- 2) **Authenticated traffic attempt:** The DUT authorizes the port and permits all Ethernet traffic. - -**Expected format of evidence:** Packet capture logs showing that no Ethernet traffic is permitted before authentication, and that traffic flows after successful authentication. - -#### 11.1.2.4 O-RU Authentication Lifecycle with Manufacturer and Operator Certificates - -**Requirement Name:** O-RU Authentication Lifecycle Validation - -**Requirement Reference:** SEC-CTL-OFHPLS-11, SEC-CTL-OFHPLS-12, clause 5.2.5.5.3.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The O-RU has a manufacturer installed X.509 Certificate. The procedure defined in IEEE 802.1X and shown in Figures 5.2.5.5.3.2-1/2 [5] is performed to authenticate and authorize a DUT within the Open FH. - -**Threat References:** T-FRHAUL-01A - -**DUT/s:** O-RU - -**Test Name:** TC\_ORU\_Authentication\_Lifecycle\_Validation - -**Purpose:** To verify that the O-RU implements the full 802.1X authentication lifecycle for secure onboarding and operational access, including: - -- Presence and use of a manufacturer-installed X.509 certificate during initial EAP-TLS authentication. - -- Placement into a provisioning VLAN following initial authentication as instructed by the authentication server to the authenticator. -- Enrolment into the operator’s PKI and installation of an operator-issued certificate. -- Re-authentication using the operator certificate and transition to operational VLAN. - -## Procedure and execution steps - -### Preconditions - -- The DUT supports IEEE 802.1X in the supplicant role. -- The DUT has not yet been enrolled in the operator’s PKI. -- The DUT is equipped with a valid manufacturer-installed X.509 certificate, provisioned by a trusted manufacturer CA. -- The DUT supports a certificate enrolment mechanism to obtain an operator-issued X.509 certificate after initial authentication. -- The authentication server is reachable by the authenticator (EXAMPLE: O-DU or switch connected to the O-RU) and provisioned with trust anchors (CA certificates) for both the manufacturer and operator CAs. It is configured to: - - Accept the manufacturer certificate for initial onboarding and instruct the authenticator to assign a provisioning VLAN. - - Accept the operator certificate for operational access and instruct the authenticator to assign an operational VLAN. - -### Execution steps - -- 1) Initial EAP-TLS authentication using manufacturer certificate - - The DUT performs EAP-TLS using its manufacturer certificate. - - Upon successful authentication, the authentication server instructs the authenticator to assign a provisioning VLAN to the port connected to the DUT. - - The authenticator transitions the DUT’s port to the authorized state and applies the provisioning VLAN. -- 2) Certificate enrolment into operator PKI - - Within the provisioning VLAN, the DUT connects to the operator PKI. - - The DUT requests and installs an operator-issued X.509 certificate. -- 3) Re-authentication using operator certificate - - The DUT restarts the supplicant interface. - - A second EAP-TLS exchange is initiated using the operator certificate. - - The authentication server validates the certificate and instructs the authenticator to assign the operational VLAN to the port connected to the DUT. - - The authenticator authorizes the port and applies the updated VLAN. - -### Expected results - -- The DUT successfully authenticates using its manufacturer certificate and is given access to the provisioning VLAN. -- The DUT successfully enrols in the operator PKI. - -- The DUT re-authenticates using the operator certificate and is given access to the operational VLAN. - -**Expected format of evidence:** - -- Packet captures showing two EAP-TLS authentication flows (manufacturer and operator certificates). -- Authentication server logs confirming identity and policy assignment for each certificate. -- DUT logs confirming success of certificate enrolment and the current certificate status. - -### 11.1.2.5 Unauthorized port behavior - -**Requirement Name:** Unauthorized port behavior for Authenticators - -**Requirement Reference:** SEC-CTL-OFHPLS-9, clause 5.2.5.5.3.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Authenticators place unauthorized ports in a state that allows only EAPOL (Ethertype 0x888E) traffic and blocks all other Ethernet frames until successful authentication. - -**Threat References:** T-FRHAUL-02 - -**DUT/s:** O-DU - -**Test Name:** TC\_OFHPLS\_Unauthorized\_Port\_Behavior - -**Purpose:** Verify that when the DUT is acting as an IEEE 802.1X authenticator, a port in unauthorized state only allows EAPOL frames (Ethertype 0x888E) and blocks all other Ethernet traffic until the supplicant successfully completes authentication. - -**Preconditions** - -- The DUT is configured as an 802.1X authenticator according to IEEE 802.1X-2020. -- The test equipment is configured as the 802.1X supplicant. -- The test equipment traffic generator able to send ARP, ICMP, and TCP and EAPOL (Ethertype 0x888E) frames. -- The DUT is configured with a reachable authentication server, including server IP address and shared secret. -- Packet capture is available on the test equipment side. - -**Execution Steps** - -1. Ensure the DUT port remains unauthorized - - Do not initiate EAP-TLS authentication from the test equipment. - - Confirm DUT port state is unauthorized. -2. Verify blocking of non-EAPOL traffic - - From the test equipment, send each of the following toward the DUT: - - ARP request - - ICMP Echo Request - - TCP SYN to any reachable port - -- Observe packet capture and DUT forwarding behaviour. -3. Verify EAPOL traffic is permitted - - From the test equipment, send EAPOL-Start frame toward the DUT. - - Confirm the DUT accepts EAPOL frames. - - Verify that the DUT relays the EAPOL payload to the authentication server (verified by RADIUS or Diameter messages). - 4. Trigger authentication - - Initiate EAP-TLS authentication. - - Confirm that: - 1. The authentication server returns success. - 2. The DUT transitions the controlled port to authorized state. - 3. Non-EAPOL traffic (ARP/ICMP/TCP) is now forwarded normally. - -#### Expected Results - -- Before authentication, the port remains unauthorized, and the DUT only allows EAPOL (0x888E) frames. -- Any non-EAPOL traffic (ARP, ICMP, TCP, etc.) is blocked and not forwarded. -- The DUT relays EAPOL payloads to the authentication server (verified by RADIUS or Diameter messages). -- Once authentication is completed successfully, the DUT changes the port state to authorized and Non-EAPOL traffic is forwarded as normal. - -#### Expected Format of Evidence - -- PCAP file showing: - - Non-EAPOL traffic dropped in unauthorized state. - - EAPOL forwarded to authentication server. - - Normal traffic forwarded only after authorization -- Logs showing port state transition (unauthorized to authorized) - -### 11.1.2.6 Authorization policy enforcement - -**Requirement Name:** Authorization policies for authorized ports - -**Requirement Reference:** SEC-CTL-OFHPLS-10, clause 5.2.5.5.3.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Authenticators apply authorization policies (e.g., VLAN tagging or traffic restriction) to authorized ports. - -**Threat References:** T-FRHAUL-02 - -**DUT/s:** O-DU - -**Test Name:** TC\_OFHPLS\_Authorization\_Policy\_Enforcement - -**Purpose:** Verify that the DUT applies authorization policies received from the RADIUS server (VLAN-ID or Filter-Id attributes) to authorized ports. - -#### Preconditions - -- DUT port is configured for IEEE 802.1X authenticator role. -- RADIUS server test equipment is configured with: - - Shared secret for the DUT–RADIUS connection. - - User credentials and certificates for EAP-TLS authentication. - - Authorization attributes to return in Access-Accept. -- The test equipment is configured as IEEE 802.1X supplicant. -- Packet capture is available on the test equipment side. - -#### Execution Steps - -1. Initiate EAP-TLS authentication from the supplicant (test equipment). -2. RADIUS server responds with Access-Accept including VLAN or Filter-Id attributes. -3. Verify DUT transitions the port to Authorized. -4. Send traffic from the supplicant toward the DUT. - - a) Confirm that egress traffic from the DUT shows the expected VLAN tag (if VLAN assigned). - - b) If Filter-Id is used, attempt permitted & blocked traffic types and verify enforcement. -5. Modify authorization attributes on the RADIUS server and re-authenticate. -6. Verify the DUT now applies the updated VLAN / Filter policy. - -#### Expected Results - -- After authentication, the DUT applies the VLAN ID or ACL policy provided by the RADIUS server. -- Permitted traffic is forwarded, and unauthorized traffic is blocked according to the applied policy -- Policy updates effective after re-authentication. - -#### Expected Format of Evidence - -- PCAP showing VLAN-tagged frames post-authorization. -- RADIUS server logs showing Access-Accept message and returned attributes. - -### 11.1.3 M-Plane - -#### 11.1.3.0 Applicability of Certificate Verification Based on Trust Anchor State - -The behavior of certificate-based authentication in the Open Fronthaul M-Plane depends on whether the DUT (typically the O-RU) has been provisioned with a valid, non-manufacturer trust anchor. This affects how certificate verification is performed during TLS or SSH-based mutual authentication: - -- Provisioned trust anchor (operational deployment state): The DUT verifies the peer's certificate chain according to the trust anchor and certificate validation rules defined in the O-RAN Security Protocols Specifications [2]. Mutual authentication is fully enforced. In this state, test cases requiring certificate verification apply in full. -- Manufacturer certificate only (factory fresh / pre-staging state): If the DUT has not been provisioned with a valid operator trust anchor, the DUT may skip verification of the peer certificate during the mTLS/SSH handshake, as described in O-RAN WG4 M-Plane specification [21], clause 6.4.0. In this state: - - Test steps that verify peer certificate validation is not applicable. - - Only authentication behavior observable from the DUT side (e.g., certificate presentation, handshake outcome) is assessed. - -Before executing any TLS- or SSH-based authentication test in this clause, the tester determines whether the DUT is in a provisioned state (an operator trust anchor is installed) or in a bootstrap state (only a manufacturer trust anchor is present). - -If the DUT is in a bootstrap state (manufacturer certificate only), the DUT may refuse to establish any TLS/SSH session other than the one required for certificate enrollment (e.g., CMPv2), as specified in O-RAN WG4 M-Plane specification [21], clause 6.4.0. - -### 11.1.3.1 SSH-based M-Plane authentication - -#### 11.1.3.1.0 Introduction - -The test cases outlined in this clause verify M-Plane authenticity over the Open FH interface using SSH. - -##### 11.1.3.1.1 Secure Password-Based Authentication in Open FH M-Plane Using SSH - -**Requirement Name:** M-Plane authenticity protection over Open FH interface using SSH - -**Requirement Reference:** REQ-SEC-OFHM-2, REQ-SEC-OFHM-3, clause 5.2.5.4.1, SEC-CTL-OFHM-6, clause 5.2.5.4.2 in O-RAN Security Requirements and Controls Specifications [5], SEC-CTL-OFHM-6 clause 5.2.5.4.2 in Security Requirements and Controls Specifications [5] - -**Requirement Description:** Password based Authentication for Open FH M-Plane over SSH across the Open FH interface. - -**Threat References:** T-O-RAN-05, T-FRHAUL-01, T-FRHAUL-02, T-MPLANE-01 - -**DUT/s:** O-RU - -**Test Name:** TC\_OFH\_MPLANE\_SSH-PASSWORD-BASED\_AUTHENTICATION\_AUTHORIZATION - -**Purpose:** The purpose of this test is to verify the SSH password-based authentication mechanisms on the Open FH interface by the O-RU. - -#### Procedure and execution steps - -##### Preconditions - -- The O-RU is properly configured and operational. -- Test equipment (potentially an O-DU or a dedicated SSH client simulator) is configured to establish SSH connections to the O-RU -- SSH is properly implemented and configured in the O-RU as defined in O-RAN WG4 Management Plane Specification [21], clause 5.4.2. - -## Execution steps - -- 1) Execute the test on the SSH protocol as defined in clause 6.2. -- 2) Positive Case: Successful SSH password-based authentication. - - Test the successful SSH password-based authentication of the test equipment by the O-RU. - - Establish an SSH connection from the test equipment (acting as SSH client) to the O-RU (acting as SSH server) using the SSH password. - -EXAMPLE 1: "Command: ssh -p 830 @" - -- Verify that the O-RU successfully authenticates the test equipment using the SSH password. - -- 3) Negative Case: Failed SSH password-based authentication. - - Test the handling of failed SSH password-based authentication attempts of the test equipment by the O-RU in different scenarios. - - Attempt with incorrect password - - Attempt to establish an SSH connection from the test equipment to the O-RU using an incorrect password. - -EXAMPLE 2: Command: ssh -p 830 @, using an incorrect password - -- Verify that the O-RU rejects the SSH connection due to the authentication failure. -- Attempt with non-existent username - - Attempt to establish an SSH connection using a username that does not exist in the O-RU's user database. - -EXAMPLE 3: Command: ssh -p 830 @ - -- Verify that the O-RU rejects the SSH connection, confirming that authentication does not proceed with non-existent usernames. - -## Expected Results - -For step 1): Expected results in clause 6.2 - -For step 2): - -- The SSH connection is successfully established using the SSH password. -- The O-RU validates the test equipment's SSH password for authentication. - -For step 3): - -- The SSH connection attempt fails due to the incorrect password. -- The O-RU identifies the authentication failure and denies access. -- The SSH connection attempt fails due to the invalid username. -- The O-RU identifies the authentication failure and prevents access. - -## Expected format of evidence - -For step 1): Logs and screenshots showing adherence to SSH protocol specifications as defined in O-RAN WG4 Management Plane Specification [21], clause 5.4.2. - -For step 2): Logs showing successful SSH authentication events. - -For step 3): Logs or error messages indicating failed SSH password-based authentication attempts for both incorrect password and invalid username scenarios. - -#### 11.1.3.1.2 Open FH M-Plane SSH-certificate-based authentication at O-RU - -**Requirement Name:** M-Plane authenticity protection over Open FH interface using SSH - -**Requirement Reference:** REQ-SEC-OFHM-2, REQ-SEC-OFHM-3, clause 5.2.5.4.1, SEC-CTL-OFHM-7, SEC-CTL-OFHM-8, clause 5.2.5.4.2 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Certificate based Authentication for Open FH M-Plane over SSH across the Open FH interface at O-RU. - -**Threat References:** T-O-RAN-05, T-FRHAUL-01, T-FRHAUL-02, T-MPLANE-01 - -**DUT/s:** O-RU - -**Test Name:** TC\_OFH\_MPLANE\_SSH-CERTIFICATE-BASED\_AUTHENTICATION \_O-RU - -**Purpose:** The purpose of this test is to verify the SSH-certificate-based authentication mechanisms on the Open FH interface at O-RU, using test equipment to simulate O-DU. - -#### Procedure and execution steps - -##### Preconditions - -- The O-RU is properly configured and operational. -- Test equipment capable of simulating SSH client functionality is prepared to represent the O-DU. -- SSH keys and certificates are generated and installed on both the O-RU and the test equipment. -- The CA root certificate/public key used to sign the certificates is configured on both O-RU and O-DU (test equipment) -- SSH is properly implemented and configured in the O-RU as defined in O-RAN WG4 Management Plane Specification [21], clause 5.4.2. -- The O-RU is in an operational state where an operator (non-manufacturer) trust anchor is provisioned and certificate-based SSH M-Plane access is enabled. If only a manufacturer certificate is present and the O-RU is configured to allow TLS/SSH interactions only for enrollment (e.g. CMPv2) as described in WG4 M-Plane [21] clause 6.4.0 and clause 11.1.3.0, this test is not applicable. - -##### Execution steps - -Execute the test on the SSH protocol as defined in clause 6.2. - -Authentication of O-DU by O-RU (test equipment simulates O-DU) - -O-RU is device under test and is the SSH server. O-DU or O-DU simulator is the SSH client. - -- Positive Case: Successful SSH-certificate-based authentication. - - Establish an SSH connection from the O-DU to the O-RU using the SSH certificate. - - Verify that the O-RU successfully authenticates the O-DU using the SSH certificate. -- Negative Case: Failed SSH-certificate-based authentication. - - Test the handling of failed SSH-certificate-based authentication attempts by the O-RU in different scenarios. - - Attempt with invalid certificate (Invalid due to public – private key mismatch) -Attempt to establish an SSH connection using an incorrect or invalid SSH certificate. - -EXAMPLE 1: "Command: **ssh -p 830 -i -o CertificateFile= @**" - -Verify that the O-RU rejects the SSH connection due to the authentication failure. - -- Attempt with invalid username - -Attempt to establish an SSH connection using a valid SSH certificate, but with a username that does not exist in the O-RU's system. - -EXAMPLE 2: "Command: **ssh -p 830 -i -o CertificateFile= @**" - -Verify that the O-RU rejects the SSH connection, confirming that the system does not authenticate usernames that are not registered or recognized. - -## Expected Results - -For step 1): Expected results in clause 6.2 - -For Positive Case: - -- The SSH connection is successfully established using the correct SSH certificate. -- The DUT (O-RU) validates the test equipment's SSH certificate for authentication. - -For Negative Case: - -- The SSH connection attempt fails due to the incorrect or invalid SSH certificate. -- The DUT identifies the authentication failure and denies access accordingly. - -## Expected format of evidence - -For step 1): Logs and screenshots showing adherence to SSH protocol specifications as defined in O-RAN WG4 Management Plane Specification [21], clause 5.4.2. - -For Positive Case: Logs showing successful SSH authentication and authorization events. - -For Negative Case: Logs or error messages indicating failed SSH-certificate-based authentication attempts for both invalid certificate and non-existent username scenarios. - -### 11.1.3.1.3 Void - -### 11.1.3.1.4 Open FH M-Plane SSH-certificate-based authentication at O-DU - -**Requirement Name:** M-Plane authenticity protection over Open FH interface using SSH - -**Requirement Reference:** REQ-SEC-OFHM-2, REQ-SEC-OFHM-3, clause 5.2.5.4.1, SEC-CTL-OFHM-7, SEC-CTL-OFHM-8, clause 5.2.5.4.2 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Certificate based Authentication for Open FH M-Plane over SSH across the Open FH interface at O-DU. - -**Threat References:** T-O-RAN-05, T-FRHAUL-01, T-FRHAUL-02, T-MPLANE-01 - -**DUT/s:** O-DU - -**Test Name:** TC\_OFH\_MPLANE\_SSH-CERTIFICATE-BASED\_AUTHENTICATION \_O-DU - -**Purpose:** The purpose of this test is to verify the SSH-certificate-based authentication and authorization mechanisms on the Open FH interface at O-DU, using test equipment to simulate O-RU. - -**Procedure and execution steps** - -## Preconditions - -- The O-DU is properly configured and operational. -- Test equipment capable of simulating SSH server functionality is prepared to represent the O-RU. -- SSH keys and certificates are generated and installed on both the O-DU and the test equipment. -- The CA root certificate/public key used to sign the certificates is configured on both O-RU and O-DU -- SSH is properly implemented and configured as defined in O-RAN WG4 Management Plane Specification [21], clause 5.4.2. - -## Execution steps - -- 1) Execute the test on the SSH protocol as defined in clause 6.2. - -Authentication of O-RU by O-DU (test equipment simulates O-RU) - -O-DU is device under test and is the SSH client. O-RU or O-RU simulator is the SSH server. - -- 2) Positive Case: Successful SSH-certificate-based authentication: - - Establish an SSH connection from the O-DU to the O-RU using the SSH certificate. - - Verify that the O-DU successfully authenticates the O-RU using the SSH certificate. -- 3) Negative Case: Failed SSH-certificate-based authentication. - - Test the handling of failed SSH-certificate-based authentication attempts by the O-DU in different scenarios. - - - - The O-RU or O-RU simulator CA root key/certificate is not configured on the O-DU or wrong CA root key/certificate is configured on the O-DU - - Attempt to establish an SSH connection from O-DU to O-RU/O-RU simulator with valid SSH certificate. - -EXAMPLE 1: "Command: **ssh -p 830 -i -o CertificateFile= @**" - -- Verify that the O-DU rejects the SSH connection due to the authentication failure. - -## Expected Results - -For step 1): Expected results as in clause 6.2 - -For step 2): Positive Case: - -- The SSH connection is successfully established using the correct SSH certificate. - -For step 3): Negative Case: - -- The SSH connection attempt fails due to the misconfiguration of O-RU CA root key/certificate in O-DU. -- The DUT is denied SSH connection due to authentication failure. - -## Expected format of evidence - -For step 1): Logs and screenshots showing adherence to SSH protocol specifications as defined in O-RAN WG4 Management Plane Specification [21], clause 5.4.2. - -For step 2): Positive Case: Logs showing successful SSH authentication events. - -For step 3): Negative Case: Logs or error messages indicating failed SSH-certificate-based authentication attempts. - -### 11.1.3.1.5 Open FH M-Plane SSH-key-based authentication at O-RU - -**Requirement Name:** M-Plane authenticity protection over Open FH interface using SSH - -**Requirement Reference:** Clause 5.4 in O-RAN WG4 Management Plane Specification [21], REQ-SEC-OFHM-2 clause 5.2.5.4.1 in security requirements and control specifications, SEC-CTL-OFHM-8 clause 5.2.5.4.2 in security requirements and control specifications [5] - -**Requirement Description:** SSH key-based Authentication for Open FH M-Plane over SSH across the Open FH interface at O-RU. - -**Threat References:** T-O-RAN-05, T-FRHAUL-01, T-FRHAUL-02, T-MPLANE-01 - -**DUT/s:** O-RU - -**Test Name:** TC\_OFH\_MPLANE\_SSH-KEY-BASED\_AUTHENTICATION\_O-RU - -**Purpose:** The purpose of this test is to verify the SSH-key-based authentication mechanisms on the Open FH interface between O-RU and O-DU, using test equipment as needed to simulate O-DU - -#### Procedure and execution steps - -##### Preconditions - -- The O-RU is properly configured and operational. -- Test equipment capable of simulating SSH client functionality is prepared to represent the O-DU. -- SSH private and public keys are generated for O-DU/O-DU simulator and O-RU. The public key of O-DU or O-DU simulator is installed on O-RU and public key of the O-RU is installed on the O-DU or O-DU simulator -- SSH is properly implemented and configured as defined in [2] clause 4.1. - -##### Execution steps - -Execute the test on the SSH protocol as defined in clause 6.2. - -O-RU is device under test and is the SSH server. O-DU or O-DU simulator is the SSH client - -- Positive Case: Successful SSH- key-based authentication. - - Establish an SSH connection from the O-DU or O-DU simulator to the O-RU using the SSH private key of O-DU - - Verify that the O-RU successfully authenticates the O-DU using the SSH key. -- Negative Case: Failed SSH-key-based authentication. - - Test the handling of failed SSH-key-based authentication attempts by the O-RU in different scenarios. - - Attempt with invalid private key of the O-DU - -Attempt to establish an SSH connection from O-DU or O-DU simulator to the O-RU using an incorrect or invalid SSH private key of the O-DU - -EXAMPLE 1: "Command: **ssh -p 830 -i @**" - -Verify that the O-RU rejects the SSH connection due to the authentication failure. - -- Attempt with invalid username -- Attempt to establish an SSH connection using a valid SSH private key, but with a username that does not exist in the O-RU's system. - -EXAMPLE 2: "Command: **ssh -p 830 -i @**" - -Verify that the O-RU rejects the SSH connection, confirming that the system does not authenticate usernames that are not registered or recognized. - -### Expected Results - -For step 1): Expected results in clause 6.2 - -Positive Case: - -- The SSH connection is successfully established using the correct SSH key -- The DUT (O-RU) validates the test equipment's SSH public key for authentication. -- The DUT identifies the authentication failure and denies access accordingly. - -Negative Case: - -- The SSH connection attempt fails due to the incorrect or invalid SSH private key. -- The SSH connection attempt fails due to invalid username. - -### Expected format of evidence - -For step 1): Logs and screenshots showing adherence to SSH protocol specifications as defined in [2] clause 4.1. - -Positive Case: Logs showing successful SSH authentication events. - -Negative Case: Logs or error messages indicating failed SSH-key-based authentication attempts for both invalid key and non-existent username scenarios. - -#### 11.1.3.1.6 Open FH M-Plane SSH-key-based authentication at O-DU - -**Requirement Name:** M-Plane authenticity protection over Open FH interface using SSH - -**Requirement Reference:** Clause 5.4 in O-RAN WG4 Management Plane Specification [21], REQ-SEC-OFHM-2 clause 5.2.5.4.1 in security requirements and control specifications, SEC-CTL-OFHM-7 clause 5.2.5.4.2 in security requirements and control specifications [5] - -**Requirement Description:** SSH key based Authentication for Open FH M-Plane over SSH across the Open FH interface at O-DU. - -**Threat References:** T-O-RAN-05, T-FRHAUL-01, T-FRHAUL-02, T-MPLANE-01 - -**DUT/s:** O-DU - -**Test Name:** TC\_OFH\_MPLANE\_SSH-KEY-BASED\_AUTHENTICATION\_O-DU - -**Purpose:** The purpose of this test is to verify the SSH-key-based authentication mechanisms on the Open FH interface between O-RU and O-DU, using test equipment as needed to simulate O-RU - -### Procedure and execution steps - -#### Preconditions - -- The O-DU device is properly configured and operational. -- Test equipment capable of simulating SSH server functionality is prepared to represent the O-RU. - -- SSH private and public keys are generated for O-DU and O-RU/O-RU simulator. The public key of the O-DU is configured in O-RU/O-RU simulator and the public key of the O-RU/O-RU simulator is configured in O-DU. -- SSH is properly implemented and configured as defined in [2] clause 4.1. - -### Execution steps - -Execute the test on the SSH protocol as defined in clause 6.2. - -O-DU is device under test and is the SSH client. O-RU or O-RU simulator is the SSH server. - -- Positive Case: Successful SSH-key-based authentication: - - Establish an SSH connection from O-DU to the O-RU using the valid SSH private key of O-DU - - Verify that the O-DU successfully authenticates the O-RU using the O-RU SSH public key.(The public key of the O-RU/O-RU simulator is present in known\_hosts file on the O-DU which is the ssh client) -- Negative Case: Failed SSH-key-based authentication. - - Test the handling of failed SSH-key-based authentication attempts by the O-DU in different scenarios. - - The O-RU or O-RU simulator public key is not present in the ssh known\_hosts file or invalid key is present in ssh known\_hosts file on the O-DU for the corresponding O-RU. - -Attempt to establish an SSH connection from O-DU to O-RU/O-RU simulator with valid private key of O-DU - -EXAMPLE 1: "Command: **ssh -p 830 -i @**" - -Verify that the O-DU rejects the SSH connection due to the authentication failure - -### Expected Results - -For step 1): Expected results in clause 6.2 - -Positive Case: - -- The SSH connection is successfully established using the valid SSH key -- The DUT (O-DU) validates the test equipment's SSH public key for authentication. - -Negative Case: - -- The SSH connection attempt fails - -### Expected format of evidence - -For step 1): Logs and screenshots showing adherence to SSH protocol specifications as defined in [2] clause 4.1. - -Positive Case: Logs showing successful SSH authentication events. - -Negative Case: Logs or error messages indicating failed SSH-key-based authentication attempts. - -## 11.1.3.2 SSH-based M-Plane integrity, confidentiality and replay protection - -**Requirement Name:** M-Plane confidentiality, integrity and replay protection over Open FH M-Plane interface using SSH - -**Requirement Reference:** REQ-SEC-OFHM-1, clause 5.2.5.4.1, SEC-CTL-OFHM-6, SEC-CTL-OFHM-7, SEC-CTL-OFHM-8, clause 5.2.5.4.2 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Confidentiality, integrity, and replay protection of M-Plane communications via SSH - -**Threat References:** T-O-RAN-05, T-FRHAUL-01, T-FRHAUL-02, T-MPLANE-01 - -**DUT/s:** O-RU, O-DU - -**Test Name:** TC\_OFH\_MPLANE\_SSH\_CONFIDENTIALITY\_INTEGRITY\_REPLAY - -**Purpose:** To verify the enforcement of security policies over the Open FH M-Plane interface, ensuring that sensitive data remains protected through confidentiality, integrity, and replay protection using SSH. - -### Procedure and execution steps - -#### Preconditions - -- The O-RU and O-DU devices are properly configured and operational. -- SSH keys and certificates are generated and installed on both the O-RU and O-DU devices. -- SSH configuration is enabled to enforce confidentiality, integrity and replay protection on the Open FH M-plane interface. -- SSH is properly implemented and configured as defined in O-RAN WG4 Management Plane Specification [21], clause 5.4.2. - -#### Execution steps - -- 1) Confidentiality verification: - - Establish an SSH connection between the O-RU and O-DU using proper SSH keys and certificates. - - Transmit data over this connection. - - Capture and analyse the transmitted data to verify encryption, ensuring confidentiality. -- 2) Integrity protection verification: - - During the same SSH session, modify the transmitted packets midway. - - Attempt to deliver the modified packets to the DUT. - - Verify that the DUT detects and discards these packets. -- 3) Replay protection verification: - - Replay previously captured packets to the DUT within the same SSH session. - - Confirm that the DUT detects and discards replayed packets. - -#### Expected Results - -- Confidentiality: All sensitive data transmitted over the Open FH M-Plane interface is encrypted, with no data exposed in clear text. -- Integrity protection: The DUT detects and discards altered packets, ensuring the data has not been tampered with. -- Replay protection: The DUT detects and discards replayed packets, preventing replay attacks. - -#### Expected format of evidence - -- Logs or screenshots showing SSH protocol adherence, as defined in O-RAN WG4 Management Plane Specification [21], clause 5.4.2. -- Evidence of secure communication sessions established over the Open FH M-Plane interface, including details of encryption verification. - -- Logs or screenshots showing the DUT's response to replayed and integrity-compromised packets, demonstrating the effectiveness of the security mechanisms in place. - -### 11.1.3.3 TLS-based M-Plane authentication - -#### 11.1.3.3.0 Introduction - -The test cases outlined in this clause verify TLS-based Open FH M-Plane authenticity. - -#### 11.1.3.3.1 Open FH M-plane TLS Authentication - -**Requirement Name:** M-Plane authenticity protection over Open FH interface using TLS - -**Requirement Reference:** REQ-SEC-OFHM-1, REQ-SEC-OFHM-2, clause 5.2.5.4.1, SEC-CTL-OFHM-1, SEC-CTL-OFHM-2, SEC-CTL-OFHM-3, clause 5.2.5.4.2 in O-RAN Security Requirements and Controls Specifications [5]. - -**Requirement Description:** TLS-based authentication for M-Plane over the Open FH interface - -**Threat References:** T-O-RAN-05, T-FRHAUL-01, T-FRHAUL-02, T-MPLANE-01 - -**DUT/s:** O-RU, O-DU - -**Test Name:** TC\_OFH\_MPLANE\_TLS\_AUTHENTICATION - -**Purpose:** Verify the TLS-based authentication mechanism for M-Plane over the Open FH interface by testing each DUT (O-RU or O-DU) independently. This test validates the correctness of the TLS handshake, certificate verification, and authentication process. - -#### Procedure and execution steps - -##### Preconditions - -- Valid and invalid certificates are available for the testing. -- Testing equipment acting as a client (for O-RU as DUT) or server (for O-DU a DUT). -- For positive case: The DUT and the testing equipment are configured with valid TLS certificates for mutual authentication. -- For negative case: The DUT and the testing equipment are configured with invalid TLS certificates. -- The DUT is provisioned with an operator (non-manufacturer) trust anchor and is configured to accept TLS-based NETCONF sessions on the Open FH M-Plane interface. If only a manufacturer certificate is present and the DUT is configured to allow TLS interactions only for certificate enrollment (e.g. CMPv2) as described in WG4 M-Plane [21] clause 6.4.0 and clause 11.1.3.0, this test is not applicable. -- - -##### Execution steps - -- 1) Execute the test on the TLS protocol as defined in clause 6.3. -- 2) Positive Case: Successful authentication. - - Test the successful authentication of the DUT over the Open FH M-Plane interface using TLS. - - For O-RU as the DUT - - The test equipment initiates a TLS handshake with the DUT (NETCONF server). - - The DUT presents its certificate to the client and validates the client certificate. - - Observe and validate that the DUT verifies the client's certificate. - -- Check O-RU logs or use network monitoring tools to confirm certificate verification and presentation. -- For O-DU as the DUT - - The DUT NETCONF client initiates a TLS handshake with the testing equipment (NETCONF server). - - The DUT presents its certificate to the server and validates the server certificate. - - Observe and validate that the DUT correctly verifies the server certificate. - - Check DUT logs or use network monitoring tools to confirm certificate verification and presentation. -- 3) Negative Case: Failed authentication. - - Test the failure of authentication over the Open FH M-Plane interface due to invalid certificates. - - For O-RU as DUT: - - The test equipment initiates a TLS handshake with the DUR, presenting an invalid certificate. - - Observe and validate that the DUT rejects the invalid certificate. - - Check DUT logs or network monitoring tools for certificate validation errors. - - Confirm that the TLS handshake fails and mutual authentication is not completed. - -## Expected Results - -For step 1): Expected results in clause 6.3 - -For step 2) positive case (successful authentication): The DUT successfully authenticates against the NETCONF client/server over the TLS-based Open FH M-Plane interface. The TLS handshake completes without errors, and both sides verify each other's certificates correctly. - -For step 3), negative case (failed authentication) The DUT correctly rejects the invalid certificate. The TLS handshake fails, and mutual authentication is not established. - -## Expected format of evidence - -For step 1): Logs showing adherence to TLS protocol specifications as defined in [2] clause 4.2. In case the logs do not show the required information, screenshots are used. - -For step 2), Logs indicating successful authentication. In case the logs do not show the required information, screenshots are used. - -For step 3), Logs indicating failed authentication. In case the logs do not show the required information, screenshots are used. - -### 11.1.3.3.2 Void - -## 11.1.3.4 TLS-based M-Plane integrity, confidentiality and replay protection - -**Requirement Name:** M-Plane confidentiality, integrity, and replay protection over Open FH M-plane interface using TLS - -**Requirement Reference:** REQ-SEC-OFHM-1, clause 5.2.5.4.1, SEC-CTL-OFHM-1, clause 5.2.5.4.2 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Confidentiality, integrity, and replay protection of M-Plane data using TLS - -**Threat References:** T-O-RAN-05, T-FRHAUL-01, 02, T-MPLANE-01 - -**DUT/s:** O-RU, O-DU - -**Test Name:** TC\_OFH\_MPLANE\_TLS\_CONFIDENTIALITY\_INTEGRITY\_REPLAY - -**Purpose:** To verify the confidentiality, integrity, and replay protection of Open FH M-Plane data using TLS. - -#### Procedure and execution steps - -##### Preconditions - -- O-RU, O-DU support TLS and are connected in a simulated or real network environment. -- The Open FH M-Plane interface is configured for testing. -- TLS is properly implemented and configured as defined in [2] clause 4.2. - -##### Execution steps - -- 1) Confidentiality verification: - - Establish a secure communication session over the Open FH M-Plane interface. - - Capture the network traffic during the session. - - Analyse the captured traffic to verify that all data is encrypted, ensuring confidentiality. -- 2) Integrity protection verification: - - Capture protected packets after the TLS handshake. - - Modify the captured packets. - - Inject the modified packets into the DUT. - - Confirm that the DUT discards the injected packets, e.g., does not deliver it to the higher layer. -- 3) Replay protection verification: - - Capture protected packets after the TLS handshake. - - Replay the captured packets into the DUT. - - Confirm that the DUT discards the replayed packets. - -##### Expected results - -- Confidentiality: All data transmitted over the Open FH M-Plane interface is encrypted, with no data exposed in clear text. -- Integrity protection: The DUT detects and discards altered packets, ensuring data has not been tampered with. -- Replay protection: The DUT detects and discards replayed packets, preventing replay attacks. - -##### Expected format of evidence - -The following evidence, in one or more formats as applicable, should be provided: - -- Logs or screenshots showing TLS protocol adherence, as defined in the O-RAN Security Protocols Specifications [2] clause 4.2. -- Logs or screenshots of the encrypted packets delivered to each TLS endpoint on the Open FH M-Plane. -- Logs or screenshots showing the DUT's response to replayed and integrity-compromised packets, demonstrating the effectiveness of the security mechanisms in place. - -#### 11.1.3.5 Open FH M-plane NACM Authorization validation - -**Requirement Name:** Open FH Interface security requirements - -**Requirement Reference:** REQ-SEC-OFHM-3 clause 5.2.5.4.1, REQ-NAC-MPLANE-FUN-1, REQ-NAC-MPLANE-FUN-2, REQ-NAC-MPLANE-FUN-3 clause 5.2.5.4.3, SEC-CTL-OFHM-4 clause 5.2.5.4.2, REQ-SEC-SLM-AAI-EVT-1 to REQ-SEC-SLM-AAI-EVT-10, clause 5.3.8.11.6, O-RAN Security Requirements and Controls Specifications [5] - -**Threat References:** T-O-RAN-05, T-FRHAUL-01, T-FRHAUL-02, T-MPLANE-01 - -**Requirement Description:** Requirements on Open FH Interface Least Privilege Access Control - -**DUT/s:** O-RU - -**Test Name:** TC\_OFH\_NACM\_VALIDATION - -**Purpose:** This test validates the Open FH interface security requirements of O-RU for NACM rule(s) enforcement. - -#### Procedure and execution steps - -##### Preconditions - -- The O-RU (Netconf server) is authenticated with O-RU controller (Netconf client) using mTLS or SSH as part of the NETCONF call home procedure of O-RU -- NACM configuration parameters are set to default value. -- The user used by Netconf client user is mapped to NETCONF user defined in O-RU. - -##### Execution steps - -- 1) Verify the NACM configuration as defined in clause 6.7.1 -- 2) Positive case: - - a. The netconf client user performs operation to validate global NACM enforcement control setting of - - enable-nacm = true - - read-default = deny - - write-default = deny - - exec-default = deny - - enable-external-groups = true - - b. The netconf client user performs operation as per the NACM rule sets for the “sudo” group which is defined in table 6.5-1 of O-RAN WG4 Management Plane Specification [21]. -- 3) Negative case: - - a. The netconf client user performs operation to violate the global NACM enforcement control setting of - - enable-nacm = true - - read-default = deny - - write-default = deny - - exec-default = deny - - enable-external-groups = true - - b. The netconf client user performs operation to violate NACM rule sets for the “sudo” group violating the rules defined in table 6.5-1 of O-RAN WG4 Management Plane Specification [21] - -#### Expected results - -- 1) Expected results as defined clause 6.7.1 -- 2) Positive case: - -The O-RU validates the Netconf client user operation as per the configured NACM rules and authorizes the operation and sends successful response. - -- 3) Negative case: - -The O-RU validates the Netconf client user operation as per the configured NACM rules and denies the operation and sends failure response. - -**Expected format of evidence:** - -- NACM Logs or screenshots showing successful and failed authorization. - -## 11.1.4 U-Plane - -### 11.1.4.1 U-Plane eCPRI Unexpected Input - -#### 11.1.4.1.0 Introduction - -The test cases in this clause focus on O-DU's and O-RU's capability to recognize, handle, and respond appropriately to such anomalies in user plane packets over the eCPRI. This includes scenarios where packets are malformed or when they present unexpected payload sizes. - -#### 11.1.4.1.1 Open FH U-Plane Malformed Packet - -**Requirement Name:** Handling and rejection of malformed or invalid user plane packets - -**Requirement Reference:** Clause 5.2.5.2.1 in O-RAN Security Requirements and Controls Specifications [5], REQ-SEC-TRAN-1, clause 5.3.4.1 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Detection and rejection of malformed or invalid Open FH user-plane eCPRI packets by an Open FH end point (O-DU, or O-RU) - -**Threat References:** T-FRHAUL-01, T-FRHAUL-02, T-UPLANE-01 - -**DUT/s:** O-RU, O-DU - -**Test Name:** TC\_OFH\_U-PLANE\_MALFORMED\_PACKET - -**Purpose:** The purpose of this test is to verify the O-DU's ability to handle and reject malformed or invalid user plane packets. - -#### Procedure and execution steps - -##### Preconditions - -- Test equipment supports the ability to establish an Open FH link with the DUT -- Test equipment supports the ability to generate Open FH U Plane packets (including malformed packets) -- A valid eCPRI connection is established between the DUT and the Test equipment. - -##### Execution steps - -- 1) Generate a user plane packet with invalid or malformed data, such as incorrect headers, corrupted payload, or unsupported formats. -- 2) Transmit the malformed packet over the eCPRI. - -- 3) Monitor the DUT's response and behaviour. -- 4) Verify that the DUT identifies and rejects the malformed packet. -- 5) Observe the impact on the DUT, such as error messages, logging, or abnormal behaviour. - -#### Expected Results - -- The DUT detects and rejects malformed or invalid user plane packets. -- It handles the rejection gracefully without affecting normal operation. -- Appropriate error messages or log entries are generated. - -#### Expected Format of Evidence: - -- Detailed execution logs of the performed steps. -- Logs containing the detection and rejection of the malformed packet. In case the logs do not show the required information, screenshots are used. - -### 11.1.4.1.2 Open FH U-Plane Unexpected Payload Size - -**Requirement Name:** Handling and rejection of malformed or invalid user plane packets - -**Requirement Reference:** Clause 5.2.5.2.1 in O-RAN Security Requirements and Controls Specifications [5], REQ-SEC-TRAN-1, clause 5.3.4.1 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Handling of unexpected payload sizes in user-plane packets by an Open FH end point (O-DU, or O-RU) - -**Threat References:** T-FRHAUL-01, T-FRHAUL-02, T-UPLANE-01 - -**DUT/s:** O-RU, O-DU - -**Test Name:** TC\_OFH\_U-PLANE\_UNEXPECTED\_PAYLOAD\_SIZE - -**Purpose:** The purpose of this test is to verify the DUT's ability to handle unexpected payload sizes in user plane packets. - -#### Procedure and execution steps - -##### Preconditions - -- Test equipment supports the ability to establish an Open FH link with the DUT -- Test equipment supports the ability to generate Open FH U Plane packets with unexpected payload sizes. -- A valid eCPRI connection is established between the DUT and the Test equipment. - -##### Execution steps - -- 1) Generate a user plane packet with an unexpected payload size, exceeding the normal or allowed range. -- 2) Transmit the packet with the unexpected payload size over the eCPRI. -- 3) Monitor the DUT's response and behaviour. -- 4) Verify that the DUT detects the unexpected payload size and takes appropriate action. -- 5) Observe the impact on the DUT, such as error handling, packet drops, or performance degradation. - -#### Expected Results - -- The DUT detects and handles unexpected payload sizes in user plane packets. -- It either rejects the packet or handles it with appropriate error handling mechanisms. -- The DUT maintains acceptable performance levels despite the unexpected payload size. - -**Expected Format of Evidence:** - -- Detailed execution logs of the performed steps. -- Logs containing the detection and handling of the unexpected payload size. In case the logs do not show the required information, screenshots are used. - -## 11.1.5 S-Plane - -### 11.1.5.0 Introduction - -The tests outlined in this clause focus on PTP as a packet-based clock synchronization protocol, which is susceptible to various network-based attacks. The LLS-C1, LLS-C2, and LLS-C3 configurations are considered in this assessment, as they rely on external timeTransmitters for synchronization. In contrast, LLS-C4 features a local PRTC (Primary Reference Time Clock) embedded within the O-RU, which provides time synchronization internally to the O-RU. This local PRTC operates independently and does not rely on an external timeTransmitter, such as an O-DU or a PRTC/T-GM in the Open Fronthaul (Open FH), to maintain synchronization. Consequently, there is no external network communication path that could be exploited to disrupt synchronization in the O-RU. Additionally, while LLS-C4 may be vulnerable to GNSS-related attacks, such attacks are not considered in the current set of tests. - -#### 11.1.5.1 DoS Attack against a timeTransmitter - -##### 11.1.5.1.0 Introduction - -The tests outlined in this clause evaluate the system's defence capabilities against DoS attacks targeting the timeTransmitter, especially in different LLS configurations. - -##### 11.1.5.1.1 DoS timeTransmitter LLS C1 C2 C3 - -Refer to the test case in clause 7.5.1 for test verification - -##### 11.1.5.1.2 DoS timeTransmitter LLS C4 - -**NOTE:** In LLS-C4, the local PRTC is embedded in the O-RU and provides time synchronization internally to the O-RU. This local PRTC does not depend on an external timeTransmitter, such as the O-DU or a PRTC/T-GM in Open FH, to maintain its synchronization. Therefore, there is no external network communication path where a DoS attack targeting a timeTransmitter could be launched. - -#### 11.1.5.2 Spoofing of timeTransmitters in the S-Plane - -##### 11.1.5.2.0 Introduction - -The tests presented in this clause focus on assessing the system's defences against potential spoofing attacks on timeTransmitters. Specifically, these tests examine scenarios where attackers may try to impersonate or manipulate the timeTransmitter's communications to disrupt accurate time synchronization. - -##### 11.1.5.2.1 Impersonation timeTransmitter - -**Requirement Name:** Spoofing Prevention for timeTransmitters in the S-Plane - -**Requirement Reference:** REQ-SEC-OFSP-2, clause 5.2.5.3.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The S-Plane provides a means to prevent spoofing of timeTransmitters - -**Threat References:** T-SPANE-02, T-SPANE-03 - -**DUT/s:** O-RU, O-DU - -**Test Name:** TC\_IMPERSONATION\_TIMETRANSMITTER - -**Purpose:** The purpose of this test is to verify the protection of the S-plane against an impersonation attack where an attacker sends fake ANNOUNCE messages to declare itself as the best clock (Grandmaster). The test evaluates whether the DUT correctly enforces vendor-implemented protection mechanisms to prevent time synchronization disruptions. - -### Procedure and execution steps - -#### Preconditions - -- The vendor documentation on the anti-spoofing mechanisms implemented for protecting the S-plane against timeTransmitter (EXAMPLE: 802.1X Port-based Network Access Control (PNAC), redundancy with multiple timeTransmitters, cryptographic integrity checks). -- The vendor detailed the test procedures they followed internally to validate their implementation, including the expected behavior and results of their security mechanisms under both normal and attack conditions. -- For LLS-C1: The timeTransmitter functionality is enabled on the O-DU. O-DU is acting as a timeTransmitter and directly synchronizes O-RU. -- For LLS-C2: One or more Ethernet switches are allowed in the Open Fronthaul network. O-DU acting as timeTransmitter to distribute network timing toward O-RU. -- For LLS-C3: One or more PRTC/T-GM are implemented in the Open Fronthaul network to distribute network timing toward O-DU and O-RU. -- A network monitoring tool is set up to capture and analyse network traffic. - -#### Execution steps - -- 1) Verify that the vendor documentation provides clear descriptions of security mechanisms for preventing timeTransmitter spoofing. -- 2) Use a network monitoring tool to observe normal time synchronization traffic. -- 3) Establish a baseline for comparison before testing. -- 4) Follow the vendor's test procedures to reproduce the vendor's internal tests. -- 5) Compare the obtained results with the documented results from the vendor to verify if the DUT behaves as expected. -- 6) Verify that the DUT rejects the impersonated clock and maintains the synchronization based on the legitimate timeTransmitter. -- 7) If gaps are found in vendor-provided tests, propose further test steps to enhance security validation. - -#### Expected Results - -- The vendor's test cases are sufficient, and security mechanisms perform as expected. -- The DUT detects and mitigates the impersonation attack. -- The synchronization status remains stable and accurate. -- The actual test results match the vendor's documented expected results. -- If insufficient tests are found: - - The tester documents missing areas and recommends further test procedures. - - The vendor may be required to implement additional security measures. - -**Expected Format of Evidence:** - -- Summary of the vendor's provided test procedures and security mechanisms. -- Logs showing successful execution of vendor tests. -- Statement confirming whether vendor tests are adequate or insufficient. -- Recommendations for additional security validations (if necessary). - -#### 11.1.5.2.2 Rogue PTP Instance - -**Requirement Name:** Spoofing Prevention for timeTransmitter in the S-Plane - -**Requirement Reference:** REQ-SEC-OFSP-2, clause 5.2.5.3.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The S-Plane provides a means to prevent spoofing of master clocks - -**Threat References:** T-SPLANE-02, T-SPLANE-03 - -**DUT/s:** O-RU, O-DU - -**Test Name:** TC\_ROGUE\_PTP\_INSTANCE - -**Purpose:** The purpose of this test is to verify the protection of the S-plane against an attacker sending manipulated or malicious ANNOUNCE messages to declare itself as the best clock (Grandmaster). The test evaluates whether the DUT correctly enforces vendor-implemented protection mechanisms to prevent time synchronization disruptions. - -#### Procedure and execution steps - -##### Preconditions - -- The vendor documentation describes the security mechanisms implemented to prevent rogue PTP instances. -- The vendor details the test procedures they followed to validate their implementation, including the expected behaviour and results of their security mechanisms under both normal and attack conditions. -- For LLS-C1: The timeTransmitter functionality is enabled on the O-DU. O-DU is acting as a timeTransmitter and directly synchronizes O-RU. -- For LLS-C2: One or more Ethernet switches are allowed in the Open Fronthaul network. O-DU acting as timeTransmitter to distribute network timing toward O-RU. -- For LLS-C3: One or more PRTC/T-GM are implemented in the Open Fronthaul network to distribute network timing toward O-DU and O-RU. -- A network monitoring tool is set up to capture and analyse network traffic. - -##### Execution steps - -- 1) Verify that the vendor documentation provides clear descriptions of security mechanisms for preventing rogue PTP instances. -- 2) Use a network monitoring tool to observe normal time synchronization traffic. -- 3) Establish a baseline for comparison before testing. -- 4) Follow the vendor's test procedures to reproduce the vendor's internal tests. -- 5) Compare the obtained results with the documented results from the vendor to verify if the DUT behaves as expected. -- 6) Verify that the DUT detects and rejects the attacker's proposed Grandmaster candidate. - -- 7) If gaps are found in vendor-provided tests, propose further test steps to enhance security validation. - -### Expected Results - -- The vendor's test cases are sufficient, and security mechanisms perform as expected. -- The DUT detects and rejects rogue PTP messages. -- The synchronization remains stable and accurate. -- The actual test results match the vendor's documented expected results. -- If insufficient tests are found: - - The tester documents missing areas and recommends further test procedures. - - The vendor may be required to implement additional security measures. - -### Expected Format of Evidence: - -- Summary of the vendor's provided test procedures and security mechanisms. -- Logs showing successful execution of vendor tests. -- Statement confirming whether vendor tests are adequate or insufficient. -- Recommendations for additional security validations (if necessary). - -## 11.1.5.3 Clock Accuracy Protection Against MITM Attacks - -### 11.1.5.3.1 Selective Interception and Removal of PTP Timing Packets - -**Requirement Name:** Clock Accuracy Protection Against MITM Attacks - -**Requirement Reference:** REQ-SEC-OFSP-3, clause 5.2.5.3.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Protection of the S-plane from attacks involving selective loss of PTP timing packets - -**Threat References:** T-SPLANE-04, T-SPLANE-05 - -**DUT/s:** O-RU, O-DU - -**Test Name:** TC\_SELECTIVE\_INTERCEPTION\_REMOVAL\_PTP\_TIMING\_PACKETS - -**Purpose:** The purpose of this test is to verify the resilience of the S-plane against an attack where PTP timing packets are selectively intercepted and removed. - -### Procedure and execution steps - -#### Preconditions - -- For LLS-C2: One or more Ethernet switches are allowed in the Open Fronthaul network. O-DU acting as master to distribute network timing toward O-RU. -- For LLS-C3: One or more PRTC/T-GM are implemented in the Open Fronthaul network to distribute network timing toward O-DU and O-RU. -- The network monitoring tool is set up to capture and analyse network traffic between the O-RU and O-DU. - -#### Execution steps - -- 1) Set up the test environment with the O-RAN O-RU, O-DU, and other relevant network components. -- 2) Configure the network monitoring tool to capture PTP timing packets between the O-RU and O-DU. - -- 3) Start the network monitoring tool to capture the initial state of PTP timing packets. - - 4) Simulate an attack by using a packet manipulation tool to selectively intercept and remove specific PTP timing packets. - - For LLS-C2, use a network device or software with packet interception capabilities to intercept PTP timing packets between the O-RU and O-DU. Modify the intercepted packets to selectively remove PTP timing packets. - - For LLS-C3, use a network device or software capable of deep packet inspection (DPI) to intercept and analyse PTP timing packets. Modify the intercepted packets to selectively remove PTP timing packets. - - 5) Verify the functionality of the O-RU and O-DU during the attack simulation. - - 6) Observe the synchronization status and the impact on timing accuracy between the O-RU and O-DU. - - 7) Capture and analyse the network traffic using the network monitoring tool during the attack simulation. -- NOTE: The network monitoring tool can be Wireshark or tcpdump, configured to capture packets on the interfaces between the O-RU, O-DU and to identify the intercepted and removed PTP timing packets. -- 8) Stop the network monitoring tool to finalize the captured traffic. - -### Expected Results - -- Detection of missing PTP timing packets: The S-plane is able to detect the absence of specific PTP timing packets that were selectively intercepted and removed. -- Synchronization maintenance: Despite the missing PTP timing packets, the O-RU and O-DU still maintain synchronization. Any deviations from expected synchronization are minimal and within acceptable thresholds. -- Corrective actions: Upon detecting the missing PTP timing packets, the O-RU and O-DU initiate predefined corrective actions to restore synchronization and mitigate the effects of the missing packets. -- Network traffic analysis: The captured network traffic clearly shows the instances where specific PTP timing packets were intercepted and removed. -- No system failures: The system (O-RU and O-DU) doesn't experience any catastrophic failures or shutdowns due to the missing PTP timing packets. - -### Expected Format of Evidence: - -The following evidence, in one or more formats as applicable, should be provided for each configuration (LLS-C2, LLS-C3): - -- Recorded network traffic captured by the monitoring tool during the attack simulation showing selective interception and removal of PTP timing packets in LLS-C2 (with Ethernet switches) and LLS-C3 (with PRTC/T-GM). -- Observations and analysis of the impact on synchronization and timing accuracy. -- Any issues or anomalies encountered during the attack simulation. - -#### 11.1.5.3.2 Delay Attack on PTP Timing Packets - -**Requirement Name:** Clock Accuracy Protection Against MITM Attacks - -**Requirement Reference:** REQ-SEC-OFSP-3, clause 5.2.5.3.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Protection of S-plane synchronization from PTP timing packet delay attacks - -**Threat References:** T-SPLANE-04, T-SPLANE-05 - -**DUT/s:** O-RU, O-DU - -**Test Name:** TC\_DELAY\_ATTACK\_PTP\_TIMING\_PACKETS - -**Purpose:** The purpose of this test is to verify the S-plane's resilience against a delay attack on PTP timing packets. - -#### Procedure and execution steps - -##### Preconditions - -- For LLS-C2: One or more Ethernet switches are allowed in the Open Fronthaul network. O-DU acting as master to distribute network timing toward O-RU. -- For LLS-C3: One or more PRTC/T-GM are implemented in the Open Fronthaul network to distribute network timing toward O-DU and O-RU. -- Time synchronization is established and operational within the network. - -##### Execution steps - -- 1) Start the network monitoring tool to capture the initial state of PTP timing packets. -- 2) Simulate an attack by introducing delays in PTP timing packets using a network emulation tool. -- For LLS-C2 and LLS-C3, use a custom script or tool that supports packet manipulation and delay to introduce artificial delays in PTP timing packets between the O-RU and O-DU or between PRTC/T-GM devices. -- 3) Verify the functionality of the O-RU and O-DU during the delay attack on PTP timing packets. -- 4) Observe the synchronization status and timing accuracy within the LLS configuration. - -##### Expected Results - -- The S-plane detects the delay attack on PTP timing packets and applies appropriate measures to mitigate the impact within all LLS configurations. -- The O-RU and O-DU detects the delayed PTP timing packets, compensate for the introduced delays, and maintain synchronization. - -##### Expected Format of Evidence: - -The following evidence, in one or more formats as applicable, should be provided for each configuration (LLS-C2, LLS-C3): - -- Recorded network traffic captured by the monitoring tool during the attack. This includes logs showing the introduction of delays in PTP timing packets for LLS-C2 (with Ethernet switches) and LLS-C3 (with PRTC/T-GM). -- Observations and analysis of the impact on synchronization and timing accuracy within each LLS configuration. -- Any issues or anomalies encountered during the attack simulation. - -## 11.2 Y1 - -### 11.2.1 Y1 Authenticity - -**Requirement Name:** Y1 protection in terms of authenticity - -**Requirement Reference-**NEAR-RT-9, clause 5.1.3.2.4, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Mutual authentication of Near-RT RIC and Y1 consumers to ensure Y1 interface authenticity - -**Threat References:** T-Y1-01, T-Y1-02, T-Y1-03 - -**DUT/s:** Near-RT RIC, Y1 consumers - -**Test Name:** TC\_Y1\_AUTHENTICATION - -**Purpose:** The purpose of this test is to verify the authenticity of the Y1 interface, ensuring that only legitimate and mutually authenticated Near-RT RIC, Y1 consumers can participate in the communication over the Y1 interface. - -## Procedure and execution steps - -### Preconditions - -- Near-RT RIC & Y1 Consumers support mTLS and be connected in a simulated/real network environment. -- The test environment is set up with the Y1 interface configured. -- The tester has access to the original data transported over the Y1 interface. -- mTLS is properly implemented and configured as defined in [2] clause 4.2. - -### Execution steps - -- 1) Execute the test on the mTLS protocol as defined in clause 6.3. -- 2) Valid Authentication Certificates (positive case): - - The tester sends a request to establish a connection with the Y1 interface using valid authentication certificates. - - The tester verifies the mutual certificate verification between Near-RT RIC and Y1 consumers. - - The tester captures and analyses the response received from the Y1 interface. -- 3) Invalid Authentication Certificates (negative case): - - The tester sends a request to establish a connection with the Y1 interface with invalid certificates. - - The tester captures and analyses the response received from the Y1 interface. -- 4) No Authentication Certificates (Negative Case): - - The tester sends a request to establish a connection without any certificates. - - The tester captures and analyses the response from the Y1 interface. - -## Expected results - -For 1) Expected results in clause 6.3 - -For 2) 'Valid Authentication Certificates': The Y1 interface accepts the valid certificates and responds with a successful authentication message. The mutual certificate verification process is successful. - -For 3) 'Invalid Authentication Certificates': The connection attempt is rejected, and an authentication failure message is received. The mutual certificate verification process fails due to the use of invalid certificates. - -For 4) 'No Authentication Certificates': The connection attempt is rejected, and an authentication failure message is received. The mutual certificate verification process fails due to the absence of certificates. - -## Expected Format of Evidence: - -The following evidence, in one or more formats as applicable, should be provided: - -- Logs and screenshots showing adherence to mTLS protocol specifications as defined in [2] clause 4.2. -- Logs of authentication requests and responses on the Y1 interface - -- Logs of the mutual certificate verification process. -- Screenshots or logs of error messages or unusual behaviours for both invalid and no certificate scenarios. - -## 11.2.2 Y1 confidentiality, integrity, and replay protection - -**Requirement Name:** Y1 protection in terms of confidentiality, integrity and replay - -**Requirement Reference:** SEC-CTL-NEAR-RT-11, clause 5.1.3.2.4, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Confidentiality, integrity, and replay protection of Y1 interface communications - -**Threat References:** T-Y1-01, T-Y1-02, T-Y1-03 - -**DUT/s:** Near-RT RIC, Y1 consumers - -**Test Name:** TC\_Y1\_CONFIDENTIALITY\_INTEGRITY\_REPLAY - -**Purpose:** To verify the enforcement of security policies over the Y1 interface, ensuring that sensitive data remains protected through confidentiality, integrity, and replay protection. - -### Procedure and execution steps - -#### Preconditions - -- Near-RT RIC and Y1 consumers support TLS and connected within simulated or real network environments. -- The Y1 interface is configured for testing. -- TLS is properly implemented and configured as defined in [2] clause 4.2. - -#### Execution steps - -- 1) Confidentiality verification: - - Establish a secure communication session over the Y1 interface. - - Capture the network traffic during the session. - - Analyse the captured traffic to verify that all data is encrypted, ensuring confidentiality. -- 2) Integrity protection verification: - - Capture protected packets after the TLS handshake. - - Modify the captured packets. - - Inject the modified packets to the DUT. - - Confirm that the DUT discards the injected packets, e.g., does not deliver it to the higher layer. -- 3) Replay protection verification: - - Capture protected packets after the TLS handshake. - - Replay the captured packets to the DUT. - - Confirm that the DUT discards the replayed packets. - -#### Expected results - -- Confidentiality: All sensitive data transmitted over the Y1 interface is encrypted, with no data exposed in clear text. -- Integrity protection: The DUT detects and discards altered packets, ensuring data has not been tampered with. - -- Replay protection: The DUT detects and discards replayed packets, preventing replay attacks. - -#### Expected Format of Evidence: - -The following evidence, in one or more formats as applicable, should be provided: - -- Logs showing TLS protocol adherence, as defined in the O-RAN Security Protocols Specifications [2] clause 4.2. In case the logs do not show the required information, screenshots are used. -- Logs with the evidence of secure communication sessions established over the Y1 interface, including details of encryption verification. -- Logs showing the DUT's response to replayed and integrity-compromised packets, demonstrating the effectiveness of the security mechanisms in place. In case the logs do not show the required information, screenshots are used. - -### 11.2.3 Y1 Authorization - -**Requirement Name:** Y1 protection in terms of authorization - -**Requirement Reference:** SEC-CTL-NEAR-RT-10, clause 5.1.3.2.4, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Near-RT RIC Y1 Interface supports OAuth 2.0 based authorization. - -**Threat References:** T-Y1-01 - -**DUT/s:** Near-RT RIC - -**Test Name:** TC\_Y1\_AUTHORIZATION - -**Purpose:** The purpose of this test is to validate that the Y1 interface enforces an authorization mechanism to prevent unauthorized access. - -#### Procedure and execution steps - -##### Preconditions - -- Near-RT RIC Y1 Interface supports OAuth 2.0 and is the Resource Server -- Y1 Consumer may be real or simulated -- Test 6.6.2 Scenario: - - Preconditions enabled as specified in Clause 6.6.2 (to validate DUT as O-Auth2.0 supported Resource Server) - - Y1 Consumer configured with the permitted role to have access to the resource to be requested -- Not permitted role: - - Y1 Consumer configured with a role, that does not permit access to the resource -- Invalid Access Token Scenario: - - Y1 Consumer is configured to present an invalid access token -- No Access Token Scenario: - - Y1 Consumer is configured to present no access token - -##### Execution steps - -- 1) Execute the test to verify OAuth 2.0 enabled Resource Server as defined in clause 6.6.2. This test includes the check for Y1 consumer access with Valid access tokens (Positive Case) - -- Verify the validation required for valid access token as defined in clause 6.6.2 -- 2) Not permitted role (negative case): -- The Y1 Consumer sends a request directly to the resource server to access protected resources using a valid access token, however the role does not permit access to the resource. - - Verify that Resource Server rejects access to the requested resource as Consumer does not have permitted role. -- 3) Invalid access tokens (negative case): -- The Y1 Consumer sends a request directly to the resource server to access protected resources using an incorrect access token. - - Verify that Resource Server rejects access to the requested resource due to incorrect access token. -- 4) No access tokens (negative case): -- The Y1 Consumer sends a request directly to the resource server to access protected resources without providing any access token. - - Verify that Resource Server rejects access to the requested resource without an access token. - -### Expected Results - -For 1) Expected results as in clause 6.6.2 - -For 2) Not permitted role: The DUT verifies the role of the Y1 consumer for the requested resource, as not allowed/incorrect, and the access is rejected, and an access failure message is generated. - -For 3) Incorrect access tokens: The DUT verifies the access token, and token being invalid, the access is rejected, and an access failure message is generated. - -For 4) No access tokens: The DUT rejects the access due to the absence of tokens, and an appropriate error or unauthorized access message is generated. - -### Expected Format of Evidence: - -The following evidence, in one or more formats as applicable, should be provided: - -- Logs of the request sent to access protected resources using valid access tokens. -- Logs highlighting the successful authorization message. In case the logs do not show the required information, screenshots are used. -- Logs of the request sent to access protected resources when role is not permitted, when using invalid access tokens and no access token. -- Logs showing the rejection of the access and the access failure message when consumer role is not permitted, consumer configured to present invalid access token and consumer configured to present no access token are used. In case the logs do not show the required information, screenshots are used. - -## 11.3 O1 - -### 11.3.1 O1 Authenticity - -**Requirement Name:** O1 protection in terms of authenticity - -**Requirement Reference:** SEC-CTL-O1-2, SEC-CTL-O1-5, clause 5.2.2.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Authenticity of the O1 interface ensuring communication only between authenticated O-RAN NF - -**Threat References:** T-MPLANE-01, T-O-RAN-05 - -**DUT/s:** SMO, O-CU, O-DU, Near-RT RIC - -**Test Name:** TC\_O1\_AUTHENTICATION - -**Purpose:** The purpose of this test is to verify the authenticity of the O1 interface, ensuring that only legitimate and authenticated O-RAN NFs can participate in the communication over the O1 interface. - -#### Procedure and execution steps - -##### Preconditions - -- SMO, O-CU, O-DU, Near-RT RIC support mTLS and be connected in simulated/real network environment. -- The test environment is set up with O1 interface configured. -- The tester has access to the original data transported over the O1 interface. -- mTLS is properly implemented and configured as defined in [2] clause 4.2. - -##### Execution steps - -- 1) Execute the test on the mTLS protocol as defined in clause 6.3. -- 2) Valid Authentication Certificates (positive case): - - The tester sends a request to establish a connection with the O1 interface using valid authentication certificates. - - The tester verifies the mutual certificate verification between the ORAN NFs - - The tester captures and analyses the response received from the O1 interface. -- 3) Invalid Authentication Certificates (negative case): - - The tester sends a request to establish a connection with the O1 interface with invalid certificates. - - The tester captures and analyses the response received from the O1 interface. -- 4) No Authentication Certificates (Negative Case): - - The tester sends a request to establish a connection without any certificates. - - The tester captures and analyses the response from the O1 interface. - -#### Expected results - -For 1) Expected results in clause 6.3 - -For 2) 'Valid Authentication Certificates': The O1 interface accepts the valid certificates and responds with a successful authentication message. The mutual certificate verification process is successful. - -For 3) 'Invalid Authentication Certificates': The connection attempt is rejected, and an authentication failure message is received. The mutual certificate verification process fails due to the use of invalid certificates. - -For 4) 'No Authentication Certificates': The connection attempt is rejected, and an authentication failure message is received. The mutual certificate verification process fails due to the absence of certificates. - -#### Expected Format of Evidence: - -The following evidence, in one or more formats as applicable, should be provided: - -- Logs and screenshots showing adherence to mTLS protocol specifications as defined in [2] clause 4.2. -- Logs of authentication requests sent to the O1 interface. -- Logs of the mutual certificate verification process. -- Screenshots or logs of error messages or unusual behaviours for both invalid and no certificate scenarios. - -### 11.3.2 O1 confidentiality, integrity and replay protection - -**Requirement Name:** O1 protection in terms of confidentiality, integrity and replay - -**Requirement Reference:** SEC-CTL-O1-1, SEC-CTL-O1-4, clause 5.2.2.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Confidentiality, integrity, and replay protection of O1 interface communications - -**Threat References:** T-MPLANE-01, T-O-RAN-05 - -**DUT/s:** SMO, O-CU, O-DU, Near-RT RIC - -**Test Name:** TC\_O1\_CONFIDENTIALITY\_INTEGRITY\_REPLAY - -**Purpose:** To verify the enforcement of security policies over the O1 interface, ensuring that sensitive data remains protected through confidentiality, integrity, and replay protection. - -#### Procedure and execution steps - -##### Preconditions - -- SMO, O-CU, O-DU, Near-RT RIC support TLS and be connected in simulated/real network environment. -- The O1 interface is configured for testing. -- TLS is properly implemented and configured as defined in [2] clause 4.2. - -##### Execution steps - -- 1) Confidentiality verification: - - Establish a secure communication session over the O1 interface. - - Capture the network traffic during the session. - - Analyse the captured traffic to verify that all data is encrypted, ensuring confidentiality. -- 2) Integrity protection verification: - - Capture protected packets after the TLS handshake. - - Modify the captured packets. - - Inject the modified packets to the DUT. - - Confirm that the DUT discards the injected packets, e.g., does not deliver it to the higher layer. -- 3) Replay protection verification: - - Capture protected packets after the TLS handshake. - - Replay the captured packets to the DUT. - - Confirm that the DUT discards the replayed packets. - -#### Expected results - -- Confidentiality: All sensitive data transmitted over the O1 interface is encrypted, with no data exposed in clear text. -- Integrity protection: The DUT detects and discards altered packets, ensuring data has not been tampered with. -- Replay protection: The DUT detects and discards replayed packets, preventing replay attacks. - -#### Expected Format of Evidence: - -The following evidence, in one or more formats as applicable, should be provided: - -- Logs or screenshots showing TLS protocol adherence, as defined in the O-RAN Security Protocols Specifications [2] clause 4.2. -- Evidence of secure communication sessions established over the O1 interface, including details of encryption verification. -- Logs or screenshots showing the DUT's response to replayed and integrity-compromised packets, demonstrating the effectiveness of the security mechanisms in place. - -### 11.3.3 O1 Interface Network Configuration Access Control Model (NACM) Validation - -#### 11.3.3.0 Introduction - -Following zero trust principles, O-RAN O1 interface shall enforce confidentiality, integrity and authenticity through an encrypted transport, and shall support least privilege access control using the network configuration access control model. The network configuration access control model (NACM) [14] provides the means to restrict access for users to a preconfigured subset of all available NETCONF protocol operations and content. - -The security test case in this clause validates the NACM enforcement on the O-RAN architecture element O1 interface for the role-based access control. - -#### 11.3.3.1 O1 Interface NACM Validation - -**Requirement Name:** O1 Interface security requirements - -**Requirement Reference:** REQ-NAC-FUN-1 to REQ-NAC-FUN-10, REQ-SEC-SLM-AAI-EVT-1 to REQ-SEC-SLM-AAI-EVT-10, clause 5.3.8.11.6 clause 5.2.2.3, O-RAN Security Requirements and Controls Specifications [5] - -**Threat References:** T-O-RAN-02, T-O-RAN-06 - -**Requirement Description:** Requirements of O1 Interface Confidentiality, Integrity & Authenticity protection and Least Privilege Access Control - -**DUT/s:** Non-RT RIC, Near-RT RIC, O-CU-CP, O-CU-UP, O-DU - -**Test Name:** TC\_O1\_NACM\_VALIDATION - -**Purpose:** O-RAN architecture elements managed by SMO through O1 interface shall support secured NETCONF sessions over TLS and role-based least privilege access control enforced by NACM [14]. This test validates the O1 interface security requirements of the O-RAN architecture elements with the focus on role-based NACM rule(s) set enforcement. - -#### Procedure and execution steps - -#### Preconditions - -DUT shall be the O-RAN architecture element with: - -- IP enabled O1 interface, reachable from the authentication server - -- Valid certificate loaded for the server and necessary certificate authorities (CAs) -- Client's root CA required to validate NETCONF client certificate -- Valid TLS Client-to-NETCONF username mapping -- Configure the O-RAN element with the SMO details (SMO network address and port) -- The NACM configurations are set to default values as specified in clause 5.2.2.3 defined in [5] - -### Execution steps - -- 1) Verify the NACM configurations as defined in clause 6.7.1 - -First set up a host/device with TLS client software installed, valid client certificates, keys, root CA certificate for the server (O-RAN architecture element), and all intermediate CA certificates required to validate the client certificate. - -The following test steps shall be validated: - -- 1) Initiate NETCONF call home procedure from the O-RAN element towards SMO over O1 interface. - -NOTE: The O-RAN element may initiate the NETCONF call home procedure as part of its initialization automatically. - -- 2) SMO connects with O-RAN element over O1 interface using TLS 1.2 or TLS 1.3 - if available with a user account from the O1\_nacm\_management group -- 3) Verify the session is established and mapped to the correct NETCONF user -- 4) Verify the global NACM enforcement control setting of - - enable-nacm = true - - read-default = deny - - write-default = deny - - exec-default = deny - - enable-external-groups = true -- 5) Verify the NACM rule sets for the following pre-defined groups - - O1\_nacm\_management - - O1\_user\_management - - O1\_network\_management - - O1\_network\_monitoring - - O1\_software\_management for only PNFs -- 6) Close the NETCONF session and TLS connection - -Upon availability of the NETCONF operations set(s) definition per NACM group, the NACM rule set(s) enforcement by the DUT shall be validated for each of those pre-defined groups listed above. - -### Expected results - -- 1) Expected results as defined clause 6.7.1 -- 2) The O-RAN architecture element supports the NETCONF over TLS session over its O1 interface and NACM enforcement control settings. - -### Expected format of evidence: - -Logs or screenshots showing: - -- O1 interface setup. -- Valid server certificate and CA details. -- Client's root CA and intermediate CA certificates. -- TLS Client-to-NETCONF username mapping. -- O-RAN element configured with SMO details. -- Initiation of NETCONF call home procedure. -- TLS 1.2 or TLS 1.3 connection establishment. -- Correct NETCONF user session mapping. - -## 11.4 O2 - -### 11.4.1 O2 Authenticity - -**Requirement Name:** O2 protection in terms of authenticity - -**Requirement Reference:** SEC-CTL-O-CLOUD-INTERFACE-3, clause 5.1.8.9.2, O-RAN Security Requirements and Controls Specifications [5] - -**Threat References:** T-O2-01 - -**DUT/s:** SMO, O-Cloud - -**Test Name:** TC\_O2\_AUTHENTICATION - -**Purpose:** The purpose of this test is to verify the authenticity of the O2 interface, ensuring that only legitimate and authenticated O-Cloud and SMO can participate in the communication over the O2 interface. - -#### Procedure and execution steps - -##### Preconditions - -- O-Cloud and SMO support mTLS and be connected in simulated/real network environment. -- The test environment is set up with O2 interface configured. -- The tester has access to the original data transported over the O2 interface. -- mTLS is properly implemented and configured as defined in [2] clause 4.2. - -##### Execution steps - -- 1) Executes the tests on the mTLS protocol as defined in clause 6.3 -- 2) Valid Authentication Certificates (positive case): - - The tester sends a request to establish a connection with the O2 interface using valid authentication certificates. - - The tester verifies the mutual certificate verification between the ORAN NFs. - - The tester captures and analyses the response from the O2 interface. -- 3) Invalid Authentication Certificates (negative case): - - The tester sends a request to establish a connection with the O2 interface with invalid certificates. - -- The tester captures and analyses the response from the O2 interface. -- 4) No Authentication Certificates (negative case): -- The tester sends a request to establish a connection without any certificates. - - The tester captures and analyses the response from the O2 interface. - -**Expected results** - -For 1) Expected results in clause 6.3 - -For 2) 'Valid Authentication Certificates': The O2 interface accepts the valid certificates and respond with a successful authentication message. - -For 3) 'Invalid Authentication Certificates': The connection is rejected, and an authentication failure message is received. The mutual certificate verification process fails due to the use of invalid certificates. - -For 4) 'No Authentication Certificates': The connection attempt is rejected, and an authentication failure message is received. The mutual certificate verification process fails due to the absence of certificates. - -**Expected Format of Evidence:** - -The following evidence, in one or more formats as applicable, should be provided: - -- Logs and screenshots showing adherence to mTLS protocol specifications as defined in [2] clause 4.2. -- Logs of authentication requests and responses on the O2 interface. -- Logs of the mutual certificate verification process. -- Screenshots or logs of error messages or unusual behaviours for both invalid and no certificate scenarios. - -## 11.4.2 O2 confidentiality, integrity and replay protection - -**Requirement Name:** O2 protection in terms of confidentiality, integrity and replay - -**Requirement Reference:** SEC-CTL-O-CLOUD-INTERFACE-1, clause 5.1.8.9.2, O-RAN Security Requirements and Controls Specifications [5] - -**Threat References:** T-O2-01 - -**DUT/s:** SMO, O-Cloud - -**Test Name:** TC\_O2\_CONFIDENTIALITY\_INTEGRITY\_REPLAY - -**Purpose:** To verify the enforcement of security policies over the O2 interface, ensuring that sensitive data remains protected through confidentiality, integrity, and replay protection. - -**Procedure and execution steps****Preconditions** - -- O-Cloud and SMO support TLS and be connected in simulated/real network environment. -- The O2 interface is configured for testing. -- TLS is properly implemented and configured as defined in [2] clause 4.2. - -**Execution steps** - -- 1) Confidentiality verification: - - Establish a secure communication session over the O2 interface. - -- Capture the network traffic during the session. - - Analyse the captured traffic to verify that all data is encrypted, ensuring confidentiality. -- 2) Integrity protection verification: -- Capture protected packets after the TLS handshake. - - Modify the captured packets. - - Inject the modified packets to the DUT. - - Confirm that the DUT discards the injected packets, e.g., does not deliver it to the higher layer. -- 3) Replay protection verification: -- Capture protected packets after the TLS handshake. - - Replay the captured packets to the DUT. - - Confirm that the DUT discards the replayed packets. - -#### Expected results - -- Confidentiality: All sensitive data transmitted over the O2 interface is encrypted, with no data exposed in clear text. -- Integrity protection: The DUT detects and discards altered packets, ensuring data has not been tampered with. -- Replay protection: The DUT detects and discards replayed packets, preventing replay attacks. - -#### Expected Format of Evidence: - -The following evidence, in one or more formats as applicable, should be provided: - -- Logs or screenshots showing TLS protocol adherence, as defined in the O-RAN Security Protocols Specifications [2] clause 4.2. -- Evidence of secure communication sessions established over the O2 interface, including details of encryption verification. -- Logs or screenshots showing the DUT's response to replayed and integrity-compromised packets, demonstrating the effectiveness of the security mechanisms in place. - -### 11.4.3 O2 Authorization - -**Requirement Name:** O2 protection in terms of authorization - -**Requirement Reference:** SEC-CTL-O-CLOUD-INTERFACE-2, clause 5.1.8.9.2, O-RAN Security Requirements and Controls Specifications [5] - -**Threat References:** T-O2-01 - -**DUT/s:** SMO, O-Cloud - -**Test Name:** TC\_O2\_AUTHORIZATION - -**Purpose:** The purpose of this test is to validate that the O2 interface enforces an authorization mechanism to prevent unauthorized access. - -#### Procedure and execution steps - -#### Preconditions - -- O-Cloud and SMO support OAuth 2.0 and are connected in simulated/real network environment. - -- The test environment is set up with O2 interface configured. -- The tester has access to the original data transported over the O2 interface. -- OAuth 2.0 is properly implemented and configured. - -#### Execution steps - -- 1) Execute the tests on the OAuth 2.0 protocol as defined in clause 6.6 -- 2) Valid access tokens (positive case): - - The tester sends a request to access protected resources using a valid access token. - - The tester captures and analyses the response from the O2 interface. -- 3) Invalid access tokens (negative case): - - The tester sends a request to access protected resources using an invalid or incorrect access token. - - The tester captures and analyses the response from the O2 interface. -- 4) No access tokens (negative case): - - The tester sends a request to access protected resources without providing any access token. - - The tester captures and analyses the response from the O2 interface. - -#### Expected results - -For 1). Expected results in clause 6.6 - -For 2) 'Valid access tokens': The O2 interface accepts the valid access tokens and responds with a successful authorization message. - -For 3) 'Invalid access tokens': The access is rejected, and an access failure message is received. - -For 4) 'No access tokens': The access is rejected due to the absence of tokens, and an appropriate error or unauthorized access message is received. - -#### Expected Format of Evidence: - -The following evidence, in one or more formats as applicable, should be provided: - -- Logs of the request sent to access protected resources using valid access tokens. -- Screenshots or logs highlighting the successful authorization message. -- Logs of the request sent to access protected resources using invalid or incorrect access tokens. -- Screenshots or logs showing the rejection of the access and the access failure message. - -## 11.5 E2 - -### 11.5.1 E2 confidentiality, integrity and replay protection - -**Requirement Name:** E2 protection in terms of confidentiality, integrity, and replay - -**Requirement Reference:** SEC-CTL-E2, clause 5.2.4.2, SEC-CTL-NEAR-RT-2, SEC-CTL-NEAR-RT-7, clause 5.1.3.2.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Confidentiality, integrity, and replay protection of E2 interface communications - -**Threat References:** T-O-RAN-05, T-NEAR-RT-01, T-NEAR-RT-02, T-NEAR-RT-03, T-NEAR-RT-04 - -**DUT/s:** O-CU, O-DU, Near-RT RIC - -**Test Name:** TC\_E2\_CONFIDENTIALITY\_INTEGRITY\_REPLAY - -**Purpose:** To verify the enforcement of security policies over the E2 interface, ensuring that sensitive data remains protected through confidentiality, integrity, and replay protection - -### Procedure and execution steps - -#### Preconditions - -- Near-RT RIC and E2 nodes support IPsec and are connected in simulated/real network environment. -- The E2 interface is configured for testing. -- The tunnel mode IPsec ESP and IKE certificate authentication is implemented. -- The tester shall base the test on the profile defined in [2] clause 4.5. - -#### Execution steps - -- 1) Confidentiality verification: - - Establish a secure communication session using IPsec over the E2 interface. - - Capture the network traffic during the session. - - Analyse the captured traffic to verify that all data is encrypted, ensuring confidentiality. -- 2) Integrity protection verification: - - Capture traffic during a secure session. - - Modify the captured packets. - - Inject the modified packets to the DUT. - - Confirm that the DUT discards the injected packets, e.g., does not deliver it to the higher layer. -- 3) Replay protection verification: - - Capture protected packets during a secure session and attempt to replay them. - - Replay the captured packets to the DUT. - - Confirm that the DUT discards the replayed packets. - -#### Expected Results - -- Confidentiality: All sensitive data transmitted over the E2 interface is encrypted, with no data exposed in clear text. -- Integrity protection: The DUT detects and discards altered packets, ensuring data has not been tampered with. -- Replay protection: The DUT detects and discards replayed packets, preventing replay attacks. - -#### Expected format of evidence: - -The following evidence, in one or more formats as applicable, should be provided: - -- Logs or screenshots showing TLS protocol adherence, as defined in the O-RAN Security Protocols Specifications [2] clause 4.5. -- Evidence of secure communication sessions established over the E2 interface, including details of encryption verification. - -- Logs or screenshots showing the DUT's response to replayed and integrity-compromised packets, demonstrating the effectiveness of the security mechanisms in place. - -## 11.5.2 E2 Authenticity - -### 11.5.2.1 E2 Authenticity with certificate - -**Requirement Name:** Data Authentication over E2 interface - -**Requirement Reference:** SEC-CTL-NEAR-RT-2, clause 5.1.3.2.1, SEC-CTL-E2-1, clause 5.2.4.2 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Mutual authentication of Near-RT RIC and E2 nodes over the E2 interface using valid certificates - -**Threat References:** T-O-RAN-05, T-NEAR-RT-01, T-NEAR-RT-02, T-NEAR-RT-03, T-NEAR-RT-04 - -**DUT/s:** O-CU, O-DU, Near-RT RIC - -**Test Name:** TC\_E2\_AUTHENTICATION\_CERT - -**Purpose:** The purpose of this test is to verify the authenticity of the E2 interface with valid certificates, ensuring that only legitimate and authenticated Near-RT RIC and E2 nodes can participate in the communication over the E2 interface. - -#### Procedure and execution steps - -##### Preconditions - -- Near-RT RIC and E2 nodes support IPsec and are connected in simulated/real network environment. -- Near-RT RIC and E2 nodes support IPsec and are configured to use certificate-based authentication. -- The test environment is set up with E2 interface configured. Communication sessions over the E2 interface are established. -- The vendor provides documentation describing how authenticity protection is achieved for the data transmission over the E2 interface. -- The tunnel mode IPsec ESP and IKE certificate authentication is implemented. -- Tester has knowledge of the security parameters of tunnel for decrypting the ESP packets. -- Tester has access to the original user data transported over the E2 interface. -- IPsec is properly implemented and configured. The tester bases the test on the profile defined in [2] clause 4.5. - -##### Execution steps - -- 1) Execute the tests on the IPsec protocol as defined in clause 6.5. -- 2) Valid Authentication Credentials: - - The tester sends a request to establish a connection with the E2 interface using valid certificates. - - The tester captures and analyses the response from the E2 interface. -- 3) Invalid Authentication Credentials: - - The tester sends a request to establish a connection with the E2 interface using invalid certificates. - - The tester captures and analyses the response from the E2 interface. -- 4) No Authentication Credentials: - -- The tester sends a request to establish a connection with the E2 interface without providing any certificates. -- The tester captures and analyses the response from the E2 interface. - -### Expected Results - -For 1) Expected results in clause 6.5.4 - -For 2) 'Valid Authentication Credentials': The E2 interface accepts the valid certificate and responds with a successful authentication message. - -For 3) 'Invalid Authentication Credentials': The connection is rejected due to the certificate verification failure, and an authentication failure message is received. - -For 4) 'No Authentication Credentials': The connection attempt fails due to the absence of certificates, and an authentication failure message is received. - -### Expected format of evidence: - -- Logs and screenshots showing adherence to IPsec protocol specifications as defined in [2] clause 4.5. -- Screenshots or logs of request-response messages confirming authentication with valid credentials. -- Screenshots or logs capturing the rejection of requests with invalid credentials. -- Screenshots or logs documenting attempts to connect without credentials and their rejection. - -## 11.5.2.2 E2 Authenticity with PSK - -**Requirement Name:** Data Authentication over E2 interface - -**Requirement Reference:** SEC-CTL-NEAR-RT-2, clause 5.1.3.2.1, SEC-CTL-E2-1, clause 5.2.4.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Mutual authentication of Near-RT RIC and E2 nodes over the E2 interface using valid pre-shared keys - -**Threat References:** T-O-RAN-05, T-NEAR-RT-01, T-NEAR-RT-02, T-NEAR-RT-03, T-NEAR-RT-04 - -**DUT/s:** O-CU, O-DU, Near-RT RIC - -**Test Name:** TC\_E2\_AUTHENTICATION\_PSK - -**Purpose:** The purpose of this test is to verify the authenticity of the E2 interface with valid PSK, ensuring that only legitimate and authenticated Near-RT RIC and E2 nodes can participate in the communication over the E2 interface. - -### Procedure and execution steps - -#### Preconditions - -- Near-RT RIC and E2 nodes support IPsec and are connected in simulated/real network environment. -- Near-RT RIC and E2 nodes support IPsec and are configured to use PSK-based authentication. -- The test environment is set up with E2 interface configured. Communication sessions over the E2 interface are established. -- The vendor provides documentation describing how authenticity protection is achieved for the data transmission over the E2 interface. -- The tunnel mode IPsec ESP and IKE certificate authentication is implemented. -- Tester has knowledge of the security parameters of tunnel for decrypting the ESP packets. -- Tester has access to the original user data transported over the E2 interface. - -- IPsec is properly implemented and configured. The bases the test on the profile defined in [2] clause 4.5. - -### Execution steps - -- 1) Execute the tests on the IPsec protocol as defined in clause 6.5. -- 2) Valid Authentication Credentials: - - The tester sends a request to establish a connection with the E2 interface using valid PSKs. - - The tester captures and analyses the response from the E2 interface. -- 3) Invalid Authentication Credentials (Incorrect PSKs): - - The tester sends a request to establish a connection with the E2 interface with incorrect PSKs. - - The tester captures and analyses the response from the E2 interface. -- 4) No Authentication Credentials (No PSKs): - - The tester sends a request to establish a connection with the E2 interface without providing any PSKs. - - The tester captures and analyses the response from the E2 interface. - -### Expected Results - -For 1) Expected results in clause 6.5.4 - -For 2) 'Valid Authentication Credentials': The E2 interface accepts the valid PSK and responds with a successful authentication message. - -For 3) 'Invalid Authentication Credentials (Incorrect PSKs)': The connection is rejected due to PSK verification failure, and an authentication failure message is received. - -For 4) 'No Authentication Credentials (No PSKs)': The connection attempt fails due to the absence of PSKs, and an authentication failure message is received. - -### Expected format of evidence: - -- Logs and screenshots showing adherence to IPsec protocol specifications as defined in [2] clause 4.5. -- Logs or screenshots documenting request and response messages for successful authentication using valid credentials. -- Logs or screenshots capturing the request and response messages when invalid credentials are rejected. -- Logs or screenshots documenting the request and response messages for rejections of connections without PSKs. - -## 11.5.2.3 E2 Interface data validation by Near-RT RIC - -**Requirement Name:** Validation of the data received via E2 interface by Near-RT RIC - -**Requirement Reference:** SEC-CTL-NEAR-RT-17, clause 5.1.3.2.5, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The Near-RT RIC shall verify data received through the E2 interface as follows: - -The data values are valid. - -The data is being received at or below a pre-defined rate. - -The Near-RT RIC shall log security event(s) if any of the verification steps fail. - -**Threat References:** T-NEAR-RT-01, T-xApp-01 - -**DUT/s:** Near-RT RIC - -**Test Name:** TC\_E2\_Interface\_data\_validation\_by\_NearRTRIC - -**Purpose:** To validate the E2 traffic that is received by Near-RT RIC via E2 interface. The Near-RT RIC uses E2 interface to collect near real-time information (EXAMPLE:- UE basis, Cell basis) and provide value added services. These real-time information needs to be validated when it gets received at Near-RT RIC and security events are to be logged if data validation fails. E2 interface connects the Near-Real-Time RIC with other E2 nodes like O-CU, O-DU, and O-eNB. - -### Procedure and execution steps - -EXAMPLE 1: One of the incoming data values to the Near-RT RIC are the measurement reports (carried in E2 Indication messages) that include: - -- Channel quality reports: Signal strength, signal-to-noise ratio (SNR), and modulation quality. -- Interference reports: Identifying sources of interference. -- Load reports: Current load on E2 nodes - -### Preconditions - -Client is the test system which simulates E2 data traffic towards Near-RT RIC. This includes all the supported E2 support services (EXAMPLE: E2 RESET procedure), Measurement reports and other supported services. Test system is also capable of simulating multiple E2 connections where E2 traffic can be pushed. - -- Near-RT RIC is fully operational and data value validation in Near-RT RIC is defined, and the pre-defined data threshold rate is set. By fully operational Near-RT RIC, this means the Near-RT RIC is enabled with necessary xApps and configurations at the platform level. -- Client system is logged in and the initial control connections are up with Near-RT RIC. At this point the Near-RT RIC has subscribed with E2 Nodes in the Client system and is expecting data at a predefined rate. -- Login to the DUT with authorized credentials and start data collection required for checking the data handling. - -### Execution steps - -- 1) From the client system, Initiate the E2 traffic with valid data values towards Near-RT RIC over single E2 connection -- 2) From the client test system, Initiate the E2 traffic with valid data on multiple E2 connections simultaneously -- 3) From the client test system, initiate invalid E2 traffic data - -EXAMPLE 2: Invalid values (or) Invalid format in the measurement reports (or) Invalid E2 Node configuration information sent in E2 setup request (or) Invalid cause in the E2 reset request - -- 4) From the client test system, initiate the E2 data which is equal to the Near-RT RIC predefined data rate via multiple E2 connections simultaneously -- 5) From the client test system, initiate sudden burst of E2 data which is more than the Near-RT RIC predefined data rate via multiple E2 connections simultaneously - -### Expected results - -After step 1, the DUT processes the data traffic received over a single E2 connection. - -After step 2, the DUT processes the data traffic received simultaneously over multiple E2 connections. - -After step 3, the DUT discards the data and security event is logged with the logs fields as per clause 5.3.8.8 of [5]. - -After step 4, the DUT receives E2 traffic and handles it because E2 data is at, or below the pre-defined rate in DUT. - -After step 5, the DUT discards the spilled over data and security events are logged with the log fields are as per clause 5.3.8.8 of [5] because the E2 data rate is higher than the pre-defined rate in DUT. - -**Expected format of evidence:** Log files, traffic captures and/or report files. - -## 11.6 A1 - -### 11.6.1 A1 Authenticity - -**Requirement Name:** A1 protection in terms of authenticity - -**Requirement Reference:** SEC-CTL-A1-2, clause 5.2.1.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Mutual authentication of Non-RT RIC and Near-RT RIC to ensure A1 interface authenticity - -**Threat References:** T-A1-01 - -**DUT/s:** Non-RT RIC, Near-RT RIC - -**Test Name:** TC\_A1\_Authentication - -**Purpose:** The purpose of this test is to verify the authenticity of the A1 interface, ensuring that only legitimate and authenticated Non-RT RIC, Near-RT RIC can participate in the communication over the A1 interface. - -#### Procedure and execution steps - -##### Preconditions - -- Non-RT RIC & Near-RT RIC support mTLS and be connected in a simulated/real network environment. -- The test environment is set up with the A1 interface configured. -- The tester has access to the original data transported over the A1 interface. -- mTLS is properly implemented and configured as defined in [2] clause 4.2. - -##### Execution steps - -- 1) Execute the test on the mTLS protocol as defined in clause 6.3. -- 2) Valid Authentication Certificates (positive case): - - The tester sends a request to establish a connection with the A1 interface using valid authentication certificates. - - The tester verifies the mutual certificate verification between Non-RT RIC and Near-RT RIC. - - The tester captures and analyses the response received from the A1 interface. -- 3) Invalid Authentication Certificates (negative case): - - The tester sends a request to establish a connection with the A1 interface with invalid certificates. - - The tester captures and analyses the response received from the A1 interface. -- 4) No Authentication Certificates (negative Case): - - The tester sends a request to establish a connection without any certificates. - - The tester captures and analyses the response from the A1 interface. - -#### Expected results - -For 1) Expected results in clause 6.3 - -For 2) 'Valid Authentication Certificates': The A1 interface accepts the valid certificates and responds with a successful authentication message. The mutual certificate verification process is successful. - -For 3) 'Invalid Authentication Certificates': The connection attempt is rejected, and an authentication failure message is received. The mutual certificate verification process fails due to the use of invalid certificates. - -For 4) 'No Authentication Certificates': The connection attempt is rejected, and an authentication failure message is received. The mutual certificate verification process fails due to the absence of certificates. - -#### Expected Format of Evidence: - -The following evidence, in one or more formats as applicable, should be provided: - -- Logs and screenshots showing adherence to mTLS protocol specifications as defined in [2] clause 4.2. -- Logs of authentication requests and responses on the A1 interface. -- Logs of the mutual certificate verification process. -- Screenshots or logs of error messages or unusual behaviours for both invalid and no certificate scenarios. - -## 11.6.2 A1 confidentiality, integrity and replay protection - -**Requirement Name:** A1 protection in terms of confidentiality, integrity, and replay - -**Requirement Reference:** SEC-CTL-A1, clause 5.2.1.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Confidentiality, integrity, and replay protection of A1 interface communications - -**Threat References:** T-A1-02, T-A1-03 - -**DUT/s:** Non-RT RIC, Near-RT RIC - -**Test Name:** TC\_A1\_CONFIDENTIALITY\_INTEGRITY\_REPLAY - -**Purpose:** To verify the enforcement of security policies over the A1 interface, ensuring that sensitive data remains protected through confidentiality, integrity, and replay protection. - -#### Procedure and execution steps - -##### Preconditions - -- Non-RT RIC & Near-RT RIC support TLS and connected within simulated or real network environments. -- The A1 interface is configured for testing. -- TLS is properly implemented and configured as defined in [2] clause 4.2. - -##### Execution steps - -- 1) Confidentiality verification: - - Establish a secure communication session over the A1 interface. - - Capture the network traffic during the session. - - Analyse the captured traffic to verify that all data is encrypted, ensuring confidentiality. -- 2) Integrity protection verification: - - Capture protected packets after the TLS handshake. - - Modify the captured packets. - - Inject the modified packets to the DUT. - -- Confirm that the DUT discards the injected packets, e.g., does not deliver it to the higher layer. -- 3) Replay protection verification: -- Capture protected packets after the TLS handshake. - - Replay the captured packets to the DUT. - - Confirm that the DUT discards the replayed packets. - -#### Expected results - -- Confidentiality: All sensitive data transmitted over the A1 interface is encrypted, with no data exposed in clear text. -- Integrity protection: The DUT detects and discards altered packets, ensuring data has not been tampered with. -- Replay protection: The DUT detects and discards replayed packets, preventing replay attacks. - -#### Expected Format of Evidence: - -The following evidence, in one or more formats as applicable, should be provided: - -- Logs or screenshots showing TLS protocol adherence, as defined in the O-RAN Security Protocols Specifications [2] clause 4.2. -- Evidence of secure communication sessions established over the A1 interface, including details of encryption verification. -- Logs or screenshots showing the DUT's response to replayed and integrity-compromised packets, demonstrating the effectiveness of the security mechanisms in place. - -### 11.6.3 A1 Authorization - -**Requirement Name:** A1 protection in terms of authorization - -**Requirement Reference:** SEC-CTL-A1-3, clause 5.2.1.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Authorization control on the A1 interface preventing unauthorized access - -**Threat References:** T-A1-01 - -**DUT/s:** Non-RT RIC, Near-RT RIC - -**Test Name:** TC\_A1\_Authorization - -**Purpose:** The purpose of this test is to validate that the A1 interface enforces an authorization mechanism to prevent unauthorized access. - -#### Procedure and execution steps - -##### Preconditions - -- Non-RT RIC and Near-RT RIC support OAuth 2.0 and are connected in simulated/real network environment. -- The test environment is set up with A1 interface configured. -- The tester has access to the original data transported over the A1 interface. -- OAuth 2.0 is properly implemented and configured. - -##### Execution steps - -- 1) Execute the test on the OAuth 2.0 protocol as defined in clause 6.6. - -- 2) Valid access tokens (positive case): - - The tester sends a request to access protected resources using a valid access token. - - The tester captures and analyses the response from the A1 interface. -- 3) Invalid access tokens (negative case): - - The tester sends a request to access protected resources using an invalid or incorrect access token. - - The tester captures and analyses the response from the A1 interface. -- 4) No access tokens (negative case): - - The tester sends a request to access protected resources without providing any access token. - - The tester captures and analyses the response from the A1 interface. - -## Expected Results - -For 1) Expected results in clause 6.6 - -For 2) 'Valid access tokens': The A1 interface accepts the valid access tokens and responds with a successful authorization message. - -For 3) 'Invalid access tokens': The access is rejected, and an access failure message is received. - -For 4) 'No access tokens': The access is rejected due to the absence of tokens, and an appropriate error or unauthorized access message is received. - -## Expected Format of Evidence: - -The following evidence, in one or more formats as applicable, should be provided: - -- Logs of the request sent to access protected resources using valid access tokens. -- Screenshots or logs highlighting the successful authorization message. -- Logs of the request sent to access protected resources using invalid or incorrect access tokens. -- Screenshots or logs showing the rejection of the access and the access failure message. - -# 11.7 R1 - -## 11.7.1 R1 Authenticity - -**Requirement Name:** R1 protection in terms of authenticity - -**Requirement Reference:** SEC-CTL-R1-2, clause 5.2.6.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Authenticity of the R1 interface ensuring communication only between authenticated Non-RT RIC and rApps - -**Threat References:** T-R1-03 - -**DUT/s:** Non-RT RIC, rApps - -**Test Name:** TC\_R1\_AUTHENTICATION - -**Purpose:** The purpose of this test is to verify the authenticity of the R1 interface, ensuring that only legitimate and authenticated Non-RT RIC, rApps can participate in the communication over the R1 interface. - -## Procedure and execution steps - -### Preconditions - -- Non-RT RIC & rApps support mTLS and be connected in a simulated/real network environment. -- The test environment is set up with the R1 interface configured. -- The tester has access to the original data transported over the R1 interface. -- mTLS is properly implemented and configured as defined in [2] clause 4.2. - -### Execution steps - -- 1) Execute the test on the mTLS protocol as defined in clause 6.3. -- 2) Valid Authentication Certificates (positive case): - - The tester sends a request to establish a connection with the R1 interface using valid authentication certificates. - - The tester verifies the mutual certificate verification between Non-RT RIC and rApps. - - The tester captures and analyses the response received from the R1 interface. -- 3) Invalid Authentication Certificates (negative case): - - The tester sends a request to establish a connection with the R1 interface with invalid certificates. - - The tester captures and analyses the response received from the R1 interface. -- 4) No Authentication Certificates (negative Case): - - The tester sends a request to establish a connection without any certificates. - - The tester captures and analyses the response from the R1 interface. - -### Expected results - -For 1) Expected results in clause 6.3 - -For 2) 'Valid Authentication Certificates': The R1 interface accepts the valid certificates and responds with a successful authentication message. The mutual certificate verification process is successful. - -For 3) 'Invalid Authentication Certificates': The connection attempt is rejected, and an authentication failure message is received. The mutual certificate verification process fails due to the use of invalid certificates. - -For 4) 'No Authentication Certificates': The connection attempt is rejected, and an authentication failure message is received. The mutual certificate verification process fails due to the absence of certificates. - -### Expected Format of Evidence: - -The following evidence, in one or more formats as applicable, should be provided: - -- Logs and screenshots showing adherence to mTLS protocol specifications as defined in [2] clause 4.2. -- Logs of authentication requests and responses on the R1 interface. -- Logs of the mutual certificate verification process. -- Screenshots or logs of error messages or unusual behaviours for both invalid and no certificate scenarios. - -## 11.7.2 R1 confidentiality, integrity and replay protection - -**Requirement Name:** R1 protection in terms of confidentiality, integrity and replay - -**Requirement Reference:** SEC-CTL-R1-1, clause 5.2.6.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Confidentiality, integrity, and replay protection of R1 interface communications - -**Threat References:** T-R1-06, T-R1-07 - -**DUT/s:** Non-RT RIC, rApps - -**Test Name:** TC\_R1\_CONFIDENTIALITY\_INTEGRITY\_REPLAY - -**Purpose:** To verify the enforcement of security policies over the R1 interface, ensuring that sensitive data remains protected through confidentiality, integrity and replay protection. - -#### **Procedure and execution steps** - -##### **Preconditions** - -- Non-RT RIC & rApps supporting TLS, connected within simulated or real network environments. -- The R1 interface is configured for testing. -- TLS is properly implemented and configured as defined in [2] clause 4.2. - -##### **Execution steps** - -- 1) Confidentiality verification: - - Establish a secure communication session over the R1 interface. - - Capture the network traffic during the session. - - Analyse the captured traffic to verify that all data is encrypted, ensuring confidentiality. -- 2) Integrity protection verification: - - Capture protected packets after the TLS handshake. - - Modify the captured packets. - - Inject the modified packets to the DUT. - - Confirm that the DUT discards the injected packets, e.g., does not deliver it to the higher layer. -- 3) Replay protection verification: - - Capture protected packets after the TLS handshake. - - Replay the captured packets to the DUT. - - Confirm that the DUT discards the replayed packets. - -##### **Expected results** - -- Confidentiality: All sensitive data transmitted over the R1 interface is encrypted, with no data exposed in clear text. -- Integrity protection: The DUT detects and discards altered packets, ensuring data has not been tampered with. -- Replay protection: The DUT detects and discards replayed packets, preventing replay attacks. - -##### **Expected Format of Evidence:** - -The following evidence, in one or more formats as applicable, should be provided: - -- Logs or screenshots showing TLS protocol adherence, as defined in the O-RAN Security Protocols Specifications [2] clause 4.2. - -- Evidence of secure communication sessions established over the R1 interface, including details of encryption verification. -- Logs or screenshots showing the DUT's response to replayed and integrity-compromised packets, demonstrating the effectiveness of the security mechanisms in place. - -### 11.7.3 R1 Authorization - -**Requirement Name:** R1 protection in terms of authorization - -**Requirement Reference:** SEC-CTL-R1-3, clause 5.2.6.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Authorization enforcement on the R1 interface to prevent unauthorized access - -**Threat References:** T-R1-01, T-R1-04, T-R1-05 - -**DUT/s:** Non-RT RIC, rApps - -**Test Name:** TC\_R1\_AUTHORIZATION - -**Purpose:** The purpose of this test is to validate that the R1 interface enforces an authorization mechanism to prevent unauthorized access. - -#### Procedure and execution steps - -##### Preconditions - -- Non-RT RIC and rApps support OAuth 2.0 and are connected in simulated/real network environment. -- The test environment is set up with R1 interface configured. -- The tester has access to the original data transported over the R1 interface. -- OAuth 2.0 is properly implemented and configured. - -##### Execution steps - -- 1) Execute the test on the OAuth 2.0 protocol as defined in clause 6.6. -- 2) Valid access tokens (positive case): - - The tester sends a request to access protected resources using a valid access token. - - The tester captures and analyses the response from the R1 interface. -- 3) Invalid access tokens (negative case): - - The tester sends a request to access protected resources using an invalid or incorrect access token. - - The tester captures and analyses the response from the R1 interface. -- 4) No access tokens (negative case): - - The tester sends a request to access protected resources without providing any access token. - - The tester captures and analyses the response from the R1 interface. - -##### Expected Results - -For 1) Expected results in clause 6.6 - -For 2) 'Valid access tokens': The R1 interface accepts the valid access tokens and responds with a successful authorization message. - -For 3) 'Invalid access tokens': The access is rejected, and an access failure message is received. - -For 4) 'No access tokens': The access is rejected due to the absence of tokens, and an appropriate error or unauthorized access message is received. - -#### Expected Format of Evidence: - -The following evidence, in one or more formats as applicable, should be provided: - -- Logs of the request sent to access protected resources using valid access tokens. -- Screenshots or logs highlighting the successful authorization message. -- Logs of the request sent to access protected resources using invalid or incorrect access tokens. -- Screenshots or logs showing the rejection of the access and the access failure message. - ---- - -## 12 Security test of O-RU - -### 12.1 Overview - -This clause contains security tests to validate the security protection mechanism specific to O-RU. - -### 12.2 SSH on M-Plane interface - -**Requirement Name:** Network Security Protocol - SSH - -**Requirement Reference:** REQ-SEC-OFHM-1, REQ-SEC-OFHM-2, REQ-SEC-OFHM-3, clause 5.2.5.4.1, SEC-CTL-OFHM-6, SEC-CTL-OFHM-7, SEC-CTL-OFHM-8, clause 5.2.5.4.2 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Robust protocol implementation with adequately strong cipher suites is being required for SSH - -**Threat References:** T-O-RAN-05 - -**DUT/s:** O-RU - -**Test Name:** TC\_SSH\_MPlane - -**Purpose:** To verify implementation of the SSH protocol in O-RU along with validation of supported SSH version and robustness of cryptographic algorithms used for host key, symmetric encryption, key exchange, and MACs as specified in O-RAN WG4 Management Plane Specification [21], clause 5.4.2. - -#### Procedure and execution steps - -##### Preconditions - -DUT is the O-RU with SSH service enabled as server. Client is a test equipment with SSH audit tool which is used for server-side testing. - -##### Execution steps - -Follow the test case in clause 6.2 of the present document. - -##### Expected results - -The DUT supports only SSHv2 version with no older version supported and algorithms (for host key, symmetric encryption, key exchange, and MACs) defined in O-RAN WG4 Management Plane Specification [21], clause 5.4.2. - -**Expected format of evidence:** As defined in clause 6.2 of the present document. - -## 12.3 TLS on M-Plane interface - -**Requirement Name:** Network Security Protocol - TLS - -**Requirement Reference:** REQ-SEC-OFHM-1, REQ-SEC-OFHM-2, clause 5.2.5.4.1, SEC-CTL-OFHM-1, SEC-CTL-OFHM-2, SEC-CTL-OFHM-3, clause 5.2.5.4.2 in O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Support TLS 1.2 and TLS 1.3 with protocol profiles - -**Threat References:** T-O-RAN-05 - -**DUT/s:** O-RU - -**Test Name:** TC\_TLS\_MPlane - -**Purpose:** To verify implementation of the TLS protocol in O-RU along with validation of mandated/optional TLS versions and cipher suites specified in clause 5.2.5.3 of [5]. Since NETCONF implementations support X.509v3 certificate-based authentication using TLS 1.2, and TLS 1.3 mutual authentication is also be tested using both valid and invalid client certificates. - -### Procedure and execution steps - -#### Preconditions - -DUT is the O-RU with TLS service enabled as server equipped with Trust Anchor certificate(s) for authentication of client certificate(s). Client is a testing equipment with TLS scanning tool with client certificate(s). - -#### Execution steps - -Follow the test case in clause 6.3 of the present document. - -#### Expected results - -The DUT supports TLS version 1.2 and version 1.3 with no older version. Protocol profiles/Cipher suites defined in O-RAN Security Protocols Specification [2], clause 4.1.2 are supported. - -**Expected format of evidence:** As defined in clause 6.3 of the present document. - -## 12.4 Security functional requirements and test cases - -The 802.1X Supplicant Validation test cases in clause 11.2.2 of the present document apply to O-RU. - ---- - -## 13 Security test of Near-RT RIC - -### 13.1 Overview - -This clause contains security tests to validate the security protection mechanism specific to Near-RT RIC. - -### 13.2 Void - -### 13.3 Transactional APIs - -#### 13.3.1 Introduction - -Transactional APIs in the Near-RT RIC are APIs that are based on HTTP/TLS, i.e. APIs based on REST or gRPC. - -### 13.3.2 TLS for transactional APIs - -**Requirement Name:** TLS for transactional APIs - -**Requirement Reference:** SEC-CTL-NEAR-RT-6, clause 5.1.3.2.3, O-RAN Security Requirements and Controls Specifications [5]. - -**Requirement Description:** Transactional APIs (REST and gRPC) support TLS to provide message confidentiality and integrity. - -**Threat References:** T-NEAR-RT-01, T-NEAR-RT-02, T-NEAR-RT-03, T-NEAR-RT-04 - -**DUT/s:** xApp, Near-RT RIC - -**Test Name:** TC\_TLS\_APIs - -**Purpose:** To verify the transactional APIs (REST and gRPC) support TLS to provide message confidentiality and integrity. - -#### Procedure and execution steps - -##### Preconditions - -DUT is configured and with TLS support enabled. - -The other end may be simulated or a testing equipment. - -##### Execution steps - -Follow the test case in clause 6.3 of the present document. - -##### Expected results - -The transaction APIs provides confidentiality and integrity protection for data in transit. - -**Expected format of evidence:** Tool reports, log files, traffic captures and/or screenshots. - -### 13.3.3 mTLS for transactional APIs - -**Requirement Name:** mTLS for transactional APIs - -**Requirement Reference:** SEC-CTL-NEAR-RT-1, clause 5.1.3.2.1, O-RAN Security Requirements and Controls Specifications [5]. - -**Requirement Description:** The communication between xApps and Near-RT RIC platform APIs is mutually authenticated. - -**Threat References:** T-NEAR-RT-01, T-NEAR-RT-02, T-NEAR-RT-03, T-NEAR-RT-04 - -**DUT/s:** xApp, Near-RT RIC - -**Test Name:** TC\_mTLS\_APIs - -**Purpose:** To verify the transactional APIs (REST and gRPC) support mutual TLS (mTLS) authentication via X.509v3 certificates. - -#### Procedure and execution steps - -##### Preconditions - -Applicability: DUTs that support mTLS as a mutual authentication mechanism. - -DUT is configured and with mTLS support enabled. The other end may be simulated or a testing equipment. - -##### Execution steps - -Follow the test case in clause 6.3 of the present document. - -#### Expected results - -The transactional APIs support mutual TLS (mTLS) authentication. - -**Expected format of evidence:** Tool reports, log files, traffic captures and/or screenshots. - -### 13.3.4 OAuth 2.0 for transactional APIs - -**Requirement Name:** OAuth 2.0 for transactional APIs - -**Requirement Reference:** SEC-CTL-NEAR-RT-3, clause 5.1.3.2.2, O-RAN Security Requirements and Controls Specifications [5]. - -**Requirement Description:** Near-RT RIC architecture provides an authorization framework. - -**Threat References:** T-NEAR-RT-01, T-NEAR-RT-02, T-NEAR-RT-03, T-NEAR-RT-04 - -**DUT/s:** xApp, Near-RT RIC - -**Test Name:** TC\_OAuth2.0\_API - -**Purpose:** To verify the transactional APIs (REST and gRPC) in the DUT support the OAuth 2.0 authorization framework. - -#### Procedure and execution steps - -##### Preconditions - -DUT is configured and with OAuth 2.0 support enabled. - -The other end may be simulated or a testing equipment. - -##### Execution steps - -Follow the test case in clause 6.6.2 of the present document. - -#### Expected results - -The transactional APIs support the use of OAuth 2.0. - -**Expected format of evidence:** Tool reports, log files, traffic captures and/or screenshots. - -## 13.4 Security test of Near-RT RIC OAuth 2.0 Resource Owner/Server - -### 13.4.1 Overview - -This clause contains security tests to verify OAuth2.0 implementation on Near-RT RIC as resource owner/server for A1-P. - -### 13.4.2 Near-RT RIC OAuth 2.0 Resource Owner/Server - -**Requirement Name:** Near-RT RIC support as OAuth2.0 resource owner/server - -**Requirement Reference:** SEC-CTL-NEAR-RT-4, clause 5.1.3.2.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** OAuth 2.0 security controls for Near-RT RIC authorization of service requests - -**Threat References:** T-NEAR-RT-01, T-NEAR-RT-02, T-NEAR-RT-03, T-NEAR-RT-04 - -**DUT/s:** Near-RT RIC - -**Test Name:** TC\_NearRTRIC\_OAuth2.0\_Server - -**Purpose:** To validate the Near-RT RIC support as OAuth 2.0 resource owner/server for A1-P, as specified in clause 4.7, O-RAN Security Protocols Specifications [2] for service requests received from a Near-RT RIC. - -#### **Procedure and execution steps** - -##### **Preconditions** - -DUT is acting as a resource owner/server with OAuth 2.0 support enabled. OAuth2.0 Client is the test system equipped to send the service requests over a secured TLS communication with mutual TLS authentication. - -##### **Execution steps** - -Follow the test case in clause 6.6.2 of the present document. - -##### **Expected results** - -The DUT is able to authorize/deny access to resources using OAuth 2.0. - -**Expected format of evidence:** Log files, traffic captures and/or report files. - -## **13.5 Security test of Near-RT RIC OAuth 2.0 client** - -### **13.5.1 Overview** - -This clause contains security tests to verify the implementation on Near-RT RIC as OAuth2.0 client for A1-EI. - -### **13.5.2 Near-RT RIC OAuth 2.0 client** - -**Requirement Name:** Near-RT RIC support as OAuth2.0 client for A1-EI - -**Requirement Reference:** SEC-CTL-NEAR-RT-5, clause 5.1.3.2.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** OAuth 2.0 security controls for Near-RT RIC authorization of service requests - -**Threat References:** T-NEAR-RT-01, T-NEAR-RT-02, T-NEAR-RT-03, T-NEAR-RT-04 - -**DUT/s:** Near-RT RIC - -**Test Name:** TC\_NearRTRIC\_OAuth2.0\_Client - -**Purpose:** To validate the Near-RT RIC support as OAuth 2.0 client for A1-EI, as specified in clause 4.7, O-RAN Security Protocols Specifications [2] - -#### **Procedure and execution steps** - -##### **Preconditions** - -DUT is acting as a resource client with OAuth 2.0 support enabled. - -##### **Execution steps** - -Follow the test case in clause 6.6.1 of the present document. - -##### **Expected results** - -The DUT is able to request and be permitted access to resources using OAuth2.0 - -**Expected format of evidence:** Log files, traffic captures and/or report files. - -## 14 Security test of xApps - -### 14.1 Overview - -This clause contains security tests to validate the security protection mechanism specific to xApps deployed on Near-RT RIC. - -### 14.2 xApp Signing and Verification - -The security test cases defined in clause 9.5.2 apply to this clause. - -### 14.3 xAppID - -#### 14.3.1 xApp ID format check - -**Requirement Name:** xApp ID uniqueness check for the xApp instance - -**Requirement Reference:** SEC-CTL-NEAR-RT-13, clause 5.1.3.2.5, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** To validate the format of xApp ID string and the uniqueness of the same which will be a Universally Unique Identifier (UUID) version 4 (as described in IETF RFC 9562 [30]). - -**Threat References:** T-NEAR-RT-05 - -**DUT/s:** Near-RT RIC - -**Test Name:** TC\_xApp\_ID\_validation - -**Purpose:** To validate the xApp ID format that uniquely identifies the xApp instance. In this test, we are initiating registration requests from 3 xApp instances and validating the response from Near-RT RIC. The xApp ID format is checked against Universally Unique Identifier (UUID) version 4 (as described in IETF RFC 9562 [30]). - -#### Procedure and execution steps - -##### Preconditions - -xApp instances are pre-provisioned with initial registration credential (OAuth 2.0 token), and the xApp instance CSR message. - -NOTE 1: xApp instances can be instantiated of the same or different xApp images - -##### Execution steps - -- 1) Initiate the first xApp instance registration procedure with DUT and get for the registration response. -- 2) Initiate the second xApp instance registration procedure with DUT and get for the registration response. -- 3) Initiate the third xApp instance registration procedure with DUT and get for the registration response. - -##### Expected results - -After each execution step, the Registration response from DUT includes the xApp certificate for the xApp instance. The field "Subject Alternative Name" in the xApp instance certificate contains URI for the xApp ID as an URN. This URI contains the xApp ID of the different xApp instances. - -The xApp ID generated in SAN field of xApp instance certificate after each execution step is unique and randomly different from the others (i.e., the UUIDs do not reflect a counter-based increment). - -The assigned xApp ID format is compliant with Universally Unique Identifier (UUID) version 4 (as described in IETF RFC 9562 [30]. Section 6.9 "Unguessability" in IETF RFC 9562 states "Implementations SHOULD utilize a cryptographically secure pseudorandom number generator (CSPRNG) to provide values that are both difficult to predict ("unguessable") and have a low likelihood of collision ("unique")."). - -NOTE 2: the certificate details could be seen with the openssl tool - -**Expected format of evidence:** Log files, traffic captures, report files, certificates and/or screenshots. - -### 14.3.2 xApp ID in xApp instance Certificate - -**Requirement Name:** xApp ID presence in "Subject Alternative Name" field of the xApp instance certificate. - -**Requirement Reference:** SEC-CTL-NEAR-RT-14, clause 5.1.3.2.5, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** "Subject Alternative Name" in the xApp instance certificate contains URI for the xApp ID as an URN. This URI contains the xApp ID of the xApp instance using the UUID format as described in IETF RFC 9562 [30]. - -**Threat References:** T-xApp-02, T-NEAR-TR-05 - -**DUT/s:** Near-RT RIC - -**Test Name:** TC\_xApp\_ID\_check\_in\_xApp\_instance\_certificate - -**Purpose:** To check the xApp ID embedded in subject Alternate Name field of xApp instance certificate. - -#### Procedure and execution steps - -##### Preconditions - -xApp image is available for instantiation. - -xApp Registration procedure is successfully done and xApp instance certificate has been assigned to xApp as part of the Registration response. - -##### Execution steps - -- 1) Establish a TLS session to the xApp instance with authorized credentials. - -EXAMPLE 1: TLS session may be established using one of the services that xApp instance provides - -- 2) Capture the xApp instance certificate (X.509v3) on the xApp instance and open the certificate to check the details. - -EXAMPLE 2: `Openssl x509 -in -text -noout` - -- 3) Check the "Subject Alternative Name" field in the certificate details. - -##### Expected results - -The "Subject Alternative Name" contained in the certificate of the xApp instance, contains URI for the xApp ID as an URN. xApp ID of the xApp instance is conformant to UUID format as described in IETF RFC 9562 [30]. - -**Expected format of evidence:** Log files, traffic captures, screenshots, certificates and/or report files. - -# 15 Security test of Non-RT RIC - -## 15.1 Overview - -This clause contains security tests to validate the security protection mechanism specific to Non-RT RIC and the R1 and A1 interfaces. Security test cases for rApps are covered in a separate sub-clause. - -## 15.2 Non-RT RIC - -### 15.2.1 Non-RT RIC OAuth 2.0 Resource Owner/Server - -**Requirement Name:** Server authorization support - -**Requirement Reference:** SEC-CTL-NonRTRIC-1, clause 5.1.2.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Non-RT RIC supports OAuth 2.0 as a Server - -**Threat References:** T-NONRTRIC-01, T-NONRTRIC-02, T-NONRTRIC-03 - -**DUT/s:** Non-RT RIC - -**Test Name:** TC\_NonRTRIC\_OAuth2.0\_Server - -**Purpose:** To verify the Non-RT RIC supports OAuth 2.0 resource owner/server for A1-EI. - -#### Procedure and execution steps - -##### Preconditions - -The DUT is acting as a Resource Owner/Server and has OAuth 2.0 support enabled. - -The rest of the elements of the setup may be real or simulated. - -##### Execution steps - -Follow the test case in clause 6.6.2 of the present document. - -##### Expected results - -The DUT is able to authorize/deny access to resources using OAuth 2.0. - -**Expected format of evidence:** Log files, traffic captures and/or report files. - -### 15.2.2 Non-RT RIC OAuth 2.0 Client - -**Requirement Name:** Client authorization support - -**Requirement Reference:** SEC-CTL-NonRTRIC-2, clause 5.1.2.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Non-RT RIC supports OAuth 2.0 as a Client - -**Threat References:** T-NONRTRIC-01, T-NONRTRIC-02, T-NONRTRIC-03 - -**DUT/s:** Non-RT RIC - -**Test Name:** TC\_NonRTRIC\_OAuth2.0\_Client - -**Purpose:** To verify the Non-RT RIC supports OAuth 2.0 client for A1-P. - -**Procedure and execution steps****Preconditions** - -The DUT is acting as a Client and has OAuth 2.0 support enabled. - -The rest of the elements of the setup may be real or simulated. - -**Execution steps** - -Follow the test case in clause 6.6.1 of the present document. - -**Expected results** - -The DUT is able to request and be permitted access to resources using OAuth 2.0. - -**Expected format of evidence:** Log files, traffic captures and/or report files. - -## 15.2.3 Non-RT RIC Framework OAuth 2.0 - -**Requirement Name:** Framework Server authorization support - -**Requirement Reference:** SEC-CTL-NonRTRIC-4, SEC-CTL-NonRTRIC-5, clause 5.1.2.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Non-RT RIC Framework supports OAuth 2.0 as a Server - -**Threat References:** T-NONRTRIC-01, T-NONRTRIC-02, T-NONRTRIC-03 - -**DUT/s:** Non-RT RIC - -**Test Name:** TC\_NonRTRIC\_OAuth2.0\_Framework\_Server - -**Purpose:** To verify the Non-RT RIC Framework supports OAuth 2.0 as a resource owner/server. - -**Procedure and execution steps****Preconditions** - -The DUT is acting as a Resource Owner and has OAuth 2.0 support enabled. - -The rest of the elements of the setup may be real or simulated. - -**Execution steps** - -Follow the test case in clause 6.6.2 of the present document. - -**Expected results** - -The DUT is able to authorize access to resources using OAuth 2.0. - -**Expected format of evidence:** Log files, traffic captures and/or report files. - -## 15.3 R1 interface - -Void - -## 15.4 A1 interface - -Void - -## 16 Security test of rApps - -### 16.1 Overview - -This clause contains security tests to validate the security protection mechanism specific to rApps deployed on Non-RT RIC. - -### 16.2 rApp Signing and Verification - -The security test cases defined in clause 9.5.2 apply to this clause. - -### 16.3 rApp Authorization - -#### 16.3.1 rApp OAuth 2.0 Client - -**Requirement Name:** rApp OAuth2.0 Client support - -**Requirement Reference:** SEC-CTL-NonRTRIC-6, clause 5.1.2.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** rApps provide client authorization requests to the Non-RT RIC Framework. - -**Threat References:** T-rAPP-04 - -**DUT/s:** rApps - -**Test Name:** TC\_OAuth2.0\_rApp - -**Purpose:** To verify the rApp supports OAuth 2.0 client capabilities. - -#### Procedure and execution steps - -##### Preconditions - -The DUT is acting as an OAuth2.0 Client with OAuth 2.0 support enabled. - -The rest of the elements of the setup may be real or simulated. - -##### Execution steps - -Follow the test case in clause 6.6.1 of the present document. - -##### Expected results - -The DUT is able to request access and be permitted access to resources using OAuth 2.0. - -**Expected format of evidence:** Log files, traffic captures and/or report files. - -## 17 Security test of SMO - -### 17.1 Overview - -This clause contains security tests to validate security protection mechanisms related to the SMO. The test cases validate the security of SMO termination of O1 interfaces, SMO, SMO Services (SMOS) Communications, SMO External Interfaces, and SMO Logging are secured to zero trust principles for confidentiality, integrity, authentication, - -and authorization. Definitions for the O-RAN terms SMO Service (SMOS), SMO Function (SMOF), SMO External Interfaces, and SMO External System are provided in [1]. - -The test cases apply to the normative security requirements specified in [5] based upon the following approved security architecture: - -The SMO enforces confidentiality, integrity and authenticity through an encrypted transport for the O1 interface and supports least privilege access control using the network configuration access control model (NACM) for authorization. - -The SMO supports mutual authentication and authorization of SMO Functions (SMOF) and External Interfaces. - -SMO Internal Communications provide communication and services between the SMO, SMOFs, Non-RT RIC Functions, and rApps. SMO Internal Communications shall provide confidentiality and integrity protection of data in transit and shall support mutual authentication and authorization for access to services and resources. - -SMO External Interfaces provide import of AI enrichment data from external data sources to the SMO. SMO External Interfaces shall provide confidentiality and integrity protection of data in transit and shall support mutual authentication and authorization for access to services and resources. - -## 17.2 Void - -## 17.3 SMO - -### 17.3.1 SMO OAuth 2.0 Resource Owner/Server - -**Requirement Name:** SMO supports OAuth 2.0 resource owner/server role - -**Requirement Reference:** SEC-CTL-SMO-3, clause 5.1.1.2.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** OAuth 2.0 security controls for SMO to authorize service requests from SMO Functions. - -**Threat References:** T-SMO-02, T-SMO-05 - -**DUT/s:** SMO, SMO Functions - -**Test Name:** TC\_SMO\_OAuth2.0\_Resource\_Owner\_Server - -**Purpose:** To verify that the SMO supports OAuth 2.0 resource owner/server capabilities. - -#### Procedure and execution steps - -##### Preconditions - -DUT is the SMO with OAuth 2.0 support enabled. - -##### Execution steps - -Follow the test case in clause 6.6.2 of the present document. - -##### Expected results - -The DUT is able to authorize/deny access requests received from SMO Functions using OAuth 2.0. - -**Expected format of evidence:** Log entries, packet captures, and screenshots. - -### 17.3.2 SMO OAuth 2.0 Client - -**Requirement Name:** SMO supports OAuth 2.0 client functionality - -**Requirement Reference:** SEC-CTL-SMO-4, clause 5.1.1.2.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** OAuth 2.0 security controls for SMO to support client functionality for service requests to other SMO Functions - -**Threat References:** T-SMO-02, T-SMO-05 - -**DUT/s:** SMO - -**Test Name:** TC\_SMO\_OAuth2.0\_Client - -**Purpose:** To verify the SMO supports OAuth 2.0 client capabilities. - -#### **Procedure and execution steps** - -##### **Preconditions** - -DUT is the SMO with OAuth 2.0 support enabled. - -##### **Execution steps** - -Follow the test case in clause 6.6.1 of the present document. - -##### **Expected results** - -The DUT is able to request and be permitted/denied access to resources using OAuth 2.0. - -**Expected format of evidence:** Log entries, packet captures, and screenshots. - -### **17.3.3 SMO mTLS for mutual authentication** - -**Requirement Name:** SMO support for mutual authentication of SMO Functions using mTLS - -**Requirement Reference:** SEC-CTL-SMO-5, clause 5.1.1.2.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** SMO support mTLS for mutual authentication with SMO Functions. - -**Threat References:** T-SMO-01, T-SMO-04 - -**DUT/s:** SMO - -**Test Name:** TC\_SMO\_mTLS - -**Purpose:** To verify the SMO supports mutual authentication with SMO Functions using mTLS, with PKI and X.509 certificates. - -#### **Procedure and execution steps** - -##### **Preconditions** - -DUT is the SMO with mTLS support enabled. An external OAuth 2.0 Authorization Server is available and configured. - -##### **Execution steps** - -Follow the test case in clause 6.3 of the present document. - -##### **Expected results** - -The DUT supports mutual authentication of SMO Functions using mTLS. - -**Expected format of evidence:** Log entries, packet captures, and screenshots. - -## 17.4 SMO Internal Communications - -### 17.4.1 TLS for SMO Internal Communications - -**Requirement Name:** TLS support for protection at transport layer between SMO Functions - -**Requirement Reference:** SEC-CTL-SMO-Internal-1, clause 5.1.1.2.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Data in transit protection with TLS for SMO Internal Communications - -**Threat References:** T-SMO-09 - -**DUT/s:** SMO, Non-RT RIC - -**Test Name:** TC\_SMO\_TLS\_Internal\_Communications - -**Purpose:** To verify the SMO supports TLS on SMO Internal Communications. - -#### Procedure and execution steps - -##### Preconditions - -DUT is the SMO with TLS support enabled. - -##### Execution steps - -Follow the test case in clause 6.3 of the present document. - -##### Expected results - -The SMO Internal Communications provide confidentiality and integrity protection using TLS for data in transit. - -**Expected format of evidence:** Log entries, packet captures, and screenshots. - -### 17.4.2 mTLS for SMO Internal Communications – SMO Functions - -**Requirement Name:** mTLS support for mutual authentication between SMO Functions - -**Requirement Reference:** SEC-CTL-SMO-Internal-2, clause 5.1.1.2.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Mutual authentication with mTLS for SMO Internal Communications - -**Threat References:** T-SMO-01, T-SMO-04 - -**DUT/s:** SMO - -**Test Name:** TC\_SMO\_mTLS\_Internal\_Communications - -**Purpose:** To verify SMO Functions support mutual authentication using mTLS, with PKI and X.509 certificates, for SMO Internal Communications. - -#### Procedure and execution steps - -##### Preconditions - -DUT is the SMO Function with mTLS support enabled. - -##### Execution steps - -Follow the test case in clause 6.3 of the present document. - -##### Expected results - -The DUT supports mutual authentication using mTLS. - -**Expected format of evidence:** Log entries, packet captures, and screenshots. - -## 17.5 SMO External Interfaces - -### 17.5.1 TLS for SMO External Interfaces - -**Requirement Name:** SMO External Interfaces support for TLS - -**Requirement Reference:** SEC-CTL-SMO-External-1, clause 5.1.1.2.3, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Data in transit protection with TLS on SMO External Interfaces - -**Threat References:** T-SMO-09 - -**DUT/s:** SMO - -**Test Name:** TC\_SMO\_TLS\_External\_Interfaces - -**Purpose:** To verify the SMO supports TLS on SMO External Interface. - -#### Procedure and execution steps - -##### Preconditions - -DUT is the SMO with TLS support enabled. - -##### Execution steps - -Follow the test case in clause 6.3 of the present document. - -##### Expected results - -The DUT's External Interface provides confidentiality and integrity protection using TLS for data in transit. - -**Expected format of evidence:** Log entries, packet captures, and screenshots. - -### 17.5.2 mTLS for SMO External Interfaces - -**Requirement Name:** SMO External Interfaces support for mTLS - -**Requirement Reference:** SEC-CTL-SMO-External-2, clause 5.1.1.2.3, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Mutual authentication with mTLS on SMO External Interfaces - -**Threat References:** T-SMO-01, T-SMO-04 - -**DUT/s:** SMO - -**Test Name:** TC\_SMO\_mTLS\_External\_Interfaces - -**Purpose:** To verify the SMO supports mutual authentication using mTLS, with PKI and X.509 certificates for SMO External Interfaces. - -#### Procedure and execution steps - -##### Preconditions - -DUT is the SMO with mTLS support enabled. - -##### Execution steps - -Follow the test case in clause 6.3 of the present document. - -#### Expected results - -The DUT supports mutual authentication of SMO Functions using mTLS for SMO External Interfaces. - -**Expected format of evidence:** Log entries, packet captures, and screenshots. - -### 17.5.3 SMO Framework OAuth 2.0 Resource Owner/Server for External Interface - -**Requirement Name:** SMO External Interfaces support for OAuth 2.0 resource owner/server role - -**Requirement Reference:** SEC-CTL-SMO-External-3, clause 5.1.1.2.3, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** SMO supports OAuth 2.0 resource owner/server role to authorize service requests from external systems - -**Threat References:** T-SMO-02, T-SMO-05 - -**DUT/s:** SMO - -**Test Name:** TC\_SMO\_OAuth2.0\_Resource\_Owner\_Server\_External\_Interface - -**Purpose:** To verify the SMO supports OAuth 2.0 resource owner/server capabilities for SMO External Interfaces. - -#### Procedure and execution steps - -##### Preconditions - -DUT is the SMO with OAuth 2.0 support enabled. An external OAuth 2.0 Authorization Server is available and configured. - -##### Execution steps - -Follow the test case in clause 6.6.2 of the present document. - -#### Expected results - -The DUT is able to authorize/deny access requests received from an external system using OAuth 2.0. - -**Expected format of evidence:** Log entries, packet captures, and screenshots. - -### 17.5.4 SMO Functions OAuth 2.0 Client - -**Requirement Name:** SMO External Interfaces support for OAuth 2.0 client functionality - -**Requirement Reference:** SEC-CTL-SMO-External-4, clause 5.1.1.2.3, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** SMO support as OAuth 2.0 client for service requests to external systems - -**Threat References:** T-SMO-02, T-SMO-05 - -**DUT/s:** SMO - -**Test Name:** TC\_SMO\_OAuth2.0\_Client\_External\_Interface - -**Purpose:** To verify if the SMO supports OAuth 2.0 client capabilities for External Interfaces. - -#### Procedure and execution steps - -##### Preconditions - -DUT is the SMO with OAuth 2.0 support enabled. An external OAuth 2.0 Authorization Server is available and configured. - -#### Execution steps - -Follow the test case in clause 6.6.1 of the present document. - -#### Expected results - -The DUT is able to request and be permitted/denied access to external resources using OAuth 2.0. - -**Expected format of evidence:** Log entries, packet captures, and screenshots. - -## 17.6 SMO Logging - -### 17.6.1 TLS for SMO Logging Export - -**Requirement Name:** SMO log export support for TLS via SMO External Interface - -**Requirement Reference:** SEC-CTL-SMO-Log-1, clause 5.1.1.2.4, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** TLS support for SMO Logging Export - -**Threat References:** T-SMO-16 - -**DUT/s:** SMO - -**Test Name:** TC\_SMO\_TLS\_Logging\_Export - -**Purpose:** To verify the SMO supports TLS for SMO logging export. - -#### Procedure and execution steps - -##### Preconditions - -DUT is the SMO with TLS support enabled. - -##### Execution steps - -Follow the test case in clause 6.3 of the present document. - -##### Expected results - -The DUT provides confidentiality and integrity protection for logging export. - -**Expected format of evidence:** Log entries, packet captures, and screenshots. - -### 17.6.2 mTLS for SMO Logging Export - -**Requirement Name:** mTLS support on SMO logging export - -**Requirement Reference:** SEC-CTL-SMO-Log-3, clause 5.1.1.2.4, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** SMO log export support for mutual authentication using mTLS with public key infrastructure (PKI) with X.509v3 certificates - -**Threat References:** T-SMO-01 - -**DUT/s:** SMO - -**Test Name:** TC\_SMO\_mTLS\_Logging\_Export - -**Purpose:** To verify the SMO supports mutual authentication using mTLS, with PKI and X.509 certificates, for SMO logging export. - -#### Procedure and execution steps - -##### Preconditions - -DUT is the SMO with mTLS support enabled. - -##### Execution steps - -Follow the test case in clause 6.3 of the present document. - -##### Expected results - -The DUT supports mutual authentication using mTLS for SMO logging export. - -**Expected format of evidence:** Log entries, packet captures, and screenshots. - ---- - -## 18 Security test of O-Cloud - -### 18.1 Overview - -This clause contains security tests to validate the security protection mechanism specific to O-Cloud hosting the O-RAN architecture elements/system. - -### 18.2 Void - -### 18.3 O-Cloud virtualization layer - -#### 18.3.1 Secure authentication (positive case) - -**Requirement Name:** Secure authentication to O-Cloud APIs - -**Requirement Reference:** REQ-SEC-OCLOUD-1, clause 5.1.8.1.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Authentication for accessing management interfaces of the O-Cloud Platform - -**Threat References:** T-VM-C-01, T-VM-C-02, T-VM-C-03, T-VM-C-04, T-VM-C-05, T-VM-C-06 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_OCloud\_Secure\_Authentication\_Positive - -**Purpose:** The purpose of this test is to ensure secure authentication to O-Cloud APIs. - -##### Procedure and execution steps - -##### Preconditions - -- O-Cloud authentication mechanism is enabled. -- Valid credentials are available for authentication. - -##### Execution steps - -Attempt to access O-Cloud APIs with valid authentication credentials: - -- Send an API request with valid authentication credentials. - -EXAMPLE: Send an API request by executing **curl** command or using a Kubernetes client using the valid API key or access token for authentication (e.g., valid kubeconfig file or service account token). - -- Capture the response received, including the status code and response body. -- Verify that the API response returns a success status code. - -#### Expected results - -The API response returns a success status code. - -#### Expected Format of Evidence: - -Logs containing the requests to the DUT and the responses from the DUT. - -### 18.3.2 Secure authentication (negative case) - -**Requirement Name:** Secure authentication to O-Cloud APIs - -**Requirement Reference:** REQ-SEC-OCLOUD-1, clause 5.1.8.1.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Authentication for accessing management interfaces of the O-Cloud Platform - -**Threat References:** T-VM-C-01, T-VM-C-02, T-VM-C-03, T-VM-C-04, T-VM-C-05, T-VM-C-06 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_OCloud\_Secure\_Authentication\_Negative - -**Purpose:** The purpose of this test is to intentionally validate the behaviour of the authentication mechanism when encountering invalid or unauthorized authentication credentials. - -#### Procedure and execution steps - -##### Preconditions - -O-Cloud authentication mechanism is enabled. - -##### Execution steps - -Attempt to access O-Cloud APIs with invalid authentication credentials: - -- Send an API request with invalid authentication credentials. - -EXAMPLE: Send an API request by executing **curl** command or using a Kubernetes client using the invalid or expired API key or access token for authentication (e.g., invalid kubeconfig file, expired service account token). - -- Capture the response received, including the status code and response body. -- Verify that the API response returns an authentication failure status code. - -#### Expected results - -The API response returns an authentication failure status code. - -#### Expected Format of Evidence: - -Logs containing the requests to the DUT and the responses from the DUT. - -### 18.3.3 Secure authorization (positive case) - -**Requirement Name:** Secure authorization for accessing O-Cloud APIs - -**Requirement Reference:** REQ-SEC-OCLOUD-2, clause 5.1.8.1.1, SEC-CTL-OCLOUD-1, clause 5.1.8.1.2, SEC-CTL-OCLOUD-ISO-3, clause 5.1.8.4.3, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** O-Cloud ensures authorized management access and enforce least privilege - -**Threat References:** T-VM-C-01, T-VM-C-02, T-VM-C-03, T-VM-C-04, T-VM-C-05, T-VM-C-06 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_OCloud\_Secure\_Authorization\_Positive - -**Purpose:** The purpose of this test is to verify that the authorization mechanism for accessing O-Cloud APIs is functioning correctly, ensuring that entities have appropriate permissions to perform specific actions on O-Cloud resources. - -#### Procedure and execution steps - -NOTE: Entities include Applications, SMO and O-Cloud software components. - -#### Preconditions - -- Valid authentication credentials. -- O-Cloud access control system is enabled containing different levels of permissions assigned to entities. - -EXAMPLE 1: Access control system such as Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC). - -#### Execution steps - -1) Authenticate with valid credentials: - -- Use valid authentication credentials to establish a connection with the O-Cloud API. - -2) Send an API request with authorized permissions: - -- Construct a valid API request to perform a specific action, - -EXAMPLE 2: specific action includes creating a pod, updating a deployment, or deleting a service. - -- Ensure that the requested action aligns with the entity's assigned permissions. -- Send the request to the O-Cloud API endpoint. - -3) Validate the response: - -- Verify that the API response returns a success status code indicating the action was successfully executed. - -#### Expected results - -The API response returns a success status code, confirming that the requested action was authorized and executed successfully. - -#### Expected Format of Evidence: - -Logs containing the requests to the DUT and the responses from the DUT. - -### 18.3.4 Secure authorization (negative case) - -**Requirement Name:** Secure authorization for accessing O-Cloud APIs - -**Requirement Reference:** REQ-SEC-OCLOUD-2, clause 5.1.8.1.1, SEC-CTL-OCLOUD-1, clause 5.1.8.1.2, SEC-CTL-OCLOUD-ISO-3, clause 5.1.8.4.3, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** O-Cloud ensures authorized management access and enforce least privilege - -**Threat References:** T-VM-C-01, T-VM-C-02, T-VM-C-03, T-VM-C-04, T-VM-C-05, T-VM-C-06 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_OCloud\_Secure\_Authorization\_Negative - -**Purpose:** The purpose of this test is to intentionally validate the behaviour of the authorization mechanism when encountering unauthorized or invalid access attempts. - -#### Procedure and execution steps - -##### Preconditions - -- Valid authentication credentials. -- O-Cloud access control system is enabled containing different levels of permissions assigned to entities. - -EXAMPLE 1: Access control system such as Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC). - -##### Execution steps - -- 1) Authenticate with valid credentials: - - Use valid authentication credentials to establish a connection with the O-Cloud API. -- 2) Send an API request with unauthorized permissions: - - Construct a valid API request to perform a specific action that exceeds the entity's assigned permissions,EXAMPLE 2: specific action includes creating a pod, updating a deployment, or deleting a service. - - Send the request to the O-Cloud API endpoint. -- 3) Validate the response: - - Verify that the API response returns a failure status code indicating the action was unauthorized. - -##### Expected results - -The API response returns a failure status code, indicating that the requested action was unauthorized. - -##### Expected Format of Evidence: - -Logs containing the requests to the DUT and the responses from the DUT. - -## 18.3.5 Validate network connections allowed by network policies - -**Requirement Name:** Isolation & secure communication between Applications - -**Requirement Reference:** REQ-SEC-OCLOUD-ISO-6, clause 5.1.8.4.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** O-Cloud enforces network policies that allow permitted connections. - -**Threat References:** T-VM-C-01, T-VM-C-02, T-VM-C-03, T-VM-C-04, T-VM-C-05, T-VM-C-06 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_OCloud\_Connection\_Allowed\_Policies - -**Purpose:** The purpose of this test is to ensure that network connections between VMs/Containers allowed by network policies are successfully established. - -#### Procedure and execution steps - -### Preconditions - -O-Cloud with network policies is configured to allow specific VMs/Containers to VMs/Containers communication. - -### Execution steps - -- 1) Deploy two VMs/Containers A and B, in different zones or with different environment. - -EXAMPLE 1: Zones such as namespaces in Kubernetes, environment such as labels in Kubernetes - -- 2) Define network policies that explicitly allow communication between the two VMs/Containers. -- 3) Attempt to establish a network connection from VM/Container A to VM/Container B using tools. - -EXAMPLE 2: tools such as curl or ping in Kubernetes - -- 4) Capture the response or output received. - -### Expected results - -The network connection from VM/Container A to VM/Container B is successfully established, indicating that the network policies allow the communication between the VMs/Containers. - -### Expected Format of Evidence: - -Logs containing the requests to the DUT and the responses from the DUT. - -## 18.3.6 Validate network connections not allowed by network policies - -**Requirement Name:** Isolation & secure communication between Applications - -**Requirement Reference:** REQ-SEC-OCLOUD-ISO-6, clause 5.1.8.4.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** O-Cloud enforces network policies that allow permitted connections. - -**Threat References:** T-VM-C-01, T-VM-C-02, T-VM-C-03, T-VM-C-04, T-VM-C-05, T-VM-C-06 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_OCloud\_Connection\_Not\_Allowed\_Policies - -**Purpose:** The purpose of this test is to ensure that network connections between VMs/Containers not allowed by network policies are blocked. - -### Procedure and execution steps - -#### Preconditions - -O-Cloud with network policies is configured to deny specific VM/Container to VM/Container communication. - -#### Execution steps - -- 1) Deploy two VMs/Containers A and B, in different zones or with different environment. - -EXAMPLE 1: Zones such as namespaces in Kubernetes, environment such as labels in Kubernetes - -- 2) Define network policies that explicitly deny communication between the two VMs/Containers. -- 3) Attempt to establish a network connection from VM/Container A to VM/Container B using tools. - -EXAMPLE 2: tools such as curl or ping in Kubernetes - -- 4) Capture the response or output received. - -### Expected results - -The network connection from VM/Container A to VM/Container B is blocked, indicating that the network policies correctly deny the communication between the VMs/Containers. - -#### Expected Format of Evidence: - -Logs containing the requests to the DUT and the responses from the DUT. - -### 18.3.7 Validate network connections from outside the allowed network ranges - -**Requirement Name:** Isolation & secure communication between Applications - -**Requirement Reference:** REQ-SEC-OCLOUD-ISO-6, clause 5.1.8.4.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** O-Cloud enforces network policies that allow permitted connections. - -**Threat References:** T-VM-C-01, T-VM-C-02, T-VM-C-03, T-VM-C-04, T-VM-C-05, T-VM-C-06 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_OCloud\_Connection\_Allowed\_Outside - -**Purpose:** The purpose of this test is to ensure that network connections from IP addresses outside the allowed network ranges are denied. - -#### Procedure and execution steps - -##### Preconditions - -O-Cloud with network policies is configured to restrict access based on IP ranges. - -##### Execution steps - -- 1) Define network policies that restrict access to certain IP ranges. -- 2) Attempt to access services or VMs/Containers from IP addresses outside the allowed ranges, either through direct IP access or using service names. -- 3) Capture the response or output received. - -**EXAMPLE:** In this test case, the service name refers to the Kubernetes service object's name. The service acts as a load balancer and provides a stable DNS name that can be used to access the pods associated with it. For example, consider a service named **my-service** that is linked with a set of pods. The test case involves attempting to access my-service from IP addresses outside the allowed ranges. This can be done using tools like curl or by making HTTP requests to *http://my-service*. - -##### Expected results - -Access attempts from outside the allowed IP ranges is denied, and the response or output indicates a connection failure. - -#### Expected Format of Evidence: - -Logs containing the requests to the DUT and the responses from the DUT. - -### 18.3.8 Exploitation of O-Cloud component vulnerabilities - -**Requirement Name:** O-Cloud hardening and secure configuration. - -**Requirement Reference:** REQ-SEC-SYS-1, clause 5.3.6.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Known vulnerabilities in the software of an O-RAN architecture element are identified - -**Threat References:** T-O-RAN-02, T-VM-C-01, T-VM-C-05 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_OCloud\_Vulnerability\_Scanning - -**Purpose:** The purpose of this test is to identify and assess the presence of vulnerabilities in O-Cloud components and evaluate the effectiveness of their mitigation measures. - -#### Procedure and execution steps - -##### Preconditions - -- O-Cloud with various O-Cloud components deployed. - -EXAMPLE: in the context of Kubernetes, components include etcd, kubelet - -- O-Cloud with security best practices is implemented. - -##### Execution steps - -- 1) Identify known vulnerabilities specific to the versions of used O-Cloud components using vulnerability scanning tools. -- 2) If known vulnerabilities exist, follow publicly available exploit scenarios or utilize penetration testing tools to attempt exploitation. -- 3) Monitor the O-Cloud and capture any signs of successful exploitation or vulnerabilities being triggered. - -##### Expected results - -For step 1), no known vulnerabilities exist in the O-Cloud - -For step 2), mitigation measures, such as applying security patches or configuration changes are implemented to address known vulnerabilities. - -For step 3), Exploit attempts fails to compromise the O-Cloud. - -##### Expected Format of Evidence: - -Logs containing the requests to the DUT and the responses from the DUT. - -## 18.3.9 Identification and remediation of insecure configuration settings - -**Requirement Name:** O-Cloud hardening and secure configuration - -**Requirement Reference:** REQ-SEC-O-CLOUD-ISO-7, Clause 5.1.8.4.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The O-Cloud Platform does not permit configuration change of any component without proper authorization - -**Threat References:** T-O-RAN-02, T-VM-C-01, T-VM-C-05 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_OCloud\_Insecure\_Configuration - -**Purpose:** The purpose of this test is to identify insecure configuration settings in the O-Cloud and verify the effectiveness of remediation measures. - -#### Procedure and execution steps - -##### Preconditions - -O-Cloud with a configuration review and hardening process in place. - -##### Execution steps - -- 1) Review the O-Cloud configuration for common security misconfigurations, such as weak authentication settings, insecure defaults, or unencrypted communication. -- 2) Identify and simulate scenarios where insecure configurations can be exploited. -- 3) Monitor the O-Cloud and capture any signs of insecure configurations being successfully exploited. - -#### Expected results - -- The O-Cloud configuration is hardened and securely configured to mitigate common security misconfigurations. -- Insecure scenarios are identified and remediated, ensuring a hardened O-Cloud. If insecure scenarios are rectified, testing has to be repeated. - -#### Expected Format of Evidence: - -Logs containing the requests to the DUT and the responses from the DUT. - -### 18.3.10 Validation of logging and monitoring for security incidents - -**Requirement Name:** logging and monitoring for security incidents - -**Requirement Reference:** REQ-SEC-OCLOUD-O2dms-4, clause 5.1.8.9.1.1, REQ-SEC-OCLOUD-O2ims-4, clause 5.1.8.9.1.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** O-Cloud DMS and IMS log SMO's management operations for auditing. - -**Threat References:** T-GEN-01, T-GEN-02, T-GEN-03, T-GEN-04, T-GEN-05, T-GEN-06 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_OCloud\_Security\_Logs - -**Purpose:** The purpose of this test is to validate logging and monitoring for security incidents. - -#### Procedure and execution steps - -##### Preconditions - -- An O-Cloud is deployed and operational -- A logging and monitoring system is implemented and configured to capture and analyse security events. - -##### Execution steps - -- 1) Simulate security incidents such as unauthorized access attempts or Application compromise: - - Attempt to perform unauthorized API requests or access O-Cloud resources without appropriate permissions. - - Mimic a compromised Application by running malicious code or attempting privilege escalation. - - Monitor the O-Cloud and capture any signs of security incidents being logged or detected. -- 2) Monitor the O-Cloud for detection and alerting of security events: - - Configure the logging and monitoring systems to capture relevant security events, such as failed authentication attempts, privilege escalation, or anomalous Application behaviour. - - Monitor the O-Cloud in real-time or periodically to detect the simulated security incidents. - - Verify that the monitoring system generates alerts or notifications for detected security events. - -#### Expected results - -- For the first step, unauthorized access attempts and Application compromise attempts are captured as security events in the logs. -- For the second step, the monitoring system detects and generates alerts for the simulated security incidents. - -**Expected Format of Evidence:** - -Logs containing the requests to the DUT and the responses from the DUT. - -### 18.3.11 O-Cloud Privilege Escalation Prevention - -**Requirement Name:** O-Cloud privilege escalation prevention - -**Requirement Reference:** REQ-SEC-OCLOUD-ISO-1, REQ-SEC-OCLOUD-ISO-3, clause 5.1.8.4.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** O-Cloud prevents unauthorized privilege escalation - -**Threat References:** T-VM-C-01 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_OCloud\_Privilege\_Escalation\_Prevention - -**Purpose:** To verify that privilege escalation is effectively prevented in O-Cloud by enforcing security policies. - -EXAMPLE 1: PodSecurity admission (PSA). - -**Procedure and execution steps****Preconditions:** - -O-Cloud with security policies (EXAMPLE: Kubernetes cluster with PodSecurity admission (PSA)) configured and enforced. - -**Execution steps:** - -- 1) Attempt to create a VM or Container that attempts to escalate privileges - -EXAMPLE 2: in Kubernetes by specifying the **hostPID: true** or **hostNetwork: true** field in the pod's security context. - -- 2) Monitor the API server response and logs - -**Expected results:** - -For step 1: The VM or Container creation request is denied by the O-Cloud API server. - -For step 2: The O-Cloud API server logs should show a message indicating a violation of the security policies. - -**Expected format of evidence:** - -- Screenshot: Displaying the API server's response to the VM or Container creation attempt. -- Executed Commands: Details of the VM or Container creation parameters and security context used. -- API Server Logs: Messages indicating a violation of security policies. -- Conclusion Logs: Indicating whether the test passed or failed based on expected results. - -### 18.3.12 O-Cloud mutual authentication - -**Requirement Name:** O-Cloud mutual authentication between applications - -**Requirement Reference:** SEC-CTL-O-CLOUD-ISO-1, clause 5.1.8.4.3, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** O-Cloud ensures mTLS authentication is enforced - -**Threat References:** T-GEN-04 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_OCLOUD\_MUTUAL\_AUTHENTICATION - -**Purpose:** To verify that communication between different applications running on the O-Cloud is secured through mutual TLS (mTLS) authentication. - -#### Procedure and execution steps - -##### Preconditions: - -- Environment: An O-Cloud is set up with two or more deployed applications - -EXAMPLE: A cluster with two applications, each running in separate pods. - -- mTLS configuration: Deployed applications in the O-Cloud are configured with mTLS as defined in [2] clause 4.2. -- Tools setup: Network sniffers, packet capture and TLS inspection tools are deployed to monitor and verify TLS handshake process. -- Valid, expired, and revoked certificates are prepared for testing. Ensure that the infrastructure for checking revoked certificates (CRL/OCSP server) is operational and accessible to the applications. - -##### Execution steps: - -- Initiate mTLS-secured sessions between applications and capture the TLS handshake process. - - Validate the exchange and authentication of certificates using TLS inspection tools. -- 1) Attempt connections using valid certificates and record the outcomes. - - 2) Attempt connections using expired certificates and record the outcomes. - - 3) Attempt connections, confirm that applications recognize the certificates as revoked (evidenced by querying the CRL or OCSP server), and record outcomes. - - 4) Attempt to establish an unauthenticated session (no certificate presented) and record the outcome. - -##### Expected results: - -- mTLS sessions are successfully established only with valid certificates. -- mTLS session establishment with expired certificates fails. -- mTLS session establishment with revoked certificates fails. -- Any attempt to initiate an unauthenticated session (without presenting a certificate) is rejected. - -##### Expected format of evidence: - -Logs from network sniffers, packet captures and TLS inspection tools showing: - -- Successful mTLS handshakes with valid certificates. -- Rejections due to expired certificates, ensuring the application appropriately identifies and handles certificates beyond their validity period. - -- Rejections due to revoked certificates, with specific emphasis on the application's process for recognizing revoked certificates through mechanisms such as CRL (Certificate Revocation List) and OCSP (Online Certificate Status Protocol) queries. -- Rejection of unauthenticated sessions, demonstrating the system's enforcement of mTLS authentication by not allowing sessions without certificate authentication. - -### 18.3.13 O-Cloud authorization - -**Requirement Name:** O-Cloud authorization - -**Requirement Reference:** REQ-SEC-OCLOUD-2, clause 5.1.8.1.1, SEC-CTL-OCLOUD-1, clause 5.1.8.1.2, SEC-CTL-O-CLOUD-ISO-3, clause 5.1.8.4.3, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** O-Cloud enforces access control, ensuring only authorized actions per least privilege - -**Threat References:** T-GEN-04 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_OCLOUD\_AUTHORIZATION - -**Purpose:** To verify that authorization policies are correctly enforced according to the least privilege principle. - -#### Procedure and execution steps - -##### Preconditions: - -- Environment: An O-Cloud is set up with two or more applications - -EXAMPLE 1: A cluster with two applications, each running in separate pods. - -- Access control configuration: Access control policies are defined and applied to applications, ensuring permissions are scoped to the minimum necessary privileges. -- Tools setup: auditing tools are deployed to monitor and verify access control policies. - -EXAMPLE 2: Kubernetes audit logs for access control verification. - -##### Execution steps: - -- Map out the actions each application can perform on another according to the access control policies. - -EXAMPLE 3: using 'kubectl describe role' and 'kubectl describe rolebinding' to detail the actions each application is permitted to perform on another under the access control policies. - -- Perform an action that is allowed by the access control policy and record the outcomes. Validate that permitted actions align with the mapped policies. - -EXAMPLE 4: using 'kubectl auth can-i' to validate that the action is permitted. - -- Attempt actions that are not permitted by the access control policies and record the outcomes. - -EXAMPLE 5: using 'kubectl auth can-i' to confirm that actions beyond the scope of granted permissions are denied. - -##### Expected results: - -- All actions that are explicitly granted by the access control policies are successfully performed without errors. Audit logs reflect the correct enforcement of these policies. -- Any attempts to perform actions outside the scope of granted permissions are denied, with audit logs accurately recording these access denials in accordance with the access control policies. - -EXAMPLE 6: Monitor Kubernetes audit logs to capture policy decisions, noting both allowed and denied actions. - -**Expected format of evidence:** - -Detailed logs capturing: - -- Allowed actions, correlating with the defined access control policies. -- Denied actions, specifically those attempted outside the granted permissions, highlighting the effective enforcement of access control policies. - -## 18.4 Application deployment by O-Cloud - -### 18.4.1 Verification of Application artifacts with valid signature by O-Cloud during deployment - -The security test cases defined in clause 9.5.2 apply to this clause. - -### 18.4.2 Verification of Application artifacts with incorrect signature by O-Cloud during deployment - -The security test cases defined in clause 9.5.2 apply to this clause. - -## 18.5 Resource Management and enforcement in O-Cloud - -### 18.5.1 O-Cloud Resource Consumption Limit Enforcement - -**Requirement Name:** Resource Management and enforcement in O-Cloud - -**Requirement Reference:** REQ-SEC-LCM-SD-5 to REQ-SEC-LCM-SD-6, clause 5.3.2.3.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The NFO compares an Application's resource consumption with the defined quotas from the Application descriptor and enforces limits. If the resource consumption exceeds the defined quotas, the NFO generates an alarm to notify the SMO. - -**Threat References:** T-VM-C-05, T-AppLCM-04, T-AppLCM-05 - -**DUT/s:** SMO (NFO) - -**Test Name:** TC\_OCloud\_Resource\_Consumption\_Limit\_Enforcement - -**Purpose:** To verify the DUT is able to ensure that resources (CPU, memory, etc.) consumed by VMs or Containers are within the defined limits, preventing any single application from monopolizing the system's resources. - -#### Procedure and execution steps - -##### Preconditions: - -- O-Cloud environment with resource quotas and limits enforced. -- A configured SMO to set and enforce resource quotas and limits. - -##### Execution steps: - -- 1) Set up resource quotas and limit ranges: - - Create a dedicated isolated environment for testing. - - Define a resource quota for the environment, specifying the maximum allowed CPU and memory. - -- Define a limit range to set default request and limit values for resources. -- 2) Attempt to deploy a VM or Container that requests resources beyond the defined limits: - - Create a VM or Container configuration that requests resources exceeding the set limits. - - Try to deploy the VM or Container in the test environment. - - 3) Monitor the deployment status and logs: - - Check the deployment status of the VM or Container. - - Check NFO logs for an alarm when a resource limit is exceeded. - -**Expected results:** - -For step 1: Confirmation that a dedicated isolated environment for testing has been setup and both resource quota and limit range have been established. - -For step 2: The deployment request for the VM or Container is denied or remains in a "Pending" or equivalent state. - -For step 3: Logs or descriptions should show a message indicating a violation of the resource quotas or limits. - -**Expected format of evidence:** - -- Configuration Details: Information on the set resource quotas and limit ranges, including the maximum allowed CPU and memory. -- Executed Commands: Details of the VM or Container creation parameters, specifically the requested resources. -- NFO Logs: Messages indicating any violations of the resource quotas or limits during the deployment attempt. -- Deployment Status: Logs or screenshots showing the status of the VM or Container deployment, especially if it's denied or remains in a "Pending" state due to resource constraints. - -EXAMPLE: using Kubernetes: - -- 1) Set up resource quotas and limit ranges in Kubernetes: - - Create a namespace: `kubectl create namespace test-limits` - - Apply a ResourceQuota and LimitRange as previously detailed. -- 2) Attempt to deploy a Pod in Kubernetes: - - Create a pod configuration (`resource-hog-pod.yaml`) that requests excessive resources. - - Deploy using: `kubectl apply -f resource-hog-pod.yaml` -- 3) Monitor the deployment status and logs in Kubernetes: - - Check pod status: `kubectl get pods -n test-limits` - - Describe the pod for details: `kubectl describe pod resource-hog -n test-limits` - -END of EXAMPLE - -## 18.5.2 O-Cloud Storage Volume Limit Enforcement - -**Requirement Name:** Resource Management and enforcement in O-Cloud - -**Requirement Reference:** REQ-SEC-LCM-SD-5, clause 5.3.2.3.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The NFO compares an Application's resource consumption with the defined quotas from the Application descriptor and enforces limits. If the resource consumption exceeds the defined quotas, the NFO generates an alarm to notify the SMO. - -**Threat References:** T-VM-C-05, T-AppLCM-04, T-AppLCM-05 - -**DUT/s:** SMO (NFO) - -**Test Name:** TC\_OCloud\_Storage\_Volume\_Limit\_Enforcement - -**Purpose:** To verify the DUT is able to limit the storage volume allocations for applications predefined in a O-Cloud environment. - -**Procedure and execution steps:** - -**Preconditions:** - -- O-Cloud environment with storage volume configurations. -- A configured SMO to set and enforce resource quotas for storage. - -**Execution steps:** - -- 1) Set up Storage Volume Quotas: - - Create a dedicated isolated environment for testing. - - Define a storage volume quota for the environment, specifying the maximum allowed storage volume size. -- 2) Attempt to allocate a storage volume beyond the defined limits: - - Create a configuration that requests a storage volume size exceeding the set limits. - - Deploy the configuration in the test environment. -- 3) Monitor the storage allocation status and logs: - - Check the status of the storage allocation. - - Monitor the NFO logs for an alarm being generated when a storage quota violation occurs. - -**Expected results:** - -For step 1: Confirmation that a dedicated isolated environment for testing has been setup and storage volume quota has been defined. - -For step 2: The storage volume allocation request is denied. - -For step 3: Logs or descriptions should show a message indicating a violation of the storage quotas. - -**Expected format of evidence:** - -- **Configuration Details:** Information on the set storage volume quotas, including the maximum allowed storage volume size. -- **Executed Commands:** Details of the storage volume allocation parameters, specifically the requested storage size. -- **NFO Logs:** Messages indicating any violations of the storage volume quotas during the allocation attempt. -- **Allocation Status:** Logs or screenshots showing the status of the storage volume allocation, especially if it is denied due to exceeding the set limits. - -EXAMPLE: using Kubernetes: - -- Create a namespace: `kubectl create namespace test-storage` - -- Apply a ResourceQuota for storage: -apiVersion: v1 -kind: ResourceQuota -metadata: -  name: storage-quota -  namespace: test-storage -spec: -  hard: -    requests.storage: 10Gi -- Apply the ResourceQuota: `kubectl apply -f storage-quota.yaml` -- Create and deploy a PersistentVolumeClaim (PVC) requesting 15Gi. -- Monitor the PVC status and logs. - -END of EXAMPLE - -## 18.5.3 O-Cloud CPU Overcommit Prevention - -**Requirement Name:** Resource Management and enforcement in O-Cloud - -**Requirement Reference:** REQ-SEC-LCM-SD-5 to REQ-SEC-LCM-SD-6, clause 5.3.2.3.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The NFO compares an Application's resource consumption with the defined quotas from the Application descriptor and enforces limits. If the resource consumption exceeds the defined quotas, the NFO generates an alarm to notify the SMO. - -**Threat References:** T-VM-C-05, T-AppLCM-04, T-AppLCM-05 - -**DUT/s:** SMO (NFO) - -**Test Name:** TC\_OCloud\_CPU\_Overcommit\_Prevention - -**Purpose:** To verify that the O-Cloud does not overcommit CPU resources, leading to performance degradation or system instability. - -### Procedure and execution steps - -#### Preconditions: - -- O-Cloud with CPU allocation settings. -- A configured SMO to manage CPU overcommitment. - -#### Execution steps: - -- 1) Set CPU Overcommit Ratios: - - Create a dedicated isolated environment for testing. - - Define CPU overcommit ratios. -- 2) Attempt to deploy multiple applications: - - Sequentially deploy applications until the CPU limits are reached based on the overcommit ratios. - - Monitor the CPU utilization of each deployed application. -- 3) Monitor the deployment status and CPU utilization metrics: - - Check the deployment status of the applications. - -- Monitor CPU utilization metrics. -- Check NFO logs for an alarm when an application exceeds CPU limits. - -**Expected results:** - -For step 1: Confirmation that a dedicated isolated environment for testing has been setup and CPU overcommit ratios has been defined. - -For step 2: Applications should not be deployed beyond the capacity determined by the CPU overcommit ratios. - -For step 3: CPU utilization metrics should remain stable and within acceptable thresholds. NFO generates an alarm when CPU limits are exceeded. - -**Expected format of evidence:** - -- Configuration Details: Information on the set CPU overcommit ratios. -- Executed Commands: Details of the application deployments and their respective CPU utilization. -- NFO Logs: Messages indicating any violations of the CPU overcommit ratios during application deployments. -- Deployment Status: Logs or screenshots showing the status of the application deployments, especially if any are denied due to reaching CPU limits. -- CPU Utilization Metrics: Graphs or logs showing the CPU utilization of each deployed application, ensuring they remain within acceptable thresholds. - -EXAMPLE: using Kubernetes: - -- 1) Set CPU Overcommit Ratios: - - Manage CPU overcommitment in Kubernetes by setting CPU requests and limits on Pods. -- 2) Attempt to deploy multiple applications: - - Deploy a Pod with a CPU request of '500m' (half a CPU core) and a limit of '1' (one full CPU core). -- 3) Monitor the deployment status and CPU utilization metrics: - - Use 'kubectl describe node ' to view CPU allocation and utilization. - - Monitor CPU metrics using tools like Prometheus. - -END of EXAMPLE - -## 18.5.4 O-Cloud Memory Overcommit Prevention - -**Requirement Name:** Resource Management and enforcement in O-Cloud - -**Requirement Reference:** REQ-SEC-LCM-SD-5 to REQ-SEC-LCM-SD-6, clause 5.3.2.3.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The NFO compares an Application's resource consumption with the defined quotas from the Application descriptor and enforces limits. If the resource consumption exceeds the defined quotas, the NFO generates an alarm to notify the SMO. - -**Threat References:** T-VM-C-05, T-AppLCM-04, T-AppLCM-05 - -**DUT/s:** SMO (NFO) - -**Test Name:** TC\_OCloud\_Memory\_Overcommit\_Prevention - -**Purpose:** To verify that the O-Cloud does not overcommit memory resources. - -## Procedure and execution steps - -### Preconditions: - -- O-Cloud with memory allocation settings. -- A configured SMO to manage memory overcommitment - -### Execution steps: - -- 1) Set Memory Overcommit Ratios: - - Create a dedicated isolated environment for testing. - - Define memory overcommit ratios. -- 2) Attempt to deploy applications: - - Sequentially deploy applications until memory limits are reached based on the overcommit ratios. - - Monitor memory utilization of each deployed application. -- 3) Monitor deployment status and memory utilization metrics: - - Check deployment status of the applications. - - Monitor memory utilization metrics. - - Check NFO logs for an alarm when an application exceeds memory limits - -### Expected results: - -For step 1: Confirmation that a dedicated isolated environment for testing has been setup and memory overcommit ratios has been defined. - -For step 2: Applications should not be deployed beyond the capacity determined by the memory overcommit ratios. - -For step 3: Memory utilization should remain stable and within acceptable thresholds. NFO generates an alarm when memory limits are exceeded. - -### Expected format of evidence: - -- Configuration Details: Information on the set memory overcommit ratios. -- Executed Commands: Details of the application deployments and their respective memory use. -- NFO Logs: Messages indicating any violations of the memory overcommit ratios during application deployments. -- Deployment Status: Logs or screenshots showing the status of the application deployments, especially if any are denied due to reaching memory limits. -- Memory Use Metrics: Graphs or logs showing the memory utilization of each deployed application, ensuring they remain within acceptable thresholds. - -EXAMPLE: using Kubernetes: - -- 1) Set Memory Overcommit Ratios: - - Manage memory overcommitment in Kubernetes by setting memory requests and limits on Pods. -- 2) Attempt to deploy applications: - - Deploy a Pod with a memory request of '256Mi' and a limit of '512Mi'. -- 3) Monitor deployment status and memory utilization metrics: - -- Use `kubectl describe node ` to view memory allocation and utilization. -- Monitor memory metrics using tools like Prometheus. - -END of EXAMPLE - -## 18.5.5 O-Cloud Network Overcommit Prevention - -**Requirement Name:** Resource Management and enforcement in O-Cloud - -**Requirement Reference:** REQ-SEC-OCLOUD-ISO-6, clause 5.1.8.4.2 REQ-SEC-LCM-SD-5 to REQ-SEC-LCM-SD-6, clause 5.3.2.3.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Prevention of network bandwidth overcommitment in the O-Cloud environment - -**Threat References:** T-VM-C-05, T-AppLCM-04, T-AppLCM-05 - -**DUT/s:** O-Cloud, SMO (NFO) - -**Test Name:** TC\_OCloud\_Network\_Overcommit\_Prevention - -**Purpose:** To verify that the O-Cloud environment does not overcommit network bandwidth. - -### Procedure and execution steps - -#### Preconditions: - -- O-Cloud environment with network configurations. -- Tools to manage network overcommitment. - -#### Execution steps: - -- 1) Set Network Overcommit Ratios: - - Define network bandwidth overcommit ratios. -- 2) Attempt to utilize network bandwidth: - - Deploy applications designed to generate high network traffic. - - Monitor network traffic. -- 3) Monitor network traffic metrics: - - Check network traffic metrics for the applications. - - Check NFO logs for an alarm when an application exceeds network bandwidth limits. - -#### Expected results: - -For step 1: Confirmation that network bandwidth overcommit ratios has been defined. - -For steps 2 and 3: Applications' network traffic should be throttled or limited once the bandwidth determined by the overcommit ratios is reached. NFO generates an alarm when network limits are exceeded. - -#### Expected format of evidence: - -- Configuration Details: Information on the set network bandwidth overcommit ratios. -- Executed Commands: Details of the application deployments and their respective network traffic generation. -- O-Cloud and NFO Logs: Messages indicating any violations of the network overcommit ratios during high network traffic. - -- Deployment Status: Logs or screenshots showing the status of the application deployments, especially if network traffic is throttled or limited. -- Network Traffic Metrics: Graphs or logs showing the network traffic of each deployed application, ensuring they remain within the set bandwidth limits. - -EXAMPLE: using Kubernetes: - -1) Set Network Overcommit Ratios: - -- Native Kubernetes doesn't offer direct network bandwidth controls. However, third-party plugins like 'Calico' or 'Cilium' can be used to set network policies that limit bandwidth. - -2) Attempt to utilize network bandwidth: - -- Deploy a Pod and apply a network policy that limits its bandwidth. - -3) Monitor network traffic metrics: - -- Use monitoring tools integrated with the network plugin (e.g., 'calicoctl' for Calico) to observe the network traffic metrics. - -END of EXAMPLE - -## 18.5.6 O-Cloud Storage Overcommit Prevention - -**Requirement Name:** Resource Management and enforcement in O-Cloud - -**Requirement Reference:** REQ-SEC-LCM-SD-5 to REQ-SEC-LCM-SD-6, clause 5.3.2.3.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The NFO compares an Application's resource consumption with the defined quotas from the Application descriptor and enforces limits. If the resource consumption exceeds the defined quotas, the NFO generates an alarm to notify the SMO. - -**Threat References:** T-VM-C-05, T-AppLCM-04, T-AppLCM-05 - -**DUT/s:** SMO (NFO) - -**Test Name:** TC\_OCloud\_Storage\_Overcommit\_Prevention - -**Purpose:** To verify that the O-Cloud does not overcommit storage resources. - -**Procedure and execution steps** - -**Preconditions:** - -- O-Cloud environment with storage configurations. -- A configured SMO to manage Storage overcommitment. - -**Execution steps:** - -1) Set Storage Overcommit Ratios: - -- Define storage overcommit ratios. - -2) Attempt to allocate storage beyond defined limits: - -- Deploy applications that request storage space. -- Monitor storage allocation and utilization. - -3) Monitor storage allocation and utilization metrics: - -- Check storage metrics for the applications. -- Check NFO logs for an alarm when an application exceeds storage limits. - -**Expected results:** - -For step 1: Confirmation that storage overcommit ratios has been defined. - -For step 2: Storage allocations do not exceed the capacity determined by the storage overcommit ratios. - -For step 3: Storage usage remains stable and within acceptable thresholds. NFO generates an alarm when storage limits are exceeded. - -**Expected format of evidence:** - -- Configuration Details: Information on the set storage overcommit ratios. -- Executed Commands: Details of the application deployments and their respective storage requests. -- NFO Logs: Messages indicating any violations of the storage overcommit ratios during storage allocation. -- Deployment Status: Logs or screenshots showing the status of the application deployments, especially if storage allocations are denied or limited. -- Storage usage Metrics: Graphs or logs showing the storage utilization of each deployed application, ensuring they remain within the set storage limits. - -EXAMPLE: using Kubernetes: - -- 1) Set Storage Overcommit Ratios: - - Use PersistentVolumeClaims (PVCs) with specific storage requests. Overcommitment can occur if the total storage requested by PVCs exceeds the actual available storage. -- 2) Attempt to allocate storage beyond defined limits: - - Deploy a Pod that uses a PVC requesting more storage than available on the PersistentVolume (PV). -- 3) Monitor storage allocation and utilization metrics: - - Use 'kubectl get pvc' and 'kubectl get pv' to monitor storage allocations. - - Monitor storage metrics using tools like Prometheus. - -END of EXAMPLE - -## 18.6 Secure Update - -### 18.6.1 O-Cloud Infrastructure Software Package Integrity - Positive - -**Requirement Name:** O-Cloud software images authenticity and Integrity - -**Requirement Reference:** REQ-SEC-ALM-PKG-2 to REQ-SEC-ALM-PKG-6, REQ-SEC-ALM-PKG-16, clause 5.3.2.1.1, SEC-CTL-ALM-PKG-1, SEC-CTL-ALM-PKG-1B, clause 5.3.2.1.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Ensure Authenticity and Integrity of O-Cloud Software Images - -**Threat References:** T-GEN-01 - -**DUT/s:** O-Cloud, SMO - -**Test Name:** TC\_OCloud\_Software\_Package\_Integrity - -**Purpose:** To verify the O-Cloud software image authenticity and integrity. - -### Procedure and execution steps - -#### Preconditions - -- Signed O-Cloud software package as per Clause 5 of O-RAN Security Protocols Specifications [2] -- All necessary artifacts of the O-Cloud software image (public key, digitally signed certificates, signature (Signed hash) encryption key if any for security-sensitive artifacts) are provided. - -EXAMPLE: O-Cloud software includes AAL drivers, IMS, DMS, Host OS, Hypervisor, Container Engine. - -#### Execution steps - -- 1) The tester is properly authenticated and have the required access privileges to perform the test activity. -- 2) The tester shall verify the authenticity and integrity of the list of images. The O-Cloud software package shall be verified with the provided X.509 certificate and signature provided by the O-Cloud Software Provider. The cryptographic hash of the software image is calculated and verified against the hash in the signature by the Software Provider. -- 3) On successful validation of O-Cloud software images in Step 2, the Service Provider shall sign the verified O-cloud software image with its private key and onboard it to the SMO. -- 4) The newly signed O-Cloud images shall be onboarded to the O-cloud Image Repository. -- 5) The tester shall verify the digital signature of the O-Cloud software image bundle provided by the Software and Service Provider before deployment. -- 6) Monitor the SMO logs for signature verification events related to the upgrade. -- 7) Monitor the O-Cloud logs for any signature verification events related to the upgrade. - -#### Expected results - -Logs show that the software package integrity check has been executed for the O-Cloud software at each stage - -The signature validation for the O-Cloud software image during onboarding are checked and is successful. - -#### Expected format of evidence: - -Snapshots captured in SMO logs regarding the Signature verification success. - -Logs from SMO and O-Cloud (O2ims logs) to indicate the successful signature verification from the Software Provider. - -## 18.6.2 O-Cloud Infrastructure Software Package Integrity Failure – Negative - -**Requirement Name:** O-Cloud software images authenticity and Integrity - -**Requirement Reference:** REQ-SEC-ALM-PKG-2 to REQ-SEC-ALM-PKG-6, REQ-SEC-ALM-PKG-16, clause 5.3.2.1.1, SEC-CTL-ALM-PKG-1, SEC-CTL-ALM-PKG-1B, clause 5.3.2.1.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Ensure Authenticity and Integrity of O-Cloud Software Images - -**Threat References:** T-GEN-01 - -**DUT/s:** O-Cloud, SMO - -**Test Name:** TC\_OCloud\_Software\_Package\_Integrity\_Failure - -**Purpose:** To verify the O-Cloud software image authenticity and integrity validation failure for invalid O-cloud software image. - -## Procedure and execution steps - -### Preconditions - -- O-Cloud software package obtained from the Software Provider. -- All necessary artifacts of the O-Cloud software image (public key, digitally signed certificates, Signature (signed hash) encryption key if any for security-sensitive artifacts) are provided. - -EXAMPLE: O-Cloud software includes AAL drivers, IMS, DMS, Host OS, Hypervisor, Container Engine. - -### Execution steps - -- 1) The tester is properly authenticated and has the required access privileges to perform the upgrade activity. -- 2) Attempt to validate the O-Cloud Software with the wrong public key. -- 3) Verify that the SMO detects the incorrect cryptographic signature and does not allow onboarding of the software package. -- 4) Monitor the SMO logs for any signature verification events related to the software integrity check. - -### Expected results - -Logs show that the software package integrity check has failed. - -The O-cloud software image shall not be onboarded due to the software integrity failure. - -### Expected format of evidence: - -Snapshots captured in SMO regarding the signature verification failure. - -SMO Logs: Onboarding failure logs to indicate that integrity failure for the O-Cloud software Package. - -## 18.6.3 Secure Update procedure for O-Cloud Platform – Positive - -**Requirement Name:** Secure update of O-Cloud software at the infrastructure level layer. - -**Requirement Reference:** REQ-SEC-OCLOUD-SU-1, REQ-SEC-OCLOUD-SU-5, REQ-SEC-OCLOUD-SU-7, clause 5.1.8.5.1, SEC-CTL-OCLOUD-SU-4, SEC-CTL-OCLOUD-SU-7, clause 5.1.8.5.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Ensure secure update of O-Cloud Software Images at the Infrastructure level. - -**Threat References:** T-GEN-01 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_SECURE\_UPDATE\_OF\_O-CLOUD\_PLATFORM - -**Purpose:** To verify the secure update procedure for the O-Cloud Infrastructure using verified O-cloud software image. - -## Procedure and execution steps - -### Preconditions - -- Verified O-Cloud software package obtained from Service Provider. -- All necessary artifacts of the O-Cloud software image (public key, digitally signed certificates, encryption key if any for security-sensitive artifacts) shall be provided. -- All necessary documents related to the Upgrade procedure of the O-Cloud components shall be available. -- All necessary dependencies for O-Cloud software packages are considered prior to update. -- All documents related to backward compatibility are made available by the O-Cloud Software provider. - -EXAMPLE 1: O-Cloud software includes AAL drivers, IMS, DMS, Host OS, Hypervisor, Container Engine. - -#### Execution steps - -- 1) The tester is properly authenticated and has the required access privileges to perform the upgrade activity. -- 2) The O-Cloud Platform to ensure image verification. -- 3) The tester performs all the necessary pre-upgrade steps on the O-Cloud Platform to ensure successful update. - -EXAMPLE 2: Back up (using Snapshots, Clones) any important components, such as app-level state stored in a database, or state of critical nodes. - -- 4) As per the Upgrade documentation, the tester shall perform the upgrade of the O-Cloud Platform components. - -EXAMPLE 3: Phased upgrades for service availability. - -EXAMPLE 4: Stage the Upgrade procedure: upgrade control plane nodes and upgrade the worker nodes. - -- 5) Monitor the O-Cloud logs (see EXAMPLE 5) for the update steps performed on the platform. - -EXAMPLE 5: O2ims logs - -- 6) Perform a Post-Update Audit to verify the status of the O-Cloud Platform. -- 7) Verify in the SMO that the software version for the O-Cloud platform components is updated to the required version. - -#### Expected results - -The version of the O-Cloud software components is updated to the required version. - -EXAMPLE 6: AAL driver version, IMS version, DMS version, Host OS version, Hypervisor, Container Engine. - -#### Expected format of evidence: - -O-Cloud logs: Log captures indicating the Steps performed during the Update. - -Snapshot: Executed command on CLI, GUI, API server - -SMO Log: Notification on the successful upgrade of the O-Cloud components. - -### 18.6.4 Secure Update failure and rollback - -**Requirement Name:** Rollback to the previous version on the unsuccessful update of the O-Cloud Platform. - -**Requirement Reference:** REQ-SEC-OCLOUD-SU-5, REQ-SEC-OCLOUD-SU-6, clause 5.1.8.5.1, SEC-CTL-OCLOUD-SU-6, SEC-CTL-OCLOUD-SU-7, clause 5.1.8.5.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The O-Cloud platform maintains its last verified state if updates fail or incidents occur during update. - -**Threat References:** T-GEN-01 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_SECURE\_UPDATE\_FAILURE\_OF\_O-CLOUD\_PLATFORM - -**Purpose:** To verify on failure of secure update procedure for the O-Cloud platform, it rolls back to its last verified state. - -#### Procedure and execution steps - -#### Preconditions - -- A valid O-Cloud platform software package is available. The version of the package is greater than the stable version running in the O-Cloud platform. -- The O-Cloud platform is running a stable version of its software. - -EXAMPLE 1: O-Cloud software includes AAL drivers, IMS, DMS, Host OS, Hypervisor, Container Engine. - -#### Execution steps - -- 1) The O-Cloud Platform verifies the signature of the new software package. -- 2) The tester performs all the pre-upgrade steps on the O-Cloud Platform. - -EXAMPLE 2: Back up any important components, such as app-level state stored in a database, state of critical nodes. - -- 3) Begin the update according to vendor documentation (e.g., phased upgrades). -- 4) Simulate an upgrade failure scenario. - -EXAMPLE 3: Unexpected upgrade termination, Abrupt Power failure, Network disruption. - -- 5) Monitor the O-Cloud logs (see EXAMPLE 4) for the upgrade steps performed on the platform. Verify that platform detects the failure and initiates an automatic rollback. - -EXAMPLE 4: O2ims logs - -- 6) Confirm that the O-Cloud platform has reverted to the same version of its software used prior to performing step 1 and confirm that the software execution is stable and operates as expected on the O-Cloud platform. - -#### Expected results - -The O-Cloud platform automatically rolls back to its previous version and last verified state. - -#### Expected format of evidence: - -O-Cloud logs indicating secure update failure detection and rollback. - -### 18.6.5 Unauthorised Rollback Prevention - -**Requirement Name:** Unauthorized rollback prevention to an earlier vulnerable version - -**Requirement Reference:** REQ-SEC-OCLOUD-SU-6, clause 5.1.8.5.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The O-Cloud platform prevents the unauthorized rollback of its software to an earlier vulnerable version. - -**Threat Reference:** T-GEN-01 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_UPDATE\_ROLLBACK\_PREVENTION\_O-CLOUD\_PLATFORM - -**Purpose:** To verify that the O-Cloud platform prevents unauthorized rollback to an earlier vulnerable version of its software, even if the rollback package is correctly signed, while allowing authorized rollback under controlled conditions. - -#### Procedure and execution steps - -##### Preconditions - -- The O-Cloud platform has a newer software version installed and operational. -- A correctly signed older vulnerable software version is available. - -- An incorrectly signed older non-vulnerable software version is also available. - -### Execution steps - -- 1) Unauthorized rollback attempt to a vulnerable version: - - Initiate a rollback using the correctly signed older vulnerable version of the software. - - Observe if the O-Cloud platform detects and rejects the rollback attempt. -- 2) Authorized rollback scenario (if required for performance recovery): - - Initiate an authorized rollback using the correctly signed older version of the software following the approved rollback process. - - Verify that the O-Cloud platform allows rollback in this scenario. - -### Expected results - -For step 1, the platform rejects unauthorized rollback attempts. - -For step 2, the platform successfully executes the authorized rollback. - -### Expected format of evidence - -Logs showing: - -- Rejection events for unauthorized rollback attempts. -- Authorized rollback initiation and completion logs. - -Screenshot showing the version status and error messages. - -## 18.7 Secure Storage - -### 18.7.1 Sensitive data protection in O-Cloud - -**Requirement Name:** Sensitive data protection in O-Cloud - -**Requirement Reference:** REQ-SEC-ALM-PKG-13, clause 5.3.2.1.1, REQ-SEC-OCLOUD-SS-1, clause 5.1.8.6.1, SEC-CTL-OCLOUD-SS-1, clause 5.1.8.6.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The O-Cloud Platform ensures the confidentiality and integrity of sensitive data at rest, in use, and in transit. - -**Threat References:** T-GEN-05 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_DATA\_PROTECTION\_OCLOUD - -**Purpose:** To validate that the O-Cloud ensures the integrity and confidentiality of sensitive data at rest, in use, and in transit, using state-of-the-art encryption and security practices. - -### Procedure and execution steps - -#### Preconditions: - -O-Cloud operational with a simulated deployment of workloads. - -#### Execution steps: - -- 1) Data at rest: - -- Store simulated sensitive data (e.g., secrets) in O-Cloud storage. - - Verify encryption using tools designed to check for industry-standard encryption mechanisms, focusing on confirming that data is encrypted to current security standards. -- 2) Data in use: -- Process sensitive data using an application. - - Identify write operations involving sensitive data - - Employ process monitoring tools to monitor file I/O operations and capture all write activities. - - Look for write operations to temporary file paths, cache directories or outside of the application secure storage. - - Analyse the context of write operations – are they occurring during a process that handles sensitive data? - - Ensure that the application does not log sensitive information - - Review the application's logging configuration and log output. - - Verify that sensitive data is either not logged or appropriately anonymized/encrypted before being logged. - - Check for the use of secure enclaves, if applicable. -- 3) Data in Transit: -- Initiate data transfer between O-Cloud services. - - Use packet-sniffing tools to capture the data packets. - - Analyse the TLS encrypted data, ensuring TLS is used as specified in O-RAN Security Protocols Specifications [2], clause 4.2. - -#### Expected Results: - -- Sensitive data in O-Cloud storage is encrypted according to current industry standards. Unauthorized access attempts are logged and denied. -- Data processing is secure, with no plaintext data exposure in logs or disk. Secure enclaves are used where relevant. -- All data transfers employ TLS as specified in O-RAN Security Protocols Specifications [2], clause 4.2. - -#### Expected Format of Evidence: - -- Screenshots and logs showing encryption validation and the response to unauthorized access attempts. -- Logs from process monitoring tools demonstrating the handling of sensitive data during processing. -- Packet capture files confirming the data encryption in transit using TLS as specified in O-RAN Security Protocols Specifications [2], clause 4.2. - -## 18.7.2 Secure data deletion in O-Cloud - -**Requirement Name:** Secure data deletion in O-Cloud - -**Requirement Reference:** REQ-SEC-OCLOUD-SS-2, clause 5.1.8.6.1, SEC-CTL-OCLOUD-SS-2, SEC-CTL-OCLOUD-SS-3, clause 5.1.8.6.2 O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The O-Cloud Platform supports secure deletion of data from storage and memory, ensuring that unused or deallocated data is irrecoverable by applying media-specific sanitization techniques and overwriting addressable memory locations with secure patterns. - -**Threat References:** T-GEN-05 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_DATA\_DELETION\_OCLOUD - -**Purpose:** To ensure that the O-Cloud platform securely deletes data from addressable memory locations that are no longer in use, by overwriting them with specific binary patterns. - -#### Procedure and execution steps - -##### Preconditions: - -- O-Cloud platform operational with workloads. -- Tools for memory analysis are available. - -EXAMPLE 1: **dd** for Unix/Linux or **sdelete** for Windows environments - -- File recovery tools for testing data recoverability after deletion. - -EXAMPLE 2: **TestDisk** - -##### Execution steps: - -1) Data preparation: - -- Create files with identifiable data patterns. - -EXAMPLE 3: a file filled with a repeating pattern of '1234' - -- Store these files in the O-Cloud platform's memory or storage system. - -2) Data deletion: - -- Delete the files using the O-Cloud platform's standard deletion process, which should invoke secure deletion process. - -3) Verification of secure deletion: - -- Inspect the memory or storage locations where the files were stored to confirm that the data has been overwritten. -- Search for both the original data patterns and the specific overwriting patterns (zeroes, ones, random). - -4) Data recovery attempt: - -- Use data recovery tools to attempt to retrieve the deleted files or any part of them. -- Assess if any of the original data or identifiable patterns can be recovered. - -##### Expected Results: - -- Deleted data locations are overwritten with the specified binary patterns. -- File recovery attempts are not able to reconstruct any meaningful data from these locations. - -##### Expected Format of Evidence: - -- Logs or screenshots from memory analysis tools showing the overwriting patterns. -- Reports from file recovery tools indicating the failure to recover any meaningful data. - -## 18.7.3 Data isolation in VM/Container reallocation - -**Requirement Name:** Data isolation in VM/Container reallocation - -**Requirement Reference:** REQ-SEC-OCLOUD-SS-3, clause 5.1.8.6.1, SEC-CTL-OCLOUD-SS-2, clause 5.1.8.6.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The O-Cloud Platform ensures that any data contained in a resource is not accessible when it is de-allocated from one VM/Container and reallocated to another by supporting secure deletion of data in addressable memory locations before reuse. - -**Threat References:** T-GEN-05 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_DATA\_ISOLATION\_VM\_CONTAINER\_OCLOUD - -**Purpose:** To verify that the O-Cloud effectively prevents data contained in a resource (like memory or storage) from being accessible after it is de-allocated from one VM/Container and reallocated to another. - -### Procedure and execution steps: - -#### Preconditions: - -- Set up multiple VMs/Containers within the O-Cloud. -- Tools for analyzing memory and storage content - -EXAMPLE: **hexdump, dd**, memory inspection tools - -#### Execution steps: - -- 1) Resource allocation and data storage: - - Allocate a dedicated resource (like a disk volume or memory segment) to a VM/Container. - - Store known test data in this resource. -- 2) Resource de-allocation & re-allocation: - - De-allocate the resource from the first VM/Container. - - Re-allocate the same resource to a different VM/Container. -- 3) Data accessibility check: - - Within the new VM/Container, attempt to access any residual data from the previous allocation. - - Use data analysis tools to inspect the resource for traces of the previous data. -- 4) Verification of data isolation: - - Confirm that no data from the first VM/Container is accessible or present in the resource after re-allocation. - -#### Expected Results: - -- No trace of the test data is found in the reallocated resource. -- The new VM/Container doesn't have access to any residual data from the previous allocation. - -#### Expected Format of Evidence: - -Logs or screenshots showing the absence of the test data in the re-allocated resource. - -## 18.8 Chain of trust - -### 18.8.1 Chain of Trust verification in static O-Cloud SW - -**Requirement Name:** Support of root of trust and integrity verification of static O-Cloud SW (Firmware and BIOS/UEFI, Bootloader, OS kernel) - -**Requirement Reference:** REQ-SEC-OCLOUD-COT-1, clause 5.1.8.7.1, SEC-CTL-OCLOUD-COT-1, SEC-CTL-OCLOUD-COT-2, clause 5.1.8.7.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The O-Cloud Platform supports a Chain of Trust (CoT) by verifying the integrity of all relevant components using a hardware root of trust (RoT) or, where hardware is unavailable, a software root of trust to ensure platform security. - -**Threat References:** T-VL-02 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_OCLOUD\_CHAIN\_OF\_TRUST\_STATIC\_SW - -**Purpose:** To confirm the presence and proper functioning of a secure boot process and integrity verification for O-Cloud static SW (Firmware and BIOS/UEFI, Bootloader, OS kernel), using hardware-based or software-based roots of trust mechanisms. - -#### Procedure and execution steps - -##### Preconditions: - -- Ensure the O-Cloud is set up with all components, including hardware, operating system, virtualization layer, and any applications or services running on the O-Cloud. -- Use tools capable of interfacing with the O-Cloud's root of trust mechanism. - -EXAMPLE 1: TPM management tools for hardware-based roots of trust, Keylime or any equivalent integrity verification system for automated integrity verification. - -- Access requirements: Tester needs administrative access to the O-Cloud platform to execute integrity verification commands and to collect integrity verification reports. - -##### Execution steps: - -Hardware RoT verification: - -Confirm the functionality of the root of trust mechanism in each O-Cloud node, whether it is hardware-based or an equivalent software-based solution. - -EXAMPLE 2: Use a Kubernetes DaemonSet to run tpm2\_pcread on all nodes, which verifies TPM presence and functionality by reading the PCR (Platform Configuration Registers) values. The DaemonSet collects outputs and send them for verification. - -Integrity check: - -Verify the integrity measurements against known good baselines. These measurements ensure the boot process and static O-Cloud SW integrity. - -EXAMPLE 3: Use a securely stored baseline to obtain the expected PCR values for a known secure state of the O-Cloud static SWs. This could involve securely storing PCR values following a clean installation or using manufacturer-provided values. - -EXAMPLE 4: Schedule Kubernetes CronJobs to use Keylime for periodic integrity verification. Keylime agents on nodes interact with the TPM to attest the integrity measurements, comparing them against known good values stored in Keylime's verifier. - -Report collection and analysis: - -Collect integrity reports and analyse them for discrepancies or signs of tampering. - -EXAMPLE 5: Use Keylime's centralized reporting and alerting features to collect and analyse attestation data. Integrate Keylime with an ELK stack deployed within the Kubernetes cluster for enhanced log analysis and visualization of attestation outcomes. - -#### Expected Results: - -- All O-Cloud nodes demonstrate the presence of RoT. -- Integrity measurements align with known good baselines. - -#### Expected Format of Evidence: - -- Logs confirming RoT presence on each node. -- Logs indicating successful integrity verification against known good baselines. - -## 18.8.2 Chain of Trust verification of dynamic O-Cloud SW - -**Requirement Name:** Support of root of trust and integrity verification of dynamic O-Cloud SW (virtualization layer and workloads) - -**Requirement Reference:** REQ-SEC-OCLOUD-COT-1, REQ-SEC-OCLOUD-COT-2, clause 5.1.8.7.1, SEC-CTL-OCLOUD-COT-2, SEC-CTL-OCLOUD-COT-3, clause 5.1.8.7.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The O-Cloud Platform supports a Chain of Trust (CoT) by verifying the integrity of all relevant components from the hardware layer to the application layer, using a hardware or software root of trust. It also supports remote attestation services to continuously monitor integrity and detect unauthorized changes. - -**Threat References:** T-VL-02 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_OCLOUD\_INTEGRITY\_VERIFICATION\_DYNAMIC\_SW - -**Purpose:** To ensure the integrity of dynamic software in the O-Cloud through continuous verification. - -#### Procedure and execution steps - -##### Preconditions: - -- Ensure the O-Cloud is set up with all components, including hardware, operating system, virtualization layer, and any applications or services running on the O-Cloud. -- Use tools capable of interfacing with the O-Cloud's root of trust mechanism. - -EXAMPLE 1: TPM management tools for hardware-based roots of trust, Keylime to automate integrity measurements and attestation of dynamic software components, integrating with IMA for capturing runtime integrity measurements. - -- Access requirements: Tester needs administrative access to the O-Cloud platform to execute integrity verification commands and to collect integrity verification reports. - -##### Execution steps: - -Dynamic software verification: - -Initiate continuous integrity verification of the dynamic O-Cloud SW, including executable binaries and configuration files used by the container engine and workloads. - -**EXAMPLE 2:** Implement an IMA policy to measure container images and runtime configurations upon execution. Configure Keylime to monitor the integrity of container runtime environments and deployed containers on Kubernetes nodes. This involves setting up Keylime agents within the cluster that automatically update integrity measurements for dynamic software components and verify them against expected values. - -Attestation: - -Perform attestation of the container engine configurations and active workloads to detect any unauthorized changes or potential integrity breaches. - -**EXAMPLE 3:** Deploy Keylime agents on each O-Cloud node to periodically attest the integrity of dynamic SW components based on IMA measurements. Use Keylime to trigger attestation procedures that verify IMA logs against expected integrity measurements for containerized applications. - -Report collection and anomaly detection: - -Collect attestation reports and analyse them for any discrepancies, unauthorized changes, or signs of tampering in the container engine and workloads. - -**EXAMPLE 4:** Use Keylime's web interface or API integrated with an ELK stack for logging and monitoring attestation results. Set up alerts for any attestation failures or integrity breaches detected in dynamic software. - -#### Expected Results: - -- Dynamic software components are measured upon execution, with their integrity measurements securely recorded. -- Integrity measurements are successfully captured and verified against known good baselines, indicating no unauthorized modifications. - -#### Expected Format of Evidence: - -- Logs attesting the integrity of dynamic software components, including any alerts generated for integrity failures. -- Reports detailing the comparison of runtime integrity measurements against known good baselines, demonstrating continuous integrity verification of dynamic O-Cloud dynamic software. - -## 18.9 Secure time synchronization for O-Cloud - -**Requirement Name:** Secure time synchronization for O-Cloud - -**Requirement Reference:** REQ-SEC-OCLOUD-TS-1, clause 5.1.8.12.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** It ensures all O-Cloud nodes exclusively connect to an authenticated time synchronization server for Time of Day (ToD) synchronization. - -**Threat Reference:** T-TS-01 - -**DUT/s:** O-Cloud - -**Test Name:** TC\_OCLOUD\_SECURE\_TIME\_SYN - -**Purpose:** To verify that all O-Cloud nodes are configured to exclusively connect to an authenticated time synchronization server for Time of Day (ToD) synchronization. - -#### Procedure and execution steps - -#### Preconditions: - -- A list of allowed secure time synchronization servers - -- Configuration of O-Cloud nodes - -**Execution steps:** - -- 1) Access the configuration of each O-Cloud node to review the time synchronization settings. -- 2) Check that each O-Cloud node is configured to only connect to one or more time synchronization servers from the list of allowed secure time synchronization servers. -- 3) Ensure that no other time synchronization servers are configured. -- 4) Confirm that the cryptographic keying material for verifying the server’s authenticity is present in the configuration. - -**Expected results:** - -Each O-Cloud node is configured to connect only to the allowed secure time synchronization server(s), and the cryptographic keying material for verifying each server’s authenticity is present in the configuration. - -**Expected format of evidence:** - -Screenshots showing the O-Cloud node configuration settings with the allowed time synchronization server(s) details. - ---- - -## 19 Security test of VNF/CNF - -### 19.1 Overview - -This clause contains security tests to validate the security protection mechanism specific to O-RAN architecture elements which are virtualized/containerized and deployed on the O-Cloud/SMO. - -### 19.2 Executive environment protection - -**Requirement Name:** secure executive environment provision - -**Requirement Reference:** REQ-SEC-LCM-SD-5, REQ-SEC-LCM-SD-6, REQ-SEC-LCM-SD-7, clause 5.3.2.3.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** It ensures all O-RAN architecture elements only consume the resources from its defined resource quotas. - -**Threat References:** T-AppLCM-04, T-AppLCM-05 - -**DUT/s:** SMO - -**Test Name:** TC\_SECURE\_EXECUTIVE\_ENV\_PROVISION - -**Purpose:** To test whether the NFO compares the VNF/CNF owned resource state with the defined resource quotas from the Application descriptor. - -To test whether the NFO sends an alarm to the SMO if the two resource states are inconsistent. - -**Procedure and execution steps****Preconditions** - -There are: VNF/CNF, O-Cloud, SMO, NFO, Application Descriptor, (or simulated O-Cloud, SMO) on the test environment. - -**Execution steps** - -- 1) The tester utilizes the O-Cloud to change the resource state of VNF/CNF (e.g. change vCPU size of the VNF/CNF). -- 2) The tester uses the NFO to query the parsed resource state from the Application descriptor. -- 3) The tester checks whether the NFO sends an alarm to the SMO when the NFO receives the parsed resource state from the Application descriptor and finds that the owned resource state and the parsed resource state are inconsistent. - -#### Expected Results - -The NFO sends an alarm to the SMO when the NFO detects an inconsistency between the parsed resource state from the Application descriptor and the owned resource state. - -#### Expected format of evidence: - -Screenshots of logs containing the alarm on the SMO. - -### 19.3 Signature validation during App image onboarding - -The security test cases defined in clause 9.5.2 apply to this clause. - -### 19.4 Void - -- - ---- - -## 20 Security tests of Common Application Lifecycle Management - -### 20.1 Overview - -This clause contains security tests to validate the security protection relevant to Common App LCM. - -### 20.2 Application package - -#### 20.2.1 Application package signature verification - -The security test cases defined in clause 9.5.2 apply to this clause. - -#### 20.2.2 Minimum Requirements - -**Requirement Name:** Application package includes minimal artifacts. - -**Requirement Reference:** REQ-SEC-ALM-PKG-3, clause 5.3.2.1.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** The application package includes the signing certificate and signature(s) of Solution Provider. - -**Threat References:** T-O-RAN-09 - -**DUT/s:** O-DU, O-CU, Near-RT RIC, xApp, rApp - -**NOTE:** This test case applies to VNF/CNF DUTs. It is not applicable to PNFs. - -**Test Name:** TC\_App\_Pkg\_Min\_Artifacts - -**Purpose:** The purpose of this test is to verify that an Application package includes minimal artifacts according to REQ-SEC-ALM-PKG-3. - -#### **Procedure and execution steps** - -##### **Preconditions** - -Application package available for access. - -##### **Execution steps:** - -- 1) Access the Application package contents. -- 2) Verify the Application package includes minimally the following artifacts: - - a) Signing certificate - - b) Solution Provider signature(s) - -##### **Expected Results:** - -Application package includes the minimal artifacts required. - -##### **Expected format of evidence:** - -Screenshots or logs providing evidence that the application package contains the signing certificate and signatures of the Solution Provider. - -## **20.2.3 App Package Change Log** - -**Requirement Name:** Application package shall have change logs. - -**Requirement Reference:** REQ-SEC-ALM-PKG-15, clause 5.3.2.1.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Application packages have a Change Log. - -**Threat References:** T-O-RAN-09 - -**DUT/s:** O-DU, O-CU, Near-RT RIC, xApp, rApp - -**Test Name:** TC\_App\_Pkg\_Change\_Log - -NOTE: This test case applies to VNF/CNF DUTs. It is not applicable to PNFs. - -**Purpose:** The purpose of this test is to verify that the Application packages contains a change log according to REQ-SEC-ALM-PKG-15. - -#### **Procedure and execution steps** - -##### **Preconditions** - -Application package available for access. - -##### **Execution steps:** - -- Access the Application package and external artifacts if present. -- Verify the Application package or external artifacts includes change log. -- Verify latest version noted in change log matches the current Application version. - -##### **Expected Results:** - -Change log is included in the Application package. - -**Expected format of evidence:** - -Screenshot or logs providing evidence of the change log is either provided in the application package or provided as an external artifact. - -## 20.3 Secure Decommissioning - -### 20.3.1 Post-Decommission Report - -**Requirement Name:** A complete post-decommission report shall be generated. - -**Requirement Reference:** REQ-SEC-ALM-DECOM-1, clause 5.3, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Generation of a decommissioning report for decommissioned applications - -**Threat References:** T-AppLCM-06 - -**DUT/s:** O-CU, Near-RT RIC, xApp, rApp - -**Test Name:** TC\_App\_Decommission\_Report - -**Purpose:** The purpose of this test is to ensure a decommissioning report is generated for a decommissioned Application. - -**Procedure and execution steps** - -**Preconditions** - -Ensure Application subject to decommissioning has no running instance(s) on O-RAN system. - -**Execution steps:** - -- 1) Execute decommissioning of Application -- 2) Generate report of decommissioning whether through manual or automated means - -**Expected Results:** - -Decommissioning report documenting Application decommissioning is generated. - -**Expected format of evidence:** - -A report detailing: - -- Decommissioned Application name and version -- Date and time of Application decommissioning -- Tasks performed during decommissioning -- Other pertinent details - -### 20.3.2 Trust Artifact Revocation - -**Requirement Name:** Trust artifacts revoked during Application decommissioning. - -**Requirement Reference:** REQ-SEC-ALM-DECOM-3, clause 5.3.2.5.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** All trust artifacts associated with an application are revoked at the time of decommissioning. - -**Threat References:** T-AppLCM-06 - -**DUT/s:** O-CU, Near-RT RIC, xApp, rApp - -**Test Name:** TC\_App\_Trust\_Artifact\_Revocation - -**Purpose:** The purpose of this test is to verify that all trust artifacts associated with an Application are revoked at the time of Application decommissioning. - -#### Procedure and execution steps - -##### Preconditions - -- Locate and prepare Application trust artifacts for revocation. -- Ensure Application subject to decommissioning has no running instance(s) on O-RAN system. - -##### Execution steps: - -- 1) Revoke trust artifacts from Application subject to decommissioning. -- 2) Perform a scan and verify that all trust artifacts associated with Application have been revoked. -EXAMPLE: If trust artifact is a certificate, verify that certificate is in certification revocation list. -- 3) Execute decommissioning of Application. -- 4) Attempt to instantiate Application and verify that it cannot be re-instantiated without the trust artifacts. - -##### Expected Results: - -All trust artifacts are removed from the Application and the decommissioned Application cannot be re-instantiated. - -##### Expected format of evidence: - -Screenshots, logs, or report providing evidence that the trust artifacts associated with a decommissioned application are revoked. - ---- - -## 21 Security test of O-CU-CP - -### 21.1 Overview - -The present clause contains 3GPP security test cases applicable to O-CU-CP and O-RAN specific O-CU-CP test cases. - -### 21.2 O-CU-CP 3GPP specific security functional requirements and test cases - -**Requirement Name:** 3GPP specific O-CU-CP security - -**Requirement Reference:** REQ-SEC-OCU-1, clause 5.1.4.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** “O-CU-CP and O-CU-UP shall meet the security requirements for gNB-CU-CP and gNB-CU-UP respectively”, as specified in TS 33.501 [25] - -**DUT/s:** O-CU-CP - -**Test Name:** TC\_O\_CU\_CP\_3GPP\_33\_523\_Cl\_5\_2\_2 (As defined in clause 5.2.2 of TS 33.523 [23]) - -**Purpose:** To verify the O-CU-CP meet the security requirements for gNB-CU-CP - -gNB-CU-CP specific security functional requirements and test cases specified in clause 5.2.2 of TS 33.523 [23] apply to O-CU-CP. - -## 21.3 O-RAN specific security functional requirements and test cases - -The TLS test cases in clause 6.3 of the present document apply to the O1 interface of O-CU-CP. - -The IPsec test cases in clause 6.4 of the present document apply to the E2 interface of O-CU-CP. - ---- - -## 22 Security test of O-CU-UP - -### 22.1 Overview - -The present clause contains 3GPP security test cases applicable to O-CU-UP and O-RAN specific O-CU-UP test cases. - -### 22.2 O-CU-UP 3GPP specific security functional requirements and test cases - -**Requirement Name:** 3GPP specific O-CU-UP security - -**Requirement Reference:** REQ-SEC-OCU-1, clause 5.1.4.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** “O-CU-CP and O-CU-UP shall meet the security requirements for gNB-CU-CP and gNB-CU-UP respectively”, as specified in TS 33.501 [25] - -**DUT/s:** O-CU-UP - -**Test Name:** TC\_O\_CU\_UP\_3GPP\_33\_523\_Cl\_6\_2\_2 (As defined in clause 6.2.2 of TS 33.523 [23]) - -**Purpose:** To verify the O-CU-CP meet the security requirements for gNB-CU-UP - -gNB-CU-UP specific security functional requirements and test cases specified in clause 6.2.2 of TS 33.523 [23] apply to O-CU-UP. - -### 22.3 O-RAN specific security functional requirements and test cases - -The TLS test cases in clause 6.3 of the present document apply to the O1 interface of O-CU-UP. - -The IPsec test cases in clause 6.4 of the present document apply to the E2 interface of O-CU-UP. - ---- - -## 23 Security test of O-DU - -### 23.1 Overview - -The present clause contains 3GPP security test cases applicable to O-DU and O-RAN specific O-DU test cases. - -## 23.2 O-DU 3GPP specific security functional requirements and test cases - -**Requirement Name:** 3GPP specific O-DU security - -**Requirement Reference:** REQ-SEC-ODU-1, clause 5.1.5.1, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** “O-DU shall meet the security requirements for gNB-DU” as specified in TS 33.501 [25]. - -**DUT/s:** O-DU - -**Test Name:** TC\_O\_DU\_3GPP\_33\_523\_Cl\_7\_2\_2 (As defined in clause 7.2.2 of TS 33.523 [23]) - -**Purpose:** To verify the O-DU meet the security requirements for gNB-DU - -gNB-DU specific security functional requirements and test cases specified in clause 7.2.2 of TS 33.523 [23] apply to O-DU. - -## 23.3 O-RAN specific security functional requirements and test cases - -The 802.1X Authenticator Validation test cases in clause 11.2.1 applies to O-DU for the network configuration where O-DU acts as an 802.1X authenticator. - -The 802.1X Supplicant Validation test cases in clause 11.2.2 apply to O-DU. - -The TLS test cases in clause 6.3 of the present document apply to the O1 interface and M-Plane of O-DU. - -The IPsec test cases in clause 6.4 of the present document apply to the E2 interface of O-DU. - -The SSH Server & Client test cases in clause 6.2 of the present document apply to the M-Plane of O-DU. - ---- - -## 24 End-to-End security test cases - -### 24.0 Overview - -This clause describes E2E tests evaluating and assessing the security aspects of an O-RAN conformant radio access network. - -The O-RU, O-DU, O-CU-CP and O-CU-UP as defined in O-RAN Architecture Description [1] is the System under Test (SUT) and can be viewed as an integrated black box in the context of the E2E security testing. - -### 24.1 3GPP Security Assurance Specification (SCAS) - -For NR technology, Table 24-1 applies. The test cases referenced in this table are from 3GPP TS 33.511 [8], which are applied to the O-RAN system. The table also indicates the applicable technology, specifying whether each test case pertains to NR NSA (Non-Standalone) and/or NR SA (Standalone). - -For LTE technology, Table 24-2 applies. The test cases referenced in this table are from 3GPP TS 33.216 [9], which are applied to the O-RAN system. - -The tables also contain the information relative to the 3GPP releases affected for each test case. - -**Table 24-1: List of SCAS Test Cases for NR and applicable technology from Clause 4.2.2 of 3GPP TS 33.511** - -| Test Case (O-RAN Ref. #) | Test Case (3GPP clause number and title) | Applicable Technology | Applicable 3GPP Releases | -|--------------------------|-----------------------------------------------------------------------------------|-----------------------------------|--------------------------| -| TC_SCAS_NR_E2E_24.1.1 | 4.2.2.1.1
Integrity protection of RRC-signalling | NR NSA (Options 3 and 4)
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.2 | 4.2.2.1.2
Integrity protection of user data | NR NSA (Options 4 and 7)
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.3 | 4.2.2.1.4
RRC integrity check failure | NR NSA
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.4 | 4.2.2.1.5
UP integrity check failure | NR NSA
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.5 | 4.2.2.1.6
Ciphering of RRC-signalling | NR NSA
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.6 | 4.2.2.1.7
Ciphering of user data | NR NSA
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.7 | 4.2.2.1.8
Replay protection of user data | NR NSA
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.8 | 4.2.2.1.9
Replay protection of RRC-signalling | NR NSA
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.9 | 4.2.2.1.10
Ciphering of user data based on the security policy sent by the SMF | NR NSA (Options 4 and 7)
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.10 | 4.2.2.1.11
Integrity of user data based on the security policy sent by the SMF | NR NSA (Options 4 and 7)
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.11 | 4.2.2.1.12
AS algorithms selection | NR NSA
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.12 | 4.2.2.1.13
Key refresh | NR NSA
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.13 | 4.2.2.1.14
Bidding down prevention in Xn-handovers | NR NSA (Options 4 and 7)
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.14 | 4.2.2.1.15
AS protection algorithm selection | NR NSA
NR SA | 16
17
18 | - -| | | | | -|------------------------|----------------------------------------------------------------------------------|-----------------------------------|----------------| -| TC_SCAS_NR_E2E_24.1.15 | 4.2.2.1.16
Control plane data confidentiality protection over N2/Xn interface | NR NSA (Options 4 and 7)
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.16 | 4.2.2.1.17
Control plane data integrity protection over S1/NG/Xn interface | NR NSA
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.17 | 4.2.2.1.18
Key update on dual connectivity | NR NSA
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.18 | 4.2.2.1.19
User plane security activation in Inactive scenario | NR NSA (Options 4 and 7)
NR SA | 16
17
18 | -| TC_SCAS_NR_E2E_24.1.19 | 4.2.2.1.20
User plane data confidentiality protection over N3/Xn interface | NR NSA (Options 4 and 7)
NR SA | 18 | -| TC_SCAS_NR_E2E_24.1.20 | 4.2.2.1.21
User plane data integrity protection over N3/Xn interface | NR NSA (Options 4 and 7)
NR SA | 18 | - -**Table 24-2: List of SCAS Test Cases for LTE and applicable technology from Clause 4.2.2 of 3GPP TS 33.216** - -| Test Case (O-RAN Ref. #) | Test Case (3GPP clause number and title) | Applicable Technology | Applicable 3GPP Releases | -|--------------------------|-----------------------------------------------------------------------|-----------------------|--------------------------| -| TC_SCAS_LTE_E2E_24.1.1 | 4.2.2.1.1
Control plane data confidentiality protection over S1/X2 | LTE | 16
17
18 | -| TC_SCAS_LTE_E2E_24.1.2 | 4.2.2.1.2
Control plane data integrity protection over S1/X2 | LTE | 16
17
18 | -| TC_SCAS_LTE_E2E_24.1.3 | 4.2.2.1.3
User plane data ciphering | LTE | 16
17
18 | -| TC_SCAS_LTE_E2E_24.1.4 | 4.2.2.1.4
User plane data integrity protection | LTE | 16
17
18 | -| TC_SCAS_LTE_E2E_24.1.5 | 4.2.2.1.5
AS algorithms selection | LTE | 16
17
18 | -| TC_SCAS_LTE_E2E_24.1.6 | 4.2.2.1.6
RRC integrity protection | LTE | 16
17
18 | -| TC_SCAS_LTE_E2E_24.1.7 | 4.2.2.1.7
Selection of EIA0 | LTE | 16
17
18 | -| TC_SCAS_LTE_E2E_24.1.8 | 4.2.2.1.8 (1)
Key refresh (PDCP Count) | LTE | 16
17
18 | -| TC_SCAS_LTE_E2E_24.1.9 | 4.2.2.1.8 (2)
Key refresh (DRB ID) | LTE | 16
17
18 | -| TC_SCAS_LTE_E2E_24.1.10 | 4.2.2.1.9
AS integrity algorithm selection | LTE | 16
17
18 | -| TC_SCAS_LTE_E2E_24.1.11 | 4.2.2.1.10
Bidding down prevention in X2-handovers | LTE | 16
17
18 | -| TC_SCAS_LTE_E2E_24.1.12 | 4.2.2.1.11
AS protection algorithm selection | LTE | 16
17
18 | -| TC_SCAS_LTE_E2E_24.1.13 | 4.2.2.1.12
RRC and UP downlink ciphering | LTE | 16
17
18 | -| TC_SCAS_LTE_E2E_24.1.14 | 4.2.2.1.13
Map a UE NR security capability | LTE | 16
17
18 | - -| | | | | -|-------------------------|---------------------------------------------------------------|-----|----------------| -| TC_SCAS_LTE_E2E_24.1.15 | 4.2.2.1.14
UE NR security capability | LTE | 16
17
18 | -| TC_SCAS_LTE_E2E_24.1.16 | 4.2.2.1.15
Bidding down prevention in X2-handovers | LTE | 16
17
18 | -| TC_SCAS_LTE_E2E_24.1.17 | 4.2.2.1.16
Integrity protection of user data | LTE | 18 | -| TC_SCAS_LTE_E2E_24.1.18 | 4.2.2.1.17
Select the right UP integrity protection policy | LTE | 18 | -| TC_SCAS_LTE_E2E_24.1.19 | 4.2.2.1.18
Select the right UP IP policy | LTE | 18 | -| TC_SCAS_LTE_E2E_24.1.20 | 4.2.2.1.19
Select the right UP IP policy in S1 handover | LTE | 18 | -| TC_SCAS_LTE_E2E_24.1.21 | 4.2.2.1.20
Bidding down prevention for UP IP Policy | LTE | 18 | - -## 24.2 DoS, fuzzing and blind exploitation test - -Due to the open and disaggregated nature of the O-RAN system (SUT), the attack surfaces associated with some of its transport protocols and interfaces are easy targets for attackers. Cyberattacks like DoS, fuzzing and blind exploitation are easy to launch, require little information about the target system, and can cause significant performance degradation or service interruption if not properly mitigated. - -The duration of test TRAFFIC GENERATION specified in this clause shall have a 3 minute minimum. - -**Table 24-3** summarizes the test cases and the applicable technology. - -**Table 24-3: End-to-end test cases and applicable technology** - -| Test case | | Applicable technology | | | -|-----------|-------------------------------------|-----------------------|-----|----| -| | | LTE | NSA | SA | -| Test ID | Name | | | | -| 24.2.1.1 | TC_E2E_ODU_SPlane_DoS | N/A | Y | Y | -| 24.2.1.2 | TC_E2E_ODU_SPlane_Robustness | N/A | Y | Y | -| 24.2.2.1 | TC_E2E_ODU_CPlane_eCPRI_DoS | N/A | Y | Y | -| 24.2.2.2 | TC_E2E_ODU_CPlane_eCPRI_Robustness | N/A | Y | Y | -| 24.2.2.3 | TC_E2E_ORU_CPlane_eCPRI_DoS | N/A | Y | Y | -| 24.2.2.4 | TC_E2E_ORU_CPlane_eCPRI_Robustness | N/A | Y | Y | -| 24.2.3.1 | TC_E2E_NearRTRIC_A1_DoS | N/A | Y | Y | -| 24.2.3.2 | TC_E2E_NearRTRIC_A1_Robustness | N/A | Y | Y | -| 24.2.3.3 | TC_E2E_NearRTRIC_A1_Vulnerabilities | N/A | Y | Y | -| 24.2.4.1 | TC_E2E_OCloud_SideChannel_DoS | N/A | Y | Y | - -## 24.2.1 S-Plane - -### 24.2.1.1 S-Plane PTP DoS Attack - -**Requirement Name:** O-DU S-Plane DoS Attack - -**Requirement Reference:** REQ-SEC-DOS-1, clause 5.3.5.1, O-RAN Security Requirements and Control Specification [5] - -**Requirement Description:** An O-RAN architecture element with a network interface withstands network transport protocol based volumetric DDoS attack without system crash and returning to service level after the attack. - -**Threat References:** T-O-RAN-09 - -**SUT/s:** O-RAN system - -**Test Name:** TC\_E2E\_ODU\_SPlane\_DoS - -**Purpose:** To verify that a predefined volumetric DoS attack against O-DU via the Open FH S-Plane will not crash the SUT and that after the attack ends, the SUT will return to the pre-attack service level. - -#### Procedure and execution steps - -##### Preconditions - -- The test emulator has the MAC address of the O-DU's Open FH interface and the L2 connectivity to the O-DU -- Normal UE procedures are in place and the SUT correctly handles user plane traffic. - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -Figure 24-1 shows test setup and configuration. - -![Figure 24-1: S-Plane O-DU Test setup. The diagram shows an E2E O-RAN System. On the left, there are 'UE or Emulated UE' blocks. In the center, an 'O-RU' (Radio Unit) is connected to an 'O-DU' (Distributed Unit) via an 'Open Fronthaul' interface. The 'O-DU' is part of an 'O-Cloud' which also contains an 'O-CU' (Central Unit) and an 'NRT-ric'. Above the O-Cloud is an 'SMO' (Service Management and Orchestration). On the right, the 'O-CU' is connected to a '5GC or Emulated 5GC' (5G Core). A red dashed line labeled 'S-Plane DoS attack' originates from a hacker icon (a person in a hat) and points to the 'O-DU'.](35d5c5a5774a7997f06756915721031b_img.jpg) - -Figure 24-1: S-Plane O-DU Test setup. The diagram shows an E2E O-RAN System. On the left, there are 'UE or Emulated UE' blocks. In the center, an 'O-RU' (Radio Unit) is connected to an 'O-DU' (Distributed Unit) via an 'Open Fronthaul' interface. The 'O-DU' is part of an 'O-Cloud' which also contains an 'O-CU' (Central Unit) and an 'NRT-ric'. Above the O-Cloud is an 'SMO' (Service Management and Orchestration). On the right, the 'O-CU' is connected to a '5GC or Emulated 5GC' (5G Core). A red dashed line labeled 'S-Plane DoS attack' originates from a hacker icon (a person in a hat) and points to the 'O-DU'. - -**Figure 24-1: S-Plane O-DU Test setup** - -### Execution steps - -The tester uses a test tool to generate different types of volumetric DoS Open FH S-Plane attacks against the O-DU. - -- 1) Perform test at volumetric tiers of 10Mbps, 100Mbps, 1Gbps. -- 2) Send DoS traffic streams to the O-DU over the Open FH S-Plane that are a random mix of generic Ethernet frames and PTP announce/sync messages with random MAC source addresses and the MAC address of the T-GM/T-BC or T-TC known to the O-DU. - -### Expected results - -- During the test, the SUT maintains an operational level. -- After the execution of the test, the degradation of service availability and performance of the SUT is not noticeable. - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -**Expected format of evidence:** Traffic captures and/or report files - -### 24.2.1.2 S-Plane PTP Unexpected Input - -**Requirement Name:** O-DU S-Plane Robustness - -**Requirement Reference:** REQ-SEC-OFSP-4, clause 5.2.5.3.2, O-RAN Security Requirements and Control Specification [5] - -**Requirement Description:** The O-DU can detect and defend against application level attacks across the Open FH S-Plane interface, due to misbehaviour or malicious intent. - -**Threat References:** T-O-RAN-09 - -**SUT/s:** O-RAN system - -**Test Name:** TC\_E2E\_ODU\_SPlane\_Robustness - -**Purpose:** To verify that an input not conforming to the Open FH S-Plane specification sent to the O-DU will not compromise the security of the SUT. - -**Procedure and execution steps** - -**Preconditions** - -- The test emulator has the MAC address of the O-DU’s Open FH interface and L2 connectivity to the O-DU. -- Normal UE procedures are in place and the SUT correctly handles user plane traffic. - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -Figure 24-2 shows the test setup and configuration. - -![Diagram of S-Plane PTP Unexpected Input Test Setup. It shows an 'E2E O-RAN System' box containing two 'O-RU' units connected via 'Open Fronthaul' to an 'O-DU'. The 'O-DU' is part of an 'O-Cloud' which also contains 'NRT-RIC' and 'O-CU' units. The 'O-Cloud' is connected to an 'SMO' and a '5GC or Emulated 5GC'. To the left, 'UE or Emulated UE' blocks are shown. A red dashed line labeled 'S-Plane Unexpected Input' originates from a hacker icon and points to the 'O-DU'.](4f407c97df6e5ee98fdb248ada82de59_img.jpg) - -Diagram of S-Plane PTP Unexpected Input Test Setup. It shows an 'E2E O-RAN System' box containing two 'O-RU' units connected via 'Open Fronthaul' to an 'O-DU'. The 'O-DU' is part of an 'O-Cloud' which also contains 'NRT-RIC' and 'O-CU' units. The 'O-Cloud' is connected to an 'SMO' and a '5GC or Emulated 5GC'. To the left, 'UE or Emulated UE' blocks are shown. A red dashed line labeled 'S-Plane Unexpected Input' originates from a hacker icon and points to the 'O-DU'. - -**Figure 24-2: S-Plane PTP Unexpected Input Test Setup** - -**Execution steps** - -- 1) The tester uses a packet capture tool to capture sample of legitimate PTP messages sent to the O-DU over Open FH S-Plane. -- 2) The tester uses a fuzzing tool to replay each captured PTP message while mutating its content and keeping the original source/destination MAC address. -- 3) The tester sends at least 250,000 iterations of mutated PTP message based on a random seed - -**Expected results** - -During the execution of the test, the degradation of service availability and performance of the SUT is not noticeable. - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -**Expected format of evidence:** Log files, traffic captures and/or reports - -## 24.2.2 C-Plane - -### 24.2.2.1 C-Plane eCPRI DoS Attack - -**Requirement Name:** O-DU C-Plane eCPRI DoS Attack - -**Requirement Reference:** REQ-SEC-DOS-1, clause 5.3.5.1, O-RAN Security Requirements and Control Specification [5] - -**Requirement Description:** An O-RAN architecture element with a network interface withstands network transport protocol based volumetric DDoS attack without system crash and returning to service level after the attack. - -**Threat References:** T-CPLANE-O2, T-O-RAN-09 - -**SUT/s:** O-RAN system - -**Test Name:** TC\_E2E\_ODU\_CPlane\_eCPRI\_DoS - -**Purpose:** To verify that a predefined volumetric DoS attack against the O-DU over Open FH C-Plane will not crash the SUT and that after the attack ends, the SUT will return to the pre-attack service level. - -**Procedure and execution steps** - -**Preconditions** - -- The test emulator has the MAC address of the O-DU’s Open FH interface and L2 connectivity to the O-DU. -- Normal UE procedures are in place and the SUT correctly handles user plane traffic. - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -Figure 24-3 shows the test setup and configuration. - -![Diagram of C-Plane eCPRI DoS Attack Test Setup. It shows a stack of 'UE or Emulated UE' on the left connected via 'Open Fronthaul' to an 'O-RU'. The 'O-RU' is connected to an 'O-DU' inside an 'E2E O-RAN System' box. A red dashed line labeled 'C-Plane DoS attack' with a hacker icon points to the 'O-DU'. The 'O-DU' is connected to an 'O-CU' and 'NRT-RIC' inside an 'O-Cloud' box. The 'O-CU' is connected to an 'SMO' box above it and a '5GC or Emulated 5GC' box on the right.](102806f6dea2a9f7e01d371d74f8195f_img.jpg) - -Diagram of C-Plane eCPRI DoS Attack Test Setup. It shows a stack of 'UE or Emulated UE' on the left connected via 'Open Fronthaul' to an 'O-RU'. The 'O-RU' is connected to an 'O-DU' inside an 'E2E O-RAN System' box. A red dashed line labeled 'C-Plane DoS attack' with a hacker icon points to the 'O-DU'. The 'O-DU' is connected to an 'O-CU' and 'NRT-RIC' inside an 'O-Cloud' box. The 'O-CU' is connected to an 'SMO' box above it and a '5GC or Emulated 5GC' box on the right. - -**Figure 24-3: C-Plane eCPRI DoS Attack Test Setup** - -**Execution steps** - -Use test tool to generate several types of volumetric DoS Open FH C-Plane attacks against the O-DU. - -- 1) Perform test at volumetric tiers of 10Mbps, 100Mbps, 1Gbps -- 2) Send DoS traffic to the O-DU over the Open FH S-Plane that is a random mix of eCPRI real-time Open FH C-Plane messages from arbitrary MAC addresses and the MAC address of a T-GM/T\_BC or T-TC known to the O-DU of the following types (i) LAA LBT status and response messages, (ii) Ack/Nack messages, and (iii) Wake-up Ready indication messages. Refer to Figure 4.2-1 Lower layer fronthaul data flows in [26]. - -**Expected results** - -- During the test, the SUT maintains an operational level. - -- After the execution of the test, the degradation of service availability and performance of the SUT is not noticeable. - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -**Expected format of evidence:** Traffic captures and/or report files - -### 24.2.2.2 C-Plane eCPRI Unexpected Input - -**Requirement Name:** O-DU C-Plane Robustness - -**Requirement Reference:** REQ-SEC-OFCP-2, clause 5.2.5.1.2, O-RAN Security Requirements and Control Specification [5] - -**Requirement Description:** The O-DU can detect and defend against application level attacks across the Open FH C-Plane messages with O-RUs, due to misbehaviour or malicious intent. - -**Threat References:** T-O-RAN-09 - -**SUT/s:** O-RAN system - -**Test Name:** TC\_E2E\_ODU\_CPlane\_eCPRI\_Robustness - -**Purpose:** To verify that input not conforming to the Open FH C-Plane specification will not compromise the security of the SUT. - -#### Procedure and execution steps - -##### Preconditions - -- The test emulator has the MAC address of the O-DU's Open FH interface and L2 connectivity to the O-DU. -- Normal UE procedures are in place and the SUT correctly handles user plane traffic. - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -Figure 24-4 shows the test setup and configuration. - -![Diagram of the C-Plane eCPRI Unexpected Input Test Setup. It shows an 'E2E O-RAN System' box containing two 'O-RU' units connected via 'Open Fronthaul' to an 'O-DU'. The 'O-DU' is part of an 'O-Cloud' which also contains 'NRT-RIC' and 'O-CU'. Above the 'O-DU' is an 'SMO'. To the left, multiple 'UE or Emulated UE' units are shown. To the right, a '5GC or Emulated 5GC' is connected. A red dashed arrow labeled 'C-Plane Unexpected Input' originates from a hacker icon and points to the 'O-DU'.](4d37e5b3681dcb0b4940ddd7ab5969ed_img.jpg) - -Diagram of the C-Plane eCPRI Unexpected Input Test Setup. It shows an 'E2E O-RAN System' box containing two 'O-RU' units connected via 'Open Fronthaul' to an 'O-DU'. The 'O-DU' is part of an 'O-Cloud' which also contains 'NRT-RIC' and 'O-CU'. Above the 'O-DU' is an 'SMO'. To the left, multiple 'UE or Emulated UE' units are shown. To the right, a '5GC or Emulated 5GC' is connected. A red dashed arrow labeled 'C-Plane Unexpected Input' originates from a hacker icon and points to the 'O-DU'. - -**Figure 24-4: C-Plane eCPRI Unexpected Input Test Setup** - -#### Execution steps - -- 1) The tester uses a packet capture tool to capture a sample of legitimate eCPRI messages sent over the Open FH C-Plane to the O-DU. -- 2) The tester uses a fuzzing tool to replay each captured eCPRI message while mutating its content (message type and/or payload) and keeping original source/destination MAC address. -- 3) The tester sends at least 250,000 iterations of mutated eCPRI message based on a random seed - -### Expected results - -During the execution of the test, the degradation of service availability and performance of the SUT is not noticeable. - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -**Expected format of evidence:** Traffic captures and/or report files - -### 24.2.2.3 C-Plane eCPRI DoS Attack on O-RU - -**Requirement Name:** O-RU C-Plane eCPRI DoS Attack - -**Requirement Reference:** REQ-SEC-DOS-1, clause 5.3.5.1, O-RAN Security Requirements and Control Specification [5] - -**Requirement Description:** An O-RAN architecture element with a network interface withstands network transport protocol based volumetric DDoS attack without system crash and return to service level after the attack. - -**Threat References:** T-O-RAN-09 - -**SUT/s:** O-RAN system - -**Test Name:** TC\_E2E\_ORU\_CPlane\_eCPRI\_DoS - -### Procedure and execution steps - -**Purpose:** To verify that a predefined volumetric DoS attack against O-RU over the Open FH C-Plane will not crash the SUT and that after the attack ends, the SUT will return to the pre-attack service level. - -### Preconditions - -- The test emulator has the MAC address of the O-RU's Open FH interface and L2 connectivity to the O-RU. -- Normal UE procedures are in place and the SUT correctly handles user plane traffic. - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -Figure 24-5 shows the test setup and configuration. - -![Diagram of C-Plane eCPRI DoS Attack on O-RU Test Setup. It shows an E2E O-RAN System containing an SMO, NRT-RIC, O-DU, and O-CU. Two O-RUs are connected to the O-DU via Open Fronthaul. A red dashed line labeled 'C-Plane DoS attack on O-RU' originates from a hacker icon and points to one of the O-RUs. On the left, 'UE or Emulated UE' blocks are shown. On the right, a '5GC or Emulated 5GC' block is connected to the O-CU.](64ca20a7357e612f7c65bbe816032c8a_img.jpg) - -Diagram of C-Plane eCPRI DoS Attack on O-RU Test Setup. It shows an E2E O-RAN System containing an SMO, NRT-RIC, O-DU, and O-CU. Two O-RUs are connected to the O-DU via Open Fronthaul. A red dashed line labeled 'C-Plane DoS attack on O-RU' originates from a hacker icon and points to one of the O-RUs. On the left, 'UE or Emulated UE' blocks are shown. On the right, a '5GC or Emulated 5GC' block is connected to the O-CU. - -Figure 24-5: C-Plane eCPRI DoS Attack on O-RU Test Setup - -### Execution steps - -The tester uses a test tool to generate different types of volumetric DoS Open FH C-Plane attacks against the O-RU. - -- 1) Perform test at volumetric tiers of 10Mbps, 100Mbps, 1Gbps. -- 2) Send DoS traffic stream to the O-RU over the Open FH C-Plane that is a random mix of Open FH C-Plane Scheduling commands (DL & UL), Beamforming commands, LAA LBT configuration commands/requests, and UE Channel information. - -### Expected results - -- During the test, the SUT maintains an operational level -- After the execution of the test, the degradation of service availability and performance of the SUT is not noticeable. - -**Expected format of evidence:** Traffic captures and/or report files - -## 24.2.2.4 C-Plane eCPRI Unexpected Input on O-RU - -**Requirement Name:** O-RU C-Plane Robustness - -**Requirement Reference:** REQ-SEC-OFCP-2, clause 5.2.5.1.2, O-RAN Security Requirements and Control Specification [5] - -**Requirement Description:** The O-RU can detect and defend against application level attacks across the Open FH C-Plane messages with O-DUs, due to misbehaviour or malicious intent. - -**Threat References:** T-O-RAN-09 - -**SUT/s:** O-RAN system - -**Test Name:** TC\_E2E\_ORU\_CPlane\_eCPRI\_Robustness - -**Purpose:** To verify that input not conforming to the Open FH C-Plane specification will not compromise the security of the SUT. - -### Procedure and execution steps - -#### Preconditions - -- The test emulator has the MAC address of the O-RU's Open FH interface and L2 connectivity to the O-DU. - -- Normal UE procedures are in place and the SUT correctly handles user plane traffic. - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -Figure 24-6 shows the test setup and configuration. - -![Figure 24-6: C-Plane eCPRI Unexpected Input on O-RU Test Setup. The diagram shows an E2E O-RAN System. On the left, there are multiple 'UE or Emulated UE' blocks. These are connected via 'Open Fronthaul' links to two 'O-RU' (Radio Unit) blocks. The O-RUs are connected to an 'O-DU' (Distributed Unit) block, which is part of an 'O-Cloud'. The O-DU is connected to an 'O-CU' (Central Unit) block, which is also part of the O-Cloud. The O-CU is connected to an 'NRT-RIC' (Near-Real Time RIC) block, which is connected to an 'SMO' (Service Management and Orchestration) block. A red dashed line with a hat icon represents a 'C-Plane Unexpected Input at O-RU' being sent to the O-RUs. On the right, a '5GC or Emulated 5GC' block is connected to the O-CU.](b303fb8b2c64e30aac9c32b5753d3670_img.jpg) - -Figure 24-6: C-Plane eCPRI Unexpected Input on O-RU Test Setup. The diagram shows an E2E O-RAN System. On the left, there are multiple 'UE or Emulated UE' blocks. These are connected via 'Open Fronthaul' links to two 'O-RU' (Radio Unit) blocks. The O-RUs are connected to an 'O-DU' (Distributed Unit) block, which is part of an 'O-Cloud'. The O-DU is connected to an 'O-CU' (Central Unit) block, which is also part of the O-Cloud. The O-CU is connected to an 'NRT-RIC' (Near-Real Time RIC) block, which is connected to an 'SMO' (Service Management and Orchestration) block. A red dashed line with a hat icon represents a 'C-Plane Unexpected Input at O-RU' being sent to the O-RUs. On the right, a '5GC or Emulated 5GC' block is connected to the O-CU. - -Figure 24-6: C-Plane eCPRI Unexpected Input on O-RU Test Setup - -**Execution steps** - -- 1) The tester uses a packet capture tool to capture a sample of legitimate eCPRI messages sent over the Open FH C-Plane to the O-RU. -- 2) The tester uses a fuzzing tool to replay each captured eCPRI message while mutating its content (message type and/or payload) and keeping original source/destination MAC address. -- 3) The tester sends at least 250,000 iterations of mutated eCPRI message based on a random seed. - -**Expected results** - -- After the execution of the test, the degradation of service availability and performance of the SUT is not noticeable. - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -**Expected format of evidence:** Traffic captures and/or report files - -## 24.2.3 A1 interface - -### 24.2.3.1 Near-RT RIC A1 Interface DoS Attack - -**Requirement Name:** Near-RT RIC A1 interface DoS recover - -**Requirement Reference:** REQ-SEC-NEAR-RT-6, clause 5.1.3.1, O-RAN Security Requirements and Control Specification [5] - -**Requirement Description:** The Near-RT RIC recovers, without catastrophic failure, from a volumetric DDoS attack across the A1 interface, due to misbehaviour or malicious intent. - -**Threat References:** T-O-RAN-09 - -SUT/s: O-RAN system - -Test Name: TC\_E2E\_NearRTRIC\_A1\_DoS - -**Purpose:** To verify that a predefined volumetric DoS attack against the Near-RT RIC over the A1 interface will not crash the SUT and that after the attack ends, the SUT will return to the pre-attack service level. - -### Procedure and execution steps - -#### Preconditions - -- The test emulator has the IP address information of the Near-RT RIC's A1 interface and a routable path to the target. -- Normal UE procedures are in place and the SUT correctly handles user plane traffic. - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -Figure 24-7 shows the test setup and configuration. - -![Diagram of Near-RT RIC A1 Interface DoS Attack Test Setup. The diagram shows an E2E O-RAN System containing O-RUs, an Open Fronthaul switch, an O-Cloud (with O-DU and O-CU), an NRT- RIC, and an SMO. A tester (represented by a red hat icon) is shown sending an 'A1 interface DoS attack' (indicated by a red dashed line) to the NRT- RIC. The O-RUs are connected to the Open Fronthaul switch, which is connected to the O-Cloud. The O-Cloud is connected to the NRT- RIC, which is connected to the SMO. The NRT- RIC is also connected to a 5GC or Emulated 5GC. On the left, there are multiple 'UE or Emulated UE' blocks.](93b6985cb029eb10703d0a59c2ae0c94_img.jpg) - -Diagram of Near-RT RIC A1 Interface DoS Attack Test Setup. The diagram shows an E2E O-RAN System containing O-RUs, an Open Fronthaul switch, an O-Cloud (with O-DU and O-CU), an NRT- RIC, and an SMO. A tester (represented by a red hat icon) is shown sending an 'A1 interface DoS attack' (indicated by a red dashed line) to the NRT- RIC. The O-RUs are connected to the Open Fronthaul switch, which is connected to the O-Cloud. The O-Cloud is connected to the NRT- RIC, which is connected to the SMO. The NRT- RIC is also connected to a 5GC or Emulated 5GC. On the left, there are multiple 'UE or Emulated UE' blocks. - -Figure 24-7: Near-RT RIC A1 Interface DoS Attack Test Setup - -#### Execution steps - -- 1) The tester uses a test tool to generate several types of volumetric DoS attack against the IP address of the Near-RT RIC A1 interface; -- 2) Perform test at volumetric tiers of 10Mbps, 100Mbps, 1Gbps -- 3) Send DoS traffic to the Near-RT RIC over the A1 interface that is a random mix of generic UDP packets and HTTP/HTTPS REST API calls with source addresses of Non-RT RIC, other IPs and broadcast IPs. - -#### Expected results - -- During the test, the SUT maintains an operational level. -- After the execution of the test, the degradation of service availability and performance of the SUT is not noticeable. - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -**Expected format of evidence:** Traffic captures and/or report files - -### 24.2.3.2 Near-RT RIC A1 Interface Unexpected Input - -**Requirement Name:** Near-RT RIC A1 Robustness - -**Requirement Reference:** REQ-SEC-NEAR-RT-7, clause 5.1.3.1, O-RAN Security Requirements and Control Specification [5] - -**Requirement Description:** The Near-RT RIC detects and defends against content-related attacks across the A1 interface, due to misbehaviour or malicious intent. - -**Threat References:** T-O-RAN-09 - -**SUT/s:** O-RAN system - -**Test Name:** TC\_E2E\_NearRTRIC\_A1\_Robustness - -**Purpose:** To verify that input not conforming to the A1 interface specification will not compromise the security of the SUT. - -#### Procedure and execution steps - -##### Preconditions - -- The test emulator has the IP address information of the Near-RT RIC's A1 interface and a routable path to the target. -- Normal UE procedures are in place and the SUT correctly handles user plane traffic. - -**RECOMMENDATION:** Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -Figure 24-8 shows the test setup and configuration. - -![Diagram of the test setup for Near-RT RIC A1 Interface Unexpected Input. It shows an E2E O-RAN System containing an SMO, NRT-RIC, O-DU, and O-CU. The NRT-RIC is connected to the O-DU and O-CU via the Open Fronthaul. The O-DU is connected to two O-RUs, which are connected to UE or Emulated UE. A red dashed line labeled 'A1 interface Unexpected Input' originates from a red devil face icon and points to the NRT-RIC. The NRT-RIC is also connected to a 5GC or Emulated 5GC.](22be8ddff39ab7239459476e6cb8d6e0_img.jpg) - -Diagram of the test setup for Near-RT RIC A1 Interface Unexpected Input. It shows an E2E O-RAN System containing an SMO, NRT-RIC, O-DU, and O-CU. The NRT-RIC is connected to the O-DU and O-CU via the Open Fronthaul. The O-DU is connected to two O-RUs, which are connected to UE or Emulated UE. A red dashed line labeled 'A1 interface Unexpected Input' originates from a red devil face icon and points to the NRT-RIC. The NRT-RIC is also connected to a 5GC or Emulated 5GC. - -**Figure 24-8: Near-RT RIC A1 Interface Unexpected Input Test Setup** - -##### Execution steps - -- 1) The tester uses a packet capture tool to capture samples of legitimate HTTP/HTTPS REST API messages sent over the A1 interface to the Near-RT RIC. - -- 2) The tester uses a fuzzing tool to replay each captured HTTP/HTTPS REST API message while mutating its content and keeping original source/destination IP/port. -- 3) The tester sends at least 250,000 iterations of mutated HTTP/HTTPS REST API message based on a random seed - -#### Expected results - -During the execution of the test, the degradation of service availability and performance of the SUT is not noticeable. - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -**Expected format of evidence:** Traffic captures and/or report files - -### 24.2.3.3 Near-RT RIC A1 Vulnerability Assessment - -**Requirement Name:** Near-RT RIC A1 Vulnerability Assessment - -**Requirement Reference:** REQ-SEC-SYS-1, clause 5.3.6, O-RAN Security Requirements and Control Specification [5] - -**Requirement Description:** Known vulnerabilities in the OS and applications of an O-RAN architecture element clearly identified. - -**Threat References:** T-OPENSRC-01, T-OPENSRC-02 - -**SUT/s:** O-RAN system - -**Test Name:** TC\_E2E\_NearRTRIC\_A1\_Vulnerabilities - -**Purpose:** To verify that exploitation attempts of known vulnerabilities in the Near-RT RIC will not compromise the security of the SUT. - -#### Procedure and execution steps - -##### Preconditions - -- The test emulator has the IP address information of the Near-RT RIC's A1 interface and a routable path to the target. -- Normal UE procedures are in place and the SUT correctly handles user plane traffic. -- The test requires the vulnerability scanning tool to have an up-to-date database of well-known vulnerabilities (signatures/plugins) based on Common Vulnerabilities and Exposures (CVE). - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -Figure 24-9 shows the test setup and configuration. - -![Figure 24-9: Near-RT RIC A1 Vulnerability Assessment Test Setup. The diagram shows an E2E O-RAN System. On the left, multiple 'UE or Emulated UE' units are connected to two 'O-RU' (Radio Units). These O-RUs are connected via an 'Open Fronthaul' to an 'O-Cloud'. The O-Cloud contains 'O-DU' (Distributed Unit), 'O-CU' (Central Unit), and 'NRT-RIC' (Near-Real Time RIC). The NRT-RIC is connected to an 'SMO' (Service Management and Orchestration). A red dashed line with an arrow labeled 'Exploitation over A1 interface' points from a hacker icon to the NRT-RIC. The O-Cloud is also connected to a '5GC or Emulated 5GC' (5G Core or Emulated 5G Core).](58998c9d67656e95221338204f251872_img.jpg) - -Figure 24-9: Near-RT RIC A1 Vulnerability Assessment Test Setup. The diagram shows an E2E O-RAN System. On the left, multiple 'UE or Emulated UE' units are connected to two 'O-RU' (Radio Units). These O-RUs are connected via an 'Open Fronthaul' to an 'O-Cloud'. The O-Cloud contains 'O-DU' (Distributed Unit), 'O-CU' (Central Unit), and 'NRT-RIC' (Near-Real Time RIC). The NRT-RIC is connected to an 'SMO' (Service Management and Orchestration). A red dashed line with an arrow labeled 'Exploitation over A1 interface' points from a hacker icon to the NRT-RIC. The O-Cloud is also connected to a '5GC or Emulated 5GC' (5G Core or Emulated 5G Core). - -**Figure 24-9: Near-RT RIC A1 Vulnerability Assessment Test Setup** - -### Execution steps - -The tester uses a vulnerability scanning tool to scan the IP address of the Near-RT RIC A1 interface with the following parameters defined. - -- TCP Ports: Port scanner scans all TCP ports in range 0-65535 on the IP interface of SUT. TCP SYN/ACK response by SUT is interpreted as open port. -- UDP Ports: All UDP ports documented in vendor-provided list. Other UDP ports may be considered as open for the purpose of service detection. -- Safe Checks: Disabled (to make sure that exploitation attempts of the vulnerabilities will be performed) - -**NOTE:** Due to the nature of UDP protocol, there is no simple method of open port detection similar to TCP/SCTP methods based on analysis of response message type (TCP: SYN/ACK, SCTP: INIT-ACK). In case of UDP, open port detection relies on service detection which is discussed in step 2 of this test procedure. In practice, port scans of entire UDP port range 0-65535 are impractical and time consuming. Thus, service detection is generally performed only for subset of UDP ports. UDP port subset selection is arbitrary and not standardized. Service detection in this test procedure is required for UDP ports from vendor-provided list and is optional for other UDP ports. - -### Expected results - -During the execution of the test, the degradation of service availability and performance of the SUT is not noticeable. - -**RECOMMENDATION:** Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -**Expected format of evidence:** Tool testing report and traffic captures - -## 24.2.4 O-Cloud - -### 24.2.4.1 O-Cloud side-channel DoS attack - -**Requirement Name:** O-Cloud DoS Attack - -**Requirement Reference:** REQ-SEC-DOS-1, clause 5.3.5.1, O-RAN Security Requirements and Control Specification [5] - -**Requirement Description:** An O-RAN architecture element with a network interface withstands network transport protocol based volumetric DDoS attack without system crash and returning to service level after the attack. - -**Threat References:** T-O-RAN-09 - -**SUT/s:** O-RAN system - -**Test Name:** TC\_E2E\_OCloud\_SideChannel\_DoS - -**Purpose:** To verify that a noisy neighbour DoS attack against O-Cloud for resource starvation will not crash the SUT and that after the attack ends, the SUT will return to the pre-attack service level. - -**Procedure and execution steps** - -**Preconditions** - -- The test emulator has access to the O-Cloud platform hosting the network slice(s) of the O-RAN system. -- Normal UE procedures are in place and the SUT correctly handles user plane traffic. -- Logging and alerts in the O-cloud are enabled. Network monitoring tools may be used. - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -Figure 24-10 shows the test setup and configuration. - -![Diagram of O-Cloud side-channel DoS attack test setup. It shows an E2E O-RAN System containing O-RU, Open Fronthaul, O-Cloud (with O-DU, O-CU, NRT-RIC), and SMO. On the left, multiple UE or Emulated UE units are connected to the O-RU. On the right, the O-Cloud is connected to a 5GC or Emulated 5GC. A red dashed line with a hooded figure icon points to the O-Cloud, labeled 'O-Cloud Side-channel DoS attack'.](09db9fad28b18ea44e6d78b672cd12ff_img.jpg) - -Diagram of O-Cloud side-channel DoS attack test setup. It shows an E2E O-RAN System containing O-RU, Open Fronthaul, O-Cloud (with O-DU, O-CU, NRT-RIC), and SMO. On the left, multiple UE or Emulated UE units are connected to the O-RU. On the right, the O-Cloud is connected to a 5GC or Emulated 5GC. A red dashed line with a hooded figure icon points to the O-Cloud, labeled 'O-Cloud Side-channel DoS attack'. - -**Figure 24-10: O-Cloud side-channel DoS attack Test Setup** - -Noisy neighbour VNF(s) can be deployed into an existing slice or a new slice of the shared resources with the existing slice under test. - -**Execution steps** - -- 1) The tester uses a test tool through O-Cloud MANO to instantiate noisy neighbour VNFs. - - Noisy neighbour tenant: existing slice or a new slice of the shared resources with the existing slice. - - The Noisy Neighbour tenants utilize shared resources that include CPU, memory, storage, and network. The Noisy Neighbour tenants exhaust all the remaining shared resources. The duration of the test is at least 3 minutes or long enough to cover the benchmarking tests. -- 2) Run the benchmark test again with the noisy neighbours. - -- 3) Check the logs and alerts that are associated with the test. - -#### Expected results - -- After the execution of the test, the degradation of service availability and performance of the SUT is not noticeable. -- The Noisy Neighbour attack is properly logged and alerted by the O-Cloud. - -RECOMMENDATION: Use Bidirectional throughput in different radio conditions and Data Services tests (clauses 6.0 and 7.1 from ORAN TIFG End-to-End Test Specifications [4]) as benchmarks for indicating the correct behaviour of the SUT. - -**Expected format of evidence:** Logs, results, screenshots, report - ---- - -## 25 Security test of Shared O-RU - -### 25.1 Overview - -This clause contains security tests to validate security controls related to the Shared O-RU and the Shared O-RU architecture. - -### 25.2 Shared O-RU test cases - -#### 25.2.1 mTLS for mutual authentication - -**Requirement Name:** Shared O-RU support for mTLS 1.2, or higher, for mutual authentication on the Open FH M-Plane interface with an O-RU Controller - -**Requirement Reference:** SEC-CTL-SharedORU-1, clause 5.1.9.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** mTLS support on Shared O-RU - -**Threat References:** T-SharedORU-06 - -**DUT/s:** Shared O-RU - -**Test Name:** TC\_SharedORU\_mTLS - -**Purpose:** To verify the Shared O-RU is able to mutually authenticate with an O-RU Controller using mTLS, with PKI-based X.509 certificates. - -#### Procedure and execution steps - -##### Preconditions - -DUT is the Shared O-RU with mTLS 1.2, or 1.3, support enabled. - -##### Execution steps - -Follow the test case in clause 6.3 of the present document. - -##### Expected results - -The DUT supports mutual authentication with an O-RU Controller using mTLS. - -**Expected format of evidence:** Log entries and packet captures. - -## 25.2.2 NACM Authorization - -**Requirement Name:** Shared O-RU support for NACM for permitting or denying access to an SRO - -**Requirement Reference:** SEC-CTL-SharedORU-3, clause 5.1.9.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** NACM support for Shared O-RU - -**Threat References:** T-SharedORU-22, T-SharedORU-23 - -**DUT/s:** Shared O-RU - -**Test Name:** TC\_SharedORU\_NACM\_Authorization - -**Purpose:** To verify the Shared O-RU is able to enforce role-based least privilege access control on the Open Fronthaul by using NACM [14]. - -### Procedure and execution steps - -#### Preconditions - -DUT is the Shared O-RU with: - -- IP enabled Open Fronthaul M-Plane interface, reachable from the authentication server -- Valid certificate loaded for the server and necessary certificate authorities (CAs) -- Client's root CA required to validate NETCONF client certificate -- Valid TLS Client-to-NETCONF username mapping - -#### Execution steps - -First set up a host/device with TLS client software installed, valid client certificates, keys, root CA certificate for the server (Shared O-RU), and all intermediate CA certificates required to validate the client certificate. - -The following test steps are validated: - -- 1) Start the NETCONF-over-TLS session using OpenSSL s\_client command to connect with DUT using TLS 1.2 or TLS 1.3 -- 2) Verify the session is established and mapped to the correct NETCONF user -- 3) Verify the global NACM enforcement control setting of - - enable-nacm = true - - read-default = permit - - write-default = deny - - exec-default = deny - - enable-external-groups = true -- 4) Verify the NACM rule sets for the pre-defined groups -- 5) Close the NETCONF session and TLS connection - -Upon availability of the NETCONF operations set(s) definition per NACM group, the NACM rule set(s) enforcement by the DUT is validated for each of those pre-defined groups listed above. - -#### Expected results - -The DUT supports NETCONF over TLS session over its Open Fronthaul M-Plane interface and NACM enforcement control settings. - -**Expected format of evidence:** Log entries and packet captures. - -## 25.2.3 TLS across Open Fronthaul - -**Requirement Name:** Shared O-RU support for TLS 1.2, or higher, on the Open FH M-Plane interface with an O-RU controller - -**Requirement Reference:** SEC-CTL-SharedORU-4, clause 5.1.9.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** TLS on Shared O-RU - -**Threat References:** T-SharedORU-27, T-SharedORU-28 - -**DUT/s:** Shared O-RU - -**Test Name:** TC\_SharedORU\_TLS - -**Purpose:** To verify whether Shared O-RU establishes a TLS session with an O-RU Controller and provides confidentiality and integrity protection for messages exchanged with the O-RU Controller. - -### Procedure and execution steps - -#### Preconditions - -DUT is the Shared O-RU with TLS support enabled. - -#### Execution steps - -Follow the test case in clause 6.3 of the present document. - -#### Expected results - -The DUT provides confidentiality and integrity protection for data in transit on the Open Fronthaul M-Plane interface. - -**Expected format of evidence:** Log entries and packet captures. - -## 25.2.4 Reject Password-based authentication - -**Requirement Name:** Denial of password-based authentication with an O-RU Controller by Shared O-RU - -**Requirement Reference:** SEC-CTL-SharedORU-2, clause 5.1.9.2, O-RAN Security Requirements and Controls Specifications [5] - -**Requirement Description:** Shared O-RU is able to reject password-based authentication on the Open Fronthaul M-Plane - -**Threat References:** T-SharedORU-04 - -**DUT/s:** Shared O-RU - -**Test Name:** TC\_SharedORU\_SSH\_Password\_Based\_Authentication - -**Purpose:** To verify the Shared O-RU can reject a SSH session using password-based authentication on the Open Fronthaul. - -### Procedure and execution steps - -#### Preconditions - -DUT is the Shared O-RU with password-based authentication for SSH on the Open Fronthaul disabled. - -**Execution steps** - -- 1) Enable SSH on the Open Fronthaul for the Shared O-RU. Ensure password-based authentication is not enabled on the Shared O-RU for SSH on the Open Fronthaul. -- 2) Configure the O-RU Controller as the SSH client with password-based authentication on the Open Fronthaul M-Plane. -- 3) Attempt to establish the Open Fronthaul M-Plane session between the Shared O-RU and O-RU Controller. - -**Expected results** - -The DUT rejects the Open Fronthaul M-Plane session with the O-RU Controller. - -**Expected format of evidence:** Log entries, packet captures, and/or screenshots. - -## Annex A (informative): Example of Security Testing Tools / Toolset - -**Table Annex A-1: List of sample open source security testing tools/toolset** - -| Testing Tool | Example(s) | -|-----------------------------|----------------------------------------------------------------------------------------------------------------------| -| DTLS scanning tool | open source "pySSLScan": https://github.com/DinoTools/pysslscan | -| IPsec IKE scanning tool | open source "ike-scan": https://github.com/royhills/ike-scan | -| Port scanner | open source "Nmap": https://nmap.org/ | -| SSH audit tool | open source "ssh-audit": https://github.com/jtesta/ssh-audit | -| TLS scanning tool | open source "sslyze": https://github.com/nabla-c0d3/sslyze | -| Software image signing tool | open source "Sigstore": https://github.com/sigstore | - -# Annex B (informative): Template of test report - -## 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 Section 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 the sub-module version (such as vulnerability database version) - -## C. SYSTEM UNDER TEST - -| | | -|--------------------------------------------------|----------------------------| -| C1 Total number of DUTs included in SUT | C2 Deployment architecture | -| C3 Description of SUT – connection/block diagram | | - -DUT 1\* - -| | | | -|--------------------------------------------------------|------------------|-------------------------------| -| C3 Type | C4 Serial Number | C5 Supplier (manufacture) | -| C6 SW version | | C7 HW version (if applicable) | -| 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 - -| | | -|---------------------------------------|--------------------| -| D1 Function(s) and Service(s) setting | D2 Network setting | -|---------------------------------------|--------------------| - -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 | | -| E7 Execution steps – describe differences in comparison with the execution steps defined in test spec. – limitations | | -| E8 Test results –including outputs of the test properties and the attachment of log file(s) and/or screenshots | | -| E9 Notes, including observed issues with the solutions | | -| E10 Conclusions – pass/fail – assessment of test results in comparison with the expected results – gap analysis | | - ---- - -## Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2021.11.10 | 01.00 | Final initial version 01.00 | -| 2022.03.23 | 02.00.07 | Updated clauses:

7.4 Network Protocol Fuzzing

9.4 Software Bill of Materials (SBOM)

11.2 Open Fronthaul Point-to-Point LAN Segment

17.2 O1 Interface Network Configuration Access Control Model (NACM) Validation | -| 2022.07.19 | 03.00.01 | Applied the latest O-RAN technical specifications template

Updated clauses:

2.1 Normative references

3.2 Abbreviations

6.3 TLS

6.6 OAuth 2.0

9.5 Software Image Signing and Verification

13.2 Testing of IPSec on E2

14.2 Testing of TLS on A1 | -| 2022.07.25 | 03.00.02 | Updated cross-reference clause numbers of the test cases to align with latest WG11 specs

Updated table of contents | -| 2023.03.09 | 04.00.00 | Updated clauses:
  • • 14 Security Test of xApps
  • • 15 Security test of Non-RT RIC
  • • 16 Security test of rApps
Added content to:
  • • 14.2 xApp Signing and Verification
  • • 16.2 rApp Signing and Verification
Change wording in many places to align document with ETSI PAS | - -| | | | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2023.07.10 | 05.00.00 |

Added content to:

  • • 9.4.3 SBOM Format
  • • 9.4.4 SBOM Depth
  • • 9.5.2 Software Signature Verification
  • • 12.4 O-RU Security functional requirement and test cases
  • • 13.2 IPSec on E2 interface
  • • 13.3 Transactional APIs
  • • 18.2 O2 Interface
  • • 18.3 O-Cloud virtualization layer
  • • 20 Security tests of Common Application Lifecycle Management
  • • 21 Security test of O-CU-CP
  • • 22 Security test of O-CU-UP
  • • 23 Security test of O-DU

Alignment for ETSI PAS

| -| 2024.03.20 | 07.00.00 |
  • • OAuth2.0 in Near-RT RIC
  • • OCloud tests
  • • Reorganization of interfaces testing (A1, R1)
  • • Update of SCTP test cases, removing not related with security
  • • TIFG E2E test cases adoption into clause 24, and needed update
  • • SBOM and Package testing increased
  • • E2 data validation tests for Near-RT RIC
| - -| | | | -|------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2024.07.17 | 08.00.00 |

Added content to:

  • • 6.9 X.509
  • • 7.5 Denial of Service/Message flooding
  • • 7.6 Input validation and error handling
  • • 7.7 Secure configuration enforcement
  • • 11 Security tests of O-RAN interfaces
  • • 18.4 Application instantiation by O-Cloud
  • • 18.9 Secure time synchronization for O-Cloud
  • • 20.2 Application Package

Removed content from:

  • • 6.2 SSH
  • • 6.3 TLS
  • • 6.4 DTLS
  • • 6.7 NACM
  • • 6.8 802.1X
  • • 7.5 Denial of Service/Message flooding
  • • 7.7 Secure configuration enforcement
  • • 9.4 SBOM
  • • 11 Security tests of O-RAN interfaces
| -|------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| - -| | | | -|------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2024.11.27 | 09.00.00 |

Changed content in:

  • • 6 Security Protocol & APIs Validation
  • • 7 Common Network Security Tests for O-RAN architecture elements
  • • 8 System security evaluation for O-RAN architecture element
  • • 9 Software security evaluation for O-RAN architecture elements
  • • 11.1 FH
  • • 14 Security test of xApps
  • • 18.4 Application instantiation deployment by O-Cloud
  • • 19.2 Executive environment protection
  • • 24 End-to-End security test cases

Removed content from:

  • • 6.10.1 eCPRI Session Management
  • • 6.10.4 eCPRI Access Control
  • • 6.10.6 eCPRI Timeout Error Handling
  • • 8.4.9 Storage
  • • 9.4.5 SBOM completeness check
  • • 9.4.10 SBOM OSC Components
  • • 9.5.1 Software Image/Application Package Signing
| -| 2025.03.23 | 10.00.00 |

Changed content in clauses 6, 7, 8, 11, 12, 13, 15, 16, 17, 18, 19, 20, 24, 25

Added content:

  • • 6.6.1 API Consumer
  • • 6.6.2 Resource Server
  • • 18.6.5 Unauthorised Rollback Prevention

Removed content from:

  • • 11.1.5.1.2 DoS timeTransmitter LLS C4
| - -| | | | -|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2025.07.23 | 11.00.00 |

Editorial updates applied

Added content:

  • 6.3.1 TLS Support
  • 6.3.2 TLS Version Negotiation
  • 6.3.3 TLS Deprecated Versions
  • 6.12.1 Transactional API Authentication - service producer role
  • 6.12.3. Transactional API Input Validation and Sanitization
  • 6.13 MACsec
  • 9.5.1 Signature Verification Matrix per DUT and Phase
  • 9.5.2 Signature Verification Test Cases
  • 11.1.2.3 Port-Based Access Enforcement Validation
  • 11.1.2.4 O-RU Authentication Lifecycle with Manufacturer and Operator Certificates
  • 11.1.3.1.4 Open FH M-Plane SSH-certificate-based authentication authorization at O-DU
  • 11.2.3. Y1 Authorization
  • 14.3.1.xApp ID format check

Removed content from:

  • 11.1.5.3.1. Selective Interception and Removal of PTP Timing Packets
  • 11.1.5.3.2 Delay Attack on PTP Timing Packets
  • 14.2 xApp Signing and Verification
  • 16.2 rApp Signing and Verification
  • 18.4.1 Verification of Application artifacts with valid signature by O-Cloud during deployment
  • 18.4.2 Verification of Application artifacts with incorrect signature by O-Cloud during deployment
  • 19.3 Signature validation during App image onboarding
  • 20.2.1 Application package signature verification
| -|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| - -| | | | -|------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2025.12.05 | 12.00.00 |

Editorial updates applied

Added content:

  • 6.13 MACsec
  • 7.3.3 Password Policy Enforcement
  • 7.3.4 Default Password Change
  • 7.3.5 Password stored as salted
  • 7.3.6 Client secrets stored as encrypted
  • 7.3.7 O-RU Password Policy Enforcement
  • 11.1.2.5 Unauthorized port behavior
  • 11.1.2.6 Authorization policy enforcement
  • 11.1.3.0 Applicability of Certificate Verification based on Trust Anchor State
  • 11.1.3.1.5 Open FH M-plane SSH-Key-based authentication
  • 11.1.3.5 Open FH M-plane NACM Authorization validation

Removed content from:

  • 6.6.1 API Consumer
  • 6.7.2 NACM Logging Monitoring
  • 11.1.3.1.3 Open FH M-plane SSH Certificate-based NACM Access Control
  • 19.4 Application image deployment security
| -|------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| \ No newline at end of file diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/09db9fad28b18ea44e6d78b672cd12ff_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/09db9fad28b18ea44e6d78b672cd12ff_img.jpg deleted file mode 100644 index 035eb87ca5c0e54227bc6c76adf1102be069393b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/09db9fad28b18ea44e6d78b672cd12ff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:38dda06c1bd33ae0f8bb020dd60df66c64de11cc4c43e0e156dff17ad2226589 -size 48771 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/09fcf056902487318885284a6b43b08c_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/09fcf056902487318885284a6b43b08c_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/09fcf056902487318885284a6b43b08c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/0e611959485447591664307862231ffd_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/0e611959485447591664307862231ffd_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/0e611959485447591664307862231ffd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/0ee9d674085524d589646a6c3fb21ec3_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/0ee9d674085524d589646a6c3fb21ec3_img.jpg deleted file mode 100644 index f6a5437248f28451faf0cbfc584d5d6b14a791c1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/0ee9d674085524d589646a6c3fb21ec3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb4d30b3313ea27f99556f93263848f28562c74ace3b0eca1337aba2f5841812 -size 73773 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/102806f6dea2a9f7e01d371d74f8195f_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/102806f6dea2a9f7e01d371d74f8195f_img.jpg deleted file mode 100644 index 173f3bf479f230393befef5999d3867e0b184417..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/102806f6dea2a9f7e01d371d74f8195f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6291252868c9b3ecfc0c502d986ea3033534a1d5d8be57b8aab69ea78ecf1d53 -size 45640 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/134b1f0d617209a0436333b9ab6b1ce8_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/134b1f0d617209a0436333b9ab6b1ce8_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/134b1f0d617209a0436333b9ab6b1ce8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/16152cf1d84aea10848758f51a91ff6a_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/16152cf1d84aea10848758f51a91ff6a_img.jpg deleted file mode 100644 index ed153573a94392133e94f2280773882f68f8be3d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/16152cf1d84aea10848758f51a91ff6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a05f83117ae6c8c29b8c26f4b6b19efba9bd707aa4463250e8e1b1467719e8e4 -size 77869 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1baaba7a6e54e77197475726c871067d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1baf92180f2964741688e8215d7183da_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1baf92180f2964741688e8215d7183da_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1baf92180f2964741688e8215d7183da_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/22be8ddff39ab7239459476e6cb8d6e0_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/22be8ddff39ab7239459476e6cb8d6e0_img.jpg deleted file mode 100644 index 2f3a373c44de4b18da6d75556ccda87572e19fc4..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/22be8ddff39ab7239459476e6cb8d6e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8977587c53138a1979870c1f75e8a93a6ab643ce9a2085cdff56f13f132779e4 -size 46416 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/23b110b75da6b415520918830060195e_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/23b110b75da6b415520918830060195e_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/23b110b75da6b415520918830060195e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg deleted file mode 100644 index b65c9819ba60bfe19f6cdb95d3075d756b2b6c71..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0cad14f9ac2225f628dcfe49bccbde098fb99facc8adc2cec5e351074d1e3eee -size 4528 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2a185522b492253375ed16f0c515c230_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2a185522b492253375ed16f0c515c230_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2a185522b492253375ed16f0c515c230_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2eea01382188b70064fa2818361d89f1_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2eea01382188b70064fa2818361d89f1_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2eea01382188b70064fa2818361d89f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2fdf2dbffaf6ea606624441e4574c011_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2fdf2dbffaf6ea606624441e4574c011_img.jpg deleted file mode 100644 index b65c9819ba60bfe19f6cdb95d3075d756b2b6c71..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/2fdf2dbffaf6ea606624441e4574c011_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0cad14f9ac2225f628dcfe49bccbde098fb99facc8adc2cec5e351074d1e3eee -size 4528 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg deleted file mode 100644 index 0b0782c79469394517a1b44fded1970b091dfed2..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c01ae9c750e9b34c335d831a13888c58e4f703256bbe016604fa104a87b4b5d0 -size 54298 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/318db222fae24a59c370fa6471d541b8_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/318db222fae24a59c370fa6471d541b8_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/318db222fae24a59c370fa6471d541b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/35437f160e157760713aa85be471c3f3_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/35437f160e157760713aa85be471c3f3_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/35437f160e157760713aa85be471c3f3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/35d5c5a5774a7997f06756915721031b_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/35d5c5a5774a7997f06756915721031b_img.jpg deleted file mode 100644 index a675f04ac98b07684c8d418e2cb8c839381ef738..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/35d5c5a5774a7997f06756915721031b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:031310bc4543da6fbe1b1528daf3023b1613843315d7978d76bcf64de496ffa1 -size 45471 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/3b89d812329a65ab156184a40524adf0_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/3b89d812329a65ab156184a40524adf0_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/3b89d812329a65ab156184a40524adf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4d37e5b3681dcb0b4940ddd7ab5969ed_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4d37e5b3681dcb0b4940ddd7ab5969ed_img.jpg deleted file mode 100644 index 88c7ebedcc54c08225ff9205ef544c63eca12deb..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4d37e5b3681dcb0b4940ddd7ab5969ed_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f74ee284244938c27418941463689a523b7d8365fdc3ff57b8fb4f937a4a1ff6 -size 44172 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4f407c97df6e5ee98fdb248ada82de59_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4f407c97df6e5ee98fdb248ada82de59_img.jpg deleted file mode 100644 index ad6a25e4a4c79c67aded2ce43fe7d51eaa029d20..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4f407c97df6e5ee98fdb248ada82de59_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f95573a0a71e125c427dfa0b206d3ce28bded87b58a0697f49f79e02e0112e78 -size 43846 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/5009e30a55479d3941af523871208f9d_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/5009e30a55479d3941af523871208f9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/568031aac86c633aab96b734dba3835e_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/568031aac86c633aab96b734dba3835e_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/568031aac86c633aab96b734dba3835e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/58998c9d67656e95221338204f251872_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/58998c9d67656e95221338204f251872_img.jpg deleted file mode 100644 index 97f53e925ef1fd1ed2b0c62aef3f695dc2c51e78..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/58998c9d67656e95221338204f251872_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:efc1d36b1696a01c8c82dc60ade4db191a280ce90d9155750e7c0b4bd2c7ca14 -size 45496 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/59368942873b0c35eef79a7a985025dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/5fa61cb21e87cecbe7049420f633a811_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/5fa61cb21e87cecbe7049420f633a811_img.jpg deleted file mode 100644 index 930b29c592e18e4ee9b7f13de4f79020ff712459..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/5fa61cb21e87cecbe7049420f633a811_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5f8013eada922e4dd6d610cf1f66e7ef4cde52eba107e33f0825d24ae802b0e6 -size 4550 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/5fbe6b9515c3d8f7d2526ca5bfbd012d_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/5fbe6b9515c3d8f7d2526ca5bfbd012d_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/5fbe6b9515c3d8f7d2526ca5bfbd012d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/624dbf9b985f5bd85e902ec59b87ba4f_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/624dbf9b985f5bd85e902ec59b87ba4f_img.jpg deleted file mode 100644 index b65c9819ba60bfe19f6cdb95d3075d756b2b6c71..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/624dbf9b985f5bd85e902ec59b87ba4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0cad14f9ac2225f628dcfe49bccbde098fb99facc8adc2cec5e351074d1e3eee -size 4528 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/64ca20a7357e612f7c65bbe816032c8a_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/64ca20a7357e612f7c65bbe816032c8a_img.jpg deleted file mode 100644 index 7767b40026aca4f6649638cb119cf22de751471d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/64ca20a7357e612f7c65bbe816032c8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d6be91b59174b57cd0c975ac78a3659d14662a5561fb2bd5ef7bcc4a97f256fb -size 44722 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6588b1c7f14069d96744b473ad663248_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/67fd5cc2c3bec87e3a06d5ad92744560_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/67fd5cc2c3bec87e3a06d5ad92744560_img.jpg deleted file mode 100644 index 3208b1e30230c1c26d47a82f9a238d3c112e716f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/67fd5cc2c3bec87e3a06d5ad92744560_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fb8701fa8b81071b2b688017bb4ec897f0147e170366e60f86f7fa3528862b21 -size 4528 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/686705f78594bdc18af4f9cb04b455e0_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/686705f78594bdc18af4f9cb04b455e0_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/686705f78594bdc18af4f9cb04b455e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6983ff962c0a32659de18c30790e1519_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6983ff962c0a32659de18c30790e1519_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6983ff962c0a32659de18c30790e1519_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 19f401a5cfbf08aa0ec7781203e69177a2b7e39d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/854df8ad60507803253274673f9062cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5836b6268e1b6d229168b5e47faaaafd32832660ba85975f8ee7a6e10fc63fff -size 4560 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8b4befaffc5166da571069410e207aea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/901b345e560dfa29a2c7967f95bd54bb_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/901b345e560dfa29a2c7967f95bd54bb_img.jpg deleted file mode 100644 index b65c9819ba60bfe19f6cdb95d3075d756b2b6c71..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/901b345e560dfa29a2c7967f95bd54bb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0cad14f9ac2225f628dcfe49bccbde098fb99facc8adc2cec5e351074d1e3eee -size 4528 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/93b6985cb029eb10703d0a59c2ae0c94_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/93b6985cb029eb10703d0a59c2ae0c94_img.jpg deleted file mode 100644 index 77c811d3bcb76362a830376e7daf09ce4c0b0fba..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/93b6985cb029eb10703d0a59c2ae0c94_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8dd2f4c3f1882d68d10c3981d65d850320d89edc0ef9e720b8e1de22e5aebe2 -size 44666 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg deleted file mode 100644 index c42c8b8f9c124c58034206c902414f4502efa788..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c6df7554da07e6f3e6b18e8ed1812d01c3addaf22bb701fde646661134788682 -size 49898 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a1890b9a9b85f13e67ed59bbad623659_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a1890b9a9b85f13e67ed59bbad623659_img.jpg deleted file mode 100644 index c1453a4bb6fbdbfc00286f4ae8a9cd6dd1fe0cbe..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a1890b9a9b85f13e67ed59bbad623659_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d7ee0123cef058b42de57aa9326defa6d6a2d2ee9ba022fc874499ceed3131f5 -size 72652 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/aef4390a4629604196222b9ed006a786_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/aef4390a4629604196222b9ed006a786_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/aef4390a4629604196222b9ed006a786_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/b303fb8b2c64e30aac9c32b5753d3670_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/b303fb8b2c64e30aac9c32b5753d3670_img.jpg deleted file mode 100644 index 13046e17c7ec17391e014c26dd4eaf5d72313936..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/b303fb8b2c64e30aac9c32b5753d3670_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5a756f5667e4a63714ad6e8ac49cbe7210a82c2d9ac211bfec6f46e3cb52415d -size 44421 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg deleted file mode 100644 index b38df3db3bb687a0ee4dcfed4de9aa9bcddcffd7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6a4db29f250f2f489e9af4062be3cde91fb1cd832ed24a25e13c337eee5e2bae -size 4501 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bb9f586190c7197099d25db7df9050af_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bb9f586190c7197099d25db7df9050af_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bb9f586190c7197099d25db7df9050af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bcb0b443fcfea25dcb7005487af9200d_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bcb0b443fcfea25dcb7005487af9200d_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bcb0b443fcfea25dcb7005487af9200d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bfcea196796f3bc23aeb4499b396cab1_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bfcea196796f3bc23aeb4499b396cab1_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/bfcea196796f3bc23aeb4499b396cab1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c3c2b3eb8e16ab6cd6acdec0fcf82999_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c3c2b3eb8e16ab6cd6acdec0fcf82999_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c3c2b3eb8e16ab6cd6acdec0fcf82999_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c5eb42ed730ecb12621fc63444830d4b_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c5eb42ed730ecb12621fc63444830d4b_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c5eb42ed730ecb12621fc63444830d4b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d35a80e3faed208324083399568c7461_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d35a80e3faed208324083399568c7461_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d35a80e3faed208324083399568c7461_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg deleted file mode 100644 index 2dbcdfabf876faa8d2351a2c611a8026b7243ec9..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c8cb399768710ec32e7a75a7e983605f881df7423255c4f1069d069d464a03b -size 4534 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f74adaa1840504407cd4272995426f82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg deleted file mode 100644 index 9ca5ed8ce8312dadf2e15f0daebd862b4bdd62ae..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:561b710352fd8baaf2a3809df1471acb77d5117ac44a9c52213d7a355c5d248c -size 4486 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f92ebf4eb3d62b7dfa401644b0b6e40d_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f92ebf4eb3d62b7dfa401644b0b6e40d_img.jpg deleted file mode 100644 index b65c9819ba60bfe19f6cdb95d3075d756b2b6c71..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f92ebf4eb3d62b7dfa401644b0b6e40d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0cad14f9ac2225f628dcfe49bccbde098fb99facc8adc2cec5e351074d1e3eee -size 4528 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/fac227c65a311c313325216dcf59591f_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/fac227c65a311c313325216dcf59591f_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/fac227c65a311c313325216dcf59591f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/facce731b2dbfae43a8609231a700be1_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/facce731b2dbfae43a8609231a700be1_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/facce731b2dbfae43a8609231a700be1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 4899faaa3d1f0b86af07d79ce1260385e94c7ae1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:42d2514b37b3cb42b88fc5f254210f81a97d2cd0644f6cc4b7825a09a72ca983 -size 4565 diff --git a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.STS-R005-v12.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/doc.md b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/doc.md deleted file mode 100644 index ed21fde5094d81c3d84c2a5a09824cb274e443dc..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/doc.md +++ /dev/null @@ -1,1212 +0,0 @@ - - -# --- **O-RAN Work Group 11 (Security Work Group)****Security Protocols Specifications** - -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 - -- List of figures ..... 4 -- List of tables ..... 4 -- Foreword..... 5 -- Modal verbs terminology ..... 5 -- 1 Scope..... 6 -- 2 References ..... 6 - - 2.1 Normative references ..... 6 - - 2.2 Informative references ..... 10 -- 3 Definition of terms, symbols and abbreviations ..... 11 - - 3.1 Terms ..... 11 - - 3.2 Symbols..... 11 - - 3.3 Abbreviations..... 11 -- 4 Security protocols specifications for O-RAN compliant implementation ..... 12 - - 4.1 SSH ..... 12 - - 4.1.1 General requirements ..... 12 - - 4.1.2 Required ciphers..... 13 - - 4.2 TLS ..... 14 - - 4.2.1 General Requirements ..... 14 - - 4.2.2 TLS Protocol Profile ..... 14 - - 4.2.3 TLS Certificate Profile ..... 15 - - 4.3 Support NETCONF over secure Transport..... 15 - - 4.4 DTLS..... 15 - - 4.4.1 General requirements ..... 15 - - 4.4.2 DTLS Protocol Profile ..... 15 - - 4.4.3 Certificate Profile ..... 16 - - 4.5 IPsec..... 16 - - 4.5.1 General Requirements ..... 16 - - 4.5.2 Parallel usage of IPsec and other secure transport protocols ..... 17 - - 4.5.3 Responder mode and Initiator/Responder mode support ..... 17 - - 4.6 CMPv2..... 17 - - 4.7 OAuth 2.0..... 18 - - 4.7.1 Overview ..... 18 - - 4.7.2 Basic Parameterization..... 18 - - 4.7.3 OAuth2.0 Access token API for O-RAN Elements and interfaces..... 20 - - 4.8 LDAP ..... 26 - - 4.8.1 General requirements ..... 26 - - 4.9 MACsec ..... 26 - - 4.9.1 General requirements ..... 26 - - 4.9.2 MACsec Profile..... 26 -- 5 Cryptographic operations ..... 27 -- 6 Secure File Transfer protocols ..... 30 - - 6.1 General..... 30 - - 6.2 SFTP ..... 30 - - 6.2.1 General Requirements ..... 30 - - 6.3 FTPES ..... 30 - - 6.3.1 General Requirements ..... 30 - - 6.4 HTTPS ..... 30 - - 6.4.1 General Requirements ..... 30 -- Annex A (normative): OpenAPI specifications ..... 31 - - A.1 OAuth2.0 API ..... 31 - - A.1.1 Introduction ..... 31 - - A.1.2 OAuth 2.0 Access Token API ..... 31 - -Annex B (informative): Example of TLS entity Certificate Profile for NETCONF authentication ..... 33 - -Annex (informative): Change history/Change request (history) ..... 35 - -# --- List of figures - -| | | -|------------------------------------------------------------------------|----| -| Figure 4.7-1: Access Token request process..... | 19 | -| Figure 4.7-2: Service access request based on token verification ..... | 20 | -| Figure 4.7-3: Resource structure for access token ..... | 21 | -| Figure 4.7-4: Access Token Request and Response ..... | 22 | -| Figure 4.7-5: Service request using access token ..... | 25 | - -# --- List of tables - -| | | -|-----------------------------------------------------------------------------------------|----| -| Table 4.7-1: Resources and methods overview of the Access Token API ..... | 20 | -| Table 4.7-2: Data structures supported by the POST request body on this resource..... | 22 | -| Table 4.7-3: Data structures supported by the POST Response Body on this resource. .... | 23 | -| Table 4.7-4: Headers supported by the 200 Response Code on this resource. .... | 23 | -| Table 4.7-5: Definition of type AccessTokenReq ..... | 23 | -| Table 4.7-6: Definition of type AccessTokenRsp..... | 24 | -| Table 4.7-7: Definition of type AccessTokenErr..... | 24 | -| Table 5-1: Cryptographic Operations for O-RAN ..... | 28 | -| Table B-1 ..... | 33 | - -# Foreword - -This Technical Specification (TS) has been produced by WG11 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 security protocols as to be used for O-RAN compliant implementation. - -# 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 1: 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. - -NOTE 2: All specifications issued by IETF referenced in the present document are valid in the latest version which the IETF declares as valid. Any updates to valid RFCs have to be considered and implemented, if applicable. - -- [1] Void. -- [2] IETF RFC 4252: "The Secure Shell (SSH) Authentication Protocol". -- [3] Void. -- [4] Void. -- [5] IANA: "Secure Shell (SSH) Protocol Parameters". -- [6] O-RAN ALLIANCE TS: "O-RAN Management Plane Specification". -- [7] Void. -- [8] IANA: "Transport Layer Security (TLS) Parameters". -- [9] Void. -- [10] O-RAN ALLIANCE TS: "O-RAN Operations and Maintenance Interface Specification" . -- [11] IETF RFC 6668: "SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol". -- [12] IETF RFC 8268: "More Modular Exponentiation (MODP) Diffie-Hellman (DH) Key Exchange (KEX) Groups for Secure Shell (SSH)". -- [13] IETF RFC 8308: "Extension Negotiation in the Secure Shell (SSH) Protocol". -- [14] IETF RFC 8332: "Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) Protocol". -- [15] IETF RFC 8709: "Ed25519 and Ed448 Public Key Algorithms for the Secure Shell (SSH) Protocol". -- [16] Void. -- [17] Void. -- [18] IETF RFC 8446: "The Transport Layer Security Protocol (TLS) v1.3". -- [19] Void. -- [20] 3GPP TS 33.210: "Network Domain Security (NDS); IP network layer security". - -- [21] Void. -- [22] IETF RFC 6066: "Transport Layer Security (TLS) Extensions: Extension Definitions". -- [23] Void. -- [24] IETF RFC 6083: "Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)". -- [25] Void. -- [26] 3GPP TS 33.310: Network Domain Security (NDS); Authentication Framework (AF)". -- [27] IETF RFC 4301: "Security Architecture for the Internet Protocol". -- [28] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture". -- [29] 3GPP TS 33.501: "Security architecture and procedures for 5G system". -- [30] Void. -- [31] IETF RFC 4303: "IP Encapsulating Security Payload (ESP)". -- [32] Void. -- [33] Void. -- [34] IETF RFC 7296: "Internet Key Exchange Protocol Version 2 (IKEv2)". -- [35] IETF RFC 6749: "The OAuth 2.0 Authorization framework". -- [36] IETF RFC 7519: "JSON Web Token (JWT)". -- [37] IETF RFC 7515: "JSON Web Signature (JWS)". -- [38] IETF RFC 4210: "Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP)". -- [39] IETF RFC 4211: "Internet X.509 Public Key Infrastructure Certificate Request Message Format". -- [40] NIST: "Cryptographic Standards and Guidelines". -- [41] Void. -- [42] NIST: "Digital Signature Standard (DSS) (FIPS PUB 186-5)". -- [43] Void. -- [44] NIST: "Advanced Encryption Standard (AES) (FIPS PUB 197)". -- [45] Void. -- [46] Void. -- [47] NIST: "SHA-3 Standard: Permutation-Based Hash and Extendable-Output Function (FIPS PUB 202)". -- [48] NIST SP 800-131A Rev. 2: "Transitioning the Use of Cryptographic Algorithms and Key Lengths". -- [49] Void. -- [50] IETF RFC 8017: "PKCS #1: RSA Cryptography Specifications Version 2.2". -- [51] Void. -- [52] Void. -- [53] Void. -- [54] Void. -- [55] IETF RFC 7633: "X.509v3 Transport Layer Security (TLS) Feature Extension". - -- [56] CA/Browser Forum: "Baseline Requirements for the Issuance and Management of Publicly-Trusted Certificates". -- [57] Void. -- [58] Void. -- [59] Void. -- [60] IETF RFC 7093: "Additional Methods for Generating Key Identifiers Values". -- [61] Void. -- [62] IETF RFC 6960: "X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP". -- [63] IETF RFC 3647: "Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices Framework". -- [64] IETF RFC 5280: "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile". -- [65] SFTP: "SFTP Standards". -- [66] IETF RFC 4217: "Securing FTP with TLS (FTPES)". -- [67] 3GPP TS 28.532: "Management and orchestration; Generic management services". -- [68] 3GPP TS 28.537: "Management and orchestration; Management capabilities". -- [69] IETF RFC 9110: "HTTP Semantics (HTTPS)". -- [70] IETF RFC 4253: "The Secure Shell (SSH) Transport Layer Protocol". -- [71] IETF RFC 9325: "Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)". -- [72] IETF RFC 3279: "Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile". -- [73] ITU-T Recommendation X.509: "Information technology - Open Systems Interconnection - The Directory: Public-key and attribute certificate frameworks". -- [74] IETF RFC 4511: "Lightweight Directory Access Protocol (LDAP): The Protocol". -- [75] IETF RFC 4513: "Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanisms". -- [76] IETF RFC 9147: "The Datagram Transport Layer Security (DTLS) Protocol Version 1.3". -- [77] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition". -- [78] IETF RFC 6750: "The OAuth 2.0 Authorization Framework: Bearer Token Usage". -- [79] IEEE Std 802.1AE-2018: "IEEE Standard for Local and metropolitan area networks — Media Access Control (MAC) Security". -- [80] IETF RFC 9519: "Update to the IANA SSH Protocol Parameters Registry Requirements". -- [81] IETF RFC 7427: "Signature Authentication in the Internet Key Exchange Version 2 (IKEv2)". -- [82] IETF RFC 7670: "Generic Raw Public-Key Support for IKEv2". -- [83] IETF RFC 8247: "Algorithm Implementation Requirements and Usage Guidance for the Internet Key Exchange Protocol Version 2 (IKEv2)". -- [84] IETF RFC 8983: "Internet Key Exchange Protocol Version 2 (IKEv2) Notification Status Types for IPv4/IPv6 Coexistence". - -- [85] IETF RFC 9370: "Multiple Key Exchanges in the Internet Key Exchange Protocol Version 2 (IKEv2)". -- [86] IETF RFC 5656: "Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer" -- [87] IETF RFC 5647: "AES Galois Counter Mode for the Secure Shell Transport Layer Protocol" -- [88] IETF RFC 4344: "The Secure Shell (SSH) Transport Layer Encryption Modes" -- [89] IETF RFC 4419: "Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol" -- [90] IETF RFC 8270. "Increase the Secure Shell Minimum Recommended Diffie-Hellman Modulus Size to 2048 Bits" -- [91] IETF RFC 8731, "Secure Shell (SSH) Key Exchange Method Using Curve25519 and Curve448" -- [92] IETF RFC 4418, "UMAC: Message Authentication Code using Universal Hashing" -- [93] IETF RFC 8725: "JSON Web Token Best Current Practices". -- [94] IETF RFC 7797: "JSON Web Signature (JWS) Unencoded Payload Option". -- [95] IETF RFC 9480: "Certificate Management Protocol (CMP) Updates". -- [96] IETF RFC 9481: "Certificate Management Protocol (CMP) Algorithms". -- [97] IETF RFC 9045: "Algorithm Requirements Update to the Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)". -- [98] IETF RFC 9525: "Service Identity in TLS". -- [99] IETF RFC 9654: "Online Certificate Status Protocol (OCSP) Nonce Extension". -- [100] IETF RFC 6818: "Updates to the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile". -- [101] IETF RFC 9549: "Internationalization Updates to RFC 5280". -- [102] IETF RFC 9598: "Internationalized Email Addresses in X.509 Certificates". -- [103] IETF RFC 9608: "No Revocation Available for X.509 Public Key Certificates". -- [104] IETF RFC 9618: "Updates to X.509 Policy Validation". -- [105] IETF RFC 6668: "SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol". -- [106] IETF RFC 8268: "More Modular Exponentiation (MODP) Diffie-Hellman (DH) Key Exchange (KEX) Groups for Secure Shell (SSH)". -- [107] IETF RFC 8308: "Extension Negotiation in the Secure Shell (SSH) Protocol". -- [108] IETF RFC 8332: "Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) Protocol". -- [109] IETF RFC 8709: "Ed25519 and Ed448 Public Key Algorithms for the Secure Shell (SSH) Protocol". -- [110] IETF RFC 8758: "Deprecating RC4 in Secure Shell (SSH)". -- [111] IETF RFC 9142: "Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH)". -- [112] IETF RFC 8996: "Deprecating TLS 1.0 and TLS 1.1". -- [113] IETF RFC 4055: "Additional Algorithms and Identifiers for RSA Cryptography for use in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile". -- [114] IETF RFC 5756: "Updates for RSAES-OAEP and RSASSA-PSS Algorithm Parameters". -- [115] IETF RFC 5480: "Elliptic Curve Cryptography Subject Public Key Information". - -- [116] IETF RFC 8813: "Clarifications for Elliptic Curve Cryptography Subject Public Key Information". -- [117] IETF RFC 5758: "Internet X.509 Public Key Infrastructure: Additional Algorithms and Identifiers for DSA and ECDSA". -- [118] IETF RFC 8692: "Internet X.509 Public Key Infrastructure: Additional Algorithm Identifiers for RSASSA-PSS and ECDSA Using SHAKEs". -- [119] NIST: "Secure Hash Standard (SHS) " (FIPS PUB 180-4) -- [120] IETF RFC 9113: "Hypertext Transfer Protocol Version 2 (HTTP/2)". -- [121] IETF RFC 9106: "Argon2 Memory-Hard Function for Password Hashing and Proof-of-Work Applications". -- [122] IETF RFC 7914: "The scrypt Password-Based Key Derivation Function". -- [123] OpenSSH Specifications - Description of AES-GCM cipher formats (aes128-gcm@openssh.com, aes256-gcm@openssh.com): . - -## 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 1: 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. - -NOTE 2: All specifications issued by IETF referenced in the present document are valid in the latest version which the IETF declares as valid. Any updates to valid RFCs have to be considered and implemented, if applicable. - -- [i.1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". -- [i.2] Void. -- [i.3] Void. -- [i.4] NIST SP 800-52 Rev.2: "Guidelines for the Selection, Configuration, and Use of Transport Layer Security (TLS) Implementations". -- [i.5] Void. -- [i.6] BSI TR-02102-1: "Cryptographic Mechanisms: Recommendations and Key Lengths". -- [i.7] NIST SP 800-38A: "Recommendation for Block Cipher Modes of Operation: Methods and Techniques". -- [i.8] NIST SP 800-186: "Recommendations for Discrete Logarithm-based Cryptography: Elliptic Curve Domain Parameters". -- [i.9] NIST SP 800-57 Part 1 Rev. 5: "Recommendation for Key Management: Part 1 – General". -- [i.10] Void. -- [i.11] IETF RFC 7589: "Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 Authentication". -- [i.12] NIST SP 800-90A: "Recommendation for Random Number Generation Using Deterministic Random Bit Generators". - -- [i.13] NIST SP 800-90B: “Recommendation for the Entropy Sources Used for Random Bit Generation”. -- [i.14] NIST SP 800-90C: “Recommendation for Random Bit Generator (RBG) Constructions”. -- [i.15] NIST FIPS 140-3: “Security Requirements for Cryptographic Modules”. -- [i.16] BSI: “Documentation and Analysis of the Linux Random Number Generator” -- [i.17] NIST SP 800-132: "Recommendation for Password-Based Key Derivation: Part 1: Storage Applications". -- [i.18] OWASP: "Password Storage Cheat Sheet". - -# --- 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 3GPP TR 21.905 [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 3GPP TR 21.905 [i.1]. - -| | | -|--------|---------------------------------------------------------| -| 0-RTT | Zero Round Trip Time | -| AEAD | Authenticated Encryption with Associated Data | -| AES | Advanced Encryption Standard | -| CA | Certification Authority | -| CMP | Certificate Management Protocol | -| CSPRNG | Cryptographically secure pseudo-random number generator | -| DH | Diffie–Hellman | -| DHE | Diffie–Hellman Ephemeral | -| DPD | Dead Peer Detection | -| DRBG | Deterministic Random Bit Generators | -| DTLS | Datagram Transport Layer Security | -| ECDHE | Elliptic Curve Diffie-Hellman Ephemeral | -| ESP | Encapsulating Security Payload | -| ETM | Encrypt-then-MAC | -| FTPES | Explicit SSL File Transfer Protocol | -| GCM | Galois Counter Mode | - -| | | -|---------|------------------------------------| -| HTTPS | Hypertext Transfer Protocol Secure | -| IKE | Internet Key Exchange | -| IPsec | Internet Protocol Security | -| NAT | Network Address Translation | -| NE | Network Element | -| NETCONF | Network Configuration Protocol | -| PFS | Perfect Forward Secrecy | -| PKI | Public Key Infrastructure | -| PSK | Pre-Shared Key | -| RA | Registration Authority | -| RNG | Random Number Generation | -| SA | Security Association | -| SFTP | SSH File Transfer Protocol | -| SHA | Secure Hash Algorithm | -| SPD | Security Policy Database | -| SSH | Secure Shell | -| TLS | Transport Layer Security | - -# --- 4 Security protocols specifications for O-RAN compliant implementation - -## 4.1 SSH - -### 4.1.1 General requirements - -O-RAN interfaces that implement authentication, confidentiality and integrity using SSH shall: - -- support SSHv2 as defined in IETF RFC 4252 [2], IETF RFC 4253 [70], IETF RFC 6668 [105], IETF RFC 8268 [106], IETF RFC 8308 [107], IETF RFC 9519 [80], IETF RFC 8332 [108], IETF RFC 8709 [109], IETF RFC 8758 [110], and IETF RFC 9142 [111]; -- not support SSHv1 -- disable by default cryptographically insecure ciphers as specified in clauses 4.1.2.1, 4.1.2.3, and 4.1.2.4; -- enable an O-RAN deployer to use standard SSH configurations to select the algorithms offered for negotiation; -- enable remote shell access only if required by the interface. If remote shell access is enabled, disable remote login as root or equivalent highest privileged user. Such access shall be limited to the local system console only. Root user shall not be allowed to login to the system remotely. - -Entities providing O-RAN components that support SSH for authentication, confidentiality or integrity shall: - -- stay current with SSH [5]; -- provide an upgrade path for changes to the SSH protocol and ciphers [5]. - -### 4.1.2 Required ciphers - -#### 4.1.2.0 Introduction - -O-RAN requires the following ciphers when using SSH. For more information see [2], [5], [11], [12], [13], [14], [15] and [80]. See Security clause 5.4 of the O-RAN Working Group 4 Management Plane Specification [6] for the M-plane mandated SSH ciphers. - -#### 4.1.2.1 Key agreement - -NOTE: the present document uses the IANA cipher naming convention [5]. - -- Shall be supported: - - a. ecdsa-sha2-nistp256 as defined in IETF RFC 5656 [86] - - b. ecdsa-sha2-nistp384 as defined in IETF RFC 5656 [86] - - c. ecdsa-sha2-nistp521 as defined in IETF RFC 5656 [86] - - d. ssh-ed25519 as defined in IETF RFC 8709 [15] -- Should be supported: - - a. ssh-ed448 as defined in IETF RFC 8709 [15] -- Shall not be supported: - - a. ssh-rsa - - b. ssh-dss - -#### 4.1.2.2 Symmetric algorithms for encrypting transferred data - -- Shall be supported - - a. aes256-gcm@openssh.com as defined in OpenSSH specifications [123] - - b. aes128-gcm@openssh.com as defined in OpenSSH specifications [123] - - c. aes256-ctr as defined in IETF RFC 4344 [88] - - d. aes192-ctr as defined in IETF RFC 4344 [88] - - e. aes128-ctr as defined in IETF RFC 4344 [88] - -NOTE: While aes128-gcm and aes256-gcm were originally defined in RFC 5647 [87], referencing them directly causes interoperability challenges due to their complex and less widely supported key exchange mechanism. The ciphers aes128-gcm@openssh.com and aes256-gcm@openssh.com, used by OpenSSH (see clause 1.6 of [123]), follow a simpler key selection approach. These OpenSSH variants maintain identical packet formats to RFC 5647 but use different key exchange rules, improving usability and compatibility. Therefore, this specification references the OpenSSH-defined versions for better practical adoption. - -#### 4.1.2.3 Key exchange algorithms (KexAlgorithms) - -- Shall be supported - - a. ecdh-sha2-nistp521 as defined in IETF RFC 5656 [86] - - b. ecdh-sha2-nistp384 as defined in IETF RFC 5656 [86] - - c. ecdh-sha2-nistp256 as defined in IETF RFC 5656 [86] - - d. diffie-hellman-group-exchange-sha256 as defined in IETF RFC 4419 [89], updated by IETF RFC 8270 [90] - - e. curve25519-sha256 as defined in IETF RFC 8731 [91] - - f. diffie-hellman-group14-sha256 as defined in IETF RFC 8268 [12] -- Shall not be supported: - - a. diffie-hellman-group1-sha1 - - b. diffie-hellman-group-exchange-sha1 - - c. gss-group1-sha1-\* - - d. gss-group14-sha1-\* - - e. gss-gex-sha1-\* - - f. rsa1024-sha1 - -#### 4.1.2.4 Message Authentication Codes (MACs) - -- Shall be supported - - a. hmac-sha2-512-etm (see NOTE) - - b. hmac-sha2-512 as defined in IETF RFC 6668 [11] - -- c. hmac-sha2-256-etm (see NOTE) -- d. hmac-sha2-256 as defined in IETF RFC 6668 [11] -- e. umac-128 as defined in IETF RFC 4418 [92] -- Shall not be supported: - - a. hmac-sha1 - -NOTE: ETM (Encrypt-then-MAC) does not have an SSH specification yet is a widely used and recommended practice within the SSHv2 protocol, and broadly supported in available implementations, due to its security- related advantages. - -## 4.2 TLS - -### 4.2.1 General Requirements - -O-RAN interfaces that implement one-way authentication, mutual authentication, confidentiality, integrity, and replay protection using Transport Layer Security (TLS) shall be compliant with [18], allow negotiation of both TLS 1.2 [18] and TLS 1.3 [18], and not allow negotiation to any version of SSL or any version of TLS below 1.2. Further, O-RAN interfaces using TLS may allow TLS 1.2 to be disabled by configuration ([i.4] , section 3.1). O-RAN interfaces that use a pre-shared key (PSK) should not send data on the first flight (early or 0-RTT data) because the security properties for these data are weaker than those for other kinds of TLS data and can lead to replay attacks. - -NOTE 1: In one-way TLS the server sends a Certificate message, a CertificateVerify message, and a Finished message to the client so that the client can authenticate the server by validating the server's certificate and possession of the private key associated with the certificate. In mutual TLS (mTLS) the server sends a CertificateRequest message indicating that the client must authenticate itself with a certificate. The server then sends a Certificate message, a CertificateVerify message, and a Finished message to the client. Upon receiving the server's messages, the client responds with its Authentication messages, namely Certificate and CertificateVerify, and Finished. For full details of the authentication steps in TLS see [18]. - -NOTE 2: [18] added a zero round-trip time (0-RTT) mode, saving a round trip at connection setup for some application data, at the cost of replay protection. When clients and servers share a PSK, TLS 1.3 allows clients to send data on the first flight ("early data"). The client uses the PSK to authenticate the server and to encrypt the early data. See Section 2.3 of [18] for more information. - -NOTE 3: See Appendix E.5 of [18] for a description of potential attacks, and Section 8 of [18] for mechanisms which the server can use to limit the impact of replay when using 0-RTT data. - -See clause 5.4 of the O-RAN Working Group 4 Management Plane Specification for the Open Fronthaul M-plane mandated TLS requirements [6]. - -#### 4.2.1.1 Void - -Void. - -### 4.2.2 TLS Protocol Profile - -TLS 1.2 used on an O-RAN specified interface shall support the TLS 1.2 profiles as defined by 3GPP TS 33.210 [20], clause 6.2.3. - -The Open Fronthaul has the following exception to 3GPP TS 33.210 [20], clause 6.2.3: - -- TLS 1.2 used on the Open Fronthaul interface may support cipher suites with AEAD (e.g. GCM) and PFS (e.g. ECDHE, DHE). - -TLS 1.3 used on an O-RAN specified interface shall support the TLS 1.3 profiles as defined by 3GPP TS 33.210 [20] clause 6.2.2. - -Use of a cipher suite in TLS shall be configurable. - -Additional cipher suites recommended by IANA [8] may be supported. - -The TLS cipher suites in RFC 9113 [120], Appendix A, shall be disabled or not supported. - -NOTE: The vendor and operator need to be prepared to replace integrity and/or ciphering algorithms if the current algorithm in use is compromised or deprecated. - -### 4.2.3 TLS Certificate Profile - -The present clause addresses the certificate profile requirements for the TLS entities that may behave either as client, server, or both. The profile of the certificates to be used with TLS is provided in this clause is based on requirements from 3GPP TS 33.310 [26]. The TLS entity certificate profile shall be applied to all nodes and interfaces that use the TLS protocol for secured communication in the O-RAN network. - -- The common rules for all certificates defined in 3GPP- TS 33.310 [26], clause 6.1.1 shall apply. -- The TLS entity certificate profile defined in 3GPP TS 33.310 [26], 6.1.3a shall apply. - -NOTE: Annex B provides an example of a TLS entity certificate profile used for NETCONF authentication. - -## 4.3 Support NETCONF over secure Transport - -TLS requirements for use with NETCONF on the O1 interface [10] are specified in clause 4.2. - -TLS requirements for use with NETCONF on the Open Fronthaul M-plane are specified in clause 5.4 of the O-RAN WG4 Management Plane Specification [6]. - -## 4.4 DTLS - -### 4.4.1 General requirements - -O-RAN interfaces that implement mutual authentication, integrity protection, replay protection and confidentiality protection using Datagram Transport Layer Security (DTLS) shall: - -- support DTLS 1.2 [76]; -- support DTLS for Stream Control Transmission Protocol [24]; - -and should support DTLS 1.3 [76]. - -DTLS 1.0 shall not be supported. - -NOTE: IETF RFC 6083 [24] specifies a user message limit of approximately 16k bytes, which does not align with the unlimited user message size that exists when SCTP is used without DTLS. There could be applications messages exceeding the limit, preventing the use of DTLS over SCTP, so enforcing unsecured SCTP. - -### 4.4.2 DTLS Protocol Profile - -For DTLS 1.2, all TLS 1.2 related provisions in clause 4.2.2 shall apply. - -For DTLS 1.3, all TLS 1.3 related provisions in clause 4.2.2 shall apply. - -### 4.4.3 Certificate Profile - -Certificate profile defined in clause 4.2.3 shall apply. - -## 4.5 IPsec - -### 4.5.1 General Requirements - -#### 4.5.1.1 Supported IPsec capabilities - -O-RAN interfaces that implement authentication, confidentiality and integrity using IPsec shall support IPsec according to IETF RFC 4301 [27]. The supported IPsec capabilities in this clause follow 3GPP TS 33.210 [20] for interworking purposes and further apply requirements given in [26], [28], and [29]. - -Services that shall be supported (see also 3GPP TS 33.501 [29], clause 9.8.2): - -- confidentiality, can be enabled/disabled (via ENCR\_NULL); -- integrity protection; -- data origin authentication; -- replay protection, can be enabled/disabled; -- extended sequence numbers, can be enabled/disabled. - -Protocol that shall be supported: - -- ESP (IETF RFC 4303 [31], as profiled by 3GPP TS 33.210 [20]); -- IPsec mode: Tunnel mode; -- for encrypted packets the DSCP (Differentiated Services Code Point) value of the inner packet shall be copied to the outer packet; -- NAT (Network Address Translation) traversal. - -ESP (Encapsulating Security Payload) encryption transforms shall be supported (including authenticated encryption transforms, see also 3GPP TS 33.210 [20], clause 5.3.3). - -ESP authentication transforms shall be supported according to [20], clause 5.3.4. - -IKE endpoint Identification that shall be supported, according to 3GPP TS 33.310 [26], clause 6.2.1b: - -- IP address; -- Fully Qualified domain name (FQDN) (if DNS is supported). - -Authentication that shall be supported: - -- X.509v3 digital certificates provided by a Certificate Authority (CA) solution. - -Authentication that may be supported: - -- Pre-shared Keys. - -NOTE: Use of Pre-shared Keys is not recommended. - -Key exchanges that shall be supported: - -- IKEv2 as defined in IETF RFC 7296 [34], IETF RFC 7427 [81], IETF RFC 7670 [82], IETF RFC 8247 [83], IETF RFC 8983 [84], IETF RFC 9370 [85], profile as described in 3GPP TS 33.310 [26]; -- certificate-based authentication according to 3GPP TS 33.310 [26]; -- certificates according to the profile described by 3GPP TS 33.310 [26]; -- Diffie-Hellman (DH) groups: - - DH group 19. - -Key exchanges that may be supported: - -- Diffie-Hellman (DH) groups: - - DH group 20. - -Implementations may follow recommendations regarding minimum key lengths proposed in BSI TR-02102-1 [i.6] . - -IKEv1 shall not be supported. - -Security Association multiplicity that shall be supported: - -- multiple IKE SAs (multiple IPsec tunnels); -- multiple IPsec SAs; -- multiple IPsec SAs per IPsec tunnel. - -IKE SA(s) and IPsec SA(s) shall be regularly re-established. - -When the full sequence number space of an IPsec SA(s) is used, the transmission for that SA shall stop. - -Dead-Peer-Detection (DPD) shall be supported as defined in [34]. - -Each node shall support a traffic narrowing function for the traffic selector ([34]). If the traffic selector notified from the peer (e.g. Security GW or neighbouring node) is wider than the Local/Remote Address range in the SPD (Security Policy Database) information set on the node side, the peers set the traffic selector values to the narrower range. - -### 4.5.2 Parallel usage of IPsec and other secure transport protocols - -Implementations SHALL support IPsec configuration with one or more dedicated connections in parallel with other secure transport protocols. - -EXAMPLE: It should be possible to run SSH or TLS connections within an IPsec tunnel or in parallel to IPsec tunnel(s). - -### 4.5.3 Responder mode and Initiator/Responder mode support - -Implementations SHALL support a configurable option per IKE Security Association to use "Responder mode" instead of "Responder/Initiator mode". - -Responder mode is applied to IKE SA establishment only. The introduction of "Responder mode" does not change the IKE SA rekeying behavior: Each node shall be able to operate as initiator and responder in IKE\_SA rekeying. - -## 4.6 CMPv2 - -Certificate Management Protocol version 2 (CMPv2) is based on Internet X.509 Public Key Infrastructure (PKI) Certificate Management Protocol (CMP) specified in IETF RFC 4210 [38], IETF RFC 9480 [95], IETF RFC 9481 [96], IETF RFC 4211 [39], and IETF RFC 9045 [97]. - -3GPP TS 33.310 [26] specifies the use of CMPv2 used by base stations to obtain an operator-signed certificate using a secured communication based on the vendor-signed certificate in the base station and a vendor root certificate pre-installed in the CA/RA server. - -Certificates may be installed at initial system initialization or obtained through certificate enrolment with the operators PKI. Certificate enrolment may be supported with the CMPv2 protocol between the Network Element (NE) and the operators CA as defined in 3GPP TS 33.310 [26]. A PNF that supports CMPv2 shall use the CMPv2 profile defined in 3GPP TS 33.310 [26], clause 9.5. The CA/RA server may include the trust anchor for the operator issued certificate and the appropriate certificate chains in the initialization response message. - -## 4.7 OAuth 2.0 - -### 4.7.1 Overview - -The authorization framework described in clause 4.7 of the present document uses the OAuth 2.0 framework as specified in IETF RFC 6749 [35]. It allows the service producers to authorize the requests from service consumers, and the service consumers to obtain authorization credentials ("token endpoint"). - -Interfaces requiring the use of OAuth 2.0 for authorization purposes shall support the functionality according to clause 4.7 of the present document. - -The following clauses have been introduced to guarantee interoperability and align with the existing OAuth 2.0 authorization framework in 3GPP TS 33.501 [29] (i.e., Service Based Architecture). - -### 4.7.2 Basic Parameterization - -#### 4.7.2.1 General - -Client access token authorization grants shall be supported with type Client Credentials Grant, as described in IETF RFC 6749 [35], section 4.4. Mutual TLS authentication, as specified in the present document (clause 4.2.1), is the mechanism selected by O-RAN for this security procedure. - -In addition, still aligned with Client Credential Grant as described in IETF RFC 6749 [35], section 4.4, Client Id and Client Secret may be supported for client authentication. In this case, one-way TLS may be used (certificate on server side). - -Access tokens shall be JSON Web Tokens (JWT) as described in IETF RFC 7519 [36], IETF RFC 8725 [93] and IETF RFC 7797 [94], and shall be secured with digital signatures based on JSON Web Signature (JWS) as described in IETF RFC 7515 [37]. - -The 'scope' attribute, as described in IETF RFC 6749 [35], section 3.3, shall be used to specify the allowed services per type of service producer. A more granular level of authorization may be defined by adding additional scope information with the token (e.g., to authorize specific operations, or access to particular resources or datasets), which requires verification by the service producer. - -The 'expires\_in' attribute, as described in IETF RFC 6749 [35], section 4.2.2 and 5.1, shall be used to specify the lifetime in seconds of an access token. - -OAuth 2.0 roles, as defined in IETF RFC 6749 [35], section 1.1, are as follows: - -- OAuth 2.0 authorization server: new security function in O-RAN architecture; or provided by existing OAuth 2.0 infrastructure in the network. -- OAuth 2.0 client: every API service consumer in O-RAN system (e.g., rApp, xApps) -- OAuth 2.0 resource owner/server: every API service producer in O-RAN system (e.g., Near-RT RIC platform) - -#### 4.7.2.2 Registration process - -OAuth 2.0 resource servers (API service producers) shall be registered with the OAuth 2.0 authorization server. Service producers may include additional scope information related to specific allowed service operations and resources per client type. - -Before initiating the authorization protocol, OAuth 2.0 clients shall be registered with the OAuth 2.0 authorization server. To achieve that, information about the service consumer instance and its type shall be made available in the OAuth 2.0 authorization server. The registration process is subject to implementation procedures of the operator, with the following consideration on authentication procedure: - -- OAuth 2.0 clients shall be able to authenticate securely with the authorization server and client type shall be "confidential" as specified in IETF RFC 6749 [35], section 2.1. -- Strong authentication mechanisms based on digital certificates shall be supported. - -In addition, a client authentication mechanism based on Client Id and Client Secret may be supported. - -#### 4.7.2.3 Access Token request process - -##### 4.7.2.3.0 Introduction - -After TLS mutual authentication procedure between the OAuth 2.0 client and OAuth 2.0 authorization server, or one-way TLS authentication with server certificate and client authentication based on Client Id and Client Secret has been executed, the authorization server exposes a 'Token Endpoint' where the Access Token request service can be requested by OAuth 2.0 client. - -The following procedure depicts the procedure of the OAuth 2.0 client to obtain an access token from the OAuth 2.0 authorization server. - -![Sequence diagram of the Access Token request process. It shows three steps: 1. OAuth 2.0 Client sends an AccessToken_Get Request to the OAuth 2.0 Authorization Server. 2. The server checks if the client is authorized and generates an access token if so. 3. The server sends an AccessToken_Get Response back to the client.](a734898ce18e972938949637c32a34f4_img.jpg) - -``` - -sequenceDiagram - participant Client as OAuth 2.0 Client - participant Server as OAuth 2.0 Authorization Server - Note right of Server: 2. Check whether the client (API service consumer) is authorized. If client is authorized, generate an access token. - Client->>Server: 1. AccessToken_Get Request (Expected service name(s) and producer type, client type, client id, ...) - Server-->>Client: 3. AccessToken_Get Response (expiration time, access_token) - -``` - -Sequence diagram of the Access Token request process. It shows three steps: 1. OAuth 2.0 Client sends an AccessToken\_Get Request to the OAuth 2.0 Authorization Server. 2. The server checks if the client is authorized and generates an access token if so. 3. The server sends an AccessToken\_Get Response back to the client. - -**Figure 4.7-1: Access Token request process** - -The OAuth 2.0 client shall request an access token from the OAuth 2.0 authorization server. For this operation the client shall send an HTTP POST request to the authorization server ('Token endpoint'), as described in IETF RFC 6749 [35], clause 3.2. The message, i.e., the body of the HTTP POST request, shall include the identifier of the client instance making the request, the 'scope' parameter indicating the expected services, and optionally additional scope information with more granular information about resources and operations on the resources, and optionally the type of client ('confidential') and the expected OAuth 2.0 resource owner/server. The message may include information referring to instance(s) of specific resource owner(s)/server(s) as well, if required. - -##### 4.7.2.3.1 Server requirements - -- The OAuth 2.0 authorization server shall verify that the input parameters in the access token (e.g., client type) match with the corresponding ones in the public certificate of the client, or those in the client profile previously registered. -- If the client is authorized, the authorization server shall generate an access token with appropriate scope field as defined in IETF RFC6749 [35], sections 3.3 and 4.2.2. -- The authorization server shall digitally sign the generated access token based on a private key as described in IETF RFC 7515 [37]. If the client is not authorized, the Authorization server shall not issue an access token to that client. If the authorization is successful, the Authorization server shall send the access token to the client ('200 OK'), otherwise it shall reply based on OAuth 2.0 error response defined in IETF RFC 6749 [35]. -- The success response shall include the lifetime for the token in the expires\_in field, as defined in IETF RFC 6749 [35], sections 4.2.2 and 5.1. -- The response shall include information to identify the resource owner(s)/server(s) if they differ from the related information included in the token request. - -#### 4.7.2.4 Service access request based on token verification - -Once the client is in possession of a valid access token, it may proceed with the request of service access towards the service producer (OAuth 2.0 resource owner/server). - -![Sequence diagram showing service access request based on token verification. It involves an OAuth 2.0 Client and an OAuth 2.0 Resource Owner/Server. The client sends a service request with an access token. The server verifies the token's integrity and claims, and if successful, executes the service. Finally, the server sends a service response back to the client.](5445597cceefaca1ac89e710fe339325_img.jpg) - -``` - -sequenceDiagram - participant Client as OAuth 2.0 Client - participant Server as OAuth 2.0 Resource Owner/Server - Note right of Server: 2. Verify integrity and claims in the access token. If successful, execute the requested service - Client->>Server: 1. Service request (access token) - Server-->>Client: 3. Service response - -``` - -Sequence diagram showing service access request based on token verification. It involves an OAuth 2.0 Client and an OAuth 2.0 Resource Owner/Server. The client sends a service request with an access token. The server verifies the token's integrity and claims, and if successful, executes the service. Finally, the server sends a service response back to the client. - -**Figure 4.7-2: Service access request based on token verification** - -1. The OAuth 2.0 client requests service from the OAuth 2.0 resource owner/server. The OAuth 2.0 client shall include the access token in the request. The OAuth 2.0 client and OAuth 2.0 resource owner/server shall authenticate each other via mutual TLS, as defined in the present document (clause 4.2.1). In addition, one-way TLS authentication with certificate only on server side may be supported, as defined in the clause 4.2.1. -2. The OAuth 2.0 resource owner/server shall verify the token: - - i. It ensures the integrity of the token by verifying the signature using the OAuth 2.0 authorization server's public key. - - ii. It ensures the validity period of the token by checking that the validity period in the expires\_in attribute has not been exceeded. - - iii. If the integrity check is successful and the token is within the validity period, the OAuth 2.0 resource owner/server shall verify the claims. -3. If the verification is successful, the OAuth 2.0 resource owner/server shall execute the requested service and respond back to the OAuth 2.0 client. Otherwise, it shall send a proper error response. If the HTTP protocol is used, that error response shall be based on the OAuth 2.0 error response defined in IETF RFC 6749 [35]. - -### 4.7.3 OAuth2.0 Access token API for O-RAN Elements and interfaces - -#### 4.7.3.1 Introduction - -This API allows the API Consumer to request an access token based on the procedures for "Access Token request process" as defined in clause 4.7.2.3. - -The API version number format shall follow the definitions in 3GPP TS 29.501 [77], clause 4.3.1.1. The MAJOR version field shall be 1, the MINOR version field shall be 0 and the PATCH version field shall be 0. Consequently, the URI path segment shall be set to "v1". - -The API is under development and consequently the API version shall include the pre-release version "alpha.1". - -For the general token endpoint for O-RAN RESTful service APIs, the URI structure should follow the provisions specified below, with the resource URI variable set to "oauth2". - -The resources and methods overview of the access token API are addressed in Table 4.7-1 and shown in Figure 4.7-3. - -**Table 4.7-1: Resources and methods overview of the Access Token API** - -| Resource Name | Resource URI | HTTP method | Service Operation | -|---------------|--------------|-------------|----------------------| -| Access Token | .../token | POST | Access token request | - -{apiRoot}/oauth2/ - -![Diagram showing the resource structure for an access token. A line from the text '{apiRoot}/oauth2/' leads to a box containing '/token'.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) - -``` - -graph LR - Root["{apiRoot}/oauth2/"] --> Token["/token"] - -``` - -Diagram showing the resource structure for an access token. A line from the text '{apiRoot}/oauth2/' leads to a box containing '/token'. - -Figure 4.7-3: Resource structure for access token - -#### 4.7.3.2 Service operations for access token request - -The service operation is defined in IETF RFC 6749 [35] and represented in Figure 4.7-4. - -In the present document, only the use of the "Client credentials grant type" (see IETF RFC 6749 [35], sections 1.3.4 and 4.4) is supported. - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber - -participant "API Consumer" as AC -participant " Authorization Server " as AS - -AC->>AS: POST .../token (AccessTokenReq) -AS->>AS: validate-credentials - -alt Success -AS->>AC: 200 Ok (AccessTokenRes) -else Failure -AS->>AC: 400 Bad Request (AccessTokenErr) -end - -``` - -![Sequence diagram showing the interaction between an API Consumer and an Authorization Server for an access token request. The sequence starts with a POST request from the consumer to the server. The server then performs a 'validate-credentials' self-call. An 'alt' block labeled '[Success]' contains a 200 OK response, while an 'alt' block labeled '[Failure]' contains a 400 Bad Request response.](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant Authorization Server - Note right of Authorization Server: 2 validate-credentials - alt Success - Note right of Authorization Server: 3 200 Ok (AccessTokenRes) - else Failure - Note right of Authorization Server: 4 400 Bad Request (AccessTokenErr) - end - -``` - -Sequence diagram showing the interaction between an API Consumer and an Authorization Server for an access token request. The sequence starts with a POST request from the consumer to the server. The server then performs a 'validate-credentials' self-call. An 'alt' block labeled '[Success]' contains a 200 OK response, while an 'alt' block labeled '[Failure]' contains a 400 Bad Request response. - -**Figure 4.7-4: Access Token Request and Response** - -1. The API Consumer sends an HTTP POST request to authorization server to request the access token from the Token Endpoint. -2. The authorization server authenticates the client as specified in clause 4.4.2 of IETF RFC 6749 [35] and validates the request as implied in clause 4.4.3 of IETF RFC 6749 [35]. -3. On success, the authorization server returns a "200 OK" HTTP response along with an access token response structure. -4. On failure, the authorization server returns a "400 Bad Request" HTTP response and the message content contains additional error information. - -##### 4.7.3.2.1 Resource Standard Methods - -The POST method and its request and response parameters are specified in IETF RFC 6749 [35]. - -This information is reproduced using the O-RAN scheme for RESTful API definitions below, with the request data structure represented in Table 4.7-2, the response data structures and response codes represented in Table 4.7-3 and the HTTP headers represented in Table 4.7-4. - -**Table 4.7-2: Data structures supported by the POST request body on this resource** - -| Data Type | P | Cardinality | Description | -|----------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------| -| AccessTokenReq | M | 1 | As content specified in IETF RFC 6749 [35]. See also clause 4.7.3.1.2.1. The content type is " application/x-www-form-urlencoded". | - -**Table 4.7-3: Data structures supported by the POST Response Body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|-----------------|------------------------------------------------------------------------------------------------------------------| -| AccessTokenRsp | M | 1 | 200 OK | As content specified in IETF RFC 6749 [35]. See also clause 4.7.3.1.2.2. The content type is "application/json". | -| AccessTokenErr | M | 1 | 400 Bad request | As content specified in IETF RFC 6749 [35]. See also clause 4.7.3.1.2.3. The content type is "application/json". | - -**Table 4.7-4: Headers supported by the 200 Response Code on this resource.** - -| Name | Data type | P | Cardinality | Description | -|---------------|-----------|---|-------------|---------------------------------------------| -| Cache-control | string | M | 1 | As content specified in IETF RFC 6749 [35]. | -| Pragma | string | M | 1 | As content specified in IETF RFC 6749 [35]. | - -##### 4.7.3.2.2 Data Model - -The following clauses represent the message content to be used by the OAuth2.0 access token API as O-RAN data types in line with the provisions in IETF RFC 6749 [35]. - -###### 4.7.3.2.2.1 Data type: AccessTokenReq - -The AccessTokenReq data type represents an access token request to the authorization server. Its attributes are defined by IETF RFC 6749 [35] and reproduced in Table 4.7-5. - -**Table 4.7-5: Definition of type AccessTokenReq** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------| -| grant_type | string | M | 1 | As content specified in IETF RFC 6749 [35], section 4.4.2.

In the present document, the only allowed value shall be "client_credentials". | -| client_id | string | C | 0..1 | As content specified in IETF RFC 6749 [35]. See NOTE. | -| client_secret | string | C | 0..1 | As content specified in IETF RFC 6749 [35]. See NOTE. | -| scope | string | O | 0..1 | As content specified in IETF RFC 6749 [35], section 4.4.2. | -| NOTE: As specified in IETF RFC 6749 [35], section 2.1, there are two options for authenticating the clients to the authorization server: HTTP basic authentication and access token request message content. The attributes "client_id" and "client_secret" shall be absent if HTTP basic authentication is used to convey the client credentials as per IETF RFC6749 [35], section 2.3.1, and shall be present otherwise. | | | | | - -###### 4.7.3.2.2.2 Data type: AccessTokenRsp - -The AccessTokenRsp data type represents an access token response from the authorization server. Its attributes are defined by IETF RFC 6749 [35] and reproduced in Table 4.7-6. - -**Table 4.7-6: Definition of type AccessTokenRsp.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-----------|---|-------------|----------------------------------------------------------| -| access_token | string | M | 1 | As content specified in IETF RFC 6749 [35], section 5.1. | -| token_type | string | M | 1 | As content specified in IETF RFC 6749 [35], section 5.1. | -| expires_in | integer | M | 0..1 | As content specified in IETF RFC 6749 [35], section 5.1. | -| scope | string | O | 0..1 | As content specified in IETF RFC 6749 [35], section 5.1. | - -###### 4.7.3.2.2.3 Data type: AccessTokenErr - -The AccessTokenErr data type represents an access token error response from the authorization server. Its attributes are defined by IETF RFC 6749 [35] and reproduced in Table 4.7-7. - -**Table 4.7-7: Definition of type AccessTokenErr** - -| Attribute Name | Data type | P | Cardinality | Description | -|-------------------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| error | string | M | 1 | As content specified in IETF RFC 6749 [35], section 5.2, the following values are valid: "invalid_request", "invalid_client, invalid_grant", "unauthorized_client", "unsupported_grant_type", "invalid_scope." | -| error_description | string | O | 0..1 | As content specified in IETF RFC 6749 [35], section 5.2. | -| error_uri | string | O | 0..1 | As content specified in IETF RFC 6749 [35], section 5.2. | - -#### 4.7.3.3 Service operations for Service access request - -The service operation is as follows: - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber - -participant "API Consumer" as AC -participant " API Producer " as AP - -AC->>AP: GET.../(access_token) -AP->>AP: validate(access_token) - -alt Authorized -AP->>AC: 200 Ok -else Access token invalid -AP->>AC : 401 Unauthorized -else Insufficent scope -AP->>AC : 403 Forbidden -else Other error response -AP->> AC: 4xx/5xx Error response -end -``` - -![Sequence diagram showing service request using access token. Lifelines: API Consumer and API Producer. The sequence starts with a GET request for an access token, followed by a self-call to validate it. An 'alt' block titled '[Authorized]' contains four possible responses: 200 Ok, 401 Unauthorized, 403 Forbidden, and 4xx/5xx Error response.](552265bdbcf6d43d341fd018a9076269_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note right of API Producer: 2 validate(access_token) - alt Authorized: 200 Ok - else Access token invalid: 401 Unauthorized - else Insufficient scope: 403 Forbidden - else Other error response: 4xx/5xx Error response - -``` - -Sequence diagram showing service request using access token. Lifelines: API Consumer and API Producer. The sequence starts with a GET request for an access token, followed by a self-call to validate it. An 'alt' block titled '[Authorized]' contains four possible responses: 200 Ok, 401 Unauthorized, 403 Forbidden, and 4xx/5xx Error response. - -**Figure 4.7-5: Service request using access token** - -1. The API Consumer shall access the protected resources by using access token for the service API being invoked as shown in Figure 4.7-5. The access token shall be included in the request as an HTTP header field as specified in IETF RFC 6750 [78], section 2.1. -2. The API Producer shall validate the access token and ensure that it has not expired and that its scope covers the requested resource. -3. If the token validation is successful, the API Producer shall allow access for the actual resource with the actual request and its parameters. The API Producer shall return the HTTP response as defined for the service API being invoked. -4. If the token validation fails due to invalid token or expired token, the API Producer shall return "401 Unauthorized" in line with the provisions in IETF RFC 6750 [78], section 3. -5. If the token validation is failed due to insufficient access rights to access the resource, the API Producer shall return "403 Forbidden" in line with the provisions in IETF RFC 6750 [78], section 3. -6. In case of any other error, the API Producer shall return the appropriate error as defined by the service API. - -## 4.8 LDAP - -### 4.8.1 General requirements - -LDAP, or the Lightweight Directory Access Protocol, is a widely adopted, unbiased standardized communication protocol that enables the interaction and management of distributed directory data via an IP network. This protocol plays a crucial part in the creation of both intranet and internet applications, as it facilitates the sharing of detailed information about various resources, such as users, systems, networks, services, and applications, across the entire network. - -O-RAN interfaces that implement Lightweight Directory Access Protocol (LDAP) shall: - -- support LDAP version 3 as specified in [74] and LDAP with StartTLS as specified in [75]. -- not support previous versions of LDAP. - -StartTLS operation shall be initiated prior to any other LDAP operation and all LDAP data shall be sent only after successful establishment of TLS connection. Requirements for TLS in clause 4.2 shall apply. - -## 4.9 MACsec - -### 4.9.1 General requirements - -The O-RAN interfaces that implement authentication, confidentiality and integrity using MACsec shall support MACsec capabilities according to IEEE Std 802.1AE-2018 [79]. - -### 4.9.2 MACsec Profile - -The O-RAN interfaces using MACsec shall support the mandatory cipher suites as specified in IEEE Std 802.1AE-2018 [79] clause 14, Table 14-1—MACsec Cipher Suites. - -# 5 Cryptographic operations - -Table 5-1 outlines the main cryptographic operations involved in the protection of (1) application packages for ensuring their integrity, authenticity and confidentiality (for sensitive artifacts) during delivery, onboarding, and instantiation phases, (2) the communication channel over O-RAN interfaces in terms of authenticity, confidentiality and integrity, and (3) the stored assets within O-RAN system. It contains the allowed list of algorithms, key sizes and standards according to BSI [i.6] , NIST [40], [48] and [i.9] cryptographic guidelines. - -Table 5-1: Cryptographic Operations for O-RAN - -| Cryptographic operations | Algorithms | Key sizes | Applicable standards | Usage examples | Note | -|---------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------|--------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| -| Signature generation and verification | RSASSA-PSS
RSA_PKCS1_V1_5 | >= 2048-bits | FIPS 186-5 [42] | For ensuring the integrity and authenticity of application packages during delivery, onboarding, and instantiation phases | Existing code should use PKCS #1 v1.5 padding mode for compatibility only. Implementations may not use null padding. | -| Signature generation and verification | ECDSA using NIST-approved curves (P-256, P-384, or P-521) | >= 256-bits | FIPS 186-5 [42], SP 800-186 [i.8] | | Parameter key size for DSA shall not allow the following combination: Bit lengths of L and N parameters L = 2048, N = 224 (BSI TR-02102-1 [i.6] ) | -| Symmetric Encryption/Decryption | AES_128, AES_192 and AES_256 | 128, 192 and 256 bits | FIPS 197 [44], SP 800-38 [i.7] (operation modes) | For ensuring the confidentiality of data | | -| Asymmetric Encryption/Decryption | RSAES-OAEP | >= 2048-bits | IETF RFC 8017 [50] | | | -| Hashing | SHA-2 family (SHA- 224, SHA-256, SHA-384, SHA-512, SHA-512/224 and SHA-512/256)
SHA-3 family (SHA3-224, SHA3-256, SHA3-384, and SHA3-512) | N/A | FIPS 180 [119] for SHA2
FIPS 202 [47] for SHA 3 | For ensuring the integrity of data | | -| Random Number Generation (RNG) | DRBGs (CTR_DRBG (AES), HMAC_DRBG (SHA-256), Hash_DRBG (SHA-256)) | N/A | NIST SP 800-90A [i.12]
NIST SP 800-90B [i.13]
NIST SP 800-90C [i.14] | For generating cryptographic keys for encryption and digital signatures.
For creating random nonces for secure operations. | | -| | System RNG
EXAMPLE: Linux getrandom(), /dev/urandom | N/A | For Linux: BSI [i.16] | For generating unique instance IDs.
For providing secure entropy to seed DRBGs. | | -| Password hashing with salting | Argon2id
scrypt
PBKDF2 | Salt length should be >=128 bits | Argon2id: RFC 9106 [121]
scrypt: RFC 7914 [122]
PBKDF2: NIST SP 800-132 [i.17]
See OWASP recommendations [i.18] | For securely storing passwords | Salts are stored in plaintext alongside the hash.

At least one of the specified algorithms shall be supported. | - -The signature operation shall involve X.509-based PKI certificates [74]. - -The following recommendations should be considered: - -- For the protection of cryptographic keys, Hardware Security Modules, or HSMs, should be used. - - Along with HSMs, the principle of least privilege shall be used to protect keys from unauthorized access. -- In case a legacy system does not support ECDSA, RSA signing algorithms should be used instead. Otherwise, the use of the Elliptic curve signing algorithms is recommended. -- If libraries or frameworks are in use that do not support PSS padding scheme, one of the RSA PKCS1 algorithms should be used instead. Otherwise, the use of one of the RSA PSS algorithms is recommended. -- In general, the largest key size available for an algorithm family should be used: - - For RSA, the largest supported key size is 4096 bits. - - For ECDSA, the largest supported key size is 512 bits. - - For AES, the largest supported key size is 256 bits. - -# 6 Secure File Transfer protocols - -## 6.1 General - -File Transfer management is required in several O-RAN use cases, e.g. for export of log files. - -An O-RAN architectural element that implements file management shall support at least one of these secure file transfer protocols: SFTP, FTPES and HTTPS. This is aligned with, for example, how 3GPP specifies File Management in [67] and [68]. - -SFTP is authenticated with username/password, SSH keys or X.509 certificates. FTPES is authenticated with X.509 certificates. HTTPS is mutually authenticated with X.509 certificates. - -## 6.2 SFTP - -### 6.2.1 General Requirements - -O-RAN architectural elements that implement secure file transfer using SFTP shall: - -- support secure connection and authentication using SSHv2 Authentication Protocol as defined in IETF RFC 4252 [2], IETF RFC 8308 [107], IETF RFC 9519 [80], IETF RFC 8332 [108] with all O-RAN specific requirements from clause 4.1 in the present document; -- support SFTPv3 as the SFTP Industry Best Practice [65]. - -## 6.3 FTPES - -### 6.3.1 General Requirements - -O-RAN architectural elements that implement secure file transfer using FTPES shall: - -- support secure connection and authentication using TLS with all O-RAN specific requirements from clause 4.2 in the present document; -- support FTPES as defined in IETF RFC 4217 [66], and IETF RFC 8996 [112]. - -## 6.4 HTTPS - -### 6.4.1 General Requirements - -O-RAN architectural elements that implement secure file transfer using HTTPS shall: - -- support secure connection and authentication using TLS with all O-RAN specific requirements from clause 4.2 in the present document; -- support HTTPS as defined in [69]. - -# Annex A (normative): OpenAPI specifications - -## A.1 OAuth2.0 API - -### A.1.1 Introduction - -The Open API for the OAuth2.0 Access Token API specified in clause A.1.2 is based on the API definitions in clause 4.7.3.4. - -### A.1.2 OAuth 2.0 Access Token API - -``` - -openapi: 3.0.3 -info: - title: OAuth 2.0 Access Token API - version: 1.0.0 - description: | - API for OAuth 2.0. - © 2024, O-RAN ALLIANCE. - All rights reserved. -externalDocs: - description: O-RAN.WG11.SecProtSpecs-R003-v10.00 - url: https://www.o-ran.org/specifications -servers: - - url: '{apiRoot}/oauth2/v1' - variables: - apiRoot: - description: apiRoot as defined in in clause 4.4.1 of 3GPP TS 29.501 - default: https://example.com -paths: - /token: - post: - description: Token endpoint - operationId: AccessTokenRequest - tags: - - Access Token Request - requestBody: - required: true - content: - application/x-www-form-urlencoded: - schema: - $ref: '#/components/schemas/AccessTokenReq' - responses: - '200': - description: Success case 200 OK - content: - application/json: - schema: - $ref: '#/components/schemas/AccessTokenRsp' - headers: - Cache-Control: - $ref: '#/components/headers/cache-control' - Pragma: - $ref: '#/components/headers/pragma' - '400': - description: Error in the Access Token Request - content: - application/json: - schema: - $ref: '#/components/schemas/AccessTokenErr' -components: - schemas: - AccessTokenReq: - description: Contains information related to the access token request - type: object - properties: - grant_type: - -``` - -``` - - description: Represents the Client Credentials grant type - enum: [ client_credentials ] - type: string - client_id: - description: >- - Represents the identity assigned to the client configured in the - authorization server - type: string - client_secret: - description: >- - Represents the secret assigned to the client configured in the - authorization server - type: string - scope: - description: Represents the scope of the access request - type: string - required: - - grant_type -AccessTokenRsp: - description: Contains information related to the access token response - type: object - properties: - access_token: - description: Represents the access token issued by the authorization server - type: string - token_type: - $ref: '#/components/schemas/token_type' - expires_in: - description: Represents the lifetime in seconds of the access token - type: integer - scope: - description: Represents the scope of the access request - type: string - required: - - access_token - - token_type -token_type: - description: As described in clause 6.1.1 of IETF RFC 6750 - type: string - enum: - - Bearer -AccessTokenErr: - description: Error returned in the access token response message - type: object - properties: - error: - type: string - enum: - - unauthorized_client - - unsupported_grant_type - - invalid_request - - invalid_scope - - invalid_client - - invalid_grant - error_description: - type: string - error_uri: - type: string - required: - - error -headers: - cache-control: - required: true - schema: - type: string - enum: - - no-store - pragma: - required: true - schema: - type: string - enum: - - no-cache - -``` - -# Annex B (informative): Example of TLS entity Certificate Profile for NETCONF authentication - -The purpose of the Annex is to provide an example of a TLS entity certificate profile which is used for NETCONF authentication. - -As specified in clause 6.4.2 of the O-RAN Working Group 4 Management Plane Specification [6], if authentication is based on X.509 certificates, then for the purposes of user authentication, the mapping between certificates and **user-name** is provided by the subjectAltName field of the X.509 certificate, which means that the user name is coded in the subjectAltName. The username is determined from the subjectAltName using the rules as specified in RFC 7589 [i.11]. For the purposes of NETCONF server authentication, RFC 7589 [i.11] specifies server identity as specified in clause 4 of RFC 9525 [98]. An example of a default user account for account-type CERTIFICATE is map type "san-rfc822-name" with a rfc822-name of "oranuser@o-ran.org". - -**Table B-1** - -| O-RAN TLS Certificate Profile | | | | -|-------------------------------|---------------------------------------------------------------------------------------------|-------------|----------------------------------------------------------------------| -| Field | Value | | | -| version | 3 | | | -| serial Number | Unique Positive Integer (up to 20 octets) assigned by the issuing CA as per RFC 5280 [64]. | | | -| issuer | EXAMPLE: (C=), O=, CN=< Some distinguishing name>. | | | -| subject | EXAMPLE: (C=), O=, CN=. | | | -| validity | 1 year or less | | | -| signature | See 3GPP TS 33.310 [26], clause 6.1.1 for the list of supported signature algorithms. | | | -| subjectPublicKey Info | See 3GPP TS 33.310 [26], clause 6.1.1 for the list of supported public key types. | | | -| Extensions | Mandatory | Criticality | Value | -| keyUsage | TRUE | TRUE | digitalSignature for TLS clients and servers | -| extendedKeyUsage | FALSE | FALSE | id-kp-clientAuth TLS clients | -| | | | id-kp-serverAuth for TLS servers | -| | | | Entities that may be both client and server will have both OIDs set. | - -| | | | | -|------------------------|-------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| authorityKeyIdentifier | FALSE | FALSE | This is same as the subjectKeyIdentifier of the issuer's certificate. CA utilizes the method as defined in clause 2 of IETF RFC 7093 [60]. | -| subjectKeyIdentifier | FALSE | FALSE | This is calculated by the issuing CA utilizing method as defined in clause 2 of IETF RFC 7093 [60]. | -| subjectAltName | FALSE | FALSE | rfc822Name | -| cRLDistributionPoint | TRUE | FALSE | distributionPoint | -| | | | According to IETF RFC 5280 [64] this indicates if the CRL is available for retrieval using access protocol and location with HTTP URI or LDAP. | -| authorityInfoAccess | FALSE | FALSE | id-ad-caIssuers

According to IETF RFC 5280 [64] id-ad-caIssuers describes the referenced description server and the access protocol and location, for example, using one or multiple HTTP and/or LDAP URIs. The referenced CA issuers description is intended to aid certificate users in the selection of a certification path that terminates at a point trusted by the certificate user | -| | | | id-ad-ocsp | -| | | | According to IETF RFC 5280 [64] id-ad-ocsp defines the location of the OCSP responder using HTTP URI. | - -# Annex (informative): Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2025.11.25 | 14.00 | Published as Final version 14.00 | -| 2025.11.25 | 13.02 | Updated copyright notices, merged ATT.AO-5017, ATT.AO-5018, NOK-0341 | -| 2025.10.01 | 13.01 | Merged NOK-0316, NOK.AO-0317 | -| 2025.07.11 | 13.00 | Published as Final version 13.00 | -| 2025.07.10 | 12.01 | Added SYM-0086, ATT.AO-5006, NOK-0291 and ERI-0230; fixed editorial errors | -| 2025.03.23 | 12.00 | More editorial fixes; Published as Final version 12.00 | -| 2025.03.21 | 11.03 | Added ACN.AO-0006, RMI.AO-0035, ACN-0009, ACN.AO-0007, SYM-0083, NOK-0246, ACN-0010, NOK.AO-0257, NOK-0259, NOK-0264, NOK-0265, ACN-0012, ACN-0013, ACN.AO-0014, ACN.AO-0015 | -| 2025.03.19 | 11.02 | Updated formatting to align with latest TS template (v3.0) | -| 2025.02.18 | 11.01 | Updated formatting, added NOK-0232, NOK-0233 | -| 2024.11.27 | 11.00 | More editorial fixes
Published as Final version 11.00 | -| 2024.11.27 | 10.04 | Disabled automatic update of styles in the document developer settings | -| 2024.11.27 | 10.03 | Further editorial changes | -| 2024.11.27 | 10.02 | Several minor editorial- and format corrections | -| 2024.11.27 | 10.01 | Added DTAG-0013, ATT.AO-0061, ACN.AO-0004 and ERI-0172 | -| 2024.07 | 10.00 | Published as Final version 10.00 | -| 2024.03 | 09.00 | Certificate Profile for O-RAN TLS entity
Reference Update
Published as Final version 09.00 | -| 2023.11 | 08.00 | Secure file transfer protocols added
SSH Update on no root remote login
ssh-ed448 changed to optional
Reference on SSH added
Published as Final version 08.00 | -| 2023.07 | 07.00 | Editorial alignments
TLS entity certificate profile
CMPv2 profile update
Introduction of one-way TLS authentication for OAuth2.0
Published as Final version 07.00 | -| 2023.03 | 06.00 | Cryptographic operations update
Published as Final version 06.00 | -| 2022.11 | 05.00 | TLS Cipher update
Published as Final version 05.00 | -| 2022.07.20 | 04.00 | Addition of CMPv2
Update of O-Cloud Image protocols
Addition of mTLS
Update of OAuth 2.0
Published as Final version 04.00 | -| 2021.11.08 | 03.00 | Update the O-RAN security protocols and specifications to include mandatory support for TLS 1.3
Published as Final version 03.00 | -| 2021.07.05 | 02.00 | Addition of DTLS and IPsec requirements.
Alignment of TLS 1.2 and TLS 1.3 profiles with 3GPP TS 33.210.
Typographical changes.
Published as Final version 02.00 | -| 2021.04.01 | 01.00 | Initial version of the document with requirements for TLS and SSH.
Published as Final version 01.00 | \ No newline at end of file diff --git a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 4b94da934e2c8c85c0123640346015b174f8dc14..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:53785b160680d7d75d469ea49f0daf5b5a3522fbee704e81dcd409934e1d112e -size 4601 diff --git a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/226f5e462c99b71e08dc9abaa5ae260c_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/38222c3ae003223a67635bfcc6950fbb_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/3f727e6c0d6658bc53ea10905c4561dd_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/4a04896dfb569893fba50729314024f5_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/4f8349df2ca48959fefb7c42b2bc375e_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/5445597cceefaca1ac89e710fe339325_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/5445597cceefaca1ac89e710fe339325_img.jpg deleted file mode 100644 index 87ad77e26074aa42b34a7a483bf6f07223a832ec..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/5445597cceefaca1ac89e710fe339325_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:504fa2efdb7fdeb0713586aea9efa872a390ebf20062764fde1b3680c2f6d6bf -size 32125 diff --git a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/552265bdbcf6d43d341fd018a9076269_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/552265bdbcf6d43d341fd018a9076269_img.jpg deleted file mode 100644 index 66b9e043abee8ab4545a3d3bdd08b75a3ec90f95..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/552265bdbcf6d43d341fd018a9076269_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5beff08799dfa30fdc0bb22cee7c362ccd49a2865e0c5c8bc13099440ef28f7 -size 60965 diff --git a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/79e1709a7317ead45379cbb8ff3ba802_img.jpg deleted file mode 100644 index eae21598da5b92a0f2b8e88cfaa22c251177e35f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/79e1709a7317ead45379cbb8ff3ba802_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f0d7aaa71be2b8c9ebe99872de94ab2c629b8af9d2b0e7a76f56ee54fbae17a2 -size 6719 diff --git a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/81b34087cd6755a80f84a70cf28fba82_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/83ee9f10bd3636e192d68decf7f04cec_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/854df8ad60507803253274673f9062cf_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 82827af191c934857f3a5a97842fa19fb4aa5978..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:54f690c723a011f67b244eeda5cca1f67e7a7784e122d72a637cea1ca968c8f4 -size 4531 diff --git a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/8d129c93d18909f0643766f372e9ebf6_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/a28ab03366399b5e0a61445bc57e3724_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/a734898ce18e972938949637c32a34f4_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/a734898ce18e972938949637c32a34f4_img.jpg deleted file mode 100644 index 4bb96aa2f733a308422a332730cdb5648e1a31cb..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/a734898ce18e972938949637c32a34f4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:01d0d7456eaa506e97e6fa65db70aa5180ff871d88bc457f37024f679dcc798a -size 23210 diff --git a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index d83db742d4f4a5686db46fba51a8978b3d55350c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:118a75afce84048742b1a083a2cf669dbfd2b8c692dcd080b99beca4ce23ac9f -size 4538 diff --git a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg deleted file mode 100644 index 76438aa8146538d430c50b6b05bdaa5121ec796c..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4f77fb5268b0986bd2a8ae4b91f07287f07fd1e7f61796c76bc720d36d58b773 -size 49706 diff --git a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/e345315706e3fe633bb6d593246c01bf_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/e87df69ebd4cd2dbbf6749079e6c057a_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/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000 --- a/files/WG11/O-RAN.WG11.TS.SecProtSpec.0-R005-v14.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/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/doc.md b/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/doc.md deleted file mode 100644 index a9fe109ab6fbc734bb3094f50473673dbc944e30..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/doc.md +++ /dev/null @@ -1,292 +0,0 @@ - - -# --- O-RAN Work Group 2 - -# Study on Impact of Decoupled SMO on Non-RT RIC Architecture and Interfaces - -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..... 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..... 4 -- 3.1 Terms..... 4 -- 3.2 Symbols..... 5 -- 3.3 Abbreviations ..... 5 -- 4 Impact analysis of Decoupled SMO..... 5 -- 4.1 WG2 specifications impact analysis..... 5 -- 4.1.1 Non-RT RIC architecture related aspects ..... 5 -- 4.1.2 A1 related aspects ..... 6 -- 4.1.3 R1 related aspects ..... 7 -- 4.1.4 Use cases and requirement related aspects ..... 9 -- 4.2 Recommendations ..... 9 -- Annex: Change history/Change request (history)..... 11 - -# Foreword - -This Technical Report (TR) has been produced by WG2 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 study aimed at exploring the integration of the principles and recommendations of the Decoupled SMO Architecture TR [i.1], into the WG2 specifications. - -# 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] O-RAN.WG1.TR.Decoupled-SMO-Architecture: “O-RAN Decoupled SMO Architecture”. -- [i.2] O-RAN WG1.TS.OAD: “O-RAN Architecture Description” (“OAD”). -- [i.3] O-RAN.WG2.TS.Non-RT-RIC-ARCH: " Non-RT RIC: Architecture". -- [i.4] O-RAN.WG2.TS.A1GAP: "A1 interface: General Aspects and Principles" ("A1GAP"). -- [i.5] O-RAN.WG2.TS.R1GAP: “R1 General Aspects and Principles“ (“R1GAP“). -- [i.6] O-RAN.WG2.TS.R1AP: "Application Protocols for R1 services"("R1AP"). -- [i.7] Void -- [i.8] O-RAN.WG2.TS.Use-Case-Requirements: "Non-RT RIC & A1/R1 Interface: Use Cases and Requirements" ("UCR"). - -# 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the terms apply: **A1-EI**: A1 Enrichment Information**A1-P**: A1 Policy**A1-ML**: A1 Model management**CM**: Configuration management**FM**: Fault management - -**FOCOM**: Federated O-Cloud Orchestration and Management - -**NFO**: Network Functions Orchestration**Non-RT RIC**: Non-Real Time RIC**PM**: Performance management**SMO**: Service Management and Orchestration**SMOS**: SMO service - -## 3.2 Symbols - -Void. - -## 3.3 Abbreviations - -Void. - -# --- 4 Impact analysis of Decoupled SMO - -## 4.1 WG2 specifications impact analysis - -### 4.1.1 Non-RT RIC architecture related aspects - -#### 4.1.1.1 Overview and highlights - -The architecture defined in Non-RT RIC Architecture specification [i.3] provide a functional description of Non-RT RIC and SMO, where reference to SMO functions is given in support of the services exposed over the two open interfaces, i.e. R1 and A1. - -#### 4.1.1.2 Impact analysis - -##### 4.1.1.2.1 Introduction - -In the Decoupled SMO FWID, the standardization of a Service Based Architecture for SMO, as defined in OAD [i.2] aims at ensuring the interoperability between components based on the definition of services instead of functions and interfaces. The new approach, however, does neither change the role of the Non-RT RIC nor introduce non-backward compatibility issues over R1 and A1, being the functions defined in the current Non-RT RIC Architecture specification [i.3] are one-to-one related to the corresponding services, which can now be referred to a SMOS in OAD [i.2]. - -Both Decoupled SMO Architecture TR [i.1] and OAD [i.2] state that grouping of SMOS producers in one SMOF is not subject to specification. - -Moreover, current Non-RT RIC architecture, shows O1, O2 and Open FH M-Plane interface terminations as distinct functions from the functions providing services to Non-RT RIC. With the introduction Decoupled SMO architecture, as described in OAD [i.2] the O1/Open FH M-Plane and O2 interface terminate to RAN NF OAM and NFO/FOCOM SMOS producers, respectively. Hence, Figure 6.1-1 and the definitions of interface terminations should be revised accordingly. - -###### 4.1.1.2.1a Requirements - -The Non-RT RIC Architecture specification [i.3], clause 5.1 defines the requirements for the Non-RT RIC framework. Some of these requirements are defined considering the functional architecture of SMO. The introduction of a service-based architecture for SMO, implies that SMOS related requirements should be analysed and aligned to the decoupled SMO Architectural principles. For example, the requirement REQ-NRTFWK-FUN2 is defined as, - -*The Non-RT RIC framework shall support functionality to allow Service Consumers to discover services.* - -This requirement can be seen as consisting of two sub requirements. - -1. The service management and exposure (SME) services shall support functionality to allow Service Consumers to discover services. -2. For the R1 interface, the R1 interface termination shall enable the SME Service Producers and the SME Service Consumers to exchange messages related to the SME service capabilities that are accessible via the R1 interface. - -In the decoupled SMO context, the 1st sub requirement should be a requirement towards SME SMOS and should be specified in the SME SMOS UCR TS. The 2nd sub requirement is relevant to be specified in the Non-RT RIC Architecture specification [i.3], clause 5.1. - -The 2nd sub requirement could be generalized as below, - -For the R1 interface, the R1 interface termination shall enable the Service Producers and the Service Consumers to exchange messages related to the service capabilities that are accessible via the R1 interface. - -##### 4.1.1.2.2 Conclusions - -Based on the above analysis, the following can be concluded: - -- Non-RT RIC architecture remains consistent with the overarching Decoupled SMO architecture, improving interoperability and enabling a modular approach to service management. -- SMOS (SMO Services) concept should be integrated into the Non-RT RIC Architecture specification [i.3] to ensure it aligns with the Service-Based Architecture (SBA) principles of the Decoupled SMO framework. -- Description of O1/Open FH M-Plane and O2 interfaces and the related services should be adapted to the align with the Decoupled SMO architecture and principles, e.g. by removing the interface termination boxes and refer to the corresponding SMOS producers (RAN NF OAM and NFO/FOCOM). -- The requirements in the Non-RT RIC Architecture specification [i.3], clause 5.1 which are relevant for a SMOS need to be specified in the corresponding SMOS specific UCR TS. -- The requirements relevant for the Non-RT RIC need to be specified in the Non-RT RIC Architecture specification [i.3], clause 5.1. - -### 4.1.2 A1 related aspects - -#### 4.1.2.1 Overview and highlights - -In the Non-RT RIC Architecture specification [i.3], A1 termination function which is anchored function in the Non-RT RIC reference architecture is defined as, - -A1 termination: It enables the Non-RT RIC framework and the Near-RT RIC to exchange messages over the A1 interface. - -However, In the Decoupled SMO Architecture TR [i.1] A1 termination function is neither mentioned nor shown in Fig 6.2.1-1. It's not clear then whether it is consistent with the Non-RT RIC Architecture. - -#### 4.1.2.2 Impact analysis - -##### 4.1.2.2.1 Introduction - -A1 Policy, A1 Enrichment Information and A1-ML Model management (A1-P, A1-EI, A1-ML) services are critical for facilitating interaction between the SMO/Non-RT RIC framework and Near-RT RIC through the A1 interface. The management of policies, enrichment information and ML model ensures that near real-time decisions made at the Near-RT RIC are guided or assisted by the management and orchestration services in the SMO/Non-RT RIC. - -However, there is currently ambiguity about whether producers of these services should be anchored within the Non-RT RIC or be non-anchored (i.e. flexibly deployable as part of the SMO framework or the NonRT RIC framework). - -The introduction of A1 related SMOSs with the exposure of services offered by a function consuming A1 interface services, i.e. A1-P, A1-EI and A1-ML in A1GAP [i.4], does not conflict with the A1 interface specifications and with the role of Non-RT RIC, there is however an inconsistency related to the concept of “A1 termination” anchoring, introduced in Non-RT RIC Architecture specification [i.3]. - -As for SMOS related to other external SMO interfaces, i.e. O1 and O2, it would be straightforward to assume that the A1-related SMOS producer and the termination of A1 interface are tightly coupled. - -The alternative, i.e. introducing a functional separation between the A1 related SMOS producer and the A1 interface termination, would require the definition of an additional interface or reference point between these to ensure interoperability between the two functions. - -Before the introduction of SMOS concept, the only consumers of A1 related services were the rApps. With the introduction of other SMOS, e.g. Service Assurance SMOS, also other SMOS producer may consume A1 related services SMOS to e.g. provide policies to Near RT RIC. For this reason, it seems appropriate to expose A1 related services as individual SMOS, as defined in OAD [i.2] - -Following the analysis given above, in order to confirm the assumption that A1 related functions are not anchored to the Non-RT RIC, it is necessary to revise the concept of A1 termination, possibly aligning to other SMO interfaces like O1 and O2, for example avoiding the term “A1 termination function” and use “A1 interface” or “A1 services consumer/producer” instead. - -##### 4.1.2.2.2 Conclusions - -Based on the above analysis, the following can be concluded: - -- Update the descriptions of “A1 termination” in Non-RT RIC Architecture specification [i.3], remove the box “A1 termination” from the Non-RT RIC architecture and terminate the A1 interface into the “A1 related functions”. Remove the reference to "A1 termination" from clause 8.1 and replace the remaining two occurrences of "A1 termination" with "A1 interface". This will ensure consistency between the concepts “A1 related SMOS” given in OAD and the “A1 related functions” described in Non-RT RIC Architecture TS. - -### 4.1.3 R1 related aspects - -#### 4.1.3.1 Overview and highlights - -The standardization of a Service Based Architecture for SMO, as defined in OAD [i.2] aims at ensuring the interoperability between components based on the definition of services. - -Several SMOS were introduced in OAD [i.2] clause 5.3.1.2.1 to support a service-based architecture in SMO. - -In particular, the scope of SME and DME SMOS have been defined to support service and data exposure to both internal and external SMOS consumers: - -*SME SMOS supports the exposure of other SMOSs, to both internal and external SMOS consumers.* - -*DME SMOS supports the exposure of data produced by SMOS Producers, to both internal and external SMOS consumers.* - -The R1 interface related specifications refer to the services exposed as “R1 services”, since the scope is the service exposure over R1 interface. - -The relationship between R1 services, SMOS and R1 interface has been provided in OAD [i.2]: - -***R1 Services:*** *The SMOS capabilities available for consumption by rApps, and the capabilities produced by rApps, that are accessible via the R1 interface* - -#### 4.1.3.2 Impact Analysis - -##### 4.1.3.2.1 R1 Interface - -The following paragraphs describe the R1 interface (Non-RT RIC Architecture specification [i.3] clause 6.2): - -The R1 interface is a service-based interface via which the R1 services can be consumed and produced. - -The R1 termination enables the R1 Service Producers and R1 Service Consumers to exchange messages via the R1 interface. - -The R1 termination enables the SMO/Non-RT RIC framework and the rApps to exchange messages via the R1 interface, assuming that the R1 service APIs and the rApps are registered with the R1 service management and exposure functions. - -The R1 interface is clearly identified between SMO/Non-RT RIC Framework and the rApps. This is not changed by the Decoupled SMO Architecture. - -##### 4.1.3.2.2 R1 services - -The following paragraphs describe “R1 services” concepts. - -From Non-RT RIC Architecture specification [i.3] clause 6.2: - -The R1 services are a collection of services produced and consumed by logical functions in the SMO/Non-RT RIC framework or by rApps. - -The invoker of an R1 service is referred to as R1 Service Consumer and the provider of an R1 service is referred to as R1 Service Producer. R1 Service Consumers can be rApps and/or SMO/Non-RT RIC framework functions. Further, R1 Service Producers can be rApps and/or SMO/Non-RT RIC framework functions. - -An rApp as well as a SMO/Non-RT RIC framework function can produce zero or more R1 Services, likewise an rApp as well as a SMO/Non-RT RIC framework function can consume zero or more R1 Services. - -From Non-RT RIC Architecture specification [i.3] clause 7.1: - -The set of R1 services which can be accessed via the R1 interface includes (but is not limited to): - -- Service management and exposure services, which include service registration and service discovery services, authentication services, authorization services and communication support services. The service management and exposure services support extensibility of the set of R1 services. -- Data management and exposure services, which deliver data created or collected by Data Producers to Data Consumers according to their needs. -- A1-related services, which provide access to functionality related to A1. -- AI/ML workflow services, which provide access to AI and ML workflow. -- RAN OAM-related services, which provide access to RAN OAM functionality related to the O1 and open fronthaul M-plane interfaces, and to the OAM functionality related to RAN-specific network slicing in the SMO framework. -- O2-related services, which provide access to functionality related to O2. -- rApp management services, which provide functionality for managing rApps. -- TE&IV-related services, which provide access to topology and inventory data. - -##### 4.1.3.2.3 Conclusions - -From the above, the following considerations can be derived: - -- R1 services and SMOSs listed in OAD [i.2] clause 5.3.1.2.1 and in Non-RT RIC Architecture specification [i.3] clause 7.1 are based on the same SMO capabilities -- SMOSs capabilities can be consumed/produced by rApps via R1 interface -- the introduction of Decoupled SMO architecture does not conflict with the R1 interface principles listed in R1GAP [i.5] clause 4.2 -- The R1AP [i.6] defines a service-based interface. The procedures can be extended to align with the Decoupled SMO principles without major changes to the APIs. - -### 4.1.4 Use cases and requirement related aspects - -#### 4.1.4.1 Overview and highlights - -WG2 Use cases and requirements so far assume a functional architecture for SMO. - -The Decoupled SMO feature relies on a Service Based Architecture for SMO and introduces the concepts of SMOS producers/consumers. - -#### 4.1.4.2 Impact analysis - -##### 4.1.4.2.1 Use cases - -Some of the use cases in UCR [i.8] describe the procedures involving SMO components as considering the functional architecture of SMO. The introduction of a service-based architecture for SMO, implies that the SMO functional entities, and the related blocks in the diagrams, should be analysed and aligned to the corresponding SMO service producers/consumers (as an example, 'RAN NF OAM SMOS producer' instead of 'Collection & Control' in Fig. 4.1.3.1-1). - -##### 4.1.4.2.2 Requirements - -Clause 5 of UCR [i.8] specify Non-RT RIC, A1 and R1 functional and non-functional requirements. Terminology may need a revision to align to Decoupled SMO architectural principles and definitions. - -##### 4.1.4.2.3 Conclusions - -UCR [i.8] should be analysed and aligned to comply with Decoupled SMO Architectural principles. - -## 4.2 Recommendations - -The following actions are recommended to ensure alignment of WG2 specifications for the introduction of the Decoupled SMO Architecture: - -- Introduce SMOS (SMO Services) concept into the Non-RT RIC Architecture specification [i.3] to ensure it aligns with the Service-Based Architecture (SBA) principles of the Decoupled SMO framework and the definition of R1 services. -- Analyze and align description of O1/Open FH M-Plane and O2 interfaces and the related services in Non-RT RIC Architecture specification [i.3] to comply with Decoupled SMO Architectural principles, e.g. by removing the interface termination boxes and refer to the corresponding SMOS producers (RAN NF OAM and NFO/FOCOM). -- Remove the box "A1 termination" from the Non-RT RIC architecture and terminate the A1 interface into the "A1 related functions". -- Remove the reference to "A1 termination" from clause 8.1 of Non-RT RIC Architecture specification [i.3] and replace the remaining two occurrences of "A1 termination" with "A1 interface". - -- Analyse and align UCR [i.8] to comply with Decoupled SMO Architectural principles. -- Analyse and align Non-RT RIC Architecture specification [i.3], clause 5.1 to comply with Decoupled SMO Architectural principles. - -# Annex: Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2024.07.04 | 00.00.01 | Baseline version with basic structure. | -| 2025.02.19 | 00.00.02 | RMI.AO CR-0027 A1 related Impact analysis v04 incorporated. | -| 2025.06.24 | 00.00.03 | TIM.AO CR-0001 R1 related aspects Impact analysis v07
TIM.AO CR-0002 UCR related aspects Impact analysis v01
TIM.AO CR-0003 Restructuring and editorials v02
TIM.AO CR-0004 Recommendation for Impact analysis v01
TIM.AO CR-0005.O1_OFH_M-Plane_and_O2 related aspects Impact analysis v02
Above CRs incorporated. | -| 2025.07.13 | 01.00 | Published with WG2 specifications impact analysis of Decoupled SMO, including A1 related Impact analysis, R1 related aspects Impact analysis, UCR related aspects Impact analysis, O1 OFH M-Plane and O2 related aspects Impact analysis, and Recommendation for Impact analysis. | -| 2025.10.09 | 01.00.01 | NOK.AO CR-0201 DECSMO-Non-RT RIC Arch requirement analysis v04 incorporated. | -| 2025.11.18 | 02.00 | Published with WG2 specifications impact analysis of Decoupled SMO version 2, including the Non-RT RIC Arch requirement analysis. A1 related Impact analysis, R1 related aspects Impact analysis, UCR related aspects Impact analysis, O1 OFH M-Plane and O2 related aspects Impact analysis, and Recommendations for Impact analysis. | \ No newline at end of file diff --git a/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index bef92370b92f7f62fcf03e62e04f4f2905eeb0df..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:29af4545675cb00eb2790504afe0c0bc329627f1c20c8d6156b2f4290d8d8d75 -size 4502 diff --git a/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 6a69c912b93b852487847aaabc8e3d63616636f7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_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/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_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/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-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/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-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/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_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/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_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/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_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/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index d6a68ae4b197642455d63d06b8c07d6d0ccafea1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TR.DECSMO-Impact-R005-v02.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:359b47ebbf43cdcfc8a0ae4786d55f05789b530fd830801fd0a0d1fc0458bc6a -size 4589 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/doc.md b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/doc.md deleted file mode 100644 index 87738d20aa6ee8c08d9407a269072525c58fe2d7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/doc.md +++ /dev/null @@ -1,3884 +0,0 @@ - - -# --- A1 interface: Application Protocol - -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 - -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.....6 - -4 A1 Application Protocol.....7 - -4.1 Introduction .....7 - -4.2 Compatibility of A1 versions .....7 - -5 A1 services .....7 - -5.1 Introduction .....7 - -5.2 Policy management service .....8 - -5.2.1 Introduction.....8 - -5.2.2 Service description.....8 - -5.2.3 Service operations for A1 policy types .....9 - -5.2.4 Service operations for A1 policies .....11 - -5.3 Enrichment information service .....18 - -5.3.1 Introduction.....18 - -5.3.2 Service description.....18 - -5.3.3 Service operations for A1 EI types .....20 - -5.3.4 Service operations for A1 EI jobs .....22 - -5.3.5 Service operations for A1 EI job result.....28 - -5.4 ML model management service .....29 - -5.4.1 Introduction.....29 - -5.4.2 Service description.....29 - -5.4.3 Service operations for A1 ML model management .....30 - -6 API Definitions .....34 - -6.1 Introduction .....34 - -6.1.1 Encoding of attributes in A1 data types .....34 - -6.1.2 Compatibility of API versions for A1 services .....34 - -6.1.3 URI structure .....35 - -6.2 A1-P (policy management).....35 - -6.2.1 Introduction.....35 - -6.2.2 Usage of HTTP .....35 - -6.2.3 Resources .....35 - -6.2.4 Custom Operations without associated resources .....42 - -6.2.5 Notifications .....42 - -6.2.6 Data Model .....43 - -6.2.7 Error Handling .....44 - -6.3 A1-EI (enrichment information).....45 - -6.3.1 Introduction.....45 - -6.3.2 Usage of HTTP .....45 - -6.3.3 Resources .....45 - -6.3.4 Custom Operations without associated resources .....51 - -6.3.5 Notifications .....51 - -6.3.6 Void .....52 - -6.3.7 Data model.....52 - -6.3.8 Error handling.....53 - -| | | | -|-------|-----------------------------------------------------|----| -| 6.4 | A1-ML (ML model management)..... | 54 | -| 6.4.1 | Introduction..... | 54 | -| 6.4.2 | Usage of HTTP ..... | 54 | -| 6.4.3 | Resources..... | 55 | -| 6.4.4 | Custom Operations without associated resources..... | 58 | -| 6.4.5 | Notifications ..... | 59 | -| 6.4.6 | Data model..... | 59 | -| 6.4.7 | Error handling ..... | 61 | -| | Annex A (normative): OpenAPI specification ..... | 62 | -| A.1 | General ..... | 62 | -| A.1.0 | Overview ..... | 62 | -| A.1.1 | Versioning of A1 OpenAPI documents..... | 62 | -| A.1.2 | Current API versions ..... | 62 | -| A.2 | Policy management API..... | 63 | -| A.3 | Enrichment information API..... | 67 | -| A.4 | ML model management API..... | 71 | -| | Annex (informative): Change History ..... | 75 | - -# --- Foreword - -This Technical Specification (TS) has been produced by O-RAN Alliance Working Group 2. It is part of a TS-family covering the A1 interface as identified below: - -- "A1 interface: General Aspects and Principles"; -- "A1 interface: Use Cases and Requirements"; -- "A1 interface: Transport Protocol"; -- "A1 interface: Application Protocol"; -- "A1 interface: Type Definitions"; and -- "A1 interface: Test Specification". - -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 application protocol of the A1 interface. It includes service definitions and API definitions for the A1 policy management service (A1-P), the A1 enrichment information service (A1-EI), and the ML model management service. - -# --- 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.WG2.TS.A1UCR: "A1 interface: Use Cases and Requirements" ("A1UCR"). -- [2] O-RAN.WG2.TS.A1GAP: "A1 interface: General Aspects and Principles" ("A1GAP"). -- [3] O-RAN.WG2.TS.A1TP: "A1 interface: Transport Protocol" ("A1TP"). -- [4] O-RAN.WG2.TS.A1TD: "A1 interface: Type Definitions" ("A1TD"). -- [5] Void -- [6] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3". -- [7] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format". -- [8] "Semantic Versioning Specification 2.0.0" ("SemVer"). - -NOTE: Available at: - -- [9] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". -- [10] IETF RFC 9457: "Problem Details for HTTP APIs" -- [11] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3". -- [12] OpenAPI Initiative: "OpenAPI 3.0.1 Specification". - -NOTE: Available at: . - -- [13] IANA: "Hypertext Transfer Protocol (HTTP) Status Code Registry". - -NOTE: Available at: - -## 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 29.xxx-SBI-Stage3-Template. - -NOTE: Available at: [https://www.3gpp.org/ftp/Information/All\\_Templates](https://www.3gpp.org/ftp/Information/All_Templates). - -[i.2] 3GPP TS 32.158: "Design rules for REpresentational State Transfer (REST) Solution Sets (SS)". - -# --- 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the terms given in A1GAP [2], clause 3.1 and the following apply: - -**EiJobId:** Simple Data Type representing the EI job identifier. - -**EI job identifier:** identifier of an EI job that is used for requesting and delivering A1 enrichment information. - -**EI job result:** resulting enrichment information delivered based on an EI job. - -**EiTypeId:** Simple Data Type representing the EI type identifier. - -**EI type identifier:** identifier of an EI type. - -**PolicyId:** Simple Data Type representing the policy identifier. - -**policy identifier:** identifier of an A1 policy that is used in policy operations. - -**PolicyObject:** representation of an A1 policy in JSON format used as payload in HTTP based policy procedures. - -**policy statement:** expression of a goal in an A1 policy that is related to policy objectives and/or policy resources and is to be applied to/for the entities identified by the scope identifier. - -**PolicyStatusObject:** representation of the status of an A1 policy in JSON format used as payload in HTTP based policy procedures. - -**PolicyTypeId:** Simple Data Type representing the policy type identifier. - -**policy type:** model on which a PolicyObject and a PolicyStatusObject is based. - -**policy type identifier:** identifier of a policy type. - -**scope identifier:** identifier of what the statements in the policy or the EI job applies to (UE, group of UEs, slice, QoS flow, network resource or combinations thereof). - -## 3.2 Symbols - -Void. - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given in A1GAP [2], clause 3.3 and the following apply: - -| | | -|----|------------------| -| Id | Identifier | -| ML | Machine Learning | - -REST -URI - -REpresentational State Transfer -Uniform Resource Identifier - -# --- 4 A1 Application Protocol - -## 4.1 Introduction - -The present document specifies a REST realisation of the A1 interface architecture, and the policy, EI, and ML model procedures identified in A1GAP [2], clause 6. It is based on HTTP as defined in A1TP [3], clause 8 and application data models defined in A1TD [4], clauses 6 and 8. - -This definition of the A1 Application Protocol (A1AP) corresponds to a REST-based Solution Set and is based on the principles and guidelines in 3GPP TS 29.501 [6] and the related TS template [i.1]. The design patterns for HTTP procedures and JSON objects follow 3GPP TS 32.158 [i.2], clause 6. - -## 4.2 Compatibility of A1 versions - -The version number of the present document indicates that there may be implications for the compatibility between A1 implementations in Non/Near-RT RICs that are based on different versions of this specification. - -The present document specifies APIs which can have different versions. There is no one-to-one mapping between the version number of present document and the API version number of an API specified in the present document. There can be a change in the version number of the present document even if there is no change in the version number of the APIs specified in the present document. - -The compatibility of A1 implementations in Non/Near-RT RICs depends on the A1 services that are implemented and which API version(s) that are implemented for each A1 service. The API version is indicated in the URI (see clauses 6.2.1 and 6.3.1) and in the OpenAPI document (see Annex A). The present document handles the API compatibility aspects while A1TD [4] handles the compatibility for data types used by the A1 APIs. - -# --- 5 A1 services - -## 5.1 Introduction - -The present document specifies the APIs for the following services defined in A1GAP [2], clause 4.1.3: - -- A1-P:** A1 policy management service; -- A1-EI:** A1 enrichment information service; and -- A1-ML:** A1 ML model management service. - -The A1 application protocol is based on signalling between a service consumer and a service producer residing in the Non-RT RIC or in the Near-RT RIC as described by the A1 service architecture in A1GAP [2], clause 4.1.3. - -The APIs are specified based on the principles and guidelines for service-based interfaces specified in 3GPP TS 29.501 [6]. It is the service producer that handles the resources on which the service consumer performs operations. The terms consumer and producer do not refer to the direction of the data transfer over the A1 interface. - -## 5.2 Policy management service - -### 5.2.1 Introduction - -The A1-P service defines service operations that are used with policy types defined in A1TD [4], clause 7.2. - -### 5.2.2 Service description - -#### 5.2.2.1 Functional elements - -The A1 application protocol for A1-P is based on signalling between the A1-P Consumer residing in the Non-RT RIC and the A1-P Producer residing in the Near-RT RIC. Both the A1-P Consumer and the A1-P Producer contain an HTTP Client and an HTTP Server. - -![Diagram illustrating the HTTP roles in the service framework. The A1-P Consumer (top) contains an HTTP Client and an HTTP Server. The A1-P Producer (bottom) also contains an HTTP Client and an HTTP Server. Arrows show requests (PUT, GET, DELETE) from the Consumer's HTTP Client to the Producer's HTTP Server, and responses (POST) from the Producer's HTTP Server to the Consumer's HTTP Client. The Consumer's HTTP Server is labeled as the notification destination.](e1a0d046fbe7f28f5e93a47091851747_img.jpg) - -The diagram shows the interaction between an A1-P Consumer and an A1-P Producer. The A1-P Consumer contains an HTTP Client and an HTTP Server. The A1-P Producer also contains an HTTP Client and an HTTP Server. Arrows indicate the direction of HTTP requests and responses. The Consumer's HTTP Client sends requests (PUT, GET, DELETE) to the Producer's HTTP Server. The Producer's HTTP Server sends responses (POST) to the Consumer's HTTP Client. The Consumer's HTTP Server is labeled as the notification destination. - -URI paths shown on the left: - -- .../policytypes -- .../policytypes/{policyTypeId} -- .../policytypes/{policyTypeId}/policies -- .../policytypes/{policyTypeId}/policies/{policyId} -- .../policytypes/{policyTypeId}/policies/{policyId}/status - -Diagram illustrating the HTTP roles in the service framework. The A1-P Consumer (top) contains an HTTP Client and an HTTP Server. The A1-P Producer (bottom) also contains an HTTP Client and an HTTP Server. Arrows show requests (PUT, GET, DELETE) from the Consumer's HTTP Client to the Producer's HTTP Server, and responses (POST) from the Producer's HTTP Server to the Consumer's HTTP Client. The Consumer's HTTP Server is labeled as the notification destination. - -NOTE: Arrows indicate direction of HTTP requests sent from HTTP Client to HTTP Server and HTTP responses sent from HTTP Server to HTTP Client. - -**Figure 5.2.2.1-1 HTTP roles in service framework** - -The present document specifies the A1 policy procedures defined in A1UCR [1], clause 6 and A1GAP [2], clause 6.2 using HTTP operations in accordance with A1TP [3], clause 8 where a policy is represented as a JSON object in accordance with IETF RFC 8259 [7] as defined in A1TD [4]. - -#### 5.2.2.2 Policy representation - -The following principles are used for A1 policies when JSON is used as resource representation format: - -- a policy corresponds to a resource (in the REST sense); -- a policy is represented as a JSON object referred to as a PolicyObject; -- a PolicyObject contains a scope identifier and at least one policy statement (e.g. one or more policy objective statements and/or one or more policy resource statements); -- a policy is identified by a policyId that is included in the URI when an operation is for a single policy; -- the policyId is assigned by the A1-P Consumer when the policy is created; -- the A1-P Producer cannot modify or delete a policy; -- policy status and feedback notifications for a specific policy is subscribed to when the policy is created by providing a callback URI in the Create policy operation; -- a PolicyObject does not contain any information related to which internal function in the Near-RT RIC that is to evaluate the policy; - -- the A1-P Producer indicates for which policy types policy creation is supported, and the JSON schemas for policy types can be retrieved by the A1-P Consumer; and -- the A1-P Consumer cannot create, modify, or delete policy types. - -#### 5.2.2.3 Representation objects - -The following JSON objects are used within the service operations of the A1-P service: - -##### PolicyTypeObject - -The PolicyTypeObject contains the JSON schemas used to validate a PolicyObject and a PolicyStatusObject. - -##### PolicyObject - -The PolicyObject is the JSON representation of an A1 policy. - -##### PolicyStatusObject - -The PolicyStatusObject is the JSON representation of the enforcement status of an A1 policy. - -##### ProblemDetails - -The ProblemDetails object is the JSON representation of the content in a response message with other HTTP error response codes (4xx/5xx). - -#### 5.2.2.4 Resource identifiers - -The URI for A1 policy types is: - -.../policytypes - -A single policy type is identified by adding the value of the policy type identifier to the URI: - -.../policytypes/{policyTypeId} - -The URI for A1 policies is: - -.../policytypes/{policyTypeId}/policies - -A single policy is identified by adding the value of the policy identifier to the URI: - -.../policytypes/{policyTypeId}/policies/{policyId} - -The URI for status of a single policy is: - -.../policytypes/{policyTypeId}/policies/{policyId}/status - -The URI for policy notification is referred to as the notificationDestination and is a callback URI provided when creating a policy. - -### 5.2.3 Service operations for A1 policy types - -#### 5.2.3.1 Introduction - -Table 5.2.3.1-1 describes the mapping between the A1 policy type operations and the HTTP methods used to realise them, and the mandatory HTTP status codes for the operations. - -**Table 5.2.3.1-1 A1 policy operations to HTTP methods mapping** - -| Service operation | HTTP method | HTTP status codes | -|-------------------------------|-------------|-------------------| -| Query policy type identifiers | GET | 200 | -| Query policy type | GET | 200, 404 | - -The following clauses describe the policy type operations. - -NOTE: The present document does not define any limits for how many policyTypeId that can be transferred in a single A1 message. - -#### 5.2.3.2 Query policy type identifiers - -##### 5.2.3.2.1 General - -The A1-P Consumer uses the Query policy type identifiers operation to discover policy types. - -The operation to query policy type identifiers is based on HTTP GET. The resource to be read is identified within the URI while the message body is empty, and the response returns an array of identifiers representing all available policy types. - -![Sequence diagram showing the interaction between A1-P Consumer and A1-P Producer for the Query policy type identifiers operation. The Consumer sends a GET request to /policytypes, and the Producer responds with a 200 OK containing an array of PolicyTypeIds.](b0211cee4b20034939d883ac0d70f696_img.jpg) - -``` - -sequenceDiagram - participant A1-P Consumer - participant A1-P Producer - Note left of A1-P Consumer: A1-P Consumer - Note right of A1-P Producer: A1-P Producer - A1-P Consumer->>A1-P Producer: 1. GET .../policytypes - A1-P Producer-->>A1-P Consumer: 2. 200 OK (array(PolicyTypeId)) - Note left of A1-P Consumer: A1-P Consumer - Note right of A1-P Producer: A1-P Producer - -``` - -Sequence diagram showing the interaction between A1-P Consumer and A1-P Producer for the Query policy type identifiers operation. The Consumer sends a GET request to /policytypes, and the Producer responds with a 200 OK containing an array of PolicyTypeIds. - -**Figure 5.2.3.2.1-1 Query policy type identifiers operation** - -- 1) The A1-P Consumer shall send an HTTP GET request to the A1-P Producer. The target URI shall identify the resource "/policytypes". The message body shall be empty. -- 2) The A1-P Producer shall return the HTTP GET response. On success, "200 OK" shall be returned. The message body shall carry an array of policy type identifiers representing all available policy types. On failure, the appropriate error code shall be returned, and the response message body may contain additional error information. - -##### 5.2.3.2.2 Query all policy type identifiers procedure - -The procedure to query all policy type identifiers is based on the Query policy type identifiers operation illustrated in figure 5.2.3.2.1-1. - -#### 5.2.3.3 Query policy type - -##### 5.2.3.3.1 General - -A1-P Consumer uses the Query policy type procedures to read the schemas for a specific policy type or for all policy types. The Query policy type operation is used in the following procedures: - -- Query single policy type; -- Query multiple policy types; and -- Query all policy types. - -The operation to query a policy type is based on HTTP GET. The policy type to be read is identified with a URI that includes the policyTypeId while the message body is empty, and the response returns the PolicyTypeObject. - -![Sequence diagram showing the query policy type operation between an A1-P Consumer and an A1-P Producer. Step 1: GET .../policytypes/{policyTypeId} from Consumer to Producer. Step 2: 200 OK (PolicyTypeObject) from Producer to Consumer.](5a4e62bead259c258d069fd3663ea670_img.jpg) - -``` - -sequenceDiagram - participant A1-P Consumer - participant A1-P Producer - Note left of A1-P Consumer: A1-P Consumer - Note right of A1-P Producer: A1-P Producer - A1-P Consumer->>A1-P Producer: 1. GET .../policytypes/{policyTypeId} - A1-P Producer-->>A1-P Consumer: 2. 200 OK (PolicyTypeObject) - Note left of A1-P Consumer: A1-P Consumer - Note right of A1-P Producer: A1-P Producer - -``` - -Sequence diagram showing the query policy type operation between an A1-P Consumer and an A1-P Producer. Step 1: GET .../policytypes/{policyTypeId} from Consumer to Producer. Step 2: 200 OK (PolicyTypeObject) from Producer to Consumer. - -**Figure 5.2.3.3.1-1 Query policy type operation** - -- 1) The A1-P Consumer shall send an HTTP GET request to the A1-P Producer. The target URI shall identify the policy type to be read based on the policyTypeId under the resource "/policytypes". The message body shall be empty. -- 2) The A1-P Producer shall return the HTTP GET response. On success, "200 OK" shall be returned. The message body shall carry a PolicyTypeObject representing the read policy type. On failure, the appropriate error code shall be returned, and the response message body may contain additional error information. - -On reception of a policyTypeId that does not exist, "404 Not Found" shall be returned. - -##### **5.2.3.3.2 Query single policy type procedure** - -The procedure to query single policy type is based on the Query policy type operation illustrated in figure 5.2.3.3.1-1. - -##### **5.2.3.3.3 Query multiple policy types procedure** - -The procedure to query multiple policy types is a sequence of Query policy type operations. - -##### **5.2.3.3.4 Query all policy types procedure** - -The procedure to query all policy types is a sequence of Query policy type operations for each policy type identifier retrieved as described in clause 5.2.3.2.1. - -### **5.2.4 Service operations for A1 policies** - -#### **5.2.4.1 Introduction** - -Table 5.2.4.1-1 describes the mapping between the A1 policy operations and the HTTP methods used to realise them, and the mandatory HTTP status codes for the operations. - -**Table 5.2.4.1-1 A1 policy operations to HTTP methods mapping** - -| Service operation | HTTP method | HTTP status codes | -|--------------------------|-------------|--------------------| -| Query policy identifiers | GET | 200, 404 | -| Create policy | PUT | 201, 400, 404, 409 | -| Update policy | PUT | 200, 400, 409 | -| Query policy | GET | 200, 404 | -| Delete policy | DELETE | 204, 404 | -| Query policy status | GET | 200, 404 | -| Notify policy status | POST | 204, 400 | - -The following clauses describe the policy operations. For details on the policy-related objects (in JSON format) transferred in the HTTP message bodies, see A1TD [4], clause 6.4. - -The policy scope in a PolicyObject contains a scope identifier that can be e.g. a ueId, a groupId or a cellId. The A1-P Consumer maps policyIds to scope identifiers in order to manage e.g. all policies applicable to a specific individual ueId. If there are several policies related to the same scope identifier, then several policy operations can be used to manage that specific scope. - -The A1-P Producer enables the A1-P Consumer to create policies of specific types and the A1-P Consumer can discover the supported policy types. The A1-P Consumer indicates the policyTypeId when creating or updating a policy and when querying for a specific policy. - -NOTE: The present document does not define any limits for how many policyId that can be transferred in a single A1 message. - -#### 5.2.4.2 Query policy identifiers - -##### 5.2.4.2.1 General - -The A1-P Consumer uses the Query policy identifiers operation to discover policies for a specific policy type or for all policy types. The Query policy identifiers operation is used in the following procedures: - -- Query policy identifiers; and -- Query all policy identifiers. - -The operation to query all policy identifiers is based on HTTP GET. The policy type resource to be read is identified within the URI while the message body is empty, and the response returns an array of identifiers representing all available policies of that policy type. - -![Sequence diagram showing the Query policy identifiers operation. The A1-P Consumer sends a GET request to the A1-P Producer, and the A1-P Producer responds with a 200 OK containing an array of PolicyIds.](63e0c22852c26699d0bd095a2d796bab_img.jpg) - -``` - -sequenceDiagram - participant A1-P Consumer - participant A1-P Producer - Note left of A1-P Consumer: A1-P Consumer - Note right of A1-P Producer: A1-P Producer - A1-P Consumer->>A1-P Producer: 1. GET .../policytypes/{policyTypeId}/policies - A1-P Producer-->>A1-P Consumer: 2. 200 OK (array(PolicyId)) - Note left of A1-P Consumer: A1-P Consumer - Note right of A1-P Producer: A1-P Producer - -``` - -Sequence diagram showing the Query policy identifiers operation. The A1-P Consumer sends a GET request to the A1-P Producer, and the A1-P Producer responds with a 200 OK containing an array of PolicyIds. - -Figure 5.2.4.2.1-1 Query policy identifiers operation - -- 1) The A1-P Consumer shall send an HTTP GET request to the A1-P Producer. The target URI shall identify the resource "/policytypes/{policyTypeId}/policies". The message body shall be empty. -- 2) The A1-P Producer shall return the HTTP GET response. On success, "200 OK" shall be returned. The message body shall carry an array of policy identifiers representing all available policies of the given policy type. On failure, the appropriate error code shall be returned, and the response message body may contain additional error information. - -On reception of a policyTypeId that does not exist, "404 Not Found" shall be returned. - -##### 5.2.4.2.2 Query policy identifiers procedure - -The procedure to query policy identifiers is based on the Query policy identifiers operation illustrated in figure 5.2.4.2.1-1. - -##### 5.2.4.2.3 Query all policy identifiers procedure - -The procedure to query all policy identifiers is based on the Query policy identifiers operation. The operation is performed for each policy type for which policies have been created, or for each policy type identifier discovered using the Query policy type identifiers operation defined in clause 5.2.3.2.1. - -#### 5.2.4.3 Create policy - -##### 5.2.4.3.1 General - -The A1-P Consumer uses the Create policy procedure to create an A1 policy. The Create policy operation is used in the following procedures: - -- Create single policy; and -- Create multiple policies. - -The operation to create a policy is based on HTTP PUT. The policy to be created is identified with a URI that includes the policyTypeId and the policyId and the message body contains the PolicyObject. - -If the policy creation request is accepted, the policy shall be enforced. - -In case a policy already exists for the provided URI, the PUT request shall be handled as for Update single policy (see clause 5.2.4.4.1). - -![Sequence diagram showing the Create policy operation between A1-P Consumer and A1-P Producer. The Consumer sends a PUT request to the Producer, and the Producer responds with a 201 Created status.](5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg) - -``` - -sequenceDiagram - participant A1-P Consumer - participant A1-P Producer - Note left of A1-P Consumer: A1-P Consumer - Note right of A1-P Producer: A1-P Producer - A1-P Consumer->>A1-P Producer: 1. PUT .../policytypes/{policyTypeId}/policies/{policyId} (PolicyObject) - A1-P Producer-->>A1-P Consumer: 2. 201 Created (PolicyObject) - Note left of A1-P Consumer: A1-P Consumer - Note right of A1-P Producer: A1-P Producer - -``` - -Sequence diagram showing the Create policy operation between A1-P Consumer and A1-P Producer. The Consumer sends a PUT request to the Producer, and the Producer responds with a 201 Created status. - -Figure 5.2.4.3.1-1 Create policy operation - -- 1) The A1-P Consumer shall generate the policyId and send an HTTP PUT request to the A1-P Producer. The target URI shall identify the resource (policyId) to be created under the resource "/policytypes/{policyTypeId}/policies". The message body shall carry a PolicyObject. -- 2) The A1-P Producer shall return the HTTP PUT response. On success, "201 Created" shall be returned. The "Location" HTTP header shall be present and shall carry the URI of the new policy and the message body shall carry the PolicyObject. On failure, the appropriate error code shall be returned, and the message body may contain additional error information. - -When creating a policy, the A1-P Consumer shall include a policyTypeId in the URI for the PUT request. The policyTypeId shall be used by the A1-P Producer to select the appropriate schemas to use for validation of the PolicyObject and for PolicyStatus. - -The A1-P Consumer may subscribe to policy status and feedback notifications related to the created policy. Policy status and feedback notifications are subscribed to by including the notificationDestination as a query parameter in the PUT request. - -On reception of a policyTypeId that does not exist, "404 Not Found" shall be returned. - -On failure to validate the PolicyObject, "400 Bad Request" shall be returned. - -In case the new policy would be identical to, or would be overlapping or conflicting with, an existing policy, "409 Conflict" shall be returned. - -##### 5.2.4.3.2 Create single policy procedure - -The procedure to create single policy is based on the Create policy operation illustrated in figure 5.2.4.3.1-1. - -##### 5.2.4.3.3 Create multiple policies procedure - -The procedure to create multiple policies is a sequence of Create policy operations. - -#### 5.2.4.4 Update policy - -##### 5.2.4.4.1 General - -The A1-P Consumer uses the Update single policy procedure to update an A1 policy. The Update policy operation is used in the following procedures: - -- Update single policy; and -- Update multiple policies. - -The operation to update a single policy is based on HTTP PUT. The policy to be updated is identified with a URI that includes the policyTypeId and the policyId and the message body contains the PolicyObject for the updated policy. - -If the policy update request is accepted, the policy shall be enforced. In case a policy does not exist for the provided URI, the PUT request shall be handled as for Create single policy (see clause 5.2.4.3.1). - -![Sequence diagram of the Update policy operation procedure. It shows two lifelines: A1-P Consumer and A1-P Producer. Step 1: A1-P Consumer sends a PUT request to A1-P Producer with the URI .../policytypes/{policyTypeId}/policies/{policyId} and a PolicyObject. Step 2: A1-P Producer returns a 200 OK response with the updated PolicyObject.](66c2bf11a8f117cddf67eff92d4c736c_img.jpg) - -``` - -sequenceDiagram - participant A1-P Consumer - participant A1-P Producer - Note left of A1-P Consumer: A1-P Consumer - Note right of A1-P Producer: A1-P Producer - A1-P Consumer->>A1-P Producer: 1. PUT .../policytypes/{policyTypeId}/policies/{policyId} (PolicyObject) - A1-P Producer-->>A1-P Consumer: 2. 200 OK (PolicyObject) - Note left of A1-P Consumer: A1-P Consumer - Note right of A1-P Producer: A1-P Producer - -``` - -Sequence diagram of the Update policy operation procedure. It shows two lifelines: A1-P Consumer and A1-P Producer. Step 1: A1-P Consumer sends a PUT request to A1-P Producer with the URI .../policytypes/{policyTypeId}/policies/{policyId} and a PolicyObject. Step 2: A1-P Producer returns a 200 OK response with the updated PolicyObject. - -**Figure 5.2.4.4.1-1 Update policy operation procedure** - -- 1) The A1-P Consumer shall send an HTTP PUT request to the A1-P Producer. The target URI shall identify the policy to be updated based on the policyId under the resource "/policytypes/{policyTypeId}/policies". The message body shall contain a PolicyObject. -- 2) The A1-P Producer shall return the HTTP PUT response. On success, "200 OK" shall be returned. The message body shall carry a PolicyObject representing the updated policy. On failure, the appropriate error code shall be returned, and the response message body may contain additional error information. - -The A1-P Consumer may subscribe to policy status and feedback notifications related to the updated policy. Policy status and feedback notifications are subscribed to by including the notificationDestination as a query parameter in the PUT request. The A1-P Consumer may change the notificationDestination for policy status and feedback notifications in an update policy request. The A1-P Consumer may cancel policy status and feedback notifications. Policy status and feedback notifications are cancelled by omitting notificationDestination in the PUT request. - -On failure to validate the PolicyObject fails, "400 Bad Request" shall be returned. - -In case the policy after update would be identical to, or would be overlapping or conflicting with, an existing policy, "409 Conflict" shall be returned. - -##### 5.2.4.4.2 Update single policy procedure - -The procedure to update single policy is based on the Update policy operation illustrated in figure 5.2.4.4.1-1. - -##### 5.2.4.4.3 Update multiple policies procedure - -The procedure to update multiple policies is a sequence of Update policy operations. - -#### 5.2.4.5 Query policy - -##### 5.2.4.5.1 General - -The A1-P Consumer uses the Query policy operation to read an A1 policy. The Query policy operation is used in the following procedures: - -- Query single policy; -- Query multiple policies; and -- Query all policies. - -The operation to query a policy is based on HTTP GET. The policy to be read is identified with a URI that includes the policyTypeId and the policyId while the message body is empty, and the response returns the PolicyObject. - -![Sequence diagram showing the Query policy operation between an A1-P Consumer and an A1-P Producer. The Consumer sends a GET request to the Producer, and the Producer responds with a 200 OK containing a PolicyObject.](3f1987804d7d78bc3b3bc560e974280a_img.jpg) - -``` - -sequenceDiagram - participant A1-P Consumer - participant A1-P Producer - Note left of A1-P Consumer: A1-P Consumer - Note right of A1-P Producer: A1-P Producer - A1-P Consumer->>A1-P Producer: 1. GET .../policytypes/{policyTypeId}/policies/{policyId} - A1-P Producer-->>A1-P Consumer: 2. 200 OK (PolicyObject) - Note left of A1-P Consumer: A1-P Consumer - Note right of A1-P Producer: A1-P Producer - -``` - -Sequence diagram showing the Query policy operation between an A1-P Consumer and an A1-P Producer. The Consumer sends a GET request to the Producer, and the Producer responds with a 200 OK containing a PolicyObject. - -**Figure 5.2.4.5.1-1 Query policy operation** - -- 1) The A1-P Consumer shall send an HTTP GET request to the A1-P Producer. The target URI shall identify the policy to be read based on the policyId under the resource "/policytypes/{policyTypeId}/policies". The message body shall be empty. -- 2) The A1-P Producer shall return the HTTP GET response. On success, "200 OK" shall be returned. The message body shall carry a PolicyObject representing the read policy. On failure, the appropriate error code shall be returned, and the response message body may contain additional error information. - -On reception of policyTypeId and policyId for which no policy exists, "404 Not Found" shall be returned. - -##### 5.2.4.5.2 Query single policy procedure - -The procedure to query single policy is based on the Query policy operation illustrated in figure 5.2.4.5.1-1. - -##### 5.2.4.5.3 Query multiple policies procedure - -The procedure to query multiple policies is a sequence of Query policy operations. - -NOTE: To query all policies applicable to e.g. a dynamically defined group of UEs, a slice or a cell, the A1-P Consumer identifies applicable policyId(s) and makes a sequence of single policy queries. - -##### 5.2.4.5.4 Query all policies procedure - -The procedure to query all policies is, for each policyTypeId retrieved as described in clause 5.2.3.2.1, a sequence of Query policy operations for each policyId retrieved as described in clause 5.2.4.2.1. - -#### 5.2.4.6 Delete policy - -##### 5.2.4.6.1 General - -The A1-P Consumer uses the Delete policy procedure to delete an A1 policy. The Delete policy operation is used in the following procedures: - -- Delete single policy; and -- Delete multiple policies. - -The operation to delete a policy is based on HTTP DELETE. The policy to be deleted is identified with a URI that includes the policyTypeId and the policyId. Neither request nor response contain any PolicyObject in the message body. - -![Sequence diagram for Delete policy operation showing A1-P Consumer sending a DELETE request to A1-P Producer and receiving a 204 No Content response.](6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg) - -``` - -sequenceDiagram - participant A1-P Consumer - participant A1-P Producer - Note left of A1-P Consumer: A1-P Consumer - Note right of A1-P Producer: A1-P Producer - A1-P Consumer->>A1-P Producer: 1. DELETE .../policytypes/{policyTypeId}/policies/{policyId} - A1-P Producer-->>A1-P Consumer: 2. 204 No Content - -``` - -Sequence diagram for Delete policy operation showing A1-P Consumer sending a DELETE request to A1-P Producer and receiving a 204 No Content response. - -**Figure 5.2.4.6.1-1 Delete policy operation** - -- 1) The A1-P Consumer shall send an HTTP DELETE request to the A1-P Producer. The target URI shall identify the policy to be deleted based on the policyId under the resource "/policytypes/{policyTypeId}/policies". The message body shall be empty. -- 2) The A1-P Producer shall return the HTTP DELETE response. On success, "204 No Content" shall be returned. The message body shall be empty. On failure, the appropriate error code shall be returned, and the response message body may contain additional error information. - -On the reception of policyTypeId and policyId for which no policy exists, "404 Not Found" shall be returned. - -##### 5.2.4.6.2 Delete single policy procedure - -The procedure to delete single policy is based on the Delete policy operation illustrated in figure 5.2.4.6.1-1. - -##### 5.2.4.6.3 Delete multiple policies procedure - -The procedure to delete multiple policies is a sequence of Delete policy operations. - -#### 5.2.4.7 Query policy status - -##### 5.2.4.7.1 General - -The A1-P Consumer uses the Query policy status operation to query the status of an A1 policy. - -The operation to query status for a policy is based on HTTP GET. The policy for which status is to be read is identified with a URI that includes the policyTypeId and the policyId while the message body is empty, and the response returns a PolicyStatusObject. - -![Sequence diagram illustrating the Query policy status operation. The A1-P Consumer sends a GET request to the A1-P Producer, and the A1-P Producer returns a 200 OK response with a PolicyStatusObject.](8307f6b04df072c9332f9987e034272c_img.jpg) - -``` - -sequenceDiagram - participant A1-P Consumer - participant A1-P Producer - Note left of A1-P Consumer: A1-P Consumer - Note right of A1-P Producer: A1-P Producer - A1-P Consumer->>A1-P Producer: 1. GET .../policytypes/{policyTypeId}/policies/{policyId}/status - A1-P Producer-->>A1-P Consumer: 2. 200 OK (PolicyStatusObject) - Note left of A1-P Consumer: A1-P Consumer - Note right of A1-P Producer: A1-P Producer - -``` - -Sequence diagram illustrating the Query policy status operation. The A1-P Consumer sends a GET request to the A1-P Producer, and the A1-P Producer returns a 200 OK response with a PolicyStatusObject. - -**Figure 5.2.4.7.1-1 Query policy status operation** - -- 1) The A1-P Consumer shall send an HTTP GET request to the A1-P Producer. The target URI shall identify the policy for which status is to be read based on the policyId under the resource "/policytypes/{policyTypeId}/policies". The message body shall be empty. -- 2) The A1-P Producer shall return the HTTP GET response. On success, "200 OK" shall be returned. The message body shall carry a PolicyStatusObject representing the status of the policy. On failure, the appropriate error code shall be returned, and the response message body may contain additional error information. - -On reception of policyTypeId and policyId for which no policy status exists, "404 Not Found" shall be returned. - -##### 5.2.4.7.2 Query policy status procedure - -The procedure to query policy status is based on the Query policy status operation illustrated in figure 5.2.4.7.1-1. - -#### 5.2.4.8 Notify policy status - -##### 5.2.4.8.1 General - -The A1-P Producer uses the Notify policy status operation to update the A1-P Consumer about changes of the status of an A1 policy. - -Notify policy status is an operation that requires the A1-P Producer to have a reduced feature HTTP Client for sending HTTP POST requests and receiving HTTP POST responses. Correspondingly, the A1-P Consumer is required to have a reduced feature HTTP Server for receiving HTTP POST requests and sending HTTP POST responses. - -The A1-P Consumer uses the Create single policy operation defined in clause 5.2.4.3.1, or the Update single policy operation defined in clause 5.2.4.4.1, to subscribe to policy status and feedback notifications for a policy. - -The policy status and feedback notifications are sent to the notificationDestination provided when creating or updating the policy. The PolicyStatusObject contains the information about policy status and may contain information about causes for status change. - -The operation to notify policy status is based on HTTP POST. The URI contains the target resource for policy status and feedback notification handling. The notification content is represented in a PolicyStatusObject that is included in the message body. - -![Sequence diagram for Notify policy status operation. It shows two lifelines: A1-P Consumer and A1-P Producer. Step 1: A1-P Producer sends a POST {notificationDestination} (PolicyStatusObject) to A1-P Consumer. Step 2: A1-P Consumer returns a 204 No content response to A1-P Producer.](dfe556fea00682b09a59427aaf72051c_img.jpg) - -``` - -sequenceDiagram - participant A1-P Consumer - participant A1-P Producer - Note left of A1-P Consumer: A1-P Consumer - Note right of A1-P Producer: A1-P Producer - A1-P Producer->>A1-P Consumer: 1. POST {notificationDestination} (PolicyStatusObject) - A1-P Consumer-->>A1-P Producer: 2. 204 No content - -``` - -Sequence diagram for Notify policy status operation. It shows two lifelines: A1-P Consumer and A1-P Producer. Step 1: A1-P Producer sends a POST {notificationDestination} (PolicyStatusObject) to A1-P Consumer. Step 2: A1-P Consumer returns a 204 No content response to A1-P Producer. - -**Figure 5.2.4.8.1-1 Notify policy status operation** - -- 1) The A1-P Producer shall send an HTTP POST request to the A1-P Consumer. The target URI (notificationDestination) identifies the sink for policy status and feedback notifications. The message body shall contain a PolicyStatusObject. -- 2) The A1-P Consumer shall return the HTTP POST response with "204 No Content". The message body shall be empty. - -On failure to validate the PolicyStatusObject, "400 Bad Request" shall be returned, and the response message body may contain additional error information. - -##### **5.2.4.8.2 Notify policy status procedure** - -The procedure to notify policy status and feedback is based on the Notify policy status operation illustrated in figure 5.2.4.8.1-1. - -## 5.3 Enrichment information service - -### 5.3.1 Introduction - -The A1-EI service defines service operations that are used with EI types defined in A1TD [4], clause 9.2. - -### 5.3.2 Service description - -#### 5.3.2.1 Functional elements - -The A1 application protocol for A1-EI is based on signalling between the A1-EI Consumer residing in the Near-RT RIC and the A1-EI Producer residing in the Non-RT RIC. Both the A1-EI Consumer and the A1-EI Producer contain an HTTP Client and an HTTP Server. - -![Diagram showing HTTP roles in service framework. At the top, an 'A1-EI Producer' box contains an 'HTTP Server' and an 'HTTP Client'. At the bottom, an 'A1-EI Consumer' box contains an 'HTTP Client' and an 'HTTP Server'. Arrows show requests from clients to servers and responses from servers to clients. On the left, GET, PUT, and DELETE operations are listed. On the right, POST is listed. URI examples on the left include ../eitypes, ../eitypes/{eiTypeId}, ../ejobs, ../ejobs/{eiJobId}, and ../ejobs/{eiJobId}/status. On the right, {jobStatusNotificationUri} and {jobResultUri} are shown.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) - -Diagram showing HTTP roles in service framework. At the top, an 'A1-EI Producer' box contains an 'HTTP Server' and an 'HTTP Client'. At the bottom, an 'A1-EI Consumer' box contains an 'HTTP Client' and an 'HTTP Server'. Arrows show requests from clients to servers and responses from servers to clients. On the left, GET, PUT, and DELETE operations are listed. On the right, POST is listed. URI examples on the left include ../eitypes, ../eitypes/{eiTypeId}, ../ejobs, ../ejobs/{eiJobId}, and ../ejobs/{eiJobId}/status. On the right, {jobStatusNotificationUri} and {jobResultUri} are shown. - -NOTE: Arrows indicate direction of HTTP requests sent from HTTP Client to HTTP Server and HTTP responses sent from HTTP Server to HTTP Client. - -**Figure 5.3.2.1-1 HTTP roles in service framework** - -The present document specifies the A1 EI procedures defined in A1GAP [2], clause 6.3 using HTTP operations in accordance with A1TP [3], clause 8 where EI types, jobs and job status and results are represented as JSON objects in accordance with RFC 8259 [7] as defined in A1TD [4], clause 8.4. - -#### 5.3.2.2 A1 EI representation - -The following principles are used for A1 enrichment information when JSON is used as resource representation format: - -- the A1-EI Producer indicates the EI types that are available; -- an EI type is identified by an EI type identifier and the schemas for available EI types can be retrieved by the A1-EI Consumer; -- an EI job can be created for delivery of information of a specific A1 EI type; -- an EI job corresponds to a resource (in the REST sense); -- an EI job, when transferred over HTTP, is represented as a JSON object referred to as an EiJobObject; -- an EI job object contains a scope identifier and parameters and conditions related to the EI type the job is for; -- an EI job is identified by an EI job identifier that is included in the URI for an EI job operation; -- the EI job identifier is assigned by the A1-EI Consumer when the EI job is created; -- status for a specific EI job can be queried and notifications can be subscribed to when the EI job is created by providing a callback URI in the create EI job operation; -- an EI job object does not contain any information related to which source that produces it nor which internal function in the near-RIC that is to consume it; -- EI job results are delivered to a callback URI provided in the create EI job operation; and -- delivered A1 EI that is represented as a JSON object is referred to as an EiJobResultObject. - -#### 5.3.2.3 Representation objects - -The following JSON objects are used within the service operations of the A1-EI service: - -EiTypeObject - -The EI type object contains the JSON schemas used to formulate an EI job and interpret an EI job status object and an EI job result object. - -##### **EiJobObject** - -The EI job object is the JSON representation of an EI job. - -##### **EiJobStatusObject** - -The EI job status object is the JSON representation of the status for an EI job. - -##### **EiJobResultObject** - -The EI job result object is the JSON representation of the result delivered during an EI job. - -##### **ProblemDetails** - -The problem details object is the JSON representation of the content in a response message with other HTTP error response codes (4xx/5xx). - -#### 5.3.2.4 Resource identifiers - -The URI for A1 enrichment information is: - -.../eitypes - -A single EI type is identified by adding the value of the EI type identifier to the URI: - -.../eitypes/{eiTypeId} - -The URI for A1 EI jobs is: - -.../eijobs - -A single EI job is identified by adding the value of the EI job identifier to the URI: - -.../eijobs/{eiJobId} - -The URI for status of an EI job is: - -.../eijobs/{eiJobId}/status - -The URI for EI job status notification is referred to as the jobStatusNotificationUri and is a callback URI provided when creating an EI job. - -The URI for delivery of EI job result is referred to as the jobResultUri and is a callback URI provided when creating an EI job. - -### 5.3.3 Service operations for A1 EI types - -#### 5.3.3.1 Introduction - -Table 5.3.3.1-1 describes the mapping between the A1 EI types operations, and the HTTP methods used to realise them, and the mandatory HTTP status codes. - -**Table 5.3.3.1-1 A1 EI operations to HTTP methods mapping** - -| Service operation | HTTP method | HTTP status codes | -|---------------------------|-------------|-------------------| -| Query EI type identifiers | GET | 200 | -| Query EI type | GET | 200, 404 | - -The following clauses describe the EI types operations. For further information on the EI objects transferred in the HTTP message bodies, see A1TD [4], clause 8.4.1. - -The purpose of the EI types operations is to enable the A1-EI Consumer to - -- identify which EI types that are available from the A1-EI Producer. Each specific type of enrichment information is identified by a unique EI type identifier (EiTypeId); and -- request detailed information related to a specific EI type that can be used to create an EI job and to handle the delivery of results from the EI job. - -NOTE: The present document does not define any limits for how many eiTypeId/eiJobId that can be transferred in a single A1 message. - -#### 5.3.3.2 Query EI type identifiers - -##### 5.3.3.2.1 General - -The A1-EI Consumer uses the Query EI type identifiers operation to query which EI types that are currently supported. - -The operation to query EI type identifiers is based on HTTP GET. The resource to be read is identified within the URI while the message body is empty, and the response returns an array of identifiers representing all available EI types. - -![Sequence diagram showing the Query EI type identifiers operation. The A1-EI Consumer sends a GET request to the A1-EI Producer, and the A1-EI Producer responds with a 200 OK containing an array of EiTypeId.](608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg) - -``` - -sequenceDiagram - participant A1-EI Consumer - participant A1-EI Producer - Note left of A1-EI Consumer: A1-EI Consumer - A1-EI Consumer->>A1-EI Producer: 1. GET .../eitypes - Note right of A1-EI Producer: A1-EI Producer - A1-EI Producer-->>A1-EI Consumer: 2. 200 OK (array(EiTypeId)) - -``` - -Sequence diagram showing the Query EI type identifiers operation. The A1-EI Consumer sends a GET request to the A1-EI Producer, and the A1-EI Producer responds with a 200 OK containing an array of EiTypeId. - -**Figure 5.3.3.2.1-1 Query EI type identifiers operation** - -- 1) The A1-EI Consumer shall send an HTTP GET request to the A1-EI Producer. The target URI shall identify the resource "/eitypes". The message body shall be empty. -- 2) The A1-EI Producer shall return the HTTP GET response. On success, "200 OK" shall be returned. The message body shall carry an array of EI type identifiers representing all available EI types. On failure, the appropriate error code shall be returned, and the response message body may contain additional error information. - -##### 5.3.3.2.2 Query EI type identifiers procedure - -The procedure to query EI type identifiers is based on the Query EI type identifiers operation illustrated in figure 5.3.3.2.1-1. - -#### 5.3.3.3 Query EI type - -##### 5.3.3.3.1 General - -The A1-EI Consumer uses the Query EI type operation to read the schemas for an EI type. - -The operation to query an EI type is based on HTTP GET. The EI type to be queried is identified with a URI that includes the eiTypeId while the message body is empty, and the response returns the EiTypeObject. - -![Sequence diagram showing the Query EI type operation. It consists of two lifelines: A1-EI Producer and A1-EI Consumer. Step 1: A1-EI Consumer sends a GET request to A1-EI Producer with the URI .../eitypes/{eiTypeId}. Step 2: A1-EI Producer responds with a 200 OK status and an EiTypeObject in the message body.](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) - -``` - -sequenceDiagram - participant A1-EI Consumer - participant A1-EI Producer - Note left of A1-EI Consumer: A1-EI Consumer - A1-EI Consumer->>A1-EI Producer: 1. GET .../eitypes/{eiTypeId} - Note right of A1-EI Producer: A1-EI Producer - A1-EI Producer-->>A1-EI Consumer: 2. 200 OK (EiTypeObject) - -``` - -Sequence diagram showing the Query EI type operation. It consists of two lifelines: A1-EI Producer and A1-EI Consumer. Step 1: A1-EI Consumer sends a GET request to A1-EI Producer with the URI .../eitypes/{eiTypeId}. Step 2: A1-EI Producer responds with a 200 OK status and an EiTypeObject in the message body. - -**Figure 5.3.3.3.1-1 Query EI type operation** - -- 1) The A1-EI Consumer shall send an HTTP GET request to the A1-EI Producer. The target URI shall identify the EI type to be read based on the eiTypeId under the resource "/eitypes". The message body shall be empty. -- 2) The A1-EI Producer shall return the HTTP GET response. On success, "200 OK" shall be returned. The message body shall carry an EiTypeObject representing the read EI type. On failure, the appropriate error code shall be returned, and the response message body may contain additional error information. - -On reception of an eiTypeId that does not exist, "404 Not Found" shall be returned. - -##### **5.3.3.3.2 Query EI type procedure** - -The procedure to query EI type is based on the Query EI type operation illustrated in figure 5.3.3.3.1-1. - -### **5.3.4 Service operations for A1 EI jobs** - -#### **5.3.4.1 Introduction** - -Table 5.3.4.1-1 describes the mapping between the A1 EI jobs operations and the HTTP methods used to realise them, and the mandatory HTTP status codes. - -**Table 5.3.4.1-1 A1 EI operations to HTTP methods mapping** - -| Service operation | HTTP method | HTTP status codes | -|--------------------------|-------------|--------------------| -| Query EI job identifiers | GET | 200 | -| Create EI job | PUT | 201, 400, 404, 409 | -| Query EI job | GET | 200, 404 | -| Update EI job | PUT | 200, 400, 409 | -| Delete EI job | DELETE | 204, 404 | -| Query EI job status | GET | 200, 404 | -| Notify EI job status | POST | 204, 400 | - -The following clauses describe the EI jobs operations. For further information on the EI job objects transferred in the HTTP message bodies, see A1TD [4], clauses 8.4.2, 8.4.3, and 8.4.5. - -The EI job contains a definition of the content and conditions for the delivery of the EI job result. - -The A1-EI Producer enables the A1-EI Consumer to create EI jobs for specific EI types and the A1-EI Consumer can discover the supported EI types. The A1-EI Consumer indicates the eiTypeId in all EI job related operations. - -**NOTE:** The present document does not define any limits for how many eiTypeId/eiJobId that can be transferred in a single A1 message. - -#### 5.3.4.2 Query EI job identifiers - -##### 5.3.4.2.1 General - -The A1-EI Consumer uses the Query EI job identifiers operation to check which EI jobs that exist. - -The operation to query EI job identifiers is based on HTTP GET. The resource to be read is identified within the URI while the message body is empty, and the response returns an array of identifiers representing all available EI jobs. The operation can be performed for each EI type for which EI jobs have been created, or for all created EI jobs. - -![Sequence diagram illustrating the Query EI job identifiers operation. The A1-EI Consumer sends a GET request to the A1-EI Producer, and the A1-EI Producer returns a 200 OK response with an array of EI job identifiers.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) - -``` - -sequenceDiagram - participant A1-EI Consumer - participant A1-EI Producer - Note left of A1-EI Consumer: A1-EI Consumer - A1-EI Consumer->>A1-EI Producer: 1. GET .../eijobs - Note right of A1-EI Producer: A1-EI Producer - A1-EI Producer-->>A1-EI Consumer: 2. 200 OK (array(EiJobId)) - -``` - -Sequence diagram illustrating the Query EI job identifiers operation. The A1-EI Consumer sends a GET request to the A1-EI Producer, and the A1-EI Producer returns a 200 OK response with an array of EI job identifiers. - -**Figure 5.3.4.2.1-1 Query EI job identifiers operation** - -- 1) The A1-EI Consumer shall send an HTTP GET request to the A1-EI Producer. The target URI shall identify the resource "/eijobs". The message body shall be empty. -- 2) The A1-EI Producer shall return the HTTP GET response. On success, "200 OK" shall be returned. The message body shall carry an array of EI job identifiers representing all available EI jobs of the given EI type, or of all EI types. On failure, the appropriate error code shall be returned, and the response message body may contain additional error information. - -To request EI job identifiers only related to a specific EI type, the A1-EI Consumer includes the eiTypeId as a query parameter in the GET request. - -##### 5.3.4.2.2 Query EI job identifiers procedure - -The procedure to query EI job identifiers is based on the Query EI job identifiers operation illustrated in figure 5.3.4.2.1-1. - -#### 5.3.4.3 Create EI job - -##### 5.3.4.3.1 General - -The A1-EI Consumer uses the Create EI job operation to create an EI job. - -The operation to create an EI job is based on HTTP PUT. The EI job to be created is identified with a URI that includes the eiJobId and the message body contains the EiJobObject. The format of the EiJobObject is checked, and the request is either accepted or rejected. If accepted, delivery of EI results will start based on the content and conditions defined in the EI job. - -NOTE: In case an EI job already exists for the provided URI, the PUT request is handled as for Update EI job (see clause 5.3.4.4.1). - -![Sequence diagram for Create EI job operation. The diagram shows two lifelines: A1-EI Producer and A1-EI Consumer. The interaction consists of two steps: 1. The A1-EI Consumer sends a PUT request to the A1-EI Producer with the URI .../eijobs/{eiJobId} and an EiJobObject body. 2. The A1-EI Producer responds with a 201 Created OK status and an EiJobObject body.](366a77fdefb0097b3289b4a011911390_img.jpg) - -``` - -sequenceDiagram - participant A1-EI Consumer - participant A1-EI Producer - Note left of A1-EI Consumer: A1-EI Consumer - Note right of A1-EI Producer: A1-EI Producer - A1-EI Consumer->>A1-EI Producer: 1. PUT .../eijobs/{eiJobId} (EiJobObject) - A1-EI Producer-->>A1-EI Consumer: 2. 201 Created OK (EiJobObject) - -``` - -Sequence diagram for Create EI job operation. The diagram shows two lifelines: A1-EI Producer and A1-EI Consumer. The interaction consists of two steps: 1. The A1-EI Consumer sends a PUT request to the A1-EI Producer with the URI .../eijobs/{eiJobId} and an EiJobObject body. 2. The A1-EI Producer responds with a 201 Created OK status and an EiJobObject body. - -**Figure 5.3.4.3.1-1 Create EI job operation** - -- 1) The A1-EI Consumer shall generate the eiJobId and send an HTTP PUT request to the A1-EI Producer. The target URI shall identify the resource (eiJobId) be created under the resource "/eijobs". The message body shall carry an EiJobObject. -- 2) The A1-EI Producer shall return the HTTP PUT response. On success, "201 Created" shall be returned. The "Location" HTTP header shall be present and shall carry the URI of the new EI job and the message body shall carry the EiJobObject. On failure, the appropriate error code shall be returned, and the message body may contain additional error information. - -The A1-EI Consumer may subscribe to EI job status notifications related to the created EI job. EI job status notifications are subscribed to by including the jobStatusNotificationUri in the EiJobObject. - -On reception of an eiTypeId that does not exist, "404 Not Found" shall be returned. - -On failure to validate the EiJobObject, "400 Bad Request" shall be returned. - -In case the new EI job would be identical to, or would be overlapping or conflicting with, an existing EI job, "409 Conflict" shall be returned. - -##### 5.3.4.3.2 Create EI job procedure - -The procedure to create EI job is based on the Create EI job operation illustrated in figure 5.3.4.3.1-1. - -#### 5.3.4.4 Update EI job - -##### 5.3.4.4.1 General - -The A1-EI Consumer uses the Update EI job operation to update an EI job. - -The operation to update a single EI job is based on HTTP PUT. The EI job to be updated is identified with a URI that includes the eiJobId and the message body contains the EiJobObject for the updated EI job. - -NOTE: In case an EI job does not exist for the provided URI, the PUT request is handled as for Create EI job (see clause 5.3.4.3.1). - -![Sequence diagram for Update EI job operation. It shows two lifelines: A1-EI Producer and A1-EI Consumer. Step 1: A1-EI Consumer sends a PUT request to A1-EI Producer with the URI .../eijobs/{eiJobId} and an EiJobObject body. Step 2: A1-EI Producer responds with a 200 OK status and the updated EiJobObject body.](552265bdbcf6d43d341fd018a9076269_img.jpg) - -``` - -sequenceDiagram - participant A1-EI Consumer - participant A1-EI Producer - Note left of A1-EI Consumer: A1-EI Consumer - A1-EI Consumer->>A1-EI Producer: 1. PUT .../eijobs/{eiJobId} (EiJobObject) - Note right of A1-EI Producer: A1-EI Producer - A1-EI Producer-->>A1-EI Consumer: 2. 200 OK (EiJobObject) - Note right of A1-EI Consumer: A1-EI Consumer - -``` - -Sequence diagram for Update EI job operation. It shows two lifelines: A1-EI Producer and A1-EI Consumer. Step 1: A1-EI Consumer sends a PUT request to A1-EI Producer with the URI .../eijobs/{eiJobId} and an EiJobObject body. Step 2: A1-EI Producer responds with a 200 OK status and the updated EiJobObject body. - -**Figure 5.3.4.4.1-1 Update EI job operation** - -- 1) The A1-EI Consumer shall send an HTTP PUT request to the A1-EI Producer. The target URI shall identify the EI job to be updated based on the eiJobId under the resource "/eijobs". The message body shall contain an EiJobObject. -- 2) The A1-EI Producer shall return the HTTP PUT response. On success, "200 OK" shall be returned. The message body shall carry an EiJobObject representing the updated EI job. On failure, the appropriate error code shall be returned, and the response message body may contain additional error information. - -The A1-EI Consumer may subscribe to EI job status notifications related to the updated EI job. EI job status notifications are subscribed to by including the jobStatusNotificationUri in the EiJobObject. The A1-EI Consumer may change the jobStatusNotificationUri for EI job status notifications in an update EI job request. The A1-EI Consumer may cancel EI job status notifications. EI job status notifications are cancelled by omitting jobStatusNotificationUri in the EiJobObject. - -On failure to validate the EiJobObject, "400 Bad Request" shall be returned. - -In case the EI job after update would be identical to, or would be overlapping or conflicting with, an existing EI job, "409 Conflict" shall be returned. - -##### **5.3.4.4.2 Update EI job procedure** - -The procedure to update EI job is based on the Update EI job operation illustrated in figure 5.3.4.4.1-1. - -#### **5.3.4.5 Query EI job** - -##### **5.3.4.5.1 General** - -The A1-EI Consumer uses the Query EI job operation to read an EI job. - -The operation to query an EI job is based on HTTP GET. The EI job to be read is identified with a URI that includes the eiJobId while the message body is empty, and the response returns the EI job object. - -![Sequence diagram for Query EI job operation. It shows two lifelines: A1-EI Producer and A1-EI Consumer. Step 1: A1-EI Consumer sends a GET request to A1-EI Producer with the URI .../eijobs/{eiJobId}. Step 2: A1-EI Producer responds with a 200 OK status and the EiJobObject body.](f7d969388c4f7e30cd04a061314bfa0e_img.jpg) - -``` - -sequenceDiagram - participant A1-EI Consumer - participant A1-EI Producer - Note left of A1-EI Consumer: A1-EI Consumer - A1-EI Consumer->>A1-EI Producer: 1. GET .../eijobs/{eiJobId} - Note right of A1-EI Producer: A1-EI Producer - A1-EI Producer-->>A1-EI Consumer: 2. 200 OK (EiJobObject) - Note right of A1-EI Consumer: A1-EI Consumer - -``` - -Sequence diagram for Query EI job operation. It shows two lifelines: A1-EI Producer and A1-EI Consumer. Step 1: A1-EI Consumer sends a GET request to A1-EI Producer with the URI .../eijobs/{eiJobId}. Step 2: A1-EI Producer responds with a 200 OK status and the EiJobObject body. - -**Figure 5.3.4.5.1-1 Query EI job operation** - -- 1) The A1-EI Consumer shall send an HTTP GET request to the A1-EI Producer. The target URI shall identify the EI job to be read based on the eiJobId under the resource "/eijobs". The message body shall be empty. - -- 2) The A1-EI Producer shall return the HTTP GET response. On success, "200 OK" shall be returned. The message body shall carry an EiJobObject representing the read EI job. On failure, the appropriate error code shall be returned, and the response message body may contain additional error information. - -On reception of eiJobId for which no EI job exists, "404 Not Found" shall be returned. - -##### **5.3.4.5.2 Query EI job procedure** - -The procedure to query EI job is based on the Query EI job operation illustrated in figure 5.3.4.5.1-1. - -#### **5.3.4.6 Delete EI job** - -##### **5.3.4.6.1 General** - -The A1-EI Consumer uses the Delete EI job operation to delete an EI job. - -The operation to delete an EI job is based on HTTP DELETE. The EI job to be deleted is identified with a URI that includes the eiJobId. Neither request nor response contain any EI job object in the message body. - -![Sequence diagram for Delete EI job operation showing A1-EI Consumer sending a DELETE request to A1-EI Producer and receiving a 204 response.](f1fbb1287d999c7034742de35bdab836_img.jpg) - -``` - -sequenceDiagram - participant A1-EI Consumer - participant A1-EI Producer - Note left of A1-EI Consumer: - A1-EI Consumer->>A1-EI Producer: 1. DELETE .../eijobs/{eiJobId} - Note right of A1-EI Producer: - A1-EI Producer-->>A1-EI Consumer: 2. 204 No content - Note right of A1-EI Consumer: - -``` - -Sequence diagram for Delete EI job operation showing A1-EI Consumer sending a DELETE request to A1-EI Producer and receiving a 204 response. - -**Figure 5.3.4.6.1-1 Delete EI job operation** - -- 1) The A1-EI Consumer shall send an HTTP DELETE request to the A1-EI Producer. The target URI shall identify the EI job to be deleted based on the eiJobId under the resource "/eijobs". The message body shall be empty. -- 2) The A1-EI Producer shall return the HTTP DELETE response. On success, "204 No Content" shall be returned. The message body shall be empty. On failure, the appropriate error code shall be returned, and the response message body may contain additional error information. - -On reception of eiJobId for which no EI job exists, "404 Not Found" shall be returned. - -##### **5.3.4.6.2 Delete EI job procedure** - -The procedure to delete EI job is based on the Delete EI job operation illustrated in figure 5.3.4.6.1-1. - -#### **5.3.4.7 Query EI job status** - -##### **5.3.4.7.1 General** - -The A1-EI Consumer uses the Query EI job status operation to query the status of an EI job. - -The operation to query status for an EI job is based on HTTP GET. The EI job for which status is to be read is identified with a URI that includes the eiJobId while the message body is empty, and the response returns an EI job status object. - -![Sequence diagram for Figure 5.3.4.7.1-1: Query EI job status operation. It shows an A1-EI Consumer sending a GET request to an A1-EI Producer, and the producer responding with a 200 OK status object.](a149b400127a3e3e50b3c98d27c5935c_img.jpg) - -``` - -sequenceDiagram - participant A1-EI Consumer - participant A1-EI Producer - Note left of A1-EI Consumer: A1-EI Consumer - Note right of A1-EI Producer: A1-EI Producer - A1-EI Consumer->>A1-EI Producer: 1. GET .../eijobs/{eiJobId}/status - A1-EI Producer-->>A1-EI Consumer: 2. 200 OK (EiJobStatusObject) - -``` - -Sequence diagram for Figure 5.3.4.7.1-1: Query EI job status operation. It shows an A1-EI Consumer sending a GET request to an A1-EI Producer, and the producer responding with a 200 OK status object. - -**Figure 5.3.4.7.1-1 Query EI job status operation** - -- 1) The A1-EI Consumer shall send an HTTP GET request to the A1-EI Producer. The target URI shall identify the EI job for which status is to be read based on the eiJobId under the resource "/eijobs". The message body shall be empty. -- 2) The A1-EI Producer shall return the HTTP GET response. On success, "200 OK" shall be returned. The message body shall carry an EI job status object representing the status of the EI job. On failure, the appropriate error code shall be returned, and the response message body may contain additional error information. - -On reception of eiJobId for which no EI job status exists, "404 Not Found" shall be returned. - -##### **5.3.4.7.2 Query EI job status procedure** - -The procedure to query EI job status is based on the Query EI job status operation illustrated in figure 5.3.4.7.1-1. - -#### **5.3.4.8 Notify EI job status** - -##### **5.3.4.8.1 General** - -The A1-EI Producer uses the Notify EI job status operation to notify the A1-EI Consumer about changes in status of an EI job. All notifications are sent to the URI for notification handling provided during EI job creation and the EiJobStatusObject contains the information about the status of the EI job. - -The operation to notify EI job status is based on HTTP POST. The URI contains the target resource for EI job status notification handling. The notification content is represented in an EI job status object that is included in the message body. - -![Sequence diagram for Figure 5.3.4.8.1-1: Notify EI job status operation. It shows an A1-EI Producer sending a POST request with an EiJobStatusObject to an A1-EI Consumer, and the consumer responding with a 204 No Content status.](6929132b4964d52244da61d4614bc4d6_img.jpg) - -``` - -sequenceDiagram - participant A1-EI Producer - participant A1-EI Consumer - Note left of A1-EI Producer: A1-EI Producer - Note right of A1-EI Consumer: A1-EI Consumer - A1-EI Producer->>A1-EI Consumer: 1. POST {jobStatusNotificationUri} (EiJobStatusObject) - A1-EI Consumer-->>A1-EI Producer: 2. 204 No Content - -``` - -Sequence diagram for Figure 5.3.4.8.1-1: Notify EI job status operation. It shows an A1-EI Producer sending a POST request with an EiJobStatusObject to an A1-EI Consumer, and the consumer responding with a 204 No Content status. - -**Figure 5.3.4.8.1-1 Notify EI job status operation** - -- 1) The A1-EI Producer shall send an HTTP POST request to the A1-EI Consumer. The target URI (jobStatusNotificationUri) identifies the sink for EI job status notifications. The message body shall contain an EI job status object. -- 2) The A1-EI Consumer shall return the HTTP POST response with "204 No Content". The response message body shall be empty. - -On failure to validate the EiJobStatusObject fails, "400 Bad Request" shall be returned, and the response message body may contain additional error information. - -##### 5.3.4.8.2 Notify EI job status procedure - -The procedure to notify EI job status is based on the Notify EI job status operation illustrated in figure 5.3.4.8.1-1. - -### 5.3.5 Service operations for A1 EI job result - -#### 5.3.5.1 Introduction - -Table 5.3.5.1-1 describes the mapping between the A1 EI job result operations, and the HTTP methods used to realise them, and the mandatory HTTP status codes. - -**Table 5.3.5.1-1 A1 EI operations to HTTP methods mapping.** - -| Service operation | HTTP method | HTTP status codes | -|-----------------------|-------------|-------------------| -| Deliver EI job result | POST | 204, 400 | - -The following clauses describe the A1 EI job result operations. For further information on the EI job result objects transferred in the HTTP message bodies, see A1TD [4], clause 8.4.4. - -The purpose of the A1EI job result operations is to enable the A1-EI Producer to deliver EI job results according to the service description agreed during job creation. The URL to which the EI job result is delivered is transferred from the A1-EI consumer in the EI job object. - -#### 5.3.5.2 Deliver EI job result - -##### 5.3.5.2.1 General - -The A1-EI Producer uses the Deliver EI job result operation to deliver EI job results using push-based method. - -The push-based delivery method of EI is based on subscribe-notify paradigm where the EI job creation corresponds to the subscription and the delivery of EI job result is made using HTTP POST in the same way as notifications. - -As specified in the EI job definition, the EI job results can be delivered in a single push or in several that are repeated with regular intervals or irregularly based on events. - -The operation to deliver EI job result is based on HTTP POST. The URI contains the target resource for EI job result handling. The delivered content is represented by an EI job result object. - -![Sequence diagram showing the Deliver EI job result operation between A1-EI Producer and A1-EI Consumer. Step 1: POST {jobResultUri} (EIJobResultObject) from Producer to Consumer. Step 2: 204 No Content response from Consumer to Producer.](e266d0e53f36cd41c30f1bb5c8a11c84_img.jpg) - -``` - -sequenceDiagram - participant A1-EI Producer - participant A1-EI Consumer - Note left of A1-EI Producer: A1-EI Producer - Note right of A1-EI Consumer: A1-EI Consumer - A1-EI Producer->>A1-EI Consumer: 1. POST {jobResultUri} (EIJobResultObject) - A1-EI Consumer-->>A1-EI Producer: 2. 204 No Content - Note left of A1-EI Producer: A1-EI Producer - Note right of A1-EI Consumer: A1-EI Consumer - -``` - -Sequence diagram showing the Deliver EI job result operation between A1-EI Producer and A1-EI Consumer. Step 1: POST {jobResultUri} (EIJobResultObject) from Producer to Consumer. Step 2: 204 No Content response from Consumer to Producer. - -**Figure 5.3.5.2.1-1 Deliver EI job result operation** - -- 1) The A1-EI Producer shall send an HTTP POST request to the A1-EI Consumer. The target URI (jobResultUri) identifies the sink for EI job result deliveries. The message body shall contain an EI job result object. - -- 2) The A1-EI Consumer shall return the HTTP POST response with "204 No Content". The response message body shall be empty. - -On failure to validate the EiJobResultObject fails, "400 Bad Request" shall be returned, and the response message body may contain additional error information. - -##### **5.3.5.2.2 Deliver EI job result procedure** - -The procedure to deliver EI job result is based on the Deliver EI job result operation illustrated in figure 5.3.5.2.1-1. - -## 5.4 ML model management service - -### 5.4.1 Introduction - -The A1-ML service defines service operations that are used for two sets of use cases, Near-RT RIC as A1-ML Consumer and Non-RT RIC as A1-ML Consumer, as specified in A1UCR [1], clauses 8 and 9. - -### 5.4.2 Service description - -#### 5.4.2.1 Functional elements - -The A1 application protocol for A1-ML is based on signalling between the A1-ML Consumer residing in the Near-RT RIC and the A1-ML Producer residing in the Non-RT RIC, as well as signalling between the A1-ML Consumer residing in the Non-RT RIC and the A1-ML Producer residing in the Near-RT RIC. Both the A1-ML Consumer and the A1-ML Producer contain an HTTP Client and an HTTP Server. - -![Diagram showing HTTP roles in service framework. It depicts two boxes: 'A1-ML Producer' at the top and 'A1-ML Consumer' at the bottom. Each box contains an 'HTTP Server' and an 'HTTP Client'. Arrows show requests from clients to servers and responses from servers to clients. On the left, GET, POST, and DELETE methods are listed. On the right, a POST request is shown from the Consumer's HTTP Client to the Producer's HTTP Server. A list of paths is on the far left: .../training-jobs, .../training-jobs/{trainingJobId}, .../training-jobs/{trainingJobId}/status, .../training-capabilities. A label {trainingJobStatusNotificationUri} points to the Consumer's HTTP Server.](68d8089266ace7197304b43dcaf5d08e_img.jpg) - -Diagram showing HTTP roles in service framework. It depicts two boxes: 'A1-ML Producer' at the top and 'A1-ML Consumer' at the bottom. Each box contains an 'HTTP Server' and an 'HTTP Client'. Arrows show requests from clients to servers and responses from servers to clients. On the left, GET, POST, and DELETE methods are listed. On the right, a POST request is shown from the Consumer's HTTP Client to the Producer's HTTP Server. A list of paths is on the far left: .../training-jobs, .../training-jobs/{trainingJobId}, .../training-jobs/{trainingJobId}/status, .../training-capabilities. A label {trainingJobStatusNotificationUri} points to the Consumer's HTTP Server. - -NOTE: Arrows indicate direction of HTTP requests sent from HTTP Client to HTTP Server and HTTP responses sent from HTTP Server to HTTP Client. - -**Figure 5.4.2.1-1 HTTP roles in service framework** - -The present document specifies the A1 ML model procedures defined in A1GAP [2], clause 6.4 using HTTP operations in accordance with A1TP [3], clause 8. - -#### 5.4.2.2 Principles for ML model management - -The following principles are used for A1 ML model management: - -- the A1-ML Producer indicates the AI/ML capabilities that are available; -- information about training capabilities can be queried.; - -- a training job can be created for an available training capability; -- a training job corresponds to a resource (in the REST sense); -- a training job is identified by a training job identifier; -- the training job identifier is assigned by the A1-ML Producer when the training job is created; -- status for a specific training job can be queried, and notifications can be subscribed to when the training job is requested by providing a callback URI in the create training job operation. - -#### 5.3.2.3 Representation objects - -The following JSON objects are used within the service operations of the A1-ML service: - -##### ProblemDetails - -The problem details object is the JSON representation of the content in a response message with other HTTP error response codes (4xx/5xx). - -#### 5.4.2.4 Resource identifiers - -The URI for ML model training jobs is: - -.../training-jobs - -A single training job is identified by adding the value of the training identifier the URI: - -.../training-jobs/{trainingJobId} - -The URI for status of a single training job is: - -.../training-jobs/{trainingJobId}/status - -The URI for training job status notification is referred to as the trainingJobStatusNotificationUri and is a callback URI provided when creating a training job. - -The URI for information on training capabilities is: - -.../training-capabilities - -### 5.4.3 Service operations for A1 ML model management - -#### 5.4.3.1 Introduction - -Table 5.4.3.1-1 describes the mapping between the A1 ML model management operations, and the HTTP methods used to realise them, and the mandatory HTTP status codes. - -**Table 5.4.3.1-1 A1 ML operations to HTTP methods mapping** - -| Service operation | HTTP method | HTTP status codes | -|-----------------------------------------|-------------|-------------------| -| Create AI/ML model training job | POST | 201, 400 | -| Cancel AI/ML model training job | DELETE | 200, 404 | -| Query AI/ML model training job status | GET | 200, 404 | -| Notify AI/ML model training job status | POST | 204, 400 | -| Query AI/ML model training capabilities | GET | 200 | - -#### 5.4.3.2 Create AI/ML model training job - -##### 5.4.3.2.1 General - -The A1-ML Consumer uses this operation to create AI/ML model training job. - -The operation to create AI/ML model training job is based on HTTP POST. - -![Sequence diagram for Create AI/ML model training job operation. It shows an A1-ML Consumer sending a POST request to an A1-ML Producer, which responds with a 201 Created status.](98e54d5540b2efe3e24af3cf936bc4ea_img.jpg) - -``` - -sequenceDiagram - participant A1-ML Consumer - participant A1-ML Producer - Note left of A1-ML Consumer: A1-ML Consumer - Note right of A1-ML Producer: A1-ML Producer - A1-ML Consumer->>A1-ML Producer: 1. POST .../training-jobs (TrainingJobInfo) - A1-ML Producer-->>A1-ML Consumer: 2. 201 Created (TrainingJobInfo) - Note left of A1-ML Consumer: A1-ML Consumer - Note right of A1-ML Producer: A1-ML Producer - -``` - -Sequence diagram for Create AI/ML model training job operation. It shows an A1-ML Consumer sending a POST request to an A1-ML Producer, which responds with a 201 Created status. - -**Figure 5.4.3.2.1-1: Create AI/ML model training job operation** - -The service operation is as follows: - -1. The A1-ML Consumer shall send an HTTP POST request to the A1-ML Producer. The target URI shall identify the resource “/training-jobs“, under which the new training job is to be created. The message content shall carry a TrainingJobInfo structure. -2. The A1-ML Producer shall return the HTTP POST response. On success, "201 Created" shall be returned. The "Location" HTTP header shall be present and shall carry the URI of the new training job resource with the assigned trainingJobId. The message content shall carry the TrainingJobInfo. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -On failure to validate the TrainingJobInfo, "400 Bad Request" shall be returned. - -##### 5.4.3.2.2 Request training procedure - -The procedure to request training is based on the Create AI/ML model training job operation illustrated in figure 5.4.3.2.1-1. - -#### 5.4.3.3 Delete AI/ML model training job - -##### 5.4.3.3.1 General - -When an AI/ML model training is ongoing, the A1-ML Consumer uses this operation to cancel the AI/ML model training, and delete the existing AI/ML model training job. - -The operation to delete an AI/ML model training job is based on HTTP DELETE. - -![Sequence diagram for Delete AI/ML model training job operation. It shows an A1-ML Consumer sending a DELETE request to an A1-ML Producer, which responds with a 204 No Content status.](8d33918c43de10bb6d76f330c4f10e69_img.jpg) - -``` - -sequenceDiagram - participant A1-ML Consumer - participant A1-ML Producer - Note left of A1-ML Consumer: A1-ML Consumer - Note right of A1-ML Producer: A1-ML Producer - A1-ML Consumer->>A1-ML Producer: 1. DELETE .../training-jobs/{trainingJobId} - A1-ML Producer-->>A1-ML Consumer: 2. 204 No Content - Note left of A1-ML Consumer: A1-ML Consumer - Note right of A1-ML Producer: A1-ML Producer - -``` - -Sequence diagram for Delete AI/ML model training job operation. It shows an A1-ML Consumer sending a DELETE request to an A1-ML Producer, which responds with a 204 No Content status. - -**Figure 5.4.3.3.1-1: Delete AI/ML model training job operation** - -The service operation is as follows: - -1. The A1-ML Consumer shall send an HTTP DELETE request to the A1-ML Producer. The target URI shall identify the resource /training-jobs/{trainingJobId}, where trainingJobId is the identifier of the training job to be deleted. -2. The A1-ML Producer shall return the HTTP DELETE response. On success, the A1-ML Producer shall return HTTP status code 204 No content. If the specified trainingJobId does not exist, the A1-ML Producer shall return 404 Not Found. On failure, appropriate error codes shall be returned, and the message content may contain additional error information. - -##### **5.4.3.3.2 Cancel training procedure** - -The procedure to cancel training is based on the Delete training job operation illustrated in figure 5.4.3.3.1-1. - -#### **5.4.3.4 Query AI/ML model training job status** - -##### **5.4.3.4.1 General** - -The A1-ML Consumer uses the Query AI/ML model training job status operation to query the status of an AI/ML model training job. - -The operation to query status for an AI/ML model training job is based on HTTP GET. The AI/ML model training job for which status is to be read is identified with a URI that includes the trainingJobId while the message body is empty, and the response returns the status of the AI/ML model training job. - -![Sequence diagram showing the Query AI/ML model training status operation. The A1-ML Consumer sends a GET request to the A1-ML Producer, and the A1-ML Producer returns a 200 OK response with TrainingJobStatus.](04c7ffb4a475a374f52b88704ecd295f_img.jpg) - -``` - -sequenceDiagram - participant A1-ML Consumer - participant A1-ML Producer - Note left of A1-ML Consumer: A1-ML Consumer - Note right of A1-ML Producer: A1-ML Producer - A1-ML Consumer->>A1-ML Producer: 1. GET .../training-jobs/{trainingJobId}/status - A1-ML Producer-->>A1-ML Consumer: 2. 200 OK (TrainingJobStatus) - Note left of A1-ML Consumer: A1-ML Consumer - Note right of A1-ML Producer: A1-ML Producer - -``` - -Sequence diagram showing the Query AI/ML model training status operation. The A1-ML Consumer sends a GET request to the A1-ML Producer, and the A1-ML Producer returns a 200 OK response with TrainingJobStatus. - -**Figure 5.4.3.4.1-1 Query AI/ML model training status operation** - -- 1) The A1-ML Consumer shall send an HTTP GET request to the A1-ML Producer. The target URI shall identify the AI/ML model training job for which status is to be read based on the trainingJobId under the resource "/training-jobs". The message body shall be empty. -- 2) The A1-ML Producer shall return the HTTP GET response. On success, "200 OK" shall be returned. The message body shall carry a TrainingJobStatus representing the status of the AI/ML model training job. On failure, the appropriate error code shall be returned, and the response message body may contain additional error information. - -On reception of trainingJobId for which no AI/ML model training job status exists, "404 Not Found" shall be returned. - -##### **5.4.3.4.2 Query AI/ML model training job status procedure** - -The procedure to query AI/ML model training job status is based on the Query AI/ML model training job operation illustrated in figure 5.4.3.4.1-1. - -#### 5.4.3.5 Notify AI/ML model training job status - -##### 5.4.3.5.1 General - -The A1-ML Producer uses this operation to notify AI/ML model training job status. - -The operation to notify AI/ML model training job status is based on HTTP POST. - -![Sequence diagram showing the interaction between A1-ML Consumer and A1-ML Producer for job status notification. Step 1: A1-ML Producer sends a POST request to A1-ML Consumer. Step 2: A1-ML Consumer responds with 204 No Content.](dbbc0baac7341cda76cc4f8355dce23f_img.jpg) - -``` - -sequenceDiagram - participant A1-ML Consumer - participant A1-ML Producer - Note left of A1-ML Consumer: A1-ML Consumer - Note right of A1-ML Producer: A1-ML Producer - A1-ML Producer->>A1-ML Consumer: 1. POST {trainingJobStatusNotificationUri} (TrainingJobStatus) - A1-ML Consumer-->>A1-ML Producer: 2. 204 No Content - -``` - -Sequence diagram showing the interaction between A1-ML Consumer and A1-ML Producer for job status notification. Step 1: A1-ML Producer sends a POST request to A1-ML Consumer. Step 2: A1-ML Consumer responds with 204 No Content. - -**Figure 5.4.3.5.1-1: Notify AI/ML model training job status operation** - -The service operation is as follows: - -1. The A1-ML Producer shall send an HTTP POST request to the A1-ML Consumer. The target URI (trainingJobStatusNotificationUri) identifies the sink for AI/ML model training job status notifications. The message body shall carry a TrainingJobStatus representing the status of the AI/ML model training job. -2. The A1-ML Consumer shall return the HTTP POST response with "204 No Content". The response message body shall be empty. - -On failure to validate the TrainingJobStatus, "400 Bad Request" shall be returned, and the response message body may contain additional error information. - -##### 5.4.3.5.2 Notify AI/ML model training job status procedure - -The procedure to notify AI/ML model training job status is based on the Notify AI/ML model training job status operation illustrated in figure 5.4.3.5.1-1. - -#### 5.4.3.6 Query AI/ML model training capabilities - -##### 5.4.3.6.1 General - -The A1-ML Consumer uses this operation to query AI/ML model training capabilities. - -The operation to query AI/ML model training capabilities is based on HTTP GET. - -![Sequence diagram showing the interaction between an A1-ML Consumer and an A1-ML Producer. The Consumer sends a GET request for training capabilities, and the Producer responds with a 200 OK containing an array of TrainingCapabilityInfo.](cfb98c691c1af5befe32ff9442eea511_img.jpg) - -``` - -sequenceDiagram - participant A1-ML Consumer - participant A1-ML Producer - Note left of A1-ML Consumer: A1-ML Consumer - Note right of A1-ML Producer: A1-ML Producer - A1-ML Consumer->>A1-ML Producer: 1. GET .../training-capabilities - A1-ML Producer-->>A1-ML Consumer: 2. 200 OK (array(TrainingCapabilityInfo)) - Note left of A1-ML Consumer: A1-ML Consumer - Note right of A1-ML Producer: A1-ML Producer - -``` - -Sequence diagram showing the interaction between an A1-ML Consumer and an A1-ML Producer. The Consumer sends a GET request for training capabilities, and the Producer responds with a 200 OK containing an array of TrainingCapabilityInfo. - -**Figure 5.4.3.6.1-1: Query AI/ML model training capabilities operation** - -The service operation is as follows: - -1. The A1-ML Consumer shall send an HTTP GET request to the A1-ML Producer. The target URI shall identify the resource "/training-capabilities" and may also contain optional filtering criteria. -2. The A1-ML Producer shall return the HTTP GET response. On success, "200 OK" shall be returned. The message content shall carry the array(TrainingCapabilityInfo) that match the given filter criteria. On failure, the appropriate error code shall be returned, and the response message body may contain additional error information. - -##### 5.4.3.6.2 Query AI/ML model training capabilities procedure - -The procedure to query AI/ML model training capabilities is based on the Query AI/ML model training capabilities operation illustrated in figure 5.4.3.6.1-1. - -# 6 API Definitions - -## 6.1 Introduction - -### 6.1.1 Encoding of attributes in A1 data types - -Identifiers and parameters that have been defined as integers are, when used over the A1 interface, encoded as JSON "number". - -Identifiers and parameters that have a hexadecimal or octet string representation are, when used over the A1 interface, encoded as JSON "string" with character ordering preserved and zeros filling rules followed. - -### 6.1.2 Compatibility of API versions for A1 services - -The API name for each of the A1 services is defined in the following clauses. The API version number is visible in the OpenAPI document in Annex A where the major field is defined in the following clauses. Based on the versioning rules defined by SemVer [8], this implies that implementations of an A1 service in the Non/Near-RT RICs are - -- compatible if the major field of the API version numbers are the same and any difference between the sets of supported features is handled within the API version itself; or -- not compatible in case the major field of the API version numbers are different. - -The history of the introduction of an A1 service, and new API versions, is captured in the Change History clause of the present document. The services and API versions specified in the present document are summarized in clause A.1.2. - -NOTE: Non/Near-RT RIC products that implement different API versions of an A1 service can be made compatible as it is possible to support several versions of an API at the same time where the different versions are addressed by separate URIs. - -### 6.1.3 URI structure - -The URI structure of APIs for A1 services is based on the design principles in 3GPP TS 29.501 [6], clause 4.4.1 where "apiName" is the name of the API and "apiVersion" indicates the major field of the API version number. - -## 6.2 A1-P (policy management) - -### 6.2.1 Introduction - -This clause contains the definition of the REST based API for the A1 policy management service. - -The name of the API is A1-P and for the API version defined in the present document the major field of the API version number is 2. - -Based on the URI structure defined in 3GPP TS 29.501 [6], clause 4.4.1 the request URI used in HTTP request from the A1-P consumer towards the A1-P producer shall have the following structure: - -**{apiRoot}/A1-P/v2/** - -where the "ResourceUriPart" shall be as defined in clause 6.2.3. - -### 6.2.2 Usage of HTTP - -#### 6.2.2.1 General - -The A1 Transport, HTTP protocol and security requirements, is described in A1TP [3]. - -#### 6.2.2.2 HTTP standard headers - -Encodings and applicable MIME media type for the related Content-Type header are not specified in this version of the present document. - -#### 6.2.2.3 HTTP custom headers - -No HTTP custom headers are specified in this version of the present document. - -### 6.2.3 Resources - -#### 6.2.3.1 Overview - -##### 6.2.3.1.1 Resource URI structure - -The resource URI structure for the A1-P API is illustrated in figure 6.2.3.1.1-1. - -![A hierarchical tree diagram showing the resource URI structure of the A1-P API. The root is {apiRoot}/A1-P/v2. It branches to /policytypes, which branches to /{policyTypeId}, which branches to /policies, which branches to /{policyId}, which finally branches to /status.](1142ba0197b158bb198186fe8baccc32_img.jpg) - -``` - - graph TD - Root["{apiRoot}/A1-P/v2"] --> PolicyTypes["/policytypes"] - PolicyTypes --> PolicyTypeId["/{policyTypeId}"] - PolicyTypeId --> Policies["/policies"] - Policies --> PolicyId["/{policyId}"] - PolicyId --> Status["/status"] - -``` - -A hierarchical tree diagram showing the resource URI structure of the A1-P API. The root is {apiRoot}/A1-P/v2. It branches to /policytypes, which branches to /{policyTypeId}, which branches to /policies, which branches to /{policyId}, which finally branches to /status. - -**Figure 6.2.3.1.1-1: Resource URI structure of the A1-P API** - -##### **6.2.3.1.2 Resources and methods** - -Table 6.2.3.1.2-1 provides an overview of the resources and HTTP methods defined for the A1-P API. - -**Table 6.2.3.1.2-1: Resources and methods overview** - -| Resource name | Resource URI | HTTP method or custom operation | Description | -|---------------------------------|--------------------------------------------------------|---------------------------------|--------------------------------------------| -| All Policy Type Identifiers | /policytypes | GET | Query all policy type identifiers | -| Individual Policy Type Object | /policytypes/{policyTypeId} | GET | Query single policy type | -| Individual Policy Object | /policytypes/{policyTypeId}/policies/{policyId} | PUT | Create single policy, Update single policy | -| | | GET | Query single policy | -| | | DELETE | Delete single policy | -| Individual Policy Status Object | /policytypes/{policyTypeId}/policies/{policyId}/status | GET | Query policy status | -| All Policy Identifiers | /policytypes/{policyTypeId}/policies | GET | Query all policy identifiers | - -For each combination of a resource and an HTTP method in table 6.2.3.1.2-1, the HTTP status codes are as defined for the A1 policy procedures listed in the Description column and defined in clauses 5.2.3 and 5.2.4. For any other combination of a resource defined for this API and an HTTP method, including those HTTP methods that are not defined for this API, the HTTP status code 405 (Method Not Allowed) shall be used to indicate that the method is not supported on the resource. - -##### **6.2.3.1.3 Policy type identifier** - -The PolicyTypeId is constructed based on two parts separated by "\_" (underscore): - -`typename_version` - -where - -`typename` is the unique label of the policy type; - -`version` is the version of the policy type defined as major.minor.patch as described in SemVer [8]. - -The typename and version is assigned, and their uniqueness ensured, by the organizational entity that is responsible for the definition and maintenance of the policy type definition. - -NOTE: The typename can be based on a prefix that indicates the organizational entity (e.g. O-RAN or a company designator) and a text string that can be descriptive of the class, use case or variant of the policy type. - -#### 6.2.3.2 Individual Policy Object - -##### 6.2.3.2.0 General - -The name of the resource is the PolicyId assigned by the A1-P Consumer when the policy is created. - -##### 6.2.3.2.1 Description - -The resource represents an A1 policy. - -##### 6.2.3.2.2 Resource Definition - -The Resource URI and the supported resource variables are as defined in previous clauses. - -##### 6.2.3.2.3 Resource Standard Methods - -###### 6.2.3.2.3.1 HTTP PUT - -This method shall support the request data structures specified in table 6.2.3.2.3.1-1 and the response data structures and response codes specified in table 6.2.3.2.3.1-2. - -**Table 6.2.3.2.3.1-1: Data structures supported by the HTTP PUT Request Body on this resource** - -| Data type | P | Cardinality | Description | -|--------------|---|-------------|---------------| -| PolicyObject | M | 1 | Create policy | - -**Table 6.2.3.2.3.1-2: Data structures supported by the HTTP PUT Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|-----------------------|-------------------------------------------| -| PolicyObject | M | 1 | 201 Created
200 OK | Confirmation of created or updated policy | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -This method shall support the URI query parameters specified in table 6.2.3.2.3.1-3. - -**Table 6.2.3.2.3.1-3: URI query parameters supported by the HTTP PUT method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|-------------------------|-----------|---|-------------|-----------------------------------|----------------------| -| notificationDestination | string | O | 0..1 | Transfer of URL for notifications | Status notifications | - -This method shall support the response headers specified in table 6.2.3.2.3.1-4. - -**Table 6.2.3.2.3.1-4: Headers supported by the 201-response code on the resource** - -| Name | Data type | P | Cardinality | Description | -|----------|-----------|---|-------------|------------------------------------------------| -| Location | string | M | 1 | Contains the URI of the newly created resource | - -###### 6.2.3.2.3.2 HTTP GET - -This method shall support the request data structures specified in table 6.2.3.2.3.2-1 and the response data structures and response codes specified in table 6.2.3.2.3.2-2. - -**Table 6.2.3.2.3.2-1: Data structures supported by the HTTP GET Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|---------------------------------------------------------| -| N/A | | 0 | There is no object in the message body of a GET request | - -**Table 6.2.3.2.3.2-2: Data structures supported by the HTTP GET Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|------------------------------| -| PolicyObject | M | 1 | 200 OK | Requested policy object | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -###### 6.2.3.2.3.3 HTTP DELETE - -This method shall support the request data structures specified in table 6.2.3.2.3.3-1 and the response data structures and response codes specified in table 6.2.3.2.3.3-2. - -**Table 6.2.3.2.3.3-1: Data structures supported by the HTTP DELETE Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|------------------------------------------------------------| -| N/A | | | There is no object in the message body of a DELETE request | - -**Table 6.2.3.2.3.3-2: Data structures supported by the HTTP DELETE Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|-------------------------------------| -| N/A | | | 204 No content | Confirmation of successful deletion | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -###### 6.2.3.2.3.4 HTTP POST - -This method is not supported on the resource. - -##### 6.2.3.2.4 Resource Custom Operations - -No custom operations are defined. - -#### 6.2.3.3 Individual Policy Status Object - -##### 6.2.3.3.1 Description - -The resource represents the status of an A1 policy. - -##### 6.2.3.3.2 Resource Definition - -The Resource URI and the supported resource variables are as defined in previous clauses. - -##### 6.2.3.3.3 Resource Standard Methods - -###### 6.2.3.3.3.1 HTTP PUT - -Method is not supported on this resource. - -###### 6.2.3.3.3.2 HTTP GET - -This method shall support the request data structures specified in table 6.2.3.3.3.2-1 and the response data structures and response codes specified in table 6.2.3.3.3.2-2. - -**Table 6.2.3.3.3.2-1: Data structures supported by the HTTP GET Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|---------------------------------------------------------| -| N/A | | | There is no object in the message body of a GET request | - -**Table 6.2.3.3.3.2-2: Data structures supported by the HTTP GET Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|--------------------|---|-------------|----------------|--------------------------------| -| PolicyStatusObject | M | 1 | 200 OK | Requested policy status object | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -###### 6.2.3.3.3.3 HTTP DELETE - -Method is not supported on this resource. - -###### 6.2.3.3.3.4 HTTP POST - -Method is not supported on this resource. - -##### 6.2.3.3.4 Resource Custom Operations - -No custom operations are defined. - -#### 6.2.3.4 All Policy Identifiers - -##### 6.2.3.4.1 Description - -The resource represents A1 policy identifiers. - -##### 6.2.3.4.2 Resource Definition - -The Resource URI and the supported resource variables are as defined in previous clauses. - -##### 6.2.3.4.3 Resource Standard Methods - -###### 6.2.3.4.3.1 HTTP PUT - -Method is not supported on this resource. - -###### 6.2.3.4.3.2 HTTP GET - -This method shall support the request data structures specified in table 6.2.3.6.3.2-1 and the response data structures and response codes specified in table 6.2.3.6.3.2-2. - -**Table 6.2.3.4.3.2-1: Data structures supported by the HTTP GET Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|---------------------------------------------------------| -| N/A | | | There is no object in the message body of a GET request | - -**Table 6.2.3.4.3.2-2: Data structures supported by the HTTP GET Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|-----------------|---|-------------|----------------|------------------------------| -| array(PolicyId) | M | 0..N | 200 OK | All policy identifiers | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -###### **6.2.3.4.3.3 HTTP DELETE** - -Method is not supported on this resource. - -###### **6.2.3.4.3.4 HTTP POST** - -Method is not supported on this resource. - -##### **6.2.3.4.4 Resource Custom Operations** - -No custom operations are defined. - -#### **6.2.3.5 All Policy Type Identifiers** - -##### **6.2.3.5.1 Description** - -The resource represents A1 policy type identifiers. - -##### **6.2.3.5.2 Resource Definition** - -The Resource URI and the supported resource variables are as defined in previous clauses. - -##### **6.2.3.5.3 Resource Standard Methods** - -###### **6.2.3.5.3.1 HTTP PUT** - -Method is not supported on this resource. - -###### **6.2.3.5.3.2 HTTP GET** - -This method shall support the request data structures specified in table 6.2.3.5.3.2-1 and the response data structures and response codes specified in table 6.2.3.5.3.2-2. - -**Table 6.2.3.5.3.2-1: Data structures supported by the HTTP GET Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|---------------------------------------------------------| -| N/A | | | There is no object in the message body of a GET request | - -**Table 6.2.3.5.3.2-2: Data structures supported by the HTTP GET Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|---------------------|---|-------------|----------------|------------------------------| -| array(PolicyTypeId) | M | 0..N | 200 OK | All policy type identifiers | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -###### **6.2.3.5.3.3 HTTP DELETE** - -Method is not supported on this resource. - -###### **6.2.3.5.3.4 HTTP POST** - -Method is not supported on this resource. - -##### **6.2.3.5.4 Resource Custom Operations** - -No custom operations are defined. - -#### **6.2.3.6 Individual Policy Type Object** - -##### **6.2.3.6.1 Description** - -The resource represents an A1 policy type. - -##### **6.2.3.6.2 Resource Definition** - -The Resource URI and the supported resource variables are as defined in previous clauses. - -##### **6.2.3.6.3 Resource Standard Methods** - -###### **6.2.3.6.3.1 HTTP PUT** - -Method is not supported on this resource. - -###### **6.2.3.6.3.2 HTTP GET** - -This method shall support the request data structures specified in table 6.2.3.6.3.2-1 and the response data structures and response codes specified in table 6.2.3.6.3.2-2. - -**Table 6.2.3.6.3.2-1: Data structures supported by the HTTP GET Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|---------------------------------------------------------| -| N/A | | | There is no object in the message body of a GET request | - -**Table 6.2.3.6.3.2-2: Data structures supported by the HTTP GET Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|------------------|---|-------------|----------------|------------------------------| -| PolicyTypeObject | M | 1 | 200 OK | Requested policy type object | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -###### 6.2.3.6.3.3 HTTP DELETE - -This method is not supported on the resource. - -###### 6.2.3.6.3.4 HTTP POST - -This method is not supported on the resource. - -##### 6.2.3.6.4 Resource Custom Operations - -No custom operations are defined. - -### 6.2.4 Custom Operations without associated resources - -No custom operations are defined. - -### 6.2.5 Notifications - -#### 6.2.5.0 General - -Table 6.2.5.0-1 provides an overview of the callback URIs and HTTP methods defined for the A1-P API. - -**Table 6.2.5.0-1: Notifications overview** - -| Notification | Callback URI | HTTP method or custom operation | Description | -|----------------------------|---------------------------|---------------------------------|----------------------| -| Policy Status Notification | {notificationDestination} | POST | Notify policy status | - -For each combination of a callback URI and an HTTP method in table 6.2.5.0-1, the HTTP status codes are as defined for the procedure listed in the Description column and defined in clause 5.2.4.8. - -#### 6.2.5.1 Policy Status Notification - -##### 6.2.5.1.1 Description - -The Policy Status Notification is used by the A1-P Producer to report status changes and feedback about an A1 policy to A1-P Consumer that has subscribed to such notifications. - -##### 6.2.5.1.2 Target URI - -The Callback URI "{notificationDestination}" shall be used with the callback URI variables defined in table 6.2.5.1.2-1. - -**Table 6.2.5.1.2-1: Callback URI variables** - -| Name | Definition | -|-------------------------|-----------------------------------------------| -| notificationDestination | String formatted as URI with the Callback Uri | - -##### 6.2.5.1.3 Standard Methods - -###### 6.2.5.1.3.1 HTTP PUT - -Method is not supported for this target URI. - -###### 6.2.5.1.3.2 HTTP GET - -Method is not supported for this target URI. - -###### 6.2.5.1.3.3 HTTP DELETE - -Method is not supported for this target URI. - -###### 6.2.5.1.3.4 HTTP POST - -This method shall support the request data structures specified in table 6.2.5.1.3.4-1 and the response data structures and response codes specified in table 6.2.5.1.3.4-2. - -**Table 6.2.5.1.3.4-1: Data structures supported by the HTTP POST Request Body** - -| Data type | P | Cardinality | Description | -|--------------------|---|-------------|---------------| -| PolicyStatusObject | M | 1 | Notify policy | - -**Table 6.2.5.1.3.4-2: Data structures supported by the HTTP POST Response Body** - -| Data type | P | Cardinality | Response codes | Description | -|-----------|---|-------------|----------------|---------------------------------------| -| N/A | | | 204 No content | Confirmation of received notification | - -### 6.2.6 Data Model - -#### 6.2.6.1 Introduction - -This clause specifies the application protocol data model supported by the A1-P API. - -The data model for the data types transported in the A1-P procedures is defined in A1TD [4], clause 6. - -#### 6.2.6.2 Simple data types and enumerations - -##### 6.2.6.2.1 Simple data types - -The resource identifiers defined in clause 5.2.2.4 include policy type identifier and policy identifier based on the simple data types specified in table 6.2.6.2.1-1. - -**Table 6.2.6.2.1-1: General definition of simple data types** - -| Type Name | Type Definition | Description | Applicability | -|--------------|-----------------|-----------------------------------------------------------------------------------------------------|---------------| -| PolicyTypeId | string | policy type identifier assigned by the owner of a policy type definition (see A1TD [4], clause 7.1) | used in URI | -| PolicyId | string | policy identifier assigned by the A1-P Consumer when a policy is created (see clause 6.2.3.2.0) | used in URI | - -#### 6.2.6.3 Structured data types - -##### 6.2.6.3.1 Problem details - -In case a policy request is not accepted, additional information can be provided in the response in addition to the HTTP error status code. - -The ProblemDetails statement specified in table 6.2.6.3.1-1 contains attributes defined in IETF RFC 9457 [10], clause 3.1: - -**Table 6.2.6.3.1-1: Definition of statement type ProblemDetails** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-----------|---|-------------|---------------------------------------------------------------------------------|---------------| -| type | string | O | 0..1 | a URI reference according to IETF RFC 3986 [9] that identifies the problem type | | -| title | string | O | 0..1 | human-readable summary of the problem type | | -| status | number | O | 0..1 | the HTTP status code | | -| detail | string | O | 0..1 | human-readable explanation | | -| instance | string | O | 0..1 | URI reference that identifies the specific occurrence of the problem | | - -### 6.2.7 Error Handling - -#### 6.2.7.1 General - -HTTP error handling is specified based on 3GPP TS 29.500 [11], clause 5.2.4 and according to the principles in 3GPP TS 29.501 [6], clause 4.8. - -#### 6.2.7.2 Protocol Errors - -No protocol errors are described in the present document. - -#### 6.2.7.3 Application Errors - -The application errors defined for the A1-P service are listed in table 6.2.7.3-1. - -**Table 6.2.7.3-1: Application errors** - -| Application Error | HTTP status code | Description | -|--------------------|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Bad Request | 400 | Used when the Near-RT RIC or the Non-RTR RIC cannot or will not process a request, e.g. when the validation of PolicyObject towards a policy type schema, or the validation of PolicyStatusObject towards a policy status schema, fails. | -| Not Found | 404 | Used when the Near-RT RIC did not find a current representation for the resource representing a policy type or a policy, e.g. for a policy type that is not available or a policy that does not exist. | -| Method Not Allowed | 405 | Used when the HTTP method is not supported by the resource defined for the A1-P API. | -| Conflict | 409 | Used if the Near-RT RIC detects that a policy requested to be created or updated may be overlapping or conflicting with a policy that exists, e.g. if the policy in the request is identical to an existing policy. | - -Application errors should be mapped to the most applicable 4xx/5xx HTTP error status code. If no such status code is applicable, one of the status codes 400 (Bad Request) or 500 (Internal Server Error) should be used. - -The HTTP status codes listed in table 6.2.7.3-1 shall be used as defined in clause 5.2.3 for the A1-P procedures and clause 6.2.3 for the resources. - -Implementations may use additional HTTP error status codes in addition to those listed in table 6.2.7.3-1, as long as they are valid HTTP status codes. - -A list of all valid HTTP status codes and their specification documents can be obtained from the HTTP status code registry [13]. - -In addition, the response body may contain a JSON representation of a "ProblemDetails" data structure in the payload body as defined in clause 6.2.6.3.1. In that case, as defined by IETF RFC 9457 [10], clause 3 the "Content-Type" HTTP header shall be set to "application/problem+json". - -## 6.3 A1-EI (enrichment information) - -### 6.3.1 Introduction - -This clause contains the definition of the REST based API for the A1 enrichment information service. - -The name of the API is A1-EI and for the API version defined in the present document the major field of the API version number is 1. - -Based on the URI structure defined in 3GPP TS 29.501 [6], clause 4.4.1 the request URI used in HTTP request from the A1-EI consumer towards the A1-EI producer shall have the following structure: - -**{apiRoot}/A1-EI/v1/** - -where the "ResourceUriPart" shall be as defined in clause 6.3.3. - -### 6.3.2 Usage of HTTP - -#### 6.3.2.1 General - -The A1 Transport, HTTP protocol and security requirements, is described in A1TP [3]. - -#### 6.3.2.2 HTTP standard headers - -Encodings and applicable MIME media type for the related Content-Type header are not specified in this version of the present document. - -#### 6.3.2.3 HTTP custom headers - -No HTTP custom headers are specified in the present document. - -### 6.3.3 Resources - -#### 6.3.3.1 Overview - -##### 6.3.3.1.1 Resource URI structure - -The resource URI structure for the A1-EI API is illustrated in figure 6.3.3.1.1-1. - -![Resource URI structure of the A1-EI API diagram](e22af684d8e56d4c61e61bb5ddac1087_img.jpg) - -``` - - graph TD - Root["{apiRoot}/A1-EI/v1"] --> eiTypes["/eiTypes"] - Root --> eiJobs["/eiJobs"] - eiTypes --> eiTypeId["/{eiTypeId}"] - eiJobs --> eiJobId["/{eiJobId}"] - eiJobId --> status["/status"] - -``` - -Resource URI structure of the A1-EI API diagram - -**Figure 6.3.3.1.1-1: Resource URI structure of the A1-EI API** - -##### **6.3.3.1.2 Resources and methods** - -Table 6.3.3.1.2-1 provides an overview of the resources and HTTP methods defined for the A1-EI API. - -**Table 6.3.3.1.2-1: Resources and methods overview** - -| Resource name | Resource URI | HTTP method or custom operation | Description | -|--------------------------|-------------------------|---------------------------------|-------------------------------| -| All EI Type Identifiers | /eitypes | GET | Query all EI type identifiers | -| Individual EI Type | /eitypes/{eiTypeId} | GET | Query EI type | -| All EI Jobs | /ejobs | GET | Query all EI job identifiers | -| Individual EI Job | /ejobs/{eiJobId} | GET | Query EI job | -| | | PUT | Create/Update EI job | -| | | DELETE | Delete EI job | -| Individual EI Job Status | /ejobs/{eiJobId}/status | GET | Query EI job status | - -For each combination of a resource and an HTTP method in table 6.3.3.1.2-1, the HTTP status codes are as defined for the A1-EI procedures listed in the Description column and defined in clauses 5.3.3 to 5.3.5. For any other combination of a resource defined for this API and an HTTP method, including those HTTP methods that are not defined for this API, the HTTP status code 405 (Method Not Allowed) shall be used to indicate that the method is not supported on the resource. - -##### **6.3.3.1.3 EI type identifier** - -The EiTypeId is constructed based on two parts separated by "\_" (underscore): - -`typename_version` - -where - -`typename` is the unique label of the EI type; - -`version` is the version of the EI type defined as major.minor.patch as described in SemVer [8]. - -The typename and version is assigned, and their uniqueness ensured, by the organizational entity that is responsible for the definition and maintenance of the EI type definition. - -**NOTE:** The typename can be based on a prefix that indicates the organizational entity (e.g. O-RAN or a company designator) and a text string that can be descriptive of the class, use case or variant of the EI type. - -##### 6.3.3.1.4 EI job identifier - -An EiJobId is assigned by the Near-RT RIC and is unique within the domain of operation of the Non-RT RIC. - -#### 6.3.3.2 All EI Type Identifiers - -##### 6.3.3.2.1 Description - -The resource represents EI type identifiers. - -##### 6.3.3.2.2 Resource Definition - -The Resource URI and the supported resource variables are as defined in previous clauses. - -##### 6.3.3.2.3 Resource Standard Methods - -###### 6.3.3.2.3.1 HTTP GET - -This method shall support the request data structures specified in table 6.3.3.2.3.1-1 and the response data structures and response codes specified in table 6.3.3.2.3.1-2. - -**Table 6.3.3.2.3.1-1: Data structures supported by the HTTP GET Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|---------------------------------------------------------| -| N/A | | | There is no object in the message body of a GET request | - -**Table 6.3.3.2.3.1-2: Data structures supported by the HTTP GET Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|-----------------|---|-------------|----------------|------------------------------| -| Array(EiTypeId) | M | 0..N | 200 OK | All EI type identifiers | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -##### 6.3.3.2.4 Resource Custom Operations - -No custom operations are defined. - -#### 6.3.3.3 Individual EI Type - -##### 6.3.3.3.1 Description - -The resource represents an EI type. - -##### 6.3.3.3.2 Resource Definition - -The Resource URI and the supported resource variables are as defined in previous clauses. - -##### 6.3.3.3.3 Resource Standard Methods - -###### 6.3.3.3.3.1 HTTP GET - -This method shall support the request data structures specified in table 6.3.3.3.3.1-1 and the response data structures and response codes specified in table 6.3.3.3.3.1-2. - -**Table 6.3.3.3.3.1-1: Data structures supported by the HTTP GET Request Body on this resource** - -| Data type | P | Cardinality | Description | | -|-----------|---|-------------|---------------------------------------------------------|--| -| N/A | | | There is no object in the message body of a GET request | | - -**Table 6.3.3.3.3.1-2: Data structures supported by the HTTP GET Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|------------------------------| -| EiTypeObject | M | 1 | 200 OK | Requested EI type object | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -##### 6.3.3.3.4 Resource Custom Operations - -No custom operations are defined. - -#### 6.3.3.4 All EI Jobs - -##### 6.3.3.4.1 Description - -The resource represents EI job identifiers. - -##### 6.3.3.4.2 Resource Definition - -The Resource URI and the supported resource variables are as defined in previous clauses. - -##### 6.3.3.4.3 Resource Standard Methods - -###### 6.3.3.4.3.1 HTTP GET - -This method shall support the request data structures specified in table 6.3.3.4.3.1-1 and the response data structures and response codes specified in table 6.3.3.4.3.1-2. - -**Table 6.3.3.4.3.1-1: Data structures supported by the HTTP GET Request Body on this resource** - -| Data type | P | Cardinality | Description | | -|-----------|---|-------------|---------------------------------------------------------|--| -| N/A | | | There is no object in the message body of a GET request | | - -**Table 6.3.3.4.3.1-2: Data structures supported by the HTTP GET Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|------------------------------| -| array(EiJobId) | M | 0..N | 200 OK | All EI job identifiers | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -This method shall support the URI query parameters specified in table 6.3.3.4.3.1-3. - -**Table 6.3.3.4.3.1-3: URI query parameters supported by the HTTP GET method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|----------|-----------|---|-------------|-----------------------------------------------------|---------------------------------------------------| -| eiTypeId | string | O | 0..1 | eiTypeId for which EI Job identifiers are requested | Retrieve EI Job identifiers for a certain EI Type | - -#### 6.3.3.5 Individual EI Job - -##### 6.3.3.5.1 Description - -The resource represents an EI job. - -##### 6.3.3.5.2 Resource Definition - -The Resource URI and the supported resource variables are as defined in previous clauses. - -##### 6.3.3.5.3 Resource Standard Methods - -###### 6.3.3.5.3.1 HTTP PUT - -This method shall support the request data structures specified in table 6.3.3.5.3.1-1 and the response data structures and response codes specified in table 6.3.3.5.3.1-2. - -**Table 6.3.3.5.3.1-1: Data structures supported by the HTTP PUT Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-------------|---|-------------|-------------------------| -| EiJobObject | M | 1 | Create or Update EI job | - -**Table 6.3.3.5.3.1-2: Data structures supported by the HTTP PUT Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|-----------------------|-------------------------------------------| -| EiJobObject | M | 1 | 201 Created
200 OK | Confirmation of created or updated EI job | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -This method shall support the response headers specified in table 6.3.3.5.3.1-3. - -**Table 6.3.3.5.3.1-3: Headers supported by the 201-response code on the resource** - -| Name | Data type | P | Cardinality | Description | -|----------|-----------|---|-------------|------------------------------------------------| -| Location | string | M | 1 | Contains the URI of the newly created resource | - -###### 6.3.3.5.3.2 HTTP GET - -This method shall support the request data structures specified in table 6.3.3.5.3.2-1 and the response data structures and response codes specified in table 6.3.3.5.3.2-2. - -**Table 6.3.3.5.3.2-1: Data structures supported by the HTTP GET Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|---------------------------------------------------------| -| N/A | | | There is no object in the message body of a GET request | - -**Table 6.3.3.5.3.2-2: Data structures supported by the HTTP GET Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|------------------------------| -| EiJobObject | M | 1 | 200 OK | Requested EI job object | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -###### 6.3.3.5.3.3 HTTP DELETE - -This method shall support the request data structures specified in table 6.3.3.5.3.3-1 and the response data structures and response codes specified in table 6.3.3.5.3.3-2. - -**Table 6.3.3.5.3.3-1: Data structures supported by the HTTP DELETE Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|------------------------------------------------------------| -| N/A | | | There is no object in the message body of a DELETE request | - -**Table 6.3.3.5.3.3-2: Data structures supported by the HTTP DELETE Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|-------------------------------------| -| N/A | | | 204 No content | Confirmation of successful deletion | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -##### 6.3.3.5.4 Resource Custom Operations - -No custom operations are defined. - -#### 6.3.3.6 Individual EI Job Status - -##### 6.3.3.6.1 Description - -The resource represents the status of an EI job. - -##### 6.3.3.6.2 Resource Definition - -The Resource URI and the supported resource variables are as defined in previous clauses. - -##### 6.3.3.6.3 Resource Standard Methods - -###### 6.3.3.6.3.1 HTTP GET - -This method shall support the request data structures specified in table 6.3.3.6.3.1-1 and the response data structures and response codes specified in table 6.3.3.6.3.1-2. - -**Table 6.3.3.6.3.1-1: Data structures supported by the HTTP GET Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|---------------------------------------------------------| -| N/A | | | There is no object in the message body of a GET request | - -**Table 6.3.3.6.3.1-2: Data structures supported by the HTTP GET Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|-------------------|---|-------------|----------------|--------------------------------| -| EiJobStatusObject | M | 1 | 200 OK | Requested EI job status object | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -##### 6.2.3.3.4 Resource Custom Operations - -No custom operations are defined. - -### 6.3.4 Custom Operations without associated resources - -No custom operations are defined. - -### 6.3.5 Notifications - -#### 6.3.5.0 General - -Table 6.3.5.0-1 provides an overview of the callback URIs and HTTP methods defined for the A1-EI API. - -**Table 6.3.5.0-1: Notifications overview** - -| Notification | Callback URI | HTTP method or custom operation | Description | -|----------------------------|----------------------------|---------------------------------|-----------------------| -| EI Job Status Notification | {jobStatusNotificationUri} | POST | Notify EI job status | -| EI Job Result Delivery | {jobResultUri} | POST | Deliver EI job result | - -For each combination of a callback URI and an HTTP method in table 6.3.5.0-1, the HTTP status codes are as defined for the procedures listed in the Description column and defined in clauses 5.3.4.8 and 5.3.5.2. - -#### 6.3.5.1 EI Job Status Notification - -##### 6.3.5.1.1 Description - -The EI Job Status Notification is used by the A1-EI Producer to report status changes about an EI job to an A1-EI Consumer that has subscribed to such notifications. - -##### 6.3.5.1.2 Target URI - -The Callback URI "{jobStatusNotificationUri}" shall be used with the callback URI variables defined in table 6.3.5.1.2-1. - -**Table 6.3.5.1.2-1: Callback URI variables** - -| Name | Definition | -|--------------------------|-----------------------------------------------| -| jobStatusNotificationUri | String formatted as URI with the Callback Uri | - -##### 6.3.5.1.3 Standard Methods - -###### 6.3.5.1.3.1 HTTP POST - -This method shall support the request data structures specified in table 6.3.5.1.3.1-1 and the response data structures and response codes specified in table 6.3.5.1.3.1-2. - -**Table 6.3.5.1.3.1-1: Data structures supported by the HTTP POST Request Body** - -| Data type | P | Cardinality | Description | -|-------------------|---|-------------|----------------------| -| EiJobStatusObject | M | 1 | Notify EI job status | - -**Table 6.3.5.1.3.1-2: Data structures supported by the HTTP POST Response Body** - -| Data type | P | Cardinality | Response codes | Description | -|-----------|---|-------------|----------------|---------------------------------------| -| N/A | | | 204 No content | Confirmation of received notification | - -#### 6.3.5.2 EI Job Result Delivery - -##### 6.3.5.2.1 Description - -The EI Job Result Delivery is used by the A1-EI Producer to deliver results related to an EI job to an A1-EI Consumer that has created such job. - -##### 6.3.5.2.2 Target URI - -The Callback URI "{jobResultUri}" shall be used with the callback URI variables defined in table 6.3.5.2.2-1. - -**Table 6.3.5.2.2-1: Callback URI variables** - -| Name | Definition | -|--------------|-----------------------------------------------| -| jobResultUri | String formatted as URI with the Callback Uri | - -##### 6.3.5.2.3 Standard Methods - -###### 6.3.5.2.3.1 HTTP POST - -This method shall support the request data structures specified in table 6.3.5.2.3.1-1 and the response data structures and response codes specified in table 6.3.5.2.3.1-2. - -**Table 6.3.5.2.3.1-1: Data structures supported by the HTTP POST Request Body** - -| Data type | P | Cardinality | Description | -|-------------------|---|-------------|--------------------------------------------------| -| EiJobResultObject | M | 1 | Carry EI payload, i.e. the result from an EI job | - -**Table 6.3.5.2.3.1-2: Data structures supported by the HTTP POST Response Body** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|---------------------------------------| -| N/A | | | 204 No content | Confirmation of received notification | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -### 6.3.6 Void - -### 6.3.7 Data model - -#### 6.3.7.1 Introduction - -This clause specifies the application protocol data model supported by the A1-EI API. - -The data model for the data types transported in the A1-EI procedures is defined in A1TD [4], clause 8. - -#### 6.3.7.2 Simple data types and enumerations - -##### 6.3.7.2.1 Simple data types - -The resource identifiers defined in clause 5.3.2.4 include EI type identifier or EI job identifier based on the simple data types specified in table 6.3.7.2.1-1. - -**Table 6.3.7.2.1-1: General definition of simple data types for URI identifiers** - -| Type Name | Type Definition | Description | Applicability | -|-----------|-----------------|---------------------------------------------------------------------------------------------------|---------------| -| EiTypeId | string | EI type identifier assigned by the owner of an EI type definition (see clause 6.3.3.1.3) | used in URI | -| EiJobId | string | EI job identifier assigned by the A1-EI Consumer when an EI job is created (see clause 6.3.3.1.4) | used in URI | - -**Table 6.3.7.2.1-2: General definition of simple data types for callback URIs** - -| Callback URI | Type Definition | Description | Applicability | -|--------------------------|-----------------|--------------------------------------------|-------------------------------------------------------------------------| -| jobStatusNotificationUri | string | target URI for EI job status notifications | provided in EI Job object and used in job status notification procedure | -| jobResultUri | string | target URI for EI job results | provided in EI Job object and used in job result deliver procedure | - -#### 6.3.7.3 Structured data types - -##### 6.3.7.3.1 Problem details - -The problem details statement is the same as defined for A1-P, see clause 6.2.6.3.1. - -### 6.3.8 Error handling - -#### 6.3.8.1 General - -HTTP error handling is specified based on 3GPP TS 29.500 [11], clause 5.2.4 and according to the principles in 3GPP TS 29.501 [6], clause 4.8. - -#### 6.3.8.2 Protocol Errors - -No protocol errors are described in this version of the present document. - -#### 6.3.8.3 Application Errors - -The application errors defined for the A1-EI service are listed in table 6.3.8.3-1. - -**Table 6.3.8.3-1: Application errors** - -| Application Error | HTTP status code | Description | -|--------------------|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| -| Bad Request | 400 | Used when the Near-RT RIC or the Non-RTR RIC cannot or will not process a request, e.g. when the validation of an object towards a schema, fails. | -| Not Found | 404 | Used when the Non-RT RIC did not find a current representation for the resource representing an EI type or an EI job. | -| Method Not Allowed | 405 | Used when the HTTP method is not supported by the resource defined for the A1-EI API. | -| Conflict | 409 | Used if the Non-RT RIC detects that an EI job requested to be created or updated may be overlapping or conflicting with an EI job that exists. | - -Application errors should be mapped to the most applicable 4xx/5xx HTTP error status code. If no such status code is applicable, one of the status codes 400 (Bad Request) or 500 (Internal Server Error) should be used. - -The HTTP status codes listed in table 6.3.8.3-1 shall be used as defined in clauses 5.3.3 to 5.3.5 for the A1-EI procedures and clause 5.3.3 for the resources. - -Implementations may use additional HTTP error status codes in addition to those listed in table 6.3.8.3-1, as long as they are valid HTTP status codes. - -A list of all valid HTTP status codes and their specification documents can be obtained from the HTTP status code registry [13]. - -In addition, the response body may contain a JSON representation of a "ProblemDetails" data structure in the payload body as defined in clause 6.2.6.3.1. In that case, as defined by IETF RFC 9457 [10], clause 3 the "Content-Type" HTTP header shall be set to "application/problem+json". - -## 6.4 A1-ML (ML model management) - -### 6.4.1 Introduction - -This clause contains the definition of the REST based API for the A1 ML model management Service referred to as A1-ML. - -The present document defines API version 1 (v1) of the A1-ML API. - -Based on the URI structure defined in 3GPP TS 29.501 [6], clause 4.4.1 the request URI used in HTTP request from the A1-ML consumer towards the A1-ML producer shall have the following structure: - -`{apiRoot}/a1-ml/v1/` - -where the "ResourceUriPart" shall be as defined in clause 6.3.3. - -### 6.4.2 Usage of HTTP - -#### 6.4.2.1 General - -The A1 Transport, HTTP protocol and security requirements, is described in A1TP [3]. - -#### 6.4.2.2 HTTP standard headers - -Encodings and applicable MIME media type for the related Content-Type header are not specified in this version of the present document. - -#### 6.4.2.3 HTTP custom headers - -No HTTP custom headers are specified in the present document. - -### 6.4.3 Resources - -#### 6.4.3.1 Overview - -##### 6.4.3.1.1 Resource URI structure - -The resource URI structure for the A1-ML API is illustrated in figure 6.4.3.1.1-1. - -![A hierarchical tree diagram showing the resource URI structure for the A1-ML API. The root is {apiRoot}/a1-ml/v1. It branches into /training-capabilities and /training-jobs. /training-jobs further branches into /{trainingJobId}, which in turn branches into /status.](71b0a68b4dd64961465d2b0e790538de_img.jpg) - -``` - - graph TD - Root["{apiRoot}/a1-ml/v1"] --> TC["/training-capabilities"] - Root --> TJ["/training-jobs"] - TJ --> TJID["/{trainingJobId}"] - TJID --> Status["/status"] - -``` - -A hierarchical tree diagram showing the resource URI structure for the A1-ML API. The root is {apiRoot}/a1-ml/v1. It branches into /training-capabilities and /training-jobs. /training-jobs further branches into /{trainingJobId}, which in turn branches into /status. - -Figure 6.4.3.1.1-1: Resource URI structure of the A1-ML API - -##### 6.4.3.1.2 Resources and methods - -Table 6.4.3.1.2-1 provides an overview of the resources and HTTP methods defined for the A1-ML API. - -Table 6.4.3.1.2-1: Resources and methods overview - -| Resource name | Resource URI | HTTP method or custom operation | Description | -|--------------------------------------------|---------------------------------------|---------------------------------|-----------------------------------------| -| All AI/ML model training capabilities | /training-capabilities | GET | Query AI/ML model training capabilities | -| All AI/ML model training jobs | /training-jobs | POST | Create AI/ML model training job | -| Individual AI/ML model training job | /training-jobs/{trainingJobId} | DELETE | Cancel AI/ML model training job | -| Individual AI/ML model training job status | /training-jobs/{trainingJobId}/status | GET | Query AI/ML model training job status | - -#### 6.4.3.2 All AI/ML model training capabilities - -##### 6.4.3.2.1 Description - -The resource represents AI/ML model training capabilities. - -##### 6.4.3.2.2 Resource Definition - -The Resource URI and the supported resource variables are as defined in previous clauses. - -##### 6.4.3.2.3 Resource Standard Methods - -###### 6.4.3.2.3.1 HTTP PUT - -Method is not supported on this resource. - -###### 6.4.3.2.3.2 HTTP GET - -This method shall support the request data structures specified in table 6.4.3.2.3.2-1 and the response data structures and response codes specified in table 6.4.3.2.3.2-2. - -**Table 6.4.3.2.3.2-1: Data structures supported by the HTTP GET Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|---------------------------------------------------------| -| N/A | | | There is no object in the message body of a GET request | - -**Table 6.4.3.2.3.2-2: Data structures supported by the HTTP GET Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|-------------------------------|---|-------------|----------------|------------------------------------------------------------------------------| -| array(TrainingCapabilityInfo) | M | 0..N | 200 OK | All AI/ML model training capabilities that match the given SelectionCriteria | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -This method shall support the URI query parameters specified in table 6.4.3.2.3.2-3. - -**Table 6.4.3.2.3.2-3: URI query parameters supported by the HTTP GET method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|-----------------|-----------|---|-------------|-----------------------------------------------------------|---------------| -| minMemory | integer | O | 0..1 | The minimum memory requirement, with the unit of Megabyte | | -| environmentType | string | O | 0..1 | The platform execution service type | | -| dependency | string | O | 0..1 | Platform dependency that needs to be installed | | - -###### 6.4.3.2.3.3 HTTP DELETE - -Method is not supported on this resource. - -###### 6.4.3.2.3.4 HTTP POST - -Method is not supported on this resource. - -##### 6.4.3.2.4 Resource Custom Operations - -No custom operations are defined. - -#### 6.4.3.3 All AI/ML model training jobs - -##### 6.4.3.3.1 Description - -The resource represents all AI/ML model training jobs created. - -The methods defined in clause 6.4.3.3.3 shall be supported by this resource. - -##### 6.4.3.3.2 Resource Definition - -The Resource URI and the supported resource variables are as defined in previous clauses. - -##### 6.4.3.3.3 Resource Standard Methods - -###### 6.4.3.3.3.1 POST - -This method shall support the request data structures specified in the table 6.4.3.3.3.1-1 and the response data structures, and response codes specified in table 6.4.3.3.3.1-2 and the HTTP headers specified in table 6.4.3.3.3.1-3. - -**Table 6.4.3.3.3.1-1: Data structures supported by the HTTP POST request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------------|---|-------------|---------------------------------------------------------------------| -| TrainingJobInfo | M | 1 | Information related to the creation of the AI/ML model training job | - -**Table 6.4.3.3.3.1-2: Data structures supported by the HTTP POST response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|-----------------|---|-------------|----------------|--------------------------------------------------| -| TrainingJobInfo | M | 1 | 201 Created | Confirmation of created AI/ML model training job | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -**Table 6.4.3.3.3.1-3: Headers supported by the 201 Response Code on this resource.** - -| Name | Data type | P | Cardinality | Description | -|----------|-----------|---|-------------|------------------------------------------------| -| Location | string | M | 1 | Contains the URI of the newly created resource | - -##### 6.4.3.3.4 Resource Custom Methods - -None. - -#### 6.4.3.4 Individual AI/ML model training job - -##### 6.4.3.4.1 Description - -The resource represents an individual AI/ML model training job. - -The methods defined in clause 6.4.3.4.3 shall be supported by this resource. - -##### 6.4.3.4.2 Resource Definition - -The Resource URI and the supported resource variables are as defined in previous clauses. - -##### 6.4.3.4.3 Resource Standard Methods - -###### 6.4.3.4.3.1 DELETE - -This method shall support the request data structures specified in the table 6.4.3.4.3.1-1 and the response data structures, and response codes specified in table 6.4.3.4.3.1-2. - -**Table 6.4.3.4.3.1-1: Data structures supported by the HTTP DELETE request body on this resource.** - -| Data type | P | Cardinality | Description | | -|-----------|---|-------------|----------------------------------------------------------------|--| -| N/A | | | There is no object in the message content of a DELETE request. | | - -**Table 6.4.3.4.3.1-2: Data structures supported by the HTTP DELETE response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|--------------------------------------| -| N/A | | | 204 No content | Confirmation of successful deletion. | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description. | - -##### 6.4.3.4.4 Resource Custom Methods - -None. - -#### 6.4.3.5 Individual AI/ML model training job Status - -##### 6.4.3.5.1 Description - -The resource represents the status of an AI/ML model training job. - -##### 6.4.3.5.2 Resource Definition - -The Resource URI and the supported resource variables are as defined in previous clauses. - -##### 6.4.3.5.3 Resource Standard Methods - -###### 6.4.3.5.3.1 HTTP GET - -This method shall support the request data structures specified in table 6.4.3.5.3.1-1 and the response data structures and response codes specified in table 6.4.3.5.3.1-2. - -**Table 6.4.3.5.3.1-1: Data structures supported by the HTTP GET Request Body on this resource** - -| Data type | P | Cardinality | Description | | -|-----------|---|-------------|---------------------------------------------------------|--| -| N/A | | | There is no object in the message body of a GET request | | - -**Table 6.4.3.5.3.1-2: Data structures supported by the HTTP GET Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|-------------------|---|-------------|----------------|--------------------------------------------------| -| TrainingJobStatus | M | 1 | 200 OK | Requested AI/ML model training job status object | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -##### 6.4.3.5.4 Resource Custom Operations - -No custom operations are defined. - -### 6.4.4 Custom Operations without associated resources - -No custom operations are defined. - -### 6.4.5 Notifications - -#### 6.4.5.1 Training Job Status Notification - -##### 6.4.5.1.1 Description - -The Training Job Status Notification is used by the AI-ML Producer to report status changes about an AI/ML model training job to an AI-ML Consumer that has subscribed to such notifications. - -##### 6.4.5.1.2 Target URI - -The Callback URI "{trainingJobStatusNotificationUri}" shall be used with the callback URI variables defined in table 6.4.5.1.2-1. - -**Table 6.4.5.1.2-1: Callback URI variables** - -| Name | Definition | -|----------------------------------|-----------------------------------------------| -| trainingJobStatusNotificationUri | String formatted as URI with the Callback Uri | - -##### 6.4.5.1.3 Standard Methods - -###### 6.4.5.1.3.1 HTTP POST - -This method shall support the request data structures specified in table 6.4.5.1.3.1-1 and the response data structures, and response codes specified in table 6.4.5.1.3.1-2. - -**Table 6.4.5.1.3.1-1: Data structures supported by the HTTP POST Request Body** - -| Data type | P | Cardinality | Description | -|-------------------|---|-------------|----------------------------------------| -| TrainingJobStatus | M | 1 | Notify AI/ML model training job status | - -**Table 6.4.5.1.3.1-2: Data structures supported by the HTTP POST Response Body** - -| Data type | P | Cardinality | Response codes | Description | -|-----------|---|-------------|----------------|---------------------------------------| -| N/A | | | 204 No content | Confirmation of received notification | - -### 6.4.6 Data model - -#### 6.4.6.1 Introduction - -This clause specifies the application protocol data model supported by the AI-ML API. - -#### 6.4.6.2 Simple data types and enumerations - -##### 6.4.6.2.1 Simple data types - -No simple data types are defined in this version of the specification. - -##### 6.4.6.2.2 Enumerations - -No enumerations are defined in this version of the specification. - -#### 6.4.6.3 Structured data types - -##### 6.4.6.3.1 TrainingCapabilityInfo - -The TrainingCapabilityInfo data type represents all AI/ML model training capabilities that match the given selection criteria. It contains the attributes defined in table 6.4.6.3.1-1. - -**Table 6.4.6.3.1-1: Definition of type TrainingCapabilityInfo** - -| Attribute Name | Data type | P | Cardinality | Description | -|-----------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| environmentInfo | Object | M | 1 | The environment information about the AI/ML model training software environment including e.g. environment type and dependencies | -| resourceInfo | Object | O | 0..1 | The resource information about the supported AI/ML model training environment. The resource information consists of the memory of the AI/ML model training environment given in the unit of Megabyte. | - -##### 6.4.6.3.2 ModelId - -The ModelId data type represents information of AI/ML model. It contains the attributes defined in table 6.4.6.3.2-1. - -**Table 6.4.6.3.2-1: Definition of type ModelId** - -| Attribute Name | Data type | P | Cardinality | Description | -|-----------------|-----------|---|-------------|----------------------------------| -| modelName | String | M | 1 | Name of the model. | -| modelVersion | String | M | 1 | Version of the model. | -| artifactVersion | String | O | 0..1 | Artifact version of AI/ML model. | - -##### 6.4.6.3.3 TrainingJobInfo - -The TrainingJobInfo data type represents information of an AI/ML model training job. It contains the attributes defined in table 6.4.6.3.3-1. - -**Table 6.4.6.3.3-1: Definition of type TrainingJobInfo** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------| -| modelId | ModelId | M | 1 | The model identifier which contains model name, model version, and artifact version. See clause 6.4.6.3.2. | -| modelLocation | Uri | O | 0..1 | Location of the AI/ML model. | -| trainingDataset | Uri | O | 0..1 | Information for reference to the training dataset. | -| trainingConfig | Object | O | 0..1 | trainingConfig provided by the training service producer. | -| trainingJobStatusNotificationUri | Uri | O | 0..1 | Callback URI where the notification should be delivered to. | - -##### 6.4.6.3.4 TrainingJobStatus - -The attributes of the TrainingJobStatus object are not specified in the present document. - -##### 6.4.6.3.5 Problem details - -The problem details statement is the same as defined for A1-P, see clause 6.2.6.3.1. - -### 6.4.7 Error handling - -#### 6.4.7.1 General - -HTTP error handling is specified based on 3GPP TS 29.500 [11], clause 5.2.4 and according to the principles in 3GPP TS 29.501 [6], clause 4.8. - -#### 6.4.7.2 Protocol Errors - -No specific protocol errors are defined in the present document. - -#### 6.4.7.3 Application Errors - -No additional application errors defined in the present document. - -# Annex A (normative): OpenAPI specification - -## A.1 General - -### A.1.0 Overview - -This annex specifies the formal definition of the A1 API(s). It consists of OpenAPI documents in YAML format that are based on the OpenAPI Specification [12]. - -Informative copies of the OpenAPI documents contained in this O-RAN Technical Specification may be available at a later stage. - -### A.1.1 Versioning of A1 OpenAPI documents - -The OpenAPI documents for the A1 services found in this clause are versioned as specified in SemVer [8] as described in the OpenAPI Specification [12]. When included in the present document, the OpenAPI documents are considered as released and are versioned using three-field version number major.minor.patch where the main compatibility expectations stated in SemVer [8] implies: - -- the major field is stepped up when incompatible API changes are made to the OpenAPI document. This corresponds to saying that implementations of an A1 service in Non/Near-RT RICs are incompatible in case the major field of the API version numbers are different. The major field of the API version number is indicated in the URI for the A1 API defined in clause 4; -- the minor field is stepped up when features are added to the OpenAPI document in way that keeps implementations compatible although all features are not supported by both the service producer and the service consumer of the A1 service; and -- the patch field is stepped up when errors are corrected in a backward compatible way, or when editorial changes are made to the OpenAPI document, but no features are added. - -NOTE: Non/Near-RT RIC products that implement different API versions of an A1 service can be compatible by supporting API versions with the same major field in the API version numbers. The present document specifies only one API version, and contains only one OpenAPI document, for each A1 service. - -### A.1.2 Current API versions - -The present document defines the API versions indicated in table A.1.2-1. - -**Table A.1.2-1 API versions** - -| API name | API version number | -|----------|--------------------| -| A1-P | 2.2.3 | -| A1-EI | 1.3.1 | -| A1-ML | 1.0.0 | - -NOTE: API name and major field of API version number are defined in clauses 6.2.1, 6.3.1, and 6.4.1 and API version is visible in an OpenAPI document in the following clauses. - -## A.2 Policy management API - -``` - -openapi: 3.0.1 -info: - version: 2.2.3 - description: | - This module is for API for Policy Management Service. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at https://www.o-ran.org/sccl -externalDocs: - description: 'O-RAN.WG2.TS.A1AP-R005-v06.00 A1 interface: Application Protocol' - url: 'https://www.o-ran.org/specifications' -servers: - - url: '{apiRoot}/A1-P/v2' - variables: - apiRoot: - default: 'https://example.com' - description: 'apiRoot as defined in clause 6.2.1 in O-RAN.WG2.TS.A1AP' -paths: - '/policytypes': - get: - description: 'Get all policy type identifiers' - tags: - - All Policy Type Identifiers - responses: - 200: - description: 'Array of all policy type identifiers' - content: - application/json: - schema: - type: array - items: - "$ref": "#/components/schemas/PolicyTypeId" - minItems: 0 - - '/policytypes/{policyTypeId}': - parameters: - - name: policyTypeId - in: path - required: true - schema: - "$ref": "#/components/schemas/PolicyTypeId" - get: - description: 'Get the schemas for a policy type' - tags: - - Individual Policy Type - responses: - 200: - description: 'The policy type schemas' - content: - application/json: - schema: - "$ref": "#/components/schemas/PolicyTypeObject" - 404: - "$ref": "#/components/responses/404-NotFound" - - '/policytypes/{policyTypeId}/policies': - get: - description: 'Get all policy identifiers' - tags: - - All Policy Identifiers - parameters: - - name: policyTypeId - in: path - required: true - schema: - "$ref": "#/components/schemas/PolicyTypeId" - -``` - -``` - -responses: - 200: - description: 'Array of all policy identifiers' - content: - application/json: - schema: - type: array - items: - "$ref": "#/components/schemas/PolicyId" - minItems: 0 - 404: - "$ref": "#/components/responses/404-NotFound" - -'/policytypes/{policyTypeId}/policies/{policyId}': - parameters: - - name: policyTypeId - in: path - required: true - schema: - "$ref": "#/components/schemas/PolicyTypeId" - - name: policyId - in: path - required: true - schema: - "$ref": "#/components/schemas/PolicyId" - put: - description: 'Create, or update, a policy' - tags: - - Individual Policy Object - parameters: - - name: notificationDestination - in: query - required: false - schema: - "$ref": "#/components/schemas/NotificationDestination" - requestBody: - required: true - content: - application/json: - schema: - "$ref": "#/components/schemas/PolicyObject" - responses: - 200: - description: 'The policy was updated' - content: - application/json: - schema: - "$ref": "#/components/schemas/PolicyObject" - 201: - description: 'The policy was created' - content: - application/json: - schema: - "$ref": "#/components/schemas/PolicyObject" - headers: - Location: - description: 'Contains the URI of the created policy' - required: true - schema: - type: string - 400: - "$ref": "#/components/responses/400-BadRequest" - 404: - "$ref": "#/components/responses/404-NotFound" - 409: - "$ref": "#/components/responses/409-Conflict" - callbacks: - policyStatusNotification: - '{ $request.query.notificationDestination }': - post: - description: 'Notify about status for this policy' - -``` - -``` - - requestBody: - required: true - content: - application/json: - schema: - "$ref": "#/components/schemas/PolicyStatusObject" - responses: - 204: - description: 'Notification received' - 400: - "$ref": "#/components/responses/400-BadRequest" -get: - description: 'Query a policy' - tags: - - Individual Policy Object - responses: - 200: - description: 'The requested policy' - content: - application/json: - schema: - "$ref": "#/components/schemas/PolicyObject" - 404: - "$ref": "#/components/responses/404-NotFound" -delete: - description: 'Delete a policy' - tags: - - Individual Policy Object - responses: - 204: - description: 'The policy was deleted' - 404: - "$ref": "#/components/responses/404-NotFound" - -'/policytypes/{policyTypeId}/policies/{policyId}/status': - parameters: - - name: policyTypeId - in: path - required: true - schema: - "$ref": "#/components/schemas/PolicyTypeId" - - name: policyId - in: path - required: true - schema: - "$ref": "#/components/schemas/PolicyId" - get: - description: 'Query a policy status' - tags: - - Individual Policy Status Object - responses: - 200: - description: 'The requested policy status' - content: - application/json: - schema: - "$ref": "#/components/schemas/PolicyStatusObject" - 404: - "$ref": "#/components/responses/404-NotFound" - -components: - schemas: - # - # Representation objects - # - PolicyObject: - description: 'A generic policy object that can be used to transport any policy. Additionally, a policy shall be valid according to the schema of its specific policy type.' - type: object - - PolicyStatusObject: - -``` - -``` - -description: 'A generic policy status object that can be used to transport any policy status. -Additionally, a policy status shall be valid according to the schema of its specific policy type.' -type: object - -PolicyTypeObject: - description: 'A definition of a policy type, i.e. the schemas for a policy respectively its status' - type: object - properties: - policySchema: - "$ref": "#/components/schemas/JsonSchema" - statusSchema: - "$ref": "#/components/schemas/JsonSchema" - required: - - policySchema - -ProblemDetails: - description: 'A problem detail to carry details in an HTTP response according to RFC 7807' - type: object - properties: - type: - type: string - title: - type: string - status: - type: number - detail: - type: string - instance: - type: string - -# -# Simple data types -# -JsonSchema: - description: 'A JSON schema following http://json-schema.org/draft-07/schema' - "$ref": "#http://json-schema.org/draft-07/schema" - -NotificationDestination: - description: 'A complete callback URI defined according to IETF RFC 3986 where to send -notifications' - type: string - -PolicyId: - description: 'Policy identifier assigned by the AI-P Consumer when a policy is created' - type: string - -PolicyTypeId: - description: 'Policy type identifier assigned by the AI-P Provider' - type: string - -responses: - 400-BadRequest: - description: 'Object in payload not properly formulated or not related to the method' - content: - application/problem+json: - schema: - "$ref": "#/components/schemas/ProblemDetails" - - 404-NotFound: - description: 'No resource found at the URI' - content: - application/problem+json: - schema: - "$ref": "#/components/schemas/ProblemDetails" - - 405-MethodNotAllowed: - description: 'Method not allowed for the URI' - content: - application/problem+json: - schema: - "$ref": "#/components/schemas/ProblemDetails" - -``` - -``` - -409-Conflict: - description: 'Request could not be processed in the current state of the resource' - content: - application/problem+json: - schema: - "$ref": "#/components/schemas/ProblemDetails" - -``` - -## A.3 Enrichment information API - -``` - -openapi: 3.0.1 -info: - title: 'AI-EI Enrichment Information Service' - version: 1.3.1 - description: | - This module is for API for AI Enrichment Information Service. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at https://www.o-ran.org/sccl -externalDocs: - description: 'O-RAN.WG2.TS.A1AP-R005-v06.00 AI interface: Application Protocol' - url: 'https://www.o-ran.org/specifications' -servers: - - url: '{apiRoot}/AI-EI/v1' - variables: - apiRoot: - default: 'https://example.com' - description: 'apiRoot as defined in clause 6.3.1 in O-RAN.WG2.TS.A1AP' -paths: - '/eitypes': - get: - description: 'Get all EI type identifiers' - tags: - - All EI Type Identifiers - responses: - 200: - description: 'Array of all EI type identifiers' - content: - application/json: - schema: - type: array - items: - "$ref": "#/components/schemas/EiTypeId" - minItems: 0 - - '/eitypes/{eiTypeId}': - parameters: - - name: eiTypeId - in: path - required: true - schema: - "$ref": "#/components/schemas/EiTypeId" - get: - description: 'Get the schemas for an EI type' - tags: - - EI Type - responses: - 200: - description: 'The EI type schemas' - content: - application/json: - schema: - "$ref": "#/components/schemas/EiTypeObject" - 404: - "$ref": "#/components/responses/404-NotFound" - -``` - -``` - -'/eijobs': - get: - description: 'Get all EI job identifiers' - tags: - - All EI job Identifiers - parameters: - - name: eiTypeId - in: query - schema: - "$ref": "#/components/schemas/EiTypeId" - responses: - 200: - description: 'Array of all EI job identifiers' - content: - application/json: - schema: - type: array - items: - "$ref": "#/components/schemas/EiJobId" - minItems: 0 - 404: - "$ref": "#/components/responses/404-NotFound" - -'/eijobs/{eiJobId}': - parameters: - - name: eiJobId - in: path - required: true - schema: - "$ref": "#/components/schemas/EiJobId" - put: - description: 'Create, or update, an EI job' - tags: - - Individual EI job - requestBody: - required: true - content: - application/json: - schema: - "$ref": "#/components/schemas/EiJobObject" - responses: - 200: - description: 'The EI job was updated' - content: - application/json: - schema: - "$ref": "#/components/schemas/EiJobObject" - 201: - description: 'The EI job was created' - content: - application/json: - schema: - "$ref": "#/components/schemas/EiJobObject" - headers: - Location: - description: 'Contains the URI of the created EI job' - required: true - schema: - type: string - 400: - "$ref": "#/components/responses/400-BadRequest" - 404: - "$ref": "#/components/responses/404-NotFound" - 409: - "$ref": "#/components/responses/409-Conflict" - callbacks: - jobStatusNotification: - '{ $request.body.jobStatusNotificationUri }': - post: - description: 'Notify about status changes for this EI job' - requestBody: - -``` - -``` - - required: true - content: - application/json: - schema: - "$ref": "#/components/schemas/EiJobStatusObject" - responses: - 204: - description: 'Notification received' - 400: - "$ref": "#/components/responses/400-BadRequest" - jobResult: - '{$request.body.jobResultUri}': - post: - description: 'Deliver result for this EI job' - requestBody: - required: true - content: - application/json: - schema: - "$ref": "#/components/schemas/EiResultObject" - responses: - 204: - description: 'Information received' - 400: - "$ref": "#/components/responses/400-BadRequest" - get: - description: 'Query an EI job' - tags: - - Individual EI job Object - responses: - 200: - description: 'The requested EI job' - content: - application/json: - schema: - "$ref": "#/components/schemas/EiJobObject" - 404: - "$ref": "#/components/responses/404-NotFound" - delete: - description: 'Delete an EI job' - tags: - - Individual EI job - responses: - 204: - description: 'The EI job was deleted' - 404: - "$ref": "#/components/responses/404-NotFound" - -'/eijobs/{eiJobId}/status': - parameters: - - name: eiJobId - in: path - required: true - schema: - "$ref": "#/components/schemas/EiJobId" - get: - description: 'Query status for an EI job' - tags: - - Individual EI job Object - responses: - 200: - description: 'The requested EI job status' - content: - application/json: - schema: - "$ref": "#/components/schemas/EiJobStatusObject" - 404: - "$ref": "#/components/responses/404-NotFound" - -components: - schemas: - -``` - -``` - -# -# Representation objects -# -EiTypeObject: - description: 'A definition of an EI type, i.e. the JSON schemas for an EI job, its status and its result, and the job constraints'' - type: object - properties: - eiJobDefinitionSchema: - "$ref": "#/components/schemas/JsonSchema" - eiJobStatusSchema: - "$ref": "#/components/schemas/JsonSchema" - eiJobResultSchema: - "$ref": "#/components/schemas/JsonSchema" - eiJobConstraintsSchema: - "$ref": "#/components/schemas/JsonSchema" - -EiJobObject: - description: 'A generic EI job object that can be used to transport any EI job.' - type: object - properties: - eiTypeId: - type: string - jobResultUri: - type: string - jobStatusNotificationUri: - type: string - jobDefinition: - type: EiJobDefinition - required: - - eiTypeId - - jobResultUri - - jobDefinition - -EiJobDefinition: - description: 'An object representing an EI job definition.' - type: object - -EiJobStatusObject: - description: 'A generic EI job status object that can be used to transport any EI job status.' - type: object - properties: - eiJobStatus: - type: string - enum: - - ENABLED - - DISABLED - required: - - eiJobStatus - -EiResultObject: - description: 'A generic EI job result object that can be used to transport any EI job result.' - type: object - -EiJobConstraintsObject: - description: 'A generic EI job constraints object.' - type: object - -ProblemDetails: - description: 'A problem detail to carry details in an HTTP response according to RFC 7807' - type: object - properties: - type: - type: string - title: - type: string - status: - type: number - detail: - type: string - instance: - -``` - -``` - -type: string - -# -# Simple data types -# -JsonSchema: - description: 'A JSON schema following http://json-schema.org/draft-07/schema' - "$ref": "#http://json-schema.org/draft-07/schema" - -EiJobId: - description: 'EI job identifier assigned by the A1-EI Consumer when an EI job is created' - type: string - -EiTypeId: - description: 'EI type identifier assigned by the A1-EI Provider' - type: string - -JobStatusNotificationUri: - description: 'A complete callback URI defined according to IETF RFC 3986 where to send -notifications' - type: string - -JobResultUri: - description: 'A complete callback URI defined according to IETF RFC 3986 where to send results' - type: string - -responses: - 400-BadRequest: - description: 'Object in payload not properly formulated or not related to the method' - content: - application/problem+json: - schema: - "$ref": "#/components/schemas/ProblemDetails" - - 404-NotFound: - description: 'No resource found at the URI' - content: - application/problem+json: - schema: - "$ref": "#/components/schemas/ProblemDetails" - - 405-MethodNotAllowed: - description: 'Method not allowed for the URI' - content: - application/problem+json: - schema: - "$ref": "#/components/schemas/ProblemDetails" - - 409-Conflict: - description: 'Request could not be processed in the current state of the resource' - content: - application/problem+json: - schema: - "$ref": "#/components/schemas/ProblemDetails" - -``` - -## A.4 ML model management API - -``` - -openapi: 3.0.1 -info: - title: 'A1 Model Management Service' - version: 1.0.0 - description: | - This module is for API for A1 Model Management service. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at https://www.o-ran.org/sccl - -``` - -``` - -externalDocs: - description: 'O-RAN.WG2.TS.A1AP-R005-v06.00 A1 interface: Application Protocol' - url: 'https://www.o-ran.org/specifications' -servers: - - url: '{apiRoot}/a1-ml/v1' - variables: - apiRoot: - description: 'apiRoot as defined in clause 6.4 in O-RAN.WG2.TS.A1AP' - default: https://example.com -paths: - /training-capabilities: - get: - summary: Query AI/ML model training capabilities - tags: [All AI/ML model training capabilities] - parameters: - - name: minMemory - in: query - schema: - type: integer - - name: environmentType - in: query - schema: - type: string - - name: dependency - in: query - schema: - type: string - responses: - '200': - description: All AI/ML model training capabilities that match the given filter criteria - content: - application/json: - schema: - type: array - items: - $ref: '#/components/schemas/TrainingCapabilityInfo' - - /training-jobs: - post: - summary: Create an AI/ML model training job - tags: [Training Jobs] - requestBody: - required: true - content: - application/json: - schema: - $ref: '#/components/schemas/TrainingJobInfo' - responses: - '201': - description: Training job created - headers: - Location: - description: URI of the created training job resource - required: true - schema: - type: string - content: - application/json: - schema: - $ref: '#/components/schemas/TrainingJobInfo' - '400': - $ref: '#/components/responses/400-BadRequest' - callbacks: - trainingJobStatusNotification: - '{ $request.body#/trainingJobStatusNotificationUri }': - post: - summary: Training job status notification - requestBody: - required: true - content: - application/json: - -``` - -``` - - schema: - $ref: '#/components/schemas/TrainingJobStatus' - responses: - '204': - description: No Content - '400': - $ref: '#/components/responses/400-BadRequest' - -/training-jobs/{trainingJobId}: - delete: - summary: 'Delete an AI/ML model training job' - tags: - - Delete AI/ML model training job - responses: - '204': - description:'The AI/ML model training job was AI/ML deleted' - '404': - $ref: '#/components/responses/404-NotFound' - -/training-jobs/{trainingJobId}/status: - get: - summary: Get the status of an AI/ML model training job - tags: - - Query AI/ML model training job status - responses: - '200': - description: 'Training job status retrieved successfully' - content: - application/json: - schema: - type: array - items: - $ref: '#/components/schemas/TrainingJobStatus' - '404': - $ref: '#/components/responses/404-NotFound' - -components: - schemas: - TrainingCapabilityInfo: - type: object - properties: - environmentInfo: - type: object - description: Environment information about the AI/ML model training software environment - resourceInfo: - type: object - description: The resource information - required: [environmentInfo] - - ModelId: - type: object - description: Information identifying an AI/ML model - properties: - modelName: - type: string - description: Name of the model - modelVersion: - type: string - description: Version of the model - artifactVersion: - type: string - description: Artifact version of the model - required: [modelName, modelVersion] - - TrainingJobInfo: - type: object - description: Information related to the creation of an AI/ML model training job - properties: - modelId: - $ref: '#/components/schemas/ModelId' - modelLocation: - -``` - -``` -type: string -format: uri -description: Location of the AI/ML model -trainingDataset: -type: string -format: uri -description: Reference to the training dataset -trainingConfig: -type: object -description: Training configuration (producer-specific schema) -trainingJobStatusNotificationUri: -type: string -format: uri -description: Callback URI where notifications should be delivered -required: [modelId] - -TrainingJobStatus: -type: object -description: Information related to the status of an AI/ML model training job - -ProblemDetails: -description: 'A problem detail to carry details in an HTTP response according to RFC 7807' -type: object -properties: -type: -type: string -title: -type: string -status: -type: number -detail: -type: string -instance: -type: string - -responses: -400-BadRequest: -description: Object in payload not properly formulated or not related to the method -content: -application/problem+json: -schema: { $ref: '#/components/schemas/ProblemDetails' } -404-NotFound: -description: No resource found at the URI -content: -application/problem+json: -schema: { $ref: '#/components/schemas/ProblemDetails' } -``` - -# Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------| -| 2019.09.30 | 01.00 | First version with A1-P/v1 (A1 policy management service). | -| 2020.03.13 | 01.01 | Removal of multi-object operations and PATCH based procedures.
Included OpenAPI Specification and aligned text with it. | -| 2022.07.30 | 02.00 | Defining A1-P/v2 based on policy types. | -| 2020.11.09 | 03.00 | Defining A1-EI/v1 (A1 enrichment information service). | -| 2021.03.13 | 03.01 | Separation of application protocol from type definitions. Data models and type definitions moved to A1 interface: Type Definitions v01.00. | -| 2022.04.01 | 03.02 | Enhancing alignment and consistency between A1-P and A1-EI OpenAPIs. | -| 2022.11.17 | 04.00 | Aligning to O-RAN drafting rules.
Enhanced alignment between A1-P and A1-EI, and between A1AP and A1TD. | -| 2023.11.30 | 04.01 | ETSI PAS related editorial enhancement and applying latest template. | -| 2024.03.31 | 04.02 | Editorial enhancements and alignment of notation for status and feedback | -| 2024.07.31 | 04.03 | Updated specification designator to R004 | -| 2024.11.30 | 04.04 | Updating general referencing and for A1 service architecture | -| 2025.07.31 | 05.00 | ETSI PAS related editorial enhancement and applying latest template.
Introduction of A1-ML service operations and resources. | -| 2025.11.30 | 06.00 | Updated software license statements.
Defining A1-ML/v1 (A1 ML model management service). | \ No newline at end of file diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/04c7ffb4a475a374f52b88704ecd295f_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/04c7ffb4a475a374f52b88704ecd295f_img.jpg deleted file mode 100644 index 54823e99585d253456da1f0c6534fbf8a2f61e3d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/04c7ffb4a475a374f52b88704ecd295f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a1cd9f10e2956e3eae500ec47562fb1d3c968e2e7e3b20c0f00c9b29ba23c8a2 -size 30567 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/0827b9260fe5458dbe416ebfc78c469e_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/08783c875dd39684fee7f2a40b584c64_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/0a65720e640be13541e947c06c7a8c7f_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/1099a4137017f2d9721d546bbb1e9362_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/1142ba0197b158bb198186fe8baccc32_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/1142ba0197b158bb198186fe8baccc32_img.jpg deleted file mode 100644 index 762180d4cac5823afeca570b885adb71c4dda302..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/1142ba0197b158bb198186fe8baccc32_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d52e41b93fdba23a9fa3202a9b41be6895c2a29db2bfce3497c3bc7dd1f6ff52 -size 24084 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/14af8d47efd24c21fddf71b2415b6397_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/1baaba7a6e54e77197475726c871067d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/22af211207188ebc64d7b60ca052b367_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/22f30783614672d201275c116a5d8516_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/29f3760c0230631eb03f67030ef65ed0_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/2b3a967f6ce4f23649be995a353e39f8_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/2b3a967f6ce4f23649be995a353e39f8_img.jpg deleted file mode 100644 index 8cd0d5aced5dc4188833370dcb36ee777a8ac6d2..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/2b3a967f6ce4f23649be995a353e39f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2532a76080a964c1c4d6c956aed237bfd2d49a0904e076d8d9a539c7319edf5a -size 38456 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/366a77fdefb0097b3289b4a011911390_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/366a77fdefb0097b3289b4a011911390_img.jpg deleted file mode 100644 index 03e826fdfddb0ae8e782304064cdb0d66f2428f0..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/366a77fdefb0097b3289b4a011911390_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:914c2970139e9e6163e43f891f44f1a18d497b82424df4ad0a0c5b725ac350a5 -size 29038 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/38866d3f212726e1c8e92001ca0dd6f8_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/3f1987804d7d78bc3b3bc560e974280a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/3f1987804d7d78bc3b3bc560e974280a_img.jpg deleted file mode 100644 index 78ee2318ea9599d2c79fa6a76663ded1cee5696d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/3f1987804d7d78bc3b3bc560e974280a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bfde75d02ac40d179cfb30ccdbfdfeca025622ae425601bd5778dec15bd86ce9 -size 30375 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/3f727e6c0d6658bc53ea10905c4561dd_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/4f8349df2ca48959fefb7c42b2bc375e_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/552265bdbcf6d43d341fd018a9076269_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/552265bdbcf6d43d341fd018a9076269_img.jpg deleted file mode 100644 index 2fa1076a5a6a5f1505b1677a001934d0c3cb93b9..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/552265bdbcf6d43d341fd018a9076269_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:65f82d2027abdbbac5af8c89f67b3e50ff8e0627829c1ca7b6fccb0dcda8e3dd -size 27936 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index cd15d3d6f918cc6066ba42ec8f0244ce6a9b6549..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6278d4614448b34b99fb5bad2e01af582cf4a1c21f527994324dae32ed6c0d06 -size 4571 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/5a4e62bead259c258d069fd3663ea670_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/5a4e62bead259c258d069fd3663ea670_img.jpg deleted file mode 100644 index 108921d125fb9d6911aa6ceb4e9549a1c31515c5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/5a4e62bead259c258d069fd3663ea670_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4d9edab4fe10265f0650bcdf2a2c0070e2bb4643742a8c9f97b3b156a092fe62 -size 28779 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg deleted file mode 100644 index a49297127673801f0b66a822e1f4ce91173419b9..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/5a9282ac54ca7bc50f1d2ab6cfb376ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:45875d9470c3406a19a39267ed86fec2122db623f99fc7660a373addfb50658e -size 31241 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/5ae3023386ee15fae372871afce28865_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg deleted file mode 100644 index da43f7301f4bade1cfa1ae8d3fbc4dad5dedf91d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4f34e8380b029db0463c117db6d3113cc51d8b48958fbda47e0603bd476559e4 -size 25329 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/63e0c22852c26699d0bd095a2d796bab_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/63e0c22852c26699d0bd095a2d796bab_img.jpg deleted file mode 100644 index e8e0fa2f1ebe0963242dfac1e4b6aacfa0a4102b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/63e0c22852c26699d0bd095a2d796bab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f80c0ef55fa370301820f118a35a60548cbdfb3c2f150b06bf732dca3e8a67f3 -size 28443 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/6588b1c7f14069d96744b473ad663248_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/66c2bf11a8f117cddf67eff92d4c736c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/66c2bf11a8f117cddf67eff92d4c736c_img.jpg deleted file mode 100644 index 3e66084b227b35a8f3a8f524312fa4253db84786..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/66c2bf11a8f117cddf67eff92d4c736c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:432f6f3872c858a2cc3611dba737e29151ddd3604ee6a1f6119e11ec240322cc -size 30842 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/68d8089266ace7197304b43dcaf5d08e_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/68d8089266ace7197304b43dcaf5d08e_img.jpg deleted file mode 100644 index a346c35815ea44b20818a564d49526e6052ff201..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/68d8089266ace7197304b43dcaf5d08e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f75fe8e1b0d5d388f58befd9b2c8353477931b2cc60814a558373e1d264e848f -size 36389 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/6929132b4964d52244da61d4614bc4d6_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/6929132b4964d52244da61d4614bc4d6_img.jpg deleted file mode 100644 index 1126d767b217ab6e453d5c94f632abf3efe5faa4..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/6929132b4964d52244da61d4614bc4d6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5075311cde372ac566c8a2e5c69b35d05a1b76662a0ff19485609b992999bb06 -size 28726 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/6a5342571eca4b46338fdfb3c42a8055_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/6a9c5a85a12499d60c5a3a75c643b852_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg deleted file mode 100644 index ff38540711083b718f00473dd4dffc0b9a7f5818..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/6f341f415ee0f8c724e5d6daeb1e9b4a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1cf827c4fd117962e98c8b0ad81eab79a43e54268fba9495326e32b7c0d4345a -size 29345 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/71b0a68b4dd64961465d2b0e790538de_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/71b0a68b4dd64961465d2b0e790538de_img.jpg deleted file mode 100644 index dfb75fa6440ab55b87e1d3377767e39589c02a44..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/71b0a68b4dd64961465d2b0e790538de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2da662bbe29307a9f2c3656040b280829b0acd7d30833c5a6804dff6ac432534 -size 22062 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/7d08458fbe0bd5f306c00c16d68b25f2_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/81b34087cd6755a80f84a70cf28fba82_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8307f6b04df072c9332f9987e034272c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8307f6b04df072c9332f9987e034272c_img.jpg deleted file mode 100644 index 4999a9137413aac5e9af5d59c91ee3760e5d392c..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8307f6b04df072c9332f9987e034272c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:87710a2ea8ebf570de76c3fee3ae03da6c4d8d50115b32567ec6e28f09ab9b0f -size 32394 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/83ee9f10bd3636e192d68decf7f04cec_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8447c5519e85d7a9e029fbf321da4c4f_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/854df8ad60507803253274673f9062cf_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8b4befaffc5166da571069410e207aea_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8d129c93d18909f0643766f372e9ebf6_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8d138b6bf0be359dc7f079db4899bc41_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8d33918c43de10bb6d76f330c4f10e69_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8d33918c43de10bb6d76f330c4f10e69_img.jpg deleted file mode 100644 index 6f44201dad9e3192518984bdc098c729346e0d3f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8d33918c43de10bb6d76f330c4f10e69_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9e1cfba98a77563540a290a281a8d1e294e8c6f6fb9c3161607e25a15086da10 -size 27865 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/8fbe9e67b51710384633b6407d60420d_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/9159d999b6514420a64eae80e52f1fd5_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg deleted file mode 100644 index 43399ec6957e9c6174c2f2a6a64192cb9c3b0985..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7fe712e936f6969074c3d48d11a01b33d03deaed88ac43a51ba26ce87c5f0c4a -size 28015 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/9a6ff2584005112f32fbd551cb6f0591_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/9b59a11096b85b2bc74c6f653a354e28_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg deleted file mode 100644 index c895e0e9bbc34ffd99f979f82980e64d5f603c6e..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e3a36462d1e49382801b803fee6f1d120d67fc93ae4d6ac85443de05dccd731d -size 27918 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a28ab03366399b5e0a61445bc57e3724_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a76a30cf23764f0b907220e7c3c70ce1_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a82aef1d2f3f1a527328950e9db947ee_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg deleted file mode 100644 index 42825d5bfd6716033507c71a43ee51669a6e1cfc..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:27f448edf750589012c63172ee90485fbfd33c4c386fa0b9a61dcdf5bad3e78b -size 25243 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/b0211cee4b20034939d883ac0d70f696_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/b0211cee4b20034939d883ac0d70f696_img.jpg deleted file mode 100644 index f656f8883cb1ce2d8158698c9a4e6aed43627d07..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/b0211cee4b20034939d883ac0d70f696_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:891acdb67e2f9b5faccfb3e8933aec5032c3373bd053393784520219741d2fbf -size 27646 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/be8d4d130f4e1f103926de61c4bfc23c_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/c4315e81a5a818379fcf31519a9c2cbe_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/cb5f64aa26cee1c05257b7c6bbba7408_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/cfb98c691c1af5befe32ff9442eea511_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/cfb98c691c1af5befe32ff9442eea511_img.jpg deleted file mode 100644 index 628d01fc5c65b1902885be5ace8b651f98666f56..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/cfb98c691c1af5befe32ff9442eea511_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:75bc16b3d731c5d7037ff2662ac04d26d44f20074b74781db8a4fa8ac9b0d7fd -size 29595 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg deleted file mode 100644 index 2b4fa1490ed2a7f2b0d5506cca5cf8630229bb2a..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3c911fe010e929e4f6685ab536c75561158bf962977a19f69e5d2ff5294e9b3c -size 27953 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/d879e5f2c388bb87ee9614f63364dcf0_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/d90d939bcbf43d474efaeeaa335a635c_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/d90f17b29a73eddf151f51effa8912e0_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/dbbc0baac7341cda76cc4f8355dce23f_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/dbbc0baac7341cda76cc4f8355dce23f_img.jpg deleted file mode 100644 index 0bb4b6ebc3b7584a2ad10950bf335962b4ad9c39..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/dbbc0baac7341cda76cc4f8355dce23f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:05deccffb947cbf99aa568356bab080588eae6230a4832a448549c980442bc33 -size 29720 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/dfe556fea00682b09a59427aaf72051c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/dfe556fea00682b09a59427aaf72051c_img.jpg deleted file mode 100644 index 61ddc88d1fa10a443b56e341ae8f8829cd632d6c..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/dfe556fea00682b09a59427aaf72051c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:423ea6d290646b8331395288ab713315595ca0213f04052fcca3d33ecd56c22b -size 30068 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e11e3fe4228e889a962514269f5a000b_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e1a0d046fbe7f28f5e93a47091851747_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e1a0d046fbe7f28f5e93a47091851747_img.jpg deleted file mode 100644 index 4d0fe476d9cc1773ae9c314413e513be72703d07..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e1a0d046fbe7f28f5e93a47091851747_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8b653c303edaf8e2869e20be81f654c16515adef25ea5ace5892d5a94782b724 -size 38530 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg deleted file mode 100644 index 16f5900427aebacd406b3a62c26fb31c27733a92..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9f854cf510c5f4679b51d81bb93d749acb35282650cca3dd43a10fef8f3a80c3 -size 20532 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e266d0e53f36cd41c30f1bb5c8a11c84_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e266d0e53f36cd41c30f1bb5c8a11c84_img.jpg deleted file mode 100644 index 4db251a673f2cd9ee34eed5e82bf5634c1f56e97..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e266d0e53f36cd41c30f1bb5c8a11c84_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fc5ec0d9bb9213333985bdcf57775bfaccbbab34862fe87da3967b7f184b98d8 -size 25931 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e32e1bcf367a284cc7a4186056810d22_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e511e373339b5f948f239b19e0c37dd4_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e87df69ebd4cd2dbbf6749079e6c057a_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f1fbb1287d999c7034742de35bdab836_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f1fbb1287d999c7034742de35bdab836_img.jpg deleted file mode 100644 index c96304640b172c338b7fd60ebd61a488e8457c31..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f1fbb1287d999c7034742de35bdab836_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e19db6726dd8ae68e972175674583d37bc4331dfb159d7e78af40cecac1e547b -size 25938 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f250ba4162fe40d8ddfd05b74fa48895_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f3d768b0299c4763bc703b606391c48b_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f74adaa1840504407cd4272995426f82_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f7d969388c4f7e30cd04a061314bfa0e_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f7d969388c4f7e30cd04a061314bfa0e_img.jpg deleted file mode 100644 index 33dd88e9c41982a78dba7721ad55eb203cc6b576..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f7d969388c4f7e30cd04a061314bfa0e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:01241cdd4d6f28a3dca7c6911bc9012b3c12eeba63195ff476daaad1797a4b6a -size 24780 diff --git a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/f7dbd497160f02888f34fdf243648aa2_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/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1AP-R005-v06.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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/doc.md b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/doc.md deleted file mode 100644 index 6d157602d46987f9da3363c9a7200a3f31623f5f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/doc.md +++ /dev/null @@ -1,794 +0,0 @@ - - -# --- **A1 interface: General Aspects and Principles** - -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..... | 6 | -| 3.3 Abbreviations ..... | 6 | -| 4 General Aspects..... | 6 | -| 4.1 A1 architecture ..... | 6 | -| 4.1.1 General..... | 6 | -| 4.1.2 Role of A1 in the O-RAN architecture ..... | 7 | -| 4.1.3 A1 service architecture ..... | 7 | -| 4.2 A1 interface general principles..... | 9 | -| 4.3 A1 interface specification objectives..... | 10 | -| 4.4 A1 interface capabilities..... | 10 | -| 5 Functions of the A1 interface ..... | 11 | -| 5.1 Policy management ..... | 11 | -| 5.1.1 Introduction..... | 11 | -| 5.1.2 The policy management function..... | 11 | -| 5.1.3 Lifecycle aspects of A1 policies ..... | 12 | -| 5.1.4 Identification and scope of A1 policies..... | 13 | -| 5.1.5 A1 policy content..... | 14 | -| 5.2 A1 enrichment information ..... | 15 | -| 5.2.1 Introduction..... | 15 | -| 5.2.2 The enrichment information function ..... | 15 | -| 5.2.3 Lifecycle aspects of A1 enrichment information ..... | 15 | -| 5.2.4 Identification of A1 enrichment information ..... | 17 | -| 5.2.5 A1 enrichment information format and delivery ..... | 17 | -| 5.3 ML model management..... | 17 | -| 5.3.1 Introduction..... | 17 | -| 6 Signalling procedures of the A1 interface ..... | 17 | -| 6.1 General ..... | 17 | -| 6.2 Policy related procedures ..... | 17 | -| 6.3 Enrichment information transfer procedures ..... | 18 | -| 6.4 ML model related procedures..... | 18 | -| 7 A1 interface protocol structure..... | 19 | -| 8 Other A1 interface specifications ..... | 19 | -| 8.1 A1 TS-family overview..... | 19 | -| 8.2 A1 interface: Use Cases and Requirements..... | 20 | -| 8.3 A1 interface: Transport Protocol ..... | 20 | -| 8.4 A1 interface: Application Protocol..... | 20 | -| 8.5 A1 interface: Type Definitions ..... | 20 | -| 8.6 A1 interface: Test Specification ..... | 20 | -| Annex (informative): Change History ..... | 21 | - -# --- Foreword - -This Technical Specification (TS) has been produced by O-RAN Alliance Working Group 2. It is part of a TS-family covering the A1 interface as identified below: - -- "A1 interface: General Aspects and Principles"; -- "A1 interface: Use Cases and Requirements"; -- "A1 interface: Transport Protocol"; -- "A1 interface: Application Protocol"; -- "A1 interface: Type Definitions"; and -- "A1 interface: Test Specification". - -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 general aspects and principles of the A1 interface. - -# --- 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] Void. -- [2] O-RAN.WG2.TS.Use-Case-Requirements: "Non-RT RIC & A1/R1 Interface: Use Cases and Requirements". -- [3] Void. -- [4] O-RAN.WG1.TS.OAD: "O-RAN Architecture Description". -- [5] O-RAN.WG2.TS.A1TD: "A1 interface: Type Definitions" ("A1TD"). -- [6] O-RAN.WG2.TS.A1UCR: "A1 interface: Use Cases and Requirements" ("A1UCR"). -- [7] O-RAN.WG2.TS.A1AP: "A1 interface: Application Protocol" ("A1AP"). -- [8] O-RAN.WG2.TS.A1TP: "A1 interface: Transport Protocol" ("A1TP"). -- [9] O-RAN.WG2.TS.A1TS: "A1 interface: Test Specification" ("A1TS"). - -## 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.AIML: "AI/ML workflow description and requirements". -- [i.2] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". -- [i.3] O-RAN.WG2.TS.Non-RT-RIC-ARCH: "Non-RT RIC: Architecture". - -# 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.2], clause 3, the O-RAN specifications Non-RT RIC & A1/R1 Interface: Use Cases and Requirements [2], clause 3.1, Non-RT RIC: Architecture [i.3], clause 3.1, O-RAN Architecture Description [4], clause 3.1, and the following apply: - -**A1 enrichment information:** enrichment information that is collected or derived at SMO/Non-RT RIC either from non-network data sources or from network functions themselves and provided over the A1 interface to be utilized by Near-RT RIC. - -NOTE 1: A1 enrichment information is either not directly available to Near-RT RIC from O-RAN network functions via standardized interfaces or cannot be derived in Near-RT RIC from network function data due to processing or storage constraints. - -NOTE 2: Inferred/modelled information elements that can be provided over O1-CM is not considered as A1 enrichment information. - -**A1 interface:** interface between Non-RT RIC and Near-RT RIC. - -**A1 policy:** declarative policy 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 policy type:** formal schema-based definition of how an A1 policy, and its status, is expressed and validated. - -**available A1 policy type:** A1 policy type for which the policy type identifier can be discovered, and policy type information and policy type status can be queried, over the A1 interface. - -**available EI type:** EI type for which the EI type identifier can be discovered, and EI type information and EI type status can be queried, over the A1 interface. - -**declarative policy:** type of policy that uses statements to express the goals of the policy, but not how to accomplish those goals. - -**EI job:** request for delivery of A1 enrichment information expressed using formal statements. - -**EI type:** formal schema-based definition of how request and result deliveries for A1 enrichment information, and the status and constraints related to an EI job, is expressed and validated. - -**enrichment information:** information provided to an entity, in addition to the information that is generally available to it, in order to enhance the performance of its tasks. - -NOTE: The availability or usage of enrichment information is not critical for the entity to be able to perform its tasks. - -**External enrichment information:** information provided by an O-RAN external information source through a direct and secure connection with Near-RT RIC. - -NOTE: Detailed specification of a direct interface for external enrichment information is out of scope of the present document. - -**policy:** set of rules that are used to manage and control the changing and/or maintaining of the state of one or more managed objects. - -**policy objectives:** statements with the objective to reach the goal of the policy. - -**policy resources:** statements expressing the use of resources. - -**RAN intent:** expression of high-level operational or business goals to be achieved by the radio access network, allowing an operator to specify the desired SLAs that RAN needs to fulfil for all or a class of users in a given area over a period of time. - -NOTE: RAN intent is not in A1 scope. - -## 3.2 Symbols - -Void. - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [i.2], clause 4, the O-RAN specifications Non-RT RIC & A1/R1 Interface: Use Cases and Requirements [2], clause 3.3, Non-RT RIC: Architecture [i.3], clause 3.3, O-RAN Architecture Description [4], clause 3.3, and the following apply: - -| | | -|-------|--------------------------------------| -| A1-EI | A1 Enrichment Information service | -| A1-ML | A1 ML model management service | -| A1-P | A1 Policy management service | -| BSS | Business Support System | -| EI | Enrichment Information | -| IP | Internet Protocol | -| JSON | JavaScript Object Notation | -| HTTP | Hypertext Transfer Protocol | -| KPI | Key Performance Indicator | -| KQI | Key Quality Indicator | -| QoS | Quality of Service | -| QoE | Quality of Experience | -| RIC | RAN Intelligent Controller | -| SLA | Service Level Agreement | -| SMO | Service Management and Orchestration | -| TCP | Transmission Control Protocol | -| TLS | Transport Layer Security | -| UE | User Equipment | - -# 4 General Aspects - -## 4.1 A1 architecture - -### 4.1.1 General - -O-RAN Architecture Description [4] includes a Non-RT RIC and a Near-RT RIC which are connected through the A1 interface as shown in figure 4.1.1-1. - -![Diagram showing the A1 interface between Non-RT RIC and Near-RT RIC](43fec6623ab9cb223a9ff74e2d2a4402_img.jpg) - -``` - -graph TD - NonRT[Non-RT RIC] <--> |A1| NearRT[Near-RT RIC] - -``` - -Diagram showing the A1 interface between Non-RT RIC and Near-RT RIC - -Figure 4.1.1-1: A1 is the interface between the Non-RT RIC and the Near-RT RIC - -### 4.1.2 Role of A1 in the O-RAN architecture - -The Non-RT RIC function resides in the SMO layer as described in O-RAN Architecture Description [4], that also handles deployment, configuration, and data collection from RAN nodes. - -In the SMO layer there also resides functions that handle AI/ML workflow, e.g. training and update of ML models, as well as functions for deployment of ML models and other applications as described in AI/ML workflow description and requirements [i.1]. - -The SMO Layer may also have access to data other than that available in the RAN network functions and this enrichment information can be used to enhance the RAN guidance and optimization functions. - -One purpose of the SMO layer is to optimize the RAN performance towards fulfilment of the SLAs in the RAN intent. The purpose of the A1 interface is to enable the Non-RT RIC function to provide policy-based guidance, support for AI/ML workflows, and enrichment information to the Near-RT RIC function so that the RAN can optimize e.g. RRM under certain conditions. - -![Diagram illustrating the A1 interface and related components in the O-RAN architecture. The diagram shows the flow of information from RAN intent, O-RAN external information sources, and O-RAN internal information sources through the SMO (containing Non-RT RIC), Near-RT RIC, and E2 nodes. The A1 interface is highlighted between the Non-RT RIC and Near-RT RIC.](1c953f32bd34345dfd68fddf8a3736d6_img.jpg) - -The diagram illustrates the O-RAN architecture components and information flow. At the top, a large downward arrow labeled 'RAN intent' points into a dashed box labeled 'SMO'. Inside the SMO box is a rectangle labeled 'Non-RT RIC'. To the right of the SMO box, a cylinder labeled 'O-RAN external information sources' has an arrow labeled 'Information' pointing to the Non-RT RIC. Below the SMO box is a rectangle labeled 'Near-RT RIC', connected to the Non-RT RIC by a double-headed blue arrow labeled 'A1'. To the right of the Near-RT RIC, a dashed arrow labeled 'Delivery of External Enrichment Information' points to it from below. Below the Near-RT RIC is a rectangle labeled 'E2 nodes', connected to the Near-RT RIC by a double-headed green arrow labeled 'E2'. To the left of the Near-RT RIC and E2 nodes, a purple arrow labeled 'O1' points from the E2 nodes up to the Near-RT RIC. Below the E2 nodes, a label 'O-RAN internal information sources' has a dashed line pointing up towards the E2 nodes. - -Diagram illustrating the A1 interface and related components in the O-RAN architecture. The diagram shows the flow of information from RAN intent, O-RAN external information sources, and O-RAN internal information sources through the SMO (containing Non-RT RIC), Near-RT RIC, and E2 nodes. The A1 interface is highlighted between the Non-RT RIC and Near-RT RIC. - -**Figure 4.1.2-1: Illustration of A1 and related interfaces in the O-RAN architecture** - -The E2 nodes in figure 4.1.2-1 refers to RAN nodes such as an O-CU-CP, an O-CU-UP, an O-DU or an O-eNB. A1 policies and A1 enrichment information derived from various (O-RAN internal and O-RAN external) sources, are provided by the Non-RT RIC to the Near-RT RIC via the A1 interface. - -### 4.1.3 A1 service architecture - -#### 4.1.3.1 A1 policy management service (A1-P) - -The A1 policy management service (A1-P), and the policy related procedures listed in clause 6.2, are defined for communication between an A1-P service consumer referred to as A1-P Consumer and an A1-P service producer referred to as A1-P Producer. SMO/Non-RT RIC framework takes the role of A1-P Consumer and Near-RT RIC takes the role of A1-P Producer as illustrated in figure 4.1.3.1-1. - -![Diagram of A1-P interface showing SMO/Non-RT RIC framework with A1-P Consumer and Near-RT RIC with A1-P Producer connected via A1-P interface.](990567efebf979be51f56d1150012c9d_img.jpg) - -``` - -graph TD - subgraph SMO_NonRT_RIC_framework [SMO/Non-RT RIC framework] - A1P_Consumer[A1-P Consumer] - end - subgraph Near_RT_RIC [Near-RT RIC] - A1P_Producer[A1-P Producer] - end - A1P_Producer -- A1-P --> A1P_Consumer - -``` - -Diagram of A1-P interface showing SMO/Non-RT RIC framework with A1-P Consumer and Near-RT RIC with A1-P Producer connected via A1-P interface. - -**Figure 4.1.3.1-1: A1-P** - -Based on high level goals for the system expressed in RAN intent, and on observables (events and counters) provided over O1, the Non-RT RIC can define policies that are provided to the Near-RT RIC over the A1 interface. The purpose of the A1 policies is to guide the RAN performance towards the overall goal expressed in RAN intent. The A1 policies are declarative policies that contain statements on policy objectives and policy resources applicable to e.g. UEs and cells. - -The Non-RT RIC can manage the A1 policies based on A1 policy status and feedback information provided by the Near-RT RIC, and on the network status provided over O1. The Non-RT RIC can use the O1 observables to continuously evaluate the impact of the A1 policies towards fulfilment of the RAN intent and based on internal conditions it can decide to issue/update the goals expressed in the A1 policies. - -The Near-RT RIC functions based on its internal functions or applications, the configuration received over O1 and the temporary policies received over A1. The A1 policies may not survive a re-start of the Near-RT RIC. - -To support the policy enforcement in the Near-RT RIC, the Non-RT RIC can provide enrichment information over the A1 interface. - -#### 4.1.3.2 A1 enrichment information service (A1-EI) - -The A1 enrichment information service (A1-EI), and the enrichment information transfer procedures listed in clause 6.3, are defined for communication between an A1-EI service consumer referred to as A1-EI Consumer and an A1-EI service producer referred to as A1-EI Producer. SMO/Non-RT RIC framework RIC takes the role of A1-EI Producer and Near-RT RIC takes the role of A1-P Consumer as illustrated in figure 4.1.3.2-1. - -![Diagram of A1-EI interface showing SMO/Non-RT RIC framework with A1-EI Producer and Near-RT RIC with A1-EI Consumer connected via A1-EI interface.](7affafe7362a2d2d072e9d4bf515f0bb_img.jpg) - -``` - -graph TD - subgraph SMO_NonRT_RIC_framework [SMO/Non-RT RIC framework] - A1EI_Producer[A1-EI Producer] - end - subgraph Near_RT_RIC [Near-RT RIC] - A1EI_Consumer[A1-EI Consumer] - end - A1EI_Producer -- A1-EI --> A1EI_Consumer - -``` - -Diagram of A1-EI interface showing SMO/Non-RT RIC framework with A1-EI Producer and Near-RT RIC with A1-EI Consumer connected via A1-EI interface. - -**Figure 4.1.3.2-1: A1-EI** - -Enrichment information is generically defined as *information provided to an entity, in addition to the information that is generally available to it, in order to enhance the performance of its tasks*. It can be produced based on information from one or more sources, e.g. by relaying, combining, refining or analysing information from the input source(s). - -In O-RAN Architecture Description [4] it is described that external systems can provide enrichment data to the SMO. This is referred to as "O-RAN external information sources" while the network functions in the RAN are examples of "O-RAN internal information sources". - -SMO can collect information from O-RAN internal and O-RAN external information sources. Based on this information, Non-RT RIC can derive information that could be beneficial for both Non-RT RIC and/or Near-RT RIC internal functions or applications, e.g. an ML model, to improve its performance. - -In relation to the A1 interface, two types of enrichment information are distinguished: A1 enrichment information and external enrichment information. - -The A1 interface is used for discovery, request, and delivery of A1 enrichment information. - -The A1 interface is also used for the discovery of external enrichment information and the SMO / Non-RT RIC is responsible for the authentication of the source and the security of the direct connection. - -NOTE: The handling of direct connections, and discovery or delivery of external enrichment information involving the A1 interface is not defined in the present document. - -#### 4.1.3.3 A1 ML model management service (A1-ML) - -The A1 ML model management service (A1-ML), and the ML model related procedures listed in clause 6.4, are defined for communication between an A1-ML service consumer referred to as A1-ML Consumer and an A1-ML service producer referred to as A1-ML Producer. Depending on the use case, SMO/Non-RT RIC framework takes the role of A1-ML Producer and Near-RT RIC takes the role of A1-ML Consumer, or SMO/Non-RT RIC framework takes the role of A1-ML Consumer and Near-RT RIC takes the role of A1-ML Producer, as illustrated in figure 4.1.3.3-1. - -![Diagram of A1-ML service roles between SMO/Non-RT RIC framework and Near-RT RIC.](0bf9346902e9a3bdabf05ceacc1947f5_img.jpg) - -The diagram illustrates the A1-ML service roles between the SMO/Non-RT RIC framework and the Near-RT RIC. The SMO/Non-RT RIC framework is shown in the top box, containing an 'A1-ML Producer' and an 'A1-ML Consumer'. The Near-RT RIC is shown in the bottom box, containing an 'A1-ML Consumer' and an 'A1-ML Producer'. Two vertical double-headed arrows connect the top and bottom boxes, labeled 'A1-ML'. The left arrow connects the 'A1-ML Producer' in the top box to the 'A1-ML Consumer' in the bottom box. The right arrow connects the 'A1-ML Consumer' in the top box to the 'A1-ML Producer' in the bottom box. - -Diagram of A1-ML service roles between SMO/Non-RT RIC framework and Near-RT RIC. - -Figure 4.1.3.3-1: A1-ML - -The A1-ML service supports AI/ML workflows between SMO/Non-RT RIC and Near-RT RIC. - -SMO/Non-RT RIC and Near-RT RIC can exchange AI/ML model training related messages via A1 interface. - -## 4.2 A1 interface general principles - -The general principles for the specification of the A1 interface are as follows: - -- the A1 interface is an open logical interface within O-RAN architecture between the Non-RT RIC functionality in the SMO and the Near-RT RIC functionality in the RAN; - -- the A1 interface enables a multi-vendor environment and is independent of specific implementations of the SMO, Non-RT RIC, and Near-RT RIC; -- the A1 interface is defined in an extensible way that enables new services and data types to be added without needing to change the protocol stack or the procedures; -- the A1 interface enables policy-based guidance (objective, resource) of radio resource management internal functions or applications that are part of Near-RT RIC; -- the A1 interface enable mechanisms for Near-RT RIC to provide status and feedback information regarding enforcement of A1 policies to Non-RT RIC; -- the policy enforcement service in Near-RT RIC requires that the policies transferred over A1 interface are expressed using a standardized mechanism (language, syntax, etc.); -- the A1 interface enables transmission of A1 enrichment information from Non-RT RIC to Near-RT RIC as needed by Near-RT RIC; -- the A1 interface enables Near-RT to discover available enrichment information for which secure delivery can be provided, and to request delivery of enrichment information; -- A1 policies are created, modified, and deleted by the Non-RT RIC; -- the A1 policies are enforced until deleted and it is the responsibility of Non-RT RIC to create and delete policies based on context information e.g. observability from RAN indicating RAN intent fulfilment received over O1; -- EI jobs are created, modified, and deleted by the Near-RT RIC based on the needs of its internal functions; -- the Non-RT RIC delivers A1 enrichment information to the Near-RT RIC according to an EI job as long as the EI job is enabled and until it is deleted; and -- the A1 interface enables mechanisms for SMO/Non-RT RIC to exchange AI/ML model training related messages with Near-RT RIC. - -## 4.3 A1 interface specification objectives - -The A1 interface specification facilitates the following: - -- inter-connection of Non-RT RIC functionality in the SMO with Near-RT RIC functionality in the Radio Access Network supplied by different manufacturers; -- provision of policies for individual UEs or groups of UEs, or for individual cells or group of cells; -- provision of status and feedback from Near-RT RIC that enables Non-RT RIC to monitor the enforcement of policies; -- provision of enrichment information as requested by Near-RT RIC; and -- exchange of AI/ML model training related messages between SMO/Non-RT RIC and Near-RT RIC. - -## 4.4 A1 interface capabilities - -As described in Non-RT RIC & A1/R1 Interface: Use Cases and Requirements [2], the A1 interface supports: - -- transfer of policy management information from Non-RT RIC to Near-RT RIC; -- policy status and feedback information from Near-RT RIC to Non-RT RIC; -- discovery and request of A1 enrichment information from Near-RT RIC to Non-RT RIC and delivery of A1 enrichment information from Non-RT RIC to Near-RT RIC; and - -- request of AI/ML model training, and transfer of AI/ML model training status between SMO/Non-RT RIC and Near-RT RIC. - -As described in A1TP [8], clause 7, the A1 interface supports: - -- Authorization of requests to access A1 services. - -# --- 5 Functions of the A1 interface - -## 5.1 Policy management - -### 5.1.1 Introduction - -The purpose of A1 policies is to enable the Non-RT RIC function in the SMO to guide the Near-RT RIC function, and hence the RAN, towards a better fulfilment of the RAN intent. - -NOTE: RAN intent represents e.g. the SLA from the BSS (Business Support System) that the RAN is to fulfil for all users or for a subset of users (e.g. QCI or slice). Based on the permanent configuration and the available resources, the RAN strives to deliver the expected QoS for the users. - -By utilising the observability over O1, and the A1 policy status and feedback information, the Non-RT RIC can conclude that the RAN intent is not achieved. The Non-RT RIC can then decide to use A1 policies that enable the Near-RT RIC to e.g. optimize RRM for a single UE or for a group of UEs. - -EXAMPLE: When the Non-RT RIC understands that the available resources in a certain area are not enough to fulfil the SLA for all users in a slice, it can then decide to temporarily change the QoS targets for some users (dynamic group of users) belonging to the same slice (pre-defined group of users). - -There are different types of A1 policies referred to as A1 policy types. A Non-RT RIC need not use all A1 policy types, and a specific function in the Near-RT RIC may only support one specific A1 policy type. Non-RT RIC can discover available A1 policy types over the A1 interface. - -NOTE: As A1 policy types represent capabilities of the Near-RT RIC and they may also be indicated to the Non-RT RIC in other ways. - -### 5.1.2 The policy management function - -The policy management function is used by the Non-RT RIC to provision and manage A1 policies in the Near-RT RIC. The Non-RT RIC is responsible for definition and administration of A1 policies. - -The function is used to query the available A1 policy types in the Near-RT RIC. - -The function is used to create, update, and delete A1 policies in the Near-RT RIC. - -The function is used to query the presence, content, and run-time status of an A1 policy in the Near-RT RIC. - -The function is supported by A1 policy status and feedback information from the Near-RT RIC to the Non-RT RIC. - -NOTE 1: As the Near-RT RIC cannot change the content of a policy, only a change in enforcement status can be notified. If context is changed in such a way that the enforcement status of a policy is changed, the Non-RT RIC is notified and may decide to delete the policy. - -NOTE 2: Feedback on the fulfilment of A1 policies in the Near-RT RIC is not transferred over the A1 interface. The Non-RT RIC can estimate the fulfilment of A1 policies based on O1 observables. - -NOTE 3: Before and after the creation of an A1 policy, the Non-RT RIC can monitor the network to understand the effect of the A1 policy on performance. Performance monitoring or tracing is not handled over the A1 interface. - -### 5.1.3 Lifecycle aspects of A1 policies - -Per default, the Near-RT RIC controls the RAN based on the persistent configuration. The RAN operation can be optimized using A1 policies that, compared to the persistent configuration, - -- are not critical to traffic; -- have temporary validity; -- handle individual UE or dynamically defined groups of UEs; -- express goals for the optimization rather than direct changes to the configuration; and -- are non-persistent, i.e., do not survive a restart of the Near-RT RIC. - -An A1 policy exists in the Near-RT RIC after it has been created by the Non-RT RIC using the Create policy procedure and accepted by the Near-RT RIC. - -For an A1 policy, the Near-RT RIC can provide status and feedback information to the Non-RT RIC. - -The Near-RT RIC continuously evaluates the policy conditions versus the environment and notifies the Non-RT RIC in case the enforcement status of the policy changes due to e.g. environment changes. - -When a create A1 policy request is accepted, the Non-RT RIC can assume that the policy is enforced until policy status is queried or a change in enforcement status is notified. - -An A1 policy can be updated by the Non-RT RIC using the Update policy procedure. After the update, the policy is evaluated and enforced by the Near-RT RIC based on the updated policy statements. - -An A1 policy exists in the Near-RT RIC until it is deleted by the Non-RT RIC using the Delete policy procedure. - -The states related to policy lifecycle and policy enforcement are illustrated in figure 5.1.3-1. - -![State transition diagram for policy in the Non-RT RIC. The diagram shows two main states: ENFORCED and NOT_ENFORCED. Transitions include Create policy (1), Update policy (2), Query policy (4), Query policy status (4), Delete policy (3), Query policy status (5), Notify policy status (5), and Notify policy status (6).](5a95b187de0044da69b7322e04761b86_img.jpg) - -``` - -stateDiagram-v2 - [*] --> ENFORCED : Create policy (1) - ENFORCED --> ENFORCED : Query policy (4) -Update policy (2) -Query policy status (4) - ENFORCED --> [*] : Delete policy (3) - ENFORCED --> NOT_ENFORCED : Query policy status (5) -Notify policy status (5) - NOT_ENFORCED --> ENFORCED : Update policy (2) -Query policy status (6) -Notify policy status (6) - NOT_ENFORCED --> [*] : Delete policy (3) - NOT_ENFORCED --> NOT_ENFORCED : Query policy (4) -Query policy status (4) - -``` - -State transition diagram for policy in the Non-RT RIC. The diagram shows two main states: ENFORCED and NOT\_ENFORCED. Transitions include Create policy (1), Update policy (2), Query policy (4), Query policy status (4), Delete policy (3), Query policy status (5), Notify policy status (5), and Notify policy status (6). - -**Figure 5.1.3-1: State transition diagram for policy in the Non-RT RIC** - -The state transition diagram in figure 5.1.3-1 illustrates the Non-RT RIC view of the states of a policy instance during the policy lifecycle. All state transitions are related to A1 policy related procedures as listed in clause 6.1 with the following notes: - -- NOTE 1: A Create policy request is accepted after the policy has been validated and considered as being possible to enforce. -- NOTE 2: An Update policy request is accepted after the policy has been validated and considered as being possible to enforce, it does not cause a state transition unless it makes a policy possible to enforce. -- NOTE 3: A Delete policy request, whether accepted or not, always leads to that the Non-RT RIC considers the policy as deleted. -- NOTE 4: A Query policy request does not cause a state transition, and a Query policy status request does not cause a state transition in case the enforcement status has not changed. -- NOTE 5: A Query policy request or a Notify policy status cause a state transition in case the enforcement status has changed from ENFORCED to NOT\_ENFORCED. -- NOTE 6: A Query policy request or a Notify policy status cause a state transition in case the enforcement status has changed from NOT\_ENFORCED to ENFORCED. - -### 5.1.4 Identification and scope of A1 policies - -#### 5.1.4.0 General - -An A1 policy type is identified by the policy type identifier (PolicyTypeId). Different policy types have different PolicyTypeIds. Based on the PolicyTypeId, schemas are identified and used for creation, validation, and formulation, and for query of the status, of A1 policies of that type. - -An A1 policy is identified by a policy identifier (PolicyId) that shall be assigned by Non-RT RIC. The PolicyId shall be locally unique within Non-RT RIC and sent in the policy request operations that carry representations of A1 policies. - -A1 policies consist of a scope identifier and one or more policy statements as illustrated in figure 5.1.4.0-1. The scope identifier represents what the policy statements are to be applied on (e.g. UEs, QoS flows, or cells). The policy statements represent the goals to the Near-RT RIC and covers policy objectives and policy resources. - -![Diagram illustrating the structure of an A1 policy. It shows a box labeled 'A1 policy' containing two sub-boxes: 'Scope identifier' and 'Policy statement(s)'.](4636adff5682a064f0ae5f13a1d464a6_img.jpg) - -``` - -graph TD - subgraph A1_policy [A1 policy] - direction TB - SI[Scope identifier] - PS[Policy statement(s)] - end - -``` - -Diagram illustrating the structure of an A1 policy. It shows a box labeled 'A1 policy' containing two sub-boxes: 'Scope identifier' and 'Policy statement(s)'. - -Figure 5.1.4.0-1: Illustration of the structure of an A1 policy - -By including policy statements with policy objectives, - -- the quality of experience can be optimized for UEs or QoS flows that are identified either explicitly by e.g. a UE identifier or a QoS identifier, or implicitly by e.g. a group identifier from which the Near-RT RIC can deduce a set of UEs; and -- energy saving can be applied to one or more cells that are identified either explicitly by e.g. a cell identifier or implicitly by e.g. a list of identifiers from which the Near-RT RIC can deduce a set of cells. - -By including policy statements with policy resources, UEs can e.g. be made to avoid certain cells or the radio network can be optimized in specific areas. - -The identifiers that can be used as scope identifier in A1 policies are defined as data types in the A1 Type Definitions specification [5], clause 6.3.1. The scope identifier can be composed by a single or a by a combination of these as defined for each policy type definition in A1TD [5], clause 7.2. - -#### 5.1.4.1 Identification of UEs - -In the scope of A1 policies, a UE is identified by a UE identifier. The UE identifier identifies a logical UE entity that is known to the RAN and measurements related to it. It does not identify any hardware equipment or user subscription. - -The UE identifier is used for correlating O1-PM data with service targets and enables evaluation of the fulfilment of policies. In order to be able to utilize non-RAN data for the usage of A1 policies, non-RAN data need to include identifiers that can be correlated with the UE identifier by the Non-RT RIC. - -If the Non-RT RIC needs to express policies for multiple individual UEs, it can be done through a set of policies, one for each individual UE. - -#### 5.1.4.2 Identification of groups of UEs - -In the scope of A1 policies, a group of UEs can be identified based on a group identifier. - -When the Near-RT RIC receives a group identifier in an A1 policy, it may resolve it into a set of UEs that are present in the nodes controlled by the Near-RT RIC and applies the policy statements to each one of the UEs. - -#### 5.1.4.3 Identification of slices - -When the Near-RT RIC receives a slice identifier in an A1 policy, it may resolve it into a set of UEs and a set of QoS flows that are present in the nodes controlled by the Near-RT RIC and applies the policy statements to each one of the UEs or the QoS flows. - -#### 5.1.4.4 Identification of QoS flows - -When the Near-RT RIC receives a QoS identifier in an A1 policy, it may resolve it into a set of QoS flows (that are related to the applications that the Non-RT RIC is intending to optimize) and the set of UEs (that are present in the nodes controlled by the Near-RT RIC) for which they apply. Then it applies the policy statements to each one of the UEs and QoS flows. - -#### 5.1.4.5 Identification of cells - -In the scope of A1 policies, a part of the radio network can be identified based on a cell identifier or a set of cell identifiers. - -When the scope identifier in an A1 policy contains one or more cell identifiers, the policy statement may contain policy resources and the policy may implicitly impact on multiple UEs handled by the specified cell(s). - -An A1 policy is applied to a specific cell when a cell identifier is included in the scope. An A1 policy is applied to a group of cells when a set of cell identifiers is included in the scope. When no cell identifier or set of cell identifiers is included in the scope, a policy may apply to multiple cells. - -If the Non-RT RIC needs to express policies for a group of cells (i.e. a set of cells), it is done through a set of policies for individual cells or through a set of cell identifiers or other identifiers that the Near-RT RIC may resolve into a set of cell identifiers. - -### 5.1.5 A1 policy content - -#### 5.1.5.1 General - -In addition to a scope identifier, an A1 policy contains policy statements. There are several kinds of policy statements that cover policy objectives and policy resources. - -NOTE: The detailed rules for how to formulate policy statements, and which combinations of identifiers and statements that are allowed, are specified for the policy types defined in A1TD [5], clause 7.2. - -#### 5.1.5.2 Policy objectives - -A statement for policy objectives expresses the goal for the policy. It can be related to e.g. QoS or QoE targets, or KPI or KQI targets. For detailed definitions of statements for policy objectives, see A1TD [5], clause 6.3.3. - -There is normally only one statement for policy objectives in an A1 policy. - -#### 5.1.5.3 Policy resources - -A statement for policy resources expresses the conditions for resource usage for the policy. It can be related to e.g. cell preferences. For detailed definitions of statements for policy resources, see A1TD [5], clause 6.3.4. - -Statements for policy resources can be combined with a statement for policy objectives in an A1 policy. - -## 5.2 A1 enrichment information - -### 5.2.1 Introduction - -The purpose of A1 enrichment information is to enable the Near-RT RIC to improve its RAN optimization performance by utilizing information that is not available within the RAN. The information sources can be O-RAN internal and O-RAN external, and the derived A1 enrichment information can be provided by the Non-RT RIC over the A1 interface. - -There are different types of A1 enrichment information referred to as EI types. A Near-RT RIC may not need to use all EI types, and a specific function in the Near-RT RIC may only need one specific type of A1 enrichment information. - -An EI type is identified by the EI type identifier (EiTypeId). Based on the EiTypeId, information can be provided about the A1 enrichment information properties and how to request delivery of the A1 enrichment information. - -The Near-RT RIC can discover available EiTypeIds over A1 and request delivery of A1 enrichment information related to an available EiTypeId. The Non-RT RIC controls the access to A1 enrichment information and how the connection for delivery of the enrichment information can be made. - -NOTE: There may be functions in the SMO or the Non-RT RIC that also utilize enrichment information for their tasks, it may be the same or different enrichment information as exposed over the A1 interface. This is outside the scope of the present document to describe. - -### 5.2.2 The enrichment information function - -The enrichment information function is used by the Non-RT RIC to produce and make A1 enrichment information available to the Near-RT RIC. The Non-RT RIC is responsible for exposure and secure delivery of A1 enrichment information. - -The function is used to publish available EiTypeIds over A1. - -The function is used to deliver A1 enrichment information for an EiTypeId based on an EI job. - -### 5.2.3 Lifecycle aspects of A1 enrichment information - -#### 5.2.3.1 Registration of enrichment information source - -Before the Non-RT RIC can provide a certain EiTypeId over A1, the SMO needs to set-up the collection of input information from O-RAN internal and/or external sources and the Non-RT RIC needs to set-up the functions that produce the enrichment information based on the input information and deliver it. When onboarding and set-up is complete, the new EiTypeId can be discovered over A1. - -#### 5.2.3.2 Discovery of enrichment information - -##### 5.2.3.2.0 General - -Before a Near-RT RIC can use A1 enrichment information it needs to identify that the needed EiTypeId is available and how to access it. - -The Near-RT RIC can discover available EiTypeIds using A1-EI. The Non-RT RIC controls which EiTypeIds are discoverable and accessible by a specific Near-RT RIC. - -For a specific EiTypeId, the Near-RT RIC can request a detailed description of the enrichment information provided and how to formulate a request for delivery of it. - -##### 5.2.3.2.1 Lifecycle aspects of EI types - -The Non-RT RIC is responsible for ensuring that the EI types that are discoverable over A1 can be used for EI jobs and delivery of EI job results. An EiTypeId shall not be made available until EI jobs can be created, and EI job results delivered for that EI type. - -In case Non-RT RIC detects that it is no longer able to deliver EI job results for an EI type, the EiTypeId should no longer be discoverable over A1. - -#### 5.2.3.3 Request and Delivery of enrichment information - -##### 5.2.3.3.0 General - -A1 enrichment information can be delivered to the Near-RT RIC in different ways depending on the type of the A1 enrichment information or on the needs from the using internal function or application. - -A1 enrichment information can be delivered on an as per needed basis, due to an event or continuously. For continuous delivery, different mechanisms can be used depending on the volume of enrichment information to be delivered. - -Following the discovery that an EiTypeId is available, the request and delivery of A1 enrichment information is done in two steps: - -- 1) First the Near-RT RIC requests over A1 to get A1 enrichment information for the EiTypeId by creating an EI job that contains a description of the information that is requested and which delivery mechanism to use. -- 2) Then the Non-RT RIC sets up the appropriate connection and delivers A1 enrichment information according to the agreed details for the EI job. - -##### 5.2.3.3.1 Lifecycle aspects of EI jobs - -The Near-RT RIC can initiate creation, update, and deletion of EI jobs. The EI job is created when the Near-RT RIC needs A1 enrichment information of a specific EI type and the EI job is deleted when the Near-RT RIC no longer needs the information. - -In case the Near-RT RIC temporarily cannot use delivered EI, it can discard or buffer the received EI or stop the EI delivery by deleting the EI job and re-create it when it is ready to receive delivered EI. - -The Near-RT RIC may query existing EI jobs after a re-start, and either delete, update, or keep the EI jobs if still relevant. - -##### 5.2.3.3.2 Lifecycle aspects of EI job results - -The Non-RT RIC is responsible for the set-up of connections to the Near-RT RIC for the delivery of EI job results according to the agreed EI job. The delivery of the EI job results is started when the EI job is created and stopped when the EI job is deleted. - -In case delivery connections cannot be set-up to the Near-RT RIC, the Non-RT RIC need not buffer any information produced while the delivery connections are not successful. In case the EI cannot be successfully produced or delivered according to an agreed EI job, the Near-RT RIC can detect this through the delivered EI job results, or through lack of delivered EI job results. - -The Near-RT RIC may evaluate the received EI job results. If the received EI job results are not according to expectations, the Near-RT RIC can update the EI job or delete it. - -### 5.2.4 Identification of A1 enrichment information - -A1 enrichment information is identified by the A1 enrichment information identifier (EiTypeId). Different types of A1 enrichment information have different EiTypeIds. - -The Near-RT RIC can request delivery of A1 enrichment information from the Non-RT RIC by creating an EI job for an EiTypeId. The EI job and the EI job results are identified by an EI job identifier (EiJobId) assigned by the Near-RT RIC. - -### 5.2.5 A1 enrichment information format and delivery - -#### 5.2.5.1 Push based delivery - -When A1 enrichment information has been produced during an EI job, it is pushed from the Non-RT RIC to the Near-RT RIC. This can be done once, regularly or event based depending on the conditions set for the EI job. - -## 5.3 ML model management - -### 5.3.1 Introduction - -The purpose of A1 ML model management is to enable: - -- the Near-RT RIC to request the Non-RT RIC to train an AI/ML model; -- the Non-RT RIC to request the Near-RT RIC to train an AI/ML model; -- the Near-RT RIC to query the training status of an AI/ML model that is trained at Non-RT RIC/SMO; -- the Non-RT RIC to query the training status of an AI/ML model that is trained at Near-RT RIC; -- the Non-RT RIC to discover training capabilities provided by Near-RT RIC's; and -- the Near-RT RIC to discover training capabilities provided by Non-RT RIC/SMO. - -# --- 6 Signalling procedures of the A1 interface - -## 6.1 General - -The usage of the procedures listed in this clause are described in A1UCR [6] and defined in detail in A1AP [7]. - -## 6.2 Policy related procedures - -Policy related procedures include: - -- Query policy type identifiers procedure; -- Query policy type procedure; - -- Query policy type status procedure; -- Notify policy type status procedure; -- Create policy procedure; -- Query policy identifiers procedure; -- Query policy procedure; -- Update policy procedure; -- Delete policy procedure; -- Query policy status procedure; and -- Notify policy status procedure. - -## 6.3 Enrichment information transfer procedures - -A1 enrichment information related procedures include: - -For EI discovery: - -- Query EI type identifiers; -- Query EI type; -- Query EI type status, and -- Notify EI type status. - -For EI job control: - -- Query EI job identifiers; -- Create EI job; -- Query EI job; -- Update EI job; -- Delete EI job; -- Query EI job status; and -- Notify EI job status. - -For EI delivery: - -- Deliver EI job result. - -## 6.4 ML model related procedures - -A1 ML model related procedures include: - -- Query AI/ML model training capabilities; -- Request AI/ML model training; -- Cancel AI/ML model training; -- Query AI/ML model training job status; and - -- Notify AI/ML model training job status. - -# 7 A1 interface protocol structure - -The protocol stack of the A1 interface is shown in figure 7-1. The transport network layer is built on IP transport. For the secure and reliable transport of messages, HTTP/TLS is added on top of TCP/IP. The application layer protocol is based on a RESTful approach with transfer of JSON formatted policy statements. - -The detailed description is provided in A1TP [8]. - -![Figure 7-1: Illustration of the A1 protocol stack. The diagram shows two protocol stacks for Non-RT RIC and Near-RT RIC. The layers, from top to bottom, are: Data Interchange (JSON), Application (HTTP), Security (TLS), Transport (TCP), Network (IP), Data link (Data link layer), and Physical (Physical layer). The layers are connected by horizontal lines between the two stacks.](a734898ce18e972938949637c32a34f4_img.jpg) - -| | | | -|------------------|-----------------|-----------------| -| Data Interchange | JSON | JSON | -| Application | HTTP | HTTP | -| Security | TLS | TLS | -| Transport | TCP | TCP | -| Network | IP | IP | -| Data link | Data link layer | Data link layer | -| Physical | Physical layer | Physical layer | -| | Non-RT RIC | Near-RT RIC | - -Figure 7-1: Illustration of the A1 protocol stack. The diagram shows two protocol stacks for Non-RT RIC and Near-RT RIC. The layers, from top to bottom, are: Data Interchange (JSON), Application (HTTP), Security (TLS), Transport (TCP), Network (IP), Data link (Data link layer), and Physical (Physical layer). The layers are connected by horizontal lines between the two stacks. - -Figure 7-1: Illustration of the A1 protocol stack - -# 8 Other A1 interface specifications - -## 8.1 A1 TS-family overview - -The present document is part of a TS-family covering the A1 interface. The other specifications cover Use Cases and Requirements, Transport Protocol, Application Protocol, Type Definitions, and Test cases. - -The relations between the A1 specifications and their relations to other O-RAN specifications for architecture and for use cases and requirements are illustrated in figure 8.1-1. - -![Figure 8.1-1: Overview of relations between A1 specifications. The diagram shows the flow and relationships between various O-RAN specifications leading to the A1 family of Technical Specifications. Inputs include WG1: O-RAN Architecture Description, O-RAN Security Requirements and Protocols Specifications, and WG1: Use Cases Detailed Specification. These lead to WG2: Non-RT RIC Architecture Specification and WG2: Use Cases and Requirements Specification. These then lead into the A1 family of Technical Specifications, which includes A1 General Aspects and Principles, A1 Transport Protocol Specification, A1 Use cases and Requirements (Stage 2 procedures), A1 Application Protocols Specification (Stage 3 procedures), A1 Type Definitions Specification, and A1 Test Specification. Arrows indicate dependencies and flow between these components.](5445597cceefaca1ac89e710fe339325_img.jpg) - -The diagram illustrates the relationships between various O-RAN specifications and the A1 family of Technical Specifications. On the left, three boxes represent external specifications: 'WG1: O-RAN Architecture Description', 'O-RAN Security Requirements and Protocols Specifications', and 'WG1: Use Cases Detailed Specification'. Arrows from the first two point to 'WG2: Non-RT RIC Architecture Specification'. Arrows from the third point to 'WG2: Use Cases and Requirements Specification'. Both WG2 specifications point into a dashed box labeled 'A1 family of Technical Specifications'. Inside this box, 'WG2: Non-RT RIC Architecture Specification' points to 'A1 General Aspects and Principles'. 'WG2: Use Cases and Requirements Specification' points to 'A1 Use cases and Requirements (Stage 2 procedures)'. 'A1 General Aspects and Principles' has a bidirectional arrow to 'A1 Transport Protocol Specification' and arrows to 'A1 Use cases and Requirements (Stage 2 procedures)', 'A1 Application Protocols Specification (Stage 3 procedures)', and 'A1 Type Definitions Specification'. 'A1 Transport Protocol Specification' has an arrow to 'A1 Use cases and Requirements (Stage 2 procedures)'. 'A1 Use cases and Requirements (Stage 2 procedures)' has an arrow to 'A1 Application Protocols Specification (Stage 3 procedures)'. 'A1 Application Protocols Specification (Stage 3 procedures)' has a bidirectional arrow to 'A1 Type Definitions Specification' and an arrow to 'A1 Test Specification'. 'A1 Type Definitions Specification' has an arrow to 'A1 Test Specification'. - -Figure 8.1-1: Overview of relations between A1 specifications. The diagram shows the flow and relationships between various O-RAN specifications leading to the A1 family of Technical Specifications. Inputs include WG1: O-RAN Architecture Description, O-RAN Security Requirements and Protocols Specifications, and WG1: Use Cases Detailed Specification. These lead to WG2: Non-RT RIC Architecture Specification and WG2: Use Cases and Requirements Specification. These then lead into the A1 family of Technical Specifications, which includes A1 General Aspects and Principles, A1 Transport Protocol Specification, A1 Use cases and Requirements (Stage 2 procedures), A1 Application Protocols Specification (Stage 3 procedures), A1 Type Definitions Specification, and A1 Test Specification. Arrows indicate dependencies and flow between these components. - -Figure 8.1-1: Overview of relations between A1 specifications - -## 8.2 A1 interface: Use Cases and Requirements - -A1UCR [6] describes the use cases for the A1 procedures and the related requirements. - -## 8.3 A1 interface: Transport Protocol - -A1TP [8] defines how the A1 protocol stack is based on TCP/IP, HTTP/1.1 over TLS and JSON as data interchange format. - -## 8.4 A1 interface: Application Protocol - -A1AP [7] defines the resources, the service operations and the service APIs for the A1 services including the URIs for HTTP based procedures. - -## 8.5 A1 interface: Type Definitions - -A1TD [5] defines attributes, data types and objects for HTTP based procedures and JSON examples of objects are provided. - -## 8.6 A1 interface: Test Specification - -A1TS [9] defines test cases for - -- A1 conformance testing of Non-RT RIC; -- A1 conformance testing of Near-RT RIC; and -- A1 interoperability testing between Non-RT RIC and Near-RT RIC - -based on the procedures defined in A1AP [7]. - -# Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------| -| 2019.09.30 | 01.00 | First version | -| 2020.07.30 | 02.00 | Definitions, functions and procedures for A1 enrichment information and A1 policy type description. | -| 2020.11.09 | 02.01 | Enhancing description of LCM aspects for A1 enrichment information service. | -| 2021.03.13 | 02.02 | Editorial corrections to apply latest template and update references. Enhance description of life cycle aspects for A1 policies. | -| 2021.07.16 | 02.03 | Enhancing descriptions of A1 policy scope and content. | -| 2022.07.30 | 03.00 | Adapting to ODR template and general updates to align with A1 suite specifications | -| 2022.11.17 | 03.01 | Aligning to O-RAN drafting rules. | -| 2023.11.30 | 03.02 | ETSI PAS related editorial enhancements and applying latest template. | -| 2024.03.31 | 03.03 | Editorial enhancements, alignment of notation for status and feedback, and extended cell identification. | -| 2024.07.31 | 04.00 | General aspects of A1 ML model management service | -| 2024.11.30 | 05.00 | Updated A1 service architecture, and A1 ML functions and related procedures | -| 2025.03.31 | 05.01 | Updated A1 ML related procedures | -| 2025.07.31 | 05.02 | Applying latest template | -| 2025.11.30 | 05.03 | Updated A1 ML related procedures | \ No newline at end of file diff --git a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg deleted file mode 100644 index 89a3d386ebdd6c97c1a14dc83725156c46a3a642..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/0bf9346902e9a3bdabf05ceacc1947f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e45a9a8c0af4b3208fb4f66f716531ef74695920d5bf8d4b8ca7a01f3b852834 -size 26562 diff --git a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/1c953f32bd34345dfd68fddf8a3736d6_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/1c953f32bd34345dfd68fddf8a3736d6_img.jpg deleted file mode 100644 index a339e0c23f3b1f56981aa852d39078406bfb1662..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/1c953f32bd34345dfd68fddf8a3736d6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bcc746b0f43b01361db5d3726044c87a204122a45d68b52b87b865fcdacdc40c -size 41915 diff --git a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/226f5e462c99b71e08dc9abaa5ae260c_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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg deleted file mode 100644 index e5eb097c5ec6e8a8554828b94fd0e7a9a223eea6..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/43fec6623ab9cb223a9ff74e2d2a4402_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4d19c6c601a79a5503496009f1e8018e25e6f6719d2f904b4bb64119ccbff628 -size 7529 diff --git a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/4636adff5682a064f0ae5f13a1d464a6_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/4636adff5682a064f0ae5f13a1d464a6_img.jpg deleted file mode 100644 index 1617e24e0b8dae4edff3897c34f06ca624575730..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/4636adff5682a064f0ae5f13a1d464a6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a54515a893177cfe4d38b63b0c19f3a08793252feec817c10e4c4af439565c0 -size 8471 diff --git a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/5445597cceefaca1ac89e710fe339325_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/5445597cceefaca1ac89e710fe339325_img.jpg deleted file mode 100644 index 2b27b2ce4c3d70acd08287968091ecfb4ca613d0..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/5445597cceefaca1ac89e710fe339325_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f72336525b479b6dda4baab64e3dd1cd23f79fa44d8a661a1d54dfbdebe4045 -size 63148 diff --git a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/5a95b187de0044da69b7322e04761b86_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/5a95b187de0044da69b7322e04761b86_img.jpg deleted file mode 100644 index e03ea33c5ffc07a3907497f83badcb7c0ff9b9bc..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/5a95b187de0044da69b7322e04761b86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b58b253d32d2f74251284219e020e6f485beaac6d6883a44fe221bb50113aa41 -size 59515 diff --git a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/6a5342571eca4b46338fdfb3c42a8055_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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg deleted file mode 100644 index ad523337117db7bf070ed30c17a1058ae52ceb57..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8bc5d5ad9b3f89a94e72eb36bc187eae4c0480357aeb7933ff26a3e9ac0a6c5c -size 18786 diff --git a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/83ee9f10bd3636e192d68decf7f04cec_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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/854df8ad60507803253274673f9062cf_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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/89100a6476d1d96f22c192db16502fec_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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/990567efebf979be51f56d1150012c9d_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/990567efebf979be51f56d1150012c9d_img.jpg deleted file mode 100644 index a467a5515f3c95da501e013e0bd1a31b973c482a..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/990567efebf979be51f56d1150012c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5723fcf60e19b136fafb23c25780e1217345239ebadcf9d8328cc758055b1a88 -size 19068 diff --git a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/a28ab03366399b5e0a61445bc57e3724_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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/a734898ce18e972938949637c32a34f4_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/a734898ce18e972938949637c32a34f4_img.jpg deleted file mode 100644 index 1ca4d09209136edbfae50b40642c70f97b9b394a..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/a734898ce18e972938949637c32a34f4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6e6f34c46d5152300b16d5584c8e3f0bc0ce5fa4d396a5a691e742466051277a -size 38935 diff --git a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index f3a71b98fcfc274b0603208cc5e23601d7fc924a..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:84a0e505aa8e8fcec39c03736b466858a7c1ef91abe309cdd2974ee18257e23b -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/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/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1GAP-R005-v05.03/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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/doc.md b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/doc.md deleted file mode 100644 index f86f6611c6dc5af2247c6728f79df63a4e558493..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/doc.md +++ /dev/null @@ -1,4888 +0,0 @@ - - -# --- A1 interface: Type Definitions - -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.....5 - -Modal verbs terminology.....5 - -1 Scope.....6 - -2 References .....6 - -2.1 Normative references .....6 - -2.2 Informative references.....7 - -3 Definition of terms, symbols and abbreviations.....7 - -3.1 Terms.....7 - -3.2 Symbols.....7 - -3.3 Abbreviations .....8 - -4 A1 Application data model.....8 - -4.1 Introduction .....8 - -4.2 Compatibility of A1 type definitions.....8 - -5 Generic aspects and common data types.....9 - -5.1 Encoding of attributes in A1 data types.....9 - -5.2 Current type definitions.....9 - -6 A1-P data model.....9 - -6.1 Introduction .....9 - -6.2 Simple data types and enumerations .....10 - -6.2.1 Simple data types.....10 - -6.2.2 Enumerations .....12 - -6.3 Structured data types .....13 - -6.3.1 ScopeIdentifier.....13 - -6.3.2 Structured data types for statements .....19 - -6.3.3 Statements for policy objectives .....20 - -6.3.4 Statements for policy resources .....30 - -6.4 Policy representations objects .....33 - -6.4.1 Policy object .....33 - -6.4.2 Policy status object .....34 - -6.4.3 Policy type object .....34 - -6.5 Binary data .....34 - -7 A1-P data types (A1 policy types) .....35 - -7.1 Introduction .....35 - -7.1.1 Identification and compatibility of policy types .....35 - -7.1.2 Common definitions .....35 - -7.1.3 Schema identification .....43 - -7.2 Policy type definitions.....44 - -7.2.1 QoS target .....44 - -7.2.2 QoE target.....46 - -7.2.3 Traffic steering preferences .....48 - -7.2.4 QoS optimization with resource directive.....49 - -7.2.5 QoE optimization with resource directive .....51 - -7.2.6 UE level target.....53 - -7.2.7 Slice SLA target.....55 - -7.2.8 Load balancing.....57 - -7.2.9 Energy Savings .....60 - -8 A1-EI data model .....62 - -8.1 Introduction .....62 - -8.2 Simple data types and enumerations .....63 - -8.2.1 Simple data types.....63 - -- 8.2.2 Enumerations .....63 -- 8.3 Structured data types .....64 - - 8.3.1 ScopeIdentifier.....64 - - 8.3.2 Statements for EI job definition.....64 - - 8.3.3 Statements for EI job result .....65 - - 8.3.4 Statements for EI job constraints .....67 -- 8.4 EI representations objects.....67 - - 8.4.1 EI type object.....67 - - 8.4.2 EI job object.....68 - - 8.4.3 EI job status object.....69 - - 8.4.4 EI job result object.....69 - - 8.4.5 EI job constraints object .....69 -- 8.5 Binary data .....69 -- 9 A1-EI data types (EI types).....70 - - 9.1 Introduction .....70 - - 9.1.1 Identification and compatibility of EI types .....70 - - 9.1.2 Common definitions .....70 - - 9.2 EI type definitions .....71 - - 9.2.1 UE location and velocity information.....71 -- Annex A (Informative): Policy examples.....79 - - A.1 Generic scope identifier.....79 - - A.1.1 RAN UE ID based generic scope identifier.....79 - - A.1.2 AMF UE NGAP ID based generic scope identifier.....79 - - A.1.3 MME UE SIAP ID based generic scope identifier .....80 - - A.1.4 gNB-CU UE F1AP ID based generic scope identifier .....80 - - A.1.5 gNB-CU-CP UE E1AP ID based generic scope identifier .....81 - - A.1.6 eNB UE X2AP ID based scope identifier .....81 - - A.1.7 M-NG-RAN node UE XnAP ID based scope identifier.....81 - - A.2 QoS (Quality of Service).....82 - - A.2.1 QoS based resource optimization per-UE .....82 - - A.2.2 QoS based resource optimization per-slice .....82 - - A.3 QoE (Quality of Experience).....83 - - A.3.1 QoE based resource optimization per-UE .....83 - - A.3.2 QoE based resource optimization per-slice .....83 - - A.4 TSP (Traffic Steering Preferences) .....83 - - A.4.1 Traffic steering per-UE .....83 - - A.4.2 Traffic steering per-slice .....84 - - A.5 QoS optimization with resource directive .....84 - - A.6 QoE optimization with resource directive.....85 - - A.7 Status object for notification .....85 - - A.8 UE level.....85 - - A.8.1 UE level per-QoS .....85 - - A.8.2 UE level per-slice .....86 - - A.9 RAN Slice SLA assurance .....86 - - A.9.1 Support of maximum slice throughput SLA.....86 - - A.9.2 Support of maximum number of UEs and PDU sessions per slice SLA .....86 - - A.9.3 Support of UE-level performance targets for slice users .....87 - - A.9.4 Support of slice priority.....87 - - A.10 Load balancing .....87 - - A.10.1 Load balancing per-cell with target downlink PRB usage .....87 - - A.10.2 Load balancing per-cell per-slice with target downlink and uplink PRB usage .....88 - -| | | -|----------------------------------------------------------------------------------------------------------|-----------| -| A.11 Energy saving ..... | 88 | -| A.11.1 Comprehensive energy saving..... | 88 | -| A.11.1.1 Energy saving over tracking area ..... | 88 | -| A.11.1.2 Energy saving over cell list..... | 88 | -| A.11.2 Energy saving with exclusion cell list ..... | 89 | -| A.11.2.1 Energy saving over cells that are to remain operational but can have some coverage impact ..... | 89 | -| A.11.2.2 Energy saving over cells that are to remain operational and maintain full coverage ..... | 89 | -| Annex B (Informative): EI examples ..... | 91 | -| B.1 Generic examples ..... | 91 | -| B.1.1 EI job status ..... | 91 | -| B.2 UE geo-location and velocity ..... | 91 | -| B.2.1 Statement for EI job constraints ..... | 91 | -| B.2.2 Statement for EI job definition ..... | 91 | -| B.2.3 Statement for EI job result..... | 91 | -| Annex C (Informative): JSON schema identification and versioning ..... | 93 | -| C.1 General ..... | 93 | -| C.2 Embedding a subschema ..... | 93 | -| C.3 Versioning of policy type schemas and common data types schema..... | 94 | -| C.3.1 General ..... | 94 | -| C.3.2 Versioning of policy types ..... | 94 | -| Annex (informative): Change History ..... | 95 | - -# --- Foreword - -This Technical Specification (TS) has been produced by O-RAN Alliance Working Group 2. It is part of a TS-family covering the A1 interface as identified below: - -- "A1 interface: General Aspects and Principles"; -- "A1 interface: Use Cases and Requirements"; -- "A1 interface: Transport Protocol"; -- "A1 interface: Application Protocol"; -- "A1 interface: Type Definitions"; and -- "A1 interface: Test Specification". - -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 data model and the data types that are used in the body of the procedures in the A1 interface. - -# --- 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.WG2.TS.Use-Case-Requirements: "Non-RT RIC and A1/R1 interface: Use Cases and Requirements". -- [2] O-RAN.WG2.TS.A1GAP: "A1 interface: General Aspects and Principles" ("A1GAP"). -- [3] O-RAN.WG2.TS.A1AP: "A1 interface: Application Protocol" ("A1AP"). -- [4] 3GPP TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3". -- [5] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". -- [6] IETF RFC8259: "The JavaScript Object Notation (JSON) Data Interchange Format". -- [7] json-schema Draft 2020-12 ("JSON Schema"). - -NOTE: Available at: - -- [8] Void -- [9] 3GPP TS 38.473: "NG-RAN; F1 application protocol (FIAP)". -- [10] 3GPP TS 23.003: "Numbering, addressing and identification". -- [11] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2". -- [12] Recommendation ITU-T P.1203.3: "Parametric bitstream-based quality assessment of progressive download and adaptive audiovisual streaming services over reliable transport - Quality integration module". -- [13] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements". -- [14] Void -- [15] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description". -- [16] 3GPP TS 23.203: "Policy and charging control architecture". -- [17] GSMA NG.116 (23 November 2020): "Generic Network Slice Template Version 4.0". -- [18] Void. - -- [19] Semantic Versioning Specification 2.0.0 ("SemVer"). -- NOTE: Available at: -- [20] 3GPP TS 29.572: "5G System; Location Management Services; Stage 3". -- [21] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". -- [22] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)". -- [23] 3GPP TS 32.425: "Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN)". -- [24] 3GPP TS 37.483: "E1 Application Protocol (E1AP)". -- [25] 3GPP TS 38.401: "NG-RAN; Architecture description" -- [26] 3GPP TS 36.423: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP)". -- [27] 3GPP TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)". -- [28] O-RAN.WG1.TS.OAD: "O-RAN Architecture Description". - -## 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. - -Not applicable. - -# --- 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the terms given in A1GAP [2], clause 3.1, A1AP [3], clause 3.1, and the following apply: - -**ScopeIdentifier:** structured data type representing the scope identifier - -NOTE: see A1AP [3]. - -**Statement:** structured data type representing a policy statement that is policy type specific. - -NOTE: see A1AP [3]. - -## 3.2 Symbols - -Void. - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given in A1GAP [2], clause 3.3, A1AP [3], clause 3.3, and the following apply: - -| | | -|-----------|-----------------------------------------| -| AMF | Access and Mobility Management Function | -| E1AP | E1 Application Protocol | -| F1AP | F1 Application Protocol | -| gNB-CU-CP | gNB Central Unit Control Plane | -| GUAMI | Globally Unique AMF Identifier | -| GUMMEI | Globally Unique MME Identifier | -| MME | Mobility Management Entity | -| MOS | Mean Opinion Score | -| NGAP | Next Generation Application Protocol | -| PEE | Power, Energy and Environment | -| SDU | Service Data Unit | -| TaI | Tracking Area Identity | -| TSP | Traffic Steering Preference | - -# 4 A1 Application data model - -## 4.1 Introduction - -The present document together with A1AP [3] contains a REST method realization of the A1 interface architecture and the A1 procedures identified in A1GAP [2]. - -A1AP [3] contains the service description, service operations, resource indicators and the API definition (including the OpenAPI document) for the A1 services. The present document contains the data model and the definitions of the objects transported in the procedures defined for the A1 services. - -The data types defined in the present document have a lifecycle that is independent from the A1 services defined in A1AP [3]. The A1 data models are based on the documentation guidelines for data models in API definitions specified in 3GPP TS 29.501 [4], clause 5.2.4 and data types specified in 3GPP TS 29.571 [5]. It is based on structured data types and objects as specified in IETF RFC 8259 [6] and JSON Schema [7]. - -## 4.2 Compatibility of A1 type definitions - -The version number of the present document indicates that there may be implications for the compatibility between implementations of policy types and/or EI types defined in different versions of the present document. - -The first two-digit value of the present document is incremented when - -- at least one policy type and/or one EI type has been added or removed; and/or -- at least one policy type and/or one EI type has been updated in a non-backward compatible way. - -The second two-digit value of the present document is incremented when at least one policy type and/or one EI type has been updated in a backward compatible way. - -Policy type compatibility is described in clause 7.1.1 and EI type compatibility is described in clause 9.1.1. - -The compatibility of A1 implementations in Non/Near-RT RICs depends on the policy types and/or EI types that are implemented. The present document handles the compatibility for data types used by the A1 services while A1AP [3] handles the A1 service compatibility aspects. - -# 5 Generic aspects and common data types - -## 5.1 Encoding of attributes in A1 data types - -The encoding of 3GPP attributes into JSON is based on their original definitions, and their value ranges, rather than on encodings used in other protocols or solutions sets. The definitions are referred to in the data type definitions (see clauses 6.2 and 6.3) and the corresponding encodings are seen in the type definitions (see clauses 7.1.2.1 and 7.2). - -## 5.2 Current type definitions - -The present document defines the policy types, EI types and common data types listed in table 5.2-1. - -**Table 5.2-1: Type definitions in the present document** - -| Type | Type name | Type version | Definition | -|------------------------------------------|---------------------------|--------------|--------------------| -| Common data types | common | 3.0.1 | See clause 7.1.2.1 | -| Policy types | | | | -| QoS target | QoSTarget | 6.0.1 | See clause 7.2.1 | -| QoE target | QoETarget | 6.0.1 | See clause 7.2.2 | -| Traffic steering preferences | TrafficSteeringPreference | 6.0.1 | See clause 7.2.3 | -| QoS optimization with resource directive | QoSandTSP | 6.0.1 | See clause 7.2.4 | -| QoE optimization with resource directive | QoEandTSP | 6.0.1 | See clause 7.2.5 | -| UE level target | UELevelTarget | 5.0.1 | See clause 7.2.6 | -| Slice SLA target | SliceSLATarget | 4.0.2 | See clause 7.2.7 | -| Load balancing | LoadBalancing | 3.0.1 | See clause 7.2.8 | -| Energy saving | EnergySaving | 3.0.2 | See clause 7.2.9 | -| EI types | | | | -| UE location and velocity information | UEGeoandVel | 5.0.1 | See clause 9.2.1 | - -# 6 A1-P data model - -## 6.1 Introduction - -This clause specifies the application data model and data types supported by the A1-P API specified in A1AP [3], clause 6.2. The data model is based on policy statements that include attributes and are combined with a scope identifier into policy objects. - -Simple data types and enumerations can be referenced from structured data type and policy types. Clause 6.3 defines attributes to be used for scope information and attributes that are not defined as part of the statements (structured data types as defined in coming clauses). - -For policy objectives, policy statements for the following characteristics are defined: - -- QoS targets; - -- QoE targets; -- UE level targets; -- Slice SLA targets; -- Load balancing targets; and -- Energy saving targets. - -For policy resources, policy statements for the following characteristics are defined: - -- Traffic steering optimization; -- Slice SLA assurance; -- Load balancing; and -- Energy saving. - -Clause 6.4 contains the formal representation definitions of the policy representation object types defined in the A1-P service description in A1AP [3], clause 5.2. - -## 6.2 Simple data types and enumerations - -### 6.2.1 Simple data types - -The simple data types are defined in table 6.2.1-1. - -**Table 6.2.1-1: Definition of simple data types for scope and statements** - -| Type Name | Type Definition | Description | Applicability | -|-------------------|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| RanUeId | string | UE identifier, based on RAN UE Id (see 3GPP TS 38.401 [25], clause 6.2.5, and 3GPP TS 38.473 [9], clause 9.2.2.1).
Encoded as 16 hexadecimal characters. | 5G RAN | -| AmfUeNgapId | integer | AMF UE NGAP ID (see 3GPP TS 38.413 [21], clause 9.3.3.1).
Integer with value range 0 to $2^{40} - 1$ . | 4G RAN/5G RAN | -| AmfRegionId | string | AMF Region ID (see 3GPP TS 38.413 [21], clause 9.3.3.3).
Encoded as two hexadecimal characters. | 4G RAN/5G RAN | -| AmfSetId | string | AMF Set ID uniquely identifies an AMF Set within the AMF Region (see 3GPP TS 38.413 [21], clause 9.3.3.12).
Encoded as three hexadecimal characters where the first character is limited to values 0 to 3. | 4G RAN/5G RAN | -| AmfPointer | string | AMF Pointer identifies one or more AMF(s) within the AMF Set (see 3GPP TS 38.413 [21], clause 9.3.3.19).
Encoded as two hexadecimal characters where the first character is limited to values 0 to 3. | 4G RAN/5G RAN | -| MmeUeS1apId | integer | MME UE S1AP ID (see 3GPP TS 36.413 [22], clause 9.2.3.3).
Integer with value range 0 to $2^{32} - 1$ . | 4G RAN | -| MmeGroupId | string | MME Group ID (see 3GPP TS 36.413 [22], clause 9.2.3.9).
Encoded as four hexadecimal characters. | 4G RAN | -| MmeCode | string | MMEC (see 3GPP TS 36.413 [22], clause 9.2.3.12).
Encoded as two hexadecimal characters. | 4G RAN | -| GnbCuUeF1apId | integer | gNB-CU UE F1AP ID (see 3GPP TS 38.401 [25], clause 6.2.1 and 3GPP TS 38.473 [9], clause 9.3.1.4).
Integer with value range 0 to $2^{32} - 1$ . | 5G RAN | -| GnbCuCpUeE1apId | integer | gNB-CU-CP UE E1AP ID (see 3GPP TS 38.401 [25], clause 6.2.1, and 3GPP TS 37.483 [24], clause 9.3.1.4).
Integer with value range 0 to $2^{32} - 1$ . | 5G RAN | -| EnbUeX2apId | integer | eNB UE X2AP ID (see 3GPP TS 36.423 [26], clause 9.2.24).
Integer with value range 0 to 4095. | 4G RAN/5G RAN | -| NgRanNodeUeXnapId | integer | NG-RAN node UE XnAP ID (see 3GPP TS 38.423 [27], clause 9.2.3.16).
Integer with value range 0 to $2^{32} - 1$ . | 5G RAN | - -The simple data type for JSON schemas is defined in table 6.2.1-2. - -**Table 6.2.1-2: Definition of JsonSchema** - -| Type Name | Type Definition | Description | Applicability | -|------------|---------------------------------------------------------------------------------------------------------|-----------------------------------------------------|---------------| -| JsonSchema | https://json-schema.org/draft/2020-12/schema | A JSON schema meta-schema following JSON Schema [7] | | - -### 6.2.2 Enumerations - -#### 6.2.2.1 PreferenceType - -The enumeration PreferenceType represents the preference of a specific network resource (e.g. cell usage). It shall comply with the provisions defined in table 6.2.2.1-1. - -**Table 6.2.2.1-1: Definition of PreferenceType** - -| Enumeration value | Description | Applicability | -|-------------------|------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| -| SHALL | equals to select the resource | select the cell regardless of if connection retainability might be at risk | -| PREFER | equals to favour the selection of the resource | favour the selection of the cell even if it is not with the best radio quality if the connection retainability is not at risk. | -| AVOID | equals to avoid selecting the resource | avoid selecting the cell unless the connection retainability is at risk | -| FORBID | equals to not select the resource | do not select the cell under any conditions | - -#### 6.2.2.2 EnforcementStatusType - -The enumeration EnforcementStatusType represents if a policy is enforced or not. It shall comply with the provisions defined in table 6.2.2.2-1. - -**Table 6.2.2.2-1: Definition of EnforcementStatusType** - -| Enumeration value | Description | Applicability | -|-------------------|----------------------------------------|---------------| -| ENFORCED | equals that the policy is enforced | | -| NOT_ENFORCED | equals that the policy is not enforced | | - -#### 6.2.2.3 EnforcementReasonType - -The enumeration EnforcementReasonType represents the reason why notification is sent (e.g. why enforcement status has changed). It also represents the latest reason for change of enforcement status to NON\_ENFORCED in case policy status is queried. It shall comply with the provisions defined in table 6.2.2.3-1. - -**Table 6.2.2.3-1: Definition of EnforcementReasonType** - -| Enumeration value | Description | Applicability | -|--------------------------|-----------------------------------------------------------------|---------------------------------------------------------------------------------------------------| -| SCOPE_NOT_APPLICABLE | One or more attributes of the ScopeIdentifier cannot be applied | The scope provided can no longer be applied for enforcing the policy | -| STATEMENT_NOT_APPLICABLE | Policy statement(s) cannot be applied | The statement(s) can no longer be applied due to other changes | -| OTHER_REASON | Any other reason | Policy can no longer be enforced for other reasons than scope or statement becoming inapplicable. | - -#### 6.2.2.4 AvoidanceType - -The enumeration AvoidanceType represents the avoidance of a specific network resource (e.g. cell usage). It shall comply with the provisions defined in table 6.2.2.4-1. - -**Table 6.2.2.4-1: Definition of AvoidanceType** - -| Enumeration value | Description | Applicability | -|-------------------|-------------------------------------------------|-----------------------------------------------------------------| -| AVOID | equals to avoid selecting the network resource | avoid selecting the cell as network resource | -| FORBID | equals to forbid selecting the network resource | do not select the cell as network resource under any conditions | - -## 6.3 Structured data types - -### 6.3.1 ScopeIdentifier - -#### 6.3.1.1 Introduction - -A1 policies are defined in A1GAP [2], clause 5.1.4.0 as containing a scope identifier and one or more policy statements where policy statements contain policy objectives and/or policy resources. This clause defines the structured data type ScopeIdentifier. - -The ScopeIdentifier contains the attributes defined in table 6.3.1.1-1: - -**Table 6.3.1.1-1: Definition of data type ScopeIdentifier** - -| Attribute Name | Data Type | P | Cardinality | Description | Applicability | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---|-------------|---------------------------------------------------------------------------------------------|---------------| -| ueId | UEId | C | 0..1 | identifies the UE that policy statement(s) are applied to, see clause 6.3.1.7 | | -| groupId | GroupId | C | 0..1 | identifies multiple UEs that policy statement(s) are applied to, see clause 6.3.1.2 | | -| sliceId | SliceId | C | 0..1 | identifies the network slice that policy statement(s) are applied to, see clause 6.3.1.3 | | -| qosId | QoSId | C | 0..1 | identifies the QoS flow that policy statement(s) are applied to, see clause 6.3.1.4 | | -| cellId | CellId | C | 0..1 | identifies the cell that the policy statement(s) are applied to, see clause 6.3.1.5 | | -| cellIdList | CellIdList | C | 0..1 | identifies the list of cells that the policy statement(s) are applied to, see Table 6.3.2-1 | | -| talList | TalList | C | 0..1 | identifies the list of Tals that the policy statement(s) are applied to, see Table 6.3.2-3 | | -| NOTE 1: Presence condition "C" means that least one attribute shall be included when the scope is defined. The allowed combinations of attributes depend on the policy statement that is combined with the ScopeIdentifier and is policy type specific, see clause 7.2. | | | | | | -| NOTE 2: Encoding of 3GPP attributes into number and string is described in clause 5.1 and applied to the JSON encodings in clause 7.1.2.1. | | | | | | -| NOTE 3: cellId and cellIdList shall not be present at the same time in a ScopeIdentifier for defining A1 policies. | | | | | | -| NOTE 4: CellIdList shall include only those cells that are associated with unique Near-RT RIC. | | | | | | -| NOTE 5: TalList shall include only those tracking area codes that cover cells associated with a unique Near-RT RIC. | | | | | | - -#### 6.3.1.2 GroupId - -GroupId is defined based on different RF selection priority parameters for 4G and 5G networks. GroupId does not explicitly define a UE group, and does not enable any group management operations, but is a property that several UE can share and thereby enables implicit identification of a dynamic set of UEs for which the same policy can be applied. - -The GroupId contains the attributes defined in table 6.3.1.2-1: - -**Table 6.3.1.2-1: Definition of type GroupId** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------|---------------| -| spId | integer | C | 0..1 | identifier of a subscriber profile that can be shared by several UEs (see 3GPP TS 36.300) [15].
Value range is between 1 and 256. | 4G RAN | -| rfspIndex | integer | C | 0..1 | identifier of a RF selection priority that can be shared by several UEs (see 3GPP TS 23.501) [11].
Value range is between 1 and 256. | 5G RAN | - -NOTE: Presence condition "C" means that one and only attribute shall be included when this data type is used. - -#### 6.3.1.3 SliceId - -SliceId is based on the definition of S-NSSAI (see 3GPP TS 23.003 [10]) and includes a PLMN identifier. - -The SliceId contains the attributes defined in table 6.3.1.3-1: - -**Table 6.3.1.3-1: Definition of type SliceId** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------|-------------------| -| sst | integer | M | 1 | Slice/Service type part of S-NSSAI (see 3GPP TS 23.003 [10]).
Integer with value range 0 to 255. | 5G RAN | -| sd | string | O | 0..1 | Slice Differentiator of S-NSSAI
Encoded as 6 hexadecimal characters | 5G RAN | -| plmnId | PlmnId | M | 1 | PLMN Identifier (see 3GPP TS 23.003 [10]), see table 6.3.1.6-1 | 4G RAN and 5G RAN | - -#### 6.3.1.4 QosId - -QosId is defined based on different QoS identifiers for 4G and 5G networks. - -The QosId contains the attributes defined in table 6.3.1.4-1: - -**Table 6.3.1.4-1: Definition of type QosId** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-----------|---|-------------|--------------------------------------------------------------------------------------|---------------| -| qcl | integer | C | 0..1 | QoS Class Identifier (see 3GPP TS 23.203 [16]).
Value range is between 1 and 256. | 4G RAN | -| 5ql | integer | C | 0..1 | 5G QoS Identifier (see 3GPP TS 23.501 [11]).
Value range is between 1 and 256. | 5G RAN | - -NOTE: Presence condition "C" means that one and only attribute shall be included when this data type is used. - -#### 6.3.1.5 CellId - -CellId is based on the definition of the global cell identifiers ECGI and NCGI (see 3GPP TS 23.003 [10]) for 4G and 5G RANs. - -The CellId contains the attributes defined in table 6.3.1.5-1 and 6.3.1.5-2: - -**Table 6.3.1.5-1: Definition of type Cld** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|---------------------------------------------------------------------------------------------------------------|-----------|---|-------------|----------------------------------------------------------------------------------|---------------| -| ecl | integer | C | 0..1 | E-UTRAN Cell identifier (see 3GPP TS 23.003 [10])
28 bits encoded as integer. | 4G RAN | -| ncl | integer | C | 0..1 | NR Cell identifier (see 3GPP TS 23.003 [10])
36 bits encoded as integer. | 5G RAN | -| NOTE: Presence condition "C" means that one and only attribute shall be included when this data type is used. | | | | | | - -**Table 6.3.1.5-2: Definition of type CellId** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-----------|---|-------------|----------------------------------------------------------------|---------------| -| plmnId | PlmnId | M | 1 | PLMN Identifier (see 3GPP TS 23.003 [10]), see table 6.3.1.6-1 | | -| cid | CId | M | 1 | Cell Identifier, see table 6.3.1.5-1 | | - -#### 6.3.1.6 PlmnId - -This clause contains the definition of the structured data type PlmnId. PlmnId is based on the definition in 3GPP TS 23.003 [10]. - -The PlmnId contains the attributes defined in table 6.3.1.6-1: - -**Table 6.3.1.6-1: Definition of type PlmnId** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-----------|---|-------------|--------------------------------------------------------------------------|---------------| -| mcc | string | M | 1 | Mobile Country Code (see 3GPP TS 23.003 [10])
Contains 3 digits. | | -| mnc | string | M | 1 | Mobile Network Code (see 3GPP TS 23.003 [10])
Contains 2 or 3 digits. | | - -#### 6.3.1.7 UId - -UId is defined based on the UE associated identifiers listed in O-RAN Architecture Description [28], table 5.5-1 with the exception that C-RNTI is not supported in the scope identifier of A1 policies. - -**Table 6.3.1.7-1: Definition of type GuRanUId** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-------------|---|-------------|-----------------------------------|---------------| -| globalGnblD | GlobalGnblD | M | 1 | Global gNB ID, see clause 6.3.1.8 | 5G RAN | -| ranUId | RanUId | M | 1 | RAN UE ID, see clause 6.2.1 | 5G RAN | - -**Table 6.3.1.7-2: Definition of type GuAmfUeNgapId** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-------------|---|-------------|----------------------------------------------------|---------------| -| guAmf | GuAmf | M | 1 | Globally unique AMF Identifier, see clause 6.3.1.9 | 4G RAN/5G RAN | -| amfUeNgapId | AmfUeNgapId | M | 1 | AMF UE NGAP ID, see clause 6.2.1 | 4G RAN/5G RAN | - -**Table 6.3.1.7-3: Definition of type GuMmeUeS1apld** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-------------|---|-------------|-----------------------------------------------------|---------------| -| guMmeI | GuMmeI | M | 1 | Globally unique MME Identifier, see clause 6.3.1.10 | 4G RAN | -| mmeUeS1apld | MmeUeS1apld | M | 1 | MME UE S1AP ID, see clause 6.2.1 | 4G RAN | - -**Table 6.3.1.7-4: Definition of type Ueld** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-----------------------|-----------------------|---|-------------|-------------------------------------------------------------|---------------| -| guRanUeld | GuRanUeld | C | 0..1 | Globally unique RAN UE ID, see table 6.3.1.7-1 | 5G RAN | -| guAmfUeNgapld | GuAmfUeNgapld | C | 0..1 | Globally unique AMF UE NGAP ID, see table 6.3.1.7-2 | 4G RAN/5G RAN | -| guMmeUeS1apld | GuMmeUeS1apld | C | 0..1 | Globally unique MME UE S1AP ID, see table 6.3.1.7-3 | 4G RAN | -| guGnbCuUeF1apld | GuGnbCuUeF1apld | C | 0..1 | Globally unique gNB-CU UE F1AP ID, see table 6.3.1.7-5 | 5G RAN | -| guGnbCuCpUeE1apld | GuGnbCuCpUeE1apld | C | 0..1 | Globally unique gNB-CU-CP UE E1AP ID, see table 6.3.1.7-6 | 5G RAN | -| guEnbUeX2apld | GuEnbUeX2apld | C | 0..1 | Globally unique eNB UE X2AP ID, see table 6.3.1.7-7 | 4G RAN/5G RAN | -| guNgRanNodeUeXnapUeld | GuNgRanNodeUeXnapUeld | C | 0..1 | Globally unique NG-RAN node UE XnAP ID, see table 6.3.1.7-8 | 5G RAN | - -NOTE: Presence condition "C" means that one and only attribute shall be included when this data type is used. - -**Table 6.3.1.7-5: Definition of type GuGnbCuUeF1apld** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|---------------|---|-------------|-------------------------------------|---------------| -| globalGnbld | GlobalGnbld | M | 1 | Global gNB ID, see clause 6.3.1.8 | 5G RAN | -| gnbCuUeF1apld | GnbCuUeF1apld | M | 1 | gNB-CU UE F1AP ID, see clause 6.2.1 | 5G RAN | - -**Table 6.3.1.7-6: Definition of type GuGnbCuCpUeE1apld** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-----------------|-----------------|---|-------------|----------------------------------------|---------------| -| globalGnbld | GlobalGnbld | M | 1 | Global gNB ID, see clause 6.3.1.8 | 5G RAN | -| gnbCuCpUeE1apld | GnbCuCpUeE1apld | M | 1 | gNB-CU-CP UE E1AP ID, see clause 6.2.1 | 5G RAN | - -**Table 6.3.1.7-7: Definition of type GuEnbUeX2apld** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-------------|---|-------------|------------------------------------|---------------| -| globalEnbld | GlobalEnbld | M | 1 | Global eNB ID, see clause 6.3.1.11 | 4G RAN/5G RAN | -| enbUeX2apld | EnbUeX2apld | M | 1 | eNB UE X2AP ID, see clause 6.2.1 | 4G RAN/5G RAN | - -**Table 6.3.1.7-8: Definition of type GuNgRanNodeUeXnapUeld** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|---------------------------|---------------------------|---|-------------|--------------------------------------------|---------------| -| globalNgRanNodeUeXnapUeld | GlobalNgRanNodeUeXnapUeld | M | 1 | Global NG-RAN Node ID, see clause 6.3.1.12 | 5G RAN | -| ngRanNodeUeXnapUeld | NgRanNodeUeXnapUeld | M | 1 | NG-RAN node UE XnAP ID, see clause 6.2.1 | 5G RAN | - -#### 6.3.1.8 GlobalGnblId - -This clause contains the definition of the structured data type GlobalGnblId. This is based on Global gNB ID defined in 3GPP TS 38.413 [21], clause 9.3.1.6, in 3GPP TS 38.473 [9], clause 9.3.1.305, and in 3GPP TS 38.423 [27], clause 9.2.2.1. - -The GlobalGnblId contains the attributes defined in table 6.3.1.8-1 and 6.3.1.8-2: - -**Table 6.3.1.8-1: Definition of type GnblId** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| gnblIdLength | integer | M | 1 | This indicates the number of bits for encoding the gNB ID (see 3GPP TS 38.413 [21], clause 9.3.1.6).
Integer with value range 22 to 32. | 5G RAN | -| gnblIdValue | integer | M | 1 | gNB ID (see 3GPP TS 38.413 [21], clause 9.3.1.6).
Encoded as integer with value range 0 to $2^{32} - 1$ . | 5G RAN | - -**Table 6.3.1.8-2: Definition of type GlobalGnblId** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-----------|---|-------------|-------------------------------------|---------------| -| plmnId | PlmnId | M | 1 | PLMN Identifier, see clause 6.3.1.6 | 5G RAN | -| gnblId | GnblId | M | 1 | gNB Identifier, see table 6.3.1.8-1 | 5G RAN | - -#### 6.3.1.9 GuAmI - -This clause contains the definition of the structured data type GuAmI. This is based on GUAMI defined in 3GPP TS 38.413 [21], clause 9.3.3.3. - -The GuAmI contains the attributes defined in table 6.3.1.9-1: - -**Table 6.3.1.9-1: Definition of type GuAmI** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-------------|---|-------------|-----------------------------------------|---------------| -| plmnId | PlmnId | M | 1 | PLMN Identifier, see clause 6.3.1.6 | 4G RAN/5G RAN | -| amfRegionId | AmfRegionId | M | 1 | AMF Region Identifier, see clause 6.2.1 | 4G RAN/5G RAN | -| amfSetId | AmfSetId | M | 1 | AMF Set Identifier, see clause 6.2.1 | 4G RAN/5G RAN | -| amfPointer | AmfPointer | M | 1 | AMF Pointer, see clause 6.2.1 | 4G RAN/5G RAN | - -#### 6.3.1.10 GuMmeI - -This clause contains the definition of the structured data type GuMmeI. This is based on GUMMEI defined in 3GPP TS 36.413 [22], clause 9.2.3.9. - -The GuMmeI contains the attributes defined in table 6.3.1.10-1: - -**Table 6.3.1.10-1: Definition of type GuMmeI** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|------------|---|-------------|----------------------------------------|---------------| -| plmnId | PlmnId | M | 1 | PLMN Identifier, see clause 6.3.1.6 | 4G RAN | -| mmeGroupId | MmeGroupId | M | 1 | MME Group Identifier, see clause 6.2.1 | 4G RAN | -| mmeCode | MmeCode | M | 1 | MME Code, see clause 6.2.1 | 4G RAN | - -#### 6.3.1.11 GlobalEnbId - -This clause contains the definition of the structured data type GlobalEnbId. This is based on Global eNB ID defined in 3GPP TS 36.413 [22], clause 9.2.1.37 and in 3GPP 36.423 [26], clause 9.2.22. - -The GlobalEnbId contains the attributes defined in table 6.3.1.11-1 and 6.3.1.11-2: - -**Table 6.3.1.11-1: Definition of type EnbId** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|---------------------------------------------------------------------------------------------------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| macroEnbId | string | C | 0..1 | Macro eNB ID (see 3GPP TS 36.423 [26], clause 9.2.22). Encoded as five hexadecimal characters. | 4G RAN/5G RAN | -| homeEnbId | string | C | 0..1 | Home eNB ID (see 3GPP TS 36.423 [26], clause 9.2.22). Encoded as seven hexadecimal characters. | 4G RAN/5G RAN | -| shortMacroEnbId | string | C | 0..1 | Short Macro eNB ID (see 3GPP TS 36.423 [26], clause 9.2.22). Encoded as five hexadecimal characters where the first character is limited to values 0 to 3. | 4G RAN/5G RAN | -| longMacroEnbId | string | C | 0..1 | Long Macro eNB ID (see 3GPP TS 36.423 [26], clause 9.2.22). Encoded as six hexadecimal characters where the first character is limited to values 0 to 1. | 4G RAN/5G RAN | -| NOTE: Presence condition "C" means that one and only attribute shall be included when this data type is used. | | | | | | - -**Table 6.3.1.11-2: Definition of type GlobalEnbId** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-----------|---|-------------|--------------------------------------|---------------| -| plmnId | PlmnId | M | 1 | PLMN Identifier, see clause 6.3.1.6 | 4G RAN/5G RAN | -| enbId | EnbId | M | 1 | eNB Identifier, see table 6.3.1.11-1 | 4G RAN/5G RAN | - -#### 6.3.1.12 GlobalNgRanNodeId - -This clause contains the definition of the structured data type GlobalNgRanNodeId. This is based on Global NG-RAN Node ID defined in 3GPP TS 38.423 [27], clause 9.2.2.3. - -The GlobalNgRanNodeId contains the attributes defined in tables 6.3.1.12-1, 6.3.1.12-2, and 6.3.1.12-3. - -**Table 6.3.1.12-1: Definition of type NgEnbld** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-------------------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------|---------------| -| macroNgEnbld | integer | C | 1 | Macro ng-eNB ID (see 3GPP TS 38.423 [27], clause 9.2.2.2).
Encoded as integer with value range 0 to $2^{20}$ -1. | 5G RAN | -| shortMacroNgEnbld | integer | C | 1 | Short Macro ng-eNB ID (see 3GPP TS 38.423 [27], clause 9.2.2.2).
Encoded as integer with value range 0 to $2^{18}$ -1. | 5G RAN | -| longMacroNgEnbld | integer | C | 1 | Long Macro ng-eNB ID (see 3GPP TS 38.423 [27], clause 9.2.2.2).
Encoded as integer with value range 0 to $2^{21}$ -1. | 5G RAN | - -NOTE: Presence condition "C" means that one and only attribute shall be included when this data type is used. - -**Table 6.3.1.12-2: Definition of type GlobalNgEnbld** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-----------|---|-------------|-----------------------------------------|---------------| -| plmnId | PlmnId | M | 1 | PLMN Identifier, see clause 6.3.1.6 | 5G RAN | -| ngEnbld | NgEnbld | M | 1 | ng-eNB Identifier, see table 6.3.1.12-1 | 5G RAN | - -**Table 6.3.1.12-3: Definition of type GlobalNgRanNodeId** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|---------------|---|-------------|----------------------------------------|---------------| -| globalGnbld | GlobalGnbld | C | 0..1 | Global gNB ID, see table 6.3.1.8-2 | 5G RAN | -| globalNgEnbld | GlobalNgEnbld | C | 0..1 | Global ng-eNB ID, see table 6.3.1.12-2 | 5G RAN | - -NOTE: Presence condition "C" means that one and only attribute shall be included when this data type is used. - -### 6.3.2 Structured data types for statements - -This clause contains definitions of structured data types that are used in statements for policy objectives and/or statements for policy resources. - -The CellIdList contains the attributes defined in table 6.3.2-1: - -**Table 6.3.2-1: Definition of type CellIdList** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|---------------|---|-------------|-----------------------------------|---------------| -| cellIdList | array(CellId) | M | 1..N | list of CellIds, see clause 6.3.1 | | - -The TalList contains the attributes defined in table 6.3.2-2 and 6.3.2-3: - -**Table 6.3.2-2: Definition of type Tal** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-----------|---|-------------|---------------------------------------------------------------------------------------|-------------------| -| plmnId | PlmnId | M | 1 | PLMN Identifier (see 3GPP TS 23.003 [10]), see table 6.3.1.6-1 | 4G RAN and 5G RAN | -| tac | string | M | 1 | Tracking Area Code (see 3GPP TS 23.003 [10]).
Encoded as 6 hexadecimal characters. | 5G RAN | - -**Table 6.3.2-3: Definition of type TalList** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|------------|---|-------------|---------------------------------|-------------------| -| talList | array(Tal) | M | 1..N | list of Tals, see table 6.3.2-2 | 4G RAN and 5G RAN | - -### 6.3.3 Statements for policy objectives - -#### 6.3.3.1 Introduction - -A1 policies are defined in A1GAP [2], clause 5.1.4.0 as containing a scope identifier and one or more policy statements where policy statements contain policy objectives and/or policy resources. This clause defines the structured data types and attributes to be used for policy objectives. - -Table 6.3.3.1-1 specifies the data types defined for policy objectives in the A1-P interface protocol. The possible combinations of these are defined in clause 7. - -**Table 6.3.3.1-1: Statements for policy objectives** - -| Data type | Clause defined | Description | Applicability | -|--------------------|----------------|-----------------------------------------|---------------| -| QosObjectives | 6.3.3.2 | Attributes related to QoS targets | | -| QoeObjectives | 6.3.3.3 | Attributes related to QoE targets | | -| UeLevelObjectives | 6.3.3.4 | Attributes related to UE level targets | | -| SliceSlaObjectives | 6.3.3.5 | Attributes related to slice SLA targets | | -| LbObjectives | 6.3.3.6 | Attributes related to load balancing | | -| EsObjectives | 6.3.3.7 | Attributes related to energy saving | | - -#### 6.3.3.2 QoS target - -The QosObjectives statement contains the attributes defined in table 6.3.3.2-1: - -**Table 6.3.3.2-1: Definition of statement type QosObjectives** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|------------------------------------------------------------------------------------------------------------|-----------|---|-------------|---------------------------------------------------|---------------| -| gfbr | number | C | 0..1 | Guaranteed Flow Bit Rate, see 3GPP TS 23.501 [11] | 5G RAN | -| mfbr | number | C | 0..1 | Maximum Flow Bit Rate, see 3GPP TS 23.501 [11] | 5G RAN | -| priorityLevel | number | C | 0..1 | Priority Level, see 3GPP TS 23.501 [11] | 5G RAN | -| pdb | number | C | 0..1 | Packet Delay Budget, see 3GPP TS 23.501 [11] | 5G RAN | -| NOTE: Presence condition "C" means that least one attribute shall be included when this statement is used. | | | | | | - -#### 6.3.3.3 QoE target - -The QoeObjectives statement contains the attributes defined in table 6.3.3.3-1: - -**Table 6.3.3.3-1: Definition of statement type QoeObjectives** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| qoeScore | number | C | 0..1 | mean opinion score (MOS) value between 1 and 5, it can be either e.g. video MOS as specified in ITU-T P.1203.3 [12] or a customized MOS | | -| initialBuffering | number | C | 0..1 | refers to the time in seconds between the initiation of video playback by the user and the actual start of the playback as specified in ITU-T P.1203.3 [12] | | -| reBuffFreq | number | C | 0..1 | it can be calculated by taking the number of stalling events (excluding the initial buffering) and dividing by the length of media as specified in ITU-T P.1203.3 [12] or by a customized time window | | -| stallRatio | number | C | 0..1 | ratio of the sum of duration of the stalling events to the total media length as specified in ITU-T P.1203.3 [12] or by a customized time window. | | -| NOTE 1: Presence condition "C" means that least one attribute shall be included when this statement is used.
NOTE 2: In the present document, the QoE target is applicable to video streaming services. | | | | | | - -Application server will measure the QoE related attributes (e.g. MOS, initial buffering, reBuffFreq, stallRatio) for a specific service based on application info. However, it is too late for the network to optimize the radio resource when the application server finds the QoE is too bad. The Near-RT RIC could predict the QoE related attributes based on the network side info (e.g. QoS parameters, radio conditions, Packet measure report etc.) e.g. by performing model inference for a specific ML model received from the Non-RT RIC. The predicted value is approximately the QoE related attribute which will be measured at application server later, but it is estimated at the Near-RT RIC in real time. So, the Near-RT RIC could decide to optimize the radio resource based on the predicted value and the QoE target contained in the A1 policy. - -#### 6.3.3.4 UE level targets - -The UeLevelObjectives statement contains the attributes defined in table 6.3.3.4-1: - -**Table 6.3.3.4-1: Definition of statement type UeLevelObjectives** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-------------------------|-----------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| ulThroughput | number | C | 0..1 | the average UL RAN UE throughput as the UE performance targets or RAN optimization constraints. See 3GPP TS 28.552 [13], clause 5.1.1.3.3. | | -| dlThroughput | number | C | 0..1 | the average DL RAN UE throughput as the UE performance targets or RAN optimization constraints. See 3GPP TS 28.552 [13], clause 5.1.1.3.1. | | -| ulPacketDelay | number | C | 0..1 | Uplink Packet delay with precision of 0.1 millisecond as the UE performance targets or RAN optimization constraints. See 3GPP TS 28.552 [13], clause 5.1.1.1.4. | | -| dlPacketDelay | number | C | 0..1 | Downlink Packet delay with precision of 0.1 millisecond as the UE performance targets or RAN optimization constraints. See 3GPP TS 28.552 [13], clause 5.1.3.3.3. | | -| ulPdcpsduPacketLossRate | number | C | 0..1 | UL reliability as the UE performance targets or RAN optimization constraints. See 3GPP TS 28.552 [13], clause 5.1.3.1.1. | | -| dlRicsduPacketLossRate | number | C | 0..1 | DL reliability as the UE performance targets or RAN optimization constraints. See 3GPP TS 28.552 [13], clause 5.1.1.35. | | -| dlReliability | ReliabilityType | C | 0..1 | DL reliability as the UE performance targets or RAN optimization constraints. | | -| ulReliability | ReliabilityType | C | 0..1 | UL reliability as the UE performance targets or RAN optimization constraints. | | - -NOTE: Presence condition "C" means that least one attribute shall be included when this statement is used. - -The ReliabilityType represents the success probability of transmitting a data packet of X bytes within a certain delay. It shall comply with the provisions defined in table 6.3.3.4-2. - -**Table 6.3.3.4-2: Definition of type ReliabilityType** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|--------------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| packetSize | number | M | 1 | data package size in unit of bytes | | -| userPlaneLatency | number | M | 1 | the time it takes to deliver a data packet from the radio protocol layer 2/3 SDU ingress point to the radio protocol layer 2/3 SDU egress point of the radio interface in unit of ms | | -| successProbability | number | M | 1 | the success probability of transmitting a data packet in packet size within the user plane latency, a number between 0 and 1 | | - -#### 6.3.3.5 Slice SLA target - -The SliceSlaObjectives statement contains the attributes defined in table 6.3.3.5-1: - -**Table 6.3.3.5-1: Definition of statement type SliceSlaObjectives** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-------------------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| maxNumberOfUes | number | C | 0..1 | This attribute describes the partial SLA target for providing maximum number of RRC connected UEs to be served by the network slice concurrently. Scope identifier designates the respective network slice and optionally slice SLA resources can further designate targeted cells. See NG.116 [17], clause 3.4.17 ("Maximum Number of UEs"). | | -| maxNumberOfPdu Sessions | number | C | 0..1 | This attribute describes the partial SLA target for providing maximum number of PDU sessions to be supported by the network slice concurrently. Scope identifier designates the respective network slice and optionally slice SLA resources can further designate targeted cells. See NG.116 [17], clause 3.4.16 ("Maximum number of PDU sessions"). | | -| guaDITHptPerSlice | number | C | 0..1 | This attribute describes the partial SLA target for providing guaranteed data rate as kbps in downlink to be served by the network slice for the aggregate of all GBR QoS flows in downlink belonging to the set of all UEs using the network slice. Scope identifier designates the respective network slice and optionally slice SLA resources can further designate targeted cells. If there are designed targeted cells, the downlink data rate is aggregated over the designated targeted cells within the respective network slice under the control of the near-RT RIC. If no cell is designated, the downlink data rate is aggregated over all the cells within the respective network slice under the control of the near-RT RIC. See NG.116 [17], clause 3.4.5 ("Guaranteed downlink throughput quota"). | | -| maxDITHptPerSlice | number | C | 0..1 | This attribute describes the partial SLA target for providing maximum data rate supported by the network slice for all UEs together in downlink in kbps. Scope identifier designates the respective network slice and optionally slice SLA resources can further designate targeted cells. See NG.116 [17], clause 3.4.5 ("Max downlink throughput"). | | -| maxDITHptPerUe | number | C | 0..1 | This attribute describes the maximum data rate supported by the network slice per UE in downlink in kbps. Scope identifier designates the respective network slice and optionally slice SLA resources can further designate targeted cells. See NG.116 [17], clause 3.4.6 ("Downlink maximum throughput per UE"). This attribute applies to all UEs that are a member of that slice in the designated target cells. | | - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-----------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| guaUIThptPerSlice | number | C | 0..1 | This attribute describes the partial SLA target for providing guaranteed data rate as kbps in uplink to be served by the network slice for the aggregate of all GBR QoS flows in uplink belonging to the set of all UEs using the network slice. Scope identifier designates the respective network slice and optionally slice SLA resources can further designate targeted cells. If there are designed targeted cells, the uplink data rate is aggregated over the designated targeted cells within the respective network slice under the control of the near-RT RIC. If no cell is designated, the uplink data rate is aggregated over all the cells within the respective network slice under the control of the near-RT RIC. See NG.116 [17], clause 3.4.31 ("Guaranteed uplink throughput quota"). | | -| maxUIThptPerSlice | number | C | 0..1 | This attribute describes the partial SLA target for providing maximum data rate supported by the network slice for all UEs together in uplink in kbps. Scope identifier designates the respective network slice and optionally slice SLA resources can further designate targeted cells. See NG.116 [17], clause 3.4.31 ("Max uplink throughput"). | | -| maxUIThptPerUe | number | C | 0..1 | This attribute describes the maximum data rate supported by the network slice per UE in uplink in kbps. Scope identifier designates the respective network slice and optionally slice SLA resources can further designate targeted cells. See NG.116 [17], clause 3.4.32 ("Uplink maximum throughput per UE"). This attribute applies to all UEs that are a member of that slice in the designated target cells. | | -| maxDIPacketDelayPerUe | number | C | 0..1 |

This attribute describes the maximum delay for DL packets in ms as the performance target that is communicated to the Near-RT RIC. This attribute applies to all UEs that are a member of the designated slice in the designated target cells.

This attribute is based on Packet Delay Budget (see GSMA NG.116 [17], clause 3.4.26 ("Slice quality of service parameters: Packet Delay Budget")). The Packet Delay Budget parameter in GSMA NG.116 [17] is for both uplink & downlink while maxDIPacketDelayPerUe is only for downlink. Packet Delay Budget parameter in GSMA NG.116 [17] is defined per 5QI per slice while maxDIPacketDelayPerUe is defined per slice.

| | - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|---------------------------------|------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| maxUIPacketDelayPerUe | number | C | 0..1 |

This attribute describes the maximum delay for UL packets in ms as the performance target that is communicated to the Near-RT RIC. This attribute applies to all UEs that are a member of the designated slice in the designated target cells.

This attribute is based on Packet Delay Budget (see GSMA NG.116 [17], clause 3.4.26 (“Slice quality of service parameters: Packet Delay Budget”)). The Packet Delay Budget parameter in GSMA NG.116 [17] is for both uplink & downlink while maxUIPacketDelayPerUe is only for uplink. Packet Delay Budget parameter in GSMA NG.116 [17] is defined per 5QI per slice while maxUIPacketDelayPerUe is defined per slice.

| | -| maxDIPdcpSduPacketLossRatePerUe | number | C | 0..1 |

This attribute describes the maximum DL PDCP SDU level packet loss rate, a number between 0 and 1, as the performance target that is communicated to the Near-RT RIC. This attribute applies to all UEs that are a member of the designated slice in the designated target cells.

This attribute is based on Maximum Packet Loss Rate (see GSMA NG.116 [17], clause 3.4.26 (“Slice quality of service parameters: Maximum Packet Loss Rate”)). The Maximum Packet Loss Rate parameter in GSMA NG.116 [17] is for both uplink & downlink while maxDIPdcpSduPacketLossRatePerUe is only for downlink.

| | -| maxUIRlcSduPacketLossRatePerUe | number | C | 0..1 |

This attribute describes the maximum UL RLC SDU level packet loss rate, a number between 0 and 1, as the performance target that is communicated to the Near-RT RIC. This attribute applies to all UEs that are a member of the designated slice in the designated target cells.

This attribute is based on Maximum Packet Loss Rate (see GSMA NG.116 [17], clause 3.4.26 (“Slice quality of service parameters: Maximum Packet Loss Rate”)). The Maximum Packet Loss Rate parameter in GSMA NG.116 [17] is for both uplink & downlink while maxUIPdcpSduPacketLossRatePerUe is only for uplink.

| | -| minDReliabilityPerUe | Reliability Type | C | 0..1 |

This attribute describes the minimum DL reliability as the performance target that is communicated to the Near-RT RIC. The definition of minDReliabilityPerUe corresponds to that of dReliability in table 6.3.3.4-1. This attribute applies to all UEs that are a member of the designated slice in the designated target cells.

| | - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-----------------------|------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| minUIReliabilityPerUe | Reliability Type | C | 0..1 | This attribute describes the minimum UL reliability as the performance target that is communicated to the Near-RT RIC. The definition of minUIReliabilityPerUe corresponds to that of uIReliability in table 6.3.3.4-1. This attribute applies to all UEs that are a member of the designated slice in the designated target cells. | | -| maxDJitterPerUe | number | C | 0..1 | This attribute describes the maximum DL jitter in ms, which is the deviation from the desired packet arrival time to the actual packet arrival time, as the performance target that is communicated to the Near-RT RIC. This attribute applies to all UEs that are a member of the designated slice in the designated target cells. | | -| maxUJitterPerUe | number | C | 0..1 | This attribute describes the maximum UL jitter in ms, which is the deviation from the desired packet arrival time to the actual packet arrival time, as the performance target that is communicated to the Near-RT RIC. This attribute applies to all UEs that are a member of the designated slice in the designated target cells. | | -| dlSlicePriority | number | C | 0..1 | This attribute describes the priority of the slice in DL, that is communicated to the Near-RT RIC, for providing prioritization for using RAN resources. According to this attribute, QoS flows under a slice are prioritized. The lower the value, the higher the priority. The value shall be greater than or equal to 1. | | -| ulSlicePriority | number | C | 0..1 | This attribute describes the priority of the slice in UL, that is communicated to the Near-RT RIC, for providing prioritization for using RAN resources. According to this attribute, QoS flows under a slice are prioritized. The lower the value, the higher the priority. The value shall be greater than or equal to 1. | | -| maxDIPktSize | number | C | 0..1 | This attribute describes the maximum packet size to be supported by the network slice in the downlink in Bytes, that is communicated to the Near-RT RIC, for optimizing the RAN performance, especially for URLLC case and very small packets. Scope identifier designates the respective network slice and optionally slice SLA resources can further designate targeted cells. This attribute applies to all UEs that are a member of that slice in the designated target cells. This attribute is based on Maximum supported packet size (see GSMA NG.116 [17], clause 3.4.11 (“Maximum supported packet size”)). The Maximum supported packet size in GSMA NG.116 [17] is for both uplink & downlink while maxDIPktSize is only for downlink. | | - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-----------------------------------------------------------------------------------------------------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| maxUIPktSize | number | C | 0..1 | This attribute describes the maximum packet size to be supported by the network slice in the uplink in Bytes, that is communicated to the Near-RT RIC, for optimizing the RAN performance, especially for URLLC case and very small packets. Scope identifier designates the respective network slice and optionally slice SLA resources can further designate targeted cells. This attribute applies to all UEs that are a member of that slice in the designated target cells. This attribute is based on Maximum supported packet size (see GSMA NG.116 [17], clause 3.4.11 (“Maximum supported packet size”)). The Maximum supported packet size in GSMA NG.116 [17] is for both uplink & downlink while maxUIPktSize is only for uplink. | | -| NOTE 1: Presence condition "C" means that at least one attribute shall be included when this statement is used. | | | | | | -| NOTE 2: Void | | | | | | -| NOTE 3: Void | | | | | | - -#### 6.3.3.6 Load balancing targets - -The LbObjectives statement contains the attributes defined in table 6.3.3.6-3. The DILbObjective and UILbObjective included in LbObjectives are defined in tables 6.3.3.6-1 and 6.3.3.6-2. - -**Table 6.3.3.6-1: Definition of statement type DILbObjective** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| -| dlTargetPrbUsg | number | M | 1 | The target downlink PRB usage in percent. The denominator is the total number of PRBs in the cell, and the numerator is the number of PRBs specified by dlPrbUsgType. Value range: 0-100 [%] | | -| dlPrbUsgType | number | M | 1 | This attribute specifies the downlink PRB usage type used in the calculation of dlTargetPrbUsg.
1: Mean DL PRB used for data traffic (see 3GPP TS 28.552 [13], clause 5.1.1.2.5)
2: Peak DL PRB used for data traffic (see 3GPP TS 28.552 [13], clause 5.1.1.2.9)
3: Mean DL PRB used for data traffic per S-NSSAI (see 3GPP TS 28.552 [13], clause 5.1.1.2.5)
4: Peak DL PRB used for data traffic per S-NSSAI (see 3GPP TS 28.552 [13], clause 5.1.1.2.9) | If only cellId is included in the scope, applicable values are 1-2. If cellId and sliceId are included in the scope, applicable values are 3-4. | - -**Table 6.3.3.6-2: Definition of statement type UILbObjective** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| -| ulTargetPrbUsg | Number | M | 1 | The target uplink PRB usage in percent. The denominator is the total number of PRBs in the cell, and the numerator is the number of PRBs specified by ulPrbUsgType. Value range: 0-100 [%] | | -| ulPrbUsgType | Number | M | 1 | This attribute specifies the uplink PRB usage type used in the calculation of ulTargetPrbUsg.
1: Mean UL PRB used for data traffic (see 3GPP TS 28.552 [13], clause 5.1.1.2.5)
2: Peak UL PRB used for data traffic (see 3GPP TS 28.552 [13], clause 5.1.1.2.9)
3: Mean UL PRB used for data traffic per S-NSSAI (see 3GPP TS 28.552 [13], clause 5.1.1.2.5)
4: Peak UL PRB used for data traffic per S-NSSAI (see 3GPP TS 28.552 [13], clause 5.1.1.2.9) | If only cellId is included in the scope, applicable values are 1-2. If cellId and sliceId are included in the scope, applicable values are 3-4. | - -**Table 6.3.3.6-3: Definition of statement type LbObjectives** - -| Attribute Name | Data Type | P | Cardinality | Description | Applicability | -|---------------------------------------------------------------------------------------------------------------|---------------|---|-------------|--------------------------------------------------------------------------|---------------| -| dlLbObjective | DLbObjective | C | 0..1 | This schema indicates target PRB usage of downlink, see table 6.3.3.6-1. | | -| ulLbObjective | UILbObjective | C | 0..1 | This schema indicates target PRB usage of uplink, see table 6.3.3.6-2. | | -| NOTE: Presence condition "C" means that at least one attribute shall be included when this statement is used. | | | | | | - -#### 6.3.3.7 Energy saving targets - -The EsObjectives statement contains the attributes defined in table 6.3.3.7-1: - -**Table 6.3.3.7-1: Definition of statement type EsObjectives** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-----------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| targetPeeEnergy | number | C | 0..1 | Target average value of energy consumption PEE.Energy of PNF such as O-RU in kWh over targeted list of cells
For "PEE.Energy" see 3GPP TS 28.552 [13], clause 5.1.1.19.3, for 5G NR and 3GPP TS 32.425 [25], clause 4.12.2, for 4G LTE. | 4G, 5G | -| esPercentage | number | C | 0..1 | Energy consumption reduction of O-RU in percentage. The energy consumption i.e. PEE.Energy is measured based on method defined in 3GPP TS 28.552[13], clause 5.1.1.19.3, for 5G NR and 3GPP TS 32.425 [23], clause 4.12.2, for 4G LTE.
Value range is between 0 and 100. | 4G, 5G | - -NOTE: Presence condition "C" means that one and only attribute shall be included when this data type is used. - -### 6.3.4 Statements for policy resources - -#### 6.3.4.1 Introduction - -A1 policies are defined in A1GAP [2], clause 5.1.4.0 as containing a scope identifier and one or more policy statements where policy statements contain policy objectives and/or policy resources. This clause defines the structured data types and attributes to be used for policy resources. - -Table 6.3.4.1-1 specifies the data types defined for policy resources in the A1-P interface protocol. The usage of these is policy type specific and defined in clause 7.2. - -**Table 6.3.4.1-1: Statements for policy resources** - -| Data type | Clause defined | Description | Applicability | -|-------------------|----------------|---------------------------------------------------------------------------------------------------------------------------------|---------------| -| TspResources | 6.3.4.2 | Attributes used to schedule traffic on available cells in a different way than what would be through default behavior | | -| SliceSlaResources | 6.3.4.3 | Attributes used to indicate the RAN resources (such as cells or tracking areas) targeted for the respective slice SLA objective | | -| LbResources | 6.3.4.4 | Attributes used for load balancing between a congested cell and indicated candidate cells | | -| EsResources | 6.3.4.5 | Attributes used to express conditions for cells to apply network energy savings | | - -#### 6.3.4.2 Traffic steering preference - -The TspResources statement is defined in table 6.3.4.2-2 as an array of the type TspResource defined in table 6.3.4.2-1. - -**Table 6.3.4.2-1: Definition of type TspResource** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|----------------|---|-------------|-----------------------------------------------------------|---------------| -| cellIdList | CellIdList | M | 1 | list of CellIds, see clause 6.3.2 | | -| preference | PreferenceType | M | 1 | the preference of cell usage [SHALL/PREFER/AVOID/FORBID]. | | -| primary | boolean | O | 0..1 | indicates applicability to the selection of primary cell | | - -**Table 6.3.4.2-2: Definition of statement type TspResources** - -| Attribute Name | Data Type | P | Cardinality | Description | Applicability | -|----------------|--------------------|---|-------------|---------------------|---------------| -| tspResources | array(TspResource) | M | 1..N | list of TspResource | | - -When the value of the preference attribute is set to PREFER or AVOID, the cellIdList contains cells in descending order of importance for how they should be preferred or avoided, e.g. the first entry is *most preferred* or *most avoided*. When the preference value is set to SHALL or FORBID, the cellIdList contains cells that are of equal importance. - -When the value of the primary attribute is set to *true*, and the value of the preference attribute is set to SHALL, then only a cell in the cellIdList is to be used as primary cell. When the value of the primary attribute is set to *true*, and the value of the preference attribute is set to PREFER, then a cell in the cellIdList may be used as primary cell. When the value of the primary attribute is set to *true*, and the preference value is set to AVOID or FORBID, then no cell in the cellIdList is to be used as primary cell. - -When the value of the primary attribute is set to *false*, and the value of the preference attribute is set to SHALL, then only one or more cells in the cellIdList are to be used as secondary cell. When the value of the primary attribute is set to *false*, and the value of the preference attribute is set to PREFER, then one or more cells in the cellIdList may be used as secondary cell. When the value of the primary attribute is set to *false*, and the preference value is set to AVOID or FORBID, then no cell in the cellIdList is to be used as secondary cell. - -When the primary attribute is not included, the statement shall be handled in the same way as when the primary attribute is set to *false*. - -#### 6.3.4.3 Slice SLA Policy Resources - -The SliceSlaResources statement is defined in table 6.3.4.3-1. - -**Table 6.3.4.3-1: Definition of type SliceSlaResources** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-------------------------------------------------------------------------------------------------------------------|------------|---|-------------|-----------------------------------|---------------| -| cellIdList | CellIdList | C | 0..1 | list of CellIds, see clause 6.3.2 | | -| talList | TalList | C | 0..1 | list of Tals, see clause 6.3.2 | | -| NOTE: Presence condition "C" means that one and only one attribute shall be included when this statement is used. | | | | | | - -#### 6.3.4.4 Load Balancing Policy Resources - -The LbResources statement is defined in table 6.3.4.4-1. - -**Table 6.3.4.4-1: Definition of type LbResources** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|------------|---|-------------|-------------------------------------------------------------------------------------------|---------------| -| cellIdList | CellIdList | M | 1 | list of CellIds used to designate candidate cells to which cell load is to be transferred | | - -#### 6.3.4.5 Energy Savings resources - -The EsResources statement is defined in Table 6.3.4.5-2 as an array of the type EsResource defined in Table 6.3.4.5-1. - -**Table 6.3.4.5-1: Definition of type EsResource** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-----------------------|---------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| operationalCells | CellIdList | C | 0..1 | list of Cells preferred to keep operational, see clause 6.3.2 table 6.3.2-1 for the definition of the data type CellIdList, see NOTE 1 | 4G, 5G | -| operationalPreference | AvoidanceType | C | 0..1 | the operational preference of the cells while performing network energy saving [AVOID/FORBID], see clause 6.2.2.4 for the definition of the data type AvoidanceType, see NOTE 2 | 4G, 5G | -| coverageCells | CellIdList | C | 0..1 | list of cells with coverage preferences, see clause 6.3.2 table 6.3.2-1 for the definition of the data type CellIdList, see NOTE 1 | 4G, 5G | -| coveragePreference | AvoidanceType | C | 0..1 | the coverage preference of the cells while performing network energy saving [AVOID/FORBID], see clause 6.2.2.4 for the definition of the data type AvoidanceType, see NOTE 3 | 4G, 5G | -| dlPrbUsage | integer | O | 0..1 | The DL PRB usage (in percentage). The value range of this attribute is from 0 to 100. For "RRU.PrbDI", see 3GPP TS 28.552 [13], clause 5.1.1.2.1. A cell shall not perform network energy saving when its DL PRB usage is higher than the specified value. This attribute applies to all cells within the policy scope. | 5G | -| ulPrbUsage | integer | O | 0..1 | The UL PRB usage (in percentage). The value range of this attribute is from 0 to 100. For "RRU.PrbUI" see 3GPP TS 28.552 [13], clause 5.1.1.2.2. A cell shall not perform network energy saving when its UL PRB usage is higher than the specified value. This attribute applies to all cells within the policy scope. | 5G | - -NOTE 1: Presence condition "C" means that least operationalCells or coverageCells shall be included when this statement is used. - -NOTE 2: Presence condition "C" means that the operationalPreference shall only be included in case operationalCells is included. - -NOTE 3: Presence condition "C" means that the coveragePreference shall only be included in case coverageCells is included. - -**Table 6.3.4.5-2: Definition of statement type EsResources** - -| Attribute Name | Data Type | P | Cardinality | Description | Applicability | -|----------------|-------------------|---|-------------|--------------------|---------------| -| esResources | array(EsResource) | M | 1..N | list of EsResource | 4G, 5G | - -When the value of the operationalPreference attribute is set to FORBID, the operationalCells contains cells that are forbidden from being non-operational while performing the network energy savings. The operationalCells contains cells that are of equal importance. - -When the value of the operationalPreference attribute is set to AVOID, the operationalCells contains cells that should be avoided from being non-operational while performing the network energy savings. The operationalCells contains cells in - -descending order of importance for how they should be avoided, e.g. the first entry is most avoided from being non-operational while performing the network energy savings. - -When the value of the coveragePreference attribute is set to FORBID, the coverageCells contains cells that are forbidden from having any coverage impact while performing the network energy savings. The coverageCells contains cells that are of equal importance. - -When the value of the coveragePreference attribute is set to AVOID, the coverageCells contains cells that should be avoided from having any coverage impact while performing the network energy savings. The coverageCells contains cells in descending order of importance for how they should be avoided, e.g. the first entry is most avoided from having any coverage impact while performing the network energy savings. - -If dlPrbUsage is present in EsResource, then a cell may perform network energy saving methods only when its DL PRB usage is not higher than the specified dlPrbUsage value. If ulPrbUsage is present in EsResource, then a cell may perform network energy saving methods only when its UL PRB usage is not higher than the specified ulPrbUsage value. If both dlPrbUsage and ulPrbUsage are present in EsResource, then a cell may perform network energy saving methods only when its DL PRB usage is not higher than the specified dlPrbUsage value and its UL PRB usage is not higher than the specified ulPrbUsage value. The conditions should be checked when the corresponding performance measurements are available at the Near-RT RIC. - -## 6.4 Policy representations objects - -### 6.4.1 Policy object - -#### 6.4.1.1 General - -A PolicyObject is based on IETF RFC 8259 [6] and it always contains one set of: - -- one ScopeIdentifier; and -- one or more Statements. - -The PolicyObject can contain objective and/or resource statements as defined in table 6.4.1.1-1. - -**Table 6.4.1.1-1: General definition of PolicyObject** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------|---|-------------|--------------------|---------------| -| scope | ScopeIdentifier | M | 1 | See clause 6.3.1 | | -| qosObjectives | QosObjectives | C | 0..1 | See clause 6.3.3.2 | | -| qoeObjectives | QoeObjectives | C | 0..1 | See clause 6.3.3.3 | | -| ueLevelObjectives | UeLevelObjectives | C | 0..1 | See clause 6.3.3.4 | | -| sliceSlaObjectives | SliceSlaObjectives | C | 0..1 | See clause 6.3.3.5 | | -| lbObjectives | LbObjectives | C | 0..1 | See clause 6.3.3.6 | | -| tspResources | TspResources | C | 0..1 | See clause 6.3.4.2 | | -| sliceSlaResources | SliceSlaResources | O | 0..1 | See clause 6.3.4.3 | | -| lbResources | LbResources | C | 0..1 | See clause 6.3.4.4 | | -| esObjectives | EsObjectives | C | 0..1 | See clause 6.3.3.7 | | -| esResources | EsResources | C | 0..1 | See clause 6.3.4.5 | | -| NOTE: Presence condition "M" means that the data type shall be included in a PolicyObject. Allowed combinations are listed in clause 7. Presence condition "C" means that at least one Statement (for policy objectives and/or policy resources) shall be included. Presence condition "O" means that the data type can be optionally included in a PolicyObject. | | | | | | - -This definition is general and indicates how to formally construct a PolicyObject. The policy types in clause 7.2 define PolicyObjects for usage in the A1 service operations defined in A1AP [3], clause 5.3. - -#### 6.4.1.2 Allowed combinations - -A Statement can be applied together with a ScopeIdentifier containing different combinations of identifiers attributes. Not all combinations are relevant and different combinations are relevant for different policy types (see clause 7). - -### 6.4.2 Policy status object - -A PolicyStatusObject is based on IETF RFC 8259 [6] and contains: - -- one enforceStatus attribute; and conditionally -- one enforceReason attribute. - -The PolicyStatusObject contains status related attributes as defined in table 6.4.2-1: - -**Table 6.4.2-1: General definition of PolicyStatusObject** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---|-------------|------------------|--------------------------------------------------------------| -| enforceStatus | EnforcementStatusType | M | 1 | See clause 6.2.2 | statement indicating enforcement status of policy | -| enforceReason | EnforcementReasonType | C | 0..1 | See clause 6.2.2 | statement indicating reason for change of enforcement status | -| NOTE: Presence condition "M" means that the data type shall be included in a PolicyStatusObject used with the PolicyObjects defined in the present document. A PolicyObject and a PolicyStatusObject for a future policy type may be defined based on other attributes. Presence condition "C" means that the enforceReason shall only be included in case enforceStatus is NON_ENFORCED. | | | | | | - -### 6.4.3 Policy type object - -A PolicyTypeObject is based on IETF RFC 8259 [6] and contains: - -- one JSON schema for PolicyObject; and optionally -- one JSON schema for PolicyStatusObject. - -The type PolicyTypeObject is defined in table 6.4.3-1. - -**Table 6.4.3-1: General definition of PolicyTypeObject** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-------------------------------------------------------------------------------------------------------------|------------|---|-------------|-----------------------------|---------------| -| policySchema | JsonSchema | M | 1 | The schemas are policy type | | -| statusSchema | JsonSchema | O | 0..1 | specific | | -| NOTE 1: Clause 7.2 contains definitions and policy type specific schemas for O-RAN defined A1 policy types. | | | | | | -| NOTE 2: The policySchema attribute shall contain the compound policy schema as described in clause 7.1.3.1. | | | | | | - -The JSON schema for a PolicyObject is used by the A1-P Producer to validate a PolicyObject during Create policy and Update policy procedures. The JSON schema for a PolicyStatusObject is used by the A1-P Consumer to validate a PolicyStatusObject during Query policy status and Feedback policy procedures. The PolicyTypeObject can be retrieved using the Query policy type procedure. - -## 6.5 Binary data - -Binary data is not applicable in the present document. - -# 7 A1-P data types (A1 policy types) - -## 7.1 Introduction - -### 7.1.1 Identification and compatibility of policy types - -A policy type is identified by a PolicyTypeId as defined in A1AP [3], clause 6.2.3.1.3. The PolicyTypeId is a string that consists of two parts: a typename and a version. - -When updating a policy type, the version in the PolicyTypeId is updated according to SemVer [19] to reflect its compatibility with other policy types that has the same typename. - -Two policy types are considered as different if the PolicyTypeId is different, i.e. even if the typename is the same and the version only differs in the patch version digit. - -Two policy types are compatible in case the typename is the same and the major version digit in the version is the same. In general, two policy types X and Y are compatible when all objects that can be created based on policy type X can be validated by the schemas for policy type Y and all objects that can be created based on policy type Y can be validated by the schemas for policy type X. - -### 7.1.2 Common definitions - -#### 7.1.2.1 Scope and resource identifiers - -An A1 policy type always contains a ScopeIdentifier with data types defined in clause 6.3.1. It may also contain attributes for a resource statement that includes identifiers defined in clauses 6.3.2 and 6.3.4. To enable multiple policy types to be created based on the same identifiers, the policy schemas can link to the same JSON subschema for common data types. - -Each policy type definition links to a specific version of the common data types schema and the compatibility relations are described in Annex C. The policy types defined in the present document link to the version of the common data types schema defined in the present document. - -When updating the common data types schema, the version is updated according to SemVer [19]. The \$id keyword in the common data types schema contains the version as part of the URI. - -``` -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "$id": "https://schemas.o-ran.org/jsonschemas/altd/common_3.0.1", - "description": "This module is for scope identifier definitions. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at https://www.o-ran.org/sccl", - "$defs": { - "RanUserId": { - "type": "string", - "pattern": "^[A-Fa-f0-9]{16}$" - }, - "GroupId": { - "oneOf": [ - { - "type": "object", - "properties": { - "spId": { - "type": "integer", - "minimum": 1, - "maximum": 256 - } - } - } - ] - } - } -} -``` - -``` - - } - }, - "additionalProperties": false, - "required": ["spId"] -}, -{ - "type": "object", - "properties": { - "rfspIndex": { - "type": "integer", - "minimum": 1, - "maximum": 256 - } - }, - "additionalProperties": false, - "required": ["rfspIndex"] -} -] -}, - -"SliceId": { - "type": "object", - "properties": { - "sst": { - "type": "integer", - "minimum": 0, - "maximum": 255 - }, - "sd": { - "type": "string", - "pattern": "^[A-Fa-f0-9]{6}$" - }, - "plmnId": {"$ref": "#/$defs/PlmnId"} - }, - "additionalProperties": false, - "required": ["sst", "plmnId"] -}, - -"QosId": { - "oneOf": [ - { - "type": "object", - "properties": { - "5qi": { - "type": "integer", - "minimum": 1, - "maximum": 256 - } - }, - "additionalProperties": false, - "required": ["5qi"] - }, - { - "type": "object", - "properties": { - "qci": { - "type": "integer", - "minimum": 1, - "maximum": 256 - } - }, - "additionalProperties": false, - "required": ["qci"] - } - ] -}, - -"TaIList": { - "type": "array", - "items": { - "$ref": "#/$defs/TaI" - } -} - -``` - -``` - - }, - "minItems": 1 - }, - "Tai": { - "type": "object", - "properties": { - "plmnId": {"$ref": "#/$defs/PlmnId"}, - "tac": { - "type": "string", - "pattern": "^[A-Fa-f0-9]{6}$" - } - }, - "additionalProperties": false, - "required": ["plmnId", "tac"] - }, - "CellIdList": { - "type": "array", - "items": { - "$ref": "#/$defs/CellId" - }, - "minItems": 1 - }, - "CellId": { - "type": "object", - "properties": { - "plmnId": {"$ref": "#/$defs/PlmnId"}, - "cId": {"$ref": "#/$defs/CId"} - }, - "additionalProperties": false, - "required": ["plmnId", "cId"] - }, - "CId": { - "oneOf": [ - { - "type": "object", - "properties": { - "ncI": {"$ref": "#/$defs/NcI"} - }, - "additionalProperties": false, - "required": ["ncI"] - }, - { - "type": "object", - "properties": { - "ecI": {"$ref": "#/$defs/EcI"} - }, - "additionalProperties": false, - "required": ["ecI"] - } - ] - }, - "NcI": { - "type": "integer", - "minimum": 0, - "maximum": 68719476735 - }, - "EcI": { - "type": "integer", - "minimum": 0, - "maximum": 268435455 - }, - "PlmnId": { - "type": "object", - "properties": { - "mcc": { - "type": "string", - "pattern": "^[0-9]{3}$" - }, - "mnc": { - -``` - -``` - - "type": "string", - "pattern": "^[0-9]{2,3}$" - } - }, - "additionalProperties": false, - "required": ["mcc", "mnc"] - }, - - "MmeGroupId": { - "type": "string", - "pattern": "^[A-Fa-f0-9]{4}$" - }, - - "MmeCode": { - "type": "string", - "pattern": "^[A-Fa-f0-9]{2}$" - }, - - "GuMmeI": { - "type": "object", - "properties": { - "plmnId": {"$ref": "#/$defs/PlmnId"}, - "mmeGroupId": {"$ref": "#/$defs/MmeGroupId"}, - "mmeCode": {"$ref": "#/$defs/MmeCode"} - }, - "additionalProperties": false, - "required": ["plmnId", "mmeGroupId", "mmeCode"] - }, - - "MmeUeSlapId": { - "type": "integer", - "minimum": 0, - "maximum": 4294967295 - }, - - "GuMmeUeSlapId": { - "type": "object", - "properties": { - "guMmeI": {"$ref": "#/$defs/GuMmeI"}, - "mmeUeSlapId": {"$ref": "#/$defs/MmeUeSlapId"} - }, - "additionalProperties": false, - "required": ["guMmeI", "mmeUeSlapId"] - }, - - "AmfRegionId": { - "type": "string", - "pattern": "^[A-Fa-f0-9]{2}$" - }, - - "AmfSetId": { - "type": "string", - "pattern": "^[0-3][A-Fa-f0-9]{2}$" - }, - - "AmfPointer": { - "type": "string", - "pattern": "^[0-3][A-Fa-f0-9]{1}$" - }, - - "GuAmI": { - "type": "object", - "properties": { - "plmnId": {"$ref": "#/$defs/PlmnId"}, - "amfRegionId": {"$ref": "#/$defs/AmfRegionId"}, - "amfSetId": {"$ref": "#/$defs/AmfSetId"}, - "amfPointer": {"$ref": "#/$defs/AmfPointer"} - }, - "additionalProperties": false, - "required": ["plmnId", "amfRegionId", "amfSetId", "amfPointer"] - }, - - "AmfUeNgapId": { - "type": "integer", - "minimum": 0, - "maximum": 1099511627775 - }, - - "GuAmfUeNgapId": { - "type": "object", - -``` - -``` - - "properties": { - "guAmI": {"$ref": "#/$defs/GuAmI"}, - "amfUeNgapId": {"$ref": "#/$defs/AmfUeNgapId"} - }, - "additionalProperties": false, - "required": ["guAmI", "amfUeNgapId"] - }, - - "GnbId": { - "type": "object", - "properties": { - "gnbIdLength": { - "type": "integer", - "minimum": 22, - "maximum": 32 - }, - "gnbIdValue": { - "type": "integer", - "minimum": 0, - "maximum": 4294967295 - } - }, - "additionalProperties": false, - "required": ["gnbIdLength", "gnbIdValue"] - }, - - "GlobalGnbId": { - "type": "object", - "properties": { - "plmnId": {"$ref": "#/$defs/PlmnId"}, - "gnbId": {"$ref": "#/$defs/GnbId"} - }, - "additionalProperties": false, - "required": ["plmnId", "gnbId"] - }, - - "GuRanUeId": { - "type": "object", - "properties": { - "globalGnbId": {"$ref": "#/$defs/GlobalGnbId"}, - "ranUeId": {"$ref": "#/$defs/RanUeId"} - }, - "additionalProperties": false, - "required": ["globalGnbId", "ranUeId"] - }, - - "GnbCuUeFlapId": { - "type": "integer", - "minimum": 0, - "maximum": 4294967295 - }, - - "GuGnbCuUeFlapId": { - "type": "object", - "properties": { - "globalGnbId": {"$ref": "#/$defs/GlobalGnbId"}, - "gnbCuUeFlapId": {"$ref": "#/$defs/GnbCuUeFlapId"} - }, - "additionalProperties": false, - "required": ["globalGnbId", "gnbCuUeFlapId"] - }, - - "GnbCuCpUeElapId": { - "type": "integer", - "minimum": 0, - "maximum": 4294967295 - }, - - "GuGnbCuCpUeElapId": { - "type": "object", - "properties": { - "globalGnbId": {"$ref": "#/$defs/GlobalGnbId"}, - "gnbCuCpUeElapId": {"$ref": "#/$defs/GnbCuCpUeElapId"} - }, - "additionalProperties": false, - "required": ["globalGnbId", "gnbCuCpUeElapId"] - }, - -``` - -``` - -"EnbUeX2apId": { - "type": "integer", - "minimum": 0, - "maximum": 4095 -}, -"EnbId": { - "oneOf": [ - { - "type": "object", - "properties": { - "macroEnbId": { - "type": "string", - "pattern": "^[A-Fa-f0-9]{5}$" - } - }, - "additionalProperties": false, - "required": ["macroEnbId"] - }, - { - "type": "object", - "properties": { - "homeEnbId": { - "type": "string", - "pattern": "^[A-Fa-f0-9]{7}$" - } - }, - "additionalProperties": false, - "required": ["homeEnbId"] - }, - { - "type": "object", - "properties": { - "shortMacroEnbId": { - "type": "string", - "pattern": "^[0-3][A-Fa-f0-9]{4}$" - } - }, - "additionalProperties": false, - "required": ["shortMacroEnbId"] - }, - { - "type": "object", - "properties": { - "longMacroEnbId": { - "type": "string", - "pattern": "^[0-1][A-Fa-f0-9]{5}$" - } - }, - "additionalProperties": false, - "required": ["longMacroEnbId"] - } - ] -}, -"GlobalEnbId": { - "type": "object", - "properties": { - "plmnId": { "$ref": "#/$defs/PlmnId" }, - "enbId": { "$ref": "#/$defs/EnbId" } - }, - "additionalProperties": false, - "required": ["plmnId", "enbId"] -}, -"GuEnbUeX2apId": { - "type": "object", - "properties": { - "globalEnbId": { "$ref": "#/$defs/GlobalEnbId" }, - "enbUeX2apId": { "$ref": "#/$defs/EnbUeX2apId" } - }, - "additionalProperties": false, - "required": ["globalEnbId", "enbUeX2apId"] -} - -``` - -``` - - }, - "NgRanNodeUeXnapId": { - "type": "integer", - "minimum": 0, - "maximum": 4294967295 - }, - "NgEnbId": { - "oneOf": [ - { - "type": "object", - "properties": { - "macroNgEnbId": { - "type": "integer", - "minimum": 0, - "maximum": 1048575 - } - }, - "additionalProperties": false, - "required": ["macroNgEnbId"] - }, - { - "type": "object", - "properties": { - "shortMacroNgEnbId": { - "type": "integer", - "minimum": 0, - "maximum": 262143 - } - }, - "additionalProperties": false, - "required": ["shortMacroNgEnbId"] - }, - { - "type": "object", - "properties": { - "longMacroNgEnbId": { - "type": "integer", - "minimum": 0, - "maximum": 2097151 - } - }, - "additionalProperties": false, - "required": ["longMacroNgEnbId"] - } - ] - }, - "GlobalNgEnbId": { - "type": "object", - "properties": { - "plmnId": {"$ref": "#/$defs/PlmnId"}, - "ngEnbId": {"$ref": "#/$defs/NgEnbId"} - }, - "additionalProperties": false, - "required": ["plmnId", "ngEnbId"] - }, - "GlobalNgRanNodeId": { - "oneOf": [ - { - "type": "object", - "properties": { - "globalGnbId": {"$ref": "#/$defs/GlobalGnbId"} - }, - "additionalProperties": false, - "required": ["globalGnbId"] - }, - { - "type": "object", - "properties": { - "globalNgEnbId": {"$ref": "#/$defs/GlobalNgEnbId"} - }, - -``` - -``` - - "additionalProperties": false, - "required": ["globalNgEnbId"] - } - ] - }, - "GuNgRanNodeUeXnapUeId": { - "type": "object", - "properties": { - "globalNgRanNodebId": {"$ref": "#/$defs/GlobalNgRanNodeId"}, - "ngRanNodeUeXnapId": {"$ref": "#/$defs/NgRanNodeUeXnapId"} - }, - "additionalProperties": false, - "required": ["globalNgRanNodebId", "ngRanNodeUeXnapId"] - }, - "UeId": { - "oneOf": [ - { - "type": "object", - "properties": { - "guRanUeId": {"$ref": "#/$defs/GuRanUeId"} - }, - "additionalProperties": false, - "required": ["guRanUeId"] - }, - { - "type": "object", - "properties": { - "guAmfUeNgapId": {"$ref": "#/$defs/GuAmfUeNgapId"} - }, - "additionalProperties": false, - "required": ["guAmfUeNgapId"] - }, - { - "type": "object", - "properties": { - "guMmeUeSlapId": {"$ref": "#/$defs/GuMmeUeSlapId"} - }, - "additionalProperties": false, - "required": ["guMmeUeSlapId"] - }, - { - "type": "object", - "properties": { - "guGnbCuUeFlapId": {"$ref": "#/$defs/GuGnbCuUeFlapId"} - }, - "additionalProperties": false, - "required": ["guGnbCuUeFlapId"] - }, - { - "type": "object", - "properties": { - "guGnbCuCpUeElapId": {"$ref": "#/$defs/GuGnbCuCpUeElapId"} - }, - "additionalProperties": false, - "required": ["guGnbCuCpUeElapId"] - }, - { - "type": "object", - "properties": { - "guEnbUeX2apId": {"$ref": "#/$defs/GuEnbUeX2apId"} - }, - "additionalProperties": false, - "required": ["guEnbUeX2apId"] - }, - { - "type": "object", - "properties": { - "guNgRanNodeUeXnapUeId": {"$ref": "#/$defs/GuNgRanNodeUeXnapUeId"} - }, - "additionalProperties": false, - -``` - -``` - - "required": ["guNgRanNodeUeXnapUeId"] - } - ] - } -} -} -} - -``` - -#### 7.1.2.2 Policy status - -This is a generic policy status schema, it may be adjusted and used together with a policy schema in a PolicyTypeObject and will then be identified by the same policy type identifier as the policy schema. - -``` - -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "description": "This module is for O-RAN standard policy status. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at https://www.o-ran.org/sccl", - "type": "object", - "properties": { - "enforceStatus": { - "type": "string", - "enum": [ - "ENFORCED", - "NOT_ENFORCED" - ] - }, - "enforceReason": { - "type": "string", - "enum": [ - "SCOPE_NOT_APPLICABLE", - "STATEMENT_NOT_APPLICABLE", - "OTHER_REASON" - ] - } - }, - "additionalProperties": false, - "required": ["enforceStatus"] -} - -``` - -### 7.1.3 Schema identification - -#### 7.1.3.1 General - -The policy schemas defined in clause 7.2 (e.g. policy schema for QoS target in clause 7.2.1.3.1) are base schemas that embed a subschema with common data types definitions. The base schemas can be used for creating or validating A1 policies after embedding the content of the linked common data types schema. A schema resulting from embedding the content of a linked subschema into a base schema is referred to as a compound schema document, see JSON Schema Draft 2020-12 [7]. It is the compound policy schemas that are identified by the policy type identifier and included in the PolicyTypeObject specified in clause 6.4.3. - -The base schema and the linked subschema together represent the same JSON schema as the compound schema created by embedding the linked subschema into the base schema at the place where it is linked. Hence, the versions of a compound policy schema and its base policy schema are the same, and is indicated in the policy type identifier. The policy type identifier is part of the \$id keyword included in the policy schema. The \$id keyword of the embedded subschemas are included in the subschema. - -#### 7.1.3.2 Schema URI structure - -The base URI for A1 policy types and embedded schemas is: - -{uriRoot}/a1td - -where uriRoot follows an absolute URI syntax, but excludes the "query" component. The URI root contains the "scheme" component and may contain an "authority" component and may also contain a prefix subcomponent. - -The \$id keyword for the policy schemas are constructed from the base URI and the policy type identifier: - -{uriRoot}/a1td/ - -The \$id keyword for the subschema with common data types is constructed from the base URI, the name "common", and the version (x.y.z): - -{uriRoot}/a1td/common\_ - -In the JSON schemas defined in the present document, the default uriRoot is: - - - -## 7.2 Policy type definitions - -### 7.2.1 QoS target - -#### 7.2.1.1 Policy type identifier - -PolicyTypeId: ORAN\_QoSTarget\_6.0.1 - -#### 7.2.1.2 Rationale - -##### 7.2.1.2.1 Use case - -See Non-RT RIC & A1/R1 interface: Use Cases and Requirements [1], clause 4.3. - -##### 7.2.1.2.2 Statements, restrictions and extensions - -A QoS statement can be applied together with ScopeIdentifier containing different combinations of identifiers. Not all combinations are relevant. Table 7.2.1.2.2-1 indicates the combinations that are allowed. - -**Table 7.2.1.2.2-1: Allowed combinations of qosObjectives statement with ScopeIdentifier** - -| Policy statement | ScopeIdentifier | ueId | groupId | sliceId | qosId | cellId | -|------------------|-----------------|------|---------|---------|-------|--------| -| qosObjectives | | 1 | 0..1 | 0 | 1 | 0..1 | -| qosObjectives | | 1 | 0 | 0..1 | 1 | 0..1 | -| qosObjectives | | 0 | 1 | 0 | 1 | 0..1 | -| qosObjectives | | 0 | 0 | 1 | 1 | 0..1 | -| qosObjectives | | 0 | 0 | 0 | 1 | 0..1 | - -NOTE: on each row is listed a combination of identifiers that is allowed for the indicated statement. Notation is the same as for cardinality: "0" means the identifier shall not occur, "0..1" means the identifier may occur and "1" means the identifier shall occur. Only at most one occurrence of an identifier is allowed in the present version. - -#### 7.2.1.3 JSON schemas - -##### 7.2.1.3.1 Policy schema - -``` -"$schema": "https://json-schema.org/draft/2020-12/schema", -"$id": "https://schemas.o-ran.org/jsonschemas/a1td/oran_qosTarget_6.0.1", -``` - -``` - -"description": "This module is for O-RAN standard QoS Target policy. -Copyright 2026 O-RAN ALLIANCE e.V. -Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); -You may not use this file except in compliance with the License. -You may obtain a copy of the License at https://www.o-ran.org/sccl", - -"type": "object", -"properties": { - - "scope": { - "anyOf": [ - { - "type": "object", - "properties": { - "ueId": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/UeId"}, - "groupId": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/GroupId"}, - "qosId": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["ueId", "qosId"] - }, - { - "type": "object", - "properties": { - "ueId": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/UeId"}, - "sliceId": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/SliceId"}, - "qosId": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["ueId", "qosId"] - }, - { - "type": "object", - "properties": { - "groupId": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/GroupId"}, - "qosId": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["groupId", "qosId"] - }, - { - "type": "object", - "properties": { - "sliceId": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/SliceId"}, - "qosId": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["sliceId", "qosId"] - }, - { - "type": "object", - "properties": { - "qosId": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["qosId"] - } - ] - }, - - "qosObjectives": { - "type": "object", - "properties": { - "gfbr": {"type": "number"}, - "mfbr": {"type": "number"}, - "priorityLevel": {"type": "number"}, - } - } -} - -``` - -``` - - "pdb": {"type": "number"} - }, - "minProperties": 1, - "additionalProperties": false -} -}, - -"additionalProperties": false, -"required": ["scope", "qosObjectives"], - -"$defs": { - "https://schemas.o-ran.org/jsonschemas/altd/common_3.0.1": -} -} - -``` - -##### 7.2.1.3.2 Policy status schema - -The generic policy status schema in clause 7.1.2.2 is used. - -### 7.2.2 QoE target - -#### 7.2.2.1 Policy type identifier - -**PolicyTypeId: ORAN\_QoETarget\_6.0.1** - -#### 7.2.2.2 Rationale - -##### 7.2.2.2.1 Use case - -See Non-RT RIC & A1/R1 interface: Use Cases and Requirements [1], clause 4.2. - -##### 7.2.2.2.2 Statements, restrictions and extensions - -A QoE statement can be applied together with ScopeIdentifier containing different combinations of identifiers. Not all combinations are relevant. Table 7.2.2.2.2-1 indicates the combinations that are allowed. - -**Table 7.2.2.2.2-1: Allowed combinations of qoeObjectives statement with ScopeIdentifier** - -| Policy statement | ScopeIdentifier | ueId | groupId | sliceId | qosId | cellId | -|------------------|-----------------|------|---------|---------|-------|--------| -| qoeObjectives | | 1 | 0 | 1 | 0..1 | 0..1 | -| qoeObjectives | | 1 | 0 | 0 | 1 | 0..1 | -| qoeObjectives | | 0 | 0 | 1 | 0..1 | 0..1 | -| qoeObjectives | | 0 | 0 | 0 | 1 | 0..1 | - -NOTE: on each row is listed a combination of identifiers that is allowed for the indicated statement. Notation is the same as for cardinality: "0" means the identifier shall not occur, "0..1" means the identifier may occur and "1" means the identifier shall occur. Only at most one occurrence of an identifier is allowed in the present version. - -#### 7.2.2.3 JSON schemas - -##### 7.2.2.3.1 Policy schema - -``` - -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "$id": "https://schemas.o-ran.org/jsonschemas/altd/oran_qoetarget_6.0.1", - "description": "This module is for O-RAN standard QoE Target policy. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); - -``` - -You may not use this file except in compliance with the License. -You may obtain a copy of the License at , - -``` - -"type": "object", -"properties": { - - "scope": { - "anyOf": [ - { - "type": "object", - "properties": { - "ueId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/UeId"}, - "sliceId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/SliceId"}, - "qosId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["ueId", "sliceId"] - }, - { - "type": "object", - "properties": { - "ueId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/UeId"}, - "qosId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["ueId", "qosId"] - }, - { - "type": "object", - "properties": { - "sliceId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/SliceId"}, - "qosId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["sliceId"] - }, - { - "type": "object", - "properties": { - "qosId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["qosId"] - } - ] - }, - - "goeObjectives": { - "type": "object", - "properties": { - "goeScore": {"type": "number"}, - "initialBuffering": {"type": "number"}, - "reBuffFreq": {"type": "number"}, - "stallRatio": {"type": "number"} - }, - "minProperties": 1, - "additionalProperties": false - } -}, - -"additionalProperties": false, -"required": ["scope", "goeObjectives"], - -"$defs": { - "https://schemas.o-ran.org/jsonschemas/altd/common_3.0.1": - -} - -``` - -} - -##### 7.2.2.3.2 Policy status schema - -The generic policy status schema in clause 7.1.2.2 is used. - -### 7.2.3 Traffic steering preferences - -#### 7.2.3.1 Policy type identifier - -PolicyTypeId: **ORAN\_TrafficSteeringPreference\_6.0.1** - -#### 7.2.3.2 Rationale - -##### 7.2.3.2.1 Use case - -See in Non-RT RIC & A1/R1 interface: Use Cases and Requirements [1], clause 4.1. - -##### 7.2.3.2.2 Statements, restrictions and extensions - -A TSP statement can be applied together with ScopeIdentifier containing different combinations of identifiers. Not all combinations are relevant. Table 7.2.3.2.2-1 indicates combinations that are allowed. - -**Table 7.2.3.2.2-1: Allowed combinations of tspResources statement with ScopeIdentifier** - -| Policy statement | ScopeIdentifier | ueId | groupId | sliceId | qosId | cellId | -|------------------|-----------------|------|---------|---------|-------|--------| -| tspResources | | 1 | 0 | 0..1 | 0..1 | 0..1 | -| tspResources | | 0 | 0 | 1 | 0..1 | 0..1 | - -NOTE: on each row is listed a combination of identifiers that is allowed for the indicated statement. Notation is the same as for cardinality: “0” means the identifier shall not occur, “0..1” means the identifier may occur and “1” means the identifier shall occur. Only at most one occurrence of an identifier is allowed in the present version. - -#### 7.2.3.3 JSON schemas - -##### 7.2.3.3.1 Policy schema - -``` -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "$id": "https://schemas.o-ran.org/jsonschemas/altd/oran_trafficsteeringpreference_6.0.1" - "description": "This module is for O-RAN standard Traffic Steering Preference policy. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at https://www.o-ran.org/sccl", - - "type": "object", - "properties": { - - "scope": { - "anyOf": [ - { - "type": "object", - "properties": { - "ueId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/UeId"}, - "sliceId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/SliceId"}, - "qosId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - } - ] - } - } -} -``` - -``` - - "required": ["ueId"] - }, - { - "type": "object", - "properties": { - "sliceId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/SliceId"}, - "qosId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["sliceId"] - } -] -}, - -"tspResources": { - "type": "array", - "items": { - "$ref": "#/$defs/TspResource" - }, - "minItems": 1 -} -}, - -"additionalProperties": false, -"required": ["scope", "tspResources"], - -"$defs": { - "PreferenceType": { - "type": "string", - "enum": [ - "SHALL", - "PREFER", - "AVOID", - "FORBID" - ] - }, - "TspResource": { - "type": "object", - "properties": { - "cellIdList": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellIdList"}, - "preference": {"$ref": "#/$defs/PreferenceType"}, - "primary": {"type": "boolean"} - }, - "required": ["cellIdList", "preference"], - "additionalProperties": false - }, - "https://schemas.o-ran.org/jsonschemas/altd/common_3.0.1": - -} -} - -``` - -##### 7.2.3.3.2 Policy status schema - -The generic policy status schema in clause 7.1.2.2 is used. - -### 7.2.4 QoS optimization with resource directive - -#### 7.2.4.1 Policy type identifier - -PolicyTypeId: ORAN\_QoSandTSP\_6.0.1 - -#### 7.2.4.2 Rationale - -##### 7.2.4.2.1 Use case - -Addresses both the use cases specified in Non-RT RIC & A1/R1 interface: Use Cases and Requirements [1], clauses 4.3 and 4.1. - -##### 7.2.4.2.2 Statements, restrictions and extensions - -The allowed combinations of ScopeIdentifier and statements is the common subset of those defined for the policy type QoS Target and the policy type Traffic Steering Preferences. - -#### 7.2.4.3 JSON schemas - -##### 7.2.4.3.1 Policy schema - -``` -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "$id": "https://schemas.o-ran.org/jsonschemas/altd/oran_qosandtsp_6.0.1", - "description": "This module is for O-RAN standard QoS Target and Traffic Steering Preference policy. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at https://www.o-ran.org/sccl", - - "type": "object", - "properties": { - - "scope": { - "anyOf": [ - { - "type": "object", - "properties": { - "ueId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/UeId"}, - "sliceId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/SliceId"}, - "qosId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["ueId", "qosId"] - }, - { - "type": "object", - "properties": { - "sliceId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/SliceId"}, - "qosId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["sliceId", "qosId"] - } - ] - }, - - "qosObjectives": { - "type": "object", - "properties": { - "gfbr": {"type": "number"}, - "mfbr": {"type": "number"}, - "priorityLevel": {"type": "number"}, - "pdb": {"type": "number"} - }, - "minProperties": 1, - "additionalProperties": false - }, - }, -} -``` - -``` - - "tspResources": { - "type": "array", - "items": { - "$ref": "#/$defs/TspResource" - }, - "minItems": 1 - } - }, - - "additionalProperties": false, - "required": ["scope", "qosObjectives", "tspResources"], - - "$defs": { - "PreferenceType": { - "type": "string", - "enum": [ - "SHALL", - "PREFER", - "AVOID", - "FORBID" - ] - }, - "TspResource": { - "type": "object", - "properties": { - "cellIdList": { "$ref": "#/jsonschemas/altd/common_3.0.1/$defs/CellIdList" }, - "preference": { "$ref": "#/$defs/PreferenceType" }, - "primary": { "type": "boolean" } - }, - "required": ["cellIdList", "preference"], - "additionalProperties": false - }, - "https://schemas.o-ran.org/jsonschemas/altd/common_3.0.1": - } - } - } -} - -``` - -##### 7.2.4.3.2 Policy status schema - -The generic policy status schema in clause 7.1.2.2 is used. - -### 7.2.5 QoE optimization with resource directive - -#### 7.2.5.1 Policy type identifier - -PolicyTypeId: **ORAN\_QoEandTSP\_6.0.1** - -#### 7.2.5.2 Rationale - -##### 7.2.5.2.1 Use case - -Addresses both the use cases specified in Non-RT RIC & A1/R1 interface: Use Cases and Requirements [1], clauses 4.2 and 4.1. - -##### 7.2.5.2.2 Statements, restrictions and extensions - -The allowed combinations of ScopeIdentifier and statements is the common subset of those defined for the policy type QoE Target and the policy type Traffic Steering Preferences. - -#### 7.2.5.3 JSON schemas - -##### 7.2.5.3.1 Policy schema - -``` -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "$id": "https://schemas.o-ran.org/jsonschemas/altd/oran_qoeandtsp_6.0.1", - "description": "This module is for O-RAN standard QoE Target and Traffic Steering Preference policy. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at https://www.o-ran.org/sccl", - - "type": "object", - "properties": { - - "scope": { - "anyOf": [ - { - "type": "object", - "properties": { - "ueId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/UeId"}, - "sliceId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/SliceId"}, - "qosId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["ueId", "sliceId"] - }, - { - "type": "object", - "properties": { - "ueId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/UeId"}, - "qosId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["ueId", "qosId"] - }, - { - "type": "object", - "properties": { - "sliceId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/SliceId"}, - "qosId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["sliceId"] - } - ] - }, - - "qoeObjectives": { - "type": "object", - "properties": { - "qoeScore": {"type": "number"}, - "initialBuffering": {"type": "number"}, - "reBuffFreq": {"type": "number"}, - "stallRatio": {"type": "number"} - }, - "minProperties": 1, - "additionalProperties": false - }, - - "tspResources": { - "type": "array", - "items": { - "$ref": "#/$defs/TspResource" - }, - "minItems": 1 - } - } -} -``` - -``` - - } - }, - - "additionalProperties": false, - "required": ["scope", "goeObjectives", "tspResources"], - - "$defs": { - "PreferenceType": { - "type": "string", - "enum": [ - "SHALL", - "PREFER", - "AVOID", - "FORBID" - ] - }, - "TspResource": { - "type": "object", - "properties": { - "cellIdList": { "$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellIdList" }, - "preference": { "$ref": "#/$defs/PreferenceType" }, - "primary": { "type": "boolean" } - }, - "required": ["cellIdList", "preference"], - "additionalProperties": false - }, - "https://schemas.o-ran.org/jsonschemas/altd/common_3.0.1": - } -} - -``` - -##### 7.2.5.3.2 Policy status schema - -The generic policy status schema in clause 7.1.2.2 is used. - -### 7.2.6 UE level target - -#### 7.2.6.1 Policy type identifier - -PolicyTypeId: **ORAN\_UELevelTarget\_5.0.1** - -#### 7.2.6.2 Rationale - -##### 7.2.6.2.1 Use case - -Addresses the use case specified in Non-RT RIC & A1/R1 interface: Use Cases and Requirements [1], clause 4.3. - -##### 7.2.6.2.2 Statements, restrictions and extensions - -A UE level statement can be applied together with scope identifiers containing different combinations of identifiers. Not all combinations are relevant. Table 7.2.6.2.2-1 indicates the combinations that are allowed. - -**Table 7.2.6.2.2-1: Allowed combinations of ueLevelObjectives statement with ScopeIdentifier** - -| Policy statement | Scope identifier | ueId | groupId | sliceId | qosId | cellId | -|-------------------|------------------|------|---------|---------|-------|--------| -| ueLevelObjectives | | 1 | 0..1 | 0..1 | 0 | 0..1 | -| ueLevelObjectives | | 1 | 0..1 | 0..1 | 1 | 0..1 | -| ueLevelObjectives | | 1 | 0 | 1 | 0..1 | 0..1 | - -NOTE: on each row is listed a combination of identifiers that is allowed for the indicated statement. Notation is the same as for cardinality: "0" means the identifier shall not occur, "0..1" means the identifier may occur and "1" means the identifier shall occur. Only at most one occurrence of an identifier is allowed in the present version. - -#### 7.2.6.3 JSON schemas - -##### 7.2.6.3.1 Policy schema - -``` -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "$id": "https://schemas.o-ran.org/jsonschemas/altd/oran_ueleveltarget_5.0.1", - "description": "This module is for O-RAN standard UE Level Target policy. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at https://www.o-ran.org/sccl", - - "type": "object", - "properties": { - - "scope": { - "anyOf": [ - { - "type": "object", - "properties": { - "ueId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/UeId"}, - "groupId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/GroupId"}, - "sliceId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/SliceId"}, - "cellId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["ueId"] - }, - { - "type": "object", - "properties": { - "ueId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/UeId"}, - "groupId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/GroupId"}, - "sliceId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/SliceId"}, - "qosId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["ueId", "qosId"] - }, - { - "type": "object", - "properties": { - "ueId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/UeId"}, - "sliceId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/SliceId"}, - "qosId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/QosId"}, - "cellId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["ueId", "sliceId"] - } - ] - }, - }, -} -``` - -``` - - "ueLevelObjectives": { - "type": "object", - "properties": { - "ulThroughput": { "type": "number" }, - "dlThroughput": { "type": "number" }, - "ulPacketDelay": { "type": "number" }, - "dlPacketDelay": { "type": "number" }, - "ulPdcpsduPacketLossRate": { "type": "number" }, - "dlRlcSduPacketLossRate": { "type": "number" }, - "dlReliability": { "$ref": "#/$defs/ReliabilityType" }, - "ulReliability": { "$ref": "#/$defs/ReliabilityType" } - }, - "minProperties": 1, - "additionalProperties": false - } - }, - - "additionalProperties": false, - "required": ["scope", "ueLevelObjectives"], - - "$defs": { - "ReliabilityType": { - "type": "object", - "properties": { - "packetSize": { "type": "number" }, - "userPlaneLatency": { "type": "number" }, - "successProbability": { "type": "number" } - }, - "required": ["packetSize", "userPlaneLatency", "successProbability"] - }, - "$ref": "https://schemas.o-ran.org/jsonschemas/altd/common_3.0.1": - } -} - -``` - -##### 7.2.6.3.2 Policy status schema - -The generic policy status schema in clause 7.1.2.2 is used. - -### 7.2.7 Slice SLA target - -#### 7.2.7.1 Policy type identifier - -PolicyTypeId: ORAN\_SliceSLATarget\_4.0.2 - -#### 7.2.7.2 Rationale - -##### 7.2.7.2.1 Use case - -See Non-RT RIC and A1/R1 interface: Use Cases and Requirements [1], clause 4.5. - -##### 7.2.7.2.2 Statements, restrictions and extensions - -The sliceSlaObjectives statement can be applied together with ScopeIdentifier containing sliceId identifier. Table 7.2.7.2.2-1 indicates the combination that is allowed. - -**Table 7.2.7.2.2-1: Allowed combinations of sliceSlaObjectives statement with ScopeIdentifier** - -| Policy statement | scopeId | groupId | sliceId | qosId | cellId | -|---------------------------------------------------------------------------------------|---------|---------|---------|-------|--------| -| sliceSlaObjectives | 0 | 0 | 1 | 0 | 0 | -| NOTE: "0" means the identifier shall not occur, "1" means the identifier shall occur. | | | | | | - -The sliceSlaResources statement can optionally be applied together with sliceSlaObjectives statement. - -#### 7.2.7.3 JSON schemas - -##### 7.2.7.3.1 Policy schema - -``` -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "$id": "https://schemas.o-ran.org/jsonschemas/altd/oran_sliceslatarget_4.0.2", - "description": "This module is for O-RAN standard slice SLA policy. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at https://www.o-ran.org/sccl", - - "type": "object", - "properties": { - - "scope": { - "type": "object", - "properties": { - "sliceId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/SliceId"} - }, - "additionalProperties": false, - "required": ["sliceId"] - }, - - "sliceSlaObjectives": { - "type": "object", - "properties": { - "maxNumberOfUes": {"type": "number"}, - "maxNumberOfPduSessions": {"type": "number"}, - "guaDlThptPerSlice": {"type": "number"}, - "maxDlThptPerSlice": {"type": "number"}, - "maxDlThptPerUe": {"type": "number"}, - "guaUlThptPerSlice": {"type": "number"}, - "maxUlThptPerSlice": {"type": "number"}, - "maxUlThptPerUe": {"type": "number"}, - "maxDlPacketDelayPerUe": {"type": "number"}, - "maxUlPacketDelayPerUe": {"type": "number"}, - "maxDlPdcpsduPacketLossRatePerUe": { - "type": "number", - "minimum": 0, - "maximum": 1 - }, - "maxUlRlcSduPacketLossRatePerUe": { - "type": "number", - "minimum": 0, - "maximum": 1 - }, - "minDlReliabilityPerUe": {"$ref": "#/$defs/ReliabilityType"}, - "minUlReliabilityPerUe": {"$ref": "#/$defs/ReliabilityType"}, - "maxDlJitterPerUe": {"type": "number"}, - "maxUlJitterPerUe": {"type": "number"}, - "dlSlicePriority": { - "type": "number", - "minimum": 1 - }, - "ulSlicePriority": { - "type": "number", - "minimum": 1 - }, - "maxDlPktSize": {"$type": "number"}, - "maxUlPktSize": {"$type": "number"} - }, - "minProperties": 1, - "additionalProperties": false - }, - }, -} -``` - -``` - - "sliceSlaResources": { - "type": "object", - "properties": { - "cellIdList": {"$ref": "/schemas/altd/common_3.0.1#/$defs/CellIdList"}, - "taILList": {"$ref": "/schemas/altd/common_3.0.1#/$defs/TaILList"} - }, - "additionalProperties": false, - "oneOf": [ - {"required": ["cellIdList"]}, - {"required": ["taILList"]} - ] - } - }, - "additionalProperties": false, - "required": ["scope", "sliceSlaObjectives"], - - "$defs": { - "ReliabilityType": { - "type": "object", - "properties": { - "packetSize": {"type": "number"}, - "userPlaneLatency": {"type": "number"}, - "successProbability": { - "type": "number", - "minimum": 0, - "maximum": 1 - } - }, - "required": ["packetSize", "userPlaneLatency", "successProbability"] - }, - "https://schemas.o-ran.org/schemas/altd/common_3.0.1": - } -} - -``` - -##### 7.2.7.3.2 Policy status schema - -The generic policy status schema in clause 7.1.2.2 is used. - -### 7.2.8 Load balancing - -#### 7.2.8.1 Policy type identifier - -PolicyTypeId: **ORAN\_LoadBalancing\_3.0.1** - -#### 7.2.8.2 Rationale - -##### 7.2.8.2.1 Use case - -See Non-RT RIC & A1/R1 interface: Use Cases and Requirements [1], clause 4.5. - -##### 7.2.8.2.2 Statements, restrictions and extensions - -A `lbObjectives` statement can be applied together with `ScopeIdentifier` containing different combinations of identifiers. Not all combinations are relevant. Table 7.2.8.2.2-1 indicates the combinations that are allowed. - -`ScopeIdentifier` is used to designate a cell from which load needs to be transferred to other cells. If `sliceId` is applied together with `cellId`, only a part of the load associated with a designated slice among the cell load is transferred to other cells. - -`ScopeIdentifier` also indicates the measurement range for calculating the load specified by `ulPrbUsgType` and `dlPrbUsgType` in `lbObjectives` statement. If only `cellId` is applied, applicable values for `ulPrbUsgType` and `dlPrbUsgType` are 1-2. If `sliceId` is applied together with `cellId`, applicable values for `ulPrbUsgType` and `dlPrbUsgType` are 3-4. - -Regardless of the combination of ScopeIdentifier and lbObjectives statement, lbResources statement indicates the target cells to which the load is transferred. - -**Table 7.2.8.2.2-1: Allowed combinations of lbObjectives statement with ScopeIdentifier** - -| Policy statement | ScopeIdentifier | ueId | groupId | sliceId | qosId | cellId | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------|---------|---------|-------|--------| -| lbObjectives | | 0 | 0 | 0..1 | 0 | 1 | -| NOTE: on each row is listed a combination of identifiers that is allowed for the indicated statement.
Notation is the same as for cardinality: "0" means the identifier shall not occur, "0..1" means the identifier may occur and "1" means the identifier shall occur. Only at most one occurrence of an identifier is allowed in the present version. | | | | | | | - -The lbObjectives statement is applied together with lbResources statement. - -#### 7.2.8.3 JSON schemas - -##### 7.2.8.3.1 Policy schema - -``` -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "$id": "https://schemas.o-ran.org/jsonschemas/altd/oran_loadbalancing_3.0.1", - "description": "This module is for O-RAN standard Load Balancing policy. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at https://www.o-ran.org/sccl", - - "type": "object", - "properties": { - - "scope": { - "anyOf": [ - { - "type": "object", - "properties": { - "sliceId": { "$ref": "/jsonschemas/altd/common_3.0.1#/$defs/SliceId" }, - "cellId": { "$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellId" } - }, - "additionalProperties": false, - "required": [ "cellId" ] - } - ] - }, - - "lbObjectives": { - "anyOf": [ - { - "type": "object", - "properties": { - "dlLbObjective": { "$ref": "#/$defs/DlLbObjective" }, - "ulLbObjective": { "$ref": "#/$defs/UlLbObjective" } - }, - "maxProperties": 2, - "additionalProperties": false, - "required": [ "dlLbObjective", "ulLbObjective" ] - }, - { - "type": "object", - "properties": { - "dlLbObjective": { "$ref": "#/$defs/DlLbObjective" } - }, - "maxProperties": 1, - "additionalProperties": false, - "required": [ "dlLbObjective" ] - } - ] - } - } -} -``` - -``` - - }, - { - "type": "object", - "properties": { - "ulLbObjective": { "$ref": "#/$defs/UlLbObjective" } - }, - "maxProperties": 1, - "additionalProperties": false, - "required": [ "ulLbObjective" ] - } - ] -}, - -"lbResources": { - "type": "object", - "properties": { - "cellIdList": { "$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellIdList" } - }, - "required": [ "cellIdList" ], - "additionalProperties": false -} -}, - -"additionalProperties": false, -"required": [ "scope", "lbResources", "lbObjectives" ], - -"$defs": { - "DlLbObjective": { - "type": "object", - "properties": { - "dlTargetPrbUsg": { - "type": "number", - "minimum": 0, - "maximum": 100 - }, - "dlPrbUsgType": { - "type": "number", - "minimum": 1, - "maximum": 4 - } - }, - "additionalProperties": false, - "required": [ "dlTargetPrbUsg", "dlPrbUsgType" ] - }, - "UlLbObjective": { - "type": "object", - "properties": { - "ulTargetPrbUsg": { - "type": "number", - "minimum": 0, - "maximum": 100 - }, - "ulPrbUsgType": { - "type": "number", - "minimum": 1, - "maximum": 4 - } - }, - "additionalProperties": false, - "required": [ "ulTargetPrbUsg", "ulPrbUsgType" ] - }, - - "https://schemas.o-ran.org/jsonschemas/altd/common_3.0.1": - - } -} - -``` - -### 7.2.9 Energy Savings - -#### 7.2.9.1 Policy type identifier - -PolicyTypeId: **ORAN\_EnergySaving\_3.0.2** - -#### 7.2.9.2 Rationale - -##### 7.2.9.2.1 Use case - -See Non-RT RIC & A1 interface: Use Cases and Requirements [1], clause 4.8. - -##### 7.2.9.2.2 Statements, restrictions and extensions - -An energy saving statement (i.e. esObjectives and/or esResources) can be applied together with ScopeIdentifier containing different combinations of identifiers. Not all combinations are relevant. The following table indicates combinations that are allowed. - -**Table 7.2.9.2.2-1: Allowed combinations of esObjectives / esResources statement with ScopeIdentifier** - -| ScopeIdentifier
Policy statement | ueId | groupId | qosId | talList | cellId | cellIdList | -|-------------------------------------|------|---------|-------|---------|--------|------------| -| esObjectives / esResources | 0 | 0 | 0 | 0 | 1 | 0 | -| esObjectives / esResources | 0 | 0 | 0 | 0 | 0 | 1 | -| esObjectives / esResources | 0 | 0 | 0 | 1 | 0 | 0 | - -NOTE 1: On each row is listed a combination of identifiers that is allowed for the indicated statement. Notation is the same as for cardinality: "0" means the identifier shall not occur, "0..1" means the identifier may occur and "1" means the identifier shall occur. Only at most one occurrence of an identifier is allowed in the present version. - -NOTE 2 : When ScopeIdentifier contains talList or cellIdList, and esResources is present, the cells indicated in esResources should be a subset of the cells implied by the ScopeIdentifier. - -#### 7.2.9.3 JSON schemas - -##### 7.2.9.3.1 Policy schema - -``` - -"$schema": "https://json-schema.org/draft/2020-12/schema", -"$id": "https://schemas.o-ran.org/jsonschemas/altd/oran_energysaving_3.0.2", -"description": "This module is for O-RAN standard Energy saving policy. -Copyright 2026 O-RAN ALLIANCE e.V. -Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); -You may not use this file except in compliance with the License. -You may obtain a copy of the License at https://www.o-ran.org/sccl", - -"type": "object", -"properties": { - "scope": { - "anyOf": [ - { - "type": "object", - "properties": { - "cellId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/CellId"} - }, - "additionalProperties": false, - "required": ["cellId"] - }, - ] - } -} - -``` - -``` - - { - "type": "object", - "properties": { - "cellIdList": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/CellIdList"} - }, - "additionalProperties": false, - "required": ["cellIdList"] - }, - { - "type": "object", - "properties": { - "taILList": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/TaILList"} - }, - "additionalProperties": false, - "required": ["taILList"] - } - ] -}, - -"esObjectives": { - "oneOf": [ - { - "type": "object", - "properties": { - "targetPeeEnergy": {"type": "integer"} - }, - "additionalProperties": false, - "required": ["targetPeeEnergy"] - }, - { - "type": "object", - "properties": { - "esPercentage": { - "type": "integer", - "minimum": 0, - "maximum": 100 - } - }, - "additionalProperties": false, - "required": ["esPercentage"] - } - ] -}, - -"esResources": { - "type": "array", - "items": {"$ref": "#/$defs/EsResource"}, - "minItems": 1 -} - -"additionalProperties": false, -"anyOf": [ - {"required": ["scope", "esObjectives"]}, - {"required": ["scope", "esResources"]} -], - -"$defs": { - "AvoidanceType": { - "type": "string", - "enum": [ - "AVOID", - "FORBID" - ] - }, - "EsResource": { - "oneOf": [ - { - "type": "object", - "properties": { - "operationalCells": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/CellIdList"}, - -``` - -``` - - "operationalPreference": {"$ref": "#/$defs/AvoidanceType"}, - "dlPrbUsage": {"type": "integer", "minimum": 0, "maximum": 100}, - "ulPrbUsage": {"type": "integer", "minimum": 0, "maximum": 100} - }, - "additionalProperties": false, - "required": ["operationalCells", "operationalPreference"] -}, -{ - "type": "object", - "properties": { - "coverageCells": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/CellIdList"}, - "coveragePreference": {"$ref": "#/$defs/AvoidanceType"}, - "dlPrbUsage": {"type": "integer", "minimum": 0, "maximum": 100}, - "ulPrbUsage": {"type": "integer", "minimum": 0, "maximum": 100} - }, - "additionalProperties": false, - "required": ["coverageCells", "coveragePreference"] -}, -{ - "type": "object", - "properties": { - "operationalCells": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/CellIdList"}, - "operationalPreference": {"$ref": "#/$defs/AvoidanceType"}, - "coverageCells": {"$ref": "/jschemas/altd/common_3.0.1#/$defs/CellIdList"}, - "coveragePreference": {"$ref": "#/$defs/AvoidanceType"}, - "dlPrbUsage": {"type": "integer", "minimum": 0, "maximum": 100}, - "ulPrbUsage": {"type": "integer", "minimum": 0, "maximum": 100} - }, - "additionalProperties": false, - "required": ["operationalCells", "operationalPreference", "coverageCells", "coveragePreference"] -} -] -}, -"https://schemas.o-ran.org/jschemas/altd/common_3.0.1": -} -} -} - -``` - -##### 7.2.9.3.2 Policy status schema - -The generic policy status schema in clause 7.1.2.2 is used. - -# 8 A1-EI data model - -## 8.1 Introduction - -This clause specifies the application data model supported by the A1-EI API specified in A1AP [3], clause 6.3. The purpose of the data model is to be the basis for - -- definition of EI types; and -- the EI representation objects that are transported in the body of the A1-EI procedures. - -There are two kinds of EI types: those defined by O-RAN and those defined by another entity. EI types need to define: - -- an EiTypeIdentifier for usage in the A1-EI procedures and URI structure; and -- the content to be transported in the body of the A1-EI procedures. - -The content is referred to as EI representation objects for the O-RAN defined EI types and is defined by using the A1-EI data model specified in this clause. An EI type defined outside of O-RAN may use the A1-EI data model or another model that covers the content corresponding to the schemas and objects. - -The present document covers the data model for O-RAN defined EI types. The O-RAN defined EI types are based on the statements and attributes defined in the data model and may extend it with EI type specific rules and attributes. - -The O-RAN defined EI types are defined based on JSON Schema [7]. An EI type is defined by four schemas for EI job definition, EI job constraints, EI job status and EI job result. The schemas are used to validate the EI representation objects transferred in the body of the A1-EI procedures. - -## 8.2 Simple data types and enumerations - -### 8.2.1 Simple data types - -The EI job contains URIs for EI job status notifications and EI job results. The simple data types for callback URIs are defined in table 8.2.1-1. - -**Table 8.2.1-1: General definition of simple data types for callback URIs** - -| Type Name | Type Definition | Description | Applicability | -|--------------------------|-----------------|--------------------------------------------|--------------------------------------------------------------------------------| -| JobStatusNotificationUri | string | target URI for EI job status notifications | provided in EI Job object and used in the Notify EI job notification procedure | -| JobResultUri | string | target URI for EI job results | provided in EI Job object and used in the Deliver EI job result procedure | - -The simple data type for JSON schemas is defined in table 8.2.1-2. - -**Table 8.2.1-2: Definition of JsonSchema** - -| Type Name | Type Definition | Description | Applicability | -|------------|---------------------------------------------------------------------------------------------------------|-----------------------------------------------------|---------------| -| JsonSchema | https://json-schema.org/draft/2020-12/schema | A JSON schema meta-schema following JSON Schema [7] | | - -### 8.2.2 Enumerations - -#### 8.2.2.1 JobStatusType - -The enumeration JobStatusType represents if an EI job is confirmed to deliver EI results. It shall comply with the provisions defined in table 8.2.2.1-1. - -**Table 8.2.2.1-1: Enumeration JobStatusType** - -| Enumeration value | Description | Applicability | -|-------------------|------------------------|--------------------------------------------------------------------| -| ENABLED | the EI Job is enabled | the A1-EI producer is able to deliver EI result for the EI Job | -| DISABLED | the EI Job is disabled | the A1-EI producer is not able to deliver EI result for the EI Job | - -#### 8.2.2.2 GadShapeType - -The enumeration GadShapeType represents the different types or shapes of geographic areas. It shall comply with the provisions defined in table 8.2.2.2-1. - -**Table 8.2.2.2-1: Enumeration GadShapeType** - -| Enumeration value | Description | Applicability | -|----------------------------|---------------------------------------------------------|---------------| -| POINT | Ellipsoid point | | -| POINT_UNCERTAINTY_CIRCLE | Ellipsoid point with uncertainty circle | | -| POINT_UNCERTAINTY_ELLIPSE | Ellipsoid point with uncertainty ellipse | | -| POLYGON | Polygon | | -| POINT_ALTITUDE | Ellipsoid point with altitude | | -| POINT_ALTITUDE_UNCERTAINTY | Ellipsoid point with altitude and uncertainty ellipsoid | | -| ELLIPSOID_ARC | Ellipsoid arc | | - -#### 8.2.2.3 VelocityDescType - -The enumeration VelocityDescType represents the different types of UE velocity descriptions. It shall comply with the provisions defined in table 8.2.2.3-1. - -**Table 8.2.2.3-1: Enumeration VelocityDescType** - -| Enumeration value | Description | Applicability | -|-------------------------|---------------------------------------------------|---------------| -| H_VELOCITY | Horizontal velocity | | -| HV_VELOCITY | Horizontal and vertical velocity | | -| H_VELOCITY_UNCERTAINTY | Horizontal velocity with uncertainty | | -| HV_VELOCITY_UNCERTAINTY | Horizontal and vertical velocity with uncertainty | | - -## 8.3 Structured data types - -### 8.3.1 ScopeIdentifier - -The ScopeIdentifier is EI type specific. - -If the ScopeIdentifier contains attributes corresponding to the A1 policy ScopeIdentifier, they are the same as defined for A1-P, see clause 6.3.1. - -### 8.3.2 Statements for EI job definition - -#### 8.3.2.1 Introduction - -This clause defines the structured data type and attributes to be used for EI job definition, which are summarized in table 8.3.2.1-1. - -**Table 8.3.2.1-1: Statements for EI job definition** - -| Data type | Clause defined | Description | Applicability | -|--------------------------|----------------|----------------------------------------------------------------|---------------| -| UeGeoandVelEIDescription | 8.3.2.2 | EI job definition for UE geo-location and velocity information | | - -#### 8.3.2.2 UE geo-location and velocity information - -The UeGeoandVelEIDescription statement contains the attributes defined in table 8.3.2.2-1: - -**Table 8.3.2.2-1: Definition of UEGeoandVelEIDescription** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-------------------------------------------------------------------------------------------|------------------|---|-------------|---------------------------------------------------------------------|---------------| -| gadShape | GadShapeType | M | 1 | GAD shapes used for UE geo-location information, see clause 8.2.2.2 | | -| velocityDesc | VelocityDescType | O | 1 | Type of description for UE velocity information, see clause 8.2.2.3 | | -| granularityPeriod | integer | M | 1 | Interval of periodic measurement in milliseconds | | -| reportingPeriod | integer | M | 1 | Interval of periodic reporting in milliseconds | | -| reportingAmount | integer | M | 1 | Number of periodic reports | | -| NOTE: Event-triggered measurement and reporting is not specified in the present document. | | | | | | - -### 8.3.3 Statements for EI job result - -#### 8.3.3.1 Introduction - -This clause defines the structured data type and attributes to be used for EI job result definition, which are summarized in table 8.3.3.1-1. - -**Table 8.3.3.1-1: Statements for EI job result definition** - -| Data type | Clause defined | Description | Applicability | -|---------------------|----------------|-----------------------------------------------------------------------|---------------| -| UeGeoandVelEIResult | 8.3.3.2 | EI job result definition for UE geo-location and velocity information | | - -#### 8.3.3.2 UE geo-location and velocity EI - -The UEGeoandVelEIResult statement contains the attributes defined in table 8.3.3.2-1: - -**Table 8.3.3.2-1: Definition of UEGeoandVelEIResult** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------------------------------------------------------------------------------------------------------------|------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------|---------------| -| timeStamp | DateTime | M | 1 | Indicates the UTC time corresponding to the UE geo-location and velocity enrichment information, see 3GPP TS 29.571 [5], clause 5.2.2. | | -| ueId | Ueld | M | 1 | UE identifier, see clause 6.3.1.7. | | -| gadShape | GadShapeType | M | 1 | GAD shapes used for UE geo-location information, see clause 8.2.2.2 | | -| geoLocation | GeoLocationType | M | 1 | Indicates the UE geo-location enrichment information, see table 8.3.2.2-2 | | -| velocityDesc | VelocityDescType | O | 0..1 | Type of description for UE velocity information, see clause 8.2.2.3 | | -| velocity | VelocityType | C | 0..1 | Indicates the UE velocity enrichment information, see table 8.3.2.2-3 | | -| NOTE: Presence condition "C" means that the attribute shall be included if the attribute "velocityDesc" is included. | | | | | | - -The GeoLocationType is defined in table 8.3.2.2-2 as a list of following mutually exclusive alternatives. - -**Table 8.3.2.2-2: Definition of GeoLocationType** - -| Data type | Cardinality | Discriminator name | Discriminator mapping | Description | -|--------------------------|-------------|--------------------|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------| -| Point | 1 | gadShape | POINT | Geolocation consisting of a single ellipsoid point, represented by its longitude and latitude, see 3GPP TS 29.572 [20], clause 6.1.6.2.6 | -| PointUncertaintyCircle | 1 | gadShape | POINT_UNCERTAINTY_CIRCLE | Geolocation consisting of a point and an uncertainty value, see 3GPP TS 29.572 [20], clause 6.1.6.2.7 | -| PointUncertaintyEllipse | 1 | gadShape | POINT_UNCERTAINTY_ELLIPSE | Geolocation consisting of a point and an uncertainty ellipse, see 3GPP TS 29.572 [20], clause 6.1.6.2.8 | -| Polygon | 1 | gadShape | POLYGON | Geolocation consisting of a list of points, see 3GPP TS 29.572 [20], clause 6.1.6.2.9 | -| PointAltitude | 1 | gadShape | POINT_ALTITUDE | Geolocation consisting of a point and an altitude value, see 3GPP TS 29.572 [20], clause 6.1.6.2.10 | -| PointAltitudeUncertainty | 1 | gadShape | POINT_ALTITUDE_UNCERTAINTY | Geolocation consisting of a point, an altitude value, and an uncertainty value, see 3GPP TS 29.572 [20], clause 6.1.6.2.11 | -| EllipsoidArc | 1 | gadShape | ELLIPSOID_ARC | Geolocation consisting of an ellipsoid arc, see 3GPP TS 29.572 [20], clause 6.1.6.2.12 | - -The VelocityType is defined in table 8.3.2.2-3 as a list of following mutually exclusive alternatives. - -**Table 8.3.2.2-3: Definition of VelocityType** - -| Data type | Cardinality | Discriminator name | Discriminator mapping | Description | -|----------------------------------------------|-------------|--------------------|-------------------------|---------------------------------------------------------------------------------------------------------------------| -| HorizontalVelocity | 1 | velocityDesc | H_VELOCITY | Horizontal velocity, see 3GPP TS 29.572 [20], clause 6.1.6.2.18 | -| HorizontalWithVerticalVelocity | 1 | velocityDesc | HV_VELOCITY | Horizontal velocity and vertical velocity, see 3GPP TS 29.572 [20], clause 6.1.6.2.19 | -| HorizontalVelocityWithUncertainty | 1 | velocityDesc | H_VELOCITY_UNCERTAINTY | Horizontal velocity with a speed uncertainty value, see 3GPP TS 29.572 [20], clause 6.1.6.2.20 | -| HorizontalWithVerticalVelocityAndUncertainty | 1 | velocityDesc | HV_VELOCITY_UNCERTAINTY | Horizontal velocity and vertical velocity with speed uncertainty values, see 3GPP TS 29.572 [20], clause 6.1.6.2.21 | - -### 8.3.4 Statements for EI job constraints - -#### 8.3.4.1 Introduction - -This clause defines the structured data type and attributes to be used for EI job constraints. Table 8.3.4.1-1 specifies the statements that can be used for EI job constraints. - -**Table 8.3.4.1-1: Statements for EI job constraints** - -| Data type | Clause defined | Description | Applicability | -|--------------------------|----------------|-----------------------------------------------------------------|---------------| -| UEGeoandVelEIConstraints | 8.3.4.2 | EI job constraints for UE geo-location and velocity information | | - -#### 8.3.4.2 UE geo-location and velocity information - -The UEGeoandVelEIConstraints contains the attributes defined in table 8.3.4.2-1: - -**Table 8.3.4.2-1: Definition of UEGeoandVelEIConstraints** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|------------------------|-------------------------|---|-------------|--------------------------------------------------------------------------------|---------------| -| supportedGadShapes | array(GadShapeType) | M | 1..N | Indicates supported GAD shapes to describe UE geo-location, see clause 8.2.2.2 | | -| supportedVelocityDescs | array(VelocityDescType) | O | 1..N | Indicates supported types of UE velocity description, see clause 8.2.2.3 | | - -## 8.4 EI representations objects - -### 8.4.1 EI type object - -The EI type object can be empty or contain EI type specific information. - -An EiTypeObject is based on IETF RFC 8259 [6] and can contain: - -- one JSON schema for EiJobDefinition; -- one JSON schema for EiJobStatusObject; -- one JSON schema for EiJobResultObject; or -- one JSON schema for EiJobConstraintsObject. - -The type EiTypeObject is defined in table 8.4.1-1. - -**Table 8.4.1-1: General definition of EiTypeObject** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|------------------------|------------|---|-------------|----------------------------------|---------------| -| eiJobDefinitionSchema | JsonSchema | O | 0..1 | The schemas are EI type specific | | -| eiJobStatusSchema | JsonSchema | O | 0..1 | | | -| eiJobResultSchema | JsonSchema | O | 0..1 | | | -| eiJobConstraintsSchema | JsonSchema | O | 0..1 | | | - -NOTE 1: Clause 9.2 contains definitions and EI type specific schemas for O-RAN defined A1 EI types. -NOTE 2: The eiJobDefinitionSchema attribute shall contain the compound EI job definition schema as described in clause 9.1.2.2. - -The JSON schema for an EiJobDefinition is used by the A1-EI Consumer to formulate an EI job definition and by the A1-EI Producer to validate an EiJobObject during Create EI job and Update EI job procedures. - -The JSON schema for an EiJobConstraintsObject is used by the A1-EI Producer to formulate EI job constraints and by the A1-EI Consumer to validate an EiJobConstraintsObject that is considered when formulating an EI job definition. - -The JSON schema for an EiJobStatusObject is used by the A1-EI Producer to formulate EI job status and by the A1-EI Consumer to validate an EiJobStatusObject during Query EI job status and Notify EI job status procedures. - -The JSON schema for an EiJobResultObject is used by the A1-EI Producer to formulate EI job results and by the A1-EI Consumer to validate an EiJobResultObject during Deliver EI job result procedures. - -The EiTypeObject and the EiJobConstraintsObject can be retrieved using the Query EI type procedure. - -### 8.4.2 EI job object - -#### 8.4.2.1 General - -An EiJobObject is based on IETF RFC 8259 [6] and contains: - -- one EI type identifier; -- one target URI for EI Job results; and -- one EI type specific job definition containing one or more EI job definition statements. - -and optionally - -- one target URI for EI Job status notifications. - -The type EiJobObject is defined in table 8.4.2-1. - -**Table 8.4.2-1: General definition of EIJobObject** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---|-------------|--------------------|------------------| -| eiTypeId | string | M | 1 | EI type identifier | EI type specific | -| jobResultUri | string | M | 1 | See clause 8.2.1 | | -| jobStatusNotificationUri | string | O | 0..1 | See clause 8.2.1 | | -| jobDefinition | JobDefinition | M | 1 | See clause 8.3.2 | EI type specific | -| NOTE: Presence condition "M" means that the data type shall be included in an EI job object for EI types based on the present document. Additional attributes may be defined for a specific EI type. | | | | | | - -This definition is general and indicates how to formally construct an EiJobObject. The EI types in clause 9.2 define EI type identifiers and schemas for EI job definitions. - -The EI job definition is related to the EI job results, i.e., it can express which of the possible EI job result attributes that should be delivered based on the EI job. - -#### 8.4.2.2 Allowed combinations - -A job definition statement can be applied together with a ScopeIdentifier containing different combinations of identifiers attributes. Not all combinations are relevant and different combinations are relevant for different EI types (see clause 9). - -### 8.4.3 EI job status object - -An EiJobStatus object is based on IETF RFC 8259 [6] and always contains: - -- one EI job status attribute. - -**Table 8.4.3-1: General definition of EIJobStatusObject** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|---|-------------|-------------|------------------------------------------| -| jobStatus | JobStatusType | M | 1 | See 8.2.2 | statement indicating status of an EI job | -| NOTE: Presence condition "M" means that the data type shall be included in an EI job status object for EI types based on the present document. Additional attributes may be defined for a specific EI type. | | | | | | - -### 8.4.4 EI job result object - -An EiJobResult object is based on IETF RFC 8259 [6] and it contains - -- one or more EI job result statements. - -### 8.4.5 EI job constraints object - -An EiJobConstraintsObject is based on IETF RFC 8259 [6] and it contains - -- one or more EI job constraints statements. - -The content is related to the EI job definition, i.e.; it can express capabilities and limitations related to supported attributes and value ranges for EI job result attributes, and EI job production and delivery attributes. - -## 8.5 Binary data - -Binary data is not applicable in this version of the present document. - -# 9 A1-EI data types (EI types) - -## 9.1 Introduction - -### 9.1.1 Identification and compatibility of EI types - -An EI type is identified by a EiTypeId as defined in A1AP [3], clause 6.3.3.1.3. The EiTypeId is a string that consists of two parts: a typename and a version. - -When updating an EI type, the version in the EiTypeId is updated according to SemVer [19] to reflect its compatibility with other EI types that has the same typename. - -Two EI types are considered as different if the EiTypeId is different, i.e. even if the typename is the same and the version only differs in the patch version digit. - -Two EI types are compatible in case the typename is the same and the major version digit in the version is the same. In general, two EI types X and Y are compatible when all objects that can be created based on EI type X can be validated by the schemas for EI type Y and all objects that can be created based on EI type Y can be validated by the schemas for EI type X. - -### 9.1.2 Common definitions - -#### 9.1.2.1 EI job status - -This is a generic EI job status schema, it may be adjusted and used together with an EI job schema in an EiTypeObject and will then be identified by the same EI type identifier as the EI job schema. - -``` -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "description": "This module is for O-RAN standard EI status. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at https://www.o-ran.org/sccl", - - "type": "object", - "properties": { - "jobStatus": { - "type": "string", - "enum": [ - "ENABLED", - "DISABLED" - ] - } - }, - "additionalProperties": false, - "required": ["jobStatus"] -} -``` - -If an EI type specific status schema contains additional attributes, they are included based on the structure of the generic schema. - -#### 9.1.2.2 Scope identifiers and common data types - -The EI job definition schemas defined in clause 9.2 can be base schemas that embed a subschema with common data types definitions in same way as described for policy types in clause 7.1. - -An EI type definition can link to the common data types schema defined in clause 7.1.2.1 and the compatibility relations are the same as for A1 policy types as described in Annex C. The EI types defined in the present document link to the version of the common data types schema defined in the present document. - -It is the compound EI job definition schemas that are identified by the EI type identifier and included in the EiTypeObject specified in clause 8.4.1. - -#### 9.1.2.3 Schema identification - -The EI type identifier is part of the \$id keyword included in the EI job definition schema. - -The \$id keyword for the EI job definition schemas are constructed from the URI base and the EI type identifier in the same was as for policy types as described in clause 7.1.3.2. The base URI for EI types is the same as for policy types. - -## 9.2 EI type definitions - -### 9.2.1 UE location and velocity information - -#### 9.2.1.1 EI type identifier - -EiTypeId: **ORAN\_UEGeoandVel\_5.0.1** - -#### 9.2.1.2 Rationale - -##### 9.2.1.2.1 Use case - -See Non-RT RIC and A1/R1 interface: Use Cases and Requirements [1], clauses 4.4, 4.5, and 4.7. - -##### 9.2.1.2.2 Statements, restrictions and extensions - -A UEGeoandVelEIDescription statement can be applied together with ScopeIdentifier containing different combinations of identifiers. Not all combinations are relevant. Table 9.2.1.2.2-1 indicates the combinations that are allowed. - -**Table 9.2.1.2.2-1: Allowed combinations of UEGeoandVelEIDescription with ScopeIdentifier** - -| ScopeIdentifier | ueId | groupId | sliceId | qosId | cellId | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|---------|---------|-------|--------| -| UEGeoandVelEIDescription | 1 | 0 | 0 | 0 | 0 | -| NOTE 1: on each row is listed a combination of identifiers that is allowed for the indicated statement. Notation is the same as for cardinality: "0" means the identifier shall not occur and "1" means the identifier shall occur. | | | | | | -| NOTE 2: A single UE identifier is allowed in the scope of the present document. Whether the scope for UEGeoandVelEIDescription statement can be extended to a group of UEs, UEs in a slice, or UEs in a cell is For Further Study. | | | | | | - -#### 9.2.1.3 JSON schemas - -##### 9.2.1.3.1 EI job definition schema - -``` -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "$id": "https://schemas.o-ran.org/jsonschemas/altd/oran_uegeoandvel_5.0.1", - "description": "This module is for O-RAN standard UE geo-location and velocity EI job definition. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at https://www.o-ran.org/sccl", - "type": "object", -``` - -``` - -"properties": { - - "scope": { - "type": "object", - "properties": { - "ueId": {"$ref": "/jsonschemas/altd/common_3.0.1#/$defs/UeId"} - }, - "additionalProperties": false, - "required": ["ueId"] - }, - - "ueGeoandVelEIDescription": { - "type": "object", - "properties": { - "gadShape": {"$ref": "#/$defs/GadShapeType"}, - "granularityPeriod": { - "type": "number", - "minimum": 1, - "maximum": 60000 - }, - "reportingPeriod": { - "type": "number", - "minimum": 1, - "maximum": 60000 - }, - "reportingAmount": { - "type": "number", - "minimum": 1, - "maximum": 3600000 - }, - "velocityDesc": {"$ref": "#/$defs/VelocityDescType"} - }, - "required": ["gadShape", "granularityPeriod", "reportingPeriod", "reportingAmount"], - "additionalProperties": false - } -}, - -"additionalProperties": false, -"required": ["scope", "ueGeoandVelEIDescription"], - -"$defs": { - "GadShapeType": { - "type": "string", - "enum": [ - "POINT", - "POINT_UNCERTAINTY_CIRCLE", - "POINT_UNCERTAINTY_ELLIPSE", - "POLYGON", - "POINT_ALTITUDE", - "POINT_ALTITUDE_UNCERTAINTY", - "ELLIPSOID_ARC" - ] - }, - "VelocityDescType": { - "type": "string", - "enum": [ - "H_VELOCITY", - "HV_VELOCITY", - "H_VELOCITY_UNCERTAINTY", - "HV_VELOCITY_UNCERTAINTY" - ] - }, - "https://schemas.o-ran.org/jsonschemas/altd/common_3.0.1": - -} -} - -``` - -##### 9.2.1.3.2 El job constraints schema - -``` -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "description": "This module is for O-RAN standard UE geo-location and velocity EI job constraints. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at https://www.o-ran.org/sccl", - - "type": "object", - "properties": { - - "ueGeoandVelEIConstraints": { - "type": "object", - "properties": { - "supportedGadShapes": { - "type": "array", - "items": { - "$ref": "#/$defs/GadShapeType" - }, - "minItems": 1 - }, - "supportedVelocityDescs": { - "type": "array", - "items": { - "$ref": "#/$defs/VelocityDescType" - }, - "minItems": 1 - } - }, - "required": ["supportedGadShapes"], - "additionalProperties": false - } - }, - - "additionalProperties": false, - "required": ["ueGeoandVelEIConstraints"], - - "$defs": { - "GadShapeType": { - "type": "string", - "enum": [ - "POINT", - "POINT_UNCERTAINTY_CIRCLE", - "POINT_UNCERTAINTY_ELLIPSE", - "POLYGON", - "POINT_ALTITUDE", - "POINT_ALTITUDE_UNCERTAINTY", - "ELLIPSOID_ARC" - ] - }, - "VelocityDescType": { - "type": "string", - "enum": [ - "H_VELOCITY", - "HV_VELOCITY", - "H_VELOCITY_UNCERTAINTY", - "HV_VELOCITY_UNCERTAINTY" - ] - } - } -} -``` - -##### 9.2.1.3.3 El job status schema - -The generic EI job status schema in clause 9.1.2.1 is used. - -##### 9.2.1.3.4 El job result schema - -``` -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "description": "This module is for O-RAN standard UE geo-location and velocity EI job results. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); - You may not use this file except in compliance with the License. - You may obtain a copy of the License at https://www.o-ran.org/sccl", - - "type": "array", - "items": { - "$ref": "#/$defs/UEGeoandVeleEIResult" - }, - "minItems": 1, - - "$defs": { - "UEGeoandVeleEIResult": { - "type": "object", - "properties": { - "timeStamp": { "$ref": "#/$defs/DateTime" }, - "ueId": { "$ref": "/jsonschemas/altd/common_3.0.1#/$defs/UeId" }, - "gadShape": { "$ref": "#/$defs/GadShapeType" }, - "velocityDesc": { "$ref": "#/$defs/VelocityDescType" } - }, - "allOf": [ - { - "if": { - "properties": { "gadShape": { "const": "POINT" } } - }, - "then": { - "properties": { "geoLocation": { "$ref": "#/$defs/Point" } } - } - }, - { - "if": { - "properties": { "gadShape": { "const": "POINT_UNCERTAINTY_CIRCLE" } } - }, - "then": { - "properties": { "geoLocation": { "$ref": "#/$defs/PointUncertaintyCircle" } } - } - }, - { - "if": { - "properties": { "gadShape": { "const": "POINT_UNCERTAINTY_ELLIPSE" } } - }, - "then": { - "properties": { "geoLocation": { "$ref": "#/$defs/PointUncertaintyEllipse" } } - } - }, - { - "if": { - "properties": { "gadShape": { "const": "POLYGON" } } - }, - "then": { - "properties": { "geoLocation": { "$ref": "#/$defs/Polygon" } } - } - }, - { - "if": { - "properties": { "gadShape": { "const": "POINT_ALTITUDE" } } - }, - "then": { - "properties": { "geoLocation": { "$ref": "#/$defs/PointAltitude" } } - } - }, - { - "if": { - "properties": { "gadShape": { "const": "POINT_ALTITUDE_UNCERTAINTY" } } - }, - "then": { - -``` - -``` - - "properties": { "geoLocation": { "$ref": "#/$defs/PointAltitudeUncertainty" } } - } -}, -{ - "if": { - "properties": { "gadShape": { "const": "ELLIPSOID_ARC" } } - }, - "then": { - "properties": { "geoLocation": { "$ref": "#/$defs/EllipsoidArc" } } - } -}, -{ - "if": { - "properties": { "velocityDesc": { "const": "H_VELOCITY" } }, - "required": ["velocityDesc"] - }, - "then": { - "properties": { "velocity": { "$ref": "#/$defs/HorizontalVelocity" } } - } -}, -{ - "if": { - "properties": { "velocityDesc": { "const": "HV_VELOCITY" } }, - "required": ["velocityDesc"] - }, - "then": { - "properties": { - "velocity": { "$ref": "#/$defs/HorizontalWithVerticalVelocity" } - } - } -}, -{ - "if": { - "properties": { "velocityDesc": { "const": "H_VELOCITY_UNCERTAINTY" } }, - "required": ["velocityDesc"] - }, - "then": { - "properties": { - "velocity": { "$ref": "#/$defs/HorizontalVelocityWithUncertainty" } - } - } -}, -{ - "if": { - "properties": { "velocityDesc": { "const": "HV_VELOCITY_UNCERTAINTY" } }, - "required": ["velocityDesc"] - }, - "then": { - "properties": { - "velocity": { "$ref": "#/$defs/HorizontalWithVerticalVelocityAndUncertainty" } - } - } -} -], -"required": ["timeStamp", "ueId", "gadShape", "geoLocation"] -}, -{ - "DateTime": { - "type": "string", - "format": "date-time" - }, - "GadShapeType": { - "type": "string", - "enum": [ - "POINT", - "POINT_UNCERTAINTY_CIRCLE", - "POINT_UNCERTAINTY_ELLIPSE", - "POLYGON", - "POINT_ALTITUDE", - "POINT_ALTITUDE_UNCERTAINTY", - "ELLIPSOID_ARC" - ] - } -] - -``` - -``` - -}, -"VelocityDescType": { - "type": "string", - "enum": [ - "H_VELOCITY", - "HV_VELOCITY", - "H_VELOCITY_UNCERTAINTY", - "HV_VELOCITY_UNCERTAINTY" - ] -}, -"Point": { - "type": "object", - "properties": { - "lon": { - "type": "number", - "minimum": -180, - "maximum": 180 - }, - "lat": { - "type": "number", - "minimum": -90, - "maximum": 90 - } - }, - "required": ["lon", "lat"] -}, -"PointUncertaintyCircle": { - "type": "object", - "properties": { - "point": { "$ref": "#/$defs/Point" }, - "uncertainty": { "$ref": "#/$defs/Uncertainty" } - }, - "required": ["point", "uncertainty"] -}, -"PointUncertaintyEllipse": { - "type": "object", - "properties": { - "point": { "$ref": "#/$defs/Point" }, - "uncertaintyEllipse": { "$ref": "#/$defs/UncertaintyEllipse" }, - "confidence": { "$ref": "#/$defs/Confidence" } - }, - "required": ["point", "uncertainty", "confidence"] -}, -"Polygon": { - "type": "array", - "items": { - "$ref": "#/$defs/Point" - }, - "minItems": 3, - "maxItems": 15 -}, -"PointAltitude": { - "type": "object", - "properties": { - "point": { "$ref": "#/$defs/Point" }, - "altitude": { "$ref": "#/$defs/Altitude" } - }, - "required": ["point", "altitude"] -}, -"PointAltitudeUncertainty": { - "type": "object", - "properties": { - "point": { "$ref": "#/$defs/Point" }, - "altitude": { "$ref": "#/$defs/Altitude" }, - "uncertaintyEllipse": { "$ref": "#/$defs/UncertaintyEllipse" }, - "uncertaintyAltitude": { "$ref": "#/$defs/Uncertainty" }, - "confidence": { "$ref": "#/$defs/Confidence" } - }, - "required": ["point", "altitude", "uncertaintyEllipse", "uncertaintyAltitude", "confidence"] -}, -"EllipsoidArc": { - "type": "object", - -``` - -``` - -"properties": { - "point": { "$ref": "#/$defs/Point" }, - "innerRadius": { "$ref": "#/$defs/InnerRadius" }, - "uncertaintyRadius": { "$ref": "#/$defs/Uncertainty" }, - "offsetAngle": { "$ref": "#/$defs/Angle" }, - "includeAngle": { "$ref": "#/$defs/Angle" }, - "confidence": { "$ref": "#/$defs/Confidence" } -}, -"required": [ - "point", - "innerRadius", - "uncertaintyRadius", - "offsetAngle", - "includeAngle", - "confidence" -] -}, -"HorizontalVelocity": { - "type": "object", - "properties": { - "hSpeed": { "$ref": "#/$defs/HorizontalSpeed" }, - "bearing": { "$ref": "#/$defs/Angle" } - }, - "required": ["hSpeed", "bearing"] -}, -"HorizontalWithVerticalVelocity": { - "type": "object", - "properties": { - "hSpeed": { "$ref": "#/$defs/HorizontalSpeed" }, - "bearing": { "$ref": "#/$defs/Angle" }, - "vSpeed": { "$ref": "#/$defs/VerticalSpeed" }, - "vDirection": { "$ref": "#/$defs/VerticalDirection" } - }, - "required": ["hSpeed", "bearing", "vSpeed", "vDirection"] -}, -"HorizontalVelocityWithUncertainty": { - "type": "object", - "properties": { - "hSpeed": { "$ref": "#/$defs/HorizontalSpeed" }, - "bearing": { "$ref": "#/$defs/Angle" }, - "hUncertainty": { "$ref": "#/$defs/SpeedUncertainty" } - }, - "required": ["hSpeed", "bearing", "hUncertainty"] -}, -"HorizontalWithVerticalVelocityAndUncertainty": { - "type": "object", - "properties": { - "hSpeed": { "$ref": "#/$defs/HorizontalSpeed" }, - "bearing": { "$ref": "#/$defs/Angle" }, - "vSpeed": { "$ref": "#/$defs/VerticalSpeed" }, - "vDirection": { "$ref": "#/$defs/VerticalDirection" }, - "hUncertainty": { "$ref": "#/$defs/SpeedUncertainty" }, - "vUncertainty": { "$ref": "#/$defs/SpeedUncertainty" } - }, - "required": ["hSpeed", "bearing", "vSpeed", "vDirection", "hUncertainty", "vUncertainty"] -}, -"Uncertainty": { - "type": "number", - "minimum": 0 -}, -"UncertaintyEllipse": { - "type": "object", - "properties": { - "semiMajor": { "$ref": "#/$defs/Uncertainty" }, - "semiMinor": { "$ref": "#/$defs/Uncertainty" }, - "orientationMajor": { "$ref": "#/$defs/Orientation" } - }, - "required": ["semiMajor", "semiMinor", "orientationMajor"] -}, -"Orientation": { - "type": "integer", - "minimum": 0, - -``` - -``` - "maximum": 100 - }, - "Confidence": { - "type": "number", - "minimum": 0, - "maximum": 100 - }, - "Altitude": { - "type": "number", - "minimum": -32767, - "maximum": 32767 - }, - "InnerRadius": { - "type": "integer", - "minimum": 0, - "maximum": 327675 - }, - "Angle": { - "type": "integer", - "minimum": 0, - "maximum": 360 - }, - "HorizontalSpeed": { - "type": "number", - "minimum": 0, - "maximum": 2047 - }, - "VerticalSpeed": { - "type": "number", - "minimum": 0, - "maximum": 255 - }, - "VerticalDirection": { - "type": "string", - "enum": [ - "UPWARD", - "DOWNWARD" - ] - }, - "SpeedUncertainty": { - "type": "number", - "minimum": 0, - "maximum": 255 - }, - "$ref": "https://schemas.o-ran.org/jsonschemas/altd/common_3.0.1": -} -} -} -``` - -# Annex A (Informative): Policy examples - -## A.1 Generic scope identifier - -### A.1.0 General - -These are examples of policies that illustrate the usage of the generic ScopeIdentifier definitions in clause 7.1.2.1. - -### A.1.1 RAN UE ID based generic scope identifier - -``` -{ - "scope": { - "ueId": { - "guRanUeId": { "globalGnbId": { "plmnId": { "mcc": "123", "mnc": "45" }, - "gnbId": { "gnbIdLength": 25, "gnbIdValue": 6028163 } }, - "ranUeId": "1234567890ABCDEF" } - }, - "groupId": { - "spId": 123 - }, - "sliceId": { - "sst": 123, "sd": "456DEF", "plmnId": { "mcc": "123", "mnc": "45" } - }, - "qosId": { - "5qi": 123 - }, - "cellId": { - "plmnId": { "mcc": "123", "mnc": "45" }, "cId": { "nci": 12345678901 } - } - } -} -``` - -### A.1.2 AMF UE NGAP ID based generic scope identifier - -``` -{ - "scope": { - "ueId": { - "guAmfUeNgapId": { "guAmf": { - "plmnId": { "mcc": "123", "mnc": "45" }, "amfRegionId": "48", "amfSetId": "001", "amfPointer": "12" }, - "amfUeNgapId": 100 } - }, - "groupId": { - "spId": 123 - }, - "sliceId": { - "sst": 123, "sd": "456DEF", "plmnId": { "mcc": "123", "mnc": "45" } - }, - "qosId": { - "5qi": 123 - }, - } -} -``` - -``` - - "cellId": { - "plmnId": {"mcc":"123", "mnc":"45"}, "cId": {"ncI": 12345678901} - } - } -} - -``` - -### A.1.3 MME UE S1AP ID based generic scope identifier - -``` - -{ - "scope": { - "ueId": { - "guMmeUeS1apId": {"guMmeI": { - "plmnId": {"mcc":"123", "mnc":"45"}, "mmeGroupId": "1111", "mmeCode": "11"}, - "mmeUeS1apId": 100} - }, - "groupId": { - "spId": 123 - }, - "sliceId": { - "sst": 123, "sd": "456DEF", "plmnId": {"mcc":"123", "mnc":"45"} - }, - "qosId": { - "5qi": 123 - }, - "cellId": { - "plmnId": {"mcc":"123", "mnc":"45"}, "cId": {"ncI": 12345678901} - } - } -} - -``` - -### A.1.4 gNB-CU UE F1AP ID based generic scope identifier - -``` - -{ - "scope": { - "ueId": { - "guGnbCuUeF1apId": {"globalGnbId": { - "plmnId": {"mcc":"123", "mnc":"45"}, "gnbId": {"gnbIdLength": 25, "gnbIdValue": 6028163}}, - "gnbCuUeF1apId": 100} - }, - "groupId": { - "spId": 123 - }, - "sliceId": { - "sst": 123, "sd": "456DEF", "plmnId": {"mcc":"123", "mnc":"45"} - }, - "qosId": { - "5qi": 123 - }, - "cellId": { - "plmnId": {"mcc":"123", "mnc":"45"}, "cId": {"ncI": 12345678901} - } - } -} - -``` - -### A.1.5 gNB-CU-CP UE E1AP ID based generic scope identifier - -``` -{ - "scope": { - "ueId": { - "guGnbCuCpUeElapId": { "globalGnbId": { - "plmnId": { "mcc": "123", "mnc": "45" }, "gnbId": { "gnbIdLength": 25, "gnbIdValue": 6028163 } }, - "gnbCuCpUeElapId": 100 } - }, - "groupId": { - "spId": 123 - }, - "sliceId": { - "sst": 123, "sd": "456DEF", "plmnId": { "mcc": "123", "mnc": "45" } - }, - "qosId": { - "5qi": 123 - }, - "cellId": { - "plmnId": { "mcc": "123", "mnc": "45" }, "cId": { "nci": 12345678901 } - } - } -} -``` - -### A.1.6 eNB UE X2AP ID based scope identifier - -``` -{ - "scope": { - "ueId": { - "guEnbUeX2apId": { - "globalEnbId": { - "plmnId": { "mcc": "123", "mnc": "45" }, - "enbId": { "macroEnbId": "11111" } }, - "enbUeX2apId": 100 } - }, - "sliceId": { - "sst": 123, "sd": "456DEF", "plmnId": { "mcc": "123", "mnc": "45" } - }, - "qosId": { - "5qi": 123 - }, - "cellId": { - "plmnId": { "mcc": "123", "mnc": "45" }, "cId": { "nci": 12345678901 } - } - } -} -``` - -### A.1.7 M-NG-RAN node UE XnAP ID based scope identifier - -``` -{ - "scope": { - "ueId": { - "guNgRanNodeUeXnapUeId": { - "globalNgRanNodeId": { "globalNgEnbId": { - "plmnId": { "mcc": "123", "mnc": "45" }, - "ngEnbId": { "macroNgEnbId": "12111" } } }, - "ngRanNodeUeXnapId": 100321 } - } - } -} -``` - -``` - - }, - "sliceId": { - "sst": 123, "sd": "456DEF", "plmnId": {"mcc":"123", "mnc":"45"} - }, - "qosId": { - "5qi": 123 - }, - "cellId": { - "plmnId": {"mcc":"123", "mnc":"45"}, "cId": {"nci": 12345678901} - } - } -} - -``` - -## A.2 QoS (Quality of Service) - -### A.2.1 QoS based resource optimization per-UE - -``` - -{ - "scope": { - "ueId": { - "guRanUeId": {"globalGnbId": { - "plmnId": {"mcc":"123", "mnc":"45"}, "gnbId": {"gnbIdLength": 25, "gnbIdValue": 6028163}}, - "ranUeId": "0000000000000855" - } - }, - "qosId": { - "5qi": 67 - } - }, - "qosObjectives": { - "priorityLevel": 50 - } -} - -``` - -### A.2.2 QoS based resource optimization per-slice - -``` - -{ - "scope": { - "sliceId": { - "sst": 11, "sd": "456DEF", "plmnId": {"mcc":"248", "mnc":"35"}}, - "qosId": { - "5qi": 67 - }, - "cellId": { - "plmnId": {"mcc":"248", "mnc":"35"}, "cId": { "nci": 24} - } - }, - "qosObjectives": { - "gfbr": 1000, - "mfbr": 500, - "pdb": 120 - } -} - -``` - -## A.3 QoE (Quality of Experience) - -### A.3.1 QoE based resource optimization per-UE - -``` -{ - "scope": { - "ueId": { - "guRanUeId": { "globalGnbId": { - "plmnId": { "mcc": "123", "mnc": "45" }, "gnbId": { "gnbIdLength": 25, "gnbIdValue": 6028163 } }, - "ranUeId": "0000000000000855" } - }, - "qosId": { - "5qi": 67 - } - }, - - "qoeObjectives": { - "initialBuffering": 30, - "reBuffFreq": 5, - "stallRatio": 2 - } -} -``` - -### A.3.2 QoE based resource optimization per-slice - -``` -{ - "scope": { - "sliceId": { - "sst": 11, "sd": "456DEF", "plmnId": { "mcc": "248", "mnc": "35" } } - }, - - "qoeObjectives": { - "qoeScore": 4.25 - } - } -} -``` - -## A.4 TSP (Traffic Steering Preferences) - -### A.4.1 Traffic steering per-UE - -``` -{ - "scope": { - "ueId": { - "guRanUeId": { "globalGnbId": { - "plmnId": { "mcc": "248", "mnc": "35" }, "gnbId": { "gnbIdLength": 25, "gnbIdValue": 6028163 } }, - "ranUeId": "0000000000000855" } - } - }, - - "tspResources": [ - { - "cellIdList": [ - { "plmnId": { "mcc": "248", "mnc": "35" }, "cId": { "ncI": 39 } }, - { "plmnId": { "mcc": "248", "mnc": "35" }, "cId": { "ncI": 40 } } - ], - "preference": "PREFER" - }, - { - "cellIdList": [ - { "plmnId": { "mcc": "248", "mnc": "35" }, "cId": { "ncI": 81 } }, - { "plmnId": { "mcc": "248", "mnc": "35" }, "cId": { "ncI": 82 } }, - { "plmnId": { "mcc": "248", "mnc": "35" }, "cId": { "ncI": 83 } } - ], - } - ] -} -``` - -``` - - "preference": "FORBID" - } -] -} - -``` - -### A.4.2 Traffic steering per-slice - -``` - -{ - "scope": { - "sliceId": { - "sst": 11, "sd": "456DEF", "plmnId": {"mcc": "248", "mnc": "35"} - }, - "qosId": { - "5qi": 67 - } - }, - "tspResources": [ - { - "cellIdList": [ - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 55}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 65}} - ], - "preference": "SHALL" - }, - { - "cellIdList": [ - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 31}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 32}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 33}} - ], - "preference": "AVOID" - } - ] -} - -``` - -## A.5 QoS optimization with resource directive - -``` - -{ - "scope": { - "ueId": { - "guRanUeId": {"globalGnbId": { - "plmnId": {"mcc": "248", "mnc": "35"}, "gnbId": {"gnbIdLength": 25, "gnbIdValue": 6028163}}, - "ranUeId": "0000000000000855" - } - }, - "qosId": { - "5qi": 67 - } - }, - "qosObjectives": { - "priorityLevel": 50 - }, - "tspResources": [ - { - "cellIdList": [ - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 39}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 40}} - ], - "preference": "PREFER" - }, - { - "cellIdList": [ - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 81}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 82}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 83}} - ], - "preference": "AVOID" - } - ] -} - -``` - -``` - - ], - "preference": "AVOID" - } -] -} - -``` - -## A.6 QoE optimization with resource directive - -``` - -{ - "scope": { - "sliceId": { - "sst": 11, "sd": "456DEF", "plmnId": {"mcc":"248", "mnc":"35"} - } - }, - - "qoeObjectives": { - "qoeScore": 4.25 - }, - - "tspResources": [ - { - "cellIdList": [ - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 55}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 65}} - ], - "preference": "SHALL" - }, - { - "cellIdList": [ - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 21}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 22}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 23}} - ], - "preference": "AVOID" - } - ] -} - -``` - -## A.7 Status object for notification - -``` - -{ - "enforceStatus": "NOT_ENFORCED", - "enforceReason": "SCOPE_NOT_APPLICABLE" -} - -``` - -## A.8 UE level - -### A.8.1 UE level per-QoS - -``` - -{ - "scope": { - "ueId": { - "guRanUeId": {"globalGnbId": { - "plmnId": {"mcc":"123", "mnc":"45"}, "gnbId": {"gnbIdLength": 25, "gnbIdValue": 6028163}}, - "ranUeId": "00000000000000855"} - }, - "qosId": { - "5qi": 67 - } - }, - - "ueLevelObjectives": { - "ulPacketDelay": 0.5 - } -} - -``` - -} - -### A.8.2 UE level per-slice - -``` -{ - "scope": { - "ueId": { - "guRanUeId": { "globalGnbId": { - "plmnId": { "mcc": "248", "mnc": "35" }, "gnbId": { "gnbIdLength": 25, "gnbIdValue": 6028163 } }, - "ranUeId": "00000000000000855" - } - }, - "sliceId": { - "sst": 11, "sd": "456DEF", "plmnId": { "mcc": "248", "mnc": "35" } - } - }, - "ueLevelObjectives": { - "dlThroughput": 5000 - } -} -``` - -## A.9 RAN Slice SLA assurance - -### A.9.1 Support of maximum slice throughput SLA - -``` -{ - "scope": { - "sliceId": { "sst": 1, "sd": "456DEF", "plmnId": { "mcc": "248", "mnc": "35" } } - }, - "sliceSlaObjectives": { - "maxDlThptPerUe": 50000, - "maxUlThptPerUe": 25000, - "maxDlThptPerSlice": 300000000, - "maxUlThptPerSlice": 150000000 - } -} -``` - -### A.9.2 Support of maximum number of UEs and PDU sessions per slice SLA - -``` -{ - "scope": { - "sliceId": { "sst": 3, "sd": "456DEF", "plmnId": { "mcc": "248", "mnc": "35" } } - }, - "sliceSlaObjectives": { - "maxNumberOfUes": 100, - "maxNumberOfPduSessions": 800 - }, - "sliceSlaResources": { - "cellIdList": [ - { "plmnId": { "mcc": "248", "mnc": "35" }, "cId": { "ncI": 1 } }, - { "plmnId": { "mcc": "248", "mnc": "35" }, "cId": { "ncI": 2 } }, - { "plmnId": { "mcc": "248", "mnc": "35" }, "cId": { "ncI": 3 } } - ] - } -} -``` - -### A.9.3 Support of UE-level performance targets for slice users - -``` -{ - "scope": { - "sliceId": {"sst": 2, "sd": "123DEF", "plmnId": {"mcc":"248", "mnc":"35"}} - }, - "sliceSlaObjectives": { - "maxDLPacketDelayPerUe": 5, - "maxULPacketDelayPerUe": 5 - }, - "sliceSlaResources": { - "cellIdList": [ - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 1}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 2}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 3}} - ] - } -} -``` - -### A.9.4 Support of slice priority - -``` -{ - "scope": { - "sliceId": {"sst": 1, "sd": "123DEF", "plmnId": {"mcc":"248", "mnc":"35"}} - }, - "sliceSlaObjectives": { - "dlSlicePriority": 20, - "ulSlicePriority": 30 - }, - "sliceSlaResources": { - "cellIdList": [ - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 1}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 2}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 3}} - ] - } -} -``` - -## A.10 Load balancing - -### A.10.1 Load balancing per-cell with target downlink PRB usage - -``` -{ - "scope": { - "cellId": { - "plmnId": {"mcc":"123", "mnc":"45"}, "cId": {"ncI": 31}} - }, - "lbObjectives": { - "dlLbObjective": { - "dlTargetPrbUsg": 80, - "dlPprbUsgType": 1 - } - }, - "lbResources": { - "cellIdList": [ - {"plmnId": {"mcc": "123", "mnc": "45"}, "cId": {"ncI": 32}}, - {"plmnId": {"mcc": "123", "mnc": "45"}, "cId": {"ncI": 33}}, - {"plmnId": {"mcc": "123", "mnc": "45"}, "cId": {"ncI": 34}} - ] - } -} -``` - -### A.10.2 Load balancing per-cell per-slice with target downlink and uplink PRB usage - -``` -{ - "scope": { - "cellId": { - "plmnId": {"mcc": "123", "mnc": "45"}, "cId": {"ncI": 31} - }, - "sliceId": { - "sst": 11, "sd": "456DEF", "plmnId": {"mcc": "123", "mnc": "45"} - } - }, - "lbObjectives": { - "dlLbObjective": { - "dlTargetPrbUsg": 80, - "dlPrbUsgType": 3 - }, - "ulLbObjective": { - "ulTargetPrbUsg": 80, - "ulPrbUsgType": 3 - } - }, - "lbResources": { - "cellIdList": [ - {"plmnId": {"mcc": "123", "mnc": "45"}, "cId": {"ncI": 32}}, - {"plmnId": {"mcc": "123", "mnc": "45"}, "cId": {"ncI": 33}}, - {"plmnId": {"mcc": "123", "mnc": "45"}, "cId": {"ncI": 34}} - ] - } -} -``` - -## A.11 Energy saving - -### A.11.1 Comprehensive energy saving - -#### A.11.1.1 Energy saving over tracking area - -``` -{ - "scope": { - "taILList": [ - {"plmnId": {"mcc": "248", "mnc": "35"}, "tac": "123456"} - ] - }, - "esObjectives": { - "targetPeeEnergy": 20 - } -} -``` - -#### A.11.1.2 Energy saving over cell list - -``` -{ - "scope": { - "cellIdList": [ - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 71}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 72}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 73}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 81}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 82}}, - {"plmnId": {"mcc": "248", "mnc": "35"}, "cId": {"ncI": 83}} - ] - }, -} -``` - -``` - - "esObjectives": { - "esPercentage": 10 - } - } -} - -``` - -### A.11.2 Energy saving with exclusion cell list - -#### A.11.2.1 Energy saving over cells that are to remain operational but can have some coverage impact - -``` - -{ - "scope": { - "taILList": [ - { "plmnId": { "mcc": "248", "mnc": "35"}, "tac": "123456"} - ] - }, - - "esObjectives": { - "esPercentage": 10 - }, - - "esResources": [ - { - "operationalCells": [ - { "plmnId": { "mcc": "248", "mnc": "35"}, "cId": { "ncI": 91}}, - { "plmnId": { "mcc": "248", "mnc": "35"}, "cId": { "ncI": 92}}, - { "plmnId": { "mcc": "248", "mnc": "35"}, "cId": { "ncI": 93}} - ], - "operationalPreference": "FORBID" - } - ] -} - -``` - -#### A.11.2.2 Energy saving over cells that are to remain operational and maintain full coverage - -``` - -{ - "scope": { - "taILList": [ - { "plmnId": { "mcc": "248", "mnc": "35"}, "tac": "123456"} - ] - }, - - "esObjectives": { - "esPercentage": 10 - }, - - "esResources": [ - { - "operationalCells": [ - { "plmnId": { "mcc": "248", "mnc": "35"}, "cId": { "ncI": 91}}, - { "plmnId": { "mcc": "248", "mnc": "35"}, "cId": { "ncI": 92}}, - { "plmnId": { "mcc": "248", "mnc": "35"}, "cId": { "ncI": 93}} - ], - "operationalPreference": "FORBID" - }, - { - "coverageCells": [ - { "plmnId": { "mcc": "248", "mnc": "35"}, "cId": { "ncI": 91}}, - { "plmnId": { "mcc": "248", "mnc": "35"}, "cId": { "ncI": 92}}, - { "plmnId": { "mcc": "248", "mnc": "35"}, "cId": { "ncI": 93}} - ], - "coveragePreference": "FORBID" - } - ] -} - -``` - - - -# Annex B (Informative): EI examples - -## B.1 Generic examples - -### B.1.1 EI job status - -This is an example of EI job status that illustrates the usage of the generic EI job status schema defined in clause 9.1.1. - -``` -{ - "jobStatus": "DISABLED" -} -``` - -## B.2 UE geo-location and velocity - -### B.2.1 Statement for EI job constraints - -``` -{ - "ueGeoandVelEIConstraints": { - "supportedGadShapes": ["POINT", "POINT_ALTITUDE"], - "supportedVelocityDescs": ["H_VELOCITY", "HV_VELOCITY"] - } -} -``` - -### B.2.2 Statement for EI job definition - -``` -{ - "scope": { - "ueId": { - "guRanUeId": { - "globalGnbId": { - "plmnId": { "mcc": "123", "mnc": "45" }, - "gnbId": { "gnbIdLength": 25, "gnbIdValue": 6028163 } - }, - "ranUeId": "0000000000000855" - } - } - }, - "ueGeoandVelEIDescription": { - "gadShape": "POINT", - "granularityPeriod": 500, - "reportingPeriod": 500, - "reportingAmount": 1200, - "velocityDesc": "H_VELOCITY" - } -} -``` - -### B.2.3 Statement for EI job result - -``` -[ -{ - "timeStamp": "2022-05-30T09:00:30.5Z", - "ueId": { - "guRanUeId": { - "globalGnbId": { - "plmnId": { "mcc": "123", "mnc": "45" }, - "gnbId": { "gnbIdLength": 25, "gnbIdValue": 6028163 } - }, - "ranUeId": "0000000000000855" - } - }, - "gadShape": "POINT", - "geoLocation": { - "lon": -122.960625, - } -} -``` - -``` - "lat": 45.545112 - }, - "velocityDesc": "H_VELOCITY", - "velocity": { - "hSpeed": 15, - "bearing": 90 - } -} -] -``` - -# Annex C (Informative): JSON schema identification and versioning - -## C.1 General - -The base URI defined in clause 7.1 is used for the policy types and EI types, as well as the subschemas they link to, defined in the present document. - -Since the base URI is the same, data types defined in the subschema can be referred to with relative URI, e.g. "/jsonschemas/altd/common\_x.y.z/#/\$defs/UeId". - -## C.2 Embedding a subschema - -A subschema is defined with \$schema and \$id keywords, e.g.: - -``` -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "$id": "https://schemas.o-ran.org/jsonschemas/altd/common_2.0.0", - "$defs": { - ... - } -} -``` - -A subschema is linked using \$defs keyword in the base schema, e.g.: - -``` -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "$id": "https://schemas.o-ran.org/jsonschemas/altd/ORAN_QoSTarget_4.0.1", - ... - "$defs": { - "https://schemas.o-ran.org/jsonschemas/altd/common_2.0.0": - } -} -``` - -In a compound schema, a subschema is embedded into the base schema after the \$defs where it is linked, e.g.: - -``` -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "$id": "https://schemas.o-ran.org/jsonschemas/altd/ORAN_QoSTarget_4.0.1", - ... - "$defs": { - "https://schemas.o-ran.org/jsonschemas/altd/common_2.0.0": { - "$schema": "https://json-schema.org/draft/2020-12/schema", - "$id": "https://schemas.o-ran.org/jsonschemas/altd/common_2.0.0", - "$defs": { - ... - } - } - } -} -``` - -## C.3 Versioning of policy type schemas and common data types schema - -### C.3.1 General - -The common data types schema specified in clause 7.1.2.1 and the policy schemas specified in clause 7.2 can be updated independently but a policy schema update can also require, or be required by, an update of the common data types schema. When the common data types schema is updated, all policy schemas are updated to link to the new version of common data types schema ensuring that all schemas and linking are consistent within the present document. - -The following update scenarios can occur: - -- Policy type is updated but the update has not required a change to the common data types. If the common data types schema is updated, the updated policy schema links to the new common data types schema, and all other policy schemas are updated to link to the new common data types schema. -- Policy type is updated and the update has required a change to the common data types. The new policy schema links to the new common data types schema. All other policy schemas are updated to link to the new common data types schema. -- The common data types are updated. All policy schemas are updated to link to the new common data types schema. Policy schemas that are impacted by the updated common data types schema also incorporate any required changes. - -### C.3.2 Versioning of policy types - -When updating a policy schema to link to a new common data types schema, the update may result in a major, minor, or patch update to the policy type version - -NOTE: An update of a policy schema may link to a new version of the common data types schema without being impacted by the changes made to it and if it is impacted it can result in an update that is either compatible or not compatible. - -When linking to a new version of the common data types schema that has impact on the compatibility of the policy type, the policy type major version is incremented. - -When linking to a new version of the common data types schema and no further changes are made to the policy schema, the policy type patch version is incremented. - -# Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2021.03.13 | 01.00 | First version based on data models and policy types from A1AP v03.00 | -| 2021.07.16 | 02.00 | Introducing new policy types for UE Level target and Slice SLA target. Enhancing data type definitions and JSON encodings. | -| 2022.04.01 | 03.00 | Introducing new policy type for Load balancing | -| 2022.07.30 | 04.00 | Introducing new EI type for UE location and velocity information | -| 2022.11.17 | 05.00 | Aligning to O-RAN drafting rules.
Enhanced alignment between A1-P and A1-EI, and between A1AP and A1TD. | -| 2023.03.22 | 05.01 | Editorial enhancements | -| 2023.07.31 | 06.00 | Enhanced descriptions for SliceSlaObjectives and UE identifier options for ScopeIdentifier, and adapting to latest template | -| 2023.11.30 | 07.00 | ETSI PAS related editorial enhancements and extended description of packet delay and packet loss attributes and UE identifier options for ScopeIdentifier. Updating to latest JSON schema draft. | -| 2024.03.31 | 08.00 | Editorial enhancements. Introducing new policy type for Energy saving. | -| 2024.07.31 | 09.00 | Segmentation of JSON schemas. Adding attributes to Slice SLA target and Network energy saving policy types. | -| 2024.11.30 | 10.00 | Updates to the common schema and the policy and EI types related to that. Updated references. | -| 2025.03.31 | 10.01 | Editorial enhancement | -| 2025.07.31 | 11.00 | Updates to the common schema and the policy and EI types related to that, updates to the Load balancing policy type, and adapting to latest template | -| 2025.11.30 | 11.01 | Updated software license statements | \ No newline at end of file diff --git a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/0827b9260fe5458dbe416ebfc78c469e_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/08783c875dd39684fee7f2a40b584c64_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/0a65720e640be13541e947c06c7a8c7f_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/1099a4137017f2d9721d546bbb1e9362_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/11358a9fa9cfdf9faa0e5645ce4336f9_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/14af8d47efd24c21fddf71b2415b6397_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/185df94f4a6a5245323255e844a30ec0_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/188fd1cc0a6b1ef1f70fb01d59e058c0_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/226f5e462c99b71e08dc9abaa5ae260c_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/22af211207188ebc64d7b60ca052b367_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/253600420ae7bd7d0119563b895cbf8a_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/2b357e4034ff41a2e0c3ca8c25c00c9d_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/2d6a2e109d10cdfbc7b816a4d60d0174_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/38222c3ae003223a67635bfcc6950fbb_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/38866d3f212726e1c8e92001ca0dd6f8_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/3a4f4369128594c5db0aa6b853c0666e_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/3f727e6c0d6658bc53ea10905c4561dd_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/446c0bd806260f25430cadb01a6786c7_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/481b1f80fc31ebebb30d1f57d31e3af3_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 6c400c8e18d340845dcd5f64ebcce72c91af451f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4dfc726e23a82b724f0777c6071d9a3aff15cd924beeac2fb8bcdee90598fc89 -size 4609 diff --git a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/4db00373eb0bec04341ee887235bbfea_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/4f8349df2ca48959fefb7c42b2bc375e_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/5009e30a55479d3941af523871208f9d_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/5009e30a55479d3941af523871208f9d_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/56ac11fb9683d7b846fb65c845d80f22_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index 6c400c8e18d340845dcd5f64ebcce72c91af451f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/59368942873b0c35eef79a7a985025dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4dfc726e23a82b724f0777c6071d9a3aff15cd924beeac2fb8bcdee90598fc89 -size 4609 diff --git a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/59fcc0e3699f239444841881a2e75da0_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/5ae3023386ee15fae372871afce28865_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/60e345365fd1e52e01c91e3fd3cc6515_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/6588b1c7f14069d96744b473ad663248_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/6a5342571eca4b46338fdfb3c42a8055_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/6a9c5a85a12499d60c5a3a75c643b852_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/6c8a96787f532bd1fa4719e738cf556f_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/79898de98da3367d0ea9beef38f5c01c_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/7d08458fbe0bd5f306c00c16d68b25f2_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/7f4320cee12fc1dbb865cc6b67462a91_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/81b34087cd6755a80f84a70cf28fba82_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/829cdaf00f7219d70e571064b2b13291_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/83ee9f10bd3636e192d68decf7f04cec_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8447c5519e85d7a9e029fbf321da4c4f_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/854df8ad60507803253274673f9062cf_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/89100a6476d1d96f22c192db16502fec_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8b4befaffc5166da571069410e207aea_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8d129c93d18909f0643766f372e9ebf6_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8d138b6bf0be359dc7f079db4899bc41_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8dcca7651accff77ce832523fe2c7e64_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8fa517d2ddade6ee8fc26d015f1fc59a_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/8fbe9e67b51710384633b6407d60420d_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/9156549264d36ead617a1dec7987f970_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/9159d999b6514420a64eae80e52f1fd5_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index cd15d3d6f918cc6066ba42ec8f0244ce6a9b6549..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/970a901d8e537da4b6ff719d8931912f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6278d4614448b34b99fb5bad2e01af582cf4a1c21f527994324dae32ed6c0d06 -size 4571 diff --git a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index a147dab70be399f6d4959b0c16983f6be877b109..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/990afa9d07fb81cf8760867cb4247a79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b2655748c6c115e7727bc778d3907c3b997507c0e64d35669ee55324ce304ec3 -size 4527 diff --git a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/9a6ff2584005112f32fbd551cb6f0591_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/9b59a11096b85b2bc74c6f653a354e28_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/a28ab03366399b5e0a61445bc57e3724_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/a76a30cf23764f0b907220e7c3c70ce1_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/a7a2a8be6bea14f9e4740dbb3d24437e_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/a7fcb275d0eed586509a47f4f86a9725_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/a82aef1d2f3f1a527328950e9db947ee_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/be8d4d130f4e1f103926de61c4bfc23c_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/c389468860cd886ab9c732473e959f0f_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/c4315e81a5a818379fcf31519a9c2cbe_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/cb5f64aa26cee1c05257b7c6bbba7408_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d0516b99882398c64c90f71c12e808e2_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d2c29dfabebacb6f853683a6c3759320_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d879e5f2c388bb87ee9614f63364dcf0_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d90d939bcbf43d474efaeeaa335a635c_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/d90f17b29a73eddf151f51effa8912e0_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/da74b0e807fd62f32abdc3c05ffbabf4_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/da8cb3d696f15f2c6de7aff6955d12d3_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e11a88256307cfd7ebdbb5f6adcfa07a_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e32e1bcf367a284cc7a4186056810d22_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e511e373339b5f948f239b19e0c37dd4_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e87df69ebd4cd2dbbf6749079e6c057a_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/e882a6bdfd0e868314f3a26f536145a3_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/f250ba4162fe40d8ddfd05b74fa48895_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/f3d768b0299c4763bc703b606391c48b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/f74adaa1840504407cd4272995426f82_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/f7dbd497160f02888f34fdf243648aa2_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_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/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 6d148e5c5aeadf9fa2a25a7ba6c7c8e3ebcf5cc5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:37fc40475798ddc0c3681dd541b84a426d3b11ea065ba8491c3a15abebad9e14 -size 4537 diff --git a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TD-R005-v11.01/images/ff748955b94dcb8337283fbe12baa475_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/doc.md b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/doc.md deleted file mode 100644 index 0a622465a7ea9b794eea255bc8a84244709a3c39..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/doc.md +++ /dev/null @@ -1,3851 +0,0 @@ - - -# --- A1 interface: Test 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., Buschkauler Weg 27, 53347 Alfter, Germany - -Register of Associations, Bonn VR 11238, VAT ID DE321720189 - -# Contents - -| | | -|-----------------------------------------------------------------------|----| -| Foreword..... | 4 | -| Modal verbs terminology..... | 4 | -| Introduction ..... | 5 | -| 1 Scope..... | 5 | -| 2 References ..... | 5 | -| 2.1 Normative references ..... | 5 | -| 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 Test methodology ..... | 6 | -| 4.1 General ..... | 6 | -| 4.2 Conformance testing Non-RT RIC..... | 7 | -| 4.2.1 General..... | 7 | -| 4.2.2 Test configuration..... | 7 | -| 4.3 Conformance testing Near-RT RIC..... | 8 | -| 4.3.1 General..... | 8 | -| 4.3.2 Test configuration..... | 8 | -| 4.4 Interoperability testing between Non-RT RIC and Near-RT RIC ..... | 9 | -| 4.4.1 General ..... | 9 | -| 4.4.2 Test configuration..... | 9 | -| 5 Test cases for Non-RT RIC ..... | 11 | -| 5.1 General ..... | 11 | -| 5.1.1 Device under test requirements..... | 11 | -| 5.1.2 Test simulator capabilities ..... | 11 | -| 5.2 Conformance test cases for A1-P Consumer ..... | 11 | -| 5.2.1 Query policy type test scenarios ..... | 11 | -| 5.2.2 Create policy test scenarios..... | 13 | -| 5.2.3 Query policy test scenarios ..... | 14 | -| 5.2.4 Update policy test scenarios..... | 16 | -| 5.2.5 Delete policy test scenarios..... | 17 | -| 5.2.6 Notify policy status test scenarios..... | 18 | -| 5.3 Conformance test cases for A1-EI Producer ..... | 20 | -| 5.3.1 Query EI types test scenarios..... | 20 | -| 5.3.2 Create EI job test scenarios..... | 22 | -| 5.3.3 Query EI jobs test scenarios..... | 24 | -| 5.3.4 Update EI job test scenarios..... | 28 | -| 5.3.5 Delete EI job test scenarios..... | 30 | -| 5.3.6 Status of EI jobs test scenarios..... | 31 | -| 5.3.7 Deliver EI job result test scenarios ..... | 33 | -| 6 Test cases for Near-RT RIC ..... | 35 | -| 6.1 General ..... | 35 | -| 6.1.1 Device under test requirements..... | 35 | -| 6.1.2 Test simulator capabilities ..... | 35 | -| 6.2 Conformance Test Cases for A1-P Producer..... | 35 | -| 6.2.1 Query policy type test scenarios ..... | 35 | -| 6.2.2 Create policy test scenarios..... | 38 | -| 6.2.3 Query policy test scenarios ..... | 40 | -| 6.2.4 Update policy test scenarios..... | 44 | -| 6.2.5 Delete policy test scenarios..... | 46 | - -| | | | -|--------------------------------------------------|-------------------------------------------------------------------------|-----------| -| 6.2.6 | Notify policy status test scenarios..... | 47 | -| 6.3 | Conformance test cases for A1-EI Consumer ..... | 48 | -| 6.3.1 | Query EI types test scenarios..... | 48 | -| 6.3.2 | Create EI job test scenarios..... | 50 | -| 6.3.3 | Query EI jobs test scenarios..... | 51 | -| 6.3.4 | Update EI job test scenarios..... | 53 | -| 6.3.5 | Delete EI job test scenarios..... | 54 | -| 6.3.6 | Status of EI jobs test scenarios..... | 55 | -| 6.3.7 | Deliver EI job result test scenarios ..... | 57 | -| 7 | Test cases for interoperability between Non-RT RIC and Near-RT RIC..... | 59 | -| 7.1 | General ..... | 59 | -| 7.1.1 | System under test requirements ..... | 59 | -| 7.1.2 | Test tools and simulators capabilities ..... | 60 | -| 7.2 | Interoperability test cases for A1-P ..... | 60 | -| 7.2.1 | Query policy type test scenarios ..... | 60 | -| 7.2.2 | Create policy test scenario ..... | 62 | -| 7.2.3 | Query policy test scenarios ..... | 63 | -| 7.2.4 | Update policy test scenarios..... | 66 | -| 7.2.5 | Delete policy test scenarios..... | 67 | -| 7.2.6 | Notify policy status test scenarios..... | 68 | -| 7.3 | Interoperability test cases for A1-EI..... | 69 | -| 7.3.1 | Query EI types test scenarios..... | 69 | -| 7.3.2 | Create EI job test scenario ..... | 72 | -| 7.3.3 | Query EI jobs test scenarios..... | 73 | -| 7.3.4 | Update EI job test scenarios..... | 76 | -| 7.3.5 | Delete EI job test scenarios..... | 77 | -| 7.3.6 | Status of EI jobs test scenarios..... | 78 | -| 7.3.7 | Deliver EI job result test scenarios ..... | 80 | -| Annex (informative): Change History ..... | | 82 | - -# --- Foreword - -This Technical Specification (TS) has been produced by O-RAN Alliance Working Group 2. It is part of a TS-family covering the A1 interface as identified below: - -- "A1 interface: General Aspects and Principles"; -- "A1 interface: Use Cases and Requirements"; -- "A1 interface: Transport Protocol"; -- "A1 interface: Application Protocol"; -- "A1 interface: Type Definitions"; and -- "A1 interface: Test Specification". - -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 - -The purpose of the present document is to specify test cases for the A1 interface. Test cases and methodology for A1-P Consumer, A1-P Producer, A1-EI Consumer, and A1-EI Producer are separately specified. The present document will also address A1 related test cases for Interoperability between Non-RT RIC and Near-RT RICs. - -The present document contains normative requirements on A1 test cases for Conformance testing and Interoperability testing. For each specified test case, these requirements cover the entrance criteria, procedure and expected result. The test cases are defined based on the procedures specified for the A1 Application Protocol for which the test cases are used to validate conformance and interoperability. The present document does not require that all test cases are supported by a DUT, and a subset of the test cases may not be applicable in a specific testing. It is the responsibility of the tester to identify which test cases that are relevant based on an implementation statement related to a DUT. - -The test cases require test equipment with specific capabilities needed to perform testing. The clauses on the test configurations in the present document describes some of the main capabilities that test equipment will provide. - -The test cases require certain functionality in the DUTs to perform testing. The present document does not require any specific implementation of such functionality. - -NOTE 1: When standardised APIs are available for rApps and xApps, it is foreseen that such apps can be part of the test equipment and used for testing of production grade DUTs. - -Testing of the A1-P and A1-EI procedures requires that at least one policy type and one EI type is supported by both sides of the A1 interface during testing. The policy type(s) or EI type(s) to be used in a test case is agreed between the testing entities as described for the test entrance criteria of the test case. - -NOTE 2: Testing of expected behaviour related to policy types and EI types is not in scope of the present document, only the procedural aspects that requires presence of some policy type or EI type. - -# 1 Scope - -The present document specifies test cases for conformance testing and interoperability testing of the Non-RT RIC and the Near-RT RIC over the A1 interface. - -# 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] Void. -- [2] Void. -- [3] O-RAN.WG2.TS.A1TP: "A1 interface: Transport Protocol" ("A1TP"). -- [4] O-RAN.WG2.TS.A1AP: "A1 interface: Application Protocol" ("A1AP"). - -[5] Void. - -## 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.A1GAP: "A1 interface: General Aspects and Principles" ("A1GAP"). -- [i.2] O-RAN.WG2.TS.A1TD: "A1 interface: Type Definitions" ("A1TD"). - -# --- 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the terms given in A1GAP [i.1], clause 3.1, A1AP [4], clause 3.1, and A1TD [i.2], clause 3.1 apply. - -## 3.2 Symbols - -Void. - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given in A1GAP [i.1], clause 3.3, A1AP [4], clause 3.3, A1TD [i.2], clause 3.3 and the following apply: - -| | | -|-----|-------------------| -| DUT | Device Under Test | -|-----|-------------------| - -# --- 4 Test methodology - -## 4.1 General - -This clause describes the methodology for conformance and interoperability testing of Non-RT RIC and Near-RT RIC over A1 interface. - -For conformance tests, simulators are used for testing A1 procedures. These simulators will have capability of generating HTTP requests and responses for GET, PUT, POST and DELETE operations. There will be flexibility in configuring URI, headers and body for these HTTP requests and responses to enable creation of various test cases. - -For interoperability tests, devices under tests are Non-RT RIC and Near-RT RIC, these devices are brought to operation by connecting to appropriate real or simulated devices. - -## 4.2 Conformance testing Non-RT RIC - -### 4.2.1 General - -Non-RT RIC is the device under test, clause 5 of the present document specifies conformance tests for A1-P Consumer and A1-EI Producer functionality as specified in document A1AP [4], clause 5. - -### 4.2.2 Test configuration - -#### 4.2.2.0 Overview - -The test configuration for A1 conformance testing of Non-RT RIC is illustrated in figure 4.2.2.0-1. - -![Diagram illustrating the Non-RT RIC A1 conformance test setup. The diagram shows two main components: Non-RT RIC (DUT) and Test Simulator. The Non-RT RIC (DUT) contains an A1-P Consumer and an A1-EI Producer. The Test Simulator contains an A1-P Producer and an A1-EI Consumer. The A1-P Consumer is connected to the A1-P Producer via an A1 interface. The A1-EI Producer is connected to the A1-EI Consumer via an A1 interface.](9791722d75115ddcc599b07d7bc35d73_img.jpg) - -``` - -graph TD - subgraph Non-RT_RIC [Non-RT RIC (DUT)] - A1P_Consumer[A1-P Consumer] - A1EI_Producer[A1-EI Producer] - end - subgraph Test_Simulator [Test Simulator] - A1P_Producer[A1-P Producer] - A1EI_Consumer[A1-EI Consumer] - end - A1P_Consumer -- A1 --> A1P_Producer - A1EI_Producer -- A1 --> A1EI_Consumer - -``` - -Diagram illustrating the Non-RT RIC A1 conformance test setup. The diagram shows two main components: Non-RT RIC (DUT) and Test Simulator. The Non-RT RIC (DUT) contains an A1-P Consumer and an A1-EI Producer. The Test Simulator contains an A1-P Producer and an A1-EI Consumer. The A1-P Consumer is connected to the A1-P Producer via an A1 interface. The A1-EI Producer is connected to the A1-EI Consumer via an A1 interface. - -Figure 4.2.2.0-1 Illustration of Non-RT RIC A1 conformance test setup - -#### 4.2.2.1 Device under test (Non-RT RIC) - -For enabling conformance testing, the Non-RT RIC has implemented A1-P Consumer and/or A1-EI Producer functionality and the service operations specified in A1AP [4], clause 5 that are required to perform testing of the applicable test cases. It also supports one agreed policy type and/or one agreed EI type. - -#### 4.2.2.2 Test simulator - -The test simulator has A1-P Producer and A1-EI Consumer that both have HTTP Client and HTTP Server capabilities and have flexibility to generate, receive and validate HTTP messages for all the A1 procedures. The test simulator logs all message content during the testing. - -The A1-P Producer in the test simulator has all the capabilities needed to operate the A1-P test cases, including: - -- Enable and disable policy types; -- Changing parameters in A1-P procedure response messages; -- Responding with success and failure messages; -- Ability to deliver policy status notifications by sending HTTP POST messages with JSON body created based on configured schemas; and -- Validation of message contents based on configured schemas (headers, return codes, JSON body etc.). - -The A1-EI Consumer in the test simulator has all the capabilities needed to operate the A1-EI test cases, including: - -- Send query messages for EI types; -- Create and delete EI jobs for available EI types; and -- Request and receive EI job status notifications and EI job results. - -## 4.3 Conformance testing Near-RT RIC - -### 4.3.1 General - -Near-RT RIC is the device under test, clause 6 of the present document specifies conformance tests for A1-P Producer and A1-EI Consumer functionality as specified in document A1AP [4], clause 5. - -### 4.3.2 Test configuration - -#### 4.3.2.0 Overview - -The test configuration for A1 conformance testing of Near-RT RIC is illustrated in figure 4.3.2.0-1. - -![Diagram of Near-RT RIC A1 conformance test setup showing a Test Simulator connected to a Near-RT RIC (DUT) via A1 interfaces.](7affafe7362a2d2d072e9d4bf515f0bb_img.jpg) - -The diagram illustrates the test configuration for A1 conformance testing of the Near-RT RIC (DUT). It is divided into two main sections: the Test Simulator and the Near-RT RIC (DUT). - -- Test Simulator:** This section is enclosed in a dotted box and contains two dashed boxes: - - A1-P Consumer:** Located on the left side of the Test Simulator. - - A1-EI Producer:** Located on the right side of the Test Simulator. -- Near-RT RIC (DUT):** This section is enclosed in a dotted box and contains two solid boxes: - - A1-P Producer:** Located on the left side of the Near-RT RIC (DUT). - - A1-EI Consumer:** Located on the right side of the Near-RT RIC (DUT). -- Connections:** - - An A1 interface connects the A1-P Consumer in the Test Simulator to the A1-P Producer in the Near-RT RIC (DUT). - - An A1 interface connects the A1-EI Producer in the Test Simulator to the A1-EI Consumer in the Near-RT RIC (DUT). - -Diagram of Near-RT RIC A1 conformance test setup showing a Test Simulator connected to a Near-RT RIC (DUT) via A1 interfaces. - -Figure 4.3.2.0-1 Illustration of Near-RT RIC A1 conformance test setup - -#### 4.3.2.1 Device under test (Near-RT RIC) - -For enabling conformance testing, the Near-RT RIC has implemented A1-P Producer and/or A1-EI Consumer functionality and the service operations specified in A1AP [4], clause 5 that are required to perform testing of the applicable test cases. It also supports one agreed policy type and/or one agreed EI type. - -#### 4.3.2.2 Test simulator - -The test simulator has A1-P Consumer and A1-EI Producer that both have HTTP Client and HTTP Server capabilities and have flexibility to generate, receive and validate HTTP messages for all the A1 procedures. The test simulator logs all message content during the testing. - -The A1-P Consumer in the test simulator has all the capabilities needed to operate the A1-P test cases, including: - -- Send query messages for policy types; - -- Create and delete policies for available policy types; and -- Request and receive policy status notifications. - -The A1-EI Producer in the test simulator has all the capabilities needed to operate the A1-EI test cases, including: - -- Enable and disable EI job types. -- Changing parameters in A1-EI procedure response messages; -- Responding with success and failure messages; -- Ability to deliver EI job status notifications and EI job results by sending HTTP POST messages with JSON body created based on configured schemas; and -- Validation of message contents based on configured schemas (headers, return codes, JSON body etc.). - -## 4.4 Interoperability testing between Non-RT RIC and Near-RT RIC - -### 4.4.1 General - -Both Non-RT RIC and Near-RT RIC are the devices under test or constitutes a system under test, they may be from different vendors or from the same vendor. Clause 7 of the present document specifies interoperability test cases for A1-P and A1-EI functionality as specified in document A1AP [4], clause 5. - -Test methodology is conceived to be non-intrusive to ensure that production ready devices and software can be used in the test setup. - -A protocol analyser connected to A1 interface use a tap to collect and analyses packets passively for test case validation. - -In addition to the devices under test, some additional functionalities may be needed to bring the devices under test to operational state and to facilitate test case execution. These are optional depending on DUT implementation and can be provided by real devices or by simulators. - -### 4.4.2 Test configuration - -#### 4.4.2.0 Overview - -The test configuration for A1 interoperability testing between Non-RT RIC and Near-RT RIC is illustrated in Figure 4.4.2.0-1. - -![Diagram illustrating the Non-RT RIC and Near-RT RIC interoperability test setup. The setup is divided into two main sections: the SMO framework and the UE + RAN + Core. The SMO framework contains the O1 functionality (simulator or real) and the Non-RT RIC (DUT). The UE + RAN + Core section contains the UEs (simulator or real), the E2 node functionality (simulator or real), and the 4G/5G Core functionality (simulator or real). The Near-RT RIC (DUT) is connected to the O1 functionality via the O1 interface, to the E2 node functionality via the E2 interface, and to the Protocol Analyzer via the A1 interface (tap for capturing).](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) - -``` - -graph TD - subgraph SMO_framework [SMO framework] - O1_func[O1 functionality (simulator or real)] - NonRT_RIC[Non-RT RIC (DUT)] - end - subgraph UE_RAN_Core [UE + RAN + Core] - UEs[UEs (simulator or real)] - E2_func[E2 node functionality (simulator or real)] - Core[4G/5G Core functionality (simulator or real)] - end - NearRT_RIC[Near-RT RIC (DUT)] - PA[Protocol Analyzer] - - O1_func -- O1 --> NearRT_RIC - E2_func -- E2 --> NearRT_RIC - NonRT_RIC -- A1 --> PA - UEs --- E2_func --- Core - -``` - -Diagram illustrating the Non-RT RIC and Near-RT RIC interoperability test setup. The setup is divided into two main sections: the SMO framework and the UE + RAN + Core. The SMO framework contains the O1 functionality (simulator or real) and the Non-RT RIC (DUT). The UE + RAN + Core section contains the UEs (simulator or real), the E2 node functionality (simulator or real), and the 4G/5G Core functionality (simulator or real). The Near-RT RIC (DUT) is connected to the O1 functionality via the O1 interface, to the E2 node functionality via the E2 interface, and to the Protocol Analyzer via the A1 interface (tap for capturing). - -**Figure 4.4.2.0-1 Illustration of Non-RT RIC and Near-RT RIC interoperability test setup** - -#### 4.4.2.1 System under test (Non-RT RIC and Near-RT RIC) - -Non-RT RIC and Near-RT RIC will have a minimal set of matching functionalities to facilitate testing of A1-P and/or A1-EI procedures. As an entry criterion for interoperability testing, Non-RT RIC and Near-RT RIC need to have at least one matching policy type and/or EI type. - -#### 4.4.2.2 Test tools and simulators (SMO framework, E2 nodes, UEs, etc.) - -##### 4.4.2.2.1 SMO O1 functionality (Simulator or real) - -SMO O1 functionality may be needed if Non-RT RIC relies on O1 functionality for provisioning. This interface is also needed if the Non-RT RIC collects performance metrics via O1 interface. - -##### 4.4.2.2.2 UEs and RAN (simulator or real) - -For triggering A1-P and A1-EI procedures across A1 interface, Near-RT RIC may need one or more E2 Node(s). These can be real or simulated nodes with supported E2 Service Model functionality as needed by Near-RT RIC involved in the tests. - -A simulated or real UE call activity may be needed to invoke the appropriate Near-RT RIC functionality and/or O1 metrics. - -##### 4.4.2.2.3 4G/5G Core Network. - -Depending on the Non-RT RIC, Near-RT RIC and/or E2 Nodes used, a simulated or real 4G/5G Core Network may be needed for UE activity. - -##### 4.4.2.2.4 Tap interface and protocol analyser - -A tap interface and protocol analyser can be used on A1 interface to passively capture and analyse packets for test case validation. - -# 5 Test cases for Non-RT RIC - -## 5.1 General - -### 5.1.1 Device under test requirements - -The Non-RT RIC that acts as Device Under Test (DUT) in the test scenarios of this clause can be a function that is under development, or it can be a finalised commercial product. The requirements on the DUT for these tests are that it can handle the procedures defined for a Non-RT RIC and the purpose of the test scenarios is to validate that it conforms to the A1 service definitions in A1AP [4], clause 5. - -In addition to the basic conformance requirements, the following is required for a Non-RT RIC when it acts as DUT: - -- It shall be possible for the DUT to initiate the A1-P procedures in a controlled manner for each A1-P related test case; -- For A1-P related test cases, it shall be possible for the DUT to support A1 policy types to use in the test cases after agreement with the test simulator. It shall be possible to formulate A1 policies based on agreed policy types, and it shall be possible to validate PolicyStatusObjects based on the schemas of the agreed policy types; and -- For A1-EI related test cases, it shall be possible for the DUT to support EI types to use in the test cases after agreement with the test simulator. It shall be possible to validate EiJobObjects based on the schemas of the agreed EI types. - -NOTE: The present document does not require usage of any specific policy type or EI type since specific behaviour is not validated, only the application protocol aspects and procedures are validated for conformance testing of the A1 services. - -### 5.1.2 Test simulator capabilities - -The test simulator has the same basic capabilities as required for a Near-RT RIC. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analysing them regarding conformance to the A1 service definitions; -- Controlled initiation of procedures with configurable URIs and payload formulated and modified based on the schemas of the agreed policy types and EI types; and -- Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the A1 service definitions in A1AP [4], clause 5. - -## 5.2 Conformance test cases for A1-P Consumer - -### 5.2.1 Query policy type test scenarios - -#### 5.2.1.1 Query all policy type identifiers (positive case) - -##### 5.2.1.1.1 Test description and applicability - -The purpose of this test case is to test the query policy types functionality of A1-P Consumer as specified in A1AP [4] clause 5.2.3.2. The expected outcome is successful validation of the Query all policy type identifiers request. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query all policy type identifiers procedure. - -##### 5.2.1.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate A1-P Query all policy type identifiers procedure. -- 2) A set of policy types (at least two) are supported in the test simulator. - -##### 5.2.1.1.3 Test methodology - -###### 5.2.1.1.3.1 Initial conditions - -- 1) The test simulator has A1-P Producer service ready and available to receive HTTP requests from the DUT. - -###### 5.2.1.1.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Query all policy type identifiers request. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. -- b) The HTTP request is a GET operation. -- c) The HTTP request message body is empty. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.2.3.2.1. - -###### 5.2.1.1.3.3 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 5.2.1.2 Query single policy type (positive case) - -##### 5.2.1.2.1 Test description and applicability - -This purpose of this test case is to test the query policy type functionality of A1-P Consumer as specified in A1AP [4] clause 5.2.3.3. The expected outcome is successful validation of the Query single policy type request. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query single policy type procedure. - -##### 5.2.1.2.2 Test entrance criteria - -- 1) The DUT has the functionality to initiate A1-P Query single policy type procedure -- 2) A known set of policy types are supported in the test simulator. -- 3) Policy type identifiers used for this test are known in advance and used in DUT to formulate the Query single policy type request, and in test Simulator for selecting the appropriate schemas for the policy type object. - -##### 5.2.1.2.3 Test methodology - -###### 5.2.1.2.3.1 Initial conditions - -- 1) The test Simulator has A1-P Producer service ready and available to receive HTTP requests from the DUT. - -###### 5.2.1.2.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Query single policy type request with a known policyTypeId. - -Step 2. At the test Simulator the contents of the received HTTP request are recorded. - -Step 3. The test Simulator does the following validation: - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. -- b) The HTTP request is a GET operation. -- c) The policyTypeId in the URI match the policy type being queried. -- d) The message body is empty. - -Step 4. The test Simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.2.3.3.1. - -###### 5.2.1.2.3.3 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 5.2.2 Create policy test scenarios - -#### 5.2.2.1 Create single policy (positive case) - -##### 5.2.2.1.1 Test description and applicability - -This purpose of this test case is to test the create policy functionality of A1-P Consumer as specified in A1AP [4] clause 5.2.4.3. The expected outcome is successful validation of the Create single policy request. - -This test case is conditionally mandatory if the DUT claims to support A1-P service. - -##### 5.2.2.1.2 Test entrance criteria - -- 1) The DUT has the functionality to initiate A1-P Create single policy procedure. -- 2) The DUT and the test simulator have agreed on a policy type to use for this test. -- 3) The policyTypeId and the JSON schemas of the policy type used for this test are available and used in DUT to formulate the create policy request, and in test simulator to validate the request. - -##### 5.2.2.1.3 Test methodology - -###### 5.2.2.1.3.1 Initial conditions - -- 1) The test simulator has A1-P Producer service ready and available to receive HTTP requests from the DUT. -- 2) No policy exists in the test simulator for the agreed policy type with the same policyId that will be used by the DUT. - -Note: The DUT is required to generate a unique policyId during the Create single policy procedure (see A1AP [4] clauses 5.2.2.2 and 5.2.3.2.2). - -###### 5.2.2.1.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Create single policy request for the agreed policy type. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. -- b) The HTTP request is a PUT operation. - -- c) The policyTypeId is supported. -- d) A policy with the policyId does not exist. -- e) The HTTP request message body contains the PolicyObject of the policy to be created and the PolicyObject conforms to the schema. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.3.2.2.2. - -###### 5.2.2.1.3.3 Expected result - -The test is considered passed if Step 3 validation has passed. - -NOTE: Presence or validation of optional query parameter for notificationDestination is not used to determine validation on this test. - -### 5.2.3 Query policy test scenarios - -#### 5.2.3.1 Query all policy identifiers (positive case) - -##### 5.2.3.1.1 Test description and applicability - -The purpose of this test case is to test the query policies functionality of A1-P Consumer as specified in A1AP [4] clause 5.2.4.2. The expected outcome is successful validation of the Query all policy identifiers request. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query all policy identifiers procedure. - -##### 5.2.3.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate A1-P Query all policy identifiers procedure. -- 2) The DUT and the test simulator have agreed on a policy type to use for this test. -- 3) A set of policies (at least two) for the agreed policy type exist in the test simulator. - -##### 5.2.3.1.3 Test methodology - -###### 5.2.3.1.3.1 Initial conditions - -- 1) The test simulator has A1-P Producer service ready and available to receive HTTP requests from the DUT. - -###### 5.2.3.1.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Query all policy identifiers request. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. -- b) The HTTP request is a GET operation. -- c) The message body is empty. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.2.4.2.1. - -###### 5.2.3.1.3.3 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 5.2.3.2 Query single policy (positive case) - -##### 5.2.3.2.1 Test description and applicability - -The purpose of this test case is to test the query policy functionality of A1-P Consumer as specified in A1AP [4] clause 5.2.4.5. The expected outcome is successful validation of the Query single policy request. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query single policy procedure. - -##### 5.2.3.2.2 Test entrance criteria - -- 1) The DUT has functionality to initiate A1-P Query single policy procedure. -- 2) A policy exists in test simulator and the policyTypeId and the policyId is known to DUT. - -##### 5.2.3.2.3 Test methodology - -###### 5.2.3.2.3.1 Initial conditions - -- 1) The test simulator has A1-P Producer service ready and available to receive HTTP requests from the DUT. - -###### 5.2.3.2.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Query single policy request for the existing policy identified by policyTypeId and policyId. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. -- b) The HTTP request is a GET operation. -- c) The policyTypeId and policyId in the URI match the policy being queried. -- d) The message body is empty. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.2.4.5.1. - -###### 5.2.3.2.3.3 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 5.2.3.3 Query policy status (positive case) - -##### 5.2.3.3.1 Test description and applicability - -The purpose of this test case is to test the query policy status functionality of A1-P Consumer as specified in A1AP [4] clause 5.2.4.7. The expected outcome is successful validation of the Query policy status request. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query policy status procedure. - -##### 5.2.3.3.2 Test entrance criteria - -- 1) The DUT has functionality to initiate A1-P Query policy status procedure. - -- 2) A policy exists in test simulator and the policyTypeId and the policyId is known to DUT. - -##### 5.2.3.3.3 Test methodology - -###### 5.2.3.3.3.1 Initial conditions - -- 1) The test simulator has A1-P Producer service ready and available to receive HTTP requests from the DUT. - -###### 5.2.3.3.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Query policy status request for the existing policy identified by policyTypeId and policyId. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. -- b) The HTTP request is a GET operation. -- c) The policyTypeId and policyId in the URI match the policy being queried. -- d) The message body is empty. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.2.4.7.1. - -###### 5.2.3.3.3.3 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 5.2.4 Update policy test scenarios - -#### 5.2.4.1 Update single policy (positive case) - -##### 5.2.4.1.1 Test description and applicability - -The purpose of this test case is to test the update policy functionality of A1-P Consumer as specified in A1AP [4] clause 5.2.4.4. The expected outcome is successful validation of Update single policy request. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Update single policy procedure. - -##### 5.2.4.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate A1-P Update single policy procedure. -- 2) A policy exists in test simulator and the policyTypeId and the policyId is known to DUT. -- 3) The JSON schemas of the policy type used for this test are available and used in DUT to formulate the Update single policy request, and in test simulator to validate the request. - -##### 5.2.4.1.3 Test methodology - -###### 5.2.4.1.3.1 Initial conditions - -- 1) The test simulator has A1-P Producer service ready and available to receive HTTP request from the DUT. - -###### 5.2.4.1.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Update single policy request for the existing policy identified by policyTypeId and policyId. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. -- b) The HTTP request is a PUT operation. -- c) The policyTypeId and policyId in the URI match the policy being updated. -- d) The HTTP request message body contains the PolicyObject of the policy to be updated and the PolicyObject conforms to the schema of the policy type. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.2.4.4.1. - -###### 5.2.4.1.3.3 Expected result - -The test is considered passed if Step 3 validation has passed. - -NOTE: Presence or validation of optional query parameter for notificationDestination is not used to determine validation on this test. - -### 5.2.5 Delete policy test scenarios - -#### 5.2.5.1 Delete single policy (positive case) - -##### 5.2.5.1.1 Test description and applicability - -This purpose of this test case is to test the delete policy functionality of A1-P Consumer as specified in A1AP [4] clause 5.2.4.6. The expected outcome is successful validation of the Delete single policy request. - -This test case is conditionally mandatory if the DUT claims to support A1-P service. - -##### 5.2.5.1.2 Test entrance criteria - -- 1) The DUT has the functionality to initiate A1-P Delete policy procedure. -- 2) A policy exists in test simulator and the policyTypeId and the policyId is known to DUT. - -##### 5.2.5.1.3 Test methodology - -###### 5.2.5.1.3.1 Initial conditions - -- 1) The test simulator has A1-P Producer service ready and available to receive HTTP requests from the DUT. - -###### 5.2.5.1.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Delete policy request for the existing policy identified by policyTypeId and policyId. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. - -- b) The HTTP request is a DELETE operation. -- c) The policyTypeId and policyId in the URI match the policy being deleted -- d) The message body is empty. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.2.4.6.1. - -###### 5.2.5.1.3.3 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 5.2.6 Notify policy status test scenarios - -#### 5.2.6.1 Notify policy status (positive case) - -##### 5.2.6.1.1 Test description and applicability - -This purpose of this test case is to test the policy status notification functionality of A1-P Consumer as specified in A1AP [4] clause 5.2.4.8. The expected outcome is successful policy status request and reception. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and supports the Notify policy status procedure. - -##### 5.2.6.1.2 Test entrance criteria - -The test entrance criteria for Create single policy specified in clause 5.2.2.1.2 applies. And in addition: - -- 1) The DUT has the functionality to request and receive policy status notifications. - -##### 5.2.6.1.3 Test methodology - -###### 5.2.6.1.3.1 Initial conditions - -The initial conditions for Create single policy specified in clause 5.2.2.1.3.1 applies. And in addition: - -- 1) The test simulator supports generation of a PolicyStatusObject based on the policy status schema of the agreed policy type used for this test. -- 2) The DUT has HTTP server ready and available to receive HTTP requests from the test simulator. - -NOTE: The DUT is expected to provide callback URI (notificationDestination) during the Create single policy procedure (see A1AP [4] clause 5.2.4.3) for which it can relate received policy status notifications to the policyId that was generated when creating the policy for which policy status notifications is requested. - -###### 5.2.6.1.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Create single policy request for the agreed policy type including the notificationDestination query parameter. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a)-e) as defined for Create single policy in clause 5.2.2.1.3.2. -- f) The notificationDestination query parameter is included. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.2.4.8.1. - -Step 5. The test simulator initiates the Notify policy status procedure and sends a HTTP POST request to the provided callback URI (notificationDestination) in the DUT with message body containing the PolicyStatusObject conforming to the schema of the used policy type. - -Step 6. At the test simulator the received HTTP response is recorded. - -NOTE: For the time between Step 4 and Step 5, the test simulator need not simulate any change in policy status but can send status notifications directly with any content that conforms to the status schema of the used policy type. - -###### 5.2.6.1.3.3 Expected result - -The test is considered passed if the following conditions are met: - -- 1) Step 3 validation has passed -- 2) Check the HTTP response recorded in step 6 of procedure and that the return code is "204 No content". - -#### 5.2.6.2 Notify policy status – schema validation failure (negative case) - -##### 5.2.6.2.1 Test description and applicability - -This purpose of this test case is to test the policy status notification functionality of A1-P Consumer as specified in A1AP [4] clause 5.2.4.8. The expected outcome is failure due to schema validation failure. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and supports the Notify policy status procedure. - -##### 5.2.6.2.2 Test entrance criteria - -The test entrance criteria in clause 5.2.6.1.2 applies. - -##### 5.2.6.2.3 Test methodology - -###### 5.2.6.2.3.1 Initial conditions - -The initial conditions in clause 5.2.6.1.3.1 applies. - -###### 5.2.6.2.3.2 Procedure - -Steps 1-6 of clause 5.2.6.1.3.2 applies with the following modification: - -In Step 5: A spelling mistake should be introduced in the PolicyStatusObject for schema validation error in DUT. - -###### 5.2.6.2.3.3 Expected result - -The test is considered passed if the following conditions are met: - -- 1) Step 3 validation has passed -- 2) Check the HTTP response recorded in step 6 of procedure and that the return code is "400 Bad request". - -#### 5.2.6.3 Void - -## 5.3 Conformance test cases for A1-EI Producer - -### 5.3.1 Query EI types test scenarios - -#### 5.3.1.1 Query EI type identifiers (positive case) - -##### 5.3.1.1.1 Test description and applicability - -This purpose of this test case is to test query EI type identifiers functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.3.2. The expected outcome is successful retrieval of EI type identifiers. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and Query EI type identifiers procedure. - -##### 5.3.1.1.2 Test entrance criteria - -- 1) The DUT supports the Query EI type identifiers procedure. -- 2) The test simulator has the functionality to initiate A1-EI Query EI type identifiers procedure. -- 3) The DUT supports a known set of EI types (two or more) used for this test. - -##### 5.3.1.1.3 Test methodology - -###### 5.3.1.1.3.1 Initial conditions - -- 1) The DUT has A1-EI Producer service ready and available to receive HTTP requests from the test simulator. -- 2) The DUT supports the three different test configurations listed below to test complete functionality: - - a) DUT has no EI type available. - - b) DUT has a single EI type available. - - c) DUT has two or more EI types available. - -###### 5.3.1.1.3.2 Procedure - -- Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.3.3 and empty message body. -- Step 2. At the test simulator the received HTTP response is recorded. -- Step 3. Repeat Step 1 and Step 2 for the three test configurations. - -###### 5.3.1.1.3.3 Expected result - -At the test simulator check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met for all three test configurations listed in clause 5.3.1.1.3.1: - -- 1) The return code is "200 OK". -- 2) Response message body is validated depending on the test configuration used: - - a) If the DUT has no EI type available, message body is an empty array. - - b) If the DUT has single EI type available, message body contains an array with one eiTypeId. - -- c) If the DUT has two or more EI jobs available, message body contains an array of all the eiTypeIds available in DUT. - -#### 5.3.1.2 Query EI type (positive case) - -##### 5.3.1.2.1 Test description and applicability - -The purpose of this test case is to test query EI type functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.3.3. The expected outcome is successful retrieval of EI type object. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Query EI type procedure. - -##### 5.3.1.2.2 Test entrance criteria - -- 1) The DUT supports the Query EI type procedure. -- 2) The test simulator has the functionality to initiate A1-EI Query EI type procedure. -- 3) The DUT and the test simulator have agreed on an EI type to use for this test. -- 4) The EI type identifier and the JSON schemas of the EI type used for this test are available and used in test simulator to formulate the Query EI request, and in DUT for selecting the appropriate schemas for the EI type object. - -##### 5.3.1.2.3 Test methodology - -###### 5.3.1.2.3.1 Initial conditions - -- 1) The DUT has A1-EI Producer service ready and available to receive HTTP requests from the test simulator. -- 2) The DUT has the EI type available. - -###### 5.3.1.2.3.2 Procedure - -Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.3.3 containing the known eiTypeId and empty message body. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 5.3.1.2.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "200 OK". -- 2) Response message body content contains an EiTypeObject representing the read EI job. - -#### 5.3.1.3 Query EI type (negative case) – eiTypeId not supported - -##### 5.3.1.3.1 Test description and applicability - -The purpose of this test case is to test query EI type functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.3.3. The expected outcome is failure due to eiTypeId not being supported. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Query EI type procedure. - -##### 5.3.1.3.2 Test entrance criteria - -The test entrance criteria specified in clause 5.3.1.2.2 applies, except that the agreed eiTypeId is NOT available in DUT. - -##### 5.3.1.3.3 Test methodology - -###### 5.3.1.3.3.1 Initial conditions - -The initial conditions specified in clause 5.3.1.2.3.1 applies. - -###### 5.3.1.3.3.2 Procedure - -Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.3.3 containing the unsupported eiTypeId and with empty message body. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 5.3.1.3.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "404 Not Found". - -NOTE: Presence or validation of optional ProblemDetails object in the response is not used to determine validation on this test. - -### 5.3.2 Create EI job test scenarios - -#### 5.3.2.1 Create EI job (positive case) - -##### 5.3.2.1.1 Test description and applicability - -This purpose of this test case is to test the create EI job functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.4.3. The expected outcome is successful creation of the EI job. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service. - -##### 5.3.2.1.2 Test entrance criteria - -- 1) The DUT and the test simulator have agreed on an EI type to use for this test. -- 2) The eiTypeId and the JSON schemas of the EI type used for this test are available and used in test simulator to formulate the Create EI job request, and in DUT to validate and handle the request. -- 3) The DUT supports the A1-EI Create EI job policy procedure. -- 4) The test simulator has the functionality to initiate Create EI job procedure. - -##### 5.3.2.1.3 Test methodology - -###### 5.3.2.1.3.1 Initial conditions - -- 1) The DUT has A1-EI Producer service ready and available to receive HTTP requests from the test simulator. -- 2) No EI job exists in the DUT for the agreed EI type with the same eiJobId that will be used by the test simulator. - -###### 5.3.2.1.3.2 Procedure - -Step 1. Send an HTTP PUT request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.3.3 including a new eiJobId, message body containing the EiJobObject in JSON format with the agreed eiTypeId included and conforming to the schema of the EI type. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 5.3.2.1.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "201 Created". -- 2) Response message body content contains an EiJobObject representing the created EI job. -- 3) The location header is present and carries the URI of the new EI job. - -#### 5.3.2.2 Create EI job (negative case) – eiTypeId not supported - -##### 5.3.2.2.1 Test description and applicability - -The purpose of this test case is to test the create EI job functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.4.3. The expected outcome is failure due to eiTypeId not being supported. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service - -##### 5.3.2.2.2 Test entrance criteria - -The test entrance criteria specified in clause 5.3.2.1.2 applies except that the agreed eiTypeId is NOT available in DUT. - -##### 5.3.2.2.3 Test methodology - -###### 5.3.2.2.3.1 Initial conditions - -The initial conditions specified in clause 5.3.2.1.3.1 applies. - -###### 5.3.2.2.3.2 Procedure - -Step 1. Send an HTTP PUT request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.3.3, and a message body containing the EiJobObject in JSON format including the unsupported eiTypeId. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 5.3.2.2.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "404 Not found". - -NOTE: Presence or validation of optional ProblemDetails object in the response is not used to determine validation on this test. - -#### 5.3.2.3 Create EI job (negative case) – schema validation failure - -##### 5.3.2.3.1 Test description and applicability - -The purpose of this test case is to test the create EI job functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.4.3. The expected outcome is failure due to schema validation failure. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service - -##### 5.3.2.3.2 Test entrance criteria - -The test entrance criteria specified in clause 5.3.2.1.2 applies. - -##### 5.3.2.3.3 Test methodology - -###### 5.3.2.3.3.1 Initial conditions - -The initial conditions specified in clause 5.3.2.1.3.1 applies. - -###### 5.3.2.3.3.2 Procedure - -Step 1. Send an HTTP PUT request from test simulator to DUT with the correct URI as specified in A1AP [4] clause 6.3.3 and a message body containing the EiJobObject in JSON format. A spelling mistake should be introduced in the EiJobObject for schema validation error in DUT. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 5.3.2.3.3.2 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "400 Bad Request". - -NOTE: Presence or validation of optional ProblemDetails object in the response is not used to determine validation on this test. - -### 5.3.3 Query EI jobs test scenarios - -#### 5.3.3.1 Query EI job identifiers for a single EI type (positive case) - -##### 5.3.3.1.1 Test description and applicability - -This purpose of this test case is to test query EI job identifiers functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.4.2. The expected outcome is successful retrieval of all EI job identifiers of a given EI type. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and Query EI job identifiers procedure. - -##### 5.3.3.1.2 Test entrance criteria - -- 1) The DUT supports the Query EI job identifiers procedure. -- 2) The test simulator has the functionality to initiate A1-EI Query EI job identifiers procedure. -- 3) The DUT and the test simulator have agreed on an EI type to use for this test. - -##### 5.3.3.1.3 Test methodology - -###### 5.3.3.1.3.1 Initial conditions - -- 1) The DUT has A1-EI Producer service ready and available to receive HTTP requests from the test simulator. -- 2) The DUT supports the three different test configurations listed below to test complete functionality: - - a) DUT has no EI job available for the agreed EI type - - b) DUT has a single EI job available for the agreed EI type - - c) DUT has two or more EI job available for the agreed EI type - -###### 5.3.3.1.3.2 Procedure - -Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.3.3 with the agreed eiTypeId as query parameter and with empty message body. - -Step 2. At the test simulator the received HTTP response is recorded. - -Step 3. Repeat Step 1 and Step 2 for the three test configurations. - -###### 5.3.3.1.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met for all three test configurations: - -- 1) The return code is "200 OK". -- 2) Response message body is validated depending on the three test configurations used in clause 5.3.3.1.3.1 - - a) If the DUT has no EI job available, message body is an empty array - - b) If the DUT has single EI job available, message body contains an array with one eiJobId available with the given EI type. - - c) If the DUT has two or more EI jobs available, message body contains an array of eiJobIds of all the available EI jobs of the given EI type. - -#### 5.3.3.2 Query EI job identifiers for a single EI type (negative case) – eiTypeId not supported - -##### 5.3.3.2.1 Test description and applicability - -This purpose of this test case is to test query EI job identifiers functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.4.2. The expected outcome is failure due to eiTypeId not being supported. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Query EI job identifiers procedure. - -##### 5.3.3.2.2 Test entrance criteria - -The test entrance criteria specified in clause 5.3.3.1.2 applies, except that the agreed eiTypeId is NOT available in DUT. - -##### 5.3.3.2.3 Test methodology - -###### 5.3.3.2.3.1 Initial conditions - -- 1) The DUT has A1-EI Producer service ready and available to receive HTTP requests from the test simulator. - -###### 5.3.3.2.3.2 Procedure - -- Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.3.3 with the unsupported eiTypeId included as query parameter and with empty message body. -- Step 2. At the test simulator the received HTTP response is recorded. - -###### 5.3.3.2.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "400 Bad request". - -NOTE: Presence or validation of optional ProblemDetails object in the response is not used to determine validation on this test. - -#### 5.3.3.3 Query EI job identifiers for all EI types (positive case) - -##### 5.3.3.3.1 Test description and applicability - -This purpose of this test case is to test query EI job identifiers functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.4.2. The expected outcome is successful retrieval of all EI job identifiers of all EI types. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and Query EI job identifiers procedure. - -##### 5.3.3.3.2 Test entrance criteria - -- 1) The DUT supports the Query EI job identifiers procedure. -- 2) The test simulator has the functionality to initiate A1-EI Query EI job identifiers procedure. -- 3) The DUT supports a known set of EI types (two or more) used for this test. - -##### 5.3.3.3.3 Test methodology - -###### 5.3.3.3.3.1 Initial conditions - -- 1) The DUT has A1-EI Producer service ready and available to receive HTTP requests from the test simulator. -- 2) The DUT supports the two different test configurations listed below to test complete functionality: - - a) DUT has no EI job available for any of the EI types supported. - - b) DUT has one or more EI jobs available for each EI type supported. - -###### 5.3.3.3.3.2 Procedure - -- Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.3.3 without eiTypeId included as query parameter and with empty message body. -- Step 2. At the test simulator the received HTTP response is recorded. - -Step 3. Repeat Step 1 and Step 2 for the two test configurations. - -###### 5.3.3.3.3.3 Expected result - -At the test simulator check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met for all two test configurations: - -- 1) The return code is "200 OK". -- 2) Response message body is validated depending on the two test configurations used in clause 5.3.3.3.3.1 - - a) If the DUT has no EI job available, message body is an empty array. - - b) If the DUT has one or more EI jobs available, message body contains an array of eiJobIds of all the available EI jobs of all EI types. - -#### 5.3.3.4 Query EI job (positive case) - -##### 5.3.3.4.1 Test description and applicability - -The purpose of this test case is to test query EI job functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.4.5. The expected outcome is successful retrieval of EI job for the given eiJobId. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Query EI job procedure. - -##### 5.3.3.4.2 Test entrance criteria - -- 1) The DUT supports the Query EI job procedure. -- 2) The test simulator has the functionality to initiate A1-EI Query EI job procedure. -- 3) An EI job exists in the DUT and the eiJobId is known to the test simulator. - -##### 5.3.3.4.3 Test methodology - -###### 5.3.3.4.3.1 Initial conditions - -- 1) The DUT has A1-EI Producer service ready and available to receive HTTP request from the test simulator. - -###### 5.3.3.4.3.2 Procedure - -Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.3.3 containing the known eiJobId and with empty message body. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 5.3.3.4.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "200 OK". -- 2) Response message body content contains an EiJobObject representing the read EI job. - -#### 5.3.3.5 Query EI job (negative case) – EI job does not exist - -##### 5.3.3.5.1 Test description and applicability - -The purpose of this test case is to test query EI job functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.4.5. The expected outcome is failure due to EI job being non-existent. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Query EI job procedure. - -##### 5.3.3.5.2 Test entrance criteria - -The test entrance criteria specified in clause 5.3.3.4.2 applies, additionally an eiJobId to use for which no EI job exist in the DUT is known in advance. - -##### 5.3.3.5.3 Test methodology - -###### 5.3.3.5.3.1 Initial conditions - -The initial conditions specified in clause 5.3.3.4.3.1 applies. - -###### 5.3.3.5.3.2 Procedure - -- Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.3.3 containing the eiJobId for which no EI job exist and with empty message body. -- Step 2. At the test simulator the received HTTP response is recorded. - -###### 5.3.3.5.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "404 Not Found". - -NOTE: Presence or validation of optional ProblemDetails object in the response is not used to determine validation on this test. - -### 5.3.4 Update EI job test scenarios - -#### 5.3.4.1 Update EI job (positive case) - -##### 5.3.4.1.1 Test description and applicability - -The purpose of this test case is to test update EI job functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.4.4. The expected outcome is successful update of the EI job. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and Update EI job procedure. - -##### 5.3.4.1.2 Test entrance criteria - -- 1) The DUT supports the Update EI job procedure. -- 2) The test simulator has the functionality to initiate Update EI job procedure. -- 3) An EI job exists in the DUT and the eiTypeID and eiJobID is known to the test simulator. -- 4) The EI type and the JSON schemas of the EI type used for this test are available and used in test simulator to formulate the Update EI job request, and in DUT to validate and handle the request. - -##### 5.3.4.1.3 Test methodology - -###### 5.3.4.1.3.1 Initial conditions - -- 1) The DUT has A1-EI Producer service ready and available to receive HTTP request from the test simulator. - -###### 5.3.4.1.3.2 Procedure - -Step 1. Send an HTTP PUT request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.3.3 and message body containing the EiJobObject in JSON format with the agreed eiTypeId included and confirming to the schema of the EI type. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 5.3.4.1.3.2 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "200 OK". -- 2) Response message body content contains an EiJobObject representing the updated EI job sent in Step 1. - -#### 5.3.4.2 Update EI job (negative case) – schema validation failure - -##### 5.3.4.2.1 Test description and applicability - -The purpose of this test case is to test update EI job functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.4.4. The expected outcome is failure to update the EI job due to schema validation failure. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and Update EI job procedure. - -##### 5.3.4.2.2 Test entrance criteria - -The test entrance criteria specified in clause 5.3.4.1.2 applies. - -##### 5.3.4.2.3 Test methodology - -###### 5.3.4.2.3.1 Initial conditions - -The initial conditions specified in clause 5.3.4.1.3.1 applies. - -###### 5.3.4.2.3.2 Procedure - -Step 1. Send an HTTP PUT request from test simulator to DUT with the correct URI as specified in A1AP [4] clause 6.3.3 and a message body containing the EiJobObject in JSON format. A spelling mistake should be introduced in the EiJobObject for schema validation error in the DUT. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 5.3.4.2.3.2 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "400 Bad Request". - -NOTE: Presence or validation of optional ProblemDetails object in the response is not used to determine validation on this test. - -### 5.3.5 Delete EI job test scenarios - -#### 5.3.5.1 Delete EI job (positive case) - -##### 5.3.5.1.1 Test description and applicability - -The purpose of this test case is to test the delete EI job functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.4.6. The expected outcome is successful deletion of EI job. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service. - -##### 5.3.5.1.2 Test entrance criteria - -- 1) The DUT supports the Delete EI job procedure. -- 2) The test simulator has the functionality to initiate A1-EI Delete EI job procedure. -- 3) An EI job exists in DUT and the eiJobId is known to test simulator. - -##### 5.3.5.1.3 Test methodology - -###### 5.3.5.1.3.1 Initial conditions - -- 1) The DUT has A1-EI Producer service ready and available to receive HTTP request from the test simulator. - -###### 5.3.5.1.3.2 Procedure - -Step 1. Send an HTTP DELETE request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.3.3 containing the known eiJobId and with empty message body. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 5.3.5.1.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "204 No Content" -- 2) The message body is empty. - -#### 5.3.5.2 Delete EI job (negative case) – EI job does not exist - -##### 5.3.5.2.1 Test description and applicability - -The purpose of this test case is to test the delete EI job functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.4.6. The expected outcome is failure due to EI job being non-existent. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service. - -##### 5.3.5.2.2 Test entrance criteria - -The test entrance criteria specified in clause 5.3.5.1.2 applies, additionally the eiJobId to use for which no EI job exists in the DUT is known in advance. - -##### 5.3.5.2.3 Test methodology - -###### 5.3.5.2.3.1 Initial conditions - -The initial conditions specified in clause 5.3.5.1.3.1 applies. - -###### 5.3.5.2.3.2 Procedure - -Step 1. Send an HTTP DELETE request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.3.3 containing the unsupported eiJobId and with empty message body. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 5.3.5.2.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "404 Not Found". - -NOTE: Presence or validation of optional ProblemDetails object in the response is not used to determine validation on this test. - -### 5.3.6 Status of EI jobs test scenarios - -#### 5.3.6.1 Query EI job status (positive case) - -##### 5.3.6.1.1 Test description and applicability - -The purpose of this test case is to test the query EI job status functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.4.7. The expected outcome is successful retrieval of EI job status object. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Query EI job status procedure. - -##### 5.3.6.1.2 Test entrance criteria - -- 1) The DUT supports the Query EI job status procedure. -- 2) The test simulator has the functionality to initiate A1-EI Query EI job status procedure. -- 3) An EI job exists in the DUT and test simulator is aware of the eiJobId. - -##### 5.3.6.1.3 Test methodology - -###### 5.3.6.1.3.1 Initial conditions - -- 1) The DUT has A1-EI Producer service ready and available to receive HTTP requests from the test simulator. - -###### 5.3.6.1.3.2 Procedure - -Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.3.3 containing the known eiJobId and with empty message body. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 5.3.6.1.3.3 Expected result - -Check the HTTP response recorded in step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "200 OK". -- 2) Response message body content contains an EiJobStatusObject representing the status of the EI job. - -#### 5.3.6.2 Query EI job status (negative case) EI job does not exist - -##### 5.3.6.2.1 Test description and applicability - -The purpose of this test case is to test the query EI job status functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.4.7. The expected outcome is failure due to EI job being non-existent. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Query EI job status procedure. - -##### 5.3.6.2.2 Test entrance criteria - -The test entrance criteria specified in clause 5.3.6.1.2 applies, additionally an eiJobId to use for which no EI job exist in the DUT is known in advance. - -##### 5.3.6.2.3 Test methodology - -###### 5.3.6.2.3.1 Initial conditions - -The initial conditions specified in clause 5.3.6.1.3.1 applies. - -###### 5.3.6.2.3.2 Procedure - -- Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.3.3 containing the eiJobId for which no EI job exist and with empty message body. -- Step 2. At the test simulator the received HTTP response is recorded. - -###### 5.3.6.2.3.2 Expected result - -Check the HTTP response recorded in step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "404 Not Found". - -NOTE: Presence or validation of optional ProblemDetails object in the response is not used to determine validation on this test. - -#### 5.3.6.3 Notify EI job status (positive case) - -##### 5.3.6.3.1 Test description and applicability - -This purpose of this test case is to test the notify EI job status functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.4.8. The expected outcome is successful request for EI job status. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and supports the Notify EI job status procedure. - -##### 5.3.6.3.2 Test entrance criteria - -The test entrance criteria for Create EI job specified in clause 5.3.2.1.2 applies. - -##### 5.3.6.3.3 Test methodology - -###### 5.3.6.3.3.1 Initial conditions - -The initial conditions for Create EI job specified in clause 5.3.2.1.3.1 applies. - -###### 5.3.6.3.3.2 Procedure - -Step 1. Same as for Create EI job, see clause 5.3.2.1.3.2, including the jobStatusNotificationUri parameter in the EiJobObject. - -Step 2. At the test simulator the received HTTP response is recorded. - -Step 3. Same as Step 1 but with another jobStatusNotificationUri parameter included. - -Step 4. At the test simulator the received HTTP response is recorded. - -Step 5. Same as Step 1 but without a jobStatusNotificationUri parameter included. - -Step 6. At the test simulator the received HTTP response is recorded. - -NOTE: Steps 3-4 and 5-6 correspond to the procedure for Update EI job but it is not required that the EiJobObject in the message body is modified in the test case for Notify EI job status except for the jobStatusNotificationUri. - -###### 5.3.6.3.3.3 Expected result - -Check the HTTP response recorded in Step 2, 4 and 6 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "201 Created" in Step 2. -- 2) The return code is "200 OK" in Step 4. -- 3) The return code is "200 OK" in Step 6. - -### 5.3.7 Deliver EI job result test scenarios - -#### 5.3.7.1 Deliver EI job result (positive case) - -##### 5.3.7.1.1 Test description and applicability - -This purpose of this test case is to test the deliver EI job result functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.5.2. The expected outcome is successful request for EI job results. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and supports the Deliver EI job result procedure. - -##### 5.3.7.1.2 Test entrance criteria - -The test entrance criteria for Create EI job specified in clause 5.3.2.1.2 applies. - -##### 5.3.7.1.3 Test methodology - -###### 5.3.7.1.3.1 Initial conditions - -The initial conditions for Create EI job specified in clause 5.3.2.1.3.1 applies. - -###### 5.3.7.1.3.2 Procedure - -Step 1. Same as for Create EI job, see clause 5.3.2.1.3.2, including the jobResultUri parameter in the EiJobObject. - -Step 2. At the test simulator the received HTTP response is recorded. - -Step 3. Same as Step 1 but with another jobResultUri parameter included. - -Step 4. At the test simulator the received HTTP response is recorded. - -NOTE: Steps 3-4 correspond to the procedure for Update EI job, but it is not required that the EiJobObject in the message body is modified in the test case for Deliver EI job status except for the jobResultUri. - -###### 5.3.7.1.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "201 Created" in Step 2. -- 2) The return code is "200 OK" in Step 4. - -#### 5.3.7.2 Deliver EI job result – no callback (negative case) - -##### 5.3.7.2.1 Test description and applicability - -This purpose of this test case is to test the deliver EI job result functionality of A1-EI Producer as specified in A1AP [4] clause 5.3.5.2. The expected outcome is successful request for EI job results. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and supports the Deliver EI job result procedure. - -##### 5.3.7.2.2 Test entrance criteria - -The test entrance criteria specified in clause 5.3.7.1.2 applies. - -##### 5.3.7.2.3 Test methodology - -###### 5.3.7.2.3.1 Initial conditions - -The initial conditions specified in clause 5.3.7.1.3.1 applies. - -###### 5.3.7.2.3.2 Procedure - -Step 1. Same as for Create EI job, see clause 5.3.2.1.3.2 but without a jobResultUri parameter included. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 5.3.7.2.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -The return code is "400 Bad request" in Step 2. - -# 6 Test cases for Near-RT RIC - -## 6.1 General - -### 6.1.1 Device under test requirements - -The Near-RT RIC that acts as Device Under Test (DUT) in the test scenarios of this clause can be a function that is under development, or it can be a finalised commercial product. The requirements on the DUT for these tests are that it can handle the procedures defined for a Near-RT RIC and the purpose of the test scenarios is to validate that it conforms to the A1 service definitions in A1AP [4], clause 5. - -In addition to the basic conformance requirements, the following is required for a Near-RT RIC when it acts as DUT: - -- It shall be possible for the DUT to initiate the A1-EI procedures in a controlled manner for each A1-EI related test case. -- For A1-P related test cases, it shall be possible for the DUT to support A1 policy types to use in the test cases after agreement with the test simulator. It shall be possible to validate PolicyObjects based on agreed policy types. -- For A1-EI related test cases, it shall be possible for the DUT to support EI types to use in the test cases after agreement with the test simulator. It shall be possible to validate EiJobStatusObjects based on agreed EI types, and it shall be possible to formulate EI jobs based on the schemas of the agreed EI types. - -NOTE: The present document does not require usage of any specific policy type or EI type since specific behaviour is not validated, only the application protocol aspects and procedures are validated for conformance testing of the A1 services. - -### 6.1.2 Test simulator capabilities - -The test simulator has the same basic capabilities as required for a Non-RT RIC. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analysing them regarding compliance to the A1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified based on the schemas of the agreed policy types and EI types. -- Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the A1 service definitions in A1AP [4], clause 5. - -## 6.2 Conformance Test Cases for A1-P Producer - -### 6.2.1 Query policy type test scenarios - -#### 6.2.1.1 Query all policy type identifiers (positive case) - -##### 6.2.1.1.1 Test description and applicability - -The purpose of this test case is to test the query policy types functionality of A1-P Producer as specified in A1AP [4] clause 5.2.3.2. The expected outcome is successful retrieval of policy type identifiers. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query all policy type identifiers procedure. - -##### 6.2.1.1.2 Test entrance criteria - -- 1) The DUT supports the Query all policy type identifiers procedure. -- 2) The test simulator has the functionality to initiate A1-P Query all policy type identifiers procedure. -- 3) A set of policy types (at least two) are supported in the DUT. - -##### 6.2.1.1.3 Test methodology - -###### 6.2.1.1.3.1 Initial conditions - -- 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. -- 2) The DUT supports the three different test configurations listed below to test complete functionality: - - a) DUT has no policy types available. - - b) DUT has a single policy type available. - - c) DUT has two or more policy types available. - -###### 6.2.1.1.3.2 Procedure - -Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3 and message body is empty. - -Step 2. At the test simulator the received HTTP response is recorded. - -Step 3. Repeat Step 1 and Step 2 for the three test configurations. - -###### 6.2.1.1.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met for all three test configurations listed in clause 6.2.1.1.3.1: - -- 1) The return code is "200 OK". -- 2) Response message body is validated depending on the three test configurations used: - - a) If the DUT has no policy types available, message body is an empty array - - b) If the DUT has single policy type available, message body contains an array with one policyTypeId. - - c) If the DUT has two or more policy types available, message body contains an array with all the policyTypeIds available in DUT. - -#### 6.2.1.2 Query single policy type (positive case) - -##### 6.2.1.2.1 Test description and applicability - -This purpose of this test case is to test the query policy type functionality of A1-P Producer as specified in A1AP [4] clause 5.2.3.3. The expected outcome is successful retrieval of the policy type object. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query single policy type procedure. - -##### 6.2.1.2.2 Test entrance criteria - -- 1) The DUT supports the Query single policy type procedure. - -- 2) The test simulator has the functionality to initiate A1-P Query single policy type procedure. -- 3) A known set of policy types are supported in the DUT. -- 4) The policy type identifier used for this test is known in advance and used in test simulator to formulate the Query single policy type request, and in the DUT for selecting the appropriate schemas for the policy type object. - -##### 6.2.1.2.3 Test methodology - -###### 6.2.1.2.3.1 Initial conditions - -- 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. -- 2) The DUT has the policy types available. - -###### 6.2.1.2.3.2 Procedure - -- Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3, including a known policyTypeId, and empty message body. -- Step 2. At the test simulator the received HTTP response is recorded. - -###### 6.2.1.2.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "200 OK". -- 2) Response message body content contains a PolicyTypeObject representing the read policy type. - -#### 6.2.1.3 Query single policy type (negative case) – policyTypeId not supported - -##### 6.2.1.3.1 Test description and applicability - -This purpose of this test case is to test the query policy type functionality of A1-P Producer as specified in A1AP [4] clause 5.2.3.3. The expected outcome is failure due to policyTypeId not being supported. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query single policy type procedure. - -##### 6.2.1.3.2 Test entrance criteria - -The test entrance criteria specified in clause 6.2.1.2.2 applies, except that the agreed policyTypeId is NOT available in DUT. - -##### 6.2.1.3.3 Test methodology - -###### 6.2.1.3.3.1 Initial conditions - -The initial conditions specified in clause 6.2.1.2.3.1 applies. - -###### 6.2.1.3.3.2 Procedure - -- Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3 containing the unsupported policyTypeId and with empty message body. -- Step 2. At the test simulator the received HTTP response is recorded. - -###### 6.2.1.3.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "404 Not Found". - -NOTE: Presence or validation of optional ProblemDetails object in the response is not used to determine validation on this test. - -### 6.2.2 Create policy test scenarios - -#### 6.2.2.1 Create single policy (positive case) - -##### 6.2.2.1.1 Test description and applicability - -This purpose of this test case is to test the create policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.3. The expected outcome is successful creation of the policy. - -This test case is conditionally mandatory if the DUT claims to support A1-P service. - -##### 6.2.2.1.2 Test entrance criteria - -- 1) The DUT supports the A1-P Create single policy procedure. -- 2) The test simulator has the functionality to initiate A1-P Create single policy procedure. -- 3) DUT and the test simulator have agreed on a policy type to use for this test. -- 4) The policyTypeId and the JSON schemas of the policy type used for this test are available and used in test simulator to formulate the Create single policy request, and in DUT to validate and handle the request. - -##### 6.2.2.1.3 Test methodology - -###### 6.2.2.1.3.1 Initial conditions - -- 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. -- 2) No policy exists in the DUT for the agreed policy type with the same policyId that will be used by the test simulator. - -###### 6.2.2.1.3.2 Procedure - -- Step 1. Send an HTTP PUT request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3 including policyTypeId and a new policyId, and message body containing the PolicyObject in JSON format conforming to the schema of the used policy type. -- Step 2. At the test simulator the received HTTP response is recorded. - -###### 6.2.2.1.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "201 Created". -- 2) Response message body content contains a PolicyObject representing the created policy. -- 3) The location header is present and carries the URI of the new policy. - -#### 6.2.2.2 Create policy (negative case) - schema validation failure - -##### 6.2.2.2.1 Test description and applicability - -This purpose of this test case is to test the create policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.3. The expected outcome is failure due to schema validation failure. - -This test case is conditionally mandatory if the DUT claims to support A1-P service. - -##### 6.2.2.2.2 Test entrance criteria - -The test entrance criteria specified in clause 6.2.6.1.2 applies. - -##### 6.2.2.2.3 Test methodology - -###### 6.2.2.2.3.1 Initial conditions - -The initial conditions specified in clause 6.2.6.1.3.1 applies. - -###### 6.2.2.2.3.2 Procedure - -Step 1. Send an HTTP PUT request from test simulator to DUT with the correct URI as specified in A1AP [4] clause 6.2.3 and a message body containing the PolicyObject in JSON format. A spelling mistake should be introduced in the PolicyObject for schema validation error in DUT. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 6.2.2.2.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "400 Bad Request". - -NOTE: Presence or validation of optional ProblemDetails object in the response is not used to determine validation on this test. - -#### 6.2.2.3 Create policy (negative case) – policyTypeId not supported - -##### 6.2.2.3.1 Test description and applicability - -This purpose of this test case is to test the create policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.3. The expected outcome is failure due to policyTypeId not being supported. - -This test case is conditionally mandatory if the DUT claims to support A1-P service. - -##### 6.2.2.3.2 Test entrance criteria - -The test entrance criteria specified in clause 6.2.6.1.2 applies except that the agreed policyTypeId is NOT available in DUT. - -##### 6.2.2.3.3 Test methodology - -###### 6.2.2.3.3.1 Initial conditions - -The initial conditions specified in clause 6.2.6.1.3.1 applies. - -###### 6.2.2.3.3.2 Procedure - -- Step 1. Send an HTTP PUT request from test simulator to DUT with the incorrect URI, i.e., containing the not supported policyTypeId, and a message body containing the PolicyObject in JSON format. -- Step 2. At the test simulator the received HTTP response is recorded. - -###### 6.2.2.3.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "404 Not Found". - -NOTE: Presence or validation of optional ProblemDetails object in the response is not used to determine validation on this test. - -### 6.2.3 Query policy test scenarios - -#### 6.2.3.1 Query all policy identifiers (positive case) - -##### 6.2.3.1.1 Test description and applicability - -The purpose of this test case is to test the query policies functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.2. The expected outcome is successful retrieval of policy identifiers. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query all policy identifiers procedure. - -##### 6.2.3.1.2 Test entrance criteria - -- 1) The DUT supports Query all policy identifiers procedure. -- 2) The test simulator has the functionality to initiate A1-P Query all policy identifiers procedure. -- 3) The DUT and the test simulator have agreed on a policy type to use for this test. - -##### 6.2.3.1.3 Test methodology - -###### 6.2.3.1.3.1 Initial conditions - -- 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. -- 2) The DUT supports the three different test configurations listed below to test complete functionality: - - a) DUT has no policies available for the agreed policy type - - b) DUT has a single policy available for the agreed policy type - - c) DUT has two or more policies available for the agreed policy type - -###### 6.2.3.1.3.2 Procedure - -- Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3 and empty message body. -- Step 2. At the test simulator the received HTTP response is recorded. - -Step 3. Repeat Step 1 and Step 2 for the three test configurations - -###### 6.2.3.1.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met for all three test configurations specified in clause 6.2.3.1.3.1: - -- 1) The return code is "200 OK". -- 2) Response message body is validated depending on the three test configurations used: - - a) If the DUT has no policies available, message body is an empty array - - b) If the DUT has single policy available, message body contains an array with one policyId available with the given policy type. - - c) If the DUT has two or more policies available, message body contains an array of policyIds of all the available policies of the given policy type. - -#### 6.2.3.2 Query all policy identifiers (negative case) – policyTypeId not supported - -##### 6.2.3.2.1 Test description and applicability - -The purpose of this test case is to test the query policies functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.2. The expected outcome is failure due to policyTypeId not being supported. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query all policy identifiers procedure. - -##### 6.2.3.2.2 Test entrance criteria - -The test entrance criteria specified in clause 6.2.3.1.2 applies, except that the agreed policyTypeId is NOT available in DUT. - -##### 6.2.3.2.3 Test methodology - -###### 6.2.3.2.3.1 Initial conditions - -- 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. - -###### 6.2.3.2.3.2 Procedure - -- Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3 and empty message body. -- Step 2. At the test simulator the received HTTP response is recorded. - -###### 6.2.3.2.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The appropriate error code "404 Not Found" is returned. - -NOTE: Presence or validation of optional ProblemDetails object in the response is not used to determine validation on this test. - -#### 6.2.3.3 Query single policy (positive case) - -##### 6.2.3.3.1 Test description and applicability - -The purpose of this test case is to test the query policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.5. The expected outcome is successful retrieval of policy object. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query single policy procedure. - -##### 6.2.3.3.2 Test entrance criteria - -- 1) A policy exists in the DUT and test simulator is aware of the policyTypeId and policyId -- 2) The DUT supports the Query single policy procedure. -- 3) The test simulator has the functionality to initiate A1-P Query single policy procedure. - -##### 6.2.3.3.3 Test methodology - -###### 6.2.3.3.3.1 Initial conditions - -- 1) The DUT supports the Query single policy procedure. -- 2) The test simulator has the functionality to initiate A1-P Query single policy procedure. - -###### 6.2.3.3.3.2 Procedure - -- Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3 and empty message body. -- Step 2. At the test simulator the received HTTP response is recorded. - -###### 6.2.3.3.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "200 OK". -- 2) Response message body content contains a PolicyObject representing the read policy. - -#### 6.2.3.4 Query single policy (negative case) – policy does not exist - -##### 6.2.3.4.1 Test description and applicability - -The purpose of this test case is to test the query policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.5. The expected outcome is failure due to policy being non-existent. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query single policy procedure. - -##### 6.2.3.4.2 Test entrance criteria - -- 1) The DUT supports Query single policy procedure. -- 2) The test simulator has the functionality to initiate A1-P Query single policy procedure. -- 3) test simulator is aware of the policyTypeId and policyId to use for which no policy exists in the DUT. - -##### 6.2.3.4.3 Test methodology - -###### 6.2.3.4.3.1 Initial conditions - -- 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. - -###### 6.2.3.4.3.2 Procedure - -Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3 and empty message body. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 6.2.3.4.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "404 Not Found". - -NOTE: Presence or validation of optional ProblemDetails object in the response is not used to determine validation on this test. - -#### 6.2.3.5 Query policy status (positive case) - -##### 6.2.3.5.1 Test description and applicability - -The purpose of this test case is to test the query policy status functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.7. The expected outcome is successful retrieval of policy status object. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query policy status procedure. - -##### 6.2.3.5.2 Test entrance criteria - -- 1) The DUT supports the Query policy status procedure. -- 2) The test simulator has the functionality to initiate A1-P Query policy status procedure. -- 3) A policy exists in the DUT and the policyTypeId and policyId is known to the test simulator. - -##### 6.2.3.5.3 Test methodology - -###### 6.2.3.5.3.1 Initial conditions - -- 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. - -###### 6.2.3.5.3.2 Procedure - -Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in in A1AP [4] clause 6.2.3 and empty message body. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 6.2.3.5.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "200 OK". -- 2) Response message body content contains a PolicyStatusObject representing the status of the policy. - -#### 6.2.3.6 Query policy status (negative case) – policy does not exist - -##### 6.2.3.6.1 Test description and applicability - -The purpose of this test case is to test the query policy status functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.7. The expected outcome is failure due to policy being non-existent. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query policy status procedure. - -##### 6.2.3.6.2 Test entrance criteria - -- 1) The DUT supports Query policy status procedure. -- 2) The test simulator has the functionality to initiate A1-P Query policy status procedure. -- 3) Test simulator is aware of the policyTypeId and policyId to use for which no policy exists in the DUT. - -##### 6.2.3.6.3 Test methodology - -###### 6.2.3.6.3.1 Initial conditions - -- 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. -- 2) No policy exists for the policyTypeId and policyId that will be used by the test simulator. - -###### 6.2.3.6.3.2 Procedure - -Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3 and empty message body. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 6.2.3.6.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "404 Not Found". - -NOTE: Presence or validation of optional ProblemDetails object in the response is not used to determine validation on this test. - -### 6.2.4 Update policy test scenarios - -#### 6.2.4.1 Update single policy (positive case) - -##### 6.2.4.1.1 Test description and applicability - -The purpose of this test case is to test the update policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.4. The expected outcome is successful update of the policy. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Update single policy procedure. - -##### 6.2.4.1.2 Test entrance criteria - -- 1) The DUT supports the Update single policy procedure. -- 2) The test simulator has the functionality to initiate A1-P Update single policy procedure. -- 3) A policy exists in the DUT and the policyTypeId and policyId is known to the test simulator. -- 4) Policy type identifiers used for this test are known in advance and used in DUT to formulate the Update single policy request, in test simulator for selecting the appropriate schemas for the policy type object. - -##### 6.2.4.1.3 Test methodology - -###### 6.2.4.1.3.1 Initial conditions - -- 1) The DUT has A1-P Producer service ready and available to receive HTTP request from the test simulator. - -###### 6.2.4.1.3.2 Procedure - -- Step 1. Send an HTTP PUT request from test simulator to DUT with the correct URI as specified in A1AP [4] clause 6.2.3 and message body containing the PolicyObject in JSON format. -- Step 2. At the test simulator the received HTTP response is recorded. - -###### 6.2.4.1.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "200 OK". -- 2) Response message body content is verified to match the PolicyObject sent in Step 1. - -#### 6.2.4.2 Update single policy (negative case) – schema validation failure - -##### 6.2.4.2.1 Test description and applicability - -The purpose of this test case is to test the update policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.4. The expected outcome is failure due to schema validation failure. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and the Update single policy procedure. - -##### 6.2.4.2.2 Test entrance criteria - -The test entrance criteria specified in clause 6.2.6.1.2 applies. - -##### 6.2.4.2.3 Test methodology - -###### 6.2.4.2.3.1 Initial conditions - -The initial conditions specified in clause 6.2.4.1.3.1 applies. - -###### 6.2.4.2.3.2 Procedure - -- Step 1. Send an HTTP PUT request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3 and a message body containing the PolicyObject in JSON format. A spelling mistake should be introduced in the PolicyObject for schema validation error in DUT - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 6.2.4.2.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "400 Bad Request". - -NOTE: Presence or validation of optional ProblemDetails object in the response is not used to determine validation on this test. - -### 6.2.5 Delete policy test scenarios - -#### 6.2.5.1 Delete single policy (positive case) - -##### 6.2.5.1.1 Test description and applicability - -This purpose of this test case is to test the delete policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.6. The expected outcome is successful deletion of the policy - -This test case is conditionally mandatory if the DUT claims to support A1-P service. - -##### 6.2.5.1.2 Test entrance criteria - -- 1) The DUT supports the Delete policy procedure -- 2) The test simulator has the functionality to initiate Delete policy procedure. -- 3) A policy exists in the DUT and the policyTypeId and policyId is known to the test simulator. - -##### 6.2.5.1.3 Test methodology - -###### 6.2.5.1.3.1 Initial conditions - -- 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. - -###### 6.2.5.1.3.2 Procedure - -Step 1. Send an HTTP DELETE request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3. - -Step 2. At the test simulator the received HTTP response is recorded. - -###### 6.2.5.1.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "204 No content". -- 2) Response message body is empty. - -#### 6.2.5.2 Delete single policy (negative case) – policy does not exist - -##### 6.2.5.2.1 Test description and applicability - -This purpose of this test case is to test the delete policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.6. The expected outcome is failure due to policy being non-existent. - -This test case is conditionally mandatory if the DUT claims to support A1-P service. - -##### 6.2.5.2.2 Test entrance criteria - -- 1) The DUT supports the Delete single procedure. -- 2) The test simulator has the functionality to initiate Delete single policy procedure. -- 3) Test simulator is aware of the policyTypeId and policyId to use for which no policy exists in the DUT. - -##### 6.2.5.2.3 Test methodology - -###### 6.2.5.2.3.1 Initial conditions - -- 1) DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. -- 2) No policy exists in DUT for the policyTypeId and policyId that will be used by the test simulator. - -###### 6.2.5.2.3.2 Procedure - -- Step 1. Send an HTTP DELETE request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3 and empty message body. -- Step 2. At the test simulator the received HTTP response is recorded. - -###### 6.2.5.2.3.3 Expected result - -Check the HTTP response recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "404 Not Found". - -NOTE: Presence or validation of optional ProblemDetails object in the response is not used to determine validation on this test. - -### 6.2.6 Notify policy status test scenarios - -#### 6.2.6.1 Notify policy status (positive case) - -##### 6.2.6.1.1 Test description and applicability - -This purpose of this test case is to test the policy status notification functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.8. The expected outcome is successful request for policy status. - -This test case is conditionally mandatory if the DUT claims to support A1-P service and supports the Notify policy status procedure. - -##### 6.2.6.1.2 Test entrance criteria - -The test entrance criteria for Create single policy specified in clause 6.2.2.1.2 applies. - -##### 6.2.6.1.3 Test methodology - -###### 6.2.6.1.3.1 Initial conditions - -The initial conditions for Create single policy specified in clause 6.2.2.1.3.1 applies. - -###### 6.2.6.1.3.2 Procedure - -Step 1. Same as for Create single policy, see clause 6.2.2.1.3.2, including the notificationDestination query parameter. - -Step 2. At the test simulator the received HTTP response is recorded. - -Step 3. Same as Step 1 but with another notificationDestination query parameter included. - -Step 4. At the test simulator the received HTTP response is recorded. - -Step 5. Same as Step 1 but without a notificationDestination query parameter included. - -Step 6. At the test simulator the received HTTP response is recorded. - -NOTE: Steps 3-4 and 5-6 correspond to the procedure for Update single policy but it is not required that the PolicyObject in the message body is modified in the test case for Notify policy status. - -###### 6.2.6.1.3.3 Expected result - -Check the HTTP response recorded in Step 2, 4 and 6 of procedure. - -The test is considered passed if the following conditions are met: - -- 1) The return code is "201 Created" in Step 2. -- 2) The return code is "200 OK" in Step 4. -- 3) The return code is "200 OK" in Step 6. - -## 6.3 Conformance test cases for A1-EI Consumer - -### 6.3.1 Query EI types test scenarios - -#### 6.3.1.1 Query EI type identifiers (positive case) - -##### 6.3.1.1.1 Test description and applicability - -The purpose of this test case is to test query EI type identifiers functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.3.2. The expected outcome is successful validation of the Query EI type identifiers request. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Query EI type identifiers procedure. - -##### 6.3.1.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate A1-EI Query EI type identifiers procedure. -- 2) The test simulator supports the Query EI type identifiers procedure. - -##### 6.3.1.1.3 Test methodology - -###### 6.3.1.1.3.1 Initial conditions - -- 1) The test simulator has A1-EI Producer service ready and available to receive HTTP requests from the DUT. - -###### 6.3.1.1.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Query EI type identifiers request. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in A1AP [4] clause 6.3.3. -- b) The HTTP request is a GET operation. -- c) The message body is empty. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.3.3.2.1. - -###### 6.3.1.1.3.3 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 6.3.1.2 Query EI type (positive case) - -##### 6.3.1.2.1 Test description and applicability - -The purpose of this test case is to test query EI type functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.3.3. The expected outcome is successful validation of the Query EI type request. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Query EI type procedure. - -##### 6.3.1.2.2 Test entrance criteria - -- 1) The DUT has the functionality to initiate A1-P Query EI type procedure. -- 2) A known set of EI types are supported in the test simulator. -- 3) The EI type identifier used for this test is known in advance and available in DUT to send the Query EI type request for the corresponding EI type and used by the test simulator for selecting the appropriate schemas for the EI job object. - -##### 6.3.1.2.3 Test methodology - -###### 6.3.1.2.3.1 Initial conditions - -- 1) The test simulator has A1-EI Producer service ready and available to receive HTTP requests from the DUT. -- 2) The test simulator has EI types available. - -###### 6.3.1.2.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Query EI type request with a known eiTypeId. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a) The HTTP request is a GET operation. -- b) The URI conforms to the format specified in A1AP [4] clause 6.3.3. -- c) The HTTP request message body is empty. -- d) The eiTypeId in the URI match the EI type being queried. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.3.3.3.1. - -###### 6.3.1.2.3.3 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 6.3.2 Create EI job test scenarios - -#### 6.3.2.1 Create EI job (positive case) - -##### 6.3.2.1.1 Test description and applicability - -This purpose of this test case is to test the create EI job functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.3. The expected outcome is successful validation of the EI job creation request. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service. - -##### 6.3.2.1.2 Test entrance criteria - -- 1) The DUT and the test simulator have agreed on an EI type to use for this test. -- 2) The eiTypeId and the JSON schemas of the EI type used for this test are available and used in DUT to formulate the Create EI job request, and in test simulator to validate the request. -- 3) The DUT has the functionality to initiate A1-EI Create EI job procedure. - -##### 6.3.2.1.3 Test methodology - -###### 6.3.2.1.3.1 Initial conditions - -- 1) The test simulator has A1-EI Producer service ready and available to receive HTTP requests from the DUT. -- 2) No EI job exists in the test simulator for the agreed EI type with the same eiJobId that will be used by the DUT. - -NOTE: The DUT is required to generate a unique eiJobId during the Create EI job procedure (see A1AP [4] clause 5.3.4.3). - -###### 6.3.2.1.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Create EI job request for the agreed EI type. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in A1AP [4] clause 6.3.3. -- b) The HTTP request is a PUT operation. -- c) The eiTypeId is supported. -- d) An EI job with the eiJobId does not exist. - -- e) The HTTP request message body contains the EiJobObject of the EI job to be created and the EiJobObject conforms to the schema. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.3.4.3.1. - -###### 6.3.2.1.3.3 Expected result - -The test is considered passed if Step 3 validation has passed. - -NOTE: Presence or validation of optional parameter for jobStatusNotificationUri is not used to determine validation on this test. - -### 6.3.3 Query EI jobs test scenarios - -#### 6.3.3.1 Query EI job identifiers for a single EI type (positive case) - -##### 6.3.3.1.1 Test description and applicability - -The purpose of this test case is to test query EI job identifiers functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.2. The expected outcome is successful validation of the Query EI job identifiers request querying for a single EI type. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Query EI job identifiers procedure. - -##### 6.3.3.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate A1-EI Query EI job identifiers procedure. -- 2) An EI type is agreed to be used in this test and the eiTypeId is known in advance. -- 3) A set of EI jobs (at least two) exist in the test simulator for the agreed EI type. - -##### 6.3.3.1.3 Test methodology - -###### 6.3.3.1.3.1 Initial conditions - -- 1) The test simulator has A1-EI Producer service ready and available to receive HTTP requests from the DUT. -- 2) The test simulator has EI jobs available for the agreed EI type. - -###### 6.3.3.1.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Query EI job identifiers request for the agreed EI type. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a) The HTTP request is a GET operation. -- b) The URI conforms to the format specified in A1AP [4] clause 6.3.3. -- c) The message body is empty. -- d) A query parameter with an eiTypeId is included. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.3.4.2.1. - -###### 6.3.3.1.3.3 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 6.3.3.2 Query EI job identifiers for all EI types (positive case) - -##### 6.3.3.2.1 Test description and applicability - -The purpose of this test case is to test query EI job identifiers functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.2. The expected outcome is successful validation of the Query EI job identifiers request querying for all EI types. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Query EI job identifiers procedure. - -##### 6.3.3.2.2 Test entrance criteria - -- 1) The DUT has functionality to initiate A1-EI Query EI job identifiers procedure. -- 2) The test simulator supports at least one EI type. - -##### 6.3.3.2.3 Test methodology - -###### 6.3.3.2.3.1 Initial conditions - -- 1) The test simulator has A1-EI Producer service ready and available to receive HTTP requests from the DUT. -- 2) One or more EI jobs exist in the test simulator for each EI type supported. - -###### 6.3.3.2.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Query EI job identifiers request for all EI types. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in A1AP [4] clause 6.3.3. -- b) The HTTP request is a GET operation. -- c) No query parameter with an eiTypeId is included. -- d) The message body is empty. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.3.4.2.1. - -###### 6.3.3.2.3.3 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 6.3.3.3 Query EI job (positive case) - -##### 6.3.3.3.1 Test description and applicability - -The purpose of this test case is to test query EI job functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.5. The expected outcome is successful validation of the Query EI job request. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Query EI job procedure. - -##### 6.3.3.3.2 Test entrance criteria - -- 1) The DUT has functionality to initiate A1-EI Query EI job procedure. -- 2) An EI job exists in test simulator and DUT is aware of the eiJobId. - -##### 6.3.3.3.3 Test methodology - -###### 6.3.3.3.3.1 Initial conditions - -- 1) The test simulator has A1-EI Producer service ready and available to receive HTTP request from the DUT. - -###### 6.3.3.3.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Query EI job request for the existing EI job identified by the eiJobId. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in A1AP [4] clause 6.3.3. -- b) The HTTP request is a GET operation. -- c) The eiJobId in the URI match the EI job being queried. -- d) The HTTP request message body is empty. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.3.4.5.1. - -###### 6.3.3.3.3.3 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 6.3.4 Update EI job test scenarios - -#### 6.3.4.1 Update EI job (positive case) - -##### 6.3.4.1.1 Test description and applicability - -The purpose of this test case is to test update EI job functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.4. The expected outcome is successful validation of the Update EI job request. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Update EI job procedure. - -##### 6.3.4.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate A1-EI Update Job procedure. -- 2) An EI job exists in test simulator and DUT is aware of the eiTypeId and eiJobId -- 3) The eiTypeId and the JSON schemas of the EI job type used for this test are available in DUT to formulate the Update EI job request and used by the test simulator for validation purpose. - -##### 6.3.4.1.3 Test methodology - -###### 6.3.4.1.3.1 Initial conditions - -- 1) The test simulator has A1-EI Producer service ready and available to receive HTTP request from the DUT. - -###### 6.3.4.1.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Update EI job request for the existing EI job identified by the eiJobId. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in A1AP [4] clause 6.3.3. -- b) The HTTP request is a PUT operation -- c) The eiJobId in the URI match the EI job to be updated. -- d) The HTTP request message body contains the EiJobObject of the EI job being updated with the correct eiTypeId included and the EiJobObject conforms to the schema of the EI type. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.3.4.4.1. - -###### 6.3.4.1.3.3 Expected result - -The test is considered passed if Step 3 validation has passed. - -NOTE: Presence or validation of optional query parameter for jobStatusNotificationUri is not used to determine validation on this test - -### 6.3.5 Delete EI job test scenarios - -#### 6.3.5.1 Delete EI job (positive case) - -##### 6.3.5.1.1 Test description and applicability - -The purpose of this test case is to test the delete EI job functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.6. The expected outcome is successful validation of the Delete EI job request - -This test case is conditionally mandatory if the DUT claims to support A1-EI service. - -##### 6.3.5.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate A1-EI Delete EI job procedure. -- 2) An EI job exists in test simulator and the eiJobId is known to DUT. - -##### 6.3.5.1.3 Test methodology - -###### 6.3.5.1.3.1 Initial conditions - -- 1) The test simulator has A1-EI Producer service ready and available to receive HTTP request from the DUT. - -###### 6.3.5.1.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Delete EI job request for the existing EI job identified by the eiJobId. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in A1AP [4] clause 6.3.3. -- b) The HTTP request is a DELETE operation. -- c) The eiJobId in the URI match the EI job being deleted. -- d) The HTTP request message body is empty. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.3.4.6.1. - -###### 6.3.5.1.3.3 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 6.3.6 Status of EI jobs test scenarios - -#### 6.3.6.1 Query EI job status (positive case) - -##### 6.3.6.1.1 Test description and applicability - -The purpose of this test case is to test the query EI job status functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.7. The expected outcome is successful validation of the Query EI job status request. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Query EI job status procedure. - -##### 6.3.6.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate A1-EI Query EI job status procedure. -- 2) An EI job exists in test simulator and DUT is aware of the eiJobId. - -##### 6.3.6.1.3 Test methodology - -###### 6.3.6.1.3.1 Initial conditions - -- 1) The test simulator has A1-EI Producer service ready and available to receive HTTP request from the DUT. - -###### 6.3.6.1.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Query EI job status request for the existing EI job identified by the eiJobId. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in A1AP [4] clause 6.3.3. -- b) The HTTP request is a GET operation. -- c) The eiJobId in the URI match the EI job being queried. - -- d) The HTTP request message body is empty. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.3.4.7.1. - -###### 6.3.6.1.3.3 Expected result - -The test is considered passed if Step 3 validation has passed and HTTP response "200 OK" is sent. - -#### 6.3.6.2 Notify EI job status (positive case) - -##### 6.3.6.2.1 Test description and applicability - -This purpose of this test case is to test the notify EI job status functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.8. The expected outcome is successful EI job status notification request and reception. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and supports the Notify EI job procedure. - -##### 6.3.6.2.2 Test entrance criteria - -The test entrance criteria for Create EI job specified in clause 6.3.2.1.2 applies. And in addition: - -- 1) The DUT has the functionality to request and receive EI job status notifications. - -##### 6.3.6.2.3 Test methodology - -###### 6.3.6.2.3.1 Initial conditions - -The initial conditions for Create EI job specified in clause 6.3.2.1.3.1 applies. And in addition: - -- 1) The test simulator supports generation of an EiJobStatusObject based on the EI job status schema of the agreed EI type used for this test. -- 2) The DUT has HTTP server ready and available to receive HTTP requests from the test simulator. - -NOTE: The DUT is expected to provide callback URI (jobStatusNotificationUri) during the Create EI job procedure (see A1AP [4] clause 5.3.4.43) for which it can relate received EI job status notifications to the eiJobId that was generated when creating the EI job for which EI job status notifications is requested. - -###### 6.3.6.2.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Create EI job request for the agreed EI job type including the jobStatusNotificationUri parameter in the EiJobObject. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a)-e) as defined for Create EI job in clause 6.3.2.1.3.2. -- f) The jobStatusNotificationUri parameter is included in the EiJobObject. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.3.4.3.1. - -Step 5. The test simulator initiates the Notify EI job status procedure and sends a HTTP POST request to the provided callback URI (jobStatusNotificationUri) in the DUT with message body containing the EiJobStatusObject conforming to the schema of the used EI type. - -Step 6. At the test simulator the received HTTP response is recorded. - -NOTE: For the time between Step 4 and Step 5, the test simulator need not simulate any change in job status but can send status update directly with any content that conforms to the status schema of the used EI type. - -###### 6.3.6.2.3.3 Expected result - -The test is considered passed if the following conditions are met: - -- 1) Step 3 validation has passed -- 2) Check the HTTP response recorded in step 6 of procedure and that the return code is "204 No content". - -#### 6.3.6.3 Notify EI job status – schema validation failure (negative case) - -##### 6.3.6.3.1 Test description and applicability - -This purpose of this test case is to test the notify EI job status functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.8. The expected outcome is failure due to schema validation failure. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service and supports the Notify EI job status procedure. - -##### 6.3.6.3.2 Test entrance criteria - -The test entrance criteria in clause 6.3.6.2.2 applies. - -##### 6.3.6.3.3 Test methodology - -###### 6.3.6.3.3.1 Initial conditions - -The initial conditions in clause 6.3.6.2.3.1 applies. - -###### 6.3.6.3.3.2 Procedure - -Steps 1-6 of clause 6.3.6.2.3.2 applies with the following modification: - -In Step 5: A spelling mistake should be introduced in the EiJobStatusObject for schema validation error in DUT. - -###### 6.3.6.3.3.3 Expected result - -The test is considered passed if the following conditions are met: - -- 1) Step 3 validation has passed -- 2) Check the HTTP response recorded in step 6 of procedure and that the return code is "400 Bad request". - -#### 6.3.6.4 Void - -### 6.3.7 Deliver EI job result test scenarios - -#### 6.3.7.1 Deliver EI job result (positive case) - -##### 6.3.7.1.1 Test description and applicability - -This purpose of this test case is to test the deliver EI job result functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.5.2. The expected outcome is successful EI job result request and reception. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service. - -##### 6.3.7.1.2 Test entrance criteria - -The test entrance criteria for Create EI job specified in clause 6.3.2.1.2 applies. - -NOTE: No specific functionality is needed in DUT to request EI job results as it is covered by Create EI job procedure. - -##### 6.3.7.1.3 Test methodology - -###### 6.3.7.1.3.1 Initial conditions - -The initial conditions for Create EI job specified in clause 6.3.2.1.3.1 applies. And in addition: - -- 1) The test simulator supports generation of an EiJobResultObject based on the EI job result schema of the agreed EI type used for this test. -- 2) The DUT has HTTP server ready and available to receive HTTP requests from the test simulator. - -NOTE: The DUT is expected to provide callback URI (jobResultUri) during the Create EI job procedure (see A1AP [4] clause 5.3.4.3) for which it can relate received EI job results to the eiJobId that was generated when creating the EI job for which EI job result is delivered. - -###### 6.3.7.1.3.2 Procedure - -Step 1. Initiate appropriate action in the DUT to initiate Create EI job request for the agreed EI job type including the jobResultUri parameter in the EiJobObject. - -Step 2. At the test simulator the contents of the received HTTP request are recorded. - -Step 3. The test simulator does the following validation: - -- a)-e) as defined for Create EI job in clause 6.3.2.1.3.2. -- f) The jobResultUri parameter is included in the EiJobObject. - -Step 4. The test simulator generates the appropriate HTTP response as specified in A1AP [4] clause 5.3.4.3.1. - -Step 5. The test simulator initiates the Deliver EI job result procedure and sends a HTTP POST request to the provided callback URI (jobResultUri) in the DUT with message body containing the EiJobResultObject conforming to the schema of the used EI type. - -Step 6. At the test simulator the received HTTP response is recorded. - -NOTE: For the time between Step 4 and Step 5, the test simulator need not follow the timing attributes in the EiJobObject if such are defined for the used EI type but can send the job delivery directly with any content that conforms to the result schema of the used EI type. - -###### 6.3.7.1.3.3 Expected result - -The test is considered passed if the following conditions are met: - -- 1) Step 3 validation has passed -- 2) Check the HTTP response recorded in step 6 of procedure and that the return code is "204 No content". - -#### 6.3.7.2 Deliver EI job result – schema validation failure (negative case) - -##### 6.3.7.2.1 Test description and applicability - -This purpose of this test case is to test the deliver EI job result functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.5.2. The expected outcome is failure due to schema validation failure. - -This test case is conditionally mandatory if the DUT claims to support A1-EI service - -##### 6.3.7.2.2 Test entrance criteria - -The test entrance criteria in clause 6.3.7.1.2 applies. - -##### 6.3.7.2.3 Test methodology - -##### 6.3.7.2.3.1 Initial conditions - -The initial conditions in clause 6.3.7.1.3.1 applies. - -#### 6.3.7.2.3.2 Procedure - -Steps 1-6 of clause 6.3.7.1.3.2 applies with the following modification: - -In Step 5: A spelling mistake should be introduced in the EiJobResultObject for schema validation error in DUT. - -#### 6.3.7.2.3.3 Expected result - -The test is considered passed if the following conditions are met: - -- 1) Step 3 validation has passed -- 2) Check the HTTP response recorded in step 6 of procedure and that the return code is "400 Bad request". - -### 6.3.7.3 Void - ---- - -## 7 Test cases for interoperability between Non-RT RIC and Near-RT RIC - -### 7.1 General - -#### 7.1.1 System under test requirements - -The system under test is a Non-RT RIC and a Near-RT RIC that acts as DUTs referred to Non-RTR-DUT and Near-RTR-DUT in the test scenarios of this clause. The requirements on the DUTs for these tests are that they can handle the procedures defined for a Non-RT RIC and Near-RT RIC and the purpose of the test scenarios is to validate that Non-RT RIC and Near-RT RIC are interoperable. The Non-RT RIC and the Near-RT RIC can be functions that are under development, or they can be finalised commercial products, that have passed the conformance test scenarios defined in clauses 5 and 6. - -In addition to the basic conformance requirements, and the DUT requirements in clause 5 and 6, the following is required for Non-RT RIC and Near-RT RIC when they act as DUTs in this test system: - -- It shall be possible for the DUTs to initiate the A1 procedures in a controlled manner and to generate relevant response for each test case. For this some additional functionality is required, this can be implemented as installable test applications or in other vendor specific way. -- To enable validation of A1 procedure messages captured between the DUTs an ability to disable encryption is required. -- A1 policy types and EI types used in test scenarios are agreed and configured in the DUTs in advance. - -NOTE: The present document does not require usage of any specific policy type or EI type since specific behaviour is not validated, only the application protocol aspects and procedures are validated for interoperability testing of the A1 services. - -## 7.1.2 Test tools and simulators capabilities - -A TAP interface and protocol analyser is required for recording and validating A1 procedure message sequences and contents and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUTs level of interoperability. - -SMO framework with O1 functionality may be required to bring the DUTs into operational state. - -Depending on how the functionality in the DUTs required for the test scenarios is implemented, there may be a need to connect Near-RTR-DUT to E2 Nodes connected to RUs, UEs and Core Network. These can be replaced by appropriate simulators. - -NOTE: In the future, when then open APIs for rApps and xApps are fully specified, test apps can be provided as part of the test tools and used to trigger the request messages and generate the content of the response messages for the test scenarios. - -## 7.2 Interoperability test cases for A1-P - -### 7.2.1 Query policy type test scenarios - -#### 7.2.1.1 Query all policy type identifiers (positive case) - -##### 7.2.1.1.1 Test description and applicability - -The purpose of this test case is to test the query policy types functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.3.2. The expected outcome is successful Query all policy type identifiers operation. - -This test case is conditionally mandatory if the DUTs claim to support A1-P service and the Query all policy type identifiers procedure. - -##### 7.2.1.1.2 Test entrance criteria - -- 1) The Non-RTR-DUT has functionality to initiate A1-P Query all policy type identifiers procedure. -- 2) A set of policy types (at least two) are supported in the Near-RTR-DUT. -- 3) The supported policyTypeIds are known to the “protocol analyser”. - -##### 7.2.1.1.3 Test methodology - -###### 7.2.1.1.3.1 Initial conditions - -- 1) The Near-RTR-DUT has A1-P Producer service ready and available to receive HTTP requests from the Non-RTR-DUT. -- 2) The Near-RTR-DUT supports the three different test configurations listed below to test complete functionality: - - a) Near-RTR-DUT has no policy types available. - - b) Near-RTR-DUT has a single policy type available. - - c) Near-RTR-DUT has two or more policy types available. - -###### 7.2.1.1.3.2 Procedure - -Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap/TAP interface. - -Step 1. Initiate appropriate action in the Non-RTR-DUT to initiate Query all policy type identifiers request. - -Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -Step 3. Repeat Step 1 and Step 2 for the three test configurations. - -#### 7.2.1.1.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met for all three test configurations listed in clause 7.2.1.1.3.1: - -For the request message - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. -- b) The HTTP request is a GET operation. -- c) The HTTP request message body is empty. - -For the response message - -- 1) The return code is "200 OK". -- 2) Response message body is validated depending on the three test configurations used - - a) If the Near-RTR-DUT has no policy types available, message body is an empty array - - b) If the Near-RTR-DUT has single policy type available, message body contains an array with one policyTypeId. - - c) If the Near-RTR-DUT has two or more policy types available, message body contains an array with all the policyTypeIds available in Near-RTR-DUT. - -#### 7.2.1.2 Query single policy type (positive) - -##### 7.2.1.2.1 Test description and applicability - -The purpose of this test case is to test the query policy types functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.3.3. The expected outcome is successful Query single policy type operation. - -This test case is conditionally mandatory if the DUTs claim to support A1-P service and the Query single policy type procedure. - -##### 7.2.1.2.2 Test entrance criteria - -- 1) The Non-RTR-DUT has functionality to initiate A1-P Query single policy procedure. -- 2) A known set of policy types are supported in the Near-RTR-DUT. -- 3) The supported policyTypeIds are known to the protocol analyser. - -##### 7.2.1.2.3 Test methodology - -###### 7.2.1.2.3.1 Initial conditions - -- 1) The Near-RTR-DUT has A1-P Producer service ready and available to receive HTTP requests from the Non-RTR-DUT. - -###### 7.2.1.2.3.2 Procedure - -Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. - -Step 1. Initiate appropriate action in the Non-RTR-DUT to initiate Query single policy request with a known policyTypeId. - -Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -#### 7.2.1.2.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -For the request message - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. -- b) The HTTP request is a GET operation. -- c) The policyTypeId in the URI match the policy type being queried. -- d) The HTTP request message body is empty. - -For the response message - -- 1) The return code is "200 OK". -- 2) Response message body content contains a PolicyTypeObject representing the read policy type. - -## 7.2.2 Create policy test scenario - -### 7.2.2.1 Create single policy (positive) - -#### 7.2.2.1.1 Test description and applicability - -This purpose of this test case is to test the create policy functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.4.3. The expected outcome is successful creation of the policy. - -This test case is conditionally mandatory if the DUTs claim to support A1-P service. - -#### 7.2.2.1.2 Test entrance criteria - -- 1) The Non-RTR-DUT has functionality to initiate A1-P Create single policy procedure. -- 2) The DUTs have agreed on a policy type to use for this test. -- 3) The policyTypeId and the JSON schemas of the policy type used for this test are available and used in Non-RTR-DUT to formulate the Create single policy request, and in Near-RTR-DUT to validate and handle the request. -- 4) The agreed policyTypeId is known to the protocol analyser. - -#### 7.2.2.1.3 Test methodology - -##### 7.2.2.1.3.1 Initial conditions - -- 1) The Near-RTR-DUT has A1-P Producer service ready and available to receive HTTP requests from the Non-RTR-DUT. -- 2) No policy exists in the Near-RTR-DUT for the policy type with the same policyId that will be used by the Non-RTR-DUT. - -##### 7.2.2.1.3.2 Procedure - -Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. - -Step 1. Initiate appropriate action in the Non-RTR-DUT to initiate Create single policy request for the agreed policy type. - -Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -#### 7.2.2.1.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -For the request message - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. -- b) The HTTP request is a PUT operation. -- c) The policyTypeId is as agreed to be used. -- d) The HTTP request message body contains the PolicyObject of the policy to be created and the PolicyObject conforms to the schema. - -NOTE: Presence or validation of optional query parameter for notificationDestination is not used to determine validation on this test. - -For the response message - -- 1) The return code is "201 Created". -- 2) Response message body content contains a PolicyObject representing the created policy. -- 3) The location header is present and carries the URI of the new policy. - -### 7.2.3 Query policy test scenarios - -#### 7.2.3.1 Query all policy identifiers - -##### 7.2.3.1.1 Test description and applicability - -The purpose of this test case is to test the query all policies functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.4.2. The expected outcome is successful retrieval of policy identifiers. - -This test case is conditionally mandatory if the DUTs claim to support A1-P service and the Query all policy identifiers procedure. - -##### 7.2.3.1.2 Test entrance criteria - -- 1) The Non-RTR-DUT has functionality to initiate A1-P Query all policy identifiers procedure. -- 2) The DUTs have agreed on a policy type to use for this test. -- 3) A set of policies (at least two) for the agreed policy type exist in the Near-RTR-DUT. -- 4) The agreed policyTypeId is known to the protocol analyser. - -##### 7.2.3.1.3 Test methodology - -###### 7.2.3.1.3.1 Initial conditions - -- 1) The Near-RTR-DUT has A1-P Producer service ready and available to receive HTTP requests from the Non-RTR-DUT. -- 2) The Near-RTR-DUT supports three different test configurations listed below to test complete functionality: - -- a) Near-RTR-DUT has no policies available for the agreed policy type. -- b) Near-RTR-DUT has a single policy available for the agreed policy type. -- c) Near-RTR-DUT has two or more policies available for the agreed policy type. - -#### 7.2.3.1.3.2 Procedure - -Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. - -Step 1. Initiate appropriate action in the Non-RTR-DUT to initiate Query all policy identifiers request. - -Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -Step 3. Repeat Step 1 and Step 2 for the three test configurations. - -#### 7.2.3.1.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met for all three test configurations listed in clause 7.2.3.1.3.1: - -For the request messages - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. -- b) The HTTP request is a GET operation. -- c) The message body is empty. - -For the response messages - -- 1) The return code is "200 OK". -- 2) Response message body is validated depending on the three test configurations used: - - a) If the Near-RTR-DUT has no policies available, message body is an empty array. - - b) If the Near-RTR-DUT has single policy available, message body contains an array with one policyId available with the given policy type. - - c) If the Near-RTR-DUT has two or more policies available, message body contains an array of policyIds of all the available policies of the given policy type. - -### 7.2.3.2 Query single policy - -#### 7.2.3.2.1 Test description and applicability - -The purpose of this test case is to test the query single policy functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.4.5. The expected outcome is successful retrieval of policy object. - -This test case is conditionally mandatory if the DUTs claim to support A1-P service and the Query single policy procedure. - -#### 7.2.3.2.2 Test entrance criteria - -- 1) The Non-RTR-DUT has functionality to initiate A1-P Query single policy procedure. -- 2) A policy exists in the Near-RTR-DUT and the policyTypeId and policyId are known to Non-RTR-DUT. -- 3) The policyTypeId and policyId are known to the protocol analyser. - -### 7.2.3.2.3 Test methodology - -#### 7.2.3.2.3.1 Initial conditions - -- 1) The Near-RTR-DUT has A1-P Producer service ready and available to receive HTTP requests from the Non-RTR-DUT. - -#### 7.2.3.2.3.2 Procedure - -Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. - -Step 1. Initiate appropriate action in the Non-RTR-DUT to initiate Query single policy request. - -Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -#### 7.2.3.2.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -For the request message - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. -- b) The HTTP request is a GET operation. -- c) The policyTypeId and policyId in the URI match the policy being queried. -- d) The message body is empty. - -For the response messages - -- 1) The return code is "200 OK". -- 2) Response message body content contains a PolicyObject representing the read policy. - -### 7.2.3.3 Query policy status (positive case) - -#### 7.2.3.3.1 Test description and applicability - -The purpose of this test case is to test the query policy status functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.4.7. The expected outcome is successful retrieval of policy status object. - -This test case is conditionally mandatory if the DUTs claim to support A1-P service and the Query policy status procedure. - -#### 7.2.3.3.2 Test entrance criteria - -- 1) The Non-RTR-DUT has functionality to initiate A1-P Query policy status procedure. -- 2) A policy exists in the Near-RTR-DUT and the policyTypeId and policyId are known to the Non-RTR-DUT. -- 3) The policyTypeId and policyId are known to the protocol analyser. - -### 7.2.3.3.3 Test methodology - -#### 7.2.3.3.3.1 Initial conditions - -- 1) The Near-RTR-DUT has A1-P Producer service ready and available to receive HTTP requests from the Non-RTR-DUT. - -#### 7.2.3.3.3.2 Procedure - -- Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. -- Step 1. Initiate appropriate action in the Non-RTR-DUT to initiate Query policy status request. -- Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -#### 7.2.3.3.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -For the request message - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. -- b) The HTTP request is a GET operation. -- c) The policyTypeId and policyId in the URI match the policy being queried. -- d) The message body is empty. - -For the response messages - -- 1) The return code is "200 OK". -- 2) Response message body content contains a PolicyStatusObject representing the status of the policy. - -### 7.2.4 Update policy test scenarios - -#### 7.2.4.1 Update single policy (positive case) - -##### 7.2.4.1.1 Test description and applicability - -The purpose of this test case is to test the update policy functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.4.4. The expected outcome is successful update of the policy. - -This test case is conditionally mandatory if the DUTs claim to support A1-P service and the Update single policy procedure. - -##### 7.2.4.1.2 Test entrance criteria - -- 1) The Non-RTR-DUT has functionality to initiate A1-P Update single policy procedure. -- 2) A policy exists in the Near-RTR-DUT and the policyTypeId and policyId are known to the Non-RTR-DUT. -- 3) The policyTypeId and the JSON schemas of the policy type used for this test are available and used in Non-RTR-DUT to formulate the Update single policy request, and in Near-RTR-DUT to validate and handle the request. -- 4) The policyTypeId and the policyId are known to the protocol analyser. - -##### 7.2.4.1.3 Test methodology - -###### 7.2.4.1.3.1 Initial conditions - -- 1) The Near-RTR-DUT has A1-P Producer service ready and available to receive HTTP requests from the Non-RTR-DUT. - -#### 7.2.4.1.3.2 Procedure - -- Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. -- Step 1. Initiate appropriate action in the Non-RTR-DUT to initiate Update single policy request. -- Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -#### 7.2.4.1.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -For the request messages - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. -- b) The HTTP request is a PUT operation. -- c) The policyTypeId and policyId in the URI match the policy being updated. -- d) The HTTP request message body contains the PolicyObject of the policy to be updated and the PolicyObject conforms to the schema of the policy type. - -For the response messages - -- 1) The return code is "200 OK". -- 2) Response message body content is verified to match the PolicyObject sent in Step 1. - -### 7.2.5 Delete policy test scenarios - -#### 7.2.5.1 Delete single policy (positive case) - -##### 7.2.5.1.1 Test description and applicability - -The purpose of this test case is to test the delete policy functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.4.6. The expected outcome is successful deletion of the policy. - -This test case is conditionally mandatory if the DUTs claim to support A1-P service. - -##### 7.2.5.1.2 Test entrance criteria - -- 1) The Non-RTR-DUT has functionality to initiate A1-P Delete single policy procedure. -- 2) A policy exists in the Near-RTR-DUT and the policyTypeId and policyId are known to the Non-RTR-DUT. -- 3) The policyTypeId and the policyId are known to the protocol analyser. - -##### 7.2.5.1.3 Test methodology - -###### 7.2.5.1.3.1 Initial conditions - -- 1) The Near-RTR-DUT has A1-P Producer service ready and available to receive HTTP requests from the Non-RTR-DUT. - -###### 7.2.5.1.3.2 Procedure - -- Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. - -Step 1. Initiate appropriate action in the Non-RTR-DUT to initiate Delete single policy request. - -Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -#### 7.2.5.1.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -For the request messages - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. -- b) The HTTP request is a DELETE operation. -- c) The policyTypeId and policyId in the URI match the policy being deleted. -- d) The message body is empty. - -For the response messages - -- 1) The return code is "204 No content". -- 2) Response message body is empty. - -### 7.2.6 Notify policy status test scenarios - -#### 7.2.6.1 Notify policy status (positive case) - -##### 7.2.6.1.1 Test description and applicability - -The purpose of this test case is to test the policy status notification functionality of A1-P Consumer and A1-P Producer as specified in A1AP [4] clause 5.2.4.8. The expected outcome is successful policy status request and reception. - -This test case is optional if the DUTs claim to support A1-P service and supports the Notify policy status procedure. - -##### 7.2.6.1.2 Test entrance criteria - -The test entrance criteria for Create single policy specified in clause 7.2.2.1.2 applies. And in addition: - -- 1) Non-RTR-DUT has the functionality to request and receive policy status notifications. -- 2) Near-RTR-DUT has the functionality to provide policy status notifications. -- 3) Non-RTR-DUT and Near-RTR-DUT have agreed on a how to requests and trigger the policy status notification based on supported policy types and functionality in the Near-RTR-DUT. - -##### 7.2.6.1.3 Test methodology - -###### 7.2.6.1.3.1 Initial conditions - -The initial conditions for Create single policy specified in clause 7.2.2.1.3.1 applies. And in addition: - -- 1) The Near-RTR-DUT supports generation of a PolicyStatusObject based on the policy status schema of the agreed policy type used for this test. -- 2) The Non-RTR-DUT has HTTP server ready and available to receive HTTP requests from the Near-RTR-DUT for policy status notifications. - -NOTE: The Non-RTR-DUT is expected to provide callback URI (notificationDestination) during the Create single policy procedure (see A1AP [4] clause 5.2.4.3) for which it can relate received policy status notifications to the policyId that was generated when creating the policy for which policy status notifications is requested. - -#### 7.2.6.1.3.2 Procedure - -- Step 1. Same as for Create single policy, see clause 7.2.2.1.3.2, including the notificationDestination query parameter. -- Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. -- Step 3. Initiate appropriate action in the Near-RTR-DUT to initiate Notify policy status request for the created policy. -- Step 4. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -#### 7.2.6.1.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met for the Create policy operation: - -For the request message - -- a)-e) As defined for Create single policy in clause 7.2.2.1.3.3. -- f) The notificationDestination query parameter is included. - -For the response message - -- 1) The return code is "201 Created". - -Check the HTTP messages recorded in Step 4 of procedure. - -The test is considered passed if the following conditions are met for the Notify policy status operation: - -For the request message - -- a) The URI is the notificationDestination provided in the Create policy operation. -- b) The HTTP request is a POST operation. -- c) The HTTP request message body contains the PolicyStatusObject of the policy for which status is updated and the PolicyStatusObject conforms to the status schema. - -For the response message - -- 1) The return code is "204 No content". - -## 7.3 Interoperability test cases for A1-EI - -### 7.3.1 Query EI types test scenarios - -#### 7.3.1.1 Query EI type identifiers (positive case) - -##### 7.3.1.1.1 Test description and applicability - -The purpose of this test case is to test query EI type identifiers functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.3.2. The expected outcome is successful retrieval of EI type identifiers. - -This test case is conditionally mandatory if the DUTs claim to support A1-EI service and Query EI type identifiers procedure. - -#### 7.3.1.1.2 Test entrance criteria - -- 1) The Near-RTR-DUT has functionality to initiate A1-EI Query EI type identifiers procedure. -- 2) The Non-RTR-DUT supports a known set of EI types (two or more) used for this test. -- 3) The supported eiTypeIds are known to the protocol analyser - -#### 7.3.1.1.3 Test methodology - -##### 7.3.1.1.3.1 Initial conditions - -- 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. -- 2) The Non-RTR-DUT supports the three different test configurations listed below to test complete functionality: - - a) Non-RTR-DUT has no EI type available. - - b) Non-RTR-DUT has a single EI type available. - - c) Non-RTR-DUT has two or more EI types available. - -##### 7.3.1.1.3.2 Procedure - -Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. - -Step 1. Initiate appropriate action in the Near-RTR-DUT to initiate Query EI type identifiers request. - -Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -Step 3. Repeat Step 1 and Step 2 for the three test configurations. - -##### 7.3.1.1.3.3 Expected result - -The test is considered passed if the following conditions are met for all three test configurations listed in clause 7.3.1.1.3.1: - -For the request message - -- a) The URI conforms to the format specified in A1AP [4] clause 6.2.3. -- b) The HTTP request is a GET operation. -- c) The HTTP request message body is empty. - -For the response message - -- 1) The return code is "200 OK". -- 2) Response message body is validated depending on the test configuration used: - - a) If the Non-RTR-DUT has no EI type available, message body is an empty array. - - b) If the Non-RTR-DUT has single EI type available, message body contains an array with one eiTypeId. - - c) If the Non-RTR-DUT has two or more EI jobs available, message body contains an array of all the eiTypeIds available in DUT. - -### 7.3.1.2 Query EI type (positive case) - -#### 7.3.1.2.1 Test description and applicability - -The purpose of this test case is to test query EI type functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.3.3. The expected outcome is successful retrieval of EI type object. - -This test case is conditionally mandatory if the DUTs claim to support A1-EI service and the Query EI type procedure. - -#### 7.3.1.2.2 Test entrance criteria - -- 1) The Near-RTR-DUT has the functionality to initiate A1-EI Query EI type procedure. -- 2) A known set of EI types are supported in the Non-RTR-DUT. -- 3) The supported eiTypeIds are known to the protocol analyser. - -#### 7.3.1.2.3 Test methodology - -##### 7.3.1.2.3.1 Initial conditions - -- 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. - -##### 7.3.1.2.3.2 Procedure - -- Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. -- Step 1. Initiate appropriate action in the Near-RTR-DUT to initiate Query EI type request with a known eiTypeId. -- Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -##### 7.3.1.2.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -For the request message - -- a) The URI conforms to the format specified in A1AP [4] clause 6.3.3. -- b) The HTTP request is a GET operation. -- c) The eiTypeId in the URI match the EI type being queried. -- d) The HTTP request message body is empty. - -For the response message - -- 1) The return code is "200 OK". -- 2) Response message body content contains an EiTypeObject representing the read EI job. - -## 7.3.2 Create EI job test scenario - -### 7.3.2.1 Create EI job (positive case) - -#### 7.3.2.1.1 Test description and applicability - -This purpose of this test case is to test the create EI job functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.4.3. The expected outcome is successful creation of the EI job. - -This test case is conditionally mandatory if the DUTs claim to support A1-EI service. - -#### 7.3.2.1.2 Test entrance criteria - -- 1) The Near-RTR-DUT has functionality to initiate A1-EI Create EI job procedure. -- 2) The DUTs have agreed on an EI type to use for this test. -- 3) The eiTypeId and the JSON schemas of the EI type used for this test are available and used in Near-RTR-DUT to formulate the Create EI job request, and in Non-RTR-DUT to validate and handle the request. -- 4) The agreed eiTypeId is known to the protocol analyser. - -#### 7.3.2.1.3 Test methodology - -##### 7.3.2.1.3.1 Initial conditions - -- 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. -- 2) No EI job exists in the Non-RTR-DUT for the EI job type with the same eiJobId that will be used by the Near-RTR-DUT. - -##### 7.3.2.1.3.2 Procedure - -Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. - -Step 1. Initiate appropriate action in the Near-RTR-DUT to initiate Create EI job request for the agreed EI job type. - -Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -##### 7.3.2.1.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -For the request message - -- a) The URI conforms to the format specified in A1AP [4] clause 6.3.3. -- b) The HTTP request is a PUT operation. -- c) The eiTypeId is as agreed to be used. -- d) The HTTP request message body contains the EiJobObject of the EI job to be created and the EiJobObject conforms to the schema. - -For the response message - -- 1) The return code is "201 Created". - -- 2) Response message body content contains an EiJobObject representing the created EI job. -- 3) The location header is present and carries the URI of the new EI job. - -### 7.3.3 Query EI jobs test scenarios - -#### 7.3.3.1 Query EI job identifiers for a single EI type (positive case) - -##### 7.3.3.1.1 Test description and applicability - -This purpose of this test case is to test query EI job identifiers functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.4.2. The expected outcome is successful retrieval of all EI job identifiers of a given EI type. - -This test case is conditionally mandatory if the DUTs claim to support A1-EI service and Query EI job identifiers procedure. - -##### 7.3.3.1.2 Test entrance criteria - -- 1) The Near-RTR-DUT has functionality to initiate A1-EI Query EI job identifiers procedure. -- 2) The DUTs have agreed on an EI type to use for this test. -- 3) A set of EI jobs (at least two) for the agreed EI type exist in the Non-RT-DUT. -- 4) The agreed eiTypeId is known to the protocol analyser. - -##### 7.3.3.1.3 Test methodology - -###### 7.3.3.1.3.1 Initial conditions - -- 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. -- 2) The Non-RTR-DUT supports three different test configurations listed below to test complete functionality: - - a) Non-RTR-DUT has no EI jobs available for the agreed EI type. - - b) Non-RTR-DUT has an EI job available for the agreed EI type. - - c) Non-RTR-DUT has two or more EI jobs available for the agreed EI type. - -###### 7.3.3.1.3.2 Procedure - -Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. - -Step 1. Initiate appropriate action in the Near-RTR-DUT to initiate Query all EI job identifiers. - -Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -Step 3. Repeat Step 1 and Step 2 for the three test configurations. - -###### 7.3.3.1.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met for all three test configurations listed in clause 7.3.3.1.3.1: - -For the request messages - -- a) The URI conforms to the format specified in A1AP [4] clause 6.3.3 with the agreed eiTypeId as query parameter -- b) The HTTP request is a GET operation. - -- c) The message body is empty. -- d) A query parameter with an eiTypeId is included. - -For the response messages - -- 1) The return code is "200 OK". -- 2) Response message body is validated depending on the three test configurations used: - - a) If the Non-RTR-DUT has no EI job available, message body is an empty array. - - b) If the Non-RTR-DUT has single EI job available, message body contains an array with one eiJobId available with the given EI type. - - c) If the Non-RTR-DUT has two or more EI jobs available, message body contains an array of eiJobIds of all the available EI jobs of the given EI type. - -### 7.3.3.2 Query EI job identifiers for all EI types (positive case) - -#### 7.3.3.2.1 Test description and applicability - -This purpose of this test case is to test query EI job identifiers functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.4.2. The expected outcome is successful retrieval of all EI job identifiers of all EI types. - -This test case is conditionally mandatory if the DUTs claim to support A1-EI service and Query EI job identifiers procedure. - -#### 7.3.3.2.2 Test entrance criteria - -- 1) The Near-RTR-DUT has functionality to initiate A1-EI Query EI job identifiers procedure. -- 2) The DUTs supports a known set of EI types (two or more) used for this test. -- 3) The agreed eiTypeIds are known to the protocol analyser. - -#### 7.3.3.2.3 Test methodology - -##### 7.3.3.2.3.1 Initial conditions - -- 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT -- 2) The Non-RTR-DUT supports the two different test configurations listed below to test complete functionality: - - a) Non-RTR-DUT has no EI job available for any of the EI types supported. - - b) Non-RTR-DUT has one or more EI jobs available for each EI type supported. - -##### 7.3.3.2.3.2 Procedure - -Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. - -Step 1. Initiate appropriate action in the Near-RTR-DUT to initiate Query EI job identifiers request. - -Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -##### 7.3.3.2.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met for all two test configurations listed in clause 7.3.3.2.3.1: - -For the request messages - -- a) The URI conforms to the format specified in A1AP [4] clause 6.3.3 without eiTypeId included as query parameter -- b) The HTTP request is a GET operation. -- c) No query parameter with an eiTypeId is included. -- d) The message body is empty. - -For the response messages - -- 1) The return code is "200 OK". -- 2) Response message body is validated depending on the two test configurations used: - - a) If the Non-RTR-DUT has no EI job available, message body is an empty array. - - b) If the Non-RTR-DUT has one or more EI jobs available, message body contains an array of eiJobIds of all the available EI jobs of all EI types. - -### 7.3.3.3 Query EI job (positive case) - -#### 7.3.3.3.1 Test description and applicability - -The purpose of this test case is to test query EI job functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.4.5. The expected outcome is successful retrieval of EI job for the given eiJobId. - -This test case is conditionally mandatory if the DUTs claim to support A1-EI service and the Query EI job procedure. - -#### 7.3.3.3.2 Test entrance criteria - -- 1) The Near-RTR-DUT has functionality to initiate A1-EI Query EI job procedure. -- 2) An EI job exists in the Non-RTR-DUT and the eiJobId is known to the Near-RTR-DUT. -- 3) The eiJobId is known to the protocol analyser. - -#### 7.3.3.3.3 Test methodology - -##### 7.3.3.3.3.1 Initial conditions - -- 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. - -##### 7.3.3.3.3.2 Procedure - -- Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. -- Step 1. Initiate appropriate action in the Near-RTR-DUT to initiate Query EI job request. -- Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -##### 7.3.3.3.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -- a) The URI conforms to the format specified in A1AP [4] clause 6.3.3. -- b) The HTTP request is a GET operation. - -- c) The eiJobId in the URI match the EI job being queried. -- d) The HTTP request message body is empty. - -For the response messages - -- 1) The return code is “200 OK”. -- 2) Response message body content contains an EiJobObject representing the EI job. - -### 7.3.4 Update EI job test scenarios - -#### 7.3.4.1 Update EI job (positive case) - -##### 7.3.4.1.1 Test description and applicability - -The purpose of this test case is to test update EI job functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.4.4. The expected outcome is successful update of the EI job. - -This test case is conditionally mandatory if the DUTs claim to support A1-EI service and Update EI job procedure. - -##### 7.3.4.1.2 Test entrance criteria - -- 1) The Non-RTR-DUT has functionality to initiate A1-EI Update EI job procedure. -- 2) An EI job exists in the Non-RTR-DUT and the eiTypeID and eiJobID are known to the Near-RTR-DUT. -- 3) The eiTypeID and the JSON schemas of the EI type used for this test are available and used in Near-RTR-DUT to formulate the Update EI job request, and in Non-RTR-DUT to validate and handle the request. -- 4) The eiTypeID and the eiTypeID are known to the protocol analyser. - -##### 7.3.4.1.3 Test methodology - -###### 7.3.4.1.3.1 Initial conditions - -- 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. - -###### 7.3.4.1.3.2 Procedure - -Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. - -Step 1. Initiate appropriate action in the Near-RTR-DUT to initiate Update EI job request. - -Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -###### 7.3.4.1.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -For the request messages - -- a) The URI conforms to the format specified in A1AP [4] clause 6.3.3. -- b) The HTTP request is a PUT operation. -- c) The eiJobId in the URI match the EI job to be updated. - -- d) The HTTP request message body contains the EiJobObject of the EI job being updated and the EiJobObject conforms to the schema of the EI type. - -For the response messages - -- 1) The return code is "200 OK". -- 2) Response message body content is verified to match the EiJobObject sent in Step 1. - -### 7.3.5 Delete EI job test scenarios - -#### 7.3.5.1 Delete EI job (positive case) - -##### 7.3.5.1.1 Test description and applicability - -The purpose of this test case is to test the delete EI job functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.4.6. The expected outcome is successful validation of the Delete EI job request - -This test case is conditionally mandatory if the DUTs claim to support A1-EI service. - -##### 7.3.5.1.2 Test entrance criteria - -- 1) The Non-RTR-DUT has functionality to initiate A1-EI Delete EI job procedure. -- 2) An EI job exists in the Non-RTR-DUT and the eiJobId is known to the Near-RTR-DUT. -- 3) The eiJobId is known to the protocol analyser. - -##### 7.3.5.1.3 Test methodology - -###### 7.3.5.1.3.1 Initial conditions - -- 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. - -###### 7.3.5.1.3.2 Procedure - -- Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. -- Step 1. Initiate appropriate action in the Near-RTR-DUT to initiate Delete EI job request. -- Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -###### 7.3.5.1.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met: - -For the request messages - -- a) The URI conforms to the format specified in A1AP [4] clause 6.3.3. -- b) The HTTP request is a DELETE operation. -- c) The eiJobId in the URI match the EI job being deleted. -- d) The message body is empty. - -For the response messages - -- 1) The return code is "204 No content". -- 2) Response message body is empty. - -### 7.3.6 Status of EI jobs test scenarios - -#### 7.3.6.1 Query EI job status (positive case) - -##### 7.3.6.1.1 Test description and applicability - -The purpose of this test case is to test the query EI job status functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.4.7. The expected outcome is successful retrieval of EI job status object. - -This test case is conditionally mandatory if the DUTs claim to support A1-EI service and the Query EI job status procedure. - -##### 7.3.6.1.2 Test entrance criteria - -- 1) The Near-RTR-DUT has functionality to initiate Query EI job status procedure. -- 2) An EI job exists in the Non-RTR-DUT and the eiJobId is known to the Near-RTR-DUT. -- 3) The agreed eiTypeId is known to the protocol analyser. - -##### 7.3.6.1.3 Test methodology - -###### 7.3.6.1.3.1 Initial conditions - -- 1) The Non-RTR-DUT has A1-EI Producer service ready and available to receive HTTP requests from the Near-RTR-DUT. - -###### 7.3.6.1.3.2 Procedure - -Step 0. Enable protocol analyser to capture and decode the A1 signalling between the DUTs via the tap interface. - -Step 1. Initiate appropriate action in the Near-RTR-DUT to initiate Query EI job status request. - -Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -###### 7.3.6.1.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met - -For the request messages - -- a) The URI conforms to the format specified in A1AP [4] clause 6.3.3. -- b) The HTTP request is a GET operation. -- c) The eiJobId in the URI match the EI job being queried. -- d) The HTTP request message body is empty. - -For the response messages - -- 1) The return code is "200 OK". -- 2) Response message body content contains an EiJobStatusObject representing the status of the EI job. - -### 7.3.6.2 Notify EI job status (positive case) - -#### 7.3.6.2.1 Test description and applicability - -This purpose of this test case is to test the notify EI job status functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.4.8. The expected outcome is successful request and delivery of EI job status notification. - -This test case is optional if the DUTs claim to support A1-EI service and supports the Notify EI job status procedure. - -#### 7.3.6.2.2 Test entrance criteria - -The test entrance criteria for Create EI job specified in clause 7.3.2.1.2 applies. And in addition: - -- 1) Near-RTR-DUT has the functionality to request and receive EI job status notification -- 2) Non-RTR-DUT has the functionality to provide EI job status notification. -- 3) Non-RTR-DUT and Near-RTR-DUT have agreed on a how to request and trigger the EI job status notification based on supported EI types and functionality in the Non-RTR-DUT. - -#### 7.3.6.2.3 Test methodology - -##### 7.3.6.2.3.1 Initial conditions - -The initial conditions for Create EI job specified in clause 7.3.2.1.3.1 applies. And in addition: - -- 1) The Near-RTR-DUT supports generation of an EiJobStatusObject based on the EI job status schema of the agreed EI type used for this test. -- 2) The Near-RTR-DUT has HTTP server ready and available to receive HTTP requests from the Non-RTR-DUT for EI job status notifications. - -NOTE: The Near-RTR-DUT is expected to provide callback URI (jobStatusNotificationUri) during the Create EI job procedure (see A1AP [4] clause 5.3.4.3) for which it can relate received EI job status notifications to the eiJobId that was generated when creating the EI job for which EI job status notifications is requested. - -##### 7.3.6.2.3.2 Procedure - -- Step 1. Same as for Create EI job, see clause 7.3.2.1.3.2, including the jobStatusNotificationUri parameter in EiJobObject. -- Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. -- Step 3. Initiate appropriate action in the Non-RTR-DUT to initiate EI job status notification for the created EI job. -- Step 4. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -##### 7.3.6.2.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met for the Create EI job operation: - -For the request message - -- a)-d) As defined for Create EI job in clause 7.3.2.1.3.3. -- e) The jobStatusNotificationUri parameter is included in the EiJobObject. - -For the response message - -- 1)-3) As defined for Create EI job in clause 7.3.2.1.3.3. - -Check the HTTP messages recorded in Step 4 of procedure. - -The test is considered passed if the following conditions are met for the EI job status notification operation: - -For the request message - -- a) The URI is the jobStatusNotificationUri provided in the Create EI job operation. -- b) The HTTP request is a POST operation. -- c) The HTTP request message body contains the EiJobStatusObject of the EI job for which status is updated and the EiJobStatusObject conforms to the EI type status schema. - -For the response message - -- 1) The return code is "204 No content". - -## 7.3.7 Deliver EI job result test scenarios - -### 7.3.7.1 Deliver EI job result (positive case) - -#### 7.3.7.1.1 Test description and applicability - -This purpose of this test case is to test the deliver EI job result functionality of A1-EI Producer and A1-EI Consumer as specified in A1AP [4] clause 5.3.5.2. The expected outcome is successful EI job result request and delivery of EI job results. - -This test case is optional if the DUTs claim to support A1-EI service. - -#### 7.3.7.1.2 Test entrance criteria - -The test entrance criteria for Create EI job specified in clause 7.3.2.1.2 applies. And in addition: - -- 1) Non-RTR-DUT and Near-RTR-DUT have agreed on a how to trigger the EI job results delivery based on supported EI types and functionality in the Non-RTR-DUT. - -#### 7.3.7.1.3 Test methodology - -##### 7.3.7.1.3.1 Initial conditions - -The initial conditions for Create EI job specified in clause 7.3.2.1.3.1 applies. And in addition: - -- 1) The Near-RTR-DUT has HTTP server ready and available to receive HTTP requests from the Non-RTR-DUT for EI job result delivery. - -NOTE: The Near-RTR-DUT is expected to provide callback URI (jobResultUri) during the Create EI job procedure (see A1AP [4] clause 5.3.4.3) for which it can relate received EI job results to the eiJobId that was generated when creating the EI job for which EI job result is delivered. - -##### 7.3.7.1.3.2 Procedure - -Step 1. Same as for Create EI job, see clause 7.3.2.1.3.2, including the jobResultUri parameter in the EiJobObject. - -Step 2. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -Step 3. Initiate appropriate action in the Non-RTR-DUT to initiate EI job result delivery for the created EI job. - -Step 4. At the protocol analyser the contents of the HTTP request and the HTTP response are recorded. - -#### 7.3.7.1.3.3 Expected result - -Check the HTTP messages recorded in Step 2 of procedure. - -The test is considered passed if the following conditions are met for the Create EI job operation: - -For the request message - -- a)-d) As defined for Create EI job in clause 7.3.2.1.3.3. - -For the response message - -- 1)-3) As defined for Create EI job in clause 7.3.2.1.3.3. - -Check the HTTP messages recorded in Step 4 of procedure. - -The test is considered passed if the following conditions are met for the EI job result notification operation: - -For the request message - -- a) The URI is the jobResultUri provided in the Create EI job operation. -- b) The HTTP request is a POST operation. -- c) The HTTP request message body contains the EiJobResultObject of the EI job for which result is delivered and the EiJobResultObject conforms to the EI type result schema. - -For the response message - -- 1) The return code is "204 No content". - ---- - -## Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|--------------------------------------------------------------------------------------------------------------------------| -| 2021.11.24 | 01.00 | A1-P conformance test cases for Non-RT RIC and Near-RT RIC | -| 2022.04.01 | 02.00 | Introducing A1-EI conformance test cases for Non-RT RIC and Near-RT RIC | -| 2022.11.17 | 03.00 | Introducing A1-P and A1-EI interoperability test cases for Non-RT RIC and Near-RT RIC. Aligning to O-RAN drafting rules. | -| 2023.11.30 | 04.00 | ETSI PAS related editorial enhancements, applying latest template and updating test cases applicability | -| 2024.03.31 | 04.01 | Editorial enhancements and alignment of notation for status and feedback | -| 2024.07.31 | 04.02 | Editorial enhancements | -| 2024.11.30 | 04.03 | Editorial enhancements of references | -| 2025.07.31 | 04.04 | Editorial enhancements and applying latest template | -| 2025.11.30 | 05.00 | Voiding negative test cases related to callbacks | \ No newline at end of file diff --git a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/0827b9260fe5458dbe416ebfc78c469e_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/0a65720e640be13541e947c06c7a8c7f_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/1099a4137017f2d9721d546bbb1e9362_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/14af8d47efd24c21fddf71b2415b6397_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/1baaba7a6e54e77197475726c871067d_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/226f5e462c99b71e08dc9abaa5ae260c_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/22af211207188ebc64d7b60ca052b367_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/22f30783614672d201275c116a5d8516_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/36fb8f844f936e7a1de4838da774f2f9_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/3f727e6c0d6658bc53ea10905c4561dd_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/446c0bd806260f25430cadb01a6786c7_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/5ae3023386ee15fae372871afce28865_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/60e345365fd1e52e01c91e3fd3cc6515_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/6588b1c7f14069d96744b473ad663248_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/6a9c5a85a12499d60c5a3a75c643b852_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg deleted file mode 100644 index 7ab5e230f537d94c175f28c43685e5673b302075..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/7affafe7362a2d2d072e9d4bf515f0bb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5bb0975597e4919806bee3a39082f4c82d6b1b84c127246a8b0c210b9d9d1bf7 -size 51205 diff --git a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/7d08458fbe0bd5f306c00c16d68b25f2_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/7f4320cee12fc1dbb865cc6b67462a91_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/83ee9f10bd3636e192d68decf7f04cec_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8447c5519e85d7a9e029fbf321da4c4f_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/854df8ad60507803253274673f9062cf_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8b4befaffc5166da571069410e207aea_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8d138b6bf0be359dc7f079db4899bc41_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/8fbe9e67b51710384633b6407d60420d_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/9156549264d36ead617a1dec7987f970_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/9159d999b6514420a64eae80e52f1fd5_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/970a901d8e537da4b6ff719d8931912f_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/9791722d75115ddcc599b07d7bc35d73_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/9791722d75115ddcc599b07d7bc35d73_img.jpg deleted file mode 100644 index 6a55f5ff9429ada418a306be42b240bb576a0b19..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/9791722d75115ddcc599b07d7bc35d73_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bdebe58b9093a4e8b8a62e0840a3012b5e3433b2867a85e8008b162f11bf61ba -size 49311 diff --git a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/9a6ff2584005112f32fbd551cb6f0591_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/9b59a11096b85b2bc74c6f653a354e28_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/a28ab03366399b5e0a61445bc57e3724_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/a76a30cf23764f0b907220e7c3c70ce1_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/a82aef1d2f3f1a527328950e9db947ee_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/be8d4d130f4e1f103926de61c4bfc23c_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg deleted file mode 100644 index 0062b0f64913ccc18f37e8aa1362d66a71c3fa98..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3b2221d6cade692a1f4de8398131e6ecc8a437442ffd7147465e7033854f1b5c -size 71820 diff --git a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d0516b99882398c64c90f71c12e808e2_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d2c29dfabebacb6f853683a6c3759320_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/d90f17b29a73eddf151f51effa8912e0_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e11e3fe4228e889a962514269f5a000b_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e32e1bcf367a284cc7a4186056810d22_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/e882a6bdfd0e868314f3a26f536145a3_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/f250ba4162fe40d8ddfd05b74fa48895_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/f3d768b0299c4763bc703b606391c48b_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/f74adaa1840504407cd4272995426f82_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/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1TS-R005-v05.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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/doc.md b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/doc.md deleted file mode 100644 index 6688da079912514958a995f6556d64d410b2107c..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/doc.md +++ /dev/null @@ -1,2304 +0,0 @@ - - -# --- A1 interface: Use Cases and Requirements - -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.....5 - -Modal verbs terminology.....5 - -1 Scope.....6 - -2 References .....6 - -2.1 Normative references .....6 - -2.2 Informative references.....6 - -3 Definition of terms, symbols, abbreviations and conventions.....7 - -3.1 Terms.....7 - -3.2 Symbols.....7 - -3.3 Abbreviations .....7 - -3.4 Conventions.....7 - -3.4.1 General.....7 - -3.4.2 Requirements .....7 - -3.4.3 UML diagrams.....7 - -4 General .....8 - -5 Requirements.....8 - -5.1 Functional requirements .....8 - -6 Use cases for A1 policy management .....10 - -6.1 Policy type discovery use cases.....10 - -6.1.1 Background and goal of the use cases .....10 - -6.1.2 Entities/resources involved in the use cases.....10 - -6.1.3 Solutions .....10 - -6.1.4 Required data .....13 - -6.2 Policy type status use cases .....13 - -6.2.1 Background and goal of the use cases .....13 - -6.2.2 Entities/resources involved in the use cases.....13 - -6.2.3 Solutions .....14 - -6.2.4 Required data .....17 - -6.3 Create policy use cases.....17 - -6.3.1 Background and goal of the use cases .....17 - -6.3.2 Entities/resources involved in the use cases.....17 - -6.3.3 Solutions .....18 - -6.3.4 Required data .....18 - -6.4 Query policy use cases .....18 - -6.4.1 Background and goal of the use cases .....18 - -6.4.2 Entities/resources involved in the use cases.....18 - -6.4.3 Solutions .....19 - -6.4.4 Required data .....20 - -6.5 Update policy use cases.....20 - -6.5.1 Background and goal of the use cases .....20 - -6.5.2 Entities/resources involved in the use cases.....20 - -6.5.3 Solutions .....21 - -6.5.4 Required data .....21 - -6.6 Delete policy use cases.....21 - -6.6.1 Background and goal of the use cases .....21 - -6.6.2 Entities/resources involved in the use cases.....22 - -6.6.3 Solutions .....22 - -6.6.4 Required data .....22 - -6.7 Policy status use cases.....22 - -6.7.1 Background and goal of the use cases .....22 - -6.7.2 Entities/resources involved in the use cases.....23 - -6.7.3 Solutions .....23 - -- 6.7.4 Required data .....24 -- 7 Use cases for A1 enrichment information .....24 - - 7.1 EI discovery use cases.....24 - - 7.1.1 Background and goal of the use cases .....24 - - 7.1.2 Entities/resources involved in the use cases.....25 - - 7.1.3 Solutions .....25 - - 7.2 EI type status use cases .....26 - - 7.2.1 Background and goal of the use cases .....26 - - 7.2.2 Entities/resources involved in the use cases.....27 - - 7.2.3 Solutions .....27 - - 7.2.4 Required data .....30 - - 7.3 Create EI job use cases .....30 - - 7.3.1 Background and goal of the use cases .....30 - - 7.3.2 Entities/resources involved in the use cases.....30 - - 7.3.3 Solutions .....31 - - 7.3.4 Required data .....31 - - 7.4 Query EI jobs use cases.....31 - - 7.4.1 Background and goal of the use cases .....31 - - 7.4.2 Entities/resources involved in the use cases.....31 - - 7.4.3 Solutions .....32 - - 7.4.4 Required data .....33 - - 7.5 Update EI job use cases.....33 - - 7.5.1 Background and goal of the use cases .....33 - - 7.5.2 Entities/resources involved in the use cases.....33 - - 7.5.3 Solutions .....34 - - 7.5.4 Required data .....34 - - 7.6 Delete EI job use cases.....34 - - 7.6.1 Background and goal of the use cases .....34 - - 7.6.2 Entities/resources involved in the use cases.....35 - - 7.6.3 Solutions .....35 - - 7.6.4 Required data .....35 - - 7.7 EI job status use cases .....36 - - 7.7.1 Background and goal of the use cases .....36 - - 7.7.2 Entities/resources involved in the use cases.....36 - - 7.7.3 Solutions .....36 - - 7.7.4 Required data .....37 - - 7.8 EI delivery use cases .....38 - - 7.8.1 Background and goal of the use cases .....38 - - 7.8.2 Entities/resources involved in the use cases.....38 - - 7.8.3 Solutions .....38 - - 7.8.4 Required data .....39 -- 8 Use cases for A1 ML model management service – Near-RT RIC as A1-ML Consumer .....39 - - 8.1 Request AI/ML model training use cases.....39 - - 8.1.1 Background and goal of the use cases .....39 - - 8.1.2 Entities/resources involved in the use cases.....39 - - 8.1.3 Solutions .....40 - - 8.1.4 Required data .....41 - - 8.2 AI/ML model training job status use cases .....41 - - 8.2.1 Background and goal of the use cases .....41 - - 8.2.2 Entities/resources involved in the use cases.....41 - - 8.2.3 Solutions .....42 - - 8.2.4 Required data .....43 - - 8.3 Discover AI/ML model training capabilities use cases .....43 - - 8.3.1 Background and goal of the use cases .....43 - - 8.3.2 Entities/resources involved in the use cases.....43 - - 8.3.3 Solutions .....44 - - 8.3.4 Required data .....44 - - 8.4 Cancel AI/ML model training use cases.....45 - -- 8.4.1 Background and goal of the use cases .....45 -- 8.4.2 Entities/resources involved in the use cases.....45 -- 8.4.3 Solutions .....45 -- 8.4.4 Required data .....46 -- 9 Use cases for A1 ML model management service – Non-RT RIC as A1-ML Consumer .....46 - - 9.1 Request AI/ML model training use cases.....46 - - 9.1.1 Background and goal of the use cases .....46 - - 9.1.2 Entities/resources involved in the use cases.....46 - - 9.1.3 Solutions .....47 - - 9.1.4 Required data .....47 - - 9.2 AI/ML model training job status use cases .....48 - - 9.2.1 Background and goal of the use cases .....48 - - 9.2.2 Entities/resources involved in the use cases.....48 - - 9.2.3 Solutions .....48 - - 9.2.4 Required data .....49 - - 9.3 Discover AI/ML model training capabilities use cases .....50 - - 9.3.1 Background and goal of the use cases .....50 - - 9.3.2 Entities/resources involved in the use cases.....50 - - 9.3.3 Solutions .....50 - - 9.3.4 Required data .....51 - - 9.4 Cancel AI/ML model training use cases.....51 - - 9.4.1 Background and goal of the use cases .....51 - - 9.4.2 Entities/resources involved in the use cases.....51 - - 9.4.3 Solutions .....52 - - 9.4.4 Required data .....52 -- Annex A (normative): Authorization of service access requests .....53** - - A.1 Pre-conditions.....53 - - A.2 A1 service access based on token verification use cases .....53 - - A.2.1 Background and goal of the use cases .....53 - - A.2.2 Entities/resources involved in the use cases.....53 - - A.2.3 Solutions .....53 - - A.2.4 Required data .....54 -- Annex (informative): Change History .....55** - -# --- Foreword - -This Technical Specification (TS) has been produced by O-RAN Alliance Working Group 2. It is part of a TS-family covering the A1 interface as identified below: - -- "A1 interface: General Aspects and Principles"; -- "A1 interface: Use Cases and Requirements"; -- "A1 interface: Transport Protocol"; -- "A1 interface: Application Protocol"; -- "A1 interface: Type Definitions"; and -- "A1 interface: Test Specification". - -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 use cases and requirements for the A1 interface. - -# --- 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.WG2.TS.A1GAP: "A1 interface: General Aspects and Principles" ("A1GAP"). -- [2] Void -- [3] O-RAN.WG2.TS.A1AP: "A1 interface: Application Protocol" ("A1AP"). -- [4] O-RAN.WG2.TS.A1TD: "A1 interface: Type Definitions" ("A1TD"). -- [5] O-RAN.WG2.TS.Non-RT-RIC-ARCH: "Non-RT RIC Architecture". -- [6] O-RAN.WG3.TS.RICARCH: "Near-RT RIC Architecture". -- [7] Recommendation ITU-T M.3020: "Management interface specification methodology". -- [8] OMG® Unified Modeling Language (OMG UML) version 2.5.1 ("OMG UML"). -- [9] O-RAN.WG11.TS.SecProtSpec.0: "O-RAN Security Protocols Specifications" ("SPS"). - -## 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. - -Not applicable. - -# 3 Definition of terms, symbols, abbreviations and conventions - -## 3.1 Terms - -For the purposes of the present document, the terms given in A1GAP [1], clause 3.1 apply. - -## 3.2 Symbols - -Void. - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given in A1GAP [1], clause 3.3 apply. - -## 3.4 Conventions - -### 3.4.1 General - -For the purposes of the present document, the conventions in the following clauses apply. - -### 3.4.2 Requirements - -The requirements and solutions for use cases are based on the methodology specified in ITU-T M.3020 [7], clause A.1.2. - -### 3.4.3 UML diagrams - -The sequence diagrams for the messages that are exchanged between use case actors are based on the OMG UML [8], clause 17.4.4.1 and an example is illustrated in figure 3.4.3-1. - -![UML sequence diagram showing interactions between a service consumer and a service producer. Lifelines: service consumer, service producer. Messages: synchronous message (solid line), reply message (dashed line), asynchronous message (dashed line).](ba9d6e1a75eb6672d04e61a86e1b8a61_img.jpg) - -``` - -sequenceDiagram - participant SC as service consumer - participant SP as service producer - Note left of SC: - SC->>SP: synchronous message - SP-->>SC: reply message - SP-->>SC: asynchronous message - Note right of SP: - -``` - -UML sequence diagram showing interactions between a service consumer and a service producer. Lifelines: service consumer, service producer. Messages: synchronous message (solid line), reply message (dashed line), asynchronous message (dashed line). - -Figure 3.4.3-1: Example of UML messages. - -For each message in the present document, the following information is indicated: - -- interface name and procedure name; -- type of message (e.g. request or response); and -- transferred information (if applicable). - -An example is illustrated in figure 3.4.3-2. - -![Sequence diagram showing a service consumer sending a 'Query single policy request (policy identifier)' to a service producer, and the service producer responding with a 'Query single policy response (policy information)'.](d0abac95583b52a3b35f74a215567334_img.jpg) - -``` - -sequenceDiagram - participant SC as service consumer - participant SP as service producer - Note left of SC: - Note right of SP: - SC->>SP: 1 <> Query single policy request (policy identifier) - SP-->>SC: 2 <> Query single policy response (policy information) - -``` - -Sequence diagram showing a service consumer sending a 'Query single policy request (policy identifier)' to a service producer, and the service producer responding with a 'Query single policy response (policy information)'. - -Figure 3.4.3-2: Example of message labels used in the present document. - -# 4 General - -Non-RT RIC with A1 termination function and A1 related functions in the SMO/Non-RT RIC framework is defined in Non-RT RIC Architecture [5]. - -Near-RT RIC with A1 Termination and internal functions is defined in Near-RT RIC Architecture [6]. - -Access token request, and service access request based on token verification, is defined in SPS [9], clause 4.7. - -The A1 policy management service (A1-P) and the A1-P procedures are defined in A1GAP [1], clause 4.1.3.1, the service operations and the API are defined in A1AP [3], clause 6.2, and policy types are defined in A1TD [4], clause 7.2. - -The A1 enrichment information service (A1-EI) and the A1-EI procedures are defined in A1GAP [1], clause 4.1.3.2, the service operations and the API are defined in A1AP [3], clause 6.3, and EI types are defined in A1TD [4], clause 9.2. - -The A1 ML model management service (A1-ML) is defined in A1GAP [1], clause 4.1.3.3. - -# 5 Requirements - -## 5.1 Functional requirements - -For the A1 policy management service (A1-P), the functional requirements are included in table 5.1-1. - -**Table 5.1-1: A1 Policy management service (A1-P) functional requirements** - -| REQ | Description | Note | -|----------------|------------------------------------------------------------------------------------------------------------------------|------| -| REQ-A1-P-FUN1 | A1-P shall support discovery of policy type identifiers | | -| REQ-A1-P-FUN2 | An A1 policy type shall be identified by a policy type identifier | | -| REQ-A1-P-FUN3 | A1-P shall support retrieval of information about A1 policy types | | -| REQ-A1-P-FUN4 | A1-P shall support retrieval of status information related to an A1 policy type | | -| REQ-A1-P-FUN5 | A1-P shall support subscription to, and notification about, changes in status information related to an A1 policy type | | -| REQ-A1-P-FUN6 | A1-P shall support request of policy enforcement related to an A1 policy type by managing an A1 policy | | -| REQ-A1-P-FUN7 | A1-P shall support discovery of policy identifiers | | -| REQ-A1-P-FUN8 | A1-P shall support retrieval of information about an A1 policy | | -| REQ-A1-P-FUN9 | A1-P shall support retrieval of status information related to an A1 policy | | -| REQ-A1-P-FUN10 | A1-P shall support subscription to, and notification about, changes in status information related to an A1 policy | | -| REQ-A1-P-FUN11 | A1-P shall support authorization of service access requests | | - -For the A1 enrichment information service (A1-EI), the functional requirements are included in table 5.1-2. - -**Table 5.1-2: A1 enrichment information service (A1-EI) functional requirements** - -| REQ | Description | Note | -|-----------------|------------------------------------------------------------------------------------------------------------------|------| -| REQ-A1-EI-FUN1 | A1-EI shall support discovery of EI type identifiers | | -| REQ-A1-EI-FUN2 | An EI type shall be identified by an EI type identifier | | -| REQ-A1-EI-FUN3 | A1-EI shall support retrieval of information about EI types | | -| REQ-A1-EI-FUN4 | A1-EI shall support retrieval of status information related to an EI type | | -| REQ-A1-EI-FUN5 | A1-EI shall support subscription to, and notification about, changes in status information related to an EI type | | -| REQ-A1-EI-FUN6 | A1-EI shall support request of enrichment information related to an EI type by managing an EI job | | -| REQ-A1-EI-FUN7 | A1-EI shall support discovery of EI job identifiers | | -| REQ-A1-EI-FUN8 | A1-EI shall support retrieval of information about an EI job | | -| REQ-A1-EI-FUN9 | A1-EI shall support retrieval of status information related to an EI job | | -| REQ-A1-EI-FUN10 | A1-EI shall support subscription to, and notification about, changes in status information related to an EI job. | | -| REQ-A1-EI-FUN11 | A1-EI shall support delivery of enrichment information over the A1 interface | | -| REQ-A1-EI-FUN12 | A1-EI shall support authorization of service access requests | | - -For the A1 ML model management service (A1-ML), the functional requirements are included in table 5.1-3. - -**Table 5.1-3: A1 ML model management service (A1-ML) functional requirements** - -| REQ | Description | Note | -|----------------|-------------------------------------------------------------------------------|------| -| REQ-A1-ML-FUN1 | A1-ML shall support authorization of service access requests | | -| REQ-A1-ML-FUN2 | A1-ML shall support the request of AI/ML model training | | -| REQ-A1-ML-FUN3 | A1-ML shall support query of AI/ML model training job status. | | -| REQ-A1-ML-FUN4 | A1-ML shall support notification for AI/ML model training job status changes. | | -| REQ-A1-ML-FUN5 | A1-ML shall support discovery of AI/ML model training capabilities. | | -| REQ-A1-ML-FUN6 | A1-ML shall support cancellation of AI/ML model training | | - -# 6 Use cases for A1 policy management - -## 6.1 Policy type discovery use cases - -### 6.1.1 Background and goal of the use cases - -The policy type discovery use cases define how Non-RT RIC can detect which A1 policy types are available in a Near-RT RIC and how Non-RT RIC can retrieve information about one or more A1 policy types. - -Policy type information is provided by the Near-RT RIC and is used by Non-RT RIC for creating and by Near-RT RIC for validating A1 policies. When policy type identifier and policy type information are known, the Non-RT RIC can create A1 policies in a Near-RT RIC as described by policy creation use cases. - -### 6.1.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - - a) Discovers A1 policy types available in Near-RT RIC. -- 2) Near-RT RIC: - - b) Makes A1 policy types available to Non-RT RIC for which it can support A1 policies. - -### 6.1.3 Solutions - -#### 6.1.3.1 Query all policy type identifiers - -**Table 6.1.3.1-1: Query all policy type identifiers use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to discover policy type identifiers for A1 policy types that are available in Near-RT RIC | | -| Actors and Roles | Non-RT RIC as A1-P Consumer
Near-RT RIC as A1-P Producer | | -| Assumptions | A1 policy types are available in Near-RT RIC | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-P service | | -| Begins when | Non-RT RIC initiates A1 policy type identifiers query | | -| Step 1 (M) | Non-RT RIC sends Query policy type identifiers request | | -| Step 2 (M) | Near-RT RIC sends Query policy type identifiers response containing policy type identifiers | | -| Ends when | Non-RT RIC has received policy type identifiers for all available A1 policy types | | -| Exceptions | | | -| Post-conditions | Policy type identifiers are known to Non-RT RIC | | -| Traceability | REQ-A1-P-FUN1 | | - -![Sequence diagram for Figure 6.1.3.1-1: Query all policy type identifiers. It shows a Non-RT RIC sending a request to a Near-RT RIC and receiving a response.](e9314c83043183351ed74908e9bf2f90_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Non-RT RIC->>Near-RT RIC: 1 <> Query policy type identifiers request - Near-RT RIC-->>Non-RT RIC: 2 <> Query policy type identifiers response (policy type identifiers) - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - -``` - -Sequence diagram for Figure 6.1.3.1-1: Query all policy type identifiers. It shows a Non-RT RIC sending a request to a Near-RT RIC and receiving a response. - -Figure 6.1.3.1-1: Query all policy type identifiers - -#### 6.1.3.2 Query single policy type - -Table 6.1.3.2-1: Query single policy type use case - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to retrieve policy type information about an A1 policy type | | -| Actors and Roles | Non-RT RIC as A1-P Consumer
Near-RT RIC as A1-P Producer | | -| Assumptions | The policy type identifier known to the Non-RT RIC corresponds to an available A1 policy type | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-P service.
The policy type identifier is known to the Non-RT RIC. | | -| Begins when | Non-RT RIC initiates A1 policy type query | | -| Step 1 (M) | Non-RT RIC sends Query single policy type request containing the policy type identifier of the policy type being queried | | -| Step 2 (M) | Near-RT RIC sends Query single policy type response containing policy type information | | -| Ends when | Non-RT RIC has received the A1 policy type information | | -| Exceptions | | | -| Post-conditions | A1 policy type information is known to Non-RT RIC | | -| Traceability | REQ-A1-P-FUN2, REQ-A1-P-FUN3 | | - -![Sequence diagram for Figure 6.1.3.2-1: Query single policy type. It shows a Non-RT RIC sending a request with a policy type identifier to a Near-RT RIC and receiving a response with policy type information.](8e14350b4b669119a3bdfca7869110ca_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Non-RT RIC->>Near-RT RIC: 1 <> Query single policy type request (policy type identifier) - Near-RT RIC-->>Non-RT RIC: 2 <> Query single policy type response (policy type information) - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - -``` - -Sequence diagram for Figure 6.1.3.2-1: Query single policy type. It shows a Non-RT RIC sending a request with a policy type identifier to a Near-RT RIC and receiving a response with policy type information. - -Figure 6.1.3.2-1: Query single policy type - -#### 6.1.3.3 Query multiple policy types - -**Table 6.1.3.3-1: Query multiple policy types use case** - -| Use case stage | Evolution / specification | <>
Related use | -|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to retrieve policy type information for a selection of A1 policy types it is interested in | | -| Actors and Roles | Non-RT RIC as A1-P Consumer
Near-RT RIC as A1-P Producer | | -| Assumptions | The policy type identifiers known to the Non-RT RIC correspond to available A1 policy types | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-P service.
The policy type identifiers are known to the Non-RT RIC. | | -| Begins when | Non-RT RIC initiates A1 policy types query | | -| Step 1 - ref (M) | Non-RT RIC queries for information about a single policy type | 6.1.3.2 | -| Step 2 - loop (M) | Non-RT RIC repeats Step 1 for the policy type identifiers it is interested in | | -| Ends when | Non-RT RIC has received information about multiple available A1 policy types | | -| Exceptions | | | -| Post-conditions | Information about multiple A1 policy types is known to Non-RT RIC | | -| Traceability | REQ-A1-P-FUN2, REQ-A1-P-FUN3 | | - -![Sequence diagram for 'Query multiple policy types' showing a loop for multiple policy type identifiers, with a reference to the single policy type query use case.](7f17c430b9598e4d748a8041457810b3_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note left of Non-RT RIC: Query multiple policy types - loop for a selection of policy type identifiers - ref for Query single policy type - end - -``` - -Sequence diagram for 'Query multiple policy types' showing a loop for multiple policy type identifiers, with a reference to the single policy type query use case. - -**Figure 6.1.3.3-1: Query multiple policy types** - -#### 6.1.3.4 Query all policy type information - -**Table 6.1.3.4-1: Query all policy type information use case** - -| Use case stage | Evolution / specification | <>
Related use | -|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to retrieve policy type information for all A1 policy types that are available in Near-RT RIC | | -| Actors and Roles | Non-RT RIC as A1-P Consumer
Near-RT RIC as A1-P Producer | | -| Assumptions | The policy type identifiers known to the Non-RT RIC correspond to all available A1 policy types. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-P service.
All policy type identifiers are known to the Non-RT RIC. | | -| Begins when | Non-RT RIC initiates A1 policy types query | | -| Step 1 - ref (M) | Non-RT RIC queries for information about a single policy type | 6.1.3.2 | -| Step 2 - loop (M) | Non-RT RIC repeats Step 1 for all policy type identifiers | | -| Ends when | Non-RT RIC has received information about all available A1 policy types | | -| Exceptions | | | -| Post-conditions | Information about all available A1 policy types is known to Non-RT RIC | | -| Traceability | REQ-A1-P-FUN2, REQ-A1-P-FUN3 | | - -![Sequence diagram for 'Query all policy types' use case. It shows a 'Non-RT RIC' actor on the left and a 'Near-RT RIC' actor on the right. A 'loop' box labeled '[for all policy type identifiers]' contains a 'ref' box labeled 'Query single policy type'. The interaction starts with a dashed arrow from Non-RT RIC to Near-RT RIC, and ends with a dashed arrow from Near-RT RIC back to Non-RT RIC.](410562339ce067fdc6fa41940c118658_img.jpg) - -Sequence diagram for 'Query all policy types' use case. It shows a 'Non-RT RIC' actor on the left and a 'Near-RT RIC' actor on the right. A 'loop' box labeled '[for all policy type identifiers]' contains a 'ref' box labeled 'Query single policy type'. The interaction starts with a dashed arrow from Non-RT RIC to Near-RT RIC, and ends with a dashed arrow from Near-RT RIC back to Non-RT RIC. - -**Figure 6.1.3.4-1: Query all policy types** - -### 6.1.4 Required data - -An A1 policy type is identified by a policy type identifier. A list of policy type identifiers is provided by Near-RT RIC corresponding to available A1 policy types. The Non-RT RIC provides a policy type identifier when querying for information about a single A1 policy type. The Near-RT RIC includes policy type information in response to a query for information about an A1 policy type. - -## 6.2 Policy type status use cases - -### 6.2.1 Background and goal of the use cases - -The policy type status use cases define how Non-RT RIC can detect status of an A1 policy type and subscribe to notifications for changes in availability and state of policy types. - -Policy type status information is provided by the Near-RT RIC and is used by Non-RT RIC when managing A1 policies. - -### 6.2.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - -- a) Requests policy type status. - - b) Subscribes to notifications for changes in policy type status. -- 2) Near-RT RIC: -- a) Responds to queries for policy type status. - - b) Handles subscriptions and notifies Non-RT RIC about changes in availability and state of policy types. - -### 6.2.3 Solutions - -#### 6.2.3.1 Query policy type status - -**Table 6.2.3.1-1: Query policy type status use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to retrieve policy type status information for an A1 policy type | | -| Actors and Roles | Non-RT RIC as A1-P Consumer
Near-RT RIC as A1-P Producer | | -| Assumptions | The policy type identifier known to the Non-RT RIC corresponds to an available policy type | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-P service.
The policy type identifier is known to the Non-RT RIC. | | -| Begins when | Non-RT RIC initiates A1 policy type status query | | -| Step 1 (M) | Non-RT RIC sends Query policy type status request containing the policy type identifier of the policy type being queried for status | | -| Step 2 (M) | Near-RT RIC sends Query policy type status response containing policy type status information | | -| Ends when | Non-RT RIC has received the A1 policy type status information | | -| Exceptions | | | -| Post-conditions | Policy type status information is known to Non-RT RIC | | -| Traceability | REQ-A1-P-FUN4 | | - -![Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for querying policy type status. The diagram shows two lifelines for Non-RT RIC and Near-RT RIC. Step 1: A solid arrow labeled '1 <> Query policy type status request (policy type identifier)' goes from the top Non-RT RIC box to the top Near-RT RIC box. Step 2: A dashed arrow labeled '2 <> Query policy type status response (policy type status information)' goes from the bottom Near-RT RIC box to the bottom Non-RT RIC box.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) - -Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for querying policy type status. The diagram shows two lifelines for Non-RT RIC and Near-RT RIC. Step 1: A solid arrow labeled '1 <> Query policy type status request (policy type identifier)' goes from the top Non-RT RIC box to the top Near-RT RIC box. Step 2: A dashed arrow labeled '2 <> Query policy type status response (policy type status information)' goes from the bottom Near-RT RIC box to the bottom Non-RT RIC box. - -**Figure 6.2.3.3-1: Query policy type status** - -#### 6.2.3.2 Subscription for policy type status notification - -**Table 6.2.3.2-1: Subscribe policy type status use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to subscribe to notifications for policy type status information for A1 policy types | | -| Actors and Roles | Non-RT RIC as A1-P Consumer
Near-RT RIC as A1-P Producer | | -| Assumptions | Non-RT RIC is interested in notifications of policy types that are made available or unavailable, and/or notifications of state changes of a policy type | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-P service.
Policy type identifiers are known to the Non-RT RIC when subscribing for notifications on type state changes. | | -| Begins when | Non-RT RIC initiates A1 Policy type status subscribe | | -| Step 1 (M) | Non-RT RIC sends Subscribe policy type status request containing the policy type status subscription information including policy type identifier(s) if type state changes are requested. | | -| Step 2 (M) | Near-RT RIC sends Subscribe policy type status response | | -| Ends when | Policy type status subscription has been created | | -| Exceptions | | | -| Post-conditions | Non-RT RIC is subscribed to policy type status notifications | | -| Traceability | REQ-A1-P-FUN5 | | - -**Table 6.2.3.2-2: Update policy type status subscription use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to update its subscription to notifications for policy type status information for A1 policy types | | -| Actors and Roles | Non-RT RIC as A1-P Consumer
Near-RT RIC as A1-P Producer | | -| Assumptions | Non-RT RIC is interested in notifications of policy types that are made available or unavailable, and/or notifications of state changes of a policy type | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-P service.
Policy type status notifications has been subscribed to. | | -| Begins when | Non-RT RIC initiates A1 Policy type status subscribe | | -| Step 1 (M) | Non-RT RIC sends Subscribe policy type status request containing the updated policy type status subscription information | | -| Step 2 (M) | Near-RT RIC sends Subscribe policy type status response | | -| Ends when | Policy type status subscription has been updated | | -| Exceptions | | | -| Post-conditions | Non-RT RIC is subscribed to policy type status notifications | | -| Traceability | REQ-A1-P-FUN5 | | - -**Table 6.2.3.2-3: Unsubscribe policy type status use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to unsubscribe from notifications for policy type status information for A1 policy types | | -| Actors and Roles | Non-RT RIC as A1-P Consumer
Near-RT RIC as A1-P Producer | | -| Assumptions | Non-RT RIC is no longer interested in notifications of policy types status | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-P service.
Policy type status notifications has been subscribed to. | | -| Begins when | Non-RT RIC initiates A1 Policy type status unsubscribe | | -| Step 1 (M) | Non-RT RIC sends Subscribe policy type status request containing policy type status subscription information with no content | | -| Step 2 (M) | Near-RT RIC sends Subscribe policy type status response | | -| Ends when | Policy type status subscription has been deleted | | -| Exceptions | | | -| Post-conditions | Non-RT RIC is not subscribed to policy type status notifications | | -| Traceability | REQ-A1-P-FUN5 | | - -![Sequence diagram showing the subscription for policy type status notifications. It involves two lifelines: Non-RT RIC and Near-RT RIC. Step 1: Non-RT RIC sends a 'Subscribe policy type status request (policy type status subscription information)' to Near-RT RIC. Step 2: Near-RT RIC sends a 'Subscribe policy type status response' back to Non-RT RIC.](16152cf1d84aea10848758f51a91ff6a_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Non-RT RIC->>Near-RT RIC: 1 <> Subscribe policy type status request (policy type status subscription information) - Near-RT RIC-->>Non-RT RIC: 2 <> Subscribe policy type status response - -``` - -Sequence diagram showing the subscription for policy type status notifications. It involves two lifelines: Non-RT RIC and Near-RT RIC. Step 1: Non-RT RIC sends a 'Subscribe policy type status request (policy type status subscription information)' to Near-RT RIC. Step 2: Near-RT RIC sends a 'Subscribe policy type status response' back to Non-RT RIC. - -**Figure 6.2.3.2-1: Subscription for policy type status notifications** - -#### 6.2.3.3 Notify policy type status - -**Table 6.2.3.3-1: Notify policy type status use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to receive policy type status information for an A1 Policy type | | -| Actors and Roles | Non-RT RIC as A1-P Consumer
Near-RT RIC as A1-P Producer | | -| Assumptions | | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-P service.
Non-RT RIC has subscribed to policy type status notifications and provided a callback URI. | | -| Begins when | Event occurs in Near-RT RIC related to the status of an A1 Policy type, either a change in availability or of the type state | | -| Step 1 (M) | Near-RT RIC sends Notify policy type status message containing the policy type status information | | -| Ends when | Non-RT RIC has received the policy type status information | | -| Exceptions | | | -| Post-conditions | Policy type status information is known to Non-RT RIC | | -| Traceability | REQ-A1-P-FUN5 | | - -![Sequence diagram showing a 'Notify policy type status' message from a Near-RT RIC to a Non-RT RIC. The diagram shows two lifelines: Non-RT RIC and Near-RT RIC. A message labeled '1 <> Notify policy type status (policy type status information)' is sent from the top Near-RT RIC to the bottom Non-RT RIC.](2cde062fd82833415971a8bd1a2cafab_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note right of Near-RT RIC: - Note left of Non-RT RIC: - Near-RT RIC->>Non-RT RIC: 1 <> Notify policy type status (policy type status information) - -``` - -Sequence diagram showing a 'Notify policy type status' message from a Near-RT RIC to a Non-RT RIC. The diagram shows two lifelines: Non-RT RIC and Near-RT RIC. A message labeled '1 <> Notify policy type status (policy type status information)' is sent from the top Near-RT RIC to the bottom Non-RT RIC. - -Figure 6.2.3.3-1: Notify policy type status - -### 6.2.4 Required data - -The policy type status information includes policy type availability change information (i.e. if A1 policy type has been made available or unavailable) and/or state change information related to an A1 policy type. - -The state of the A1 policy type indicates if A1 policies can be created for the policy type or not, and if A1 policies for the policy type would be enforced or not enforced. - -The policy type status subscription information includes details on whether notifications are requested for changes in A1 policy type availability and/or changes in state of the A1 policy type for which policy type identifiers were provided. - -## 6.3 Create policy use cases - -### 6.3.1 Background and goal of the use cases - -The create policy use cases define how Non-RT RIC can create an A1 policy for an A1 policy type and subscribe to notifications for changes in policy status. - -### 6.3.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - - a) Creates A1 policy in Near-RT RIC. -- 2) Near-RT RIC: - - b) Enforces A1 policies for available A1 policy types. - -### 6.3.3 Solutions - -#### 6.3.3.1 Create single policy - -**Table 6.3.3.1-1: Create single policy use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to create A1 policy for an A1 policy type | | -| Actors and Roles | Non-RT RIC as A1-P Consumer
Near-RT RIC as A1-P Producer | | -| Assumptions | The policy type information known to the Non-RT RIC corresponds to an available A1 policy type.
Non-RT RIC has the schema for formulating A1 policy information. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-P service.
The policy type information is known to the Non-RT RIC. | | -| Begins when | Non-RT RIC initiates A1 policy creation | | -| Step 1 (M) | Non-RT RIC sends Create policy request containing the policy identifier and the policy information | | -| Step 2 (M) | Near-RT RIC sends Create policy response | | -| Ends when | A1 policy has been created | | -| Exceptions | | | -| Post-conditions | The A1 policy exists | | -| Traceability | REQ-A1-P-FUN6 | | - -![Sequence diagram for 'Create single policy' use case. It shows two lifelines: Non-RT RIC and Near-RT RIC. Step 1: Non-RT RIC sends a solid arrow message '1 <> Create single policy request (policy identifier, policy information)' to Near-RT RIC. Step 2: Near-RT RIC sends a dashed return arrow message '2 <> Create single policy response' back to Non-RT RIC.](8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg) - -Sequence diagram for 'Create single policy' use case. It shows two lifelines: Non-RT RIC and Near-RT RIC. Step 1: Non-RT RIC sends a solid arrow message '1 <> Create single policy request (policy identifier, policy information)' to Near-RT RIC. Step 2: Near-RT RIC sends a dashed return arrow message '2 <> Create single policy response' back to Non-RT RIC. - -**Figure 6.3.3.4-1: Create single policy** - -### 6.3.4 Required data - -For creating an A1 policy of a certain policy type, the Non-RT RIC provides the policy identifier and the policy information, the callback URI for policy result delivery, and optionally the callback URI for policy status notifications. - -## 6.4 Query policy use cases - -### 6.4.1 Background and goal of the use cases - -The query policies use cases define how Non-RT RIC can query for information on existing A1 policies. - -### 6.4.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - - a) Discovers A1 policies that exist in the Near-RT RIC. - -- b) Retrieves policy information. -- 2) Near-RT RIC: - - a) Handles A1 policies. - - b) Responds to queries for policy identifiers and policy information. - -### 6.4.3 Solutions - -#### 6.4.3.1 Query policy identifiers - -**Table 6.4.3.1-1: Query policy identifiers use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to discover policy identifiers for A1 policies that exist in Near-RT RIC | | -| Actors and Roles | Non-RT RIC as A1-P Consumer
Near-RT RIC as A1-P Producer | | -| Assumptions | A1 policies exist in Near-RT RIC | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-P service | | -| Begins when | Non-RT RIC initiates A1 policy identifiers query | | -| Step 1 (M) | Non-RT RIC sends Query policy identifiers request | | -| Step 2 (M) | Near-RT RIC sends Query policy identifiers response containing policy identifiers | | -| Ends when | Non-RT RIC has received policy identifiers for existing A1 policies | | -| Exceptions | | | -| Post-conditions | Policy identifiers are known to Non-RT RIC | | -| Traceability | REQ-A1-P-FUN7 | | - -![Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for querying policy identifiers. Step 1: Non-RT RIC sends a 'Query policy identifiers request' to Near-RT RIC. Step 2: Near-RT RIC returns a 'Query policy identifiers response (policy identifiers)' to Non-RT RIC.](12de9b926df0384ec07702671827c9cd_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Non-RT RIC->>Near-RT RIC: 1 <> Query policy identifiers request - Near-RT RIC-->>Non-RT RIC: 2 <> Query policy identifiers response (policy identifiers) - -``` - -Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for querying policy identifiers. Step 1: Non-RT RIC sends a 'Query policy identifiers request' to Near-RT RIC. Step 2: Near-RT RIC returns a 'Query policy identifiers response (policy identifiers)' to Non-RT RIC. - -**Figure 6.4.3.1-1: Query policy identifiers** - -#### 6.4.3.2 Query single policy - -**Table 6.4.3.2-1: Query single policy use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to retrieve information about an A1 policy | | -| Actors and Roles | Non-RT RIC as A1-P Consumer
Near-RT RIC as A1-P Producer | | -| Assumptions | The A1 policy identifier known to the Non-RT RIC corresponds to an existing A1 policy.
Non-RT RIC has the schema for interpreting policy information. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-P service.
The policy identifier is known to the Non-RT RIC. | | -| Begins when | Non-RT RIC initiates A1 policy query | | -| Step 1 (M) | Non-RT RIC sends Query policy request containing the policy identifier | | -| Step 2 (M) | Near-RT RIC sends Query policy response containing policy information | | -| Ends when | Non-RT RIC has received the policy information about the A1 policy | | -| Exceptions | | | -| Post-conditions | Policy information is known to Near-RT RIC | | -| Traceability | REQ-A1-P-FUN8 | | - -![Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for a 'Query single policy' use case. Step 1: Non-RT RIC sends a 'Query single policy request (policy identifier)' to Near-RT RIC. Step 2: Near-RT RIC sends a 'Query single policy response (policy information)' back to Non-RT RIC.](3da1a07cb87051bf616c9876db958cf0_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Non-RT RIC->>Near-RT RIC: 1 <> Query single policy request (policy identifier) - Near-RT RIC-->>Non-RT RIC: 2 <> Query single policy response (policy information) - -``` - -Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for a 'Query single policy' use case. Step 1: Non-RT RIC sends a 'Query single policy request (policy identifier)' to Near-RT RIC. Step 2: Near-RT RIC sends a 'Query single policy response (policy information)' back to Non-RT RIC. - -**Figure 6.4.3.2-1: Query single policy** - -### 6.4.4 Required data - -For querying policy identifiers, the Non-RT RIC optionally provides a policy type identifier as filter parameter. - -For querying an A1 policy, the Non-RT RIC provides a policy identifier. - -The policy information includes the A1 policy definition. - -## 6.5 Update policy use cases - -### 6.5.1 Background and goal of the use cases - -The update policy use cases define how Non-RT RIC can update an existing A1 policy. - -Non-RT RIC provides updated policy information. The reason for the update can be related to state of the A1 policy type and received policy status information. - -### 6.5.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - -- a) Updates A1 policy in Near-RT RIC that it has created. -- 2) Near-RT RIC: - - b) Handles A1 policies for available policy types. - -### 6.5.3 Solutions - -#### 6.5.3.1 Update single policy - -**Table 6.5.3.1-1: Update single policy use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to update an existing A1 policy | | -| Actors and Roles | Non-RT RIC as A1-P Consumer
Near-RT RIC as A1-P Producer | | -| Assumptions | The policy identifier known to the Non-RT RIC corresponds to an existing A1 policy that was created by the Non-RT RIC | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-P service.
The A1 policy exists. | | -| Begins when | Non-RT RIC initiates A1 policy update | | -| Step 1 (M) | Non-RT RIC sends Update policy request containing the updated policy information | | -| Step 2 (M) | Near-RT RIC sends Update policy response | | -| Ends when | A1 policy has been updated | | -| Exceptions | | | -| Post-conditions | The A1 policy exists | | -| Traceability | REQ-A1-P-FUN6 | | - -![Sequence diagram for Update single policy use case. It shows two lifelines: Non-RT RIC and Near-RT RIC. Step 1: Non-RT RIC sends a solid arrow message '1 <> Update single policy request (policy information)' to Near-RT RIC. Step 2: Near-RT RIC sends a dashed return arrow message '2 <> Update single policy response' back to Non-RT RIC.](73dff6b45b2b9ffd384bab3235f869af_img.jpg) - -Sequence diagram for Update single policy use case. It shows two lifelines: Non-RT RIC and Near-RT RIC. Step 1: Non-RT RIC sends a solid arrow message '1 <> Update single policy request (policy information)' to Near-RT RIC. Step 2: Near-RT RIC sends a dashed return arrow message '2 <> Update single policy response' back to Non-RT RIC. - -**Figure 6.5.3.4-1: Update single policy** - -### 6.5.4 Required data - -For updating an A1 policy, the Non-RT RIC provides the policy identifier and updated policy information and/or callback URI for policy status notifications. - -## 6.6 Delete policy use cases - -### 6.6.1 Background and goal of the use cases - -The delete policy use cases define how Non-RT RIC can delete an A1 policy. - -The reason for the deletion can be related to the state of the A1 policy type and received policy status information. - -### 6.6.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - - a) Deletes A1 policy in Near-RT RIC that it has created. -- 2) Near-RT RIC: - - b) Handles A1 policies for available policy types. - -### 6.6.3 Solutions - -#### 6.6.3.1 Delete single policy - -**Table 6.6.3.1-1: Delete single policy use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to delete an existing A1 policy | | -| Actors and Roles | Non-RT RIC as A1-P Consumer
Near-RT RIC as A1-P Producer | | -| Assumptions | The policy identifier known to the Non-RT RIC corresponds to an existing A1 policy that was created by the Non-RT RIC | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-P service.
The A1 policy exists. | | -| Begins when | Non-RT RIC initiates A1 policy deletion | | -| Step 1 (M) | Non-RT RIC sends Delete policy request containing the policy identifier | | -| Step 2 (M) | Near-RT RIC sends Delete policy response | | -| Ends when | A1 policy has been deleted | | -| Exceptions | | | -| Post-conditions | The A1 policy does not exist | | -| Traceability | REQ-A1-P-FUN6 | | - -![Sequence diagram for 'Delete single policy' use case. It shows two lifelines: Non-RT RIC and Near-RT RIC. Step 1: A solid arrow points from the top Non-RT RIC box to the top Near-RT RIC box, labeled '1 <> Delete single policy request (policy identifier)'. Step 2: A dashed arrow points from the top Near-RT RIC box to the bottom Non-RT RIC box, labeled '2 <> Delete single policy response'.](b2ea162a0f53d5e0504b7d28346e0754_img.jpg) - -Sequence diagram for 'Delete single policy' use case. It shows two lifelines: Non-RT RIC and Near-RT RIC. Step 1: A solid arrow points from the top Non-RT RIC box to the top Near-RT RIC box, labeled '1 <> Delete single policy request (policy identifier)'. Step 2: A dashed arrow points from the top Near-RT RIC box to the bottom Non-RT RIC box, labeled '2 <> Delete single policy response'. - -**Figure 6.6.3.1-1: Delete single policy** - -### 6.6.4 Required data - -For deleting an A1 policy, the Non-RT RIC provides the policy identifier. - -## 6.7 Policy status use cases - -### 6.7.1 Background and goal of the use cases - -The policy status use cases define how Non-RT RIC can detect status, and changes in status, of an A1 policy. - -Policy status information is provided by the Near-RT RIC and is used by Non-RT RIC when managing A1 policies. - -### 6.7.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - - a) Requests A1 policy status. - - b) Receives notifications about changes in policy status. -- 2) Near-RT RIC: - - a) Handles A1 policy and responds to queries for policy status. - - b) Notifies Non-RT RIC about changes in policy status. - -### 6.7.3 Solutions - -#### 6.7.3.1 Query policy status - -**Table 6.7.3.1-1: Query policy status use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to retrieve policy status information for an existing A1 policy | | -| Actors and Roles | Non-RT RIC as A1-P Consumer
Near-RT RIC as A1-P Producer | | -| Assumptions | The policy identifier known to the Non-RT RIC corresponds to an existing A1 policy that was created by the Non-RT RIC.
Non-RT RIC has the schema for interpreting policy status information. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-P service.
The policy identifier is known to the Non-RT RIC. | | -| Begins when | Non-RT RIC initiates A1 policy status query | | -| Step 1 (M) | Non-RT RIC sends Query policy status request containing the policy identifier of the A1 policy being queried for status | | -| Step 2 (M) | Near-RT RIC sends Query policy status response containing policy status information | | -| Ends when | Non-RT RIC has received the A1 policy status information | | -| Exceptions | | | -| Post-conditions | Policy status information is known to Non-RT RIC | | -| Traceability | REQ-A1-P-FUN9 | | - -![Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for querying policy status. Step 1: Non-RT RIC sends a 'Query policy status request (policy identifier)' to Near-RT RIC. Step 2: Near-RT RIC returns a 'Query policy status response (policy status information)' to Non-RT RIC.](19a59d6b53059ebd27b13c98793f88e0_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Non-RT RIC->>Near-RT RIC: 1 <> Query policy status request (policy identifier) - Near-RT RIC-->>Non-RT RIC: 2 <> Query policy status response (policy status information) - -``` - -Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for querying policy status. Step 1: Non-RT RIC sends a 'Query policy status request (policy identifier)' to Near-RT RIC. Step 2: Near-RT RIC returns a 'Query policy status response (policy status information)' to Non-RT RIC. - -**Figure 6.7.3.1-1: Query policy status** - -#### 6.7.3.2 Notify policy status change - -**Table 6.7.3.2-1: Notify policy status change use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to receive policy status change information for an existing A1 policy | | -| Actors and Roles | Non-RT RIC as A1-P Consumer
Near-RT RIC as A1-P Producer | | -| Assumptions | Non-RT RIC has the schema for interpreting policy status information. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-P service.
A callback URI for policy status notifications has been provided when creating and/or updating the A1 policy. | | -| Begins when | Event occurs in Near-RT RIC related to the status change of the A1 policy | | -| Step 1 (M) | Near-RT RIC sends Notify policy status message containing the policy status information | | -| Ends when | Non-RT RIC has received the A1 policy status change information | | -| Exceptions | | | -| Post-conditions | Policy status information is known to Non-RT RIC | | -| Traceability | REQ-A1-P-FUN10 | | - -![Sequence diagram showing the 'Notify policy status change' interaction. A dashed vertical line on the left represents the Non-RT RIC, and a dashed vertical line on the right represents the Near-RT RIC. A solid horizontal arrow points from the Near-RT RIC to the Non-RT RIC, labeled '1 <> Notify policy status (policy status change information)'.](7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg) - -Sequence diagram showing the 'Notify policy status change' interaction. A dashed vertical line on the left represents the Non-RT RIC, and a dashed vertical line on the right represents the Near-RT RIC. A solid horizontal arrow points from the Near-RT RIC to the Non-RT RIC, labeled '1 <> Notify policy status (policy status change information)'. - -**Figure 6.7.3.2-1: Notify policy status change** - -### 6.7.4 Required data - -The policy status information includes the A1 policy status that is formulated based on, and validated against, the policy status schema and indicates if A1 policy is enforced or not enforced. - -The policy status change information includes indication about a change of the A1 policy status. - -# --- 7 Use cases for A1 enrichment information - -## 7.1 EI discovery use cases - -### 7.1.1 Background and goal of the use cases - -The EI discovery use cases define how Near-RT RIC can detect which EI types are available in Non-RT RIC and how Near-RT RIC can retrieve information about EI types. - -EI type information is provided by Non-RT RIC and is used by Near-RT RIC for creating, and by Non-RT RIC for validating, EI jobs. EI type information is also used by Non-RT RIC for creating, and by Near-RT RIC for validating, EI job results. - -When EI type identifier and EI type information are known, the Near-RT RIC can create EI jobs in a Non-RT RIC as described by EI job creation use cases, and the Non-RT RIC can deliver EI job results to Near-RT RIC as described by EI delivery use cases. - -EI job constraints information is provided by Non-RT RIC and used by Near-RT RIC when formulating EI job definitions based on the EI type information. - -### 7.1.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - - a) Makes EI types available to Near-RT RIC for which it can support EI jobs and deliver EI job results. - - b) Provides information on EI types and constraints for EI jobs. -- 2) Near-RT RIC: - - a) Discovers EI types available in Non-RT RIC. - - b) Retrieves EI type information. - -### 7.1.3 Solutions - -#### 7.1.3.1 Query EI type identifiers - -**Table 7.1.3.1-1: Query EI type identifiers use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC to discover EI type identifiers for EI types that are available in Non-RT RIC | | -| Actors and Roles | Non-RT RIC as A1-EI Producer
Near-RT RIC as A1-EI Consumer | | -| Assumptions | EI types are available in Non-RT RIC | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-EI service | | -| Begins when | Near-RT RIC initiates EI type identifiers query | | -| Step 1 (M) | Near-RT RIC sends Query EI type identifiers request | | -| Step 2 (M) | Non-RT RIC sends Query EI type identifiers response containing EI type identifiers | | -| Ends when | Near-RT RIC has received EI type identifiers for available EI types | | -| Exceptions | | | -| Post-conditions | EI type identifiers are known to Non-RT RIC | | -| Traceability | REQ-A1-EI-FUN1 | | - -![Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for Query EI type identifiers. Step 1: Near-RT RIC sends a request to Non-RT RIC. Step 2: Non-RT RIC sends a response back to Near-RT RIC.](dd380ccd5aca1151074fede04826f1a4_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Near-RT RIC->>Non-RT RIC: 1 <> Query EI type identifiers request - Non-RT RIC-->>Near-RT RIC: 2 <> Query EI type identifiers response (EI type identifiers) - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - -``` - -Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for Query EI type identifiers. Step 1: Near-RT RIC sends a request to Non-RT RIC. Step 2: Non-RT RIC sends a response back to Near-RT RIC. - -**Figure 7.1.3.1-1: Query EI type identifiers** - -#### 7.1.3.2 Query EI type - -**Table 7.1.3.2-1: Query EI type use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC to retrieve EI type information about an EI type | | -| Actors and Roles | Non-RT RIC as A1-EI Producer
Near-RT RIC as A1-EI Consumer | | -| Assumptions | The EI type identifier known to the Near-RT RIC corresponds to an available EI type | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-EI service.
The EI type identifier is known to the Near-RT RIC. | | -| Begins when | Near-RT RIC initiates EI type query | | -| Step 1 (M) | Near-RT RIC sends Query EI type request containing the EI type identifier of the EI type being queried | | -| Step 2 (M) | Non-RT RIC sends Query EI type response containing EI type information and EI job constraints information | | -| Ends when | Near-RT RIC has received the EI type information | | -| Exceptions | | | -| Post-conditions | EI type information is known to Near-RT RIC | | -| Traceability | REQ-A1-EI-FUN2, REQ-A1-EI-FUN3 | | - -![Sequence diagram for Query EI type use case. It shows two lifelines: Non-RT RIC (top left) and Near-RT RIC (top right). Step 1: A solid arrow points from Near-RT RIC to Non-RT RIC with the message '1 <> Query EI type request (EI type identifier)'. Step 2: A dashed arrow points from Non-RT RIC to Near-RT RIC with the message '2 <> Query EI type response (EI type information, EI job constraints information)'. The lifelines are labeled again at the bottom.](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) - -Sequence diagram for Query EI type use case. It shows two lifelines: Non-RT RIC (top left) and Near-RT RIC (top right). Step 1: A solid arrow points from Near-RT RIC to Non-RT RIC with the message '1 <> Query EI type request (EI type identifier)'. Step 2: A dashed arrow points from Non-RT RIC to Near-RT RIC with the message '2 <> Query EI type response (EI type information, EI job constraints information)'. The lifelines are labeled again at the bottom. - -**Figure 7.1.3.2-1: Query EI type** - -### 7.1.4 Required data - -An EI type is identified by an EI type identifier. A list of EI type identifiers is provided by Non-RT RIC corresponding to available EI types. The Near-RT RIC provides an EI type identifier when querying for information about an EI type. In response to a query for information about an EI type, the Non-RT RIC includes EI type information and optionally also EI job constraints information. - -The EI type information includes the schemas for EI job definition, EI job status, EI job result and EI job constraints. The EI job constraints information includes information on how EI job can be created and how EI job results can be produced and delivered. - -## 7.2 EI type status use cases - -### 7.2.1 Background and goal of the use cases - -The EI type status use cases define how Near-RT RIC can detect status of an EI type and subscribe to notifications for changes in availability and status of EI types. - -EI type status information is provided by the Non-RT RIC and is used by Near-RT RIC when managing EI jobs. - -### 7.2.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - - a) Responds to queries for EI type status. - - b) Handles subscriptions and notifies Near-RT RIC about changes in availability and state of EI types. -- 2) Near-RT RIC: - - a) Requests EI type status. - - b) Subscribes to notifications for changes in EI type status. - -### 7.2.3 Solutions - -#### 7.2.3.1 Query EI type status - -**Table 7.2.3.1-1: Query EI type status use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC to retrieve EI type status information for an EI type | | -| Actors and Roles | Non-RT RIC as A1-EI Producer
Near-RT RIC as A1-EI Consumer | | -| Assumptions | The EI type identifier known to the Near-RT RIC corresponds to an available EI type | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-EI service.
The EI type identifier is known to the Near-RT RIC. | | -| Begins when | Near-RT RIC initiates EI type status query | | -| Step 1 (M) | Near-RT RIC sends Query EI type status request containing the EI type identifier of the EI type being queried for status | | -| Step 2 (M) | Non-RT RIC sends Query EI type status response containing EI type status information | | -| Ends when | Near-RT RIC has received the EI type status information | | -| Exceptions | | | -| Post-conditions | EI type status information is known to Near-RT RIC | | -| Traceability | REQ-A1-EI-FUN4 | | - -![Sequence diagram for Query EI type status. It shows two lifelines: Non-RT RIC and Near-RT RIC. Step 1: Near-RT RIC sends a solid arrow message '1 <> Query EI type status request (EI type identifier)' to Non-RT RIC. Step 2: Non-RT RIC sends a dashed arrow message '2 <> Query EI type status response (EI type status information)' back to Near-RT RIC.](356eb99ab9489bbd647223390a913903_img.jpg) - -Sequence diagram for Query EI type status. It shows two lifelines: Non-RT RIC and Near-RT RIC. Step 1: Near-RT RIC sends a solid arrow message '1 <> Query EI type status request (EI type identifier)' to Non-RT RIC. Step 2: Non-RT RIC sends a dashed arrow message '2 <> Query EI type status response (EI type status information)' back to Near-RT RIC. - -**Figure 7.2.3.1-1: Query EI type status** - -#### 7.2.3.2 Subscription for EI type status notification - -**Table 7.2.3.2-1: Subscribe EI type status use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC to subscribe to notifications for EI type status information | | -| Actors and Roles | Non-RT RIC as A1-EI Producer
Near-RT RIC as A1-EI Consumer | | -| Assumptions | Near-RT RIC is interested in notifications of EI types that are made available or unavailable, and/or notifications of state changes of a policy type | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-EI service.
EI type identifiers are known to the Near-RT RIC when subscribing for notifications on type state changes. | | -| Begins when | Near-RT RIC initiates EI type status subscribe | | -| Step 1 (M) | Near-RT RIC sends Subscribe EI type status request containing the EI type status subscription information including EI type identifier(s) if type state changes are requested. | | -| Step 2 (M) | Non-RT RIC sends Subscribe EI type status response | | -| Ends when | EI type status subscription has been created | | -| Exceptions | | | -| Post-conditions | Near-RT RIC is subscribed to EI type status notifications | | -| Traceability | REQ-A1-EI-FUN5 | | - -**Table 7.2.3.2-2: Update type status subscription use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC to update its subscription to notifications for EI type status information | | -| Actors and Roles | Non-RT RIC as A1-EI Producer
Near-RT RIC as A1-EI Consumer | | -| Assumptions | Near-RT RIC is interested in notifications of EI types that are made available or unavailable, and/or notifications of state changes of a policy type | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-EI service.
EI type status notifications has been subscribed to. | | -| Begins when | Near-RT RIC initiates EI type status subscribe | | -| Step 1 (M) | Near-RT RIC sends Subscribe EI type status request containing the updated EI type status subscription information | | -| Step 2 (M) | Non-RT RIC sends Subscribe EI type status response | | -| Ends when | EI type status subscription has been updated | | -| Exceptions | | | -| Post-conditions | Near-RT RIC is subscribed to EI type status notifications | | -| Traceability | REQ-A1-EI-FUN5 | | - -**Table 7.2.3.2-3: Unsubscribe EI type status use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC to unsubscribe from notifications for EI type status information | | -| Actors and Roles | Non-RT RIC as A1-EI Producer
Near-RT RIC as A1-EI Consumer | | -| Assumptions | Near-RT RIC is no longer interested in notifications of EI types status | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-EI service.
EI type status notifications have been subscribed to. | | -| Begins when | Near-RT RIC initiates EI type status unsubscribe | | -| Step 1 (M) | Near-RT RIC sends Subscribe EI type status request containing the EI type status subscription information with no content | | -| Step 2 (M) | Non-RT RIC sends Subscribe EI type status response | | -| Ends when | EI type status subscription has been deleted | | -| Exceptions | | | -| Post-conditions | Near-RT RIC is not subscribed to EI type status notifications | | -| Traceability | REQ-A1-EI-FUN5 | | - -![Sequence diagram for 'Subscribe EI type status' use case. It shows two lifelines: Non-RT RIC (top left) and Near-RT RIC (top right). Step 1: A solid arrow points from Near-RT RIC to Non-RT RIC with the message '1 <> Subscribe EI type status request (EI type status subscription information)'. Step 2: A dashed arrow points from Non-RT RIC to Near-RT RIC with the message '2 <> Subscribe EI type status response'. The lifelines are labeled again at the bottom.](474a819357587e34949a3e110ff19b30_img.jpg) - -Sequence diagram for 'Subscribe EI type status' use case. It shows two lifelines: Non-RT RIC (top left) and Near-RT RIC (top right). Step 1: A solid arrow points from Near-RT RIC to Non-RT RIC with the message '1 <> Subscribe EI type status request (EI type status subscription information)'. Step 2: A dashed arrow points from Non-RT RIC to Near-RT RIC with the message '2 <> Subscribe EI type status response'. The lifelines are labeled again at the bottom. - -**Figure 7.2.3.2-1: Subscribe EI type status** - -#### 7.2.3.3 Notify EI type status - -**Table 7.2.3.3-1: Notify EI type status use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC to receive EI type status information for an EI type | | -| Actors and Roles | Non-RT RIC as A1-EI Producer
Near-RT RIC as A1-EI Consumer | | -| Assumptions | | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-EI service.
Near-RT RIC has subscribed to EI type status notifications and provided a callback URI. | | -| Begins when | Event occurs in Non-RT RIC related to the status of an EI type, either a change in availability or of the type state | | -| Step 1 (M) | Non-RT RIC sends Notify EI type status request containing the EI type status information | | -| Ends when | Near-RT RIC has received the EI type status information | | -| Exceptions | | | -| Post-conditions | EI type status information is known to Near-RT RIC | | -| Traceability | REQ-A1-EI-FUN5 | | - -![Sequence diagram showing the 'Notify EI type status' message flow. A Non-RT RIC sends a message labeled '1 <> Notify EI type status (EI type status information)' to a Near-RT RIC. The diagram shows two instances of each RIC, with the message being sent from the top Non-RT RIC to the top Near-RT RIC.](fa01531ea2c45beeb4036005da3037a4_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC as Non-RT RIC - participant Near-RT RIC as Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Non-RT RIC->>Near-RT RIC: 1 <> Notify EI type status (EI type status information) - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - -``` - -Sequence diagram showing the 'Notify EI type status' message flow. A Non-RT RIC sends a message labeled '1 <> Notify EI type status (EI type status information)' to a Near-RT RIC. The diagram shows two instances of each RIC, with the message being sent from the top Non-RT RIC to the top Near-RT RIC. - -**Figure 7.2.3.3-1: Notify EI type status** - -### 7.2.4 Required data - -The EI type status information includes EI type availability change information (i.e. if EI type has been made available or unavailable) and/or state change information related to an EI type. - -The state of the EI type state indicates if EI jobs can be created for the EI type or not, and if EI jobs for the EI type would be enabled or disabled. - -The EI type status subscription information includes details on if notifications are requested for changes in EI type availability and/or changes in state of the EI type for which EI type identifiers were provided. - -## 7.3 Create EI job use cases - -### 7.3.1 Background and goal of the use cases - -The create EI job use cases define how Near-RT RIC can create an EI job for an EI type and subscribe to notifications for changes in EI job status. - -Near-RT RIC provides EI job definition information based on EI type information and considering the EI job constraints. - -### 7.3.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - - a) Handles EI jobs for available EI types. -- 2) Near-RT RIC: - - b) Creates EI job in Non-RT RIC. - -### 7.3.3 Solutions - -#### 7.3.3.1 Create EI job - -**Table 7.3.3.1-1: Create EI job use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC to create EI job for an EI type | | -| Actors and Roles | Non-RT RIC as A1-EI Producer
Near-RT RIC as A1-EI Consumer | | -| Assumptions | The EI type information known to the Near-RT RIC corresponds to an available EI type.
Near-RT RIC has the schema for formulating EI job definition. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-EI service.
The EI type information is known to the Near-RT RIC. | | -| Begins when | Near-RT RIC initiates EI job creation | | -| Step 1 (M) | Near-RT RIC sends Create EI job request containing the EI job identifier and the EI job definition | | -| Step 2 (M) | Non-RT RIC sends Create EI job response | | -| Ends when | EI job has been created | | -| Exceptions | | | -| Post-conditions | EI job exists | | -| Traceability | REQ-A1-EI-FUN6 | | - -![Sequence diagram for 'Create EI job' use case. It shows two lifelines: Non-RT RIC and Near-RT RIC. Step 1: Near-RT RIC sends a solid arrow message labeled '1 <> Create EI job request (EI job identifier, EI job information)' to Non-RT RIC. Step 2: Non-RT RIC sends a dashed arrow message labeled '2 <> Create EI job response' back to Near-RT RIC.](98e54d5540b2efe3e24af3cf936bc4ea_img.jpg) - -Sequence diagram for 'Create EI job' use case. It shows two lifelines: Non-RT RIC and Near-RT RIC. Step 1: Near-RT RIC sends a solid arrow message labeled '1 <> Create EI job request (EI job identifier, EI job information)' to Non-RT RIC. Step 2: Non-RT RIC sends a dashed arrow message labeled '2 <> Create EI job response' back to Near-RT RIC. - -**Figure 7.3.3.3-1: Create EI job** - -### 7.3.4 Required data - -For creating an EI job of a certain EI type, the Near-RT RIC provides the EI job identifier and the EI job information, the callback URI for EI job result delivery, and optionally the callback URI for EI job status notifications. - -EI job information includes the EI job definition that is formulated based on, and validated against, the EI job definition schema. The EI job definition can be formulated considering the EI job constraints information if provided. - -## 7.4 Query EI jobs use cases - -### 7.4.1 Background and goal of the use cases - -The query EI jobs use cases define how Near-RT RIC can query for information on existing EI jobs. - -### 7.4.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - -- a) Handles EI job. - - b) Responds to queries for EI job identifiers and EI job information. -- 2) Near-RT RIC: -- a) Discovers EI jobs available in Non-RT RIC. - - b) Retrieves EI job information. - -### 7.4.3 Solutions - -#### 7.4.3.1 Query EI job identifiers - -**Table 7.4.3.1-1: Query EI job identifiers use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC to discover job identifiers for EI jobs that exist in Non-RT RIC | | -| Actors and Roles | Non-RT RIC as A1-EI Producer
Near-RT RIC as A1-EI Consumer | | -| Assumptions | EI jobs exist in Non-RT RIC | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-EI service | | -| Begins when | Near-RT RIC initiates EI job identifiers query | | -| Step 1 (M) | Near-RT RIC sends Query EI job identifiers request | | -| Step 2 (M) | Non-RT RIC sends Query EI job identifiers response containing EI job identifiers | | -| Ends when | Near-RT RIC has received EI job identifiers | | -| Exceptions | | | -| Post-conditions | EI job identifiers are known to Non-RT RIC | | -| Traceability | REQ-A1-EI-FUN7 | | - -![Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for Query EI job identifiers. Step 1: Near-RT RIC sends a request to Non-RT RIC. Step 2: Non-RT RIC sends a response back to Near-RT RIC.](94fd137860c16c8dfd75512f10161fe8_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Near-RT RIC->>Non-RT RIC: 1 <> Query EI job identifiers request - Non-RT RIC-->>Near-RT RIC: 2 <> Query EI job identifiers response (EI job identifiers) - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - -``` - -Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for Query EI job identifiers. Step 1: Near-RT RIC sends a request to Non-RT RIC. Step 2: Non-RT RIC sends a response back to Near-RT RIC. - -**Figure 7.4.3.1-1: Query EI job identifiers** - -#### 7.4.3.2 Query EI job - -**Table 7.4.3.2-1: Query EI job use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC to retrieve information about an EI job | | -| Actors and Roles | Non-RT RIC as A1-EI Producer
Near-RT RIC as A1-EI Consumer | | -| Assumptions | The EI job identifier known to the Near-RT RIC corresponds to an existing EI job.
Near-RT RIC has the schema for interpreting EI job information. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-EI service.
The EI job identifier is known to the Near-RT RIC. | | -| Begins when | Near-RT RIC initiates EI job query | | -| Step 1 (M) | Near-RT RIC sends Query EI job request containing the EI job identifier | | -| Step 2 (M) | Non-RT RIC sends Query EI job response containing EI job information | | -| Ends when | Near-RT RIC has received the EI job information | | -| Exceptions | | | -| Post-conditions | EI job information is known to Near-RT RIC | | -| Traceability | REQ-A1-EI-FUN8 | | - -![Sequence diagram for Query EI job use case. It shows two lifelines: Non-RT RIC (top) and Near-RT RIC (bottom). Step 1: A solid arrow points from Non-RT RIC to Near-RT RIC with the message '1 <> Query EI job request (EI job identifier)'. Step 2: A dashed arrow points from Near-RT RIC back to Non-RT RIC with the message '2 <> Query EI job response (EI job information)'.](5478f70a6cef3e5672b2b22d28830cfb_img.jpg) - -Sequence diagram for Query EI job use case. It shows two lifelines: Non-RT RIC (top) and Near-RT RIC (bottom). Step 1: A solid arrow points from Non-RT RIC to Near-RT RIC with the message '1 <> Query EI job request (EI job identifier)'. Step 2: A dashed arrow points from Near-RT RIC back to Non-RT RIC with the message '2 <> Query EI job response (EI job information)'. - -**Figure 7.4.3.3-1: Query EI job** - -### 7.4.4 Required data - -For querying EI job identifiers, the Near-RT RIC provides optionally an EI type identifier as filter parameter. - -For querying EI job, the Near-RT RIC provides an EI job identifier. - -EI job information includes the EI job definition. - -## 7.5 Update EI job use cases - -### 7.5.1 Background and goal of the use cases - -The update EI job use cases define how Near-RT RIC can update an existing EI job. - -Near-RT RIC provides updated EI job definition information. The reason for the update can be related to state of the EI type, EI job status and previously received EI job results. - -### 7.5.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - -- a) Handles EI jobs for available EI types. -- 2) Near-RT RIC: - - b) Updates EI job in Non-RT RIC that it has created. - -### 7.5.3 Solutions - -#### 7.5.3.1 Update EI job - -**Table 7.5.3.1-1: Update EI job use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC to update an existing EI job | | -| Actors and Roles | Non-RT RIC as A1-EI Producer
Near-RT RIC as A1-EI Consumer | | -| Assumptions | The EI job identifier known to the Near-RT RIC corresponds to an existing EI job that was created by the Near-RT RIC | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-EI service.
The EI job exists. | | -| Begins when | Near-RT RIC initiates EI job update | | -| Step 1 (M) | Near-RT RIC sends Update EI job request containing the updated EI job information | | -| Step 2 (M) | Non-RT RIC sends Update EI job response | | -| Ends when | EI job has been updated | | -| Exceptions | | | -| Post-conditions | EI job exists | | -| Traceability | REQ-A1-EI-FUN6 | | - -![Sequence diagram for Update EI job. It shows two lifelines: Non-RT RIC (top) and Near-RT RIC (top). The interaction starts with the Near-RT RIC sending a message '1 <> Update EI job request (EI job identifier, EI job information)' to the Non-RT RIC. The Non-RT RIC then responds with '2 <> Update EI job response' back to the Near-RT RIC. The lifelines are also labeled at the bottom of the diagram.](8658cfab6a458b4a80ab2e384c61ff89_img.jpg) - -Sequence diagram for Update EI job. It shows two lifelines: Non-RT RIC (top) and Near-RT RIC (top). The interaction starts with the Near-RT RIC sending a message '1 <> Update EI job request (EI job identifier, EI job information)' to the Non-RT RIC. The Non-RT RIC then responds with '2 <> Update EI job response' back to the Near-RT RIC. The lifelines are also labeled at the bottom of the diagram. - -**Figure 7.5.3.3-1: Update EI job** - -### 7.5.4 Required data - -For updating an EI job, the Near-RT RIC provides the EI job identifier and updated EI job information and/or callback URI for EI job status notifications. - -## 7.6 Delete EI job use cases - -### 7.6.1 Background and goal of the use cases - -The delete EI job use cases define how Near-RT RIC can delete an EI job. - -The reason for the deletion can be related to the state of the EI type, EI job status and previously received EI job results. - -### 7.6.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - - a) Handles EI jobs for available EI types. -- 2) Near-RT RIC: - - b) Deletes EI job in Non-RT RIC that it has created. - -### 7.6.3 Solutions - -#### 7.6.3.1 Delete EI job - -**Table 7.6.3.1-1: Delete EI job use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC to delete an existing EI job | | -| Actors and Roles | Non-RT RIC as A1-EI Producer
Near-RT RIC as A1-EI Consumer | | -| Assumptions | The EI job identifier known to the Near-RT RIC corresponds to an existing EI job that was created by the Near-RT RIC | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-EI service.
The EI job exists. | | -| Begins when | Near-RT RIC initiates EI job deletion | | -| Step 1 (M) | Near-RT RIC sends Delete EI job request containing the EI job identifier | | -| Step 2 (M) | Non-RT RIC sends Delete EI job response | | -| Ends when | EI job has been deleted | | -| Exceptions | | | -| Post-conditions | EI job does not exist | | -| Traceability | REQ-A1-EI-FUN6 | | - -![Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for deleting an EI job. The diagram shows two lifelines: Non-RT RIC (top) and Near-RT RIC (bottom). Step 1: A solid arrow points from Near-RT RIC to Non-RT RIC with the message '1 <> Delete EI job request (EI job identifier)'. Step 2: A dashed arrow points from Non-RT RIC to Near-RT RIC with the message '2 <> Delete EI job response'.](b2ddf2a678bd20b1b491023eb1db6458_img.jpg) - -Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for deleting an EI job. The diagram shows two lifelines: Non-RT RIC (top) and Near-RT RIC (bottom). Step 1: A solid arrow points from Near-RT RIC to Non-RT RIC with the message '1 <> Delete EI job request (EI job identifier)'. Step 2: A dashed arrow points from Non-RT RIC to Near-RT RIC with the message '2 <> Delete EI job response'. - -**Figure 7.6.3.3-1: Delete EI job** - -### 7.6.4 Required data - -For deleting an EI job, the Near-RT RIC provides the EI job identifier. - -## 7.7 EI job status use cases - -### 7.7.1 Background and goal of the use cases - -The EI job status use cases define how Near-RT RIC can detect status, and changes in status, of an EI job. - -EI job status information is provided by the Non-RT RIC and is used by Near-RT RIC when managing EI jobs. - -### 7.7.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - - a) Handles EI job and responds to queries for EI job status. - - b) Notifies Near-RT RIC about changes in EI job status. -- 2) Near-RT RIC: - - a) Requests EI job status. - - b) Receives notifications about changes in EI job status. - -### 7.7.3 Solutions - -#### 7.7.3.1 Query EI job status - -**Table 7.7.3.1-1: Query EI job status use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC to retrieve EI job status information for an existing EI job | | -| Actors and Roles | Non-RT RIC as A1-EI Producer
Near-RT RIC as A1-EI Consumer | | -| Assumptions | The EI job identifier known to the Near-RT RIC corresponds to an existing EI job that was created by the Near-RT RIC.
Near-RT RIC has the schema for interpreting EI job status information. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-EI service.
The EI job identifier is known to the Near-RT RIC. | | -| Begins when | Near-RT RIC initiates EI job status query | | -| Step 1 (M) | Near-RT RIC sends Query EI job status request containing the EI job identifier of the EI job being queried for status | | -| Step 2 (M) | Non-RT RIC sends Query EI job status response containing EI job status information | | -| Ends when | Near-RT RIC has received the EI job status information | | -| Exceptions | | | -| Post-conditions | EI job status information is known to Near-RT RIC | | -| Traceability | REQ-A1-EI-FUN9 | | - -![Sequence diagram for Query EI job status. A Non-RT RIC sends a request to a Near-RT RIC, and the Near-RT RIC responds. The diagram shows two lifelines for Non-RT RIC and Near-RT RIC. Step 1: Non-RT RIC to Near-RT RIC: <> Query EI job status request (EI job identifier). Step 2: Near-RT RIC to Non-RT RIC: <> Query EI job status response (EI job status information).](145d00f59802048185303f15937ea65c_img.jpg) - -Sequence diagram for Query EI job status. A Non-RT RIC sends a request to a Near-RT RIC, and the Near-RT RIC responds. The diagram shows two lifelines for Non-RT RIC and Near-RT RIC. Step 1: Non-RT RIC to Near-RT RIC: <> Query EI job status request (EI job identifier). Step 2: Near-RT RIC to Non-RT RIC: <> Query EI job status response (EI job status information). - -Figure 7.7.3.1-1: Query EI job status - -#### 7.7.3.2 Notify EI job status - -Table 7.7.3.2-1: Notify EI job status use case - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC to receive EI job status information for an existing EI job | | -| Actors and Roles | Non-RT RIC as A1-EI Producer
Near-RT RIC as A1-EI Consumer | | -| Assumptions | Near-RT RIC has the schema for interpreting EI job status information. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-EI service.
A callback URI for EI job status notifications has been provided when creating and/or updating the EI job. | | -| Begins when | Event occurs in Non-RT RIC related to the status of the EI job | | -| Step 1 (M) | Non-RT RIC sends Notify EI job status request containing the EI job status information | | -| Ends when | Near-RT RIC has received the EI job status information | | -| Exceptions | | | -| Post-conditions | EI job status information is known to Near-RT RIC | | -| Traceability | REQ-A1-EI-FUN10 | | - -![Sequence diagram for Notify EI job status. A Non-RT RIC sends a request to a Near-RT RIC. The diagram shows two lifelines for Non-RT RIC and Near-RT RIC. Step 1: Non-RT RIC to Near-RT RIC: <> Notify EI job status request (EI job status information).](6be06b7dc72bb42afcb3465394667c3b_img.jpg) - -Sequence diagram for Notify EI job status. A Non-RT RIC sends a request to a Near-RT RIC. The diagram shows two lifelines for Non-RT RIC and Near-RT RIC. Step 1: Non-RT RIC to Near-RT RIC: <> Notify EI job status request (EI job status information). - -Figure 7.7.3.2-1: Notify EI job status - -### 7.7.4 Required data - -EI job status information includes the EI job status that is formulated based on, and validated against, the EI job status schema. The EI job status information includes indication if EI job is enabled or disabled. - -## 7.8 EI delivery use cases - -### 7.8.1 Background and goal of the use cases - -The EI delivery use cases define how Non-RT RIC delivers EI job results to Near-RT RIC based on an EI job. - -Depending on the EI job definition, the EI job result can be delivered in one delivery message or in repeated delivery messages. - -### 7.8.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - - a) Handles EI job and delivers EI job results. -- 2) Near-RT RIC: - - b) Receives EI job result related to an EI job it has created. - -### 7.8.3 Solutions - -#### 7.8.3.1 Deliver EI job result - -**Table 7.8.3.1-1: Deliver EI job result use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to deliver EI job result based on an EI job | | -| Actors and Roles | Non-RT RIC as A1-EI Producer
Near-RT RIC as A1-P Consumer | | -| Assumptions | There is enrichment information based on the EI job definition that is to be delivered | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-EI service.
EI job exists and is enabled. | | -| Begins when | Non-RT RIC initiates EI job result delivery | | -| Step 1 (M) | Non-RT RIC sends push request with EI job result to be delivered | | -| Step 2 (M) | Near-RT RIC validates the received information and sends push response | | -| Ends when | Near-RT RIC has received enrichment information | | -| Exceptions | | | -| Post-conditions | EI job result for the EI job has been delivered | | -| Traceability | REQ-A1-EI-FUN11 | | - -![Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for delivering an EI job result. Step 1: Non-RT RIC sends a request to Near-RT RIC. Step 2: Near-RT RIC sends a response back to Non-RT RIC.](1b2ad37940c441d410002c05ff71c7c5_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Non-RT RIC->>Near-RT RIC: 1 <> Deliver EI job result request (EI job result information) - Near-RT RIC-->>Non-RT RIC: 2 <> Deliver EI job result response - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - -``` - -Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for delivering an EI job result. Step 1: Non-RT RIC sends a request to Near-RT RIC. Step 2: Near-RT RIC sends a response back to Non-RT RIC. - -**Figure 7.8.3.1-1: Deliver EI job result** - -#### 7.8.3.2 Deliver EI job results - -Table 7.8.3.2-1: Deliver EI job results use case - -| Use case stage | Evolution / specification | <>
Related use | -|--------------------------|--------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to deliver EI job results based on an EI job | | -| Actors and Roles | Non-RT RIC as A1-EI Producer
Near-RT RIC as A1-P Consumer | | -| Assumptions | There is enrichment information based on the EI job definition that is to be delivered in more than one delivery message | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-EI service.
EI job exists and is enabled. | | -| Begins when | Non-RT RIC initiates EI job result delivery | | -| Step 1 – ref (M) | Non-RT RIC delivers EI job result | 7.8.3.1 | -| Step 2 – loop (M) | Non-RT RIC repeats Step 1 as per the EI job definition | | -| Ends when | The EI job is completed or deleted. | | -| Exceptions | | | -| Post-conditions | EI job result for the EI job has been delivered | | -| Traceability | REQ-A1-EI-FUN11 | | - -![Sequence diagram for Deliver EI job results. Lifelines: Non-RT RIC and Near-RT RIC. A loop box labeled 'loop [according to EI job definition]' contains a 'ref' box labeled 'Deliver EI job result'. The interaction starts with Non-RT RIC and ends with Near-RT RIC.](4ff00a489baaa34a0c01070de1d613db_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note right of Non-RT RIC: loop according to EI job definition - Note right of Non-RT RIC: ref Deliver EI job result - -``` - -Sequence diagram for Deliver EI job results. Lifelines: Non-RT RIC and Near-RT RIC. A loop box labeled 'loop [according to EI job definition]' contains a 'ref' box labeled 'Deliver EI job result'. The interaction starts with Non-RT RIC and ends with Near-RT RIC. - -Figure 7.8.3.2-1: Deliver EI job results - -### 7.8.4 Required data - -EI job result information contains the enrichment information requested in the EI job definition. It is formulated based on, and validated against, the EI job result schema. - -# 8 Use cases for A1 ML model management service – Near-RT RIC as A1-ML Consumer - -## 8.1 Request AI/ML model training use cases - -### 8.1.1 Background and goal of the use cases - -The Request AI/ML model training use cases define how Near-RT RIC requests SMO/Non-RT RIC to train an AI/ML Model. - -### 8.1.2 Entities/resources involved in the use cases - -- 1) SMO/Non-RT RIC: - -- a) Produces AI/ML model training services. - - b) Makes AI/ML model training services available to Near-RT RIC. -- 2) Near-RT RIC: -- b) Requests AI/ML model training from SMO/Non-RT RIC. - -### 8.1.3 Solutions - -#### 8.1.3.1 Request AI/ML model training - -**Table 8.1.3.1-1: Request AI/ML model training use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC requests training of an AI/ML model. | | -| Actors and Roles | SMO/Non-RT RIC as producer of AI/ML training services.
Non-RT RIC as A1-ML Producer.
Near-RT RIC as A1-ML Consumer. | | -| Assumptions | AI/ML training services are produced by the SMO/Non-RT RIC framework or by rApps for the AI/ML model that training is requested for.
Near-RT RIC is aware of that SMO/Non-RT RIC can train the AI/ML model. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-ML service. | | -| Begins when | Near-RT RIC determines the need to train an AI/ML model | | -| Step 1 (M) | Near-RT RIC sends Request training request | | -| Step 2 (M) | Non-RT RIC sends Request training response | | -| Step 3 (M) | SMO/Non-RT RIC trains the AI/ML model | | -| Step 4 (M) | Non-RT RIC sends Notify AI/ML model training job status message containing the AI/ML model training job status and status-dependent information | | -| Ends when | Near-RT RIC has the location of the trained AI/ML model | | -| Exceptions | | | -| Post-conditions | Trained AI/ML model is available to Near-RT RIC | | -| Traceability | REQ-A1-ML-FUN2 | | - -![Sequence diagram showing the interaction between SMO/Non-RT RIC and Near-RT RIC for AI/ML model training. The sequence is: 1. Near-RT RIC sends 'Request training request' to SMO/Non-RT RIC; 2. SMO/Non-RT RIC sends 'Request training response' to Near-RT RIC; 3. SMO/Non-RT RIC performs internal 'Train the Model'; 4. SMO/Non-RT RIC sends 'Notify AI/ML model training job status' to Near-RT RIC.](26e334e61dd059cff029338a2a604d8d_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC - participant SMO/Non-RT RIC - Note left of SMO/Non-RT RIC: 3 Train the Model - Near-RT RIC->>SMO/Non-RT RIC: 1 «A1» Request training request (Information for training, notification URI) - SMO/Non-RT RIC-->>Near-RT RIC: 2 «A1» Request training response (training job id) - SMO/Non-RT RIC->>Near-RT RIC: 4 «A1» Notify AI/ML model training job status (training job id, training job status, status-dependent information) - -``` - -Sequence diagram showing the interaction between SMO/Non-RT RIC and Near-RT RIC for AI/ML model training. The sequence is: 1. Near-RT RIC sends 'Request training request' to SMO/Non-RT RIC; 2. SMO/Non-RT RIC sends 'Request training response' to Near-RT RIC; 3. SMO/Non-RT RIC performs internal 'Train the Model'; 4. SMO/Non-RT RIC sends 'Notify AI/ML model training job status' to Near-RT RIC. - -**Figure 8.1.3.1-1: Request AI/ML model training - Near-RT RIC requests AI/ML model training** - -### 8.1.4 Required data - -Information for training (e.g. information about training dataset, model identifier, training criteria), and a notification URI to receive notification is provided by Near-RT RIC. - -SMO/Non-RT RIC provides the training job identifier and the information for training job status notification, including status-dependent information (e.g location of the trained model, or details in case of non-successful training). - -## 8.2 AI/ML model training job status use cases - -### 8.2.1 Background and goal of the use cases - -This use cases define how Near-RT RIC queries AI/ML model training job status and receives notification about AI/ML model training job status change. AI/ML model training job status is provided by the SMO/Non-RT RIC. - -### 8.2.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - - a) Responds to queries for AI/ML model training job status. - - b) Notifies Near-RT RIC about changes in AI/ML model training job status. -- 2) Near-RT RIC: - - a) Requests AI/ML model training job status. - - b) Receives notifications about changes in AI/ML model training job status. - -### 8.2.3 Solutions - -#### 8.2.3.1 Query AI/ML model training job status - -**Table 8.2.3.1-1: Query AI/ML model training job status use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC to retrieve AI/ML model training job status for an existing AI/ML model training job | | -| Actors and Roles | Non-RT RIC as A1-ML Producer
Near-RT RIC as A1-ML Consumer | | -| Assumptions | The AI/ML model training job identifier known to the Near-RT RIC corresponds to an existing AI/ML model training job that was created based on the training request from Near-RT RIC. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-ML service.
The AI/ML model training job identifier is known to the Near-RT RIC. | | -| Begins when | Near-RT RIC initiates AI/ML model training job status query | | -| Step 1 (M) | Near-RT RIC sends Query AI/ML model training job status request containing the AI/ML model training job identifier of the AI/ML model training job being queried for status | | -| Step 2 (M) | Non-RT RIC sends Query AI/ML model training job status response containing AI/ML model training job status | | -| Ends when | Near-RT RIC has received the AI/ML model training job status | | -| Exceptions | | | -| Post-conditions | AI/ML model training job status is known to Near-RT RIC | | -| Traceability | REQ-A1-ML-FUN3 | | - -![Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for querying AI/ML model training job status. The diagram shows two lifelines: Non-RT RIC (left) and Near-RT RIC (right). Step 1: A solid arrow labeled '1 «A1» Query AI/ML model training job status request (training job id)' points from the Near-RT RIC lifeline to the Non-RT RIC lifeline. Step 2: A dashed arrow labeled '2 «A1» Query AI/ML model training job status response (training job status)' points from the Non-RT RIC lifeline to the Near-RT RIC lifeline.](82fbb97c1145cac89ac72dd080fad17a_img.jpg) - -Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for querying AI/ML model training job status. The diagram shows two lifelines: Non-RT RIC (left) and Near-RT RIC (right). Step 1: A solid arrow labeled '1 «A1» Query AI/ML model training job status request (training job id)' points from the Near-RT RIC lifeline to the Non-RT RIC lifeline. Step 2: A dashed arrow labeled '2 «A1» Query AI/ML model training job status response (training job status)' points from the Non-RT RIC lifeline to the Near-RT RIC lifeline. - -**Figure 8.2.3.1-1: Query AI/ML model training job status** - -#### 8.2.3.2 Notify AI/ML model training job status - -**Table 8.2.3.2-1: Notify AI/ML model training job status use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC to receive AI/ML model training job status for an existing AI/ML model training job | | -| Actors and Roles | Non-RT RIC as A1-ML Producer
Near-RT RIC as A1-ML Consumer | | -| Assumptions | | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-ML service.
A callback URI for AI/ML model training job status notifications has been provided when creating the AI/ML model training job. | | -| Begins when | Event occurs in SMO/Non-RT RIC related to the status of the AI/ML model training job | | -| Step 1 (M) | Non-RT RIC sends Notify AI/ML model training job status message containing the AI/ML model training job status and optionally status-dependent information | | -| Ends when | Near-RT RIC has received the AI/ML model training job status | | -| Exceptions | | | -| Post-conditions | AI/ML model training job status is known to Near-RT RIC | | -| Traceability | REQ-A1-ML-FUN4 | | - -![Sequence diagram showing the notification flow from Non-RT RIC to Near-RT RIC.](9a14684f8ae1345c6efea6f5994c730c_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note left of Non-RT RIC: (Top) - Note right of Near-RT RIC: (Bottom) - Non-RT RIC->>Near-RT RIC: 1 «A1» Notify AI/ML model training job status (training job id, training job status, status-dependent information) - -``` - -Sequence diagram showing the notification flow from Non-RT RIC to Near-RT RIC. - -**Figure 8.2.3.2-1: Notify AI/ML model training job status** - -### 8.2.4 Required data - -SMO/Non-RT RIC provides the training job id, the training job status, and optionally the status-dependent information. - -## 8.3 Discover AI/ML model training capabilities use cases - -### 8.3.1 Background and goal of the use cases - -These use cases define how Near-RT RIC discovers AI/ML model training capabilities. AI/ML model training capabilities are provided by the Non-RT RIC. - -### 8.3.2 Entities/resources involved in the use cases - -- 1) SMO/Non-RT RIC: - - a) Provides information on AI/ML model training capabilities. - - b) Makes AI/ML model training capabilities available to Near-RT RIC. -- 2) Near-RT RIC: - -- a) Discovers AI/ML model training capabilities. - -### 8.3.3 Solutions - -#### 8.3.3.1 Query AI/ML model training capabilities - -**Table 8.3.3.1-1 Query AI/ML model training capabilities use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC is to discover AI/ML model training capabilities provided by Non-RT RIC. | | -| Actors and Roles | Non-RT RIC as A1-ML Producer
Near-RT RIC as A1-ML Consumer | | -| Assumptions | AI/ML model training capabilities are provided by the SMO/Non-RT RIC framework or by rApps that registered the AI/ML model training capabilities in the Non-RT RIC. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-ML service. | | -| Begins when | Near-RT RIC determines the need to discover AI/ML model training capabilities provided by Non-RT RIC | | -| Step 1 (M) | Near-RT RIC sends Query AI/ML model training capabilities request for the information on the AI/ML model training capabilities by providing selection criteria | | -| Step 2 (M) | Non-RT RIC looks up the information of the AI/ML model training capabilities | | -| Step 3 (M) | Non-RT RIC sends Query AI/ML model training capabilities response containing the information of AI/ML model training capabilities | | -| Ends when | Near-RT RIC has received the AI/ML model training capabilities | | -| Exceptions | | | -| Post-conditions | AI/ML model training capabilities are known to Near-RT RIC | | -| Traceability | REQ-A1-ML-FUN5 | | - -![Sequence diagram showing the interaction between SMO/Non-RT RIC and Near-RT RIC for querying AI/ML model training capabilities. The sequence starts with the Near-RT RIC sending a request (Step 1) to the SMO/Non-RT RIC. The SMO/Non-RT RIC then performs an internal lookup (Step 2) and finally sends a response (Step 3) back to the Near-RT RIC.](24a89bcaba787f2bc1721356480a4a01_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC - participant SMO/Non-RT RIC - Note right of Near-RT RIC: 1 «A1» Query AI/ML model training capabilities request (Selection criteria) - Near-RT RIC->>SMO/Non-RT RIC: 1 «A1» Query AI/ML model training capabilities request (Selection criteria) - Note left of SMO/Non-RT RIC: 2 Look up AI/ML model training capabilities - SMO/Non-RT RIC-->>SMO/Non-RT RIC: 2 Look up AI/ML model training capabilities - Note right of SMO/Non-RT RIC: 3 «A1» Query AI/ML model training capabilities response (AI/ML model training capabilities information) - SMO/Non-RT RIC->>Near-RT RIC: 3 «A1» Query AI/ML model training capabilities response (AI/ML model training capabilities information) - -``` - -Sequence diagram showing the interaction between SMO/Non-RT RIC and Near-RT RIC for querying AI/ML model training capabilities. The sequence starts with the Near-RT RIC sending a request (Step 1) to the SMO/Non-RT RIC. The SMO/Non-RT RIC then performs an internal lookup (Step 2) and finally sends a response (Step 3) back to the Near-RT RIC. - -**Figure 8.3.3.1-1 Query AI/ML model training capabilities** - -### 8.3.4 Required data - -The selection criteria include AI/ML model training environment requirement for query of AI/ML model training capabilities is provided by Near-RT RIC. - -SMO/Non-RT RIC provides the AI/ML model training capabilities. - -## 8.4 Cancel AI/ML model training use cases - -### 8.4.1 Background and goal of the use cases - -The Cancel AI/ML model training use cases define how Near-RT RIC requests SMO/Non-RT RIC to cancel the training of an AI/ML Model. - -### 8.4.2 Entities/resources involved in the use cases - -- 1) SMO/Non-RT RIC: - - a) Produces AI/ML model training services. - - b) Makes AI/ML model training services available to Near-RT RIC. -- 2) Near-RT RIC: - - a) Requests to cancel AI/ML model training from SMO/Non-RT RIC. - -### 8.4.3 Solutions - -#### 8.4.3.1 Cancel AI/ML model training - -**Table 8.4.3.1-1: Cancel AI/ML model training use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Near-RT RIC cancels training of an AI/ML model. | | -| Actors and Roles | SMO/Non-RT RIC as producer of AI/ML training services.
Non-RT RIC as A1-ML Producer.
Near-RT RIC as A1-ML Consumer. | | -| Assumptions | AI/ML training services are produced by the SMO/Non-RT RIC framework or by rApps for the AI/ML model that training is requested for.
Near-RT RIC is aware of that SMO/Non-RT RIC can train the AI/ML model. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-ML service. | | -| Begins when | Near-RT RIC determines the need to cancel the training an AI/ML model | | -| Step 1 (M) | Near-RT RIC sends Cancel training request containing the training job identifier | | -| Step 2 (M) | Non-RT RIC sends Cancel training response | | -| Ends when | The training has been cancelled | | -| Exceptions | | | -| Post-conditions | AI/ML model is not trained | | -| Traceability | REQ-A1-ML-FUN6 | | - -![Sequence diagram showing the cancellation of AI/ML model training. A Near-RT RIC sends a 'Cancel training request' (training job id) to an SMO/Non-RT RIC, which responds with a 'Cancel training response'.](e22af684d8e56d4c61e61bb5ddac1087_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC - participant SMO/Non-RT RIC - Note left of Near-RT RIC: Near-RT RIC - Near-RT RIC->>SMO/Non-RT RIC: 1 «A1» Cancel training request (training job id) - SMO/Non-RT RIC-->>Near-RT RIC: 2 «A1» Cancel training response - Note right of SMO/Non-RT RIC: SMO/Non-RT RIC - -``` - -Sequence diagram showing the cancellation of AI/ML model training. A Near-RT RIC sends a 'Cancel training request' (training job id) to an SMO/Non-RT RIC, which responds with a 'Cancel training response'. - -Figure 8.4.3.1-1: Cancel AI/ML model training - Near-RT RIC requests to cancel AI/ML model training - -### 8.4.4 Required data - -Training job identifier is provided by Near-RT RIC. - -# 9 Use cases for A1 ML model management service – Non-RT RIC as A1-ML Consumer - -## 9.1 Request AI/ML model training use cases - -### 9.1.1 Background and goal of the use cases - -The Request AI/ML model training use cases define how Non-RT RIC requests Near-RT RIC to train an AI/ML Model. - -### 9.1.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - - a) Requests AI/ML model training from Non-RT RIC. -- 2) Near-RT RIC: - - a) Produce AI/ML model training services. - - b) Makes AI/ML model training services available to Non-RT RIC. - -### 9.1.3 Solutions - -#### 9.1.3.1 Request AI/ML model training - -**Table 9.1.3.1-1: Request AI/ML model training use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC requests training of an AI/ML model. | | -| Actors and Roles | Near-RT RIC as producer of AI/ML training services and A1-ML Producer.
Non-RT RIC as A1-ML Consumer. | | -| Assumptions | Non-RT RIC is aware of that Near-RT RIC can train the AI/ML model. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-ML service. | | -| Begins when | Non-RT RIC determines the need to train an AI/ML model | | -| Step 1 (M) | Non-RT RIC sends Request training request | | -| Step 2 (M) | Near-RT RIC sends Request training response | | -| Step 3 (M) | Near-RT RIC trains the AI/ML model | | -| Step 4 (M) | Near-RT RIC sends Notify AI/ML model training job status message containing the AI/ML model training job status and status-dependent information | | -| Ends when | Non-RT RIC has the location of the trained AI/ML model | | -| Exceptions | | | -| Post-conditions | Trained AI/ML model is available to Non-RT RIC | | -| Traceability | REQ-A1-ML-FUN2 | | - -![Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for AI/ML model training. The steps are: 1. Non-RT RIC sends a Request training request to Near-RT RIC. 2. Near-RT RIC sends a Request training response back to Non-RT RIC. 3. Near-RT RIC performs the training internally. 4. Near-RT RIC sends a Notify AI/ML model training job status message to Non-RT RIC.](683f755e8456c884716de4fce48c7e63_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note left of Non-RT RIC: 1 «A1» Request training request -(Information for training, notification URI) - Non-RT RIC->>Near-RT RIC: 1 - Note right of Near-RT RIC: 2 «A1» Request training response -(training job id) - Near-RT RIC-->>Non-RT RIC: 2 - Note right of Near-RT RIC: 3 Train the Model - Near-RT RIC-->>Near-RT RIC: 3 - Note right of Near-RT RIC: 4 «A1» Notify AI/ML model training job status -(training job id, training job status, status-dependent information) - Near-RT RIC-->>Non-RT RIC: 4 - -``` - -Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for AI/ML model training. The steps are: 1. Non-RT RIC sends a Request training request to Near-RT RIC. 2. Near-RT RIC sends a Request training response back to Non-RT RIC. 3. Near-RT RIC performs the training internally. 4. Near-RT RIC sends a Notify AI/ML model training job status message to Non-RT RIC. - -**Figure 9.1.3.1-1: AI/ML model training - Non-RT RIC requests AI/ML model training** - -### 9.1.4 Required data - -Information for training (e.g. information about training dataset, model identifier, training criteria), and a notification URI to receive notification is provided by Non-RT RIC. - -Near-RT RIC provides the training job identifier and the information for training job status notification, including status-dependent information (e.g location of the trained model, or details in case of non-successful training). - -## 9.2 AI/ML model training job status use cases - -### 9.2.1 Background and goal of the use cases - -These use cases define how Non-RT RIC queries AI/ML model training job status and receives notification about AI/ML model training job status change. AI/ML model training job status is provided by the Near-RT RIC. - -### 9.2.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - - a) Requests AI/ML model training job status. - - b) Receives notifications about changes in AI/ML model training job status. -- 2) Near-RT RIC: - - a) Responds to queries for AI/ML model training job status. - - b) Notifies Non-RT RIC about changes in AI/ML model training job status. - -### 9.2.3 Solutions - -#### 9.2.3.1 Query AI/ML model training job status - -**Table 9.2.3.1-1: Query AI/ML model training job status use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to retrieve AI/ML model training job status for an existing AI/ML model training job | | -| Actors and Roles | Near-RT RIC as A1-ML Producer
Non-RT RIC as A1-ML Consumer | | -| Assumptions | The AI/ML model training job identifier known to the Non-RT RIC corresponds to an existing AI/ML model training job that was created based on the training request from Non-RT RIC. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-ML service.
The AI/ML model training job identifier is known to the Non-RT RIC. | | -| Begins when | Non-RT RIC initiates AI/ML model training job status query | | -| Step 1 (M) | Non-RT RIC sends Query AI/ML model training job status request containing the AI/ML model training job identifier of the AI/ML model training job being queried for status | | -| Step 2 (M) | Near-RT RIC sends Query AI/ML model training job status response containing AI/ML model training job status | | -| Ends when | Non-RT RIC has received the AI/ML model training job status | | -| Exceptions | | | -| Post-conditions | AI/ML model training job status is known to Non-RT RIC | | -| Traceability | REQ-A1-ML-FUN3 | | - -![Sequence diagram for Figure 9.2.3.1-1: Query AI/ML model training job status. It shows a Non-RT RIC sending an A1 message to a Near-RT RIC, and the Near-RT RIC responding with another A1 message.](01e00200a536673d6cd0e6d8705047a0_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Note right of Near-RT RIC: - Non-RT RIC->>Near-RT RIC: «A1» Query AI/ML model training job status request (training job id) - Near-RT RIC-->>Non-RT RIC: «A1» Query AI/ML model training job status response (training job status) - -``` - -Sequence diagram for Figure 9.2.3.1-1: Query AI/ML model training job status. It shows a Non-RT RIC sending an A1 message to a Near-RT RIC, and the Near-RT RIC responding with another A1 message. - -Figure 9.2.3.1-1: Query AI/ML model training job status - -#### 9.2.3.2 Notify AI/ML model training job status - -Table 9.2.3.2-1: Notify AI/ML model training job status use case - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC to receive AI/ML model training job status for an existing AI/ML model training job | | -| Actors and Roles | Near-RT RIC as A1-ML Producer
Non-RT RIC as A1-ML Consumer | | -| Assumptions | | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-ML service.
A callback URI for AI/ML model training job status notifications has been provided when creating the AI/ML model training job. | | -| Begins when | Event occurs in Near-RT RIC related to the status of the AI/ML model training job | | -| Step 1 (M) | Near-RT RIC sends Notify AI/ML model training job status message containing the AI/ML model training job status and optionally status-dependent information | | -| Ends when | Non-RT RIC has received the AI/ML model training job status | | -| Exceptions | | | -| Post-conditions | AI/ML model training job status is known to Non-RT RIC | | -| Traceability | REQ-A1-ML-FUN4 | | - -![Sequence diagram for Figure 9.2.3.2-1: Notify AI/ML model training job status. It shows a Near-RT RIC sending an A1 message to a Non-RT RIC.](a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Near-RT RIC->>Non-RT RIC: «A1» Notify AI/ML model training job status (training job id, training job status, status-dependent information) - -``` - -Sequence diagram for Figure 9.2.3.2-1: Notify AI/ML model training job status. It shows a Near-RT RIC sending an A1 message to a Non-RT RIC. - -Figure 9.2.3.2-1: Notify AI/ML model training job status - -### 9.2.4 Required data - -Near-RT RIC provides the training job id, the training job status, and optionally the status-dependent information (e.g location of the trained model, or details in case of non-successful training). - -## 9.3 Discover AI/ML model training capabilities use cases - -### 9.3.1 Background and goal of the use cases - -These use cases define how Non-RT RIC discovers AI/ML model training capabilities. AI/ML model training capabilities are provided by the Near-RT RIC. - -### 9.3.2 Entities/resources involved in the use cases - -- 1) Non-RT RIC: - - a) Discovers AI/ML model training capabilities. -- 2) Near-RT RIC: - - a) Provides information on AI/ML model training capabilities. - - b) Makes AI/ML model training capabilities available to Non-RT RIC. - -### 9.3.3 Solutions - -#### 9.3.3.1 Query AI/ML model training capabilities - -**Table 9.3.3.1-1 Query AI/ML model training capabilities use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC is to discover AI/ML model training capabilities provided by Near-RT RIC. | | -| Actors and Roles | Near-RT RIC as A1-ML Producer
Non-RT RIC as A1-ML Consumer | | -| Assumptions | Non-RT RIC is aware of that Near-RT RIC can train an AI/ML model and can provide the information on AI/ML model training capabilities. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-ML service. | | -| Begins when | Non-RT RIC determines the need to discover AI/ML model training capabilities provided by Near-RT RIC | | -| Step 1 (M) | Non-RT RIC sends Query AI/ML model training capabilities request for the information on the AI/ML model training capabilities by providing selection criteria | | -| Step 2 (M) | Near-RT RIC looks up the information of the AI/ML model training capabilities | | -| Step 3 (M) | Near-RT RIC sends Query AI/ML model training capabilities response containing the information of AI/ML model training capabilities | | -| Ends when | Non-RT RIC has received the AI/ML model training capabilities | | -| Exceptions | | | -| Post-conditions | AI/ML model training capabilities are known to Non-RT RIC | | -| Traceability | REQ-A1-ML-FUN5 | | - -![Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for querying AI/ML model training capabilities. The sequence is: 1. Non-RT RIC sends a request to Near-RT RIC. 2. Near-RT RIC performs a self-call to look up capabilities. 3. Near-RT RIC sends a response back to Non-RT RIC.](fe25bbee6685ab20f50ffc80c3feddd8_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note left of Non-RT RIC: 1 «A1» Query AI/ML model training capabilities request (Selection criteria) - Non-RT RIC->>Near-RT RIC: Request - Note right of Near-RT RIC: 2 Look up AI/ML model training capabilities - Near-RT RIC-->>Non-RT RIC: Response - Note left of Non-RT RIC: 3 «A1» Query AI/ML model training capabilities response (AI/ML model training capabilities information) - -``` - -Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for querying AI/ML model training capabilities. The sequence is: 1. Non-RT RIC sends a request to Near-RT RIC. 2. Near-RT RIC performs a self-call to look up capabilities. 3. Near-RT RIC sends a response back to Non-RT RIC. - -**Figure 9.3.3.1-1 Query AI/ML model training capabilities** - -### 9.3.4 Required data - -The selection criteria include AI/ML model training environment requirement for query of AI/ML model training capabilities is provided by Non-RT RIC. - -Near-RT RIC provides the AI/ML model training capabilities. - -## 9.4 Cancel AI/ML model training use cases - -### 9.4.1 Background and goal of the use cases - -The Cancel AI/ML model training use cases define how Non-RT RIC requests Near-RT RIC to cancel the training of an AI/ML Model. - -### 9.4.2 Entities/resources involved in the use cases - -- 1) SMO/Non-RT RIC: - - a) Request to cancel AI/ML model training from SMO/Non-RT RIC. -- 2) Near-RT RIC: - - a) Produces AI/ML model training services. - - b) Makes AI/ML model training services available to Near-RT RIC. - -### 9.4.3 Solutions - -#### 9.4.3.1 Cancel AI/ML model training - -**Table 9.4.3.1-1: Cancel AI/ML model training use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Non-RT RIC cancels training of an AI/ML model. | | -| Actors and Roles | Near-RT RIC as producer of AI/ML training services.
Near-RT RIC as A1-ML Producer.
Non-RT RIC as A1-ML Consumer. | | -| Assumptions | AI/ML training services are produced by the Near-RT RIC framework for the AI/ML model that training is requested for.
Non-RT RIC is aware of that SMO/Non-RT RIC can train the AI/ML model. | | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the A1-ML service. | | -| Begins when | Non-RT RIC determines the need to cancel the training of an AI/ML model | | -| Step 1 (M) | Non-RT RIC sends Cancel training request containing the training job identifier | | -| Step 2 (M) | Near-RT RIC sends Cancel training response | | -| Ends when | The training has been cancelled | | -| Exceptions | | | -| Post-conditions | AI/ML model is not trained | | -| Traceability | REQ-A1-ML-FUN6 | | - -![Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for cancelling AI/ML model training. Step 1: Non-RT RIC sends a 'Cancel training request (training job id)' to Near-RT RIC. Step 2: Near-RT RIC sends a 'Cancel training response' back to Non-RT RIC.](3493d7ba4c86f944e159de1bf45ff03d_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC: Near-RT RIC - Non-RT RIC->>Near-RT RIC: 1 «A1» Cancel training request (training job id) - Near-RT RIC-->>Non-RT RIC: 2 «A1» Cancel training response - -``` - -Sequence diagram showing the interaction between Non-RT RIC and Near-RT RIC for cancelling AI/ML model training. Step 1: Non-RT RIC sends a 'Cancel training request (training job id)' to Near-RT RIC. Step 2: Near-RT RIC sends a 'Cancel training response' back to Non-RT RIC. - -**Figure 9.4.3.1-1: Cancel AI/ML model training - Non-RT RIC requests to cancel AI/ML model training** - -### 9.4.4 Required data - -Training job identifier is provided by Non-RT RIC. - -# --- Annex A (normative): Authorization of service access requests - -## A.1 Pre-conditions - -The preconditions of the A1 use cases in clauses 6 to 8 are that the actors are authorized for using the A1 service and the authorization procedures are defined in SPS [9], clause 4.7. The registration process for the entity acting as service producer is described in SPS [9], clause 4.7.2.2, and the access token request process for the entity acting as service consumer is described in SPS [9], clause 4.7.2.3. - -## --- A.2 A1 service access based on token verification use cases - -### A.2.1 Background and goal of the use cases - -The service access request based on token verification is described generically in SPS [9], clause 4.7.2.4. - -The A1 service access use cases define how the access token is transferred and verified. This description applies to all solutions specified in clauses 6 to 8 although they do not explicitly refer to token transfer or verification. - -### A.2.2 Entities/resources involved in the use cases - -- 1) SMO/Non-RT RIC framework: - - a) either makes service access requests containing access token; or - - b) verifies received access token before sending service access responses. -- 2) Near-RT RIC: - - a) either verifies received access token before sending service access responses; or - - b) makes service access requests containing access token. - -### A.2.3 Solutions - -#### A.2.3.1 General - -The notation A1 Consumer refers to either A1-P Consumer, A1-EI Consumer, or A1-ML Consumer while the notation A1 Producer refers to either A1-P Producer, A1-EI Producer, or A1-ML Producer. SMO/Non-RT RIC framework acts as A1 Consumer for A1-P and/or A1-ML when Near-RT RIC acts as A1 Producer for A1-P and/or A1-ML, and SMO/Non-RT RIC framework acts as A1 Producer for A1-EI and/or A1-ML when Near-RT RIC acts as A1 Consumer for A1-EI and/or A1-ML. - -The notation “service access” for the use case, the procedure, and the request/response messages in this clause refers to the use case, procedure and request/response message names used in the solutions in clauses 6 to 8. - -#### A.2.3.2 Service access request - -**Table A.2.3.2-1: Service access use case** - -| Use case stage | Evolution / specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | A1 Producer to verify access token in service access request received from A1 Consumer | SPS [9], clause 4.7.2.4 | -| Actors and Roles | SMO/Non-RT RIC framework as A1 Consumer and Near-RT RIC as A1 Producer
or
SMO/Non-RT RIC framework as A1 Producer and Near-RT RIC as A1 Consumer | | -| Assumptions | See solutions for A1-P, A1-EI, and A1-ML use cases | Clauses 6 to 8 | -| Pre-conditions | A1 interface is established, and the actors are authorized for using the requested A1 service. | SPS [9], clause 4.7 | -| Begins when | A1 Consumer initiates service access | | -| Step 1 (M) | A1 Consumer sends A1 service access request message containing access token | Clauses 6 to 8 | -| Step 2 (M) | A1 Producer verifies the access token. | | -| Step 3 (M) | A1 Producer sends A1 service access response message. | Clauses 6 to 8 | -| Ends when | Service access request has been verified. | | -| Exceptions | If token verification was not successful, further details may be provided that may indicate what is needed to access the service. | | -| Post-conditions | If verification was successful, the service has been executed. | | -| Traceability | REQ-A1-P-FUN11, REQ-A1-EI-FUN12, REQ-A1-ML-FUN1 | | - -![Sequence diagram for Service access. Lifelines: A1 Consumer and A1 Producer. Step 1: A1 Consumer sends '1 «A1» service access request (access token)' to A1 Producer. Step 2: A1 Producer performs '2 verify the access token'. Step 3: A1 Producer sends '3 «A1» service access response' back to A1 Consumer.](195611c20b2dc7ed0fa3033392e22908_img.jpg) - -``` - -sequenceDiagram - participant A1 Consumer - participant A1 Producer - Note right of A1 Producer: 2 verify the access token - A1 Consumer->>A1 Producer: 1 «A1» service access request (access token) - A1 Producer-->>A1 Consumer: 3 «A1» service access response - -``` - -Sequence diagram for Service access. Lifelines: A1 Consumer and A1 Producer. Step 1: A1 Consumer sends '1 «A1» service access request (access token)' to A1 Producer. Step 2: A1 Producer performs '2 verify the access token'. Step 3: A1 Producer sends '3 «A1» service access response' back to A1 Consumer. - -**Figure A.2.3.2-1: Service access** - -### A.2.4 Required data - -In addition to the data required in the solutions in clauses 6 to 8, the access token is included in the service access request message. - -In case service access is rejected due to that access is forbidden, the service access response message may include information on the token scope necessary to access the service. - -# --- Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|---------------------------------------------------------------------------------| -| 2022.07.30 | 01.00 | First version | -| 2022.11.17 | 01.01 | Aligning to O-RAN drafting rules | -| 2023.11.30 | 01.02 | Editorial enhancement and applying latest template | -| 2024.03.31 | 01.03 | Editorial enhancements and alignment of notation for status and feedback. | -| 2024.07.31 | 01.04 | Updated specification designator to R004 | -| 2024.11.30 | 02.00 | Use cases for Authorization of service access requests and AI/ML model training | -| 2025.03.31 | 03.00 | Use case for AI/ML model training job status with Non-RT RIC as A1-ML Consumer | -| 2025.07.31 | 04.00 | Use case for AI/ML model training capabilities discovery | -| 2025.11.30 | 05.00 | Use case for AI/ML model training cancellation | \ No newline at end of file diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/01e00200a536673d6cd0e6d8705047a0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/01e00200a536673d6cd0e6d8705047a0_img.jpg deleted file mode 100644 index 35156335f27fb18c8a6ae66ba45ab7b8bb88bb4f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/01e00200a536673d6cd0e6d8705047a0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6e8cd6973d4d4034fd3ac6e331842b9aa00ba27678c64b5efdf581069a4dbd5 -size 34214 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/12de9b926df0384ec07702671827c9cd_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/12de9b926df0384ec07702671827c9cd_img.jpg deleted file mode 100644 index 7ed15c20e2c923f55fd79d9810a45a7649f88979..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/12de9b926df0384ec07702671827c9cd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0ef963247f9d0ed2e1cfab0eaf8c98f087b2c8db21af9593d264f27ed03b0c9f -size 23040 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/145d00f59802048185303f15937ea65c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/145d00f59802048185303f15937ea65c_img.jpg deleted file mode 100644 index a3c65c40c8d0a552e9f67ef6bfa0a8e428e9930e..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/145d00f59802048185303f15937ea65c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5ede2876fb50f33cbc807a4d218b3525f9c609630e79a5f89e242df1c48f9f93 -size 27016 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/16152cf1d84aea10848758f51a91ff6a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/16152cf1d84aea10848758f51a91ff6a_img.jpg deleted file mode 100644 index 777fd1fdab928c7c26ca660e5e45b1b291648038..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/16152cf1d84aea10848758f51a91ff6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fad70cff10b7666c1462b6707670f4b7f84cc4ef8c2dbabb4a66963b630c7ae6 -size 29707 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg deleted file mode 100644 index 06f7632d52bdca40f97a02376673a0d96a34febf..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:26c0252f6bc3142d043389abd540e6de52dc5dfa5bef3d714c068f0cb2bdbf3a -size 27749 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/195611c20b2dc7ed0fa3033392e22908_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/195611c20b2dc7ed0fa3033392e22908_img.jpg deleted file mode 100644 index 606930e47fb539b2b1ef59e3c4e2634c6d5e52f9..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/195611c20b2dc7ed0fa3033392e22908_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:23499d3f6ced2562ead3abf19f98a998a0742a10d997c9ddffdc28af84ba3385 -size 27988 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/19a59d6b53059ebd27b13c98793f88e0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/19a59d6b53059ebd27b13c98793f88e0_img.jpg deleted file mode 100644 index 4c30f81ddf897865405e11592a988090af0ad30b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/19a59d6b53059ebd27b13c98793f88e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:09818d975850f386fc4c60be2348dd0db961c61578ead2a6f33a36188745fa88 -size 24978 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/1b2ad37940c441d410002c05ff71c7c5_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/1b2ad37940c441d410002c05ff71c7c5_img.jpg deleted file mode 100644 index c9fc40d50db7e2e5b632e58d86996c7b7742515e..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/1b2ad37940c441d410002c05ff71c7c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:577366a6653c7e954727127775da596f00f6fbc1ba0a4a658e81a0d20dba8609 -size 23893 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/24a89bcaba787f2bc1721356480a4a01_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/24a89bcaba787f2bc1721356480a4a01_img.jpg deleted file mode 100644 index 62d5d0121377d7dc1c43bf474493b6e9dd4b2d7c..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/24a89bcaba787f2bc1721356480a4a01_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ce0a2761c305eef5c28e977e1a585741f593042e33e1683808e6212bea61a9a7 -size 42356 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/253600420ae7bd7d0119563b895cbf8a_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/26e334e61dd059cff029338a2a604d8d_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/26e334e61dd059cff029338a2a604d8d_img.jpg deleted file mode 100644 index 963178dc68386333c57b4e5ae7683bc326b8cfa6..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/26e334e61dd059cff029338a2a604d8d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:70e68d177989b312126f18416b163da0273cb1e184fd049b4c5f0f89104801ff -size 50597 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg deleted file mode 100644 index 00510310974e83324cd54ea7fd71362bfa0c77e8..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2396ee570888f119e953f59b860eacc3b2988a92e171900841efc77fdfef74cc -size 18607 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/3493d7ba4c86f944e159de1bf45ff03d_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/3493d7ba4c86f944e159de1bf45ff03d_img.jpg deleted file mode 100644 index 5ec7180400e5b41706ffa19a9d375f808f9d83bd..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/3493d7ba4c86f944e159de1bf45ff03d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d0d3c1e79b749bc7fecea8c456a7ce63759457a27dbac485d0263831e36ec0d6 -size 19546 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/356eb99ab9489bbd647223390a913903_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/356eb99ab9489bbd647223390a913903_img.jpg deleted file mode 100644 index ed131a2bba0e1ab8ee9b24284fe281aa4b7f3abb..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/356eb99ab9489bbd647223390a913903_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bd67b21de6500fc6e7ba83d39f53d9d1c49aebea902eac96f0ca39c9053ed4f9 -size 25661 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/36fb8f844f936e7a1de4838da774f2f9_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/3da1a07cb87051bf616c9876db958cf0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/3da1a07cb87051bf616c9876db958cf0_img.jpg deleted file mode 100644 index f99e1a1f1d6086c964e5f597d5f1349afe9b3305..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/3da1a07cb87051bf616c9876db958cf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6af52b7b3439986080c202a98d8c13c0777fee87a623445edf6ae95c1c79e06c -size 24059 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/410562339ce067fdc6fa41940c118658_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/410562339ce067fdc6fa41940c118658_img.jpg deleted file mode 100644 index cc5e4a583a028f97c0371285f1e1d3e822360027..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/410562339ce067fdc6fa41940c118658_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:dc76654dc38aef2ac8ab8bb0c7525b91f1da1d6ba12530daeed7cbf50dedda2a -size 20527 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/474a819357587e34949a3e110ff19b30_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/474a819357587e34949a3e110ff19b30_img.jpg deleted file mode 100644 index c5031a6c600207c68681134c2c3a0229c8b9fefa..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/474a819357587e34949a3e110ff19b30_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0360f698ace8fb98f47341e993fc2774bc219e8694ba2f42de1a9ddfc17eb510 -size 27495 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/4ff00a489baaa34a0c01070de1d613db_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/4ff00a489baaa34a0c01070de1d613db_img.jpg deleted file mode 100644 index a413ace9821e49632ee20e6408c9600680daed19..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/4ff00a489baaa34a0c01070de1d613db_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6371eadd933d80f1775023df8c4d4a9ae50ba1899d582a24a7b371b0583abbd8 -size 21618 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/5478f70a6cef3e5672b2b22d28830cfb_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/5478f70a6cef3e5672b2b22d28830cfb_img.jpg deleted file mode 100644 index 3b47d9963a2aa4d6d949fd2eb2880b9bb3deb433..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/5478f70a6cef3e5672b2b22d28830cfb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4d1e33ee8010c1d7d6e2e2dbad4dce583ca5095e9fd812f02cb87bcdf19d414e -size 22673 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/683f755e8456c884716de4fce48c7e63_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/683f755e8456c884716de4fce48c7e63_img.jpg deleted file mode 100644 index 729459dce6fb5ad704ead0cf7182529f7457e93f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/683f755e8456c884716de4fce48c7e63_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7a098a413244ee8e9bf489f868c9f7ebb40576359c7d58de641bb1559a008610 -size 46869 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/6be06b7dc72bb42afcb3465394667c3b_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/6be06b7dc72bb42afcb3465394667c3b_img.jpg deleted file mode 100644 index 4b080c5c7cc645421a9b162f2cabe07eea441ab4..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/6be06b7dc72bb42afcb3465394667c3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d3b1bddf211f43ea473136cb1269f4618e42252884777bce774204c7b8a5fec0 -size 17449 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/73dff6b45b2b9ffd384bab3235f869af_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/73dff6b45b2b9ffd384bab3235f869af_img.jpg deleted file mode 100644 index 4d385d717e1b1e88ed0761cd3c05ad47366f9585..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/73dff6b45b2b9ffd384bab3235f869af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2416c7debe321256da3821a9996723b02353ee68a79fee16cbc6c0aa5421a5d9 -size 24158 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg deleted file mode 100644 index 8e90c6a38dde2e521d92ab054c5b995b4d853d0b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/7e1c9b51e067a48cd0fcc9748d8bd8d8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:66aea40ef96ca375e2e66682bb03bab93c88b8625d66624a40fd4756583e3373 -size 18114 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/7f17c430b9598e4d748a8041457810b3_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/7f17c430b9598e4d748a8041457810b3_img.jpg deleted file mode 100644 index 88f034ad98648cb6ee68b81be9f5755e072df2f2..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/7f17c430b9598e4d748a8041457810b3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4a7af595dcb652ba82ae32a3eeed52294e4e2ecc231ed65a25315dce8910b359 -size 24269 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/82fbb97c1145cac89ac72dd080fad17a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/82fbb97c1145cac89ac72dd080fad17a_img.jpg deleted file mode 100644 index ab064d805d1774d0b5bb909c09577a7ccb29b99d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/82fbb97c1145cac89ac72dd080fad17a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe201bba6eb1102a6893c5e9f82ba74eebdc2a3cbfdafc680aaf47561748ecda -size 30933 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg deleted file mode 100644 index b1edd5661cee47dfd65aa717287c09a61016569c..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/8592a32c2fdf17c1e562f0ba6b7e8e1a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:88e29c8e70e10c608dea72b0e26d179f7b51fd34cc2dae256040dd6392f2bae7 -size 26026 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/8658cfab6a458b4a80ab2e384c61ff89_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/8658cfab6a458b4a80ab2e384c61ff89_img.jpg deleted file mode 100644 index dec067f36e39ddf4332a685cf37f221693e64aed..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/8658cfab6a458b4a80ab2e384c61ff89_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3a3867540ad15f48529c06dc76ecdda3cee014f22357abe006337740d182f111 -size 25277 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/8e14350b4b669119a3bdfca7869110ca_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/8e14350b4b669119a3bdfca7869110ca_img.jpg deleted file mode 100644 index ca649b29e09f34a05bf07f8670fe1c0e60dda511..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/8e14350b4b669119a3bdfca7869110ca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3b8e2efe0e80ce93437c881f499291c40fe28bd0242ed888c2b0df22863ce4ac -size 26505 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/9156549264d36ead617a1dec7987f970_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/94fd137860c16c8dfd75512f10161fe8_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/94fd137860c16c8dfd75512f10161fe8_img.jpg deleted file mode 100644 index 71c99a410eea4c3c663ab03bb2cd6268b2d6249f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/94fd137860c16c8dfd75512f10161fe8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2f329c74d655fd648df911e49cf3fd1207ba611d722ba2e69bc5c925abb8b54e -size 23487 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg deleted file mode 100644 index 794e3b30a12fced2a7da1fe04accbe7352cbff26..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/98e54d5540b2efe3e24af3cf936bc4ea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:918c6a5086ab77003e13b93adbb0d2db2f626098eb6d92c477a504f30d0d8873 -size 24123 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/9a14684f8ae1345c6efea6f5994c730c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/9a14684f8ae1345c6efea6f5994c730c_img.jpg deleted file mode 100644 index a8078bbcc8de9d7a9e4d6f5e4eb4048c8e58088b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/9a14684f8ae1345c6efea6f5994c730c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d3253144d5818272d8878195188977b52ceef1a6a7b2adac2c95a7e4a2e213cb -size 23497 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg deleted file mode 100644 index e87bcab2d61d2778cb6ae812607826b3e5e51e47..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a1764517bf145bc71aadff99ed3d3c7e98ffaac3f6a224c9459578a88198997a -size 25112 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/a76a30cf23764f0b907220e7c3c70ce1_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/b2ddf2a678bd20b1b491023eb1db6458_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/b2ddf2a678bd20b1b491023eb1db6458_img.jpg deleted file mode 100644 index 8065896c8a167c1c8386aaebcaba481bd505659c..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/b2ddf2a678bd20b1b491023eb1db6458_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ed21d545f9db64fcfffa390bbb119f364933de03d0264d3d326026a9876b6646 -size 20987 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/b2ea162a0f53d5e0504b7d28346e0754_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/b2ea162a0f53d5e0504b7d28346e0754_img.jpg deleted file mode 100644 index 3c58b3c704ea82b6dfb975da9e713085f4c2eced..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/b2ea162a0f53d5e0504b7d28346e0754_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f16b8ceeeb3f39102c78e3586ad65822e1b175dbeae7ae009eb462723b6ce2d -size 22493 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/ba9d6e1a75eb6672d04e61a86e1b8a61_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/ba9d6e1a75eb6672d04e61a86e1b8a61_img.jpg deleted file mode 100644 index f43a21a31f4ab47b0daa55527675970aea16ebc0..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/ba9d6e1a75eb6672d04e61a86e1b8a61_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9bd4d8e2bfb6ecd4f10d58730359a0f570da11524b3b5d1ed399119195f28774 -size 19414 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/d0abac95583b52a3b35f74a215567334_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/d0abac95583b52a3b35f74a215567334_img.jpg deleted file mode 100644 index 3ebe0fe2a1c088097adf902b9d2ec57d0072f5aa..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/d0abac95583b52a3b35f74a215567334_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e85b14f734f5f0143eec943eedf5bb3aba38e1f2572b001f5a9be009245ee9ca -size 27803 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/dd380ccd5aca1151074fede04826f1a4_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/dd380ccd5aca1151074fede04826f1a4_img.jpg deleted file mode 100644 index fdb52efdad10ef4613ec466d7f6879da56a4bdc6..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/dd380ccd5aca1151074fede04826f1a4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7340cbe036decfcf86d12183c09c51033ab12632439fa3c590d64554b998a03e -size 24400 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg deleted file mode 100644 index f059949e9b9e2c7674b29470fd193435e91ce93b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8aa110b8de53f567c7e5a1f8fbded3f2fd4f3c8b58e246edcf1415c3cd9499c8 -size 21665 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg deleted file mode 100644 index 4f7dd37a002ffbdf18ebc4cb454c1496f9bc4674..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:946d5f0d6ac666137e395f5b9f6892e58db3afd49beb8495a20eb8014ee1a526 -size 28623 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg deleted file mode 100644 index 9b5bad10669e25638e4084563170332ea22188e7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:281c1a4c0ad6cadc7c4dce42470fba45c4f8d4f2037da076ca295fb8932044e9 -size 27395 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg deleted file mode 100644 index 9dce5469327952ec0793ab2d35e7d3c1350d2380..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f1c5f8180632d584f6992cc5db6d41cf8a3763257a050f4e7dfe87512dfbde1 -size 16701 diff --git a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.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/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg b/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg deleted file mode 100644 index 8447d1fad1f925ae2da9d342a5d740beed723db6..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.A1UCR-R005-v05.00/images/fe25bbee6685ab20f50ffc80c3feddd8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9cac530345b4711ce423484cb8ebbf1854517773330f3f0566dd50dfebce90df -size 41208 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/doc.md b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/doc.md deleted file mode 100644 index 317b6343693bdec9dc0d2f325ef917094799caa7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/doc.md +++ /dev/null @@ -1,11207 +0,0 @@ - - -# --- **R1 interface: Application Protocols for R1 Services** - -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.....7 - -Modal verbs terminology.....7 - -1 Scope.....8 - -2 References .....8 - -2.1 Normative references .....8 - -2.2 Informative references.....9 - -3 Definition of terms, symbols and abbreviations.....10 - -3.1 Terms.....10 - -3.2 Symbols.....10 - -3.3 Abbreviations .....11 - -4 Application protocol for the R1 services.....12 - -4.1 Introduction .....12 - -4.2 Version conventions for the present document .....12 - -5 RESTful R1 service APIs.....12 - -5.1 Overview .....12 - -5.2 Versioning of RESTful R1 service APIs.....13 - -5.3 URI structure and supported content formats.....13 - -5.4 General considerations for RESTful R1 service APIs.....14 - -5.4.1 Usage of HTTP header fields.....14 - -5.4.2 Handling of large query results.....14 - -5.4.3 Error reporting .....14 - -6 Service management and exposure services.....15 - -6.1 Service registration API .....15 - -6.1.1 Introduction.....15 - -6.1.2 API version .....15 - -6.1.3 Resource structure and methods .....15 - -6.1.4 Service operations.....15 - -6.1.5 Resources.....19 - -6.1.6 Custom operations without associated resources.....21 - -6.1.7 Notifications .....21 - -6.1.8 Data model.....21 - -6.1.9 Error Handling.....21 - -6.2 Service discovery API.....22 - -6.2.1 Introduction.....22 - -6.2.2 API version .....22 - -6.2.3 Resource structure and methods .....22 - -6.2.4 Service operations.....22 - -6.2.5 Resources.....23 - -6.2.6 Custom operations without associated resources.....24 - -6.2.7 Notifications .....24 - -6.2.8 Data model.....24 - -6.2.9 Error Handling.....24 - -6.3 Service events subscription API.....25 - -6.3.1 Introduction.....25 - -6.3.2 API version .....25 - -6.3.3 Resource structure and methods .....25 - -6.3.4 Service operations.....25 - -6.3.5 Resources.....28 - -6.3.6 Custom operations without associated resources.....29 - -6.3.7 Notifications .....29 - -6.3.8 Data Model .....29 - -6.3.9 Error Handling.....30 - -- 6.4 Bootstrap API.....30 - - 6.4.1 Introduction.....30 - - 6.4.2 API version.....30 - - 6.4.3 Resource structure and methods .....30 - - 6.4.4 Service Operations.....30 - - 6.4.5 Resources.....31 - - 6.4.6 Custom operation without associated resources. ....32 - - 6.4.7 Notifications .....32 - - 6.4.8 Data Model .....32 - - 6.4.9 Error Handling.....33 -- 7 Data management and exposure services .....34 - - 7.1 Data registration API.....34 - - 7.1.1 Introduction.....34 - - 7.1.2 API version.....34 - - 7.1.3 Resource structure and methods .....34 - - 7.1.4 Service Operations.....35 - - 7.1.4 Service Operations.....38 - - 7.1.5 Resources.....39 - - 7.1.6 Custom operation without associated resources. ....43 - - 7.1.7 Notifications .....43 - - 7.1.8 Data Model .....43 - - 7.1.9 Error Handling.....46 - - 7.2 Data discovery API .....46 - - 7.2.1 Introduction.....46 - - 7.2.2 API version.....46 - - 7.2.3 Resource structure and methods .....46 - - 7.2.4 Service operations.....47 - - 7.2.5 Resources.....48 - - 7.2.6 Custom operation without associated resources. ....50 - - 7.2.7 Notifications .....51 - - 7.2.8 Data Model .....51 - - 7.2.9 Error Handling.....51 - - 7.3 Data access API.....52 - - 7.3.1 Introduction.....52 - - 7.3.2 API version.....52 - - 7.3.3 Resource structure and methods .....52 - - 7.3.4 Service Operations.....53 - - 7.3.5 Resources.....58 - - 7.3.6 Custom operation without associated resources. ....62 - - 7.3.7 Notifications .....63 - - 7.3.8 Data Model .....64 - - 7.3.9 Error Handling.....66 - - 7.4 HTTP based Push data API.....68 - - 7.4.1 Introduction.....68 - - 7.4.2 API version.....68 - - 7.4.3 Resource structure and methods .....68 - - 7.4.4 Service Operations.....68 - - 7.4.5 Resources.....69 - - 7.4.6 Custom operation without associated resources. ....69 - - 7.4.7 Notifications .....69 - - 7.4.8 Data Model .....70 - - 7.4.9 Error Handling.....70 - - 7.5 HTTP based Pull data API .....70 - - 7.5.1 Introduction.....70 - - 7.5.2 API version.....70 - - 7.5.3 Resource structure and methods .....70 - - 7.5.4 Service Operations.....71 - - 7.5.5 Resources.....72 - - 7.5.6 Custom operation without associated resources. ....73 - -- 7.5.7 Notifications .....73 -- 7.5.8 Data Model .....73 -- 7.5.9 Error Handling.....73 -- 7.6 Data offer API .....74 - - 7.6.1 Introduction.....74 - - 7.6.2 API version .....74 - - 7.6.3 Resource structure and methods .....74 - - 7.6.4 Service Operations.....75 - - 7.6.5 Resources.....77 - - 7.6.6 Custom operation without associated resources. ....79 - - 7.6.7 Notifications .....80 - - 7.6.8 Data Model .....82 - - 7.6.9 Error Handling.....85 -- 8 RAN OAM related services. ....85 - - 8.1 Configuration management API.....85 - - 8.1.1 Introduction.....85 - - 8.1.2 API version .....85 - - 8.1.3 Resource structure and methods .....85 - - 8.1.4 Service operations.....86 - - 8.1.5 Resources.....88 - - 8.1.6 Custom operations without associated resources. ....88 - - 8.1.7 Notifications .....88 - - 8.1.8 Data model.....89 - - 8.1.9 Error Handling.....89 - - 8.2 Fault management API.....89 - - 8.2.1 Introduction.....89 - - 8.2.2 API version .....89 - - 8.2.3 Resource structure and methods .....90 - - 8.2.4 Service operations.....90 - - 8.2.5 Resources.....92 - - 8.2.6 Custom operations without associated resources. ....93 - - 8.2.7 Notifications .....93 - - 8.2.8 Data model.....93 - - 8.2.9 Error Handling.....94 - - 8.3 Configuration schema information API. ....94 - - 8.3.1 Introduction.....94 - - 8.3.2 API version .....94 - - 8.3.3 Resource structure and methods .....94 - - 8.3.4 Service operations.....95 - - 8.3.5 Resources.....96 - - 8.3.6 Custom operations without associated resources. ....98 - - 8.3.7 Notifications .....98 - - 8.3.8 Data model.....98 - - 8.3.9 Error Handling.....99 -- 9. AI related services .....100 - - 9.1 AI policy management API .....100 - - 9.1.1 Introduction.....100 - - 9.1.2 API version .....100 - - 9.1.3 Resource structure and methods .....100 - - 9.1.4 Service operations.....101 - - 9.1.5 Resources.....112 - - 9.1.6 Custom operation without associated resources . ....121 - - 9.1.7 Notifications .....121 - - 9.1.8 Data Model .....122 - - 9.1.9 Error Handling.....126 -- 10. AI/ML workflow services .....127 - - 10.1 AI/ML model registration API .....127 - - 10.1.1 Introduction.....127 - -- 10.1.2 API version .....127 -- 10.1.3 Resource structure and methods .....127 -- 10.1.4 Service operations.....128 -- 10.1.5 Resources.....131 -- 10.1.6 Custom operation without associated resources. ....134 -- 10.1.7 Notifications .....134 -- 10.1.8 Data Model .....134 -- 10.1.9 Error Handling.....136 -- 10.2 AI/ML model discovery API.....137 - - 10.2.1 Introduction.....137 - - 10.2.2 API version .....137 - - 10.2.3 Resource structure and methods .....137 - - 10.2.4 Service operations.....137 - - 10.2.5 Resources.....139 - - 10.2.6 Custom operation without associated resources .....141 - - 10.2.7 Notifications .....141 - - 10.2.8 Data Model .....141 - - 10.2.9 Error Handling.....142 -- 10.3 AI/ML model training API.....142 - - 10.3.1 Introduction.....142 - - 10.3.2 API version .....142 - - 10.3.3 Resource structure and methods .....143 - - 10.3.4 Service operations.....143 - - 10.3.5 Resources.....147 - - 10.3.6 Custom operation without associated resources. ....149 - - 10.3.7 Notifications.....150 - - 10.3.8 Data Model .....150 - - 10.3.9 Error Handling.....151 -- 10.4 AI/ML model deployment API .....151 - - 10.4.1 Introduction.....151 - - 10.4.2 API version .....151 - - 10.4.3 Resource structure and methods .....152 - - 10.4.4 Service operations.....153 - - 10.4.5 Resources.....155 - - 10.4.6 Custom operation without associated resources. ....156 - - 10.4.7 Notifications .....156 - - 10.4.8 Data Model .....157 -- 10.5 Void.....157 - -**Annex A (normative): OpenAPI specifications.....158** - -- A.1 General .....158 - - A.1.1 Overview .....158 - - A.1.2 Common schemas for general use .....158 -- A.2 Service management and exposure service .....161 - - A.2.1 Service registration API.....161 - - A.2.2 Service discovery API .....163 - - A.2.3 Service events subscription API .....165 - - A.2.4 Bootstrap API .....166 -- A.3 Data management and exposure service.....167 - - A.3.1 Data registration API .....167 - - A.3.2 Data discovery API.....173 - - A.3.3 Data access API .....175 - - A.3.4 HTTP based Push data API .....180 - - A.3.5 HTTP based Pull data API.....180 - - A.3.6 Data offer API.....181 -- A.4 RAN OAM related services.....184 - - A.4.1 Configuration management API .....184 - - A.4.2 Fault management API .....185 - - A.4.3 Configuration schema information API.....185 -- A.5 AI related service.....188 - -- A.5.1 AI policy management API.....188 -- A.6 AI/ML workflow service.....195 - - A.6.1 AI/ML model registration API.....195 - - A.6.2 AI/ML model discovery API.....199 - - A.6.3 AI/ML model training API.....202 - - A.6.4 AI/ML model deployment API.....205 -- Annex B (normative): Common data types for R1 service APIs.....207** - - B.1 Introduction .....207 - - B.2 Common data types for Generic Usage.....207 - - B.2.1 Introduction.....207 - - B.2.2 Simple data types.....207 - - B.2.3 Enumeration.....207 - - B.2.4 Structured data types.....207 - - B.2.5 Re-used data types .....209 - - B.3 Common data types for Service management and exposure .....209 - - B.3.1 Introduction.....209 - - B.3.2 Simple data types.....209 - - B.3.3 Enumerations .....209 - - B.3.4 Structured data types.....209 - - B.3.5 Re-used data types .....209 - - B.4 Common data types for Data Management and Exposure .....210 - - B.4.1 Introduction.....210 - - B.4.2 Simple data types.....210 - - B.4.3 Enumerations .....211 - - B.4.4 Structured data types.....211 - - B.4.5 Re-used data types .....212 - - B.5 Common data types for RAN OAM related services .....212 - - B.5.1 Introduction.....212 - - B.5.2 Simple data types.....212 - - B.5.3 Enumerations .....212 - - B.5.4 Structured data types.....212 - - B.5.5 Re-used data types .....212 -- Annex (informative): Bibliography .....214 -- Annex (informative): Change history .....215 - -# --- Foreword - -This Technical Specification (TS) has been produced by WG2 of the O-RAN ALLIANCE. It is part of a TS-family covering the WG2: R1 Interface Specifications. - -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 Application Protocols for R1 Services. - -# --- 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 29.501 (v16.0): “5G System; Principles and Guidelines for Services Definition; (“3GPP TS 29.501“). -- [2] 3GPP TS 29.500: “5G System; Technical Realization of Service Based Architecture; Stage 3“. (“3GPP TS 29.500“) -- [3] OpenAPI: “OpenAPI 3.0.3 Specification“, -NOTE: Available at : -- [4] ETSI GS NFV-SOL 013 Rel3: “Protocols and Data Models; Specification of common aspects for RESTful NFV MANO APIs“. -- [5] O-RAN.WG2.TS.R1GAP: “R1 General Aspects and Principles“ (“R1GAP“). -- [6] O-RAN.WG2.TS.R1UCR: “R1 Use Cases and Requirements“ (“R1UCR“). -- [7] O-RAN.WG2.TS.R1TP: “Transport Protocols for R1 services“ (“R1TP“). -- [8] IETF RFC 3986: “Uniform Resource Identifier (URI): Generic Syntax“. -- [9] 3GPP TS 29.222 (v18.6.0): “Common API Framework for 3GPP Northbound APIs. (“3GPP TS 29.222“) -- [10] IETF RFC 7807: “Problem Details for HTTP APIs“. -- [11] Semantic Versioning 2.0.0. -NOTE: Available at : . -- [12] IETF RFC 8259: “The JavaScript Object Notation (JSON) Data Interchange Format“. -- [13] IETF RFC 4229: “HTTP Header Field Registrations“. -- [14] json-schema 2020-12, -NOTE: Available at: ““. -- [15] Kafka Documentation -NOTE : Available at : ““. -- [16] W3C REC-xmlschema-1-20010502 : “XML Schema Part 1 : Structures“, - -NOTE : Available at : . - -[17] W3C REC-xmlschema-2-20010502 : “XML Schema Part 2 : Datatypes“, - -NOTE : Available at : . - -[18] W3C REC-xml-names-19990114: “Namespaces in XML“ - -NOTE: Available at : . - -[19] IETF RFC 1035: “DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION“. - -[20] 3GPP TS 28.532: “Management and orchestration; Generic management services“. (“3GPP TS 28.532“). - -[21] 3GPP TS 28.622: “ Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)“ (“3GPP TS 28.622“) - -[22] 3GPP TS 28.623 (v17.9.0): “Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions“. (“3GPP TS 28.623“). - -[23] O-RAN.WG2.TS.A1AP: “A1 Interface: Application Protocol“ (“A1AP“). - -[24] O-RAN.WG2.TS.A1TD: “A1 interface: Type Definitions“ (“A1TD“). - -[25] IETF RFC 9110: “HTTP Semantics“. - -[26] 3GPP TS 28.111: " Management and orchestration;Fault Management (FM) (“3GPP TS 28.111“). - -[27] Protocol Buffers Documentation. - -NOTE: Available at : “”. - -[28] Avro Documentation. - -NOTE: Available at : “”. - -[29] 3GPP TS 32.158: " Management and orchestration;Design rules for REpresentational State Transfer (REST) Solution Sets (SS) (“3GPP TS 32.158“). - -[30] CloudEvents- version1.0 (“CloudEvents”) - -NOTE: Available at : “spec/cloudevents/spec.md at v1.0.2 · cloudevents/spec · GitHub” - -[31] HTTP Protocol Binding for CloudEvents - Version 1.0.2 (“HTTP-CloudEvents”) - -NOTE: Available at : “spec/cloudevents/bindings/http-protocol-binding.md at v1.0.2 · cloudevents/spec · GitHub”. - -## 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] W3C REC-xmlschema-0-20010502: “XML Schema Part 0: Primer“ - -NOTE: Available at : . - -# --- 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the following terms apply: - -**API Consumer:** The Service Consumer consuming one or more services using APIs. - -NOTE: The Service Consumer role is introduced in R1GAP [5]. - -**API Producer:** The Service Producer that offers its services for consumption via APIs. - -NOTE: The Service Producer role is introduced in R1GAP [5]. - -**DME type:** data type managed and exposed by the DME services and identified by a data type identifier. - -## 3.2 Symbols - -Void - -## 3.3 Abbreviations - -For the purposes of the present document, the following abbreviations apply: - -| | | -|------|-----------------------------------| -| API | Application programming interface | -| FQDN | Fully qualified domain name | -| IOC | Information Object Class | - -# 4 Application protocol for the R1 services - -## 4.1 Introduction - -The present document contains a realization for the procedures identified in R1GAP [5]. It is based on transport protocols as defined in R1TP [7]. This definition of the R1 Application Protocols (R1AP) defined in the present document is based on the 3GPP service framework for network functions specified in 3GPP TS 29.501 [1]. - -## 4.2 Version conventions for the present document - -The version number of the present document follows the “xx.yy“ versioning scheme. There could be implications for the interoperability between rApps and R1 service API implementations in SMO/Non-RT RIC framework that are based on different versions of the present document. - -An incremented “xx“ version field of the present document could indicate that a new major feature (e.g., a new R1 service) has been added or that an incompatible change has been made to one or more R1 service APIs. An incremented “yy“ version field could indicate that an optional feature has been added, a technical issue has been fixed, or that clarifications or editorial corrections have been made. - -The version conventions for RESTful R1 service APIs are defined in clause 5.2. - -# 5 RESTful R1 service APIs - -## 5.1 Overview - -The design of the RESTful R1 service APIs is based on the procedures and requirements defined in R1UCR [6] and R1GAP [5], and on the protocol design framework as specified in 3GPP TS 29.501 [1] . - -The API version of a service API includes a pre-release version (e.g., “-alpha.1“) if the service API is under development. - -The present document defines the protocols for the R1 service APIs listed in table 5.1-1. - -**Table 5.1-1: RESTful R1 service APIs and their versions defined in the present document.** - -| R1 Services | Service API | API Version | -|------------------------------------------|----------------------------------|---------------| -| Service management and exposure services | Service registration | 1.2.0 | -| | Service discovery | 1.2.0 | -| | Service events subscription | 1.2.0 | -| | Bootstrap | 1.0.1 | -| Data management and exposure services | Data registration | 2.0.0-alpha.3 | -| | Data discovery | 2.0.1 | -| | Data access | 2.0.0-alpha.3 | -| | HTTP based push data | 1.0.0 | -| | HTTP based pull data | 1.0.0 | -| | Data offer | 2.0.0-alpha.1 | -| RAN OAM-related services | Configuration management | 1.0.0-alpha.1 | -| | Fault management | 1.0.0 | -| | Configuration schema information | 1.0.1 | -| A1-related services | A1 policy management | 1.0.1 | -| AI/ML workflow services | AI/ML model registration | 1.0.1 | -| | AI/ML model discovery | 1.1.1 | -| | AI/ML model training | 1.0.0-alpha.2 | -| | AI/ML model deployment | 1.0.0-alpha.2 | - -## 5.2 Versioning of RESTful R1 service APIs - -Each RESTful R1 service API is versioned independently. The API version number defined in the present document contains three numerical fields following a MAJOR.MINOR.PATCH pattern, and may contain a pre-release version field, according to SemVer [11]. - -The API version number held by an implementation may additionally include a build metadata field, according to SemVer [11], to indicate a specific deployment. The content of this field is implementation specific; it is provided by the deployment. The path segment used in URI structures indicate the MAJOR field of the API version number. The full API version number is visible in the “version“ field of the “info“ object of each OpenAPI document in Annex A, as well as in the ServiceAPIDescription information communicated during service registration and service discovery (see annex B.3.4.1). - -To indicate the full API version the API Consumer intends to use, the API Consumer may include the “Version“ HTTP header (see IETF RFC 4229 [13] ) in an HTTP request, in which case the header shall contain the version identifier as defined above. It is optional to include the build metadata field. - -The API Producer shall include in the response the “Version“ HTTP header signalling the used API version, including the build metadata if available. If the build metadata have been omitted in the request, the API Producer shall use the combination of MAJOR, MINOR, PATCH, and pre-release indicator as requested and the highest supported value for the build metadata field for that combination, if available. In case the API Consumer has not sent a “Version“ header in the request, the API Producer shall use the latest available version, and signal it in the “Version“ header. - -NOTE: In case multiple versions are supported by an API Producer under the URI for a major version, this allows the API Consumer to request a particular version. This mechanism is referred to as “microversioning“. - -If the API version signalled by the API Consumer in the “Version“ request header is not supported by the API Producer, the API Producer shall respond with a “406 Not Acceptable“ error and may include in the response payload body a Problem Details structure providing more information on the cause of the error. - -## 5.3 URI structure and supported content formats - -This clause specifies the URI prefix and the supported content formats applicable to the RESTful R1 service APIs. - -All resource URIs of the APIs shall have the following prefix: - -**{apiRoot}
/** - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [1], i.e.: - -**{apiRoot}
** - -with the following components: - -- The {apiRoot} shall be set as described in 3GPP TS 29.501[1], clause 4.4.1; however, the restrictions w.r.t the operator specific FQDN of the host portion defined there do not apply. -- The indicates the API name of the service interface in an abbreviated form. It is defined in the clause specifying the corresponding RESTful R1 service API. -- The indicates the major version (see clause 5.2) of the API and is defined in the clause specifying the corresponding RESTful R1 service API. -- Each represents a specific resource of the API. It is defined in the corresponding RESTful R1 service API for each one of the defined resources. - -For HTTP requests and responses that have message content, the content format JSON (see IETF RFC 8259 [12]) shall be supported. The JSON format shall be signalled by the content type “application/json“. - -All resource URIs of the API shall comply with the URI syntax as defined in IETF RFC 3986 [8]. An implementation that dynamically generates resource URI parts (individual path segments, sequences of path segments that are separated by “/”, query parameter values) shall ensure that these parts only use the character set that is allowed by IETF RFC 3986 [8] for these parts. - -## 5.4 General considerations for RESTful R1 service APIs - -### 5.4.1 Usage of HTTP header fields - -HTTP headers are components of the headers section of the HTTP request and response messages. The usage of HTTP header fields shall follow the definitions in ETSI GS NFV-SOL 013 [4], clause 4.2. - -### 5.4.2 Handling of large query results - -The handling of large query results shall be supported by RESTful R1 service APIs as specified in ETSI GS NFV-SOL 013 [4], clause 5.4.2. - -### 5.4.3 Error reporting - -In RESTful interfaces, application errors are mapped to HTTP errors. Since HTTP error information is generally not enough to discover the root cause of the error, additional application specific error information is typically delivered in the message content based on the ProblemDetails data type. - -HTTP error responses shall be supported as specified in 3GPP TS 29.501 [1], clause 4.8. Protocol errors and application errors specified in 3GPP TS 29.500 [2], table 5.2.7.1-1, shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in 3GPP TS 29.500 [2], table 5.2.7.1-1. - -If an HTTP method is not defined for a particular resource in the present document, that method is not supported. When that method is requested on the resource, the API Producer shall return a “405 Method Not Allowed” response. The message content may include a ProblemDetails structure. - -# 6 Service management and exposure services - -## 6.1 Service registration API - -### 6.1.1 Introduction - -This API allows the API Consumer to manage registrations of service APIs based on the procedures for “Registration of services“ defined in R1GAP [5]. - -### 6.1.2 API version - -For the service registration API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 2 and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1] for a definition of the version fields). Consequently, the URI path segment shall be set to “v1“. - -### 6.1.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined for the CAPIF\_Publish\_Service\_API (see 3GPP TS 29.222 [9], for Figure 8.2.2.1-1 in Clause 8.2.2). - -Table 6.1.3-1 lists the individual resources defined for the API, the applicable HTTP methods as defined in 3GPP TS 29.222 [9], clause 8.2) and the associated service operations. - -**Table 6.1.3-1: Resources and methods overview of the service registration API** - -| Resource Name
3GPP TS 29.222 [9] | Resource URI
3GPP TS 29.222 [9] | HTTP method
3GPP TS 29.222 [9] | Service Operation | -|-------------------------------------|--------------------------------------|-----------------------------------|---------------------------------------| -| APF published APIs | /{apfld}/service-apis | POST | Register service API | -| | | GET | Query service APIs | -| Individual APF published API | /{apfld}/service-apis/{serviceApiId} | PUT | Update registered service API | -| | | DELETE | Deregister service API | -| | | PATCH | Partial update registered service API | - -### 6.1.4 Service operations - -#### 6.1.4.1 Register service API - -##### 6.1.4.1.1 Operation definition - -A Service Producer uses the Register service API operation as API Consumer to register with the API Producer service APIs for services it is capable of producing. - -The operation is based on HTTP POST. - -``` -@startuml -autonumber -participant "API Consumer" as cons -participant "API Producer" as prod -cons ->> prod : POST .../{apfld}/service-apis (ServiceAPIDescription) -``` - -``` -prod --> cons : 201 Created (ServiceAPIDescription) -@enduml -``` - -![Sequence diagram for Register service API operation. It shows an API Consumer sending a POST request to an API Producer, and the API Producer responding with a 201 Created status.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: - API Consumer->>API Producer: 1 POST .../{apflId}/service-apis (ServiceAPIDescription) - Note right of API Producer: - API Producer-->>API Consumer: 2 201 Created (ServiceAPIDescription) - Note left of API Consumer: - -``` - -Sequence diagram for Register service API operation. It shows an API Consumer sending a POST request to an API Producer, and the API Producer responding with a 201 Created status. - -**Figure 6.1.4.1.1-1: Register service API operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP POST request to the API Producer. The target URI shall identify the resource (.../{apflId}/service-apis/) under which the new registration is requested to be created. The message content shall carry a ServiceAPIDescription structure. The API Producer shall process the message content received in the HTTP POST message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall generate the service API identifier and construct the URI for the created resource. The API Producer shall return the HTTP POST response. On success “201 Created“ shall be returned. The “Location“ header shall be present and shall carry the URI of the new registration resource. The message content shall carry the registered service API description. On failure, the appropriate error code shall be returned, and the message response body may contain additional error information. - -##### **6.1.4.1.2 Referenced procedures.** - -###### **6.1.4.1.2.1 Register service procedure** - -The Register service API operation illustrated in figure 6.1.4.1.1-1 is based on the Register service procedure defined in R1GAP [5]. - -#### **6.1.4.2 Update registered service API.** - -##### **6.1.4.2.1 Operation definition** - -A Service Producer uses the Update registered service API operation as API Consumer to update a complete service API registration with the API Producer. - -The operation is based on HTTP PUT. - -``` -@startuml -autonumber -participant "API Consumer" as cons -participant "API Producer" as prod -cons --> prod : PUT .../{apflId}/service-apis/{serviceApiId} (ServiceAPIDescription) -prod --> cons : 200 OK (ServiceAPIDescription) -@enduml -``` - -![Sequence diagram for Update registered service API operation. It shows an API Consumer sending a PUT request to an API Producer, and the API Producer responding with a 200 OK status.](2cde062fd82833415971a8bd1a2cafab_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: - API Consumer->>API Producer: 1 PUT .../{apflId}/service-apis/{serviceApiId} (ServiceAPIDescription) - Note right of API Producer: - API Producer-->>API Consumer: 2 200 OK (ServiceAPIDescription) - Note left of API Consumer: - Note right of API Producer: - -``` - -Sequence diagram for Update registered service API operation. It shows an API Consumer sending a PUT request to an API Producer, and the API Producer responding with a 200 OK status. - -**Figure 6.1.4.2.1-1: Update registered service API operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP PUT request to the API Producer. The target URI shall identify the resource (.../{apflId}/service-apis/{serviceApiId}). The message content shall carry an updated service API description. The API Producer shall determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP PUT response. On success “200 OK“ shall be returned. The message content shall carry the updated service API description. On failure, the appropriate error code shall be returned, and the message response body may contain additional error information. - -##### **6.1.4.2.2 Referenced procedures.** - -###### **6.1.4.2.2.1 Update service registration procedure** - -The Update registered service API operation illustrated in figure 6.1.4.2.1-1 is based on the Update service registration procedure defined in R1GAP [5]. - -#### **6.1.4.3 Deregister service API** - -##### **6.1.4.3.1 Operation definition** - -A Service Producer uses the Deregister service API operation as API Consumer to deregister a service with the API Producer - -The operation is based on HTTP DELETE. - -``` - -@startuml -autonumber -participant "API Consumer" as cons -participant "API Producer" as prod -cons ->> prod : DELETE .../{apflId}/service-apis/{serviceApiId} -prod -->> cons : 204 No Content -@enduml - -``` - -![Sequence diagram for Deregister service API operation. It shows an API Consumer sending a DELETE request to an API Producer, and the API Producer responding with a 204 No Content status.](4aa740e8119817a3f9b9f72d06eaa53d_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: - API Consumer->>API Producer: 1 DELETE .../{apflId}/service-apis/{serviceApiId} - Note right of API Producer: - API Producer-->>API Consumer: 2 204 No Content - Note left of API Consumer: - Note right of API Producer: - -``` - -Sequence diagram for Deregister service API operation. It shows an API Consumer sending a DELETE request to an API Producer, and the API Producer responding with a 204 No Content status. - -**Figure 6.1.4.3.1-1: Deregister service API operation.** - -The service operation is as follows: - -1. To deregister a service, The API Consumer shall send an HTTP DELETE. request to the API Producer . The target URI shall identify the resource to be deleted (.../{apfId}/service-apis/{serviceApiId}. The API Producer shall process the message content received in the HTTP DELETE message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP DELETE response. On success “204 No Content“ shall be returned. On failure, the appropriate error code shall be returned, and the message response body may contain additional error information. - -##### **6.1.4.3.2 Referenced procedures** - -###### **6.1.4.3.2.1 Deregister service procedure** - -The Deregister service API operation illustrated in figure 6.1.4.3.1-1 is based on the Deregister service procedure defined in R1GAP [5]. - -#### **6.1.4.4 Partially update registered service API** - -##### **6.1.4.4.1 Operation definition** - -A Service Producer uses the Partially update registered service API operation as API Consumer to partially update a service API registration with the API Producer. - -The operation is based on HTTP PATCH. - -``` -@startuml -autonumber -participant "API Consumer" as cons -participant "API Producer" as prod -cons ->> prod : PATCH.../{apfId}/service-apis/{serviceApiId} (ServiceAPIDescriptionPatch) -prod -->> cons : 200 OK (ServiceAPIDescription) -@enduml -``` - -![Sequence diagram showing the partial update registered service API operation. The API Consumer sends a PATCH request to the API Producer, and the API Producer responds with a 200 OK status.](aa9441a5971655a79987d70fc551b26a_img.jpg) - -``` - -sequenceDiagram - autonumber - participant API Consumer - participant API Producer - API Consumer->>API Producer: PATCH.../{apfId}/service-apis/{serviceApiId} (ServiceAPIDescriptionPatch) - API Producer-->>API Consumer: 200 OK (ServiceAPIDescription) - -``` - -Sequence diagram showing the partial update registered service API operation. The API Consumer sends a PATCH request to the API Producer, and the API Producer responds with a 200 OK status. - -**Figure 6.1.4.4.1-1: Partial update registered service API operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP PATCH request to the API Producer. The target URI shall identify the resource (.../{apfId}/service-apis/{serviceApiId}. The message content shall carry a service API description patch structure. The API Producer shall determine if the request sent by the API Consumer is authorized or not. If so, the API Producer shall process the message content received in the HTTP PATCH message. -2. The API Producer shall return the HTTP PATCH response. On success “200 OK“ shall be returned. The message content shall carry the updated service API description. On failure, the appropriate error code shall be returned, and the message response body may contain additional error information. - -##### 6.1.4.4.2 Referenced procedures. - -###### 6.1.4.4.2.1 Update service registration procedure - -The Update registered service API operation illustrated in figure 6.1.4.2.1-1 is based on the Update service registration procedure defined in R1GAP [5]. - -#### 6.1.4.5 Query service APIs - -##### 6.1.4.5.1 Operation definition - -The API Consumer uses the Query service APIs operation to retrieve the service API descriptions that are registered with the API Producer. - -The operation is based on HTTP GET. - -``` -@startuml -autonumber -participant "API Consumer" as cons -participant "API Producer" as prod -cons ->> prod : GET .../{apfId}/service-apis -prod -->> cons : 200 OK array(ServiceAPIDescription) -@enduml -``` - -![Sequence diagram showing the Query service API operation. The API Consumer sends a GET request to the API Producer, and the API Producer responds with a 200 OK status and an array of ServiceAPIDescription.](327ba94498e3381cf08eb41e3fd3d77f_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 GET .../{apfId}/service-apis - API Consumer->> API Producer: 1 GET .../{apfId}/service-apis - Note right of API Producer: 2 200 OK array(ServiceAPIDescription) - API Producer-->> API Consumer: 2 200 OK array(ServiceAPIDescription) -``` - -Sequence diagram showing the Query service API operation. The API Consumer sends a GET request to the API Producer, and the API Producer responds with a 200 OK status and an array of ServiceAPIDescription. - -Figure 6.1.4.5.1-1: Query service API operation - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../{apfId}/service-apis). The message content shall be empty. The API producer shall process the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the “200 OK“ on success and the message content shall carry a list requested service API description. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -##### 6.1.4.5.2 Referenced procedures - -###### 6.1.4.5.2.1 Query register service procedure - -The Query service APIs operation illustrated in figure 6.1.4.5.1-1 is based on the query registered service procedure defined in R1GAP [5]. - -### 6.1.5 Resources - -#### 6.1.5.1 Overview - -This clause defines the resources for the service registration API based on 3GPP TS 29.222 [9]. - -#### 6.1.5.2 Resource: "APF published APIs" - -This resource is defined in 3GPP TS 29.222 [9], clause 8.2 with the following URI: - -**{apiRoot}/published-apis//{apfId}/service-apis** - -By consuming this API, an rApp takes the role of the APF (API publishing function). - -In addition to the provisions in 3GPP TS 29.222 [9], clause 8.1, the following shall apply: - -- The value of the {apfId} resource URI variable shall be set to the rAppId of the rApp that performs the service registration. - -##### 6.1.5.2.1 Resource Standard Methods - -###### 6.1.5.2.1.1 POST - -This method shall support the URI query parameters, request data, response data structures and response codes specified in 3GPP TS 29.222 [9], clause 8.2.2.2.3.1. - -###### 6.1.5.2.1.2 GET - -This method shall support the URI query parameters, request data structures, response data structures, and response codes specified in 3GPP TS 29.222 [9], clause 8.2.2.2.3.2. - -##### 6.1.5.2.2 Resource Custom Operations - -None - -#### 6.1.5.3 Resource: "Individual APF published API" - -This resource is defined in 3GPP TS 29.222 [9], clause 8.2.2.3 with the following URI: - -**{apiRoot}/published-apis//{apfId}/service-apis/{serviceApiId}** - -By consuming this API, an rApp takes the role of the APF (API publishing function). - -In addition to the provisions in 3GPP TS 29.222 [9], clause 8.2, the following shall apply: - -- The value of the {apfId} resource URI variable shall be set to the rAppId of the rApp that performed the service registration. - -##### 6.1.5.3.1 Resource Standard Methods - -###### 6.1.5.3.1.1 PUT - -This method shall support the URI query parameters, request data structures, response data structures and response codes specified in 3GPP TS 29.222 [9], clause 8.2.2.3.3.2. - -###### 6.1.5.3.1.2 DELETE - -This method shall support the URI query parameters, request data, response data structures and response codes specified in 3GPP TS 29.222 [9], clause 8.2.2.3.3.3. - -###### 6.1.5.3.1.3 PATCH - -This method shall support the URI query parameters, request data structures, response data structures and response codes specified in 3GPP TS 29.222 [9], clause 8.2.2.3.3.4. - -##### 6.1.5.3.2 Resource Custom Operations - -None. - -### 6.1.6 Custom operations without associated resources. - -None. - -### 6.1.7 Notifications - -None - -### 6.1.8 Data model - -#### 6.1.8.1 General - -The application data model is defined in 3GPP TS 29.222 [9], clause 8.2.4. In addition, the adaptations specified in clause B.3 apply to this API. - -#### 6.1.8.2 Structured data types - -None. - -#### 6.1.8.3 Simple data types and enumerations - -None. - -#### 6.1.8.4 Re-used data types - -The re-used data types are defined in clause B.3 - -#### 6.1.8.5 Service-specific registration information - -None. - -### 6.1.9 Error Handling - -#### 6.1.9.1 General - -HTTP error handling is applicable for this API as specified in 3GPP TS 29.222 [9], clause 7.7 . - -#### 6.1.9.2 Protocol Errors - -Protocol error handling shall be supported as specified in 3GPP TS 29.222 [9], clause 8.1.5.2 . - -#### 6.1.9.3 Application Errors - -Application error handling shall be supported as specified in 3GPP TS 29.222 [9], clause 8.2.5.3. - -## 6.2 Service discovery API - -### 6.2.1 Introduction - -This API allows the API Consumer to perform service discovery based on the service discovery procedures defined in R1GAP [5]. The API is based on the CAPIF\_Discover\_Service\_API as specified in 3GPP TS 29.222 [9]. - -### 6.2.2 API version - -For the service discovery API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 2 and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1] for a definition of the version fields). Consequently, the URI path segment shall be set to “v1”. - -### 6.2.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined for the CAPIF\_Discovery\_Service\_API (see 3GPP TS 29.222 [9], Figure 8.1.2.1-1 in clause 8.1.2) - -Table 6.2.3-1 lists the individual resources defined for the API and the applicable HTTP methods as defined in 3GPP TS 29.222 [9], clause 8.1 of) and the associated service operations. - -**Table 6.2.3-1: Resources and methods overview of the service discovery API** - -| Resource Name
3GPP TS 29.222 [9] | Resource URI
3GPP TS 29.222 [9] | HTTP method
3GPP TS 29.222 [9] | Service Operation | -|-------------------------------------|------------------------------------|-----------------------------------|--------------------| -| All published service APIs | .../allServiceAPIs | GET | Query service APIs | - -### 6.2.4 Service operations - -#### 6.2.4.1 Query service APIs - -##### 6.2.4.1.1 Operation definition - -The API Consumer uses the Query service APIs operation to discover service APIs information. - -The operation is based on HTTP GET as per figure 6.2.4.1.1-1. The HTTP GET response contains information about all services that the API Consumer is authorized to access and that match the filtering criteria. - -``` -@startuml -autonumber -participant "API Consumer" as cons -participant "API Producer" as prod -cons -->> prod : GET .../allServiceAPIs -prod -->> cons : 200 OK (DiscoveredAPIs) -@enduml -``` - -![Sequence diagram illustrating the Query service APIs operation. It shows an API Consumer sending a GET request to an API Producer, and the API Producer returning a 200 OK response with discovered APIs.](d734a6ea1b381280f043fcf70391b6db_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET .../allServiceAPIs - API Producer-->>API Consumer: 2 200 OK (DiscoveredAPIs) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - -``` - -Sequence diagram illustrating the Query service APIs operation. It shows an API Consumer sending a GET request to an API Producer, and the API Producer returning a 200 OK response with discovered APIs. - -**Figure 6.2.4.1.1-1: Query service APIs operation** - -This service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../allServiceAPIs) and may also contain that includes the rApp identifier and optional filtering criteria. The API Producer shall process the service discovery details received in the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP GET response. On success “200 OK“ shall be returned and the message content shall carry a list of service profiles that the API Consumer is authorized to access and that match the filtering criteria, if provided. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -##### 6.2.4.1.2 Referenced procedures - -###### 6.2.4.1.2.1 Discovery services procedure - -The Query service APIs operation illustrated in figure 6.2.4.1.1-1 is based on the Discover services procedure as defined in R1GAP [5]. - -### 6.2.5 Resources - -#### 6.2.5.1 Overview - -This clause defines the resource for the Service discovery API based on 3GPP TS 29.222 [9]. - -#### 6.2.5.2 Resource: "All published service APIs" - -This resource is defined in 3GPP TS 29.222 [9], clause 8.1 with the following URI: - -**{apiRoot}/service-apis //allserviceapis** - -In addition to the provisions in 3GPP TS 29.222 [9], clause 8.1, the following shall apply: - -- 1) In the GET method, the URI query parameters “api-name“ and “api-version“ are relevant in the context of the SME services and shall be supported by the API Producer to allow filtering the query by name and/or version of the service API. The API Consumer may provide these parameters. The following parameters are not applicable in the context of the SME services and therefore need not be supported: comm-type, protocol, aef-id, data-format, api-cat, preferred-aef-loc, supported-features, api-supported-features. -- 2) In the GET method, the URI query parameter “api-invoker-id“ shall carry the rAppId of the rApp that performs the service discovery. - -##### 6.2.5.2.1 Resource Standard Methods - -###### 6.2.5.2.1.1 GET - -This method shall support the URI query parameters, response data structures and response codes specified in 3GPP TS 29.222 [9], clause 8.1.2.2.3.1 . - -##### 6.2.5.2.2 Resource Custom Operations - -None. - -### 6.2.6 Custom operations without associated resources - -None. - -### 6.2.7 Notifications - -None. - -### 6.2.8 Data model - -#### 6.2.8.1 General - -The application data model is defined in 3GPP TS 29.222 [9], clause 8.1.4, apply to this API. In addition, the adaptations specified in clause B.3 apply to this API. - -#### 6.2.8.2 Structured data types - -None. - -#### 6.2.8.3 Simple data types and enumerations - -None. - -#### 6.2.8.4 Re-used data types - -The re-used data types are defined in clause B.3. - -#### 6.2.8.5 Service-specific registration information - -None. - -### 6.2.9 Error Handling - -#### 6.2.9.1 General - -HTTP error handling is applicable for this API as specified in 3GPP TS 29.222 [9], clause 7.7 . - -#### 6.2.9.2 Protocol Errors - -Protocol error handling shall be supported as specified in 3GPP TS 29.222 [9], clause 8.1.5.2 . - -#### 6.2.9.3 Application Errors - -Application error handling shall be supported as specified in 3GPP TS 29.222 [9], clause 8.2.5.3 . - -## 6.3 Service events subscription API - -### 6.3.1 Introduction - -This API allows the API Consumer to subscribe to and unsubscribe from service event notifications as specified in R1GAP [5]. The API is based on the CAPIF\_Events\_API as specified in 3GPP TS 29.222 [9]. - -### 6.3.2 API version - -For the service events subscription API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 2 and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1], clause 4.3.1.1, for a definition of the version fields). Consequently, the URI part segment shall be set to “v1”. - -### 6.3.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined for the CAPIF\_Events\_API (see 3GPP TS 29.222 [9], Figure 8.3.2.1-1 in clause 8.3.1). - -Table 6.3.3-1 lists the individual resources defined for the API and the applicable HTTP methods as defined in 3GPP TS 29.222 [9], clause 8.3.1, and the associated service operations. - -**Table 6.3.3-1: Resources and methods overview of the service subscription API** - -| Resource Name
3GPP TS 29.222 [9] | Resource URI
3GPP TS 29.222 [9] | HTTP method
3GPP TS 29.222 [9] | Service Operation | -|--------------------------------------|------------------------------------------------|-----------------------------------|----------------------------| -| CAPIF Events Subscriptions | /{subscriberId}/subscriptions | POST | Subscribe service events | -| Individual CAPIF Events Subscription | /{subscriberId}/subscriptions/{subscriptionId} | DELETE | Unsubscribe service events | - -### 6.3.4 Service operations - -#### 6.3.4.1 Subscribe service events. - -##### 6.3.4.1.1 Operation definition - -The API Consumer uses the subscribe service events API operation to subscribe to service event notifications. - -The operation is based on HTTP POST. - -``` -@startuml -autonumber -participant "API Consumer" as cons -participant "API Producer" as prod -cons ->> prod : POST ../{subscriberId}/subscriptions/ (EventSubscription) -prod -->> cons : 201 Created (subscriptionId) -@enduml -``` - -![Sequence diagram showing the Subscribe service events APIs operation. An API Consumer sends a POST request to an API Producer, and the API Producer responds with a 201 Created status.](5a1abd59a95fa47ae192807de151e9eb_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 POST .../{subscriberId}/subscriptions/ (EventSubscription) - API Producer-->>API Consumer: 2 201 Created (subscriptionId) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - -``` - -Sequence diagram showing the Subscribe service events APIs operation. An API Consumer sends a POST request to an API Producer, and the API Producer responds with a 201 Created status. - -**Figure 6.3.4.1.1-1: Subscribe service events APIs operation.** - -This service operation is as follows: - -1. The API Consumer shall send an HTTP POST request to the API Producer. The target URI shall identify the resource (“.../{subscriberId}/subscriptions/”) under which the new subscription is requested to be created. The message content shall carry a EventSubscription structure. The API Producer shall process the request received in the HTTP POST message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return HTTP POST response. On success “201 Created” shall be returned. The “Location” HTTP header shall be present and shall carry the URI for the newly created resource i.e., subscription identifier. The message content shall carry a EventSubscription structure that represents the new resource. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -##### **6.3.4.1.2 Referenced procedures.** - -###### **6.3.4.1.2.1 Subscribe service availability.** - -The Subscribe service events operation illustrated in figure 6.3.4.1.1-1 is based on the Subscribe service availability procedure defined in R1GAP [5]. - -#### **6.3.4.2 Unsubscribe service events.** - -##### **6.3.4.2.1 Operation definition** - -The API Consumer uses the unsubscribe service events operation to unsubscribe from service event notifications. - -The operation is based on HTTP DELETE. - -``` - -@startuml -autonumber -participant "API Consumer" as cons -participant "API Producer" as prod -cons ->> prod :DELETE.../{subscriberId}/subscriptions/{subscriptionId} -prod -->> cons : 204 No Content -@enduml - -``` - -![Sequence diagram for Unsubscribe service events operation. It shows an API Consumer sending a DELETE request to an API Producer, and the API Producer responding with a 204 No Content status.](a149b400127a3e3e50b3c98d27c5935c_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - API Consumer->>API Producer: 1 DELETE.../{subscriberId}/subscriptions/{subscriptionId} - API Producer-->>API Consumer: 2 204 No Content - -``` - -Sequence diagram for Unsubscribe service events operation. It shows an API Consumer sending a DELETE request to an API Producer, and the API Producer responding with a 204 No Content status. - -**Figure 6.3.4.2.1-1: Unsubscribe service events operation.** - -This service operation is as follows: - -1. The API Consumer shall send an HTTP DELETE request to the API Producer. . The target URI shall identify the resource (“.../{subscriberId}/subscriptions/{subscriptionId}“). The message content shall be empty. The API Producer shall process the request received in the HTTP DELETE message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP DELETE response. On success “204 No Content“ shall be returned. The message content shall be empty. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -##### **6.3.4.2.2 Referenced procedures.** - -###### **6.3.4.2.2.1 Unsubscribe service availability.** - -The Unsubscribe service events operation illustrated in figure 6.3.4.3.1-1 is based on the Unsubscribe service availability procedure defined in R1GAP [5]. - -#### **6.3.4.3 Notification service API** - -##### **6.3.4.3.1 Operation definition** - -The API Producer sends notifications to all subscribed API Consumers. - -The operation is based on HTTP POST. - -``` - -@startuml -autonumber -participant "API Consumer" as cons -participant "API Producer" as prod -prod ->> cons : POST.../Event notification {callback URI} -@enduml - -``` - -![Sequence diagram for Notification service API operation. It shows an API Producer sending a POST request to an API Consumer, with a callback URI in the message.](bdcc4eb452fcc6ba091949b77546a6d4_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - API Producer->>API Consumer: 1 POST.../Event notification {callback URI} - -``` - -Sequence diagram for Notification service API operation. It shows an API Producer sending a POST request to an API Consumer, with a callback URI in the message. - -**Figure 6.3.4.3.1-1: Notification service API operation** - -This service operation is as follows: - -1. The API Producer shall send an HTTP POST request to the API Consumer. The target URI (“.../Eventnotification“) shall contain the call back URI received in the subscription request to notify the generated events to all the subscribed API Consumers. - -##### 6.3.4.3.2 Referenced procedures. - -###### 6.3.4.3.2.1 Notify service availability changes. - -The Notification service API operation illustrated in figure 6.3.4.3.1-1 is based on the Notify service availability changes procedure defined in R1GAP [5]. - -### 6.3.5 Resources - -#### 6.3.5.1 Overview - -This clause defines the resource for the Service events subscription API based on 3GPP TS 29.222 [9]. - -#### 6.3.5.2 Resource: "CAPIF Events Subscriptions" - -This resource is defined in 3GPP TS 29.222 [9], clause 8.3, with the following URI: - -**{apiRoot}/capif-events//{subscriberId}/subscriptions** - -This resource shall support the resource URI variables defined in 3GPP TS 29.222 [9], table 8.3.2.2.2-1. - -##### 6.3.5.2.1 Resource Standard Methods - -###### 6.3.5.2.1.1 POST - -This method shall support the URI query parameters, request data, response data structures and response codes specified in 3GPP TS 29.222 [9], clause 8.3.2.2.3.1. - -##### 6.3.5.2.2 Resource Custom Operations - -None - -#### 6.3.5.3 Resource: "Individual CAPIF Events Subscription" - -This resource is defined in 3GPP TS 29.222 [9], clause 8.3, with the following URI: - -**{apiRoot}/capif-events//{subscriberId}/subscriptions/{subscriptionId}** - -This resource shall support the resource URI variables defined in 3GPP TS 29.222 [9], table 8.3.2.3.2-1. - -##### 6.3.5.3.1 Resource Standard Methods - -###### 6.3.5.3.1.1 DELETE - -This method shall support the URI query parameters, request data, response data structures and response codes specified in 3GPP TS 29.222 [9], clause 8.3.2.3.3.1. - -###### 6.3.5.3.1.2 PUT - -This method shall support the URI query parameters, request data, response data structures and response codes specified in 3GPP TS 29.222 [9], clause 8.3.2.3.3.2. - -###### 6.3.5.3.1.2 PATCH - -This method shall support the URI query parameters, request data, response data structures and response codes specified in 3GPP TS 29.222 [9], clause 8.3.2.3.3.3. - -##### 6.3.5.3.2 Resource Custom Operations - -None. - -### 6.3.6 Custom operations without associated resources. - -None. - -### 6.3.7 Notifications - -#### 6.3.7.1 General - -The delivery of notification shall conform to 3GPP TS 29.222 [9], clause 8.3.3.1. - -#### 6.3.7.2 Event Notification - -##### 6.3.7.2.1 Description - -Event Notifications is used by the API Producer to notify all the subscribed API Consumers. The API Consumers shall subscribe to Event Notifications via the Individual CAPIF Events Subscription resource. - -##### 6.3.7.2.2 Notification definition - -This method shall support the request data structures, URI query parameters and the response data structures as specified in 3GPP TS 29.222 [9], clause 8.3.3.2.2. - -### 6.3.8 Data Model - -#### 6.3.8.1 General - -The application data model is defined in 3GPP TS 29.222 [9], clause 8.3.4. In addition, the adaptations specified in clause B.3 of the present document and the data types listed in 3GPP TS 29.222 [9], clause 7.2, also apply to this API. - -#### 6.3.8.2 Structured data types - -None. - -#### 6.3.8.3 Simple data types and enumerations - -None. - -#### 6.3.8.4 Re-used data types - -The re-used data types are defined in clause B.3. - -#### 6.3.8.5 Service-specific registration information - -None. - -### 6.3.9 Error Handling - -General error responses are defined in 3GPP TS 29.222 [9], clause 7.7. - -## 6.4 Bootstrap API - -### 6.4.1 Introduction - -This API allows the API Consumer to discover the entry points into the Service management and exposure services and the related token endpoints as defined in R1GAP [5]. - -### 6.4.2 API version - -For the Bootstrap API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 0 and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1] for a definition of the version fields). Consequently, the URI path segment shall be set to “v1”. - -### 6.4.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined in clause 5.2. The resource URI variable shall be “bootstrap”. The for each resource shall be set as described in clause 6.4.5. - -Figure 6.4.3-1 shows the overall resource URI structure defined for the bootstrap API. - -![Diagram showing the resource URI structure for the bootstrap API. The base path is {apiRoot}/bootstrap/{apiVersion}. A callout box points to a specific resource path: /bootstrap-info.](cad89c017c9e7c1785bcd104fde4e737_img.jpg) - -``` - - {apiRoot}/bootstrap/{apiVersion} - | - +--- /bootstrap-info - -``` - -Diagram showing the resource URI structure for the bootstrap API. The base path is {apiRoot}/bootstrap/{apiVersion}. A callout box points to a specific resource path: /bootstrap-info. - -**Figure 6.4.3-1: Resource URI structure of the Bootstrap API** - -Table: 6.4.3-1 1 lists the individual resources defined for the API, the applicable HTTP methods, and the associated service operations. - -**Table 6.1.3-1: Resource and methods overview of the Bootstrap API** - -| Resource name | Resource URI | HTTP method | Service Operation | -|----------------|---------------------|-------------|-----------------------------| -| Bootstrap info | .../bootstrap-info/ | GET | Query bootstrap information | - -### 6.4.4 Service Operations - -#### 6.4.4.1 Query bootstrap information - -##### 6.4.4.1.1 Operation definition - -The API Consumer uses this operation to retrieve bootstrap information . - -The operation to query bootstrap information based on HTTP GET. - -``` -@startuml -autonumber -``` - -``` - -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: GET .../bootstrap-info -Producer -->> Consumer: 200 OK (BootstrapInformation) -@enduml - -``` - -![Sequence diagram showing the interaction between an API Consumer and an API Producer. The Consumer sends a GET request for .../bootstrap-info, and the Producer responds with a 200 OK status containing BootstrapInformation.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET .../bootstrap-info - API Producer-->>API Consumer: 2 200 OK (BootstrapInformation) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - -``` - -Sequence diagram showing the interaction between an API Consumer and an API Producer. The Consumer sends a GET request for .../bootstrap-info, and the Producer responds with a 200 OK status containing BootstrapInformation. - -**Figure 6.4.4.1.1-1: Query bootstrap information operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../bootstrap-info). The message content shall be empty. -2. The API Producer shall return the HTTP response. On success, “200 OK“ shall be returned. The message content shall carry the BootstrapInformation. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -##### **6.4.4.1.2 Referenced procedures.** - -###### **6.4.4.1.2.1 Discover bootstrap procedure** - -The Query bootstrap operation illustrated in figure 6.4.4.1.1-1. is based on the Discover bootstrap procedure defined for the Service management and exposure services in R1GAP [5]. - -### 6.4.5 Resources - -#### 6.4.5.1 Overview - -The following clause defines the resources for the Bootstrap API. - -#### 6.4.5.2 Resource: "Bootstrap info" - -##### 6.4.5.2.1 Description - -The resource represents the bootstrap information for service management and exposure services. - -Only the methods defined in clause 6.4.5.2.3 shall be supported by this resource. - -##### 6.4.5.2.2 Resource Definition - -Resource URI: {apiRoot}/bootstrap//bootstrap-info - -The resource URI variables supported by the resource is defined in Table 6.4.5.2.2-1. - -**Table 6.4.5.2.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|------------------| -| apiRoot | See clause 5.2 | -| apiVersion | See clause 6.4.2 | - -##### 6.4.5.2.3 Resource Standard Methods - -###### 6.4.5.2.3.1 GET - -This method shall support the URI query parameters specified in table 6.4.5.2.3.1-1, the request data structure specified in table 6.4.5.2.3.1-2 and the response data structure and response code specified in 6.4.5.2.3.1-3. - -**Table 6.4.5.2.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| N/A | | | | | | - -**Table 6.4.5.2.3.1-2: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|--------------------------------------| -| N/A | | | A GET request has no message content | - -**Table 6.4.5.2.3.1-3: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------------|---|-------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| BootstrapInformation | M | 1 | 200 OK | The bootstrap information has been queried successfully by the rApp and the response contains a BootstrapInformation structure as a representation of the query resource. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -##### 6.4.5.2.4 Resource Custom Operations - -None. - -### 6.4.6 Custom operation without associated resources. - -None. - -### 6.4.7 Notifications - -None. - -### 6.4.8 Data Model - -#### 6.4.8.1 Structured data types - -##### 6.4.8.1.1 Overview - -The following clauses define the structured data types and their attributes to be used by the bootstrap API. - -##### 6.4.8.1.2 Data type: BootstrapInformation - -The BootstrapInformation data type represents entry point information for the Service management and exposure services. It contains the attributes defined in table 6.4.8.1.2-1. - -**Table 6.4.8.1.2-1: Definition of type BootstrapInformation** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-------------------------------|---|-------------|----------------------------| -| apiEndpoints | array(ApiEndpointInformation) | M | 1..N | Information about the API. | - -##### **6.4.8.1.3 Data type: ApiEndpointInformation** - -The ApiEndpointInformation data type represents entry point information for a single API. It contains the attributes defined in table 6.4.8.1.3-1. - -**Table 6.4.8.1.3-1: Definition of type ApiEndpointInformation** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|----------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiName | string | M | 1 | Name of API , as defined in the URI structure as .

The following values shall be supported
“service-apis“ for discovery and
“published-apis“ for service registration. | -| tokenEndPoint | InterfaceDescription | C | 0..1 | InterfaceDescription as defined in clause B.3.5, Token endpoint shall be provided if the API requires authorization over OAuth2.0 | -| apiEndPoint | InterfaceDescription | M | 1 | InterfaceDescription as defined in clause B.3.5, End point of the API | - -#### **6.4.8.2 Simple data types and enumerations** - -None - -#### **6.4.8.3 Re-used data types** - -None - -#### **6.4.8.4 Service-specific registration information** - -None. - -### **6.4.9 Error Handling** - -#### **6.4.9.1 General** - -In addition to the general provisions in clause 5.4.3, the requirements in the following clauses are applicable for Bootstrap API. - -#### **6.4.9.2 Protocol Errors** - -No specific protocol errors are defined in the present document. - -#### **6.4.9.3 Application Errors** - -No additional application errors defined in the present document. - -# 7 Data management and exposure services - -## 7.1 Data registration API - -### 7.1.1 Introduction - -This API enables the API Consumer to register DME type production capabilities based on the data registration service procedure defined in R1GAP [5]. - -### 7.1.2 API version - -For the data registration API as specified in the present document, the MAJOR version field shall be 2, the MINOR version field shall be 0 and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1] for a definition of the version fields). Consequently, the URI path segment shall be set to “v2“. - -The API is under development and consequently the API version shall include the pre-release version “alpha.2“. - -### 7.1.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined in clause 5.2. The resource URI variable shall be “dataregistration“. The for each resource shall be set as described in clause 7.1.5. - -Figure 7.1.3-1 shows the overall resource URI structure defined for the data registration API. - -![A hierarchical diagram showing the resource URI structure for the Data registration API. The root is {apiRoot}/data-registration/. It branches to /production-capabilities, which then branches to /{registrationId}, which finally branches to /data-jobs.](0fa5b60804100c3aead10404f9f226f9_img.jpg) - -``` - -graph TD - Root["{apiRoot}/data-registration/"] --- PC["/production-capabilities"] - PC --- RI["/{registrationId}"] - RI --- DJ["/data-jobs"] - -``` - -A hierarchical diagram showing the resource URI structure for the Data registration API. The root is {apiRoot}/data-registration/. It branches to /production-capabilities, which then branches to /{registrationId}, which finally branches to /data-jobs. - -**Figure 7.1.3-1: Resource URI structure of the Data registration API** - -Table: 7.1.3-1 lists the individual resources defined for the API, the applicable HTTP methods, and the associated service operations. - -**Table 7.1.3-1: Resource and methods overview of the Data registration API** - -| Resource name | Resource URI | HTTP method | Service Operation | -|------------------------------------------------------|--------------------------------------------------------|-------------|---------------------| -| Registered DME type production capabilities | .../production- capabilities | POST | Register DME type | -| Individual registered DME type production capability | .../production-capabilities/{registrationId} | DELETE | Deregister DME type | -| | | PUT | Update DME type | -| | | GET | Query DME type | -| All subscribed data jobs | .../production-capabilities/{registrationId}/data-jobs | GET | Query data jobs | - -### 7.1.4 Service Operations - -#### 7.1.4.1 Register DME type - -##### 7.1.4.1.1 Operation definition - -The API Consumer uses this operation to register DME type production capabilities. - -The operation to register the capability to produce a DME type is based on HTTP POST. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: POST .../production-capabilities (DmeTypeRelatedCapabilities) -Producer -->> Consumer: 201 Created (DmeTypeRelatedCapabilities) -@enduml -``` - -![Sequence diagram showing the Register DME type operation. An API Consumer sends a POST request to an API Producer, and the API Producer responds with a 201 Created status.](05d8710f69c476939295486ab1440350_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 POST .../production-capabilities (DmeTypeRelatedCapabilities) - API Producer-->>API Consumer: 2 201 Created (DmeTypeRelatedCapabilities) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram showing the Register DME type operation. An API Consumer sends a POST request to an API Producer, and the API Producer responds with a 201 Created status. - -**Figure 7.1.4.1.1 -1: Register DME type operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP POST request to the API Producer. The target URI shall identify the resource (.../production-capabilities) under which the new registration is requested to be created. The message content shall carry a DmeTypeRelatedCapabilities structure. -2. The API Producer shall generate the registration identifier and construct the URI for the created resource. The API Producer shall return the HTTP POST response. On success, “201 Created“ shall be returned. The “Location“ header shall be present and shall carry the URI of the new registration resource. The message content shall carry a DmeTypeRelatedCapabilities structure that represents the new resource. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -##### 7.1.4.1.2 Referenced procedures. - -###### 7.1.4.1.2.1 Register DME type procedure - -The Register DME type operation illustrated in figure 7.1.4.1.1-1. is based on the Register DME type procedure defined for the Data registration service in R1GAP [5]. - -#### 7.1.4.2 Deregister DME type. - -##### 7.1.4.2.1 Operation definition - -The API Consumer uses this operation to deregister DME type production capabilities. - -The operation to deregister the capability to produce a DME type is based on HTTP DELETE. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: DELETE .../production-capabilities/{registrationId} -Producer -->> Consumer: 204 No Content -@enduml -``` - -![Sequence diagram for Deregister DME type operation. It shows an API Consumer sending a DELETE request to an API Producer, and the API Producer responding with a 204 No Content status.](315bdbeafb39026e19b77c26b19d9d1f_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - API Consumer->>API Producer: 1 DELETE .../production-capabilities/{registrationId} - Note right of API Producer: API Producer - API Producer-->>API Consumer: 2 204 No Content - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram for Deregister DME type operation. It shows an API Consumer sending a DELETE request to an API Producer, and the API Producer responding with a 204 No Content status. - -**Figure 7.1.4.2.1-1: Deregister DME type operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP DELETE request to the API Producer. The target URI shall identify the resource to be deleted (.../production-capabilities/{registrationId}). -2. The API Producer shall return the HTTP DELETE response. On success, “204 No Content“ shall be returned and the response message content shall be empty. On failure, the appropriate error code shall be returned, and the message response content may contain additional error information. - -##### 7.1.4.2.2 Referenced procedures. - -###### 7.1.4.2.2.1 Deregister DME type procedure. - -The Deregister DME type operation illustrated in figure 7.1.4.2.1-1 is based on the Deregister DME type procedure defined for the Data registration service in R1GAP [5]. - -#### 7.1.4.3 Update DME type - -##### 7.1.4.3.1 Operation definition - -The API Consumer uses this operation to update the registration of production capabilities related to a DME type. - -The operation to update the registration of production capability related to a DME type is based on HTTP PUT. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: PUT .../production-capabilities/{registrationId} -(DmeTypeRelatedCapabilities) -Producer -->> Consumer: 200 OK (DmeTypeRelatedCapabilities) -@enduml -``` - -![Sequence diagram for Update DME type operation. It shows an API Consumer sending a PUT request to an API Producer, and the API Producer responding with a 200 OK.](145d00f59802048185303f15937ea65c_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - API Consumer->>API Producer: 1 PUT .../production-capabilities/{registrationId} (DmeTypeRelatedCapabilities) - API Producer-->>API Consumer: 2 200 OK (DmeTypeRelatedCapabilities) - -``` - -Sequence diagram for Update DME type operation. It shows an API Consumer sending a PUT request to an API Producer, and the API Producer responding with a 200 OK. - -**Figure 7.1.4.3.1 -1: Update DME type operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP PUT request to the API Producer. The target URI shall identify the resource (.../production-capabilities/{registrationId}). The message content shall carry an updated DmeTypeRelatedCapabilities structure. The API producer shall process the HTTP PUT message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP response. On success, “200 OK“ shall be returned. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -##### **7.1.4.3.2 Referenced procedures.** - -###### **7.1.4.3.2.1 Update DME type procedure** - -The Update DME type operation illustrated in figure 7.1.4.4.1-1. is based on the Update DME type procedure defined for the Data registration service in R1GAP [5]. - -#### **7.1.4.4 Query DME type** - -##### **7.1.4.4.1 Operation definition** - -The API Consumer uses this operation to query the registration of production capability information on a specific DME type that it has previously registered. - -The operation to query the registration of production capability is based on HTTP GET. - -``` - -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer ->> Producer: GET .../production-capabilities/{registrationId} -Producer -->> Consumer: 200 OK (DmeTypeRelatedCapabilities) -@enduml - -``` - -![Sequence diagram for Query DME type operation. It shows an API Consumer sending a GET request to an API Producer, and the API Producer responding with a 200 OK.](a9bd36d25444d896e8d6941ff59d8f2d_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - API Consumer->>API Producer: 1 GET .../production-capabilities/{registrationId} - API Producer-->>API Consumer: 2 200 OK (DmeTypeRelatedCapabilities) - -``` - -Sequence diagram for Query DME type operation. It shows an API Consumer sending a GET request to an API Producer, and the API Producer responding with a 200 OK. - -**Figure 7.1.4.4.1 -1: Query DME type operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../production-capabilities/{registrationId}). The message content shall be empty. The API producer shall process the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP response. On success, “200 OK“ shall be returned. The message content shall carry the queried production capability information. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -##### **7.1.4.4.2 Referenced procedures.** - -###### **7.1.4.4.2.1 Query DME type procedure** - -The Query DME type operation illustrated in figure 7.1.4.4.1-1. is based on the Query DME type procedure defined for the Data registration service in R1GAP [5]. - -### 7.1.4 Service Operations - -#### 7.1.4.5 Query data jobs - -##### 7.1.4.5.1 Operation definition - -The API Consumer uses this operation to query all the data jobs information associated with a specific DME type that it has previously registered. - -The operation to Query data jobs is based on HTTP GET. - -``` - -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer ->> Producer: GET .../production-capabilities/{registrationId}/data-jobs -Producer -->> Consumer: 200 OK (array(DataJobInfo)) -@enduml - -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for the 'Query All data job operation'. The Consumer sends a GET request to the Producer, and the Producer responds with a 200 OK containing an array of DataJobInfo.](1b2ad37940c441d410002c05ff71c7c5_img.jpg) - -``` - -sequenceDiagram - autonumber - participant Consumer as API Consumer - participant Producer as API Producer - Consumer->>Producer: GET .../production-capabilities/{registrationId}/data-jobs - Producer-->>Consumer: 200 OK (array(DataJobInfo)) - -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for the 'Query All data job operation'. The Consumer sends a GET request to the Producer, and the Producer responds with a 200 OK containing an array of DataJobInfo. - -**Figure 7.1.4.5.1-1: Query All data job operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../production-capabilities/{registrationId}/data-jobs). The message content shall be empty. The API producer shall process the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP response. On success, “200 OK“ shall be returned. The message content shall carry an array of DataJobInfo. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -##### 7.1.4.5.2 Referenced procedures. - -###### 7.1.4.5.2.1 Query data subscription information procedure - -The Query data jobs operation illustrated in figure 7.1.4.5.1-1. is based on the Query data subscription information procedure defined for the Data registration service in R1GAP [5]. - -### 7.1.5 Resources - -#### 7.1.5.1 Overview - -The following clause defines the resources for the Data registration API. - -#### 7.1.5.2 Resource: "Registered DME type production capabilities" - -##### 7.1.5.2.1 Description - -The resource represents the registered capabilities of an API Consumer to produce DME types. - -Only the methods defined in clause 7.1.5.2.3 shall be supported by this resource. - -##### 7.1.5.2.2 Resource Definition - -Resource URI: {apiRoot}/data-registration//production-capabilities - -The resource URI variables supported by the resource are defined in Table 7.1.5.2.2-1. - -**Table 7.1.5.2.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|------------------| -| apiRoot | See clause 5.2 | -| apiVersion | See clause 7.1.2 | - -##### 7.1.5.2.3 Resource Standard Methods - -###### 7.1.5.2.3.1 POST - -This method shall support the request data structure specified in the table 7.1.5.2.3.1-1 and the response data structure and response code specified in the table 7.1.5.2.3.1-2, and the HTTP headers specified in table 7.1.5.2.3.1-3. - -**Table 7.1.5.2.3.1-1: Data structures supported by the POST request body on this resource.** - -| Data Type | P | Cardinality | Description | -|----------------------------|---|-------------|------------------------------------------------------------------| -| DmeTypeRelatedCapabilities | M | 1 | Registered capabilities of a Data Producer related to a DME type | - -**Table 7.1.5.2.3.1-2: Data structures supported by the POST response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------------------|---|-------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| DmeTypeRelatedCapabilities | M | 1 | 201 Created | The operation was successful, and the message content of the POST response contains a DmeTypeProdCapRegistration structure as a representation of the created resource. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -**Table 7.1.5.2.3.1-3: Headers supported by the 201 Response Code on this resource.** - -| Name | Data type | P | Cardinality | Description | -|----------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Location | string | M | 1 | Contains the URI of the newly created “Individual registered DME type production capability” resource, as defined in clause 7.1.5.3, with the registrationId in the URI. | - -##### **7.1.5.2.4 Resource Custom Operations** - -None - -#### **7.1.5.3 Resource: "Individual registered DME type production capability"** - -##### **7.1.5.3.1 Description** - -The resource represents an individual registered DME type production capability. - -Only the methods defined in clause 7.1.5.3.3 shall be supported by this resource. - -##### **7.1.5.3.2 Resource Definition** - -Resource URI: {apiRoot}/data-registrations//production-capabilities/{registrationId} - -The resource URI variables supported by the resource are defined in Table 7.1.5.3.2-1. - -**Table 7.1.5.3.2-1: Resource URI variables for the resource.** - -| Name | Definition | -|----------------|----------------------------------------------------------------------| -| apiRoot | See clause 5.2 | -| apiVersion | See clause 7.1.2 | -| registrationId | The related DME type production capabilities registration identifier | - -##### **7.1.5.3.3 Resource Standard Methods** - -###### **7.1.5.3.3.1 DELETE** - -This method shall support the request data structure specified in table 7.1.5.3.3.1-1 and the response data structure and response code specified in 7.1.5.3.3.1-2. - -**Table 7.1.5.3.3.1-1: Data structures supported by the DELETE request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|-----------------------------------------| -| N/A | | | A DELETE request has no message content | - -**Table 7.1.5.3.3.1-2: Data structures supported by the DELETE response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| -| N/A | | | 204 No Content | The DME type production capability registration associated with the registrationId has been deleted successfully. The message content shall be empty. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -# 7.1.5.3.3.2 PUT - -This method shall support the request data structure specified in the table 7.1.5.3.3.2-1 and the response data structure and response code specified in the table 7.1.5.3.3.2-2. - -**Table 7.1.5.3.3.2-1: Data structures supported by the PUT request body on this resource.** - -| Data Type | P | Cardinality | Description | -|----------------------------|---|-------------|----------------------------------------------------| -| DmeTypeRelatedCapabilities | M | 1 | Updated DME type production capability information | - -**Table 7.1.5.2.3.2-2: Data structures supported by the PUT response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------------------|---|-------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| DmeTypeRelatedCapabilities | M | 1 | 200 OK | The DME type production capability registration associated with the registrationId has been updated successfully and the response contain the DmeTypeProdCapRegistration as a representation of the updated resource. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -#### 7.1.5.3.3.3 GET - -This method shall support the request data structure specified in the table 7.1.5.3.3.3-1 and the response data structure and response code specified in the table 7.1.5.3.3.3-2. - -**Table 7.1.5.3.3.3-1: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|--------------------------------------| -| N/A | | | A GET request has no message content | - -**Table 7.1.5.2.3.3-2: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------------------|---|-------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| DmeTypeRelatedCapabilities | M | 1 | 200 OK | The DME type production capability registration associated with the registrationId has been queried successfully and the response contain the DmeTypeProdCapRegistration as a representation of the query resource. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -**7.1.5.3.4 Resource Custom Operations** - -None. - -**7.1.5.4 Resource: "All subscribed data jobs"** - -**7.1.5.4.1 Description** - -The resource represents all data job information associated with DME type registration identifier. - -Only the methods defined in clause 7.1.5.4.3 shall be supported by this resource. - -**7.1.5.4.2 Resource Definition** - -Resource URI: {apiRoot}/data-registrations//production-capabilities/{registrationId}/data-jobs - The resource URI variables supported by the resource are defined in Table 7.1.5.4.2-1. - -**Table 7.1.5.4.2-1: Resource URI variables for the resource.** - -| Name | Definition | -|----------------|-----------------------------------------------------------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 7.1.2. | -| registrationId | The related DME type production capabilities registration identifier. | - -**7.1.5.4.3 Resource Standard Methods** - -**7.1.5.4.3.1 GET** - -This method shall support the request data structure specified in the table 7.1.5.4.3.1-1 and the response data structure and response code specified in the table 7.1.5.4.3.1-2. - -**Table 7.1.5.4.3.1-1: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|---------------------------------------| -| N/A | | | A GET request has no message content. | - -**Table 7.1.5.4.3.1-2: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|--------------------|---|-------------|----------------|--------------------------------------------------------------------------------------------| -| array(DataJobInfo) | M | 0..N | 200 OK | Provides information for the data job as per clause 7.3.8.1.2 | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -**7.1.5.4.4 Resource Custom Operations** - -None. - -**7.1.6 Custom operation without associated resources.** - -None. - -**7.1.7 Notifications** - -None. - -**7.1.8 Data Model** - -**7.1.8.1 Structured data types** - -**7.1.8.1.1 Overview** - -The following clauses define the structured data types and their attributes to be used by the service API. - -**7.1.8.1.2 Data type: DmeTypeRelatedCapabilities** - -The DmeTypeRelatedCapabilities data type represents capabilities of a data provider entity (such as Data Producer, SME functions) related to providing data instances of a DME type for collection or consumption. It contains the attributes defined in table 7.1.8.1.2-1. - -**Table 7.1.8.1.2-1: Definition of type DmeTypeRelatedCapabilities.** - -| Attribute Name | Data type | P | Cardinality | Description | -|--------------------|-------------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| dmeTypeDefinition | DmeTypeDefinition | M | 1 | Information of the DME type. | -| dataAccessEndpoint | InterfaceDescription | O | 0..1 | Endpoint to which to send the data request or data subscription for data instances of this DME type.

This attribute shall be provided in data registration requests and responses related to data registration.

It may be provided in data discovery responses. If this information is not provided, the data access endpoint can be discovered by means outside the scope of the of the DME services. | -| dataDeliveryMode | array(DataDeliveryMode) | M | 1..N | Supported modes for data delivery for this DME type, i.e. one time (data request) or continuous (data subscription) or both. | -| constraints | object | O | 0..1 | When this data structure is used for registration, this attribute represents producer constraints related to the DME type based on the dataProductionSchema.

When this data structure is used for discovery, this attribute represents constraints applicable to the consumption of data instances of this DME type based on the dataProductionSchema | - -### 7.1.8.1.3 Data type: DmeTypeDefinition - -The DmeTypeDefinition data type represents information about a DME type. It contains the attributes defined in table 7.1.8.1.3-1. - -**Table 7.1.8.1.3-1: Definition of type DmeTypeDefinition.** - -| Attribute Name | Data type | P | Cardinality | Description | -|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| dmeTypeId | DmeTypeIdStruct | M | 1 | The identifier of the DME type being registered. | -| metadata | Metadata | M | 1 | Metadata that can be used in discovering the DME type. | -| dataProductionSchema | object | O | 0..1 | Schema that defines the information necessary to formulate a data request or data subscription. If this attribute is not present, the schema is assumed to be known from the DME type definition that is referenced by dmeTypeId (see note). | -| dataDeliverySchemas | array (DeliverySchema) | M | 1.. N | List of delivery schemas supported by the producer for the DME type being registered (see note). | -| dataDeliveryMechanisms | array (DataDeliveryMechanism) | M | 1.. N | see clause B.4.4.2 | -| NOTE: The schemas for data production and data delivery are DME type specific and are not defined in the present version of the document. | | | | | - -### 7.1.8.1.4 Data type: Metadata - -The Metadata data type contains the attributes defined in table 7.1.8.1.4-1 and the set of metadata attributes may be extended by deployments. - -**Table 7.1.8.1.4-1: Definition of type Metadata.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|---------------|---|-------------|---------------------------------------------------------| -| dataCategory | array(string) | M | 1.. N | Defines the category of the DME type e.g., PM counters. | -| rat | array(string) | O | 0.. N | Defines the radio access technology e.g., 5G. | - -#### 7.1.8.1.5 Data type: DeliverySchema - -The DeliverySchema data type contains the attributes defined in table 7.1.8.1.5-1. - -**Table 7.1.8.1.5-1: Definition of type DeliverySchema.** - -| Attribute Name | Data type | P | Cardinality | Description | -|------------------|-------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| type | SchemaTypes | M | 1 | Type of the schema. | -| deliverySchemaId | string | M | 1 | A Data Producer may support one or more delivery schemas and for each supported schema type a delivery schema identifier is assigned. A Data Consumer uses this attribute while creating a data job and request to deliver the data using specific schema type which is identified by this attribute. | -| schema | string | O | 0..1 | The schema serialized to string. If this attribute is not present, the schema is assumed to be known from the DME type definition that is referenced by the DME type identifier. | - -#### 7.1.8.2 Simple data types and enumerations - -##### 7.1.8.2.1 Introduction - -This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. - -##### 7.1.8.2.2 Simple data types - -No simple data types are defined in this version of the specification. - -##### 7.1.8.2.3 Enumeration - -###### 7.1.8.2.3.1 Enumeration: SchemaTypes - -**Table 7.1.8.3.3.1-1: Enumeration SchemaTypes.** - -| Enumeration value | Description | -|-------------------|--------------------------------------------------| -| JSON_SCHEMA | Following JSON Schema 2020-12 [14]. | -| XML_SCHEMA | Following XML Schema [16], [17], [18] and [i.1]. | -| PROTOBUF_SCHEMA | Following PROTOBUF Schema [27]. | -| AVRO_SCHEMA | Following AVRO Schema [28]. | - -#### 7.1.8.3 Re-used data types - -None. - -### 7.1.8.4 Service-specific registration information - -None. - -## 7.1.9 Error Handling - -### 7.1.9.1 General - -In addition to the general provisions in clause 5.4.3, the requirements in the following clauses are applicable for the Data Registration API. - -### 7.1.9.2 Protocol Errors - -No specific protocol errors are defined in the present document. - -### 7.1.9.3 Application Errors - -No additional application errors defined in the present document. - -## 7.2 Data discovery API - -### 7.2.1 Introduction - -This API enables the API Consumer to discover the available DME types based on the data discovery service procedures defined in R1GAP [5]. - -### 7.2.2 API version - -For the data discovery API as specified in the present document, the MAJOR version field shall be 2, the MINOR version field shall be 0 and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1] for a definition of the version fields). Consequently, the URI path segment shall be set to “v2“. - -### 7.2.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined in clause 5.2. The resource URI variable shall be “datadiscovery“. The for each resource shall be set as described in clause 7.2.5. - -Figure 7.2.3-1 shows the overall resource URI structure defined for the data discovery API. - -![A hierarchical diagram showing the resource URI structure for the Data discovery API. The root is {apiRoot}/data-discovery/. A line descends from this root to a box containing /dme-types. From this box, another line descends to a box containing /{dmeTypeId}.](81a736eb35b4bda9584394c61ef44aec_img.jpg) - -``` - -graph TD - Root["{apiRoot}/data-discovery/"] --> DmeTypes["/dme-types"] - DmeTypes --> DmeTypeId["/{dmeTypeId}"] - -``` - -A hierarchical diagram showing the resource URI structure for the Data discovery API. The root is {apiRoot}/data-discovery/. A line descends from this root to a box containing /dme-types. From this box, another line descends to a box containing /{dmeTypeId}. - -Figure 7.2.3-1: Resource URI structure of the Data discovery API - -Table 7.2.3-1 lists the individual resources defined for the API, the applicable HTTP methods, and the associated service operations. - -**Table 7.2.3-1: Resources and methods overview of the Data discovery API** - -| Resource name | Resource URI | HTTP method | Service Operation | -|----------------------|---------------------------|-------------|------------------------------------------| -| All DME types | .../dme-types | GET | Discover DME types | -| Individual DME types | .../dme-types/{dmeTypeId} | GET | Query capabilities related to a DME type | - -## 7.2.4 Service operations - -### 7.2.4.1 Discover DME types. - -#### 7.2.4.1.1 Operation definition - -The API Consumer uses this operation to discover the available DME types. - -The operation to discover the DME types is based on HTTP GET. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer ->> Producer: GET .../dme-types -Producer -->> Consumer: 200 OK (array(DmeTypeRelatedCapabilities)) -@enduml -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for the Discover DME types operation. The Consumer sends a GET request to the Producer, and the Producer responds with a 200 OK status and an array of DmeTypeRelatedCapabilities.](659a041a7997f9eea79f4e2f3ba265a5_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET .../dme-types - API Producer-->>API Consumer: 2 200 OK (array(DmeTypeRelatedCapabilities)) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for the Discover DME types operation. The Consumer sends a GET request to the Producer, and the Producer responds with a 200 OK status and an array of DmeTypeRelatedCapabilities. - -**Figure 7.2.4.1.1 -1: Discover DME types operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../dme-types) and may also contain query parameters to discover the available DME types. -2. The API Producer shall return the HTTP GET response. On success, “200 OK“ shall be returned and the message content shall carry an array of Dme type related capabilities. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 7.2.4.1.2 Referenced procedures. - -##### 7.2.4.1.2.1 Discover DME types procedure. - -The Discover DME types operation illustrated in figure 7.2.4.1.1-1 is based on the Discover DME types procedure defined for the Data discovery service in R1GAP [5]. - -## 7.2.4.2 Query DME type information - -### 7.2.4.2.1 Operation definition - -The API Consumer uses this operation to query for information about a specific DME type identified by a DME type identifier. - -The operation to query for information about a specific DME type is based on HTTP GET. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: GET .../dme-types/{dmeTypeId} -Producer -->> Consumer: 200 OK (DmeTypeRelatedCapabilities) -@enduml -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for the Query DME type information operation. The API Consumer sends a GET request to the API Producer, and the API Producer responds with a 200 OK status and DmeTypeRelatedCapabilities.](1316d63eca7b84e13c27f55f0027b7b5_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET .../dme-types/{dmeTypeId} - API Producer-->>API Consumer: 2 200 OK (DmeTypeRelatedCapabilities) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for the Query DME type information operation. The API Consumer sends a GET request to the API Producer, and the API Producer responds with a 200 OK status and DmeTypeRelatedCapabilities. - -Figure 7.2.4.2.1-2: Query DME type information operation - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../dme-types/{dmeTypeId}) and the message content shall be empty. -2. The API Producer shall return the HTTP GET response. On success, “200 OK“ shall be returned and the message content shall carry capability information related to the DME type identified by {dmeTypeId}. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -### 7.2.4.2.2 Referenced procedures. - -#### 7.2.4.2.2.1 Query DME type information procedure - -The Query DME type operation illustrated in figure 7.2.4.2.1-1 is based on the Query DME type information procedure defined for the Data discovery service in R1GAP [5]. - -## 7.2.5 Resources - -### 7.2.5.1 Overview - -The following clause defines the resources for the Data discovery API. - -### 7.2.5.2 Resource: "All DME types" - -#### 7.2.5.2.1 Description - -The resource represents the available DME types. Only the methods defined in clause 7.2.5.2.3 shall be supported by this resource. - -## 7.2.5.2.2 Resource Definition - -Resource URI: {apiRoot}/data-discovery//dme-types - -The resource URI variables supported by the resource are defined in Table 7.2.5.2.2-1. - -**Table 7.2.5.2.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|-------------------| -| apiRoot | See clause 5.2 . | -| apiVersion | See clause 7.2.2. | - -## 7.2.5.2.3 Resource Standard Methods - -### 7.2.5.2.3.1 GET - -This method shall support the URI query parameters specified in table 7.2.5.2.3.1-1, the request data structure specified in the table 7.2.5.2.3.1-2 and the response data structure and response code specified in the table 7.2.5.2.3.1-3. - -**Table 7.2.5.2.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | Applicability | -|--------------------|---------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------|---------------| -| identity-namespace | string | O | 0..1 | Identity namespace, which shall match the “namespace” part of the “dmeTypeId” attribute. (See NOTE1) | | -| identity-name | string | O | 0..1 | Identity name, which shall match the “name” part of the “dmeTypeId” attribute. (See NOTE1). | | -| data-category | array(string) | O | 0..N | Set of data category entries, all of which shall match entries of the “dataCategory” attribute. (See NOTE1 and NOTE 2). | | - -NOTE 1: If multiple query parameters are provided these shall be combined with AND when evaluating the query. - -NOTE 2: The encoding of query parameter for array of string shall follow the guideline defined in 3GPP TS 29.501 [1] clause 5.3.13. - -**Table 7.2.5.2.3.1-2: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|--------------------------------------------------------------| -| N/A | | | There is no object in the message content of the GET request | - -**Table 7.2.5.2.3.1-3: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|------------------------------------|---|-------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------| -| array (DmeTypeRelatedCapabilities) | M | 0.. N | 200 OK | The operation was successful.

The message content of the GET response carries an array of DmeTypeRelatedCapabilities structures. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -## 7.2.5.2.4 Resource Custom Operations - -None. - -### 7.2.5.3 Resource: "Individual DME type" - -#### 7.2.5.3.1 Description - -The resource represents a DME type. - -#### 7.2.5.3.2 Resource Definition - -Resource URI: {apiRoot}/data-discovery//dme-types/{dmeTypeId} - -The resource URI variables supported by the resource are defined in Table 7.2.5.3.2-1. - -**Table 7.2.5.3.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|--------------------------------------------| -| apiRoot | See clause 5.2 | -| apiVersion | See clause 7.2.2 | -| dmeTypeId | DME type identifier identifying a DME type | - -#### 7.2.5.3.3 Resource Standard Methods - -##### 7.2.5.3.3.1 GET - -This method shall support the URI query parameters specified in table 7.2.5.3.3.1-1, the request data structure specified in table 7.2.5.3.3.1-2 and the response data structure and response code specified in 7.2.5.3.3.1-3. - -**Table 7.2.5.3.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| N/A | | | | | | - -**Table 7.2.5.3.3.1-2: Data structures supported by the GET request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|------------------------------------------------| -| N/A | | | The message content of a GET request is empty. | - -**Table 7.2.5.3.3.1-3: Data structures supported by the GET response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------------------|---|-------------|----------------|--------------------------------------------------------------------------------------------------| -| DmeTypeRelatedCapabilities | M | 1 | 200 OK | The operation was successful.

The message content a DmeTypeRelatedCapabilities structure. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -#### 7.2.5.3.4 Resource Custom Operations - -None. - -### 7.2.6 Custom operation without associated resources. - -None. - -## 7.2.7 Notifications - -None. - -## 7.2.8 Data Model - -### 7.2.8.1 Structured data types - -#### 7.2.8.1.1 Overview - -The following clause defines the structured data types and their attributes to be used by the service API. - -For this service API, no structured data types are defined in the present document. - -### 7.2.8.2 Simple data types and enumerations - -#### 7.2.8.2.1 Introduction - -The following clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. - -#### 7.2.8.2.2 Simple data types - -For this service API, no simple data types are defined in the present document. - -#### 7.2.8.2.3 Enumerations - -For this service API, no enumerations are defined in the present document. - -### 7.2.8.3 Re-used data types - -None. - -### 7.2.8.4 Service-specific registration information - -None. - -## 7.2.9 Error Handling - -### 7.2.9.1 General - -In addition to the general provisions in clause 5.4.3, the requirements in the following clauses are applicable for the Data Discovery API. - -### 7.2.9.2 Protocol Errors - -No specific protocol errors are defined in the present document. - -### 7.2.9.3 Application Errors - -No additional application errors defined in the present document. - -## 7.3 Data access API - -### 7.3.1 Introduction - -This API enables the API Consumer to request or subscribe data instances based on the Data request service and Data subscription service procedures defined in R1GAP [5]. The API definition applies to both scenarios when rApp is the Service Consumer and when DME is the Service Consumer, respectively. - -### 7.3.2 API version - -For the Data access API as specified in the present document, the MAJOR version field shall be 2, the MINOR version field shall be 0 and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1] for a definition of the version fields). Consequently, the URI path segment shall be set to “v2”. - -The API is under development and consequently the API version shall include the pre-release version “alpha.3”. - -### 7.3.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined in clause 5.2. The resource URI variable shall be “data-access”. The for each resource shall be set as described in clause 7.3.5. - -Figure 7.3.3-1 shows the overall resource URI structure defined for the Data access API. - -![A hierarchical diagram showing the resource URI structure for the Data access API. The root is {apiRoot}/data-access//, which branches to /data-jobs. /data-jobs branches to /{dataJobId}, which in turn branches to /status.](a548c5381cebd2650c5edb725b19f795_img.jpg) - -``` - -graph TD - Root["{apiRoot}/data-access//"] --- Jobs["/data-jobs"] - Jobs --- JobId["/{dataJobId}"] - JobId --- Status["/status"] - -``` - -A hierarchical diagram showing the resource URI structure for the Data access API. The root is {apiRoot}/data-access//, which branches to /data-jobs. /data-jobs branches to /{dataJobId}, which in turn branches to /status. - -**Figure 7.3.3-1: Resource URI structure of the Data access API** - -Table 7.3.3-1 lists the individual resources defined for the API, the applicable HTTP methods, and the associated service operations. - -**Table 7.3.3-1: Resources and methods overview of the data access API** - -| Resource name | Resource URI | HTTP method | Service Operation | -|----------------------------|----------------------------------|-------------|-------------------------------| -| All data jobs | .../data-jobs | POST | Create an individual data job | -| | | GET | Query data job identifiers | -| Individual data job | .../data-jobs/{dataJobId} | DELETE | Cancel data job | -| | | PUT | Update data job | -| | | GET | Query data job | -| Individual data job status | .../data-jobs/{dataJobId}/status | GET | Query data Job status | - -### 7.3.4 Service Operations - -#### 7.3.4.1 Create data job - -##### 7.3.4.1.1 Operation definition - -The API Consumer uses Create data job operation to create the job for data request or subscription. A data job can be either for data request or data subscription. - -NOTE: An API Producer supporting the Data access API shall support at least one type of the services, data request (one time delivery mode) or data subscription (continuous delivery mode). The mean for communicating the service support capabilities with API Consumers is not specified in this version of the specification. - -The operations are based on HTTP POST. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: POST .../data-jobs (DataJobInfo) -Producer -->> Consumer: 201 Created (DataJobInfo) -@enduml -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for the 'Create data job' operation. The Consumer sends a POST request to the Producer, and the Producer responds with a 201 Created status.](f5d2a88925807080157c7cfb1d41cf0b_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 POST .../data-jobs (DataJobInfo) - API Consumer->>API Producer: 1 POST .../data-jobs (DataJobInfo) - Note right of API Producer: 2 201 Created (DataJobInfo) - API Producer-->>API Consumer: 2 201 Created (DataJobInfo) -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for the 'Create data job' operation. The Consumer sends a POST request to the Producer, and the Producer responds with a 201 Created status. - -**Figure 7.3.4.1.1-1: Create data job operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP POST request to the API Producer. The target URI shall identify the resource (.../data-jobs) under which the new data job is to be created. The message content shall carry a DataJobInfo. -2. The API Producer shall return the HTTP POST response. On success, “201 Created“ shall be returned. The Location header shall be present and shall carry the URI of the new data job resource with dataJobId assigned by the service producer. The message content shall carry a DataJobInfo representing the created data job. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -### 7.3.4.1.2 Referenced procedures - -#### 7.3.4.1.2.1 Request data procedure - -The Create data job operation illustrated in figure 7.3.4.1.1-1 is based on the Request data procedure defined for the Data request service in R1GAP [5]. - -#### 7.3.4.1.2.2 Subscribe data procedure - -The Create data job operation illustrated in figure 7.3.4.1.1-1 is based on the Subscribe data procedure defined for the Data subscription service in R1GAP [5]. - -### 7.3.4.2 Cancel data job - -#### 7.3.4.2.1 Operation definition - -The API Consumer uses Cancel data job operation to cancel a data job. - -The operations are based on HTTP DELETE. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: DELETE .../data-jobs/{dataJobId} -Producer -->> Consumer: 204 No Content -@enduml -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for the Cancel data job operation. The API Consumer sends a DELETE request to the API Producer, and the API Producer responds with a 204 No Content status.](86692d82da6655813b5acf58a767a38c_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - API Consumer->>API Producer: 1 DELETE .../data-jobs/{dataJobId} - Note right of API Producer: API Producer - API Producer-->>API Consumer: 2 204 No Content -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for the Cancel data job operation. The API Consumer sends a DELETE request to the API Producer, and the API Producer responds with a 204 No Content status. - -Figure 7.3.4.2.1-3: Cancel data job operation. - -The service operation is as follows: - -1. The API Consumer shall send an HTTP DELETE request to API Producer. The target URI shall identify the resource (.../data-jobs/{dataJobId}). -2. The API Producer shall return the HTTP DELETE response. On success, “204 No Content“ shall be returned. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -#### 7.3.4.2.2 Referenced procedures - -##### 7.3.4.2.2.1 Cancel data request procedure - -The Cancel data job operation illustrated in figure 7.3.4.2.1-1 is based on the cancel data request procedure defined for the Data request service in R1GAP [5]. - -##### 7.3.4.2.2.2 Unsubscribe data procedure - -The Cancel data job operation illustrated in figure 7.3.4.2.1-1 is based on the Unsubscribe data procedure defined for the Data subscription service in R1GAP [5]. - -### 7.3.4.3 Notify data availability - -#### 7.3.4.3.1 Operation definition - -The API Producer uses this operation to notify data availability related to a data subscription. - -The operation is based on HTTP POST. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Producer -->> Consumer: POST {dataAvailabilityNotificationUri} -(Notification(DataAvailabilityNotification)) -Consumer -->> Producer : 204 No Content -@enduml -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for the Notify data availability operation. The API Producer sends a POST request to the API Consumer, and the API Consumer responds with a 204 No Content status.](3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Producer->>API Consumer: 1 POST {dataAvailabilityNotificationUri} (Notification(DataAvailabilityNotification)) - API Consumer-->>API Producer: 2 204 No Content - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for the Notify data availability operation. The API Producer sends a POST request to the API Consumer, and the API Consumer responds with a 204 No Content status. - -Figure 7.3.4.3.1-4: Notify data availability operation. - -The service operation is as follows: - -1. The API Producer shall send an HTTP POST request to API Consumer. The target URI (dataAvailabilityNotificationUri) identifies the address where to send the notifications. The message content shall carry a Notification message that includes a DataAvailabilityNotification payload. -2. The API Consumer shall return the HTTP POST response. On success, “204 No Content“ shall be returned. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -#### 7.3.4.3.2 Referenced procedures - -##### 7.3.4.3.2.1 Notify data availability procedure - -The Notify data availability operation illustrated in figure 7.3.4.3.1-1 is based on the Notify data availability procedure defined for the Data subscription service in R1GAP [5]. - -### 7.3.4.4 Update data job - -#### 7.3.4.4.1 Operation definition - -The API Consumer uses this operation to update the created job for data subscription. - -The operation to update a data job is based on HTTP PUT. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: PUT ...../data-jobs/{dataJobId} (DataJobInfo) -Producer -->> Consumer: 200 OK (DataJobInfo) -@enduml -``` - -![Sequence diagram for Update data job operation. It shows an API Consumer sending a PUT request to an API Producer, and the API Producer responding with a 200 OK status.](675af5bb2357ce5b510e613d04f66bdc_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note over API Consumer: API Consumer - Note over API Producer: API Producer - API Consumer->>API Producer: 1 PUT /data-jobs/{dataJobId} (DataJobInfo) - API Producer-->>API Consumer: 2 200 OK (DataJobInfo) - Note over API Consumer: API Consumer - Note over API Producer: API Producer - -``` - -Sequence diagram for Update data job operation. It shows an API Consumer sending a PUT request to an API Producer, and the API Producer responding with a 200 OK status. - -**Figure 7.3.4.4.1 -1: Update data job operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP PUT request to the API Producer. The target URI shall identify the resource (.../data-jobs/{dataJobId}). The message content shall carry an update DataJobInfo structure. The API Producer shall process the HTTP PUT message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP response. On success, “200 OK“ shall be returned. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. -3. The API Producer shall reject the update data job with “405 Method Not Allowed“ if the dataJobId in the target URI is associated with delivery mode “ONE\_TIME“. - -NOTE: Updating the Data Job can introduce discontinuities in the produced data that are specific to the DME type and/or Data Producer. - -**7.3.4.4.2 Referenced procedures** - -**7.3.4.3.2.1 Update data job procedure** - -The Update data job operation illustrated in figure 7.3.4.4.1-1. is based on the Update data subscription procedure defined for the Data subscription service in R1GAP [5]. - -**7.3.4.5 Query data job** - -**7.3.4.5.1 Operation definition** - -The API Consumer uses this operation to query the created job. - -The operation to query the data job is based on HTTP GET. - -``` - -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer ->> Producer: GET /data-jobs/{dataJobId} -Producer -->> Consumer: 200 OK (DataJobInfo) -@enduml - -``` - -![Sequence diagram for Query data job operation. It shows an API Consumer sending a GET request to an API Producer, and the API Producer responding with a 200 OK status.](3711f8e9365e67e6019303fc07924eed_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note over API Consumer: API Consumer - Note over API Producer: API Producer - API Consumer->>API Producer: 1 GET /data-jobs/{dataJobId} - API Producer-->>API Consumer: 2 200 OK (DataJobInfo) - Note over API Consumer: API Consumer - Note over API Producer: API Producer - -``` - -Sequence diagram for Query data job operation. It shows an API Consumer sending a GET request to an API Producer, and the API Producer responding with a 200 OK status. - -**Figure 7.3.4.5.1 -1: Query data job operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (...../data-jobs/{dataJobId}). The message content shall be empty. The API producer shall process the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP response. On success, “200 OK“ shall be returned. The message content shall carry the queried data job information. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -**7.3.4.5.2 Referenced procedures.** - -**7.3.4.5.2.1 Query data job procedure** - -The Query data job operation illustrated in figure 7.3.4.5.1-1. is based on the Query data subscription procedure defined for the Data subscription service in R1GAP [5]. - -**7.3.4.6 Query data job status** - -**7.3.4.6.1 Operation definition** - -The API Consumer uses this operation to query the data job status. - -The operation to query the data job is based on HTTP GET. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: GET ...../data-jobs/{dataJobId}/status -Producer -->> Consumer: 200 OK (DataJobStatusInfo) -@enduml -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for the Query data job status operation. The API Consumer sends a GET request to the API Producer, and the API Producer responds with a 200 OK status.](44c649b1c110b4cd617810ae17342927_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET ...../data-jobs/{dataJobId}/status - API Producer-->>API Consumer: 2 200 OK (DataJobStatusInfo) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for the Query data job status operation. The API Consumer sends a GET request to the API Producer, and the API Producer responds with a 200 OK status. - -**Figure 7.3.4.6.1 -1: Query data job status operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (...../data-jobs/{dataJobId}/status). The message content shall be empty. The API producer shall process the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP response. On success, “200 OK“ shall be returned. The message content shall carry the queried data job status information. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -**7.3.4.6.2 Referenced procedures.** - -**7.3.4.6.2.1 Query data job procedure** - -The Query data job status operation illustrated in figure 7.3.4.6.1-1. is based on the Query data subscription status procedure defined for the Data subscription service in R1GAP [5]. - -### 7.3.4.7 Query data job identifiers - -#### 7.3.4.7.1 Operation definition - -The API Consumer uses Query data job identifiers operation to get the data job identifiers for all the jobs that are created for the specific API consumer. A data job can be either for data request or data subscription. - -The operations are based on HTTP GET. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: GET ../data-jobs -Producer -->> Consumer: 200 OK (array(dataJobId)) -@enduml -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for the 'Query data job identifiers' operation. The API Consumer sends a GET request to ../data-jobs, and the API Producer responds with a 200 OK containing an array of dataJobId.](10b0dda884baae493ad958422d11b552_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET ../data-jobs - API Producer-->>API Consumer: 2 200 OK (array(dataJobId)) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for the 'Query data job identifiers' operation. The API Consumer sends a GET request to ../data-jobs, and the API Producer responds with a 200 OK containing an array of dataJobId. - -**Figure 7.3.4.7.1 -1: Query data job operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (...../data-jobs/). The message content shall be empty. The API producer shall process the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP response. On success, “200 OK“ shall be returned. The message content shall carry an array of data job identifiers (dataJobId) created by the API Consumer. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -#### 7.3.4.7.2 Referenced procedures. - -##### 7.3.4.7.2.1 Query data job identifiers procedure - -The Query data job identifiers operation illustrated in figure 7.3.4.7.1-1. is based on the Query data subscription procedure defined for the Data subscription service in R1GAP [5]. - -### 7.3.5 Resources - -#### 7.3.5.1 Overview - -This clause defines the resources for the Data access API. - -### 7.3.5.2 Resource: "All data jobs" - -#### 7.3.5.2.1 Description - -The resource All data jobs represents all data jobs created by a particular consumer. - -Only the methods defined in clause 7.3.5.2.3 shall be supported by these resources. - -#### 7.3.5.2.2 Resource Definition - -Resource URI: {apiRoot}/data-access//data-jobs - -The resource URI variables supported by the resource are defined in Table 7.3.5.2.2-1. - -**Table 7.3.5.2.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|-------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 7.3.2. | - -#### 7.3.5.2.3 Resource Standard Methods - -##### 7.3.5.2.3.1 POST - -This method shall support the request data structure specified in the table 7.3.5.2.3.1-1, and the response data structure and response code specified in the table 7.3.5.2.3.1-2. - -**Table 7.3.5.2.3.1-1: Data structures supported by the POST request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-------------|---|-------------|------------------------------------------------------| -| DataJobInfo | M | 1 | Provides information for the data job to be created. | - -**Table 7.3.5.2.3.1-2: Data structures supported by the POST response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------| -| DataJobInfo | M | 1 | 201 Created | The operation was successful.

The message content of the POST response contains a DataJobInfo representing the created resource. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation was unsuccessful.

Detailed problem description may be carried in the response message content. | - -**Table 7.3.5.2.3.1-3: Headers supported by the 201-response code this resource.** - -| Name | Data type | P | Cardinality | Description | -|----------|-----------|---|-------------|--------------------------------------------------------------------------------| -| Location | String | M | 1 | Contains the URI of the newly created resource as defined in clause 7.3.5.2.2. | - -##### 7.3.5.2.3.2 GET - -This method shall support the request data structure specified in table 7.3.5.2.3.2 -1 and the response data structure and response code specified in 7.3.5.2.3.2 -2. - -**Table 7.3.5.2.3.2-1: Data structure supported by the GET request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|-------------------------------------------------------------| -| N/A | | | There is no object in the message content of a GET request. | - -**Table 7.3.5.2.3.2-2: Data structures supported by the HTTP GET response body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|------------------|---|-------------|----------------|-------------------------------| -| array(dataJobId) | M | 0..N | 200 OK | All data job identifiers. | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description. | - -### 7.3.5.2.4 Resource Custom Operations - -None. - -## 7.3.5.3 Resource: "Individual data job" - -### 7.3.5.3.1 Description - -The resource Individual data job represents an individual data job for a data request or data subscription. - -Only the methods defined in clause 7.3.5.3.3 shall be supported by these resources. - -### 7.3.5.3.2 Resource Definition - -Resource URI: {apiRoot}/data-access//data-jobs/{dataJobId} - -The resource URI variables supported by the resource are defined in Table 7.3.5.3.2-1. - -**Table 7.3.5.3.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|-----------------------------------------------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 7.3.2. | -| dataJobId | The data job identifier assigned by the Service Producer. | - -### 7.3.5.3.3 Resource Standard Methods - -#### 7.3.5.3.3.1 DELETE - -This method shall support the request data structure specified in table 7.3.5.3.3.1-1 and the response data structure and response code specified in 7.3.5.3.3.1-2. - -**Table 7.3.5.3.3.1-1: Data structures supported by the DELETE request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|----------------------------------------------------------------| -| N/A | | | There is no object in the message content of a DELETE request. | - -**Table 7.3.5.3.3.1-2: Data structures supported by the DELETE response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|---------------------------------------------------------------------------------------------------------------------| -| N/A | | | 204 No content | The operation was successful.

The data request has been cancelled. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation was unsuccessful.

Detailed problem description may be carried in the response message content. | - -### 7.3.5.3.3.2 PUT - -This method shall support the request data structure specified in table 7.3.5.3.3.2-1 and the response data structure and response code specified in 7.3.5.3.3.2-2. - -**Table 7.3.5.3.3.2-1: Data structure supported by the PUT request body on this resource.** - -| Data type | P | Cardinality | Description | -|-------------|---|-------------|---------------------------------------| -| DataJobInfo | M | 1 | Provides update data job information. | - -**Table 7.3.5.3.3.2-2: Data structure supported by the PUT response body on this resource.** - -| Data type | P | Cardinality | Response code | Description | -|----------------|---|-------------|---------------|---------------------------------------------------------------------------------------------------------------------| -| DataJobInfo | M | 1 | 200 OK | The operation was successful.

Data job information updated successfully. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation was unsuccessful.

Detailed problem description may be carried in the response message content. | - -### 7.3.5.3.3.3 GET - -This method shall support the request data structure specified in table 7.3.5.3.3.3-1 and the response data structure and response code specified in 7.3.5.3.3.3-2. - -**Table 7.3.5.3.3.3-1: Data structure supported by the GET request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|-------------------------------------------------------------| -| N/A | | | There is no object in the message content of a GET request. | - -**Table 7.3.5.3.3.3-2: Data structure supported by the GET response body on this resource.** - -| Data type | P | Cardinality | Response code | Description | -|----------------|---|-------------|---------------|---------------------------------------------------------------------------------------------------------------------| -| DataJobInfo | M | 1 | 200 OK | The operation was successful. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation was unsuccessful.

Detailed problem description may be carried in the response message content. | - -### 7.3.5.3.4 Resource Custom Operations - -None. - -### 7.3.5.4 Resource: "Individual data job status" - -#### 7.3.5.4.1 Description - -The resource Individual data job status represents an individual data job status for a data request or data subscription. Only the methods defined in clause 7.3.5.4.3 shall be supported by these resources. - -#### 7.3.5.4.2 Resource Definition - -Resource URI: {apiRoot}/data-access//data-jobs/{dataJobId}/status - -The resource URI variables supported by the resource are defined in Table 7.3.5.4.2-1. - -**Table 7.3.5.4.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|-----------------------------------------------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 7.3.2. | -| dataJobId | The data job identifier assigned by the Service Producer. | - -#### 7.3.5.4.3 Resource Standard Methods - -##### 7.3.5.4.3.1 GET - -This method shall support the request data structure specified in table 7.3.5.4.3.3-1 and the response data structure and response code specified in 7.3.5.4.3.3-2. - -**Table 7.3.5.4.3.3-1: Data structure supported by the GET request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|-------------------------------------------------------------| -| N/A | | | There is no object in the message content of a GET request. | - -**Table 7.3.5.4.3.3-2: Data structure supported by the GET response body on this resource.** - -| Data type | P | Cardinality | Response code | Description | -|--------------------|---|-------------|---------------|---------------------------------------------------------------------------------------------------------------------| -| DataJobSatatusInfo | M | 1 | 200 OK | The operation was successful. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation was unsuccessful.

Detailed problem description may be carried in the response message content. | - -#### 7.3.5.4.4 Resource Custom Operations - -None. - -### 7.3.6 Custom operation without associated resources. - -None. - -### 7.3.7 Notifications - -#### 7.3.7.0 General - -**Table 7.3.7.0-1: Notifications overview** - -| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | -|--------------------------------|-----------------------------------|---------------------------------|---------------------------------| -| Data Availability Notification | {dataAvailabilityNotificationUri} | POST | Notify data availability | - -#### 7.3.7.1 Notify data availability. - -##### 7.3.7.1.1 Description - -The notification informs the receiver about the availability of data for a data subscription and provides details about how to access them. - -##### 7.3.7.1.2 Target URI - -This callback URI is provided in the attribute “dataAvailabilityNotificationUri” when creating a data job for data subscription. - -##### 7.3.7.1.3 Standard Methods - -###### 7.3.7.1.3.1 POST - -This method shall support the request data structures specified in table 7.3.7.1.3.1-1 and the response data structure and response codes specified in table 7.3.7.1.3.1-2. - -The use of the method shall conform to the structured content mode of CloudEvents as specified in HTTP-CloudEvents [31], i.e. the “Content-Type” HTTP request header shall be set to “application/cloudevents+json”. - -**Table 7.3.7.1.3.1-1: Data structures supported by the HTTP POST request body on this resource.** - -| Data type | P | Cardinality | Description | -|--------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Notification | M | 1 | To notify data availability, the notification structure defined in clause B.2.4.5 shall be used, with the “type” attribute set to “org.o-ran.DME.DATA_AVAILABILITY” and the “data” attribute containing a “DataAvailabilityNotification” structure defined in clause 7.3.8.1.5. | - -**Table 7.3.7.1.3.1-2: Data structures supported by the HTTP POST response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|-----------------------------------------------------------------------------------------------------------------| -| N/A | | | 204 No content | Confirmation of received notification | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation was unsuccessful.
Detailed problem description may be carried in the response message content. | - -## 7.3.8 Data Model - -### 7.3.8.1 Structured data types - -#### 7.3.8.1.1 Overview - -The following clauses define the data type and attributes to be used in the resource representation. - -#### 7.3.8.1.2 Data type: DataJobInfo - -The DataJobInfo contains the attributes defined in table 7.3.8.1.2-1. - -**Table 7.3.8.1.2-1: Definition of type DataJobInfo** - -| Attribute Name | Data type | P | Cardinality | Description | -|---------------------------------|-----------------------------|---|-------------|--------------------------------------------------------------------------------------------------| -| dataDeliveryMode | DataDeliveryMode | M | 1 | See clause 7.3.8.2.3.1. | -| dmeTypeId | DmeTypeId | M | 1 | See clause B.4.2. | -| productionJobDefinition | object | M | 1 | Job description based on the DME type specific dataProductionSchema. | -| dataDeliveryMethod | DataDeliveryMethod | M | 1 | See clause B.4.3.1. | -| dataDeliverySchemaId | string | M | 1 | A delivery schema identifier provided by a Data Producer during the data registration procedure. | -| pullDeliveryDetailsHttp | PullDeliveryDetailsHttp | C | 0..1 | See clause 7.3.8.1.3 (See NOTE 1). | -| dataAvailabilityNotificationUri | Uri | C | 0..1 | Callback URI for data availability notifications (See NOTE 2). | -| pushDeliveryDetailsHttp | PushDeliveryDetailsHttp | C | 0..1 | See clause 7.3.8.1.4 (See NOTE 3). | -| streamingConfigurationKafka | StreamingConfigurationKafka | C | 0..1 | See clause 7.3.8.1.6 (See NOTE 4). | -| dataJobInfoStatus | ProcessMonitor | C | 0..1 | ProcessMonitor datatype is specified in 3GPP TS 28.622 [21] clause 4.3.43. (See NOTE 5) | - -NOTE 1: If dataDeliveryMethod is PULL\_HTTP and dataDeliveryMode is ONE\_TIME, the pullDeliveryDetailsHttp attribute shall be present in the Create data job response. - -NOTE 2: if dataDeliveryMethod is PULL\_HTTP, and dataDeliveryMode is CONTINUOUS, the dataAvailabilityNotificationUri attribute shall be present in the Create data job request and Create data job response. - -NOTE 3: If dataDeliveryMethod is PUSH\_HTTP, the pushDeliveryDetailsHttp attribute shall be present in the Create data job request and Create data job response. - -NOTE 4: If dataDeliveryMethod is STREAMING\_KAFKA, the streamingConfigurationKafka attribute shall be present in the Create data job request sent by the DME as API Consumer and in the Create data job response sent by the DME as API Producer. If the streamingConfigurationKafka attribute is present in the Create data job request, it shall be present in the corresponding Create data job response. - -NOTE 5 : When API Consumer requesting the datajob, the dataJobInfoStatus shall not present in the request. When API Producer creating a data job the response shall include the DataJobInfo with dataJobInfoStatus. - -#### 7.3.8.1.3 Data type: PullDeliveryDetailsHttp - -The PullDeliveryDetailsHttp data type signals how to pull data using the HTTP protocol. It contains the attributes defined in table 7.3.8.1.3-1. - -**Table 7.3.8.1.3-1: Definition of type PullDeliveryDetailsHttp** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-----------|---|-------------|------------------------------------| -| dataPullUri | Uri | M | 1 | URI which data can be pulled from. | - -#### 7.3.8.1.4 Data type: PushDeliveryDetailsHttp - -The PushDeliveryDetailsHttp data type signals how to push data using the HTTP protocol. It contains the attributes defined in table 7.3.8.1.4-1. - -**Table 7.3.8.1.4-1: Definition of type PushDeliveryDetailsHttp** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-----------|---|-------------|----------------------------------| -| dataPushUri | Uri | M | 1 | URI to which data can be pushed. | - -#### 7.3.8.1.5 Data type: DataAvailabilityNotification - -The DataAvailabilityNotification contains the attributes defined in table 7.3.8.1.5-1. - -**Table 7.3.8.1.5-1: Definition of type DataAvailabilityNotification** - -| Attribute Name | Data type | P | Cardinality | Description | -|-------------------------|-------------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| dataJobId | string | M | 1 | Data job identifier. | -| pullDeliveryDetailsHttp | PullDeliveryDetailsHttp | C | 0..1 | See clause 7.3.8.2.3.2. If the dataDeliveryMechanism attribute of the data job identified by the dataJobId attribute is PULL_HTTP, this attribute shall be included. Otherwise, it shall be absent. | - -#### 7.3.8.1.6 Data type: StreamingConfigurationKafka - -The StreamingConfigurationKafka data type signals a data streaming configuration for the Kafka protocol. It contains the attributes defined in table 7.3.8.1.6-1. - -**Table 7.3.8.1.6-1: Definition of type StreamingConfigurationKafka** - -| Attribute Name | Data type | P | Cardinality | Description | -|-----------------------|-------------------------------|---|-------------|--------------------------| -| topicName | string | M | 1 | Name of the Kafka topic. | -| kafkaBootstrapServers | array (ServerAddressWithPort) | M | 1.. N | See clause 7.3.8.1.7. | - -#### 7.3.8.1.7 Data type: ServerAddressWithPort - -The ServerAddressWithPort contains the attributes defined in table 7.3.8.1.7-1. - -**Table 7.3.8.1.7-1: Definition of type ServerAddressWithPort** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-----------|---|-------------|--------------------------------------------------------------------------| -| hostname | string | M | 1 | hostname shall follow DNS naming convention as defined in IETF RFC 1035. | -| portAddress | integer | M | 1 | Port address, e.g., 9092. | - -## 7.3.8.2 Simple data types and enumerations - -### 7.3.8.2.1 Introduction - -This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. - -### 7.3.8.2.2 Simple data types - -None. - -### 7.3.8.2.3 Enumerations - -#### 7.3.8.2.3.1 Enumeration: DataDeliveryMode - -This indicates whether the data instance is created in a one-time data delivery (data request) or continuously (data subscription). - -**Table 7.3.8.2.3.1-1: Enumeration type of DataDeliveryMode** - -| Enumerations Value | Description | -|--------------------|---------------------------------------------------------------------------------------------------| -| ONE_TIME | indicate the data job to be created is for on-time data delivery, i.e., for data request. | -| CONTINUOUS | indicate the data job to be created is for continuous data delivery, i.e., for data subscription. | - -#### 7.3.8.2.3.2 Void - -### 7.3.8.3 Re-used data types - -None. - -### 7.3.8.4 Service-specific registration information - -The following structure defines the content of the “serviceCapabilities” attribute in the “ServiceProperties” data type (see clause B.3.4.2) for registration and discovery of this service. - -**Table 7.3.8.4-1: Definition of the service-specific registration information** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------------------|-------------------------|---|-------------|------------------------------------------------------------------------------------------------| -| supportedDataDeliveryModes | array(DataDeliveryMode) | M | 1..N | Indicates whether one-time or continuous data delivery, or both, are supported by the service. | - -## 7.3.9 Error Handling - -### 7.3.9.1 General - -For the Data access API, HTTP error responses shall be supported as specified in 3GPP TS 29.501 [1]. Protocol errors and application errors specified in 3GPP TS 29.500 [2], table 5.2.7.2-1, shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in 3GPP TS 29.500 [2], table 5.2.7.1-1. - -In addition, the requirements in the following clauses are applicable for the Data access API. - -### 7.3.9.2 Protocol Errors - -No specific protocol errors are defined in the present document. - -### 7.3.9.3 Application Errors - -No additional application errors defined in the present document. - -## 7.4 HTTP based Push data API - -### 7.4.1 Introduction - -This API enables the API Producer to push data to the API Consumer based on the Push data service procedures defined in R1GAP [5]. The API definition applies to both scenarios when rApp is the Service Consumer and when DME is the Service Consumer, respectively. - -### 7.4.2 API version - -For the Push data API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 0 and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1] for a definition of the version fields). - -### 7.4.3 Resource structure and methods - -The resource URI is a callback URI provided when creating a data job or data offer. - -### 7.4.4 Service Operations - -#### 7.4.4.1 Push data - -##### 7.4.4.1.1 Operation definition - -The API Producer uses Push data operation to push data payload to the API Consumer. - -The operation is based on HTTP POST. - -``` -@startuml -autonumber -Participant "API Producer" as Producer -Participant "API Consumer" as Consumer -Producer ->> Consumer: POST {dataPushUri}(data payload) -Consumer -->> Producer: 204 No Content -@enduml -``` - -![Sequence diagram showing the Push data operation. The API Producer sends a POST request with {dataPushUri} and data payload to the API Consumer. The API Consumer responds with a 204 No Content status.](a69578b3473c27629eb691e06d9f04fc_img.jpg) - -``` -sequenceDiagram - participant API Producer - participant API Consumer - Note left of API Producer: 1 POST {dataPushUri}(data payload) - API Producer->>API Consumer: POST {dataPushUri}(data payload) - Note right of API Consumer: 2 204 No Content - API Consumer-->>API Producer: 204 No Content -``` - -Sequence diagram showing the Push data operation. The API Producer sends a POST request with {dataPushUri} and data payload to the API Consumer. The API Consumer responds with a 204 No Content status. - -Figure 7.4.4.1.1-1: Push data operation - -The service operation is as follows: - -1. The API Producer shall send an HTTP POST request to the API Consumer. The target URI (dataPushUri) identifies the destination for pushing data to. The message content shall carry the data payload. The Content-Type header shall be present and set to the exact media type of the data payload. -2. The API Consumer shall return the HTTP POST response. On success, “204 No Content” shall be returned. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -7.4.4.1.2 Referenced procedures. - -7.4.4.1.2.1 Push data procedure - -The Push data operation illustrated in figure 7.4.4.1.1-1 is based on the Push data procedure defined for the Push data service in R1GAP [5]. - -7.4.5 Resources - -7.4.5.1 Overview - -This clause defines the resources for the Push data API. - -7.4.5.2 Resource: "Push delivery URI" - -7.4.5.2.1 Description - -The resource represents the destination for pushing data to. - -7.4.5.2.2 Resource Definition - -The resource URI is a callback URI provided in the “PushDeliveryDetailsHttp“ data structure when creating a data job for data subscription or a data offer. - -7.4.5.2.3 Resource Standard Methods - -7.4.5.2.3.1 POST - -The method shall support carrying the data payload in the request body. The format of the data payload and Content-Type header are determined by the data message schema. - -The method shall support the response data structures and response codes specified in table 7.4.5.2.3.1-1. - -**Table 7.4.5.2.3.1-1: Data structures supported by the HTTP POST response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|---------------------------------------------------------------------------------------------------------------------| -| N/A | | | 204 No content | Confirmation of received data delivery. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation was unsuccessful.

Detailed problem description may be carried in the response message content. | - -7.4.5.2.4 Resource Custom Operations - -None. - -7.4.6 Custom operation without associated resources. - -None. - -7.4.7 Notifications - -None. - -## 7.4.8 Data Model - -### 7.4.8.1 Structured data types - -None. - -### 7.4.8.2 Simple data types and enumerations - -None. - -### 7.4.8.3 Re-used data types - -None. - -### 7.4.8.4 Service-specific registration information - -None. - -## 7.4.9 Error Handling - -### 7.4.9.1 General - -For the Push data API, HTTP error responses shall be supported as specified in 3GPP TS 29.501 [1]. Protocol errors and application errors specified in 3GPP TS 29.500 [2], table 5.2.7.2-1, shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in 3GPP TS 29.500 [2], table 5.2.7.1-1. - -In addition, the requirements in the following clauses are applicable for the Push data API. - -### 7.4.9.2 Protocol Errors - -No specific protocol errors are defined in the present document. - -### 7.4.9.3 Application Errors - -No additional application errors defined in the present document. - -## 7.5 HTTP based Pull data API - -### 7.5.1 Introduction - -This API enables the API Consumer to pull data from the API Producer based on the Pull data service procedures defined in R1GAP [5]. The API definition applies to both scenarios when rApp is the Service Consumer and when DME is the Service Consumer, respectively. - -### 7.5.2 API version - -For the Pull data API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 0 and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1] for a definition of the version fields). - -### 7.5.3 Resource structure and methods - -The resource URI is a target URI provided when creating a data job for data request or a data offer, or when notifying the data availability for data subscription. - -## 7.5.4 Service Operations - -### 7.5.4.1 Pull data. - -#### 7.5.4.1.1 Operation definition - -The API Consumer uses Pull data operation to pull data payload from the API Producer. - -The operation is based on HTTP GET. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: GET {dataPullUri} -alt data ready - Producer -->> Consumer: 200 OK (data payload) -else data not ready - Producer -->> Consumer: 202 Accepted -end -@enduml -``` - -![Sequence diagram showing the Pull data operation between an API Consumer and an API Producer. The Consumer sends a GET request to the Producer. The Producer responds with either a 200 OK (data payload) if the data is ready, or a 202 Accepted if the data is not ready. The diagram includes lifelines for the API Consumer and API Producer, and an alt block labeled 'data ready' and 'data not ready'.](ff7977984f2552f326b2089d7595fff3_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 GET {dataPullUri} - alt data ready: 2 200 OK (data payload) - else data not ready: 3 202 Accepted - Note right of API Producer: -``` - -Sequence diagram showing the Pull data operation between an API Consumer and an API Producer. The Consumer sends a GET request to the Producer. The Producer responds with either a 200 OK (data payload) if the data is ready, or a 202 Accepted if the data is not ready. The diagram includes lifelines for the API Consumer and API Producer, and an alt block labeled 'data ready' and 'data not ready'. - -Figure 7.5.4.1.1-1: Pull data operation. - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI (dataPullUri) identifies the destination for pulling data from. -2. The API Producer shall return the HTTP GET response. On success, “200 OK“ shall be returned, the message content shall carry the data payload. The Content-Type header shall be present and set to the exact media type of the data payload. -3. If the data payload is not ready yet, “202 Accepted“ shall be returned, with the Retry-After header optionally provided to indicate how long the API Consumer should wait before making a follow-up request. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -#### 7.5.4.1.2 Referenced procedures. - -##### 7.5.4.1.2.1 Pull data procedure - -The Pull data operation illustrated in figure 7.5.4.1.1-1 is based on the Retrieve data procedure defined for the Pull data service in R1GAP [5]. - -## 7.5.5 Resources - -### 7.5.5.1 Overview - -This clause defines the resources for the Pull data API. - -### 7.5.5.2 Resource: "Pull delivery URI" - -#### 7.5.5.2.1 Description - -The resource represents the destination for pulling data from. - -#### 7.5.5.2.2 Resource Definition - -The resource URI is a target URI provided in the “PullDeliveryDetailsHttp“ data structure when creating a data job for data request or a data offer, or when notifying the data availability for data subscription. - -#### 7.5.5.2.3 Resource Standard Methods - -##### 7.5.5.2.3.1 GET - -This method shall support the request data structures specified in table 7.5.5.2.3.1-1 the response data structures and response codes specified in table 7.5.5.2.3.1-2 and the HTTP response headers as defined in table 7.5.5.2.3.1-3. - -**Table 7.5.5.2.3.1-1: Data structures supported by the HTTP GET request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|-------------------------------------------------------------| -| NA | | | There is no object in the message content of a GET request. | - -**Table 7.5.5.2.3.1-2: Data structures supported by the HTTP GET response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|---------------------------------------------------------------------------------------------------------------------| -| N/A | | | 200 OK | Carry data payload in the response body. | -| N/A | | | 202 Accepted | Data payload is not ready, retry later and the response body shall be empty. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation was unsuccessful.

Detailed problem description may be carried in the response message content. | - -The method shall support carrying the data payload in the response body of the “200OK“ response. The format of the data payload and Content-Type header are determined by the data message schema. - -**Table 7.5.5.2.3.1-3: Headers supported by the 202 Response code on this resource** - -| Name | Data type | P | Cardinality | Description | -|-------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Retry-After | string | O | 0..1 | Indicates to the API Consumer the length of the time interval to wait until sending the next request, or the point in time when such request should earliest be sent. The format is defined in IETF RFC 9110 [25]. | - -#### 7.5.5.2.4 Resource Custom Operations - -None. - -### 7.5.6 Custom operation without associated resources. - -None. - -### 7.5.7 Notifications - -None. - -### 7.5.8 Data Model - -#### 7.5.8.1 Structured data types - -None. - -#### 7.5.8.2 Simple data types and enumerations - -None. - -#### 7.5.8.3 Re-used data types - -None. - -#### 7.5.8.4 Service-specific registration information - -None. - -### 7.5.9 Error Handling - -#### 7.5.9.1 General - -For the Pull data API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [1]. Protocol errors and application errors specified in 3GPP TS 29.500 [2], table 5.2.7.2-1, shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in 3GPP TS 29.500 [2], table 5.2.7.1-1. - -In addition, the requirements in the following clauses are applicable for the Pull data API. - -#### 7.5.9.2 Protocol Errors - -No specific protocol errors are defined in the present document. - -#### 7.5.9.3 Application Errors - -No additional application errors defined in the present document. - -## 7.6 Data offer API - -### 7.6.1 Introduction - -This API enables an API Consumer to trigger the API Producer to collect a data instance produced by the API Consumer and to store it for later consumption, based on the procedures for managing a data offer defined in R1GAP [5]. The API definition applies to the scenario when a Data Producer is the Service Consumer and the DME framework is the Service Producer. - -### 7.6.2 API version - -For the Data offer API as specified in the present document, the MAJOR version field shall be 2, the MINOR version field shall be 0 and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1] for a definition of the version fields). Consequently, the URI path segment shall be set to “v2”. - -The API is under development and consequently the API version shall include the pre-release version “alpha.1”. - -### 7.6.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined in clause 5.2. The resource URI variable shall be “data-offer”. The for each resource shall be set as described in clause 7.6.5. - -Figure 7.6.3-1 shows the overall resource URI structure defined for the Data offer API. - -![A hierarchical diagram showing the resource URI structure. The root is {apiRoot}/data-offer//, which branches to /offers, which in turn branches to /{dataOfferId}.](4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg) - -``` - -graph TD - Root["{apiRoot}/data-offer//"] --> Offers["/offers"] - Offers --> DataOfferId["/{dataOfferId}"] - -``` - -A hierarchical diagram showing the resource URI structure. The root is {apiRoot}/data-offer//, which branches to /offers, which in turn branches to /{dataOfferId}. - -**Figure 7.6.3-1: Resource URI structure of the Data offer API** - -Table 7.6.3-1 lists the individual resources defined for the API, the applicable HTTP methods, and the associated service operations. - -**Table 7.6.3-1: Resource and methods overview of the Data offer API** - -| Resource name | Resource URI | HTTP method | Service Operation | -|-----------------------|--------------------------|-------------|---------------------------------| -| All data offers | .../offers | POST | Create an individual data offer | -| Individual data offer | .../offers/{dataOfferId} | DELETE | Cancel data offer | - -## 7.6.4 Service Operations - -### 7.6.4.1 Create data offer - -#### 7.6.4.1.1 Operation definition - -The API Consumer uses the Create data offer operation to create a data offer. - -The operation is based on HTTP POST. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: POST .../offers (DataOfferInfo) -Producer -->> Consumer: 201 Created (DataOfferInfo) -@enduml -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for the Create data offer operation. The API Consumer sends a POST request to the API Producer, and the API Producer responds with a 201 Created status.](aa73c8651865e31f7a2f7b8a9c068461_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 POST .../offers (DataOfferInfo) - API Producer-->>API Consumer: 2 201 Created (DataOfferInfo) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for the Create data offer operation. The API Consumer sends a POST request to the API Producer, and the API Producer responds with a 201 Created status. - -Figure 7.6.4.1.1-1: Create data offer operation - -The service operation is as follows: - -1. The API Consumer shall send an HTTP POST request to the API Producer. The target URI shall identify the resource (.../offers) under which the new data offer is to be created. The message content shall carry a DataOfferInfo structure. -2. The API Producer shall return the HTTP POST response. On success, “201 Created“ shall be returned. The Location header shall be present and shall carry the URI of the new data offer resource with dataOfferId assigned by the API producer. The message content shall carry a DataOfferInfo representing the created data offer. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -#### 7.6.4.1.2 Referenced procedures. - -##### 7.6.4.1.2.1 Create data offer procedure - -The Create data offer operation illustrated in figure 7.6.4.1.1-1 is based on the Create data offer procedure defined for the Data offer service in R1GAP [5]. - -### 7.6.4.2 Cancel data offer - -#### 7.6.4.2.1 Operation definition - -The API Consumer uses the Cancel data offer operation to cancel a data offer, i.e. to indicate to the API Producer that it has stopped the delivery of data for the data offer. - -The operation is based on HTTP DELETE. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: DELETE .../offers/{dataOfferId} -``` - -``` - -Producer --> Consumer: 204 No Content -@enduml - -``` - -![Sequence diagram for Cancel data offer operation. It shows an API Consumer sending a DELETE request to an API Producer, and the API Producer responding with a 204 No Content status.](0931f3e098bd4539041de11c50cec2d2_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: Producer --> Consumer: 204 No Content - API Consumer->>API Producer: 1 DELETE .../offers/{dataOfferId} - API Producer-->>API Consumer: 2 204 No Content - -``` - -Sequence diagram for Cancel data offer operation. It shows an API Consumer sending a DELETE request to an API Producer, and the API Producer responding with a 204 No Content status. - -**Figure 7.6.4.2.1-1: Cancel data offer operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP DELETE request to the API Producer. The target URI shall identify the resource (`.../offers/{dataOfferId}`). -2. The API Producer shall return the HTTP DELETE response. On success, “204 No Content” shall be returned. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -NOTE: For some data delivery methods, due to race conditions, residual produced data can arrive at the API Producer even after having received the HTTP DELETE request. The API Producer should be robust against this situation. - -### 7.6.4.2.2 Referenced procedures. - -#### 7.6.4.2.2.1 Cancel data offer procedure. - -The Cancel data offer operation illustrated in figure 7.6.4.2.1-1 is based on the cancel data offer procedure defined for the Data offer service in R1GAP [5]. - -### 7.6.4.3 Notify data offer termination - -#### 7.6.4.3.1 Operation definition - -The API Producer uses this operation to notify the API Consumer that it has stopped collecting the offered data. The API Consumer stops producing data. - -The operation is based on HTTP POST. - -``` - -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Producer --> Consumer: POST {dataOfferTerminationNotificationUri} Notification( -(DataOfferTerminationNotification)) -Consumer --> Consumer: Stop producing data -Consumer --> Producer: 204 No Content -@enduml - -``` - -![Sequence diagram for Notify data offer termination. The diagram shows an API Producer sending a POST request to an API Consumer, stopping data production, and receiving a 204 No Content response.](3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note right of API Producer: 1 POST {dataOfferTerminationNotificationUri} Notification( (DataOfferTerminationNotification)) - API Producer->>API Consumer: 1 POST {dataOfferTerminationNotificationUri} Notification( (DataOfferTerminationNotification)) - Note left of API Consumer: 2 Stop producing data - API Consumer-->>API Consumer: 2 Stop producing data - Note right of API Consumer: 3 204 No Content - API Consumer-->>API Producer: 3 204 No Content - -``` - -Sequence diagram for Notify data offer termination. The diagram shows an API Producer sending a POST request to an API Consumer, stopping data production, and receiving a 204 No Content response. - -**Figure 7.6.4.3.1-1: Notify data offer termination** - -The service operation is as follows: - -1. The API Producer shall send an HTTP POST request to the API Consumer. The target URI (`dataOfferTerminationNotificationUri` which was provided during data offer creation) identifies the address where to send the notifications. The message content shall carry a Notification message that includes a `DataOfferTerminationNotification` payload. -2. The API Producer shall stop producing data. -3. The API Consumer shall return the HTTP POST response. On success, “204 No Content“ shall be returned. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -NOTE: For some data delivery methods, due to race conditions, residual produced data can arrive at the API Producer even after having received the “204 No Content“ response. The API Producer should be robust against this situation. - -## 7.6.4.3.2 Referenced procedures. - -### 7.6.4.3.2.1 Notify data offer termination procedure. - -The Notify data offer termination operation illustrated in figure 7.6.4.3.1-1 is based on the Notify data offer termination procedure defined for the Data offer service in R1GAP [5]. - -## 7.6.5 Resources - -### 7.6.5.1 Overview - -This clause defines the resources for the Data offer API. - -### 7.6.5.2 Resource: "All data offers" - -#### 7.6.5.2.1 Description - -The resource All data offers represents all data offers created by a particular consumer. - -Only the methods defined in clause 7.6.5.2.3 shall be supported by these resources. - -#### 7.6.5.2.2 Resource Definition - -Resource URI: `{apiRoot}/data-offer//offers` - -The resource URI variables supported by the resource are defined in Table 7.6.5.2.2-1. - -**Table 7.6.5.2.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|-------------------| -| apiRoot | See clause 5.3. | -| apiVersion | See clause 7.6.2. | - -### 7.6.5.2.3 Resource Standard Methods - -#### 7.6.5.2.3.1 POST - -This method shall support the request data structure specified in the table 7.6.5.2.3.1-1, and the response data structure and response code specified in the table 7.6.5.2.3.1-2. - -**Table 7.6.5.2.3.1-1: Data structures supported by the POST request body on all data jobs.** - -| Data Type | P | Cardinality | Description | -|---------------|---|-------------|------------------------------------------------------| -| DataOfferInfo | M | 1 | Provides information for the data job to be created. | - -**Table 7.6.5.2.3.1-2: Data structures supported by the POST response body on all data jobs.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------| -| DataOfferInfo | M | 1 | 201 Created | The operation was successful.

The message content of the POST response contains a DataOfferInfo representing the created resource. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation was unsuccessful.

Detailed problem description may be carried in the response message content. | - -**Table 7.6.5.2.3.1-3: Headers supported by the 201-response code on the resource.** - -| Name | Data type | P | Cardinality | Description | -|----------|-----------|---|-------------|--------------------------------------------------------------------------------| -| Location | String | M | 1 | Contains the URI of the newly created resource as defined in clause 7.6.5.3.2. | - -### 7.6.5.2.4 Resource Custom Operations - -None. - -## 7.6.5.3 Resource: "Individual data offer" - -### 7.6.5.3.1 Description - -The resource Individual data offer represents an individual data offer. - -The methods defined in clause 7.6.5.3.3 shall be supported by this resource. - -### 7.6.5.3.2 Resource Definition - -Resource URI: {apiRoot}/data-offer //offers/{dataOfferId} - -The resource URI variables supported by the resource is defined in Table 7.6.5.3.2-1. - -**Table 7.6.5.3.2-1: Resource URI variables for the resource** - -| Name | Definition | -|-------------|-------------------------------------------------------------| -| apiRoot | See clause 5.3. | -| apiVersion | See clause 7.6.2. | -| dataOfferId | The data offer identifier assigned by the Service Producer. | - -### 7.6.5.3.3 Resource Standard Methods - -#### 7.6.5.3.3.1 DELETE - -This method shall support the request data structure specified in table 7.6.5.3.3.1-1 and the response data structure and response code specified in 7.6.5.3.3.1-2. - -**Table 7.6.5.3.3.1-1: Data structure supported by the DELETE request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|----------------------------------------------------------------| -| N/A | | | There is no object in the message content of a DELETE request. | - -**Table 7.6.5.3.3.1-2: Data structure supported by the DELETE response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|---------------------------------------------------------------------------------------------------------------------| -| N/A | | | 204 No content | The operation was successful.

The data offer has been cancelled. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation was unsuccessful.

Detailed problem description may be carried in the response message content. | - -#### 7.6.5.3.4 Resource Custom Operations - -None. - -### 7.6.6 Custom operation without associated resources. - -None. - -## 7.6.7 Notifications - -### 7.6.7.0 General - -**Table 7.6.7.0-1: Notifications overview** - -| Notification | Callback URI | HTTP method or custom operation | Description (service operation) | -|-------------------------------------------|---------------------------------------|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Data Offer Termination Notification | {dataOfferTerminationNotificationUri} | POST | Notify data offer termination | -| Data Offer Data Availability Notification | {dataAvailabilityNotificationUri} | POST | Notify availability of data for a data offer

Deviating from the general callback pattern, the {dataAvailabilityNotificationUri} is a local URI addressing an endpoint at the API producer side. | - -### 7.6.7.1 Notify data offer termination - -#### 7.6.7.1.1 Description - -The notification informs the Data Producer as API Consumer that the sender of the notification, i.e. the Api Producer, does not intend to collect the data instance related to the data offer from the Data Producer any longer. The Data Producer shall stop data production when receiving this notification. - -#### 7.6.7.1.2 Target URI - -The target URI is a callback URI that has been provided in the attribute “dataOfferTerminationNotificationUri” when creating the related data offer. - -#### 7.6.7.1.3 Standard Methods - -##### 7.6.7.1.3.1 POST - -This method shall support the request data structures specified in table 7.6.7.1.3.1-1 and the response data structure and response codes specified in table 7.6.7.1.3.1-2. - -The use of the method shall conform to the structured content mode of CloudEvents as specified in HTTP-CloudEvents [31], i.e. the “Content-Type” HTTP request header shall be set to “application/cloudevents+json”. - -**Table 7.6.7.1.3.1-1: Data structures supported by the HTTP POST request body on this resource.** - -| Data type | P | Cardinality | Description | -|--------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Notification | M | 1 | To notify data offer termination, the notification structure defined in clause B.2.4.5 shall be used, with the “type” attribute set to “org.o-ran.DME.DATA_OFFER_TERMINATION” and the “data” attribute containing a “DataOfferTerminationNotification” structure defined in clause 7.6.8.1.3. | - -**Table 7.6.7.1.3.1-2: Data structures supported by the HTTP POST response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|---------------------------------------------------------------------------------------------------------------------| -| N/A | | | 204 No content | Confirmation of received notification. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation was unsuccessful.

Detailed problem description may be carried in the response message content. | - -### 7.6.7.2 Notify data offer data availability - -#### 7.6.7.2.1 Description - -The notification, which is sent by the Data Producer as API Consumer, informs the Data Consumer as API Producer about the availability of data for a data offer and provides details about how to access them. - -NOTE: Due to the special nature of a data offer, this pattern deviates from the usual notification pattern where the notification is sent by the API Producer to the API consumer. - -#### 7.6.7.2.2 Target URI - -The target URI is local URI in API Producer's URI space that has been provided in the attribute “dataAvailabilityNotificationUri” in the response to the request that has created the related data offer. - -#### 7.6.7.2.3 Standard Methods - -##### 7.6.7.2.3.1 POST - -This method shall support the request data structures specified in table 7.6.7.2.3.1-1 and the response data structure and response codes specified in table 7.6.7.2.3.1-2. - -The use of the method shall conform to the structured content mode of CloudEvents as specified in HTTP-CloudEvents [31], i.e. the “Content-Type” HTTP request header shall be set to “application/cloudevents+json”. - -**Table 7.6.7.2.3.1-1: Data structures supported by the HTTP POST request body on this resource.** - -| Data type | P | Cardinality | Description | -|--------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Notification | M | 1 | To notify data offer termination, the notification structure defined in clause B.2.4.5 shall be used, with the “type” attribute set to “org.o-ran.DME.DATA_OFFER_TERMINATION” and the “data” attribute containing a “DataOfferTerminationNotification” structure defined in clause 7.6.8.1.3. | - -**Table 7.6.7.2.3.1-2: Data structures supported by the HTTP POST response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|---------------------------------------------------------------------------------------------------------------------| -| N/A | | | 204 No content | Confirmation of received notification. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation was unsuccessful.

Detailed problem description may be carried in the response message content. | - -## 7.6.8 Data Model - -### 7.6.8.1 Structured data types - -#### 7.6.8.1.1 Overview - -The following clauses define the data types and attributes to be used in the resource representation. - -#### 7.6.8.1.2 Data type: DataOfferInfo - -The DataOfferInfo contains the attributes defined in table 7.6.8.1.2-1. - -**Table 7.6.8.1.2-1: Definition of type DataOfferInfo** - -| Attribute Name | Data type | P | Cardinality | Description | -|-------------------------------------|-----------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| dataDeliveryMode | DataDeliveryMode | M | 1 | See clause 7.3.8.2.3.1 | -| dmeTypeId | DmeTypeId | M | 1 | See clause B.4.2 | -| productionJobDefinition | object | M | 1 | Job definition based on the DME type specific dataProductionSchema | -| dataDeliveryMethods | array (DataDeliveryMethod) | M | 1..N | Data delivery method(s), see clause B.4.3.1(NOTE 1). | -| dataDeliverySchemaIds | array (string) | M | 1..N | Delivery schema identifiers (NOTE 1). | -| pullDeliveryDetailsHttp | PullDeliveryDetailsHttp | C | 0..1 |

Access details for HTTP Pull delivery of the data, managed by the API Consumer, see clause 7.3.8.1.3.

The API Consumer shall provide this attribute in the HTTP request to create a data offer if the value "PULL_HTTP" is included in "dataDeliveryMechanisms".

The API Producer shall include this attribute in HTTP responses if it has chosen "PULL_HTTP" data delivery.

| -| dataAvailabilityNotificationUri | Uri | C | 0..1 |

Callback URI to receive data availability notifications, managed by the API Producer.

The API Consumer shall not include this attribute in the HTTP request to create a data offer.

The API Producer shall include this attribute in HTTP responses if it has chosen "PULL_HTTP" data delivery in "CONTINUOUS" delivery mode.

| -| dataOfferTerminationNotificationUri | Uri | M | 1 | Callback URI to receive data offer termination notifications, managed by the API Consumer. | -| pushDeliveryDetailsHttp | PushDeliveryDetailsHttp | C | 0..1 |

Access details for HTTP Push delivery of the data, managed by the API Producer, see clause 7.3.8.1.4.

The API Consumer shall not provide this attribute in the HTTP request to create a data offer.

The API Producer shall include this attribute in HTTP responses if it has chosen "PUSH_HTTP" data delivery.

| -| streamingConfigurationKafka | StreamingConfigurationKafka | C | 0..1 |

Konfiguration to stream data over a Kafka bus, see clause 7.3.8.1.6. This attribute shall not be present in the HTTP request to create a data offer.

If the value "STREAMING_KAFKA" is included in "dataDeliveryMechanisms", this attribute shall be included in HTTP responses.

| - -NOTE 1: In the HTTP request to create a data offer, the API Consumer shall include all items it supports. In HTTP responses, the API Producer shall include the single item that has been chosen from the alternatives proposed during data offer creation. - -### 7.6.8.1.3 Data type: DataOfferTerminationNotification - -The DataOfferTerminationNotification contains the attributes defined in table 7.6.8.1.3-1. - -**Table 7.6.8.1.3-1: Definition of type DataOfferTerminationNotification** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-----------|---|-------------|------------------------------------------------| -| dataOfferId | string | M | 1 | Identifier of the data offer to be terminated. | - -### 7.6.8.1.4 Data type: DataOfferDataAvailabilityNotification - -The DataOfferDataAvailabilityNotification contains the attributes defined in table 7.6.8.1.4-1. - -**Table 7.6.8.1.4-1: Definition of type DataofferDataAvailabilityNotification** - -| Attribute Name | Data type | P | Cardinality | Description | -|-------------------------|-------------------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| dataOfferId | string | M | 1 | Identifier of the data offer to be terminated. | -| pullDeliveryDetailsHttp | PushDeliveryDetailsHttp | C | 1 |

Access details for HTTP Push delivery of the data, managed by the API Producer, see clause 7.3.8.1.4.

The API Consumer shall not provide this attribute in the HTTP request to create a data offer.

The API Producer shall include this attribute in HTTP responses if it has chosen “PUSH_HTTP” data delivery.

| - -### 7.6.8.2 Simple data types and enumerations - -None. - -### 7.6.8.3 Re-used data types - -Table 7.6.8.3-1 specified data types re-used from the Data Access API. - -**Table 7.6.8.3-1 Re-used data types** - -| Data type | Reference | Comments | -|------------------------------|------------------|----------| -| DataDeliveryMethod | Clause B.4.3.1 | | -| PullDeliveryDetailsHttp | Clause 7.3.8.1.3 | | -| PushDeliveryDetailsHttp | Clause 7.3.8.1.4 | | -| DataAvailabilityNotification | Clause 7.6.8.1.4 | | -| StreamingConfigurationKafka | Clause 7.3.8.1.6 | | - -### 7.6.8.4 Service-specific registration information - -None. - -## 7.6.9 Error Handling - -### 7.6.9.1 General - -For the Data offer API, HTTP error responses shall be supported as specified in clause 4.8 of 3GPP TS 29.501 [1]. Protocol errors and application errors specified in 3GPP TS 29.500 [2], table 5.2.7.2-1, shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in 3GPP TS 29.500 [2], table 5.2.7.1-1. - -In addition, the requirements in the following clauses are applicable for the Data offer API. - -### 7.6.9.2 Protocol Errors - -No specific protocol errors are defined in the present document. - -### 7.6.9.3 Application Errors - -No additional application errors defined in the present document. - ---- - -## 8 RAN OAM related services. - -### 8.1 Configuration management API - -#### 8.1.1 Introduction - -This API allows the API Consumer to request managing configuration data based on the procedures for “Configuration management (CM) service” defined in R1GAP [5]. - -#### 8.1.2 API version - -For the Configuration management API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 0 and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1] for a definition of the version fields). Consequently, the URI variable shall be set to “v1”. - -The Configuration management API is under development and consequently the API version shall include the pre-release version “alpha.1”. - -#### 8.1.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined for the Generic provisioning management service API (see 3GPP TS 28.532 [20], Figure 12.1.1.3.1.1-1 in Clause 12.1.1.3.1.1). - -Table 8.1.3-1 lists the individual resources defined for the API, the applicable HTTP methods as defined in 3GPP TS 28.532 [20], clause 12.1.1, and the associated service operations. Table 8.1.3-1 lists the individual resources defined for the API, the applicable HTTP methods, and the associated service operations. - -**Table 8.1.3-1: Resources and methods overview of the configuration management API** - -| Resource Name
3GPP TS 28.532 [20] | Resource URI
3GPP TS 28.532 [20] | HTTP method
3GPP TS 28.532 [20] | Service Operation | -|--------------------------------------|-------------------------------------------|------------------------------------|------------------------------| -| MOI | .../{URI-LDN-first part}/{className}={id} | GET | Read configuration data. | -| | | PATCH | Write configuration changes. | - -NOTE: CM service procedures related to M-Plane nodes, such as O-RUs, are not currently supported in this API resource structure and can be defined in future releases. - -## 8.1.4 Service operations - -### 8.1.4.1 Read configuration data - -#### 8.1.4.1.1 Operation definition - -A Service Consumer uses the Read configuration data API operation as API Consumer to read configuration with the API Producer. - -The operation is based on HTTP GET as per figure 8.1.4.1.1-1. The HTTP GET response contains configuration data that the API Consumer has requested. - -``` -@startuml -autonumber -participant "API Consumer" as cons -participant "API Producer" as prod -cons ->> prod : GET .../{URI-LDN-first part}/{className}={id} -prod -->> cons : 200 OK (Configuration Data) -@enduml -``` - -![Sequence diagram showing the interaction between an API Consumer and an API Producer. The API Consumer sends a GET request to the API Producer, and the API Producer responds with a 200 OK status containing configuration data.](91e400bc8bab58306b4d18432e94c9de_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET .../{URI-LDN-first part}/{className}={id} - API Producer-->>API Consumer: 2 200 OK (Configuration Data) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - -``` - -Sequence diagram showing the interaction between an API Consumer and an API Producer. The API Consumer sends a GET request to the API Producer, and the API Producer responds with a 200 OK status containing configuration data. - -**Figure 8.1.4.1.1-1: Read configuration data operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer that includes the Node Identifier and optional query criteria. The API Producer shall process the read information received in the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP GET response. On success “200 OK“ shall be returned and the message content shall carry configuration data. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -### 8.1.4.1.2 Referenced procedures - -#### 8.1.4.1.2.1 Reading configuration data procedure - -The procedure for reading configuration data API operation illustrated in figure 8.1.4.1.1-1 is based on Read Configuration procedure defined in R1GAP [5]. - -### 8.1.4.2 Write configuration changes - -#### 8.1.4.2.1 Operation definition - -A Service Consumer uses the Write configuration changes API operation as API Consumer to write configuration with the API Producer. - -The operation is based on HTTP PATCH as per figure 8.1.4.2.1-1. The HTTP PATCH response contains configuration data that the API Consumer has requested. - -``` -@startuml -autonumber -participant "API Consumer" as cons -participant "API Producer" as prod -cons ->> prod : PATCH ../{URI-LDN-first part}/{className}={id} -prod -->> cons : 200 OK (Configuration Data) -@enduml -``` - -![Sequence diagram showing the write configuration changes operation. An API Consumer sends a PATCH request to an API Producer, and the API Producer responds with a 200 OK containing configuration data.](d15e2d3e8dd9157eb7f0cc120097484a_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 PATCH ../{URI-LDN-first part}/{className}={id} - API Consumer->> API Producer: 1 PATCH ../{URI-LDN-first part}/{className}={id} - Note right of API Producer: 2 200 OK (Configuration Data) - API Producer-->> API Consumer: 2 200 OK (Configuration Data) -``` - -Sequence diagram showing the write configuration changes operation. An API Consumer sends a PATCH request to an API Producer, and the API Producer responds with a 200 OK containing configuration data. - -**Figure 8.1.4.2.1-1: Write configuration changes operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP PATCH request to the API Producer that includes the Node Identifier and optional query criteria along with payload which includes attribute identifiers, attribute values and modify operator as part of modification list defined in 3GPP TS 28.532 [20] clause 11.1.1.3.2. The API Producer shall process the write configuration changes information received in the HTTP PATCH message and determine if the request sent by the API consumer is authorized or not. -2. The API Producer shall return the HTTP PATCH response. On success “200 OK“ shall be returned and the message content shall carry configuration data. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -NOTE: Response format to represent “partial success“ is not specified in the present document. - -### 8.1.4.1.2 Referenced procedures. - -#### 8.1.4.1.2.1 Writing configuration change procedure. - -The procedure for writing configuration data API operation illustrated in figure 8.1.4.2.1-1 is based on write Configuration procedure defined in R1GAP [5] . - -## 8.1.5 Resources - -### 8.1.5.1 Overview - -This clause defines the resources for the Configuration management (CM) service API based on the RESTful HTTP-based solution set for the Generic provisioning management service defined in 3GPP TS 28.532 [20], clause 12.1.1. - -The Configuration management (CM) service Producer take the role of the Generic provisioning MnS Producer defined in 3GPP TS 28.532 [20] . By consuming this API, an rApp as Configuration management (CM) service Consumer takes the role of the Generic provisioning MnS Consumer defined in 3GPP TS 28.532 [20]. - -### 8.1.5.2 Resource: "MOI" - -#### 8.1.5.2.1 Description - -The MOI resource represents a managed object instance, or a tree of these, containing the configuration data . - -#### 8.1.5.2.2 Resource definition - -The resource URI structure of the provisioning MnS is defined in 3GPP TS 28.532 [20], as per clause 12.1.1.3.1.1, with the following URI: - -**{apiRoot}/ProvMnS/{apiVersion}/{URI-LDN-first-part}/{className}={id}** - -The resource URI variables are specified in 3GPP TS 28.532 [20], clause 12.1.1.3.2.1.2. - -NOTE: HTTP methods GET and PATCH shall only be used. - -#### 8.1.5.2.3 Resource standard methods - -##### 8.1.5.2.3.1 GET - -This method shall support the URI query parameters, request data structures, response data structures and response codes specified in 3GPP TS 28.532 [20], clause 12.1.1.3.2.1.3.2. - -##### 8.1.5.2.3.2 PATCH - -This method shall support the URI parameters, request data structures, response data structures and response codes specified in 3GPP TS 28.532 [20], clause 12.1.1.3.2.1.3.3. - -#### 8.1.5.2.3 Resource custom operations - -None. - -## 8.1.6 Custom operations without associated resources. - -None. - -## 8.1.7 Notifications - -NOTE: The notifications are not specified in present version of the document. - -## 8.1.8 Data model - -### 8.1.8.1 General - -The application data model is defined in 3GPP TS 28.532 [20], clause 12.1.1.4, apply to this API. - -### 8.1.8.2 Structured data types - -None. - -### 8.1.8.3 Simple data types and enumerations - -None. - -### 8.1.8.4 Re-used data types - -None. - -### 8.1.8.5 Service-specific registration information - -None. - -## 8.1.9 Error Handling - -### 8.1.9.1 General - -HTTP error handling is applicable for this API as specified in 3GPP TS 28.532 [20], clause A.1.1. - -### 8.1.9.2 Protocol Errors - -No specific protocol errors are defined in the present document. - -### 8.1.9.3 Application Errors - -No specific protocol errors are defined in the present document. - -## 8.2 Fault management API - -### 8.2.1 Introduction - -This API allows the API Consumer to read information about alarms and to acknowledge alarms based on the procedures for the ‘‘Fault management (FM) service’’ defined in R1GAP [5]. The API is based on the AlarmList IOC as specified in 28.111 [26], clause 7.3.2. . - -### 8.2.2 API version - -For the fault management API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 0 and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1] for a definition of the version fields). Consequently, the URI variable shall be set to ‘‘v1’’. - -### 8.2.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined for the Generic provisioning management service API (see 3GPP TS 28.532 [20], figure 12.1.1.3.1.1-1 in clause 12.1.1.3.1.1). - -Table 8.2.3-1 lists the individual resources defined for the API, the applicable HTTP methods as defined in 3GPP TS 28.532 [20], clause 12.1.1, and the associated service operations. - -**Table 8.2.3-1: Resources and methods overview of the fault management API** - -| Resource Name
3GPP TS 28.532 [20] | Resource URI
3GPP TS 28.532 [20] | HTTP method
3GPP TS 28.532 [20] | Service Operation | -|--------------------------------------|-------------------------------------------------------------------|------------------------------------|--------------------------------------| -| Alarm list | .../{URI-LDN-first part}/{className}={id}/AlarmList={alarmListId} | GET | Query alarms. | -| | | PATCH | Change alarm acknowledgement status. | - -NOTE: FM service procedures related to M-Plane nodes, such as O-RUs, are not currently supported in this API resource structure and can be defined in future releases. - -### 8.2.4 Service operations - -#### 8.2.4.1 Query alarms - -##### 8.2.4.1.1 Operation definition - -A Service Consumer uses the Query alarms API operation as API Consumer to query alarm information from the API Producer. - -The operation is based on HTTP GET as per figure 8.2.4.1.1-1. The HTTP GET response contains a list of alarm records matching the query of the API Consumer. - -``` -@startuml -autonumber -participant "API Consumer" as cons -participant "API Producer" as prod -cons ->> prod : GET .../{URI-LDN-first part}/{className}={id}/AlarmList={alarmListId} -prod -->> cons : 200 OK (Alarm List) -@enduml -``` - -![Sequence diagram showing the Query alarms operation. The API Consumer sends a GET request to the API Producer, and the API Producer responds with a 200 OK (Alarm List).](713cb30a2b5e9f2cea007cefb2e27a40_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 GET .../{URI-LDN-first part}/{className}={id}/AlarmList={alarmListId} - API Consumer->>API Producer: 1 GET .../{URI-LDN-first part}/{className}={id}/AlarmList={alarmListId} - Note right of API Producer: 2 200 OK (Alarm List) - API Producer-->>API Consumer: 2 200 OK (Alarm List) -``` - -Sequence diagram showing the Query alarms operation. The API Consumer sends a GET request to the API Producer, and the API Producer responds with a 200 OK (Alarm List). - -**Figure 8.2.4.1.1-1: Query alarms operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer that includes either “SubNetwork“ or “ManagedElement“ as the class name, the related object instance identifier, the alarm list identifier, and optional - -query criteria. The API Producer shall process the information received in the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. - -2. The API Producer shall return the HTTP GET response. On success “200 OK“ shall be returned and the message content shall carry the representation of the alarm list. If query criteria were given, the content of the alarm entries in the returned alarm list shall match the query criteria. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -### 8.2.4.1.2 Referenced procedures - -#### 8.2.4.1.2.1 Query alarms procedure - -The procedure for querying alarm information illustrated in figure 8.2.4.1.1-1 is based on the Query Alarms procedure defined in R1GAP [5]. - -### 8.2.4.2 Change alarm acknowledgement state - -#### 8.2.4.2.1 Operation definition - -A Service Consumer uses the Change alarm acknowledgement state API operation as API Consumer to acknowledge or unacknowledge one or more alarms with the API Producer. - -The operation is based on HTTP PATCH as per figure 8.2.4.2.1-1. - -``` -@startuml -autonumber -participant "API Consumer" as cons -participant "API Producer" as prod -cons -->> prod : PATCH .../{URI-LDN-first part}/{className}={id}/AlarmList={alarmListId} (Alarm Update Information) -alt success, no information returned - prod -->> cons : 204 No Content -else success, updated information returned - prod -->> cons : 200 OK (Alarm List) -else error - prod -->> cons : Error response -end -@enduml -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for the Change alarm acknowledgement state operation. The API Consumer sends a PATCH request to the API Producer. The API Producer responds with one of three possible outcomes: 204 No Content (success, no information returned), 200 OK (Alarm List) (success, updated information returned), or an Error response (error).](cc3d87694102054bcd694ae696bc41fa_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 PATCH .../{URI-LDN-first part}/{className}={id}/AlarmList={alarmListId} (Alarm Update Information) - API Consumer->>API Producer: 1 PATCH .../{URI-LDN-first part}/{className}={id}/AlarmList={alarmListId} (Alarm Update Information) - alt success, no information returned : 2 204 No Content - API Producer-->>API Consumer: 2 204 No Content - else success, updated information returned : 3 200 OK (Alarm List) - API Producer-->>API Consumer: 3 200 OK (Alarm List) - else error : 4 Error response - API Producer-->>API Consumer: 4 Error response - end -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for the Change alarm acknowledgement state operation. The API Consumer sends a PATCH request to the API Producer. The API Producer responds with one of three possible outcomes: 204 No Content (success, no information returned), 200 OK (Alarm List) (success, updated information returned), or an Error response (error). - -**Figure 8.2.4.2.1-1: Change alarm acknowledgement state operation.** - -The service operation is as follows: - -1. The API Consumer shall send a PATCH request to the API Producer that includes in the resource URI either “SubNetwork“ or “ManagedElement“ as the class name, the related object instance identifier, and the alarm list - -identifier. Further, it shall include in the message content information about which alarms to be updated as well as information about the actual alarm acknowledgements / unacknowledgments. The API Producer shall process the information received in the HTTP PATCH message and determine if the request sent by the API Consumer is authorized or not. - -2. The API Producer shall return the HTTP PATCH response. -3. On success, the API Producer should return a “204 No Content“ response message with empty message content. -4. On success, the API Producer may alternatively return a “200 OK“ response message with the representation of updated alarm list in the message content. -5. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 8.2.4.2.2 Referenced procedures - -##### 8.2.4.2.2.1 Change alarm acknowledgement state procedure - -The procedure for changing the acknowledgement state of one or more alarms illustrated in figure 8.2.4.2.1-1 is based on the Change alarm acknowledgement state procedure defined in RIGAP [5]. - -### 8.2.5 Resources - -#### 8.2.5.1 Overview - -This clause defines the resources for the Fault management (FM) service API based on the RESTful HTTP-based solution set for the Generic provisioning management service defined in 3GPP TS 28.532 [20], clause 12.1.1. - -The Fault management (FM) service Producer take the role of the Generic provisioning MnS Producer defined in 3GPP TS 28.532 [20]. By consuming this API, an rApp as Fault management (FM) service Consumer takes the role of the Generic provisioning MnS Consumer defined in 3GPP TS 28.532 [20]. - -#### 8.2.5.2 Resource: "Alarm list" - -##### 8.2.5.2.1 Description - -The “Alarm list“ resource represents a list of alarms related to either a subnetwork or a managed element. It allows to query alarms and to change the acknowledgement state of alarms. - -##### 8.2.5.2.2 Resource definition - -The resource URI structure of the alarm list as managed by the Generic provisioning MnS is defined as per 3GPP TS 28.532 [20], clause 12.1.1.3.1.1, for the AlarmList IOC as defined in 3GPP TS 28.111 [26], clause 7.3.2, with the following URI: - -**{apiRoot}/ProvMnS//{URI-LDN-first-part}/{className}={id}/AlarmList={alarmListId}** - -The resource URI variables supported by the resource are defined in Table 8.2.5.2.2-1. - -**Table 8.2.5.2.2-1: Resource URI variables for the resource** - -| Name | Definition | -|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 8.2.2. | -| URI-LDN-first-part | See 3GPP TS 28.532 [20], clause 12.1.1.3.2.1.2. | -| className | Name of the object class (IOC) of the managed object instance to which the alarm list is attached. Shall be either “SubNetwork“ or “ManagedElement“ as defined in 3GPP TS 28.622 [21], clause 4.3.26.1. | -| id | Identifier of the managed object instance to which the alarm list is attached. | -| alarmListId | Identifier of the managed object instance which is the alarm list. | - -### 8.2.5.2.3 Resource standard methods - -#### 8.2.5.2.3.1 GET - -This method shall support the URI query parameters, HTTP headers, response data structures and response codes specified in 3GPP TS 28.532 [20], clause 12.1.1.3.2.1.3.2. - -EXAMPLE 1: This request queries the whole alarm list: GET /SubNetwork=SN123/AlarmList=AL123 HTTP/1.1. - -EXAMPLE 2: This request queries a single alarm: GET -/SubNetwork=SN123/AlarmList=AL123?fields=/attributes/alarmRecords/ALARM456 HTTP/1.1. - -NOTE: Selection of alarm records in the query based on then values of other alarm attributes than alarm identifier is not supported in the present version. - -#### 8.2.5.2.3.2 PATCH - -This method shall support the URI query parameters, HTTP headers, response data structures and response codes specified in 3GPP TS 28.532 [20], clause 12.1.1.3.2.1.3.3. - -To change the alarm state, the patch payload shall contain values for the “ackState“ attribute (“ACKNOWLEDGED“ or “UNACKNOWLEDGED“) and the “ackUserId“ attribute and may contain a value for the “ackSystemId“ attribute, as defined in 3GPP TS 28.111 [26], clause 7.3.1.2. - -### 8.2.5.3.3 Resource custom operations - -None. - -## 8.2.6 Custom operations without associated resources - -None. - -## 8.2.7 Notifications - -None. - -## 8.2.8 Data model - -### 8.2.8.1 General - -The application data model is defined in 3GPP TS 28.111 [26], clause Annex A.1.3. The key IOCs for this API are SubNetwork, ManagedElement and AlarmList. - -### 8.2.8.2 Structured data types - -None. - -### 8.2.8.3 Simple data types and enumerations - -None. - -### 8.2.8.4 Re-used data types - -None. - -### 8.2.8.5 Service-specific registration information - -None. - -## 8.2.9 Error Handling - -### 8.2.9.1 General - -HTTP error handling is applicable for this API as specified in 3GPP TS 28.111 [26], clause A.1.3. - -### 8.2.9.2 Protocol Errors - -No specific protocol errors are defined in the present document. - -### 8.2.9.3 Application Errors - -No specific protocol errors are defined in the present document. - -## 8.3 Configuration schema information API. - -### 8.3.1 Introduction - -This API enables the API Consumer to retrieve configuration schema information based on the procedure defined in R1GAP [5]. - -### 8.3.2 API version - -For the configuration schema information API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 0 and the PATCH version field shall be 0 (see clause 4.3.1.1 of 3GPP TS 29.501 [1] for a definition of the version fields). Consequently, the URI path segment shall be set to "v1". - -### 8.3.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined in clause 5.2. The resource URI variable shall be "ran-oam-cm-schema-info". The for each resource shall be set as described in clause 8.3.5. - -Figure 8.3.3-1 shows the overall resource URI structure defined for the retrieving configuration information API. - -![A hierarchical diagram showing the resource URI structure. At the top is the root path '{apiRoot}/ran-oam-cm-schema-info/'. A vertical line descends from this root to a horizontal line that branches to a box containing '/schemas'. From the bottom of the '/schemas' box, another vertical line descends to a second horizontal line that branches to a box containing '/{schemaId}'.](bd49a5a0bc3234abe21419ad830be088_img.jpg) - -``` - -graph TD - Root["{apiRoot}/ran-oam-cm-schema-info/"] --> Schemas["/schemas"] - Schemas --> SchemaId["/{schemaId}"] - -``` - -A hierarchical diagram showing the resource URI structure. At the top is the root path '{apiRoot}/ran-oam-cm-schema-info/'. A vertical line descends from this root to a horizontal line that branches to a box containing '/schemas'. From the bottom of the '/schemas' box, another vertical line descends to a second horizontal line that branches to a box containing '/{schemaId}'. - -**Figure 8.3.3-1: Resource URI structure of the configuration schemas information API** - -Table: 8.3.3-1 lists the individual resources defined for the API, the applicable HTTP methods, and the associated service operations. - -**Table 8.3.3-1 Resource and methods overview of the configuration schemas information API** - -| Resource Name | Resource URI | HTTP method | Service Operation | -|-------------------------------|------------------------|-------------|-----------------------------------| -| All schema information | .../schemas | GET | Get all schema information | -| Individual schema information | .../schemas/{schemaId} | GET | Get Individual schema information | - -### 8.3.4 Service operations - -#### 8.3.4.1 Get all schema information - -##### 8.3.4.1.1 Operation definition - -An API consumer uses the Get all schema information operation to get Schemas. - -``` -@startuml -autonumber -participant "API Consumer" as cons -participant " API Producer " as prod -cons ->>prod: GET .../schemas -prod-->> cons : 200 OK (array(Schema)) -@enduml -``` - -![Sequence diagram showing the interaction between an API Consumer and an API Producer for the 'Get all schema information' operation. The consumer sends a GET request to .../schemas, and the producer responds with a 200 OK containing an array of schemas.](9fc0c37f0024c76bce2fb5115a7f2c50_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET .../schemas - API Producer-->>API Consumer: 2 200 OK (array(Schema)) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram showing the interaction between an API Consumer and an API Producer for the 'Get all schema information' operation. The consumer sends a GET request to .../schemas, and the producer responds with a 200 OK containing an array of schemas. - -Figure 8.3.4.1.1-1 Get all schema information operation. - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to API Producer. The target URI shall identify the resource (.../schemas). The API Producer shall process the request received in the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP GET response. On success "200 OK" shall be returned and the message content shall carry an array of schema. On failure, the appropriate error code shall be returned, and the message response body may contain additional error information. - -##### 8.3.4.1.2 Referenced procedures - -###### 8.3.4.1.2.1 Get schemas procedure - -The Get all schema information operation illustrated in figure 8.3.4.1.1-1 is based on Get schemas procedure defined in R1GAP [5]. - -### 8.3.4.2 Get Individual schema information - -#### 8.3.4.2.1 Operation definition - -An API consumer uses the Get Individual schema information to get one or more schemas of interest for a schemaId. - -``` -@startuml -autonumber -participant "API Consumer" as cons -participant " API Producer " as prod -cons ->>prod: GET .../schemas/{schemaId} -prod-->> cons : 200 OK (Schema) -@enduml -``` - -![Sequence diagram showing the interaction between an API Consumer and an API Producer. The API Consumer sends a GET request to the API Producer, and the API Producer returns a 200 OK response with a Schema.](97b3ed12d7f6c65cf3f7187326728409_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 GET .../schemas/{schemaId} - API Consumer->>API Producer: 1 GET .../schemas/{schemaId} - Note right of API Producer: 2 200 OK (Schema) - API Producer-->>API Consumer: 2 200 OK (Schema) -``` - -Sequence diagram showing the interaction between an API Consumer and an API Producer. The API Consumer sends a GET request to the API Producer, and the API Producer returns a 200 OK response with a Schema. - -Figure 8.3.4.2.1-1 retrieving specific schema API operation. - -The service operation is as follows: - -- 1) The API Consumer shall send an HTTP GET request to API Producer. The target URI shall identify the resource (.../schemas/{schemaId}), the message content shall be empty. The API Producer shall process the request received in the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -- 2) The API Producer shall return the HTTP GET response. On success "200 OK" shall be returned and the message content shall carry the Schema matching the API Consumer HTTP GET request URI and schemaId . On failure, the appropriate error code shall be returned, and the message response body may contain additional error information. - -#### 8.3.4.2.2 Referenced procedures - -##### 8.3.4.2.2.1 Get Schemas procedure - -The Get individual schema information operation illustrated in figure 8.3.4.2.1-1 is based on Get schemas procedure defined in R1GAP [5]. - -## 8.3.5 Resources - -### 8.3.5.1 Overview - -This clause defines the resources for the retrieving configuration schemas API. - -#### 8.3.5.2 Resource : " All schema information" - -##### 8.3.5.2.1 Description - -The resource represents a collection of configuration schema information. - -Only the methods defined in clause 8.3.3 shall be supported by this resource. - -### 8.3.5.2.2 Resource Definition - -Resource URI: {apiRoot}/ran-oam-cm-schema-info//schemas - -The resource URI variables supported by the resource is defined in table 8.3.5.2.2-1. - -**Table 8.3.5.2.2-1: Resource URI variables** - -| Name | Definition | -|------------|------------------| -| apiRoot | See clause 5.2 | -| apiVersion | See clause 8.3.2 | - -### 8.3.5.2.3 Resource Standard Methods - -#### 8.3.5.2.3.1 HTTP GET - -This method shall support the request data structure specified in table 8.3.5.2.3.1 -1 and the response data structures and response codes specified in 8.3.5.2.3.1 -2. - -**Table 8.3.5.2.3.1-1: Data structure supported by the GET request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|-------------------------------------------------------------| -| N/A | | | There is no object in the message content of a GET request. | - -**Table 8.3.5.2.3.1-2: Data structures supported by the GET Response Body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|--------------------------------------------------------------------------------------------| -| array(Schema) | O | 0..N | 200 OK | The results with the schema information | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -### 8.3.5.2.4 Resource Custom Operations - -None - -## 8.3.5.3 Resource: "Individual schema information" - -### 8.3.5.3.1 Description - -The resource represents a schema definition. - -Only the methods defined in clause 8.3.3 shall be supported by this resource. - -### 8.3.5.3.2 Resource Definition - -Resource URI: {apiRoot}/ran-oam-cm-schema-info//schemas/{schemaId} - -The resource URI variables supported by the resource is defined in the table 8.3.5.3.2-1. - -**Table 8.3.5.3.2-1: Resource URI variables** - -| Name | Definition | -|------------|---------------------------------------------------------------------------------------------------------------------------| -| apiRoot | See clause 5.2 | -| apiVersion | See clause 8.3.2 | -| schemaId | Where schemaId = "name" (for latest revision or if revision is not available) or "name@revision" for a specific revision. | - -### 8.3.5.3.3 Resource Standard Methods - -#### 8.3.5.3.3.1 HTTP GET - -This method shall support the request data structure specified in table 8.3.5.3.3.1 -1 and the response data structures and response codes specified in 8.3.5.3.3.1 -2. - -**Table 8.3.5.3.3.1-1: Data structure supported by the GET request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|-------------------------------------------------------------| -| N/A | | | There is no object in the message content of a GET request. | - -**Table 8.3.5.3.3.1-2: Data structures supported by the GET Response Body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|--------------------------------------------------------------------------------------------| -| Schema | M | 1 | 200 OK | The results with the schema information matching the request | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -#### 8.3.5.3.4 Resource Custom Operations - -None. - -### 8.3.6 Custom operations without associated resources - -None - -### 8.3.7 Notifications - -None - -### 8.3.8 Data model - -The following clause specifies the application data model supported by the retrieving configuration schemas API. - -#### 8.3.8.1 Data Type: Schema - -The Schema data type contains the attributes defined in table 8.3.8.1.1-1. - -**Table 8.3.8.1.1-1: Definition of type Schema** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|---------------|---|-------------|------------------------------------------------| -| name | string | M | 1 | The unique name of the schema | -| revision | string | C | 0..1 | The unique revision of the schema (See NOTE 3) | -| location | Uri | M | 1 | Location of where to find the schema content | -| type | SchemaType | M | 1 | See clause 8.3.8.2.3.1. (See NOTE 2). | -| namespace | string | O | 0..1 | The namespace of the schema, (See NOTE 1). | -| features | Array(string) | O | 0..N | List of supported features (See NOTE 1). | -| deviations | Array(string) | O | 0..N | List of schema deviation(s) (See NOTE 1). | - -NOTE 1: Only applicable if type is YANG. -NOTE 2: This data type is designed to provide extensibility. As specified in clause 8.3.8.2.3.1, Only YANG is supported in the present version of the present document. -NOTE 3 : this attribute is required for YANG. - -### 8.3.8.2 Simple data types and enumerations - -#### 8.3.8.2.1 Introduction - -The following clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. - -#### 8.3.8.2.2 Simple data types - -None. - -#### 8.3.8.2.3 Enumerations - -##### 8.3.8.2.3.1 Enumeration: SchemaTypes - -**Table 8.3.8.2.3.1-1: Enumeration SchemaTypes.** - -| Enumeration value | Description | -|-------------------|-------------| -| YANG | YANG schema | - -### 8.3.8.3 Re-used data types - -None. - -## 8.3.9 Error Handling - -### 8.3.9.1 General - -In addition to the general provisions in clause 5.4.3, the requirements in the following clauses are applicable for the retrieving configuration schema API. - -### 8.3.9.2 Protocol Errors - -No specific protocol errors are defined in the present document. - -### 8.3.9.3 Application Errors - -No specific protocol errors are defined in the present document. - -## 9. A1 related services - -### 9.1 A1 policy management API - -#### 9.1.1 Introduction - -This API allows the API Consumer to Query policy types and create, query, update and delete A1 policies based on the procedures for “A1 policy management“ defined in R1GAP [5]. - -#### 9.1.2 API version - -For the A1 policy management API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 0, and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1] for a definition of the version fields). Consequently, the URI path segment shall be set to “v1“. - -#### 9.1.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined in clause 5.2. The resource URI variable shall be “a1-policy-management“. The for each resource shall be set as described in clause 9.1.5. - -Figure 9.1.3-1 shows the overall resource URI structure defined for the A1 policy management API for querying policy types and policies, for life cycle management of policies, and for subscriptions to A1 policy status notifications. - -![A hierarchical tree diagram showing the resource URI structure for the A1 policy management API. The root is {apiRoot}/a1-policy-management//, which branches into /policy-types and /policies. /policy-types branches into /{policyTypeId}. /policies branches into /{policyId} and /subscriptions. /{policyId} branches into /status. /subscriptions branches into /{subscriptionId}.](226da964acee69b4d04409dc4c06a042_img.jpg) - -``` - -graph TD - Root["{apiRoot}/a1-policy-management//"] --> PolicyTypes["/policy-types"] - Root --> Policies["/policies"] - PolicyTypes --> PolicyTypeId["/{policyTypeId}"] - Policies --> PolicyId["/{policyId}"] - Policies --> Subscriptions["/subscriptions"] - PolicyId --> Status["/status"] - Subscriptions --> SubscriptionId["/{subscriptionId}"] - -``` - -A hierarchical tree diagram showing the resource URI structure for the A1 policy management API. The root is {apiRoot}/a1-policy-management//, which branches into /policy-types and /policies. /policy-types branches into /{policyTypeId}. /policies branches into /{policyId} and /subscriptions. /{policyId} branches into /status. /subscriptions branches into /{subscriptionId}. - -**Figure 9.1.3-1: Resource URI structure of the A1 policy management API.** - -Table 9.1.3-1 lists the individual resources defined for the API, the applicable HTTP methods, and the associated service operations. - -**Table 9.1.3-1: Resources and methods overview of the A1 policy management API** - -| Resource name | Resource URI | HTTP method | Service Operation | -|------------------------------------------|---------------------------------------------|-------------|---------------------------------------| -| All A1 policy types | .../policy-types | GET | Query A1 policy type identifiers. | -| Individual A1 policy type | .../policy-types/{policyTypeId} | GET | Query A1 policy type. | -| All A1 policies | .../policies | GET | Query A1 policy identifiers. | -| | | POST | Create A1 policy. | -| Individual A1 policy | .../policies/{policyId} | GET | Query A1 policy. | -| | | PUT | Update A1 policy. | -| | | DELETE | Delete A1 policy. | -| Individual A1 policy status | .../policies/{policyId}/status | GET | Query A1 policy status. | -| All A1 policy status subscriptions | .../policies/subscriptions | POST | Subscribe A1 policy status. | -| Individual A1 policy status subscription | .../policies/subscriptions/{subscriptionId} | PUT | Update A1 policy status subscription. | -| | | GET | Query A1 policy status subscription. | -| | | DELETE | Unsubscribe A1 policy status. | -| Policy status change notifications | {notificationDestination} | POST | Notify A1 policy status changes. | - -## 9.1.4 Service operations - -### 9.1.4.1 Query A1 policy type identifiers - -#### 9.1.4.1.1 Operation definition - -The API Consumer uses this operation to query available A1 policy type identifiers. - -The operation to query available A1 policy type identifiers is based on HTTP GET. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer --> Producer: GET .../policy-types -Producer --> Consumer : 200 OK (array(PolicyTypeInfo)) -@enduml -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for the 'Query A1 policy type identifiers' operation. The Consumer sends a GET request to the Producer, and the Producer responds with a 200 OK status containing an array of PolicyTypeInfo.](ffefa4f6eab4ce450aa5ecd3d3fd70bb_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET .../policy-types - API Producer-->>API Consumer: 2 200 OK (array(PolicyTypeInfo)) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for the 'Query A1 policy type identifiers' operation. The Consumer sends a GET request to the Producer, and the Producer responds with a 200 OK status containing an array of PolicyTypeInfo. - -**Figure 9.1.4.1.1-1: Query A1 policy type identifiers operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource “/policy-types“ and optionally query parameters, the message content shall be empty. The API Producer shall process - -the request received in the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. - -2. The API Producer shall return the HTTP GET response. On success, “200 OK“ shall be returned. The message content shall carry an array of policy type information representing available policy types and for each policy type identifier the Near-RT RIC identifiers of those Near-RT RICs that support the related A1 policy type. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -NOTE: The behavior of the query parameters is specified in table 9.1.5.2.3.1-3. - -### 9.1.4.1.2 Referenced procedures. - -#### 9.1.4.1.2.1 Query A1 policy type identifiers procedure - -The Query A1 policy type identifiers API operation illustrated in figure 9.1.4.1.1-1 is based on the Query A1 policy type identifiers procedure defined in R1GAP [5]. - -### 9.1.4.2 Query A1 policy type - -#### 9.1.4.2.1 Operation definition - -The API Consumer uses this operation to query an A1 policy type. - -The Query A1 policy type operation is based on HTTP GET. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: GET .../policy-types/{policyTypeId} -Producer -->> Consumer : 200 OK (PolicyTypeObject) -@enduml -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for the Query A1 policy type operation. The API Consumer sends a GET request to the API Producer, and the API Producer responds with a 200 OK status and a PolicyTypeObject.](85e7d6eb95be2fe34f09499ca16536de_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET .../policy-types/{policyTypeId} - API Producer-->>API Consumer: 2 200 OK (PolicyTypeObject) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for the Query A1 policy type operation. The API Consumer sends a GET request to the API Producer, and the API Producer responds with a 200 OK status and a PolicyTypeObject. - -Figure 9.1.4.2.1-1: Query A1 policy type operation. - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the policy type to be read based on the policyTypeId under the resource “/policy-types“. The message content shall be empty. The API Producer shall process the request received in the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP GET response. On success, “200 OK“ shall be returned. The message content shall carry a PolicyTypeObject representing the read policy type. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -9.1.4.2.2 Referenced procedures. - -9.1.4.2.2.1 Query A1 policy type procedure - -The Query A1 policy type API operation illustrated in figure 9.1.4.2.1-1 is based on the Query A1 policy type procedure defined in R1GAP [5]. - -9.1.4.3 Query A1 policy identifiers - -9.1.4.3.1 Operation definition - -The API Consumer uses this operation to query A1 policy identifiers. - -The operation to query A1 policy identifiers is based on HTTP GET. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: GET .../policies -Producer -->> Consumer : 200 OK (array(PolicyInformation)) -@enduml -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for the Query A1 policy identifiers operation. The API Consumer sends a GET request to the API Producer, and the API Producer responds with a 200 OK status containing an array of PolicyInformation.](80d994053160f3b1d88b075564af9e57_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET .../policies - API Producer-->>API Consumer: 2 200 OK (array(PolicyInformation)) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for the Query A1 policy identifiers operation. The API Consumer sends a GET request to the API Producer, and the API Producer responds with a 200 OK status containing an array of PolicyInformation. - -Figure 9.1.4.3.1-1: Query A1 policy identifiers operation. - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource “/policies“ and optionally query parameters. The message content shall be empty. The API Producer shall process the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP GET response. On success, “200 OK“ shall be returned. The message content shall carry an array of policy information which includes Near-RT RIC identifiers where A1 policies exist and for each Near-RT RIC identifier the policy identifiers of those policies that exist in that Near-RT RIC. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -NOTE: The behavior of the query parameters is specified in table 9.1.5.2.3.1-3. - -9.1.4.3.2 Referenced procedures. - -9.1.4.3.2.1 Query A1 policy identifiers procedure - -The Query A1 policy identifiers API operation illustrated in figure 9.1.4.3.1-1 is based on the Query A1 policy identifiers procedure defined in R1GAP [5]. - -### 9.1.4.4 Create A1 policy - -#### 9.1.4.4.1 Operation definition - -The API Consumer uses this operation to create an A1 policy. - -The Create A1 policy operation is based on HTTP POST. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer ->> Producer: POST .../policies(PolicyObjectInformation) -Producer ->> Consumer : 201 Created(PolicyObjectInformation) - -@enduml -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for the Create A1 policy operation. The API Consumer sends a POST request to the API Producer, and the API Producer responds with a 201 Created status.](09ec8c855800290ecbc282cfef399c32_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 POST .../policies(PolicyObjectInformation) - API Producer-->>API Consumer: 2 201 Created (PolicyObjectInformation) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for the Create A1 policy operation. The API Consumer sends a POST request to the API Producer, and the API Producer responds with a 201 Created status. - -**Figure 9.1.4.4.1-1: Create A1 policy operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP POST request to the API Producer. The target URI shall identify the resource “/policies” under which the A1 policy shall be created. The message content shall carry a PolicyObjectInformation which includes a nearRtRicId and a PolicyObject. The API Producer shall process the HTTP POST message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP POST response. On success, “201 Created” shall be returned. The message content shall carry the PolicyObjectInformation, and the “Location” HTTP header shall be present and shall carry the URI for the newly created service resource with policyId assigned by the API Producer. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -#### 9.1.4.4.2 Referenced procedures. - -##### 9.1.4.4.2.1 Create A1 policy procedure. - -The Create A1 policy API operation illustrated in figure 9.1.4.4.1-1 is based on the Create A1 policy procedure defined in R1GAP [5]. - -### 9.1.4.5 Query A1 policy - -#### 9.1.4.5.1 Operation definition - -The API Consumer uses this operation to query an A1 policy. - -The Query A1 policy operation is based on HTTP GET. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer --> Producer: GET .../policies/{policyId} -Producer --> Consumer : 200 OK (PolicyObject) -@enduml -``` - -![Sequence diagram showing the interaction between an API Consumer and an API Producer for the Query A1 policy operation. The Consumer sends a GET request to the Producer, and the Producer responds with a 200 OK status and a PolicyObject.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET .../policies/{policyId} - API Producer-->>API Consumer: 2 200 OK (PolicyObject) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram showing the interaction between an API Consumer and an API Producer for the Query A1 policy operation. The Consumer sends a GET request to the Producer, and the Producer responds with a 200 OK status and a PolicyObject. - -**Figure 9.1.4.5.1-1: Query A1 policy operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the policy to be read based on the policyId under the resource “/policies“. The message content shall be empty. The API Producer shall process the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP GET response. On success, “200 OK“ shall be returned. The message content shall carry a PolicyObject representing the read policy. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -**9.1.4.5.2 Referenced procedures.** - -**9.1.4.5.2.1 Query A1 policy procedure** - -The Query A1 policy API operation illustrated in figure 9.1.4.5.1-1 is based on the Query A1 policy procedure defined in R1GAP [5]. - -**9.1.4.6 Update A1 policy** - -**9.1.4.6.1 Operation definition** - -The API Consumer uses this operation to update an A1 policy. - -The Update A1 policy operation is based on HTTP PUT. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer --> Producer: PUT.../policies/{policyId}(PolicyObject) -Producer --> Consumer : 200 OK (PolicyObject) -@enduml -``` - -![Sequence diagram for Update A1 policy operation. It shows an API Consumer sending a PUT request to an API Producer, and the API Producer responding with a 200 OK status.](238754529581b74f0696943d436494bb_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - API Consumer->>API Producer: 1 PUT.../policies/{policyId}(PolicyObject) - API Producer-->>API Consumer: 2 200 OK (PolicyObject) - -``` - -Sequence diagram for Update A1 policy operation. It shows an API Consumer sending a PUT request to an API Producer, and the API Producer responding with a 200 OK status. - -Figure 9.1.4.6.1-1: Update A1 policy operation. - -The service operation is as follows: - -1. The API Consumer shall send an HTTP PUT request to the API Producer. The target URI shall identify the policy to be updated based on the policyId under the resource “/policies“. The message content shall contain a PolicyObject. The API Producer shall process the HTTP PUT message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP PUT response. On success, “200 OK“ shall be returned. The message content shall carry a PolicyObject representing the updated policy. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -### 9.1.4.6.2 Referenced procedures. - -#### 9.1.4.6.2.1 Update A1 policy procedure - -The Update A1 policy API operation illustrated in figure 9.1.4.6.1-1 is based on the Update A1 policy procedure defined in R1GAP [5]. - -### 9.1.4.7 Delete A1 policy - -#### 9.1.4.7.1 Operation definition - -The API Consumer uses this operation to delete an A1 policy. - -The Delete A1 policy operation is based on HTTP GET. - -``` - -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer ->> Producer: DELETE.../policies/{policyId} -Producer ->> Consumer : 204 No Content -@enduml - -``` - -![Sequence diagram for Delete A1 policy operation. It shows an API Consumer sending a DELETE request to an API Producer, and the API Producer responding with a 204 No Content status.](528f6dcec0ac99b060b0da5883c82b8f_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - API Consumer->>API Producer: 1 DELETE.../policies/{policyId} - API Producer-->>API Consumer: 2 204 No Content - -``` - -Sequence diagram for Delete A1 policy operation. It shows an API Consumer sending a DELETE request to an API Producer, and the API Producer responding with a 204 No Content status. - -**Figure 9.1.4.7.1-1: Delete A1 policy operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP DELETE request to the API Producer. The target URI shall identify the policy to be deleted based on the policyId under the resource “/policies“. The message content shall be empty. The API Producer shall process the HTTP DELETE message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP DELETE response. On success, “204 No Content“ shall be returned. The message content shall be empty. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -**9.1.4.7.2 Referenced procedures.** - -**9.1.4.7.2.1 Delete A1 policy procedure.** - -The Delete A1 policy API operation illustrated in figure 9.1.4.7.1-1 is based on the Delete A1 policy procedure defined in R1GAP [5]. - -**9.1.4.8 Query A1 policy status** - -**9.1.4.8.1 Operation definition** - -The API Consumer uses this operation to query A1 policy status. - -The operation to query A1 policy status is based on HTTP GET. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer --> Producer: GET .../policies/{policyId}/status -Producer --> Consumer : 200 OK (PolicyStatusObject) -@enduml -``` - -![Sequence diagram for Query A1 policy status operation. It shows two lifelines: API Consumer and API Producer. The API Consumer sends a GET request to the API Producer for the resource .../policies/{policyId}/status. The API Producer responds with a 200 OK status containing a PolicyStatusObject.](7ef82ab74729923b27507495301d73a6_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 GET .../policies/{policyId}/status - API Consumer->>API Producer: 1 GET .../policies/{policyId}/status - Note right of API Producer: 2 200 OK (PolicyStatusObject) - API Producer-->>API Consumer: 2 200 OK (PolicyStatusObject) -``` - -Sequence diagram for Query A1 policy status operation. It shows two lifelines: API Consumer and API Producer. The API Consumer sends a GET request to the API Producer for the resource .../policies/{policyId}/status. The API Producer responds with a 200 OK status containing a PolicyStatusObject. - -**Figure 9.1.4.8.1-1: Query A1 policy status operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource “.../policies/{policyId}/status“. The message content shall be empty. The API Producer shall process the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP GET response. On success, “200 OK“ shall be returned. The message content shall carry a PolicyStatusObject representing the status of the A1 policy. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -### 9.1.4.8.1 Referenced procedures - -#### 9.1.4.8.1.1 Query A1 policy status procedure - -The Query A1 policy status operation illustrated in figure 9.1.4.8.1-1 is based on the Query A1 policy enforcement status procedure defined in R1GAP [5]. - -### 9.1.4.9 Subscribe A1 policy status - -#### 9.1.4.9.1 Operation definition - -The API Consumer uses this operation to subscribe to notifications for status changes of A1 policies. - -The operation to subscribe to A1 policy status is based on HTTP POST. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer --> Producer: POST .../policies/subscriptions (PolicyStatusSubscription) -Producer --> Consumer : 201 Created (PolicyStatusSubscription) -@enduml -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for subscribing to A1 policy status. The API Consumer sends a POST request to the API Producer, and the API Producer responds with a 201 Created status.](b5d72de0273027513b3c617a66f6ab1b_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 POST .../policies/subscriptions (PolicyStatusSubscription) - API Producer-->>API Consumer: 2 201 Created (PolicyStatusSubscription) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for subscribing to A1 policy status. The API Consumer sends a POST request to the API Producer, and the API Producer responds with a 201 Created status. - -**Figure 9.1.4.9.1-1: Subscribe to A1 policy status operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP POST request to the API Producer. The target URI shall identify the resource “/policies/subscriptions“ under which the new subscription is requested to be created. The message content shall carry a PolicyStatusSubscription structure. The API Producer shall process the request received in the HTTP POST message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP POST response. On success, “201 Created“ shall be returned. The location header shall be present and shall carry the URI of new subscription resource with subscriptionId assigned by the API producer. The message content shall carry a PolicyStatusSubscription structure that represents the new resource. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 9.1.4.9.2 Referenced procedures - -##### 9.1.4.9.2.1 Subscribe A1 policy status procedure - -The Subscribe A1 policy status operation illustrated in figure 9.1.4.9.1-1 is based on the Subscribe A1 policy status procedure defined in R1GAP [5]. - -### 9.1.4.10 Update A1 policy status subscription - -#### 9.1.4.10.1 Operation definition - -The API Consumer uses this operation to update a subscription for A1 policy status notifications. - -The operation to update an individual A1 policy status subscription is based on HTTP PUT. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer --> Producer: PUT .../policies/subscriptions/{subscriptionId}\n( -PolicyStatusSubscription) -Producer --> Consumer : 200 OK (PolicyStatusSubscription) -@enduml -``` - -![Sequence diagram showing the Update A1 policy status subscription operation. The API Consumer sends a PUT request to the API Producer, and the API Producer responds with a 200 OK status.](aa22da43c463563d3d0035722bd79449_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 - API Consumer->>API Producer: PUT .../policies/subscriptions/{subscriptionId} (PolicyStatusSubscription) - Note right of API Producer: 2 - API Producer-->>API Consumer: 200 OK (PolicyStatusSubscription) -``` - -Sequence diagram showing the Update A1 policy status subscription operation. The API Consumer sends a PUT request to the API Producer, and the API Producer responds with a 200 OK status. - -**Figure 9.1.4.10.1-1: Update A1 policy status subscription operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP PUT request to the API Producer. The target URI shall identify the resource (.../policies/subscriptions / {subscriptionId}). The message content shall carry the updated PolicyStatusSubscription structure. The API Producer shall process the request received in the HTTP PUT message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP PUT response. On success, “200 OK“ shall be returned. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 9.1.4.10.2 Referenced procedures. - -##### 9.1.4.10.2.1 Update A1 policy status subscription procedure - -The Update A1 policy status subscription operation illustrated in figure 9.1.4.10.1-1 is based on the Update A1 policy status procedure defined in RIGAP [5]. - -### 9.1.4.11 Query A1 policy status subscription - -#### 9.1.4.11.1 Operation definition - -The API Consumer uses this operation to query a subscription for A1 policy status. - -The operation to query an individual A1 policy status subscription is based on HTTP GET. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer --> Producer: GET .../policies/subscriptions/{subscriptionId} -Producer --> Consumer : 200 OK (PolicyStatusSubscription) -``` - -``` -@enduml -``` - -![Sequence diagram for Query A1 policy status subscription operation. It shows an API Consumer sending a GET request to an API Producer, which responds with a 200 OK containing a PolicyStatusSubscription object.](a5404b7275b06497eecf9b5883604753_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - API Consumer->>API Producer: 1 GET .../policies/subscriptions/{subscriptionId} - API Producer-->>API Consumer: 2 200 OK (PolicyStatusSubscription) - -``` - -Sequence diagram for Query A1 policy status subscription operation. It shows an API Consumer sending a GET request to an API Producer, which responds with a 200 OK containing a PolicyStatusSubscription object. - -**Figure 9.1.4.11.1-1: Query A1 policy status subscription operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource “/policies/subscriptions/{subscriptionId}“. The message content shall be empty. The API Producer shall process the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP GET response. On success, “200 OK“ shall be returned. The message content shall carry the PolicyStatusSubscription representing the queried policy status subscription. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -**9.1.4.11.2 Referenced procedures.** - -**9.1.4.11.2.1 Query A1 policy status subscription procedure** - -The Query A1 policy status subscription operation illustrated in figure 9.1.4.11.1-1 is based on the Query A1 policy status subscription procedure defined in R1GAP [5]. - -**9.1.4.12 Unsubscribe A1 policy status** - -**9.1.4.12.1 Operation definition** - -The API Consumer uses this operation to unsubscribe from notifications on status changes of A1 policies. - -The operation to unsubscribe from A1 policy status notifications is based on HTTP DELETE. - -``` - -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer ->> Producer: DELETE .../policies/subscriptions/{subscriptionId} -Producer ->> Consumer : 204 No Content -@enduml - -``` - -![Sequence diagram for Unsubscribe from A1 policy status operation. It shows an API Consumer sending a DELETE request to an API Producer, which responds with a 204 No Content.](627bd3eabebc7105a04e854f2c59f47d_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - API Consumer->>API Producer: 1 DELETE .../policies/subscriptions/{subscriptionId} - API Producer-->>API Consumer: 2 204 No Content - -``` - -Sequence diagram for Unsubscribe from A1 policy status operation. It shows an API Consumer sending a DELETE request to an API Producer, which responds with a 204 No Content. - -**Figure 9.1.4.12.1-1: Unsubscribe from A1 policy status operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP DELETE request to the API Producer. The target URI shall identify the resource “/policies/subscriptions/{subscriptionId}“. The message content shall be empty. The API Producer shall process the request received in the HTTP DELETE message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP DELETE response. On success, “204 No Content“ shall be returned. The message content shall be empty. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -**9.1.4.12.2 Referenced procedures.** - -**9.1.4.12.2.1 Unsubscribe A1 policy status procedure** - -The Unsubscribe A1 policy status operation illustrated in figure 9.1.4.12.1-1 is based on the Unsubscribe A1 policy status procedure defined in R1GAP [5]. - -**9.1.4.13 Notify A1 policy status changes** - -**9.1.4.13.1 Operation definition** - -The API Producer uses this operation to notify the API Consumer about status changes of an A1 policy. - -The operation to notify A1 policy status is based on HTTP POST. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Producer --> Consumer : POST ../{notificationDestination} (A1PolicyStatusChangeNotification) -Consumer --> Producer : 204 No Content -@enduml -``` - -![Sequence diagram showing the Notify A1 policy status changes API operation. The API Producer sends a POST request to the API Consumer, and the API Consumer responds with 204 No Content.](e845d172f83764c1db7998397af2b9d5_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - API Producer->>API Consumer: 1 POST ../{notificationDestination}(A1PolicyStatusChangeNotification) - API Consumer-->>API Producer: 2 204 No Content - -``` - -Sequence diagram showing the Notify A1 policy status changes API operation. The API Producer sends a POST request to the API Consumer, and the API Consumer responds with 204 No Content. - -**Figure 9.1.4.13.1-1: Notify A1 policy status changes API operation.** - -The service operation is as follows: - -1. The API Producer shall send an HTTP POST request to the API Consumer . The target URI (notificationDestination) identifies the sink for policy status change notifications. The message body shall contain a A1PolicyStatusChangeNotifications. -2. The API Consumer shall return the HTTP POST response with “204 No Content“. The message body shall be empty. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -**9.1.4.13.2 Referenced procedures.** - -**9.1.4.13.2.1 Notify A1 policy status procedure** - -The Notify A1 policy status changes operation illustrated in figure 9.1.4.13.1-1 is based on the Notify A1 policy status changes procedure defined in R1GAP [5]. - -## 9.1.5 Resources - -### 9.1.5.1 Overview - -This clause defines the resources for the A1 policy management API. - -### 9.1.5.2 Resource: "All A1 policy types" - -#### 9.1.5.2.1 Description - -The resource All A1 policy types represents all A1 policy types that are available in all Near-RT RIC's over the A1 Interface. - -The methods defined in clause 9.1.5.2.3 shall be supported by these resources. - -#### 9.1.5.2.2 Resource Definition - -Resource URI: {apiRoot}/a1-policy-management //policy-types - -The resource URI variables supported by the resource are defined in Table 9.1.5.2.2-1. - -**Table 9.1.5.2.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|-------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 9.1.2. | - -#### 9.1.5.2.3 Resource Standard Methods - -##### 9.1.5.2.3.1 GET - -This method shall support the URI query parameters specified in table 9.1.5.2.3.1-1, the request data structure specified in the table 9.1.5.2.3.1-2 and the response data structures, and response code specified in the table 9.1.5.2.3.1-3. - -**Table 9.1.5.2.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | Applicability | -|-------------|-----------|---|-------------|-------------------------------------------------|---------------| -| nearRtRicId | string | O | 0..1 | The identifier of Near-RT RIC (See NOTE). | | -| typeName | string | O | 0..1 | The unique label of the policy type (See NOTE). | | - -NOTE: If multiple query parameters are provided these shall be combined with AND when evaluating the query. - -**Table 9.1.5.2.3.1-2: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|---------------------------------------------------------------| -| N/A | | | There is no object in the message content of the GET request. | - -**Table 9.1.5.2.3.1-3: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|-----------------------|---|-------------|----------------|---------------------------------------------------------------------------------------------| -| array(PolicyTypeInfo) | M | 0.. N | 200 OK | The operation is successful, the policy type information. (See NOTE1 ,NOTE 2 , and NOTE 3). | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -NOTE 1: If a Near-RT RIC identifier has been provided as query parameter, the response body shall contain only entries for policy types supported by the related Near-RT RIC. -NOTE 2: If a policy type identifier has been provided as query parameter, the response body shall contain only entries for the related policy type. -NOTE 3: If both a Near-RT RIC identifier and a policy type identifier have been provided as query parameters, the response body shall contain only entries for the related policy type supported by the related Near-RT RIC. - -#### 9.1.5.2.4 Resource Custom Operations - -None. - -### 9.1.5.3 Resource: "Individual A1 policy type" - -#### 9.1.5.3.1 Description - -The resource individual A1 policy type represents the A1 policy type that are available in the A1 policy management service. Only the methods defined in clause 9.1.5.3.3 shall be supported by these resources. - -#### 9.1.5.3.2 Resource Definition - -Resource URI: {apiRoot}/a1-policy-management //policy-types/{policyTypeId} - -The resource URI variables supported by the resource are defined in Table 9.1.5.3.2-1. - -**Table 9.1.5.3.2-1: Resource URI variables for the resource** - -| Name | Definition | -|--------------|-----------------------------------------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 9.1.2. | -| policyTypeId | The policy type identifier as defined in A1TD [24]. | - -### 9.3.5.3.3 Resource Standard Methods - -#### 9.3.5.3.3.1 GET - -This method shall support the URI query parameters specified in table 9.1.5.3.3.1-1, and the response data structure and response code specified in the table 9.1.5.3.3.1-2. - -**Table 9.1.5.3.3.1-1: Data structures supported by the HTTP GET request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|-------------------------------------------------------------| -| N/A | | | There is no object in the message content of a GET request. | - -**Table 9.1.5.3.3.1-2: Data structures supported by the HTTP GET response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|------------------|---|-------------|----------------|-------------------------------------------------------| -| PolicyTypeObject | M | 1 | 200 OK | Requested policy type object as defined in A1TD [24]. | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description. | - -### 9.1.5.3.4 Resource Custom Operations - -None. - -## 9.1.5.4 Resource: "All A1 policies" - -### 9.1.5.4.1 Description - -The resource All A1 policies represents the A1 policy that are available in the A1 policy management service. - -Only the methods defined in clause 9.1.5.4.3 shall be supported by these resources. - -### 9.1.5.4.2 Resource Definition - -Resource URI: {apiRoot}/a1-policy-management //policies - -The resource URI variables supported by the resource are defined in Table 9.1.5.4.2-1. - -**Table 9.1.5.4.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|-------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 9.1.2. | - -### 9.1.5.4.3 Resource Standard Methods - -#### 9.1.5.4.3.1 GET - -This method shall support the URI query parameters specified in table 9.1.5.4.3.1-1, the request data structure specified in the table 9.1.5.4.3.1-2 and the response data structure and response code specified in the table 9.1.5.4.3.1-3. - -**Table 9.1.5.4.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | Applicability | -|-------------------------------------------------------------------------------------------------------------|-----------|---|-------------|-------------------------------------------|---------------| -| nearRtRicId | string | O | 0..1 | The identifier of Near-RT RIC (See NOTE). | | -| policyTypeId | string | O | 0..1 | The identifier of the policy (See NOTE). | | -| NOTE: If multiple query parameters are provided these shall be combined with AND when evaluating the query. | | | | | | - -**Table 9.1.5.4.3.1-2: Data structures supported by the HTTP GET request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|------------------------------------------------------------| -| N/A | | | There is no object in the message content of a GET request | - -**Table 9.1.5.4.3.1-3: Data structures supported by the HTTP GET response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|-------------|----------------|--------------------------------------------------------------------------------------------------| -| array(PolicyInformation) | M | 0..N | 200 OK | The operation is successful, and the response body carries a list of policy information entries. | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | -| NOTE 1: If a Near-RT RIC identifier has been provided as query parameter, the response body shall contain only entries for policies existing in the related Near-RT RIC.
NOTE 2: If a policy type identifier has been provided as query parameter, the response body shall contain only entries for policies of the related policy type.
NOTE 3: If both a Near-RT RIC identifier and a policy type identifier have been provided as query parameters, the response body shall contain only entries for policies of the related policy type existing in the related Near-RT RIC. | | | | | - -#### 9.1.5.4.3.2 POST - -This method shall support the request data structures specified in table 9.1.5.4.3.2-1 and the response data structures and response codes specified in table 9.1.5.4.3.2-2 and the HTTP headers specified in table 9.1.5.4.3.2-3. - -**Table 9.1.5.4.3.2-1: Data structures supported by the HTTP POST request body on this resource.** - -| Data type | P | Cardinality | Description | -|-------------------------|---|-------------|----------------------------------------------------| -| PolicyObjectInformation | M | 1 | Information related to the creation of the policy. | - -**Table 9.1.5.4.3.2-2: Data structures supported by the HTTP POST response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|-------------------------|---|-------------|----------------|-----------------------------------------| -| PolicyObjectInformation | M | 1 | 201 Created | Confirmation of creation of the policy. | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description. | - -**Table 9.1.5.4.3.2-3: Headers supported by the 201 Response Code on this resource.** - -| Name | Data type | P | Cardinality | Description | -|----------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------| -| Location | string | M | 1 | Contains the URI of the newly created “Individual registered” A1 policy resource, as defined in clause 9.1.5.3, with the policyId in the URI. | - -#### 9.1.5.4.4 Resource Custom Operations - -None. - -### 9.1.5.5 Resource: "Individual A1 policy" - -#### 9.1.5.5.1 Description - -The resource Individual A1 policy represents an A1 policy created by the A1 policy management service. - -Only the methods defined in clause 9.1.5.5.3 shall be supported by these resources. - -#### 9.1.5.5.2 Resource Definition - -Resource URI: {apiRoot}/a1-policy-management //policies/{policyId} - -The resource URI variables supported by the resource are defined in Table 9.1.5.5.2-1. - -**Table 9.1.5.5.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|----------------------------------------------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 9.1.2. | -| policyId | Policy Identifier of the policy as defined in A1AP [23]. | - -#### 9.1.5.5.3 Resource Standard Methods - -##### 9.1.5.5.3.1 PUT - -This method shall support the request data structures specified in table 9.1.5.5.3.1-1 and the response data structure and response codes specified in table 9.1.5.5.3.1-2. - -**Table 9.1.5.5.3.1-1: Data structures supported by the HTTP PUT request body on this resource.** - -| Data type | P | Cardinality | Description | -|--------------|---|-------------|--------------------| -| PolicyObject | M | 1 | Update the Policy. | - -**Table 9.1.5.5.3.1-2: Data structures supported by the HTTP PUT response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|---------------------------------| -| PolicyObject | M | 1 | 200 OK | Confirmation of updated policy. | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description. | - -#### 9.1.5.5.3.2 GET - -This method shall support the request data structures specified in table 9.1.5.5.3.2-1 and the response data structures and response codes specified in table 9.1.5.5.3.2-2. - -**Table 9.1.5.5.3.2-1: Data structures supported by the HTTP GET request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|-------------------------------------------------------------| -| N/A | | 0 | There is no object in the message content of a GET request. | - -**Table 9.1.5.5.3.2-2: Data structures supported by the HTTP GET response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|-------------------------------| -| PolicyObject | M | 1 | 200 OK | Requested policy object. | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description. | - -#### 9.1.5.5.3.3 DELETE - -This method shall support the request data structures specified in table 9.1.5.5.3.3-1 and the response data structures and response codes specified in table 9.1.5.5.3.3-2. - -**Table 9.1.5.5.3.3-1: Data structures supported by the HTTP DELETE request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|----------------------------------------------------------------| -| N/A | | | There is no object in the message content of a DELETE request. | - -**Table 9.1.5.5.3.3-2: Data structures supported by the HTTP DELETE response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|--------------------------------------| -| N/A | | | 204 No content | Confirmation of successful deletion. | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description. | - -#### 9.1.5.5.4 Resource Custom Operations - -None. - -### 9.1.5.6 Resource: "Individual A1 policy status" - -#### 9.1.5.6.1 Description - -The resource Individual A1 policy status represents the status of an A1 policy that is available in the A1 policy management service. - -Only the methods defined in clause 9.1.5.6.3 shall be supported by these resources. - -#### 9.1.5.6.2 Resource Definition - -Resource URI: {apiRoot}/a1-policy-management //policies/{policyId}/status - -The resource URI variables supported by the resource are defined in Table 9.1.5.6.2-1. - -**Table 9.1.5.6.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|-------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 9.1.2. | - -#### 9.1.5.6.3 Resource Standard Methods - -##### 9.1.5.6.3.1 GET - -This method shall support the request data structures specified in table 9.1.5.6.3.1-1 and the response data structures and response codes specified in table 9.1.5.6.3.1-2. - -**Table 9.1.5.6.3.1-1: Data structures supported by the HTTP GET request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|-------------------------------------------------------------| -| N/A | | 0 | There is no object in the message content of a GET request. | - -**Table 9.1.5.6.3.1-2: Data structures supported by the HTTP GET response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|--------------------|---|-------------|----------------|----------------------------------------------------------------------| -| PolicyStatusObject | M | 1 | 200 OK | Requested policy status object as defined in A1TD[24], clause 6.4.2. | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description. | - -#### 9.1.5.6.4 Resource Custom Operations - -None. - -### 9.1.5.7 Resource: "All A1 policy status subscriptions" - -#### 9.1.5.7.1 Description - -The resource represents the subscriptions for A1 policy status notifications. - -The methods defined in clause 9.1.5.7.3 shall be supported by this resource. - -### 9.1.5.7.2 Resource Definition - -Resource URI: {apiRoot}/a1-policy-management //policies/subscriptions - -The resource URI variables supported by the resource are defined in table 9.1.5.7.2-1. - -**Table 9.1.5.7.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|-------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 9.1.2. | - -### 9.1.5.7.3 Resource Standard Methods - -#### 9.1.5.7.3.1 POST - -This method shall support the request data structures specified in table 9.1.5.7.3.1-1 and the response data structures and response codes specified in table 9.1.5.7.3.1-2 and the HTTP headers specified in table 9.1.5.7.3.1-3. - -**Table 9.1.5.7.3.1-1: Data structures supported by the HTTP POST request body on this resource.** - -| Data type | P | Cardinality | Description | -|--------------------------|---|-------------|-----------------------------------------------------------| -| PolicyStatusSubscription | M | 1 | Information of A1 Policy status subscription information. | - -**Table 9.1.5.7.3.1-2: Data structures supported by the POST response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|--------------------------|---|-------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| -| PolicyStatusSubscription | M | 1 | 201 Created | The operation was successful.

The message content of the POST response contains a PolicyStatusSubscriptionInfo representing the created resource. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation was unsuccessful.

Detailed problem description may be carried in the response message content. | - -**Table 9.1.5.7.3.1-3: Headers supported by the 201-response code on the resource.** - -| Name | Data type | P | Cardinality | Description | -|----------|-----------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------| -| Location | String | M | 1 | Contains the URI of the newly created "Individual A1 policy status subscription" resource as defined in clause 9.1.5.5.2 with subscriptionId in the URI. | - -### 9.1.5.7.4 Resource Custom Operations - -None - -### 9.1.5.8 Resource: "Individual A1 policy status subscription" - -#### 9.1.5.8.1 Description - -The resource represents a subscription for A1 policy status notifications. - -The methods defined in clause 9.1.5.8.3 shall be supported by this resource. - -#### 9.1.5.8.2 Resource Definition - -Resource URI: {apiRoot}/a1-policy-management //policies/subscriptions/{subscriptionId} - -The resource URI variables supported by the resource are defined in Table 9.1.5.8.2-1. - -**Table 9.1.5.8.2-1: Resource URI variables for the resource** - -| Name | Definition | -|----------------|-----------------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 9.1.2. | -| subscriptionId | Identifier of subscription. | - -#### 9.1.5.8.3 Resource Standard Methods - -##### 9.1.5.8.3.1 PUT - -This method shall support the request data structures specified in table 9.1.5.8.3.1-1 and the response data structure and response codes specified in table 9.1.5.8.3.1-2. - -**Table 9.1.5.8.3.1-1: Data structures supported by the HTTP PUT request body on this resource.** - -| Data type | P | Cardinality | Description | -|--------------------------|---|-------------|-------------------------------------------------| -| PolicyStatusSubscription | M | 1 | Updated Policy status subscription information. | - -**Table 9.1.5.8.3.1-2: Data structures supported by the HTTP PUT response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|--------------------------|---|-------------|----------------|--------------------------------------------------------------------------------------------| -| PolicyStatusSubscription | M | 1 | 200 OK | Confirmation of updated policy status subscription. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -##### 9.1.5.8.3.2 GET - -This method shall support the request data structures specified in table 9.1.5.8.3.2-1 and the response data structures and response codes specified in table 9.1.5.8.3.2-2. - -**Table 9.1.5.8.3.2-1: Data structures supported by the HTTP GET request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|-------------------------------------------------------------| -| N/A | | 0 | There is no object in the message content of a GET request. | - -**Table 9.1.5.8.3.2-2: Data structures supported by the HTTP GET response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|--------------------------|---|-------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| PolicyStatusSubscription | M | 1 | 200 OK | Requested policy status subscription information associated with the subscriptionId has been queried successfully and the response contains the PolicyStatusSubscriptionInfo as representation of the queried resource. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -### 9.1.5.8.3.3 DELETE - -This method shall support the request data structures specified in table 9.1.5.8.3.3-1 and the response data structures and response codes specified in table 9.1.5.8.3.3-2. - -**Table 9.1.5.8.3.3-1: Data structures supported by the HTTP DELETE request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|----------------------------------------------------------------| -| N/A | | | There is no object in the message content of a DELETE request. | - -**Table 9.1.5.8.3.3-2: Data structures supported by the HTTP DELETE response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|--------------------------------------------------------------------------------------------| -| N/A | | | 204 No content | Confirmation of successful deletion. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -### 9.1.5.8.4 Resource Custom Operations - -None. - -## 9.1.6 Custom operation without associated resources - -None. - -## 9.1.7 Notifications - -### 9.1.7.1 Resource: Policy status change notifications - -#### 9.1.7.1.1 Description - -The resource represents the destination for A1 policy status change notifications. - -#### 9.1.7.1.2 Resource Definition - -The resource URI (notificationDestination) is provided when subscribing to A1 policy status notifications. - -### 9.1.7.1.3 Resource Standard Methods - -#### 9.1.7.1.3.1 POST - -This method shall support the request data structures specified in table 9.1.7.1.3.1-1 and the response data structure and response codes specified in table 9.1.7.1.3.1-2. - -**Table 9.1.7.1.3.1-1: Data structures supported by the HTTP POST request body on this resource** - -| Data type | P | Cardinality | Description | -|-----------------------------------|---|-------------|---------------------------------------------------------------| -| A1PolicyStatusChange Notification | M | 1 | Notify policy status change as specified in clause 9.1.8.1.6. | - -**Table 9.1.7.1.3.1-2.: Data structures supported by the HTTP POST response body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|-----------|---|-------------|----------------|----------------------------------------| -| N/A | | | 204 No content | Confirmation of received notification. | - -## 9.1.8 Data Model - -### 9.1.8.1 Structured data types - -#### 9.1.8.1.1 Overview - -The following clause defines the structured data types and their attributes to be used by the A1 policy management API. - -#### 9.1.8.1.2 Data type: PolicyTypeInfo - -The PolicyTypeInfo data type represents a pair of policy type identifier and related Near-RT RIC identifier. It contains the attributes defined in table 9.1.8.1.2-1. - -**Table 9.1.8.1.2-1: Definition of type PolicyTypeInfo.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-------------|---|-------------|-------------------------------------------------------------------| -| policyTypeId | string | M | 1 | Policy Type identifier as defined in A1AP [23], clause 6.2.3.1.3. | -| nearRtRicId | NearRtRicId | M | 1 | Near-RT RIC identifier. | - -The data model for the data types transported is defined in A1TD [24]. - -#### 9.1.8.1.3 Data type: PolicyInformation - -The PolicyInformation data type represents a pair of policy identifier and related Near-RT RIC identifier. It contains the attributes defined in table 9.1.8.1.3-1. - -**Table 9.1.8.1.3-1: Definition of type PolicyInformation.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-------------|---|-------------|--------------------------------------------------------| -| policyId | string | M | 1 | Policy Identifier of a policy as defined in A1AP [23]. | -| nearRtRicId | NearRtRicId | M | 1 | Near-RT RIC identifier. | - -9.1.8.4 Data type: PolicyObjectInformation - -The PolicyObjectInformation data type represents a policy object, related Near-RT RIC identifier and optional policy type identifier. It contains the attributes defined in table 9.1.8.1.4-1. - -**Table 9.1.8.1.4-1: Definition of type PolicyObjectInformation** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|--------------|---|-------------|-----------------------------------------------------------------------------------------------------| -| policyObject | object | M | 1 | Policy Object is a JSON representation of an A1 policy; the A1 policies are specified in A1TD [24]. | -| nearRtRicId | NearRtRicId | M | 1 | Near-RT RIC identifier. | -| policyTypeId | PolicyTypeId | O | 0..1 | policy type identifier as defined in A1AP [23]. | - -9.1.8.1.5 Data type: PolicyStatusSubscription - -The PolicyStatusSubscription data type represents the subscription information of A1 policy status. It contains the attributes defined in table 9.1.8.1.5-1. - -**Table 9.1.8.1.5-1: Definition of type PolicyStatusSubscription** - -| Attribute Name | Data type | P | Cardinality | Description | -|-------------------------|---------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------| -| subscriptionScope | QueryFilter | C | 1 | See clause 9.1.8.3.3.1.
See NOTE 2, NOTE 4, NOTE 6, NOTE 8, NOTE 10. | -| notificationDestination | URI | M | 1 | Call back URI for A1 policy status notifications | -| policyIdList | array(policyId) | C | 1..N | List of identifiers of A1 policies as defined in clause 6.2.6 of A1AP [23].
See NOTE 1 ,NOTE 3 and NOTE 4. | -| policyTypeIdList | array(policyTypeId) | C | 1..N | List of A1 policy type identifiers as defined in clause 9.1.5.4.3.1
See NOTE 1, NOTE 5, NOTE 6, NOTE9 and NOTE 10. | -| nearRtRicIdList | array(NearRtRicId) | C | 1..N | List of Near-RT RIC identifiers as defined in clause 9.1.5.4.3.1.
See NOTE 1, NOTE 7, NOTE 8, NOTE9 and NOTE 10. | - -NOTE 1: It is conditionally optional to include either a policyIdList; or a policyTypeIdList; or a nearRtRicIdList; or a policyTypeIdList and a nearRtRicIdList; or none of the lists. - -NOTE 2: If neither policyIdList nor policyTypeIdList nor nearRtRicIdList is provided, then a subscriptionScope shall be provided. - -NOTE 3: If a policyIdList is provided, the subscription is for the status of the indicated A1 policies. - -NOTE 4 : if a policyIdList is provided then subscriptionScope shall not be provided. - -NOTE 5: If a policyTypeIdList is provided, the subscription is for the status of A1 policies of the indicated A1 policy types. - -NOTE 6: If both policyTypeIdList and subscriptionScope are provided, then the subscription is for the status of A1 policies of the indicated A1 policy types that fulfill the subscriptionScope. - -NOTE 7: If a nearRtRicIdList is provided, the subscription is for the status of A1 policies created in the indicated Near-RT RICs. - -NOTE 8: If both nearRtRicIdList and subscriptionScope are provided, then the subscription is for the status of A1 policies created in the indicated Near-RT RICs that fulfill the subscriptionScope. - -NOTE 9: If both policyTypeIdList and nearRtRicIdList are provided, then the subscription is for the status of A1 policies of the indicated A1 policy types created in the indicated Near-RT RICs. - -NOTE 10: If policyTypeIdList, nearRtRicIdList and subscriptionScope are provided, then the subscription is for the status of A1 policies of the indicated A1 policy types created in the indicated Near-RT RICs that fulfill the subscriptionScope. - -#### 9.1.8.1.6 Data type: A1PolicyStatusChangeNotification - -**Table 9.1.8.1.6-1: Definition of type A1PolicyStatusChangeNotification** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|---------------------------------|---|-------------|--------------------------------------------------------------| -| subscriptionId | SubscriptionId | M | 1 | Identifier of Subscription as specified in clause 9.1.5.5.2. | -| policyStates | array(SubscriptionStatusObject) | M | 1..N | List of policy states to be notified about. | - -### 9.1.8.1.7 Data type: SubscriptionStatusObject - -**Table 9.1.8.1.7-1: Definition of type SubscriptionStatusObject** - -| Attribute Name | Data type | P | Cardinality | Description | -|--------------------|--------------------|---|-------------|-----------------------------------------------------------------| -| policyId | PolicyId | M | 1 | Policy identifier as specified in clause 6.2.6 of A1AP [23]. | -| policyStatusObject | PolicyStatusObject | M | 1..N | Policy status object as specified in clause 6.4.2 of A1TD [24]. | - -## 9.1.8.2 Simple data types and enumerations - -### 9.1.8.2.1 Introduction - -The following clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. - -### 9.1.8.2.2 Simple data types - -The resource identifiers defined in clause include policy type identifier and policy identifier based on the simple data types specified in table 9.1.8.2.2-1. - -**Table 9.1.8.2.2-1: General definition of simple data types** - -| Type Name | Type Definition | Description | Applicability | -|--------------|-----------------|-------------------------------------------------------------|---------------| -| PolicyTypeId | string | policy type identifier as defined in A1TD [24]. | | -| PolicyId | string | policy identifier of an A1 policy as defined in A1 AP [23]. | | -| NearRtRicId | string | Near RT RIC identifier. | | - -### 9.1.8.3.3 Enumerations - -#### 9.1.8.3.3.1 Enumeration: QueryFilter - -This indicates whether the request is for A1 policies created by the requesting API Consumer, for A1 policies created by other API Consumers, or for all A1 policies created by any API Consumer. - -**Table 9.1.8.3.3.1 -1: Enumeration type of QueryFilter** - -| Enumerations Value | Description | -|--------------------|--------------------------------------------------------| -| OWN | indicate the A1 policies created by API Consumer. | -| OTHERS | indicate the A1 policies created other API Consumers. | -| ALL | indicate the A1 policies created by any API Consumers. | - -## 9.1.8.3 Re-used data types - -None. - -## 9.1.8.4 Service-specific registration information - -None. - -## 9.1.9 Error Handling - -### 9.1.9.1 General - -In addition to the general provisions in clause 5.4.3, the requirements in the following clauses are applicable for the A1 policy management API. - -### 9.1.9.2 Protocol Errors - -No specific protocol errors are defined in the present document. - -### 9.1.9.3 Application Errors - -The application errors defined for the A1 policy management service are listed in table 9.1.9.3-1. - -**Table 9.1.9.3-1: Application errors** - -| Application Error | HTTP status code | Description | -|--------------------|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Unauthorized | 401 | Used when the API consumer lacks proper authentication credentials or has provided invalid credentials | -| Forbidden | 403 | Used when the API Consumer has successfully authenticated the user, but the user is still denied access to the requested resource. | -| Bad Request | 400 | Used when the A1 policy management service cannot or will not process a request, e.g., when the validation of PolicyObject towards a policy type schema, or the validation of PolicyStatusObject towards a policy status schema, fails. | -| Not Found | 404 | Used when the Near-RT RIC did not find a current representation for the resource representing a policy type or a policy, e.g., for a policy type that is not available or a policy that does not exist. | -| Method Not Allowed | 405 | Used when the HTTP method is not supported by the resource defined for the A1 policy management API. | -| Conflict | 409 | Used if detecting that a policy requested to be created or updated may be overlapping or conflicting with a policy that exists in the Near-RT RIC. | - -Application errors should be mapped to the most applicable 4xx/5xx HTTP error status code. If no such status code is applicable, one of the status codes 400 (Bad Request) or 500 (Internal Server Error) should be used. - -The HTTP status codes listed in table 9.1.9.3-1 shall be used as defined in clause 5.4.3 for the A1 policy management procedures and clause 9.1.5 for the resources. - -Implementations may use additional HTTP error status codes in addition to those listed in table 9.1.9.3-1, as long as they are valid HTTP status codes. - -A list of all valid HTTP status codes and their specification documents can be obtained from the HTTP status code registry [21]. - -In addition, the response body may contain a JSON representation of a “ProblemDetails“ data structure in the payload body as defined in clause 9.1.8.2.2. In that case, as defined by IETF RFC 7807 [10], the “Content-Type“ HTTP header shall be set to “application/problem+json“. - -## 10. AI/ML workflow services - -### 10.1 AI/ML model registration API - -#### 10.1.1 Introduction - -This API enables the API Consumer to register, query, update and deregister an AI/ML model based on the AI/ML model registration service defined in R1GAP [5]. - -#### 10.1.2 API version - -For the AI/ML model registration API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 0 and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1] for a definition of the version fields). Consequently, the URI path segment shall be set to “v1“. - -#### 10.1.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined in clause 5.2. The resource URI variable shall be “ai-ml-model-registration“. The for each resource shall be set as described in clause 10.1.5. - -Figure 10.1.3-1 shows the overall resource URI structure defined for the model registration API. - -![A hierarchical diagram showing the resource URI structure. At the top is the root path '{apiRoot}/ai-ml-model-registration/{apiVersion}'. A line descends from this root to a box containing '/model-registrations'. From this box, another line descends to a second box containing '{modelRegistrationId}'.](66b2567aa84dd1d036931b056352e11e_img.jpg) - -``` - -graph TD - Root["{apiRoot}/ai-ml-model-registration/{apiVersion}"] --> Box1["/model-registrations"] - Box1 --> Box2["/{modelRegistrationId}"] - -``` - -A hierarchical diagram showing the resource URI structure. At the top is the root path '{apiRoot}/ai-ml-model-registration/{apiVersion}'. A line descends from this root to a box containing '/model-registrations'. From this box, another line descends to a second box containing '{modelRegistrationId}'. - -**Figure 10.1.3-1: Resource URI structure of the AI/ML model registration API** - -Table: 10.1.3-1 1 lists the individual resources defined for the API, the applicable HTTP methods, and the associated service operations. - -**Table 10.1.3-1: Resource and methods overview of the AI/ML model registration API** - -| Resource name | Resource URI | HTTP method | Service Operation | -|------------------------------------------|------------------------------------------------|-------------|--------------------------------------------| -| Registered model registrations | .../ model-registrations | POST | Register model information. | -| Individual registered model registration | .../ model-registrations/{modelRegistrationId} | GET | Query model registration information. | -| | | PUT | Update model registration information. | -| | | DELETE | Deregister model registration information. | - -## 10.1.4 Service operations - -### 10.1.4.1 Register model information - -#### 10.1.4.1.1 Operation definition - -The API Consumer uses this operation to register AI/ML model information. - -The operation to register the model information is based on HTTP POST. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer ->> Producer: POST .../model-registrations (ModelRelatedInformation) -Producer -->> Consumer: 201 Created (ModelRelatedInformation) -@enduml -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for the 'Register model information' operation. The Consumer sends a POST request to the Producer, and the Producer responds with a 201 Created status.](49b9b8bd6845ff94f361b147c84fc945_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 POST .../model-registrations (ModelRelatedInformation) - API Producer-->>API Consumer: 2 201 Created (ModelRelatedInformation) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for the 'Register model information' operation. The Consumer sends a POST request to the Producer, and the Producer responds with a 201 Created status. - -**Figure 10.1.4.1.1 -1: Register model information operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP POST request to the API Producer. The target URI shall identify the resource (.../model-registrations) under which the new registration is requested to be created. The message content shall carry a ModelRelatedInformation structure. -2. The API Producer shall generate the model registration identifier and construct the URI for the created resource. The API Producer shall return the HTTP POST response. On success, “201 Created“ shall be returned. The “Location“ header shall be present and shall carry the URI of the new registration resource. The message content shall carry a ModelRelatedInformation structure that represents the new resource. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -### 10.1.4.1.2 Referenced procedures. - -#### 10.1.4.1.2.1 Register AI/ML model procedure - -The Register model information operation illustrated in figure 10.1.4.1.1-1. is based on the Register AI/ML model procedure defined for the AI/ML workflow services in R1GAP [5]. - -### 10.1.4.2 Deregisster model information. - -#### 10.1.4.2.1 Operation definition - -The API Consumer uses this operation to delete the registered model information. - -The operation to deregister an AI/ML model information that was previously registered is based on HTTP DELETE. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: DELETE .../model-registrations/{modelRegistrationId} -Producer -->> Consumer: 204 No Content -@enduml -``` - -![Sequence diagram showing the interaction between API Consumer and API Producer for the deregister model information operation. The API Consumer sends a DELETE request to the API Producer, and the API Producer responds with a 204 No Content status.](ccb9a8830d90ffdcecfc4ef45ce72dbe_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: - API Consumer->>API Producer: 1 DELETE .../model-registrations/{modelRegistrationId} - Note right of API Producer: - API Producer-->>API Consumer: 2 204 No Content -``` - -Sequence diagram showing the interaction between API Consumer and API Producer for the deregister model information operation. The API Consumer sends a DELETE request to the API Producer, and the API Producer responds with a 204 No Content status. - -**Figure 10.1.4.2.1 -1: Deregisster model information operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP DELETE request to the API Producer. The target URI shall identify the resource to be deleted (.../model-registrations/{modelRegistrationId}). -2. The API Producer shall return the HTTP DELETE response. On success, “204 No Content“ shall be returned and the response message content shall be empty. On failure, the appropriate error code shall be returned, and the message response content may contain additional error information. - -### 10.1.4.2.2 Referenced procedures. - -#### 10.1.4.2.2.1 Deregisster AI/ML Model procedure. - -The Deregisster model information operation illustrated in figure 10.1.4.2.1-1 is based on the Deregisster AI/ML model procedure defined for the AI/ML workflow services in R1GAP [5]. - -### 10.1.4.3 Update model information - -#### 10.1.4.3.1 Operation definition - -The API Consumer uses this operation to Update model information. - -The operation to update the model information is based on HTTP PUT. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: PUT.../model-registrations/\n{modelRegistrationId} -(ModelRelatedInformation) -Producer -->> Consumer: 200 OK (ModelRelatedInformation) -@enduml -``` - -![Sequence diagram showing the Update model information operation. An API Consumer sends a PUT request to an API Producer, and the API Producer responds with a 200 OK status.](8768e42bf1062f1af11f259fc52a92e9_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: 1 - API Consumer->>API Producer: PUT.../model-registrations/\n{modelRegistrationId} (ModelRelatedInformation) - Note right of API Producer: 2 - API Producer-->>API Consumer: 200 OK (ModelRelatedInformation) -``` - -Sequence diagram showing the Update model information operation. An API Consumer sends a PUT request to an API Producer, and the API Producer responds with a 200 OK status. - -**Figure 10.1.4.3.1 -1: Update model information operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP PUT request to the API Producer. The target URI shall identify the resource (.../model-registrations/{modelRegistrationId}). The message content shall carry an updated ModelRelatedInformation structure. The API producer shall process the HTTP PUT message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP PUT response. On success, “200 OK“ shall be returned. The message body shall contain updated ModelRelatedInformation structure On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -**10.1.4.3.2 Referenced procedures.** - -**10.1.4.3.2.1 Update AI/ML model registration procedure** - -The Update model information operation illustrated in figure 10.1.4.1.1-1. is based on the Update AI/ML model registration procedure defined for the AI/ML workflow services in R1GAP [5]. - -**10.1.4.4 Query model information** - -**10.1.4.4.1 Operation definition** - -The API Consumer uses this operation to query model information that it has previously registered. - -The operation to query model information is based on HTTP GET. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer -->> Producer: GET .../model-registrations/{modelRegistrationId} -Producer -->> Consumer: 200 OK (ModelRelatedInformation) -@enduml -``` - -![Sequence diagram showing the 'Query model information operation'. It features two 'API Consumer' boxes on the left and two 'API Producer' boxes on the right. A solid arrow labeled '1 GET .../model-registrations/{modelRegistrationId}' points from the top API Consumer to the top API Producer. A dashed return arrow labeled '2 200 OK (ModelRelatedInformation)' points from the top API Producer back to the top API Consumer.](3a568746c00925506d5c39f2a86a5a63_img.jpg) - -Sequence diagram showing the 'Query model information operation'. It features two 'API Consumer' boxes on the left and two 'API Producer' boxes on the right. A solid arrow labeled '1 GET .../model-registrations/{modelRegistrationId}' points from the top API Consumer to the top API Producer. A dashed return arrow labeled '2 200 OK (ModelRelatedInformation)' points from the top API Producer back to the top API Consumer. - -**Figure 10.1.4.4.1 -1: Query model information operation** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../model-registrations/{modelRegistrationId}). The message content shall be empty. The API producer shall process the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP GET response. On success, “200 OK“ shall be returned. The message content shall carry the queried model related information. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -**10.1.4.4.2 Referenced procedures.** - -**10.1.4.4.2.1 Query AI/ML model registration procedure** - -The Query model information operation illustrated in figure 10.1.4.4.1-1. is based on the Query AI/ML model registration procedure defined for the AI/ML workflow services in R1GAP [5]. - -## 10.1.5 Resources - -### 10.1.5.1 Overview - -The following clause defines the resources for the AI/ML model registration API. - -### 10.1.5.2 Resource: "Registered model registrations" - -#### 10.1.5.2.1 Description - -The resource represents the model information of an rApp that it wants to register. - -Only the methods defined in clause 10.1.5.2.3 shall be supported by this resource. - -#### 10.1.5.2.2 Resource Definition - -Resource URI: {apiRoot}/ai-ml-model-registration//model-registrations - -The resource URI variables supported by the resource is defined in Table 10.1.5.2.2-1. - -**Table 10.1.5.2.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|--------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 10.1.2. | - -### 10.1.5.2.3 Resource Standard Methods - -#### 10.1.5.2.3.1 POST - -This method shall support the request data structure specified in the table 10.1.5.2.3.1-1 and the response data structure and response code specified in the table 10.1.5.2.3.1-2, and the HTTP headers specified in table 10.1.5.2.3.1-3. - -**Table 10.1.5.2.3.1-1: Data structures supported by the POST request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-------------------------|---|-------------|----------------------------------| -| ModelRelatedInformation | M | 1 | Information related to the model | - -**Table 10.1.5.2.3.1-2: Data structures supported by the POST response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|-------------------------|---|-------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| ModelRelatedInformation | M | 1 | 201 Created | The operation was successful, and the message content of the POST response contains a ModelRelatedInformation structure as a representation of the created resource. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -**Table 10.1.5.2.3.1-3: Headers supported by the 201 Response Code on this resource.** - -| Name | Data type | P | Cardinality | Description | -|----------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Location | string | M | 1 | Contains the URI of the newly created “Individual registered ModelInformation” resource, as defined in clause 10.1.5.3, with the registrationId in the URI. | - -### 10.1.5.3 Resource: "Individual registered model registration" - -#### 10.1.5.3.1 Description - -The resource represents the model information of an rApp that it wants to update, deregister, and query. - -Only the methods defined in clause 10.1.5.3.3 shall be supported by this resource. - -#### 10.1.5.3.2 Resource Definition - -Resource URI: {apiRoot}/ai-ml-model-registration//model-registrations/{modelRegistrationId} -The resource URI variables supported by the resource are defined in Table 10.1.5.3.2-1. - -**Table 10.1.5.3.2-1: Resource URI variables for the resource.** - -| Name | Definition | -|---------------------|-------------------------------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 10.1.2. | -| modelRegistrationId | The registration identifier of the model. | - -### 10.1.5.3.3 Resource Standard Methods - -#### 10.1.5.3.3.1 DELETE - -This method shall support the request data structure specified in table 10.1.5.3.3.1-1 and the response data structure and response code specified in 10.1.5.3.3.1-2. - -**Table 10.1.5.3.3.1-1: Data structure supported by the DELETE request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|------------------------------------------| -| N/A | | | A DELETE request has no message content. | - -**Table 10.1.5.3.3.1-2: Data structure supported by the DELETE response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------| -| N/A | | | 204 No Content | The AI/ML model registration associated with the modelRegistrationId has been deleted successfully. The message content shall be empty. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -#### 10.1.5.3.3.2 PUT - -This method shall support the request data structure specified in the table 10.1.5.3.3.2-1 and the response data structure and response code specified in the table 10.1.5.3.3.2-2. - -**Table 10.1.5.3.3.2-1: Data structures supported by the PUT request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-------------------------|---|-------------|------------------------------------| -| ModelRelatedInformation | M | 1 | Updated model related information. | - -**Table 10.1.5.3.3.2-2: Data structures supported by the PUT response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|-------------------------|---|-------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| ModelRelatedInformation | M | 1 | 200 OK | The model related information associated with the modelRegistrationId has been updated successfully and the response contain the ModelRelatedInformation as a representation of the updated resource. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -#### 10.1.5.3.3.3 GET - -This method shall support the request data structure specified in the table 10.1.5.3.3.3-1 and the response data structure and response code specified in the table 10.1.5.3.3.3-2. - -**Table 10.1.5.3.3.3-1: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|--------------------------------------| -| N/A | | | A GET request has no message content | - -**Table 10.1.5.3.3-2: Data structures supported by the GET response body on this resource.** - -| Data Type | P | Cardinality | Response codes | Description | -|-------------------------|---|-------------|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| ModelRelatedInformation | M | 1 | 200 OK | The model related information registration associated with the modelRegistrationId has been queried successfully and the response contain the ModelRelatedInformation as a representation of the query resource. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation has failed, and the message content may contain Problem description details. | - -**10.1.5.3.4 Resource Custom Operations** - -None. - -**10.1.6 Custom operation without associated resources.** - -None. - -**10.1.7 Notifications** - -None. - -**10.1.8 Data Model** - -**10.1.8.1 Structured data types** - -**10.1.8.1.1 Overview** - -The following clauses define the structured data types and their attributes to be used by the AI/ML model registration API. - -**10.1.8.1.2 Data type: ModelRelatedInformation** - -The ModelRelatedInformation data type represents registration information for an AI/ML model . It contains the attributes defined in table 10.1.8.1.2-1. - -**Table 10.1.8.1.2-1: Definition of type ModelRelatedInformation.** - -| Attribute Name | Data type | P | Cardinality | Description | -|------------------|------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------| -| modelId | ModelId | M | 1 | Identifier of a model | -| description | string | M | 1 | Description of the AI/ML model | -| modelInformation | ModelInformation | M | 1 | Information of the AI/ML model | -| modelLocation | URI | O | 0..1 | Location of the model stored in the runtime catalogue that can be discovered and referred to when using AI/ML workflow services. | - -**10.1.8.1.3 Data type: ModelId** - -The ModelId data type represents information of AI/ML model . It contains the attributes defined in table 10.1.8.1.3-1. - -**Table 10.1.8.1.3-1: Definition of type ModelId.** - -| Attribute Name | Data type | P | Cardinality | Description | -|-----------------|-----------|---|-------------|-----------------------------------------------------------| -| modelName | String | M | 1 | Name of the model as specified in R1GAP [1]. | -| modelVersion | String | M | 1 | Version of the model as specified in R1GAP [1]. | -| artifactVersion | String | O | 0..1 | Artifact version of AIML model as specified in R1GAP [1]. | - -#### 10.1.8.1.4 Data type: ModelInformation - -The Model information data type contains the attributes defined in table 10.1.8.1.4-1. - -**Table 10.1.8.1.4-1: Definition of type ModelInformation.** - -| Attribute Name | Data type | P | Cardinality | Description | -|-------------------|--------------------------|---|-------------|-------------------------------------------------------------------------------------------| -| metadata | MetaData | M | 1 | Metadata of the model. | -| inputDataType | array(dataTypeId) | M | 1..N | Input data type for the model, the structure of dataTypeId is specified in clause 7.1.8. | -| outputDataType | array(dataTypeId) | M | 1..N | Output data type for the model, the structure of dataTypeId is specified in clause 7.1.8. | -| targetEnvironment | array(TargetEnvironment) | O | 0..N | Information on the target environment is required for deployment of an AI/ML model. | - -#### 10.1.8.1.5 Data type: MetaData - -The Metadata data type contains the attributes defined in table 10.1.8.1.5-1. - -**Table 10.1.8.1.5-1: Definition of type MetaData.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-----------|---|-------------|------------------------------------------------------------------------------------------------| -| author | String | M | 1 | Author of the AIML model. | -| owner | String | O | 0..1 | Ownership of the AIML model to regulate how the model can be used in the Run-Time environment. | - -#### 10.1.8.1.6 TargetEnvironment - -The TargetEnvironment data type contains the attributes defined in table 10.1.8.1.6-1. - -**Table 10.1.8.1.6-1: Definition of type TargetEnvironment** - -| Attribute Name | Data type | P | Cardinality | Description | -|-----------------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| -| platformName | String | M | 1 | Name of the platform. | -| environmentType | String | M | 1 | Name of the platform Execution service type, and this is dependent on the platformName. | -| dependencyList | URI | M | 1 | Location to the template that has all the list of dependencies platform must provide needs to be installed for the model. (for example, scikit-learn 0.21.3). | - -## 10.1.8.2 Simple data types and enumerations - -### 10.1.8.2.1 Enumerations - -For this AI/ML model registration API, no enumerations are defined in the present document. - -## 10.1.9 Error Handling - -### 10.1.9.1 General - -In addition to the general provisions in clause 5.4.3, the requirements in the following clauses are applicable for the AI/ML model Registration API. - -### 10.1.9.2 Protocol Errors - -No specific protocol errors are defined in the present document. - -### 10.1.9.3 Application Errors - -No additional application errors defined in the present document. - -## 10.2 AI/ML model discovery API - -### 10.2.1 Introduction - -This API enables the API Consumer to discover an AI/ML model based on the AI/ML model discovery service defined in R1GAP [5]. - -### 10.2.2 API version - -For the AI/ML model discovery API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 1 and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1] for a definition of the version fields). Consequently, the URI path segment shall be set to “v1.1“. - -### 10.2.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined in clause 5.2. The resource URI variable shall be “ai-ml-model-discovery“. - -Figure 10.2.3-1 shows the overall resource URI structure defined for the AI/ML model discovery API. - -![A tree diagram showing the resource URI structure. The root is {apiRoot}/ai-ml-model-discovery/. It branches into two boxes: /models and /{modelId}.](0db2dd2a5c02140f5b395569f17ab91d_img.jpg) - -``` - - {apiRoot}/ai-ml-model-discovery/ - | - +-- /models - | - +-- /{modelId} - -``` - -A tree diagram showing the resource URI structure. The root is {apiRoot}/ai-ml-model-discovery/. It branches into two boxes: /models and /{modelId}. - -Figure 10.2.3-1: Resource URI structure of the AI/ML model discovery API - -Table: 10.2.3-1 lists the individual resources defined for the API, the applicable HTTP methods, and the associated service operations. - -Table 10.2.3-1: Resource and methods overview of the AI/ML model discovery API - -| Resource name | Resource URI | HTTP method | Service Operation | -|------------------------|-------------------|-------------|----------------------------------| -| ALL registered models | .../models | GET | Discover registered AI/ML models | -| Individual AI/ML model | /models/{modelId} | GET | Query AI/ML model | - -## 10.2.4 Service operations - -### 10.2.4.1 Discover AI/ML models - -The API Consumer uses this operation to discover the registered AI/ML models. - -The operation to discover the AI/ML models is based on HTTP GET. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -``` - -``` - -Participant "API Producer" as Producer -Consumer --> Producer: GET .../models -Producer --> Consumer: 200 OK (array(ModelRelatedInformation)) -@enduml - -``` - -![Sequence diagram for Discover models operation. It shows an API Consumer sending a GET .../models request to an API Producer, which responds with a 200 OK containing an array of ModelRelatedInformation.](1bc1746388cb64bf23b356ce2365dfc2_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET .../models - API Producer-->>API Consumer: 2 200 OK (array(ModelRelatedInformation)) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - -``` - -Sequence diagram for Discover models operation. It shows an API Consumer sending a GET .../models request to an API Producer, which responds with a 200 OK containing an array of ModelRelatedInformation. - -**Figure 10.2.4.1-1: Discover models operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource (.../models) and may also contain query parameters to discover the registered model identifiers. The API Producer shall process the request received in the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP GET response. On success, “200 OK“ shall be returned and the message content shall carry an array of ModelRelatedInformation that shall include modelId and corresponding metadata. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -**10.2.4.1.2 Referenced procedures.** - -**10.2.4.1.2.1 Discover AI/ML model procedure.** - -The Discover AI/ML models operation illustrated in figure 10.2.4.1-1 is based on the Discover AI/ML model procedure defined for the AI/ML workflow service in R1GAP [5]. - -**10.2.4.2 Query AI/ML models** - -The API Consumer uses this operation to query location information about a registered AI/ML model. - -The operation to query the AI/ML models is based on HTTP GET. - -``` - -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer --> Producer: GET /models/{modelId} -Producer --> Consumer: 200 OK (ModelLocationInformation) -@enduml - -``` - -![Sequence diagram for Query AI/ML models operation. It shows an API Consumer sending a GET /models/{modelId} request to an API Producer, which responds with a 200 OK containing ModelLocationInformation.](a00c2ce2bca7f7c0d7a597c7e199db9a_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 GET /models/{modelId} - API Producer-->>API Consumer: 2 200 OK (ModelLocationInformation) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - -``` - -Sequence diagram for Query AI/ML models operation. It shows an API Consumer sending a GET /models/{modelId} request to an API Producer, which responds with a 200 OK containing ModelLocationInformation. - -**Figure 10.2.4.2-1: Query models operation.** - -![Diagram showing the Query models operation where an API Consumer sends an HTTP GET request for a specific modelId to an API Producer, which then returns a 200 OK response with ModelLocationInformation or an error code.](98c911c074a0e29fafec169cbfa7248d_img.jpg) - -- 1) The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource "/models/{modelId}", the message content shall carry a modelId. The API Producer shall process the request received in the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -- 2) The API Producer shall return the HTTP GET response. On success, "200 OK" shall be returned and the message content shall carry a ModelLocationInformation structure. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -**10.2.4.2.2 Referenced procedures.** - -**10.2.4.2.2.1 Discover AI/ML model procedure.** - -The Discover AI/ML models operation illustrated in figure 10.2.4.2-1 is based on the Discover AI/ML model procedure defined for the AI/ML workflow service in R1GAP [5]. - -**10.2.5 Resources** - -**10.2.5.1 Overview** - -This clause defines the resource for the AI/ML model discovery API. - -**10.2.5.2 Resource: "All registered models"** - -**10.2.5.2.1 Description** - -The resource represents all registered AI/ML models in the Non-RT RIC. - -The methods defined in clause 10.2.5.2.3 shall be supported by this resource. - -**10.2.5.2.2 Resource Definition** - -Resource URI: **{apiRoot}/ai-ml-model-discovery//models** - -The resource URI variables supported by the resource is defined in table 10.2.5.2.2-1. - -**Table 10.2.5.2.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|--------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 10.2.2. | - -**10.2.5.2.3 Resource Standard Methods** - -**10.2.5.2.3.1 GET** - -This method shall support the URI query parameters specified in table 10.2.5.2.3.1-1, the request data structure specified in the table 10.2.5.2.3.1-2 and the response data structures, and response code specified in the table 10.2.5.2.3.1-3. - -**Table 10.2.5.2.3.1-1: URI query parameters supported by the GET method on this resource.** - -| Name | Data type | P | Cardinality | Description | Applicability | -|---------------|-----------|---|-------------|------------------------------------------------------------|---------------| -| model-name | string | O | 0..1 | Name of the model as specified in R1GAP [5] (See NOTE). | | -| model-version | string | O | 0..1 | Version of the model as specified in R1GAP [5] (See NOTE). | | - -NOTE: If multiple query parameters are provided these shall be combined with AND when evaluating the query. - -**Table 10.2.5.2.3.1-2: Data structures supported by the GET request body on this resource.** - -| Data Type | P | Cardinality | Description | -|-----------|---|-------------|---------------------------------------------------------------| -| N/A | | | There is no object in the message content of the GET request. | - -**Table 10.2.5.2.3.1-3: Data structures supported by the HTTP GET response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|---------------------------------|---|-------------|----------------|-----------------------------------------------------------------------------------------------------------| -| array (ModelRelatedInformation) | O | 0..N | 200 OK | The message content of the GET response carries an array of model identifiers and metadata of the models. | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description. | - -## 10.2.5.3 Resource; “Individual AI/ML model” - -### 10.2.5.3.1 Description - -The resource represents the model location. - -The methods defined in clause 10.2.5.2.3 shall be supported by this resource. - -### 10.2.5.3.2 Resource Definition - -Resource URI: {apiRoot}/ai-ml-model-discovery//models/{modelId} - -The resource URI variables supported by the resource is defined in table 10.2.5.3.2-1. - -**Table 10.2.5.3.2-1: Resource URI variable for the resource** - -| Name | Definition | -|------------|-------------------| -| apiRoot | See clause 5.2 | -| apiVersion | See clause 10.2.2 | - -### 10.2.5.3.3 Resource Standard Methods - -#### 10.2.5.3.3.1 GET - -This method shall support the request data structures specified in the table 10.2.5.3.3.1-1 and the response data structures and response codes specified in table 10.2.5.3.3.1-2. - -**Table 10.2.5.3.3.1-1: Data structures supported by the HTTP GET request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|------------------------------| -| modelId | M | 1 | The identifier of the model. | - -**Table 10.2.5.3.3.1-2: Data structures supported by the HTTP GET Response Body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|-------------------------|---|-------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| ModelLocationInfomation | | | 200 OK | The model location related information associated with the modelId has been got successfully and the response contain the ModelLocationInformation as a representation of the updated resource. | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -### 10.2.5.3.4 Resource Custom Methods - -None. - -## 10.2.6 Custom operation without associated resources - -None. - -## 10.2.7 Notifications - -NOTE: no notifications are specified in the current version of the present document. - -## 10.2.8 Data Model - -### 10.2.8.1 Structured data types - -#### 10.2.8.1.1 Overview - -The following clause defines the structured data types and their attributes to be used by the service API. - -#### 10.2.8.1.2 Data type: ModelRelatedInformation - -The ModelRelatedInformation data type represents registration information for an AI/ML model . It contains the attributes defined in table 10.2.8.1.2-1. - -**Table 10.2.8.1.2-1: Definition of type ModelRelatedInformation.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------| -| modelId | ModelId | M | 1 | Identifier of a model as specified in clause 10.1.8.1.3 | -| metadata | string | M | 1 | Description of the AI/ML model that includes the AI/ML model related information and training related information. | - -#### 10.2.8.1.3 Data type: ModelLocationInfomation - -The ModelLocationInfomation data type represents location information for an AI/ML model . It contains the attributes defined in table 10.2.8.1.3-1. - -**Table 10.2.8.1.3-1: Definition of type ModelRelatedInformation.** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-----------|---|-------------|----------------------------------------------------------| -| locationUri | string | M | 1 | The URI where the AI/ML model artifact can be accessed. | -| modelId | ModelId | O | 0..1 | Identifier of a model as specified in clause 10.1.8.1.3. | - -## 10.2.8.2 Simple data types and enumerations - -### 10.2.8.2.1 Introduction - -The following clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. - -### 10.2.8.2.2 Simple data types - -For this service API, no simple data types are defined in the present document. - -### 10.2.8.3.3 Enumerations - -For this service API, no enumerations are defined in the present document. - -## 10.2.9 Error Handling - -### 10.2.9.1 General - -In addition to the general provisions in clause 5.4.3, the requirements in the following clauses are applicable for the AI/ML model discovery API. - -### 10.2.9.2 Protocol Errors - -No specific protocol errors are defined in the present document. - -### 10.2.9.3 Application Errors - -No additional application errors defined in the present document. - -## 10.3 AI/ML model training API - -### 10.3.1 Introduction - -This API enables the API Consumer to request AI/ML model training, query AI/ML model training job status, and cancel AI/ML model training based on the procedures for ‘AI/ML model training services’ as defined in R1GAP [5]. It also allows the API Producer to notify AI/ML model training job status change based on the procedure for ‘AI/ML model training services’ defined in R1GAP [5]. - -### 10.3.2 API version - -For the AI/ML model training API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 0, and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1] for a definition of the version fields). Consequently, the URI path segment shall be set to ‘v1’. - -The AI/ML model training API is under development and consequently the API version shall include the pre-release version “alpha.1”. - -### 10.3.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined in clause 5.2. The resource URI variable shall be “ai-ml-model-training”. - -Figure 10.3.3-1 shows the overall resource URI structure defined for the AI/ML model training API. - -![A hierarchical diagram showing the resource URI structure. It starts with {apiRoot}/ai-ml-model-training/{apiVersion} at the top, branching down to /training-jobs, then to /{trainingJobId}, and finally to /status.](8d9be1ac4372e563dc3eb6d4aa5690d6_img.jpg) - -``` - -graph TD - Root["{apiRoot}/ai-ml-model-training/{apiVersion}"] --> T["/training-jobs"] - T --> J["/{trainingJobId}"] - J --> S["/status"] - -``` - -A hierarchical diagram showing the resource URI structure. It starts with {apiRoot}/ai-ml-model-training/{apiVersion} at the top, branching down to /training-jobs, then to /{trainingJobId}, and finally to /status. - -**Figure 10.3.3-1: Resource URI structure of the AI/ML model training API** - -Table: 10.3.3-1 lists the individual resources defined for the API, the applicable HTTP methods, and the associated service operations. - -**Table 10.3.3-1: Resource and methods overview of the AI/ML model training API** - -| Resource name | Resource URI | HTTP method | Service Operation | -|--------------------------------------------|------------------------------------------|-------------|----------------------------------------| -| All AI/ML model training jobs | .../training-jobs | POST | Request AI/ML model training. | -| Individual AI/ML model training job | .../training-jobs/{trainingJobId} | DELETE | Cancel AI/ML model training job. | -| Individual AI/ML model training job status | .../training-jobs/{trainingJobId}/status | GET | Query AI/ML model training job status. | - -### 10.3.4 Service operations - -#### 10.3.4.1 Request AI/ML model training - -##### 10.3.4.1.1 Operation definition - -The API Consumer uses this operation to request AI/ML model training. - -The operation to create AI/ML model training job is based on HTTP POST. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -``` - -``` - -Consumer ->> Producer: POST .../training-jobs (TrainingJobInfo) -Producer -->> Consumer: 201 Created (TrainingJobInfo) -@enduml - -``` - -![Sequence diagram for Request AI/ML model training operation](b02ba0b73e95416eb547976f6145b169_img.jpg) - -``` - -sequenceDiagram - autonumber - participant C as API Consumer - participant P as API Producer - C->>P: POST .../training-jobs (TrainingJobInfo) - P-->>C: 201 Created (TrainingJobInfo) - -``` - -The diagram shows a sequence of two messages between an API Consumer and an API Producer. Message 1 is a POST request from the Consumer to the Producer for the resource path ".../training-jobs" carrying "TrainingJobInfo". Message 2 is a successful response (201 Created) from the Producer back to the Consumer, also carrying "TrainingJobInfo". - -Sequence diagram for Request AI/ML model training operation - -**Figure 10.3.4.1.1-1: Request AI/ML model training operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP POST request to the API Producer. The target URI shall identify the resource “/training-jobs“, the message content shall carry a TrainingJobInfo structure which includes information for training. The API Producer shall process the request received in the HTTP POST message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall generate the training job identifier and construct the URI for the created resource. The API Producer shall return the HTTP POST response. On success, “201 Created“ shall be returned. The “Location“ HTTP header shall be present and shall carry the URI for the newly created resource. The message content shall carry a TrainingJobInfo structure represents the new resource. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -**10.3.4.1.2 Referenced procedures.** - -**10.3.4.1.2.1 Request AI/ML model training procedure** - -The request AI/ML model training operation illustrated in figure 10.3.4.1.1-1 is based on the request AI/ML model training procedure defined in R1GAP [5]. - -**10.3.4.2 Cancel AI/ML model training** - -**10.3.4.2.1 Operation definition** - -The API Consumer uses this operation to cancel AI/ML model training. - -The operation to delete AI/ML model training job is based on HTTP DELETE. - -``` - -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer ->> Producer: DELETE .../training-jobs/{trainingJobId} -Producer -->> Consumer: 204 No Content -@enduml - -``` - -![Sequence diagram for Cancel AI/ML model training operation. It shows an API Consumer sending a DELETE request to an API Producer, which responds with 204 No Content.](200e768e8ed91aadff59c651287d1009_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - API Consumer->>API Producer: 1 DELETE .../training-jobs/{trainingJobId} - API Producer-->>API Consumer: 2 204 No Content - -``` - -Sequence diagram for Cancel AI/ML model training operation. It shows an API Consumer sending a DELETE request to an API Producer, which responds with 204 No Content. - -**Figure 10.3.4.2.1-1: Cancel AI/ML model training operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP DELETE request to the API Producer. The target URI shall identify the training job resource to be deleted as “/training-jobs/{trainingJobId}“, the message content shall be empty. The API Producer shall process the request received in the HTTP DELETE message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP DELETE response. On success, “204 No Content“ shall be returned. The message content shall be empty. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -**10.3.4.2.2 Referenced procedures.** - -**10.3.4.2.2.1 Cancel AI/ML model training procedure** - -The cancel AI/ML model training operation illustrated in figure 10.3.4.2.1-1 is based on the cancel AI/ML model training procedure defined in R1GAP [5]. - -**10.3.4.3 Query AI/ML model training job status** - -**10.3.4.3.1 Operation definition** - -The API Consumer uses this operation to query the AI/ML model training job status. - -The operation to query AI/ML model training job status is based on HTTP GET. - -``` - -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer ->> Producer: GET .../training-jobs/{trainingJobId}/status -Producer -->> Consumer: 200 OK (TrainingJobStatus) -@enduml - -``` - -![Sequence diagram for Query AI/ML model training job status operation. It shows an API Consumer sending a GET request to an API Producer, which responds with 200 OK containing TrainingJobStatus.](66d5189a924662748cac6a9b22a272e9_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - API Consumer->>API Producer: 1 GET .../training-jobs/{trainingJobId}/status - API Producer-->>API Consumer: 2 200 OK (TrainingJobStatus) - -``` - -Sequence diagram for Query AI/ML model training job status operation. It shows an API Consumer sending a GET request to an API Producer, which responds with 200 OK containing TrainingJobStatus. - -**Figure 10.3.4.3.1-1: Query AI/ML model training job status operation.** - -The service operation is as follows: - -1. The API Consumer shall send an HTTP GET request to the API Producer. The target URI shall identify the resource “/training-jobs/{trainingJobId}/status“, the message content shall be empty. The API Producer shall process the request received in the HTTP GET message and determine if the request sent by the API Consumer is authorized or not. -2. The API Producer shall return the HTTP GET response. On success, “200 OK“ shall be returned. The message content shall carry a TrainingJobStatus representing the status of the training job, which is identified by the trainingJobId. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -**10.3.4.3.2 Referenced procedures.** - -**10.3.4.3.2.1 Query AI/ML model training job status procedure** - -The query AI/ML model training job status operation illustrated in figure 10.3.4.3.1-1 is based on the query AI/ML model training job status procedure defined in R1GAP [5]. - -**10.3.4.4 Notify AI/ML model training job status change** - -**10.3.4.4.1 Operation definition** - -The API Producer uses this operation to notify the status change of an AI/ML model training job. - -The operation to notify AI/ML model training job status change is based on HTTP POST. - -``` -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer <<- Producer: POST {notificationDestination} (TrainingJobStatusChangeNotification) -Consumer -->> Producer: 204 No Content -@enduml -``` - -![Sequence diagram showing the notification operation. The API Producer sends a POST request to the API Consumer, and the API Consumer responds with a 204 No Content status.](7f7718a1d18d1f9055d85871d02364b3_img.jpg) - -``` -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Producer->>API Consumer: 1 POST {notificationDestination} (TrainingJobStatusChangeNotification) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer-->>API Producer: 2 204 No Content -``` - -Sequence diagram showing the notification operation. The API Producer sends a POST request to the API Consumer, and the API Consumer responds with a 204 No Content status. - -**Figure 10.3.4.4.1-1: Notify AI/ML model training job status change operation.** - -The service operation is as follows: - -1. The API Producer shall send an HTTP POST request to the API Consumer. The target URI {notificationDestination} shall be the one provided by API Consumer during the creation of the training job, the message content shall carry a TrainingJobStatusChangeNotification which includes the updated training job status. The API Consumer shall process the request received in the HTTP POST message and determine if the request sent by the API Producer is authorized or not. -2. The API Consumer shall return the HTTP POST response. On success, “204 No Content“ shall be returned. The message content shall be empty. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -#### 10.3.4.4.2 Referenced procedures. - -##### 10.3.4.4.2.1 Notify AI/ML model training job status change procedure - -The notify AI/ML model training job status change operation illustrated in figure 10.3.4.4.1-1 is based on the notify AI/ML model training job status change procedure defined in R1GAP [5]. - -### 10.3.5 Resources - -#### 10.3.5.1 Overview - -This clause defines the resource for the AI/ML model training API. - -#### 10.3.5.2 Resource: "All AI/ML model training jobs" - -##### 10.3.5.2.1 Description - -The resource represents all AI/ML model training jobs created in the AI/ML model training API producer. - -The methods defined in clause 10.3.5.2.3 shall be supported by this resource. - -##### 10.3.5.2.2 Resource Definition - -Resource URI: {apiRoot}/ai-ml-model-training//training-jobs - -The resource URI variables supported by the resource is defined in table 10.3.5.2.2-1. - -**Table 10.3.5.2.2-1: Resource URI variables for the resource** - -| Name | Definition | -|------------|--------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 10.3.2. | - -##### 10.3.5.2.3 Resource Standard Methods - -###### 10.3.5.2.3.1 POST - -This method shall support the request data structures specified in the table 10.3.5.2.3.1-1 and the response data structures, and response codes specified in table 10.3.5.2.3.1-2 and the HTTP headers specified in table 10.3.5.2.3.1-3. - -**Table 10.3.5.2.3.1-1: Data structures supported by the HTTP POST request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------------|---|-------------|----------------------------------------------------------------------| -| TrainingJobInfo | M | 1 | Information related to the creation of the AI/ML model training job. | - -**Table 10.3.5.2.3.1-2: Data structures supported by the HTTP POST response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|-----------------|---|-------------|----------------|-----------------------------------------------------------| -| TrainingJobInfo | M | 1 | 201 Created | Confirmation of creation of the AI/ML model training job. | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description. | - -**Table 10.3.5.2.3.1-3: Headers supported by the 201 Response Code on this resource.** - -| Name | Data type | P | Cardinality | Description | -|----------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| -| Location | string | M | 1 | Contains the URI of the newly created individual AI/ML model training job resource, as defined in clause 10.3.5.3, with the trainingJobId in the URI. | - -**10.3.5.2.4 Resource Custom Methods** - -None. - -**10.3.5.3 Resource: "Individual AI/ML model training job"** - -**10.3.5.3.1 Description** - -The resource represents an individual AI/ML model training job created in the AI/ML model training API producer. - -The methods defined in clause 10.2.5.3.3 shall be supported by this resource. - -**10.3.5.3.2 Resource Definition** - -Resource URI: {apiRoot}/ai-ml-model-training//training-jobs/{trainingJobId} - -The resource URI variables supported by the resource is defined in table 10.3.5.3.2-1. - -**Table 10.3.5.3.2-1: Resource URI variables for the resource** - -| Name | Definition | -|---------------|---------------------------------------------------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 10.3.2. | -| trainingJobId | The training job identifier assigned by the Service Producer. | - -**10.3.5.3.3 Resource Standard Methods** - -**10.3.5.3.3.1 DELETE** - -This method shall support the request data structures specified in the table 10.3.5.3.3.1-1 and the response data structures, and response codes specified in table 10.3.5.3.3.1-2. - -**Table 10.3.5.3.3.1-1: Data structures supported by the HTTP DELETE request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|----------------------------------------------------------------| -| N/A | | | There is no object in the message content of a DELETE request. | - -**Table 10.3.5.3.3.1-2: Data structures supported by the HTTP DELETE response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|--------------------------------------| -| N/A | | | 204 No content | Confirmation of successful deletion. | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description. | - -### 10.3.5.3.4 Resource Custom Methods - -None. - -### 10.3.5.4 Resource: "Individual AI/ML model training job status" - -#### 10.3.5.4.1 Description - -The resource represents the status of an individual AI/ML model training job created in the Non-RT RIC. - -The methods defined in clause 10.3.5.4.3 shall be supported by this resource. - -#### 10.3.5.4.2 Resource Definition - -Resource URI: {apiRoot}/ai-ml-model-training//training-jobs/{trainingJobId}/status - -The resource URI variables supported by the resource is defined in table 10.3.5.4.2-1. - -**Table 10.3.5.4.2-1: Resource URI variables for the resource** - -| Name | Definition | -|---------------|---------------------------------------------------------------| -| apiRoot | See clause 5.2. | -| apiVersion | See clause 10.3.2. | -| trainingJobId | The training job identifier assigned by the Service Producer. | - -#### 10.3.5.4.3 Resource Standard Methods - -##### 10.3.5.4.3.1 GET - -This method shall support the request data structures specified in the table 10.3.5.4.3.1-1 and the response data structures, and response codes specified in table 10.3.5.4.3.1-2. - -**Table 10.3.5.4.3.1-1: Data structures supported by the HTTP GET request body on this resource.** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|-------------------------------------------------------------| -| N/A | | | There is no object in the message content of a GET request. | - -**Table 10.3.5.4.3.1-2: Data structures supported by the HTTP GET response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|-------------------|---|-------------|----------------|---------------------------------------------| -| TrainingJobStatus | M | 1 | 200 OK | The status of the AI/ML model training job. | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description. | - -#### 10.3.5.4.4 Resource Custom Methods - -None. - -### 10.3.6 Custom operation without associated resources. - -None. - -### 10.3.7 Notifications - -#### 10.3.7.1 Notify training job status change. - -##### 10.3.7.1.1 Description - -The notification informs the receiver about the updated status of an AI/ML model training job. - -##### 10.3.7.1.2 Resource Definition - -The Resource URI {notificationDestination} is a callback URI provided when creating an AI/ML model training job. - -##### 10.3.7.1.3 Resource Standard Methods - -###### 10.3.7.1.3.1 POST - -This method shall support the request data structures specified in table 10.3.7.1.3.1-1 and the response data structure and response codes specified in table 10.3.7.1.3.1-2. - -**Table 10.3.7.1.3.1-1: Data structures supported by the HTTP POST request body on this resource.** - -| Data type | P | Cardinality | Description | -|-------------------------------------|---|-------------|---------------------------------------------------------| -| TrainingJobStatusChangeNotification | M | 1 | Notify a status changes of an AI/ML model training job. | - -**Table 10.3.7.1.3.1-2: Data structures supported by the HTTP POST response body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|---------------------------------------------------------------------------------------------------------------------| -| N/A | | | 204 No content | Confirmation of received notification. | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation was unsuccessful.

Detailed problem description may be carried in the response message content. | - -### 10.3.8 Data Model - -#### 10.3.8.1 Structured data types - -##### 10.3.8.1.1 Overview - -The following clauses define the data types and attributes to be used by the AI/ML model training API. - -##### 10.3.8.1.2 Data type: TrainingJobInfo - -**Table 10.3.8.1.2-1: Definition of type TrainingJobInfo** - -| Attribute Name | Data type | P | Cardinality | Description | -|-----------------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------| -| modelId | ModelId | M | 1 | The model identifier which contains model name, model version, and artifact version. See clause 10.1.8.1.3-1. | -| modelLocation | Uri | O | 0..1 | Location of the AI/ML model. | -| trainingDataset | Uri | O | 0..1 | Information for reference to the training dataset. | - -| | | | | | -|-------------------------|--------|---|------|--------------------------------------------------------------| -| trainingConfig | Object | O | 0..1 | trainingConfig provided by the training service producer. | -| notificationDestination | Uri | O | 0..1 | Callback URI where the notification should be delivered to. | -| trainingProducerId | String | O | 0..1 | Identifier of training producer "apfld" as specified in SME. | - -## 10.3.8.2 Simple data types and enumerations - -### 10.3.8.2.1 Overview - -The following clauses define simple data types and enumerations that can be referenced from data structure defined in the previous clauses. - -### 10.3.8.2.2 Simple data types - -No simple data types are defined in this version of the specification. - -### 10.3.8.2.3 Enumerations - -No enumerations are defined in this version of the specification. - -## 10.3.9 Error Handling - -### 10.3.9.1 General - -For the AI/ML model training API, HTTP error responses shall be supported as specified in 3GPP TS 29.501 [1]. Protocol errors and application errors specified in 3GPP TS 29.500 [2], table 5.2.7.2-1, shall be supported for an HTTP method if the corresponding HTTP status codes are specified as mandatory for that HTTP method in 3GPP TS 29.500 [2], table 5.2.7.1-1. - -In addition, the requirements in the following clauses are applicable for the AI/ML model training API. - -### 10.3.9.2 Protocol Errors - -No specific protocol errors are defined in the present document. - -### 10.3.9.3 Application Errors - -No additional application errors defined in the present document. - -## 10.4 AI/ML model deployment API - -### 10.4.1 Introduction - -This API enables the API Consumer to request the deployment of an AI/ML model based on the AI/ML model deployment request service defined in R1GAP [5]. - -### 10.4.2 API version - -For the AI/ML model deployment API as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 0 and the PATCH version field shall be 0 (see 3GPP TS 29.501 [1] for a definition of the version fields). Consequently, the URI path segment shall be set to "v1". - -The AI/ML model deployment API is under development and consequently the API version shall include the pre-release version "alpha.1". - -### 10.4.3 Resource structure and methods - -The request URIs used in HTTP requests from the API Consumer towards the API Producer shall have the resource URI structure as defined in clause 5.2. The resource URI variable shall be "ai-ml-model-deployment". The for each resource shall be set as described in clause 10.4.5. - -Figure 10.4.3-1 shows the overall resource URI structure defined for the AI/ML model deployment API. - -![Resource URI structure diagram showing a hierarchy: {apiRoot}/ai-ml-model-deployment/ -> /model-deployments -> /{modelDeploymentId} -> /status](92c9263daf7fbd044894e2b273ae21af_img.jpg) - -``` - -graph TD - Root["{apiRoot}/ai-ml-model-deployment/"] --> ModelDeployments["/model-deployments"] - ModelDeployments --> ModelDeploymentId["/{modelDeploymentId}"] - ModelDeploymentId --> Status["/status"] - -``` - -Resource URI structure diagram showing a hierarchy: {apiRoot}/ai-ml-model-deployment/ -> /model-deployments -> /{modelDeploymentId} -> /status - -**Figure 10.4.3-1: Resource URI structure of the AI/ML model deployment API** - -Table: 10.4.3-1 lists the individual resources defined for the API, the applicable HTTP methods, and the associated service operations. - -**Table 10.4.3-1: Resource and methods overview of the AI/ML model deployment API** - -| Resource name | Resource URI | HTTP method | Service Operation | -|------------------------------------|--------------------------------------------------|-------------|--------------------------------------| -| All AI/ML model deployments | .../model-deployments | POST | Request AI/ML model deployment. | -| Individual AI/ML deployment status | .../model-deployments/{modelDeploymentId}/status | GET | Query AI/ML model deployment status. | - -## 10.4.4 Service operations - -### 10.4.4.1 Request AI/ML model deployment - -#### 10.4.4.1.1 Operation definition - -The API Consumer uses this operation to request AI/ML model deployment. - -The operation to request AI/ML model deployment is based on HTTP POST. - -``` - -@startuml -autonumber -Participant "API Consumer" as Consumer -Participant "API Producer" as Producer -Consumer --> Producer: POST .../model-deployments (ModelDeploymentInformation) -Producer --> Consumer: 201 Created (ModelDeploymentInformation) -@enduml - -``` - -![Sequence diagram showing the request AI/ML model deployment operation. An API Consumer sends a POST request to an API Producer, and the API Producer responds with a 201 Created status.](60f844d947ea0bccdd9f64d81d5f8d26_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - API Consumer->>API Producer: 1 POST .../model-deployments (ModelDeploymentInformation) - API Producer-->>API Consumer: 2 201 Created (ModelDeploymentInformation) - Note left of API Consumer: API Consumer - Note right of API Producer: API Producer - -``` - -Sequence diagram showing the request AI/ML model deployment operation. An API Consumer sends a POST request to an API Producer, and the API Producer responds with a 201 Created status. - -**Figure 10.4.4.1.1-1: Request AI/ML model deployment operation.** - -The service operation is as follows: - -- 1) The API Consumer shall send an HTTP POST request to the API Producer. The target URI shall identify the resource "/modeldeployments", the message content shall carry a ModelDeploymentInformation which includes information for deployment. The API Producer shall process the request received in the HTTP POST message and determine if the request sent by the API Consumer is authorized or not. -- 2) The API Producer shall generate the deployment identifier and construct the URI for the created resource. The API Producer shall return the HTTP POST response. On success, "201 Created" shall be returned. The "Location" header shall be present and shall carry the URI of the new resource. The message content shall carry a ModelDeploymentInformation structure that represents the new resource. On failure, the appropriate error code shall be returned, and the message content may contain additional error information. - -**10.4.4.1.2 Referenced procedures.** - -**10.4.4.1.2.1 Request AI/ML model deployment procedure** - -The request AI/ML model deployment operation illustrated in figure 10.4.4.1.1-1 is based on the request AI/ML model deployment procedure defined in R1GAP [5]. - -**10.4.4.2 Notify AI/ML model deployment status change** - -**10.4.4.2.1 Operation definition** - -The API Producer uses this operation to notify the change of an AI/ML model deployment status. - -The operation to notify AI/ML model deployment status change is based on HTTP POST. - -``` - -@startuml -autonumber -participant "API Consumer" as Consumer -participant "API Producer" as Producer -Consumer <<- Producer: POST {notificationDestination}(DeploymentStatusChangeNotification) -Consumer -->> Producer: 204 No Content -@enduml - -``` - -![Sequence diagram showing the interaction between an API Consumer and an API Producer for notifying AI/ML model deployment status change. The API Producer sends a POST request to the API Consumer, and the API Consumer responds with a 204 No Content status.](53499879d98034410ecba2c386c58f0c_img.jpg) - -``` - -sequenceDiagram - participant API Consumer - participant API Producer - Note right of API Producer: 1 POST {notificationDestination}(DeploymentStatusChangeNotification) - API Producer->>API Consumer: 1 POST {notificationDestination}(DeploymentStatusChangeNotification) - Note left of API Consumer: 2 204 No Content - API Consumer-->>API Producer: 2 204 No Content - -``` - -Sequence diagram showing the interaction between an API Consumer and an API Producer for notifying AI/ML model deployment status change. The API Producer sends a POST request to the API Consumer, and the API Consumer responds with a 204 No Content status. - -**Figure 10.4.4.2.1-1: Notify AI/ML model deployment status change operation.** - -The service operation is as follows: - -- 1) The API Producer shall send an HTTP POST request to the API Consumer. The target URI {notificationDestination} may be provided by API Consumer during the ai/ml model deployment request, where the message content shall carry a DeploymentStatusChangeNotification which includes the updated AI/ML model deployment status. The API Consumer shall process the request received in the HTTP POST message and determine if the request sent by the API Producer is authorized or not. -- 2) The API Consumer shall return the HTTP POST response. On success, “204 No Content” shall be returned. The message content shall be empty. On failure, the appropriate error code shall be returned, and the response message content may contain additional error information. - -**10.4.4.2.2 Referenced procedures.** - -**10.4.4.2.2.1 Notify AI/ML model deployment status change procedure** - -The notify AI/ML model deployment status change operation illustrated in figure 10.4.4.2.1-1 is based on the AI/ML model deployment procedure defined in R1GAP [5]. - -## 10.4.5 Resources - -### 10.4.5.1 Overview - -This clause defines the resource for the AI/ML model deployment API. - -### 10.4.5.2 Resource: "All AI/ML model deployment" - -#### 10.4.5.2.1 Description - -The resource represents all AI/ML model deployment in the Non-RT RIC. - -The methods defined in clause 10.4.5.2.3 shall be supported by this resource. - -#### 10.4.5.3.2 Resource Definition - -Resource URI: {apiRoot}/ai-ml-model-deployment/ - -The resource URI variables supported by the resource is defined in table 10.4.5.2.2-1. - -**Table 10.4.5.3.2-1: Resource URI variable for the resource** - -| Name | Definition | -|------------|-------------------| -| apiRoot | See clause 5.2 | -| apiVersion | See clause 10.4.2 | - -### 10.4.5.2.3 Resource Standard Methods - -#### 10.4.5.2.3.1 POST - -This method shall support the request data structures specified in the table 10.4.5.2.3.1-1 and the response data structures and response codes specified in table 10.4.5.2.3.1-2. - -**Table 10.4.5.2.3.1-1: Data structures supported by the HTTP POST Request Body on this resource.** - -| Data type | P | Cardinality | Description | -|----------------------------|---|-------------|----------------------------------------------------------| -| ModelDeploymentInformation | M | 1 | Information related to the deployment of the AI/ML model | - -**Table 10.4.5.2.3.1-2: Data structures supported by the HTTP POST Response Body on this resource.** - -| Data type | P | Cardinality | Response codes | Description | -|----------------------------|---|-------------|----------------|---------------------------------------------------------------------------------------------------------------| -| ModelDeploymentInformation | 1 | M | 201 Created | The operation was successful.
The message content of the POST response carries ModelDeploymentInformation. | -| ProblemDetails | O | 0..1 | 4xx/5xx | Detailed problem description | - -### 10.4.5.2.4 Resource Custom Methods - -None. - -## 10.4.6 Custom operation without associated resources. - -None. - -## 10.4.7 Notifications - -### 10.4.7.1 Notify AI/ML model deployment status change - -#### 10.4.7.1.1 Overview - -The notification informs the receiver about the AI/ML model deployment status. - -#### 10.4.7.1.2 Resource Definition - -The Resource URI {notificationDestination} is a callback URI provided when requesting deployment of an AI/ML model. - -#### 10.4.7.1.3 Resource Standard Methods - -##### 10.4.7.1.3.1 POST - -This method shall support the request data structures specified in table 10.4.7.1.3.1-1 and the response data structure and response codes specified in table 10.4.7.1.3.1-2. - -**Table 10.4.7.1.3.1-1: Data structures supported by the HTTP POST request body on this resource** - -| Data type | P | Cardinality | Description | -|------------------------------------|---|-------------|--------------------------------------------------------------| -| DeploymentStatusChangeNotification | M | 1 | Notify a status changes of an AI/ML model deployment status. | - -**Table 10.4.7.1.3.1-2: Data structures supported by the HTTP POST response body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|----------------|-------------------------------------------------------------------------------------------------------------| -| N/A | | | 204 No Content | Confirmation of received notification | -| ProblemDetails | O | 0..1 | 4xx/5xx | The operation was unsuccessful. Detailed problem description may be carried in the response message content | - -## 10.4.8 Data Model - -### 10.4.8.1 Structured data types - -#### 10.4.8.1.1 Overview - -The following clauses define the structured data types and their attributes to be used by the AI/ML model deployment API. - -#### 10.4.8.1.2 Data type: ModelDeploymentInformation - -The ModelDeploymentInformation data type represents deployment information for an AI/ML model. It contains the attributes defined in table 10.4.8.1.2-1. - -**Table 10.4.8.1.2-1: Definition of type ModelDeploymentInformation.** - -| Attribute Name | Data type | P | Cardinality | Description | -|-------------------------|-----------|---|-------------|------------------------------------------------------------------------------------------------| -| modelId | ModelId | M | 1 | Identifier of a model. See clause 10.1.8.1.3 | -| notificationDestination | Uri | O | 0..1 | Callback URI where the notification would be delivered to, once the deployment status changes. | - -## 10.5 Void - -# Annex A (normative): OpenAPI specifications - -## A.1 General - -### A.1.1 Overview - -This Annex formally specifies the RESTful R1 service APIs by defining OpenAPI documents in YAML format that comply with the OpenAPI 3.0.3 Specification [3]. - -The Open API specifications of the RESTful R1 service APIs provided in this annex are versioned as described in clause 5.2. - -The OpenAPI's define in this annex has references to the common definitions define in clause A.1.2 of the present document. - -### A.1.2 Common schemas for general use - -#### A.1.2.1 Introduction - -The Open API specified in clause A.1.2.2 provides schemas for general data types and responses for usage across the R1 APIs. - -#### A.1.2.2 Common definitions - -``` - -openapi: 3.0.3 -info: - title: 'R1 Common definitions' - version: 1.0.1 - description: | - R1 Common definitions - O-RAN.WG2.R1AP_Common.yaml. - - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/sccl license: - name: SCCL - url: https://o-ran.org/scclexternalDocs: - description: 'O-RAN.WG2.R1AP' - url: 'https://www.o-ran.org/specifications' -paths: {} -components: - schemas: - Uri: - description: 'A string formatted according to IETF RFC 3986 [8].' - type: string - ProblemDetails: - description: 'A problem detail to carry details in an HTTP response according to RFC 7807' - type: object - properties: - type: - description: 'a URI reference according to IETF RFC 3986 that identifies the problem type' - type: string - title: - description: 'human-readable summary of the problem type' - type: string - status: - description: 'the HTTP status code' - type: number - detail: - description: 'human-readable explanation ' - type: string - instance: - description: 'URI reference that identifies the specific occurrence of the problem' - -``` - -``` - - type: string -responses: - '400': - description: 'Bad Request' - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '401': - description: 'Unauthorized' - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '403': - description: 'Forbidden' - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '404': - description: 'Not Found' - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '405': - description: 'Method Not Allowed' - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '406': - description: 'Not Acceptable' - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '409': - description: 'Conflict' - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '411': - description: 'Length Required' - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '413': - description: 'Payload Too Large' - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '414': - description: 'URI Too Large' - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '415': - description: 'Unsupported Media Type' - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '429': - description: 'Too Many Requests' - content: - -``` - -``` - - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '500': - description: 'Internal Server Error' - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '502': - description: 'Bad Gateway' - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '503': - description: 'Service Unavailable' - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - -``` - -### A.1.2.3 Notification - -``` - -openapi: 3.2.0 -info: - title: 'R1 Common definitions' - version: 1.0.0 - description: | - R1 Common definitions - O-RAN.WG2.R1AP_Notification.yaml. - Copyright 2025 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/scclALLIANCE. - All rights reserved. - license: - name: SCCL - url: https://o-ran.org/sccl -externalDocs: - description: 'O-RAN.WG2.R1AP' - url: 'https://www.o-ran.org/specifications' -paths: {} -components: - schemas: - NotificationType: - type: string - description: 'A string formatted as concatenation of "org.o-ran.", a string representing the service name (e.g. "DME"), a dot ".", and an API-specific name for the event type (e.g. "DATA_AVAILABILITY") defined in the API specification.' - Notification: - type: object - description: 'The general Notification data structure is specified in table B.2.4.5-1, aligned with the CloudEvents [30].' - properties: - id: - type: string - description: 'Identifier of the event, unique within the scope identified by the "source" attribute, as defined in CloudEvents [30].' - example: '123456789' - specversion: - type: string - description: 'The version of the CloudEvents specification which the event uses, as defined in CloudEvents [X]. E.g. the spec version is 1.0 aligned with the version of the CloudEvents specification [X]. (See NOTE).' - example: '1.0' - type: - -``` - -``` -$ref: '#/components/schemas/NotificationType' -source: - type: string - description: 'The source from which the event from has originated, as defined in CloudEvents -[30]'.' - example: 'https://example.com/data-access/v2/data-jobs/1234567' -time: - type: string - description: 'Timestamp when the event is generated, as defined in CloudEvents [30].'.' - example: '2020-01-01T00:00:00Z' -datacontenttype: - type: object - description: 'Content type of the value of the "data" attribute, as defined in CloudEvents -[30].(See NOTE).'.' - example: 'application/json' -dataschema: - type: Uri - description: 'Identifies the schema that data adheres to, as defined in CloudEvents [30].'.' - example: 'https://example.com/data' -data: - type: object - additionalProperties: true - description: 'Application event payload data encoded as declared by the "datacontenttype" -attribute. The structure of this attribute is defined by the API that specifies the notification type.'.' -required: - - id - - specversion - - type - - source -``` - -## A.2 Service management and exposure service - -### A.2.1 Service registration API - -#### A.2.1.1 Introduction - -The Open API for this service is reusing the CAPIF\_Publish\_Service\_API as specified in clause A.2.1.2 with exceptions specified in clause A.2.1.3 below. - -#### A.2.1.2 CAPIF\_Publish\_Service\_API - -The Open API for the SME service registration API specified in clause 6.1 reuses the CAPIF\_Publish\_Service\_API as specified in 3GPP TS 29.222 [9], clause A.3. - -The API version of the Service registration API as specified in clause 6.1.2 shall use the CAPIF\_Publish\_Service\_API OpenAPI version as specified in Table A.2.1.2-1. - -Table A.2.1.2-1 - -| API name | API version | CAPIF OpenAPI version | -|--------------------------|-------------|-----------------------| -| Service registration API | 1.2.0 | 1.3.0 | - -#### A.2.1.3 Adaptations and Exceptions - -The OpenAPI code below represents the "VersionExtensions" data type which needs to be added to the OpenAPI definitions of the CAPIF\_Publish\_Service\_API defined in 3GPP TS 29.222 [9]. - -``` -openapi: 3.0.3 -info: - title: 'Version_Extensions' -``` - -``` - -version: 1.0.0 -description: | - R1 Common definitions - O-RAN.WG2.R1AP_Common.yaml. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/scclALLIANCE. - All rights reserved. -license: - name: SCCL - url: https://o-ran.org/sccl -externalDocs: - description: 'O-RAN.WG2.R1AP' - url: 'https://www.o-ran.org/specifications' - -components: - schemas: - VersionExtensions: - Description: ' The VersionExtensions data structure specified in table B.3.4.1-1 in R1AP defines O- -RAN extensions to the CAPIF Version data type which allows to signal the versions supported for an -interface endpoint.' - type: object - properties: - fullApiVersions: - description: ' List of version strings, as defined in R1GAP clause 5.2, to signal the API -versions supported by the API Producer for a particular major API version.' - type: array - items: - type: string - minItems: 1 - -``` - -The OpenAPI code below represents the "ServiceProperties" data type which needs to be added to the OpenAPI definitions of the CAIF\_Publish\_Service\_API defined in 3GPP TS 29.222 [9]. - -``` - -openapi: 3.0.3 -info: - title: 'Service_Properties' - version: 1.0.0 - description: | - R1 Common definitions - O-RAN.WG2.R1AP_Common.yaml. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/scclALLIANCE. - All rights reserved. - license: - name: SCCL - url: https://o-ran.org/sccl -externalDocs: - description: 'O-RAN.WG2.R1AP' - url: 'https://www.o-ran.org/specifications' - -components: - schemas: - ServiceProperties: - description: 'Defines a container that can be used by individual service APIs to register and -discover service-specific properties.' - type: object - properties: - serviceCapabilities: - description: ' Service capabilities. The content of this attribute is service-specific and is -defined per service.' - type: object - -``` - -Table A.2.1.3-1 below lists exceptions and adaptations related to certain attributes in certain CAPIF data types when re-using the CAPIF\_Publish\_Service\_API in the context of the present document . - -**Table A.2.1.3-1: Message content exceptions and adaptations when reusing the CAPIF\_Publish\_Service\_API** - -| Data type | Reference | Attributes | Adaptations/Exceptions | -|-----------------------|--------------------------------|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| ServiceAPIDescription | 3GPP TS 29.222 [9], clause A.3 | supportedFeatures | Not required to be supported. | -| | | shareableInfo | Not required to be supported. | -| | | serviceAPICategory | Not required to be supported. | -| | | ccfld | Not required to be supported. | -| | | apiSuppFeats | Not required to be supported. | -| | | pubApiPath | Not required to be supported. | -| | | vendorSpecific-o-ran.org | This additional attribute shall be present if service-specific registration information is available for the service API. It shall have the type ServiceProperties as specified in clause B.3.4.2 and defined in annex A.2.1.3. | -| AefProfile | 3GPP TS 29.222 [9], clause A.3 | aeflId | Shall be set to the value of "rAppId" if an rApp produces the API. | -| | | aeflLocation | Not required to be supported. | -| | | domainName | Not required to be supported. | -| | | serviceKpis | Not required to be supported. | -| | | uelpRange | Not required to be supported. | -| Version | 3GPP TS 29.222 [9], clause A.3 | vendorSpecific-o-ran.org | This additional attribute shall be supported and shall have the type VersionExtensions as specified in clause B.3.4.1 and defined above. | - -## A.2.2 Service discovery API - -### A.2.2.1 Introduction - -The Open API for this service is reusing the CAPIF\_Discover\_Service\_API in as specified in clause A.2.2.2 with exceptions specified in clause A.2.2.3 below. - -### A.2.2.2 CAPIF\_Discovery\_Service\_API - -The Open API for the SME service discovery API specified in clause 6.2 reuses the CAPIF\_Discover\_Service\_API as specified in 3GPP TS 29.222 [9], clause A.2. - -The API version of the Service discovery API as specified in clause 6.2.2 shall use the CAPIF\_Discover\_Service\_API OpenAPI version as specified in Table A.2.2.2-1. - -**Table A.2.2.2-1** - -| API name | API version | CAPIF OpenAPI version | -|----------------------|-------------|-----------------------| -| Service discover API | 1.2.0 | 1.3.0 | - -### A.2.2.3 Adaptations and Exceptions - -Table A.2.2.3-1 lists exceptions and adaptations related to CAPIF message content when re-using the CAPIF\_Discover\_Service\_API in the context of the present document. - -Table A.2.2.3-1 lists exceptions and adaptations related to CAPIF URI query parameters when re-using the CAPIF\_Discover\_Service\_API in the context of the present document. - -**Table A.2.2.3-1: Message content exceptions and adaptations when reusing the CAPIF\_Discover\_Service\_API** - -| Data type | Reference | Attributes | Exceptions/Adaptations | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| ServiceAPIDescription | 3GPP TS 29.222 [9], clause A.3 | supportedFeatures | Not required to be supported. | -| | | shareableInfo | Not required to be supported. | -| | | serviceAPICategory | Not required to be supported. | -| | | ccfld | Not required to be supported. | -| | | apiSuppFeats | Not required to be supported. | -| | | pubApiPath | Not required to be supported. | -| | | vendorSpecific-o-ran.org | This additional attribute shall be present if service-specific registration information is available for the service API. It shall have the type ServiceProperties as specified in clause B.3.4.2 and defined in annex A.2.1.3. | -| | | ue-ip-addr | Not required to be supported. | -| | | service-kpis | Not required to be supported. | -| AefProfile | 3GPP TS 29.222 [9], clause A.3 | aeflId | Shall be set to the value of "rAppId" if an rApp produces the API.

Shall be set to an identifier related to the SMO/Non-RT RIC functions if these produce the API. See note. | -| | | aefLocation | Not required to be supported. | -| | | domainName | Not required to be supported. | -| Version | 3GPP TS 29.222 [9], clause A.3 | vendorSpecific-o-ran.org | This additional attribute shall be supported and shall have the type VersionExtensions as specified in clause B.3.4.1 and defined in annex A.2.1.3. | -| NOTE: It is out of scope of the present document whether each SMO/Non-RT RIC framework function is identifiable by a separate identifier value or whether such decomposition information is hidden from the rApps. However, the SMO/Non-RT RIC framework shall ensure that the identifiers used for rApps as AEFs and the identifiers used for SMO/Non-RT RIC framework functions as AEFs do not collide. | | | | - -The Query parameters in the table A.2.2.3-2 below are not required to be supported when the CAPIF\_Discover\_Service\_API is reused. - -**Table A.2.2.3-2: Query parameters exceptions and adaptations when reusing the CAPIF\_Discover\_Service\_API** - -| Resource | Reference | Exceptions | Comment | -|-----------------|--------------------------------|------------------------|------------------------------------------------------------------| -| /allServiceAPIs | 3GPP TS 29.222 [9], clause A.2 | api-invoker-id | Shall be set to the value of "rAppId" for an API-consuming rApp. | -| | 3GPP TS 29.222 [9], clause A.2 | comm-type | Not required to be supported. | -| | 3GPP TS 29.222 [9], clause A.2 | protocol | Not required to be supported. | -| | 3GPP TS 29.222 [9], clause A.2 | aef-id | Not required to be supported. | -| | 3GPP TS 29.222 [9], clause A.2 | data-format | Not required to be supported. | -| | 3GPP TS 29.222 [9], clause A.2 | api-cat | Not required to be supported. | -| | 3GPP TS 29.222 [9], clause A.2 | preferred-aef-loc | Not required to be supported. | -| | 3GPP TS 29.222 [9], clause A.2 | supported-features | Not required to be supported. | -| | 3GPP TS 29.222 [9], clause A.2 | api-supported-features | Not required to be supported. | -| | 3GPP TS 29.222 [9], clause A.2 | ue-ip-addr | Not required to be supported. | -| | 3GPP TS 29.222 [9], clause A.2 | service-kpis | Not required to be supported. | - -## A.2.3 Service events subscription API - -### A.2.3.1 Introduction - -The Open API for this service is reusing the CAPIF\_Events\_API as specified in clause A.2.3.2 with exceptions specified in clause A.2.3.3 below. - -### A.2.3.2 CAPIF\_Events\_API - -The Open API for the SME service events subscription API specified in clause 6.3 reuses the CAPIF\_Events\_API as specified in 3GPP TS 29.222 [9], clause A.4. - -The API version of the SME service events subscription API as specified in clause 6.3.2 shall use the CAPIF\_Events\_API OpenAPI version as specified in Table A.2.3.2-1 - -**Table A.2.3.2-1** - -| API name | API version | CAPIF OpenAPI version | -|---------------------------------|-------------|-----------------------| -| Service events subscription API | 1.2.0 | 1.3.0 | - -### A.2.3.3 Adaptations and Exceptions - -Table A.2.3.3-1 lists exceptions and adaptations related to CAPIF message content when re-using the CAPIF\_Events\_API in the context of the present document. - -**Table A.2.3.3-1: Message content exceptions and adaptations when reusing the CAPIF\_Events\_API** - -| Data type | Reference | Attributes | Exceptions/Adaptations | -|----------------------------|--------------------------------|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| AccessControlPolicyListExt | 3GPP TS 29.222 [9], Clause A.4 | | Not required to be supported. | -| CAPIFEvent | 3GPP TS 29.222 [9], Clause A.4 | | See clause B.3.5. | -| CAPIFEventDetail | 3GPP TS 29.222 [9], Clause A.4 | accCtrlPollList | Not required to be supported. | -| | | invocationLogs | Not required to be supported. | -| | | apiTopoHide | Not required to be supported. | -| CAPIFEventFilter | 3GPP TS 29.222 [9], Clause A.4 | apiInvokerIds | Shall be set to the value of "rAppId" for an API-consuming rApp. | -| | | aeIds | Shall be set to the value of "rAppId" if an rApp produces the API.
Shall be set to an identifier related to the SMO/Non-RT RIC framework functions if these produce the API.
See table A.2.2.3-1. | -| | | ReportingInformation | Not required to be supported. | -| EventNotification | 3GPP TS 29.222 [9], Clause A.4 | invocationLogs | Not required to be supported. | -| | | apiTopoHide | Not required to be supported. | -| EventSubscription | 3GPP TS 29.222 [9], Clause A.4 | supportedFeatures | Not required to be supported. | -| | | eventReq | Not required to be supported. | -| TopologyHiding | 3GPP TS 29.222 [9], Clause A.4 | | Not required to be supported. | - -## A.2.4 Bootstrap API - -### A.2.4.1 Introduction - -The Open API for this service as specified in clause A.2.4.2. - -### A.2.4.2 Bootstrap API - -``` - -openapi: 3.0.3 -info: - title: 'BootStrap' - version: 1.0.0 - description: | - API for BootStrap service. - R1 Common definitions - O-RAN.WG2.R1AP_Common.yaml. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/scclALLIANCE. - All rights reserved. -license: - name: SCCL - url: https://o-ran.org/sccl - -externalDocs: - description: 'O-RAN.WG2.R1AP' - url: 'https://www.o-ran.org/specifications' - -servers: - - url: '{apiRoot}/bootstrap/v1/' - variables: - apiRoot: - description: 'apiRoot as defined in clause 5.3 in O-RAN.WG2.R1AP' - default: 'https://example.com' - -paths: - -``` - -``` - -'/bootstrap-info': - get: - description: 'To discover the entry points into Service management and exposure ' - responses: - '200': - description: '.' - content: - application/json: - schema: - $ref: '#/components/schemas/BootstrapInformation' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -components: - schemas: - BootstrapInformation: - type: object - properties: - apiEndpoints: - type: array - items: - $ref: '#/components/schemas/ApiEndpointInformation' - ApiEndpointInformation: - type: object - properties: - apiName: - type: string - description: 'Name of the API ("service-apis" or "published-apis")' - tokenEndPoint: - $ref: 'TS29122_CAPIF_publish_Service_API.yaml#/components/schemas/InterfaceDescription' - description: 'Token endpoint shall be provided if the API requires authorization over OAuth2.0' - nullable: true - apiEndPoint: - $ref: 'TS29122_CAPIF_publish_Service_API.yaml#/components/schemas/InterfaceDescription' - description: 'End point of the API' - nullable: true - required: - - apiName - - apiEndPoint - -``` - -## A.3 Data management and exposure service - -### A.3.1 Data registration API - -#### A.3.1.1 Introduction - -The Open API for the Data Registration API is specified in clause A.3.1.2. - -#### A.3.1.2 Data registration API - -``` - -openapi: 3.0.3 -info: - title: 'Data registration service' - version: 2.0.0-alpha.3 - -``` - -``` - -description: | - API for Data registration service. - R1 Common definitions - O-RAN.WG2.R1AP_Common.yaml. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/scclALLIANCE. - All rights reserved. -license: - name: SCCL - url: https://o-ran.org/sccl - -externalDocs: - description: 'O-RAN.WG2.R1AP' - url: 'https://www.o-ran.org/specifications' - -servers: - - url: '{apiRoot}/data-registration/v2/' - variables: - apiRoot: - description: 'apiRoot as defined in clause 5.3 in O-RAN.WG2.R1AP' - default: 'https://example.com' - -paths: - '/production-capabilities': - post: - description: 'Registers the capabilities of a Data Producer related to a DME type as specified in clause 7.1.5.2.3.1.' - tags: - - Registered DME type production capabilities - requestBody: - required: true - content: - application/json: - schema: - $ref: '#/components/schemas/DmeTypeRelatedCapabilities' - responses: - '201': - description: 'Success case 201 created' - content: - application/json: - schema: - $ref: '#/components/schemas/DmeTypeRelatedCapabilities' - headers: - Location: - description: 'URI of the newly created Individual registered DME type production capability' -resource' - required: true - schema: - type: string - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '405': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' - '409': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' - '413': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' - '415': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - -``` - -``` - - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' - - '/production-capabilities/{registrationId}': - parameters: - - name: registrationId - in: path - description: 'The DME type production capabilities registration identifier as defined in clause 7.1.5.3.2' - required: true - schema: - $ref: '#/components/schemas/registrationId' - put: - description: 'Updates the DME type production capability associated with the registrationId as specified in clause 7.1.5.3.2' - tags: - - Individual registered DME type production capability - requestBody: - required: true - content: - application/json: - schema: - $ref: '#/components/schemas/DmeTypeRelatedCapabilities' - responses: - '200': - description: 'Success case 200 with updated information' - content: - application/json: - schema: - $ref: '#/components/schemas/DmeTypeRelatedCapabilities' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '411': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/411' - '413': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' - '415': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' - get: - description: 'Retrieves the registered DME type production capability associated with the registrationId as specified in clause 7.1.5.3.3.' - tags: - - Individual registered DME type production capability - responses: - '200': - description: 'Success case 200 with queried information' - content: - application/json: - schema: - $ref: '#/components/schemas/DmeTypeRelatedCapabilities' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - -``` - -``` - - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -delete: - description: 'Deletes the DME type production capability associated with the registrationId as specified in clause 7.3.1.' - tags: - - Individual registered DME type production capability - responses: - '204': - description: 'The registration was deleted' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' - -components: - schemas: - registrationId: - description: 'The related DME type production capabilities registration identifier' - type: string - example: '12345' - DmeTypeRelatedCapabilities: - description: 'Represents capabilities of a Data Producer related to providing data instances of a DME type, as defined in clause 7.1.8.1.2.' - type: object - properties: - dmeTypeDefinition: - $ref: '#/components/schemas/DmeTypeDefinition' - constraints: - description: 'Formulates producer constraints or constraints applicable to the consumption related to the DME type based on the dataProductionSchema' - type: object - dataAccessEndpoint: - $ref: 'TS29222_CAPIF_Publish_Service_API.yaml#/components/schemas/InterfaceDescription' - dataDeliveryMode: - type: array - items: - $ref: '#/components/schemas/DataDeliveryMode' - description: 'Supported modes for data delivery (e.g., one-time data request or continuous data subscription).' - required: - - dmeTypeDefinition - - dataDeliveryMode - DmeTypeDefinition: - description: 'Represents information about a DME type, as defined in clause 7.1.8.1.3.' - type: object - -``` - -``` - -properties: - dmeTypeId: - $ref: '#/components/schemas/DmeTypeIdStruct' - metadata: - $ref: '#/components/schemas/Metadata' - dataProductionSchema: - type: object - description: 'Schema that defines the information necessary to formulate a data request or data -subscription. If this attribute is not present, the schema is assumed to be known from the DME type -definition that is referenced by dmeTypeId.' - dataDeliverySchemas: - description: 'List of delivery schemas supported by the producer for the DME type being -registered.' - type: array - items: - $ref: '#/components/schemas/DeliverySchema' - dataDeliveryMechanisms: - description: 'Supported data delivery mechanisms as defined in clause B.4.4.2.' - type: array - items: - $ref: '#/components/schemas/DataDeliveryMechanism' -required: -- dmeTypeId -- metadata -- dataDeliverySchemas -- dataDeliveryMechanisms -DmeTypeIdStruct: - description: 'Represents the identifier of a DME type, as defined in clause B.4.4.1.' - type: object - properties: - namespace: - type: string - description: 'Indicating the entity responsible for the DME type definition.' - example: 'ORAN' - name: - type: string - description: 'Name of the DME type. The string can be any character except ":" (colon).' - pattern: '^[^:]{1,}S$' - example: 'RanOamPmData' - version: - type: string - description: 'Version of the DME type. The versioning and allowed characters are according to -SemVer [11]' - example: '1.0.0' - required: - - namespace - - name - - version -DeliverySchema: - description: 'Represents a delivery schema supported by the Data Producer, as defined in clause -7.1.8.1.5.' - type: object - properties: - type: - $ref: '#/components/schemas/SchemaTypes' - deliverySchemaId: - type: string - description: 'A Data Producer may support one or more delivery schemas and for each supported -schema type a delivery schema identifier is assigned. A Data Consumer uses this attribute while creating a -data job and request to deliver the data using specific schema type which is identified by this -attribute.' - schema: - type: string - description: 'The schema serialized to string. If this attribute is not present, the schema is -assumed to be known from the DME type definition that is referenced by dmeTypeId.' - required: - - type - - deliverySchemaId -DataDeliveryMechanism: - description: 'Represents the data delivery mechanism supported by a Data Producer, as defined in -clause B.4.4.2.' - -``` - -``` - -type: object -properties: - dataDeliveryMethod: - $ref: '#/components/schemas/DataDeliveryMethod' - kafkaDeliveryConfiguration: - $ref: '#/components/schemas/KafkaDeliveryConfiguration' -required: -- dataDeliveryMethod -oneOf: -- properties: - - dataDeliveryMethod: - enum: [STREAMING_KAFKA] - required: [kafkaDeliveryConfiguration] - description: 'This attribute shall be present if the deliveryMethod attribute is set to STREAMING_KAFKA' -DataDeliveryMethod: - type: string - description: 'Enumeration of data delivery methods supported by a Data Producer, as defined in clause B.4.3.1.' - enum: - - PULL_HTTP - - PUSH_HTTP - - STREAMING_KAFKA -Metadata: - description: 'Metadata that can be used in discovering the DME type' - type: object - properties: - dataCategory: - description: 'Defines the category of the DME type e.g., PM counters' - type: array - items: - type: string - minItems: 1 - rat: - description: 'Defines the radio access technology e.g., 5G' - type: array - items: - type: string - minItems: 1 - required: - - dataCategory -SchemaTypes: - description: 'Enumeration of schema types supported for data delivery, as defined in clause 7.1.8.2.3.1.' - type: string - enum: - - JSON_SCHEMA - - XML_SCHEMA - - PROTOBUF_SCHEMA - - AVRO_SCHEMA -KafkaDeliveryConfiguration: - description: 'These configuration will be applied if STREAMING_KAFKA is selected as delivery method as defined in clause B.4.4.3' - type: object - properties: - numPartitions: - description: 'Number of partitions' - type: integer - cleanUpPolicy: - description: 'cleanUpPolicy is based on cleanup.policy defined in the Kafka Documentation [15].' - type: string - compressionType: - description: 'compressionType is based on compression.type defined in the Kafka Documentation [15].' - type: string - retentionBytes: - description: 'retentionBytes is based on retention.bytes defined in the Kafka Documentation [15]. This attribute is applicable ONLY when cleanUpPolicy is set to DELETE' - type: integer - retentionMs: - -``` - -``` - -description: 'retentionMs is based on retention.ms defined in the Kafka Documentation [15]. This -attribute is applicable ONLY when cleanUpPolicy is set to DELETE' -type: integer -required: -- cleanUpPolicy -- compressionType -DataDeliveryMode: -type: string -description: 'Enumeration of data delivery modes supported by a Data Producer, as defined in clause -7.3.8.2.3.1' -enum: -- ONE_TIME #description: 'indicate the data job to be created is for on-time data delivery, -i.e., for data request.' -- CONTINUOUS #description: 'indicate the data job to be created is for continuous data delivery, -i.e., for data subscription.' - -``` - -## A.3.2 Data discovery API - -### A.3.2.1 Introduction - -The Open API for the Data Discovery API is specified in clause A.3.2.2. - -### A.3.2.2 Data discovery API - -``` - -openapi: 3.0.3 -info: - title: 'Data discovery service' - version: 2.0.1 - description: | - API for Data discovery service. - R1 Common definitions - O-RAN.WG2.R1AP_Common.yaml. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/scclALLIANCE. - All rights reserved. - license: - name: SCCL - url: https://o-ran.org/sccl - -externalDocs: - description: 'O-RAN.WG2.R1AP' - url: 'https://www.o-ran.org/specifications' - -servers: -- url: '{apiRoot}/data-discovery/v2/' - variables: - apiRoot: - description: 'apiRoot as defined in clause 5.3 in O-RAN.WG2.R1AP' - default: 'https://example.com' - -paths: - /dme-types: - get: - description: 'To discover the available DME types' - parameters: - - name: identity-namespace - in: query - description: 'Identity namespace to match the "namespace" part of the "dmeTypeId" attribute' - schema: - type: string - - name: identity-name - in: query - description: 'Identity name to match the "name" part of the "dmeTypeId" attribute.' - schema: - type: string - - name: data-category - in: query - -``` - -``` - -description: 'Set of data category entries, all of which to match entries of the "dataCategory" -attribute.' -schema: - type: array - explode: false - items: - type: string -responses: - '200': - description: 'The response body contains the result of the search over the list of registered -APIs.' - content: - application/json: - schema: - type: array - items: - $ref: 'O- -RAN.WG2.R1AP_DataRegistration.yaml#/components/schemas/DmeTypeRelatedCapabilities' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '414': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/414' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -/dme-types/{dmeTypeId}: - get: - description: To obtain information about an individual DME type. - parameters: - - name: dmeTypeId - in: path - required: true - schema: - $ref: '#/components/schemas/dmeTypeId' - responses: - '200': - description: The response body contains information about the DME type. - content: - application/json: - schema: - $ref: 'O- -RAN.WG2.R1AP_DataRegistration.yaml#/components/schemas/DmeTypeRelatedCapabilities' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '414': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/414' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - -``` - -``` - - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -components: - schemas: - dmeTypeId: - type: string - description: 'The DmeTypeId is constructed based on the three parts separated by ":" (colon) - {dmeTypeId} = {namespace}:{name}:{version}. See O- - RAN.WG2.R1AP_DataRegistration.yaml#/components/schemas/DmeTypeIdStruct for the definition of "namespace", - "name" and "version".' - -``` - -## A.3.3 Data access API - -### A.3.3.1 Introduction - -The Open API for the Data access API is specified in clause A.3.3.2. - -### A.3.3.2 Data access API - -``` - -openapi: 3.2.0 -info: - title: 'Data access service' - version: 2.0.0-alpha.3 - description: | - API for Data access service. - R1 Common definitions - O-RAN.WG2.R1AP_Common.yaml. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/scclALLIANCE. - All rights reserved. - license: - name: SCCL - url: https://o-ran.org/sccl - -externalDocs: - description: 'O-RAN.WG2.R1AP' - url: 'https://www.o-ran.org/specifications' - -servers: - - url: '{apiRoot}/data-access/v2/' - variables: - apiRoot: - description: 'apiRoot as defined in clause 5.3 in O-RAN.WG2.R1AP' - default: 'https://example.com' - -paths: - '/data-jobs': - post: - description: 'To create a data job' - tags: - - Create all data jobs - requestBody: - required: true - content: - application/json: - schema: - $ref: '#/components/schemas/DataJobInfo' - responses: - '201': - description: 'Success case 201 created' - content: - application/json: - schema: - $ref: '#/components/schemas/DataJobInfo' - headers: - Location: - -``` - -``` - - description: 'Contains the URI of the newly created resource' - required: true - schema: - type: string - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '405': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' - '409': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' - '413': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' - '415': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' - callbacks: - DataAvailabilityNotification: - '{$request.body.dataAvailabilityNotificationUri}': - post: - description: 'Notification on the availability of requested data, with the "type" attribute -set to "org.o-ran.DME.DATA_AVAILABILITY" and the "data" attribute containing a -"DataAvailabilityNotification" structure defined in clause 7.3.8.1.5.' - requestBody: - required: true - content: - application/cloudevents+json: - schema: - $ref: '# O-RAN.WG2.R1AP_Notification.yaml#/components/Notification' - responses: - '204': - description: 'The notification was delivered' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -'/data-jobs/{dataJobId}': - parameters: - - name: dataJobId - in: path - required: true - schema: - $ref: '#/components/schemas/dataJobId' - get: - description: 'To get the created data job' - tags: - - Individual data job - -``` - -``` - -responses: - '200': - description: 'Success case 200 OK' - content: - application/json: - schema: - $ref: '#/components/schemas/DataJobInfo' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -put: - description: 'To update the created data job' - tags: - - Individual data job - requestBody: - required: true - content: - application/json: - schema: - $ref: '#/components/schemas/DataJobInfo' - responses: - '200': - description: 'The data job was updated' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -delete: - description: 'To delete the created data job' - tags: - - Individual data job - responses: - '204': - description: 'The data job was deleted' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - -``` - -``` - - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -'/data-jobs/{dataJobId}/status': - description: 'To get the status of the created data job' - tags: - - Individual data job - parameters: - - name: dataJobId - in: path - required: true - schema: - $ref: '#/components/schemas/dataJobId' - get: - description: 'To get the status of the created data job' - tags: - - Individual data job - responses: - '200': - description: 'The data job status is returned' - content: - application/json: - schema: - $ref: '#/components/schemas/DataJobStatus' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -components: - schemas: - dataJobId: - description: 'A successful created data job is identified by dataJobId ' - type: string - DataJobInfo: - description: 'Information related to a data job' - allOf: - - type: object - properties: - dataDeliveryMode: - $ref: '#/components/schemas/DataDeliveryMode' - dmeTypeId: - $ref: '#/components/schemas/DmeTypeIdStruct' - productionJobDefinition: - description: 'Job description based on the DME type specific dataProductionSchema' - type: object - dataDeliveryMethod: - $ref: '#/components/schemas/DataDeliveryMethod' - dataDeliverySchemaId: - description: 'A delivery schema identifier provided by a Data Producer during the data registration procedure' - type: string - required: [ dataDeliveryMode, dmeTypeId, productionJobDefinition, dataDeliveryMethod, dataDeliverySchemaId ] - - type: object - oneOf: - - properties: - dataDeliveryMethod: - type: string - -``` - -``` - - enum: [ PULL_HTTP ] - dataDeliveryMode: - type: string - enum: [ ONE_TIME ] - required: - - pullDeliveryDetailsHttp - - properties: - dataDeliveryMethod: - type: string - enum: [ PULL_HTTP ] - dataDeliveryMode: - type: string - enum: [ CONTINUOUS ] - required: - - dataAvailabilityNotificationUri - - properties: - dataDeliveryMethod: - type: string - enum: [STREAMING_KAFKA] - required: - - streamingConfigurationKafka - - properties: - dataDeliveryMethod: - type: string - enum: [ PUSH_HTTP ] - required: - - pushDeliveryDetailsHttp -DataDeliveryMode: - description: 'This indicates whether the data instance is created in a one-time data delivery (data -request) or continuously (data subscription)' - type: string - enum: - - ONE_TIME - - CONTINUOUS -DataDeliveryMethod: - description: 'This indicates supported delivery method' - type: string - enum: [ PULL_HTTP, PUSH_HTTP, STREAMING_KAFKA ] -PullDeliveryDetailsHttp: - description: 'The PullDeliveryDetailsHttp data type signals how to pull data using the HTTP -protocol.' - readOnly: true - type: object - properties: - dataPullUri: - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/schemas/Uri' - required: [ dataPullUri ] -PushDeliveryDetailsHttp: - description: 'The PushDeliveryDetailsHttp data type signals how to push data using the HTTP -protocol.' - type: object - properties: - dataPushUri: - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/schemas/Uri' - required: [ dataPushUri ] -StreamingConfigurationKafka: - description: 'The StreamingConfigurationKafka data type signals a data streaming configuration for -the Kafka protocol.' - type: object - properties: - topicName: - description: 'Name of the Kafka topic' - type: string - kafkaBootstrapServers: - description: 'Server configuration' - type: array - items: - $ref: '#/components/schemas/ServerAddressWithPort' - required: [ topicName, kafkaBootstrapServers ] -ServerAddressWithPort: - description: 'Server configuration' -``` - -``` - -type: object -properties: - hostname: - description: 'string identifying a hostname shall be formatted according to clause 2.3.1 as -defined in IETF RFC 1035 [19]' - type: string - portAddress: - description: 'Port address, e.g. 9092' - type: integer - minimum: 1 - maximum: 65535 - required: [ hostname, portAddress ] -DataAvailabilityNotification: - description: 'Availability of the data' - type: object - properties: - dataJobId: - description: 'data job identifier' - type: string - pullDeliveryDetailsHttp: - $ref: '#/components/schemas/PullDeliveryDetailsHttp' -DataJobStatus: - description: 'The status of the data job' - type: string - $ref: 'TS28623_GenericNrm.yaml#/components/schemas/ProcessMonitor' -DmeTypeIdStruct: - description: 'Defining the attributes of DME type identifier' - type: object - properties: - namespace: - type: string - description: 'Indicating the entity responsible for the DME type definition.' - name: - type: string - description: 'Name of the DME type. The string can be any character except ":" (colon)' - pattern: '^[^:]{1,}$' - version: - type: string - description: 'Version of the DME type. The versioning and allowed characters are according to -SemVer [11]' - required: [ namespace, name, version ] - -``` - -### A.3.4 HTTP based Push data API - -Deliberately, no OpenAPI is specified for this API in the present document. - -**NOTE:** OpenAPI requires the definition of the valid content types for the request message content. However, this API is agnostic with respect to the content type of the data carried in the request message. Within the DME services, the valid content types are defined as part of separate data message schemas which specify the structure of the data to be carried over the API. Because of the requirement to fix the content types that can be carried over the API, defining an OpenAPI would restrict the versatility of the API. - -### A.3.5 HTTP based Pull data API - -Deliberately, no OpenAPI is specified for this API in the present document. - -**NOTE:** OpenAPI requires the definition of the valid content types for the response message content. However, this API is agnostic with respect to the content type of the data carried in the response message. Within the DME services, the valid content types are defined as part of a separate data message schema which specifies the structure of the data to be carried over the API. Because of the requirement to fix the content types that can be carried over the API, defining an OpenAPI would restrict the versatility of the API. - -## A.3.6 Data offer API - -### A.3.6.1 Introduction - -The Open API for the Data offer API is specified in clause A.3.6.2. - -### A.3.6.2 Data offer API - -``` - -openapi: 3.0.3 -info: - title: 'Data offer service' - version: 2.0.0-alpha.1 - description: | - API for Data offer service. - R1 Common definitions - O-RAN.WG2.R1AP_Common.yaml. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/scclALLIANCE. - All rights reserved. - license: - name: SCCL - url: https://o-ran.org/sccl - -externalDocs: - description: 'O-RAN.WG2.R1AP' - url: 'https://www.o-ran.org/specifications' - -servers: - - url: '{apiRoot}/data-offer/v1' - variables: - apiRoot: - description: 'apiRoot as defined in clause 5.3 in O-RAN.WG2.R1AP' - default: 'https://example.com' - apiConsumerId: - description: 'Identifier of API Consumer' - default: '' - -paths: - '/offers': - post: - description: 'Allows to create a new data offer' - tags: - - All data offers - requestBody: - required: true - content: - application/json: - schema: - $ref: '#/components/schemas/DataOfferInfo' - responses: - '201': - description: 'Success case 201 created' - content: - application/json: - schema: - $ref: '#/components/schemas/DataOfferInfo' - headers: - Location: - description: 'Contains the URI of the newly created resource' - required: true - schema: - type: string - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - -``` - -``` - - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '405': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' - '409': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' - '413': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' - '415': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -links: - notifyDataAvailabilityLink: - operationId: notifyDataOfferDataAvailability - parameters: - notificationSink: "$response.body#/dataAvailabilityNotificationUri" - description: 'The URI referring to the notification target, local to the API Producer.' - server: - url: {apiRoot} - variables: - apiRoot: - description: 'target operation to be called against the server defined in -{apiRoot} i.e. notificationSink is local to {apiRoot}' - default: 'https://example.com' -callbacks: - -DataOfferTerminationNotification: - '{$request.body.dataOfferTerminationNotificationUri}': - post: - description: 'Notification on termination of data offer by the API producer, with the "type" -attribute set to "org.o-ran.DME.DATA_OFFER_TERMINATION" and the "data" attribute containing a -"DataOfferTerminationNotification" structure defined in clause 7.6.8.1.3.' - requestBody: - required: true - content: - application/cloudevents+json: - schema: - $ref: '#O-RAN.WG2.R1AP_Notification.yaml#/components/Notification ' -responses: - '204': - description: 'The notification was delivered' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -'/offers/{dataOfferId}': - parameters: - - name: dataOfferId - in: path - required: true - schema: - type: string - -``` - -``` - -delete: - description: 'To delete the data offer' - tags: - - Individual data offer - responses: - '204': - description: 'The data offer was deleted.' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -'/{notificationSink}': - post: - description: 'Notification on the availability of offered data, with the "type" attribute set to - "org.o-ran.DME.DATA_OFFER_DATA_AVAILABILITY" and the "data" attribute containing a - "DataOfferDataAvailabilityNotification" structure defined in clause 7.6.8.1.4.' - operationId: notifyDataOfferDataAvailability - parameters: - - name: notificationSink - in: path - required: true - schema: - type: string - requestBody: - required: true - content: - application/cloudevents+json: - schema: - $ref: 'O-RAN.WG2.R1AP_Notification.yaml#/components/Notification' - responses: - '204': - description: 'The notification was delivered' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -components: - schemas: - DataOfferInfo: - description: 'Information related to a data offer' - type: object - properties: - dataDeliveryMode: - $ref: 'O-RAN.WG2.R1AP_DataAccess.yaml#/components/schemas/DataDeliveryMode' - dmeTypeId: - $ref: 'O-RAN.WG2.R1AP_DataDiscovery.yaml#/components/schemas/DmeTypeId' - productionJobDefinition: - -``` - -``` - -description: 'Job description based on the DME type specific dataProductionSchema' -type: object -dataDeliveryMethods: - type: array - items: - $ref: ' O-RAN.WG2.R1AP_DataAccess.yaml#/components/schemas/DataDeliveryMethod' -dataDeliverySchemaIds: - description: 'A delivery schema identifier provided by a Data Producer during the data -registration procedure' - type: array - items: - type: string -pullDeliveryDetailsHttp: - $ref: ' O-RAN.WG2.R1AP_DataAccess.yaml#/components/schemas/PullDeliveryDetailsHttp' -dataAvailabilityNotificationUri: - $ref: '/components/schemas/DataOfferAvailabilityNotification' -dataOfferTerminationNotificationUri: - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/schemas/Uri' -pushDeliveryDetailsHttp: - $ref: 'O-RAN.WG2.R1AP_DataAccess.yaml#/components/schemas/PushDeliveryDetailsHttp' -streamingConfigurationKafka: - $ref: 'O-RAN.WG2.R1AP_DataAccess.yaml#/components/schemas/StreamingConfigurationKafka' -required: [ "dataDeliveryMode", "dmeTypeId", "productionJobDefinition", " dataDeliveryMethods ", -"dataDeliverySchemaIds", "dataOfferTerminationNotificationUri"] -DataOfferTerminationNotification: - description: 'Termination of a data offer by the API producer' - type: object - properties: - dataOfferId: - description: 'Identifies the deleted data offer' - type: string - required: ["dataOfferId"] -DataOfferDataAvailabilityNotification: - description: 'Availability of the data' - type: object - properties: - dataOfferId: - description: 'data offer identifier' - type: string - pullDeliveryDetailsHttp: - $ref: 'O-RAN.WG2.R1AP_DataAccess.yaml#/components/schemas/PullDeliveryDetailsHttp' - required: ['dataOfferId', 'pullDeliveryDetailsHttp']: - type: string - required: ["dataOfferId"] - -``` - -## A.4 RAN OAM related services - -### A.4.1 Configuration management API - -#### A.4.1.1 Introduction - -The Open API for this service is reusing the provisioning management service API as specified in clause A.4.1.2 with exceptions specified in clause A.4.1.3 below. - -#### A.4.1.2 Configuration management API - -The Open API for the Configuration management API specified in clause 8.1 reuses the Provisioning management service API (TS28532\_ProvMnS.yaml) as specified in 3GPP TS 28.532 [20], clause A.1.1. - -The API version of the Configuration management API as specified in clause 8.1.2 shall use the Provisioning management service OpenAPI version as specified in Table A.4.1.2-1. - -**Table A.4.1.2-1** - -| API name | API version | ProvMnS OpenAPI version | -|------------------------------|-------------|-------------------------| -| Configuration management API | 1.0.0 | 18.5.0 | - -#### A.4.1.3 Adaptations and Exceptions - -Table A.4.1.3-1 lists exceptions and adaptations related to HTTP methods when re-using the TS28532\_ProvMnS \_API in the context of the present document. - -**Table A.4.1.3-1: HTTP methods exceptions and adaptations when reusing the TS28532\_ProvMnS \_API** - -| HTTP Methods | Reference | Attributes | Exceptions/Adaptations | -|--------------|-----------------------------------|------------|-----------------------------------------------------------------| -| PUT | 3GPP TS 28.532 [20], clause A.1.1 | | HTTP operation not required to be supported in current version. | -| DELETE | 3GPP TS 28.532 [20], clause A.1.1 | | HTTP operation not required to be supported in current version. | - -Within the PATCH request message content, the following content types shall be supported. - -- application/3gpp-json-patch+json (3GPPTS 32.158 [29]). - -### A.4.2 Fault management API - -#### A.4.2.1 Introduction - -The Open API for this service is reusing the provisioning management service API as specified in clause A.4.2.2 with exceptions specified in clause A.4.2.3 below. - -#### A.4.2.2 Fault management API - -The Open API for the fault management API specified in clause 8.1 reuses the Provisioning management service API (TS28111\_FaultNrm.yaml) as specified in 3GPP TS 28.111 [26], clause A.1.3. - -The API version of the fault management API as specified in clause 8.2.2 shall use the FaultNRM service OpenAPI version as specified in Table A.4.2.2-1. - -**Table A.4.2.2-1** - -| API name | API version | FaultNrm OpenAPI | -|----------------------|-------------|------------------| -| Fault management API | 1.0.0 | 18.1.0 | - -#### A.4.2.3 Adaptations and Exceptions - -NOTE: The adaptations and exceptions are not specified in present version of the document. - -### A.4.3 Configuration schema information API - -#### A.4.3.1 Introduction - -The Open API for the Configuration schema information API is specified in clause A.4.3.2. - -### A.4.3.2 Configuration schema information API - -``` - -openapi: 3.0.3 -info: - title: 'Configuration Schema information API' - version: 1.0.1 - description: This API enables the API Consumer to retrieve configuration schema information based on the procedure defined in R1GAP [5]. - R1 Common definitions - O-RAN.WG2.R1AP_Common.yaml. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/scclALLIANCE. - All rights reserved. -license: - name: SCCL - url: https://o-ran.org/sccl - -apiVersion: - description: See clause 8.3.2 (Version of the API, e.g., v1) - default: v1 -externalDocs: - description: 'O-RAN.WG2.R1AP' - url: 'https://www.o-ran.org/specifications' -servers: - - url: '{apiRoot}/ran-oam-cm-schema-info/v1' - variables: - apiRoot: - description: 'apiRoot as defined in clause 10.3 in O-RAN.WG2.R1AP' - default: 'https://example.com' -paths: - '/schemas': - get: - summary: Get all schema information - description: 'Retrieves configuration schema information' - responses: - '200': - description: 'The results with the schema information' - content: - application/json: - schema: - type: array - items: - $ref: '#/components/schemas/Schema' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '405': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' - '409': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' - '413': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' - '415': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' - -``` - -``` - -'/schemas/{schemaId}': - get: - summary: Get individual schema information - parameters: - - name: schemaId - in: path - required: true - description: Where schemaId = "name" (for latest revision or if revision is not available) or -"name@revision" for a specific revision. - schema: - type: string - responses: - '200': - description: The results with the schema information matching the request. - content: - application/json: - schema: - $ref: '#/components/schemas/Schema' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '405': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' - '409': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' - '413': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' - '415': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -components: - schemas: - Schema: - type: object - required: - - name - - location - - type - properties: - name: - type: string - description: The unique name of the schema. - revision: - type: string - description: The unique revision of the schema (required for YANG). - location: - type: string - format: uri - description: Location of where to find the schema content. - type: - $ref: '#/components/schemas/SchemaType' - description: This data type is designed to provide extensibility. As specified in clause -8.3.8.2.3.1, Only YANG is supported in the present version of the present document. - namespace: - type: string - description: The namespace of the schema, (See NOTE 1, clause 8.3.8.2.3.1, only applicable if -type is YANG). - features: - type: array - -``` - -``` - - items: - type: string - description: List of supported features (See NOTE 1, clause 8.3.8.2.3.1, only applicable if type -is YANG). - deviations: - type: array - items: - type: string - description: List of schema deviation(s) (See NOTE 1, clause 8.3.8.2.3.1, only applicable if type -is YANG). - SchemaType: - type: string - enum: - - YANG - description: Enumeration of schema types. - -``` - -## A.5 A1 related service - -### A.5.1 A1 policy management API - -#### A.5.1.1 Introduction - -The Open API for the A1 policy management API is specified in clause A.5.1.2. - -#### A.5.1.2 A1 policy management API - -``` - -openapi: 3.0.3 -info: - title: 'A1 policy management API' - version: 1.0.1 - description: | - API for A1 policy management service. - R1 Common definitions - O-RAN.WG2.R1AP_Common.yaml. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/scclALLIANCE. - All rights reserved. -license: - name: SCCL - url: https://o-ran.org/sccl - -externalDocs: - description: 'O-RAN.WG2.R1AP' - url: 'https://www.o-ran.org/specifications' - -servers: - - url: '{apiRoot}/a1-policy-management/v1' - variables: - apiRoot: - description: 'apiRoot as defined in clause 5.3 in O-RAN.WG2.R1AP' - default: 'https://example.com' - -paths: - '/policy-types': - get: - description: 'To query A1 policy type identifier' - tags: - - All A1 policy types - parameters: - - name: nearRtRicId - in: query - description: 'The identifier of Near-RT RIC' - schema: - type: string - - name: typeName - -``` - -``` - -in: query -description: 'The unique label of the policy type' -schema: - type: string -responses: - '200': - description: 'Success case 200 with queried information' - content: - application/json: - schema: - type: array - items: - $ref: '#/components/schemas/PolicyTypeInfo' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -'/policy-types/{policyTypeId}': - parameters: - - name: policyTypeId - in: path - required: true - schema: - $ref: '#/components/schemas/policyTypeId' - get: - description: 'To query AI policy type' - tags: - - Individual AI policy type - responses: - '200': - description: 'Success case 200 with queried information' - content: - application/json: - schema: - $ref: '#/components/schemas/PolicyTypeObject' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -'/policies': - get: - description: 'To query AI policy type' - tags: - -``` - -``` - -- All A1 policies -parameters: - - name: nearRtRicId - in: query - description: 'The identifier of Near-RT RIC' - schema: - type: string - - name: policyTypeId - in: query - description: 'The identifier of the policy' - schema: - type: string -responses: - '200': - description: 'Success case 200 with queried information' - content: - application/json: - schema: - type: array - items: - $ref: '#/components/schemas/PolicyInformation' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -post: - description: 'To create A1 policies' - tags: - - All A1 policies - requestBody: - required: true - content: - application/json: - schema: - $ref: '#/components/schemas/PolicyObjectInformation' - responses: - '201': - description: 'Success case 201 created' - content: - application/json: - schema: - $ref: '#/components/schemas/PolicyObjectInformation' - headers: - Location: - description: 'Contains the URI of the newly created resource' - required: true - schema: - type: string - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '405': - -``` - -``` - - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' - '409': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' - '413': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' - '415': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -'/policies/{policyId}': - parameters: - - name: policyId - in: path - required: true - schema: - $ref: '#/components/schemas/policyId' - put: - description: 'To update a created policy' - tags: - - Individual A1 policy - requestBody: - required: true - content: - application/json: - schema: - "$ref": "#/components/schemas/PolicyObject" - responses: - 200: - description: 'The policy was updated' - content: - application/json: - schema: - "$ref": "#/components/schemas/PolicyObject" - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '411': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/411' - '413': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' - '415': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' - get: - description: 'To query created A1 policy' - tags: - - Individual A1 policy - responses: - '200': - description: 'Success case 200 with queried information' - content: - -``` - -``` - - application/json: - schema: - $ref: '#/components/schemas/PolicyObject' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -delete: - description: 'To delete the created AI policy' - tags: - - Individual AI policy - responses: - '204': - description: 'The created AI policy was deleted' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -'/policies/subscriptions': - post: - summary: Create a new AI policy status subscription - description: This operation creates a new subscription for receiving AI policy status notifications. - tags: - - AI policy status subscription - requestBody: - required: true - content: - application/json: - schema: - $ref: '#/components/schemas/PolicyStatusSubscription' - responses: - '201': - description: 'Success case 201 created' - content: - application/json: - schema: - $ref: '#/components/schemas/PolicyStatusSubscription' - headers: - Location: - description: 'Contains the URI of the newly created resource' - required: true - schema: - type: string - -``` - -``` - - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -'/policies/subscriptions/{subscriptionId}': - parameters: - - name: subscriptionId - in: path - required: true - schema: - $ref: '#/components/schemas/subscriptionId' - get: - summary: Get details of an AI policy status subscription - description: This operation retrieves information about a specific subscription. - tags: - - AI policy status subscription - responses: - '200': - description: OK - content: - application/json: - schema: - $ref: '#/components/schemas/PolicyStatusSubscription' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' - put: - description: 'This operation modifies an existing subscription.' - tags: - - AI policy status subscription - requestBody: - required: true - content: - application/json: - schema: - "$ref": "#/components/schemas/PolicyStatusSubscription" - responses: - 200: - description: 'The policy was updated' - content: - application/json: - schema: - -``` - -``` - - "$ref": "#/components/schemas/PolicyObject" - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '411': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/411' - '413': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' - '415': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' - - delete: - summary: Delete an A1 policy status subscription - description: This operation removes a subscription. - tags: - - A1 policy status subscription - responses: - '204': - description: No Content -components: - schemas: - policyTypeId: - description: 'Policy Type identifier as defined in A1AP [23], clause 6.2.3.1.3' - type: string - policyId: - description: 'Policy Identifier of a policy' - type: string - NearRtRicId: - description: 'Near-RT RIC identifier' - type: string - subscriptionId: - description: 'subscription identity of the policy' - type: string - PolicyObject: - description: 'Policy Object is a JSON representation of an A1 policy; the A1 policies are specified in A1TD [24]' - type: object - PolicyTypeObject: - description: 'policy type object as defined in A1TD' - type: object - PolicyTypeInformation: - description: 'Available policy types and for each policy type identifier the Near-RT RIC identifiers of those Near-RT RICs that support the related A1 policy type' - type: object - properties: - policyTypeId: - description: 'Identity of the policy type' - type: string - nearRtRicId: - $ref: '#/components/schemas/NearRtRicId' - required: ["policyTypeId", "nearRtRicId"] - PolicyInformation: - description: 'Near-RT RIC identifiers where A1 policies exist and for each Near-RT RIC identifier the policy identifiers of those policies that exist in that Near-RT RIC' - type: object - properties: - -``` - -``` - -policyId: - description: - $ref: '#/components/schemas/policyId' - -nearRtRicId: - $ref: '#/components/schemas/NearRtRicId' -required: ["policyId", "nearRtRicId"] -PolicyObjectInformation: - description: 'Information related to the creation of the policy' - type: object - properties: - policyObject: - description: 'Policy Object is a JSON representation of an AI policy; the AI policies are specified in AI TD [24]' - type: object - nearRtRicId: - $ref: '#/components/schemas/NearRtRicId' - policyTypeId: - $ref: "#/components/schemas/policyTypeId" - required: ["policyObject", "nearRtRicId"] - PolicyStatusSubscription: - description: 'PolicyStatusSubscription data type represents the subscription information of AI policy status' - type: object - properties: - subscriptionScope: - $ref: '#/components/schemas/QueryFilter' - notificationDestination: - type: URI - description: URI for policy status notifications - policyIdList: - type: array - items: - $ref: '#/components/schemas/policyId' - policyTypeIdList: - type: array - items: - $ref: '#/components/schemas/policyTypeId' - nearRtRicIdList: - type: array - items: - $ref: '#/components/schemas/nearRtRicId' - QueryFilter: - type: string - enum: - - OWN #'indicate the AI policies created by API Consumer ' - - OTHERS #'indicate the AI policies created other API Consumers' - - ALL #'indicate the AI policies created by any API Consumers' - -``` - -## A.6 AI/ML workflow service - -### A.6.1 AI/ML model registration API - -#### A.6.1.1 Introduction - -The Open API for the AI/ML model registration API is specified in clause A.6.1.2. - -#### A.6.1.2 AI/ML model registration API - -``` - -openapi: 3.0.3 -info: - title: 'AI/ML Model registration API ' - version: 1.0.1 - description: API for registering an AI/ML model - API for AI/ML Model registration service. - -``` - -``` - -R1 Common definitions - O-RAN.WG2.R1AP_Common.yaml. -Copyright 2026 O-RAN ALLIANCE e.V. -Licensed under the Standards Collaboration -Copyright License Version 1.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at -https://www.o-ran.org/scclALLIANCE. -All rights reserved. -license: - name: SCCL - url: https://o-ran.org/sccl - -externalDocs: - description: 'O-RAN.WG2.R1AP' - url: 'https://www.o-ran.org/specifications' - -servers: - - url: '{apiRoot}/ai-ml-model-registration/{apiVersion}' - -paths: - '/model-registrations': - post: - description: 'Register a new AI/ML model' - tags: - - Registered AI/ML Model registration details - requestBody: - required: true - content: - application/json: - schema: - $ref: '#/components/schemas/ModelRelatedInformation' - responses: - '201': - description: 'Success case 201 created' - content: - application/json: - schema: - $ref: '#/components/schemas/ModelRelatedInformation' - headers: - Location: - description: 'Contains the URI of the newly created resource' - required: true - schema: - type: string - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '405': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' - '409': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' - '413': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' - '415': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' - - '/model-registrations/{modelRegistrationId}': - get: - summary: Get details of a registered AI/ML model - parameters: - -``` - -``` - -- in: path - name: modelRegistrationId - required: true - schema: - type: string -responses: - '200': - description: AI/ML model details retrieved successfully - content: - application/json: - schema: - $ref: '#/components/schemas/ModelRelatedInformation' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '405': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' - '409': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' - '413': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' - '415': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -put: - summary: Update information of a registered AI/ML model - parameters: - - in: path - name: modelRegistrationId - required: true - schema: - type: string - requestBody: - required: true - content: - application/json: - schema: - $ref: '#/components/schemas/ModelRelatedInformation' - responses: - '200': - description: AI/ML model information updated successfully - content: - application/json: - schema: - $ref: '#/components/schemas/ModelRelatedInformation' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '405': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' - '409': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' - '413': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' - -``` - -``` - - '415': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' - -delete: - summary: Deregister an AI/ML model - parameters: - - in: path - name: modelRegistrationId - required: true - schema: - type: string - responses: - '204': - description: AI/ML model deregistered successfully - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -components: - schemas: - ModelRelatedInformation: - type: object - properties: - modelId: - $ref: '#/components/schemas/ModelId' - description: - type: string - modelInformation: - $ref: '#/components/schemas/ModelInformation' - modelLocation: - type: string - format: uri - required: - - modelId - - description - - modelInformation - ModelId: - type: object - description: 'Identifier of a model' - properties: - modelName: - type: string - description: 'name of AI/ML model as specified in R1GAP' - modelVersion: - type: string - description: 'version of AI/ML model as specified in R1GAP' - artifactVersion: - type: string - format: uri - description: 'artifact version of AI/ML model as specified in R1GAP' - required: - -``` - -``` - - - modelName - - modelVersion -ModelInformation: - type: object - properties: - metadata: - description: 'Meta data of AI/ML Model' - $ref: '#/components/schemas/MetaData' - inputDataType: - type: array - description: 'Input data type for the model, the structure of dataTypeId is specified in clause -7.1.8' - items: - $ref: 'O-RAN.WG2.R1AP_DataRegistration.yaml#/components/schemas/DataTypeId' # DataTypeId is -specified (clause 7.1.8) - outputDataType: - type: array - description: 'Output data type for the model, the structure of dataTypeId is specified in -(clause 7.1.8)' - items: - $ref: 'O-RAN.WG2.R1AP_DataRegistration.yaml#/components/schemas/DataTypeId' # DataTypeId is -specified (clause 7.1.8) - targetEnvironment: - type: array - description: 'Information on the target environment is required for deployment of an AI/ML -model' - items: - $ref: '#/components/schemas/TargetEnvironment' - required: - - metadata - - inputDataType - - outputDataType -MetaData: - type: object - properties: - author: - type: string - description: 'Author of an AI/ML model' - owner: - type: string - required: - - author -TargetEnvironment: - type: object - properties: - platformName: - type: string - description: 'Name of the platform' - environmentType: - type: string - description: 'Name of the platform execution service type, and this is dependent on the -platformName' - dependencyList: - type: string - format: uri - description: 'Location to the template that has all the list of dependencies platform must -provide needs to be installed for the model. (for example, scikit-learn 0.21.3)' - required: - - platformName - - environmentType - - dependencyList - -``` - -## A.6.2 AI/ML model discovery API - -### A.6.2.1 Introduction - -The Open API for the AI/ML model discovery API is specified in clause A.6.2.2. - -## A.6.2.2 AI/ML model discovery API - -``` - -openapi: 3.0.0 -info: - title: AI/ML Model Discovery API - version: 1.1.1 # Placeholder: actual version to be defined in clause 10.2.2. - description: | - R1 Common definitions - O-RAN.WG2.R1AP_Common.yaml. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/scclALLIANCE. - All rights reserved. - license: - name: SCCL - url: https://o-ran.org/sccl - -servers: - - url: '{apiRoot}/ai-ml-model-discovery/{apiVersion}' - description: Base URL for the AI/ML Model Discovery API. - variables: - apiRoot: - description: The root path of the API, as defined in clause 5.2 of the specification. - default: https://example.com/api # Example placeholder for apiRoot - apiVersion: - description: The version of the API, as defined in clause 10.2.2 of the specification. - default: v1.1 # Example placeholder for apiVersion - -paths: - /models: - get: - summary: Retrieve all registered AI/ML models - description: | - This resource represents all registered AI/ML models in the Non-RT RIC. - This GET method supports filtering by `model-name` and `model-version` - query parameters. If multiple query parameters are provided, these - shall be combined with an AND logical operation when evaluating the query. - operationId: getAllRegisteredModels - parameters: - - name: model-name - in: query - description: Name of the model as specified in R1GAP[5]. - required: false - schema: - type: string - - name: model-version - in: query - description: Version of the model as specified in R1GAP[5]. - required: false - schema: - type: string - responses: - '200': - description: | - The message content of the GET response carries an array of model - identifiers and metadata of the models. - content: - application/json: - schema: - type: array - items: - $ref: '#/components/schemas/ModelRelatedInformation' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - -``` - -``` - - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '414': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/414' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' - -/models/{modelId}: - get: - summary: Retrieve an individual AI/ML model's location - description: | - This resource represents the model location for a specific AI/ML model, - identified by its unique `modelId`. - operationId: getIndividualModelLocation - parameters: - - name: modelId - in: path - description: The unique identifier of the AI/ML model. - required: true - schema: - $ref: '#/components/schemas/ModelId' - responses: - '200': - description: | - The model location related information associated with the `modelId` - has been successfully retrieved. The response contains the - `ModelLocationInformation` as a representation of the resource. - content: - application/json: - schema: - $ref: '#/components/schemas/ModelLocationInformation' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '414': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/414' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' - -components: - schemas: - ModelRelatedInformation: - type: object - description: 'The ModelRelatedInformation data type represents registration information for an AI/ML -model' - required: - - modelId - - metadata - properties: - -``` - -``` - -modelId: - $ref: 'O-RAN.WG2.R1AP_AI/ML_model_registrtaion_API.yaml/components/schemas/ModelId' - description: "Identifier of a model as specified in clause 10.1.8.1.3" -metadata: - type: string - description: "Description of the AIML model that includes the AI/ML model related information -and training related information" -ModelLocationInformation: - type: object - description: | - Represents the location and related information for an individual AI/ML model. - required: - - locationUrl - properties: - locationUri: - type: string - format: uri - description: The URI where the AI/ML model artifact can be accessed or downloaded. - example: "https://model-repo.example.com/models/123e4567-e89b-12d3-a456-426614174000/v1.0" - modelId: # Including modelId here for context, though not strictly required by the prompt's schema -definition - $ref: 'O-RAN.WG2.R1AP_AI/ML_model_registrtaion_API.yaml/components/schemas/ModelId' - description:"Identifier of a model as specified in clause 10.1.8.1.3" - -``` - -## A.6.3 AI/ML model training API - -### A.6.3.1 Introduction - -The Open API for the AI/ML model API is specified in clause A.6.3.2. - -### A.6.3.2 AI/ML model training API - -``` - -openapi: 3.0.3 -info: - title: 'AI/ML Model Training API' - version: 1.0.0-alpha.2 - description: | - R1 Common definitions - O-RAN.WG2.R1AP_Common.yaml. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/scclALLIANCE. - All rights reserved. -license: - name: SCCL - url: https://o-ran.org/sccl -externalDocs: - description: 'O-RAN.WG2.R1AP' - url: 'https://www.o-ran.org/specifications' -servers: - - url: '{apiRoot}/ai-ml-model-training/v1' - variables: - apiRoot: - description: 'apiRoot as defined in clause 10.3 in O-RAN.WG2.R1AP' - default: 'https://example.com' -paths: - '/training-jobs': - post: - summary: Create a new AI/ML model training job - tags: - - Creation of AI/ML model training job - requestBody: - required: true - -``` - -``` - -content: - application/json: - schema: - $ref: "#/components/schemas/TrainingJobDescription" -responses: - '201': - description: 'Success case 201 created' - content: - application/json: - schema: - $ref: '#/components/schemas/TrainingJobInfo' - headers: - Location: - description: 'Contains the URI of the newly created resource' - required: true - schema: - type: string - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '405': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/405' - '409': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/409' - '413': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/413' - '415': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/415' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' - -'/training-jobs/{trainingJobId}': - delete: - summary: 'Delete an AI/ML model training job' - tags: - - Delete AI/ML model training job - responses: - '204': - description: 'The AI/ML model training job was AI/ML deleted' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' - -'/training-jobs/{trainingJobId}/status': - get: - summary: Get the status of an AI/ML model training job - -``` - -``` - -tags: - - Status of AI/ML model training job -parameters: - - in: path - name: trainingJobId - required: true - schema: - type: string -responses: - '200': - description: 'Training job status retrieved successfully' - content: - application/json: - schema: - type: array - items: - $ref: '#/components/schemas/TrainingJobStatus' - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' - '406': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/406' - '429': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/429' - '500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - '502': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/502' - '503': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/503' -components: - schemas: - TrainingJobDescription: - type: object - properties: - modelId: - $ref: "#O-RAN.WG2.R1AP_ai_ml_model_registration.yaml/components/schemas/modelId" - description: "The model identifier which contains model name, model version, and artifact -version see clause 10.1.8.1.3-1 in R1AP." - modelLocation: - type: string - format: uri - description: "Location of the AI/ML model." - trainingDataset: - type: string - format: uri - description: "Information for reference to the training dataset." - validationDataset: - type: string - format: uri - description: "Information for reference to the validation dataset." - trainingConfig: - type: object - description: "Configuration of AI/ML model training based on training service producer specific -trainingConfigSchema." - notificationDestination: - type: string - format: uri - description: "Callback URI where the notification should be delivered to." - consumerRAppId: - type: string - description: "rAppId of the training service consumer rApp." - producerRAppId: - type: string - description: "rAppId of the training service producer rApp." - required: - -``` - -``` -- modelId -``` - -## A.6.4 AI/ML model deployment API - -### A.6.4.1 Introduction - -The Open API for the AI/ML model deployment API is specified in clause A.6.4.2. - -### A.6.4.2 AI/ML model deployment API - -``` -openapi: 3.0.3 -info: - title: 'AI/ML Model Deployment API' - version: 1.0.0-alpha.1 - description: | - R1 Common definitions - O-RAN.WG2.R1AP_Common.yaml. - Copyright 2026 O-RAN ALLIANCE e.V. - Licensed under the Standards Collaboration - Copyright License Version 1.0 (the "License"); - you may not use this file except in compliance with the License. - You may obtain a copy of the License at - https://www.o-ran.org/scclALLIANCE. - All rights reserved. -license: - name: SCCL - url: https://o-ran.org/sccl -externalDocs: - description: 'O-RAN.WG2.R1AP' - url: 'https://www.o-ran.org/specifications' -servers: - - url: '{apiRoot}/ai-ml-model-deployment/v1' - variables: - apiRoot: - description: 'apiRoot as defined in clause 5.2 in O-RAN.WG2.R1AP' - default: 'https://example.com' -paths: - '/model-deployments': - post: - summary: Request AI/ML model deployment - tags: - - Request AI/ML model deployment - requestBody: - required: true - content: - application/json: - schema: - $ref: '#/components/schemas/ModelDeploymentInformation' - responses: - '201': - description: 'AI/ML model deployment created successfully' - content: - application/json: - schema: - $ref: '#/components/schemas/ModelDeploymentInformation' - headers: - Location: - description: 'URI of the created deployment resource' - required: true - schema: - type: string - '400': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/400' - '401': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/401' - '403': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/403' - '404': -``` - -``` -$ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/404' -'500': - $ref: 'O-RAN.WG2.R1AP_Common.yaml#/components/responses/500' - -components: - schemas: - ModelDeploymentInformation: - type: object - properties: - modelId: - $ref: '#/components/schemas/ModelId' - description: 'Unique identifier for the AI/ML model.' - deploymentLocation: - type: string - format: uri - description: 'URI for the deployment location.' - deploymentConfig: - type: object - description: 'Configuration parameters for AI/ML model deployment.' - required: - - modelId - - deploymentLocation - - DeploymentStatus: - type: object - properties: - deploymentId: - type: string - description: 'Identifier for the AI/ML model deployment.' - status: - type: string - description: 'Current status of the deployment.' - details: - type: string - description: 'Additional details about the deployment status.' -``` - -## Annex B (normative): Common data types for R1 service APIs - -### B.1 Introduction - -In the subsequent clauses, common data types for the following areas are defined: - -- Generic usage, -- Service management and exposure, -- Data management and exposure, -- RAN OAM. - -### B.2 Common data types for Generic Usage - -#### B.2.1 Introduction - -This clause defines common data types for generic usage. - -#### B.2.2 Simple data types - -**Table B.2.2-1: Simple data types for generic use** - -| Type name | Type Definition | Description | -|------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Uri | string | A string formatted according to IETF RFC 3986 [8]. | -| NotificationType | string | A string formatted as concatenation of "org.o-ran.", a string representing the service name (e.g. "DME"), a dot ".", and an API-specific name for the event type (e.g. "DATA_AVAILABILITY") defined in the API specification. | - -#### B.2.3 Enumeration - -##### B.2.3.1 Void - -#### B.2.4 Structured data types - -##### B.2.4.1 Data type: ProblemDetails - -The ProblemDetails structure is specified in table B.2.4.1-1. It is based on IETF RFC 7807 [10] and shall comply with the provisions defined there. - -**Table B.2.4.1-1: Definition of type ProblemDetails** - -| Attribute name | Data type | P | Cardinality | Description | -|----------------|-----------|---|-------------|--------------------------------------------------------------------------------| -| type | string | O | 0..1 | URI reference according to IETF RFC 3986 [8] that identifies the problem type. | -| title | string | O | 0..1 | Human-readable summary of the problem type. | -| status | number | O | 0..1 | The HTTP status code. | -| detail | string | O | 0..1 | Human-readable explanation. | -| instance | string | O | 0..1 | URI reference that identifies the specific occurrence of the problem. | - -B.2.4.2 Void - -B.2.4.3 Void - -B.2.4.4 Void - -B.2.4.5 Data type: Notification - -The general Notification data structure is specified in table B.2.4.5-1, aligned with the CloudEvents specification [30]. - -**Table B.2.4.5-1: Definition of type Notification** - -| Attribute name | Data type | P | Cardinality | Description | -|-----------------|------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| id | string | M | 1 | Unique identifier of the event, unique within the scope identified by the “source” attribute, as defined in CloudEvents [30]. | -| specversion | string | M | 1 | The version of the CloudEvents specification which the event uses, as defined in CloudEvents [X]. E.g. the spec version is 1.0 aligned with the version of the CloudEvents specification [30]. (See NOTE). | -| type | NotificationType | M | 1 | See table B.2.2. | -| source | string | M | 1 | The source from which the event from has originated, as defined in CloudEvents [30]. | -| dataschema | Uri | O | 0..1 | Identifies the schema that data adheres to, as defined in CloudEvents [30]. (See NOTE). | -| datacontenttype | object | O | 0..1 | Content type of the value of the “data” attribute, as defined in CloudEvents [30]. (See NOTE). | -| data | string | O | 0..1 | Application event payload data encoded as declared by the “datacontenttype” attribute. The structure of this attribute is defined by the API that specifies the notification type. | -| time | string | O | 0..1 | Timestamp when the event is generated, as defined in CloudEvents [30]. | - -NOTE : The naming convention is aligned with that of CloudEvents, hence deviating from the “lowerCamel” convention used commonly in the R1 service APIs. - -## B.2.5 Re-used data types - -Re-used data types are not defined in the present document. - -# B.3 Common data types for Service management and exposure - -## B.3.1 Introduction - -This clause defines common data types for usage in the service management and exposure APIs. - -Clause B.3.5 references and profiles data types defined in external specifications and defines restrictions on and adaptations of these data type for their usage within the context of the service management and exposure APIs. - -## B.3.2 Simple data types - -None. - -## B.3.3 Enumerations - -None. - -## B.3.4 Structured data types - -### B.3.4.1 Data type: VersionExtensions - -The VersionExtensions data structure specified in table B.3.4.1-1 defines extensions to the CAIF "Version" data type which allows to signal the versions supported for an interface endpoint. - -**Table B.3.4.1-1: Definition of type VersionExtensions** - -| Attribute name | Data type | P | Cardinality | Description | -|-----------------|---------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------| -| fullApiVersions | array(string) | M | 1..N | List of version strings, as defined in clause 5.2, to signal the API versions supported by the API Producer for a particular major API version. | - -### B.3.4.2 Data type: ServiceProperties - -The ServiceProperties data structure specified in table B.3.4.2-1 defines a container to be used to register and discover service-specific properties of individual service APIs. - -**Table B.3.4.2-1: Definition of type ServiceProperties** - -| Attribute name | Data type | P | Cardinality | Description | -|---------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------| -| serviceCapabilities | object | M | 0..1 | Service capabilities. The content of this attribute is service-specific and is defined per service. | - -## B.3.5 Re-used data types - -Table B.3.5-1 references data types that are reused from external documents by the service management and exposure APIs and defines restrictions on and adaptations of these data type for their usage within the context of the service management and exposure APIs. - -**NOTE:** All externally-defined data types that are directly used in request or response message content of the service management and exposure APIs (such as ServiceAPIDescription) are listed below. In addition, those externally-defined data types are listed that are descendants of a directly used data type and for which restrictions and adaptations are defined in the present document. Other external descendant data types are not listed, as they are referenced directly in the external specification. - -**Table B.3.5-1: Re-used data types** - -| Data type | Reference | Comments | Applicability | -|-----------------------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| ServiceAPIDescription | 3GPP TS 29.222 [9], clause 8.2.4.2.2 | The following attributes are not applicable in the context of the R1 SME services and therefore need not be supported: "supportedFeatures", "shareableInfo", "serviceAPICategory", "ccfId", "apiSuppFeats", "pubApiPath" | | -| InterfaceDescription | 3GPP TS 29.222 [9], clause 8.2.4.2.3 | The CAPIF feature "ExtendedIntfDesc" shall be supported . | | -| AefProfile | 3GPP TS 29.222 [9], clause 8.2.4.2.4 |

The AEF profile holds information related to the discoverable APIs produced by a single API Producer.

In case the API Producer is an rApp, the "aeId" attribute shall contain the value of the rAppID.

The following attributes are not applicable in the context of the R1 SME services and need therefore not be supported: "aeLocation", "domainName", "serviceKpis", and "ueIpRange".

| | -| Version | 3GPP TS 29.222 [9], clause 8.2.4.2.5 | The following additional attribute shall be supported: "vendorSpecific-o-ran.org" of type VersionsList as specified in clause B.3.4.1, to signal the full API versions supported | | -| CAPIEvent | 3GPP TS 29.222 [9], clause 8.3.4.3.3 | The enumeration values "SERVICE_API_AVAILABLE", "SERVICE_API_UNAVAILABLE" and "SERVICE_API_UPDATE" shall be supported. The remaining enumeration values are not applicable in the context of the R1 SME services and therefore need not be supported. | | - -## B.4 Common data types for Data Management and Exposure - -### B.4.1 Introduction - -This clause defines common data types for DME usage. - -### B.4.2 Simple data types - -**Table B.4.2-1: Simple data types** - -| Type Name | Type Definition | Description | -|-----------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| DmeTypeId | string | A DME type Id is constructed based on the three parts separated by ":" (colon)
{dataTypeId} = {namespace}:{name}:{version}
See clause B.4.4.1 for the definition of "namespace", "name" and "version". | - -### B.4.3 Enumerations - -#### B.4.3.1 Enumeration: DataDeliveryMethod - -**Table B.4.3.1-1: Enumeration: DataDeliveryMethod** - -| Enumeration value | Description | -|-------------------|----------------------------------------------------------------------------| -| STREAMING_KAFKA | Kafka based streaming delivery mechanism as defined in R1TP [7], clause 6. | -| PULL_HTTP | HTTP based pull delivery mechanism as defined in clause 7.5. | -| PUSH_HTTP | HTTP based push delivery mechanism as defined in clause 7.4. | - -### B.4.4 Structured data types - -#### B.4.4.1 Data type: DmeTypeIdStruct - -The DmeTypeIdStruct data type contains the attributes defined in table B.4.4.1-1. - -**Table B.4.4.1-1: Definition of type DmeTypeIdStruct** - -| Attribute Name | Data type | P | Cardinality | Description | -|----------------|-----------|---|-------------|----------------------------------------------------------------------------------------------| -| namespace | string | M | 1 | Indicating the entity responsible for the DME type definition. | -| name | string | M | 1 | Name of the DME type. The string shall not contain the colon ":" character. | -| version | string | M | 1 | Version of the DME type. The versioning and allowed characters are according to SemVer [11]. | - -#### B.4.4.2 Data type: DataDeliveryMechanism - -The DataDeliveryMechanism data type contains the attributes defined in table B.4.4.2-1. - -**Table B.4.4.2-1: Definition of type DataDeliveryMechanism** - -| Attribute Name | Data type | P | Cardinality | Description | -|------------------------------------------------------------------------------------------------------|----------------------------|---|-------------|-------------------------------------------------------------------| -| dataDeliveryMethod | DataDeliveryMethod | M | 1 | Delivery method supported by a Data Producer. See clause B.4.3.1. | -| kafkaDeliveryConfiguration | KafkaDeliveryConfiguration | C | 0..1 | See clause B.4.4.3 (NOTE). | -| NOTE: This attribute shall be presented if the "deliveryMethod" attribute is set to STREAMING_KAFKA. | | | | | - -#### B.4.4.3 Data type: KafkaDeliveryConfiguration - -The KafkaDeliveryConfiguration data type contains the attributes defined in table B.4.4.3-1. - -**Table B.4.4.3-1: Definition of type KafkaDeliveryConfiguration** - -| Attribute Name | Data type | P | Cardinality | Description | -|-----------------|-----------|---|-------------|----------------------------------------------------------------------------------------| -| numPartitions | integer | O | 0..1 | Number of partitions. | -| cleanUpPolicy | string | M | 1 | cleanUpPolicy is based on cleanup.policy defined in the Kafka Documentation [15]. | -| compressionType | string | M | 1 | compressionType is based on compression.type defined in the Kafka Documentation [15] . | -| retentionBytes | integer | C | 0..1 | retentionBytes is based on retention.bytes defined in the Kafka Documentation [15]. | -| retentionMs | integer | C | 0..1 | retentionMs is based on retention.ms defined in the Kafka Documentation [15]. | - -NOTE: Presence condition “C” this attribute may be included when cleanUpPolicy is set to DELETE. - -### B.4.5 Re-used data types - -Re-used data types are not defined in the present document. - -## B.5 Common data types for RAN OAM related services - -### B.5.1 Introduction - -This clause defines common data types for usage in the RAN OAM related service APIs. - -Clause B.5.5 references and profiles data types defined in external specifications and defines restrictions on and adaptations of these data type for their usage within the context of the RAN OAM related APIs. - -### B.5.2 Simple data types - -None. - -### B.5.3 Enumerations - -None. - -### B.5.4 Structured data types - -None. - -### B.5.5 Re-used data types - -Table B.5.5-1 references data types that are reused from external documents by the RAN OAM related service APIs and defines restrictions on and adaptations of these data type for their usage within the context of the RAN OAM related APIs. - -NOTE: All externally defined data types that are directly used in request or response message content of the RAN OAM related service APIs are listed below. In addition, those externally defined data types are listed that are descendant of a directly used data type and for which restrictions and adaptations are defined in the present document. Other external ancestor data types are not listed, as they are referenced directly in the external specification. - -**Table B.5.5-1: Re-used data types** - -| Data type | Reference | Comments | Applicability | -|------------------|---------------------------------------------|-----------------------------------|----------------------| -| Resource | 3GPP TS 28.532 [20], clause 12.1.1.4.1a.1 | All the attributes are supported. | | -| Scope | 3GPP TS 28.532 [20], clause 12.1.1.4.1a.2 | All the attributes are supported. | | -| PatchItem | 3GPP TS 28.532 [20]ss, clause 12.1.1.4.1a.9 | All the attributes are supported. | | - ---- - -## Annex (informative): Bibliography - -ETSI GS NFV-SOL 015v1.2.1: “Protocols and Data Models; Specification of Patterns and Conventions for RESTful NFV-MANO APIs“, December 2020. - -## Annex (informative): Change history - -| Date | Revision | Description | -|------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2025.11.24 | 10.00 | updates to Open APIs to include the SCCL license, updates to data availability notifications for Data access API and for Data offer API and updated the configuration schema API to release version. | -| 2025.07.07 | 09.00 | Published with updating the Configuration management API, Data registration API, configuration schema API and AI/ML model discovery API, Void the clause of AI/ML model retrieve API, and adopting the specifications to TS template version04. | -| 2025.03.14 | 08.00 | Published with updating the Bootstrap API, RAN OAM CM API's, RAN OAM FM API's, Adding Configuration schema information API, AI/ML Model deployment API, AI/ML model retrieve API, Updates to AI/ML model registration API, AI/ML model discovery API and AI/ML model training API. | -| 2024.11.21 | 07.00 | Published with migration of all API's from Release 17 to Release 18 of 3GPP, Updated the A1 Policy management API and Model discovery API and moved the same to release version, Updated the Data registration API, Data access API and Data offer API by removing the consumerId from the uri structure. | -| 2024.07.18 | 06.00 | Published with addition of Bootstrap API in SME, AI/ML model registration, AI/ML model discovery, AI/ML model training API in AI/ML workflow service, Updated A1 policy management API, Uplifted all the DME, AI/ML,A1 policy management APIs in compliance with 29.501 URI Structure, and generalized the DME API to support further enhancements. Updated the naming of data type to DME type. | -| 2024.03.18 | 05.00 | Published with addition of A1 policy management API , RAN OAM CM and FM API , updates to data registration API and removing alpha indicator for data registration API. | -| 2023.11.20 | 04.00 | Published as version 04.00 with addition of Service events subscription API, data access API, Configuration management API and removed alpha indicator for data registration API , data discovery API , service events subscription API and data access API. | -| 2023.07.29 | 03.00 | Published version 03.00 | -| 2023.03.24 | 02.00 | Published version 02.00 | -| 2022.11.19 | 01.00 | Published version 01.00 | \ No newline at end of file diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/00504fc688ebcf131ccbeff94dfc9939_img.jpg deleted file mode 100644 index 1f736cf95c23a213c3fdfb25c16513492c291ea8..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/00504fc688ebcf131ccbeff94dfc9939_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3faa0f7026148616d072e350e9329f8b53db0425bb5281e5a2fca4d413c3d9c3 -size 18042 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/01b37b45a159c6e8efb7e2f67f99ba68_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/05d8710f69c476939295486ab1440350_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/05d8710f69c476939295486ab1440350_img.jpg deleted file mode 100644 index a6faa936abd31c860074d7c494d6c0d0a393d890..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/05d8710f69c476939295486ab1440350_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0cb5762757fd11d0961b3f183a107afa2b52305747764bb09667e551f4355eb7 -size 30736 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/05ec650892a1d3916ffe3d2a7ec29928_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0827b9260fe5458dbe416ebfc78c469e_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/08783c875dd39684fee7f2a40b584c64_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0931f3e098bd4539041de11c50cec2d2_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0931f3e098bd4539041de11c50cec2d2_img.jpg deleted file mode 100644 index 82c958db064b740c657c25221c7f0d2da391a2a6..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0931f3e098bd4539041de11c50cec2d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:cd1c12c95aeaf894f11d72e408e211f89ce1c0c0130363c602631f4192120342 -size 20114 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/09ec8c855800290ecbc282cfef399c32_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/09ec8c855800290ecbc282cfef399c32_img.jpg deleted file mode 100644 index 1934419c1d54c611023334119ebeba293b745347..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/09ec8c855800290ecbc282cfef399c32_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:98dd88cb764c04222921942629329d9e6e7bf7f2a82610a09c4f8cb0bb229b5d -size 23811 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/09fcf056902487318885284a6b43b08c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/09fcf056902487318885284a6b43b08c_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/09fcf056902487318885284a6b43b08c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0a65720e640be13541e947c06c7a8c7f_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0db2dd2a5c02140f5b395569f17ab91d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0db2dd2a5c02140f5b395569f17ab91d_img.jpg deleted file mode 100644 index 11a46ef5f129a14005d360f937550a17b8cf13e1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0db2dd2a5c02140f5b395569f17ab91d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e48cbe9812a1c5d77d7c4435cfd7f7b82a5d7850b2a614de49f5d3dfa1b57b6d -size 15508 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0e611959485447591664307862231ffd_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0e611959485447591664307862231ffd_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0e611959485447591664307862231ffd_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0fa5b60804100c3aead10404f9f226f9_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0fa5b60804100c3aead10404f9f226f9_img.jpg deleted file mode 100644 index b9d3a538b70907fba46ed3a64e03badc17a4e80e..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/0fa5b60804100c3aead10404f9f226f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9f3074155db4c402457f658f208d4fff51257c8a7d67629c86abeb42c35f2a1c -size 25360 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index d8f0264b92ff5f0b557c75de9f128fde3c488556..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:62aa973c54ec5a286ff3adfc660621d8e843d54798275206fa7405428feebace -size 4575 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/10b0dda884baae493ad958422d11b552_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/10b0dda884baae493ad958422d11b552_img.jpg deleted file mode 100644 index 87785010631772f75e0589e6e2f517315975a773..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/10b0dda884baae493ad958422d11b552_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e5dd02f5cd16cef19b1fbd3b77db19ba26fc87e4a31b5371899c803338e151c6 -size 18765 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1316d63eca7b84e13c27f55f0027b7b5_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1316d63eca7b84e13c27f55f0027b7b5_img.jpg deleted file mode 100644 index 62302177ba18c112c789c99fefecfd763d238956..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1316d63eca7b84e13c27f55f0027b7b5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6afa1b94f7580e4d8c0a5440f4ae5ebcc7e6ac3d1f60d38a5e640fe64f0f8bc -size 22758 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/13249a22bfff48bf6d20110d7228bfcd_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1396371bb5cf61891981fff2e338ec58_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/145d00f59802048185303f15937ea65c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/145d00f59802048185303f15937ea65c_img.jpg deleted file mode 100644 index 03461b60fdbc57f4262fb8e07916d147d076cae4..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/145d00f59802048185303f15937ea65c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d87488bb654ed0a1688ef3dbd195e071f54347fb3e0b9d6a365dd9a7bc3e6332 -size 31672 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/14af8d47efd24c21fddf71b2415b6397_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/153b4763edcf6b16d783052c7ad165f1_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index cd15d3d6f918cc6066ba42ec8f0244ce6a9b6549..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6278d4614448b34b99fb5bad2e01af582cf4a1c21f527994324dae32ed6c0d06 -size 4571 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1a827b10290f33d4fec04d0e8ef7a897_img.jpg deleted file mode 100644 index 82508d91e53af0340f6be235394848c5cc9fea09..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1a827b10290f33d4fec04d0e8ef7a897_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6209323b6cf191d245f93477ff3ff4b8aa0b474c3e95e22cd8705a3c2dd418e1 -size 24468 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1b2ad37940c441d410002c05ff71c7c5_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1b2ad37940c441d410002c05ff71c7c5_img.jpg deleted file mode 100644 index a521ab35e28cf9e45456e9b36f3f6357738fe14f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1b2ad37940c441d410002c05ff71c7c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:737984a3340c6663d07b5d51cc7fd63dae3ab73db969ff352f8dff03c9e5bcc6 -size 26959 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1baaba7a6e54e77197475726c871067d_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1bc1746388cb64bf23b356ce2365dfc2_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1bc1746388cb64bf23b356ce2365dfc2_img.jpg deleted file mode 100644 index a86b9bf3a8afde2bc6c4be6662a7f105cb409dfc..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1bc1746388cb64bf23b356ce2365dfc2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:dfdbadf89319e2d099b7e2f59c3fdb1973b6ed2f589f23bab61b42928b1849b8 -size 22350 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1d92d4ad55f2aa411dc849438982f26b_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1e7157ed1c2b915b5b1823b6ad189038_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/1f0d4018f872bfcffec260045c6dd734_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/200e768e8ed91aadff59c651287d1009_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/200e768e8ed91aadff59c651287d1009_img.jpg deleted file mode 100644 index e17335d773fccb7f282f47129e925c7f691f4462..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/200e768e8ed91aadff59c651287d1009_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2c8ee4f26e1a233ba09111a36fb689f14f5bf41c308a4aa5c5289ec1015abf65 -size 22068 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/20f6eb79fde32ab3f6b6757552e424ce_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/226da964acee69b4d04409dc4c06a042_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/226da964acee69b4d04409dc4c06a042_img.jpg deleted file mode 100644 index 8eda32684110480d1d5878cfd86cc7de4b47460b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/226da964acee69b4d04409dc4c06a042_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8602010f44bf8369c0177e60a919d4d674d12be78da8093644205d4347010683 -size 28436 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/226f5e462c99b71e08dc9abaa5ae260c_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/227840abf8cd09f4f3e83336421daccb_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/238754529581b74f0696943d436494bb_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/238754529581b74f0696943d436494bb_img.jpg deleted file mode 100644 index dd8eb4511a062ea6feb2ed2bc9918935582ae71b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/238754529581b74f0696943d436494bb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:75903515c938f2a6f7aa5a747af92ec20e7416663ac4b011edb12fe189baef3d -size 20696 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/253600420ae7bd7d0119563b895cbf8a_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/256ec100c3aeedb411eee5a09386812e_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2576e074afbb2a591f07da0fe1987ff1_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/27ac7312556b7c7fb279e4fb33be33cf_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/29f3760c0230631eb03f67030ef65ed0_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2a185522b492253375ed16f0c515c230_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2a185522b492253375ed16f0c515c230_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2a185522b492253375ed16f0c515c230_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg deleted file mode 100644 index cd15d3d6f918cc6066ba42ec8f0244ce6a9b6549..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6278d4614448b34b99fb5bad2e01af582cf4a1c21f527994324dae32ed6c0d06 -size 4571 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2cb201535956cd78d7fd3cc89f3c7d03_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg deleted file mode 100644 index 8787084f8e4b57d1cdf574ee10571b52724454a0..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:49f4a63ca673ec545bb2d1a78da11bfb016adbf839f0a38a5c798a2a338ae03b -size 27801 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2e4532799b1f5837a5d909b20ab68ab6_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2eea01382188b70064fa2818361d89f1_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2eea01382188b70064fa2818361d89f1_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/2eea01382188b70064fa2818361d89f1_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3117e1f4e4767bab3f5c7cfaf4804652_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/315bdbeafb39026e19b77c26b19d9d1f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/315bdbeafb39026e19b77c26b19d9d1f_img.jpg deleted file mode 100644 index 5ae78e6b3fd245af3fc842b86028e012590f6162..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/315bdbeafb39026e19b77c26b19d9d1f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:296ed937520cb6af52e6c307834ad0588ada6f6f25a1fbb9337db2ffe8fc9658 -size 25253 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/327ba94498e3381cf08eb41e3fd3d77f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/327ba94498e3381cf08eb41e3fd3d77f_img.jpg deleted file mode 100644 index 7f6d834561c6c757879dc85f348c33ddd50790ea..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/327ba94498e3381cf08eb41e3fd3d77f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:51bd716dc6b22781b5486ec3cf3d5db71277189924888f0580b967c1e3e6c52a -size 21975 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/35437f160e157760713aa85be471c3f3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/35437f160e157760713aa85be471c3f3_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/35437f160e157760713aa85be471c3f3_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/36e2350ea1a3ef6ca68c655394300a91_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/36e4a08fb5114c98c80f946714cc6c30_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3711f8e9365e67e6019303fc07924eed_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3711f8e9365e67e6019303fc07924eed_img.jpg deleted file mode 100644 index 4fb871c8f63e09b310490a8b5e1ceef9236d864f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3711f8e9365e67e6019303fc07924eed_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0ebff80b26c3919ab3b65468bb448ef23b374168cf30a6992b98a15e40c7e726 -size 20811 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/38222c3ae003223a67635bfcc6950fbb_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/38866d3f212726e1c8e92001ca0dd6f8_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3a4f4369128594c5db0aa6b853c0666e_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3a568746c00925506d5c39f2a86a5a63_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3a568746c00925506d5c39f2a86a5a63_img.jpg deleted file mode 100644 index 0edd59cd59a0c4c0bee6d0280c7f916f17b022d6..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3a568746c00925506d5c39f2a86a5a63_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:42d9d86aec2993344bd2bdae7442beceb812c6c127ef0360e03ff616a875f305 -size 27261 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg deleted file mode 100644 index 05358fbe29420bb03cdbaf2a6ffdbdf6a5adf4d0..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c93ec51d24ff23e33f3b3c4aac0b480abb381d3251d35fe51b044bdd58ecfb16 -size 33529 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3b89d812329a65ab156184a40524adf0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3b89d812329a65ab156184a40524adf0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3b89d812329a65ab156184a40524adf0_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg deleted file mode 100644 index fe98a935e3db9a951ec7d75a4ec66d9f3e6afa04..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/3e2dcee303cecdd31b7f9ec0d8942fed_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d291360d4dc2b0be8b0941df9a27fb39a43f06a9c684693b2f6bc0e4e0abb825 -size 29685 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/41863cc6f48c5a6ff0290186547042d9_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/446c0bd806260f25430cadb01a6786c7_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/44c649b1c110b4cd617810ae17342927_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/44c649b1c110b4cd617810ae17342927_img.jpg deleted file mode 100644 index 158934f6a4e00d723a39d0a122f08504e586d7af..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/44c649b1c110b4cd617810ae17342927_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:de5f51f08aea8e79e76634a2633c9ca111f7d2c06e6f9f3f6808431c09b7ea57 -size 23643 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/481b1f80fc31ebebb30d1f57d31e3af3_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/488b6387bc5fe15b9528eca7968a8733_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4932f76f000f1673ac40baf1419fbb3b_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/49b9b8bd6845ff94f361b147c84fc945_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/49b9b8bd6845ff94f361b147c84fc945_img.jpg deleted file mode 100644 index 7b17d9acebfb640fa471b6aabc2881f90c23c4da..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/49b9b8bd6845ff94f361b147c84fc945_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a0fbd7d59097b5a9f512dc5d2abda91f71a90e71fa3868231ce7b6ae17132533 -size 29093 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4a04896dfb569893fba50729314024f5_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4aa740e8119817a3f9b9f72d06eaa53d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4aa740e8119817a3f9b9f72d06eaa53d_img.jpg deleted file mode 100644 index 186cef172ede271774ca84ae39272f00222c4fc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4aa740e8119817a3f9b9f72d06eaa53d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:102b28878a4bb1c5b740dfb1859bdfd240e5e0bdd13b5db17f9df3e68ecb30ce -size 22749 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4b241e690aacaf391e2b28dd9307575c_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4b81ac66c571b3118659e4d9f47abb22_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg deleted file mode 100644 index e25442098c9c16f1fd5f3b9a8a0c4ebc6e01f69c..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4dc0d6f219d7eb8923d60e8cec8cbf0b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:440f6ccb036f92f13ee84b3760dc85a5a4902e615ea7b27cc6ea0ecb8eae4807 -size 15923 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/4f8349df2ca48959fefb7c42b2bc375e_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/5009e30a55479d3941af523871208f9d_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/5009e30a55479d3941af523871208f9d_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/527578a453197a501cd46c0d0e579cd1_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/528f6dcec0ac99b060b0da5883c82b8f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/528f6dcec0ac99b060b0da5883c82b8f_img.jpg deleted file mode 100644 index 5e5fd885ce089dc2463e8c0d42912262f7090bb2..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/528f6dcec0ac99b060b0da5883c82b8f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6b9c5397b92ce6c404ec3f2940bdd140e5895b295ac564861053eb6608368a11 -size 19247 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/52a225f71b166b0c65c2f29f32a79f7f_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/53499879d98034410ecba2c386c58f0c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/53499879d98034410ecba2c386c58f0c_img.jpg deleted file mode 100644 index f714c0dd22e80891c87ab16f2f55e10149cacd69..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/53499879d98034410ecba2c386c58f0c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ac34b8d5fed53e6e214ecf2e5720cc636bd9c51fd87c3c19dea0b859eb44ed9 -size 28850 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/568031aac86c633aab96b734dba3835e_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/568031aac86c633aab96b734dba3835e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/568031aac86c633aab96b734dba3835e_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/56ac11fb9683d7b846fb65c845d80f22_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/59368942873b0c35eef79a7a985025dc_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/59edd779768a6eb448c9b0ca5402346e_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/59fcc0e3699f239444841881a2e75da0_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/5a1abd59a95fa47ae192807de151e9eb_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/5a1abd59a95fa47ae192807de151e9eb_img.jpg deleted file mode 100644 index 06893efb4a36824965f03c0844c409e97faec350..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/5a1abd59a95fa47ae192807de151e9eb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c549f4ba555646c51f9990e2039bca2de8bb61e300da09deb5fa18780a92f35e -size 26504 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/60d6a326e6061d71ea69c9375ec96631_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/60f844d947ea0bccdd9f64d81d5f8d26_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/60f844d947ea0bccdd9f64d81d5f8d26_img.jpg deleted file mode 100644 index 67a4f01d1953847a38a05806f912823d8cabf33e..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/60f844d947ea0bccdd9f64d81d5f8d26_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:feb57510d958c25ec602c5e6646554b445a64468f2f441b64947425a1346bf56 -size 29162 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6254e6ff201e39d022a590c8b6e3de2b_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/627bd3eabebc7105a04e854f2c59f47d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/627bd3eabebc7105a04e854f2c59f47d_img.jpg deleted file mode 100644 index e7a4296cee790d0b72605e19303347137bba908a..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/627bd3eabebc7105a04e854f2c59f47d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4ea10c46a8db12f039c19147dcbb2cea77bae2488171c0f1946ea0f6592e218e -size 24701 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6588b1c7f14069d96744b473ad663248_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/659a041a7997f9eea79f4e2f3ba265a5_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/659a041a7997f9eea79f4e2f3ba265a5_img.jpg deleted file mode 100644 index 64fb978353deda051d11f2ad2cc96737236650e5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/659a041a7997f9eea79f4e2f3ba265a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:accd80da5698c710b68698789f2c06e8c317703361054b7dbf56cc87f5d7d103 -size 24523 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/66b2567aa84dd1d036931b056352e11e_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/66b2567aa84dd1d036931b056352e11e_img.jpg deleted file mode 100644 index eedc3d422415ccfa56f1546f477c185b9331e567..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/66b2567aa84dd1d036931b056352e11e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a5ea935e4bb148df74d4d7422bae979f55dcb7db9cb0617f601fd86b52aff70 -size 18481 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/66d5189a924662748cac6a9b22a272e9_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/66d5189a924662748cac6a9b22a272e9_img.jpg deleted file mode 100644 index 0ef77db83c942a0b398c93738fe22c4807bd15d8..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/66d5189a924662748cac6a9b22a272e9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c010f09c72042b2d711d08ec43a8efa7d7bd0e13fc55f509ad70de7255e6c36 -size 24047 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/675af5bb2357ce5b510e613d04f66bdc_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/675af5bb2357ce5b510e613d04f66bdc_img.jpg deleted file mode 100644 index d0199e9cb14084c1c6f7756253af96d3db62ae36..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/675af5bb2357ce5b510e613d04f66bdc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b7db4f6291ea415352df90deeaac121b651e1251402d8ae5de92e90623e5161e -size 24702 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/681c354e00e1c0fe098ba665ff155cb8_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6983ff962c0a32659de18c30790e1519_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6983ff962c0a32659de18c30790e1519_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6983ff962c0a32659de18c30790e1519_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6a9c5a85a12499d60c5a3a75c643b852_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6c6024603c6fd57b23210b79f573b3bd_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6c8a96787f532bd1fa4719e738cf556f_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6d8454e3fdef6561c6f64adf0092e9b9_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6da6e06f73c5bf331c5e55773dc6d010_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6f794c8c41326b510934ce3f3d622202_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/6ff798305e82bdf8233f1381ff9f7c49_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/713cb30a2b5e9f2cea007cefb2e27a40_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/713cb30a2b5e9f2cea007cefb2e27a40_img.jpg deleted file mode 100644 index 50a420450ee9d13bc1214919d47d9eb15ec96e2d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/713cb30a2b5e9f2cea007cefb2e27a40_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6f905c7f1b81c266d51752d5e9719436fba6a1dbda3ec6f0453931773503935b -size 28641 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/728298e0fbc8de5f3894ce6cb10fb413_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/76fb24764e6c9c644b30056855c81aa5_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/78b47bea9d645c52984f5f4c6740db05_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/79898de98da3367d0ea9beef38f5c01c_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7c66f12495a47e87f0a0314a0d3a2eff_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7d08458fbe0bd5f306c00c16d68b25f2_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7ef82ab74729923b27507495301d73a6_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7ef82ab74729923b27507495301d73a6_img.jpg deleted file mode 100644 index 9f86b2e98580a320bb9733e6e5355f8811456cf2..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7ef82ab74729923b27507495301d73a6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2a3eddbaaeac5c31d81cf0b65e15bf6a8d82f8ecd18438c9e3a7af661337eab6 -size 25346 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7f4320cee12fc1dbb865cc6b67462a91_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7f7718a1d18d1f9055d85871d02364b3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7f7718a1d18d1f9055d85871d02364b3_img.jpg deleted file mode 100644 index 0af162f4580d7228fab3cf2a79e75f607b37c210..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/7f7718a1d18d1f9055d85871d02364b3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1a7c4aa69b75ad1d6bc462a5f0e697388621a841fc938330f5b7cc16098a3f16 -size 32909 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/80d994053160f3b1d88b075564af9e57_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/80d994053160f3b1d88b075564af9e57_img.jpg deleted file mode 100644 index d6f07ba592aefd95eccd39651ae8ed8fe7e5d00c..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/80d994053160f3b1d88b075564af9e57_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:74de136d6d62c40c97ec11e28672e60dadbfc218d8a3460e31a1499b22d0c6cc -size 20057 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/81a736eb35b4bda9584394c61ef44aec_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/81a736eb35b4bda9584394c61ef44aec_img.jpg deleted file mode 100644 index f75fb42607c28b5f35955586aab7c5d2922533d4..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/81a736eb35b4bda9584394c61ef44aec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a54ee1bc244eba679ddacb9e36e0e19ee6861af5f0b15c1b2257ca577166cffc -size 16531 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/829cdaf00f7219d70e571064b2b13291_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/83ee9f10bd3636e192d68decf7f04cec_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/854df8ad60507803253274673f9062cf_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/85e7d6eb95be2fe34f09499ca16536de_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/85e7d6eb95be2fe34f09499ca16536de_img.jpg deleted file mode 100644 index 3a47fb333be95d1e64acd7cceeb5575aaab22622..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/85e7d6eb95be2fe34f09499ca16536de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e74012597e6990be1380f45f3392965cc31ac8d82ff8344e3123369dc74ad06d -size 22416 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/86692d82da6655813b5acf58a767a38c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/86692d82da6655813b5acf58a767a38c_img.jpg deleted file mode 100644 index a50bbe601d3193c53701d5303604da0cad6425c0..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/86692d82da6655813b5acf58a767a38c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ad09bc24b869e20bbca4c6223acd00d750839b93cb3c203743850ff689d52993 -size 21528 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8768e42bf1062f1af11f259fc52a92e9_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8768e42bf1062f1af11f259fc52a92e9_img.jpg deleted file mode 100644 index 3b44e1e8c91d7d5bcc47455a6d33164d4aed86f7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8768e42bf1062f1af11f259fc52a92e9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:568aab02f7da06c2441799a08f838598248bf898ff0466ae40137dff1ba34dd4 -size 30340 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8d129c93d18909f0643766f372e9ebf6_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8d138b6bf0be359dc7f079db4899bc41_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8d9be1ac4372e563dc3eb6d4aa5690d6_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8d9be1ac4372e563dc3eb6d4aa5690d6_img.jpg deleted file mode 100644 index 080fa2793c7d532a7887dff356f19af0be044c63..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8d9be1ac4372e563dc3eb6d4aa5690d6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8075f2df6849aaf8c54bdd0bf3d4198ee83245cbc4a77c10f4ef38361e2f7f50 -size 24657 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8e0160fd55391f6f2bbdef38ceb6f823_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/8fbe9e67b51710384633b6407d60420d_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9156549264d36ead617a1dec7987f970_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/91e400bc8bab58306b4d18432e94c9de_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/91e400bc8bab58306b4d18432e94c9de_img.jpg deleted file mode 100644 index e73db75298aee5deb21d944e6ccca4b95aaf7972..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/91e400bc8bab58306b4d18432e94c9de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:255d7e38df6c08535528c104e800d1ee2689fa40c4ec3001cb875d6356999a37 -size 24096 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/92c9263daf7fbd044894e2b273ae21af_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/92c9263daf7fbd044894e2b273ae21af_img.jpg deleted file mode 100644 index f55ea1b65cc4c9549769e8d90436a6eda653052d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/92c9263daf7fbd044894e2b273ae21af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8099dee59973acdf2cdb19c54cd96e7373419a4591a49a3821425c99afa57cd2 -size 19878 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/92eab1c7ce3162be3f7dabe7a3035249_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/970a901d8e537da4b6ff719d8931912f_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/97b3ed12d7f6c65cf3f7187326728409_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/97b3ed12d7f6c65cf3f7187326728409_img.jpg deleted file mode 100644 index 2301e69e370ce8c58355fa2afa4f4ee129996d4c..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/97b3ed12d7f6c65cf3f7187326728409_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4d7adea8c2701bea2479a0aeeaec178f34135f039c36c7d88a5ec55461e7bf2c -size 20581 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/98c911c074a0e29fafec169cbfa7248d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/98c911c074a0e29fafec169cbfa7248d_img.jpg deleted file mode 100644 index 26e8636604cf3acc7bafba1e923d9f03d2e1ec0f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/98c911c074a0e29fafec169cbfa7248d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e3b49e876f9609905bdc2141e8b4fcf39c6a1f02774b2424036923aea69f2001 -size 6556 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9a2aa33c5d905f8a0646278a48a2e565_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9a6ff2584005112f32fbd551cb6f0591_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9ba81901bf408ed950fce012b4890b1d_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9c34076a317aa1ad4225725b4b578f9f_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9c7046c19fb32a2d21ac26f5e90a7098_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9fc0c37f0024c76bce2fb5115a7f2c50_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9fc0c37f0024c76bce2fb5115a7f2c50_img.jpg deleted file mode 100644 index 4c73585e8747221db4334db5065c736f6368ff73..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/9fc0c37f0024c76bce2fb5115a7f2c50_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:abdeaea95145d345417b8f9f79d999befec975ff7ffe2c9edfa854abab7acd3e -size 19185 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a00c2ce2bca7f7c0d7a597c7e199db9a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a00c2ce2bca7f7c0d7a597c7e199db9a_img.jpg deleted file mode 100644 index 4b2e28aace3125f4a789f882559c3664557fc7f8..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a00c2ce2bca7f7c0d7a597c7e199db9a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d917d8dbe5aa542d2137802fdd7056c7cc04c27e6fd33f9cb7dea0a4104588d6 -size 21923 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg deleted file mode 100644 index 2dbbb06f540625d01b10dba2efcba445939655a6..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d2536d07e1a20733f58683e6b70f47a2693b64606a27312e3775a522004b0124 -size 24839 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a5404b7275b06497eecf9b5883604753_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a5404b7275b06497eecf9b5883604753_img.jpg deleted file mode 100644 index e9ad6f293b3d67f359b6fcac7636f1c37290682f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a5404b7275b06497eecf9b5883604753_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3596fe7fc9afd835ad3f21651a0ed6b131e0127a84e51ec65a307af4243754de -size 24401 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a548c5381cebd2650c5edb725b19f795_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a548c5381cebd2650c5edb725b19f795_img.jpg deleted file mode 100644 index c7a8b7994dd65266ecd190703b38979c67d1fe48..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a548c5381cebd2650c5edb725b19f795_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4b0e606e11300d263e24e72ba00bcc00d70185af5ffa3c42ddb05063b051aa96 -size 20321 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a69578b3473c27629eb691e06d9f04fc_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a69578b3473c27629eb691e06d9f04fc_img.jpg deleted file mode 100644 index 80b576a81696e4c5ec356694613d7aebf4179d28..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a69578b3473c27629eb691e06d9f04fc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bd321c8e384aaf4c4b43966550357aaf9cd2f01df7e0079b1b94dd23d2d87007 -size 19467 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a76a30cf23764f0b907220e7c3c70ce1_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a7fcb275d0eed586509a47f4f86a9725_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a82aef1d2f3f1a527328950e9db947ee_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a9bb99d15f54792e1c9a14b1e465369a_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a9bd36d25444d896e8d6941ff59d8f2d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a9bd36d25444d896e8d6941ff59d8f2d_img.jpg deleted file mode 100644 index e7dad4fb4f39a057f49299bf6654744ba1265e68..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a9bd36d25444d896e8d6941ff59d8f2d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:046f08f6c0b21b0599e7713c3268c1de62fea472ac2d7dfe08ae7ecf3dfd9cd3 -size 25372 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/a9f8bc87c084c4c84bae1128815c277c_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/aa22da43c463563d3d0035722bd79449_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/aa22da43c463563d3d0035722bd79449_img.jpg deleted file mode 100644 index b2126b7ea15031ae595a1fb3d34cf160d2ed974b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/aa22da43c463563d3d0035722bd79449_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f4e56cf7b67acc15a2cccd62807d6a0549d8c0ee6a63c4693a39f78926135b87 -size 27732 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/aa73c8651865e31f7a2f7b8a9c068461_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/aa73c8651865e31f7a2f7b8a9c068461_img.jpg deleted file mode 100644 index 252e8c33d3c157a5c32a2445486a657c7a387bc3..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/aa73c8651865e31f7a2f7b8a9c068461_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7b84b04ee43e17364ad3870e51aae4856a5822b824f307784a2d5bd2b26ee2c0 -size 20688 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/aa9441a5971655a79987d70fc551b26a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/aa9441a5971655a79987d70fc551b26a_img.jpg deleted file mode 100644 index 1845efe78ff36a0c6290755f084670e2de3af0c7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/aa9441a5971655a79987d70fc551b26a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:80bb2feff9911d586688efdfaeac31dc71f7afe66ad37973cf709c6cbdef9802 -size 30202 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/acfb2707966cd2618f2dc86b1a02702c_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/aef4390a4629604196222b9ed006a786_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/aef4390a4629604196222b9ed006a786_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/aef4390a4629604196222b9ed006a786_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/b02ba0b73e95416eb547976f6145b169_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/b02ba0b73e95416eb547976f6145b169_img.jpg deleted file mode 100644 index 9aef451976edc66be854a6416b0b56f93dd18e75..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/b02ba0b73e95416eb547976f6145b169_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:78fb26f339051c9bc84f1a44c08ef39f269257f55ade340cdd1be0b62c34541d -size 22206 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/b0e533f20bac2474664e1bebb7813606_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/b5d72de0273027513b3c617a66f6ab1b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/b5d72de0273027513b3c617a66f6ab1b_img.jpg deleted file mode 100644 index 03c975639c02bfddd2a075f919f5e840a2b6e772..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/b5d72de0273027513b3c617a66f6ab1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8a071c0fd244522fe35988808447174e1c0bf090b40fc054bc2784177ab3ce0 -size 29004 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/b9335fb94d07a154a00c3c63aaa36096_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/bb8abc0cc19db87acc1c3d7321599690_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/bd49a5a0bc3234abe21419ad830be088_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/bd49a5a0bc3234abe21419ad830be088_img.jpg deleted file mode 100644 index 1c64e79a7768afdfd1784937dcfcd6c2d0a6bda4..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/bd49a5a0bc3234abe21419ad830be088_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:68c432e9cc77241c2f376c1c27300cded0a56418f358d1c00bb9a500e1a6feec -size 16785 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg deleted file mode 100644 index 7b709785e7bde6ab0aefde9a9de8aa8821419443..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7fce5ec145d266c60c3b370530b3bedf9dceca212603e3c67667c5ad79226fb7 -size 4577 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/bdcc4eb452fcc6ba091949b77546a6d4_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/bdcc4eb452fcc6ba091949b77546a6d4_img.jpg deleted file mode 100644 index 5fe6c5f69e568505a1cfa11e040a91813f76bd72..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/bdcc4eb452fcc6ba091949b77546a6d4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2f8e54c8501c5ae8944403e6be207510d45dd2091006a26277655d9257c52953 -size 17149 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/be8d4d130f4e1f103926de61c4bfc23c_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 4b94da934e2c8c85c0123640346015b174f8dc14..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:53785b160680d7d75d469ea49f0daf5b5a3522fbee704e81dcd409934e1d112e -size 4601 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/c4315e81a5a818379fcf31519a9c2cbe_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg deleted file mode 100644 index 7b709785e7bde6ab0aefde9a9de8aa8821419443..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7fce5ec145d266c60c3b370530b3bedf9dceca212603e3c67667c5ad79226fb7 -size 4577 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/c964194b41a0636cf95ab198c9196bcd_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/cad89c017c9e7c1785bcd104fde4e737_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/cad89c017c9e7c1785bcd104fde4e737_img.jpg deleted file mode 100644 index be203ee917b84ebeb7943b054e8fde268c47b758..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/cad89c017c9e7c1785bcd104fde4e737_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:44ab968a36e2587778916e4b1639a70adbd2caf5ea2cac44b54cbfd3fe39d687 -size 9769 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/cb8f0521a69f168a06222045bea81a86_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/cc3d87694102054bcd694ae696bc41fa_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/cc3d87694102054bcd694ae696bc41fa_img.jpg deleted file mode 100644 index 1ccacd89e3fbedbc9f8eda702356b22be26a8602..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/cc3d87694102054bcd694ae696bc41fa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edcdb955ff056f927afb263a5860b4de12a8197c19b7d6dce549a69f3e361ff2 -size 68380 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ccb9a8830d90ffdcecfc4ef45ce72dbe_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ccb9a8830d90ffdcecfc4ef45ce72dbe_img.jpg deleted file mode 100644 index 9f27bc4d4d56fd32e0c1ad6a0d1480e33554cb44..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ccb9a8830d90ffdcecfc4ef45ce72dbe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:66cd80568b0f5740dcdc6709d483d137edbfa46c7cfbd501ffa31bfe70768f06 -size 26497 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/cdfbee2c06c086fdee6cb58317c947e0_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d04c50badc78d5ba47bf4e352af4a754_img.jpg deleted file mode 100644 index 63cd53f1e7cc4677bdec9ef0ea06924bdb40be88..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d04c50badc78d5ba47bf4e352af4a754_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:13fd56a394f45cf919dbff8bd3f8fb38b8769b09d3cf568f15e55f4e374537d4 -size 18499 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d0516b99882398c64c90f71c12e808e2_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg deleted file mode 100644 index b79021f63a07d313bf9daef30a94ac8aba2cb13d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b1e66687716ec63866ac48ef91a5e642f215e97bb0cd472fc0c3b6f9f22cfa9e -size 24555 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d1ec9820fe8d23d83e066389a9cd7338_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index d8f0264b92ff5f0b557c75de9f128fde3c488556..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:62aa973c54ec5a286ff3adfc660621d8e843d54798275206fa7405428feebace -size 4575 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d35a80e3faed208324083399568c7461_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d35a80e3faed208324083399568c7461_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d35a80e3faed208324083399568c7461_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d597715604d00e1ab3b00cc3f16e59de_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg deleted file mode 100644 index 906cfa3e335fa066178666798b1e682123ab5bbc..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7558e80b8b6753f3c8ac88b7a990fd41969120e17f577b323d99ed1d08ca3eb3 -size 19164 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d7c4779f679cb390727824a9896ecb5f_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d879e5f2c388bb87ee9614f63364dcf0_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d90d939bcbf43d474efaeeaa335a635c_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d90f17b29a73eddf151f51effa8912e0_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/d96da198567c411a05faab4ce5b4e58c_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/da8cb3d696f15f2c6de7aff6955d12d3_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/dbd230eafb5429741c22c2f7293118af_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/df495bddeb5d8826c7571714e6db1478_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e010d665d27407ff5e238d1c45c1c98f_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e06de71ced5f7c5e97414f01f39d550c_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e32e1bcf367a284cc7a4186056810d22_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e339d97a55f726bb82f15798d7eb80b7_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e374c531ea6c45899ce8ec331e437bd1_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e3b551138548092502c92a99ebfdb7bc_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e511e373339b5f948f239b19e0c37dd4_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e6eb959227f4726d42277c0f920bedbc_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e6fd4575ef3cf7eb94822dd1ff429503_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e8411aa566660d595a395a2f41d1f009_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e845d172f83764c1db7998397af2b9d5_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e845d172f83764c1db7998397af2b9d5_img.jpg deleted file mode 100644 index cb8cf412bc1a0916cf9ecd0c98ba7d5b77aab083..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e845d172f83764c1db7998397af2b9d5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:84483f98997c65c70092c683d4cf59b5969d440cc4b6351886d57aa13dd39f9c -size 27115 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e87df69ebd4cd2dbbf6749079e6c057a_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/e9d7df9758d9a042bb17daa9842760db_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg deleted file mode 100644 index cd15d3d6f918cc6066ba42ec8f0244ce6a9b6549..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6278d4614448b34b99fb5bad2e01af582cf4a1c21f527994324dae32ed6c0d06 -size 4571 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ef484b2179ee14c86e53e9f5b3c0d848_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f250ba4162fe40d8ddfd05b74fa48895_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f3d768b0299c4763bc703b606391c48b_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg deleted file mode 100644 index e7f965129e97c0e8ed564844a4749ca72d37b9c1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:22119772431751304192bd69f1f8c4a64733c3d63f41b1f9ff0edf054be27345 -size 4605 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f5d2a88925807080157c7cfb1d41cf0b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f5d2a88925807080157c7cfb1d41cf0b_img.jpg deleted file mode 100644 index 0fac3402441ee40372373f501b4b25416028a4fd..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f5d2a88925807080157c7cfb1d41cf0b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:736f70d16f2bfe7cfa0a3dce2cf05a39439c586be10f2d0f92b1af849979a9ed -size 21186 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f74adaa1840504407cd4272995426f82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f7dbd497160f02888f34fdf243648aa2_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f929e9fcf3f37d82af20f84f9c8b942a_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/f9b17af787dbdc9711539cd71df3d782_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/fac227c65a311c313325216dcf59591f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/fac227c65a311c313325216dcf59591f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/fac227c65a311c313325216dcf59591f_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/fbee1b51966e04afd72119133d952535_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/fbee1b51966e04afd72119133d952535_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/fbee1b51966e04afd72119133d952535_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 6d148e5c5aeadf9fa2a25a7ba6c7c8e3ebcf5cc5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:37fc40475798ddc0c3681dd541b84a426d3b11ea065ba8491c3a15abebad9e14 -size 4537 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ff748955b94dcb8337283fbe12baa475_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/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ff7977984f2552f326b2089d7595fff3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ff7977984f2552f326b2089d7595fff3_img.jpg deleted file mode 100644 index 9ae8e521aa9b65f24dcf52e4e75f207276d6346f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ff7977984f2552f326b2089d7595fff3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7bec1b7946b8903d530902b321ae532f7a99ad92a8a48a3a36f927dd35baadbf -size 33258 diff --git a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ffefa4f6eab4ce450aa5ecd3d3fd70bb_img.jpg b/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ffefa4f6eab4ce450aa5ecd3d3fd70bb_img.jpg deleted file mode 100644 index c55e194f1ed40dc09fdd7390026be3a18ec92873..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1AP-R005-v10.00/images/ffefa4f6eab4ce450aa5ecd3d3fd70bb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:acc1925f223ace3dbc6b3cf64179e52d5fe8a27a4cdb46e75f9bd85ff2f44439 -size 22211 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/doc.md b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/doc.md deleted file mode 100644 index aa941bfbc98d0b21bf029a3cbe7695eaf18e114f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/doc.md +++ /dev/null @@ -1,1126 +0,0 @@ - - -# --- **R1 interface: General Aspects and Principles** - -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 | -| 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..... | 6 | -| 4 General Aspects of R1 Interface and R1 Services ..... | 7 | -| 4.1 Introduction..... | 7 | -| 4.2 General principles..... | 7 | -| 4.3 Specification objectives ..... | 7 | -| 4.4 Capabilities ..... | 7 | -| 5 R1 Services..... | 8 | -| 5.1 Service management and exposure services ..... | 8 | -| 5.1.1 General ..... | 8 | -| 5.1.2 Bootstrap service ..... | 8 | -| 5.1.3 Service registration service ..... | 9 | -| 5.1.4 Service discovery service ..... | 9 | -| 5.1.5 Void..... | 10 | -| 5.1.6 Authentication and authorization ..... | 10 | -| 5.1.7 Void..... | 11 | -| 5.2 Data management and exposure services..... | 11 | -| 5.2.1 General ..... | 11 | -| 5.2.2 Data registration service..... | 12 | -| 5.2.3 Data discovery service ..... | 13 | -| 5.2.4 Data request service ..... | 14 | -| 5.2.5 Data subscription service ..... | 14 | -| 5.2.6 Data delivery services ..... | 15 | -| 5.2.7 Data offer service ..... | 16 | -| 5.3 A1-related Services..... | 17 | -| 5.3.1 General ..... | 17 | -| 5.3.2 A1 policy management services..... | 17 | -| 5.3.3 A1 enrichment information related services..... | 19 | -| 5.3.4 A1 ML model management services..... | 19 | -| 5.4 RAN OAM-related Services ..... | 19 | -| 5.4.1 General ..... | 19 | -| 5.4.2 Network Information service..... | 20 | -| 5.4.3 Fault management (FM) service..... | 20 | -| 5.4.4 Performance management (PM) service ..... | 20 | -| 5.4.5 Configuration management (CM) service ..... | 21 | -| 5.5 O2-related Services..... | 22 | -| 5.5.1 General ..... | 22 | -| 5.5.2 O2 Infrastructure management service..... | 22 | -| 5.5.3 O2 Deployment management service..... | 23 | -| 5.6 AI/ML Workflow Services ..... | 23 | -| 5.6.1 General ..... | 23 | -| 5.6.2 AI/ML model registration service ..... | 24 | -| 5.6.3 AI/ML model storage service..... | 25 | - -| | | | -|--------|-------------------------------------------------------------------|----| -| 5.6.4 | AI/ML model discovery services ..... | 26 | -| 5.6.5 | AI/ML model change subscription service..... | 26 | -| 5.6.6 | AI/ML model training capability registration service ..... | 26 | -| 5.6.7 | AI/ML Model deployment request service..... | 27 | -| 5.6.8 | AI/ML model training services ..... | 27 | -| 5.6.9 | AI/ML model performance monitoring service..... | 28 | -| 5.6.10 | AI/ML model inference service ..... | 28 | -| 5.6.11 | AI/ML model training capability query services..... | 29 | -| 5.7 | rApp management Services ..... | 29 | -| 5.7.1 | General ..... | 29 | -| 5.7.2 | rApp registration service ..... | 29 | -| 6 | R1 Interface Protocol Structure..... | 30 | -| | Annex (informative):Change history/Change request (history) ..... | 31 | - -# --- Foreword - -This Technical Specification (TS) has been produced by WG2 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 general aspects and principles of the R1 interface. It is part of a TS-family covering the R1 interface specifications. - -# --- 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.WG2.TS.A1AP: "A1 Interface: Application Protocol" ("A1AP"). -- [2] O-RAN.WG2.TS.Use-Case-Requirements: "Non-RT RIC & A1/R1 Interface: Use Cases and Requirements" ("UCR"). -- [3] O-RAN.WG2.TS.Non-RT-RIC-ARCH: "Non-RT RIC: Architecture". -- [4] O-RAN.WG11.TS.SecProtSpec.0: "Security Protocols Specifications" ("SPS"). -- [5] O-RAN.WG2.TS.R1TP: "Transport protocols for R1 Services" ("R1TP"). -- [6] O-RAN.WG6.TS.O2IMS: "O2IMS-Interface Specifications" ("O2IMS"). -- [7] O-RAN.WG6.TS.O2DMS : "O2dms Interface Specification: Profile based on ETSI NFV Protocol and Data Models" ("O2DMS"). -- [8] O-RAN.WG6.TS.O2-GA&P: "O2 Interface General Aspects and Principles" ("O2GAP"). -- [9] O-RAN.WG11.TS.SRCS.0: "Security Requirements and Controls Specification" ("SRS"). -- [10] O-RAN.WG10.TS.OAM-Architecture: "Operations and Maintenance Architecture" ("OAM 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". - -# 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the following terms apply: - -**AI/ML model:** An algorithm that applies AI/ML techniques to produce model output data based on model input data. - -**AI/ML model training:** A process to train an AI/ML model by learning the input/output relationship in a data driven manner and obtain a trained AI/ML model that can be used for inference. - -**Data job:** An entity that provides data related to a DME type. - -**Data instance:** The set of data which resulted from a data job. - -**DME type:** Data type managed and exposed by the DME services and identified by a DME type identifier. - -**Non-RT RIC:** O-RAN non-real-time RAN Intelligent Controller: a logical function in the SMO framework 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. The Non-RT RIC is comprised of the Non-RT RIC framework and Non-RT RIC applications (rApps). - -**Non-RT RIC framework:** Functionality internal to the SMO framework that logically terminates the A1 interface and provides the R1 services to rApps through the R1 interface. - -**rApp:** Non-RT RIC application: an application designed to consume and/or produce R1 Services. - -**NOTE:** rApps can leverage the functionality provided by the SMO/Non-RT RIC framework to deliver value added services related to intelligent RAN optimization and operation. - -**R1:** A service based interface between rApps and R1 termination in the Non-RT RIC framework via which R1 Services can be produced and consumed. - -**R1 Services:** A collection of services including, but not limited to, service registration and discovery services, authentication and authorization services, AI/ML workflow services, RAN OAM-related services as well as A1 and O2 related services. - -**rApp instance:** An individual occurrence of a Non-RT RIC application running in the Non-RT RIC runtime environment. - -**rApp instance identifier:** A unique identifier for each rApp instance, assigned by the SMO/Non-RT RIC framework during rApp registration. - -## 3.2 Symbols - -Void - -## 3.3 Abbreviations - -For the purposes of the present document, the following abbreviations apply. - -| | | -|------|-----------------------------| -| AI | Artificial Intelligence | -| EI | Enrichment Information | -| FQDN | Fully Qualified Domain Name | -| FM | Fault Management | -| ML | Machine Learning | -| PM | Performance Management | -| RAN | Radio Access Network | - -| | | -|--------|--------------------------------------| -| RBAC | Role Based Access Control | -| RIC | RAN Intelligent Controller | -| RT | Real-time | -| rAppId | rApp Instance Identifier | -| SMO | Service Management and Orchestration | -| TBAC | Target Based Access Control | - -# --- 4 General Aspects of R1 Interface and R1 Services - -## 4.1 Introduction - -The following clauses cover the general aspects for R1 interface. - -## 4.2 General principles - -The general principles for the specification of the R1 interface are as follows: - -- The R1 interface is an open logical interface within the O-RAN architecture between the rApps and the Non-RT RIC framework. -- The R1 interface supports the exchange of control signalling information and the collection and delivery of data between endpoints. -- The R1 interface enables multi-vendor rApps to consume or produce the R1 services and is independent of specific implementations of the SMO and Non-RT RIC framework. -- The R1 interface is defined in an extensible way that enables new services and data types to be added without needing to change the protocols or the procedures. - -## 4.3 Specification objectives - -The R1 interface specifications shall: - -- Facilitate inter-connection between rApps and Non-RT RIC framework supplied by different vendors. -- Provide a level of abstraction between rApps and SMO/Non-RT RIC framework that can be the consumers and or producers of R1 services. - -## 4.4 Capabilities - -As described in UCR [2], the R1 interface shall support: - -- Registration and Deregistration of R1 services, -- Authentication of rApps, -- Authorization of requests to access R1 services, -- Facilitation of service discovery and service notifications for the registered R1 Services, -- Registration and Deregistration of DME types, -- Subscription and Unsubscription for registered DME types and collection and delivery of data for subscribed DME types, -- Functionalities related to A1 and O2 interfaces, RAN OAM and AI/ML workflow. - -# 5 R1 Services - -## 5.1 Service management and exposure services - -### 5.1.1 General - -As described in the Non-RT RIC Architecture specification [3], the Service management and exposure services provided by the SMO/Non-RT RIC framework enable: - -- Registration of services, -- Discovery of services, -- Authentication and authorization, -- Communication support, -- Bootstrap (optional), - -Additionally, if the Bootstrap service is provided by the SMO/Non-RT RIC framework, an rApp can use it to discover the endpoints of the Service management and exposure services. - -The Service management and exposure services handle R1 services that are produced and/or consumed by rApps, as well as R1 services that are produced by functions in the SMO/Non-RT RIC framework and consumed by rApps. Additionally, the information related to the registered services is stored and the status of the service registrations is kept updated. - -The Service management and exposure services also handle the authorization of Service Consumers. When an R1 service is registered, it is available for discovery and invocation, by authorized Service Consumers. - -In the following, the term "Service Producer" refers to the role of an rApp to register and produce a service, and the term "Service Consumer" refers to the role of an rApp to discover and consume a service, using the Service management and exposure service. The term "Service management and exposure services Producer" refers to the logical R1 Service management and exposure functions in the SMO/Non-RT RIC framework acting as Service Producers of one or more of the Service management and exposure services. - -**NOTE:** An rApp can discover services produced by other functions than rApps via the R1 interface, while services registered by rApps cannot be discovered by other functions than rApps via the R1 interface. The R1 interface only specifies how rApp interacts using the Service management and exposure services in the roles of Service Producer and Service Consumer. - -### 5.1.2 Bootstrap service - -#### 5.1.2.1 Overview - -If the Bootstrap service is provided by the SMO/Non-RT RIC framework, an rApp can use it to discover the endpoints of the Service management and exposure services. - -#### 5.1.2.2 Bootstrap - -The endpoint on which the Bootstrap service can be reached shall be version independent. It can be provisioned to the rApp or can be obtained e.g. from a fixed well-known address or FQDN. - -The following procedure is defined: - -**Discover bootstrap:** This procedure enables determination of the endpoints of the other Service management and exposure services. - -### 5.1.3 Service registration service - -#### 5.1.3.1 Overview - -This service allows Service Producers to register information about the R1 services they produce. - -#### 5.1.3.2 Registration of services - -Register service is a procedure where a Service Producer declares its produced services to the Service management and exposure services Producer. Upon successful registration of a service, the information about the services is stored. Deregister service is a procedure where a Service Producer declares which services are no longer provided. The Service Producer can also update the registered information related to a service. - -When registering a service, the Service Producer provides the information about the service, and may provide information on, but not limited to, the following: - -- profile of the service, -- information on how to access the service, -- information on the API, -- limitations/capabilities of the Service Producer. - -The following procedures are defined: - -**Register service:** A Service Producer uses this procedure to register an R1 service that it produces with the capabilities that are being exposed. On receiving the request, the Service management and exposure services Producer determines whether the Service Producer is authorized to produce the service, and whether there are any conflicts. In the response, the Service management and exposure services Producer informs the Service Producer on the capabilities that they are allowed to expose. - -**Deregister service:** A Service Producer can use this procedure to deregister an R1 service that it is registered to provide. - -**Update service registration:** A Service Producer can use this procedure to update the registration of an R1 service that it provides. - -**Partially update service registration:** A Service Producer can use this procedure to Partially update the registration of an R1 service that it provides. - -**Query registered services:** A Service Producer can use this procedure to retrieve information about the registered services. - -### 5.1.4 Service discovery service - -#### 5.1.4.1 Overview - -This service allows Service Consumers to discover R1 services they intend to consume. - -#### 5.1.4.2 Discovery of services - -For service discovery, a set of procedures enables a Service Consumer to retrieve information on available services based on selection criteria. - -**NOTE:** Available services either have been registered by service-producing rApps using the Service registration service (in case these are produced by rApps) or have been made known to the Service discovery service Producer by other means (in case they are produced by Service Producers inside the SMO/Non-RT RIC framework). - -Upon receiving the request to discover services, the Service management and exposure services Producer verifies the identity of the Service Consumer (see clause 5.1.6). The Service management and exposure services Producer retrieves the stored service information, applies the authorization policy, and performs filtering of service information based on the selection criteria provided in the request. - -The following procedures are defined: - -**Discover services:** A Service Consumer uses this procedure to discover registered services. The Service Consumer can provide selection criteria to inquire about the registered services. The response contains a filtered list of available services based on which services the consumer is authorized to access. - -**Subscribe service availability:** A Service Consumer can subscribe to notifications regarding changes in service(s) that are available and thereby receive a notification when a service has been registered, updated, or deregistered by a Service Producer. The subscription is created for the Service Consumer based on the services and capabilities that it is authorized to access, i.e., the Service Consumer only gets notified about changes in registration status of services that it is authorized to access. Upon subscription, the Service Consumer can pass selection criteria in order to control the set of services about which it wishes to be notified. - -**Update service availability subscription:** A Service Consumer can update each of its own subscriptions for notifications regarding changes in the available services. - -**Unsubscribe service availability:** A Service Consumer can unsubscribe from notifications regarding changes in the available services. - -**Notify service availability changes:** The Service management and exposure services Producer can use this procedure to notify a subscribed Service Consumer about changes in the set of registered services that the Service Consumer is authorized to access. - -### 5.1.5 Void - -### 5.1.6 Authentication and authorization - -#### 5.1.6.1 Overview - -Authentication and authorization are realized as a combination of procedures and services that allow asserting the identity of Service Producers and Service Consumers and ensure that only authorized consumers can access the R1 services. - -#### 5.1.6.2 Authentication - -Authentication will be performed to authenticate the Service Consumers and Service Producers to allow them to provide or access R1 Services. Service Consumers and Service Producers can initiate secure communication for R1 services after the authentication information is validated. - -Authentication procedures shall comply to the requirements specified in SRS [9], clause 5.2.6. - -#### 5.1.6.3 Authorization - -Authorization procedures are used to grant Service Consumers access to registered R1 services and to allow Service Producers to produce R1 services. - -Authorization can be based on a mechanism to enforce authorization by policies, where exposed R1 services are further subject to authorization policies before granting access to registered services. Authorization policies refer to the attributes that are associated to the Service Consumer. For example, authorization policy can be RBAC or TBAC and the additional details are supplied in the policy attributes. - -Authorization procedures shall comply to the requirements specified in SRS [9], clause 5.2.6. - -The following procedures are defined: - -**Access token request:** A Service Consumer can use the Access token request procedure to request access to the services as specified in SPS [4], clause 4.7.3.2. A token is granted for subsequent use of the requested R1 services that require authorization as specified in SPS [4], clause 4.7.3.3. - -**Revoke access:** A Service Consumer with appropriate privileges (administrator) can use the Revoke access procedure to revoke the access to exposed R1 services. - -NOTE: The details of the Revoke access procedure are not defined in this version of the specification. - -### 5.1.7 Void - -## 5.2 Data management and exposure services - -### 5.2.1 General - -As described in the Non-RT RIC Architecture specification [3], the Data management and exposure services enable: - -- Registration of DME types, -- Discovery of DME types, -- Request for data, -- Subscription to data, -- Collection of data from Data Producers and consumption of data by Data Consumers, -- Access to optional data processing in the SMO/Non-RT RIC framework. - -The Data management and exposure services use DME types as descriptions of certain types of data that are available. A DME type is defined by a DME type identifier and the syntax of the DME type is given by an associated schema. A DME type is defined by one schema while a schema may be associated with one or multiple DME types. - -A Data Producer registers its production capabilities related to a DME type. The production capabilities information includes DME type information and producer constraints. When one or more production capabilities related to a DME type have been registered, it is available for discovery, and request for / subscription to data, by authorized Data Consumers. A Data Consumer uses the discovered information about the DME type for requesting or subscribing to data instances. Further, the data instances for a DME type may be stored, or the actual data production may be triggered by the SMO/Non-RT RIC framework on the need for data collection, including based on a request for data by a Data Consumer or a data offer from a Data Producer. - -Data Consumer refers to an rApp that can consume data for a DME type and Data Producer refers to an rApp that can produce data for a DME type. - -Based on DME type information, to trigger data collection or data consumption, data instances can be requested or subscribed to. While a data request causes the delivery of a data instance as a one-time response, a data subscription potentially causes multiple data delivery actions. Data consumption refers to a Data Consumer requesting for or subscribing to a data instance. Data collection refers to the SMO/Non-RT RIC framework requesting for or subscribing to a data instance. - -When initiating a data request or data subscription, the data instance to obtain is defined by the DME type information and by additional characteristics as listed below. - -NOTE: DME type information can be made available to Data Consumers using the Discover DME types procedure (see clause 5.2.3.2) or from configuration. DME type information can be made available by Data Producers to the Data management and exposure functions using the Register DME types procedure (see clause 5.2.2.2). - -This information that defines a data instance may contain, but is not limited to, the following parameters: - -- DME type identifier, -- time interval for the data instance (start and end of the interval during which the data have been or will be collected), -- granularity of collection (how often data are to be collected), -- periodicity of delivery (how often data are to be delivered), -- scope (i.e., filter on the data), -- target (i.e., filter on the managed objects that the data is associated with). - -The collection of data from the Data Producers can for instance be started based on a trigger from a Data Consumer that requests/subscribes to specified data that needs to be generated and collected, at the discretion of functions in the SMO/Non-RT RIC framework or based on a data offer from a Data Producer. If an additional Data Consumer request for / subscribes to a data instance of a certain DME type and scope that is already being collected by the Data Management and Exposure functions, no additional data collection will be started with the Data Producer if the collected data meets the criteria of additional request. Once the data production is initiated, Data Consumer can query the status of production of data instances, or the Data Consumer can be notified if there are any changes in data production as part of subscribe data. - -Data management and exposure services include services that are produced by the Data management and exposure functions, as well as services to be produced by the Data Producers or Data Consumers and consumed by the Data management and exposure functions. - -NOTE: In the Non-RT RIC Architecture specification [3], it is described that the Data management and exposure services can enable an rApp to discover and consume DME types produced by functions other than rApps, and that DME types produced by rApps can be consumed by functions other than rApps. The R1 interface only specifies how rApps interact with the Data management and exposure service in the roles of Data Producer and Data Consumer. - -### 5.2.2 Data registration service - -#### 5.2.2.1 Overview - -Data Producers consume this service to register DME types. The Data management and exposure functions in the SMO/Non-RT RIC framework produce this service. - -#### 5.2.2.2 Registration of DME types - -Register DME type is a procedure where a Data Producer registers its production capabilities related to a DME type. Query DME type registration is a procedure where a Data Producer queries its production capabilities related to a DME type that it has previously registered. Update DME type registration is a procedure where a Data Producer updates its production capabilities related to a DME type that it has previously registered with the Data registration and discovery service Producer. Deregister DME type is a procedure where a Data Producer deregister its production capabilities related to a DME type. - -As part of the Register DME type procedure, the Data Producer provides the data type identifier and further information about its production capabilities related to the DME type, such as if it is stored e.g., in an object store or can be continuously produced and delivered and may provide information on, including but not limited to, the following: - -- DME type information which includes: - - information on how to deliver the data, e.g., via push, pull or streaming, - - periodicity of the data, in case it is generated periodically, - - information on the data syntax (schema), - -- the supported data delivery methods (i.e., push and pull) by the Data Producer, -- Producer constraints of the Data Producer to filter the data (e.g., to provide only certain types of events if requested so by the Data Consumers), -- information whether the Data Producer supports data request or data subscription or both. - -The Query data subscription information is a procedure where a Data Producer can retrieve the data subscription information for a DME type that has previously registered. - -The following procedures are defined: - -**Register DME type:** A Data Producer uses this procedure to register its production capabilities related to a DME type. On receiving the request, the Data registration service Producer determines whether the Data Producer is authorized to produce the DME type. In the response, the Data registration service Producer informs the Data Producer if it is allowed to produce the DME type. - -**Query DME type registration:** A Data Producer uses this procedure to retrieve information about a its registration of production capabilities related to a DME type that it has previously registered. - -**Update DME type registration:** A Data Producer uses this procedure to update its registration of production capabilities related to a DME type that it has previously registered. - -**Deregister DME type:** A Data Producer can use this procedure to deregister its production capabilities related to a DME type that it has previously registered for which it is no longer able to produce data instances. - -**Query data subscription information:** A Data Producer can use this procedure to retrieve the data subscription information for a DME type it has previously registered. - -### 5.2.3 Data discovery service - -#### 5.2.3.1 Overview - -Data Consumers consume this service to discover available DME types. The Data management and exposure functions in the SMO/Non-RT RIC framework produce this service. - -#### 5.2.3.2 Discovery of DME types - -This set of procedures enables a Data Consumer to retrieve information on the registered DME types. - -Discovery of a DME type does not imply availability of data instances of that DME type. It is just an indication that Data Consumers can request or subscribe to data for that DME type. It can happen that the actual data production is only triggered by the request or subscription actions of the Data Consumers. - -The following procedures are defined: - -**Discover DME types:** A Data Consumer can discover the DME types that are available. For each DME type, a DME type identifier and additional metadata are provided. - -**Query DME type information:** A Data Consumer can retrieve information on a specific DME type identified by a DME type identifier. Such information enables the Data Consumer to formulate a request or subscription for data instances of that DME type. - -**Subscribe DME types changes:** A Data Consumer can subscribe to notifications regarding changes in the set of available DME types and thereby receive notifications when DME types have been registered or deregistered. The subscription is created for the Data Consumer based on the DME types that it is authorized to access, i.e., the Data Consumer can only subscribe to get notified about changes in availability status of DME types that it is authorized to access. - -**Unsubscribe DME types changes:** A Data Consumer can unsubscribe from notifications regarding changes in the set of available DME types. - -**Notify DME types changes:** The Data registration and discovery service Producer uses this procedure to notify a subscribed Data Consumer about changes in the set of available DME types. - -### 5.2.4 Data request service - -#### 5.2.4.1 Overview - -For data consumption, Data Consumers consume this service to request data instances, and the Data management and exposure functions in the SMO/Non-RT RIC framework produce this service. - -For data collection, the Data management and exposure functions in the SMO/Non-RT RIC framework consume this service to request data instances, and Data Producers produce this service. - -#### 5.2.4.2 Requesting data. - -This set of procedures allows a Data request service Consumer to specify a data instance (for a registered DME type) to be delivered to it. The data instance is defined by information specified in clause 5.2.1 - -Data request is a one-time request and is performed via Request data procedure. - -A data request can be stopped using the Cancel data request procedure. Data request service Consumer can query the status of the production of the data. - -The following procedures are defined: - -**Request data:** The Service Consumer provides, to the Data request service Producer, information on the data it requests based on the DME type information. - -**Cancel data request:** The Service Consumer cancels a data request. - -**Query data request status:** The Service Consumer queries the status of production of the data. - -### 5.2.5 Data subscription service - -#### 5.2.5.1 Overview - -For data consumption, Data Consumers consume this service to subscribe to data instances, and the Data management and exposure functions in the SMO/Non-RT RIC framework produce this service. - -For data collection, the Data management and exposure functions in the SMO/Non-RT RIC framework consume this service to subscribe to data instances, and Data Producers produce this service. - -#### 5.2.5.2 Subscribing to data. - -This set of procedures allows a Data subscription service Consumer to specify a data instance (for a registered DME type) to be delivered to it, and to choose the delivery service to use (e.g., push or pull). The data instance is defined by information specified in clause 5.2.1. - -Subscribe data is a procedure that initiates the delivery of a data instance in potentially multiple chunks of data. A data subscription can be stopped using the Unsubscribe data procedure. A data subscription can be updated using Update data subscription procedure and a data subscription can be queried using Query data subscription. - -The following procedures are defined: - -**Subscribe data:** The Service Consumer provides, to the Data subscription service Producer, information on the data it wants to subscribe to be based on the DME type information retrieved using the Discover DME types procedure. - -**Notify data availability:** The Service Consumer is provided information on the availability and retrieval scheme of the subscribed data instance. As a precondition, the Service Consumer must have used the Subscribe data procedure to create a subscription. - -**Update data subscription:** The Service Consumer updates a data subscription. - -**Query data subscription:** The Service Consumer queries a data subscription. - -**Unsubscribe data:** The Service Consumer cancels a data subscription. - -**Query data subscription status:** The Service Consumer uses this procedure to query the status of data subscription by providing the data job identifier. - -**Notify change of data subscription status:** The Service Consumer is provided information on the changes in the status of the data subscription. Data production is handled as part of data subscription and whenever there are changes in the data production it will be notified as part of the data subscription status change. - -The procedures for delivery of data instances are described in clause 5.2.6. - -### 5.2.6 Data delivery services - -#### 5.2.6.1 Overview - -Data delivery is handled through a set of services as defined below which deliver data as requested using the Request data procedure (see clause 5.2.4.2) or the Subscribe data procedure (see clause 5.2.5.2) or indicated using the Create data offer procedure (see clause 5.2.6). - -Data delivery messages relate to a particular data request, data subscription or data offer. The data can be delivered in different ways, e.g.: from a REST endpoint, via a message bus or from an object store location. - -The means where and how the data can be retrieved can be made known to the recipient of the data by different means as part of the Request data, Subscribe data, Notify data availability, or Create data offer procedure. - -NOTE: Additional procedures for data delivery can be added in later releases. - -#### 5.2.6.2 Pull data service. - -The pull data service allows the Service Consumer to obtain data via a pull mechanism from the Service Producer. Retrieval of data can occur once or multiple times (polling). - -For data consumption, Data Consumers consume this service and the Data management and exposure functions in the SMO/Non-RT RIC framework produce this service. - -For data collection, the Data management and exposure functions in the SMO/Non-RT RIC framework consume this service and Data Producers produce this service. - -The following procedure is defined: - -**Retrieve data:** The Service Consumer retrieves, from the Service Producer, data instances about whose existence the Service Consumer has been informed as part of the Request data, Notify data availability, or Create data offer procedure, using a pull communication mechanism. - -#### 5.2.6.3 Push data service - -The push data service allows the Service Consumer to push data to the Service Producer, - -For data consumption, the Data management and exposure functions in the SMO/Non-RT RIC framework consume this service and Data Consumers produce this service. - -For data collection, Data Producers consume this service and the Data management and exposure functions in the SMO/Non-RT RIC framework produces this service. - -The following procedure is defined: - -**Push data:** The Service Consumer provides, to the Service Producer a data instance using a push communication mechanism as arranged as part of the Request data, Subscribe data, or Create data offer procedure. - -#### 5.2.6.4 Point to multipoint data streaming service - -This service allows each Data Producer to deliver data to multiple Data Consumers using a message bus. It can be used as a delivery mechanism for data subscription or data offer. - -For data subscription, the Data management and exposure functions in the SMO/Non-RT RIC framework inform the Data Producer which data stream to use to send data. Further, they inform the Data Consumer which data stream to use to fetch data. - -For data offer, the Data management and exposure functions in the SMO/Non-RT RIC framework inform the Data Producer which data stream to use to send data. - -The following procedures are defined: - -**Send data to data stream:** The Data Producer sends data to a stream that is distributed by the message bus. - -**Fetch data from data stream:** The Data Consumer fetches data from a stream that is distributed by the message bus. - -### 5.2.7 Data offer service - -#### 5.2.7.1 Overview - -Data Producers consume this service to request producing data to the Data offer service Producer for immediate collection and storage. The Data management and exposure functions in the SMO/Non-RT RIC framework produce this service. - -#### 5.2.7.2 Managing a data offer. - -This service allows a Data Producer to declare to the Data offer service Producer that it intends to produce data instances for immediate collection and storage by the latter. Prior to creating a data offer, the Data Producer has registered the related DME type. - -The Data Producer provides information on the data that it intends to provide based on the DME type information it has provided during data registration (see clause 5.2.2.2) and specifies additional characteristics of the data instance it intends to provide, similar to the information passed in the data request or data subscription (see clause 5.2.4.2 and 5.2.5.2). - -The Data Producer can further indicate that it no longer intends to produce data for a data offer by deleting the offer. - -The Data offer service Producer can indicate to the Data Producer that it does no longer wishes to receive data related to the offer by sending a data offer termination notification to the Data Producer, subsequently stopping collecting data related to the offer and terminating the offer. - -The following procedures are defined: - -**Create data offer:** A Data Producer provides, to the Data offer service Producer, information on the data it intends to deliver based on the DME type information passed during the Register DME type procedure. In case the push data service is intended to be used for data delivery, the Data offer service Producer provides to the Service Consumer information regarding the endpoint on which to receive the pushed data. In case the pull data service is intended to be used for data delivery, the Data offer service Producer provides to the Service Consumer information regarding the endpoint on which to receive the data availability notifications. - -**Terminate data offer:** A Data Producer terminates a data offer it has created. - -**Notify data offer termination:** The Data offer service Producer provides, to the Data Producer, a notification that it intends to stop collecting data from the data offer and terminating the offer. Following the reception of such notification, the Data Producer shall not deliver further data related to the data offer. The procedures for the delivery of data instances are described in clause 5.2.6. - -## 5.3 A1-related Services - -### 5.3.1 General - -As described in the Non-RT RIC Architecture specification [3], the A1-related services produced by the SMO/Non-RT RIC framework enable the following functionalities related to the management of A1 policies and A1 enrichment information: - -- Creation, modification, deletion, and query of A1 policies, -- Discovery of supported A1 policy types, -- Querying the status of A1 policies, -- Subscribe to event notifications related to A1 policies, -- Registration and deregistration of EI types. - -### 5.3.2 A1 policy management services - -#### 5.3.2.1 Overview - -The A1 Policy management service is an R1 service that enables an rApp (the consumer of that service) to - -- discover available A1 policy types and subscribe to notifications on added or removed A1 policy types, -- query for details of A1 policy types and details of A1 policy and enforcement status, -- create, update, and delete an A1 policy, -- subscribe to A1 policy enforcement status changes. - -The term "A1 policy management service Producer" refers to the A1-related functions in the SMO/Non-RT RIC framework acting as Service Producer of the A1 policy management service. The term "A1 policy management service Consumer" refers to an rApp acting as Service Consumer of the A1 policy management service. - -NOTE 1: Another name for this service that does not depend on southbound interface naming is not defined in the present document. - -NOTE 2: The terms A1 policy type, A1 policy type identifier, A1 policy and A1 policy identifier refer to definitions made for the A1-P service over the A1 interface, see A1AP [1], and are used unchanged in the procedures of the A1 policy management service over the R1 interface. - -#### 5.3.2.2 A1 Policy management - -The following procedures are defined: - -**Query A1 policy type identifiers:** An A1 policy management service Consumer can use this procedure to query for the available A1 policy types. The A1 policy management service Producer will respond with the list of identifiers for all the available A1 policy types. - -**Subscribe to policy type availability changes:** An A1 policy management service Consumer can use this procedure to subscribe to notifications on policy type availability changes, i.e., when an A1 policy type becomes available or when an A1 policy type becomes unavailable. - -**Query A1 policy type:** An A1 policy management service Consumer can use this procedure to query the details of an A1 policy type by providing the A1 policy type identifier. The A1 policy management service Producer will respond with information about the A1 policy type. - -**Query A1 policy identifiers:** An A1 policy management service Consumer can use this procedure to query for the A1 policies, or a subset of the A1 policies by providing query parameters such as A1 policy type identifier or Near-RT RIC identifier. The A1 policy management service Producer will return the list of A1 policy identifiers that matches with the query criteria. - -**Query A1 policy:** An A1 policy management service Consumer can use this procedure to query for the details of an A1 policy by providing the A1 policy identifier. The A1 policy management service Producer will respond with information about the A1 policy. - -**Create A1 policy:** An A1 policy management service Consumer can use this procedure to create an A1 policy by providing the below parameters: - -- Information about the A1 policy, -- A1 policy type identifier, -- Near-RT RIC identifier. - -On receiving the request, the A1 policy management service Producer determines whether the A1 policy type is supported by the Near-RT RIC, assigns an A1 policy identifier for the new A1 policy, and informs the A1 policy management service Consumer on the outcome of the A1 policy creation. - -**Update A1 Policy:** An A1 policy management service Consumer can use this procedure to update an A1 policy by providing the below parameters: - -- information about the A1 policy, -- A1 policy identifier. - -On receiving the request, the A1 policy management service Producer determines whether the A1 policy is available in the Near-RT RIC and informs the A1 policy management service Consumer on the outcome of the A1 policy update. - -**Query A1 policy status:** An A1 policy management service Consumer can use this procedure to query the enforcement status of a single A1 policy by providing the A1 policy identifier. The A1 policy management service Producer will respond with the enforcement status of the A1 policy. - -**Subscribe A1 policy status:** An A1 policy management service Consumer can use this procedure to subscribe to status changes of A1 policies by providing either a list of A1 policies or a list of Near-RT RIC identifiers or a list of policy type identifiers. i.e., when A1 policies status becomes enforced or not enforced. - -**Query A1 policy status subscription:** An A1 policy management service Consumer can use this procedure to query an A1 policy status subscription. - -**Update A1 policy status subscription:** An A1 policy management service Consumer can use this procedure to update an A1 policy status subscription. - -**Unsubscribe A1 policy status:** An A1 policy management service Consumer can use this procedure to unsubscribe from status changes of A1 policies. - -**Notify A1 policy status changes:** An A1 policy management service Consumer is provided information on the status change of an A1 policy (i.e., when status changes from enforced or not enforced). - -**Delete A1 policy:** An A1 policy management service Consumer can use this procedure to delete an existing A1 policy. The A1 policy management service Producer will respond with the outcome of the A1 policy deletion. - -NOTE: In the responses of the above procedures, the A1 policy management service Producer can either use stored information that has already been received via the A1 interface (e.g., information on available A1 policy types), or information directly resulting from an A1 procedure performed due to the R1 procedure (e.g., creation of an A1 policy). - -### 5.3.3 A1 enrichment information related services - -#### 5.3.3.1 Overview - -A1 enrichment information related services enable rApp to register and unregister of EI types of which data it can produce as the source for the EI job results delivered over the A1 interface. - -#### 5.3.3.2 A1 enrichment information - -The following procedures are defined: - -**Register EI type:** An rApp uses this procedure to register an EI type that it can produce as the source for the EI job results delivered over the A1 interface to the A1 enrichment information functions. In the registration request, the rApp includes the EI source data type registered in the DME functions. On receiving the request, the A1 enrichment information functions can subscribe EI source data from DME functions using the EI source data type. In the response, the A1 enrichment information functions inform the rApp on the EI type capabilities that it is registered to provide. - -**Deregister EI type:** An rApp can use this procedure to unregister EI types that it has previously registered, but that it is no longer able to produce. - -### 5.3.4 A1 ML model management services - -#### 5.3.4.1 Overview - -The availability of AI/ML model training capabilities over A1 is indicated in the AI/ML model training capability registration as specified in Clause 5.6.6 . - -## 5.4 RAN OAM-related Services - -### 5.4.1 General - -As described in the Non-RT RIC Architecture specification [3], the RAN OAM-related services produced by the SMO/Non-RT RIC framework provide access to OAM functionality that enables the Service Consumer: - -- To obtain information about alarms. -- To change their acknowledgment status. -- To obtain performance information related to the network. -- To obtain the current configuration of the network. -- To provision changes of the configuration of the network. -- To obtain additional information related to the network. - -### 5.4.2 Network Information service - -#### 5.4.2.1 Overview - -The Network Information service provides to the Service Consumer information related to the network, in particular the RAN, that has been aggregated from multiple information sources that the SMO has access to, e.g., configuration, topology, network element state, geolocation, inventory, etc. - -#### 5.4.2.2 Queries related to information about cells. - -The Network Information service supports various information queries that give the rApps access to information aggregated from multiple sources. - -The following procedure is defined: - -**Query cells-related information:** This service operation allows to query aggregated information related to RAN cells. - -NOTE: How to query the information, and how this relates to the Data management and exposure services, is not defined in the present document. - -### 5.4.3 Fault management (FM) service - -#### 5.4.3.1 Overview - -The Fault management service allows the Service Consumer to obtain information about alarms. - -The RAN OAM-related functions in the SMO/Non-RT RIC framework produce this service. - -#### 5.4.3.2 Querying alarm information - -The FM service shall allow the Service Consumer to query alarm information. - -The following procedure is defined: - -**Query alarms:** This procedure allows the Service Consumer to query the alarm list to obtain the whole list, a subset of the alarms in the list, or an individual alarm. The Service Consumer may specify a set of filtering criteria to control what is returned as result. - -#### 5.4.3.3 Changing the alarm acknowledgement state. - -The FM service shall allow the Service Consumer to change the acknowledgement state of individual alarms (i.e., to acknowledge or unacknowledge them). - -The following procedure is defined: - -**Change alarm acknowledgement state:** This procedure allows the Service Consumer to change the acknowledgement state of an alarm (i.e., to acknowledge or unacknowledge it). - -### 5.4.4 Performance management (PM) service - -#### 5.4.4.1 Overview - -The performance management service allows the Service Consumer to access performance information that was collected from the network elements by the Service Producer. - -The RAN OAM-related functions in the SMO/Non-RT RIC framework produce this service. - -#### 5.4.4.2 Querying performance information - -The PM service shall allow to query performance information using a set of filtering criteria. - -The following procedure is defined: - -**Query performance information:** This procedure allows to query performance information that has been collected from the network elements. The Service Consumer specifies a set of filtering criteria to determine the set of information returned. - -NOTE: How to query the information, and how this relates to the Data management and exposure services, is not defined in the present document. - -### 5.4.5 Configuration management (CM) service - -#### 5.4.5.1 Overview - -In the following, the term "Service Consumer" refers to the role of an rApp that consumes the Configuration management (CM) service. The term "Configuration management service Producer" refers to the role of the logical RAN OAM-related functions in the SMO/Non-RT RIC framework producing the CM service. - -The CM service allows the Service Consumer to access configuration information pertaining to the managed entities, as obtained by the CM service Producer. The CM service further allows the Service Consumer to request configuration changes related to the managed entities. - -NOTE: As a preliminary definition in the context of R1, the term "managed entities" represents (i) the RAN nodes and RAN functions managed by the SMO via O1 or M-plane interfaces, and (ii) the group of these known as RAN-specific network slice subnets. The exact definition of the term "managed entity" is not defined in the present document. - -The following capabilities are provided by the CM service Producer over the R1 interface: - -- Retrieving configuration schemas -- Reading configuration data -- Writing configuration changes - -#### 5.4.5.2 Retrieving configuration schemas. - -The CM service allows the Service Consumer to retrieve information pertaining to the configuration schemas of one or more managed entities. - -The following procedure is defined: - -**Get schemas:** A Service Consumer can use this procedure to retrieve configuration schemas for the managed entities. The CM service Producer will respond with the requested schemas. The schemas provide information about which configuration attributes are supported by the managed entities. - -#### 5.4.5.3 Reading configuration data - -The CM service allows the Service Consumer to read the configuration data, related to one or more managed entities. - -The following procedure is defined: - -**Read Configuration:** This procedure enables the Service Consumer to obtain configuration data (including the configuration attributes) related to one or more managed entities from the CM service Producer, subject to optional filtering criteria. The CM service Producer responds to the Service Consumer by providing the requested configuration data or indicates a failure with an appropriate cause. - -#### 5.4.5.4 Writing configuration changes - -The CM service allows the Service Consumer to write configuration changes, related to one or more managed entities. - -The following procedure is defined: - -**Write Configuration:** This procedure enables the Service Consumer to request the CM service Producer for writing configuration changes related to one or more managed entities. The CM service Producer responds to the Service Consumer with the status of the write operation for the configuration changes requested by the Service Consumer or indicates a failure with an appropriate cause. - -## 5.5 O2-related Services - -### 5.5.1 General - -As described in the Non-RT RIC Architecture specification [3], the O2-related services produced by the SMO/Non-RT RIC framework provide access to O-Cloud management functionality that enables the Service Consumer: - -- To obtain information related to O-Cloud infrastructure management such as, - - Infrastructure Inventory, - - Infrastructure Monitoring, - - Infrastructure Provisioning, - - Infrastructure Lifecycle Management, - - Infrastructure Software Management. -- To obtain information related to O-Cloud deployment management such as, - - Deployment Inventory, - - Deployment Monitoring, - - Deployment Lifecycle Management, -- To provision changes of the configuration of the O-Cloud, -- To obtain additional information related to the O-Cloud. - -NOTE: Details about O-Cloud deployment management services, provision of configuration changes, additional information related to the O-Cloud is not defined in the present document. - -### 5.5.2 O2 Infrastructure management service - -#### 5.5.2.1 Overview - -O2 Infrastructure management service allows the Service Consumer to obtain information related to O-Cloud infrastructure management services. - -O2 related functions in the SMO/Non-RT RIC framework produce this service as specified in O2IMS [6]. - -#### 5.5.2.2 Query O2-IMS Information - -O2 Infrastructure management service shall support various information queries that give the rApps access to information related O-Cloud infrastructure management services. - -The following procedures are defined: - -**Query O2ims\_Infrastructure Inventory related information:** This service procedure allows to query information related to infrastructure resource inventory and event notification service of O-Cloud. - -**Query O2ims\_InfrastructureMonitoring related information:** This service procedure allows to query information related to telemetry reporting. - -**Query O2ims\_InfrastructureProvisioning information:** This service procedure allows to query information related to O-Cloud provisioning services. - -**Query O2ims\_InfrastructureLifecycleManagement information:** This service procedure allows to query information related to support of procedures for the automation of O-Clouds lifecycle events. - -### 5.5.3 O2 Deployment management service - -#### 5.5.3.1 Overview - -O2 deployment management service allows the Service Consumer to obtain information related to O-Cloud deployment management services. - -O2 related functions in the SMO/Non-RT RIC framework produce this service as specified in O2DMS [7] and O2GAP [8]. - -#### 5.5.3.2 Query O2-DMS Information - -O2 deployment management service shall support various information queries that give the rApps access to information related O-Cloud deployment management services. - -The following procedures is defined: - -**Query O2dms\_ Deployment Monitoring related information:** This service procedure allows to query information related to telemetry reporting. - -## 5.6 AI/ML Workflow Services - -### 5.6.1 General - -As described in the Non-RT RIC Architecture specification [3], the AI/ML workflow services enable: - -- Training of an AI/ML model -- Registration of an AI/ML model, -- Discovery of an AI/ML model, -- Subscription to change of an AI/ML model, -- Registration of capability to train an AI/ML model (optional), -- Query of AI/ML model training capability (optional), -- Storage of an AI/ML model, -- Monitoring the performance of a deployed AI/ML model, -- Retrieving the model location details of an AI/ML model. -- Requesting the deployment of an AI/ML model. -- Querying AI/ML model inference capabilities. - -- Requesting inference of an AI/ML model. - -The AI/ML workflow services include AI/ML model management and exposure services, which are produced by the AI/ML workflow functions. An AI/ML model is identified by a model identifier, which includes model name, model version and artifact version. Model identifier and model-related information can be registered, discovered and de-registered. - -The model identifier can be used by an rApp in the AI/ML workflow procedures. - -The cloud native application developer assigns the model name and the model version as part of an rApp package for model onboarding, see clause 6 in OAM architecture [10]. The model name and model version are not changed after onboarding or after rApp deployment with the AI/ML model, or after training by an AI/ML model training service Producer. If the AI/ML model needs to be upgraded, the cloud native application developer updates the model version, and the upgraded model is onboarded as part of a new rApp package. - -The onboarded AI/ML model comes pre-trained, or is specialized during onboarding, and this is reflected in the initial value of the artifact version of the AI/ML model. After the registered AI/ML model has been trained by an AI/ML model training service Producer, the artifact version is updated. - -AI/ML model Producer refers to an rApp that can register an AI/ML model and provides model-related information. When an AI/ML Model has been registered, it can be trained by authorized AI/ML Model Trainers and is available for discovery and deployment, by authorized AI/ML Model Consumers. - -NOTE: The AI/ML model Producer acting in the run-time process is related to the rApp provided for onboarding, with an AI/ML model in the rApp package, by the cloud native application developer acting in the design-time process. - -AI/ML model Trainer refers to an rApp that can train an AI/ML model, store a new AI/ML model artifact version, and provides training-related information. model training can be initiated via the AI/ML Model training service. Model storage and deletion can be initiated via the AI/ML model storage service. - -AI/ML model Consumer refers to an rApp that can discover and request deployment or inference of AI/ML model artifact versions of an AI/ML model. AI/ML model discovery allows an AI/ML model Consumer to discover AI/ML model identifiers and AI/ML model metadata based on registered AI/ML models and provided selection criteria. AI/ML model change notifications allow AI/ML model Consumer to be notified about changes of the subscribed AI/ML models. - -NOTE: Deployment of an rApp with an AI/ML model, e.g., after AI/ML model discovery, is not specified in the present document. - -AI/ML model performance monitoring allows authorized AI/ML model performance monitoring service consumers to monitor the performance of deployed AI/ML models and receive periodical, or event based performance related information. - -AI/ML inference service allows authorized AI/ML model Consumers to request the inference of an AI/ML model. AI/ML inference service Producer provides model performance information via the AI/ML model performance monitoring service. - -### 5.6.2 AI/ML model registration service - -#### 5.6.2.1 Overview - -AI/ML model Producers consume this service to register, query, update and delete an AI/ML model registration. - -The AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. - -#### 5.6.2.2 Registration of AI/ML model - -This set of procedures enable AI/ML model Producer to register, and manage the registration of, an AI/ML model. - -As part of the Register AI/ML model procedure, the AI/ML model Producer provides the producer identifier, model - -identifier and model-related information. - -The following procedures are defined: - -**Register AI/ML model:** An AI/ML model Producer uses this procedure to register an AI/ML model. On receiving the request, the AI/ML model management and exposure service Producer determines whether the AI/ML model Producer is authorized to register the AI/ML model. In the response, the AI/ML model management and exposure service Producer informs the AI/ML model Producer of the AI/ML model registration details. - -**Query AI/ML model registration:** An AI/ML model Producer can use this procedure to retrieve information about model registrations it has previously made. - -**Update AI/ML model registration:** An AI/ML model Producer can use this procedure to update an AI/ML model registration it has previously made. - -**Deregister AI/ML model:** An AI/ML model Producer can use this procedure to deregister an AI/ML model it has previously registered. - -### 5.6.3 AI/ML model storage service - -#### 5.6.3.1 Overview - -AI/ML model storage service Consumers consume this service to store and delete an AI/ML model or the location of the AI/ML model. The AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. - -#### 5.6.3.2 Storage of AI/ML model - -This set of procedures enable AI/ML model storage service Consumer to store and delete the AI/ML models and their locations. - -The following procedures are defined: - -**Store AI/ML model:** An AI/ML model storage service Consumer uses this procedure to store an AI/ML model. On receiving the request, the AI/ML model storage service Producer determines whether the AI/ML model storage service Consumer is authorized to store the AI/ML model. In the response, the AI/ML model storage service Producer informs the AI/ML model storage service Consumer if the AI/ML model is stored and about the location of the stored AI/ML model if stored. - -**Store location of AI/ML model:** An AI/ML model storage service Consumer uses this procedure to store the location of an AI/ML model. On receiving the request, the AI/ML model storage service Producer determines whether the AI/ML model storage service Consumer is authorized to store location of the AI/ML model. In the response, the AI/ML model storage service Producer informs the AI/ML model storage service Consumer if the location of the AI/ML model is stored. - -**Delete AI/ML model:** An AI/ML model storage service Consumer can use this procedure to delete an AI/ML model previously stored. On receiving the request, the AI/ML model storage service Producer determines whether the AI/ML model storage service Consumer is authorized to delete the AI/ML model. the AI/ML model storage service Producer informs the AI/ML model storage service Consumer that the AI/ML model is deleted. - -**Delete location of AI/ML model:** An AI/ML model storage service Consumer can use this procedure to delete the AI/ML model location previously stored. On receiving the request, the AI/ML model storage service Producer determines whether the AI/ML model storage service Consumer is authorized to delete the AI/ML model file location. In the response, the AI/ML model storage service Producer informs the AI/ML model storage service Consumer that the location of the AI/ML model is deleted. - -### 5.6.4 AI/ML model discovery services - -#### 5.6.4.1 Overview - -AI/ML model Consumers consume this service to discover registered AI/ML Models and their related information. The AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. - -#### 5.6.4.2 Discovery of AI/ML model - -This procedure enables an AI/ML model Consumer to discover registered AI/ML models and to retrieve information on the registered AI/ML models. - -The following procedure is defined: - -**Discover AI/ML model:** An AI/ML model Consumer can discover the AI/ML models that are registered based on provided selection criteria. For each registered AI/ML model, model identifiers and model metadata are provided as a response. The AI/ML model Consumer can only discover AI/ML models that it is authorized to access. - -### 5.6.5 AI/ML model change subscription service - -#### 5.6.5.1 Overview - -AI/ML model Consumers consume this service to subscribe to change notifications for registered AI/ML models and to receive notifications about AI/ML model changes. The AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. - -#### 5.6.5.2 Subscribing to AI/ML model changes. - -This set of procedures enable AI/ML model Consumer to subscribe to change notifications for registered AI/ML models. - -The following procedures are defined: - -**Subscribe AI/ML models changes:** An AI/ML model Consumer can use this procedure to subscribe to notifications regarding changes related to registered AI/ML models and thereby receive notifications when AI/ML models have been registered or deregistered, when information has been updated, and when new model versions and/or artifact versions have been stored or deleted. The subscription is created for the Model Consumer based on the AI/ML models that it is authorized to access, i.e., the AI/ML model Consumer can only subscribe to get notified about model changes of AI/ML models that it is authorized to access. - -**Unsubscribe AI/ML models changes:** An AI/ML model Consumer can unsubscribe from notifications regarding changes related to registered AI/ML models. - -**Notify AI/ML models changes:** The AI/ML model management and exposure service Producer uses this procedure to notify a subscribed AI/ML model Consumer about changes related to registered AI/ML models. - -### 5.6.6 AI/ML model training capability registration service - -#### 5.6.6.1 Overview - -AI/ML model Trainers consume this service to register, query, update and deregister its AI/ML model training capability. The AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. - -AI/ML model Trainer consumes this service to register its AI/ML model training capability. Register AI/ML model training capability is a procedure where an AI/ML model Trainer registers its capability to train AI/ML models to the AI/ML model management and exposure service Producer. Deregister AI/ML model training capability is a procedure where an AI/ML model Trainer declares the training capability is no longer available. - -#### 5.6.6.2 Registration of AI/ML training capability - -This set of procedures enable AI/ML model Trainer to register, and manage the registration of, its training capabilities. - -As part of the Register AI/ML model training capability procedure, the AI/ML model Trainer provides the rApp identifier and further information about the training capability, it may provide information on, including but not limited to, the following: - -- Information on the training platform that can be provided, e.g., framework and library, -- Information on available training resources. - -The following procedures are defined: - -**Register AI/ML model training capability:** An AI/ML model Trainer uses this procedure to register the capability to train AI/ML models. On receiving the request, the AI/ML model management and exposure service Producer determines whether the AI/ML model Trainer is authorized to register the AI/ML model training capability. In the response, the AI/ML model management and exposure service Producer informs the AI/ML model Trainer if the AI/ML model training capability is registered. - -**Query AI/ML model training capability:** An AI/ML model Trainer uses this procedure to query an AI/ML model training capability registration it has previously made. - -**Update AI/ML model training capability:** An AI/ML model Trainer uses this procedure to update an AI/ML model training capability registration it has previously made. - -**Deregister AI/ML model training capability:** An AI/ML model Trainer can use this procedure to deregister an AI/ML model training capability that it has previously registered. - -### 5.6.7 AI/ML Model deployment request service - -This procedure enables an AI/ML model deployment Service Consumer to request the deployment of a registered AI/ML model. The AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. - -The following procedure is defined: - -**Request AI/ML model deployment:** An AI/ML model deployment Service Consumer requests the deployment of a registered AI/ML model. The model identifier and target deployment location of the registered AI/ML model is provided in the request. The AI/ML model deployment Service Consumer can only request the deployment of registered AI/ML models that it is authorized to access. The AI/ML model deployment Service Consumer is notified of the outcome of the model deployment request. - -### 5.6.8 AI/ML model training services - -#### 5.6.8.1 Overview - -AI/ML model training service Consumers consume this service to request AI/ML model training, query AI/ML model training job status, cancel AI/ML model training, and receive notification about AI/ML model training job status change. AI/ML model Trainers or the AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. - -#### 5.6.8.2 AI/ML model training - -This set of procedures enable AI/ML model training service Consumer to request and manage the AI/ML model training of an AI/ML model. - -The following procedures are defined: - -**Request AI/ML model training:** An AI/ML model training service Consumer uses this procedure to request training of an AI/ML model by providing the information for training. The AI/ML training service Producer - -determines whether the AI/ML model training Consumer is authorized to request training of the AI/ML model. The AI/ML training service Producer creates the AI/ML model training job and responds to the AI/ML model training service Consumer with the training job identifier. - -**Query AI/ML model training job status:** An AI/ML model training service Consumer uses this procedure to query AI/ML model training job status by providing the training job identifier that it has previously received. - -**Cancel AI/ML model training:** An AI/ML model training service Consumer uses this procedure to request to cancel the training of an AI/ML model by providing the training job identifier that it has previously received. - -**Notify AI/ML model training job status change:** An AI/ML training service Producer uses this procedure to notify an AI/ML model training service Consumer about a status change of an AI/ML model training job. - -### 5.6.9 AI/ML model performance monitoring service - -#### 5.6.9.1 Overview - -The AI/ML model performance monitoring service is produced by the AI/ML model Consumer rApp. Authorized AI/ML model performance Consumers consume this service to subscribe to, and receive, performance information related to a deployed AI/ML model. During AI/ML model registration, supported AI/ML model performance related information is provided as part of the registration information. - -#### 5.6.9.2 Monitoring the performance of a deployed AI/ML model. - -This set of procedures enables the AI/ML model performance monitoring service Consumers to subscribe to, and receive, regular performance information related to a deployed AI/ML model. As part of the Subscribe AI/ML model performance procedure, the AI/ML model performance monitoring service Consumers provide the AI/ML model identifier, information for the AI/ML model performance monitoring, and optionally a notification URI to receive regular performance related information of the specified deployed AI/ML model. - -The following procedures are defined: - -**Subscribe AI/ML model performance:** AI/ML model performance monitoring service Consumers can use this procedure to subscribe to specific or all performance related information of a deployed AI/ML model. Supported AI/ML model performance related information is provided as part of the AI/ML model registration information. In the request, AI/ML model performance monitoring service Consumers can specify whether to be periodically notified or only notified in the occurrence of a specific event (e.g., if the performance of a deployed AI/ML model drops below a certain threshold). On receiving the subscription request, the AI/ML model performance monitoring service Producer creates the subscription and informs the AI/ML model performance monitoring service Consumer of the subscription ID. - -**Unsubscribe AI/ML model performance:** An AI/ML model performance monitoring service Consumer can unsubscribe from specific or all AI/ML model performance related information of a deployed AI/ML model. - -**Notify AI/ML model performance:** An AI/ML model performance monitoring service Producer can use this procedure to notify the AI/ML model performance monitoring service Consumers about performance information related to a deployed AI/ML model. - -### 5.6.10 AI/ML model inference service - -#### 5.6.10.1 Overview - -AI/ML model Consumer consumes this service to query the inference capabilities and initiate the inference of an AI/ML model. The AI/ML model Producer or the AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. - -#### 5.6.10.2 Inference of AI/ML model - -The below set of procedures enable AI/ML model Consumer to query inference capabilities and request inference of an AI/ML model. - -The following procedures are defined: - -**Query AI/ML model inference capabilities:** An AI/ML model Consumer uses this procedure to retrieve the inference capability information such as model identifier, input data and output data. On receiving the request, the AI/ML inference service Producer determines whether the AI/ML model Consumer is authorized to retrieve the inference capability information. In the response, the AI/ML inference service Producer informs the AI/ML model Consumer regarding the AI/ML model inference capability information. - -**Request AI/ML model inference:** An AI/ML model Consumer uses this procedure to request inference for an AI/ML model by providing the model identifier and input data. On receiving the request, the AI/ML inference service Producer determines whether the AI/ML model Consumer is authorized to request the inference of the AI/ML model. In the response, the AI/ML inference service Producer informs the AI/ML model Consumer of the model inference job identifier. - -**Cancel AI/ML model inference:** An AI/ML model Consumer uses this procedure to request to cancel the inference by providing the inference job identifier that it has previously received. - -### 5.6.11 AI/ML model training capability query services - -#### 5.6.11.1 Overview - -The AI/ML model training capability query service allows the Service Consumers to query all the available registered AI/ML model training capability. The AI/ML workflow functions in the SMO/Non-RT RIC framework produce this service. - -#### 5.6.11.2 Query of AI/ML model training capability - -This procedure enables a Service Consumer to query registered AI/ML model training capability. - -The following procedure is defined: - -**Query AI/ML model training capability:** A Service Consumer uses this procedure to retrieve the registered AI/ML model training capability information based on provided selection criteria. The Service Consumer can only query the AI/ML model training capability information of the AI/ML models that it is authorized to access. In the response, the Service Producer informs the Service Consumer AI/ML model Trainer rAppIds and the registered AI/ML model training capability information. - -## 5.7 rApp management Services - -### 5.7.1 General - -As described in the Non-RT RIC Architecture specification [3], clause 7.8, the rApp management services enable the following functionality: - -- rApp registration - -### 5.7.2 rApp registration service - -#### 5.7.2.1 Overview - -The rApp consumes this service to register with the rApp registration service Producer. - -#### 5.7.2.2 Registration of rApps - -The rApp consumes this service to register with the rApp registration service Producer and may provide information such as rApp name, vendor, software version, certificates, role of the rApp (Service Producer and / or Service Consumer), and security credentials. On successful registration, the rApp registration service Producer responds with an rApp instance identifier (rAppId). - -NOTE: The procedure for provisioning the security credentials by an rApp with the rApp registration service Producer is not defined in the present document. - -The following procedures are defined: - -**Registration:** An rApp can use this procedure to register with the rApp registration service Producer. - -**Update registration:** An rApp can use this procedure to update its registration with the rApp registration service Producer. - -**Deregistration:** An rApp can use this procedure to deregister with the rApp registration service Producer . - -# --- 6 R1 Interface Protocol Structure - -"R1TP" [5] defines the R1 transport protocol stack. - -# Annex (informative): Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2025.11.10 | 13.00 | Published version by updating the Data registration procedures and AI/ML model training capability registration services | -| 2025.07.10 | 12.00 | Published version by updating the rApp registration from SME to rApp management services. | -| 2024.03.15 | 11.00 | Published final version by updating the data subscription and data request, deprecating Heartbeat service | -| 2024.11.21 | 10.00 | Published as final version by adding the A1 ML model management services, procedure to query of AI/ML model training capabilities , procedure to retrieve the status of the data request and data subscription and updated the existing procedures for service registration and authorization service. | -| 2024.07.11 | 09.00 | Published final version by adding production capability related to DME type, added AI/ML model inference service, updated query procedure for subscription data and updated subscription procedures for SME. | -| 2024.03.18 | 08.00 | Published final version by adding AI/ML performance monitoring procedures and aligning the terms Producer and Consumer. | -| 2023.11.20 | 07.00 | Published final version by adding the AI/ML related service procedures and updated the data types to DME types and added the data streaming service in DME service. | -| 2023.07.27 | 06.00 | Published as Final version 06.00. | -| 2023.03.24 | 05.00 | Published as Final version 05.00. | -| 2022.11.18 | 04.00 | Published as Final version 04.00. | -| 2022.07.27 | 03.00 | Published as Final version 03.00. | -| 2022.03.31 | 02.00 | Published as Final version 02.00. | -| 2021.11.23 | 01.00 | Published as Final version 01.00. | \ No newline at end of file diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/854df8ad60507803253274673f9062cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index e20d85525829ce0ee72f0f1e7d337440c0022085..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:70202500dcd1d7555a287caab20530fcb4adfd35aaacfd59604999379d6de583 -size 4432 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 607dad2c40b148f2aa126f2acf40dc58dcec9ece..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1GAP-R005-v13.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:08182fc858d80dc6f48caf8a55cd8ea09ba9da42eaf1110e4b1ff102d2186056 -size 4519 diff --git a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/doc.md b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/doc.md deleted file mode 100644 index d625d0c2244e0428ad97abc4794277fe9591636e..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/doc.md +++ /dev/null @@ -1,1191 +0,0 @@ - - -# --- Type Definitions for R1 Services - -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..... | 5 | -| 3 Definition of terms, symbols and abbreviations..... | 5 | -| 3.1 Terms..... | 5 | -| 3.2 Symbols..... | 5 | -| 3.3 Abbreviations ..... | 5 | -| 4 R1 Application data model..... | 6 | -| 4.1 Introduction ..... | 6 | -| 4.2 Version conventions for the present document ..... | 6 | -| 5 Data type definitions for Data Management and Exposure services..... | 7 | -| 5.1 Common definitions..... | 7 | -| 5.1.1 Introduction..... | 7 | -| 5.1.2 Identifiers and Metadata ..... | 7 | -| 5.1.3 Versioning of DME types ..... | 7 | -| 5.1.4 Schemas for DME types ..... | 7 | -| 5.1.5 Common data type definitions ..... | 8 | -| 5.2 Definition of individual DME types..... | 9 | -| 5.2.1 Introduction..... | 9 | -| 5.2.2 DME type: RAN OAM PM data ..... | 9 | -| 5.2.3 DME type: RAN OAM Trace Metrics..... | 16 | -| Annex (informative): Change history ..... | 23 | - -# --- Foreword - -This Technical Specification (TS) has been produced by WG2 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 Type Definitions for R1Services. It is part of a TS-family covering the R1 interface specifications. - -# --- 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.WG2.TS.R1AP: "Application Protocols for R1 Services " ("R1AP"). -- [2] O-RAN.WG2.TS.R1GAP: "R1 interface: General Aspects and Principles" ("R1GAP"). -- [3] O-RAN.WG2.TS.R1UCR: "R1 Use Cases and Requirements" ("R1UCR"). -- [4] Semantic Versioning 2.0.0. " ("Semver") - -NOTE: ["https://semver.org](https://semver.org). - -- [5] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format" ("JSON"). -- [6] json-schema 2020-12, "" ("JSON schema"). -- [7] W3C REC-xmlschema-1-20010502: "XML Schema Part 1: Structures", - -NOTE: . - -- [8] W3C REC-xmlschema-2-20010502: "XML Schema Part 2: Datatypes", - -NOTE: . - -- [9] W3C REC-xml-names-19990114: "Namespaces in XML". - -NOTE: . - -- [10] 3GPP TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) ". -- [11] Void. -- [12] IETF RFC 3339: " Data and Time on the Internet: Timestamps". -- [13] 3GPP TS 32.401: "Telecommunication management; Performance Management (PM); Concept and requirements". -- [14] Void. -- [15] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for managed objects". - -- [16] Void. -- [17] O-RAN TS: "O1 Interface Specification for O-CU-UP and O-CU-CP". -- [18] O-RAN.TS: "O1 Interface Specification for O-DU". -- [19] 3GPP TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management". -- [20] 3GPP TS 32.423: "Telecommunication management; Subscriber and equipment trace; Trace data definition and management". - -## 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. - -- [i.1] W3C REC-xmlschema-0-20010502: "XML Schema Part 0: Primer". - -NOTE: . - -# --- 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the terms given in R1GAP [2], R1AP [1], and the following apply: - -**DME type:** data type managed and exposed by the DME services and identified by a DME type identifier. - -NOTE: The present document defines O-RAN specific DME types and O-RAN re-uses 3GPP data types where applicable. - -## 3.2 Symbols - -Void - -## 3.3 Abbreviations - -For the purposes of the present document, the following abbreviations apply: - -| | | -|-----|-------------------------| -| RAT | Radio Access Technology | -|-----|-------------------------| - -# --- 4 R1 Application data model - -## 4.1 Introduction - -The present document together with R1AP [1] defines the realization of the R1 procedures defined in R1GAP [2] and R1UCR[3]. - -R1AP [1] contains the service description, service operations, resource definition and the API definition (including the Open API document) for the R1 services. The present document contains the data model and the definitions of the schema-based objects transported in the procedures defined for the R1 services. - -The data types defined in the present document are API-independent and are lifecycle independently from the APIs defined in R1AP[1]. - -## 4.2 Version conventions for the present document - -The version number of the present document follows the "xx.yy" versioning scheme. There could be implications for the compatibility between implementations that uses DME types defined in different versions of this specification. - -An incremented "xx" version field of the present document could indicate that a new major feature (e.g., a new DME type) has been added, removed or that an incompatible change has been made to one or more DME types. An incremented "yy" version field could indicate that an optional feature has been added, a technical issue has been fixed, or that clarifications or editorial corrections have been made. - -The compatibility of rApps and R1 service API implementations in SMO/Non-RT RIC framework depends on the R1 service APIs and data types that are implemented. The present document handles the versions for protocol-agnostic data types used by the R1 services while the R1 service API versioning aspects are handled in R1AP[1]. - -# --- 5 Data type definitions for Data Management and Exposure services - -## 5.1 Common definitions - -### 5.1.1 Introduction - -This clause provides common definitions applicable to multiple DME types. - -### 5.1.2 Identifiers and Metadata - -#### 5.1.2.1 DME type identifier - -A DME type is identified by an identifier defined as `dmeTypeId` in R1AP [1], clause B.4.2. The DME type identifier consists of a namespace, name and a version. - -#### 5.1.2.2 Data category - -A DME type shall be assigned to at least one data category. Assigned data category values can be used as query parameter when searching for available DME types as specified in R1AP [1] . - -### 5.1.3 Versioning of DME types - -When updating a DME type, the version in the DME type identifier (see clause 5.1.2.1) is updated according to SemVer [4] to reflect its compatibility with other DME types that have the same namespace and name. - -Two DME types with the same namespace and name are incompatible if the major version digit in the version is different. - -Two DME types are only considered to be identical if all three of their attribute's namespace, name and version are identical. - -The version in the DME type identifier includes a pre-release version (e.g., “-alpha.1”) if the definition of a DME type is under development. - -### 5.1.4 Schemas for DME types - -#### 5.1.4.1 General - -The definition of a DME type is based on two schemas, a data production schema and a data delivery schema. - -#### 5.1.4.2 Data production schema - -The data production schema defines the structure for how to formulate parameters for the production of data instances of a DME type by a data job or a data offer. A data production schema can be based on data types defined in other specifications. - -Table 5.1.4.2-1 defines the attributes of the data production schema. - -**Table 5.1.4.2-1: Definition of attributes for the data production schema** - -| Attribute Name | Data Type Name | P | Cardinality | Description | -|----------------|----------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------| -| dataSelector | DataSelector | M | 1 | Selects the data to be included in the data instance to be produced. See NOTE1. | -| targetSelector | TargetSelector | M | 1 | This property selects the geographical area, or the entities, for which the data instance is to be produced. See NOTE1. | -| timing | Timing | M | 1 | This property defines the time-related parameters for the production of the data instances. See NOTE1. | - -NOTE 1: Every DME type shall define these types as part of defining the data production schema. - -NOTE 2: Additional attributes may be included in a data production schema. - -#### 5.1.4.3 Data delivery schema - -The data delivery schema defines the structure of the delivered content resulting from the related data job or data offer. A data delivery schema can be based on data types defined in other specifications The data delivery schema type is defined in R1AP [1]. - -A DME type can be defined with one or more data delivery schemas each based on different schema technologies such as for example JSON schema [6] and XSD [7], [8], [9] and [i.1]. - -### 5.1.5 Common data type definitions - -#### 5.1.5.1 Structured Data Types - -##### 5.1.5.1.1 Data type: CollectionWindow - -This data type allows selecting the window for data collection and contains the attributes defined in table: 5.1.5.1.1-1. - -**Table 5.1.5.1.1-1: Definition of data type CollectionWindow** - -| Attribute Name | Data Type | P | Cardinality | Description | -|----------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------| -| startTime | TimeOfDay | M | 1 | This attribute specifies the start of the collection period. See clause 5.1.2.2. | -| stopTime | TimeOfDay | O | 0..1 | This attribute specifies the end of the collection period. If not provided, the time period is indefinite. See clause 5.1.2.2. | - -#### 5.1.5.2 Simple data types - -**Table 5.1.5.2-1: Definition of simple data types** - -| Type Name | Type Definition | Description | Applicability | -|-------------------|-----------------|-------------------------------------------------------------------------------------|---------------| -| GranularityPeriod | integer | Granularity period simple data type is defined in 3GPP 32.401 [13], clause 5.4.1.4. | | -| TimeOfDay | string | String with format as defined in IETF RFC 3339 [12], clause 5.6. | | - -#### 5.1.5.3 Enumerations - -##### 5.1.5.3.1 Enumeration: DataCategory - -**Table 5.1.5.3.1-1: Enumeration DataCategory** - -| Enumeration Value | Description | -|-----------------------------|--------------------------------------------------------------------| -| PERFORMANCE_MANAGEMENT_DATA | Category for DME type definitions for performance management data. | - -## 5.2 Definition of individual DME types - -### 5.2.1 Introduction - -This clause defines DME types. - -A DME type can be registered and discovered using the DME services. Data instances of a DME type can be produced by means of a data job or data offer. - -The definition of a DME type follows a template that includes but is not limited to: - -- 1) the declaration of a DME type identifier, -- 2) the assignment of a data category, -- 3) the definition of the data types needed for the data production schema (in terms of data selector, target selector, timing and optionally further types) and the data delivery schema or schemas, -- 4) the definition of the data production schema and data delivery schema or schemas. - -### 5.2.2 DME type: RAN OAM PM data - -#### 5.2.2.1 DME type identifier - -The definition of the DME type identifier is provided in clause 5.1.2.2. The DME type for RAN OAM PM data is identified as: - -DmeTypeId: ORAN:RanOamPmData:1.0.0. - -#### 5.2.2.2 Data category - -The definition of the data category is provided in clause 5.1.2.1. The DME type for RAN OAM PM data is categorized as: - -DataCategory: PERFORMANCE\_MANAGEMENT\_DATA. - -#### 5.2.2.3 Data type definitions - -##### 5.2.2.3.1 Structured data types - -###### 5.2.2.3.1.1 Data type: DataSelector - -This data type allows selecting the attributes of the data instance to be produced and contains the attributes defined in table: 5.2.2.3.1.1-1. - -**Table 5.2.2.3.1.1-1: Definition of data type DataSelector** - -| Attribute Name | Data Type | P | Cardinality | Description | -|----------------|----------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| managementData | ManagementData | M | 1 |

The definition of the managementData attribute is aligned with the definition of the ManagementData class specified in 3GPP TS 28.622 [10], clause 4.3.50 with the restriction that metrics defined in 3GPP TS 32.422 [19] are not allowed.

The managementData attribute can be used to address performance measurements, KPIs defined by 3GPP and O-RAN, as well as vendor-specific performance measurements and KPIs. Example of O-RAN defined performance measurement for RAN OAM is defined in O1 Interface Specification for O-CU-UP and O-CU-CP [17] and O1 Interface Specification for O-DU [18].

| - -###### 5.2.2.3.1.2 Data type: TargetSelector - -This data type allows selecting the target for which data are to be produced and contains the following attributes defined in table 5.2.2.3.1.2-1: - -**Table 5.2.2.3.1.2-1: Definition of data type TargetSelector** - -| Attribute Name | Data Type | P | Cardinality | Description | -|-----------------------------------------------------------------------------------------------------------------------|------------|---|-------------|-----------------------------------------------------------------------| -| nodeFilter | NodeFilter | C | 0..1 | The NodeFilter type is defined in 3GPP TS 28.622 [10], clause 4.3.49. | -| objectInstances | DnList | C | 0..1 | See clause 5.2.2.3.1.4 | -| NOTE: Presence condition "C" means one and only one of these attributes shall be present when this data type is used. | | | | | - -###### 5.2.2.3.1.3 Data type: Timing - -This data type allows selecting the timing for production of the data instance and contains the attributes defined in table: 5.2.2.3.1.3-1. - -**Table 5.2.2.3.1.3-1: Definition of data type Timing** - -| Attribute Name | Data Type | P | Cardinality | Description | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---|-------------|--------------------------------------------------------------------------------| -| collectionWindow | CollectionWindow | M | 1 | see clause 5.2.1.3.1.4 | -| granularityPeriod | GranularityPeriod | M | 1 | see clause 5.1.4.2 | -| reportingPeriod | integer | C | 0..1 | Reporting period as defined in 3GPP TS 32.401 [13], clause 5.4.1.5. (See NOTE) | -| NOTE: For subscribe data procedure as defined in R1AP [1], clause 7.3.4.1.2.2, this attribute shall be present if the data is delivered in the form of files and shall be absent if the data is streamed. For data request procedure as defined in R1AP [1], clause 7.3.4.1.2.1 this attribute shall be absent. | | | | | - -###### 5.2.2.3.1.4 Data type: DnList - -This data type allows selecting list of DNs and contains the attributes defined in table: 5.2.2.3.1.4-1. - -**Table 5.2.2.3.1.4-1: Definition of data type DnList** - -| Attribute Name | Data Type | P | Cardinality | Description | -|----------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| -| DnList | array(Dn) | M | 1..N | The Dn data type is defined in 3GPP TS 32.300 [15], clause 7. Example of DN in a string representation is defined in 3GPP TS 32.300 [15], clause 8. | - -##### **5.2.2.3.2 Simple data types** - -None. - -##### **5.2.2.3.3 Enumerations** - -None. - -#### **5.2.2.4 Schemas** - -##### **5.2.2.4.1 Data production schema** - -The data production schema is based on the JSON schema. - -``` -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "description": "dataJobSchema for data subscription/data request.Copyright 2026 O-RAN ALLIANCE e.V. Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); You may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.o-ran.org/sccl.", - "version": "v1.1", - "type": "object", - "properties": { - "dataSelector": { - "managementData": { - "$ref": "#/definitions/ManagementData" - } - }, - "targetSelector": { - "oneOf": [ - { - "type": "object", - "properties": { - "nodeFilter": { - "$ref": "#/definitions/NodeFilter" - } - }, - "additionalProperties": false - }, - { - "type": "object", - "properties": { - "objectInstances": { - "$ref": "#/definitions/DnList" - } - }, - "additionalProperties": false - } - ] - }, - "timing": { - "type": "object", - "properties": { - "collectionWindow": { - "type": "object", - "properties": { - "startTime": { - "$ref": "#/definitions/TimeOfDay" - } - }, - } - } - } - } -} -``` - -``` - - "stopTime": { - "$ref": "#/definitions/TimeOfDay" - } - }, - "additionalProperties": false, - "required": [ - "startTime", - "stopTime" - ] - }, - "granularityPeriod": { - "$ref": "#/definitions/GranularityPeriod" - }, - "reportingPeriod": { - "$ref": "#/definitions/ReportingPeriod" - } - }, - "additionalProperties": false, - "required": [ - "collectionWindow", - "granularityPeriod" - ] -} -}, -"required": [ - "dataSelector", - "targetSelector" -], -"definitions": { - "ManagementData": { - "oneOf": [ - { - "type": "object", - "properties": { - "mgtDataCategory": { - "type": "string" - } - }, - "additionalProperties": false, - "required": [ - "mgtDataCategory" - ] - }, - { - "type": "object", - "properties": { - "mgtDataName": { - "type": "array" - } - }, - "additionalProperties": false, - "required": [ - "mgtDataName" - ] - } - ] - }, - "NodeFilter": { - "type": "array", - "properties": { - "areaOfInterest": { - "$ref": "#/definitions/AreaOfInterest" - }, - "networkDomain": { - "$ref": "#/definitions/NetworkDomain" - }, - "cPuPType": { - "$ref": "#/definitions/CPuPType" - }, - "sst": { - "$ref": "#/definitions/Sst" - } - } - } -} - -``` - -``` - - } - }, - "additionalProperties": false -}, -"DnList": { - "type": "array", - "minItems": 1, - "items": { - "$ref": "#/definitions/Dn" - } -}, -"Dn": { - "type": "string" -}, -"AreaOfInterest": { - "oneOf": [ - { - "type": "object", - "properties": { - "geoAreaToCellMapping": { - "$ref": "#/definitions/GeoAreaToCellMapping" - } - }, - "additionalProperties": false, - "required": [ - "geoAreaToCellMapping" - ] - }, - { - "type": "object", - "properties": { - "taiList": { - "type": "array", - "item": { - "$ref": "#/definitions/Tai" - }, - "minItems": 1, - "maxItems": 8 - } - }, - "additionalProperties": false, - "required": [ - "taiList" - ] - }, - { - "type": "object", - "properties": { - "nrCellIdList": { - "type": "array", - "items": { - "$ref": "#/definitions/NrCellIdList" - }, - "minItems": 1, - "maxItems": 32 - } - }, - "additionalProperties": false, - "required": [ - "nrCellIdList" - ] - }, - { - "type": "object", - "properties": { - "eutraCellIdList": { - "type": "array", - "items": { - "$ref": "#/definitions/E-UTRACGI" - }, - "minItems": 1, - -``` - -``` - - "maxItems": 32 - } - }, - "additionalProperties": false, - "required": [ - "eutraCellIdList" - ] - } -] -}, -"NetworkDomain": { - "type": "string", - "enum": [ - "RAN", - "CN" - ] -}, -"CPuPType": { - "type": "string", - "enum": [ - "CU", - "UP" - ] -}, -"Sst": { - "type": "integer" -}, -"GranularityPeriod": { - "type": "integer" -}, -"ReportingPeriod": { - "type": "integer" -}, -"GeoAreaToCellMapping": { - "type": "object", - "properties": { - "convexGeoPolygon": { - "type": "array", - "items": { - "$ref": "#/definitions/GeoCoordinate" - }, - "minItems": 3 - }, - "associationThreshold": { - "type": "integer" - } - }, - "additionalProperties": false, - "required": [ - "convexGeoPolygon" - ] -}, -"GeoCoordinate": { - "type": "object", - "properties": { - "latitude": { - "type": "number" - }, - "longitude": { - "type": "number" - } - }, - "additionalProperties": false, - "required": [ - "latitude", - "longitude" - ] -}, -"Tai": { - "type": "object", - "properties": { - -``` - -``` - - "mcc": { - "type": "integer" - }, - "mnc": { - "type": "integer" - }, - "tac": { - "type": "integer" - } - }, - "additionalProperties": false, - "required": [ - "mcc", - "mnc", - "tac" - ] - }, - "NrCellIdList": { - "oneOf": [ - { - "type": "object", - "properties": { - "nrCGI": { - "$ref": "#/definitions/NRCGI" - } - }, - "additionalProperties": false, - "required": [ - "nrCGI" - ] - }, - { - "type": "object", - "properties": { - "e-utraCGI": { - "$ref": "#/definitions/E-UTRACGI" - } - }, - "additionalProperties": false, - "required": [ - "e-utraCGI" - ] - } - ] - }, - "NRCGI": { - "type": "object", - "properties": { - "plmnIdentity": { - "type": "string", - "format": "base64" - }, - "nrCellIdentity": { - "type": "string", - "format": "base32" - } - }, - "additionalProperties": false, - "required": [ - "plmnIdentity", - "nrCellIdentity" - ] - }, - "E-UTRACGI": { - "type": "object", - "properties": { - "plmnIdentity": { - "type": "string", - "format": "base64" - }, - "e-utraCellIdentity": { - -``` - -``` - - "type": "string", - "format": "base32" - } - }, - "additionalProperties": false, - "required": [ - "plmnIdentity", - "e-utraCellIdentity" - ] - }, - "TimeOfDay": { - "type": "string", - "Description": "String with format as defined in clause 5.6 of IETF RFC 3339. Examples, -20:15:00, 20:15:00-08:00 (for 8 hours behind UTC)." - } -} -} - -``` - -##### 5.2.2.4.2 Data delivery schemas - -###### 5.2.2.4.2.1 Data delivery schema# 1 - -This data delivery schema is based on the XML schema and is defined in 3GPP TS 28.532 [11], clause 12.3.2.4. - -### 5.2.3 DME type: RAN OAM Trace Metrics - -#### 5.2.3.1 DME type identifier - -The definition of the DME type identifier is provided in clause 5.1.2.2. The DME type for RAN OAM TraceMetrics is identified as: - -DmeTypeId: ORAN:RanOamTraceMetrics:1.0.0. - -#### 5.2.3.2 Data category - -The definition of the data category is provided in clause 5.1.2.1. The DME type for RAN OAM TraceMetrics is categorized as: - -DataContext: RAN\_OAM\_TRACE\_METRICS\_DATA. - -#### 5.2.3.3 Data type definitions - -##### 5.2.3.3.1 Structured data types - -###### 5.2.3.3.1.1 Data type: DataSelector - -This data type allows selecting the attributes of the data instance to be produced and contains the attributes defined in table: 5.2.3.3.1.1-1. - -**Table 5.2.3.3.1.1-1: Definition of data type DataSelector** - -| Attribute Name | Data Type | P | Cardinality | Description | -|-----------------------|-----------|---|-------------|------------------------------------------------------------------------------| -| supportedTraceMetrics | String | M | 1 | The list of trace metrics as specified in 3GPP TS 28.622 [10], clause 4.4.1. | - -###### 5.2.3.3.1.2 Data type: TargetSelector - -This data type allows selecting the target for which data are to be produced and contains the following attributes defined in table 5.2.3.3.1.2-1. - -**Table 5.2.3.3.1.2-1: Definition of data type TargetSelector** - -| Attribute Name | Data Type | P | Cardinality | Description | -|-----------------------------------------------------------------------------------------------------------------------|------------|---|-------------|-----------------------------------------------------------------------| -| nodeFilter | NodeFilter | C | 0..1 | The NodeFilter type is defined in 3GPP TS 28.622 [10], clause 4.3.49. | -| objectInstances | DnList | C | 0..1 | See clause 5.2. 3.3.1.4 | -| NOTE: Presence condition “C” means one and only one of these attributes shall be present when this data type is used. | | | | | - -###### **5.2.3.3.1.3 Data type: Timing** - -This data type allows selecting the timing for production of the data instance and contains the attributes defined in table: 5.2.3.3.1.3-1. - -**Table 5.2.3.3.1.3-1: Definition of data type Timing** - -| Attribute Name | Data Type | P | Cardinality | Description | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---|-------------|--------------------------------------------------------------------------------| -| collectionWindow | CollectionWindow | M | 1 | see clause 5.2.1.3.1.4 | -| granularityPeriod | GranularityPeriod | M | 1 | see clause 5.1.4.2 | -| reportingPeriod | integer | C | 0..1 | Reporting period as defined in 3GPP TS 32.401 [13], clause 5.4.1.5. (See NOTE) | -| NOTE: For subscribe data procedure as defined in R1AP [1], clause 7.3.4.1.2.2, this attribute shall be present if the data is delivered in the form of files and shall be absent if the data is streamed. For data request procedure as defined in R1AP [1], clause 7.3.4.1.2.1 this attribute shall be absent. | | | | | - -###### **5.2.3.3.1.4 Data type: DnList** - -This data type allows selecting list of DNs and contains the attributes defined in table: 5.2.3.3.1.4-1. - -**Table 5.2.3.3.1.4-1: Definition of data type DnList** - -| Attribute Name | Data Type | P | Cardinality | Description | -|----------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| -| DnList | array(Dn) | M | 1..N | The Dn data type is defined in 3GPP TS 32.300 [15], clause 7. Example of DN in a string representation is defined in 3GPP TS 32.300 [15], clause 8. | - -##### **5.2.3.3.2 Simple data types** - -None. - -##### **5.2.3.3.3 Enumerations** - -None. - -#### **5.2.3.4 Schemas** - -##### **5.2.3.4.1 Data production schema** - -The data production schema is based on the JSON schema. - -``` -{ - "$schema": "https://json-schema.org/draft/2020-12/schema", - "description": "dataJobSchema for data subscription/data request. Copyright 2026 O-RAN ALLIANCE e.V. Licensed under the Standards Collaboration, Copyright License Version 1.0 (the \"License\"); You may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.o-ran.org/sccl.", - "version": "v1.1", - "type": "object", - "properties": { - "dataSelector": { -``` - -``` - - "supportedTraceMetrics": { - "$ref": "#/definitions/SupportedTraceMetrics" - } - }, - "targetSelector": { - "oneOf": [ - { - "type": "object", - "properties": { - "nodeFilter": { - "$ref": "#/definitions/NodeFilter" - } - }, - "additionalProperties": false - }, - { - "type": "object", - "properties": { - "objectInstances": { - "$ref": "#/definitions/DnList" - } - }, - "additionalProperties": false - } - ] - }, - "timing": { - "type": "object", - "properties": { - "collectionWindow": { - "type": "object", - "properties": { - "startTime": { - "$ref": "#/definitions/TimeOfDay" - }, - "stopTime": { - "$ref": "#/definitions/TimeOfDay" - } - }, - "additionalProperties": false, - "required": [ - "startTime", - "stopTime" - ] - }, - "granularityPeriod": { - "$ref": "#/definitions/GranularityPeriod" - }, - "reportingPeriod": { - "$ref": "#/definitions/ReportingPeriod" - } - }, - "additionalProperties": false, - "required": [ - "collectionWindow", - "granularityPeriod" - ] - } - } - }, - "required": [ - "dataSelector", - "targetSelector" - ], - "definitions": { - "SupportedTraceMetrics": { - "type": "object", - "properties": { - "supportedTraceMetrics": { - "type": "array", - "items": { - "type": "string" - } - } - } - } - } -} - -``` - -``` - - } - } -}, -"required": [ - "SupportedTraceMetrics" -], -"additionalProperties": false -}, -"NodeFilter": { - "type": "array", - "properties": { - "areaOfInterest": { - "$ref": "#/definitions/AreaOfInterest" - }, - "networkDomain": { - "$ref": "#/definitions/NetworkDomain" - }, - "cPuPType": { - "$ref": "#/definitions/CPuPType" - }, - "sst": { - "$ref": "#/definitions/Sst" - } - }, - "additionalProperties": false -}, -"DnList": { - "type": "array", - "minItems": 1, - "items": { - "$ref": "#/definitions/Dn" - } -}, -"Dn": { - "type": "string" -}, -"AreaOfInterest": { - "oneOf": [ - { - "type": "object", - "properties": { - "geoAreaToCellMapping": { - "$ref": "#/definitions/GeoAreaToCellMapping" - } - }, - "additionalProperties": false, - "required": [ - "geoAreaToCellMapping" - ] - }, - { - "type": "object", - "properties": { - "taiList": { - "type": "array", - "item": { - "$ref": "#/definitions/Tai" - }, - "minItems": 1, - "maxItems": 8 - } - }, - "additionalProperties": false, - "required": [ - "taiList" - ] - }, - { - "type": "object", - "properties": { - "nrCellIdList": { - -``` - -``` - - "type": "array", - "items": { - "$ref": "#/definitions/NrCellIdList" - }, - "minItems": 1, - "maxItems": 32 - } - }, - "additionalProperties": false, - "required": [ - "nrCellIdList" - ] - }, - { - "type": "object", - "properties": { - "eutraCellIdList": { - "type": "array", - "items": { - "$ref": "#/definitions/E-UTRACGI" - }, - "minItems": 1, - "maxItems": 32 - } - }, - "additionalProperties": false, - "required": [ - "eutraCellIdList" - ] - } -] -}, -"NetworkDomain": { - "type": "string", - "enum": [ - "RAN", - "CN" - ] -}, -"CPuPType": { - "type": "string", - "enum": [ - "CU", - "UP" - ] -}, -"Sst": { - "type": "integer" -}, -"GranularityPeriod": { - "type": "integer" -}, -"ReportingPeriod": { - "type": "integer" -}, -"GeoAreaToCellMapping": { - "type": "object", - "properties": { - "convexGeoPolygon": { - "type": "array", - "items": { - "$ref": "#/definitions/GeoCoordinate" - }, - "minItems": 3 - }, - "associationThreshold": { - "type": "integer" - } - }, - "additionalProperties": false, - "required": [ - -``` - -``` - - "convexGeoPolygon" - ] - }, - "GeoCoordinate": { - "type": "object", - "properties": { - "latitude": { - "type": "number" - }, - "longitude": { - "type": "number" - } - }, - "additionalProperties": false, - "required": [ - "latitude", - "longitude" - ] - }, - "Tai": { - "type": "object", - "properties": { - "mcc": { - "type": "integer" - }, - "mnc": { - "type": "integer" - }, - "tac": { - "type": "integer" - } - }, - "additionalProperties": false, - "required": [ - "mcc", - "mnc", - "tac" - ] - }, - "NrCellIdList": { - "oneOf": [ - { - "type": "object", - "properties": { - "nrCGI": { - "$ref": "#/definitions/NRCGI" - } - }, - "additionalProperties": false, - "required": [ - "nrCGI" - ] - }, - { - "type": "object", - "properties": { - "e-utraCGI": { - "$ref": "#/definitions/E-UTRACGI" - } - }, - "additionalProperties": false, - "required": [ - "e-utraCGI" - ] - } - ] - }, - "NRCGI": { - "type": "object", - "properties": { - "plmnIdentity": { - -``` - -``` - - "type": "string", - "format": "base64" - }, - "nrCellIdentity": { - "type": "string", - "format": "base32" - } - }, - "additionalProperties": false, - "required": [ - "plmnIdentity", - "nrCellIdentity" - ] - }, - "E-UTRACGI": { - "type": "object", - "properties": { - "plmnIdentity": { - "type": "string", - "format": "base64" - }, - "e-utraCellIdentity": { - "type": "string", - "format": "base32" - } - }, - "additionalProperties": false, - "required": [ - "plmnIdentity", - "e-utraCellIdentity" - ] - }, - "TimeOfDay": { - "type": "string", - "Description": "String with format as defined in clause 5.6 of IETF RFC 3339. Examples, -20:15:00, 20:15:00-08:00 (for 8 hours behind UTC)." - } -} -} -} - -``` - -##### 5.2.3.4.2 Data delivery schemas - -###### 5.2.3.4.2.1 Data delivery schema# 1 - -This data delivery schema for streaming trace is based on the Trace record schema and is defined in 3GPP TS 32.423 [20], clause 5.2. - -# --- Annex (informative): Change history - -| Date | Revision | Description | -|------------|----------|----------------------------------------------------------------------------------------------------------------| -| 2025.11.10 | 04.02 | Published final version by adding the sccl license to the JSON schemas | -| 2024.03.14 | 04.01 | Published final version by adding an example of RAN OAM Trace Metrics | -| 2024.11.21 | 04.00 | Published the final version by adding a new DME type for RAN OAM Trace Metrics | -| 2024.07.11 | 03.00 | Published the final version by refactoring the DME type definitions. | -| 2024.03.18 | 02.00 | Published the final version by removing the alpha for RanOamPmData and adding the Data Production schema table | -| 2023.11.20 | 01.00 | Published the final version with a DME data type | \ No newline at end of file diff --git a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/11358a9fa9cfdf9faa0e5645ce4336f9_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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/185df94f4a6a5245323255e844a30ec0_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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/226f5e462c99b71e08dc9abaa5ae260c_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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/253600420ae7bd7d0119563b895cbf8a_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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/2b357e4034ff41a2e0c3ca8c25c00c9d_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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/6a5342571eca4b46338fdfb3c42a8055_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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/83ee9f10bd3636e192d68decf7f04cec_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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/854df8ad60507803253274673f9062cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/89100a6476d1d96f22c192db16502fec_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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/8dcca7651accff77ce832523fe2c7e64_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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/a28ab03366399b5e0a61445bc57e3724_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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/c389468860cd886ab9c732473e959f0f_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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TD-R005-v04.02/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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/doc.md b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/doc.md deleted file mode 100644 index c58544fb8d19269183bf0ddd061bc0bfad897c7d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/doc.md +++ /dev/null @@ -1,5652 +0,0 @@ - - -# --- **R1 interface: Test 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., Buschkauler 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..... | 6 | -| 3 Definition of terms, symbols and abbreviations..... | 7 | -| 3.1 Terms..... | 7 | -| 3.2 Symbols..... | 7 | -| 3.3 Abbreviations ..... | 7 | -| 4 Test methodology ..... | 7 | -| 4.1 General ..... | 7 | -| 4.2 Conformance testing of rApps..... | 7 | -| 4.2.1 General..... | 7 | -| 4.2.2 Test configuration ..... | 7 | -| 4.3 Conformance testing of SMO/Non-RT RIC framework ..... | 8 | -| 4.3.1 General..... | 8 | -| 4.3.2 Test configuration ..... | 8 | -| 5 SME Service Registration service test cases ..... | 9 | -| 5.1 Conformance test cases for rApp ..... | 9 | -| 5.1.1 General..... | 9 | -| 5.1.2 Register service API as API Consumer test scenario..... | 10 | -| 5.2 Conformance test cases for SMO/Non-RT RIC framework..... | 14 | -| 5.2.1 General..... | 14 | -| 5.2.2 Register service API as API Producer test scenario..... | 14 | -| 6 SME Service Discovery service test cases ..... | 18 | -| 6.1 Conformance test cases for rApp ..... | 18 | -| 6.1.1 General..... | 18 | -| 6.1.2 Discover service API as API Consumer test scenario ..... | 19 | -| 6.2 Conformance test cases for SMO/Non-RT RIC framework..... | 20 | -| 6.2.1 General..... | 20 | -| 6.2.2 Service discovery API as API Producer test scenario..... | 20 | -| 7 SME Service Subscription service test cases ..... | 21 | -| 7.1 Conformance test cases for rApp ..... | 21 | -| 7.1.1 General..... | 21 | -| 7.1.2 Service events subscription API as API Consumer test scenario..... | 21 | -| 7.2 Conformance test cases for SMO/Non-RT RIC framework..... | 23 | -| 7.2.1 General..... | 23 | -| 7.2.2 Service events subscription API as API Producer test scenario..... | 23 | -| 8 DME Data registration service test cases ..... | 26 | -| 8.1 Conformance test cases for rApp ..... | 26 | -| 8.1.1 General..... | 26 | -| 8.1.2 Data registration API as API consumer test scenario ..... | 26 | -| 8.2 Conformance test cases for SMO/Non-RT RIC framework..... | 30 | -| 8.2.1 General..... | 30 | -| 8.2.2 Data registration API as API Producer test scenario ..... | 30 | -| 9 DME Data request service test cases..... | 35 | -| 9.1 Conformance test cases for rApp ..... | 35 | - -- 9.1.1 General.....35 -- 9.1.2 Data access API as API Consumer test scenario .....35 -- 9.2 Conformance test cases for SMO/Non-RT RIC framework.....37 -- 9.2.1 General.....37 -- 9.2.2 Data access API as API Producer test scenario .....38 -- 10 DME Data subscription service test cases.....40 -- 10.1 Conformance test cases for rApp .....40 -- 10.1.1 General.....40 -- 10.1.2 Data access API as API Consumer test scenario .....41 -- 10.2 Conformance test cases for SMO/Non-RT RIC framework.....45 -- 10.2.1 General.....45 -- 10.2.2 Data access API as API Producer test scenario .....45 -- 11 A1 related services test cases .....51 -- 11.1 Conformance test cases for rApp .....51 -- 11.1.1 General.....51 -- 11.1.2 A1 policy management API as API Consumer test scenario .....52 -- 11.2 Conformance test cases for SMO/Non-RT RIC framework.....60 -- 11.2.1 General.....60 -- 11.2.2 A1 policy management API as API Producer test scenario .....61 -- 12 DME Data discovery services test cases .....71 -- 12.1 Conformance test cases for rApp .....71 -- 12.1.1 General.....71 -- 12.1.2 Data discover API as API Consumer test scenario .....72 -- 12.2 Conformance test cases for SMO/Non-RT RIC framework.....73 -- 12.2.1 General.....73 -- 13 DME Data offer service test cases .....75 -- 13.1 Conformance test cases for rApp .....75 -- 13.1.1 General.....75 -- 13.1.2 Data offer API as API Consumer test scenario.....76 -- 13.2 Conformance test cases for SMO/Non-RT RIC framework.....77 -- 13.2.1 General.....77 -- 13.2.2 Data offer API as API Producer test scenario.....78 -- 14 SME Boot strap service test cases .....80 -- 14.1 Conformance test cases for rApp .....80 -- 14.1.1 General.....80 -- 14.1.2 Bootstrap API as API Consumer test scenario.....81 -- 14.2 Conformance test cases for SMO/Non-RT RIC framework.....81 -- 14.2.1 General.....81 -- 14.2.2 Bootstrap API as API Producer test scenario.....82 -- 15 AI/ML workflow AI/ML model registration API test cases .....83 -- 15.1 Conformance test cases for rApp .....83 -- 15.1.1 General.....83 -- 15.1.2 AI/ML model registration API as API consumer test scenario.....83 -- 15.2 Conformance test cases for SMO/Non-RT RIC framework.....86 -- 15.2.1 General.....86 -- 15.2.2 AI/ML model registration API as API Producer test scenario.....86 -- 16 AI/ML workflow AI/ML model discovery API test cases .....90 -- 16.1 Conformance test cases for rApp .....90 -- 16.1.1 General.....90 -- 16.1.2 AI/ML model discovery API as API Consumer test scenario .....90 -- 16.2 Conformance test cases for SMO/Non-RT RIC framework.....92 -- 16.2.1 General.....92 -- 16.2.2 AI/ML model discovery API as API Producer test scenario .....92 -- 17 RAN OAM Configuration management service test cases .....94 -- 17.1 Conformance test cases for rApp .....94 - -- 17.1.1 General.....94 -- 17.1.2 Configuration management API as API Consumer test scenario.....94 -- 17.1.3 Configuration schema information API as API Consumer test scenario .....96 -- 17.2 Conformance test cases for SMO/Non-RT RIC framework.....97 -- 17.2.1 General.....97 -- 17.2.2 Configuration management as API Producer test scenario.....98 -- 17.2.3 Configuration schema information API as API Producer test scenario .....99 -- 18 RAN OAM Fault management service test cases .....101 -- 18.1 Conformance test cases for rApp .....101 -- 18.1.1 General.....101 -- 18.1.2 Fault management API as API Consumer test scenario.....101 -- 18.2 Conformance test cases for SMO/Non-RT RIC framework.....103 -- 18.2.1 General.....103 -- 18.2.2 Fault management as API Producer test scenario .....103 -- 19 DME Data delivery service test cases .....105 -- 19.1 Conformance test cases for rApp .....105 -- 19.1.1 General.....105 -- 19.1.2 HTTP based Push data API as API producer test scenario .....106 -- 19.1.3 HTTP based Pull data API as API Consumer test scenario .....106 -- 19.2 Conformance test cases for SMO/Non-RT RIC framework.....107 -- 19.2.1 General.....107 -- 19.2.2 HTTP based Push data API as API Consumer test scenario.....107 -- 19.2.3 HTTP based Pull data API as API Producer test scenario .....108 -- 20 AI/ML workflow AI/ML model training API test cases .....109 -- 20.1 Conformance test cases for rApp .....109 -- 20.1.1 General.....109 -- 20.1.2 AI/ML model training API as API Consumer test scenario.....109 -- 20.2 Conformance test cases for SMO/Non-RT RIC framework.....111 -- 20.2.1 General.....111 -- 20.2.2 AI/ML model training API as API Producer test scenario.....112 -- 21 AI/ML workflow AI/ML model deployment API test cases.....115 -- 21.1 Conformance test cases for rApp .....115 -- 21.1.1 General.....115 -- 21.1.2 AI/ML model deployment API as API Consumer test scenario .....115 -- 21.2 Conformance test cases for SMO/Non-RT RIC framework.....116 -- 21.2.1 General.....116 -- 21.2.2 AI/ML model deployment API as API Producer test scenario .....116 -- Annex (informative): Change history.....119 - -# --- Foreword - -This Technical Specification (TS) has been produced by WG2 of the O-RAN ALLIANCE. It is part of a TS-family covering the WG2: R1 Interface Specifications. - -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 - -The purpose of the present document is to specify conformance and interoperability test cases for the R1 interface. Test cases and methodology for the R1 Service Consumer and R1 Service Producer, are separately specified. - -The present document contains R1 test cases for conformance testing and interoperability testing. For each specified test case, cover the entrance criteria, procedure and expected result. The test cases are defined based on the procedures, interface and functional requirements as specified in the R1 specifications series for which the test cases are used to validate conformance and interoperability. - -# --- 1 Scope - -The present document specifies test cases for conformance testing and interoperability testing of the rApps and R1 services over R1 interface. - -# --- 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.WG2.TS.R1GAP: "R1 General Aspects and Principles"("R1GAP"). -- [2] O-RAN.WG2.TS.R1UCR: "R1 Use Cases and Requirements"("R1UCR"). -- [3] O-RAN.WG2.TS.R1TP: "Transport Protocols for R1 services"("R1TP"). -- [4] O-RAN.WG2.TS.R1AP: "Application Protocols for R1 services"("R1AP"). -- [5] O-RAN.WG2.TS.Non-RT-RIC-ARCH: "Non-RT RIC: Architecture"("Non-RT RIC ARCH"). - -## 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 R1GAP [1], R1UCR [2], R1TP [3] apply. - -## 3.2 Symbols - -Void - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given in R1GAP [1], R1UCR [2], R1TP [3] apply. - -# --- 4 Test methodology - -## 4.1 General - -This clause describes the methodology for conformance and interoperability testing of rApps and SMO/Non-Real Time RIC framework over R1 interface. - -For conformance tests, simulators are used for testing R1 procedures. These simulators will have capability of generating HTTP requests and responses. There will be flexibility in configuring URI, headers and body for these HTTP requests and responses to enable creation of various test cases. - -For interoperability tests, devices under tests are rApps and SMO/Non-RT RIC framework that are defined in the Non-RT RIC architecture specification [5], these devices are brought to operation by connecting to appropriate real or simulated devices. - -## 4.2 Conformance testing of rApps - -### 4.2.1 General - -For conformance testing of rApps, rApp is the device under test and SMO/Non-RT RIC framework is the test simulator. - -The present document specifies conformance tests for API Consumer and API Producer functionality as specified in R1AP [4]. - -### 4.2.2 Test configuration - -#### 4.2.2.1 Overview - -The test configuration for R1 conformance testing of rApp is illustrated in figure 4.2.2.1-1. For testing of rApp over R1 interface, the rApp is onboarded and instantiated in the cloud environment of the test simulator. - -![Figure 4.2.2.1-1: Illustration of R1 conformance testing of rApps. The diagram shows a 'DUT' (Device Under Test) box containing an 'rApp'. The 'rApp' is connected via an 'R1' interface to a 'Test simulator' box. The 'Test simulator' box contains several functional blocks: 'O-cloud functionality', 'SMO/Non-RT RIC framework functionality', 'Near-RT RIC functionality', 'UEs', 'E2 node functionality', and '4G/5G Core functionality'. Connections are as follows: 'O-cloud functionality' connects to 'SMO/Non-RT RIC framework functionality' via an 'O2' interface; 'SMO/Non-RT RIC framework functionality' connects to 'Near-RT RIC functionality' via an 'A1' interface; 'UEs' connect to 'SMO/Non-RT RIC framework functionality' via an 'O1' interface; 'E2 node functionality' connects to 'SMO/Non-RT RIC framework functionality' via an 'O1' interface and to '4G/5G Core functionality' via an 'E2' interface.](990567efebf979be51f56d1150012c9d_img.jpg) - -Figure 4.2.2.1-1: Illustration of R1 conformance testing of rApps. The diagram shows a 'DUT' (Device Under Test) box containing an 'rApp'. The 'rApp' is connected via an 'R1' interface to a 'Test simulator' box. The 'Test simulator' box contains several functional blocks: 'O-cloud functionality', 'SMO/Non-RT RIC framework functionality', 'Near-RT RIC functionality', 'UEs', 'E2 node functionality', and '4G/5G Core functionality'. Connections are as follows: 'O-cloud functionality' connects to 'SMO/Non-RT RIC framework functionality' via an 'O2' interface; 'SMO/Non-RT RIC framework functionality' connects to 'Near-RT RIC functionality' via an 'A1' interface; 'UEs' connect to 'SMO/Non-RT RIC framework functionality' via an 'O1' interface; 'E2 node functionality' connects to 'SMO/Non-RT RIC framework functionality' via an 'O1' interface and to '4G/5G Core functionality' via an 'E2' interface. - -**Figure 4.2.2.1-1: Illustration of R1 conformance testing of rApps.** - -#### 4.2.2.2 Device under test rApps - -For enabling conformance testing, rApp has implemented API Consumer and/or API Producer functionality and the procedures as specified in R1AP [4] that are required to perform testing of the applicable R1 service test cases. - -#### 4.2.2.3 Test simulator - -For enabling conformance testing, the test simulator has implemented API Producer and/or API Consumer functionality, have HTTP Client and HTTP Server capabilities, and have flexibility to generate, receive, and validate HTTP messages for all the R1 procedures. The test simulator logs all message content during the testing. - -As illustrated in figure 4.2.2.1-1, test simulator has all the capabilities required to execute the conformance testing of an rApp. For example, the test simulator has the capabilities to simulate the functionality of A1, O1, and O2 in a cloud environment. - -## 4.3 Conformance testing of SMO/Non-RT RIC framework - -### 4.3.1 General - -For conformance testing of SMO/Non-RT RIC framework, SMO/Non-RT RIC framework is the device under test and rApp is the test simulator. - -The present document specifies conformance tests for API Consumer and API Producer functionality as specified in R1AP [4]. - -### 4.3.2 Test configuration - -#### 4.3.2.1 Overview - -The test configuration for R1 conformance testing of SMO/Non-RT RIC framework is illustrated in figure 4.3.2.1-1. - -![Diagram illustrating R1 conformance testing of Non-RT RIC framework. The diagram shows a 'DUT' (Device Under Test) box containing the 'SMO/Non-RT RIC framework'. Below this, several interfaces are labeled: O2, O1, O1, A1, and R1. The O2 interface connects to 'O-cloud functionality'. The first O1 interface connects to 'Near-RT RIC functionality'. The second O1 interface connects to 'rApp(s)'. The A1 interface connects to 'E2 node functionality'. The R1 interface connects to '4G/5G Core functionality'. Below 'Near-RT RIC functionality' is an 'E2' interface connecting to 'E2 node functionality'. 'UEs' (User Equipment) are connected to 'E2 node functionality'. The entire setup is labeled 'Test simulator' at the bottom.](562f471e8153729557e6a4ee6343c32c_img.jpg) - -Diagram illustrating R1 conformance testing of Non-RT RIC framework. The diagram shows a 'DUT' (Device Under Test) box containing the 'SMO/Non-RT RIC framework'. Below this, several interfaces are labeled: O2, O1, O1, A1, and R1. The O2 interface connects to 'O-cloud functionality'. The first O1 interface connects to 'Near-RT RIC functionality'. The second O1 interface connects to 'rApp(s)'. The A1 interface connects to 'E2 node functionality'. The R1 interface connects to '4G/5G Core functionality'. Below 'Near-RT RIC functionality' is an 'E2' interface connecting to 'E2 node functionality'. 'UEs' (User Equipment) are connected to 'E2 node functionality'. The entire setup is labeled 'Test simulator' at the bottom. - -Figure 4.3.2.1-1: Illustration of R1 conformance testing of Non-RT RIC framework. - -#### 4.3.2.2 Device under test (SMO/Non-RT RIC Framework) - -For enabling conformance testing, the SMO/Non-RT RIC framework has implemented API Producer and/or API Consumer functionality, and the procedures specified in R1AP [4], that are required to perform testing of the applicable test cases. - -#### 4.3.2.3 Test simulator - -For enabling conformance testing, the test simulator rApp(s) has both API Producer and/or API Consumer and HTTP Server capabilities and have flexibility to generate, receive and validate HTTP messages for all the R1 procedures. - -As illustrated in figure 4.3.2.1-1, test simulator has all the capabilities required to execute the conformance testing of an SMO/Non-RT RIC framework. For example, the test simulator has the capabilities to simulate the functionality of A1, O1, and O2. - -# 5 SME Service Registration service test cases - -## 5.1 Conformance test cases for rApp - -### 5.1.1 General - -#### 5.1.1.1 Device under test requirements - -The rApp that acts as Device Under Test (DUT) in these test scenarios, the requirements on the DUT for these tests are that it can handle the SME service registration service, and the purpose of the test scenarios is to validate that it confirms API Consumer functionality as specified in R1AP [4], clause 6.1.4. - -#### 5.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance API Producer functionality as specified in R1AP [4], clause 6.1.4. - -### 5.1.2 Register service API as API Consumer test scenario - -#### 5.1.2.1 Register service (positive case) - -##### 5.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the Register service API as specified in R1AP [4], clause 6.1.4.1. The expected outcome is successful validation of the request from the DUT. - -##### 5.1.2.1.2 Test entrance criteria - -The DUT has functionality to initiate the Register service procedure as defined in R1GAP [1], clause 5.1.3.2. - -NOTE: The DUT provides the service API description as defined in R1AP [4], clause A.2.1.3. The service being registered can be a standard or non-standard R1 service. - -##### 5.1.2.1.3 Test methodology - -###### 5.1.2.1.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 5.1.2.1.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to register a service that it produces. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 6.1.5.2. -- b) The HTTP request is a POST operation. -- c) The HTTP request message content includes rApp identifier and the service API description conforms to the schema as specified in R1AP [4], clause 6.1.4.1. - -Step 4. The test simulator generates the service API identifier and constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 6.1.4.1.1. - -##### 5.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 5.1.2.2 Update registered service (positive case) - -##### 5.1.2.2.1 Test description and applicability - -The purpose of this test case is to test the Update registered service API as specified in R1AP [4], clause 6.1.4.2. The expected outcome is successful validation of the request from the DUT. - -##### 5.1.2.2.2 Test entrance criteria - -- a) The DUT has functionality to initiate the Update registered service procedure as defined in R1GAP [1], clause 5.1.3.2. - -- b) A service API registration exists in test simulator and the serviceApiId and the apfId are known to DUT. -- c) The schema of the ServiceAPIDescription used for this test are available and used in DUT to formulate the Update registered service request, and in test simulator to validate the request. - -NOTE: The DUT provides the ServiceApiDescription as defined in R1AP [4], clause A.2.1.3. The service being updated can be a standard or non-standard R1 service. - -##### 5.1.2.2.3 Test methodology - -###### 5.1.2.2.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 5.1.2.2.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to update a registered service API identified by the apfId and the serviceApiId. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 6.1.5.3. -- b) The HTTP request is a PUT operation. -- c) The apfId and the serviceApiId in the URI match the service API being updated. -- d) The HTTP request message body contains the ServiceAPIDescription of the service API to be updated and conforms to the schema as specified in R1AP [4], clause 6.1.4.2. - -Step 4. The test simulator updates the resource, and a representation of the updated resource shall be returned in the response body the appropriate HTTP response as specified in R1AP [4], clause 6.1.5.3.1.1. - -##### 5.1.2.2.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 5.1.2.3 Deregister service (positive case) - -##### 5.1.2.3.1 Test description and applicability - -The purpose of this test case is to test the Deregister service API as specified in R1AP [4], clause 6.1.4.3. The expected outcome is successful validation of the request from the DUT. - -##### 5.1.2.3.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Deregister service procedure as defined in R1GAP [1], clause 5.1.3.2. -- 2) A service API registration exists in test simulator and the serviceApiId and the apfId are known to DUT. - -##### 5.1.2.3.3 Test methodology - -###### 5.1.2.3.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 5.1.2.3.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to deregister a service API identified by the apfID and the serviceApiId. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 6.1.5.3. -- b) The HTTP request is a DELETE operation. -- c) The serviceApiId and apfId in the URI match the service being deleted. -- d) The message body is empty. - -Step 4. The test simulator generated the appropriate HTTP response as specified in R1AP [4], clause 6.1.5.3.1.2. - -##### 5.1.2.3.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 5.1.2.4 Query registered service (positive case) - -##### 5.1.2.4.1 Test description and applicability - -The purpose of this test case is to test the Query service APIs as specified in R1AP [4], clause 6.1.4.5. The expected outcome is successful validation of the request from the DUT. - -##### 5.1.2.4.2 Test entrance criteria - -- 1) The DUT has functionality to initiate Query registered service procedure. -- 2) A set of service API registrations exist in the test simulator and the apfId is known to DUT. - -##### 5.1.2.4.3 Test methodology - -###### 5.1.2.4.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 5.1.2.4.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query service APIs that are registered by the apfId. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 6.1.5.3. -- b) The HTTP request is a GET operation. -- c) The apfId in the URI match the service APIs being queried. -- d) The message body is empty. - -Step 4. The test simulator generated the appropriate HTTP response as specified in R1AP [4], clause 6.1.5.2.1.2 - -##### 5.1.2.4.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 5.1.5.5 Partially updated registered service (positive case) - -##### 5.1.5.5.1 Test description and applicability - -The purpose of this test case is to test the partially update registered service API as specified in R1AP [4], clause 6.1.4.4. The expected outcome is successful validation of the request from the DUT. - -##### 5.1.5.5.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Partially update registered service procedure as defined in R1GAP [1], clause 5.1.3.2. -- 2) A service API registration exists in test simulator and the serviceApiId and the apfId are known to DUT -- 3) The schema of the ServiceAPIDescriptionPatch used for this test are available and used in DUT to formulate the Partially update registered service request, and in test simulator to validate the request. - -NOTE: The DUT provides the ServiceApiDescriptionPatch as defined in R1AP [4]. The service being updated can be a standard or non-standard R1 service. - -##### 5.1.5.5.3 Test methodology - -###### 5.1.5.5.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 5.1.5.5.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to partially update a registered service API identified by the apfId and the serviceApiId. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 6.1.5.3. -- b) The HTTP request is a PATCH operation. -- c) The apfId and the serviceApiId in the URI match the service API being updated. -- d) The HTTP request message body contains the ServiceAPIDescriptionPatch of the service API to be updated and conforms to the schema as specified in R1AP [4], clause 6.1.4.4. - -Step 4. The test simulator updates the resource, and a representation of the partially updated resource shall be returned in the response body the appropriate HTTP response as specified in R1AP [4], clause 6.1.5.3.1.3. - -##### 5.1.5.5.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 5.2 Conformance test cases for SMO/Non-RT RIC framework - -### 5.2.1 General - -#### 5.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as Device Under Test (DUT) in these test scenarios, the requirements on the DUT for these tests are that it can handle the SME service registration service, and the purpose of the test scenarios is to validate that it confirms API Producer functionality as specified in R1AP [4], clause 6.1.4. - -#### 5.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as specified in section 4.3.2. In addition, it has the following capabilities: - -- 1) Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- 2) Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to API Producer functionality as specified in R1AP [4], clause 6.1.4. - -### 5.2.2 Register service API as API Producer test scenario - -#### 5.2.2.1 Register service (positive case) - -##### 5.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the Register service API as specified in R1AP [4], clause 6.1.4.1. The expected outcome is successful validation of the response from the DUT. - -##### 5.2.2.1.2 Test entrance criteria - -The test simulator has functionality to initiate the Register service procedure as defined in R1GAP [1], clause 5.1.3.2. - -NOTE: The test simulator provides the service API description as defined in R1AP [4], clause A.2.1.3. The service being registered can be a standard or non-standard R1 service. - -##### 5.2.2.1.3 Test methodology - -###### 5.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -###### 5.2.2.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to register a service that it produces. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a POST request. -- b) The URI conforms to the format specified in R1AP [4], clause 6.1.5.2.1.1. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 6.1.4.1. - -Step 4. The DUT generates the service API identifier and constructs the URI for the created resource. - -Step 5. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 6.1.4.1.1. - -Step 6. At the test simulator the contents of the received HTTP response is recorded. - -Step 7. The test simulator does the following validation: - -- a) The HTTP response message content includes the information as specified in R1AP [4], clause 6.1.4.1, and the Location header will be present. -- b) The URI confirms to the format specified in R1AP [4], clause 6.1.5.2. - -##### 5.2.2.1.4 Expected result - -The test is considered passed if Step 7 validation has passed. - -#### 5.2.2.2 Update registered service (positive case) - -##### 5.2.2.2.1 Test description and applicability - -The purpose of this test case is to test the Update registered service API as specified in R1AP [4], clause 6.1.4.2. The expected outcome is successful validation of the response from the DUT. - -##### 5.2.2.2.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Update registered service procedure as defined in RIGAP [1], clause 5.1.3.2. -- 2) A service API registration exists in DUT and the serviceApiId and the apfId are known to test simulator. -- 3) The schema of the ServiceAPIDescription used for this test are available and used in test simulator to formulate the Update registered service request, and in the test simulator to validate the request. - -NOTE: The test simulator provides the ServiceApiDescription as defined in R1AP [4], clause A.2.1.3. The service being updated can be a standard or non-standard R1 service. - -##### 5.2.2.2.3 Test methodology - -###### 5.2.2.2.3.1 Initial conditions - -The DUT as API Producer is ready and available to receive HTTP requests from the test simulator. - -###### 5.2.2.2.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to update a registered service API identified by the apfId and the serviceApiId. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 6.1.5.3. -- b) The HTTP request is a PUT operation. -- c) The apfId and the serviceApiId in the URI match the service API being updated. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 6.1.4.2. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 6.1.4.2.1. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The HTTP response message content includes the information as specified in R1AP [4], clause 6.1.4.2, and the Location header will be present. - -##### 5.2.2.2.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -#### 5.2.2.3 Deregister service (positive case) - -##### 5.2.2.3.1 Test description and applicability - -The purpose of this test case is to test the Deregister service API as specified in R1AP [4], clause 6.1.4.3. The expected outcome is successful validation of the response from the DUT. - -##### 5.2.2.3.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Deregister service procedure as defined in R1GAP [1], clause 5.1.3.2. -- 2) A service API registration exists in DUT and the serviceApiId and the appId are known to test simulator. - -##### 5.2.2.3.3 Test methodology - -###### 5.2.2.3.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the test simulator. - -###### 5.2.2.3.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to deregister a service API identified by the appId and the serviceApiId. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a DELETE request. -- b) The URI format as specified in R1AP [4], clause 6.1.5.3.1.2. -- c) The HTTP request content includes the information as specified in R1AP [4], clause 6.1.4.3.1. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 6.1.4.3.1. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 6.1.5.3. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 6.1.4.3.1. -- c) The message body is empty. - -##### 5.2.2.3.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -#### 5.2.2.4 Query registered service (positive case) - -##### 5.2.2.4.1 Test description and applicability - -The purpose of this test case is to test the Query service APIs as specified in R1AP [4], clause 6.1.4.5. The expected outcome is successful validation of the response from the DUT. - -##### 5.2.2.4.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate Query registered service procedure as defined in R1GAP [1], clause 5.1.3.2. -- 2) A set of service API registrations exist in the DUT and the apfId is known to test simulator. - -##### 5.2.2.4.3 Test methodology - -###### 5.2.2.4.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -###### 5.2.2.4.3.2 Procedure - -- Step 1. The test simulator as an API Consumer initiates a HTTP request to query service APIs that are registered by the apfId. -- Step 2. The DUT receives the HTTP request. -- Step 3. The DUT does the following validation: - - a) The HTTP request is a GET request. - - b) The URI format as specified in R1AP [4]R1AP [4], clause 6.1.5.2.1.2. - - c) The HTTP request message content includes the information as specified in R1AP [4], clause 6.1.4.5.1 -- Step 4. The DUT initiates a HTTP Response. -- Step 5. At the test simulator the contents of the received HTTP response is recorded. -- Step 6. The test simulator does the following validation: - - a) The URI conforms to the format specified in R1AP [4], clause 6.1.5.2. - - b) The HTTP response message content includes the information as specified in R1AP [4], clause 6.1.4.5.1. - -##### 5.2.2.4.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -#### 5.2.5.5 Partially update registered service (positive case) - -##### 5.2.5.5.1 Test description and applicability - -The purpose of this test case is to test the partially update registered service API as specified in R1AP [4], clause 6.1.4.4. The expected outcome is successful validation of the response from the DUT. - -##### 5.2.5.5.2 Test entrance criteria - -- 3) The test simulator has functionality to initiate the Partially update registered service procedure as defined in R1GAP [1], clause 5.1.3.2. - -- 4) A service API registration exists in DUT and the serviceApiId and the apfId are known to test simulator -- 5) The schema of the ServiceAPIDescriptionPatch used for this test are available and used in test simulator to formulate the Partially update registered service request, and in test simulator to validate the request. - -NOTE: The test simulator provides the ServiceApiDescriptionPatch as defined in R1AP [4]. The service being updated can be a standard or non-standard R1 service. - -##### 5.2.5.5.3 Test methodology - -###### 5.2.5.5.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -###### 5.2.5.5.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to partially update a registered service API identified by the apfId and the serviceApiId. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a PATCH request. -- b) The URI format as specified in R1AP [4], clause 6.1.5.3.1.3. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 6.1.4.4. - -Step 4. The DUT initiates a HTTP Response. - -Step 5. At the test simulator the contents of the received HTTP request is recorded. - -Step 6. The test simulator does the following validation: - -- a) The HTTP response message content includes the information as specified in R1AP [4], clause 6.1.4.4, and the Location header will be present. - -##### 5.2.5.5.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -# --- 6 SME Service Discovery service test cases - -## 6.1 Conformance test cases for rApp - -### 6.1.1 General - -#### 6.1.1.1 Device under test requirements - -The rApp that acts as Device Under Test (DUT) in these test scenarios, the requirements on the DUT for these tests are that it can handle the SME service discovery service, and the purpose of the test scenarios is to validate that it conforms to the Service discovery API specified in R1AP [4], clause 6.2.4. - -#### 6.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance API Producer functionality as specified in R1AP [4], clause 6.2.4. - -### 6.1.2 Discover service API as API Consumer test scenario - -#### 6.1.2.1 Query service (positive case) - -##### 6.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the Query service APIs operation as specified in R1AP [4], clause 6.2.4.1. The expected outcome is successful validation of the request from the DUT. - -##### 6.1.2.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Discover services procedure. -- 2) A set of service API registrations exist in the test simulator. - -##### 6.1.2.1.3 Test methodology - -###### 6.1.2.1.3.1 Initial conditions - -- 1) The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 6.1.2.1.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query service APIs. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 6.2.5.2. -- b) The HTTP request is a GET operation. -- c) The message body is empty. - -Step 4. The test simulator generated the appropriate HTTP response as specified in R1AP [4], clause 6.2.5.2.1.1. - -NOTE: Presence or validation of optional filter parameters is not used to determine validation on this test. - -##### 6.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 6.2 Conformance test cases for SMO/Non-RT RIC framework - -### 6.2.1 General - -#### 6.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as Device Under Test (DUT) in these test scenarios, the requirements on the DUT for these tests are that it can handle the SME service discovery service, and the purpose of the test scenarios is to validate that it conforms to the Service discovery API specified in R1AP [4], clause 6.2.4. - -#### 6.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as specified in section 4.3.2. In addition, it has the following capabilities: - -- 1) Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- 2) Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to API Producer functionality as specified in R1AP [1], clause 6.2.4. - -### 6.2.2 Service discovery API as API Producer test scenario - -#### 6.2.2.1 Query service (positive case) - -##### 6.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the Query service APIs as specified in R1AP [1] clause 6.2.4.1. The expected outcome is successful validation of the response from the DUT. - -##### 6.2.2.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Discover services procedure. -- 2) A set of service API registrations exist in the test simulator. - -##### 6.2.2.1.3 Test methodology - -###### 6.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -###### 6.2.2.1.3.2 Procedure - -- Step 1. The test simulator as an API Consumer initiates a HTTP request to query service APIs that are registered by the apflId. -- Step 2. The DUT receives the HTTP request. -- Step 3. The DUT does the following validation: - - a) The HTTP request is a GET request. - - b) The URI conforms to the format as specified in R1AP[4], clause 6.2.5.2. - - c) The HTTP request message content includes the information as specified in R1AP [4], clause 6.2.4.1. - -Step 4. The DUT initiates a HTTP Response. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP[4], clause 6.2.5.2. -- b) The HTTP response message content includes the information as specified in R1AP[4], clause 6.2.4.1. - -##### 6.2.2.1.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -# --- 7 SME Service Subscription service test cases - -## 7.1 Conformance test cases for rApp - -### 7.1.1 General - -#### 7.1.1.1 Device under test requirements - -The rApp that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the SME service subscription service, and the purpose of the test scenarios is to validate that it conforms to the API Consumer functionality as specified in R1AP [4], clause 6.3.4. - -#### 7.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Consumer functionality as specified in R1AP[4], clause 6.3.4. - -### 7.1.2 Service events subscription API as API Consumer test scenario - -#### 7.1.2.1 Subscribe service events (positive case) - -##### 7.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the Events subscription service API as specified in R1AP[4], clause 6.3.4.1. The expected outcome is successful validation of the request from the DUT. - -##### 7.1.2.1.2 Test entrance criteria - -The DUT has functionality to initiate the Subscribe service availability procedure as defined in R1GAP [1], clause 5.1.4. - -NOTE: The DUT provides the events subscription structure as defined in R1AP[4], clause 6.3.3. The service event being subscribed to can be a standard or non-standard R1 service event. - -##### 7.1.2.1.3 Test methodology - -###### 7.1.2.1.3.1 Initial conditions - -- 1) The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. -- 2) The subscriberId is known to DUT. - -###### 7.1.2.1.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to subscribe to service event notifications. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP[4], clause 6.3.5.2. -- b) The HTTP request is a POST operation. -- c) The HTTP request message content includes the information as specified in R1AP[4], clause 6.3.4.1.1. - -Step 4. The test simulator generates the subscription identifier and constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP[4], clause 6.3.4.1.1. - -##### 7.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 7.1.2.2 Unsubscribe service events (positive case) - -##### 7.1.2.2.1 Test description and applicability - -The purpose of this test case is to test the unsubscribe service API as specified in R1AP[4], clause 6.3.4.2. The expected outcome is successful validation of the request from the DUT. - -##### 7.1.2.2.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Unsubscribe service availability procedure as defined in R1GAP [1], clause 5.1.4. -- 2) A subscription exists and the subscriberId and subscriptionId are known to the DUT. - -##### 7.1.2.2.3 Test methodology - -###### 7.1.2.2.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 7.1.2.2.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to unsubscribe from service event notifications identified by the subscriberId and subscriptionId. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP[4], clause 6.3.5.3. - -- b) The HTTP request is a DELETE operation. -- c) The subscriberId and subscriptionId in the URI match the service events being deleted. -- d) The message body is empty. - -Step 4. The test simulator generated the appropriate HTTP response as specified in R1AP[4], clause 6.3.5.3.1.1. - -##### 7.1.2.2.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 7.2 Conformance test cases for SMO/Non-RT RIC framework - -### 7.2.1 General - -#### 7.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the SME service events subscription service, and the purpose of the test scenarios is to validate that it conforms to the API Producer functionality as specified in R1AP [4], clause 6.3.4. - -#### 7.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as specified in section 4.3.2. In addition, it has the following capabilities: - -- 1) Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- 2) Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Producer functionality as specified in R1AP[4], clause 6.3.4. - -### 7.2.2 Service events subscription API as API Producer test scenario - -#### 7.2.2.1 Service events subscription (positive case) - -##### 7.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the Events subscription service API as specified in R1AP[4], clause 6.3.4.1. The expected outcome is successful validation of the response from the DUT. - -##### 7.2.2.1.2 Test entrance criteria - -The test simulator has functionality to initiate the Subscribe service availability procedure as defined in R1GAP [1], clause 5.1.4. - -NOTE: The test simulator provides the events subscription structure as defined in R1AP[4], clause 6.3.3. The service being subscribed to can be a standard or non-standard R1 service. - -##### 7.2.2.1.3 Test methodology - -###### 7.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -###### 7.2.2.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to subscribe to service event notifications. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a POST request. -- b) The URI conforms to the format specified in R1AP[4], clause 6.3.5.2.1.1. -- c) The HTTP request message content includes the information as specified in R1AP[4], clause 6.3.4.1.1. - -Step 4. The DUT generates the subscription identifier and constructs the URI for the created resource. - -Step 5. The DUT sends the appropriate HTTP response as specified in R1AP[4], clause 6.3.4.1.1. - -Step 6. At the test simulator the contents of the received HTTP response is recorded. - -Step 7. The test simulator does the following validation: - -- a) The HTTP response message content includes the information as specified in R1AP[4], clause 6.3.4.1.1, and the Location header will be present. -- b) The URI conforms to the format specified in R1AP[4], clause 6.3.5.2. - -##### 7.2.2.1.4 Expected result - -The test is considered passed if Step 7 validation has passed. - -#### 7.2.2.2 Unsubscribe service events (positive case) - -##### 7.2.2.2.1 Test description and applicability - -The purpose of this test case is to test the Unsubscribe service API as specified in R1AP[4], clause 6.3.4.2. The expected outcome is successful validation of the response from the DUT. - -##### 7.2.2.2.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Unsubscribe service availability procedure as defined in R1GAP [1], clause 5.1.4. -- 2) A subscription exists and the subscriberId and subscriptionId are known to the test simulator. - -##### 7.2.2.2.3 Test methodology - -###### 7.2.2.2.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -###### 7.2.2.2.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to unsubscribe from service event notifications identified by the subscriberId and subscriptionId. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a DELETE request. - -- b) The URI format as specified in R1AP [4], clause 6.3.5.3.1.1. -- c) The subscriberId and subscriptionId in the URI match the service events being deleted. -- d) The message body is empty. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP[4] , clause 6.3.4.2.1. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The return code is "204 No content". -- b) The response message body is empty. - -##### 7.2.2.2.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -#### 7.2.2.3 Notification service (positive case) - -##### 7.2.2.3.1 Test description and applicability - -The purpose of this test case is to test the notification service API as specified in R1AP[4], clause 6.3.4.3. The expected outcome is successful validation of the event notification from the DUT. - -##### 7.2.2.3.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Notify service availability changes procedure as defined in R1GAP [1], clause 5.1.4. -- 2) A subscription exists in the DUT. - -##### 7.2.2.3.3 Test methodology - -###### 7.2.2.3.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -###### 7.2.2.3.3.2 Procedure - -Step 1. The DUT as an API producer initiates the sending of a HTTP POST request. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The HTTP request is a POST operation. -- b) The callback URI matches the URI provided in the subscription. - -##### 7.2.2.3.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -# 8 DME Data registration service test cases - -## 8.1 Conformance test cases for rApp - -### 8.1.1 General - -#### 8.1.1.1 Device under test requirements - -The rApp that acts as DUT in the test scenarios, the requirements on the DUT for these tests are that it can handle the Data registration service, and the purpose of the test scenarios is to validate that it conforms to the API Consumer functionality as specified in R1AP [4], clause 7.1.4. - -#### 8.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Consumer functionality as specified in R1AP [4], clause 7.1.4. - -### 8.1.2 Data registration API as API consumer test scenario - -#### 8.1.2.1 Register DME type (positive case) - -##### 8.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the Register DME type in Data registration API as specified in R1AP [4], clause 7.1.4.1. The expected outcome is successful validation of the request from the DUT. - -##### 8.1.2.1.2 Test entrance criteria - -The DUT has functionality to initiate the Register DME type procedure as defined in R1GAP [1], clause 5.2.2. - -NOTE: The DUT provides the service API description as defined in R1AP [4], clause A.2.1.3. The service being registered can be a standard or non-standard R1 service. - -##### 8.1.2.1.3 Test methodology - -###### 8.1.2.1.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 8.1.2.1.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to register a DmeTypeRelatedCapabilities. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 7.1.5.2.2. -- b) The HTTP request is a POST operation. -- c) The HTTP request message content includes DmeTypeRelatedCapabilities as specified in R1AP [4], clause 7.1.4. - -Step 4. The test simulator generates the registrationId and constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.1.5.2.3.1. - -##### 8.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 8.1.2.2 Deregister DME type (positive case) - -##### 8.1.2.2.1 Test description and applicability - -The purpose of this test case is to test the Deregister DME type in Data registration API as specified in R1AP [4], clause 7.1.4.2. The expected outcome is successful validation of the request from the DUT. - -##### 8.1.2.2.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Deregister DME type procedure as defined in R1GAP [1], clause 5.2.2.2. -- 2) A DME type exists in test simulator and the registrationId is known to the DUT. - -##### 8.1.2.2.3 Test methodology - -###### 8.1.2.2.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 8.1.2.2.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to Deregister DME type. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.1.5.3.2. -- b) The HTTP request is a DELETE operation. -- c) The registrationId in the URI match the DME type being deregistered. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.1.5.3.3. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.1.5.3.3 - -##### 8.1.2.2.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 8.1.2.3 Query DME type (positive case) - -##### 8.1.2.3.1 Test description and applicability - -The purpose of this test case is to test the Query DME type in Data registration API as specified in R1AP [4], clause 7.1.4.4. The expected outcome is successful validation of the request from the DUT. - -##### 8.1.2.3.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the query DME type registration procedure as defined in R1GAP [1], clause 5.2.2.2. -- 2) A DME type exists in test simulator and the registrationId is known to the DUT. - -##### 8.1.2.3.3 Test methodology - -###### 8.1.2.3.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 8.1.2.3.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query a DME type. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.1.5.3.2. -- b) The HTTP request is a GET operation. -- c) The registrationId in the URI match the DME type being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.1.5.3.3. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.1.5.3.3. - -##### 8.1.2.3.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 8.1.2.4 Update DME type (positive case) - -##### 8.1.2.4.1 Test description and applicability - -The purpose of this test case is to test the Update DME type in Data registration API as specified in R1AP [4], clause 7.1.4.3. The expected outcome is successful validation of the request from the DUT. - -##### 8.1.2.4.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Update DME type registration procedure as defined in R1GAP [1], clause 5.2.2.2. -- 2) A DME type exists in test simulator and the registrationId and DmeTypeRelatedCapabilities are known to the DUT. - -##### 8.1.2.4.3 Test methodology - -###### 8.1.2.4.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 8.1.2.4.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to update a DME type identified by the `registrationId` and `DmeTypeRelatedCapabilities`. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 7.1.5.3.2. -- b) The HTTP request is a PUT operation. -- c) The `registrationId` and `DmeTypeRelatedCapabilities` in the URI match the DME type being updated. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.1.5.3.3. - -Step 4. The test simulator updates the resource, and a representation of the updated resource shall be returned in the response body the appropriate HTTP response as specified in R1AP [4], clause 7.1.5.3.3. - -##### 8.1.2.4.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 8.1.2.5 Query data subscription information (positive case) - -##### 8.1.2.5.1 Test description and applicability - -The purpose of this test case is to test the Query data jobs in the Data registration API as specified in R1AP [4], clause 7.1.4.5. The expected outcome is successful validation of the request from the DUT. - -##### 8.1.2.5.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Query data subscription information procedure as defined in R1GAP [1], clause 5.2.2. -- 2) A of set of data jobs exist in the test simulator and the `registrationId` is known to the DUT - -##### 8.1.2.5.3 Test methodology - -###### 8.1.2.5.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 8.1.2.5.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query a set of data jobs. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.1.5.4.2. - -- b) The HTTP request is a GET operation. -- c) The registrationId in the URI match the DME type being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.1.4.5.1. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.1.4.5.1 - -##### 8.1.2.5.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 8.2 Conformance test cases for SMO/Non-RT RIC framework - -### 8.2.1 General - -#### 8.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the Data registration service, and the purpose of the test scenarios is to validate that it conforms to the API Producer functionality as specified in R1AP [4], clause 7.1.4. - -#### 8.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a rApp. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Producer functionality as specified in R1AP [4], clause 7.1.4. - -### 8.2.2 Data registration API as API Producer test scenario - -#### 8.2.2.1 Register DME type (positive case) - -##### 8.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the Register DME type in Data registration API as specified in R1AP [4], clause 7.1.4.1. The expected outcome is successful validation of the request from the DUT. - -##### 8.2.2.1.2 Test entrance criteria - -The test simulator has functionality to initiate the Register DME type procedure as defined in R1GAP [1], clause 5.2.2. - -##### 8.2.2.1.3 Test methodology - -###### 8.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -###### 8.2.2.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to register a DmeTypeRelatedCapabilities. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a POST request. -- b) The URI conforms to the format specified in R1AP [4], clause 7.1.5.2.2. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.1.5.2.3.1. - -Step 4. The DUT generates the data job and constructs the URI for the created resource. - -Step 5. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.1.5.2.3.1. - -Step 6. At the test simulator the contents of the received HTTP response is recorded. - -Step 7. The test simulator does the following validation: - -- a) The HTTP response message content includes the information as specified in R1AP [4], clause 7.1.5.2.3.1, and the Location header will be present. -- b) The URI conforms to the format specified in R1AP [4], clause 7.1.5.2.2. - -##### 8.2.2.1.4 Expected result - -The test is considered passed if Step 7 validation has passed. - -#### 8.2.2.2 Deregister DME type (positive case) - -##### 8.2.2.2.1 Test description and applicability - -The purpose of this test case is to test the Deregister DME type in Data registration API as specified in R1AP [4], clause 7.1.4.2. The expected outcome is successful validation of the request from the DUT. - -##### 8.2.2.2.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Deregister DME type procedure as defined in R1GAP [1] clause 5.2.2.2. -- 2) A DME type exists in test simulator and the registrationId is known to the DUT. - -##### 8.2.2.2.3 Test methodology - -###### 8.2.2.2.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -###### 8.2.2.2.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to Deregister DME type. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.1.5.3.2. -- b) The HTTP request is a DELETE operation. - -- c) The registrationId in the URI match the DME type being deregistered. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.1.5.3.3. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.1.5.3.3. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 7.1.5.3.2. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 7.1.5.3.3. - -##### 8.2.2.2.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -#### 8.2.2.3 Query DME type (positive case) - -##### 8.2.2.3.1 Test description and applicability - -The purpose of this test case is to test the Query DME type in Data registration API as specified in R1AP [4], clause 7.1.4.4. The expected outcome is successful validation of the request from the DUT. - -##### 8.2.2.3.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the query DME type registration procedure as defined in R1GAP [1], clause 5.2.2.2. -- 2) A DME type exists in test simulator and the registrationId is known to the DUT. - -##### 8.2.2.3.3 Test methodology - -###### 8.2.2.3.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -###### 8.2.2.3.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to query a DME type. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.1.5.3.2. -- b) The HTTP request is a GET operation. -- c) The registrationId in the URI match the data job status being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.1.5.3.3. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.1.5.3.3. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.1.5.3.2. - -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 7.1.5.3.3. - -##### 8.2.2.3.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -#### 8.2.2.4 Update DME type (positive case) - -##### 8.2.2.4.1 Test description and applicability - -The purpose of this test case is to test the Update DME type in Data registration API as specified in R1AP [4], clause 7.1.4.3. The expected outcome is successful validation of the request from the DUT. - -##### 8.2.2.4.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Update DME type registration procedure as defined in R1GAP [1], clause 5.2.2.2 -- 2) A DME type exists in test simulator and the registrationId and DmeTypeRelatedCapabilities are known to the DUT - -##### 8.2.2.4.3 Test methodology - -###### 8.2.2.4.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -###### 8.2.2.4.3.2 Procedure - -- Step 1. The test simulator as an API Consumer initiates a HTTP request to update a DME type identified by the registrationId and DmeTypeRelatedCapabilities. -- Step 2. The DUT receives the HTTP request. -- Step 3. The DUT does the following validation: - - a) The HTTP request is a PUT request. - - b) The URI conforms to the format specified in R1AP [4], clause 7.1.5.3.2. - - c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.1.5.3.3. -- Step 4. The DUT generates the data job and constructs the URI for the created resource. -- Step 5. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.1.5.3.3. -- Step 6. At the test simulator the contents of the received HTTP response is recorded. -- Step 7. The test simulator does the following validation: - - a) The HTTP response message content includes the information as specified in R1AP [4], clause 7.1.5.3.3. - - b) The URI conforms to the format specified in R1AP [4], clause 7.1.5.3.2. - -##### 8.2.2.4.4 Expected result - -The test is considered passed if Step 7 validation has passed. - -#### 8.2.2.5 Query data subscription information (positive case) - -##### 8.2.2.5.1 Test description and applicability - -The purpose of this test case is to test the Query data jobs in the Data registration API as specified in R1AP [4], clause 7.1.4.5. The expected outcome is successful validation of the request from the DUT. - -##### 8.2.2.5.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Query data subscription information procedure as defined in R1GAP [1], clause 5.2.2. -- 2) A set of data jobs exist in the DUT and the registrationId is known to the test simulator - -##### 8.2.2.5.3 Test methodology - -###### 8.2.2.5.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -###### 8.2.2.5.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to query a set of data jobs. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.1.5.4.2. -- b) The HTTP request is a GET operation. -- c) The registrationId in the URI match the DME Type being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.1.4.5.1. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.1.4.5.1 - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.1.5.4.2 -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 7.1.4.5.1. - -##### 8.2.2.5.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -# 9 DME Data request service test cases - -## 9.1 Conformance test cases for rApp - -### 9.1.1 General - -#### 9.1.1.1 Device under test requirements - -The rApp that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the DME Data request service, and the purpose of the test scenarios is to validate that it conforms to the API Consumer functionality as specified in R1AP [4], clause 7.3.4. - -#### 9.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Consumer functionality as specified in R1AP [4], clause 7.3.4. - -### 9.1.2 Data access API as API Consumer test scenario - -#### 9.1.2.1 Create data job (positive case) - -##### 9.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the create data job API as specified in R1AP [4], clause 7.3.4.1. The expected outcome is successful validation of the request from the DUT. - -##### 9.1.2.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the request data procedure as defined in R1GAP [1], clause 5.2.4. -- 2) The DataJobInfo is known to the DUT. - -##### 9.1.2.1.3 Test methodology - -###### 9.1.2.1.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 9.1.2.1.3.2 Procedure - -- Step 1. The DUT as an API Consumer initiates a HTTP request to create a data job. -- Step 2. At the test simulator the contents of the received HTTP request is recorded. -- Step 3. The test simulator does the following validation: - - a) The URI conforms to the format specified in R1AP [4], clause 7.3.4.1. - -- b) The HTTP request is a POST operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.1. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [1], clause 7.3.4.1.1. - -##### 9.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 9.1.2.2 Cancel data job (positive case) - -##### 9.1.2.2.1 Test description and applicability - -The purpose of this test case is to test the Cancel data job API as specified in R1AP [4], clause 7.3.4.2. The expected outcome is successful validation of the request from the DUT. - -##### 9.1.2.2.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the cancel data request procedure as defined in R1GAP [1], clause 5.2.4. -- 2) A data job exists in test simulator and the dataJobId is known to the DUT. - -##### 9.1.2.2.3 Test methodology - -###### 9.1.2.2.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 9.1.2.2.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to cancel a data job. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.3. -- b) The HTTP request is a DELETE operation. -- c) The dataJobID in the URI match the data job being deleted. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.2. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [1], clause 7.3.4.2.1. - -##### 9.1.2.2.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 9.1.2.3 Query data job status (positive case) - -##### 9.1.2.3.1 Test description and applicability - -The purpose of this test case is to test the query data job status API as specified in R1AP [4], clause 7.3.4.6 The expected outcome is successful validation of the request from the DUT. - -##### 9.1.2.3.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the query data request status procedure as defined in RIGAP [1], clause 5.2.4. -- 2) A data job exists in test simulator and the dataJobId is known to the DUT. - -##### 9.1.2.3.3 Test methodology - -###### 9.1.2.3.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 9.1.2.3.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query a data job status. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.4.6.1. -- b) The HTTP request is a GET operation. -- c) The dataJobID in the URI match the data job being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.6.1. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.6.1. - -##### 9.1.2.3.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 9.2 Conformance test cases for SMO/Non-RT RIC framework - -### 9.2.1 General - -#### 9.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the DME Data request service, and the purpose of the test scenarios is to validate that it conforms to the API Producer functionality as specified in R1AP [4], clause 7.3.4. - -#### 9.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a rApp. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Producer functionality as specified in R1AP [4], clause 7.3.4. - -### 9.2.2 Data access API as API Producer test scenario - -#### 9.2.2.1 Create data job (positive case) - -##### 9.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the create data job API as specified in R1AP [4], clause 7.3.4.1. The expected outcome is successful validation of the request from the DUT. - -##### 9.2.2.1.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the request data procedure as defined in RIGAP [1], clause 5.2.4. -- 2) The DataJobInfo is known to the DUT - -##### 9.2.2.1.3 Test methodology - -###### 9.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -###### 9.2.2.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to create a data job. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a POST request. -- b) The URI conforms to the format specified in R1AP [4], clause 7.3.5.2.3.1. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.1. - -Step 4. The DUT generates the data job and constructs the URI for the created resource. - -Step 5. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.1. - -Step 6. At the test simulator the contents of the received HTTP response is recorded. - -Step 7. The test simulator does the following validation: - -- a) The HTTP response message content includes the information as specified in R1AP [4], clause 7.3.4.1, and the Location header will be present. -- b) The URI conforms to the format specified in R1AP [4], clause 7.3.5.3. - -##### 9.2.2.1.4 Expected result - -The test is considered passed if Step 7 validation has passed. - -#### 9.2.2.2 Cancel data job (positive case) - -##### 9.2.2.2.1 Test description and applicability - -The purpose of this test case is to test the Cancel data job API as specified in R1AP [4], clause 7.3.4.2. The expected outcome is successful validation of the request from the DUT. - -##### 9.2.2.2.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the cancel data request procedure as defined in R1GAP [1], clause 5.2.4. -- 2) A data job exists in DUT and the dataJobId is known to the test simulator. - -##### 9.2.2.2.3 Test methodology - -###### 9.2.2.2.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -###### 9.2.2.2.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to cancel a data job. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.3.3.1. -- b) The HTTP request is a DELETE operation. -- c) The dataJobID in the URI match the data job being deleted. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.2. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.2. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 7.3.5.3. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 7.3.4.2. - -##### 9.2.2.2.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -#### 9.2.2.3 Query data job status (positive case) - -##### 9.2.2.3.1 Test description and applicability - -The purpose of this test case is to test the query data job status API as specified in R1AP [4], clause 7.3.4.6 The expected outcome is successful validation of the request from the DUT. - -##### 9.2.2.3.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the query data request status procedure as defined in R1GAP [1], clause 5.2.4. -- 2) A data job exists in the DUT and the dataJobId is known to the test simulator. - -##### 9.2.2.3.3 Test methodology - -###### 9.2.2.3.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -###### 9.2.2.3.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to query a data job status. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.4. -- b) The HTTP request is a GET operation. -- c) The dataJobID in the URI match the data job status being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.6.1. - -Step 4. The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.6.1. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.4. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 7.3.4.6.1. - -##### 9.2.2.3.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -# --- 10 DME Data subscription service test cases - -## 10.1 Conformance test cases for rApp - -### 10.1.1 General - -#### 10.1.1.1 Device under test requirements - -The rApp that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the DME Data subscription service, and the purpose of the test scenarios is to validate that it conforms to the API Consumer functionality as specified in R1AP [4], clause 7.3.4. - -#### 10.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. - -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Consumer functionality as specified in R1AP [4], clause 7.3.4. - -### 10.1.2 Data access API as API Consumer test scenario - -#### 10.1.2.1 Create data job (positive case) - -##### 10.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the create data job API as specified in R1AP [4], clause 7.3.4.1. The expected outcome is successful validation of the request from the DUT. - -##### 10.1.2.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the subscribe data procedure as defined in R1GAP [1], clause 5.2.5. -- 2) The DataJobInfo is known to the DUT - -##### 10.1.2.1.3 Test methodology - -###### 10.1.2.1.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 10.1.2.1.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to create a data job. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.4.1. -- b) The HTTP request is a POST operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.1. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.1.1. - -##### 10.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 10.1.2.2 Cancel data job (positive case) - -##### 10.1.2.2.1 Test description and applicability - -The purpose of this test case is to test the Cancel data job API as specified in R1AP [4], clause 7.3.4.2. The expected outcome is successful validation of the request from the DUT. - -##### 10.1.2.2.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the unsubscribe data procedure as defined in R1GAP [1], clause 5.2.5. - -- 2) A data job exists in test simulator and the dataJobId is known to the DUT. - -##### 10.1.2.2.3 Test methodology - -###### 10.1.2.2.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 10.1.2.2.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to cancel a data job. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.3. -- b) The HTTP request is a DELETE operation. -- c) The dataJobID in the URI match the data job being deleted. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.2. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.2.1. - -##### 10.1.2.2.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 10.1.2.3 Query data job (positive case) - -##### 10.1.2.3.1 Test description and applicability - -The purpose of this test case is to test the query data job API as specified in R1AP [4], clause 7.3.4.5 The expected outcome is successful validation of the request from the DUT. - -##### 10.1.2.3.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the query data subscription procedure as defined in R1GAP [1], clause 5.2.5. -- 2) A data job exists in test simulator and the dataJobId is known to the DUT. - -##### 10.1.2.3.3 Test methodology - -###### 10.1.2.3.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 10.1.2.3.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query a data job. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.4.5.1. - -- b) The HTTP request is a GET operation. -- c) The dataJobID in the URI match the data job being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.5.1. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.6.1. - -##### 10.1.2.3.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 10.1.2.4 Query data job status (positive case) - -##### 10.1.2.4.1 Test description and applicability - -The purpose of this test case is to test the query data job status API as specified in R1AP [4], clause 7.3.4.6 The expected outcome is successful validation of the request from the DUT. - -##### 10.1.2.4.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the query data subscription status procedure as defined in R1GAP [1], clause 5.2.5. -- 2) A data job exists in test simulator and the dataJobId is known to the DUT. - -##### 10.1.2.4.3 Test methodology - -###### 10.1.2.4.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 10.1.2.4.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query a data job status. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.4.6.1. -- b) The HTTP request is a GET operation. -- c) The dataJobID in the URI match the data job being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.6.1. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.6.1. - -###### 10.1.2.4.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 10.1.2.5 Query data job identifiers (positive case) - -##### 10.1.2.5.1 Test description and applicability - -The purpose of this test case is to test the query data job identifiers API as specified in R1AP [4], clause 7.3.4.7 The expected outcome is successful validation of the request from the DUT. - -##### 10.1.2.5.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the query data subscription status procedure as defined in R1GAP [1], clause 5.2.5. -- 2) A set of data jobs exists in test simulator. - -##### 10.1.2.5.3 Test methodology - -###### 10.1.2.5.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 10.1.2.5.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query data job identifiers. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.4.7.1. -- b) The HTTP request is a GET operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.7.1. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.7.1. - -###### 10.1.2.5.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 10.1.2.6 Update data job (positive case) - -##### 10.1.2.6.1 Test description and applicability - -The purpose of this test case is to test the Update data job API as specified in R1AP [4], clause 7.3.4.5. The expected outcome is successful validation of the request from the DUT. - -##### 10.1.2.6.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Update data job procedure as defined in R1GAP [1], clause 5.2.5. -- 2) A data job exists in test simulator and the dataJobId and DataJobInfo are known to the DUT. - -##### 10.1.2.6.3 Test methodology - -###### 10.1.2.6.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 10.1.2.6.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to update a data job identified by the dataJobId and DataJobInfo. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 7.3.4.4. -- b) The HTTP request is a PUT operation. -- c) The dataJobId and DataJobInfo in the URI match the data job being updated -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.4.1. - -Step 4. The test simulator updates the resource, and a representation of the updated resource shall be returned in the response body the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.4.1. - -##### 10.1.2.6.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 10.2 Conformance test cases for SMO/Non-RT RIC framework - -### 10.2.1 General - -#### 10.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the DME Data subscription service, and the purpose of the test scenarios is to validate that it conforms to the API Producer functionality as specified in R1AP [4], clause 7.3.4. - -#### 10.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a rApp. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Producer functionality as specified in R1AP [4], clause 7.3.4. - -### 10.2.2 Data access API as API Producer test scenario - -#### 10.2.2.1 Create data job (positive case) - -##### 10.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the create data job API as specified in R1AP [4], clause 7.3.4.1. The expected outcome is successful validation of the request from the DUT. - -##### 10.2.2.1.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the subscribe data procedure as defined in R1GAP [1], clause 5.2.5. -- 2) The DataJobInfo is known to the DUT - -##### 10.2.2.1.3 Test methodology - -###### 10.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -###### 10.2.2.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to create a data job. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a POST request. -- b) The URI conforms to the format specified in R1AP [4], clause 7.3.5.2.3.1. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.1. - -Step 4. The DUT generates the data job and constructs the URI for the created resource. - -Step 5. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.1. - -Step 6. At the test simulator the contents of the received HTTP response is recorded. - -Step 7. The test simulator does the following validation: - -- a. The HTTP response message content includes the information as specified in R1AP [4], clause 7.3.4.1, and the Location header will be present. -- b. The URI conforms to the format specified in R1AP [4], clause 7.3.5.3. - -##### 10.2.2.1.4 Expected result - -The test is considered passed if Step 7 validation has passed. - -#### 10.2.2.2 Cancel data job (positive case) - -##### 10.2.2.2.1 Test description and applicability - -The purpose of this test case is to test the Cancel data job API as specified in R1AP [4], clause 7.3.4.2. The expected outcome is successful validation of the request from the DUT. - -##### 10.2.2.2.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the unsubscribe data procedure as defined in R1GAP [1], clause 5.2.5. -- 2) A data job exists in DUT and the dataJobId is known to the test simulator. - -##### 10.2.2.2.3 Test methodology - -###### 10.2.2.2.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -###### 10.2.2.2.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to cancel a data job. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.3.3.1. -- b) The HTTP request is a DELETE operation. -- c) The dataJobID in the URI match the data job being deleted. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.2. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.2. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 7.3.5.3. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 7.3.4.2. - -##### 10.2.2.2.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -#### 10.2.2.3 Query data job (positive case) - -##### 10.2.2.3.1 Test description and applicability - -The purpose of this test case is to test the query data job API as specified in R1AP [4], clause 7.3.4.5 The expected outcome is successful validation of the request from the DUT. - -##### 10.2.2.3.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the query data subscription procedure as defined in R1GAP [1], clause 5.2.5. -- 2) A data job exists in the DUT and the dataJobId is known to the test simulator. - -##### 10.2.2.3.3 Test methodology - -###### 10.2.2.3.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -###### 10.2.2.3.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to query a data job. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.3. -- b) The HTTP request is a GET operation. - -- c) The dataJobID in the URI match the data job being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.5.1. - -Step 4. The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.5.1. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.3. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 7.3.4.5.1. - -##### 10.2.2.3.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -#### 10.2.2.4 Query data job status (positive case) - -##### 10.2.2.4.1 Test description and applicability - -The purpose of this test case is to test the query data job status API as specified in R1AP [4], clause 7.3.4.6 The expected outcome is successful validation of the request from the DUT. - -##### 10.2.2.4.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the query data subscription status procedure as defined in R1GAP [1], clause 5.2.5. -- 2) A data job exists in the DUT and the dataJobId is known to the test simulator. - -##### 10.2.2.4.3 Test methodology - -###### 10.2.2.4.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -###### 10.2.2.4.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to query a data job status. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.4. -- b) The HTTP request is a GET operation. -- c) The dataJobID in the URI match the data job status being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.6.1. - -Step 4. The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.6.1. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.4. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 7.3.4.6.1. - -##### 10.2.2.4.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -#### 10.2.2.5 Query data job identifiers (positive case) - -##### 10.2.2.5.1 Test description and applicability - -The purpose of this test case is to test the query data job identifiers API as specified in R1AP [4], clause 7.3.4.7 The expected outcome is successful validation of the request from the DUT. - -##### 10.2.2.5.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the query data subscription status procedure as defined in R1GAP [1], clause 5.2.5. -- 2) A set of data jobs exists in the DUT. - -##### 10.2.2.5.3 Test methodology - -###### 10.2.2.5.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -###### 10.2.2.5.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to query a set of data job identifiers. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.2. -- b) The HTTP request is a GET operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.7.1. - -Step 4. The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.4.7.1. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.2. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 7.3.4.7.1. - -##### 10.2.2.5.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -#### 10.2.2.6 Update data job (positive case) - -##### 10.2.2.6.1 Test description and applicability - -The purpose of this test case is to test the Update data job API as specified in R1AP [4], clause 7.3.4.4. The expected outcome is successful validation of the request from the DUT. - -##### 10.2.2.6.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Update data job procedure as defined in R1GAP [1], clause 5.2.5. -- 2) A data job exists in the DUT and the dataJobId and DataJobInfo are known to the test simulator. - -#### 10.2.2.6.3 Test methodology - -##### 10.2.2.6.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 10.2.2.6.3.2 Procedure - -- Step 1. The test simulator as an API Consumer initiates a HTTP request to update a data job identified by the dataJobId and DataJobInfo. -- Step 2. The DUT receives the HTTP request. -- Step 3. The DUT does the following validation: - - a) The URI conforms to the format specified in R1AP [4], clause 7.3.5.3. - - b) The HTTP request is a PUT operation. - - c) The dataJobId and DataJobInfo in the URI match the data job being updated - - d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.3.4.4 -- Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.3.5.3. -- Step 5. At the test simulator the contents of the received HTTP response is recorded. -- Step 6. The test simulator does the following validation: - - e) The URI conforms to the format specified in R1AP [4], clause 7.3.5.3. - - f) The HTTP response message content includes the information as specified in R1AP [4], clause 7.3.4.4. - -#### 10.2.2.6.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 10.2.2.7 Notify data availability (positive case) - -#### 10.2.2.7.1 Test description and applicability - -The purpose of this test case is to test the Notify data availability API as specified in R1AP [4], clause 7.3.4.3. The expected outcome is successful validation of the request from the DUT. - -#### 10.2.2.7.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Notify data availability procedure as defined in R1GAP [1], clause 5.2.5. -- 2) A data subscription exists in the DUT. - -#### 10.2.2.7.3 Test methodology - -##### 10.2.2.7.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -##### 10.2.2.7.3.2 Procedure - -- Step 1. The DUT as an API producer initiates the sending of a HTTP POST request. -- Step 2. At the test simulator the contents of the received HTTP request is recorded. -- Step 3. The test simulator does the following validation: - - a) The HTTP request is a POST operation. - - b) The callback URI matches the URI provided in the data subscription. - -#### 10.2.2.7.4 Expected result - -The test is considered passed if Step 3 validation has passed. - ---- - -## 11 A1 related services test cases - -### 11.1 Conformance test cases for rApp - -#### 11.1.1 General - -##### 11.1.1.1 Device under test requirements - -The rApp that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the A1 policy management service, and the purpose of the test scenarios is to validate that it conforms to the API Consumer functionality as specified in R1AP [4], clause 9.1.4. - -##### 11.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Consumer functionality as specified in R1AP [4], clause 9.1.4. - -## 11.1.2 A1 policy management API as API Consumer test scenario - -### 11.1.2.1 Query A1 policy type identifiers (positive case) - -#### 11.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the query A1 policy type identifiers API as specified in R1AP [4], clause 9.1.4.1. The expected outcome is successful validation of the request from the DUT. - -#### 11.1.2.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Query A1 policy type identifiers procedure as defined in R1GAP [1], clause 5.3.2. -- 2) A set of A1 policy types exists in test simulator. - -#### 11.1.2.1.3 Test methodology - -##### 11.1.2.1.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 11.1.2.1.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query A1 policy type identifiers. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.4.1. -- b) The HTTP request is a GET operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.1. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.5.2. - -#### 11.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 11.1.2.2 Query A1 policy type (positive case) - -#### 11.1.2.2.1 Test description and applicability - -The purpose of this test case is to test the query A1 policy type API as specified in R1AP [4], clause 9.1.4.2. The expected outcome is successful validation of the request from the DUT. - -#### 11.1.2.2.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the query A1 policy type procedure as defined in R1GAP [1], clause 5.3.2. -- 2) An A1 policy type exists in test simulator and the policyTypeId is known to the DUT. - -### 11.1.2.2.3 Test methodology - -#### 11.1.2.2.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -#### 11.1.2.2.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query an A1 policy type. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.4.2. -- b) The HTTP request is a GET operation. -- c) The policyTypeID in the URI match the A1 policy type being queried. The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.2. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.5.3. - -### 11.1.2.2.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 11.1.2.3 Query A1 policy identifiers (positive case) - -### 11.1.2.3.1 Test description and applicability - -The purpose of this test case is to test the query A1 policy identifiers API as specified in R1AP [4], clause 9.1.4.3 The expected outcome is successful validation of the request from the DUT. - -### 11.1.2.3.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the query A1 policy identifiers procedure as defined in R1GAP [1], clause 5.3.2. -- 2) A set of A1 policies exists in test simulator. - -### 11.1.2.3.3 Test methodology - -#### 11.1.2.3.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -#### 11.1.2.3.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query A1 policy identifiers. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.4.3. -- b) The HTTP request is a GET operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.3. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.5.4. - -#### 11.1.2.3.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 11.1.2.4 Create A1 policy (positive case) - -#### 11.1.2.4.1 Test description and applicability - -The purpose of this test case is to test the create A1 policy API as specified in R1AP [4], clause 9.1.4.4. The expected outcome is successful validation of the request from the DUT. - -#### 11.1.2.4.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the create A1 policy procedure as defined in R1GAP [1], clause 5.3.2. -- 2) The PolicyObjectInformation is known to the DUT. - -#### 11.1.2.4.3 Test methodology - -##### 11.1.2.4.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 11.1.2.4.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to create an A1 policy. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.4.4. -- b) The HTTP request is a POST operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.4. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.5.4. - -#### 11.1.2.4.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 11.1.2.5 Query A1 policy (positive case) - -#### 11.1.2.5.1 Test description and applicability - -The purpose of this test case is to test the query A1 policy API as specified in R1AP [4], clause 9.1.4.5 The expected outcome is successful validation of the request from the DUT. - -#### 11.1.2.5.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the query A1 policy procedure as defined in R1GAP [1], clause 5.3.2. -- 2) An A1 policy exists in test simulator and the policyId is known to the DUT. - -### 11.1.2.5.3 Test methodology - -#### 11.1.2.5.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -#### 11.1.2.5.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query an A1 policy. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.4.5. -- b) The HTTP request is a GET operation. -- c) The policyId in the URI match the A1 policy being queried. The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.5. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.5.5. - -### 11.1.2.5.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 11.1.2.6 Update A1 policy (positive case) - -### 11.1.2.6.1 Test description and applicability - -The purpose of this test case is to test the Update A1 policy API as specified in R1AP [4], clause 9.1.4.6. The expected outcome is successful validation of the request from the DUT. - -### 11.1.2.6.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Update A1 policy procedure as defined in R1GAP [1], clause 5.3.2. -- 2) An A1 policy exists in test simulator and the policyId and PolicyObject are known to the DUT. - -### 11.1.2.6.3 Test methodology - -#### 11.1.2.6.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -#### 11.1.2.6.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to update an A1 policy identified by the policyId and PolicyObject. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 9.1.4.6. -- b) The HTTP request is a PUT operation. - -- c) The policyId and PolicyObject in the URI match the A1 policy being updated -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.6. - -Step 4. The test simulator updates the resource, and a representation of the updated resource shall be returned in the response body the appropriate HTTP response as specified in R1AP [4], clause 9.1.5.5. - -#### 11.1.2.6.4 Expected result - -The test is considered passed if Step 3 validation has passed - -### 11.1.2.7 Delete A1 policy (positive case) - -#### 11.1.2.7.1 Test description and applicability - -The purpose of this test case is to test the Delete A1 policy API as specified in R1AP [4], clause 9.1.4.6. The expected outcome is successful validation of the request from the DUT. - -#### 11.1.2.7.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Delete A1 policy procedure as defined in R1GAP [1], clause 5.3.2. -- 2) An A1 policy exists in test simulator and the policyId is known to the DUT. - -#### 11.1.2.7.3 Test methodology - -##### 11.1.2.7.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 11.1.2.7.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to delete an A1 policy. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.4.7. -- b) The HTTP request is a DELETE operation. -- c) The policyId in the URI match the A1 policy being deleted. The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.7. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.5.5. - -#### 11.1.2.7.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 11.1.2.8 Query A1 policy status (positive case) - -#### 11.1.2.8.1 Test description and applicability - -The purpose of this test case is to test the query A1 policy status API as specified in R1AP [4], clause 9.1.4.8 The expected outcome is successful validation of the request from the DUT. - -#### 11.1.2.8.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the query A1 policy status procedure as defined in R1GAP [1], clause 5.3.2. -- 2) An A1 policy exists in test simulator and the policyId is known to the DUT. - -#### 11.1.2.8.3 Test methodology - -##### 11.1.2.8.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 11.1.2.8.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query an A1 policy status. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.4.8. -- b) The HTTP request is a GET operation. -- c) The policyId in the URI match the A1 policy status being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.8 . - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.5.6. - -#### 11.1.2.8.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 11.1.2.9 Subscribe A1 policy status (positive case) - -#### 11.1.2.9.1 Test description and applicability - -The purpose of this test case is to test the subscribe A1 policy status API as specified in R1AP [4], clause 9.1.4.9 The expected outcome is successful validation of the request from the DUT. - -#### 11.1.2.9.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the subscribe A1 policy status procedure as defined in R1GAP [1], clause 5.3.2. -- 2) The PolicyStatusSubscription is known to the DUT - -#### 11.1.2.9.3 Test methodology - -##### 11.1.2.9.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 11.1.2.9.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to create an A1 policy status subscription. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.4.9. -- b) The HTTP request is a POST operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.9. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.5.7. - -#### 11.1.2.9.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 11.1.2.10 Update A1 policy status subscription (positive case) - -#### 11.1.2.10.1 Test description and applicability - -The purpose of this test case is to test the Update A1 policy status subscription API as specified in R1AP [4], clause 9.1.4.10. The expected outcome is successful validation of the request from the DUT. - -#### 11.1.2.10.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Update A1 policy status subscription procedure as defined in R1GAP [1], clause 5.3.2. -- 2) An A1 policy status subscription exists in test simulator and the subscriptionId and PolicyStatusSubscription are known to the DUT. - -#### 11.1.2.10.3 Test methodology - -##### 11.1.2.10.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 11.1.2.10.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to update an A1 policy status subscription identified by the subscriptionId and PolicyStatusSubscription. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 9.1.4.10. -- b) The HTTP request is a PUT operation. -- c) The subscriptionId and PolicyStatusSubscription in the URI match the status subscription being updated -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.10. - -Step 4. The test simulator updates the resource, and a representation of the updated resource shall be returned in the response body the appropriate HTTP response as specified in R1AP [4], clause 9.1.5.8. - -#### 11.1.2.10.4 Expected result - -The test is considered passed if Step 3 validation has passed - -### 11.1.2.11 Query A1 policy status subscription (positive case) - -#### 11.1.2.11.1 Test description and applicability - -The purpose of this test case is to test the query A1 policy status subscription API as specified in R1AP [4], clause 9.1.4.11. The expected outcome is successful validation of the request from the DUT. - -#### 11.1.2.11.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the query A1 policy status subscription procedure as defined in R1GAP [1], clause 5.3.2. -- 2) An A1 policy status subscription exists in test simulator and the subscriptionId is known to the DUT. - -#### 11.1.2.11.3 Test methodology - -##### 11.1.2.11.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 11.1.2.11.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query an A1 policy status subscription. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.4.11. -- b) The HTTP request is a GET operation. -- c) The subscriptionId in the URI match the A1 policy status subscription being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.11 . - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.5.8. - -#### 11.1.2.11.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 11.1.2.12 Unsubscribe A1 policy status (positive case) - -#### 11.1.2.12.1 Test description and applicability - -The purpose of this test case is to test the Unsubscribe A1 policy status API as specified in R1AP [4], clause 9.1.4.12. The expected outcome is successful validation of the request from the DUT. - -#### 11.1.2.12.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Unsubscribe A1 policy procedure as defined in R1GAP [1], clause 5.3.2. -- 2) An A1 policy status subscription exists in test simulator and the subscriptionId is known to the DUT. - -### 11.1.2.12.3 Test methodology - -#### 11.1.2.12.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -#### 11.1.2.12.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to delete an A1 policy status subscription. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.4.12. -- b) The HTTP request is a DELETE operation. -- c) The subscriptionId in the URI match the A1 policy status subscription being deleted. The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.12. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.5.8. - -### 11.1.2.12.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 11.2 Conformance test cases for SMO/Non-RT RIC framework - -### 11.2.1 General - -#### 11.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the DME Data subscription service, and the purpose of the test scenarios is to validate that it conforms to the API Producer functionality as specified in R1AP [4], clause 9.1.4. - -#### 11.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a rApp. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Producer functionality as specified in R1AP [4], clause 9.1.4. - -## 11.2.2 A1 policy management API as API Producer test scenario - -### 11.2.2.1 Query A1 policy type identifiers (positive case) - -#### 11.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the query A1 policy type identifiers API as specified in R1AP [4], clause 9.1.4.1. The expected outcome is successful validation of the request from the DUT. - -#### 11.2.2.1.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Query A1 policy type identifiers procedure as defined in RIGAP [1], clause 5.3.2. -- 2) A set of A1 policy types exists in the DUT. - -#### 11.2.2.1.3 Test methodology - -##### 11.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -##### 11.2.2.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to query a set of A1 policy type identifiers. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.4.1. -- b) The HTTP request is a GET operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.1. - -Step 4. The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.1. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.2. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.1 - -#### 11.2.2.1.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 11.2.2.2 Query A1 policy type (positive case) - -#### 11.2.2.2.1 Test description and applicability - -The purpose of this test case is to test the query A1 policy type API as specified in R1AP [4], clause 9.1.4.2 The expected outcome is successful validation of the request from the DUT. - -#### 11.2.2.2.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the query A1 policy type procedure as defined in R1GAP [1], clause 5.3.2. -- 2) An A1 policy type exists in DUT and the policyTypeId is known to the test simulator. - -#### 11.2.2.2.3 Test methodology - -##### 11.2.2.2.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -##### 11.2.2.2.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to query an A1 policy type. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.3. -- b) The HTTP request is a GET operation. -- c) The policyTypeId in the URI match the A1 policy type being queried. The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.2. - -Step 4. The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.2. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.3. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.2. - -#### 11.2.2.2.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 11.2.2.3 Query A1 policy identifiers (positive case) - -#### 11.2.2.3.1 Test description and applicability - -The purpose of this test case is to test the query A1 policy identifiers API as specified in R1AP [4], clause 9.1.4.3. The expected outcome is successful validation of the request from the DUT. - -#### 11.2.2.3.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Query A1 policy identifiers procedure as defined in R1GAP [1], clause 5.3.2. -- 2) A set of A1 policies exists in the DUT. - -### 11.2.2.3.3 Test methodology - -#### 11.2.2.3.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -#### 11.2.2.3.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to query a set of A1 policy identifiers. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.4. -- b) The HTTP request is a GET operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.3. - -Step 4. The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.3. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.4. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.3. - -#### 11.2.2.3.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 11.2.2.4 Create A1 policy (positive case) - -#### 11.2.2.4.1 Test description and applicability - -The purpose of this test case is to test the create A1 policy API as specified in R1AP [4], clause 9.1.4.4. The expected outcome is successful validation of the request from the DUT. - -#### 11.2.2.4.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the create A1 policy procedure as defined in R1GAP [1], clause 5.3.2. -- 2) The PolicyObjectInformation is known to the test simulator - -#### 11.2.2.4.3 Test methodology - -##### 11.2.2.4.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -##### 11.2.2.4.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to create an A1 policy. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a POST request. -- b) The URI conforms to the format specified in R1AP [4], clause 9.1.5.4 -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.4. - -Step 4. The DUT generates the A1 policy and constructs the URI for the created resource. - -Step 5. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.4. - -Step 6. At the test simulator the contents of the received HTTP response is recorded. - -Step 7. The test simulator does the following validation: - -- a) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.4, and the Location header will be present. -- b) The URI conforms to the format specified in R1AP [4], clause 9.1.5.4. - -#### 11.2.2.4.4 Expected result - -The test is considered passed if Step 7 validation has passed. - -### 11.2.2.5 Query A1 policy (positive case) - -#### 11.2.2.5.1 Test description and applicability - -The purpose of this test case is to test the query A1 policy API as specified in R1AP [4], clause 9.1.4.5 The expected outcome is successful validation of the request from the DUT. - -#### 11.2.2.5.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the query A1 policy procedure as defined in R1GAP [1], clause 5.3.2. -- 2) An A1 policy exists in DUT and the policyId is known to the test simulator. - -#### 11.2.2.5.3 Test methodology - -##### 11.2.2.5.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -##### 11.2.2.5.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to query an A1 policy. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.5. -- b) The HTTP request is a GET operation. -- c) The policyId in the URI match the A1 policy being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.5. - -Step 4. The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.5. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.5 -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.5. - -#### 11.2.2.5.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -#### 11.2.2.6 Update A1 policy (positive case) - -##### 11.2.2.6.1 Test description and applicability - -The purpose of this test case is to test the Update A1 policy API as specified in R1AP [4], clause 9.1.4.6. The expected outcome is successful validation of the request from the DUT. - -##### 11.2.2.6.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Update A1 policy procedure as defined in R1GAP [1], clause 5.3.2. -- 2) An A1 policy exists in the DUT and the policyId and PolicyObject are known to the test simulator. - -##### 11.2.2.6.3 Test methodology - -###### 11.2.2.6.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -###### 11.2.2.6.3.2 Procedure - -- Step 1. The test simulator as an API Consumer initiates a HTTP request to update an A1 policy identified by the policyId and PolicyObject. -- Step 2. The DUT receives the HTTP request. -- Step 3. The DUT does the following validation: - - a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.5. - - b) The HTTP request is a PUT operation. - - c) The policyId and PolicyObject in the URI match the A1 policy being updated - - d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.6 -- Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.6. -- Step 5. At the test simulator the contents of the received HTTP response is recorded. -- Step 6. The test simulator does the following validation: - - a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.5. - - b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.6. - -##### 11.2.2.6.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 11.2.2.7 Delete A1 policy (positive case) - -#### 11.2.2.7.1 Test description and applicability - -The purpose of this test case is to test the Delete A1 policy API as specified in R1AP [4], clause 9.1.4.6. The expected outcome is successful validation of the request from the DUT. - -#### 11.2.2.7.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Delete A1 policy procedure as defined in R1GAP [1], clause 5.3.2. -- 2) An A1 policy exists in DUT and the policyId is known to the test simulator. - -#### 11.2.2.7.3 Test methodology - -##### 11.2.2.7.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -##### 11.2.2.7.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to Delete an A1 policy - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.5. -- b) The HTTP request is a DELETE operation. -- c) The policyID in the URI match the A1 policy being deleted. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.7 - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.7. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 9.1.5.5. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.7 - -#### 11.2.2.7.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 11.2.2.8 Query A1 policy status (positive case) - -#### 11.2.2.8.1 Test description and applicability - -The purpose of this test case is to test the query A1 policy status API as specified in R1AP [4], clause 9.1.4.8 The expected outcome is successful validation of the request from the DUT. - -#### 11.2.2.8.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the query A1 policy procedure as defined in R1GAP [1], clause 5.3.2. - -- 2) An A1 policy exists in DUT and the policyId is known to the test simulator. - -### 11.2.2.8.3 Test methodology - -#### 11.2.2.8.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -#### 11.2.2.8.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to query an A1 policy status. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.36 -- b) The HTTP request is a GET operation. -- c) The policyId in the URI match the A1 policy status being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.8. - -Step 4. The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.8. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.6. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.8. - -#### 11.2.2.8.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 11.2.2.9 Subscribe A1 policy status (positive case) - -#### 11.2.2.9.1 Test description and applicability - -The purpose of this test case is to test the subscribe A1 policy status API as specified in R1AP [4], clause 9.1.4.9 The expected outcome is successful validation of the request from the DUT. - -#### 11.2.2.9.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the subscribe A1 policy status procedure as defined in R1GAP [1], clause 5.3.2. -- 2) The PolicyStatusSubscription is known to the test simulator - -#### 11.2.2.9.3 Test methodology - -##### 11.2.2.9.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -#### 11.2.2.9.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to create an A1 policy status subscription. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a POST request. -- b) The URI conforms to the format specified in R1AP [4], clause 9.1.5.7 -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.9. - -Step 4. The DUT generates the A1 policy status subscription and constructs the URI for the created resource. - -Step 5. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.9. - -Step 6. At the test simulator the contents of the received HTTP response is recorded. - -Step 7. The test simulator does the following validation: - -- a) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.9, and the Location header will be present. -- b) The URI conforms to the format specified in R1AP [4], clause 9.1.5.7. - -#### 11.2.2.9.4 Expected result - -The test is considered passed if Step 7 validation has passed. - -### 11.2.2.10 Update A1 policy status subscription (positive case) - -#### 11.2.2.10.1 Test description and applicability - -The purpose of this test case is to test the Update A1 policy status subscription API as specified in R1AP [4], clause 9.1.4.10. The expected outcome is successful validation of the request from the DUT. - -#### 11.2.2.10.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Update A1 policy status subscription procedure as defined in RIGAP [1], clause 5.3.2. -- 2) An A1 policy status subscription exists in the DUT and the subscriptionId and PolicyStatusSubscription are known to the test simulator. - -#### 11.2.2.10.3 Test methodology - -##### 11.2.2.10.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -##### 11.2.2.10.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to update an A1 policy status subscription identified by the subscriptionId and PolicyStatusSubscription. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.8. -- b) The HTTP request is a PUT operation. -- c) The subscriptionId and PolicyStatusSubscription in the URI match the A1 policy status subscription being updated -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.10 - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.10. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.8. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.10. - -#### 11.2.2.10.4 Expected result - -The test is considered passed if Step 6 validation has passed - -### 11.2.2.11 Query A1 policy status subscription (positive case) - -#### 11.2.2.11.1 Test description and applicability - -The purpose of this test case is to test the query A1 policy status subscription API as specified in R1AP [4], clause 9.1.4.11 -The expected outcome is successful validation of the request from the DUT. - -#### 11.2.2.11.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the query A1 policy status subscription procedure as defined in RIGAP [1], clause 5.3.2. -- 2) An A1 policy status subscription exists in test simulator and the subscriptionId is known to the DUT. - -#### 11.2.2.11.3 Test methodology - -##### 11.2.2.11.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -##### 11.2.2.11.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to query an A1 policy status subscription. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.8 . -- b) The HTTP request is a GET operation. -- c) The subscriptionId in the URI match the A1 policy status subscription being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.11. - -Step 4. The DUT constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.5. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.8 -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.11. - -#### 11.2.2.11.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 11.2.2.12 Unsubscribe A1 policy status (positive case) - -#### 11.2.2.12.1 Test description and applicability - -The purpose of this test case is to test the Unsubscribe A1 policy status API as specified in R1AP [4], clause 9.1.4.12. The expected outcome is successful validation of the request from the DUT. - -#### 11.2.2.12.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Unsubscribe A1 policy procedure as defined in R1GAP [1], clause 5.3.2. -- 2) An A1 policy subscription exists in DUT and the subscriptionId is known to the test simulator. - -#### 11.2.2.12.3 Test methodology - -##### 11.2.2.12.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -##### 11.2.2.12.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to delete an A1 policy status subscription - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 9.1.5.8. -- b) The HTTP request is a DELETE operation. -- c) The subscriptionId in the URI match the A1 policy status subscription being deleted. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 9.1.4.12. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 9.1.4.12. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 9.1.5.8. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 9.1.4.12. - -#### 11.2.2.12.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 11.2.2.13 Notify A1 policy status changes (positive case) - -#### 11.2.2.13.1 Test description and applicability - -The purpose of this test case is to test the Notify A1 policy status changes API as specified in R1AP [4], clause 9.1.4.13. The expected outcome is successful validation of the request from the DUT. - -#### 11.2.2.13.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Notify A1 policy status changes procedure as defined in R1GAP [1], clause 5.3.2. -- 2) An A1 policy status exists in the DUT. - -#### 11.2.2.13.3 Test methodology - -##### 11.2.2.13.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -##### 11.2.2.13.3.2 Procedure - -Step 1. The DUT as an API producer initiates the sending of a HTTP POST request. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The HTTP request is a POST operation. -- b) The callback URI matches the URI provided in the A1 policy status subscription. - -#### 11.2.2.13.4 Expected result - -The test is considered passed if Step 3 validation has passed. - ---- - -## 12 DME Data discovery services test cases - -### 12.1 Conformance test cases for rApp - -#### 12.1.1 General - -##### 12.1.1.1 Device under test requirements - -The rApp that acts as Device Under Test (DUT) in these test scenarios, the requirements on the DUT for these tests are that it can handle the data discovery service, and the purpose of the test scenarios is to validate that it conforms to the data discovery API specified in R1AP [4], clause 7.2.4. - -##### 12.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. - -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance API Producer functionality as specified in R1AP [4], clause 7.2.4. - -## 12.1.2 Data discover API as API Consumer test scenario - -### 12.1.2.1 Discover DME types (positive case) - -#### 12.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the Discover DME types operation as specified in R1AP [4], clause 7.2.4.1. The expected outcome is successful validation of the request from the DUT. - -#### 12.1.2.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Discover DME types procedure. -- 2) A set of DMETYPERelatedCapabilities exist in the test simulator. - -#### 12.1.2.1.3 Test methodology - -##### 12.1.2.1.3.1 Initial conditions - -- 1) The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 12.1.2.1.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to Discover DME types. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 7.2.5.2. -- b) The HTTP request is a GET operation. -- c) The message body is empty. - -Step 4. The test simulator generated the appropriate HTTP response as specified in R1AP [4], clause 7.2.5.2.3.1 - -NOTE: Presence or validation of optional filter parameters is not used to determine validation on this test. - -#### 12.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 12.1.3.1 Query capabilities related to DME type (positive case) - -#### 12.1.3.1.1 Test description and applicability - -The purpose of this test case is to test the Query capabilities related to DME type operation as specified in R1AP [4], clause 7.2.4.2. The expected outcome is successful validation of the request from the DUT. - -#### 12.1.3.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Query DME type information procedure. - -- 2) A set of service DMETyPeRelatedCapabilities exist in the test simulator. - -#### 12.1.3.1.3 Test methodology - -##### 12.1.3.1.3.1 Initial conditions - -- 1) The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 12.1.3.1.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query for information about a specific DME type with dmeTypeId. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 7.2.5.3. -- b) The HTTP request is a GET operation. -- c) The message body is empty. - -Step 4. The test simulator generated the appropriate HTTP response as specified in R1AP [4], clause 7.2.5.3.3.1 - -##### 12.1.3.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 12.2 Conformance test cases for SMO/Non-RT RIC framework - -### 12.2.1 General - -#### 12.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as Device Under Test (DUT) in these test scenarios, the requirements on the DUT for these tests are that it can handle the SME service discovery service, and the purpose of the test scenarios is to validate that it conforms to the Data discovery API specified in R1AP [4], clause 7.2.4. - -#### 12.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as specified in section 4.3.2. In addition, it has the following capabilities: - -- 1) Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- 2) Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to API Producer functionality as specified in R1AP [4], clause 7.2.4. - -## 12.2.2 data discovery API as API Producer test scenario - -### 12.2.2.1 Discover DME types (positive case) - -#### 12.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the Data discovery APIs as specified in R1AP [4], clause 7.2. The expected outcome is successful validation of the response from the DUT. - -#### 12.2.2.1.2 Test entrance criteria - -- 1) The DUT supports the functionality to Discover DME types procedure. -- 2) A set of DMETTypeRelatedCapabilities are supported in the test simulator. - -#### 12.2.2.1.3 Test methodology - -##### 12.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -##### 12.2.2.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to Data discovery APIs for all dme types . - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a GET request. -- b) The URI conforms to the format as specified in R1AP [4], clause 7.2.5.2 -- c) The HTTP request message content includes the information as specified in R1AP[4], clause 7.2.5.2.3.1. - -Step 4. The DUT initiates a HTTP Response. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.2.5.2. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 7.2.5.2.3.1. - -#### 12.2.2.1.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 12.2.3.1 Query capabilities related to DME type (positive case) - -#### 12.2.3.1.1 Test description and applicability - -The purpose of this test case is to test the Data discovery APIs as specified in R1AP [4], clause 7.2. The expected outcome is successful validation of the response from the DUT. - -#### 12.2.3.1.2 Test entrance criteria - -- 1) The DUT supports the functionality to Discover DME types procedure. - -- 2) A set of DMETyPeRelatedCapabilities are supported in the test simulator. - -### 12.2.3.1.3 Test methodology - -#### 12.2.3.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -#### 12.2.3.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to Data discovery APIs for all dme type with dmeTypeId . - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a GET request. -- b) The URI conforms to the format as specified in R1AP [4], clause 7.2.5.3 -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.2.5.3.3.1. - -Step 4. The DUT initiates a HTTP Response. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.2.5.3. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 7.2.5.3.3.1. - -#### 12.2.3.1.4 Expected result - -The test is considered passed if Step 6 validation has passed. - ---- - -## 13 DME Data offer service test cases - -### 13.1 Conformance test cases for rApp - -#### 13.1.1 General - -##### 13.1.1.1 Device under test requirements - -The rApp that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the DME Data offer service, and the purpose of the test scenarios is to validate that it conforms to the API Consumer functionality as specified in R1AP [4], clause 7.6.4. - -##### 13.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. - -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Consumer functionality as specified in R1AP [4], clause 7.6.4. - -## 13.1.2 Data offer API as API Consumer test scenario - -### 13.1.2.1 Create data offer (positive case) - -#### 13.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the create data offer API as specified in R1AP [4], clause 7.6.4.1. The expected outcome is successful validation of the request from the DUT. - -#### 13.1.2.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the create data offer procedure as defined in R1GAP [1], clause 5.2.7. -- 2) The DataOfferInfo is known to the DUT - -#### 13.1.2.1.3 Test methodology - -##### 13.1.2.1.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 13.1.2.1.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to create a data offer. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.6.4.1. -- b) The HTTP request is a POST operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.6.4.1. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 7.6.4.1.1. - -##### 13.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 13.1.2.2 Cancel data offer (positive case) - -#### 13.1.2.2.1 Test description and applicability - -The purpose of this test case is to test the Cancel data offer API as specified in R1AP [4], clause 7.6.4.2. The expected outcome is successful validation of the request from the DUT. - -#### 13.1.2.2.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the terminate data offer procedure as defined in R1GAP [1], clause 5.2.7. - -- 2) A data offer exists in test simulator and the dataOfferId is known to the DUT. - -### 13.1.2.2.3 Test methodology - -#### 13.1.2.2.3.1 Initial conditions - -1. The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. -2. The dataOfferId exists in the test simulator. - -#### 13.1.2.2.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to cancel a data offer. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.6.5.3. -- b) The HTTP request is a DELETE operation. -- c) The dataOfferId in the URI matches the data offer being deleted. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.6.4.2. - -Step 4. The test simulator generates and sends the appropriate HTTP response as specified in R1AP[4], clause 7.6.4.2.1. - -#### 13.1.2.2.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 13.2 Conformance test cases for SMO/Non-RT RIC framework - -### 13.2.1 General - -#### 13.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the DME Data offer service, and the purpose of the test scenarios is to validate that it conforms to the API Producer functionality as specified in R1AP [4], clause 7.6.4. - -#### 13.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a rApp. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Producer functionality as specified in R1AP [4], clause 7.6.4. - -## 13.2.2 Data offer API as API Producer test scenario - -### 13.2.2.1 Create data offer (positive case) - -#### 13.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the create data offer API as specified in R1AP [4], clause 7.6.4.1. The expected outcome is successful validation of the request from the DUT. - -#### 13.2.2.1.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the create data offer procedure as defined in RIGAP [1], clause 5.2.7. - -#### 13.2.2.1.3 Test methodology - -##### 13.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -##### 13.2.2.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to create a data offer. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a POST request. -- b) The URI conforms to the format specified in R1AP [4], clause 7.6.5.2.3.1. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.6.4.1. - -Step 4. The DUT generates the data offer and constructs the URI for the created resource. - -Step 5. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.6.4.1. - -Step 6. At the test simulator the contents of the received HTTP response is recorded. - -Step 7. The test simulator does the following validation: - -- a) The HTTP response message content includes the information as specified in R1AP [4], clause 7.6.4.1, and the Location header will be present. -- b) The URI conforms to the format specified in R1AP [4], clause 7.6.5.3. - -#### 13.2.2.1.4 Expected result - -The test is considered passed if Step 7 validation has passed. - -### 13.2.2.2 Cancel data offer (positive case) - -#### 13.2.2.2.1 Test description and applicability - -The purpose of this test case is to test the Cancel data offer API as specified in R1AP [4], clause 7.6.4.2. The expected outcome is successful validation of the request from the DUT. - -#### 13.2.2.2.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the cancel data request procedure as defined in R1GAP [1], clause 5.2.7. -- 2) A data offer exists in DUT and the dataOfferId is known to the test simulator. - -#### 13.2.2.2.3 Test methodology - -##### 13.2.2.2.3.1 Initial conditions - -- 1) The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. -- 2) The dataOfferId is known to the DUT - -##### 13.2.2.2.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to cancel a data offer. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.6.5.3.3.1. -- b) The HTTP request is a DELETE operation. -- c) The dataOfferId in the URI match the data offer being deleted. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 7.6.4.2. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.6.4.2. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 7.6.5.3. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 7.6.4.2. - -##### 13.2.2.2.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -#### 13.2.2.3 Notify data offer termination (positive case) - -##### 13.2.2.3.1 Test description and applicability - -The purpose of this test case is to test the Notify data offer termination API as specified in R1AP [4], clause 7.6.4.3. The expected outcome is successful validation of the request from the DUT. - -##### 13.2.2.3.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Notify data offer termination procedure as defined in R1GAP [1], clause 5.2.7. -- 2) A data offer exists in the DUT. - -### 13.2.2.3.3 Test methodology - -#### 13.2.2.3.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -#### 13.2.2.3.3.2 Procedure - -Step 1. The DUT as an API producer initiates the sending of a HTTP POST request. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The HTTP request is a POST operation. -- b) The callback URI matches the URI provided in the data offer. - -Step 4. The test simulator sends the HTTP response as specified in RIAP [4], clause 7.6.4.3. - -#### 13.2.2.3.4 Expected result - -The test is considered passed if Step 3 validation has passed. - ---- - -## 14 SME Boot strap service test cases - -### 14.1 Conformance test cases for rApp - -#### 14.1.1 General - -##### 14.1.1.1 Device under test requirements - -The rApp that acts as Device Under Test (DUT) in these test scenarios, the requirements on the DUT for these tests are that it can handle the Bootstrap service, and the purpose of the test scenarios is to validate that it confirms API Consumer functionality as specified in RIAP [4], clause 6.4.4. - -##### 14.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance API Producer functionality as specified in RIAP [4], clause 6.4.4. - -## 14.1.2 Bootstrap API as API Consumer test scenario - -### 14.1.2.1 Query bootstrap information (positive case) - -#### 14.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the Bootstrap APIs operation as specified in R1AP [4], clause 6.4.4.1. The expected outcome is successful validation of the request from the DUT. - -#### 14.1.2.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Discover bootstrap procedure. -- 2) A BootstrapInformation exist in the test simulator. - -#### 14.1.2.1.3 Test methodology - -##### 14.1.2.1.3.1 Initial conditions - -- 1) The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 14.1.2.1.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to BootstrapAPIs. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 6.4.5.2. -- b) The HTTP request is a GET operation. -- c) The message body is empty. - -Step 4. The test simulator generated the appropriate HTTP response as specified in R1AP [4], clause 6.4.5.2.3.1. - -NOTE: Presence or validation of optional filter parameters is not used to determine validation on this test. - -#### 14.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 14.2 Conformance test cases for SMO/Non-RT RIC framework - -### 14.2.1 General - -#### 14.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as Device Under Test (DUT) in these test scenarios, the requirements on the DUT for these tests are that it can handle the Bootstrap service, and the purpose of the test scenarios is to validate that it conforms to the Bootstrap API specified in R1AP [4], clause 6.4.4. - -#### 14.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as specified in section 4.3.2. In addition, it has the following capabilities: - -- 1) Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- 2) Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to API Producer functionality as specified in R1AP [4], clause 6.4.4. - -## 14.2.2 Bootstrap API as API Producer test scenario - -### 14.2.2.1 Query bootstrap information (positive case) - -#### 14.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the Bootstrap APIs as specified in R1AP [4], clause 6.4.4.1. The expected outcome is successful validation of the response from the DUT. - -#### 14.2.2.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Discover bootstrap procedure. -- 2) A BootstrapInformation exist in the test simulator. - -#### 14.2.2.1.3 Test methodology - -##### 14.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -##### 14.2.2.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to Bootstrap API for bootstrap information. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a GET request. -- b) The URI conforms to the format as specified in R1AP [4], clause 6.2.5.2. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 6.2.5.2. - -Step 4. The DUT initiates a HTTP Response. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 6.2.5.2. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause. 6.2.5.2. - -#### 14.2.2.1.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -## 15 AI/ML workflow AI/ML model registration API test cases - -### 15.1 Conformance test cases for rApp - -#### 15.1.1 General - -##### 15.1.1.1 Device under test requirements - -The rApp that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the AI/ML model registration service, and the purpose of the test scenarios is to validate that it conforms to the API Consumer functionality as specified in R1AP [4], clause 10.1.4. - -##### 15.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Consumer functionality as specified in R1AP [4], clause 10.1.4. - -#### 15.1.2 AI/ML model registration API as API consumer test scenario - -##### 15.1.2.1 Register model information (positive case) - -###### 15.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the Register AI/ML model information in AI/ML model registration API as specified in R1AP [4], clause 10.1. The expected outcome is successful validation of the request from the DUT. - -###### 15.1.2.1.2 Test entrance criteria - -The DUT has functionality to initiate the Register AI/ML model procedure as defined in R1GAP [1], clause 5.6.2. - -NOTE: The DUT provides the ModelRelatedInformation as defined in R1AP [4], clause 10.1.4. - -###### 15.1.2.1.3 Test methodology - -###### 15.1.2.1.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 15.1.2.1.3.2 Procedure - -- Step 1. The DUT as an API Consumer initiates a HTTP request to register an AI/ML model by providing ModelRelatedInformation. -- Step 2. At the test simulator the contents of the received HTTP request is recorded. -- Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 10.1.5.2.2. -- b) The HTTP request is a POST operation. -- c) The HTTP request message content includes ModelRelatedInformation as specified in R1AP [4], clause 10.1.4. - -Step 4. The test simulator generates the registrationId and constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4], clause 10.1.5.2.3.1. - -#### 15.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 15.1.2.2 Deregister model information (positive case) - -#### 15.1.2.2.1 Test description and applicability - -The purpose of this test case is to test the Deregister the registered model information in AI/ML model registration API as specified in R1AP [4], clause 10.1.4. The expected outcome is successful validation of the request from the DUT. - -#### 15.1.2.2.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Deregister AI/ML model procedure as defined in R1GAP [1], clause 5.6.2.2. -- 2) A ModelRelatedInformation exists in test simulator and the registrationId is known to the DUT. - -#### 15.1.2.2.3 Test methodology - -##### 15.1.2.2.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 15.1.2.2.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to Deregister an AI/ML model information. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 10.1.5.3.2. -- b) The HTTP request is a DELETE operation. -- c) The registrationId in the URI match the ModelRelatedInformation being deregistered. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 10.1.5.3.3. - -Step 4. The test simulator generated the appropriate HTTP response as specified in R1AP [4], clause 10.1.5.3.3 - -#### 15.1.2.2.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 15.1.2.3 Query model information (positive case) - -#### 15.1.2.3.1 Test description and applicability - -The purpose of this test case is to test the Query model registration information in AI/ML model registration API as specified in R1AP [4], clause 10.1.4.4. The expected outcome is successful validation of the request from the DUT. - -#### 15.1.2.3.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the query AI/ML model registration procedure as defined in RIGAP [1], clause 5.6.2.2. -- 2) A ModelRelatedInformation exists in test simulator and the registrationId is known to the DUT. - -#### 15.1.2.3.3 Test methodology - -##### 15.1.2.3.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 15.1.2.3.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query a ModelRelatedInformation. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 10.1.5.3.2. -- b) The HTTP request is a GET operation. -- c) The registrationId in the URI match the AI/ML model being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 10.1.5.3.3. - -Step 4. The test simulator generated the appropriate HTTP response as specified in R1AP [4], clause 10.1.5.3.3. - -#### 15.1.2.3.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 15.1.2.4 Update model information (positive case) - -#### 15.1.2.4.1 Test description and applicability - -The purpose of this test case is to test the Update registered model information in AI/ML model API as specified in R1AP [4], clause 10.1.4.3. The expected outcome is successful validation of the request from the DUT. - -#### 15.1.2.4.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Update AI/ML model registration procedure as defined in RIGAP [1], clause 5.6.2.2. -- 2) An AI/ML model exists in test simulator and the registrationId and ModelRelatedInformation are known to the DUT. - -#### 15.1.2.4.3 Test methodology - -##### 15.1.2.4.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 15.1.2.4.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to update a registered AI/ML model identified by the registrationId and ModelRelatedInformation. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 10.1.5.3.2. -- b) The HTTP request is a PUT operation. -- c) The `registrationId` and `ModelRelatedInformation` in the URI match the AI/ML model being updated. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 10.1.5.3.3. - -Step 4. The test simulator updates the resource, and a representation of the updated resource shall be returned in the response body the appropriate HTTP response as specified in R1AP [4], clause 10.1.5.3.3. - -#### 15.1.2.4.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 15.2 Conformance test cases for SMO/Non-RT RIC framework - -### 15.2.1 General - -#### 15.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the AI/ML model registration service, and the purpose of the test scenarios is to validate that it conforms to the API Producer functionality as specified in R1AP [4], clause 10.1.4. - -#### 15.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a rApp. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Producer functionality as specified in R1AP [4], clause 10.1.4. - -### 15.2.2 AI/ML model registration API as API Producer test scenario - -#### 15.2.2.1 Register model information (positive case) - -##### 15.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the Register AI/ML model information in AI/ML model registration API as specified in R1AP [4], clause 10.1.4. The expected outcome is successful validation of the request from the DUT. - -##### 15.2.2.1.2 Test entrance criteria - -The test simulator has functionality to initiate the Register AI/ML model procedure as defined in R1GAP [1], clause 5.6.2. - -### 15.2.2.1.3 Test methodology - -#### 15.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -#### 15.2.2.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to register a ModelRelatedInformation. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a POST request. -- b) The URI conforms to the format specified in R1AP [4], clause 10.1.5.2.2. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 10.1.5.2.3.1. - -Step 4. The DUT generates the registrationId and constructs the URI for the created resource. - -Step 5. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 10.1.5.2.3.1. - -Step 6. At the test simulator the contents of the received HTTP response is recorded. - -Step 7. The test simulator does the following validation: - -- a) The HTTP response message content includes the information as specified in R1AP [4], clause 10.1.5.2.3.1, and the Location header will be present. -- b) The URI conforms to the format specified in R1AP [4], clause 10.1.5.2.2. - -### 15.2.2.1.4 Expected result - -The test is considered passed if Step 7 validation has passed. - -## 15.2.2.2 Deregister model information (positive case) - -### 15.2.2.2.1 Test description and applicability - -The purpose of this test case is to test the Deregister registered AI/ML model information in AI/ML model registration API as specified in R1AP [4], clause 10.1.4. The expected outcome is successful validation of the request from the DUT. - -### 15.2.2.2.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the AI/ML model procedure as defined in R1GAP [1], clause 5.6.2.2. -- 2) A ModelRelatedInformation exists in test simulator and the registrationId is known to the DUT. - -### 15.2.2.2.3 Test methodology - -#### 15.2.2.2.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -#### 15.2.2.2.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to Deregister an AI/ML model information. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 10.1.5.3.2. -- b) The HTTP request is a DELETE operation. -- c) The registrationId in the URI match the ModelRelatedInformation being deregistered. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 10.1.5.3.3. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 10.1.5.3.3. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 10.1.5.3.2. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 10.1.5.3.3. - -#### 15.2.2.2.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 15.2.2.3 Query model information (positive case) - -#### 15.2.2.3.1 Test description and applicability - -The purpose of this test case is to test the Query model registration information in AI/ML model registration API as specified in R1AP [4], clause 10.1.4.4. The expected outcome is successful validation of the request from the DUT. - -#### 15.2.2.3.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the query AI/ML model registration procedure as defined in R1GAP [1], clause 5.6.2.2. -- 2) A ModelRelatedInformation exists in test simulator and the registrationId is known to the DUT. - -#### 15.2.2.3.3 Test methodology - -##### 15.2.2.3.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -##### 15.2.2.3.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to query a ModelRelatedInformation. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 10.1.5.3.2. -- b) The HTTP request is a GET operation. -- c) The registrationId in the URI match the AI/ML model being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 10.1.5.3.3. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 10.1.5.3.3. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 10.1.5.3.2. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 10.1.5.3.3. - -#### 15.2.2.3.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 15.2.2.4 Update model information (positive case) - -#### 15.2.2.4.1 Test description and applicability - -The purpose of this test case is to test the Update registered model information in AI/ML model API as specified in R1AP [4], clause 10.1.4.3. The expected outcome is successful validation of the request from the DUT. - -#### 15.2.2.4.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Update AI/ML model registration procedure as defined in R1GAP [1], clause 5.6.2.2 -- 2) An AI/ML model exists in test simulator and the registrationId and ModelRelatedInformation are known to the DUT. - -#### 15.2.2.4.3 Test methodology - -##### 15.2.2.4.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -##### 15.2.2.4.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to update an AI/ML model information identified by the registrationId and ModelRelatedInformation. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a PUT request. -- b) The URI conforms to the format specified in R1AP [4], clause 10.1.5.3.2. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 10.1.5.3.3. - -Step 4. The DUT generates the registrationId and constructs the URI for the created resource. - -Step 5. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 10.1.5.3.3. - -Step 6. At the test simulator the contents of the received HTTP response is recorded. - -Step 7. The test simulator does the following validation: - -- a) The HTTP response message content includes the information as specified in R1AP [4], clause 10.1.5.3.3. -- b) The URI conforms to the format specified in R1AP [4], clause 10.1.5.3.2. - -#### 15.2.2.4.4 Expected result - -The test is considered passed if Step 7 validation has passed. - ---- - -## 16 AI/ML workflow AI/ML model discovery API test cases - -### 16.1 Conformance test cases for rApp - -#### 16.1.1 General - -##### 16.1.1.1 Device under test requirements - -The rApp that acts as Device Under Test (DUT) in these test scenarios, the requirements on the DUT for these tests are that it can handle the AI/ML model discovery service, and the purpose of the test scenarios is to validate that it conforms to the AI/ML model discovery API specified in R1AP [4], clause 10.2.4. - -##### 16.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance API Producer functionality as specified in R1AP [4], clause 10.2.4. - -#### 16.1.2 AI/ML model discovery API as API Consumer test scenario - -##### 16.1.2.1 Discover AI/ML models (positive case) - -###### 16.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the Discover registered AI/ML models as specified in R1AP [4], clause 10.2.4.1. The expected outcome is successful validation of the request from the DUT. - -###### 16.1.2.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Discover AI/ML model procedure. -- 2) A set of ModelRelatedInformation exist in the test simulator. - -###### 16.1.2.1.3 Test methodology - -###### 16.1.2.1.3.1 Initial conditions - -- 1) The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 16.1.2.1.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to Discover registered AI/ML models. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 10.2.5.2.2. -- b) The HTTP request is a GET operation. -- c) The message body is empty. - -Step 4. The test simulator generated the appropriate HTTP response as specified in R1AP [4], clause 10.2.5.2.3.1 - -NOTE: Presence or validation of optional filter parameters is not used to determine validation on this test. - -#### 16.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 16.1.2.2 Query AI/ML models (positive case) - -#### 16.1.2.2.1 Test description and applicability - -The purpose of this test case is to test the Query AI/ML models API as specified in R1AP [4], clause 10.2.4.2. The expected outcome is successful validation of the request from the DUT. - -#### 16.1.2.2.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Discover AI/ML model procedure as defined in R1GAP [1], clause 5.6.4. -- 2) A model exists in the test simulator and the modelId is known to the DUT - -#### 16.1.2.2.3 Test methodology - -##### 16.1.2.2.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 16.1.2.2.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to Query registered AI/ML models. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 10.2.5.3.2. -- b) The HTTP request is a GET operation. -- c) The modelId in the URI match the model being queried. - -Step 4. The test simulator generated the appropriate HTTP response as specified in R1AP [4], clause 10.2.4.2 - -#### 16.1.2.2.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 16.2 Conformance test cases for SMO/Non-RT RIC framework - -### 16.2.1 General - -#### 16.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as Device Under Test (DUT) in these test scenarios, the requirements on the DUT for these tests are that it can handle the AI/ML model discovery service, and the purpose of the test scenarios is to validate that it conforms to the AI/ML model discovery API specified in R1AP [4], clause 10.2.4. - -#### 16.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as specified in section 4.3.2. In addition, it has the following capabilities: - -- 1) Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- 2) Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to API Producer functionality as specified in R1AP [4], clause 10.2.4. - -### 16.2.2 AI/ML model discovery API as API Producer test scenario - -#### 16.2.2.1 Discover AI/ML models (positive case) - -##### 16.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the AI/ML model discovery APIs as specified in R1AP [4], clause 10.2.4. The expected outcome is successful validation of the response from the DUT. - -##### 16.2.2.1.2 Test entrance criteria - -- 1) The DUT supports the functionality to Discover AI/ML model procedure. -- 2) A set of ModelRelatedInformation are supported in the test simulator. - -##### 16.2.2.1.3 Test methodology - -###### 16.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -###### 16.2.2.1.3.2 Procedure - -- Step 1. The test simulator as an API Consumer initiates a HTTP request to AI/ML model discovery APIs for registered AI/ML models. -- Step 2. The DUT receives the HTTP request. -- Step 3. The DUT does the following validation: - - a) The HTTP request is a GET request. - - b) The URI conforms to the format as specified in R1AP [4], clause 10.2.5.2.2 - - c) The HTTP request message content includes the information as specified in R1AP [4], clause 10.2.5.2.3.1. - -Step 4. The DUT initiates a HTTP Response. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 10.2.5.2.2. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 10.2.5.2.3.1. - -#### 16.2.2.1.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 16.2.2.2 Query AI/ML models (positive case) - -#### 16.2.2.2.1 Test description and applicability - -The purpose of this test case is to test the Query AI/ML model API as specified in R1AP [4], clause 10.2.4.2. The expected outcome is successful validation of the response from the DUT. - -#### 16.2.2.2.2 Test entrance criteria - -- 1) The DUT supports the functionality to Discover AI/ML model procedure. -- 2) A model exists in the DUT and the modelId is known to the test simulator. - -#### 16.2.2.2.3 Test methodology - -##### 16.2.2.2.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -##### 16.2.2.2.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to Query a registered AI/ML models. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a GET request. -- b) The URI conforms to the format as specified in R1AP [4], clause 10.2.5.3.2 -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 10.2.4.2. - -Step 4. The DUT initiates a HTTP Response. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 10.2.5.3.2. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 10.2.4.2. - -#### 16.2.2.2.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -## 17 RAN OAM Configuration management service test cases - -### 17.1 Conformance test cases for rApp - -#### 17.1.1 General - -##### 17.1.1.1 Device under test requirements - -The rApp that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the RAN OAM Configuration management service, and the purpose of the test scenarios is to validate that it conforms to the API Consumer functionality as specified in R1AP [4], clause 8.1.4. - -##### 17.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Consumer functionality as specified in R1AP [4], clause 8.1.4. - -#### 17.1.2 Configuration management API as API Consumer test scenario - -##### 17.1.2.1 Read configuration data (positive case) - -###### 17.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the read configuration data API as specified in R1AP [4], clause 8.1.4.1. The expected outcome is successful validation of the request from the DUT. - -###### 17.1.2.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the read configuration data procedure as defined in R1GAP [1], clause 5.4.5. -- 2) A managed entity with configuration data exists in the test simulator and the URI parameter and className are known to the DUT - -###### 17.1.2.1.3 Test methodology - -###### 17.1.2.1.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 17.1.2.1.3.2 Procedure - -- Step 1. The DUT as an API Consumer initiates a HTTP request to read configuration data. -- Step 2. At the test simulator the contents of the received HTTP request is recorded. -- Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 8.1.4.1. -- b) The HTTP request is a GET operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 8.1.4.1. - -Step 4. The test simulator sends the appropriate HTTP response as specified in R1AP [4], clause 8.1.4.1.1. - -#### 17.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 17.1.2.2 Write configuration changes (positive case) - -#### 17.1.2.2.1 Test description and applicability - -The purpose of this test case is to test the Write configuration changes API as specified in R1AP [4], clause 8.1.4.2. The expected outcome is successful validation of the request from the DUT. - -#### 17.1.2.2.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the write configuration procedure as defined in R1GAP [1], clause 5.4.5. -- 2) A managed entity with configuration data exists in the test simulator and the URI parameter and className are known to the DUT - -#### 17.1.2.2.3 Test methodology - -##### 17.1.2.2.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 17.1.2.2.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to write a configuration change identified by the URI parameter and className. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 8.1.5.2. -- b) The HTTP request is a PATCH operation. -- c) The URI matches the configuration being changed. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 8.1.4.2. - -Step 4. The test simulator sends the appropriate HTTP response as specified in R1AP [4], clause 8.1.4.2.1. - -#### 17.1.2.2.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 17.1.3 Configuration schema information API as API Consumer test scenario - -#### 17.1.3.1 Get all schema information (positive case) - -##### 17.1.3.1.1 Test description and applicability - -The purpose of this test case is to test the Get all schema information in the Configuration schema information API as specified in R1AP [4], clause 8.3.4.1. The expected outcome is successful validation of the request from the DUT. - -##### 17.1.3.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Get schemas procedure as defined in R1GAP [1], clause 5.4.5. -- 2) A set of schemas exists in the test simulator. - -##### 17.1.3.1.3 Test methodology - -###### 17.1.3.1.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 17.1.3.1.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to get all schema information for a set of schemas. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 8.3.5.2. -- b) The HTTP request is a GET operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 8.3.4.1.1. - -Step 4. The test simulator generates and sends the appropriate HTTP response as specified in R1AP [4], clause 8.3.4.1.1 - -##### 17.1.3.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -#### 17.1.3.2 Get individual schema information (positive case) - -##### 17.1.3.2.1 Test description and applicability - -The purpose of this test case is to test the Get individual schema information in the Configuration schema information API as specified in R1AP [4], clause 8.3.4.2. The expected outcome is successful validation of the request from the DUT. - -##### 17.1.3.2.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Get schemas procedure as defined in R1GAP [1], clause 5.4.5. -- 2) At least one schema exists in the test simulator and the schemaId is known to the DUT - -### 17.1.3.2.3 Test methodology - -#### 17.1.3.2.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -#### 17.1.3.2.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to get schema information for a schema. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 8.3.5.3. -- b) The HTTP request is a GET operation. -- c) The schemaId in the URI matches the schema information being requested. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 8.3.4.2.1. - -Step 4. The test simulator generates and sends the appropriate HTTP response as specified in R1AP [4], clause 8.3.4.2.1. - -#### 17.1.3.2.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 17.2 Conformance test cases for SMO/Non-RT RIC framework - -### 17.2.1 General - -#### 17.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as DUT in the test scenarios, the requirements on the DUT for these tests are that it can handle the RAN OAM **Configuration management**, and the purpose of the test scenarios is to validate that it conforms to the API Producer functionality as specified in R1AP [4] clause 8.1.4. - -#### 17.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a rApp. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Producer functionality as specified in R1AP **Error! Reference source not found.** clause 8.1.4. - -## 17.2.2 Configuration management as API Producer test scenario - -### 17.2.2.1 Read configuration data (positive case) - -#### 17.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the read configuration data API as specified in R1AP **Error! Reference source not found.** clause 8.1.4.1. The expected outcome is successful validation of the response from the DUT. - -#### 17.2.2.1.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Read configuration procedure as defined in R1GAP **Error! Reference source not found.** clause 5.4.5. -- 2) A managed entity with configuration data exists in the test simulator and the URI parameter and className are known to the test simulator - -#### 17.2.2.1.3 Test methodology - -##### 17.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -##### 17.2.2.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to read configuration data. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a GET request. -- b) The URI conforms to the format specified in R1AP **Error! Reference source not found.** clause 8.1.5.2. -- c) The HTTP request message content includes the information as specified in R1AP **Error! Reference source not found.** clause 8.1.4.1. - -Step 4. The DUT sends the appropriate HTTP response (200 OK) with configuration data as specified in R1AP [4] clause 8.1.4.1. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The HTTP response message content includes the configuration data as specified in R1AP [4] clause 8.1.4.1 and Clause 8.1.8 (Data model). -- b) The response URI conforms to the format specified in R1AP [4] clause 8.1.5.2. - -#### 17.2.2.1.4 Expected result - -The test is considered passed if Step 6 validations succeed. - -## 17.2.2.2 Write configuration changes (positive case) - -### 17.2.2.2.1 Test description and applicability - -The purpose of this test case is to test the Write configuration changes API as specified in R1AP **Error! Reference source not found.** clause 8.1.4.2. The expected outcome is successful validation of the response from the DUT. - -### 17.2.2.2.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the write configuration procedure as defined in R1GAP **Error! Reference source not found.** clause 5.4.5. -- 2) A managed entity with configuration data exists in the test simulator and the URI parameter and className are known to the test simulator. - -### 17.2.2.2.3 Test methodology - -#### 17.2.2.2.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -#### 17.2.2.2.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to write a configuration change identified by the URI parameter and className. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP **Error! Reference source not found.** clause 8.1.5.2.3.2. -- b) The HTTP request is a PATCH operation. -- c) The URI Parameter and className in the URI match the configuration being changed. -- d) The HTTP request message content includes the information as specified in R1AP **Error! Reference source not found.** clause 8.1.4.2 and Clause 8.1.8 for Data model. - -Step 4. The DUT sends the appropriate HTTP response (200 OK or 204 No Content) as specified in R1AP [4] clause 8.1.4.2. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- c) The response URI conforms to the format specified in R1AP [4] clause 8.1.5.2. -- d) The HTTP response message content includes the information as specified in R1AP **Error! Reference source not found.** clause 8.1.4.2. - -#### 17.2.2.2.4 Expected result - -The test is considered passed if Step 6 validations succeed. - -## 17.2.3 Configuration schema information API as API Producer test scenario - -### 17.2.3.1 Get all schema information (positive case) - -#### 17.2.3.1.1 Test description and applicability - -The purpose of this test case is to test the Get all schema information in the Configuration schema information API clause 8.3.4.1. The expected outcome is successful validation of the request from the DUT. - -#### 17.2.3.1.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Get schemas procedure as defined in R1GAP [1], clause 5.4.5. -- 2) A set of schemas exists in the DUT. - -#### 17.2.3.1.3 Test methodology - -##### 17.2.3.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -##### 17.2.3.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to get all schema information for a set of schemas. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 8.3.5.2. -- b) The HTTP request is a GET operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 8.3.4.1.1. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 8.3.4.1.1 - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The HTTP response message content includes the information as specified in R1AP [4], clause 8.3.4.1.1. - -#### 17.2.3.1.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -## 17.3.1.2 Get individual schema information (positive case) - -### 17.3.1.2.1 Test description and applicability - -The purpose of this test case is to test the Get individual schema information in the Configuration schema information API clause 8.3.4.2. The expected outcome is successful validation of the request from the DUT. - -### 17.3.1.2.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Get schemas procedure as defined in R1GAP [1], clause 5.4.5. -- 2) At least one schema exists in the DUT and the schemaId is known to the test simulator - -### 17.3.1.2.3 Test methodology - -#### 17.3.1.2.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -#### 17.3.1.2.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to get schema information for a schema. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 8.3.5.3. -- b) The HTTP request is a GET operation. -- c) The schemaId in the URI matches the schema information being requested. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 8.3.4.2.1. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 8.3.4.2.1. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The HTTP response message content includes the information as specified in R1AP [4], clause 8.3.4.2.1. - -#### 17.3.1.2.4 Expected result - -The test is considered passed if Step 6 validation has passed. - ---- - -## 18 RAN OAM Fault management service test cases - -### 18.1 Conformance test cases for rApp - -#### 18.1.1 General - -##### 18.1.1.1 Device under test requirements - -The rApp that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the RAN OAM Configuration management service, and the purpose of the test scenarios is to validate that it conforms to the API Consumer functionality as specified in R1AP [4], clause 8.2.4. 18.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. -- Validating messages and issuing verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Consumer functionality as specified in R1AP [4] clause 8.2.4. - -## 18.1.2 Fault management API as API Consumer test scenario - -### 18.1.2.1 Query alarms (positive case) - -#### 18.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the Query alarms API as specified in R1AP [4] clause 8.2.4.1. The expected outcome is successful validation of the request from the DUT. - -#### 18.1.2.1.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Query alarms procedure as defined in R1GAP [1] clause 5.4.3. -- 2) A list of alarms exists in the test simulator and the URI parameter, className and alarmListId are known to the DUT. - -#### 18.1.2.1.3 Test methodology - -##### 18.1.2.1.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 18.1.2.1.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to query alarms. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4] clause 8.2.5.2. -- b) The HTTP request is a GET operation. -- c) The HTTP request message content includes the information as specified in R1AP [4] clause 8.2.5.2. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4] clause 8.2.4.1.1. - -#### 18.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. 18.1.2.2 Change alarm acknowledgement state (positive case) - -### 18.1.2.2.1 Test description and applicability - -The purpose of this test case is to test the Change alarm acknowledgement state API as specified in R1AP [4] clause 8.2.4.2. The expected outcome is successful validation of the request from the DUT. - -#### 18.1.2.2.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Change alarm acknowledgement state procedure as defined in R1GAP [1] clause 5.4.3. -- 2) A list of alarms exists in the test simulator and the URI parameter, className and alarmListId are known to the DUT. - -### 18.1.2.2.3 Test methodology - -#### 18.1.2.2.3.1 Initial conditions - -- 1) The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. -- 2) The alarm list identifier is known to the test simulator and the resource URI either “SubNetwork” or “ManagedElement” as the class name, the related object instance identifier for the alarmListId is known to DUT. - -#### 18.1.2.2.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to change the alarm acknowledgement state identified by the URI parameter, className and alarmListId. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4] clause 8.2.5.2. -- b) The HTTP request is a PATCH operation. -- c) The URI Parameter and className in the URI match the alarmListId alarm acknowledgement state being changed. -- d) The HTTP request message content includes the information as specified in R1AP [4] clause 8.2.5.2. - -Step 4. The test simulator constructs the URI for the created resource and sends the appropriate HTTP response as specified in R1AP [4] clause 8.2.5.2. - -#### 18.1.2.2.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 18.2 Conformance test cases for SMO/Non-RT RIC framework - -### 18.2.1 General - -#### 18.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as DUT in the test scenarios, the requirements on the DUT for these tests are that it can handle the Fault management service, and the purpose of the test scenarios is to validate that it conforms to the API Producer functionality as specified in R1AP [4] clause 8.2.4. - -#### 18.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a rApp. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT’s conformance to the API Producer functionality as specified in R1AP **Error! Reference source not found.** clause 8.2.4. - -## 18.2.2 Fault management as API Producer test scenario - -### 18.2.2.1 Query alarms (positive case) - -#### 18.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the Query alarms API as specified in R1AP **Error! Reference source not found.** clause 8.2.4.1. The expected outcome is successful validation of the response from the DUT. - -#### 18.2.2.1.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Query alarms procedure as defined in R1GAP **Error! Reference source not found.** clause 5.4.3. -- 2) A list of alarms exists in the test simulator and the URI parameter, className and alarmListId are known to the test simulator - -#### 18.2.2.1.3 Test methodology - -##### 18.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -##### 18.2.2.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to query alarms. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a GET request. -- b) The URI conforms to the format specified in R1AP **Error! Reference source not found.** clause 8.2.5.2.3.1. -- c) The HTTP request message content includes the information as specified in R1AP **Error! Reference source not found.** clause 8.2.5.2.3.1 - -Step 4. The DUT sends the appropriate HTTP response (200 OK) with the alarm list as specified in R1AP **Error! Reference source not found.** clause 8.2.5.2.3.1 - -Step 5. At the test simulator the contents of the received HTTP response. - -Step 6. The test simulator does the following validation: - -- a) The HTTP response code is 200 OK -- b) The HTTP response message content includes the information as specified in R1AP **Error! Reference source not found.,** clause 8.2.5.2.3.1 and clause 8.2.8 for Data model. - -#### 18.2.2.1.4 Expected result - -The test is considered passed if Step 6 validations succeed. - -## 18.2.2.2 Change alarm acknowledgement state (positive case) - -### 18.2.2.2.1 Test description and applicability - -The purpose of this test case is to test the Change alarm acknowledgement state API as specified in R1AP **Error! Reference source not found.** clause 8.2.4.2. The expected outcome is successful validation of the request from the DUT. - -### 18.2.2.2.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Change alarm acknowledgement state procedure as defined in R1GAP **Error! Reference source not found.** clause 5.4.3. -- 2) A list of alarms exists in the test simulator and the URI parameter, className and alarmListId are known to the test simulator. - -### 18.2.2.2.3 Test methodology - -#### 18.2.2.2.3.1 Initial conditions - -1. The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. -2. The alarm list identifier is known to the DUT and the resource URI (either “SubNetwork“ or “ManagedElement“ as the class name) and the related object instance identifier for the alarmListId is known to test simulator. - -#### 18.2.2.2.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to change the alarm acknowledgement state identified by the URI parameter, className and alarmListId. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP **Error! Reference source not found.** clause 8.2.5.2.3.2. -- b) The HTTP request is a PATCH operation. -- c) The URI Parameter and className and alarmListId, match the alarm acknowledgement state being changed. -- d) The HTTP request message content includes the information as specified in R1AP **Error! Reference source not found.** clause 8.2.5.2.3.2. - -Step 4. The DUT sends the appropriate HTTP response (200 OK or 204 No Content) as specified in R1AP **Error! Reference source not found.** clause 8.2.5.2.3.2. - -Step 5. At the test simulator the contents of the received HTTP response. - -Step 6. The test simulator does the following validation: - -- a) The HTTP response code is 200 OK or 204 No Content. -- b) The HTTP response message content includes the information as specified in R1AP **Error! Reference source not found.** clause 8.2.5.2.3.2 and clause 8.2.8 for Data model. - -#### 18.2.2.2.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -## 19 DME Data delivery service test cases - -### 19.1 Conformance test cases for rApp - -#### 19.1.1 General - -##### 19.1.1.1 Device under test requirements - -The rApp acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the DME Data delivery service, and the purpose of the test scenarios is to validate that it conforms to the API Producer functionality as specified in R1AP [4], clause 7.4.4. - -##### 19.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Producer functionality as specified in R1AP [4], clause 7.4.4. - -#### 19.1.2 HTTP based Push data API as API producer test scenario - -##### 19.1.2.1 Push data (positive case) - -###### 19.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the Push data in the HTTP based Push data API as specified in R1AP [4], clause 7.4.4.1. The expected outcome is successful validation of the request from the DUT. - -###### 19.1.2.1.2 Test entrance criteria - -The DUT has functionality to initiate the Push data procedure as defined in R1GAP [1], clause 5.2.6. - -##### 19.1.2.1.3 Test methodology - -###### 19.1.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -###### 19.1.2.1.3.2 Procedure - -Step 1. The DUT as an API Producer initiates a HTTP request to push a data payload. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.4.5.2.2. -- b) The HTTP request is a POST operation. - -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.4.4.1.1. - -Step 4. The test simulator generates and sends the appropriate HTTP response as specified in R1AP [4], clause 7.4.4.1.1. - -#### 19.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 19.1.3 HTTP based Pull data API as API Consumer test scenario - -#### 19.1.3.1 Pull data (positive case) - -##### 19.1.3.1.1 Test description and applicability - -The purpose of this test case is to test the Pull data in the HTTP based Pull data API as specified in R1AP [4], clause 7.5.4.1. The expected outcome is successful validation of the request from the DUT. - -##### 19.1.3.1.2 Test entrance criteria - -The DUT has functionality to initiate the Pull data procedure as defined in R1GAP [1], clause 5.2.6. - -##### 19.1.3.1.3 Test methodology - -###### 19.1.3.1.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 19.1.3.1.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to pull a data payload. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.5.5.2.2. -- b) The HTTP request is a GET operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.5.4.1.1. - -Step 4. The test simulator generates and sends the appropriate HTTP response as specified in R1AP [4], clause 7.5.4.1.1. - -##### 19.1.3.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 19.2 Conformance test cases for SMO/Non-RT RIC framework - -### 19.2.1 General - -#### 19.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the DME Data delivery service, and the purpose of the test scenarios is to validate that it conforms to the API Producer functionality as specified in R1AP [4], clause 7.4.4. - -### 19.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a rApp. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Producer functionality as specified in R1AP [4], clause 7.4.4. - -## 19.2.2 HTTP based Push data API as API Consumer test scenario - -### 19.2.2.1 Push data (positive case) - -#### 19.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the Push data in the HTTP based Push data API as specified in R1AP [4], clause 7.4.4.1. The expected outcome is successful validation of the request from the DUT. - -#### 19.2.2.1.2 Test entrance criteria - -The DUT has functionality to initiate the Push data procedure as defined in R1GAP [1], clause 5.2.6. - -#### 19.2.2.1.3 Test methodology - -##### 19.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -##### 19.2.2.1.3.2 Procedure - -Step 1. The DUT as an API Producer initiates a HTTP request to push a data payload. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.4.5.2.2. -- b) The HTTP request is a POST operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.4.4.1.1. - -Step 4. The test simulator sends the appropriate HTTP response as specified in R1AP [4], clause 7.4.4.1.1. - -#### 19.2.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 19.2.3 HTTP based Pull data API as API Producer test scenario - -### 19.2.3.1 Pull data (positive case) - -#### 19.2.3.1.1 Test description and applicability - -The purpose of this test case is to test the Pull data in the HTTP based Pull data API as specified in R1AP [4], clause 7.5.4.1. The expected outcome is successful validation of the response from the DUT. - -#### 19.2.3.1.2 Test entrance criteria - -The test simulator has functionality to initiate the Pull data procedure as defined in R1GAP [1], clause 5.2.6. - -#### 19.2.3.1.3 Test methodology - -##### 19.2.3.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -##### 19.2.3.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to pull a data payload. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 7.5.5.2.2. -- b) The HTTP request is a GET operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 7.5.4.1.1. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 7.5.4.1.1. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The HTTP response message content includes the information as specified in R1AP [4], clause 7.5.4.1.1. - -#### 19.2.3.1.4 Expected result - -The test is considered passed if Step 6 validation has passed - -## 20 AI/ML workflow AI/ML model training API test cases - -### 20.1 Conformance test cases for rApp - -#### 20.1.1 General - -##### 20.1.1.1 Device under test requirements - -The rApp that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the AI/ML training services, and the purpose of the test scenarios is to validate that it conforms to the API Consumer functionality as specified in R1AP [4], clause 10.3.4. - -##### 20.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Consumer functionality as specified in R1AP [4], clause 10.3.4. - -#### 20.1.2 AI/ML model training API as API Consumer test scenario - -##### 20.1.2.1 Request AI/ML model training (positive case) - -###### 20.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the request AI/ML model training as specified in R1AP [4], clause 10.3.4.1. The expected outcome is successful validation of the request from the DUT. - -###### 20.1.2.1.2 Test entrance criteria - -The DUT has functionality to initiate the Request AI/ML model training procedure as defined in R1GAP [1], clause 5.6.8. - -##### 20.1.2.1.3 Test methodology - -###### 20.1.2.1.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 20.1.2.1.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request for AI/ML model training. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 10.3.5.2.2. -- b) The HTTP request is a POST operation. - -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 10.3.4.1.1. - -Step 4. The test simulator sent the appropriate HTTP response as specified in R1AP [4], clause 10.3.4.1.1. - -#### 20.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 20.1.2.2 Cancel AI/ML model training (positive case) - -#### 20.1.2.2.1 Test description and applicability - -The purpose of this test case is to test the cancel AI/ML model training as specified in R1AP [4], clause 10.3.4.2. The expected outcome is successful validation of the request from the DUT. - -#### 20.1.2.2.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Cancel AI/ML model training procedure as defined in R1GAP [1], clause 5.6.8. -- 2) A training job exists in the test simulator and the trainingJobId is known to the DUT. - -#### 20.1.2.2.3 Test methodology - -##### 20.1.2.2.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -##### 20.1.2.2.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP to cancel AI/ML model training. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 10.3.5.3.2. -- b) The HTTP request is a DELETE operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 10.3.4.2.1. - -Step 4. The test simulator sent the appropriate HTTP response as specified in R1AP [4], clause 10.3.4.2.1. - -#### 20.1.2.2.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -### 20.1.2.3 Query AI/ML model training job status (positive case) - -#### 20.1.2.3.1 Test description and applicability - -The purpose of this test case is to test the Query AI/ML model training job status as specified in R1AP [4], clause 10.3.4.3. The expected outcome is successful validation of the request from the DUT. - -#### 20.1.2.3.2 Test entrance criteria - -- 1) The DUT has functionality to initiate the Query AI/ML model training job status procedure as defined in R1GAP [1], clause 5.6.8. - -- 2) A training job exists in the test simulator and the trainingJobId is known to the DUT. - -### 20.1.2.3.3 Test methodology - -#### 20.1.2.3.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -#### 20.1.2.3.3.2 Procedure - -Step 1. The DUT as an API Consumer initiates a HTTP request to Query a training job status. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 10.3.5.4.2. -- b) The HTTP request is a GET operation. -- c) The trainingJobId in the URI match the training job status being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 10.3.4.3.1. - -Step 4. The test simulator sent the appropriate HTTP response as specified in R1AP [4], clause 10.3.4.3.1. - -#### 20.1.2.3.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 20.2 Conformance test cases for SMO/Non-RT RIC framework - -### 20.2.1 General - -#### 20.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as Device Under Test (DUT) in these test scenarios, the requirements on the DUT for these tests are that it can handle the AI/ML model training services, and the purpose of the test scenarios is to validate that it conforms to the AI/ML model training API specified in R1AP [4], clause 10.3.4. - -#### 20.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as specified in clause 4.3.2. In addition, it has the following capabilities: - -- 1) Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- 2) Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to API Producer functionality as specified in R1AP [4], clause 10.3.4. - -## 20.2.2 AI/ML model training API as API Producer test scenario - -### 20.2.2.1 Request AI/ML model training (positive case) - -#### 20.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the Request AI/ML model training APIs as specified in R1AP [4], clause 10.3.4.1. The expected outcome is successful validation of the response from the DUT. - -#### 20.2.2.1.2 Test entrance criteria - -The test simulator supports the functionality to initiate the Request AI/ML model training procedure as defined in R1GAP [1], clause 5.6.8. - -#### 20.2.2.1.3 Test methodology - -##### 20.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -##### 20.2.2.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request for AI/ML model training. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a POST request. -- b) The URI conforms to the format as specified in R1AP [4], clause 10.3.5.2.2 -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 10.3.4.1.1. - -Step 4. The DUT initiates a HTTP Response. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 10.3.5.2.2. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 10.3.4.1.1. - -#### 20.2.2.1.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 20.2.2.2 Cancel AI/ML model training (positive case) - -#### 20.2.2.2.1 Test description and applicability - -The purpose of this test case is to test the Cancel AI/ML model training APIs as specified in R1AP [4], clause 10.3.4.2. The expected outcome is successful validation of the response from the DUT. - -#### 20.2.2.2.2 Test entrance criteria - -The test simulator supports the functionality to initiate the Cancel AI/ML model training procedure as defined in R1GAP [1], clause 5.6.8. - -A training job exists in the DUT and the trainingJobId is known to the test simulator. - -### 20.2.2.2.3 Test methodology - -#### 20.2.2.2.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -#### 20.2.2.2.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to cancel AI/ML model training. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 10.3.5.3.2. -- b) The HTTP request is a DELETE operation. -- c) The trainingJobId in the URI match the training job being cancelled. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 10.3.4.2.1. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 10.3.4.2.1. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 10.3.5.3.2. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 10.3.4.2.1. - -#### 20.2.2.2.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 20.2.2.3 Query AI/ML model training job status (positive case) - -#### 20.2.2.3.1 Test description and applicability - -The purpose of this test case is to test the Query AI/ML model training job status as specified in R1AP [4], clause 10.3.4.3. The expected outcome is successful validation of the request from the DUT. - -#### 20.2.2.3.2 Test entrance criteria - -- 1) The test simulator has functionality to initiate the Query AI/ML model training job status procedure as defined in R1GAP [1], clause 5.6.8. -- 2) A training job exists in the DUT and the trainingJobId is known to the test simulator. - -#### 20.2.2.3.3 Test methodology - -##### 20.2.2.3.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -##### 20.2.2.3.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request to query a training job status. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 10.3.5.4.2. -- b) The HTTP request is a GET operation. -- c) The trainingJobId in the URI match the training job status being queried. -- d) The HTTP request message content includes the information as specified in R1AP [4], clause 10.3.4.3.1. - -Step 4. The DUT sends the appropriate HTTP response as specified in R1AP [4], clause 10.3.4.3.1. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 10.3.5.4.2. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 10.3.4.3.1. - -#### 20.2.2.3.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 20.2.2.4 Notify AI/ML model training job status change (positive case) - -#### 20.2.2.4.1 Test description and applicability - -The purpose of this test case is to test the Notify AI/ML model training job status change APIs as specified in R1AP [4], clause 10.3.4.4. The expected outcome is successful validation of the response from the DUT. - -#### 20.2.2.4.2 Test entrance criteria - -- 1) The DUT supports the functionality to initiate the Notify AI/ML model training job status change procedure as defined in R1GAP [1], clause 5.6.8. -- 2) A training job exists in the DUT. - -#### 20.2.2.4.3 Test methodology - -##### 20.2.2.4.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -##### 20.2.2.4.3.2 Procedure - -- Step 1. The DUT as an API producer initiates the sending of a HTTP POST request. -- Step 2. At the test simulator the contents of the received HTTP request is recorded. -- Step 3. The test simulator does the following validation: - - a) The HTTP request is a POST operation. - - b) The callback URI matches the URI provided in the creation of the training job. -- Step 4. The test simulator sends the HTTP response as specified in R1AP [4], clause 10.3.4.4.1. - -#### 20.2.2.4.4 Expected result - -The test is considered passed if Step 3 validation has passed. - ---- - -## 21 AI/ML workflow AI/ML model deployment API test cases - -### 21.1 Conformance test cases for rApp - -#### 21.1.1 General - -##### 21.1.1.1 Device under test requirements - -The rApp that acts as DUT in these test scenarios, the requirements on the DUT for these tests are that it can handle the AI/ML model deployment request services, and the purpose of the test scenarios is to validate that it conforms to the API Consumer functionality as specified in R1AP [4], clause 10.4.4. - -##### 21.1.1.2 Test simulator capabilities - -The test simulator has the capabilities as required for a SMO/Non-RT RIC framework. In addition, it has the following capabilities: - -- Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to the API Consumer functionality as specified in R1AP [4], clause 10.4.4. - -#### 21.1.2 AI/ML model deployment API as API Consumer test scenario - -##### 21.1.2.1 Request AI/ML model deployment (positive case) - -###### 21.1.2.1.1 Test description and applicability - -The purpose of this test case is to test the request AI/ML model deployment as specified in R1AP [4], clause 10.4.4.1. The expected outcome is successful validation of the request from the DUT. - -###### 21.1.2.1.2 Test entrance criteria - -The DUT has functionality to initiate the Request AI/ML model deployment procedure as defined in R1GAP [1], clause 5.6.7. - -###### 21.1.2.1.3 Test methodology - -###### 21.1.2.1.3.1 Initial conditions - -The test simulator as API Producer is ready and available to receive HTTP requests from the DUT. - -###### 21.1.2.1.3.2 Procedure - -- Step 1. The DUT as an API Consumer initiates a HTTP request for AI/ML model deployment. -- Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The URI confirms to the format specified in R1AP [4], clause 10.4.5.2. -- b) The HTTP request is a POST operation. -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 10.4.4.1.1. - -Step 4. The test simulator sent the appropriate HTTP response as specified in R1AP [4], clause 10.4.4.1.1. - -#### 21.1.2.1.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## 21.2 Conformance test cases for SMO/Non-RT RIC framework - -### 21.2.1 General - -#### 21.2.1.1 Device under test requirements - -The SMO/Non-RT RIC framework that acts as Device Under Test (DUT) in these test scenarios, the requirements on the DUT for these tests are that it can handle the AI/ML model deployment request services, and the purpose of the test scenarios is to validate that it conforms to the AI/ML model deployment API specified in R1AP [4], clause 10.4.4. - -#### 21.2.1.2 Test simulator capabilities - -The test simulator has the capabilities as specified in clause 4.3.2. In addition, it has the following capabilities: - -- 1) Recording of received HTTP requests and responses and analyzing them regarding conformance to the R1 service definitions. -- 2) Controlled initiation of procedures with configurable URIs and payload formulated and modified. - -Validating messages and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUT's conformance to API Producer functionality as specified in R1AP [4], clause 10.4.4. - -### 21.2.2 AI/ML model deployment API as API Producer test scenario - -#### 21.2.2.1 Request AI/ML model deployment (positive case) - -##### 21.2.2.1.1 Test description and applicability - -The purpose of this test case is to test the Request AI/ML model deployment APIs as specified in R1AP [4], clause 10.4.4.1. The expected outcome is successful validation of the response from the DUT. - -##### 21.2.2.1.2 Test entrance criteria - -The test simulator supports the functionality to initiate the Request AI/ML model deployment procedure as defined in R1GAP [1], clause 5.6.7. - -##### 21.2.2.1.3 Test methodology - -###### 21.2.2.1.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP responses from the DUT. - -#### 21.2.2.1.3.2 Procedure - -Step 1. The test simulator as an API Consumer initiates a HTTP request for AI/ML model deployment. - -Step 2. The DUT receives the HTTP request. - -Step 3. The DUT does the following validation: - -- a) The HTTP request is a POST request. -- b) The URI conforms to the format as specified in R1AP [4], clause 10.4.5.2 -- c) The HTTP request message content includes the information as specified in R1AP [4], clause 10.4.4.1.1. - -Step 4. The DUT initiates a HTTP Response. - -Step 5. At the test simulator the contents of the received HTTP response is recorded. - -Step 6. The test simulator does the following validation: - -- a) The URI conforms to the format specified in R1AP [4], clause 10.4.5.2. -- b) The HTTP response message content includes the information as specified in R1AP [4], clause 10.4.4.1.1. - -#### 21.2.2.1.4 Expected result - -The test is considered passed if Step 6 validation has passed. - -### 21.2.2.2 Notify AI/ML model deployment status change (positive case) - -#### 21.2.2.2.1 Test description and applicability - -The purpose of this test case is to test the Notify AI/ML model deployment job status change APIs as specified in R1AP [4], clause 10.4.4.2. The expected outcome is successful validation of the response from the DUT. - -#### 21.2.2.2.2 Test entrance criteria - -- 1) The DUT supports the functionality to initiate the Request AI/ML model deployment procedure as defined in R1GAP [1], clause 5.6.7 -- 2) A model exists in the DUT and the notificationDestination is known to the test simulator. - -#### 21.2.2.2.3 Test methodology - -##### 21.2.2.2.3.1 Initial conditions - -The test simulator as API Consumer is ready and available to receive HTTP requests from the DUT. - -##### 21.2.2.2.3.2 Procedure - -Step 1. The DUT as an API producer initiates the sending of a HTTP POST request. - -Step 2. At the test simulator the contents of the received HTTP request is recorded. - -Step 3. The test simulator does the following validation: - -- a) The HTTP request is a POST operation. -- b) The callback URI matches the URI provided in the model deployment request. - -Step 4. The test simulator sends the HTTP response as specified in R1AP [4], clause 10.4.4.2.1. - -#### 21.2.2.2.4 Expected result - -The test is considered passed if Step 3 validation has passed. - -## Annex (informative): Change history - -| Date | Revision | Description | -|------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2025.11.24 | 05.00 | Included The test cases related to Configuration management service, Fault management Service, DME -Query Data subscription, HTTP PUSH , HTTP Pull, Config schema , AI/ML model training, AI/ML model deployment, AI/ML model discovery. | -| 2025.07.10 | 04.00 | Published with conformance test of rApp and Non-RT RIC as DUT for Data offer testcases, Boot strap test case, AI/ML model discovery testcase , AI/ML model registration testcase and Configuration management testcase for rApp as DUT. | -| 2025.03.13 | 03.00 | Published with Conformance test of rApp and Non-RT RIC as DUT for DME, A1 policy management and SME | -| 2024.11.21 | 02.00 | Published with Conformance test of Non-RT RIC as DUT for Service registration test case | -| 2024.07.11 | 01.00 | Published with conformance testing of rApps and SMO/Non-RT RIC Framework and with one Service registration test case | \ No newline at end of file diff --git a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/0827b9260fe5458dbe416ebfc78c469e_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/08783c875dd39684fee7f2a40b584c64_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/0a65720e640be13541e947c06c7a8c7f_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/1099a4137017f2d9721d546bbb1e9362_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/13249a22bfff48bf6d20110d7228bfcd_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/14af8d47efd24c21fddf71b2415b6397_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/1baaba7a6e54e77197475726c871067d_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/22af211207188ebc64d7b60ca052b367_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/22f30783614672d201275c116a5d8516_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/253600420ae7bd7d0119563b895cbf8a_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/29f3760c0230631eb03f67030ef65ed0_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index f3a71b98fcfc274b0603208cc5e23601d7fc924a..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:84a0e505aa8e8fcec39c03736b466858a7c1ef91abe309cdd2974ee18257e23b -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/318db222fae24a59c370fa6471d541b8_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/318db222fae24a59c370fa6471d541b8_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/318db222fae24a59c370fa6471d541b8_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/36e2350ea1a3ef6ca68c655394300a91_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/36fb8f844f936e7a1de4838da774f2f9_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/38222c3ae003223a67635bfcc6950fbb_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/38866d3f212726e1c8e92001ca0dd6f8_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/3a4f4369128594c5db0aa6b853c0666e_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/3f727e6c0d6658bc53ea10905c4561dd_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/446c0bd806260f25430cadb01a6786c7_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/481b1f80fc31ebebb30d1f57d31e3af3_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4a04896dfb569893fba50729314024f5_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4b81ac66c571b3118659e4d9f47abb22_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4db00373eb0bec04341ee887235bbfea_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/4f8349df2ca48959fefb7c42b2bc375e_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/5009e30a55479d3941af523871208f9d_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/5009e30a55479d3941af523871208f9d_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/52a225f71b166b0c65c2f29f32a79f7f_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/562f471e8153729557e6a4ee6343c32c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/562f471e8153729557e6a4ee6343c32c_img.jpg deleted file mode 100644 index 5121fc1b38172a2eacc1d9c67cb4fc1970382c09..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/562f471e8153729557e6a4ee6343c32c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:deaa3f99054a8f7508d5d5f0d29fbab74fd81523caf4d22f36c41fc45a5d6323 -size 57086 diff --git a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/56ac11fb9683d7b846fb65c845d80f22_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/59368942873b0c35eef79a7a985025dc_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/59fcc0e3699f239444841881a2e75da0_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/5ae3023386ee15fae372871afce28865_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/60d6a326e6061d71ea69c9375ec96631_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/60e345365fd1e52e01c91e3fd3cc6515_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6588b1c7f14069d96744b473ad663248_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/681c354e00e1c0fe098ba665ff155cb8_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6a5342571eca4b46338fdfb3c42a8055_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6a9c5a85a12499d60c5a3a75c643b852_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6b0834ca8cdd18832ed461378d51dcb7_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6c6024603c6fd57b23210b79f573b3bd_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6c8a96787f532bd1fa4719e738cf556f_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/79898de98da3367d0ea9beef38f5c01c_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/7a3d4c97055e3021cefb0c5850050bff_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index f3a71b98fcfc274b0603208cc5e23601d7fc924a..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:84a0e505aa8e8fcec39c03736b466858a7c1ef91abe309cdd2974ee18257e23b -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/7f4320cee12fc1dbb865cc6b67462a91_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/81b34087cd6755a80f84a70cf28fba82_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/829cdaf00f7219d70e571064b2b13291_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8447c5519e85d7a9e029fbf321da4c4f_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/854df8ad60507803253274673f9062cf_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/89100a6476d1d96f22c192db16502fec_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8b4befaffc5166da571069410e207aea_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8d138b6bf0be359dc7f079db4899bc41_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/9156549264d36ead617a1dec7987f970_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/9159d999b6514420a64eae80e52f1fd5_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/970a901d8e537da4b6ff719d8931912f_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/990567efebf979be51f56d1150012c9d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/990567efebf979be51f56d1150012c9d_img.jpg deleted file mode 100644 index e3e39ad99193aed7cf176df61d37ed9f38e7cca0..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/990567efebf979be51f56d1150012c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8707160b000d562bcbf520da90a4c6c1e08e3483a48a3c24de990ea78a9f19da -size 50790 diff --git a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/990afa9d07fb81cf8760867cb4247a79_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/9a6ff2584005112f32fbd551cb6f0591_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/9b59a11096b85b2bc74c6f653a354e28_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a28ab03366399b5e0a61445bc57e3724_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a76a30cf23764f0b907220e7c3c70ce1_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a7fcb275d0eed586509a47f4f86a9725_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a82aef1d2f3f1a527328950e9db947ee_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/a9bb99d15f54792e1c9a14b1e465369a_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/c389468860cd886ab9c732473e959f0f_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/c4315e81a5a818379fcf31519a9c2cbe_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/c5538ac451af9d74926b82278f11fb87_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/cb5f64aa26cee1c05257b7c6bbba7408_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/cb8f0521a69f168a06222045bea81a86_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d0516b99882398c64c90f71c12e808e2_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg deleted file mode 100644 index 4b94da934e2c8c85c0123640346015b174f8dc14..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:53785b160680d7d75d469ea49f0daf5b5a3522fbee704e81dcd409934e1d112e -size 4601 diff --git a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d2c29dfabebacb6f853683a6c3759320_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d597715604d00e1ab3b00cc3f16e59de_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d879e5f2c388bb87ee9614f63364dcf0_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d90d939bcbf43d474efaeeaa335a635c_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/d90f17b29a73eddf151f51effa8912e0_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index f3a71b98fcfc274b0603208cc5e23601d7fc924a..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:84a0e505aa8e8fcec39c03736b466858a7c1ef91abe309cdd2974ee18257e23b -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index f3a71b98fcfc274b0603208cc5e23601d7fc924a..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:84a0e505aa8e8fcec39c03736b466858a7c1ef91abe309cdd2974ee18257e23b -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/dbd230eafb5429741c22c2f7293118af_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e11e3fe4228e889a962514269f5a000b_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e32e1bcf367a284cc7a4186056810d22_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e3b551138548092502c92a99ebfdb7bc_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 364df5703e2728ce466bd0737dc228958c42f689..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1d4f853812c3a1f9820c9d5711d2b089e78052b458d9c8f7021b4cf74759092f -size 4611 diff --git a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e87df69ebd4cd2dbbf6749079e6c057a_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/e882a6bdfd0e868314f3a26f536145a3_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/f250ba4162fe40d8ddfd05b74fa48895_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/f3d768b0299c4763bc703b606391c48b_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/f74adaa1840504407cd4272995426f82_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/f7dbd497160f02888f34fdf243648aa2_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.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/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1TS-R005-v05.00/images/ff748955b94dcb8337283fbe12baa475_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/doc.md b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/doc.md deleted file mode 100644 index eaaa69d987e6cf804e969b96d1a1737f05ec2964..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/doc.md +++ /dev/null @@ -1,7615 +0,0 @@ - - -# --- **R1 interface: Use Cases and Requirements** - -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..... | 7 | -| Modal verbs terminology..... | 7 | -| 1 Scope..... | 8 | -| 2 References..... | 8 | -| 2.1 Normative references..... | 8 | -| 2.2 Informative references..... | 8 | -| 3 Definition of terms, symbols and abbreviations..... | 8 | -| 3.1 Terms..... | 8 | -| 3.2 Symbols..... | 9 | -| 3.3 Abbreviations..... | 9 | -| 3.4 Conventions..... | 9 | -| 3.4.1 General..... | 9 | -| 3.4.2 Requirements..... | 9 | -| 4 General..... | 9 | -| 5 Requirements..... | 10 | -| 5.1 General..... | 10 | -| 5.2 Security..... | 10 | -| 5.3 SME services functional requirements..... | 10 | -| 5.4 DME services functional requirements..... | 10 | -| 5.5 RAN OAM-related services functional requirements..... | 11 | -| 5.6 AI/ML workflow services functional requirements..... | 13 | -| 5.7 AI-related services functional requirements..... | 13 | -| 6 Use cases for Service Management and Exposure..... | 14 | -| 6.1 SME use case 1: Bootstrap..... | 14 | -| 6.1.1 Overview..... | 14 | -| 6.1.2 Background and goal of the use case..... | 14 | -| 6.1.3 Entities/resources involved in the use case..... | 14 | -| 6.1.4 Solutions..... | 15 | -| 6.1.5 Required data..... | 16 | -| 6.2 SME Use case 2: Manage Service Registration..... | 16 | -| 6.2.1 Overview..... | 16 | -| 6.2.2 Background and goal of the use case..... | 16 | -| 6.2.3 Entities/resources involved in the use case..... | 16 | -| 6.2.4 Solutions..... | 17 | -| 6.2.5 Required data..... | 20 | -| 6.3 SME use case 3: Discovery of services..... | 21 | -| 6.3.1 Overview..... | 21 | -| 6.3.2 Background and goal of the use case..... | 21 | -| 6.3.3 Entities/resources involved in the use case..... | 21 | -| 6.3.4 Solutions..... | 21 | -| 6.3.5 Required data..... | 22 | -| 6.4 SME use case 4: Subscribe service availability..... | 22 | -| 6.4.1 Overview..... | 22 | -| 6.4.2 Background and goal of the use case..... | 23 | -| 6.4.3 Entities/resources involved in the use case..... | 23 | -| 6.4.4 Solutions..... | 23 | -| 6.4.5 Required data..... | 28 | -| 6.5 SME use case 5: Query registered services..... | 28 | -| 6.5.1 Overview..... | 28 | -| 6.5.2 Background and goal of the use case..... | 28 | -| 6.5.3 Entities/resources involved in the use case..... | 28 | -| 6.5.4 Solutions..... | 29 | -| 6.5.5 Required data..... | 30 | -| 7 Use cases for Data Management and Exposure Services..... | 30 | - -- 7.1 DME use case 1: Data registration, update, and deregistration. ....30 - - 7.1.1 Overview .....30 - - 7.1.2 Background and goal of the use case.....30 - - 7.1.3 Entities/resources involved in the use case. ....30 - - 7.1.4 Solutions .....31 - - 7.1.5 Required data. ....37 -- 7.2 DME use case 2: Discovery of DME types. ....37 - - 7.2.1 Overview .....37 - - 7.2.2 Background and goal of the use case. ....37 - - 7.2.3 Entities/resources involved in the use case. ....37 - - 7.2.4 Solutions .....38 - - 7.2.5 Required data. ....45 -- 7.3 DME use case 3: Data offer.....45 - - 7.3.1 Overview .....45 - - 7.3.2 Background and goal of the use case.....46 - - 7.3.3 Entities/resources involved in the use case. ....46 - - 7.3.4 Solutions .....47 - - 7.3.5 Required data. ....53 -- 7.4 DME use case 4: Data request-Data Consumer rApp requests data for consumption from the DME functions.54 - - 7.4.1 Overview .....54 - - 7.4.2 Background and goal of the use case.....54 - - 7.4.3 Entities/resources involved in the use case. ....54 - - 7.4.4 Solutions .....55 - - 7.4.5 Required data. ....56 -- 7.5 DME use case 5: Data request – DME functions request data for collection from a Data Producer rApp. ....56 - - 7.5.1 Overview .....56 - - 7.5.2 Background and goal of the use case.....56 - - 7.5.3 Entities/resources involved in the use case. ....57 - - 7.5.4 Solutions .....57 - - 7.5.5 Required data. ....58 -- 7.6 DME use case 6: The DME functions subscribe data for collection from a Data Producer rApp.....59 - - 7.6.1 Overview .....59 - - 7.6.2 Background and goal of the use case. ....59 - - 7.6.3 Entities/resources involved in the use case. ....59 - - 7.6.4 Solutions .....59 - - 7.6.5 Required data. ....67 -- 7.7 DME use case 7: A Data Consumer rApp subscribes data for consumption using the Data request and subscription service. ....68 - - 7.7.1 Overview .....68 - - 7.7.2 Background and goal of the use case.....68 - - 7.7.3 Entities/resources involved in the use case. ....68 - - 7.7.4 Solutions .....69 - - 7.7.5 Required data. ....76 -- 7.8 DME use case 8: Data Producer rApp query the data subscription information for its registered DME types.76 - - 7.8.1 Overview .....76 - - 7.8.2 Background and goal of the use case.....76 - - 7.8.3 Entities/resources involved in the use case. ....77 - - 7.8.4 Solutions .....77 - - 7.8.5 Required data. ....78 -- 8 Use cases for RAN OAM-Related Services.....78 - - 8.1 RAN OAM-Related use case 1: Alarm query. ....78 - - 8.1.1 Overview .....78 - - 8.1.2 Background and goal of the use case.....79 - - 8.1.3 Entities/resources involved in the use case. ....79 - - 8.1.4 Solutions .....79 - - 8.1.5 Required data. ....80 - - 8.2 RAN OAM-Related use case 2: Alarm acknowledgement / unacknowledgement.....80 - - 8.2.1 Overview .....80 - - 8.2.2 Background and goal of the use case.....80 - - 8.2.3 Entities/resources involved in the use case. ....80 - - 8.2.4 Solutions .....81 - - 8.2.5 Required data. ....82 - -- 8.3 RAN OAM-Related use case 3: Performance information query. ....82 - - 8.3.1 Overview .....82 - - 8.3.2 Background and goal of the use case.....82 - - 8.3.3 Entities/resources involved in the use case. ....82 - - 8.3.4 Solutions .....83 - - 8.3.5 Required data. ....84 -- 8.4 RAN OAM-Related use case 4: Retrieve configuration schemas. ....84 - - 8.4.1 Overview .....84 - - 8.4.2 Background and goal of the use case.....84 - - 8.4.3 Entities/resources involved in the use case. ....84 - - 8.4.4 Solutions .....85 - - 8.4.5 Required data. ....86 -- 8.5 RAN OAM-Related use case 5: Read configuration data. ....86 - - 8.5.1 Overview .....86 - - 8.5.2 Background and goal of the use case.....86 - - 8.5.3 Entities/resources involved in the use case. ....86 - - 8.5.4 Solutions .....87 - - 8.5.5 Required data. ....88 -- 8.6 RAN OAM-Related use case 6: Writing configuration changes. ....88 - - 8.6.1 Overview .....88 - - 8.6.2 Background and goal of the use case.....88 - - 8.6.3 Entities/resources involved in the use case. ....88 - - 8.6.4 Solutions .....89 - - 8.6.5 Required data. ....90 -- 9 Use cases for O2-Related Services.....90 -- 10 Use cases for A1-Related Services.....91 - - 10.1 Void.....91 - - 10.2 Void.....91 - - 10.3 A1-Related use case 1: Query A1 policy type identifiers.....91 - - 10.3.1 Overview .....91 - - 10.3.2 Background and goal of the use case.....91 - - 10.3.3 Entities/resources involved in the use case. ....91 - - 10.3.4 Solutions .....92 - - 10.3.5 Required data .....93 - - 10.4 A1-Related use case 2: Query an A1 policy type.....93 - - 10.4.1 Overview .....93 - - 10.4.2 Background and goal of the use case.....93 - - 10.4.3 Entities/resources involved in the use case. ....93 - - 10.4.4 Solutions .....94 - - 10.4.5 Required data .....95 - - 10.5 A1-Related use case 3: Query A1 policy identifiers .....95 - - 10.5.1 Overview .....95 - - 10.5.2 Background and goal of the use case.....95 - - 10.5.3 Entities/resources involved in the use case. ....95 - - 10.5.4 Solutions .....96 - - 10.5.5 Required data .....97 - - 10.6 A1-related use case 4: Create, Query, Update and Delete an A1 policy .....97 - - 10.6.1 Overview .....97 - - 10.6.2 Background and goal of the use case.....97 - - 10.6.3 Entities/resources involved in the use case. ....97 - - 10.6.4 Solutions .....97 - - 10.6.5 Required data .....104 - - 10.7 A1-Related use case 5: Query the status of an A1 policy.....105 - - 10.7.1 Overview .....105 - - 10.7.2 Background and goal of the use case.....105 - - 10.7.3 Entities/resources involved in the use case. ....105 - - 10.7.4 Solutions .....105 - - 10.7.5 Required data .....106 - - 10.8 A1-Related use case 6: Subscribe to status of an A1 policy.....106 - - 10.8.1 Overview .....106 - - 10.8.2 Background and goal of the use case.....106 - -| | | | -|--------|-------------------------------------------------------------------------------------------------------------------------------------------------|-----| -| 10.8.3 | Entities/resources involved in the use case ..... | 106 | -| 10.8.4 | Solutions ..... | 107 | -| 10.8.5 | Required data ..... | 110 | -| 11 | Use cases for AI/ML Workflow Services ..... | 110 | -| 11.1 | AI/ML workflow-related use case 1: AI/ML model registration and deregistration ..... | 110 | -| 11.1.1 | Overview ..... | 110 | -| 11.1.2 | Background and goal of the use case ..... | 110 | -| 11.1.3 | Entities/resources involved in the use case ..... | 110 | -| 11.1.4 | Solutions ..... | 111 | -| 11.1.5 | Required data ..... | 117 | -| 11.2 | AI/ML workflow-related use case 2: Discovery of AI/ML Model ..... | 117 | -| 11.2.1 | Overview ..... | 117 | -| 11.2.2 | Background and goal of the use case ..... | 117 | -| 11.2.3 | Entities/resources involved in the use case ..... | 117 | -| 11.2.4 | Solutions ..... | 118 | -| 11.2.5 | Required data ..... | 119 | -| 11.3 | AI/ML workflow-related use case 3: AI/ML training – AI/ML workflow functions producing AI/ML training services ..... | 119 | -| 11.3.1 | Overview ..... | 119 | -| 11.3.2 | Background and goal of the use case ..... | 119 | -| 11.3.3 | Entities/resources involved in the use case ..... | 119 | -| 11.3.4 | Solutions ..... | 120 | -| 11.3.5 | Required data ..... | 126 | -| 11.4 | AI/ML workflow-related use case 4: AI/ML training – rApp producing AI/ML training services ..... | 126 | -| 11.4.1 | Overview ..... | 126 | -| 11.4.2 | Background and goal of the use case ..... | 126 | -| 11.4.3 | Entities/resources involved in the use case ..... | 126 | -| 11.4.4 | Solutions ..... | 127 | -| 11.4.5 | Required data ..... | 133 | -| 11.5 | AI/ML workflow-related use case 5: AI/ML model Retrieve ..... | 133 | -| 11.5.1 | Overview ..... | 133 | -| 11.5.2 | Background and goal of the use case ..... | 133 | -| 11.5.3 | Entities/resources involved in the use case ..... | 133 | -| 11.5.4 | Solutions ..... | 134 | -| 11.5.5 | Required data ..... | 135 | -| 11.6 | AI/ML workflow-related use case 6: AI/ML model deployment ..... | 135 | -| 11.6.1 | Overview ..... | 135 | -| 11.6.2 | Background and goal of the use case ..... | 135 | -| 11.6.3 | Entities/resources involved in the use case ..... | 135 | -| 11.6.4 | Solutions ..... | 136 | -| 11.6.5 | Required data ..... | 137 | -| 11.7 | AI/ML workflow-related use case 7: AI/ML model performance monitoring – AI/ML workflow functions consuming performance monitoring service ..... | 137 | -| 11.7.1 | Overview ..... | 137 | -| 11.7.2 | Background and goal of the use case ..... | 137 | -| 11.7.3 | Entities/resources involved in the use case ..... | 137 | -| 11.7.4 | Solutions ..... | 138 | -| 11.7.5 | Required data ..... | 141 | -| 11.8 | AI/ML workflow-related use case 8: AI/ML model performance monitoring – rApp consuming performance monitoring service ..... | 142 | -| 11.8.1 | Overview ..... | 142 | -| 11.8.2 | Background and goal of the use case ..... | 142 | -| 11.8.3 | Entities/resources involved in the use case ..... | 142 | -| 11.8.4 | Solutions ..... | 143 | -| 11.8.5 | Required data ..... | 146 | -| 11.9 | AI/ML workflow-related use case 9: AI/ML model training capability registration and deregistration ..... | 146 | -| 11.9.1 | Overview ..... | 146 | -| 11.9.2 | Background and goal of the use case ..... | 147 | -| 11.9.3 | Entities/resources involved in the use case ..... | 147 | -| 11.9.4 | Solutions ..... | 147 | -| 11.9.5 | Required data ..... | 153 | - -- 11.10 AI/ML workflow-related use case 10: AI/ML model inference – AI/ML workflow functions producing AI/ML inference..... 153 - - 11.10.1 Overview ..... 153 - - 11.10.2 Background and goal of the use case ..... 153 - - 11.10.3 Entities/resources involved in the use case ..... 153 - - 11.10.4 Solutions ..... 154 - - 11.10.5 Required data ..... 156 -- 11.11 AI/ML workflow-related use case 11: AI/ML model change subscription. .... 157 - - 11.11.1 Overview ..... 157 - - 11.11.2 Background and goal of the use case ..... 157 - - 11.11.3 Entities/resources involved in the use case ..... 157 - - 11.11.4 Solutions ..... 158 - - 11.11.5 Required data ..... 162 -- 11.12 AI/ML workflow-related use case 12: Query of AI/ML Model inference capabilities - AI/ML workflow functions producing AI/ML inference ..... 162 - - 11.12.1 Overview ..... 162 - - 11.12.2 Background and goal of the use case ..... 162 - - 11.12.3 Entities/resources involved in the use case ..... 162 - - 11.12.4 Solutions ..... 163 - - 11.12.5 Required data ..... 164 -- 11.13 AI/ML Workflow-related use case 13: Query of AI/ML Model training capability ..... 164 - - 11.13.1 Overview ..... 164 - - 11.13.2 Background and goal of the use case ..... 164 - - 11.13.3 Entities/resources involved in the use case ..... 164 - - 11.13.4 Solutions ..... 165 - - 11.13.5 Required data ..... 166 -- 12 Use cases for rApp Management Services ..... 166 - - 12.1 rApp Management use case 1: rApp registration ..... 166 - - 12.1.1 Overview ..... 166 - - 12.1.2 Background and goal of the use case ..... 166 - - 12.1.3 Entities/resources involved in the use case. .... 166 - - 12.1.4 Solutions ..... 167 - - 12.1.5 Required data. .... 168 -- Annex (informative): Change history ..... 169 - -# Foreword - -This Technical Specification (TS) has been produced by WG2 of the O-RAN ALLIANCE. It is part of a TS-family covering the WG2: R1 Interface Specifications. - -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 Use cases and Requirements for R1 interface. - -# 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.WG2.TS.R1GAP: "R1 interface: General Aspects and Principles". ("R1GAP") -- [2] O-RAN.WG2.TS.Use-Case-Requirements: " Non-RT RIC & A1/R1 Interface: Use Cases and Requirements". ("UCR") -- [3] O-RAN.WG2.TS.A1TD: "A1 interface: Type Definitions". ("A1TD") -- [4] O-RAN.WG11.TS.SRCS.0: "Security Requirements and Controls Specification". ("SRS") -- [5] O-RAN.WG2.TS.A1AP: "A1 interface: Application Protocol". ("A1AP") -- [6] O-RAN.WG2.TS.A1UCR: "A1 interface: Use Cases and Requirements". ("A1UCR") -- [7] Recommendation ITU-T M.3020: "Management interface specification methodology". ("ITU-T M.3020"). - -## 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. - -Not applicable - -# 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the following terms apply: - -**Non-RT RIC:** O-RAN non-real-time RAN Intelligent Controller: a logical function in the SMO framework 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. The Non-RT RIC is comprised of the Non-RT RIC framework and Non-RT RIC applications (rApps). - -**Non-RT RIC framework:** Functionality internal to the SMO framework that logically terminates the A1 interface and provides the R1 services to rApps through the R1 interface. - -**rApp:** Non-RT RIC application: an application designed to consume and/or produce R1 Services. - -NOTE: rApps can leverage the functionality provided by the SMO/Non-RT RIC framework to deliver value added services related to intelligent RAN optimization and operation. - -**DME type:** data type managed and exposed by the DME services and identified by a data type identifier. - -## 3.2 Symbols - -Void - -## 3.3 Abbreviations - -For the purposes of the present document, the following abbreviations apply: - -| | | -|------------|------------------------------------------| -| API | Application programming Interface | -| AuthN | Authentication | -| AuthZ | Authorization | -| DME | Data Management and Exposure | -| FWK | Framework | -| FM | Fault management | -| ID | Identifier | -| Non-RT RIC | Non-real time RAN Intelligent Controller | -| PM | Performance management | -| SME | Service Management and Exposure | -| SMO | Service Management and Orchestration | - -## 3.4 Conventions - -### 3.4.1 General - -For the purposes of the present document, the conventions in the following clauses apply. - -### 3.4.2 Requirements - -The requirements and solutions for use cases are based on the methodology specified in ITU-T M.3020 [7], clause A.1.2. - -# --- 4 General - -The R1 interface is defined between the rApps and the Non-RT RIC framework, as defined in R1GAP [1]. - -In the use case sequence flows, solid lines are used for the message interactions which are defined in O-RAN specifications. Dashed lines are used to represent the messages interactions that are not specified in O-RAN specifications or can be implementation specific interactions. - -# 5 Requirements - -## 5.1 General - -The general R1 interface requirements are specified in UCR [2] - -## 5.2 Security - -The security requirements applicable to the R1 interface are specified in SRS [4], clause 5.2.6. - -## 5.3 SME services functional requirements. - -This clause specifies the SME services functional requirements. - -The functional requirements are specified in table 5.3-1. - -**Table 5.3-1: SME services functional requirements** - -| REQ | Description | Note | -|-------------------------------------|-------------------------------------------------------------------------------------------------|------| -| REQ-R1-SME-rAppreg-FUN1 | The SME services shall support registration of an rApp. | | -| REQ-R1-SME-rAppreg-FUN2 | The SME services shall support authentication of an rApp. | | -| REQ-R1-SME-Servicemag-FUN1 | The SME services shall support registration of a service. | | -| REQ-R1-SME-Servicemag-FUN2 | The SME services shall support update of a service registration. | | -| REQ-R1-SME-Servicemag-FUN3 | The SME services shall support deregistration of a registered service. | | -| REQ-R1-SME-Service discovery - FUN1 | The SME services shall support the discovery of services. | | -| REQ-R1-SME-Servicesub-FUN1 | The SME services shall support subscription to notifications of service availability changes. | | -| REQ-R1-SME-Servicesub-FUN2 | The SME services shall support sending notifications for the service availability changes. | | -| REQ-R1-SME-Servicesub-FUN3 | The SME services shall support unsubscription to notifications of service availability changes. | | - -## 5.4 DME services functional requirements - -This clause specifies the DME services functional requirements. - -The functional requirements are specified in table 5.4-1. - -**Table 5.4-1: DME services functional requirements** - -| REQ | Description | Note | -|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------|------| -| REQ-R1-DME-Regdatatype-FUN1 | The DME services shall support registration, query, update and deregistration of a DME type. | | -| REQ-R1-DME-Regdatatype-FUN2 | The DME services shall support the query of data subscription information for its registered DME type | | -| REQ-R1-DME-Discoverydatatype-FUN1 | The DME services shall support querying available DME types. | | -| REQ-R1-DME-Subscribedatatypechanges-FUN1 | The DME services shall support subscription to notifications regarding changes in the availability of DME types. | | -| REQ-R1-DME-Notifydatatypechanges-FUN1 | The DME services shall support sending notifications about changes in the availability of DME types. | | -| REQ-R1-DME-Unsubscribedatatypechanges-FUN1 | The DME services shall support to unsubscribe from notifications regarding changes in the availability of DME types. | | -| REQ-R1-DME-Dataoffer -FUN1 | The DME services shall support the creation of data offers. | | -| REQ-R1-DME-Dataoffer -FUN2 | The DME services shall support the termination of data offers. | | -| REQ-R1-DME-Data subscription-FUN1 | The DME services shall support the creation of data subscriptions. | | -| REQ-R1-DME-Data subscription-FUN2 | The DME services shall support the termination of data subscriptions. | | -| REQ-R1-DME-Data subscription-FUN3 | The DME services shall support the update of data subscriptions. | | -| REQ-R1-DME-Data subscription-FUN4 | The DME services shall support the query of data subscriptions. | | -| REQ-R1-DME-Data request-FUN1 | The DME services shall support the creation of data requests. | | -| REQ-R1-DME-Data request-FUN2 | The DME services shall support the cancellation of data requests. | | -| REQ-R1-DME-Data delivery-FUN1 | The DME services shall support the delivery of subscribed or requested data. | | -| REQ-R1-DME-Data subscription-FUN1 | The DME services shall support the query the status of data subscriptions. | | - -## 5.5 RAN OAM-related services functional requirements. - -This clause specifies the FM, CM and PM services functional requirements. - -The functional requirements are specified in table 5.5-1. - -**Table 5.5-1: FM, CM and PM services functional requirements** - -| REQ | Description | Note | -|---------------------------|------------------------------------------------------------------------------------------------------------------|------| -| REQ-R1-OAM-FMservice-FUN1 | The FM service shall support querying alarm information related to the O-RAN managed entities. | | -| REQ-R1-OAM-FMservice-FUN2 | The FM service shall support changing the acknowledgement state of alarms related to the O-RAN managed entities. | | -| REQ-R1-OAM-PMservice-FUN1 | The PM service shall support querying performance information related to the O-RAN managed entities. | | -| REQ-R1-OAM-CMservice-FUN1 | The CM service should support retrieving configuration schema related to the O-RAN managed entities. | | -| REQ-R1-OAM-CMservice-FUN2 | The CM service shall support retrieving configuration data related to O-RAN managed entities. | | -| REQ-R1-OAM-CMservice-FUN3 | The CM service shall support to write configuration changes to O-RAN managed entities. | | - -NOTE: The querying of performance information, and how this relates to the Data management and exposure services, is not defined in the present document. - -## 5.6 AI/ML workflow services functional requirements - -This clause specifies the AI/ML workflow services functional requirements. - -The functional requirements are specified in table 5.6-1. - -**Table 5.6-1: AI/ML workflow services functional requirements** - -| REQ | Description | Note | -|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|------| -| REQ-R1-AIML-Deploymodel-FUN1 | The AI/ML workflow services shall support the request of deployment of an AI/ML model. | | -| REQ-R1-AIML-Retrievemodel-FUN1 | The AI/ML workflow services shall support retrieving the location details of a registered AI/ML model. | | -| REQ-R1-AI/ML-training-FUN1 | The AI/ML workflow services shall support training of AI/ML models. | | -| REQ-R1-AI/ML-training-FUN2 | The AI/ML workflow services shall support query of AI/ML training job status. | | -| REQ-R1-AI/ML-training-FUN3 | The AI/ML workflow services shall support notification for AI/ML training job status changes. | | -| REQ-R1-AI/ML-Discovery -FUN1 | The AI/ML workflow services shall support discovery of registered AI/ML models. | | -| REQ-R1-AIML-Registermodel-FUN1 | The AI/ML workflow services shall support registration and deregistration of an AI/ML model, and query and update of a model registration. | | -| REQ-R1-AIML-Performance-FUN1 | The AI/ML workflow services shall support subscription to AI/ML model performance information. | | -| REQ-R1-AIML-Performance-FUN2 | The AI/ML workflow services shall support notification of AI/ML model performance information. | | -| REQ-R1-AIML-inference -FUN1 | The AI/ML workflow services shall support request and cancel for the inference of an AI/ML model. | | -| REQ-R1-AIML-inference -FUN2 | The AI/ML workflow services shall support query of the inference capability information for a registered AI/ML model. | | -| REQ-R1-AI/ML-Registertraincap -FUN1 | The AI/ML workflow services should support registration, deregistration, update and query of an AI/ML model trainer's training capability. | | - -## 5.7 A1-related services functional requirements - -This clause specifies the A1 policy management services and A1 enrichment information related services functional requirements. - -The functional requirements are specified in table 5.7.1-1. - -**Table 5.7.1-1: A1 policy management services functional requirements.** - -| REQ | Description | Note | -|------------------|----------------------------------------------------------------------------------------------------------------------------|------| -| REQ-R1-A1P- FUN1 | The A1 policy management service shall support querying an A1 policy type. | | -| REQ-R1-A1P- FUN2 | The A1 policy management service shall support querying A1 policy identifiers. | | -| REQ-R1-A1P- FUN3 | The A1 policy management service shall support querying A1 policy type identifiers. | | -| REQ-R1-A1P- FUN4 | The A1 policy management service shall support querying an A1 policy. | | -| REQ-R1-A1P- FUN5 | The A1 policy management service shall support querying the status of an A1 policy. | | -| REQ-R1-A1P- FUN6 | The A1 policy management service shall support subscription to notifications regarding status changes of an A1 policy. | | -| REQ-R1-A1P- FUN7 | The A1 policy management services shall support sending notifications regarding status changes of an A1 policy. | | -| REQ-R1-A1P- FUN8 | The A1 policy management service shall support unsubscription from notifications regarding status changes of an A1 policy. | | -| REQ-R1-A1P- FUN9 | The A1 policy management service shall support creating, querying, updating, and deleting an A1 policy. | | - -# 6 Use cases for Service Management and Exposure - -## 6.1 SME use case 1: Bootstrap - -### 6.1.1 Overview - -This use case provides the description and requirements for retrieving bootstrap information that enables an rApp to optionally discover the SME services for registering and discovering service API. - -### 6.1.2 Background and goal of the use case - -The rApp can use the bootstrap service to discover the SME services for registering and discovering service APIs. - -### 6.1.3 Entities/resources involved in the use case. - -1) SME functions in the role of SME services Producer - -- a) support functionality that allows the rApp to retrieve the bootstrap information that enables it to discover the SME services. - -2) rApp - -- a) retrieves the bootstrap information that enables it to discover the SME services, - -### 6.1.4 Solutions - -#### 6.1.4.1 rApp bootstrap - -Table 6.1.4.1-1: rApp bootstrap use case - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | Find the SME service endpoints, | | -| Actors and Roles |
  • – rApp in the role of SME services Consumer.
  • – SME functions in the role of SME services Producer.
| | -| Assumptions | n/a | | -| Preconditions | The rApp is instantiated. | | -| Begins when | The rApp is ready for registration. | | -| Step 1 | The rApp will initiate a bootstrap request to find the SME endpoints. | | -| Step 2 | The SME functions respond with the details of the service endpoints. | | -| Ends when | The rApp has retrieved the details of the service endpoints. | | -| Exceptions | n/a | | -| Post Conditions | The rApp has retrieved the details of the service endpoints. | | -| Traceability | | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "SMO/Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box " Non-anchored functions in SMO/Non-RT RIC Framework " #cadetBlue - participant "SME functions" as SEF - endbox -==bootstrap == -rApp -> SEF :<>Bootstrap request -activate SEF -SEF -> rApp :<>Bootstrap response -Deactivate SEF - -``` - -![Sequence diagram for rApp bootstrap use case flow. The diagram shows an rApp participant on the left and an SME functions participant inside a 'Non-anchored functions in SMO/Non-RT RIC Framework' box. The sequence starts with a 'bootstrap' activation bar. Step 1: rApp sends a '<>Bootstrap request' message to SME functions. Step 2: SME functions sends a '<>Bootstrap response' message back to rApp. The diagram uses color coding: rApp lifeline is yellow, the SME functions box is teal, and the bootstrap activation bar is black.](bffdddb47fced140f8d17fdc2a29f592_img.jpg) - -Sequence diagram for rApp bootstrap use case flow. The diagram shows an rApp participant on the left and an SME functions participant inside a 'Non-anchored functions in SMO/Non-RT RIC Framework' box. The sequence starts with a 'bootstrap' activation bar. Step 1: rApp sends a '<>Bootstrap request' message to SME functions. Step 2: SME functions sends a '<>Bootstrap response' message back to rApp. The diagram uses color coding: rApp lifeline is yellow, the SME functions box is teal, and the bootstrap activation bar is black. - -Figure 6.1.4.1-1: rApp bootstrap use case flow diagram - -### 6.1.5 Required data. - -The rApp may obtain information about the SME services endpoints from the producer of bootstrap service. - -## 6.2 SME Use case 2: Manage Service Registration - -### 6.2.1 Overview - -This use case allows an rApp as Service Producer to register each of its produced services, update the service information of each of its registered services and deregister each of its registered service as specified in R1GAP [1]. - -### 6.2.2 Background and goal of the use case - -An rApp as a Service Producer can register each of the new services it produces. Other rApps that are Service Consumers can discover the registered services. - -After an rApp as a Service Producer has successfully registered the each of the services it produces, it can update and/or deregister each of the registered services. - -### 6.2.3 Entities/resources involved in the use case. - -- 1) SME functions in the role of SME services Producer: - - a. support functionality to register a service produced by an rApp, - - b. support authorization of an rApp to determine whether an rApp can register a service, update a registered service, and deregister a registered service, - - c. support validation of the new service produced by an rApp that includes determining whether there are conflicts with services registered earlier, - - d. provide the response of success or failure result to Register service request, Update service registration request and Deregister service request. -- 2) rApp - - a. supports to initiate the procedure to register a service it produces, update a registered service, and deregister a registered service. - -### 6.2.4 Solutions - -#### 6.2.4.1 Register Service - -**Table 6.2.4.1-1: Register service use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp successfully registers a service. | | -| Actors and Roles |
  • – rApp in the role of Service Producer that requests service registration.
  • – SME functions in the role of SME services Producer that handles the service registration.
| | -| Assumptions | n/a | | -| Preconditions | The rApp is deployed and authorised to register a service and optionally has the bootstrap info. | | -| Begins when | The rApp determines the need to register a service. | | -| Step 1 (M) | The rApp requests the SME functions to register a service by providing the rAppId and service profile. | | -| Step 2 (M) | The SME functions check whether the rApp is authorised to register a service. | | -| Step 3 (M) | The SME functions validate the information about the new service produced by the rApp, that includes determining whether there are conflicts with services registered earlier. | | -| Step 4 (M) | The SME functions register the service and make the service endpoint available for discovery. | | -| Step 5 (M) | The SME functions respond to the rApp with a success result along with a service identifier. | | -| Ends when | The rApp was able to register a service. | | -| Exceptions | n/a | | -| Post Conditions | The rApp will be able to update and de-register the registered service. | | -| Traceability | REQ-R1-SME-Servicemag-FUN1. | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp -endbox -box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "SME functions" as SME -endbox -rApp->>SME: Register service request (rAppId, service profile) -activate SME - SME --> SME : AuthZ - note right - check authorization to - register a service - end note - SME --> SME : Validate - SME --> SME : register service - SME -->>rApp: Register service response (service identifier) -deactivate SME -@enduml - -``` - -![Sequence diagram for Register service use case flow. Lifelines: rApp and Non-RT RIC (containing SME functions). The process involves: 1. rApp sends Register service request (rAppId, service profile) to SME functions. 2. SME functions perform AuthZ (check authorization to register a service). 3. SME functions perform Validate. 4. SME functions perform register service. 5. SME functions return Register service response (service identifier) to rApp.](dfe556fea00682b09a59427aaf72051c_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant Non-RT RIC as Non-RT RIC - Note right of Non-RT RIC: Non-anchored functions in SMO/Non-RT RIC Framework - Note right of Non-RT RIC: SME functions - rApp->>SME functions: 1 <>Register service request (rAppId, service profile) - Note right of SME functions: 2 AuthZ check authorization to register a service - SME functions-->>SME functions: 3 Validate - SME functions-->>SME functions: 4 register service - SME functions-->>rApp: 5 <>Register service response (service identifier) - -``` - -Sequence diagram for Register service use case flow. Lifelines: rApp and Non-RT RIC (containing SME functions). The process involves: 1. rApp sends Register service request (rAppId, service profile) to SME functions. 2. SME functions perform AuthZ (check authorization to register a service). 3. SME functions perform Validate. 4. SME functions perform register service. 5. SME functions return Register service response (service identifier) to rApp. - -Figure 6.2.4.1-1: Register service use case flow diagram. - -#### 6.2.4.2 Update service registration - -Table 6.2.4.2-1: Update service registration use case. - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | The rApp successfully updates a service registration. | | -| Actors and Roles |
  • rApp in the role of Service Producer that requests updating the registered information of a service.
  • SME functions in the role of SME services Producer in SMO/Non-RT RIC framework that handles the update to registered service.
| | -| Assumptions | n/a | | -| Preconditions | The rApp is authorised to update service. The rApp has registered a service. | | -| Begins when | The rApp determines the need to update the registered information of a service. | | -| Step 1 (M) | The rApp requests the SME functions to update the service information of registered service by providing rAppId, service identifier and delta service profile. | | -| Step 2 (M) | The SME functions check whether the rApp is authorised to update a registered service. | | -| Step 3 (M) | The SME functions update the service information and make the updated service endpoint available for discovery. | | -| Step 4 (M) | The SME functions respond to rApp with successful result. | | -| Ends when | The rApp was able to update service registration. | | -| Exceptions | n/a | | -| Post Conditions | The rApp will be able to update and de-register the registered service. | | -| Traceability | REQ-R1-SME-Servicemag-FUN2. | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber - -``` - -``` - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rApp" as rApp - endbox - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "SME functions" as SME - endbox - rApp -> SME : <>Update service registration request (rAppId, service identifier, service profile) - activate SME - SME --> SME : AuthZ - note right - check authorization to - update a registered service - end note - SME --> SME : service update - deactivate SME - SME -> rApp : <>Update service registration response -@enduml - -``` - -![Sequence diagram for Update service registration use case flow. It shows an rApp sending a request to SME functions, which then perform internal steps (AuthZ, service update) before returning a response. A note indicates that the internal steps involve checking authorization and updating a registered service.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant SME as SME functions - Note right of SME: check authorization to update a registered service - rApp->>SME: 1 <>Update service registration request (rAppId, service identifier, service profile) - activate SME - SME-->>SME: 2 AuthZ - SME-->>SME: 3 service update - deactivate SME - SME-->>rApp: 4 <>Update service registration response - -``` - -Sequence diagram for Update service registration use case flow. It shows an rApp sending a request to SME functions, which then perform internal steps (AuthZ, service update) before returning a response. A note indicates that the internal steps involve checking authorization and updating a registered service. - -Figure 6.2.4.2-1: Update service registration use case flow diagram. - -#### 6.2.4.3 Deregister Service - -Table 6.2.4.3-1: Deregister service use case. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp successfully deregister a service. | | -| Actors and Roles |
  • rApp in the role of Service Producer that requests service deregistration.
  • SME functions in the role of SME services Producer that handles the service deregistration.
| | -| Assumptions | n/a | | -| Preconditions | The rApp is authorised to deregister a service. The rApp has previously registered the service that is requested to be deregistered. | | -| Begins when | The rApp determines the need to deregister a registered service. | | -| Step 1 (M) | The rApp requests the SME functions to deregister a service by providing the rAppId and service identifier. | | -| Step 2 (M) | The SME functions check if rApp is authorised to deregister a service. | | -| Step 3 (M) | The SME functions remove the registered service and remove the service endpoint from the set of endpoints that can be discovered. | | -| Step 4 (M) | The SME functions respond to rApp with a successful result. | | -| Ends when | The rApp was able to deregister a service. | | -| Exceptions | n/a | | -| Post Conditions | The rApp has deregistered a registered service; service endpoint will be no longer available for service discovery. | | -| Traceability | REQ-R1-SME-Servicemag-FUN3. | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rApp" as rApp -endbox - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "SME functions" as SME -endbox -rApp -> SME : <>Deregister service request (rAppId, service identifier) -activate SME -SME --> SME : AuthZ -note right -check authorization to -deregister a registered service -end note -SME --> SME : Remove service profile -SME -> rApp : <>Deregister service response -deactivate SME -@enduml - -``` - -![Sequence diagram for Deregister service use case flow. The diagram shows an rApp lifeline on the left and a Non-RT RIC lifeline on the right. The Non-RT RIC contains a sub-box for 'Non-anchored functions in SMO/Non-RT RIC Framework' which contains the 'SME functions'. The sequence of messages is: 1. rApp sends a '<>Deregister service request (rAppId, service identifier)' to SME functions. 2. SME functions perform an 'AuthZ' check (indicated by a self-call and a note 'check authorization to deregister a registered service'). 3. SME functions perform 'Remove service profile' (indicated by another self-call). 4. SME functions send a '<>Deregister service response' back to the rApp.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) - -Sequence diagram for Deregister service use case flow. The diagram shows an rApp lifeline on the left and a Non-RT RIC lifeline on the right. The Non-RT RIC contains a sub-box for 'Non-anchored functions in SMO/Non-RT RIC Framework' which contains the 'SME functions'. The sequence of messages is: 1. rApp sends a '<>Deregister service request (rAppId, service identifier)' to SME functions. 2. SME functions perform an 'AuthZ' check (indicated by a self-call and a note 'check authorization to deregister a registered service'). 3. SME functions perform 'Remove service profile' (indicated by another self-call). 4. SME functions send a '<>Deregister service response' back to the rApp. - -Figure 6.2.4.3-1: Deregister service use case flow diagram. - -### 6.2.5 Required data. - -The service profile information includes e.g., the name of the service, service type, communication mechanism, interface endpoint details (such as IP address, port number, URI, protocol), version number, and data format. - -For registering a service, the rApp needs to provide the rAppId and the service profile. On successful registration, the SME services Producer assigns a service identifier for the newly registered service and returns it to the rApp. - -For updating a registered service, the rApp needs to provide the rAppId, the service identifier and the delta information that needs to be changed in the service profile. - -For de-registering a registered service, the rApp needs to provide the rAppId and the service identifier. - -NOTE: It is up to the design of the authorization mechanism whether the rAppId will be passed as a separate piece of information or will be embedded in or implied by the authorization information. - -## 6.3 SME use case 3: Discovery of services - -### 6.3.1 Overview - -This usecase allows an rApp as a Service Consumer to discover the available services. - -### 6.3.2 Background and goal of the use case - -The discovery of services is specified as part of Service management and exposure services in R1GAP [1]. - -An rApp in the role of Service Consumer will be able to discover the available services. - -### 6.3.3 Entities/resources involved in the use case. - -- 1) SME functions in the role of SME services Producer - - a. support functionality to discover the available services, - - b. support authorization of an rApp to determine which services an rApp can discover, - - c. retrieve the stored service information and performs filtering of available services based on selection criteria that may be provided by the rApp, - - d. provide response of success or failure to Discover service request. -- 2) rApp - - a. supports initiating the procedure to discover available services, optionally providing selection criteria. - -### 6.3.4 Solutions - -#### 6.3.4.1 Discover the services. - -**Table 6.3.4.1-1: Discover service use case.** - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | The rApp discovers the available services. | | -| Actors and Roles |
  • – rApp in the role of Service Consumer that requests to discover the available services.
  • – SME functions in the role of SME services Producer that handles the discovery of available services.
| | -| Assumptions | n/a | | -| Preconditions | The rApp is authorised to discover services. | | -| Begins when | The rApp determines the need to discover the available services. | | -| Step 1 (M) | The rApp requests the SME functions to discover available services based on the rAppId and optional selection criteria. | | -| Step 2 (M) | The SME functions check which services the rApp is authorized to discover. | | -| Step 3 (M) | The SME functions respond with the set of available services and their service identifiers. The list contains only those available services that match the selection criteria if those were provided by the rApp, or all available services otherwise. | | -| Ends when | The rApp was able to discover the available services. | | -| Exceptions | n/a | | -| Post Conditions | The rApp can request access to the available services. | | -| Traceability | REQ-R1-SME-Service Discovery -FUN1. | | - -``` -@startuml -'https://plantuml.com/sequence-diagram -``` - -``` - -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp -endbox -box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant " SME functions" as SME -endbox -rApp -> SME : <>Discover service request(rAppId) -activate SME -SME --> SME: AuthZ -note right -check authorization to -discover available services -end note -SME -> rApp :<> Discover service response(list of services) -deactivate SME -@enduml - -``` - -![Sequence diagram for Discover service use case flow. It shows an rApp lifeline on the left and a 'Non-anchored functions in SMO/Non-RT RIC Framework' box on the right containing 'SME functions'. The sequence is: 1. rApp sends a 'Discover service request(rAppId)' to SME functions. 2. SME functions perform an 'AuthZ' check (indicated by a self-call and a note 'check authorization to discover available services'). 3. SME functions send a 'Discover service response(list of services)' back to the rApp.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg) - -Sequence diagram for Discover service use case flow. It shows an rApp lifeline on the left and a 'Non-anchored functions in SMO/Non-RT RIC Framework' box on the right containing 'SME functions'. The sequence is: 1. rApp sends a 'Discover service request(rAppId)' to SME functions. 2. SME functions perform an 'AuthZ' check (indicated by a self-call and a note 'check authorization to discover available services'). 3. SME functions send a 'Discover service response(list of services)' back to the rApp. - -Figure 6.3.4.1-1: Discover service use case flow diagram. - -### 6.3.5 Required data. - -For discovering a service, the rApp needs to provide the rAppId and optional selection criteria such as e.g., name of the service, service type, and capabilities. - -The SME functions respond with information about a set of services which includes e.g., endpoint information and service identifiers. - -NOTE: Whether an rApp may be allowed to discover services for which it is currently not authorized but might be able to obtain authorization later is not defined in the present document. - -## 6.4 SME use case 4: Subscribe service availability. - -### 6.4.1 Overview - -This use case allows an rApp as Service Consumer to subscribe to notifications and unsubscribe from notifications regarding changes in service availability, to receive notifications about subscribed events and to update its subscriptions. - -### 6.4.2 Background and goal of the use case - -The subscribe service availability, notify service availability changes, unsubscribe service availability and update service availability subscriptions procedures are defined as part of Service management and exposure services in R1GAP [1]. - -The rApp in the role of Service Consumer can subscribe to notifications and unsubscribe from notifications regarding changes in the availability of services. - -### 6.4.3 Entities/resources involved in the use case. - -- 1) SME functions in the role of SME services Producer - - a) support functionality to subscribe to and unsubscribe from service availability notifications by an rApp as well as to update its subscriptions, - - b) support notifying the rApp regarding the changes in the availability of services, - - c) provide response of success or failure to subscribe service availability request, update service availability subscription request and unsubscribe service availability request. -- 2) rApp - - a) supports functionality to initiate requests to subscribe to and unsubscribe from service availability notifications as well as to update its subscriptions, - - b) supports functionality to accept notifications of the changes in service availability from the SME services Producer. - -### 6.4.4 Solutions - -#### 6.4.4.1 Subscribe to service availability notifications. - -**Table 6.4.4.1-1: Subscribe to service availability notifications.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp subscribes to notifications about changes of the availability of services. | | -| Actors and Roles |
  • – rApp in the role of Service Consumer that requests subscription to service availability notifications.
  • – SME functions in the role of SME services Producer entity that handles the subscription requests.
| | -| Assumptions | n/a | | -| Preconditions | The rApp is authorized to subscribe to notifications about changes in service availability. | | -| Begins when | The rApp determines to subscribe to notifications, regarding changes in the availability of services. | | -| Step 1 (M) | The rApp requests the SME functions to subscribe to notifications regarding changes in the available services with rAppId and optional service identifiers. | | -| Step 2 (M) | The SME functions check whether the rApp is authorized to send a subscription request. | | -| Step 3 (M) | The SME functions respond with subscription identifier. | | -| Ends when | The rApp was able to subscribe to notifications. | | -| Exceptions | n/a | | -| Post Conditions | The rApp can receive notifications when there are any changes in the services availability.
The rApp can unsubscribe from service availability notifications. | | -| Traceability | REQ-R1-SME-Servicesub-FUN1. | | - -``` -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -``` - -``` - -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp -endbox -box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "SME functions " as SME -endbox -autonumber -rApp -> SME : <> Subscribe service availability request(rAppId) -activate SME - SME --> SME : AuthZ - note right - check authorization to - send a subscription request - end note - SME -> rApp : <> Subscribe service availability response (subscription identifier) - deactivate SME -@enduml - -``` - -![UML Sequence diagram showing the interaction between an rApp and SME functions within a Non-RT RIC. The rApp sends a 'Subscribe service availability request' to the SME functions. The SME functions perform an internal 'AuthZ' check, with a note indicating they 'check authorization to send a subscription request'. Finally, the SME functions return a 'Subscribe service availability response' with a subscription identifier to the rApp.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant SME as SME functions - Note right of SME: check authorization to -send a subscription request - rApp->>SME: 1 <> Subscribe service availability request(rAppId) - activate SME - SME-->>SME: 2 AuthZ - SME-->>rApp: 3 <> Subscribe service availability response (subscription identifier) - deactivate SME - -``` - -UML Sequence diagram showing the interaction between an rApp and SME functions within a Non-RT RIC. The rApp sends a 'Subscribe service availability request' to the SME functions. The SME functions perform an internal 'AuthZ' check, with a note indicating they 'check authorization to send a subscription request'. Finally, the SME functions return a 'Subscribe service availability response' with a subscription identifier to the rApp. - -Figure 6.4.4.1-1: Subscribe to of services availability notifications use case flow diagram. - -#### 6.4.4.2 Notify service availability changes. - -**Table 6.4.4.2-1: Notify service availability changes use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp receives notifications about changes in the available services. | | -| Actors and Roles |
  • rApp in the role of Service Consumer that receives notifications on service availability changes.
  • SME functions in the role of SME services Producer that sends notifications on service availability changes.
| | -| Assumptions | n/a | | -| Preconditions | The rApp has subscribed to notifications on service availability changes. | | -| Begins when | The SME functions determine to send notifications, regarding changes in the available service/s to subscribed rApp. | | -| Step 1 (M) | The SME functions detect changes in service availability (due to service registration, service update, service deregistration and heartbeat failure). | | -| Step 2 (M) | The SME functions send notifications regarding the changes to be subscribed rApp with subscription identifier and information about service changes. | | -| Step 3(M) | The rApp processes the changes. | | -| Ends when | The rApp was able to process the changes in the available services. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-SME-Servicesub-FUN2. | | - -``` -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "SME functions " as SME - endbox -autonumber -SME --> SME : Trigger changes in the service/s -SME -> rApp : <> notify changes \n(subscription identifier, service identifier/s) -rApp --> rApp : Process the changes -@enduml -``` - -![Sequence diagram for Notify service availability changes. Lifelines: rApp (Non-RT RIC) and SME functions (Non-anchored functions in SMO/Non-RT RIC Framework). Sequence: 1. SME functions self-call 'Trigger changes in the service/s'; 2. SME functions send '<> notify changes (subscription identifier, service identifier/s)' to rApp; 3. rApp self-call 'Process the changes'.](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg) - -``` -sequenceDiagram - participant rApp - participant SME as SME functions - Note right of SME: 1 Trigger changes in the service/s - SME->>rApp: <> notify changes (subscription identifier, service identifier/s) - Note left of rApp: 3 Process the changes - rApp-->>rApp: -``` - -Sequence diagram for Notify service availability changes. Lifelines: rApp (Non-RT RIC) and SME functions (Non-anchored functions in SMO/Non-RT RIC Framework). Sequence: 1. SME functions self-call 'Trigger changes in the service/s'; 2. SME functions send '<> notify changes (subscription identifier, service identifier/s)' to rApp; 3. rApp self-call 'Process the changes'. - -Figure 6.4.4.2-1: Notify service availability changes use case flow diagram. - -#### 6.4.4.3 Unsubscribe from service availability notifications. - -Table 6.4.4.3-1: Unsubscribe from service availability notifications. - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | The rApp unsubscribes from service availability notifications. | | -| Actors and Roles |
  • – rApp in the role of Service Consumer that requests unsubscribe from service availability notifications.
  • – SME functions in the role of SME services Producer that process the unsubscribe service availability request.
| | -| Assumptions | n/a | | -| Preconditions | The rApp is authorized to unsubscribe from service availability notifications.
The rApp has subscribed to notification changes. | | -| Begins when | The rApp determines to unsubscribe from service availability notifications. | | -| Step 1 (M) | The rApp requests the SME functions to unsubscribe from service availability notifications with rAppId and subscription identifier. | | -| Step 2 (M) | The SME functions check whether the rApp is authorized to unsubscribe. | | -| Step 3 (M) | The SME functions send a response. | | -| Ends when | The rApp was able to unsubscribe from service availability notifications. | | -| Exceptions | n/a | | -| Post Conditions | The rApp is not subscribed to service availability notifications. | | -| Traceability | REQ-R1-SME-Servicesub-FUN3. | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp -endbox -box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "SME functions " as SME -endbox -autonumber -rApp -> SME : <> Unsubscribe from service availability notifications request(subscription identifier) -activate SME - SME -> SME : AuthZ - note right - check authorization to - unsubscribe - end note - SME -> rApp : <> Unsubscribe from service availability notifications response -deactivate SME -@enduml - -``` - -![Sequence diagram for 'Unsubscribe service availability use case flow diagram'. It shows an rApp sending a request to unsubscribe from service availability notifications to SME functions within the Non-RT RIC. The SME functions perform an authorization check and return a response. The diagram includes three numbered steps: 1. rApp to SME functions: Unsubscribe request; 2. SME functions internal call: AuthZ (check authorization to unsubscribe); 3. SME functions to rApp: Unsubscribe response.](a149b400127a3e3e50b3c98d27c5935c_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant SME as SME functions - Note right of SME: check authorization to unsubscribe - rApp->>SME: 1 <> Unsubscribe from service availability notifications request(subscription identifier) - activate SME - SME->>SME: 2 AuthZ - deactivate SME - SME-->>rApp: 3 <> Unsubscribe from service availability notifications response - -``` - -Sequence diagram for 'Unsubscribe service availability use case flow diagram'. It shows an rApp sending a request to unsubscribe from service availability notifications to SME functions within the Non-RT RIC. The SME functions perform an authorization check and return a response. The diagram includes three numbered steps: 1. rApp to SME functions: Unsubscribe request; 2. SME functions internal call: AuthZ (check authorization to unsubscribe); 3. SME functions to rApp: Unsubscribe response. - -Figure 6.4.4.3-1: Unsubscribe service availability use case flow diagram. - -#### 6.4.4.4 Update subscriptions to service availability notifications - -Table 6.4.4.4-1: Update subscriptions to service availability notifications - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | The rApp updates its subscriptions to notifications about changes of the availability of services. | | -| Actors and Roles |
  • rApp in the role of Service Consumer that requests updating one of its subscriptions to service availability notifications.
  • SME functions in the role of SME services Producer entity that handles the update subscription requests.
| | -| Assumptions | n/a | | -| Preconditions | The rApp is authorized to update its subscriptions to notifications about changes in service availability. | | -| Begins when | The rApp determines to update one of its subscriptions to notifications regarding changes in the availability of services. | | -| Step 1 (M) | The rApp requests the SME functions to update one of its subscriptions to notifications regarding changes in the available services with rAppId and subscription identifier. | | -| Step 2 (M) | The SME functions check whether the rApp is authorized to update the subscription. | | -| Step 3 (M) | The SME functions send a response. | | -| Ends when | The rApp was able to update one of its subscriptions to notifications. | | -| Exceptions | n/a | | -| Post Conditions | None | | -| Traceability | REQ-R1-SME-Servicesub-FUN4. | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "SME functions" as SME - endbox -autonumber -rApp -> SME : <> Update service availability subscription request(subscriptionId, -subscription update information) -activate SME - -``` - -``` - -SME --> SME : AuthZ -note right -check authorization to -update the subscription -end note -SME -> rApp : <> Update service availability subscription response -deactivate SME -@enduml - -``` - -![Sequence diagram for 'Update subscriptions to service availability notifications use case flow diagram'. The diagram shows an rApp on the left and 'Non-anchored functions in SMO/Non-RT RIC Framework' on the right. Step 1: rApp sends 'Update service availability subscription request' to SME functions. Step 2: SME functions perform 'AuthZ' (check authorization to update the subscription). Step 3: SME functions send 'Update service availability subscription response' back to rApp.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) - -Sequence diagram for 'Update subscriptions to service availability notifications use case flow diagram'. The diagram shows an rApp on the left and 'Non-anchored functions in SMO/Non-RT RIC Framework' on the right. Step 1: rApp sends 'Update service availability subscription request' to SME functions. Step 2: SME functions perform 'AuthZ' (check authorization to update the subscription). Step 3: SME functions send 'Update service availability subscription response' back to rApp. - -**Figure 6.4.4.1-1: Update subscriptions to service availability notifications use case flow diagram.** - -### 6.4.5 Required data. - -To receive notifications regarding changes in service availability, the rApp as Service Consumer subscribes to notifications by providing rAppId and optional service identifier/s. When the SME functions have successfully processed the request, they respond by providing a subscription identifier. - -The SME functions send notifications to the subscribed rApp when there are changes in the availability of services by providing subscription identifier, service identifiers and information about the changes. - -For updating a subscription, a subscribed rApp needs to provide the subscription identifier and subscription update information. - -For unsubscribing from notifications, a subscribed rApp needs to provide subscription identifier. - -## 6.5 SME use case 5: Query registered services - -### 6.5.1 Overview - -This use case allows an rApp as Service Producer to retrieve the service information of registered services as specified in R1GAP [1]. - -### 6.5.2 Background and goal of the use case - -An rApp as a Service registration service Consumer can retrieve the service information of its registered services from the Service registration services Producer. - -### 6.5.3 Entities/resources involved in the use case. - -- 1) SME functions in the role of Service registration service Producer - - a. support functionality to query the information of registered services, - - b. support authorization of an rApp to determine whether an rApp can query the information of registered services, - - c. retrieve the stored service information and performs filtering of available services based on the selection criteria that may be provided by rApp, - -d. provide the response of success or failure result to Query registered services request. - -#### 2) rApp - -a. supports to initiate the procedure to query the service information of its registered services. - -### 6.5.4 Solutions - -#### 6.5.4.1 Query registered services - -**Table 6.5.4.1-1: Query registered services use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp is aware of the service information of its registered services. | | -| Actors and Roles |
  • – rApp in the role of Service registration service Consumer that queries registered services.
  • – SME functions in the role of Service registration service Producer that handles the queries for registered services.
| | -| Assumptions | n/a | | -| Preconditions | The rApp is authorized to query its registered services. | | -| Begins when | The rApp determines the need to query registered services. | | -| Step 1 (M) | The rApp requests the SME functions to query registered services based on the rAppId and optional selection criteria. | | -| Step 2 (M) | The SME functions check if the rApp is authorized to query registered services. | | -| Step 3 (M) | The SME functions respond with service API descriptions that match the query. | | -| Ends when | The rApp was able to query registered services. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | n/a | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp -endbox -box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant " SME functions" as SME -endbox -rApp -> SME : <> Query registered services request (rAppId) -activate SME -SME --> SME: AuthZ -note right -check authorization to -query registered services -end note -SME -> rApp :<> Query registered services response (service API descriptions) -deactivate SME -@enduml - -``` - -![Sequence diagram for 'Query registered services' use case. It shows an rApp on the left and Non-anchored functions in SMO/Non-RT RIC Framework on the right. Step 1: rApp sends a 'Query registered services request (rAppId)' to SME functions. Step 2: SME functions perform an 'AuthZ' check (with a note 'check authorization to query registered services'). Step 3: SME functions return a 'Query registered services response (service API descriptions)' to the rApp.](fa01531ea2c45beeb4036005da3037a4_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant SME as SME functions - Note right of SME: check authorization to query registered services - rApp->>SME: 1 <> Query registered services request (rAppId) - SME-->>SME: 2 AuthZ - SME-->>rApp: 3 <> Query registered services response (service API descriptions) - -``` - -Sequence diagram for 'Query registered services' use case. It shows an rApp on the left and Non-anchored functions in SMO/Non-RT RIC Framework on the right. Step 1: rApp sends a 'Query registered services request (rAppId)' to SME functions. Step 2: SME functions perform an 'AuthZ' check (with a note 'check authorization to query registered services'). Step 3: SME functions return a 'Query registered services response (service API descriptions)' to the rApp. - -Figure 6.5.4.1-1: Query registered services use case flow diagram. - -### 6.5.5 Required data. - -For querying registered services, the rApp needs to provide the rAppId and optional selection criteria e.g., service name, service type and capabilities. - -The SME functions respond with service API descriptions that match the selection criteria. - -# 7 Use cases for Data Management and Exposure Services - -## 7.1 DME use case 1: Data registration, update, and deregistration. - -### 7.1.1 Overview - -This use case defines how an rApp as DME registration and discovery services consumer registers as producer of data for a DME type, queries a DME type registration, updates a DME type registration and deregisters as producer of data for a DME type. - -### 7.1.2 Background and goal of the use case - -The Register DME type Query DME type registration, Update DME type registration and Deregister DME type procedures are defined as part of Data management and exposure services in R1GAP [1]. - -### 7.1.3 Entities/resources involved in the use case. - -- 1) Data management and exposure functions - - a) support functionality to allow an rApp to register, query, update and deregister as producer of data for a DME type, - - b) support functionality to allow an rApp to register the constraints for how it can produce and deliver data for the registered DME type, - - c) support validation of DME type information (e.g., schema validation). -- 2) rApp - - a) initiates the procedure to register, query, update and deregister as producer of data for a DME type. - -### 7.1.4 Solutions - -#### 7.1.4.1 Register DME type - -**Table 7.1.4.1-1: DME type registration** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp registers as producer of data for a DME type. | | -| Actors and Roles |
  • – rApp in the role of Data registration and discovery service Consumer.
  • – Data management and exposure functions in the role of Data registration and discovery service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the Data management and exposure services.
  • – The rApp not registered as producer of data for the DME type that they intend to register in Data management and exposure functions.
| | -| Begins when | The rApp determines the need to register as a producer of data for a DME type. | | -| Step 1 (M) | The rApp requests the Data management and exposure functions to register as producer of data for a DME type by providing the rAppId and DME type information. | | -| Step 2 (M) | The Data management and exposure functions check with SME functions whether the rApp is authorized to register as producer of data. | | -| Step 3 (M) | The Data management and exposure functions validate the DME type information. | | -| Step 4(M) | The Data management and exposure functions register the rApp as Data Producer of the DME type. Further, in case this rApp is the first producer of data that registers for the DME type, the Data management and exposure functions add the DME type to the set of discoverable DME types. | | -| Step 5(M) | The Data management and exposure functions respond to rApp with successful DME type registration along with DME type registration identifier. | | -| Ends when | The rApp was able to register as producer of data for a DME type. | | -| Exceptions | n/a | | -| Post Conditions | The DME type is discoverable. | | -| Traceability | REQ-R1-DME-Regdatatype-FUN1 | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "Data management and\n exposure functions" as DME - endbox -rApp -> DME :<>Register DME type request (rAppId,\n{ DME type information}) -activate DME -DME --> DME :AuthZ -note right -Check authorization in collaboration -with SME functions -end note - -``` - -``` - -DME --> DME :Validate -note right -validation of DME type information -end note -DME --> DME :Register DME type -DME -> rApp :<>Register DME type response (DME type registration identifier) -deactivate DME -@enduml - -``` - -![Sequence diagram for Register DME type use case flow. Lifelines: rApp and Non-RT RIC (containing Data management and exposure functions). The sequence shows: 1. rApp sends Register DME type request to Data management and exposure functions; 2. AuthZ check with SME functions; 3. Validate DME type information; 4. Register DME type; 5. rApp receives Register DME type response.](e05b36c0d46549e681ce6581422c66b2_img.jpg) - -``` - -sequenceDiagram - participant rApp - box "Non-RT RIC" - participant DME as Data management and exposure functions - end - Note over DME: Non-anchored functions in SMO/Non-RT RIC Framework - rApp->>DME: 1 «R1»Register DME type request (rAppId, { DME type information}) - DME->>DME: 2 AuthZ - Note right of DME: Check authorization in collaboration with SME functions - DME->>DME: 3 Validate - Note right of DME: validation of DME type information - DME->>DME: 4 Register DME type - DME-->>rApp: 5 «R1»Register DME type response (DME type registration identifier) - -``` - -Sequence diagram for Register DME type use case flow. Lifelines: rApp and Non-RT RIC (containing Data management and exposure functions). The sequence shows: 1. rApp sends Register DME type request to Data management and exposure functions; 2. AuthZ check with SME functions; 3. Validate DME type information; 4. Register DME type; 5. rApp receives Register DME type response. - -Fig 7.1.4.1-1: Register DME type use case flow diagram. - -#### 7.1.4.2 Deregister DME type. - -Table 7.1.4.2-1: DME type deregistration - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp deregisters as producer of data for a DME type. | | -| Actors and Roles |
  • – rApp in the role of Data registration and discovery service Consumer.
  • – Data management and exposure functions in the role of Data registration and discovery service Producer.
| | -| Assumptions | The rApp is not producing any data for the DME type. | | -| Preconditions |
  • – The rApp has registered as producer of data for a DME type.
  • – The rApp is authorized to access the Data management and exposure services.
| | -| Begins when | The rApp determines the need to deregister as producer of data for a DME type that it no longer intends to produce. | | -| Step 1 (M) | The rApp requests Data management and exposure functions to be deregistered as producer of data for a DME type by providing rAppId and DME type registration identifier. | | -| Step 2(M) | The Data management and exposure functions check with SME functions whether the rApp is authorized to deregister as producer of data. | | -| Step 3 (M) | The Data management and exposure functions remove the registration of the rApp as producer of data for the DME type. Further, in case no other producer of data for the DME type is registered, the Data management and exposure functions remove the DME type from the set of discoverable DME types. | | -| Step 4 (M) | The Data management and exposure functions respond to the rApp with successful deregistration. | | -| Ends when | The rApp was able to deregister the as producer of data for the DME type. | | -| Exceptions | n/a | | -| Post Conditions | The rApp will not receive any request of data for the DME type and if no other producer is registered, the DME type is not discoverable any longer. | | -| Traceability | REQ-R1-DME-Regdatatype-FUN1 | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "Data management and\n exposure functions" as DME - endbox -rApp -> DME :<>Deregister DME type request \n(rAppId,DME type registration identifier) -activate DME -DME --> DME :AuthZ -note right -Check authorization in collaboration -with SME functions -end note -DME --> DME :Deregister DME type -DME -> rApp :<>Deregister DME type response -deactivate DME -@enduml - -``` - -![Sequence diagram for 'Deregister DME type' use case. The diagram shows an rApp sending a 'Deregister DME type request' to 'Data management and exposure functions'. The functions then perform 'AuthZ' (authorization check) and 'Deregister DME type' operations. A note indicates that the authorization check is done 'in collaboration with SME functions'. Finally, the functions send a 'Deregister DME type response' back to the rApp. The entire process is contained within a 'Non-RT RIC' frame.](cfb98c691c1af5befe32ff9442eea511_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant DME as Data management and exposure functions - Note right of DME: Check authorization in collaboration with SME functions - rApp->>DME: 1 «R1» Deregister DME type request (rAppId, DME type registration identifier) - DME-->>DME: 2 AuthZ - DME-->>DME: 3 Deregister DME type - DME-->>rApp: 4 «R1» Deregister DME type response - -``` - -Sequence diagram for 'Deregister DME type' use case. The diagram shows an rApp sending a 'Deregister DME type request' to 'Data management and exposure functions'. The functions then perform 'AuthZ' (authorization check) and 'Deregister DME type' operations. A note indicates that the authorization check is done 'in collaboration with SME functions'. Finally, the functions send a 'Deregister DME type response' back to the rApp. The entire process is contained within a 'Non-RT RIC' frame. - -Figure 7.1.4.2-1: Deregister DME type use case flow diagram. - -#### 7.1.4.3 Update DME type registration - -Table 7.1.4.3-1: Update DME type registration - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp as producer of data updates a DME type registration it has previously created. | | -| Actors and Roles |
  • – rApp in the role of Data registration and discovery service Consumer.
  • – Data management and exposure functions in the role of Data registration and discovery service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp has registered as producer of data for a DME type.
  • – The rApp is authorized to access the Data management and exposure services.
| | -| Begins when | The rApp determines the need to update a DME type registration it has previously created. | | -| Step 1 (M) | The rApp requests Data management and exposure functions to update a DME type registration it has previously created by providing rAppId, DME type registration identifier and DME type registration update information. | | -| Step 2(M) | The Data management and exposure functions check with SME functions whether the rApp is authorized to update its registered DME type. | | -| Step 3 (M) | The Data management and exposure functions update the registered DME type. | | -| Step 4 (M) | The Data management and exposure functions respond to the rApp with successful result. | | -| Ends when | The rApp has updated the DME type registration. | | -| Exceptions | n/a | | -| Post Conditions | The updated DME type is discoverable. | | -| Traceability | REQ-R1-DME-Regdatatype-FUN1 | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "Data management and\nexposure functions" as DME - endbox -rApp -> DME :<>Update DME type registration request \n(rAppId,DME type registration -identifier, DME type registration update information) -activate DME -DME --> DME :AuthZ -note right -Check authorization in collaboration -with SME functions -end note -DME --> DME :Update DME type registration -DME -> rApp :<>Update DME type registration response -deactivate DME -@enduml - -``` - -![Sequence diagram for Update DME type registration use case flow. Lifelines: rApp and Data management and exposure functions (DME). The diagram shows a request from rApp to DME, an internal AuthZ check by DME, an internal Update DME type registration by DME, and a response from DME to rApp. A note indicates the AuthZ check is in collaboration with SME functions.](6e15fc9ea763541c5913d26f85072ae1_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant DME as Data management and exposure functions - Note right of DME: Check authorization in collaboration with SME functions - rApp->>DME: 1 «R1»Update DME type registration request (rAppId,DME type registration identifier, DME type registration update information) - activate DME - DME-->>DME: 2 AuthZ - DME-->>DME: 3 Update DME type registration - DME-->>rApp: 4 «R1»Update DME type registration response - deactivate DME - -``` - -Sequence diagram for Update DME type registration use case flow. Lifelines: rApp and Data management and exposure functions (DME). The diagram shows a request from rApp to DME, an internal AuthZ check by DME, an internal Update DME type registration by DME, and a response from DME to rApp. A note indicates the AuthZ check is in collaboration with SME functions. - -Figure 7.1.4.3-1: Update DME type registration use case flow diagram. - -#### 7.1.4.4 Query DME type registration - -Table 7.1.4.4-1: Query DME type registration - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp as producer of data query a DME type registration it has previously created. | | -| Actors and Roles |
  • – rApp in the role of Data registration and discovery service Consumer.
  • – Data management and exposure functions in the role of Data registration and discovery service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp has registered as producer of data for a DME type.
  • – The rApp is authorized to access the Data management and exposure services.
| | -| Begins when | The rApp determines the need to query a DME type registration it has previously created. | | -| Step 1 (M) | The rApp requests Data management and exposure functions to query a DME type registration it has previously created by providing rAppId and DME type registration identifier. | | -| Step 2(M) | The Data management and exposure functions check with SME functions whether the rApp is authorized to query its registered DME type. | | -| Step 3 (M) | The Data management and exposure functions query the registered DME type. | | -| Step 4 (M) | The Data management and exposure functions respond to the rApp with DME type registration information. | | -| Ends when | The rApp has queried the DME type registration. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-DME-Regdatatype-FUN1 | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "Data management and\n exposure functions" as DME - endbox -rApp -> DME :<>Query DME type registration request (rAppId, \n DME type registration identifier) -activate DME -DME --> DME :AuthZ -note right -Check authorization in collaboration -with SME functions -end note -DME --> DME :Query DME type registration -DME -> rApp :<>Query DME type registration response (DME type registration information) -deactivate DME -@enduml - -``` - -![Sequence diagram for Query DME type registration use case flow. The diagram shows an rApp on the left interacting with the Non-RT RIC on the right. The Non-RT RIC contains a box for 'Non-anchored functions in SMO/Non-RT RIC Framework', which includes 'Data management and exposure functions'. The sequence is: 1. rApp sends '«R1»Query DME type registration request (rAppId, DME type registration identifier)' to the Data management and exposure functions. 2. The functions send an 'AuthZ' message to SME functions (indicated by a dashed line and a note: 'Check authorization in collaboration with SME functions'). 3. The functions send a 'Query DME type registration' message to the SME functions. 4. The functions return '«R1»Query DME type registration response (DME type registration information)' to the rApp.](145d00f59802048185303f15937ea65c_img.jpg) - -Sequence diagram for Query DME type registration use case flow. The diagram shows an rApp on the left interacting with the Non-RT RIC on the right. The Non-RT RIC contains a box for 'Non-anchored functions in SMO/Non-RT RIC Framework', which includes 'Data management and exposure functions'. The sequence is: 1. rApp sends '«R1»Query DME type registration request (rAppId, DME type registration identifier)' to the Data management and exposure functions. 2. The functions send an 'AuthZ' message to SME functions (indicated by a dashed line and a note: 'Check authorization in collaboration with SME functions'). 3. The functions send a 'Query DME type registration' message to the SME functions. 4. The functions return '«R1»Query DME type registration response (DME type registration information)' to the rApp. - -Figure 7.1.4.4-1: Query DME type registration use case flow diagram. - -### 7.1.5 Required data. - -The DME type information includes the data type identifier, metadata describing the DME type, the schemas for the data content, and constraints for how data can be produced, delivered, and accessed. - -For registering a DME type, the rApp provides the rAppId and DME type information. On successful registration, Data management and exposure functions provide a DME type registration identifier for the registration of the rApp as producer of data for the DME type. - -For querying a DME type registration, the rApp provides the rAppId and DME type registration identifier. - -For updating a DME type registration, the rApp provides the rAppId, DME type registration identifier and DME type registration update information. - -For deregistering a DME type, the rApp provides the rAppId and the DME type registration identifier. - -NOTE: Data management and exposure functions are not required to check whether the rApp is not producing any data for the DME type it tries to deregister. - -## 7.2 DME use case 2: Discovery of DME types. - -### 7.2.1 Overview - -This use case enables an rApp to retrieve information about registered and available DME types and query a DME type identifier and its associated information. It also enables an rApp to subscribe to and unsubscribe from notifications regarding changes in the availability of DME types. - -### 7.2.2 Background and goal of the use case. - -The discover DME type and query DME type information, subscribe DME types changes, unsubscribe DME types changes and notify DME types changes procedure are defined as part of the Data management and exposure services in R1 GAP [1]. - -### 7.2.3 Entities/resources involved in the use case. - -- 1) Data management and exposure functions in the role of Data registration and discovery service Producer, - - a) support functionality allowing rApps to discover the DME types that are available, - -- b) support functionality allowing rApps to retrieve the information about a specific data type identified by a DME type identifier, - - c) support functionality allowing rApps to subscribe to and unsubscribe from notifications regarding the availability of DME types, - - d) support functionality to notify rApps about changes in the availability of DME types. -- 2) rApp in the role of Data registration and discovery service Consumer. -- a) initiates the procedure to discover DME types and query DME type information, subscribe DME types of changes and unsubscribe DME types changes, - - b) supports functionality to receive notifications regarding changes in the availability of DME types. - -### 7.2.4 Solutions - -#### 7.2.4.1 Discover DME type. - -**Table 7.2.4.1-1: Discover DME types.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp retrieves the information on available DME types | | -| Actors and Roles |
  • – rApp in the role of Data registration and discovery service Consumer.
  • – Data management and exposure functions in the role of Data registration and discovery service Producer
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the Data registration and discovery services.
  • – At least one DME type is registered and available with the Data management and exposure functions.
| | -| Begins when | The rApp determines the need to discover the available DME types. | | -| Step 1 (M) | The rApp requests the Data management and exposure functions for the information on the available DME types by providing rAppId and optional filter criteria. | | -| Step 2(M) | The Data management and exposure functions validate if the rApp is authorized to discover the available DME types. | | -| Step 3(M) | The Data management and exposure functions provide the information about available DME types. The list contains only those available DME types that match the filtering criteria if those were provided by the rApp, or all available DME types otherwise. For each DME type, the data type identifier and meta data are provided. | | -| Ends when | The rApp was able to discover the available DME types. | | -| Exceptions | n/a | | -| Post Conditions | The rApp can retrieve specific information related to a DME type by providing its data type identifier. | | -| Traceability | REQ-R1-DME-discoverydatatype-FUN1 | | - -``` -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp -``` - -``` - -endbox -box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "Data management and\nexposure functions" as DME -endbox -rApp -> DME :<> Discover DME types request\n(rAppId, Query information) -activate DME -DME --> DME :AuthZ -note right -Check authorization in collaboration -with SME functions -end note -DME -> rApp :<>Discover DME types response\n(data type identifiers and metadata) -deactivate DME -@enduml - -``` - -![Sequence diagram titled 'Non-RT RIC' showing the interaction between an rApp and Data management and exposure functions (DME). The sequence is: 1. rApp sends a 'Discover DME types request' to DME. 2. DME performs an 'AuthZ' check, with a note indicating 'Check authorization in collaboration with SME functions'. 3. DME sends a 'Discover DME types response' back to the rApp. The diagram is contained within a box labeled 'Non-anchored functions in SMO/Non-RT RIC Framework'.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) - -``` - -sequenceDiagram - box "Non-RT RIC" - participant rApp - participant DME as Data management and exposure functions - end - Note right of DME: Check authorization in collaboration with SME functions - rApp->>DME: 1 «R1» Discover DME types request (rAppId, Query information) - activate DME - DME-->>DME: 2 AuthZ - DME-->>rApp: 3 «R1» Discover DME types response (data type identifiers and metadata) - deactivate DME - -``` - -Sequence diagram titled 'Non-RT RIC' showing the interaction between an rApp and Data management and exposure functions (DME). The sequence is: 1. rApp sends a 'Discover DME types request' to DME. 2. DME performs an 'AuthZ' check, with a note indicating 'Check authorization in collaboration with SME functions'. 3. DME sends a 'Discover DME types response' back to the rApp. The diagram is contained within a box labeled 'Non-anchored functions in SMO/Non-RT RIC Framework'. - -**Figure 7.2.4.1-1: Discover DME types use case flow diagram.** - -#### 7.2.4.2 Query DME type information - -**Table 7.2.4.2-1: Query DME type information** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| -| Goal | The rApp retrieves detailed information on a specific DME type. | | -| Actors and Roles |
  • – rApp in the role of Data registration and discovery service Consumer.
  • – Data management and exposure functions in the role of Data registration and discovery service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the Data registration and discovery service.
  • – The rApp is aware of the data type identifier of the DME type about which it intends to retrieve detail information.
| Error! Reference source not found. | -| Begins when | The rApp determines the need to retrieve the information on a specific DME type. | | -| Step 1 (M) | The rApp requests the Data management and exposure functions for the information on a specific DME type by providing the data type identifier. | | -| Step 2(M) | The Data management and exposure functions validate if the rApp is authorized to retrieve the information. | | -| Step 3(M) | The Data management and exposure functions provide the information on the requested data type identifier | | -| Ends when | The rApp has all the information of a DME type | | -| Exceptions | n/a | | -| Post Conditions | The rApp can formulate a request or subscription for data of that DME type. | | -| Traceability | REQ-R1-DME-discoverydatatype-FUN1 | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "Data management and\n exposure functions" as DME - endbox -rApp -> DME :<>Query DME type information request \n(data type identifier) -activate DME -DME --> DME :AuthZ -note right -Check authorization in collaboration -with SME functions -end note -DME -> rApp :<> Query DME type information response \n(DME type information) -deactivate DME -@enduml - -``` - -![Sequence diagram titled 'Query DME type information use case flow diagram'. It shows an rApp sending a request to 'Data management and exposure functions' within the 'Non-anchored functions in SMO/Non-RT RIC Framework'. The functions perform an authorization check with SME functions and return a response. The diagram includes three numbered steps: 1. Request, 2. AuthZ, 3. Response.](95e259e8cb3519025066052af263f8c0_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant DM as Data management and exposure functions - Note right of DM: Check authorization in collaboration with SME functions - rApp->>DM: 1 «R1» Query DME type information request (data type identifier) - DM-->>DM: 2 AuthZ - DM-->>rApp: 3 «R1» Query DME type information response (DME type information) - -``` - -Sequence diagram titled 'Query DME type information use case flow diagram'. It shows an rApp sending a request to 'Data management and exposure functions' within the 'Non-anchored functions in SMO/Non-RT RIC Framework'. The functions perform an authorization check with SME functions and return a response. The diagram includes three numbered steps: 1. Request, 2. AuthZ, 3. Response. - -Figure 7.2.4.2-1: Query DME type information use case flow diagram - -#### 7.2.4.3 Subscribe DME types changes. - -Table 7.2.4.3-1: Subscribe DME types changes. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| -| Goal | The rApp subscribes to notifications regarding changes in the availability of DME types. | | -| Actors and Roles |
  • – rApp in the role of Data registration and discovery service Consumer.
  • – Data management and exposure functions in the role of Data registration and discovery service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the Data registration and discovery service.
  • – The rApp is aware of the data type identifier of the DME type.
| Error! Reference source not found. | -| Begins when | The rApp determines the need to subscribe to notifications regarding changes in the availability of DME types. | | -| Step 1 (M) | The rApp requests the Data management and exposure functions to subscribe to notifications regarding DME types availability changes by providing the rAppId and data type identifier(s). | | -| Step 2(M) | The Data management and exposure functions validate if the rApp is authorized to subscribe to notifications. | | -| Step 3(M) | The Data management and exposure functions create the subscription. | | -| Step 4(M) | The Data management and exposure functions respond to the request with subscription ID. | | -| Ends when | The rApp was able to subscribe to notifications regarding DME types changes. | | -| Exceptions | n/a | | -| Post Conditions |

The rApp can receive notifications when there are any changes in the set of DME types.

The rApp can unsubscribe from the notifications.

| | -| Traceability | n/a | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true - -``` - -``` - -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "Data management and\n exposure functions" as DME - endbox -rApp -> DME :<>Subscribe DME types changes request \n(rAppId, data type identifier(s)) -activate DME -DME --> DME :Authz -note right -Check authorization in collaboration -with SME functions -end note -DME --> DME : create subscription -DME -> rApp :<> Subscribe DME types changes response \n(subscription ID) -deactivate DME -@enduml - -``` - -![Sequence diagram for 'Subscribe DME types changes' use case flow. Lifelines: rApp and Data management and exposure functions (DME). The process involves: 1. rApp sends a request to DME; 2. DME performs an internal 'Authz' check (noted as collaborating with SME functions); 3. DME performs an internal 'create subscription' step; 4. DME sends a response back to rApp.](9252ccfbbe9e34cb108f0060f2b563f1_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant DME as Data management and exposure functions - Note right of DME: Check authorization in collaboration with SME functions - rApp->>DME: 1 «R1»Subscribe DME types changes request (rAppId, data type identifier(s)) - activate DME - DME-->>DME: 2 Authz - DME-->>DME: 3 create subscription - DME-->>rApp: 4 «R1» Subscribe DME types changes response (subscription ID) - deactivate DME - -``` - -Sequence diagram for 'Subscribe DME types changes' use case flow. Lifelines: rApp and Data management and exposure functions (DME). The process involves: 1. rApp sends a request to DME; 2. DME performs an internal 'Authz' check (noted as collaborating with SME functions); 3. DME performs an internal 'create subscription' step; 4. DME sends a response back to rApp. - -Figure 7.2.4.3-1: Subscribe DME types changes use case flow diagram - -#### 7.2.4.4 Notify DME types changes. - -**Table 7.2.4.4-1: Notify DME types changes.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| -| Goal | The rApp receives a notification regarding a change in the availability of DME types. | | -| Actors and Roles |
  • – rApp in the role of Data registration and discovery service Consumer.
  • – Data management and exposure functions in the role of Data registration and discovery service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the Data registration and discovery service.
  • – The rApp is subscribed to notifications.
| Error! Reference source not found. | -| Begins when | The Data management and exposure functions determine to send a notification regarding a change in the availability of DME types to the subscribed rApp. | | -| Step 1(M) | The Data management and exposure functions send a notification to the subscribed rApp with subscription ID, data type identifier(s) and information about the changes in the availability of DME types | | -| Ends when | The rApp was able to receive the notification. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | n/a | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "Data management and\n exposure functions" as DME - endbox - DME -> rApp : <> Notify DME types changes(subscription ID, data type identifier(s), \navailability change details) -@enduml - -``` - -![Sequence diagram for 'Notify DME types changes' use case. It shows a lifeline for 'rApp' and a participant box for 'Non-anchored functions in SMO/Non-RT RIC Framework' containing 'Data management and exposure functions'. A message arrow labeled '1' and '«R1» Notify DME types changes(subscription ID, data type identifier(s), availability change details)' points from the functions to the rApp lifeline.](030c758fd425016b03290c8f11bef69d_img.jpg) - -Sequence diagram for 'Notify DME types changes' use case. It shows a lifeline for 'rApp' and a participant box for 'Non-anchored functions in SMO/Non-RT RIC Framework' containing 'Data management and exposure functions'. A message arrow labeled '1' and '«R1» Notify DME types changes(subscription ID, data type identifier(s), availability change details)' points from the functions to the rApp lifeline. - -**Figure 7.2.4.4-1: Notify DME types changes use case flow diagram.** - -#### 7.2.4.5 Unsubscribe DME types changes. - -**Table 7.2.4.5-1: Unsubscribe DME types changes.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| -| Goal | The rApp unsubscribes from notifications. | | -| Actors and Roles |
  • – rApp in the role of Data registration and discovery service Consumer.
  • – Data management and exposure functions in the role of Data registration and discovery service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the Data registration and discovery service.
  • – The rApp is subscribed to notifications regarding DME types changes.
| Error! Reference source not found. | -| Begins when | The rApp determines the need to unsubscribe from notifications regarding changes in the availability of DME types. | | -| Step 1 (M) | The rApp requests the Data management and exposure functions to unsubscribe from notifications regarding DME types changes by providing the rAppId and subscription ID. | | -| Step 2(M) | The Data management and exposure functions validate if the rApp is authorized to unsubscribe from notifications. | | -| Step 3(M) | The Data management and exposure functions cancel the subscription | | -| Step 4(M) | The Data management and exposure functions respond to the request. | | -| Ends when | The rApp was able to unsubscribe from notifications regarding changes in the availability of DME types. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | n/a | | - -``` -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "Data management and\n exposure functions" as DME - endbox -rApp -> DME :<>Unsubscribe DME types changes request(rAppId, \nsubscription ID) -activate DME -DME --> DME :Authz -note right -Check authorization in collaboration -with SME functions -end note -DME --> DME : cancel subscription -DME -> rApp :<> Unsubscribe DME types changes response -deactivate DME -@enduml -``` - -![Sequence diagram for 'Unsubscribe DME types of changes' use case. It shows an rApp sending a request to 'Data management and exposure functions' within the 'Non-RT RIC' framework. The functions perform authorization and cancellation, returning a response. A note indicates authorization is checked in collaboration with SME functions.](60ffbad6c0fb7371a57fe8f267d2d141_img.jpg) - -``` - -sequenceDiagram - participant rApp - subgraph Non-RT RIC - participant DME as Data management and exposure functions - end - Note right of DME: Check authorization in collaboration with SME functions - rApp->>DME: 1 «R1» Unsubscribe DME types changes request(rAppId, subscription ID) - DME-->>DME: 2 Authz - DME-->>DME: 3 cancel subscription - DME-->>rApp: 4 «R1» Unsubscribe DME types changes response - -``` - -Sequence diagram for 'Unsubscribe DME types of changes' use case. It shows an rApp sending a request to 'Data management and exposure functions' within the 'Non-RT RIC' framework. The functions perform authorization and cancellation, returning a response. A note indicates authorization is checked in collaboration with SME functions. - -Figure 7.2.4.5-1: Unsubscribe DME types of changes use case flow diagram. - -### 7.2.5 Required data. - -For the Discover DME types request, the rApp provides the rAppId and optional query information. - -The Data management and exposure functions respond with information about all available DME types which includes for each DME type, the data type identifier, and related metadata information. If filtering criteria were provided in the related request, the response only contains information about those DME types that match the filtering criteria. - -For the Query DME type information request, the rApp provides the data type identifier. - -The Data management and exposure functions respond with information related to the DME type. - -For subscription to notifications regarding changes in the availability of DME types, the rApp provides the rAppId and the data type identifier(s). The Data management and exposure functions respond with a unique subscription identifier. - -The Data management and exposure functions send notifications to the subscribed rApp by providing the subscription identifier, data type identifier(s) and related information about the changes in the availability of DME types. - -For unsubscribing from notifications regarding changes in the availability of DME types, the subscribed rApp needs to send the rAppId and subscription identifier. - -## 7.3 DME use case 3: Data offer. - -### 7.3.1 Overview - -This use case allows a Data Producer rApp as Service Consumer to create and terminate a data offer to trigger the collection of a data instance it wishes to deliver to the Data management and exposure functions as Data management and exposure services Producer for collection. - -Further, it allows the Data management and exposure functions as Data management and exposure services Producer to indicate to the Data Producer rApp as Service Consumer that they intend to stop collecting the data instance related to a data offer. - -### 7.3.2 Background and goal of the use case - -A Data Producer rApp as Service Consumer can create a data offer which indicates to the Data management and exposure functions that the rApp intends to deliver a data instance to the Data management and exposure services Producer for collection. - -Further, the Data Producer rApp as Service Consumer can terminate a data offer it has created earlier to indicate to the Data management and exposure functions that the Data Producer no longer wishes to deliver the data instance for collection. - -Finally, the Data management and exposure functions can indicate to the Data Producer rApp as Service Consumer via a data offer termination notification that they will stop collecting a data instance and will terminate the related data offer created earlier by the Data Producer rApp. - -### 7.3.3 Entities/resources involved in the use case. - -- 1) Data management and exposure functions as Data management and exposure services Producer - - a. support functionality to create a data offer as requested by a Data Producer rApp, - - b. support authorization of a Data Producer rApp to determine whether it can create a data offer, - - c. support to send data offer termination notifications, - - d. support to receive the offered data from the rApp and store them, - - e. provide the response of success or failure result to the create data offer request and the terminate data offer request. -- 2) rApp - - a. supports initiating the procedure to create a data offer indicating its intent to deliver data for collection and subsequent storage, - - b. supports to receive data offer termination notifications, - - c. supports to request terminating a data offer created earlier, - - d. supports to produce and deliver the offered data. - -### 7.3.4 Solutions - -#### 7.3.4.1 Create data offer. - -**Table 7.3.4.1-1: Create data offer use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use case | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| -| Goal | The rApp creates a data offer to specify a data instance it produces for collection. | | -| Actors and Roles |
  • – rApp in the role of Data Producer that requests data offer creation.
  • – Data management and exposure functions in the role of Data management and exposure services Producer that handles the data offer creation.
| | -| Assumptions | n/a | | -| Preconditions | The rApp is deployed and is authorized to access the Data management and exposure functions. | | -| Begins when | The rApp determines the need to create a data offer. | | -| Step 1 (M) | The rApp requests the Data management and exposure functions to create a data offer by providing the rAppId, registered data type identifier, further information about the data instance, and intended delivery method(s). | | -| Step 2 (M) | The Data management and exposure functions check whether the rApp is authorized to create a data offer. | | -| Step 3 (M) | The Data management and exposure functions validate the information provided with the request. | | -| Step 4 (M) | The Data management and exposure functions create the data offer and prepare an endpoint for the delivery of notifications or push data. | | -| Step 5 (M) | The Data management and exposure functions respond to the rApp with a success result along with the data offer identifier and endpoint for the delivery of notifications or push data. | | -| Ends when | The rApp was able to create a data offer. | | -| Exceptions | n/a | | -| Post Conditions | The Data management and exposure functions are ready to collect the data instance related to the data offer and the rApp is ready to produce it. Further, the rApp and the Data management and exposure services Producer will be able to terminate the data offer. | | -| Traceability | n/a | | - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 70 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rapp" as rapp - endbox - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "Data management and\n exposure functions" as dme - endbox -endbox -rapp -> dme: <> Create data offer request \n(rAppId, dataTypeId, dataInstanceInfo, -deliveryMethods, notifyEndpointInfo) -activate dme -dme --> dme: AuthZ -``` - -``` - -note right - Check authorization in collaboration - with SME functions -end note -dme --> dme: Validate request -dme --> dme: Create data offer\nand prepare\ndelivery endpoint -dme -> rapp: <> Create data offer response (dataOfferId, deliveryEndpointInfo) -deactivate dme -@enduml - -``` - -![Sequence diagram for 'Create data offer' use case. Lifelines: rApp and Non-RT RIC (containing Data management and exposure functions). The sequence shows: 1. rApp sends a request to the functions; 2. Functions perform authorization (with a note about SME collaboration); 3. Functions validate the request; 4. Functions prepare the data offer and endpoint; 5. Functions return a response to rApp.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant Non-RT RIC as Non-RT RIC - Note right of rApp: Check authorization in collaboration with SME functions - rApp->>Non-RT RIC: 1 <> Create data offer request (rAppId, dataTypeId, dataInstanceIdInfo, deliveryMethods, notifyEndpointInfo) - Note right of Non-RT RIC: 2 AuthZ - Note right of Non-RT RIC: 3 Validate request - Note right of Non-RT RIC: 4 Create data offer and prepare delivery endpoint - Non-RT RIC-->>rApp: 5 <> Create data offer response (dataOfferId, deliveryEndpointInfo) - -``` - -Sequence diagram for 'Create data offer' use case. Lifelines: rApp and Non-RT RIC (containing Data management and exposure functions). The sequence shows: 1. rApp sends a request to the functions; 2. Functions perform authorization (with a note about SME collaboration); 3. Functions validate the request; 4. Functions prepare the data offer and endpoint; 5. Functions return a response to rApp. - -Figure 7.3.4.1-1: Create data offer use case flow diagram. - -#### 7.3.4.2 Deliver offered data. - -Table 7.3.4.2-1: Deliver offered data use case. - -| Use Case Stage | Evolution / Specification | <>
Related use case | -|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| -| Goal | The rApp delivers a data instance it produces for collection, based on a data offer created earlier. | | -| Actors and Roles |
  • – rApp in the role of Data Producer that produces an offered data instance.
  • – DME functions in the role of Data management and exposure services Producer that collect the offered data instance.
| | -| Assumptions | n/a | | -| Preconditions | A data offer has been created. | | -| Begins when | The rApp starts delivering the produced data related to the data offer. | | -| Alternative procedure | Each time a set of data becomes available for delivery, Steps 1-3 are executed if pull is used as the data delivery method. | | -| Step 1 (M) | The Data Producer rApp sends to the Data management and exposure functions a Notify data availability message, including details how to pull the requested data and the data offer identifier. | | -| Step 2 (M) | The Data management and exposure functions send a pull data request message, using the pull delivery details obtained in step 1 | | -| Step 3 (M) | The Data Producer rApp responds with a pull data response, including the data to be collected. | | -| Alternative procedure | Each time a set of data becomes available for delivery, Step 4 is executed if push is used as the data delivery method. | | -| Step 4 (M) | The Data Producer rApp sends to the Data management and exposure functions a push data message, including the data to be collected and the subscription identifier. | | -| Step 5 (M) | The Data management and exposure functions store the delivered data. | | -| Ends when | The rApp has delivered to the Data management and exposure functions for collection the produced data related to the data offer. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | n/a | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke -box #ivory -participant "rApp" as rApp -end box - -box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue -participant "Data management and\nexposure functions" as dme -end box - -loop when data becomes available -alt pull data delivery method - rApp -> dme : <> Notify data availability (pull delivery details, data offer ID) - dme -> rApp : <> Pull data request (pull delivery details) - rApp -> dme : <> Pull data response (with data payload) - -``` - -``` - -else push data delivery method - rApp -> dme : <> Push data message (data payload, data offer ID) -end -dme --> dme: Store data -end -@enduml - -``` - -![Sequence diagram for 'Deliver offered data use case flow diagram'. It shows interactions between an rApp and 'Non-anchored functions in SMO/Non-RT RIC Framework'. A loop titled '[when data becomes available]' contains an alt block for '[pull data delivery method]' with steps 1-3, and a '[push data delivery method]' with step 4. Step 5, 'Store data', occurs after the alt block within the loop.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant DME as Data management and exposure functions - Note right of DME: Non-anchored functions in SMO/Non-RT RIC Framework - - loop when data becomes available - alt pull data delivery method - rApp->>DME: 1 <> Notify data availability (pull delivery details, data offer ID) - DME-->>rApp: 2 <> Pull data request (pull delivery details) - rApp->>DME: 3 <> Pull data response (with data payload) - else push data delivery method - rApp->>DME: 4 <> Push data message (data payload, data offer ID) - end - DME-->>DME: 5 Store data - end - -``` - -Sequence diagram for 'Deliver offered data use case flow diagram'. It shows interactions between an rApp and 'Non-anchored functions in SMO/Non-RT RIC Framework'. A loop titled '[when data becomes available]' contains an alt block for '[pull data delivery method]' with steps 1-3, and a '[push data delivery method]' with step 4. Step 5, 'Store data', occurs after the alt block within the loop. - -Figure 7.3.4.2-1: Deliver offered data use case flow diagram. - -#### 7.3.4.3 Terminate data offer by Data Producer - -**Table 7.3.4.3-1: Terminate data offer by Data Producer use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use case | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| -| Goal | The Data Producer rApp terminates a data offer to indicate it stops producing a data instance for collection. | | -| Actors and Roles |
  • – rApp in the role of Data Producer that requests data offer termination.
  • – Data management and exposure functions in the role of Data management and exposure services Producer that handles the data offer termination.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the Data management and exposure functions.
  • – The rApp has created a data offer.
| | -| Begins when | The rApp determines the need to terminate a data offer it has created previously. | | -| Step 1 (M) | The rApp requests the Data management and exposure functions to terminate a data offer by providing the rAppId and the data offer identifier. | | -| Step 2 (M) | The Data management and exposure functions check whether the rApp is authorized to terminate the data offer. | | -| Step 3 (M) | The Data management and exposure functions validate the information provided with the request. | | -| Step 4 (M) | The Data management and exposure functions stop collecting the data instance and terminate the data offer. | | -| Step 5 (M) | The Data management and exposure functions respond to the rApp with a success result along with the data offer identifier. | | -| Ends when | The rApp was able to terminate the data offer. | | -| Exceptions | n/a | | -| Post Conditions | The data instance associated with the data offer is no longer collected. | | -| Traceability | n/a | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 70 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rapp" as rapp - endbox - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "Data management and\n exposure functions" as dme - endbox -endbox -rapp -> dme: <> Terminate data offer request (rAppId, dataOfferId) -activate dme -dme --> dme: AuthZ -note right - Check authorization in collaboration - with SME functions -end note -dme --> dme: Validate request -dme --> dme: Stop collecting data\nand terminate data offer -dme -> rapp: <> Terminate data offer response (dataOfferId) -deactivate dme - -``` - -@endum1 - -![Sequence diagram for 'Terminate data offer by Data Producer use case'. It shows an rApp sending a 'Terminate data offer request' to 'Data management and exposure functions' within the 'Non-RT RIC'. The functions perform authorization, validation, and stop collecting data, then return a 'Terminate data offer response' to the rApp. A note indicates steps 2 and 3 involve checking authorization with SME functions.](40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant DM as Data management and exposure functions - Note right of DM: Check authorization in collaboration with SME functions - rApp->>DM: 1 <> Terminate data offer request (rAppId, dataOfferId) - DM-->>DM: 2 AuthZ - DM-->>DM: 3 Validate request - DM-->>DM: 4 Stop collecting data and terminate data offer - DM-->>rApp: 5 <> Terminate data offer response (dataOfferId) - -``` - -Sequence diagram for 'Terminate data offer by Data Producer use case'. It shows an rApp sending a 'Terminate data offer request' to 'Data management and exposure functions' within the 'Non-RT RIC'. The functions perform authorization, validation, and stop collecting data, then return a 'Terminate data offer response' to the rApp. A note indicates steps 2 and 3 involve checking authorization with SME functions. - -Figure 7.3.4.3-1: Terminate data offer by Data Producer use case flow diagram. - -#### 7.3.4.4 Terminate data offer by DME services Producer. - -Table 7.3.4.4-1: Terminate data offer by DME services Producer use case. - -| Use Case Stage | Evolution / Specification | <>
Related use case | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| -| Goal | The Data management and exposure functions send a data offer termination notification to indicate they do not intend to collect the data instance from the Data Producer any longer. | | -| Actors and Roles |
  • rApp in the role of Data Producer that receives a data offer termination notification.
  • Data management and exposure functions in the role of Data management and exposure services Producer that sends the data offer termination notification.
| | -| Assumptions | n/a | | -| Preconditions | The rApp has created a data offer. | | -| Begins when | The Data management and exposure functions determine a need to terminate a data offer. | | -| Step 1 (M) | The Data management and exposure functions send to the rApp a data offer termination notification providing the data offer ID. | | -| Step 2 (M) | After a delay to allow the Data Producer to react to the notification, the Data management and exposure functions stop collecting data for the affected data offer and terminate the offer. | | -| Step 3 (M) | The rApp stops delivering to the Data management and exposure functions data related to the affected data offer. | | -| Ends when | The Data management and exposure functions were able to terminate the data offer. | | -| Exceptions | n/a | | -| Post Conditions | The data instance associated with the data offer is no longer collected. | | -| Traceability | n/a | | - -@startuml - -``` - -!pragma teoz true -skinparam ParticipantPadding 70 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rapp" as rapp - endbox -box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "Data management and\nexposure functions" as dme -endbox -endbox -dme -> rapp: <> Terminate data offer notification (dataOfferId) -dme --> dme: Stop collecting data and\nterminate data offer -rapp --> rapp: Stop delivering data -@enduml - -``` - -![Sequence diagram for 'Terminate data offer by DME services Producer use case flow diagram'. The diagram shows two lifelines: 'rapp' (within 'Non-RT RIC') and 'Data management and exposure functions' (within 'Non-anchored functions in SMO/Non-RT RIC Framework'). The sequence of messages is: 1. A solid arrow from 'Data management and exposure functions' to 'rapp' labeled '<> Terminate data offer notification (dataOfferId)'. 2. A dashed self-loop arrow on 'Data management and exposure functions' labeled 'Stop collecting data and terminate data offer'. 3. A dashed self-loop arrow on 'rapp' labeled 'Stop delivering data'.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) - -Sequence diagram for 'Terminate data offer by DME services Producer use case flow diagram'. The diagram shows two lifelines: 'rapp' (within 'Non-RT RIC') and 'Data management and exposure functions' (within 'Non-anchored functions in SMO/Non-RT RIC Framework'). The sequence of messages is: 1. A solid arrow from 'Data management and exposure functions' to 'rapp' labeled '<> Terminate data offer notification (dataOfferId)'. 2. A dashed self-loop arrow on 'Data management and exposure functions' labeled 'Stop collecting data and terminate data offer'. 3. A dashed self-loop arrow on 'rapp' labeled 'Stop delivering data'. - -**Figure 7.3.4.4-1: Terminate data offer by DME services Producer use case flow diagram.** - -#### 7.3.5 Required data. - -The Create data offer request contains the rAppId, the registered data type identifier for the data to be produced and additional information related to the data instance to be produced such as scope, target, context, timing etc. Also, the request contains the supported delivery method(s) for the data and information on the endpoint where to send data offer termination notifications. - -The Create data offer response contains the data offer identifier. In case of the pull delivery method, the response further contains information about the endpoint where to send data availability notifications. In case of the push delivery method, the response further contains information about the endpoint where to push the data. - -The Notify data availability message contains pull delivery details (e.g., a URI) and the data offer identifier. - -In the Pull data request, the Data management and exposure functions use the pull delivery details provided in the notify data availability message to locate the data. - -The Pull data response contains a set of data for collection. - -The Push data message contains a set of data for collection and the data offer identifier. - -The Terminate data offer request contains the rAppId and the data offer ID. - -The Terminate data offer response contains the data offer ID. - -The Data offer termination notification contains the data offer ID. - -## 7.4 DME use case 4: Data request-Data Consumer rApp requests data for consumption from the DME functions. - -### 7.4.1 Overview - -This use case describes how a Data Consumer rApp requests to obtain one-off data for consumption from the DME functions. - -### 7.4.2 Background and goal of the use case - -The Data request and subscription service and Data delivery service procedures are defined as part of the Data management and exposure services in R1GAP [1]. - -After performing the Data discovery procedure, an rApp will be able to request data from the Data management and exposure functions, and the Data management and exposure functions deliver the requested data. - -### 7.4.3 Entities/resources involved in the use case. - -- 1) Data management and exposure functions - - a. support functionality to receive a data request from an rApp, - - b. support functionality to authorize the rApps request for data, - - c. support functionality to provide data to an rApp. -- 2) rApp - - a. support functionality to request data, - - b. support functionality to retrieve the data. - -## 7.4.4 Solutions - -### 7.4.4.1 Data Consumer rApp request data - -**Table 7.4.4.1-1: Use case: A Data Consumer rApp requests data for consumption from the DME functions.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | An rApp obtains the data they intend to consume from the Data Management and Exposure functions via the request data procedure. | | -| Actors and Roles |
  • – Data Consumer rApp in the role of Data management and exposure services Consumer.
  • – Data management and exposure functions in the role of Data management and exposure services Producer that provides data.
| | -| Assumptions | n/a | | -| Preconditions |
  • – rApp is deployed, authenticated, and authorized for usage of the Data management and exposure services.
  • – Data management and exposure functions produce the Data management and exposure services.
| | -| Begins when | An rApp, as a Data Consumer, initiates the request data procedure. | | -| Step 1 (M) | The Data Consumer rApp sends to the Data management and exposure functions a request data request to obtain data for consumption, providing its rAppId and data instance information. | | -| Step 2 (M) | The Data management and exposure functions check the Data Consumer rApps authorization. | | -| Step 3 (M) | The Data management and exposure functions validate the Data Consumer's data request. | | -| Step 4 (M) | The Data management and exposure functions send to the Data Consumer rApp the data request response and include pull delivery details for the requested data instance. | | -| Step 5 (M) | The Data Consumer rApp sends to the Data management and exposure functions a pull data request message, using the pull delivery details received in step 4. | | -| Step 6 (M) | The Data management and exposure functions respond with a pull data response, including in the payload the data to be consumed. | | -| Ends when | The requested data have been delivered to the Data Consumer rApp for consumption. | | -| Exceptions | n/a | | -| Post Conditions | The Data Consumer rApp has consumed the requested data. | | -| Traceability | n/a | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rApp" as rApp - end box - box "Non-RT RIC"" #whitesmoke - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "Data management and \n exposure functions" as dme - end box - dme <- rApp : <> Request data request (rAppId, Data instance information) - dme --> dme :AuthZ - note right - Check authorization in collaboration - with SME functions - -``` - -``` - -end note -dme --> dme: Validate -rApp <- dme : <> Request data response (pull delivery details) -dme <- rApp : <> Pull data request(pull delivery details) -rApp <- dme : <> Pull data response (with data payload) -@enduml - -``` - -![Sequence diagram showing a Data Consumer rApp requesting data from Non-RT RIC Data management and exposure functions. The sequence includes: 1. Request data request (rAppId, Data instance information), 2. AuthZ (Check authorization in collaboration with SME functions), 3. Validate, 4. Request data response (pull delivery details), 5. Pull data request (pull delivery details), 6. Pull data response (with data payload).](2cf3896394a2342a2b46c504ab9a8830_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant DME as Data management and exposure functions - Note right of DME: Check authorization in collaboration with SME functions - rApp->>DME: 1 <> Request data request (rAppId, Data instance information) - DME-->>DME: 2 AuthZ - DME-->>DME: 3 Validate - DME-->>rApp: 4 <> Request data response (pull delivery details) - rApp->>DME: 5 <> Pull data request(pull delivery details) - DME-->>rApp: 6 <> Pull data response (with data payload) - -``` - -Sequence diagram showing a Data Consumer rApp requesting data from Non-RT RIC Data management and exposure functions. The sequence includes: 1. Request data request (rAppId, Data instance information), 2. AuthZ (Check authorization in collaboration with SME functions), 3. Validate, 4. Request data response (pull delivery details), 5. Pull data request (pull delivery details), 6. Pull data response (with data payload). - -**Figure 7.4.4.1-1: A Data Consumer rApp requests data for consumption from the DME functions use case flow diagram.** - -### 7.4.5 Required data. - -For Request data request, the rApp provides to the Data management and exposure functions its rApp identifier (rAppId) and data instance information. Data instance information includes data type identifier, scope i.e., filter on the data, and optional constraints, e.g., time interval (i.e., start time and end time), etc. - -For Request data response, the Data management and exposure functions provide pull delivery details. The pull delivery details are used to locate the requested data instance, e.g., using a URI. - -NOTE: A request identifier, assigned by the Service Producer, can be a part of pull delivery details if necessary, during the protocol design stage. - -For Pull data request, the rApp provides pull delivery details. - -For Pull data response, the Data management and exposure functions provide the requested data. - -## 7.5 DME use case 5: Data request – DME functions request data for collection from a Data Producer rApp. - -### 7.5.1 Overview - -This use case describes how the Data management and exposure functions request to obtain one-off data for consumption from a Data Producer rApp. - -### 7.5.2 Background and goal of the use case - -The Data request and subscription service and Data delivery service procedures are defined as part of Data management and exposure services in R1GAP [1]. - -The Data management and exposure functions request data from a Data Producer rApp, and the Data Producer rApp delivers the requested data. - -### 7.5.3 Entities/resources involved in the use case. - -- 1) Data management and exposure functions - - a. support functionality to request data, - - b. support functionality to retrieve the data. -- 2) rApp - - a. supports functionality to provide data to the DME. - -### 7.5.4 Solutions - -#### 7.5.4.1 DME functions request data for collection from a Data Producer rApp. - -**Table 7.5.4.1-1: Use case: DME functions request data for collection from a Data Producer rApp.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The DME functions obtain the data they intend to collect from the Data Producer rApp via request data procedure | | -| Actors and Roles |
  • – rApp in the role of Data Producer
  • – Data management and exposure functions in the role of Data management and exposure services Consumer
| | -| Assumptions | n/a | | -| Preconditions |
  • – rApp is deployed and authenticated.
  • – Data management and exposure functions have the data type identifier of the needed data.
| | -| Begins when | The Data management and exposure functions initiate the request data procedure to collect data from the Data Producer rApp. | | -| Step 1 (M) | The Data management and exposure functions send the Data Producer rApp a request data request to obtain data for collection, providing data instance information. | | -| Step 2 (M) | The Data Producer rApp validates the Data management and exposure functions data request. | | -| Step 3 (M) | The Data Producer rApp replies with a request data response message, including details how to pull the requested data. | | -| Step 4 (M) | The Data management and exposure functions send to the Data Producer rApp a pull data request message, using the pull delivery details received in step 3. | | -| Step 5 (M) | The Data Producer rApp responds with a pull data response, including in the payload the data to be collected. | | -| Ends when | The requested data have been delivered to the Data management and exposure functions for collection. | | -| Exceptions | n/a | | -| Post Conditions | The Data management and exposure functions have collected the requested data. | | -| Traceability | n/a | | - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke -``` - -``` - -box #ivory - participant "rApp" as rApp -end box -box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "Data management and\n exposure functions" as dme -end box - -dme -> rApp : <> Request data request (Data instance information) -rApp --> rApp: validate -rApp -> dme : <> Request data response (pull delivery details) -dme -> rApp : <> Pull data request (pull delivery details) -rApp -> dme : <> Pull data response (with data payload) -@enduml - -``` - -![Sequence diagram showing the interaction between an rApp and Data management and exposure functions within the Non-RT RIC. The sequence consists of five steps: 1. rApp sends a Request data request (Data instance information) to the functions. 2. rApp performs a self-call 'validate'. 3. rApp sends a Request data response (pull delivery details) to the functions. 4. The functions send a Pull data request (pull delivery details) back to the rApp. 5. The rApp sends a Pull data response (with data payload) to the functions.](3337af75dfee8af7687b4f49914d6c93_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant DME as Data management and exposure functions - Note right of DME: Non-anchored functions in SMO/Non-RT RIC Framework - rApp->>DME: 1 <> Request data request (Data instance information) - rApp-->>rApp: 2 validate - rApp->>DME: 3 <> Request data response (pull delivery details) - DME->>rApp: 4 <> Pull data request (pull delivery details) - rApp->>DME: 5 <> Pull data response (with data payload) - -``` - -Sequence diagram showing the interaction between an rApp and Data management and exposure functions within the Non-RT RIC. The sequence consists of five steps: 1. rApp sends a Request data request (Data instance information) to the functions. 2. rApp performs a self-call 'validate'. 3. rApp sends a Request data response (pull delivery details) to the functions. 4. The functions send a Pull data request (pull delivery details) back to the rApp. 5. The rApp sends a Pull data response (with data payload) to the functions. - -Figure 7.5.4.1-1: DME functions request data for collection from a Data Producer rApp use case flow diagram. - -### 7.5.5 Required data. - -For the Request data request, the Data management and exposure functions provide data instance information. Data instance information includes data type identifier, scope (i.e., filter on the data), and optional constraints, e.g., time interval (i.e., start time and end time), etc. - -For Request data response, the Data Producer rApp provides pull delivery details. The pull delivery details are used to locate the requested data instance, e.g., using a URI. - -NOTE: A request identifier, assigned by the service producer, can be a part of pull delivery details if necessary, during the protocol design stage. - -For Pull data request, the Data management and exposure functions use the pull delivery details provided in the Request data response to locate the data. - -For Pull data response, the rApp provides the requested data. - -## 7.6 DME use case 6: The DME functions subscribe data for collection from a Data Producer rApp. - -### 7.6.1 Overview - -This use case describes how the DME functions subscribe data for collection from a Data Producer rApp, update the data subscription, query the data subscription, obtain the data, query the status of the data subscription, and terminate the data subscription. - -### 7.6.2 Background and goal of the use case. - -The Data subscription service and Data delivery service procedures are defined as part of Data management and exposure services in R1GAP [1]. - -The Data management and exposure functions subscribe data from a Data Producer rApp for collection, update the data subscription, query the data subscription, and its status, and terminate the data subscription. - -The Data Producer rApp delivers the requested data. - -### 7.6.3 Entities/resources involved in the use case. - -- 1) Data management and exposure functions - - a. support functionality to request subscription to data, update the data subscription, query the data subscription, query the subscription status, and termination of the subscription, - - b. support functionality to obtain the data for collection. -- 2) Data Producer rApp - - a. supports functionality to subscribe to data, - - b. supports functionality to update a data subscription, - - c. supports functionality to query a data subscription, - - d. supports functionality to terminate a data subscription, - - e. supports functionality to provide data to the DME functions, - - f. supports functionality to provide the status of data subscriptions. - -### 7.6.4 Solutions - -#### 7.6.4.1 DME functions subscribe data for collection from a Data producer rApp. - -**Table 7.6.4.1-1: Use case: The DME functions subscribe data for collection from a Data Producer rApp.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The Data management and exposure functions obtain data they intend to collect from a Data Producer rApp via the subscribe data procedure. | | -| Actors and Roles |
  • – rApp in the role of Data Producer.
  • – Data management and exposure functions: entity in the role of Data subscription service Consumer and Pull data service Consumer and/or Push data service Producer and/or owner of the point to multipoint data stream configuration.
| | -| Assumptions | If point to multipoint data stream is used as delivery method, data stream endpoint is configured as part of preconditions, or the configuration may also take place as part of the subscription. | | -| Preconditions |
  • – rApp is deployed and authenticated.
  • – Data management and exposure functions have the data type identifier of the needed data.
  • – For point to multipoint data stream delivery method, the data stream endpoint has been configured.
| | -| Begins when | The Data management and exposure functions initiate the Subscribe data procedure to collect a data instance. | | -| Step 1 (M) | The Data management and exposure functions send to the Data Producer rApp a subscribe data request to subscribe the data to be collected providing Data instance information. | | -| Alternative procedure | If point to multipoint data stream is used as delivery method, the Data management and exposure functions provide a data stream endpoint. | | -| Step 2 (M) | The Data management and exposure functions send to the Data Producer rApp a subscribe data request to subscribe the data to be collected providing Data instance information and data stream endpoint. | | -| Step 3 (M) | The Data Producer rApp validates the request. | | -| Step 4 (M) | The Data Producer rApp creates the subscription. | | -| Step 5 (M) | The Data Producer rApp replies with a subscribe data response message, including the subscription identifier. | | -| Alternative procedure | Each time a set of data becomes available for delivery, Steps 5-7 are executed if pull data is used as the data delivery method. | | -| Step 6 (M) | The Data Producer rApp sends to the Data management and exposure functions a Notify data availability message, including details how to pull the requested data and the subscription identifier. | | -| Step 7 (M) | The Data management and exposure functions send a pull data request message, using the pull delivery details obtained in step 5. | | -| Step 8 (M) | The Data Producer rApp responds with a pull data response, including the data to be collected. | | -| Alternative procedure | Each time a set of data becomes available for delivery, Step 8 is executed if push data is used as the data delivery method. | | -| Step 9 (M) | The Data Producer rApp sends to the Data management and exposure functions a push data message, including the subscription identifier and the data to be collected. | | -| Alternative procedure | Each time a set of data becomes available for delivery, Step 10 is executed if point to multipoint data stream is used as the delivery method. | | -| Step 10 (M) | The Data Producer rApp send the data-to-data stream endpoint. | | -| Ends when | The subscribed data instance has been delivered for collection to the Data management and exposure functions. | | -| Exceptions | n/a | | -| Post Conditions | The Data management and exposure functions have collected the needed data. | | -| Traceability | REQ-R1-DME-Data subscription-FUN1, REQ-R1-DME-Data delivery-FUN1 | | - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -``` - -``` -box "Non-RT RIC" #whitesmoke -box #ivory -participant "rApp" as rApp -end box -box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue -participant "Data management and\n exposure functions" as dme -end box -alt Pull or push data delivery method -dme -> rApp : <> subscribe data request (data instance information) -else Point to multipoint data stream delivery method -dme -> rApp : <> subscribe data request (data instance information,\n data stream enpoint) -end -activate dme -rApp --> rApp : Validate request -rApp --> rApp : Create subscription -rApp -> dme : <> subscribe data response (subscription ID) -deactivate dme - -loop when data becomes available -alt Pull data delivery method -rApp -> dme : <> Notify data availability (pull delivery details, subscription ID) -dme -> rApp : <> Pull data request -rApp -> dme : <> Pull data response (with data payload) -else Push data delivery method -rApp -> dme : <> Push data message (subscription ID, data payload) -else Point to multipoint data stream delivery method -rApp -> dme: <> rApp sends data payload to data stream endpoint - -end -end -@enduml -``` - -![Sequence diagram titled 'Non-RT RIC' showing the interaction between an rApp and Non-anchored functions in SMO/Non-RT RIC Framework for data subscription. The diagram includes an 'alt [Pull or push data delivery method]' block with 'Point to multipoint data stream delivery method' and a 'loop [when data becomes available]' block with 'alt [Pull data delivery method]' and 'Push data delivery method'.](fed4a04822c24fb22cca3a14f4ddae83_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant DME as Data management and exposure functions - Note right of DME: Non-anchored functions in SMO/Non-RT RIC Framework - - alt Pull or push data delivery method: Point to multipoint data stream delivery method - rApp->>DME: 1 «R1» subscribe data request (data instance information) - rApp->>DME: 2 «R1» subscribe data request (data instance information, data stream endpoint) - end - DME-->>rApp: 3 Validate request - DME-->>rApp: 4 Create subscription - DME->>rApp: 5 «R1» subscribe data response (subscription ID) - - loop when data becomes available - alt Pull data delivery method - DME->>rApp: 6 «R1» Notify data availability (pull delivery details, subscription ID) - rApp->>DME: 7 «R1» Pull data request - DME->>rApp: 8 «R1» Pull data response (with data payload) - else Push data delivery method - DME->>rApp: 9 «R1» Push data message (subscription ID, data payload) - else Point to multipoint data stream delivery method - rApp->>DME: 10 «R1» rApp sends data payload to data stream endpoint - end - end - -``` - -Sequence diagram titled 'Non-RT RIC' showing the interaction between an rApp and Non-anchored functions in SMO/Non-RT RIC Framework for data subscription. The diagram includes an 'alt [Pull or push data delivery method]' block with 'Point to multipoint data stream delivery method' and a 'loop [when data becomes available]' block with 'alt [Pull data delivery method]' and 'Push data delivery method'. - -Figure 7.6.4.1-1: DME functions subscribe data for collection from a Data Producer rApp use case flow diagram. - -7.6.4.2 DME functions terminate the data subscription. - -**Table 7.6.4.2-1: Use case: The DME functions terminate the data subscription.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Data management and exposure functions terminate the data subscription. | | -| Actors and Roles |
  • – rApp in the role of Data Producer
  • – Data management and exposure functions in the role of Data subscription service Consumer
| | -| Assumptions | n/a | | -| Preconditions | The DME functions have subscribed data. | | -| Begins when | The DME functions determine to terminate the data subscription. | | -| Step 1 (M) | The DME functions send the Unsubscribe data request with subscription ID as parameter. | | -| Step 2 (M) | The rApp validates the request. | | -| Step 3 (M) | The rApp removes the data subscription. | | -| Step 4 (M) | The rApp responds to the request. | | -| Ends when | The DME functions have terminated the data subscription. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-DME-Data subscription-FUN2 | | - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke -box #ivory -participant rApp as rApp -end box -box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue -participant "Data management and\n exposure functions" as DME -end box - -rApp <- DME: <> Unsubscribe data request\n (subscription ID) -activate rApp -rApp --> rApp : validate request -rApp --> rApp : remove subscription -rApp -> DME: <> Unsubscribe data response -deactivate rApp -@enduml -``` - -![Sequence diagram showing the termination of a data subscription. The diagram is titled 'Non-RT RIC' and contains a sub-box 'Non-anchored functions in SMO/Non-RT RIC Framework'. It features two lifelines: 'rApp' and 'Data management and exposure functions'. The sequence of messages is: 1. rApp sends '<> Unsubscribe data request (subscription ID)' to the functions; 2. The functions send a 'validate request' back to rApp; 3. The functions send a 'remove subscription' message to rApp; 4. The functions send '<> Unsubscribe data response' back to rApp.](52c40e2f443985dc63f45dec57d90c8c_img.jpg) - -Sequence diagram showing the termination of a data subscription. The diagram is titled 'Non-RT RIC' and contains a sub-box 'Non-anchored functions in SMO/Non-RT RIC Framework'. It features two lifelines: 'rApp' and 'Data management and exposure functions'. The sequence of messages is: 1. rApp sends '<> Unsubscribe data request (subscription ID)' to the functions; 2. The functions send a 'validate request' back to rApp; 3. The functions send a 'remove subscription' message to rApp; 4. The functions send '<> Unsubscribe data response' back to rApp. - -Figure 7.6.4.2-1: The DME functions terminate the data subscription. - -### 7.6.4.3 DME functions update a data subscription. - -Table 7.6.4.3-1: Use case: The DME functions update a data subscription. - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | Data management and exposure functions update a data subscription. | | -| Actors and Roles |
  • – rApp in the role of Data Producer
  • – Data management and exposure functions in the role of Data subscription service Consumer
| | -| Assumptions | n/a | | -| Preconditions | The DME functions have subscribed to data instance. | | -| Begins when | The DME functions determine to update a data subscription. | | -| Step 1 (M) | The DME functions send the Update data subscription request with subscription ID and data subscription update information as parameter. | | -| Step 2 (M) | The rApp validates the request. | | -| Step 3 (M) | The rApp updates data subscription. | | -| Step 4 (M) | The rApp responds to the request. | | -| Ends when | The DME functions have updated the data subscription. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-DME-Data subscription-FUN3 | | - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke -box #ivory -participant rApp as rApp -end box -box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue -participant "Data management and\n exposure functions" as DME -end box -``` - -``` - -rApp <- DME: <> Update data subscription request\n (subscription ID,\n data subscription update information) -activate rApp -rApp --> rApp : validate request -rApp --> rApp : update data subscription -rApp -> DME: <> Update data subscription response -deactivate rApp -@enduml - -``` - -![Sequence diagram showing the interaction between an rApp and Non-anchored functions in SMO/Non-RT RIC Framework for updating a data subscription. The diagram includes four steps: 1. rApp sends an Update data subscription request; 2. rApp validates the request; 3. rApp updates the data subscription; 4. rApp sends an Update data subscription response.](61a7f401eb46fe99a71f27bc37493f04_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant Non-anchored functions in SMO/Non-RT RIC Framework - Note right of Non-anchored functions: Data management and exposure functions - rApp->>Non-anchored functions: 1 «R1» Update data subscription request (subscription ID, data subscription update information) - activate rApp - rApp-->>rApp: 2 validate request - rApp-->>rApp: 3 update data subscription - rApp->>Non-anchored functions: 4 «R1» Update data subscription response - deactivate rApp - Note right of Non-anchored functions: Data management and exposure functions - -``` - -Sequence diagram showing the interaction between an rApp and Non-anchored functions in SMO/Non-RT RIC Framework for updating a data subscription. The diagram includes four steps: 1. rApp sends an Update data subscription request; 2. rApp validates the request; 3. rApp updates the data subscription; 4. rApp sends an Update data subscription response. - -Figure 7.6.4.3-1: The DME functions update the data subscription. - -7.6.4.4 DME functions query a data subscription. - -Table 7.6.4.4-1: Use case: The DME functions query a data subscription. - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | Data management and exposure functions query a data subscription. | | -| Actors and Roles |
  • – rApp in the role of Data Producer
  • – Data management and exposure functions in the role of Data subscription service Consumer
| | -| Assumptions | n/a | | -| Preconditions | The DME functions have subscribed to data instance. | | -| Begins when | The DME functions determine to query a data subscription. | | -| Step 1 (M) | The DME functions send the Query data subscription request with subscription ID as parameter. | | -| Step 2 (M) | The rApp validates the request. | | -| Step 3 (M) | The rApp responds to the request with data subscription information. | | -| Ends when | The DME functions have queried the data subscription. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-DME-Data subscription-FUN4 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -``` - -``` - -autonumber -box "Non-RT RIC" #whitesmoke -box #ivory -participant rApp as rApp -end box -box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue -participant "Data management and\n exposure functions" as DME -end box - -rApp <- DME: <> Query data subscription request\n (subscription ID) -activate rApp -rApp --> rApp : validate request -rApp -> DME: <> Query data subscription response\n (data subscription information) -deactivate rApp -@enduml - -``` - -![Sequence diagram showing the interaction between rApp and Data management and exposure functions within the Non-RT RIC framework. The process involves three steps: 1. rApp sends a Query data subscription request (subscription ID) to DME; 2. rApp validates the request internally; 3. rApp receives a Query data subscription response (data subscription information) from DME.](fcc757566216206ceddbd6c775e8db02_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant DME as Data management and exposure functions - Note right of DME: Non-anchored functions in SMO/Non-RT RIC Framework - rApp->>DME: 1 <> Query data subscription request (subscription ID) - activate rApp - rApp-->>rApp: 2 validate request - rApp->>DME: 3 <> Query data subscription response (data subscription information) - deactivate rApp - -``` - -Sequence diagram showing the interaction between rApp and Data management and exposure functions within the Non-RT RIC framework. The process involves three steps: 1. rApp sends a Query data subscription request (subscription ID) to DME; 2. rApp validates the request internally; 3. rApp receives a Query data subscription response (data subscription information) from DME. - -Figure 7.6.4.4-1: The DME functions query the data subscription. - -### 7.6.4.5 DME functions query status of data subscription. - -Table 7.6.4.5-1: Use case: The DME functions query status of data subscription. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Data management and exposure functions query status of a created data subscription. | | -| Actors and Roles |
  • – rApp in the role of Data Producer
  • – Data management and exposure functions in the role of Data subscription service Consumer
| | -| Assumptions | n/a | | -| Preconditions | The DME functions have subscribed to data instance. | | -| Begins when | The DME functions determine the need to query the status a data subscription. | | -| Step 1 (M) | The DME functions send the Query data subscription status request with subscription ID as parameter. | | -| Step 2 (M) | The rApp validates the request. | | -| Step 3 (M) | The rApp responds to the request with the status of the data subscription. | | -| Ends when | The DME functions have queried the status of data subscription. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-DME-Data subscription-FUN1 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke -box #ivory -participant rApp as rApp -end box -box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue -participant "Data management and\n exposure functions" as DME -end box - -rApp <- DME: <> Query data subscription status request\n (subscription ID) -activate rApp -rApp --> rApp : validate request -rApp -> DME: <> Query data subscription status response\n (data subscription information) -deactivate rApp -@enduml - -``` - -![UML Sequence diagram showing the interaction between an rApp and Data management and exposure functions within the Non-RT RIC. The sequence starts with the rApp sending a 'Query data subscription status request' (subscription ID) to the functions. The functions then perform an internal 'validate request' step. Finally, the functions return a 'Query data subscription status response' (data subscription information) to the rApp.](5801c19431e76330430e92a598cc7a16_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant DME as Data management and exposure functions - Note right of DME: Non-anchored functions in SMO/Non-RT RIC Framework - rApp->>DME: 1 «R1» Query data subscription status request (subscription ID) - activate rApp - rApp-->>rApp: 2 validate request - rApp->>DME: 3 «R1» Query data subscription status response (data subscription information) - deactivate rApp - -``` - -UML Sequence diagram showing the interaction between an rApp and Data management and exposure functions within the Non-RT RIC. The sequence starts with the rApp sending a 'Query data subscription status request' (subscription ID) to the functions. The functions then perform an internal 'validate request' step. Finally, the functions return a 'Query data subscription status response' (data subscription information) to the rApp. - -Figure 7.6.4.5-1: The DME functions query the status of data subscription. - -### 7.6.5 Required data. - -In the subscribe data request, the Data management and exposure functions provide data instance information. Data instance information includes the data type identifier, scope (i.e., filter on the data), periodicity of collection and additional optional constraints periodicity of reporting, etc. - -If point to multipoint data stream is used as delivery method, the Data management and exposure functions provide the data stream endpoint to Data Producer to send data. - -In the subscribe data response, the Data Producer rApp provides the subscription identifier. The subscription identifier is a unique identifier assigned by service Producer to identify a specific subscription. - -In the update data subscription request, the Data management and exposure functions provide the subscription identifier and data subscription update information. - -In the query data subscription request, the Data management and exposure functions provide the subscription identifier. In the query data subscription response, the Data Producer rApp provides the data subscription information. - -In the unsubscribe data request, the Data management and exposure functions provide the subscription identifier. - -In the notify data availability message, the Data Producer rApp provides pull delivery details (e.g., a URI) and the subscription identifier. - -In the pull data request, the Data management and exposure functions use the pull delivery details provided in the notify data availability message to locate the data. - -In the pull data response, the Data Producer rApp provides a set of data for collection. - -In the query data subscription status request, the Data management and exposure functions provide the subscription identifier. - -In the query data subscription status response, the Data Producer rApp provides the data subscription status information. - -In the push data message, the Data Producer rApp provides the subscription identifier and a set of data for collection. - -When point to multipoint data stream is used, Data Producer rApp sends the data to the data stream endpoint. - -## 7.7 DME use case 7: A Data Consumer rApp subscribes data for consumption using the Data request and subscription service. - -### 7.7.1 Overview - -This use case describes how a Data Consumer rApp subscribes data it needs to consume, update the data subscription, query the data subscription obtains the data, and terminates the data subscription. - -### 7.7.2 Background and goal of the use case - -The Data subscription service and Data delivery service procedures are defined as part of Data management and exposure services in R1GAP [1]. - -A Data Consumer rApp will be able to subscribe data based on the DME type information it is aware of e.g., from discovery or configuration, update the data subscription, query the data subscription, and terminate the data subscription using Data management and exposure procedures. - -Data management and exposure functions deliver the subscribed data using Data delivery services. - -### 7.7.3 Entities/resources involved in the use case. - -- 1) Data management and exposure functions - - a. support services that allow an rApp to subscribe data, update the data subscription, query the data subscription and terminate the data subscription, - - b. deliver the subscribed data to an rApp that has subscribed. -- 2) rApp - - a. supports functionality to initiate a data subscription, - - b. supports functionality to initiate an update of a data subscription, - - c. supports functionality to initiate a query of a data subscription, - - d. supports functionality to initiate the termination of a data subscription, - - e. supports functionality to obtain the subscribed data. - -## 7.7.4 Solutions - -### 7.7.4.1 Subscribe data and delivery of subscribed data. - -**Table 7.7.4.1-1: Subscribing data and delivery of subscribed data.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | rApp subscribes the data it needs to consume, and the subscribed data is delivered. | | -| Actors and Roles |
  • – rApp in the role of Data management and exposure services Consumer.
  • – Data management and exposure functions in the role of Data management and exposure services Producer.
| | -| Assumptions | If point to multipoint data stream is used as delivery method, data stream endpoint configured as part of preconditions, or the configuration may also take place as part of the subscription. | | -| Preconditions |
  • – The rApp is authorized to access the Data management and exposure services,
  • – The rApp has obtained the DME type information e.g., by discovery or configuration.
  • – For point to multipoint data stream delivery method, data stream endpoint has been configured by Data management and exposure functions.
| | -| Begins when | The rApp determines the need to subscribe data it needs to consume. | | -| Step 1 (M) | The rApp subscribes data that it needs to consume with rAppId and Data instance information as parameters. | | -| Step 2 (M) | The Data management and exposure functions check for authorization with SME functions whether the rApp is authorized to subscribe data. | | -| Step 3 (M) | The Data management and exposure functions validate the request. | | -| Step 4 (M) | The Data management and exposure functions create the subscription. | | -| Step 5 (M) | The Data management and exposure functions respond to the request with subscription ID as a parameter. | | -| Alternative procedure | If point to multipoint data stream is used as a delivery method, the Data management and exposure functions provide the data stream endpoint. | | -| Step 6 (M) | The Data management and exposure functions respond to the request with subscription ID as a parameter and data stream endpoint. | | -| Alternative procedure | Each time a set of subscribed data becomes available for delivery, Steps 7-9 are executed if “pull data” is used as the data delivery method. | | -| Step 7 (M) | The Data management and exposure functions notify the availability of data with subscription ID and pull delivery details as parameters. | | -| Step 8 (M) | The rApp send a pull data request based on the pull delivery details received in the previous step. | | -| Step 9 (M) | The Data management and exposure functions respond to the pull data request with data payload as a parameter. | | -| Alternative procedure | Each time a set of subscribed data becomes available for delivery, Step 10 is executed if the “push data” is used as the data delivery method. | | -| Step 10 (M) | The Data management and exposure functions send a push data message with subscription ID and data payload as parameters. | | -| Alternative procedure | Each time a set of data becomes available for delivery, Step 11 is executed if point to multipoint data stream is used as the data delivery method. | | -| Step 11 (M) | rApp fetches the data from the data stream endpoint. | | -| Ends when | The rApp has terminated the subscription. | | -| Exceptions | n/a | | -| Post Conditions | The rApp has the data it determined it needed. | | -| Traceability | REQ-R1-DME-Data subscription-FUN1, REQ-R1-DME-Data delivery-FUN1 | | - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -``` - -``` - -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke -box #ivory -participant rApp as rApp -end box -box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue -participant "Data management and\n exposure functions" as DME -end box - -rApp -> DME : <> Subscribe data request (rAppId, Data instance information) -DME --> DME : AuthZ -note right -Check authorization in collaboration -with SME functions -end note -DME --> DME : Validate request -DME --> DME : Create subscription -Alt Pull or push delivery method - -rApp <- DME : <> Subscribe data response(subscription ID) -else Point to multipoint data stream delivery method -rApp <- DME : <> Subscribe data response(subscription ID, data stream endpoint) -end - -loop when data becomes available -alt Pull data delivery method -rApp <- DME : <> Notify data availability (pull delivery details, subscription ID ) -rApp -> DME : <> Pull data request -rApp <- DME : <> Pull data response (data payload) -else Push data delivery method -DME -> rApp : <> Push data message (subscription ID, data payload) -else Point to multipoint data stream delivery method -rApp -> DME: <> rApp fetches data payload from data stream endpoint - -end -end - -@enduml - -``` - -![Sequence diagram for 'Subscribe data and delivery of subscribed data use case flow diagram'. It shows interactions between an rApp and 'Non-anchored functions in SMO/Non-RT RIC Framework'. The process involves subscription requests, authorization checks, and data delivery via pull or push methods. A note indicates that step 2 (AuthZ) involves checking authorization in collaboration with SME functions.](c3254408eadbf152632a8faf16310722_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant Non-anchored functions in SMO/Non-RT RIC Framework - Note right of Non-anchored functions: Check authorization in collaboration with SME functions - - Note left of Non-anchored functions: "Non-RT RIC" - Note right of Non-anchored functions: Data management and exposure functions - - rApp->>Non-anchored functions: 1 «R1» Subscribe data request (rAppId, Data instance information) - Non-anchored functions-->>rApp: 2 AuthZ - Non-anchored functions-->>rApp: 3 Validate request - Non-anchored functions-->>rApp: 4 Create subscription - - alt Pull or push delivery method - Note left of Non-anchored functions: [Point to multipoint data stream delivery method] - Non-anchored functions-->>rApp: 5 «R1» Subscribe data response(subscription ID) - else Point to multipoint data stream delivery method - Non-anchored functions-->>rApp: 6 «R1» Subscribe data response(subscription ID, data stream endpoint) - end - - loop when data becomes available - alt Pull data delivery method - Note left of Non-anchored functions: [Point to multipoint data stream delivery method] - Non-anchored functions-->>rApp: 7 «R1» Notify data availability (pull delivery details, subscription ID ) - rApp->>Non-anchored functions: 8 «R1» Pull data request - Non-anchored functions-->>rApp: 9 «R1» Pull data response (data payload) - else Push data delivery method - Non-anchored functions-->>rApp: 10 «R1» Push data message (subscription ID, data payload) - else Point to multipoint data stream delivery method - rApp->>Non-anchored functions: 11 «R1» rApp fetches data payload from data stream endpoint - end - end - - Note right of Non-anchored functions: Data management and exposure functions - -``` - -Sequence diagram for 'Subscribe data and delivery of subscribed data use case flow diagram'. It shows interactions between an rApp and 'Non-anchored functions in SMO/Non-RT RIC Framework'. The process involves subscription requests, authorization checks, and data delivery via pull or push methods. A note indicates that step 2 (AuthZ) involves checking authorization in collaboration with SME functions. - -Figure 7.7.4.1-1: Subscribe data and delivery of subscribed data use case flow diagram. - -### 7.7.4.2 Terminate data subscription. - -**Table 7.7.4.2-1: Terminate data subscription.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | rApp terminates the data subscription. | | -| Actors and Roles |
  • – rApp in the role of Data management and exposure services Consumer.
  • – Data management and exposure functions in the role of Data management and exposure services Producer.
| | -| Assumptions | n/a | | -| Preconditions | The rApp has created a data subscription. | | -| Begins when | The rApp determines to terminate the data subscription. | | -| Step 1 (M) | The rApp sends the Unsubscribe data request with rAppId and subscription ID as parameters. | | -| Step 2 (M) | The Data management and exposure functions check for authorization with SME functions whether the rApp is authorized to terminate subscriptions. | | -| Step 3 (M) | The Data management and exposure functions validate the request. | | -| Step 4(M) | The Data management and exposure functions remove the subscription. | | -| Step 5 (M) | The Data management and exposure functions respond to the request. | | -| Ends when | rApp has terminated the data subscription. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-DME-Data subscription-FUN2 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke -box #ivory -participant rApp as rApp -end box -box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue -participant "Data management and\n exposure functions" as DME -end box - -rApp -> DME: <> Unsubscribe data request\n (rAppId, subscription ID) -activate DME -DME --> DME : AuthZ -note right -Check authorization in collaboration -with SME functions -end note - -DME --> DME : Validate request -DME --> DME : Remove subscription -rApp <- DME: <> Unsubscribe data response -deactivate DME -@enduml - -``` - -![Sequence diagram for 'Terminate data subscription use case flow diagram'. It shows an rApp sending an 'Unsubscribe data request' to 'Data management and exposure functions' within the 'Non-RT RIC'. The functions perform 'AuthZ' (checking authorization with SME functions), 'Validate request', and 'Remove subscription' before returning an 'Unsubscribe data response'.](7f7211748473542096717109ebe5a9d6_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant DM as Data management and exposure functions - Note right of DM: Check authorization in collaboration with SME functions - rApp->>DM: 1 <> Unsubscribe data request (rAppId, subscription ID) - DM-->>DM: 2 AuthZ - DM-->>DM: 3 Validate request - DM-->>DM: 4 Remove subscription - DM-->>rApp: 5 <> Unsubscribe data response - -``` - -Sequence diagram for 'Terminate data subscription use case flow diagram'. It shows an rApp sending an 'Unsubscribe data request' to 'Data management and exposure functions' within the 'Non-RT RIC'. The functions perform 'AuthZ' (checking authorization with SME functions), 'Validate request', and 'Remove subscription' before returning an 'Unsubscribe data response'. - -Figure 7.7.4.2-1: Terminate data subscription use case flow diagram. - -### 7.7.4.3 Update a data subscription. - -Table 7.7.4.3-1: Update a data subscription. - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | rApp update a data subscription. | | -| Actors and Roles |
  • rApp in the role of Data management and exposure services Consumer.
  • Data management and exposure functions in the role of Data management and exposure services Producer.
| | -| Assumptions | n/a | | -| Preconditions | The rApp has subscribed to data instance. | | -| Begins when | The rApp determines to update a data subscription. | | -| Step 1 (M) | The rApp sends the Update data subscription request with rAppId, subscription ID and data subscription update information as parameters. | | -| Step 2 (M) | The Data management and exposure functions check for authorization with SME functions whether the rApp is authorized to update a data subscription. | | -| Step 3 (M) | The Data management and exposure functions validate the request. | | -| Step 4(M) | The Data management and exposure functions updates the data subscription. | | -| Step 5 (M) | The Data management and exposure functions respond to the request. | | -| Ends when | rApp has updated the data subscription. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-DME-Data subscription-FUN3 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - -``` - -``` - -box #ivory - participant rApp as rApp -end box -box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "Data management and\n exposure functions" as DME -end box - -rApp -> DME: <> Update data subscription request\n (rAppId, subscription ID\n, data subscription update information) -activate DME -DME --> DME : AuthZ -note right -Check authorization in collaboration -with SME functions -end note - -DME --> DME : Validate request -DME --> DME : Update data subscription -rApp <- DME: <> Update data subscription response -deactivate DME -@enduml - -``` - -![Sequence diagram for 'Update a data subscription' use case. Lifelines: rApp and Non-anchored functions in SMO/Non-RT RIC Framework (DME). The sequence shows: 1. rApp sends request to DME; 2. DME performs AuthZ (with a note about SME collaboration); 3. DME validates request; 4. DME updates subscription; 5. DME returns response to rApp.](694df81535f89c7bfb9ef0df6f130dc0_img.jpg) - -``` - -sequenceDiagram - box ivory rApp - participant rApp - end - box cadetblue Non-anchored functions in SMO/Non-RT RIC Framework - participant DME as Data management and exposure functions - end - rApp->>DME: 1 «R1» Update data subscription request (rAppId, subscription ID, data subscription update information) - activate DME - DME-->>DME: 2 AuthZ - Note right of DME: Check authorization in collaboration with SME functions - DME-->>DME: 3 Validate request - DME-->>DME: 4 Update data subscription - DME-->>rApp: 5 «R1» Update data subscription response - deactivate DME - -``` - -Sequence diagram for 'Update a data subscription' use case. Lifelines: rApp and Non-anchored functions in SMO/Non-RT RIC Framework (DME). The sequence shows: 1. rApp sends request to DME; 2. DME performs AuthZ (with a note about SME collaboration); 3. DME validates request; 4. DME updates subscription; 5. DME returns response to rApp. - -Figure 7.7.4.3-1: Update a data subscription use case flow diagram. - -### 7.7.4.4 Query a data subscription. - -**Table 7.7.4.4-1: Query a data subscription.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | rApp query a data subscription. | | -| Actors and Roles |
  • – rApp in the role of Data management and exposure services Consumer.
  • – Data management and exposure functions in the role of Data management and exposure services Producer.
| | -| Assumptions | n/a | | -| Preconditions | The rApp has subscribed to data instance. | | -| Begins when | The rApp determines to query a data subscription. | | -| Step 1 (M) | The rApp sends the Query data subscription request with rAppId, subscription ID as parameters. | | -| Step 2 (M) | The Data management and exposure functions check for authorization with SME functions whether the rApp is authorized to query a data subscription. | | -| Step 3 (M) | The Data management and exposure functions validate the request. | | -| Step 4 (M) | The Data management and exposure functions respond to the request with the data subscription information. | | -| Ends when | rApp has queried the data subscription. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-DME-Data subscription-FUN4 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke -box #ivory -participant rApp as rApp -end box -box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue -participant "Data management and\n exposure functions" as DME -end box - -rApp -> DME: <> Query data subscription request(rAppId, subscription ID) -activate DME -DME --> DME : AuthZ -note right -Check authorization in collaboration -with SME functions -end note - -DME --> DME : Validate request -rApp <- DME: <> Query data subscription response\n (data subscription information) -deactivate DME -@enduml - -``` - -![Sequence diagram for 'Query a data subscription use case flow'. The diagram shows an rApp on the left interacting with 'Non-anchored functions in SMO/Non-RT RIC Framework' on the right. The interaction consists of four steps: 1. rApp sends a '<> Query data subscription request(rAppId, subscription ID)' to the framework. 2. The framework performs 'AuthZ' (Check authorization in collaboration with SME functions). 3. The framework performs 'Validate request'. 4. The framework sends a '<> Query data subscription response (data subscription information)' back to the rApp. The framework is divided into two 'Data management and exposure functions' blocks.](8ab30dbff406204a68c59ae7c1b77413_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant Framework as Non-anchored functions in SMO/Non-RT RIC Framework - Note right of Framework: Data management and exposure functions - rApp->>Framework: 1 <> Query data subscription request(rAppId, subscription ID) - Note right of Framework: 2 AuthZ Check authorization in collaboration with SME functions - Framework-->>Framework: 3 Validate request - Note right of Framework: Data management and exposure functions - Framework-->>rApp: 4 <> Query data subscription response (data subscription information) - -``` - -Sequence diagram for 'Query a data subscription use case flow'. The diagram shows an rApp on the left interacting with 'Non-anchored functions in SMO/Non-RT RIC Framework' on the right. The interaction consists of four steps: 1. rApp sends a '<> Query data subscription request(rAppId, subscription ID)' to the framework. 2. The framework performs 'AuthZ' (Check authorization in collaboration with SME functions). 3. The framework performs 'Validate request'. 4. The framework sends a '<> Query data subscription response (data subscription information)' back to the rApp. The framework is divided into two 'Data management and exposure functions' blocks. - -Figure 7.7.4.4-1: Query a data subscription use case flow diagram. - -## 7.7.5 Required data. - -The rApp defines the data it needs to consume in data instance information parameter. Data instance information includes data type identifier, scope (i.e., filter on the data), periodicity of collection and additional optional constraints e.g., periodicity of reporting,, etc. - -A subscription ID is a unique identifier per subscription assigned by the Data management and exposure functions. If point to multipoint data stream is used as delivery method, the Data management and exposure functions provide the data stream endpoint. The rApp requests the Data management and exposure functions with rAppId and subscription identifier as parameters to terminate the data subscription. - -In the update data subscription request, the rApp provides the rAppId, subscription ID and data subscription update information. - -In the query data subscription request, the rApp provides the rAppId and subscription identifier. In the query data subscription response, the Data management and exposure functions provide the data subscription information. - -In the notify data availability message, the Data management and exposure functions provide pull delivery details (e.g., a URI) and the subscription identifier. - -In the pull data request, the rApp uses the pull delivery details provided in the notify data availability message to locate the data. - -In the pull data response, the Data management and exposure functions provide a set of data for consumption. - -In the push data message, the Data management and exposure functions provide the subscription identifier and a set of data for consumption. - -When point to multipoint data stream is used, rApp fetches the data from data stream endpoint. - -## 7.8 DME use case 8: Data Producer rApp query the data subscription information for its registered DME types. - -### 7.8.1 Overview - -This use case enables an rApp, as a producer of data for a DME type, to retrieve data subscription information a DME type it has previously registered. This capability ensures that, in the event of a crash or corruption, the rApp can recover or resume those data jobs efficiently. - -### 7.8.2 Background and goal of the use case - -The procedures for Query data subscription information for a registered DME type are defined as part of the Data Management and Exposure services in R1 GAP [1]. - -### 7.8.3 Entities/resources involved in the use case. - -- 1) Data management and exposure functions - - a) support functionality to allow an rApp to query, the data subscription information a DME type it has previously registered, -- 2) rApp - - a) Initiates the procedure to query the data, it has been subscribed to for its registered DME type. - -### 7.8.4 Solutions - -#### 7.8.4.1 Query data subscription info for its registered DME type - -**Table 7.8.4.1-1: Query data subscription info for its registered DME type** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp, as a producer of data, queries the information of the data that has been subscribed to for a DME type it has previously registered | | -| Actors and Roles |
  • – rApp in the role of Data Registration Consumer.
  • – Data Management and Exposure functions in the role of Data Registration Producer.
| | -| Assumptions | The DME type may have a list of subscriptions that it has associated with it. | | -| Preconditions |
  • – The rApp has registered as a producer of data for a DME type.
  • – The rApp is authorized to access the Data Management and Exposure services.
| | -| Begins when | The rApp determines the need to query the subscription information for its DME type. | | -| Step 1 (M) | The rApp requests the Data Management and Exposure functions to retrieve data subscription information for a DME type it has previously registered, by providing its rAppId and DME type registration identifier. | | -| Step 2(M) | The Data Management and Exposure functions check with the SME functions whether the rApp is authorized to query data subscription information for its registered DME type. | | -| Step 3 (M) | The Data Management and Exposure functions queries the data subscription information for the registered DME type. | | -| Step 4 (M) | The Data Management and Exposure functions respond to the rApp with a list of data subscription information associated with the rAppId. | | -| Ends when | The rApp has successfully queried and received data subscription information for its registered DME type. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-DME-Regdatatype-FUN2 | | - -``` -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue -``` - -``` - -participant "Data management and\n exposure functions" as DME -endbox -rApp -> DME :<>Query data subscription information\n for a DME type request (rAppId, \n DME type registration identifier) -activate DME -DME --> DME :AuthZ -note right -Check authorization in collaboration -with SME functions -end note -DME --> DME :Query data subscription information for a\n DME type registration identifier -DME -> rApp :<> Query data subscription information\n for a DME type response\n Array(data subscription information) -deactivate DME -@enduml - -``` - -![Sequence diagram showing the interaction between an rApp and the Non-RT RIC framework for querying data subscription information. The diagram includes four numbered steps: 1. rApp sends a request to the Data management and exposure functions; 2. The functions perform an internal AuthZ check; 3. The functions query the subscription information; 4. The functions return the response to the rApp. A callout box for step 2 indicates a collaboration with SME functions.](719ef0f734259484038b2434e5dc3f24_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant DME as Data management and exposure functions - Note right of DME: Check authorization in collaboration with SME functions - rApp->>DME: 1 «R1»Query data subscription information for a DME type request (rAppId, DME type registration identifier) - activate DME - DME-->>DME: 2 AuthZ - DME-->>DME: 3 Query data subscription information for a DME type registration identifier - DME-->>rApp: 4 «R1» Query data subscription information for a DME type response Array(data subscription information) - deactivate DME - -``` - -Sequence diagram showing the interaction between an rApp and the Non-RT RIC framework for querying data subscription information. The diagram includes four numbered steps: 1. rApp sends a request to the Data management and exposure functions; 2. The functions perform an internal AuthZ check; 3. The functions query the subscription information; 4. The functions return the response to the rApp. A callout box for step 2 indicates a collaboration with SME functions. - -Figure 7.8.4.1-1: Query data subscription info for its registered DME type - -### 7.8.5 Required data. - -For the 'Query data subscription information for a DME type' request, the rApp provides the rAppId and the DME type registration identifier. The Data Management and Exposure functions respond with an array of data subscription information objects that are associated with the rAppId and DME type that the rApp has previously registered. - -## 8 Use cases for RAN OAM-Related Services - -### 8.1 RAN OAM-Related use case 1: Alarm query. - -#### 8.1.1 Overview - -This use case allows an rApp acting as Service Consumer to query alarm information. - -### 8.1.2 Background and goal of the use case - -An rApp acting as Service Consumer can query from the Fault management service Producer information about an individual alarm, a set of alarms matching provided filtering criteria or all active alarms available in the alarm list. - -### 8.1.3 Entities/resources involved in the use case. - -- 1) RAN OAM-related functions as Fault management service Producer. - - a. receive the request to query alarm information, - - b. provide the response of success or failure result to the Query alarm information request. -- 2) rApp - - a. supports functionality to initiate the procedure to query alarm information. - -### 8.1.4 Solutions - -#### 8.1.4.1 Query alarm information - -**Table 8.1.4.1-1: Query alarm information use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use case | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| -| Goal | The rApp obtains alarm information from the Fault management service Producer. | | -| Actors and Roles |
  • – rApp in the role of Service Consumer that queries alarm information.
  • – RAN OAM-related functions in the role of Fault management service Producer that provides alarm information in response to the alarm queries.
| | -| Assumptions | n/a | | -| Preconditions | The rApp is deployed and authorized to query alarm information. | | -| Begins when | The rApp determines the need to query alarm information. | | -| Step 1 (M) | The rApp queries alarm information from the RAN OAM-related functions by providing the rAppId and optional query information that determines the requested result set. | | -| Step 2 (M) | The RAN OAM-related functions check whether the rApp is authorized to query alarm information. | | -| Step 3 (M) | The RAN OAM-related functions validate the query information if it has been provided with the request. | | -| Step 4 (M) | The Ran OAM-related functions respond to the rApp with a success result along with the requested alarm information. | | -| Ends when | The rApp was able to query alarm information. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | n/a | | - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 70 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rapp" as rapp - endbox -``` - -``` - -box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "RAN OAM-related functions" as fmsp -endbox -endbox -rapp -> fmsp: <> Query alarm information request (rAppId, queryInfo) -fmsp --> fmsp: AuthZ -note right -Check authorization in collaboration -with SME functions -end note -fmsp --> fmsp: Validate request -fmsp -> rapp: <> Query alarm information response (alarmInfo) -@enduml - -``` - -![Sequence diagram for Query alarm information use case flow. It shows an rApp sending a request to RAN OAM-related functions, which then perform internal AuthZ and Validate request steps, returning a response. A note indicates the AuthZ step involves checking authorization in collaboration with SME functions.](18bb06865e2dada3656ea3d57f290f7f_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant RAN_OAM as RAN OAM-related functions - Note right of RAN_OAM: Check authorization in collaboration with SME functions - rApp->>RAN_OAM: <> Query alarm information request (rAppId, queryInfo) - RAN_OAM-->>RAN_OAM: AuthZ - RAN_OAM-->>RAN_OAM: Validate request - RAN_OAM-->>rApp: <> Query alarm information response (alarmInfo) - -``` - -Sequence diagram for Query alarm information use case flow. It shows an rApp sending a request to RAN OAM-related functions, which then perform internal AuthZ and Validate request steps, returning a response. A note indicates the AuthZ step involves checking authorization in collaboration with SME functions. - -Figure 8.1.4.1-1: Query alarm information use case flow diagram. - -### 8.1.5 Required data. - -The Query alarm information request contains the rAppId and optional query information. The query information determines the requested alarm information, for instance a single alarm with a particular alarm ID, all alarms in the alarm list or a subset of these alarms that match a set of filtering parameters. - -The Query alarm information response contains the requested alarm information scoped by the query information provided in the request. - -## 8.2 RAN OAM-Related use case 2: Alarm acknowledgement / unacknowledgement. - -### 8.2.1 Overview - -This use case allows an rApp acting as Service Consumer to acknowledge and unacknowledge an alarm with the Fault management service Producer. - -### 8.2.2 Background and goal of the use case - -An rApp acting as Service Consumer can acknowledge and unacknowledge an individual alarm managed by the Fault management service Producer. - -### 8.2.3 Entities/resources involved in the use case. - -- 1) RAN OAM-related functions in the role of Fault management service Producer. - - a. receive the request to change the acknowledgement state of an alarm, - -- b. store the alarm acknowledgement state information, - - c. provide the response of success or failure result to the Change alarm acknowledgement state request. -- 2) rApp -- a. supports functionality to initiate the procedure to change the acknowledgement state of an alarm. - -## 8.2.4 Solutions - -### 8.2.4.1 Change alarm acknowledgement state - -**Table 8.2.4.1-1: Change alarm acknowledgement state use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use case | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| -| Goal | The rApp requests the Service Producer to acknowledge an alarm. | | -| Actors and Roles |
  • – rApp in the role of Service Consumer that requests to acknowledge an alarm.
  • – RAN OAM-related functions in the role of Fault management service Producer that handles the request to acknowledge an alarm.
| | -| Assumptions | The rApp is aware of the alarm ID of the alarm to be acknowledged or unacknowledged. | | -| Preconditions | The rApp is deployed and is authorized to consume the Fault management service. | | -| Begins when | The rApp determines the need to acknowledge an alarm. | | -| Step 1 (M) | The rApp requests the RAN OAM-related functions to change the acknowledgement state of an alarm by providing the rAppId, the alarm ID and the new acknowledgement state (i.e., acknowledged, or unacknowledged). | | -| Step 2 (M) | The RAN OAM-related functions check whether the rApp is authorized to change the acknowledgement state of alarms. | | -| Step 3 (M) | The RAN OAM-related functions validate the alarm ID that has been provided with the request. | | -| Step 4 (M) | The RAN OAM-related functions persist the new state of the alarm identified by the alarm ID to represent the alarm acknowledgement state change. | | -| Step 5 (M) | The RAN OAM-related functions respond to the rApp with a success result. | | -| Ends when | The rApp was able to acknowledge an alarm. | | -| Exceptions | n/a | | -| Post Conditions | The state of the alarm identified by the alarm ID has been changed according to the request. | | -| Traceability | n/a | | - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 70 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rapp" as rapp - endbox - - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "RAN OAM-related functions" as fmsp - endbox -``` - -``` - -endbox -endbox -rapp -> fmsp: <> Change alarm acknowledgement state request\n(rAppId,alarmId, -newAlarmState) -fmsp --> fmsp: AuthZ -note right -Check authorization in collaboration -with SME functions -end note - -fmsp --> fmsp: Validate request -fmsp --> fmsp: Persist new alarm state -fmsp -> rapp: <> Change alarm acknowledgement state response -@enduml - -``` - -![Sequence diagram for Change alarm acknowledgement state use case. It shows an rApp sending a request to RAN OAM-related functions within the Non-RT RIC. The functions perform internal steps: AuthZ (checked with a note about SME collaboration), Validate request, and Persist new alarm state, before returning a response to the rApp.](e7010c66da16316c2935dfbbef5056b3_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant Non-RT RIC as Non-RT RIC - Note right of Non-RT RIC: Non-anchored functions in SMO/Non-RT RIC Framework - Note right of Non-RT RIC: RAN OAM-related functions - - rApp->>Non-RT RIC: <> Change alarm acknowledgement state request (rAppId,alarmId,newAlarmState) - Note right of Non-RT RIC: AuthZ - Note right of Non-RT RIC: Check authorization in collaboration with SME functions - Note right of Non-RT RIC: Validate request - Note right of Non-RT RIC: Persist new alarm state - Non-RT RIC-->>rApp: <> Change alarm acknowledgement state response - -``` - -Sequence diagram for Change alarm acknowledgement state use case. It shows an rApp sending a request to RAN OAM-related functions within the Non-RT RIC. The functions perform internal steps: AuthZ (checked with a note about SME collaboration), Validate request, and Persist new alarm state, before returning a response to the rApp. - -Figure 8.2.4.1-1: Change alarm acknowledgement state use case flow diagram. - -## 8.2.5 Required data. - -The Change alarm acknowledgement state request contains the rAppId, the alarm ID of the alarm to be acknowledged or unacknowledged and the requested new acknowledgement state of the alarm. - -NOTE: If and how the RAN OAM-related functions ensure that the alarm IDs from multiple network elements do not collide is not defined in the present document. - -# 8.3 RAN OAM-Related use case 3: Performance information query. - -## 8.3.1 Overview - -This use case allows an rApp acting as a Service Consumer to query the performance information pertaining to the managed entities. - -## 8.3.2 Background and goal of the use case - -An rApp acting as a Service Consumer can query the performance information pertaining to one or more managed entities from the Performance management Service Producer. - -## 8.3.3 Entities/resources involved in the use case. - -- 1) RAN OAM-related functions as Performance Management Service Producer - -- a. receives the request to query the performance information related to one or more managed entities. -- b. provides the response of success or failure result to the performance information query request. - -2) rApp - -- a. supports functionality to initiate the procedure to query the performance information. - -### 8.3.4 Solutions - -#### 8.3.4.1 Query performance information - -**Table 8.3.4.1-1: Query performance information use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use case | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| -| Goal | The rApp obtains performance information from the Performance management service Producer. | | -| Actors and Roles |
  • – rApp in the role of Service Consumer that queries performance information pertaining to one or more managed entities.
  • – RAN OAM-related functions in the role of Performance Management service Producer that provide the requested performance information.
| | -| Assumptions | n/a | | -| Preconditions | The rApp is deployed and authorized to query performance information. | | -| Begins when | The rApp determines the need to query performance information. | | -| Step 1 (M) | The rApp queries performance information from the RAN OAM-related functions by providing the rAppId, optional query criteria and information about the managed entities, along with the desired performance information, that determines the requested result set. | | -| Step 2 (M) | The RAN OAM-related functions check whether the rApp is authorized to query the performance information. | | -| Step 3 (M) | The RAN OAM-related functions validate the performance information criteria if they were provided with the request. | | -| Step 4 (M) | The RAN OAM-related functions respond to the rApp with a success result along with the desired performance management information. | | -| Ends when | The rApp was able to receive the performance information response. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-OAM-PMservice-FUN1 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 70 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rapp" as rapp - endbox - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "RAN OAM-related functions" as fmsp - endbox -endbox -rapp -> fmsp: <> Query performance information request(rAppId, queryCriteria) -fmsp --> fmsp: AuthZ -note right -Check authorization in collaboration -with SME functions - -``` - -``` - -end note -fmsp --> fmsp: Validate request -fmsp -> rapp: <>Query Performance information response(performanceInformation) -@enduml - -``` - -![Sequence diagram for Figure 8.3.4.1-1: Query performance information use case flow diagram. The diagram shows an rApp on the left and Non-RT RIC on the right. The rApp sends a <> Query performance information request(rAppId, queryCriteria) to the Non-RT RIC. Inside the Non-RT RIC, the request is processed by RAN OAM-related functions. A dashed arrow points to a note box containing 'Check authorization in collaboration with SME functions'. Another dashed arrow points to 'AuthZ', followed by 'Validate request'. Finally, the Non-RT RIC sends a <> Query Performance information response(performanceInformation) back to the rApp.](4806f9f95fff13a30d6523bd6ffeac63_img.jpg) - -Sequence diagram for Figure 8.3.4.1-1: Query performance information use case flow diagram. The diagram shows an rApp on the left and Non-RT RIC on the right. The rApp sends a <> Query performance information request(rAppId, queryCriteria) to the Non-RT RIC. Inside the Non-RT RIC, the request is processed by RAN OAM-related functions. A dashed arrow points to a note box containing 'Check authorization in collaboration with SME functions'. Another dashed arrow points to 'AuthZ', followed by 'Validate request'. Finally, the Non-RT RIC sends a <> Query Performance information response(performanceInformation) back to the rApp. - -Figure 8.3.4.1-1: Query performance information use case flow diagram - -### 8.3.5 Required data. - -The request for querying performance information contains the rAppId, and query criteria (including information about the related managed entities and about the requested performance information). The performance information query response is scoped by the information provided in the request. - -NOTE: The querying of performance information, and how this relates to the Data management and exposure services, is not defined in the present document. - -## 8.4 RAN OAM-Related use case 4: Retrieve configuration schemas. - -### 8.4.1 Overview - -This use case allows an rApp acting as a CM service Consumer to retrieve information pertaining to the configuration schemas of one or more managed entities. - -### 8.4.2 Background and goal of the use case - -An rApp acting as a CM service Consumer can retrieve information pertaining to one or more managed entities from the Configuration management service Producer. - -### 8.4.3 Entities/resources involved in the use case. - -- 1) RAN OAM-related functions as Configuration management service Producer - - a. receives the Get schemas request to retrieve configuration schema information related to one or more managed entities, - - b. provides the response of success or failure result to the Get schema request. -- 2) rApp - - a. supports functionality to initiate Get schemas procedure to retrieve the configuration schema information. - -## 8.4.4 Solutions - -### 8.4.4.1 Retrieve configuration schema information - -**Table 8.4.4.1-1: Retrieve configuration schema information use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use case | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| -| Goal | The rApp obtains configuration schema information from the Configuration management service Producer. | | -| Actors and Roles |
  • – rApp in the role of CM service Consumer that request the configuration schema information pertaining to one or more managed entities.
  • – RAN OAM-related functions in the role of Configuration management service Producer that provide the requested configuration schema information.
| | -| Assumptions | n/a | | -| Preconditions | The rApp is deployed and authorized to request the configuration schema information. | | -| Begins when | The rApp determines the need to request the configuration schema information. | | -| Step 1 (M) | The rApp requests “Get schemas” to obtain the configuration schema information from the RAN OAM-related functions by providing the rAppId, optional query criteria and information about the managed entities, along with the desired configuration schema information, that determines the requested result set. | | -| Step 2 (M) | The RAN OAM-related functions check whether the rApp is authorized to request Get Schemas to retrieve configuration schema information. | | -| Step 3 (M) | The RAN OAM-related functions validate the information provided with Get Schema request, if they were provided with the request. | | -| Step 4 (M) | The RAN OAM-related functions respond to the rApp with a success result along with the desired configuration schema information. | | -| Ends when | The rApp was able to receive the configuration schema information. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-OAM-CmService-FUN1 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 70 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rapp" as rapp - endbox - - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "RAN OAM-related functions" as cmsp - endbox -endbox - -rapp -> cmsp: <> Get schemas request(rAppId, queryCriteria) -cmsp --> cmsp: AuthZ -note right -Check authorization in -Collaboration with SME functions -end note -cmsp --> cmsp: Validate request -cmsp -> rapp: <>Get schemas response (configurationSchema) -@enduml - -``` - -![Sequence diagram for Retrieve configuration schema information use case flow. It shows an rApp sending a Get schemas request to RAN OAM-related functions in the Non-RT RIC. The functions perform authorization (AuthZ) and validation, then return a Get schemas response. A callout indicates that the AuthZ step involves checking authorization in collaboration with SME functions.](2b60ebe01f77d22e53da1fbe73083b01_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant NonRT RIC as Non-RT RIC - Note right of NonRT RIC: Non-anchored functions in SMO/Non-RT RIC Framework - rApp->>NonRT RIC: <> Get schemas request(rAppId, queryCriteria) - Note right of NonRT RIC: RAN OAM-related functions - NonRT RIC-->>NonRT RIC: AuthZ - Note right of NonRT RIC: Check authorization in Collaboration with SME functions - NonRT RIC-->>NonRT RIC: Validate request - NonRT RIC-->>rApp: <>Get schemas response (configurationSchema) - Note right of NonRT RIC: RAN OAM-related functions - -``` - -Sequence diagram for Retrieve configuration schema information use case flow. It shows an rApp sending a Get schemas request to RAN OAM-related functions in the Non-RT RIC. The functions perform authorization (AuthZ) and validation, then return a Get schemas response. A callout indicates that the AuthZ step involves checking authorization in collaboration with SME functions. - -Figure 8.4.4.1-1: Retrieve configuration schema information use case flow diagram. - -### 8.4.5 Required data. - -The Get schemas request for retrieval of configuration schemas information contains the rAppId, and query criteria (including information about the related managed entities and about the requested configuration schemas information). The Get schemas response is scoped by the information provided in the request. - -NOTE: It is up to the design of the authorization mechanism whether the rAppId will be passed as a separate piece of information or will be embedded in or implied by the authorization information. - -## 8.5 RAN OAM-Related use case 5: Read configuration data. - -### 8.5.1 Overview - -This use case allows an rApp acting as a CM service Consumer to retrieve information pertaining to the configuration data of one or more managed entities. - -### 8.5.2 Background and goal of the use case - -An rApp acting as a CM service Consumer can retrieve configuration data pertaining to one or more managed entities from the Configuration management service Producer. - -### 8.5.3 Entities/resources involved in the use case. - -- 1) RAN OAM-related functions as Configuration management service Producer. - - a. receives the request to read configuration data related to one or more managed entities. - - b. provides the response of success or failure result to the read configuration data request. -- 2) rApp - - a. supports functionality to initiate procedure to read configuration data. - -## 8.5.4 Solutions - -### 8.5.4.1 Read configuration data. - -**Table 8.5.4.1-1: Read configuration data use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use case | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| -| Goal | The rApp obtains configuration data from the Configuration management service Producer. | | -| Actors and Roles |
  • – rApp in the role of Service Consumer that request the configuration data pertaining to one or more managed entities.
  • – RAN OAM-related functions in the role of Configuration Management service Producer that provide the requested configuration data information.
| | -| Assumptions | rApp can optionally query configuration schema before requesting to read configuration data. | | -| Preconditions | The rApp is deployed and authorized to request the configuration data. | | -| Begins when | The rApp determines the need to request the configuration data. | | -| Step 1 (M) | The rApp requests "Read configuration" to obtain the configuration data from the RAN OAM-related functions by providing the rAppId, optional query criteria and information about the managed entities, along with information about the desired configuration data, that determines the requested result set. | | -| Step 2 (M) | The RAN OAM-related functions check whether the rApp is authorized to Read configuration data. | | -| Step 3 (M) | The RAN OAM-related functions validate information provided with the Read configuration request. | | -| Step 4 (M) | The RAN OAM-related functions respond to the rApp with a success result along with the desired configuration data. | | -| Ends when | The rApp was able to receive the configuration data. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-OAM-CmService-FUN2 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 70 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rapp" as rapp - endbox - - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "RAN OAM-related functions" as cmSP - endbox -endbox -rapp -> cmSP: <> Read configuration request(rAppId, queryCriteria) -cmSP --> cmSP: AuthZ -note right -Check authorization in Collaboration -with SME functions -end note -cmSP --> cmSP: Validate request -cmSP -> rapp: <> Read configuration response (configurationData) -@enduml - -``` - -![Sequence diagram for Read configuration data use case flow. The diagram shows an rApp on the left and the Non-RT RIC on the right. The rApp sends a Read configuration request (rAppId, queryCriteria) to the RAN OAM-related functions in the Non-RT RIC. The RAN OAM-related functions then call AuthZ, which checks authorization in collaboration with SME functions. After validation, the RAN OAM-related functions send a Read configuration response (configurationData) back to the rApp.](3b11cc18f8ee769d0076c139dbf81ba3_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant Non-RT RIC - Note right of Non-RT RIC: Non-anchored functions in SMO/Non-RT RIC Framework - Note right of Non-RT RIC: RAN OAM-related functions - rApp->>Non-RT RIC: <> Read configuration request(rAppId, queryCriteria) - Note right of Non-RT RIC: AuthZ - Note right of Non-RT RIC: Check authorization in Collaboration with SME functions - Note right of Non-RT RIC: Validate request - Non-RT RIC-->>rApp: <> Read configuration response (configurationData) - Note right of Non-RT RIC: RAN OAM-related functions - -``` - -Sequence diagram for Read configuration data use case flow. The diagram shows an rApp on the left and the Non-RT RIC on the right. The rApp sends a Read configuration request (rAppId, queryCriteria) to the RAN OAM-related functions in the Non-RT RIC. The RAN OAM-related functions then call AuthZ, which checks authorization in collaboration with SME functions. After validation, the RAN OAM-related functions send a Read configuration response (configurationData) back to the rApp. - -Figure 8.5.4.1-1: Read configuration data use case flow diagram. - -## 8.5.5 Required data. - -The read configuration request for reading configuration data contains the rAppId, and query criteria (including information about the related managed entities and about the requested configuration data information). The read configuration response is scoped by the information provided in the request. - -NOTE: It is up to the design of the authorization mechanism whether the rAppId will be passed as a separate piece of information or will be embedded in or implied by the authorization information. - -# 8.6 RAN OAM-Related use case 6: Writing configuration changes. - -## 8.6.1 Overview - -This use case allows an rApp acting as a CM service Consumer to write information pertaining to the configuration changes of one or more managed entities. - -## 8.6.2 Background and goal of the use case - -An rApp acting as a CM service Consumer can write information pertaining to the configuration changes for one or more managed entities through the CM service Producer. - -## 8.6.3 Entities/resources involved in the use case. - -- 1) RAN OAM-related functions as CM service Producer. - - a. receives the Write configuration changes request to write configuration change information related to one or more managed entities. - - b. provides the response of success or failure result to the Service Consumer that initiated the Write configuration request. -- 2) rApp - - a. supports functionality to initiate Write configuration changes request to write the configuration change information. - -## 8.6.4 Solutions - -### 8.6.4.1 Write configuration changes. - -**Table 8.6.4.1-1: Write Configuration changes use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use case | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| -| Goal | The rApp writes configuration change information to the CM service Producer. | | -| Actors and Roles |
  • – rApp in the role of CM service Consumer that requests writing the configuration change information pertaining to one or more managed entities.
  • – RAN OAM-related functions in the role of CM service Producer that initiate provisioning the requested configuration changes.
| | -| Assumptions | rApp optionally query configuration schema before preparing the write configuration change information. | | -| Preconditions | The rApp is deployed and authorized to write the configuration change information. Optionally the rApp is subscribed to receive information related to write configuration change status from RAN OAM-related function through Notification or polling. | | -| Begins when | The rApp determines the need to write the configuration change information. | | -| Step 1 (M) | The rApp sends a Write configuration changes request to write the configuration change information to the RAN OAM-related functions by providing the rAppId, along with the desired configuration changes information for one or more managed entities. | | -| Step 2 (M) | The RAN OAM-related functions check whether the rApp is authorized to initiate the Write configuration changes request. | | -| Step 3 (M) | The RAN OAM-related functions validate the information provided in the Write configuration changes request. | | -| Step 4 (M) | The RAN OAM-related functions create a Write configuration job from the information provided in the Write configuration changes request. | | -| Step 5 (M) | RAN OAM-related functions respond to the rApp with information about the job created such as job identifier. The rApp can use this information for querying or receiving notification about the status / result of the requested configuration change. | | -| Ends when | The rApp was able to receive the Write configuration response. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-OAM-CmService-FUN3. | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 70 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -Autonumber - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rApp" as rapp - endbox - - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "RAN OAM-related functions" as cmsp - endbox -endbox - -rapp -> cmsp: <> Write configuration changes request\n(rAppId, configuration changes information) - -``` - -``` - -cmsp --> cmsp: AuthZ -note right -Check authorization in -Collaboration with SME functions -end note -cmsp --> cmsp: Validate request -cmsp --> cmsp: Create job - -cmsp -> rapp: <> Write configuration changes response\n (Job information) -@enduml - -``` - -![Sequence diagram for 'Write configuration changes use case flow diagram'. It shows an rApp on the left and Non-RT RIC on the right. The rApp sends a 'Write configuration changes request' to the Non-RT RIC. Inside the Non-RT RIC, the request is processed by 'RAN OAM-related functions' through steps: 2 AuthZ (with a note 'Check authorization in Collaboration with SME functions'), 3 Validate request, and 4 Create job. Finally, the rApp receives a 'Write configuration changes response (Job information)'.](f61d0925551545b5938b3a4d1bbf63c3_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant Non-RT RIC - Note right of Non-RT RIC: Non-anchored functions in SMO/Non-RT RIC Framework - Note right of Non-RT RIC: RAN OAM-related functions - rApp->>Non-RT RIC: 1 «R1» Write configuration changes request (rAppId, configuration changes information) - Note right of Non-RT RIC: 2 AuthZ - Note right of Non-RT RIC: Check authorization in Collaboration with SME functions - Note right of Non-RT RIC: 3 Validate request - Note right of Non-RT RIC: 4 Create job - Non-RT RIC-->>rApp: 5 «R1» Write configuration changes response (Job information) - -``` - -Sequence diagram for 'Write configuration changes use case flow diagram'. It shows an rApp on the left and Non-RT RIC on the right. The rApp sends a 'Write configuration changes request' to the Non-RT RIC. Inside the Non-RT RIC, the request is processed by 'RAN OAM-related functions' through steps: 2 AuthZ (with a note 'Check authorization in Collaboration with SME functions'), 3 Validate request, and 4 Create job. Finally, the rApp receives a 'Write configuration changes response (Job information)'. - -Figure 8.6.4.1-1: Write configuration changes use case flow diagram. - -### 8.6.5 Required data. - -The request for writing configuration changes information contains the rAppId and write configuration information for one or more managed entities (e.g., list of attributes and desired values). - -The RAN OAM-related functions respond to the rApp with configuration job information created, e.g., job identifier. The rApp can use this job information for querying or receiving notifications about the status / result of the requested configuration change which includes e.g.: - -- a success result if all the requested configuration changes were written in the related managed entities or -- a partial success result if some but not all requested configuration changes were written in the related mentioned managed entities, optionally with further information about the reason of the errors or -- a failure result if one of the requested configuration changes were written in the related managed entities, optionally with further information about the reason of the errors. - -## 9 Use cases for O2-Related Services - -NOTE: Use cases for O2-Related services are not defined in the present document. - -## 10 Use cases for A1-Related Services - -10.1 Void - -10.2 Void - -10.3 A1-Related use case 1: Query A1 policy type identifiers - -### 10.3.1 Overview - -This use case provides the description and requirements for querying the A1 policy type identifiers. - -### 10.3.2 Background and goal of the use case - -Query A1 policy type identifiers procedure is defined as part of A1 policy management service in R1GAP [1]. - -### 10.3.3 Entities/resources involved in the use case. - -- 1) A1 Policy functions - - a. support functionality to allow rApps to query the A1 policy type identifiers. -- 2) rApp - - a. initiates the Query A1 policy type identifiers procedure. - -## 10.3.4 Solutions - -### 10.3.4.1 Query A1 policy type identifiers. - -**Table 10.3.4.1-1: Query A1 policy type identifiers** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp retrieves the list of identifiers for all the available A1 policy types. | | -| Actors and Roles |
  • – rApp in the role of A1 policy management service Consumer.
  • – A1 policy functions in the role of A1 policy management service Producer.
| | -| Assumptions | rApp is authorized to consume the A1 policy management service. | | -| Preconditions | n/a | | -| Begins when | The rApp determines the need to query the identifiers for all the available A1 policy types. | | -| Step 1 (M) | The rApp queries the available A1 policy type identifiers, providing the rAppId and optional selection criteria (Near-RT RIC identifier and/or typename (see 3 in A1AP [5], clause 6.2.3.1.)). | | -| Step 2 (M) | The A1 policy management functions validate if the rApp is authorized to query A1 policy type identifiers. | | -| Step 3 (M) | The A1 policy management functions respond with the list of identifiers for all the available A1 policy types that matches with the query criteria. Further, the response includes for each A1 policy type identifier a list of Near-RT RIC identifiers of those Near-RT RICs that support the related A1 policy type. | | -| Ends when | The rApp has the identifiers of all the available A1 policy types. | | -| Exceptions | n/a | | -| Post Conditions | The rApp has the identifiers of all the available A1 policy types. | | -| Traceability | REQ-R1-A1P- FUN3. | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram' -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "A1 policy functions " as A1P - endbox - rApp -> A1P : <> Query A1 policy type identifiers request (rAppId) - activate A1P - A1P --> A1P : AuthZ - note right - Check authorization in collaboration - with SME functions - end note - A1P -> rApp : <> Query A1 policy type identifiers response (list of A1 policy type identifiers) - Deactivate A1P -@enduml - -``` - -![Sequence diagram for 'Query A1 policy type identifiers' use case. It shows an rApp sending a request to A1 policy functions, which then check authorization with SME functions and return a response.](8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant A1PF as A1 policy functions - Note right of A1PF: Check authorization in collaboration with SME functions - - Note over rApp, A1PF: Non-RT RIC - Note over A1PF: Non-anchored functions in SMO/Non-RT RIC Framework - - rApp->>A1PF: 1 «R1» Query A1 policy type identifiers request (rAppId) - A1PF->>A1PF: 2 AuthZ - A1PF-->>rApp: 3 «R1» Query A1 policy type identifiers response (list of A1 policy type identifiers) - -``` - -Sequence diagram for 'Query A1 policy type identifiers' use case. It shows an rApp sending a request to A1 policy functions, which then check authorization with SME functions and return a response. - -Figure 10.3.4.1-1: Query A1 policy type identifiers use case flow diagram. - -### 10.3.5 Required data - -For querying the A1 policy type identifiers, the rApp sends a query request to the A1 policy functions and optionally provides a Near-RT RIC identifier and/or a typename (see in A1AP [5], clause 6.2.3.1.3) as a selection criterion. - -If the rApp queries with no selection criteria, the A1 policy functions respond with a list of A1 policy type identifiers. Further, the response includes for each A1 policy type identifier a list of Near-RT RIC identifiers of those Near-RT RICs that support the related A1 policy type. - -If the rApp queries with selection criteria, the A1 policy functions respond with a list of A1 policy type identifiers which match with the query criteria. Further, the response includes for each A1 policy type identifier a list of Near-RT RIC identifiers of those Near-RT RICs that support the related A1 policy type. - -## 10.4 A1-Related use case 2: Query an A1 policy type - -### 10.4.1 Overview - -This use case provides the description and requirements for querying the information of an A1 policy type. - -### 10.4.2 Background and goal of the use case - -Query A1 policy type procedure is defined as part of A1 policy management service in R1GAP [1]. - -### 10.4.3 Entities/resources involved in the use case. - -- 3) A1 Policy functions - - a. support functionality to allow rApps to query the information of an A1 policy type. -- 4) rApp - - a. initiates the Query A1 policy type procedure. - -## 10.4.4 Solutions - -### 10.4.4.1 Query A1 policy type. - -**Table 10.4.4.1-1: Query A1 policy type** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp retrieves information about A1 policy type. | | -| Actors and Roles |
  • – rApp in the role of A1 policy management service Consumer.
  • – A1 policy functions in the role of A1 policy management service Producer.
| | -| Assumptions | rApp is authorized to consume the A1 policy management service. | | -| Preconditions | rApp is aware of the A1 policy type identifier. | | -| Begins when | The rApp determines the need to query the information of an A1 policy type. | | -| Step 1 (M) | The rApp queries the information of an A1 policy type with the A1 policy functions by providing rAppId and an A1 policy type identifier. | | -| Step 2 (M) | The A1 policy functions validate if the rApp is authorized to access the information of an A1 policy type. | | -| Step 3 (M) | The A1 policy functions retrieve the policy type information. | | -| Step 4 (M) | The A1 policy functions respond with the requested A1 policy type information. | | -| Ends when | The rApp have received the information about the requested A1 policy type. | | -| Exceptions | n/a | | -| Post Conditions | The rApp have the information about the requested A1 policy type. | | -| Traceability | REQ-R1-A1P- FUN1. | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram' -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "A1 policy functions " as A1P - endbox -rApp -> A1P : <> Query A1 policy type request (rAppId, A1 policy type identifier) -activate A1P -A1P --> A1P : AuthZ -note right -Check authorization in collaboration -with SME functions -end note -A1P --> A1P: retrieve policy type information -A1P -> rApp : <> Query A1 policy type response (A1 policy type information) -Deactivate A1P -@enduml - -``` - -![Sequence diagram for Query A1 policy type use case. It shows an rApp sending a request to A1 policy functions, which then perform authorization and data retrieval before returning a response. A callout box indicates that step 2 involves checking authorization in collaboration with SME functions.](b3d488012fdceacab867cf24c5efef05_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant A1_policy_functions as A1 policy functions - Note right of A1_policy_functions: Check authorization in collaboration with SME functions - rApp->>A1_policy_functions: 1 «R1» Query A1 policy type request (rAppId, A1 policy type identifier) - A1_policy_functions-->>A1_policy_functions: 2 AuthZ - A1_policy_functions-->>A1_policy_functions: 3 retrieve policy type information - A1_policy_functions-->>rApp: 4 «R1» Query A1 policy type response (A1 policy type information) - -``` - -Sequence diagram for Query A1 policy type use case. It shows an rApp sending a request to A1 policy functions, which then perform authorization and data retrieval before returning a response. A callout box indicates that step 2 involves checking authorization in collaboration with SME functions. - -Figure 10.4.4.1-1: Query A1 policy type use case flow diagram - -### 10.4.5 Required data - -For querying an A1 policy type, the rApp provides the rAppId and an A1 policy type identifier. The A1 policy functions respond with the information about the A1 policy type. - -## 10.5 A1-Related use case 3: Query A1 policy identifiers - -### 10.5.1 Overview - -This use case provides the description and requirements for querying the A1 policy identifiers. - -### 10.5.2 Background and goal of the use case - -Query A1 policy identifiers procedure is defined as part of A1 policy management service in RIGAP [1]. - -### 10.5.3 Entities/resources involved in the use case. - -- 1) A1 Policy functions - - a. support functionality to allow rApps to query the A1 policy identifiers. -- 2) rApp - - a. initiates the Query A1 policy identifiers procedure. - -## 10.5.4 Solutions - -### 10.5.4.1 Query A1 policy identifiers. - -**Table 10.5.4.1-1: Query A1 policy identifiers.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp retrieves the existing A1 policy identifiers. | | -| Actors and Roles |
  • – rApp in the role of A1 policy management service Consumer.
  • – A1 policy functions in the role of A1 policy management service Producer.
| | -| Assumptions | rApp is authorized to consume the A1 policy management service. | | -| Preconditions | n/a | | -| Begins when | The rApp determines the need to query the A1 policy identifiers. | | -| Step 1 (M) | The rApp queries the A1 policy identifiers with the A1 policy functions and may provide an A1 policy type identifier and/or a Near RT RIC identifier. | | -| Step 2 (M) | The A1 policy functions validate if the rApp is authorized to query A1 policy identifiers. | | -| Step 3 (M) | The A1 policy functions respond with the list of A1 policy identifiers that matches with the query criteria. | | -| Ends when | The rApp has the list of A1 policy identifiers. | | -| Exceptions | n/a | | -| Post Conditions | The rApp has the list of A1 policy identifiers. | | -| Traceability | REQ-R1-A1P- FUN2. | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram' -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "A1 policy functions " as A1P - endbox -rApp -> A1P : <> Query A1 policy identifiers request (rAppId) -activate A1P -A1P --> A1P : AuthZ -note right -Check authorization in collaboration -with SME functions -end note -A1P -> rApp : <> Query A1 policy identifiers response (list of A1 policy identifiers) -Deactivate A1P -@enduml - -``` - -![Sequence diagram for 'Query A1 policy identifiers' use case. It shows an rApp sending a request to A1 policy functions, which then call an AuthZ function to check authorization with SME functions, and finally return a response to the rApp.](d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant NonRT RIC as Non-RT RIC - Note right of NonRT RIC: Non-anchored functions in SMO/Non-RT RIC Framework - rApp->>NonRT RIC: 1 «R1» Query A1 policy identifiers request (rAppId) - NonRT RIC->>NonRT RIC: 2 AuthZ - Note right of NonRT RIC: Check authorization in collaboration with SME functions - NonRT RIC-->>rApp: 3 «R1» Query A1 policy identifiers response (list of A1 policy identifiers) - -``` - -Sequence diagram for 'Query A1 policy identifiers' use case. It shows an rApp sending a request to A1 policy functions, which then call an AuthZ function to check authorization with SME functions, and finally return a response to the rApp. - -Figure 10.5.4.1-1: Query A1 policy identifiers use case flow diagram. - -## 10.5.5 Required data - -For querying the A1 policy identifiers, the rApp optionally provides an A1 policy type identifier and/or a Near RT RIC identifier as a query parameter. The A1 policy functions respond with the list of A1 policy identifiers. - -# 10.6 A1-related use case 4: Create, Query, Update and Delete an A1 policy - -## 10.6.1 Overview - -This use case enables rApps to create an A1 policy, query an A1 policy, update an A1 policy, and delete an A1 policy. - -## 10.6.2 Background and goal of the use case - -Create A1 policy, Query A1 policy, Update A1 policy, and Delete A1 policy procedures are defined as part of A1 policy management service in R1GAP [1]. - -## 10.6.3 Entities/resources involved in the use case. - -- 3) A1 policy functions - - a. support functionality to allow rApps to request creating7., querying, updating and deleting an A1 policy. -- 4) rApp - - a. initiates the procedures for creating an A1 policy, querying an A1 policy, updating an A1 policy, and deleting an A1 policy. - -## 10.6.4 Solutions - -### 10.6.4.1 Create a single A1 policy in an identified Near-RT RIC - -**Table 10.6.4.1-1: Create a single A1 policy in an identified Near-RT RIC.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------| -| Goal | The rApp initiates creation of an A1 policy in an identified Near-RT RIC. | | -| Actors and Roles |
  • – rApp in the role of the A1 policy management service Consumer.
  • – A1 policy functions in the role of the A1 policy management service Producer.
| | -| Assumptions | rApp is authorized to consume the A1 policy management service. | | -| Preconditions | The rApp is aware about the A1 policy type. | | -| Begins when | The rApp determines to create a new A1 policy. | | -| Step 1 (M) | The rApp requests the A1 policy functions to create a new A1 policy of certain type by providing a policy type identifier, policy information, rApp identifier, and a Near-RT RIC identifier. | | -| Step 2 (M) | The A1 policy functions validate if the rApp is authorized to create A1 policies. | | -| Step 3 (M) | The A1 policy functions generate the A1 policy identifier. | | -| Step 4 (M) | The A1 policy functions create a single A1 policy in the Near-RT RIC corresponding to the given Near-RT RIC identifier. | See A1UCR [6], clause 6.3 | -| Step 5 (M) | The A1 policy functions store the mapping of A1 policy identifier to the Near-RT RIC identifier. | | -| Step 6(M) | The A1 policy functions respond to rApp with the A1 policy identifier of the created A1 policy. | | -| Ends when | The rApp has created a new A1 policy. | | -| Exceptions | n/a | | -| Post Conditions | An A1 policy exists and the rApp will be able to query, update and delete the A1 policy. | | -| Traceability | REQ-R1-A1P- FUN9. | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram' -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "A1 policy functions " as A1P - endbox - rApp -> A1P :1 <> Create A1 policy request\n (policy type identifier, policy -information, Near-RT RIC identifier, rAppId) - activate A1P - A1P --> A1P :2 AuthZ - note right - Check authorization in collaboration - with SME functions - end note - A1P --> A1P : 3 Generate A1 policy identifier - ref over A1P - 4 create single policy(see A1 UCR clause 6.3) - end ref - A1P --> A1P :5 Store A1 policy identifier - A1P -> rApp : 6 <> Create A1 policy response (policy identifier) - Deactivate A1P -@enduml - -``` - -![Sequence diagram showing the interaction between an rApp and Non-RT RIC for creating an A1 policy. The diagram includes steps: 1. rApp sends 'Create A1 policy request' to A1 policy functions; 2. A1 policy functions perform 'AuthZ' (checked with SME functions); 3. A1 policy functions 'Generate A1 policy identifier'; 4. A1 policy functions 'create single policy' (ref); 5. A1 policy functions 'Store A1 policy identifier'; 6. A1 policy functions send 'Create A1 policy response' back to rApp.](592f13acca3e6d5152dd4489f030d004_img.jpg) - -``` -sequenceDiagram - participant rApp - participant NonRT RIC as Non-RT RIC - Note right of NonRT RIC: Non-anchored functions in SMO/Non-RT RIC Framework - - rApp->>NonRT RIC: 1 «R1» Create A1 policy request (policy type identifier, policy information, Near-RT RIC identifier, rAppId) - NonRT RIC-->>NonRT RIC: 2 AuthZ - Note right of NonRT RIC: Check authorization in collaboration with SME functions - NonRT RIC-->>NonRT RIC: 3 Generate A1 policy identifier - Note right of NonRT RIC: ref create single policy(see A1 UCR clause 6.3) - NonRT RIC-->>NonRT RIC: 4 create single policy(see A1 UCR clause 6.3) - NonRT RIC-->>NonRT RIC: 5 Store A1 policy identifier - NonRT RIC-->>rApp: 6 «R1» Create A1 policy response (policy identifier) -``` - -Sequence diagram showing the interaction between an rApp and Non-RT RIC for creating an A1 policy. The diagram includes steps: 1. rApp sends 'Create A1 policy request' to A1 policy functions; 2. A1 policy functions perform 'AuthZ' (checked with SME functions); 3. A1 policy functions 'Generate A1 policy identifier'; 4. A1 policy functions 'create single policy' (ref); 5. A1 policy functions 'Store A1 policy identifier'; 6. A1 policy functions send 'Create A1 policy response' back to rApp. - -Figure 10.6.4.1-1: Create a single A1 policy in an identified Near-RT RIC flow diagram. - -### 10.6.4.2 Query an A1 policy - -**Table 10.6.4.2-1: Query an A1 policy** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp queries an existing A1 policy. | | -| Actors and Roles |
  • – rApp in the role of an A1 policy management service Consumer.
  • – A1 policy functions in the role of an A1 policy management service Producer.
| | -| Assumptions | The rApp is authorized to consume the A1 policy management service. | | -| Preconditions |
  • – The rApp is aware about the A1 policy identifier of the A1 policy that it wants to query.
  • – A1 policy functions are aware of the Near-RT RIC identifier corresponding to this A1 policy identifier so that it can query the A1 policy at the relevant Near-RT RIC instance.
| | -| Begins when | The rApp determines to query an existing A1 policy. | | -| Step 1 (M) | The rApp requests the A1 policy functions to query an existing A1 policy by providing the A1 policy identifier, and its rApp identifier. | | -| Step 2 (M) | The A1 policy functions validate if the rApp is authorized to query an A1 policy. | | -| Step 3 (M) | A1 policy functions respond with the result of the A1 policy query including policy information. | See NOTE | -| Ends when | The rApp has the A1 policy information. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-A1P- FUN9. | | - -NOTE: The A1 policy functions may use A1UCR [6], 6.4.3.2 Query single policy to retrieve the A1 policy information from the relevant Near-RT RIC whenever an rApp queries an A1 policy. It may also choose to respond to the rApp query with the latest policy information previously received from the relevant Near-RT RIC. - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box "Non-RT RIC FWK/SMO FWK" #cadetBlue - participant "A1 policy functions " as A1P - endbox -rApp -> A1P :<>Query A1 policy request (A1 policy identifier, \n rAppId) -activate A1P - A1P --> A1P : AuthZ - note right - Check authorization in collaboration - with SME functions - end note - A1P -> rApp :<>Query A1 policy response (policy information) - Deactivate A1P -@enduml - -``` - -![Sequence diagram for Query A1 policy use case flow. It shows an rApp sending a request to A1 policy functions, which then perform an authorization check with SME functions before returning a response.](140bd031d724324269168296afd1e04d_img.jpg) - -The diagram illustrates the interaction for the 'Query A1 policy' use case within the Non-RT RIC. It features two lifelines: 'rApp' on the left and 'Non-RT RIC FWK/SMO FWK' on the right. The 'Non-RT RIC FWK/SMO FWK' lifeline contains two 'A1 policy functions' blocks. The sequence of messages is as follows: 1. The 'rApp' sends an '«R1»Query A1 policy request (A1 policy identifier, rApp Id)' to the top 'A1 policy functions' block. 2. A dashed arrow labeled '2 AuthZ' points from the top 'A1 policy functions' block to a note box containing the text 'Check authorization in collaboration with SME functions'. 3. The 'rApp' receives an '«R1»Query A1 policy response (policy information)' from the bottom 'A1 policy functions' block. - -Sequence diagram for Query A1 policy use case flow. It shows an rApp sending a request to A1 policy functions, which then perform an authorization check with SME functions before returning a response. - -Figure 10.6.4.2-1: Query A1 policy use case flow diagram. - -### 10.6.4.3 Update an A1 policy - -**Table 10.6.4.3-1: Update an A1 policy.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| -| Goal | The rApp updates an existing A1 policy. | | -| Actors and Roles |
  • – rApp in the role of an A1 policy management service Consumer.
  • – A1 policy functions in the role of an A1 policy management service Producer.
| | -| Assumptions | The rApp is authorized to consume the A1 policy management service. | | -| Preconditions |
  • – The rApp is aware of the identifier of the A1 policy that it wants to update.
  • – A1 policy functions are aware of the existing policy to be updated was created by the rApp.
  • – A1 policy functions are aware of the Near-RT RIC identifier corresponding to this A1 policy identifier so that it can update the A1 policy at the relevant Near-RT RIC instance.
| | -| Begins when | The rApp determines to update an existing A1 policy. | | -| Step 1 (M) | The rApp requests the A1 policy functions to update an existing A1 policy by providing the A1 policy identifier, policy update information, rApp identifier. | | -| Step 2 (M) | The A1 policy functions validate if the rApp is authorized to update an A1 policy. | | -| Step 3 (M) | The A1 policy functions update a single A1 policy in the Near-RT RIC. | See A1UCR [6] clause 6.5 | -| Step 4 (M) | The A1 policy functions respond with the result of the A1 policy update. | | -| Ends when | The rApp has updated the A1 policy. | | -| Exceptions | n/a | | -| Post Conditions | The content of the A1 policy has changed. | | -| Traceability | REQ-R1-A1P- FUN9. | | - -``` -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box "Non-RT RIC FWK/SMO FWK" #cadetBlue - participant "A1 policy functions " as A1P - endbox -rApp -> A1P :<>Update A1 policy request (A1 policy identifier, \n policy information, rApp Id) -activate A1P - A1P --> A1P : AuthZ - note right - Check authorization in collaboration - with SME functions - end note -ref over A1P - 3 Update single policy(see A1 UCR clause 6.5) -end ref -autonumber 4 -A1P -> rApp :<>Update A1 policy response -deactivate A1P -@enduml -``` - -![Sequence diagram for Update A1 policy use case flow. Lifelines: rApp and Non-RT RIC FWK/SMO FWK (containing A1 policy functions). The sequence starts with rApp sending an 'Update A1 policy request' (R1) to the A1 policy functions. The A1 policy functions then perform an 'AuthZ' check, with a note indicating they 'Check authorization in collaboration with SME functions'. Next, a 'ref' block labeled '3 Update single policy(see A1 UCR clause 6.5)' occurs. Finally, the A1 policy functions send an 'Update A1 policy response' (R1) back to the rApp.](cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant Non-RT RIC FWK/SMO FWK as Non-RT RIC FWK/SMO FWK (A1 policy functions) - Note right of Non-RT RIC FWK/SMO FWK: Check authorization in collaboration with SME functions - rApp->>Non-RT RIC FWK/SMO FWK: 1 <>Update A1 policy request (A1 policy identifier, policy information, rApp Id) - Non-RT RIC FWK/SMO FWK-->>Non-RT RIC FWK/SMO FWK: 2 AuthZ - Note right of Non-RT RIC FWK/SMO FWK: ref 3 Update single policy(see A1 UCR clause 6.5) - Non-RT RIC FWK/SMO FWK-->>rApp: 4 <>Update A1 policy response - -``` - -Sequence diagram for Update A1 policy use case flow. Lifelines: rApp and Non-RT RIC FWK/SMO FWK (containing A1 policy functions). The sequence starts with rApp sending an 'Update A1 policy request' (R1) to the A1 policy functions. The A1 policy functions then perform an 'AuthZ' check, with a note indicating they 'Check authorization in collaboration with SME functions'. Next, a 'ref' block labeled '3 Update single policy(see A1 UCR clause 6.5)' occurs. Finally, the A1 policy functions send an 'Update A1 policy response' (R1) back to the rApp. - -Figure 10.6.4.3-2: Update A1 policy use case flow diagram. - -### 10.6.4.4 Delete an A1 policy - -Table 10.6.4.4-1: Delete an A1 policy. - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| -| Goal | The rApp deletes an existing A1 policy. | | -| Actors and Roles |
  • rApp in the role of an A1 policy management service Consumer.
  • A1 policy functions in the role of an A1 policy management service Producer.
| | -| Assumptions | The rApp is authorized to consume A1 policy management service. | | -| Preconditions |
  • The rApp is aware of the identifier of the A1 policy that it wants to delete.
  • A1 policy functions are aware of the existing policy to be deleted was created by the rApp.
  • A1 policy functions are aware of the Near-RT RIC identifier corresponding to this A1 policy identifier so that it can delete the A1 policy at the relevant Near-RT RIC instance.
| | -| Begins when | The rApp determines to delete an existing A1 policy. | | -| Step 1 (M) | The rApp requests the A1 policy functions to delete an existing A1 policy by providing the A1 policy identifier and rApp identifier. | | -| Step 2 (M) | The A1 policy functions validate if the rApp is authorized to delete an A1 policy. | | -| Step 3 (M) | The A1 policy functions delete a single A1 policy in the Near-RT RIC. | See A1UCR [6] clause 6.6 | -| Step 4(M) | The A1 policy functions respond with the result of A1 policy delete. | | -| Ends when | The rApp has deleted an A1 policy. | | -| Exceptions | n/a | | -| Post Conditions | The A1 policy has ceased to exist. | | -| Traceability | REQ-R1-A1P- FUN9. | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 - -``` - -``` - -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box "Non-RT RIC FWK/SMO FWK" #cadetBlue - participant "A1 policy functions " as A1P - endbox -rApp -> A1P :<>Delete A1 policy request (A1 policy identifier, \n rAppId) -activate A1P - A1P --> A1P : AuthZ - note right - Check authorization in collaboration - with SME functions - end note -ref over A1P - 3 Delete single policy(see A1 UCR clause 6.6) -end ref -autonumber 4 -A1P -> rApp :<>Delete A1 policy response -Deactivate A1P -@enduml - -``` - -![Sequence diagram for Delete A1 policy use case flow. Lifelines: rApp and Non-RT RIC FWK/SMO FWK (containing A1 policy functions). The sequence shows: 1. rApp sends a Delete A1 policy request to A1 policy functions. 2. A1P performs an internal AuthZ check (note: Check authorization in collaboration with SME functions). 3. Inside a 'ref' block, A1P calls 'Delete single policy' (see A1 UCR clause 6.6). 4. A1P returns the Delete A1 policy response to rApp.](6a993bfdf2e00cfad01c4d2188a75d86_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant A1P as A1 policy functions - Note right of A1P: Check authorization in collaboration with SME functions - rApp->>A1P: 1 <>Delete A1 policy request (A1 policy identifier, rAppId) - activate A1P - A1P-->>A1P: 2 AuthZ - Note right of A1P: Check authorization in collaboration with SME functions - Note right of A1P: 3 Delete single policy(see A1 UCR clause 6.6) - A1P-->>rApp: 4 <>Delete A1 policy response - deactivate A1P - -``` - -Sequence diagram for Delete A1 policy use case flow. Lifelines: rApp and Non-RT RIC FWK/SMO FWK (containing A1 policy functions). The sequence shows: 1. rApp sends a Delete A1 policy request to A1 policy functions. 2. A1P performs an internal AuthZ check (note: Check authorization in collaboration with SME functions). 3. Inside a 'ref' block, A1P calls 'Delete single policy' (see A1 UCR clause 6.6). 4. A1P returns the Delete A1 policy response to rApp. - -Figure 10.6.4.4-1: Delete A1 policy use case flow diagram. - -### 10.6.5 Required data - -For creating an A1 policy of a certain type in a Near-RT RIC, the rApp provides an A1 policy type identifier, A1 policy information, its rApp identifier (rAppId) and, a Near-RT RIC identifier. The A1 policy functions respond with the A1 policy identifier of the created policy. - -For querying an A1 policy, the rApp provides an A1 policy identifier, and its rApp identifier (rAppId). The A1 policy functions respond with A1 policy information. - -For updating an A1 policy, the rApp provides an A1 policy identifier, A1 policy updated information, and its rApp identifier (rAppId). - -For deleting an A1 policy, the rApp provides an A1 policy identifier and its rApp identifier (rAppId). - -## 10.7 A1-Related use case 5: Query the status of an A1 policy - -### 10.7.1 Overview - -This use case provides the description and requirements for querying the status of an A1 policy status. - -### 10.7.2 Background and goal of the use case - -Query A1 policy status procedure is defined as part of A1 policy management service in R1GAP [1]. - -### 10.7.3 Entities/resources involved in the use case. - -- 1) A1 policy functions - - a. support functionality to allow rApps to query the status of an A1 policy. -- 2) rApp - - a. initiates the procedure for querying status of an A1 policy. - -### 10.7.4 Solutions - -#### 10.7.4.1 Query the status of an A1 policy. - -**Table 10.7.4.1-1: Query status of A1 policy.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp is informed about the status of an A1 policy. | | -| Actors and Roles |
  • – rApp in the role of A1 policy management service Consumer.
  • – A1 policy functions in the role of A1 policy management service Producer.
| | -| Assumptions | rApp is authorized to use A1 policy management service. | | -| Preconditions | rApp is aware of the identifier of the A1 policy that it wants to get the status for. | | -| Begins when | The rApp determines the need to query the status of an A1 policy. | | -| Step 1 (M) | The rApp queries the status of an A1 policy with A1 policy functions by providing an rAppId and A1 policy identifier. | | -| Step 2 (M) | The A1 policy functions validate if the rApp is authorized to query the status of an A1 policy. | | -| Step 3 (M) | The A1 policy functions respond with the status of the corresponding A1 policy. | See NOTE | -| Ends when | The rApp has received the status of an A1 policy. | | -| Exceptions | n/a | | -| Post Conditions | The rApp has the status of an A1 policy. | | -| Traceability | REQ-R1-A1P- FUN5. | | - -NOTE: The A1 policy functions may use A1UCR [6], clause 6.7.3.1 Query policy status, or A1UCR [6], 6.7.3.2 Notify policy status change to respond with the latest status of the corresponding A1 policy - -``` -@startuml -'https://plantuml.com/sequence-diagram' -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke -box #ivory -``` - -``` - -participant rApp as rApp -endbox -box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "A1 policy functions" as A1P -endbox -rApp -> A1P: <>Query A1 policy status request(rAppId,A1 policy identifier) -activate A1P -A1P --> A1P :AuthZ -note right - Check authorization in collaboration - with SME functions -end note -A1P -> rApp : <>Query A1 policy status response -Deactivate A1P -@enduml - -``` - -![Sequence diagram for Query status of A1 policy use case flow. The diagram shows an rApp on the left and a Non-RT RIC box on the right. Inside the Non-RT RIC box is a 'Non-anchored functions in SMO/Non-RT RIC Framework' box containing 'A1 policy functions'. The sequence is: 1. rApp sends a 'Query A1 policy status request' to the A1 policy functions. 2. The A1 policy functions send an 'AuthZ' message to themselves, with a note 'Check authorization in collaboration with SME functions'. 3. The A1 policy functions send a 'Query A1 policy status response' back to the rApp.](e18841eb4a995df8354a793459e12fd0_img.jpg) - -Sequence diagram for Query status of A1 policy use case flow. The diagram shows an rApp on the left and a Non-RT RIC box on the right. Inside the Non-RT RIC box is a 'Non-anchored functions in SMO/Non-RT RIC Framework' box containing 'A1 policy functions'. The sequence is: 1. rApp sends a 'Query A1 policy status request' to the A1 policy functions. 2. The A1 policy functions send an 'AuthZ' message to themselves, with a note 'Check authorization in collaboration with SME functions'. 3. The A1 policy functions send a 'Query A1 policy status response' back to the rApp. - -Figure 10.7.4.1-1: Query status of A1 policy use case flow diagram. - -## 10.7.5 Required data - -For the Query A1 policy status request, the rApp provides the rAppId and the A1 policy identifier. - -The A1 policy functions respond with the status of the A1 policy. The status information of A1 policy is defined in A1TD [3]. - -## 10.8 A1-Related use case 6: Subscribe to status of an A1 policy. - -### 10.8.1 Overview - -This use case provides the description and requirements for subscribe to status of an A1 policy. - -### 10.8.2 Background and goal of the use case - -Subscribe to A1 policy status changes procedure is defined as part of A1 policy management service in R1GAP [1]. - -### 10.8.3 Entities/resources involved in the use case. - -- 1) A1 Policy functions in the role of A1 policy management service Producer - - a. support functionality to allow rApps to subscribe to and unsubscribe from A1 policy status changes. - - b. support notifying the rApp regarding the changes in the status of an A1 policy. - - c. provide response of success or failure to subscribe to A1 policy status changes and unsubscribe to A1 policy status changes. -- 2) rApp - -- a. supports functionality to initiate requests to subscribe to and unsubscribe from A1 policy status changes, -- b. supports functionality to accept notifications of status change of an A1 policy from A1 policy management service Producer. - -## 10.8.4 Solutions - -### 10.8.4.1 Subscribe to A1 policy status change. - -**Table 10.8.4.1-1: subscribe to A1 policy status change.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp subscribes to notifications about changes of the status of an A1 policy. | | -| Actors and Roles |
  • - rApp in the role of A1 policy management service Consumer.
  • - A1 policy functions in the role of A1 policy management service Producer.
| | -| Assumptions | rApp is aware of the A1 policy identifier of the A1 policy that it is interested in subscribing to status change notifications for. | | -| Preconditions | rApp is authorized to consume the A1 policy management service. | | -| Begins when | The rApp determines the need to subscribe to notifications, regarding changes in the status of an A1 policy. | | -| Step 1 (M) | The rApp request the A1 policy functions to subscribe to notifications regarding changes in the status of an A1 policy by providing the rAppId and A1 policy identifier. | | -| Step 2 (M) | The A1 policy functions check whether the rApp is authorized to send a subscription request. | | -| Step 3 (M) | The A1 policy functions respond with subscription identifier. | | -| Ends when | The rApp was able to subscribe to notifications. | | -| Exceptions | n/a | | -| Post Conditions |

The rApp can receive notifications when there are any changes in the status of the A1 policy.

The rApp can unsubscribe from status change notifications of the A1 policy.

| | -| Traceability | REQ-R1-A1P- FUN6. | | - -``` -@startuml -'https://plantuml.com/sequence-diagram' -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "A1 policy functions "as A1P - endbox -rApp -> A1P : <> subscribe A1 policy status change request\n(rAppId, A1 policy identifier) -activate A1P -A1P --> A1P : AuthZ -note right -Check authorization in collaboration -with SME functions -``` - -``` - -end note -A1P -> rApp : <> subscribe A1 policy status change response (subscription identifier) -Deactivate A1P -@enduml - -``` - -![Sequence diagram for 'Subscribe to A1 policy status change use case flow diagram'. It shows an rApp lifeline on the left and a Non-RT RIC lifeline on the right. The Non-RT RIC contains a box for 'Non-anchored functions in SMO/Non-RT RIC Framework' which includes 'A1 policy functions'. The sequence is: 1. rApp sends '«R1» subscribe A1 policy status change request (rAppId, A1 policy identifier)' to A1 policy functions. 2. A1 policy functions send an 'AuthZ' message to check authorization in collaboration with SME functions. 3. A1 policy functions send '«R1» subscribe A1 policy status change response (subscription identifier)' back to the rApp.](69467ece0a576b4c2ec3e0c89ba61527_img.jpg) - -Sequence diagram for 'Subscribe to A1 policy status change use case flow diagram'. It shows an rApp lifeline on the left and a Non-RT RIC lifeline on the right. The Non-RT RIC contains a box for 'Non-anchored functions in SMO/Non-RT RIC Framework' which includes 'A1 policy functions'. The sequence is: 1. rApp sends '«R1» subscribe A1 policy status change request (rAppId, A1 policy identifier)' to A1 policy functions. 2. A1 policy functions send an 'AuthZ' message to check authorization in collaboration with SME functions. 3. A1 policy functions send '«R1» subscribe A1 policy status change response (subscription identifier)' back to the rApp. - -Figure 10.8.4.1-1: Subscribe to A1 policy status change use case flow diagram. - -### 10.8.4.2 Notify A1 policy status change. - -Table 10.8.4.2 -1: Notify A1 policy status change use case. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp receives notifications about changes in the status of an A1 policy. | | -| Actors and Roles |
  • - rApp in the role of A1 policy management service Consumer.
  • - A1 policy functions in the role of A1 policy management service Producer.
| | -| Assumptions | n/a | | -| Preconditions | The rApp has subscribed to notifications on changes in the status of an A1 policy. | | -| Begins when | The A1 policy functions determine to send notifications, regarding changes in the status of the A1 policy to the subscribed rApp. | | -| Step 1 (M) | The A1 policy functions detect changes in status (i.e., an A1 policy status becomes enforced or not enforced). | | -| Step 2 (M) | The A1 policy functions send notifications regarding the changes to the subscribed rApp with subscription identifier and information about status changes of the A1 policy. | | -| Ends when | The rApp was able to process the changes in the status of the A1 policy. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-A1P- FUN7 | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "A1 policy functions " as A1P - endbox -autonumber -A1P->>A1P: detect the status change - -``` - -``` -A1P-> rApp : <> notify changes \n(subscription identifier) -@enduml -``` - -![Sequence diagram for Notify status change use case flow. It shows an rApp lifeline on the left and a 'Non-anchored functions in SMO/Non-RT RIC Framework' box on the right containing 'A1 policy functions'. Step 1: A dashed arrow points from the A1 policy functions to themselves with the text '1 detect the status change'. Step 2: A solid arrow points from the A1 policy functions to the rApp with the text '2 <> notify changes (subscription identifier)'.](ba676d18b6a00f27c5bfaec9eeec20be_img.jpg) - -Sequence diagram for Notify status change use case flow. It shows an rApp lifeline on the left and a 'Non-anchored functions in SMO/Non-RT RIC Framework' box on the right containing 'A1 policy functions'. Step 1: A dashed arrow points from the A1 policy functions to themselves with the text '1 detect the status change'. Step 2: A solid arrow points from the A1 policy functions to the rApp with the text '2 <> notify changes (subscription identifier)'. - -Figure 10.8.4.2 -1: Notify status change use case flow diagram. - -### 10.8.4.3 Unsubscribe from A1 policy status change. - -Table 10.8.4.3-1: Unsubscribe from A1 policy status change. - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | The rApp unsubscribes from A1 policy status change notifications. | | -| Actors and Roles |
  • rApp in the role of A1 policy management service Consumer.
  • A1 policy functions in the role of A1 policy management service Producer.
| | -| Assumptions | n/a | | -| Preconditions | The rApp is authorized to unsubscribe from A1 policy status change notifications.
The rApp has subscribed to A1 policy status change notifications. | | -| Begins when | The rApp determines to unsubscribe from A1 policy status change. | | -| Step 1 (M) | The rApp requests the A1 policy functions to unsubscribe from A1 policy status changes with rAppId and subscription identifier. | | -| Step 2 (M) | The A1 policy functions check whether the rApp is authorized to unsubscribe. | | -| Step 3 (M) | The A1 policy functions send a response. | | -| Ends when | The rApp was able to unsubscribe from A1 policy status change. | | -| Exceptions | n/a | | -| Post Conditions | The rApp is not subscribed to A1 policy status change. | | -| Traceability | REQ-R1-A1P- FUN9 | | - -``` -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp -endbox -box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "A1 policy functions " as A1P -endbox -autonumber -rApp -> A1P : <> Unsubscribe from A1 policy status change request(rAppId, subscription identifier) -activate A1P -``` - -``` - -A1P -> A1P : AuthZ -note right - Check authorization in collaboration - with SME functions -end note - -A1P -> rApp : <> Unsubscribe from A1 policy status change response -deactivate A1P -@enduml - -``` - -![Sequence diagram for 'Unsubscribe from A1 policy status change use case flow diagram'. It shows an rApp sending a request to A1 policy functions, which then call an AuthZ function (checked by a note about SME functions), and finally returning a response to the rApp.](a5404b7275b06497eecf9b5883604753_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant A1P as A1 policy functions - Note right of A1P: Check authorization in collaboration with SME functions - rApp->>A1P: 1 «R1» Unsubscribe from A1 policy status change request(rAppId, subscription identifier) - A1P->>A1P: 2 AuthZ - A1P->>rApp: 3 «R1» Unsubscribe from A1 policy status change response - -``` - -Sequence diagram for 'Unsubscribe from A1 policy status change use case flow diagram'. It shows an rApp sending a request to A1 policy functions, which then call an AuthZ function (checked by a note about SME functions), and finally returning a response to the rApp. - -Figure 10.8.4.3-1: Unsubscribe from A1 policy status change use case flow diagram. - -## 10.8.5 Required data - -To receive notifications regarding changes in status change of an A1 policy, the rApp as A1 policy service Consumer subscribes to notifications by providing rAppId and A1 policy identifier. When the A1 policy functions have successfully processed the request, they respond by providing a subscription identifier. - -The A1 policy functions send notifications to the subscribed rApp when there are changes in status changes of the A1 policy by providing subscription identifier, and information about the changes (i.e., A1 policy status becomes enforced or not enforced). - -For unsubscribing from notifications, a subscribed rApp needs to provide the rAppId and subscription identifier. - -# 11 Use cases for AI/ML Workflow Services - -## 11.1 AI/ML workflow-related use case 1: AI/ML model registration and deregistration - -### 11.1.1 Overview - -This use case enables an rApp as AI/ML model management and exposure services Consumer to register AI/ML models, query AI/ML model registration, update AI/ML model registrations and deregister AI/ML models. - -### 11.1.2 Background and goal of the use case - -An AI/ML model producer rApp can register an AI/ML model, query and update the registration of an AI/ML model and deregister an AI/ML model with the AI/ML workflow functions. - -### 11.1.3 Entities/resources involved in the use case. - -- 1) AI/ML workflow functions as AI/ML model management and exposure services Producer - -- a. support the functionality to allow an rApp to register, query and update the registration of, and deregister an AI/ML model, - - b. provide the response of success or failure results to the register AI/ML model, query, and update AI/ML model registration, and deregister AI/ML model request. -- 2) rApp as AI/ML model management and exposure services Consumer -- a. support to initiate the procedure to register an AI/ML model, query and update the registration of an AI/ML model and deregister an AI/ML model. - -## 11.1.4 Solutions - -### 11.1.4.1 Register AI/ML model. - -**Table 11.1.4.1-1: Register AI/ML model.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The AI/ML model producer rApp registers an AI/ML model. | | -| Actors and Roles |
  • – rApp in the role of AI/ML model management and exposure services Consumer.
  • – AI/ML workflow functions in the role of AI/ML model management and exposure services Producer.
| | -| Assumptions | The AI/ML model that they intend to register in AI/ML workflow functions has not been registered before. | | -| Preconditions |
  • – The rApp is authorized to access the AI/ML model management and exposure services for registering an AI/ML model.
  • – The AI/ML model is certified and onboarded in SMO run time library.
| | -| Begins when | The AI/ML model producer rApp determines the need to register an AI/ML model. | | -| Step 1 (M) | The rApp requests the AI/ML workflow functions to register the AI/ML model by providing the rAppId and AI/ML model-related information. | | -| Step 2 (M) | The AI/ML workflow functions check whether the rApp is authorized to register an AI/ML model. | | -| Step 3 (M) | The AI/ML workflow functions validate the register AI/ML model request. | | -| Step 4(M) | The AI/ML workflow functions register the AI/ML model. | | -| Step 5(M) | The AI/ML workflow functions respond to rApp with successful AI/ML model registration along with AI/ML model registration identifier. | | -| Ends when | The AI/ML model producer rApp was able to register the AI/ML model. | | -| Exceptions | n/a | | -| Post Conditions | The AI/ML model is discoverable, and the rApp can query, update, or delete the model registration. | | -| Traceability | REQ-R1-AIML-Registermodel-FUN1 | | - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent -autonumber - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rApp" as src -``` - -``` - -endbox - -box " Non-anchored functions in SMO/Non-RT RIC Framework " #cadetBlue - participant "AI/ML workflow functions" as ML -endbox - -endbox - -src -> ML: <> Register AI/ML model request (rAppId, AI/ML model-related information) -ML -> ML: Authz -note right -Check authorization in -collaboration with SME functions -end note -ML -> ML: Validate -ML -> ML: Register AI/ML model -ML -> src: <> Register AI/ML model response (AI/ML model registration identifier) -@enduml - -``` - -![Sequence diagram for Register AI/ML model use case flow. Lifelines: rApp and Non-anchored functions in SMO/Non-RT RIC Framework (AI/ML workflow functions). The sequence shows: 1. rApp sends Register AI/ML model request to AI/ML workflow functions. 2. AI/ML workflow functions perform Authz (Check authorization in collaboration with SME functions). 3. AI/ML workflow functions perform Validate. 4. AI/ML workflow functions perform Register AI/ML model. 5. AI/ML workflow functions send Register AI/ML model response back to rApp.](9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg) - -``` - -sequenceDiagram - box Non-RT RIC - participant rApp - participant ML as AI/ML workflow functions - end - rApp->>ML: 1 «R1» Register AI/ML model request (rAppId, AI/ML model-related information) - ML->>ML: 2 Authz - Note right of ML: Check authorization in collaboration with SME functions - ML->>ML: 3 Validate - ML->>ML: 4 Register AI/ML model - ML->>rApp: 5 «R1» Register AI/ML model response (AI/ML model registration identifier) - -``` - -Sequence diagram for Register AI/ML model use case flow. Lifelines: rApp and Non-anchored functions in SMO/Non-RT RIC Framework (AI/ML workflow functions). The sequence shows: 1. rApp sends Register AI/ML model request to AI/ML workflow functions. 2. AI/ML workflow functions perform Authz (Check authorization in collaboration with SME functions). 3. AI/ML workflow functions perform Validate. 4. AI/ML workflow functions perform Register AI/ML model. 5. AI/ML workflow functions send Register AI/ML model response back to rApp. - -**Figure 11.1.4.1-1: Register AI/ML model use case flow diagram.** - -### 11.1.4.2 Query AI/ML model registration. - -**Table 11.1.4.2-1: Query AI/ML model registration.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The AI/ML model producer rApp queries an AI/ML model registration. | | -| Actors and Roles |
  • – rApp in the role of AI/ML model management and exposure services Consumer.
  • – AI/ML workflow functions in the role of AI/ML model management and exposure services Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the AI/ML model management and exposure services for registering an AI/ML model.
  • – The AI/ML model has been registered by the rApp.
| | -| Begins when | The AI/ML model producer rApp determines the need to query the registration of a registered AI/ML model. | | -| Step 1 (M) | The AI/ML model producer rApp requests to query the registration of an AI/ML model by providing rAppId and registration identifier. | | -| Step 2 (M) | The AI/ML workflow functions check whether the rApp is authorized to query the AI/ML model registration. | | -| Step 3(M) | The AI/ML workflow functions look up the information of queried AI/ML model. | | -| Step 4(M) | The AI/ML workflow functions respond to rApp with AI/ML model-related information. | | -| Ends when | The AI/ML model producer rApp was able to query the AI/ML model registration. | | -| Exceptions | n/a | | -| Post Conditions | The AI/ML model is discoverable, and the rApp can query, update or delete the AI/ML model registration. | | -| Traceability | REQ-R1-AIML-Registermodel-FUN1 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent -autonumber - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rApp" as src - endbox - - box " Non-anchored functions in SMO/Non-RT RIC Framework " #cadetBlue - participant "AI/ML workflow functions" as ML - endbox -endbox - -src -> ML: <> Query AI/ML model request (rAppId, AI/ML model registration identifier) -ML -> ML: Authz -note right -Check authorization in -collaboration with SME functions -end note -ML -> ML: Look up AI/ML model registration -ML -> src: <> Query AI/ML model response (AI/ML model-related information) -@enduml - -``` - -![Sequence diagram for Query AI/ML model registration use case flow. Lifelines: rApp (left), Non-RT RIC (right). The Non-RT RIC contains a sub-block 'Non-anchored functions in SMO/Non-RT RIC Framework' which includes 'AI/ML workflow functions'. The sequence is: 1. rApp sends 'Query AI/ML model request (rAppId, AI/ML model registration identifier)' to AI/ML workflow functions. 2. AI/ML workflow functions perform 'Authz' (Check authorization in collaboration with SME functions). 3. AI/ML workflow functions perform 'Look up AI/ML model registration'. 4. AI/ML workflow functions send 'Query AI/ML model response (AI/ML model-related information)' back to rApp.](7e12e1e0d03a03790d2e9d74c3454bff_img.jpg) - -Sequence diagram for Query AI/ML model registration use case flow. Lifelines: rApp (left), Non-RT RIC (right). The Non-RT RIC contains a sub-block 'Non-anchored functions in SMO/Non-RT RIC Framework' which includes 'AI/ML workflow functions'. The sequence is: 1. rApp sends 'Query AI/ML model request (rAppId, AI/ML model registration identifier)' to AI/ML workflow functions. 2. AI/ML workflow functions perform 'Authz' (Check authorization in collaboration with SME functions). 3. AI/ML workflow functions perform 'Look up AI/ML model registration'. 4. AI/ML workflow functions send 'Query AI/ML model response (AI/ML model-related information)' back to rApp. - -Figure 11.1.4.2-1: Query AI/ML model registration use case flow diagram. - -### 11.1.4.3 Update AI/ML model registration. - -Table 11.1.4.3-1: Update AI/ML model registration. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The AI/ML model producer rApp updates the registration of an AI/ML model. | | -| Actors and Roles |
  • – rApp in the role of AI/ML model management and exposure services Consumer.
  • – AI/ML workflow functions in the role of AI/ML model management and exposure services Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the AI/ML model management and exposure services for updating an AI/ML model registration.
  • – The AI/ML model has been registered by the rApp.
| | -| Begins when | The AI/ML model producer rApp determines the need to update the registration of an AI/ML model. | | -| Step 1 (M) | The AI/ML model producer rApp requests to update the registration of an AI/ML model by providing rAppId, updated model registration information, etc. | | -| Step 2 (M) | The AI/ML workflow functions check whether the rApp is authorized to update the registration. | | -| Step 3 (M) | The AI/ML workflow functions validate the update AI/ML model registration request. | | -| Step 4 (M) | The AI/ML workflow functions update the registration of the AI/ML model. | | -| Step 5 (M) | The AI/ML workflow functions respond to the model producer rApp with successful update AI/ML model registration response. | | -| Ends when | The AI/ML model producer rApp was able to update the registration of the AI/ML model. | | -| Exceptions | n/a | | -| Post Conditions | The rApp can query, update, or delete the AI/ML model registration. The updated AI/ML model is discoverable and is notified to all subscribed model consumer rApps. | | -| Traceability | REQ-R1-AIML-Registermodel-FUN1 | | - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -``` - -``` - -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rApp" as app - endbox - - box "Non-anchored functions \n in SMO/Non-RT RIC FWK" #cadetBlue - participant "AI/ML workflow functions" as aif - endbox -endbox - -autonumber -app -> aif: <> Update model registration request \n (rAppId, AI/ML model registration -identifier, \n updated model registration information) -activate aif -aif --> aif: AuthZ -note right -Check authorization in -collaboration with SME functions -end note -aif --> aif: Validate -aif --> aif: Update model \n registration information -app <- aif: <> Update model registration response -deactivate aif -@enduml - -``` - -![UML Sequence diagram for 'Update registration of an AI/ML model'. Lifelines: rApp and AI/ML workflow functions (within Non-RT RIC). The sequence shows: 1. rApp sends an Update model registration request to AI/ML workflow functions. 2. AI/ML workflow functions perform AuthZ (with a note: Check authorization in collaboration with SME functions). 3. AI/ML workflow functions perform Validate. 4. AI/ML workflow functions perform Update model registration information. 5. AI/ML workflow functions return an Update model registration response to rApp.](eabcb2f8b9acedb194571d5bc734b463_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant AI/ML_workflow_functions as AI/ML workflow functions - Note right of AI/ML_workflow_functions: Check authorization in collaboration with SME functions - rApp->>AI/ML_workflow_functions: 1 «R1» Update model registration request (rAppId, AI/ML model registration identifier, updated model registration information) - activate AI/ML_workflow_functions - AI/ML_workflow_functions-->>AI/ML_workflow_functions: 2 AuthZ - AI/ML_workflow_functions-->>AI/ML_workflow_functions: 3 Validate - AI/ML_workflow_functions-->>AI/ML_workflow_functions: 4 Update model registration information - AI/ML_workflow_functions-->>rApp: 5 «R1» Update model registration response - deactivate AI/ML_workflow_functions - -``` - -UML Sequence diagram for 'Update registration of an AI/ML model'. Lifelines: rApp and AI/ML workflow functions (within Non-RT RIC). The sequence shows: 1. rApp sends an Update model registration request to AI/ML workflow functions. 2. AI/ML workflow functions perform AuthZ (with a note: Check authorization in collaboration with SME functions). 3. AI/ML workflow functions perform Validate. 4. AI/ML workflow functions perform Update model registration information. 5. AI/ML workflow functions return an Update model registration response to rApp. - -Figure 11.1.4.3-1: Update registration of an AI/ML model use case flow diagram. - -### 11.1.4.4 Deregister AI/ML model. - -**Table 11.1.4.4-1: Deregister AI/ML model.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The AI/ML model producer rApp deregisters an AI/ML model. | | -| Actors and Roles |
  • – rApp in the role of AI/ML model management and exposure services Consumer.
  • – AI/ML workflow functions in the role of AI/ML model management and exposure services Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the AI/ML model management and exposure services.
  • – The AI/ML model has been registered by the rApp.
| | -| Begins when | The AI/ML model producer rApp determines the need to deregister an AI/ML model it has previously registered. | | -| Step 1 (M) | The rApp requests AI/ML workflow functions to deregister the AI/ML model by providing rAppId and AI/ML model registration identifier. | | -| Step 2 (M) | The AI/ML workflow functions check whether the rApp is authorized to deregister the AI/ML model. | | -| Step 3 (M) | The AI/ML workflow functions delete the registration of the AI/ML model. | | -| Step 4 (M) | The AI/ML workflow functions respond to the rApp with successful deregister AI/ML model response. | | -| Ends when | The AI/ML model producer rApp was able to deregister the AI/ML model. | | -| Exceptions | n/a | | -| Post Conditions | The AI/ML model is not discoverable any longer. | | -| Traceability | REQ-R1-AIML-Registermodel-FUN1 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent -autonumber - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rApp" as src - endbox - - box " Non-anchored functions in SMO/Non-RT RIC Framework " #cadetBlue - participant "AI/ML workflow functions" as ML - endbox - -endbox - -src -> ML: <> Deregister AI/ML model request \n(rAppId, AI/ML model registration identifier) -ML -> ML: Authz -note right -Check authorization in -collaboration with SME functions -end note -ML -> ML: Deregister AI/ML model -ML -> src: <> Deregister AI/ML model response -@enduml - -``` - -![Sequence diagram for 'Deregister AI/ML model' use case. The diagram shows an rApp on the left interacting with 'Non-anchored functions in SMO/Non-RT RIC Framework' on the right. The sequence is: 1. rApp sends a '«R1» Deregister AI/ML model request' to the framework. 2. The framework performs an 'Authz' check, with a note 'Check authorization in collaboration with SME functions'. 3. The framework performs the 'Deregister AI/ML model' action. 4. The framework sends a '«R1» Deregister AI/ML model response' back to the rApp. The framework contains 'AI/ML workflow functions' at the top and bottom.](2d548db0b26b7bf33244320322d5ee2c_img.jpg) - -Sequence diagram for 'Deregister AI/ML model' use case. The diagram shows an rApp on the left interacting with 'Non-anchored functions in SMO/Non-RT RIC Framework' on the right. The sequence is: 1. rApp sends a '«R1» Deregister AI/ML model request' to the framework. 2. The framework performs an 'Authz' check, with a note 'Check authorization in collaboration with SME functions'. 3. The framework performs the 'Deregister AI/ML model' action. 4. The framework sends a '«R1» Deregister AI/ML model response' back to the rApp. The framework contains 'AI/ML workflow functions' at the top and bottom. - -Figure 11.1.4.4-1: Deregister AI/ML model use case flow diagram. - -### 11.1.5 Required data - -The AI/ML model-related information includes the AI/ML model identifier, AI/ML model description, input, and output datatype, etc. - -For registering an AI/ML model, the rApp provides the rAppId and AI/ML model-related information. On successful registration, AI/ML workflow functions provide an AI/ML model registration identifier for the registration of the AI/ML model. - -For querying the registration of an AI/ML model, the rApp needs to provide the rAppId and the AI/ML model registration identifier. - -For updating the registration of an AI/ML model, the rApp needs to provide the rAppId, the AI/ML model registration identifier and the updated AI/ML model-related information or the modified part of the AI/ML model-related information. - -For deregistering an AI/ML model, the rApp provides the rAppId and the AI/ML model registration identifier. - -## 11.2 AI/ML workflow-related use case 2: Discovery of AI/ML Model. - -### 11.2.1 Overview - -This use case enables an rApp to retrieve information about registered AI/ML Models and their associated information. - -### 11.2.2 Background and goal of the use case. - -The discover AI/ML model procedure is defined as part of the AI/ML workflow services in R1GAP [1]. - -### 11.2.3 Entities/resources involved in the use case. - -- 1) AI/ML workflow functions in the role of AI/ML model management and exposure service Producer - - a) support functionality allowing rApps to discover the registered AI/ML Models, -- 2) rApp in the role of AI/ML model management and exposure Consumer - - a) initiates the procedure to discover the registered AI/ML models. - -## 11.2.4 Solutions - -### 11.2.4.1 Discover AI/ML models. - -**Table 11.2.4.1-1: Discover AI/ML models.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp discovers registered AI/ML models. | | -| Actors and Roles |
  • – rApp in the role of AI/ML model management and exposure Consumer.
  • – AI/ML workflow functions in the role of AI/ML model management and exposure service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the AI/ML workflow services.
  • – At least one AI/ML model is registered with the AI/ML workflow functions.
| | -| Begins when | The rApp determines the need to discover the registered AI/ML models. | | -| Step 1 (M) | The rApp requests the AI/ML workflow functions for the information on the AI/ML Models by providing rAppId and optional selection criteria. | | -| Step 2(M) | The AI/ML workflow functions validate if the rApp is authorized to discover the registered AI/ML models. | | -| Step 3(M) | The AI/ML workflow functions provide the information about registered AI/ML models. The list contains the information of those AI/ML models that match the filtering criteria if those were provided by the rApp, or of all AI/ML models otherwise. For each AI/ML model, the model identifier and model metadata are provided. | | -| Ends when | The rApp was able to discover the registered AI/ML models. | | -| Exceptions | n/a | | -| Post Conditions | The rApp can use the AI/ML model identifier in other AI/ML workflow services. | | -| Traceability | REQ-R1-AI/ML-discovery -FUN1 | | - -``` -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant " AI/ML workflow functions " as aif - endbox -rApp ->aif:<> Discover AI/ML model request\n(rAppId,Selection criteria) -activate aif -aif --> aif:AuthZ -note right -Check authorization in collaboration -with SME functions -end note -aif -> rApp :<>Discover AI/ML model response\n(model identifiers,model metadata) -deactivate aif -@enduml -``` - -![Figure 11.2.4.1-1: Discover AI/ML model use case flow diagram. The diagram shows a sequence of interactions between an rApp and the Non-RT RIC framework. 1. The rApp sends an 'R1 Discover AI/ML model request' (rAppId, Selection criteria) to the AI/ML workflow functions. 2. The AI/ML workflow functions send an 'AuthZ' request to the SME functions, with a note 'Check authorization in collaboration with SME functions'. 3. The AI/ML workflow functions send an 'R1 Discover AI/ML model response' (model identifiers, model metadata) back to the rApp. The Non-RT RIC framework contains 'Non-anchored functions in SMO/Non-RT RIC Framework' and 'AI/ML workflow functions'.](2c41e286ea9a1b008d3beb348d86096f_img.jpg) - -Figure 11.2.4.1-1: Discover AI/ML model use case flow diagram. The diagram shows a sequence of interactions between an rApp and the Non-RT RIC framework. 1. The rApp sends an 'R1 Discover AI/ML model request' (rAppId, Selection criteria) to the AI/ML workflow functions. 2. The AI/ML workflow functions send an 'AuthZ' request to the SME functions, with a note 'Check authorization in collaboration with SME functions'. 3. The AI/ML workflow functions send an 'R1 Discover AI/ML model response' (model identifiers, model metadata) back to the rApp. The Non-RT RIC framework contains 'Non-anchored functions in SMO/Non-RT RIC Framework' and 'AI/ML workflow functions'. - -**Figure 11.2.4.1-1: Discover AI/ML model use case flow diagram.** - -## 11.2.5 Required data - -For the Discover AI/ML model request, the rApp provides the rAppId and optional selection criteria. - -The AI/ML workflow functions respond with information which includes the model identifiers and metadata information. The metadata information contains AI/ML model related information and training related information. - -If selection criteria information was provided in the related request, the response only contains information about those AI/ML models information that match the filtering criteria. - -## 11.3 AI/ML workflow-related use case 3: AI/ML training – AI/ML workflow functions producing AI/ML training services. - -### 11.3.1 Overview - -This use case defines how an rApp as an AI/ML training services Consumer requests AI/ML training, queries AI/ML training job status, cancels AI/ML training, and receives notification about AI/ML training job status change, when the AI/ML workflow functions in the SMO/Non-RT RIC framework acts as the AI/ML training services Producer. - -### 11.3.2 Background and goal of the use case - -An AI/ML training services Consumer rApp can request the AI/ML workflow functions in the Non-RT RIC framework to train an AI/ML model. For on-going AI/ML training, the AI/ML training services Consumer rApp can query the training job status or cancel the AI/ML training. If the training job status is changed, the AI/ML workflow functions can notify the AI/ML training service Consumer rApp about the training job status change. - -### 11.3.3 Entities/resources involved in the use case. - -- 1) AI/ML workflow functions as AI/ML training services Producer - - a. support the functionality to allow an AI/ML training services Consumer rApp to request training, query training job status, and cancel training. - - b. provide the response of success or failure results to the request training, query training job status, and cancel training request. - - c. support the functionality to notify an AI/ML training services Consumer rApp about the training job status change. - -2) AI/ML training services Consumer rApp - -- a. support to initiate the procedure to request AI/ML training, query AI/ML training job status, and cancel AI/ML training. -- b. support the functionality to receive notification of AI/ML training job status change. - -### 11.3.4 Solutions - -#### 11.3.4.1 Request AI/ML training. - -**Table 11.3.4.1-1: Request AI/ML training use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The AI/ML training services Consumer rApp requests training of an AI/ML model. | | -| Actors and Roles |
  • – AI/ML training services Consumer rApp in the role of Service Consumer.
  • – The AI/ML workflow functions in the role of Service Producer.
| | -| Assumptions | n/a | | -| Preconditions | The AI/ML training services Consumer rApp is deployed, authenticated, and authorized to consume AI/ML training services. | | -| Begins when | The AI/ML training services Consumer rApp determines the need to train an AI/ML model. | | -| Step 1 (M) | The AI/ML training services Consumer rApp requests the AI/ML workflow functions to train an AI/ML model providing rAppId, information for training, and optionally a notification URI, etc. | | -| Step 2 (M) | The AI/ML workflow functions check with SME functions whether the AI/ML training services Consumer rApp is authorized to request training. | | -| Step 3 (M) | The AI/ML workflow functions validate the request. | | -| Step 4 (M) | The AI/ML workflow functions create the training job. | | -| Step 5 (M) | The AI/ML workflow functions respond to the AI/ML training services Consumer rApp with training job identifier as a parameter. | | -| Ends when | The AI/ML training services Consumer rApp is able to create the training job at the AI/ML workflow functions. | | -| Exceptions | n/a | | -| Post Conditions | The AI/ML workflow functions can retrieve model to be trained from model repository and consume training data from DME. | | -| Traceability | REQ-R1-AI/ML-training-FUN1 | | - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "AI/ML training services \n Consumer rApp" as con - endbox - - box "Non-anchored functions \n in SMO/Non-RT RIC FWK" #cadetBlue - participant "AI/ML workflow functions" as aif - endbox -endbox - -autonumber -con -> aif: <> Request training request \n (rApp id, information for training, \n notification URI, etc.) -activate aif -``` - -``` - -aif --> aif: AuthZ -note right -Check authorization in -collaboration with SME functions -end note -aif --> aif: Validate -aif --> aif: Create training job -con <- aif: <> Request training response \n (training job id) -deactivate aif -@enduml - -``` - -![Sequence diagram titled 'Non-RT RIC' showing the interaction between 'AI/ML training services Consumer rApp' and 'AI/ML workflow functions'. The sequence includes: 1. Request training request (rApp id, information for training, notification URI, etc.), 2. AuthZ (with a note: Check authorization in collaboration with SME functions), 3. Validate, 4. Create training job, and 5. Request training response (training job id).](da85343976fdbb19f866d9ddbdad0eae_img.jpg) - -``` - -sequenceDiagram - participant Consumer rApp as AI/ML training services Consumer rApp - participant Workflow Functions as AI/ML workflow functions - Note right of Workflow Functions: Check authorization in collaboration with SME functions - Consumer rApp->>Workflow Functions: 1 «R1» Request training request (rApp id, information for training, notification URI, etc.) - Workflow Functions-->>Workflow Functions: 2 AuthZ - Workflow Functions-->>Workflow Functions: 3 Validate - Workflow Functions-->>Workflow Functions: 4 Create training job - Workflow Functions-->>Consumer rApp: 5 «R1» Request training response (training job id) - -``` - -Sequence diagram titled 'Non-RT RIC' showing the interaction between 'AI/ML training services Consumer rApp' and 'AI/ML workflow functions'. The sequence includes: 1. Request training request (rApp id, information for training, notification URI, etc.), 2. AuthZ (with a note: Check authorization in collaboration with SME functions), 3. Validate, 4. Create training job, and 5. Request training response (training job id). - -Figure 11.3.4.1-1: Request AI/ML training use case flow diagram. - -### 11.3.4.2 Query AI/ML training job status. - -**Table 11.3.4.2-1: Query AI/ML training job status use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The AI/ML training services Consumer rApp query training job status of a created training job. | | -| Actors and Roles |
  • AI/ML training services Consumer rApp in the role of Service Consumer.
  • The AI/ML workflow functions in the role of Service Producer.
| | -| Assumptions | n/a | | -| Preconditions | The AI/ML training services Consumer rApp is deployed, authenticated, and authorized to consume AI/ML training services. | | -| Begins when | The AI/ML training services Consumer rApp determines the need to query the training job status. | | -| Step 1 (M) | The AI/ML training services Consumer rApp queries the AI/ML workflow functions about the status of a created training job by providing rAppId and training job identifier. | | -| Step 2 (M) | The AI/ML workflow functions check with SME functions whether the AI/ML training services Consumer rApp is authorized to query the training job status. | | -| Step 3 (M) | The AI/ML workflow functions validate the request. | | -| Step 4 (M) | The AI/ML workflow functions respond to the AI/ML training services Consumer rApp with training job status. | | -| Ends when | The AI/ML training services Consumer rApp is able to obtain the training job status. | | -| Exceptions | n/a | | -| Post Conditions | The training job status is known to the AI/ML training services Consumer rApp. | | -| Traceability | REQ-R1-AI/ML-training-FUN2 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "AI/ML training services \n Consumer rApp" as con - endbox - - box "Non-anchored functions \n in SMO/Non-RT RIC FWK" #cadetBlue - participant "AI/ML workflow functions" as aif - endbox -endbox - -autonumber -con -> aif: <> Query training status request \n (rApp id, training id) -activate aif -aif --> aif: AuthZ -note right -Check authorization in -collaboration with SME functions -end note -aif --> aif: Validate -con <- aif: <> Query training status response \n (training job status) -deactivate aif -@enduml - -``` - -![Sequence diagram for 'Query AI/ML training job status'. Lifelines: AI/ML training services Consumer rApp and Non-anchored functions in SMO/Non-RT RIC FWK. The process involves: 1. Request (rApp id, training id), 2. AuthZ (check authorization), 3. Validate, 4. Response (training job status).](b0b9bc3067d012eb2fa3539217b9c34d_img.jpg) - -``` - -sequenceDiagram - participant Consumer rApp - participant Non-anchored functions in SMO/Non-RT RIC FWK - Note right of Non-anchored functions: Check authorization in collaboration with SME functions - Consumer rApp->>Non-anchored functions: 1 «R1» Query training status request (rApp id, training id) - Non-anchored functions-->>Consumer rApp: 2 AuthZ - Non-anchored functions-->>Consumer rApp: 3 Validate - Non-anchored functions-->>Consumer rApp: 4 «R1» Query training status response (training job status) - -``` - -Sequence diagram for 'Query AI/ML training job status'. Lifelines: AI/ML training services Consumer rApp and Non-anchored functions in SMO/Non-RT RIC FWK. The process involves: 1. Request (rApp id, training id), 2. AuthZ (check authorization), 3. Validate, 4. Response (training job status). - -Figure 11.3.4.2-1: Query AI/ML training job status use case flow diagram. - -### 11.3.4.3 Cancel AI/ML training. - -Table 11.3.4.3-1: Cancel AI/ML training use case. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The AI/ML training services Consumer rApp cancels training of an AI/ML model. | | -| Actors and Roles |
  • AI/ML training services Consumer rApp in the role of Service Consumer.
  • The AI/ML workflow functions in the role of Service Producer.
| | -| Assumptions | n/a | | -| Preconditions | The AI/ML training services Consumer rApp is deployed, authenticated, and authorized to consume AI/ML training services. | | -| Begins when | The AI/ML training services Consumer rApp determines to cancel the training of an AI/ML model. | | -| Step 1 (M) | The AI/ML training services Consumer rApp cancels the training by providing rAppId and training job identifier. | | -| Step 2 (M) | The AI/ML workflow functions check with SME functions whether the AI/ML training services Consumer rApp is authorized to cancel the training. | | -| Step 3 (M) | The AI/ML workflow functions validate the request. | | -| Step 4 (M) | The AI/ML workflow functions stop the training job. | | -| Step 5 (M) | The AI/ML workflow functions respond to the AI/ML training services Consumer rApp. | | -| Ends when | The AI/ML workflow functions are able to cancel training of an AI/ML model. | | -| Exceptions | n/a | | -| Post Conditions | The training is cancelled, and the training job is terminated. | | -| Traceability | REQ-R1-AI/ML-training-FUN1 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -``` - -``` - -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent - -box Non-RT RIC #whitesmoke - box #ivory - participant AI/ML training services \n Consumer rApp as con - endbox - - box Non-anchored functions \n in SMO/Non-RT RIC FWK" #cadetBlue - participant "AI/ML workflow functions" as aif - endbox -endbox - -autonumber -con -> aif: <> Cancel training request \n (rApp id, training job id.) -activate aif -aif -> aif: AuthZ -note right -Check authorization in -collaboration with SME functions -end note -aif --> aif: Validate -aif --> aif: Stop training job -con <- aif: <> Cancel training response -deactivate aif - -@enduml - -``` - -![Sequence diagram for Cancel AI/ML training use case. Lifelines: AI/ML training services Consumer rApp and AI/ML workflow functions. The sequence shows a request from the consumer to the workflow functions, followed by internal steps (AuthZ, Validate, Stop training job) with a note about SME collaboration, and finally a response back to the consumer.](72d448a65347c51989171748789c7d4b_img.jpg) - -``` - -sequenceDiagram - participant Consumer rApp as AI/ML training services Consumer rApp - participant AI/ML workflow functions - Note right of AI/ML workflow functions: Check authorization in collaboration with SME functions - Consumer rApp->>AI/ML workflow functions: 1 «R1» Cancel training request (rApp id, training job id.) - activate AI/ML workflow functions - AI/ML workflow functions-->>AI/ML workflow functions: 2 AuthZ - AI/ML workflow functions-->>AI/ML workflow functions: 3 Validate - AI/ML workflow functions-->>AI/ML workflow functions: 4 Stop training job - AI/ML workflow functions-->>Consumer rApp: 5 «R1» Cancel training response - deactivate AI/ML workflow functions - -``` - -Sequence diagram for Cancel AI/ML training use case. Lifelines: AI/ML training services Consumer rApp and AI/ML workflow functions. The sequence shows a request from the consumer to the workflow functions, followed by internal steps (AuthZ, Validate, Stop training job) with a note about SME collaboration, and finally a response back to the consumer. - -Figure 11.3.4.3-1: Cancel AI/ML training use case flow diagram. - -### 11.3.4.4 Notify AI/ML training job status change. - -**Table 11.3.4.4-1: Notify AI/ML training job status change use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The AI/ML workflow functions notify the AI/ML training services Consumer rApp about the training job status change of a created training job. | | -| Actors and Roles |
  • AI/ML training services Consumer rApp in the role of Service Consumer.
  • The AI/ML workflow functions in the role of Service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • The AI/ML training services Consumer rApp is deployed, authenticated, and authorized to consume AI/ML training services.
  • The AI/ML training services Consumer rApp had provided a notification URI to the AI/ML workflow functions.
| | -| Begins when | The AI/ML workflow functions determine the need to notify training job status change to the AI/ML training services Consumer rApp. | | -| Step 1 (M) | The AI/ML workflow functions notify the training job status change to AI/ML training services Consumer rApp. | | -| Ends when | The AI/ML training services Consumer rApp is notified about the updated training job status. | | -| Exceptions | n/a | | -| Post Conditions | The updated training job status is known to the AI/ML training services Consumer rApp. | | -| Traceability | REQ-R1-AI/ML-training-FUN3 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "AI/ML training services \n Consumer rApp" as con - endbox - - box "Non-anchored functions \n in SMO/Non-RT RIC FWK" #cadetBlue - participant "AI/ML workflow functions" as aif - endbox -endbox - -autonumber -con <- aif: <> Notify training job status change \n (training job id, training job status, -model id) -@enduml - -``` - -![Figure 11.3.4.4-1: Notify AI/ML training job status change use case flow diagram. The diagram shows the interaction within a Non-RT RIC. On the left, two boxes represent 'AI/ML training services Consumer rApp'. On the right, a teal box labeled 'Non-anchored functions in SMO/Non-RT RIC FWK' contains two 'AI/ML workflow functions' boxes. An arrow labeled '1 «R1» Notify training job status change (training job id, training job status, model id)' points from the top 'AI/ML workflow functions' box to the top 'AI/ML training services Consumer rApp' box.](5661815043254c37a4e3e4833f51e727_img.jpg) - -Figure 11.3.4.4-1: Notify AI/ML training job status change use case flow diagram. The diagram shows the interaction within a Non-RT RIC. On the left, two boxes represent 'AI/ML training services Consumer rApp'. On the right, a teal box labeled 'Non-anchored functions in SMO/Non-RT RIC FWK' contains two 'AI/ML workflow functions' boxes. An arrow labeled '1 «R1» Notify training job status change (training job id, training job status, model id)' points from the top 'AI/ML workflow functions' box to the top 'AI/ML training services Consumer rApp' box. - -**Figure 11.3.4.4-1: Notify AI/ML training job status change use case flow diagram.** - -## 11.3.5 Required data - -For requesting training, the AI/ML training services Consumer rApp needs to provide its rAppId, information for training (e.g., information about training dataset, model identifier, training criteria.), and optionally a notification URI to receive notification about training job status change. If the AI/ML workflow functions accept the training request, they assign a training job identifier for the created training job. - -For querying training job status, the AI/ML training services Consumer rApp needs to provide its rAppId and the training job identifier. The AI/ML workflow functions respond with the status of the training job identified by the training job identifier. - -For cancelling training, the AI/ML training services Consumer rApp needs to provide its rAppId and the training job identifier. - -For notifying training job status change, the AI/ML workflow functions provide the training job status, the training job identifier, and optionally model identifier. - -## 11.4 AI/ML workflow-related use case 4: AI/ML training – rApp producing AI/ML training services. - -### 11.4.1 Overview - -This use case defines how an rApp as an AI/ML training services Consumer requests AI/ML training, queries AI/ML training job status, cancels AI/ML training, and receives notification about AI/ML training job status change, when another rApp acts as the AI/ML training services Producer. - -### 11.4.2 Background and goal of the use case - -An AI/ML training services Consumer rApp can request the AI/ML training service Producer rApp to train an AI/ML model. For on-going AI/ML training, the AI/ML training services Consumer rApp can query the training job status or cancel the AI/ML training. If the training job status is changed, the AI/ML training services Producer rApp can notify the AI/ML training service Consumer rApp about the training job status change. - -### 11.4.3 Entities/resources involved in the use case. - -- 1) AI/ML training services Producer rApp - - a. supports the functionality to allow an AI/ML training services Consumer rApp to request training, query training job status, and cancel training. - - b. provides the response of success or failure results to the request training, query training job status, and cancel training request. - -- c. supports the functionality to notify an AI/ML training services Consumer rApp about the training job status change. -- 2) AI/ML training services Consumer rApp -- a. supports to initiate the procedure to request AI/ML training, query AI/ML training job status, and cancel AI/ML training, - - b. supports the functionality to receive notification of AI/ML training job status change. - -## 11.4.4 Solutions - -### 11.4.4.1 Request AI/ML training. - -**Table 11.4.4.1-1: Request AI/ML training use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The AI/ML training services Consumer rApp requests training of an AI/ML model. | | -| Actors and Roles |
  • – AI/ML training services Consumer rApp in the role of Service Consumer.
  • – AI/ML training service Producer rApp in the role of Service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The AI/ML training services Consumer rApp is deployed, authenticated, and authorized to consume AI/ML training services.
  • – The AI/ML training services Producer rApp is deployed, authenticated, and authorized to produce AI/ML training services.
| | -| Begins when | The AI/ML training services Consumer rApp determines the need to train an AI/ML model. | | -| Step 1 (M) | The AI/ML training services Consumer rApp requests the AI/ML training services Producer rApp to train an AI/ML model providing rAppId, information for training, and optionally a notification URI, etc. | | -| Step 2 (M) | The AI/ML training services Producer rApp checks with SME functions whether the AI/ML training services Consumer rApp is authorized to request training. | | -| Step 3 (M) | The AI/ML training services Producer rApp validates the request. | | -| Step 4 (M) | The AI/ML training services Producer rApp creates the training job. | | -| Step 5 (M) | The AI/ML training services Producer rApp responds to the AI/ML training services Consumer rApp with training job identifier as a parameter. | | -| Ends when | The AI/ML training services Consumer rApp is able to create the training job at the AI/ML training services Producer rApp. | | -| Exceptions | n/a | | -| Post Conditions | The AI/ML training service Producer rApp can retrieve model to be trained from model repository and consume training data from DME. | | -| Traceability | REQ-R1-AI/ML-training-FUN1 | | - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "AI/ML training services \n Consumer rApp" as con - participant "AI/ML training services \n Producer rApp" as aif - endbox -endbox -``` - -``` - -box "Non-anchored functions \n in SMO/Non-RT RIC FWK" #cadetBlue - participant "SME functions" as sme -endbox - -autonumber -con -> aif: Request training request \n (rApp id, information for training, \n notification URI, etc.) -activate aif -aif <-> sme: <> Check authorization in \n collaboration with SME functions -aif --> aif: Validate -aif --> aif: Create training job -con <- aif: Request training response \n (training job id) -deactivate aif -@enduml - -``` - -![Sequence diagram for Request AI/ML training use case flow. The diagram shows interactions between AI/ML training services (Consumer rApp and Producer rApp) within the Non-RT RIC and SME functions within Non-anchored functions in SMO/Non-RT RIC FWK. The flow consists of five steps: 1. Request training request from Consumer rApp to Producer rApp; 2. Check authorization in collaboration with SME functions from Producer rApp to SME functions; 3. Validate from SME functions to Producer rApp; 4. Create training job from SME functions to Producer rApp; 5. Request training response from Producer rApp to Consumer rApp.](684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg) - -``` - -sequenceDiagram - participant Consumer rApp - participant Producer rApp - participant SME functions - Note right of Producer rApp: Non-anchored functions in SMO/Non-RT RIC FWK - Consumer rApp->>Producer rApp: 1 Request training request (rApp id, information for training, notification URI, etc.) - activate Producer rApp - Producer rApp->>SME functions: 2 <> Check authorization in collaboration with SME functions - activate SME functions - SME functions-->>Producer rApp: 3 Validate - activate Producer rApp - Producer rApp-->>SME functions: 4 Create training job - deactivate Producer rApp - SME functions-->>Producer rApp: - deactivate SME functions - Producer rApp-->>Consumer rApp: 5 Request training response (training job id) - deactivate Producer rApp - -``` - -Sequence diagram for Request AI/ML training use case flow. The diagram shows interactions between AI/ML training services (Consumer rApp and Producer rApp) within the Non-RT RIC and SME functions within Non-anchored functions in SMO/Non-RT RIC FWK. The flow consists of five steps: 1. Request training request from Consumer rApp to Producer rApp; 2. Check authorization in collaboration with SME functions from Producer rApp to SME functions; 3. Validate from SME functions to Producer rApp; 4. Create training job from SME functions to Producer rApp; 5. Request training response from Producer rApp to Consumer rApp. - -Figure 11.4.4.1-1: Request AI/ML training use case flow diagram. - -11.4.4.2 Query AI/ML training job status. - -Table 11.4.4.2-1: Query AI/ML training job status use case. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The AI/ML training services Consumer rApp query training job status of a created training job. | | -| Actors and Roles |
  • AI/ML training services Consumer rApp in the role of Service Consumer.
  • AI/ML training service Producer rApp in the role of Service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • The AI/ML training services Consumer rApp is deployed, authenticated, and authorized to consume AI/ML training services.
  • The AI/ML training services Producer rApp is deployed, authenticated, and authorized to produce AI/ML training services.
| | -| Begins when | The AI/ML training services Consumer rApp determines the need to query the training job status. | | -| Step 1 (M) | The AI/ML training services Consumer rApp queries the AI/ML training service Producer rApp about the status of a created training job by providing rAppId and training job identifier. | | -| Step 2 (M) | The AI/ML training service Producer rApp checks with SME functions whether the AI/ML training services Consumer rApp is authorized to query the training job status. | | -| Step 3 (M) | The AI/ML training service Producer rApp validates the request. | | -| Step 4 (M) | The AI/ML training service Producer rApp responds to the AI/ML training services Consumer rApp with training job status. | | -| Ends when | The AI/ML training services Consumer rApp is able to obtain the training job status. | | -| Exceptions | n/a | | -| Post Conditions | The training job status is known to the AI/ML training services Consumer rApp. | | -| Traceability | REQ-R1-AI/ML-training-FUN2 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "AI/ML training services \n Consumer rApp" as con - participant "AI/ML training services \n Producer rApp" as aif - endbox - - box "Non-anchored functions \n in SMO/Non-RT RIC FWK" #cadetBlue - participant "SME functions" as sme - endbox -endbox - -autonumber -con -> aif: Query training job status request (rApp id, training id) -activate aif -aif <-> sme: <> Check authorization in \n collaboration with SME functions -aif --> aif: Validate -con <- aif: Query training job status response (training job status) - -``` - -``` -deactivate aif -@enduml -``` - -![Sequence diagram for 'Query AI/ML training job status' use case. The diagram shows interactions between AI/ML training services Consumer rApp, AI/ML training services Producer rApp, and SME functions within the Non-RT RIC and Non-anchored functions in SMO/Non-RT RIC FWK.](536768a30136cd5c2d57f46c25d1d804_img.jpg) - -``` - -sequenceDiagram - participant Consumer rApp as AI/ML training services Consumer rApp - participant Producer rApp as AI/ML training services Producer rApp - participant SME as SME functions - - Note right of Producer rApp: Non-anchored functions in SMO/Non-RT RIC FWK - - Consumer rApp->>Producer rApp: 1 Query training job status request (rApp id, training id) - Producer rApp->>SME: 2 «R1» Check authorization in collaboration with SME functions - SME-->>Producer rApp: 3 Validate - Producer rApp->>Consumer rApp: 4 Query training job status response (training job status) - -``` - -Sequence diagram for 'Query AI/ML training job status' use case. The diagram shows interactions between AI/ML training services Consumer rApp, AI/ML training services Producer rApp, and SME functions within the Non-RT RIC and Non-anchored functions in SMO/Non-RT RIC FWK. - -Figure 11.4.4.2-1: Query AI/ML training job status use case flow diagram. - -### 11.4.4.3 Cancel AI/ML training. - -Table 11.4.4.3-1: Cancel AI/ML training use case. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The AI/ML training services Consumer rApp cancels training of an AI/ML model. | | -| Actors and Roles |
  • AI/ML training services Consumer rApp in the role of Service Consumer.
  • AI/ML training service Producer rApp in the role of Service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • The AI/ML training services Consumer rApp is deployed, authenticated, and authorized to consume AI/ML training services.
  • The AI/ML training services Producer rApp is deployed, authenticated, and authorized to produce AI/ML training services.
| | -| Begins when | The AI/ML training services Consumer rApp determines to cancel the training of an AI/ML model. | | -| Step 1 (M) | The AI/ML training services Consumer rApp cancels the training by providing rAppId and training job identifier. | | -| Step 2 (M) | The AI/ML training service Producer rApp checks with SME functions whether the AI/ML training services Consumer rApp is authorized to cancel the training. | | -| Step 3 (M) | The AI/ML training service Producer rApp validates the request. | | -| Step 4 (M) | The AI/ML training service Producer rApp stops the training job. | | -| Step 5 (M) | The AI/ML training service Producer rApp responds to the AI/ML training services Consumer rApp. | | -| Ends when | The AI/ML training service Producer rApp is able to cancel training of an AI/ML model. | | -| Exceptions | n/a | | -| Post Conditions | The training is cancelled, and the training job is terminated. | | -| Traceability | REQ-R1-AI/ML-training-FUN1 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "AI/ML training services \n Consumer rApp" as con - participant "AI/ML training services \n Producer rApp" as aif - endbox - - box "Non-anchored functions \n in SMO/Non-RT RIC FWK" #cadetBlue - participant "SME functions" as sme - endbox -endbox - -autonumber -con -> aif: Cancel training request \n (rApp id, training job id.) -activate aif -aif <-> sme: <> Check authorization in \n collaboration with SME functions -aif --> aif: Validate -aif --> aif: Stop training job -con <- aif: Cancel training response -deactivate aif -@enduml - -``` - -![Sequence diagram for Cancel AI/ML training use case flow. The diagram is titled 'Non-RT RIC' and shows interactions between 'AI/ML training services Consumer rApp', 'AI/ML training services Producer rApp', and 'SME functions' (located within 'Non-anchored functions in SMO/Non-RT RIC FWK'). The sequence of messages is: 1. Consumer rApp sends 'Cancel training request (rApp id, training job id.)' to Producer rApp. 2. Producer rApp sends '«R1» Check authorization in collaboration with SME functions' to SME functions. 3. SME functions send 'Validate' (self-call) to Producer rApp. 4. SME functions send 'Stop training job' (self-call) to Producer rApp. 5. Producer rApp sends 'Cancel training response' back to Consumer rApp.](245166735676c675f98f535bc4c6f0a1_img.jpg) - -``` - -sequenceDiagram - participant Consumer rApp as AI/ML training services Consumer rApp - participant Producer rApp as AI/ML training services Producer rApp - participant SME functions as SME functions - - Note right of Producer rApp: Non-anchored functions in SMO/Non-RT RIC FWK - - Consumer rApp->>Producer rApp: 1 Cancel training request (rApp id, training job id.) - activate Producer rApp - Producer rApp->>SME functions: 2 «R1» Check authorization in collaboration with SME functions - activate SME functions - SME functions-->>Producer rApp: 3 Validate - activate Producer rApp - Producer rApp-->>Producer rApp: 4 Stop training job - deactivate Producer rApp - deactivate SME functions - Producer rApp-->>Consumer rApp: 5 Cancel training response - deactivate Producer rApp - -``` - -Sequence diagram for Cancel AI/ML training use case flow. The diagram is titled 'Non-RT RIC' and shows interactions between 'AI/ML training services Consumer rApp', 'AI/ML training services Producer rApp', and 'SME functions' (located within 'Non-anchored functions in SMO/Non-RT RIC FWK'). The sequence of messages is: 1. Consumer rApp sends 'Cancel training request (rApp id, training job id.)' to Producer rApp. 2. Producer rApp sends '«R1» Check authorization in collaboration with SME functions' to SME functions. 3. SME functions send 'Validate' (self-call) to Producer rApp. 4. SME functions send 'Stop training job' (self-call) to Producer rApp. 5. Producer rApp sends 'Cancel training response' back to Consumer rApp. - -Figure 11.4.4.3-1: Cancel AI/ML training use case flow diagram. - -11.4.4.4 Notify AI/ML training job status change. - -Table 11.4.4.4-1: Notify AI/ML training job status change use case. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The AI/ML training service Producer notifies the AI/ML training services Consumer rApp about the training job status change of a created training job. | | -| Actors and Roles |
  • AI/ML training services Consumer rApp in the role of Service Consumer.
  • AI/ML training service Producer rApp in the role of Service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • The AI/ML training services Consumer rApp is deployed, authenticated, and authorized to consume AI/ML training services.
  • The AI/ML training services Consumer rApp had provided a notification URI to the AI/ML training services Producer rApp.
  • The AI/ML training services Producer rApp is deployed, authenticated, and authorized to produce AI/ML training services.
| | -| Begins when | The AI/ML training service Producer determines the need to notify training job status change to the AI/ML training services Consumer rApp. | | -| Step 1 (M) | The AI/ML training service Producer notifies the training job status change to AI/ML training services Consumer rApp. | | -| Ends when | The AI/ML training services Consumer rApp is notified about the updated training job status. | | -| Exceptions | n/a | | -| Post Conditions | The updated training job status is known to the AI/ML training services Consumer rApp. | | -| Traceability | REQ-R1-AI/ML-training-FUN3 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent - -box "Non-RT RIC" #whitesmoke - participant "AI/ML training services \n Consumer rApp" as con - participant "AI/ML training services \n Producer rApp" as aif -endbox -autonumber -con <- aif: Notify training job status change \n (training job id, training job status, model id) -@enduml - -``` - -![Figure 11.4.4.4-1: Notify AI/ML training job status change use case flow diagram. The diagram shows a 'Non-RT RIC' containing four components: 'AI/ML training services Consumer rApp' (top-left), 'AI/ML training services Producer rApp' (top-right), 'AI/ML training services Consumer rApp' (bottom-left), and 'AI/ML training services Producer rApp' (bottom-right). A message labeled '1 Notify training job status change (training job id, training job status, model id)' is shown with an arrow pointing from the top-right Producer rApp to the bottom-left Consumer rApp.](24a5d31d8d81bf0e4fe402416b8b2f49_img.jpg) - -Figure 11.4.4.4-1: Notify AI/ML training job status change use case flow diagram. The diagram shows a 'Non-RT RIC' containing four components: 'AI/ML training services Consumer rApp' (top-left), 'AI/ML training services Producer rApp' (top-right), 'AI/ML training services Consumer rApp' (bottom-left), and 'AI/ML training services Producer rApp' (bottom-right). A message labeled '1 Notify training job status change (training job id, training job status, model id)' is shown with an arrow pointing from the top-right Producer rApp to the bottom-left Consumer rApp. - -**Figure 11.4.4.4-1: Notify AI/ML training job status change use case flow diagram.** - -## 11.4.5 Required data - -For requesting training, the AI/ML training services Consumer rApp needs to provide its rAppId, information for training (e.g., information about training dataset, model identifier, training criteria.), and optionally a notification URI to receive notification about training job status change. If the AI/ML training service Producer rApp accepts the training request, it assigns a training job identifier for the created training job. - -For querying training job status, the AI/ML training services Consumer rApp needs to provide its rAppId and the training job identifier. The AI/ML training service Producer rApp responses with the status of the training job identified by the training job identifier. - -For cancelling training, the AI/ML training services Consumer rApp needs to provide its rAppId and the training job identifier. - -For notifying training job status change, the AI/ML training service Producer rApp provides the training job status, the training job identifier, and optionally model identifier. - -## 11.5 AI/ML workflow-related use case 5: AI/ML model Retrieve. - -### 11.5.1 Overview - -This use case defines how an rApp retrieves model location details as a consumer of registered AI/ML model(s). - -### 11.5.2 Background and goal of the use case. - -The AI/ML model retrieve procedures are defined as part of the AI/ML workflow services as part of AI/ML workflow services in R1GAP [1]. - -### 11.5.3 Entities/resources involved in the use case. - -- 1) AI/ML workflow functions - - a) support model management and exposure functionality to allow an rApp to retrieve the location details of AI/ML model(s). -- 2) rApp - - a) initiates the procedure to retrieve the location details of AI/ML model(s). - -## 11.5.4 Solutions - -### 11.5.4.1 Retrieve model. - -**Table 11.5.4.1-1: Model retrieve.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp retrieves AI/ML model(s). | | -| Actors and Roles |
  • – rApp in the role of Model retrieve service Consumer.
  • – AI/ML workflow functions in the role of Model retrieve service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the AI/ML Model retrieve service.
  • – The rApp has the model identifier(s).
| | -| Begins when | The rApp determines the need to retrieve the AI/ML model. | | -| Step 1 (M) | The rApp requests the AI/ML workflow functions to retrieve an AI/ML model by providing the rApp ID, and the AI/ML model identifier(s). | | -| Step 2 (M) | The AI/ML workflow functions check with SME functions whether the rApp is authorized to retrieve AI/ML models. | | -| Step 3 (M) | The AI/ML workflow functions fetch the model location details of registered AI/ML model(s). | | -| Step 4(M) | The AI/ML workflow functions respond to rApp AI/ML model identifier, model location details. | | -| Ends when | The rApp has the location details. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-AIML-Retrievemodel-FUN1 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent -autonumber - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "Model Consumer rApp" as rApp - endbox - - box " Non-anchored functions in SMO/Non-RT RIC Framework " #cadetBlue - participant "AI/ML workflow functions" as ML - endbox -endbox - -group Model Consumer rApp model retrieve -rApp -> ML: <> Retrieve AI/ML model information request \n (rAppId, AI/ML model identifier(s)) -ML -> ML: AuthZ -ML -> ML: fetch the model location details \n of registered AI/ML model(s) -ML -> rApp: <> Retrieve AI/ML model information response \n (AI/ML model identifier(s), model location details) -end -@enduml - -``` - -![Sequence diagram for 'Retrieve model' use case. The diagram shows a 'Model Consumer rApp' interacting with 'AI/ML workflow functions' within a 'Non-RT RIC'. The interaction is titled 'Model Consumer rApp model retrieve'. The sequence of messages is: 1. Retrieve AI/ML model information request (rAppId, AI/ML model identifier(s)) from rApp to workflow functions; 2. AuthZ response from workflow functions; 3. fetch the model location details of registered AI/ML model(s) response from workflow functions; 4. Retrieve AI/ML model information response (AI/ML model identifier(s), model location details) from workflow functions back to rApp.](1e95fc0be1c9782d078a26fb32facddd_img.jpg) - -``` - -sequenceDiagram - participant rApp as Model Consumer rApp - participant RIC as Non-RT RIC - subgraph RIC [Non-RT RIC] - participant AW as AI/ML workflow functions - end - Note right of rApp: Model Consumer rApp model retrieve - rApp->>AW: 1 «R1» Retrieve AI/ML model information request (rAppId, AI/ML model identifier(s)) - AW-->>AW: 2 AuthZ - AW-->>AW: 3 fetch the model location details of registered AI/ML model(s) - AW-->>rApp: 4 «R1» Retrieve AI/ML model information response (AI/ML model identifier(s), model location details) - -``` - -Sequence diagram for 'Retrieve model' use case. The diagram shows a 'Model Consumer rApp' interacting with 'AI/ML workflow functions' within a 'Non-RT RIC'. The interaction is titled 'Model Consumer rApp model retrieve'. The sequence of messages is: 1. Retrieve AI/ML model information request (rAppId, AI/ML model identifier(s)) from rApp to workflow functions; 2. AuthZ response from workflow functions; 3. fetch the model location details of registered AI/ML model(s) response from workflow functions; 4. Retrieve AI/ML model information response (AI/ML model identifier(s), model location details) from workflow functions back to rApp. - -Figure 11.5.4.1-1: Retrieve model use case flow diagram. - -## 11.5.5 Required data - -For Retrieve AI/ML model information request, the rApp provides the rAppId, and model- identifier(s). - -For Retrieve AI/ML model information response, the AI/ML workflow functions provide model identifier(s) and model location details. - -# 11.6 AI/ML workflow-related use case 6: AI/ML model deployment - -## 11.6.1 Overview - -This use case defines how an rApp requests the deployment of an AI/ML model as an AI/ML model Consumer. - -## 11.6.2 Background and goal of the use case. - -The AI/ML model deployment procedures are defined as part of the AI/ML workflow services as part of AI/ML workflow services in R1GAP [1]. - -## 11.6.3 Entities/resources involved in the use case. - -- 1) AI/ML workflow functions - - a) support model management and exposure functionality to allow an rApp to request the deployment of an AI/ML model. -- 2) rApp - - a) initiates the procedure to deploy the updated artifact version of an AI/ML model being consumed by the rApp. - -## 11.6.4 Solutions - -### 11.6.4.1 Retrieve model. - -**Table 11.6.4.1-1: Model deployment.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp requests to deploy an AI/ML model being consumed by the rApp. | | -| Actors and Roles |
  • – rApp in the role of Model deployment service Consumer.
  • – AI/ML workflow functions in the role of Model deployment service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the Model deployment service.
  • – The rApp is authorized to access the AI/ML model referenced in the deployment request.
  • – The AI/ML model referenced in the deployment request is being consumed by the rApp requesting the deployment.
| | -| Begins when | The rApp determines the need to deployment an AI/ML model. | | -| Step 1 (M) | The rApp requests the AI/ML workflow functions to deploy an AI/ML model by providing the rAppId, the AI/ML model identifier and the target deployment location of the AI/ML model. | | -| Step 2 (M) | The AI/ML workflow functions authorize the rApps deployment request. | | -| Step 3 (M) |

The AI/ML workflow functions send the model deployment response to the rApp.

The AI/ML workflow functions trigger the rApp deployment procedure.

NOTE: The rApp deployment procedure is not specified in this specification.

| | -| Step 4 (M) | The AI/ML workflow functions notify the rApp the model deployment status. | | -| Ends when | n/a | | -| Exceptions | n/a | | -| Post Conditions | The model deployment status is known to the rApp, | | -| Traceability | REQ-R1-AIML-Deploymodel-FUN1 | | - -``` - -@startuml!pragma teoz trueskinparam ParticipantPadding 5skinparam BoxPadding 10skinparam -defaultFontSize 12skinparam lifelineStrategy solid skinparam SequenceGroupBackgroundColor -Transparentskinparam SequenceGroupBodyBackgroundColor Transparentautonumber -box "Non-RT RIC" #whitesmoke box #ivory participant "Model Consumer rApp" as rApp endbox -box " Non-anchored functions in SMO/Non-RT RIC Framework " #cadetBlue participant -"AI/ML workflow functions" as ML endboxendbox - -group Model deploymentrApp -> ML : <> Model deployment request (rAppId, AI/ML Model -Identifier,\n the target deployment location of the AI/ML model)ML -> ML: AuthZnote right -Check authorization in collaboration with SME functionsend note -ML -> rApp : <> Model deployment response -note over ML The rApp deployment procedure is not specified in this specification end note -ML -> rApp : <> Model deployment status notification (AI/ML model identifier, deployment -status) - -``` - -![Sequence diagram for Model deployment use case flow. Lifelines: Model Consumer rApp and Non-RT RIC (containing AI/ML workflow functions). The sequence shows: 1. Model deployment request from rApp to RIC; 2. Authorization check by RIC; 3. Model deployment response from RIC to rApp; 4. Model deployment status notification from RIC to rApp. A note indicates the rApp deployment procedure is not specified in this specification.](4c63a0e17b54c7e61d512c276932114c_img.jpg) - -``` - -sequenceDiagram - participant rApp as Model Consumer rApp - participant RIC as Non-RT RIC (AI/ML workflow functions) - Note right of RIC: The rApp deployment procedure is not specified in this specification - rApp->>RIC: 1 «R1» Model deployment request (rAppID, AI/ML Model Identifier, the target deployment location of the AI/ML model) - RIC->>RIC: 2 AuthZ Check authorization in collaboration with SME functions - RIC-->>rApp: 3 «R1» Model deployment response - RIC-->>rApp: 4 «R1» Model deployment status notification (AI/ML model identifier, deployment status) - -``` - -Sequence diagram for Model deployment use case flow. Lifelines: Model Consumer rApp and Non-RT RIC (containing AI/ML workflow functions). The sequence shows: 1. Model deployment request from rApp to RIC; 2. Authorization check by RIC; 3. Model deployment response from RIC to rApp; 4. Model deployment status notification from RIC to rApp. A note indicates the rApp deployment procedure is not specified in this specification. - -Figure 11.6.4.1-1: Model deployment use case flow diagram. - -### 11.6.5 Required data - -For a model deployment request, the rApp provides the rAppId, AI/ML model identifier, and the target deployment location of the AI/ML model. - -For a model deployment status notification, AI/ML workflow functions provide AI/ML model identifier and the deployment status. - -## 11.7 AI/ML workflow-related use case 7: AI/ML model performance monitoring – AI/ML workflow functions consuming performance monitoring service - -### 11.7.1 Overview - -This use case enables the AI/ML workflow functions as AI/ML model performance monitoring service consumer to subscribe to AI/ML model performance and receive notifications of AI/ML model performance information. - -### 11.7.2 Background and goal of the use case - -An AI/ML model performance monitoring service consumer can subscribe to AI/ML model performance and receive notifications of AI/ML model performance information. - -### 11.7.3 Entities/resources involved in the use case - -- 1) rApp as AI/ML model performance monitoring service Producer - - a. supports the functionality to allow an authorized consumer to subscribe to, and receive notifications of, AI/ML model performance information. -- 2) AI/ML workflow functions as AI/ML model performance monitoring service Consumer - - a. support the functionality to initiate the procedure to subscribe to, and receive notifications of, AI/ML model performance information. - -## 11.7.4 Solutions - -### 11.7.4.1 Subscribe AI/ML model performance. - -**Table 11.7.4.1-1: Subscribe AI/ML model performance.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The AI/ML workflow functions subscribe to AI/ML model performance. | | -| Actors and Roles |
  • – rApp in the role of AI/ML model performance monitoring service Producer.
  • – AI/ML workflow functions in the role of AI/ML model performance monitoring service Consumer.
| | -| Assumptions | The supported AI/ML model performance information are part of the AI/ML model registration information. | | -| Preconditions | The rApp has deployed a registered AI/ML model. | | -| Begins when | The AI/ML workflow functions determine the need to monitor the AI/ML model performance of a deployed AI/ML model. | | -| Step 1 (M) | The AI/ML workflow functions subscribe to AI/ML model performance with AI/ML model identifier, required AI/ML model performance information (optional), periodicity (optional), event notification conditions (optional), and notification URI as parameters. | | -| Step 2 (M) | The rApp validates the subscription request. | | -| Step 3 (M) | The rApp creates the subscription. | | -| Step 4 (M) | The rApp responds to the request with subscription ID as a parameter. | | -| Ends when | The subscription is created, and AI/ML workflow functions have the subscription ID. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-AIML-Performer-FUN1 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke -box #ivory -participant rApp as rApp -end box -box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue -participant "AI/ML Workflow functions" as AIML -end box - -AIML -> rApp : <> Subscribe AI/ML model performance request (AI/ML model identifier, \n -AI/ML model performance information (optional), Periodicity (optional),\n -EventNotificationConditions (optional), Notification URI) -rApp --> rApp : Validate request -rApp --> rApp : Create subscription -rApp -> AIML: <> Subscribe AI/ML model performance response (Subscription ID) - -@enduml - -``` - -![Sequence diagram titled 'Non-RT RIC' showing the interaction between an rApp and AI/ML Workflow functions. The sequence consists of four steps: 1. rApp sends a 'Subscribe AI/ML model performance request' to the functions. 2. The functions validate the request. 3. The functions create a subscription. 4. The functions send a 'Subscribe AI/ML model performance response' with a Subscription ID back to the rApp.](e2245b4865907ad1259fd155f4beb6cf_img.jpg) - -``` -sequenceDiagram - participant rApp - participant AI/ML Workflow functions - Note right of AI/ML Workflow functions: Non-anchored functions in SMO/Non-RT RIC Framework - rApp->>AI/ML Workflow functions: 1 «R1» Subscribe AI/ML model performance request (AI/ML model identifier, AI/ML model performance information (optional), Periodicity (optional), EventNotificationConditions (optional), Notification URI) - AI/ML Workflow functions-->>rApp: 2 Validate request - AI/ML Workflow functions-->>rApp: 3 Create subscription - AI/ML Workflow functions-->>rApp: 4 «R1» Subscribe AI/ML model performance response (Subscription ID) -``` - -Sequence diagram titled 'Non-RT RIC' showing the interaction between an rApp and AI/ML Workflow functions. The sequence consists of four steps: 1. rApp sends a 'Subscribe AI/ML model performance request' to the functions. 2. The functions validate the request. 3. The functions create a subscription. 4. The functions send a 'Subscribe AI/ML model performance response' with a Subscription ID back to the rApp. - -Figure 11.7.4.1-1: Subscribe AI/ML model performance use case flow diagram. - -11.7.4.2 Notify AI/ML model performance. - -Table 11.7.4.2-1: Notify AI/ML model performance. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp notifies subscribed consumers of AI/ML model performance information. | | -| Actors and Roles |
  • – rApp in the role of AI/ML model performance monitoring service Producer.
  • – AI/ML workflow functions in the role of AI/ML model performance monitoring service Consumer.
| | -| Assumptions | The supported AI/ML model performance information are part of the AI/ML model registration information. | | -| Preconditions |
  • – The rApp has deployed a registered AI/ML model.
  • – The AI/ML workflow functions subscribed to AI/ML model performance.
| | -| Begins when | The rApp determines the need to notify subscribed consumers of the performance information of a deployed AI/ML model. | | -| Alternative procedure | In the case of event-based notifications, the rApp notifies subscribed consumers of the AI/ML model performance information every time an event is triggered in Step 1. | | -| Step 1 (M) | The rApp checks the occurrence of the notification events specified in the subscription request. | | -| Step 2 (M) | The rApp notifies the subscribed consumers of the AI/ML model performance information providing the requested AI/ML model performance information and the event triggered as parameters. If no AI/ML model performance information is specified in the subscription request, all supported AI/ML model performance information is provided. | | -| Alternative procedure | In the case of periodic notifications, the rApp notifies subscribed consumers of the AI/ML model performance information as per the notification periodicity specified in the subscription. | | -| Step 3 (M) | The rApp notifies the subscribed consumers of the AI/ML model performance information providing the requested AI/ML model performance information. If no AI/ML model performance information is specified in the subscription request, all supported AI/ML model performance information is provided. | | -| Ends when | The rApp is able to terminate the subscription or the AI/ML model is no longer deployed. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-AIML-Performer-FUN2 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke -box #ivory -participant "AI/ML model performance monitoring \n service Producer rApp" as rApp -end box -box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue -participant "AI/ML Workflow functions" as AIML -end box - -Loop Periodicity of notifications specified in the subscription request -Alt Event based notifications -rApp --> rApp : Check if specified event is triggered - -``` - -``` - -rApp -> AIML : <> Notify AI/ML model performance (AI/ML model identifier, \n AI/ML -model performance information, EventNotificationType) -else Periodical notifications - rApp -> AIML : <> Notify AI/ML model performance (AI/ML model identifier, \n -AI/ML model performance information) -end -end - -@enduml - -``` - -![Sequence diagram titled 'Non-RT RIC' showing the interaction between an 'AI/ML model performance monitoring service producer rApp' and 'AI/ML Workflow functions'. The diagram includes a loop for 'Periodicity of notifications specified in the subscription request' containing an 'alt' block for 'Event based notifications' (steps 1 and 2) and 'Periodical notifications' (step 3).](f4e5a86da5c799372a7c1ea2397dedb7_img.jpg) - -``` - -sequenceDiagram - participant rApp as AI/ML model performance monitoring service producer rApp - participant AIML as AI/ML Workflow functions - Note right of AIML: Non-anchored functions in SMO/Non-RT RIC Framework - loop Periodicity of notifications specified in the subscription request - alt Event based notifications - Note left of rApp: 1 Check if specified event is triggered - rApp->>AIML: 2 «R1» Notify AI/ML model performance (AI/ML model identifier, AI/ML model performance information, EventNotificationType) - else Periodical notifications - rApp->>AIML: 3 «R1» Notify AI/ML model performance (AI/ML model identifier, AI/ML model performance information) - end - end - -``` - -Sequence diagram titled 'Non-RT RIC' showing the interaction between an 'AI/ML model performance monitoring service producer rApp' and 'AI/ML Workflow functions'. The diagram includes a loop for 'Periodicity of notifications specified in the subscription request' containing an 'alt' block for 'Event based notifications' (steps 1 and 2) and 'Periodical notifications' (step 3). - -Figure 11.7.4.2-1: Notify AI/ML model performance use case flow diagram. - -## 11.7.5 Required data - -For the Subscribe AI/ML model performance request, the AI/ML workflow functions provide the AI/ML model identifier and notification URI. In the Subscribe AI/ML model performance request, the AI/ML workflow functions optionally provide the required AI/ML model performance information, Notification event conditions upon which the Notify AI/ML model performance is triggered, and periodicity of the notification. - -For the Subscribe AI/ML model performance response, the rApp provides the Subscription ID. - -For the Notify AI/ML model performance, the rApp provides the AI/ML model performance information specified in the Subscribe AI/ML model performance request, as well as the event that triggered the notification if notification event conditions are specified in the Subscribe AI/ML model performance request. If no required AI/ML performance information is specified in the Subscribe AI/ML model performance request, all supported AI/ML model performance information is provided in the Notify AI/ML model performance. - -## 11.8 AI/ML workflow-related use case 8: AI/ML model performance monitoring – rApp consuming performance monitoring service - -### 11.8.1 Overview - -This use case defines how an rApp as AI/ML model performance monitoring service Consumer subscribes to AI/ML model performance and receives notifications of AI/ML model performance information. - -### 11.8.2 Background and goal of the use case - -An AI/ML model performance monitoring service Consumer can subscribe to AI/ML model performance and receive notifications of AI/ML model performance information. - -### 11.8.3 Entities/resources involved in the use case - -- 1) rApp as AI/ML model performance monitoring service Producer - - a. supports the functionality to allow an authorized consumer to subscribe to, and receive notifications of, AI/ML model performance information. -- 2) rApp as AI/ML model performance monitoring service Consumer - - a. supports the functionality to initiate the procedure to subscribe to, and receive notifications of, AI/ML model performance information. - -## 11.8.4 Solutions - -### 11.8.4.1 Subscribe AI/ML model performance. - -**Table 11.8.4.1-1: Subscribe AI/ML model performance.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | rApp subscribes to AI/ML model performance. | | -| Actors and Roles |
  • – rApp in the role of AI/ML model performance monitoring service Producer.
  • – rApp in the role of AI/ML model performance monitoring service Consumer.
| | -| Assumptions | The supported AI/ML model performance information are part of the AI/ML model registration information. | | -| Preconditions | The AI/ML model performance monitoring service producer rApp has deployed a registered AI/ML model. | | -| Begins when | The AI/ML model performance monitoring service Consumer rApp determines the need to monitor the AI/ML model performance of a deployed AI/ML model. | | -| Step 1 (M) | The AI/ML model performance monitoring service Consumer rApp subscribes to AI/ML model performance with AI/ML model identifier, required AI/ML model performance information (optional), periodicity (optional), event notification conditions (optional), and notification URI as parameters. | | -| Step 2 (M) | The AI/ML model performance monitoring service Producer rApp checks with SME functions whether the AI/ML model performance monitoring service Consumer is authorized to subscribe to AI/ML model performance. | | -| Step 3 (M) | The AI/ML model performance monitoring service Producer rApp validates the subscription request. | | -| Step 4 (M) | The rApp creates the subscription. | | -| Step 5 (M) | The rApp responds to the request with subscription ID as a parameter. | | -| Ends when | The subscription is created, and The AI/ML model performance monitoring service Consumer rApp has the subscription ID. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-AIML-Performer-FUN1 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke -box #ivory -participant "The AI/ML model performance monitoring \n service Producer rApp" as rApp -participant " The AI/ML model performance monitoring \n service Consumer rApp " as AIML -end box -box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue -participant "SME functions" as SME -end box - -AIML -> rApp : Subscribe AI/ML model performance request (AI/ML model identifier, \n AI/ML -model performance information (optional), Periodicity (optional),\n -EventNotificationConditions (optional), Notification URI) -rApp --> SME : <> AuthZ -note right -Check authorization in -collaboration with SME functions -end note - -``` - -``` - -rApp --> rApp : Validate request -rApp --> rApp : Create subscription -rApp -> AIML: Subscribe AI/ML model performance response (Subscription ID) - -@enduml - -``` - -![Sequence diagram titled 'Non-RT RIC' showing the interaction between 'The AI/ML model performance monitoring service producer rApp' and 'The AI/ML model performance monitoring service consumer rApp'. The sequence includes: 1. Subscribe AI/ML model performance request (AI/ML model identifier, AI/ML model performance information (optional), Periodicity (optional), EventNotificationConditions (optional), Notification URI); 2. «R1» AuthZ (linked to 'Check authorization in collaboration with SME functions' in the 'Non-anchored functions in SMO/Non-RT RIC Framework' box); 3. Validate request; 4. Create subscription; 5. Subscribe AI/ML model performance response (Subscription ID).](b02ba0b73e95416eb547976f6145b169_img.jpg) - -Sequence diagram titled 'Non-RT RIC' showing the interaction between 'The AI/ML model performance monitoring service producer rApp' and 'The AI/ML model performance monitoring service consumer rApp'. The sequence includes: 1. Subscribe AI/ML model performance request (AI/ML model identifier, AI/ML model performance information (optional), Periodicity (optional), EventNotificationConditions (optional), Notification URI); 2. «R1» AuthZ (linked to 'Check authorization in collaboration with SME functions' in the 'Non-anchored functions in SMO/Non-RT RIC Framework' box); 3. Validate request; 4. Create subscription; 5. Subscribe AI/ML model performance response (Subscription ID). - -Figure 11.8.4.1-1: Subscribe AI/ML model performance use case flow diagram. - -11.8.4.2 Notify AI/ML model performance. - -Table 11.8.4.2-1: Notify AI/ML model performance. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp notifies subscribed consumers of AI/ML model performance information. | | -| Actors and Roles |
  • – rApp in the role of AI/ML model performance monitoring service Producer.
  • – rApp in the role of AI/ML model performance monitoring service Consumer.
| | -| Assumptions | The supported AI/ML model performance information are part of the AI/ML model registration information. | | -| Preconditions |
  • – The rApp has deployed a registered AI/ML model.
  • – The AI/ML model performance monitoring service consumer rApp subscribed to AI/ML model performance.
| | -| Begins when | The rApp determines the need to notify subscribed consumers of the performance information of a deployed AI/ML model. | | -| Alternative procedure | In the case of event-based notifications, the rApp notifies subscribed consumers of the AI/ML model performance information every time an event is triggered in Step 1. | | -| Step 1 (M) | The rApp checks the occurrence of the notification events specified in the subscription request. | | -| Step 2 (M) | The rApp notifies the subscribed consumers of the AI/ML model performance information providing the requested AI/ML model performance information and the event triggered as parameters. If no AI/ML model performance information is specified in the subscription request, all supported AI/ML model performance information is provided. | | -| Alternative procedure | In the case of periodic notifications, the rApp notifies subscribed consumers of the AI/ML model performance information as per the notification periodicity specified in the subscription. | | -| Step 3 (M) | The rApp notifies the subscribed consumers of the AI/ML model performance information providing the requested AI/ML model performance information. If no AI/ML model performance information is specified in the subscription request, all supported AI/ML model performance information is provided. | | -| Ends when | The rApp is able to terminate the subscription or the AI/ML model is no longer deployed. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-AIML-Performer-FUN2 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke -box #ivory -participant "AI/ML model performance monitoring \n service Producer rApp" as rApp -participant " The AI/ML model performance monitoring \n service Consumer rApp " as AIML - -end box - -Loop Periodicity of notifications specified in the subscription request -Alt Event based notifications -rApp --> rApp : Check if specified event is triggered -rApp -> AIML : Notify AI/ML model performance (AI/ML model identifier, \n AI/ML model performance information, EventNotificationType) - -``` - -``` - -else Periodical notifications - rApp -> AI/ML : Notify AI/ML model performance (AI/ML model identifier, \n AI/ML -model performance information) -end -end - -@enduml - -``` - -![Sequence diagram titled 'Non-RT RIC' showing the interaction between an AI/ML model performance monitoring service producer rApp and a service consumer rApp. The diagram features a 'loop' for notification periodicity and an 'alt' block for event-based notifications. Step 1: Check if specified event is triggered. Step 2: Notify AI/ML model performance (AI/ML model identifier, AI/ML model performance information, EventNotificationType). Step 3: Notify AI/ML model performance (AI/ML model identifier, AI/ML model performance information).](1cd38e4f2ffcae2871964fa6313a9a27_img.jpg) - -``` - -sequenceDiagram - participant Producer as AI/ML model performance monitoring service producer rApp - participant Consumer as The AI/ML model performance monitoring service consumer rApp - Note right of Producer: [Periodicity of notifications specified in the subscription request] - loop Periodicity of notifications specified in the subscription request - alt Event based notifications - Note left of Producer: 1 Check if specified event is triggered - Producer->>Consumer: 2 Notify AI/ML model performance (AI/ML model identifier, AI/ML model performance information, EventNotificationType) - else Periodical notifications - Note left of Producer: 3 Notify AI/ML model performance (AI/ML model identifier, AI/ML model performance information) - Producer->>Consumer: - end - end - -``` - -Sequence diagram titled 'Non-RT RIC' showing the interaction between an AI/ML model performance monitoring service producer rApp and a service consumer rApp. The diagram features a 'loop' for notification periodicity and an 'alt' block for event-based notifications. Step 1: Check if specified event is triggered. Step 2: Notify AI/ML model performance (AI/ML model identifier, AI/ML model performance information, EventNotificationType). Step 3: Notify AI/ML model performance (AI/ML model identifier, AI/ML model performance information). - -Figure 11.8.4.2-1: Notify AI/ML model performance use case flow diagram. - -## 11.8.5 Required data - -For the Subscribe AI/ML model performance request, the AI/ML model performance monitoring service Consumer rApp provides the AI/ML model identifier and notification URI. In the Subscribe AI/ML model performance request, the AI/ML model performance monitoring service Consumer rApp optionally provides the required AI/ML model performance information, Notification event conditions upon which the Notify AI/ML model performance is triggered, and periodicity of the notification. - -For the Subscribe AI/ML model performance response, the AI/ML model performance monitoring service Producer rApp provides the Subscription ID. - -For the Notify AI/ML model performance, the AI/ML model performance monitoring service producer rApp provides the AI/ML model performance information specified in the Subscribe AI/ML model performance request, as well as the event that triggered the notification if notification event conditions are specified in the Subscribe AI/ML model performance request. If no required AI/ML performance information is specified in the Subscribe AI/ML model performance request, all supported AI/ML model performance information is provided in the Notify AI/ML model performance. - -## 11.9 AI/ML workflow-related use case 9: AI/ML model training capability registration and deregistration - -### 11.9.1 Overview - -This use case defines how an rApp registers and deregisters AI/ML model training capability. - -## 11.9.2 Background and goal of the use case - -The register AI/ML model training capability and unregister AI/ML model training capability are optional procedures defined as part of the AI/ML model training capability registration service in R1GAP [1]. - -## 11.9.3 Entities/resources involved in the use case - -- 1) AI/ML workflow functions - - a) support functionality to allow an rApp to register and unregister AI/ML model training capability, - - b) support validation of AI/ML model training capability information. -- 2) rApp: - - a) initiates the procedure to register and unregister AI/ML model training capability. - -## 11.9.4 Solutions - -### 11.9.4.1 Register AI/ML model training capability. - -**Table 11.9.4.1-1: AI/ML Model training capability registration.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp registers an AI/ML model training capability. | | -| Actors and Roles |
  • – rApp in the role of AI/ML model management and exposure service Consumer.
  • – AI/ML workflow functions in the role of AI/ML model management and exposure service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the AI/ML model management and exposure services.
  • – The rApp is registered as producer of AI/ML model training with SME, it intends to register its training capability in AI/ML workflow functions.
| | -| Begins when | The rApp determines the need to register an AI/ML model training capability. | | -| Step 1 (M) | The rApp requests the AI/ML workflow functions to register an AI/ML model training capability by providing the rAppId and AI/ML model training capability information. | | -| Step 2 (M) | The AI/ML workflow functions check with SME functions whether the rApp is registered as producer of AI/ML model training service. | | -| Step 3(M) | The AI/ML workflow functions register the rApp's AI/ML model training capability. | | -| Step 4(M) | The AI/ML workflow functions respond to rApp with successful AI/ML model training capability registration along with AI/ML model training capability registration ID. | | -| Ends when | The rApp was able to register an AI/ML model training capability. | | -| Exceptions | n/a | | -| Post Conditions | The AI/ML model training capability is registered. The rApp can query, update or delete the AI/ML model training capability registration. | | -| Traceability | REQ-R1-AI/ML-Registertraincap -FUN1 | | - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent -autonumber -``` - -``` - -box "Non-RT RIC" #whitesmoke - box " Non-anchored functions in SMO/Non-RT RIC Framework " #cadetBlue - participant "AI/ML workflow functions" as ML - endbox - - box #ivory - participant "Training service Producer rApp" as src - endbox -endbox - -src -> ML: <> Register AI/ML model training capability request (rAppId, AI/ML model training capability information) -ML -> ML: Authz -ML -> ML: register AI/ML model training capability -ML -> src: <> Register AI/ML model training capability response (AI/ML model training capability registration ID) -@enduml - -``` - -![Sequence diagram for Register AI/ML model training capability. Lifelines: AI/ML workflow functions (ML) and Training service Producer rApp (src). The sequence shows: 1. src sends a Register AI/ML model training capability request to ML; 2. ML performs an internal Authz; 3. ML performs an internal register AI/ML model training capability; 4. ML sends a Register AI/ML model training capability response back to src.](b0384c8e0ff826a8116ab2ff67dadc43_img.jpg) - -Sequence diagram for Register AI/ML model training capability. Lifelines: AI/ML workflow functions (ML) and Training service Producer rApp (src). The sequence shows: 1. src sends a Register AI/ML model training capability request to ML; 2. ML performs an internal Authz; 3. ML performs an internal register AI/ML model training capability; 4. ML sends a Register AI/ML model training capability response back to src. - -Figure 11.9.4.1-1: Register AI/ML model training capability use case flow diagram. - -### 11.9.4.2 Deregister AI/ML model training capability - -Table 11.9.4.2-1: AI/ML Model training capability deregistration - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | The rApp deregisters an AI/ML model training capability. | | -| Actors and Roles |
  • rApp in the role of AI/ML model management and exposure service Consumer.
  • AI/ML workflow functions in the role of AI/ML model management and exposure service Producer.
| | -| Assumptions | The rApp is not producing any AI/ML model training capability. | | -| Preconditions |
  • The rApp has registered an AI/ML model training capability.
  • The rApp is authorized to access the AI/ML model management and exposure services.
| | -| Begins when | The rApp determines the need to deregister an AI/ML model training capability that it no longer intends to produce. | | -| Step 1 (M) | The rApp requests AI/ML workflow functions to deregister an AI/ML model training capability by providing rAppId and AI/ML model training capability registration ID. | | -| Step 2 (M) | The AI/ML workflow functions remove the registration of the rApp as producer of AI/ML model training capability. | | -| Step 3 (M) | The AI/ML workflow functions respond to the rApp with successful deregistration. | | -| Ends when | The rApp was able to deregister the AI/ML model training capability. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-AI/ML-Registertraincap -FUN1 | | - -``` - -@startuml -!pragma teoz true - -``` - -``` - -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent -autonumber - -box "Non-RT RIC" #whitesmoke - box " Non-anchored functions in SMO/Non-RT RIC Framework " #cadetBlue - participant "AI/ML workflow functions" as ML - endbox - - box #ivory - participant "Training service Producer rApp" as src - endbox -endbox - -src -> ML: <> Deregister AI/ML model training capability (rAppId, AI/ML model training -capability registration ID) -ML -> ML: Deregister AI/ML model training capability -ML -> src: <> Deregister AI/ML model training capability response -@enduml - -``` - -![UML Sequence diagram titled 'Non-RT RIC' showing the interaction for 'Deregister AI/ML model training capability'. Lifelines include 'AI/ML workflow functions' (ML) and 'Training service Producer rApp' (src). The sequence is: 1. src sends a request to ML; 2. ML performs an internal self-call; 3. ML sends a response back to src.](223792b3652794024244c277cc46394b_img.jpg) - -``` - -sequenceDiagram - participant src as Training service Producer rApp - participant ML as AI/ML workflow functions - Note left of ML: AI/ML workflow functions - Note right of src: Training service Producer rApp - Note right of ML: AI/ML workflow functions - Note right of src: Training service Producer rApp - src->>ML: 1 «R1» Deregister AI/ML model training capability (rAppId, AI/ML model training capability registration ID) - ML->>ML: 2 Deregister AI/ML model training capability - ML->>src: 3 «R1» Deregister AI/ML model training capability response - -``` - -UML Sequence diagram titled 'Non-RT RIC' showing the interaction for 'Deregister AI/ML model training capability'. Lifelines include 'AI/ML workflow functions' (ML) and 'Training service Producer rApp' (src). The sequence is: 1. src sends a request to ML; 2. ML performs an internal self-call; 3. ML sends a response back to src. - -Figure 11.9.4.2-1: Deregister AI/ML model training capability use case flow diagram. - -### 11.9.4.3 Update AI/ML model training capability registration. - -**Table 11.9.4.3-1: Update AI/ML model training capability registration.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp updates the registration of an AI/ML model training capability. | | -| Actors and Roles |
  • – rApp in the role of AI/ML model management and exposure services Consumer.
  • – AI/ML workflow functions in the role of AI/ML model management and exposure services Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the AI/ML model management and exposure services for updating an AI/ML model training capability registration.
  • – The rApp has registered an AI/ML model training capability.
| | -| Begins when | The AI/ML model training service producer rApp determines the need to update the registration of an AI/ML model training capability. | | -| Step 1 (M) | The AI/ML model training service producer rApp requests to update the registration of an AI/ML model training capability by providing rAppId, AI/ML model training capability registration ID, updated model training capability registration information, etc. | | -| Step 2 (M) | The AI/ML workflow functions check whether the rApp is authorized to update the registration. | | -| Step 3 (M) | The AI/ML workflow functions validate the update AI/ML model training capability registration request. | | -| Step 4 (M) | The AI/ML workflow functions update the registration of the AI/ML model training capability. | | -| Step 5 (M) | The AI/ML workflow functions respond to the rApp with successful update AI/ML model training capability registration response. | | -| Ends when | The rApp was able to update the registration of the AI/ML model training capability. | | -| Exceptions | n/a | | -| Post Conditions | The rApp can query, update or delete the AI/ML model training capability registration. | | -| Traceability | REQ-R1-AI/ML-Registertraincap -FUN1 | | - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rApp" as app - endbox - - box "Non-anchored functions \n in SMO/Non-RT RIC FWK" #cadetBlue - participant "AI/ML workflow functions" as aif - endbox -endbox - -autonumber -app -> aif: <> Update model training capability registration request \n (rAppId, AI/ML model training capability registration identifier, \n updated model training capability registration information) -activate aif -aif --> aif: AuthZ -note right -Check authorization in -collaboration with SME functions -``` - -``` - -end note -aif --> aif: Validate -aif --> aif: Update model training capability\n registration information -app <- aif: <> Update model training capability registration response -deactivate aif -@enduml - -``` - -![Sequence diagram titled 'Non-RT RIC' showing the interaction between an rApp and Non-anchored functions in SMO/Non-RT RIC FWK for updating AI/ML model training capability registration. The sequence includes: 1. rApp sends a request to AI/ML workflow functions; 2. AI/ML workflow functions call AuthZ (with a note to check authorization with SME functions); 3. AI/ML workflow functions call Validate; 4. AI/ML workflow functions update registration information; 5. AI/ML workflow functions return a response to the rApp.](2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant AI/ML_workflow_functions as AI/ML workflow functions - Note right of AI/ML_workflow_functions: Check authorization in collaboration with SME functions - rApp->>AI/ML_workflow_functions: 1 «R1» Update model training capability registration request (rAppId, AI/ML model training capability registration identifier, updated model training capability registration information) - AI/ML_workflow_functions-->>AI/ML_workflow_functions: 2 AuthZ - AI/ML_workflow_functions-->>AI/ML_workflow_functions: 3 Validate - AI/ML_workflow_functions-->>AI/ML_workflow_functions: 4 Update model training capability registration information - AI/ML_workflow_functions-->>rApp: 5 «R1» Update model training capability registration response - -``` - -Sequence diagram titled 'Non-RT RIC' showing the interaction between an rApp and Non-anchored functions in SMO/Non-RT RIC FWK for updating AI/ML model training capability registration. The sequence includes: 1. rApp sends a request to AI/ML workflow functions; 2. AI/ML workflow functions call AuthZ (with a note to check authorization with SME functions); 3. AI/ML workflow functions call Validate; 4. AI/ML workflow functions update registration information; 5. AI/ML workflow functions return a response to the rApp. - -Figure 11.9.4.3-1: Update registration of an AI/ML training capability model use case flow diagram. - -11.9.4.4 Query AI/ML model training capability registration. - -Table 11.9.4.4-1: Query AI/ML model training capability registration. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp queries an AI/ML model training capability registration. | | -| Actors and Roles |
  • – rApp in the role of AI/ML model management and exposure services Consumer.
  • – AI/ML workflow functions in the role of AI/ML model management and exposure services Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the AI/ML model management and exposure services for registering an AI/ML model.
  • – The AI/ML model training capability has been registered by the rApp.
| | -| Begins when | The AI/ML model training service producer rApp determines the need to query the registration of a registered AI/ML model training capability. | | -| Step 1 (M) | The AI/ML model training service producer rApp requests to query the registration of an AI/ML model training capability by providing rAppId and AI/ML model training capability registration ID. | | -| Step 2 (M) | The AI/ML workflow functions check whether the rApp is authorized to query the AI/ML model training capability registration. | | -| Step 3(M) | The AI/ML workflow functions look up the information of queried AI/ML model training capability. | | -| Step 4(M) | The AI/ML workflow functions respond to rApp with AI/ML model training capability information. | | -| Ends when | The AI/ML model training service producer rApp was able to query the AI/ML model training capability registration. | | -| Exceptions | n/a | | -| Post Conditions | The rApp can query, update, or delete the AI/ML model training capability registration. | | -| Traceability | REQ-R1-AI/ML-Registertraincap -FUN1 | | - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent -autonumber - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rApp" as src - endbox - - box " Non-anchored functions in SMO/Non-RT RIC Framework " #cadetBlue - participant "AI/ML workflow functions" as ML - endbox -endbox - -src -> ML: <> Query AI/ML model training capability request (rAppId, AI/ML model training capability registration ID) -ML -> ML: Authz -note right -Check authorization in -collaboration with SME functions -end note -ML -> ML: Look up AI/ML model training capability registration -``` - -``` -ML -> src: <> Query AI/ML model training capability response (AI/ML model training capability information) -@enduml -``` - -![Sequence diagram showing the interaction between an rApp and the Non-RT RIC for updating an AI/ML training capability model registration. The diagram includes four steps: 1. rApp sends a Query AI/ML model training capability request (rAppID, AI/ML model training capability registration ID) to the Non-RT RIC. 2. The Non-RT RIC performs authorization (Authz) in collaboration with SME functions. 3. The Non-RT RIC looks up the AI/ML model training capability registration. 4. The Non-RT RIC returns the Query AI/ML model training capability response (AI/ML model training capability information) to the rApp. The Non-RT RIC contains 'Non-anchored functions in SMO/Non-RT RIC Framework' and 'AI/ML workflow functions'.](09797d4289ec96309d21a9a993153dab_img.jpg) - -Sequence diagram showing the interaction between an rApp and the Non-RT RIC for updating an AI/ML training capability model registration. The diagram includes four steps: 1. rApp sends a Query AI/ML model training capability request (rAppID, AI/ML model training capability registration ID) to the Non-RT RIC. 2. The Non-RT RIC performs authorization (Authz) in collaboration with SME functions. 3. The Non-RT RIC looks up the AI/ML model training capability registration. 4. The Non-RT RIC returns the Query AI/ML model training capability response (AI/ML model training capability information) to the rApp. The Non-RT RIC contains 'Non-anchored functions in SMO/Non-RT RIC Framework' and 'AI/ML workflow functions'. - -**Figure 11.9.4.4-1: Update registration of an AI/ML training capability model use case flow diagram.** - -## 11.9.5 Required data - -The AI/ML model training capability information includes but not limited to supported training frameworks, supported library packages, supported library versions, resource information. - -For registering an AI/ML model training capability, the rApp provides the rAppId and AI/ML model training capability information. On successful registration, AI/ML workflow functions provide an AI/ML model training capability registration ID for the registration of the AI/ML model training capability information. - -For deregistering an AI/ML model training capability, the rApp provides the rAppId and the AI/ML model training capability registration ID. - -For updating the registration of an AI/ML model training capability, the rApp needs to provide the rAppId, the AI/ML model training capability registration ID and the updated AI/ML model training capability information or the modified part of the AI/ML model training capability information. - -For querying the registration of an AI/ML model training capability, the rApp needs to provide the rAppId and the AI/ML model training capability registration ID. - -## 11.10 AI/ML workflow-related use case 10: AI/ML model inference – AI/ML workflow functions producing AI/ML inference. - -### 11.10.1 Overview - -This use case enables an rApp to request and cancel an inference for an AI/ML model. - -### 11.10.2 Background and goal of the use case - -The request and cancel AI/ML model inference procedures are defined as part of the AI/ML workflow services in R1GAP [1]. - -### 11.10.3 Entities/resources involved in the use case - -- 1) AI/ML workflow functions in the role of AI/ML model inference service Producer, - - a) support functionality allowing rApps to request, and cancel the inference of a registered AI/ML Model, -- 2) rApp in the role of AI/ML model inference service Consumer. - - a) initiates the procedure to request and cancel the inference of an AI/ML model. - -## 11.10.4 Solutions - -### 11.10.4.1 Request AI/ML model inference - -**Table 11.10.4.1-1: Request AI/ML model inference use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The AI/ML inference services Consumer requests inference for an AI/ML model. | | -| Actors and Roles |
  • AI/ML inference services Consumer in the role of Service Consumer.
  • The AI/ML workflow functions in the role of Service Producer.
| | -| Assumptions | n/a | | -| Preconditions | The AI/ML inference services Consumer is deployed, authenticated, and authorized to consume AI/ML inference services. | | -| Begins when | The AI/ML inference services Consumer determines the need to initiate the inference an AI/ML model. | | -| Step 1 (M) | The AI/ML inference services Consumer requests the AI/ML workflow functions to infer an AI/ML model providing rAppId and model identifier. | | -| Step 2 (M) | The AI/ML workflow functions check with SME functions whether the AI/ML inference services Consumer is authorized to request inference for an AI/ML model. | | -| Step 3 (M) | The AI/ML workflow functions validate the request. | | -| Step 4 (M) | The AI/ML workflow functions respond to the AI/ML inference services Consumer with inference job identifier as a parameter. | | -| Ends when | The AI/ML inference services Consumer is able to obtain the inference job identifier. | | -| Exceptions | n/a | | -| Post Conditions | The inference job exists, and the inference service Consumer can cancel the AI/ML model inference. | | -| Traceability | REQ-R1-AIML-inference -FUN1. | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent -autonumber - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rApp" as rApp - endbox - - box " Non-anchored functions in SMO/Non-RT RIC Framework " #cadetBlue - participant "AI/ML workflow functions" as ML - endbox -endbox - -rApp -> ML: <> Request AI/ML model inference request \n (rAppId, AI/ML model identifier) -ML -> ML: AuthZ - -note right -Check authorization in -Collaboration with SME functions -end note - -ML-> ML :validate -ML -> rApp: <> Request AI/ML model inference response \n (inference job identifier) - -``` - -@endum1 - -![Sequence diagram for 'Request AI/ML model inference' use case. It shows an rApp sending a request (R1) to AI/ML workflow functions, which then perform authorization (AuthZ) and validation (validate) steps, returning a response (R1) with an inference job identifier.](137bcfed81ada68ca5162ca5afed35c7_img.jpg) - -``` - -sequenceDiagram - actor rApp - participant AI/ML_workflow_functions as AI/ML workflow functions - Note right of AI/ML_workflow_functions: Check authorization in Collaboration with SME functions - rApp->>AI/ML_workflow_functions: 1 «R1» Request AI/ML model inference request (rAppId, AI/ML model identifier) - AI/ML_workflow_functions->>AI/ML_workflow_functions: 2 AuthZ - AI/ML_workflow_functions->>AI/ML_workflow_functions: 3 validate - AI/ML_workflow_functions-->>rApp: 4 «R1» Request AI/ML model inference response (inference job identifier) - -``` - -Sequence diagram for 'Request AI/ML model inference' use case. It shows an rApp sending a request (R1) to AI/ML workflow functions, which then perform authorization (AuthZ) and validation (validate) steps, returning a response (R1) with an inference job identifier. - -Figure 11.10.4.1-1: Request AI/ML model inference use case flow diagram. - -### 11.10.4.2 Cancel AI/ML model inference - -Table 11.10.4.2-1: Cancel AI/ML model inference use case. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The AI/ML inference services Consumer cancels the AI/ML model inference that it has previously requested. | | -| Actors and Roles |
  • AI/ML inference services Consumer in the role of Service Consumer.
  • The AI/ML workflow functions in the role of Service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • The AI/ML inference services Consumer is deployed, authenticated, and authorized to consume AI/ML inference services.
  • The inference job exists, and the AI/ML inference Consumer is aware of the job identifier.
| | -| Begins when | The AI/ML inference services Consumer determines the need to cancel the inference of an AI/ML model. | | -| Step 1 (M) | The AI/ML inference services Consumer requests the AI/ML workflow functions to cancel the inference for an AI/ML model providing rAppId and inference job identifier. | | -| Step 2 (M) | The AI/ML workflow functions check with SME functions whether the AI/ML inference services Consumer is authorized to cancel the inference job for an AI/ML model. | | -| Step 3(M) | The AI/ML workflow functions cancel the inference job. | | -| Step 4 (M) | The AI/ML workflow functions respond to the AI/ML inference services Consumer rApp with cancellation of inference job. | | -| Ends when | The AI/ML inference service job has been cancelled. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-AIML-inference -FUN1 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent -autonumber - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rApp" as rApp - endbox - - box " Non-anchored functions in SMO/Non-RT RIC Framework " #cadetBlue - participant "AI/ML workflow functions" as ML - endbox -endbox - -rApp -> ML: <> Cancel AI/ML model inference request \n (rAppId,inference job identifier) -ML -> ML: AuthZ - -note right -Check authorization in -Collaboration with SME functions -end note - -ML -> ML : Stop inference job -ML -> rApp: <> Cancel AI/ML model inference response -@enduml - -``` - -![Sequence diagram for 'Cancel AI/ML model inference' use case. Lifelines: rApp and AI/ML workflow functions (within Non-RT RIC). The process involves: 1. rApp sends a 'Cancel AI/ML model inference request' to the workflow functions. 2. The workflow functions perform an 'AuthZ' check (with a note about checking authorization and SME collaboration). 3. The workflow functions send a 'Stop inference job' message. 4. The workflow functions return a 'Cancel AI/ML model inference response' to the rApp.](86986d4dfd54f298d7b9fa9f82ab3009_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant AI/ML_workflow_functions as AI/ML workflow functions - Note right of AI/ML_workflow_functions: Check authorization in Collaboration with SME functions - rApp->>AI/ML_workflow_functions: 1 «R1» Cancel AI/ML model inference request (rAppId,inference job identifier) - AI/ML_workflow_functions->>AI/ML_workflow_functions: 2 AuthZ - AI/ML_workflow_functions->>AI/ML_workflow_functions: 3 Stop inference job - AI/ML_workflow_functions->>rApp: 4 «R1» Cancel AI/ML model inference response - -``` - -Sequence diagram for 'Cancel AI/ML model inference' use case. Lifelines: rApp and AI/ML workflow functions (within Non-RT RIC). The process involves: 1. rApp sends a 'Cancel AI/ML model inference request' to the workflow functions. 2. The workflow functions perform an 'AuthZ' check (with a note about checking authorization and SME collaboration). 3. The workflow functions send a 'Stop inference job' message. 4. The workflow functions return a 'Cancel AI/ML model inference response' to the rApp. - -Figure 11.10.4.2-1: Cancel AI/ML model inference use case flow diagram. - -### 11.10.5 Required data - -For creating AI/ML model inference job, the AI/ML inference services Consumer needs to provide its rAppId and the model identifier. The AI/ML workflow functions respond with the creation of inference job by providing the inference job identifier. - -For cancellation of an AI/ML inference job, the AI/ML inference services Consumer needs to provide its rAppId and the inference job identifier. - -## 11.11 AI/ML workflow-related use case 11: AI/ML model change subscription. - -### 11.11.1 Overview - -This use case defines how an rApp subscribes to registered AI/ML models. It enables an rApp to subscribe to and unsubscribe from notifications regarding changes in the registered AI/ML models. - -### 11.11.2 Background and goal of the use case - -The subscribe AI/ML models changes procedure, unsubscribe AI/ML models changes procedure and notify AI/ML models changes procedure are defined as part of the AI/ML workflow services in R1GAP [1]. - -### 11.11.3 Entities/resources involved in the use case - -- 1) AI/ML workflow functions - - a) support functionality to allow an rApp to subscribe and unsubscribe the registered AI/ML model changes, - - b) support functionality to notify rApp about changes of registered AI/ML model, - - c) support validation of selection criteria. -- 2) rApp - - a) initiates the procedure to subscribe and unsubscribe registered AI/ML model changes, - - b) support functionality to receive notification regarding changes of subscribed AI/ML model. - -## 11.11.4 Solutions - -### 11.11.4.1 Subscribe AI/ML model changes - -**Table 11.11.4.1-1: Subscribe AI/ML model changes.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| -| Goal | The rApp subscribes to notifications regarding changes of AI/ML models. | | -| Actors and Roles |
  • – rApp in the role of AI/ML model management and exposure service Consumer.
  • – AI/ML workflow functions in the role of AI/ML model management and exposure service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorised to access the AI/ML model management and exposure service.
  • – The rApp is aware of the AI/ML model identifier of the AI/ML model.
| Error! Reference source not found. | -| Begins when | The rApp determines the need to subscribe to notifications regarding changes of registered AI/ML models. | | -| Step 1 (M) | The rApp requests the AI/ML workflow functions to subscribe to notifications regarding AI/ML model changes with rAppId and AI/ML model identifier selection criteria. | | -| Step 2 (M) | The AI/ML workflow functions receive the AI/ML model subscription request, and check whether the rApp is authorized to subscribe to identified AI/ML models. | | -| Step 3 (M) | The AI/ML workflow functions validate the subscribe AI/ML model request. | | -| Step 4 (M) | The AI/ML workflow functions establish the AI/ML model subscription. | | -| Step 5 (M) | The AI/ML workflow functions send back a response with a subscription identifier matching the request in Step 1 to rApp. | | -| Ends when | The rApp was able to subscribe to notifications regarding AI/ML model changes. | | -| Exceptions | n/a | | -| Post Conditions |

The rApp can receive notifications when changes are made to any of the AI/ML models that matches AI/ML model identifier selection criteria.

The rApp can unsubscribe from the notifications.

| | -| Traceability | n/a | | -| NOTE: AI/ML model identifier includes model name, model version and artifact version. AI/ML model identifier selection criteria could be upper and/or lower bounds of model version and artifact version number, or list of individual model version and artifact version numbers, etc. Selection criteria is used to identify AI/ML models to be subscribed, which can be applied to part, or all of AI/ML model identifier components. | | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent -autonumber - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rApp" as rApp - endbox - box " Non-anchored functions in SMO/Non-RT RIC Framework " #cadetBlue - participant "AI/ML workflow functions" as ML - endbox - -``` - -``` - -endbox -endbox - -rApp -> ML: <> Subscribe AI/ML model change request (rAppId, \n AI/ML model identifier -selection criteria) -ML -> ML: Authz -note right -Check authorization in -collaboration with SME functions -end note -ML -> ML: Validate -ML -> ML: Create subscription -ML -> rApp: <> Subscribe AI/ML model change response (subscription identifier) -@enduml - -``` - -![Sequence diagram titled 'Subscribe AI/ML model changes use case flow diagram'. It shows the interaction between an rApp and AI/ML workflow functions within the Non-RT RIC framework. 1. rApp sends a 'Subscribe AI/ML model change request' to the AI/ML workflow functions. 2. The AI/ML workflow functions perform 'Authz' (Authorization), with a note stating 'Check authorization in collaboration with SME functions'. 3. The AI/ML workflow functions perform 'Validate'. 4. The AI/ML workflow functions perform 'Create subscription'. 5. The AI/ML workflow functions send a 'Subscribe AI/ML model change response' back to the rApp.](e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg) - -``` - -sequenceDiagram - participant rApp - box Non-RT RIC - participant ML as AI/ML workflow functions - end - Note over ML: Non-anchored functions in SMO/Non-RT RIC Framework - rApp->>ML: 1 «R1» Subscribe AI/ML model change request (rAppId, AI/ML model identifier selection criteria) - ML->>ML: 2 Authz - Note right of ML: Check authorization in collaboration with SME functions - ML->>ML: 3 Validate - ML->>ML: 4 Create subscription - ML->>rApp: 5 «R1» Subscribe AI/ML model change response (subscription identifier) - -``` - -Sequence diagram titled 'Subscribe AI/ML model changes use case flow diagram'. It shows the interaction between an rApp and AI/ML workflow functions within the Non-RT RIC framework. 1. rApp sends a 'Subscribe AI/ML model change request' to the AI/ML workflow functions. 2. The AI/ML workflow functions perform 'Authz' (Authorization), with a note stating 'Check authorization in collaboration with SME functions'. 3. The AI/ML workflow functions perform 'Validate'. 4. The AI/ML workflow functions perform 'Create subscription'. 5. The AI/ML workflow functions send a 'Subscribe AI/ML model change response' back to the rApp. - -**Figure 11.11.4.1-1: Subscribe AI/ML model changes use case flow diagram** - -### 11.11.4.2 Notify AI/ML model changes - -Table 11.11.4.2-1: Notify AI/ML model changes. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| -| Goal | The rApp receives a notification regarding a change of a registered AI/ML model. | | -| Actors and Roles |
  • – rApp in the role of AI/ML model management and exposure service Consumer.
  • – AI/ML workflow functions in the role of AI/ML model management and exposure service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorised to access the AI/ML model management and exposure service.
  • – The rApp is subscribed to notifications.
| Error! Reference source not found. | -| Begins when | The AI/ML workflow functions determine to send a notification regarding the change of a subscribed AI/ML model to the subscribing rApp. | | -| Step 1(M) | The AI/ML workflow functions send a notification to the subscribing rApp with AI/ML model identifier and available change details. | | -| Ends when | The rApp was able to receive the notification. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | n/a | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent -autonumber - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rApp" as rApp - endbox - box "Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant "AI/ML workflow functions" as ML - endbox -endbox - -ML -> rApp: <> Notify AI/ML model changes (AI/ML model identifier, available change details) -@enduml - -``` - -![UML Sequence diagram for 'Notify AI/ML model changes'. The diagram shows a lifeline for 'rApp' and a sequence group 'Non-anchored functions in SMO/Non-RT RIC Framework' containing 'AI/ML workflow functions'. A message arrow labeled '1 <> Notify AI/ML model changes (AI/ML model identifier, available change details)' points from the AI/ML workflow functions to the rApp lifeline.](33859177822cce0c1b03fd3d37de14f6_img.jpg) - -UML Sequence diagram for 'Notify AI/ML model changes'. The diagram shows a lifeline for 'rApp' and a sequence group 'Non-anchored functions in SMO/Non-RT RIC Framework' containing 'AI/ML workflow functions'. A message arrow labeled '1 <> Notify AI/ML model changes (AI/ML model identifier, available change details)' points from the AI/ML workflow functions to the rApp lifeline. - -Figure 11.11.4.2-1: Notify AI/ML model changes use case flow diagram. - -### 11.11.4.3 Unsubscribe AI/ML model changes - -**Table 11.11.4.3-1: Unsubscribe AI/ML model changes.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| -| Goal | The rApp unsubscribes from notifications. | | -| Actors and Roles |
  • – rApp in the role of AI/ML model management and exposure service Consumer.
  • – AI/ML workflow functions in the role of AI/ML model management and exposure service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorised to access the AI/ML model management and exposure service.
  • – The rApp is subscribed to notifications regarding AI/ML model changes.
| Error! Reference source not found. | -| Begins when | The rApp determines the need to unsubscribe from notifications regarding changes of registered AI/ML model. | | -| Step 1 (M) | The rApp requests the AI/ML workflow functions to unsubscribe from notifications regarding AI/ML model changes by providing the rAppId and subscription identifier | | -| Step 2 (M) | The AI/ML workflow functions check whether the rApp is authorized to unsubscribe from notifications regarding AI/ML model changes | | -| Step 3(M) | The AI/ML workflow functions cancel the subscription | | -| Step 4(M) | The AI/ML workflow functions respond to the request. | | -| Ends when | The rApp was able to unsubscribe from notifications regarding changes of registered AI/ML model. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | n/a | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent -autonumber - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rApp" as rApp - endbox - box " Non-anchored functions in SMO/Non-RT RIC Framework " #cadetBlue - participant "AI/ML workflow functions" as ML - endbox -endbox - -rApp -> ML: <> Unsubscribe AI/ML model change request (rAppId, subscription identifier) -ML -> ML: Authz -note right -Check authorization in -collaboration with SME functions -end note -ML -> ML: Cancel subscription -ML -> rApp: <> Unsubscribe AI/ML model change response -@enduml - -``` - -![Sequence diagram for Unsubscribe AI/ML model changes use case flow. It shows an rApp sending an unsubscribe request to AI/ML workflow functions, which then check authorization and cancel the subscription, returning a response.](a76fa39f5daf6a026e032495262ed0f6_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant AI/ML_workflow_functions as AI/ML workflow functions - Note right of AI/ML_workflow_functions: Check authorization in collaboration with SME functions - rApp->>AI/ML_workflow_functions: 1 <> Unsubscribe AI/ML model change request (rAppId, subscription identifier) - AI/ML_workflow_functions->>AI/ML_workflow_functions: 2 Authz - AI/ML_workflow_functions->>AI/ML_workflow_functions: 3 Cancel subscription - AI/ML_workflow_functions->>rApp: 4 <> Unsubscribe AI/ML model change response - -``` - -Sequence diagram for Unsubscribe AI/ML model changes use case flow. It shows an rApp sending an unsubscribe request to AI/ML workflow functions, which then check authorization and cancel the subscription, returning a response. - -Figure 11.11.4.3-1: Unsubscribe AI/ML model changes use case flow diagram - -### 11.11.5 Required data - -For subscription to notifications regarding changes of registered AI/ML model, the rApp provides the rAppId and the AI/ML model identifier selection criteria. The AI/ML workflow functions send back a subscription identifier in response. - -The AI/ML workflow functions send notifications to the subscribing rApp by providing the AI/ML model identifier(s) and available change details of AI/ML model(s). - -For unsubscribing from notifications regarding changes of registered AI/ML model, the rApp needs to send the rAppId and AI/ML model subscription identifier. - -## 11.12 AI/ML workflow-related use case 12: Query of AI/ML Model inference capabilities - AI/ML workflow functions producing AI/ML inference - -### 11.12.1 Overview - -This use case enables an rApp to query the inference capability information of an AI/ML model. - -### 11.12.2 Background and goal of the use case - -The query AI/ML model inference capabilities procedure are defined as part of the AI/ML workflow services in R1GAP [1]. - -### 11.12.3 Entities/resources involved in the use case - -- 1) AI/ML workflow functions in the role of AI/ML model inference service Producer, - - a) Support functionality allowing rApps to query the inference capability of an AI/ML Model, -- 2) rApp in the role of AI/ML model inference service Consumer. - - a) Initiates the procedure to query the inference capability of an AI/ML model. - -## 11.12.4 Solutions - -### 11.12.4.1 Query AI/ML model inference capability - -**Table 11.12.4.1-1: Query AI/ML model inference capability use case.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The AI/ML inference services Consumer retrieves the AI/ML model inference capability information. | | -| Actors and Roles |
  • AI/ML inference services Consumer in the role of Service Consumer.
  • The AI/ML workflow functions in the role of Service Producer.
| | -| Assumptions | Service Consumer is authorized to request inference capability information of a registered AI/ML model. | | -| Preconditions | The AI/ML inference services Consumer is deployed, authenticated, and authorized to consume AI/ML inference services. | | -| Begins when | The AI/ML inference services Consumer determines the need to query the inference capability information of a registered AI/ML model. | | -| Step 1 (M) | The AI/ML inference services Consumer requests the AI/ML workflow functions to provide inference capability information by passing on the query parameters such as model identifier and associated model information. | | -| Step 2 (M) | The AI/ML workflow functions check with SME functions whether the AI/ML inference services Consumer is authorized to request the inference capability information for a registered AI/ML model. | | -| Step 3 (M) | The AI/ML workflow functions respond to the AI/ML inference services Consumer rApp with the requested inference capability information that matches the query criteria. | | -| Ends when | The AI/ML model inference capability information has been retrieved. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-AIML-inference -FUN2 | | - -``` -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -skinparam SequenceGroupBackgroundColor Transparent -skinparam SequenceGroupBodyBackgroundColor Transparent -autonumber - -box "Non-RT RIC" #whitesmoke - box #ivory - participant "rApp" as rApp - endbox - - box " Non-anchored functions in SMO/Non-RT RIC Framework " #cadetBlue - participant "AI/ML workflow functions" as ML - endbox -endbox - -rApp -> ML: <> Query AI/ML model inference capability request \n (rAppId, query criteria) -ML -> ML: AuthZ - -note right -Check authorization in -Collaboration with SME functions -end note -``` - -``` -ML -> rApp: <> Query AI/ML model inference capability response \n (inference capability information) -@enduml -``` - -![Sequence diagram for 'Query AI/ML model inference capability use case'. It shows an rApp sending a request to AI/ML workflow functions in the Non-RT RIC, which then check authorization with SME functions before returning a response.](e01c6273c4177746475715ee9c17a882_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant NonRT RIC as Non-RT RIC - Note right of NonRT RIC: Non-anchored functions in SMO/Non-RT RIC Framework - - rApp->>NonRT RIC: 1 «R1» Query AI/ML model inference capability request (rAppId, query criteria) - Note right of NonRT RIC: 2 AuthZ Check authorization in Collaboration with SME functions - NonRT RIC-->>rApp: 3 «R1» Query AI/ML model inference capability response (inference capability information) - -``` - -Sequence diagram for 'Query AI/ML model inference capability use case'. It shows an rApp sending a request to AI/ML workflow functions in the Non-RT RIC, which then check authorization with SME functions before returning a response. - -Figure 11.12.4.1-1: Query AI/ML model inference capability use case flow diagram. - -### 11.12.5 Required data - -For querying of an AI/ML model inference capability information, the AI/ML inference services Consumer needs to provide its rAppId and the query criteria (including the model identifier and model information). The AI/ML workflow functions respond with inference capability information such as model identifier or inference latency. - -## 11.13 AI/ML Workflow-related use case 13: Query of AI/ML Model training capability - -### 11.13.1 Overview - -This use case defines how an rApp queries AI/ML model training capability. - -### 11.13.2 Background and goal of the use case - -The query AI/ML model training capability is an optional procedure defined as part of the AI/ML model training capability query service in R1GAP [1]. - -### 11.13.3 Entities/resources involved in the use case - -- 1) AI/ML workflow functions in the role of AI/ML model management and exposure service producer, - - a) Supports functionality allowing rApps to query the registered AI/ML model training capability, -- 2) rApp in the role of AI/ML model management and exposure service consumer. - - a) Initiates the procedure to query the registered AI/ML model training capability. - -## 11.13.4 Solutions - -### 11.13.4.1 Query AI/ML model training capability - -**Table 11.13.4.1-1: Query AI/ML model training capability.** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The rApp queries registered AI/ML model training capability | | -| Actors and Roles |
  • – rApp in the role of AI/ML model management and exposure service Consumer.
  • – AI/ML workflow functions in the role of AI/ML model management and exposure service Producer.
| | -| Assumptions | n/a | | -| Preconditions |
  • – The rApp is authorized to access the AI/ML workflow services.
  • – At least one AI/ML model training capability is registered with the AI/ML workflow functions.
| | -| Begins when | The rApp determines the need to query the registered AI/ML model training capability. | | -| Step 1 (M) | The rApp requests the AI/ML workflow functions for the information on the AI/ML model training capability by providing its rAppId and selection criteria. | | -| Step 2(M) | The AI/ML workflow functions check if the rApp is authorized to query the registered AI/ML model training capability. | | -| Step 3(M) | The AI/ML workflow functions look up the information of queried AI/ML model training capability. | | -| Step 4(M) | The AI/ML workflow functions provide the information about the registered AI/ML model training capability and corresponding AI/ML model Trainer rAppIds. | | -| Ends when | The AI/ML model training capability has been received. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-R1-AI/ML-Registertraincap -FUN1 | | - -``` - -@startuml -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "Non-RT RIC" #whitesmoke - box #ivory - participant rApp as rApp - endbox - box " Non-anchored functions in SMO/Non-RT RIC Framework" #cadetBlue - participant " AI/ML workflow functions " as aif - endbox -rApp ->aif:<> Query AI/ML model training capability request\n(rAppId, Selection criteria) -activate aif -aif --> aif:AuthZ -note right -Check authorization in collaboration -with SME functions -end note -aif --> aif: Look up AI/ML model training capability registration -aif -> rApp :<> Query AI/ML model training capability response\n(AI/ML model Trainer rAppIds, AI/ML model training capability information) -deactivate aif -@enduml - -``` - -![Sequence diagram for Query AI/ML model training capability use case flow. The diagram shows an rApp on the left interacting with the Non-RT RIC on the right. The Non-RT RIC contains a box for 'Non-anchored functions in SMO/Non-RT RIC Framework' which includes 'AI/ML workflow functions'. The sequence is: 1. rApp sends a '«R1» Query AI/ML model training capability request (rAppId, Selection criteria)' to the AI/ML workflow functions. 2. The AI/ML workflow functions send an 'AuthZ' message to SME functions, with a note 'Check authorization in collaboration with SME functions'. 3. The AI/ML workflow functions send a 'Look up AI/ML model training capability registration' message to the SME functions. 4. The AI/ML workflow functions send a '«R1» Query AI/ML model training capability response (AI/ML model Trainer rAppIds, AI/ML model training capability information)' back to the rApp.](87f8b579bc67022e8dd0a0a50585fd4d_img.jpg) - -Sequence diagram for Query AI/ML model training capability use case flow. The diagram shows an rApp on the left interacting with the Non-RT RIC on the right. The Non-RT RIC contains a box for 'Non-anchored functions in SMO/Non-RT RIC Framework' which includes 'AI/ML workflow functions'. The sequence is: 1. rApp sends a '«R1» Query AI/ML model training capability request (rAppId, Selection criteria)' to the AI/ML workflow functions. 2. The AI/ML workflow functions send an 'AuthZ' message to SME functions, with a note 'Check authorization in collaboration with SME functions'. 3. The AI/ML workflow functions send a 'Look up AI/ML model training capability registration' message to the SME functions. 4. The AI/ML workflow functions send a '«R1» Query AI/ML model training capability response (AI/ML model Trainer rAppIds, AI/ML model training capability information)' back to the rApp. - -Figure 11.13.4.1-1: Query AI/ML model training capability use case flow diagram. - -## 11.13.5 Required data - -For the Query AI/ML model training capability request, the rApp provides the rAppId and selection criteria. - -The AI/ML workflow functions respond with information which includes the AI/ML model Trainer rAppIds and AI/ML model training capability information that match the selection criteria. The AI/ML model training capability information contains training platform information and training resource information. - -# 12 Use cases for rApp Management Services - -## 12.1 rApp Management use case 1: rApp registration - -### 12.1.1 Overview - -This use case provides the description and requirements for registering an rApp with the SMO/Non-RT RIC framework. - -### 12.1.2 Background and goal of the use case - -The rApp registration procedure registers the rApp to the SMO/Non-RT RIC framework. To register an rApp, an rApp may pass relevant info that may include the rApp name, vendor, software version, and other information needed by the SMO/Non-RT RIC framework. - -### 12.1.3 Entities/resources involved in the use case. - -- 1) rApp management functions in the role of rApp registration service producer - - a) assign the rApp with an ID. -- 2) rApp - - a) initiates the procedure of rApp registration. - -## 12.1.4 Solutions - -### 12.1.4.1 rApp registration - -**Table 12.1.4.1-1: rApp registration use case** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Register the rApp to the rApp registration service producer in the SMO/Non-RT RIC framework. | | -| Actors and Roles |
  • – rApp in the role of rApp registration service consumer
  • – rApp management functions in the role of rApp registration service producer
| | -| Assumptions | n/a | | -| Preconditions | The rApp is instantiated. | | -| Begins when | The rApp is ready for registration. | | -| Step 1 (M) | The rApp sends a registration request to the rApp management functions in the SMO/Non-RT RIC framework passing relevant information needed. | | -| Step 2 (M) | The rApp management functions process the rApp registration request that may include.
  • - performing authentication,
  • - if rApp is authenticated, rAppId will be assigned to rApp.
| | -| Step 3 (M) | Response to the registration request along with the rAppId. | | -| Ends when | The rApp is allocated with an rAppId. | | -| Exceptions | n/a | | -| Post Conditions | The rApp is registered with the SMO/Non-RT RIC framework and an rAppId is allocated to the rApp. | | -| Traceability | REQ-R1-SME-rAppreg-FUN1, REQ-R1-SME-rAppreg-FUN2. | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -box "SMO/Non-RT RIC" #whitesmoke -box #ivory -participant rApp as rApp -endbox -box " Non-anchored functions in SMO/Non-RT RIC Framework " #cadetBlue -participant "rApp management functions" as RMF -endbox -endbox -==rApp registration == -rApp -> RMF:<>Registration request -activate RMF -RMF--> RMF : AuthN -note right -registration processing -assign rAppId -end note -RMF -> rApp :<>Registration response (rAppId) -Deactivate RMF -@enduml - -``` - -![Sequence diagram for rApp registration use case flow. The diagram shows an rApp on the left interacting with the SMO/Non-RT RIC on the right. The SMO/Non-RT RIC contains 'Non-anchored functions in SMO/Non-RT RIC Framework' and 'rApp management functions'. The sequence is: 1. rApp sends a '«R1»Registration request' to the rApp management functions. 2. The rApp management functions send an 'AuthN' message to the non-anchored functions, which perform 'registration processing assign rAppId'. 3. The rApp management functions send a '«R1»Registration response (rAppId)' back to the rApp.](c6240283e2f65a6d02db47fa4ab0c518_img.jpg) - -``` - -sequenceDiagram - participant rApp - participant SMO/Non-RT RIC - Note right of SMO/Non-RT RIC: Non-anchored functions in SMO/Non-RT RIC Framework - Note right of SMO/Non-RT RIC: rApp management functions - Note right of SMO/Non-RT RIC: rApp registration - rApp->>SMO/Non-RT RIC: 1 «R1»Registration request - activate SMO/Non-RT RIC - SMO/Non-RT RIC->>SMO/Non-RT RIC: 2 AuthN - Note right of SMO/Non-RT RIC: registration processing assign rAppId - SMO/Non-RT RIC->>rApp: 3 «R1»Registration response (rAppId) - deactivate SMO/Non-RT RIC - -``` - -Sequence diagram for rApp registration use case flow. The diagram shows an rApp on the left interacting with the SMO/Non-RT RIC on the right. The SMO/Non-RT RIC contains 'Non-anchored functions in SMO/Non-RT RIC Framework' and 'rApp management functions'. The sequence is: 1. rApp sends a '«R1»Registration request' to the rApp management functions. 2. The rApp management functions send an 'AuthN' message to the non-anchored functions, which perform 'registration processing assign rAppId'. 3. The rApp management functions send a '«R1»Registration response (rAppId)' back to the rApp. - -Figure 12.1.4.1-1: rApp registration use case flow diagram - -### 12.1.5 Required data. - -For registering, an rApp needs to provide the security credentials along with e.g., rApp name, vendor, software version, certificates etc. and the role an rApp is trying to register (Service producer and/or Service consumer). - -The response to the rApp registration includes the status of registration i.e., success or failure. - -For successful rApp registration, the response will also include the rAppId. - -For unsuccessful rApp registration, the response will also include the error code along with relevant information. - -## Annex (informative): Change history - -| Date | Revision | Description | -|------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 21.11.2025 | 12.00 | Updated the use case for DME for retrieval of data jobs for a registered DME type | -| 07.07.2025 | 11.00 | Updated the rApp registration use case from SME to rApp management, updated the AI/ML training capability use case and Specification aligned with TS template version 04 | -| 13.03.2025 | 10.00 | Added usecases for AI/ML model training capability registration and data job status | -| 21.11.2024 | 09.00 | Added usecases for AI/ML inference capability information Query | -| 18.07.2024 | 08.00 | Added use cases for AI/ML model training capability registration, Query for data subscription, AI/ML model inference use case for create and delete and updated the SME subscription use case. | -| 20.04.2024 | 07.00 | Added the use cases for AI/ML performance monitoring use cases and updated the document with Producer and Consumer roles. | -| 20.11.2023 | 06.00 | Added the use cases and requirements to Data management and exposure services, A1 related services, AI/ML model workflow services, updated the data type to DME type. | -| 29.07.2023 | 05.00 | Published as Final version 05.00 | -| 24.03.2023 | 04.00 | Published as Final Version 04.00 | -| 10.11.2022 | 03.00 | Published as Final Version 03.00 | -| 29.07.2022 | 02.00 | Published as Final version 02.00 | -| 01.04.2022 | 01.00 | Published as Final version 01.00 | \ No newline at end of file diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/030c758fd425016b03290c8f11bef69d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/030c758fd425016b03290c8f11bef69d_img.jpg deleted file mode 100644 index 03a72cdf14cf8edaba03402ca6719459331691a9..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/030c758fd425016b03290c8f11bef69d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9c357f2f880f4714d0540a795c1e4ecdec8914270e5ca560218b68fe400987b7 -size 42136 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/05ec650892a1d3916ffe3d2a7ec29928_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/08783c875dd39684fee7f2a40b584c64_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/09797d4289ec96309d21a9a993153dab_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/09797d4289ec96309d21a9a993153dab_img.jpg deleted file mode 100644 index f20561316f2e588d2c5f32dc85bea4d8bd00de4e..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/09797d4289ec96309d21a9a993153dab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0124dfc0a137134c206d07f117f93bfa40f62c716b5cd9551699946fb8b77735 -size 40881 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/0a65720e640be13541e947c06c7a8c7f_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/137bcfed81ada68ca5162ca5afed35c7_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/137bcfed81ada68ca5162ca5afed35c7_img.jpg deleted file mode 100644 index b5768288e9a9b61528a0c7599e2ed1f1eb18e42d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/137bcfed81ada68ca5162ca5afed35c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b486e43d84f28019f66e21f6ad8c8c57125101950041aef71972aa077c1d87c0 -size 65224 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/140bd031d724324269168296afd1e04d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/140bd031d724324269168296afd1e04d_img.jpg deleted file mode 100644 index fad25197ced020e760f9903dabd0e183541c5131..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/140bd031d724324269168296afd1e04d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e71d079146e7ed2bf7e50b2f421bccf2ed0464dfc80b9a617a635a468e102f20 -size 45165 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/145d00f59802048185303f15937ea65c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/145d00f59802048185303f15937ea65c_img.jpg deleted file mode 100644 index 17f480cb116226bd02b799f8c22f26c755ae580a..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/145d00f59802048185303f15937ea65c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d5430ffc6f119a6f85fb8a412d7ce8fbaa63edf39cd7937c5e8bf3e43d629450 -size 54699 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/153b4763edcf6b16d783052c7ad165f1_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/185df94f4a6a5245323255e844a30ec0_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/18bb06865e2dada3656ea3d57f290f7f_img.jpg deleted file mode 100644 index 4053f448d555c3a868cef3d288f421db2de051c3..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/18bb06865e2dada3656ea3d57f290f7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:74808cfec820f0778e5b06cce8a4c0807c966775b233d914e6adf2872cd68593 -size 48310 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg deleted file mode 100644 index 6dc435c8c9573156f66c93d3b6aa4ed484eb5f20..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/1cd38e4f2ffcae2871964fa6313a9a27_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d8b654ab216924b8ee22b678cf04be1252200d91ce351ba788ec4ca3ea5c9da4 -size 102677 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/1e7157ed1c2b915b5b1823b6ad189038_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/1e95fc0be1c9782d078a26fb32facddd_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/1e95fc0be1c9782d078a26fb32facddd_img.jpg deleted file mode 100644 index 5a4ef16bc18d638b37fcd87a6bf01a8f8a1430be..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/1e95fc0be1c9782d078a26fb32facddd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:680f8a1dbab1b896fca565111ddd43a9263a352fc6099b56aa3fb47367c1f8c1 -size 75744 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/223792b3652794024244c277cc46394b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/223792b3652794024244c277cc46394b_img.jpg deleted file mode 100644 index dd51e7bc647e77e421c877a8d4461778a2e1ecf6..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/223792b3652794024244c277cc46394b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:328d2fa2368c20763c5b6913af7b004d25fd55444b42ecbbbce7cd31bf199433 -size 39431 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/22f30783614672d201275c116a5d8516_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/245166735676c675f98f535bc4c6f0a1_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/245166735676c675f98f535bc4c6f0a1_img.jpg deleted file mode 100644 index 29f610e5b5d4486424403cc4d021aa233c1c0d48..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/245166735676c675f98f535bc4c6f0a1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:10b02a0f6bdd528b4ef81b3fb4e9b3adbc75390da92e76bc782f19399dfbffe2 -size 69249 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/24a5d31d8d81bf0e4fe402416b8b2f49_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/24a5d31d8d81bf0e4fe402416b8b2f49_img.jpg deleted file mode 100644 index 6967bd16e7fe030f0ccbda839d381c0ac42f430e..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/24a5d31d8d81bf0e4fe402416b8b2f49_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:21b8d5d4663d12e599c082b8b1869f28127425f45f62b6497c067d07fec8c65f -size 33739 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg deleted file mode 100644 index 1e752c5cb1f650d2d2479df69dc19a04f2504efd..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:94b34ac34f288548a6254325d3a940658bbdc1ae2efeb8b067bffd3f77c17b9a -size 40391 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2b60ebe01f77d22e53da1fbe73083b01_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2b60ebe01f77d22e53da1fbe73083b01_img.jpg deleted file mode 100644 index 6d0a9c153024969362737fe5a503f8f82b7158d8..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2b60ebe01f77d22e53da1fbe73083b01_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6b9967da61e35d4cd79f8e5fc90a64cc799cfdb00a9738c5746c8c59474d28f1 -size 49224 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2c41e286ea9a1b008d3beb348d86096f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2c41e286ea9a1b008d3beb348d86096f_img.jpg deleted file mode 100644 index 77f04be15262cc6788171959c2b7bdbc65c16cf4..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2c41e286ea9a1b008d3beb348d86096f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d86177469d77f9ece9f8acd36115948c2b53c86a28a5798c90035f752135e96 -size 51263 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2c83b9d9c8c8076be3a1de47288c226d_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2cb201535956cd78d7fd3cc89f3c7d03_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2cf3896394a2342a2b46c504ab9a8830_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2cf3896394a2342a2b46c504ab9a8830_img.jpg deleted file mode 100644 index eac83924f63ba8d33652a78a1d1420709ba62e95..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2cf3896394a2342a2b46c504ab9a8830_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f16e159741b431c34acf148639dbe9558b813ede89de7c98d360278407c73b75 -size 65207 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2d548db0b26b7bf33244320322d5ee2c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2d548db0b26b7bf33244320322d5ee2c_img.jpg deleted file mode 100644 index 3efa7c78015c7b82cb3e2f2f375702c26edef63a..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2d548db0b26b7bf33244320322d5ee2c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03f665f31fcb48ee8e9d85685b6a5f977f1eeda9ff9f61935917e874ecb953c1 -size 54814 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg deleted file mode 100644 index ff94a13ed054ab47e289f585a5556a63caace9ff..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/2ed8cadf211f7d2dba5eecc5f0ad1876_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:12ce5c43d3a6077ff1775719fe40b4bbff770888475409a6903380672ce1ad28 -size 66262 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/3117e1f4e4767bab3f5c7cfaf4804652_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/3337af75dfee8af7687b4f49914d6c93_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/3337af75dfee8af7687b4f49914d6c93_img.jpg deleted file mode 100644 index d376607edfdca111be1fd7b58265994f8a2600e6..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/3337af75dfee8af7687b4f49914d6c93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:00469d6de34a316be15f99167a302412bbb43b1f886a06ff958344b4316d5892 -size 59774 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/33859177822cce0c1b03fd3d37de14f6_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/33859177822cce0c1b03fd3d37de14f6_img.jpg deleted file mode 100644 index 65f6ecd7f4fc4e534bfd9c2c10bdf7721c26adbf..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/33859177822cce0c1b03fd3d37de14f6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f845c1c4044c49d303772e2880d98089d3d7100a92bad1437c2b5acda17ebf70 -size 28698 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg deleted file mode 100644 index f423696aabc68c33b798e1479b12575377fcae18..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:da6fd083d21e535da0132cc08723e3539ddc8d0e32fb6eb3d14c6bf52f10660f -size 91603 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/36fb8f844f936e7a1de4838da774f2f9_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/38222c3ae003223a67635bfcc6950fbb_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/3a4f4369128594c5db0aa6b853c0666e_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg deleted file mode 100644 index 6fed7a69fbfcfb5d4007d7461dca2065f2755179..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b2c23ad84a3a47c52e8a41414a5d1005796785831a165c2127e381e5cf9dac5e -size 48275 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg deleted file mode 100644 index 0bbe86b0266d22216842ec12e10f18630c7f2a61..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/40a8c30f7ea5ecea4912e040c97c5b9c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe35bf0496ef794504255c9cc0ff4d42d057ce84fddc171df03df5b14b7c4bd8 -size 59205 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/4806f9f95fff13a30d6523bd6ffeac63_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/4806f9f95fff13a30d6523bd6ffeac63_img.jpg deleted file mode 100644 index 98a122c9fa57e66a738d5989f13119855925f8ef..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/4806f9f95fff13a30d6523bd6ffeac63_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:aa99a86134536bbcba4e690fa8a61a66a74b103c9f097f7cdf1e1fd8de4664a2 -size 44503 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg deleted file mode 100644 index 9a863b394765b18d479d501944f60c148027a95d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:aeebb8bde371d400db3d90b60ee5b95ef05ccfec1bc00f59e115f62d9778d3fb -size 4523 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/4a04896dfb569893fba50729314024f5_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/4c63a0e17b54c7e61d512c276932114c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/4c63a0e17b54c7e61d512c276932114c_img.jpg deleted file mode 100644 index c56b96cd84429f9ff7d6368f09933fd42e716593..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/4c63a0e17b54c7e61d512c276932114c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:019fe6ee543380a9e804c0e8eb1c4f5b910fdcb877f0dd7c1e66daf0edc7a562 -size 80158 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/4db00373eb0bec04341ee887235bbfea_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/52c40e2f443985dc63f45dec57d90c8c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/52c40e2f443985dc63f45dec57d90c8c_img.jpg deleted file mode 100644 index 68a09ed98072abf129d0c42377dbc9a4f8fc4606..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/52c40e2f443985dc63f45dec57d90c8c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:35029830b1eeaaca61dd75a2724050f9dbf95d79ceace2ac37167139fc25e9e3 -size 45711 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/536768a30136cd5c2d57f46c25d1d804_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/536768a30136cd5c2d57f46c25d1d804_img.jpg deleted file mode 100644 index 5c11a2f05974a18ca095295a7bf338fc3392195e..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/536768a30136cd5c2d57f46c25d1d804_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bcf483cf399abda7cb507dbdfd866c2867fcc5b5ef3387ff5fd79c5cff5a2902 -size 61862 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/5661815043254c37a4e3e4833f51e727_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/5661815043254c37a4e3e4833f51e727_img.jpg deleted file mode 100644 index 6ff679ddbaf998cae04f5a89a6a409f9a5559d09..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/5661815043254c37a4e3e4833f51e727_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4d9ad000ec22fce806b558980f1f44190d746d374f7c0b32cdad81b83907553b -size 38922 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/56ac11fb9683d7b846fb65c845d80f22_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/5801c19431e76330430e92a598cc7a16_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/5801c19431e76330430e92a598cc7a16_img.jpg deleted file mode 100644 index 8c7e1f3adfb520d1dcea8872516dde9f62af6dee..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/5801c19431e76330430e92a598cc7a16_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1f1084dce5327ee0c070f9d311bd7439d2728d4cdc0bfb8ab65cdcecef3caaff -size 55662 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/592f13acca3e6d5152dd4489f030d004_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/592f13acca3e6d5152dd4489f030d004_img.jpg deleted file mode 100644 index 8df9ef24a7f394503de6433a60e6c48953c4581f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/592f13acca3e6d5152dd4489f030d004_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6b229dd85dac0d2aee76ca7e771b8641b4352b545f8f5e68acd7ed663bf589db -size 64277 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/59368942873b0c35eef79a7a985025dc_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg deleted file mode 100644 index b26c0f426fe3fda78264a73a38f2420d641fc8a6..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d60b0c05fc57018fb1e6600910ff94634f6d20b3c438027dbc5a935fb934081a -size 59967 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/61a7f401eb46fe99a71f27bc37493f04_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/61a7f401eb46fe99a71f27bc37493f04_img.jpg deleted file mode 100644 index b7f3c09b3265a9a23158ecf8e7c889ab2aa7ab91..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/61a7f401eb46fe99a71f27bc37493f04_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5eee5baae9245114d19660cc25f714b0de5d14bc450afce5b0f18641ea43a9a9 -size 51502 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6588b1c7f14069d96744b473ad663248_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg deleted file mode 100644 index 81c627efb69f8aab00065fc65f3e652eaa225e41..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c42bcc84ba94c677644bd5f109783f29f49f6e63b0386e2d2e6f910170adad8a -size 77304 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/69467ece0a576b4c2ec3e0c89ba61527_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/69467ece0a576b4c2ec3e0c89ba61527_img.jpg deleted file mode 100644 index 0f4b8b5384dce8c7716efb14780f39e8c69f1490..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/69467ece0a576b4c2ec3e0c89ba61527_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:89a4606743b3bc26f5454b589c1d37b2836278939c55f8ac0957ebcd2eeeebcc -size 45398 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/694df81535f89c7bfb9ef0df6f130dc0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/694df81535f89c7bfb9ef0df6f130dc0_img.jpg deleted file mode 100644 index f30ed4fb897f06223b0e1d32dd05ffbd02a11e1c..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/694df81535f89c7bfb9ef0df6f130dc0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:480cd676f85954e1c451de1caa30bdce3049bb1ccd9259eb9fb8ce3fc020004e -size 67477 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6a5342571eca4b46338fdfb3c42a8055_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg deleted file mode 100644 index accde5ec6f3abefa28455f2329ab9c022ddf05cb..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6a993bfdf2e00cfad01c4d2188a75d86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ace7a87eebb5a84be48b697aeaa15ed709889d25335c5afb7de2daa3d69c6eaf -size 52385 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6b0834ca8cdd18832ed461378d51dcb7_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6c6024603c6fd57b23210b79f573b3bd_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6c8a96787f532bd1fa4719e738cf556f_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6d8454e3fdef6561c6f64adf0092e9b9_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6e15fc9ea763541c5913d26f85072ae1_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6e15fc9ea763541c5913d26f85072ae1_img.jpg deleted file mode 100644 index d67a605df35b833ed0b0909b0c9bd6b2b163f995..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6e15fc9ea763541c5913d26f85072ae1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:359395114cabc3c6ffd1c3b687b64eca2b21b3363b88bd0c0da8bce0eb0323e3 -size 55476 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/719ef0f734259484038b2434e5dc3f24_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/719ef0f734259484038b2434e5dc3f24_img.jpg deleted file mode 100644 index 6543546eb473238fa02a6ecb44a32423583020ab..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/719ef0f734259484038b2434e5dc3f24_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1264b7e1fee6c8bf7374482d27a9583002cc7d42f36aca1ccda9f7483e96b837 -size 73985 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/728298e0fbc8de5f3894ce6cb10fb413_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/72d448a65347c51989171748789c7d4b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/72d448a65347c51989171748789c7d4b_img.jpg deleted file mode 100644 index 359cdee360e690fbfda96b7cd8228a62a74349dc..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/72d448a65347c51989171748789c7d4b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9ce9ed86f9231aaa86b2e06718cd241e3c8997df1d2dc1f41a29fa6b0ee008cd -size 65358 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/7e12e1e0d03a03790d2e9d74c3454bff_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/7e12e1e0d03a03790d2e9d74c3454bff_img.jpg deleted file mode 100644 index 2855b20d5b43961621fb06d48930b65043d88823..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/7e12e1e0d03a03790d2e9d74c3454bff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:572b82e149eb400c1bb3dc6d309109ad996599319869416771021a91565e168d -size 50779 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/7f7211748473542096717109ebe5a9d6_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/7f7211748473542096717109ebe5a9d6_img.jpg deleted file mode 100644 index a165ee48f72879a87ffb6d3caf0cea6b8b7f660f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/7f7211748473542096717109ebe5a9d6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:25f013ecfb805f8954cbce3fc7933b781e37f564842ee3a0d86a2cbd941158ff -size 62058 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg deleted file mode 100644 index aa11db61ffe1fcae5c0deee5b290a8017751097d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ebdf9afa7e7378a0104216dd9b9cc632b3681d185ff22adb07bcdcf78a191ca5 -size 48780 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8237c46643affc7cc057ae950dbcf1f2_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/829cdaf00f7219d70e571064b2b13291_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/83ee9f10bd3636e192d68decf7f04cec_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/854df8ad60507803253274673f9062cf_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/86986d4dfd54f298d7b9fa9f82ab3009_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/86986d4dfd54f298d7b9fa9f82ab3009_img.jpg deleted file mode 100644 index 013ae77c7dd76ecbef4bbc10ce69a840e663cb8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/86986d4dfd54f298d7b9fa9f82ab3009_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9febe6b816f2c29dec12bf83250b540e0d89cbbfae4247cef0a18f919120ee4a -size 57596 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/87f8b579bc67022e8dd0a0a50585fd4d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/87f8b579bc67022e8dd0a0a50585fd4d_img.jpg deleted file mode 100644 index 2487039f0d35002ba96cf7a5f8b3282bf384043d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/87f8b579bc67022e8dd0a0a50585fd4d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d8cbd53d0f03bab2645f43ff4d9d73fb3d2f9db4c104dd3173373ec96c7db3fb -size 50154 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8ab30dbff406204a68c59ae7c1b77413_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8ab30dbff406204a68c59ae7c1b77413_img.jpg deleted file mode 100644 index bbb25e2997b0b3ad6eefc2eafdc6e4fc3b40a25b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8ab30dbff406204a68c59ae7c1b77413_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f5ccf14736e09db18b085701a764fdb0b41817669c3c8f7520fe87ae61daf7ce -size 55537 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8b4befaffc5166da571069410e207aea_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg deleted file mode 100644 index d3dd89fa5a565b338e4a453a2a087aa4496ab93b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a7543ad90877668af6233a60eda6adea8505c2a856cd97aa777acb272bc2a18e -size 43393 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8d138b6bf0be359dc7f079db4899bc41_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8e0160fd55391f6f2bbdef38ceb6f823_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8fa679f79a1bb1f527cba9f29e784e89_img.jpg deleted file mode 100644 index 2a6774b35889722b8ec46351252d2a40bf6f7896..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/8fa679f79a1bb1f527cba9f29e784e89_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0163ded9b155c0b6393d4ad7a1386c6e0ced7b1d2b99f9f57c069eade74b8b95 -size 46196 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/9156549264d36ead617a1dec7987f970_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg deleted file mode 100644 index a8b84283d44d182761c7251fc28132dd69da7204..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/9252ccfbbe9e34cb108f0060f2b563f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a7e1267e0037ef02f905ad98e937477862fcac9ae66a3ef21b5009e1f843e775 -size 65517 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/95e259e8cb3519025066052af263f8c0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/95e259e8cb3519025066052af263f8c0_img.jpg deleted file mode 100644 index 77cdaa5ebbb09c8bd3c6388451d5f8e27583a9a7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/95e259e8cb3519025066052af263f8c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d715712555556afee7a9f8f919d89a43d0d0b26e4c1e5ba0ca7d911168c80959 -size 59240 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/9c1d3678db4a12d5864cb2a4def1135d_img.jpg deleted file mode 100644 index 8b3f61e2570e00b044b7baf4ecf02886359f3ed4..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/9c1d3678db4a12d5864cb2a4def1135d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b957b5abdfe8691708fecdbc6983b447489da03d232d64392b62f26ced1e28e9 -size 39079 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg deleted file mode 100644 index 954f54be8e1d74f4cc292e7808c519463184d8ca..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/9e3c3a68ea23d6b0c0243f2baa1cb99f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f402f04adcba3c2fc9aaa68b6ece06ba8936df1204efc3835d4e15a11b5e8389 -size 53757 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/9f6dec4d4e9fde40bce018861ef1278e_img.jpg deleted file mode 100644 index 3485593eb87aeee14cbc1bca1d51343d3a168c4a..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/9f6dec4d4e9fde40bce018861ef1278e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:532b8246a02d1aad5357eb8ee33b364790ab1d1060ed79ea5f58a1352d31aa49 -size 57405 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg deleted file mode 100644 index b3c3382138c74990758af0111ff1d6ae9a8af160..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:beb5ad06ebfeca5788c32453b44a575c0b9bcd9ccd47989f184a2c7e895c72b5 -size 56422 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a0e8fe7862a6d7341faf5dac275277cc_img.jpg deleted file mode 100644 index a205dce72a4977bddda10f4dc6eb7821670293d9..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a0e8fe7862a6d7341faf5dac275277cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:867c10450db80840dc8ef36ea7049e193f47f885a88db494dfe1d3a951506a5e -size 59593 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg deleted file mode 100644 index b6ebfd081fb38cfca680b90157c100781c0ed6df..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:180afbea8b2bd485503bad5f911d9aa58e4e0dbb526fee0aad109a610ed8f5af -size 41466 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a5404b7275b06497eecf9b5883604753_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a5404b7275b06497eecf9b5883604753_img.jpg deleted file mode 100644 index 6c9843f81da9679e1cf3bc66bef9c4101b4f173d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a5404b7275b06497eecf9b5883604753_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:72ad6975a87238fd72d93da9887910b3fe0e435f68bd872826b9cca9e9818f05 -size 41991 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a76a30cf23764f0b907220e7c3c70ce1_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a76fa39f5daf6a026e032495262ed0f6_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a76fa39f5daf6a026e032495262ed0f6_img.jpg deleted file mode 100644 index d676260389e04da9deeb2ce7af40d80c91d8f8be..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a76fa39f5daf6a026e032495262ed0f6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:66cc6d531fddd04de3968219a3f35a17e24546dc4082c196f61e6336d9e615d9 -size 45436 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a7fcb275d0eed586509a47f4f86a9725_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/a9bb99d15f54792e1c9a14b1e465369a_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg deleted file mode 100644 index 0d3754dbef8461ade0e159a35c808fcdc41afab8..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e3cf55172f86950a82e6a6c1811feca3130cc7403a066fbf1d20e04050cdea6a -size 44722 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/aef4390a4629604196222b9ed006a786_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/aef4390a4629604196222b9ed006a786_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/aef4390a4629604196222b9ed006a786_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/b02ba0b73e95416eb547976f6145b169_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/b02ba0b73e95416eb547976f6145b169_img.jpg deleted file mode 100644 index f5341a7dd248ded6ed9bdbe1331d0c87504a83a0..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/b02ba0b73e95416eb547976f6145b169_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:007086e1ff093140d15bc6cbb630b13e22f475d8b0a0314413cf49fe8790ad40 -size 59955 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg deleted file mode 100644 index e5738ce2d36e651e4f957dbaa559026a9c82a90d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ffed61a3d6a76bc8f96845eb2b60c7ae3e2fdbda8dec077678453c8dd6e8c25d -size 43403 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/b0b9bc3067d012eb2fa3539217b9c34d_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/b0b9bc3067d012eb2fa3539217b9c34d_img.jpg deleted file mode 100644 index 3175e30c17e77d88e2c7a50a72003bbb02fb8159..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/b0b9bc3067d012eb2fa3539217b9c34d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2eecda19befcc2eadf73170f2f98cb067e1aada6c38834fcc9ac0ecbe528111b -size 62744 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/b3d488012fdceacab867cf24c5efef05_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/b3d488012fdceacab867cf24c5efef05_img.jpg deleted file mode 100644 index fa4aaabb0622de360dfab48748d55f5525f562e0..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/b3d488012fdceacab867cf24c5efef05_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:559c20425387c7b370e82d5c8ab69bab6c5b9813ab73c69b7d84cd2355c8f8a9 -size 48883 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg deleted file mode 100644 index 67cd0bb4ad5edfafe2e5d564484476f28d723678..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:890ceed8a7373af5dc4e6409326b47930cb0e366eb1253bc204523a63bad404e -size 32191 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/bffdddb47fced140f8d17fdc2a29f592_img.jpg deleted file mode 100644 index 043750eb06d31fe347cdda88a4d185b067b4faec..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/bffdddb47fced140f8d17fdc2a29f592_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:377d233e5cab1ff7320d01933bd4a1a773ba9444569ea9c0966f7abd11b65b01 -size 38076 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/c3254408eadbf152632a8faf16310722_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/c3254408eadbf152632a8faf16310722_img.jpg deleted file mode 100644 index 89191022a17ccf8df6cc197f2a7fdf5efe68dc61..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/c3254408eadbf152632a8faf16310722_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7f632cdeefdd54b358c16dfca6e8c6f37c2ad5e117258c0a80e4062ccf196de7 -size 145847 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/c389468860cd886ab9c732473e959f0f_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/c4315e81a5a818379fcf31519a9c2cbe_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/c6240283e2f65a6d02db47fa4ab0c518_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/c6240283e2f65a6d02db47fa4ab0c518_img.jpg deleted file mode 100644 index b0ad5344c7794df61c3ea426580c35fe5ccaa9f6..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/c6240283e2f65a6d02db47fa4ab0c518_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:86e9e40d1c2f2a1eb2812be30e06b2e241099146175edf9bc9e40a752f070c20 -size 52031 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg deleted file mode 100644 index a37dc8cc751b0c831b539bccee1ef4eef97e79a7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:88a1105440a76e8ffd670d947fc81e023cf0247ae0b875912a4e799db951eb44 -size 54307 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/cfb98c691c1af5befe32ff9442eea511_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/cfb98c691c1af5befe32ff9442eea511_img.jpg deleted file mode 100644 index 03f2279482c63a0aaada16133a29488973a1707c..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/cfb98c691c1af5befe32ff9442eea511_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6f0a33c0a7e41ff52c48d510702e69d3a42f700a1d811375126129162229ec0a -size 62146 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/d0516b99882398c64c90f71c12e808e2_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/d1ec9820fe8d23d83e066389a9cd7338_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/d35a80e3faed208324083399568c7461_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/d35a80e3faed208324083399568c7461_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/d35a80e3faed208324083399568c7461_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/d879e5f2c388bb87ee9614f63364dcf0_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg deleted file mode 100644 index 581d5d6195d354ed38aad062d7ca57d12bf93d42..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/d9ea7e6c55ac790700d27c96ba7f66a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e8b2022215052312c5a4312b9b538fb7bebce1e955ddd06080cac7d407dfdcfd -size 45955 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/da74b0e807fd62f32abdc3c05ffbabf4_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/da85343976fdbb19f866d9ddbdad0eae_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/da85343976fdbb19f866d9ddbdad0eae_img.jpg deleted file mode 100644 index 104f2ce45d941ad3a9b2234d88f2c17632f07a82..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/da85343976fdbb19f866d9ddbdad0eae_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5096c17ce7d620748eccbc80d21253c09b0a73fabaedfc866c1b1fb5e355f5d1 -size 70142 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/da8cb3d696f15f2c6de7aff6955d12d3_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/df495bddeb5d8826c7571714e6db1478_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/dfe556fea00682b09a59427aaf72051c_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/dfe556fea00682b09a59427aaf72051c_img.jpg deleted file mode 100644 index 61c3a146795e4c560fdaefb5bbd3e717365754bd..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/dfe556fea00682b09a59427aaf72051c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ee74094509d7dc0802a405a6405a8ab2d42308cd61bfb037ff1baa9209c89975 -size 53203 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e01c6273c4177746475715ee9c17a882_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e01c6273c4177746475715ee9c17a882_img.jpg deleted file mode 100644 index f652dd8c40e6ec409ee48cab6cf46d050e35c75b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e01c6273c4177746475715ee9c17a882_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3e27ceb0267b56076356bcce5956830767665dce3d726a31b3899ce44f4e6a09 -size 59525 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e05b36c0d46549e681ce6581422c66b2_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e05b36c0d46549e681ce6581422c66b2_img.jpg deleted file mode 100644 index dc2346f700a39281e283696133fea5125a10a96a..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e05b36c0d46549e681ce6581422c66b2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:636d45b4f83b0d14c68ba24d811bc380145f056478aeae38eb22c12a0cf1b817 -size 63052 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg deleted file mode 100644 index 63734bde3f1f19509d0441f8b9a1c3dda58a0029..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e180f2b5fcbe8001554a7c0677cd3f82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1cb8ca84a2aa1b71cde9c6f5f4f9f75a46637e59f62fd74054452bf25d18400b -size 46501 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e18841eb4a995df8354a793459e12fd0_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e18841eb4a995df8354a793459e12fd0_img.jpg deleted file mode 100644 index f720c0f04470d41f19ea1365c7c5cdbd75113c94..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e18841eb4a995df8354a793459e12fd0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:34a1e0d2fe107fb08f42711100646516f0be66b2284f75303934102d0bb190a8 -size 46429 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e2245b4865907ad1259fd155f4beb6cf_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e2245b4865907ad1259fd155f4beb6cf_img.jpg deleted file mode 100644 index 3f5748220a7bea0f661ad73a5a96a91514b366cc..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e2245b4865907ad1259fd155f4beb6cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33a139eb1d5926c27619b9876d207480a8d28db49ad02a79558920859344f670 -size 60678 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e32e1bcf367a284cc7a4186056810d22_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e7010c66da16316c2935dfbbef5056b3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e7010c66da16316c2935dfbbef5056b3_img.jpg deleted file mode 100644 index e7016fdbac134f34980743ed590a70a2b2a2142c..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e7010c66da16316c2935dfbbef5056b3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1230eab8b2908c4f46c5c56acef5dceb8861eae722451f0737db3873c58a3498 -size 55723 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e882a6bdfd0e868314f3a26f536145a3_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg deleted file mode 100644 index 50ce4d7e92ff5fa0fca448a5327dd8d424e1a429..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:180e48cf206ff2ae619f6ed8d232c61c8c374ed47ad568a4209381caab52fe1a -size 54850 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/eabcb2f8b9acedb194571d5bc734b463_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/eabcb2f8b9acedb194571d5bc734b463_img.jpg deleted file mode 100644 index afbb9460e7517187bd3de34825cc059d6fb52baf..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/eabcb2f8b9acedb194571d5bc734b463_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9a0b45dbf3161ebefa1963f1559d262c81bb46dba18c2ae698b8560520d97fcd -size 67250 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg deleted file mode 100644 index 62fb71711f97d3a1df97125833904b14c212d017..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f9a176b773d0a423779e007851f2dbdee8b6efb1261414303b847da711544960 -size 97431 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/f61d0925551545b5938b3a4d1bbf63c3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/f61d0925551545b5938b3a4d1bbf63c3_img.jpg deleted file mode 100644 index 6fb40493d4c23813285cd8ab3e3097a54c23e88b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/f61d0925551545b5938b3a4d1bbf63c3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d8a8000621f53fe6e1179176f87b577efa7390e397f1b4fd0ee0cc1cc316104a -size 61283 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/f929e9fcf3f37d82af20f84f9c8b942a_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg deleted file mode 100644 index 6ea9d6d029226abda4dc2290b8c5276d47bfe80d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3e7562b3ca7cd89e9bf796cc9d5c869ff6f7e2dbcd85b42fd9a1b25cd68305a3 -size 45528 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/facce731b2dbfae43a8609231a700be1_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/facce731b2dbfae43a8609231a700be1_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/facce731b2dbfae43a8609231a700be1_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/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/fcc757566216206ceddbd6c775e8db02_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/fcc757566216206ceddbd6c775e8db02_img.jpg deleted file mode 100644 index d759516602df2c8f0eb55d5a28fe1690233a8a74..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/fcc757566216206ceddbd6c775e8db02_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0460ee8df1eb6aa4d2b2d29c545e6308fa0a7320193a59fbb7d48797d1e92b39 -size 48576 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 6d148e5c5aeadf9fa2a25a7ba6c7c8e3ebcf5cc5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:37fc40475798ddc0c3681dd541b84a426d3b11ea065ba8491c3a15abebad9e14 -size 4537 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/fed4a04822c24fb22cca3a14f4ddae83_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/fed4a04822c24fb22cca3a14f4ddae83_img.jpg deleted file mode 100644 index e4aa9a997048f0c02a63a1883ad7a410b241d0b4..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/fed4a04822c24fb22cca3a14f4ddae83_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b4978957d7191bfc8afb941966dbd593e36f1a3b4ac8d2025241db45769ad43e -size 160516 diff --git a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.R1UCR-R005-v12.00/images/ff748955b94dcb8337283fbe12baa475_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/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/doc.md b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/doc.md deleted file mode 100644 index 28bbda62e59eaf4a87a438f1eb343c3d9b1733d0..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/doc.md +++ /dev/null @@ -1,7517 +0,0 @@ - - -# --- Non-RT RIC & A1/R1 interface: Use Cases and Requirements - -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., Buschkauer 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..... | 8 | -| 3.3 Abbreviations ..... | 8 | -| 4 Use cases..... | 9 | -| 4.1 Traffic steering ..... | 9 | -| 4.1.1 Background and goal of the use case..... | 9 | -| 4.1.2 Entities/resources involved in the use case..... | 10 | -| 4.1.3 Solutions ..... | 10 | -| 4.1.4 Required data..... | 17 | -| 4.1.5 A1 usage example..... | 18 | -| 4.1.6 Enrichment information example ..... | 20 | -| 4.1.7 A1 usage example in multi-access environment ..... | 21 | -| 4.2 QoE optimization ..... | 24 | -| 4.2.1 Background and goal of the use case..... | 24 | -| 4.2.2 Entities/resources involved in the use case..... | 25 | -| 4.2.3 Solutions ..... | 25 | -| 4.2.4 Required data..... | 31 | -| 4.2.5 A1 usage example..... | 32 | -| 4.3 QoS based resource optimization..... | 33 | -| 4.3.1 Background and goal of the use case..... | 33 | -| 4.3.2 Entities/resources involved in the use case..... | 34 | -| 4.3.3 Solutions ..... | 34 | -| 4.3.4 Required data..... | 38 | -| 4.3.5 A1 usage example..... | 38 | -| 4.4 Context-based dynamic HO management for V2X ..... | 41 | -| 4.4.1 Background and goal of the use case..... | 41 | -| 4.4.2 Entities/resources involved in the use case..... | 41 | -| 4.4.3 Solutions ..... | 42 | -| 4.4.4 Required data..... | 45 | -| 4.4.5 Proposed solution(s) ..... | 45 | -| 4.4.6 A1 enrichment interface aspects..... | 46 | -| 4.4.7 A1 usage example..... | 47 | -| 4.5 RAN slice SLA assurance..... | 48 | -| 4.5.1 Background and goal of the use case..... | 48 | -| 4.5.2 Entities/resources involved in the use case..... | 48 | -| 4.5.3 Solutions ..... | 49 | -| 4.5.4 Required data..... | 57 | -| 4.5.5 A1 usage example..... | 58 | -| 4.5.6 O1 usage example..... | 61 | -| 4.6 NSSI resource allocation optimization..... | 62 | -| 4.6.1 Background and goal of the use case..... | 62 | -| 4.6.2 Entities/resources involved in the use case..... | 63 | -| 4.6.3 Solutions ..... | 63 | -| 4.6.4 Required data..... | 69 | -| 4.6.5 O1 usage example..... | 70 | - -| | | | -|-------|----------------------------------------------------------------------------------------------------|-----| -| 4.7 | Massive MIMO optimization..... | 71 | -| 4.7.1 | Massive MIMO Grid-of-Beams Beamforming (GoB BF) optimization..... | 71 | -| 4.7.2 | Massive MIMO Non-GoB Beamforming (Non-GoB BF) optimization..... | 77 | -| 4.7.3 | MIMO optimization via MIMO DL Tx power optimization, MU-MIMO pairing, and MIMO mode selection..... | 86 | -| 4.7.4 | AI/ML-based initial access (SS Burst Set) configuration optimization..... | 91 | -| 4.8 | Network energy saving..... | 96 | -| 4.8.1 | Carrier and cell switch off/on..... | 96 | -| 4.8.2 | RF channel reconfiguration..... | 112 | -| 4.8.3 | Advanced sleep mode..... | 126 | -| 4.8.4 | Time domain cell DTX/DRX optimization (3GPP Rel-18)..... | 135 | -| 4.8.5 | Spatial and power domain optimization (3GPP Rel-18)..... | 142 | -| 4.8.6 | SSB-less SCell optimization for inter-band CA (3GPP Rel-18)..... | 149 | -| 4.8.7 | PA power optimization for O-RU energy saving..... | 156 | -| 4.8.8 | External power source coordination-based energy saving..... | 163 | -| 4.9 | O-Cloud resource optimization..... | 170 | -| 4.9.1 | Use case: O-Cloud node draining use case..... | 170 | -| 5 | Requirements..... | 184 | -| 5.1 | Functional requirements..... | 184 | -| 5.1.1 | Non-RT RIC functional requirements..... | 184 | -| 5.1.2 | A1 interface functional requirements..... | 185 | -| 5.1.3 | R1 interface functional requirements..... | 185 | -| 5.2 | Non-functional requirements..... | 186 | -| 5.2.1 | Non-RT RIC non-functional requirements..... | 186 | -| 5.2.2 | A1 interface non-functional requirements..... | 186 | -| 5.2.3 | R1 interface non-functional requirements..... | 187 | -| | Annex (informative): Change history/Change request (history)..... | 188 | - -# --- Foreword - -This Technical Specification (TS) has been produced by WG2 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 WG2 Non-RT RIC Use Cases and Requirements, including A1 and R1 interfaces. - -# 1 Scope - -The present document specifies the RAN optimization and control related use cases that have been approved within O-RAN WG2. The purpose of the use cases is to help identify requirements for O-RAN defined interfaces and functions, specifically Non-RT RIC function and A1 and R1 interfaces, eventually leading to formal drafting of interface specifications. For each use case, the document describes the motivation, resources, steps involved, and data requirements. Finally, the requirements clause details the functional and non-functional requirements derived from these use cases. - -# 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: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for the 5G system; Stage 1” -- [2] 3GPP TS 23.501: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2” -- [3] 3GPP TS 28.530: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; Concepts, use cases and requirements” -- [4] 3GPP TS 28.541: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3” -- [5] 3GPP TS 28.552: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; 5G performance measurements” -- [6] 3GPP TS 36.314: “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements” -- [7] 3GPP TS 38.314: “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Layer 2 Measurements” -- [8] 3GPP TS 37.340: “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage 2” -- [9] GSMA: “Generic Network Slice Template Version 4.0”, November 2020 -- [10] O-RAN TS: “Management Plane Specification” (“MP”) - -- [11] 3GPP TS 32.423: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Subscriber and equipment trace; Trace data definition and management” -- [12] O-RAN TS: “Control, User and Synchronization Plane Specification” (“CUS”) -- [13] O-RAN TS: “O2 Interface General Aspects and Principles” (“O2-GA&P”) -- [14] O-RAN TS: “Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN” (“ORCH-USE-CASES”) -- [15] O-RAN TS: “Slicing Architecture” -- [16] O-RAN TS: “Near-Real-time RAN Intelligent Controller E2 Service Model (E2SM) KPM” (“E2SM-KPM”) -- [17] 3GPP TS 28.554: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; 5G end to end Key Performance Indicators (KPI)” -- [18] 3GPP TS 32.422: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Subscriber and equipment trace; Trace control and configuration management” -- [19] 3GPP TS 37.320: “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2” -- [20] 3GPP TS 38.331: “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification” -- [21] 3GPP TS 38.300: “NR; NR and NG-RAN Overall Description; Stage 2” -- [22] 3GPP TS 38.306: “NR; User Equipment (UE) radio access capabilities” -- [23] 3GPP TS 28.558: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; UE level measurements for 5G system” -- [24] O-RAN TS: “A1 interface: Type Definitions” (“A1TD”) -- [25] 3GPP TS 28.310: “Management and orchestration; Energy efficiency of 5G”, V19.1.0 (2025-06) - -## 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] 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.3] O-RAN.WG1.MMIMO-USE-CASES-TR-v01.00: “O-RAN Working Group 1, Massive MIMO Use Cases”, Technical Report, March 2022 -- [i.4] ETSI ES 203 228, Environmental Engineering (EE); Assessment of mobile network energy efficiency -- [i.5] ETSI ES 202 706-1, Metrics and measurement method for energy efficiency of wireless access network equipment; Part 1: Power consumption - static measurement method - -# --- 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the terms and definitions [given in 3GPP TR 21.905 [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 3GPP TR 21.905 [i.1]. - -**A1:** Interface between orchestration/NMS layer containing Non-RT RIC and eNB/gNB containing Near-RT RIC. - -**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 between Near-RT RIC and the Multi-RAT CU protocol stack and the underlying RAN DU. - -**E2 node:** O-CU-CP, O-CU-UP, O-DU, O-gNB, O-eNB. - -**Energy consumption:** Integral of power consumption over time [i.5]. - -**Energy efficiency:** Relation between the useful output and energy/power consumption [i.4]. - -**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 in the SMO framework 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. The Non-RT RIC is comprised of the Non-RT RIC framework and Non-RT RIC applications (rApps). - -**Non-RT RIC framework:** Functionality internal to the SMO framework that logically terminates the A1 interface and provides the R1 services to rApps through the R1 interface. - -**NMS:** A Network Management System. - -**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 (e.g., 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. - -**rApp:** Non-RT RIC application: An application designed to consume and /or produce R1 Services. - -**NOTE:** rApps can leverage the functionality provided by the SMO and Non-RT RIC framework to deliver value added services related to intelligent RAN optimization and operation. - -**R1 interface:** Interface between rApps and Non-RT RIC framework via which R1 Services can be produced and consumed. - -**R1 services:** A collection of services including, but not limited to, service registration and discovery services, authentication and authorization services, AI/ML workflow services, and A1, O1 and O2 interface related services. - -## 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. 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]. - -| | | -|-----|----------------------------------| -| 5QI | 5G Quality of Service Identifier | -| ASM | Advanced Sleep Mode | -| CAM | Cooperative Awareness Message | -| 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 | - -| | | -|--------|-----------------------------------------| -| m-MIMO | Massive Multiple Input, Multiple Output | -| MBB | Mobile BroadBand | -| QoE | Quality of Experience | -| RIC | O-RAN RAN Intelligent Controller | -| SINR | Signal-to-Interference-plus-Noise Ratio | -| SMO | Service Management and Orchestration | -| SSB | Synchronization Signal Block | - -# --- 4 Use cases - -## 4.1 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.1.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). 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) - -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 [8]). 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 either cell-centric or UE-centric. Even in different areas 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 both cell- and UE-centric algorithms do exist. - -Such current solutions suffer from following limitations: - -- 1) It is hard to adapt the RRM control to diversified scenarios and optimization objectives. - -2) 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. - -3) 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.1.2 Entities/resources involved in the use case - -- 1) SMO (including 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) Retrieve necessary performance, configuration, and other data for performing data statistical analysis that will provide enrichment information for Near-RT RIC to assist in the traffic steering function. For example, this could be an analysis method to construct radio fingerprint based on UE measurement report with RSRP/RSRQ/CQI information for serving and neighbouring cells. - - c) Support communication of policies to Near-RT RIC. - - d) Support communication of measurement configuration parameters to RAN nodes. - - e) Support communication of enrichment information to Near-RT RIC, e.g., radio fingerprint information, etc. -- 2) Near-RT RIC: - - a) Support interpretation and enforcement of policies from Non-RT RIC. - - b) Support using enrichment information to optimize control function, e.g., Near-RT RIC can use radio fingerprint to directly predict the inter-frequency cell measurement based on the intra-frequency cell measurement result to speed up the traffic steering with much reduced signaling overhead. -- 3) E2 nodes: - - a) Support data collection with required granularity to SMO over O1 interface. - -### 4.1.3 Solutions - -#### 4.1.3.1 Traffic steering – policy part - -The context of traffic steering – policy part is captured in table 4.1.3.1-1. - -**Table 4.1.3.1-1: Traffic steering – policy part** - -| 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. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - A1 and 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 can request via SMO 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
  • c) Preferences on user traffic distribution over primary cells and secondary cells
  • d) Preferences on which carriers to be used for primary component carriers and secondary component carriers in multiple frequency coordination to optimize user traffic distribution
| | -| Step 3 (M) | The Near-RT RIC receives relevant information 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 are 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. | | -| Traceability |
  • - REQ-Non-RT-RIC-FUN1, REQ-Non-RT-RIC-FUN2, REQ-Non-RT-RIC-FUN3, REQ-Non-RT-RIC-FUN4, REQ-Non-RT-RIC-FUN5
  • - REQ-A1-FUN1
  • - REQ-Non-RT-RIC-NonFUN1, REQ-Non-RT-RIC-NonFUN2
| | - -``` -@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 - smo -> non : Data retrieval -end - -non -> non : Decision of optimization action - -group A1 Policies - non -> near : <> Traffic steering policy create message - near -> ran : <> Traffic steering 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 steering policy delete message -end -@enduml - -``` - -Traffic steering use case flow diagram given in figure 4.1.3.1-1 illustrates the overall procedure for the traffic steering use case. - -![Sequence diagram for Traffic steering use case flow. Lifelines: Collection & Control, non-RT RIC, near-RT RIC, E2 Nodes. The process involves data collection, performance monitoring, decision making, policy creation/enforcement, and policy deletion/enforcement.](cab0834804fb031b43865554cc8d06ab_img.jpg) - -``` - -sequenceDiagram - box "Service Management and Orchestration" - participant CC as Collection & Control - participant nRT as non-RT RIC - end - box "O-RAN" - participant nearRT as near-RT RIC - participant EN as E2 Nodes - end - - CC->>nRT: 1 <> Data collection - nRT-->>CC: 2 Data retrieval - nRT->>nRT: 3 Performance monitoring and evaluation - nRT->>nRT: 4 Performance trigger for traffic steering - - rect rgb(255, 255, 255) - Note over CC, EN: 01 additional data collection - CC->>nRT: 5 <>Request additional measurements - nRT->>EN: 6 <> PM measurement configuration - CC->>nRT: 7 <> Data collection - nRT-->>CC: 8 Data retrieval - end - - nRT->>nRT: 9 Decision of optimization action - - rect rgb(255, 255, 255) - Note over nRT, nearRT: A1 Policies - nRT->>nearRT: 10 <> Traffic steering policy create message - nearRT->>nearRT: 11 Traffic steering enforcement - end - - CC->>nRT: 12 <> Data collection - nRT-->>CC: 13 Data retrieval - nRT->>nRT: 14 Performance monitoring and evaluation - nRT->>nRT: 15 Decision to remove policy - - rect rgb(255, 255, 255) - Note over nRT, nearRT: A1 Policies - nRT->>nearRT: 16 <> Traffic steering policy delete message - nearRT->>nearRT: 17 Traffic steering enforcement - end - -``` - -Sequence diagram for Traffic steering use case flow. Lifelines: Collection & Control, non-RT RIC, near-RT RIC, E2 Nodes. The process involves data collection, performance monitoring, decision making, policy creation/enforcement, and policy deletion/enforcement. - -Figure 4.1.3.1-1: Traffic steering use case flow diagram - -#### 4.1.3.2 Traffic steering – EI part - -The context of traffic steering – EI part is captured in table 4.1.3.2-1. - -Table 4.1.3.2-1: Traffic steering - EI part - -| Use Case Stage | Evolution / Specification | <> | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Goal | Assist in traffic optimization in RAN in accordance with produced enrichment information. | | -| Actors and Roles | Non-RT RIC: Enrichment information generation function.
Near-RT RIC: Enrichment information consumption 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 and 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.
  • - Non-RT RIC performs data analytics to generate/update the enrichment information.
| | -| Begins when | Operator specified trigger condition or event is detected. | | -| Step 1 (O) | If required, Non-RT RIC can request via SMO additional, more specific, performance measurement data to be collected from E2 nodes to assess the performance. | | -| Step 2 (M) | When receiving EI request/subscription message from Near-RT RIC, Non-RT RIC responds/notifies relevant enrichment information to Near-RT RIC over A1. The example enrichment information can include:

a) Radio fingerprint | | -| Step 3 (M) | The Near-RT RIC uses the enrichment information to optimize control function. | | -| Step 4 (M) | In the EI subscription-notification mode, if there is an update on enrichment information. Non-RT RIC notifies the updated enrichment information to Near-RT RIC over A1 for optimizing control function. | | -| Stop When | In the EI subscription-notification mode, EI notification continues until Non-RT RIC receives unsubscription message from Near-RT RIC. | | -| Exceptions | None identified. | | -| Post Conditions | Non-RT RIC monitors the performance by collecting the relevant performance events and counters from E2 nodes via SMO. | | -| Traceability |
  • - REQ-Non-RT-RIC-FUN1, REQ-Non-RT-RIC-FUN2, REQ-Non-RT-RIC-FUN3, REQ-Non-RT-RIC-FUN5, REQ-Non-RT-RIC-FUN7
  • - REQ-A1-FUN2
| | - -| Use Case Stage | Evolution / Specification | <> | -|----------------|--------------------------------------------------|-------------| -| | | Related use | -| | - REQ-Non-RT-RIC-NonFUN1, REQ-Non-RT-RIC-NonFUN2 | | - -``` - -@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 - smo -> non : Data retrieval -end - -non -> non : Decision of optimization action - -``` - -``` -group A1 Policies - non -> near : <> Traffic steering policy create message - near -> ran : <> Traffic steering enforcement -end - -non -> non : Performance monitoring and evaluation -non -> non : Decision to remove policy -group A1 Policies - non -> near : <> Traffic steering policy delete message -end - -ran -> smo : <> Data collection -smo -> non : Data retrieval of RAN and non-RAN data - -group Alt 1:A1 Enrichment Information - near -> non : <> Traffic steering enrichment information request message - non -> near: <> Traffic steering enrichment information response message - near -> ran: <> Use the enrichment information to optimize control function -end - -group Alt 2:A1 Enrichment Information - near -> non : <> Traffic steering enrichment information subscription message - non -> near: <> Traffic steering enrichment information notification message - near -> ran: <> Use the enrichment information to optimize control function - non -> non : Update the enrichment information - non -> near: <> Traffic steering enrichment information notification message - near -> ran: <> Use the enrichment information to optimize control function - near -> non: <> Traffic steering enrichment information unsubscription message - non -> near: <> Traffic steering enrichment information unsubscription -confirmation message -end - -@enduml -``` - -Traffic steering use case flow diagram (with EI part) is given in figure 4.1.3.2-1. - -![Sequence diagram for Traffic steering use case flow (with EI part). Lifelines: Service Management and Orchestration (Collection & Control, non-RT RIC), O-RAN (near-RT RIC, E2 Nodes). The diagram shows interactions for data collection, policy creation, and enrichment information handling.](2cde062fd82833415971a8bd1a2cafab_img.jpg) - -``` - -sequenceDiagram - participant SM as Service Management and Orchestration - subgraph SM [Service Management and Orchestration] - CC[Collection & Control] - nRT[non-RT RIC] - end - subgraph ORAN [O-RAN] - nRTic[near-RT RIC] - EN[E2 Nodes] - end - - Note left of SM: Service Management and Orchestration - Note right of ORAN: O-RAN - - nRT->>CC: 1 <> Data collection - CC->>nRT: 2 Data retrieval - nRT->>EN: 3 Performance monitoring and evaluation - EN->>nRT: 4 Performance trigger for traffic steering - - Note left of SM: O1 Data collection - CC->>EN: 5 Request additional measurements - EN->>CC: 6 <> PM measurement configuration - CC->>EN: 7 <> Data collection - EN->>CC: 8 Data retrieval - - nRT->>EN: 9 Decision of optimization action - - Note left of SM: A1 Policies - nRT->>EN: 10 <> Traffic steering policy create message - EN->>nRT: 11 <> Traffic steering enforcement - - nRT->>EN: 12 Performance monitoring and evaluation - EN->>nRT: 13 Decision to remove policy - - Note left of SM: A1 Policies - nRT->>EN: 14 <> Traffic steering policy delete message - - nRT->>CC: 15 <> Data collection - CC->>nRT: 16 Data retrieval of RAN and non-RAN data - nRT->>EN: 17 Enrichment information generation/update - - Note left of SM: ALT 1: A1 Enrichment Information - nRT->>EN: 18 <> Traffic steering enrichment information request message - EN->>nRT: 19 <> Traffic steering enrichment information response message - nRT->>EN: 20 <> Use the enrichment information to optimize control function - - Note left of SM: ALT 2: A1 Enrichment Information - nRT->>EN: 21 <> Traffic steering enrichment information subscription message - EN->>nRT: 22 <> Traffic steering enrichment information notification message - nRT->>EN: 23 <> Use the enrichment information to optimize control function - - nRT->>EN: 24 Update the enrichment information - EN->>nRT: 25 <> Traffic steering enrichment information notification message - nRT->>EN: 26 <> Use the enrichment information to optimize control function - - nRT->>EN: 27 <> Traffic steering enrichment information unsubscription message - EN->>nRT: 28 <> Traffic steering enrichment information unsubscription confirmation message - -``` - -Sequence diagram for Traffic steering use case flow (with EI part). Lifelines: Service Management and Orchestration (Collection & Control, non-RT RIC), O-RAN (near-RT RIC, E2 Nodes). The diagram shows interactions for data collection, policy creation, and enrichment information handling. - -Figure 4.1.3.2-1: Traffic steering use case flow diagram (with EI part) - -### 4.1.4 Required data - -The measurement counters and KPIs (as defined by 3GPP and will be extended for O-RAN use cases) should be appropriately aggregated by cell, QoS type, slice, etc. - -- 1) Measurement reports with RSRP/RSRQ/CQI information for serving and neighboring cells. In multi-access scenarios this will also include intra-RAT and inter-RAT measurement reports, cell quality thresholds, CGI reports and measurement gaps on per-UE or per-frequency. -- 2) UE connection and mobility/handover statistics with indication of successful and failed handovers, other metrics including threshold of number of UEs to trigger traffic management at O-DU, O-CU-CP, etc. -- 3) Cell load statistics such as information in the form of number of active users or connections, number of scheduled active users per TTI, PRB utilization, and CCE utilization, bearer metrics such as number of bearers to trigger traffic management at O-DU, O-CU-CP, etc. -- 4) Per user performance statistics such as PDCP throughput, RLC or MAC layer latency, DL throughput thresholds to trigger traffic management at O-DU, O-CU-CP, etc. - -### 4.1.5 A1 usage example - -An example scenario is here used to describe the use of A1 for traffic management, implying the Non-RT RIC sending policies for allocation of the control plane (RRC) and the user plane for different services, identified by their 5QI. - -In the scenario a UE with UEid=1, belonging to a subnet slice identified by S-NSSAI=1, having a voice (5QI=1) and an MBB (5QI=9) connection established, enters an area covered by four frequency bands. The Non-RT RIC understands the requirements and characteristics of the services and decides to let the voice and RRC connection reside on the low band (here covered by a macro cell B becoming the PCell), while the MBB connection should preferably use the higher band (here provided by a smaller cell C and D becoming the SCells) and avoid the low band if possible. Cell A is used for MBB if required for coverage reasons. - -Policies are sent to any cell of concern, e.g., where the UE resides and can move. - -The desired use of the cells is shown in figure 4.1.5-1. - -![Diagram showing four cells (A, B, C, D) and their characteristics. Cell A is a macro cell with low band, narrow bandwidth, and low latency. Cell B is a macro cell with high band, wide bandwidth, and high latency. Cells C and D are smaller cells. A UE is shown moving from Cell A towards Cell B. Arrows indicate that MBB traffic should use Cell A or C/D, while RRC and Voice traffic should use Cell B.](77464a47f104d0d647b2414591137b64_img.jpg) - -The diagram illustrates a network scenario with four cells: Cell A, Cell B, Cell C, and Cell D. Cell A is a macro cell on the left, and Cell B is a macro cell on the right. Cells C and D are smaller cells located between A and B. A UE (User Equipment) is shown moving from Cell A towards Cell B. Above Cell A, text indicates 'Low band', 'Narrow bandwidth', and 'Low latency'. Above Cell B, text indicates 'High band', 'Wide bandwidth', and 'High latency'. Below the cells, an arrow labeled 'MBB' points from Cell A towards Cell C and D. Another arrow labeled 'RRC and Voice' points from Cell B towards the UE. - -Diagram showing four cells (A, B, C, D) and their characteristics. Cell A is a macro cell with low band, narrow bandwidth, and low latency. Cell B is a macro cell with high band, wide bandwidth, and high latency. Cells C and D are smaller cells. A UE is shown moving from Cell A towards Cell B. Arrows indicate that MBB traffic should use Cell A or C/D, while RRC and Voice traffic should use Cell B. - -**Figure 4.1.5-1: Desired use of the cells** - -Two policies over A1 are needed to accomplish the desired behavior, described in JSON format below. Note that as part of the scope, the cell\_id is optional, and if omitted it is up to the Near-RT RIC to locate the UE and there enforce the policy. - -``` -{ - "policy_id": "1", - "scope": { - "ue_id": "1", - "slice_id": "1", - "qos_id": "1", - "cell_id": "X" // Policy for Cell X, where X is one of A, B, C or D - }, - "statement": { - "cell_id_list": "B", - "preference": "Shall", - "primary": true // Control plane and voice on Cell B (becoming PCell) - } -} -``` - -``` - -} - -{ - "policy_id": "2", - "scope": { - "ue_id": "1", - "slice_id": "1", - "qos_id": "9", - "cell_id": "X" // Policy for Cell X, where X is one of A, B, C or D - }, - "statement": { - "cell_id_list": {"B", "A"}, - "preference": "Avoid", - "primary": false // Avoid MBB on Cell A and Cell B - }, - "statement": { - "cell_id_list": {"C", "D"}, - "preference": "Prefer", - "primary": false // Prefer MBB on Cell C and Cell D - } -} - -``` - -Besides the cell level preference policy, there are also carrier level preference policy for the traffic steering use case. Taking the above scenario as an example, the UE with UEid=1, belonging to a subnet slice identified by S-NSSAI=1, having a voice (5QI=1) and an MBB (5QI=9) connection established, enters the area covered by four cells identified by cell A, cell B, cell C and cell D, respectively. - -Assuming that cell A and cell B work on the same frequency carrier which can be identified by Arfcn\_1, cell C and cell D work on the same frequency carrier which can be identified by Arfcn\_2. Carrier Arfcn\_1 is in low frequency and have narrow bandwidth and adapt to voice (5QI=1) connection. Carrier Arfcn\_2 is in high frequency and have wide bandwidth and adapt to MBB (5QI=9) connection, meanwhile, avoid connection to the low frequency bands. - -The following policies are needed to accomplish this as described in JSON format below. - -``` - -{ - "policy_id": "1", - "scope": { - "ue_id": "1", - "slice_id": "1", - "qos_id": "1", - "cell_id": "X" // Policy for Cell X, where X is one of A, B, C or D - }, - -``` - -``` - - "statement": { - - "carrier_id_list": "Arfcn_1", - - "preference": "Prefer", - - "primary": true // Control plane on Carrier Arfcn_1 (becoming Primary Component Carrier) - - }, - -} - -{ - - "policy_id": "2", - - "scope": { - - "ue_id": "1", - - "slice_id": "1", - - "qos_id": "9", - - "cell_id": "X" // Policy for Cell X, where X is one of A, B, C or D - - }, - - "statement": { - - "carrier_id_list ": "Arfcn_1", - - "preference": "Avoid", - - "primary": false // Avoid MBB on Carrier Arfcn_1, and no carrier in the carrier_id_list is to -be used as secondary component carrier. That is said, Arfcn_1 is not used as secondary component -carrier, because it is already used for primary component carrier as the policy 1 stated. - - }, - - "statement": { - - "carrier_id_list": "Arfcn_2", - - "preference": "Prefer", - - "primary": false // Prefer MBB on Carrier Arfcn_2, and Arfcn_2 is used as secondary component -carrier - - } - -} - -``` - -### 4.1.6 Enrichment information example - -Radio fingerprint is composed of multiple virtual grids. The virtual grids are constructed based on the historical report of intra-frequency and inter-frequency measurement results of UEs from both the serving cell and the neighbor cell. The serving cell is divided into multiple grids according to the signaling measurement difference. It can be seen as a kind of different space partition method which is different with the traditional space partition method based on geographical location. To construct the radio fingerprint, the grid index and the grid attributes need to be defined. The grid index is to identify a specific virtual grid and this index consists of cell ID and corresponding coverage quality, e.g., RSRP segment ID, of at least three intra-frequency cells. The grid attributes are used to describe the wireless characteristics of the grid, such as coverage of inter-frequency neighbor cells, including RSRP, Reference Signal Receiving Quality (RSRQ), Received Signal Strength Indication (RSSI), Channel Quality Indicator (CQI), Modulation and Coding Scheme (MCS), - -beam ID, etc., handover performance indicators, and so on. The virtual grids of the radio fingerprint are shown in figure 4.1.6-1. - -![Illustration of the virtual grid of radio fingerprint. It shows a 'Serving Cell' represented by a circle containing a 3D grid of cubes. An arrow labeled 'IntraFreq MR from UEs' points to the grid. To the right, a box titled 'Grid i' contains an 'Index' section with 'ServingCell ID, RSRP Segment ID, IntraFreq_NeighborCell_1 ID, RSRP Segment ID, IntraFreq_NeighborCell_2 ID, RSRP Segment ID' and an 'Attribute' section with 'Coverage of inter-freq neighbor cells, e.g. RSRP, RSRQ, RSSL, CQI, Handover performance indicators, UE lists, etc.'](79e1709a7317ead45379cbb8ff3ba802_img.jpg) - -Illustration of the virtual grid of radio fingerprint. It shows a 'Serving Cell' represented by a circle containing a 3D grid of cubes. An arrow labeled 'IntraFreq MR from UEs' points to the grid. To the right, a box titled 'Grid i' contains an 'Index' section with 'ServingCell ID, RSRP Segment ID, IntraFreq\_NeighborCell\_1 ID, RSRP Segment ID, IntraFreq\_NeighborCell\_2 ID, RSRP Segment ID' and an 'Attribute' section with 'Coverage of inter-freq neighbor cells, e.g. RSRP, RSRQ, RSSL, CQI, Handover performance indicators, UE lists, etc.' - -Figure 4.1.6-1: Illustration of the virtual grid of radio fingerprint - -### 4.1.7 A1 usage example in multi-access environment - -The Non-RT RIC can send policies for traffic distribution in a multi-access environment based on UE characteristics and traffic patterns for different services that can be identified by their 5QI. The following example scenario illustrates this, in which there are three UEs with the following characteristics. - -| | | | | -|------------------|-----------------------------------|----------------------------------------------------------|-----------------------------------------------------------------| -| 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 | -| Mobility Pattern | Stationary | High mobility | Low mobility | - -The UEs are in an area covered by three frequency bands identified by cell A, cell B and cell C respectively. Cell A is the macro licensed cell with the best coverage. Cell B is the unlicensed cell with limited coverage and cell C is a licensed cell with narrow bandwidth but provides greater coverage area than cell B. - -The cell layout for multi-access use case is shown in figure 4.1.7-1. - -![Cell layout for multi-access use case. It shows three overlapping ellipses representing coverage areas: Cell A (Licensed band, large orange ellipse), Cell B (Unlicensed band, small green ellipse), and Cell C (Narrow bandwidth licensed band, medium blue ellipse). UE Id=1 (stationary) is in Cell B. UE Id=2 (high mobility) is in Cell C with a dashed arrow pointing towards Cell A. UE Id=3 (low mobility) is in Cell A.](7ede87328f6b696dcffa65ebc4570cc8_img.jpg) - -Cell layout for multi-access use case. It shows three overlapping ellipses representing coverage areas: Cell A (Licensed band, large orange ellipse), Cell B (Unlicensed band, small green ellipse), and Cell C (Narrow bandwidth licensed band, medium blue ellipse). UE Id=1 (stationary) is in Cell B. UE Id=2 (high mobility) is in Cell C with a dashed arrow pointing towards Cell A. UE Id=3 (low mobility) is in Cell A. - -Figure 4.1.7-1: Cell layout for multi-access use case - -From a traffic distribution perspective, since UE with UE Id=1 is a stationary UE the FTP and email traffic with (5QI=8) should preferably be routed over secondary unlicensed cell B and should avoid licensed cells, cell A and cell C. The voice traffic should be routed over cell A. - -For UE with UE Id=2, since it is a highly mobile UE, all the traffic should be routed over licensed cells, preferably cell A to avoid disruption in connections. However, if there is a shortage of bandwidth in cell A, the email traffic (5QI=8) can be routed over unlicensed band (cell B). Given that this is a high mobility UE, there can be a policy that a minimum of - -50% and maximum of 70% of all traffic from this UE should be routed over cell A which should be the primary cell and remaining can be routed over secondary cell. - -For UE with UE Id=3, since it is a low mobility UE both the progressive video (5QI=8) and file sharing (5QI=8) should be routed over unlicensed band (cell B). The voice traffic should be routed over cell A. - -The following policies are needed to accomplish this as described in JSON format below. - -- Policy Id 1: For group of UEs with UE Id, 1, 2 and 3. It sets the preference for voice traffic (5QI=1) on cell A for all the UEs. Further, dual connectivity should be enabled for all these UEs whenever possible. -- Policy Id 2: For group of UEs with UE Id, 1 and 3. It sets the preference for all traffic with (5QI=8) on cell B for both the UEs and also avoids cell A and cell C for routing this traffic. -- Policy Id 3: For UE with UE Id=2. It sets the preference for advanced driving traffic with (5QI=83) on cell A and C and also avoids cell B for routing this traffic. -- Policy Id 4: For UE with UE Id=2. It sets the preference for email traffic with (5QI=8) on cell A and C for the high mobility UE. However, it does not avoid use of cell B for routing this traffic in case of bandwidth limitation. -- Policy Id 5: For UE with UE Id=2. It sets the preference that minimum of 50% and a maximum of 70% of all traffic from this UE should be routed through cell A for this UE. - -``` -{ - "group_id": "1", - "ue_id_list": {"1","2","3"} // Define group_1 list of UEs, 1, 2 and 3 - - "policy_id": "1", - "scope": { - "group_id": "1", - "qos_id": "1", - "cell_id": "X" // Policy for Cell X, where X is one of A, B, or C for this group of UEs - }, - "statement": { - "cell_id_list": "A", - "preference": "Prefer", - "dual connectivity": true, // dual connectivity is preferred for UEs in group 1 - "primary": true // Cell A is preferred primary cell for 5QI=1 (Voice), for UEs in group 1 - } -} -``` - -``` -{ - "group_id": "2", - "ue_id_list": {"1","3"} // Define group_1 list of UEs, 1 and 3 - - "policy_id": "2", - "scope": { -``` - -``` - "group_id": "2", - "qos_id": "8", - "cell_id": "X" // Policy for Cell X, where X is one of A, B, or C -}, -"statement": { - "cell_id_list": {"A", "C"}, - "preference": "Avoid", - "primary": false // Avoid 5QI=8 traffic on Cell A and C -}, -"statement": { - "cell_id_list": {"B"}, - "preference": "Prefer", - "primary": false // Prefer 5QI=8 traffic on Cell B for stationary and low mobility UEs -} -} -``` - -``` -{ - "policy_id": "3", - "scope": { - "ue_id": "2", - "slice_id": "2", - "qos_id": "83", - "cell_id": "X" // Policy for Cell X, where X is one of A, B, or C - }, - "statement": { - "cell_id_list": {"B"}, - "preference": "Avoid", - "primary": false // Avoid 5QI=83 traffic on Cell B - }, - "statement": { - "cell_id_list": {"A", "C"}, - "preference": "Prefer", - "primary": true // Prefer 5QI=83 traffic on Cell A or C for high mobility UE - } -} -``` - -``` -{ - "policy_id": "4", -} -``` - -``` -"scope": { - "ue_id": "2", - "slice_id": "2", - "qos_id": "8", - "cell_id": "X" // Policy for Cell X, where X is one of A, B, or C -}, -"statement": { - "cell_id_list": {"A", "C"}, - "preference": "Prefer", - "primary": true // Prefer 5QI=8 traffic on Cell A or C and don't avoid cell B -} -} -``` - -``` -{ - "policy_id": "5", - "scope": { - "ue_id": "2", - "slice_id": "2", - "traffic distribution": "X" // Policy for traffic distribution - }, - "statement": { - "cell_id_list": {"A"}, - "preference": "Prefer", - "minimum": "50%", - "maximum": "70%", // Prefer 50-70% of traffic distribution on cell A for this UE - } -} -``` - -## 4.2 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.2.1 Background and goal of the use case - -The highly demanding 5G native applications such as 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. - -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, and 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.2.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) E2 nodes: - - 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.2.3 Solutions - -#### 4.2.3.1 Model training and distribution - -The context of model training and distribution is captured in table 4.2.3.1-1. - -**Table 4.2.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. | | -| 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. | | -| 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. | | -| 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. | | -| Traceability |
  • - REQ-Non-RT-RIC-FUN1, REQ-Non-RT-RIC-FUN3, REQ-Non-RT-RIC-FUN4, REQ-Non-RT-RIC-FUN5
  • - REQ-A1-FUN1, REQ-A1-FUN2, REQ-A1-FUN4
| | - -``` -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -``` - -``` -skinparam defaultFontSize 12 - -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 as "near-RT RIC" - Participant ran as "E2 Nodes" -End box - -ran --> smo : <> Data collection -app --> smo: Data retrieval of application data -smo --> non : Data retrieval - -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 - smo -> non : Data retrieval of RAN and application - non -> non : Performance monitoring & evaluation - non -> non : Model re-training/update - non -> near: <> Update AI/ML models -end - -@enduml -``` - -Image: O-RAN ALLIANCE logo - -O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00 - -The QoE use case flow diagram – model training and distribution/update is given in figure 4.2.3.1-1. - -![Figure 4.2.3.1-1: QoE use case flow diagram - model training and distribution/update](85b10db535b22e64c7d37f362705ddbf_img.jpg) - -``` - - sequenceDiagram - box yellow Service Management and Orchestration - participant CC as Collection & Control - participant nRT as non-RT RIC - end - box pink O-RAN - participant nrRT as near-RT RIC - participant E2 as E2 Nodes - participant app as app - end - - Note over CC, app: Data collection phase - app-->>CC: <<01>> Data collection - E2-->>CC: Data retrieval of application data - CC->>nRT: Data retrieval - - rect white - Note right of nRT: ML workflow - nRT->>nRT: Training of ML models - nRT->>nRT: Deploy internal ML models - nRT->>nrRT: <<01>> Deploy AI/ML models - end - - rect white - Note right of nRT: Performance evaluation and optimization - CC->>nRT: Data retrieval of RAN and application - nrRT->>nRT: Performance monitoring & evaluation - nRT->>nRT: Model re-training/update - nRT->>nrRT: <<01>> Update AI/ML models - end - -``` - -Figure 4.2.3.1-1: QoE use case flow diagram - model training and distribution/update - -**Figure 4.2.3.1-1: QoE use case flow diagram - model training and distribution/update** - -### 4.2.3.2 Policy generation and performance evaluation - -The context of policy generation and performance evaluation is captured in table 4.2.3.2-1. - ---- - -© 2026 by the O-RAN ALLIANCE e.V. Your use is subject to the copyright statement on the cover page of this specification. 28 - -**Table 4.2.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. | | -| Step 3 (M) | Near-RT RIC receives the policy from the Non-RT RIC over the A1 interface. And the Near-RT RIC inferences 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 receive policy feedback from Near-RT RIC and performance measurement data collected from SMO 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. | | -| 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. | | -| Traceability |
  • - REQ-Non-RT-RIC-FUN1, REQ-Non-RT-RIC-FUN3, REQ-Non-RT-RIC-FUN4, REQ-Non-RT-RIC-FUN5
  • - REQ-A1-FUN1, REQ-A1-FUN2, REQ-A1-FUN4
| | - -``` -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -``` - -``` -Box "Service Management and Orchestration" #gold -``` - -``` -Participant "Collection & Control" as smo -``` - -``` -Participant "non-RT RIC" as non -``` - -``` -End box -``` - -``` -Box "O-RAN" #lightpink -``` - -``` -Participant ran as "E2 Nodes" -``` - -``` -Participant near as "near-RT RIC" -``` - -``` -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 create message -``` - -``` -end -``` - -``` -group E2 control & Policy -``` - -``` -ran -> near: <> Data collection -``` - -``` -near -> near : ML model inference -``` - -``` -near -> near : E2 control or policy generation -``` - -``` -near -> ran: <> QoE optimization enforcement message -``` - -``` -end -``` - -``` -group Performance evaluation and optimization -``` - -``` -near ->non: <> QoE optimization policy feedback message -``` - -``` -smo -> non: Data retrieval -``` - -``` -non -> non: performance monitoring -``` - -``` -non -> non: update A1 policy -``` - -``` -non -> near : <> QoE optimization policy update message -``` - -``` -near -> near: Update E2 control or policy -``` - -``` -ran -> near : <> Data collection -``` - -``` -near -> ran: <> QoE optimization enforcement message -``` - -``` -end -``` - -@enduml - -The QoE use case flow diagram – policy generation and performance evaluation is given in figure 4.2.3.2-1. - -![Sequence diagram showing the QoE use case flow for policy generation and performance evaluation. The diagram is divided into two main sections: 'Service Management and Orchestration' (yellow background) and 'O-RAN' (pink background). The O-RAN section contains 'near-RT RIC' and 'E2 Nodes'. The Service Management and Orchestration section contains 'Collection & Control' and 'non-RT RIC'. The flow starts with data collection and retrieval between SMO and near-RT RIC. The near-RT RIC then generates A1 policies (performance monitoring, QoE optimization policy generation) and sends a create message to the SMO. The SMO then sends a feedback message to the near-RT RIC. The near-RT RIC then generates E2 control & Policy (data collection, ML model inference, E2 control or policy generation) and sends an enforcement message to the E2 Nodes. The E2 Nodes then send a feedback message to the near-RT RIC. The near-RT RIC then performs performance evaluation and optimization (data retrieval, performance monitoring, update A1 policy) and sends an update message to the SMO. The SMO then sends an enforcement message to the near-RT RIC. The near-RT RIC then updates E2 control or policy and sends an enforcement message to the E2 Nodes. The E2 Nodes then send a data collection message to the near-RT RIC.](4f148853ae68fdcf5e43f7604cab457d_img.jpg) - -``` - -sequenceDiagram - participant SMO as Service Management and Orchestration - subgraph O-RAN - participant near-RT RIC - participant E2 Nodes - end - Note right of SMO: A1 policies - Note right of near-RT RIC: E2 control & Policy - Note right of near-RT RIC: Performance evaluation and optimization - - SMO->>near-RT RIC: <> Data collection - near-RT RIC-->>SMO: Data retrieval - Note right of near-RT RIC: performance monitoring - Note right of near-RT RIC: QoE optimization policy generation - near-RT RIC->>SMO: <> QoE optimization policy create message - Note right of SMO: Data retrieval - SMO->>near-RT RIC: <> QoE optimization policy feedback message - Note right of near-RT RIC: <> Data collection - Note right of near-RT RIC: ML model inference - Note right of near-RT RIC: E2 control or policy generation - near-RT RIC->>E2 Nodes: <> QoE optimization enforcement message - Note right of near-RT RIC: performance monitoring - Note right of near-RT RIC: update A1 policy - near-RT RIC->>SMO: <> QoE optimization policy update message - Note right of near-RT RIC: Update E2 control or policy - near-RT RIC->>E2 Nodes: <> QoE optimization enforcement message - Note right of E2 Nodes: <> Data collection - E2 Nodes->>near-RT RIC: <> QoE optimization enforcement message - -``` - -Sequence diagram showing the QoE use case flow for policy generation and performance evaluation. The diagram is divided into two main sections: 'Service Management and Orchestration' (yellow background) and 'O-RAN' (pink background). The O-RAN section contains 'near-RT RIC' and 'E2 Nodes'. The Service Management and Orchestration section contains 'Collection & Control' and 'non-RT RIC'. The flow starts with data collection and retrieval between SMO and near-RT RIC. The near-RT RIC then generates A1 policies (performance monitoring, QoE optimization policy generation) and sends a create message to the SMO. The SMO then sends a feedback message to the near-RT RIC. The near-RT RIC then generates E2 control & Policy (data collection, ML model inference, E2 control or policy generation) and sends an enforcement message to the E2 Nodes. The E2 Nodes then send a feedback message to the near-RT RIC. The near-RT RIC then performs performance evaluation and optimization (data retrieval, performance monitoring, update A1 policy) and sends an update message to the SMO. The SMO then sends an enforcement message to the near-RT RIC. The near-RT RIC then updates E2 control or policy and sends an enforcement message to the E2 Nodes. The E2 Nodes then send a data collection message to the near-RT RIC. - -Figure 4.2.3.2-1: QoE use case flow diagram - policy generation and performance evaluation - -### 4.2.4 Required data - -Multi-dimensional data are expected to be retrieved by Non-RT RIC for AI/ML model training and policies/intents generation. - -- 1) Network level measurement report, including: - - UE level radio channel information, mobility related metrics - - L2 measurement report related to traffic pattern, e.g., throughput, latency, packets per-second, inter frame arrival time - - RAN protocol stack status: e.g., PDCP buffer status - - 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. - -### 4.2.5 A1 usage example - -There are 3 examples to explain how A1 policy works for QoE optimization. - -One is for ue\_id (100), slice\_id (1) and qos\_id (5QI=50), the target QoE score (for example video MOS 80) should be satisfied. - -``` -{ - "policy_id": "1", - "scope": { - "ue_id": "100", - "slice_id": "1", - "qos_id": "50" - }, - "statement": { - "qoe_score": "80" - } -} -``` - -The second example is to regulate specific QoE targets, for example, initial buffering time for video streaming is required within 2 seconds, rebuffering frequency is 2 times and stalling ratio is 5% for a customized time window (e.g., 30 seconds). - -``` -{ - "policy_id": "2", - "scope": { - "ue_id": "101", - "slice_id": "1", - "qos_id": "51" - }, - "statement": { - "initial_buffering": "2", - "reBuffFreq": "2", - "stallRatio": "5" - } -} -``` - -The specific user id need not be required, and only slice\_id and flow\_id are required for specific QoE targets. - -``` -{ - "policy_id": "3", -``` - -``` - "scope": { - "slice_id": "1", - "flow_id": "51" - }, - "statement": { - "initial_buffering": "2", - "reBuffFreq": "2", - "stallRatio": "5" - } -} -``` - -## 4.3 QoS based resource optimization - -This use case provides the background and motivation for the O-RAN architecture to support RAN QoS based resource optimization. Moreover, some high-level description and requirements over Non-RT RIC and A1 interfaces are introduced. - -### 4.3.1 Background and goal of the use case - -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. - -Take an emergency service as an example of a slice tenant. 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 core network 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-prioritize 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: - -1. A fire draws a lot of emergency personnel to an area. -2. Because of this, RAN resources becomes congested which affects the video quality for all video feeds in the area. -3. The emergency control command have 5 active video feeds and selects one video feed which is of specific interest. -4. The emergency control command requests higher resolution of a selected feed, while demoting the other. -5. 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). -6. The Non-RT RIC updates the policy for the associated UEs in the associated Near-RT RIC over the A1 interface. -7. Near-RT RIC enforce the modified QoS target for the associated UEs over the E2 interface to fulfil the request. -8. The emergency control command experiences a higher resolution of the selected video feed. - -### 4.3.2 Entities/resources involved in the use case - -- 1) Non-RT RIC: - - a) Monitor necessary QoS related metrics from network function and other SMO functions. - - b) Send policies to Near-RT RIC to drive QoS based resource optimization at RAN level in terms of expected behavior. -- 2) Near-RT RIC: - - a) Support interpretation and execution of A1 policies for QoS based resource optimization. -- 3) E2 nodes: - - a) Support network state and UE performance report with required granularity to SMO over O1 interface. - - b) Support QoS enforcement based on messages from E2, which are expected to influence RRM behavior. - -### 4.3.3 Solutions - -#### 4.3.3.1 QoS based resource optimization - -The context of QoS based resource optimization is captured in table 4.3.3.1-1. - -**Table 4.3.3.1-1: QoS based resource optimization** - -| Use Case Stage | Evolution / Specification | <> | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Goal | Drive QoS based resource optimization in RAN in accordance with defined policies and configuration. | | -| Actors and Roles | Non-RT RIC: Creates A1 policies.
Near-RT RIC: Enforces A1 policies.
RAN: Policy enforcement.
SMO: Termination point for O1 interface. | | -| Assumptions | All relevant functions and components are instantiated and configured according wanted default behavior.
A1 interface connectivity is established with Non-RT RIC.
O1 interface connectivity is established with SMO.
The default configuration will handle most situations. | | -| Pre-conditions | Network is operational with default configuration.
SMO has established the data collection and sharing process, and Non-RT RIC has access to this data.
Non-RT RIC analyzes the data from RAN to understand the current resource consumption. | | -| Begins when | Non-RT RIC observes that resources are close to congestion in a certain area. | | -| Step 1 (O) | If needed, Non-RT RIC orders additional RAN observability, SMO configures additional observability over O1. | | -| Step 2 | Non-RT RIC evaluates RAN resource utilization for all users in a slice in specific area. | | -| Step 3 | Non-RT RIC asks for additional information from additional SMO functionality, e.g., E2E slice assurance function. | | -| Step 4 | Non-RT RIC determines dynamic group of users for which QoS target shall be changed. | | -| Step 5 | Non-RT issues A1 policy/policies with QoS target based on information from other SMO functionality. | | -| Ends when | Non-RT RIC (through O1 observability) understands that situation of resource constraints within the slice is resolved, and the deployed policies are deleted over A1. | | -| Exceptions | None identified. | | -| Post Conditions | Non-RT RIC monitors the performance by collecting the relevant performance events and counters from E2 nodes via SMO. | | -| Traceability | - REQ-Non-RT-RIC-FUN1, REQ-Non-RT-RIC-FUN2, REQ-Non-RT-RIC-FUN3, REQ-Non-RT-RIC-FUN4, REQ-Non-RT-RIC-FUN5 | | - -| Use Case Stage | Evolution / Specification | <> | -|----------------|---------------------------|-------------| -| | | Related use | -| | - REQ-A1-FUN1 | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -Autonumber - -Box "External enrichment server" #lightblue - Entity sliceuserdata as "Slice user data" -End box - -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 -non-> non: Evaluation of resource consumption -non-> non: Indication of approaching congestion in certain area -group O1 configuration - non -> smo: Request additional measurements - smo -> ran: <> PM measurement configuration - ran -> smo : <> Data collection - smo -> non : Additional data retrieval -end - -non -> non: Detailed evaluation of situation - -``` - -``` -non -> smo: Request additional info on priorities -smo -> sliceuserdata: Request Non-RAN info on priorities -sliceuserdata -> smo: Non-RAN information on priorities -smo-> non: Additional information on priorities - -group A1 Policies - non -> near : <> QoS based resource optimization policy create message - near -> ran : <> QoS based resource optimization enforcement -end - -ran -> smo: <> Data collection (incl specific data) -smo -> non: Data retrieval of RAN and non-RAN data -non -> non: Detailed evaluation of congestion situation to understand the effect of -policy -non -> non: Evaluation of congestion situation to understand when gone -group A1 policies - non -> near: <> QoS target policy delete message -end - -@enduml -``` - -The flow diagram of the QoS based resource optimization use case is given in figure 4.3.3.1-1. - -![Flow diagram of QoS based resource optimization use case. The diagram shows interactions between Service Management and Orchestration (SMO), O-RAN (Near-RT RIC, E2 Nodes), and an External enrichment server. The SMO contains Collection & Control and Non-RT RIC. The O-RAN contains Near-RT RIC and E2 Nodes. The External enrichment server contains Slice user data. The sequence of messages is: 1. Non-RT RIC to Near-RT RIC: <> Data collection; 2. Near-RT RIC to Non-RT RIC: Evaluation of resource consumption; 3. Near-RT RIC to Non-RT RIC: Indication of approaching congestion in certain area; 4. Non-RT RIC to Near-RT RIC: Request additional measurements; 5. Non-RT RIC to Near-RT RIC: <> PM measurement configuration; 6. Non-RT RIC to Near-RT RIC: <> Data collection; 7. Non-RT RIC to Near-RT RIC: Additional data retrieval; 8. Near-RT RIC to Non-RT RIC: Detailed evaluation of situation; 9. Non-RT RIC to Near-RT RIC: Request additional info on priorities; 10. Non-RT RIC to External enrichment server: Request Non-RAN info on priorities; 11. External enrichment server to Non-RT RIC: Non-RAN information on priorities; 12. Non-RT RIC to Near-RT RIC: Additional information on priorities; 13. Non-RT RIC to Near-RT RIC: <> QoS based resource optimization policy create message; 14. Near-RT RIC to E2 Nodes: <> QoS based resource optimization enforcement; 15. Non-RT RIC to Near-RT RIC: <> Data collection (incl specific data); 16. Non-RT RIC to Near-RT RIC: Data retrieval of RAN and non-RAN data; 17. Near-RT RIC to Non-RT RIC: Detailed evaluation of congestion situation to understand the effect of policy; 18. Near-RT RIC to Non-RT RIC: Evaluation of congestion situation to understand when gone; 19. Non-RT RIC to Near-RT RIC: <> QoS target policy delete message.](02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg) - -Flow diagram of QoS based resource optimization use case. The diagram shows interactions between Service Management and Orchestration (SMO), O-RAN (Near-RT RIC, E2 Nodes), and an External enrichment server. The SMO contains Collection & Control and Non-RT RIC. The O-RAN contains Near-RT RIC and E2 Nodes. The External enrichment server contains Slice user data. The sequence of messages is: 1. Non-RT RIC to Near-RT RIC: <> Data collection; 2. Near-RT RIC to Non-RT RIC: Evaluation of resource consumption; 3. Near-RT RIC to Non-RT RIC: Indication of approaching congestion in certain area; 4. Non-RT RIC to Near-RT RIC: Request additional measurements; 5. Non-RT RIC to Near-RT RIC: <> PM measurement configuration; 6. Non-RT RIC to Near-RT RIC: <> Data collection; 7. Non-RT RIC to Near-RT RIC: Additional data retrieval; 8. Near-RT RIC to Non-RT RIC: Detailed evaluation of situation; 9. Non-RT RIC to Near-RT RIC: Request additional info on priorities; 10. Non-RT RIC to External enrichment server: Request Non-RAN info on priorities; 11. External enrichment server to Non-RT RIC: Non-RAN information on priorities; 12. Non-RT RIC to Near-RT RIC: Additional information on priorities; 13. Non-RT RIC to Near-RT RIC: <> QoS based resource optimization policy create message; 14. Near-RT RIC to E2 Nodes: <> QoS based resource optimization enforcement; 15. Non-RT RIC to Near-RT RIC: <> Data collection (incl specific data); 16. Non-RT RIC to Near-RT RIC: Data retrieval of RAN and non-RAN data; 17. Near-RT RIC to Non-RT RIC: Detailed evaluation of congestion situation to understand the effect of policy; 18. Near-RT RIC to Non-RT RIC: Evaluation of congestion situation to understand when gone; 19. Non-RT RIC to Near-RT RIC: <> QoS target policy delete message. - -Figure 4.3.3.1-1: Flow diagram of QoS based resource optimization use case - -### 4.3.4 Required data - -For this use case, different kind of observability need to be reported to Non-RT RIC. First Non-RT RIC shall monitor resource consumption in the area. As long as resource consumption is low, the RAN scheduler will be able to give all users in an area the needed resources. When resource consumption in an area increases above a threshold, there is risk of that the default configuration of RAN will not be enough to fulfil the requirements. At this point, the Non-RT RIC need to be able to configure more detailed reporting for individual UEs that the Non-RT RIC is interested in. This detailed observability should provide the Non RT RIC better insight in performance for specific users and therefore includes observability of e.g., user throughput and delay. With this more detailed observability, the Non-RT RIC can understand when pre-configured priorities are not enough for the scheduler to solve the problem and when additional (non-RAN) information to solve the prioritization is needed. - -### 4.3.5 A1 usage example - -#### Example scenario - -- One emergency RAN sub-slice defined (S-NSSAI=1) with a ratio of 50% configured. 5QI=74 configured for a minimum bitrate of 500 kbps. -- 4 UEs (UeId=10, 11, 12, 13) in the area which belongs to S-NSSAI = 1 and with active flows of 5QI = 74. -- Resource shortage means that minimum bitrate 500 kbps cannot be fulfilled for all users. -- E2E Slice assurance function indicates to Non-RT RIC that UeId=10 and 12 needs to be prioritized. -- Because of resource shortage, increasing minimum bitrate for UeId=10 and 12 will not improve, instead minimum bitrate for other users in slice needs to be lowered. - -``` -{ -{ - "policy_id": "1", - "scope": { - "ue_id": "11", - "slice_id": "1", - "flow_id": "74" - }, - "statement": { - "gfbr": "0" - } -} -{ - "policy_id": "2", - "scope": { - "ue_id": "13", - "slice_id": "1", - "flow_id": "74" - }, - "statement": { - "gfbr": "0" - } -} -``` - -- An alternative way to temporarily change RAN behavior for S-NSSAI=1 users is to change the relative priority in the scheduler. This would change the relative resource assignment to different users with different priority. - -``` -- { -- { -- "policy_id": "1", -- "scope": { -- "ue_id": "10", -- "slice_id": "1", -- "flow_id": "74" -- }, -- "statement": { -``` - -``` -- "priority_level": "10" -- } -- } -- -- -``` - -``` -- { -- "policy_id": "2", -- "scope": { -- "ue_id": "12", -- "slice_id": "1", -- "flow_id": "74" -- }, -- "statement": { -- "priority_level": "10" -- } -- } -``` - -``` -- { -- "policy_id": "3", -- "scope": { -- "ue_id": "11", -- "slice_id": "1", -- "flow_id": "74" -- }, -- "statement": { -- "priority_level": "1" -- } -- } -``` - -``` -- { -- "policy_id": "4", -- "scope": { -- "ue_id": "13", -- "slice_id": "1", -- "flow_id": "74" -- }, -- "statement": { -``` - -``` - -- "priority_level": "1" -- } -- } - -``` - -## 4.4 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.4.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) [i.2], 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 Neighbor 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.4.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) E2 nodes: - - 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.4.3 Solutions - -#### 4.4.3.1 Context-based dynamic handover management for V2X - -The context of the context-based dynamic handover management for V2X is captured in table 4.4.3.1-1. - -**Table 4.4.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. | | -| 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. | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 6 | 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. | | -| Traceability |
  • - REQ-Non-RT-RIC-FUN1, REQ-Non-RT-RIC-FUN2, REQ-Non-RT-RIC-FUN3, REQ-Non-RT-RIC-FUN4, REQ-Non-RT-RIC-FUN7
  • - REQ-A1-FUN1, REQ-A1-FUN2, REQ-A1-FUN3, REQ-A1-FUN5
| | - -``` - -@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 + E2 Node" -End box - -Box "External" #lightcyan - Participant V2X as "V2X Application Server" -End box - -``` - -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 - -group "Data Collection Subscription, for Inference" - -RIC -> RIC : <> Subscription request: UE E2 data collection - -RIC -> NON : <> Subscription request: UE EI data collection - -NON -> V2X : <> Subscription request: UE EI data collection - -V2X -> NON : <> Subscription Ack: UE EI data collection - -NON -> RIC : <> Subscription Ack: UE EI data collection - -end - -group "Measurement Data Collection for Inference" - -RIC -> RIC : <> Subscription Request:{UE E2 measurement report} - -RIC -> NON : <> Subscription Request:{UE EI measurement report} - -NON -> V2X : <> Subscription Request:{UE EI measurement report} - -V2X -> NON : <> Report:{UE EI measurement report} - -NON -> RIC : <> Report:{UE EI measurement report} - -end - -RIC -> RIC : V2X HO Optimization - -RIC -> Collector : <> SMO data collection - -SMO -> SMO: Update NearRT\_model2 - -SMO -> RIC : <> Deploy NearRT\_Model2 - -@enduml - -@enduml - -The flow diagram of the V2X HO management use case is given in figure 4.4.3.1-1. - -![Sequence diagram for V2X HO management use case flow. Lifelines: Orchestration, Collector, Resource Controller, Data Lake, non-RT RIC, ML Training Host(s), near-RT RIC + E2 Node, V2X Application Server. The diagram shows steps for model deployment, data collection subscription, measurement data collection, and V2X HO optimization.](f142b022cfc716cd967297f027efe647_img.jpg) - -``` - -sequenceDiagram - participant Orchestration - participant Collector - participant Resource Controller - participant Data Lake - participant non-RT RIC - participant ML Training Host(s) - participant near-RT RIC + E2 Node - participant V2X Application Server - - Note right of non-RT RIC: Assume trained models are available in SMO - - 1. Orchestration->>Collector: <> SMO data collection - 2. Orchestration->>Resource Controller: <> Deploy NonRT_Model1 - 3. Resource Controller->>non-RT RIC: Execute NonRT_Model1 - 4. non-RT RIC->>near-RT RIC + E2 Node: <> V2X HO Optimization Policy (create/update/delete) - 5. Orchestration->>Resource Controller: <> Deploy NearRT_Model1 - 6. Orchestration->>Resource Controller: <> Deploy NearRT_Model2 - - Note right of near-RT RIC + E2 Node: "Data Collection Subscription, for Inference" - 7. near-RT RIC + E2 Node->>Collector: <> Subscription request: UE E2 data collection - 8. Collector->>non-RT RIC: <> Subscription request: UE EI data collection - 9. non-RT RIC->>V2X Application Server: <> Subscription request: UE EI data collection - 10. V2X Application Server->>non-RT RIC: <> Subscription Ack: UE EI data collection - 11. non-RT RIC->>Collector: <> Subscription Ack: UE EI data collection - - Note right of near-RT RIC + E2 Node: "Measurement Data Collection For Inference" - 12. near-RT RIC + E2 Node->>Collector: <> Subscription Request: (UE E2 measurement report) - 13. Collector->>non-RT RIC: <> Subscription Request: (UE EI measurement report) - 14. non-RT RIC->>V2X Application Server: <> Subscription Request: (UE EI measurement report) - 15. V2X Application Server->>non-RT RIC: <> Report: (UE EI measurement report) - 16. non-RT RIC->>Collector: <> Report: (UE EI measurement report) - - 17. near-RT RIC + E2 Node->>Collector: V2X HO Optimization - 18. Orchestration->>Collector: <> SMO data collection - 19. Orchestration->>Resource Controller: Update NearRT_model2 - 20. Orchestration->>Resource Controller: <> Deploy NearRT_Model2 - -``` - -Sequence diagram for V2X HO management use case flow. Lifelines: Orchestration, Collector, Resource Controller, Data Lake, non-RT RIC, ML Training Host(s), near-RT RIC + E2 Node, V2X Application Server. The diagram shows steps for model deployment, data collection subscription, measurement data collection, and V2X HO optimization. - -Figure 4.4.3.1-1: V2X HO management use case flow diagram - -### 4.4.4 Required data - -The measurement counters and KPIs (as defined by 3GPP) should 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. - -### 4.4.5 Proposed solution(s) - -#### 4.4.5.1 Workflow overview - -The use case workflow consists of these main components: - -1. **Data collection & maintenance:** This is required at Non-RT RIC (over O1 and Enrichment Interface (EI)). Required radio measurements and V2X related metrics are collected over a longer period of time (sufficient to facilitate model training). The O1/EI data collection is used for offline training of models, as well as for generating A1 policies for V2X HO optimization. The E2 (and EI) data collection is used for model execution in the Near-RT RIC. Details of the models are described below. -2. **Long-term HO analytics & model maintenance:** The Non-RT RIC long-term analytics is responsible for providing the relevant models for V2X HO optimization over A1 interface. Based on O-RAN A1 interface specs v1, these policies can be defined at per-UE level, UE group level, cell or xNB level etc. This will provide the optimization scope/objective for the Near-RT RIC V2X HO xApp. The xApp hosts two AI/ML-assisted functions: 1. HO anomaly detection & prediction, 2. HO anomaly avoidance. The 1. trained model's input is [E2: HO sequences, UE radio measurements; EI: position, velocity, direction, (O) navigation data, (O) cell load data of cells in the area] of a given time window, while the output is [anomaly likelihoods for possible future HO sequences]. The 2. trained model's **input** is [E2 report, EI report, output of 1. model, (O) navigation data, (O) cell load data of cells in the area] and its **output** is [UE-customized NRT sequence for cells that the UE is about to touch, with lower anomaly likelihood, (O) with validity time]. The two models are regularly retrained/updated based on new radio/V2X data. -4. **HO anomaly prediction & detection:** The navigation information and HO sequence and predicted HO sequence of V2X UEs in scope are evaluated and HO anomalies are detected or predicted. If any, it is delegated for further consideration for HO sequence optimization. -5. **HO sequence optimization:** Based on the E2 and enrichment reports and the prediction/detection output, the trained AI/ML model outputs UE-customized NRTs for the cells that I. are in scope, II. the UE is about to come in touch with. -6. **V2X HO optimization execution:** The new NRTs are deployed at xNBs through E2 policies. - -#### 4.4.5.2 Overview of ML models - -While many combinations and deployments are possible, this proposal outlines one specific set of models and analytics that can be useful to drive such a use case. - -**NonRT\_Model1:** The Non-RT RIC ML-assisted solution uses the O1-based and EI-based data collection to monitor the V2X UE HO performance metrics and the navigation indicators (position, direction, speed, (O) traffic indicators). Based on the performance monitoring, the model aims to represent navigation and radio environments/conditions and maintain a data base in order to classify HO situations. **Input:** historical radio, HO, and location, direction, velocity data. **Output:** maintained database with locations, directions, velocities and cells, HO situations, HO anomalies, and/or sequences of all these, together with prevalence rates (=estimated probabilities). - -**NearRT\_Model1:** The first ML-assisted near-RT xApp model in the Near-RT RIC aims to rate/score future/current HO situations (on a UE level) based on real-time radio (E2) and navigation conditions (EI), i.e., predict/detect anomalous HO situations. **Input:** per-UE current radio parameters, HO history, location, direction, velocity. **Output:** predicted HO sequence(s) with probabilities for anomalies at specific cell pairs. - -**NearRT\_Model2:** The second ML-assisted near-RT xApp model in the Near-RT RIC aims to choose alternative, UE specific NRTs for a set of cells and UEs so as to resolve or avoid anomalous HO situations. **Input:** input and output of the NearRT\_Model1. **Output:** alternative, UE specific NRTs for some cells (e.g., with temporal validity/expiration time). - -### 4.4.6 A1 enrichment interface aspects - -1. As per ETSI EN 302 637-2 [i.2], V2X UE provides CAMs (which include its GPS coordinates) on a 0.1-1s temporal granularity to the V2X application server. The inference part of this use case depends on accurate navigation data from V2X UEs, thus we expect this data to be provided through the A1-EI without substantial processing or delay. -2. The data (in particular the GPS coordinates) received over A1-EI need to be correlated with RAN UE data. For this problem there might be different requirements for the training data collection and the inference data collection. E.g., the - -UE data association might be solved using the ECGI + C-RNTI identifiers at any point in time (inference), but when collecting historical data for training it is essential to save the data in such a way that later correlation is possible as well. - -### 4.4.7 A1 usage example - -As of now the A1 aspect of the use case is confined to whether the HO optimization is, within a certain scope, activated or not. Thus, some of the attributes can overlap with the policy scope, but they are proposed in order to allow for more fine-grained control (e.g., optimize for only vehicles that are faster than 100 km/h [vel\_range], between 7am and 9am on workdays [time\_range], within a given geographical area [pos\_range] or [cell\_id\_list].) - -The proposed (optional) attributes of the statement type **v2x\_nrt\_opt** are captured in table 4.4.7-1. - -**Table 4.4.7-1: Definition of statement type v2x\_nrt\_opt/extra scope identifiers** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-----------|-----|-------------|---------------------------------------------|---------------| -| cell_id_list | Array | "M" | "1..N" | list of CellIDs | | -| time_range | Array | "O" | "1..N" | refers to the time intervals of activation | | -| pos_range | Array | "O" | "1..N" | refers to GPS position ranges of activation | | -| vel_range | Array | "O" | "1..N" | refers to velocity ranges of activation | | -| | | | | | | - -``` -{ - "title": "policies", - "description": "O-RAN A1 policy", - "type": "object", - "properties": { - "policy_id": {"type": "string"}, - "scope": { - ... - }, - "statement": { - "cell_id_list": {"type": "number"}, - "time_range": {"type": "number"}, - "pos_range": {"type": "number"}, - "vel_range": {"type": "number"} - } - } -} -``` - -## 4.5 RAN slice SLA assurance - -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 as specified in 3GPP TS 23.501 [2]. 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 as specified in 3GPP TS 28.530 [3], especially in RAN side. Exemplary slice performance requirements are specified in terms of throughput, energy efficiency, latency and reliability at a high level in SDOs such as 3GPP TS 22.261 [1] and GSMA [9]. 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 as specified in 3GPP TS 28.552 [5] and information model definitions as specified in 3GPP TS 28.541 [4] 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.5.1 Background and goal of the use case - -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.5.2 Entities/resources involved in the use case - -- 1) Non-RT RIC: - - a) Retrieve RAN slice SLA target from respective entities such as SMO, NSSMF. - - b) Long term monitoring of RAN slice performance measurements. - - c) Training of potential ML models that will be deployed in Non-RT RIC for slow loop optimization and/or Near-RT RIC for fast loop optimization. - - d) Support deployment and update of AI/ML models into Near-RT RIC. - - e) Receive slice control/slice SLA assurance rApps from SMO. - - f) Create and update A1 policies based on RAN intent and A1 feedback. - - g) Send A1 policies and enrichment information to Near-RT RIC to drive slice assurance. - - h) Send O1 reconfiguration requests to SMO for slow-loop slice assurance. -- 2) Near-RT RIC: - - a) Near-real-time monitoring of slice specific RAN performance measurements. - -- b) Support deployment and execution of the AI/ML models from Non-RT RIC. - - c) Receive slice SLA assurance xApps from SMO. - - d) Support interpretation and execution of policies from Non-RT RIC. - - e) Perform optimized RAN (E2) actions to achieve RAN slice requirements based on O1 configuration, A1 policy, and E2 reports. -- 3) E2 nodes: -- a) Support slice assurance actions such as slice-aware resource allocation, prioritization, etc. - - b) Support slice specific performance measurements through O1. - - c) Support slice specific performance reports through E2. - -### 4.5.3 Solutions - -#### 4.5.3.1 Creation and deployment of RAN slice SLA assurance applications - -The context of the creation and deployment of RAN slice SLA assurance applications is captured in table 4.5.3.1-1. - -**Table 4.5.3.1-1: Creation and deployment of RAN slice SLA assurance applications** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Training and distribution of the RAN slice SLA assurance applications. | | -| Actors and Roles | Non-RT RIC, Near-RT RIC, SMO | | -| Assumptions | All relevant functions and components are instantiated.
A1, O1 interface connectivity is established. | | -| Pre-conditions | Near-RT RIC and Non-RT RIC are instantiated with A1 interface. A1 connectivity being established between them.
O1 interface is established between SMO and Near-RT RIC. | | -| Begins when | A RAN slice is activated, or an operator defined trigger is detected. | | -| Step 1 (M) | Non-RT RIC retrieves a RAN slice SLA from SMO (e.g., from NSSMF). | | -| Step 2a (O) | Non-RT RIC starts to collect slice specific performance measurements (PMs) via O1. Examples of the PMs are CSI, PRB usage, L2 throughput, RAN latency, etc. Applicable PMs are specified in 3GPP TS 28.552 [5]. | | -| Step 2b (O) | Non-RT RIC starts to collect Enrichment Information (EIs) from external applications. Examples of the external applications are public safety application triggering slice priority during an emergency event, or location-based enrichment information, etc. | | -| Step 3 (O) | Non-RT RIC does the model training during a certain period of time using the collected data in step 2 and generates RAN slice SLA assurance AI/ML models. | | -| Step 4 (M) | Non-RT RIC deploys RAN slice SLA assurance rApp (which can include the newly trained AI/ML model(s)). | | -| Step 5 (O) | Non-RT RIC deploys RAN slice SLA assurance xApp(s) to respective Near-RT RICs (which can include the newly trained AI/ML model(s)). | | -| Step 6 (O) | Non-RT RIC continues collecting slice specific performance measurements (PMs) via O1 and receives/utilizes A1 feedback if available. Non-RT RIC can update the AI/ML models within rApp and xApp(s). | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Ends when | A RAN slice is deactivated. | | -| Exceptions | None identified. | | -| Post Conditions | RAN slice SLA assurance applications are deployed. | | -| Traceability | REQ-Non-RT-RIC-FUN1, REQ-Non-RT-RIC-FUN2, REQ-Non-RT-RIC-FUN3, REQ-Non-RT-RIC-FUN4, REQ-Non-RT-RIC-FUN5, REQ-Non-RT-RIC-FUN9, REQ-A1-FUN2, REQ-A1-FUN4 | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "Service Management and Orchestration" #gold - Participant SMO as "SMO Functions" - Boundary Collector - Participant NON as "Non-RT RIC" -end box - -Box "O-RAN" #lightpink - Participant RIC as "Near-RT RIC" - Participant E2NODES as "E2 Nodes" -End box - -Box "External" #lightcyan - Participant APP as "App" -End box - -SMO-> NON : RAN Slice SLA Retrieval -E2NODES-> Collector : <> Data Collection -RIC-> Collector : <> Data Collection - -group opt - -``` - -``` -APP-> Collector : Enrichment information collection - -end - -Collector-> NON : Retrieval of RAN and non-RAN data - -group opt - NON-> NON : Training of AI/ML models -end - -NON-> NON : Deploy rApp -group opt - NON-> RIC : <> Deploy xApp -end - -group opt - Collector-> NON : Retrieval of RAN and non-RAN data - NON-> NON : Performance monitoring & evaluation - NON-> NON : Model re-training - NON-> NON : Update rApp -end - -group opt - NON-> RIC : <> Update xApp -end - -@enduml -``` - -The flow diagram of the creation and deployment of RAN slice SLA assurance applications is given in figure 4.5.3.1-1. - -![Sequence diagram showing the creation and deployment of RAN slice SLA assurance applications. Lifelines include SMO Functions, Collector, Non-RT RIC, Near-RT RIC, E2 Nodes, and App. The process involves SLA retrieval, data collection, enrichment, model training, and application deployment with optional loops for updates and re-training.](40ebe9179df298f1b6d76822f28d90aa_img.jpg) - -``` - -sequenceDiagram - participant SMO as SMO Functions - participant C as Collector - participant NRT as Non-RT RIC - participant NRT2 as Near-RT RIC - participant E2 as E2 Nodes - participant App as App - - Note left of SMO: Service Management and Orchestration - Note right of NRT2: O-RAN - Note right of App: External - - SMO->>NRT: 1 RAN Slice SLA Retrieval - NRT->>C: 2 <> Data Collection - NRT->>C: 3 <> Data Collection - opt Enrichment information collection - C->>NRT: 4 Enrichment information collection - end - NRT->>C: 5 Retrieval of RAN and non-RAN data - opt Training of AI/ML models - NRT->>NRT: 6 Training of AI/ML models - end - NRT->>C: 7 Deploy rApp - opt <> Deploy xApp - NRT->>NRT2: 8 <> Deploy xApp - end - opt Retrieval of RAN and non-RAN data - NRT->>C: 9 Retrieval of RAN and non-RAN data - C->>NRT: 10 Performance monitoring & evaluation - NRT->>C: 11 Model re-training - NRT->>C: 12 Update rApp - end - opt <> Update xApp - NRT->>NRT2: 13 <> Update xApp - end - -``` - -Sequence diagram showing the creation and deployment of RAN slice SLA assurance applications. Lifelines include SMO Functions, Collector, Non-RT RIC, Near-RT RIC, E2 Nodes, and App. The process involves SLA retrieval, data collection, enrichment, model training, and application deployment with optional loops for updates and re-training. - -Figure 4.5.3.1-1: Creation and deployment of RAN slice SLA assurance applications - -#### 4.5.3.2 RAN slice SLA assurance - -The context of RAN slice SLA assurance is captured in table 4.5.3.2-1. - -Table 4.5.3.2-1: RAN slice SLA assurance - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | RAN slice SLA assurance | | -| Actors and Roles | SMO functions, Non-RT RIC framework, RAN slice SLA assurance rApp, Near-RT RIC, E2 nodes | | -| Assumptions | All relevant functions and components are instantiated.
A1, O1, E2 interface connectivity is established. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Pre-conditions |

Near-RT RIC and Non-RT RIC are instantiated with A1 interface connectivity being established between them.

O1 interfaces are established between SMO and Near-RT RIC, and SMO and E2 nodes.

RAN slice SLA assurance applications have been deployed in Non-RT RIC and Near-RT RIC respectively.

| | -| Begins when | A RAN slice is activated, or an operator defined trigger is detected. | | -| Step 1 (M) | RAN slice SLA assurance rApp retrieves relevant information from Non-RT RIC framework via R1, such as active RAN slices (such as active S-NSSAIs, network slice subnet instances, topology), RAN slice SLA information, NF configuration, etc. | | -| Step 2 (O) | RAN slice SLA assurance rApp retrieves relevant enrichment information from Non-RT RIC framework via R1. | | -| Step 3a (M) |

RAN slice SLA assurance rApp requests relevant slicing specific PMs.

Examples of the PMs are layer 2 throughput, PRB usage, CSI, RAN latency.

| | -| Step 3b (M) | Non-RT RIC framework triggers retrieval of requested O1 PMs by interacting with SMO. | | -| Step 3c (M) | RAN slice SLA assurance rApp starts retrieving E2 node generated slice specific PMs from Non-RT RIC framework via R1. | | -| Step 4 (M) | RAN slice SLA assurance rApp monitors and evaluates performance of RAN slices which can include detection of possible RAN slice SLA violation. | | -| Step 5 (O) | RAN slice SLA assurance rApp decides to apply O1 reconfiguration on certain E2 nodes and/or Near-RT RIC. RAN slice SLA assurance rApp triggers O1 reconfiguration through Non-RT RIC framework using R1. | | -| Step 6a (O) |

RAN slice SLA assurance rApp decides to apply A1 policy based RAN slice SLA assurance considering RAN slice SLA requirements and/or operator-defined RAN intents, EI from external application servers and O1 based long term trends. In addition to these input parameters, A1 feedback from Near-RT RIC, when available, can be utilized for updating existing policies.

The policies include scope identifiers (e.g., S-NSSAI, flow ID, and cell ID) and/or policy statements (e.g., slice specific KPI targets).

| | -| Step 6b (O) | RAN slice SLA assurance rApp triggers creation/update/removal of A1 policies on respective Near-RT RICs through Non-RT RIC framework via R1. | | -| Step 6c (O) | Non-RT RIC framework applies A1 policy creation/update/removal on respective Near-RT RICs through A1 interface. | | -| Step 6d (O) | Near-RT RIC applies A1 policy-based RAN slice SLA assurance. | | -| Step 6e (O) | RAN slice SLA assurance rApp retrieves A1 feedback generated from respective Near-RT RICs. Steps include Near-RT RIC sending the A1 | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|---------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | feedback via A1 to Non-RT RIC framework, and then rApp retrieving this feedback via R1 from Non-RT RIC framework. | | -| Ends when | RAN slice(s) is deactivated or an operator defined trigger is detected. | | -| Exceptions | None identified. | | -| Post Conditions | SLA assurance for RAN slice(s) over a period of time is achieved. | | -| Traceability | REQ-Non-RT-RIC-FUN1, REQ-Non-RT-RIC-FUN5, REQ-Non-RT-RIC-FUN8, REQ-Non-RT-RIC-FUN9, REQ-A1-FUN1, REQ-A1-FUN3, REQ-A1-FUN5 | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "Service Management and Orchestration" #gold - Participant SMO as "SMO Functions" - Participant NON as "Non-RT RIC Framework" - Participant RAPP as "SLA Assurance rApp" -end box - -Box "O-RAN" #lightpink - Participant RIC as "Near-RT RIC" - Participant E2NODES as "E2 Nodes" -End box - -Box "External" #lightcyan - Participant APP as "App" -End box - -SMO-> NON : RAN Slice SLA assurance related data\n (e.g. RAN Slice SLA, NF configuration, topology) -RAPP-> NON : <> Request for RAN Slice SLA assurance related data -NON-> RAPP : <> RAN Slice SLA assurance related data - -``` - -``` -group Opt: Enrichment information collection - RAPP-> NON : <> Request RAN Slice SLA assurance related EI - APP-> SMO : EI collection - SMO-> NON : RAN Slice SLA assurance related EI data - NON-> RAPP : <> RAN Slice SLA assurance related EI data retrieval -end - -RAPP-> NON : <> Request slice specific PMs - -group Opt: Slice specific PM configuration - NON-> SMO : Request new PM - SMO-> RIC : <> PM configuration - SMO-> E2NODES : <> PM configuration -end - -E2NODES-> SMO : <> Slice specific PMs -RIC-> SMO : <> Slice specific PMs -SMO-> NON : Slice specific PMs -NON-> RAPP : <> Slice specific PM retrieval - -RAPP-> RAPP : Performance monitoring and evaluation -RAPP-> RAPP : Trigger for RAN slice SLA assurance \n(e.g. SLA violation detection) - -group Opt: O1 Configuration update - RAPP-> RAPP : Creation of slice specific O1 configuration - RAPP-> NON : <> Request for O1 configuration update - NON-> SMO : Request for O1 configuration update - SMO-> RIC : <> Configuration update - SMO-> E2NODES : <> Configuration update -end - -group Opt: A1 Policy creation / update / removal - RAPP-> RAPP : Creation / update / removal of RAN slice SLA assurance policy - RAPP-> NON : <> Request for A1 policy creation / update / removal - NON-> RIC : <> RAN slice SLA assurance policy creation / update / removal -``` - -``` -group Opt: A1 Enrichment information transfer - NON-> RIC : <> RAN slice SLA assurance related EI -end - -group Near-RT RIC RAN slice SLA assurance - RIC<-> E2NODES : <> RAN slice SLA assurance -end - -group Opt: A1 policy feedback - RIC-> NON : <> RAN slice SLA assurance policy feedback - NON-> RAPP : <> RAN slice SLA assurance policy feedback -end - -end - -@enduml -``` - -The flow diagram of the RAN slice SLA assurance is given in figure 4.5.3.2-1. - -![Sequence diagram for RAN slice SLA assurance showing interactions between SMO Functions, Non-RT RIC Framework, SLA Assurance App, Near-RT RIC, E2 Nodes, and External App. The diagram is divided into several optional sections: Enrichment information collection, Slice specific PM configuration, OI Configuration update, and A1 Policy creation/update/removal. It details the flow of data and requests for SLA assurance related to RAN slices.](255efa1d461fc79b4ed367aaec11637f_img.jpg) - -The sequence diagram illustrates the RAN slice SLA assurance process. The participants are SMO Functions, Non-RT RIC Framework, SLA Assurance App, Near-RT RIC, E2 Nodes, and External App. The process starts with the SLA Assurance App sending RAN Slice SLA assurance related data to the Non-RT RIC Framework. The framework then requests this data from the SMO Functions. The SMO Functions return the data, which is then passed to the App. The App then initiates several optional processes: - - -- Opt: Enrichment information collection:** The App requests RAN Slice SLA assurance related EI from the framework, which in turn requests it from the SMO Functions. The SMO Functions return the EI data, which is then retrieved by the framework and passed to the App. -- Opt: Slice specific PM configuration:** The App requests new PM configuration from the framework, which sends it to the SMO Functions. The SMO Functions return the PM configuration, which is then passed to the framework and then to the App. -- Opt: OI Configuration update:** The App requests an OI configuration update from the framework, which sends it to the SMO Functions. The SMO Functions return the configuration update, which is then passed to the framework and then to the App. -- Opt: A1 Policy creation / update / removal:** The App requests policy creation/update/removal from the framework, which sends it to the SMO Functions. The SMO Functions return the policy, which is then passed to the framework. The framework then sends it to the Near-RT RIC, which in turn sends it to the E2 Nodes. The E2 Nodes return the RAN slice SLA assurance, which is then passed back to the framework and then to the App. - - The diagram also shows optional feedback loops from the Near-RT RIC and E2 Nodes back to the framework and App. - -Sequence diagram for RAN slice SLA assurance showing interactions between SMO Functions, Non-RT RIC Framework, SLA Assurance App, Near-RT RIC, E2 Nodes, and External App. The diagram is divided into several optional sections: Enrichment information collection, Slice specific PM configuration, OI Configuration update, and A1 Policy creation/update/removal. It details the flow of data and requests for SLA assurance related to RAN slices. - -Figure 4.5.3.2-1: RAN slice SLA assurance - -### 4.5.4 Required data - -The measurement counters and KPIs (as defined by 3GPP and will be extended for O-RAN use cases) should be appropriately aggregated by cell, QoS type, slice, etc. Examples for required data for RAN slice SLA assurance use case are as follows: - -- 1) Per UE and/or per slice performance statistics as specified in 3GPP TS 28.552 [5], 3GPP TS 36.314 [6], 3GPP TS 38.314 [7], 3GPP TS 28.558 [23] such as: - - a) CQI related measurements; such as wideband CQI distribution (as specified in 3GPP TS 28.552 [5], clause 5.1.1.11.1) - - b) UE throughput related measurements; such as average DL / UL UE throughput in gNB (as specified in 3GPP TS 28.552 [5], clauses 5.1.1.3.1, 5.1.1.3.3), scheduled IP throughput in DL/UL (as specified in 3GPP TS 36.314 [6], clauses 4.1.6.1, 4.1.6.2) - - c) RRC connection related measurements; such as mean / max number of RRC connections (as specified in 3GPP TS 28.552 [5], clauses 5.1.1.4.1, 5.1.1.4.2), attempted / successful RRC connection establishments (as specified in 3GPP TS 28.552 [5], clauses 5.1.1.15.1, 5.1.1.15.2) - -- d) DRB related measurements; such as number of DRBs attempted to / successfully setup (as specified in 3GPP TS 28.552 [5], clauses 5.1.1.10.1, 5.1.1.10.2) - - e) PDU session management related measurements; such as number of PDU sessions requested to / successfully / failed to setup (as specified in 3GPP TS 28.552 [5], clauses 5.1.1.5.1, 5.1.1.5.2, 5.1.1.5.3) - - f) Number of active UEs; such as mean number of active UEs in the UL / DL per cell (as specified in 3GPP TS 28.552 [5], clauses 5.1.1.23.1, 5.1.1.23.3) - - g) Radio resource utilization related measurements; such as mean DL / UL PRB used for data traffic (as specified in 3GPP TS 28.552 [5], clauses 5.1.1.2.5, 5.1.1.2.7) - - h) PDCP data volume measurements; such as DL / UL PDCP PDU data volume (as specified in 3GPP TS 28.552 [5], clauses 5.1.3.6.1.1, 5.1.3.6.1.2), data volume in DL/UL (as specified in 3GPP TS 36.314 [6], clauses 4.1.8.1, 4.1.8.2) - - i) Average user plane delay; such as UL PDCP packet average delay (as specified in 3GPP TS 28.558 [23], clause 6.3.1.1.5), average delay DL air-interface (as specified in 3GPP TS 28.552 [5], clause 5.1.1.1.1), average delay UL on over-the-air interface (as specified in 3GPP TS 28.552 [5], clause 5.1.1.1.3), average delay DL in gNB-DU (as specified in 3GPP TS 28.552 [5], clause 5.1.3.3.3), average delay DL on F1-U (as specified in 3GPP TS 28.552 [5], clause 5.1.3.3.2), average delay DL in CU-UP (as specified in 3GPP TS 28.552 [5], clause 5.1.3.3.1), average over-the-air interface packet delay in the UL per DRB per UE (as specified in 3GPP TS 38.314 [7], clause 4.2.1.2.2), average delay DL air-interface (as specified in 3GPP TS 28.558 [23], clause 6.3.1.1.1) - - j) Packet drop and loss rate measurements; such as DL RLC SDU packet drop rate in gNB-DU (as specified in 3GPP TS 28.552 [5], clause 5.1.3.2.2), UL / DL F1-U packet loss rate (as specified in 3GPP TS 28.552 [5], clauses 5.1.3.1.2, 5.1.3.1.3), packet Uu loss rate in the DL per DRB per UE (as specified in 3GPP TS 38.314 [7], clause 4.2.1.5.1) -- 2) O1 configuration information for NR NRM such as NRCellCU (as specified in 3GPP TS 28.541 [4], clause 4.3.4), NRCellDU (as specified in 3GPP TS 28.541 [4], clause 4.3.5), GNBDUFunction (as specified in 3GPP TS 28.541 [4], clause 4.3.1), GNBCUCPFunction (as specified in 3GPP TS 28.541 [4], clause 4.3.2), GNBCUUPFunction (as specified in 3GPP TS 28.541 [4], clause 4.3.3), RRMPolicy\_ (as specified in 3GPP TS 28.541 [4], clause 4.3.43) - - 3) Slice SLA information; such as ServiceProfile (as specified in 3GPP TS 28.541 [4], clause 6.3.3), SliceProfile (as specified in 3GPP TS 28.541 [4], clause 6.3.4) - - 4) Enrichment information; such as UE geo-location information (as specified in A1TD [24], clause 8.3.3.2) - -### 4.5.5 A1 usage example - -#### Example scenario 1 - -- One mobile leased line network slice for live broadcasting is defined (S-NSSAI=1). -- The SLA for the slice is defined with the total UL/DL throughput of 30 Mbps of the users in the slice provided in the coverage area (cellId=1, 2, 3). -- Non-RT RIC generates A1 policy for Near-RT RIC slice SLA assurance, which includes S-NSSAI and cellId as scope identifiers, and per-slice total PDCP layer throughput target as a policy statement. -- Near-RT RIC enforces the policy and guides RAN behavior via E2 to meet the slice SLA. - -``` -{ - "PolicyId": "1", -``` - -``` - -"scope": { - "sliceId": "1", - "cellId": "1", "2", "3", // Multiple cellIds need to be supported -}, -"statement": { - "uLThptPerSlice": "30" - "dLThptPerSlice": "30" -} -} -} - -``` - -#### Example scenario 2 - -#### Background of the scenario - -- SLA violation occurs when a cell is congested, and not enough resources are allocated to slice users. To minimize this kind of SLA violation, load balancing is effective. -- Although load balancing can be performed using traffic steering preference policy type, that approach is insufficient to reduce the load to desired level, because there will be a gap between the actual load and the load recognized by Non-RT RIC due to long monitoring and control interval of Non-RT RIC. As shown in figure 4.5.5-1, the near-real-time control loop can achieve smaller reaction time than the non-real-time control loop. Therefore, it is preferable to use Near-RT RIC for load balancing. -- In this scenario, by using A1 policy for load balancing, the load balancing is performed in a shorter cycle, which is more effective in assuring slice SLAs. - -![Diagram illustrating control loops between Non-RT RIC, Near-RT RIC, and E2 nodes. Non-RT RIC sends a 'Policy' via a 'Non-real-time control loop' to Near-RT RIC. Near-RT RIC sends a 'Control' via a 'Near-real-time control loop' to E2 nodes. Both RICs receive 'Monitoring' data from E2 nodes.](4842f073775fb1e84d101c02fd74e59e_img.jpg) - -``` - -graph TD - NonRT[Non-RT RIC] -- "Non-real-time control loop (Policy)" --> NearRT[Near-RT RIC] - NearRT -- "Near-real-time control loop (Control)" --> E2[E2 nodes] - E2 -- "Monitoring" --> NonRT - E2 -- "Monitoring" --> NearRT - -``` - -Diagram illustrating control loops between Non-RT RIC, Near-RT RIC, and E2 nodes. Non-RT RIC sends a 'Policy' via a 'Non-real-time control loop' to Near-RT RIC. Near-RT RIC sends a 'Control' via a 'Near-real-time control loop' to E2 nodes. Both RICs receive 'Monitoring' data from E2 nodes. - -Figure 4.5.5-1: Illustration of the control loops involving Non-RT RIC, Near-RT RIC and E2 nodes - -##### Overall flow in the scenario - -- In this scenario, Non-RT RIC monitors the load and performance under the cell and decides whether the cell load should be balanced or not. Only when cell congestion is detected or predicted, A1 policy for load balancing is sent to Near-RT RIC, and Near-RT RIC performs cell load balancing to ease the cell congestion and solve SLA violation. - -- The following example describes the overall steps in load balancing to assure slice SLAs defined by delay requirement. Note that the step number corresponds to the number given in figure 4.5.5-2. -- (1) An A1 policy (PolicyId: 1) corresponding to SLA of slice #1, which includes delay requirement per UE for users of cell A~E, and slice #1, is sent from Non-RT RIC to Near-RT RIC. - - (2) To monitor the cell load and performance of delay, Non-RT RIC collects mean DL PRB used for data traffic (as specified in 3GPP TS 28.552 [5], clause 5.1.1.2.5) from cell A~E, and distribution of delay DL air-interface (per S-NSSAI) (as specified in 3GPP TS 28.552 [5], clause 5.1.1.1.2) from cell A~E via O1. - - (3) In Non-RT RIC, when the load of cell A is high, and the percentage of packets of slice #1 experiencing a longer delay than required, Non-RT RIC determines that the SLA violation is due to high load and decides to start load balancing. Non-RT RIC sends an A1 policy (PolicyId: 2) to transfer the load of cell A to neighboring non-congested cells (cell B, D and E) until the load of cell A becomes smaller than 80%. - - (4) To monitor the load and radio quality, Near-RT RIC collects mean DL PRB used for data traffic (as specified in 3GPP TS 28.552 [5], clause 5.1.1.2.5) from cell A~E, and per-UE RSRP measurement and RSRQ measurement (as specified in E2SM-KPM [16], clauses 8.2.1.2.2, 8.2.1.2.3 and in 3GPP TS 28.552 [5], clauses 5.1.1.22, 5.1.1.31) via E2. - - (5) Near-RT RIC decides the combination of UEs to be handed over and target cells based on the information collected in (4). Near-RT RIC sends E2 CONTROL for UE-level hand over control to decrease the load of cell A below 80%. - - (6) Non-RT RIC continues to monitor the cell load and performance. When Non-RT RIC decides that the cell load becomes low enough to not cause SLA violation, it notifies deletion of the policy (PolicyId: 2) to Near-RT RIC. - -![Diagram illustrating the overall flow in the load balancing scenario. It shows interactions between RAN intent, Enrichment information, SMO, non-RT RIC, near-RT RIC, and E2 nodes. The flow includes: (1) A1 policy (PolicyId: 1) from non-RT RIC to near-RT RIC; (2) O1 Measurement from non-RT RIC to SMO; (3) A1 policy (PolicyId: 2) from non-RT RIC to near-RT RIC; (4) E2 REPORT from E2 nodes to near-RT RIC; (5) E2 CONTROL from near-RT RIC to E2 nodes; (6) Delete policy (PolicyId: 2) from non-RT RIC to near-RT RIC.](b34c69e1ec326b01c3a485b27b1df5f6_img.jpg) - -The diagram illustrates the interaction flow for load balancing. At the top, 'RAN intent' and 'Enrichment information' are inputs. The 'SMO' contains the 'non-RT RIC'. The 'non-RT RIC' interacts with the 'near-RT RIC' via 'A1' messages. The 'near-RT RIC' interacts with 'E2 nodes' via 'E2' messages. The 'O1' interface connects the 'non-RT RIC' to the 'SMO'. The 'E2 nodes' send 'E2 REPORT' data to the 'near-RT RIC'. The 'near-RT RIC' sends 'E2 CONTROL' messages to the 'E2 nodes'. The 'non-RT RIC' sends 'A1 policy (PolicyId: 1)' and 'A1 policy (PolicyId: 2)' to the 'near-RT RIC'. The 'non-RT RIC' also sends 'O1 Measurement' data to the 'SMO'. The 'non-RT RIC' sends a 'Delete policy (PolicyId: 2)' message to the 'near-RT RIC'. - -**(1) A1 policy (PolicyId: 1)** - Scope: Cell A, B, C, D, E, and Slice#1 - Policy Statement: sliceSlaObjectives - Attribute: maxDIPacketDelayPerUe - -**(2) O1 Measurement** - • Mean DL PRB used for data traffic [TS 28.552] (from Cell A, B, C, D, E) - • Distribution of delay DL air-interface (per S-NSSAI) [TS 28.552] (from Cell A, B, C, D, E) - -**(3) A1 policy (PolicyId: 2)** - Scope: Cell A - lbObjectives: - - targetPrbUsg: 80 - - prbUsgType: 1 - lbResources: - - cellIdList: Cell B, D, E - -**(4) E2 REPORT** - • RSRP, RSRQ measurements (Per-UE) - • Mean DL PRB used for data traffic [TS 28.552] (from Cell A, B, C, D, E) - -**(5) E2 CONTROL** - • CONTROL RIC Style Type=3 (Connected mode mobility control) - > Control Action ID=1 (Handover Control) [E2SM KPM] - -**(6) Delete policy (PolicyId: 2)** - -Diagram illustrating the overall flow in the load balancing scenario. It shows interactions between RAN intent, Enrichment information, SMO, non-RT RIC, near-RT RIC, and E2 nodes. The flow includes: (1) A1 policy (PolicyId: 1) from non-RT RIC to near-RT RIC; (2) O1 Measurement from non-RT RIC to SMO; (3) A1 policy (PolicyId: 2) from non-RT RIC to near-RT RIC; (4) E2 REPORT from E2 nodes to near-RT RIC; (5) E2 CONTROL from near-RT RIC to E2 nodes; (6) Delete policy (PolicyId: 2) from non-RT RIC to near-RT RIC. - -Figure 4.5.5-2: Illustration of the overall flow in the load balancing scenario - -``` -{ - "PolicyId": "2", - "scope": { - "cellId": "A" // Designate a cell of which load is to be transferred to other cells - }, -} -``` - -``` - - "lbObjectives": { - "targetPrbUsg": 80 // Target load of Cell A - "prbUsgType": 1 // PRB usage type used in the calculation of targetPrbUsg - }, - "lbResources": { - "cellIdList": "B", "D", "E", // Designate cells to which cell load is transferred - } -} - -``` - -The illustration of the cell congestion in multi-cell environment is given in figure 4.5.5-3. - -![Diagram illustrating cell congestion in a multi-cell environment. It shows two overlapping coverage areas. The left area contains Cell A, Cell C, Cell D, and Cell E. The right area contains Cell B. Users are represented by small rectangles, some red (slice #1) and some blue (other users). Cell A and Cell D are highlighted with blue backgrounds, while Cell E is highlighted with a green background. A legend indicates that red rectangles are 'Users of slice #1', blue rectangles are 'Other users', and the background color of a cell indicates the connected cell.](50ef8602c7c9edd2da0e2133e772c2a2_img.jpg) - -Diagram illustrating cell congestion in a multi-cell environment. It shows two overlapping coverage areas. The left area contains Cell A, Cell C, Cell D, and Cell E. The right area contains Cell B. Users are represented by small rectangles, some red (slice #1) and some blue (other users). Cell A and Cell D are highlighted with blue backgrounds, while Cell E is highlighted with a green background. A legend indicates that red rectangles are 'Users of slice #1', blue rectangles are 'Other users', and the background color of a cell indicates the connected cell. - -**Figure 4.5.5-3: Illustration of the cell congestion in multi-cell environment** - -### 4.5.6 O1 usage example - -#### Example scenario - -- One mobile leased line network slice for live broadcasting is defined (S-NSSAI=1). -- The SLA for the slice is defined with the average total UL/DL throughput of 30 Mbps of the users in the slice provided in the coverage area (cellId=1, 2, 3). -- Note that O1 configuration is used to assure SLAs defined as long term performance values such as average throughput, which do not need frequent reconfiguration. -- In order to calculate the number of required PRBs to meet throughput requirement of the slice, Non-RT RIC collects wideband CQI distribution and data volume in UL/DL via O1. The calculated value is converted to the portion of PRB allocation to the slice i.e., rRMPolicyDedicatedRatio (as specified in 3GPP TS 28.541 [4]). -- Non-RT RIC sends rRMPolicyDedicatedRatio as O1 reconfiguration requests to E2 nodes. -- Non-RT RIC also collects UL/DL PRB used for data traffic and average UL/DL UE throughput in gNB. When the PRB usage becomes low, Non-RT RIC reconfigures rRMPolicyDedicatedRatio via O1 to decrease the allocated PRBs. When the PRB usage becomes high and throughput deterioration occurs, Non-RT RIC reconfigures rRMPolicyDedicatedRatio via O1 to increase the allocated PRBs. - -The illustration of the RRMPolicy reconfiguration via O1 is given in figure 4.5.6-1. - -![Figure 4.5.6-1: Illustration of the RRMPolicy reconfiguration via O1. The diagram shows two scenarios of PRB usage over time for Slice #1. In the left scenario, the initial PRB allocation is based on 'Wideband CQI distribution' and 'Data volume in UL'. The 'Monitoring and Reconfiguration in Non-RT RIC' identifies a need to 'Decrease PRBs for Slice #1 via O1 (rRMPolicyRatio)'. The right scenario shows the result: 'Low PRB usage' with a downward arrow indicating the decrease. In the right scenario, the initial PRB allocation is based on 'Data volume in UL'. The 'Monitoring and Reconfiguration in Non-RT RIC' identifies a need to 'Increase PRBs for Slice #1 via O1 (rRMPolicyRatio)'. The result shows 'High PRB usage' with an upward arrow indicating the increase, and a note about 'Throughput deterioration'.](e0113695dbf148bf5ec34354e544414b_img.jpg) - -Figure 4.5.6-1: Illustration of the RRMPolicy reconfiguration via O1. The diagram shows two scenarios of PRB usage over time for Slice #1. In the left scenario, the initial PRB allocation is based on 'Wideband CQI distribution' and 'Data volume in UL'. The 'Monitoring and Reconfiguration in Non-RT RIC' identifies a need to 'Decrease PRBs for Slice #1 via O1 (rRMPolicyRatio)'. The right scenario shows the result: 'Low PRB usage' with a downward arrow indicating the decrease. In the right scenario, the initial PRB allocation is based on 'Data volume in UL'. The 'Monitoring and Reconfiguration in Non-RT RIC' identifies a need to 'Increase PRBs for Slice #1 via O1 (rRMPolicyRatio)'. The result shows 'High PRB usage' with an upward arrow indicating the increase, and a note about 'Throughput deterioration'. - -Figure 4.5.6-1: Illustration of the RRMPolicy reconfiguration via O1 - -## 4.6 NSSI resource allocation optimization - -This use case provides the background, objectives, solution, and requirements for the NSSI resource optimization, an rApp implemented in Non-RT RIC, which leverages AI/ML inference on slice performance measurement data to determine the actions to automatically optimize the resource allocation for network slice instances. - -### 4.6.1 Background and goal of the use case - -Network slicing is essential to 5G, as it enables many new services across manufacturing, autonomous driving, gaming, and many more via the provision of ultra-low latency in URLLC and huge data volume in eMBB features that require different or contrasting QoS requirements exploiting a shared RAN node. The goal of this use case is to ensure the resources are allocated dynamically and efficiently among multiple network slices sharing the RAN node. - -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 time and locations. Cars with autonomous driving capability tend to require more URLLC services in the morning or afternoon rush hours in major freeways in big cities, while subscribers tend to consume eMBB services to watch video streaming at night in residential areas. Therefore, NSSI resource optimization rApp trains the AI/ML model, based on the huge volume of performance data collected over days, weeks, months from O-RAN nodes. It then performs inference function on the model with input measurements to predict the traffic demand patterns of 5G networks in different times and locations for each network slice, and automatically optimize the resource allocation for network slice instances accordingly. - -### 4.6.2 Entities/resources involved in the use case - -- 1) Non-RT RIC: - - a) Receive measurements to monitor the usage of RRM resources (e.g., PRB, RRC, DRB) identified by S-NSSAI from E2 nodes via the O1 interface. - - b) Perform the model training with input measurements data received from E2 nodes to create the model. - - c) Perform the inference function on the model with the input measurements data to determine if any actions shall be executed to update the resources on the E2 nodes. - - d) Configure the resources at the E2 nodes via O1 interface. - - e) Receive notifications from E2 nodes indicating the resource re-configuration was done. - - f) Update the O-Cloud resources via the O2 interface. - - g) Receive notifications from O-Cloud indicating the resource was updated. -- 2) E2 nodes (O-CU-CP, O-CU-UP, D-DU): - - a) Support the collections and reporting of measurements that are used to monitor the resource usage on per network slice basis via the O1 interface. - - b) Support the re-configuration of attributes to update the resources allocated to each network slice via the O1 interface. - -### 4.6.3 Solutions - -#### 4.6.3.1 NSSI resource optimization - -The context of the NSSI resource optimization is captured in table 4.6.3.1-1. - -**Table 4.6.3.1-1: NSSI resource optimization** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The goal is to ensure the resources (e.g., PRB, RRC, DRB) are allocated dynamically and efficiently among multiple network slices sharing the E2 nodes. | | -| Actors and Roles |
  • - SMO functions.
  • - Non-RT RIC framework.
  • - rApp: NSSI resource optimization.
  • - E2 nodes (i.e., O-CU-CP, O-CU-UP, O-DU).
| | -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - O1 interface connectivity is established.
| | -| Pre-conditions |
  • - O1 interfaces have been established to enable SMO to receive measurements from E2 nodes and configure the E2 nodes.
  • - R1 interface has been established to enable the rApp to receive measurements from E2 nodes and configure the E2 nodes via Non-RT RIC framework.
| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | - E2 nodes have been configured to collect the measurements and send them to Non-RT RIC framework. | | -| Begins when | The rApp utilizes the model to perform the inference function. | | -| Step 1 (M) | The rApp performs the offline model training with input measurements data received from E2 nodes to create the model. | | -| Step 2 (M) | Non-RT RIC framework receives the measurements from O-CU-CP via O1 to monitor the usage of RRM resources (e.g., RRC connected user). | | -| Step 3 (M) | Non-RT RIC framework sends the measurements to rApp via R1 interface. | | -| Step 4 (M) | Non-RT RIC framework receives the measurements from O-CU-UP via O1 to monitor the usage of RRM resources (e.g., the number of DRB allocated, and the number of PDU sessions). | | -| Step 5 (M) | Non-RT RIC framework sends the measurements to rApp via R1 interface. | | -| Step 6 (M) | Non-RT RIC framework receives the measurements from O-CU-UP via O1 to monitor the usage of RRM resources (e.g., the number of PRBs used in the downlink and uplink data traffic). | | -| Step 7 (M) | Non-RT RIC framework sends the measurements to rApp via R1 interface. | | -| Step 8 (M) | The rApp performs the inference function based on the model with input measurements data received to determine the actions to update the resources allocated to slices on the E2 nodes if needed. | | -| | If the rApp decides the RRM resources (e.g., RRC) in O-CU-CP need to be updated, then steps 9 to 12 are executed. | | -| Step 9 (O) | rApp requests Non-RT RIC framework via R1 interface to update the RRM resources for slices in O-CU-CP. | | -| Step 10 (O) | Non-RT RIC framework uses the modify MOI (Managed Object Instance) operation to configure the MOI(s) associated with the RRM resources at O-CU-CP via O1 interface. | | -| Step 11 (O) | Non-RT RIC framework receives a notification from O-CU-CP via O1 interface indicating the resource re-configuration was successful. | | -| Step 12 (O) | Non-RT RIC framework notifies rApp via R1 interface indicating the RRM resources in O-CU-CP have been successfully updated. | | -| | If the rApp decides the RRM resources (e.g., DRB) in O-CU-UP need to be updated, then steps 13 to 16 are executed. | | -| Step 13 (O) | rApp requests Non-RT RIC framework via R1 interface to update the RRM resources for slices in O-CU-UP. | | -| Step 14 (O) | Non-RT RIC framework uses the modify MOI operation to configure the MOI(s) associated with the RRM resource at O-CU-UP via O1 interface. | | -| Step 15 (O) | Non-RT RIC framework receives a notification from O-CU-UP via O1 interface indicating the resource re-configuration was successful. | | -| Step 16 (O) | Non-RT RIC framework notifies rApp via R1 interface indicating the RRM resources in O-CU-UP have been successfully updated. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | If the rApp decides the RRM resources (e.g., PRB) in O-DU need to be updated, then steps 17 to 20 are executed. | | -| Step 17 (O) | rApp requests Non-RT RIC framework via R1 interface to update the RRM resources for slices in O-DU. | | -| Step 18 (O) | Non-RT RIC framework uses the modify MOI operation to configure the MOI(s) associated with the RRM resource at O-DU via O1 interface. | | -| Step 19 (O) | Non-RT RIC framework receives a notification from O-DU via O1 interface indicating the resource re-configuration was successful. | | -| Step 20 (O) | Non-RT RIC framework notifies rApp via R1 interface indicating the RRM resources in O-DU have been successfully updated. | | -| | If the rApp decides the O-Cloud resources need to be updated, then steps 21 to 24 are executed: | | -| Step 21 (O) | rApp requests Non-RT RIC framework via R1 interface to update the O-Cloud resources. | | -| Step 22 (O) | Non-RT RIC framework re-configures the O-Cloud resources via O2 interface. | | -| Step 23 (O) | Non-RT RIC framework receives a notification via O2 interface indicating the resource re-configuration was successful. | | -| Step 24 (O) | Non-RT RIC framework notifies rApp via R1 interface indicating the O-Cloud resources have been successfully updated. | | -| Ends when | The resources have been optimized. | | -| Exceptions | None identified. | | -| Post Conditions | None. | | -| Traceability | REQ-R1-FUN9, REQ-R1-FUN10. | | - -NOTE: How the O-Cloud resources are to be monitored and updated is not defined in the present document. - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "Service Management and Orchestration" #gold - Participant NON as "Non-RT RIC Framework\n& O1/2 terminations" - Participant RAPP as "NSSI Optimization rApp" - -``` - -``` -end box -``` - -``` -Box "O-RAN" #lightpink -``` - -``` - Participant CUCP as "O-CU-CP" -``` - -``` - Participant CUUP as "O-CU-UP" -``` - -``` - Participant DU as "O-DU" -``` - -``` - Participant OC as "O-Cloud" -``` - -``` -End box -``` - -``` -RAPP-> RAPP : Perform offline model training with \ninput measurement data from E2\nnodes to create the model. -``` - -``` -group Loop: NSSI resource optimization loop -``` - -``` -group input data collection -``` - -``` - CUCP->NON : <> PM data to monitor the usage of RRM resources (e.g. RRC) -``` - -``` - NON-> RAPP : <> input measurement data \nfor RRM resources -``` - -``` - CUUP->NON : <> PM data to monitor the usage of RRM resources (e.g. DRB) -``` - -``` - NON-> RAPP : <> input measurement data \nfor RRM resources -``` - -``` - DU->NON : <> PM data to monitor the usage of RRM resources (e.g. PRB) -``` - -``` - NON-> RAPP : <> input measurement data \nfor RRM resources -``` - -``` -end -``` - -``` -group Inference -``` - -``` - RAPP-> RAPP : Performs inference based on the model \nwith input measurement data from E2\nnodes to decide the actions to update\nthe resources in E2 nodes if needed -``` - -``` -end -``` - -``` - group Opt: resources in O-CU-CP need to be updated -``` - -``` - RAPP-> NON : <> Request to update the \nRRM resources (e.g. RRC) -``` - -``` - NON-> CUCP : <> Configure the MOI associated with the RRM resources -``` - -``` - CUCP-> NON : <> Notify the resource re-configuration was successful -``` - -``` - NON-> RAPP : <> Notify the RRM \nresources being updated -``` - -``` -end -``` - -``` - group Opt: resources in O-CU-UP need to be updated -``` - -``` -RAPP-> NON : <> Request to update the \n RRM resources (e.g. DRB) -NON-> CUUP : <> Configure the MOI associated with the RRM resources -CUUP-> NON : <> Notify the resource re-configuration was successful -NON-> RAPP : <> Notify the RRM \nresources being updated - -end - -group Opt: resources in O-DU need to be updated - RAPP-> NON : <> Request to update the \nRRM resources (e.g. PRB) - NON-> DU : <> Configure the MOI associated with the RRM resources - DU-> NON : <> Notify the resource re-configuration was successful - NON-> RAPP : <> Notify the RRM \nresources being updated - -End - -group Opt: O-Cloud resources need to be updated - RAPP-> NON : <> Request to update the \nO-Cloud resources - NON-> OC : <> Configure the MOI associated with the O-Cloud resources - OC-> NON : <> Notify the resource re-configuration was successful - NON-> RAPP : <> Notify the O-Cloud \nresources being updated - -end -end -@enduml -``` - -The flow diagram of the NSSI resource optimization is given in figure 4.6.3.1-1. - -![NSSI resource optimization flow diagram showing interactions between Service Management and Orchestration and O-RAN components (O-CU-CP, O-CU-UP, O-DU, O-Cloud).](27788c2a26d9641e68232a4eff1299b9_img.jpg) - -The diagram illustrates the NSSI resource optimization flow. It is divided into two main horizontal sections at the top: **Service Management and Orchestration** (yellow) and **O-RAN** (pink). The Service Management and Orchestration section contains two boxes: **Non-RT RIC Framework & O1/I2 terminations** and **NSSI Optimization rApp**. The O-RAN section contains four boxes: **O-CU-CP**, **O-CU-UP**, **O-DU**, and **O-Cloud**. A text box between them states: "Perform offline model training with 1 input measurement data from E2 nodes to create the model." with an arrow pointing from the rApp to the O-RAN components. - -The main part of the diagram is a sequence of messages within a **Loop: NSSI resource optimization loop**: - -- input data collection**: - - 2 <> PM data to monitor the usage of RRM resources (e.g. RRC) - - 3 <> input measurement data for RRM resources - - 4 <> PM data to monitor the usage of RRM resources (e.g. DRB) - - 5 <> input measurement data for RRM resources - - 6 <> PM data to monitor the usage of RRM resources (e.g. PRB) - - 7 <> input measurement data for RRM resources -- Inference**: - - 8 Performs inference based on the model with input measurement data from E2 nodes to decide the actions to update the resources in E2 nodes if needed -- Opt: resources in O-CU-CP need to be updated**: - - 9 <> Request to update the RRM resources (e.g. RRC) - - 10 <> Configure the MOI associated with the RRM resources - - 11 <> Notify the resource re-configuration was successful - - 12 <> Notify the RRM resources being updated -- Opt: resources in O-CU-UP need to be updated**: - - 13 <> Request to update the RRM resources (e.g. DRB) - - 14 <> Configure the MOI associated with the RRM resources - - 15 <> Notify the resource re-configuration was successful - - 16 <> Notify the RRM resources being updated -- Opt: resources in O-DU need to be updated**: - - 17 <> Request to update the RRM resources (e.g. PRB) - - 18 <> Configure the MOI associated with the RRM resources - - 19 <> Notify the resource re-configuration was successful - - 20 <> Notify the RRM resources being updated -- Opt: O-Cloud resources need to be updated**: - - 21 <> Request to update the O-Cloud resources - - 22 <> Configure the MOI associated with the O-Cloud resources - - 23 <> Notify the resource re-configuration was successful - - 24 <> Notify the O-Cloud resources being updated - -The diagram ends with a footer section containing the same **Non-RT RIC Framework & O1/I2 terminations** and **NSSI Optimization rApp** boxes, and the **O-CU-CP**, **O-CU-UP**, **O-DU**, and **O-Cloud** boxes. - -NSSI resource optimization flow diagram showing interactions between Service Management and Orchestration and O-RAN components (O-CU-CP, O-CU-UP, O-DU, O-Cloud). - -Figure 4.6.3.1-1: NSSI resource optimization flow diagram - -### 4.6.4 Required data - -This sub-clause contains the input and output data of model training and inference. - -#### 4.6.4.1 Input data - -The measurement input data are used in model training and inference. They include the following measurements to monitor the resource usage for network slices in E2 nodes: - -1) Measurements used to monitor the usage of RRC related resources in O-CU-CP include: - -- Mean number of RRC connections – provides the mean number of RRC connections with sub-counters per S-NSSAI (as specified in 3GPP TS 28.552 [5], clause 5.1.1.4.1). -- Max number of RRC connections – provides the max number of RRC connections with sub-counters per S-NSSAI (as specified in 3GPP TS 28.552 [5], clause 5.1.1.4.2). - -2) Measurements used to monitor the usage of DRB related resources in O-CU-UP include: - -- Mean number of DRBs being allocated – provides the mean number of DRBs being allocated in the PDU sessions with sub-counters per S-NSSAI (as specified in 3GPP TS 28.552 [5], clause 5.1.1.10.9). -- Peak number of DRBs being allocated – provides the peak number of DRBs being allocated in the PDU sessions with sub-counters per S-NSSAI (as specified in 3GPP TS 28.552 [5], clause 5.1.1.10.10). - -3) Measurements used to monitor the usage of PRB related resources in O-DU include: - -- Mean DL PRB used for data traffic – provides the mean number of PRBs used in downlink for data traffic with sub-counters per S-NSSAI (as specified in 3GPP TS 28.552 [5], clause 5.1.1.2.5). -- Peak DL PRB used for data traffic – provides the peak number of PRBs used in downlink for data traffic with sub-counters per S-NSSAI (as specified in 3GPP TS 28.552 [5], clause 5.1.1.2.9). -- Mean UL PRB used for data traffic – provides the mean number of PRBs used in uplink for data traffic with sub-counters per S-NSSAI (as specified in 3GPP TS 28.552 [5], clause 5.1.1.2.7). -- Peak UL PRB used for data traffic – provides the peak number of PRBs used in uplink for data traffic with sub-counters per S-NSSAI (as specified in 3GPP TS 28.552 [5], clause 5.1.1.2.10). -- Mean number of PDU sessions being allocated – provides the mean number of PDU sessions being allocated with sub-counters per S-NSSAI (as specified in 3GPP TS 28.552 [5], clause 5.1.1.5.4). -- Peak number of PDU sessions being allocated – provides the peak number of PDU sessions being allocated with sub-counters per S-NSSAI (as specified in 3GPP TS 28.552 [5], clause 5.1.1.5.5). -- Mean number of active UEs in the DL per cell – provides the mean number of active UEs in downlink with sub-counters per S-NSSAI (as specified in 3GPP TS 28.552 [5], clause 5.1.1.23.1). -- Max number of active UEs in the DL per cell – provides the max number of active UEs in downlink with sub-counters per S-NSSAI (as specified in 3GPP TS 28.552 [5], clause 5.1.1.23.2). -- Mean number of active UEs in the UL per cell – provides the mean number of active UEs in uplink with sub-counters per S-NSSAI (as specified in 3GPP TS 28.552 [5], clause 5.1.1.23.3). -- Max number of active UEs in the UL per cell – provides the max number of active UEs in uplink with sub-counters per S-NSSAI (as specified in 3GPP TS 28.552 [5], clause 5.1.1.23.4). - -#### 4.6.4.2 Output data - -The output data, including NRCellCU IOC, NRCellDU IOC, GNBDFUFunction IOC, GNBCUCPFunction IOC, GNBCUUPFunction IOC and RRMPolicyRatio IOC with RRMPolicy abstract class (as specified in 3GPP TS 28.541 [4]), are needed to enable NSSI resource optimization rApp to re-configure the resources via O1 and O2 interfaces. - -### 4.6.5 O1 usage example - -An example of two NSSIs, where NSSI#1 groups E2 nodes (i.e., O-DU, O-CU-CP, and O-CU-UP), and NSSI#2 groups 5GC NFs is shown in figure 4.6.5-1. It also shows that two network slices, identified by S-NSSAI#1 supporting URLLC, and S-NSSAI#2 supporting eMBB. The goal of this use case is to optimize the resources associated with RAN network slices. - -![Diagram illustrating NSSI resource optimization. It shows two main groups: NSSI#1 (containing O-DU, O-CU-UP, and O-CU-CP) and NSSI#2 (containing 5GC). NSSI#1 is further divided into User plane (O-CU-UP) and Control plane (O-CU-CP). S-NSSAI#1 and S-NSSAI#2 are shown as labels for the network slices supported by the O-DU and O-CU-UP.](a9159a006d67a834a7b1a771c18191cc_img.jpg) - -The diagram illustrates the resource optimization example. It shows two main groups: NSSI#1 and NSSI#2. NSSI#1 contains the O-DU, O-CU-UP, and O-CU-CP. NSSI#2 contains the 5GC. The O-DU is connected to the O-CU-UP and O-CU-CP. The O-CU-UP is connected to the 5GC. The O-CU-CP is connected to the 5GC. The O-DU is labeled with S-NSSAI#1 and S-NSSAI#2. The O-CU-UP is labeled with S-NSSAI#1 and S-NSSAI#2. The O-CU-CP is labeled with S-NSSAI#1 and S-NSSAI#2. The 5GC is labeled with S-NSSAI#1 and S-NSSAI#2. The diagram is divided into User plane and Control plane sections. - -Diagram illustrating NSSI resource optimization. It shows two main groups: NSSI#1 (containing O-DU, O-CU-UP, and O-CU-CP) and NSSI#2 (containing 5GC). NSSI#1 is further divided into User plane (O-CU-UP) and Control plane (O-CU-CP). S-NSSAI#1 and S-NSSAI#2 are shown as labels for the network slices supported by the O-DU and O-CU-UP. - -Figure 4.6.5-1: NSSI resource optimization example - -NSSI resources optimization rApp runs model inference with input measurement data collected from E2 nodes for S-NSSAI#1 and S-NSSAI#2, and detects a traffic pattern for O-DU serving an area with high density of business and residential users at the time on a given day. An example of PRB resource allocation for S-NSSAI#1 and S-NSSAI#2 at the O-DU is shown in figure 4.6.5-2. - -- At 15:00, the dedicated resources and prioritized resources for S-NSSAI#1 were increased to 20% and 50% respectively for as more cars demand more URLLC services at the start of rush hours. -- At 17:00, the dedicated resources, prioritized resources, and shared resources for S-NSSAI#1 were further increased as the rush hours traffic getting worse. -- At 19:00, the dedicated resources, prioritized resources, and shared resources for S-NSSAI#2 were increased to 20%, 60%, and 75% respectively as more residential users demand more eMBB services for home video streaming. -- At 20:00, the dedicated resources, prioritized resources, and shared resources for S-NSSAI#1 were decreased as the rush hours traffic coming to end. -- At 21:00, the dedicated resources, prioritized resources, and shared resources for S-NSSAI#2 were further increased as the demand for eMBB services increased. -- At 22:00, the dedicated resources, prioritized resources, and shared resources for S-NSSAI#1 were decreased as the demand for URLLC services further reduced. -- At 24:00, the dedicated resources, prioritized resources, and shared resources for S-NSSAI#2 were decreased to 10%, 25%, and 60% respectively as the demand for eMBB services further reduced. - -![Figure 4.6.5-2: Example of network slice resource allocations for O-DU. The figure shows two network slices, S-NSSAI#1 and S-NSSAI#2, over a timeline from 13:00 to 24:00. Each slice has a vertical bar representing resource allocation, divided into Shared resources (diagonal lines), Prioritized resources (cross-hatch), and Dedicated resources (solid fill). The Y-axis for each slice shows percentages from 0 to 100, with labels for MaxRatio, MinRatio, and DedicatedRatio. S-NSSAI#1 shows higher resource usage during the day (13:00-17:00) and lower usage at night (19:00-24:00). S-NSSAI#2 shows the opposite pattern, with higher usage at night and lower usage during the day.](5a31f8496931f6aa7570270dbeefca1e_img.jpg) - -| Time | S-NSSAI#1 MaxRatio | S-NSSAI#1 MinRatio | S-NSSAI#1 DedicatedRatio | S-NSSAI#2 MaxRatio | S-NSSAI#2 MinRatio | S-NSSAI#2 DedicatedRatio | -|-------|--------------------|--------------------|--------------------------|--------------------|--------------------|--------------------------| -| 13:00 | 75 | 25 | 10 | 60 | 25 | 10 | -| 15:00 | 50 | 20 | 0 | 60 | 25 | 10 | -| 17:00 | 60 | 30 | 0 | 60 | 25 | 10 | -| 19:00 | 60 | 45 | 15 | 75 | 20 | 0 | -| 20:00 | 60 | 45 | 15 | 75 | 20 | 0 | -| 21:00 | 45 | 30 | 10 | 80 | 25 | 0 | -| 22:00 | 45 | 30 | 10 | 80 | 25 | 0 | -| 24:00 | 45 | 30 | 10 | 60 | 25 | 10 | - -Figure 4.6.5-2: Example of network slice resource allocations for O-DU. The figure shows two network slices, S-NSSAI#1 and S-NSSAI#2, over a timeline from 13:00 to 24:00. Each slice has a vertical bar representing resource allocation, divided into Shared resources (diagonal lines), Prioritized resources (cross-hatch), and Dedicated resources (solid fill). The Y-axis for each slice shows percentages from 0 to 100, with labels for MaxRatio, MinRatio, and DedicatedRatio. S-NSSAI#1 shows higher resource usage during the day (13:00-17:00) and lower usage at night (19:00-24:00). S-NSSAI#2 shows the opposite pattern, with higher usage at night and lower usage during the day. - -Figure 4.6.5-2: Example of network slice resource allocations for O-DU - -## 4.7 Massive MIMO optimization - -Massive MIMO optimization is one of the top priority use cases in O-RAN. Several massive MIMO sub-features have been proposed and studied during the massive MIMO pre-normative study, which is documented in the O-RAN.WG1.MMIMO-USE-CASES-TR-v01.00 [i.3], including the potential data requirements for each of the sub-use cases. The following sub-clauses provide the background, objectives, solutions, deployment options, and identified WG2 requirements for massive MIMO sub-features - -### 4.7.1 Massive MIMO Grid-of-Beams Beamforming (GoB BF) optimization - -#### 4.7.1.1 Background and goal of the use case - -Massive MIMO (mMIMO) is among the key methods to increase performance and QoS in 5G networks. Capacity enhancement is obtained by means of beamforming of the transmitted signals, and by spatially multiplexing data streams. Beamforming can increase the received signal power and simultaneously decrease the interference generated for other users, hence resulting in higher SINR and higher user throughputs. Grid-of-Beams (GoB) with the corresponding beam sweeping has been introduced to allow beamforming of the control channels used during initial access as well as for data transmission and reception, mainly for high frequency (but can be used also for the sub-6 GHz band) MIMO operation. The physical properties of the antenna array and its possible configurations characterize the span of the beams, namely the horizontal and vertical aperture in which beamforming is supported, and therefore the coverage area and the shape of the cell. mMIMO can be deployed in 5G macrocell clusters as well as in heterogeneous networks, where macrocells and small cells co-exist and complement each other for better aggregated capacity and coverage. In order to obtain optimal beamforming and cell resources (Tx power, PRB) configuration, one will have to look at a multi-cell environment instead of a single cell. Moreover, different vendors can have different implementations in terms of the number of beams, the horizontal/vertical beam widths, azimuth and elevation range, to achieve the desired coverage. In a multi-node/multi- - -vendor scenario, centralized monitoring and control is required to offer optimal coverage, capacity and mobility performance as well as control over electromagnetic emissions in order to comply with regulatory requirements. - -The problem associated with traditional mMIMO BF is that its performance is highly dependent on the choice of the Beam Forming (BF) pattern. Manual configuration is usually based on the empirical knowledge and manual test results of the domain expert(s) and is performed in a semi-static way. That is, (near-)real time contextual, per-site information (such as cell geometry change, user/traffic distribution, mobility patterns, seasonalities etc.) is taken into account in a suboptimal and non-real-time way. This can cause one or more of the following problems: - -1. High inter-cell interference. -2. Unbalanced traffic between neighboring cells. -3. Low performance at the cell edges or throughout the cell. -4. Poor handover performance. - -This solution proposes a framework that allows the operator to flexibly configure the mMIMO BF parameters in a cell or in a cluster of cells by means of policies and configuration assisted by Machine Learning (ML) techniques. The configuration optimization relies on contextual information and patterns such as the user distribution, traffic demand distribution, cell geometries, and mobility. - -#### 4.7.1.2 Entities/resources involved in the use case - -- 1) SMO & Non-RT RIC Framework (FW): - - a) Collect the necessary configurations, performance indicators, and measurement reports from the E2 nodes (O-DU), triggered by Non-RT RIC FW if required. - - b) Transfer collected data towards rApp. - - c) Provide optimized mMIMO GoB parameters via O1 (to O-DU) or open FH M-plane (to O-RU) interface. - - d) Optional: Retrieve necessary enrichment information (UE location related information, e.g., GPS coordinates) for the purpose of i) training relevant rApps and ii) execution of relevant rApps. -NOTE: Exposure of enrichment information to rApps is not defined in the present document. - - e) Monitor the performance of the respective cells; when the optimization objective fails, initiate fallback procedure and/or trigger the rApp model retraining and re-optimization. - - f) Execute the inference/control loop periodically or event-triggered. - - g) Optional: The ML model training can be done by the Non-RT RIC FW. -- 2) rApps: - - a) Retrieve the necessary configurations, performance indicators, and measurement reports from the E2 nodes and necessary enrichment information via the SMO, for the purpose of training and execution of relevant AI/ML models. - - b) Infer an optimized GoB BF configuration. -- 3) E2 nodes & O-RU: - - a) Collect and provide necessary measurements and KPIs to the SMO (see Required data clause). - - b) Apply mMIMO GoB configuration received from the SMO. - -NOTE: Both aggregated and disaggregated gNB architecture are supported. - -#### 4.7.1.3 Solutions - -The context of the creation and deployment of mMIMO GoB BF optimization applications is captured in table 4.7.1.3-1. - -Table 4.7.1.3-1: Creation and deployment of mMIMO GoB BF optimization applications - -| Use Case Stage | Evolution / Specification | <> | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Goal | Optimized beamforming configuration with the Grid-of-Beams method. | | -| Actors and Roles | SMO, Non-RT RIC, E2 nodes, O-RU | | -| Assumptions | All relevant functions and components are instantiated.
O1 and OFH-MP interface connectivity is established. | | -| Pre-conditions | Near-RT RIC and Non-RT RIC are instantiated.
O1 interface is established between SMO and Near-RT RIC and E2 nodes, OFH-MP is established between O-DU(s) and O-RU(s). | | -| Begins when | GoB BF optimization rApp with initial ML model is deployed. | | -| Step 1 (M) | SMO/Non-RT RIC FW collects the necessary configurations, performance indicators, and measurement reports from E2 nodes (O-DU). | | -| Step 2 (O) | SMO/Non-RT RIC FW collects input data from external apps. | | -| Step 3-6 (M) | Collected data is transferred to rApp from the SMO/Non-RT RIC FW and rApp trains the necessary ML model(s). | | -| Step 7-10 (M) | A new optimization trigger is applied or re-optimization of the GoB BF is necessary due to low performance. ML model assisted rApp infers optimized GoB BF configuration and transfers it to the SMO/Non-RT RIC. | | -| Step 11-13 (M) | SMO/Non-RT RIC FW applies the optimized GoB BF configuration via O1 or via O1 and OFH-MP. | | -| Step 14-20 (O) | SMO/Non-RT RIC FW continuously monitors GoB BF performance in respective cells. Optionally, it initiates fallback in case performance is unsatisfactory and requests ML model retraining/update. Then, rApp retrains/updates the respective ML model(s). | | -| Ends when | On operator request of rApp is disabled. | | -| Exceptions | None identified. | | -| Post Conditions | GoB BF configuration is active. | | -| Traceability | REQ-Non-RT-RIC-FUN1, REQ-Non-RT-RIC-FUN5, REQ-Non-RT-RIC-FUN6, REQ-Non-RT-RIC-FUN8, REQ-Non-RT-RIC-FUN9 | | - -``` - -@startuml - -box "Service Management & \nOrchestration Framework" #gold - Participant "SMO & Non-RT RIC FW" as SMO - Participant "rApps" as rAPP -end box - -box "E2 Nodes" #lightpink - -``` - -``` -collections "O-CUs" as OCU -collections "O-DUs" as ODU - -end box - -box "O-RUs" #lightpink - collections "O-RUs" as ORUs -end box - -box "External" #lightseagreen - Participant APP -end box - -Autonumber - -activate APP -activate SMO -activate rAPP -activate ODU -||| - -group Data Collection - ODU -> SMO : <> Data Collection - APP --> SMO : Data Collection -end - -group ML Training - ODU -> SMO : <> Data Collection - APP --> SMO : Data Collection - SMO -> rAPP: <> Data Retrieval - rAPP --> rAPP: AI/ML model training -end - -group ML Inference -alt - hnote over rAPP: Optimization Target/Trigger received -else -``` - -``` - -SMO --> SMO: Performance Degradation -end - -SMO -> rAPP: <> Data Retrieval -rAPP --> rAPP: AI/ML model inference -rAPP -> SMO: <> Optimal mMIMO GoB Configuration -end - -group GoB Configuration -alt via O1 - SMO -> ODU: <> Provide new mMIMO GoB configuration -else via OFH-MP - SMO -> ORUs: <> Provide new mMIMO GoB configuration - SMO -> ODU: <> Information about new mMIMO GoB configuration -end -end - -group ML Performance Monitoring - ODU -> SMO : <> Data Collection - APP --> SMO : Data Collection - SMO --> SMO : Performance monitoring and evaluation - opt - SMO --> SMO : Fallback (e.g. restore configuration) - SMO -> ODU: <> Default/Fallback mMIMO configuration - SMO -> rAPP : <> Model retraining and update request - rAPP --> rAPP : ML Model retraining - end -end - -@enduml - -``` - -The flow diagram of GoB BF optimization is given in figure 4.7.1.3-1. - -![Sequence diagram for GoB BF optimization showing interactions between Service Management & Orchestration Framework, E2 Nodes, O-RUs, and External APP.](8ab30dbff406204a68c59ae7c1b77413_img.jpg) - -The diagram illustrates the sequence of interactions for GoB BF optimization across five main phases: - -- Data Collection:** - - 1 <> Data Collection (rApps to O-CUs) - - 2 Data Collection (O-CUs to rApps) -- ML Training:** - - 3 <> Data Collection (rApps to O-CUs) - - 4 Data Collection (O-CUs to rApps) - - 5 <> Data Retrieval (rApps to O-CUs) - - 6 AI/ML model training (O-CUs to rApps) -- ML Inference:** - - alt: Optimization Target/Trigger received - - 7 Performance Degradation (O-CUs to rApps) - - 8 <> Data Retrieval (rApps to O-CUs) - - 9 AI/ML model inference (O-CUs to rApps) - - 10 <> Optimal mMIMO GoB Configuration (rApps to O-CUs) -- GoB Configuration:** - - alt: [via O1] - - 11 <> Provide new mMIMO GoB configuration (rApps to O-CUs) - - alt: [via OFH-MP] - - 12 <> Provide new mMIMO GoB configuration (rApps to O-RUs) - - 13 <> Information about new mMIMO GoB configuration (rApps to O-CUs) -- ML Performance Monitoring:** - - 14 <> Data Collection (rApps to O-CUs) - - 15 Data Collection (O-CUs to rApps) - - 16 Performance monitoring and evaluation (O-CUs to rApps) - - opt: Fallback (e.g. restore configuration) - - 17 Fallback (e.g. restore configuration) (O-CUs to rApps) - - 18 <> Default/Fallback mMIMO configuration (rApps to O-CUs) - - 19 <> Model retraining and update request (rApps to O-CUs) - - 20 ML Model retraining (O-CUs to rApps) - -Sequence diagram for GoB BF optimization showing interactions between Service Management & Orchestration Framework, E2 Nodes, O-RUs, and External APP. - -Figure 4.7.1.3-1: Flow diagram of GoB BF optimization - -#### 4.7.1.4 Required data - -The specification of the data communicated over O1 is outside the scope of WG2. There are no data that are relevant for the A1 interface. - -### 4.7.2 Massive MIMO Non-GoB Beamforming (Non-GoB BF) optimization - -This use case provides the background and motivation for the O-RAN architecture to support Non-Grid of Beams beamforming optimization. Non-RT RIC could be used to train AI/ML models for Non-GoB BF selection xApps, which intelligently recommend best Non-GoB BF modes to a O-gNB or O-DU. - -Note that non-AI/ML based solutions for Non-GoB BF optimization is not precluded. The AI/ML model training, deployment, and inference described below are not applicable to non-AI/ML based solutions. - -#### 4.7.2.1 Background and goal of the use case - -Non-GoB BF approaches are an important class of beamforming algorithms for 5G massive MIMO deployments, especially for implementations in sub-6 GHz frequency bands. For example, beam weights can be computed at the O-gNB or O-DU based on channel measurements of Sounding Reference Signals (SRS) without predefined beam sets, assuming uplink and downlink correspondence. - -Noted that Non-GoB BF modes are not standardized, instead they are vendor-specific proprietary algorithms. Multiple Non-GoB BF modes can be implemented, as some modes perform better than others under particular wireless conditions. Non-GoB BF modes can differ in the following aspects: - -- MIMO modes (i.e., SU-MIMO or MU-MIMO) -- Channel estimation algorithms -- Beam weight calculation approaches (e.g., Matched Filter (MF), Zero-Forcing (ZF), eigen-beamforming, etc.) -- Time and frequency granularity of beamforming, etc. - -To select the best Non-GoB BF modes, the SMO/Non-RT RIC and the Near-RT RIC are not required to understand the details of a specific Non-GoB BF modes, e.g., how the beamforming weights are computed under a mode. They only need to know how many Non-GoB BF modes are supported in the O-DU and the performance of each mode. - -The goal of this use case is therefore to provide an intelligent control over multiple supported Non-GoB BF modes in order to recommend a preferred mode to a BS as a function of wireless conditions, such as channel quality, UE location and mobility, interference condition, PHY layer configuration, etc. - -#### 4.7.2.2 Entities/resources involved in the use case - -- 1) SMO/Non-RT RIC: - - a) Retrieve the number of supported Non-GoB BF modes in O-DU via the O1 interface. - - b) Retrieve performance measurement data and UE context information (e.g., SRS periodicity) from O-DU via the O1 interface, for each Non-GoB BF mode. - - c) Collect enrichment information from external sources such as application servers. - - d) Associate enrichment information with collected measurements and configurations. - - e) Perform model training. - - f) Perform model deployment. - - g) Perform model performance monitoring and model re-training. - - h) Send enrichment information to the Near-RT RIC for inference via the A1 interface. - -Note that the model can be trained in the Non-RT RIC framework or in the Non-GoB BF optimization rApp. - -- 2) Near-RT RIC: - - a) Receive enrichment information via the A1 interface. - - b) Support AI/ML model deployment from the SMO/Non-RT RIC. - - c) Receive performance measurement data and UE context information (e.g., SRS periodicity) from O-DU via the E2 interface. - - d) Associate enrichment information with collected measurements and configurations. - - e) Select Non-GoB modes, e.g., by performing model inference. - - f) Send Non-GoB BF control/policy message to O-DU via the E2 interface. - -Note that the requirements of Near-RT RIC are under the scope of WG3. - -- 3) O-DU: - - a) Send the number of supported Non-GoB BF modes to SMO/Non-RT RIC via the O1 interface. - - b) Send measurement data and UE context information (e.g., SRS periodicity) to SMO/Non-RT RIC via the O1 interface. - - c) Send measurement data and UE context information (e.g., SRS periodicity) to the Near-RT RIC via the E2 interface. - - d) Support Non-GoB control/policy message received from the Near-RT RIC via the E2 interface. - -Note that the requirements of O1 interface for O-DU are under the scope of WG5. - -#### 4.7.2.3 Solutions - -##### 4.7.2.3.1 AI/ML-assisted Non-GoB BF mode selection - -Note that data collection over E2 interface and E2 control/policy procedures shown in table 4.7.2.3.1-2 and in figure 4.7.2.3.1-2 are under the scope of WG3. Note that external interface between the Non-RT RIC and the external sources (e.g., application servers) is not specified by O-RAN. - -The context of the AI/ML-assisted Non-GoB BF mode selection – model training, deployment, and update is captured in table 4.7.2.3.1-1. - -**Table 4.7.2.3.1-1: AI/ML-assisted Non-GoB BF mode selection – model training, deployment, and update** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To train an AI/ML model to select the best Non-GoB BF modes given wireless conditions and per-UE configurations. | | -| Actors and Roles | SMO, Non-RT RIC, Near-RT RIC, O-DU, external sources, e.g., application server | | -| Assumptions | - All relevant functions and components are instantiated. | | -| Pre-conditions |
  • - O1 interface is established between SMO and O-DU to enable SMO/Non-RT RIC to obtain the number of supported Non-GoB BF modes and to collect performance measurement data and associated per-UE configuration.
  • - A1 interface is established between Non-RT RIC and Near-RT RIC to enable enrichment information transfer.
  • - O-DU supports Non-GoB BF.
| | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Begins when | Operator specified trigger condition or event is satisfied. | | -| Step 1 (M) | SMO requests the number of supported Non-GoB BF modes in O-DU via the O1 interface. | | -| Step 2 (M) | SMO collects the number of supported Non-GoB BF modes in O-DU via the O1 interface. | | -| Step 3 (M) | Non-RT RIC retrieves collected information. | | -| Step 4 (M) | For each Non-GoB BF mode, SMO requests performance measurement data and associated UE context information (e.g., SRS periodicity) from O-DU for model training via the O1 interface. | | -| Step 5 (M) | SMO collects required performance measurement data and UE context information (e.g., SRS periodicity) from O-DU via the O1 interface. | | -| Step 6 (O) | SMO collects enrichment information (e.g., UE mobility and location info) from external sources, e.g., application server. | | -| Step 7 (O) | Non-RT RIC retrieves collected data and enrichment information. | | -| Step 8 (O) | For each Non-GoB BF mode, Non-RT RIC associates received enrichment information with measurement data and UE context information. | | -| Step 9 (M) | Non-RT RIC performs model training. | | -| Step 10 (M) | Non-RT RIC requests to deploy the trained AI/ML model. | | -| Step 11 (M) | SMO/Non-RT RIC deploys trained model to the Near-RT RIC via O1 or O2 interface. | | -| Step 12 (M) | SMO requests performance measurement data, including the active Non-GoB BF mode index, from O-DU for performance monitoring via the O1 interface. | | -| Step 13 (M) | SMO collects performance measurement data, including the active Non-GoB BF mode index, from O-DU for performance monitoring via the O1 interface. | | -| Step 14 (O) | SMO collects enrichment information (e.g., UE mobility and location info) from external sources, e.g., application server. | | -| Step 15 (O) | Non-RT RIC retrieves collected performance monitoring data and enrichment information. | | -| Step 16 (M) | Non-RT RIC evaluates the performance of deployed AI/ML model. | | -| Step 17 (M) | Non-RT RIC re-trains the model. | | -| Step 18 (M) | Non-RT RIC requests to deploy the updated AI/ML model. | | -| Step 19 (M) | SMO/Non-RT RIC updates model in the Near-RT RIC via O1 or O2 interface. | | -| Ends when | Operator specified trigger condition or event is satisfied. | | -| Exceptions | None identified. | | -| Post Conditions | Near-RT RIC executes the deployed model for AI/ML-assisted Non-GoB BF. | | - -| Use Case Stage | Evolution / Specification | <> | -|----------------|----------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Traceability | REQ-Non-RT-RIC-FUN1, REQ-Non-RT-RIC-FUN4, REQ-Non-RT-RIC-FUN5, REQ-Non-RT-RIC-FUN9,
REQ-A1-FUN2 | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -autonumber - -Box "Service Management and Orchestration" #gold - Participant "SMO functions" as smo - Participant "Non-RT RIC" as non -End box - -Box "O-RAN" #lightpink - Participant near as "Near-RT RIC" - Participant ran as "O-DU" -End box - -Box "External" #lightcyan - Participant "Application Server" as app -End box - -group Data Collection - smo -> ran : <> Request the number of supported Non-GoB BF modes - ran -> smo : <> Collect the number of supported Non-GoB BF modes - smo -> non : Retrieve collected information - - smo -> ran : <> Request measurement data and UE context information for each Non-GoB BF mode - ran -> smo : <> Collect measurement data and UE context information for each Non-GoB BF mode - app -> smo : Collect enrichment information (e.g., UE location/mobility, etc.) - -``` - -``` - -smo -> non : Retrieve collected data -end - -group AI/ML workflow - non -> non : Associate enrichment information with \n measurements and configurations - non -> non : Train AI/ML models to select \n the best Non-GoB mode - non -> smo : Request to deploy trained AI/ML models - smo -> near: <> or <> \n Deploy AI/ML models -end - -group Performance evaluation and optimization - smo -> ran : <> Request measurement data and UE context information - ran -> smo : <> Collect measurement data and UE context information - app -> smo : Collect enrichment information (e.g., UE location/mobility, etc.) - smo -> non : Retrieve collected data - non -> non : Performance monitoring & evaluation - non -> non : Re-train AI/ML models - non -> smo : Request to deploy updated AI/ML models - smo -> near: <> or <> \n Update AI/ML models -end - -@enduml - -``` - -The flow diagram of the AI/ML-assisted Non-GoB BF mode selection - model training, deployment, and performance monitoring is given in figure 4.7.2.3.1-1. - -![Sequence diagram for AI/ML-assisted Non-GoB BF mode selection. Lifelines: SMO functions, Non-RT RIC, Near-RT RIC, O-DU, Application Server. The process is divided into three phases: Data Collection, AI/ML workflow, and Performance evaluation and optimization. The diagram shows 19 numbered interactions between these components.](364054adcd1b427fa259450e006c6b38_img.jpg) - -``` - -sequenceDiagram - participant SMO functions - participant Non-RT RIC - participant Near-RT RIC - participant O-DU - participant Application Server - - Note left of SMO functions: Data Collection - SMO functions->>Near-RT RIC: 1 <> Request the number of supported Non-GoB BF modes - Near-RT RIC-->>SMO functions: 2 <> Collect the number of supported Non-GoB BF modes - SMO functions->>Non-RT RIC: 3 Retrieve collected information - SMO functions->>Near-RT RIC: 4 <> Request measurement data and UE context information for each Non-GoB BF mode - Near-RT RIC-->>SMO functions: 5 <> Collect measurement data and UE context information for each Non-GoB BF mode - SMO functions->>Application Server: 6 Collect enrichment information (e.g., UE location/mobility, etc.) - SMO functions->>Non-RT RIC: 7 Retrieve collected data - - Note left of SMO functions: AI/ML workflow - Non-RT RIC->>Near-RT RIC: 8 Associate enrichment information with measurements and configurations - Near-RT RIC-->>Non-RT RIC: 9 Train AI/ML models to select the best Non-GoB mode - Non-RT RIC->>SMO functions: 10 Request to deploy trained AI/ML models - SMO functions->>Near-RT RIC: 11 <> or <> Deploy AI/ML models - - Note left of SMO functions: Performance evaluation and optimization - SMO functions->>Near-RT RIC: 12 <> Request measurement data and UE context information - Near-RT RIC-->>SMO functions: 13 <> Collect measurement data and UE context information - SMO functions->>Application Server: 14 Collect enrichment information (e.g., UE location/mobility, etc.) - SMO functions->>Non-RT RIC: 15 Retrieve collected data - Non-RT RIC->>Near-RT RIC: 16 Performance monitoring & evaluation - Near-RT RIC-->>Non-RT RIC: 17 Re-train AI/ML models - Non-RT RIC->>SMO functions: 18 Request to deploy updated AI/ML models - SMO functions->>Near-RT RIC: 19 <> or <> Update AI/ML models - -``` - -Sequence diagram for AI/ML-assisted Non-GoB BF mode selection. Lifelines: SMO functions, Non-RT RIC, Near-RT RIC, O-DU, Application Server. The process is divided into three phases: Data Collection, AI/ML workflow, and Performance evaluation and optimization. The diagram shows 19 numbered interactions between these components. - -Figure 4.7.2.3.1-1: AI/ML-assisted Non-GoB BF mode selection - model training, deployment, and performance monitoring - -The context of the AI/ML-assisted Non-GoB BF mode selection – model inference is captured in table 4.7.2.3.1-2. - -Table 4.7.2.3.1-2: AI/ML-assisted Non-GoB BF mode selection – model inference - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To generate Non-GoB control/policy message. | | -| Actors and Roles | SMO, Non-RT RIC, Near-RT RIC, O-DU, external sources, e.g., application server | | -| Assumptions | - All relevant functions and components are instantiated. | | -| Pre-conditions |
  • - A1 interface is established between Non-RT RIC and Near-RT RIC to enable enrichment information transfer.
  • - E2 interface is established between Near-RT RIC and O-DU to enable Non-GoB BF mode selection via E2 control/policy message
| | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|--------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| | - O-DU supports Non-GoB BF. | | -| Begins when | Operator specified trigger condition or event is satisfied. | | -| Step 1 (O) | The Near-RT RIC queries available EI type identifiers. | | -| Step 2 (O) | The Non-RT RIC responds an array of identifiers of all available EI types. | | -| Step 3 (O) | The Near-RT RIC queries the EI type to support Non-GoB BF inference (e.g., UE mobility/location info). | | -| Step 4 (O) | The Non-RT RIC responds detailed information related to the queried EI type. | | -| Step 5 (O) | The Near-RT RIC creates an EI job. | | -| Step 6 (O) | The Non-RT RIC responds to the EI job creation request. | | -| Step 7 (O) | SMO collects enrichment information (e.g., UE mobility/location info) from external sources, e.g., application server. | | -| Step 8 (O) | Non-RT RIC retrieves collected enrichment information. | | -| Step 9 (O) | Non-RT RIC delivers collected enrichment information as EI job results to the Near-RT RIC via the A1 interface. | | -| Step 9 (M) | Near-RT RIC requests measurement data and UE context information (e.g., SRS periodicity) from O-DU via the E2 interface. | | -| Step 9 (M) | Near-RT RIC collects measurement data and UE context information (e.g., SRS periodicity) from O-DU via the E2 interface. | | -| Step 9 (M) | Near-RT RIC associates received enrichment information with collected measurement data and UE context information. | | -| Step 9 (M) | Near-RT RIC selects the best Non-GoB BF mode, e.g., by performing model inference. | | -| Step 9 (M) | Near-RT RIC generates Non-GoB control/policy message based on inferred Non-GoB BF mode selection. | | -| Step 9 (M) | Near-RT RIC sends Non-GoB control/policy message to O-DU via the E2 interface. | | -| Ends when | Operator specified trigger condition or event is satisfied. | | -| Exceptions | None identified. | | -| Post Conditions | Non-RT RIC monitors the performance of AI/ML-assisted Non-GoB BF mode selection in the Near-RT RIC. | | -| Traceability | REQ-Non-RT-RIC-FUN9,
REQ-A1-FUN3 | | - -@startuml - -skinparam ParticipantPadding 5 - -skinparam BoxPadding 10 - -skinparam defaultFontSize 12 - -autonumber - -Box “Service Management and Orchestration” #gold - -Participant “SMO Functions” as smo - -Participant “Non-RT RIC” as non - -End box - -Box “O-RAN” #lightpink - -Participant near as “Near-RT RIC” - -Participant ran as “O-DU” - -End box - -Box “External” #lightcyan - -Participant “Application Server” as app - -End box - -group Query EI identifiers - -non <- near : <> Query EI type identifiers - -non -> near : <> List of EI type identifiers - -end - -group Query EI type - -non <- near : <> Query EI type - -non -> near : <> Information for the EI type - -end - -group Create EI job - -non <- near : <> Create EI job - -non -> near : <> EI job creation response - -end - -app -> smo : Collect enrichment information (e.g., UE location/mobility, etc.) - -smo -> non : Retrieve collected data - -group Deliver EI job results - -non -> near : <> Deliver EI job results - -end - -group E2 control & Policy - -near -> ran : <> Request measurement data \n and UE context information - -ran -> near : <> Collect measurement data \n and UE context information - -near -> near: Associate enrichment information with \n collected measurements and configurations - -near -> near : Perform AI/ML model inference - -near -> near : Generate Non-GoB control/policy message - -near -> ran : <> Non-GoB control/policy message - -end - -@enduml - -The flow diagram of the AI/ML-assisted Non-GoB BF mode selection – inference is given in figure 4.7.2.3.1-2. - -![Sequence diagram showing the AI/ML-assisted Non-GoB BF mode selection - inference process. The diagram involves three main lifelines: Service Management and Orchestration (SMO Functions, Non-RT RIC), O-RAN (Near-RT RIC, O-DU), and External (Application Server). The process starts with the SMO Functions sending a 'Query EI identifiers' request to the Non-RT RIC, which responds with a list of identifiers. Next, the SMO Functions send a 'Query EI type' request, and the Non-RT RIC responds with information for the EI type. Then, the SMO Functions send a 'Create EI job' request, and the Non-RT RIC responds with a job creation response. The SMO Functions then send a 'Collect enrichment information' request to the O-DU, which responds with collected data. The SMO Functions then send a 'Deliver EI job results' request to the Non-RT RIC, which responds with the job results. Finally, the SMO Functions send an 'E2 control & Policy' request to the O-DU, which responds with a Non-GoB control/policy message. The O-DU then sends a 'Request measurement data and UE context information' request to the Near-RT RIC, which responds with 'Collect measurement data and UE context information'. The Near-RT RIC then performs 'Associate enrichment information with collected measurements and configurations', 'Perform AI/ML model inference', and 'Generate Non-GoB control/policy message', finally sending the 'Non-GoB control/policy message' to the O-DU.](96c8d8b0159c47a7478ada46d781060b_img.jpg) - -``` - -sequenceDiagram - participant SMO Functions - participant Non-RT RIC - participant Near-RT RIC - participant O-DU - participant Application Server - - Note left of SMO Functions: Service Management and Orchestration - Note right of O-DU: O-RAN - Note right of Application Server: External - - SMO Functions->>Non-RT RIC: Query EI identifiers - Note right of Non-RT RIC: Query EI identifiers - Non-RT RIC-->>SMO Functions: 1 <> Query EI type identifiers - Non-RT RIC-->>SMO Functions: 2 <> List of EI type identifiers - - SMO Functions->>Non-RT RIC: Query EI type - Note right of Non-RT RIC: Query EI type - Non-RT RIC-->>SMO Functions: 3 <> Query EI type - Non-RT RIC-->>SMO Functions: 4 <> Information for the EI type - - SMO Functions->>Non-RT RIC: Create EI job - Note right of Non-RT RIC: Create EI job - Non-RT RIC-->>SMO Functions: 5 <> Create EI job - Non-RT RIC-->>SMO Functions: 6 <> EI job creation response - - SMO Functions->>O-DU: 7 Collect enrichment information (e.g., UE location/mobility, etc.) - SMO Functions->>O-DU: 8 Retrieve collected data - - SMO Functions->>Non-RT RIC: Deliver EI job results - Note right of Non-RT RIC: Deliver EI job results - Non-RT RIC-->>SMO Functions: 9 <> Deliver EI job results - - Note left of O-DU: E2 control & Policy - O-DU->>Near-RT RIC: 10 <> Request measurement data and UE context information - Note right of Near-RT RIC: <> Request measurement data and UE context information - Near-RT RIC-->>O-DU: 11 <> Collect measurement data and UE context information - Note right of Near-RT RIC: <> Collect measurement data and UE context information - Near-RT RIC->>Near-RT RIC: 12 Associate enrichment information with collected measurements and configurations - Note right of Near-RT RIC: Associate enrichment information with collected measurements and configurations - Near-RT RIC->>Near-RT RIC: 13 Perform AI/ML model inference - Note right of Near-RT RIC: Perform AI/ML model inference - Near-RT RIC->>Near-RT RIC: 14 Generate Non-GoB control/policy message - Note right of Near-RT RIC: Generate Non-GoB control/policy message - Near-RT RIC-->>O-DU: 15 <> Non-GoB control/policy message - Note right of Near-RT RIC: <> Non-GoB control/policy message - -``` - -Sequence diagram showing the AI/ML-assisted Non-GoB BF mode selection - inference process. The diagram involves three main lifelines: Service Management and Orchestration (SMO Functions, Non-RT RIC), O-RAN (Near-RT RIC, O-DU), and External (Application Server). The process starts with the SMO Functions sending a 'Query EI identifiers' request to the Non-RT RIC, which responds with a list of identifiers. Next, the SMO Functions send a 'Query EI type' request, and the Non-RT RIC responds with information for the EI type. Then, the SMO Functions send a 'Create EI job' request, and the Non-RT RIC responds with a job creation response. The SMO Functions then send a 'Collect enrichment information' request to the O-DU, which responds with collected data. The SMO Functions then send a 'Deliver EI job results' request to the Non-RT RIC, which responds with the job results. Finally, the SMO Functions send an 'E2 control & Policy' request to the O-DU, which responds with a Non-GoB control/policy message. The O-DU then sends a 'Request measurement data and UE context information' request to the Near-RT RIC, which responds with 'Collect measurement data and UE context information'. The Near-RT RIC then performs 'Associate enrichment information with collected measurements and configurations', 'Perform AI/ML model inference', and 'Generate Non-GoB control/policy message', finally sending the 'Non-GoB control/policy message' to the O-DU. - -Figure 4.7.2.3.1-2: AI/ML-assisted Non-GoB BF mode selection - inference - -#### 4.7.2.4 Required data - -The specification of the data communicated over O1 is outside the scope of WG2. - -The following enrichment information from external sources (e.g., application server) are used in model training and inference: - -- UE location -- UE mobility -- Time granularity of the enrichment information reports (e.g., integer multiple of a second) - -Note that for model inference, above EI is sent from Non-RT RIC to Near-RT RIC via the A1 interface. - -#### 4.7.2.5 A1 enrichment information example - -In training phase, the retrieved enrichment information (e.g., UE mobility and location information) needs to be associated with collected per-UE L1/L2 measurement reporting (e.g., L1-RSRP and/or L1-SINR, etc.) and UE context information (e.g., UE-specific SRS periodicity) by the Non-RT RIC. In the inference phase, such data association is performed by the Near-RT RIC. Therefore, the EI delivered over the A1 interface should contain necessary UE identification to facilitate the data association at the Near-RT RIC. The Near-RT RIC shall be able to recognize the UE identification and be able to map it to the UE identification used over the E2 interface. - -For example, the A1 enrichment information contains the following information elements: - -- UE identifier -- Position of the UE -- Height of the UE -- Time stamp when the position and height was recorded - -### 4.7.3 MIMO optimization via MIMO DL Tx power optimization, MU-MIMO pairing, and MIMO mode selection - -This use case will provide the objective, solutions, and data requirements related to MIMO optimization based on three key sub-features involving downlink transmit power, MIMO pairing enhancement (user separability), and user MIMO mode selection (MU-MIMO or SU-MIMO) that are described in detail in the O-RAN.WG1.MMIMO-USE-CASES-TR-v01.00 [i.3]. The use-case leverages Non-RT RIC to train and host the relevant models and applications that rely on O1 interface services to intelligently optimize MIMO capacity and user experience. - -#### 4.7.3.1 Background and goal of the use case - -##### 4.7.3.1.1 MIMO downlink transmit power optimization - -For general downlink precoding, the downlink transmit power is usually evenly distributed across the UEs. However, depending on the UE separability and path loss deltas, this can result in good cell capacity at the expense of individual UE quality. This can be due to several issues such as cell edge UEs having general downlink SINR issues (even without MU-MIMO), poor UE separability between cell edge UEs, and poor uplink SINR resulting in degraded SRS which are a few example issues. The result of these issues can be manifested by observations of very poor individual UE SINRs (either downlink, uplink, or both) when running in a MU-MIMO mode. Therefore, although the capacity of the cell has been significantly increased, certain customer experiences can become unacceptable in this MU-MIMO mode. - -The solution to the problem described above is to simply provide observations of UE performance in the form of periodic histograms of UE channel quality as well as the overall cell capacity in order to compute an optimal solution via AI/ML with control of the downlink minimum required SINR threshold to achieve a minimal UE quality requirement that is set by the operator. The minimum required SINR is a threshold recommendation and thus doesn't require real time AI/ML adjustment of transmit power directly but rather leaves this to the scheduler to adjust and optimize consistent with its numerous other priorities and requirements. - -The value of this observability and adjustability allows the operator to optimize the trade-off between cell capacity and individual user/customer quality which is essential to provide the best customer experience. The trade-off, for example, can reduce a very high cell centre data rate (which would likely be unnoticeable for the user) to allow more power to be allocated to the cell edge user (who is noticing low tput and large latencies) to improve the cell edge data rate situation. - -##### 4.7.3.1.2 MU-MIMO pairing enhancement (user separability) - -Existing channel orthogonality between multiple users is critical to create user separability and allow for the opportunity to share radio frequency resources simultaneously. Failing this, residual interference will be too high to maintain adequate post pairing radio link signal quality levels required to sustain MU-MIMO mode assignments. With mobility there is an added demand to adjust beamforming weight assignments to not only maintain signal power levels at the user end (beam quality), but also to continuously limit the inter user interference experienced between users assigned with the same radio resource allocations. If these challenges are left unaddressed, a 5G massive MIMO deployment will fail to utilize the full capability of large antenna arrays powered by transceivers designed to transmit data channel signals towards a spatially confined direction. Further, the network will also fail to realize potential multiplexing gains as fewer radio resource blocks are shared between users within the same cell, reducing spectral efficiency. - -Another important aspect is the need to efficiently identify users with low demand for radio resources - sources of bursty traffic. An intelligent assessment of how best such users can be effectively paired, if at all, with other users, needs to be pre-determined by the RIC. In summary, this use case suggests various measurement objects that are recommended as input into the AI/ML analytics Apps to optimally determine the outputs required to optimize the MU-MIMO feature operation. - -The AI/ML assisted modelling and training output, along with the Non-RT RIC based enhancement/inference, will strive to deliver end goal solution selections and system configuration options that upon adoption within the respective domains where they reside, realize an optimization framework that maximizes the potential of a MU-MIMO feature. Capacity augmentation will be realized by successfully assigning MU-MIMO layers to a greater number of users simultaneously, more often, and more uniformly across the serving area of each gNB. - -##### 4.7.3.1.3 MIMO mode selection optimization (MU-MIMO vs SU-MIMO selection) - -A successful MU-MIMO operation involves the realization of as many orthogonal radio frequency channel links between multiple spatially separated users as possibly as supported by the implementation software at the digital domain. Key to such realization is the successful beamforming weight determination that enables not only the phase addition of multipath signals at the user receiver, but also the choice of precoding algorithms which limit the residual interference between the paired users. It can make sense for the scheduler to prioritize the assignment of radio resources to a MU-MIMO mode of operation during periods of congestion or when high latency requiring applications are supported (to free up other resources that can be assigned sooner). However, doing so at the expense of undesirably lower spectral efficiency on these assigned radio resources will reduce overall sector throughput levels and create poor user experience. It is important to find a means through the AI/ML agent to distinguish users and identify sectors where optimal operation means a greater assignment of SU-MIMO modes independently to users, especially those requiring higher throughput, using devices that are capable of supporting higher layer SU-MIMO count, and operating in an environment that sustains a greater channel rank. - -With increased loading massive MIMO systems will incur rising levels of interference on the uplink from connected users and on the downlink from the gNB. In addition to normal SINR measurements, the diagnosis of interference from all spatial directions uniformly (white spatial noise) versus specific directions (spatially correlated noise) will be of interest and will require MIMO modes (SU-MIMO vs MU-MIMO) to be properly selected for assignment on a user basis. Such - -implementation will optimize the per user and per cell throughputs, taking into consideration channel orthogonality conditions rank realizable, and per user effective bandwidth requirement. - -#### 4.7.3.2 Entities/resources involved in the use case - -- 1) SMO/Non-RT RIC: - - a) Retrieve relevant performance measurement data and RAN configurations from O-DU via the O1 interface. - - b) Perform model training and model deployment based on identified measurement data. - - c) Perform model performance monitoring and model re-training as required. - - d) Provide RAN configuration recommendations based on identified parameters to O-DU over O1 interface. - - e) Allow rApps to access the measurement data and to provide configuration recommendations via relevant R1 interface services. -- 2) O-DU: - - a) Send measurement data and RAN configurations to SMO/Non-RT RIC via the O1 interface. - - b) Support implementation of MIMO configuration parameters received from the SMO/Non-RT RIC via the O1 interface. - -#### 4.7.3.3 Solutions - -##### 4.7.3.3.1 MIMO optimization via DL SINR threshold, MU-MIMO pairing, and MIMO mode selection - -The context of the MIMO optimization via DL Tx power, pairing enhancement, and mode selection is captured in table 4.7.3.3.1-1. - -**Table 4.7.3.3.1-1: MIMO optimization via DL Tx power, pairing enhancement, and mode selection** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To train and deploy AI/ML models for MIMO optimization that given wireless conditions and RAN configuration information as input will generate configuration recommendations for DL SINR threshold, MU-MIMO user pairing, and MIMO mode selection. | | -| Actors and Roles | SMO, Non-RT RIC, O-DU | | -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - O1 interface connectivity is established.
| | -| Pre-conditions |
  • - O1 interface is established between SMO and O-DU to enable SMO/Non-RT RIC to collect performance measurement data and associated RAN configurations.
  • - O-DU supports the implementation of identified configuration parameters when configuration recommendation is received via O1 interface.
| | -| Begins when | Operator specified trigger condition or event is satisfied. | | -| Step 1 (M) | SMO requests performance measurement data and associated RAN configurations from O-DU for model training via the O1 interface. | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 2 (M) | SMO collects required performance measurement data and RAN configurations from O-DU via the O1 interface. | | -| Step 3 (M) | Non-RT RIC FW retrieves collected information. | | -| Step 4 (O) | Non-RT RIC performs model training/update. | | -| Step 5 (O) | Non-RT RIC deploys trained model for inference. | | -| Step 6 (M) | SMO requests performance measurement data from O-DU for performance monitoring via the O1 interface for rApp execution and optionally model inference. | | -| Step 7 (M) | SMO collects performance measurement data from O-DU for performance monitoring via the O1 interface for rApp execution and optionally model inference. | | -| Step 8 (M) | Non-RT RIC FW retrieves the collected data. | | -| Step 9 (M) | rApp accesses the collected data via R1 interface services. | | -| Step 10 (M) | rApp performance monitoring and evaluation and optional model inference. | | -| Step 11 (M) | rApp generates configuration recommendation. | | -| Step 12 (M) | Non-RT RIC FW retrieves the configuration recommendation via R1 interface services. | | -| Step 13 (M) | Non-RT RIC provides configuration output to SMO O1 termination. | | -| Step 14 (M) | SMO communicates MIMO configuration recommendation to O-DU via O1 interface. | | -| Ends when | Operator specified trigger condition or event is satisfied. | | -| Exceptions | None identified. | | -| Post Conditions | O-DU implements the configuration recommendations provided by MIMO optimization App. | | -| Traceability | REQ-Non-RT-RIC-FUN1, REQ-Non-RT-RIC-FUN2, REQ-Non-RT-RIC-FUN5, REQ-Non-RT-RIC-FUN8
REQ-R1-FUN9 | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -autonumber - -Box "Service Management and Orchestration" #gold - Participant "Collection & Control" as smo - -``` - -``` - -Participant "Non-RT RIC" as non -Participant "rApps" as rapp -End box - -Box "O-RAN" #lightpink - Participant ran as "O-DU" -End box - -group Data Collection - smo -> ran : <> Request measurement data and RAN configurations - ran -> smo : <> Collect measurement data and RAN configurations - smo -> non : Retrieve collected data and configuration -end - -group AI/ML workflow (O) - non --> non : Train/update AI/ML models for MIMO optimization - non --> non: Deploy AI/ML models -end - -group Performance evaluation and optimization - smo -> ran : <> Request measurement data and RAN configurations - ran -> smo : <> Collect measurement data and RAN configurations - smo -> non : Retrieve collected data and configuration - non -> rapp : <> Access collected data and configuration - rapp -> rapp : Performance monitoring & evaluation, \n optional model inference - rapp -> rapp : Generate MIMO configuration recommendation - rapp -> non : <> Provide MIMO configuration recommendation - non -> smo : Provide MIMO configuration recommendation - smo -> ran : <> MIMO configuration recommendation message -end - -@enduml - -``` - -The call flow for MIMO optimization use case is given in figure 4.7.3.3.1-1. - -![Sequence diagram for MIMO optimization use case showing interactions between Service Management and Orchestration (Collection & Control, Non-RT RIC, rApps) and O-RAN (O-DU).](90183a52275501da5a0fd5c63d837009_img.jpg) - -The diagram illustrates the call flow for the MIMO optimization use case across three main phases: Service Management and Orchestration, Data Collection, and Performance evaluation and optimization. The participants involved are Collection & Control, Non-RT RIC, rApps, and O-DU. - -``` - -sequenceDiagram - participant CC as Collection & Control - participant NRIC as Non-RT RIC - participant RA as rApps - participant OD as O-DU - - Note over CC, NRIC, RA: Service Management and Orchestration - Note over CC, NRIC, RA: Data Collection - Note over CC, NRIC, RA: AI/ML workflow (O) - Note over CC, NRIC, RA: Performance evaluation and optimization - - CC->>OD: 1 <> Request measurement data and RAN configurations - OD-->>CC: 2 <> Collect measurement data and RAN configurations - CC->>NRIC: 3 Retrieve collected data and configuration - - Note right of NRIC: AI/ML workflow (O) - NRIC->>NRIC: 4 Train/update AI/ML models for MIMO optimization - NRIC->>NRIC: 5 Deploy AI/ML models - - CC->>OD: 6 <> Request measurement data and RAN configurations - OD-->>CC: 7 <> Collect measurement data and RAN configurations - CC->>NRIC: 8 Retrieve collected data and configuration - NRIC->>RA: 9 <> Access collected data and configuration - RA->>RA: 10 Performance monitoring & evaluation, optional model inference - RA->>RA: 11 Generate MIMO configuration recommendation - RA->>NRIC: 12 <> Provide MIMO configuration recommendation - NRIC->>CC: 13 Provide MIMO configuration recommendation - CC->>OD: 14 <> MIMO configuration recommendation message - -``` - -Sequence diagram for MIMO optimization use case showing interactions between Service Management and Orchestration (Collection & Control, Non-RT RIC, rApps) and O-RAN (O-DU). - -Figure 4.7.3.3.1-1: Call flow for MIMO optimization use case - -#### 4.7.3.4 Required data - -The specification of the data communicated over O1 is outside the scope of WG2. - -There are no data that are relevant for the A1 interface. - -### 4.7.4 AI/ML-based initial access (SS Burst Set) configuration optimization - -#### 4.7.4.1 Background and goal of the use case - -3GPP NR based wireless cellular networks promises to provide leaner system design compared to its predecessors in a bid to improve spectral efficiency, power consumption performance and reduce interferences. Ultra-lean design aims to minimize “always on” reference signal transmissions in the downlink. Synchronization Signals Burst (SSB) sets are one of the high-overhead “always on” reference signals. In large scale NR networks with thousands of gNB/Transmission-Reception Points (TRPs) deployed, system configurations derived statically/manually aiming to accommodate worst case scenario which may arise only for a small window of time can impact on the followings: - -1. Increased overhead i.e., degraded utilization of time-frequency resources affecting Spectral Efficiency (SE). -2. Increased interferences among the cells. -3. Increased power consumptions in both network and UEs leading increased network CAPEX and reduced UE battery life respectively. - -In this context, this sub-use case proposes an AI/ML assisted optimization framework wherein AI/ML agent/engine running at Non-RT RIC can infer optimal SSB set configuration (i.e., number of SS blocks, SS beam directions and SS - -burst periodicity) based on Configuration (CM) parameters, Performance Measurements (PM), Key Performance Indicators (KPI), and measurement report traces obtained from the E2 nodes (O-CU-CP, O-CU-UP, O-DU, O-eNB) and O-RU. At high-level, the goal of the optimization problem is to minimize SS signal transmissions overhead i.e., determine the minimum number of SSB beams required, their directions and periodicity subject to KPI (integrity, mobility, etc.) targets. - -The overall scheme can be summarized as follows. Based on the history/trace/distribution of UE-specific beams (e.g., P2 beams), the AI/ML engine determines the minimum number of SSB beams, their directions and the maximum periodicity of the SS burst required to achieve KPI targets as per history/trace/distribution of UE-specific beams. Furthermore, in order to handle the lower probability occurrences in the statistical models e.g., UEs appearing in a completely new direction that has not been considered in the training data, the AI/ML engine (if required) updates the optimal set (e.g., adds beam directions that compliments the optimal directions, updates the SS burst periodicity etc.). Finally, the AI/ML engine shares the optimized SSB set configuration with gNB. - -#### 4.7.4.2 Entities/resources involved in the use case - -- 1) SMO & Non-RT RIC framework: - - a) Collect the necessary Configuration (CM) parameters, Performance Measurements (PM), Key Performance Indicators (KPI), and measurement report traces from the E2 nodes (O-CU-CP, O-CU-UP, O-DU, O-eNB) and O-RU. - - b) Allow the rApp to receive the CMs, PMs, KPIs measurement data (collected via O1) to perform the AI/ML model training and provide inference on the SSB set configuration parameters (number of SS blocks, SS beam directions and SS burst periodicity). - - c) Write/update the optimized SSB set configuration via O1 (to O-DU) interface. -- 2) rApps: - - a) Retrieve the necessary Configuration (CM) parameters, Performance Measurements (PM), Key Performance Indicators (KPI), and measurement report traces pertaining to the E2 nodes and O-RU from the SMO/Non-RT RIC framework via R1 for the purpose of optimizing SSB set configuration. - - b) Train AI/ML model to optimize the SSB set configurations. - - c) Modify/update the SSB set configurations, optimized by the inference engine of the rApp, and write the configuration output to the SMO/Non-RT RIC framework via R1. - - d) Monitor the performance of the respective cells. Upon KPI degradation, initiate rollback to the previous version of the AI/ML model, if any, and/or trigger the AI/ML model retraining. - - e) Execute the inference/control loop periodically or on an event-triggered based. -- 3) E2 nodes and O-RU: - - a) Report the desired performance measurements and KPIs, configuration parameters and CM changes, trace reports and measurements to the SMO via O1. - - b) Receive the optimized SSB set configurations from the SMO via O1 and apply the configuration on the O-DU which may further exercise the configuration update on the O-RU. - -NOTE: Both aggregated and disaggregated gNB architectures are supported. - -#### 4.7.4.3 Solutions - -The context of the creation and deployment of mMIMO SSB set optimization applications is captured in table 4.7.4.3-1. - -**Table 4.7.4.3-1: Creation and deployment of mMIMO SSB set optimization applications** - -| Use Case Stage | Evolution / Specification | <> | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Goal | SSB set optimization | | -| Actors and Roles | SMO/Non-RT RIC framework, SS burst set optimization rApp, E2 nodes, O-RU | | -| Assumptions | All relevant functions and components are instantiated.
O1 interface connectivity is established. | | -| Pre-conditions | SMO/Non-RT RIC framework is instantiated.
O1 interface is established between SMO and E2 nodes. | | -| Begins when | SSB optimization rApp with initial ML model is deployed. | | -| Step 1-3(M) | SMO/Non-RT RIC framework collects the necessary configurations, performance indicators, and measurement reports from E2 nodes. | | -| Step 4-5 (M) | rApp retrieves the necessary configurations, performance indicators, and measurement data from SMO/Non-RT RIC framework via R1 and trains AI/ML model for the purpose of optimizing SSB set configuration. | | -| Step 6 (M) | SMO/Non-RT RIC framework collects observation data from E2 nodes. | | -| Step 7-9 (M) | rApp retrieves the observation data from SMO/Non-RT RIC framework via R1, infers SSB set configuration, and shares the configuration to SMO/Non-RT RIC framework. | | -| Step 10-11 (M) | SMO/Non-RT RIC framework writes/updates SSB set configuration at E2 nodes. | | -| Step 12-18(M) | rApp continuously monitors KPIs in respective cells. In case of unsatisfactory performance, it initiates fallback and retrains/updates the respective AI/ML model(s). | | -| Ends when | On operator request for rApp to be disabled. | | -| Exceptions | None identified. | | -| Post Conditions | SSB set configuration is active. | | -| Traceability | REQ-Non-RT-RIC-FUN1, REQ-Non-RT-RIC-FUN2, REQ-Non-RT-RIC-FUN5, REQ-Non-RT-RIC-FUN6 | | - -The flow diagram of SSB set optimization is given in figure 4.7.4.3-1. - -![Sequence diagram for SSB set optimization showing interactions between Service Management and Orchestration (SMO, rApps) and O-RAN Nodes (E2-Nodes, O-RUs).](abeba89144744fac6a1571aa9f94889e_img.jpg) - -``` - -sequenceDiagram - box gold Service Management and Orchestration - participant SMO as SMO & Non-RT RIC FW - participant rApps as rApps - end - box lightpink O-RAN Nodes - participant E2Nodes as E2-Nodes(O-CUs & O-DUs) - participant ORUs as O-RUs - end - - rect rgb(255, 255, 255) - Note over SMO, ORUs: Data Collection and Pre-Processing - ORUs->>E2Nodes: 1 «FH» Observation, Measurement Data Collection - E2Nodes->>SMO: 2 «O1» Observation, Measurement Collection - SMO->>rApps: 3 Data Pre-Processing and AI/ML Training Data Generation - end - - rect rgb(255, 255, 255) - Note over SMO, rApps: AI/ML Engine/Agent Training - rApps->>SMO: 4 «R1» Data Retrieval - SMO->>rApps: 5 AI/ML Training - end - - rect rgb(255, 255, 255) - Note over SMO, ORUs: Model Deployment and Inference Generation - ORUs->>E2Nodes: 6 «O1» Observation, Measurement Collection - E2Nodes->>SMO: 7 «R1» Model Data - SMO->>rApps: 8 AI/ML Inference - rApps->>SMO: 9 «R1» Updated Optimal SSB Configs - SMO->>E2Nodes: 10 «O1» Updated SSB Configurations - E2Nodes->>ORUs: 11 «FH» Updated SSB Configurations - end - - rect rgb(255, 255, 255) - Note over SMO, ORUs: ML Agent Performance Monitoring - ORUs->>E2Nodes: 12 «FH» Data Collection - E2Nodes->>SMO: 13 «O1» KPIs, Measurement Report, Observations - SMO->>rApps: 14 «R1» Performance Data - rApps->>SMO: 15 Performance Evaluation & Fallback Config Decision - - opt if - rApps->>SMO: 16 «R1» Default/Fallback decision/SSB Configuration - SMO->>E2Nodes: 17 «O1» Default/Fallback SSB Configuration - E2Nodes->>rApps: 18 AI/ML Re-Training Trigger - end - end - -``` - -Sequence diagram for SSB set optimization showing interactions between Service Management and Orchestration (SMO, rApps) and O-RAN Nodes (E2-Nodes, O-RUs). - -**Figure 4.7.4.3-1: Flow diagram of SSB set optimization** - -``` - -@startuml - -skinparam defaultFontSize 12 - -Box "Service Management and Orchestration" #gold - Participant "SMO & Non-RT RIC FW" as SMO - Participant "rApps" as NRTRIC -End box - -Box "O-RAN Nodes" #lightpink - Participant "E2-Nodes (O-CUs & O-DUs)" as E2NODES - Participant "O-RUs" as ORUs -End box - -Autonumber - -group Data Collection and Pre-Processing - ORUs -> E2NODES : <> Observation, Measurement Data Collection - -``` - -``` -E2NODES -> SMO : <> Observation, Measurement Collection -SMO -> SMO : Data Pre-Processing and AI/ML Training Data Generation - -end - -group AI/ML Engine/Agent Training - SMO -> NRTRIC : <> Data Retrieval - NRTRIC -> NRTRIC: AI/ML Training -end - -group Model Deployment and Inference Generation - E2NODES -> SMO : <> Observation, Measurement Collection - SMO -> NRTRIC : <> Model Data - NRTRIC -> NRTRIC: AI/ML Inference - NRTRIC -> SMO : <> Updated Optimal SSB Configs - SMO -> E2NODES : <> Updated SSB Configurations - E2NODES -> ORUs : <> Updated SSB Configurations - -end - -group ML Agent Performance Monitoring - ORUs -> E2NODES : <> Data Collection - E2NODES -> SMO : <> KPIs, Measurement Report, Observations - SMO -> NRTRIC: <> Performance Data - NRTRIC -> NRTRIC: Performance Evaluation & Fallback Config Decision -group if - NRTRIC -> SMO : <> Default/Fallback decision/SSB Configuration - SMO -> E2NODES : <> Default/Fallback SSB Configuration - SMO -> NRTRIC : <> Model retraining and update request - NRTRIC -> NRTRIC: AI/ML Re-Training Trigger -end -end -@enduml -``` - -#### 4.7.4.4 Required data - -##### 4.7.4.4.1 Input data - -- 1) Supported SSB configurations per cell (as specified in 3GPP TS 38.331 [20], clause 6.3.2 and in 3GPP TS 28.541 [4], clause 4.3.5). -- 2) Key Performance Indicator (KPIs) such as integrity and cell/beam mobility KPIs, etc., for service level assurance (as specified in 3GPP TS 28.552 [5] and in 3GPP TS 28.554 [17]). -- 3) CSI-RS beam configuration and CSI-RS beam-specific UE measurement reporting from tracing of RRC messages (as specified in 3GPP TS 38.331 [20], clause 5.5.5.2). -- 4) PMs, such as the distribution of SS-RSRP, SS-RSRQ across of UEs measured per cell, number of RRC connected UEs (mean, max) measured per cell, intra-NRCell SSB beam switch measurement and received random access preambles on a per SSB/per cell basis (as specified in 3GPP TS 28.552 [5], clauses 5.1.1.22, 5.1.1.31, 5.1.1.4, 5.1.1.20 and 5.1.1.21). -- 5) Radio Link Failure (RLF) tracing across UEs across SSBs per cell (as specified in 3GPP TS 37.320 [19], clause 5.4.1.2, 3GPP TS 32.422 [18], clause 4.3 and in 3GPP TS 38.331 [20], clause 5.3.10). -- 6) DL/UL throughput per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.3). - -##### 4.7.4.4.2 Output data - -- 1) Inferred SSB set (number of SS blocks, SS beam directions and SS burst periodicity) configuration per cell (as specified in 3GPP TS 28.541 [4], clauses 4.3.39 and 4.3.40). - -## 4.8 Network energy saving - -This clause contains the set of energy saving use cases. - -### 4.8.1 Carrier and cell switch off/on - -#### 4.8.1.1 Background and goal of the use case - -Mobile networks often utilize multiple frequency layers (carriers) to cover the same service area. At low load, i.e., when the expected traffic volume is lower than a fixed threshold, ES can be achieved by switching off one or more carriers or entire cells without impairing the user experience. UEs previously served by the carrier or cell will be offloaded by the E2 node(s) to a new target carrier or cell prior to the switch off. - -However, the switch off/on decisions are not a trivial task. There are conflicting targets between system performance and energy savings. Other carriers / cells will have to serve the additional traffic and traffic is changing over time. E2 node(s) and O-RU(s) support several techniques effecting energy consumption which might also be load dependent. While energy savings for the switched off carrier/cell is maximized, the overall energy consumption of the network might even increase. - -Carrier and cell switch off/on control by the Non-RT or Near-RT RIC can consider overall network energy efficiency instead of local optimization. The switch off/on decision can optionally be made by an AI/ML model within the inference host, deployed at the Non-RT RIC to further improve decision making. Among others, the AI/ML models' functionality can include prediction of future traffic, user mobility, and resource usage and can also predict expected energy efficiency - -enhancements, resource usage, and network performance for different ES optimization states. Also, with addition of per-UE geographical location information such as trace record for immediate MDT measurement (as specified in 3GPP TS 32.423 [11], clause 4.34.1) and trace record for UE location information (as specified in 3GPP TS 32.423 [11], clause 4.34.2) as input data, the increased accuracy for UE location/trajectory prediction could be expected for more efficient solution so that it could prevent switched off cell(s) from being switched on even though meaningful number of UEs generating/receiving traffic do not exist in that cell(s). In that sense these collections could be conditionally activated during some cells being switched off and be deactivated once all cells switched on in terms of UE energy saving. Possible differences among collected types of geographical location information such as between MDT and LMF are expected to be absorbed and exposed to rApp(s) based on R1 data type definition. - -Before switching off/on carrier(s) or cell(s), there is a possibility the E2 node(s) and O-RU(s) of performing some preparation actions for off switching (e.g. check ongoing emergency calls and warning messages, to enable, disable, modify carrier aggregation and/or dual connectivity, to trigger HO traffic and UEs from cells/carriers to other cells or carriers, informing neighbour nodes via X2/Xn interface, etc.) as well as for on switching (e.g., cell probing, informing neighbour nodes via X2/Xn interface, etc.). This solution proposes a framework that allows the operator to flexibly configure carrier and cell switch off/on parameters in a cell or in a cluster of cells through O1 configuration formulated by rApp towards E2 node(s) and O-RU(s) or A1 policies formulated by rApp towards Near-RT RIC through SMO/Non-RT RIC framework assisted by machine learning (ML) techniques. - -#### 4.8.1.2 Entities/resources involved in the use case - -##### 1) SMO/Non-RT RIC framework function: - -- a) Collect the configurations, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) from E2 node(s) and trace records (e.g., per-UE measurement metrics and location information) through O1 Interface, for the purpose of decision making, optionally using training and inference of AI/ML models that assist such EE/ES functions. It is assumed that configurations, performance indicators and measurement reports collected from the O-DU contain the related information for the corresponding O-RU(s). -- b) Transfer collected data towards rApp. -- c) Signal updated configurations for EE/ES optimization towards E2 node(s) (O-CU) through O1 Interface. -- d) (Optionally) Retrain, update, configure EE/ES AI/ML models in Non-RT RIC. -- e) Provide A1 policies to Near-RT RIC via A1 interface based on the request from energy saving rApp in the case of A1 policy-based solution. -- f) Send enrichment information to the Near-RT RIC for calculation of coverage overlap via the A1 interface in the case of A1 policy-based solution. - -##### 2) rApps: - -###### a. Energy saving rApp - -- a) Collect the necessary configurations, performance indicators, and measurement reports from SMO/Non-RT RIC framework, for the purpose of training and execution of relevant AI/ML models. -- b) (Optionally) Retrain, update, configure EE/ES AI/ML model. -- c) Infer an optimized O1 configuration for EE/ES based on the data collected using R1 interface. -- d) Infer an optimized A1 policy for EE/ES based on the data collected using R1 interface in the case of A1 policy-based solution. - -###### b. EI producer rApp ( For A1-EI solution) - -- a) Support to produce enrichment information data requested by Near-RT RIC to ascertain overlapping carriers/cells and the coverage of those carriers/cells (e.g., geo location information of carriers/cells , coverage samples mapped geo location, etc.) - -- b) Send enrichment information to the Near-RT RIC through SMO/Non-RT RIC framework functions for calculation of coverage overlap via the A1 interface. -- 3) E2 nodes: -- a) Report cell configuration, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports, trace records such as per-UE measurement metrics and location information) to SMO via O1 interface. - - b) Report measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) to Near-RT RIC via E2 interface in the case of A1 policy-based solution. - - c) Perform actions required for EE/ES optimization. - - o e.g. check ongoing emergency calls and warning messages, perform some preparation actions for off switching (e.g., to enable, disable, modify carrier aggregation and/or dual connectivity, to trigger HO traffic and UEs from cells/carriers to other cells or carriers, informing neighbour nodes via X2/Xn interface etc.) as well as for on switching (e.g., cell probing, informing neighbour nodes via X2/Xn interface etc.) and make final decision on switch off/on and notify SMO via O1 interface about performed actions in case of O1 based solution or notify Near-RT RIC via E2 interface about performed actions in case of A1 policy-based solution. -- 4) O-RU: -- a) Report EC and EE related information via open FH M-plane interface to O-DU. - - b) Support actions required to perform EE/ES optimization. - - o Updated carrier configuration (i.e., activation, deactivation or sleep). -- 5) Near-RT RIC (For A1 policy-based solution): -- a) Collect measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) from E2 nodes. - - b) (Optionally) Receive EE/ES AI/ML model for deployment via O1 or O2 interface. - - c) Receive EE/ES related policies via A1 interface for consideration during optimization. - - d) Analyse the received data from E2 nodes and perform AI/ML model inference to determine EE/ES. Optimization (i.e., if carriers or cells are recommended to be switched off/on) considering the optimization targets/policies. - - e) Provide policies or required information to E2 node (O-CU) via E2 to trigger actions for EE/ES optimization. - - f) Receive enrichment information via the A1 interface. - - g) Associate enrichment information with collected measurements. - -#### 4.8.1.3 Solution - -##### 4.8.1.3.1 O1 interface based carrier and cell switch off/on optimization for energy saving - -In this solution, decision making, potentially including AI/ML model training and inference, is done at the Non-RT RIC. The context of the O1 interface based carrier and cell switch off/on optimization for energy saving is captured in table 4.8.1.3.1-1. - -**Table 4.8.1.3.1-1: O1 interface based carrier and cell switch off/on optimization for energy saving** - -| Use Case Stage | Evolution / Specification | <> | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Goal | Enable carrier and cell switch off/on energy saving functions in the network by means of configuration parameter change and actions controlled by Non-RT RIC and allow for AI/ML-based solutions. | | -| Actors and Roles | SMO/Non-RT RIC framework function: O1 termination. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | rApp: Carrier and cell switch off/on optimization.
E2 node(s), O-RU: Enforces carrier and cell switch off/on optimization configurations. | | -| Assumptions | O1 interface connectivity is established.
Open FH M-plane interface is established between E2 node(s) and O-RU.
Network is operational.
Non-RT RIC has knowledge about overlapping carriers/cells and the coverage of those carriers/cells (e.g., which carrier/cell is a coverage layer, and which is a capacity layer). | | -| Pre-conditions | Operator has set the targets for energy saving functions in the Non-RT RIC. | | -| Begins when | Operator enables the optimization rApp along with initial ML model for carrier and cell switch off/on energy saving functions and E2 node(s) and O-RU(s) become operational. | | -| Step 1 (M) | rApp requests to collect necessary configurations, performance indicators, and measurement data (e.g., cell load related information and traffic information, EE/EC measurement reports, cell level configurations, per-UE measurement metrics and location information) towards SMO/Non-RT RIC framework function over R1 interface. | | -| Step 2 (M) | SMO/Non-RT RIC framework function requests data collection towards E2 node(s) and O-RU(s) (via E2 node(s)) over O1 Interface. | | -| Step 3 (M) | E2 node(s) upon receiving request from SMO/Non-RT RIC framework function requests and collect necessary data from O-RU(s) over open FH M-plane interface. | | -| Step 4 (M) | E2 node(s) sends the configuration data, configured measurement data to SMO/Non-RT RIC framework function periodically or event based. | | -| Step 5 (M) | rApp collects the configuration data, collected measurement data for processing. | | -| Step 6 (O) | AI/ML models can be retrained either on Non-RT RIC framework or on rApp. If Non-RT RIC framework is hosting retraining, then rApp to select AI/ML model and initiate retraining on Non-RT RIC framework.
See NOTE 1. | | -| Step 7 (O) | Upon receiving retraining request from rApp. Non-RT RIC framework initiates AI/ML model retraining. | | -| Step 8 (O) | rApp monitors retrained AI/ML model and retrieves retrained AI/ML model.
See NOTE 2. | | -| Step 9 (O) | Upon receiving retrieval request from rApp, Non-RT RIC framework to transfer AI/ML model to rApp.
See NOTE 3. | | -| Step 10 (O) | If AI/ML model retraining is hosted by rApp then AI/ML model to be retrained on rApp itself. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 11 (O) | Once AI/ML model retraining is performed, AI/ML models are deployed and activated for inferencing for which rApp constantly monitors,
(i) performance and energy consumption of the E2 node(s)
(ii) energy consumption of O-RU(s).
rApp monitors performance and energy consumption for evaluation of necessary O1 configurations required to perform cell and carrier shutdown. | | -| Step 12 (M) | rApp generates O1 configurations to prepare and execute cell(s) and carrier(s) off/on SMO/Non-RT RIC framework function. | | -| Step 13 (M) | SMO/Non-RT RIC framework function instructs E2 node(s) via O1 interface to perform the received request(s) from the rApp. | | -| Step 14 (M) | O-RU(s) is informed about the updated O-RU(s) configuration via open FH M-plane interface by E2 node. O-RU(s) to notify E2 node(s) once O-RU(s) configuration is implemented. | | -| Step 15 (M) | E2 node(s) will inform SMO/Non-RT RIC framework function once cell or carrier switch off/on is completed. | | -| Step 16 (M) | SMO/Non-RT RIC framework inform rApp about completion of cell or carrier switch off/on over R1 interface. | | -| Step 17 (M) | rApp monitors energy saving objectives and if energy saving objectives are not achieved, it can decide to initiate fallback mechanism for example, reverting changes over O1 interface for carrier and cell switch off/on optimization, and/or AI/ML model update or retraining. | | -| Ends when | E2 node(s) becomes non-operational or when the operator disables the optimization functions or ML model for energy saving. | | -| Exceptions | TBD | | -| Post Conditions | rApp continues monitoring of energy saving function at E2 node(s) and O-RU.

E2 node(s) and O-RU(s) operate using the newly deployed parameters/models and state (off/on). | | - -NOTE 1: AI/ML procedures mentioned here can be subject to change based on future work on AI/ML workflow in WG2. - -NOTE 2: AI/ML model retrieval procedure over R1 interface is for illustration purpose, can be subject to change based on future work on AI/ML workflow in WG2. - -NOTE 3: AI/ML model transfer procedure over R1 interface is for illustration purpose, can be subject to change based on future work on AI/ML workflow in WG2. - -``` -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -Skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -``` - -``` - -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -Box "Service Management and Orchestration Framework" #gold -Box #lightgrey -Participant "Energy Saving\nrApp" as rAPP -End Box -Participant "SMO / Non-RT RIC\nFWK Function" as NRTF -End box -Box " RAN Nodes" #lightpink - Participant "E2-Node(s)" as E2NODES - Participant "O-RU(s) " as ORUs -End box -group Data Collection - rAPP-> NRTF : <> Data collection request - NRTF -> E2NODES : <> Data collection request - E2NODES <-> ORUs : <> Data collection request - E2NODES -> NRTF : <> Data Collection - NRTF -> rAPP : <> Data Collection -End -group Data Analysis /AIML Training and Inference -alt trainig on Non-RT RIC Fwk - rAPP -> NRTF : <> Select AI/ML Model and Inintiate re-training - NRTF -> NRTF : AI/ML Model re-training - rAPP -> NRTF : <> Retrive Re-trained AIML Model -Note right -rApp monitors re-trained -model parameters and decides -to retrieve AIML model -End note - NRTF -> rAPP : <> Transfer Re-trained AI/ML Model -Else trainig on rApp - rAPP -> rAPP : AI/ML Model re-training -end - rAPP -> rAPP : Deploy and activate re-trained\nAI/ML Model for inferencing -Note right - -``` - -Performance and Energy - -Consumption Monitoring - -(E2 Node(s) and O-RU(s)) - -and O1 configuration evaluation. - -End note - -end - -group Actor Decision Making - -rAPP -> NRTF : <> Configuration to prepare and execute \nfor carrier(s) and cell(s) switch off/on - -NRTF -> E2NODES : <> E2-Node(s) configurations for \ncarrier(s) and cell(s) switch off/on - -E2NODES <-> ORUs : <> Update O-RU(s) Configurations \nand notification of update - -E2NODES -> NRTF : <> Inform Completion of \ncarrier(s) and cell(s) switch off/on - -NRTF -> rAPP : <> Inform Completion of \ncarrier(s) and cell(s) switch off/on - -rAPP -> rAPP : Performance monitoring and \nevaluation of AI/ML model \n(with possible actions, \ne.g. fallback, re-training) - -end - -@enduml - -@startuml - -'https://plantuml.com/sequence-diagram - -!pragma teoz true - -Skin rose - -skinparam ParticipantPadding 5 - -skinparam BoxPadding 10 - -skinparam defaultFontSize 12 - -skinparam lifelineStrategy solid - -autonumber - -Box "Service Management and Orchestration Framework" #gold - -Box #lightgrey - -Participant "Energy Saving\nrApp" as rAPP - -End Box - -Participant "SMO / Non-RT RIC\nFWK Function" as NRTF - -End box - -Box " RAN Nodes" #lightpink - -Participant "E2-Node(s)" as E2NODES - -Participant "O-RU(s)" as ORUs - -End box - -group Data Collection - -``` - -rAPP-> NRTF : <> Data collection request -NRTF -> E2NODES : <> Data collection request -E2NODES <-> ORUs : <> Data collection request -E2NODES -> NRTF : <> Data Collection -NRTF -> rAPP : <> Data Collection - -``` - -End - -group Data Analysis /AIML Training and Inference - -alt trainig on Non-RT RIC Fwk - -``` - -rAPP -> NRTF : <> Select AI/ML Model and Inintiate re-training -NRTF -> NRTF : AI/ML Model re-training -rAPP -> NRTF : <> Retrive Re-trained AIML Model - -``` - -Note right - -rApp monitors re-trained -model parameters and decides -to retrieve AIML model - -End note - -``` - -NRTF -> rAPP : <> Transfer Re-trained AI/ML Model - -``` - -Else trainig on rApp - -``` - -rAPP -> rAPP : AI/ML Model re-training - -``` - -end - -``` - -rAPP -> rAPP : Deploy and activate re-trained\nAI/ML Model for inferencing - -``` - -Note right - -Performance and Energy -Consumption Monitoring -(E2 Node(s) and O-RU(s)) -and O1 configuration evaluation. - -End note - -end - -group Actor Decision Making - -``` - -rAPP -> NRTF : <> Configuration to prepare and execute \nfor carrier(s) and cell(s) switch off/on - -``` - -``` -NRTF -> E2NODES : <> E2-Node(s) configurations for\ncarrier(s) and cell(s) -switch off/on -E2NODES <-> ORUs : <> Update O-RU(s) Configurations \nand notification of update -E2NODES -> NRTF :<> Inform Completion of\ncarrier(s) and cell(s) switch off/on -NRTF -> rAPP : <> Inform Completion of\ncarrier(s) and cell(s) switch off/on -rAPP -> rAPP : Performance monitoring and\nevaluation of AI/ML model \n(with possible actions,\ne.g. fallback, re-training) -end - -@enduml -``` - -The flow diagram of O1 interface based carrier and cell switch off/on optimization for energy saving is given in figure 4.8.1.3.1-1. - -![Sequence diagram showing the flow of O1 interface based carrier and cell switch off/on optimization for energy saving. The diagram is divided into three main phases: Data Collection, Data Analysis /AI/ML Training and Inference, and Actor Decision Making. Lifelines include Energy Saving rApp, SMO / Non-RT RIC FWK Function, E2-Node(s), and O-RU(s).](6d697ce8828ba75fddee0a1b7767a7ca_img.jpg) - -The diagram illustrates the interaction between the Service Management and Orchestration Framework (SMO) and RAN Nodes (E2-Node(s) and O-RU(s)) for energy saving optimization. The sequence is as follows: - -- Data Collection:** - - 1 <> Data collection request: Energy Saving rApp to SMO / Non-RT RIC FWK Function. - - 2 <> Data collection request: SMO / Non-RT RIC FWK Function to E2-Node(s). - - 3 <> Data collection request: E2-Node(s) to O-RU(s). - - 4 <> Data Collection: O-RU(s) to E2-Node(s). - - 5 <> Data Collection: E2-Node(s) to SMO / Non-RT RIC FWK Function. -- Data Analysis /AI/ML Training and Inference:** - - alt [training on Non-RT RIC Fwk]: - - 6 <> Select AI/ML Model and Initiate re-training: Energy Saving rApp to SMO / Non-RT RIC FWK Function. - - 7 AI/ML Model re-training: SMO / Non-RT RIC FWK Function (self-call). - - 8 <> Retrieve Re-trained AI/ML Model: Energy Saving rApp to SMO / Non-RT RIC FWK Function. - - 9 <> Transfer Re-trained AI/ML Model: SMO / Non-RT RIC FWK Function to Energy Saving rApp. - - alt [training on rApp]: - - 10 AI/ML Model re-training: Energy Saving rApp (self-call). - - 11 Deploy and activate re-trained AI/ML Model for inferencing: Energy Saving rApp to SMO / Non-RT RIC FWK Function. - - Note: Performance and Energy Consumption Monitoring (E2 Node(s) and O-RU(s)) and O1 configuration evaluation. -- Actor Decision Making:** - - 12 <> Configuration to prepare and execute for carrier(s) and cell(s) switch off/on: Energy Saving rApp to SMO / Non-RT RIC FWK Function. - - 13 <> E2-Node(s) configurations for carrier(s) and cell(s) switch off/on: SMO / Non-RT RIC FWK Function to E2-Node(s). - - 14 <> Update O-RU(s) Configurations and notification of update: E2-Node(s) to O-RU(s). - - 15 <> Inform Completion of carrier(s) and cell(s) switch off/on: O-RU(s) to E2-Node(s). - - 16 <> Inform Completion of carrier(s) and cell(s) switch off/on: E2-Node(s) to SMO / Non-RT RIC FWK Function. - - 17 Performance monitoring and evaluation of AI/ML model (with possible actions, e.g. fallback, re-training): Energy Saving rApp (self-call). - -Sequence diagram showing the flow of O1 interface based carrier and cell switch off/on optimization for energy saving. The diagram is divided into three main phases: Data Collection, Data Analysis /AI/ML Training and Inference, and Actor Decision Making. Lifelines include Energy Saving rApp, SMO / Non-RT RIC FWK Function, E2-Node(s), and O-RU(s). - -Figure 4.8.1.3.1-1: Flow diagram of O1 interface based carrier and cell switch off/on optimization for energy saving - -##### 4.8.1.3.2 A1 policy based carrier and cell switch off/on optimization for energy saving - -In this solution, decision making, potentially using AI/ML model inference, is done at Near-RT RIC. While AI/ML model training might be hosted in Non-RT or Near-RT RIC, the description below is based on AI/ML model training in the Non-RT RIC. - -The context of the A1 policy based carrier and cell switch off/on optimization for energy saving is captured in table 4.8.1.3.2-1 - -**Table 4.8.1.3.2-1: A1 policy based carrier and cell switch off/on optimization for energy saving** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Enable A1 policy based carrier and cell switch off/on energy saving functions in the network by means of configuration parameter change and actions controlled by Near-RT RIC and allow for AI/ML-based solutions. | | -| Actors and Roles | SMO/Non-RT RIC framework function: A1 & O1 termination.
rApp: Carrier and cell switch off/on optimization.
E2 node(s), O-RU: Enforces carrier and cell switch off/on optimization configurations.
Near -RT RIC: Energy savings decision making function. | | -| Assumptions | O1 interface connectivity is established between SMO and E2 nodes.
R1 interface connectivity is established.
Open FH M-plane interface is established between E2 node(s) and O-RU.
E2 interface connectivity is established between E2 node and Near-RT RIC.
A1 interface is established between Non-RT RIC and Near-RT RIC.
Network is operational. | | -| Pre-conditions | Operator has set the targets for energy saving functions in the Non-RT RIC. | | -| Begins when | Operator enables the optimization rApp along with initial ML model for carrier and cell switch off/on energy saving functions and E2 node(s) and O-RU(s) become operational.
See NOTE 1. | | -| Step 1 (M) | rApp requests to collect necessary configurations, performance indicators, and measurement data (e.g., cell load related information and traffic information, EE/EC measurement reports, cell level configurations) towards SMO/Non-RT RIC framework function over R1 interface. | | -| Step 2 (M) | SMO/Non-RT RIC framework function requests data collection towards E2 node(s) and O-RU(s) (via E2 node(s)) over O1 Interface. | | -| Step 3 (M) | E2 node(s) upon receiving request from SMO/Non-RT RIC framework function requests and collect necessary data from O-RU(s) over open FH M-plane interface. | | -| Step 4 (M) | E2 node(s) sends the configuration data, configured measurement data to SMO/Non-RT RIC framework function periodically or event based. | | -| Step 5 (M) | rApp collects the configuration data, collected measurement data for processing. | | -| Step 6 (O) | AI/ML models can be retrained either on SMO/Non-RT RIC framework or on rApp.
If SMO/Non-RT RIC framework is hosting retraining, then rApp to select AI/ML model and initiate retraining on Non-RT RIC framework.
See NOTE 2. | | - -| Use Case Stage | Evolution / Specification | <> | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 7 (O) | Upon receiving retraining request from rApp. SMO/Non-RT RIC framework initiates AI/ML model retraining. | | -| Step 8 (O) | rApp monitors retrained AI/ML model before requesting to deploy towards Near-RT RIC. | | -| Step 9 (O) | rApp request SMO/Non-RT RIC framework to deploy AI/ML model in Near-RT RIC over R1 Interface.
See NOTE 3. | | -| Step 10 (O) | If AI/ML model retraining is hosted by rApp then AI/ML model to be retrained on rApp itself. | | -| Step 11 (O) | Once AI/ML model retraining is performed rApp to transfer AI/ML model to Non-RT RIC framework for deployment to Near-RT RIC. | | -| Step 12 (O) | Upon receiving request to deploy AI/ML model, Non-RT RIC framework to deploy AI/ML model in Near-RT RIC. | | -| Step 13 (M) | rApp to trigger EE/ES optimization through A1 policy to prepare and execute cell(s) and carrier(s) off/on. | | -| Step 14 (M) | Non-RT RIC framework receives policy from rApp and forwards it towards Near-RT RIC via A1 Interface. | | -| Step 15 (M) | Near-RT RIC provides A1 policy response to SMO/Non-RT RIC framework. | | -| Step 16 (M) | Non-RT RIC framework informs rApp about A1 policy feedback. | | -| Step 17 (M) | rApp monitors energy saving objectives as per A1 policy. | | -| Step 18 (M) | Near-RT RIC receives the policy from the Non-RT RIC over the A1 interface and inferences the EE/ES related AI/ML models and converts policy to specific E2 control or policy commands. | | -| Step 19 (O) | The Near-RT RIC creates an EI job to ascertain overlapping carriers/cells and the coverage of those carriers/cells (e.g., geo location information of carriers/cells, coverage samples mapped geo location, etc.). | | -| Step 20 (O) | SMO/Non-RT RIC framework functions requests EI rApp to deliver EI data as per details mentioned by Near-RT RIC. | | -| Step 21 (O) | EI rApp delivers requested EI data to SMO/Non-RT RIC framework functions. | | -| Step 22 (O) | Non-RT RIC delivers collected enrichment information as EI job results to the Near-RT RIC via the A1 interface. | | -| Step 23 (M) | Near-RT RIC requests data collection from E2 node(s) and O-RU(s) via E2 interface. | | -| Step 24 (M) | Upon receiving data collection request E2 nodes requests and collect measurement data. | | -| Step 25 (M) | Near-RT RIC collects measurement data from E2 node(s) and O-RU(s) via E2 interface. | | -| Step 26 (M) | Inferencing AI/ML model to evaluate & generate E2 control or policies for cell and carrier switch off/on. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 27 (M) | Near-RT RIC generates and sends cell and carrier switch off/on control/policy message based on inferred AI/ML model to E2 nodes and O-RU(s) via E2 interface. | | -| Step 28 (M) | O-RU(s) node to update configurations to execute cell or carrier switch off/on. | | -| Step 29 (M) | E2 nodes feedbacks E2 control/policy to Near-RT RIC. | | -| Step 30 (M) | Near-RT RIC to notify Non-RT RIC if any change in the state of policy. | | -| Step 31 (M) | SMO/Non-RT RIC framework forwards notification received from Near-RT RIC to rApp. | | -| Step 32 (O) | If energy saving objectives are not achieved rApp can decide to initiate fallback mechanism for example, updating or deleting A1 policy for carrier and cell switch off/on optimization. | | -| Step 33 (O) | SMO/Non-RT RIC framework send update or delete A1 policies to Near-RT RIC. | | -| Step 34 (O) | rApp can update or retrain AI/ML model based on evaluation of energy saving objectives. | | -| Step 35 (O) | SMO/Non-RT RIC framework send update or retrain AI/ML model to Near-RT RIC. | | -| Ends when | E2 node(s) becomes non-operational or when the operator disables the rApp or ML model for energy saving. | | -| Exceptions | N/A | | -| Post Conditions | rApp continues monitoring of energy saving function at E2 node(s) and O-RU.
E2 node(s) and O-RU(s) operate using the newly deployed parameters/models and state (off/on). | | - -NOTE 1: Operator can set policies through rApp or allow AI/ML model in rApp to infer policies. - -NOTE 2: AI/ML procedures mentioned here can be subject to change based on future work on AI/ML workflow in WG2. - -NOTE 3: AI/ML model deployment procedure over R1 interface is for illustration purpose, can be subject to change based on future work on AI/ML workflow in WG2. - -``` -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -Skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -Box "Service Management and Orchestration Framework" #gold -Box #lightgrey -``` - -``` - -Participant "Energy Saving\nrApp" as ESrAPP -Participant "Enrichment Information\nrApp" as EIrApp - -End Box - -Participant "SMO / Non-RT RIC\nFWK Function" as NRTF -End box - -Box " O-RAN Nodes" #lightpink - Participant "Near-RT RIC" as NeRT - Participant "E2-Node(s)" as E2NODES - Participant "O-RU(s) " as ORUs -End box - -group Data Collection - ESrAPP -> NRTF : <> Data collection request - NRTF -> E2NODES : <> Data collection request - E2NODES <-> ORUs : <> Data collection request - E2NODES -> NRTF : <> Data Collection - NRTF -> ESrAPP : <> Data Collection -End - -group Data Analysis /AI/ML Training and Inference -alt training on Non-RT RIC Fwk - ESrAPP -> NRTF : <> Select AI/ML Model and Initiate re-training - NRTF -> NRTF : AI/ML Model re-training - ESrAPP <-> NRTF : <> Monitoring AI/ML Model -Note over ESrAPP ,NRTF - ES rApp monitors re-trained model parameters and decides to deploy AI/ML model -End note - - ESrAPP -> NRTF : <> Request to Deploy AI/ML Model in Near-RT RIC -Else training on rApp - ESrAPP -> ESrAPP : AI/ML Model re-training - ESrAPP -> NRTF : <> Transfer AI/ML Model to deploy in Near-RT RIC -end - - NRTF -> NeRT : Deploy re-trained AI/ML Model -end - -group Actor Decision Making - ESrAPP -> NRTF : <> Create A1 Policy - -``` - -``` - -NRTF -> NeRT : <> Policy to prepare and execute \nfor carrier(s) and cell(s) -switch off/on - -NeRT -> NRTF : <> A1 Policy create Response - -NRTF -> ESrAPP : <> A1 Policy create Response - -ESrAPP -> ESrAPP : Monitor Energy saving objectives - -NeRT -> NeRT : Interpreting A1 Policy - -group collect EI Data - - NeRT -> NRTF: <> Create EI job - NRTF -> EIrApp : <> Request EI data - EIrApp -> NRTF : <> Deliver enrichment information - NRTF -> NeRT: <> Deliver EI job results - -end - - NeRT -> E2NODES : <> Measurement Data\nCollection Request - E2NODES <-> ORUs : <> Measurement Data Collection - E2NODES -> NeRT : <> Measurement Data Delivery - NeRT -> NeRT : AI/ML Model Inference\n to Evaluate E2 Control/Policy - NeRT -> E2NODES : <> E2 Control/Policy for\nCell and Carrier Switch off/on - E2NODES <-> ORUs : <> Update O-RU configurations \nand notification of update - E2NODES -> NeRT : <> E2 Control/Policy Feedback - -group Opt - - NeRT -> NRTF : <> Notify A1 Policy Status - NRTF -> ESrAPP : <> Notify A1 Policy Status - -end - -group Opt - - ESrAPP -> NRTF : <> Update or Delete A1 Policy - NRTF -> NeRT : <> Update or Delete Policy - ESrAPP -> NRTF : <> Update or Retrain AI/ML Model - NRTF -> NeRT : Update or Retrain AI/ML Model - -end - -end - -@enduml - -``` - -The flow diagram of A1 interface based carrier and cell switch off/on optimization for energy saving is given in figure 4.8.1.3.2-1. - -![Sequence diagram showing the flow of A1 interface based carrier and cell switch off/on optimization for energy saving. Lifelines include Energy Saving rApp, Enrichment Information rApp, SMO / Non-RT RIC FWK Function, Near-RT RIC, E2-Node(s), and O-RU(s). The process involves Data Collection, Data Analysis (AI/ML Training and Inference), and Actor Decision Making phases.](59e29b37c5e332b0be088cde8c4d217e_img.jpg) - -``` - -sequenceDiagram - participant ES as Energy Saving rApp - participant EI as Enrichment Information rApp - participant SMO as SMO / Non-RT RIC FWK Function - participant NRT as Near-RT RIC - participant E2 as E2-Node(s) - participant ORU as O-RU(s) - - Note left of ES: Service Management and Orchestration Framework - Note right of ORU: O-RAN Nodes - - Note left of ES: Data Collection - ES->>SMO: 1 <> Data collection request - SMO->>E2: 2 <> Data collection request - E2->>ORU: 3 <> Data collection request - ORU-->>E2: 4 <> Data Collection - E2-->>SMO: 5 <> Data Collection - - Note left of ES: Data Analysis AI/ML Training and Inference - alt training on Non-RT RIC Fwk - ES->>SMO: 6 <> Select AI/ML Model and Initiate re-training - SMO->>E2: 7 AI/ML Model re-training - ES->>SMO: 8 <> Monitoring AI/ML Model - Note right of ES: ES rApp monitors re-trained model parameters and decides to deploy AI/ML model - ES->>SMO: 9 <> Request to Deploy AI/ML Model in Near-RT RIC - else training on rApp - ES->>SMO: 10 AI/ML Model re-training - ES->>SMO: 11 <> Transfer AI/ML Model to deploy in Near-RT RIC - end - SMO->>NRT: 12 Deploy re-trained AI/ML Model - - Note left of ES: Actor Decision Making - ES->>SMO: 13 <> Create A1 Policy - SMO->>NRT: 14 <> Policy to prepare and execute for carrier(s) and cell(s) switch off/on - NRT->>SMO: 15 <> A1 Policy create Response - ES->>SMO: 16 <> A1 Policy create Response - ES->>SMO: 17 Monitor Energy saving objectives - - Note left of ES: collect EI Data - SMO->>NRT: 19 <> Create EI job - ES->>SMO: 20 <> Request EI data - SMO->>EI: 21 <> Deliver enrichment information - NRT->>ORU: 22 <> Deliver EI job results - - NRT->>E2: 23 <> Measurement Data Collection Request - E2->>ORU: 24 <> Measurement Data Collection - ORU-->>E2: 25 <> Measurement Data Delivery - SMO->>NRT: 26 AI/ML Model Inference to Evaluate E2 ControlPolicy - NRT->>E2: 27 <> E2 ControlPolicy for Cell and Carrier Switch off/on - E2->>ORU: 28 <> Update O-RU configurations and notification of update - E2-->>NRT: 29 <> E2 ControlPolicy Feedback - - opt - SMO->>NRT: 30 <> Notify A1 Policy Status - ES->>SMO: 31 <> Notify A1 Policy Status - end - - opt - ES->>SMO: 32 <> Update or Delete A1 Policy - SMO->>NRT: 33 <> Update or Delete Policy - ES->>SMO: 34 <> Update or Retrain AI/ML Model - SMO->>NRT: 35 Update or Retrain AI/ML Model - end - -``` - -Sequence diagram showing the flow of A1 interface based carrier and cell switch off/on optimization for energy saving. Lifelines include Energy Saving rApp, Enrichment Information rApp, SMO / Non-RT RIC FWK Function, Near-RT RIC, E2-Node(s), and O-RU(s). The process involves Data Collection, Data Analysis (AI/ML Training and Inference), and Actor Decision Making phases. - -Figure 4.8.1.3.2-1: Flow diagram of A1 interface based carrier and cell switch off/on optimization for energy saving - -NOTE: Above mentioned AI/ML procedures are illustration purpose and details are not defined in the present document. - -#### 4.8.1.4 Required data - -This sub-clause contains the input and output data of model training and inference for energy saving cell and carrier shutdown. - -##### 4.8.1.4.1 Input data - -The measurement input data are used in model training and inference. They can include the following measurements to monitor energy consumption and energy efficiency of E2 node(s) and O-RU(s): - -- a) DL PDCP SDU data volume per interface (data volume in DL delivered from O-CU-UP to O-DU, per PLMN, per QoS level, per slice, per interface (F1-U, Xn-U, X2-U)) (as specified in 3GPP TS 28.552 [5], clause 5.1.3.6.2.3) -- b) UL PDCP SDU data volume per interface (data volume in UL delivered to O-CU-UP from O-DU, per PLMN, per QoS level, per slice, per interface (F1-U, Xn-U, X2-U)) (as specified in 3GPP TS 28.552 [5], clause 5.1.3.6.2.4) -- c) RSRQ measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.31) -- d) RSRP measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.22) -- e) SINR measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.32) -- f) PNF energy consumption (as specified in 3GPP TS 28.552 [5], clause 5.1.1.19.3) -- g) Power consumed by physical network function & its components (as specified in 3GPP TS 28.552 [5], clause 5.1.1.19.2 and in MP [10], clauses B.1, B.5) -- h) Transmit power (as specified in MP [10], clauses B.1, B.2.1) -- i) M1 MDT measurement in trace record for immediate MDT measurements (as specified in 3GPP TS 32.423 [11], clause 4.34.1) -- j) UE location in trace record for UE location information (as specified in 3GPP TS 32.423 [11], clause 4.34.2) - -##### 4.8.1.4.2 Output data - -rApps to deliver energy saving & energy efficiency policies for cell/carrier switch off/on optimization through R1 interface. - -### 4.8.2 RF channel reconfiguration - -#### 4.8.2.1 Background and goal of the use case - -In mobile networks m-MIMO antennas are used for beamforming techniques to enhance cell capacity and throughput. To achieve beamforming, O-RU(s) need to concentrate the power amplifiers at the radome by combining radiating elements. At low load, i.e., when the expected traffic volume or number of connected users are lower than the configured threshold, ES can be achieved by reducing the power consumption of O-RU(s) by switching off certain Tx/Rx arrays. For example, 32 out of 64 Tx/Rx arrays of an O-RU(s) can be switched off in a digital m-MIMO architecture and correspondingly the number of spatial layers and SSBs can be reduced. The procedure (involvement of respective O-RAN interfaces) of the RF channel reconfiguration depends on the management architecture model (hybrid or hierarchical) and the deployment option. The switch off/on decision can be made by an AI/ML model within the inference host deployed at the Non-RT - -RIC. Among others the AI/ML models can include prediction of future traffic, user mobility, and resource usage and can also predict expected energy efficiency enhancements, resource usage, and network performance for different ES optimization states. - -This solution proposes a framework that allows the operator to flexibly configure RF channel reconfiguration parameters in a cell or in a cluster of cells through O1 configuration formulated by rApp towards E2 node(s) and O-RU(s) through SMO/Non-RT RIC or A1 policies formulated by rApp towards Near-RT RIC through SMO/Non-RT RIC framework assisted by Machine Learning (ML) techniques. - -#### 4.8.2.2 Entities/resources involved in the use case - -- 1) SMO/Non-RT RIC framework function: - - a) Collect the configurations, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) from E2 node(s), for the purpose of decision making, optionally using training and inference of AI/ML models that assist such EE/ES functions. - - b) Transfer collected data towards rApp. It is assumed that configurations, performance indicators and measurement reports collected from the O-DU contain the related information for the corresponding O-RU(s). - - c) Signal updated configurations for EE/ES optimization towards E2 node(s) (O-CU) through O1 interface. - - d) (Optionally) Retrain, update, configure EE/ES AI/ML models in Non-RT RIC. - - e) Provide A1 policies to Near-RT RIC via A1 interface based on the request from energy saving rApp in the case of A1 policy-based solution. -- 2) rApps: - - a) Collect the necessary configurations, performance indicators, and measurement reports from SMO/Non-RT RIC framework function, for the purpose of training and execution of relevant AI/ML models. - - b) (Optionally) Retrain, update, configure EE/ES AI/ML model. - - c) Infer an optimized RF channel configuration for EE/ES based on the data collected using R1 interface. - - d) Provide optimized A1 policy for EE/ES based on the data collected using R1 interface in the case of A1 policy-based solution. -- 3) E2 nodes: - - a) Report cell configuration, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) to SMO via O1 interface. - - b) Report measurement reports to Near-RT RIC via E2 interface in the case of A1 policy-based solution. - - c) Perform actions required to perform RF channel reconfiguration (i.e., O-RU Tx/Rx array selection, modification of the number of SSB beams, modification of the O-RU antenna transmit power, modification of the number of SU/MU MIMO data layers or spatial streams) as part of EE/ES optimization. -- 4) O-RU: - - a) Report EC and EE related information via open FH M-plane interface to O-DU. - - b) Perform actions required to be performed due to RF channel reconfiguration (i.e., O-RU Tx/Rx array selection, modification of the number of SSB beams, modification of the O-RU antenna transmit power, modification of the number of SU/MU MIMO spatial streams or data layers) as part of EE/ES optimization. -- 5) Near-RT RIC (For A1 policy-based solution): - - a) Collect measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) from E2 nodes. - - b) (Optionally) Receive EE/ES AI/ML model for deployment via O1 or O2 interface. - - c) Receive EE/ES related policies via A1 interface for consideration during optimization. - -- d) Analyse the received data from E2 nodes and perform AI/ML model inference to determine EE/ES. Optimization (i.e., if carriers or cells are recommended to be switched off/on) considering the optimization targets/policies. -- e) Provide policies or required information to E2 node via E2 to trigger actions for EE/ES optimization. - -#### 4.8.2.3 Solution - -##### 4.8.2.3.1 O1 policy based RF channel reconfiguration optimization for energy saving - -In this solution, decision making, potentially including AI/ML model training and inference, is done at the Non-RT RIC. - -The context of the O1 interface based RF channel reconfiguration optimization for energy saving is captured in table 4.8.2.3.1-1. - -**Table 4.8.2.3.1-1: O1 interface based RF channel reconfiguration optimization for energy saving** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Enable RF channel reconfiguration energy saving functions in the network by means of configuration parameter change and actions controlled by Non-RT RIC and allow for AI/ML-based solutions. | | -| Actors and Roles | SMO/Non-RT RIC framework function: Termination point for O1 interface.
E2 node(s), O-RU(s): Enforces optimized RF channel configuration.
rApp: RF channel reconfiguration optimization. | | -| Assumptions | O1 interface connectivity is established.
Open FH M-plane interface is established between E2 node(s) and O-RU.
Network is operational. | | -| Pre-conditions | Operator has set the targets for energy saving functions in the Non-RT RIC. | | -| Begins when | Operator enables the optimization rApp along with initial ML model for RF channel reconfiguration saving functions and E2 node(s) and O-RU(s) become operational. | | -| Step 1 (M) | rApp requests to collect necessary configurations, performance indicators, and measurement data towards SMO/Non-RT RIC framework function over R1 interface. | | -| Step 2 (M) | SMO/Non-RT RIC framework function requests data collection towards E2 node(s) and O-RU(s) (via E2 node(s)) over O1 interface. | | -| Step 3 (M) | E2 node(s) upon receiving request from SMO/Non-RT RIC framework function requests and collect necessary data from O-RU(s) over open FH M-plane interface. | | -| Step 4 (M) | E2 node(s) send the configuration data, configured measurement data to SMO/Non-RT RIC framework periodically or event based. | | -| Step 5 (M) | rApp collects the configuration data, collected measurement data for processing. | | - -| Use Case Stage | Evolution / Specification | <> | -|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 6 (O) | AI/ML models can be retrained either on Non-RT RIC framework or on rApp. If Non-RT RIC framework is hosting retraining, then rApp to select AI/ML model and initiate retraining on Non-RT RIC framework.

See NOTE 1. | | -| Step 7 (O) | Upon receiving retraining request from rApp. Non-RT RIC framework initiates AI/ML model retraining. | | -| Step 8 (O) | rApp monitors retrained AI/ML model and retrieves retrained AI/ML model.

See NOTE 2. | | -| Step 9 (O) | Upon receiving retrieval request from rApp, Non-RT RIC framework to transfer AI/ML model to rApp.

See NOTE 3. | | -| Step 10 (O) | If AI/ML model retraining is hosted by rApp then AI/ML model to be retrained on rApp itself. | | -| Step 11 (O) | Once AI/ML model retraining is performed, AI/ML models are deployed and activated for inferencing for which rApp constantly monitors performance and energy consumption to evaluate necessary O1 configurations to perform RF channel reconfiguration. | | -| Step 12 (M) | rApp to request the SMO/Non-RT RIC framework to configure E2 node(s) to prepare and execute RF channel reconfigurations as below,
  • i. O-RU Tx/Rx array selection.
  • ii. Modify the number of SU/MU MIMO spatial streams or data layers.
  • iii. Modify the number of SSB beams.
  • iv. Modify O-RU antenna transmit power.
| | -| Step 13 (M) | SMO/Non-RT RIC framework function to requests to configure E2 node(s) for RF channel reconfiguration through O1 interface. | | -| Step 14 (M) | O-RU(s) is informed about the updated O-RU configuration via open FH M-plane interface by E2 node(s). O-RU(s) to inform E2 node(s) once O-RU(s) configuration is implemented. | | -| Step 15 (M) | E2 node(s) will inform SMO/Non-RT RIC framework function once RF channel reconfiguration is completed. | | -| Step 16 (M) | SMO/Non-RT RIC framework function to inform rApp about completion of RF channel reconfiguration over R1 interface. | | -| Step 17 (M) | rApp monitors energy saving objectives. If energy saving objectives are not achieved, it can decide to initiate fallback mechanism for example, reverting changes over O1 interface for RF channel reconfigurations, and/or AI/ML model update or retraining. | | -| Ends when | E2 node(s) becomes non-operational or when the operator disables the optimization functions or ML model for energy saving. | | -| Exceptions | TBD. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Post Conditions |

rApp continues monitoring of energy saving function at E2 node(s) and O-RU(s).

E2 node(s) and O-RU(s) operate using the newly deployed parameters/models and state.

| | - -NOTE 1: AI/ML procedures mentioned here can be subject to change based on future work on AI/ML workflow in WG2. - -NOTE 2: AI/ML model retrieval procedure over R1 interface is for illustration purpose, can be subject to change based on future work on AI/ML workflow in WG2. - -NOTE 3: AI/ML model transfer procedure over R1 interface is for illustration purpose, can be subject to change based on future work on AI/ML workflow in WG2. - -``` - -@startuml -'https://plantuml.com/sequence-diagram - -!pragma teoz true - -Skin rose - -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber - -Box "Service Management and Orchestration Framework" #gold -Box #lightgrey -Participant "Energy Saving\nrApp" as rAPP -End box - -Participant " SMO / Non-RT RIC\nFWK Function " as NRTF -End box - -Box "RAN Nodes" #lightpink - Participant "E2-Node(s)" as E2NODES - Participant "O-RU(s)" as ORUs -End box - -group Data Collection - rAPP-> NRTF : <> Data collection request - NRTF -> E2NODES : <> Data collection request - -``` - -``` - -E2NODES <-> ORUs : <> Data collection request -E2NODES -> NRTF : <> Data Collection -NRTF -> rAPP : <> Data Collection - -End - -group Data Analysis /AIML Training and Inference -alt trainig on Non-RT RIC Fwk - rAPP -> NRTF : <> Select AI/ML Model and Inintiate re-training - NRTF -> NRTF : AI/ML Model re-training - rAPP -> NRTF : <> Retrive Re-trained AIML Model -Note right - rApp monitors re-trained - model parameters and decides - to retrieve AIML model -End note - NRTF -> rAPP : <> Transfer Re-trained AI/ML Model -Else trainig on rApp - rAPP -> rAPP : AI/ML Model re-training -end - - rAPP -> rAPP : Deploy and activate re-trained\nAI/ML Model for inferencing -Note Right - Performance and Energy - Consumption Monitoring - (E2 Node(s) and O-RU(s)) - and O1 configuration evaluation. -End note -end - -group Actor Decision Making - rAPP -> NRTF : <> Configuration to prepare and execute \nfor RF Channel - Reconfiguration - NRTF <-> E2NODES : <> E2-Node configurations for\nRF Channel Reconfiguration - E2NODES <-> ORUs : <> Update O-RU Configurations \nnand notification of update - E2NODES -> NRTF : <> Inform Completion of\nnRF Channel Reconfiguration - NRTF -> rAPP : <> Inform Completion of RF Channel Reconfiguration - -``` - -``` -rAPP -> rAPP : Performance monitoring and evaluation of AI/ML model \n(with possible actions, \ne.g. fallback, re-training) - -end -``` - -``` -@enduml -``` - -The flow diagram of O1 interface based RF channel reconfiguration optimization for energy saving is shown in figure 4.8.2.3.1-1. - -![Sequence diagram showing the flow of O1 interface based RF channel reconfiguration optimization for energy saving. The diagram involves four lifelines: Energy Saving rApp, SMO / Non-RT RIC FWK Function, E2-Node(s), and O-RU(s). The process is divided into three main phases: Data Collection, Data Analysis /AI/ML Training and Inference, and Actor Decision Making. The sequence of messages includes data collection requests, data collection responses, model selection and re-training, model retrieval, model transfer, model deployment, configuration preparation, E2-Node configuration updates, O-RU configuration updates, and completion notifications.](aa39f51ba214496042ee3e2ce4ecee80_img.jpg) - -``` -sequenceDiagram - participant ES as Energy Saving rApp - participant SMO as SMO / Non-RT RIC FWK Function - participant E2 as E2-Node(s) - participant ORU as O-RU(s) - - Note left of ES: Data Collection - ES->>SMO: 1 <> Data collection request - SMO->>E2: 2 <> Data collection request - E2->>ORU: 3 <> Data collection request - ORU-->>E2: 4 <> Data Collection - E2-->>SMO: 5 <> Data Collection - - Note left of ES: Data Analysis /AI/ML Training and Inference - alt training on Non-RT RIC Fwk - ES->>SMO: 6 <> Select AI/ML Model and Initiate re-training - SMO->>SMO: 7 AI/ML Model re-training - Note right of SMO: rApp monitors re-trained model parameters and decides to retrieve AI/ML model - ES->>SMO: 8 <> Retrieve Re-trained AI/ML Model - SMO-->>ES: 9 <> Transfer Re-trained AI/ML Model - else training on rApp - ES->>ES: 10 AI/ML Model re-training - end - ES->>SMO: 11 Deploy and activate re-trained AI/ML Model for inferencing - Note right of SMO: Performance and Energy Consumption Monitoring (E2 Node(s) and O-RU(s)) and O1 configuration evaluation. - - Note left of ES: Actor Decision Making - ES->>SMO: 12 <> Configuration to prepare and execute for RF Channel Reconfiguration - SMO->>E2: 13 <> E2-Node configurations for RF Channel Reconfiguration - E2->>ORU: 14 <> Update O-RU Configurations and notification of update - ORU-->>E2: 15 <> Inform Completion of RF Channel Reconfiguration - E2-->>SMO: 16 <> Inform Completion of RF Channel Reconfiguration - ES->>ES: 17 Performance monitoring and evaluation of AI/ML model (with possible actions, e.g. fallback, re-training) -``` - -Sequence diagram showing the flow of O1 interface based RF channel reconfiguration optimization for energy saving. The diagram involves four lifelines: Energy Saving rApp, SMO / Non-RT RIC FWK Function, E2-Node(s), and O-RU(s). The process is divided into three main phases: Data Collection, Data Analysis /AI/ML Training and Inference, and Actor Decision Making. The sequence of messages includes data collection requests, data collection responses, model selection and re-training, model retrieval, model transfer, model deployment, configuration preparation, E2-Node configuration updates, O-RU configuration updates, and completion notifications. - -**Figure 4.8.2.3.1-1: Flow diagram of O1 interface based RF channel reconfiguration optimization for energy saving** - -##### 4.8.2.3.2 A1 policy based RF channel reconfiguration optimization for energy saving - -In this solution, decision making, potentially using AI/ML model inference, is done at Near-RT RIC. While AI/ML model training might be hosted in Non-RT or Near-RT RIC, the description below is based on AI/ML model inferencing in the Near-RT RIC. - -The context of the A1 policy based optimization for energy saving is captured in table 4.8.2.3.2-1. - -**Table 4.8.2.3.2-1: A1 policy based optimization for energy saving** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Enable A1 policy based RF channel reconfiguration energy saving functions in the network by means of configuration parameter change and actions controlled by Near-RT RIC and allow for AI/ML-based solutions. | | -| Actors and Roles | SMO/Non-RT RIC framework function: A1 & O1 termination
rApp: RF channel reconfiguration optimization
E2 node(s), O-RU: Enforces RF channel reconfiguration
Near-RT RIC: RF channel reconfiguration energy savings decision making function | | -| Assumptions | O1 interface connectivity is established between SMO and E2 nodes.
R1 interface connectivity is established.
Open FH M-plane interface is established between O-DU and O-RU.
E2 interface connectivity is established between E2 nodes and Near-RT RIC.
A1 interface is established between Non-RT RIC and Near-RT RIC.
Network is operational. | | -| Pre-conditions | Operator has set the targets for energy saving functions in the Non-RT RIC. | | -| Begins when | Operator enables the optimization rApp along with initial ML model for RF channel reconfiguration energy saving functions and E2 node(s) and O-RU(s) become operational.
See NOTE. | | -| Step 1 (M) | rApp requests for necessary configurations, performance indicators, and measurement data towards SMO/Non-RT RIC framework function over R1 interface.
Configurations may contain data related to node capability such as O-RU RF channel configuration/TRx control capability information which rApp needs to know before formulating A1 policies for ASM optimization. | | -| Step 2 (M) | SMO/Non-RT RIC framework function requests data collection towards E2 node(s) and O-RU(s) (via E2 node(s)) over O1 Interface. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 3 (M) | E2 node(s) upon receiving request from SMO/Non-RT RIC framework function requests and collect necessary data from O-RU(s) over open FH M-plane interface. | | -| Step 4 (M) | E2 node(s) sends the configuration data, configured measurement data to SMO/Non-RT RIC framework function periodically or event based. | | -| Step 5 (M) | rApp collects the configuration data, collected measurement data for processing. | | -| Step 6 (M) | rApp to trigger EE/ES optimization through A1 policy to prepare and execute RF channel configuration/Trx control. | | -| Step 7 (M) | Non-RT RIC framework receives policy from rApp and forwards it towards Near-RT RIC via A1 interface. | | -| Step 8 (M) | Near-RT RIC provides A1 policy response to SMO/Non-RT RIC framework. | | -| Step 9 (M) | Non-RT RIC framework informs rApp about A1 policy feedback. | | -| Step 10 (M) | rApp monitors energy saving objectives as per A1 policy. | | -| Step 11 (M) | The Near-RT RIC receives the policy from the Non-RT RIC over the A1 interface. It then interprets the policy to determine the required data collection and E2 control/policies. | | -| Step 12 (M) | Inferencing AI/ML model to evaluate & generate E2 control or policies for RF channel configuration/Trx Control optimization. | | -| Step 13 (M) | Near-RT RIC to notify Non-RT RIC if any change in the state of policy. | | -| Step 14 (M) | SMO/Non-RT RIC framework forwards notification received from Near-RT RIC to rApp. | | -| Step 15 (O) | If energy saving objectives are not achieved rApp may decide to initiate fallback mechanism for example, updating or deleting A1 policy for RF channel configuration/Trx control optimization. | | -| Step 16 (O) | SMO/Non-RT RIC framework send update or delete A1 policies to Near-RT RIC. | | -| Step 17 (O) | rApp can update or retrain AI/ML model based on evaluation of energy saving objectives. | | -| Step 18 (O) | SMO/Non-RT RIC framework send update or retrained AI/ML model to Near-RT RIC. | | -| Ends when | E2 node(s) becomes non-operational. | | -| Exceptions | N/A | | -| Post Conditions | rApp continues monitoring of energy saving function at E2 node(s) and O-RU.

E2 node(s) and O-RU(s) operate using the newly deployed parameters/models and state (off/on). | | - -NOTE: Operator can set policies through rApp or allow AI/ML model in rApp to infer policies. - -``` -@startuml -``` - -``` -'https://plantuml.com/sequence-diagram -``` - -``` -!pragma teoz true -``` - -Skin rose - -skinparam ParticipantPadding 5 - -skinparam BoxPadding 10 - -skinparam defaultFontSize 12 - -skinparam lifelineStrategy solid - -autonumber - -Box "Service Management and Orchestration Framework" #gold - -Box #lightgrey - -Participant "Energy Saving\nrApp" as ESrAPP - -End Box - -Participant "SMO / Non-RT RIC\nFWK Function" as NRTF - -End box - -Box " O-RAN Nodes" #lightpink - -Participant "Near-RT RIC" as NeRT - -Participant "E2-Node(s)" as E2NODES - -Participant "O-RU(s) " as ORUs - -End box - -group Data Collection - -ESrAPP -> NRTF : <> Data collection request - -NRTF -> E2NODES : <> Data collection request - -E2NODES <-> ORUs : <> Data collection request - -E2NODES -> NRTF : <> Data Collection - -NRTF -> ESrAPP : <> Data Collection - -End - -group Data Analysis /AI/ML Model Selection and Training - -Note over ESrAPP , NeRT - -rApp/Non-RT RIC performs AIML Model Selection ,re-training and decides -to deploy Model in Near-RT RIC or provide AIML Model access details. - -End note - -end - -group Actor Decision Making - -ESrAPP -> NRTF : <> Create AI Policy - -NRTF -> NeRT : <> Policy to prepare and execute \nfor RF Channel -Configuration/Trx Control - -NeRT -> NRTF : <> AI Policy create Response - -NRTF -> ESrAPP : <> AI Policy create Response - -``` - -ESrAPP -> ESrAPP : Monitor Energy saving objectives - -NeRT -> NeRT : Interpreting AI Policy - -group E2 Data Collection - -Note over NeRT , ORUs - -Near-RT RIC to trigger E2 data collection from different E2 Nodes. - -In the case of O-DU, data collected is expected to include the data from the related O- -RU(s) - -End note - -end - -NeRT -> NeRT : AI/ML Model Inference\n to Evaluate E2 Control/Policy - -group E2 Control /Policy - -Note over NeRT , ORUs - -Near-RT RIC to trigger RF Channel Configuration/Trx Control - -E2 Control /Policy towards E2 Nodes and O-RU via O-DU - -End note - -end - -group Opt - -NeRT -> NRTF : <> Notify AI Policy Status - -NRTF -> ESrAPP : <> Notify AI Policy Status - -end - -group Opt - -ESrAPP -> NRTF : <> Update or Delete AI Policy - -NRTF -> NeRT : <> Update or Delete Policy - -ESrAPP -> NRTF : <> Update AI/ML Model - -NRTF -> NeRT : Update AI/ML Model - -end - -end - -@enduml - -``` - -``` - -@startuml - -'https://plantuml.com/sequence-diagram - -!pragma teoz true - -Skin rose - -skinparam ParticipantPadding 5 - -skinparam BoxPadding 10 - -skinparam defaultFontSize 12 - -``` - -``` - -skinparam lifelineStrategy solid -autonumber -Box "Service Management and Orchestration Framework" #gold -Box #lightgrey -Participant "Energy Saving\nrApp" as ESrAPP -End Box -Participant "SMO / Non-RT RIC\nFWK Function" as NRTF -End box -Box " O-RAN Nodes" #lightpink - Participant "Near-RT RIC" as NeRT - Participant "E2-Node(s)" as E2NODES - Participant "O-RU(s) " as ORUs -End box -group Data Collection - ESrAPP -> NRTF : <> Data collection request - NRTF -> E2NODES : <> Data collection request - E2NODES <-> ORUs : <> Data collection request - E2NODES -> NRTF : <> Data Collection - NRTF -> ESrAPP : <> Data Collection -End -group Data Analysis /AI/ML Model Selection and Training -Note over ESrAPP , NeRT -rApp/Non-RT RIC performs AIML Model Selection ,re-training and decides -to deploy Model in Near-RT RIC or provide AIML Model access details. -End note -end -group Actor Decision Making - ESrAPP -> NRTF : <> Create AI Policy - NRTF -> NeRT : <> Policy to prepare and execute \nfor RF Channel -Configuration/Trx Control - NeRT -> NRTF : <> AI Policy create Response - NRTF -> ESrAPP : <> AI Policy create Response - ESrAPP -> ESrAPP : Monitor Energy saving objectives - NeRT -> NeRT : Interpreting AI Policy -group E2 Data Collection -Note over NeRT , ORUs - -``` - -``` - -Near-RT RIC to trigger E2 data collection from different E2 Nodes. - -In the case of O-DU, data collected is expected to include the data from the related O- -RU(s) - -End note - -end - - NeRT -> NeRT : AI/ML Model Inference\n to Evaluate E2 Control/Policy -group E2 Control /Policy - -Note over NeRT , ORUs - -Near-RT RIC to trigger RF Channel Configuration/Trx Control - -E2 Control /Policy towards E2 Nodes and O-RU via O-DU - -End note - -end - -group Opt - - NeRT -> NRTF : <> Notify A1 Policy Status - NRTF -> ESrAPP : <> Notify A1 Policy Status - -end - -group Opt - - ESrAPP -> NRTF : <> Update or Delete A1 Policy - NRTF -> NeRT : <> Update or Delete Policy - ESrAPP -> NRTF : <> Update AI/ML Model - NRTF -> NeRT : Update AI/ML Model - -end - -end - -@enduml - -``` - -The flow diagram of A1 interface based RF channel reconfiguration optimization for energy saving is shown in figure 4.8.2.3.2-1. - -![Sequence diagram showing the flow of A1 interface based RF channel reconfiguration optimization for energy saving. Lifelines include Energy Saving rApp, SMO / Non-RT RIC FWK Function, Near-RT RIC, E2-Node(s), and O-RU(s). The process involves Data Collection, Data Analysis /AI/ML Model Selection and Training, Actor Decision Making, and E2 Control Policy phases.](65b5e4a95d403df0ea5e8ff94f162a6a_img.jpg) - -The diagram illustrates the interaction between the Service Management and Orchestration Framework (SMO) and O-RAN Nodes for energy saving optimization. The lifelines are: Energy Saving rApp, SMO / Non-RT RIC FWK Function, Near-RT RIC, E2-Node(s), and O-RU(s). - -**Sequence of Interactions:** - -- Data Collection:** - - 1 <> Data collection request (rApp to SMO) - - 2 <> Data collection request (SMO to E2-Node(s)) - - 3 <> Data collection request (E2-Node(s) to O-RU(s)) - - 4 <> Data Collection (E2-Node(s) to SMO) - - 5 <> Data Collection (SMO to rApp) -- Data Analysis /AI/ML Model Selection and Training:** - - rApp/Non-RT RIC performs AI/ML Model Selection, re-training and decides to deploy Model in Near-RT RIC or provide AI/ML Model access details. -- Actor Decision Making:** - - 6 <> Create A1 Policy (rApp to SMO) - - 7 <> Policy to prepare and execute for RF Channel Configuration/Tx Control (SMO to Near-RT RIC) - - 8 <> A1 Policy create Response (Near-RT RIC to SMO) - - 9 <> A1 Policy create Response (SMO to rApp) - - 10 Monitor Energy saving objectives (rApp internal) - - 11 Interpreting A1 Policy (Near-RT RIC internal) - - E2 Data Collection:** Near-RT RIC to trigger E2 data collection from different E2 Nodes. In the case of O-DU, data collected is expected to include the data from the related O-RU(s). - - 12 AI/ML Model Inference to Evaluate E2 Control/Policy (Near-RT RIC internal) - - E2 Control Policy:** Near-RT RIC to trigger RF Channel Configuration/Tx Control E2 Control /Policy towards E2 Nodes and O-RU via O-DU. - - Opt:** - - 13 <> Notify A1 Policy Status (Near-RT RIC to SMO) - - 14 <> Notify A1 Policy Status (SMO to rApp) - - Opt:** - - 15 <> Update or Delete A1 Policy (rApp to SMO) - - 16 <> Update or Delete Policy (SMO to Near-RT RIC) - - 17 <> Update AI/ML Model (rApp to SMO) - - 18 Update AI/ML Model (SMO to Near-RT RIC) - -Sequence diagram showing the flow of A1 interface based RF channel reconfiguration optimization for energy saving. Lifelines include Energy Saving rApp, SMO / Non-RT RIC FWK Function, Near-RT RIC, E2-Node(s), and O-RU(s). The process involves Data Collection, Data Analysis /AI/ML Model Selection and Training, Actor Decision Making, and E2 Control Policy phases. - -Figure 4.8.2.3.2-1: Flow diagram of A1 interface based RF channel reconfiguration optimization for energy saving - -#### 4.8.2.4 Required data - -This sub-clause contains the input and output data of model training and inference for energy saving using RF channel reconfiguration. - -##### 4.8.2.4.1 Input data - -The measurement input data are used in model training and inference. They can include the following measurements to monitor energy consumption and energy efficiency of E2 node(s) and O-RU(s): - -- a) DL PDCP SDU data volume per interface (data volume in DL delivered from O-CU-UP to O-DU, per PLMN, per QoS level, per slice, per interface (F1-U, Xn-U, X2-U)) (as specified in 3GPP TS 28.552 [5], clause 5.1.3.6.2.3) -- b) UL PDCP SDU data volume per interface (data volume in UL delivered to O-CU-UP from O-DU, per PLMN, per QoS level, per slice, per interface (F1-U, Xn-U, X2-U)) (as specified in 3GPP TS 28.552 [5], clause 5.1.3.6.2.4) -- c) RSRQ measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.31) -- d) RSRP measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.22) -- e) SINR measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.32) -- f) PNF energy consumption (as specified in 3GPP TS 28.552 [5], clause 5.1.1.19.3) -- g) Power consumed by physical network function & its components (as specified in 3GPP TS 28.552 [5], clause 5.1.1.19.2 and in MP [10], clauses B.1, B.5) -- h) Transmit power (as specified in MP [10], clauses B.1, B.2.1) - -##### 4.8.2.4.2 Output data - -rApps to deliver energy saving & energy efficiency A1 policies for RF channel reconfiguration optimization through R1 interface. - -### 4.8.3 Advanced sleep mode - -This use case describes a method to achieve intelligent energy saving by optimizing the sleep mode via Non-RT RIC-based guidance. - -#### 4.8.3.1 Background and goal of the use case - -Mobile networks were often designed to provide higher data rates, better coverage, and ubiquitous connectivity. They have to be always available and well-dimensioned in order to ensure the best Quality of Service (QoS) even in peak hours and emergency or mass event scenarios. This may lead to an over-dimensioned and under-utilized network particularly when the traffic demand is low, such is the case during night hours. - -The energy consumption of a network is composed of two components: - -- A fixed component, which is mainly due to the system architecture and includes the power consumption of control signals, backhaul infrastructure, and load-independent consumption of baseband processors. -- A variable, load-dependent component, which depends on the transported traffic. - -Over-provisioning of the network as well as low load periods translate into significant, and unnecessary, energy consumption, due to the fixed component. Sleep modes, which consist in shutting down the O-RU for a certain period of time, are an efficient way to handle this component. - -It consists in a progressive deactivation of the O-RU's components according to the time needed by each of them to shut down then reactivate again. According to this transition time, four levels of sleep modes have been specified in CUS [12], clause 16. Deeper sleep levels allow more energy saving but induce larger delays for the users who arrive to the network and who need to wait longer for the components to be reactivated. Hence, Non-RT RIC can provide policies in such cases where reactivation time may not be concern or proactively reactivates. - -O-RU and E2 nodes (O-CU, O-DU) may implement various sleep modes. The sleep modes could be enabled by SMO/Non-RT RIC through A1 policy. When enabled, the Near-RT RIC selects among the sleep modes considering their capabilities, the actual traffic situation, and the network conditions. Different SM operate at different time scales (e.g., symbol, slot, frame). - -This solution proposes a framework that allows the operator to flexibly select various sleep modes parameters through A1 policy formulated by rApp towards Near-RT RIC through SMO/Non-RT RIC framework assisted by Machine Learning (ML) techniques. - -#### 4.8.3.2 Entities/resources involved in the use case - -##### 1) SMO/Non-RT RIC framework function: - -- Collect the configurations, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) from E2 node(s) and trace records (e.g., per-UE measurement metrics and location information) through O1 interface, for the purpose of decision making, optionally using training and inference of AI/ML models that assist such EE/ES functions. -- Transfer collected data towards rApp. It is assumed that configurations, performance indicators and measurement reports collected from the O-DU contain the related information for the corresponding O-RU(s). -- Signal A1 policies for Near-RT RIC for ASM optimization A1 interface. -- (Optionally) Retrain, update, configure AI/ML models in Non-RT RIC. - -##### 2) rApps: - -- Collect the necessary configurations, performance indicators, and measurement reports from SMO/Non-RT RIC framework function, for the purpose of training and execution of relevant AI/ML models. -- (Optionally) Retrain, update, configure EE/ES AI/ML model. -- Infer an optimized A1 policy for ASM based on the data collected using R1 interface. - -##### 3) E2 nodes: - -- Report cell configuration, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports, Trace records such as per-UE measurement metrics and location information) to SMO via O1 interface. -- Report measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) to Near-RT RIC via E2 interface. -- Support actions required to perform ASM and Trx control for EE/ES optimization. - -##### 4) O-RU: - -- Report EC and EE related information via open FH M-plane interface to O-DU . -- Support actions required to perform ASM and Trx control for EE/ES optimization. - -##### 5) Near-RT RIC (For A1 policy based solution): - -- Collect measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) from E2 nodes. -- (Optionally) Receive EE/ES AI/ML model for deployment via O1 or O2 interface. -- Receive EE/ES related policies via A1 interface for consideration during optimization. -- Analyse the received data from E2 nodes and perform AI/ML model inference to determine ASM & Trx control EE/ES. Optimization (i.e., ASM to be activated for certain time and cells) considering the optimization targets/policies. -- Provide policies or required information to E2 node (O-CU) via E2 to trigger actions for EE/ES optimization. - -#### 4.8.3.3 Solution - -##### 4.8.3.3.1 A1 policy based ASM optimization for energy saving - -In this solution, decision making, potentially using AI/ML model inference, is done at Near-RT RIC. While AI/ML model training might be hosted in Non-RT or Near-RT RIC, the description below is based on AI/ML model inferencing in the Near-RT RIC. - -The context of the A1 policy based ASM optimization for energy saving is captured in table 4.8.3.3.1-1. - -**Table 4.8.3.3.1-1: A1 policy based ASM optimization for energy saving** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Enable A1 policy based ASM energy saving functions in the network by means of configuration parameter change and actions controlled by Near-RT RIC and allow for AI/ML-based solutions. | | -| Actors and Roles | SMO/Non-RT RIC framework function: A1 & O1 termination.
rApp: ASM optimization.
E2 node(s), O-RU: Enforces ASM E2 controls or policies.
Near-RT RIC: ASM energy savings decision making function. | | -| Assumptions | O1 interface connectivity is established between SMO and E2 nodes.
R1 interface connectivity is established.
Open FH M-plane interface is established between E2 node(s) and O-RU.
E2 interface connectivity is established between E2 node and Near-RT RIC.
A1 interface is established between Non-RT RIC and Near-RT RIC.
Network is operational. | | -| Pre-conditions | Operator has set the targets for energy saving functions in the Non-RT RIC. | | -| Begins when | Operator enables the optimization rApp along with initial ML model for ASM energy saving functions and E2 node(s) and O-RU(s) become operational.
See NOTE. | | -| Step 1 (M) | rApp requests to collect necessary configurations, performance indicators, and measurement data towards SMO/Non-RT RIC framework function over R1 interface.
Configurations may contain data related to node capability such as O-RU ASM capability information which rApp needs to know before formulating A1 policies for ASM optimization. | | -| Step 2 (M) | SMO/Non-RT RIC framework function requests data collection towards E2 node(s) and O-RU(s) (via E2 node(s)) over O1 interface. | | -| Step 3 (M) | E2 node(s) upon receiving request from SMO/Non-RT RIC framework function requests and collect necessary data from O-RU(s) over open FH M-plane interface. | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 4 (M) | E2 node(s) sends the configuration data, configured measurement data to SMO/Non-RT RIC framework function periodically or event based. | | -| Step 5 (M) | rApp collects the configuration data, collected measurement data for processing. | | -| Step 6 (M) | rApp to trigger EE/ES optimization through A1 policy to prepare and execute ASM & Trx control. | | -| Step 7 (M) | Non-RT RIC framework receives policy from rApp and forwards it towards Near-RT RIC via A1 interface. | | -| Step 8 (M) | Near-RT RIC provides A1 policy response to SMO/Non-RT RIC framework. | | -| Step 9 (M) | Non-RT RIC framework informs rApp about A1 policy feedback. | | -| Step 10 (M) | rApp monitors energy saving objectives as per A1 policy. | | -| Step 11 (M) | The Near-RT RIC receives the policy from the Non-RT RIC over the A1 interface. It then interprets the policy to determine the required data collection and E2 control/policies. | | -| Step 12 (M) | Inferencing AI/ML model to evaluate & generate E2 control or policies for ASM optimization. | | -| Step 13 (M) | Near-RT RIC to notify Non-RT RIC if any change in the state of policy. | | -| Step 14 (M) | SMO/Non-RT RIC framework forwards notification received from Near-RT RIC to rApp. | | -| Step 15 (O) | If energy saving objectives are not achieved rApp may decide to initiate fallback mechanism for example, updating or deleting A1 policy for ASM optimization. | | -| Step 16 (O) | SMO/Non-RT RIC framework send update or delete A1 policies to Near-RT RIC | | -| Step 17 (O) | rApp can update or retrain AI/ML model based on evaluation of energy saving objectives. | | -| Step 18 (O) | SMO/Non-RT RIC framework send update or retrain AI/ML model to Near-RT RIC. | | -| Ends when | E2 node(s) becomes non-operational or when the operator disables the rApp or ML model for energy saving. | | -| Exceptions | N/A | | -| Post Conditions | rApp continues monitoring of energy saving function at E2 node(s) and O-RU.
E2 node(s) and O-RU(s) operate using the newly deployed parameters/models and state (off/on). | | - -NOTE: Operator can set policies through rApp or allow AI/ML model in rApp to infer policies. - -``` -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -Skin rose -skinparam ParticipantPadding 5 -``` - -``` - -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -Box "Service Management and Orchestration Framework" #gold -Box #lightgrey -Participant "Energy Saving\nrApp" as ESRAPP - -End Box - -Participant "SMO / Non-RT RIC\nFWK Function" as NRTF - -End box - -Box " O-RAN Nodes" #lightpink - Participant "Near-RT RIC" as NeRT - Participant "E2-Node(s)" as E2NODES - Participant "O-RU(s) " as ORUs - -End box - -group Data Collection - ESRAPP -> NRTF : <> Data collection request - NRTF -> E2NODES : <> Data collection request - E2NODES <-> ORUs : <> Data collection request - E2NODES -> NRTF : <> Data Collection - NRTF -> ESRAPP : <> Data Collection - -End - -group Data Analysis /AI/ML Model Selection and Training - -Note over ESRAPP , NeRT -rApp/Non-RT RIC performs AIML Model Selection ,re-training and decides -to deploy Model in Near-RT RIC or provide AIML Model access details. - -End note - -end - -group Actor Decision Making - - ESRAPP -> NRTF : <> Create A1 Policy - NRTF -> NeRT : <> Policy to prepare and execute \nfor ASM - NeRT -> NRTF : <> A1 Policy create Response - NRTF -> ESRAPP : <> A1 Policy create Response - ESRAPP -> ESRAPP : Monitor Energy saving objectives - NeRT -> NeRT : Interpreting A1 Policy - -``` - -``` - -group E2 Data Collection - -Note over NeRT , ORUs -Near-RT RIC to trigger E2 data collection from E2 Nodes and O-RU via O-DU -End note -end - - NeRT -> NeRT : AI/ML Model Inference\n to Evaluate E2 Control/Policy - -group E2 Control /Policy - -Note over NeRT , ORUs -Near-RT RIC to trigger E2 Control /Policy towards E2 Nodes and O-RU via O-DU -End note -end - -group Opt - - NeRT -> NRTF : <> Notify A1 Policy Status - NRTF -> ESRAPP : <> Notify A1 Policy Status - -end - -group Opt - - ESRAPP -> NRTF : <> Update or Delete A1 Policy - NRTF -> NeRT : <> Update or Delete Policy - ESRAPP -> NRTF : <> Update AI/ML Model - NRTF -> NeRT : Update AI/ML Model - -end -end - -@enduml - -@startuml -'https://plantuml.com/sequence-diagram - -!pragma teoz true - -Skin rose - -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber - -Box "Service Management and Orchestration Framework" #gold -Box #lightgrey - -Participant "Energy Saving\nrApp" as ESRAPP - -``` - -``` -End Box -``` - -``` -Participant "SMO / Non-RT RIC\nFWK Function" as NRTF -``` - -``` -End box -``` - -``` -Box " O-RAN Nodes" #lightpink -``` - -``` - Participant "Near-RT RIC" as NeRT -``` - -``` - Participant "E2-Node(s)" as E2NODES -``` - -``` - Participant "O-RU(s) " as ORUs -``` - -``` -End box -``` - -``` -group Data Collection -``` - -``` - ESRAPP -> NRTF : <> Data collection request -``` - -``` - NRTF -> E2NODES : <> Data collection request -``` - -``` - E2NODES <-> ORUs : <> Data collection request -``` - -``` - E2NODES -> NRTF : <> Data Collection -``` - -``` - NRTF -> ESRAPP : <> Data Collection -``` - -``` -End -``` - -``` -group Data Analysis /AI/ML Model Selection and Training -``` - -``` -Note over ESRAPP , NeRT -``` - -``` -rApp/Non-RT RIC performs AIML Model Selection , re-training and decides -to deploy Model in Near-RT RIC or provide AIML Model access details. -``` - -``` -End note -``` - -``` -end -``` - -``` -group Actor Decision Making -``` - -``` - ESRAPP -> NRTF : <> Create A1 Policy -``` - -``` - NRTF -> NeRT : <> Policy to prepare and execute \nfor ASM -``` - -``` - NeRT -> NRTF : <> A1 Policy create Response -``` - -``` - NRTF -> ESRAPP : <> A1 Policy create Response -``` - -``` - ESRAPP -> ESRAPP : Monitor Energy saving objectives -``` - -``` - NeRT -> NeRT : Interpreting A1 Policy -``` - -``` -group E2 Data Collection -``` - -``` -Note over NeRT , ORUs -``` - -``` -Near-RT RIC to trigger E2 data collection from E2 Nodes and O-RU via O-DU -``` - -``` -End note -``` - -``` -end -``` - -``` - NeRT -> NeRT : AI/ML Model Inference\n to Evaluate E2 Control/Policy -``` - -``` -group E2 Control /Policy -``` - -``` -Note over NeRT , ORUs -``` - -``` -Near-RT RIC to trigger E2 Control /Policy towards E2 Nodes and O-RU via O-DU - -End note - -end - -group Opt - NeRT -> NRTF : <> Notify A1 Policy Status - NRTF -> ESRAPP : <> Notify A1 Policy Status -end - -group Opt - ESRAPP -> NRTF : <> Update or Delete A1 Policy - NRTF -> NeRT : <> Update or Delete Policy - ESRAPP -> NRTF : <> Update AI/ML Model - NRTF -> NeRT : Update AI/ML Model -end - -end - -@enduml -``` - -The flow diagram of A1 interface based ASM optimization for energy saving is shown in figure 4.8.3.3.1-1. - -![Sequence diagram showing the flow of A1 interface based ASM optimization for energy saving. Lifelines include Energy Saving rApp, SMO / Non-RT RIC FWK Function, Near-RT RIC, E2-Node(s), and O-RU(s). The process involves Data Collection, Data Analysis / AI/ML Model Selection and Training, Actor Decision Making, E2 Data Collection, and E2 Control /Policy.](cf03eff1218a8cc1be6b05de892162de_img.jpg) - -``` - -sequenceDiagram - participant rApp as Energy Saving rApp - participant FWK as SMO / Non-RT RIC FWK Function - participant RIC as Near-RT RIC - participant E2 as E2-Node(s) - participant RU as O-RU(s) - - Note left of rApp: Service Management and Orchestration Framework - Note right of RU: O-RAN Nodes - - Note left of rApp: Data Collection - rApp->>FWK: 1 <> Data collection request - FWK->>E2: 2 <> Data collection request - E2->>RU: 3 <> Data collection request - RU-->>E2: 4 <> Data Collection - E2-->>FWK: 5 <> Data Collection - - Note left of rApp: Data Analysis /AI/ML Model Selection and Training - Note right of rApp: rApp/Non-RT RIC performs AI/ML Model Selection ,re-training and decides to deploy Model in Near-RT RIC or provide AI/ML Model access details. - - Note left of rApp: Actor Decision Making - rApp->>FWK: 6 <> Create A1 Policy - FWK->>RIC: 7 <> Policy to prepare and execute for ASM - RIC-->>FWK: 8 <> A1 Policy create Response - FWK-->>rApp: 9 <> A1 Policy create Response - rApp->>rApp: 10 Monitor Energy saving objectives - - Note right of RIC: E2 Data Collection - RIC->>RIC: 11 Interpreting A1 Policy - Note right of RIC: Near-RT RIC to trigger E2 data collection from E2 Nodes and O-RU via O-DU - RIC->>RIC: 12 AI/ML Model Inference to Evaluate E2 Control/Policy - - Note right of RIC: E2 Control /Policy - Note right of RIC: Near-RT RIC to trigger E2 Control /Policy towards E2 Nodes and O-RU via O-DU - - Note left of rApp: Opt - RIC-->>FWK: 13 <> Notify A1 Policy Status - FWK-->>rApp: 14 <> Notify A1 Policy Status - - Note left of rApp: Opt - rApp->>FWK: 15 <> Update or Delete A1 Policy - FWK->>RIC: 16 <> Update or Delete Policy - rApp->>FWK: 17 <> Update AI/ML Model - FWK->>RIC: 18 Update AI/ML Model - -``` - -Sequence diagram showing the flow of A1 interface based ASM optimization for energy saving. Lifelines include Energy Saving rApp, SMO / Non-RT RIC FWK Function, Near-RT RIC, E2-Node(s), and O-RU(s). The process involves Data Collection, Data Analysis / AI/ML Model Selection and Training, Actor Decision Making, E2 Data Collection, and E2 Control /Policy. - -Figure 4.8.3.3.1-1: Flow diagram of A1 interface based ASM optimization for energy saving - -#### 4.8.3.4 Required data - -This sub-clause contains the input and output data of model training and inference for energy saving using ASM. - -##### 4.8.3.4.1 Input data - -The measurement input data are used in model training and inference. They can include the following measurements to monitor energy consumption and energy efficiency of E2 node(s) and O-RU(s): - -- a) DL PDCP SDU data volume per interface (data volume in DL delivered per PLMN, per QoS level, per slice, per interface ((from O-CU-UP to O-DU over F1-U, to external O-CU-UP over Xn-U and to external O-eNB over X2-U)) (as specified in 3GPP TS 28.552 [5], clause 5.1.3.6.2.3) -- b) UL PDCP SDU data volume per interface (data volume in UL delivered per PLMN, per QoS level, per slice, per interface ((from O-DU to O-CU-UP over F1-U, to external O-CU-UP over Xn-U and to external O-eNB over X2-U)) (as specified in 3GPP TS 28.552 [5], clause 5.1.3.6.2.4) -- c) RSRQ measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.31) -- d) RSRP measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.22) -- e) SINR measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.32) -- f) PNF energy consumption (as specified in 3GPP TS 28.552 [5], clause 5.1.1.19.3) -- g) Power consumed by physical network function & its components (as specified in 3GPP TS 28.552 [5], clause 5.1.1.19.2 and in MP [10], clauses B.1, B.5) -- h) Transmit power (as specified in MP [10], clauses B.1, B.2.1) -- i) M1 MDT measurement in trace record for immediate MDT measurements (as specified in 3GPP TS 32.423 [11], clause 4.34.1) -- j) UE location in trace record for UE location information (as specified in 3GPP TS 32.423 [11], clause 4.34.2) -- k) O-RU ASM capability information (as specified in MP [10], clause 20.4) - -##### 4.8.3.4.2 Output data - -rApps to deliver energy saving & energy efficiency policies for ASM optimization through R1 interface. - -### 4.8.4 Time domain cell DTX/DRX optimization (3GPP Rel-18) - -#### 4.8.4.1 Background and goal of the use case - -In 3GPP Release 18 [21], clause 15.4.2.3, Discontinuous Transmission (DTX) and Discontinuous Reception (DRX) mechanisms were further enhanced to improve energy efficiency for the gNB. To reduce the gNB's downlink transmission and uplink reception active time, the UE can be configured with a periodic cell DTX/DRX pattern, which defines active and non-active periods. This pattern is common for UEs configured with this feature in the cell, and the cell DTX/DRX patterns can be configured and activated separately. A maximum of two cell DTX/DRX patterns can be configured per MAC entity for different serving cells. When cell DTX is activated, the UE may not monitor PDCCH in selected cases or does not monitor SPS occasions during the non-active duration of the cell DTX. Similarly, when cell DRX is activated, the UE does not transmit on CG resources or transmit an SR during the non-active duration of the cell DRX. This feature is applicable only to UEs in the RRC\_CONNECTED state and does not impact the Random Access procedure, SSB transmission, paging, or system information broadcasting. Cell DTX/DRX can be activated or deactivated via RRC signaling or L1 group common signaling. - -Cell DTX/DRX is characterized by: - -- Active duration: The duration during which the UE is expected to receive PDCCHs, SPS occasions, and transmit SR or CG. In this duration, the gNB's transmission/reception of PDCCH, SPS, SR, CG, and periodic/semi-persistent CSI reports are not impacted for energy-saving purposes. -- Cycle: Specifies the periodic repetition of the active duration followed by a non-active period. - -The active duration and cycle parameters are common between cell DTX and DRX when both are configured. If there is an emergency call or a public safety-related service (e.g., MPS or MCS), the network ensures that these services are not - -impacted, possibly by releasing or deactivating the cell DTX/DRX configuration. The network should also ensure at least partial overlap between the UE's connected mode DRX on-duration and cell DTX/DRX active duration, ensuring that the UE's DRX periodicity is a multiple of the cell DTX/DRX periodicity, or vice versa. - -The Non-RT RIC considers several factors when generating A1 policies for energy savings through cell DTX/DRX. These factors include real-time traffic patterns, the density of Rel-18-capable UEs, and the potential for energy savings in specific cells. It also evaluates QoE/QoS requirements to ensure service quality is maintained. Based on this analysis, the Non-RT RIC generates A1 policies that include, but are not limited to, the following: - -**Activate DTX/DRX** in cells with low traffic or a high concentration of Rel-18 UEs. - -**Steer Rel-18 UEs** toward specific cells, enabling those cells to either operate efficiently or be shut down. - -**Bar non-Rel-18 UEs** from cells optimized for DTX/DRX to maximize energy savings. - -**Balance QoE/QoS** by adjusting traffic steering and DTX/DRX settings, ensuring energy efficiency without service degradation. - -These A1 policies are enforced by the Near-RT RIC, which dynamically applies DTX/DRX configurations and traffic steering decisions in near-real-time. - -#### 4.8.4.2 Entities/resources involved in the use case - -##### 1) SMO/Non-RT RIC framework: - -- Collect the configurations, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) from E2 node(s)\_and trace records (e.g., per-UE measurement metrics, location information, Rel-18 and pre-Rel-18 supported UE information) through O1 interface, for the purpose of decision making. -- Transfer collected data towards rApp. It is assumed that configurations, performance indicators and measurement reports collected from the O-DU contain the related information for the corresponding O-RU(s). -- Create A1 policies for Near-RT RIC based on rApp request to optimize time domain cell DTX/DRX via the A1 interface. - -##### 2) rApps: - -- Collect the necessary configurations, performance indicators, and measurement reports from SMO/Non-RT RIC framework function, for the purpose of training and execution of relevant AI/ML models. -- (Optionally) Retrain, update, configure EE/ES AI/ML model. -- Infer an optimized A1 policy for time domain cell DTX/DRX optimization based on the data collected using R1 interface. - -##### 3) E2 nodes: - -- Report cell configuration, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports, trace records such as per-UE measurement metrics, location information and Rel-18 and pre-Rel-18 supported UE information) to SMO via O1 interface. -- Report measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) to Near-RT RIC via E2 interface. -- Support actions required to perform time domain cell DTX/DRX based optimization for EE/ES optimization. - -Note that the requirements of O1 interface for E2 nodes are under the scope of WG10. - -##### 4) O-RU: - -- Report EC and EE related information via open FH M-plane interface to O-DU. - -b) Support actions required to perform time domain cell DTX/DRX based optimization for EE/ES optimization. Note that the requirements for O-RU and open FH are under the scope of WG4. - -##### 5) Near-RT RIC: - -- a) Collect measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports, Rel-18 and pre-Rel-18 supported UE information) from E2 nodes. -- b) (Optionally) Receive EE/ES AI/ML model for deployment via O1 or O2 interface. -- c) Analyse the received data from E2 nodes and perform AI/ML model inference to determine time domain cell DTX/DRX based EE/ES optimization (i.e., time domain cell DTX/DRX to be activated for certain time and cells) considering the optimization targets/policies. -- d) Provide policies or required information to E2 node (O-CU) via E2 to trigger actions for EE/ES optimization. - -Note that the requirements for Near-RT RIC are under the scope of WG3. - -#### 4.8.4.3 Solution - -##### 4.8.4.3.1 A1 policy based time domain cell DTX/DRX optimization for energy saving - -In this solution, decision making, potentially using AI/ML model inference, is done at Near-RT RIC. While AI/ML model training might be hosted in Non-RT RIC or Near-RT RIC, the description below is based on AI/ML model inferencing in the Near-RT RIC. - -The context of the A1 policy based time domain cell DTX/DRX optimization for energy saving is captured in table 4.8.4.3.1-1. - -**Table 4.8.4.3.1-1: A1 policy based time domain cell DTX/DRX optimization for energy saving** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | A1 policy based guidance for performing time domain cell DTX/DRX energy saving in the network. | | -| Actors and Roles | SMO/Non-RT RIC framework function: A1 & O1 termination.
rApp: Time domain cell DTX/DRX optimization.
E2 node(s): Enforces time domain cell DTX/DRX on O-RU based on E2 policy or control.
Near-RT RIC: Time domain cell DTX/DRX energy savings decision making function. | | -| Assumptions | O1 interface connectivity is established between SMO and E2 nodes.
R1 interface connectivity is established.
Open FH M-plane interface is established between E2 node(s) and O-RU.
E2 interface connectivity is established between E2 node and Near-RT RIC.
A1 interface is established between Non-RT RIC and Near-RT RIC.
Network is operational. | | -| Pre-conditions | Operator has set the targets for energy saving in the Non-RT RIC. | | - -| Use Case Stage | Evolution / Specification | <> | -|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Begins when | Operator enables the rApp along with initial ML model for time domain cell DTX/DRX energy saving and E2 node(s) and O-RU(s) become operational.

See NOTE. | | -| Step 1 (M) | rApp requests to collect necessary configurations, performance indicators, and measurement data towards SMO/Non-RT RIC framework over R1 interface.

Configurations may contain data related to UE capability to support 3GPP Rel-18, which rApp needs to know before formulating A1 policies for time domain cell DTX/DRX optimization. | | -| Step 2 (M) | SMO/Non-RT RIC framework requests data collection towards E2 node(s) and O-RU(s) (via E2 node(s)) over O1 interface. | | -| Step 3 (M) | E2 node(s) upon receiving request from SMO/Non-RT RIC framework requests and collect necessary data from O-RU(s) over open FH M-plane interface. | | -| Step 4 (M) | E2 node(s) sends the configuration data, configured measurement data to SMO/Non-RT RIC framework periodically or event based. | | -| Step 5 (M) | rApp collects the configuration data, collected measurement data for processing. | | -| Step 6 (M) | rApp to trigger EE/ES optimization through A1 policy to prepare and execute time domain cell DTX/DRX optimization. | | -| Step 7 (M) | SMO/Non-RT RIC framework receives policy from rApp and forwards it towards Near-RT RIC via A1 interface. | | -| Step 8 (M) | Near-RT RIC provides A1 policy response to SMO/Non-RT RIC framework. | | -| Step 9 (M) | SMO/Non-RT RIC framework informs rApp about A1 policy feedback. | | -| Step 10 (M) | rApp monitors energy saving objectives as per A1 policy. | | -| Step 11 (M) | It then interprets the policy to determine the required data collection and E2 control/policies. | | -| Step 12 (M) | Inferencing AI/ML model to evaluate & generate E2 control or policies for time domain cell DTX/DRX optimization. | | -| Step 13 (M) | Near-RT RIC to notify Non-RT RIC if any change in the state of policy. | | -| Step 14 (M) | SMO/Non-RT RIC framework forwards notification received from Near-RT RIC to rApp. | | -| Step 15 (O) | If energy saving objectives are not achieved rApp may decide to initiate fallback mechanism for example, updating or deleting A1 policy for time domain cell DTX/DRX optimization. | | -| Step 16 (O) | SMO/Non-RT RIC framework send update or delete A1 policies to Near-RT RIC. | | -| Ends when | E2 node(s) becomes non-operational or when the operator disables the rApp for ML model for energy saving. | | -| Exceptions | N/A | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Post Conditions | rApp continues monitoring of energy saving function at E2 node(s) and O-RU.
E2 node(s) and O-RU(s) operate using the newly deployed parameters/models and state (off/on). | | - -NOTE: Operator can set policies through rApp or allow AI/ML model in rApp to infer policies. - -``` -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -Skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -Box "Service Management and Orchestration Framework" #gold -Box #lightgrey -Participant "Energy Saving\rApp" as ESRAPP - -End Box - -Participant "SMO / Non-RT RIC\nFWK " as NRTF - -End box - -Box " O-RAN Nodes" #lightpink - Participant "Near-RT RIC" as NeRT - Participant "E2-Node(s)" as E2NODES - Participant "O-RU(s) " as ORUs - -End box - -group Data Collection - ESRAPP -> NRTF : <> Data collection request - NRTF -> E2NODES : <> Data collection request - E2NODES <-> ORUs : <> Data collection request - E2NODES -> NRTF : <> Data Collection - NRTF -> ESRAPP : <> Data Collection -End - -group Data Analysis /AI/ML Model Selection and Training -Note over ESRAPP , NeRT -``` - -``` - -rApp/Non-RT RIC performs AI/ML model selection, retraining, and deployment decisions. - -For a model deployment request, the rApp provides the rAppId, AI/ML model identifier, and -target deployment location - -End note - -End - -group Actor Decision Making - - ESrAPP -> NRTF : <> Create A1 Policy - NRTF -> NeRT : <> Policy to prepare and execute \nfor Time domain Cell DTX/DRX optimization - NeRT -> NRTF : <> A1 Policy create Response - NRTF -> ESrAPP : <> A1 Policy create Response - ESrAPP -> ESrAPP : Monitor Energy saving objectives - NeRT -> NeRT : Interpreting A1 Policy - -group E2 Data Collection - -Note over NeRT , ORUs - -Near-RT RIC to trigger E2 data collection from E2 Nodes and O-RU via O-DU - -End note - -end - - NeRT -> NeRT : AI/ML Model Inference\n to Evaluate E2 Control/Policy - -group E2 Control /Policy - -Note over NeRT , ORUs - -Near-RT RIC to trigger E2 Control /Policy towards E2 Nodes - -End note - -end - -group Opt - - NeRT -> NRTF : <> Notify A1 Policy Staus - NRTF -> ESrAPP : <> Notify A1 Policy Staus - -end - -group Opt - - ESrAPP -> NRTF : <> Update or Delete A1 Policy - NRTF -> NeRT : <> Update or Delete Policy - -end - -end - -@enduml - -``` - -The flow diagram of A1 interface-based time domain cell DTX/DRX optimization for energy saving is shown in figure 4.8.4.3.1-1. - -![Sequence diagram showing the flow of A1 interface-based time domain cell DTX/DRX optimization for energy saving. The diagram is divided into two main lifelines: 'Service Management and Orchestration Framework' (left) and 'O-RAN Nodes' (right, containing Near-RT RIC, E2-Node(s), and O-RU(s)). The process includes Data Collection, Data Analysis/AI/ML Model Selection and Training, Actor Decision Making, E2 Data Collection, and E2 Control/Policy. Key messages include 'Data collection request', 'Data Collection', 'Create A1 Policy', 'A1 Policy to prepare and execute for Time domain Cell DTX/DRX optimization', 'A1 Policy create Response', 'Monitor Energy saving objectives', 'Interpreting A1 Policy', 'AI/ML Model Inference to Evaluate E2 Control/Policy', 'Notify A1 Policy Status', and 'Update or Delete A1 Policy'.](f4e5a86da5c799372a7c1ea2397dedb7_img.jpg) - -The sequence diagram illustrates the interaction for energy saving optimization. It starts with the **Service Management and Orchestration Framework** (Energy Saving rApp) sending a **«R1» Data collection request** to the **SMO / Non-RT RIC FWK**. The SMO then sends a **«O1» Data collection request** to the **Near-RT RIC**, which in turn sends a **«FH» Data collection request** to the **E2-Node(s)** and **O-RU(s)**. Responses are returned through the chain: **«O1» Data Collection** from E2-Node(s) to Near-RT RIC, and **«R1» Data Collection** from Near-RT RIC to Energy Saving rApp. - -Next, the **Data Analysis /AI/ML Model Selection and Training** phase occurs, where the rApp/Non-RT RIC performs model selection, retraining, and deployment decisions. The **Actor Decision Making** phase follows, with the Energy Saving rApp sending a **«R1» Create A1 Policy** to the SMO. The SMO sends an **«A1» Policy to prepare and execute for Time domain Cell DTX/DRX optimization** to the Near-RT RIC, which responds with an **«A1» A1 Policy create Response**. The Energy Saving rApp then receives a **«R1» A1 Policy create Response** and begins to **Monitor Energy saving objectives**. - -The Near-RT RIC proceeds with **Interpreting A1 Policy**, followed by **E2 Data Collection** (triggered by Near-RT RIC via O-DU) and **AI/ML Model Inference to Evaluate E2 Control/Policy**. This leads to **E2 Control /Policy** (triggered by Near-RT RIC towards E2 Nodes). Optional steps include **«A1» Notify A1 Policy Status** and **«R1» Notify A1 Policy Status**, as well as **«R1» Update or Delete A1 Policy** and **«A1» Update or Delete Policy**. - -Sequence diagram showing the flow of A1 interface-based time domain cell DTX/DRX optimization for energy saving. The diagram is divided into two main lifelines: 'Service Management and Orchestration Framework' (left) and 'O-RAN Nodes' (right, containing Near-RT RIC, E2-Node(s), and O-RU(s)). The process includes Data Collection, Data Analysis/AI/ML Model Selection and Training, Actor Decision Making, E2 Data Collection, and E2 Control/Policy. Key messages include 'Data collection request', 'Data Collection', 'Create A1 Policy', 'A1 Policy to prepare and execute for Time domain Cell DTX/DRX optimization', 'A1 Policy create Response', 'Monitor Energy saving objectives', 'Interpreting A1 Policy', 'AI/ML Model Inference to Evaluate E2 Control/Policy', 'Notify A1 Policy Status', and 'Update or Delete A1 Policy'. - -Figure 4.8.4.3.1-1: Flow diagram of A1 interface-based time domain cell DTX/DRX optimization for energy saving - -#### 4.8.4.4 Required data - -This sub-clause contains the input and output data of model training and inference for energy saving using time domain cell DTX/DRX optimization. - -##### 4.8.4.4.1 Input data - -The measurement input data are used in model training and inference. They can include the following measurements to monitor energy consumption and energy efficiency of E2 node(s) and O-RU(s): - -- a) DL PDCP SDU data volume per interface (data volume in DL delivered per PLMN, per QoS level, per slice, per interface (from O-CU-UP to O-DU over F1-U, to external O-CU-UP over Xn-U and to external O-eNB over X2-U)) (as specified in 3GPP TS 28.552 [5], clause 5.1.3.6.2.3) -- b) UL PDCP SDU data volume per interface (data volume in UL delivered per PLMN, per QoS level, per slice, per interface (from O-DU to O-CU-UP over F1-U, to external O-CU-UP over Xn-U and to external O-eNB over X2-U)) (as specified in 3GPP TS 28.552 [5], clause 5.1.3.6.2.4) -- c) RSRQ measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.31) -- d) RSRP measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.22) -- e) SINR measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.32) -- f) PNF energy consumption (as specified in 3GPP TS 28.552 [5], clause 5.1.1.19.3) -- g) Power consumed by physical network function & its components (as specified in 3GPP TS 28.552 [5], clause 5.1.1.19.2 and in MP [10], clauses B.1, B.5) -- h) Transmit power (as specified in MP [10], clauses B.1, B.2.1) -- i) M1 MDT measurement in trace record for immediate MDT measurements (as specified in 3GPP TS 32.423 [11], clause 4.34.1) -- j) UE location in trace record for UE location information (as specified in 3GPP TS 32.423 [11], clause 4.34.2) -- k) UE capability information to support the time domain cell DTX/DRX inter-band CA operation (as specified in 3GPP TS 38.306 [22], clause 4.2.7.2) -- l) Measurement of paging success rate, helps optimize DRX cycle length to minimize paging failures and avoid unnecessary wake ups (as specified in 3GPP TS 28.552 [5], clause 5.1.1.27) -- m) DRX cycle parameters like on-duration timer, inactivity timer, and short/long DRX cycle lengths per UE (as specified in 3GPP TS 38.331 [20], clause 5.7) -- n) Battery usage patterns from UEs during active and DRX modes to optimize DRX configurations to balance energy savings for the network and battery preservation for UEs (as specified 3GPP TS 28.552 [5], clause A.122) -- o) Quality of Service (QoS) class identifier or 5G QoS indicator assigned to UEs to determine which UEs can enter DRX mode without compromising critical services e.g., VoIP, real-time video (as specified 3GPP TS 23.501 [2], clauses 5.7.3, 5.7.4) - -##### 4.8.4.4.2 Output data - -rApps to deliver energy saving & energy efficiency A1 policies for time domain cell DTX/DRX optimization through R1 interface. - -### 4.8.5 Spatial and power domain optimization (3GPP Rel-18) - -#### 4.8.5.1 Background and goal of the use case - -In 3GPP Release-18 [21], clause 15.4.2.7 Spatial Domain (SD) and Power Domain (PD) adaptations were introduced. These features enable the gNB to dynamically adjust the number of active antenna elements and transmission power based on UE channel conditions. In the spatial domain, adaptive control allows antenna elements to be turned on or off depending on demand, while in the power domain, transmission power is adjusted according to the CSI (Channel State Information) reports provided by UEs. These adaptations optimize energy consumption of Transceiver Unit (TXRU) and Power Amplifier (PA) while maintaining service quality. - -The Non-RT RIC, through A1 policies, provides high-level guidance to the Near-RT RIC on how to manage these energy-saving features. For spatial domain adaptation, A1 policies advise the Near-RT RIC to prioritize cells with the highest potential for energy savings, such as those with a lower number of active UEs or with more Rel-18-capable UEs. This allows the Near-RT RIC to adapt spatial resources more efficiently, focusing energy-saving efforts where they are most impactful. - -For power domain adaptation, the Non-RT RIC provides policy-level guidance based on long-term traffic patterns and CSI reports. A1 policies direct the Near-RT RIC to target cells where transmission power reductions can be implemented without compromising service. The policies focus on balancing energy efficiency with maintaining adequate network performance by advising which cells are suitable for power reduction. - -Through these A1 policies, the Non-RT RIC enables the Near-RT RIC to manage spatial and power resources dynamically, ensuring that energy-saving measures are applied where they offer the most benefit, all while maintaining service quality. This high-level guidance helps align real-time network operations with strategic energy-saving goals. - -**Adaptive spatial control:** Non-RT RIC A1 policies enable dynamic control of antenna elements prioritizing cells with lower traffic density or higher Rel-18 UE concentration for enhanced energy efficiency. - -**Transmission power:** Non-RT RIC A1 policies enable dynamic downlink power control of cells with lower traffic density or higher Rel-18 UE concentration for enhanced energy efficiency. - -**Steer Rel-18 UEs** toward specific cells, enabling those cells to either operate efficiently or be shut down. - -**Bar non-Rel-18 UEs** from cells optimized for power and spatial energy savings to maximize energy savings. - -#### 4.8.5.2 Entities/resources involved in the use case - -##### 1) SMO/Non-RT RIC framework: - -- Collect the configurations, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) from E2 node(s) and trace records (e.g., per-UE measurement metrics, location information, Rel-18 and pre-R-18 supported UE information) through O1 interface, for the purpose of decision making. -- Transfer collected data towards rApp. It is assumed that configurations, performance indicators and measurement reports collected from the O-DU contain the related information for the corresponding O-RU(s). -- Create A1 Policies for Near-RT RIC based on rApp request for spatial and power domain energy savings optimization via A1 Interface. - -##### 2) rApps: - -- Collect the necessary configurations, performance indicators, and measurement reports from SMO/Non-RT RIC framework, for the purpose of training and execution of relevant AI/ML models. -- (Optionally) Retrain, update, configure EE/ES AI/ML model. -- Infer an optimized A1 policy for spatial and power domain optimization on the data collected using R1 interface. - -##### 3) E2 node: - -- Report cell configuration, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports, trace records such as per-UE measurement metrics, location information and Rel-18 and pre-Rel-18 supported UE information) to SMO via O1 interface. -- Report measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) to Near-RT RIC via E2 interface. -- Support actions required to perform spatial and power domain optimization for EE/ES optimization. - -Note that the requirements of O1 interface for E2 nodes are under the scope of WG10. - -##### 4) O-RU: - -- Report EC and EE related information via open FH M-plane interface to O-DU. -- Support actions required to perform spatial and power domain optimization for EE/ES optimization. - -Note that the requirements for O-RU and open FH are under the scope of WG4. - -##### 5) Near- RT RIC: - -- a) Collect measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports, Rel-18 and pre-R-18 supported UE information) from E2 nodes. -- b) (Optionally) Receive EE/ES AI/ML model for deployment via O1 or O2 interface. -- c) Receive EE/ES related policies via A1 interface for consideration during optimization. -- d) Analyse the received data from E2 nodes and perform AI/ML model inference to determine spatial and power domain based EE/ES optimization. -- e) Provide policies or required information to E2 node (O-CU) via E2 to trigger actions for EE/ES optimization. - -Note that the requirements for Near-RT RIC are under the scope of WG3. - -#### 4.8.5.3 Solution - -##### 4.8.5.3.1 A1 policy-based spatial and power domain optimization - -In this solution, decision making, potentially using AI/ML model inference, is done at Near-RT RIC. While AI/ML model training might be hosted in Non-RT or Near-RT RIC. - -The context of the A1 policy based spatial and power domain optimization for energy saving is captured in table 4.8.5.3.1-1. - -**Table 4.8.5.3.1-1: A1 policy-based spatial and power domain optimization** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | A1 policy-based guidance for spatial and power domain energy saving optimization in the network. | | -| Actors and Roles | SMO/Non-RT RIC framework: A1 & O1 termination.
rApp: Provides policy for cell power and spatial domain optimization.
E2 node(s): Enforces mechanism for spatial and power domain optimization on O-RU based on E2 controls or policies.
Near-RT RIC: Spatial and power domain optimization energy savings decision making. | | -| Assumptions | O1 interface connectivity is established between SMO and E2 nodes.
R1 interface connectivity is established.
Open FH M-plane interface is established between O-DU and O-RU.
E2 interface connectivity is established between E2 node and Near-RT RIC.
A1 interface is established between Non-RT RIC and Near-RT RIC.
Network is operational. | | -| Pre-conditions | Operator has set the targets for energy saving in the Non-RT RIC. | | -| Begins when | Operator enables the optimization rApp along with initial ML model for spatial and power domain optimization energy saving and E2 node(s) and O-RU(s) become operational.
See NOTE. | | - -| Use Case Stage | Evolution / Specification | <> | -|----------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 1 (M) | rApp requests to collect necessary configurations, performance indicators, and measurement data towards SMO/Non-RT RIC framework over R1 interface.

Configurations may contain data related to UE capability to support 3GPP Rel-18, which rApp needs to know before formulating A1 policies for spatial and power domain optimization. | | -| Step 2 (M) | SMO/Non-RT RIC framework requests data collection towards E2 node(s) and O-RU(s) (via E2 node(s)) over O1 interface. | | -| Step 3 (M) | O-DU upon receiving request from SMO/Non-RT RIC framework requests and collect necessary data from O-RU(s) over open FH M-plane interface. | | -| Step 4 (M) | E2 node(s) sends the configuration data, configured measurement data to SMO/Non-RT RIC framework periodically or event based. | | -| Step 5 (M) | rApp collects the configuration data, collected measurement data for processing. | | -| Step 6 (M) | rApp to trigger EE/ES optimization through A1 policy to prepare and execute spatial and power domain optimization. | | -| Step 7 (M) | SMO/Non-RT RIC framework receives policy from rApp and forwards it towards Near-RT RIC via A1 interface. | | -| Step 8 (M) | Near-RT RIC provides A1 policy response to SMO/Non-RT RIC framework. | | -| Step 9 (M) | SMO/Non-RT RIC framework informs rApp about A1 policy feedback. | | -| Step 10 (M) | rApp monitors energy saving objectives as per A1 policy. | | -| Step 11 (M) | The Near-RT RIC receives the policy from the Non-RT RIC over the A1 interface. It then interprets the policy to determine the required data collection and E2 control/policies. | | -| Step 12 (M) | Inferencing AI/ML model to evaluate & generate E2 control or policies for spatial and power domain optimization. | | -| Step 13 (M) | Near-RT RIC to notify Non-RT RIC if any change in the state of policy. | | -| Step 14 (M) | SMO/Non-RT RIC framework forwards notification received from Near-RT RIC to rApp. | | -| Step 15 (O) | If energy saving objectives are not achieved rApp may decide to initiate fallback mechanism for example, updating or deleting A1 policy for spatial and power domain optimization. | | -| Step 16 (O) | SMO/Non-RT RIC framework send update or delete A1 policies to Near-RT RIC. | | -| Ends when | E2 node(s) becomes non-operational or when the operator disables the rApp. | | -| Exceptions | N/A | | -| Post Conditions | rApp continues monitoring of energy saving at E2 node(s) and O-RU.

E2 node(s) and O-RU(s) operate using the newly deployed parameters/models and state (off/on). | | -| NOTE: Operator can set policies through rApp or allow AI/ML model in rApp to infer policies. | | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -Skin rose - -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber - -Box "Service Management and Orchestration Framework" #gold -Box #lightgrey -Participant "Energy Saving\nrApp" as ESRAPP - -End Box - -Participant "SMO / Non-RT RIC\nFWK" as NRTF - -End box - -Box " O-RAN Nodes" #lightpink - Participant "Near-RT RIC" as NeRT - Participant "E2-Node(s)" as E2NODES - Participant "O-RU(s) " as ORUs - -End box - -group Data Collection - ESRAPP -> NRTF : <> Data collection request - NRTF -> E2NODES : <> Data collection request - E2NODES <-> ORUs : Data collection request - E2NODES -> NRTF : <> Data Collection - NRTF -> ESRAPP : <> Data Collection -End - -group Data Analysis /AI/ML Model Selection and Training - -Note over ESRAPP , NeRT - -rApp/Non-RT RIC performs AI/ML model selection, retraining, and deployment decisions. - -For a model deployment request, the rApp provides the rAppId, AI/ML model identifier, and target deployment location - -End note - -end - -``` - -``` - -group Actor Decision Making - ESrAPP -> NRTF : <> Create A1 Policy - NRTF -> NeRT : <> Policy to prepare and execute \nfor spatial and power -domain optimization - NeRT -> NRTF : <> A1 Policy create Response - NRTF -> ESrAPP : <> A1 Policy create Response - ESrAPP -> ESrAPP : Monitor Energy saving objectives - NeRT -> NeRT : Interpreting A1 Policy - -group E2 Data Collection -Note over NeRT , ORUs -Near-RT RIC to trigger E2 data collection from E2 Nodes and O-RU via O-DU -End note -end - - NeRT -> NeRT : AI/ML Model Inference\n to Evaluate E2 Control/Policy - -group E2 Control /Policy -Note over NeRT , ORUs -Near-RT RIC to trigger E2 Control /Policy towards E2 Nodes and O-RU via O-DU -End note -end - -group Opt - NeRT -> NRTF : <> Notify A1 Policy Staus - NRTF -> ESrAPP : <> Notify A1 Policy Staus -end - -group Opt - ESrAPP -> NRTF : <> Update or Delete A1 Policy - NRTF -> NeRT : <> Update or Delete Policy -end - -end - -@enduml - -``` - -The flow diagram of A1 interface-based mechanism for spatial and power domain optimization for energy saving is shown in figure 4.8.5.3.1-1. - -![Sequence diagram showing the flow of an A1 interface-based mechanism for spatial and power domain optimization for energy saving. The diagram is divided into two main lifelines: 'Service Management and Orchestration Framework' (left) and 'O-RAN Nodes' (right). The O-RAN Nodes lifeline includes Near-RT RIC, E2-Node(s), and O-RU(s). The process involves Data Collection, Data Analysis/AI/ML Model Selection and Training, Actor Decision Making, E2 Data Collection, and E2 Control/Policy. The Energy Saving rApp initiates the process by sending a Data collection request to the SMO/Non-RT RIC FWK Function, which then triggers a chain of requests through the Near-RT RIC to the E2-Node(s) and O-RU(s). The SMO/Non-RT RIC FWK Function performs AI/ML model selection, retraining, and deployment decisions. The Near-RT RIC then creates an A1 Policy and sends it to the SMO/Non-RT RIC FWK Function, which in turn sends it to the Energy Saving rApp. The Energy Saving rApp monitors energy saving objectives and sends a response to the SMO/Non-RT RIC FWK Function. The Near-RT RIC interprets the A1 Policy and triggers E2 data collection from the E2-Node(s) and O-RU(s) via the O-DU. The Near-RT RIC then performs AI/ML Model Inference to evaluate the E2 Control/Policy. The Near-RT RIC then triggers E2 Control/Policy towards the E2-Node(s) and O-RU(s) via the O-DU. The SMO/Non-RT RIC FWK Function sends a notification of the A1 Policy status to the Energy Saving rApp. The Energy Saving rApp then sends an update or delete request to the SMO/Non-RT RIC FWK Function, which in turn sends an update or delete request to the Near-RT RIC.](00a0b3a0485d8e735df9cb73dbdf36d6_img.jpg) - -**Service Management and Orchestration Framework** - -Energy Saving rApp | SMO / Non-RT RIC FWK Function - -**O-RAN Nodes** - -Near-RT RIC | E2-Node(s) | O-RU(s) - -**Data Collection** - -- 1 «R1» Data collection request (rApp to SMO) -- 2 «O1» Data collection request (SMO to Near-RT RIC) -- 3 Data collection request (Near-RT RIC to E2-Node(s) and O-RU(s)) -- 4 «O1» Data Collection (E2-Node(s) and O-RU(s) to Near-RT RIC) -- 5 «R1» Data Collection (Near-RT RIC to SMO) - -**Data Analysis /AI/ML Model Selection and Training** - -rApp/Non-RT RIC performs AI/ML model selection, retraining, and deployment decisions. -For a model deployment request, the rApp provides the rAppId, AI/ML model identifier, and target deployment location - -**Actor Decision Making** - -- 6 «R1» Create A1 Policy (rApp to SMO) -- 7 «A1» Policy to prepare and execute for spatial and power domain optimization (SMO to Near-RT RIC) -- 8 «A1» A1 Policy create Response (Near-RT RIC to SMO) -- 9 «R1» A1 Policy create Response (SMO to rApp) -- 10 Monitor Energy saving objectives (rApp) -- 11 Interpreting A1 Policy (Near-RT RIC) - -**E2 Data Collection** - -Near-RT RIC to trigger E2 data collection from E2 Nodes and O-RU via O-DU - -12 AI/ML Model Inference to Evaluate E2 Control/Policy (Near-RT RIC) - -**E2 Control /Policy** - -Near-RT RIC to trigger E2 Control /Policy towards E2 Nodes and O-RU via O-DU - -**Opt** - -- 13 «A1» Notify A1 Policy Status (Near-RT RIC to SMO) -- 14 «R1» Notify A1 Policy Status (SMO to rApp) - -**Opt** - -- 15 «R1» Update or Delete A1 Policy (rApp to SMO) -- 16 «A1» Update or Delete Policy (SMO to Near-RT RIC) - -Sequence diagram showing the flow of an A1 interface-based mechanism for spatial and power domain optimization for energy saving. The diagram is divided into two main lifelines: 'Service Management and Orchestration Framework' (left) and 'O-RAN Nodes' (right). The O-RAN Nodes lifeline includes Near-RT RIC, E2-Node(s), and O-RU(s). The process involves Data Collection, Data Analysis/AI/ML Model Selection and Training, Actor Decision Making, E2 Data Collection, and E2 Control/Policy. The Energy Saving rApp initiates the process by sending a Data collection request to the SMO/Non-RT RIC FWK Function, which then triggers a chain of requests through the Near-RT RIC to the E2-Node(s) and O-RU(s). The SMO/Non-RT RIC FWK Function performs AI/ML model selection, retraining, and deployment decisions. The Near-RT RIC then creates an A1 Policy and sends it to the SMO/Non-RT RIC FWK Function, which in turn sends it to the Energy Saving rApp. The Energy Saving rApp monitors energy saving objectives and sends a response to the SMO/Non-RT RIC FWK Function. The Near-RT RIC interprets the A1 Policy and triggers E2 data collection from the E2-Node(s) and O-RU(s) via the O-DU. The Near-RT RIC then performs AI/ML Model Inference to evaluate the E2 Control/Policy. The Near-RT RIC then triggers E2 Control/Policy towards the E2-Node(s) and O-RU(s) via the O-DU. The SMO/Non-RT RIC FWK Function sends a notification of the A1 Policy status to the Energy Saving rApp. The Energy Saving rApp then sends an update or delete request to the SMO/Non-RT RIC FWK Function, which in turn sends an update or delete request to the Near-RT RIC. - -Figure 4.8.5.3.1-1: Flow diagram of A1 interface-based mechanism for spatial and power domain optimization for energy saving - -#### 4.8.5.4 Required data - -This sub-clause contains the input and output data of model training and inference for energy saving using spatial and power domain optimization. - -##### 4.8.5.4.1 Input data - -The measurement input data is used in model training and inference. They can include the following measurements to monitor energy consumption and energy efficiency of E2 node(s) and O-RU(s): - -- DL PDCP SDU data volume per interface (data volume in DL delivered per PLMN, per QoS level, per slice, per interface ((from O-CU-UP to O-DU over F1-U, to external O-CU-UP over Xn-U and to external O-eNB over X2-U)) (as specified in 3GPP TS 28.552 [5], clause 5.1.3.6.2.3) - -- b) UL PDCP SDU data volume per interface (data volume in UL delivered per PLMN, per QoS level, per slice, per interface ((from O-DU to O-CU-UP over F1-U, to external O-CU-UP over Xn-U and to external O-eNB over X2-U)) (as specified in 3GPP TS 28.552 [5], clause 5.1.3.6.2.4) -- c) RSRQ measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.31) -- d) RSRP measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.22) -- e) SINR measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.32) -- f) PNF Energy consumption (as specified in 3GPP TS 28.552 [5], clause 5.1.1.19.3) -- g) Power consumed by physical network function & its components (as specified in 3GPP TS 28.552 [5], clause 5.1.1.19.2 and in MP [10], clauses B.1, B.5) -- h) Transmit power (as specified in MP [10], clauses B.1, B.2.1) -- i) M1 MDT measurement in trace record for immediate MDT measurements (as specified in 3GPP TS 32.423 [11], clause 4.34.1) -- j) UE location in trace record for UE location information (as specified in 3GPP TS 32.423 [11], clause 4.34.2) -- k) UE capability information related to Rel-18 Spatial and Power domain energy savings, including the following capability indicators: powerAdaptation-CSI-Feedback-r18, powerAdaptation-CSI-FeedbackAperiodic-r18, powerAdaptation-CSI-FeedbackPUCCH-r18, powerAdaptation-CSI-FeedbackPUSCH-r18, spatialAdaptation-CSI-Feedback-r18, spatialAdaptation-CSI-FeedbackAperiodic-r18, spatialAdaptation-CSI-FeedbackPUCCH-r18, spatialAdaptation-CSI-FeedbackPUSCH-r18 (as specified in 3GPP TS 38.306 [22], clause 4.2.7.2) -- l) Handover Measurement Data (as specified 3GPP TS 28.552 [5], clauses 5.1.1.6.5, 5.1.3.7) - -##### 4.8.5.4.2 Output data - -rApps to deliver energy saving & energy efficiency A1 policies for mechanism for spatial and power domain optimization through R1 interface. - -### 4.8.6 SSB-less SCell optimization for inter-band CA (3GPP Rel-18) - -#### 4.8.6.1 Background and goal of the use case - -3GPP Rel-18 [21], clause 15.4.2.6 introduces the concept of SSB-less secondary cell (SCell) activation for carrier aggregation, which allows efficient use of secondary carriers without needing constant synchronization signals. This enhances spectral efficiency and data throughput for users with high demand, without burdening the network with unnecessary signaling. The SSB-less SCell operation for inter-band CA is designed to enhance energy efficiency while maintaining data throughput in carrier aggregation scenarios. By operating without the need for continuous synchronization signal block (SSB) transmissions, the network can reduce power consumption on secondary cells, particularly in periods of lower traffic demand. The primary goal of this use case is to maximize energy savings without degrading user experience by intelligently enabling and disabling SCells based on real-time traffic demand. - -The SSB-less SCell feature, as specified in [20], enables User Equipment (UE) to obtain a timing reference from a serving cell other than its primary serving cell, even when Synchronization Signal Block (SSB) or Secondary Management and Control Channel (SMTC) configurations are unavailable. Within the O-RAN framework, this capability can be enhanced through Non-RT RIC-driven predictive analytics, which anticipate optimal conditions for activating SSB-less SCells. By pre-configuring network parameters, the Non-RT RIC ensures seamless SCell switching and synchronization without relying on SSB transmissions, significantly reducing energy consumption. Meanwhile, the Near-RT RIC, leveraging its near real-time decision-making capabilities, dynamically adjusts SCell parameters based on A1 policies, ensuring efficient and adaptive network operation. - -Based on this analysis, the Non-RT RIC generates A1 policies that include, but are not limited to, the following: - -**Activate SSB-less SCells in appropriate cells** to improve spectral efficiency while minimizing unnecessary synchronization transmissions, reducing power consumption during low-traffic periods. - -**Steer Rel-18 UEs towards SSB-less SCells** where energy savings can be maximized, ensuring that secondary cells operate efficiently without impacting service quality. - -**Bar non-Rel-18 UEs from SSB-less optimized SCells** to maintain seamless operation and prevent unnecessary fallback to legacy synchronization mechanisms, maximizing energy efficiency. - -#### 4.8.6.2 Entities/resources involved in the use case - -##### 1) SMO/Non-RT RIC framework: - -- Collect the configurations, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) from E2 node(s) and trace records (e.g., per-UE measurement metrics, location information, Rel-18 and pre-Rel-18 supported UE information) through O1 Interface, for the purpose of decision making. -- Transfer collected data towards rApp. It is assumed that configurations, performance indicators and measurement reports collected from the O-DU contain the related information for the corresponding O-RU(s). -- Create A1 Policies for Near-RT RIC based on rApp request to optimize SSB-less SCell energy savings via the A1 interface. - -##### 2) rApps: - -- Collect the necessary configurations, performance indicators, and measurement reports from SMO/Non-RT RIC framework, for the purpose of training and execution of relevant AI/ML models. -- (Optionally) Retrain, update, configure EE/ES AI/ML model. -- Infer an optimized A1 policy for SSB-less SCell based optimization on the data collected using R1 interface. - -##### 3) E2 node: - -- Report cell configuration, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports, trace records such as per-UE measurement metrics, location information and Rel-18 and pre-Rel-18 supported UE information) to SMO via O1 interface. -- Report measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) to Near-RT RIC via E2 interface. -- Support actions required to perform SSB-less SCell based optimization for EE/ES optimization. - -Note that the requirements of O1 interface for E2 nodes are under the scope of WG10. - -##### 4) O-RU : - -- Report EC and EE related information via open FH M-Plane interface to O-DU. -- Support actions required to perform SSB-less SCell based optimization for EE/ES optimization. - -Note that the requirements for O-RU and open FH are under the scope of WG4. - -##### 5) Near- RT RIC: - -- Collect measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports, Rel-18 and pre-Rel-18 supported UE information) from E2 nodes. -- (Optionally) Receive EE/ES AI/ML model for deployment via O1 or O2 interface. -- Receive EE/ES related policies via A1 interface for consideration during optimization. -- Analyse the received data from E2 nodes and perform AI/ML model inference to determine SSB-less SCell based EE/ES Optimization (i.e., SSB-less SCell to be activated for certain time and cells) considering the optimization targets/policies. -- Provide policies or required information to E2 node (O-CU) via E2 to trigger actions for EE/ES optimization. - -Note that the requirements for Near-RT RIC are under the scope of WG3. - -#### 4.8.6.3 Solution - -##### 4.8.6.3.1 A1 policy-based SSB-less SCell optimization for energy saving - -In this solution, decision making, potentially using AI/ML model inference, is done at Near-RT RIC. While AI/ML model training might be hosted in Non-RT or Near-RT RIC. - -The context of the A1 policy-based SSB-less SCell optimization for energy saving is captured in table 4.8.6.3.1-1. - -**Table 4.8.6.3.1-1: A1 policy-based SSB-less SCell optimization for energy saving** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | A1 policy-based guidance for performing SSB-less S-Cell optimization energy saving in the network. | | -| Actors and Roles | SMO/Non-RT RIC framework:A1 & O1 termination.
rApp: SSB-less SCell optimization.
E2 node(s): Enforces SSB-less SCell optimization on O-RU based on E2 policy or control.
Near-RT RIC: SSB-less SCell energy savings decision making function. | | -| Assumptions | O1 interface connectivity is established between SMO and E2 nodes.
R1 interface connectivity is established.
Open FH M-plane interface is established between O-DU and O-RU.
E2 interface connectivity is established between E2 node and Near-RT RIC.
A1 interface is established between Non-RT RIC and Near-RT RIC.
Network is operational. | | -| Pre-conditions | Operator has set the targets for energy saving in the Non-RT RIC. | | -| Begins when | Operator enables the rApp along with initial ML model for SSB-less SCell energy saving and E2 node(s) and O-RU(s) become operational.
See NOTE. | | -| Step 1 (M) | rApp requests to collect necessary configurations, performance indicators, and measurement data towards SMO/Non-RT RIC framework over R1 interface.
Configurations may contain data related to UE capability to support 3GPP Rel-18, which rApp needs to know before formulating A1 policies for SSB-less SCell optimization. | | -| Step 2 (M) | SMO/Non-RT RIC framework requests data collection towards E2 node(s) and O-RU(s) (via E2 node(s)) over O1 interface. | | -| Step 3 (M) | E2 node(s) upon receiving request from SMO/Non-RT RIC framework requests and collect necessary data form O-RU(s). | | -| Step 4 (M) | E2 node(s) sends the configuration data, configured measurement data to SMO/Non-RT RIC framework periodically or event based. | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 5 (M) | rApp collects the configuration data, collected measurement data for processing. | | -| Step 6 (M) | rApp to trigger EE/ES optimization through A1 policy to prepare and execute SSB-less SCell optimization. | | -| Step 7 (M) | Non-RT RIC framework receives policy from rApp and forwards it towards Near-RT RIC via A1 interface. | | -| Step 8 (M) | Near-RT RIC provides A1 policy response to SMO/Non-RT RIC framework. | | -| Step 9 (M) | SMO/Non-RT RIC framework informs rApp about A1 policy feedback. | | -| Step 10 (M) | rApp monitors energy saving objectives as per A1 policy. | | -| Step 11 (M) | The Near-RT RIC receives the policy from the Non-RT RIC over the A1 interface. It then interprets the policy to determine the required data collection and E2 control/policies. | | -| Step 12 (M) | Inferencing AI/ML model to evaluate & generate E2 control or policies for SSB-less SCell optimization. | | -| Step 13 (M) | Near-RT RIC to notify Non-RT RIC if any change in the state of policy. | | -| Step 14 (M) | SMO/Non-RT RIC framework forwards notification received from Near-RT RIC to rApp. | | -| Step 15 (O) | If energy saving objectives are not achieved rApp may decide to initiate fallback mechanism for example, updating or deleting A1 policy for SSB-less SCell optimization. | | -| Step 16 (O) | SMO/Non-RT RIC framework send update or delete A1 policies to Near-RT RIC. | | -| Ends when | E2 node(s) becomes non-operational or when the operator disables the rApp. | | -| Exceptions | N/A | | -| Post Conditions | rApp continues monitoring of energy saving at E2 node(s) and O-RU.
E2 node(s) and O-RU(s) operate using the newly deployed parameters and state (off/on). | | - -NOTE: Operator can set policies through rApp or allow AI/ML model in rApp to infer policies. - -``` -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -Skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -``` - -``` - -Box "Service Management and Orchestration Framework" #gold - -Box #lightgrey -Participant "Energy Saving\nrApp" as ESrAPP - -End Box - -Participant "SMO / Non-RT RIC\nFWK " as NRTF - -End box - -Box " O-RAN Nodes" #lightpink - Participant "Near-RT RIC" as NeRT - Participant "E2-Node(s)" as E2NODES - Participant "O-RU(s) " as ORUs - -End box - -group Data Collection - ESrAPP -> NRTF : <> Data collection request - NRTF -> E2NODES : <> Data collection request - E2NODES <-> ORUs : Data collection request - E2NODES -> NRTF : <> Data Collection - NRTF -> ESrAPP : <> Data Collection - -End - -group Data Analysis /AI/ML Model Selection and Training - -Note over ESrAPP , NeRT -rApp/Non-RT RIC performs AI/ML model selection, retraining, and deployment decisions. - -For a model deployment request, the rApp provides the rAppId, AI/ML model identifier, and target deployment location - -End note - -End - -group Actor Decision Making - ESrAPP -> NRTF : <> Create AI Policy - NRTF -> NeRT : <> Policy to prepare and execute \nfor SSB-less-S-Cell Operation - NeRT -> NRTF : <> AI Policy create Response - NRTF -> ESrAPP : <> AI Policy create Response - ESrAPP -> ESrAPP : Monitor Energy saving objectives - NeRT -> NeRT : Interpreting AI Policy - -group E2 Data Collection - -Note over NeRT , ORUs - -``` - -``` - -Near-RT RIC to trigger E2 data collection from E2 Nodes and O-RU via O-DU - -End note - -end - - NeRT -> NeRT : AI/ML Model Inference\n to Evaluate E2 Control/Policy -group E2 Control /Policy -Note over NeRT , ORUs -Near-RT RIC to trigger E2 Control /Policy towards E2 Nodes -End note - -end - -group Opt - NeRT -> NRTF : <> Notify A1 Policy Status - NRTF -> ESrAPP : <> Notify A1 Policy Status -end - -group Opt - ESrAPP -> NRTF : <> Update or Delete A1 Policy - NRTF -> NeRT : <> Update or Delete Policy -end - -end - -@enduml - -``` - -The flow diagram of A1 interface based SSB-less SCell optimization for energy saving is shown in figure 4.8.6.3.1-1. - -![Sequence diagram showing the flow of A1 interface based SSB-less SCell optimization for energy saving. Lifelines: Energy Saving rApp, SMO / Non-RT RIC FWK, Near-RT RIC, E2-Node(s), O-RU(s). The process includes Data Collection, Data Analysis / AI/ML Model Selection and Training, Actor Decision Making, E2 Data Collection, and E2 Control / Policy.](53499879d98034410ecba2c386c58f0c_img.jpg) - -``` - -sequenceDiagram - participant rApp as Energy Saving rApp - participant FWK as SMO / Non-RT RIC FWK - participant RIC as Near-RT RIC - participant Node as E2-Node(s) - participant RU as O-RU(s) - - Note left of rApp: Service Management and Orchestration Framework - Note right of Node: O-RAN Nodes - - Note over rApp, FWK: Data Collection - rApp->>FWK: 1 «R1» Data collection request - FWK->>Node: 2 «O1» Data collection request - Node->>RU: 3 Data collection request - RU-->>Node: 4 «O1» Data Collection - Node-->>FWK: 5 «R1» Data Collection - - Note over rApp, FWK: Data Analysis /AI/ML Model Selection and Training - Note right of FWK: rApp/Non-RT RIC performs AI/ML model selection, retraining, and deployment decisions. -For a model deployment request, the rApp provides the rAppId, AI/ML model identifier, and target deployment location - - Note over rApp, FWK: Actor Decision Making - rApp->>FWK: 6 «R1» Create A1 Policy - FWK->>RIC: 7 «A1» Policy to prepare and execute for SSB-less-S-Cell Operation - RIC-->>FWK: 8 «A1» A1 Policy create Response - FWK-->>rApp: 9 «R1» A1 Policy create Response - rApp->>rApp: 10 Monitor Energy saving objectives - - Note over RIC: E2 Data Collection - Note right of RIC: Near-RT RIC to trigger E2 data collection from E2 Nodes and O-RU via O-DU - RIC->>Node: 11 Interpreting A1 Policy - Note over RIC: E2 Control /Policy - Note right of RIC: Near-RT RIC to trigger E2 Control /Policy towards E2 Nodes - RIC->>Node: 12 AI/ML Model Inference to Evaluate E2 Control/Policy - - Note over rApp, FWK: Opt - FWK-->>RIC: 13 «A1» Notify A1 Policy Status - RIC-->>FWK: 14 «R1» Notify A1 Policy Status - - Note over rApp, FWK: Opt - rApp->>FWK: 15 «R1» Update or Delete A1 Policy - FWK->>RIC: 16 «A1» Update or Delete Policy - -``` - -Sequence diagram showing the flow of A1 interface based SSB-less SCell optimization for energy saving. Lifelines: Energy Saving rApp, SMO / Non-RT RIC FWK, Near-RT RIC, E2-Node(s), O-RU(s). The process includes Data Collection, Data Analysis / AI/ML Model Selection and Training, Actor Decision Making, E2 Data Collection, and E2 Control / Policy. - -Figure 4.8.6.3.1-1: Flow diagram of A1 interface based SSB-less SCell optimization for energy saving - -#### 4.8.6.4 Required data - -This sub-clause contains the input and output data of model training and inference for energy saving using SSB-less SCell optimization. - -##### 4.8.6.4.1 Input data - -The measurement input data is used in model training and inference. They can include the following measurements to monitor energy consumption and energy efficiency of E2 node(s) and O-RU(s): - -- a) DL PDCP SDU data volume per interface (data volume in DL delivered per PLMN, per QoS level, per slice, per interface ((from O-CU-UP to O-DU over F1-U, to external O-CU-UP over Xn-U and to external O-eNB over X2-U)) (as specified in 3GPP TS 28.552 [5], clause 5.1.3.6.2.3) - -- b) UL PDCP SDU data volume per interface (data volume in UL delivered per PLMN, per QoS level, per slice, per interface ((from O-DU to O-CU-UP over F1-U, to external O-CU-UP over Xn-U and to external O-eNB over X2-U)) (as specified in 3GPP TS 28.552 [5], clause 5.1.3.6.2.4) -- c) RSRQ measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.31) -- d) RSRP measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.22) -- e) SINR measurement per SSB per cell (as specified in 3GPP TS 28.552 [5], clause 5.1.1.32) -- f) PNF Energy consumption (as specified in 3GPP TS 28.552 [5], clause 5.1.1.19.3) -- g) Power consumed by physical network function & its components (as specified in 3GPP TS 28.552 [5], clause 5.1.1.19.2 and in MP [10], clauses B.1, B.5) -- h) Transmit power (as specified in MP [10], clauses B.1, B.2.1) -- i) M1 MDT measurement in trace record for immediate MDT measurements including RSRP, RSRQ, SINR (as specified in 3GPP TS 32.423 [11], clause 4.34.1) -- j) UE location in trace record for UE location information (as specified in 3GPP TS 32.423 [11], clause 4.34.2) -- k) UE capability information to support the SSB-less SCell inter-band carrier aggregation operation; scellWithoutSSB, scellWithoutSSB-InterBandCA-r18 (as specified in 3GPP TS 38.306 [22], clause 4.2.7.2) -- l) DL cell PDCP SDU data volume on X2 interface (as specified in 3GPP TS 28.552 [5], clause 5.1.2.1.1.2) and UL Cell PDCP SDU Data Volume on Xn Interface (as specified in 3GPP TS 28.552 [5], clause 5.1.2.1.2.3) - -##### 4.8.6.4.2 Output data - -rApps to deliver energy saving & energy efficiency A1 policies for SSB-less SCell optimization through R1 interface. - -### 4.8.7 PA power optimization for O-RU energy saving - -#### 4.8.7.1 Background and goal of the use case - -The O-RU energy saving could be achieved by optimizing its Power Amplifier (PA) operating region according to the traffic scheduling requirements, to reduce the O-RU power consumption. To facilitate this, the SMO (Non-RT RIC) framework analyses various network data and KPIs to generate A1 policies and provide them to Near-RT RIC via A1 interface. The Near-RT RIC, leveraging its near-real-time decision-making capabilities, prepare E2 policies or configuration changes dynamically and deliver them to the E2 node (i.e., O-DU) via E2 interface. The O-DU analyses the E2 policies or applies the configuration changes provided by Near-RT RIC. Once the conditions mentioned in the E2 policy are satisfied or based on requested configuration changes, the O-DU configures the maximum output power of the O-RU via fronthaul M-plane or C-plane interface. The O-RU subsequently optimizes its power amplifier parameters according to the configured maximum output power. This could result in a reduction of PA power consumption, thereby achieving energy saving in O-RU and enhancing the overall energy efficiency of the O-RAN network. - -#### 4.8.7.2 Entities/resources involved in the use case - -- 1) SMO/Non-RT RIC framework: - - a) Collect the configurations, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) from E2 node(s) through O1 interface, for the purpose of decision making. - - b) Transfer collected data towards rApp. It is assumed that configurations, performance indicators and measurement reports collected from the O-DU contain the related information for the corresponding O-RU(s). - - c) Create A1 policies for Near-RT RIC based on rApp request to optimize O-RU power amplifier to achieve energy savings via the A1 interface. - -##### 2) rApps: - -- a) Collect the necessary configurations, performance indicators, and measurement reports from SMO/Non-RT RIC framework, for the purpose of training and execution of relevant AI/ML models. -- b) (Optionally) Retrain, update, configure EE/ES AI/ML model. -- c) Infer an optimized A1 policy for O-RU PA power optimization based on the data collected using R1 interface. - -##### 3) E2 node: - -- a) Report cell configuration, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports to SMO via O1 interface. -- b) Report measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) to Near-RT RIC via E2 interface. -- c) Support actions required to perform O-RU PA power optimization for EE/ES optimization. - -Note that the requirements of O1 interface for E2 nodes are under the scope of WG10. - -##### 4) O-RU: - -- a) Report EC and EE related information via open FH M-plane interface to O-DU. -- b) Support actions required to perform PA power optimization for EE/ES optimization. - -Note that the requirements for O-RU and open FH are under the scope of WG4. - -##### 5) Near- RT RIC: - -- a) Collect measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports from E2 nodes via E2 interface. -- b) (Optionally) Receive EE/ES AI/ML model for deployment via O1 or O2 interface. -- c) Receive EE/ES related policies via A1 interface for consideration during optimization. -- d) Analyse the received data from E2 nodes and perform AI/ML model inference to determine O-RU PA optimization (i.e., maximum Tx output power to be configured in a specific O-RU) considering the optimization targets/policies. -- e) Provide policies or required information to E2 node (O-CU) via E2 to trigger actions for EE/ES optimization. - -Note that the requirements for Near-RT RIC are under the scope of WG3. - -#### 4.8.7.3 Solution - -##### 4.8.7.3.1 A1 policy-based PA power optimization for energy saving - -In this solution, decision making, potentially using AI/ML model inference, is done at Near-RT RIC. While AI/ML model training might be hosted in Non-RT or Near-RT RIC. - -The context of the A1 policy-based PA power optimization for energy saving is captured in table 4.8.7.3.1-1. - -**Table 4.8.7.3.1-1: A1 policy-based PA power optimization for energy saving** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|---------------------------------------------------------------------------------------------|-------------------------| -| Goal | A1 policy-based guidance for performing PA power optimization energy saving in the network. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Actors and Roles | SMO/Non-RT RIC framework: A1 & O1 termination.
rApp: PA power optimization.
E2 node(s): Enforces PA power optimization on O-RU based on E2 policy or control.
Near-RT RIC: PA power optimization-based energy savings decision making function. | | -| Assumptions | O1 interface connectivity is established between SMO and E2 nodes.
R1 interface connectivity is established.
Open FH M-plane interface is established between O-DU and O-RU.
E2 interface connectivity is established between E2 node and Near-RT RIC.
A1 interface is established between Non-RT RIC and Near-RT RIC.
Network is operational. | | -| Pre-conditions | Operator has set the targets for energy saving in the Non-RT RIC. | | -| Begins when | Operator enables the rApp along with initial ML model for PA power optimization-based energy saving and E2 node(s) and O-RU(s) become operational.
See NOTE. | | -| Step 1 (M) | rApp requests to collect necessary configurations, performance indicators, and measurement data towards SMO/Non-RT RIC framework over R1 interface.
Configurations may contain data related to maximum Tx output power, which rApp needs to know before formulating A1 policy for O-RU PA power optimization. | | -| Step 2 (M) | SMO/Non-RT RIC framework requests data collection towards E2 node(s) and O-RU(s) (via E2 node(s)) over O1 interface. | | -| Step 3 (M) | O-DU upon receiving request from SMO/Non-RT RIC framework requests and collect necessary data from O-RU(s). | | -| Step 4 (M) | E2 node(s) sends the configuration data, configured measurement data to SMO/Non-RT RIC framework periodically or event based. | | -| Step 5 (M) | rApp collects the configuration data, collected measurement data for processing. | | -| Step 6 (M) | rApp to trigger EE/ES optimization through A1 policy to prepare and execute PA power optimization. | | -| Step 7 (M) | Non-RT RIC framework receives policy from rApp and forwards it towards Near-RT RIC via A1 interface. | | -| Step 8 (M) | Near-RT RIC provides A1 policy response to SMO/Non-RT RIC framework. | | -| Step 9 (M) | SMO/Non-RT RIC framework informs rApp about A1 policy feedback. | | -| Step 10 (M) | rApp monitors energy saving objectives as per A1 policy. | | -| Step 11 (M) | The Near-RT RIC receives the policy from the Non-RT RIC over the A1 interface.
It then interprets the policy to determine the required data collection and E2 control/policies. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 12 (M) | Inferencing AI/ML model to evaluate & generate E2 control or policies for PA power optimization. | | -| Step 13 (M) | Near-RT RIC to notify Non-RT RIC if any change in the state of policy. | | -| Step 14 (M) | SMO/Non-RT RIC framework forwards notification received from Near-RT RIC to rApp. | | -| Step 15 (O) | If energy saving objectives are not achieved rApp may decide to initiate fallback mechanism for example, updating or deleting A1 policy for O-RU PA power optimization. | | -| Step 16 (O) | SMO/Non-RT RIC framework send update or delete A1 policies to Near-RT RIC | | -| Ends when | E2 node(s) becomes non-operational or when the operator disables the rApp. | | -| Exceptions | N/A | | -| Post Conditions | rApp continues monitoring of energy saving at E2 node(s) and O-RU.
E2 node(s) and O-RU(s) operate using the newly deployed parameters and state (off/on). | | - -NOTE: Operator can set policies through rApp or allow AI/ML model in rApp to infer policies. - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -Skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber -Box "Service Management and Orchestration Framework" #gold -Box #lightgrey -Participant "Energy Saving\rApp" as ESRAPP -End Box -Participant "SMO / Non-RT RIC\rFWK " as NRTF -End box -Box " O-RAN Nodes" #lightpink -Participant "Near-RT RIC" as NeRT - -``` - -``` - -Participant "E2-Node(s)" as E2NODES -Participant "O-RU(s) " as ORUs - -End box - -group Data Collection - ESrAPP -> NRTF : <> Data collection request - NRTF -> E2NODES : <> Data collection request - E2NODES <-> ORUs : Data collection request - E2NODES -> NRTF : <> Data Collection - NRTF -> ESrAPP : <> Data Collection -End - -group Data Analysis /AI/ML Model Selection and Training -Note over ESrAPP , NeRT - -rApp/Non-RT RIC performs AI/ML model selection, retraining, and deployment decisions. - -For a model deployment request, the rApp provides the rAppId, AI/ML model identifier, and -target deployment location - -End note - -End - -group Actor Decision Making - ESrAPP -> NRTF : <> Create A1 Policy - NRTF -> NeRT : <> Prepare policy and execute \nfor PA power optimization - NeRT -> NRTF : <> A1 Policy create Response - NRTF -> ESrAPP : <> A1 Policy create Response - ESrAPP -> ESrAPP : Monitor Energy saving objectives - NeRT -> NeRT : Interpreting A1 Policy - -group E2 Data Collection -Note over NeRT , ORUs - -Near-RT RIC to trigger E2 data collection from E2 Nodes and O-RU via O-DU - -End note - -end - - NeRT -> NeRT : AI/ML Model Inference\n to Evaluate E2 Control/Policy - -group E2 Control /Policy -Note over NeRT , ORUs - -Near-RT RIC to trigger E2 Control /Policy towards E2 Nodes - -End note - -end - -group Opt - -``` - -``` -NeRT -> NRTF : <> Notify A1 Policy Status -NRTF -> ESRAPP : <> Notify A1 Policy Status -end -group Opt - ESRAPP -> NRTF : <> Update or Delete A1 Policy - NRTF -> NeRT : <> Update or Delete Policy -end -end -@enduml -``` - -The flow diagram of A1 interface-based O-RU PA optimization for energy saving is shown in figure 4.8.7.3.1-1. - -![Sequence diagram showing the flow of A1 interface-based O-RU PA optimization for energy saving. Lifelines include Energy Saving rApp, SMO / Non-RT RIC FWK, Near-RT RIC, E2-Node(s), and O-RU(s). The process involves Data Collection, Data Analysis / AI/ML Model Selection and Training, and Actor Decision Making phases.](a76fa39f5daf6a026e032495262ed0f6_img.jpg) - -The diagram illustrates the interaction between the Service Management and Orchestration Framework and O-RAN Nodes for energy saving optimization. The sequence of messages is as follows: - -- Data Collection:** - - 1 «R1» Data collection request (Energy Saving rApp to SMO / Non-RT RIC FWK) - - 2 «O1» Data collection request (SMO / Non-RT RIC FWK to E2-Node(s)) - - 3 Data collection request (E2-Node(s) to O-RU(s)) - - 4 «O1» Data Collection (O-RU(s) to E2-Node(s)) - - 5 «R1» Data Collection (E2-Node(s) to SMO / Non-RT RIC FWK) -- Data Analysis /AI/ML Model Selection and Training:** - - rApp/Non-RT RIC performs AI/ML model selection, retraining, and deployment decisions. For a model deployment request, the rApp provides the rAppId, AI/ML model identifier, and target deployment location. -- Actor Decision Making:** - - 6 «R1» Create A1 Policy (Energy Saving rApp to SMO / Non-RT RIC FWK) - - 7 «A1» Prepare policy and execute for PA power optimization (SMO / Non-RT RIC FWK to Near-RT RIC) - - 8 «A1» A1 Policy create Response (Near-RT RIC to SMO / Non-RT RIC FWK) - - 9 «R1» A1 Policy create Response (SMO / Non-RT RIC FWK to Energy Saving rApp) - - 10 Monitor Energy saving objectives (Energy Saving rApp to SMO / Non-RT RIC FWK) - - 11 Interpreting A1 Policy (Near-RT RIC to E2-Node(s)) - - E2 Data Collection:** Near-RT RIC to trigger E2 data collection from E2 Nodes and O-RU via O-DU - - 12 AI/ML Model Inference to Evaluate E2 Control/Policy (Near-RT RIC to E2-Node(s)) - - E2 Control /Policy:** Near-RT RIC to trigger E2 Control /Policy towards E2 Nodes - - 13 «A1» Notify A1 Policy Status (Near-RT RIC to SMO / Non-RT RIC FWK) - - 14 «R1» Notify A1 Policy Status (SMO / Non-RT RIC FWK to Energy Saving rApp) - - 15 «R1» Update or Delete A1 Policy (Energy Saving rApp to SMO / Non-RT RIC FWK) - - 16 «A1» Update or Delete Policy (SMO / Non-RT RIC FWK to Near-RT RIC) - -Sequence diagram showing the flow of A1 interface-based O-RU PA optimization for energy saving. Lifelines include Energy Saving rApp, SMO / Non-RT RIC FWK, Near-RT RIC, E2-Node(s), and O-RU(s). The process involves Data Collection, Data Analysis / AI/ML Model Selection and Training, and Actor Decision Making phases. - -Figure 4.8.7.3.1-1: Flow diagram of A1 interface-based O-RU PA optimization for energy saving - -#### 4.8.7.4 Required data - -This sub-clause contains the input and output data of model training and inference for energy saving using O-RU PA power optimization. - -##### 4.8.7.4.1 Input data - -The measurement input data is used in model training and inference. They can include the following measurements to monitor energy consumption and energy efficiency of E2 node(s) and O-RU(s): - -- a) DL PDCP SDU data volume per interface (data volume in DL delivered per PLMN, per QoS level, per slice, per interface ((from O-CU-UP to O-DU over F1-U, to external O-CU-UP over Xn-U and to external O-eNB over X2-U)) (as specified in 3GPP TS 28.552 [5], clause 5.1.3.6.2.3) - -- b) UL PDCP SDU data volume per interface (data volume in UL delivered per PLMN, per QoS level, per slice, per interface ((from O-DU to O-CU-UP over F1-U, to external O-CU-UP over Xn-U and to external O-eNB over X2-U)) (as specified in 3GPP TS 28.552 [5], clause 5.1.3.6.2.4) -- c) PNF Energy consumption (as specified in 3GPP TS 28.552 [5], clause 5.1.1.19.3) -- d) Power consumed by physical network function & its components (as specified in 3GPP TS 28.552 [5], clause 5.1.1.19.2 and in MP [10], clauses B.1-1, B.5) -- e) M1 MDT measurement in trace record for immediate MDT measurements including RSRP, RSRQ, SINR (as specified in 3GPP TS 32.423 [11], clause 4.34.1) - -##### 4.8.7.4.2 Output data - -rApps to deliver energy saving & energy efficiency A1 policies for PA power optimization through R1 interface. - -### 4.8.8 External power source coordination-based energy saving - -#### 4.8.8.1 Background and goal of the use case - -In 3GPP Release 19 [25], clauses 5.1.6.2, 5.2.5.1, 8.3.1, 8.3.2, and 8.3.3, and Annex C.1, the framework is described for an operator to have awareness about the external power source. - -In O-RAN, energy source and supply information is obtained by the SMO via standard management paths. When the O-RU exposes such information, it shall be provided over O1 (M-plane) using WG4 YANG/NRM attributes (when available). The SMO may also ingest the information from external systems (e.g., an energy management system) using SMO integrations. The interface between an external power source and the O-RU is out of scope for O-RAN. - -The SMO (Non-RT RIC) may use the energy source/supply information—together with other network data—to create or update an A1 energy saving policy for the relevant cells. - -These A1 policies are enforced by the Near-RT RIC, which dynamically applies configurations or provide E2 policy to switch the external power source and configure an appropriate energy saving methods in the O-RU through E2 node in near-real-time. - -#### 4.8.8.2 Entities/resources involved in the use case - -##### 1) SMO/Non-RT RIC framework: - -- a) Energy source and supply information can be made available at SMO framework (operator configures energy source and supply information [25] or collect through E2 node using O1 interface). -- b) Collect the configurations, performance indicators and measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports) from E2 node(s) through O1 interface, for the purpose of decision making. -- c) Transfer collected data towards rApp. It is assumed that energy supply and source information and configurations, performance indicators and measurement reports collected from the O-DU contain the related information for the corresponding O-RU(s). -- d) Create A1 policies for Near-RT RIC based on rApp requests to optimize the O-RU energy consumption based on energy source and supply information via the A1 interface. - -##### 2) rApps: - -- a) Collect the energy source and supply information, necessary configurations, performance indicators, and measurement reports from SMO/Non-RT RIC framework the purpose of training and execution of relevant AI/ML models. - -- b) (Optionally) Retrain, update, configure EE/ES AI/ML model. -- c) Infer an optimized AI policy for energy source configuration changes and external power source coordination-based energy optimization based on the data collected using R1 interface. - -##### 3) E2 node: - -- a) Report energy source and supply information, cell configuration, performance indicators and measurement data (e.g., cell load related information and traffic information, EE/EC measurement) and reports to SMO via O1 interface. -- b) Report energy source and supply information and measurement data (e.g., cell load related information and traffic information, EE/EC measurement reports) to Near-RT RIC via E2 interface. -- c) Support actions required to forward the energy source configuration changes and to perform external power source coordination-based energy optimization for E2 node and O-RU for EE/ES optimization. - -Note that the requirements of O1 interface for E2 nodes are under the scope of WG10. - -##### 4) O-RU : - -- a) Report energy source and supply information and EC/EE related information via open FH M-plane interface to O-DU. -- b) Support actions required to forward the energy source configuration changes and to perform energy saving for EE/ES optimization. - -Note that the requirements for O-RU and open FH are under the scope of WG4. - -##### 5) Near- RT RIC: - -- a) Collect measurement reports (e.g., cell load related information and traffic information, EE/EC measurement reports, Rel-18 and pre-R-18 supported UE information) from E2 nodes. -- b) (Optionally) Receive EE/ES AI/ML model for deployment via O1 or O2 interface. -- c) Analyse the received data from E2 nodes and perform AI/ML model inference to determine external power coordination-based EE/ES. Optimization (i.e., specific energy saving method to be activated for certain time and cells) considering the energy source and supply information and optimization targets/policies. -- d) Provide policies or required information to E2 node (O-CU) via E2 to trigger actions for EE/ES optimization. - -Note that the requirements for Near-RT RIC are under the scope of WG3. - -#### 4.8.8.3 Solution - -##### 4.8.8.3.1 A1 energy saving policy for external power source coordination - -In this solution, decision making, potentially using AI/ML model inference, is done at Near-RT RIC. While AI/ML model training might be hosted in Non-RT or Near-RT RIC, the description below is based on AI/ML model inferencing in the Near-RT RIC. - -The context of the A1 policy based external power source coordination-based energy optimization for energy saving is captured in table 4.8.8.3.1-1. - -**Table 4.8.8.3.1-1: A1 energy saving policy for external power source coordination** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|----------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | A1 policy-based guidance for performing external power source coordination-based energy saving in the network. | | - -| Use Case Stage | Evolution / Specification | <> | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Actors and Roles | SMO/Non-RT RIC framework A1 & O1 termination.
rApp: External power source coordination-based energy optimization.
E2 node(s): Enforces external power source coordination-based energy saving on E2 node and/or O-RU based on E2 policy or control.
Near-RT RIC: External power source coordination-based energy savings decision making function. | | -| Assumptions | O1 interface connectivity is established between SMO and E2 nodes.
R1 interface connectivity is established.
Open FH M-plane interface is established between O-DU and O-RU.
E2 interface connectivity is established between E2 node and Near-RT RIC.
A1 interface is established between Non-RT RIC and Near-RT RIC.
Network is operational. | | -| Pre-conditions | Operator collected the energy source and supply information from external power source control panel/energy supplier control panel.
Operator has set the targets for energy saving in the Non-RT RIC. | | -| Begins when | Operator enables the rApp along with initial ML model for external power source coordination-based energy saving and E2 node(s) and O-RU(s) become operational.
See NOTE. | | -| Step 1 (M) | rApp requests to collect energy source and supply information, necessary configurations, performance indicators, and measurement data towards SMO/Non-RT RIC framework over R1 interface.
Configurations may contain data related to O-RU capability to support the exposure of external power source (energy source and supply) information, which rApp needs to know before formulating A1 policies for external power source coordination-based energy optimization. | | -| Step 2 (M) | SMO/Non-RT RIC framework requests data collection towards E2 node(s) and O-RU(s) (via E2 node(s)) over O1 interface. | | -| Step 3 (M) | O-DU upon receiving request from SMO/Non-RT RIC framework requests and collect necessary data including external power source (energy source and supply) information from O-RU(s). | | -| Step 4 (M) | E2 node(s) sends the energy source and supply information, configuration data, configured measurement data to SMO/Non-RT RIC framework periodically or event based. | | -| Step 5 (M) | rApp collects the energy source and supply information (either operator configuring the information to SMO framework or exposed through E2 node(s) via O1 interface), configuration data, collected measurement data for processing. | | -| Step 6 (M) | rApp to trigger EE/ES optimization through A1 policy to prepare and execute external power source coordination-based energy optimization. | | - -| Use Case Stage | Evolution / Specification | <> | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | | Related use | -| Step 7 (M) | SMO/Non-RT RIC framework receives policy from rApp and forwards it towards Near-RT RIC via A1 interface. | | -| Step 8 (M) | Near-RT RIC provides A1 policy response to SMO/Non-RT RIC framework. | | -| Step 9 (M) | SMO/Non-RT RIC framework informs rApp about A1 policy feedback. | | -| Step 10 (M) | rApp monitors energy source and supply information and energy saving objectives as per A1 policy. | | -| Step 11 (M) | Near RT-RIC then interprets the policy to determine the required data collection and E2 control/policies. | | -| Step 12 (M) | Near RT-RIC Inferencing AI/ML model to evaluate & generate E2 control or policies for external power source configuration and energy optimization according to the energy source and supply information. | | -| Step 13 (M) | Near-RT RIC to notify Non-RT RIC if any change in the state of policy. | | -| Step 14 (M) | SMO/Non-RT RIC framework forwards notification received from Near-RT RIC to rApp. | | -| Step 15 (O) | If energy saving objectives are not achieved rApp may decide to initiate fallback mechanism for example, updating or deleting A1 policy for external power source coordination-based energy optimization. | | -| Step 16 (O) | SMO/Non-RT RIC framework send update or delete A1 policies to Near-RT RIC. | | -| Ends when | E2 node(s) becomes non-operational or when the operator disables the rApp for energy saving. | | -| Exceptions | N/A | | -| Post Conditions | rApp continues monitoring of energy saving functionality at E2 node(s) and O-RU.

E2 node(s) and O-RU(s) operate using the newly deployed parameters and state (off/on). | | - -NOTE: Operator can set policies through rApp or allow AI/ML model in rApp to infer policies. - -``` -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -Skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -``` - -``` - -autonumber - -Box "Service Management and Orchestration Framework" #gold -Box #lightgrey -Participant "Energy Saving\nrApp" as ESrAPP - -End Box - -Participant "SMO / Non-RT RIC\nFWK " as NRTF -End box - -Box " O-RAN Nodes" #lightpink - Participant "Near-RT RIC" as NeRT - Participant "E2-Node(s)" as E2NODES - Participant "O-RU(s) " as ORUs -End box - -group Data Collection - ESrAPP -> NRTF : <> Data collection request - Note over ESrAPP, NRTF : Operator configure the energy source and supply information - NRTF -> E2NODES : <> Data collection request - E2NODES <-> ORUs : <> Data collection request - E2NODES -> NRTF : <> Data Collection - NRTF -> ESrAPP : <> Data Collection -End - -group Data Analysis /AI/ML Model Selection and Training -Note over ESrAPP , NeRT - -rApp/Non-RT RIC performs AI/ML model selection, retraining, and deployment decisions. - -For a model deployment request, the rApp provides the rAppId, AI/ML model identifier, and target deployment location - -End note - -End - -group Actor Decision Making - ESrAPP -> NRTF : <> Create AI Policy - NRTF -> NeRT : <> Policy to prepare and execute for external \npower source coordination based energy optimization - NeRT -> NRTF : <> AI Policy create Response - NRTF -> ESrAPP : <> AI Policy create Response - ESrAPP -> ESrAPP : Monitor Energy saving objectives - NeRT -> NeRT : Interpreting AI Policy - -``` - -``` - -group E2 Data Collection - -Note over NeRT , ORUs -Near-RT RIC to trigger E2 data collection from E2 Nodes and O-RU via O-DU -End note -end - - NeRT -> NeRT : AI/ML Model Inference\n to Evaluate E2 Control/Policy - -group E2 Control /Policy - -Note over NeRT , ORUs -Near-RT RIC to trigger E2 Control /Policy towards E2 Nodes -End note -end - -group Opt - - NeRT -> NRTF : <> Notify A1 Policy Status - NRTF -> ESRAPP : <> Notify A1 Policy Status - -end - -group Opt - - ESRAPP -> NRTF : <> Update or Delete A1 Policy - NRTF -> NeRT : <> Update or Delete Policy - -end - -end - -@enduml - -``` - -The flow diagram of A1 energy saving policy for external power source coordination is shown in figure 4.8.8.3.1-1. - -![Sequence diagram showing the flow of an A1 energy saving policy for external power source coordination. The diagram is divided into two main lifelines: 'Service Management and Orchestration Framework' (left) and 'O-RAN Nodes' (right, containing Near-RT RIC, E2-Node(s), and O-RU(s)). The process includes Data Collection, Data Analysis/AI/ML Model Selection and Training, and Actor Decision Making. The Near-RT RIC triggers E2 data collection and control policies towards E2 Nodes. The SMO/Non-RT RIC FWK performs AI/ML model selection and policy creation. The Energy Saving rApp monitors energy saving objectives and interacts with the SMO/Non-RT RIC FWK.](633486b12958f97e062b5cf9e0801e99_img.jpg) - -The diagram illustrates the interaction between the Service Management and Orchestration Framework and O-RAN Nodes for an A1 energy saving policy. The sequence of messages is as follows: - -- Data Collection:** - - 1 «R1» Data collection request: Energy Saving rApp to SMO / Non-RT RIC FWK. - - Operator configure the energy source and supply information (note). - - 2 «O1» Data collection request: SMO / Non-RT RIC FWK to E2-Node(s). - - 3 Data collection request: E2-Node(s) to O-RU(s). - - 4 «O1» Data Collection: O-RU(s) to E2-Node(s). - - 5 «R1» Data Collection: E2-Node(s) to SMO / Non-RT RIC FWK. -- Data Analysis /AI/ML Model Selection and Training:** - - rApp/Non-RT RIC performs AI/ML model selection, retraining, and deployment decisions. For a model deployment request, the rApp provides the rAppId, AI/ML model identifier, and target deployment location (note). -- Actor Decision Making:** - - 6 «R1» Create A1 Policy: Energy Saving rApp to SMO / Non-RT RIC FWK. - - 7 «A1» Policy to prepare and execute for external power source coordination based energy optimization: SMO / Non-RT RIC FWK to Near-RT RIC. - - 8 «A1» A1 Policy create Response: Near-RT RIC to SMO / Non-RT RIC FWK. - - 9 «R1» A1 Policy create Response: SMO / Non-RT RIC FWK to Energy Saving rApp. - - 10 Monitor Energy saving objectives: Energy Saving rApp (self-call). - - 11 Interpreting A1 Policy: Near-RT RIC to E2-Node(s). - - E2 Data Collection:** Near-RT RIC to trigger E2 data collection from E2 Nodes and O-RU via O-DU (note). - - 12 AI/ML Model Inference to Evaluate E2 Control/Policy: Near-RT RIC to E2-Node(s). - - E2 Control /Policy:** Near-RT RIC to trigger E2 Control /Policy towards E2 Nodes (note). - - 13 «A1» Notify A1 Policy Status: Near-RT RIC to SMO / Non-RT RIC FWK. - - 14 «R1» Notify A1 Policy Status: SMO / Non-RT RIC FWK to Energy Saving rApp. - - 15 «R1» Update or Delete A1 Policy: Energy Saving rApp to SMO / Non-RT RIC FWK. - - 16 «A1» Update or Delete Policy: SMO / Non-RT RIC FWK to Near-RT RIC. - -Sequence diagram showing the flow of an A1 energy saving policy for external power source coordination. The diagram is divided into two main lifelines: 'Service Management and Orchestration Framework' (left) and 'O-RAN Nodes' (right, containing Near-RT RIC, E2-Node(s), and O-RU(s)). The process includes Data Collection, Data Analysis/AI/ML Model Selection and Training, and Actor Decision Making. The Near-RT RIC triggers E2 data collection and control policies towards E2 Nodes. The SMO/Non-RT RIC FWK performs AI/ML model selection and policy creation. The Energy Saving rApp monitors energy saving objectives and interacts with the SMO/Non-RT RIC FWK. - -Figure 4.8.8.3.1-1: Flow diagram of A1 energy saving policy for external power source coordination - -#### 4.8.8.4 Required data - -This sub-clause contains the input and output data of model training and inference for energy saving using external power source coordination-based energy optimization. - -##### 4.8.8.4.1 Input data - -The measurement input data are used in model training and inference. They can include the following measurements to monitor energy consumption and energy efficiency of E2 node(s) and O-RU(s): - -- a) Energy supply information (energySupplyMode and energySourceList) (as specified in 3GPP TS 28.310 [25], clause 8.3.1.2). -- b) Energy source information (energySourceType, energySourceCef, renewableEnergy, and energyCompositionPercentage) (as specified in 3GPP TS 28.310 [25], clause 8.3.2.2). -- c) Energy information group (energySupplyModeRefList and memberDNList) (as specified in 3GPP TS 28.310 [25], clause 8.3.3.2). - -- d) DL PDCP SDU data volume per interface (data volume in DL delivered per PLMN, per QoS level, per slice, per interface ((from O-CU-UP to O-DU over F1-U, to external O-CU-UP over Xn-U and to external O-eNB over X2-U)) (as specified in 3GPP TS 28.552 [5], clause 5.1.3.6.2.3) -- e) UL PDCP SDU data volume per interface (data volume in UL delivered per PLMN, per QoS level, per slice, per interface ((from O-DU to O-CU-UP over F1-U, to external O-CU-UP over Xn-U and to external O-eNB over X2-U)) (as specified in 3GPP TS 28.552 [5], clause 5.1.3.6.2.4) -- f) Power consumed by physical network function & its components (as specified in 3GPP TS 28.552 [5], clause 5.1.1.19.2 and in MP [10], clauses B.1, B.5) - -##### 4.8.8.4.2 Output data - -rApps to deliver energy saving & energy efficiency A1 policies for external power source coordination-based energy optimization through R1 interface. - -## 4.9 O-Cloud resource optimization - -This clause contains the set of O-Cloud resource optimization use cases - -### 4.9.1 Use case: O-Cloud node draining use case - -This use case describes the procedure for the SMO/Non-RT RIC to perform draining of specific O-Cloud node [O-Cloud node description based on O2-GA&P [13] recommendation by rApp through SMO, which can result in relocation of network functions or its components to another O-Cloud node, thereby restoring network function i.e., network healing. - -#### 4.9.1.1 Background and goal of the use case - -When one or more NF(s) is (are) experiencing some performance degradation, and there is possibility that issue could not be fixed, or root cause could not be identified just by analyzing O1 (FCAPS) data. There can be a requirement of correlating O1 and O2 (FCAPS) data optionally with the help of AI/ML, which can result in identification of root cause. - -Examples for reasons to perform O-Cloud node draining: - -- There is possibility of faulty or misconfiguration of underneath O-Cloud node. By co-relating RAN OAM and O2 related data rApp will help in identifying issue in O-Cloud node which is found to be the root cause of NF's performance degradation, then O-Cloud can be drained, and relocation of the NF(s) on another O-Cloud node can be performed. This example explains a scenario where an action can be invoked when NF(s) performance degradation happens due to O-Cloud node(s), which can be resolved by draining the O-Cloud node. - -NOTE: The O-Cloud node(s) is set to maintenance mode (as specified in O2-GA&P [13], clause 3.10.2) by default, when this use case is called. - -#### 4.9.1.2 Entities/resources involved in the use case - -- 1) SMO/Non-RT RIC framework: - - To collect necessary performance, configuration, and other data for rApp to define and update policies which guides the SMO for O-Cloud resource management through O2 related functions over O2 interface. - - Non-RT RIC framework should support rApp for managing data to and from O2 related functions related to resource management. - - Train AI/ML model with data from O1 and O2, which supports rApp to predict possible requirement of O-Cloud node draining. -- 2) rApps: - -- Collect the necessary configurations, performance indicators, and measurement reports from SMO/Non-RT RIC framework. - - (Optionally) Retrain, update, configure AI/ML model. - - Infer an optimized policies/recommendations for O-Cloud node draining based on the data collected using R1 interface. -- 3) O2 related functions (NFO/FOCOM): -- To support discovery and delivery of O-Cloud IMS/DMS FCAPS data. - - To support reception of policy/recommendations from rApp and enforcing these policies/recommendations towards O-Cloud over O2 interface. -- 4) RAN OAM functions: -- Retrieve relevant PM, CM, FM data from E2 nodes via the O1 interface. - - Allow rApps to access the PM, CM, FM data over R1 interface. -- 5) O-Cloud (IMS and DMS): -- To support delivery of O-Cloud (IMS/DMS) resource performance, configuration, and other data to O2 related functions. - - To provide feedback post completion or non-completion of recommendations to Non-RT RIC through O2 related functions. - - To support to relocate network function and drain O-Cloud node. -- 6) E2 nodes: -- Support to send fault and measurement data, RAN configurations to SMO/Non-RT RIC via the O1 interface. - -#### 4.9.1.3 Solutions - -In this solution, decision making, potentially using AI/ML model inference, is done at rApp. While AI/ML model training might be hosted in Non-RT RIC, the description below is based on AI/ML model training in the Non-RT RIC. - -The context of Non-RT RIC based O-Cloud node draining is captured in table 4.9.1.3-1. - -**Table 4.9.1.3-1: Non-RT RIC based O-Cloud node draining** - -| Use Case Stage | Evolution / Specification | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | Draining O-Cloud node through O2 related functions. | -| Actors and Roles | SMO/Non-RT RIC framework.
rApp: O-Cloud policy/recommendations triggering function.
O2 related functions (NFO/FOCOM): Orchestration and management related functions.
RAN OAM functions: O1 FCAPS functions.
O-Cloud IMS and DMS: O-Cloud policy enforcement and resource data reporting.
E2 node: To report network function data to SMO/Non-RT RIC. | -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - O1 and O2 interface connectivity is established with SMO including RAN OAM functions /O2 related functions.
  • - R1 interface connectivity is established between rApp and Non-RT RIC framework.
| -| Pre-conditions |
  • - Network is operational.
| -| Begins when | Operator specified trigger condition or event is detected. | - -| Use Case Stage | Evolution / Specification | -|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Step 1 (M) | rApp sent discovery request to SMO/Non-RT RIC framework to discover O2 related services. | -| Step 2 (M) | Non-RT RIC framework resolves the request and sent service discovery result to rApp. | -| Step 3 (M) | rApp requests O2 related data from O2 related functions (NFO/FOCOM).
rApp can request data such as compute utilization, memory usage, availability of network function, performance of API responses from NF deployments, status of AAL logical processing unit, etc. | -| Step 4 (M) | Non-RT RIC framework processes the data request and request O2 related function (NFO and FOCOM) to collect O2ims and O2dms related data. | -| Step 5 (M) | O2 related function (FOCOM) performs data request and collection from O-Cloud (IMS). | -| Step 6 (M) | O2 related function (NFO) performs data request and collection from O-Cloud (DMS). | -| Step 7 (M) | SMO/Non-RT RIC framework collect and store O2ims and O2dms related data. | -| Step 8 (M) | SMO/Non-RT RIC framework delivers O2 related data towards rApp over R1 Interface. | -| Step 9 (M) | rApp requests RAN OAM related data to be collected from E2 nodes such as availability of E2 node, accessibility KPIs, UEs connected, user traffic and alarms reported on interface level, etc., to understand performance of E2 nodes. | -| Step 10 (M) | Non-RT RIC framework forwards request to E2 nodes through RAN OAM functions. | -| Step 11 (M) | RAN OAM functions request and collect data from E2 nodes. | -| Step 12 (M) | SMO/Non-RT RIC framework to collect and store RAN OAM related PM data. | -| Step 13 (M) | SMO/Non-RT RIC framework delivers RAN OAM related O1 data towards rApp. | -| Step 14 (O) | AI/ML models can be retrained either on Non-RT RIC framework or on rApp. If Non-RT RIC framework is hosting retraining, then rApp selects AI/ML model and initiate retraining on Non-RT RIC framework.

See NOTE 1. | -| Step 15 (O) | Upon receiving retraining request from rApp. Non-RT RIC framework initiates AI/ML model retraining. | -| Step 16 (O) | rApp monitors retrained AI/ML model and retrieves retrained AI/ML model.

See NOTE 2. | -| Step 17 (O) | If AI/ML model retraining is hosted by rApp then AI/ML model to be retrained on rApp itself. | -| Step 18 (O) | Once AI/ML model retraining is performed, AI/ML models are deployed and activated for inferencing for which rApp constantly monitors O1 and O2 related data. | -| Step 19 (M) | rApp identifies the requirement of fault recovery or maintenance of O-Cloud node and formulate policy/recommendations to drain, which can relocate network function to another O-Cloud node.
rApp can sent policy or recommendations to O2 related function (FOCOM) for O-Cloud node draining. rApp to include the necessary identifiers of the O-Clouds to be drained.
See NOTE 3. | -| Step 20 (M) | Post receiving policy/recommendations for draining of O-Cloud node, O-Cloud to perform NF relocation (optionally) and drain O-Cloud node as specified in ORCH-USE-CASES [14], clause 3.12.2, then O2 related function (FOCOM) Informs rApp about NF relocation (optionally) and drain O-Cloud node R1 Interface. | -| Step 21 (M) | rApp monitors O1 and O2 PM, FM data from NF for any undesirable behaviour. | -| Ends when | If network function/E2 node becomes non-operational or when the operator disables the rApp. | -| Exceptions | N/A | - -| Use Case Stage | Evolution / Specification | -|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------| -| Post Conditions | rApp continues close loop monitoring of O-Cloud node telemetry. | -| NOTE 1: AI/ML procedures mentioned here can be subject to change based on future work on AI/ML workflow in WG2. | | -| NOTE 2: AI/ML model retrieval procedure over R1 interface is for illustration purpose, can be subject to change based on future work on AI/ML workflow in WG2. | | -| NOTE 3: Identifiers mentioned above are not specified in the present document. | | - -``` - -@startuml -'https://plantuml.com/sequence-diagram -!pragma teoz true -Skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber - -Box "O-Cloud" #lightseagreen - participant "DMS" as DMS - participant "IMS" as IMS -End box - -Box "Service Management and Orchestration Framework" #gold - Participant "O2 Related Function\nNFO & FOCOM" as ORF - Participant "RAN OAM Functions" as OAM -Box #lightgrey - Participant "Non-RT RIC\nFramework Function" as nRT - Participant "rApp" as rApp -End Box -End box - -Box " RAN Nodes" #lightpink - Participant "E2 Node" as E2Node -End box - -group O2 Related Data Collection - rApp -> nRT : <> O2 Related service Discovery - nRT -> rApp : <> O2 Related service Result - -``` - -``` -rApp -> nRT : <> O2 Related Data subscription request -``` - -``` -nRT -> ORF : Data subscription request(O2ims and Odms related) -``` - -``` -Note right -``` - -``` -Data subscription request O2, which can include -``` - -``` -NF compute utilization, memory usage , availability -``` - -``` -of Network function ,API responses from NFs etc. -``` - -``` -End note -``` - -``` -loop #while for each data delivery -``` - -``` -ORF <-> IMS : <> Data\nRequest & collection -``` - -``` -ORF <-> DMS : <> Data\nRequest & collection -``` - -``` -ORF -> nRT : Data delivery(O2ims and Odms related) -``` - -``` -nRT -> rApp: <> O2 Related Data Delivery -``` - -``` -End loop -``` - -``` -End -``` - -``` -group O1 Data Collection -``` - -``` -rApp -> nRT : <> O1 Data subscription request -``` - -``` -nRT -> OAM : Data subscription Request -``` - -``` -Note right -``` - -``` -Data such as Availability of E2 Node, -``` - -``` -accessibly KPIs , UEs connected , user traffic -``` - -``` -and alarms reported on interface level etc. -``` - -``` -End note -``` - -``` -loop #while foreach data delivery -``` - -``` -OAM <-> E2Node : <> Data Request and Collection -``` - -``` -OAM -> nRT : Data Retrieval -``` - -``` -nRT -> rApp: <> O1 Data Delivery -``` - -``` -End Loop -``` - -``` -End -``` - -``` -group Data Analysis AI/ML Training and Inference -``` - -``` -alt training on Non-RT RIC Fwk -``` - -``` -rApp -> nRT : <> Select AI/ML Model and Initiate re-training -``` - -``` -nRT -> nRT : AI/ML Model re-training -``` - -``` -rApp <-> nRT : <> Request and Transfer Re-trained AI/ML Model -``` - -``` -Note over rApp -``` - -``` -rApp monitors re-trained - -model parameters and decides - -to retrieve AI/ML model - -End note - -Else trainig on rApp - - rApp -> rApp : AI/ML Model re-training - -end - - rApp -> rApp : Deploy and activate re-trained\nAI/ML Model for inferencing - -Note left - -AI/ML model inference deployed in rApp to evaluate policy/recommendations - -based on O1 & O2 Related Data analyzed. - -End Note - -End - -group Action - -rApp -> ORF : <> O-Cloud Node Drain Policy /recomendation - -Note over nRT,rApp - -Node Identifier & other node related details to be included in request. - -End Note - -group O-Cloud Operation - -ref over ORF , IMS, DMS - - As specified in O-RAN.WG6.ORCH-USE-CASES [14], clause 3.12.2 O-Cloud to perform NF - -relocation (optionally) - - and draining of O-Cloud node Based - - policy/recommendation from rApp. - -End - -end - -ORF -> rApp : <> Policy or Recommedation Completion Feedback - -end - -rApp -> rApp : Monitor NF's PM/FM\nPost Relocation - -Note over rApp - -rApp to monitor PM, FM of NF for any undesirable behaviour - -End Note - -@enduml - -@startuml -``` - -``` - -'https://plantuml.com/sequence-diagram - -!pragma teoz true - -Skin rose - -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -autonumber - -Box "O-Cloud" #lightseagreen - participant "DMS" as DMS - participant "IMS" as IMS -End box - -Box "Service Management and Orchestration Framework" #gold - Participant "O2 Related Function\nNFO & FOCOM" as ORF - Participant "RAN OAM Functions" as OAM -Box #lightgrey - Participant "Non-RT RIC\nFramework Function" as nRT - Participant "rApp" as rApp -End Box -End box - -Box " RAN Nodes" #lightpink - Participant "E2 Node" as E2Node -End box - -group O2 Related Data Collection - rApp -> nRT : <> O2 Related service Discovery - nRT -> rApp : <> O2 Related service Result - rApp -> nRT : <> O2 Related Data subscription request - nRT -> ORF : Data subscription request(O2ims and Odms related) - -Note right -Data subscription request O2, which may include -NF compute utilization, memory usage , availability -of Network function ,API responses from NFs etc. -End note - -``` - -``` - -loop #white for each data delievery -ORF <-> IMS : <> Data\nRequest & collection -ORF <-> DMS : <> Data\nRequest & collection -ORF -> nRT : Data delivery(O2ims and Odms related) -nRT -> rApp: <> O2 Related Data Delivery -End loop -End - -group O1 Data Collection -rApp -> nRT : <> O1 Data subscritpion request -nRT -> OAM : Data subscription Request -Note right -Data such as Availability of E2 Node, -accessibly KPIs , UEs connected , user traffic -and alarms reported on interface level etc. -End note - -loop #white foreach data delievery -OAM <-> E2Node : <> Data Request and Collection -OAM -> nRT : Data Retrieval -nRT -> rApp: <> O1 Data Delivery -End Loop -End - -group Data Analysis AI/ML Training and Inference -alt trainig on Non-RT RIC Fwk - rApp -> nRT : <> Select AI/ML Model and Inintiate re-training - nRT -> nRT : AI/ML Model re-training - rApp <-> nRT : <> Request and Transfer Re-trained AIML Model -Note over rApp -rApp monitors re-trained -model parameters and decides -to retrieve AIML model -End note - -Else trainig on rApp - rApp -> rApp : AI/ML Model re-training -end - -rApp -> rApp : Deploy and activate re-trained\nAI/ML Model for inferencing - -``` - -Note left - -AI/ML model inference deployed in rApp to evaluate policy/recommendations -based on O1 & O2 Related Data analyzed. - -End Note - -End - -group Action - -rApp -> ORF : <> O-Cloud Node Drain Policy /recommendation - -Note over nRT,rApp - -Node Identifier & other node related details to be included in request. - -End Note - -group O-Cloud Operation - -ref over ORF , IMS, DMS - -As specified in O-RAN.WG6.ORCH-USE-CASES [14], clause 3.12.2 O-Cloud to perform NF -relocation (optionally) - -and draining of O-Cloud node Based -policy/recommendation from rApp. - -End - -end - -ORF -> rApp : <> Policy or Recommendation Completion Feedback - -end - -rApp -> rApp : Monitor NF's PM/FM\nPost Relocation - -Note over rApp - -rApp to monitor PM, FM of NF for any undesirable behaviour - -End Note - -@enduml - -@startuml - -' - -!pragma teoz true - -Skin rose - -skinparam ParticipantPadding 5 - -skinparam BoxPadding 10 - -skinparam defaultFontSize 12 - -skinparam lifelineStrategy solid - -autonumber - -``` -Box "O-Cloud" #lightseagreen - participant "DMS" as DMS - participant "IMS" as IMS -End box - -Box "Service Management and Orchestration Framework" #gold - Participant "O2 Related Function\nNFO & FOCOM" as ORF - Participant "RAN OAM Functions" as OAM -Box #lightgrey - Participant "Non-RT RIC\nFramework Function" as nRT - Participant "rApp" as rApp -End Box -End box - -Box " RAN Nodes" #lightpink - Participant "E2 Node" as E2Node -End box - -group O2 Related Data Collection - rApp -> nRT : <> O2 Related service Discovery - nRT -> rApp : <> O2 Related service Result - rApp -> nRT : <> O2 Related Data subscription request - nRT -> ORF : Data subscription request(O2ims and Odms related) - -Note right -Data subscription request O2, which may include -NF compute utilization, memory usage , availability -of Network function ,API responses from NFs etc. -End note - -loop #white for each data delivery -ORF <-> IMS : <> Data\nRequest & collection -ORF <-> DMS : <> Data\nRequest & collection -ORF -> nRT : Data delivery(O2ims and Odms related) -nRT -> rApp: <> O2 Related Data Delivery -End loop - -End - -group O1 Data Collection -``` - -``` - -rApp -> nRT : <> O1 Data subscription request - -nRT -> OAM : Data subscription Request - -Note right -Data such as Availability of E2 Node, -accessibly KPIs , UEs connected , user traffic -and alarms reported on interface level etc. - -End note - -loop #white foreach data delivery -OAM <-> E2Node : <> Data Request and Collection -OAM -> nRT : Data Retrieval -nRT -> rApp: <> O1 Data Delivery -End Loop - -End - -group Data Analysis AI/ML Training and Inference -alt training on Non-RT RIC Fwk - rApp -> nRT : <> Select AI/ML Model and Initiate re-training - nRT -> nRT : AI/ML Model re-training - rApp <-> nRT : <> Request and Transfer Re-trained AIML Model -Note over rApp -rApp monitors re-trained -model parameters and decides -to retrieve AIML model -End note -Else training on rApp - rApp -> rApp : AI/ML Model re-training -end - rApp -> rApp : Deploy and activate re-trained\nAI/ML Model for inferencing -Note left -AIML model inference deployed in rApp to evaluate policy/recommendations -based on O1 & O2 Related Data analyzed. -End Note -End - -group Action - -rApp -> ORF : <> O-Cloud Node Drain Policy / recommendation - -``` - -``` -Note over nRT,rApp -Node Identifier & other node related details to be included in request. -End Note - -group O-Cloud Operation -ref over ORF , IMS, DMS - - As specified in O-RAN.WG6.ORCH-USE-CASES [14], clause 3.12.2 O-Cloud to perform NF -relocation (optionally) - - and draining of O-Cloud node Based - - policy/recommendation from rApp. -End - -end - -ORF -> rApp : <> Policy or Recommendation Completion Feedback -end - -rApp -> rApp : Monitor NF's PM/FM\nPost Relocation - -Note over rApp -rApp to monitor PM, FM of NF for any undesirable behaviour -End Note - -@enduml -``` - -The workflow for Non-RT RIC based O-Cloud node draining is shown in figure 4.9.1.3-1. - -![Sequence diagram showing interactions between O-Cloud (DMS, IMS), Service Management and Orchestration Framework (O2 Related Function, RAN OAM Functions, Non-RT RIC Framework Function, rApp), and RAN Nodes (E2 Node). The diagram is divided into sections: O2 Related Data Collection, O1 Data Collection, Data Analysis AI/ML Training and Inference, and Action. It details message exchanges for data collection, model training, and policy recommendations.](6e0f8561f98e81dc4918793f6a884357_img.jpg) - -**Sequence Diagram: O-RAN Use Case Requirements** - -**Participants:** - -- O-Cloud:** DMS, IMS -- Service Management and Orchestration Framework:** O2 Related Function (NFO & FOCOM), RAN OAM Functions, Non-RT RIC Framework Function, rApp -- RAN Nodes:** E2 Node - -**Sequence of Interactions:** - -- O2 Related Data Collection:** - - Non-RT RIC Framework Function sends **1 <> O2 Related service Discovery** to rApp. - - rApp returns **2 <> O2 Related service Result** to Non-RT RIC Framework Function. - - Non-RT RIC Framework Function sends **3 <> O2 Related Data subscription request** to rApp. - - rApp sends **4 Data subscription request(O2ims and Odms related)** to O2 Related Function (NFO & FOCOM). - - For each data delivery: - - O2 Related Function sends **5 <> Data Request & collection** to DMS. - - DMS returns **6 <> Data Request & collection** to O2 Related Function. - - O2 Related Function sends **7 Data delivery(O2ims and Odms related)** to Non-RT RIC Framework Function. - - Non-RT RIC Framework Function sends **8 <> O2 Related Data Delivery** to rApp. -- O1 Data Collection:** - - Non-RT RIC Framework Function sends **9 <> O1 Data subscription request** to rApp. - - rApp sends **10 Data subscription Request** to O2 Related Function (NFO & FOCOM). - - For each data delivery: - - O2 Related Function sends **11 <> Data Request & and Collection** to E2 Node. - - E2 Node returns **12 Data Retrieval** to O2 Related Function. - - O2 Related Function sends **13 <> O1 Data Delivery** to rApp. -- Data Analysis AI/ML Training and Inference:** - - [training on Non-RT RIC Fwk]**: - - Non-RT RIC Framework Function sends **14 <> Select AI/ML Model and Initiate re-training** to rApp. - - rApp performs **15 AI/ML Model re-training**. - - rApp sends **16 <> Request and Transfer Re-trained AI/ML Model** to Non-RT RIC Framework Function. - - [training on rApp]**: - - rApp performs **17 AI/ML Model re-training**. - - rApp sends **18 Deploy and activate re-trained AI/ML Model for inferencing** to Non-RT RIC Framework Function. -- Action:** - - Non-RT RIC Framework Function sends **19 <> O-Cloud Node Drain Policy /recommendation** to rApp. - - rApp sends **20 <> Policy or Recommendation Completion Feedback** to Non-RT RIC Framework Function. - - O-Cloud Operation (performed by O2 Related Function): - - As specified in clause 3.12.2 of "Resource Optimization Use Cases" in O-RAN.WG6.ORCH-USE-CASES, O-Cloud to perform NF relocation (optionally) and draining of O-Cloud node Based policy/recommendation from rApp. - - Post-relocation, E2 Node sends **21 Monitor NF's PM/FM Post Relocation** to rApp. - - rApp monitors PM, FM of NF for any undesirable behaviour. - -**Notes:** - -- Data subscription request O2:** which may include NF compute utilization, memory usage, availability of Network function, API responses from NFs etc. -- Data such as Availability of E2 Node:** accessibility KPIs, UEs connected, user traffic & and alarms reported on interface level etc. -- rApp monitors re-trained model parameters:** and decides to retieve AI/ML model -- AI/ML model inference deployed in rApp:** to evaluate policy/recommendations based on O1 & O2 Related Data analyzed. -- Node Identifier & other node related details:** to be included in request. -- rApp to monitor PM, FM of NF:** for any undesirable behaviour - -Sequence diagram showing interactions between O-Cloud (DMS, IMS), Service Management and Orchestration Framework (O2 Related Function, RAN OAM Functions, Non-RT RIC Framework Function, rApp), and RAN Nodes (E2 Node). The diagram is divided into sections: O2 Related Data Collection, O1 Data Collection, Data Analysis AI/ML Training and Inference, and Action. It details message exchanges for data collection, model training, and policy recommendations. - -**Figure 4.9.1.3-1: Workflow for Non-RT RIC based O-Cloud node draining** - -#### 4.9.1.4 Required data - -This sub-clause contains the input and output data required for O-Cloud node drain. - -##### 4.9.1.4.1 Input data - -O2 related data (O-Cloud FCAPS data) - -1. DMS telemetry data to understand state and health of network functions deployed on O-Cloud node. -2. IMS telemetry data to understand the state and health of O-Cloud nodes. -3. IMS/DMS inventory data to understand configuration of nodes and network functions deployments on O-Cloud nodes. -4. Monitoring data such as compute utilization, memory usage, availability of network function, performance of API responses from NF deployments, status of AAL logical processing unit, etc. - -RAN OAM related data (E2 node and O-RU/network function data) - -1. The measurement counters and KPIs (as defined by 3GPP and will be extended for O-RAN use cases) should be appropriately aggregated by cell, slice, etc. -2. E2 node KPIs such as availability of E2 node, accessibility KPIs, UEs connected, user traffic and alarms reported on interface level etc. to understand whether E2 nodes behaving as usual. - -##### 4.9.1.4.2 Output data - -O2 related data - -1. rApp to provide policy based guidance or trigger recommendations to drain O-Cloud node towards O2 related function (NFO/ FOCOM). - -# 5 Requirements - -## 5.1 Functional requirements - -### 5.1.1 Non-RT RIC functional requirements - -The Non-RT RIC functional requirements are captured in table 5.1.1-1. - -**Table 5.1.1-1: Non-RT RIC functional requirements** - -| REQ | Description | Note | -|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| -| REQ-Non-RT-RIC-FUN1 | Non-RT RIC shall support data retrieval and analysis; the data can include performance, configuration or other data related to the application (recommended data shown in required data clause for different use cases). | | -| REQ-Non-RT-RIC-FUN2 | Non-RT RIC shall support relevant AI/ML model training based on the data in [REQ-Non-RT-RIC-FUN1] for non-real-time optimization of configuration parameters in RAN or Near-RT RIC, as applicable for the use case. | | -| REQ-Non-RT-RIC-FUN3 | Non-RT RIC shall support relevant AI/ML model training based on the data in [REQ-Non-RT-RIC-FUN1] for generating/optimizing policies and intents to guide the behavior of applications in Near-RT RIC or RAN, as applicable for the use case. | | -| REQ-Non-RT-RIC-FUN4 | Non-RT RIC shall support training of relevant AI/ML models based on the data in [REQ-Non-RT-RIC-FUN1] to be deployed/updated in Near-RT RIC as required by the applications. | | -| REQ-Non-RT-RIC-FUN5 | Non-RT RIC shall support performance monitoring and evaluation. | | -| REQ-Non-RT-RIC-FUN6 | Non-RT RIC shall support a fallback mechanism to prevent drastic degradation/fluctuation of performance, e.g. to restore to the previous policy or configuration. | | -| REQ-Non-RT-RIC-FUN7 | Non-RT RIC shall be able to produce enrichment information through data analysis. | | -| REQ-Non-RT-RIC-FUN8 | Non-RT RIC shall be able to request O1 reconfiguration for non-real-time optimization of configuration parameters in E2 nodes and/or Near-RT RIC, as applicable for the use case. | | -| REQ-Non-RT-RIC-FUN9 | Non-RT RIC shall support retrieval of external information as applicable for the use case. | | - -### 5.1.2 A1 interface functional requirements - -The A1 interface functional requirements are captured in table 5.1.2-1. - -**Table 5.1.2-1: A1 interface functional requirements** - -| REQ | Description | Note | -|-------------|----------------------------------------------------------------------------------------------------|------| -| REQ-A1-FUN1 | A1 interface shall support communication of policies from Non-RT RIC to Near-RT RIC. | | -| REQ-A1-FUN2 | A1 interface shall support AI/ML model deployment and update from Non-RT RIC to Near-RT RIC. | | -| REQ-A1-FUN3 | A1 interface shall support communication of enrichment information from Non-RT RIC to Near-RT RIC. | | -| REQ-A1-FUN4 | A1 interface shall support feedback from Near-RT RIC for monitoring AI/ML model performance. | | -| REQ-A1-FUN5 | A1 interface shall support the policy feedback from Near-RT RIC to Non-RT RIC. | | - -### 5.1.3 R1 interface functional requirements - -The R1 interface functional requirements are captured in table 5.1.3-1. - -**Table 5.1.3-1: R1 interface functional requirements** - -| REQ | Description | Note | -|-------------|----------------------------------------------------------------------------------------------------------------------------|------------------------------| -| REQ-R1-FUN1 | R1 interface shall support registration of services. | Based on REQ-nRTRfW-R1r-10 | -| REQ-R1-FUN2 | R1 interface shall support discovery of registered services. | Based on REQ-nRTRAApp-R1r-30 | -| REQ-R1-FUN3 | R1 interface shall support authentication of rApp. | Based on REQ-nRTRfW-R1r-10 | -| REQ-R1-FUN4 | R1 interface shall support authorization of service request. | Based on REQ-nRTRfW-R1r-10 | -| REQ-R1-FUN5 | R1 interface shall support subscription and unsubscription of notifications for added/updated/removed registered services. | Based on REQ-nRTRfW-R1r-120 | -| REQ-R1-FUN6 | R1 interface shall support registration of data types. | Based on REQ-nRTRfW-R1r-30 | -| REQ-R1-FUN7 | R1 interface shall support subscription of data types. | Based on REQ-nRTRfW-R1r-30 | -| REQ-R1-FUN8 | R1 interface shall support A1 related services. | | -| REQ-R1-FUN9 | R1 interface shall support O1 related services. | | - -| REQ | Description | Note | -|--------------|-----------------------------------------------------------------------|--------------------------------------------------------| -| REQ-R1-FUN10 | R1 interface shall support O2 related services. | | -| REQ-R1-FUN11 | R1 interface shall support AI/ML workflow services. | | -| REQ-R1-FUN12 | R1 interface shall support services related to network slice subnets. | Please refer to Slicing Architecture [15] for details. | - -## 5.2 Non-functional requirements - -### 5.2.1 Non-RT RIC non-functional requirements - -The Non-RT RIC non-functional requirements are captured in table 5.2.1-1. - -Table 5.2.1-1: Non-RT RIC non-functional requirements - -| REQ | Description | Note | -|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|------| -| REQ-Non-RT-RIC-NON-FUN1 | Non-RT RIC shall not update the same policy or configuration parameter for a given Near-RT RIC or RAN function more often than once per second. | | -| REQ-Non-RT-RIC-NON-FUN2 | Non-RT RIC shall be able to update policies in several Near-RT RICs. | | - -### 5.2.2 A1 interface non-functional requirements - -The A1 interface non-functional requirements are captured in table 5.2.2-1. - -Table 5.2.2-1: A1 interface non-functional requirements - -| REQ | Description | Note | -|-----|-------------|------| -| | | | - -### 5.2.3 R1 interface non-functional requirements - -The R1 interface non-functional requirements are captured in table 5.2.3-1. - -**Table 5.2.3-1: R1 interface non-functional requirements** - -| REQ | Description | Note | -|-----|-------------|------| -| | | | - -# Annex (informative): Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2019.02.08 | 01.00.01 | Draft for template | -| 2019.03.12 | 01.00.02 | First draft with Scope, references, acronyms | -| 2019.03.20 | 01.00.03 | Initial addition of use case contributions:
  • - Traffic Steering use case for development of Non-RT RIC functionality and A1 interface use case
  • - QoE use case
| -| 2019.04.10 | 01.00.04 | Addition of CRs:
  • - Traffic steering use case
  • - QoE Optimization use case
  • - 3D-MIMO beamforming optimization use case
| -| 2019.04.12 | 01.00.05 | Addition of CRs:
  • - 2019-04-08-CMCC-ATT-CR-A1-O1 description-revision
  • - 2019-04-03-CMCC-CR -Add Recommended requirements for Near-RT RIC and E2 in UCR Annex
| -| 2019.04.15 | 01.00.06 | Updates throughout the document based on the editorial and co-chair team review.
Addition of CRs:
  • - 2019_04_14_O-RAN.WG2 UsecaseRequirement.DraftSpec-CR-form-CMCC-Orange-TIM_v2.00
  • - 2019-04-03-CMCC-ATT-CR -Add Recommended requirements for Near-RT RIC and E2 in UCR Annex v2-minor revision
  • - 2019-04-11-ATT-CMCC-UCR-TrafficSteeringA1.PlantUMLSource
  • - 2019-04-11-ATT-CMCC-UCR-E2Annex.PlantUMLSource
Addition of requirements to traceability section of use case tables.

Addition of REQ-Non-RT RIC-FUN9 for Non-RT RIC fallback mechanism. | -| 2019.04.18 | 01.00.07 | Addition of CR:
  • - 2019-04-18-CMCC-ATT-Netsia-CR-Modifications to A1 and O1 related requirements
| -| 2019.04.26 | 01.00.08 | Addition of CR:
  • - 2019-04-22-ATT-CR -Requirements Consolidation for UCR doc v1 clean
| -| 2019.04.27 | 01.00.09 | Editorial fixes (reference issues, upper case/lower case fixes, etc.) | -| 2019.05.01 | 01.00.10 | Updating the traceability section of uses case to reflect the consolidated requirements | -| 2019.05.06 | 01.00 | Final version 01.00 | -| 2019.10.07 | 02.00.01 | Initial version of v2.0 | -| 2019.12.27 | 02.00.02 | Addition of CR:
  • - 2019.11.20-ORAN-WG2_Netsia_Usecase_CR_Removal_Of_3D_MIMO
Note: This CR is for removing 3D MIMO from WG2 and moving it to UCTG as it does not have WG2 specific impact. | -| 2020.01.03 | 02.00.03 | Addition of CR:
  • - WG2_2019.09.03_Ericsson_CR_Update_on_UCR_for_RAN_traffic_steering
| -| 2020.01.03 | 02.00.04 | Addition of CR:
  • - 2019.12.12-ORAN-WG2_Ericsson_Usecase_CR_QoS_
| - -| | | | -|------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | based_resource_optimization | -| 2020.01.09 | 02.00.05 | Addition of CR:
- 2020.01.09-ORAN-WG2_Ericsson_Usecase_CR_QoS_based_resource_optimization | -| 2020.01.12 | 02.00.06 | Addition of CR:
- WG2_2020.01.09_CMCC_CR_Update on enrichment information for traffic steering use case | -| 2020.01.15 | 02.00.07 | Addition of CR:
- 2020.01.08-ORAN-WG2.UseCaseReqs_CR_NOK_V2XHO

Editorial updates in various sections | -| 2020.01.23 | 02.00.08 | Addition of CR:
- ORAN-WG2_CMCC_Correction on QoE optimization use case.docx

Addition of missing rows (exceptions, post conditions, traceability) to QoS use case, Table 3.3.3-1 | -| 2020.02.06 | 02.00.09 | Addition of CR:
- ORAN-WG2_CMCC_Correction on QoE optimization use case - v2.docx

Editorial updates | -| 2020.02.23 | 02.00.10 | Editorial updates based on WG2 review comments | -| 2020.03.01 | 02.00.11 | Editorial updates based on spec naming convention, fixing header/table of contents uniformity, plantuml source embedding and other editorial updates | -| 2020.03.01 | 02.00 | Final 02.00 | -| 2020.10.31 | 02.01.01 | Initial version of v2.1 | -| 2020.11.01 | 02.01.02 | Addition of CR:
- INT.AO-2020.07.12-WG2-CR-0004-MultiAccess_v02.00.docx | -| 2020.11.01 | 02.01 | Final 02.01 | -| 2021.02.23 | 03.00.01 | Initial version of v3.0 | -| 2021.02.27 | 03.00.02 | Addition of CR:
- JNPR.AO-2020.10.22-WG2-CR-0001-RAN_SLA_ASSR-v04.docx | -| 2021.03.10 | 03.00 | Final version 03.00 | -| 2021.07.06 | 04.00.01 | Initial version of v4.0 | -| 2021.07.06 | 04.00.02 | Addition of CR:
- ERI-2021-03-30-WG2-CR-0034-R1 Functional requirements-v03 | -| 2021.07.06 | 04.00.03 | Addition of CR:
- ERI-2021-05-17-WG2-CR-0035-Definitions and Abbreviations-v03 | -| 2021.07.19 | 04.00 | Final version 04.00 | -| 2021.11.12 | 05.00.01 | Initial version of v5.0 | -| 2021.11.13 | 05.00.02 | Addition of CR:
- INT-2021.10.05-WG2-CR-0022-NSSI-Resource-Optimization-v06 | -| 2021.11.13 | 05.00.03 | Addition of CR:
- KDDI.AO-2021.11.02-WG2-CR-0003-RAN_SLA_ASSR-v02 | -| 2021.11.24 | 05.00.04 | Updates to address WG2 review comments | -| 2021.11.24 | 05.00 | Final version 05.00 | - -| | | | -|------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2022.03.24 | 05.00.05 | Adopted new spec revision numbering per O-RAN Work Procedures
Initial version towards v6.0, starting with v05.00.05 per new revision numbering | -| 2022.03.24 | 05.00.06 | Addition of CR:
- KDDI.AO-2022.01.21-WG2-CR-0004-RAN_SLA_ASSR-v04 | -| 2022.03.24 | 05.00.07 | Addition of CR:
- NOK-2022.03.08-WG2-CR-0023-mMIMO_GoB-v04 | -| 2022.03.24 | 05.00.08 | Addition of CR:
- INT-2022.02.14-WG2-CR-00023-Non-GoB beamforming UC-v06 | -| 2022.03.24 | 05.00.09 | Addition of CR:
- ATT-2022.02.18-WG2-CR-0004-MUMIMO Optimization UC-v05 | -| 2022.03.24 | 05.00.10 | Changes accepted from v05.00.09
Baseline for WG2 Approval | -| 2022.04.01 | 05.00.11 | Addressing the WG2 review comments (with track changes on) | -| 2022.04.01 | 05.00.12 | Changes accepted from v05.00.11
Clean version for TSC Approval | -| 2022.04.15 | 06.00 | Final version 06.00 | -| 2023.03.13 | 06.00.01 | Initial version towards v07.00, starting with v06.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.13 | 06.00.02 | Addition of CR:
- JNPR-2022.01.19-WG2-CR-0007-R1interfaceSliceSubnetRequirement-v03 | -| 2023.03.13 | 06.00.03 | Addition of CR:
- INT-2022.03.30-WG2-CR-00032-Massive MIMO use case introduction-v03 | -| 2023.03.13 | 06.00.04 | Addition of CR:
- RMI-2022.09.13-WG2-CR-0005.UCR.Energy saving_Cell & Carrier Shutdown Use Case-v11

Editorial updates for consistency with existing use case headings (Removal of "3.8.1.2 O1 Interface Based Optimization" heading and setting the remainder subheadings from level 5 to level 4) | -| 2023.03.14 | 06.00.05 | Addition of CR:
- RMI-2022.09.16-WG2-CR-0006.UCR.Energy saving_RF Channel Reconfiguration Description_v10

Editorial updates for consistency with existing use case headings (Removal of "3.8.2.2 O1 Interface Based Optimization" heading and setting the remainder subheadings from level 5 to level 4) | -| 2023.03.14 | 06.00.06 | Changes accepted from v06.00.05
Baseline for WG2 approval | -| 2023.03.24 | 06.00.07 | WG2 review comments are addressed, and approval is completed. Ready for TSC approval and publication.
Added O-RAN Release "R003" to document name and title. | -| 2023.03.24 | 07.00 | Final version 07.00 | -| 2023.07.19 | 07.00.01 | Initial version towards v08.00, starting with v07.00.01 per O-RAN specification revision numbering process
Addition of CR:
- RMI-2022.09.27-WG2-CR-0007.UCR.O-Cloud Node Draining Use Case-v09. | - -| | | | -|------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2023.07.19 | 07.00.02 | Addition of CR:
- RMI-2023.01.26-WG2-CR-0009.UCR.Energy saving_Cell & Carrier Shutdown Use Case (A1 Policy Based Solution)_v07 | -| 2023.07.19 | 07.00.03 | Addition of CR:
- CMCC-2023.05.16-WG2-CR-0002-Adding frequency preference policy to UCR-v2 | -| 2023.07.19 | 07.00.04 | Update of the spec to latest O-RAN TS template except for splitting the references to normative and informative. This split is planned to be made in next release of the document. Update of the spec to Times New Roman font. | -| 2023.07.27 | 07.00.05 | WG2 review comments are addressed, and approval is completed. | -| 2023.07.27 | 07.00.06 | All changes accepted, clean version. | -| 2023.07.27 | 08.00 | Final version 08.00 | -| 2023.09.12 | 08.00.01 | Initial version towards v09.00, starting with v08.00.01 per O-RAN specification revision numbering process
Addition of CR:
- JNPR-2023.09.12-WG2-CR-0008-O-RAN-Use-Case-Requirements-ODR-References-Section-v01 | -| 2023.09.12 | 08.00.02 | Addition of CR:
- JNPR-2023.09.12-WG2-CR-0009-O-RAN-Use-Case-Requirements-ODR-References-Section-v01 | -| 2023.09.13 | 08.00.03 | Addition of CR:
- JNPR-2023.09.13-WG2-CR-0010-O-RAN-Use-Case-Requirements-ODR-References-Update-v01 | -| 2023.09.13 | 08.00.04 | Addition of CR:
- JNPR-2023.09.13-WG2-CR-0011-O-RAN-Use-Case-Requirements-ODR-References-Correction-v01 | -| 2023.11.08 | 08.00.05 | Addition of CR:
- FJT-2023.06.13-WG2-CR-0001.UCR.Energy_saving_Cell&Carrier_SwitchedOffOn_Use_Case-v04 | -| 2023.11.08 | 08.00.06 | Addition of CR:
- RMI-2023.08.29-WG2-CR-0015.UCR.ES.Advance Sleep Mode Use case Description_v04 | -| 2023.11.08 | 08.00.07 | Addition of CR:
- RMI-2023.09.22-WG2-CR-0017.UCR.A1 Policy Based Energy saving_RF Channel Reconfiguration Description_v03 | -| 2023.11.08 | 08.00.08 | Clean version for WG2 approval | -| 2023.11.16 | 08.00.09 | WG2 review comments are addressed, and approval is completed.
The spec's title has changed per WG2 decision. | -| 2023.11.16 | 08.00.10 | All changes accepted, clean version. | -| 2023.11.16 | 09.00 | Final version 09.00 | -| 2024.01.17 | 09.00.01 | Initial version towards v10.00, starting with v09.00.01 per O-RAN specification revision numbering process
Addition of CRs:
- JNPR-2023.09.13-WG2-CR-0012-O-RAN-Use-Case-Requirements-ODR-Required-Data-Reference-Correction-v02
- JNPR-2023.10.19-WG2-CR-0013-O-RAN-Use-Case-Requirements-ODR-References-Wording-v03 | - -| | | | -|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | |
  • - JNPR-2023.10.19-WG2-CR-0014-O-RAN-Use-Case-Requirements-ODR-Figures-References-Wording- Corrections-v02
  • - JNPR-2023.10.19-WG2-CR-0015-O-RAN-Use-Case-Requirements-ODR-Figures-Numbers-Corrections-v03
  • - JNPR-2023.10.19-WG2-CR-0018-O-RAN-Use-Case-Requirements-ODR-Notes-v03
  • - JNPR-2023.10.25-WG2-CR-0019-O-RAN-Use-Case-Requirements-ODR-Modal-Verbs_Shall_Shall_not_Should_Should_not_Must_Must_not-v02
  • - JNPR-2023.10.30-WG2-CR-0020-O-RAN-Use-Case-Requirements-ODR-Modal-Verbs_Can_Cannot_May_Need_not-v01
  • - JNPR-2023.10.30-WG2-CR-0021-O-RAN-Use-Case-Requirements-ODR-FFS-Concepts-v01
| -| 2024.02.27 | 09.00.02 | Addition of CRs:
  • - JNPR-2024.01.29-WG2-CR-0022-O-RAN-Use-Case-Requirements-ODR-Clauses-v01
  • - JNPR-2024.01.29-WG2-CR-0023-O-RAN-Use-Case-Requirements-ODR-Figures-Capital_Letters-v01
| -| 2024.03.21 | 09.00.03 | Addition of CR:
  • - MAV-2023.05.17-WG2-CR-0015-mMIMO-SSBopt_v06
| -| 2024.03.30 | 09.00.04 | WG2 review comments are addressed, and approval is completed. | -| 2024.03.30 | 09.00.05 | All changes accepted, clean version. | -| 2024.03.30 | 10.00 | Final version 10.00 | -| 2024.06.28 | 10.00.01 | Initial version towards v11.00, starting with v10.00.01 per O-RAN specification revision numbering process
Addition of CR:
  • - JNPR-2024.05.31-WG2-CR-0024-O-RAN-Use-Case-Requirements-ODR-Capital_Letters-Editorial_Changes-Fixes-v01
| -| 2024.07.12 | 10.00.02 | WG2 review comments are addressed, and approval is completed. | -| 2024.07.12 | 10.00.03 | All changes accepted, clean version. | -| 2024.07.12 | 10.01 | Final version 10.01 | -| 2024.11.07 | 10.01.01 | Initial version towards next release, starting with v10.01.01 per O-RAN specification revision numbering process
Addition of CRs:
  • - JNPR-2024.09.09-WG2-CR-0025-O-RAN-Use-Case-Requirements-ODR-References-v01
  • - ERI-2024.10.17-WG2-CR-0369-Add_R1_to_Scope-v01
Update of the header to be consistent with the O-RAN TS template | -| 2024.11.20 | 10.01.02 | Addition of CR:
  • - DTAG-2024.10.22-WG2-CR-0004-Use case numbering-v02
Updated copyright statement on the cover page and footer to 2025
Editorial changes to align to O-RAN TS template v02.01
Added 3GPP Release 18 related text to Normative and Informative References clauses
Editorial updates | -| 2024.11.21 | 10.01.03 | Clean version for WG2 approval | -| 2024.12.04 | 10.01.04 | WG2 review comments are addressed, and approval is completed. | - -| | | | -|------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2024.12.04 | 10.01.05 | All changes accepted, clean version. | -| 2024.12.04 | 10.02 | Final version 10.02 | -| 2025.02.12 | 10.02.01 | Initial version towards next release, starting with v10.02.01 per O-RAN specification revision numbering process
Addition of CRs:
  • - JNPR-2025.02.03-WG2-CR-0026-O-RAN-Use-Case-Requirements-Rel-18-Upgrade-v01
  • - JNPR-2025.02.03-WG2-CR-0027-O-RAN-Use-Case-Requirements-Rel-18-Upgrade-28.552-v01
  • - JNPR-2025.02.03-WG2-CR-0028-O-RAN-Use-Case-Requirements-Rel-18-Upgrade-36.314-v01
  • - JNPR-2025.02.03-WG2-CR-0029-O-RAN-Use-Case-Requirements-Rel-18-Upgrade-38.913-v01
Editorial corrections in Change history/Change request (history) table | -| 2025.02.24 | 10.02.02 | Addition of CR:
  • - RMI-2024.10.28-WG2-CR-0024.UCR.Energy saving_Cell DTXDRX optimization in time domain use case Description_v02
| -| 2025.03.12 | 10.02.03 | Addition of CRs:
  • - JNPR.AO-2025.02.03-WG2-CR-0030-O-RAN-Use-Case-Requirements-Definition-needed-items-v01
  • - JNPR.AO-2025.02.12-WG2-CR-0031-O-RAN-Use-Case-Requirements-Removal_of_38.913_reference-v02
  • - JNPR.AO-2025.02.21-WG2-CR-0032-O-RAN-Use-Case-Requirements-Removal-of-undefined-items-v01
Editorial updates to Copyright Statement to align to O-RAN TS template v03.00 | -| 2025.03.12 | 10.02.04 | Clean version for WG2 approval | -| 2025.03.20 | 10.02.05 | WG2 review comments are addressed, and approval is completed. | -| 2025.03.20 | 10.02.06 | All changes accepted, clean version. | -| 2025.03.20 | 10.03 | Final version 10.03 | -| 2025.07.08 | 10.03.01 | Initial version towards next release, starting with v10.03.01 per O-RAN specification revision numbering process
Addition of CRs:
  • - JNPR-2025.05.06-WG2-CR-0033-O-RAN-Use-Case-Requirements-ETSI_PAS_Comments-v01
  • - JNPR-2025.05.06-WG2-CR-0034-O-RAN-Use-Case-Requirements-ETSI_PAS_Comments-RAN_to_E2_Nodes-v01
Editorial updates to align to O-RAN TS template v05 | -| 2025.07.08 | 10.03.02 | Clean version for WG2 approval | -| 2025.07.16 | 10.04 | Final version 10.04 | -| 2025.11.19 | 10.04.01 | Initial version towards next release, starting with v10.04.01 per O-RAN specification revision numbering process
Addition of CRs:
  • - RMI-2024.10.28-WG2-CR-0026.UCR.Energy saving_spatial and power domain use case Description_v05
  • - RMI-2024.10.28-WG2-CR-0023.UCR.Energy saving_SSB-less S-Cell optimization Description_v07
  • - RMI-2025.10.06-WG2-CR-0038.UCR.Energy saving_PA_Power_Optimization Description_v03
| - -| | | | -|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | |
  • - RMI-2025.10.06-WG2-CR-0039.UCR.Energy saving_External_Power_Source_Coordination_based_ES_use case Description_v03
  • - ERI-2025.10.21-WG2-CR-0509-WG2UCR-TSP pcell preference-v01
| -| 2025.11.19 | 10.04.02 | Clean version for WG2 approval | -| 2025.11.26 | 10.04.03 | WG2 review comments are addressed, and approval is completed. | -| 2025.11.26 | 10.04.04 | All changes accepted, clean version. | -| 2025.11.26 | 11.00 | Final version 11.00 | \ No newline at end of file diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/00a0b3a0485d8e735df9cb73dbdf36d6_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/00a0b3a0485d8e735df9cb73dbdf36d6_img.jpg deleted file mode 100644 index 2d3c54e26c6f9a29939c6cdbf154b740ac17fbc1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/00a0b3a0485d8e735df9cb73dbdf36d6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9b90c058b175bcf7df3fb30748cbfb8facce1f6d2f0cc20f4a1b7fdd011ba63e -size 172162 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg deleted file mode 100644 index 77897c77fff5e000913f8a985615d9e7422621d5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c9cde1275743d799d73170972c9d2327ab4fd14c718cc2ed208bf6e7bef580f1 -size 97847 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg deleted file mode 100644 index 930b29c592e18e4ee9b7f13de4f79020ff712459..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5f8013eada922e4dd6d610cf1f66e7ef4cde52eba107e33f0825d24ae802b0e6 -size 4550 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/09fcf056902487318885284a6b43b08c_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/09fcf056902487318885284a6b43b08c_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/09fcf056902487318885284a6b43b08c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg deleted file mode 100644 index 99d51db6a2c18dcbe6bcc1f561696a4e371a21f0..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9ecb2d471360b4d468ad5d5c8340c5d4addd77780d4445c6363b69978de3c22e -size 4544 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 930b29c592e18e4ee9b7f13de4f79020ff712459..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5f8013eada922e4dd6d610cf1f66e7ef4cde52eba107e33f0825d24ae802b0e6 -size 4550 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/255efa1d461fc79b4ed367aaec11637f_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/255efa1d461fc79b4ed367aaec11637f_img.jpg deleted file mode 100644 index 4c06faf9bd3b7884698fe7e4942bb66b40921ba7..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/255efa1d461fc79b4ed367aaec11637f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f54bc4c345faf11d275aae1155e0e184312ee12d5bdfbfa2f9a62ede22cc6f56 -size 173083 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/27788c2a26d9641e68232a4eff1299b9_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/27788c2a26d9641e68232a4eff1299b9_img.jpg deleted file mode 100644 index 987d567b0176effb5ae04435abab2f9ddd83a9bf..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/27788c2a26d9641e68232a4eff1299b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:75344d60d6fa018afe9b1827bafcb38cddb7f38453e7c460d26f2d06e9ece393 -size 249936 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2a185522b492253375ed16f0c515c230_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2a185522b492253375ed16f0c515c230_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2a185522b492253375ed16f0c515c230_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg deleted file mode 100644 index 6adbbefaf8a438bdf0ac964042b4c8f403c6459f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ce6ac3089ae9d68fa3f922b11254b2009f5d39351a1e4bc1bb6364c4b8451626 -size 4543 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg deleted file mode 100644 index ad59e8c1a89667c75077441bc9f98a3d7509b632..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d045c98f4ab34e5cb743acf887994b30dcb958cee1afd318de742254f3eabd56 -size 145198 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2eea01382188b70064fa2818361d89f1_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2eea01382188b70064fa2818361d89f1_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/2eea01382188b70064fa2818361d89f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/318db222fae24a59c370fa6471d541b8_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/318db222fae24a59c370fa6471d541b8_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/318db222fae24a59c370fa6471d541b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/35437f160e157760713aa85be471c3f3_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/35437f160e157760713aa85be471c3f3_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/35437f160e157760713aa85be471c3f3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/364054adcd1b427fa259450e006c6b38_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/364054adcd1b427fa259450e006c6b38_img.jpg deleted file mode 100644 index f6711eac0ad1ecd02ba6c44e11427e2c445ac10c..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/364054adcd1b427fa259450e006c6b38_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1620d92a1ae9121f1b5af37803079165297bb29ce85ce33878b2ab49586aa791 -size 158244 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/3b89d812329a65ab156184a40524adf0_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/3b89d812329a65ab156184a40524adf0_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/3b89d812329a65ab156184a40524adf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/40ebe9179df298f1b6d76822f28d90aa_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/40ebe9179df298f1b6d76822f28d90aa_img.jpg deleted file mode 100644 index 6422d659aade80bab9ce04b79b3f2b47c8155e33..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/40ebe9179df298f1b6d76822f28d90aa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:27b83c3d58a2ae66202ab601cdfce27f8d0d4d9160c952b750e86678a292e580 -size 140033 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4842f073775fb1e84d101c02fd74e59e_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4842f073775fb1e84d101c02fd74e59e_img.jpg deleted file mode 100644 index 5a7dee864f699769e8c3931850fd5ad59e4ffe83..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4842f073775fb1e84d101c02fd74e59e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ba636701f0ca5b1be1c471e1bb9d496033ae8b33ba4d575b5d344aefd191464b -size 21238 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg deleted file mode 100644 index 930b29c592e18e4ee9b7f13de4f79020ff712459..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5f8013eada922e4dd6d610cf1f66e7ef4cde52eba107e33f0825d24ae802b0e6 -size 4550 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4f148853ae68fdcf5e43f7604cab457d_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4f148853ae68fdcf5e43f7604cab457d_img.jpg deleted file mode 100644 index 6672178e41756d7c67d67c70bed86cd4848f4bbd..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4f148853ae68fdcf5e43f7604cab457d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:27266d7574f1e4b5448eb1ed48b493388c8a474599a582f14f54107ffe3a90a8 -size 99835 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/5009e30a55479d3941af523871208f9d_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/5009e30a55479d3941af523871208f9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg deleted file mode 100644 index 0aa11c3870d5e84391c7789354cc6dc6bcd7be9d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2be92e367da08bf5c56c58ee292a05f557fc63186d6445e09bbb9def315c944f -size 47722 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg deleted file mode 100644 index 2dbcdfabf876faa8d2351a2c611a8026b7243ec9..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c8cb399768710ec32e7a75a7e983605f881df7423255c4f1069d069d464a03b -size 4534 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index b65c9819ba60bfe19f6cdb95d3075d756b2b6c71..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0cad14f9ac2225f628dcfe49bccbde098fb99facc8adc2cec5e351074d1e3eee -size 4528 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/53499879d98034410ecba2c386c58f0c_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/53499879d98034410ecba2c386c58f0c_img.jpg deleted file mode 100644 index 817cf5b8554b0df9ef73f7e76786da1dfdbe030a..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/53499879d98034410ecba2c386c58f0c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:76b66092a861d17266452587dae6bb9a48d5eeac72719a3e0465f6cff32c84b6 -size 174438 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/568031aac86c633aab96b734dba3835e_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/568031aac86c633aab96b734dba3835e_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/568031aac86c633aab96b734dba3835e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/59368942873b0c35eef79a7a985025dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/59e29b37c5e332b0be088cde8c4d217e_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/59e29b37c5e332b0be088cde8c4d217e_img.jpg deleted file mode 100644 index 291ff6891d0fc657cee08a1da2549c1d9583303f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/59e29b37c5e332b0be088cde8c4d217e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8d38a4db95d5a26eae1736ba6c98556d209dd189b525a2df22b67ab3d807567a -size 212968 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/5a31f8496931f6aa7570270dbeefca1e_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/5a31f8496931f6aa7570270dbeefca1e_img.jpg deleted file mode 100644 index 19463a0d4fb8c3d7400d48242658b769c325accb..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/5a31f8496931f6aa7570270dbeefca1e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9804c41e83a0936355fba0520a01bc762a49af5f66d3fb8ee48f44ce9a470245 -size 61513 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/633486b12958f97e062b5cf9e0801e99_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/633486b12958f97e062b5cf9e0801e99_img.jpg deleted file mode 100644 index 34ee97e7f4217e3c8cbaa145ec36d8dcfb486ecf..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/633486b12958f97e062b5cf9e0801e99_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:34969135b788793ea6f42a46187e3b983b911f40bc957fcb6f5f957f5f60b179 -size 164636 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/65b5e4a95d403df0ea5e8ff94f162a6a_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/65b5e4a95d403df0ea5e8ff94f162a6a_img.jpg deleted file mode 100644 index 12f403e1f9b09dff5a3d5b7161bb4fbe0b602c10..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/65b5e4a95d403df0ea5e8ff94f162a6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e5a0bdcff11b57c5f8ceba2a32519d575a5a842ccdd14c1481697044bb219257 -size 194979 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6983ff962c0a32659de18c30790e1519_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6983ff962c0a32659de18c30790e1519_img.jpg deleted file mode 100644 index b65c9819ba60bfe19f6cdb95d3075d756b2b6c71..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6983ff962c0a32659de18c30790e1519_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0cad14f9ac2225f628dcfe49bccbde098fb99facc8adc2cec5e351074d1e3eee -size 4528 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg deleted file mode 100644 index 707941421aff5cd71fb19110cb689048cc8a9cac..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8ad17e1571c7052e6960ea4afd75aba573a0d15eb69e3f5c72f9153847b228c9 -size 196048 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6e0f8561f98e81dc4918793f6a884357_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6e0f8561f98e81dc4918793f6a884357_img.jpg deleted file mode 100644 index aa2f328a00a0223a54bd2a60d6e825a5a3438cda..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6e0f8561f98e81dc4918793f6a884357_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:371a392a9b2fa6762dc70cabac47f8ec467e7177b74ab607245cbcff12e9820a -size 284004 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg deleted file mode 100644 index 99d51db6a2c18dcbe6bcc1f561696a4e371a21f0..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9ecb2d471360b4d468ad5d5c8340c5d4addd77780d4445c6363b69978de3c22e -size 4544 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg deleted file mode 100644 index 930b29c592e18e4ee9b7f13de4f79020ff712459..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5f8013eada922e4dd6d610cf1f66e7ef4cde52eba107e33f0825d24ae802b0e6 -size 4550 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/77464a47f104d0d647b2414591137b64_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/77464a47f104d0d647b2414591137b64_img.jpg deleted file mode 100644 index aa6997e8b105087752cf83e8368836daedd01eba..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/77464a47f104d0d647b2414591137b64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:654174f74eb8ddb88901f376199a15d7627ea1651172aa36cef2b9f2ceaba19a -size 39527 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/79e1709a7317ead45379cbb8ff3ba802_img.jpg deleted file mode 100644 index ed8bd4a927f4acfd9607b3d1294a3e97a81824a4..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/79e1709a7317ead45379cbb8ff3ba802_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:697c799bca15ce74633464dc1441762d01fbd10190188b1ef1ad8dad36caf825 -size 23971 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7ede87328f6b696dcffa65ebc4570cc8_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7ede87328f6b696dcffa65ebc4570cc8_img.jpg deleted file mode 100644 index 38978aceea6810057465d0d810de0819f279600f..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7ede87328f6b696dcffa65ebc4570cc8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:17ae54415a9c0c9c63219211b5e71b2995f4f6f3a5180462a02507f1bf604106 -size 33941 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 930b29c592e18e4ee9b7f13de4f79020ff712459..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5f8013eada922e4dd6d610cf1f66e7ef4cde52eba107e33f0825d24ae802b0e6 -size 4550 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/854df8ad60507803253274673f9062cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/85b10db535b22e64c7d37f362705ddbf_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/85b10db535b22e64c7d37f362705ddbf_img.jpg deleted file mode 100644 index 3d704b30e648e6d62b9210266ff59c3cb102c0ec..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/85b10db535b22e64c7d37f362705ddbf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:79d4a1c71220c85ec898748f9a23c6293df31d89a494a1f86c8fa442a5c6b05d -size 79278 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8ab30dbff406204a68c59ae7c1b77413_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8ab30dbff406204a68c59ae7c1b77413_img.jpg deleted file mode 100644 index 575fea29e18eb98a04ce01df2dfd253359de25cc..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8ab30dbff406204a68c59ae7c1b77413_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:78f6eff84d399451215193be6a82c0747fd8d9eaf39bcb78ad01414b90c1a04a -size 275647 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/90183a52275501da5a0fd5c63d837009_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/90183a52275501da5a0fd5c63d837009_img.jpg deleted file mode 100644 index de7733782e446b803feaceef1db336571683126e..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/90183a52275501da5a0fd5c63d837009_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e381d051e37f0d0045274add87e8ebf596e6929f5a2d9ee7c6c1c37560a9254c -size 121758 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index 930b29c592e18e4ee9b7f13de4f79020ff712459..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5f8013eada922e4dd6d610cf1f66e7ef4cde52eba107e33f0825d24ae802b0e6 -size 4550 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/96c8d8b0159c47a7478ada46d781060b_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/96c8d8b0159c47a7478ada46d781060b_img.jpg deleted file mode 100644 index c9d94f578ae2d785598a983085b8705170bd7a67..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/96c8d8b0159c47a7478ada46d781060b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e4eb3898140b4a91b766caff7b7218771b541bfb0cd3ebe82e52afb1b37c224e -size 111510 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 930b29c592e18e4ee9b7f13de4f79020ff712459..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5f8013eada922e4dd6d610cf1f66e7ef4cde52eba107e33f0825d24ae802b0e6 -size 4550 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a76fa39f5daf6a026e032495262ed0f6_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a76fa39f5daf6a026e032495262ed0f6_img.jpg deleted file mode 100644 index 5d1a747802a4de1a6871684cea0aa2f68b02026b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a76fa39f5daf6a026e032495262ed0f6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bd6383bd06e3937e66855e924838f749780bf2d27eec672abeb967c41c3efa5d -size 174858 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a9159a006d67a834a7b1a771c18191cc_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a9159a006d67a834a7b1a771c18191cc_img.jpg deleted file mode 100644 index ccee3a85d39a565099d7875e6d82fedb9f2034f2..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a9159a006d67a834a7b1a771c18191cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5e80c24a69feb9d774555055b6425050d4b0f68e814962e160311d4ae9e0660c -size 40138 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/aa39f51ba214496042ee3e2ce4ecee80_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/aa39f51ba214496042ee3e2ce4ecee80_img.jpg deleted file mode 100644 index bb3b9514fc85f0e54f8fcf4ebf409ec5d945eac1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/aa39f51ba214496042ee3e2ce4ecee80_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:61578567d71811e37d28a44cd44b98adbe1fd39477b2eb05577d55d90f86f202 -size 195580 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/abeba89144744fac6a1571aa9f94889e_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/abeba89144744fac6a1571aa9f94889e_img.jpg deleted file mode 100644 index e8c58adc7bdc5ccbc3f910358a3627fea538fd28..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/abeba89144744fac6a1571aa9f94889e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:aa755b53218b6a9dfc618b547a7208023af47aed983484db63822449817d008b -size 127168 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/aef4390a4629604196222b9ed006a786_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/aef4390a4629604196222b9ed006a786_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/aef4390a4629604196222b9ed006a786_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg deleted file mode 100644 index 1593d93a5cfe844e37dcea1ea4d1237fcd2a29f6..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/b34c69e1ec326b01c3a485b27b1df5f6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9ff97c6ebb2dd0c085fec704b3da364bb38ea311c3d005dd5501e03dcfb82e1f -size 72607 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/bb9f586190c7197099d25db7df9050af_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/bb9f586190c7197099d25db7df9050af_img.jpg deleted file mode 100644 index ac3cfab543f601f0f5d5df0819baff17d274a951..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/bb9f586190c7197099d25db7df9050af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d57cf478d6a7b5f2ccc5b9b3097071939cf811679cce8997ebdcbc5222840d3b -size 4513 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index 930b29c592e18e4ee9b7f13de4f79020ff712459..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5f8013eada922e4dd6d610cf1f66e7ef4cde52eba107e33f0825d24ae802b0e6 -size 4550 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/cab0834804fb031b43865554cc8d06ab_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/cab0834804fb031b43865554cc8d06ab_img.jpg deleted file mode 100644 index cc6a1601486483b2a2affd829af20aaf58698a41..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/cab0834804fb031b43865554cc8d06ab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d2e399a58d0f4edf7c6eb327f57166776c3a34a91c366974d3e5ca53bbf0c8fd -size 140937 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg deleted file mode 100644 index 12e490161b1ca814d948b6b2f7176bf9e027eee1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cd4f22da9bbed8aed363cc4fa0298bef3fb68bd57d3cbef3c29081f0466bc2 -size 4432 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/cf03eff1218a8cc1be6b05de892162de_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/cf03eff1218a8cc1be6b05de892162de_img.jpg deleted file mode 100644 index 81360a6a0996bdea48c5734dda42807ec1d59ff9..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/cf03eff1218a8cc1be6b05de892162de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:29c301095d9a3f57877522c9ef78f356fc067108a30e89a8834dd945a6f3f1c0 -size 189664 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d35a80e3faed208324083399568c7461_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d35a80e3faed208324083399568c7461_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d35a80e3faed208324083399568c7461_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e0113695dbf148bf5ec34354e544414b_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e0113695dbf148bf5ec34354e544414b_img.jpg deleted file mode 100644 index 8718e01c0efaa16162687d6c6cff099eb9377f82..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e0113695dbf148bf5ec34354e544414b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b71209d6394a32c6dc008217cdf50e8e6c4fb780056f8b89c7508eaa21b70a85 -size 42188 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 39011cdab27ee913e1ca087f29fdcc3802c89b71..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b0e44e6839fc4c2018f7bd21b79c28568b1d080b15af370c79abb7dd09281e2f -size 4535 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/f142b022cfc716cd967297f027efe647_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/f142b022cfc716cd967297f027efe647_img.jpg deleted file mode 100644 index 0308385be81f1755aa36ad4b2b2a736e150f27e9..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/f142b022cfc716cd967297f027efe647_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:83fb3e743bae6c2533dc1e647ba64a6a89fa9ffd61eff04728695f4b0130c70b -size 136677 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index 8910d6d5fa787b40ee439fa1b34e9d16e8ab8319..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ba79438cf6921f10d9d22de8b993869a10644acc3b5189088b3d908ec1481c9 -size 4536 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg deleted file mode 100644 index 233074ab1ed670df0b948c986455955660b072d0..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:398c8049391638ddfe6bcfd12d7d80897edb01a5fd817f9ef38961396bfa58b7 -size 164187 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg deleted file mode 100644 index c3d86fb0327196a9f4e535de607f9679893b3bb5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1aa7b7ea2d2f7a405b9ed225a9d75ba10a49558f5daba7eec5731fe0cfefc643 -size 4531 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/fac227c65a311c313325216dcf59591f_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/fac227c65a311c313325216dcf59591f_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/fac227c65a311c313325216dcf59591f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/facce731b2dbfae43a8609231a700be1_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/facce731b2dbfae43a8609231a700be1_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/facce731b2dbfae43a8609231a700be1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 5f24fa39ffa7c49caa538a942ffd98725711ddb5..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:655859aa4af4dbe7bdfeeb59379fe05d52b3e9ff5a0b453f1eda486e9903256f -size 4571 diff --git a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG2/O-RAN.WG2.TS.Use-Case-Requirements-R005-v11.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/doc.md b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/doc.md deleted file mode 100644 index 21ca0671398f564a5aac1139b029f99bba69b9d8..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/doc.md +++ /dev/null @@ -1,12133 +0,0 @@ - - -# --- **O-RAN Work Group 3 (Near-Real-time RAN Intelligent Controller and E2 Interface)** - -## **Near-RT RIC APIs** - -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..... | 5 | -| Modal verbs terminology ..... | 5 | -| 1 Scope..... | 6 | -| 2 References ..... | 6 | -| 2.1 Normative references ..... | 6 | -| 2.2 Informative references ..... | 6 | -| 3 Definition of terms, symbols and abbreviations ..... | 7 | -| 3.1 Terms ..... | 7 | -| 3.2 Symbols..... | 7 | -| 3.3 Abbreviations..... | 7 | -| 4 General ..... | 7 | -| 4.1 Introduction..... | 7 | -| 4.2 General Principles ..... | 7 | -| 4.3 Version Control..... | 8 | -| 4.4 Message Contents ..... | 8 | -| 4.5 Handling of missing, unknown or erroroneous IEs ..... | 8 | -| 5 A1-related API ..... | 8 | -| 5.1 Overview..... | 8 | -| 5.2 A1-related API Procedures ..... | 10 | -| 5.2.1 A1 Policy Setup procedure..... | 10 | -| 5.2.2 A1 Policy Update procedure ..... | 12 | -| 5.2.3 A1 Policy Delete procedure ..... | 13 | -| 5.3 Elements for A1-related API Communication..... | 15 | -| 5.3.1 General ..... | 15 | -| 5.3.2 Message Functional Definiton and Content..... | 15 | -| 5.3.3 Information Element Definitions ..... | 17 | -| 5.3.4 Message and Information Element Abstract Syntax ..... | 19 | -| 5.3.5 Message Transfer Syntax ..... | 22 | -| 6 E2-related API..... | 22 | -| 6.1 Overview..... | 22 | -| 6.1.1 Protocol Stack ..... | 22 | -| 6.1.2 List of E2 related APIs, procedures and messages..... | 23 | -| 6.2 E2-related API Procedures..... | 24 | -| 6.2.1 E2_Subscription_API procedures ..... | 25 | -| 6.2.2 E2_Indication_API procedures ..... | 32 | -| 6.2.3 E2_Control_API procedures ..... | 33 | -| 6.3 Elements for E2-related API Communication ..... | 37 | -| 6.3.1 General ..... | 37 | -| 6.3.2 Message Functional Definiton and Content..... | 37 | -| 6.3.3 Information Element Definitions ..... | 49 | -| 6.3.4 Message and Information Element Abstract Syntax ..... | 52 | -| 6.3.5 Message Transfer Syntax ..... | 63 | -| 7 SDL API..... | 63 | -| 7.1 Overview..... | 63 | -| 7.1.1 Protocol Stack ..... | 63 | -| 7.1.2 List of SDL APIs, procedures and messages ..... | 64 | -| 7.2 SDL API Procedures..... | 65 | -| 7.2.1 Void..... | 65 | -| 7.2.2 Void..... | 65 | -| 7.2.3 SDL Subscribe Information procedure ..... | 65 | -| 7.2.4 SDL Information Push procedure ..... | 67 | - -| | | | -|--------|--------------------------------------------------------|-----| -| 7.2.5 | SDL Information Update Notify procedure ..... | 68 | -| 7.2.6 | SDL Information Fetch procedure ..... | 69 | -| 7.2.7 | Store Data procedure ..... | 70 | -| 7.2.8 | Modify Data procedure ..... | 70 | -| 7.3 | Elements for SDL API Communication ..... | 75 | -| 7.3.1 | General ..... | 75 | -| 7.3.2 | Message Functional Definition and Content ..... | 75 | -| 7.3.3 | Information Element Definitions ..... | 81 | -| 7.3.4 | Message and Information Element Abstract Syntax ..... | 91 | -| 7.3.5 | Message Transfer Syntax ..... | 100 | -| 8 | Management API ..... | 100 | -| 8.1 | Overview ..... | 100 | -| 8.1.1 | Protocol Stack ..... | 100 | -| 8.1.2 | List of Management APIs, procedures and messages ..... | 101 | -| 8.2 | Management API Procedures ..... | 101 | -| 8.2.1 | xApp Registration Procedure ..... | 101 | -| 8.3 | Elements for Management API Communication ..... | 103 | -| 8.3.1 | General ..... | 103 | -| 8.3.2 | Message Functional Definition and Content ..... | 103 | -| 8.3.3 | Information Element Definitions ..... | 104 | -| 8.3.4 | Message and Information Element Abstract Syntax ..... | 105 | -| 8.3.5 | Message Transfer Syntax ..... | 107 | -| 9 | Enablement API ..... | 107 | -| 9.1 | Overview ..... | 107 | -| 9.1.1 | Protocol Stack ..... | 107 | -| 9.1.2 | List of Enablement APIs, procedures and messages ..... | 108 | -| 9.2 | Enablement API Procedures ..... | 109 | -| 9.2.1 | Enabl_ Discovery_ API Procedures ..... | 109 | -| 9.2.2 | Enabl_ Events_ API Procedures ..... | 111 | -| 9.3 | Elements for Enablement API Communication ..... | 119 | -| 9.3.1 | General ..... | 119 | -| 9.3.2 | Message Functional Definition and Content ..... | 119 | -| 9.3.3 | Information Element Definitions ..... | 127 | -| 9.3.4 | Message and Information Element Abstract Syntax ..... | 129 | -| 9.3.5 | Message Transfer Syntax ..... | 136 | -| 9A | AI/ML API ..... | 136 | -| 9A.1 | Overview ..... | 136 | -| 9A.1.1 | Protocol Stack ..... | 136 | -| 9A.1.2 | List of AI/ML APIs, procedures and messages ..... | 137 | -| 9A.2 | AI/ML API Procedures ..... | 138 | -| 9A.2.1 | Data Pipelining API Procedures ..... | 138 | -| 9A.2.2 | Inference API Procedures ..... | 145 | -| 9A.2.3 | AIML Training API Procedures ..... | 152 | -| 9A.3 | Elements for AI/ML API Communication ..... | 163 | -| 9A.3.1 | General ..... | 163 | -| 9A.3.2 | Message Functional Definition and Content ..... | 163 | -| 9A.3.3 | Information Element Definitions ..... | 177 | -| 9A.3.4 | Message and Information Element Abstract Syntax ..... | 187 | -| 10 | Common definitions across APIs ..... | 201 | -| 10.1 | Information element definitions ..... | 201 | -| 10.1.1 | PTI ..... | 201 | -| 10.1.2 | xApp ID ..... | 202 | -| 10.1.3 | API Name ..... | 202 | -| 10.1.4 | API Version ..... | 202 | -| 10.1.5 | A1 Policy Type ID ..... | 202 | -| 10.1.6 | Global E2 Node ID ..... | 203 | -| 10.1.7 | RAN Function ID ..... | 203 | -| 10.1.8 | Void ..... | 203 | - -| | | | -|------------------------------------------|-------------------------------------------|-----| -| 10.1.9 | Endpoint Information ..... | 203 | -| 10.2 | Information element abstract syntax ..... | 203 | -| 10.2.1 | Abstract syntax in Protocol Buffers..... | 203 | -| Annex (informative): Change History..... | | 206 | - -# Foreword - -This Technical Specification (TS) has been produced by WG3 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 signalling and data transport protocols for Near-RT RIC APIs. The protocols are developed in accordance with the functionalities and interactions stated in [2]. - -# 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 TR 21.905: “Vocabulary for 3GPP Specifications”. -- [2] O-RAN.WG3.RICARCH-v03.00.00: “O-RAN, Near-Real-time RAN Intelligent Controller, Near-RT RIC Architecture”. -- [3] O-RAN.WG3.E2AP-v02.01.00: “O-RAN, Near-Real-time RAN Intelligent Controller, E2 Application Protocol(E2AP)”. -- [4] Protocol buffers. Available at . -- [5] gRPC. Available at . -- [6] O-RAN.WG11.SecReqSpecs: “O-RAN, Security Requirements Specifications”. -- [7] O-RAN.WG2.A1TD-v04.00: “O-RAN, A1 interface: Type Definitions”. -- [8] O-RAN.WG3.E2SM-v02.01.02: “O-RAN, Near-Real-time RAN Intelligent Controller, E2 Service Model (E2SM)”. -- [9] IETF RFC 4122: “A Universally Unique Identifier (UUID) URN Namespace”. -- [10] O-RAN.WG3.Y1AP-v01.00: " O-RAN Y1 interface: Application Protocol". -- [11] O-RAN.WG3.Y1TD-v01.00: " O-RAN Y1 interface: Type Definitions". -- [12] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)". -- [13] O-RAN.WG2.TS.R1GAP-R004-v10.00: "R1 interface: General Aspects and Principles". - -## 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] Semantic Versioning Specification. Available at . - -# --- 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the following terms apply: - -**Near-RT RIC:** as defined in [2]. - -**Near-RT RIC APIs:** interfaces that connect xApp and Near-RT RIC platform. - -**Near-RT RIC Platform:** a software platform to host xApps. The Near-RT RIC is comprised of the Near-RT RIC Platform and xApps. - -**xApp:** as defined in [2]. - -## 3.2 Symbols - -No Symbol is defined in this document. - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply: - -| | | -|-------------|-------------------------------------------| -| API | Application Programming Interface | -| Near-RT RIC | Near-real-time RAN Intelligent Controller | -| PTI | Procedure Transaction Identity | - -# --- 4 General - -## 4.1 Introduction - -Clause 4 specifies the principles and conventions commonly applied to Near-RT RIC API design with the Network API approach as described in clause 7.1.2 of [2]. - -## 4.2 General Principles - -For each Near-RT RIC API, the following principles should be followed: - -- A default solution that includes network protocol and message encoding should be defined to ensure interoperability. The default solution requires mandatory support by all Near-RT RIC platforms and xApps. The optional protocols available for a given APIs are discoverable by xApps. -- The IEs in the Near-RT RIC API which refer to different specifications shall be encoded as defined in the referred specification. - -The common data types applicable to several API categories should be collected in clause 10. - -In addition, the following design principles shall apply: - -- Parallel transactions, i.e., multiple ongoing Near-RT RIC API procedures of the same types related to the same xApp, and platform functionality are supported. - -## 4.3 Version Control - -An API version shall consist of at least 3 fields, following a MAJOR.MINOR.PATCH pattern according to the Semantic Versioning Specification [i.1] unless specified otherwise. - -EXAMPLE: "1.0.0". - -The basic rules as reproduced from [i.1] shall apply for incrementing the versions: - -- MAJOR version is incremented if backward incompatible change is made. -- MINOR version is incremented if functional change is made in a backward compatible way. -- PATCH version is incremented if correction is made in a backward compatible way. - -## 4.4 Message Contents - -### 4.4.1 General - -The Near-RT RIC API messages are defined in message tables, with “Presence” and “Range” attributes set accordingly. - -### 4.4.2 Presence - -The definitions and usages of “Presence” attribute can be found in clause 9.1.1 of NGAP [12]. - -### 4.4.3 Range - -The definitions and usages of “Range” attribute can be found in clause 9.1.3 of NGAP [12]. - -## 4.5 Handling of missing, unknown or erroroneous IEs - -### 4.5.1 General - -The receiver uses its local API version to detect missing, unknown or erroroneous IEs in the received messages. - -If an IE that shall be present (e.g., a mandatory IE, or a conditionally mandatory IE with condition(s) satisfied) is missing in the initiating message of a procedure, the receiver shall reject the message, and if possible, indicate appropriate cause in the corresponding unsuccessful outcome message. If such an IE is missing in the outcome message of a procedure, the receiver shall consider the procedure as unsuccessfully terminated and initiate local error handling. - -If a received message contains an unknown IE, the receiver should ignore the IE and process the rest of the message, unless specified otherwise in the document. - -If an erroroneous IE (which may be falsely present, or violates its range in definition) is detected in the initiating message of a procedure, the receiver shall reject the message, and if possible, indicate appropriate cause in the corresponding unsuccessful outcome message. If such an erroroneous IE is detected in the outcome message of a procedure, the receiver shall consider the procedure as unsuccessfully terminated and initiate local error handling. - -# --- 5 A1-related API - -## 5.1 Overview - -### 5.1.1 Protocol Stack - -In this version of specification, the default protocol stack for the A1 related APIs is shown on Figure 5.1.1-1. - -NOTE: the network layer for security protection is FFS. - -![Protocol stack for A1 related APIs diagram showing layers from Application down to Physical Layer.](562f471e8153729557e6a4ee6343c32c_img.jpg) - -| | -|-----------------| -| Application | -| gRPC | -| HTTP/2 | -| TCP | -| IP | -| Data Link Layer | -| Physical Layer | - -Protocol stack for A1 related APIs diagram showing layers from Application down to Physical Layer. - -**Figure 5.1.1-1: Protocol stack for A1 related APIs** - -The A1 related APIs use gRPC [5] with Protocol Buffers [4] as the application layer serialization protocol. - -### 5.1.2 List of A1 related APIs, procedures and messages - -The A1 related API procedures introduced in clause 9.2 of [2] are categorized under the A1 related APIs. These APIs include: - -- A1 Policy API: enabling A1 policy related operations for the xApps. -- A1 Enrichment Information (A1-EI) API: enabling A1-EI related operations for the xApps. - -These APIs are summarized in Table 5.1.2-1. - -**Table 5.1.2-1: List of A1 related APIs** - -| API Name | Description | -|---------------|----------------------------------------------------------| -| A1_Policy_API | Service for A1 policy related operations | -| A1_EI_API | Service for A1 enrichment information related operations | - -The table 5.1.2-2 lists the API procedures for each A1 related API. - -**Table 5.1.2-2: List of A1 related API procedures** - -| API Name | API procedure | Communication type | -|---------------|---------------------------|--------------------| -| A1_Policy_API | A1 Policy Setup | Request/Response | -| | A1 Policy Update | Request/Response | -| | A1 Policy Delete | Request/Response | -| | A1 Policy Query | Request/Response | -| | A1 Policy Status Update | Request/Response | -| A1_EI_API | A1 EI Subscription Setup | Request/Response | -| | A1 EI Subscription Update | Request/Response | -| | A1 EI Subscription Delete | Request/Response | -| | A1 EI Delivery | Notify | -| | A1 EI Query | Request/Response | - -The table 5.1.2-3 lists the messages for each A1 related API procedure. - -**Table 5.1.2-3: List of A1 related API messages** - -| API Procedure | Initiated by | Initiating Message | Outcome Message | | -|---------------|--------------|--------------------|--------------------|----------------------| -| | | | Successful Outcome | Unsuccessful Outcome | - -| | | | | | -|---------------------------|----------------------|-----------------------------------|--------------------------------------------|--------------------------------------------| -| A1 Policy Setup | Near-RT RIC platform | A1 POLICY SETUP REQUEST | A1 POLICY SETUP RESULT (SUCCESS) | A1 POLICY SETUP RESULT (FAILURE) | -| A1 Policy Update | Near-RT RIC platform | A1 POLICY UPDATE REQUEST | A1 POLICY UPDATE RESULT (SUCCESS) | A1 POLICY UPDATE RESULT (FAILURE) | -| A1 Policy Delete | Near-RT RIC platform | A1 POLICY DELETE REQUEST | A1 POLICY DELETE RESULT (SUCCESS) | A1 POLICY DELETE RESULT (FAILURE) | -| A1 Policy Query | Near-RT RIC platform | A1 POLICY QUERY REQUEST | A1 POLICY QUERY RESULT (SUCCESS) | A1 POLICY QUERY RESULT (FAILURE) | -| A1 Policy Status Update | xApp | A1 POLICY STATUS UPDATE | A1 POLICY STATUS UPDATE ACK | A1 POLICY STATUS UPDATE ERROR | -| A1 EI Subscription Setup | xApp | A1 EI SUBSCRIPTION SETUP REQUEST | A1 EI SUBSCRIPTION SETUP RESULT (SUCCESS) | A1 EI SUBSCRIPTION SETUP RESULT (FAILURE) | -| A1 EI Subscription Update | xApp | A1 EI SUBSCRIPTION UPDATE REQUEST | A1 EI SUBSCRIPTION UPDATE RESULT (SUCCESS) | A1 EI SUBSCRIPTION UPDATE RESULT (FAILURE) | -| A1 EI Subscription Delete | xApp | A1 EI SUBSCRIPTION DELETE REQUEST | A1 EI SUBSCRIPTION DELETE RESULT (SUCCESS) | A1 EI SUBSCRIPTION DELETE RESULT (FAILURE) | -| A1 EI Delivery | Near-RT RIC platform | A1 EI Delivery | - | - | -| A1 EI Query | xApp | A1 EI QUERY REQUEST | A1 EI QUERY RESULT (SUCCESS) | A1 EI QUERY RESULT (FAILURE) | - -## 5.2 A1-related API Procedures - -### 5.2.1 A1 Policy Setup procedure - -#### 5.2.1.1 General - -The purpose of the A1 Policy Setup procedure is to enable the execution of the transferred A1 policy. - -#### 5.2.1.2 Successful operation - -``` -@startuml -Skin rose -Participant rp as "Near-RT RIC Platform" -Participant ap as "xApp" - -rp->>ap: A1 POLICY SETUP REQUEST -ap->>rp: A1 POLICY SETUP RESULT\n[A1 Policy Setup Result=success] - -@enduml -``` - -![Sequence diagram for successful A1 Policy Setup procedure. The Near-RT RIC Platform sends an A1 POLICY SETUP REQUEST to the xApp. The xApp responds with an A1 POLICY SETUP RESULT message containing [A1 Policy Setup Result=success].](e9314c83043183351ed74908e9bf2f90_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC Platform - participant xApp - Near-RT RIC Platform->>xApp: A1 POLICY SETUP REQUEST - xApp-->>Near-RT RIC Platform: A1 POLICY SETUP RESULT -[A1 Policy Setup Result=success] - -``` - -Sequence diagram for successful A1 Policy Setup procedure. The Near-RT RIC Platform sends an A1 POLICY SETUP REQUEST to the xApp. The xApp responds with an A1 POLICY SETUP RESULT message containing [A1 Policy Setup Result=success]. - -Figure 5.2.1.2-1: A1 Policy Setup procedure, successful operation - -The Near-RT RIC Platform initiates the procedure by sending A1 POLICY SETUP REQUEST message to xApp. - -The A1 POLICY SETUP REQUEST message shall contain the information required by the xApp to setup one A1 policy including *A1 Policy Type ID IE*, *A1 Policy ID IE*, and *A1 Policy Object IE*. - -Upon reception of the A1 POLICY SETUP REQUEST message, the xApp shall transform the received A1 policy into appropriate E2 / A1-EI operation(s) requirements, and shall trigger Near-RT RIC Platform to accommodate E2 / A1-EI operation(s) requirements. - -If Near-RT RIC Platform is able to accommodate E2 / A1-EI operation(s) requirements, xApp replies A1 POLICY SETUP RESULT message with *A1 Policy Setup Result IE* set to *success* to Near-RT RIC Platform. And xApp should store the received *A1 Policy Type ID IE*, *A1 Policy ID IE*, *A1 Policy Object IE* as basic elements of A1 policy profile, and label the status of corresponding A1 policy as “enforced”. - -#### 5.2.1.3 Unsuccessful operation - -``` - -@startuml -Skin rose -Participant rp as "Near-RT RIC Platform" -Participant ap as "xApp" - -rp->ap: A1 POLICY SETUP REQUEST -ap->rp: A1 POLICY SETUP RESULT\n[A1 Policy Setup Result=failure] - -@enduml - -``` - -![Sequence diagram for unsuccessful A1 Policy Setup procedure. The Near-RT RIC Platform sends an A1 POLICY SETUP REQUEST to the xApp. The xApp responds with an A1 POLICY SETUP RESULT message containing [A1 Policy Setup Result=failure].](18442e4e239480f0c3c95b547aa8fde2_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC Platform - participant xApp - Near-RT RIC Platform->>xApp: A1 POLICY SETUP REQUEST - xApp-->>Near-RT RIC Platform: A1 POLICY SETUP RESULT -[A1 Policy Setup Result=failure] - -``` - -Sequence diagram for unsuccessful A1 Policy Setup procedure. The Near-RT RIC Platform sends an A1 POLICY SETUP REQUEST to the xApp. The xApp responds with an A1 POLICY SETUP RESULT message containing [A1 Policy Setup Result=failure]. - -Figure 5.2.1.3-1: A1 Policy Setup procedure, unsuccessful operation - -If xApp cannot transform the received A1 policy into appropriate E2 / A1-EI operation(s) requirements due to unsupported A1 policy type, xApp replies A1 POLICY SETUP RESULT message with *A1 Policy Setup Result IE* set to *failure* to Near-RT RIC Platform, possible with *Cause IE* set to *Not supported A1 policy type*. - -If xApp cannot transform the received A1 policy into appropriate E2 / A1-EI operation(s) requirements due to violation of of the requirements as stated in 5.2.1.2.2, 5.2.2.2.2, 5.2.3.2.2, 5.2.4.2.2, 5.2.5.2.2, 5.2.6.2.2, 5.2.7.2.2 and 5.2.8.2.2 of [7], xApp replies A1 POLICY SETUP RESULT message with *A1 Policy Setup Result IE* set to *failure* to Near-RT RIC Platform, possible with *Cause IE* set to *Not allowed statements, restrictions and extensions*. - -If Near-RT RIC Platform cannot accommodate E2 / A1-EI operation(s) requirements, xApp replies A1 POLICY SETUP RESULT message with *A1 Policy Setup Result* IE set to *failure* to Near-RT RIC Platform, possible with *Cause* IE set to *Near-RT RIC Platform cannot accommodate E2 / A1-EI operations requirements*. - -#### 5.2.1.4 Abnormal conditions - -If A1 policy indicated by *A1 Policy Type ID* IE, *A1 Policy ID* IE contained in A1 POLICY SETUP REQUEST message is being enforced by xApp, xApp replies A1 POLICY SETUP RESULT message with *A1 Policy Setup Result* IE set to *failure* to Near-RT RIC Platform, possible with *Cause* IE set to *A1 policy already enabled at xApp*. - -### 5.2.2 A1 Policy Update procedure - -#### 5.2.2.1 General - -The purpose of the A1 Policy Update procedure is to update the execution of the transferred A1 policy. - -#### 5.2.2.2 Successful operation - -``` -@startuml -Skin rose -Participant rp as "Near-RT RIC Platform" -Participant ap as "xApp" - -rp->>ap: A1 POLICY UPDATE REQUEST -ap->>rp: A1 POLICY UPDATE RESULT\n[A1 Policy Update Result=success] - -@enduml -``` - -![Sequence diagram showing the A1 Policy Update procedure. The Near-RT RIC Platform sends an A1 POLICY UPDATE REQUEST to the xApp, and the xApp responds with an A1 POLICY UPDATE RESULT message containing [A1 Policy Update Result=success].](af6be343f0c0a8f155f965dcf337b8af_img.jpg) - -``` -sequenceDiagram - participant Near-RT RIC Platform - participant xApp - Note left of Near-RT RIC Platform: Near-RT RIC Platform - Note right of xApp: xApp - Near-RT RIC Platform->>xApp: A1 POLICY UPDATE REQUEST - Note right of xApp: A1 POLICY UPDATE RESULT [A1 Policy Update Result=success] - xApp-->>Near-RT RIC Platform: A1 POLICY UPDATE RESULT [A1 Policy Update Result=success] - Note left of Near-RT RIC Platform: Near-RT RIC Platform - Note right of xApp: xApp -``` - -Sequence diagram showing the A1 Policy Update procedure. The Near-RT RIC Platform sends an A1 POLICY UPDATE REQUEST to the xApp, and the xApp responds with an A1 POLICY UPDATE RESULT message containing [A1 Policy Update Result=success]. - -Figure 5.2.2.2-1: A1 Policy Update procedure, successful operation - -The Near-RT RIC Platform initiates the procedure by sending A1 POLICY UPDATE REQUEST message to xApp. - -The A1 POLICY UPDATE REQUEST message shall contain the information required by the xApp to update one A1 policy including *A1 Policy Type ID* IE, *A1 Policy ID* IE, and *A1 Policy Object* IE. - -Upon reception of the A1 POLICY SETUP REQUEST message, the xApp shall transform the received A1 policy into appropriate E2 / A1-EI operation(s) requirements. If the transformed E2 / A1-EI operation(s) requirements are the same as before, xApp replies A1 POLICY UPDATE RESULT message with *A1 Policy Update Result* IE set to *success* to Near-RT RIC Platform; else, xApp shall trigger Near-RT RIC Platform to accommodate E2 / A1-EI operation(s) requirements. - -If Near-RT RIC Platform to accommodate E2 / A1-EI operation(s) requirements succeeds, xApp replies A1 POLICY UPDATE RESULT message with *A1 Policy Update Result* IE set to *success* to Near-RT RIC Platform. And xApp should update the stored information of *A1 Policy Object* IE of A1 policy profile, and label the status of corresponding A1 policy as “enforced”. - -#### 5.2.2.3 Unsuccessful operation - -``` -@startuml -Skin rose -Participant rp as "Near-RT RIC Platform" -Participant ap as "xApp" -``` - -``` - -rp->ap: A1 POLICY UPDATE REQUEST -ap->rp: A1 POLICY UPDATE RESULT\n[A1 Policy Update Result=failure] - -@enduml - -``` - -![Sequence diagram showing an unsuccessful A1 Policy Update procedure between Near-RT RIC Platform and xApp.](ff0952ef692c9d960ce5f6708bcc9711_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC Platform - participant xApp - Near-RT RIC Platform->>xApp: A1 POLICY UPDATE REQUEST - xApp-->>Near-RT RIC Platform: A1 POLICY UPDATE RESULT [A1 Policy Update Result=failure] - -``` - -Sequence diagram showing an unsuccessful A1 Policy Update procedure between Near-RT RIC Platform and xApp. - -**Figure 5.2.2.3-1: A1 Policy Update procedure, unsuccessful operation** - -If xApp cannot transform the received A1 policy into appropriate E2 / A1-EI operation(s) requirements due to not support the corresponding A1 policy type, xApp replies A1 POLICY UPDATE RESULT message with *A1 Policy Update Result* IE set to *failure* to Near-RT RIC Platform, possible with *Cause* IE set to *Not supported A1 policy type*. - -If xApp cannot transform the received A1 policy into appropriate E2 / A1-EI operation(s) requirements due to violation of the requirements as stated in 5.2.1.2.2, 5.2.2.2.2, 5.2.3.2.2, 5.2.4.2.2, 5.2.5.2.2, 5.2.6.2.2, 5.2.7.2.2 and 5.2.8.2.2 of [7], xApp replies A1 POLICY UPDATE RESULT message with *A1 Policy Update Result* IE set to *failure* to Near-RT RIC Platform, possible with *Cause* IE set to *Not allowed statements, restrictions and extensions*. - -If Near-RT RIC Platform cannot accommodate E2 / A1-EI operation(s) requirements, xApp replies A1 POLICY UPDATE RESULT message with *A1 Policy Update Result* IE set to *failure* to Near-RT RIC Platform, possible with *Cause* IE set to *Near-RT RIC Platform cannot accommodate E2 / A1-EI operations requirements*. - -#### 5.2.2.4 Abnormal conditions - -If A1 policy indicated by *A1 Policy Type ID* IE, *A1 Policy ID* IE contained in A1 POLICY UPDATE REQUEST message is not enabled by xApp, xApp replies A1 POLICY UPDATE RESULT message with *A1 Policy Update Result* IE set to *failure* to Near-RT RIC Platform, possible with *Cause* IE set to *Not enabled A1 policy at xApp*. - -### 5.2.3 A1 Policy Delete procedure - -#### 5.2.3.1 General - -The purpose of the A1 Policy Delete procedure is to terminate the execution of the transferred A1 policy. - -#### 5.2.3.2 Successful operation - -``` - -@startuml -Skin rose -Participant rp as "Near-RT RIC Platform" -Participant ap as "xApp" - -rp->ap: A1 POLICY DELETE REQUEST -ap->rp: A1 POLICY DELETE RESULT\n[A1 Policy Delete Result=success] - -@enduml - -``` - -![Sequence diagram for successful A1 Policy Delete procedure. The Near-RT RIC Platform sends an A1 POLICY DELETE REQUEST to the xApp. The xApp responds with an A1 POLICY DELETE RESULT message where A1 Policy Delete Result is set to success.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC Platform - participant xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform - Note over xApp: xApp - Near-RT RIC Platform->>xApp: A1 POLICY DELETE REQUEST - xApp-->>Near-RT RIC Platform: A1 POLICY DELETE RESULT [A1 Policy Delete Result=success] - Note over Near-RT RIC Platform: Near-RT RIC Platform - Note over xApp: xApp - -``` - -Sequence diagram for successful A1 Policy Delete procedure. The Near-RT RIC Platform sends an A1 POLICY DELETE REQUEST to the xApp. The xApp responds with an A1 POLICY DELETE RESULT message where A1 Policy Delete Result is set to success. - -**Figure 5.2.3.2-1: A1 Policy Delete procedure, successful operation** - -The Near-RT RIC Platform initiates the procedure by sending A1 POLICY DELETE REQUEST message to xApp. - -The A1 POLICY DELETE REQUEST message shall contain the information required by the xApp to delete one A1 policy including *A1 Policy Type ID IE*, *A1 Policy ID IE*. - -Upon reception of the A1 POLICY DELETE REQUEST message, the xApp shall locate the E2 / A1-EI operation(s) associated with the A1 policy indicated by *A1 Policy Type ID IE*, *A1 Policy ID IE* contained in A1 POLICY DELETE REQUEST message, and shall trigger Near-RT RIC Platform to terminate the accommodation of located E2 / A1-EI operation(s). - -No matter Near-RT RIC Platform to terminate the accommodation of located E2 / A1-EI operation(s) succeeds or not, xApp replies A1 POLICY DELETE RESULT message with *A1 Policy Delete Result IE* set to *success* to Near-RT RIC Platform. And xApp should delete the stored A1 policy profile associated. - -#### 5.2.3.3 Unsuccessful operation - -``` - -@startuml -Skin rose -Participant rp as "Near-RT RIC Platform" -Participant ap as "xApp" - -rp->>ap: A1 POLICY DELETE REQUEST -ap-->>rp: A1 POLICY DELETE RESULT\n[A1 Policy Delete Result=failure] - -@enduml - -``` - -![Sequence diagram for unsuccessful A1 Policy Delete procedure. The Near-RT RIC Platform sends an A1 POLICY DELETE REQUEST to the xApp. The xApp responds with an A1 POLICY DELETE RESULT message where A1 Policy Delete Result is set to failure.](d17f75945bbb3feb84a153ecfedb9b81_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC Platform - participant xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform - Note over xApp: xApp - Near-RT RIC Platform->>xApp: A1 POLICY DELETE REQUEST - xApp-->>Near-RT RIC Platform: A1 POLICY DELETE RESULT [A1 Policy Delete Result=failure] - Note over Near-RT RIC Platform: Near-RT RIC Platform - Note over xApp: xApp - -``` - -Sequence diagram for unsuccessful A1 Policy Delete procedure. The Near-RT RIC Platform sends an A1 POLICY DELETE REQUEST to the xApp. The xApp responds with an A1 POLICY DELETE RESULT message where A1 Policy Delete Result is set to failure. - -**Figure 5.2.3.3-1: A1 Policy Delete procedure, unsuccessful operation** - -If xApp cannot locate the E2 / A1-EI operation(s) associated with the A1 policy indicated by *A1 Policy Type ID IE*, *A1 Policy ID IE* contained in A1 POLICY DELETE REQUEST message, xApp replies A1 POLICY DELETE RESULT message with *A1 Policy Delete Result IE* set to *failure* to Near-RT RIC Platform, possible with *Cause IE* set to *Not enabled A1 policy at xApp*. - -#### 5.2.3.4 Abnormal conditions - -Not applicable. - -## 5.3 Elements for A1-related API Communication - -### 5.3.1 General - -### 5.3.2 Message Functional Definition and Content - -#### 5.3.2.1 A1 POLICY SETUP REQUEST - -This message is sent by the RIC Platform and is used to request the destined xApp to enable the execution of the nested A1 policy. - -Direction: RIC Platform → xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 5.3.3.1 | | -| A1 Policy Type ID | M | | 5.3.3.2 | | -| A1 Policy ID | M | | 5.3.3.3 | | -| A1 Policy Object | M | | OCTET
STRING | Defined in [7]. | - -#### 5.3.2.2 A1 POLICY SETUP RESULT - -This message is sent by the xApp as response to the request to enable the execution of the nested A1 policy. - -Direction: xApp → RIC Platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Message Type | M | | 5.3.3.1 | | -| A1 Policy Type ID | M | | 5.3.3.2 | | -| A1 Policy ID | M | | 5.3.3.3 | | -| A1 Policy Setup Result | M | | 5.3.3.4 | | -| Cause | O | | 5.3.3.5 | | -| A1 Policy Object | C | | OCTET
STRING | Defined in [7].
This IE shall present if the A1 Policy Setup Result IE is set to success.
When present, this IE is copied from the corresponding Request message. | - -#### 5.3.2.3 A1 POLICY UPDATE REQUEST - -This message is sent by the RIC Platform and is used to request the destined xApp to update the execution of the nested A1 policy. - -Direction: RIC Platform → xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 5.3.3.1 | | -| A1 Policy Type ID | M | | 5.3.3.2 | | -| A1 Policy ID | M | | 5.3.3.3 | | -| A1 Policy Object | M | | OCTET
STRING | Defined in [7]. | - -#### 5.3.2.4 A1 POLICY UPDATE RESULT - -This message is sent by xApp as response to the request to update the execution of the nested A1 policy. - -Direction: xApp → RIC Platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Message Type | M | | 5.3.3.1 | | -| A1 Policy Type ID | M | | 5.3.3.2 | | -| A1 Policy ID | M | | 5.3.3.3 | | -| A1 Policy Update Result | M | | 5.3.3.4 | | -| Cause | O | | 5.3.3.5 | | -| A1 Policy Object | C | | OCTET
STRING | Defined in [7].
This IE shall present if the A1 Policy Update Result IE is set to success.
When present, this IE is copied from the corresponding Request message. | - -#### 5.3.2.5 A1 POLICY DELETE REQUEST - -This message is sent by the RIC Platform and is used to request the destined xApp to terminate the execution of the nested A1 policy. - -Direction: RIC Platform → xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 5.3.3.1 | | -| A1 Policy Type ID | M | | 5.3.3.2 | | -| A1 Policy ID | M | | 5.3.3.3 | | - -#### 5.3.2.6 A1 POLICY DELETE RESULT - -This message is sent by xApp as response to the request to terminate the execution of the nested A1 policy. - -Direction: xApp → RIC Platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 5.3.3.1 | | -| A1 Policy Type ID | M | | 5.3.3.2 | | -| A1 Policy ID | M | | 5.3.3.3 | | -| A1 Policy Delete Result | M | | 5.3.3.4 | | -| Cause | O | | 5.3.3.5 | | - -- 5.3.2.7 A1 POLICY QUERY REQUEST -- 5.3.2.8 A1 POLICY QUERY RESULT -- 5.3.2.9 A1 POLICY STATUS UPDATE -- 5.3.2.10 A1 POLICY STATUS UPDATE ACK -- 5.3.2.11 A1 POLICY STATUS UPDATE ERROR - -- 5.3.2.12 A1-EI SUBSCRIPTION SETUP REQUEST -- 5.3.2.13 A1-EI SUBSCRIPTION SETUP RESULT -- 5.3.2.14 A1-EI SUBSCRIPTION UPDATE REQUEST -- 5.3.2.15 A1-EI SUBSCRIPTION UPDATE RESULT -- 5.3.2.16 A1-EI SUBSCRIPTION DELETE REQUEST -- 5.3.2.17 A1-EI SUBSCRIPTION DELETE RESULT -- 5.3.2.18 A1-EI DELIVERY - -- 5.3.2.19 A1-EI QUERY REQUEST -- 5.3.2.20 A1-EI QUERY RESULT - -### 5.3.3 Information Element Definitions - -#### 5.3.3.1 Message Type - -The Message Type IE identifies the message being sent. It is mandatory for all messages. - -| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | -|------------------|----------|-------|-------------------------------------------------------------------|-----------------------------------------------------------------------| -| Message Type | | | | | -| >Procedure Type | M | | CHOICE (A1 policy setup, A1 policy update, A1 policy delete, ...) | | -| >Type of Message | M | | CHOICE (Request, Result, ...) | Refer to Table 5.1.2-3 for applicable choices for each procedure type | - -#### 5.3.3.2 A1 Policy Type ID - -Defined in 10.1.5. - -#### 5.3.3.3 A1 Policy ID - -The A1 Policy ID IE identifies one A1 policy under one A1 policy type. - -| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | -|---------------|----------|-------|-----------------------|-----------------------| -| A1 Policy ID | M | | STRING | | - -#### 5.3.3.4 Result - -The Result IE indicates the procedure succeeds or not. - -| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | -|---------------|----------|-------|------------------------------------|-----------------------| -| Result | M | | ENUMERATED (success, failure, ...) | | - -#### 5.3.3.5 Cause - -The Cause IE indicates the reason for a particular event in A1-related API. - -| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | -|------------------------------|----------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| -| CHOICE Cause Group | M | | | | -| >A1-related API Layer | | | | | -| >>A1-related API Layer Cause | M | | ENUMERATED (Unspecified A1-related API layer reason, Not supported A1 policy type, Not allowed statements, restrictions and extensions, Near-RT RIC Platform cannot accommodate E2 / A1-EI operations requirements, A1 policy already enabled at xApp, Not enabled A1 policy at xApp, ...) | | -| >Transport Layer | | | | | -| >>Transport Layer Cause | M | | ENUMERATED (Unspecified transport layer reason, Transport Resource Unavailable, ...) | | -| >Protocol | | | | | -| >>Protocol Cause | M | | ENUMERATED (Unspecified protocol reason, Transfer Syntax Error, Abstract Syntax Error (Reject), Abstract Syntax Error (Ignore and Notify), Message not Compatible with Receiver State, Semantic Error, Abstract Syntax Error (Falsely Constructed Message), ...) | | -| >Misc | | | | | -| >>Miscellaneous Cause | M | | ENUMERATED (Unspecified miscellaneous reason, Control Processing Overload, Hardware failure, O&M intervention, ...) | | - -The meaning of the different cause values is described in the following table. In general, “not supported” cause values indicate that the related capability is missing. On the other hand, “not available” cause values indicate that the related capability is present, but insufficient resources were available to perform the requested action. - -| A1-related API Layer cause | Meaning | -|----------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------| -| Unspecified A1-related API layer reason | Sent for A1-related API layer cause when none of the specified cause values applies. | -| Not supported A1 policy type | The A1 policy type is not supported. | -| Not allowed statements, restrictions and extensions | The A1 policy object is illegal due to violation of statements, restrictions and extensions required for corresponding A1 policy type. | -| Near-RT RIC Platform cannot accommodate E2 / A1-EI operations requirements | The RIC platform failed to setup xApp's requested E2 / A1-EI operation(s). | -| A1 policy already enabled at xApp | The A1 policy indicated by A1 Policy Type ID and A1 Policy ID is enforced already. | -| Not enabled A1 policy at xApp | The A1 policy indicated by A1 Policy Type ID and A1 Policy ID is not enforced. | - -| Transport Layer cause | Meaning | -|------------------------------------|---------------------------------------------------------------------------------| -| Unspecified transport layer reason | Sent for transport layer cause when none of the specified cause values applies. | -| Transport Resource Unavailable | The required transport resources are not available. | - -| Protocol cause | Meaning | -|-----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| -| Unspecified protocol reason | Sent for protocol cause when none of the specified cause values applies. | -| Transfer Syntax Error | The received message included a transfer syntax error. | -| Abstract Syntax Error (Reject) | The received message included an abstract syntax error and the concerning criticality indicated “reject”. | -| Abstract Syntax Error (Ignore And Notify) | The received message included an abstract syntax error and the concerning criticality indicated “ignore and notify”. | -| Message Not Compatible With Receiver State | The received message was not compatible with the receiver state. | -| Semantic Error | The received message included a semantic error. | -| Abstract Syntax Error (Falsely Constructed Message) | The received message contained IEs or IE groups in wrong order or with too many occurrences. | - -| Miscellaneous cause | Meaning | -|----------------------------------|-------------------------------------------------------------------------------| -| Unspecified miscellaneous reason | Sent for miscellaneous cause when none of the specified cause values applies. | -| Control Processing Overload | Control processing overload | -| Hardware Failure | Action related to hardware failure | -| O&M Intervention | The action is due to O&M intervention. | - -### 5.3.4 Message and Information Element Abstract Syntax - -#### 5.3.4.1 Solution 1: gRPC with Protocol Buffers - -##### 5.3.4.1.1 Usage of gRPC with Protocol Buffers - -This solution uses Protocol Buffers as message encoding, and also as the Interface Definition Language (IDL) for gRPC [5]. - -Table 5.3.4.1.1-1 lists the mapping of A1-related APIs and corresponding gRPC services. - -**Table 5.3.4.1.1-1: Mapping of A1-related APIs and gRPC services** - -| API Name | gRPC service(s) | -|---------------|-----------------| -| A1_Policy_API | A1_Policy_API | - -A procedure of an A1-related API is mapped to a *gRPC method*. - -Table 5.3.4.1.1-2 lists the A1-related APIs abstract syntax included in this document. - -**Table 5.3.4.1.1-2: List of A1-related APIs abstract syntax** - -| API Name / Contents | Clause | Version | File Name | -|---------------------------------------------|-------------|---------|---------------------------------------------| -| A1_Policy_API | 5.3.4.1.2.1 | 1.0.0 | a1_policy_api_ver_1_0_0.proto | -| A1-related API common information elements | 5.3.4.1.3 | 1.0.0 | a1_related_apis_common_ies_ver_1_0_0.proto | -| Near-RT RIC API common information elements | 10.2.1 | 3.0.0 | near_rt_ric_apis_common_ies_ver_3_0_0.proto | - -##### 5.3.4.1.2 API Definitions - -###### 5.3.4.1.2.1 A1\_Policy\_API - -``` - -syntax = "proto3"; - -package ricapi.a1_policy_api.v1; - -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; -import "a1_related_apis_common_ies_ver_1_0_0.proto"; - -// gRPC service and rpc definition -service A1_Policy_API { - rpc A1PolicySetupProc(A1PolicySetupInitMsg) returns (A1PolicySetupOutMsg) {}; - rpc A1PolicyUpdateProc(A1PolicyUpdateInitMsg) returns (A1PolicyUpdateOutMsg) {}; - rpc A1PolicyDeleteProc(A1PolicyDeleteInitMsg) returns (A1PolicyDeleteOutMsg) {}; -} - -message A1PolicySetupInitMsg { - optional A1PolicySetupRequest a1_policy_setup_request = 1; -} - -message A1PolicySetupOutMsg { - oneof type_of_message { - A1PolicySetupResult a1_policy_setup_result = 1; - } -} - -message A1PolicyUpdateInitMsg { - optional A1PolicyUpdateRequest a1_policy_update_request = 1; -} - -message A1PolicyUpdateOutMsg { - oneof type_of_message { - A1PolicyUpdateResult a1_policy_update_result = 1; - } -} - -message A1PolicyDeleteInitMsg { - optional A1PolicyDeleteRequest a1_policy_delete_request = 1; -} - -message A1PolicyDeleteOutMsg { - oneof type_of_message { - A1PolicyDeleteResult a1_policy_delete_result = 1; - } -} - -``` - -``` - -// ----- messages of al_policy_API ----- -// ----- messages of Al Policy Setup procedure ----- -message AlPolicySetupRequest { - optional near_rt_ric_apis_common_ies.v3.AlPolicyTypeId al_policy_type_id = 1; - optional al_related_apis_common_ies.v1.AlPolicyId al_policy_id = 2; - optional al_related_apis_common_ies.v1.AlPolicyObject al_policy_object = 3; -} - -message AlPolicySetupResult { - optional near_rt_ric_apis_common_ies.v3.AlPolicyTypeId al_policy_type_id = 1; - optional al_related_apis_common_ies.v1.AlPolicyId al_policy_id = 2; - optional al_related_apis_common_ies.v1.Result al_policy_setup_result = 3; - optional al_related_apis_common_ies.v1.Cause cause = 4; - optional al_related_apis_common_ies.v1.AlPolicyObject al_policy_object = 5; -} - -// ----- messages of Al Policy Update procedure ----- -message AlPolicyUpdateRequest { - optional near_rt_ric_apis_common_ies.v3.AlPolicyTypeId al_policy_type_id = 1; - optional al_related_apis_common_ies.v1.AlPolicyId al_policy_id = 2; - optional al_related_apis_common_ies.v1.AlPolicyObject al_policy_object = 3; -} - -message AlPolicyUpdateResult { - optional near_rt_ric_apis_common_ies.v3.AlPolicyTypeId al_policy_type_id = 1; - optional al_related_apis_common_ies.v1.AlPolicyId al_policy_id = 2; - optional al_related_apis_common_ies.v1.Result al_policy_update_result = 3; - optional al_related_apis_common_ies.v1.Cause cause = 4; - optional al_related_apis_common_ies.v1.AlPolicyObject al_policy_object = 5; -} - -// ----- messages of Al Policy Delete procedure ----- -message AlPolicyDeleteRequest { - optional near_rt_ric_apis_common_ies.v3.AlPolicyTypeId al_policy_type_id = 1; - optional al_related_apis_common_ies.v1.AlPolicyId al_policy_id = 2; -} - -message AlPolicyDeleteResult { - optional near_rt_ric_apis_common_ies.v3.AlPolicyTypeId al_policy_type_id = 1; - optional al_related_apis_common_ies.v1.AlPolicyId al_policy_id = 2; - optional al_related_apis_common_ies.v1.Result al_policy_delete_result = 3; - optional al_related_apis_common_ies.v1.Cause cause = 4; -} - -``` - -##### 5.3.4.1.3 Information Element Definitions - -``` - -syntax = "proto3"; - -package ricapi.al_related_apis_common_ies.v1; - -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; -// ----- Information Elements ----- -// -----A----- -message AlPolicyObject { - optional string value = 1; -} - -message AlPolicyId { - optional string value = 1; -} - -// -----C----- -message Cause { - oneof cause_group { - AlRelatedApiLayerCause al_related_api_layer_cause = 1; - TransportLayerCause transport_layer_cause = 2; - ProtocolLayerCause protocol_layer_cause = 3; - MiscCause misc_cause = 4; - } -} - -``` - -``` -enum A1RelatedApiLayerCause { - A1_RELATED_API_LAYER_UNSPECIFIED = 0; - NOT_SUPPORTED_A1_POLICY_TYPE = 1; - NOT_ALLOWED_STATEMENTS_RESTRICTIONS_AND_EXTENSIONS = 2; - NEAR_RT_RIC_PLATFORM_CANNOT_ACCOMMODATE_E2_A1_EI_OPERATIONS_REQUIREMENTS = 3; - A1_POLICY_ALREADY_ENABLED_AT_XAPP = 4; - NOT_ENABLED_A1_POLICY_AT_XAPP = 5; -} - -enum TransportLayerCause { - TRANSPORT_UNSPECIFIED = 0; - TRANSPORT_RESOURCE_UNAVAILABLE = 1; -} - -enum ProtocolLayerCause { - PROTOCOL_UNSPECIFIED = 0; - TRANSFER_SYNTAX_ERROR = 1; - ABSTRACT_SYNTAX_ERROR_REJECT = 2; - ABSTRACT_SYNTAX_ERROR_IGNORE_AND_NOTIFY = 3; - MESSAGE_NOT_COMPATIBLE_WITH_RECEIVER_STATE = 4; - SEMANTIC_ERROR = 5; - ABSTRACT_SYNTAX_ERROR_FALSELY_CONSTRUCTED_MESSAGE = 6; -} - -enum MiscCause { - MISC_UNSPECIFIED = 0; - CONTROL_PROCESSING_OVERLOAD = 1; - HARDWARE_FAILURE = 2; - OAM_INTERVENTION = 3; -} -} - - // R -enum Result { - RESULT_SUCCESS = 0; - RESULT_FAILURE = 1; -} -``` - -### 5.3.5 Message Transfer Syntax - -#### 5.3.5.1 Solution 1: gRPC with Protocol Buffers - -The message transfer syntax for Solution 1 is serialized Protocol Buffers [4]. - -# --- 6 E2-related API - -## 6.1 Overview - -### 6.1.1 Protocol Stack - -In this version of specification, the default and optional protocol stacks for the E2 related APIs are shown on Figure 6.1.1-1. - -NOTE: The security protocols are specified in [6]. - -![Protocol stack diagram for E2 related APIs showing layers from Application down to Physical Layer.](d734a6ea1b381280f043fcf70391b6db_img.jpg) - -| | -|-----------------| -| Application | -| gRPC | -| HTTP/2 | -| TCP | -| IP | -| Data Link Layer | -| Physical Layer | - -Protocol stack diagram for E2 related APIs showing layers from Application down to Physical Layer. - -**Figure 6.1.1-1: Protocol stacks for E2 related APIs** - -The E2-related APIs use gRPC [5] with Protocol Buffers [4] as the application layer serialization protocol. - -### 6.1.2 List of E2 related APIs, procedures and messages - -The E2 related API procedures introduced in clause 9.3 of [2] are categorized under the E2 related APIs. These APIs include: - -- E2 Subscription API: enabling xApp to setup, modify and delete E2 subscriptions with the Near-RT RIC platform. -- E2 Indication API: enabling xApp to receive E2 indications associated with an E2 subscription. -- E2 Control API: enabling xApp to consume E2 control service from the Near-RT RIC platform. -- E2 Guidance API: enabling xApp to acquire E2 related guidance from the Near-RT RIC platform and mitigate potential conflicts with other xApps. -- E2 Query API: enabling xApp to consume E2 query service from the Near-RT RIC platform. - -These APIs are summarized in Table 6.1.2-1. - -**Table 6.1.2-1: List of E2 related APIs** - -| API Name | Description | -|---------------------|-------------------------------------------------------------------------------------------------------------------| -| E2_Subscription_API | Near-RT RIC platform service for subscription of E2 REPORT, INSERT and POLICY services | -| E2_Indication_API | Near-RT RIC platform service for delivery of subscribed information associated with E2 REPORT and INSERT services | -| E2_Control_API | Near-RT RIC platform service for E2 CONTROL | -| E2_Guidance_API | Near-RT RIC platform service for E2 related guidance | -| E2_Query_API | Near-RT RIC platform service for E2 QUERY | - -The table 6.1.2-2 lists the API procedures for each E2 related API. - -**Table 6.1.2-2: List of E2 related API procedures** - -| API Name | API procedure | Communication type | -|---------------------|-------------------------------------|--------------------| -| E2_Subscription_API | E2 Subscription | Request/Response | -| | E2 Subscription Delete | Request/Response | -| | E2 Subscription Delete Query | Request/Response | -| | E2 Subscription Delete Notification | Notify | -| | E2 Subscription Modification | Request/Response | -| E2_Indication_API | E2 Indication | Notify | -| E2_Control_API | E2 Control | Request/Response | -| E2_Guidance_API | E2 Guidance | Request/Response | -| | E2 Guidance Modification | Notify | -| E2_Query_API | E2 Query | Request/Response | - -The table 6.1.2-3 lists the messages for each E2 related API procedure. - -**Table 6.1.2-3: List of E2 related API messages** - -| API Procedure | Initiated by | Initiating Message | Outcome Message | | | -|-------------------------------------|----------------------|--------------------------------------|--------------------------------------|--------------------------------------|-------------------------------------| -| | | | Successful Outcome | Unsuccessful Outcome 1 | Unsuccessful Outcome 2 | -| E2 Subscription | xApp | E2 SUBSCRIPTION REQUEST | E2 SUBSCRIPTION SUCCESS | E2 SUBSCRIPTION FAILURE | E2 SUBSCRIPTION REJECT | -| E2 Subscription Delete | xApp | E2 SUBSCRIPTION DELETE REQUEST | E2 SUBSCRIPTION DELETE SUCCESS | E2 SUBSCRIPTION DELETE FAILURE | E2 SUBSCRIPTION DELETE REJECT | -| E2 Subscription Delete Query | Near-RT RIC platform | E2 SUBSCRIPTION DELETE REQUIRED | E2 SUBSCRIPTION DELETE ACCEPT | E2 SUBSCRIPTION DELETE DECLINE | - | -| E2 Subscription Delete Notification | Near-RT RIC platform | E2 SUBSCRIPTION DELETE NOTIFICATION | - | - | - | -| E2 Subscription Modification | xApp | E2 SUBSCRIPTION MODIFICATION REQUEST | E2 SUBSCRIPTION MODIFICATION SUCCESS | E2 SUBSCRIPTION MODIFICATION FAILURE | E2 SUBSCRIPTION MODIFICATION REJECT | -| E2 Indication | Near-RT RIC platform | E2 INDICATION PUSH | - | E2 INDICATION FAILURE | - | -| E2 Control | xApp | E2 CONTROL REQUEST | E2 CONTROL SUCCESS | E2 CONTROL FAILURE | E2 CONTROL REJECT | -| E2 Guidance | xApp | E2 GUIDANCE REQUEST | E2 GUIDANCE SUCCESS | - | - | -| E2 Guidance Modification | Near-RT RIC platform | E2 GUIDANCE MODIFICATION | - | - | - | -| E2 Query | xApp | E2 QUERY REQUEST | E2 QUERY SUCCESS | E2 QUERY FAILURE | E2 QUERY REJECT | - -## 6.2 E2-related API Procedures - -### 6.2.1 E2\_Subscription\_API procedures - -#### 6.2.1.1 E2 Subscription Procedure - -##### 6.2.1.1.1 General - -This procedure is used by an xApp to request an E2 subscription to Near-RT RIC platform. - -##### 6.2.1.1.2 Successful Operation - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: E2 SUBSCRIPTION (Request) -near -> app: E2 SUBSCRIPTION (Success) -@enduml - -``` - -![Sequence diagram showing the successful operation of the E2 Subscription procedure. The xApp sends an E2 SUBSCRIPTION (Request) message to the Near-RT RIC Platform, and the platform responds with an E2 SUBSCRIPTION (Success) message.](e7c6a6e4c3047dac05a3b92e396e9794_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - xApp->>Near-RT RIC Platform: E2 SUBSCRIPTION (Request) - Near-RT RIC Platform-->>xApp: E2 SUBSCRIPTION (Success) - -``` - -Sequence diagram showing the successful operation of the E2 Subscription procedure. The xApp sends an E2 SUBSCRIPTION (Request) message to the Near-RT RIC Platform, and the platform responds with an E2 SUBSCRIPTION (Success) message. - -**Figure 6.2.1.1.2-1: E2 Subscription procedure, successful operation** - -The xApp initiates the procedure by sending an E2 SUBSCRIPTION (Request) message to the Near-RT-RIC platform. The message contains a unique *Procedure Transaction ID* IE assigned by the initiating xApp, the *Global E2 Node ID* IE, the *RAN Function ID* IE, and the *E2 Subscription Details* IE including one or more requested E2 actions and optionally the *E2 Subscription Timer* IE. The message may include the *E2 Indication Destination* IE which specifies the xApp's endpoint to receive E2 indications (see clause 6.2.2.1), and the *E2 Subscription Delete Notification Destination* IE which specifies the xApp's endpoint to receive query/notification from the Near-RT RIC platform for E2 subscription deletion (see clause 6.2.1.3/6.2.1.4). - -NOTE: When execution order of multiple actions is not concerned, it is recommended that an E2 Subscription procedure contains a single action, to allow efficient reuse of E2 subscriptions. - -At reception of the E2 SUBSCRIPTION (Request) message, the Near-RT-RIC platform shall: - -- Search existing E2 subscription(s) for matched *Global E2 Node ID* IE, *RAN Function ID* IE and matched contents in *E2 Subscription Details* IE. If a matched E2 subscription exists, add the initiating xApp as a new subscriber of the E2 subscription. -- Initiate appropriate E2AP procedure(s) to establish RIC subscription with the target E2 Node, if existing E2 subscriptions are insufficient to fulfill the request. - -The Near-RT-RIC platform may use the value in the *E2 Subscription Timer* IE, if present, as a one-time value of the E2AP timer $T_{RICEVENTcreate}$ in clause 9.5 of [3], which is valid only for this transaction. - -If the subscription request is successfully fulfilled, the Near-RT RIC platform shall send an E2 SUBSCRIPTION (Success) message back to the xApp. Similar to [3], a successfully fulfilled request shall be sent if the E2 event trigger and at least one requested E2 action are admitted. - -In the E2 SUBSCRIPTION (Success) message, Near-RT RIC platform shall include the associated *Procedure Transaction ID* IE, *Global E2 Node ID* IE, *RAN Function ID* IE and an *E2 Request ID* IE assigned by the Near-RT RIC platform. The message - -shall also indicate the admitted E2 action(s) in the *Actions Admitted List* IE, each with the associated *E2 Action ID* IE assigned by the Near-RT RIC platform. The same *E2 Request ID* IE and *E2 Action ID* IE shall be present in any subsequent E2 INDICATION message(s). The message shall indicate, if exist, the E2 action(s) not admitted in the *Actions Not Admitted List* IE with appropriate cause(s). - -##### 6.2.1.1.3 Unsuccessful Operation - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: E2 SUBSCRIPTION (Request) -near -> app: E2 SUBSCRIPTION (Reject) -@enduml -``` - -![Sequence diagram for E2 Subscription procedure, unsuccessful operation (Reject). It shows an xApp sending an E2 SUBSCRIPTION (Request) to a Near-RT RIC Platform, which responds with an E2 SUBSCRIPTION (Reject).](e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg) - -``` -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: E2 SUBSCRIPTION (Request) - Near-RT RIC Platform-->>xApp: E2 SUBSCRIPTION (Reject) - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform -``` - -Sequence diagram for E2 Subscription procedure, unsuccessful operation (Reject). It shows an xApp sending an E2 SUBSCRIPTION (Request) to a Near-RT RIC Platform, which responds with an E2 SUBSCRIPTION (Reject). - -**Figure 6.2.1.1.3-1: E2 Subscription procedure, unsuccessful operation (Reject)** - -If the subscription request is rejected by the Near-RT RIC platform, an E2 SUBSCRIPTION (Reject) message shall be sent back to the xApp. The message shall include associated *Procedure Transaction ID* IE which is replicated from the corresponding request, the *Global E2 Node ID* IE, the *RAN Function ID* IE and appropriate *Cause* IE. - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: E2 SUBSCRIPTION (Request) -near -> app: E2 SUBSCRIPTION (Failure) -@enduml -``` - -![Sequence diagram for E2 Subscription procedure, unsuccessful operation (Failure). It shows an xApp sending an E2 SUBSCRIPTION (Request) to a Near-RT RIC Platform, which responds with an E2 SUBSCRIPTION (Failure).](bb3354f497635d15bef873577125c48d_img.jpg) - -``` -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: E2 SUBSCRIPTION (Request) - Near-RT RIC Platform-->>xApp: E2 SUBSCRIPTION (Failure) - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform -``` - -Sequence diagram for E2 Subscription procedure, unsuccessful operation (Failure). It shows an xApp sending an E2 SUBSCRIPTION (Request) to a Near-RT RIC Platform, which responds with an E2 SUBSCRIPTION (Failure). - -**Figure 6.2.1.1.3-2: E2 Subscription procedure, unsuccessful operation (Failure)** - -If the subscription request fails due to failure in E2AP procedure, the Near-RT RIC platform shall send an E2 SUBSCRIPTION (Failure) message back to the xApp. The message shall include the associated *Procedure Transaction ID* IE which is replicated from the corresponding request, *Global E2 Node ID* IE, *RAN Function ID* IE and appropriate cause. - -##### 6.2.1.1.4 Abnormal Conditions - -Not applicable. - -#### 6.2.1.2 E2 Subscription Delete Procedure, xApp initiated - -##### 6.2.1.2.1 General - -This procedure is used by an xApp to unsubscribe from an E2 subscription on Near-RT RIC platform. - -##### 6.2.1.2.2 Successful Operation - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: E2 SUBSCRIPTION DELETE (Request) -near -> app: E2 SUBSCRIPTION DELETE (Success) -@enduml -``` - -![Sequence diagram showing the successful E2 Subscription Delete procedure. The xApp sends an E2 SUBSCRIPTION DELETE (Request) message to the Near-RT RIC Platform, which responds with an E2 SUBSCRIPTION DELETE (Success) message.](e29665b8abcea967ef289c6aff07ae4c_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: E2 SUBSCRIPTION DELETE (Request) - Near-RT RIC Platform-->>xApp: E2 SUBSCRIPTION DELETE (Success) - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram showing the successful E2 Subscription Delete procedure. The xApp sends an E2 SUBSCRIPTION DELETE (Request) message to the Near-RT RIC Platform, which responds with an E2 SUBSCRIPTION DELETE (Success) message. - -**Figure 6.2.1.2.2-1: E2 Subscription Delete procedure (xApp initiated), successful operation** - -The xApp initiates the procedure by sending the E2 SUBSCRIPTION DELETE (Request) message to the Near-RT-RIC platform. The message contains the *Global E2 Node ID IE* and the *E2 Request ID IE* to indicate the target E2 subscription and optionally the *E2 Subscription Delete Timer IE*. - -At reception of the E2 SUBSCRIPTION DELETE (Request) message, the Near-RT-RIC platform shall, if the delete request is accepted by the Near-RT-RIC platform: - -- Check for other subscriber(s) of the target E2 subscription. If such subscriber(s) exists, the E2 subscription shall be maintained by the Near-RT RIC platform but no longer serve the initiating xApp; if not, the E2 subscription shall be deleted. -- Initiate appropriate E2AP procedure(s) with the target E2 Node, if necessary, to map the change in the target E2 subscription to its corresponding RIC subscription. - -The Near-RT-RIC platform may use the value in the *E2 Subscription Delete Timer IE*, if present, as a one-time value of the E2AP timer $T_{RICEVENT_{delete}}$ in clause 9.5 of [3], which is valid only for this transaction. - -Upon success of the above processing for the target E2 subscription, the Near-RT RIC platform shall stop delivering its associated E2 INDICATION message(s) to the initiating xApp and respond the xApp with an E2 SUBSCRIPTION DELETE(Success) message. The E2 SUBSCRIPTION DELETE (Success) message shall include the same *Global E2 Node ID IE* and *E2 Request ID IE* from the request message. - -##### 6.2.1.2.3 Unsuccessful Operation - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: E2 SUBSCRIPTION DELETE (Request) -``` - -``` -near -> app: E2 SUBSCRIPTION DELETE (Reject) -@enduml -``` - -![Sequence diagram for E2 Subscription Delete procedure (xApp initiated), unsuccessful operation (Reject). The diagram shows an xApp sending an E2 SUBSCRIPTION DELETE (Request) to a Near-RT RIC Platform, which responds with an E2 SUBSCRIPTION DELETE (Reject).](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - xApp->>Near-RT RIC Platform: E2 SUBSCRIPTION DELETE (Request) - Near-RT RIC Platform-->>xApp: E2 SUBSCRIPTION DELETE (Reject) - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for E2 Subscription Delete procedure (xApp initiated), unsuccessful operation (Reject). The diagram shows an xApp sending an E2 SUBSCRIPTION DELETE (Request) to a Near-RT RIC Platform, which responds with an E2 SUBSCRIPTION DELETE (Reject). - -**Figure 6.2.1.2.3-1: E2 Subscription Delete procedure (xApp initiated), unsuccessful operation (Reject)** - -If the Near-RT RIC platform rejects the request message, an E2 SUBSCRIPTION (Reject) message shall be sent back to the initiating xApp. The message shall include associated *Procedure Transaction ID IE* which is replicated from the corresponding request, the *Global E2 Node ID IE*, the *RAN Function ID IE* and appropriate *Cause IE*. - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: E2 SUBSCRIPTION DELETE (Request) -near -> app: E2 SUBSCRIPTION DELETE (Failure) -@enduml -``` - -![Sequence diagram for E2 Subscription Delete procedure (xApp initiated), unsuccessful operation (Failure). The diagram shows an xApp sending an E2 SUBSCRIPTION DELETE (Request) to a Near-RT RIC Platform, which responds with an E2 SUBSCRIPTION DELETE (Failure).](805c475f0859e607af0530ba43194bf1_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - xApp->>Near-RT RIC Platform: E2 SUBSCRIPTION DELETE (Request) - Near-RT RIC Platform-->>xApp: E2 SUBSCRIPTION DELETE (Failure) - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for E2 Subscription Delete procedure (xApp initiated), unsuccessful operation (Failure). The diagram shows an xApp sending an E2 SUBSCRIPTION DELETE (Request) to a Near-RT RIC Platform, which responds with an E2 SUBSCRIPTION DELETE (Failure). - -**Figure 6.2.1.2.3-2: E2 Subscription Delete procedure (xApp initiated), unsuccessful operation (Failure)** - -If the associated E2AP procedure(s) fails for the E2 subscription, the Near-RT RIC platform shall send an E2 SUBSCRIPTION DELETE (Failure) message back to the initiating xApp. The message shall include associated *Procedure Transaction ID IE* which is replicated from the corresponding request, the *Global E2 Node ID IE*, the *RAN Function ID IE* and appropriate *Cause IE*. - -##### 6.2.1.2.4 Abnormal Conditions - -Not applicable. - -#### 6.2.1.3 E2 Subscription Delete Query procedure - -##### 6.2.1.3.1 General - -This procedure is used by Near-RT RIC platform to consult the xApp about deleting an existing E2 subscription. - -##### 6.2.1.3.2 Successful Operations - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 - -``` - -``` - -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -near -> app: E2 SUBSCRIPTION DELETE QUERY (Required) -app -> near: E2 SUBSCRIPTION DELETE QUERY (Accept) -@enduml - -``` - -![Sequence diagram for successful E2 Subscription Delete Query procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: E2 SUBSCRIPTION DELETE QUERY (Required) from Near-RT RIC Platform to xApp. Message 2: E2 SUBSCRIPTION DELETE QUERY (Accept) from xApp to Near-RT RIC Platform.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC Platform - participant xApp - Near-RT RIC Platform->>xApp: E2 SUBSCRIPTION DELETE QUERY (Required) - xApp->>Near-RT RIC Platform: E2 SUBSCRIPTION DELETE QUERY (Accept) - -``` - -Sequence diagram for successful E2 Subscription Delete Query procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: E2 SUBSCRIPTION DELETE QUERY (Required) from Near-RT RIC Platform to xApp. Message 2: E2 SUBSCRIPTION DELETE QUERY (Accept) from xApp to Near-RT RIC Platform. - -**Figure 6.2.1.3.2-1: E2 Subscription Delete Query procedure, successful operation** - -The Near-RT RIC platform may consult each concerned xApp before deciding to delete an E2 subscription. The Near-RT RIC platform initiates the procedure by sending an E2 SUBSCRIPTION DELETE Query (Required) message to the xApp. The message contains the *Global E2 Node ID IE* and the *E2 Request ID IE* to identify the target E2 subscription. - -At reception of the E2 SUBSCRIPTION DELETE Query (Required) message, the xApp shall respond by an E2 SUBSCRIPTION DELETE Query (Accept) message, if the xApp agrees to delete the E2 subscription based on its own evaluation. The reply message shall contain the same *Global E2 Node ID IE*, *E2 Request ID IE*, and *RAN Function ID IE* as in the corresponding E2 SUBSCRIPTION DELETE (Required) message. The Near-RT RIC platform should consider the suggestions from all concerned xApps, but the decision for the E2 subscription is up to the Near-RT RIC platform. - -##### 6.2.1.3.3 Unsuccessful Operation - -If the xApp disagrees to delete the E2 subscription proposed in the E2 SUBSCRIPTION DELETE Query (Required) message, it shall reply an E2 SUBSCRIPTION DELETE Query (Decline) message to the Near-RT RIC platform. - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -near -> app: E2 SUBSCRIPTION DELETE QUERY (Required) -app -> near: E2 SUBSCRIPTION DELETE QUERY (Decline) -@enduml - -``` - -![Sequence diagram for unsuccessful E2 Subscription Delete Query procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: E2 SUBSCRIPTION DELETE QUERY (Required) from Near-RT RIC Platform to xApp. Message 2: E2 SUBSCRIPTION DELETE QUERY (Decline) from xApp to Near-RT RIC Platform.](84e5b251aa38db522f76f5cc3afcb853_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC Platform - participant xApp - Near-RT RIC Platform->>xApp: E2 SUBSCRIPTION DELETE QUERY (Required) - xApp->>Near-RT RIC Platform: E2 SUBSCRIPTION DELETE QUERY (Decline) - -``` - -Sequence diagram for unsuccessful E2 Subscription Delete Query procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: E2 SUBSCRIPTION DELETE QUERY (Required) from Near-RT RIC Platform to xApp. Message 2: E2 SUBSCRIPTION DELETE QUERY (Decline) from xApp to Near-RT RIC Platform. - -**Figure 6.2.1.3.3-2: E2 Subscription Delete Query procedure, unsuccessful operation** - -##### 6.2.1.3.4 Abnormal Conditions - -Not applicable. - -#### 6.2.1.4 E2 Subscription Delete Notification procedure - -##### 6.2.1.4.1 General - -This procedure is used by Near-RT RIC platform to notify the xApp that an existing E2 subscription has been deleted as required by the E2 Node. - -##### 6.2.1.4.2 Successful Operations - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -near -> app: E2 SUBSCRIPTION DELETE NOTIFICATION (Deleted) -@enduml - -``` - -![Sequence diagram showing the successful E2 Subscription Delete Notification procedure.](24c9e038a791677ed33100667b64f7e6_img.jpg) - -``` - -sequenceDiagram - participant near as Near-RT RIC Platform - participant app as xApp - near->>app: E2 SUBSCRIPTION DELETE NOTIFICATION (Deleted) - -``` - -Sequence diagram showing the successful E2 Subscription Delete Notification procedure. - -**Figure 6.2.1.4.2-1: E2 Subscription Delete Notification procedure, successful operation** - -After successfully deleting the E2 subscription required by the E2 Node (including removal of the RIC subscription over E2 interface and removal of corresponding subscription record in Near-RT RIC platform), the Near-RT RIC platform shall send an E2 SUBSCRIPTION DELETE NOTIFICATION (Deleted) message to the xApp to notify the deletion. - -The message shall contain the *Global E2 Node ID* IE and the *E2 Request ID* IE to identify the target E2 subscription, and the *Cause* IE with appropriate value. - -At reception of the message, the xApp shall remove its local subscription record of the E2 subscription. - -##### 6.2.1.4.3 Unsuccessful Operations - -Not applicable. - -##### 6.2.1.4.4 Abnormal Conditions - -Not applicable. - -#### 6.2.1.5 E2 Subscription Modification Procedure - -##### 6.2.1.5.1 General - -This procedure is used by an xApp to modify subscribe from an E2 subscription on Near-RT RIC platform. - -##### 6.2.1.5.2 Successful Operation - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: E2 SUBSCRIPTION MODIFICATION (Request) -@enduml - -``` - -``` -near -> app: E2 SUBSCRIPTION MODIFICATION (Success) -@enduml -``` - -![Sequence diagram for successful E2 Subscription Modification. Lifelines: xApp and Near-RT RIC Platform. The xApp sends an E2 SUBSCRIPTION MODIFICATION (Request) to the Near-RT RIC Platform, which responds with an E2 SUBSCRIPTION MODIFICATION (Success).](00504fc688ebcf131ccbeff94dfc9939_img.jpg) - -``` -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note over xApp: xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: E2 SUBSCRIPTION MODIFICATION (Request) - Near-RT RIC Platform-->>xApp: E2 SUBSCRIPTION MODIFICATION (Success) - Note over xApp: xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform -``` - -Sequence diagram for successful E2 Subscription Modification. Lifelines: xApp and Near-RT RIC Platform. The xApp sends an E2 SUBSCRIPTION MODIFICATION (Request) to the Near-RT RIC Platform, which responds with an E2 SUBSCRIPTION MODIFICATION (Success). - -**Figure 6.2.1.5.2-1: E2 Subscription Modification procedure, successful operation** - -The xApp initiates the procedure by sending an E2 SUBSCRIPTION MODIFICATION(Request) message to the Near-RT-RIC platform. The message contains the *Global E2 Node ID IE*, the *RAN Function ID IE*, and *E2 Request ID IE* to indicate the target E2 subscription and the *E2 Subscription Modification Details IE* including one or more requested E2 actions to be added, modified, and deleted. - -At reception of the E2 SUBSCRIPTION MODIFICATION (Request) message, the Near-RT-RIC platform shall: - -- Search existing E2 subscription(s) for matched *Global E2 Node ID IE*, *RAN Function ID IE* and matched contents in *E2 Subscription Details IE*. If a matched E2 subscription exists, the Near-RT-RIC platform shall initiate E2AP RIC subscription modification with the target E2 Node. - -If the modification request is successfully fulfilled, the Near-RT RIC platform shall send an E2 SUBSCRIPTION MODIFICATION(Success) message back to the xApp. - -In the E2 SUBSCRIPTION MODIFICATION(Success) message, Near-RT RIC platform shall include the associated *Procedure Transaction ID IE*, *Global E2 Node ID IE*, *RAN Function ID IE* and an *E2 Request ID IE* assigned by the Near-RT RIC platform. - -##### 6.2.1.5.3 Unsuccessful Operation - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: E2 SUBSCRIPTION MODIFICATION (Request) -near -> app: E2 SUBSCRIPTION MODIFICATION (Reject) -@enduml -``` - -![Sequence diagram for unsuccessful E2 Subscription Modification. Lifelines: xApp and Near-RT RIC Platform. The xApp sends an E2 SUBSCRIPTION MODIFICATION (Request) to the Near-RT RIC Platform, which responds with an E2 SUBSCRIPTION MODIFICATION (Reject).](dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg) - -``` -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note over xApp: xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: E2 SUBSCRIPTION MODIFICATION (Request) - Near-RT RIC Platform-->>xApp: E2 SUBSCRIPTION MODIFICATION (Reject) - Note over xApp: xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform -``` - -Sequence diagram for unsuccessful E2 Subscription Modification. Lifelines: xApp and Near-RT RIC Platform. The xApp sends an E2 SUBSCRIPTION MODIFICATION (Request) to the Near-RT RIC Platform, which responds with an E2 SUBSCRIPTION MODIFICATION (Reject). - -**Figure 6.2.1.5.3-1: E2 Subscription Modification procedure, unsuccessful operation (Reject)** - -If the Near-RT RIC platform rejects the request message, an E2 SUBSCRIPTION MODIFICATION(Reject) message shall be sent back to the initiating xApp. The message shall include associated *Procedure Transaction ID IE* which is replicated from the corresponding request, the *Global E2 Node ID IE*, the *RAN Function ID IE* and appropriate *Cause IE*. - -``` -@startuml -Skin rose -``` - -``` - -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: E2 SUBSCRIPTION MODIFICATION (Request) -near -> app: E2 SUBSCRIPTION MODIFICATION (Failure) -@enduml - -``` - -![Sequence diagram for E2 Subscription Modification procedure, unsuccessful operation (Failure). The diagram shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends an E2 SUBSCRIPTION MODIFICATION (Request) message to the Near-RT RIC Platform. The Near-RT RIC Platform responds with an E2 SUBSCRIPTION MODIFICATION (Failure) message back to the xApp.](e05b36c0d46549e681ce6581422c66b2_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: E2 SUBSCRIPTION MODIFICATION (Request) - Near-RT RIC Platform-->>xApp: E2 SUBSCRIPTION MODIFICATION (Failure) - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for E2 Subscription Modification procedure, unsuccessful operation (Failure). The diagram shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends an E2 SUBSCRIPTION MODIFICATION (Request) message to the Near-RT RIC Platform. The Near-RT RIC Platform responds with an E2 SUBSCRIPTION MODIFICATION (Failure) message back to the xApp. - -**Figure 6.2.1.5.3-2: E2 Subscription Modification procedure, unsuccessful operation (Failure)** - -If the associated E2AP procedure(s) fails for the E2 subscription modification, the Near-RT RIC platform shall send an E2 SUBSCRIPTION MODIFICATION (Failure) message back to the initiating xApp. The message shall include associated *Procedure Transaction ID IE* which is replicated from the corresponding request, the *Global E2 Node ID IE*, the *RAN Function ID IE* and appropriate *Cause IE*. - -##### 6.2.1.5.4 Abnormal Conditions - -Not applicable. - -### 6.2.2 E2\_Indication\_API procedures - -#### 6.2.2.1 E2 Indication Procedure - -##### 6.2.2.1.1 General - -This procedure is used by the Near-RT RIC platform to deliver to xApp the subscribed information associated with an E2 subscription. The procedure is triggered by the successful operation of an E2AP RIC indication procedure. - -##### 6.2.2.1.2 Successful Operation - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -near -> app: E2 INDICATION (Push) -@enduml - -``` - -![Sequence diagram for E2 Indication procedure, successful operation. The diagram shows two lifelines: xApp and Near-RT RIC Platform. The Near-RT RIC Platform sends an E2 INDICATION (Push) message to the xApp.](e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - Near-RT RIC Platform-->>xApp: E2 INDICATION (Push) - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for E2 Indication procedure, successful operation. The diagram shows two lifelines: xApp and Near-RT RIC Platform. The Near-RT RIC Platform sends an E2 INDICATION (Push) message to the xApp. - -**Figure 6.2.2.1.2-1: E2 Indication procedure, successful operation** - -The Near-RT-RIC platform initiates the procedure by sending the E2 INDICATION (Push) message containing the *Global E2 Node ID IE*, the *E2 Request ID IE*, the *E2 Action ID IE* to the xApp. The message shall also contain the *E2 Indication Type IE*, the *E2 Indication Header IE* and the *E2 Indication Message IE* to carry the information from corresponding fields, i.e. the *RIC Indication Type IE*, the *RIC Indication Header IE*, and the *RIC Indication Message IE*, respectively, in the E2AP RIC INDICATION message. The *E2 Indication SN IE* and the *E2 Call Process ID IE* shall also be included, if corresponding fields, i.e. the *RIC Indication SN IE*, and the *RIC Call Process ID IE*, respectively, are present in the E2AP RIC INDICATION message. - -At reception of the E2 INDICATION (Push) message an xApp shall: - -- Use the *Global E2 Node ID IE*, the *E2 Request ID IE* and the *E2 Action ID IE* to associate the received message to the right E2 subscription. The *E2 Request ID IE* and the *E2 Action ID IE* have been assigned in the E2 SUBSCRIPTION (Success) message for each E2 subscription. -- Process the information carried in the *E2 Indication SN IE*, the *E2 Indication Type IE*, the *E2 Indication Header IE*, the *E2 Indication Message IE* and the *E2 Call Process ID IE*. - -##### 6.2.2.1.3 Unsuccessful Operation - -``` -@sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: Skin rose - skinparam ParticipantPadding 50 - skinparam BoxPadding 10 - skinparam lifelineStrategy solid - participant "xApp" as app - participant "Near-RT RIC Platform" as near - near->>app: E2 INDICATION (Push) - app-->>near: E2 INDICATION (Failure) -@endsequence -``` - -![Sequence diagram showing an unsuccessful E2 Indication procedure. The Near-RT RIC Platform sends an E2 INDICATION (Push) message to the xApp. The xApp responds with an E2 INDICATION (Failure) message back to the Near-RT RIC Platform.](b904ac2472cab80892d1e783e6230d6e_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: Skin rose - skinparam ParticipantPadding 50 - skinparam BoxPadding 10 - skinparam lifelineStrategy solid - participant "xApp" as app - participant "Near-RT RIC Platform" as near - near->>app: E2 INDICATION (Push) - app-->>near: E2 INDICATION (Failure) - -``` - -Sequence diagram showing an unsuccessful E2 Indication procedure. The Near-RT RIC Platform sends an E2 INDICATION (Push) message to the xApp. The xApp responds with an E2 INDICATION (Failure) message back to the Near-RT RIC Platform. - -Figure 6.2.2.1.3-1: E2 Indication procedure, unsuccessful operation (Failure) - -If the received E2 INDICATION (Push) message cannot be handled successfully as specified in 6.2.2.1.2, the xApp may, according to operator's OM configuration, send E2 INDICATION (Failure) message back to the Near-RT RIC platform. The message shall include the associated *Global E2 Node ID IE*, *E2 Request ID IE*, *RAN Function ID IE*, *E2 Action ID IE*, and appropriate *Cause IE*. The *E2 Indication SN IE* shall also be included if the same name IE is present in the corresponding E2 INDICATION (Push) message. - -##### 6.2.2.1.4 Abnormal Conditions - -Not applicable. - -### 6.2.3 E2\_Control\_API procedures - -#### 6.2.3.1 E2 Control procedure - -##### 6.2.3.1.1 General - -This procedure is used by an xApp to request for E2 control service to Near-RT RIC platform. - -##### 6.2.3.1.2 Successful Operation - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: E2 CONTROL (Request) -near --> app: E2 CONTROL (Success) -@enduml -``` - -![Sequence diagram for E2 Control procedure, successful operation. The diagram shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends an E2 CONTROL (Request) message to the Near-RT RIC Platform. The Near-RT RIC Platform responds with an E2 CONTROL (Success) message. The lifelines are represented by yellow boxes with red borders.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) - -``` -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: E2 CONTROL (Request) - Near-RT RIC Platform-->>xApp: E2 CONTROL (Success) -``` - -Sequence diagram for E2 Control procedure, successful operation. The diagram shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends an E2 CONTROL (Request) message to the Near-RT RIC Platform. The Near-RT RIC Platform responds with an E2 CONTROL (Success) message. The lifelines are represented by yellow boxes with red borders. - -**Figure 6.2.3.1.2-1: E2 Control procedure, successful operation** - -The xApp initiates the procedure by sending the E2 CONTROL (Request) message to the Near-RT-RIC platform, containing the *Global E2 Node ID IE*, the *RAN Function ID IE*, optionally the *E2 Call Process ID IE*, *E2 Control Header IE*, *E2 Control Message IE*, optionally the *E2 Control Ack Request IE* and optionally the *E2 Control Timer IE*. - -At reception of the E2 CONTROL (Request) message, the Near-RT-RIC platform shall: - -- Evaluate whether to reject the request due to potential control conflict, when such evaluation is required by conflict mitigation related configuration. -- Initiate appropriate E2AP RIC Control procedure with the target E2 Node, if the request is not rejected by the Near-RT-RIC platform. - -The Near-RT-RIC platform may use the value in the *E2 Control Timer IE*, if present, as a one-time value of the E2AP timer $T_{RICcontrol}$ in Clause 9.5 of [3], which is valid only for this transaction. - -If the control request is successfully performed, and if the optional *E2 Control Ack Request IE* in the request is absent or set to “Ack”, an E2 CONTROL (Success) message shall be responded to the initiating xApp. The E2 CONTROL (Success) message shall include the *Global E2 Node ID IE*, the *RAN Function ID IE*, optionally the *E2 Call Process ID IE*, and optionally the *E2 Control Outcome IE*. The xApp may use the information contained in the optional *E2 Control Outcome IE* to determine subsequent actions. - -If the control request is successfully performed, and if the optional *E2 Control Ack Request IE* in the request is set to “NoAck”, an E2 CONTROL (Success) message is not needed and xApp may consider it success. - -##### 6.2.3.1.3 Unsuccessful Operations - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: E2 CONTROL (Request) -near --> app: E2 CONTROL (Reject) -@enduml -``` - -![Sequence diagram for E2 Control procedure, unsuccessful operation (Reject). It shows an xApp sending an E2 CONTROL (Request) to a Near-RT RIC Platform, which responds with an E2 CONTROL (Reject).](dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - xApp->>Near-RT RIC Platform: E2 CONTROL (Request) - Near-RT RIC Platform-->>xApp: E2 CONTROL (Reject) - -``` - -Sequence diagram for E2 Control procedure, unsuccessful operation (Reject). It shows an xApp sending an E2 CONTROL (Request) to a Near-RT RIC Platform, which responds with an E2 CONTROL (Reject). - -**Figure 6.2.3.1.3-1: E2 Control procedure, unsuccessful operation (Reject)** - -If the request is rejected by the Near-RT RIC platform, an E2 CONTROL (Reject) message shall be responded to the initiating xApp with appropriate *Cause* IE. The xApp may use the information contained in the *Cause* IE to determine subsequent actions. - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: E2 CONTROL (Request) -near --> app: E2 CONTROL (Failure) -@enduml - -``` - -![Sequence diagram for E2 Control procedure, unsuccessful operation (Failure). It shows an xApp sending an E2 CONTROL (Request) to a Near-RT RIC Platform, which responds with an E2 CONTROL (Failure).](a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - xApp->>Near-RT RIC Platform: E2 CONTROL (Request) - Near-RT RIC Platform-->>xApp: E2 CONTROL (Failure) - -``` - -Sequence diagram for E2 Control procedure, unsuccessful operation (Failure). It shows an xApp sending an E2 CONTROL (Request) to a Near-RT RIC Platform, which responds with an E2 CONTROL (Failure). - -**Figure 6.2.3.1.3-2: E2 Control procedure, unsuccessful operation (Failure)** - -If the request is accepted by the Near-RT RIC platform but failed in the E2AP RIC Control procedure, the Near-RT RIC platform shall send an E2 CONTROL (Failure) message back to the xApp with appropriate *Cause* IE. The xApp may use the information contained in the *Cause* IE and the optional *E2 Control Outcome* IE to determine subsequent actions. - -##### 6.2.3.1.4 Abnormal Conditions - -Not applicable. - -### 6.2.4 E2\_Query\_API procedures - -#### 6.2.4.1 E2 Query Procedure - -##### 6.2.4.1.1 General - -This procedure is used by an xApp to request RAN and/or UE related information on Near-RT RIC Platform. - -##### 6.2.4.1.2 Successful Operation - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 - -``` - -``` - -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: E2 QUERY (Request) -near -> app: E2 QUERY (Success) -@enduml - -``` - -![Sequence diagram for successful E2 Query procedure. Lifelines: xApp and Near-RT RIC Platform. The xApp sends an E2 QUERY (Request) message to the Near-RT RIC Platform, which responds with an E2 QUERY (Success) message.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: E2 QUERY (Request) - Near-RT RIC Platform-->>xApp: E2 QUERY (Success) - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for successful E2 Query procedure. Lifelines: xApp and Near-RT RIC Platform. The xApp sends an E2 QUERY (Request) message to the Near-RT RIC Platform, which responds with an E2 QUERY (Success) message. - -**Figure 6.2.4.1.2-1: E2 Query procedure, successful operation** - -The xApp initiates the procedure by sending an E2 QUERY(Request) message to the Near-RT-RIC platform. The message contains the *Global E2 Node ID IE*, and the *RAN Function ID IE* to indicate the target E2 query and the *E2 Query Header IE* and *E2 Query Message IE*. - -At reception of the E2 QUERY (Request) message, the Near-RT-RIC platform shall: - -- Determine the target RAN Function using the information in the *RAN Function ID IE*. -- Validate the *RIC Query Header IE* and *RIC Query Definition IE*. -- Initiate appropriate E2AP procedure(s) to query information to the target E2 Nodes, if the requested E2 nodes information available at Near-RT-RIC platform are insufficient to fulfil the request. - -If the query request is successfully fulfilled, the Near-RT RIC platform shall send an E2 QUERY (Success) message back to the xApp. In the E2 QUERY(Success) message, Near-RT RIC platform shall include the associated *Procedure Transaction ID IE*, *Global E2 Node ID IE*, *RAN Function ID IE*. - -##### 6.2.4.1.3 Unsuccessful Operation - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: E2 QUERY (Request) -near -> app: E2 QUERY (Reject) -@enduml - -``` - -![Sequence diagram for unsuccessful E2 Query procedure. Lifelines: xApp and Near-RT RIC Platform. The xApp sends an E2 QUERY (Request) message to the Near-RT RIC Platform, which responds with an E2 QUERY (Reject) message.](f1cbfa3fc27f58581615654fec4335d8_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: E2 QUERY (Request) - Near-RT RIC Platform-->>xApp: E2 QUERY (Reject) - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for unsuccessful E2 Query procedure. Lifelines: xApp and Near-RT RIC Platform. The xApp sends an E2 QUERY (Request) message to the Near-RT RIC Platform, which responds with an E2 QUERY (Reject) message. - -**Figure 6.2.4.1.3-1: E2 Query procedure, unsuccessful operation (Reject)** - -If the Near-RT RIC platform rejects the request message, an E2 QUERY(Reject) message shall be sent back to the initiating xApp. The message shall include associated *Procedure Transaction ID IE* which is replicated from the corresponding request, the *Global E2 Node ID IE*, the *RAN Function ID IE* and appropriate *Cause IE*. - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: E2 QUERY (Request) -near -> app: E2 QUERY (Failure) -@enduml - -``` - -![UML sequence diagram showing an unsuccessful E2 Query procedure. The xApp sends an E2 QUERY (Request) to the Near-RT RIC Platform, which responds with an E2 QUERY (Failure).](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: E2 QUERY (Request) - Near-RT RIC Platform-->>xApp: E2 QUERY (Failure) - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -UML sequence diagram showing an unsuccessful E2 Query procedure. The xApp sends an E2 QUERY (Request) to the Near-RT RIC Platform, which responds with an E2 QUERY (Failure). - -**Figure 6.2.4.1.3-2: E2 Query procedure, unsuccessful operation (Failure)** - -If the associated E2AP procedure(s) fails for the E2 QUERY, the Near-RT RIC platform shall send an E2 QUERY (Failure) message back to the initiating xApp. The message shall include associated *Procedure Transaction ID* IE which is replicated from the corresponding request, the *Global E2 Node ID* IE, the *RAN Function ID* IE and appropriate *Cause* IE. - -##### **6.2.4.1.4 Abnormal Conditions** - -Not applicable. - -## 6.3 Elements for E2-related API Communication - -### 6.3.1 General - -### 6.3.2 Message Functional Definition and Content - -#### 6.3.2.1 E2 SUBSCRIPTION (Request) - -This message is sent by an xApp to the Near-RT RIC platform for an E2 Subscription. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------------|----------|-------|---------------------------------------------------|----------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value assigned by the initiating xApp. | -| Global E2 Node ID | M | | 10.1.6 | | -| RAN Function ID | M | | 10.1.7 | | -| E2 Subscription Details | | | | | -| >E2 Event Trigger Definition | M | | RIC Event Trigger Definition, Clause 9.2.9 of [3] | | - -| | | | | | -|-------------------------------------------------|---|---------------------------|-----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| >Sequence of Actions | | 1..
| | | -| >>Requested E2 Action ID | M | | RIC Action ID, Clause 9.2.10 of [3] | Assigned by initiating xApp to uniquely identify an action within the sequence of actions. It should not be assumed that the E2 Action ID in the subsequent E2 SUBSCRIPTION (Success) message or RIC Action ID in the corresponding E2AP message has the same value. | -| >>E2 Action Type | M | | RIC Action Type, Clause 9.2.11 of [3] | | -| >>E2 Action Definition | O | | RIC Action Definition, Clause 9.2.12 of [3] | | -| >>E2 Subsequent Action | O | | RIC Subscription Action, Clause 9.2.13 of [3] | | -| E2 Subscription Timer | O | | 6.3.3.7 | | -| E2 Indication Destination | O | | 10.1.9 | When present, this IE specifies the destination address for the Near-RT RIC platform to send E2 INDICATION (Push) messages. | -| E2 Subscription Delete Notification Destination | O | | 10.1.9 | When present, this IE specifies the destination address for the Near-RT RIC platform to send E2 SUBSCRIPTION DELETE QUERY (Required) and E2 SUBSCRIPTION DELETE NOTIFICATION (Deleted) messages. | - -| Range bound | Explanation | -|------------------|--------------------------------------------------------------------------| -| maxnoofE2Actions | Maximum no. of E2 Actions requested in the E2 subscription. Value is 16. | - -#### 6.3.2.2 E2 SUBSCRIPTION (Success) - -This message is sent by the Near-RT RIC platform after the xApp's subscription request is successfully accepted with respect to the target E2 Node. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|---------------------------|-------------------------------------|-------------------------------------------------------------------------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | -| Global E2 Node ID | M | | 10.1.6 | Value replicated from corresponding request. | -| E2 Request ID | M | | 6.3.3.2 | Value assigned by the Near-RT RIC platform to indicate the associated E2 subscription in Near-RT RIC. | -| RAN Function ID | M | | 10.1.7 | Value replicated from corresponding request. | -| Actions Admitted List | | 1..
| | | -| >Requested E2 Action ID | M | | RIC Action ID, Clause 9.2.10 of [3] | Value replicated from corresponding request message | - -| | | | | | -|---------------------------|---|---------------------------|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| >E2 Action ID | M | | RIC Action ID, Clause 9.2.10 of [3] | Value assigned by Near-RT RIC platform to indicate in the associated E2 subscription the action ID that corresponds to the Requested E2 Action ID IE in the E2 SUBSCRIPTION REQUEST message. | -| Actions Not Admitted List | | 0..
| | | -| >Requested E2 Action ID | M | | RIC Action ID, Clause 9.2.10 of [3] | Value replicated from corresponding request message | -| >Cause | M | | 6.3.3.4 | | - -| Range bound | Explanation | -|------------------|--------------------------------------------------------------------------| -| maxnoofE2Actions | Maximum no. of E2 Actions requested in the E2 subscription. Value is 16. | - -#### 6.3.2.3 E2 SUBSCRIPTION (Reject) - -This message is sent by the Near-RT RIC platform after the xApp's subscription request is rejected by Near-RT RIC platform with respect to the target E2 Node. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|----------------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | -| Global E2 Node ID | M | | 10.1.6 | Value replicated from corresponding request. | -| RAN Function ID | M | | 10.1.7 | Value replicated from corresponding request. | -| Cause | M | | 6.3.3.4 | | -| Criticality Diagnostics | O | | 6.3.3.5 | | - -#### 6.3.2.4 E2 SUBSCRIPTION (Failure) - -This message is sent by the Near-RT RIC platform after the xApp's subscription request is accepted by Near-RT RIC platform but failed by E2 Node, with respect to the target E2 Node. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|----------------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | -| Global E2 Node ID | M | | 10.1.6 | Value replicated from corresponding request. | -| RAN Function ID | M | | 10.1.7 | Value replicated from corresponding request. | -| Cause | M | | 6.3.3.4 | | -| Criticality Diagnostics | O | | 6.3.3.5 | | - -#### 6.3.2.5 E2 SUBSCRIPTION DELETE (Request) - -This message is sent by the xApp to the Near-RT RIC platform to request deletion of one target E2 subscription. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Global E2 Node ID | M | | 10.1.6 | | -| E2 Request ID | M | | 6.3.3.2 | | -| RAN Function ID | M | | 10.1.7 | | -| E2 Subscription Delete Timer | O | | 6.3.3.8 | | - -#### 6.3.2.6 E2 SUBSCRIPTION DELETE (Success) - -This message is sent by the Near-RT RIC platform to the xApp to indicate success for the delete request of the target E2 subscription. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|----------------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | -| Global E2 Node ID | M | | 10.1.6 | Value replicated from corresponding request. | -| E2 Request ID | M | | 6.3.3.2 | Value replicated from corresponding request. | -| RAN Function ID | M | | 10.1.7 | Value replicated from corresponding request. | - -#### 6.3.2.7 E2 SUBSCRIPTION DELETE (Reject) - -This message is sent by the Near-RT RIC platform to the xApp when the Near-RT RIC platform rejects the delete request for the target E2 subscription. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|----------------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | -| Global E2 Node ID | M | | 10.1.6 | Value replicated from corresponding request. | -| E2 Request ID | M | | 6.3.3.2 | Value replicated from corresponding request. | -| RAN Function ID | M | | 10.1.7 | Value replicated from corresponding request. | -| Cause | M | | 6.3.3.4 | | -| Criticality Diagnostics | O | | 6.3.3.5 | | - -#### 6.3.2.8 E2 SUBSCRIPTION DELETE (Failure) - -This message is sent by the Near-RT RIC platform to the xApp when the delete request for a target E2 subscription fails due to failure in the associated E2AP procedure(s). - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|----------------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | -| Global E2 Node ID | M | | 10.1.6 | Value replicated from corresponding request. | - -| | | | | | -|-------------------------|---|--|---------|----------------------------------------------| -| E2 Request ID | M | | 6.3.3.2 | Value replicated from corresponding request. | -| RAN Function ID | M | | 10.1.7 | Value replicated from corresponding request. | -| Cause | M | | 6.3.3.4 | | -| Criticality Diagnostics | O | | 6.3.3.5 | | - -#### 6.3.2.9 E2 SUBSCRIPTION DELETE QUERY (Required) - -This message is sent by the Near-RT RIC platform to the xApp to consult the deletion of a target E2 subscription. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Global E2 Node ID | M | | 10.1.6 | | -| E2 Request ID | M | | 6.3.3.2 | | -| RAN Function ID | M | | 10.1.7 | | -| Cause | M | | 6.3.3.4 | | - -#### 6.3.2.10 E2 SUBSCRIPTION DELETE QUERY (Accept) - -This message is sent by the xApp to the Near-RT RIC platform to agree to deletion of a target E2 subscription. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Global E2 Node ID | M | | 10.1.6 | | -| E2 Request ID | M | | 6.3.3.2 | | -| RAN Function ID | M | | 10.1.7 | | - -#### 6.3.2.11 E2 SUBSCRIPTION DELETE QUERY (Decline) - -This message is sent by the xApp to the Near-RT RIC platform to decline deletion of a target E2 subscription. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Global E2 Node ID | M | | 10.1.6 | | -| E2 Request ID | M | | 6.3.3.2 | | -| RAN Function ID | M | | 10.1.7 | | -| Cause | M | | 6.3.3.4 | | - -#### 6.3.2.12 E2 SUBSCRIPTION DELETE NOTIFICATION (Deleted) - -This message is sent by the Near-RT RIC platform to the xApp to notify the deletion of a target E2 subscription. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Global E2 Node ID | M | | 10.1.6 | | -| RAN Function ID | M | | 10.1.7 | | -| E2 Request ID | M | | 6.3.3.2 | | -| Cause | M | | 6.3.3.4 | | - -#### 6.3.2.12A E2 SUBSCRIPTION MODIFICATION(Request) - -This message is sent by an xApp to the Near-RT RIC platform for an E2 Subscription Modification. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------------------------------|----------|---------------------------|---------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value assigned by the initiating xApp. | -| Global E2 Node ID | M | | 10.1.6 | | -| E2 Request ID | M | | 6.3.3.2 | | -| RAN Function ID | M | | 10.1.7 | | -| E2 Subscription Modification Details | | | | | -| >E2 Event Trigger Definition_to_be_Modified | M | | RIC Event Trigger Definition, Clause 9.2.9 of [3] | | -| >E2_Actions_to_be_Added_List | | 0..
| | | -| >>Requested E2 Action ID | M | | RIC Action ID, Clause 9.2.10 of [3] | Assigned by initiating xApp to uniquely identify an action within the sequence of actions. It should not be assumed that the E2 Action ID in the subsequent E2 SUBSCRIPTION (Success) message or RIC Action ID in the corresponding E2AP message has the same value. | -| >>E2 Action Type | M | | RIC Action Type, Clause 9.2.11 of [3] | | -| >>E2 Action Definition | O | | RIC Action Definition, Clause 9.2.12 of [3] | | -| >>E2 Action Execution Order | O | | RIC Action Execution Order 9.2.35 of [3] | | -| >>E2 Subsequent Action | O | | RIC Subscription Action, Clause 9.2.13 of [3] | | -| >E2_Actions_to_be_Modified_List | | 0..
| | | - -| | | | | | -|------------------------------------|---|-----------------------------------|-----------------------------------------------|-------------------------------------------------------| -| >>E2 Action ID | M | | RIC Action ID, Clause 9.2.10 of [3] | The E2 Action ID assigned by the Near-RT RIC platform | -| >>E2 Action Type | M | | RIC Action Type, Clause 9.2.11 of [3] | | -| >>E2 Action Definition | O | | RIC Action Definition, Clause 9.2.12 of [3] | | -| >>E2 Action Execution Order | O | | RIC Action Execution Order 9.2.35 of [3] | | -| >>E2 Subsequent Action | O | | RIC Subscription Action, Clause 9.2.13 of [3] | | -| >E2_Actions_to_be_Re
moved_List | | 0..
fE2Action
s> | | | -| >>E2 Action ID | M | | RIC Action ID, Clause 9.2.10 of [3] | The E2 Action ID assigned by the Near-RT RIC platform | - -#### 6.3.2.12B E2 SUBSCRIPTION MODIFICATION (Success) - -This message is sent by the Near-RT RIC platform after the xApp's subscription modification request is successfully accepted with respect to the target E2 Node. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------------------|----------|-----------------------------------|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | -| Global E2 Node ID | M | | 10.1.6 | Value replicated from corresponding request. | -| E2 Request ID | M | | 6.3.3.2 | Value assigned by the Near-RT RIC platform to indicate the associated E2 subscription in Near-RT RIC. | -| RAN Function ID | M | | 10.1.7 | Value replicated from corresponding request. | -| E2_Actions
Added_Admitted List | | 0..
fE2Action
s> | | | -| >Requested E2 Action ID | M | | RIC Action ID, Clause 9.2.10 of [3] | Value replicated from corresponding request message | -| >E2 Action ID | M | | RIC Action ID, Clause 9.2.10 of [3] | Value assigned by Near-RT RIC platform to indicate in the associated E2 subscription the action ID that corresponds to the Requested E2 Action ID IE in the E2 SUBSCRIPTION MODIFICATION REQUEST message. | -| E2_Actions Added_Not Admitted List | | 0..
fE2Action
s> | | | -| >Requested E2 Action ID | M | | RIC Action ID, Clause 9.2.10 of [3] | Value replicated from corresponding request message | -| >Cause | M | | 6.3.3.4 | | - -| | | | | | -|---------------------------------------------|---|-----------------------------------|-------------------------------------------|-----------------------------------------------------| -| E2_Actions
Modified_Admitted List | | 0..
fE2Action
s> | | | -| >E2 Action ID | M | | RIC Action
ID, Clause
9.2.10 of [3] | Value replicated from corresponding request message | -| E2_Actions
Modified_Not Admitted
List | | 0..
fE2Action
s> | | | -| >E2 Action ID | M | | RIC Action
ID, Clause
9.2.10 of [3] | Value replicated from corresponding request message | -| >Cause | M | | 6.3.3.4 | | -| E2_Actions
Removed_Admitted List | | 0..
ofE2Acti
ons> | | | -| >E2 Action ID | M | | RIC Action
ID, Clause
9.2.10 of [3] | Value replicated from corresponding request message | -| E2_Actions
Removed_Not Admitted
List | | 0..
ofE2Acti
ons> | | | -| >E2 Action ID | M | | RIC Action
ID, Clause
9.2.10 of [3] | Value replicated from corresponding request message | -| >Cause | M | | 6.3.3.4 | | - -#### 6.3.2.12C E2 SUBSCRIPTION MODIFICATION (Reject) - -This message is sent by the Near-RT RIC platform after the xApp's subscription modification request is rejected by Near-RT RIC platform with respect to the target E2 Node. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|----------------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | -| Global E2 Node ID | M | | 10.1.6 | Value replicated from corresponding request. | -| RAN Function ID | M | | 10.1.7 | Value replicated from corresponding request. | -| Cause | M | | 6.3.3.4 | | -| Criticality Diagnostics | O | | 6.3.3.5 | | - -#### 6.3.2.12D E2 SUBSCRIPTION MODIFICATION (Failure) - -This message is sent by the Near-RT RIC platform after the xApp's subscription modification request is accepted by Near-RT RIC platform but failed by E2 Node, with respect to the target E2 Node. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|----------------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | -| Global E2 Node ID | M | | 10.1.6 | Value replicated from corresponding request. | -| RAN Function ID | M | | 10.1.7 | Value replicated from corresponding request. | -| Cause | M | | 6.3.3.4 | | - -| | | | | | -|-------------------------|---|--|---------|--| -| Criticality Diagnostics | O | | 6.3.3.5 | | -|-------------------------|---|--|---------|--| - -#### 6.3.2.13 E2 INDICATION (Push) - -This message is sent by the Near-RT RIC platform to the xApp for delivery of subscribed information associated with an E2 subscription. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-----------------------|----------|-------|-----------------------------------------------|-----------------------| -| Message Type | M | | 6.3.3.1 | | -| Global E2 Node ID | M | | 10.1.6 | | -| E2 Request ID | M | | 6.3.3.2 | | -| RAN Function ID | M | | 10.1.7 | | -| E2 Action ID | M | | RIC Action ID, Clause 9.2.10 of [3]. | | -| E2 Indication SN | O | | RIC Indication SN, Clause 9.2.14 of [3]. | | -| E2 Indication Type | M | | RIC Indication Type, Clause 9.2.15 of [3]. | | -| E2 Indication Header | M | | RIC Indication Header, Clause 9.2.17 of [3]. | | -| E2 Indication Message | M | | RIC Indication Message, Clause 9.2.16 of [3]. | | -| E2 Call Process ID | O | | RIC Call Process ID, Clause 9.2.18 of [3]. | | - -#### 6.3.2.14 E2 INDICATION (Failure) - -This message is sent by the xApp to the Near-RT RIC platform if an error is detected in E2 INDICATION (Push) message. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------|----------|-------|--------------------------------------|-----------------------| -| Message Type | M | | 6.3.3.1 | | -| Global E2 Node ID | M | | 10.1.6 | | -| E2 Request ID | M | | 6.3.3.2 | | -| RAN Function ID | M | | 10.1.7 | | -| E2 Action ID | M | | RIC Action ID, Clause 9.2.10 of [3]. | | -| E2 Indication SN | O | | RIC Indication | | - -| | | | | | -|-------------------------|---|--|---------------------------|--| -| | | | SN, Clause 9.2.14 of [3]. | | -| Cause | M | | 6.3.3.4 | | -| Criticality Diagnostics | O | | 6.3.3.5 | | - -#### 6.3.2.15 E2 CONTROL (Request) - -This message is sent by the xApp to the Near-RT RIC platform for an E2 control request. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|------------------------------------------------|----------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value assigned by the initiating xApp. | -| Global E2 Node ID | M | | 10.1.6 | | -| RAN Function ID | M | | 10.1.7 | | -| E2 Call Process ID | O | | RIC Call Process ID, Clause 9.2.18 of [3]. | | -| E2 Control Header | M | | RIC Control Header, Clause 9.2.20 of [3]. | | -| E2 Control Message | M | | RIC Control Message, Clause 9.2.19 of [3]. | | -| E2 Control Ack Request | O | | RIC Control Ack Request, Clause 9.2.21 of [3]. | | -| E2 Control Timer | O | | 6.3.3.6 | | - -#### 6.3.2.16 E2 CONTROL (Success) - -This message is sent by the Near-RT RIC platform to the xApp for a successfully performed E2 control request. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|--------------------------------------------|----------------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | -| Global E2 Node ID | M | | 10.1.6 | | -| RAN Function ID | M | | 10.1.7 | | -| E2 Call Process ID | O | | RIC Call Process ID, Clause 9.2.18 of [3]. | | -| E2 Control Outcome | O | | RIC Control Outcome, Clause 9.2.25 of [3]. | | - -#### 6.3.2.17 E2 CONTROL (Reject) - -This message is sent by the Near-RT RIC platform to the xApp if the corresponding E2 control request is rejected by the Near-RT RIC platform. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|----------------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | -| Global E2 Node ID | M | | 10.1.6 | | -| RAN Function ID | M | | 10.1.7 | | -| Cause | M | | 6.3.3.4 | | -| Criticality Diagnostics | O | | 6.3.3.5 | | - -#### 6.3.2.18 E2 CONTROL (Failure) - -This message is sent by the Near-RT RIC platform to the xApp if the corresponding E2 control request is accepted by the Near-RT RIC platform but fails in the E2 Node. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|--------------------------------------------|----------------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | -| Global E2 Node ID | M | | 10.1.6 | | -| RAN Function ID | M | | 10.1.7 | | -| E2 Call Process ID | O | | RIC Call Process ID, Clause 9.2.18 of [3]. | | -| E2 Control Outcome | O | | RIC Control Outcome, Clause 9.2.25 of [3]. | | -| Cause | M | | 6.3.3.4 | | -| Criticality Diagnostics | O | | 6.3.3.5 | | - -#### 6.3.2.19 E2 GUIDANCE (Request) - -#### 6.3.2.20 E2 GUIDANCE (Response) - -#### 6.3.2.21 E2 GUIDANCE (Modification) - -#### 6.3.2.22 E2 QUERY (Request) - -This message is sent by an xApp to the Near-RT RIC platform for an E2 Query. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 6.3.3.1 | | - -| | | | | | -|--------------------------|---|--|---------------------------------------------|----------------------------------------| -| Procedure Transaction ID | M | | 10.1.1 | Value assigned by the initiating xApp. | -| Global E2 Node ID | M | | 10.1.6 | | -| RAN Function ID | M | | 10.1.7 | | -| E2 Query Header | M | | RIC Query Header, Clause 9.2.36 of [3]. | | -| E2 Query Definition | M | | RIC Query Definition, Clause 9.2.37 of [3]. | | - -#### 6.3.2.23 E2 QUERY (Success) - -This message is sent by the Near-RT RIC platform after the xApp's query request is successfully accepted with respect to the target E2 Node. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|------------------------------------------|----------------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | -| Global E2 Node ID | M | | 10.1.6 | Value replicated from corresponding request. | -| RAN Function ID | M | | 10.1.7 | Value replicated from corresponding request. | -| E2_Query_Outcome | M | | RIC Query Outcome, Clause 9.2.38 of [3]. | | - -#### 6.3.2.24 E2 QUERY (Reject) - -This message is sent by the Near-RT RIC platform after the xApp's query request is rejected by Near-RT RIC platform with respect to the target E2 Node. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|----------------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | -| Global E2 Node ID | M | | 10.1.6 | Value replicated from corresponding request. | -| RAN Function ID | M | | 10.1.7 | Value replicated from corresponding request. | -| Cause | M | | 6.3.3.4 | | -| Criticality Diagnostics | O | | 6.3.3.5 | | - -#### 6.3.2.25 E2 QUERY (Failure) - -This message is sent by the Near-RT RIC platform after the xApp's query request is accepted by Near-RT RIC platform but failed by E2 Node, with respect to the target E2 Node. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|----------------------------------------------| -| Message Type | M | | 6.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | - -| | | | | | -|-------------------------|---|--|---------|----------------------------------------------| -| Global E2 Node ID | M | | 10.1.6 | Value replicated from corresponding request. | -| RAN Function ID | M | | 10.1.7 | Value replicated from corresponding request. | -| Cause | M | | 6.3.3.4 | | -| Criticality Diagnostics | O | | 6.3.3.5 | | - -### 6.3.3 Information Element Definitions - -#### 6.3.3.1 Message Type - -This IE uniquely identifies the message being sent. It is mandatory for all messages. - -| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | -|------------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------| -| Message Type | | | | | -| >Procedure Type | M | | CHOICE (E2 Subscription, E2 Subscription Delete, E2 Subscription Delete Query, E2 Subscription Delete Notification, E2 Subscription Modification, E2 Indication, E2 Control, E2 Query, ...) | | -| >Type of Message | M | | CHOICE (Request, Success, Reject, Failure, ...) | Refer to Table 6.1.2-3 for applicable choices for each procedure type | - -#### 6.3.3.2 E2 Request ID - -This IE is assigned by Near-RT RIC platform to uniquely identify an E2 subscription among all the E2 subscriptions associated with the same E2 Node. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|----------------------------|-----------------------| -| E2 Request ID | M | | INTEGER (0 ... 4294967295) | | - -#### 6.3.3.3 Void - -#### 6.3.3.4 Cause - -This IE is used to indicate the reason for a particular event for the E2-related APIs. - -NOTE: Not all causes from E2AP are applicable. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------|----------|-------|-----------------------------|-----------------------| -| CHOICE Cause Group | M | | | | -| >E2-related API Cause | | | | | -| >>E2-related API Cause | M | | 6.3.3.4a. | | -| >E2AP Cause | | | | | -| >>E2AP Cause | M | | Cause, Clause 9.2.1 of [3]. | | - -##### 6.3.3.4a E2-related API Cause - -The purpose of the E2-related API Cause IE is to indicate the reason for a particular event for the E2-related APIs. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|-----------------------| -|---------------|----------|-------|-----------------------|-----------------------| - -| | | | | | -|------------------------------------------|---|--|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| CHOICE E2-related API Cause Group | M | | | | -| > Application Layer | | | | | -| >>Application Layer Cause | M | | ENUMERATED
(Unspecified,
Global E2Node ID invalid, E2 Node Reset or Disconnected,
RAN Function ID invalid, Action not supported,
Excessive actions, Duplicate action, E2 Request ID unknown,
Control conflict, E2 Indication unknown, E2AP Procedure timeout,
Essential for operation, ...) | | -| > Transport Layer | | | | | -| >>Transport Layer Cause | M | | ENUMERATED
(Unspecified, Transport Resource Unavailable, ...) | | -| > Protocol | | | | | -| >>Protocol Cause | M | | ENUMERATED
(Unspecified, Transfer Syntax Error, Abstract Syntax Error (Reject),
Abstract Syntax Error (Ignore and Notify), Message not Compatible with
Receiver State, Semantic Error, Abstract Syntax Error (Falsely Constructed Message), ...) | | -| > Misc | | | | | -| >>Miscellaneous Cause | M | | ENUMERATED
(Unspecified, Control Processing Overload, Hardware Failure, O&M Intervention, ...) | | - -The meaning of the different cause values is described in the following table. In general, "not supported" cause values indicate that the related capability is missing. On the other hand, "not available" cause values indicate that the related capability is present, but insufficient resources were available to perform the requested action. - -| Application Layer cause | Meaning | -|-------------------------------|--------------------------------------------------------------------------------------------------------------| -| Unspecified | Sent when none of the cause values below applies but still the cause is Application Layer related. | -| Global E2Node ID invalid | Global E2Node ID invalid. | -| E2 Node Reset or Disconnected | E2Node Status is Reset or Disconnected. | -| RAN Function ID invalid | Requested RAN Function ID invalid. | -| Action not supported | Requested Action not supported by RAN function. | -| Excessive actions | Excessive number of actions requested for RAN Function. | -| Duplicate action | Same action requested more than once in same subscription request. | -| E2 Request ID unknown | E2 Request ID sent to Near-RT RIC is unknown. | -| Control Conflict | Requested Control command causes conflict. | -| E2 Indication unknown | The E2 Indication message is unknown, i.e. The received indication message is not subscribed to by the xApp. | -| E2AP Procedure timeout | An E2AP procedure triggered by the E2-related API procedure is time-out. | -| Essential for operation | xApp is unwilling to delete an E2 subscription essential for its operation. | - -| Transport Layer cause | Meaning | -|-----------------------|---------| -|-----------------------|---------| - -| | | -|--------------------------------|--------------------------------------------------------------------------------------------------| -| Unspecified | Sent when none of the cause values below applies but still the cause is Transport Layer related. | -| Transport Resource Unavailable | The required transport resources are not available. | - -| Protocol cause | Meaning | -|-----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| -| Unspecified | Sent when none of the below cause values applies but still the cause is Protocol related. | -| Transfer Syntax Error | The received message included a transfer syntax error. | -| Abstract Syntax Error (Reject) | The received message included an abstract syntax error and the concerning criticality indicated "reject". | -| Abstract Syntax Error (Ignore And Notify) | The received message included an abstract syntax error and the concerning criticality indicated "ignore and notify". | -| Message Not Compatible With Receiver State | The received message was not compatible with the receiver state. | -| Semantic Error | The received message included a semantic error. | -| Abstract Syntax Error (Falsely Constructed Message) | The received message contained IEs or IE groups in wrong order or with too many occurrences. | - -| Miscellaneous cause | Meaning | -|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| -| Unspecified Failure | Sent when none of the below cause values applies and the cause is not related to any of the categories Application Layer, Transport Layer, Protocol. | -| Control Processing Overload | Control processing overload. | -| Hardware Failure | Action related to hardware failure. | -| O&M Intervention | The action is due to O&M intervention. | - -#### 6.3.3.5 Criticality Diagnostics - -The Criticality Diagnostics IE is sent by the xApp or the Near-RT RIC Platform when parts of a received message have not been comprehended or were missing. When applicable, it contains information about which IEs were not comprehended or were missing. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|----------------------------------------------------|----------|-----------------------|--------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| -| Information Element Criticality Diagnostics | | 0 .. | | | -| >IE Criticality | M | | ENUMERATED (reject, ignore, notify) | The IE Criticality is used for reporting the criticality of the triggering IE. The value 'ignore' shall not be used. | -| >IE ID | M | | ENUMERATED (Message Type, Procedure Transaction ID, Global E2 Node ID, RAN Function ID...) | The IE ID of the not understood or missing IE. | -| >Type of Error | M | | ENUMERATED (not understood, missing, ...) | | - -| Range bound | Explanation | -|----------------|--------------------------------------------------------------------------------------| -| maxnoo fErrors | Maximum no. of IE errors allowed to be reported with a single message. Value is 256. | - -#### 6.3.3.6 E2 Control Timer - -This IE specifies the suggested time to wait before timeout for the RIC Control procedure in E2AP[3]. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|-----------------------| -|---------------|----------|-------|-----------------------|-----------------------| - -| | | | | | -|------------------|---|--|--------------------------|-----------------------| -| E2 Control Timer | M | | INTEGER (10..10000, ...) | Unit in milliseconds. | -|------------------|---|--|--------------------------|-----------------------| - -#### 6.3.3.7 E2 Subscription Timer - -This IE specifies the suggested time to wait before timeout for the RIC subscription procedure in E2AP[3]. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-----------------------|----------|-------|--------------------------|-----------------------| -| E2 Subscription Timer | M | | INTEGER (10..10000, ...) | Unit in milliseconds. | - -#### 6.3.3.8 E2 Subscription Delete Timer - -This IE specifies the suggested time to wait before timeout for the RIC subscription deletion procedure in E2AP[3]. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------------|----------|-------|--------------------------|-----------------------| -| E2 Subscription Delete Timer | M | | INTEGER (10..10000, ...) | Unit in milliseconds. | - -### 6.3.4 Message and Information Element Abstract Syntax - -#### 6.3.4.1 Void - -#### 6.3.4.2 gRPC with Protocol Buffers - -##### 6.3.4.2.1 Usage of gRPC with Protocol Buffers - -This solution uses Protocol Buffers as message encoding, and also as the Interface Definition Language (IDL) for gRPC [5]. - -Table 6.3.4.2.1-1 lists the mapping of E2 related APIs and corresponding gRPC services. - -**Table 6.3.4.2.1-1: Mapping of E2 related APIs and gRPC services** - -| API Name | gRPC service(s) | -|---------------------|---------------------------------------------------| -| E2 Subscription API | E2 Subscription API, E2 Subscription API Callback | -| E2 Indication API | E2 Indication API | -| E2 Control API | E2 Control API | -| E2 Query API | E2 Query API | - -A procedure of an E2 related API is mapped to a *gRPC method*. - -Table 6.3.4.2.1-2 lists the E2 related APIs abstract syntax included in this document. - -**Table 6.3.4.2.1-2: List of E2 related APIs abstract syntax** - -| API Name / Contents | Clause | Version | File Name | -|---------------------------------------------|-------------|---------|---------------------------------------------| -| E2 Subscription API | 6.3.4.2.2.1 | 1.1.0 | e2_subscription_api_grpc_ver_1_1_0.proto | -| E2 Indication API | 6.3.4.2.2.2 | 1.0.0 | e2_indication_api_grpc_ver_1_0_0.proto | -| E2 Control API | 6.3.4.2.2.3 | 1.0.0 | e2_control_api_grpc_ver_1_0_0.proto | -| E2 Query API | 6.3.4.2.2.4 | 1.0.0 | e2_query_api_grpc_ver_1_0_0.proto | -| E2 related API common information elements | 6.3.4.2.3 | 1.2.0 | e2_related_apis_common_ies_ver_1_2_0.proto | -| Near-RT RIC API common information elements | 10.2.1 | 3.0.0 | near_rt_ric_apis_common_ies_ver_3_0_0.proto | - -##### 6.3.4.2.2 API Definitions - -###### 6.3.4.2.2.1 E2\_Subscription\_API - -``` -syntax = "proto3"; - -package ricapi.e2_subscription_api_grpc.v1; - -import "e2_related_apis_common_ies_ver_1_2_0.proto"; -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; - -// gRPC service and rpc definition -service E2_Subscription_API { - rpc E2SubscriptionProc(E2SubscriptionInitMsg) returns (E2SubscriptionOutMsg) {}; - rpc E2SubscriptionDeleteProc(E2SubscriptionDeleteInitMsg) returns (E2SubscriptionDeleteOutMsg) {}; - rpc E2SubscriptionModificationProc(E2SubscriptionModificationInitMsg) returns -(E2SubscriptionModificationOutMsg) {}; -} - -message E2SubscriptionInitMsg { - optional E2SubscriptionRequest e2_subscription_request = 1; -} - -message E2SubscriptionOutMsg { - oneof type_of_message { - E2SubscriptionSuccess e2_subscription_success = 1; - E2SubscriptionReject e2_subscription_reject = 2; - E2SubscriptionFailure e2_subscription_failure = 3; - } -} - -message E2SubscriptionDeleteInitMsg { - optional E2SubscriptionDeleteRequest e2_subscription_delete_request = 1; -} - -message E2SubscriptionDeleteOutMsg { - oneof type_of_message { - E2SubscriptionDeleteSuccess e2_subscription_delete_success = 1; - E2SubscriptionDeleteReject e2_subscription_delete_reject = 2; - E2SubscriptionDeleteFailure e2_subscription_delete_failure = 3; - } -} - -message E2SubscriptionModificationInitMsg { - optional E2SubscriptionModificationRequest e2_subscription_modification_request = 1; -} - -message E2SubscriptionModificationOutMsg { - oneof type_of_message { - E2SubscriptionModificationSuccess e2_subscription_modification_success = 1; - E2SubscriptionModificationReject e2_subscription_modification_reject = 2; - E2SubscriptionModificationFailure e2_subscription_modification_failure = 3; - } -} - -service E2 Subscription API Callback { - rpc E2SubscriptionDeleteQueryProc(E2SubscriptionDeleteQueryInitMsg) returns -(E2SubscriptionDeleteQueryOutMsg) {}; - rpc E2SubscriptionDeleteNotificationProc(E2SubscriptionDeleteNotificationInitMsg) returns -(E2SubscriptionDeleteNotificationOutMsg) {}; -} - -message E2SubscriptionDeleteQueryInitMsg { - optional E2SubscriptionDeleteQueryRequired e2_subscription_delete_query_required = 1; -} - -message E2SubscriptionDeleteQueryOutMsg { - oneof type_of_message { - E2SubscriptionDeleteQueryAccept e2_subscription_delete_query_accept = 1; - E2SubscriptionDeleteQueryDecline e2_subscription_delete_query_reject = 2; - } -} - -message E2SubscriptionDeleteNotificationInitMsg { - optional E2SubscriptionDeleteNotificationDeleted e2_subscription_delete_notification_deleted = 1; -} -``` - -``` - -} - -message E2SubscriptionDeleteNotificationOutMsg { -} - -// ----- messages of E2 Subscription API ----- -// ----- messages of E2 Subscription procedure ----- -message E2SubscriptionRequest { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 3; - optional E2SubscriptionDetails e2_subscription_details = 4; - optional uint32 e2_subscription_timer = 5; - optional near_rt_ric_apis_common_ies.v3.EndpointInformation e2_indication_destination = 6; - optional near_rt_ric_apis_common_ies.v3.EndpointInformation -e2_subscription_delete_notification_destination = 7; - - message E2SubscriptionDetails { - optional e2_related_apis_common_ies.v1.E2EventTriggerDefinition e2_event_trigger_definition = 1; - repeated E2ActionToBeSetupItem sequence_of_actions = 2 ; - - message E2ActionToBeSetupItem { - optional e2_related_apis_common_ies.v1.E2ActionId requested_e2_action_id = 1 ; - optional e2_related_apis_common_ies.v1.E2ActionType e2_action_type = 2 ; - optional e2_related_apis_common_ies.v1.E2ActionDefinition e2_action_definition = 3 ; - optional e2_related_apis_common_ies.v1.E2SubsequentAction e2_subsequent_action = 4 ; - } - } -} - -message E2SubscriptionSuccess { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional e2_related_apis_common_ies.v1.E2RequestId e2_request_id = 3; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 4; - repeated E2ActionAdmittedItem e2_actions_admitted_list = 5; - repeated E2ActionNotAdmittedItem e2_actions_not_admitted_list = 6; - - message E2ActionAdmittedItem { - optional e2_related_apis_common_ies.v1.E2ActionId requested_e2_action_id = 1 ; - optional e2_related_apis_common_ies.v1.E2ActionId e2_action_id = 2 ; - } - - message E2ActionNotAdmittedItem { - optional e2_related_apis_common_ies.v1.E2ActionId requested_e2_action_id = 1 ; - optional e2_related_apis_common_ies.v1.Cause cause = 2 ; - } -} - -message E2SubscriptionFailure { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 3; - optional e2_related_apis_common_ies.v1.Cause cause = 4; - optional e2_related_apis_common_ies.v1.CriticalityDiagnostics criticality_diagnostics = 5; -} - -message E2SubscriptionReject { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 3; - optional e2_related_apis_common_ies.v1.Cause cause = 4; - optional e2_related_apis_common_ies.v1.CriticalityDiagnostics criticality_diagnostics = 5; -} - -// ----- messages of E2 Subscription Delete procedure ----- -message E2SubscriptionDeleteRequest { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional e2_related_apis_common_ies.v1.E2RequestId e2_request_id = 3; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 4; - optional uint32 e2_subscription_delete_timer = 5; -} - -``` - -``` - -} - -message E2SubscriptionDeleteSuccess { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional e2_related_apis_common_ies.v1.E2RequestId e2_request_id = 3; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 4; -} - -message E2SubscriptionDeleteFailure { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional e2_related_apis_common_ies.v1.E2RequestId e2_request_id = 3; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 4; - optional e2_related_apis_common_ies.v1.Cause cause = 5; - optional e2_related_apis_common_ies.v1.CriticalityDiagnostics criticality_diagnostics = 6; -} - -message E2SubscriptionDeleteReject { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional e2_related_apis_common_ies.v1.E2RequestId e2_request_id = 3; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 4; - optional e2_related_apis_common_ies.v1.Cause cause = 5; - optional e2_related_apis_common_ies.v1.CriticalityDiagnostics criticality_diagnostics = 6; -} - -// ----- messages of E2 Subscription Delete Query procedure ----- -message E2SubscriptionDeleteQueryRequired { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional e2_related_apis_common_ies.v1.E2RequestId e2_request_id = 3; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 4; - optional e2_related_apis_common_ies.v1.Cause cause = 5; -} - -message E2SubscriptionDeleteQueryAccept { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional e2_related_apis_common_ies.v1.E2RequestId e2_request_id = 3; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 4; -} - -message E2SubscriptionDeleteQueryDecline { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional e2_related_apis_common_ies.v1.E2RequestId e2_request_id = 3; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 4; - optional e2_related_apis_common_ies.v1.Cause cause = 5; -} - -// ----- messages of E2 Subscription Delete Notification procedure ----- -message E2SubscriptionDeleteNotificationDeleted { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional e2_related_apis_common_ies.v1.E2RequestId e2_request_id = 3; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 4; - optional e2_related_apis_common_ies.v1.Cause cause = 5; -} - -// ----- messages of E2 Subscription Modification procedure ----- -message E2SubscriptionModificationRequest { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional e2_related_apis_common_ies.v1.E2RequestId e2_request_id = 3; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 4; - optional E2SubscriptionModificationDetails e2_subscription_details = 5; - - message E2SubscriptionModificationDetails { - optional e2_related_apis_common_ies.v1.E2EventTriggerDefinition e2_event_trigger_definition = 1; - repeated E2ActionToBeAddedItem sequence_of_actions_added = 2 ; - repeated E2ActionToBeModifiedItem sequence_of_actions_modified = 3 ; - } -} - -``` - -``` - -repeated E2ActionToBeRemovedItem sequence_of_actions_removed = 4 ; - -message E2ActionToBeAddedItem { - optional e2_related_apis_common_ies.v1.E2ActionId requested_e2_action_id = 1 ; - optional e2_related_apis_common_ies.v1.E2ActionType e2_action_type = 2 ; - optional e2_related_apis_common_ies.v1.E2ActionDefinition e2_action_definition = 3 ; - optional e2_related_apis_common_ies.v1.E2SubsequentAction e2_subsequent_action = 4 ; -} - -message E2ActionToBeModifiedItem { - optional e2_related_apis_common_ies.v1.E2ActionId e2_action_id = 1 ; - optional e2_related_apis_common_ies.v1.E2ActionType e2_action_type = 2 ; - optional e2_related_apis_common_ies.v1.E2ActionDefinition e2_action_definition = 3 ; - optional e2_related_apis_common_ies.v1.E2SubsequentAction e2_subsequent_action = 4 ; -} - -message E2ActionToBeRemovedItem { - optional e2_related_apis_common_ies.v1.E2ActionId e2_action_id = 1 ; -} -} - -message E2SubscriptionModificationSuccess { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional e2_related_apis_common_ies.v1.E2RequestId e2_request_id = 3; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 4; - repeated E2ActionAddedAdmittedItem e2_actions_added_admitted_list = 5; - repeated E2ActionAddedNotAdmittedItem e2_actions_added_not_admitted_list = 6; - repeated E2ActionModifiedAdmittedItem e2_actions_modified_admitted_list = 7; - repeated E2ActionModifiedNotAdmittedItem e2_actions_modified_not_admitted_list = 8; - repeated E2ActionRemovedAdmittedItem e2_actions_removed_admitted_list = 9; - repeated E2ActionReemovedNotAdmittedItem e2_actions_removed_not_admitted_list = 10; - - message E2ActionAddedAdmittedItem { - optional e2_related_apis_common_ies.v1.E2ActionId requested_e2_action_id = 1 ; - optional e2_related_apis_common_ies.v1.E2ActionId e2_action_id = 2 ; - } - - message E2ActionAddedNotAdmittedItem { - optional e2_related_apis_common_ies.v1.E2ActionId requested_e2_action_id = 1 ; - optional e2_related_apis_common_ies.v1.Cause cause = 2 ; - } - - message E2ActionModifiedAdmittedItem { - optional e2_related_apis_common_ies.v1.E2ActionId e2_action_id = 1 ; - optional e2_related_apis_common_ies.v1.E2ActionId modified_e2_action_id = 2 ; - } - - message E2ActionModifiedNotAdmittedItem { - optional e2_related_apis_common_ies.v1.E2ActionId e2_action_id = 1 ; - optional e2_related_apis_common_ies.v1.Cause cause = 2 ; - } - - message E2ActionRemovedAdmittedItem { - optional e2_related_apis_common_ies.v1.E2ActionId e2_action_id = 1 ; - } - - message E2ActionReemovedNotAdmittedItem { - optional e2_related_apis_common_ies.v1.E2ActionId e2_action_id = 1 ; - optional e2_related_apis_common_ies.v1.Cause cause = 2 ; - } -} - -message E2SubscriptionModificationFailure { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 3; - optional e2_related_apis_common_ies.v1.Cause cause = 4; - optional e2_related_apis_common_ies.v1.CriticalityDiagnostics criticality_diagnostics = 5; -} - -message E2SubscriptionModificationReject { - -``` - -``` - -optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; -optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; -optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 3; -optional e2_related_apis_common_ies.v1.Cause cause = 4; -optional e2_related_apis_common_ies.v1.CriticalityDiagnostics criticality_diagnostics = 5; -} - -``` - -###### 6.3.4.2.2.2 E2\_Indication\_API - -``` - -syntax = "proto3"; - -package ricapi.e2_indication_api_grpc.v1; - -import "e2_related_apis_common_ies_ver_1_2_0.proto"; -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; - -// gRPC service and rpc definition -service E2_Indication_API { - rpc E2IndicationProc(E2IndicationInitMsg) returns (E2IndicationOutMsg) {}; -} - -message E2IndicationInitMsg { - optional E2IndicationPush e2_indication_push = 1; -} - -message E2IndicationOutMsg { - oneof type_of_message { - EmptyMessage empty_message = 1; - E2IndicationFailure e2_indication_failure = 2; - } - - message EmptyMessage { - } -} - -// ----- messages of E2_Indication_API ----- -// ----- messages of E2 Indication procedure ----- -message E2IndicationPush { - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 1; - optional e2_related_apis_common_ies.v1.E2RequestId e2_request_id = 2; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 3; - optional e2_related_apis_common_ies.v1.E2ActionId e2_action_id = 4; - optional e2_related_apis_common_ies.v1.E2IndicationSN e2_indication_sn = 5; - optional e2_related_apis_common_ies.v1.E2IndicationType e2_indication_type = 6; - optional e2_related_apis_common_ies.v1.E2IndicationHeader e2_indication_header = 7; - optional e2_related_apis_common_ies.v1.E2IndicationMessage e2_indication_message = 8; - optional e2_related_apis_common_ies.v1.E2CallProcessId e2_call_process_id = 9; -} - -message E2IndicationFailure { - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 1; - optional e2_related_apis_common_ies.v1.E2RequestId e2_request_id = 2; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 3; - optional e2_related_apis_common_ies.v1.E2ActionId e2_action_id = 4; - optional e2_related_apis_common_ies.v1.E2IndicationSN e2_indication_sn = 5; - optional e2_related_apis_common_ies.v1.Cause cause = 6; - optional e2_related_apis_common_ies.v1.CriticalityDiagnostics criticality_diagnostics = 7; -} - -``` - -###### 6.3.4.2.2.3 E2\_Control\_API - -``` - -syntax = "proto3"; - -package ricapi.e2_control_api_grpc.v1; - -import "e2_related_apis_common_ies_ver_1_2_0.proto"; -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; - -// gRPC service and rpc definition -service E2_Control_API { - rpc E2ControlProc(E2ControlInitMsg) returns (E2ControlOutMsg) {}; -} - -``` - -``` - -} - -message E2ControlInitMsg { - optional E2ControlRequest e2_control_request = 1; -} - -message E2ControlOutMsg { - oneof type of message { - E2ControlSuccess e2_control_success = 1; - E2ControlReject e2_control_reject = 2; - E2ControlFailure e2_control_failure = 3; - } -} - -// ----- messages of E2_Control_API ----- -// ----- messages of E2 Control procedure ----- -message E2ControlRequest { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 3; - optional e2_related_apis_common_ies.v1.E2CallProcessId e2_call_process_id = 4; - optional e2_related_apis_common_ies.v1.E2ControlHeader e2_control_header = 5; - optional e2_related_apis_common_ies.v1.E2ControlMessage e2_control_message = 6; - optional e2_related_apis_common_ies.v1.E2ControlAckRequest e2_control_ack_request = 7; - optional uint32 e2_control_timer = 8; -} - -message E2ControlSuccess { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 3; - optional e2_related_apis_common_ies.v1.E2CallProcessId e2_call_process_id = 4; - optional e2_related_apis_common_ies.v1.E2ControlOutcome e2_control_outcome = 5; -} - -message E2ControlReject { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 3; - optional e2_related_apis_common_ies.v1.Cause cause = 4; - optional e2_related_apis_common_ies.v1.CriticalityDiagnostics criticality_diagnostics = 5; -} - -message E2ControlFailure { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 3; - optional e2_related_apis_common_ies.v1.E2CallProcessId e2_call_process_id = 4; - optional e2_related_apis_common_ies.v1.E2ControlOutcome e2_control_outcome = 5; - optional e2_related_apis_common_ies.v1.Cause cause = 6; - optional e2_related_apis_common_ies.v1.CriticalityDiagnostics criticality_diagnostics = 7; -} - -``` - -###### 6.3.4.2.2.4 E2\_Query\_API - -``` - -syntax = "proto3"; - -package ricapi.e2_query_api_grpc.v1; - -import "e2_related_apis_common_ies_ver_1_2_0.proto"; -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; - -// gRPC service and rpc definition -service E2_Query_API { - rpc E2QueryProc(E2QueryInitMsg) returns (E2QueryOutMsg) {}; -} - -message E2QueryInitMsg { - optional E2QueryRequest e2_query_request = 1; -} - -``` - -``` - -message E2QueryOutMsg { - oneof type_of_message { - E2QuerySuccess e2_query_success = 1; - E2QueryReject e2_query_reject = 2; - E2QueryFailure e2_query_failure = 3; - } -} - -// ----- messages of E2_Query_API ----- -// ----- messages of E2 Query procedure ----- -message E2QueryRequest { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 3; - optional e2_related_apis_common_ies.v1.E2QueryHeader e2_query_header = 4; - optional e2_related_apis_common_ies.v1.E2QueryDefinition e2_query_definition = 5; -} - -message E2QuerySuccess { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 3; - optional e2_related_apis_common_ies.v1.E2QueryOutcome e2_query_outcome = 4; -} - -message E2QueryReject { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 3; - optional e2_related_apis_common_ies.v1.Cause cause = 4; - optional e2_related_apis_common_ies.v1.CriticalityDiagnostics criticality_diagnostics = 5; -} - -message E2QueryFailure { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId global_e2_node_id = 2; - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 3; - optional e2_related_apis_common_ies.v1.E2QueryOutcome e2_query_outcome = 4; - optional e2_related_apis_common_ies.v1.Cause cause = 5; - optional e2_related_apis_common_ies.v1.CriticalityDiagnostics criticality_diagnostics = 6; -} - -``` - -##### 6.3.4.2.3 Information Element Definitions - -``` - -syntax = "proto3"; - -package ricapi.e2_related_apis_common_ies.v1; - -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; - -// ----- Information Elements ----- -// -----E----- -// From E2AP Clause 9.2.11 -enum E2ActionType { - E2ACTION_TYPE_REPORT = 0; - E2ACTION_TYPE_INSERT = 1; - E2ACTION_TYPE_POLICY = 2; -}; - -// From E2AP Clause 9.2.21 -enum E2ControlAckRequest { - E2_CONTROL_ACK_REQUEST_NO_ACK = 0; - E2_CONTROL_ACK_REQUEST_ACK = 1; -} - -// From E2AP Clause 9.2.15 -enum E2IndicationType { - E2_INDICATION_TYPE_REPORT = 0; -} - -``` - -``` - - E2_INDICATION_TYPE_INSERT = 1; -} - -// -----C----- -message Cause { - oneof cause_group { - E2RelatedApiCause e2_related_api_cause = 1; - E2apCause e2ap_cause = 2; - } - - message E2apCause { - oneof cause_group { - RicRequest ric_request = 1; - RicService ric_service = 2; - E2Node e2_node = 3; - Transport transport = 4; - Protocol protocol = 5; - Misc misc = 6; - } - - enum E2Node { - E2NODE_COMPONENT_UNKNOWN = 0; - } - - enum Misc { - CONTROL_PROCESSING_OVERLOAD = 0; - HARDWARE_FAILURE = 1; - OM_INTERVENTION = 2; - MISC_UNSPECIFIED = 3; - } - - enum Protocol { - TRANSFER_SYNTAX_ERROR = 0; - ABSTRACT_SYNTAX_ERROR_REJECT = 1; - ABSTRACT_SYNTAX_ERROR_IGNORE_AND_NOTIFY = 2; - MESSAGE_NOT_COMPATIBLE_WITH_RECEIVER_STATE = 3; - SEMANTIC_ERROR = 4; - ABSTRACT_SYNTAX_ERROR_FALSELY_CONSTRUCTED_MESSAGE = 5; - PROTOCOL_UNSPECIFIED = 6; - } - - enum RicRequest { - RAN_FUNCTION_ID_INVALID = 0; - ACTION_NOT_SUPPORTED = 1; - EXCESSIVE_ACTIONS = 2; - DUPLICATE_ACTION = 3; - DUPLICATE_EVENT_TRIGGER = 4; - FUNCTION_RESOURCE_LIMIT = 5; - REQUEST_ID_UNKNOWN = 6; - INCONSISTENT_ACTION_SUBSEQUENT_ACTION_SEQUENCE = 7; - CONTROL_MESSAGE_INVALID = 8; - RIC_CALL_PROCESS_ID_INVALID = 9; - CONTROL_TIMER_EXPIRED = 10; - CONTROL_FAILED_TO_EXECUTE = 11; - SYSTEM_NOT_READY = 12; - RIC_REQUEST_UNSPECIFIED = 13; - } - - enum RicService { - RAN_FUNCTION_NOT_SUPPORTED = 0; - EXCESSIVE_FUNCTIONS = 1; - RIC_RESOURCE_LIMIT = 2; - } - - enum Transport { - TRANSPORT_UNSPECIFIED = 0; - TRANSPORT_RESOURCE_UNAVAILABLE = 1; - } - } -} - -message E2RelatedApiCause { - oneof cause_group { - ApplicationLayer application_layer = 1; - } -} - -``` - -``` - - Transport transport = 2; - Protocol protocol = 3; - Misc misc = 4; - } - - enum ApplicationLayer { - APPLICATION_LAYER_UNSPECIFIED = 0; - GLOBAL_E2_NODE_ID_INVALID = 1; - E2_NODE_RESET_OR_DISCONNECTED = 2; - RAN_FUNCTION_ID_INVALID = 3; - ACTION_NOT_SUPPORTED = 4; - EXCESSIVE_ACTIONS = 5; - DUPLICATE_ACTION = 6; - E2_REQUEST_ID_UNKNOWN = 7; - CONTROL_CONFLICT = 8; - E2_INDICATION_UNKNOWN = 9; - E2AP_PROCEDURE_TIMEOUT = 10; - ESSENTIAL_FOR_OPERATION = 11; - } - - enum Misc { - MISC_UNSPECIFIED = 0; - CONTROL_PROCESSING_OVERLOAD = 1; - HARDWARE_FAILURE = 2; - OM_INTERVENTION = 3; - } - - enum Protocol { - PROTOCOL_UNSPECIFIED = 0; - TRANSFER_SYNTAX_ERROR = 1; - ABSTRACT_SYNTAX_ERROR_REJECT = 2; - ABSTRACT_SYNTAX_ERROR_IGNORE_AND_NOTIFY = 3; - MESSAGE_NOT_COMPATIBLE_WITH_RECEIVER_STATE = 4; - SEMANTIC_ERROR = 5; - ABSTRACT_SYNTAX_ERROR_FALSELY_CONSTRUCTED_MESSAGE = 6; - } - - enum Transport { - TRANSPORT_UNSPECIFIED = 0; - TRANSPORT_RESOURCE_UNAVAILABLE = 1; - } -} - -message CriticalityDiagnostics { - repeated IeCriticalityDiagnosticsItem ie_criticality_diagnostics_list = 1; - - message IeCriticalityDiagnosticsItem { - optional IeCriticality ie_criticality = 1; - optional IeId ie_id = 2; - optional TypeOfError type_of_error = 3; - } - - enum IeCriticality { - IE_CRITICALITY_REJECT = 0; - IE_CRITICALITY_IGNORE = 1; - IE_CRITICALITY_NOTIFY = 2; - } - - enum IeId { - IE_ID_CAUSE = 0; - IE_ID_CRITICALITY_DIAGNOSTICS = 1; - IE_ID_E2_ACTION_ID = 2; - IE_ID_E2_ACTIONS ADMITTED_LIST = 3; - IE_ID_E2_ACTIONS NOT ADMITTED_LIST = 4; - IE_ID_E2_CALL_PROCESS_ID = 5; - IE_ID_E2_CONTROL_ACK_REQUEST = 6; - IE_ID_E2_CONTROL_HEADER = 7; - IE_ID_E2_CONTROL_MESSAGE = 8; - IE_ID_E2_CONTROL_OUTCOME = 9; - IE_ID_E2_CONTROL_TIMER = 10; - IE_ID_E2_INDICATION_HEADER = 11; - } -} - -``` - -``` - IE_ID_E2_INDICATION_MESSAGE = 12; - IE_ID_E2_INDICATION_SN = 13; - IE_ID_E2_INDICATION_TYPE = 14; - IE_ID_E2_REQUEST_ID = 15; - IE_ID_E2_SUBSCRIPTION_DETAILS = 16; - IE_ID_GLOBAL_E2_NODE_ID = 17; - IE_ID_PROCEDURE_TRANSACTION_ID = 18; - IE_ID_RAN_FUNCTION_ID = 19; - IE_ID_SEQUENCE_OF_ACTIONS = 20; - IE_ID_E2_SUBSCRIPTION_TIMER = 21; - IE_ID_E2_SUBSCRIPTION_DELETE_TIMER = 22; - } - - enum TypeOfError { - TYPE_OF_ERROR_NOT_UNDERSTOOD = 0; - TYPE_OF_ERROR_MISSING = 1; - } -} - -// -----E----- -message E2ActionDefinition { - optional bytes value = 1; -}; - -message E2ActionId { - optional uint32 value = 1; -}; - -message E2CallProcessId { - optional bytes value = 1; -}; - -message E2ControlHeader { - optional bytes value = 1; -}; - -message E2ControlMessage { - optional bytes value = 1; -}; - -message E2ControlOutcome { - optional bytes value = 1; -}; - -message E2EventTriggerDefinition { - optional bytes value = 1; -}; - -message E2IndicationHeader { - optional bytes value = 1; -}; - -message E2IndicationMessage { - optional bytes value = 1; -}; - -message E2IndicationSN { - optional uint32 value = 1; -}; - -message E2RequestId { - optional uint32 value = 1; -}; - -message E2QueryHeader { - optional bytes value = 1; -}; - -message E2QueryDefinition { - optional bytes value = 1; -}; -``` - -``` - -message E2QueryOutcome { - optional bytes value = 1; -}; - -// From E2AP Clause 9.2.13 -message E2SubsequentAction { - optional SubsequentActionType subsequent_action_type = 1; - optional TimeToWait e2_time_to_wait = 2; - - enum SubsequentActionType { - SUBSEQUENT_ACTION_TYPE_CONTINUE = 0; - SUBSEQUENT_ACTION_TYPE_WAIT = 1; - }; - - enum TimeToWait { - TIME_TO_WAIT_W1MS = 0; - TIME_TO_WAIT_W2MS = 1; - TIME_TO_WAIT_W5MS = 2; - TIME_TO_WAIT_W10MS = 3; - TIME_TO_WAIT_W20MS = 4; - TIME_TO_WAIT_W30MS = 5; - TIME_TO_WAIT_W40MS = 6; - TIME_TO_WAIT_W50MS = 7; - TIME_TO_WAIT_W100MS = 8; - TIME_TO_WAIT_W200MS = 9; - TIME_TO_WAIT_W500MS = 10; - TIME_TO_WAIT_W1S = 11; - TIME_TO_WAIT_W2S = 12; - TIME_TO_WAIT_W5S = 13; - TIME_TO_WAIT_W10S = 14; - TIME_TO_WAIT_W20S = 15; - TIME_TO_WAIT_W60S = 16; - } -}; - -``` - -### 6.3.5 Message Transfer Syntax - -#### 6.3.5.1 Void - -#### 6.3.5.2 gRPC with Protocol Buffers - -The message transfer syntax for Solution 2 is serialized Protocol Buffers [4]. - -# --- 7 SDL API - -## 7.1 Overview - -### 7.1.1 Protocol Stack - -In this version of specification, the default and optional protocol stacks for the SDL APIs are shown on Figure 7.1.1-1. - -NOTE: The security protocols are specified in [6]. - -![Protocol stack for SDL APIs diagram showing layers from Application down to Physical Layer.](52c40e2f443985dc63f45dec57d90c8c_img.jpg) - -``` - - graph TD - Application --- gRPC - gRPC --- HTTP2 - HTTP2 --- TCP - TCP --- IP - IP --- DataLink[Data Link Layer] - DataLink --- Physical[Physical Layer] - -``` - -Protocol stack for SDL APIs diagram showing layers from Application down to Physical Layer. - -**Figure 7.1.1-1: Protocol stack for SDL APIs** - -The E2-related APIs use gRPC [5] with Protocol Buffers [4] as the application layer serialization protocol. - -### 7.1.2 List of SDL APIs, procedures and messages - -The SDL API procedures introduced in clause 9.5 of [2] are categorized under the SDL APIs. These APIs include: - -- SDL Information API: enabling subscription and retrieval of information by xApps. -- xApp Data Sharing API: enabling xApp to share specific data with Near-RT RIC platform and/or other data consumer xApps. - -These APIs are summarized in Table 7.1.2-1. - -**Table 7.1.2-1: List of SDL APIs** - -| API Name | Description | -|-----------------------|------------------------------------------------------------| -| SDL_Information_API | Near-RT RIC platform service for SDL information operation | -| Xapp_Data_Sharing_API | xApp service to share SDL data produced by the xApp | - -The table 7.1.2-2 lists the API procedures for each SDL API. - -**Table 7.1.2-2: List of SDL API procedures** - -| API Name | API procedure | Communication type | -|-----------------------|--------------------------------------|--------------------| -| SDL_Information_API | SDL Information Subscribe | Request/Response | -| | SDL Information Push | Notify | -| | SDL Information Update Notify | Notify | -| | SDL Information Fetch | Request/Response | -| Xapp_Data_Sharing_API | Xapp Shared Data Fetch | Request/Response | -| | Xapp Shared Data Subscribe | Request/Response | -| | Xapp Shared Data Subscription Delete | Request/Response | -| | Xapp Shared Data Push | Notify | - -The table 7.1.2-3 lists the messages for each SDL API procedure. - -**Table 7.1.2-3: List of SDL API messages** - -| API Procedure | Initiated by | Initiating Message | Outcome Message | | -|---------------------------|--------------|-------------------------------|--------------------------------|-------------------------------| -| | | | Successful Outcome | Unsuccessful Outcome | -| SDL Information Subscribe | xApp | SUBSCRIBE INFORMATION REQUEST | SUBSCRIBE INFORMATION RESPONSE | SUBSCRIBE INFORMATION FAILURE | - -| | | | | | -|--------------------------------------|--------------------------------------------|----------------------------------------------|-----------------------------------------------|----------------------------------------------| -| SDL Information Push | Near-RT RIC platform | INFORMATION PUSH | - | - | -| SDL Information Update Notify | Near-RT RIC platform | INFORMATION UPDATE NOTIFY | - | - | -| SDL Information Fetch | xApp | INFORMATION FETCH REQUEST | INFORMATION FETCH RESPONSE | INFORMATION FETCH FAILURE | -| Xapp Shared Data Fetch | Near-RT RIC platform or data consumer xApp | XAPP SHARED DATA FETCH REQUEST | XAPP SHARED DATA FETCH RESPONSE | XAPP SHARED DATA FETCH FAILURE | -| Xapp Shared Data Subscribe | Near-RT RIC platform or data consumer xApp | XAPP SHARED DATA SUBSCRIPTION REQUEST | XAPP SHARED DATA SUBSCRIPTION RESPONSE | XAPP SHARED DATA SUBSCRIPTION FAILURE | -| Xapp Shared Data Subscription Delete | Near-RT RIC platform or data consumer xApp | XAPP SHARED DATA SUBSCRIPTION DELETE REQUEST | XAPP SHARED DATA SUBSCRIPTION DELETE RESPONSE | XAPP SHARED DATA SUBSCRIPTION DELETE FAILURE | -| Xapp Shared Data Push | xApp | XAPP SHARED DATA PUSH | - | - | - -The table 7.1.2-4 lists the supported data categories for each SDL API in this release. - -**Table 7.1.2-4: Supported Data Categories** - -| API Name | Supported Data Categories | -|-----------------------|---------------------------| -| SDL_Information_API | E2 Node Information | -| Xapp_Data_Sharing_API | RAN Analytics Information | - -## 7.2 SDL API Procedures - -### 7.2.1 Void - -### 7.2.2 Void - -### 7.2.3 SDL Subscribe Information procedure - -#### 7.2.3.1 General - -This procedure is used by the xApp to subscribe to the SDL for the information that it is interested to obtain. - -#### 7.2.3.2 Successful Operation - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -``` - -``` - -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "Near-RT RIC Platform" as near -participant "xApp" as app -app -> near: SUBSCRIBE INFORMATION REQUEST -near -> app: SUBSCRIBE INFORMATION RESPONSE -@enduml - -``` - -![Sequence diagram illustrating the successful operation of the Subscribe Information procedure. The diagram shows two lifelines: 'Near-RT RIC Platform' (top and bottom) and 'xApp' (top and bottom). The sequence of messages is: 1. xApp (top) sends a 'SUBSCRIBE INFORMATION REQUEST' message to Near-RT RIC Platform (top). 2. Near-RT RIC Platform (top) sends a 'SUBSCRIBE INFORMATION RESPONSE' message to xApp (top).](fcc757566216206ceddbd6c775e8db02_img.jpg) - -``` - -sequenceDiagram - participant xApp as xApp - participant Near-RT RIC Platform as Near-RT RIC Platform - Note left of xApp: xApp initiates the procedure - xApp->>Near-RT RIC Platform: SUBSCRIBE INFORMATION REQUEST - Near-RT RIC Platform-->>xApp: SUBSCRIBE INFORMATION RESPONSE - -``` - -Sequence diagram illustrating the successful operation of the Subscribe Information procedure. The diagram shows two lifelines: 'Near-RT RIC Platform' (top and bottom) and 'xApp' (top and bottom). The sequence of messages is: 1. xApp (top) sends a 'SUBSCRIBE INFORMATION REQUEST' message to Near-RT RIC Platform (top). 2. Near-RT RIC Platform (top) sends a 'SUBSCRIBE INFORMATION RESPONSE' message to xApp (top). - -**Figure 7.2.3.2-1: Subscribe Information procedure, successful operation** - -The xApp initiates the procedure by sending the SUBSCRIBE INFORMATION REQUEST message. - -The message shall include: - -- the *SDL Data Type ID* IE, which indicates the requested SDL data type; -- the *Delivery Method* IE, which indicates the method of data delivery; -- the *Notification Destination* IE, which specifies the endpoint to receive associated notification(s); -- the *Notification Criteria* IE, which specifies the timing related to the notification(s). It shall include: - - the *Notification Method* IE, which indicates the notification(s) are periodic or event triggered; - - the *Notification Period* IE if the *Notification Method* IE is set to "PERIODIC", which indicates the time interval between periodic notifications; - - the *Trigger Event Definition* IE if the *Notification Method* IE is set to "EVENT\_TRIGGERED", which contains the description of the triggering event; - -The message may include: - -- the *SDL Data Description* IE, which contains the detailed descriptions for the requested data. - -When the Near-RT RIC platform receives the request, it searches the local database or data sources for the requested information. - -If the Near-RT RIC platform successfully processes the request, it shall prepare necessary resource for the subscription, assign a subscription ID, and responds to the xApp with the SUBSCRIBE INFORMATION RESPONSE message. - -#### 7.2.3.3 Unsuccessful Operation - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "Near-RT RIC Platform" as near -participant "xApp" as app -app -> near: SUBSCRIBE INFORMATION REQUEST -near -> app: SUBSCRIBE INFORMATION FAILURE -@enduml - -``` - -![Sequence diagram for Figure 7.2.3.3-1: Subscribe Information procedure, unsuccessful operation. It shows two lifelines: Near-RT RIC Platform and xApp. The xApp sends a SUBSCRIBE INFORMATION REQUEST to the Near-RT RIC Platform. The Near-RT RIC Platform responds with a SUBSCRIBE INFORMATION FAILURE message back to the xApp.](935075de5250cfe8aa0fb9d65d63dde5_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC Platform - participant xApp - xApp->>Near-RT RIC Platform: SUBSCRIBE INFORMATION REQUEST - Near-RT RIC Platform-->>xApp: SUBSCRIBE INFORMATION FAILURE - -``` - -Sequence diagram for Figure 7.2.3.3-1: Subscribe Information procedure, unsuccessful operation. It shows two lifelines: Near-RT RIC Platform and xApp. The xApp sends a SUBSCRIBE INFORMATION REQUEST to the Near-RT RIC Platform. The Near-RT RIC Platform responds with a SUBSCRIBE INFORMATION FAILURE message back to the xApp. - -**Figure 7.2.3.3-1: Subscribe Information procedure, unsuccessful operation** - -If the Near-RT RIC platform can not accept the request it shall respond with the SUBSCRIBE INFORMATION FAILURE message and the proper cause. If the message contains *Time To Wait* IE the xApp shall wait at least the indicated time before reinitiating the request to the Near-RT RIC platform. - -#### 7.2.3.4 Abnormal Conditions - -If the Near-RT RIC platform receives a SUBSCRIBE INFORMATION REQUEST message containing *Information Type* IE that is not supported by the Near-RT RIC platform, or the optional filter definition is invalid, the Near-RT RIC platform shall send the SUBSCRIBE INFORMATION FAILURE message to the xApp with an appropriate cause value. - -### 7.2.4 SDL Information Push procedure - -#### 7.2.4.1 General - -This procedure is used by the Near-RT RIC platform to send the latest information from the Near-RT RIC platform to the xApp based on what the xApp has subscribed when the *Delivery Method* IE set to "PUSH\_DELTA" or "PUSH\_FULL" in the subscribe information request. - -#### 7.2.4.2 Successful Operation - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "Near-RT RIC Platform" as near -participant "xApp" as app -near -> app: INFORMATION PUSH -@enduml - -``` - -![Sequence diagram for Figure 7.2.4.2-1: Information Push procedure, successful operation. It shows two lifelines: Near-RT RIC Platform and xApp. The Near-RT RIC Platform sends an INFORMATION PUSH message to the xApp.](a02b188a5fd52c99f84255322873bf29_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC Platform - participant xApp - Near-RT RIC Platform->>xApp: INFORMATION PUSH - -``` - -Sequence diagram for Figure 7.2.4.2-1: Information Push procedure, successful operation. It shows two lifelines: Near-RT RIC Platform and xApp. The Near-RT RIC Platform sends an INFORMATION PUSH message to the xApp. - -**Figure 7.2.4.2-1: Information Push procedure, successful operation** - -The Near-RT RIC initiates the procedure by sending the INFORMATION PUSH message. - -The message shall include: - -- the *Subscription ID* IE, which indicates the associated subscription; -- the *SDL Data Type ID* IE, which indicates the SDL data Type carried in the message; -- the *SDL Data Block* IE, which carries the SDL data and shall include: - - the *SDL Data Unit* IE, which contains a single item of the SDL data; - -- the *Modification Type* IE, which indicates type of change (added, modified, removed, etc.) associated with the SDL data in the *SDL Data Unit* IE. - -#### 7.2.4.3 Unsuccessful Operation - -Not applicable. - -#### 7.2.4.4 Abnormal Conditions - -Not applicable. - -### 7.2.5 SDL Information Update Notify procedure - -#### 7.2.5.1 General - -This procedure is used by the Near-RT RIC platform to notify the xApp that certain information subscribed by the xApp has been updated and available to be fetched. The procedure is used when the Delivery Method IE set to "UPDATE\_NOTIFY" in the subscribe information request. - -#### 7.2.5.2 Successful Operation - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "Near-RT RIC Platform" as near -participant "xApp" as app -near -> app: INFORMATION UPDATE NOTIFY -@enduml -``` - -![UML sequence diagram showing the successful operation of the Information Update Notify procedure. Two lifelines are shown: 'Near-RT RIC Platform' and 'xApp'. A message labeled 'INFORMATION UPDATE NOTIFY' is sent from the 'Near-RT RIC Platform' lifeline to the 'xApp' lifeline.](eae05333c9188c830bd0ebe58c50453a_img.jpg) - -``` -sequenceDiagram - participant Near-RT RIC Platform - participant xApp - Note left of Near-RT RIC Platform: Near-RT RIC Platform - Note right of xApp: xApp - Near-RT RIC Platform->>xApp: INFORMATION UPDATE NOTIFY -``` - -UML sequence diagram showing the successful operation of the Information Update Notify procedure. Two lifelines are shown: 'Near-RT RIC Platform' and 'xApp'. A message labeled 'INFORMATION UPDATE NOTIFY' is sent from the 'Near-RT RIC Platform' lifeline to the 'xApp' lifeline. - -**Figure 7.2.5.2-1: Information Update Notify procedure, successful operation** - -The Near-RT RIC platform initiates the procedure by sending the INFORMATION UPDATE NOTIFY message. - -The message shall include: - -- the *Subscription ID* IE, which indicates the associated subscription; -- the *SDL Data Type ID* IE, which indicates the SDL data Type carried in the message; -- the *SDL Data Block* IE, which carries the SDL data and shall include: - - the *SDL Update Notify Unit* IE, which contains a single item of the SDL data; - - the *Modification Type* IE, which indicates type of change (added, modified, removed, etc.) associated with the SDL data in the *SDL Update Notify Unit* IE. - -Once the xApp has received the message, xApp can determine to retrieve the updated information through the Information Fetch procedure described in clause 7.2.6. - -#### 7.2.5.3 Unsuccessful Operation - -Not applicable. - -#### 7.2.5.4 Abnormal Conditions - -Not applicable. - -### 7.2.6 SDL Information Fetch procedure - -#### 7.2.6.1 General - -This procedure is used by the xApp to fetch certain information from the SDL. - -#### 7.2.6.2 Successful Operation - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "Near-RT RIC Platform" as near -participant "xApp" as app -app -> near: INFORMATION FETCH REQUEST -near -> app: INFORMATION FETCH RESPONSE -@enduml -``` - -![Sequence diagram showing the successful operation of the SDL Information Fetch procedure. The xApp sends an INFORMATION FETCH REQUEST to the Near-RT RIC Platform, which responds with an INFORMATION FETCH RESPONSE.](314da473d582c4327e1e3d56fcba19dd_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp initiates the procedure - xApp->>Near-RT RIC Platform: INFORMATION FETCH REQUEST - Note right of Near-RT RIC Platform: Near-RT RIC Platform searches for data - Near-RT RIC Platform-->>xApp: INFORMATION FETCH RESPONSE - Note right of xApp: xApp receives the response - -``` - -Sequence diagram showing the successful operation of the SDL Information Fetch procedure. The xApp sends an INFORMATION FETCH REQUEST to the Near-RT RIC Platform, which responds with an INFORMATION FETCH RESPONSE. - -**Figure 7.2.6.2-1: SDL Information Fetch procedure, successful operation** - -The xApp initiates the procedure by sending the INFORMATION FETCH REQUEST message. - -The message shall include: - -- the *SDL Data Type ID* IE, which indicates the requested SDL data type. - -The message may include: - -- the *SDL Data Description* IE, which contains the detailed descriptions for the requested data. - -When the Near-RT RIC platform receives the request, it searches the local database or data sources for the fetched information. - -If the SDL contains matching data for the fetch request, the Near-RT RIC platform sends the requested data to the xApp in the INFORMATION FETCH RESPONSE message. - -#### 7.2.6.3 Unsuccessful Operation - -If the data corresponding to a fetch request is not found, the Near-RT RIC platform sends an INFORMATION FETCH FAILURE message with an appropriate failure cause. - -#### 7.2.6.4 Abnormal Conditions - -If the Near-RT RIC platform receives a INFORMATION FETCH REQUEST message containing *SDL Data Type ID* IE that is not supported by the Near-RT RIC platform, or the optional *SDL Data Description* IE definition is invalid, the Near-RT RIC platform shall send the INFORMATION FETCH FAILURE message to the xApp with an appropriate cause value. - -### 7.2.7 Store Data procedure - -### 7.2.8 Modify Data procedure - -### 7.2.9 Xapp Shared Data Fetch procedure - -#### 7.2.9.1 General - -This procedure is used by the Near-RT RIC platform or the data consumer xApp to fetch specific types of data shared by the data producer xApp. - -#### 7.2.9.2 Successful Operation - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "Data consumer \n(Near-RT RIC platform or xApp)" as consumer -participant "Data producer xApp" as producerxApp -consumer -> producerxApp: XAPP SHARED DATA FETCH REQUEST -producerxApp -> consumer: XAPP SHARED DATA FETCH RESPONSE -@enduml -``` - -![Sequence diagram for xApp Shared Data Fetch procedure, successful operation. It shows two lifelines: 'Data consumer (Near-RT RIC platform or xApp)' and 'Data producer xApp'. The consumer sends a 'XAPP SHARED DATA FETCH REQUEST' message to the producer, and the producer responds with a 'XAPP SHARED DATA FETCH RESPONSE' message.](8d1bb05debbaef0f72751449b2b55172_img.jpg) - -``` - -sequenceDiagram - participant consumer as Data consumer -(Near-RT RIC platform or xApp) - participant producerxApp as Data producer xApp - consumer->>producerxApp: XAPP SHARED DATA FETCH REQUEST - producerxApp-->>consumer: XAPP SHARED DATA FETCH RESPONSE - -``` - -Sequence diagram for xApp Shared Data Fetch procedure, successful operation. It shows two lifelines: 'Data consumer (Near-RT RIC platform or xApp)' and 'Data producer xApp'. The consumer sends a 'XAPP SHARED DATA FETCH REQUEST' message to the producer, and the producer responds with a 'XAPP SHARED DATA FETCH RESPONSE' message. - -**Figure 7.2.9.2-1: xApp Shared Data Fetch procedure, successful operation** - -The data consumer initiates the procedure by sending the XAPP SHARED DATA FETCH REQUEST message. - -The message shall include: - -- the *SDL Data Type ID* IE, which indicates the requested SDL data type. - -The message may include: - -- the *SDL Data Description* IE, which contains the detailed descriptions for the requested data. - -Upon receiving the message, the data producer xApp shall check the authorization for the data consumer to access the requested data. If the requested data is available at the producer xApp, the producer xApp shall send the requested data to the data consumer in the XAPP SHARED DATA FETCH RESPONSE message. - -#### 7.2.9.3 Unsuccessful Operation - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -``` - -``` - -skinparam lifelineStrategy solid -participant "Data consumer \n(Near-RT RIC platform or xApp)" as consumer -participant "Data producer xApp" as producerxApp -consumer -> producerxApp: XAPP SHARED DATA FETCH REQUEST -producerxApp -> consumer: XAPP SHARED DATA FETCH FAILURE -@enduml - -``` - -![Sequence diagram for Figure 7.2.9.3-1: xApp Shared Data Fetch procedure, unsuccessful operation. It shows a Data consumer (Near-RT RIC platform or xApp) sending an XAPP SHARED DATA FETCH REQUEST to a Data producer xApp, which responds with an XAPP SHARED DATA FETCH FAILURE.](5e9af8986a5845504f251d3079da8078_img.jpg) - -``` - -sequenceDiagram - participant DC as Data consumer (Near-RT RIC platform or xApp) - participant DP as Data producer xApp - Note left of DC: Data consumer - DC->>DP: XAPP SHARED DATA FETCH REQUEST - Note right of DP: Data producer xApp - DP-->>DC: XAPP SHARED DATA FETCH FAILURE - Note left of DC: Data consumer (Near-RT RIC platform or xApp) - Note right of DP: Data producer xApp - -``` - -Sequence diagram for Figure 7.2.9.3-1: xApp Shared Data Fetch procedure, unsuccessful operation. It shows a Data consumer (Near-RT RIC platform or xApp) sending an XAPP SHARED DATA FETCH REQUEST to a Data producer xApp, which responds with an XAPP SHARED DATA FETCH FAILURE. - -**Figure 7.2.9.3-1: xApp Shared Data Fetch procedure, unsuccessful operation** - -If the data consumer is not authorized, or the requested data specified in the XAPP SHARED DATA FETCH REQUEST is unavailable, the producer xApp shall send an XAPP SHARED DATA FETCH FAILURE message with appropriate cause. - -#### 7.2.9.4 Abnormal Conditions - -Not applicable. - -### 7.2.10 Xapp Shared Data Subscribe procedure - -#### 7.2.10.1 General - -This procedure is used by the Near-RT RIC platform or the data consumer xApp to subscribe to specific types of data shared by the data producer xApp. - -#### 7.2.10.2 Successful Operation - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "Data consumer \n(Near-RT RIC platform or xApp)" as consumer -participant "Data producer xApp" as producerxApp -consumer -> producerxApp: XAPP SHARED DATA SUBSCRIPTION REQUEST -producerxApp -> consumer: XAPP SHARED DATA SUBSCRIPTION RESPONSE -@enduml - -``` - -![Sequence diagram for Figure 7.2.10.2-1: xApp Shared Data Subscribe procedure, successful operation. It shows a Data consumer (Near-RT RIC platform or xApp) sending an XAPP SHARED DATA SUBSCRIPTION REQUEST to a Data producer xApp, which responds with an XAPP SHARED DATA SUBSCRIPTION RESPONSE.](c425a7b76be3f887bb251606c2a7ce9a_img.jpg) - -``` - -sequenceDiagram - participant DC as Data consumer (Near-RT RIC platform or xApp) - participant DP as Data producer xApp - Note left of DC: Data consumer - DC->>DP: XAPP SHARED DATA SUBSCRIPTION REQUEST - Note right of DP: Data producer xApp - DP-->>DC: XAPP SHARED DATA SUBSCRIPTION RESPONSE - Note left of DC: Data consumer (Near-RT RIC platform or xApp) - Note right of DP: Data producer xApp - -``` - -Sequence diagram for Figure 7.2.10.2-1: xApp Shared Data Subscribe procedure, successful operation. It shows a Data consumer (Near-RT RIC platform or xApp) sending an XAPP SHARED DATA SUBSCRIPTION REQUEST to a Data producer xApp, which responds with an XAPP SHARED DATA SUBSCRIPTION RESPONSE. - -**Figure 7.2.10.2-1: xApp Shared Data Subscribe procedure, successful operation** - -The data consumer initiates the procedure by sending the XAPP SHARED DATA SUBSCRIPTION REQUEST message. - -The message shall include: - -- the *SDL Data Type ID* IE, which indicates the requested SDL data type; -- the *Delivery Method* IE, which indicates the method of data delivery; -- the *Notification Destination* IE, which specifies the endpoint to receive associated notification(s); -- the *Notification Criteria* IE, which specifies the timing related to the notification(s). It shall include: - - the *Notification Method* IE, which indicates the notification(s) are periodic or event triggered; - - the *Notification Period* IE if the *Notification Method* IE is set to "PERIODIC", which indicates the time interval between periodic notifications; - - the *Trigger Event Definition* IE if the *Notification Method* IE is set to "EVENT\_TRIGGERED", which contains the description of the triggering event; - -The message may include: - -- the *SDL Data Description* IE, which contains the detailed descriptions for the requested data. - -Upon receiving the message, the data producer xApp shall check the authorization for the data consumer to subscribe to the requested data. If the requested subscription can be fulfilled, the producer xApp shall prepare necessary resource for the subscription, assign a subscription ID, and send the XAPP SHARED DATA SUBSCRIPTION RESPONSE message to the data consumer. - -The message shall include: - -- the *Subscription ID* IE, which contains the subscription ID. - -#### 7.2.10.3 Unsuccessful Operation - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "Data consumer \n(Near-RT RIC platform or xApp)" as consumer -participant "Data producer xApp" as producerxApp -consumer -> producerxApp: XAPP SHARED DATA SUBSCRIPTION REQUEST -producerxApp -> consumer: XAPP SHARED DATA SUBSCRIPTION FAILURE -@enduml -``` - -![Sequence diagram showing an unsuccessful subscription operation. A Data consumer (Near-RT RIC platform or xApp) sends an XAPP SHARED DATA SUBSCRIPTION REQUEST to a Data producer xApp. The Data producer xApp responds with an XAPP SHARED DATA SUBSCRIPTION FAILURE message.](cc468dcda006ef315536400517a09ad3_img.jpg) - -``` -sequenceDiagram - participant Data consumer (Near-RT RIC platform or xApp) - participant Data producer xApp - Note left of Data consumer: Data consumer - Note right of Data producer: Data producer xApp - Data consumer->>Data producer xApp: XAPP SHARED DATA SUBSCRIPTION REQUEST - Note right of Data producer: Data producer xApp - Note left of Data consumer: Data consumer (Near-RT RIC platform or xApp) - Data producer xApp-->>Data consumer: XAPP SHARED DATA SUBSCRIPTION FAILURE -``` - -Sequence diagram showing an unsuccessful subscription operation. A Data consumer (Near-RT RIC platform or xApp) sends an XAPP SHARED DATA SUBSCRIPTION REQUEST to a Data producer xApp. The Data producer xApp responds with an XAPP SHARED DATA SUBSCRIPTION FAILURE message. - -**Figure 7.2.10.3-1: xApp Shared Data Subscribe procedure, unsuccessful operation** - -If the data consumer is not authorized, or the requested subscription cannot be fulfilled, the producer xApp shall send the XAPP SHARED DATA FETCH FAILURE message with appropriate cause. - -#### 7.2.10.4 Abnormal Conditions - -Not Applicable. - -### 7.2.11 Xapp Shared Data Subscription Delete procedure - -#### 7.2.11.1 General - -This procedure is used by the Near-RT RIC platform or the data consumer xApp to delete an existing xApp shared data subscription toward the data producer xApp. - -#### 7.2.11.2 Successful Operation - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "Data consumer \n(Near-RT RIC platform or xApp)" as consumer -participant "Data producer xApp" as producerxApp -consumer -> producerxApp: XAPP SHARED DATA SUBSCRIPTION DELETE REQUEST -producerxApp -> consumer: XAPP SHARED DATA SUBSCRIPTION DELETE RESPONSE -@enduml -``` - -![Sequence diagram for successful operation. It shows two lifelines: 'Data consumer (Near-RT RIC platform or xApp)' and 'Data producer xApp'. The consumer sends a 'XAPP SHARED DATA SUBSCRIPTION DELETE REQUEST' message to the producer. The producer responds with a 'XAPP SHARED DATA SUBSCRIPTION DELETE RESPONSE' message. The lifelines are shown at the top and bottom of the diagram, with the messages occurring between them.](1399c76ef88f22b70d05ed3f781d3c48_img.jpg) - -Sequence diagram for successful operation. It shows two lifelines: 'Data consumer (Near-RT RIC platform or xApp)' and 'Data producer xApp'. The consumer sends a 'XAPP SHARED DATA SUBSCRIPTION DELETE REQUEST' message to the producer. The producer responds with a 'XAPP SHARED DATA SUBSCRIPTION DELETE RESPONSE' message. The lifelines are shown at the top and bottom of the diagram, with the messages occurring between them. - -**Figure 7.2.11.2-1: xApp Shared Data Subscription Delete procedure, successful operation** - -The data consumer initiates the procedure by sending the XAPP SHARED DATA SUBSCRIPTION DELETE message. - -The message shall include: - -- the *Subscription ID* IE, which indicates the subscription to delete; - -Upon receiving the message, the data producer xApp shall check the authorization for the data consumer. If the subscription is present, the data producer xApp shall release the resource for the subscription, and send the XAPP SHARED DATA SUBSCRIPTION DELETE RESPONSE message to the data consumer. - -#### 7.2.11.3 Unsuccessful Operation - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "Data consumer \n(Near-RT RIC platform or xApp)" as consumer -participant "Data producer xApp" as producerxApp -consumer -> producerxApp: XAPP SHARED DATA SUBSCRIPTION DELETE REQUEST -producerxApp -> consumer: XAPP SHARED DATA SUBSCRIPTION DELETE FAILURE -@enduml -``` - -![Sequence diagram for xApp Shared Data Subscription Delete procedure, unsuccessful operation. It shows a Data consumer (Near-RT RIC platform or xApp) sending a XAPP SHARED DATA SUBSCRIPTION DELETE REQUEST to a Data producer xApp, which responds with a XAPP SHARED DATA SUBSCRIPTION DELETE FAILURE.](c06fd7dbef68a8b788158f2081d9d734_img.jpg) - -``` - -sequenceDiagram - participant DC as Data consumer -(Near-RT RIC platform or xApp) - participant DP as Data producer xApp - DC->>DP: XAPP SHARED DATA SUBSCRIPTION DELETE REQUEST - DP-->>DC: XAPP SHARED DATA SUBSCRIPTION DELETE FAILURE - -``` - -Sequence diagram for xApp Shared Data Subscription Delete procedure, unsuccessful operation. It shows a Data consumer (Near-RT RIC platform or xApp) sending a XAPP SHARED DATA SUBSCRIPTION DELETE REQUEST to a Data producer xApp, which responds with a XAPP SHARED DATA SUBSCRIPTION DELETE FAILURE. - -**Figure 7.2.11.3-1: xApp Shared Data Subscription Delete procedure, unsuccessful operation** - -If the data consumer is not authorized, or the subscription indicated by the *Subscription ID* IE is not present, the data producer xApp shall send the XAPP SHARED DATA SUBSCRIPTION DELETE FAILURE message with appropriate cause. - -#### 7.2.11.4 Abnormal Conditions - -Not applicable. - -### 7.2.12 Xapp Shared Data Push procedure - -#### 7.2.12.1 General - -This procedure is used by the data producer xApp to push the subscribed SDL data to the data consumer according to an existing subscription. The procedure is used when the *Delivery Method* IE set to "PUSH\_DELTA" or "PUSH\_FULL" in the xApp shared data subscription request. - -#### 7.2.12.2 Successful Operation - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "Data consumer \n(Near-RT RIC platform or xApp)" as consumer -participant "Data producer xApp" as producerxApp -producerxApp -> consumer: XAPP SHARED DATA PUSH -@enduml - -``` - -![Sequence diagram for xApp Shared Data Push procedure, successful operation. It shows a Data producer xApp sending a XAPP SHARED DATA PUSH message to a Data consumer (Near-RT RIC platform or xApp).](1274805226c5a1f8b875aea0296b9f0f_img.jpg) - -``` - -sequenceDiagram - participant DC as Data consumer -(Near-RT RIC platform or xApp) - participant DP as Data producer xApp - DP->>DC: XAPP SHARED DATA PUSH - -``` - -Sequence diagram for xApp Shared Data Push procedure, successful operation. It shows a Data producer xApp sending a XAPP SHARED DATA PUSH message to a Data consumer (Near-RT RIC platform or xApp). - -**Figure 7.2.12.2-1: xApp Shared Data Push procedure, successful operation** - -The data producer xApp initiates the procedure by sending the XAPP SHARED DATA PUSH message. - -The message shall include: - -- the *Subscription ID* IE, which indicates the associated subscription; -- the *SDL Data Type ID* IE, which indicates the SDL data Type carried in the message; - -- the *SDL Data Block IE*, which carries the SDL data and shall include: - - the *SDL Data Unit IE*, which contains a single item of the SDL data; - - the *Modification Type IE*, which indicates type of change (added, modified, removed, etc.) associated with the SDL data in the *SDL Data Unit IE*. - -#### 7.2.12.3 Unsuccessful Operation - -Not applicable. - -#### 7.2.12.4 Abnormal Conditions - -Not applicable. - -## 7.3 Elements for SDL API Communication - -### 7.3.1 General - -Sub clauses 7.3.2 and 7.3.3 describe the structure of the messages and information elements required for the SDL API in tabular format. - -### 7.3.2 Message Functional Definition and Content - -7.3.2.1 Void - -7.3.2.2 Void - -7.3.2.3 Void - -7.3.2.4 Void - -7.3.2.5 Void - -#### 7.3.2.6 SUBSCRIBE INFORMATION REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to subscribe to the interested information. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------| -| Message Type | M | | 7.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| SDL Data Type ID | M | | 7.3.3.21 | | -| Delivery Method | M | | 7.3.3.4 | | -| SDL Data Description | O | | 7.3.3.22 | This IE may be absent, if a default SDL Data Description is available for the SDL Type ID and used in this request. | -| Notification Destination | M | | 10.1.9 | | -| Notification Criteria | M | | 7.3.3.24 | | - -#### 7.3.2.7 SUBSCRIBE INFORMATION RESPONSE - -This message is sent by the Near-RT RIC platform after successful acceptance of an xApp's request to subscribe to the information in the SDL. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 7.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Subscription ID | M | | 7.3.3.26 | | - -#### 7.3.2.8 SUBSCRIBE INFORMATION FAILURE - -This message is sent by the Near-RT RIC platform after failure to accept an xApp's request to subscribe to information in the SDL. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------------|----------|-------|-----------------------|-----------------------------------------| -| Message Type | M | | 7.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Subscription Reject Cause | M | | 7.3.3.9 | | -| Time to Wait | O | | 7.3.3.13 | If absent, no time to wait is required. | - -#### 7.3.2.9 INFORMATION PUSH - -This message is sent by the Near-RT RIC platform to an xApp containing the information subscribed by the xApp. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------------|----------|---------------------------------------|-----------------------|--------------------------------------------------------------------------------------------------| -| Message Type | M | | 7.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Subscription ID | M | | 7.3.3.26 | | -| SDL Data Type ID | M | | 7.3.3.21 | | -| SDL Data Block | | 0..1 | | | -| > SDL Data Block Item | | 1..<
maxnoof
SDLData
Units > | | | -| >> Modification Type | C | | 7.3.3.10 | Shall be present when the Delivery Method IE in the subscription request is set to "PUSH_DELTA". | -| >> SDL Data Unit | M | | 7.3.3.23 | | - -| Range bound | Explanation | -|----------------------------|----------------------------------------------------------------------------------------------| -| maxnoofSDLDataUnits | Maximum number of SDL Data Units that can be carried in an SDL Data Block. Value is 1048576. | - -#### 7.3.2.10 INFORMATION UPDATE NOTIFY - -This message is sent by the Near-RT RIC platform to inform an xApp that some of the information subscribed by the xApp has been updated. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------------------------|----------|-----------------------------------------------|-----------------------|-----------------------| -| Message Type | M | | 7.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Subscription ID | M | | 7.3.3.26 | | -| SDL Data Type ID | M | | 7.3.3.21 | | -| SDL Update Notify Block | | 0..1 | | | -| > SDL Update Notify Block Item | | 1..<
maxnoof
SDLUpdateNotify
Units > | | | -| >> Modification Type | M | | 7.3.3.10 | | -| >> SDL Update Notify Unit | M | | 7.3.3.27 | | - -| Range bound | Explanation | -|------------------------------------|----------------------------------------------------------------------------------------------------------------| -| maxnoofSDLUpdateNotifyUnits | Maximum number of SDL Update Notify Units that can be carried in an SDL Update Notify Block. Value is 1048576. | - -#### 7.3.2.11 INFORMATION FETCH REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to request certain information subscribed by the xApp. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------| -| Message Type | M | | 7.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| SDL Data Type ID | M | | 7.3.3.21 | | -| SDL Data Description | O | | 7.3.3.22 | This IE may be absent when a default definition of it exists and is used in the request. | - -#### 7.3.2.12 INFORMATION FETCH RESPONSE - -This message is sent by the Near-RT RIC platform to an xApp containing the information requested by the xApp. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------------|----------|-----------------|-----------------------|-----------------------| -| Message Type | M | | 7.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| SDL Data Type ID | M | | 7.3.3.21 | | -| SDL Data Block | | 0..1 | | | -| > SDL Data Block Item | | 1..<
maxnoof | | | - -| | | | | | -|------------------|---|---------------------------|----------|--| -| | | SDLData Units > | | | -| >> SDL Data Unit | M | | 7.3.3.23 | | - -#### 7.3.2.13 INFORMATION FETCH FAILURE - -This message is sent by the Near-RT RIC platform to an xApp if the Information fetch request failed. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 7.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Fetch Failure Cause | M | | 7.3.3.18 | Cause for failure | - -#### 7.3.2.14 STORE DATA REQUEST - -#### 7.3.2.15 STORE DATA RESPONSE - -#### 7.3.2.16 STORE DATA FAILURE - -#### 7.3.2.17 MODIFY DATA REQUEST - -#### 7.3.2.18 MODIFY DATA RESPONSE - -#### 7.3.2.19 MODIFY DATA FAILURE - -#### 7.3.2.20 XAPP SHARED DATA FETCH REQUEST - -This message is sent by the Near-RT RIC platform or a data consumer xApp to fetch data shared by the data producer xApp. - -Direction: Near-RT RIC platform / Data consumer xApp -> Data producer xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------| -| Message Type | M | | 7.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| SDL Data Type ID | M | | 7.3.3.21 | | -| SDL Data Description | O | | 7.3.3.22 | This IE may be absent when a default definition of it exists and is used in the request. | - -#### 7.3.2.21 XAPP SHARED DATA FETCH RESPONSE - -This message is sent by the data producer xApp containing the fetched data requested by the Near-RT RIC platform or the data consumer xApp. - -Direction: Data producer xApp -> Near-RT RIC platform / Data consumer xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------------|----------|--------------------------------------|-----------------------|-----------------------| -| Message Type | M | | 7.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| SDL Data Type ID | M | | 7.3.3.21 | | -| SDL Data Block | | 0..1 | | | -| > SDL Data Block Item | | 1..<
maxnoof
SDLData
Units> | | | -| >> SDL Data Unit | M | | 7.3.3.23 | | - -| Range bound | Explanation | -|----------------------------|----------------------------------------------------------------------------------------------------| -| maxnoofSDLDataUnits | Maximum number of SDL Data Block Units that can be carried in an SDL Data Block. Value is 1048576. | - -#### 7.3.2.22 XAPP SHARED DATA FETCH FAILURE - -This message is sent by the data producer xApp to the Near-RT RIC platform or the data consumer xApp if the xApp shared data fetch request fails. - -Direction: Data producer xApp -> Near-RT RIC platform / Data consumer xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|--------------------------| -| Message Type | M | | 7.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Procedure Transaction ID | -| Fetch Failure Cause | M | | 7.3.3.18 | Cause for failure | - -#### 7.3.2.23 XAPP SHARED DATA SUBSCRIPTION REQUEST - -This message is sent by the Near-RT RIC platform or a data consumer xApp to subscribe to data shared by the data producer xApp. - -Direction: Near-RT RIC platform / Data consumer xApp -> Data producer xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------| -| Message Type | M | | 7.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| SDL Data Type ID | M | | 7.3.3.21 | | -| SDL Data Description | O | | 7.3.3.22 | This IE may be absent, if a default SDL Data Description is available for the SDL Type ID and used in this request. | -| Delivery Method | M | | 7.3.3.4 | | -| Notification Destination | M | | 10.1.9 | | -| Notification Criteria | M | | 7.3.3.24 | | - -#### 7.3.2.24 XAPP SHARED DATA SUBSCRIPTION RESPONSE - -This message is sent by the data producer xApp to indicate success of the subscription request. - -Direction: Data producer xApp -> Near-RT RIC platform / Data consumer xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 7.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Subscription ID | M | | 7.3.3.26 | | - -#### 7.3.2.25 XAPP SHARED DATA SUBSCRIPTION FAILURE - -This message is sent by the data producer xApp to indicate failure of the subscription request. - -Direction: Data producer xApp -> Near-RT RIC platform / Data consumer xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 7.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Subscription Reject Cause | M | | 7.3.3.9 | | - -#### 7.3.2.26 XAPP SHARED DATA PUSH - -This message is sent by the data producer xApp to push its shared data to the subscriber (data consumer xApp or the Near-RT RIC platform). - -Direction: Data producer xApp -> Near-RT RIC platform / Data consumer xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------------|----------|---------------------------------------|-----------------------|---------------------------------------------------------------------------------------------------------| -| Message Type | M | | 7.3.3.1 | | -| Subscription ID | M | | 7.3.3.26 | The same Subscription ID as in the subscription response. | -| SDL Data Type ID | M | | 7.3.3.21 | | -| SDL Data Block | | 0..1 | | | -| > SDL Data Block Item | | 1..<
maxnoof
SDLData
Units > | | | -| >> Modification Type | C | | 7.3.3.10 | Shall be present when the Delivery Method IE in the subscription request is set to "PUSH_DELTA". | -| >> SDL Data Unit | M | | 7.3.3.23 | | - -| Range bound | Explanation | -|----------------------------|----------------------------------------------------------------------------------------------| -| maxnoofSDLDataUnits | Maximum number of SDL Data Units that can be carried in an SDL Data Block. Value is 1048576. | - -#### 7.3.2.27 XAPP SHARED DATA SUBSCRIPTION DELETE REQUEST - -This message is sent by the Near-RT RIC platform or a data consumer xApp to delete an existing subscription to the xApp shared data. - -Direction: Near-RT RIC platform / Data consumer xApp -> Data producer xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 7.3.3.1 | | - -| | | | | | -|--------------------------|---|--|----------|-----------------------------------------------------------| -| Procedure Transaction ID | M | | 10.1.1 | | -| Subscription ID | M | | 7.3.3.26 | The same Subscription ID as in the subscription response. | - -#### 7.3.2.28 XAPP SHARED DATA SUBSCRIPTION DELETE RESPONSE - -This message is sent by the data producer xApp to indicate successful deletion of an existing subscription to the xApp shared data. - -Direction: Data producer xApp -> Near-RT RIC platform / Data consumer xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 7.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | - -#### 7.3.2.29 XAPP SHARED DATA SUBSCRIPTION DELETE FAILURE - -This message is sent by the data producer xApp to indicate failure of the subscription request. - -Direction: Data producer xApp -> Near-RT RIC platform / Data consumer xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 7.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Subscription Reject Cause | M | | 7.3.3.9 | | - -### 7.3.3 Information Element Definitions - -#### 7.3.3.1 Message Type - -The Message Type IE identifies the message being sent. It is mandatory for all messages. - -| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | -|------------------|----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------| -| Message Type | | | | | -| >Procedure Type | M | | CHOICE (SDL Subscription Information, SDL Information Push, SDL Information Update Notify, SDL Information Fetch, Xapp Shared Data Fetch, Xapp Shared Data Subscribe, Xapp Shared Data Subscription Delete, Xapp Shared Data Push, ...) | | -| >Type of Message | M | | CHOICE (Request, Response, Failure, ...) | Refer to Table 7.1.2-3 for applicable choices for each procedure type | - -#### 7.3.3.2 Void - -#### 7.3.3.3 Void - -#### 7.3.3.4 Delivery Method - -The Delivery Method IE indicates the delivery method in which the xApp wants the information to be delivered. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-----------------|----------|-------|--------------------------------------------------------------|-----------------------| -| Delivery Method | M | | ENUMERATED
(UPDATE_NOTIFY, PUSH_DELTA,
PUSH_FULL, ...) | | - -**Table 7.3.3.4-1: Meaning of Delivery Method** - -| Value | Description | -|---------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| UPDATE_NOTIFY | Notifies only the summary of change in the data specified by the SDL Data Description IE. It uses the SDL Information Update Notify procedure for the notification. | -| PUSH_DELTA | Notifies the data that has changed since the last notification associated with the same subscription, from the data specified by the SDL Data Description IE. It uses the SDL Information Push procedure for the notification. | -| PUSH_FULL | Notifies all the data specified by the SDL Data Description IE. It uses the SDL Information Push procedure for the notification. | - -#### 7.3.3.5 Void - -#### 7.3.3.6 Void - -#### 7.3.3.7 Void - -#### 7.3.3.8 Void - -#### 7.3.3.9 Subscription Reject Cause - -The Subscription Reject Cause IE indicates the reason the SDL rejected the subscription. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------------|----------|-------|-----------------------------------------------------------------------------------------------------|-----------------------| -| Subscription Reject Cause | M | | ENUMERATED (SDL reached capacity, Information type not supported, Invalid filter, Unspecified, ...) | | - -#### 7.3.3.10 Modification Type - -The Modification Type IE informs the type of modification that the SDL underwent. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------|----------|-------|---------------------------------------------|-----------------------| -| Modification Type | M | | ENUMERATED (Added, Modified, Removed, ....) | | - -#### 7.3.3.11 Void - -#### 7.3.3.12 Void - -#### 7.3.3.13 Time to wait - -This IE defines the minimum allowed waiting times. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|-----------------------| -| Time to wait | M | | INTEGER (1..300) | Unit in seconds. | - -#### 7.3.3.14 Void - -#### 7.3.3.15 Void - -#### 7.3.3.16 Void - -#### 7.3.3.17 Void - -#### 7.3.3.18 Fetch Failure Cause - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------|----------|-------|-------------------------------------------------------------------------------------------------------|-----------------------| -| Fetch Failure Cause | M | | ENUMERATED (Invalid filter, Information type not supported, No information present, Unspecified, ...) | | - -#### 7.3.3.19 Void - -#### 7.3.3.20 Void - -#### 7.3.3.21 SDL Data Type ID - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| SDL Data Type ID | M | | STRING | Uniquely identifies a SDL data type. It shall be constructed with 3 fields concatenated by ":" (colon), as "{namespace}:{name}:{version}".

Clause 7.3.3.28 collects the known SDL Data Type IDs per data category. | - -#### 7.3.3.22 SDL Data Description - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------------------------------------|----------|-------|-----------------------|-----------------------| -| CHOICE Data Category | | | | | -| > E2 Node Information | | | | | -| >> SDL Data Description For E2 Node Information | M | | 7.3.3.28.1.2 | | -| > RAN Analytics Information | | | | | -| >> SDL Data Description For RAI | M | | 7.3.3.28.2.2 | | - -#### 7.3.3.23 SDL Data Unit - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------------------------|----------|-------|-----------------------|-----------------------| -| CHOICE Data Category | | | | | -| > E2 Node Information | | | | | -| >> SDL Data Unit For E2 Node Information | M | | 7.3.3.28.1.3 | | -| > RAN Analytics Information | | | | | -| >> SDL Data Unit For RAI | M | | 7.3.3.28.2.3 | | - -#### 7.3.3.24 Notification Criteria - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|---------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------| -| Notification Method | M | | ENUMERATED (PERIODIC, EVENT_TRIGGERED, ...) | | -| Notification Period | C | | INTEGER | Indicates the periodicity of notifications, in units of milliseconds.

Shall be present when Notification Method is set to "PERIODIC". | -| Trigger Event Definition | C | | 7.3.3.25 | Shall be present when Notification Method is set to "EVENT_TRIGGERED". | - -#### 7.3.3.25 Trigger Event Definition - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-----------------------------------------------------|----------|-------|-----------------------|-----------------------| -| CHOICE Data Category | | | | | -| > E2 Node Information | | | | | -| >> Trigger Event Definition For E2 Node Information | M | | 7.3.3.28.1.4 | | -| > RAN Analytics Information | | | | | -| >> Trigger Event Definition For RAI | M | | 7.3.3.28.2.4 | | - -#### 7.3.3.26 Subscription ID - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-----------------|----------|-------|-----------------------|----------------------------------------------------------------------------------------------------| -| Subscription ID | M | | STRING | Uniquely identifies a SDL data subscription among all the SDL subscriptions created by a consumer. | - -#### 7.3.3.27 SDL Update Notify Unit - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------------------------------------|----------|-------|-----------------------|-----------------------| -| CHOICE Data Category | | | | | -| > E2 Node Information | | | | | -| >> SDL Update Notify Unit For E2 Node Information | M | | 7.3.3.28.1.5 | | - -#### 7.3.3.28 SDL Data Type specific IE Definitions - -##### 7.3.3.28.1 E2 Node Information related IEs - -###### 7.3.3.28.1.1 SDL Data Type ID - -To construct the *SDL Data Type ID* IE for E2 Node Information, - -- the *namespace* field is "ORAN"; -- the *name* field is the text value of the *Information Type* IE in clause 7.3.3.28.1.6, i.e., "E2NodeList", "E2NodeComponentList", "E2NodeRanFunctionList", etc.; -- the *version* field is "1.0.0". - -EXAMPLE: "ORAN: E2NodeList:1.0.0" - -###### 7.3.3.28.1.2 SDL Data Description IE for E2 Node Information - -| IE Name | Presence | Range | Data type and reference | Semantics description | -|----------------------|----------|-------|-------------------------|-----------------------------------------------------------------------------| -| Information Type | M | | 7.3.3.28.1.6 | | -| > Filter List | | 0..1 | | Specifies the subset of the data to be subscribed for the Information Type. | - -| | | | | | -|-----------------------|---|------------------|--------------|--------------------------------------------------------------------------------------------------------| -| | | | | Multiple filters can be specified, in which case, a logical AND shall be performed across all filters. | -| >> Filter Item | | 0.. | | | -| >>> Filter Definition | M | | 7.3.3.28.1.7 | | - -| Range bound | Explanation | -|----------------|----------------------------------------------------------------------------------| -| maxnoofFilters | Maximum number of Filter Items to be contained in the Filter List. Value is 256. | - -###### 7.3.3.28.1.3 SDL Data Unit IE for E2 Node Information - -| IE Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|-------|-----------------------|-----------------------| -| Information Unit | M | | 7.3.3.28.1.11 | | - -###### 7.3.3.28.1.4 Trigger Event Definition IE For E2 Node Information - -| IE Name | Presence | Range | IE type and reference | Semantics description | -|----------------------------|----------|-------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Notify On Data Change Flag | O | | ENUMERATED (TRUE, ...) | When the IE is present and set to "TRUE", the notifications shall be triggered when the E2 Node information described by the SDL Data Description IE changes since the last notification associated with the same subscription. | - -###### 7.3.3.28.1.5 SDL Update Notify IE For E2 Node Information - -| IE Name | Presence | Range | IE type and reference | Semantics description | -|-------------------|----------|-------|-----------------------|-----------------------| -| Notification Unit | | | 7.3.3.28.1.12 | | - -###### 7.3.3.28.1.6 Information Type - -The IE indicates the type of E2 Node information the xApp requests. - -| IE Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|-------|------------------------------------------------------------------------|-----------------------| -| Information Type | M | | ENUMERATED (E2NodeList, E2NodeComponentConfig, E2NodeRanFunction, ...) | | - -###### 7.3.3.28.1.7 Filter Definition - -The IE defines a filter on the E2 Node information that the xApp requests. A Filter Definition is satisfied when the logical statement “X p Y” is True, where: - -- X is the filter type, represented by the Filter Type IE; -- p is the filter operator, represented by the Filter Condition IE; - -- Y is the set of the target values, represented by the Filter Condition Value IE. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------|----------|-------|-----------------------|-----------------------| -| Filter Type | M | | 7.3.3.28.1.8 | | -| Filter Condition | M | | 7.3.3.28.1.9 | | -| Filter Condition Value | M | | 7.3.3.28.1.10 | | - -###### 7.3.3.28.1.8 Filter Type - -The IE defines the filtering condition type to identify the E2 Node information the xApp request. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|---------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Filter Type | M | | ENUMERATED (E2NodeID, ComponentType, ServiceModel, ...) | Valid values of Filter Type IE are depending on the type of E2 Node Information indicated in the Information Type IE. See table 7.3.3.28.1.8-1 for the valid settings. | - -**Table 7.3.3.28.1.8-1: Valid Filter Type IE settings** - -| Filter Type | Information Type | | | -|---------------|------------------|-----------------------|-------------------| -| | E2NodeList | E2NodeComponentConfig | E2NodeRanFunction | -| E2NodeID | NO | YES | YES | -| ComponentType | YES | YES | NO | -| ServiceModel | YES | NO | YES | - -###### 7.3.3.28.1.9 Filter Condition - -The IE defines the filtering condition to identify the E2 Node information the xApp requests. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|-------|------------------------------------------------------------------------------|-----------------------| -| Filter Condition | M | | ENUMERATED (ContainedIn, NotContainedIn, Equals, GreaterThan, LessThan, ...) | | - -###### 7.3.3.28.1.10 Filter Condition Value - -The IE defines the filtering condition value to identify the information the xApp requests. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------------------|----------|----------|-----------------------------------------------------------|-----------------------| -| CHOICE Filter Condition Value | | | | | -| >E2NodeID | | | | | -| >>E2 Node ID List | | 1 | | | -| >>>E2 Node Item | | 1..65536 | | | -| >>>>E2 Node ID | M | | 7.3.3.14 | | -| >>>>E2 Node State | O | | 7.3.3.28.1.13 | | -| >ComponentType | | | | | -| >>E2 Node Component Type List | | 1 | | | -| >>>E2 Node Component Type Item | | 1..65536 | | | -| >>>>E2 Node Component Type | M | | E2 Node Component Interface Type IE, clause 9.2.26 of [3] | | -| >ServiceModel | | | | | - -| | | | | | -|--------------------------|---|----------|-------------------------------------------|--| -| >>RAN Function OID List | | 1 | | | -| >>>RAN Function OID Item | | 1..65536 | | | -| >>>>RAN function OID | M | | RAN Function OID IE, clause 9.2.31 of [3] | | - -###### 7.3.3.28.1.11 Information Unit - -The IE contains the E2 Node information that the Near-RT RIC platform sends to the xApp. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------------------|----------|----------------------------|--------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| CHOICE Information Unit | M | | Contents depend on Information Type. See following table for allowed settings. | | -| >E2 Node List Unit | | | | | -| >>E2 Node ID | M | | 10.1.6 | | -| >>E2 Node State | M | | 7.3.3.28.1.13 | | -| >E2 Node Component Config Unit | | | | | -| >>E2 Node ID | M | | 10.1.6 | | -| >>E2 Node Component Config List | | 1.. | | Value of "maxofE2nodeComponents" defined in 9.1.2.2 of [3]. | -| >>>E2 Node Component Type | M | | E2 Node Component Interface Type IE, clause 9.2.26 of [3] | | -| >>>E2 Node Component ID | O | | Clause 9.2.32 of [3] | | -| >>>E2 Node Component Configuration | M | | Clause 9.2.27 of [3] | | -| >>> Last Modified E2 Node Version | M | | INTEGER |

The Near-RT RIC platform maintains a version number for the E2 Node Information of each E2 Node. Incremented whenever any RAN Function or Component config changes.

This is the version number when the E2 Node Information changed last time.

| -| > Ran Function Unit | | | | | -| >>E2 Node ID | M | | 10.1.6 | | -| >>RAN Function List | | 1.. | | Value of "maxofRANfunctionIDs" defined in 9.1.2.2 of [3]. | -| >>> RAN Function ID | M | | 10.1.7 | | -| >>> RAN Function Definition | M | | Clause 9.2.23 of [3]. | | -| >>> RAN Function OID | M | | Clause 9.2.31 of [3]. | | -| >>> Last Modified E2 Node Version | M | | INTEGER |

The Near-RT RIC platform maintains a version number for the E2 Node Information of each E2 Node. Incremented whenever

| - -| | | | | | -|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------| -| | | | | any RAN Funciton or Component config changes.

This is the version number when the E2 Node Information changed last time. | -|--|--|--|--|---------------------------------------------------------------------------------------------------------------------------------| - -| Information Type | Information Unit | -|-----------------------|-------------------------------| -| E2NodeList | E2 Node List Unit | -| E2NodeComponentConfig | E2 Node Component Config Unit | -| E2NodeRanFunction | Ran Function Unit | - -###### 7.3.3.28.1.12 Notification Unit - -The IE contains the summary of E2 Node Information updates sent to the xApp. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| E2 Node ID | M | | 10.1.6 | | -| Current E2 Node Version | M | | INTEGER | The Near-RT RIC platform maintains the version number for E2 Node Information of each E2 Node. Incremented whenever any RAN Funciton or Component config changes.

This is the current version number of E2 Node Information for the E2 Node. | -| E2 Node State | O | | 7.3.3.28.1.13 | | - -###### 7.3.3.28.1.13 E2 Node State - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|--------------------------------------------------|-----------------------| -| E2 Node State | M | | ENUMERATED (CONNECTED, RESET, DISCONNECTED, ...) | | - -| E2 Node State | Meaning | -|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| CONNECTED | E2 Node has completed E2 Setup procedure.
Near-RT RIC platform has at least one validated E2NodeComponentConfig and E2NodeRanFunction record available for xApps using SDL API.
xApp may use E2 related API to request E2 Subscription and E2 Control procedures | -| RESET | E2 connection to E2 Node has been reset using E2AP Reset procedure.
Near-RT RIC platform has at least one validated E2NodeComponentConfig and E2NodeRanFunction record available for xApps using SDL API.
Previous E2 Subscriptions have been deleted
E2 related API services not available | -| DISCONNECTED | E2 connection to E2 Node is not available
xApp shall delete records for E2 Node | - -##### 7.3.3.28.2 RAN Analytics Information related IEs - -###### 7.3.3.28.2.1 SDL Data Type ID - -To construct the *SDL Data Type ID* IE for RAN Analytics Information, - -- the *namespace* field is "ORAN"; -- the *name* and *version* fields are the *RAI Type ID* and the *Version* defined in Table 6.1-1 of Y1TD [11], respectively. - -EXAMPLE: "ORAN:RAN performance analytics:1.0.0" - -###### 7.3.3.28.2.2 SDL Data Description For RAI - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------------------------------------|----------|-----------------------------------------|---------------------------------------------------------|---------------------------------------------------------------------------------------------------| -| Target Entity List | | 1 | | Represents the "targetEntities" attribute in clause 6.2.2.5.2.2 and 6.3.2.2.2.3.1 of Y1AP [10]. | -| > Target Entity Item | | 1..oofTarget
Entities> | | | -| >> Target Entity | M | | TargetEntity, clause 6 of Y1TD [11] | | -| Filter Parameters | O | | FilterParameters, clause 6 of Y1TD [11] | Represents the "filterParameters" attribute in clause 6.2.2.5.2.2 and 6.3.2.2.2.3.1 of Y1AP [10]. | -| Expected Validity Period Relative List | | 0..1 | | Represents the "expectedValidityPeriods Relative" attribute in clause 6.2.2.5.2.2 of Y1AP [10]. | -| > Expected Validity Period Relative Item | | 1..oofValidit
yPeriods
> | | | -| >> Expected Validity Period Relative | M | | ValidityPeriodRelative, clause 6.2.2.5.2.6 of Y1AP [10] | | -| Expected Validity Period List | | 0..1 | | Represents the "expectedValidity Periods" attribute in clause 6.3.2.2.2.3.1 of Y1AP [10]. | -| > Expected Validity Period Item | | 1..oofValidit
yPeriods
> | | | -| >> Expected Validity Period | M | | ValidityPeriod, clause 6.2.2.5.2.7 of Y1AP [10] | | - -| Range bound | Explanation | -|-------------------------------|-------------------------------------------------------------------------------------------------| -| maxnoofTargetEntities | Maximum number of target entities that can be carried in a target entity list. Value is 2048. | -| maxnoofValidityPeriods | Maximum number of validity periods that can be carried in a validity period list. Value is 512. | - -###### 7.3.3.28.2.3 SDL Data Unit For RAI - -| IE Name | Presence | Range | IE type and reference | Semantics description | -|------------|----------|-------|--------------------------------------------|--------------------------------------------------------------------| -| RAI Report | M | | RaiReport, clause 6.2.2.5.2.5 of Y1AP [10] | Represents a single RAI report in clause 6.2 and 6.3 of Y1AP [10]. | - -###### 7.3.3.28.2.4 Trigger Event Definition For RAI - -| IE Name | Presence | Range | IE type and reference | Semantics description | -|----------------------------|----------|-------|-------------------------------------------------|-----------------------------------------------------------------------------------------| -| Notification Event Trigger | M | | NotificationTriggerEvent, clause 6 of Y1TD [11] | Represents the "notificationTriggerEvent" attribute in clause 6.2.2.5.2.3 of Y1AP [10]. | - -### 7.3.4 Message and Information Element Abstract Syntax - -#### 7.3.4.1 Void - -#### 7.3.4.2 gRPC with Protocol Buffers - -##### 7.3.4.2.1 Usage of gRPC with Protocol Buffers - -This solution uses Protocol Buffers as message encoding, also as the Interface Definition Language (IDL) for gRPC [5]. - -Table 7.3.4.2.1-1 lists the mapping of enablement APIs and corresponding gRPC services. - -**Table 7.3.4.2.1-1: Mapping of SDL APIs and gRPC services** - -| API Name | gRPC service(s) | -|-----------------------|-------------------------------------------------------| -| SDL_Information_API | Sdl_Information_API, SDL_Information_API_Callback | -| Xapp_Data_Sharing_API | Xapp_Data_Sharing_API, Xapp_Data_Sharing_API_Callback | - -A procedure of an SDL API is mapped to a *gRPC method*. - -Table 7.3.4.1.1-2 lists the SDL APIs abstract syntax included in this document. - -**Table 7.3.4.2.1-2: List of SDL APIs abstract syntax** - -| API Name / Contents | Clause | Version | File Name | -|---------------------------------------------|-------------|---------|---------------------------------------------| -| SDL_Information_API | 7.3.4.2.2.1 | 2.0.0 | sdl_information_api_grpc_ver_2_0_0.proto | -| Xapp_Data_Sharing_API | 7.3.4.2.2.2 | 1.0.0 | xapp_data_sharing_api_grpc_ver_1_0_0.proto | -| SDL API common information elements | 7.3.4.2.3 | 2.0.0 | sdl_apis_common_ies_ver_2_0_0.proto | -| Near-RT RIC API common information elements | 10.2.1 | 3.0.0 | near_rt_ric_apis_common_ies_ver_3_0_0.proto | - -##### 7.3.4.2.2 API Definitions - -###### 7.3.4.2.2.1 SDL\_Information\_API - -``` - -syntax = "proto3"; - -package ricapi.sdl_information_api.grpc.v1; - -import "sdl_apis_common_ies_ver_2_0_0.proto"; -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; - -``` - -``` - -// gRPC service and rpc definition -service Sdl_Information_API { - rpc SdlSubscribeInformationProc(SdlSubscribeInformationInitMsg) returns - (SdlSubscribeInformationOutMsg) {}; - rpc SdlInformationFetchProc(SdlInformationFetchInitMsg) returns (SdlInformationFetchOutMsg) {}; -} - -message SdlSubscribeInformationInitMsg { - optional SubscribeInformationRequest subscribe_information_request = 1; -} - -message SdlSubscribeInformationOutMsg { - oneof type_of_message { - SubscribeInformationResponse subscribe_information_response = 1; - SubscribeInformationFailure subscribe_information_failure = 2; - } -} - -message SdlInformationFetchInitMsg { - optional InformationFetchRequest information_fetch_request = 1; -} - -message SdlInformationFetchOutMsg { - oneof type_of_message { - InformationFetchResponse information_fetch_response = 1; - InformationFetchFailure information_fetch_failure = 2; - } -} - -service Sdl_Information_API_Callback { - rpc SdlInformationPushProc(SdlInformationPushInitMsg) returns (SdlInformationPushOutMsg) {}; - rpc SdlInformationUpdateNotifyProc(SdlInformationUpdateNotifyInitMsg) returns - (SdlInformationUpdateNotifyInitMsg) {}; -} - -message SdlInformationPushInitMsg { - optional InformationPush information_push = 1; -} - -message SdlInformationPushOutMsg { -} - -message SdlInformationUpdateNotifyInitMsg { - optional InformationUpdateNotify information_update_notify = 1; -} - -message SdlInformationUpdateNotifyInitMsg { -} - -// ----- messages of SDL Information API ----- -// ----- messages of SDL Subscribe Information procedure ----- -message SubscribeInformationRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.sdl_apis_common_ies.v2.SdlDataTypeId sdl_data_type_id = 2; - optional ricapi.sdl_apis_common_ies.v2.DeliveryMethod delivery_method = 3; - optional ricapi.sdl_apis_common_ies.v2.SdlDataDescription sdl_data_description = 4; - optional ricapi.near_rt_ric_apis_common_ies.v3.EndpointInformation notification_destination = 5; - optional ricapi.sdl_apis_common_ies.v2.NotificationCriteria notification_criteria = 6; -} - -message SubscribeInformationResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.sdl_apis_common_ies.v2.SubscriptionId subscription_id = 2; -} - -message SubscribeInformationFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.sdl_apis_common_ies.v2.SubscriptionRejectCause subscription_reject_cause = 2; - optional uint32 time_to_wait = 3; -} - -// ----- messages of SDL Information Fetch procedure ----- -message InformationFetchRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.sdl_apis_common_ies.v2.SdlDataTypeId sdl_data_type_id = 2; -} - -``` - -``` - - optional ricapi.sdl_api_common_ies.v2.SdlDataDescription sdl_data_description = 3; - } - - message InformationFetchResponse { - optional ricapi.near_rt_ric_api_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.sdl_api_common_ies.v2.SdlDataTypeId sdl_data_type_id = 2; - repeated SdlDataBlockItem sdl_data_block = 3; - - message SdlDataBlockItem { - optional ricapi.sdl_api_common_ies.v2.SdlDataUnit sdl_data_unit = 1; - } - } - - message InformationFetchFailure { - optional ricapi.near_rt_ric_api_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.sdl_api_common_ies.v2.FetchFailureCause fetch_failure_cause = 2; - } - - // ----- messages of SDL Information Push procedure ----- - message InformationPush { - optional ricapi.near_rt_ric_api_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 4; - optional ricapi.sdl_api_common_ies.v2.SubscriptionId subscription_id = 1; - optional ricapi.sdl_api_common_ies.v2.SdlDataTypeId sdl_data_type_id = 2; - repeated SdlDataBlockItem sdl_data_block = 3; - - message SdlDataBlockItem { - optional ricapi.sdl_api_common_ies.v2.ModificationType modification_type = 1; - optional ricapi.sdl_api_common_ies.v2.SdlDataUnit sdl_data_unit = 2; - } - } - - // ----- messages of SDL Information Update Notify procedure ----- - message InformationUpdateNotify { - optional ricapi.near_rt_ric_api_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 4; - optional ricapi.sdl_api_common_ies.v2.SubscriptionId subscription_id = 1; - optional ricapi.sdl_api_common_ies.v2.SdlDataTypeId sdl_data_type_id = 2; - repeated SdlUpdateNotifyBlockItem sdl_update_notify_block = 3; - - message SdlUpdateNotifyBlockItem { - optional ricapi.sdl_api_common_ies.v2.ModificationType modification_type = 1; - optional ricapi.sdl_api_common_ies.v2.SdlUpdateNotifyUnit sdl_update_notify_unit = 2; - } - } -} - -``` - -###### 7.3.4.2.2.2 Xapp\_Data\_Sharing\_API - -``` - -syntax = "proto3"; - -package ricapi.xapp_data_sharing_api_grpc.v1; - -import "sdl_api_common_ies_ver_2_0_0.proto"; -import "near_rt_ric_api_common_ies_ver_3_0_0.proto"; - -// gRPC service and rpc definition -service Xapp Data Sharing API { - rpc XappSharedDataFetchProc(XappSharedDataFetchInitMsg) returns (XappSharedDataFetchOutMsg) {}; - rpc XappSharedDataSubscribeProc(XappSharedDataSubscribeInitMsg) returns -(XappSharedDataSubscribeOutMsg) {}; - rpc XappSharedDataSubscriptionDeleteProc(XappSharedDataSubscriptionDeleteInitMsg) returns -(XappSharedDataSubscriptionDeleteOutMsg) {}; -} - -message XappSharedDataFetchInitMsg { - optional XappSharedDataFetchRequest xapp_shared_data_fetch_request = 1; -} - -message XappSharedDataFetchOutMsg { - oneof type_of_message { - XappSharedDataFetchResponse xapp_shared_data_fetch_response = 1; - XappSharedDataFetchFailure xapp_shared_data_fetch_failure = 2; - } -} - -``` - -``` - -message XappSharedDataSubscribeInitMsg { - optional XappSharedDataSubscriptionRequest xapp_shared_data_subscription_request = 1; -} - -message XappSharedDataSubscribeOutMsg { - oneof type of message { - XappSharedDataSubscriptionResponse xapp_shared_data_subscription_response = 1; - XappSharedDataSubscriptionFailure xapp_shared_data_subscription_failure = 2; - } -} - -message XappSharedDataSubscriptionDeleteInitMsg { - optional XappSharedDataSubscriptionDeleteRequest xapp_shared_data_subscription_delete_request = 1; -} - -message XappSharedDataSubscriptionDeleteOutMsg { - oneof type_of_message { - XappSharedDataSubscriptionDeleteResponse xapp_shared_data_subscription_delete_response = 2; - XappSharedDataSubscriptionDeleteFailure xapp_shared_data_subscription_delete_failure = 3; - } -} - -service Xapp Data Sharing API Callback { - rpc XappSharedDataPushProc(XappSharedDataPushInitMsg) returns (XappSharedDataPushOutMsg) {}; -} - -message XappSharedDataPushInitMsg { - optional XappSharedDataPush xapp_shared_data_push = 1; -} - -message XappSharedDataPushOutMsg { -} - -// ----- messages of Xapp_Data_Sharing_API ----- -// ----- messages of Xapp Shared Data Fetch procedure ----- -message XappSharedDataFetchRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.sdl_apis_common_ies.v2.SdlDataTypeId sdl_data_type_id = 2; - optional ricapi.sdl_apis_common_ies.v2.SdlDataDescription sdl_data_description = 3; -} - -message XappSharedDataFetchResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.sdl_apis_common_ies.v2.SdlDataTypeId sdl_data_type_id = 2; - repeated SdlDataBlockItem sdl_data_block = 3; - - message SdlDataBlockItem { - optional ricapi.sdl_apis_common_ies.v2.SdlDataUnit sdl_data_unit = 1; - } -} - -message XappSharedDataFetchFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.sdl_apis_common_ies.v2.FetchFailureCause fetch_failure_cause = 2; -} - -// ----- messages of Xapp Shared Data Subscribe procedure ----- -message XappSharedDataSubscriptionRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.sdl_apis_common_ies.v2.SdlDataTypeId sdl_data_type_id = 2; - optional ricapi.sdl_apis_common_ies.v2.SdlDataDescription sdl_data_description = 3; - optional ricapi.sdl_apis_common_ies.v2.DeliveryMethod delivery_method = 4; - optional ricapi.near_rt_ric_apis_common_ies.v3.EndpointInformation notification_destination = 5; - optional ricapi.sdl_apis_common_ies.v2.NotificationCriteria notification_criteria = 6; -} - -message XappSharedDataSubscriptionResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.sdl_apis_common_ies.v2.SubscriptionId subscription_id = 2; -} - -message XappSharedDataSubscriptionFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.sdl_apis_common_ies.v2.SubscriptionRejectCause subscription_reject_cause = 2; -} - -``` - -``` - -} - -// ----- messages of Xapp Shared Data Push procedure ----- -message XappSharedDataPush { - optional ricapi.sdl_apis_common_ies.v2.SubscriptionId subscription_id = 1; - optional ricapi.sdl_apis_common_ies.v2.SdlDataTypeId sdl_data_type_id = 2; - repeated SdlDataBlockItem sdl_data_block = 3; - - message SdlDataBlockItem { - optional ricapi.sdl_apis_common_ies.v2.ModificationType modification_type = 1; - optional ricapi.sdl_apis_common_ies.v2.SdlDataUnit sdl_data_unit = 2; - } -} - -// ----- messages of Xapp Shared Data Subscription Delete procedure ----- -message XappSharedDataSubscriptionDeleteRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.sdl_apis_common_ies.v2.SubscriptionId subscription_id = 2; -} - -message XappSharedDataSubscriptionDeleteResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; -} - -message XappSharedDataSubscriptionDeleteFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.sdl_apis_common_ies.v2.SubscriptionRejectCause subscription_reject_cause = 2; -} - -``` - -##### 7.3.4.2.3 SDL API common information elements - -``` - -syntax = "proto3"; - -package ricapi.sdl_apis_common_ies.v2; - -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; - -// ----- Information Elements ----- - -// -----A----- -// From E2AP Clause 9.2.32 -message AmfName { - optional string value = 1; -} - -// -----D----- -enum DeliveryMethod { - DELIVERY_METHOD_UPDATE_NOTIFY = 0; - DELIVERY_METHOD_PUSH_DELTA = 1; - DELIVERY_METHOD_PUSH_FULL = 2; -} - -// -----E----- -// From E2AP Clause 9.2.27 -message E2NodeComponentConfiguration { - optional bytes e2_node_component_request_part = 1; - optional bytes e2_node_component_response_part = 2; -} - -// From E2AP Clause 9.2.32 -message E2NodeComponentId { - oneof e2_node_component_interface_type { - NgInterfaceType ng = 1; - XnInterfaceType xn = 2; - ElInterfaceType el = 3; - FlInterfaceType fl = 4; - WlInterfaceType wl = 5; - SlInterfaceType sl = 6; - X2InterfaceType x2 = 7; - } -} - -``` - -``` -message NgInterfaceType { - optional AmfName amf_name = 1; -} - -message XnInterfaceType { - optional GlobalNgRanNodeId global_ng_ran_node_id = 1; -} - -message ElInterfaceType { - optional near_rt_ric_apis_common_ies.v3.GnbCuUpId gnb_cu_up_id = 1; -} - -message FlInterfaceType { - optional near_rt_ric_apis_common_ies.v3.GnbDuId gnb_du_id = 1; -} - -message WlInterfaceType { - optional near_rt_ric_apis_common_ies.v3.NgEnbDuId ng_enb_du_id = 1; -} - -message SlInterfaceType { - optional MmeName mme_name = 1; -} - -message X2InterfaceType { - optional near_rt_ric_apis_common_ies.v3.GlobalEnbId global_enb_id = 1; - optional near_rt_ric_apis_common_ies.v3.GlobalEnGnbId global_en_gnb_id = 2; -} -} - -// From E2AP Clause 9.2.26 -enum E2NodeComponentType { - E2_NODE_COMPONENT_TYPE_NG = 0; - E2_NODE_COMPONENT_TYPE_XN = 1; - E2_NODE_COMPONENT_TYPE_EL = 2; - E2_NODE_COMPONENT_TYPE_FL = 3; - E2_NODE_COMPONENT_TYPE_WL = 4; - E2_NODE_COMPONENT_TYPE_SL = 5; - E2_NODE_COMPONENT_TYPE_X2 = 6; -} - -enum E2NodeState { - E2_NODE_STATE_CONNECTED = 0; - E2_NODE_STATE_RESET = 1; - E2_NODE_STATE_DISCONNECTED = 2; -} - -// -----F----- -enum FetchFailureCause { - FETCH_FAILURE_CAUSE_UNSPECIFIED = 0; - FETCH_FAILURE_CAUSE_INVALID_FILTER = 1; - FETCH_FAILURE_CAUSE_INFORMATION_TYPE_NOT_SUPPORTED = 2; - FETCH_FAILURE_CAUSE_NO_INFORMATION_PRESENT = 3; -} - -enum FilterCondition { - FILTER_CONDITION_CONTAINED_IN = 0; - FILTER_CONDITION_NOT_CONTAINED_IN = 1; - FILTER_CONDITION_EQUALS = 2; - FILTER_CONDITION_GREATER_THAN = 3; - FILTER_CONDITION_LESS_THAN = 4; -} - -message FilterConditionValue { - oneof filter_condition_value_type { - E2NodeIdList e2_node_id_list = 1; - E2NodeComponentTypeList e2_node_component_type_list = 2; - RanFunctionOidList ran_function_oid_list = 3; - } -} -``` - -``` - -message E2NodeIdList { - repeated E2NodeIdItem list = 1; - - message E2NodeIdItem { - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId e2_node_id = 1; - optional E2NodeState e2_node_state = 2; - } -} - -message E2NodeComponentTypeList { - repeated E2NodeComponentTypeItem list = 1; - - message E2NodeComponentTypeItem { - optional E2NodeComponentType e2_node_component_type = 1; - } -} - -message RanFunctionOidList { - repeated RanFunctionOidItem list = 1; - - message RanFunctionOidItem { - optional RanFunctionOid ran_function_oid = 1; - } -} - -message FilterDefinition { - optional FilterType filter_type = 1; - optional FilterCondition filter_condition = 2; - optional FilterConditionValue filter_condition_value = 3; -} - -enum FilterType { - FILTER_TYPE_E2_NODE_ID = 0; - FILTER_TYPE_COMPONENT_TYPE = 1; - FILTER_TYPE_SERVICE_MODEL = 2; -} - -// -----G----- - -// From E2AP Clause 9.2.32 -message GlobalNgRanNodeId { - oneof ng_ran_node_choice { - near_rt_ric_apis_common_ies.v3.GlobalGnbId global_gnb_id = 1; - near_rt_ric_apis_common_ies.v3.GlobalNgEnbId global_ng_enb_id = 2; - } -} - -// -----I----- - -enum InformationType { - INFORMATION_TYPE_E2NODELIST = 0; - INFORMATION_TYPE_E2NODECOMPONENTCONFIG = 1; - INFORMATION_TYPE_E2NODERANFUNCTION = 2; -} - -message InformationUnit { - oneof information_unit_type { - E2NodeListUnit e2_node_list_unit = 1; - E2NodeComponentConfigUnit e2_node_component_config_unit = 2; - RanFunctionUnit ran_function_unit = 3; - } - - message E2NodeListUnit { - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId e2_node_id = 1; - optional E2NodeState e2_node_state = 2; - } - - message E2NodeComponentConfigUnit { - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId e2_node_id = 1; - repeated E2NodeComponentConfigItem e2_node_component_config_list = 2; - - message E2NodeComponentConfigItem { - optional E2NodeComponentType e2_node_component_type = 1; - } - } -} - -``` - -``` - optional E2NodeComponentId e2_node_component_id = 2; - optional E2NodeComponentConfiguration e2_node_component_configuration = 3; - optional uint32 last_modified_e2_node_version = 4; - } -} - -message RanFunctionUnit { - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId e2_node_id = 1; - repeated RanFunctionItem ran_function_list = 2; - - message RanFunctionItem { - optional near_rt_ric_apis_common_ies.v3.RanFunctionId ran_function_id = 1; - optional RanFunctionDefinition ran_function_definition = 2; - optional RanFunctionOid ran_function_oid = 3; - optional uint32 last_modified_e2_node_version = 4; - } -} - -// -----M----- -enum ModificationType { - TYPE_ADDED = 0; - TYPE_MODIFIED = 1; - TYPE_REMOVED = 2; -} - -// From E2AP Clause 9.2.32 -message MmeName { - optional string value = 1; -} - -// -----N----- -message NotificationCriteria { - optional NotificationMethod notification_method = 1; - optional uint32 notification_period = 2; - optional TriggerEventDefinition trigger_event_definition = 3; - - enum NotificationMethod { - NOTIFICATION_METHOD_PERIODIC = 0; - NOTIFICATION_METHOD_EVENT_TRIGGERED = 1; - } -} - -message NotificationUnit { - optional near_rt_ric_apis_common_ies.v3.GlobalE2NodeId e2_node_id = 1; - optional uint32 current_e2_node_version = 2; - optional E2NodeState e2_node_state = 3; -} - -// -----R----- -// From E2AP Clause 9.2.23 -message RanFunctionDefinition { - optional bytes value = 1; -} - -// From E2AP Clause 9.2.31 -message RanFunctionOid { - optional string value = 1; -} - -// -----S----- -message SdlDataDescription { - oneof data_category { - SdlDataDescriptionForE2NodeInformation sdl_data_description_for_e2_node_information = 1; - SdlDataDescriptionForRai sdl_data_description_for_rai = 2; - } -} - -message SdlDataDescriptionForE2NodeInformation { - optional InformationType information_type = 1; - repeated FilterItem filter_list = 2; -} -``` - -``` - - message FilterItem { - optional FilterDefinition filter_definition = 1; - } - } - - message SdlDataDescriptionForRai { - repeated TargetEntityItem target_entity_list = 1; - optional bytes filter_parameters = 2; - repeated ExpectedValidityPeriodRelativeItem expected_validity_period_relative_list = 3; - repeated ExpectedValidityPeriodItem expected_validity_period_list = 4; - - message TargetEntityItem { - optional bytes target_entity = 1; - } - - message ExpectedValidityPeriodRelativeItem { - optional bytes expected_valitity_period_relative = 1; - } - - message ExpectedValidityPeriodItem { - optional bytes expected_valitity_period = 1; - } - } - - message SdlDataTypeId { - optional string value = 1; - } - - message SdlDataUnit { - oneof data_category { - SdlDataUnitForE2NodeInformation sdl_data_unit_for_e2_node_information = 1; - SdlDataUnitForRai sdl_data_unit_for_rai = 2; - } - } - - message SdlDataUnitForE2NodeInformation { - optional InformationUnit information_unit = 1; - } - - message SdlDataUnitForRai { - optional bytes rai_report = 1; - } - - message SdlUpdateNotifyUnit { - oneof data_category { - SdlUpdateNotifyUnitForE2NodeInformation sdl_update_notify_unit_for_e2_node_information = 1; - } - } - - message SdlUpdateNotifyUnitForE2NodeInformation { - optional NotificationUnit notification_unit = 1; - } - - message SubscriptionId { - optional string subscription_id = 1; - } - - enum SubscriptionRejectCause { - SUBSCRIPTION_REJECT_CAUSE_UNSPECIFIED = 0; - SUBSCRIPTION_REJECT_CAUSE_SDL_REACHED_CAPACITY = 1; - SUBSCRIPTION_REJECT_CAUSE_INFORMATION_TYPE_NOT_SUPPORTED = 2; - SUBSCRIPTION_REJECT_CAUSE_INVALID_FILTER = 3; - } - - // -----T----- - - message TimeToWait { - optional uint32 value = 1; - } - - message TriggerEventDefinition { - -``` - -``` - - oneof data_category { - TriggerEventDefinitionForE2NodeInformation trigger_event_definition_for_e2_node_information = 1; - TriggerEventDefinitionForRai trigger_event_definition_for_rai = 2; - } -} - -message TriggerEventDefinitionForE2NodeInformation { - optional EnumValue notify_on_data_change = 1; - - enum EnumValue { - ENUM_VALUE_TRUE = 0; - } -} - -message TriggerEventDefinitionForRai { - optional bytes notification_event_trigger = 1; -} - -``` - -### 7.3.5 Message Transfer Syntax - -#### 7.3.5.1 Void - -#### 7.3.5.2 gRPC with Protocol Buffers - -The message transfer syntax for Solution 2 is serialized Protocol Buffers [4]. - -# 8 Management API - -## 8.1 Overview - -### 8.1.1 Protocol Stack - -In this version of specification, the default protocol stack for the Management APIs is shown on Figure 8.1.1-1. - -NOTE: The security protocols are specified in [6]. - -![Protocol stack diagram for Management APIs showing layers from Application down to Physical Layer.](c24164782e328c82ba89b80c0ef8c3d7_img.jpg) - -| | -|-----------------| -| Application | -| gRPC | -| HTTP/2 | -| TCP | -| IP | -| Data Link Layer | -| Physical Layer | - -Protocol stack diagram for Management APIs showing layers from Application down to Physical Layer. - -**Figure 8.1.1-1: Protocol stack for Management APIs** - -The Management APIs use gRPC [5] with Protocol Buffers [4] as the application layer serialization protocol. - -### 8.1.2 List of Management APIs, procedures and messages - -The Management API procedures introduced in clause 9.4 of [2] are categorized under the Management APIs. These APIs include: - -- xApp Registration API: enabling registration of xApps with the Near-RT RIC platform. - -These APIs are summarized in Table 8.1.2-1. - -**Table 8.1.2-1: List of Management APIs** - -| API Name | Description | -|----------------------------|----------------------------------------------------| -| Mgmt_xApp_Registration_API | Near-RT RIC platform service for xApp registration | - -The table 8.1.2-2 lists the API procedures for each Management API. - -**Table 8.1.2-2: List of Management API procedures** - -| API Name | API procedure | Communication type | -|----------------------------|-------------------|--------------------| -| Mgmt_xApp_Registration_API | xApp Registration | Request/Response | - -The table 8.1.2-3 lists the messages for each management API procedure. - -**Table 8.1.2-3: List of Management API messages** - -| API Procedure | Initiated by | Initiating Message | Outcome Message | | -|-------------------|--------------|---------------------------|---------------------------|---------------------------| -| | | | Successful Outcome | Unsuccessful Outcome | -| xApp Registration | xApp | XAPP REGISTRATION REQUEST | XAPP REGISTRATION SUCCESS | XAPP REGISTRATION FAILURE | - -## 8.2 Management API Procedures - -### 8.2.1 xApp Registration Procedure - -#### 8.2.1.1 General - -This procedure is used by an xApp who wants to register in Near-RT RIC platform. - -#### 8.2.1.2 Successful Operation - -``` -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: XAPP REGISTRATION (Request) -near -> app: XAPP REGISTRATION (Success) -@enduml -``` - -![Sequence diagram for successful xApp registration. Lifelines: xApp and Near-RT RIC Platform. The xApp sends an xAPP REGISTRATION (Request) message to the platform, and the platform responds with an xAPP REGISTRATION (Success) message.](56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: xAPP REGISTRATION (Request) - Near-RT RIC Platform-->>xApp: xAPP REGISTRATION (Success) - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for successful xApp registration. Lifelines: xApp and Near-RT RIC Platform. The xApp sends an xAPP REGISTRATION (Request) message to the platform, and the platform responds with an xAPP REGISTRATION (Success) message. - -**Figure 8.2.1.2-1: xApp Registration procedure, successful operation** - -The xApp initiates the procedure by sending an xApp Registration (Request) message to the Near-RT-RIC platform. The message contains a unique *Procedure Transaction ID* IE assigned by the initiating xApp, the optional *xApp Description* IE, and the *Required APIs and Data Types* IE that specifies the APIs and data types needed for normal operation of the xApp. - -At reception of the xApp Registration (Request) message, the Near-RT-RIC platform shall: - -- Check xApp’s compatibility with the Near-RT RIC platform, using information in the *Required APIs and Data Types* IE. -- Assign an xApp ID and create the profile for the xApp. - -If the registration request is successfully fulfilled, the Near-RT RIC platform shall send an xApp Registration (Success) message back to the xApp. - -In the xApp Registration (Success) message, the Near-RT RIC platform shall include the associated *Procedure Transaction ID* IE and the *xApp ID* IE. - -#### 8.2.1.3 Unsuccessful Operation - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -participant "xApp" as app -participant "Near-RT RIC Platform" as near -app -> near: xAPP REGISTRATION (Request) -near --> app: xAPP REGISTRATION (Failure) -@enduml - -``` - -![Sequence diagram for unsuccessful xApp registration. Lifelines: xApp and Near-RT RIC Platform. The xApp sends an xAPP REGISTRATION (Request) message to the platform, and the platform responds with an xAPP REGISTRATION (Failure) message.](2e18ae7359d8c32e96919956f238ecc5_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: xAPP REGISTRATION (Request) - Near-RT RIC Platform-->>xApp: xAPP REGISTRATION (Failure) - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for unsuccessful xApp registration. Lifelines: xApp and Near-RT RIC Platform. The xApp sends an xAPP REGISTRATION (Request) message to the platform, and the platform responds with an xAPP REGISTRATION (Failure) message. - -**Figure 8.2.1.3-1: xApp Registration procedure, unsuccessful operation** - -If the registration request fails, the Near-RT RIC platform shall send an xApp Registration (Failure) message back to the xApp. The message shall include the associated *Procedure Transaction ID* IE replicated from the corresponding request and appropriate cause. - -#### 8.2.1.4 Abnormal Conditions - -Not applicable. - -## 8.3 Elements for Management API Communication - -### 8.3.1 General - -### 8.3.2 Message Functional Definition and Content - -#### 8.3.2.1 xAPP REGISTRATION REQUEST - -This message is sent by an xApp to the Near-RT RIC platform for xApp Registration. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------------|----------|---------------------------------|-----------------------|-------------------------------------------------| -| Message Type | M | | 8.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value assigned by the initiating xApp. | -| xApp Description | O | | 8.3.3.2 | | -| Required APIs and Data Types | M | | | | -| > List of Required APIs | | 0..
| | The API names and versions required by the xApp | -| >> API Name | M | | 10.1.3 | | -| >> API Version | M | | 10.1.4 | | -| > List of A1 Policy Types | | 0..
| | The A1 Policy Types required by the xApp | -| >> A1 Policy Type ID | M | | 8.3.3.3 | | -| > List of E2 Service Models | | 0..
| | The E2 Service Models required by the xApp | -| >> E2 Service Model Name | M | | 8.3.3.4 | | -| >> E2 Service Model Version | M | | 8.3.3.5 | | - -| Range bound | Explanation | -|----------------------|----------------------------------------------------------------------| -| maxnoofAPIs | Maximum no. of APIs supported by the xApp. Value is 1024. | -| maxnoofA1PolicyTypes | Maximum no. of A1 Policy Types supported by the xApp. Value is 1024. | -| maxnoofE2SMs | Maximum no. of E2SMs supported by the xApp. Value is 1024. | - -#### 8.3.2.2 xAPP REGISTRATION SUCCESS - -This message is sent by the Near-RT RIC platform after the xApp's registration request is successfully accepted. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 8.3.3.1 | | - -| | | | | | -|--------------------------|---|--|--------|----------------------------------------------| -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | -| xApp ID | M | | 10.1.2 | | - -#### 8.3.2.3 xAPP REGISTRATION FAILURE - -This message is sent by the Near-RT RIC platform after the xApp's registration request is failed. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|----------------------------------------------| -| Message Type | M | | 8.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | Value replicated from corresponding request. | -| Cause | M | | 8.3.3.6 | | - -#### 8.3.2.4 xAPP CONFIGURATION REQUEST - -#### 8.3.2.5 xAPP CONFIGURATION RESPONSE - -#### 8.3.2.6 xAPP CONFIGURATION FAILURE - -### 8.3.3 Information Element Definitions - -#### 8.3.3.1 Message Type - -This IE uniquely identifies the message being sent. It is mandatory for all messages. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|-------|-----------------------------------------|-----------------------------------------------------------------------| -| Message Type | | | | | -| >Procedure Type | M | | CHOICE (xApp Registration, ...) | | -| >Type of Message | M | | CHOICE (Request, Success, Failure, ...) | Refer to Table 8.1.2-3 for applicable choices for each procedure type | - -#### 8.3.3.2 xApp Description - -This IE provides generic information related to the xApp such as its name, vendor and purpose. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|-------|-----------------------|-----------------------| -| xApp Description | M | | STRING | | - -#### 8.3.3.3 A1 Policy Type ID - -Defined in 10.1.5. - -#### 8.3.3.4 E2 Service Model Name - -This IE specifies the name of E2 Service Model supported by the xApp. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|-----------------------| -|---------------|----------|-------|-----------------------|-----------------------| - -| | | | | | -|-----------------------|---|--|--------|--------------------------------------------| -| E2 Service Model Name | M | | STRING | The E2SM short name as in Table 5-2 of [8] | -|-----------------------|---|--|--------|--------------------------------------------| - -#### 8.3.3.5 E2 Service Model Version - -This IE is used to indicate the version of E2 Service Model supported by the xApp. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| E2 Service Model Version | M | | STRING | | - -#### 8.3.3.6 Cause - -This IE is used to indicate the reason for a particular event for the Management APIs. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-------------------------------------------------------------------------------------------------------------------|-----------------------| -| Cause | M | | ENUMERATED
(Unspecified, API Not Supported, A1 Policy Type Not Supported, E2 Service Model Not Supported, ...) | | - -### 8.3.4 Message and Information Element Abstract Syntax - -#### 8.3.4.1 Solution 1: gRPC with Protocol Buffers - -##### 8.3.4.1.1 Usage of gRPC with Protocol Buffers - -This solution uses Protocol Buffers as message encoding, and also as the Interface Definition Language (IDL) for gRPC [5]. - -Table 8.3.4.1.1-1 lists the mapping of management APIs and corresponding gRPC services. - -**Table 8.3.4.1.1-1: Mapping of management APIs and gRPC services** - -| API Name | gRPC service(s) | -|----------------------------|----------------------------| -| Mgmt_Xapp_Registration_API | Mgmt_Xapp_Registration_API | - -A procedure of an Management API is mapped to a *gRPC method*. - -Table 8.3.4.1.1-2 lists the Management APIs abstract syntax included in this document. - -**Table 8.3.4.1.1-2: List of Management APIs abstract syntax** - -| API Name / Contents | Clause | Version | File Name | -|---------------------------------------------|-------------|---------|---------------------------------------------| -| Mgmt_Xapp_Registration_API | 8.3.4.1.2.1 | 1.0.0 | mgmt_xapp_registration_api_ver_1_0_0.proto | -| Management API common information elements | 8.3.4.1.3 | 1.0.0 | mgmt_apis_common_ies_ver_1_0_0.proto | -| Near-RT RIC API common information elements | 10.2.1 | 2.0.0 | near_rt_ric_apis_common_ies_ver_3_0_0.proto | - -##### 8.3.4.1.2 API Definitions - -###### 8.3.4.1.2.1 Mgmt\_Xapp\_Registration\_API - -``` - -syntax = "proto3"; - -package ricapi.mgmt_xapp_registration_api.v1; - -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; -import "mgmt_apis_common_ies_ver_1_0_0.proto"; - -// gRPC service and rpc definition -service mgmt_Xapp_Registration_API { - rpc XappRegistrationProc(XappRegistrationInitMsg) returns (XappRegistrationOutMsg) {}; -} - -message XappRegistrationInitMsg { - optional XappRegistrationRequest xapp_registration_request = 1; -} - -message XappRegistrationOutMsg { - oneof type_of_message { - XappRegistrationSuccess xapp_registration_success = 1; - XappRegistrationFailure xapp_registration_failure = 2; - } -} - -// ----- messages of Mgmt_Xapp_Registration_API ----- -// ----- messages of xApp Registration procedure ----- - -message XappRegistrationRequest { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional mgmt_apis_common_ies.v1.XappDescription xapp_description = 2; - optional RequiredApisAndDataTypes required_apis_and_data_types = 3; - - message RequiredApisAndDataTypes { - repeated RequiredApiItem list_of_required_apis = 1; - repeated AlPolicyTypeItem list_of_al_policy_types = 2; - repeated E2ServiceModelItem list_of_e2_service_models = 3; - - message RequiredApiItem { - optional near_rt_ric_apis_common_ies.v3.ApiName api_name = 1; - optional near_rt_ric_apis_common_ies.v3.ApiVersion api_version = 2; - } - - message AlPolicyTypeItem { - optional near_rt_ric_apis_common_ies.v3.AlPolicyTypeId al_policy_type_id = 1; - } - - message E2ServiceModelItem { - optional mgmt_apis_common_ies.v1.E2ServiceModelName e2_service_model_name = 1; - optional mgmt_apis_common_ies.v1.E2ServiceModelVersion e2_service_model_version = 2; - } - } -} - -message XappRegistrationSuccess { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional near_rt_ric_apis_common_ies.v3.XappId xapp_id = 2; -} - -message XappRegistrationFailure { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional mgmt_apis_common_ies.v1.Cause cause = 2; -} - -``` - -##### 8.3.4.1.3 Information Element Definitions - -``` -syntax = "proto3"; - -package ricapi.mgmt_apis_common_ies.v1; - -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; - -// ----- Information Elements ----- -// -----C----- -enum Cause { - UNSPECIFIED = 0; - API_NOT_SUPPORTED = 1; - AI_POLICY_TYPE_NOT_SUPPORTED = 2; - E2_SERVICE_MODEL_NOT_SUPPORTED = 3; -} - -// -----E----- -message E2ServiceModelName { - optional string value = 1; -} - -message E2ServiceModelVersion { - optional string value = 1; -} - -// -----X----- -message XappDescription { - optional string value = 1; -} -``` - -### 8.3.5 Message Transfer Syntax - -#### 8.3.5.1 Solution 1: gRPC with Protocol Buffers - -The message transfer syntax for Solution 1 is serialized Protocol Buffers [4]. - -# --- 9 Enablement API - -## 9.1 Overview - -### 9.1.1 Protocol Stack - -In this version of specification, the default protocol stack for the Enablement APIs is shown on Figure 9.1.1-1. - -NOTE: The security protocols are specified in [6]. - -![Protocol stack for Enablement APIs diagram showing layers from Application down to Physical Layer.](3d1817e8551f9c226a5f561108d3b3f9_img.jpg) - -| | -|-----------------| -| Application | -| gRPC | -| HTTP/2 | -| TCP | -| IP | -| Data Link Layer | -| Physical Layer | - -Protocol stack for Enablement APIs diagram showing layers from Application down to Physical Layer. - -**Figure 9.1.1-1: Protocol stack for Enablement APIs** - -The Enablement APIs use gRPC [5] with Protocol Buffers [4] as the application layer serialization protocol. - -### 9.1.2 List of Enablement APIs, procedures and messages - -The enablement API procedures introduced in clause 9.5 of [2] are categorized under the enablement APIs. These APIs include: - -- Discovery API: enabling discovery of the Near-RT RIC APIs by xApps. -- Events API: enabling subscription/un-subscription to API-related events and event notifications. -- Registration API: enabling registration of the Near-RT RIC APIs by xApps. - -These APIs are summarized in Table 9.1.2-1. - -**Table 9.1.2-1: List of Enablement APIs** - -| API Name | Description | -|------------------------|-----------------------------------------------------| -| Enabl_Discovery_API | Near-RT RIC platform service for API discovery | -| Enabl_Events_API | Near-RT RIC platform service for API related events | -| Enabl_Registration_API | Near-RT RIC platform service for API registration | - -The table 9.1.2-2 lists the API procedures for each enablement API. - -**Table 9.1.2-2: List of enablement API procedures** - -| API Name | API procedure | Communication type | -|------------------------|-------------------------------|--------------------| -| Enabl_Discovery_API | API Discovery | Request/Response | -| Enabl_Events_API | API Event Subscription | Request/Response | -| | API Event Subscription Delete | Request/Response | -| | API Event Notification | Notify | -| Enabl_Registration_API | API Registration | Request/Response | -| | API Registration Update | Request/Response | -| | API Deregistration | Request/Response | - -The table 9.1.2-3 lists the messages for each enablement API procedure. - -**Table 9.1.2-3: List of enablement API messages** - -| API Procedure | Initiated by | Initiating Message | Outcome Message | | -|---------------|--------------|--------------------|--------------------|----------------------| -| | | | Successful Outcome | Unsuccessful Outcome | - -| | | | | | -|-------------------------------|----------------------|---------------------------------------|----------------------------------------|---------------------------------------| -| API Discovery | xApp | API DISCOVERY REQUEST | API DISCOVERY RESPONSE | API DISCOVERY FAILURE | -| API Event Subscription | xApp | API EVENT SUBSCRIPTION REQUEST | API EVENT SUBSCRIPTION RESPONSE | API EVENT SUBSCRIPTION FAILURE | -| API Event Subscription Delete | xApp | API EVENT SUBSCRIPTION DELETE REQUEST | API EVENT SUBSCRIPTION DELETE RESPONSE | API EVENT SUBSCRIPTION DELETE FAILURE | -| API Event Notification | Near-RT RIC platform | API EVENT NOTIFICATION | API EVENT NOTIFICATION ACK | - | -| API Registration | xApp | API REGISTRATION REQUEST | API REGISTRATION RESPONSE | API REGISTRATION FAILURE | -| API Registration Update | xApp | API REGISTRATION UPDATE REQUEST | API REGISTRATION UPDATE RESPONSE | API REGISTRATION UPDATE FAILURE | -| API Deregistration | xApp | API DEREGISTRATION REQUEST | API DEREGISTRATION RESPONSE | API DEREGISTRATION FAILURE | - -## 9.2 Enablement API Procedures - -### 9.2.1 Enabl\_Discovery\_API Procedures - -#### 9.2.1.1 General - -The Enabl\_Discovery\_API allows an xApp to discover service APIs available at the Near-RT RIC platform. - -The API procedure defined for Enabl\_Discovery\_API is shown in table 9.2.1.1-1. - -**Table 9.2.1.1-1: Procedure of the Enabl\_Discovery\_API** - -| API Procedure | Description | Initiated by | -|---------------|-------------------------------------------------------------------------------------------------------|--------------| -| API Discovery | This procedure is used by an xApp to discover Near-RT RIC APIs available at the Near-RT RIC platform. | xApp | - -#### 9.2.1.2 API Discovery procedure - -##### 9.2.1.2.1 Successful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" - -xApp -> RICP : 1. API DISCOVERY REQUEST -RICP -> xApp : 2. API DISCOVERY RESPONSE - -@enduml -``` - -![Sequence diagram showing the API Discovery procedure with successful operation. It consists of three identical interaction steps between an xApp and a Near-RT RIC Platform. In each step, the xApp sends a request (1. API DISCOVERY REQUEST or 1. Near-RT RIC API DISCOVERY REQUEST) and the platform responds (2. API DISCOVERY RESPONSE or 2. Near-RT RIC API DISCOVERY RESPONSE).](060648daa95345c57f019fc00ad75993_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: - xApp->>Near-RT RIC Platform: 1. API DISCOVERY REQUEST - Near-RT RIC Platform-->>xApp: 2. API DISCOVERY RESPONSE - Note left of xApp: - xApp->>Near-RT RIC Platform: 1. Near-RT RIC API DISCOVERY REQUEST - Near-RT RIC Platform-->>xApp: 2. Near-RT RIC API DISCOVERY RESPONSE - Note left of xApp: - xApp->>Near-RT RIC Platform: 1. Near-RT RIC API DISCOVERY REQUEST - Near-RT RIC Platform-->>xApp: 2. Near-RT RIC API DISCOVERY RESPONSE - -``` - -Sequence diagram showing the API Discovery procedure with successful operation. It consists of three identical interaction steps between an xApp and a Near-RT RIC Platform. In each step, the xApp sends a request (1. API DISCOVERY REQUEST or 1. Near-RT RIC API DISCOVERY REQUEST) and the platform responds (2. API DISCOVERY RESPONSE or 2. Near-RT RIC API DISCOVERY RESPONSE). - -**Figure 9.2.1.2.1-1: API Discovery procedure, successful operation** - -To discover Near-RT RIC APIs available at the API Enablement function, the xApp shall send an API DISCOVERY REQUEST message with the *xApp ID* IE and the *Query Parameters* IE to the Near-RT RIC platform. - -Upon receiving the message, the Near-RT RIC platform shall: - -1. verify the identity of the xApp and check if it is authorized to discover the Near-RT RIC APIs; -2. if the xApp is authorized to discover the Near-RT RIC APIs, the Near-RT RIC platform shall: - - a. search the API registry for APIs matching the query criteria in the *Query Parameters* IE; - - b. apply the discovery policy, if any, on the search results and filter the search results to obtain the list of service API description; - - c. return the filtered search results in the API DISCOVERY RESPONSE message. - -##### 9.2.1.2.2 Unsuccessful Operation - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" - -xApp -> RICP : 1. API DISCOVERY REQUEST -RICP -> xApp : 2. API DISCOVERY FAILURE - -@enduml - -``` - -![Sequence diagram showing an unsuccessful API discovery procedure. An xApp sends an API DISCOVERY REQUEST to a Near-RT RIC Platform, which responds with an API DISCOVERY FAILURE.](59e29b37c5e332b0be088cde8c4d217e_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. API DISCOVERY REQUEST - Near-RT RIC Platform-->>xApp: 2. API DISCOVERY FAILURE - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram showing an unsuccessful API discovery procedure. An xApp sends an API DISCOVERY REQUEST to a Near-RT RIC Platform, which responds with an API DISCOVERY FAILURE. - -**Figure 9.2.1.2.2-1: API Discovery procedure, unsuccessful operation** - -If the Near-RT RIC platform rejects the request it shall respond with the API DISCOVERY FAILURE message with a proper cause. If the message contains the *Time to Wait* IE the xApp shall wait at least the indicated time before reinitiating the request to the Near-RT RIC platform. - -##### 9.2.1.2.3 Abnormal Conditions - -Not applicable. - -### 9.2.2 Enabl\_Events\_API Procedures - -#### 9.2.2.1 General - -The Enabl\_Events\_API allows an xApp to subscribe to and unsubscribe from events related to Near-RT RIC APIs and to receive notifications of the events. - -Such events includes: - -- Availability of Near-RT RIC API: event related to availability of Near-RT RIC APIs (e.g. active, inactive) -- Update of Near-RT RIC API: event related to change in Near-RT RIC API information - -The API procedures defined for the Enabl\_Events\_API are shown in table 9.2.2.1-1. - -**Table 9.2.2.1-1: Operations of the Enabl\_Events\_API** - -| API Procedure | Description | Initiated by | -|-------------------------------|-----------------------------------------------------------------------------------------------------------|----------------------| -| API Event Subscription | This procedure is used by xApp to subscribe for receiving Near-RT RIC API related events. | xApp | -| API Event Subscription Delete | This procedure is used by xApp to unsubscribe from receiving Near-RT RIC API related events. | xApp | -| API Event Notification | This procedure is used by Near-RT RIC to send a notification of Near-RT RIC API related event to an xApp. | Near-RT RIC platform | - -#### 9.2.2.2 API Event Subscription procedure - -##### 9.2.2.2.1 Successful Operation - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" - -xApp -> RICP : 1. API EVENT SUBSCRIPTION REQUEST - -``` - -``` -RICP -> xApp : 2. API EVENT SUBSCRIPTION RESPONSE -``` - -``` -@enduml -``` - -![Sequence diagram showing a successful API Event Subscription procedure between an xApp and the Near-RT RIC Platform.](142c0ec898fdb4803450dd39592136c5_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note over xApp: xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. API EVENT SUBSCRIPTION REQUEST - Near-RT RIC Platform->>xApp: 2. API EVENT SUBSCRIPTION RESPONSE - Note over xApp: xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram showing a successful API Event Subscription procedure between an xApp and the Near-RT RIC Platform. - -**Figure 9.2.2.2.1-1: API Event Subscription procedure, successful operation** - -To subscribe to Near-RT RIC API related events, the xApp shall send an API EVENT SUBSCRIPTION REQUEST message to the Near-RT RIC platform. The message shall include the *xApp ID* IE, the *List of Events* IE, the *Event Notification Requirements* IE and the *Notification Destination* IE. - -The xApp may also include additional event filter(s) in the *List of Event Filters* IE. Such event filters include: - -- API ID(s) in the *API ID Filter* IE, if the event type is NEAR\_RT\_RIC\_API\_AVAILABLE, NEAR\_RT\_RIC\_API\_UNAVAILABLE or NEAR\_RT\_RIC\_API\_UPDATE; - -Upon receiving the message, the API Enablement function shall: - -1. verify the identity of the xApp and check if the xApp is authorized to subscribe to the Near-RT RIC API related events specified in the request message; -2. if the xApp is authorized to subscribe to the Near-RT RIC API related events, the Near-RT RIC platform shall prepare necessary resource for the subscription and associated notifications, according to the contents in the *List of Events* IE and the *Event Notification Requirements* IE, and send an API EVENT SUBSCRIPTION RESPONSE message back to the xApp. The response message shall include the assigned subscription ID in the *Subscription ID* IE. - -##### 9.2.2.2.2 Unsuccessful Operation - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" - -xApp -> RICP : 1. API EVENT SUBSCRIPTION REQUEST -RICP -> xApp : 2. API EVENT SUBSCRIPTION FAILURE - -@enduml - -``` - -![Sequence diagram showing an unsuccessful API Event Subscription procedure where the Near-RT RIC Platform returns a failure message to the xApp.](377087fbf1dd0a11c3a435bcd7b6fc35_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note over xApp: xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. API EVENT SUBSCRIPTION REQUEST - Near-RT RIC Platform->>xApp: 2. API EVENT SUBSCRIPTION FAILURE - Note over xApp: xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram showing an unsuccessful API Event Subscription procedure where the Near-RT RIC Platform returns a failure message to the xApp. - -**Figure 9.2.2.2.2-1: API Event Subscription procedure, unsuccessful operation** - -If the Near-RT RIC platform rejects the request it shall respond with the API EVENT SUBSCRIPTION FAILURE message with proper cause. If the message contains *Time to Wait* IE the xApp shall wait at least the indicated time before reinitiating the request to the Near-RT RIC platform. - -##### 9.2.2.2.3 Abnormal conditions - -If the Near-RT RIC platform receives an API EVENT SUBSCRIPTION REQUEST message containing *Event Type* IE that is not supported by the Near-RT RIC platform, or the optional filter definition is invalid, the Near-RT RIC platform shall send the API EVENT SUBSCRIPTION FAILURE message to the xApp with an appropriate cause value. - -#### 9.2.2.3 API Event Subscription Delete procedure - -##### 9.2.2.3.1 Successful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" - -xApp -> RICP : 1. API EVENT SUBSCRIPTION DELETE REQUEST -RICP -> xApp : 2. API EVENT SUBSCRIPTION DELETE RESPONSE -@enduml -``` - -![Sequence diagram showing the successful API Event Subscription Delete procedure. The xApp sends a '1. API EVENT SUBSCRIPTION DELETE REQUEST' to the Near-RT RIC Platform, which responds with '2. API EVENT SUBSCRIPTION DELETE RESPONSE'.](878e3f080378afb04bb23d5863edc6a5_img.jpg) - -``` -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. API EVENT SUBSCRIPTION DELETE REQUEST - RICP-->>xApp: 2. API EVENT SUBSCRIPTION DELETE RESPONSE -``` - -Sequence diagram showing the successful API Event Subscription Delete procedure. The xApp sends a '1. API EVENT SUBSCRIPTION DELETE REQUEST' to the Near-RT RIC Platform, which responds with '2. API EVENT SUBSCRIPTION DELETE RESPONSE'. - -**Figure 9.2.2.3.1-1: API Event Subscription Delete procedure, successful operation** - -To unsubscribe from Near-RT RIC API related events, the xApp shall send an API EVENT SUBSCRIPTION DELETE REQUEST message to the Near-RT RIC platform with the *xApp ID* IE and the *Subscription ID* IE. - -Upon receiving the message, the Near-RT RIC platform shall: - -1. verify the identity of the xApp and check if the xApp is authorized to unsubscribe from the Near-RT RIC API related events associated with the subscription ID; and -2. if the xApp is authorized to unsubscribe from the Near-RT RIC API related events, the Near-RT RIC platform shall delete the resource for the subscription and reply API EVENT SUBSCRIPTION DELETE RESPONSE to the xApp. - -##### 9.2.2.3.2 Unsuccessful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -``` - -``` - -@startuml -xApp -> RICP : 1. API EVENT SUBSCRIPTION DELETE REQUEST -RICP -> xApp : 2. API EVENT SUBSCRIPTION DELETE FAILURE - -@enduml - -``` - -![Sequence diagram for API Event Subscription Delete procedure, unsuccessful operation.](6e9d059430baba0c363e33749f68b107_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - xApp->>RICP: 1. API EVENT SUBSCRIPTION DELETE REQUEST - RICP-->>xApp: 2. API EVENT SUBSCRIPTION DELETE FAILURE - -``` - -Sequence diagram for API Event Subscription Delete procedure, unsuccessful operation. - -**Figure 9.2.2.3.2-1: API Event Subscription Delete procedure, unsuccessful operation** - -If the Near-RT RIC platform rejects the request it shall respond with the API EVENT SUBSCRIPTION DELETE FAILURE message with proper cause. If the message contains *Time To Wait* IE the xApp shall wait at least the indicated time before reinitiating the request to the Near-RT RIC platform. - -##### **9.2.2.3.3 Abnormal conditions** - -Not applicable. - -#### **9.2.2.4 API Event Notification procedure** - -##### **9.2.2.4.1 Successful Operation** - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" - -RICP -> xApp : 1. API EVENT NOTIFICATION -RICP <-- xApp : 2. API EVENT NOTIFICATION ACK - -@enduml - -``` - -![Sequence diagram for API Event Notification procedure, successful operation.](43437211ce989e9da795fecc0d499c05_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - RICP->>xApp: 1. API EVENT NOTIFICATION - xApp-->>RICP: 2. API EVENT NOTIFICATION ACK - -``` - -Sequence diagram for API Event Notification procedure, successful operation. - -**Figure 9.2.2.4.1-1: API Event Notification procedure, successful operation** - -To notify a Near-RT RIC API related event, the Near-RT RIC platform shall send an API EVENT NOTIFICATION message using the *Notification Destination* IE received in the API Event Subscription procedure. - -The Near-RT RIC platform may include details of the event in the *Event Detail* IE. Such details include: - -- if the event type is Near-RT\_RIC\_API\_AVAILABLE or Near-RT\_RIC\_API\_UNAVAILABLE, the API IDs in the *List of API IDs* IE; - -- if the event is Near-RT\_RIC\_API\_UPDATE, the updated API information in the *List of API Information IE*; - -Upon receiving the message, the xApp may reply an API EVENT NOTIFICATION ACK message. - -##### **9.2.2.4.2 Unsuccessful Operation** - -Not applicable. - -##### **9.2.2.4.3 Abnormal conditions** - -Not applicable. - -### 9.2.3 Enabl\_Registration\_API Procedures - -#### 9.2.3.1 General - -The Enabl\_Registration\_API allows an xApp to register its service APIs with the Near-RT RIC platform. - -The API procedure defined for Enabl\_Registration\_API is shown in table 9.2.3.1-1. - -**Table 9.2.3.1-1: Procedure of the Enabl\_Discovery\_API** - -| API Procedure | Description | Initiated by | -|-------------------------|----------------------------------------------------------------------------------|--------------| -| API Registration | This procedure is used by an xApp to register its Near-RT RIC APIs. | xApp | -| API Registration Update | This procedure is used by an xApp to update its registered Near-RT RIC APIs. | xApp | -| API Deregistration | This procedure is used by an xApp to deregister its registered Near-RT RIC APIs. | xApp | - -#### 9.2.3.2 API Registration procedure - -##### 9.2.3.2.1 Successful Operation - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" - -xApp -> RICP : 1. API REGISTRATION REQUEST -RICP -> xApp : 2. API REGISTRATION RESPONSE - -@enduml - -``` - -![Sequence diagram showing the API Registration procedure. It features two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. API REGISTRATION REQUEST' message to the platform, and the platform responds with a '2. API REGISTRATION RESPONSE' message back to the xApp.](78c6bfdfef4d292384fc7667315392ab_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. API REGISTRATION REQUEST - RICP-->>xApp: 2. API REGISTRATION RESPONSE - -``` - -Sequence diagram showing the API Registration procedure. It features two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. API REGISTRATION REQUEST' message to the platform, and the platform responds with a '2. API REGISTRATION RESPONSE' message back to the xApp. - -**Figure 9.2.3.2.1-1: API Registration procedure, successful operation** - -To register Near-RT RIC APIs with the Near-RT RIC platform, the xApp shall send an API REGISTRATION REQUEST message. The message shall include: - -- the *List of API Information to Register* IE, which contain the API information of the Near-RT RIC APIs to be registered. - -Upon receiving the message, the Near-RT RIC platform shall verify the authorization of the xApp, assign an API ID for each successfully registered API, and store the associated API information. The Near-RT RIC platform shall reply with an API REGISTRATION RESPONSE message. The message shall include: - -- the *List of API Information Successfully Registered* IE, which contains the API information of the successfully registered APIs; -- the *List of API Information Failed To Register* IE if any API is not successfully registered, which contains the corresponding API information and cause. - -##### 9.2.3.2.2 Unsuccessful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" - -xApp ->> RICP : 1. API REGISTRATION REQUEST -RICP ->> xApp : 2. API REGISTRATION FAILURE - -@enduml -``` - -![Sequence diagram showing an unsuccessful API registration. The xApp sends a '1. API REGISTRATION REQUEST' to the Near-RT RIC Platform, which responds with '2. API REGISTRATION FAILURE'.](ad4da36431850ac19ba59bb74ec29dc9_img.jpg) - -``` -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. API REGISTRATION REQUEST - Near-RT RIC Platform-->>xApp: 2. API REGISTRATION FAILURE -``` - -Sequence diagram showing an unsuccessful API registration. The xApp sends a '1. API REGISTRATION REQUEST' to the Near-RT RIC Platform, which responds with '2. API REGISTRATION FAILURE'. - -Figure 9.2.3.2.2-1: API Registration procedure, unsuccessful operation - -If the Near-RT RIC platform rejects the request it shall respond with the API REGISTRATION FAILURE message. The message shall include the *List of API Information Failed To Register* IE, which contains the corresponding API information and cause. - -##### 9.2.3.2.3 Abnormal Conditions - -Not applicable. - -#### 9.2.3.3 API Registration Update procedure - -##### 9.2.3.3.1 Successful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -``` - -``` - -skinparam lifelineStrategy solid - -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" - -xApp -> RICP : 1. API REGISTRATION UPDATE REQUEST -RICP -> xApp : 2. API REGISTRATION UPDATE RESPONSE - -@enduml - -``` - -![Sequence diagram for successful API registration update. Lifelines: xApp and Near-RT RIC Platform. Message 1: API REGISTRATION UPDATE REQUEST from xApp to RICP. Message 2: API REGISTRATION UPDATE RESPONSE from RICP to xApp.](cc7baa8e5118f4b42c01166637c738ea_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. API REGISTRATION UPDATE REQUEST - RICP-->>xApp: 2. API REGISTRATION UPDATE RESPONSE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - -``` - -Sequence diagram for successful API registration update. Lifelines: xApp and Near-RT RIC Platform. Message 1: API REGISTRATION UPDATE REQUEST from xApp to RICP. Message 2: API REGISTRATION UPDATE RESPONSE from RICP to xApp. - -**Figure 9.2.3.3.1-1: API Registration Update procedure, successful operation** - -To update its Near-RT RIC APIs that have been registered at the Near-RT RIC platform, the xApp shall send an API REGISTRATION UPDATE REQUEST message. The message shall include: - -- the *List of API Information to Update IE*, which contain the API information of the Near-RT RIC APIs to be updated. - -Upon receiving the message, the Near-RT RIC platform shall verify the authorization of the xApp, and update the stored API information with the new API information associated with the same API ID. The Near-RT RIC platform shall reply with an API REGISTRATION UPDATE RESPONSE message. The message shall include: - -- the *List of API IDs Successfully Updated IE*, which contains the API IDs of the successfully updated APIs; -- the *List of API IDs Failed To Update IE* if any API is not successfully updated, which contains the corresponding API ID and cause. - -##### 9.2.3.3.2 Unsuccessful Operation - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" - -xApp -> RICP : 1. API REGISTRATION UPDATE REQUEST -RICP -> xApp : 2. API REGISTRATION UPDATE FAILURE - -@enduml - -``` - -![Sequence diagram for unsuccessful API registration update. Lifelines: xApp and Near-RT RIC Platform. Message 1: API REGISTRATION UPDATE REQUEST from xApp to RICP. Message 2: API REGISTRATION UPDATE FAILURE from RICP to xApp.](58b03f2cf75e3ec5b30e05d6002ceb20_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. API REGISTRATION UPDATE REQUEST - RICP-->>xApp: 2. API REGISTRATION UPDATE FAILURE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - -``` - -Sequence diagram for unsuccessful API registration update. Lifelines: xApp and Near-RT RIC Platform. Message 1: API REGISTRATION UPDATE REQUEST from xApp to RICP. Message 2: API REGISTRATION UPDATE FAILURE from RICP to xApp. - -**Figure 9.2.3.3.2-1: API Registration Update procedure, unsuccessful operation** - -If the Near-RT RIC platform rejects the request it shall respond with the API REGISTRATION UPDATE FAILURE message. The message shall include the *List of API IDs Failed To Update* IE, which contains the API IDs that are not updated and the corresponding cause. - -##### **9.2.3.3.3 Abnormal Conditions** - -Not applicable. - -#### **9.2.3.4 API Deregistration procedure** - -##### **9.2.3.4.1 Successful Operation** - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" - -xApp -> RICP : 1. API DEREGISTRATION REQUEST -RICP -> xApp : 2. API DEREGISTRATION RESPONSE - -@enduml -``` - -![Sequence diagram for API Deregistration procedure, successful operation. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. API DEREGISTRATION REQUEST' message to the Near-RT RIC Platform. The Near-RT RIC Platform responds with a '2. API DEREGISTRATION RESPONSE' message back to the xApp.](1bd6a020aa71784ed74367899560cbb9_img.jpg) - -``` -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. API DEREGISTRATION REQUEST - RICP-->>xApp: 2. API DEREGISTRATION RESPONSE -``` - -Sequence diagram for API Deregistration procedure, successful operation. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. API DEREGISTRATION REQUEST' message to the Near-RT RIC Platform. The Near-RT RIC Platform responds with a '2. API DEREGISTRATION RESPONSE' message back to the xApp. - -**Figure 9.2.3.4.1-1: API Deregistration procedure, successful operation** - -To deregister its Near-RT RIC APIs from the Near-RT RIC platform, the xApp shall send an API DEREGISTRATION REQUEST message. The message shall include the *List of API IDs To Deregister* IE which indicates the API IDs of the APIs to be deregistered. - -Upon receiving the message, the Near-RT RIC platform shall verify the authorization of the xApp, and delete the stored API information associated with the API IDs in the request. The Near-RT RIC platform shall reply with an API DEREGISTRATION RESPONSE message. The message shall include: - -- the *List of API IDs Successfully Deregistered* IE, which contains the API IDs of the successfully deregistered APIs; -- the *List of API IDs Failed To Deregister* IE if any API is not successfully deregistered, which contains the corresponding API IDs and cause. - -##### **9.2.3.4.2 Unsuccessful Operation** - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -``` - -Participant xApp as "xApp" - Participant RICP as "Near-RT RIC Platform" - -xApp -> RICP : 1. API DEREGISTRATION REQUEST - RICP -> xApp : 2. API DEREGISTRATION FAILURE - -@enduml - -![Sequence diagram showing an unsuccessful API deregistration procedure. An xApp sends a '1. API DEREGISTRATION REQUEST' to a 'Near-RT RIC Platform', which responds with '2. API DEREGISTRATION FAILURE'.](67a1dd734d3de6e31754caf85d6fe77f_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. API DEREGISTRATION REQUEST - Near-RT RIC Platform-->>xApp: 2. API DEREGISTRATION FAILURE - -``` - -Sequence diagram showing an unsuccessful API deregistration procedure. An xApp sends a '1. API DEREGISTRATION REQUEST' to a 'Near-RT RIC Platform', which responds with '2. API DEREGISTRATION FAILURE'. - -**Figure 9.2.3.4.2-1: API Deregistration procedure, unsuccessful operation** - -If the Near-RT RIC platform rejects the request it shall respond with the API DEREGISTRATION FAILURE message. The message shall include the *List of API IDs Failed To Deregister* IE, which contains the API IDs that are not deregistered and the corresponding cause. - -##### **9.2.3.4.3 Abnormal Conditions** - -Not applicable. - -## 9.3 Elements for Enablement API Communication - -### 9.3.1 General - -### 9.3.2 Message Functional Definition and Content - -#### 9.3.2.1 API DISCOVERY REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to discover the available Near-RT RIC APIs. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9.3.3.1 | | -| xApp ID | M | | 10.1.2 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Query Parameters | | 0..1 | | | -| >API Name | O | | 9.3.3.6 | | -| >API Version | O | | 9.3.3.7 | | -| >Protocol | O | | 9.3.3.8 | | -| >Data Format | O | | 9.3.3.9 | | -| >API Category | O | | 9.3.3.10 | | - -#### 9.3.2.2 API DISCOVERY RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to carry the information of discovered Near-RT RIC APIs. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|----------------------------------------|-----------------------|----------------------------------------------------------------------| -| Message Type | M | | 9.3.3.1 | | -| xApp ID | M | | 10.1.2 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| List of API Information | | 0..
fAPIInfor
mation> | | Description of the Near-RT RIC APIs as published by the provider(s). | -| >API Information | M | | 9.3.3.2 | | - -| Range bound | Explanation | -|-----------------------|----------------------------------------------------------------------------------| -| maxnoofAPIInformation | Maximum no. of API information items supported in an API list.
Value is 1024. | - -#### 9.3.2.3 API DISCOVERY FAILURE - -This message is sent by Near-RT RIC platform to the xApp for the case of failure of the discovery of the available near-RT RIC APIs. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9.3.3.1 | | -| xApp ID | M | | 10.1.2 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Cause | M | | 9.3.3.4 | | -| Time to Wait | O | | 9.3.3.5 | | - -#### 9.3.2.4 API EVENT SUBSCRIPTION REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to subscribe for events related to Near-RT RIC APIs. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|----------------------------------------|-----------------------|----------------------------------------------------------------------------------| -| Message Type | M | | 9.3.3.1 | | -| xApp ID | M | | 10.1.2 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| List of Events | | 1..
fAPIEven
tFilter> | | | -| >Event Type | M | | 9.3.3.13 | | -| >API ID Filter | | 0..
fAPIIDFili
ters> | | API identifiers that the event subscriber wants to know in the interested event. | - -| | | | | | -|---------------------------------|---|---|--------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------| -| >>API ID | M | | 9.3.3.11 | | -| Event Notification Requirements | | 1 | | Represents the reporting requirements of the event subscription. | -| >Notification Method | M | | ENUMERATED (On Event, Periodic, ...) | | -| >Notification Period | O | | INTEGER (1.. 300, ...) | The duration between notifications expressed in unit of second. Shall be present when the Notification Method IE is set to " Periodic". | -| Notification Destination | M | | 10.1.9 | | - -| Range bound | Explanation | -|-----------------------|----------------------------------------------------------------------| -| maxnoofAPIEventFilter | Maximum no. of API event filters supported in the list. Value is 64. | -| maxnoofAPIIDFilters | Maximum no. of API ID filters supported in the list. Value is 1024. | - -#### 9.3.2.5 API EVENT SUBSCRIPTION RESPONSE - -This message is sent by Near-RT RIC platform to the xApp as successful response to API event subscription request. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9.3.3.1 | | -| xApp ID | M | | 10.1.2 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Subscription ID | M | | 9.3.3.3 | | - -#### 9.3.2.6 API EVENT SUBSCRIPTION FAILURE - -This message is sent by Near-RT RIC platform to the xApp for the case of failure of the API event subscription request. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9.3.3.1 | | -| xApp ID | M | | 10.1.2 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Cause | M | | 9.3.3.4 | | -| Time to Wait | O | | 9.3.3.5 | | - -#### 9.3.2.7 API EVENT SUBSCRIPTION DELETE REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to unsubscribe for events related to Near-RT RIC APIs. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9.3.3.1 | | -| xApp ID | M | | 10.1.2 | | -| Procedure Transaction ID | M | | 10.1.1 | | - -| | | | | | -|-----------------|---|--|---------|--| -| Subscription ID | M | | 9.3.3.3 | | -|-----------------|---|--|---------|--| - -#### 9.3.2.8 API EVENT SUBSCRIPTION DELETE RESPONSE - -This message is sent by Near-RT RIC platform to the xApp as successful response to API event subscription delete request. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9.3.3.1 | | -| xApp ID | M | | 10.1.2 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Subscription ID | M | | 9.3.3.3 | | - -#### 9.3.2.9 API EVENT SUBSCRIPTION DELETE FAILURE - -This message is sent by Near-RT RIC platform to the xApp for the case of failure of the API event subscription delete request. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9.3.3.1 | | -| xApp ID | M | | 10.1.2 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Cause | M | | 9.3.3.4 | | -| Time to Wait | O | | 9.3.3.5 | | - -#### 9.3.2.10 API EVENT NOTIFICATION - -This message is sent to a subscriber xApp from the Near-RT RIC platform to notify on an API event (based on subscription). - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|------------------------------------|-----------------------|--------------------------------------------------------------------| -| Message Type | M | | 9.3.3.1 | | -| Subscription ID | M | | 9.3.3.4 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Event Type | M | | 9.3.3.13 | | -| Event Detail | | 0.. 1 | | | -| >List of API IDs | | 0..
fAPIIDs> | | The API IDs which are available/unavailable in the relevant event. | -| >>API ID | M | | 9.3.3.11 | | -| >List of API Information | | 0..
fAPIInformation> | | Description of the Near-RT RIC APIs which are to be updated. | -| >>API Information | M | | 9.3.3.2 | | - -| Range bound | Explanation | -|-----------------------|-------------------------------------------------------------------------------| -| maxnoofAPIIDs | Maximum no. of API IDs supported in an API list. Value is 1024. | -| maxnoofAPIInformation | Maximum no. of API information items supported in an API list. Value is 1024. | - -#### 9.3.2.11 API EVENT NOTIFICATION ACK - -This message is optionally sent by the xApp to Near-RT RIC platform as acknowledgement to an API event notification. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9.3.3.1 | | -| Subscription ID | M | | 9.3.3.3 | | -| Procedure Transaction ID | M | | 10.1.1 | | - -#### 9.3.2.12 API REGISTRATION REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to register its Near-RT RIC APIs. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------------------------|----------|----------------------------------------|-----------------------|-----------------------| -| Message Type | M | | 9.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| List of API Information To Register | | 1..oofAPIInf
ormation
> | | | -| > API Information | M | | 9.3.3.2 | | - -| Range bound | Explanation | -|-----------------------|-------------------------------------------------------------------------------| -| maxnoofAPIInformation | Maximum no. of API information items supported in an API list. Value is 1024. | - -#### 9.3.2.13 API REGISTRATION RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to indicate success of the registration of Near-RT RIC APIs. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------------------------------------|----------|----------------------------------------|-----------------------|------------------------------------------| -| Message Type | M | | 9.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| List of API Information Successfully Registered | | 1..oofAPIInf
ormation
> | | The list of successfully registered APIs | -| >API Information | M | | 9.3.3.2 | | - -| | | | | | -|--------------------------------------------|---|----------------------------|---------|-------------------------------------------------------| -| List of API Information Failed To Register | | 0.. | | The list of APIs that are not successfully registered | -| >API Information | M | | 9.3.3.2 | | -| >Cause | M | | 9.3.3.4 | | - -| Range bound | Explanation | -|-----------------------|-------------------------------------------------------------------------------| -| maxnoofAPIInformation | Maximum no. of API information items supported in an API list. Value is 1024. | - -#### 9.3.2.14 API REGISTRATION FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of the registration of Near-RT RIC APIs. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------------------------|----------|----------------------------|-----------------------|--------------------------------------------------------| -| Message Type | M | | 9.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| List of API Information Failed To Register | | 1.. | | The list of APIs that are not successfully registered. | -| > API Information | M | | 9.3.3.2 | | -| > Cause | M | | 9.3.3.4 | | - -| Range bound | Explanation | -|-----------------------|-------------------------------------------------------------------------------| -| maxnoofAPIInformation | Maximum no. of API information items supported in an API list. Value is 1024. | - -#### 9.3.2.15 API REGISTRATION UPDATE REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to update its registered Near-RT RIC APIs. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-----------------------------------|----------|----------------------------|-----------------------|-----------------------| -| Message Type | M | | 9.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| List of API Information To Update | | 1.. | | | -| > API Information | M | | 9.3.3.2 | | - -| Range bound | Explanation | -|-----------------------|-------------------------------------------------------------------------------| -| maxnoofAPIInformation | Maximum no. of API information items supported in an API list. Value is 1024. | - -#### 9.3.2.16 API REGISTRATION UPDATE RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to indicate success of the registration of Near-RT RIC APIs. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------------------|----------|--------------------|-----------------------|-----------------------------------------------------| -| Message Type | M | | 9.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| List of API IDs Successfully Updated | | 1.. | | The list of successfully updated APIs | -| >API ID | M | | 9.3.3.11 | | -| List of API IDs Failed To Update | | 0.. | | The list of APIs that are not successfully updated. | -| >API ID | M | | 9.3.3.11 | | -| >Cause | M | | 9.3.3.4 | | - -| Range bound | Explanation | -|---------------|-----------------------------------------------------------------| -| maxnoofAPIIDs | Maximum no. of API IDs supported in an API list. Value is 1024. | - -#### 9.3.2.17 API REGISTRATION UPDATE FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of the registration of Near-RT RIC APIs. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|----------------------------------|----------|--------------------|-----------------------|-----------------------------------------------------| -| Message Type | M | | 9.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| List of API IDs Failed to Update | | 1.. | | The list of APIs that are not successfully updated. | -| > API ID | M | | 9.3.3.11 | | -| > Cause | M | | 9.3.3.4 | | - -| Range bound | Explanation | -|---------------|-----------------------------------------------------------------| -| maxnoofAPIIDs | Maximum no. of API IDs supported in an API list. Value is 1024. | - -#### 9.3.2.18 API DEREGISTRATION REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to deregister its Near-RT RIC APIs. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | - -| | | | | | -|-------------------------------|---|------------------------|----------|--| -| List of API IDs To Deregister | | 1..oofAPIIDs> | | | -| > API ID | M | | 9.3.3.11 | | - -| Range bound | Explanation | -|---------------|-----------------------------------------------------------------| -| maxnoofAPIIDs | Maximum no. of API IDs supported in an API list. Value is 1024. | - -#### 9.3.2.19 API DEREGISTRATION RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to indicate success of the deregistration of Near-RT RIC APIs. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------------------------------|----------|------------------------|-----------------------|---------------------------------------------------------| -| Message Type | M | | 9.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| List of API IDs Successfully Deregistered | | 1..oofAPIIDs> | | The list of successfully deregistered APIs | -| >API ID | M | | 9.3.3.11 | | -| List of API IDs Failed To Deregister | | 0..oofAPIIDs> | | The list of APIs that are not successfully deregistered | -| >API ID | M | | 9.3.3.11 | | -| >Cause | M | | 9.3.3.4 | | - -| Range bound | Explanation | -|---------------|-----------------------------------------------------------------| -| maxnoofAPIIDs | Maximum no. of API IDs supported in an API list. Value is 1024. | - -#### 9.3.2.20 API DEREGISTRATION FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of the deregistration of Near-RT RIC APIs. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------------------|----------|----------------------------------------|-----------------------|----------------------------------------------------------| -| Message Type | M | | 9.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| List of API IDs Failed To Deregister | | 1..oofAPIInf
ormation
> | | The list of APIs that are not successfully deregistered. | -| > API ID | M | | 9.3.3.11 | | -| > Cause | M | | 9.3.3.4 | | - -| Range bound | Explanation | -|---------------|-----------------------------------------------------------------| -| maxnoofAPIIDs | Maximum no. of API IDs supported in an API list. Value is 1024. | - -### 9.3.3 Information Element Definitions - -#### 9.3.3.1 Message Type - -This IE identifies the message being sent. It is mandatory for all messages. - -| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | -|------------------|----------|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------| -| Message Type | | | | | -| >Procedure Type | M | | CHOICE (API Discovery, API Event Subscription, API Event Subscription Delete, API Event Notification, API Registration, API Registration Update, API Deregistration, ...) | | -| >Type of Message | M | | CHOICE (Request, Response, Failure, ...) | Refer to Table 9.1.2-3 for applicable choices for each procedure type | - -#### 9.3.3.2 API Information - -This IE indicates the information of a Near-RT RIC API. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------------------|----------|--------------------------------|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| API Name | M | | 9.3.3.6 | | -| API ID | C | | 9.3.3.11 | Assigned by the Near-RT RIC platform. Shall be present when the API Information is associated with a registered API, or used to update a registered API. | -| API Category | M | | 9.3.3.10 | | -| Description | O | | STRING | Text description of the API | -| List of API Profiles | | 1..
| | | -| >API Version | M | | 9.3.3.7 | | -| >Protocol | O | | 9.3.3.8 | | -| >Data Format | O | | 9.3.3.9 | | -| >Endpoint Information | O | | 10.1.9 | | -| >List of Supported Data Types | | 0.. | | Shall be present for SDL APIs. When used in the API DISCOVERY RESPONSE message or the API EVENT NOTIFICATION message, it contains the supported SDL Data Types that the xApp is allowed to access. | -| >> Data Type ID | M | | STRING | For the API information of SDL APIs, this IE is populated with the SDL Data Type ID specified in clause 7.3.3.21. | - -| Range bound | Explanation | -|---------------------------|-----------------------------------------------------------------------| -| maxnoofSupportedDataTypes | Maximum no. of supported data types in an API profile. Value is 1024. | -| maxnoofAPIProfiles | Maximum no. of API profiles. Value is 256. | - -#### 9.3.3.3 Subscription ID - -The IE uniquely identifies a subscription to API-related event(s). - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-----------------|----------|-------|-----------------------|------------------------------------------------------------------------------| -| Subscription ID | M | | STRING | Identifier of the subscription resource to which the notification is related | - -#### 9.3.3.4 Cause - -This IE is used to indicate the reason for a particular event for the Enablement APIs. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|----------------------------------------------------------------------------------------------------------------------------------|-----------------------| -| Cause | M | | ENUMERATED (Unspecified, System busy, Duplicate API Information, Unknown API ID, Invalid Data Type, Unknown Subscription ID,...) | | - -The meaning of the different cause values is described in the following table. - -| Cause value | Meaning | -|---------------------------|------------------------------------------------------------------| -| Unspecified | Sent when none of the below cause values applies. | -| System busy | The system cannot process the request due to temporary overload. | -| Duplicate API Information | The same API information has been registered. | -| Unknown API ID | The API ID is unknown. | -| Invalid Data Type | The supported data type in the API information is invalid. | -| Unknown Subscription ID | The Subscription ID for API event is unknown. | - -#### 9.3.3.5 Time to Wait - -This IE specifies the time that xApp shall wait before reinitiating a request. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|------------------------|-----------------------| -| Time to Wait | M | | INTEGER (1.. 300, ...) | Unit in second | - -#### 9.3.3.6 API Name - -Defined in 10.1.3. - -#### 9.3.3.7 API Version - -Defined in 10.1.4. - -#### 9.3.3.8 Protocol - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------------------------|--------------------------------------| -| Protocol | M | | ENUMERATED (gRPC, SCTP, HTTP REST, ...) | Protocol used by the Near-RT RIC API | - -#### 9.3.3.9 Data Format - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|---------------------------------------|-----------------------------------------| -| Data Format | M | | ENUMERATED (Proto3, JSON, ASN.1, ...) | Data format used by the Near-RT RIC API | - -#### 9.3.3.10 API Category - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|--------------------------------------------------------------|-------------------------------------------------------| -| API Category | M | | ENUMERATED (E2 related APIs, SDL APIs, A1 related APIs, ...) | The Near-RT RIC API category to which the API belongs | - -#### 9.3.3.11 API ID - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------| -| API ID | M | | STRING | API identifier assigned by the Near-RT RIC platform to the published Near-RT RIC API | - -#### 9.3.3.12 Void - -#### 9.3.3.13 Event Type - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|--------------------------------------------------------------------------------------------------------------|-----------------------| -| Event Type | M | | ENUMERATED
(NEAR_RT_RIC_API_AVAILABLE,
NEAR_RT_RIC_API_UNAVAILABLE,
NEAR_RT_RIC_API_UPDATE,
...) | | - -**Table 9.3.3.13-1: Meaning of Event Types** - -| value | Description | -|-----------------------------|------------------------------------------------------------------------------| -| NEAR_RT_RIC_API_AVAILABLE | Events related to the availability of APIs after the APIs are published. | -| NEAR_RT_RIC_API_UNAVAILABLE | Events related to the unavailability of APIs after the APIs are unpublished. | -| NEAR_RT_RIC_API_UPDATE | Events related to change in API information | - -### 9.3.4 Message and Information Element Abstract Syntax - -#### 9.3.4.1 Solution 1: gRPC with Protocol Buffers - -##### 9.3.4.1.1 Usage of gRPC with Protocol Buffers - -This solution uses Protocol Buffers as message encoding, and also as the Interface Definition Language (IDL) for gRPC [5]. - -Table 9.3.4.1.1-1 lists the mapping of enablement APIs and corresponding gRPC services. - -**Table 9.3.4.1.1-1: Mapping of enablement APIs and gRPC services** - -| API Name | gRPC service(s) | -|------------------------|-------------------------------------------------| -| Enabl_Discovery_API | Enabl_Discovery_API | -| Enabl_Events_API | Enabl_Events_API, Enabl_Events_API_Notification | -| Enabl_Registration_API | Enabl_Registration_API | - -A procedure of an Enablement API is mapped to a *gRPC method*. - -Table 9.3.4.1.1-2 lists the Enablement APIs abstract syntax included in this document. - -**Table 9.3.4.1.1-2: List of Enbalement APIs abstract syntax** - -| API Name / Contents | Clause | Version | File Name | -|---------------------------------------------|-------------|---------|---------------------------------------------| -| Enabl_Discovery_API | 9.3.4.1.2.1 | 2.0.0 | enabl_discovery_api_ver_2_0_0.proto | -| Enabl_Events_API | 9.3.4.1.2.2 | 2.0.0 | enabl_events_api_ver_2_0_0.proto | -| Enabl_Registration_API | 9.3.4.1.2.3 | 1.0.0 | enabl_registration_api_ver_1_0_0.proto | -| Enablement API common information elements | 9.3.4.1.3 | 2.0.0 | enabl_apis_common_ies_ver_2_0_0.proto | -| Near-RT RIC API common information elements | 10.2.1 | 2.0.0 | near_rt_ric_apis_common_ies_ver_3_0_0.proto | - -##### 9.3.4.1.2 API Definitions - -###### 9.3.4.1.2.1 Enabl\_Discovery\_API - -``` - -syntax = "proto3"; - -package ricapi.enabl_discovery_api.v2; - -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; -import "enabl_apis_common_ies_ver_2_0_0.proto"; - -// gRPC service and rpc definition -service Enabl_Discovery_API { - rpc ApiDiscoveryProc(ApiDiscoveryInitMsg) returns (ApiDiscoveryOutMsg) {}; -} - -message ApiDiscoveryInitMsg { - optional ApiDiscoveryRequest api_discovery_request = 1; -} - -message ApiDiscoveryOutMsg { - oneof type_of_message { - ApiDiscoveryResponse api_discovery_response = 1; - ApiDiscoveryFailure api_discovery_failure = 2; - } -} - -// ----- messages of Enabl_Discovery_API ----- -// ----- messages of API Discovery procedure ----- -message ApiDiscoveryRequest { - optional near_rt_ric_apis_common_ies.v3.XappId xapp_id = 1; - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 3; - optional QueryParameters qps = 2; - - message QueryParameters { - optional near_rt_ric_apis_common_ies.v3.ApiName api_name = 1; - optional near_rt_ric_apis_common_ies.v3.ApiVersion api_version = 2; - optional enabl_apis_common_ies.v2.Protocol protocol = 3; - optional enabl_apis_common_ies.v2.DataFormat data_format = 4; - optional enabl_apis_common_ies.v2.ApiCategory api_category = 5; - }; -}; - -``` - -``` - -message ApiDiscoveryResponse { - optional near_rt_ric_apis_common_ies.v3.XappId xapp_id = 1; - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 3; - repeated enabl_apis_common_ies.v2.ApiInformation list_of_api_information = 2; -}; - -message ApiDiscoveryFailure { - optional near_rt_ric_apis_common_ies.v3.XappId xapp_id = 1; - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 4; - optional enabl_apis_common_ies.v2.Cause cause = 2; - optional uint32 time_to_wait = 3; -}; - -``` - -###### 9.3.4.1.2.2 - -###### Enabl\_Events\_API - -``` - -syntax = "proto3"; - -package ricapi.enabl_events_api.v2; - -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; -import "enabl_apis_common_ies_ver_2_0_0.proto"; - -// gRPC service and rpc definition -service Enabl_Events_API { - rpc ApiEventSubscriptionProc(ApiEventSubscriptionInitMsg) returns (ApiEventSubscriptionOutMsg) {}; - rpc ApiEventSubscriptionDeleteProc(ApiEventSubscriptionDeleteInitMsg) returns (ApiEventSubscriptionDeleteOutMsg) {}; -} - -message ApiEventSubscriptionInitMsg { - optional ApiEventSubscriptionRequest api_event_subscription_request = 1; -} - -message ApiEventSubscriptionOutMsg { - oneof type_of_message { - ApiEventSubscriptionResponse api_event_subscription_response = 1; - ApiEventSubscriptionFailure api_event_subscription_failure = 2; - } -} - -message ApiEventSubscriptionDeleteInitMsg { - optional ApiEventSubscriptionDeleteRequest api_event_subscription_delete_request = 1; -} - -message ApiEventSubscriptionDeleteOutMsg { - oneof type_of_message { - ApiEventSubscriptionDeleteResponse api_event_subscription_delete_response = 1; - ApiEventSubscriptionDeleteFailure api_event_subscription_delete_failure = 2; - } -} - -service Enabl_Events_API_Notification { - rpc ApiEventNotificationProc(ApiEventNotificationInitMsg) returns (ApiEventNotificationOutMsg) {}; -} - -message ApiEventNotificationInitMsg { - optional ApiEventNotification api_event_notification = 1; -} - -message ApiEventNotificationOutMsg { - oneof type_of_message { - ApiEventNotificationACK api_event_notification_ack = 1; - } -} - -// ----- messages of Enabl_Events_API ----- -// ----- messages of API Event Subscription procedure ----- -message ApiEventSubscriptionRequest { - optional near_rt_ric_apis_common_ies.v3.XappId xapp_id = 1; -} - -``` - -``` - -optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 5; -repeated EventItem list_of_events = 2; -optional EventNotificationRequirements event_notification_requirements = 3; -optional near_rt_ric_apis_common_ies.v3.EndpointInformation notification_destination = 4; - -message EventItem { - optional enabl_apis_common_ies.v2.EventType event_type = 1; - repeated ApiIdFilterItem api_id_filter = 2; - - message ApiIdFilterItem { - optional enabl_apis_common_ies.v2.ApiId api_id = 1; - } -} - -message EventNotificationRequirements { - optional NotificationMethod notification_method = 1; - optional uint32 notification_period = 2; - - enum NotificationMethod { - NOTIFICATION_METHOD_ON_EVENT = 0; - NOTIFICATION_METHOD_PERIODIC = 1; - } -} - -message ApiEventSubscriptionResponse { - optional near_rt_ric_apis_common_ies.v3.XappId xapp_id = 1; - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 3; - optional enabl_apis_common_ies.v2.SubscriptionId subscription_id = 2; -} - -message ApiEventSubscriptionFailure { - optional near_rt_ric_apis_common_ies.v3.XappId xapp_id = 1; - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 4; - optional enabl_apis_common_ies.v2.Cause cause = 2; - optional uint32 time_to_wait = 3; -} - -// ----- messages of API Event Subscription Delete procedure ----- -message ApiEventSubscriptionDeleteRequest { - optional near_rt_ric_apis_common_ies.v3.XappId xapp_id = 1; - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 3; - optional enabl_apis_common_ies.v2.SubscriptionId subscription_id = 2; -}; - -message ApiEventSubscriptionDeleteResponse { - optional near_rt_ric_apis_common_ies.v3.XappId xapp_id = 1; - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 3; - optional enabl_apis_common_ies.v2.SubscriptionId subscription_id = 2; -} - -message ApiEventSubscriptionDeleteFailure { - optional near_rt_ric_apis_common_ies.v3.XappId xapp_id = 1; - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 4; - optional enabl_apis_common_ies.v2.Cause cause = 2; - optional uint32 time_to_wait = 3; -} - -// ----- messages of API Event Notification procedure ----- -message ApiEventNotification { - optional enabl_apis_common_ies.v2.SubscriptionId subscription_id = 1; - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 4; - optional enabl_apis_common_ies.v2.EventType event_type = 2; - optional EventDetail event_detail = 3; - - message EventDetail { - repeated enabl_apis_common_ies.v2.ApiId list_of_api_ids = 1; - repeated enabl_apis_common_ies.v2.ApiInformation list_of_api_information = 2; - }; -}; - -message ApiEventNotificationACK { - optional enabl_apis_common_ies.v2.SubscriptionId subscription_id = 1; -} - -``` - -``` - -optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 2; -}; - -``` - -###### 9.3.4.1.2.3 - -###### Enabl\_Registration\_API - -``` - -syntax = "proto3"; - -package ricapi.enabl_registration_api_v1; - -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; -import "enabl_apis_common_ies_ver_2_0_0.proto"; - -// gRPC service and rpc definition -service Enabl_Registration_API { - rpc ApiRegistrationProc(ApiRegistrationInitMsg) returns (ApiRegistrationOutMsg) {}; - rpc ApiRegistrationUpdateProc(ApiRegistrationUpdateInitMsg) returns (ApiRegistrationUpdateOutMsg) {}; - rpc ApiDeregistrationProc(ApiDeregistrationInitMsg) returns (ApiDeregistrationOutMsg) {}; -} - -message ApiRegistrationInitMsg { - optional ApiRegistrationRequest api_registration_request = 1; -} - -message ApiRegistrationOutMsg { - oneof type_of_message { - ApiRegistrationResponse api_registration_response = 1; - ApiRegistrationFailure api_registration_failure = 2; - } -} - -message ApiRegistrationUpdateInitMsg { - optional ApiRegistrationUpdateRequest api_registration_update_request = 1; -} - -message ApiRegistrationUpdateOutMsg { - oneof type_of_message { - ApiRegistrationUpdateResponse api_registration_update_response = 1; - ApiRegistrationUpdateFailure api_registration_update_failure = 2; - } -} - -message ApiDeregistrationInitMsg { - optional ApiDeregistrationRequest api_deregistration_request = 1; -} - -message ApiDeregistrationOutMsg { - oneof type_of_message { - ApiDeregistrationResponse api_deregistration_response = 1; - ApiDeregistrationFailure api_deregistration_failure = 2; - } -} - -// ----- messages of Enabl_Registration_API ----- -// ----- messages of API Registration procedure ----- -message ApiRegistrationRequest { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - repeated ApiInformationToRegisterItem list_of_api_information_to_register = 2; - - message ApiInformationToRegisterItem { - optional enabl_apis_common_ies.v2.ApiInformation api_information = 1; - } -} - -message ApiRegistrationResponse { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - repeated ApiInformationSuccessfullyRegisteredItem list_of_api_information_successfully_registered = 2; - repeated ApiInformationFailedToRegisterItem list_of_api_information_failed_to_register = 3; - - message ApiInformationSuccessfullyRegisteredItem { - optional enabl_apis_common_ies.v2.ApiInformation api_information = 1; - } -} - -``` - -``` - - } - - message ApiInformationFailedToRegisterItem { - optional enabl_apis_common_ies.v2.ApiInformation api_information = 1; - optional enabl_apis_common_ies.v2.Cause cause = 2; - } -} - -message ApiRegistrationFailure { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - repeated ApiInformationFailedToRegisterItem list_of_api_information_failed_to_register = 2; - - message ApiInformationFailedToRegisterItem { - optional enabl_apis_common_ies.v2.ApiInformation api_information = 1; - optional enabl_apis_common_ies.v2.Cause cause = 2; - } -} - -// ----- messages of API Registration Update procedure ----- -message ApiRegistrationUpdateRequest { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - repeated ApiInformationToUpdateItem list_of_api_information_to_update = 2; - - message ApiInformationToUpdateItem { - optional enabl_apis_common_ies.v2.ApiInformation api_information = 1; - } -} - -message ApiRegistrationUpdateResponse { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - repeated ApiIdSuccessfullyUpdatedItem list_of_api_ids_successfully_updated = 2; - repeated ApiIdFailedToUpdateItem list_of_api_ids_failed_to_update = 3; - - message ApiIdSuccessfullyUpdatedItem { - optional enabl_apis_common_ies.v2.ApiId api_id = 1; - } - - message ApiIdFailedToUpdateItem { - optional enabl_apis_common_ies.v2.ApiId api_id = 1; - optional enabl_apis_common_ies.v2.Cause cause = 2; - } -} - -message ApiRegistrationUpdateFailure { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - repeated ApiIdFailedToUpdateItem list_of_api_ids_failed_to_update = 2; - - message ApiIdFailedToUpdateItem { - optional enabl_apis_common_ies.v2.ApiId api_id = 1; - optional enabl_apis_common_ies.v2.Cause cause = 2; - } -} - -// ----- messages of API Deregistration procedure ----- -message ApiDeregistrationRequest { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - repeated ApiIdToDeregisterItem list_of_api_ids_to_deregister = 2; - - message ApiIdToDeregisterItem { - optional enabl_apis_common_ies.v2.ApiId api_id = 1; - } -} - -message ApiDeregistrationResponse { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - repeated ApiIdSuccessfullyDeregisteredItem list_of_api_ids_successfully_deregistered = 2; - repeated ApiIdFailedToDeregisterItem list_of_api_ids_failed_to_deregister = 3; - - message ApiIdSuccessfullyDeregisteredItem { - optional enabl_apis_common_ies.v2.ApiId api_id = 1; - } - - message ApiIdFailedToDeregisterItem { - -``` - -``` - - optional enabl_apis_common_ies.v2.ApiId api_id = 1; - optional enabl_apis_common_ies.v2.Cause cause = 2; - } -} - -message ApiDeregistrationFailure { - optional near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - repeated ApiIdFailedToDeregisterItem list_of_api_ids_failed_to_deregister = 2; - - message ApiIdFailedToDeregisterItem { - optional enabl_apis_common_ies.v2.ApiId api_id = 1; - optional enabl_apis_common_ies.v2.Cause cause = 2; - } -} - -``` - -##### 9.3.4.1.3 Information Element Definitions - -``` - -syntax = "proto3"; - -package ricapi.enabl_apis_common_ies.v2; - -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; - -// ----- Information Elements ----- -// -----A----- -enum ApiCategory { - APICATEGORY_E2_RELATED = 0; - APICATEGORY_SDL = 1; - APICATEGORY_A1_RELATED = 2; -}; - -message ApiId { - optional string value = 1; -} - -message ApiInformation { - optional near_rt_ric_apis_common_ies.v3.ApiName api_name = 1; - optional ApiId api_id = 2; - optional ApiCategory api_category = 3; - optional string description = 4; - repeated ApiProfile list_of_api_profiles = 5; - - message ApiProfile { - optional near_rt_ric_apis_common_ies.v3.ApiVersion api_version = 1; - optional Protocol protocol = 2; - optional DataFormat data_format = 3; - optional near_rt_ric_apis_common_ies.v3.EndpointInformation endpoint_information = 4; - repeated SupportedDataTypeItem list_of_supported_data_types = 5; - message SupportedDataTypeItem { - optional string data_type_id = 1; - } - }; -}; - -// -----C----- -enum Cause { - UNSPECIFIED = 0; - SYSTEM_BUSY = 1; - DUPLICATE_API_INFORMATION = 2; - UNKNOWN_API_ID = 3; - INVALID_DATA_TYPE = 4; - UNKNOWN_SUBSCRIPTION_ID = 5; -} - -// -----D----- -enum DataFormat { - DATA_FORMAT_PROTO3 = 0; - DATA_FORMAT_JSON = 1; - DATA_FORMAT_ASNI = 2; -}; - -``` - -``` - -enum EventType { - EVENT_TYPE_NEAR_RT_RIC_API_AVAILABLE = 0; - EVENT_TYPE_NEAR_RT_RIC_API_UNAVAILABLE = 1; - EVENT_TYPE_NEAR_RT_RIC_API_UPDATE = 2; -} - -// -----P----- -enum Protocol { - PROTOCOL_GRPC = 0; - PROTOCOL_SCTP = 1; - PROTOCOL_HTTP = 2; -}; - -// -----S----- -message SubscriptionId { - optional string value = 1; -} - -``` - -### 9.3.5 Message Transfer Syntax - -#### 9.3.5.1 Solution 1: gRPC with Protocol Buffers - -The message transfer syntax for Solution 1 is serialized Protocol Buffers [4]. - -# 9A AI/ML API - -## 9A.1 Overview - -### 9A.1.1 Protocol Stack - -In this version of specification, the default protocol stack for the AI/ML APIs is shown on Figure 9A.1.1-1. - -NOTE: The security protocols are specified in [6]. - -![Protocol stack diagram for AI/ML APIs showing layers from Application down to Physical Layer.](e4aab374983ba0fc24496fe7cd11c06c_img.jpg) - -| | -|-----------------| -| Application | -| gRPC | -| HTTP/2 | -| TCP | -| IP | -| Data Link Layer | -| Physical Layer | - -Protocol stack diagram for AI/ML APIs showing layers from Application down to Physical Layer. - -**Figure 9A.1.1-1: Protocol stack for AI/ML APIs** - -The AI/ML APIs use gRPC [5] with Protocol Buffers [4] as the application layer serialization protocol. - -### 9A.1.2 List of AI/ML APIs, procedures and messages - -The AI/ML API procedures introduced in clause 9.7 of [2] are categorized under the AI/ML APIs. These APIs include: - -- Data Pipelining API: enabling data pipelining for AI/ML models for xApps. -- Inference API: enabling inference of AI/ML models for xApps. -- Training API: enabling training of AI/ML models for xApps. -- Model Management and Exposure API: enabling storing and retrieval of AI/ML models by xApps. - -These APIs are summarized in Table 9A.1.2-1. - -**Table 9A.1.2-1: List of AI/ML APIs** - -| API Name | Description | -|-----------------------------------|--------------------------------------------------------------------| -| Data Pipelining API | Near-RT RIC platform service for AI/ML model data pipelining | -| Inference API | Near-RT RIC platform service for AI/ML model inference | -| AI/ML_Training_API | Near-RT RIC platform service for AI/ML model training | -| Model Management and Exposure API | Near-RT RIC platform service for AI/ML model storing and retrieval | - -The table 9A.1.2-2 lists the API procedures for each AI/ML API. - -**Table 9A.1.2-2: List of AI/ML API procedures** - -| API Name | API procedure | Communication type | -|-----------------------------------|---------------------------------|--------------------| -| Data Pipelining API | Data Pipelining Job Setup | Request/Response | -| | Data Pipelining Job Update | Request/Response | -| | Data Pipelining Job Delete | Request/Response | -| | Data Pipelining Job Query | Request/Response | -| | Data Pipelining Request | Request/Response | -| | Data Pipelining Result Delivery | Notify | -| Inference API | Inference Job Setup | Request/Response | -| | Inference Job Update | Request/Response | -| | Inference Job Delete | Request/Response | -| | Inference Job Query | Request/Response | -| | Inference Request | Request/Response | -| | Inference Result Delivery | Notify | -| AI/ML_Training_API | Training Job Setup | Request/Response | -| | Training Job Delete | Request/Response | -| | Training Job Query | Request/Response | -| | Training Request | Request/Response | -| | Training Result Delivery | Notify | -| Model Management and Exposure API | Model Store | Request/Response | -| | Stored Model Query | Request/Response | -| | Model Retrieve | Request/Response | -| | Model Delete | Request/Response | - -The table 9A.1.2-3 lists the messages for each AI/ML API procedure. - -**Table 9A.1.2-3: List of AI/ML API messages** - -| API Procedure | Initiated by | Initiating Message | Outcome Message | | -|---------------|--------------|--------------------|--------------------|----------------------| -| | | | Successful Outcome | Unsuccessful Outcome | -| | | | | | - -| | | | | | -|---------------------------------|----------------------|------------------------------------|-------------------------------------|------------------------------------| -| Data Pipelining Job Setup | xApp | DATA PIPELINING JOB SETUP REQUEST | DATA PIPELINING JOB SETUP RESPONSE | DATA PIPELINING JOB SETUP FAILURE | -| Data Pipelining Job Update | xApp | DATA PIPELINING JOB UPDATE REQUEST | DATA PIPELINING JOB UPDATE RESPONSE | DATA PIPELINING JOB UPDATE FAILURE | -| Data Pipelining Job Delete | xApp | DATA PIPELINING JOB DELETE REQUEST | DATA PIPELINING JOB DELETE RESPONSE | DATA PIPELINING JOB DELETE FAILURE | -| Data Pipelining Job Query | xApp | DATA PIPELINING JOB QUERY REQUEST | DATA PIPELINING JOB QUERY RESPONSE | DATA PIPELINING JOB QUERY FAILURE | -| Data Pipelining Request | xApp | DATA PIPELINING REQUEST | DATA PIPELINING REQUEST RESPONSE | DATA PIPELINING REQUEST FAILURE | -| Data Pipelining Result Delivery | Near-RT RIC platform | DATA PIPELINING RESULT DELIVERY | - | - | -| Inference Job Setup | xApp | INFERENCE JOB SETUP REQUEST | INFERENCE JOB SETUP RESPONSE | INFERENCE JOB SETUP FAILURE | -| Inference Job Update | xApp | INFERENCE JOB UPDATE REQUEST | INFERENCE JOB UPDATE RESPONSE | INFERENCE JOB UPDATE FAILURE | -| Inference Job Delete | xApp | INFERENCE JOB DELETE REQUEST | INFERENCE JOB DELETE RESPONSE | INFERENCE JOB DELETE FAILURE | -| Inference Job Query | xApp | INFERENCE JOB QUERY REQUEST | INFERENCE JOB QUERY RESPONSE | INFERENCE JOB QUERY FAILURE | -| Inference Request | xApp | INFERENCE REQUEST | INFERENCE REQUEST RESPONSE | INFERENCE REQUEST FAILURE | -| Inference Result Delivery | Near-RT RIC platform | INFERENCE RESULT DELIVERY | - | - | -| Training Job Setup | xApp | TRAINING JOB SETUP REQUEST | TRAINING JOB SETUP RESPONSE | TRAINING JOB SETUP FAILURE | -| Training Job Delete | xApp | TRAINING JOB DELETE REQUEST | TRAINING JOB DELETE RESPONSE | TRAINING JOB DELETE FAILURE | -| Training Job Query | xApp | TRAINING JOB QUERY REQUEST | TRAINING JOB QUERY RESPONSE | TRAINING JOB QUERY FAILURE | -| Training Request | xApp | TRAINING REQUEST | TRAINING RESPONSE | TRAINING FAILURE | -| Training Result Delivery | Near-RT RIC platform | TRAINING RESULT DELIVERY | - | - | -| Model Store | xApp | MODEL STORE REQUEST | MODEL STORE RESPONSE | MODEL STORE FAILURE | -| Stored Model Query | xApp | STORED MODEL QUERY REQUEST | STORED MODEL QUERY RESPONSE | STORED MODEL QUERY FAILURE | -| Model Retrieve | xApp | MODEL RETRIEVE REQUEST | MODEL RETRIEVE RESPONSE | MODEL RETRIEVE FAILURE | -| Model Delete | xApp | MODEL DELETE REQUEST | MODEL DELETE RESPONSE | MODEL DELETE FAILURE | - -## 9A.2 AI/ML API Procedures - -### 9A.2.1 Data Pipelining API Procedures - -#### 9A.2.1.1 General - -This procedure is used by an xApp that wants to collect and preprocess the input data for an AI/ML model in Near-RT RIC platform. - -#### 9A.2.1.2 Date Pipelining Job Setup procedure - -##### 9A.2.1.2.1 Successful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. DATA PIPELINING JOB SETUP REQUEST -RICP -> xApp : 2. DATA PIPELINING JOB SETUP RESPONSE -@enduml -``` - -![Sequence diagram for Figure 9A.2.1.2.1-1: Data Pipelining Job Setup procedure, successful operation. The diagram shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. DATA PIPELINING JOB SETUP REQUEST' message to the Near-RT RIC Platform. The Near-RT RIC Platform responds with a '2. DATA PIPELINING JOB SETUP RESPONSE' message back to the xApp.](15d5c901284409186049549eec95c4a4_img.jpg) - -``` -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. DATA PIPELINING JOB SETUP REQUEST - RICP-->>xApp: 2. DATA PIPELINING JOB SETUP RESPONSE -``` - -Sequence diagram for Figure 9A.2.1.2.1-1: Data Pipelining Job Setup procedure, successful operation. The diagram shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. DATA PIPELINING JOB SETUP REQUEST' message to the Near-RT RIC Platform. The Near-RT RIC Platform responds with a '2. DATA PIPELINING JOB SETUP RESPONSE' message back to the xApp. - -Figure 9A.2.1.2.1-1: Data Pipelining Job Setup procedure, successful operation - -The xApp initiates the procedure by sending a DATA PIPELINING JOB SETUP REQUEST message to the Near-RT-RIC platform. The message contains *Data Pipelining Job Description* IE, which carries the configuration to create a data pipelining job. The *Pipelining Job Description* IE contains *Data Processing Instruction* IE which carries the instruction for processing the pipelining data for AI/ML model. - -At reception of the DATA PIPELINING JOB SETUP REQUEST message, the Near-RT RIC platform shall assign *Data Pipelining Job ID* IE and create the data pipelining job according to the *Pipelining Job Description* IE. - -If the DATA PIPELINING JOB SETUP REQUEST is successfully fulfilled, the Near-RT RIC platform shall send a DATA PIPELINING JOB SETUP RESPONSE message back to the xApp. In the DATA PIPELINING JOB SETUP RESPONSE message, the Near-RT RIC platform shall include the *Data Pipelining Job ID* IE. - -##### 9A.2.1.2.2 Unsuccessful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. DATA PIPELINING JOB SETUP REQUEST -RICP -> xApp : 2. DATA PIPELINING JOB SETUP FAILURE -@enduml -``` - -![Sequence diagram for Figure 9A.2.1.2.2-1: Data Pipelining Job Setup procedure, unsuccessful operation. The diagram shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. DATA PIPELINING JOB SETUP REQUEST' to the platform. The platform responds with '2. DATA PIPELINING JOB SETUP FAILURE' back to the xApp.](dbf5c0f3c7836f717d9fe62c6c40b280_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. DATA PIPELINING JOB SETUP REQUEST - Near-RT RIC Platform-->>xApp: 2. DATA PIPELINING JOB SETUP FAILURE - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for Figure 9A.2.1.2.2-1: Data Pipelining Job Setup procedure, unsuccessful operation. The diagram shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. DATA PIPELINING JOB SETUP REQUEST' to the platform. The platform responds with '2. DATA PIPELINING JOB SETUP FAILURE' back to the xApp. - -**Figure 9A.2.1.2.2-1: Data Pipelining Job Setup procedure, unsuccessful operation** - -If the DATA PIPELINING JOB SETUP REQUEST fails, the Near-RT RIC platform shall send a DATA PIPELINING JOB SETUP FAILURE message back to the xApp. The message shall include the appropriate cause. - -##### **9A.2.1.2.3 Abnormal Conditions** - -Not applicable. - -#### **9A.2.1.3 Data Pipelining Job Update procedure** - -##### **9A.2.1.3.1 Successful Operation** - -``` - -startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp ->> RICP : 1. DATA PIPELINING JOB UPDATE REQUEST -RICP -->> xApp : 2. DATA PIPELINING JOB UPDATE RESPONSE -@enduml - -``` - -![Sequence diagram for Figure 9A.2.1.3.1-1: Data Pipelining Job Update procedure, successful operation. The diagram shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. DATA PIPELINING JOB UPDATE REQUEST' to the platform. The platform responds with '2. DATA PIPELINING JOB UPDATE RESPONSE' back to the xApp.](9d1b506f1f6b6923761ba49bfb1e5b71_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. DATA PIPELINING JOB UPDATE REQUEST - Near-RT RIC Platform-->>xApp: 2. DATA PIPELINING JOB UPDATE RESPONSE - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for Figure 9A.2.1.3.1-1: Data Pipelining Job Update procedure, successful operation. The diagram shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. DATA PIPELINING JOB UPDATE REQUEST' to the platform. The platform responds with '2. DATA PIPELINING JOB UPDATE RESPONSE' back to the xApp. - -**Figure 9A.2.1.3.1-1: Data Pipelining Job Update procedure, successful operation** - -The xApp initiates the procedure by sending a DATA PIPELINING JOB UPDATE REQUEST message to the Near-RT-RIC platform. The message contains *Data Pipelining Job ID* IE, which identifies the Data Pipelining Job to be updated, and contains *Data Pipelining Job Description* IE, which carries the updated configuration for the data pipelining job. - -At reception of the DATA PIPELINING JOB UPDATE REQUEST message, the Near-RT RIC platform shall update the data pipelining job according to *Data Pipelining Job Description* IE for the data pipelining job identified by *Data Pipelining Job ID* IE. - -If the DATA PIPELINING JOB UPDATE REQUEST is successfully fulfilled, the Near-RT RIC platform shall send a DATA PIPELINING JOB UPDATE RESPONSE message back to the xApp. In the DATA PIPELINING JOB UPDATE RESPONSE message, the Near-RT RIC platform shall include the *Data Pipelining Job ID* IE. - -##### **9A.2.1.3.2 Unsuccessful Operation** - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. DATA PIPELINING JOB UPDATE REQUEST -RICP -> xApp : 2. DATA PIPELINING JOB UPDATE FAILURE -@enduml -``` - -![Sequence diagram for Data Pipelining Update procedure, unsuccessful operation. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. DATA PIPELINING JOB UPDATE REQUEST' to the RICP. The RICP responds with '2. DATA PIPELINING JOB UPDATE FAILURE' back to the xApp.](f4e5a86da5c799372a7c1ea2397dedb7_img.jpg) - -``` -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. DATA PIPELINING JOB UPDATE REQUEST - RICP-->>xApp: 2. DATA PIPELINING JOB UPDATE FAILURE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform -``` - -Sequence diagram for Data Pipelining Update procedure, unsuccessful operation. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. DATA PIPELINING JOB UPDATE REQUEST' to the RICP. The RICP responds with '2. DATA PIPELINING JOB UPDATE FAILURE' back to the xApp. - -Figure 9A.2.1.3.2-1: Data Pipelining Update procedure, unsuccessful operation - -If the DATA PIPELINING JOB UPDATE REQUEST fails, the Near-RT RIC platform shall send a DATA PIPELINING JOB UPDATE FAILURE message back to the xApp. The message shall include the *Data Pipelining Job ID* IE and the appropriate cause. - -##### 9A.2.1.3.3 Abnormal Conditions - -Not applicable. - -#### 9A.2.1.4 Data Pipelining Job Delete procedure - -##### 9A.2.1.4.1 Successful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. DATA PIPELINING JOB DELETE REQUEST -RICP -> xApp : 2. DATA PIPELINING JOB DELETE RESPONSE -@enduml -``` - -![Sequence diagram for Data Pipelining Job Delete procedure, successful operation. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. DATA PIPELINING JOB DELETE REQUEST' to the RICP. The RICP responds with '2. DATA PIPELINING JOB DELETE RESPONSE' back to the xApp.](37e75e07bd69576f817434fc996be253_img.jpg) - -``` -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. DATA PIPELINING JOB DELETE REQUEST - RICP-->>xApp: 2. DATA PIPELINING JOB DELETE RESPONSE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform -``` - -Sequence diagram for Data Pipelining Job Delete procedure, successful operation. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. DATA PIPELINING JOB DELETE REQUEST' to the RICP. The RICP responds with '2. DATA PIPELINING JOB DELETE RESPONSE' back to the xApp. - -Figure 9A.2.1.4.1-1: Data Pipelining Job Delete procedure, successful operation - -The xApp initiates the procedure by sending a DATA PIPELINING JOB DELETE REQUEST message to the Near-RT-RIC platform. The message contains *Data Pipelining Job ID* IE, which identifies the data pipelining job to be terminated and deleted. - -At reception of the DATA PIPELINING JOB DELETE REQUEST message, the Near-RT-RIC platform shall terminate the corresponding data pipelining job and delete associated *Data Pipelining Job Description*. - -If the DATA PIPELINING JOB DELETE REQUEST is successfully fulfilled, the Near-RT RIC platform shall send a DATA PIPELINING JOB DELETE RESPONSE message back to the xApp. In the DATA PIPELINING JOB DELETE RESPONSE message, the Near-RT RIC platform shall include the *Data Pipelining Job ID* IE to indicate the data pipelining job has been deleted. - -##### 9A.2.1.4.2 Unsuccessful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. DATA PIPELINING JOB DELETE REQUEST -RICP -> xApp : 2. DATA PIPELINING JOB DELETE FAILURE -@enduml -``` - -![Sequence diagram for Unsuccessful Operation of Data Pipelining Job Delete procedure. The diagram shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. DATA PIPELINING JOB DELETE REQUEST' message to the Near-RT RIC Platform. The Near-RT RIC Platform responds with a '2. DATA PIPELINING JOB DELETE FAILURE' message back to the xApp.](88e677d1623f443e57a730fe04a495a5_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. DATA PIPELINING JOB DELETE REQUEST - RICP-->>xApp: 2. DATA PIPELINING JOB DELETE FAILURE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - -``` - -Sequence diagram for Unsuccessful Operation of Data Pipelining Job Delete procedure. The diagram shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. DATA PIPELINING JOB DELETE REQUEST' message to the Near-RT RIC Platform. The Near-RT RIC Platform responds with a '2. DATA PIPELINING JOB DELETE FAILURE' message back to the xApp. - -Figure 9A.2.1.4.2-1: Data Pipelining Job Delete procedure, unsuccessful operation - -If the DATA PIPELINING JOB DELETE REQUEST fails, the Near-RT RIC platform shall send a DATA PIPELINING JOB DELETE FAILURE message back to the xApp. The message shall include the *Data Pipelining Job ID* IE and the appropriate cause. - -##### 9A.2.1.4.3 Abnormal Conditions - -Not applicable. - -#### 9A.2.1.5 Data Pipelining Job Query procedure - -##### 9A.2.1.5.1 Successful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. DATA PIPELINING JOB QUERY REQUEST -RICP -> xApp : 2. DATA PIPELINING JOB QUERY RESPONSE -@enduml -``` - -![Sequence diagram for successful Data Pipelining Job Query procedure. It shows two lifelines: xApp and Near-RT RIC Platform. Step 1: xApp sends '1. DATA PIPELINING JOB QUERY REQUEST' to Near-RT RIC Platform. Step 2: Near-RT RIC Platform sends '2. DATA PIPELINING JOB QUERY RESPONSE' back to xApp.](ecae674475cecdd0962200a5d1e2591e_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note over xApp: xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. DATA PIPELINING JOB QUERY REQUEST - Near-RT RIC Platform-->>xApp: 2. DATA PIPELINING JOB QUERY RESPONSE - Note over xApp: xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for successful Data Pipelining Job Query procedure. It shows two lifelines: xApp and Near-RT RIC Platform. Step 1: xApp sends '1. DATA PIPELINING JOB QUERY REQUEST' to Near-RT RIC Platform. Step 2: Near-RT RIC Platform sends '2. DATA PIPELINING JOB QUERY RESPONSE' back to xApp. - -**Figure 9A.2.1.5.1-1: Data Pipelining Job Query procedure, successful operation** - -The xApp initiates the procedure by sending a DATA PIPELINING JOB QUERY REQUEST message to the Near-RT-RIC platform. The message contains *Data Pipelining Job ID* IE, which identifies the data pipelining job to be queried. - -At reception of the DATA PIPELINING JOB QUERY REQUEST message, the Near-RT-RIC platform shall inspect the status of the data pipelining job identified by the *Data Pipelining Job ID* IE. - -If the DATA PIPELINING JOB QUERY REQUEST is successfully fulfilled, the Near-RT RIC platform shall send a DATA PIPELINING JOB QUERY RESPONSE message back to the xApp. In the DATA PIPELINING JOB QUERY RESPONSE message, the Near-RT RIC platform shall include the *Data Pipelining Job Status* IE of the queried data pipelining job identified by the *Data Pipelining Job ID* IE. - -##### **9A.2.1.5.2 Unsuccessful Operation** - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. DATA PIPELINING JOB QUERY REQUEST -RICP -> xApp : 2. DATA PIPELINING JOB QUERY FAILURE -@enduml - -``` - -![Sequence diagram for unsuccessful Data Pipelining Job Query procedure. It shows two lifelines: xApp and Near-RT RIC Platform. Step 1: xApp sends '1. DATA PIPELINING JOB QUERY REQUEST' to Near-RT RIC Platform. Step 2: Near-RT RIC Platform sends '2. DATA PIPELINING JOB QUERY FAILURE' back to xApp.](4fed8a9f7064898f635d0f83b0a1ae61_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note over xApp: xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. DATA PIPELINING JOB QUERY REQUEST - Near-RT RIC Platform-->>xApp: 2. DATA PIPELINING JOB QUERY FAILURE - Note over xApp: xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for unsuccessful Data Pipelining Job Query procedure. It shows two lifelines: xApp and Near-RT RIC Platform. Step 1: xApp sends '1. DATA PIPELINING JOB QUERY REQUEST' to Near-RT RIC Platform. Step 2: Near-RT RIC Platform sends '2. DATA PIPELINING JOB QUERY FAILURE' back to xApp. - -**Figure 9A.2.1.5.2-1: Data Pipelining Job Query procedure, unsuccessful operation** - -If the DATA PIPELINING JOB QUERY REQUEST fails, the Near-RT RIC platform shall send a DATA PIPELINING JOB QUERY FAILURE message back to the xApp. The message shall include the *Data Pipelining Job ID* IE and the appropriate cause. - -##### **9A.2.1.5.3 Abnormal Conditions** - -Not applicable. - -#### **9A.2.1.6 Date Pipelining Request procedure** - -##### **9A.2.1.6.1 Successful Operation** - -``` - -@startuml - -``` - -``` - -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICH as "Near-RT RIC Platform" -xApp -> RICH : 1. DATA PIPELINING REQUEST -RICH -> xApp : 2. DATA PIPELINING RESPONSE -@enduml - -``` - -![Sequence diagram for successful data pipelining request. Lifelines: xApp and Near-RT RIC Platform. Message 1: DATA PIPELINING REQUEST from xApp to Near-RT RIC Platform. Message 2: DATA PIPELINING RESPONSE from Near-RT RIC Platform to xApp.](b02ba0b73e95416eb547976f6145b169_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant RICH as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICH: Near-RT RIC Platform - xApp->>RICH: 1. DATA PIPELINING REQUEST - Note right of RICH: Near-RT RIC Platform - Note left of xApp: xApp - RICH-->>xApp: 2. DATA PIPELINING RESPONSE - -``` - -Sequence diagram for successful data pipelining request. Lifelines: xApp and Near-RT RIC Platform. Message 1: DATA PIPELINING REQUEST from xApp to Near-RT RIC Platform. Message 2: DATA PIPELINING RESPONSE from Near-RT RIC Platform to xApp. - -**Figure 9A.2.1.6.1-1: Data Pipelining Request procedure, successful operation** - -The xApp initiates the procedure by sending a DATA PIPELINING REQUEST message to the Near-RT-RIC platform. The message contains *Data Pipelining Request Description* IE, which carries the information to perform a data pipelining job identified by the *Data Pipelining Job ID* IE. - -At reception of the DATA PIPELINING REQUEST message, the Near-RT-RIC platform shall perform the data pipelining with provided input data or input data address. - -If the DATA PIPELINING REQUEST is accepted and the *Result delivery Method* IE in *Data Pipelining Job Description* IE is set to “DELIVERY”, the Near-RT RIC platform shall send a DATA PIPELINING REQUEST RESPONSE message back to the xApp to acknowledge the request. The Near-RT RIC platform then performs the data pipelining. The data pipelining result is provided to xApp via the Data Pipelining Delivery procedure. - -If the DATA PIPELINING REQUEST is accepted and the *Result delivery Method* IE in *Data Pipelining Job Description* IE is set to “RESPONSE”, the Near-RT RIC platform shall send a DATA PIPELINING REQUEST RESPONSE message back to the xApp after it finishes the requested data pipelining. In the DATA PIPELINING REQUEST RESPONSE message, the Near-RT RIC platform shall include the *Data Pipelining Job ID* IE and the *Data Pipelining Result* IE. - -##### 9A.2.1.6.2 Unsuccessful Operation - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICH as "Near-RT RIC Platform" -xApp -> RICH : 1. DATA PIPELINING REQUEST -RICH -> xApp : 2. DATA PIPELINING FAILURE -@enduml - -``` - -![Sequence diagram for unsuccessful data pipelining request. Lifelines: xApp and Near-RT RIC Platform. Message 1: DATA PIPELINING REQUEST from xApp to Near-RT RIC Platform. Message 2: DATA PIPELINING FAILURE from Near-RT RIC Platform to xApp.](58df9e48362936fbfe061cf470485b4d_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant RICH as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICH: Near-RT RIC Platform - xApp->>RICH: 1. DATA PIPELINING REQUEST - Note right of RICH: Near-RT RIC Platform - Note left of xApp: xApp - RICH-->>xApp: 2. DATA PIPELINING FAILURE - -``` - -Sequence diagram for unsuccessful data pipelining request. Lifelines: xApp and Near-RT RIC Platform. Message 1: DATA PIPELINING REQUEST from xApp to Near-RT RIC Platform. Message 2: DATA PIPELINING FAILURE from Near-RT RIC Platform to xApp. - -**Figure 9A.2.1.6.2-1: Data Pipelining Request procedure, unsuccessful operation** - -If the DATA PIPELINING REQUEST fails, the Near-RT RIC platform shall send a DATA PIPELINING FAILURE message back to the xApp. The message shall include the *Data Pipelining Job ID* IE and the appropriate cause. - -##### **9A.2.1.6.3 Abnormal Conditions** - -Not applicable. - -#### **9A.2.1.7 Data Pipelining Result Delivery procedure** - -##### **9A.2.1.7.1 Successful Operation** - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -RICP -> xApp : 2. DATA PIPELINING RESULT DELIVERY -@enduml -``` - -![Sequence diagram for Data Pipelining Result Delivery procedure. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp is at the top, and the Near-RT RIC Platform is at the bottom. A message labeled '2. DATA PIPELINING RESULT DELIVERY' is shown as a dashed arrow pointing from the Near-RT RIC Platform lifeline down to the xApp lifeline.](034b9d22fdb2e7e61ff3b15f229569bf_img.jpg) - -Sequence diagram for Data Pipelining Result Delivery procedure. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp is at the top, and the Near-RT RIC Platform is at the bottom. A message labeled '2. DATA PIPELINING RESULT DELIVERY' is shown as a dashed arrow pointing from the Near-RT RIC Platform lifeline down to the xApp lifeline. - -**Figure 9A.2.1.7.1-1: Data Pipelining Result Delivery procedure** - -The xApp initiates the procedure by sending a DATA PIPELINING RESULT DELIVERY message to the Near-RT RIC platform. The message contains *Data Pipelining Result* IE, which carries the data pipelining result. - -##### **9A.2.1.7.2 Abnormal Conditions** - -Not applicable. - -### **9A.2.2 Inference API Procedures** - -#### **9A.2.2.1 General** - -This procedure is used by an xApp that wants to get the inference result of an AI/ML model in Near-RT RIC platform. - -#### **9A.2.2.2 Inference Job Setup procedure** - -##### **9A.2.2.2.1 Successful Operation** - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. INFERENCE JOB SETUP REQUEST -RICP -> xApp : 2. INFERENCE JOB SETUP RESPONSE -@enduml -``` - -![Sequence diagram for successful inference job setup. Lifelines: xApp and Near-RT RIC Platform. Message 1: INFERENCE JOB SETUP REQUEST from xApp to Near-RT RIC Platform. Message 2: INFERENCE JOB SETUP RESPONSE from Near-RT RIC Platform to xApp.](3d13999d5257e24e629f65f28bf10251_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note over xApp: xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. INFERENCE JOB SETUP REQUEST - Near-RT RIC Platform-->>xApp: 2. INFERENCE JOB SETUP RESPONSE - Note over xApp: xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for successful inference job setup. Lifelines: xApp and Near-RT RIC Platform. Message 1: INFERENCE JOB SETUP REQUEST from xApp to Near-RT RIC Platform. Message 2: INFERENCE JOB SETUP RESPONSE from Near-RT RIC Platform to xApp. - -**Figure 9A.2.2.2.1-1: Inference Job Setup procedure, successful operation** - -The xApp initiates the procedure by sending an INFERENCE JOB SETUP REQUEST message to the Near-RT-RIC platform. The message contains *Inference Job Description* IE, which carries the configuration to create an AI/ML model inference job. - -At reception of the INFERENCE JOB SETUP REQUEST message, the Near-RT RIC platform shall assign *Inference Job ID* IE and create the AI/ML model inference job according to *Inference Job Description* IE - -If the INFERENCE JOB SETUP REQUEST is successfully fulfilled, the Near-RT RIC platform shall send an INFERENCE JOB SETUP RESPONSE message back to the xApp. In the INFERENCE JOB SETUP RESPONSE message, the Near-RT RIC platform shall include the *Inference Job ID* IE. - -##### **9A.2.2.2.2 Unsuccessful Operation** - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. INFERENCE JOB SETUP REQUEST -RICP -> xApp : 2. INFERENCE JOB SETUP FAILURE -@enduml - -``` - -![Sequence diagram for unsuccessful inference job setup. Lifelines: xApp and Near-RT RIC Platform. Message 1: INFERENCE JOB SETUP REQUEST from xApp to Near-RT RIC Platform. Message 2: INFERENCE JOB SETUP FAILURE from Near-RT RIC Platform to xApp.](435cf83a9531da350ea543aafa0add62_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note over xApp: xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. INFERENCE JOB SETUP REQUEST - Near-RT RIC Platform-->>xApp: 2. INFERENCE JOB SETUP FAILURE - Note over xApp: xApp - Note over Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for unsuccessful inference job setup. Lifelines: xApp and Near-RT RIC Platform. Message 1: INFERENCE JOB SETUP REQUEST from xApp to Near-RT RIC Platform. Message 2: INFERENCE JOB SETUP FAILURE from Near-RT RIC Platform to xApp. - -**Figure 9A.2.2.2.2-1: Inference Job Setup procedure, unsuccessful operation** - -If the INFERENCE JOB SETUP REQUEST fails, the Near-RT RIC platform shall send an INFERENCE JOB SETUP FAILURE message back to the xApp. The message shall include the appropriate cause. - -## **9A.2.2.2.3 Abnormal Conditions** - -Not applicable. - -**9A.2.2.3 Inference Job Update procedure** - -**9A.2.2.3.1 Successful Operation** - -``` - -@startuml -skin rose - -``` - -``` - -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. INFERENCE JOB UPDATE REQUEST -RICP -> xApp : 2. INFERENCE JOB UPDATE RESPONSE -@enduml - -``` - -![Sequence diagram for successful inference job update. Lifelines: xApp and Near-RT RIC Platform. Message 1: INFERENCE JOB UPDATE REQUEST from xApp to RICP. Message 2: INFERENCE JOB UPDATE RESPONSE from RICP to xApp.](884c44b6cb9fbe15347e0562a6085df2_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. INFERENCE JOB UPDATE REQUEST - RICP-->>xApp: 2. INFERENCE JOB UPDATE RESPONSE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - -``` - -Sequence diagram for successful inference job update. Lifelines: xApp and Near-RT RIC Platform. Message 1: INFERENCE JOB UPDATE REQUEST from xApp to RICP. Message 2: INFERENCE JOB UPDATE RESPONSE from RICP to xApp. - -**Figure 9A.2.2.3.1-1: Inference Job Update procedure, successful operation** - -The xApp initiates the procedure by sending an INFERENCE JOB UPDATE REQUEST message to the Near-RT-RIC platform. The message contains *Inference Job ID* IE, which carries the identifier of the Inference Job to be updated, and contains *Inference Job Description* IE, which carries the updated configuration for the AI/ML model inference job. - -At reception of the INFERENCE JOB UPDATE REQUEST message, the Near-RT RIC platform shall update the AI/ML model inference job identified by *Inference Job ID* IE according to *Inference Job Description* IE. - -If the INFERENCE JOB UPDATE REQUEST is successfully fulfilled, the Near-RT RIC platform shall send an INFERENCE JOB UPDATE RESPONSE message back to the xApp. In the INFERENCE JOB UPDATE RESPONSE message, the Near-RT RIC platform shall include the *Inference Job ID* IE. - -**9A.2.2.3.2 Unsuccessful Operation** - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. INFERENCE JOB UPDATE REQUEST -RICP -> xApp : 2. INFERENCE JOB UPDATE FAILURE -@enduml - -``` - -![Sequence diagram for unsuccessful inference job update. Lifelines: xApp and Near-RT RIC Platform. Message 1: INFERENCE JOB UPDATE REQUEST from xApp to RICP. Message 2: INFERENCE JOB UPDATE FAILURE from RICP to xApp.](24b10c86fe55f7126e355d9bc6fef7b9_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. INFERENCE JOB UPDATE REQUEST - RICP-->>xApp: 2. INFERENCE JOB UPDATE FAILURE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - -``` - -Sequence diagram for unsuccessful inference job update. Lifelines: xApp and Near-RT RIC Platform. Message 1: INFERENCE JOB UPDATE REQUEST from xApp to RICP. Message 2: INFERENCE JOB UPDATE FAILURE from RICP to xApp. - -**Figure 9A.2.2.3.2-1: Inference Job Update procedure, unsuccessful operation** - -If the INFERENCE JOB UPDATE REQUEST fails, the Near-RT RIC platform shall send an INFERENCE JOB UPDATE FAILURE message back to the xApp. The message shall include the appropriate cause. - -**9A.2.2.3.3 Abnormal Conditions** - -Not applicable. - -**9A.2.2.4 Inference Job Delete procedure** - -**9A.2.2.4.1 Successful Operation** - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICH as "Near-RT RIC Platform" -xApp -> RICH : 1. INFERENCE JOB DELETE REQUEST -RICH -> xApp : 2. INFERENCE JOB DELETE RESPONSE -@enduml -``` - -![Sequence diagram for Inference Job Delete procedure, successful operation. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. INFERENCE JOB DELETE REQUEST' message to the Near-RT RIC Platform. The Near-RT RIC Platform responds with a '2. INFERENCE JOB DELETE RESPONSE' message back to the xApp.](ff722ae9516b94709d721deaf5523d2e_img.jpg) - -``` -sequenceDiagram - participant xApp - participant RICH as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICH: Near-RT RIC Platform - xApp->>RICH: 1. INFERENCE JOB DELETE REQUEST - RICH-->>xApp: 2. INFERENCE JOB DELETE RESPONSE - Note left of xApp: xApp - Note right of RICH: Near-RT RIC Platform -``` - -Sequence diagram for Inference Job Delete procedure, successful operation. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. INFERENCE JOB DELETE REQUEST' message to the Near-RT RIC Platform. The Near-RT RIC Platform responds with a '2. INFERENCE JOB DELETE RESPONSE' message back to the xApp. - -**Figure 9A.2.2.4.1-1: Inference Job Delete procedure, successful operation** - -The xApp initiates the procedure by sending an INFERENCE JOB DELETE REQUEST message to the Near-RT-RIC platform. The message contains *Inference Job ID* IE, which identifies the inference job to be terminated and deleted. - -At reception of the INFERENCE JOB DELETE REQUEST message, the Near-RT-RIC platform shall terminate the corresponding inference job and delete associated *Inference Job Description*. - -If the INFERENCE JOB DELETE REQUEST is successfully fulfilled, the Near-RT RIC platform shall send an INFERENCE JOB DELETE RESPONSE message back to the xApp. In the INFERENCE JOB DELETE RESPONSE message, the Near-RT RIC platform shall include the *Inference Job ID* IE to indicate the inference job has been deleted. - -**9A.2.2.4.2 Unsuccessful Operation** - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICH as "Near-RT RIC Platform" -xApp -> RICH : 1. INFERENCE JOB DELETE REQUEST -RICH -> xApp : 2. INFERENCE JOB DELETE FAILURE -@enduml -``` - -![Sequence diagram for Inference Job Delete procedure, unsuccessful operation. It shows an xApp sending a 1. INFERENCE JOB DELETE REQUEST to a Near-RT RIC Platform, which responds with a 2. INFERENCE JOB DELETE FAILURE.](5a3dccee8ce4d2fa1986aba4ae8ad6e2_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. INFERENCE JOB DELETE REQUEST - Near-RT RIC Platform-->>xApp: 2. INFERENCE JOB DELETE FAILURE - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for Inference Job Delete procedure, unsuccessful operation. It shows an xApp sending a 1. INFERENCE JOB DELETE REQUEST to a Near-RT RIC Platform, which responds with a 2. INFERENCE JOB DELETE FAILURE. - -**Figure 9A.2.2.4.2-1: Inference Job Delete procedure, unsuccessful operation** - -If the INFERENCE JOB DELETE REQUEST fails, the Near-RT RIC platform shall send an INFERENCE JOB DELETE FAILURE message back to the xApp. The message shall include the appropriate cause. - -**9A.2.2.4.3 Abnormal Conditions** - -Not applicable. - -**9A.2.2.5 Inference Job Query procedure** - -**9A.2.2.5.1 Successful Operation** - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp ->> RICP : 1. INFERENCE JOB QUERY REQUEST -RICP -->> xApp : 2. INFERENCE JOB QUERY RESPONSE -@enduml - -``` - -![Sequence diagram for Inference Job Query procedure, successful operation. It shows an xApp sending a 1. INFERENCE JOB QUERY REQUEST to a Near-RT RIC Platform, which responds with a 2. INFERENCE JOB QUERY RESPONSE.](c77dfd42af832009a383aabc67238c2e_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. INFERENCE JOB QUERY REQUEST - Near-RT RIC Platform-->>xApp: 2. INFERENCE JOB QUERY RESPONSE - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for Inference Job Query procedure, successful operation. It shows an xApp sending a 1. INFERENCE JOB QUERY REQUEST to a Near-RT RIC Platform, which responds with a 2. INFERENCE JOB QUERY RESPONSE. - -**Figure 9A.2.2.5.1-1: Inference Job Query procedure, successful operation** - -The xApp initiates the procedure by sending an INFERENCE JOB QUERY REQUEST message to the Near-RT-RIC platform. The message contains *Inference Job ID* IE, which identifies the inference job to be queried. - -At reception of the INFERENCE JOB QUERY REQUEST message, the Near-RT-RIC platform shall inspect the status of the corresponding inference job. - -If the INFERENCE JOB QUERY REQUEST is successfully fulfilled, the Near-RT RIC platform shall send an INFERENCE JOB QUERY RESPONSE message back to the xApp. In the INFERENCE JOB QUERY RESPONSE message, the Near-RT RIC platform shall include the *Inference Job Status* IE of the queried inference job. - -**9A.2.2.5.2 Unsuccessful Operation** - -``` -@startuml -``` - -``` - -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. INFERENCE JOB QUERY REQUEST -RICP -> xApp : 2. INFERENCE JOB QUERY FAILURE -@enduml - -``` - -![Sequence diagram for Inference Job Query procedure, unsuccessful operation. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. INFERENCE JOB QUERY REQUEST' to the platform, and the platform responds with '2. INFERENCE JOB QUERY FAILURE'.](b55cd9b5721bd8aabc979c85316924e4_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. INFERENCE JOB QUERY REQUEST - RICP-->>xApp: 2. INFERENCE JOB QUERY FAILURE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - -``` - -Sequence diagram for Inference Job Query procedure, unsuccessful operation. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. INFERENCE JOB QUERY REQUEST' to the platform, and the platform responds with '2. INFERENCE JOB QUERY FAILURE'. - -**Figure 9A.2.2.5.2-1: Inference Job Query procedure, unsuccessful operation** - -If the INFERENCE JOB QUERY REQUEST fails, the Near-RT RIC platform shall send an INFERENCE JOB QUERY FAILURE message back to the xApp. The message shall include the appropriate cause. - -**9A.2.2.5.3 Abnormal Conditions** - -Not applicable. - -**9A.2.2.6 Inference Request procedure** - -**9A.2.2.6.1 Successful Operation** - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. INFERENCE REQUEST -RICP -> xApp : 2. INFERENCE RESPONSE -@enduml - -``` - -![Sequence diagram for Inference Request procedure, successful operation. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. INFERENCE REQUEST' to the platform, and the platform responds with '2. INFERENCE RESPONSE'.](960c6a04d04a5d8683ae3d11235a4e68_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. INFERENCE REQUEST - RICP-->>xApp: 2. INFERENCE RESPONSE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - -``` - -Sequence diagram for Inference Request procedure, successful operation. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. INFERENCE REQUEST' to the platform, and the platform responds with '2. INFERENCE RESPONSE'. - -**Figure 9A.2.2.6.1-1: Inference Request procedure, successful operation** - -The xApp initiates the procedure by sending an INFERENCE REQUEST message to the Near-RT-RIC platform. The message contains *Inference Request Description* IE, which carries the information to perform the inference job identified by the *Inference Job ID* IE. - -At reception of the INFERENCE REQUEST message, the Near-RT-RIC platform shall perform the AI/ML model inference with provided dataset. - -If the INFERENCE REQUEST is accepted and the *Result Delivery Method* IE in *Inference Job Description* IE is set to “DELIVERY”, the Near-RT RIC platform shall send an INFERENCE RESPONSE message back to the xApp to acknowledge the request. The Near-RT RIC platform then performs the inference. The inference result is provided to xApp via the Inference Result Delivery procedure. - -If the INFERENCE REQUEST is accepted and the *Result Delivery Method* IE in *Inference Job Description* IE is set to “RESPONSE”, the Near-RT RIC platform shall send an INFERENCE REQUEST RESPONSE message back to the xApp after it finishes the requested inference. In the INFERENCE REQUEST RESPONSE message, the Near-RT RIC platform shall include the *Inference Result* IE. - -#### 9A.2.2.6.2 Unsuccessful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp ->> RICP : 1. INFERENCE REQUEST -RICP -->> xApp : 2. INFERENCE FAILURE -@enduml -``` - -![Sequence diagram showing an unsuccessful inference request. The xApp sends an INFERENCE REQUEST to the Near-RT RIC Platform, which responds with an INFERENCE FAILURE.](599928760ca71d72f3248a3a9a07c446_img.jpg) - -``` -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - xApp->>RICP: 1. INFERENCE REQUEST - Note right of RICP: Near-RT RIC Platform - RICP-->>xApp: 2. INFERENCE FAILURE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform -``` - -Sequence diagram showing an unsuccessful inference request. The xApp sends an INFERENCE REQUEST to the Near-RT RIC Platform, which responds with an INFERENCE FAILURE. - -Figure 9A.2.2.6.2-1: Inference Request procedure, unsuccessful operation - -If the INFERENCE REQUEST fails, the Near-RT RIC platform shall send an INFERENCE FAILURE message back to the xApp. The message shall include the appropriate cause. - -#### 9A.2.2.6.3 Abnormal Conditions - -Not applicable. - -### 9A.2.2.7 Inference Result Delivery procedure - -#### 9A.2.2.7.1 Successful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -``` - -``` -Participant RICP as "Near-RT RIC Platform" -RICP -> xApp : 2. INFERENCE RESULT DELIVERY -@enduml -``` - -![Sequence diagram for Inference Result Delivery procedure. It shows two lifelines: xApp and Near-RT RIC Platform. A message labeled '2. INFERENCE RESULT DELIVERY' is sent from the Near-RT RIC Platform to the xApp.](6059b0a3a051cc20b414d51a4e412f3e_img.jpg) - -``` -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note right of RICP: 2. INFERENCE RESULT DELIVERY - RICP->>xApp: - Note left of xApp: -``` - -Sequence diagram for Inference Result Delivery procedure. It shows two lifelines: xApp and Near-RT RIC Platform. A message labeled '2. INFERENCE RESULT DELIVERY' is sent from the Near-RT RIC Platform to the xApp. - -Figure 9A.2.2.7.1-1: Inference Result Delivery procedure - -The xApp initiates the procedure by sending an INFERENCE RESULT DELIVERY message to the Near-RT-RIC platform. The message contains the *Inference Job ID IE* and the *Inference Result IE*, which carries the inference result for the inference job identified by the *Inference Job ID IE*. - -### 9A.2.2.7.2 Abnormal Conditions - -Not applicable. - -## 9A.2.3 AIML Training API Procedures - -### 9A.2.3.1 General - -This procedure is used by an xApp that wants to train an AI/ML model in Near-RT RIC platform. - -### 9A.2.3.2 Training Job Setup procedure - -#### 9A.2.3.2.1 Successful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. TRAINING JOB SETUP REQUEST -RICP -> xApp : 2. TRAINING JOB SETUP RESPONSE -@enduml -``` - -![Sequence diagram for Training Job Setup procedure, successful operation. It shows two lifelines: xApp and Near-RT RIC Platform. Step 1: xApp sends '1. TRAINING JOB SETUP REQUEST' to Near-RT RIC Platform. Step 2: Near-RT RIC Platform sends '2. TRAINING JOB SETUP RESPONSE' back to xApp.](e67bca96ac67ddab7a8762b49d4c438d_img.jpg) - -``` -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: 1. TRAINING JOB SETUP REQUEST - xApp->>RICP: - Note right of RICP: 2. TRAINING JOB SETUP RESPONSE - RICP->>xApp: - Note left of xApp: -``` - -Sequence diagram for Training Job Setup procedure, successful operation. It shows two lifelines: xApp and Near-RT RIC Platform. Step 1: xApp sends '1. TRAINING JOB SETUP REQUEST' to Near-RT RIC Platform. Step 2: Near-RT RIC Platform sends '2. TRAINING JOB SETUP RESPONSE' back to xApp. - -Figure 9A.2.3.2.1-1: Training Job Setup procedure, successful operation - -The xApp initiates the procedure by sending a TRAINING JOB SETUP REQUEST message to the Near-RT-RIC platform. The message contains *Training Job Description IE*, which carries the configuration to create an AI/ML model training job. - -At reception of the TRAINING JOB SETUP REQUEST message, the Near-RT RIC platform shall assign *Training Job ID* IE and create the AI/ML model training job according to *Training Job Description* IE - -If the TRAINING JOB SETUP REQUEST is successfully fulfilled, the Near-RT RIC platform shall send a TRAINING JOB SETUP RESPONSE message back to the xApp. In the TRAINING JOB SETUP RESPONSE message, the Near-RT RIC platform shall include the *Training Job ID* IE. - -### 9A.2.3.2.2 Unsuccessful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. TRAINING JOB SETUP REQUEST -RICP -> xApp : 2. TRAINING JOB SETUP FAILURE -@enduml -``` - -![Sequence diagram for Training Job Setup procedure, unsuccessful operation. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. TRAINING JOB SETUP REQUEST' message to the RICP. The RICP responds with a '2. TRAINING JOB SETUP FAILURE' message back to the xApp.](eaad3504edeecffe148decdc5c04a171_img.jpg) - -``` -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. TRAINING JOB SETUP REQUEST - RICP-->>xApp: 2. TRAINING JOB SETUP FAILURE -``` - -Sequence diagram for Training Job Setup procedure, unsuccessful operation. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. TRAINING JOB SETUP REQUEST' message to the RICP. The RICP responds with a '2. TRAINING JOB SETUP FAILURE' message back to the xApp. - -Figure 9A.2.3.2.2-1: Training Job Setup procedure, unsuccessful operation - -If the TRAINING JOB SETUP REQUEST fails, the Near-RT RIC platform shall send a TRAINING JOB SETUP FAILURE message back to the xApp. The message shall include the appropriate cause. - -### 9A.2.3.2.3 Abnormal Conditions - -Not applicable. - -## 9A.2.3.3 Training Job Delete procedure - -### 9A.2.3.3.1 Successful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. TRAINING JOB DELETE REQUEST -RICP -> xApp : 2. TRAINING JOB DELETE RESPONSE -@enduml -``` - -![Sequence diagram for successful Training Job Delete procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: TRAINING JOB DELETE REQUEST from xApp to Near-RT RIC Platform. Message 2: TRAINING JOB DELETE RESPONSE from Near-RT RIC Platform to xApp.](60f844d947ea0bccdd9f64d81d5f8d26_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. TRAINING JOB DELETE REQUEST - Near-RT RIC Platform-->>xApp: 2. TRAINING JOB DELETE RESPONSE - -``` - -Sequence diagram for successful Training Job Delete procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: TRAINING JOB DELETE REQUEST from xApp to Near-RT RIC Platform. Message 2: TRAINING JOB DELETE RESPONSE from Near-RT RIC Platform to xApp. - -**Figure 9A.2.3.3.1-1: Training Job Delete procedure, successful operation** - -The xApp initiates the procedure by sending a TRAINING JOB DELETE REQUEST message to the Near-RT-RIC platform. The message contains *Training Job ID* IE, which identifies the training job to be terminated and deleted. - -At reception of the TRAINING JOB DELETE REQUEST message, the Near-RT-RIC platform shall terminate the corresponding training job and delete associated *Training Job Description*. - -If the TRAINING JOB DELETE REQUEST is successfully fulfilled, the Near-RT RIC platform shall send a TRAINING JOB DELETE RESPONSE message back to the xApp. In the TRAINING JOB DELETE RESPONSE message, the Near-RT RIC platform shall include the *Training Job ID* IE to indicate the training job has been deleted. - -**9A.2.3.3.2 Unsuccessful Operation** - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. TRAINING JOB DELETE REQUEST -RICP -> xApp : 2. TRAINING JOB DELETE FAILURE -@enduml - -``` - -![Sequence diagram for unsuccessful Training Job Delete procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: TRAINING JOB DELETE REQUEST from xApp to Near-RT RIC Platform. Message 2: TRAINING JOB DELETE FAILURE from Near-RT RIC Platform to xApp.](3295c6ffe9f6d00c3811c37d327ac844_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. TRAINING JOB DELETE REQUEST - Near-RT RIC Platform-->>xApp: 2. TRAINING JOB DELETE FAILURE - -``` - -Sequence diagram for unsuccessful Training Job Delete procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: TRAINING JOB DELETE REQUEST from xApp to Near-RT RIC Platform. Message 2: TRAINING JOB DELETE FAILURE from Near-RT RIC Platform to xApp. - -**Figure 9A.2.3.3.2-1: Training Job Delete procedure, unsuccessful operation** - -If the TRAINING JOB DELETE REQUEST fails, the Near-RT RIC platform shall send a TRAINING JOB DELETE FAILURE message back to the xApp. The message shall include the appropriate cause. - -**9A.2.3.3.3 Abnormal Conditions** - -Not applicable. - -**9A.2.3.4 Training Job Query procedure** - -**9A.2.3.4.1 Successful Operation** - -``` - -@startuml - -``` - -``` - -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. TRAINING JOB QUERY REQUEST -RICP -> xApp : 2. TRAINING JOB QUERY RESPONSE -@enduml - -``` - -![Sequence diagram for successful Training Job Query procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: TRAINING JOB QUERY REQUEST from xApp to RICP. Message 2: TRAINING JOB QUERY RESPONSE from RICP to xApp.](137bcfed81ada68ca5162ca5afed35c7_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. TRAINING JOB QUERY REQUEST - RICP-->>xApp: 2. TRAINING JOB QUERY RESPONSE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - -``` - -Sequence diagram for successful Training Job Query procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: TRAINING JOB QUERY REQUEST from xApp to RICP. Message 2: TRAINING JOB QUERY RESPONSE from RICP to xApp. - -**Figure 9A.2.3.4.1-1: Training Job Query procedure, successful operation** - -The xApp initiates the procedure by sending a TRAINING JOB QUERY REQUEST message to the Near-RT-RIC platform. The message contains *Training Job ID* IE, which identifies the training job to be queried. - -At reception of the TRAINING JOB QUERY REQUEST message, the Near-RT-RIC platform shall look up the *Training Job Status* IE of the corresponding training job. - -If the TRAINING JOB QUERY REQUEST is successfully fulfilled, the Near-RT RIC platform shall send a TRAINING JOB QUERY RESPONSE message back to the xApp. In the TRAINING JOB QUERY RESPONSE message, the Near-RT RIC platform shall include the *Training Job Status* IE of the queried training job. - -### 9A.2.3.4.2 Unsuccessful Operation - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. TRAINING JOB QUERY REQUEST -RICP -> xApp : 2. TRAINING JOB QUERY FAILURE -@enduml - -``` - -![Sequence diagram for unsuccessful Training Job Query procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: TRAINING JOB QUERY REQUEST from xApp to RICP. Message 2: TRAINING JOB QUERY FAILURE from RICP to xApp.](dbcee1610ecdaa500f5b11abf307ea5d_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. TRAINING JOB QUERY REQUEST - RICP-->>xApp: 2. TRAINING JOB QUERY FAILURE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - -``` - -Sequence diagram for unsuccessful Training Job Query procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: TRAINING JOB QUERY REQUEST from xApp to RICP. Message 2: TRAINING JOB QUERY FAILURE from RICP to xApp. - -**Figure 9A.2.3.4.2-1: Training Job Query procedure, unsuccessful operation** - -If the TRAINING JOB QUERY REQUEST fails, the Near-RT RIC platform shall send a TRAINING JOB QUERY FAILURE message back to the xApp. The message shall include the appropriate cause. - -### 9A.2.3.4.3 Abnormal Conditions - -Not applicable. - -### 9A.2.3.5 Training Request procedure - -#### 9A.2.3.5.1 Successful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. TRAINING REQUEST -RICP -> xApp : 2. TRAINING RESPONSE -@enduml -``` - -![Sequence diagram for Training Request procedure, successful operation. The diagram shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. TRAINING REQUEST' message to the Near-RT RIC Platform. The Near-RT RIC Platform responds with a '2. TRAINING RESPONSE' message back to the xApp.](48fecf94dd9fb955caddbf2fb01b7b9b_img.jpg) - -``` -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. TRAINING REQUEST - RICP-->>xApp: 2. TRAINING RESPONSE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform -``` - -Sequence diagram for Training Request procedure, successful operation. The diagram shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. TRAINING REQUEST' message to the Near-RT RIC Platform. The Near-RT RIC Platform responds with a '2. TRAINING RESPONSE' message back to the xApp. - -**Figure 9A.2.3.5.1-1: Training Request procedure, successful operation** - -The xApp initiates the procedure by sending a TRAINING REQUEST message to the Near-RT-RIC platform. The message contains *Training Request Description* IE, which carries the information to perform a training job identified by the Training Job ID. - -At reception of the TRAINING REQUEST message, the Near-RT-RIC platform shall perform the AI/ML model training with provided dataset. - -If the TRAINING REQUEST is accepted and *Result Delivery Method* IE in *Training Job Setup* IE is set to “DELIVERY”, the Near-RT RIC platform shall send a TRAINING RESPONSE message back to the xApp to acknowledge the request. The Near-RT RIC platform then performs the training. The training result is provided to xApp via Training Result Delivery Procedure. - -If the TRAINING REQUEST is accepted and *Result Delivery Method* IE in *Training Job Setup* IE is set to “RESPONSE”, the Near-RT RIC platform shall send a TRAINING RESPONSE message back to the xApp after it finishes the requested training. In the TRAINING REQUEST RESPONSE message, the Near-RT RIC platform shall include the *Training Result* IE. - -#### 9A.2.3.5.2 Unsuccessful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. TRAINING REQUEST -RICP -> xApp : 2. TRAINING FAILURE -@enduml -``` - -![Sequence diagram for Figure 9A.2.3.5.2-1: Model Request procedure, unsuccessful operation. It shows an xApp sending a '1. TRAINING REQUEST' to a Near-RT RIC Platform, which responds with '2. TRAINING FAILURE'.](3220d3a933797114c1ba20d5c4ec093d_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. TRAINING REQUEST - Near-RT RIC Platform-->>xApp: 2. TRAINING FAILURE - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for Figure 9A.2.3.5.2-1: Model Request procedure, unsuccessful operation. It shows an xApp sending a '1. TRAINING REQUEST' to a Near-RT RIC Platform, which responds with '2. TRAINING FAILURE'. - -**Figure 9A.2.3.5.2-1: Model Request procedure, unsuccessful operation** - -If the TRAINING REQUEST fails, the Near-RT RIC platform shall send a TRAINING FAILURE message back to the xApp. The message shall include the appropriate cause. - -**9A.2.3.5.3 Abnormal Conditions** - -Not applicable. - -**9A.2.3.6 Training Result Delivery procedure** - -**9A.2.3.6.1 Successful Operation** - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICH as "Near-RT RIC Platform" -RICH -> xApp : 2. TRAINING RESULT DELIVERY -@enduml - -``` - -![Sequence diagram for Figure 9A.2.3.6.1-1: Training Result Delivery procedure. It shows an xApp sending a '2. TRAINING RESULT DELIVERY' message to a Near-RT RIC Platform.](84a9ebc99b18f354f989e127c0974a26_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 2. TRAINING RESULT DELIVERY - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for Figure 9A.2.3.6.1-1: Training Result Delivery procedure. It shows an xApp sending a '2. TRAINING RESULT DELIVERY' message to a Near-RT RIC Platform. - -**Figure 9A.2.3.6.1-1: Training Result Delivery procedure** - -The xApp initiates the procedure by sending a TRAINING RESULT DELIVERY message to the Near-RT RIC platform. The message contains *Training Result IE*, which carries the training result. - -**9A.2.3.6.2 Abnormal Conditions** - -Not applicable. - -**9A.2.4 Model Management and Exposure API Procedures** - -**9A.2.4.1 General** - -This procedure is used by an xApp that wants to store an AI/ML model in Near-RT RIC platform. - -## 9A.2.4.2 Model Store procedure - -### 9A.2.4.2.1 Successful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. MODEL STORE REQUEST -RICP -> xApp : 2. MODEL STORE RESPONSE -@enduml -``` - -![Sequence diagram for the successful Model Store procedure. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. MODEL STORE REQUEST' message to the Near-RT RIC Platform, and the platform responds with a '2. MODEL STORE RESPONSE' message back to the xApp.](2f108a589e99e93fd7aa8fac626398c7_img.jpg) - -``` -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. MODEL STORE REQUEST - RICP-->>xApp: 2. MODEL STORE RESPONSE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform -``` - -Sequence diagram for the successful Model Store procedure. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. MODEL STORE REQUEST' message to the Near-RT RIC Platform, and the platform responds with a '2. MODEL STORE RESPONSE' message back to the xApp. - -**Figure 9A.2.4.2.1-1: Model Store procedure, successful operation** - -The xApp initiates the procedure by sending a MODEL STORE REQUEST message to the Near-RT-RIC platform. The message contains *Model Related Information* IE which carries the information of an AI/ML model. It shall contain either the *Model File* IE, or the *Model Location* IE that is used by the Near-RT RIC platform to obtain the AI/ML model. - -At reception of the MODEL STORE REQUEST message, the Near-RT RIC platform shall retrieve the AI/ML model file according to the *Model Location* IE or from the received *Model File* IE payload, and store it in the Near-RT RIC platform. If the *Model ID* IE in the *Model Related Information* IE conflicts with an already stored *Model ID* or the *Artifact Version* IE in the *Model ID* IE is absent, the Near-RT RIC platform shall assign a new artifact version to the AI/ML model. - -If the MODEL STORE REQUEST is successfully fulfilled, the Near-RT RIC platform shall send a MODEL STORE RESPONSE message back to the xApp. In the MODEL STORE RESPONSE message, the Near-RT RIC platform shall include the *Model ID* IE. When the Near-RT RIC platform has assigned a new artifact version for the AI/ML model, the *Model ID* IE shall use the new artifact version for its *Artifact Version* IE. - -### 9A.2.4.2.2 Unsuccessful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. MODEL STORE REQUEST -RICP -> xApp : 2. MODEL STORE FAILURE -@enduml -``` - -![Sequence diagram for Model Store procedure, unsuccessful operation. Lifelines: xApp and Near-RT RIC Platform. Message 1: MODEL STORE REQUEST from xApp to Near-RT RIC Platform. Message 2: MODEL STORE FAILURE from Near-RT RIC Platform back to xApp.](47702b55f927e2e85ac03e79a7ebe350_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. MODEL STORE REQUEST - Near-RT RIC Platform-->>xApp: 2. MODEL STORE FAILURE - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for Model Store procedure, unsuccessful operation. Lifelines: xApp and Near-RT RIC Platform. Message 1: MODEL STORE REQUEST from xApp to Near-RT RIC Platform. Message 2: MODEL STORE FAILURE from Near-RT RIC Platform back to xApp. - -**Figure 9A.2.4.2.2-1: Model Store procedure, unsuccessful operation** - -If the MODEL STORE REQUEST fails, the Near-RT RIC platform shall send a MODEL STORE FAILURE message back to the xApp. The message shall include the appropriate cause. - -**9A.2.4.2.3 Abnormal Conditions** - -Not applicable. - -**9A.2.4.3 Stored Model Query procedure** - -**9A.2.4.3.1 Successful Operation** - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp -> RICP : 1. STORED MODEL QUERY REQUEST -RICP -> xApp : 2. STORED MODEL QUERY RESPONSE -@enduml - -``` - -![Sequence diagram for Stored Model Query procedure, successful operation. Lifelines: xApp and Near-RT RIC Platform. Message 1: STORED MODEL QUERY REQUEST from xApp to Near-RT RIC Platform. Message 2: STORED MODEL QUERY RESPONSE from Near-RT RIC Platform back to xApp.](363ee388a0fafdba587655050cf079d4_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. STORED MODEL QUERY REQUEST - Near-RT RIC Platform-->>xApp: 2. STORED MODEL QUERY RESPONSE - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for Stored Model Query procedure, successful operation. Lifelines: xApp and Near-RT RIC Platform. Message 1: STORED MODEL QUERY REQUEST from xApp to Near-RT RIC Platform. Message 2: STORED MODEL QUERY RESPONSE from Near-RT RIC Platform back to xApp. - -**Figure 9A.2.4.3.1-1: Stored Model Query procedure, successful operation** - -The xApp initiates the procedure by sending a STORED MODEL QUERY REQUEST message to the Near-RT RIC platform. The message contains the *Model ID Filter List* IE, which represents the selection criteria of queried AI/ML models. - -At reception of the STORED MODEL QUERY REQUEST message, the Near-RT RIC platform shall look up the *Model Related Information* IE of all the stored AI/ML models that matches the *Model ID Filter List* IE. If *Model ID Filter List* IE is absent, the Near-RT RIC platform shall look up all the stored AI/ML model(s) stored by the xApp. - -If the STORED MODEL QUERY REQUEST is successfully fulfilled, the Near-RT RIC platform shall send a STORED MODEL QUERY RESPONSE message back to the xApp. In the STORED MODEL QUERY RESPONSE message, the Near-RT RIC platform shall include the *Model Related Information List* IE for all the stored AI/ML models that match the selection criteria given in the request, if such AI/ML model exists. Otherwise, the *Model Related Information List* IE shall be absent. - -### 9A.2.4.3.2 Unsuccessful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp ->> RICP : 1. STORED MODEL QUERY REQUEST -RICP -->> xApp : 2. STORED MODEL QUERY FAILURE -@enduml -``` - -![Sequence diagram for Unsuccessful Stored Model Query procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: STORED MODEL QUERY REQUEST from xApp to RICP. Message 2: STORED MODEL QUERY FAILURE from RICP to xApp.](18b87e4ce7ef441f5620b8d6539a2939_img.jpg) - -``` -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. STORED MODEL QUERY REQUEST - RICP-->>xApp: 2. STORED MODEL QUERY FAILURE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform -``` - -Sequence diagram for Unsuccessful Stored Model Query procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: STORED MODEL QUERY REQUEST from xApp to RICP. Message 2: STORED MODEL QUERY FAILURE from RICP to xApp. - -**Figure 9A.2.4.3.2-1: Stored Model Query procedure, unsuccessful operation** - -If the STORED MODEL QUERY REQUEST fails, the Near-RT RIC platform shall send a STORED MODEL QUERY FAILURE message back to the xApp. The message shall include the appropriate cause. - -### 9A.2.4.3.3 Abnormal Conditions - -Not applicable. - -## 9A.2.4.4 Model Retrieve procedure - -### 9A.2.4.4.1 Successful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp ->> RICP : 1. MODEL RETRIEVE REQUEST -RICP -->> xApp : 2. MODEL RETRIEVE RESPONSE -@enduml -``` - -![Sequence diagram for Successful Model Retrieve procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: MODEL RETRIEVE REQUEST from xApp to RICP. Message 2: MODEL RETRIEVE RESPONSE from RICP to xApp.](d01f4371bb8136148156771a18b9ea89_img.jpg) - -``` -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. MODEL RETRIEVE REQUEST - RICP-->>xApp: 2. MODEL RETRIEVE RESPONSE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform -``` - -Sequence diagram for Successful Model Retrieve procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: MODEL RETRIEVE REQUEST from xApp to RICP. Message 2: MODEL RETRIEVE RESPONSE from RICP to xApp. - -**Figure 9A.2.4.4.1-1: Model Retrieve procedure, successful operation** - -The xApp initiates the procedure by sending a MODEL RETRIEVE REQUEST message to the Near-RT-RIC platform. The message contains *Model ID* IE, which represents the identifier of the retrieved AI/ML model. - -At reception of the MODEL RETRIEVE REQUEST message, the Near-RT-RIC platform shall search for stored AI/ML model that matches the *Model ID IE*. - -If the MODEL RETRIEVE REQUEST is successfully fulfilled, the Near-RT RIC platform shall send a MODEL RETRIEVE RESPONSE message back to the xApp. In the MODEL RETRIEVE RESPONSE message, the Near-RT RIC platform shall include the *Model ID IE*, and either the *Model URI IE* or *Model File IE* of the requested AI/ML model. - -#### 9A.2.4.4.2 Unsuccessful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp ->> RICP : 1. MODEL RETRIEVE REQUEST -RICP ->> xApp : 2. MODEL RETRIEVE FAILURE -@enduml -``` - -![Sequence diagram for Model Retrieve procedure, unsuccessful operation. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. MODEL RETRIEVE REQUEST' message to the Near-RT RIC Platform. The Near-RT RIC Platform responds with a '2. MODEL RETRIEVE FAILURE' message back to the xApp.](2d51fdeaad10ae6f1707dd372d200e23_img.jpg) - -``` -sequenceDiagram - participant xApp - participant RICP as Near-RT RIC Platform - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform - xApp->>RICP: 1. MODEL RETRIEVE REQUEST - RICP-->>xApp: 2. MODEL RETRIEVE FAILURE - Note left of xApp: xApp - Note right of RICP: Near-RT RIC Platform -``` - -Sequence diagram for Model Retrieve procedure, unsuccessful operation. It shows two lifelines: xApp and Near-RT RIC Platform. The xApp sends a '1. MODEL RETRIEVE REQUEST' message to the Near-RT RIC Platform. The Near-RT RIC Platform responds with a '2. MODEL RETRIEVE FAILURE' message back to the xApp. - -Figure 9A.2.4.4.2-1: Model Retrieve procedure, unsuccessful operation - -If the MODEL RETRIEVE REQUEST fails, the Near-RT RIC platform shall send a MODEL RETRIEVE FAILURE message back to the xApp. The message shall include the *Model ID IE* and appropriate cause. - -#### 9A.2.4.4.3 Abnormal Conditions - -Not applicable. - -### 9A.2.4.5 Model Delete procedure - -#### 9A.2.4.5.1 Successful Operation - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICP as "Near-RT RIC Platform" -xApp ->> RICP : 1. MODEL DELETE REQUEST -RICP ->> xApp : 2. MODEL DELETE RESPONSE -@enduml -``` - -![Sequence diagram for successful Model Delete procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: MODEL DELETE REQUEST from xApp to Near-RT RIC Platform. Message 2: MODEL DELETE RESPONSE from Near-RT RIC Platform to xApp.](a76fa39f5daf6a026e032495262ed0f6_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. MODEL DELETE REQUEST - Near-RT RIC Platform-->>xApp: 2. MODEL DELETE RESPONSE - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for successful Model Delete procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: MODEL DELETE REQUEST from xApp to Near-RT RIC Platform. Message 2: MODEL DELETE RESPONSE from Near-RT RIC Platform to xApp. - -**Figure 9A.2.4.5.1-1: Model Delete procedure, successful operation** - -The xApp initiates the procedure by sending a MODEL DELETE REQUEST message to the Near-RT-RIC platform. The message contains *Model ID List* IE, which represents the list of identifiers of the AI/ML models the xApp requests to delete. - -At reception of the MODEL DELETE REQUEST message, the Near-RT-RIC platform shall delete the stored AI/ML model files and associated information according to the *Model ID List* IE. - -If the MODEL DELETE REQUEST is successfully fulfilled, the Near-RT RIC platform shall send a MODEL DELETE RESPONSE message back to the xApp. In the MODEL DELETE RESPONSE message, the Near-RT RIC platform shall include the *Model ID Deleted List* IE to indicate the list of deleted AI/ML models, and the *Model ID Not Deleted List* IE to indicate the list of AI/ML models that are not successfully deleted, if any. - -**9A.2.4.5.2 Unsuccessful Operation** - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy dashed -Participant xApp as "xApp" -Participant RICH as "Near-RT RIC Platform" -xApp ->> RICH : 1. MODEL DELETE REQUEST -RICH -->> xApp : 2. MODEL DELETE FAILURE -@enduml - -``` - -![Sequence diagram for unsuccessful Model Delete procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: MODEL DELETE REQUEST from xApp to Near-RT RIC Platform. Message 2: MODEL DELETE FAILURE from Near-RT RIC Platform to xApp.](f4e64712104f326ff259928d8126f1f6_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC Platform - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - xApp->>Near-RT RIC Platform: 1. MODEL DELETE REQUEST - Near-RT RIC Platform-->>xApp: 2. MODEL DELETE FAILURE - Note left of xApp: xApp - Note right of Near-RT RIC Platform: Near-RT RIC Platform - -``` - -Sequence diagram for unsuccessful Model Delete procedure. Lifelines: xApp and Near-RT RIC Platform. Message 1: MODEL DELETE REQUEST from xApp to Near-RT RIC Platform. Message 2: MODEL DELETE FAILURE from Near-RT RIC Platform to xApp. - -**Figure 9A.2.4.5.2-1: Model Delete procedure, unsuccessful operation** - -If the MODELDELETE REQUEST fails, the Near-RT RIC platform shall send a MODEL DELETE FAILURE message back to the xApp. The message shall include the appropriate cause. - -**9A.2.4.4.3 Abnormal Conditions** - -Not applicable. - -## 9A.3 Elements for AI/ML API Communication - -### 9A.3.1 General - -### 9A.3.2 Message Functional Definition and Content - -#### 9A.3.2.1 DATA PIPELINING JOB SETUP REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to create a data pipelining job. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Data Pipelining Job Description | M | | 9A.3.3.23 | | - -#### 9A.3.2.2 DATA PIPELINING JOB SETUP RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to indicate success of creating a data pipelining job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Data Pipelining Job ID | M | | 9A.3.3.24 | | - -#### 9A.3.2.3 DATA PIPELINING JOB SETUP FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of creating a data pipelining job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Cause | M | | 9A.3.3.10 | | - -#### 9A.3.2.4 DATA PIPELINING JOB UPDATE REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to update a data pipelining job. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Data Pipelining Job ID | M | | 9A.3.3.24 | | - -| | | | | | -|---------------------------------|---|--|-----------|--| -| Data Pipelining Job Description | M | | 9A.3.3.23 | | -|---------------------------------|---|--|-----------|--| - -### 9A.3.2.5 DATA PIPELINING JOB UPDATE RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to indicate success of updating a data pipelining job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Data Pipelining Job ID | M | | 9A.3.3.24 | | - -### 9A.3.2.6 DATA PIPELINING JOB UPDATE FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of updating a data pipelining job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Data Pipelining Job ID | M | | 9A.3.3.24 | | -| Cause | M | | 9A.3.3.10 | | - -### 9A.3.2.7 DATA PIPELINING JOB DELETE REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to delete a data pipelining job. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Data Pipelining Job ID | M | | 9A.3.3.24 | | - -### 9A.3.2.8 DATA PIPELINING JOB DELETE RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to indicate success of deleting the data pipelining job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Data Pipelining Job ID | M | | 9A.3.3.24 | | - -### 9A.3.2.9 DATA PIPELINING JOB DELETE FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of deleting the data pipelining job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Data Pipelining Job ID | M | | 9A.3.3.24 | | -| Cause | M | | 9A.3.3.10 | | - -### 9A.3.2.10 DATA PIPELINING JOB QUERY REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to query the status of a data pipelining job. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Data Pipelining Job ID | M | | 9A.3.3.24 | | - -### 9A.3.2.11 DATA PIPELINING JOB QUERY RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to carry the status of the queried data pipelining job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|----------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Data Pipelining Job ID | M | | 9A.3.3.24 | | -| Data Pipelining Job Status | M | | 9A.3.3.25 | | - -### 9A.3.2.12 DATA PIPELINING JOB QUERY FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of querying the data pipelining job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Data Pipelining Job ID | M | | 9A.3.3.24 | | -| Cause | M | | 9A.3.3.10 | | - -### 9A.3.2.13 DATA PIPELINING REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to perform a data pipelining. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Data Pipelining Job ID | M | | 9A.3.3.24 | | -| Data Pipelining Request Description | M | | 9A.3.3.26 | | - -### 9A.3.2.14 DATA PIPELINING RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to indicate the DATA PIPELINING REQUEST is accepted. It also carries the data pipelining result if configured by the *Data Pipelining Job Description* IE when creating/updating the data pipelining job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Data Pipelining Job ID | M | | 9A.3.3.24 | | -| Data Pipelining Result | C | | 9A.3.3.27 | Shall be present if the Result Delivery Method IE in the Data Pipelining Job Description IE is set to "Response" | - -### 9A.3.2.15 DATA PIPELINING FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate the DATA PIPELINING REQUEST is rejected. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Data Pipelining Job ID | M | | 9A.3.3.24 | | -| Cause | M | | 9A.3.3.10 | | - -### 9A.3.2.16 DATA PIPELINING RESULT DELIVERY - -This message is sent by Near-RT RIC platform to xApp to deliver the result of data pipelining, if configured by the *Data Pipelining Job Description* IE when creating/updating the data pipelining job. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Data Pipelining Job ID | M | | 9A.3.3.24 | | -| Data Pipelining Result | M | | 9A.3.3.27 | | - -### 9A.3.2.17 INFERENCE JOB SETUP REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to set up an AI/ML model inference job. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Inference Job Description | M | | 9A.3.3.18 | | - -### 9A.3.2.18 INFERENCE JOB SETUP RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to indicate success of creating an AI/ML model inference job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Inference Job ID | M | | 9A.3.3.19 | | - -### 9A.3.2.19 INFERENCE JOB SETUP FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of creating an AI/ML model inference job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Cause | M | | 9A.3.3.10 | | - -### 9A.3.2.20 INFERENCE JOB UPDATE REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to update an AI/ML model inference job. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Inference Job ID | M | | 9A.3.3.19 | | -| Inference Job Description | M | | 9A.3.3.18 | | - -### 9A.3.2.21 INFERENCE JOB UPDATE RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to indicate success of updating an AI/ML model inference job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Inference Job ID | M | | 9A.3.3.19 | | - -### 9A.3.2.22 INFERENCE JOB UPDATE FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of updating an AI/ML model inference job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Inference Job ID | M | | 9A.3.3.19 | | -| Cause | M | | 9A.3.3.10 | | - -### 9A.3.2.23 INFERENCE JOB DELETE REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to delete an AI/ML model inference job. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Inference Job ID | M | | 9A.3.3.19 | | - -### 9A.3.2.24 INFERENCE JOB DELETE RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to indicate success of deleting the AI/ML model inference job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Inference Job ID | M | | 9A.3.3.19 | | - -### 9A.3.2.25 INFERENCE JOB DELETE FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of deleting the AI/ML model inference job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | - -| | | | | | -|------------------|---|--|-----------|--| -| Inference Job ID | M | | 9A.3.3.19 | | -| Cause | M | | 9A.3.3.10 | | - -### 9A.3.2.26 INFERENCE JOB QUERY REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to query the status of an AI/ML model inference job. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Inference Job ID | M | | 9A.3.3.19 | | - -### 9A.3.2.27 INFERENCE JOB QUERY RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to carry the status of the queried AI/ML model inference job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Inference Job ID | M | | 9A.3.3.19 | | -| Inference Job Status | M | | 9A.3.3.20 | | - -### 9A.3.2.28 INFERENCE JOB QUERY FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of querying the AI/ML model inference job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Inference Job ID | M | | 9A.3.3.19 | | -| Cause | M | | 9A.3.3.10 | | - -### 9A.3.2.29 INFERENCE REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to perform an AI/ML model inference. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Inference Job ID | M | | 9A.3.3.19 | | -| Inference Request Description | M | | 9A.3.3.21 | | - -### 9A.3.2.30 INFERENCE RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to indicate the INFERENCE REQUEST is accepted. It also carries the inference result if configured by the *Inference Job Description* IE when creating/updating the inference job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Inference Job ID | M | | 9A.3.3.19 | | -| Inference Result | C | | 9A.3.3.22 | Shall be present if the Result Delivery Method IE in the Inference Job Description IE is set to "Response" | - -### 9A.3.2.31 INFERENCE FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate the INFERENCE REQUEST is rejected. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Inference Job ID | M | | 9A.3.3.19 | | -| Cause | M | | 9A.3.3.10 | | - -### 9A.3.2.32 INFERENCE RESULT DELIVERY - -This message is sent by Near-RT RIC platform to xApp to deliver the result of AI/ML model inference, if configured by the *Inference Job Description* IE when creating/updating the inference job. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Inference Job ID | M | | 9A.3.3.19 | | -| Inference Result | M | | 9A.3.3.22 | | - -### 9A.3.2.33 TRAINING JOB SETUP REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to set up an AI/ML model training job. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Training Job Description | M | | 9A.3.3.11 | | - -### 9A.3.2.34 TRAINING JOB SETUP RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to indicate success of setting up an AI/ML model training job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Training Job ID | M | | 9A.3.3.12 | | - -### 9A.3.2.35 TRAINING JOB SETUP FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of setting up an AI/ML model training job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Cause | M | | 9A.3.3.10 | | - -### 9A.3.2.36 TRAINING JOB DELETE REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to delete an AI/ML model training job. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Training Job ID | M | | 9A.3.3.12 | | - -### 9A.3.2.37 TRAINING JOB DELETE RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to indicate success of deleting the AI/ML model training job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Training Job ID | M | | 9A.3.3.12 | | - -### 9A.3.2.38 TRAINING JOB DELETE FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of deleting the AI/ML model training job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|-----------------------| -|---------------|----------|-------|-----------------------|-----------------------| - -| | | | | | -|--------------------------|---|--|-----------|--| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Training Job ID | M | | 9A.3.3.12 | | -| Cause | M | | 9A.3.3.10 | | - -### 9A.3.2.39 TRAINING JOB QUERY REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to query the status of an AI/ML model training job. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Training Job ID | M | | 9A.3.3.12 | | - -### 9A.3.2.40 TRAINING JOB QUERY RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to carry the status of the queried AI/ML model training job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Training Job Status | M | | 9A.3.3.13 | | - -### 9A.3.2.41 TRAINING JOB QUERY FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of querying the AI/ML model training job. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Training Job ID | M | | 9A.3.3.12 | | -| Cause | M | | 9A.3.3.10 | | - -### 9A.3.2.42 TRAINING REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to perform an AI/ML model training. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Training Job ID | M | | 9A.3.3.12 | | - -| | | | | | -|------------------------------|---|--|-----------|--| -| Training Request Description | M | | 9A.3.3.14 | | -|------------------------------|---|--|-----------|--| - -### 9A.3.2.43 TRAINING RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to indicate success of performing an AI/ML model training. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Training Job ID | M | | 9A.3.3.12 | | -| Training Result | C | | 9A.3.3.15 | Shall be present if the Result Delivery Method IE in the TRAINING JOB SETUP REQUEST message is set to "Response" | - -### 9A.3.2.44 TRAINING FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of performing an AI/ML model training. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Training Job ID | M | | 9A.3.3.12 | | -| Cause | M | | 9A.3.3.10 | | - -### 9A.3.2.45 TRAINING RESULT DELIVERY - -This message is sent by Near-RT RIC platform to xApp to deliver the result of AI/ML model training. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Training Job ID | M | | 9A.3.3.12 | | -| Training Result | M | | 9A.3.3.15 | | - -### 9A.3.2.46 MODEL STORE REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to store an AI/ML model. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Model Related Information | M | | 9A.3.3.2 | | - -| | | | | | -|--------------------------------------------------------------------------|---|--|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------| -| Model File | O | | 9A.3.3.7 | (NOTE) | -| Model Location | O | | 9A.3.3.9 | Contains a URI. The URI points to the location where the Near-RT RIC platform can obtain the model file, e.g., a FTP server hosted by the xApp. (NOTE) | -| NOTE: Either Model File or Model Location shall be present | | | | | - -### 9A.3.2.47 MODEL STORE RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to indicate success of the storing of an AI/ML model. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Model ID | M | | 9A.3.3.3 | | - -### 9A.3.2.48 MODEL STORE FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of the storing of an AI/ML model. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Cause | M | | 9A.3.3.10 | | - -### 9A.3.2.49 STORED MODEL QUERY REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to query stored AI/ML model information. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-----------------------------|-----------------------|--------------------------------------------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Model ID Filter List | | 0...1 | | Logical "OR" is applied across multiple filter items. | -| > Model ID Filter Item | | 1.. | | If absent, the query is for all the stored AI/ML model | -| >> Model ID Filter | M | | 9A.3.3.8 | | - -| Range bound | Explanation | -|-------------------------------|-----------------------------------------------------------------------------| -| maxn ofModel IdFilters | Maximum number of data types that can be indicated as input. Value is 2048. | - -### 9A.3.2.50 STORED MODEL QUERY RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to carry the information of queried AI/ML model. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|----------------------------------|----------|-----------------------------------------------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Model Related Information List | | 0..1 | | | -| > Model Related Information Item | | 1... < maxnoof ModelRelatedInformationItems > | | | -| >> Model Related Information | M | | 9A.3.3.2 | | - -| Range bound | Explanation | -|-------------------------------------|-------------------------------------------------------------------------------------------------------------------| -| maxnoofModelRelatedInformationItems | Maximum number of ModelRelatedInformationItem that can be carried in a ModelRelatedInformationList. Value is 256. | - -### 9A.3.2.51 STORED MODEL QUERY FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of the query of AI/ML model information. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Cause | M | | 9A.3.3.10 | | - -### 9A.3.2.52 MODEL RETRIEVE REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to retrieve a stored AI/ML model. - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Model ID | M | | 9A.3.3.3 | | - -### 9A.3.2.53 MODEL RETRIEVE RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to carry the URI of retrieved AI/ML model file. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------------------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Model ID | M | | 9A.3.3.3 | | -| Model URI | O | | 9A.3.3.9 | Contains the URI of the AI/ML model. (NOTE 1) | -| Model File | O | | 9A.3.3.7 | (NOTE 1) | - -NOTE 1: Either *Model URI* or *Model File* shall be present - -### 9A.3.2.54 MODEL RETRIEVE FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure of the retrieving of the URI of AI/ML model file. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Model ID | M | | 9A.3.3.3 | | -| Cause | M | | 9A.3.3.10 | | - -### 9A.3.2.55 MODEL DELETE REQUEST - -This message is sent by an xApp to the Near-RT RIC platform to delete stored AI/ML model(s). - -Direction: xApp -> Near-RT RIC platform - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|------------------------------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Model ID List | | 1 | | | -| > Model ID Item | | 1..oofModel
IDs> | | | -| >> Model ID | M | | 9A.3.3.3 | | - -### 9A.3.2.56 MODEL DELETE RESPONSE - -This message is sent by Near-RT RIC platform to the xApp to indicate success of the deleting of an AI/ML model. - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------------|----------|------------------------------|-----------------------|--------------------------------------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Model ID Deleted List | | 1 | | The Model IDs that are successfully deleted. | -| > Model ID Item | | 1..oofModel
IDs> | | | -| >> Model ID | M | | 9A.3.3.3 | | -| Model ID Not Deleted List | | 0..1 | | The Model IDs that are not successfully deleted. | -| > Model ID Item | | 1..oofModel
IDs> | | | -| >> Model ID | M | | 9A.3.3.3 | | - -## 9A.3.2.57 MODEL DELETE FAILURE - -This message is sent by Near-RT RIC platform to the xApp to indicate failure in deleting AI/ML model(s). - -Direction: Near-RT RIC platform -> xApp - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------|----------|-------|-----------------------|-----------------------| -| Message Type | M | | 9A.3.3.1 | | -| Procedure Transaction ID | M | | 10.1.1 | | -| Cause | M | | 9A.3.3.10 | | - -## 9A.3.3 Information Element Definitions - -### 9A.3.3.1 Message Type - -This IE identifies the message being sent. It is mandatory for all messages. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-----------------|----------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------| -| Procedure Type | M | | CHOICE (Data Pipelining Job Setup, Data Pipelining Job Update, Data Pipelining Job Delete, Data Pipelining Job Query, Data Pipelining Request, Data Pipelining Result Delivery, Inference Job Setup, Inference Job Update, Inference Job Delete, Inference Job Query, Inference Request, Inference Result Delivery, Training Job Setup, Training Job Delete, Training Job Query, Training Request, Training Result Delivery, Model Store, Stored Model Query, Model Retrieve, Model Delete, ...) | | -| Type of Message | M | | CHOICE (REQUEST, RESPONSE, FAILURE, ...) | Refer to Table 9A.1.2-3 for applicable choices for each procedure type | - -### 9A.3.3.2 Model Related Information - -This IE contains the related information of an AI/ML model. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------------|----------|----------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Model ID | M | | 9A.3.3.3 | Identifier of a model | -| Description | M | | STRING | Description of the AIML model | -| Model Information | M | | - | Information of the AIML model | -| > Metadata | M | | - | Metadata of the model. | -| >> Author | M | | STRING | Author of the AIML model. | -| >> Owner | O | | STRING | Ownership of the AIML model to regulate how the model can be used in the Run-Time environment. | -| > Input Data Type List | | 1 | | | -| >> Input Data Type Item | | 1.. | | | -| >>> Input Data Type ID | M | | STRING | Input data type ID for the model, e.g., "INT8", "FP16", "FP32", etc.
If the Input Data Type List has only a single Input Data Type ID, then the Input Data Type ID is applied to all the values in the input dataset. | -| > Input Data Shape | O | | STRING | Indicates the shape of multi-dimensional data in an input data block. The string shall be a sequence of | - -| | | | | | -|----------------------------|---|----------------------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | integers separated by “;” where the n-th integer represents the length of the n-th dimension. This IE may be absent if the data is one-dimensional. | -| > Output Data Type List | | 1 | | | -| >> Output Data Type Item | | 1.. | | | -| >>> Output Data Type ID | M | | STRING | Output data type ID for the model, e.g., “INT8”, “FP16”, “FP32”, etc.
If the Output Data Type List has only a single Output Data Type ID, then the Output Data Type ID is applied to all the values in the output dataset. | -| > Output Data Shape | O | | STRING | Indicates the shape of multi-dimensional data in an output data block. The string shall be a sequence of integers separated by “;” where the n-th integer represents the length of the n-th dimension. This IE may be absent if the data is one-dimensional. | -| > Target Environment List | O | | - | Information on the target environment is required for deployment of an AI/ML model. | -| >> Target Environment Item | | | | | -| >>> Platform Name | M | | STRING | Name of the platform for model operations. | -| >>> Environment Type | M | | STRING | Name of the platform execution service type, and this is dependent on the Platform Name. | -| >>> Dependency List | M | | 9A.3.3.9 | Contains a URI. The URI points to a list of dependencies that the platform must provide needs to be installed for the model (for example, scikit-learn 0.21.3). | - -| Range bound | Explanation | -|------------------------|------------------------------------------------------------------------------| -| maxnoofInputDataTypes | Maximum number of data types that can be indicated as input. Value is 2048. | -| maxnoofOutputDataTypes | Maximum number of data types that can be indicated as output. Value is 2048. | - -### 9A.3.3.3 Model ID - -This IE contains the identifier of an AI/ML model. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|-------|-----------------------|---------------------------------------------------------------------------------------------------------------------| -| Model Name | M | | 9A.3.3.4 | Name of the model | -| Model Version | M | | 9A.3.3.5 | Version of the model | -| Artifact Version | C | | 9A.3.3.6 | Artifact version of the model. It may be absent in the MODEL STORE REQUEST message, and shall be present otherwise. | - -NOTE: An AI/ML model is identified by a model identifier, which includes model name, model version and artifact version [13]. The model name and model version are not changed after onboarding or after xApp deployment with the AI/ML model, or after training within the Near-RT RIC. If the AI/ML model needs to be upgraded, the cloud native application developer updates the model version, and the upgraded model is onboarded as part of a new xApp package. - -The onboarded AI/ML model comes pre-trained, or is specialized during onboarding, and this is reflected in the initial value of the artifact version of the AI/ML model. After the registered AI/ML model has been trained within the Near-RT RIC, the artifact version is updated. - -### 9A.3.3.4 Model Name - -This IE defined the name of an AI/ML model. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|-----------------------| -| Model Name | M | | STRING | | - -### 9A.3.3.5 Model Version - -This IE defined the version of an AI/ML model. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|-----------------------| -| Model Version | M | | STRING | | - -### 9A.3.3.6 Artifact Version - -This IE defined the artifact of an AI/ML model. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|-------|-----------------------|-----------------------| -| Artifact Version | M | | STRING | | - -### 9A.3.3.7 Model File - -This IE contains an AI/ML model file. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| -| File Format | M | | STRING | AI/ML model file format description.
In the present document, the following values are supported:
- “ONNX”. | -| File Data | M | | OCTET STRING | It is recommended to use the IE to contain a model file only when the file size is small. Protocol Buffers restrict the message size smaller than 2GB. | - -### 9A.3.3.8 Model ID Filter - -This IE contains the selection criteria of AI/ML model(s). Logical “AND” is applied across its multiple sub-IEs, if present. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|-------|-----------------------|------------------------------------------------| -| Model Name | M | | 9A.3.3.4 | Used to match the model name of a model ID. | -| Model Version | O | | 9A.3.3.5 | Used to match the model version of a model ID. | -| Artifact Version | O | | 9A.3.3.6 | Used to match the artifact of a model ID. | - -### 9A.3.3.9 URI - -This IE contains a URI address. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|-----------------------| -| URI | M | | STRING | | - -### 9A.3.3.10 Cause - -The Cause IE indicates the reason for a particular event in AI/ML API. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| -| Cause | M | | ENUMERATED (Unspecified, System busy, Storage reached capacity, Dataset problem, Invalid Request, Model access denied, Invalid model ID, ...) | | - -The meaning of the different cause values is described in the following table. - -| Cause value | Meaning | -|---------------------|------------------------------------------------------------------------------| -| Unspecified | Sent when none of the below cause values applies. | -| System busy | The system cannot process the request due to temporary overload. | -| Dataset problem | The dataset provided has problem | -| Invalid Request | The REQUEST message is invalid. | -| Model access denied | The Near-RT RIC platform cannot access the provided location of AI/ML model. | -| Invalid model ID | The provided Model ID is not found, or not complete | - -### 9A.3.3.11 Training Job Description - -This IE identifies the training job descriptions. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------------------------------------------|----------|-------|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| -| CHOICE Model Source | | | | | -| > MME | | | | | -| >> Model ID | M | | 9A.3.3.3 | Identifier of the AI/ML model to be trained. Mandatory if Model Source is "MME" | -| > New Model | | | | | -| >> Model Related Information | M | | 9A.3.3.2 | Related information of the AI/ML model. Mandatory if Model Source is "New Model" | -| >> Model URI | O | | 9A.3.3.9 | URI Location of the AI/ML model. Mandatory if Model File is not present. (NOTE 1) | -| >> Model File | O | | 9A.3.3.7 | AI/ML Model File. Mandatory if Model URI is not present. (NOTE 1) | -| Result Delivery Method | M | | ENUMERATED (RESPONSE, DELIVER, ...) | Indicates If the training result is included in Training Response or in a later Training Result Delivery message. | -| Trained Model Delivery Type | M | | ENUMERATED (Model URI, Model File, ...) | Indicates If the newly trained model is delivered through URI or as a file contained in the message. | -| Result Delivery Destination | C | | 10.1.9 | Indicates the destination address to send the Training Result Delivery message. Shall be present if the Result Delivery Method IE is set to "Delivery". | -| NOTE 1: Either Model URI or Model File shall be present | | | | | - -### 9A.3.3.12 Training Job ID - -This IE identifies the training job ID. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-----------------|----------|-------|-----------------------|--------------------------------| -| Training Job ID | M | | STRING | Identifier of the training job | - -### 9A.3.3.13 Training Job Status - -This IE identifies the training job status. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------|----------|-------|---------------------------------------------------------------------------------|-----------------------| -| Training Job Status | M | | ENUMERATED (Unspecified, Training, Validating, Suspended, Finished, Error, ...) | | - -### 9A.3.3.14 Training Request Description - -This IE contains the information of training job descriptions. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------| -| Training Request Description | M | | - | | -| > Training Dataset | O | | 9A.3.3.16 | AI/ML Model training Data Set | -| > Validation Dataset | O | | 9A.3.3.16 | AI/ML Model validation Data Set | -| > Training Dataset URI | C | | 9A.3.3.9 | The URI points to the location where the Near-RT RIC platform can obtain the training dataset. | -| > Validation Dataset URI | C | | 9A.3.3.9 | The URI points to the location where the Near-RT RIC platform can obtain the validation dataset. | - -### 9A.3.3.15 Training Result - -This IE contains the training job result. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-----------------|----------|-------|------------------------------------|----------------------------------------------------------------------------------------------| -| Training Result | M | | - | | -| > Result | M | | ENUMERATED (SUCCESS, FAILURE, ...) | If the training is successful or not | -| > Model ID | O | | 9A.3.3.3 | Newly assigned AI/ML model ID. Shall be absent if Result IE is "FAILURE".
(NOTE 1) | -| > Model URI | C | | 9A.3.3.9 | URI Location of the model stored in the Near-RT RIC that can be accessed.
(NOTE 2) | -| > Model File | C | | 9A.3.3.7 | AI/ML Model File.
(NOTE 3) | - -NOTE 1: *Artifact Version* IE of *Model ID* IE is uniquely assigned by Near-RT RIC for newly trained AI/ML model - -NOTE 2: *Model URI* IE Shall be present if the *Trained Model Delivery Type* IE in the TRAINING JOB SETUP REQUEST message is set to "Model URI" - -NOTE 3: *Model File* IE Shall be present if the *Trained Model Delivery Type* IE in the TRAINING JOB SETUP REQUEST message is set to "Model File" - -### 9A.3.3.16 AI/ML Dataset - -This IE is used to contain the AI/ML data. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------|----------|-----------------------------------|-----------------------|-----------------------| -| Dataset | | 1 | | | -| > Single Data Unit | | 1..<
maxnoof
DataUnit
s> | | | -| >> CHOICE Data Unit | M | | | | - -| | | | | | -|-------------|---|--|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| >>> BOOLEAN | | | BOOLEAN | | -| >>> INTEGER | | | INTEGER | | -| >>> REAL | | | REAL | | -| >>> NULL | | | 9A.3.3.17 | | -| Shape | M | | STRING |

Describes the shape of a multi-dimensional data set.

The string shall be a sequence of integers separated by “,” where the n-th integer represents the length of the n-th dimension. E.g., a 2-dim dataset of 3 rows and 4 columns data units has the shape value “3,4”.

By default, the 1st dimension is used to separate different samples for an AI/ML model.

| - -| Range bound | Explanation | -|-------------------------|--------------------------------------------------------------------------------------------------| -| maxnoofDataUnits | Maximum number of data batches that can be carried in a Batched Data IE . Value is 65535. | - -### 9A.3.3.17 Null Value - -This IE indicates a null value. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|---------------------------------|-----------------------| -| Null Value | M | | ENUMERATED
(NULL_VALUE, ...) | | - -### 9A.3.3.18 Inference Job Description - -This IE identifies the inference job descriptions. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-----------------------------------------------------------------------------|----------|-------|------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| -| CHOICE Model Source | | | | | -| > MME | | | | | -| >> Model ID | M | | 9A.3.3.3 | Identifier of the AI/ML model to be inferred. Mandatory if Model Source is “MME” | -| > New Model | | | | | -| >> Model Related Information | | | 9A.3.3.2 | Related information of the AI/ML model. Mandatory if Model Source is “New Model” | -| >> Model URI | O | | 9A.3.3.9 | URI Location of the AI/ML model. (NOTE 1) | -| >> Model File | O | | 9A.3.3.7 | AI/ML Model File. (NOTE 1) | -| Result Delivery Method | M | | ENUMERATED
D (Response, Delivery, ...) | Indicates If the inference result is included in Inference Response or in a later Inference Result Delivery message. | -| Inference Output Delivery Type | M | | ENUMERATED
D (Output URI, Output Data, ...) | Indicates If the inference output is delivered through URI or as a dataset contained in the message. | -| Result Delivery Destination | C | | 10.1.9 | Indicates the destination address to send the Inference Result Delivery message. Shall be present if the Result Delivery Method IE is set to “Delivery”. | -| NOTE 1: Either Model URI IE or Model File IE shall be present | | | | | - -### 9A.3.3.19 Inference Job ID - -This IE identifies the inference job ID. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|-------|-----------------------|---------------------------------| -| Inference Job ID | M | | STRING | Identifier of the inference job | - -### 9A.3.3.20 Inference Job Status - -This IE contains the inference job Status. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|----------------------|----------|-------|-----------------------------------------------------|-----------------------| -| Inference Job Status | M | | ENUMERATED (Inferring, Suspended, Idle, Error, ...) | | - -### 9A.3.3.21 Inference Request Description - -This IE contains the inference request descriptions. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-------------------------------------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------| -| Inference Request Description | M | | - | | -| > Inference Dataset | O | | 9A.3.3.16 | The AI/ML model inference input data.
(NOTE) | -| > Inference Dataset URI | O | | 9A.3.3.9 | The URI points to the location where the Near-RT RIC platform can obtain the inference input data.
(NOTE) | -| NOTE: Either Dataset IE or Input URI IE Shall be present. | | | | | - -### 9A.3.3.22 Inference Result - -This IE contains the inference result. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|-------|------------------------------------|---------------------------------------------------------------------------------------------------------| -| Inference Result | M | | - | | -| > Result | M | | ENUMERATED (SUCCESS, FAILURE, ...) | If the inference is successful or not | -| > Inference Result Dataset | O | | 9A.3.3.16 | AI/ML Model output data.
(NOTE 1) | -| > Inference Result URI | O | | 9A.3.3.9 | URI Location of the AI/ML Model output data stored in the Near-RT RIC that can be accessed.
(NOTE 2) | -| NOTE 1: Inference Result Dataset IE Shall be present if the Inference Output Delivery Type IE in the INFERENCE JOB SETUP REQUEST message is set to "Output Data" | | | | | -| NOTE 2: Inference Result URI IE Shall be present if the Inference Output Delivery Type IE in the INFERENCE JOB SETUP REQUEST message is set to "Output URI" | | | | | - -### 9A.3.3.23 Data Pipelining Job Description - -This IE defines the data pipelining job descriptions. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-----------------------------|----------|-------|-----------------------|-----------------------| -| Data Processing Instruction | M | | 9A.3.3.28 | | - -| | | | | | -|--------------------------------------|---|--|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Result Delivery Method | M | | ENUMERATE D (Response, Delivery, ...) | Indicates If the data pipelining result is included in Data Pipelining Response or in a later Data Pipelining Result Delivery message. | -| Data Pipelining Output Delivery Type | M | | ENUMERATE D (Output URI, Output Data, ...) | Indicates If the data pipelining output is delivered through URI or as a Dataset in the message. | -| Result Delivery Destination | C | | 10.1.9 | Indicates the destination address to send the Data Pipelining Result Delivery message. Shall be present if the Result Delivery Method IE is set to "Delivery". | - -### 9A.3.3.24 Data Pipelining Job ID - -This IE identifies the data pipelining job ID. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------|----------|-------|-----------------------|---------------------------------------| -| Data Pipelining Job ID | M | | STRING | Identifier of the data pipelining job | - -### 9A.3.3.25 Data Pipelining Job Status - -This IE defines the data pipelining job Status. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|----------------------------|----------|-------|------------------------------------------------------|-----------------------| -| Data Pipelining Job Status | M | | ENUMERATED (Processing, Suspended, Idle, Error, ...) | | - -### 9A.3.3.26 Data Pipelining Request Description - -This IE defines the data pipelining request descriptions. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-----------------------------------------------------------------------------------------------------------|----------|-------|-----------------------|--------------------------------------------------------------------------------------------------------------------| -| Data Pipelining Request Description | M | | - | | -| > Data Pipelining Input Dataset | O | | 9A.3.3.16 | The data pipelining input data.
(NOTE) | -| > Data Pipelining Input URI | O | | 9A.3.3.9 | The URI points to the location where the Near-RT RIC platform can obtain the data pipelining input data.
(NOTE) | -| NOTE: Either Data Pipelining Input Dataset IE or Data Pipelining Input IE Shall be present. | | | | | - -### 9A.3.3.27 Data Pipelining Result - -This IE contains the data pipelining result. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|----------------------------------|----------|-------|-------------------------------------|----------------------------------------------| -| Data Pipelining Result | M | | - | | -| > Result | M | | ENUMERATE D (SUCCESS, FAILURE, ...) | If the data pipelining is successful or not | -| > Data Pipelining Output Dataset | O | | 9A.3.3.16 | The data pipelining output data.
(NOTE 1) | - -| | | | | | -|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|--|----------|------------------------------------------------------------------------------------------------------| -| > Data Pipelining Output URI | O | | 9A.3.3.9 | URI Location of the AI/ML Model output data stored in the Near-RT RIC that can be accessed. (NOTE 2) | -| NOTE 1: Data Pipelining Output Dataset IE Shall be present if the Data Pipelining Output Delivery Type IE in the DATA PIPELINING JOB SETUP REQUEST message is set to "Output Data" | | | | | -| NOTE 2: Data Pipelining Output URI IE Shall be present if the Data Pipelining Output Delivery Type IE in the DATA PIPELINING JOB SETUP REQUEST message is set to "Output URI" | | | | | - -### 9A.3.3.28 Data Processing Instruction - -This IE contains the data pipelining instruction. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-----------------------------------|----------|------------------------------|-----------------------|-----------------------| -| Instruction List | M | | | | -| > Instruction Item | | 1.. | | | -| >> CHOICE Instruction Type | | | | | -| >>> Handle Missing Value | | | 9A.3.3.29 | | -| >>> Normalize | | | 9A.3.3.32 | | - -| Range bound | Explanation | -|--------------------------------|----------------------------------------------------------------------------------------------| -| maxnoofInstructionItems | Maximum number of Instruction Items that can be carried in an Instruction List. Value is 64. | - -### 9A.3.3.29 Handle Missing Value - -This IE contains the information of handle missing value operation. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------------|----------|-------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| CHOICE Operation Type | | | | | -| > Drop | | | | Drop a sample in the AI/ML dataset. By default, the different samples are indexed by the different values in the 1 st coordinate axis, e.g., for a 2-dim dataset, different samples can be indexed by (1,:), (2,:), (3,:) and so on. | -| >> Drop Method | M | | ENUMERATED (Any, All, THRESH) | "Any": drop the sample if any value is missing in its checked data units.
"All": drop the sample only if all values are missing in its checked data units.
"THRESH": drop the sample if the number of missing values in its checked data units exceeds the threshold value in the Drop Thresh IE. | -| >> Drop Thresh | C | | INTEGER | The threshold value for the threshold-based drop method.
Shall be present if the Drop Method IE is set to "THRESH". | -| >> Data Subset To Check | O | | 9A.3.3.31 | Specifies a subset of data units to check for missing values.
The parameter values of this IE shall be empty. | - -### 9A.3.3.30 Position Index - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|----------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Position Index | M | | STRING |

The string shall consist of N elements separated by ",", where N is the dimension of the AI/ML dataset, and each element may be a positive integer or ":". A positive integer k for the n-th element means the k-th position in the n-th dimension, and ":" means "any" position in that dimension.

E.g., a Position Index "2,:" refers to all the data units on the 2nd row of a 2-dim AI/ML dataset; another Position Index ":,:" refers to all the data units in that dataset.

| - -| Range bound | Explanation | -|-----------------------|-------------------------------------------------------------------------------------| -| maxnoofIndexes | Maximum number of index values that can be carried in a Index List. Value is 65536. | - -### 9A.3.3.31 Parameter Dictionary - -This IE defines the Parameter Dictionary structure. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------------------|----------|-----------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Parameter Dictionary | | | | | -| > Parameter Dictionary Item | | 1.. | | | -| >> Position Index | M | | 9A.3.3.30 | Used to select a subset of data units in an AI/ML dataset based on their position in the dataset. | -| >> Real Parameter Values | 0..1 | | |

The real-value parameter values used to process the data unit(s) referenced by the Position Inde9A.

The meaning of each parameter is specific to the data processing operation, and given in the respective clauses.

| -| >>> Real Parameter 1 | O | | REAL | The first real-value parameter. | -| >>> Real Parameter 2 | O | | REAL | The second real-value parameter. | -| >> Integer Parameter Values | 0..1 | | | The integer-value parameter values used to process the data unit(s) referenced by the Position Inde9A. | -| >>> Integer Parameter 1 | O | | REAL | The first integer-value parameter. | - -| Range bound | Explanation | -|-------------------------------|-------------------------------------------------------------------------------------------| -| maxnoofDictionaryItems | Maximum number of Dictionary Items that can be carried in a Dictionary. Value is 1048576. | - -### 9A.3.3.32 Normalize - -This IE contains the information of normalize operation. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------------|----------|-------|-----------------------|-----------------------| -| CHOICE Operation Type | | | | | - -| | | | | | -|------------------|---|--|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| > Clip | | | | This operation is to clip the values to a given range. | -| Clip Parameters | M | | 9A.3.3.31 |

Specifies subset(s) or all of the data units to perform clip operation, and the associated upper/lower bound.

The upper bound is given by Real Parameter 1, and the lower bound is given by Real Parameter 2 of this IE.

The data unit to be processed will be replaced by the upper bound, if the data unit's value is greater than that upper bound. The data unit to be processed will be replaced by the lower bound, if the data unit's value is less than that lower bound.

| - -## 9A.3.4 Message and Information Element Abstract Syntax - -### 9A.3.4.1 Solution 1: gRPC with Protocol Buffers - -#### 9A.3.4.1.1 Usage of gRPC with Protocol Buffers - -This solution uses Protocol Buffers as message encoding, and also as the Interface Definition Language (IDL) for gRPC [5]. - -Table 9A.3.4.1.1-1 lists the mapping of AI/ML APIs and corresponding gRPC services. - -**Table 9A.3.4.1.1-1: Mapping of AI/ML APIs and gRPC services** - -| API Name | gRPC service(s) | -|----------------------------------------|-------------------------------------------------------------| -| AIML_Data_Pipelining_API | AIML_DATA_PIPELINING_API, AIML_DATA_PIPELINING_API_Callback | -| AIML_Inference_API | AIML_Inference_API, AIML_Inference_API_Callback | -| AIML_Training_API | AIML_Training_API, AIML_Training_API_Callback | -| AIML_Model_Management_And_Exposure_API | AIML_Model_Management_And_Exposure_API | - -A procedure of an AI/ML API is mapped to a *gRPC method*. - -Table 9A.3.4.1.1-2 lists the AI/ML APIs abstract syntax included in this document. - -**Table 9A.3.4.1.1-2: List of AI/ML APIs abstract syntax** - -| API Name / Contents | Clause | Version | File Name | -|---------------------------------------------|--------------|---------|-------------------------------------------------------------| -| AIML_Data_Pipelining_API | 9A.3.4.1.2.1 | 1.0.0 | aiml_data_pipelining_api_grpc_ver_1_0_0.proto | -| AIML_Inference_API | 9A.3.4.1.2.2 | 1.0.0 | aiml_inference_api_grpc_ver_1_0_0.proto | -| AIML_Training_API | 9A.3.4.1.2.3 | 1.0.0 | aiml_training_api_grpc_ver_1_0_0.proto | -| AIML_Model_Management_And_Exposure_API | 9A.3.4.1.2.4 | 1.0.0 | aiml_model_management_and_exposure_api_grpc_ver_1_0_0.proto | -| AI/ML API common information elements | 9A.3.4.1.3 | 1.0.0 | aiml_apis_common_ies_ver_1_0_0.proto | -| Near-RT RIC API common information elements | 10.2.1 | 3.0.0 | near_rt_ric_apis_common_ies_ver_3_0_0.proto | - -#### 9A.3.4.1.2 API Definitions - -##### 9A.3.4.1.2.1 AIML\_Data\_Pipelining\_API - -``` -syntax = "proto3"; - -package ricapi.aiml_data_pipelining_api_grpc.v1; -``` - -``` -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; -import "aiml_apis_common_ies_ver_1_0_0.proto"; - -// gRPC service and rpc definition -service AIML_Data_Pipelining_API { - rpc DataPipeliningJobSetupProc(DataPipeliningJobSetupInitMsg) returns (DataPipeliningJobSetupOutMsg) {} - rpc DataPipeliningJobUpdateProc(DataPipeliningJobUpdateInitMsg) returns (DataPipeliningJobUpdateOutMsg) {} - rpc DataPipeliningJobDeleteProc(DataPipeliningJobDeleteInitMsg) returns (DataPipeliningJobDeleteOutMsg) {} - rpc DataPipeliningJobQueryProc(DataPipeliningJobQueryInitMsg) returns (DataPipeliningJobQueryOutMsg) {} - rpc DataPipeliningRequestProc(DataPipeliningRequestInitMsg) returns (DataPipeliningRequestOutMsg) {} -} - -message DataPipeliningJobSetupInitMsg { - optional DataPipeliningJobSetupRequest data_pipelining_job_setup_request = 1; -} - -message DataPipeliningJobSetupOutMsg { - oneof type of message { - DataPipeliningJobSetupResponse data_pipelining_job_setup_response = 1; - DataPipeliningJobSetupFailure data_pipelining_job_setup_failure = 2; - } -} - -message DataPipeliningJobUpdateInitMsg { - optional DataPipeliningJobUpdateRequest data_pipelining_job_update_request = 1; -} - -message DataPipeliningJobUpdateOutMsg { - oneof type of message { - DataPipeliningJobUpdateResponse data_pipelining_job_update_response = 1; - DataPipeliningJobUpdateFailure data_pipelining_job_update_failure = 2; - } -} - -message DataPipeliningJobDeleteInitMsg { - optional DataPipeliningJobDeleteRequest data_pipelining_job_delete_request = 1; -} - -message DataPipeliningJobDeleteOutMsg { - oneof type_of_message { - DataPipeliningJobDeleteResponse data_pipelining_job_delete_response = 1; - DataPipeliningJobDeleteFailure data_pipelining_job_delete_failure = 2; - } -} - -message DataPipeliningJobQueryInitMsg { - optional DataPipeliningJobQueryRequest data_pipelining_job_query_request = 1; -} - -message DataPipeliningJobQueryOutMsg { - oneof type of message { - DataPipeliningJobQueryResponse data_pipelining_job_query_response = 1; - DataPipeliningJobQueryFailure data_pipelining_job_query_failure = 2; - } -} - -message DataPipeliningRequestInitMsg { - optional DataPipeliningRequest data_pipelining_request = 1; -} - -message DataPipeliningRequestOutMsg { - oneof type of message { - DataPipeliningResponse data_pipelining_response = 1; - DataPipeliningFailure data_pipelining_failure = 2; - } -} - -service AIML_Data_Pipelining_API_Callback { - rpc DataPipeliningResultDeliveryProc(DataPipeliningResultDeliveryInitMsg) returns (DataPipeliningResultDeliveryOutMsg) {} -} -``` - -``` - -message DataPipeliningResultDeliveryInitMsg { - optional DataPipeliningResultDelivery data_pipelining_result_delivery = 1; -} - -message DataPipeliningResultDeliveryOutMsg { -} - -// ----- messages of AIML_Pipelining_API ----- -// ----- messages of Data Pipelining Job Setup procedure ----- -message DataPipeliningJobSetupRequest { - optional ricapi.near_rt_ric.apis.common.ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml.apis.common.ies.v1.DataPipeliningJobDescription data_pipelining_job_description = -2; -} - -message DataPipeliningJobSetupResponse { - optional ricapi.near_rt_ric.apis.common.ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml.apis.common.ies.v1.DataPipeliningJobId data_pipelining_job_id = 2; -} - -message DataPipeliningJobSetupFailure { - optional ricapi.near_rt_ric.apis.common.ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml.apis.common.ies.v1.Cause cause = 2; -} - -// ----- messages of Data Pipelining Job Update procedure ----- -message DataPipeliningJobUpdateRequest { - optional ricapi.near_rt_ric.apis.common.ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml.apis.common.ies.v1.DataPipeliningJobId data_pipelining_job_id = 2; - optional ricapi.aiml.apis.common.ies.v1.DataPipeliningJobDescription data_pipelining_job_description = -3; -} - -message DataPipeliningJobUpdateResponse { - optional ricapi.near_rt_ric.apis.common.ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml.apis.common.ies.v1.DataPipeliningJobId data_pipelining_job_id = 2; -} - -message DataPipeliningJobUpdateFailure { - optional ricapi.near_rt_ric.apis.common.ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml.apis.common.ies.v1.DataPipeliningJobId data_pipelining_job_id = 2; - optional ricapi.aiml.apis.common.ies.v1.Cause cause = 3; -} - -// ----- messages of Data Pipelining Job Delete procedure ----- -message DataPipeliningJobDeleteRequest { - optional ricapi.near_rt_ric.apis.common.ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml.apis.common.ies.v1.DataPipeliningJobId data_pipelining_job_id = 2; -} - -message DataPipeliningJobDeleteResponse { - optional ricapi.near_rt_ric.apis.common.ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml.apis.common.ies.v1.DataPipeliningJobId data_pipelining_job_id = 2; -} - -message DataPipeliningJobDeleteFailure { - optional ricapi.near_rt_ric.apis.common.ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml.apis.common.ies.v1.DataPipeliningJobId data_pipelining_job_id = 2; - optional ricapi.aiml.apis.common.ies.v1.Cause cause = 3; -} - -// ----- messages of Data Pipelining Job Query procedure ----- -message DataPipeliningJobQueryRequest { - optional ricapi.near_rt_ric.apis.common.ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml.apis.common.ies.v1.DataPipeliningJobId data_pipelining_job_id = 2; -} - -message DataPipeliningJobQueryResponse { - optional ricapi.near_rt_ric.apis.common.ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml.apis.common.ies.v1.DataPipeliningJobId data_pipelining_job_id = 2; - optional ricapi.aiml.apis.common.ies.v1.DataPipeliningJobStatus data_pipelining_job_status = 3; -} - -message DataPipeliningJobQueryFailure { - optional ricapi.near_rt_ric.apis.common.ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml.apis.common.ies.v1.DataPipeliningJobId data_pipelining_job_id = 2; -} - -``` - -``` - - optional ricapi.aiml_apis_common_ies.v1.Cause cause = 3; -} - -// ----- messages of Data Pipelining Request procedure ----- -message DataPipeliningRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.DataPipeliningJobId data_pipelining_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.DataPipeliningRequestDescription - data_pipelining_request_description = 3; -} - -message DataPipeliningResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.DataPipeliningJobId data_pipelining_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.DataPipeliningResult data_pipelining_result = 3; -} - -message DataPipeliningFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.DataPipeliningJobId data_pipelining_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.Cause cause = 3; -} - -// ----- messages of Data Pipelining Result Delivery procedure ----- -message DataPipeliningResultDelivery { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.DataPipeliningJobId data_pipelining_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.DataPipeliningResult data_pipelining_result = 3; -} - -``` - -#### 9A.3.4.1.2.2 AIML\_Inference\_API - -``` - -syntax = "proto3"; - -package ricapi.aiml_inference_api_grpc.v1; - -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; -import "aiml_apis_common_ies_ver_1_0_0.proto"; - -// gRPC service and rpc definition -service AIML_Inference_API { - rpc InferenceJobSetupProc(InferenceJobSetupInitMsg) returns (InferenceJobSetupOutMsg) {}; - rpc InferenceJobUpdateProc(InferenceJobUpdateInitMsg) returns (InferenceJobUpdateOutMsg) {}; - rpc InferenceJobDeleteProc(InferenceJobDeleteInitMsg) returns (InferenceJobDeleteOutMsg) {}; - rpc InferenceJobQueryProc(InferenceJobQueryInitMsg) returns (InferenceJobQueryOutMsg) {}; - rpc InferenceRequestProc(InferenceRequestInitMsg) returns (InferenceRequestOutMsg) {}; -} - -message InferenceJobSetupInitMsg { - optional InferenceJobSetupRequest inference_job_setup_request = 1; -} - -message InferenceJobSetupOutMsg { - oneof type_of_message { - InferenceJobSetupResponse inference_job_setup_response = 1; - InferenceJobSetupFailure inference_job_setup_failure = 2; - } -} - -message InferenceJobUpdateInitMsg { - optional InferenceJobUpdateRequest inference_job_update_request = 1; -} - -message InferenceJobUpdateOutMsg { - oneof type_of_message { - InferenceJobUpdateResponse inference_job_update_response = 1; - InferenceJobUpdateFailure inference_job_update_failure = 2; - } -} - -message InferenceJobDeleteInitMsg { - -``` - -``` - - optional InferenceJobDeleteRequest inference_job_delete_request = 1; - } - - message InferenceJobDeleteOutMsg { - oneof type_of_message { - InferenceJobDeleteResponse inference_job_delete_response = 1; - InferenceJobDeleteFailure inference_job_delete_failure = 2; - } - } - - message InferenceJobQueryInitMsg { - optional InferenceJobQueryRequest inference_job_query_request = 1; - } - - message InferenceJobQueryOutMsg { - oneof type_of_message { - InferenceJobQueryResponse inference_job_query_response = 1; - InferenceJobQueryFailure inference_job_query_failure = 2; - } - } - - message InferenceRequestInitMsg { - optional InferenceRequest inference_request = 1; - } - - message InferenceRequestOutMsg { - oneof type_of_message { - InferenceResponse inference_response = 1; - InferenceFailure inference_failure = 2; - } - } - - service AIML_Inference_API_Callback { - rpc InferenceResultDeliveryProc(InferenceResultDeliveryInitMsg) returns - (InferenceResultDeliveryOutMsg) {}; - } - - message InferenceResultDeliveryInitMsg { - optional InferenceResultDelivery inference_result_delivery = 1; - } - - message InferenceResultDeliveryOutMsg { - } - - // ----- messages of AIML_Inference_API ----- - // ----- messages of Inference Job Setup procedure ----- - message InferenceJobSetupRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobDescription inference_job_description = 2; - } - - message InferenceJobSetupResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobId inference_job_id = 2; - } - - message InferenceJobSetupFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.Cause cause = 2; - } - - // ----- messages of Inference Job Update procedure ----- - message InferenceJobUpdateRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobId inference_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobDescription inference_job_description = 3; - } - - message InferenceJobUpdateResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobId inference_job_id = 2; - } - -``` - -``` -message InferenceJobUpdateFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobId inference_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.Cause cause = 3; -} - -// ----- messages of Inference Job Delete procedure ----- -message InferenceJobDeleteRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobId inference_job_id = 2; -} - -message InferenceJobDeleteResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobId inference_job_id = 2; -} - -message InferenceJobDeleteFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobId inference_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.Cause cause = 3; -} - -// ----- messages of Inference Job Query procedure ----- -message InferenceJobQueryRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobId inference_job_id = 2; -} - -message InferenceJobQueryResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobId inference_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobStatus inference_job_status = 3; -} - -message InferenceJobQueryFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobId inference_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.Cause cause = 3; -} - -// ----- messages of Inference Request procedure ----- -message InferenceRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobId inference_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.InferenceRequestDescription inference_request_description = -3; -} - -message InferenceResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobId inference_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.InferenceResult inference_result = 3; -} - -message InferenceFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobId inference_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.Cause cause = 3; -} - -// ----- messages of Inference Result Delivery procedure ----- -message InferenceResultDelivery { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.InferenceJobId inference_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.InferenceResult inference_result = 3; -} -``` - -## 9A.3.4.1.2.3 - -## AIML\_Training\_API - -``` - -syntax = "proto3"; - -package ricapi.aiml_training_api_grpc.v1; - -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; -import "aiml_apis_common_ies_ver_1_0_0.proto"; - -// gRPC service and rpc definition -service AIML_Training_API { - rpc TrainingJobSetupProc(TrainingJobSetupInitMsg) returns (TrainingJobSetupOutMsg) {}; - rpc TrainingJobDeleteProc(TrainingJobDeleteInitMsg) returns (TrainingJobDeleteOutMsg) {}; - rpc TrainingJobQueryProc(TrainingJobQueryInitMsg) returns (TrainingJobQueryOutMsg) {}; - rpc TrainingRequestProc(TrainingRequestInitMsg) returns (TrainingRequestOutMsg) {}; -} - -message TrainingJobSetupInitMsg { - optional TrainingJobSetupRequest training_job_setup_request = 1; -} - -message TrainingJobSetupOutMsg { - oneof type_of_message { - TrainingJobSetupResponse training_job_setup_response = 1; - TrainingJobSetupFailure training_job_setup_failure = 2; - } -} - -message TrainingJobDeleteInitMsg { - optional TrainingJobDeleteRequest training_job_delete_request = 1; -} - -message TrainingJobDeleteOutMsg { - oneof type_of_message { - TrainingJobDeleteResponse training_job_delete_response = 1; - TrainingJobDeleteFailure training_job_delete_failure = 2; - } -} - -message TrainingJobQueryInitMsg { - optional TrainingJobQueryRequest training_job_query_request = 1; -} - -message TrainingJobQueryOutMsg { - oneof type_of_message { - TrainingJobQueryResponse training_job_query_response = 1; - TrainingJobQueryFailure training_job_query_failure = 2; - } -} - -message TrainingRequestInitMsg { - optional TrainingRequest training_request = 1; -} - -message TrainingRequestOutMsg { - oneof type_of_message { - TrainingResponse training_response = 1; - TrainingFailure training_failure = 2; - } -} - -service AIML_Training_API_Callback { - rpc TrainingResultDeliveryProc(TrainingResultDeliveryInitMsg) returns (TrainingResultDeliveryOutMsg) -{}; -} - -message TrainingResultDeliveryInitMsg { - optional TrainingResultDelivery training_result_delivery = 1; -} - -message TrainingResultDeliveryOutMsg { - -``` - -``` - -} - -// ----- messages of AIML_Training_API ----- -// ----- messages of Training Job Setup procedure ----- -message TrainingJobSetupRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.TrainingJobDescription training_job_description = 2; -} - -message TrainingJobSetupResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.TrainingJobId training_job_id = 2; -} - -message TrainingJobSetupFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.Cause cause = 2; -} - -// ----- messages of Training Job Delete procedure ----- -message TrainingJobDeleteRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.TrainingJobId training_job_id = 2; -} - -message TrainingJobDeleteResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.TrainingJobId training_job_id = 2; -} - -message TrainingJobDeleteFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.TrainingJobId training_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.Cause cause = 3; -} - -// ----- messages of Training Job Query procedure ----- -message TrainingJobQueryRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.TrainingJobId training_job_id = 2; -} - -message TrainingJobQueryResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.TrainingJobStatus training_job_status = 2; -} - -message TrainingJobQueryFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.TrainingJobId training_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.Cause cause = 3; -} - -// ----- messages of Training Request procedure ----- -message TrainingRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.TrainingJobId training_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.TrainingRequestDescription training_request_description = 3; -} - -message TrainingResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.TrainingJobId training_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.TrainingResult training_result = 3; -} - -message TrainingFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.TrainingJobId training_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.Cause cause = 3; -} - -// ----- messages of Training Result Delivery procedure ----- - -``` - -``` - -message TrainingResultDelivery { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.TrainingJobId training_job_id = 2; - optional ricapi.aiml_apis_common_ies.v1.TrainingResult training_result = 3; -} - -``` - -#### 9A.3.4.1.2.4 AIML\_Model\_Management\_And\_Exposure\_API - -``` - -syntax = "proto3"; - -package ricapi.aiml_model_management_and_exposure_api_grpc.v1; - -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; -import "aiml_apis_common_ies_ver_1_0_0.proto"; - -// gRPC service and rpc definition -service AIML_Model_Management_And_Exposure_API { - rpc ModelStoreProc(ModelStoreInitMsg) returns (ModelStoreOutMsg) {}; - rpc StoredModelQueryProc(StoredModelQueryInitMsg) returns (StoredModelQueryOutMsg) {}; - rpc ModelRetrieveProc(ModelRetrieveInitMsg) returns (ModelRetrieveOutMsg) {}; - rpc ModelDeleteProc(ModelDeleteInitMsg) returns (ModelDeleteOutMsg) {}; -} - -message ModelStoreInitMsg { - optional ModelStoreRequest model_store_request = 1; -} - -message ModelStoreOutMsg { - oneof type_of_message { - ModelStoreResponse model_store_response = 1; - ModelStoreFailure model_store_failure = 2; - } -} - -message StoredModelQueryInitMsg { - optional StoredModelQueryRequest stored_model_query_request = 1; -} - -message StoredModelQueryOutMsg { - oneof type_of_message { - StoredModelQueryResponse stored_model_query_response = 1; - StoredModelQueryFailure stored_model_query_failure = 2; - } -} - -message ModelRetrieveInitMsg { - optional ModelRetrieveRequest model_retrieve_request = 1; -} - -message ModelRetrieveOutMsg { - oneof type_of_message { - ModelRetrieveResponse model_retrieve_response = 1; - ModelRetrieveFailure model_retrieve_failure = 2; - } -} - -message ModelDeleteInitMsg { - optional ModelDeleteRequest model_delete_request = 1; -} - -message ModelDeleteOutMsg { - oneof type_of_message { - ModelDeleteResponse model_delete_response = 1; - ModelDeleteFailure model_delete_failure = 2; - } -} - -// ----- messages of AIML_Model_Management_And_Exposure_API ----- -// ----- messages of Model Store procedure ----- -message ModelStoreRequest { - -``` - -``` - -optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; -optional ricapi.aiml_apis_common_ies.v1.ModelRelatedInformation model_related_information = 2; -optional ricapi.aiml_apis_common_ies.v1.ModelFile model_file = 3; -optional ricapi.aiml_apis_common_ies.v1.Uri model_location = 4; -} - -message ModelStoreResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.ModelId model_id = 2; -} - -message ModelStoreFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.Cause cause = 2; -} - -// ----- messages of Stored Model Query procedure ----- -message StoredModelQueryRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - repeated Model_Id_Filter_Item model_id_filter_list = 2; - - message Model_Id_Filter_Item { - optional ricapi.aiml_apis_common_ies.v1.Model_Id_Filter model_id_filter = 1; - } -} - -message StoredModelQueryResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - repeated ModelRelatedInformationItem model_related_information_list = 2; - - message ModelRelatedInformationItem { - optional ricapi.aiml_apis_common_ies.v1.ModelRelatedInformation model_related_information = 1; - } -} - -message StoredModelQueryFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.Cause cause = 2; -} - -// ----- messages of Model Retrieve procedure ----- -message ModelRetrieveRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.ModelId model_id = 2; -} - -message ModelRetrieveResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.ModelId model_id = 2; - optional ricapi.aiml_apis_common_ies.v1.Uri model_uri = 3; - optional ricapi.aiml_apis_common_ies.v1.ModelFile model_file = 4; -} - -message ModelRetrieveFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.ModelId model_id = 2; - optional ricapi.aiml_apis_common_ies.v1.Cause cause = 3; -} - -// ----- messages of Model Delete procedure ----- -message ModelDeleteRequest { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - repeated ModelIdItem model_id_list = 2; - - message ModelIdItem { - optional ricapi.aiml_apis_common_ies.v1.ModelId model_id = 1; - } -} - -message ModelDeleteResponse { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - repeated ModelIdItem model_id_deleted_list = 2; - repeated ModelIdItem model_id_not_deleted_list = 3; -} - -``` - -``` - -message ModelIDItem { - optional ricapi.aiml_apis_common_ies.v1.ModelId model_id = 1; -} - -message ModelDeleteFailure { - optional ricapi.near_rt_ric_apis_common_ies.v3.ProcedureTransactionId procedure_transaction_id = 1; - optional ricapi.aiml_apis_common_ies.v1.Cause cause = 2; -} - -``` - -### 9A.3.4.1.3 Information Element Definitions - -``` - -syntax = "proto3"; - -package ricapi.aiml_apis_common_ies.v1; - -import "near_rt_ric_apis_common_ies_ver_3_0_0.proto"; - -// ----- Information Elements ----- -// -----A----- -message AiMLDataset { - repeated SingleDataUnit dataset = 1; - optional string shape = 2; - - message SingleDataUnit { - oneof data_unit { - bool bool_value = 1; - int32 int value = 2; - float real value = 3; - NullValue null value = 4; - } - } -} - -message ArtifactVersion { - optional string value = 1; -} - -// -----C----- -enum Cause { - UNSPECIFIED = 0; - SYSTEM_BUSY = 1; - STORAGE_REACHED_CAPACITY = 2; - DATASET_PROBLEM = 3; - INVALID_REQUEST = 4; - MODEL_ACCESS_DENIED = 5; - INVALID_MODEL_ID = 6; -} - -// -----D----- -message DataPipeliningJobDescription { - optional DataProcessingInstruction data_processing_instruction = 1; - optional ResultDeliveryMethod result_delivery_method = 2; - optional DataPipeliningOutputDeliveryType data_pipelining_output_delivery_type = 3; - optional ricapi.near_rt_ric_apis_common_ies.v3.EndpointInformation result_delivery_destination = 4; - - enum ResultDeliveryMethod { - DELIVERY_METHOD_RESPONSE = 0; - DELIVERY_METHOD_DELIVERY = 1; - } - - enum DataPipeliningOutputDeliveryType { - DELIVERY_TYPE_OUTPUT_URI = 0; - DELIVERY_TYPE_OUTPUT_DATA = 1; - } -} - -message DataPipeliningJobId { - optional string value = 1; -} - -enum DataPipeliningJobStatus { - -``` - -``` - - UNSPECIFIED_DATA_PIPELINING_STATUS = 0; - DATA_PIPELINING_PROCESSING = 1; - DATA_PIPELINING_SUSPENDED = 2; - DATA_PIPELINING_IDLE = 3; - DATA_PIPELINING_ERROR = 4; -} - -message DataPipeliningRequestDescription { - optional AiMlDataset data_pipelining_input_dataset = 1; - optional Uri data_pipelining_input_uri = 2; -} - -message DataPipeliningResult { - optional Result result = 1; - optional AiMlDataset data_pipelining_output_dataset = 2; - optional Uri data_pipelining_output_uri = 3; - - enum Result { - SUCCESS = 0; - FAILURE = 1; - } -} - -message DataProcessingInstruction { - repeated InstructionItem instruction_list = 1; - - message InstructionItem { - oneof instruction_type { - HandleMissingValue handle_missing_value = 1; - Normalize normalize = 2; - } - } -} - -// -----H----- -message HandleMissingValue { - oneof operation_type { - Drop drop = 1; - } - - message Drop { - optional DropMethod drop_method = 1; - optional uint32 drop_thresh = 2; - optional ParameterDictionary data_subset_to_check = 3; - - enum DropMethod { - ANY = 0; - ALL = 1; - THRESH = 2; - } - } -} - -// -----I----- -message InferenceJobDescription { - oneof model_source { - MME mme = 1; - NewModel new_model = 2; - } - optional ResultDeliveryMethod result_delivery_method = 3; - optional InferenceOutputDeliveryType inference_output_delivery_type = 4; - optional ricapi.near_rt_ric_apis_common_ies.v3.EndpointInformation result_delivery_destination = 5; - - message MME { - optional ModelId model_id = 1; - } - - message NewModel { - optional ModelRelatedInformation model_related_information = 1; - optional Uri model_uri = 2; - optional ModelFile model_file = 3; - } - - enum ResultDeliveryMethod { - DELIVERY_METHOD_RESPONSE = 0; - DELIVERY_METHOD_DELIVERY = 1; - } -} - -``` - -``` - - } - - enum InferenceOutputDeliveryType { - DELIVERY_TYPE_OUTPUT_URI = 0; - DELIVERY_TYPE_OUTPUT_DATA = 1; - } -} - -message InferenceJobId { - optional string value = 1; -} - -enum InferenceJobStatus { - UNSPECIFIED_INFERENCE_STATUS = 0; - INFERRING = 1; - INFERENCE_SUSPENDED = 2; - INFERENCE_IDLE = 3; - INFERENCE_ERROR = 4; -} - -message InferenceRequestDescription { - optional AiMlDataset inference_dataset = 1; - optional Uri inference_dataset_uri = 2; -} - -message InferenceResult { - optional Result result = 1; - optional AiMlDataset inference_result_dataset = 2; - optional Uri inference_result_uri = 3; - - enum Result { - SUCCESS = 0; - FAILURE = 1; - } -} - -// -----M----- -message ModelFile { - optional string file_format = 1; - optional bytes file_data = 2; -} - -message ModelId { - optional ModelName model_name = 1; - optional ModelVersion model_version = 2; - optional ArtifactVersion artifact_version = 3; -} - -message Model_Id_Filter { - optional ModelName model_name = 1; - optional ModelVersion model_version = 2; - optional ArtifactVersion artifact_version = 3; -} - -message ModelName { - optional string value = 1; -} - -message ModelRelatedInformation { - optional ModelId model_id = 1; - optional string description = 2; - optional ModelInformation model_information = 3; - - message ModelInformation { - optional Metadata metadata = 1; - repeated InputDataTypeItem input_data_type_list = 2; - optional string input_data_shape = 3; - repeated OutputDataTypeItem output_data_type_list = 4; - optional string output_data_shape = 5; - repeated TargetEnvironmentItem target_environment_list = 6; - - message Metadata { - optional string author = 1; - optional string owner = 2; - } - - message InputDataTypeItem { - -``` - -``` - - optional string input_data_type_id = 1; - } - - message OutputDataTypeItem { - optional string output_data_type_id = 1; - } - - message TargetEnvironmentItem { - optional string platform_name = 1; - optional string environment_type = 2; - optional Uri dependency list = 3; - } -} - -message ModelVersion { - optional string value = 1; -} - -// -----N----- -message Normalize { - oneof operation_type { - Clip clip = 1; - } - - message Clip { - optional ParameterDictionary clip parameters = 1; - } -} - -enum NullValue { - NULL_VALUE = 0; -} - -// -----P----- -message ParameterDictionary { - repeated ParameterDictionaryItem parameter_dictionary = 1; - - message ParameterDictionaryItem { - optional PositionIndex position index = 1; - optional RealParameterValues real_parameter_values = 2; - optional IntegerParameterValues integer_parameter_values = 3; - - message RealParameterValues { - optional float real_parameter_1 = 1; - optional float real_parameter_2 = 2; - } - - message IntegerParameterValues { - optional int32 integer_parameter_1 = 1; - } - } -} - -message PositionIndex { - optional string position index = 1; -} - -// -----T----- -message TrainingJobDescription { - oneof model_source { - MME mme = 1; - NewModel new_model = 2; - } - - optional ResultDeliveryMethod result_delivery_method = 3; - optional TrainedModelDeliveryType trained_model_delivery_type = 4; - optional ricapi.near rt ric apis common ies.v3.EndpointInformation result_delivery_destination = 5; - - message MME { - optional ModelId model_id = 1; - } - - message NewModel { - optional ModelRelatedInformation model_related_information = 1; - optional Uri model_uri = 2; - optional ModelFile model_file = 3; - } -} - -``` - -``` - - } - - enum ResultDeliveryMethod { - RESULT_DELIVERY_METHOD_RESPONSE = 0; - RESULT_DELIVERY_METHOD_DELIVERY = 1; - } - - enum TrainedModelDeliveryType { - TRAINED_MODEL_DELIVERY_TYPE_MODEL_URI = 0; - TRAINED_MODEL_DELIVERY_TYPE_MODEL_FILE = 1; - } -} - -message TrainingJobId { - optional string value = 1; -} - -enum TrainingJobStatus { - UNSPECIFIED_TRAINING_STATUS = 0; - TRAINING = 1; - VALIDATING = 2; - TRAINING_SUSPENDED = 3; - TRAINING_FINISHED = 4; - TRAINING_ERROR = 5; -} - -message TrainingRequestDescription { - optional TrainingJobId training_job_id = 1; - optional AiMlDataset training_dataset = 2; - optional AiMlDataset validation_dataset = 3; - optional Uri training_dataset_uri = 4; - optional Uri validation_dataset_uri = 5; -} - -message TrainingResult { - optional Result result = 1; - optional ModelId model_id = 2; - optional Uri model_uri = 3; - optional ModelFile model_file = 4; - - enum Result { - SUCCESS = 0; - FAILURE = 1; - } -} - -// -----U----- -message Uri { - optional string value = 1; -} - -``` - -## 9A.3.5 Message Transfer Syntax - -### 9A.3.5.1 Solution 1: gRPC with Protocol Buffers - -The message transfer syntax for Solution 1 is serialized Protocol Buffers [4]. - -## 10 Common definitions across APIs - -### 10.1 Information element definitions - -#### 10.1.1 PTI - -The Procedure Transaction Identity (PTI) IE allows identifying a procedure among all ongoing parallel procedures of the same type initiated by the same RICAPI peer. The PTI value is assigned to the initiating message by the procedure initiator, and - -subsequent messages shall include the same PTI value as in the initiating message, if any. PTI is released when the procedure is completed. - -| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | -|---------------|----------|-------|---------------------------------|-----------------------| -| PTI | M | | INTEGER (0..2 32 -1) | | - -### 10.1.2 xApp ID - -The xApp ID IE uniquely identifies an xApp. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|-----------------------------------------------------------------------------------------------------------| -| xApp ID | M | | STRING | The format of the xApp ID shall be a Universally Unique Identifier (UUID) version 4, as described in [9]. | - -### 10.1.3 API Name - -The API Name IE indicates the Name of each Near-RT RIC API. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| -| API Name | M | | ENUMERATED
(E2_Subscription_API,
E2_Indication_API,
E2_Control_API,
E2_Guidance_API, A1_Policy_API,
A1_EI_API, SDL_Information_API,
Xapp_Data_Sharing_API, ...) | Contains the Near-RT RIC API name. | - -The table 10.1.3-1 lists the API Names. - -**Table 10.1.3-1: List of API Names** - -| API Category | API Name | -|-----------------|----------------------------------------------------------------------------| -| E2 related APIs | E2_Subscription_API, E2_Indication_API, E2_Control_API,
E2_Guidance_API | -| A1 related APIs | A1_Policy_API, A1_EI_API | -| SDL APIs | SDL_Information_API, Xapp_Data_Sharing_API | - -### 10.1.4 API Version - -The API Version IE indicates the Version of each Near-RT RIC API. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|---------------------------------------| -| API Version | M | | STRING | Contains the Near-RT RIC API Version. | - -### 10.1.5 A1 Policy Type ID - -The A1 Policy Type ID IE identifies the type of one A1 policy. - -| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | -|-------------------|----------|-------|-----------------------|-----------------------------------| -| A1 Policy Type ID | M | | STRING | Applicable values defined in [7]. | - -## 10.1.6 Global E2 Node ID - -Defined in 9.2.6 of [3]. - -## 10.1.7 RAN Function ID - -Defined in 9.2.8 of [3]. - -## 10.1.8 Void - -## 10.1.9 Endpoint Information - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------------------------------------|----------|-------|-----------------------|-----------------------| -| Domain Name | O | | STRING | (NOTE) | -| IPv4 Address | O | | STRING | (NOTE) | -| IPv6 Address | O | | STRING | (NOTE) | -| Port | O | | INTEGER | | -| NOTE: At least one of these IEs shall be present. | | | | | - -# 10.2 Information element abstract syntax - -## 10.2.1 Abstract syntax in Protocol Buffers - -Table 10.2.1-1 lists the common IEs abstract syntax included in this document. - -**Table 10.2.1-1: List of common IEs abstract syntax** - -| API Name / Contents | Clause | Version | File Name | -|---------------------------------------------------|--------|---------|---------------------------------------------| -| Near-RT RIC API
common information
elements | 10.2.1 | 3.0.0 | near_rt_ric_apis_common_ies_ver_3_0_0.proto | - -``` - -syntax = "proto3"; - -package ricapi.near_rt_ric_apis_common_ies.v3; - -// Information elements used across different API categories - -// ----- Information Elements ----- -// -----A----- -// From A1TD Clause 5.2 -message A1PolicyTypeId { - optional string value = 1; -} - -enum ApiName { - APINAME_E2_SUBSCRIPTION_API = 0; - APINAME_E2_INDICATION_API = 1; - APINAME_E2_CONTROL_API = 2; - APINAME_E2_GUIDANCE_API = 3; - APINAME_A1_POLICY_API = 4; - APINAME_A1_EI_API = 5; - APINAME_SDL_INFORMATION_API = 6; -} - -``` - -``` - - APINAME_XAPP_DATA_SHARING_API = 7; -}; - -message ApiVersion { - optional string value = 1; -} - -// -----B----- -// BitString definition -message BitString { - optional bytes value = 1; - optional uint32 len = 2; -} - -// -----E----- -message EndpointInformation { - optional string domain_name = 1; - optional string ipv4_address = 2; - optional string ipv6_address = 3; - optional uint32 port = 4; -}; - -// -----G----- -// From E2AP Clause 9.2.6, "Global E2 Node ID" -message GlobalE2NodeId { - oneof node_type { - GlobalE2NodeGnbId gnb = 1; - GlobalE2NodeEnGnbId en_gnb = 2; - GlobalE2NodeNgEnbId ng_enb = 3; - GlobalE2NodeEnbId enb = 4; - } - - message GlobalE2NodeGnbId { - optional GlobalGnbId global_gnb_id = 1; - optional GlobalEnGnbId global_en_gnb_id = 2; - optional GnbCuUpId gnb_cu_up_id = 3; - optional GnbDuId gnb_du_id = 4; - } - - message GlobalE2NodeEnGnbId { - optional GlobalEnGnbId global_en_gnb_id = 1; - optional GnbCuUpId en_gnb_cu_up_id = 2; - optional GnbDuId en_gnb_du_id = 3; - } - - message GlobalE2NodeNgEnbId { - optional GlobalNgEnbId global_ng_enb_id = 1; - optional GlobalEnbId global_enb_id = 2; - optional NgEnbDuId ng_enb_du_id = 3; - } - - message GlobalE2NodeEnbId { - optional GlobalEnbId global_enb_id = 1; - } -} - -// From E2AP Clause 9.2.6, as part of "Global E2 Node ID" -message GlobalEnbId { - optional PlmnIdentity plmn_identity = 1; - oneof enb_id_choice { - BitString macro_enb_id = 2; - BitString home_enb_id = 3; - BitString short_macro_enb_id = 4; - BitString long_macro_enb_id = 5; - } -} - -// From E2AP Clause 9.2.6, as part of "Global E2 Node ID" -message GlobalEnGnbId { - optional PlmnIdentity plmn_identity = 1; - oneof en_gnb_id_choice { - BitString en_gnb_id = 2; - } -} - -``` - -``` - } -} - -// From E2AP Clause 9.2.6, as part of "Global E2 Node ID" -message GlobalGnbId { - optional PlmnIdentity plmn_identity = 1; - oneof gnb_id_choice { - BitString gnb_id = 2; - } -} - -// From E2AP Clause 9.2.6, as part of "Global E2 Node ID" -message GlobalNgEnbId { - optional PlmnIdentity plmn_identity = 1; - oneof ng_enb_id_choice { - BitString macro_ng_enb_id = 2; - BitString short_macro_ng_enb_id = 3; - BitString long_macro_ng_enb_id = 4; - } -} - -// From E2AP Clause 9.2.6, as part of "Global E2 Node ID" -message GnbCuUpId { - optional uint64 value = 1; -} - -// From E2AP Clause 9.2.6, as part of "Global E2 Node ID" -message GnbDuId { - optional uint64 value = 1; -} - -// -----N----- -// From E2AP Clause 9.2.6, as part of "Global E2 Node ID" -message NgEnbDuId { - optional uint64 value = 1; -}; - -// -----P----- -// From E2AP Clause 9.2.6, as part of "Global E2 Node ID" -message PlmnIdentity { - optional bytes value = 1; -}; - -message ProcedureTransactionId { - optional uint32 value = 1; -}; - -// -----R----- -// From E2AP Clause 9.2.8, "RAN Function ID" -message RanFunctionId { - optional uint32 value = 1; -}; - -// -----X----- -message XappId { - optional string value = 1; -} -``` - -## Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2025.12.08 | 03.00 | Version incremented for TSC approval. | -| 2025.11.11 | 02.00.04 | Enclosure of CRs:
CMCC-2025.09.17-WG3-CR-0026-RICAPI-Clarification on SDL data types in API discovery-v1.docx agreed at WG3 web conf. #274.
API abstract syntax version updates.
Editorial updates. | -| 2025.07.07 | 02.00.03 | Enclosure of CRs:
CMCC-2025.05.09-WG3-CR-0024-RICAPI-Restore the Proto code wrongly removed for E2 related and SDL APIs-v1.docx , and
CMCC-2025.05.12-WG3-CR-0025-RICAPI-Removing criticality fields in the message tabulars-v1.docx agreed at 202506 Fukuoka F2F RICARCH stream.
CMCC-2025.2.13-WG3-CR-0023-RICAPI-AIML Data Pipelining-v05.docx ,
CMCC-2025.2.13-WG3-CR-0022-RICAPI-AIML Inference-v05.docx ,
CMCC-2024.10.19-WG3-CR-0019-RICAPI-AIML Training-v07.docx , and
CMCC-2024.10.19-WG3-CR-0018-RICAPI-AIML MME-v08.docx agreed at WG3 web conf. #263.
Editorial updates. | -| 2025.04.27 | 02.00.02 | Enclosure of CRs:
CICT-2024.07.17-WG3-CR-0016- Message contents texts and reference v3.docx agreed at RICARCH #113.
NEC-2024.12.16-WG3-CR-0036-RICAPI-Add E2 SubscriptionModification-v03.docx agreed at 202502 Paris F2F RICARCH stream.
NEC-2025.02.02-WG3-CR-0037-RICAPI-Add E2 Query-v03.docx ,
NEC.AO-2025.02.05-WG3-CR-0038-RICAPI-qRPC Clean Slate-v02.docx ,
NOK-2025.02.21-WG3-CR-0005-RICAPI-API Discovery procedure-CORRECTIONS-v01.docx ,
NOK-2025.02.21-WG3-CR-0006-RICAPI-E2SMName-CORRECTIONS-v01.docx , and
CMCC.AO-2025.02.19-WG3-CR-0021-RICAPI-Guidelines for IE error handling-v1.docx agreed at RICARCH #115.
Editorial updates. | -| 2024.11.19 | 02.00.01 | Enclosure of CRs:
CMCC-2024.05.31-WG3-CR-00016-RICAPI-AIML API skeleton-v02.docx ,
CMCC-2024.05.31-WG3-CR-00017-RICAPI-AIML API protocol stack-v02.docx agreed at 202406 Incheon F2F RICARCH stream.
NEC-2024.09.17-WG3-CR-0032-RICAPI-add maxnoofAPIProfiles definition-v02.docx agreed at RICARCH #111.
Editorial updates. | -| 2024.04.01 | 02.00 | Version incremented for TSC approval. | -| 2024.04.01 | 01.00.06 | Editorial updates to capture comments received during on-line vote. | -| 2024.03.23 | 01.00.05 | Enclosure of CRs:
CMCC-2024.02.29-WG3-CR-0014-RICAPI-API registration service stage 3 definitions-v02.docx ,
NEC.AO-2024.02.07-WG3-CR-027-RICAPI- Introduction of qRPC for E2 related and SDL API - v5.docx ,
CMCC-2024.03.13-WG3-CR-0015-RICAPI-xApp's Endpoints for E2 Indications and E2 Subscription Delete Notifications-v01.docx agreed at RICARCH #102.
NOK-2023.12.04-WG3-CR0003-RICAPI-v6.docx agreed at WG3 regular #218.
Editorial updates. | -| 2024.03.14 | 01.00.04 | Enclosure of CRs:
CICT-2024.01.19-WG3-CR-0015-RICAPI corrections v2.docx agreed at RICARCH #100.
NOK-2023.02.01-WG3-CR0004-RICAPI-Timer-v3.docx agreed at 202402 Athens F2F RICARCH stream.
CMCC-2024.01.27-WG3-CR-0013-RICAPI-SDL Information API stage 3 updates-v03.docx , and
CMCC.AO-2024.01.21-WG3-CR-0012-RICAPI-xApp Data Sharing API and support for RAI-v04.docx agreed at RICARCH #101.
Editorial updates. | - -| | | | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2023.11.23 | 01.00.03 | Enclosure of CRs:
NEC-2023.08.17-WG3-CR-0019-RICAPI- Clarification on Data format-v02.docx agreed at RICARCH #93.
CICT-2023.09.11-WG3-CR-0014-Corrections on RICAPI v1.docx agreed at 202310 Phoenix F2F RICARCH stream.
Editorial updates. | -| 2023.08.14 | 01.00.02 | Adopt new TS template.
Enclosure of CR:
CMCC-2023.06.13-WG3-CR-0011-RICAPI-Correction of the BitString definition in GPB code-v02.docx agreed at RICARCH #92.
Editorial updates. | -| 2023.06.08 | 01.00.01 | Enclosure of CR:
CMCC.AO-2023.02.03-WG3-CR-0002-RICAPI-E2 Subscription Delete API Procedure (Platform initiated) descriptions and messages v05.docx agreed at 202302 Prague F2F RICARCH stream.
Editorial updates. | -| 2022.11.20 | 01.00 | Version incremented for TSC approval. | -| 2022.11.16 | 00.06.00 | Enclosure of CR:
VMW.AO-2022.11.11-WG3-CR-0003-RICAPI-Improvements on Proto3 definitions-v2.zip agreed at RICARCH #79.
Editorial updates. | -| 2022.11.12 | 00.05.00 | Enclosure of CR:
CMCC.AO-2022.11.09-WG3-CR-0010-RICAPI-Collection of Common IEs across API categories under Section 10-v1.zip agreed at RICARCH TG 20221111 Ad-hoc meeting.
Editorial updates. | -| 2022.11.09 | 00.04.00 | Copyright statement update in accordance to O-RAN alliance rules.
Enclosure of CRs:
CMCC.AO-2022.05.13-WG3-CR-0003-RICAPI-E2 related APIs overview v04.docx agreed at RICARCH #76.
AsiaInfo.AO-2022.08.05-WG3-CR-0004-RICAPI-Cause and Criticality Diagnostics IE Definition-v04.docx , and
CMCC.AO-2022.09.16-WG3-CR-0006-RICAPI-A1 related APIs overview v01.docx agreed at RICARCH #77.
CMCC.AO-2022.10.10-WG3-CR-0005-RICAPI-Proto3 Definitions for E2 related APIs-v1.zip agreed at 202210 Madrid F2F RICARCH stream.
CMCC-2022.08.17-WG3-CR-0004-RICAPI-Basic contents in Section 4-v3.docx ,
CMCC-2022.09.16-WG3-CR-0007-RICAPI-Enablement APIs overview for Section 9.1-v2.docx , and
CMCC-2022.11.01-WG3-CR-0009-RICAPI-Alignment on Message Type IEs for all API categories-v1.docx agreed at RICARCH #78.
CICT.AO-2021.06.01-WG3-CR-0004-procedural descriptions and msgs applied to A1-related API v9.zip ,
CMCC.AO-2022.10.25-WG3-CR-0008-SDL APIs overview and Proto3 Definitions-v3.zip ,
AsiaInfo.AO-2022.10.11-WG3-CR-0005-RICAPI-xApp Registration Procedure Description and Messages-v3.docx ,
AsiaInfo.AO-2022.10.20-WG3-CR-0006-RICAPI-Proto3 Definitions for Management APIs-v1.zip , and
CMCC.AO-2022.08.22-WG3-CR-0005-RICAPI-Proto3 Definitions for Enablement APIs-v4.zip agreed at RICARCH TG 20221108 Ad-hoc meeting.
Editorial updates. | -| 2022.08.10 | 00.03.00 | Clause assigned per API message.
Enclosure of CR:
AsiaInfo.AO-2021.11.17-WG3-CR-0001-RICAPI-E2 Subscription API Procedure descriptions and messages v09.docx agreed at RICARCH #74.
Minor editorial update. | - -| | | | -|------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2022.06.06 | 00.02.00 | Adoption of new O-RAN TS template.
Enclosure of CRs:
NOK-2022.03.21-WG3-CR-0001-RICAPI-E2NodeState-v02.docx agreed at RICARCH #67.
Lenovo.AO-2022.05.13-WG3-RICAPI-Enablement API procedure descriptions and definitions v04.docx ,
CICT-2022.04.22-WG3-CR-0009-Procedure Transaction Identity v3.docx ,
AsiaInfo.AO-2022.01.04-WG3-CR-0002-RICAPI-E2 Indication API Procedure descriptions and messages v04.docx , and
AsiaInfo.AO-2022.03.04-WG3-CR-0003-RICAPI-E2 Control API Procedure descriptions and messages v04.docx agreed at RICARCH #70.
Minor editorial update. | -| 2021.10.12 | 00.01.00 | Enclosure of CR VMW.AO-2021.07.14-WG3-CR-0002-SDLAPI-v04.docx agreed at RICARCH #56. | -| 2021.05.18 | 00.00.03 | Approved TS skeleton. | \ No newline at end of file diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/00504fc688ebcf131ccbeff94dfc9939_img.jpg deleted file mode 100644 index c5879fc7532d63a3f5192825852a683cb99c85f7..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/00504fc688ebcf131ccbeff94dfc9939_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7bfce5b51e4dd1b268e366861d2d4f09dae549c270aa6d77b927d34eb03fa8ae -size 29644 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/034b9d22fdb2e7e61ff3b15f229569bf_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/034b9d22fdb2e7e61ff3b15f229569bf_img.jpg deleted file mode 100644 index 387b9227d1f4e8e5590bcfacfe2114b5e4c363db..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/034b9d22fdb2e7e61ff3b15f229569bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2d2e165c5ad08aba8d6f96bc7e77f6814f652d7c1be0ecea1ea6548d7f90a40f -size 18548 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/060648daa95345c57f019fc00ad75993_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/060648daa95345c57f019fc00ad75993_img.jpg deleted file mode 100644 index 96b94d819bf14d328d6465605527d8ea7e8541b9..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/060648daa95345c57f019fc00ad75993_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a58d76f6d0a30b8029d568637065e946f60736d21103461ec659e7f3aa0243fc -size 49084 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index df515c946ae1ccf828363d5827150813de47e1a9..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:32868f4f82e88a218c7e459cff1b7a2eb4af345648962ef72324c3050b78e8bf -size 4544 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1274805226c5a1f8b875aea0296b9f0f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1274805226c5a1f8b875aea0296b9f0f_img.jpg deleted file mode 100644 index a98cbdb58c93806b7905d733c3ef7ba433ae466a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1274805226c5a1f8b875aea0296b9f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:06280b3e9c7818dc289ffe19422f1ae0b055d45483fc0d80b6754125fa0a6360 -size 31864 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/137bcfed81ada68ca5162ca5afed35c7_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/137bcfed81ada68ca5162ca5afed35c7_img.jpg deleted file mode 100644 index 70efaf6a4f0d22e11fc52c80e1687ae81d4fde3d..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/137bcfed81ada68ca5162ca5afed35c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:dccded8f23f475f573e1110a2fa8b95be9a3e9f438d6150f93cd8e2dceb16480 -size 23731 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1399c76ef88f22b70d05ed3f781d3c48_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1399c76ef88f22b70d05ed3f781d3c48_img.jpg deleted file mode 100644 index 64f3cdeff6fc788382ee07987d94f90385631efe..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1399c76ef88f22b70d05ed3f781d3c48_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:18852790979ded3e1cf212c8a96e7828fdf07cb01372f92fdcd8c1e48db47eb9 -size 40213 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/142c0ec898fdb4803450dd39592136c5_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/142c0ec898fdb4803450dd39592136c5_img.jpg deleted file mode 100644 index d5f3f96343c43a528e25353b644321f95390576f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/142c0ec898fdb4803450dd39592136c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f384b9c5185ee1550c6f0a1767ac34d6bd1b4a0249b49423e69343170eb466fd -size 25782 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/15d5c901284409186049549eec95c4a4_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/15d5c901284409186049549eec95c4a4_img.jpg deleted file mode 100644 index 3a262f264d8e5d713dbaf90392cf7985291b085a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/15d5c901284409186049549eec95c4a4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:151a64512ce22142e0cf45e1095c859f3bd7fa93e2eaa0295c08665309264ce8 -size 26419 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/18442e4e239480f0c3c95b547aa8fde2_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/18442e4e239480f0c3c95b547aa8fde2_img.jpg deleted file mode 100644 index f5e8ab93113c1d37232f5fbca235c92c4baf6587..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/18442e4e239480f0c3c95b547aa8fde2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0fa6da1df6b47eeda6d62512dbdf522cfc687ba3833a40ed23b6b6bc526252cc -size 25621 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/18b87e4ce7ef441f5620b8d6539a2939_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/18b87e4ce7ef441f5620b8d6539a2939_img.jpg deleted file mode 100644 index f19bf126f00c6aa4805bea131fa157d55c1bc2d3..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/18b87e4ce7ef441f5620b8d6539a2939_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:832696af68df1e63cf6ac32d6ad5c19230d42457dad68851e1e426235077d6e7 -size 25438 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1baaba7a6e54e77197475726c871067d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1bd6a020aa71784ed74367899560cbb9_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1bd6a020aa71784ed74367899560cbb9_img.jpg deleted file mode 100644 index ef551e46431724ca5e798ea3b223cfcfb0443caa..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1bd6a020aa71784ed74367899560cbb9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:913e44f1b57f376c1eae9c686b449468b4e90b0e92866a6c6da870dcb3670c5b -size 24966 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/24b10c86fe55f7126e355d9bc6fef7b9_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/24b10c86fe55f7126e355d9bc6fef7b9_img.jpg deleted file mode 100644 index 9c4c416c7fc71d3583361b2bfa09a5e9024ce8b0..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/24b10c86fe55f7126e355d9bc6fef7b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4521817c14df181c6fdbf1266a4fd55cd0daee18d9fb59efdc9689aede851b59 -size 22702 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/24c9e038a791677ed33100667b64f7e6_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/24c9e038a791677ed33100667b64f7e6_img.jpg deleted file mode 100644 index b3c21d8d9efe7c2bb91b0ab718846fb5fba3f98c..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/24c9e038a791677ed33100667b64f7e6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b8b5aee6ce398ff64813924afcd11beb2847c48da75ff6df4200b7fee454d5b -size 21382 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2837ffdadcdb1e5bababa56b564e56ed_img.jpg deleted file mode 100644 index f9c5eca1a0e9482b05ec02147b1aec2658b74a5d..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2837ffdadcdb1e5bababa56b564e56ed_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c1dee888bba4678ee9a5a72875f08db67108ef82e0a0d8612f33d113f88d86c2 -size 22129 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/28d75f39a24203712ee907b32cf0bbe5_img.jpg deleted file mode 100644 index 8eedaac28c4c09e838951d26e295c060d1bb5206..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/28d75f39a24203712ee907b32cf0bbe5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:cfdd7c0dabb0de14758260663d679dc60766f2d2334451eb64f59c343a2fc73a -size 25464 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2a185522b492253375ed16f0c515c230_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2a185522b492253375ed16f0c515c230_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2a185522b492253375ed16f0c515c230_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2d51fdeaad10ae6f1707dd372d200e23_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2d51fdeaad10ae6f1707dd372d200e23_img.jpg deleted file mode 100644 index 1866c78cefc38fd0fbdd13b6463a46a3fa9793d1..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2d51fdeaad10ae6f1707dd372d200e23_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:515550a645e74abe699a16f7d1f98114881ecbd0f66eddb52bdb36f4c2091595 -size 23764 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2e18ae7359d8c32e96919956f238ecc5_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2e18ae7359d8c32e96919956f238ecc5_img.jpg deleted file mode 100644 index c39fbe69129aec393b07a20f01b1b03d4314116b..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2e18ae7359d8c32e96919956f238ecc5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:884ea9a5403491a0c51bf21e0326f5b52a67ca18dafa251daf0d1be53e709dba -size 21251 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2eea01382188b70064fa2818361d89f1_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2eea01382188b70064fa2818361d89f1_img.jpg deleted file mode 100644 index 856584c5b574d8a266d5eae691e0614697cdad43..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2eea01382188b70064fa2818361d89f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:42e4c64d45fd3b39c682399bf2c8717353a24ac440ad04002ba7ddfb72671084 -size 4528 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2f108a589e99e93fd7aa8fac626398c7_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2f108a589e99e93fd7aa8fac626398c7_img.jpg deleted file mode 100644 index ae77e96392be8092922ef8d0294ffa87174f5579..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/2f108a589e99e93fd7aa8fac626398c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bd5bb8152898633438418b379835479a025c19b386bf5bcd79555c6001a4d495 -size 20914 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg deleted file mode 100644 index 856584c5b574d8a266d5eae691e0614697cdad43..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:42e4c64d45fd3b39c682399bf2c8717353a24ac440ad04002ba7ddfb72671084 -size 4528 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/314da473d582c4327e1e3d56fcba19dd_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/314da473d582c4327e1e3d56fcba19dd_img.jpg deleted file mode 100644 index c20f7ca65c048a0468f1f9f1736abaf6595eb9de..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/314da473d582c4327e1e3d56fcba19dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:83daec9a8d9ab5c828ac4d73f660204cb9e767e4103007f497393449d77a42f1 -size 23757 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3220d3a933797114c1ba20d5c4ec093d_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3220d3a933797114c1ba20d5c4ec093d_img.jpg deleted file mode 100644 index 8d076198c92eb82cc52165dcc30e1b7187e5c837..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3220d3a933797114c1ba20d5c4ec093d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d5c414fd8d50652e5bb825e844b2a524c653bc1546df0063044c2e809ed07992 -size 20245 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3295c6ffe9f6d00c3811c37d327ac844_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3295c6ffe9f6d00c3811c37d327ac844_img.jpg deleted file mode 100644 index 1ac1bd07adab2dbb5aa67fd80b25e3f34ccf85d2..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3295c6ffe9f6d00c3811c37d327ac844_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:22a565007bad5773eadbaa6ccf3334b8ea241e479584ca24c38090e45f0e7411 -size 23933 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/35437f160e157760713aa85be471c3f3_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/35437f160e157760713aa85be471c3f3_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/35437f160e157760713aa85be471c3f3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/363ee388a0fafdba587655050cf079d4_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/363ee388a0fafdba587655050cf079d4_img.jpg deleted file mode 100644 index b1fe3301d7e5317ace495f8ba75a93e86835fc64..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/363ee388a0fafdba587655050cf079d4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9c429513d32eb6585ea7921a5a4b32e7b6f385d16c6c249c2f8ce6dbbc7719c0 -size 23440 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/377087fbf1dd0a11c3a435bcd7b6fc35_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/377087fbf1dd0a11c3a435bcd7b6fc35_img.jpg deleted file mode 100644 index 9eb31140d48c4f561ea0bacf53330539137d6b1c..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/377087fbf1dd0a11c3a435bcd7b6fc35_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:13b62d0eb83456b3a0659cdab60f873bc08d9e7a2270b2a59a653a1866e32095 -size 24903 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/37e75e07bd69576f817434fc996be253_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/37e75e07bd69576f817434fc996be253_img.jpg deleted file mode 100644 index fd7644b555549b01cdfa43335998f82498676598..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/37e75e07bd69576f817434fc996be253_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ab508d9ab2a658971b759a458d5f3a54b78c09055d0dbcc1e2b8f390af25dd58 -size 26418 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index e873481907939580079c444e8a6a3d5f5f546b20..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b04c8ff60016f230051fd1e6b7faab682b49355b563a68403fc5d65e0720146f -size 4564 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3d13999d5257e24e629f65f28bf10251_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3d13999d5257e24e629f65f28bf10251_img.jpg deleted file mode 100644 index 97b5ad8ba44dd03a564856db1af298b13a2d4a16..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3d13999d5257e24e629f65f28bf10251_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bc368b001b2d28e5222ce12cb0bf491ae16209a900654a693e1256fa8206b43a -size 23342 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3d1817e8551f9c226a5f561108d3b3f9_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3d1817e8551f9c226a5f561108d3b3f9_img.jpg deleted file mode 100644 index dad72e339754ac3aafedc914118f8fb52ab8efe7..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/3d1817e8551f9c226a5f561108d3b3f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ac1fe543e80ac0232a60fed0676fca3a729f0511914fe40fd7ffb8435284707a -size 12663 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/43437211ce989e9da795fecc0d499c05_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/43437211ce989e9da795fecc0d499c05_img.jpg deleted file mode 100644 index b27580c8a5ac1dbe5f4716d96b938be5f2c85d1b..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/43437211ce989e9da795fecc0d499c05_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a6565ac25a28548e28d00b4d39616030da1c9e3c9c13862f4c24ebf89fc27aa0 -size 23493 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/435cf83a9531da350ea543aafa0add62_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/435cf83a9531da350ea543aafa0add62_img.jpg deleted file mode 100644 index 4ba13f41a2b1f5adec470361aa3203ddd18ce2f5..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/435cf83a9531da350ea543aafa0add62_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7eeef60007d9c5b30211641e484d77311e6e6efa72fdf6b884c5a75e2040ed70 -size 23316 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/47702b55f927e2e85ac03e79a7ebe350_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/47702b55f927e2e85ac03e79a7ebe350_img.jpg deleted file mode 100644 index e0fbfdb4b022a7641904a6a008db553b1fcfa509..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/47702b55f927e2e85ac03e79a7ebe350_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b7a2f4fa97e86ae0f954ddbedb001069e8084fc372d4ff4cc69fa2a68e9ea6d9 -size 21816 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/48fecf94dd9fb955caddbf2fb01b7b9b_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/48fecf94dd9fb955caddbf2fb01b7b9b_img.jpg deleted file mode 100644 index 4def18c4de887ca33c58e91721c65b9390073e6d..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/48fecf94dd9fb955caddbf2fb01b7b9b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fd12614bf899eb5bc455da2a45508cd6e1fe738de7aec86412d6413735a3d86c -size 19624 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg deleted file mode 100644 index b348a9f82ba9cbd555c0393af9cd9a011ec7a542..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f667258ed49de5b6f7b8b2ae1d502e5b16674ad1dee667503ea912247a83c522 -size 24057 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4fed8a9f7064898f635d0f83b0a1ae61_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4fed8a9f7064898f635d0f83b0a1ae61_img.jpg deleted file mode 100644 index 39d6aed919f6168d9f3f8613840966a21e789a78..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/4fed8a9f7064898f635d0f83b0a1ae61_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:28f7fc9bfd5c9fb2dfd2ff9f3d8831c54b66ec434ebbff7ff92b7329d72387e9 -size 25008 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/5009e30a55479d3941af523871208f9d_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/5009e30a55479d3941af523871208f9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/52c40e2f443985dc63f45dec57d90c8c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/52c40e2f443985dc63f45dec57d90c8c_img.jpg deleted file mode 100644 index f1cb3f38dcc6d40cb8fcc601a1bce2b25eddc3d1..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/52c40e2f443985dc63f45dec57d90c8c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:07175ea6d482ab2d5555d2786b8ced11e6878119add9ec31ab36e0471e969dad -size 12810 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg deleted file mode 100644 index cf30c7e86f59bc55081d84ad07d70ba9266771c4..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2d44f7eff1b861f7897b38601df0f1e74de0ef39ff5da4d7af193a475744d729 -size 4546 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/562f471e8153729557e6a4ee6343c32c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/562f471e8153729557e6a4ee6343c32c_img.jpg deleted file mode 100644 index dad72e339754ac3aafedc914118f8fb52ab8efe7..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/562f471e8153729557e6a4ee6343c32c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ac1fe543e80ac0232a60fed0676fca3a729f0511914fe40fd7ffb8435284707a -size 12663 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/568031aac86c633aab96b734dba3835e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/568031aac86c633aab96b734dba3835e_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/568031aac86c633aab96b734dba3835e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg deleted file mode 100644 index 41b641e819fb0d4c725fe6b2699b28a877da1ddf..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/56a42b3c4e1a79a71c8f27aa03b78b84_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4a4bbdb59f7008462523143a4e3d5762bd1c1b6a94651befb4e7ac81bebc0bee -size 21379 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/58b03f2cf75e3ec5b30e05d6002ceb20_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/58b03f2cf75e3ec5b30e05d6002ceb20_img.jpg deleted file mode 100644 index a1c4c969129b681804bc1cf6876469906e6b9ed6..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/58b03f2cf75e3ec5b30e05d6002ceb20_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:159f6153c543f65664b19d7f520701575a984c6f40eebcbe85866b600c3096a9 -size 26696 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/58df9e48362936fbfe061cf470485b4d_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/58df9e48362936fbfe061cf470485b4d_img.jpg deleted file mode 100644 index fa668799076bb97fd07ffa6b47160715b0157c0a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/58df9e48362936fbfe061cf470485b4d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:469799b43ba4d32e16d1f93c8e6e39770cbee14d26c6ec83ac8c4fa5b8c3a1e9 -size 21407 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/59368942873b0c35eef79a7a985025dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/599928760ca71d72f3248a3a9a07c446_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/599928760ca71d72f3248a3a9a07c446_img.jpg deleted file mode 100644 index 4d62cb35981c8413004d9bdc37d92c3411a997b3..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/599928760ca71d72f3248a3a9a07c446_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5ea76e4835da62cdfbdb3449122c5d9cfa867001c9ce0b692a7b2cac797a959b -size 20509 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/59e29b37c5e332b0be088cde8c4d217e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/59e29b37c5e332b0be088cde8c4d217e_img.jpg deleted file mode 100644 index 19837605ae28b939e41d184a1fa33c20dd69d468..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/59e29b37c5e332b0be088cde8c4d217e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e4437b91d1945534a76e7310b6bb9fd07de64abfddf2d39845c0dc6b101b1558 -size 22126 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/5a3dccee8ce4d2fa1986aba4ae8ad6e2_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/5a3dccee8ce4d2fa1986aba4ae8ad6e2_img.jpg deleted file mode 100644 index f80d7dfa95edd1a33944b09b45b3ad6d22874c84..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/5a3dccee8ce4d2fa1986aba4ae8ad6e2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8c1f23bca154a742eda144907398cf5dbaf65ec11c755be3eec5560c04f02f59 -size 23236 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/5e9af8986a5845504f251d3079da8078_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/5e9af8986a5845504f251d3079da8078_img.jpg deleted file mode 100644 index f0efbf354576069aa43ff4fd480aff754d45c9e3..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/5e9af8986a5845504f251d3079da8078_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5a2281ab99b862a0862d1011687fc98bc6edfcb13a217c60de2c1e87fc45640d -size 37994 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6059b0a3a051cc20b414d51a4e412f3e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6059b0a3a051cc20b414d51a4e412f3e_img.jpg deleted file mode 100644 index 3e94386c114457859b3fcd2e388d35f94eb0a595..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6059b0a3a051cc20b414d51a4e412f3e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:cdca46b44c3451e072049d316d049e997228bc5395d35b75e86e4af1c258622b -size 18281 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/60f844d947ea0bccdd9f64d81d5f8d26_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/60f844d947ea0bccdd9f64d81d5f8d26_img.jpg deleted file mode 100644 index d41967c6a4937b3aec857e6e5c07bd6217bc43bc..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/60f844d947ea0bccdd9f64d81d5f8d26_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f71aaccfa6fbf87ad5613ddf1280c29e8448aa3482aeadb1b1d6749cf838c82 -size 23359 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6588b1c7f14069d96744b473ad663248_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/67a1dd734d3de6e31754caf85d6fe77f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/67a1dd734d3de6e31754caf85d6fe77f_img.jpg deleted file mode 100644 index b4aae6e8af6f2f283eb3bf029609e8f9e9be64b0..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/67a1dd734d3de6e31754caf85d6fe77f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c1c3a2f8cff476ff8647e87c0e20641c94daa9c4b1ad58bd7b6b031d18566a25 -size 23298 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6983ff962c0a32659de18c30790e1519_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6983ff962c0a32659de18c30790e1519_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6983ff962c0a32659de18c30790e1519_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6e9d059430baba0c363e33749f68b107_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6e9d059430baba0c363e33749f68b107_img.jpg deleted file mode 100644 index e9accb0426cf78679507522a7ddda1a061d5f8d3..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6e9d059430baba0c363e33749f68b107_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:26f143211cfa7c8666f9c11233093fba64b095e9c071dd3f135e53ccb406fb74 -size 25023 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/78c6bfdfef4d292384fc7667315392ab_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/78c6bfdfef4d292384fc7667315392ab_img.jpg deleted file mode 100644 index bc553691a7ab2e0bcbb7d6ceed45c64b8554db96..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/78c6bfdfef4d292384fc7667315392ab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe7837c5e942dfd3a36878c0fe3728f4efabeeb536ac4ef80fcef48a3fb5e4a1 -size 23223 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 0a801dd2ecab3401992b48dc2bde5c829ec7a03b..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:610f672e2793f1c32c50e8d98df1c31573ef2d0985a7acb0fd53f3322fe617fb -size 4473 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg deleted file mode 100644 index 14b8dc9616e039a05bc8a6c296d92297fd01721f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/78ff716475b2f65bf01c3a4d02d89fc4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe94e04ef30269bd58af6fb9f583915a850c44443910179e25b5146512cc692d -size 22688 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index cf30c7e86f59bc55081d84ad07d70ba9266771c4..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2d44f7eff1b861f7897b38601df0f1e74de0ef39ff5da4d7af193a475744d729 -size 4546 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 9d55649b49cd8ee4bd4236d1939bb51c85a5ea2a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5dd8375d88bcff1ef4cdc77c712482c64e9df5833d7cec3b0f0b1d7c6ad98b64 -size 4603 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/805c475f0859e607af0530ba43194bf1_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/805c475f0859e607af0530ba43194bf1_img.jpg deleted file mode 100644 index 121d14245ebec9d8b4bdd9214c688c9ce657f684..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/805c475f0859e607af0530ba43194bf1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:155b857c6e2e0dbdc8af72944e4e9e6eb9ab7cca04d01ac08bbccaf6d82cb92e -size 24291 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/84a9ebc99b18f354f989e127c0974a26_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/84a9ebc99b18f354f989e127c0974a26_img.jpg deleted file mode 100644 index 08f95cb1c95a675084d9a1ea9bcfb48709762bd6..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/84a9ebc99b18f354f989e127c0974a26_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:76f5b38c9ba802eed2d40c3b90582fa59e1de16cc94e91822f0884f7bf346a75 -size 15232 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/84e5b251aa38db522f76f5cc3afcb853_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/84e5b251aa38db522f76f5cc3afcb853_img.jpg deleted file mode 100644 index 2ff329fe52e53c3a0f5b72f9c8ce6d6bc98e2fcb..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/84e5b251aa38db522f76f5cc3afcb853_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3939780e011ed403fc19b9ef95633328bf94b05db6357d5723cfc55c42ce675e -size 27078 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/878e3f080378afb04bb23d5863edc6a5_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/878e3f080378afb04bb23d5863edc6a5_img.jpg deleted file mode 100644 index a513599675a366a252766e6e4d909f9d8dcc5e12..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/878e3f080378afb04bb23d5863edc6a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1defc14e78359bc17d1c12fbe538ac4b09c48f223f41ee29ea5e8fb0c1977f08 -size 27605 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/884c44b6cb9fbe15347e0562a6085df2_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/884c44b6cb9fbe15347e0562a6085df2_img.jpg deleted file mode 100644 index 788d2b3377995bf4b35e56115a0a7ddc922bdf78..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/884c44b6cb9fbe15347e0562a6085df2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3af26521de89a73bfded2da218e4a40e5496efcf9a22cceb0eee9b6af1ba6a4a -size 22957 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/88e677d1623f443e57a730fe04a495a5_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/88e677d1623f443e57a730fe04a495a5_img.jpg deleted file mode 100644 index 41e0cc72615ac2ee0326428d4545d3a8058d2015..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/88e677d1623f443e57a730fe04a495a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3c83eccc62c9fb15cd7114b79e115669bb1bf91146fbed032e13ef732e1121ed -size 26961 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/8d1bb05debbaef0f72751449b2b55172_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/8d1bb05debbaef0f72751449b2b55172_img.jpg deleted file mode 100644 index 7020bd3babf24cae47570ddd7df8d2dc7ec55cfe..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/8d1bb05debbaef0f72751449b2b55172_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3a30cb41e19e5443b760eae8df155a2711959142a0416f453fdd4914703128e1 -size 36359 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 0a801dd2ecab3401992b48dc2bde5c829ec7a03b..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:610f672e2793f1c32c50e8d98df1c31573ef2d0985a7acb0fd53f3322fe617fb -size 4473 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/935075de5250cfe8aa0fb9d65d63dde5_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/935075de5250cfe8aa0fb9d65d63dde5_img.jpg deleted file mode 100644 index 9a643e7db0fbf9f6054208e1a6c6d1aeed59859a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/935075de5250cfe8aa0fb9d65d63dde5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:92a62ed5eebc0439c6767f1b72f010be1f65eeb6942d5c21a1a8c8b92d87ddde -size 23081 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/960c6a04d04a5d8683ae3d11235a4e68_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/960c6a04d04a5d8683ae3d11235a4e68_img.jpg deleted file mode 100644 index a05439eba3b59947295279c4ccfb21fe9069f6d9..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/960c6a04d04a5d8683ae3d11235a4e68_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7720c7a4a26a6d6a7b15df6ec8775820706e94f3313c8f7fda7865e3cac09971 -size 21417 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9c1d3678db4a12d5864cb2a4def1135d_img.jpg deleted file mode 100644 index 6675ddeff6b6bf9db06d1280489b575da4be5c8d..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9c1d3678db4a12d5864cb2a4def1135d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9c0c5878c0d8d2b2a11b5060086c1757c59679a6c8988eaf1d961c3943f43186 -size 25118 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9d1b506f1f6b6923761ba49bfb1e5b71_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9d1b506f1f6b6923761ba49bfb1e5b71_img.jpg deleted file mode 100644 index f4eff417080a16dcbe9a96effe8864015fb0a486..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9d1b506f1f6b6923761ba49bfb1e5b71_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:90f712706e55a961dd1d52b84c1f6a6b6df370ae707eb9e5dd51b6469aa290d0 -size 27070 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a02b188a5fd52c99f84255322873bf29_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a02b188a5fd52c99f84255322873bf29_img.jpg deleted file mode 100644 index 17f71bd6d03d0328206bb75249e04f020018b551..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a02b188a5fd52c99f84255322873bf29_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2e8806e46fcdddbff406d663652af478b94219c1bc9213d8674cd2ad6f6dcf7c -size 16652 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg deleted file mode 100644 index bc49fdc4cdc0ab8b695495a7abf3f97e4b950be4..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a5b9392ecb96e6b5e0b4ee0664210f72_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:682d2a65b6ef78debb2495377031482d30fd9f3725a921646fc97ca04253f4b4 -size 21457 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a76fa39f5daf6a026e032495262ed0f6_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a76fa39f5daf6a026e032495262ed0f6_img.jpg deleted file mode 100644 index ed913e22e3efd5705e8c1a86b33bf8c45f3026d3..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a76fa39f5daf6a026e032495262ed0f6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4fd3d2d88dc8ae0edb1ec9ecd2485c3d13f8bf5f2288f63c6370280adb4f734d -size 21959 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ad4da36431850ac19ba59bb74ec29dc9_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ad4da36431850ac19ba59bb74ec29dc9_img.jpg deleted file mode 100644 index 50d1eb0eb047e3ac8dfc08175539934f8d2f8296..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ad4da36431850ac19ba59bb74ec29dc9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:29dac86d134bb663bd18d0b39d82ee5ee39ba07317667f097c4f88dc1c87c5e7 -size 22023 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/aef4390a4629604196222b9ed006a786_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/aef4390a4629604196222b9ed006a786_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/aef4390a4629604196222b9ed006a786_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/af6be343f0c0a8f155f965dcf337b8af_img.jpg deleted file mode 100644 index 149b3eca39f49e1a5dba70b20147352e2b838e93..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/af6be343f0c0a8f155f965dcf337b8af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0ee6beb4de32a7f6562a3a0bde5c5d493f4503e9d47fe115c67e418a919f9f47 -size 24274 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b02ba0b73e95416eb547976f6145b169_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b02ba0b73e95416eb547976f6145b169_img.jpg deleted file mode 100644 index 0a3755aa6fde42d445b5e6851275fbd1a87e1979..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b02ba0b73e95416eb547976f6145b169_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c0d7bec0f7f1f319f1156de0163506fa8a9c955fde04819d969873d01cecfeaf -size 21244 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b51423b6c049f5b5fcde42e50b58f18b_img.jpg deleted file mode 100644 index e36112db916669b56c6c2ddbf487f3782a4bc714..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b51423b6c049f5b5fcde42e50b58f18b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9b0de92f4e1362c3583073f08561f1e2f6e2a109cd0ba76247b97a9467894cab -size 21415 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b55cd9b5721bd8aabc979c85316924e4_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b55cd9b5721bd8aabc979c85316924e4_img.jpg deleted file mode 100644 index e915837a0d84db1a29c4e718e721f98b959b8744..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b55cd9b5721bd8aabc979c85316924e4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7faf16a6ace81951579dea8c263e80c909f2ed3087cfaae08979f12e64445f53 -size 23103 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b904ac2472cab80892d1e783e6230d6e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b904ac2472cab80892d1e783e6230d6e_img.jpg deleted file mode 100644 index ff4bfd1619905e9b18568ddb43d16af271eef5e1..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b904ac2472cab80892d1e783e6230d6e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a7feeae4a3e7ff572e12059534b1a60c407fee70db2cebe557d419e12455b86 -size 21876 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg deleted file mode 100644 index e873481907939580079c444e8a6a3d5f5f546b20..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b04c8ff60016f230051fd1e6b7faab682b49355b563a68403fc5d65e0720146f -size 4564 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/bb3354f497635d15bef873577125c48d_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/bb3354f497635d15bef873577125c48d_img.jpg deleted file mode 100644 index 9a772c5491882319fb20dbdb235fac1581e858b9..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/bb3354f497635d15bef873577125c48d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f5c7fafdb9625676a75a8d7e5eb79328d53bd0f08812bd04b4125de003c0006e -size 22542 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c06fd7dbef68a8b788158f2081d9d734_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c06fd7dbef68a8b788158f2081d9d734_img.jpg deleted file mode 100644 index 53a7003300f4e68797b2b4e84fb9db915491020a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c06fd7dbef68a8b788158f2081d9d734_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8da251d56fbf562e20bfbd69fd59ff9d3a9b3a69ddaf8e36ab32c50400a166df -size 44037 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c24164782e328c82ba89b80c0ef8c3d7_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c24164782e328c82ba89b80c0ef8c3d7_img.jpg deleted file mode 100644 index bb3dd85ff910a63741c4c365e3d88e79d6837e21..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c24164782e328c82ba89b80c0ef8c3d7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c88c5575e5a274952b5e74e0ee09461bec6ab417606a1c3a5fe986356ffb1ac -size 13732 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c425a7b76be3f887bb251606c2a7ce9a_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c425a7b76be3f887bb251606c2a7ce9a_img.jpg deleted file mode 100644 index 4f955a0d8747d074d9611c728ffec6d5388f7d8a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c425a7b76be3f887bb251606c2a7ce9a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c3eaaedd77e96beed031c2ba618544633c727844bfff7ef2782a952cb12aecec -size 39383 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c77dfd42af832009a383aabc67238c2e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c77dfd42af832009a383aabc67238c2e_img.jpg deleted file mode 100644 index 37a437459b3c53b8cdc971efbc2c0ad242bedd58..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c77dfd42af832009a383aabc67238c2e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c3d1c06de46f692e1de67a5e4f9d4c6de3cb71b32325b01ff0e2c36e380c2b5a -size 24111 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/cc468dcda006ef315536400517a09ad3_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/cc468dcda006ef315536400517a09ad3_img.jpg deleted file mode 100644 index 54fd6707c82148fa752778daca65c83dd2e74a26..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/cc468dcda006ef315536400517a09ad3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:df67b1ba914c611ca49ddaf5b7cf68649b4f334bdd444cadfde2f20e89a931f8 -size 40579 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/cc7baa8e5118f4b42c01166637c738ea_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/cc7baa8e5118f4b42c01166637c738ea_img.jpg deleted file mode 100644 index 50a1f95dd3d24f4a76d32f790c1a6f3e2ec42f38..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/cc7baa8e5118f4b42c01166637c738ea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9b22e7e10d533e230bc8cfa44a9af0fc2382b211dbc9db1ed093095be8d729d2 -size 25200 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d01f4371bb8136148156771a18b9ea89_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d01f4371bb8136148156771a18b9ea89_img.jpg deleted file mode 100644 index ecb22795c0bdcbb61ae4c1eac79d9aab163e8906..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d01f4371bb8136148156771a18b9ea89_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d30f68e8f330ada828c25bfd05db3faa400e0c08ebdb9e95e51d0af71ee2442b -size 22544 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d17f75945bbb3feb84a153ecfedb9b81_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d17f75945bbb3feb84a153ecfedb9b81_img.jpg deleted file mode 100644 index de1887203840261b596f8b45b31bed39ca9de126..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d17f75945bbb3feb84a153ecfedb9b81_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:36ec3e26c87d38184e042e5d04034300b4f23b0a1c3730173ba8abe6056e2059 -size 25637 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d35a80e3faed208324083399568c7461_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d35a80e3faed208324083399568c7461_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d35a80e3faed208324083399568c7461_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg deleted file mode 100644 index 9cf4ef22b440f846295d5b1939fc3f04f7a76b63..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0fcf34603fd5e098f76f9182714166e02733350f7df034a0a0ee00a521f7021b -size 11890 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dbcee1610ecdaa500f5b11abf307ea5d_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dbcee1610ecdaa500f5b11abf307ea5d_img.jpg deleted file mode 100644 index e246fb8328e330b63afcd5fd3f66725134465745..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dbcee1610ecdaa500f5b11abf307ea5d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4dd141a75055bcd0ae78ec8344d86557603747a5f6607db3e10be79197071dd8 -size 21921 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dbf5c0f3c7836f717d9fe62c6c40b280_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dbf5c0f3c7836f717d9fe62c6c40b280_img.jpg deleted file mode 100644 index 4a46847044b1991fb66d7bb965ddd0476f0f6bfe..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dbf5c0f3c7836f717d9fe62c6c40b280_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:25db816e7d1d8d175ba610aa70e3b178fb558eb3b4365180c0009b8d00ca4164 -size 24783 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg deleted file mode 100644 index c3f69d2bbfed112efc9df19f4ae9e1997af03b38..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dcc2d5a5b39f780e7a224bb01ba1ef6e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b4a22db49f5337758d78ac345de0cbf876425542660369af17dd860b7c0bb2a8 -size 21426 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg deleted file mode 100644 index 769d12e87eba0fdc285ee327c51c6a00294a006b..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/dfa6249d64e9f63db89f2c5b7bbd01de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018be83952b2d073956125cb81346f22fcfa085709dde7eeba6f66d6e2bd143e -size 28420 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e05b36c0d46549e681ce6581422c66b2_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e05b36c0d46549e681ce6581422c66b2_img.jpg deleted file mode 100644 index 9951afe455e78c2c195820d7752b2a32b6f649bf..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e05b36c0d46549e681ce6581422c66b2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:26439c7f97a29c88b8829e4ac28db61a443a35e802f18400fae72d4939cf453d -size 28911 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index 856584c5b574d8a266d5eae691e0614697cdad43..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:42e4c64d45fd3b39c682399bf2c8717353a24ac440ad04002ba7ddfb72671084 -size 4528 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e29665b8abcea967ef289c6aff07ae4c_img.jpg deleted file mode 100644 index 189c953448b4e3196b36c91dd6bf67045dc4f7cb..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e29665b8abcea967ef289c6aff07ae4c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:616da0617be55806960f20a1a6e592a60eb447970d59f858c8b4540d2a4e4256 -size 24955 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e4aab374983ba0fc24496fe7cd11c06c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e4aab374983ba0fc24496fe7cd11c06c_img.jpg deleted file mode 100644 index 292759ccfbaec3ddc1f5ae6b4d526d2ef7981dfb..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e4aab374983ba0fc24496fe7cd11c06c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e8d21dcf23e9559718a07e9425e4db1ac704c369e0b9e8d825583c04ee0ee1ce -size 13623 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg deleted file mode 100644 index 0fc816d8c5946b1bc236faf7d5af4249c52c8d74..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e5d1bcc699904ca5d56caf65ec83f5f3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d7216d9120a3ffa245703725117ad4132a2c4169cb6f81fa0b59ddd2b983cf81 -size 17425 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e67bca96ac67ddab7a8762b49d4c438d_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e67bca96ac67ddab7a8762b49d4c438d_img.jpg deleted file mode 100644 index f8afcc6d893be5e42410460ad8b00c048f56a74b..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e67bca96ac67ddab7a8762b49d4c438d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7b044d48498196ea2996bdbbc2926792f73de395c167828186be167888339e03 -size 24966 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg deleted file mode 100644 index 58bc8a4b29963f0fb40ff10e53375b9ff9f913f7..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e7c6a6e4c3047dac05a3b92e396e9794_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:75898dbd5330df3f3e6daa2c16fd1543f73f112d435aff47f0e295aea66d830c -size 22252 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg deleted file mode 100644 index 3995840720594c7916c02f45fe9ee55d83fefc95..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e821c3d8a87ee2a9ff6b8644ffe6bdae_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a11d0a9431395623d7d481ab0aca81655d6319767f51b42ee5d17baa15b8222e -size 22978 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg deleted file mode 100644 index 856584c5b574d8a266d5eae691e0614697cdad43..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:42e4c64d45fd3b39c682399bf2c8717353a24ac440ad04002ba7ddfb72671084 -size 4528 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg deleted file mode 100644 index 823e9da5bdfb0c27631e5e70010f1b2310444435..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fdd1ff5affaa4d16853904300a6a7d81caf8213959bb356edf24b70bbd79e87f -size 25259 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/eaad3504edeecffe148decdc5c04a171_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/eaad3504edeecffe148decdc5c04a171_img.jpg deleted file mode 100644 index 37c3bfbdd17ada23bb7110ac58ab82ca5aa44210..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/eaad3504edeecffe148decdc5c04a171_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:882012376b3efdda24bce11e9fcbd3ebe38bcf543761ae51fd9efb6bbd654156 -size 23010 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/eae05333c9188c830bd0ebe58c50453a_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/eae05333c9188c830bd0ebe58c50453a_img.jpg deleted file mode 100644 index f26f63ce28bcebb149151e1af9f111340dc028bd..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/eae05333c9188c830bd0ebe58c50453a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:70641bd2767d0a765e85aa4b82dc1877d23824f9e31c3d0bab296aefea56b362 -size 17629 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ecae674475cecdd0962200a5d1e2591e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ecae674475cecdd0962200a5d1e2591e_img.jpg deleted file mode 100644 index 8fc89bd473f7eb76ebf2641d570bb25d437228fa..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ecae674475cecdd0962200a5d1e2591e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:31c876dd594c08eb4c55c1b32aa515334a2c5a21ef10db48a1fa46ed6b6f5f3b -size 25393 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f1cbfa3fc27f58581615654fec4335d8_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f1cbfa3fc27f58581615654fec4335d8_img.jpg deleted file mode 100644 index 62b0c6e896dbc52b0c7e9158b9af409a1ca05fa0..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f1cbfa3fc27f58581615654fec4335d8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3d3e28092fae938830a0b1a9b762b8cefb4940c3b0fede968d4047b1d6da879f -size 21881 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg deleted file mode 100644 index 15e86c304c1f3f21d05008ebd06d870aa5ce4f0c..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:78ff650a946c3fde8cfd00c18257cab63070e403d850fac805ed9a056e9ca7fd -size 24793 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f4e64712104f326ff259928d8126f1f6_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f4e64712104f326ff259928d8126f1f6_img.jpg deleted file mode 100644 index f50cd3cd0f24c3e295f7a0b3a95988b16ee498fd..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f4e64712104f326ff259928d8126f1f6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c97ab3836f3f16a400294824164f6403a75b67e1766b5c36babffcc4dca5efc6 -size 21966 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f74adaa1840504407cd4272995426f82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg deleted file mode 100644 index cf30c7e86f59bc55081d84ad07d70ba9266771c4..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2d44f7eff1b861f7897b38601df0f1e74de0ef39ff5da4d7af193a475744d729 -size 4546 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/fac227c65a311c313325216dcf59591f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/fac227c65a311c313325216dcf59591f_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/fac227c65a311c313325216dcf59591f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/facce731b2dbfae43a8609231a700be1_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/facce731b2dbfae43a8609231a700be1_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/facce731b2dbfae43a8609231a700be1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/fcc757566216206ceddbd6c775e8db02_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/fcc757566216206ceddbd6c775e8db02_img.jpg deleted file mode 100644 index 531184830902ed359d158b37d5a9b49bde454fd2..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/fcc757566216206ceddbd6c775e8db02_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b5f3a45bc6cb02619012264b608469ae1ef1ab03fcf9ecf47f2d6e27278a7849 -size 24772 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.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/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ff0952ef692c9d960ce5f6708bcc9711_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ff0952ef692c9d960ce5f6708bcc9711_img.jpg deleted file mode 100644 index b0fd8c66da5795be09a8090132a093b0e2412214..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ff0952ef692c9d960ce5f6708bcc9711_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:512d57dcb5d2d0933facacd0b89add7ca1a41be4d8428081267d73bb96c6dfad -size 26043 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ff722ae9516b94709d721deaf5523d2e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ff722ae9516b94709d721deaf5523d2e_img.jpg deleted file mode 100644 index 055d201600a14fcfa525dce1d5503b19d18d681c..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ff722ae9516b94709d721deaf5523d2e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:68935712bbb7a795173c0897d16a7cf044091511d63a4d41fbe10c0269400f14 -size 23978 diff --git a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICAPI-R005-v03.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/doc.md b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/doc.md deleted file mode 100644 index c8e039fd1adba095a76dde18b059215edb1473d5..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/doc.md +++ /dev/null @@ -1,7469 +0,0 @@ - - -# --- **O-RAN Work Group 3 (Near-Real-time RAN Intelligent Controller and E2 Interface)** - -# **Near-RT RIC 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..... | 5 | -| Modal verbs terminology ..... | 5 | -| 1 Scope..... | 6 | -| 2 References ..... | 6 | -| 2.1 Normative references ..... | 6 | -| 2.2 Informative references ..... | 7 | -| 3 Definition of terms, symbols and abbreviations ..... | 7 | -| 3.1 Terms ..... | 7 | -| 3.2 Symbols..... | 7 | -| 3.3 Abbreviations..... | 7 | -| 4 General Principles ..... | 8 | -| 5 Near-RT RIC Architecture ..... | 8 | -| 5.1 Requirements ..... | 8 | -| 5.1.0 Overall Requirements..... | 8 | -| 5.1.1 Platform Requirements..... | 8 | -| 5.1.2 xApp Requirements..... | 9 | -| 5.1.3 Near-RT RIC API Requirements ..... | 10 | -| 5.2 Overall Architecture Description..... | 11 | -| 6 Near-RT RIC Functional Description ..... | 11 | -| 6.1 General..... | 11 | -| 6.2 Functionalities of the Near-RT RIC platform..... | 12 | -| 6.2.1 Database and SDL ..... | 12 | -| 6.2.2 xApp Subscription Management..... | 13 | -| 6.2.3 Conflict Mitigation..... | 13 | -| 6.2.4 Messaging Infrastructure..... | 13 | -| 6.2.5 Security..... | 13 | -| 6.2.6 Management..... | 14 | -| 6.2.7 Interface Termination..... | 14 | -| 6.2.8 API Enablement ..... | 15 | -| 6.2.9 AI/ML Support..... | 15 | -| 6.2.10 xApp Repository Function ..... | 16 | -| 6.3 xApps ..... | 16 | -| 6A Services of Near-RT RIC platform and xApps ..... | 17 | -| 6A.1 General..... | 17 | -| 6A.2 Services provided by Near-RT RIC platform ..... | 17 | -| 6A.2.1 Overview ..... | 17 | -| 6A.2.2 A1 related services ..... | 19 | -| 6A.2.3 E2 related services..... | 19 | -| 6A.2.4 Management related services ..... | 20 | -| 6A.2.5 SDL services ..... | 20 | -| 6A.2.6 Enablement services..... | 21 | -| 6A.2.7 AI/ML services..... | 22 | -| 6A.3 Services provided by xApps ..... | 23 | -| 6A.3.1 Overview ..... | 23 | -| 6A.3.2 A1 related services ..... | 23 | -| 6A.3.3 E2 related services..... | 24 | -| 6A.3.4 Management related services ..... | 24 | -| 6A.3.5 SDL services ..... | 24 | -| 6A.3.6 Enablement services..... | 25 | -| 7 Near-RT RIC APIs ..... | 25 | - -- 7.1 Overall Description..... 25 - - 7.1.1 Introduction ..... 25 - - 7.1.2 Near-RT RIC API approaches..... 25 - - 7.1.3 Network API approach..... 28 - - 7.1.4 SDK approach ..... 28 - - 7.1.5 Near-RT RIC API support options..... 29 -- 7.2 Void..... 32 -- 7.3 Void..... 32 -- 7.4 Void..... 32 -- 7.5 Void..... 32 -- 7.6 Void..... 32 -- 7.7 Void..... 32 -- 8 External Interfaces of Near-RT RIC ..... 32 - - 8.1 E2 Interface ..... 32 - - 8.2 A1 Interface ..... 32 - - 8.3 O1 Interface ..... 32 - - 8.4 Y1 Interface ..... 32 -- 9 Near-RT RIC API Procedures..... 32 - - 9.1 General..... 32 - - 9.1A Conventions for procedure description ..... 33 - - 9.2 A1 Related API Procedures ..... 33 - - 9.2.1 Introduction ..... 33 - - 9.2.2 A1 Policy procedures ..... 34 - - 9.2.3 A1-EI related procedures ..... 45 - - 9.3 E2 Related API Procedures..... 59 - - 9.3.1 Introduction ..... 59 - - 9.3.2 RIC Functional Procedures ..... 60 - - 9.3.3 E2 Conflict Mitigation related procedures ..... 83 - - 9.4 Management API Procedures ..... 91 - - 9.4.1 xApp Registration procedure ..... 91 - - 9.4.2 xApp Deregistration procedure ..... 93 - - 9.4.3 Void..... 94 - - 9.4.4 Create MOI..... 94 - - 9.4.5 Modify MOI attributes ..... 95 - - 9.4.6 Delete MOI..... 96 - - 9.4.7 Read MOI attributes..... 97 - - 9.4.8 Notify MOI changes..... 98 - - 9.4.9 Subscription Control ..... 100 - - 9.4.10 Fault Notification ..... 101 - - 9.4.11 Fault Supervision Control ..... 102 - - 9.4.12 Performance Data File Reporting..... 103 - - 9.4.13 Report Streamed Data ..... 104 - - 9.4.14 Measurement Job Control ..... 105 - - 9.5 SDL API Procedures..... 106 - - 9.5.1 Void..... 106 - - 9.5.2 Void..... 106 - - 9.5.3 Fetch Data procedure ..... 106 - - 9.5.4 Subscribe/Update-Notify procedure..... 107 - - 9.5.5 Store Data procedure ..... 108 - - 9.5.6 Modify Data procedure ..... 109 - - 9.5.7 Subscribe/Push procedure ..... 110 - - 9.5.7A xApp Shared Data Fetch procedure ..... 111 - - 9.5.7B Procedures related to xApp Shared Data Subscription and Notification ..... 112 - - 9.5.8 Use cases of SDL APIs ..... 115 - - 9.5.9 SDL API data structures..... 122 - - 9.6 API Enablement Procedures ..... 124 - - 9.6.1 API Discovery procedure ..... 124 - - 9.6.2 Procedures related to API Event Subscription and Notification ..... 125 - -| | | | -|----------------------------------------------------------------------------------------|--------------------------------------------------------|-----| -| 9.6.3 | Procedures related to API Registration ..... | 130 | -| 9.7 | AI/ML API Procedures ..... | 136 | -| 9.7.1 | Data Pipelining service procedures ..... | 136 | -| 9.7.2 | Training service procedures ..... | 143 | -| 9.7.3 | Inference service procedures ..... | 148 | -| 9.7.4 | Model Management and Exposure Service procedures ..... | 155 | -| Annex A (informative): Potential conflict types among xApps for RRM optimization ..... | | 161 | -| Annex B (informative): Example of xApp's workflow ..... | | 162 | -| Annex (informative): Change History ..... | | 165 | - -# --- Foreword - -This Technical Specification (TS) has been produced by WG3 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 overall Near-RT-RIC (Near-real-time RAN Intelligent Controller) architecture and functionalities, including interaction between hosted applications and common functions in the Near-RT RIC platform. - -# --- 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] Void. -- [2] O-RAN.WG3.TS.E2GAP, “O-RAN Working Group 3, Near-Real-time RAN Intelligent Controller, E2 General Aspects and Principles”. -- [3] O-RAN.WG3.TS.E2AP, “O-RAN Working Group 3, Near-Real-time RAN Intelligent Controller, E2 Application Protocol (E2AP)”. -- [4] O-RAN.WG10.TS.OAM-Architecture, “O-RAN Operations and Maintenance Architecture”. -- [5] O-RAN.WG10.TS.O1-Interface, “O-RAN Operations and Maintenance Interface Specification”. -- [6] 3GPP TS 33.401: “3GPP System Architecture Evolution (SAE); Security architecture”. -- [7] 3GPP TS 33.501: “Security architecture and procedures for 5G System”. -- [8] O-RAN.WG2.TS.A1GAP, “O-RAN Working Group 2, A1 interface: General Aspects and Principles”. -- [9] O-RAN.WG2.TS.A1AP, “O-RAN Working Group 2, A1 Interface: Application Protocol”. -- [10] O-RAN.WG1.TS.OAD, “O-RAN Working Group 1, O-RAN Architecture Description”. -- [11] Void. -- [12] Void. -- [13] Void. -- [14] Void. -- [15] Void. -- [16] Void. -- [17] Void. -- [18] Void. -- [19] Void. - -- [20] O-RAN.WG6.TS.ORCH-USE-CASES, "Orchestration Use Cases and Requirements for O-RAN Virtualized RAN". -- [21] 3GPP TS 28.622: "Generic Network Resource Model (NRM)". -- [22] O-RAN.WG11.TS.Security-Requirements-Specification: "O-RAN Security Requirements and Controls Specification". -- [23] O-RAN.WG3.TS.Y1GAP: "Y1 interface: General Aspects and Principles". -- [24] O-RAN.WG3.TS.Y1AP: "Y1 interface: Application Protocol". - -## 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 3GPP TR 21.905 [i.1], O-RAN.WG1.TS.OAD [10] and the following apply: - -Void. - -## 3.2 Symbols - -For the purposes of the present document, the symbols given in [i.1] and the following apply: - -Void. - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given in [i.1] and the following apply: - -| | | -|-------|--------------------------------| -| E2SM | E2 Service Model | -| IE | Information Element | -| LCM | Life-Cycle Management | -| MnS | Management Service | -| R-NIB | Radio-Network Information Base | - -| | | -|--------|--------------------------------------| -| SCTP | Stream Control Transmission Protocol | -| SDK | Software Development Kit | -| SDL | Shared Data Layer | -| UE-NIB | UE-Network Information Base | - -# --- 4 General Principles - -The general principles for Near-RT RIC architecture are as follows: - -- The Near-RT RIC architecture and internal interfaces shall be open to support 3rd party xApps. - -# --- 5 Near-RT RIC Architecture - -## 5.1 Requirements - -### 5.1.0 Overall Requirements - -- [REQ-Overall-001] Void. - -### 5.1.1 Platform Requirements - -- [REQ-Platform-Generic-001] Near-RT RIC platform shall provide a service to expose up-to-date RAN information, history of time-varying network state, as well as configurations related to E2 Nodes, Cells, Bearers, Flows, UEs, and the mapping between them; -- [REQ-Platform-Generic-002] Near-RT RIC shall provide AI/ML support for data pipelining, model management, training and inference; -- [REQ-Platform-Generic-003] Near-RT RIC platform shall provide a messaging infrastructure; -- [REQ-Platform-Generic-004] Near-RT RIC platform shall provide O1 support for file management, tracing and metrics collected from Near-RT RIC platform and xApps toward SMO; -- [REQ-Platform-Generic-005] Near-RT RIC platform shall comply with WG11 security requirements [22]; -- [REQ-Platform-Generic-006] Near-RT RIC platform shall support mitigation of E2 related conflicts between xApps; -- [REQ-Platform-API-001] Near-RT RIC platform shall expose Near-RT RIC APIs; -- [REQ-Platform-API-002] The Near-RT RIC platform APIs shall be discoverable by xApp; -- [REQ-Platform-API-003] Void; -- [REQ-Platform-Generic-007] Void; -- [REQ-Platform-Generic-008] Near-RT RIC platform shall support subscription merging from multiple xApps; -- [REQ-Platform-Generic-009] Void; -- [REQ-Platform-Generic-010] Near-RT RIC platform shall be able to route A1 policy management messages to the registered xApps based on A1 policy type; -- [REQ-Platform-Generic-011] Near-RT RIC platform shall control access of A1-EI types for xApps based on operator policies; - -- [REQ-Platform-Management-001] The Near-RT RIC platform shall support the capability over O1 interface to expose the list of active alarms for the Near-RT RIC platform and hosted xApps; -- [REQ-Platform-Management-002] The Near-RT RIC platform shall have the capability to report, over the O1 interface, PM measurements associated with individual xApps; -- [REQ-Platform-Management-003] The Near-RT RIC platform shall support the capability over O1 interface to manage individual xApp's Administrative State. -- [REQ-Platform-Management-004] The Near-RT RIC platform shall support the capability over O1 interface to read the current configuration of individual xApps; -- [REQ-Platform-Management-005] The Near-RT RIC platform shall support the capability over O1 interface to notify of any change in the xApp configuration; -- [REQ-Platform-Management-006] The Near-RT RIC platform shall support the capability over O1 interface to notify of an associated MOI creation; -- [REQ-Platform-Management-007] The Near-RT RIC platform shall support the capability over O1 interface to notify of an associated MOI deletion; -- [REQ-Platform-Management-008] The Near-RT RIC platform shall support the capability over O1 interface to notify of an associated MOI modification; -- [REQ-Platform-Management-009] The Near-RT RIC platform shall support the capability over O1 interface to notify that there is a file available; -- [REQ-Platform-Management-010] The Near-RT RIC platform shall support PM data subscriptions for xApp streamed data; -- [REQ-Platform-Management-011] The Near-RT RIC platform shall support the capability over O1 interface to configure the xApp to produce specific PM data; -- [REQ-Platform-Management-012] The Near-RT RIC platform shall support the file transfer capability over O1 interface. - -### 5.1.2 xApp Requirements - -- [REQ-xApp-Generic-001] Void; -- [REQ-xApp-E2Related-001] Void; -- [REQ-xApp-E2Related-002] xApp shall use Near-RT RIC APIs to make use of the Information Elements (IEs) of E2SMs that are associated with it; -- [REQ-xApp-E2Related-003] Void; -- [REQ-xApp-E2Related-004] Void; -- [REQ-xApp-Generic-002] xApp shall provide collected logging, tracing and metrics information to Near-RT RIC; -- [REQ-xApp-Descriptor-001] Void; -- [REQ-xApp-Descriptor-002] Void; -- [REQ-xApp-API-001] xApps shall communicate with Near-RT RIC platform via Near-RT RIC APIs; -- [REQ-xApp-API-002] xApp shall register the Near-RT RIC APIs it produces; -- [REQ-xApp-API-003] xApp shall be capable of discovering the Near-RT RIC APIs it consumes; -- [REQ-xApp-Management-001] xApp shall be configurable based on config received over O1 interface; - -- [REQ-xApp-Management-002] xApp shall expose configuration options to activate handling of individual A1 policy type when the xApp supports multiple A1 policy types. - -### 5.1.3 Near-RT RIC API Requirements - -- [REQ-API-Generic-001] Void; -- [REQ-API-Generic-002] Near-RT RIC APIs shall not adversely impact low-latency and high throughput operations of Near-RT RIC. Specifically, the Near-RT RIC APIs shall support the Near-RT RIC control loop of execution time from 10 milliseconds to 1 second; -- [REQ-API-Generic-003] Near-RT RIC APIs shall be decoupled from specific implementation solutions, including a Shared Data Layer (SDL) that works as an overlay for underlying databases and enables simplified data access; -- [REQ-API-Generic-004] Near-RT RIC APIs shall support an API repository/registry for the services provided by the Near-RT RIC platform and/or xApps; -- [REQ-API-Generic-005] Near-RT RIC APIs shall provide means for xApps to discover the published APIs based on the xApps' needs; -- [REQ-API-Generic-006] Near-RT RIC APIs shall provide means to restrict xApps from discovering some published APIs based on configured policies; -- [REQ-API-Generic-007] Near-RT RIC APIs shall aim to simplify the development of xApps and enable rapid innovation; -- [REQ-API-Generic-008] Near-RT RIC APIs shall support xApp development in multiple programming languages (e.g., C, C++, Python, Go); -- [REQ-API-Generic-009] Near-RT RIC APIs shall support xApp subscription management based on operators' policies. An xApp may be restricted to interface with only a subset of E2 Nodes by such policies. Near-RT RIC shall be responsible for routing messages between this xApp and the subset of E2 Nodes; -- [REQ-API-Generic-010] Near-RT RIC APIs shall support mitigation of E2 related conflicts between xApps; -- [REQ-API-E2Related-001] Near-RT RIC APIs shall enable all xApps to directly use the information elements of E2SMs with which they are associated; -- [REQ-API-E2Related-002] The Near-RT RIC E2 Related APIs shall expose event-triggered RAN information and time-varying network state. -- [REQ-API-Management-001] The Near-RT RIC APIs for xApp management shall provide the capability to configure the xApp; -- [REQ-API-Management-002] The Near-RT RIC APIs for xApp management shall provide the capability to change the administrative state of the xApp; -- [REQ-API-Management-003] The Near-RT RIC APIs for xApp management shall provide the capability to read the current configuration of the xApp; -- [REQ-API-Management-004] The Near-RT RIC APIs for xApp management shall provide the capability for the xApp to notify the Management Function of any change in the xApp configuration; -- [REQ-API-Management-005] The Near-RT RIC APIs for xApp management shall provide the capability for the xApp to notify the Management Function of an associated MOI Creation; -- [REQ-API-Management-006] The Near-RT RIC APIs for xApp management shall provide the capability for the xApp to notify the Management Function of an associated MOI Deletion; - -- [REQ-API-Management-007] The Near-RT RIC APIs for xApp management shall provide the capability for the xApp to notify the Management Function of a fault detection; -- [REQ-API-Management-008] The Near-RT RIC APIs for xApp management shall provide the capability for the Consumer (SMO) to fetch the list of Active Faults on the xApp; -- [REQ-API-Management-009] The Near-RT RIC APIs for xApp management shall provide the capability for the xApp to notify the Management Function that there is a file available; -- [REQ-API-Management-010] The Near-RT RIC APIs for xApp management shall provide the capability for the Management Function to configure the xApp to send streaming data; -- [REQ-API-Management-011] The Near-RT RIC APIs for xApp management shall provide the capability for the Management Function to configure the xApp to collect specific PM data. - -## 5.2 Overall Architecture Description - -The overall O-RAN architecture specified in [10] describes the location and interfaces of Near-RT RIC, as well as possible deployment options. - -A Near-RT RIC shall be connected to only one Non-RT RIC. - -A Near-RT RIC can be connected to one or more E2 Nodes as described in [2]. - -The RRM functional allocation between Near-RT RIC and E2 Node is described in [2]. - -# --- 6 Near-RT RIC Functional Description - -## 6.1 General - -A Near-RT RIC is composed of a Near-RT RIC platform and one or more xApps. An overview is shown in Figure 6.1-1. - -Figure 6.1-1 also shows the functionalities of the Near-RT RIC platform. Those functionalities are further described in clause 6.2. - -![Near-RT RIC Architecture Overview diagram showing Service Management and Orchestration (SMO), Y1 Consumers, Near-RT RIC, and E2 Nodes. The diagram illustrates the flow of data and control between these entities through various interfaces (O1, A1, Y1, E2) and internal components like xApps and the Near-RT RIC platform.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) - -The diagram illustrates the Near-RT RIC Architecture Overview. At the top, the Service Management and Orchestration (SMO) block contains the Non-RT RIC. To its right, Y1 Consumers are shown. Below the SMO is the Near-RT RIC block, which contains multiple xApps (xApp 1, xApp 2, ..., xApp N). These xApps are connected to the Near-RT RIC platform via Near-RT RIC APIs. The Near-RT RIC platform is composed of several functional blocks: O1 Termination, A1 Termination, xApp Subscription Management, Conflict Mitigation, Y1 Termination, Shared Data Layer, AI/ML Support, Messaging Infrastructure, Security, API Enablement, Database, Management, xApp Repository, and E2 Termination. At the bottom, E2 Nodes are shown, connected to the Near-RT RIC platform via the E2 interface. A legend at the bottom right indicates that solid boxes represent 'Functional entity' and dashed boxes represent 'Functionality'. - -Near-RT RIC Architecture Overview diagram showing Service Management and Orchestration (SMO), Y1 Consumers, Near-RT RIC, and E2 Nodes. The diagram illustrates the flow of data and control between these entities through various interfaces (O1, A1, Y1, E2) and internal components like xApps and the Near-RT RIC platform. - -Figure 6.1-1: Near-RT RIC Architecture Overview - -## 6.2 Functionalities of the Near-RT RIC platform - -### 6.2.1 Database and SDL - -#### 6.2.1.0 Overview - -The database and SDL functionalities enable the Near-RT RIC platform to maintain and expose RAN/UE information and other information required to support specific use cases. - -#### 6.2.1.1 UE-NIB - -This functionality enables the Near-RT RIC platform to maintain UE related information: - -- Maintaining a list of UEs and associated data; -- Tracking and correlation of the UE identities associated with the connected E2 Nodes. - -Such information may be generated and accessed by the Near-RT RIC platform or authorized xApps. - -#### 6.2.1.2 R-NIB - -This functionality enables the Near-RT RIC platform to maintain RAN related information: - -- Maintaining the configurations and near real-time information relating to connected E2 Nodes and the mappings between them. - -Such information may be generated and accessed by the Near-RT RIC platform or authorized xApps. - -#### 6.2.1.3 SDL - -This functionality enables the Near-RT RIC platform to provide SDL services for xApps. xApps may use such services to subscribe to database notifications and to read, write and modify information stored on the database. UE-NIB, R-NIB and other use case specific information may be exposed using the SDL services. - -### 6.2.2 xApp Subscription Management - -This functionality enables the Near-RT RIC platform to handle subscription requests from different xApps for E2 related data, and provide unified data distribution to xApps for those data: - -- Managing subscriptions from xApps to E2 Nodes; -- Enforcing authorization of policies controlling xApp access to messages; -- Enabling merging of identical subscriptions from different xApps into a single subscription toward an E2 Node; -- Enabling audit of existing subscriptions and initiating associated corrective actions. - -### 6.2.3 Conflict Mitigation - -This functionality enables the Near-RT RIC platform to detect and resolve potentially overlapping or conflicting requests from multiple xApps. - -In the context of Near-RT RIC, Conflict Mitigation is about addressing conflicting interactions between different xApps. An application will typically change one or more parameters with the objective of optimizing a specific metric. Conflict Mitigation is necessary because xApps objectives may be chosen/configured such that they result in conflicting actions. - -### 6.2.4 Messaging Infrastructure - -This functionality enables the Near-RT RIC platform with low-latency message delivery between Near-RT RIC internal endpoints. It provides support for the following: - -- Endpoint registration/discovery/deletion: - - Registration: Endpoints register themselves to the messaging infrastructure; - - Discovery: Endpoints are discovered by the messaging infrastructure initially and registered to the messaging infrastructure; - - Deletion: Endpoints are deleted once they are not used anymore. -- APIs for sending/receiving messages from/to the messaging infrastructure: -- Multiple messaging modes, e.g., point-to-point mode (e.g., message exchange among endpoints), publish/subscribe mode (e.g., real-time data dispatching from E2 termination to multiple subscriber xApps); -- Message routing, namely according to the message routing information, messages can be dispatched to different endpoints; -- Message robustness, to avoid data loss during a messaging infrastructure outage/restart or to release resources from the messaging infrastructure once a message is outdated. - -### 6.2.5 Security - -The security functionality given in this clause only applies to Near-RT RIC. One of the targets of this functionality is to prevent malicious xApps from abusing radio network information (e.g., exporting to unauthorized external systems) and/or - -control capabilities over RAN functions. The security requirements for the 3GPP LTE eNB is defined in [6] and for the 5G NR gNB in [7]. - -### 6.2.6 Management - -#### 6.2.6.1 Void - -#### 6.2.6.2 OAM Management of Near-RT RIC - -OAM management consists of fault, configuration, accounting, performance, file, security and other management plane services. OAM management follows O1 related management aspects defined in [4]. - -To support OAM management services, Near-RT RIC platform shall provide the following capabilities: - -- Fault Management: The Near-RT RIC platform provides Near-RT RIC Fault Supervision MnS over the O1 interface as defined in [4]; -- Configuration management: The Near-RT RIC platform provides Near-RT RIC Provisioning MnS over the O1 interface as defined in [4]; -- Logging: logging is to capture information needed to operate, troubleshoot and report on the performance of the Near-RT RIC platform and its constituent components. Log records may be viewed and consumed directly by users and systems, indexed and loaded into a data storage, and used to compute metrics and generate reports. Near-RT RIC components log events according to a common logging format. Different logs can be generated (e.g., audit log, metrics log, error log and debug log). -- Tracing: tracing mechanisms are needed to monitor the transactions or a workflow. An example subscription workflow can be broken into two traces namely, a subscription request trace followed by a response trace. Individual traces can be analysed to understand timing latencies as the workflow traverses a particular Near-RT RIC component. -- Metrics collection: metrics for performance and fault management specific to each xApp logic and other internal functionalities are collected and published for authorized consumer (e.g., SMO). - -### 6.2.7 Interface Termination - -#### 6.2.7.1 E2 Termination - -This functionality enables termination of E2 interface with the following: - -- Terminating SCTP connection from each E2 Node; -- Routing messages from xApps through the SCTP connection to an E2 Node; -- Decoding the payload of an incoming ASN.1 message enough to determine message type; -- Handling incoming E2 messages related to E2 connectivity; -- Receiving and responding to the E2 Setup Request from an E2 Node; -- Notifying xApps of the list of RAN functions supported by an E2 Node based on information derived from the E2 Setup and RIC Service Update procedures [3]; -- Notifying the newly connected E2 Node of the list of accepted functions. - -#### 6.2.7.2 A1 Termination - -This functionality enables termination of A1 interface with the following: - -- Providing a generic API by means of which Near-RT RIC can receive and send messages via A1 interface [8]. These include, e.g., A1 policies and enrichment information received from Non-RT RIC, or A1 policy feedback sent towards Non-RT RIC. -- Sending A1 policy that is set or updated by the Non-RT RIC to suitable xApp(s) based on a list of candidate xApp(s) provided by xApp Repository functionality. - -#### 6.2.7.3 O1 Termination - -This functionality enables termination of O1 interface. - -An implementation of O1 Termination at Near-RT RIC depends on the deployment options described in [4], i.e., when Near-RT RIC is modelled as a stand-alone Managed Element. - -Near-RT RIC platform shall communicate with SMO via O1 interface. It exposes O1-related management services [5] from Near-RT RIC, and translates O1 management services to Near-RT RIC internal APIs. For the O1 management services (MnS) shown below, Near-RT RIC platform is the MnS producer and SMO is the MnS consumer: - -- Exposing provisioning management services from Near-RT RIC to O1 provisioning management service consumer; -- Exposing FM services to report faults and events from Near-RT RIC to O1 FM service consumer; -- Exposing PM services to report bulk and real-time PM data from Near-RT RIC to O1 PM service consumer; -- Exposing file management services to download ML files, software files, etc. and upload log/trace files to/from file MnS consumer; -- Exposing communication surveillance services to O1 communication surveillance service consumer. - -#### 6.2.7.4 Y1 Termination - -This functionality enables the termination of Y1 interface. - -It provides support for exposing RAN analytics information from Near-RT RIC to Y1 consumers. - -### 6.2.8 API Enablement - -This functionality provides support for registration, discovery and consumption of Near-RT RIC APIs: - -- Repository / Registry for the Near-RT RIC APIs; -- Discovery of the registered Near-RT RIC APIs; -- Authentication of xApps for use of the Near-RT RIC APIs; -- API related event subscription and notification; -- Means to avoid compatibility clashes between xApps and the services they access. - -NOTE: Different xApps (e.g., 3rd party xApp, RIC-owned xApp, etc.) may be associated with different levels of trust by the Near-RT RIC. - -### 6.2.9 AI/ML Support - -#### 6.2.9.0 Introduction - -The AI/ML support functionality enables the Near-RT RIC platform with data pipelining, model management, training and inference, which constitute complete AI/ML workflow support for xApps to implement AI/ML algorithms. xApps may use none, part, or all of this functionality, depending on its design. - -#### 6.2.9.1 Data Pipelining - -This functionality enables the Near-RT RIC platform with data ingestion and preparation for xApps. - -The input may include E2 node data collected over E2 interface, enrichment information over A1 interface, information from xApps, and data retrieved from the Near-RT RIC database through the messaging infrastructure. - -The output is data sets that are ready to be consumed by AI/ML Model. The output may be stored in an xApp specific space (e.g., a dedicated space in database) or used as input for inference (see clause 6.2.9.3). - -#### 6.2.9.1A Model Management - -The Near-RT RIC platform offers storage, retrieval, and version control of AI/ML models for xApps. The Near-RT RIC platform may store the model in an xApp specific space (e.g., a dedicated space in database), and tracks the version change of the model if the model is retrained or updated later. - -#### 6.2.9.2 Training - -This functionality enables the Near-RT RIC platform to perform AI/ML model training for xApps. The AI/ML model training capability is generic that may be used by AI/ML-based xApps for multiple use cases. The associated AI/ML models are managed by the Near-RT RIC platform (see clause 6.2.9.1A). The input data for training may come from an xApp specific space (e.g., dedicated space in database). - -#### 6.2.9.3 Inference - -This functionality enables the Near-RT RIC platform to perform AI/ML model inference for xApps. The associated AI/ML models are managed by the Near-RT RIC platform (see clause 6.2.9.1A). The input data may be the output of data pipelining, or come from an xApp specific space (e.g., a dedicated space in database). The inference result may be provided to the requesting xApp or stored in an xApp specific space (e.g., a dedicated space in database). - -### 6.2.10 xApp Repository Function - -This functionality enables the Near-RT RIC platform with the following: - -- Maintaining a list of candidate xApp(s) to A1 Termination for sending A1 policy or policy update to suitable xApp(s) based on policy type and operator policies; -- Maintaining the policy types supported in Near-RT RIC. The supported policy types are based on policy types supported by the registered xApps and operator policies; -- Performing xApp access control to requested A1-EI type based on operator policies. - -## 6.3 xApps - -The xApps collaborate with the Near-RT RIC platform to support various specialized use cases. - -The xApps may collaborate with Near-RT RIC platform to support mitigation of E2 related conflicts. - -xApp may be used to enhance the RRM capability in RAN. - -xApp may leverage zero, one or more E2SMs. - -Upon registration to the Near-RT RIC platform, an xApp shall inform the Near-RT RIC platform of its OAM and control information to enable relevant functionalities. - -NOTE: The LCM of xApp is performed by SMO and O-Cloud as specified in [4] and [20]. - -# 6A Services of Near-RT RIC platform and xApps - -## 6A.1 General - -Among the Near-RT RIC platform and the xApps, 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. Those services can be leveraged via the Near-RT RIC APIs described in clause 7. - -The interactions between service consumer and service producer are generalized that the service requests are sent from the service consumer and responses and notifications are sent from the service producer. It is the service producer that handles the resources on which the service consumer performs operations. The terms service consumer and service producer thus, do not refer to the direction of the data transfer over the Near-RT RIC APIs. - -A service-based representation is illustrated in Figure 6A.1-1. - -![Figure 6A.1-1: Service-based representation for internal Near-RT RIC. The diagram shows three stacked boxes at the top labeled 'xApp'. Below them is a horizontal line labeled 'Near-RT RIC API(s)'. At the bottom is a box labeled 'Near-RT RIC platform'. Vertical lines connect each 'xApp' box to the API line, and from the API line to the platform box. Each connection point on the API line has a small circle with a dot, representing a service interface.](36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg) - -Figure 6A.1-1: Service-based representation for internal Near-RT RIC. The diagram shows three stacked boxes at the top labeled 'xApp'. Below them is a horizontal line labeled 'Near-RT RIC API(s)'. At the bottom is a box labeled 'Near-RT RIC platform'. Vertical lines connect each 'xApp' box to the API line, and from the API line to the platform box. Each connection point on the API line has a small circle with a dot, representing a service interface. - -**Figure 6A.1-1: Service-based representation for internal Near-RT RIC** - -The services can be classified into the following categories, in regard to the relevant functionalities: - -- A1 related services; -- E2 related services; -- Management related services; -- SDL services; -- Enablement services; -- AI/ML workflow services. - -The services provided by the Near-RT RIC platform and the xApps are described in clause 6A.2 and 6A.3, respectively. - -## 6A.2 Services provided by Near-RT RIC platform - -### 6A.2.1 Overview - -An overview of the services that may be provided by the Near-RT RIC platform is shown in Table 6A.2.1-1: - -**Table 6A.2.1-1: Services provided by the Near-RT RIC platform** - -| Service Category | Service Name | Description | -|-----------------------------|---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| A1 related services | A1 EI service | This service enables the service consumer to create/update/delete/audit subscriptions to A1 Enrichment Information. It also enables the service consumer to query the Near-RT RIC platform of the supported A1 EI type(s) and the created A1 EI job(s). | -| E2 related services | E2 Subscription service | This service enables the service consumer to create/delete/modify/audit an E2 subscription related to applicable RIC services [2] with Near-RT RIC platform. The subscribed information is delivered with E2 Indication service.
This service also enables the service consumer to be queried or notified of deleting an existing E2 subscription.
(NOTE) | -| | E2 Indication service | This service enables the service consumer to receive subscribed E2 information associated with an E2 subscription. | -| | E2 Control service | This service enables the service consumer to access RIC service "CONTROL" [2] with the Near-RT RIC platform. | -| | E2 Guidance service | This service enables the service consumer to acquire E2 guidance information from the Near-RT RIC platform to avoid conflicts described in clause 6.2.3. | -| | E2 Query service | This service enables the service consumer to access RIC service "QUERY" [2] with the Near-RT RIC platform. | -| Management related services | xApp Registration service | This service enables service consumer to register/deregister itself with the Near-RT RIC platform. | -| SDL services | SDL Information service | This service enables the service consumer to store and retrieve data while hiding details such as type and location of database, management operations of database layer such as high availability, scaling, load-balancing.
This service supports defined data structures used to provide E2 Node related information. | -| Enablement services | Enabl Registration service | This service enables service consumer to register its service. | -| | Enabl Discovery service | This service enables service consumer to discover services registered by the Near-RT RIC platform and the xApps. | -| | Enabl Event service | This service enables the service consumer to create/delete subscriptions to Near-RT RIC API related events. It also enables notifications of the subscribed Near-RT RIC API related events. | -| AI/ML workflow services | Data Pipelining service | This service enables the service consumer to ingest and prepare data for AI/ML model training and/or inference with the Near-RT RIC platform. | -| | AI/ML Model Management and Exposure service | This service enables the service consumer to store and, retrieve AI/ML models with the Near-RT RIC platform for inference and/or training, The service also supports exposure of shared AI/ML models. | -| | AI/ML Training service | This service enables the service consumer to train AI/ML models with the Near-RT RIC platform. | - -| Service Category | Service Name | Description | -|------------------|-------------------------|-----------------------------------------------------------------------------------------------------| -| | AI/ML Inference service | This service enables the service consumer to perform AI/ML inference with the Near-RT RIC platform. | - -NOTE: Support for E2 interface Global Procedures (E2 SETUP, RIC Service Update, etc.) is described in clause 9.5.8 as use cases of SDL services. - -### 6A.2.2 A1 related services - -#### 6A.2.2.1 A1 EI service - -The A1 EI service supports the following operations in Table 6A.2.2.1-1. - -**Table 6A.2.2.1-1: List of A1 EI service operations** - -| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | Reference | -|---------------|---------------------------|--------------------|-------------------|-----------| -| A1 EI service | A1 EI query | Request/Response | xApp | 9.2.3.1 | -| | A1 EI subscription setup | Request/Response | xApp | 9.2.3.2 | -| | A1 EI subscription update | Request/Response | xApp | 9.2.3.3 | -| | A1 EI subscription delete | Request/Response | xApp | 9.2.3.4 | -| | A1 EI delivery | Notify | xApp | 9.2.3.5 | - -### 6A.2.3 E2 related services - -#### 6A.2.3.1 E2 Subscription service - -The E2 Subscription service supports the following operations in Table 6A.2.3.1-1. - -**Table 6A.2.3.1-1: List of E2 Subscription service operations** - -| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | Reference | -|-------------------------|-------------------------------------|--------------------|-------------------|-----------| -| E2 Subscription service | E2 Subscription | Request/Response | xApp | 9.3.2.1 | -| | E2 Subscription Delete | Request/Response | xApp | 9.3.2.2 | -| | E2 Subscription Delete Query | Request/Response | xApp | 9.3.2.2A | -| | E2 Subscription Delete Notification | Notify | xApp | 9.3.2.2A | -| | E2 Subscription Audit | Request/Response | xApp | 9.3.2.5 | -| | E2 Subscription Modification | Request/Response | xApp | 9.3.2.7 | - -#### 6A.2.3.2 E2 Indication service - -The E2 Indication service supports the following operations in Table 6A.2.3.2-1. - -**Table 6A.2.3.2-1: List of E2 Indication service operations** - -| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | Reference | -|-----------------------|--------------------|--------------------|-------------------|-----------| -| E2 Indication service | E2 Indication | Notify | xApp | 9.3.2.3 | - -#### 6A.2.3.3 E2 Control service - -The E2 Control service supports the following operations in Table 6A.2.3.3-1. - -**Table 6A.2.3.3-1: List of E2 Control service operations** - -| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | Reference | -|--------------------|--------------------|--------------------|-------------------|-----------| -| E2 Control service | E2 Control | Request/Response | xApp | 9.3.2.4 | - -#### 6A.2.3.4 E2 Guidance service - -The E2 Guidance service supports the following operations in Table 6A.2.3.4-1. - -**Table 6A.2.3.4-1: List of E2 Guidance service operations** - -| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | Reference | -|---------------------|--------------------------|--------------------|-------------------|-----------| -| E2 Guidance service | E2 Guidance | Request/Response | xApp | 9.3.3.1 | -| | E2 Guidance Modification | Notify | xApp | 9.3.3.5 | - -#### 6A.2.3.5 E2 Query service - -The E2 Query service supports the following operations in Table 6A.2.3.5-1. - -**Table 6A.2.3.5-1: List of E2 Query service operations** - -| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | Reference | -|------------------|--------------------|--------------------|-------------------|-----------| -| E2 Query service | E2 Query | Request/Response | xApp | 9.3.2.6 | - -### 6A.2.4 Management related services - -#### 6A.2.4.1 xApp Registration service - -The xApp Registration service supports the following operations in Table 6A.2.4.1-1. - -**Table 6A.2.4.1-1: List of xApp Registration service operations** - -| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | Reference | -|---------------------------|---------------------|--------------------|-------------------|-----------| -| xApp Registration service | xApp Registration | Request/Response | xApp | 9.4.1 | -| | xApp Deregistration | Request/Response | xApp | 9.4.2 | - -### 6A.2.5 SDL services - -#### 6A.2.5.1 SDL Information service - -The SDL Information service supports the following operations in Table 6A.2.5.1-1. - -**Table 6A.2.5.1-1: List of SDL Information service operations** - -| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | Reference | -|-------------------------|-------------------------------|--------------------|-------------------|--------------| -| SDL Information service | SDL Information Fetch | Request/Response | xApp | 9.5.3 | -| | SDL Subscription Information | Request/Response | xApp | 9.5.4, 9.5.7 | -| | SDL Information Update Notify | Notify | xApp | 9.5.4 | -| | SDL Information Push | Notify | xApp | 9.5.7 | -| | SDL Information Store | Request/Response | xApp | 9.5.5 | -| | SDL Information Modify | Request/Response | xApp | 9.5.6 | - -### 6A.2.6 Enablement services - -#### 6A.2.6.1 Enabl Registration service - -The Enabl Registration service supports the following operations in Table 6A.2.6.1-1. - -**Table 6A.2.6.1-1: List of Enabl Registration service operations** - -| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | Reference | -|----------------------------|-------------------------|--------------------|-------------------|-----------| -| Enabl Registration service | API Registration | Request/Response | xApp | 9.6.3.1 | -| | API Registration Update | Request/Response | xApp | 9.6.3.2 | -| | API Deregistration | Request/Response | xApp | 9.6.3.3 | - -#### 6A.2.6.2 Enabl Discovery service - -The Enabl Discovery service supports the following operations in Table 6A.2.6.2-1. - -**Table 6A.2.6.2-1: List of Enabl Discovery service operations** - -| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | Reference | -|-------------------------|--------------------|--------------------|-------------------|-----------| -| Enabl Discovery service | API Discovery | Request/Response | xApp | 9.6.1 | - -#### 6A.2.6.3 Enabl Events service - -The Enabl Events service supports the following operations in Table 6A.2.6.3-1. - -**Table 6A.2.6.3-1: List of Enabl Events service operations** - -| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | Reference | -|----------------------|-------------------------------|--------------------|-------------------|-----------| -| Enabl Events service | API Event Subscription | Request/Response | xApp | 9.6.2.1 | -| | API Event Subscription Delete | Request/Response | xApp | 9.6.2.2 | -| | API Event Notification | Notify | xApp | 9.6.2.3 | - -### 6A.2.7 AI/ML services - -#### 6A.2.7.1 Data Pipelining service - -The Data Pipelining service supports the following operations in Table 6A.2.7.1-1. - -| Table 6A.2.7.1-1:
List of Data
Pipelining
service
operationsService
Name
| Service Operations | Operation
Semantic
| Known
Consumer(s)
| Reference | -|-----------------------------------------------------------------------------------------------------|---------------------------------|-------------------------------|------------------------------|------------------| -| Data Pipelining service | Data Pipelining Job Setup | Request/Response | xApp | 9.7.1.1 | -| | Data Pipelining Job Update | Request/Response | xApp | 9.7.1.2 | -| | Data Pipelining Job Delete | Request/Response | xApp | 9.7.1.3 | -| | Data Pipelining Job Query | Request/Response | xApp | 9.7.1.4 | -| | Data Pipelining Request | Request/Response | xApp | 9.7.1.5 | -| | Data Pipelining Result Delivery | Notify | xApp | 9.7.1.5 | - -#### 6A.2.7.2 Training service - -The Training service supports the following operations in Table 6A.2.7.2-1. - -**Table 6A.2.7.2-1: List of Training service operations** - -| Service Name | Service Operations | Operation
Semantic
| Known
Consumer(s)
| Reference | -|---------------------|---------------------------|-------------------------------|------------------------------|------------------| -| Training Service | Training Job Setup | Request/Response | xApp | 9.7.2.1 | -| | Training Job Delete | Request/Response | xApp | 9.7.2.2 | -| | Training Job Query | Request/Response | xApp | 9.7.2.3 | -| | Training Request | Request/Response | xApp | 9.7.2.4 | -| | Training Result Delivery | Notify | xApp | 9.7.2.4 | - -#### 6A.2.7.3 Inference service - -The Inference service supports the following operations in Table 6A.2.7.3-1. - -**Table 6A.2.7.3-1: List of Inference service operations** - -| Service Name | Service Operations | Operation
Semantic
| Known
Consumer(s)
| Reference | -|---------------------|---------------------------|-------------------------------|------------------------------|------------------| -| Inference Service | Inference Job Setup | Request/Response | xApp | 9.7.3.1 | -| | Inference Job Update | Request/Response | xApp | 9.7.3.2 | -| | Inference Job Delete | Request/Response | xApp | 9.7.3.3 | -| | Inference Job Query | Request/Response | xApp | 9.7.3.4 | -| | Inference Request | Request/Response | xApp | 9.7.3.5 | -| | Inference Result Delivery | Notify | xApp | 9.7.3.5 | - -#### 6A.2.7.4 Model Management and Exposure service - -| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | Reference | -|---------------------------------------|--------------------|--------------------|-------------------|-----------| -| Model Management and Exposure Service | Model Store | Request/Response | xApp | 9.7.4.1 | -| | Stored Model Query | Request/Response | xApp | 9.7.4.2 | -| | Model Retrieve | Request/Response | xApp | 9.7.4.3 | -| | Model Delete | Request/Response | xApp | 9.7.4.4 | - -## 6A.3 Services provided by xApps - -### 6A.3.1 Overview - -An overview of the services that may be provided by the xApps is shown in Table 6A.3.1-1: - -**Table 6A.3.1-1: Services provided by the xApps** - -| Service Category | Service Name | Description | -|-----------------------------------------------------------------------|----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| A1 related services | A1 Policy service | This service enables the service consumer to create/update/delete/query an A1 policy object [8] for the xApp, and to be notified of the status of the A1 policy object. It also enables the service consumer to query the xApp about the supported A1 policy type(s). | -| E2 related services | E2 Conflict Mitigation Support service | The service enables the service consumer to obtain processing and information support from xApps for conflict mitigation. This service also enables the service consumer to obtain a negotiated conflict avoidance agreement from xApps. | -| Management related services (NOTE) | xApp Configuration service | This service enables the service consumer to configure the xApp. | -| | xApp PM service | This service enables the service consumer to collect PM related information from the xApp. | -| | xApp FM service | This service enables the service consumer to collect faults and events information from the xApp. | -| SDL services | xApp data sharing service | The service enables the service consumer to collect specific data shared by the xApp. | -| NOTE: Trace related service is not specified in the present document. | | | - -### 6A.3.2 A1 related services - -#### 6A.3.2.1 A1 Policy service - -The A1 Policy service supports the following operations in Table 6A.3.2.1-1. - -**Table 6A.3.2.1-1: List of A1 Policy service operations** - -| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | Reference | -|-------------------|-------------------------|--------------------|----------------------|-----------| -| A1 Policy service | A1 Policy Setup | Request/Response | Near-RT RIC platform | 9.2.2.1 | -| | A1 Policy Update | Request/Response | Near-RT RIC platform | 9.2.2.2 | -| | A1 Policy Delete | Request/Response | Near-RT RIC platform | 9.2.2.3 | -| | A1 Policy Query | Request/Response | Near-RT RIC platform | 9.2.2.4 | -| | A1 Policy Status Update | Notify | Near-RT RIC platform | 9.2.2.5 | - -### 6A.3.3 E2 related services - -#### 6A.3.3.1 E2 Conflict Mitigation Support service - -**Table 6A.3.3.1-1: List of E2 Conflict mitigation support service operations** - -| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | Reference | -|----------------------------------------|----------------------------------------------|--------------------|----------------------------|-----------| -| E2 Conflict Mitigation Support Service | E2 Conflict Mitigation Processing | Request/Response | Near-RT RIC platform | 9.3.3.6.1 | -| | E2 Conflict Mitigation Information | Request/Response | Near-RT RIC platform | 9.3.3.6.1 | -| | E2 Conflict Avoidance Negotiation | Request/Response | Near-RT RIC platform | 9.3.3.6.2 | -| | E2 Conflict Avoidance Negotiation Indication | Notify | xApp, Near-RT RIC platform | 9.3.3.6.2 | - -### 6A.3.4 Management related services - -#### 6A.3.4.1 xApp Configuration service - -``` -void -``` - -#### 6A.3.4.3 xApp PM service - -``` -void -``` - -#### 6A.3.4.4 xApp FM service - -``` -void -``` - -### 6A.3.5 SDL services - -#### 6A.3.5.1 xApp data sharing service - -The xApp data sharing service supports the following operations in Table 6A.3.5.1-1. - -**Table 6A.3.5.1-1: List of xApp Data sharing service operations** - -| Service Name | Service Operations | Operation Semantic | Known Consumer(s) | Reference | -|---------------------------|--------------------------------------|--------------------|----------------------------|-----------| -| xApp Data Sharing service | xApp Shared Data Fetch | Request/Response | Near-RT RIC platform, xApp | 9.5.7A | -| | xApp Shared Data Subscription | Request/Response | Near-RT RIC platform, xApp | 9.5.7B.1 | -| | xApp Shared Data Subscription Delete | Request/Response | Near-RT RIC platform, xApp | 9.5.7B.2 | -| | xApp Shared Data Push | Notify | Near-RT RIC platform, xApp | 9.5.7B.1 | - -### 6A.3.6 Enablement services - -Void. - -# 7 Near-RT RIC APIs - -## 7.1 Overall Description - -### 7.1.1 Introduction - -The Near-RT RIC APIs are a collection of well-defined interfaces providing Near-RT RIC platform and xApp services. These APIs need to explicitly define the possible types of information flows and data models. The Near-RT RIC APIs are essential to host 3rd party xApps in an inter-operable way on different Near-RT RIC platforms. - -The Near-RT RIC APIs consist of the following: - -- A1 related APIs: APIs to access A1 related services; -- E2 related APIs: APIs to access E2 related services; -- Management APIs: APIs to access management related services; -- SDL APIs: APIs to access Shared Data Layer related services; -- Enablement APIs: APIs to access enablement services; -- AI/ML workflow APIs: APIs to access AI/ML workflow services. - -### 7.1.2 Near-RT RIC API approaches - -Near-RT RIC APIs may be implemented using two approaches: - -- **Network API approach:** Each relevant Near-RT RIC endpoint exposes a network endpoint and specifies a particular data encoding protocol and a network transport protocol that should be used to communicate with it. A different network API may be specified for each Near-RT RIC API reflecting a trade-off between different service requirements. -- **SDK approach:** The Near-RT RIC vendor provides an SDK (software development kit). This SDK is a software library which handles all connection management and exposes a simple API for the xApp to interact with the Near-RT RIC. The interface between the SDK library embedded in the xApp and the Near-RT RIC Platform may be either vendor proprietary or aligned to the specified Network API. - -Both approaches use similar methodologies of interaction with Near-RT RIC as defined in clauses 6A and 9. Furthermore, the detailed messages and IEs for each Near-RT RIC API that the xApp will use largely stay the same in the two approaches. - -These two approaches are presented in figure 7.1.2-1 for the Network API approach and figure 7.1.2-2 for the SDK approach. - -Both approaches assume that the Near-RT RIC platform provides appropriate support services. These services, labelled “Network API support” and “SDK support” respectively in figures 7.1.2-1 and 7.1.2-2, may be integrated into other platform services (i.e., A1 Termination may provide the support services for A1 related APIs) or implemented as independent services. - -``` -@startuml -skin rose -card Near-RT-RIC { - - node xApp2 as "xApp" - node xApp1 as "xApp" - - frame Platform { - agent Netsup as "Network API support" - node Serv1 - node Serv2 - node Serv3 - } - -} - -xApp1 -- Netsup: "Network APIs" -xApp2 -- Netsup: "Network APIs" -Netsup -- Serv1 -Netsup -- Serv2 -Netsup -- Serv3 -@enduml -``` - -![UML diagram showing the Network API approach. The Near-RT-RIC contains two xApp nodes. The Platform contains a 'Network API support' node and three service nodes: Serv1, Serv2, and Serv3. Red lines connect the xApp nodes to the 'Network API support' node, labeled 'Network APIs'. Another red line connects the 'Network API support' node to each of the service nodes (Serv1, Serv2, Serv3).](392a79ccd95e682ccd08f35ab2e64144_img.jpg) - -``` - -graph TD - subgraph Near-RT-RIC - xApp1[xApp] - xApp2[xApp] - subgraph Platform - Netsup[Network API support] - Serv1[Serv1] - Serv2[Serv2] - Serv3[Serv3] - end - end - xApp1 -- "Network APIs" --- Netsup - xApp2 -- "Network APIs" --- Netsup - Netsup --- Serv1 - Netsup --- Serv2 - Netsup --- Serv3 - -``` - -UML diagram showing the Network API approach. The Near-RT-RIC contains two xApp nodes. The Platform contains a 'Network API support' node and three service nodes: Serv1, Serv2, and Serv3. Red lines connect the xApp nodes to the 'Network API support' node, labeled 'Network APIs'. Another red line connects the 'Network API support' node to each of the service nodes (Serv1, Serv2, Serv3). - -**Figure 7.1.2-1: Near-RT RIC platform supporting RIC APIs using Network API approach** - -``` -@startuml -skin rose -card Near-RT-RIC { - - frame xApp2 { -``` - -``` - -collections Logic2 as "Business Logic " -agent SDK2 as "SDK library" -} -frame xApp1 { - collections Logic1 as "Business Logic " - agent SDK1 as "SDK library" -} - -frame Platform { - agent SDKsup as "SDK support" - node Serv1 - node Serv2 - node Serv3 -} -} - -Logic1 -- SDK1: SDK APIs -Logic2 -- SDK2: SDK APIs -SDK1 -- SDKsup: "Not specified" -SDK2 -- SDKsup: "Not specified" -SDKsup -- Serv1 -SDKsup -- Serv2 -SDKsup -- Serv3 -@enduml - -``` - -![Diagram of Near-RT RIC architecture showing xApp1 and xApp2 connected to a Platform via SDK support.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) - -The diagram illustrates the Near-RT RIC architecture. At the top, a box labeled **Near-RT-RIC** contains two sub-boxes, **xApp1** and **xApp2**. Each xApp contains a **Business Logic** block connected to an **SDK library** block via a line labeled **SDK APIs**. Below the xApps is a **Platform** box. Inside the Platform, there is an **SDK support** block connected to three server blocks: **Serv1**, **Serv2**, and **Serv3**. Lines labeled **Not specified** connect the **SDK library** blocks from both xApp1 and xApp2 to the **SDK support** block in the Platform. The **SDK support** block is then connected to the three server blocks (Serv1, Serv2, Serv3). - -Diagram of Near-RT RIC architecture showing xApp1 and xApp2 connected to a Platform via SDK support. - -Figure 7.1.2-2: Near-RT RIC platform supporting RIC APIs using SDK approach - -### 7.1.3 Network API approach - -A Network API is defined in terms of a protocol stack including the definition of the following: - -- An application layer protocol used to carry a set of messages which normally contain multiple Information Elements (IEs); -- A data encoding protocol (ASN.1, Protobuf, JSON, etc.); -- A network transport protocol (SCTP, HTTPS, gRPC, etc.); -- Associated security and encryption methods. - -For the Network API approach for Near-RT RIC APIs, it is expected that each case listed in clause 7.1.1 may require a unique protocol stack definition which offers an optimal solution balancing the trade-offs between service requirements, Near-RT RIC platform complexity and xApp implementation overheads. - -Furthermore, each Network API will require a unique endpoint that the API consumer will need to discover using a combination of configuration and use of the Enablement APIs (also see clause 6A.2.6). - -Open O-RAN specified Network APIs for each case listed in clause 7.1.1 are defined in terms of the corresponding protocol stack. - -### 7.1.4 SDK approach - -An SDK (Software Development Kit) is defined as a set of software tools/libraries provided by platform vendors which helps developers in building applications on the platform. An SDK simplifies application development by: - -- Providing simple APIs to trigger commonly used functionality; -- Handling routine management tasks “under the hood”; -- Providing tools for debugging, building, testing applications. - -For the SDK approach for Near-RT RIC APIs, it is expected that a given Near-RT RIC vendor offers an SDK library that provides a language specific implementation of each case listed in clause 7.1.1. This provides a common interface to interact with all the Near-RT RIC endpoints as well as other xApps. - -The Near-RT RIC SDK library functionality would include: - -- Discovery of relevant endpoints for and connection to Near-RT RIC platform services and other xApps. -- Handles all connection management of the xApp with all relevant Near-RT RIC platform endpoints as well as other xApps. This includes: - - Authentication; - - Registration; - - Encryption/Decryption (if required); - - Failovers if any endpoint crashes. -- Presents a simple API as function definitions for sending/receiving messages; -- Provides tools for xApp debugging, building and testing. - -These services would be provided by the SDK library and so would not be exposed to the business logic within an xApp. - -Open O-RAN specified SDK APIs for each case listed in clause 7.1.1 would need to be defined for each supported programming language. - -The actual protocol stack implemented by the SDK library and used to communicate with the SDK support service in the Near-RT RIC platform may be either based on the Network APIs or left not specified and so may be vendor proprietary. - -### 7.1.5 Near-RT RIC API support options - -The two approaches to Near-RT RIC APIs are not necessarily mutually exclusive. - -For example, an xApp designed to support the Network API approach may be implemented using either an internal SDK library that provides the Network API interface or a direct implementation the Network API interface. Both of these cases are presented in figure 7.1.5-1. - -``` -@startuml -skin rose -card Near-RT-RIC { - - frame xApp2 { - collections Logic2 as "Business Logic " - agent IF2 as "Network API client" - } - frame xApp1 { - collections Logic1 as "Business Logic " - agent SDK1 as "SDK library \ninincluding Network API client" - } - frame Platform { - agent Netsup as "Network API support" - node Serv1 - node Serv2 - node Serv3 - } -} - -Logic1 -- SDK1: SDK APIs -Logic2 -- IF2 #line.dashed -SDK1 -- Netsup: "Network APIs" -IF2 -- Netsup: "Network APIs" -Netsup -- Serv1 -Netsup -- Serv2 -Netsup -- Serv3 -@enduml -``` - -![Diagram of Near-RT RIC platform architecture showing xApp1 and xApp2 interacting with a Platform via Network APIs. xApp1 uses Business Logic connected to an SDK library, which connects to the Platform's Network API support. xApp2 uses Business Logic connected to a Network API client, which also connects to the Platform's Network API support. The Platform contains Network API support and three services: Serv1, Serv2, and Serv3.](fa01531ea2c45beeb4036005da3037a4_img.jpg) - -``` - -graph TD - subgraph Near-RT-RIC - subgraph xApp1 - BL1[Business Logic] -- "SDK APIs" --> SDK1[SDK library including Network API client] - end - subgraph xApp2 - BL2[Business Logic] -.-> NAPI2[Network API client] - end - subgraph Platform - NAPI_Support[Network API support] - Serv1[Serv1] - Serv2[Serv2] - Serv3[Serv3] - NAPI_Support --- Serv1 - NAPI_Support --- Serv2 - NAPI_Support --- Serv3 - end - SDK1 -- "Network APIs" --> NAPI_Support - NAPI2 -- "Network APIs" --> NAPI_Support - end - -``` - -Diagram of Near-RT RIC platform architecture showing xApp1 and xApp2 interacting with a Platform via Network APIs. xApp1 uses Business Logic connected to an SDK library, which connects to the Platform's Network API support. xApp2 uses Business Logic connected to a Network API client, which also connects to the Platform's Network API support. The Platform contains Network API support and three services: Serv1, Serv2, and Serv3. - -**Figure 7.1.5-1: Near-RT RIC platform supporting RIC APIs using Network API approach with optional use of SDK APIs** - -Likewise, a Near-RT RIC Platform may be designed to support both the Network API approach and the SDK approach and so xApps implemented using either approach may access platform services. Both of these cases are presented in figure 7.1.5-2. - -``` - -@startuml -skin rose -card Near-RT-RIC { - - frame xApp2 { - collections Logic2 as "Business Logic" - agent SDK2 as "SDK library" - } - frame xApp1 { - collections Logic1 as "Business Logic" - agent SDK1 as "SDK library \ninclunding Network API client" - } - - frame Platform { - agent Netsup as "Network API support" - agent SDKsup as "SDK support" - node Serv1 - node Serv2 - node Serv3 - } -} - -``` - -``` - -} -} -Logic1 -- SDK1: SDK APIs -Logic2 -- SDK2: SDK APIs -SDK1 -- Netsup: "Network APIs" -SDK2 -- SDKsup: "Not specified" -Netsup -- Serv1 -Netsup -- Serv2 -Netsup -- Serv3 -SDKsup -- Serv1 -SDKsup -- Serv2 -SDKsup -- Serv3 -@enduml - -``` - -![Architecture diagram of Near-RT RIC showing two xApps (xApp1 and xApp2) connected to a Platform. xApp1 uses Business Logic connected to an SDK library with Network API client, which connects to Network API support on the Platform. xApp2 uses Business Logic connected to a standard SDK library, which connects to SDK support on the Platform. The Platform contains Network API support and SDK support, both of which connect to three servers: Serv1, Serv2, and Serv3.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) - -``` - -@startuml -package "Near-RT-RIC" { - package "xApp1" { - [Business Logic] as Logic1 - [SDK library\nincluding Network API client] as SDK1 - Logic1 -- SDK1 : SDK APIs - } - package "xApp2" { - [Business Logic] as Logic2 - [SDK library] as SDK2 - Logic2 -- SDK2 : SDK APIs - } - package "Platform" { - [Network API support] as Netsup - [SDK support] as SDKsup - node "Serv1" - node "Serv2" - node "Serv3" - Netsup -- Serv1 - Netsup -- Serv2 - Netsup -- Serv3 - SDKsup -- Serv1 - SDKsup -- Serv2 - SDKsup -- Serv3 - } - SDK1 -- Netsup : Network APIs - SDK2 -- SDKsup : Not specified -} -@enduml - -``` - -Architecture diagram of Near-RT RIC showing two xApps (xApp1 and xApp2) connected to a Platform. xApp1 uses Business Logic connected to an SDK library with Network API client, which connects to Network API support on the Platform. xApp2 uses Business Logic connected to a standard SDK library, which connects to SDK support on the Platform. The Platform contains Network API support and SDK support, both of which connect to three servers: Serv1, Serv2, and Serv3. - -Figure 7.1.5-2: Near-RT RIC platform supporting both Network API and SDK approaches - -7.2 Void - -7.3 Void - -7.4 Void - -7.5 Void - -7.6 Void - -7.7 Void - -# --- 8 External Interfaces of Near-RT RIC - -## 8.1 E2 Interface - -O-RAN.WG3.TS.E2GAP [2] specifies E2 interface general aspects and principles. - -O-RAN.WG3.TS.E2AP [3] specifies E2 interface application protocols. - -## 8.2 A1 Interface - -O-RAN.WG2.TS.A1.GAP [8] specifies A1 interface general aspects and principles. - -O-RAN.WG2.TS.A1AP [9] specifies A1 interface application protocols. - -## 8.3 O1 Interface - -An implementation of O1 interface at Near-RT RIC depends on the deployment options described in [4], i.e., when Near-RT RIC is modelled as a stand-alone Managed Element. - -O-RAN.WG10.TS.O1-Interface [5] specifies O1 interface related aspects. - -## 8.4 Y1 Interface - -Y1 interface allows the Y1 consumers to subscribe to or request the RAN analytics information service(s) provided by Near-RT RIC [23][24]. - -# --- 9 Near-RT RIC API Procedures - -## 9.1 General - -Procedures described in this clause assume the Near-RT RIC platform contains the functionalities listed in clause 6.2. API endpoints associated with the platform functionalities may vary depending on implementation. - -## 9.1A Conventions for procedure description - -The following notations are used to describe the procedure elements in the present document: - -- M: mandatory – the capability is required to be supported; -- O: optional – the capability may be supported or not. - -## 9.2 A1 Related API Procedures - -### 9.2.1 Introduction - -The following procedures are described in this clause: - -#### 1) Policy Management Service. - -In this case the A1 Service Producer role (A1AP [9] clause 3.1) resides in the Near-RT RIC. - -a) Non-RT RIC (A1 Service Consumer) originated procedures: - -- Create Single Policy procedure (A1AP [9] clause 3.2.2.2.2) using **A1 Related API: A1 Policy Setup** (request, result); -- Query Single Policy procedure (A1AP [9] clause 3.2.2.3.2) using **A1 Related API: A1 Policy Query** (request, result); -- Query All Policy Identifiers procedure (A1AP [9] clause 3.2.2.3.5) using **A1 Related API: A1 Policy Query** (request, result); -- Query Policy Status procedure (A1AP [9] clause 3.2.2.3.6) using **A1 Related API: A1 Policy Query** (request, result); -- Update Single Policy procedure (A1AP [9] clause 3.2.2.4.2) using **A1 Related API: A1 Policy Update** (request, result); -- Delete Single Policy procedure (A1AP [9] clause 3.2.2.5.2) using **A1 Related API: A1 Policy Delete** (request, result); -- Query All Policy Type Identifiers procedure (A1AP [9] clause 3.2.2.7.2) using **A1 Related API: A1 Policy Query** (request, result); -- Query Single Policy Type procedure (A1AP [9] clause 3.2.2.7.3) using **A1 Related API: A1 Policy Query** (request, result). - -b) Near-RT RIC (A1 Service Producer) originated procedures: - -- Policy Status Update procedure (A1AP [9] clause 3.2.2.6.2) using **A1 Related API: A1 Policy Status** (status, ack). - -#### 2) A1AP Enrichment Information (EI) Service - -In this case the A1 Service Producer role (A1AP [9] clause 3.1) resides in the Non-RT RIC. - -a) Near-RT RIC (A1 Service Consumer) originated procedures: - -- Query EI Type Identifiers procedure (A1AP [9] clause 3.3.2.2.2) using **A1 Related API: A1 EI Query** (request, result); -- Query EI Type procedure (A1AP [9] clause 3.3.2.2.3) using **A1 Related API: A1 EI Query** (request, result); -- Query EI Job Identifiers procedure (A1AP [9] clause 3.3.2.2) using **A1 Related API: A1 EI Query** (request, result); - -- Create EI Job procedure (A1AP [9] clause 3.3.3.3.2) using **A1 Related API: A1 EI Job Setup** (request, result); -- Query EI Job procedure (A1AP [9] clause 3.3.3.3.3) using **A1 Related API: A1 EI Query** (request, result); -- Update EI Job procedure (A1AP [9] clause 3.3.3.3.4) using **A1 Related API: A1 EI Job Update** (request, result); -- Delete EI Job procedure (A1AP [9] clause 3.3.3.3.5) using **A1 Related API: A1 EI Job Delete** (request, result); -- Query EI Job Status procedure (A1AP [9] clause 3.3.3.4.2) using **A1 Related API: A1 EI Job Status Query** (request, result). - -b) Non-RT RIC (A1 Service Producer) originated procedures: - -- Notify EI Job Status procedure (A1AP [9] clause 3.3.3.4.3) using **A1 Related API: A1 EI Job Status Notify** (status, ack); -- Deliver EI Job Result procedure (A1AP [9] clause 3.3.4.2.2) using **A1 Related API: A1 EI Job Result Delivery** (result, ack). - -### 9.2.2 A1 Policy procedures - -#### 9.2.2.1 A1 Policy Setup procedure - -The purpose of A1 Policy Setup procedure in Near-RT RIC is to support the A1AP [9] Create Single Policy procedure from the Non-RT RIC and to request and activate an A1 policy enforcement toward a suitable xApp. - -| Use Case Stage | Evolution / Specification | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | The activation of a received but not activated A1 policy in Near-RT RIC. | -| Actors and Roles |
  • Non-RT RIC: originator of HTTP PUT request to activate an A1 policy;
  • xApp: responsible for the enforcement of assigned A1 policies;
  • Near-RT RIC platform, with the following functionalities:
    • – A1 Termination;
    • – xApp Repository.
| -| Assumptions |
  • A1 policy types supported in Near-RT RIC are accessible by the Near-RT RIC platform;
  • A1 policies created in Near-RT RIC are accessible by the Near-RT RIC platform;
  • xApp selection needed information is accessible by the Near-RT RIC platform. xApp selection process is performed in the Near-RT RIC platform.
| -| Pre conditions |
  • Near-RT RIC is running normally;
  • A1 interface is connected and activated.
| -| Begins when | Non-RT RIC determines to trigger the activation of one A1 policy towards the Near-RT RIC. | -| Step 1 (M) | Non-RT RIC requests Near-RT RIC to set up an A1 policy. | -| Step 2 (M) | Near-RT RIC platform checks whether the received policy type is supported in Near-RT RIC or not. | -| | [ALT] Step 3 is executed if the received policy type is not supported in Near-RT RIC: | -| Step 3 (M) | A “400” response is directly returned to Non-RT RIC. | -| | [ELSE] Steps 4-11 are executed if the received policy type is supported in Near-RT RIC: | -| Step 4 (M) | Near-RT RIC platform then checks whether the received A1 policy has been mapped to any xApp or not. If not, Near-RT RIC platform tries to identify suitable xApp(s). (NOTE 1) | -| Step 5 (M) | Near-RT RIC platform selects suitable xApp(s). | -| | [ALT] Steps 6-10 are executed if one or more suitable xApps are identified: | -| Step 6 (M) | Near-RT RIC platform selects a suitable xApp as the target of A1 related API: A1 POLICY SETUP REQUEST message. The message includes at least the corresponding A1 policy received from Non-RT RIC. | -| | [ALT] Steps 7-8 are executed if the selected xApp accomplishes setup of the A1 policy: | -| Step 7-8 (M) | A success is notified to Near-RT RIC platform in A1 related API: A1 POLICY SETUP RESULT message, and eventually to Non-RT RIC. | -| | [ELSE] Steps 9-10 are executed if the selected xApp fails to set up the A1 policy: | -| Step 9-10 (M) | A failure is notified to Near-RT RIC platform in A1 related API: A1 POLICY SETUP RESULT message, and eventually to Non-RT RIC. | - -| | | -|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| -| | [ELSE] Step 11 is executed if no suitable xApp is identified: | -| Step 11 (M) | A “503” response is directly returned to Non-RT RIC. | -| NOTE 1: The create policy and update policy procedure in A1 interface has the identical HTTP PUT Request, so when a HTTP PUT Request is received, Near-RT RIC platform cannot decide whether it's asked for create or update from a first glance. Only after further A1 policy mapping check to find out the enforcement status of the received A1 policy, can the purpose of the received HTTP PUT request be identified. If the received A1 policy is not mapped to any xApp, Near-RT RIC platform triggers A1 Policy Setup procedure as shown here. Otherwise, Near-RT RIC platform triggers A1 Policy Update procedure. See 9.2.2.2 for details. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Participant Non as "Non-RT RIC" - -Box "Near-RT RIC" - Participant plt as "Near-RT RIC platform" - Participant xApp -End box - -autonumber -Non -> plt:<>PUT ../policytypes/{policyTypeId}/policies/{policyId}(PolicyObject) -plt <-plt: Policy type check - -alt policy type is not supported in Near-RT RIC - plt -> Non: <>400 -else policy type is supported in Near-RT RIC - plt -> plt: Policy mapping check - - plt ->plt: xApp selection process - - alt suitable xApp is identified - - plt -> xApp: A1 POLICY SETUP REQUEST - - alt success - xApp -> plt: A1 POLICY SETUP RESULT\n[success] - plt -> Non:<>201 Created (PolicyObject) - else failure - xApp -> plt: A1 POLICY SETUP RESULT \n[failure, reason] - plt -> Non:<>error code xxx - end - - else no suitable xApp is identified - - plt -> Non:<>503 - end - -end - -... -@enduml - -``` - -![Sequence diagram for A1 Policy Setup procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, and xApp. The process involves a PUT request from Non-RT RIC to Near-RT RIC platform, followed by internal checks (policy type, mapping, xApp selection). An 'alt' block 'policy type is not supported in Near-RT RIC' returns a 400 error. Another 'alt' block 'policy type is supported in Near-RT RIC' leads to an 'A1 POLICY SETUP REQUEST' to xApp. Inside this, an 'alt' block '[suitable xApp is identified]' contains a '[success]' path returning a 201 Created response and a '[failure]' path returning an error code. If no suitable xApp is identified, a 503 response is returned to the Non-RT RIC.](1142ba0197b158bb198186fe8baccc32_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC platform - participant xApp - - Note right of Near-RT RIC platform: Near-RT RIC - Note left of xApp: xApp - - Non-RT RIC->>Near-RT RIC platform: 1 <>PUT .../policytypes/{policyTypeId}/policies/{policyId}(PolicyObject) - Near-RT RIC platform->>Near-RT RIC platform: 2 Policy type check - - alt policy type is not supported in Near-RT RIC - Near-RT RIC platform-->>Non-RT RIC: 3 <>400 - else policy type is supported in Near-RT RIC - Near-RT RIC platform->>Near-RT RIC platform: 4 Policy mapping check - Near-RT RIC platform->>Near-RT RIC platform: 5 xApp selection process - - alt suitable xApp is identified - Near-RT RIC platform->>xApp: 6 A1 POLICY SETUP REQUEST - - alt success - xApp-->>Near-RT RIC platform: 7 A1 POLICY SETUP RESULT [success] - Near-RT RIC platform-->>Non-RT RIC: 8 <>201 Created(PolicyObject) - else failure - xApp-->>Near-RT RIC platform: 9 A1 POLICY SETUP RESULT [failure, reason] - Near-RT RIC platform-->>Non-RT RIC: 10 <>error code xxx - end - else no suitable xApp is identified - Near-RT RIC platform-->>Non-RT RIC: 11 <>503 - end - end - -``` - -Sequence diagram for A1 Policy Setup procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, and xApp. The process involves a PUT request from Non-RT RIC to Near-RT RIC platform, followed by internal checks (policy type, mapping, xApp selection). An 'alt' block 'policy type is not supported in Near-RT RIC' returns a 400 error. Another 'alt' block 'policy type is supported in Near-RT RIC' leads to an 'A1 POLICY SETUP REQUEST' to xApp. Inside this, an 'alt' block '[suitable xApp is identified]' contains a '[success]' path returning a 201 Created response and a '[failure]' path returning an error code. If no suitable xApp is identified, a 503 response is returned to the Non-RT RIC. - -Figure 9.2.2.1-1: A1 Policy Setup procedure - -#### 9.2.2.2 A1 Policy Update procedure - -The purpose of A1 Policy Update procedure in Near-RT RIC is to support A1AP Update Single Policy procedure from Non-RT RIC. - -| Use Case Stage | Evolution / Specification | -|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | The update of a received and already activated A1 policy in Near-RT RIC. | -| Actors and Roles |
  • Non-RT RIC: originator of HTTP PUT request to update an A1 policy;
  • xApp: responsible for the enforcement of assigned A1 policies;
  • Near-RT RIC platform, with the following functionalities:
    • A1 Termination.
| -| Assumptions |
  • A1 policy types supported in Near-RT RIC are accessible by the Near-RT RIC platform;
  • A1 policies created in Near-RT RIC are accessible by the Near-RT RIC platform.
| -| Pre conditions |
  • Near-RT RIC is running normally;
  • A1 interface is connected and activated.
| -| Begins when | Non-RT RIC determines to trigger the update of one A1 policy towards the Near-RT RIC. | -| Step 1 (M) | Non-RT RIC requests Near-RT RIC to update an A1 policy. | -| Step 2 (M) | Near-RT RIC platform checks whether the received policy type is supported in Near-RT RIC or not. | -| | [ALT] Step 3 is executed if the received A1 policy type is not supported in Near-RT RIC: | -| Step 3 (M) | A “400” response is directly returned to Non-RT RIC. | -| | [ELSE] Steps 4-9 are executed if the received policy type is supported in Near-RT RIC: | -| Step 4 (M) | Near-RT RIC platform then checks whether the received A1 policy is mapped to any xApp or not. | -| Step 5 (M) | (NOTE 1) If the received A1 policy is already mapped to one xApp, Near-RT RIC platform selects the xApp as the target of A1 related API: A1 POLICY UPDATE REQUEST message. The message includes at least the corresponding A1 policy received from Non-RT RIC. | -| | [ALT] Steps 6-7 are executed if the target xApp accomplishes update of the A1 policy: | -| Step 6-7 (M) | A success is notified to Near-RT RIC platform in A1 related API: A1 POLICY UPDATE RESULT message, and eventually to Non-RT RIC. | -| | [ELSE] Steps 8-9 are executed if the target xApp fails to update the A1 policy: | -| Step 8-9 (M) | A failure is notified to Near-RT RIC platform in A1 related API: A1 POLICY UPDATE RESULT message, and eventually to Non-RT RIC. | -| NOTE 1: The create policy and update policy procedure in A1 interface has the identical HTTP PUT Request, so when a HTTP PUT Request is received, Near-RT RIC platform cannot decide whether it's asked for create or update from a first glance. Only after further A1 policy mapping check to find out the enforcement status of the received A1 policy, can the purpose of the received HTTP PUT request be identified. If the received A1 policy is already mapped to an xApp, Near-RT RIC platform triggers A1 Policy Update procedure as shown here. Otherwise, Near-RT RIC platform triggers A1 Policy Setup procedure. See 9.2.2.1 for details. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 3 -skinparam BoxPadding 6 -skinparam defaultFontSize 12 - -Participant Non as "Non-RT RIC" -box "Near-RT RIC" - Participant plt as "Near-RT RIC platform" - Participant xApp -end box - -autonumber -Non -> plt: <>PUT ../policytypes/{policyTypeId}/policies/{policyId} (PolicyObject) -plt <-plt: Policy type check -alt policy type is not supported in Near-RT RIC - plt -> Non:<>400 -else policy type is supported in Near-RT RIC - plt -> plt: Policy mapping check - plt -> xApp: A1 POLICY UPDATE REQUEST - - alt success - xApp -> plt: A1 POLICY UPDATE RESULT\n[success] - plt -> Non: <>200 OK(PolicyObject) - else failure - -``` - -``` - -xApp -> plt: A1 POLICY UPDATE RESULT\n[failure, reason] -plt -> Non: <>error code xxx -end - -end -... -@enduml - -``` - -![Sequence diagram for A1 Policy Update procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, xApp. The process involves a PUT request from Non-RT RIC to Near-RT RIC platform, followed by internal checks (policy type and mapping). An 'alt' block for policy type support handles the case where the type is not supported (returning 400) versus when it is supported (proceeding to mapping check). Another 'alt' block for success/failure handles the final result from the xApp, returning either a 200 OK or an error code to the Non-RT RIC.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC platform - participant xApp - - Note right of Near-RT RIC platform: Near-RT RIC - Note left of xApp: xApp - - Non-RT RIC->>Near-RT RIC platform: 1 <>PUT .../policytypes/{policyTypeId}/policies/{policyId}(PolicyObject) - Near-RT RIC platform->>Near-RT RIC platform: 2 Policy type check - - alt policy type is not supported in Near-RT RIC - Near-RT RIC platform->>Non-RT RIC: 3 <>400 - else policy type is supported in Near-RT RIC - Near-RT RIC platform->>Near-RT RIC platform: 4 Policy mapping check - Near-RT RIC platform->>xApp: 5 A1 POLICY UPDATE REQUEST - - alt success - xApp->>Near-RT RIC platform: 6 A1 POLICY UPDATE RESULT [success] - Near-RT RIC platform->>Non-RT RIC: 7 <>200 OK(PolicyObject) - else failure - xApp->>Near-RT RIC platform: 8 A1 POLICY UPDATE RESULT [failure, reason] - Near-RT RIC platform->>Non-RT RIC: 9 <>error code xxx - end - end - -``` - -Sequence diagram for A1 Policy Update procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, xApp. The process involves a PUT request from Non-RT RIC to Near-RT RIC platform, followed by internal checks (policy type and mapping). An 'alt' block for policy type support handles the case where the type is not supported (returning 400) versus when it is supported (proceeding to mapping check). Another 'alt' block for success/failure handles the final result from the xApp, returning either a 200 OK or an error code to the Non-RT RIC. - -Figure 9.2.2.2-1: A1 Policy Update procedure - -#### 9.2.2.3 A1 Policy Delete procedure - -The purpose of A1 Policy Delete procedure is to support the A1AP Delete Policy procedure from Non-RT RIC. - -| Use Case Stage | Evolution / Specification | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | The deactivation of a received and already activated A1 policy in Near-RT RIC. | -| Actors and Roles |
  • Non-RT RIC: originator of HTTP DELETE request to deactivate an A1 policy;
  • xApp: responsible for the deactivation of created A1 policies;
  • Near-RT RIC platform, with the following functionalities:
    • A1 Termination.
| -| Assumptions |
  • A1 policy types supported in Near-RT RIC are accessible by Near-RT RIC platform;
  • A1 policies created in Near-RT RIC are accessible by Near-RT RIC platform.
| -| Pre conditions |
  • Near-RT RIC is running normally.
  • A1 interface is connected and activated.
| -| Begins when | Non-RT RIC determines to trigger the deactivation of one A1 policy towards the Near-RT RIC. | -| Step 1 (M) | Non-RT RIC requests Near-RT RIC to delete an A1 policy. | -| Step 2 (M) | Near-RT RIC platform checks whether the received policy type is supported in Near-RT RIC or not. | -| | [ALT] Step 3 is executed if the received policy type is not supported in Near-RT RIC: | -| Step 3 (M) | A “400” response is directly returned to Non-RT RIC. | -| | [ELSE] Steps 4-10 are executed if the received policy type is supported in Near-RT RIC: | -| Step 4 (M) | Near-RT RIC platform then checks whether the received A1 policy is mapped to any xApp or not. | -| | [ALT] Steps 5-9 are executed if the received A1 policy is already mapped to one xApp: | -| Step 5 (M) | Near-RT RIC platform selects the xApp as the target of A1 related API: A1 POLICY DELETE REQUEST message. The message includes at least the corresponding A1 policy ID received from Non-RT RIC. | -| | [ALT] Steps 6-7 are executed if the target xApp accomplishes deletion of the A1 policy: | -| Step 6-7 (M) | A success is notified to Near-RT RIC platform in A1 related API: A1 POLICY DELETE RESULT message, and eventually to Non-RT RIC. | -| | [ELSE] Steps 8-9 are executed if the target xApp fails to delete the A1 policy: | -| Step 8-9 (M) | A failure is notified to Near-RT RIC platform in A1 related API: A1 POLICY DELETE RESULT message, and eventually to Non-RT RIC. | -| | [ELSE] Step 10 is executed if the received A1 policy is not mapped to any xApp: | -| Step 10 (M) | A “503” response is directly returned to Non-RT RIC. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 3 -skinparam BoxPadding 6 -skinparam defaultFontSize 12 - -Participant Non as "Non-RT RIC" -Box "Near-RT RIC" - Participant plt as "Near-RT RIC platform" - Participant xApp -End box - -autonumber -Non -> plt: <>DELETE .../policytypes/{policyTypeId}/policies/{policyId} -plt <-plt: Policy type check -alt policy type is not supported in Near-RT RIC - plt -> Non: <>400 -else policy type is supported in Near-RT RIC - plt -> plt: Policy mapping check - - alt policy mapped - plt -> xApp: A1 POLICY DELETE REQUEST - alt success - xApp -> plt: A1 POLICY DELETE RESULT\n[success] - plt -> Non: <>204 No content - else failure - xApp -> plt: A1 POLICY DELETE RESULT\n[failure, reason] - end - end - -``` - -``` - -plt -> Non:<>error code xxx -end - -else policy not mapped - plt -> Non: <>503 -end - -end -... -@enduml - -``` - -![Sequence diagram for A1 Policy Delete procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, xApp. The process involves a DELETE request, policy type check, policy mapping check, and a final result (success, failure, or not mapped).](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC platform - participant xApp - - Note right of Near-RT RIC platform: Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - - Non-RT RIC->>Near-RT RIC platform: 1 <>DELETE ../policytypes/{policyTypeId}/policies/{policyId} - Near-RT RIC platform->>Near-RT RIC platform: 2 Policy type check - - alt policy type is not supported in Near-RT RIC - Near-RT RIC platform-->>Non-RT RIC: 3 <>400 - else policy type is supported in Near-RT RIC - Near-RT RIC platform->>Near-RT RIC platform: 4 Policy mapping check - - alt policy mapped - Near-RT RIC platform->>xApp: 5 A1 POLICY DELETE REQUEST - - alt success - xApp-->>Near-RT RIC platform: 6 A1 POLICY DELETE RESULT [success] - Near-RT RIC platform-->>Non-RT RIC: 7 <>204 No content - else failure - xApp-->>Near-RT RIC platform: 8 A1 POLICY DELETE RESULT [failure, reason] - Near-RT RIC platform-->>Non-RT RIC: 9 <>error code xxx - end - else policy not mapped - Near-RT RIC platform-->>Non-RT RIC: 10 <>503 - end - end - -``` - -Sequence diagram for A1 Policy Delete procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, xApp. The process involves a DELETE request, policy type check, policy mapping check, and a final result (success, failure, or not mapped). - -Figure 9.2.2.3-1: A1 Policy Delete procedure - -#### 9.2.2.4 A1 Policy Query procedure - -The purpose of A1 Policy Query procedure is to support the following A1AP procedures initiated by the Non-RT RIC: - -- A1AP Query Single Policy procedure; -- A1AP Query All Policy Identifiers procedure; -- A1AP Query Policy Status procedure; - -- A1AP Query All Policy Type Identifiers procedure; -- A1AP Query Single Policy Type procedure. - -Table 9.2.2.4-1 provides the list of expected xApp response for each Near-RT RIC Platform Policy query. The query may come from Near-RT platform or from the Non-RT RIC. - -**Table 9.2.2.4-1: Supported A1AP Policy Query procedures** - -| Query procedure | Platform Request | xApp Response | -|-----------------------------------|-----------------------------|------------------------------------------| -| Query Single Policy | URI containing policyId | PolicyObject | -| Query All Policy Identifiers | URI containing policyTypeId | list of current policyId | -| Query Status | URI containing policyId | PolicyStatusObject | -| Query All Policy Type Identifiers | URI | list of currently supported PolicyTypeId | -| Query Single Policy Type | URI containing PolicyTypeId | PolicyTypeObject | - -| Use Case Stage | Evolution / Specification | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal |

To obtain from an xApp information concerning A1 Policies, outcome depends on nature of Request:

  • • Query Single Policy: xApp provides PolicyObject for a given policyId;
  • • Query All Policy Identifiers: xApp provides the list of current policyId for a given policyTypeId;
  • • Query Status: xApp provides current PolicyStatusObject for a given policyId;
  • • Query All Policy Type Identifiers: xApp provides list of currently supported PolicyTypeId;
  • • Query Single Policy Type: xApp provides PolicyTypeObject of a given PolicyTypeId.
| -| Actors and Roles |
  • • Non-RT RIC: originator of query using HTTP GET request;
  • • xApp: provides appropriate response corresponding to nature of request;
  • • Near-RT RIC platform, with the following functionalities:
    • – A1 Termination;
    • – xApp Repository.
| -| Assumptions |
  • • xApp selection needed information is accessible by Near-RT RIC platform. xApp selection process is performed at Near-RT RIC platform;
  • • Near-RT RIC platform may store the results of the xApp selection process
  • • Near-RT RIC platform may hold information related to Policy Query procedures.
| -| Pre conditions |
  • • Near-RT RIC is running normally;
  • • A1 interface is connected and activated.
| -| Begins when | Non-RT RIC determines need to trigger A1 query towards the Near-RT RIC. | -| Step 1 (M) | Non-RT RIC sends to Near-RT RIC one of the A1AP Policy Management service related Query procedures. | -| Step 2 (M) | Near-RT RIC platform inspects content of HTTP GET to determine nature of Query. | -| Step 3 (M) | Near-RT RIC platform selects suitable xApp(s) to collect information for the query. | -| | [LOOP] Steps 4-6 are looped for each xApp selected by Near-RT RIC platform | -| Step 4 (O) | Near-RT RIC platform may send A1 related API: A1 POLICY QUERY REQUEST message. The message includes at least the corresponding A1 policy management service query resource URI received from Non-RT RIC. | -| Step 5 (O) | If the selected xApp(s) accomplishes the A1 policy management service query, a success is notified to Near-RT RIC platform in A1 related API: A1 POLICY QUERY RESULT message. Near-RT RIC platform may store the result. | -| Step 6 (O) | If the selected xApp(s) fails to treat the A1 policy management service query, a failure is notified to Near-RT RIC platform in A1 related API: A1 POLICY QUERY RESULT message. | -| Step 7 (M) | Near-RT RIC platform collects the responses from each xApp and/or its previously stored information, and consolidates into a response to Non-RT RIC. | -| Step 8 (M) | If A1 policy query response available, Near-RT RIC platform sends the appropriate A1AP Policy Management Service response to Non-RT RIC. | -| Step 9 (M) | If A1 policy query response not available, Near-RT RIC platform sends the appropriate A1AP Policy Management Service error to Non-RT RIC (A1AP [9] clause 4.2.7.3). | -| Step 10 (O) | Depending upon the nature of the previous A1AP Policy Management Service query and the response from the Near-RT RIC, the Non-RT RIC may initiate a subsequent A1AP Policy Management Service query. | - -``` -@startuml -skin rose -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Participant Non as "Non-RT RIC" - -Box "Near-RT RIC" - Participant plt as "Near-RT RIC platform" - Collections xApp -End box - -autonumber -Non -> plt: <>GET (URI) -plt -> plt: Inspect URI to determine nature of query -plt -> plt: xApp selection process -loop For each xApp selected by Near-RT RIC platform - plt ->xApp: A1 POLICY QUERY REQUEST (URI) - alt Success - xApp -> plt: A1 POLICY QUERY RESULT\n[success, result] - plt --> plt: store query result - else Failure - xApp -> plt: A1 POLICY QUERY RESULT \n[failure, reason] - end -end -plt -> plt: Consolidate responses -alt Response available - plt -> Non: <> 200 OK (response) -else Response not available - plt ->Non: <>Error code -end -Non --> Non: Determine if subsequent query is required -@enduml -``` - -![Sequence diagram for A1 Policy Query procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, and xApp. The process involves a GET (URI) request from Non-RT RIC to Near-RT RIC platform, followed by internal processing (inspect URI, xApp selection), a loop for each selected xApp (A1 POLICY QUERY REQUEST), an alt block for Success (A1 POLICY QUERY RESULT, store result) or Failure (A1 POLICY QUERY RESULT, failure reason), response consolidation, and a final alt block for Response available (200 OK) or Response not available (Error code), ending with a determination of subsequent queries.](834fb96b114b8fdc001625e1ae28e8b1_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC platform - participant xApp - - Note right of Near-RT RIC platform: Near-RT RIC - Note left of Non-RT RIC: Non-RT RIC - - Note right of Near-RT RIC platform: Near-RT RIC platform - Note right of xApp: xApp - - Note right of Non-RT RIC: Non-RT RIC - Note right of Near-RT RIC platform: Near-RT RIC platform - Note right of xApp: xApp - - Non-RT RIC->>Near-RT RIC platform: 1 <>GET (URI) - Near-RT RIC platform->>Near-RT RIC platform: 2 Inspect URI to determine nature of query - Near-RT RIC platform->>Near-RT RIC platform: 3 xApp selection process - - loop For each xApp selected by Near-RT RIC platform - Near-RT RIC platform->>xApp: 4 A1 POLICY QUERY REQUEST (URI) - - alt Success - xApp->>Near-RT RIC platform: 5 A1 POLICY QUERY RESULT [success, result] - Near-RT RIC platform->>Near-RT RIC platform: 6 store query result - alt Failure - xApp->>Near-RT RIC platform: 7 A1 POLICY QUERY RESULT [failure, reason] - end - end - - Near-RT RIC platform->>Near-RT RIC platform: 8 Consolidate responses - - alt Response available - Near-RT RIC platform->>Non-RT RIC: 9 <> 200 OK (response) - alt Response not available - Near-RT RIC platform->>Non-RT RIC: 10 <>Error code - end - - Non-RT RIC->>Non-RT RIC: 11 Determine if subsequent query is required - -``` - -Sequence diagram for A1 Policy Query procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, and xApp. The process involves a GET (URI) request from Non-RT RIC to Near-RT RIC platform, followed by internal processing (inspect URI, xApp selection), a loop for each selected xApp (A1 POLICY QUERY REQUEST), an alt block for Success (A1 POLICY QUERY RESULT, store result) or Failure (A1 POLICY QUERY RESULT, failure reason), response consolidation, and a final alt block for Response available (200 OK) or Response not available (Error code), ending with a determination of subsequent queries. - -Figure 9.2.2.4-1: A1 Policy Query procedure - -#### 9.2.2.5 A1 Policy Status Update procedure - -The purpose of A1 Policy Status Update procedure in Near-RT RIC is to support the A1AP Policy Status Update procedure (A1AP [9] clause 3.2.2.6) from the Near-RT RIC. - -| Use Case Stage | Evolution / Specification | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | The activation of a received but not activated A1 policy in Near-RT RIC. | -| Actors and Roles |
  • Non-RT RIC: receives the HTTP POST containing PolicyStatusObject;
  • xApp: originator of the PolicyStatusObject content to be sent to Non-RT RIC;
  • Near-RT RIC platform, with the following functionalities:
    • A1 Termination.
| -| Assumptions |
  • A1 policy types supported in Near-RT RIC are accessible by Near-RT RIC platform;
  • A1 policies created in Near-RT RIC are accessible by Near-RT RIC platform;
  • xApp selection needed data is accessible by the Near-RT RIC platform. xApp selection process is performed at the Near-RT RIC platform.
| -| Pre conditions |
  • Near-RT RIC is running normally;
  • A1 interface is connected and activated.
| -| Begins when | xApp determines need to trigger the A1 policy status update to be sent to the Non-RT RIC. | -| Step 1 (M) | xApp sends A1 related API: A1 POLICY STATUS UPDATE (PolicyStatusObject information encoded as A1TD) message to Near-RT RIC platform. | -| | [ALT] Step 2 is executed if Near-RT RIC platform rejects request: | -| Step 2 (M) | Near-RT RIC platform sends A1 Related POLICY STATUS UPDATE (Error) to xApp. | -| | [ELSE] Step 3-5 are executed if Near-RT RIC platform accepts request: | -| Step 3 (M) | Near-RT RIC platform forwards content within A1AP Policy Status Update message. | -| Step 4-5 (M) | Non-RT RIC sends A1AP acknowledgement, and Near-RT RIC platform forwards to xApp using A1 Related POLICY STATUS UPDATE (Ack) . | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Participant Non as "Non-RT RIC" - -Box "Near-RT RIC" - Participant plt as "Near-RT RIC platform" - Collections xApp -End box - -autonumber -xApp -> plt: A1 POLICY STATUS UPDATE (PolicyStatusObject) -Alt If Near-RT RIC platform rejects message from xApp - plt --> xApp: A1 POLICY STATUS UPDATE (error) -Else IF Near-RT RIC platform accepts message from xApp - plt -> Non: <>POST (PolicyStatusObject) - Non -> plt: <> 204 (No content) - plt -> xApp: A1 POLICY STATUS UPDATE (Ack) -End -@enduml - -``` - -![Sequence diagram for A1 Policy Status Update procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, xApp. The process involves an A1 POLICY STATUS UPDATE message from xApp to platform, followed by an alt block 'If Near-RT RIC platform rejects message from xApp' containing an error response, and another alt block 'If Near-RT RIC platform accepts message from xApp' containing a POST to Non-RT RIC, a 204 response, and an Ack back to xApp.](60ffbad6c0fb7371a57fe8f267d2d141_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant platform as Near-RT RIC platform - participant NonRT RIC as Non-RT RIC - - Note right of platform: Near-RT RIC - xApp->>platform: 1 A1 POLICY STATUS UPDATE (PolicyStatusObject) - alt If Near-RT RIC platform rejects message from xApp - platform-->>xApp: 2 A1 POLICY STATUS UPDATE (error) - else If Near-RT RIC platform accepts message from xApp - platform->>NonRT RIC: 3 <>POST (PolicyStatusObject) - NonRT RIC-->>platform: 4 <> 204 (No content) - platform-->>xApp: 5 A1 POLICY STATUS UPDATE (Ack) - end - -``` - -Sequence diagram for A1 Policy Status Update procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, xApp. The process involves an A1 POLICY STATUS UPDATE message from xApp to platform, followed by an alt block 'If Near-RT RIC platform rejects message from xApp' containing an error response, and another alt block 'If Near-RT RIC platform accepts message from xApp' containing a POST to Non-RT RIC, a 204 response, and an Ack back to xApp. - -Figure 9.2.2.5-1: A1 Policy Status Update procedure - -### 9.2.3 A1-EI related procedures - -#### 9.2.3.1 A1-EI Query procedure - -The purpose of A1 EI Query procedure is to support the following A1AP procedures initiated by the Near-RT RIC: - -- Query EI Type Identifiers procedure; -- Query EI Type procedure; -- Query EI Job Identifiers procedure; -- Query EI Job procedure; -- Query EI Job Status procedure. - -Table 9.2.3.1-1 provides the expected response from Near-RT RIC platform for each EI query request. The information may come from the platform or the Non-RT RIC. - -Table 9.2.3.1-1: Supported A1AP Query EI procedures - -| Query procedure | xApp request | Platform Response | -|---------------------------|-------------------------|-------------------------| -| Query EI Type Identifiers | URI containing EiTypes | List of EiTypeId | -| Query EI Type | URI containing EiTypeId | List of EiTypeObject | -| Query EI Job Identifiers | URI containing EiJobs | List of current EiJobId | -| Query EI Job | URI containing EiJobId | EiJobObject | -| Query EI Job Status | URI containing EiJobId | EiJobStatusObjec | - -| Use Case Stage | Evolution / Specification | -|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | To obtain from Non-RT RIC information concerning A1 EI, outcome depends on nature of Request:
  • • Query EI Type Identifiers: Non-RT RIC provides list of EiTypeId for a given EiTypes;
  • • Query EI Type: Non-RT RIC provides EiTypeObject for a given EiTypeId;
  • • Query EI Job Identifiers: Non-RT RIC provides list of current EiJobId for a given EiJobs;
  • • Query EI Job: Non-RT RIC provides EiJobObject for a given EiJobId;
| - -| | | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |
  • Query EI Job Status: Non-RT RIC provides EiJobStatusObject for a given EiJobId with flag Status.
| -| Actors and Roles |
  • Non-RT RIC: provides appropriate response corresponding to nature of request;
  • xApp: originator of query using HTTP GET request;
  • Near-RT RIC platform, with the following functionalities:
    • – A1 Termination.
| -| Assumptions |
  • For A1-EI query, Near-RT RIC platform is stateless and so does not store previous Query responses from Non-RT RIC
| -| Pre conditions |
  • Near-RT RIC is running normally.
  • A1 interface is connected and activated.
| -| Begins when | xApp determines need to trigger A1 EI query towards the Non-RT RIC. | -| Step 1 (M) | xApp sends A1 Related EI QUERY REQUEST (URI) to Near-RT RIC platform. | -| | [ALT] Step 2 is executed if Near-RT RIC platform rejects the request: | -| Step 2 (O) | Near-RT RIC platform may reject request and send A1 Related EI QUERY RESULT (error code) to xApp. | -| | [ELSE] Steps 3-8 are executed if Near-RT RIC platform accepts the request: | -| Step 3 (M) | Near-RT RIC platform builds appropriate A1AP EI Query message including URI and sends to non-RT RIC. | -| Step 4 (M) | Non-RT RIC inspects URI to determine nature of query and it is acceptable. | -| | [ALT] Steps 5-6 are executed if Non-RT RIC accepts the query: | -| Step 5-6 (M) | Non-RT RIC builds appropriate response (EI information encoded using A1TD) and sends to Near-RT RIC platform, Near-RT RIC platform uses A1 Related EI QUERY RESULT to send response to xApp (with EI information encoded using A1TD). | -| | [ELSE] Steps 7-8 are executed if Non-RT RIC rejects the query: | -| Step 7-8 (M) | Non-RT RIC builds appropriate response (error code) and sends to Near-RT RIC platform, Near-RT RIC platform used A1 Related EI QUERY RESULT (error code) to send response to xApp. | -| Step 9 (O) | Depending upon the nature of the previous A1AP EI query and the response from the Non-RT RIC, the xApp may initiate a subsequent A1AP EI query. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Participant Non as "Non-RT RIC" - -Box "Near-RT RIC" - Participant plt as "Near-RT RIC platform" - Collections xApp -End box - -autonumber -xApp -> plt: A1 EI QUERY REQUEST (URI) -Alt EI query rejected by Near-RT RIC platform - plt -> xApp: A1 EI QUERY RESULT (error) -Else EI query accepted by Near-RT RIC platform - plt -> Non: <>GET (URI) - Non -> Non: Inspect URI to determine \nnature of query - alt EI query accepted - Non ->plt: <> 200 OK (EI information) - plt -> xApp: A1 EI QUERY RESULT (EI information) - else EI query rejected - Non -> plt: <>Error code - plt -> xApp: A1 EI QUERY RESULT (error) - end -end -xApp <-- xApp: Determine if subsequent \nquery is required -@enduml - -``` - -![Sequence diagram for A1 EI Query procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, xApp. The process involves an A1 EI QUERY REQUEST (URI) from xApp to platform, followed by an alt block '[EI query rejected by Near-RT RIC platform]'. If rejected, an A1 EI QUERY RESULT (error) is returned. If accepted, a GET (URI) is sent to Non-RT RIC, which inspects the URI. Another alt block '[EI query accepted]' follows. If accepted, a 200 OK (EI information) is returned to platform, which then returns an A1 EI QUERY RESULT (EI information) to xApp. If rejected, an Error code is returned to platform, which returns an A1 EI QUERY RESULT (error) to xApp. Finally, xApp determines if a subsequent query is required.](41aef1f5efab13d4f38f69e86c726062_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant platform as Near-RT RIC platform - participant NonRT RIC as Non-RT RIC - - Note right of platform: Near-RT RIC - xApp->>platform: 1 A1 EI QUERY REQUEST (URI) - alt EI query rejected by Near-RT RIC platform - platform-->>xApp: 2 A1 EI QUERY RESULT (error) - else EI query accepted by Near-RT RIC platform - platform-->>NonRT RIC: 3 <>GET (URI) - Note left of NonRT RIC: 4 Inspect URI to determine nature of query - alt EI query accepted - NonRT RIC-->>platform: 5 <> 200 OK (EI information) - platform-->>xApp: 6 A1 EI QUERY RESULT (EI information) - else EI query rejected - NonRT RIC-->>platform: 7 <>Error code - platform-->>xApp: 8 A1 EI QUERY RESULT (error) - end - end - Note right of xApp: 9 Determine if subsequent query is required - xApp-->>xApp: - -``` - -Sequence diagram for A1 EI Query procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, xApp. The process involves an A1 EI QUERY REQUEST (URI) from xApp to platform, followed by an alt block '[EI query rejected by Near-RT RIC platform]'. If rejected, an A1 EI QUERY RESULT (error) is returned. If accepted, a GET (URI) is sent to Non-RT RIC, which inspects the URI. Another alt block '[EI query accepted]' follows. If accepted, a 200 OK (EI information) is returned to platform, which then returns an A1 EI QUERY RESULT (EI information) to xApp. If rejected, an Error code is returned to platform, which returns an A1 EI QUERY RESULT (error) to xApp. Finally, xApp determines if a subsequent query is required. - -Figure 9.2.3.1-1: A1 EI Query procedure - -#### 9.2.3.2 A1-EI subscription setup procedure - -The A1-EI subscription setup procedure enables xApp to setup a new A1-EI subscription toward Near-RT RIC Platform. - -| Use Case Stage | Evolution / Specification | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | To setup a new A1-EI subscription between xApp and Near-RT RIC Platform. | -| Actors and Roles |
  • Non-RT RIC: A1-EI producer.
  • xApp: requester of A1-EI subscription setup.
  • Near-RT RIC Platform, with the following functionalities:
    • A1 Termination.
    • xApp Repository.
| -| Assumptions |
  • Created EiJobObjects in Near-RT RIC is readable by Near-RT RIC platform.
  • Non-RT RIC's supported A1-EIs record in Near-RT RIC is readable by Near-RT RIC platform.
  • xApp subscribe multiple A1-EIs in integrated manner, i.e., subscribed A1-EIs indicated by A1 related API: A1-EI SUBSCRIPTION SETUP REQUEST message are dependent on each other, and only full success of all A1-EI subscriptions is viewed as message process success.
  • xApp's access permission to A1-EI is handled by Near-RT RIC platform.
| -| Pre-conditions |
  • Near-RT RIC Platform is running normal.
  • Near-RT RIC is connected to Non-RT RIC via A1 interface.
| -| Begins when | xApp determines to request subscription of A1-EI(s). | -| Step 1 (M) | xApp requests Near-RT RIC Platform to set up an A1-EI subscription by sending A1 related API: A1-EI SUBSCRIPTION SETUP REQUEST message, with A1-EI subscription setup details included. | -| Step 2 (M) | Near-RT RIC platform checks whether the originating xApp is allowed to access all the requested A1-EI(s). | -| | [ALT] Step 3 is executed if the originating xApp is not allowed to access some of the requested A1-EIs. | -| Step 3 (M) | A failure is responded to the originating xApp via A1 related API: A1-EI SUBSCRIPTION SETUP RESULT message, possibly including appropriate reason. | -| | [ELSE] Steps 4-12 are executed if the originating xApp is allowed to access all the requested A1-EIs. | -| Step 4 (M) | Near-RT RIC platform checks whether all the requested A1-EIs is supported in Non-RT RIC. | -| | [ALT] Step 5 is executed if some of the requested A1-EI(s) is NOT supported in Non-RT RIC. | -| Step 5 (M) | A failure is responded to the originating xApp via A1 related API: A1-EI SUBSCRIPTION SETUP RESULT message, possibly including appropriate reason. | -| | [ELSE] Steps 6-12 are executed if all requested A1-EI(s) is supported in Non-RT RIC. | -| Step 6 (M) | Near-RT RIC platform checks whether created EiJobObject(s) satisfies the originating xApp's request. | -| | [ALT] Step 7 is executed if created EiJobObject(s) satisfies the originating xApp's request. | -| Step 7 (M) | Near-RT RIC platform associates the identified created EiJobObject with the originating xApp, and responds success to the originating xApp via A1 related API: A1-EI SUBSCRIPTION SETUP RESULT message. | -| | [ELSE] Steps 8-12 are executed if created EiJobObject(s) does not satisfy the originating xApp's request. | -| | [LOOP] Steps 8-10 are looped for each subscribed A1-EI that does not have EiJobObject association | -| Step 8 (M) | Near-RT RIC platform makes A1 interface EiJobObject either create or update decision. | -| | [ALT] Step 9 is executed if A1 interface EiJobObject create decision is made. | -| Step 9 (M) | Near-RT RIC platform initiates create EI job procedure towards Non-RT RIC and receives response from Non-RT RIC. | -| | [ELSE] Step 10 is executed if A1 interface EiJobObject update decision is made. | -| Step 10 (M) | Near-RT RIC platform initiates update EI job procedure towards Non-RT RIC and receives response from Non-RT RIC. | -| | [ALT] Step 11 is executed if A1 interface EiJobObject create/update process shots full success. | -| Step 11 (M) | Near-RT RIC platform responds success to the originating xApp via A1 related API: A1-EI SUBSCRIPTION SETUP RESULT message. | -| | [ELSE] Step 12 is executed if A1 interface EiJobObject create/update process shots not full success. | - -| | | -|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Step 12 (M) | Near-RT RIC platform responds failure to the originating xApp via A1 related API: A1-EI SUBSCRIPTION SETUP RESULT message, possibly including appropriate reason. | -|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| - -``` - -@startuml -skin rose -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Participant Non as "Non-RT RIC" - -Box "Near-RT RIC" - Participant plt as "Near-RT RIC platform" - Participant xApp -End box - -autonumber -xApp -> plt: A1-EI SUBSCRIPTION SETUP REQUEST\n[A1-EI Subscription ID, A1-EI Subscription -Setup Details] -plt <-> plt: Check the originating xApp's\naccess permission to requested A1-EI(s) - -alt The originating xApp is NOT allowed to access some of requested A1-EI(s) - plt -> xApp: A1-EI SUBSCRIPTION SETUP RESULT [Result{failure}, Reason] - -else The originating xApp is allowed to access all requested A1-EI(s) - plt -> plt: Checks for A1-EI(s) support in Non-RT RIC - alt Some of requested A1-EI(s) is NOT supported in Non-RT RIC - plt -> xApp: A1-EI SUBSCRIPTION SETUP RESULT [Result{failure}, Reason] - else All requested A1-EI(s) is supported in Non-RT RIC - plt -> plt: Checks created EiJobObject(s) against\nthe originating xApp's request - alt Created EiJobObject(s) satisfies the originating xApp's request - plt -> xApp: A1-EI SUBSCRIPTION SETUP RESULT [Result{success}] - else Created EiJobObject(s) does not satisfy the originating xApp's request - - loop for each requested A1-EI does not have created EiJobObject association - plt -> plt: A1 interface EiJobObject\ncreate/update decide process - alt A1 interface EiJobObject create decision is made - plt <-> Non: Create EI job procedure - else A1 interface EiJobObject update decision is made - plt <-> Non: Update EI job procedure - end - end loop - - alt EiJobObject(s) create/update full success - plt -> xApp: A1-EI SUBSCRIPTION SETUP RESULT [Result{success}] - else EiJobObject(s) create/update NOT full success - plt -> xApp: A1-EI SUBSCRIPTION SETUP RESULT [Result{failure}, Reason] - end - end - end -end -... -@enduml - -``` - -![Sequence diagram for A1-EI subscription setup procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, xApp. The process involves a subscription request, permission check, support check, EiJobObject creation/update, and final result reporting with nested alt and loop blocks.](8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - participant Non-RT RIC - - Note right of Near-RT RIC platform: Near-RT RIC - - xApp->>Near-RT RIC platform: 1 A1-EI SUBSCRIPTION SETUP REQUEST [A1-EI Subscription ID, A1-EI Subscription Setup Details] - Near-RT RIC platform->>Near-RT RIC platform: 2 Check the originating xApp's access permission to requested A1-EI(s) - - alt The originating xApp is NOT allowed to access some of requested A1-EI(s) - Near-RT RIC platform->>xApp: 3 A1-EI SUBSCRIPTION SETUP RESULT [Result{failure}, Reason] - else The originating xApp is allowed to access all requested A1-EI(s) - Near-RT RIC platform->>Near-RT RIC platform: 4 Checks for A1-EI(s) support in Non-RT RIC - - alt Some of requested A1-EI(s) is NOT supported in Non-RT RIC - Near-RT RIC platform->>xApp: 5 A1-EI SUBSCRIPTION SETUP RESULT [Result{failure}, Reason] - else All requested A1-EI(s) is supported in Non-RT RIC - Near-RT RIC platform->>Near-RT RIC platform: 6 Checks created EiJobObject(s) against the originating xApp's request - - alt Created EiJobObject(s) satisfies the originating xApp's request - Near-RT RIC platform->>xApp: 7 A1-EI SUBSCRIPTION SETUP RESULT [Result{success}] - else Created EiJobObject(s) does not satisfy the originating xApp's request - loop for each requested A1-EI does not have created EiJobObject association - Near-RT RIC platform->>Near-RT RIC platform: 8 A1 interface EiJobObject create/update decide process - - alt A1 interface EiJobObject create decision is made - Near-RT RIC platform->>Non-RT RIC: 9 Create EI job procedure - else A1 interface EiJobObject update decision is made - Near-RT RIC platform->>Non-RT RIC: 10 Update EI job procedure - end - - alt EiJobObject(s) create/update full success - Near-RT RIC platform->>xApp: 11 A1-EI SUBSCRIPTION SETUP RESULT [Result{success}] - else EiJobObject(s) create/update NOT full success - Near-RT RIC platform->>xApp: 12 A1-EI SUBSCRIPTION SETUP RESULT [Result{failure}, Reason] - end - end - end - end - end - -``` - -Sequence diagram for A1-EI subscription setup procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, xApp. The process involves a subscription request, permission check, support check, EiJobObject creation/update, and final result reporting with nested alt and loop blocks. - -Figure 9.2.3.2-1: A1-EI subscription setup procedure - -#### 9.2.3.3 A1-EI subscription update procedure - -The A1-EI subscription update procedure enables xApp to update an existing A1-EI subscription toward Near-RT RIC Platform. - -| Use Case Stage | Evolution / Specification | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | To update an existing A1-EI subscription between xApp and Near-RT RIC Platform. | -| Actors and Roles |
  • Non-RT RIC: A1-EI producer.
  • xApp: requester of A1-EI subscription update.
  • Near-RT RIC Platform, with the following functionalities:
    • A1 Termination.
    • xApp Repository.
| -| Assumptions |
  • Created EiJobObjects in Near-RT RIC is readable by Near-RT RIC platform.
  • Non-RT RIC's supported A1-EIs record in Near-RT RIC is readable by Near-RT RIC platform.
  • xApp subscribe multiple A1-EIs in integrated manner, i.e., subscribed A1-EIs indicated by A1 related API: A1-EI SUBSCRIPTION SETUP REQUEST message are dependent on each other, and only full success of all A1-EI subscriptions is viewed as message process success.
  • xApp's access permission to A1-EI is handled by Near-RT RIC platform.
| -| Pre-conditions |
  • Near-RT RIC Platform is running normal.
  • Near-RT RIC is connected to Non-RT RIC via A1 interface.
| -| Begins when | xApp determines to request update of one A1-EI subscription. | -| Step 1 (M) | xApp requests Near-RT RIC Platform to update an A1-EI subscription by sending A1 related API: A1-EI SUBSCRIPTION UPDATE REQUEST message, with A1-EI subscription update details included. | -| Step 2 (M) | From A1 related API: A1-EI SUBSCRIPTION UPDATE REQUEST message, Near-RT RIC platform filters A1-EI(s) requested for 1) unsubscribing, and 2) subscribing (including new subscription needs creation and current subscription needs update). | -| Step 3 (M) | For A1-EI(s) requested for unsubscribing, execute steps 3-6. | -| Step 4 (M) | [LOOP] Steps 4-6 are looped for each requested A1-EI
Near-RT RIC platform makes A1 interface EiJobObject either delete or update decision. | -| Step 5 (M) | [ALT] Step 5 is executed if A1 interface EiJobObject delete decision is made.
Near-RT RIC platform initiates delete EI job procedure towards Non-RT RIC and receives response from Non-RT RIC. | -| Step 6 (M) | [ELSE] Step 6 is executed if A1 interface EiJobObject update decision is made.
Near-RT RIC platform initiates update EI job procedure towards Non-RT RIC and receives response from Non-RT RIC. | -| Step 7 (M) | For A1-EI(s) requested for subscribing, execute steps 7-17.
Near-RT RIC platform checks whether the originating xApp is allowed to access to the requested A1-EI(s). | -| Step 8 (M) | [ALT] Step 8 is executed if the originating xApp is not allowed to access some of the requested A1-EI(s).
A failure is responded to the originating xApp via A1 related API: A1-EI SUBSCRIPTION UPDATE RESULT message, possibly including appropriate reason. | -| Step 9 (M) | [ELSE] Steps 9-17 are executed if the originating xApp is allowed to access all the requested A1-EI(s).
Near-RT RIC platform checks whether the requested A1-EI(s) is supported in Non-RT RIC. | -| Step 10 (M) | [ALT] Step 10 is executed if some of requested A1-EI(s) is NOT supported in Non-RT RIC.
A failure is responded to the originating xApp via A1 related API: A1-EI SUBSCRIPTION UPDATE RESULT message, possibly including appropriate reason. | -| Step 11 (M) | [ELSE] Steps 11-17 are executed if all requested A1-EI(s) is supported in Non-RT RIC.
Near-RT RIC platform checks whether created EiJobObject(s) satisfies the originating xApp's request. | -| Step 12 (M) | [ALT] Step 12 is executed if created EiJobObject(s) satisfies the originating xApp's request.
Near-RT RIC platform associates the identified created EiJobObject with the originating xApp, and responds success to the originating xApp via A1 related API: A1-EI SUBSCRIPTION UPDATE RESULT message. | -| | [ELSE] Steps 13-17 are executed if created EiJobObject(s) does not satisfy the originating xApp's request. | - -| | | -|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | [LOOP] Steps 13-15 are looped for each requested A1-EI that does not have EiJobObject association | -| Step 13 (M) | Near-RT RIC platform makes A1 interface EiJobObject either create or update decision. | -| | [ALT] Step 14 is executed if A1 interface EiJobObject create decision is made. | -| Step 14 (M) | Near-RT RIC platform initiates create EI job procedure towards Non-RT RIC and receives response from Non-RT RIC. | -| | [ELSE] Step 15 is executed if A1 interface EiJobObject update decision is made. | -| Step 15 (M) | Near-RT RIC platform initiates update EI job procedure towards Non-RT RIC and receives response from Non-RT RIC. | -| | [ALT] Step 16 is executed if A1 interface EiJobObject create/update process shots full success. | -| Step 16 (M) | Near-RT RIC platform responds success to the originating xApp via A1 related API: A1-EI SUBSCRIPTION UPDATE RESULT message. | -| | [ELSE] Step 17 is executed if A1 interface EiJobObject create/update process shots not full success. | -| Step 17 (M) | Near-RT RIC platform responds failure to the originating xApp via A1 related API: A1-EI SUBSCRIPTION UPDATE RESULT message, possibly including appropriate reason. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Participant Non as "Non-RT RIC" - -Box "Near-RT RIC Platform" - Participant plt as "Near-RT RIC platform" - Participant xApp -End box - -autonumber -xApp -> plt: A1-EI SUBSCRIPTION UPDATE REQUEST\n[A1-EI Subscription ID, A1-EI Subscription Update Details] -plt -> plt: (1) Filter A1-EI(s) requested for unsubscribing; \n(2) Filter A1-EI(s) requested for subscribing. - -group For A1-EI(s) requested for unsubscribing -plt -> plt: Delete corresponding A1-EI subscription(s) -loop For each requested A1-EI - plt -> plt: A1 interface EiJobObject\ndelete/update decide process - alt A1 interface EiJobObject delete decision is made - plt <-> Non: Delete EI job procedure - else A1 interface EiJobObject update decision is made - plt <-> Non: Update EI job procedure - end -end loop -end group - -group For A1-EI(s) requested for subscribing -plt <-> plt: Check the originating xApp's\naccess permission to requested A1-EI(s) - -alt The originating xApp is NOT allowed to access some of requested A1-EI(s) - plt -> xApp: A1-EI SUBSCRIPTION UPDATE RESULT [Result{failure}, Reason] - -else The originating xApp is allowed to access all requested A1-EI(s) - plt -> plt: Checks for A1-EI(s) support in Non-RT RIC - alt Some of requested A1-EI(s) is NOT supported in Non-RT RIC - plt -> xApp: A1-EI SUBSCRIPTION UPDATE RESULT [Result{failure}, Reason] - else All requested A1-EI(s) is supported in Non-RT RIC - plt -> plt :Checks created EiJobObject(s) against\nthe originating xApp's request - end -end else - -``` - -``` -alt Created EiJobObject(s) satisfies the originating xApp's request - plt -> xApp: A1-EI SUBSCRIPTION UPDATE RESULT [Result{success}] -else Created EiJobObject(s) does not satisfy the originating xApp's request - - loop For each requested A1-EI does not have created EiJobObject association - plt -> plt: A1 interface EiJobObject\ncreate/update decide process - alt A1 interface EiJobObject create decision is made - plt <-> Non: Create EI job procedure - else A1 interface EiJobObject update decision is made - plt <-> Non: Update EI job procedure - end - end loop - - alt EiJobObject(s) create/update full success - plt -> xApp: A1-EI SUBSCRIPTION UPDATE RESULT [Result{success}] - else EiJobObject(s) create/update NOT full success - plt -> xApp: A1-EI SUBSCRIPTION UPDATE RESULT [Result{failure}, Reason] - end -end -end -end -end group -... -@enduml -``` - -![Sequence diagram showing the interaction between Non-RT RIC, Near-RT RIC platform, and xApp for A1-EI subscription updates. The diagram includes steps for request handling, filtering, decision making (delete/update), and final result reporting with various conditional logic blocks (alt/loop).](640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC platform - participant xApp - - Note over Near-RT RIC platform, xApp: Near-RT RIC Platform - - xApp->>Near-RT RIC platform: 1 A1-EI SUBSCRIPTION UPDATE REQUEST -[A1-EI Subscription ID, A1-EI Subscription Update Details] - Near-RT RIC platform->>Near-RT RIC platform: 2 (1) Filter A1-EI(s) requested for unsubscribing; -(2) Filter A1-EI(s) requested for subscribing. - - rect rgb(240, 240, 240) - Note over Non-RT RIC, Near-RT RIC platform: For A1-EI(s) requested for unsubscribing - Near-RT RIC platform->>Near-RT RIC platform: 3 Delete corresponding A1-EI subscription(s) - loop For each requested A1-EI - Near-RT RIC platform->>Near-RT RIC platform: 4 A1 interface EiJobObject -delete/update decide process - alt A1 interface EiJobObject delete decision is made - Near-RT RIC platform->>Non-RT RIC: 5 Delete EI job procedure - else A1 interface EiJobObject update decision is made - Near-RT RIC platform->>Non-RT RIC: 6 Update EI job procedure - end - end - end - - rect rgb(240, 240, 240) - Note over Non-RT RIC, Near-RT RIC platform: For A1-EI(s) requested for subscribing - Near-RT RIC platform->>Near-RT RIC platform: 7 Check the originating xApp's -access permission to requested A1-EI(s) - alt The originating xApp is NOT allowed to access some of requested A1-EI(s) - Near-RT RIC platform-->>xApp: 8 A1-EI SUBSCRIPTION UPDATE RESULT [Result{failure}, Reason] - else The originating xApp is allowed to access all requested A1-EI(s) - Near-RT RIC platform->>Near-RT RIC platform: 9 Checks for A1-EI(s) support in Non-RT RIC - alt Some of requested A1-EI(s) is NOT supported in Non-RT RIC - Near-RT RIC platform-->>xApp: 10 A1-EI SUBSCRIPTION UPDATE RESULT [Result{failure}, Reason] - else All requested A1-EI(s) is supported in Non-RT RIC - Near-RT RIC platform->>Near-RT RIC platform: 11 Checks created EiJobObject(s) against -the originating xApp's request - alt Created EiJobObject(s) satisfies the originating xApp's request - Near-RT RIC platform-->>xApp: 12 A1-EI SUBSCRIPTION UPDATE RESULT [Result{success}] - else Created EiJobObject(s) does not satisfy the originating xApp's request - loop For each requested A1-EI does not have created EiJobObject association - Near-RT RIC platform->>Near-RT RIC platform: 13 A1 interface EiJobObject -create/update decide process - alt A1 interface EiJobObject create decision is made - Near-RT RIC platform->>Non-RT RIC: 14 Create EI job procedure - else A1 interface EiJobObject update decision is made - Near-RT RIC platform->>Non-RT RIC: 15 Update EI job procedure - end - end - alt EiJobObject(s) create/update full success - Near-RT RIC platform-->>xApp: 16 A1-EI SUBSCRIPTION UPDATE RESULT [Result{success}] - else EiJobObject(s) create/update NOT full success - Near-RT RIC platform-->>xApp: 17 A1-EI SUBSCRIPTION UPDATE RESULT [Result{failure}, Reason] - end - end - end - end - end - -``` - -Sequence diagram showing the interaction between Non-RT RIC, Near-RT RIC platform, and xApp for A1-EI subscription updates. The diagram includes steps for request handling, filtering, decision making (delete/update), and final result reporting with various conditional logic blocks (alt/loop). - -Figure 9.2.3.3-1: A1-EI subscription update procedure - -#### 9.2.3.4 A1-EI subscription delete procedure - -A1-EI subscription delete procedure allows xApp to delete an existing A1-EI subscription toward Near-RT RIC Platform. - -| Use Case Stage | Evolution / Specification | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | To delete an existing A1-EI subscription between xApp and Near-RT RIC Platform. | -| Actors and Roles |
  • Non-RT RIC: A1-EI producer.
  • xApp: requester of A1-EI subscription delete.
  • Near-RT RIC Platform, with the following functionalities:
    • A1 Termination.
| -| Assumptions |
  • Created EiJobObjects in Near-RT RIC is readable by Near-RT RIC platform.
  • xApp's access permission to A1-EI subscription is handled by Near-RT RIC platform.
| -| Pre-conditions |
  • Near-RT RIC Platform is running normal.
  • Near-RT RIC is connected to Non-RT RIC via A1 interface.
| -| Begins when | xApp determines to request delete of one A1-EI subscription. | -| Step 1 (M) | xApp requests Near-RT RIC Platform to delete an A1-EI subscription by sending A1 related API: A1-EI SUBSCRIPTION DELETE REQUEST message, with A1-EI subscription ID included. | -| Step 2 (M) | Near-RT RIC platform checks whether the originating xApp is allowed to access to the requested A1-EI subscription. | -| | [ALT] Step 3 is executed if the originating xApp is not allowed to access to the requested A1-EI subscription. | -| Step 3 (M) | A failure is responded to the originating xApp via A1 related API: A1-EI SUBSCRIPTION DELETE RESULT message, possibly including appropriate reason. | -| | [ELSE] Steps 4-8 are executed if the originating xApp is allowed to access to the requested A1-EI subscription. | -| Step 4 (M) | Near-RT RIC platform finds the created EiJobObjects associated with the requested A1-EI subscription. | -| | [LOOP] Steps 5-7 are looped for each created EiJobObjects associated with the requested A1-EI subscription | -| Step 5 (M) | Near-RT RIC platform makes A1 interface EiJobObject either delete or update decision. | -| | [ALT] Step 6 is executed if A1 interface EiJobObject delete decision is made. | -| Step 6 (M) | Near-RT RIC platform initiates delete EI job procedure towards Non-RT RIC and receives response from Non-RT RIC. | -| | [ELSE] Step 7 is executed if A1 interface EiJobObject update decision is made. | -| Step 7 (M) | Near-RT RIC platform initiates update EI job procedure towards Non-RT RIC and receives response from Non-RT RIC. | -| Step 8 (M) | Near-RT RIC platform responds success to the originating xApp via A1 related API: A1-EI SUBSCRIPTION DELETE RESULT message. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 3 -skinparam BoxPadding 6 -skinparam defaultFontSize 12 - -Participant Non as "Non-RT RIC" - -Box "Near-RT RIC" - Participant plt as "Near-RT RIC platform" - Participant xApp -End box - -autonumber -xApp -> plt: A1-EI SUBSCRIPTION DELETE REQUEST\n[A1-EI Subscription ID] -plt -> plt: Check originating xApp's access\npermission to requested A1-EI subscription. - -alt Originating xApp is not allowed to access to the requested A1-EI subscription - -``` - -``` -plt -> xApp: A1-EI SUBSCRIPTION DELETE RESULT\n[Result{failure}, Reason] -else Originating xApp is allowed to access to the requested A1-EI subscription -plt -> plt: Finds the created EiJobObjects associated\nwith the requested A1-EI subscription - -loop For each created EiJobObject associated\nwith the requested A1-EI subscription - plt -> plt: A1 interface EiJobObject\ndelete/update decide process - alt A1 interface EiJobObject delete decision is made - plt <-> Non: Delete EI job procedure - else A1 interface EiJobObject update decision is made - plt <-> Non: Update EI job procedure - end -end loop - -plt -> xApp: A1-EI SUBSCRIPTION DELETE RESULT\n[Result{success}] -end -... -@enduml -``` - -![Sequence diagram for A1-EI subscription delete procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, xApp. The process involves a delete request, access permission check, an alt block for permission denial or success, a loop for EiJobObject processing, and a final success result.](255efa1d461fc79b4ed367aaec11637f_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - participant Non-RT RIC - - Note right of xApp: Near-RT RIC - xApp->>Near-RT RIC platform: 1 A1-EI SUBSCRIPTION DELETE REQUEST [A1-EI Subscription ID] - Near-RT RIC platform->>Near-RT RIC platform: 2 Check originating xApp's access permission to requested A1-EI subscription. - alt Originating xApp is not allowed to access to the requested A1-EI subscription - Near-RT RIC platform->>xApp: 3 A1-EI SUBSCRIPTION DELETE RESULT [Result{failure}, Reason] - else Originating xApp is allowed to access to the requested A1-EI subscription - Near-RT RIC platform->>Near-RT RIC platform: 4 Finds the created EiJobObjects associated with the requested A1-EI subscription - loop For each created EiJobObject associated with the requested A1-EI subscription - Near-RT RIC platform->>Near-RT RIC platform: 5 A1 interface EiJobObject delete/update decide process - alt A1 interface EiJobObject delete decision is made - Near-RT RIC platform->>Non-RT RIC: 6 Delete EI job procedure - else A1 interface EiJobObject update decision is made - Near-RT RIC platform->>Non-RT RIC: 7 Update EI job procedure - end - end - Near-RT RIC platform->>xApp: 8 A1-EI SUBSCRIPTION DELETE RESULT [Result{success}] - end - Note left of xApp: Near-RT RIC - -``` - -Sequence diagram for A1-EI subscription delete procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, xApp. The process involves a delete request, access permission check, an alt block for permission denial or success, a loop for EiJobObject processing, and a final success result. - -Figure 9.2.3.4-1: A1-EI subscription delete procedure - -#### 9.2.3.5 A1-EI delivery procedure - -The A1-EI delivery procedure allows xApp to be delivered with subscribed A1-EI from Near-RT RIC Platform. - -| Use Case Stage | Evolution / Specification | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | The delivery of A1-EI from Near-RT RIC Platform. | -| Actors and Roles |
  • Non-RT RIC: A1-EI producer.
  • xApp: AI-EI consumer.
  • Near-RT RIC Platform, with the following functionalities:
    • A1 Termination.
| -| Assumptions |
  • jobResultUri indicated by Non-RT RIC to target xApp mapping is handled by Near-RT RIC platform.
| -| Pre-conditions |
  • Near-RT RIC Platform is running normal.
  • Near-RT RIC is connected to Non-RT RIC via A1 interface.
| -| Begins when | Non-RT RIC has A1-EI produced for Near-RT RIC. | -| Step 1 (M) | Non-RT RIC sends a HTTP POST request to deliver the produced EiJobResultObject to Near-RT RIC Platform. | -| Step 2 (M) | Near-RT RIC platform maps jobResultUri indicated by Non-RT RIC to target xApps. | -| | [ALT] If at least one target xApp is identified, execute steps 3-4. | -| Step 3 (M) | Near-RT RIC platform responds Non-RT RIC with status code "204". | -| | [LOOP] Step 4 is looped for each target xApp | -| Step 4 (M) | Near-RT RIC platform delivers the A1-EI to the target xApp by sending A1 related API: A1-EI DELIVERY message, with associated A1-EI subscription ID included. | -| | [ELSE] If NO target xApp is identified, execute steps 5-6. | -| Step 5 (M) | Near-RT RIC platform responds an appropriate error code and possibly error information to Non-RT RIC. | -| Step 6 (O) | Near-RT RIC platform initiates delete EI job procedure towards Non-RT RIC to delete the corresponding EI job and receives response from Non-RT RIC. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 3 -skinparam BoxPadding 6 -skinparam defaultFontSize 12 - -Participant Non as "Non-RT RIC" - -Box "Near-RT RIC" - Participant plt as "Near-RT RIC platform" - Participant xApp -End box - -autonumber -Non -> plt: <>POST {jobResultUri} (EiJobResultObject) -plt -> plt: Mapping jobResultUri to target xApps - -alt Target xApps identified - plt -> Non: <>204 No Content - - loop For each target xApp - plt -> xApp: A1-EI DELIVERY\n[A1-EI Subscription ID, A1-EI] - end loop - -else Target xApps NOT identified - plt -> Non: <>error code 4xx/5xx (error information) - plt <-> Non: Delete EI job procedure -end - -... -@enduml - -``` - -![Sequence diagram of A1-EL delivery procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, xApp. The procedure involves a POST jobResultUri, mapping to target xApps, and then either delivering or deleting the job based on whether targets were identified.](01832e59ebad7ada5e790de6f90cc9b6_img.jpg) - -``` - -sequenceDiagram - participant Non-RT RIC - participant Near-RT RIC platform - participant xApp - - Note right of Near-RT RIC platform: Near-RT RIC - Note left of xApp: xApp - - Non-RT RIC->>Near-RT RIC platform: 1 <>POST {jobResultUri} (EiJobResultObject) - Near-RT RIC platform->>Near-RT RIC platform: 2 Mapping jobResultUri to target xApps - - alt Target xApps identified - Near-RT RIC platform->>Non-RT RIC: 3 <>204 No Content - loop For each target xApp - Near-RT RIC platform->>xApp: 4 A1-EL DELIVERY [A1-EL Subscription ID, A1-EL] - end - else Target xApps NOT identified - Near-RT RIC platform->>Non-RT RIC: 5 <>error code 4xx/5xx (error information) - Near-RT RIC platform->>Non-RT RIC: 6 Delete EI job procedure - end - - Note right of Near-RT RIC platform: Near-RT RIC platform - Note left of xApp: xApp - -``` - -Sequence diagram of A1-EL delivery procedure. Lifelines: Non-RT RIC, Near-RT RIC platform, xApp. The procedure involves a POST jobResultUri, mapping to target xApps, and then either delivering or deleting the job based on whether targets were identified. - -Figure 9.2.3.5-1: A1-EL delivery procedure - -## 9.3 E2 Related API Procedures - -### 9.3.1 Introduction - -The following procedures are described in this clause: - -E2AP RIC Functional procedures: - -- RIC Subscription using **E2 Related API: E2 Subscription** (request, reject, success, failure) and **E2 Related API: E2 Guidance** (request, response); -- RIC Subscription Delete using **E2 Related API: E2 Subscription Delete** (request, reject, success, failure); -- RIC Subscription Delete Required using **E2 Related API: E2 Subscription Delete Query** (required, accept, decline) and **E2 Related API: E2 Subscription Delete Notification** (Deleted); -- RIC Subscription Modification using **E2 Related API: E2 Subscription Modification** (request, reject, success, failure); -- RIC Subscription Audit using **E2 Related API: E2 Subscription Audit** (request, reject, success, failure); -- RIC Indication using **E2 Related API: E2 Indication** (push, failure); -- RIC Control using **E2 Related API: E2 Control** (request, reject, success, failure) and **E2 Related API: E2 Guidance** (request, response); -- RIC Query using **E2 Related API: E2 Query** (request, reject, success, failure). - -E2 Conflict Mitigation related procedures: - -- xApp initiated conflict mitigation using **E2 Related API: E2 Guidance** (request, response); -- xApp Subscription Management initiated conflict mitigation using **E2 Related API: E2 Guidance** (modification); -- Conflict mitigation related message monitoring using **E2 Related API: E2 Guidance** (modification); -- Conflict mitigation initiated conflict mitigation using **E2 Related API: E2 Guidance** (modification); -- Conflict mitigation initiated conflict detection, avoidance, and resolution related xApp processing support using **E2 Related API: E2 Conflict Mitigation Processing** (request, response); -- Conflict mitigation initiated conflict detection, avoidance, and resolution related xApp information support using **E2 Related API: E2 Conflict Mitigation Information** (request, response); -- Conflict mitigation initiated conflict avoidance using **E2 Related API: E2 Conflict Avoidance Negotiation** (request, response); -- xApp initiated conflict avoidance negotiation using **E2 Related API: E2 Conflict Avoidance Negotiation Indication** (notify). - -### 9.3.2 RIC Functional Procedures - -#### 9.3.2.1 E2 Subscription procedure - -The purpose of the E2 Subscription procedure in the Near-RT RIC is to enable an xApp to request subscriptions for REPORT, INSERT and/or POLICY service(s) from E2 interface, and to ensure that only validated and non-duplicate subscriptions are maintained by the Near-RT RIC over the E2 interface to the E2 Node and that duplicated E2 Subscription Request messages from xApps are handled gracefully. - -This procedure is based on the following assumptions: - -- xApp may obtain guidance from Near-RT RIC Platform (i.e., conflict mitigation processing) to resolve potential conflicts and/or detect partial duplications prior to sending a E2 Subscription Request (see clause 9.3.3.1); -- xApp has been configured with a trusted xApp ID; -- Near-RT RIC platform maintains all previous successful RIC Subscriptions towards the E2 Node listed in xApp's E2 Subscription request and is able to detect duplications and recover E2 Node response messages; -- Near-RT RIC platform may leverage its conflict mitigation functionality in managing E2 subscriptions (see clause 9.3.3.5); -- Near-RT RIC platform decides initiation of appropriate E2AP procedure(s), if needed, to fulfil the E2 Subscription request. -- E2 Request ID is used on E2-related APIs to identify an active RIC subscription. Near-RT Platform maintains the 1:1 mapping between E2 Request ID, used on E2 related APIs, and RIC Request ID, used on E2 interface. -- Near-RT RIC platform routes requests for E2AP procedure(s) to appropriate E2 interface; -- Near-RT RIC platform maintains a mapping of active Subscriptions (identified on E2 interface by E2 Node ID and RIC Request ID) of validated xApps. Near-RT RIC platform uses the mapping when sending E2 INDICATION messages to the correct xApp or xApps. -- Near-RT RIC platform sends the E2 Subscription response prior to sending any associated E2 Indication message to the xApp. - -The procedure is initiated by an xApp using **E2 Related API: E2 Subscription** request for a specific E2 Node. The following outcomes are possible: - -- Request fails following rejection by Near-RT RIC platform and an **E2 related API: E2 Subscription** response (Reject) is sent to xApp without E2 interface transaction. Response contains Cause (i.e., xApp not authorized to request specific subscription); -- Request towards a specific E2 Node is handled successfully following acceptance by Near-RT RIC platform but detected as duplicate and so acknowledged with an **E2 related API: E2 Subscription** response (Success) to xApp for a specific E2 Node without corresponding E2 interface transaction; -- Request towards a specific E2 Node is handled successfully following acceptance by Near-RT RIC Platform and acceptance by E2 Node and so acknowledged with an **E2 related API: E2 Subscription** response (Success) to xApp for a specific E2 Node following corresponding E2 interface transaction; -- Request towards a specific E2 Node fails following acceptance by Near-RT RIC Platform but is either rejected by E2 Node or corresponding E2AP timer expires prior to a response from E2 Node and so declined using an **E2 related API: E2 Subscription** response (Failure) to xApp for a specific E2 Node following corresponding E2 interface transaction. Response contains Cause (i.e., Request contents not accepted by E2 Node, E2AP timeout, etc.). - -| Use Case Stage | Evolution / Specification | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | E2 Subscription API procedure from xApp initiation to E2 Node and response. | -| Actors and Roles |
  • • xApp: Originator of E2 Subscription API request;
  • • Near-RT RIC platform, with the following functionalities:
    • – Database;
    • – xApp Subscription Management;
    • – Conflict Mitigation;
    • – E2 Termination.
  • • E2 Node: Handling RIC Subscription related procedure(s).
| -| Assumptions |
  • • Near-RT RIC platform maintains the records of the E2 subscriptions;
  • • Near-RT RIC platform has access to sufficient information to both detect a potential conflict and take a decision on an optimal mitigation solution;
  • • Near-RT RIC platform may generate guidance for internal processes and/or xApp as an optional addition response to Guidance Request.
| -| Pre-conditions |
  • • E2 Node has active E2 interface to Near-RT RIC;
  • • Near-RT RIC has recovered complete list of active RAN Functions on E2 Node and informed initiating xApp;
  • • xApp has been authorized to issue E2 Subscription API Requests;
  • • xApp has been authorized to request guidance from Near-RT RIC platform;
  • • Near-RT RIC platform has been configured to permit E2 Subscription API requests from specific list of xApp;
| -| Begins when | xApp determines need to propose E2 Subscription API request for a specific E2 Node ID and defines message contents (target RAN Function ID, Event Trigger, Action List). | -| Step 1 (O) | xApp can request optional E2 related API: E2 Guidance from Near-RT RIC platform (see clause 9.3.3.1 for details). | -| Step 2 (M) | xApp sends E2 related API: E2 Subscription request with message contents (target RAN Function ID, Event Trigger, Action List) for a specific E2 Node. | -| Step 3 (M) | Near-RT RIC platform, after optional conflict mitigation processing (see clause 9.3.3.5 for details), accepts or rejects proposal from xApp for specific E2 Node. | -| | [ALT] Step 4 is executed if Near-RT RIC platform rejects the proposal: | -| Step 4 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription response to xApp (Reject with Cause for specific E2 Node). | -| | [ELSE] Steps 5-11 are executed if Near-RT RIC platform accepts the proposal: | -| Step 5 (M) | Near-RT RIC platform checks the proposal against its maintained subscription records for duplicate, and determines the subsequent operation. | -| | [ALT] Steps 6-9 are executed if the subscription proposed by xApp necessitates E2AP procedure(s) (i.e., no record found for E2 Node ID with Subscription matching the same contents): | -| Step 6 (M) | Near-RT RIC platform selects appropriate E2 interface and initiates appropriate E2AP procedure(s) to E2 Node. | - -| | | -|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | [ALT] Steps 7-8 are executed if the E2AP procedure(s) in Step 6 succeeds: | -| Step 7 (M) | Near-RT RIC platform updates the subscription records. For each Action in subscription corresponding to an Indication message, Near-RT RIC platform adds the xApp ID to the distribution list associated with the E2 Node ID, RIC Request ID and Action ID. | -| Step 8 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription response to xApp (Success, E2 Node ID, corresponding E2 Request ID(s) and E2 Action ID(s)). | -| | [ELSE] Steps 9 is executed if the E2AP procedure(s) in Step 7 fails: | -| Step 9 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription response to xApp (Failure with Cause, E2 Node ID). | -| | [ELSE] Steps 10-11 are executed if the proposal can be fulfilled with existing subscription(s) (i.e., one or more records found for E2 Node ID with Subscription matching the same contents): | -| Step 10 (M) | Near-RT RIC platform updates the subscription records. For each Action in subscription corresponding to an Indication message, Near-RT RIC platform adds xApp ID to distribution list associated with E2 Node ID, RIC Request ID and Action ID. | -| Step 11 (M) | xApp Subscription Management sends E2 Related API: E2 Subscription response to xApp (Success, E2 Node ID, corresponding E2 Request ID(s) and E2 Action ID(s)). | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid - -box "Near-RT RIC" -Collections "xApp" as xApp -Participant "Near-RT RIC platform" as plt -endbox - -Collections "E2 Node" as ran - -xApp <--> plt: 1: (E2 related API) E2 Guidance (Request/Response) -xApp -> plt: 2: (E2 related API) E2 Subscription (Request, E2 Node ID) - -note over xApp, plt: 3. Conflict Mitigation -Alt Near-RT RIC platform rejects - plt -> xApp: 4: (E2 related API) E2 Subscription (Reject, E2 Node ID, Cause) -Else Near-RT RIC platform accepts - plt -> plt: 5: Detect duplication - - alt E2AP procedure(s) needed - plt <--> ran: 6: <> Appropriate E2AP procedure(s) - - alt E2AP procedure(s) succeeds - - plt -> plt: 7: Update subscription records and\n add the xApp to the distribution list - - plt -> xApp: 8: (E2 related API) E2 Subscription \n(Success, E2 Node ID, E2 Request ID(s), E2 Action ID(s)) - else E2AP procedure(s) fails - plt -> xApp: 9: (E2 related API) E2 Subscription \n (Failure, E2 Node ID, Cause) - end - else Existing subscription(s) can be reused - - plt -> plt: 10: Update subscription records and\n add the xApp to the distribution list - - plt -> xApp: 11: (E2 related API) E2 Subscription \n (Success, E2 Node ID, E2 Request ID(s), E2 Action ID(s)) - end - end - end -end -@enduml - -``` - -![Sequence diagram for E2 Subscription procedure. Lifelines: xApp, Near-RT RIC platform, E2 Node. The process involves E2 Guidance and Subscription requests from xApp to Near-RT RIC platform, followed by conflict mitigation. The platform then either rejects, detects duplication, or initiates E2AP procedures. Successful procedures result in subscription records being updated and the xApp added to the distribution list, returning success details to the xApp. Existing subscriptions can be reused.](107c8e1abcb7033ad244e30e7a910045_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - participant E2 Node - - Note right of Near-RT RIC platform: Near-RT RIC - xApp->>Near-RT RIC platform: 1: (E2 related API) E2 Guidance (Request/Response) - xApp->>Near-RT RIC platform: 2: (E2 related API) E2 Subscription (Request, E2 Node ID) - Note right of Near-RT RIC platform: 3. Conflict Mitigation - - alt Near-RT RIC platform rejects - Near-RT RIC platform-->>xApp: 4: (E2 related API) E2 Subscription (Reject, E2 Node ID, Cause) - else Near-RT RIC platform accepts - Note right of Near-RT RIC platform: 5: Detect duplication - alt E2AP procedure(s) needed - Note right of Near-RT RIC platform: 6: «E2» Appropriate E2AP procedure(s) - alt E2AP procedure(s) succeeds - Note right of Near-RT RIC platform: 7: Update subscription records and add the xApp to the distribution list - Near-RT RIC platform-->>xApp: 8: (E2 related API) E2 Subscription (Success, E2 Node ID, E2 Request ID(s), E2 Action ID(s)) - else E2AP procedure(s) fails - Near-RT RIC platform-->>xApp: 9: (E2 related API) E2 Subscription (Failure, E2 Node ID, Cause) - end - else Existing subscription(s) can be reused - Note right of Near-RT RIC platform: 10: Update subscription records and add the xApp to the distribution list - Near-RT RIC platform-->>xApp: 11: (E2 related API) E2 Subscription (Success, E2 Node ID, E2 Request ID(s), E2 Action ID(s)) - end - end - -``` - -Sequence diagram for E2 Subscription procedure. Lifelines: xApp, Near-RT RIC platform, E2 Node. The process involves E2 Guidance and Subscription requests from xApp to Near-RT RIC platform, followed by conflict mitigation. The platform then either rejects, detects duplication, or initiates E2AP procedures. Successful procedures result in subscription records being updated and the xApp added to the distribution list, returning success details to the xApp. Existing subscriptions can be reused. - -Figure 9.3.2.1-1: E2 Subscription procedure - -#### 9.3.2.2 E2 Subscription Delete procedure - -The purpose of the E2 Subscription Delete procedure in the Near-RT RIC is to ensure that a) only validated RIC Subscription Delete Request messages are issued by the Near-RT RIC over the E2 interface to the E2 Node; b) deletion requests for duplicated Subscription Requests are handled gracefully. - -This procedure is based on the following assumptions: - -- xApp has been configured with a trusted xApp ID; -- Near-RT RIC platform maintains all active subscriptions towards the E2 Node listed in xApp’s E2 Subscription Delete request and is able to detect when and if the delete request shall result in a corresponding E2 message; -- Near-RT RIC platform routes the subscription delete requests to an appropriate E2interface; -- Near-RT RIC platform maintains a mapping of active subscriptions (identified on E2 interface by E2 Node ID and RIC Request ID) of the validated xApps. Near-RT RIC platform uses the mapping when sending RIC INDICATION messages to the correct xApp; - -The procedure initiated by an xApp uses **E2 Related API: E2 Subscription Delete** to request subscription deletion for a specific E2 Node. The following outcomes are possible: - -- Request fails following rejection by Near-RT RIC platform and an **E2 Related API: E2 Subscription Delete** response (Reject) is sent to xApp without E2 interface transaction (i.e., xApp not previously associated with validated subscription); - -- Request succeeds following acceptance by Near-RT RIC platform but other subscriber(s) detected for the subscription, and an **E2 Related API: E2 Subscription Delete** response (Success) is sent to xApp without corresponding E2 transaction; -- Request succeeds following acceptance by Near-RT RIC platform and accepted by E2 Node, and an **E2 Related API: E2 Subscription Delete** response (Success) is sent to xApp following corresponding E2 transaction; -- Request fails following acceptance by Near-RT RIC platform but is either rejected by E2 Node or corresponding E2AP timer expires prior to a response from E2 Node, and an **E2 Related API: E2 Subscription Delete** response (Failure) is sent to xApp following corresponding E2 interface transaction (i.e., RIC Request ID is not known by E2 Node, time out, etc.); - -| Use Case Stage | Evolution / Specification | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | E2 Subscription Delete procedure from xApp initiation to E2 Node and response. | -| Actors and Roles |
  • • xApp: Originator of E2 Subscription Delete request;
  • • Near-RT RIC platform, with the following functionalities:
    • – Database;
    • – xApp Subscription Management;
    • – E2 Termination.
  • • E2 Node: Handling RIC Subscription Delete procedure.
| -| Assumptions |
  • • Near-RT RIC platform maintains the E2 subscription records;
| -| Pre conditions |
  • • E2 Node has active E2 interface to Near-RT RIC;
  • • Near-RT RIC has recovered complete list of active RAN Functions on E2 Node and informed initiating xApp;
  • • Near-RT RIC platform has been configured to permit RIC Subscription Delete requests from xApp.
| -| Begins when | xApp determines need to request E2 Subscription Delete for a specific E2 Node ID and E2 Request ID. | -| Step 1 (M) | xApp sends E2 related API: E2 Subscription Delete request for a specific E2 Node and E2 request ID. | -| Step 2 (M) | Near-RT RIC platform confirms that xApp proposing E2 Subscription Delete has an active subscription. | -| Step 3 (M) | Near-RT RIC platform accepts or rejects proposal from xApp. | -| | [ALT] Step 4 is executed if xApp Subscription Management rejects the proposal: | -| Step 4 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription Delete response to xApp (Reject with Cause for specific E2 Node and E2 Request ID). | -| | [ELSE] Steps 5-13 are executed if xApp Subscription Management accepts the proposal. | -| Step 5 (M) | Near-RT RIC platform checks the subscription records to determine whether or not xApp proposing Subscription Delete is the only associated xApp. | -| | [ALT] Steps 6-11 are executed if the xApp proposing Subscription Delete is the only xApp associated with the subscription (i.e., a given RIC Request ID): | -| Step 6 (M) | Near-RT RIC platform selects appropriate E2 interface and sends RIC Subscription Delete Request (RIC Request ID) to E2 Node. | -| | [ALT] Steps 7-9 are executed if E2 Node accepts Subscription Delete: | -| Step 7 (M) | E2 Node responds with RIC Subscription Delete Response . | -| Step 8 (M) | Near-RT RIC platform updates the subscription records, and deletes the distribution list(s) associated with the E2 Node ID and the RIC Request ID. | -| Step 9 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription Delete response to xApp (Success). | -| | [ELSE] Steps 10-11 are executed if E2 Node rejects Subscription Delete: | -| Step 10 (M) | E2 Node responds with RIC Subscription Delete Failure (with Cause). | -| Step 11 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription Delete response to xApp (Failure with Cause). | -| | [ELSE] Step 12 if E2 Node fails to respond prior to E2AP timer expires | -| Step 12 (M) | Near-RT RIC platform E2AP timer expires and sends E2 related API: E2 Subscription Delete response (Failure with Cause) to xApp. | -| | [ELSE] Steps 13-14 are executed if the xApp proposing Subscription Delete is one of a number of xApp associated with the subscription (i.e., a given RIC Request ID): | - -| | | -|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Step 13 (M) | Near-RT RIC platform updates the subscription records, and removes the xApp from distribution list(s) associated with the E2 Node ID and the RIC Request ID. | -| Step 14 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription Delete response to xApp (Success). | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid - -box "Near-RT RIC platform" -Collections "xApp" as xApp -participant "Near-RT RIC platform" as plt -endbox -Collections "E2 Node" as ran - -xApp -> plt: 1: (E2 related API) E2 Subscription Delete \n(Request, E2 Node ID, E2 Request ID) -plt -> plt: 2: Confirm that xApp had previously subscribed \n(i.e. record found for xApp ID) -plt -> plt: 3: Accept/Reject decision - -Alt Near-RT RIC platform rejects - plt -> xApp: 4: (E2 related API) E2 Subscription Delete \n(Reject, E2 Node ID, E2 Request ID, Cause) -Else Near-RT RIC platform accepts - plt -> plt: 5: Count valid records - - alt Single xApp record - plt -> ran: 6: <> RIC SUBSCRIPTION DELETE REQUEST \n(RIC Request ID) - alt E2 Node accepts delete request - ran -> plt: 7: <> RIC SUBSCRIPTION DELETE RESPONSE - plt -> plt: 8: Update the subscription records, \nand delete the distribution list - - plt-> xApp: 9: (E2 related API) E2 Subscription Delete \n(Success, E2 Node ID, E2 Request ID) - else E2 Node rejects delete request - ran -> plt: 10: <> RIC SUBSCRIPTION DELETE FAILURE - plt -> xApp: 11: (E2 related API) E2 Subscription Delete \n(Failure, E2 Node ID, E2 Request ID, Cause) - else Near-RT detects E2AP timeout - plt->plt: 12a. E2AP time out - plt -> xApp: 12b. (E2 related API) E2 Subscription Delete \n(Failure, E2 Node ID, E2 Request ID, Cause) - End - else Multiple xApp records - plt -> plt: 12: Update the subscription records, \nand delete the xApp from the distribution list - - plt -> xApp: 13: (E2 related API) E2 Subscription Delete \n(Success, E2 Node ID, E2 Request ID) - end -end -@enduml - -``` - -![Sequence diagram for E2 Subscription Delete procedure. Lifelines: xApp, Near-RT RIC platform, E2 Node. The procedure involves an xApp sending a delete request to the Near-RT RIC platform, which then sends a request to the E2 Node. The E2 Node returns a response or failure, which the platform then relays back to the xApp. There are alt blocks for platform rejection, single vs multiple records, and E2 node rejection/timeout.](fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - participant E2 Node - - Note over Near-RT RIC platform: Near-RT RIC platform - - xApp->>Near-RT RIC platform: 1: (E2 related API) E2 Subscription Delete (Request, E2 Node ID, E2 Request ID) - Near-RT RIC platform-->>Near-RT RIC platform: 2: Confirm that xApp had previously subscribed (i.e. record found for xApp ID) - Near-RT RIC platform-->>Near-RT RIC platform: 3: Accept/Reject decision - - alt Near-RT RIC platform rejects - Near-RT RIC platform-->>xApp: 4: (E2 related API) E2 Subscription Delete (Reject, E2 Node ID, E2 Request ID, Cause) - else Near-RT RIC platform accepts - Near-RT RIC platform-->>Near-RT RIC platform: 5: Count valid records - - alt Single xApp record - Near-RT RIC platform->>E2 Node: 6: «E2» RIC SUBSCRIPTION DELETE REQUEST (RIC Request ID) - - alt E2 Node accepts delete request - E2 Node-->>Near-RT RIC platform: 7: «E2» RIC SUBSCRIPTION DELETE RESPONSE - Near-RT RIC platform-->>Near-RT RIC platform: 8: Update the subscription records, and delete the distribution list - Near-RT RIC platform-->>xApp: 9: (E2 related API) E2 Subscription Delete (Success, E2 Node ID, E2 Request ID) - else E2 Node rejects delete request - E2 Node-->>Near-RT RIC platform: 10: «E2» RIC SUBSCRIPTION DELETE FAILURE - Near-RT RIC platform-->>xApp: 11: (E2 related API) E2 Subscription Delete (Failure, E2 Node ID, E2 Request ID, Cause) - else Near-RT detects E2AP timeout - Near-RT RIC platform-->>Near-RT RIC platform: 12a. E2AP time out - Near-RT RIC platform-->>xApp: 12b. (E2 related API) E2 Subscription Delete (Failure, E2 Node ID, E2 Request ID, Cause) - end - else Multiple xApp records - Near-RT RIC platform-->>Near-RT RIC platform: 13: Update the subscription records, and delete the xApp from the distribution list - Near-RT RIC platform-->>xApp: 14: (E2 related API) E2 Subscription Delete (Success, E2 Node ID, E2 Request ID) - end - end - Note over Near-RT RIC platform: Near-RT RIC platform - -``` - -Sequence diagram for E2 Subscription Delete procedure. Lifelines: xApp, Near-RT RIC platform, E2 Node. The procedure involves an xApp sending a delete request to the Near-RT RIC platform, which then sends a request to the E2 Node. The E2 Node returns a response or failure, which the platform then relays back to the xApp. There are alt blocks for platform rejection, single vs multiple records, and E2 node rejection/timeout. - -Figure 9.3.2.2-1: E2 Subscription Delete procedure - -#### 9.3.2.2A E2 Subscription Delete Query procedure and E2 Subscription Delete Notification procedure - -The purpose of the E2 Subscription Delete Query procedure and E2 Subscription Delete Notification Procedure in the Near-RT RIC is to ensure that deletion request of the existing subscriptions from an E2 Node is handled properly. - -The two procedures are based on the following assumptions: - -- The Near-RT RIC platform maintains the list of xApps associated with the subscription removal request from an E2 Node and, if decides to accept, uses the E2 related API: E2 Subscription Delete Notification (Deleted) to delete subscriptions toward xApps. Prior to determining whether or not to accept the subscription delete required request, the Near-RT RIC platform may send E2 related API: E2 Subscription Delete Query (required) to each xApp with an active subscription, each xApp may respond with E2 related API: E2 Subscription Delete (accept) or E2 related API: E2 Subscription Delete (decline). The procedures may be initiated by the Near-RT RIC platform, when RIC Subscription Delete Required is received from an E2 Node. The Near-RT RIC platform may use the **E2 Related API: E2 Subscription Delete Query (required)** to consult xApps. - -The following outcomes are possible: - -- xApp accepts request to delete subscription and sends E2 Related API: E2 Subscription Delete Query (accept) to accept subscription deletion. -- xApp declines request to delete subscription and sends E2 Related API: E2 Subscription Delete Query (decline) to inform Near-RT RIC platform. - -In both cases, the Near-RT RIC platform may decide whether to delete the subscription. - -The Near-RT RIC platform may also decide whether to delete the subscription without consulting xApps. - -If the Near-RT RIC platform decides to delete the subscription, it uses **E2 Related API: E2 Subscription Delete Notification (Deleted)** to inform each xApp for the eventual outcome. - -| Use Case Stage | Evolution / Specification | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | RIC subscription removal initiated from an E2 Node. | -| Actors and Roles |
  • • xApp: Recipient of E2 Subscription Delete query and notification;
  • • Near-RT RIC platform, with the following functionalities:
    • – Database;
    • – xApp Subscription Management;
    • – E2 Termination.
  • • E2 Node: Originator of RIC Subscription Delete Required.
| -| Assumptions |
  • • Near-RT RIC platform maintains the records of E2 subscriptions;
| -| Pre conditions |
  • • E2 Node has active E2 interface to Near-RT RIC;
  • • Near-RT RIC has recovered complete list of active RAN Functions on E2 Node and informed xApps;
  • • Near-RT RIC platform has been configured to accept incoming RIC subscription removal request from an E2 Node;
  • • Near-RT RIC platform has been configured to permit RIC Subscription removal request from an E2 Node.
| -| Begins when | E2 Node determines a need to request removal of some RIC subscriptions that has been subscribed toward itself from Near-RT RIC. | -| Step 1 (M) | E2 Node sends RIC Subscription Delete Required (a list of RIC Request IDs and RAN Function IDs with cause). | -| | [LOOP] Steps 2-12 are looped for each Subscription requested to be deleted: | -| Step 2 (M) | Near-RT RIC platform checks the subscription records to find the list of xApps associated with RIC subscription requested to be deleted from the E2 Node. | -| | [OPT] Steps 3-5 may be executed. For each xApp with RIC Subscription requested to be deleted: | -| Step 3 (O) | Near-RT RIC platform sends E2 related API: E2 Subscription Delete Query Required to xApp (with E2 Node ID, E2 Request ID and Cause) to request xApp advice on required subscription deletion. | -| Step 4 (O) | If xApp accepts, xApp responds with E2 related API: E2 Subscription Delete Query Accept to Near-RT RIC platform (with E2 Node ID, E2 Request ID). | - -| | | -|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Step 5 (O) | If xApp rejects, xApp responds with E2 related API: E2 Subscription Delete Query Decline to Near-RT RIC platform (with E2 Node ID, E2 Request ID). | -| Step 6 (M) | Near-RT RIC platform takes decision whether to accept/reject RIC subscription delete. | -| | [OPT] Steps 7-12 are executed if Near-RT RIC platform accepts: | -| Step 7 (M) | Near-RT RIC platform selects appropriate E2 interface and sends RIC Subscription Delete Request (RIC Request ID) to E2 Node. | -| | [ALT] Steps 8-10 are executed if E2 Node accepts Subscription Delete: | -| Step 8 (M) | E2 Node responds with RIC Subscription Delete Response . | -| Step 9 (M) | Near-RT RIC platform updates the subscription records, and deletes the distribution list associated with the E2 Node ID and the RIC Request ID. | -| Step 10 (M) | For each concerned xApp, Near-RT RIC platform sends E2 related API: E2 Subscription Delete Notification (with E2 Node ID, E2 Request ID, Cause) to inform xApp that subscription has been deleted. | -| | [ELSE] Steps 11-12 are executed if E2 Node rejects Subscription Delete: | -| Step 11 (M) | E2 Node responds with RIC Subscription Delete Failure (with Cause). | -| Step 12 (M) | Near-RT RIC platform decides subsequent processing (e.g., retry RIC Subscription Delete). The failure outcome is not needed to inform the xApp. | -| | [ELSE] Step 13 is executed if E2 Node fails to respond prior to E2AP timer expires | -| Step 13 (M) | Near-RT RIC platform E2AP timer expires and decides subsequent processing (e.g., retry RIC Subscription Delete). The failure outcome is not needed to inform the xApp. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid - -box "Near-RT RIC" - Collections "xApp" as xApp - participant "Near-RT RIC platform" as plt -endbox -Collections "E2 Node" as ran - -ran -> plt: 1. <> RIC SUBSCRIPTION DELETE REQUIRED -Loop For each RIC Request ID - plt -> plt: 2. Check subscription records for concerned xApps \n(RIC Request ID, E2 Node ID) - opt Optional - Loop For each xApp with E2 Request ID - plt -> xApp: 3. (E2 related API) E2 Subscription Delete Query \n(Required, E2 Node ID, E2 Request ID, Cause) - alt xApp accepts delete required - xApp -> plt: 4. (E2 related API) E2 Subscription Delete Query \n(Accept, E2 Node ID, E2 Request ID) - else xApp rejects delete required - xApp -> plt: 5. (E2 related API) E2 Subscription Delete Query \n(Decline, E2 Node ID, E2 Request ID) - end - end - end - plt -> plt: 6. Accept/Reject decision - - opt Near-RT RIC platform accepts - - plt -> ran: 7. <> RIC SUBSCRIPTION DELETE REQUEST - alt E2 Node accepts delete request - ran -> plt: 8. <> RIC SUBSCRIPTION DELETE RESPONSE - - plt -> plt: 9. Update subscription records, and delete the distribution list - loop For each xApp with E2 Request ID - plt -> xApp: 10. (E2 related API) E2 Subscription Delete Notification \n(Deleted, E2 - -``` - -``` - -Node ID, E2 Request ID, Cause) -end -else E2 Node rejects delete request - ran -> plt: 11. <> RIC SUBSCRIPTION DELETE FAILURE - plt -> plt: 12. Decide subsequent processing \n(e.g., retry RIC subscription delete) - -else Near-RT detects E2AP timeout - plt->plt: 13. E2AP time out. Decide subsequent processing \n(e.g., retry RIC subscription delete) -end -end -end - -@enduml - -``` - -![Sequence diagram showing the E2 Subscription Delete Query and E2 Subscription Delete Notification procedure. Lifelines: xApp, Near-RT RIC platform, and E2 Node. The process involves a delete required message from E2 Node, a loop for each RIC Request ID, an optional block for checking subscription records, a loop for each xApp with E2 Request ID, an alt block for xApp accept/reject, a decision by the platform, an optional block for platform accept, an alt block for E2 Node accept/reject, a loop for notifications if accepted, and finally handling a rejection or timeout by the platform.](e2c120be98ede6deb60dd341f5a9803b_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - participant E2 Node - - Note over xApp, Near-RT RIC platform: Near-RT RIC - - E2 Node->>Near-RT RIC platform: 1. «E2» RIC SUBSCRIPTION DELETE REQUIRED - loop For each RIC Request ID - Near-RT RIC platform->>Near-RT RIC platform: 2. Check subscription records for concerned xApps -(RIC Request ID, E2 Node ID) - opt Optional - loop For each xApp with E2 Request ID - Near-RT RIC platform->>xApp: 3. (E2 related API) E2 Subscription Delete Query -(Required, E2 Node ID, E2 Request ID, Cause) - alt xApp accepts delete required - xApp->>Near-RT RIC platform: 4. (E2 related API) E2 Subscription Delete Query -(Accept, E2 Node ID, E2 Request ID) - else xApp rejects delete required - xApp->>Near-RT RIC platform: 5. (E2 related API) E2 Subscription Delete Query -(Decline, E2 Node ID, E2 Request ID) - end - end - end - Near-RT RIC platform->>Near-RT RIC platform: 6. Accept/Reject decision - opt Near-RT RIC platform accepts - Near-RT RIC platform->>E2 Node: 7. «E2» RIC SUBSCRIPTION DELETE REQUEST - alt E2 Node accepts delete request - E2 Node->>Near-RT RIC platform: 8. «E2» RIC SUBSCRIPTION DELETE RESPONSE - Near-RT RIC platform->>Near-RT RIC platform: 9. Update subscription records, and delete the distribution list - loop For each xApp with E2 Request ID - Near-RT RIC platform->>xApp: 10. (E2 related API) E2 Subscription Delete Notification -(Deleted, E2 Node ID, E2 Request ID, Cause) - end - else E2 Node rejects delete request - E2 Node->>Near-RT RIC platform: 11. «E2» RIC SUBSCRIPTION DELETE FAILURE - Near-RT RIC platform->>Near-RT RIC platform: 12. Decide subsequent processing -(e.g., retry RIC subscription delete) - else Near-RT detects E2AP timeout - Near-RT RIC platform->>Near-RT RIC platform: 13. E2AP time out. Decide subsequent processing -(e.g., retry RIC subscription delete) - end - end - end - -``` - -Sequence diagram showing the E2 Subscription Delete Query and E2 Subscription Delete Notification procedure. Lifelines: xApp, Near-RT RIC platform, and E2 Node. The process involves a delete required message from E2 Node, a loop for each RIC Request ID, an optional block for checking subscription records, a loop for each xApp with E2 Request ID, an alt block for xApp accept/reject, a decision by the platform, an optional block for platform accept, an alt block for E2 Node accept/reject, a loop for notifications if accepted, and finally handling a rejection or timeout by the platform. - -Figure 9.3.2.2A-1: E2 Subscription Delete Query and E2 Subscription Delete Notification procedure - -#### 9.3.2.3 E2 Indication procedure - -The purpose of the E2 Indication procedure in the Near-RT RIC is to ensure delivery of RIC INDICATION messages to one or more validated xApps. - -This procedure is based on the following assumptions: - -- Near-RT RIC platform maintains a list for each E2 Node of validated xApps and the corresponding assigned E2 Request ID and E2 Action ID(s) associated with an E2 node ID, RIC REQUEST ID and RIC Action ID(s); -- E2 related API ensures delivery of E2 Indication messages from Near-RT RIC platform to all validated xApp; -- Near-RT RIC platform may support distribution of messages to multiple destinations. - -The following outcomes are possible: - -- Message is received, using E2 related API: E2 Indication (push), and successfully processed by xApp; -- Message is received, using E2 related API: E2 Indication (push), but an error is detected by the xApp and so declined using an E2 related API: E2 Indication (failure) from xApp for a specific E2 Node, E2 Request ID, E2 Action ID and E2 Indication SN. Response contains Cause (i.e., Request contents not accepted by xApp). - -| Use Case Stage | Evolution / Specification | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | E2 Indication procedure from E2 Node initiation to xApp reception. | -| Actors and Roles |
  • • xApp: Originator of RIC subscription request;
  • • Near-RT RIC platform, with the following functionalities:
    • – Database;
    • – xApp Subscription Management;
    • – E2 Termination.
  • • E2 Node: Originator of RIC Indication procedure.
| -| Assumptions |
  • • For RIC Indication procedures, Near-RT RIC platform uses E2 related API to directly send received messages to one or more xApp.
| -| Pre conditions |
  • • E2 Node has active E2 interface to Near-RT RIC;
  • • Near-RT RIC has recovered complete list of active RAN Functions on E2 Node and informed initiating xApp;
  • • Near-RT RIC platform has distribution list associating Indication messages with xApps.
| -| Begins when | E2 Node creates RIC Indication Message (RIC Request ID, RAN Function ID, RIC Action ID, optional RIC Indication SN, Indication Type, Indication Header, Indication Message, optional Call Process ID). | -| Step 1 (M) | E2 Node sends RIC Indication message to Near-RT RIC platform. | -| Step 2 (M) | Near-RT RIC platform checks distribution list for E2 Node ID, RIC REQUEST ID, RAN Function ID, RIC Action ID. | -| Step 3 (M) | Near-RT RIC platform sends E2 related API: E2 Indication (push, E2 Node ID, E2 Request ID, E2 Action ID, E2 Indication SN, Message) to xApp(s). | -| Step 4 (O) | If an error is detected in the received message, the xApp may send E2 related API: E2 Indication (failure, E2 Node ID, E2 Request ID, E2 Action ID, E2 Indication SN, Cause). | -| Step 5 (O) | The Near-RT RIC platform may send an appropriate E2AP procedure message | - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid - -box "Near-RT RIC" -Collections "xApp" as xApp -Participant "Near-RT RIC platform" as plt -endbox -``` - -Collections "E2 Node" as ran - -``` - -ran -> plt: <> 1: RIC INDICATION -plt -> plt: 2: Check distribution list - -plt -> xApp: 3. (E2 related API) E2 Indication (push) -Opt error detected - -xApp --> plt: 4: (E2 related API) E2 Indication (failure, Cause) -plt --> ran: 5: <> E2AP Procedure -end -@enduml - -``` - -![Sequence diagram for E2 Indication procedure. Lifelines: xApp, Near-RT RIC platform, and E2 Node. The process starts with the E2 Node sending a RIC INDICATION to the platform, which checks a distribution list and then pushes an indication to the xApp. An 'error detected' block follows, where the xApp sends a failure indication back to the platform, which then initiates an E2AP procedure back to the E2 Node.](9cb54072e43a6b6717eb16036a7640a2_img.jpg) - -``` - -sequenceDiagram - participant E2 Node - participant Near-RT RIC platform - participant xApp - - Note over Near-RT RIC platform: Collections "E2 Node" as ran - - E2 Node->>Near-RT RIC platform: <> 1: RIC INDICATION - Near-RT RIC platform->>Near-RT RIC platform: 2: Check distribution list - Near-RT RIC platform->>xApp: 3. (E2 related API) E2 Indication (push) - opt error detected - xApp-->>Near-RT RIC platform: 4: (E2 related API) E2 Indication (failure, Cause) - Near-RT RIC platform-->>E2 Node: 5: <> E2AP Procedure - end - -``` - -Sequence diagram for E2 Indication procedure. Lifelines: xApp, Near-RT RIC platform, and E2 Node. The process starts with the E2 Node sending a RIC INDICATION to the platform, which checks a distribution list and then pushes an indication to the xApp. An 'error detected' block follows, where the xApp sends a failure indication back to the platform, which then initiates an E2AP procedure back to the E2 Node. - -Figure 9.3.2.3-1: E2 Indication procedure - -#### 9.3.2.4 E2 Control procedure - -The purpose of the E2 Control procedure in the Near-RT RIC is to ensure that only authorized xApp may initiate RIC Control Request messages issued by the Near-RT RIC over the E2 interface to the E2 Node. - -This procedure is based on the following assumptions: - -- xApp may obtain guidance from Near-RT RIC platform to resolve potential conflicts prior to sending a E2 Control Request (see clause 9.3.3.1); -- xApp has been configured with a trusted xApp ID; -- Near-RT RIC platform may leverage its conflict mitigation functionality in processing E2 Control Request messages (see clause 9.3.3.5); -- Near-RT RIC platform may be configured to route E2 Control Request messages for a E2 node from xApp either to trigger conflict mitigation for acceptance or directly towards an appropriate E2interface; -- Near-RT RIC platform ensures that only authorized xApp may send E2 Control Request messages to appropriate E2 interface; -- Near-RT RIC platform ensures that it systematically forwards any received RIC Control Response or RIC Control Failure to appropriate xApp. - -The procedure is initiated by an xApp using E2 Related API: E2 Control request to send a request of a RIC Control for an E2 Node. The following outcomes are possible: - -- Request successful following acceptance by Near-RT RIC platform and accepted by E2 Node and so an **E2 Related API: E2 Control** response (Success with outcome) is sent to xApp following corresponding E2 transaction; -- Request fails following acceptance by Near-RT RIC platform but is either rejected by E2 Node or corresponding E2AP timer expires prior to a response from E2 Node and so an **E2 Related API: E2 Control** response (Failure with cause) is sent to xApp following corresponding E2 interface transaction (i.e., Request contents is not compliant, E2AP timeout, etc.); -- Request rejected by Near-RT Platform and so an **E2 Related API: E2 Control** response (Reject) is sent to xApp (i.e., rejected due to conflict mitigation). - -| Use Case Stage | Evolution / Specification | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | E2 Control procedure from xApp initiation to E2 Node and response. | -| Actors and Roles |
  • • xApp: Originator of E2 Control request;
  • • Near-RT RIC platform, with the following functionalities:
    • – E2 Termination.
  • • E2 Node: RIC Control procedure.
| -| Assumptions |
  • • For E2 Control procedures, Near-RT RIC platform may forward the xApp's control request directly to the E2 interface;
  • • Near-RT RIC platform has access to sufficient information to both detect a potential conflict and take a decision on an optimal mitigation solution.
| -| Pre-conditions |
  • • E2 Node has active E2 interface to Near-RT RIC;
  • • Near-RT RIC has recovered complete list of active RAN Functions on E2 Node and informed initiating xApp;
  • • xApp has been authorized to send RIC Control requests for a specific scope (E2 Node list, RAN Function, etc.);
  • • xApp has been authorized to request guidance from Near-RT RIC platform;
  • • Near-RT RIC platform has been configured to accept incoming E2 Control requests from authorized xApp and, either trigger conflict mitigation or forward directly to E2interface.
| -| Begins when | xApp determines need to propose RIC Control procedure for a E2 Node and defines message contents (RAN Function ID, Call process ID, Control Header, Control message). | -| Step 1 (O) | xApp may request E2 related API: E2 Guidance from Near-RT RIC platform (see clause 9.3.3.1 for details) | -| Step 2 (M) | xApp sends E2 related API: E2 Control request with message contents (RAN Function ID, Call process ID, Control Header, Control message) for an E2 Node. | -| Step 3 (M) | Near-RT RIC platform, after conflict mitigation (see clause 9.3.3.5), accepts or rejects proposal from xApp for specific E2 Node. | -| | [ALT] Step 4 is executed if Near-RT RIC platform rejects proposed E2 Control message. | -| Step 4 (M) | E2 related API: E2 Control response (Reject with Cause) message is sent to xApp. | -| | [ELSE] Step 5-10 are executed if Near-RT RIC platform accepts proposed E2 Control message: | -| Step 5 (M) | Near-RT RIC platform selects appropriate E2 interface and assigns an appropriate RIC Request ID. | -| Step 6 (M) | Near-RT RIC platform sends RIC Control Request (RIC Request ID, contents) to E2 Node. | -| | [ALT] Steps 7-8 are executed if E2 Node accepts RIC Control Request: | -| Step 7 (M) | E2 Node responds with RIC Control Acknowledge . | -| Step 8 (M) | Near-RT RIC platform sends E2 Related API: E2 Control response (Success with Outcome) to xApp. | -| | [ELSE] Steps 9-10 are executed if E2 Node rejects RIC Control Request: | -| Step 9 (M) | E2 Node responds with RIC Control Failure (with Cause). | -| Step 10 (M) | Near-RT RIC platform sends E2 Related API: E2 Control response (Failure with Cause) to xApp. | -| | [ELSE] Step 11 is executed if E2 Node fails to respond prior to E2AP timer expires | -| Step 11 (M) | Near-RT RIC platform E2AP timer expires and sends E2 Related API: E2 Control response (Failure with Cause) to xApp. | - -``` -@startuml -skin rose -``` - -``` - -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Participant xApp - Participant "Near-RT RIC platform" as plt -endbox - -Collections "E2 Node" as ran - -xApp <--> plt: 1: (E2 related API) Guidance (Request/Response) - -xApp -> plt: 2: (E2 related API) E2 Control (Request) - -note over xApp, plt: 3. Conflict Mitigation - -alt Near-RT RIC platform rejects request - plt -> xApp: 4: (E2 related API) E2 Control (Reject) -else Near-RT RIC platform accepts request - - plt -> plt: 5: Select appropriate E2 interface and assigns RIC Request ID - plt -> ran: 6: <> RIC CONTROL REQUEST - - alt E2 node accepts request - ran -> plt: 7: <> RIC CONTROL ACKNOWLEDGE - plt -> xApp: 8: (E2 related API) E2 Control (Success) - else E2 node rejects request - ran -> plt: 9: <> RIC CONTROL FAILURE - plt -> xApp: 10: (E2 related API) E2 Control (Failure) - else Near-RT detects E2AP timeout - plt-> plt: 11a: E2AP time out - plt -> xApp: 11b: (E2 related API) E2 Control (Failure) - end -end -end -@enduml - -``` - -![Sequence diagram illustrating the E2 Control Procedure. Lifelines: xApp, Near-RT RIC platform, and E2 Node. The diagram shows the interaction between xApp and Near-RT RIC platform for guidance and control, followed by conflict mitigation. The Near-RT RIC platform then interacts with the E2 Node via RIC CONTROL REQUEST and receives either an ACKNOWLEDGE or FAILURE, or detects a timeout. Finally, the Near-RT RIC platform sends a response back to the xApp.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - participant E2 Node - - Note right of Near-RT RIC platform: 3. Conflict Mitigation - - alt Near-RT RIC platform rejects request - Note right of Near-RT RIC platform: 4. (E2 related API) E2 Control (Reject) - else Near-RT RIC platform accepts request - Note right of Near-RT RIC platform: 5: Select appropriate E2 interface and assigns RIC Request ID - Note right of Near-RT RIC platform: 6: <> RIC CONTROL REQUEST - alt E2 node accepts request - Note right of Near-RT RIC platform: 7: <> RIC CONTROL ACKNOWLEDGE - Note right of Near-RT RIC platform: 8: (E2 related API) E2 Control (Success) - else E2 node rejects request - Note right of Near-RT RIC platform: 9: <> RIC CONTROL FAILURE - Note right of Near-RT RIC platform: 10: (E2 related API) E2 Control (Failure) - else Near-RT detects E2AP timeout - Note right of Near-RT RIC platform: 11a: E2AP time out - Note right of Near-RT RIC platform: 11b: (E2 related API) E2 Control (Failure) - end - end - -``` - -Sequence diagram illustrating the E2 Control Procedure. Lifelines: xApp, Near-RT RIC platform, and E2 Node. The diagram shows the interaction between xApp and Near-RT RIC platform for guidance and control, followed by conflict mitigation. The Near-RT RIC platform then interacts with the E2 Node via RIC CONTROL REQUEST and receives either an ACKNOWLEDGE or FAILURE, or detects a timeout. Finally, the Near-RT RIC platform sends a response back to the xApp. - -Figure 9.3.4-1 E2 Control Procedure - -#### 9.3.2.5 E2 Subscription Audit procedure - -The purpose of the E2 Subscription Audit procedure in the Near-RT RIC is to enable an xApp to initiate an audit of one or more existing E2 subscriptions. - -This procedure is based on the following assumptions: - -- xApp has been configured with a trusted xApp ID; -- Near-RT RIC platform maintains all active subscriptions towards the E2 Node listed in xApp's E2 Subscription Audit request and is able to detect when and if the audit request shall result in a corresponding E2 message; -- Near-RT RIC platform routes the subscription audit requests to an appropriate E2 interface; -- Near-RT RIC platform maintains a mapping of active subscriptions (identified on E2 interface by E2 Node ID and RIC Request ID) of the validated xApps. Near-RT RIC platform uses the mapping when sending RIC INDICATION messages to the correct xApp; - -The procedure initiated by an xApp uses **E2 Related API: E2 Subscription Audit** to request subscription audit for a specific E2 Node. The following outcomes are possible: - -- Request fails following rejection by Near-RT RIC platform and an **E2 Related API: E2 Subscription Audit** response (Reject) is sent to xApp without E2 interface transaction (i.e., xApp not previously associated with one or more validated subscription); -- Request succeeds following acceptance by Near-RT RIC platform and accepted by E2 Node, and an **E2 Related API: E2 Subscription Audit** response (Success) is sent to xApp following corresponding E2 interface transaction; -- Request succeeds following acceptance by Near-RT RIC platform and an **E2 Related API: E2 Subscription Audit** response (Success) is sent to xApp without E2 interface transaction; -- Request fails following acceptance by Near-RT RIC platform but is either rejected by E2 Node or corresponding E2AP timer expires prior to a response from E2 Node, and an **E2 Related API: E2 Subscription Audit** response (Failure) is sent to xApp following corresponding E2 interface transaction (i.e., RIC Request ID is not known by E2 Node, E2AP timeout, etc.); -- Request fails following acceptance by Near-RT RIC platform and an **E2 Related API: E2 Subscription Audit** response (Failure) is sent to xApp without E2 interface transaction. - -This procedure may result in the Near-RT RIC platform issuing **E2 related API: E2 Subscription Delete Notification** (with E2 Node ID, E2 Request ID, Cause) message(s) to inform other xApp that a subscription has been deleted. This may also occur if the Near-RT RIC platform independently initiates a RIC Subscription Audit procedure. - -| Use Case Stage | Evolution / Specification | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | E2 Subscription Audit procedure from xApp initiation to E2 Node and response. | -| Actors and Roles |
  • xApp: Originator of E2 Subscription Audit request;
  • Near-RT RIC platform, with the following functionalities:
    • Database;
    • xApp Subscription Management;
    • E2 Termination.
  • E2 Node: Handling RIC Subscription Audit procedure.
| -| Assumptions |
  • Near-RT RIC platform maintains the E2 subscription records;
| -| Pre conditions |
  • E2 Node has active E2 interface to Near-RT RIC;
  • Near-RT RIC has recovered complete list of active RAN Functions on E2 Node and informed initiating xApp;
  • Near-RT RIC platform has been configured to permit RIC Subscription Audit requests from xApp.
| -| Begins when | xApp determines need to request E2 Subscription Audit for a specific E2 Node ID and one or more E2 Request ID. | -| Step 1 (M) | xApp sends E2 related API: E2 Subscription Audit request for a specific E2 Node and one or more E2 request ID. | -| Step 2 (M) | Near-RT RIC platform confirms that xApp proposing E2 Subscription Audit has an active subscription associated with each E2 Request ID in the list provided by the xApp. | -| Step 3 (M) | Near-RT RIC platform accepts or rejects proposal from xApp. | -| | [ALT] Step 4 is executed if Near-RT RIC platform rejects the proposal: | -| Step 4 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription Audit response to xApp (Reject with Cause for specific E2 Node and one or more E2 Request ID). | -| | [ELSE] Steps 5-15 are executed if Near-RT RIC platform accepts the proposal. | -| | [ALT] Steps 5-12 are executed if the Near-RT RIC executes a corresponding E2 interface transaction. | -| Step 5 (M) | Near-RT RIC platform selects appropriate E2 interface and sends RIC Subscription Audit Request (one or more RIC Request ID including subscriptions from xApp) to E2 Node. | -| | [ALT] Steps 6-7 are executed if E2 Node accepts Subscription Audit: | -| Step 6 (M) | E2 Node responds with RIC Subscription Audit Response , with lists of confirmed, unknown and/or missing subscriptions. | -| Step 7 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription Audit response to xApp (Success). | -| | [ELSE] Steps 8-9 are executed if E2 Node rejects Subscription Audit: | -| Step 8 (M) | E2 Node responds with RIC Subscription Audit Failure (with Cause). | -| Step 9 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription Audit response to xApp (Failure with Cause). | -| | [ELSE] Step 10 is executed if E2 Node fails to respond prior to E2AP timer expires | -| Step 10 (M) | Near-RT RIC platform E2AP timer expires and sends E2 Related API: E2 Subscription Audit response (Failure with Cause) to xApp. | -| Step 11 (M) | Near-RT RIC platform updates subscription records. | -| Step 12 (O) | If one or more subscriptions are listed as missing, then the Near-RT RIC platform may initiate RIC Subscription Delete procedure to delete subscription on E2 Node. | -| | [ELSE] Steps 13-14 are executed if the Near-RT RIC determines that xApp response may be generated without a corresponding E2 interface transaction. | -| | [ALT] Step 12 is executed if the result is a success: | -| Step 13 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription Audit response to xApp (Success). | -| | [ELSE] Step 14 is executed if the result is a failure: | -| Step 14 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription Audit response to xApp (Failure with Cause). | -| Step 15 (O) | If one or more subscriptions are listed as unknown, then Near-RT RIC platform may send E2 related API: E2 Subscription Delete Notification (with E2 Node ID, E2 Request ID, Cause) to inform concerned xApps that subscription has been deleted. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid - -box "Near-RT RIC platform" - participant "xApp" as xApp - collections "Other xApp" as xApp2 - participant "Near-RT RIC platform" as plt -endbox -Collections "E2 Node" as ran - -xApp -> plt: 1: (E2 related API) E2 Subscription Audit \n(Request, E2 Node ID, List of E2 Request ID) -plt -> plt: 2: Confirm that xApp had previously subscribed \n(i.e. record found for xApp ID) -plt -> plt: 3: Accept/Reject decision - -Alt Near-RT RIC platform rejects - plt -> xApp: 4: (E2 related API) E2 Subscription Audit \n(Reject, E2 Node ID, List of E2 Request ID, Cause) - -Else Near-RT RIC platform accepts - Alt Near-RT RIC initiates E2 interface transaction - plt -> ran: 5: <> RIC SUBSCRIPTION AUDIT REQUEST \n(Audit flag, List of RIC Request ID) - alt E2 Node accepts audit request - ran -> plt: 6: <> RIC SUBSCRIPTION AUDIT RESPONSE \n(Confirmed, Unknown and/or \nMissing list of RIC Request ID) - plt-> xApp: 7: (E2 related API) E2 Subscription Audit \n(Success, E2 Node ID, Confirmed, Unknown and/or \nMissing list of E2 Request ID) - else E2 Node rejects audit request - ran -> plt: 8: <> RIC SUBSCRIPTION AUDIT FAILURE - plt -> xApp: 9: (E2 related API) E2 Subscription Audit \n(Failure, E2 Node ID, Cause) - else Near-RT detects E2AP timeout - plt-> plt: 10a. E2AP time out - plt -> xApp: 10b. (E2 related API) E2 Subscription Audit (Failure) - end - - plt -> plt: 11: Update the subscription records - plt <--> ran: 12: <> RIC Subscription Delete procedure (RIC Request ID) - - else Near-RT RIC responses without E2 interface transaction - alt Result is success - plt-> xApp: 13: (E2 related API) E2 Subscription Audit \n(Success, E2 Node ID, Confirmed, Unknown and/or \nMissing list of E2 Request ID) - else Result is failure - plt -> xApp: 14: (E2 related API) E2 Subscription Audit \n(Failure, E2 Node ID, Cause) - end - end - - plt --> xApp: 15a: (E2 related API) E2 Subscription Delete Notification \n(Deleted, E2 Node ID, E2 Request ID, Cause) - plt --> xApp2: 15b: (E2 related API) E2 Subscription Delete Notification \n(Deleted, E2 Node ID, E2 Request ID, Cause) -end - -@enduml - -``` - -![Sequence diagram for E2 Subscription Audit procedure. Lifelines: xApp, Other xApp, Near-RT RIC platform, E2 Node. The procedure involves an audit request from xApp to Near-RT RIC, a confirmation from Near-RT RIC, and subsequent handling of the request either via an E2 interface transaction with the E2 Node or directly by the Near-RT RIC platform. The diagram includes various message exchanges, decision points (accept/reject), and timeout handling.](3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Other xApp - participant Near-RT RIC platform - participant E2 Node - - Note over Near-RT RIC platform: Near-RT RIC platform - - xApp->>Near-RT RIC platform: 1: (E2 related API) E2 Subscription Audit (Request, E2 Node ID, List of E2 Request ID) - Near-RT RIC platform-->>xApp: 2: Confirm that xApp had previously subscribed (i.e. record found for xApp ID) - Near-RT RIC platform-->>xApp: 3: Accept/Reject decision - - alt Near-RT RIC platform rejects - xApp->>Near-RT RIC platform: 4: (E2 related API) E2 Subscription Audit (Reject, E2 Node ID, List of E2 Request ID, Cause) - else Near-RT RIC platform accepts - alt Near-RT RIC initiates E2 interface transaction - Near-RT RIC platform->>E2 Node: 5: «E2» RIC SUBSCRIPTION AUDIT REQUEST (Audit flag, List of RIC Request ID) - alt E2 Node accepts audit request - E2 Node-->>Near-RT RIC platform: 6: «E2» RIC SUBSCRIPTION AUDIT RESPONSE (Confirmed, Unknown and/or Missing list of RIC Request ID) - Near-RT RIC platform-->>xApp: 7: (E2 related API) E2 Subscription Audit (Success, E2 Node ID, Confirmed, Unknown and/or Missing list of E2 Request ID) - else E2 Node rejects audit request - E2 Node-->>Near-RT RIC platform: 8: «E2» RIC SUBSCRIPTION AUDIT FAILURE - Near-RT RIC platform-->>xApp: 9: (E2 related API) E2 Subscription Audit (Failure, E2 Node ID, Cause) - else Near-RT detects E2AP timeout - Near-RT RIC platform-->>Near-RT RIC platform: 10a. E2AP time out - Near-RT RIC platform-->>xApp: 10b. (E2 related API) E2 Subscription Audit (Failure) - end - else Near-RT RIC responses without E2 interface transaction - alt Result is success - Near-RT RIC platform-->>xApp: 13: (E2 related API) E2 Subscription Audit (Success, E2 Node ID, Confirmed, Unknown and/or Missing list of E2 Request ID) - else Result is failure - Near-RT RIC platform-->>xApp: 14: (E2 related API) E2 Subscription Audit (Failure, E2 Node ID, Cause) - end - end - Near-RT RIC platform-->>Near-RT RIC platform: 11: Update the subscription records - Near-RT RIC platform-->>E2 Node: 12: «E2» RIC Subscription Delete procedure (RIC Request ID) - Near-RT RIC platform-->>xApp: 15a: (E2 related API) E2 Subscription Delete Notification (Deleted, E2 Node ID, E2 Request ID, Cause) - Near-RT RIC platform-->>Other xApp: 15b: (E2 related API) E2 Subscription Delete Notification (Deleted, E2 Node ID, E2 Request ID, Cause) - end - -``` - -Sequence diagram for E2 Subscription Audit procedure. Lifelines: xApp, Other xApp, Near-RT RIC platform, E2 Node. The procedure involves an audit request from xApp to Near-RT RIC, a confirmation from Near-RT RIC, and subsequent handling of the request either via an E2 interface transaction with the E2 Node or directly by the Near-RT RIC platform. The diagram includes various message exchanges, decision points (accept/reject), and timeout handling. - -Figure 9.3.2.5-1: E2 Subscription Audit procedure - -#### 9.3.2.6 E2 Query procedure - -The purpose of the E2 Query procedure in the Near-RT RIC is to ensure that only authorized xApp may initiate RIC Query Request messages issued by the Near-RT RIC over the E2 interface to the E2 Node. - -This procedure is based on the following assumptions: - -- xApp has been configured with a trusted xApp ID; -- Near-RT RIC platform may be configured to route E2 Query Request messages for a E2 node from xApp trigger directly towards an appropriate E2 interface; - -- Near-RT RIC platform ensures that only authorized xApp may send E2 Query Request messages to appropriate E2 interface; -- Near-RT RIC platform ensures that it systematically forwards any received RIC Query Response or RIC Query Failure to appropriate xApp. - -The procedure is initiated by an xApp using E2 Related API: E2 Query request to send a request of a RIC Query for an E2 Node. The following outcomes are possible: - -- Request successful following acceptance by Near-RT RIC platform and accepted by E2 Node and so an **E2 Related API: E2 Query** response (Success with outcome) is sent to xApp following corresponding E2 transaction; -- Request fails following acceptance by Near-RT RIC platform but is either rejected by E2 Node or corresponding E2AP timer expires prior to a response from E2 Node and so an **E2 Related API: E2 Query** response (Failure with cause) is sent to xApp following corresponding E2 interface transaction (i.e., Request contents is not compliant, E2AP timeout, etc.); -- Request rejected by Near-RT Platform and so an **E2 Related API: E2 Query** response (Reject) is sent to xApp. - -| Use Case Stage | Evolution / Specification | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | E2 Query procedure from xApp initiation to E2 Node and response. | -| Actors and Roles |
  • • xApp: Originator of E2 Query request;
  • • Near-RT RIC platform, with the following functionalities:
    • – E2 Termination.
  • • E2 Node: RIC Query procedure.
| -| Assumptions |
  • • For E2 Query procedures, Near-RT RIC platform may forward the xApp's query request directly to the E2 interface;
| -| Pre-conditions |
  • • E2 Node has active E2 interface to Near-RT RIC;
  • • Near-RT RIC has recovered complete list of active RAN Functions on E2 Node and informed initiating xApp;
  • • xApp has been authorized to send RIC Query requests for a specific scope (E2 Node list, RAN Function, etc.);
  • • Near-RT RIC platform has been configured to permit RIC Query requests from xApp.
| -| Begins when | xApp determines need to propose RIC Query procedure for a E2 Node and defines message contents (RAN Function ID, Query Header, Query Definition). | -| Step 1 (M) | xApp sends E2 related API: E2 Query request with message contents (RAN Function ID, Query Header, Query Definition) for an E2 Node. | -| Step 2 (M) | Near-RT RIC platform processes request. | -| | [ALT] Step 3 is executed if Near-RT RIC platform rejects proposed E2 Query message. | -| Step 3 (M) | E2 related API: E2 Query response (Reject with Cause) message is sent to xApp. | -| | [ELSE] Step 4-10 are executed if Near-RT RIC platform accepts proposed E2 Query message: | -| Step 4 (M) | Near-RT RIC platform selects appropriate E2 interface and assigns an appropriate RIC Request ID. | -| Step 5 (M) | Near-RT RIC platform sends RIC Query Request (RIC Request ID, contents) to E2 Node. | -| | [ALT] Steps 6-7 are executed if E2 Node accepts RIC Query Request: | -| Step 6 (M) | E2 Node responds with RIC Query Response | -| Step 7 (M) | Near-RT RIC platform sends E2 Related API: E2 Query response (Success with Outcome) to xApp. | -| | [ELSE] Steps 8-9 are executed if E2 Node rejects RIC Query Request: | -| Step 8 (M) | E2 Node responds with RIC Query Failure (with Cause). | -| Step 9 (M) | Near-RT RIC platform sends E2 Related API: E2 Query response (Failure with Cause) to xApp. | -| | [ELSE] Step 10 is executed if E2 Node fails to respond prior to E2AP timer expires | -| Step 10 (M) | Near-RT RIC platform E2AP timer expires and sends E2 Related API: E2 Query response (Failure with Cause) to xApp. | - -``` -@startuml -skin rose -``` - -``` - -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Participant xApp - Participant "Near-RT RIC platform" as plt -endbox - -Collections "E2 Node" as ran - -xApp -> plt: 1. (E2 related API) E2 Query (Request) - -plt -> plt: 2. Near-RT RIC platform processes request -alt Near-RT RIC platform rejects request - plt -> xApp: 3. (E2 related API) E2 Query (Reject) -else Near-RT RIC platform accepts request - - plt -> plt: 4: Select appropriate E2 interface and assigns RIC Request ID - plt -> ran: 5: <> RIC QUERY REQUEST - - alt E2 node accepts request - ran -> plt: 6: <> RIC QUERY RESPONSE - plt -> xApp: 7. (E2 related API) E2 Query (Success) - else E2 node rejects request - ran -> plt: 8: <> RIC QUERY FAILURE - plt -> xApp: 9. (E2 related API) E2 Query (Failure) - else Near-RT detects E2AP timeout - plt-> plt: 10a. E2AP time out - plt -> xApp: 10b. (E2 related API) E2 Query (Failure) - end -end -@enduml - -``` - -![Sequence diagram illustrating the E2 Query Procedure. Lifelines: xApp, Near-RT RIC platform, and E2 Node. The process involves an E2 Query request from xApp to the platform, which then sends a RIC QUERY REQUEST to the E2 Node. The E2 Node returns a response or failure, which the platform then relays to the xApp. Timeout handling is also shown.](3198cdf0dbe501c46fe0e4073c7d8451_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - participant E2 Node - - Note over xApp, Near-RT RIC platform: Near-RT RIC - xApp->>Near-RT RIC platform: 1. (E2 related API) E2 Query (Request) - Near-RT RIC platform->>Near-RT RIC platform: 2. Near-RT RIC platform processes request - alt Near-RT RIC platform rejects request - Near-RT RIC platform->>xApp: 3. (E2 related API) E2 Query (Reject) - else Near-RT RIC platform accepts request - Near-RT RIC platform->>Near-RT RIC platform: 4: Select appropriate E2 interface and assigns RIC Request ID - Near-RT RIC platform->>E2 Node: 5: <> RIC QUERY REQUEST - alt E2 node accepts request - E2 Node->>Near-RT RIC platform: 6: <> RIC QUERY RESPONSE - Near-RT RIC platform->>xApp: 7. (E2 related API) E2 Query (Success) - else E2 node rejects request - E2 Node->>Near-RT RIC platform: 8: <> RIC QUERY FAILURE - Near-RT RIC platform->>xApp: 9. (E2 related API) E2 Query (Failure) - else Near-RT detects E2AP timeout - Near-RT RIC platform->>Near-RT RIC platform: 10a. E2AP time out - Near-RT RIC platform->>xApp: 10b. (E2 related API) E2 Query (Failure) - end - end - -``` - -Sequence diagram illustrating the E2 Query Procedure. Lifelines: xApp, Near-RT RIC platform, and E2 Node. The process involves an E2 Query request from xApp to the platform, which then sends a RIC QUERY REQUEST to the E2 Node. The E2 Node returns a response or failure, which the platform then relays to the xApp. Timeout handling is also shown. - -Figure 9.3.2.6-1: E2 Query Procedure - -#### 9.3.2.7 E2 Subscription Modification procedure - -The purpose of the E2 Subscription Modification procedure in the Near-RT RIC is to ensure that only validated RIC Subscription Modification Request messages are issued by the Near-RT RIC over the E2 interface to the E2 Node are handled gracefully. - -This procedure is based on the following assumptions: - -- xApp may obtain guidance from Near-RT RIC Platform (i.e., conflict mitigation processing) to resolve potential conflicts and/or detect partial duplications prior to sending a E2 Subscription Modification Request (see clause 9.3.3.1); -- xApp has been configured with a trusted xApp ID; -- Near-RT RIC platform maintains all previous successful RIC Subscriptions towards the E2 Node listed in xApp's E2 Subscription request and is able to detect duplications and recover E2 Node response messages; -- Near-RT RIC platform may leverage its conflict mitigation functionality in managing E2 subscriptions (see clause 9.3.3.5); -- Near-RT RIC platform decides initiation of appropriate E2AP procedure(s), if needed, to fulfil the E2 Subscription request. -- E2 Request ID is used on E2-related APIs to identify an active RIC subscription. Near-RT Platform maintains the 1:1 mapping between E2 Request ID, used on E2 related APIs, and RIC Request ID, used on E2 interface. -- Near-RT RIC platform routes the subscription modification requests to an appropriate E2interface; -- Near-RT RIC platform maintains a mapping of active Subscriptions (identified on E2 interface by E2 Node ID and RIC Request ID) of validated xApps. Near-RT RIC platform uses the mapping when sending E2 INDICATION messages to the correct xApp or xApps. -- Near-RT RIC platform sends the E2 Subscription Modification response prior to sending any associated E2 Indication message to the xApp. - -The procedure initiated by an xApp uses **E2 Related API: E2 Subscription Modification** to request subscription modify for a specific E2 Node. The following outcomes are possible: - -- Request fails following rejection by Near-RT RIC platform and an **E2 Related API: E2 Subscription Modification** response (Reject) is sent to xApp without E2 interface transaction (i.e., xApp not previously associated with validated subscription); -- Request succeeds following acceptance by Near-RT RIC without initiating a corresponding E2 transaction; and an **E2 Related API: E2 Subscription Modification** response (Success) is sent to xApp; -- Request succeeds following acceptance by Near-RT RIC platform and accepted by E2 Node, and an **E2 Related API: E2 Subscription Modification** response (Success) is sent to xApp following corresponding E2 transaction; -- Request fails following acceptance by Near-RT RIC platform but is either rejected by E2 Node or corresponding E2AP timer expires prior to a response from E2 Node, and an **E2 Related API: E2 Subscription Modification** response (Failure) is sent to xApp following corresponding E2 interface transaction (i.e., RIC Request ID is not known by E2 Node, time out, etc.); - -| Use Case Stage | Evolution / Specification | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | E2 Subscription Modification procedure from xApp initiation to E2 Node and response. | -| Actors and Roles |
  • • xApp: Originator of E2 Subscription Modification request;
  • • Near-RT RIC platform, with the following functionalities:
    • – Database;
    • – xApp Subscription Management;
    • – Conflict Mitigation;
    • – E2 Termination.
  • • E2 Node: Handling RIC Subscription Modification procedure.
| - -| | | -|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Assumptions |
  • Near-RT RIC platform maintains the E2 subscription records;
  • Near-RT RIC platform has access to sufficient information to both detect a potential conflict and take a decision on an optimal mitigation solution;
  • Near-RT RIC platform may generate guidance for internal processes and/or xApp as an optional addition response to Guidance Request.
| -| Pre conditions |
  • E2 Node has active E2 interface to Near-RT RIC;
  • Near-RT RIC has recovered complete list of active RAN Functions on E2 Node and informed initiating xApp;
  • xApp has been authorized to issue E2 Subscription Modification API Requests;
  • xApp has been authorized to request guidance from Near-RT RIC platform;
  • Near-RT RIC platform has been configured to permit RIC Subscription Modification requests from xApp.
| -| Begins when | xApp determines need to request E2 Subscription Modification for a specific E2 Node ID and E2 Request ID. | -| Step 1 (O) | xApp can request optional E2 related API: E2 Guidance from Near-RT RIC platform (see clause 9.3.3.1 for details). | -| Step 2 (M) | xApp sends E2 related API: E2 Subscription Modification request for a specific E2 Node and E2 request ID. | -| Step 3 (M) | Near-RT RIC platform, after optional conflict mitigation processing (see clause 9.3.3.5 for details), accepts or rejects proposal from xApp for specific E2 Node. | -| | [ALT] Step 4 is executed if Near-RT RIC platform rejects the proposal: | -| Step 4 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription Modification response to xApp (Reject with Cause for specific E2 Node). | -| | [ELSE] Steps 5-17 are executed if Near-RT RIC platform accepts the proposal: | -| Step 5 (M) | Near-RT RIC platform checks the subscription records to determine whether or not xApp proposing Subscription Modification is the only associated xApp. | -| | [ALT] Steps 6-12 are executed if the xApp proposing Subscription Modification is the only xApp associated with the subscription (i.e., a given RIC Request ID): | -| Step 6 (M) | Near-RT RIC platform selects appropriate E2 interface and sends RIC Subscription Modification Request (RIC Request ID) to E2 Node. | -| | [ALT] Steps 7-9 are executed if E2 Node accepts Subscription Modification: | -| Step 7 (M) | E2 Node responds with RIC Subscription Modification Response . | -| Step 8 (M) | Near-RT RIC platform updates the subscription records, and modify the distribution list(s) associated with the E2 Node ID and the RIC Request ID. | -| Step 9 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription Modification response to xApp (Success). | -| | [ELSE] Steps 10-11 are executed if E2 Node rejects Subscription Modification: | -| Step 10 (M) | E2 Node responds with RIC Subscription Modification Failure (with Cause). | -| Step 11 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription Modification response to xApp (Failure with Cause). | -| | [ELSE] Step 12 is executed if E2 Node fails to respond prior to E2AP timer expires | -| Step 12 (M) | Near-RT RIC platform E2AP timer expires and sends E2 related API: E2 Subscription Modification response (Failure with Cause) to xApp. | -| | [ELSE] Steps 13-17 are executed if the xApp proposing Subscription Modification is one of a number of xApp associated with the subscription (i.e., a given RIC Request ID): | -| | [ALT] Steps 13-14 executed if the proposal can be fulfilled with existing subscription(s) (i.e., one or more records found for E2 Node ID with Subscription matching the same contents): | -| Step 13 (M) | Near-RT RIC platform updates the subscription records. For each Action in subscription corresponding to an Indication message, Near-RT RIC platform adds xApp ID to distribution list associated with E2 Node ID, RIC Request ID and Action ID. | -| Step 14 (M) | xApp Subscription Management sends E2 Related API: E2 Subscription Modification response to xApp (Success, E2 Node ID, corresponding E2 Request ID(s) and E2 Action ID(s)). | -| | [ELSE] Steps 15-17 are executed if the subscription proposed by xApp necessitates E2AP procedure(s) (i.e., no record found for E2 Node ID with Subscription matching the same contents): | -| Step 15 (M) | Near-RT RIC platform selects appropriate E2 interface and initiates appropriate E2AP procedure(s) to E2 Node. | - -| | | -|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | [ALT] Step 16 is executed if the E2AP procedure(s) in Step 15 succeeds: | -| Step 16 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription Modification response to xApp (Success, E2 Node ID, corresponding E2 Request ID(s) and E2 Action ID(s)). | -| | [ELSE] Step 17 is executed if the E2AP procedure(s) in Step 15 fails: | -| Step 17 (M) | Near-RT RIC platform sends E2 related API: E2 Subscription Modification response to xApp (Failure with Cause, E2 Node ID). | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid - -box "Near-RT RIC platform" - Collections "xApp" as xApp - participant "Near-RT RIC platform" as plt -endbox -Collections "E2 Node" as ran - -xApp -> plt: 1: (E2 related API) Guidance \n(Request/Response) -xApp -> plt: 2: (E2 related API) E2 Subscription Modification \n(Request, E2 Node ID, E2 Request ID) -plt -> plt: 3: Confirm that xApp had previously subscribed \n(i.e. record found for xApp ID) - -Alt Near-RT RIC platform rejects - plt -> xApp: 4: (E2 related API) E2 Subscription Modification \n(Reject, E2 Node ID, E2 Request ID, Cause) -Else Near-RT RIC platform accepts - plt -> plt: 5: Count valid records - - alt Single xApp record - plt -> ran: 6: <> RIC SUBSCRIPTION MODIFICATION REQUEST - alt E2 Node accepts modification request - ran -> plt: 7: <> RIC SUBSCRIPTION MODIFICATION RESPONSE - plt -> plt: 8: Update the subscription records, \nand modify the distribution list - - plt-> xApp: 9: (E2 related API) E2 Subscription Modification \n(Success, E2 Node ID, E2 Request ID) - else E2 Node rejects modification request - ran -> plt: 10: <> RIC SUBSCRIPTION MODIFICATION FAILURE - plt -> xApp: 11: (E2 related API) E2 Subscription Modification \n(Failure, E2 Node ID, E2 Request ID, Cause) - else Near-RT detects E2AP timeout - plt->plt: 12a. E2AP time out - plt -> xApp: 12b. (E2 related API) E2 Subscription Modification \n(Failure, E2 Node ID, E2 Request ID, Cause) - End - else Multiple xApp records - alt Existing subscription(s) reused - plt -> plt: 13: Update the subscription records, \nand modify the xApp from the distribution list - plt -> xApp: 14: (E2 related API) E2 Subscription Modification \n(Success, E2 Node ID, E2 Request ID) - else E2AP procedure(s) need - plt <--> ran: 15: <> RIC Subscription procedure - alt E2AP procedure(s) succeeds - plt -> xApp: 16: (E2 related API) E2 Subscription Modification \n(Success, E2 Node ID, E2 Request ID) - else - plt -> xApp: 17: (E2 related API) E2 Subscription Modification \n(Failure, E2 Node ID, E2 Request ID, Cause) - end - end - end -end - -``` - -end -@enduml - -![Sequence diagram for E2 Subscription Modification procedure. Lifelines: xApp, Near-RT RIC platform, E2 Node. The diagram shows the interaction between an xApp and the Near-RT RIC platform to modify an E2 subscription, with various success, failure, and timeout scenarios.](dbd4bab54b57e8d1abf80e3de6471130_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - participant E2 Node - - Note left of xApp: end @enduml - - xApp->>Near-RT RIC platform: 1: (E2 related API) Guidance (Request/Response) - xApp->>Near-RT RIC platform: 2: (E2 related API) E2 Subscription Modification (Request, E2 Node ID, E2 Request ID) - Near-RT RIC platform-->>xApp: 3: Confirm that xApp had previously subscribed (i.e. record found for xApp ID) - - alt Near-RT RIC platform rejects - Near-RT RIC platform-->>xApp: 4: (E2 related API) E2 Subscription Modification (Reject, E2 Node ID, E2 Request ID, Cause) - else Near-RT RIC platform accepts - Near-RT RIC platform-->>xApp: 5: Count valid records - - alt Single xApp record - Near-RT RIC platform->>E2 Node: 6: <> RIC SUBSCRIPTION MODIFICATION REQUEST - - alt E2 Node accepts modification request - E2 Node-->>Near-RT RIC platform: 7: <> RIC SUBSCRIPTION MODIFICATION RESPONSE - E2 Node-->>Near-RT RIC platform: 8: Update the subscription records, and modify the distribution list - Near-RT RIC platform-->>xApp: 9: (E2 related API) E2 Subscription Modification (Success, E2 Node ID, E2 Request ID) - else E2 Node rejects modification request - E2 Node-->>Near-RT RIC platform: 10: <> RIC SUBSCRIPTION MODIFICATION FAILURE - Near-RT RIC platform-->>xApp: 11: (E2 related API) E2 Subscription Modification (Failure, E2 Node ID, E2 Request ID, Cause) - else Near-RT detects E2AP timeout - Near-RT RIC platform-->>xApp: 12a: E2AP time out - Near-RT RIC platform-->>xApp: 12b: (E2 related API) E2 Subscription Modification (Failure, E2 Node ID, E2 Request ID, Cause) - end - else Multiple xApp records - alt Existing subscription(s) reused - Near-RT RIC platform-->>xApp: 13: Update the subscription records, and modify the xApp from the distribution list - Near-RT RIC platform-->>xApp: 14: (E2 related API) E2 Subscription Modification (Success, E2 Node ID, E2 Request ID) - else E2AP procedure(s) need - Near-RT RIC platform->>E2 Node: 15: <> RIC Subscription procedure - - alt E2AP procedure(s) succeeds - Near-RT RIC platform-->>xApp: 16: (E2 related API) E2 Subscription Modification (Success, E2 Node ID, E2 Request ID) - Near-RT RIC platform-->>xApp: 17: (E2 related API) E2 Subscription Modification (Failure, E2 Node ID, E2 Request ID, Cause) - end - end - end - end - -``` - -Sequence diagram for E2 Subscription Modification procedure. Lifelines: xApp, Near-RT RIC platform, E2 Node. The diagram shows the interaction between an xApp and the Near-RT RIC platform to modify an E2 subscription, with various success, failure, and timeout scenarios. - -Figure 9.3.2.7-1: E2 Subscription Modification procedure - -### 9.3.3 E2 Conflict Mitigation related procedures - -#### 9.3.3.1 E2 Guidance procedure - -The purpose of the xApp initiated E2 Guidance request/response API procedure in the Near-RT RIC is to allow authorized xApp to obtain guidance from the Near-RT RIC platform (with the conflict mitigation functionality) prior to initiating an action. - -Guidance from Near-RT RIC platform may include: - -- Indication on whether or not the xApp proposed E2 Related API message or series of messages may result in a conflict with E2 related API messages from other xApps; -- Recommendations on how the proposed E2 Related message or series of messages should be modified to avoid conflict; -- Modification of previous guidance to other xApps and/or Near-RT RIC platform internal processes; -- Recommendations on how the proposed E2 Related message or series of messages should be modified to resolve an ongoing conflict. - -This procedure is based on the following assumptions: - -- xApp may use E2 Related API to obtain guidance from Near-RT RIC platform to resolve potential conflicts prior to initiating a RIC function procedure; -- xApp may use Near-RT RIC platform response in a subsequent procedure (i.e., for a RIC Functional Procedure). - -This procedure is initiated by an xApp using **E2 Related API: E2 Guidance** request. The following outcomes are possible: - -- Near-RT RIC Platform provides guidance to requesting xApp using E2 Related API: E2 Guidance response; -- Near-RT RIC Platform provides modified guidance to another xApp and/or its internal processes; -- Near-RT RIC Platform may trigger a conflict detection, avoidance, or resolution process after receiving a guidance request from an xApp. - -| Use Case Stage | Evolution / Specification | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp initiation of Conflict Mitigation guidance. | -| Actors and Roles |
  • • xApp: Originator of Conflict Mitigation guidance request. May also provide support in conflict mitigation. see clause 9.3.3.6;
  • • Other xApp(s): One or more other conflicting xApps identified by Near-RT RIC platform as being in potential conflict with originator xApp. May also provide support in conflict mitigation. see clause 9.3.3.6;
  • • Helper xApp: May provide support in conflict mitigation processing. see clause 9.3.3.6;
  • • Near-RT RIC platform, with the following functionalities:
    • – Database;
    • – Conflict mitigation.
| -| Assumptions |
  • • Near-RT RIC platform has access to sufficient information to both detect a potential conflict and take a decision on an optimal mitigation solution;
  • • Near-RT RIC platform may initiate guidance towards other xApp as an optional addition response to Guidance Request;
  • • Near-RT RIC may trigger a conflict detection, avoidance, or resolution process after receiving a guidance request from an xApp. see clause 9.3.3.6;
  • • Near-RT RIC may seek conflict mitigation support from xApps.
| -| Pre-conditions |
  • • xApp has been authorized to request guidance from Near-RT RIC platform for conflict mitigation;
  • • xApp has been assigned xApp ID.
| -| Begins when | xApp determines need to request guidance from Near-RT RIC platform for conflict mitigation. | -| Step 1 (M) | xApp sends E2 Related API E2 Guidance Request to Near-RT RIC platform. | -| Step 2 (M) | Near-RT RIC platform processes guidance request and collects related information. | -| | [ALT] Step 3 is executed if Near-RT RIC platform seeks conflict mitigation support from helper and conflicting xApps. | -| Step 3 (M) | Procedure defined in clause 9.3.3.6.1. | -| | [Else] Step 4 is executed if Near-RT RIC platform performs conflict avoidance which consists of an iterative negotiation process involving the conflicting xApps. | - -| | | -|------------|-------------------------------------------------------------------------------------------------------------------| -| Step 4 (M) | Procedure defined in clause 9.3.3.6.2. | -| | [Else] Step 5 is executed if Near-RT RIC platform performs all conflict mitigation related processing internally. | -| Step 5 (M) | Near-RT RIC platform performs conflict mitigation. | -| Step 6 (O) | Near-RT RIC platform may signal or update guidance to internal processes. | -| Step 7 (O) | Near-RT RIC platform may signal guidance to other conflicting xApps (see Clause 9.3.3.5) | -| Step 8 (M) | Near-RT RIC platform signal guidances to the requesting xApp using E2 Related API E2 Guidance response . | -| Ends with | xApp continues processing using guidance response. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid - -Collections "Other xApp(s)" as xApp -participant "xApp" as xApp2 -participant "hApp" as hApp -Participant plt as "Near-RT RIC platform" - -xApp2 -> plt: 1: (E2 related API) E2 Guidance (Request) -plt -> plt: 2: process guidance request -Alt case 1: conflict mitigation processing with xApp support - note over xApp, plt: 3: Conflict Mitigation Support: Processing and Information procedures -Else case 2 : New conflict avoidance negotiation required - note over xApp, plt: 4: Conflict Mitigation Support: Avoidance Negotiation procedures -Else case 3: platform performs all conflict mitigation related processing internally - plt->plt: 5: conflict mitigation processing -end - -plt --> plt: 6: Guidance to internal processes -xApp <-- plt: 7: (E2 related API) E2 Guidance (Modification) -plt -> xApp2: 8: (E2 related API) E2 Guidance (Response) -@enduml - -``` - -![Sequence diagram showing the xApp initiated E2 guidance request/response procedure. Lifelines: Other xApp(s), xApp, hApp, and Near-RT RIC platform. The sequence starts with xApp sending a request to the platform. The platform processes it and enters an 'alt' block with three cases: 1) conflict mitigation with xApp support, 2) new conflict avoidance negotiation, or 3) internal processing. After the alt block, the platform sends guidance to internal processes, a modification to xApp, and a response back to xApp. Other xApp(s) receive guidance in case 1.](18d7d8de298d79e7bc87af5217f11203_img.jpg) - -``` - -sequenceDiagram - participant Other xApp(s) - participant xApp - participant hApp - participant Near-RT RIC platform - - Note left of Other xApp(s): Collections "Other xApp(s)" as xApp - xApp->>Near-RT RIC platform: 1: (E2 related API) E2 Guidance (Request) - Near-RT RIC platform->>Near-RT RIC platform: 2: process guidance request - alt case 1: conflict mitigation processing with xApp support - Note over xApp, Near-RT RIC platform: 3: Conflict Mitigation Support: Processing and Information procedures - Other xApp(s)->>Other xApp(s): 6: Guidance to internal processes - else case 2 : New conflict avoidance negotiation required - Note over xApp, Near-RT RIC platform: 4: Conflict Mitigation Support: Avoidance Negotiation procedures - else case 3: platform performs all conflict mitigation related processing internally - Near-RT RIC platform->>Near-RT RIC platform: 5: conflict mitigation processing - end - Near-RT RIC platform-->>Near-RT RIC platform: 6: Guidance to internal processes - xApp <-->>Near-RT RIC platform: 7: (E2 related API) E2 Guidance (Modification) - Near-RT RIC platform->>xApp: 8: (E2 related API) E2 Guidance (Response) - -``` - -Sequence diagram showing the xApp initiated E2 guidance request/response procedure. Lifelines: Other xApp(s), xApp, hApp, and Near-RT RIC platform. The sequence starts with xApp sending a request to the platform. The platform processes it and enters an 'alt' block with three cases: 1) conflict mitigation with xApp support, 2) new conflict avoidance negotiation, or 3) internal processing. After the alt block, the platform sends guidance to internal processes, a modification to xApp, and a response back to xApp. Other xApp(s) receive guidance in case 1. - -Figure 9.3.3.1-1: xApp initiated E2 guidance request/response procedure - -9.3.3.2 Void - -9.3.3.3 Void - -9.3.3.4 Void - -#### 9.3.3.5 E2 Guidance modification procedure - -The purpose of the E2 Guidance modification procedure is to allow Near-RT RIC platform to signal a modified guidance to the xApp, which can be triggered by the Near-RT RIC platform’s internal process (e.g., xApp subscription management), or by a message from the other xApps or external interfaces. - -The guidance may also be used for Near-RT RIC platform internal purposes. - -| Use Case Stage | Evolution / Specification | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | Near-RT RIC platform indicates guidance to an xApp without request from the xApp. | -| Actors and Roles |
  • xApp
  • other xApp
  • Near-RT RIC platform, with the following functionalities:
    • Database
    • Conflict mitigation
  • External entity (e.g., E2 Node or SMO)
| -| Assumptions |
  • Near-RT RIC platform is capable of collecting related information, and generating proper guidance for an xApp.
  • Near-RT RIC may trigger a conflict detection, avoidance, or resolution process to compute guidance.
| -| Pre-conditions |
  • Message from xApp, message from external interfaces, or Near-RT RIC platform’s internal process triggers conflict mitigation in Near-RT RIC platform.
| -| Step 1 (M) | Near-RT RIC platform processes the triggering event and determines need for conflict mitigation. | -| | [ALT] Step 2 is executed if Near-RT RIC platform seeks conflict mitigation support from helper and conflicting xApps. | -| Step 2 (M) | Procedure defined in clause 9.3.3.6.1. | -| | [ELSE] Step 3 is executed if Near-RT RIC platform performs conflict avoidance which consists of an iterative negotiation process involving the conflicting xApps. | -| Step 3 (M) | Procedure defined in clause 9.3.3.6.2. | -| | [ELSE] Step 4 is executed if Near-RT RIC platform performs all conflict mitigation related processing internally. | -| Step 4 (M) | Near-RT RIC platform performs conflict mitigation. | -| Step 5 (O) | Near-RT RIC platform may provide guidance to the affected xApp using E2 Guidance modification message. | -| Step 6 (O) | Near-RT RIC platform may also use the guidance for internal purposes. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid - -Participant xApp -Collections "Other xApp(s)" as OtherxApp -Participant "Near-RT RIC platform" as plt - -plt->plt: 1: process triggering event -Alt case 1: conflict mitigation processing with xApp support -note over xApp, plt: 2: Conflict Mitigation Support: Processing and Information procedures - -``` - -``` - -Else case 2 : New xApp negotiation for conflict avoidance agreement -note over xApp, plt: 3: Conflict Mitigation Support: Avoidance Negotiation procedures -Else case 3: platform performs all conflict mitigation related processing internally -plt->plt: 4: conflict mitigation processing -end - -plt --> xApp: 5: E2 Guidance (Modification) -plt --> plt: 6: Guidance for internal purposes - -@enduml - -``` - -![Sequence diagram titled 'Figure 9.3.3.5-1 E2 Guidance Modification Procedure'. It shows interactions between xApp, Other xApp(s), and Near-RT RIC platform. The process starts with the platform processing a triggering event. An 'alt' block titled '[case 1: conflict mitigation processing with xApp support]' contains three sub-cases: 2: Conflict Mitigation Support: Processing and Information procedures; 3: Conflict Mitigation Support: Avoidance Negotiation procedures; and case 3: platform performs all conflict mitigation related processing internally. After the alt block, the platform sends '5: E2 Guidance (Modification)' to the xApp and '6: Guidance for internal purposes' to itself.](49fe8fe978c0f7e73112d231feb377eb_img.jpg) - -Sequence diagram titled 'Figure 9.3.3.5-1 E2 Guidance Modification Procedure'. It shows interactions between xApp, Other xApp(s), and Near-RT RIC platform. The process starts with the platform processing a triggering event. An 'alt' block titled '[case 1: conflict mitigation processing with xApp support]' contains three sub-cases: 2: Conflict Mitigation Support: Processing and Information procedures; 3: Conflict Mitigation Support: Avoidance Negotiation procedures; and case 3: platform performs all conflict mitigation related processing internally. After the alt block, the platform sends '5: E2 Guidance (Modification)' to the xApp and '6: Guidance for internal purposes' to itself. - -Figure 9.3.3.5-1 E2 Guidance Modification Procedure - -#### 9.3.3.6 E2 Conflict Mitigation Support procedures - -##### 9.3.3.6.1 E2 Conflict Mitigation Processing and Information - -The purpose of the Near-RT RIC platform initiated E2 Conflict Mitigation Processing request/response and E2 Conflict Mitigation Information request/response API procedures in the Near-RT RIC is to allow authorized helper and conflicting xApps, respectively, to provide support (in terms of processing and additional information) to Near-RT RIC platform during conflict detection, conflict avoidance, and conflict resolution. - -Processing or Information support from helper or conflicting xApps may consist of the following: - -- Helper xApp: E2SM processing related to conflict detection, avoidance, and resolution. This may include a helper xApp providing the platform with support for data analysis, optimization, or other E2SM related computations; -- Helper xApp: Processing support may include a helper xApp collecting and processing relevant data from E2 Nodes or Near-RT RIC platform; -- Conflicting xApps: Upon request, conflicting xApps may provide the platform with additional E2SM related information support (e.g., RIC services, RAN parameters or RAN KPIs of interest to xApps and preferences regarding these). - -This procedure is based on the following assumptions: - -- Whether an xApp supports a certain type of support service listed above (processing or information) is assumed to be known to the platform before requesting the support; - -- The Near-RT RIC platform can request processing or information support service from an xApp if and only if the xApp supports it. Furthermore, the decision to request this support is Near-RT RIC platform implementation specific. - -This procedure is initiated by Near-RT RIC platform using either **E2 Related API: E2 Conflict Mitigation Processing** or **E2 Related API: E2 Conflict Mitigation Information** request. The xApps provide the required support using **E2 Related API: E2 Conflict Mitigation Processing** response or **E2 Related API: E2 Conflict Mitigation Information** response. - -The procedure for E2 Conflict Mitigation Processing or Information support for conflict detection, avoidance, or resolution is provided below: - -| Use Case Stage | Evolution / Specification | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | Near-RT RIC platform initiated Conflict mitigation (detection, avoidance or resolution) using E2 Conflict Mitigation Processing or Information support. | -| Actors and Roles |
  • Conflicting or potentially conflicting xApps, as producers of E2 Conflict Mitigation Information support (towards Near-RT RIC platform) related to detection, avoidance, or resolution of conflicts. This support may comprise providing the platform with E2SM related information relevant to a conflict.
  • Helper xApp as producer of E2 Conflict Mitigation Processing support (towards Near-RT RIC platform) which may comprise the following:
    • – E2AP and E2SM processing support to the platform;
    • – Data analysis, optimization, and data collection from platform or E2 Nodes;
  • Near-RT RIC platform as consumer of E2 Conflict Mitigation support service,
| -| Assumptions |
  • Near-RT RIC platform has access to sufficient information to detect a potential conflict;
  • xApps can provide support for conflict mitigation to the Near-RT RIC platform;
  • Near-RT RIC platform has access to sufficient information to determine which xApps offer which type of conflict mitigation support.
| -| Pre-conditions |
  • A previous event (e.g., xApp initiated E2 Guidance Request or E2 Subscription/Control Request) has triggered conflict mitigation in the Near-RT RIC Platform.
  • In response, the platform has triggered one of the conflict detection, avoidance or resolution processes.
| -| Begins when | A triggering event as mentioned in the pre-conditions. | -| Step 1 (M) | Near-RT RIC platform detects potential conflict. | -| Step 2 (M) | Near-RT RIC platform identifies potentially conflicting xApps and triggers conflict detection, avoidance, or resolution | -| Step 3 (O) | Near-RT RIC platform sends E2 Conflict Mitigation Information request to xApps. | -| Step 4 (O) | xApps process the request and generate supporting information. | -| Step 5 (O) | xApps send E2 Conflict Mitigation Information response to Near-RT RIC platform. | -| | [ALT] Steps 6-8 are executed if the Near-RT RIC platform opts to use helper xApp for E2SM processing and intelligence. | -| Step 6 (M) | Near-RT RIC platform sends E2 Conflict Mitigation Processing request to the helper xApp. | -| Step 7A (O) | The helper xApp may gather additional information from the platform (e.g., any available dependency information between RAN control parameters and KPIs) or E2 Nodes (e.g., KPIs) using appropriate procedures. | -| Step 7B (M) | Helper xApp processes the request. | -| Step 8 (M) | Helper xApp sends E2 Conflict Mitigation Processing response to Near-RT RIC platform. | -| | [ELSE] Step 9 is executed if Near-RT RIC platform does not opt for support from a helper xApp. | -| Step 9 (M) | Near-RT RIC platform performs the required E2SM processing itself. | -| Step 10 (M) | Near-RT RIC platform generates the information/result related to detection, avoidance, or resolution. | -| Ends with | Conflict detection, avoidance, or resolution. | - -``` -@startuml -skin rose -skinparam ParticipantPadding 30 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid -``` - -``` -Collections "conflicting xApps" as xApps -Participant "helper xApp" as hApp -Participant plt as "Near-RT RIC platform" -``` - -``` - -plt -> plt: 1: Conflict mitigation processing (potential conflict detection) -plt -> plt: 2: Conflict mitigation processing (identify conflicting xApps, trigger detection, avoidance or resolution) - -plt --> xApps: 3: (E2 related API) E2 Conflict Mitigation Information (Request) -xApps --> xApps: 4: Support processing -xApps --> plt: 5: (E2 related API) E2 Conflict Mitigation Information (Response) - -alt Platform opts to use helper xApp for E2SM processing & intelligence -plt -> hApp: 6: (E2 related API) E2 Conflict Mitigation Processing (Request) -plt <--> hApp: 7A: Collect related information (Database/E2 Nodes) -hApp -> hApp: 7B: Processing processing -hApp -> plt: 8: (E2 related API) E2 Conflict Mitigation Processing (Response) -else the platform does not opt for support from helper xApp -plt -> plt: 9: Conflict mitigation processing (E2SM processing) -end -plt -> plt: 10: Conflict mitigation processing (record detection/avoidance/resolution result) -@enduml - -``` - -![Sequence diagram showing E2 Conflict Mitigation Processing with xApp support. Lifelines: conflicting xApps, helper xApp, and Near-RT RIC platform. The process involves internal platform steps, followed by a request to xApps, a response, and then an alt block for helper xApp support. If supported, the helper xApp collects info and processes it. If not, the platform processes it itself. Finally, a result is recorded.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) - -``` - -sequenceDiagram - participant plt as Near-RT RIC platform - participant xApps as conflicting xApps - participant hApp as helper xApp - - Note left of plt: 1: Conflict mitigation processing (potential conflict detection) - Note left of plt: 2: Conflict mitigation processing (identify conflicting xApps, trigger detection, avoidance or resolution) - - plt->>xApps: 3: (E2 related API) E2 Conflict Mitigation Information (Request) - Note right of xApps: 4: Support processing - xApps-->>plt: 5: (E2 related API) E2 Conflict Mitigation Information (Response) - - alt Platform opts to use helper xApp for E2SM processing & intelligence - Note left of plt: 6: (E2 related API) E2 Conflict Mitigation Processing (Request) - Note left of plt: 7A: Collect related information (Database/E2 Nodes) - Note right of hApp: 7B: Processing processing - hApp-->>plt: 8: (E2 related API) E2 Conflict Mitigation Processing (Response) - else the platform does not opt for support from helper xApp - Note left of plt: 9: Conflict mitigation processing (E2SM processing) - end - - Note left of plt: 10: Conflict mitigation processing (record detection/avoidance/resolution result) - -``` - -Sequence diagram showing E2 Conflict Mitigation Processing with xApp support. Lifelines: conflicting xApps, helper xApp, and Near-RT RIC platform. The process involves internal platform steps, followed by a request to xApps, a response, and then an alt block for helper xApp support. If supported, the helper xApp collects info and processes it. If not, the platform processes it itself. Finally, a result is recorded. - -Figure 9.3.3.6-1: E2 Conflict Mitigation Processing with xApp support - -##### 9.3.3.6.2 E2 Conflict Avoidance Negotiation - -The purpose of the E2 Conflict Avoidance Negotiation procedure is to allow Near-RT RIC platform to obtain a conflict avoidance negotiated agreement between xApps that determines, e.g., a mutually exclusive subset of the E2 Node supported RAN Function services. The procedure consists of request, response and negotiation (notify) type messages. - -The procedure is initiated by the Near-RT RIC platform **E2 Related API: E2 Conflict Avoidance Negotiation** request. The following options are considered: - -- Direct negotiation: If possible, xApps, after obtaining the request message from the Near-RT RIC platform may engage in direct negotiation using **E2 Related API: E2 Conflict Avoidance Negotiation Indication** messages to obtain, e.g., a mutually exclusive subset of the E2 Node supported RAN Function services. In each step of the negotiation, an xApp can either accept an agreement or seek further negotiation. -- Indirect negotiation: In this case, the platform can facilitate indirect negotiation between xApps using **E2 Related API: E2 Conflict Avoidance Negotiation notify** messages. The platform acts as a message relay between xApps. - -After an agreement is reached or M number of negotiation attempts are exhausted, the xApps shall respond to the Near-RT RIC platform to indicate success or failure in **Related API: E2 Conflict Avoidance Negotiation** response messages, along with any agreements. The platform may save the outcome of the negotiation (e.g., using a negotiation key) and use it for future reference during Conflict Mitigation (i.e., E2 Guidance or E2 Guidance modification). - -| Use Case Stage | Evolution / Specification | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | Near-RT RIC platform facilitates conflict avoidance negotiation between xApps. | -| Actors and Roles |
  • xApps perform conflict avoidance negotiation
  • Near-RT RIC platform as facilitator of conflict avoidance negotiation
| -| Assumptions |
  • xApp support required conflict avoidance functionalities.
| -| Pre-conditions |
  • Near-RT RIC determines the need for conflict avoidance negotiation between xApps.
  • Near-RT RIC determines the maximum number of negotiation offers #M
| -| Step 1 (M) | Near-RT RIC platform prepares xApp negotiation. | -| Step 2A-2B (M) | Near-RT RIC platform sends E2 Related API: E2 Conflict Avoidance Negotiation request to the identified xApps. This message may contain information about potentially conflicting E2SM level overlaps (e.g., overlaps in RAN Function services) and the list of xApps with corresponding addresses to be used for communication. | -| | [Loop] Step 3 is looped while an agreement is not reached AND number of negotiation offers is less than #M | -| | [ALT] Steps 3A-3D are performed if Option 1: direct negotiation is performed: | -| Step 3A (M) | xApps send E2 Related API: E2 Conflict Avoidance Negotiation (notify) messages to other xApps containing a negotiation offer or agreement to previously received offer | -| Step 3B (M) | xApp checks if agreement is reached | -| Step 3C (M) | xApp sends E2 Related API: E2 Conflict Avoidance Negotiation (notify) messages to other xApps with its negotiation offer or agreement to previously received offer | -| Step 3D (M) | Same as Step 3B | -| | [ELSE] Steps 3E-3J are performed If Option 2: indirect negotiation is performed: | -| Step 3E (M) | xApps send E2 Related API: E2 Conflict Avoidance Negotiation (notify) messages to the platform containing a negotiation offer or agreement to previously received offer | -| Step 3F (M) | Near-RT RIC platform forwards the message received in Step 3E to the other negotiating xApp(s). | -| Step 3G (M) | xApp checks if agreement is reached | -| Step 3H (M) | xApps send E2 Related API: E2 Conflict Avoidance Negotiation (notify) messages to the platform containing a negotiation offer or agreement to previously received offer | -| Step 3I (M) | Near-RT RIC platform forwards the message received in Step 3H to the other negotiating xApp(s). | -| Step 3J (M) | xApp checks if agreement is reached | -| Step 4A-B (M) | xApps send E2 Related API: E2 Conflict Avoidance Negotiation response containing the results of the negotiation process | -| Step 5A (M) | The Near-RT RIC platform compiles the agreement by combining information obtained in Step 4 from all xApps. Note: The final agreement may consist of an exclusive subset of the E2 Node supported RAN Function services available to each xApp. | -| Step 5B (O) | The Near-RT RIC platform records agreements (e.g., using a negotiation key) for future referencing. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid - -participant "xApp" as xApp2 -participant "Other xApp(s)" as xApp -Participant plt as "Near-RT RIC platform" - -plt->plt: 1: Prepare xApp negotiation -plt->xApp: 2A: (E2 related API) Conflict avoidance negotiation (request) -plt->xApp2: 2B: (E2 related API) Conflict avoidance negotiation (request) -loop While no agreement AND less than M negotiations -alt Option 1: Direct avoidance negotiation - -``` - -``` - -xApp -> xApp2: 3A: (E2 related API) Conflict avoidance negotiation indication (notify, -offer/agreement) -xApp2->xApp2: 3B: check agreement -xApp2->xApp: 3C: (E2 related API) Conflict avoidance negotiation indication (notify, -offer/agreement) -xApp->xApp: 3D: check agreement -else Option 2: Indirect avoidance negotiation -xApp->plt: 3E: (E2 related API) Conflict avoidance negotiation indication (notify, -offer/agreement) -plt->plt: relay message -plt->xApp2: 3F: (E2 related API) Conflict avoidance negotiation indication (notify, -offer/agreement) -xApp2->xApp2: 3G: check agreement -xApp2->plt: 3H: (E2 related API) Conflict avoidance negotiation indication (notify, -offer/agreement) -plt->plt: relay message -plt->xApp: 3I: (E2 related API) Conflict avoidance negotiation indication (notify, -offer/agreement) -xApp->xApp: 3J: check agreement -end -end loop -xApp->plt: 4A: (E2 related API) Conflict avoidance negotiation (response) -xApp2->plt: 4B: (E2 related API) Conflict avoidance negotiation (response) -plt->plt: 5A: Compile agreement -plt-->plt: 5B: Record agreement (negotiation key) -@enduml - -``` - -![Sequence diagram for E2 Conflict Avoidance Negotiation. Lifelines: xApp, Other xApp(s), Near-RT RIC platform. The process starts with the Near-RT RIC platform preparing negotiation, followed by a request from Other xApp(s) to xApp. A loop 'While no agreement AND less than M negotiations' contains two options: Option 1 (Direct avoidance negotiation) and Option 2 (Indirect avoidance negotiation). Option 1 involves a series of indications and checks between xApp and Other xApp(s). Option 2 involves indications and relay messages between xApp, Other xApp(s), and the Near-RT RIC platform. After the loop, responses are sent from xApp and Other xApp(s) to the platform, which then compiles and records the agreement.](3750b0149a6380885998ab3ca6a8787c_img.jpg) - -Sequence diagram for E2 Conflict Avoidance Negotiation. Lifelines: xApp, Other xApp(s), Near-RT RIC platform. The process starts with the Near-RT RIC platform preparing negotiation, followed by a request from Other xApp(s) to xApp. A loop 'While no agreement AND less than M negotiations' contains two options: Option 1 (Direct avoidance negotiation) and Option 2 (Indirect avoidance negotiation). Option 1 involves a series of indications and checks between xApp and Other xApp(s). Option 2 involves indications and relay messages between xApp, Other xApp(s), and the Near-RT RIC platform. After the loop, responses are sent from xApp and Other xApp(s) to the platform, which then compiles and records the agreement. - -Figure 9.3.3.6.2-1 E2 Conflict Avoidance Negotiation - -## 9.4 Management API Procedures - -### 9.4.1 xApp Registration procedure - -This procedure registers the xApp to the Near-RT RIC platform so that it can be managed by the SMO via the Near-RT RIC platform. When the xApp is deployed, it will register itself as a managed application to the Near-RT RIC platform by passing the relevant info through the API. Relevant info may include the xApp name, vendor, software version, YANG schemas for - -configuration management, faults raised, metrics generated, ports for messaging, supported commands (e.g., health check, aliveness probe) and other information needed by the Near-RT RIC platform and/or the SMO for managing the xApp. - -In response to an xApp Registration, Near-RT RIC platform performs the following: - -- Authenticates the xApp; -- Validates that this xApp can run on this Near-RT RIC platform; e.g., RIC has the capacity; -- Assigns an ID to the xApp; -- May act as Registration Authority (RA) of the operator Certification Authority (CA), and fetch from the CA a new End Entity (EE) operator certificate for the xApp containing the assigned xApp ID in SubjectAltName (SAN) field. - -NOTE: Refer to [22] clause 5.1.3.2 for more detailed information on the security procedure. - -- Creates an xApp Managed Object Instance (MOI) in the Near-RT RIC Config DB and populates it with the relevant information passed from the xApp; -- Sends a Notify MOI Creation to SMO if subscribed. - -The data type of the xApp ID shall be a character string that uniquely identifies the xApp instance. The format of this string shall be a Universally Unique Identifier (UUID) version 4 (as described in IETF RFC 4122). - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | To register the newly deployed xApp to the Near-RT RIC platform. | | -| Actors and Roles |
  • • xApp: originator of the xApp registration procedure;
  • • Near-RT RIC platform, with the following functionalities:
    • – Management
| | -| Assumptions | The API channel is established successfully between xApp and the Near-RT RIC platform. | | -| Pre conditions | The xApp is deployed onto the Near-RT RIC platform. As part of the initial configuration security information used in the security procedure defined in [22] clause 5.1.3.2 is provided to the xApp. xApp has established a secure connection with the Near-RT RIC platform. | | -| Begins when | An xApp is deployed and ready for registration. | | -| Step 1 (M) | xApp send xApp registration request to the Near-RT RIC platform. passing relevant information needed to manage the xApp. | | -| Step 2 (M) | Near-RT RIC platform processes the application registration, which includes (not an exhaustive list):
  • • Performing authentication and validity checks;
  • • If the checks pass, assigning an xApp ID for the xApp;
  • • Performing the security procedure specified in [22] clause 5.1.3.2;
  • • Creating an xApp Managed Object Instance in the Near-RT RIC Config DB in compliance with the YANG schemas;
  • • Populating xApp MOI with the xApp ID and the initial xApp configuration.
| | -| Step 3 (M) | The Near-RT RIC platform send the registration response to the xApp. If the response indicates the registration fails, it will send the registration response with failure results and failure cause. | | -| Step 4 (O) | If SMO has subscribed to CM Notifications from the Near-RT RIC, Near-RT RIC platform formats and sends a Notify MOI Creation to SMO to notify SMO that a MOI has been created for a new xApp. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -participant smo as "SMO" - -box "Near-RT RIC" - participant "xApp" as xApp - participant plt as "Near-RT RIC platform" -endbox - -xApp -> plt: 1. Registration request -plt -> plt: 2. Registration processing \n(validate, assign xApp ID, \nissue xApp cert, create xApp MOI) -plt -> xApp: 3. Registration response - -opt If SMO has subscribed - plt -> smo: 4. <> Notify MOI Creation -end - -@enduml - -``` - -![Sequence diagram for xApp Registration procedure. Lifelines: SMO, xApp, and Near-RT RIC platform. The xApp sends a registration request to the platform. The platform performs internal processing and returns a response. An optional block 'If SMO has subscribed' shows the platform sending a notification to the SMO.](11f18bf0233d812ad2604f88f3385d60_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant plt as Near-RT RIC platform - participant smo as SMO - - Note right of plt: Near-RT RIC - xApp->>plt: 1. Registration request - plt->>plt: 2. Registration processing (validate, assign xApp ID, issue xApp cert, create xApp MOI) - plt->>xApp: 3. Registration response - - opt If SMO has subscribed - plt->>smo: 4. <> Notify MOI Creation - end - -``` - -Sequence diagram for xApp Registration procedure. Lifelines: SMO, xApp, and Near-RT RIC platform. The xApp sends a registration request to the platform. The platform performs internal processing and returns a response. An optional block 'If SMO has subscribed' shows the platform sending a notification to the SMO. - -Figure 9.4.1-1: xApp Registration procedure - -### 9.4.2 xApp Deregistration procedure - -This procedure deregisters the xApp from the Near-RT RIC platform. - -The message flow is not specified in the present document. - -### 9.4.3 Void - -### 9.4.4 Create MOI - -An xApp must be instantiated before its associated MOI can be created. The SMO interacts with the MOI to manage the xApp. The Near-RT RIC platform is responsible for updating the xApp over the Management API to ensure that its attribute values are aligned with those of the MOI. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To Create a Managed Object Instance for an xApp. | | -| Actors and Roles |
  • Near RT-RIC platform
  • xApp
| | -| Assumptions | The API channel is established successfully between xApp and the Near-RT RIC platform. | | -| Preconditions |
  • xApp is instantiated;
  • MOI is not yet created.
| | -| Begins when | Create MOI operation received over O1 | | -| Step 1 (M) | Near-RT RIC platform sends an APIConfigurationWrite updating the xApp with the attribute values from the newly created MOI | | -| Step 2 (M) | After applying the configuration data to the xApp, a configuration response is sent over the management API to the Near-RT RIC platform. | | -| Ends when | Create MOI Response is sent over O1. | | - -``` -@startuml -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -participant smo as "SMO" -box "Near-RT RIC" -participant plt as "Near-RT RIC Platform" -participant xApp as "xApp" -endbox - -smo -> plt: <> createMOI(...) - -plt -> xApp: 1. <> xApp Configuration Request -plt --> xApp: 2. <> Result -smo --> plt: <> Result -@enduml -``` - -![Sequence diagram for xApp Create MOI. The diagram shows interactions between SMO, Near-RT RIC Platform, and xApp. The SMO sends a createMOI(...) message to the platform. The platform sends an xApp Configuration Request to the xApp. The xApp returns a Result to the platform. The platform returns a Result to the SMO.](b3d488012fdceacab867cf24c5efef05_img.jpg) - -``` - -sequenceDiagram - participant SMO - participant Platform as Near-RT RIC Platform - participant xApp - Note right of Platform: Near-RT RIC - SMO->>Platform: <> createMOI(...) - Platform->>xApp: 1. <> xApp Configuration Request - xApp-->>Platform: 2. <> Result - Platform-->>SMO: <> Result - -``` - -Sequence diagram for xApp Create MOI. The diagram shows interactions between SMO, Near-RT RIC Platform, and xApp. The SMO sends a createMOI(...) message to the platform. The platform sends an xApp Configuration Request to the xApp. The xApp returns a Result to the platform. The platform returns a Result to the SMO. - -Figure 9.4.4-1: xApp Create MOI - -### 9.4.5 Modify MOI attributes - -The Near-RT RIC platform is responsible for updating the xApp over the Management API to ensure its attribute values are aligned with those of the MOI. - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | To change an existing xApp MOI configuration. | | -| Actors and Roles |
  • Near RT-RIC platform
  • xApp
| | -| Assumptions |
  • The API channel is established successfully between xApp and the Near-RT RIC platform.
| | -| Pre conditions |
  • The xApp is installed successfully on the Near-RT RIC platform and registered to the SMO;
  • The MOI for the target xApp already exists.
| | -| Begins when | Near-RT RIC platform receives the configuration message from SMO to indicate that there's a configuration update for the xApp. | | -| Step 1 (M) | Near-RT RIC platform sends an APIConfigurationWrite updating the xApp with the attribute values contained in the O1 Modify MOI message. | | -| Step 2 (M) | The xApp sends a Configuration Response. | | -| Ends when | Near-RT RIC platform notifies SMO of success or error. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid -participant smo as "SMO" -box "Near-RT RIC" - participant plt as "Near-RT RIC Platform" - participant xApp as "xApp" -end box - -smo -> plt: <> ModifyMOIAttributes(...) -plt -> xApp: 1. (API) xApp Configuration Request -plt --> xApp: 2. (API) Result -smo --> plt: <> Result -@enduml - -``` - -![Sequence diagram for xApp Modify MOI. The diagram shows an SMO sending a ModifyMOIAttributes message to a Near-RT RIC Platform. The platform then sends an xApp Configuration Request to an xApp, which returns a Result. Finally, the platform sends a Result back to the SMO.](487c58c79e44e6cf98b6368b6667b9c6_img.jpg) - -``` - -sequenceDiagram - participant SMO - participant Near-RT RIC Platform - participant xApp - Note right of Near-RT RIC Platform: Near-RT RIC - SMO->>Near-RT RIC Platform: <> ModifyMOIAttributes(...) - Near-RT RIC Platform->>xApp: 1. (API) xApp Configuration Request - xApp-->>Near-RT RIC Platform: 2. (API) Result - Near-RT RIC Platform-->>SMO: <> Result - -``` - -Sequence diagram for xApp Modify MOI. The diagram shows an SMO sending a ModifyMOIAttributes message to a Near-RT RIC Platform. The platform then sends an xApp Configuration Request to an xApp, which returns a Result. Finally, the platform sends a Result back to the SMO. - -Figure 9.4.5-1: xApp Modify MOI - -### 9.4.6 Delete MOI - -This procedure removes the MOI for an an xApp when an edit-config delete request is received from the SMO over the O1 interface. See [5] clause 2.1.3. The SMO sends the deleteMOI request via a NETCONF command over the O1 to the Near-RT RIC platform. The Near-RT RIC platform may optionally take the xApp out of service sending a confirmation of the state change before the MOI gets deleted. Once the MOI is deleted, the Near-RT RIC platform sends a NETCONF response confirming the success or failure to the MnS Consumer (SMO). - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | To remove an existing xApp MOI. | | -| Actors and Roles |
  • Near-RT RIC platform
  • xApps
| | -| Assumptions | The API channel is established successfully between xApp and the Near-RT RIC platform. | | -| Pre conditions | The MOI exists on the target Near-RT RIC. | | -| Begins when | Near-RT RIC platform receives the edit-config Delete message from SMO to indicate that the SMO wants to delete the MOI. | | -| Step 1 (O) | Near-RT RIC platform may optionally lock the administrative state of the xApp. | | -| Step 2 (M) | Near-RT RIC platform deletes the MOI. | | -| Ends when | The MnS Consumer (SMO) receives the O1 response. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -participant smo as "SMO" -box "Near-RT RIC" - participant plt as "Near-RT RIC platform" - participant xApp as "xApp" -end box - -smo -> plt: <> DeleteMOIRequest -Opt Lock xApp state - plt -> xApp: 1. API Configuration Write \n(Change Adminstrative State to "Locked") - -``` - -``` - -end -plt -> plt: 2. MOI Deleted -smo <-- plt: <> Result -@enduml - -``` - -![Sequence diagram for xApp Delete MOI. Lifelines: SMO, Near-RT RIC platform, xApp. The SMO sends a DeleteMOIRequest to the platform. An 'opt' block titled '[Lock xApp state]' contains two steps: 1. API Configuration Write (Change Administrative State to 'Locked') from platform to xApp, and 2. MOI Deleted (self-call on platform). Finally, the platform sends an <> Result back to the SMO.](0dfdff10c725fe9c332b07ade9d23a5e_img.jpg) - -``` - -sequenceDiagram - participant SMO - participant Near-RT RIC platform - participant xApp - Note right of Near-RT RIC platform: Near-RT RIC - SMO->>Near-RT RIC platform: <> DeleteMOIRequest - opt Lock xApp state - Near-RT RIC platform->>xApp: 1. API Configuration Write (Change Administrative State to "Locked") - Near-RT RIC platform->>Near-RT RIC platform: 2. MOI Deleted - end - Near-RT RIC platform-->>SMO: <> Result - -``` - -Sequence diagram for xApp Delete MOI. Lifelines: SMO, Near-RT RIC platform, xApp. The SMO sends a DeleteMOIRequest to the platform. An 'opt' block titled '[Lock xApp state]' contains two steps: 1. API Configuration Write (Change Administrative State to 'Locked') from platform to xApp, and 2. MOI Deleted (self-call on platform). Finally, the platform sends an <> Result back to the SMO. - -Figure 9.4.6-1: xApp Delete MOI - -### 9.4.7 Read MOI attributes - -The O1 Read MOI Attributes service is supported by the xApp API Configuration Read. On receipt of a Read MOI Attributes request for an xApp, the Near-RT RIC platform uses the API Configuration Read to retrieve the current configuration values. - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | To Read the current attribute values for an existing xApp MOI. | | -| Actors and Roles |
  • Near-RT RIC platform
  • xApps
| | -| Assumptions |
  • The API channel is established successfully between xApp and the Near-RT RIC platform.
| | -| Pre conditions |
  • The MOI exists on the target Near-RT RIC.
| | -| Begins when | Near-RT RIC platform receives the Read MOI Attributes request from SMO to indicate that the SMO wants the current xApp attributes. | | -| Step 1 (O) | Near-RT RIC platform sends xApp Configuration Read (Optional because the information is already available in the MOI in the Near-RT RIC platform ). | | -| Step 2 (O) | xApp makes the operational configuration available to the Near-RT RIC platform. | | -| Ends when | The MnS Consumer (SMO) receives the O1 response. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -participant smo as "SMO" -box "Near-RT RIC" -participant plt as "Near-RT RIC platform" - -``` - -``` - -participant xApp as "xApp" -end box -smo -> plt: <> Read MOI Attributes(...) -Opt Sync MOI with xApp -plt -> xApp: 1. (API) xApp Configuration Request -plt <--xApp: 2. (API) Result -end -smo <-- plt: <> Result -@enduml - -``` - -![Sequence diagram for Read MOI Attributes. Lifelines: SMO, Near-RT RIC platform, xApp. The SMO sends a Read MOI Attributes message to the platform. An 'opt Sync MOI with xApp' block contains the platform sending an xApp Configuration Request to the xApp and receiving a Result. Finally, the platform sends the Result back to the SMO.](ffe0fef452a0ae9a20253c319c54e13c_img.jpg) - -``` - -sequenceDiagram - participant SMO - participant Near-RT RIC platform - participant xApp - Note right of Near-RT RIC platform: Near-RT RIC - SMO->>Near-RT RIC platform: <> Read MOI Attributes(...) - opt Sync MOI with xApp - Near-RT RIC platform->>xApp: 1. (API) xApp Configuration Request - xApp-->>Near-RT RIC platform: 2. (API) Result - end - Near-RT RIC platform-->>SMO: <> Result - -``` - -Sequence diagram for Read MOI Attributes. Lifelines: SMO, Near-RT RIC platform, xApp. The SMO sends a Read MOI Attributes message to the platform. An 'opt Sync MOI with xApp' block contains the platform sending an xApp Configuration Request to the xApp and receiving a Result. Finally, the platform sends the Result back to the SMO. - -Figure 9.4.7-1: Read MOI Attributes - -### 9.4.8 Notify MOI changes - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | To notify Near-RT RIC platform that some change has occurred in the xApp configuration | | -| Actors and Roles |
  • Near-RT RIC platform
  • xApps
| | -| Assumptions |
  • The API connection is established successfully between xApp and the Near-RT RIC platform.
| | -| Pre conditions |
  • The MOI exists on the target Near-RT RIC.
| | -| | [ALT 1] Attribute Value Change Notification (AVCN) | | -| Begins when | The Near-RT RIC platform receives an xApp Notify change message from the xApp. | | -| Step 1 (M) | The Near-RT RIC platform sends O1 Attribute Value Change Notification to the O1 Consumer (SMO). | | -| | [ALT 2] MOI Creation Notification | | -| Begins when | A Managed Object Instance representing xApp has been created. | | -| Step 1 (M) | The Near-RT RIC platform sends O1 MOI Creation Notification to the O1 Consumer (SMO). | | -| | [ALT 3] MOI Deletion Notification | | -| Begins when | A Managed Object Instance representing xApp has been Deleted. | | -| Step 1(M) | The Near-RT RIC platform sends O1 MOI Deletion Notification to the O1 Consumer (SMO). | | -| | [ALL CASES] | | -| Ends when | The MnS Consumer (SMO) receives the O1 response. | | - -``` -@startuml -``` - -``` -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -participant smo as "SMO" -box "Near-RT RIC" -participant plt as "Near-RT RIC Platform" -participant xApp as "xApp" -end box - -alt Attribute Value Change Notification -plt <- xApp: <> xApp Notify Change - -loop for each subscription -smo <- plt: <> Notify MOI Change(AVCN) -end -else MOI Creation Notification -plt -> plt: MOI Creation -loop for each subscription -smo <- plt: <> Notify MOI Change(MOI Created) -end -else MOI Deletion Notification -plt -> plt: MOI Deletion -loop for each subscription -smo <- plt: <> Notify MOI Change(MOI Deleted) -end -end -@enduml -``` - -![Sequence diagram titled 'Notify MOI Changes' showing interactions between SMO, Near-RT RIC Platform, and xApp. The diagram includes an 'alt' block for 'Attribute Value Change Notification', 'MOI Creation Notification', and 'MOI Deletion Notification'. Each notification type has a 'loop' for 'for each subscription' where the Near-RT RIC Platform sends a '<> Notify MOI Change' message to the SMO.](d79de2dd022d74722a84f1b2ffce691c_img.jpg) - -``` - -sequenceDiagram - participant SMO - participant Near-RT RIC Platform - participant xApp - - Note right of Near-RT RIC Platform: Near-RT RIC - alt Attribute Value Change Notification - xApp->>Near-RT RIC Platform: <> xApp Notify Change - loop for each subscription - Near-RT RIC Platform->>SMO: <> Notify MOI Change(AVCN) - end - else MOI Creation Notification - Near-RT RIC Platform->>SMO: MOI Creation - loop for each subscription - Near-RT RIC Platform->>SMO: <> Notify MOI Change(MOI Created) - end - else MOI Deletion Notification - Near-RT RIC Platform->>SMO: MOI Deletion - loop for each subscription - Near-RT RIC Platform->>SMO: <> Notify MOI Change(MOI Deleted) - end - end - -``` - -Sequence diagram titled 'Notify MOI Changes' showing interactions between SMO, Near-RT RIC Platform, and xApp. The diagram includes an 'alt' block for 'Attribute Value Change Notification', 'MOI Creation Notification', and 'MOI Deletion Notification'. Each notification type has a 'loop' for 'for each subscription' where the Near-RT RIC Platform sends a '<> Notify MOI Change' message to the SMO. - -Figure 9.4.8-1: Notify MOI Changes - -### 9.4.9 Subscription Control - -| Use Case Stage | Evolution / Specification | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | Allows a MnS Consumer to subscribe to notifications emitted by a MnS Provider. | -| Actors and Roles |
  • Near-RT RIC platform
  • xApps
| -| Assumptions |
  • The API channel is established successfully between xApp and the Near-RT RIC platform.
| -| Pre conditions |
  • An MOI exists on the target Near-RT RIC representing the xApp functionality.
| -| Begins when | Near-RT RIC platform receives a Create MOI message with arguments defining the MOI as a Subscription and associating it with one or more xApps and a consumer (SMO). | -| Step 1 (M) | A Subscription Control MOI reflecting the scope and filtering requirements for the subscription is created and associated with the instance of Managed Application representing the xApp. | -| Ends when | The MnS Consumer (SMO) receives the O1 response. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -participant smo as "SMO" - -``` - -``` - -box "Near-RT RIC" - participant plt as "Near-RT RIC platform" - participant xApp as "xApp" -endbox - -smo -> plt: <> createMOI(xApp subscription) - -Opt message received from xApp -plt <- xApp: 1. (API) xApp Notify Change -end -smo <-- plt: <> Notification -@enduml - -``` - -![Sequence diagram for xApp Subscription Control. It shows an SMO sending a createMOI message to a Near-RT RIC platform. Inside the Near-RT RIC, an xApp sends an xApp Notify Change message to the platform. The platform then sends a Notification message back to the SMO. The diagram is split into two identical halves by a horizontal line.](e16bfa31d748f4d99ec4ae3d16656926_img.jpg) - -Sequence diagram for xApp Subscription Control. It shows an SMO sending a createMOI message to a Near-RT RIC platform. Inside the Near-RT RIC, an xApp sends an xApp Notify Change message to the platform. The platform then sends a Notification message back to the SMO. The diagram is split into two identical halves by a horizontal line. - -Figure 9.4.9-1: xApp Subscription Control - -### 9.4.10 Fault Notification - -This procedure enables the xApps to notify the Near-RT RIC of a Fault Condition. Near-RT RIC platform may create an Alarm notification based on the fault reported over the API, and supplement it with additional information from the Alarm Dictionary. The notification is also used to notify Alarms changes. - -| Use case stage | Evolution/Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------|-------------------------| -| Goal | xApp informs the Near-RT RIC of the existence of a Fault condition | | -| Actors and Roles |
  • xApp
  • Near-RT RIC platform
| | -| Assumptions | | | -| Pre-conditions | | | -| Begins when | A fault condition is detected at the xApp. | | -| Step 1 (M) | xApp Management API sends a fault notification. | | -| Step 2 (M) | Near-RT RIC platform determines whether to create an Alarm notification for the fault. | | -| Ends when | xApp sends Fault Notification to the Near-RT RIC. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -participant smo as "SMO" -box "Near-RT RIC" - participant plt as "Near-RT RIC platform" - collections xApp as "xApp" -end box - -``` - -``` - -xApp -> plt: 1. Fault condition detected - -Opt Create Alarm -plt --> plt: 2. If the reported fault condition maps to a subscribed Alarm -end -smo <-- plt: <> Fault Notification - -@enduml - -``` - -![Sequence diagram for Fault Notification. Lifelines: SMO (top), Near-RT RIC platform (top), xApp (top) inside Near-RT RIC box; SMO (bottom), Near-RT RIC platform (bottom), xApp (bottom) inside Near-RT RIC box. Sequence: 1. xApp (top) sends 'Fault condition detected' to Near-RT RIC platform (top). 2. Inside 'opt Create Alarm' block, Near-RT RIC platform (top) sends message to itself (bottom). 3. Near-RT RIC platform (bottom) sends '<> Fault Notification' to SMO (bottom).](c0ca823603794512478906b302176bca_img.jpg) - -Sequence diagram for Fault Notification. Lifelines: SMO (top), Near-RT RIC platform (top), xApp (top) inside Near-RT RIC box; SMO (bottom), Near-RT RIC platform (bottom), xApp (bottom) inside Near-RT RIC box. Sequence: 1. xApp (top) sends 'Fault condition detected' to Near-RT RIC platform (top). 2. Inside 'opt Create Alarm' block, Near-RT RIC platform (top) sends message to itself (bottom). 3. Near-RT RIC platform (bottom) sends '<> Fault Notification' to SMO (bottom). - -Figure 9.4.10-1: Fault Notification - -### 9.4.11 Fault Supervision Control - -The O1 Interface supports the 3GPP “getAlarmList”. The Alarm list for the xApps is maintained on the Near-RT RIC. The xApp can notify the Near-RT RIC platform of a detected fault. Each xApp shall maintain a list of any faults that are active. These faults are notified to the Near RT RIC platform where the necessary Alarms are created. - -The SMO (consumer) may need to verify which alarms are currently active and so may request that the Near-RT RIC (producer) provides an updated list of Alarms. In order to verify that its Alarm list correctly reflects the state of faults at the xApp, the Near RT RIC platform can request an updated list of faults from the xApp. - -| Use case stage | Evolution/Specification | <> Related use | -|------------------|---------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | To validate that the Near-RT RIC Alarm list for a given xApp correctly reflects the fault status of that xApp | | -| Actors and Roles |
  • SMO
  • Near-RT RIC platform
  • xApp
| | -| Assumptions | | | -| Pre-conditions | Target xApp in service. | | -| Begins when | O1 consumer (SMO) requests Near-RT RIC platform to fetch the current Alarm List. | | -| Step 1 (M) | Near-RT RIC platform requests xApp to provide the list of current faults. | | -| Step 2 (M) | xApp sends list of current faults to Near-RT RIC platform. | | -| Ends when | O1 consumer (SMO) receives current Alarm list. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -``` - -``` - -participant smo as "SMO" -box "Near-RT RIC" - participant plt as "Near-RT RIC platform" - Collections xApp as "xApp" -End box - -smo -> plt: <> getAlarmList -plt -> xApp: 1. (API) Get Fault List -plt <-- xApp: 2. (API) Return Fault list -smo <-- plt: <> Alarm InformationList - -@enduml - -``` - -![Sequence diagram for 'Get Alarm List' showing interactions between SMO, Near-RT RIC platform, and xApp.](fc3e2b49a9f850951570e502393b697f_img.jpg) - -``` - -sequenceDiagram - participant SMO - participant Near-RT RIC platform - participant xApp - Note right of Near-RT RIC platform: Near-RT RIC - SMO->>Near-RT RIC platform: <> getAlarmList - Near-RT RIC platform->>xApp: 1. (API) Get Fault List - xApp-->>Near-RT RIC platform: 2. (API) Return Fault list - Near-RT RIC platform-->>SMO: <> Alarm InformationList - -``` - -Sequence diagram for 'Get Alarm List' showing interactions between SMO, Near-RT RIC platform, and xApp. - -Figure 9.4.11-1: Get Alarm List - -### 9.4.12 Performance Data File Reporting - -| Use case stage | Evolution/Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------|-------------------------| -| Goal | xApp informs Near-RT RIC platform that a file is ready and provides the location for that file. | | -| Actors and Roles |
  • SMO
  • Near-RT RIC platform
  • xApp
| | -| Assumptions | | | -| Pre-conditions | PerfMetricJob exists and includes a valid stream target value. | | -| Begins when | PM Streaming configuration created. | | -| Step 1 (M) | xApp sends API notification that a file is ready also providing the location of that file. | | -| Step 2 (M) | <> File Ready notification sent. | | -| Ends when | SMO receives notification. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -participant smo as "SMO" -box "Near-RT RIC" - participant plt as "Near-RT RIC platform" - Collections xApp as "xApp" - -``` - -End box - -``` -plt <- xApp: (API) 1. xApp Notify File Ready -plt -> plt: New PM data file available - -smo <- plt: 2. <> notifyFileReady Notification -@enduml -``` - -![Sequence diagram for Performance Data File Reporting. Lifelines: SMO (outside), Near-RT RIC platform (inside Near-RT RIC box), xApp (inside Near-RT RIC box). Sequence: 1. xApp sends '(API) 1. xApp Notify File Ready' to Near-RT RIC platform. 2. Near-RT RIC platform sends 'New PM data file available' to itself. 3. Near-RT RIC platform sends '2. <> notifyFileReady Notification' to SMO.](a0eb8d30ac11ba97b2733c187b89ff22_img.jpg) - -``` -sequenceDiagram - participant SMO - participant Near-RT RIC platform - participant xApp - Note right of xApp: (API) 1. xApp Notify File Ready - xApp->>Near-RT RIC platform: New PM data file available - Near-RT RIC platform->>SMO: 2. <> notifyFileReady Notification -``` - -Sequence diagram for Performance Data File Reporting. Lifelines: SMO (outside), Near-RT RIC platform (inside Near-RT RIC box), xApp (inside Near-RT RIC box). Sequence: 1. xApp sends '(API) 1. xApp Notify File Ready' to Near-RT RIC platform. 2. Near-RT RIC platform sends 'New PM data file available' to itself. 3. Near-RT RIC platform sends '2. <> notifyFileReady Notification' to SMO. - -Figure 9.4.12-1: Performance Data File Reporting - -### 9.4.13 Report Streamed Data - -When the ReportingCtrl Attribute of the PerfMetricJob ([21] Clause 4.3.33) is set to streamTarget, the Near-RT RIC shall stream the PM data to the target consumer destination based on the value of the “streamTarget” attribute. - -| Use case stage | Evolution/Specification | <> Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | Report Streamed Data | | -| Actors and Roles |
  • SMO
  • Near-RT RIC platform
  • xApp
| | -| Assumptions | | | -| Pre-conditions | PerfMetricJob exists and includes a valid stream target value.
A streaming connection has been established between the Near-RT RIC and the SMO. | | -| Begins when | PM Streaming configuration created. | | -| Step 1 (M) | (API) Near-RT RIC platform directs xApp to start streaming data. | | -| Step 2 (M) | (API) xApp streams data to Near-RT RIC platform. | | -| Step 3 (M) | Near-RT RIC platform streams PM data to subscriber. | | -| Ends when | SMO receives streamed data. | | - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -participant smo as "SMO" -box "Near-RT RIC" - participant plt as "Near-RT RIC platform" - Collections xApp as "xApp" -endbox -``` - -Note over plt: Streaming target specified in PerfMetricJob - -``` -plt -> xApp: 1. (API) Start Streaming -``` - -``` - -Loop While streaming is active -xApp -> plt: 2. (API) Sending streamed data -smo <- plt: 3. <> reportStreamData operation -end -@enduml - -``` - -![Sequence diagram for 'Report Streamed Data' showing interactions between SMO, Near-RT RIC platform, and xApp. The diagram includes a 'loop' block labeled '[While streaming is active]'. The sequence of messages is: 1. (API) Start Streaming from xApp to Near-RT RIC platform; 2. (API) Sending streamed data from Near-RT RIC platform to xApp; 3. <> reportStreamData operation from Near-RT RIC platform to SMO. A note indicates the 'Streaming target specified in PerfMetricJob'.](d04c50badc78d5ba47bf4e352af4a754_img.jpg) - -Sequence diagram for 'Report Streamed Data' showing interactions between SMO, Near-RT RIC platform, and xApp. The diagram includes a 'loop' block labeled '[While streaming is active]'. The sequence of messages is: 1. (API) Start Streaming from xApp to Near-RT RIC platform; 2. (API) Sending streamed data from Near-RT RIC platform to xApp; 3. <> reportStreamData operation from Near-RT RIC platform to SMO. A note indicates the 'Streaming target specified in PerfMetricJob'. - -Figure 9.4.13-1 Report Streamed Data - -### 9.4.14 Measurement Job Control - -Both the selection of the data at the xApp and the formatting of the data at the Near-RT RIC platform are in scope for this procedure. The CreateMeasurementJobControl request received over O1 also determines whether the PM data would be file based or streamed. - -| Use case stage | Evolution/Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To configure the collection of PM measurements | | -| Actors and Roles |
  • SMO
  • Near-RT RIC platform
  • xApp
| | -| Assumptions | | | -| Pre-conditions | Target xApp in service. | | -| Begins when | “Create PerfMetricJob” received on O1 interface. | | -| Step 1 (M) | Configure xApp to collect and forward PM data. | | -| Step 2 (M) | PM collection response. | | -| Ends when | Successful creation of PM PerformanceMetric Job confirmed on O1. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -participant smo as "SMO" -box "Near-RT RIC" - participant plt as "Near-RT RIC platform" - collections xApp as "xApp" - -``` - -Endbox - -``` -smo -> plt: <> Create PerfMetricJobMOI -plt -> xApp: 1. (API) xApp Configuration Request\n (configure Measurment Job) -plt <-- xApp: 2. (API) Result -smo <-- plt: <> Result -@enduml -``` - -![Sequence diagram for Measurement Job Control. It shows the interaction between an SMO and an xApp through a Near-RT RIC platform. The SMO sends a 'Create PerfMetricJobMOI' message to the platform. The platform sends a '1. (API) xApp Configuration Request (configure Measurment Job)' to the xApp. The xApp returns a '2. (API) Result' to the platform. Finally, the platform sends a 'Result' message back to the SMO.](af90aabfe3c8c65617da060d82bf99c5_img.jpg) - -``` -sequenceDiagram - participant SMO - participant Platform as Near-RT RIC platform - participant xApp - Note right of Platform: Near-RT RIC - SMO->>Platform: <> Create PerfMetricJobMOI - Platform->>xApp: 1. (API) xApp Configuration Request (configure Measurment Job) - xApp-->>Platform: 2. (API) Result - Platform-->>SMO: <> Result -``` - -Sequence diagram for Measurement Job Control. It shows the interaction between an SMO and an xApp through a Near-RT RIC platform. The SMO sends a 'Create PerfMetricJobMOI' message to the platform. The platform sends a '1. (API) xApp Configuration Request (configure Measurment Job)' to the xApp. The xApp returns a '2. (API) Result' to the platform. Finally, the platform sends a 'Result' message back to the SMO. - -Figure 9.4.14-1 Measurement Job Control - -## 9.5 SDL API Procedures - -### 9.5.1 Void - -### 9.5.2 Void - -### 9.5.3 Fetch Data procedure - -The Fetch Data procedure in the Near-RT RIC enables an xApp to request data for which it is authorized as the SDL client for local processing. - -| Use Case Stage | Evolution / Specification | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp fetches data as the SDL client. | -| Actors and Roles |
  • xApp: Originator of Fetch Data request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • SDL API services have been registered with Near-RT RIC platform;
  • xApp has successfully registered as a client to the SDL before;
  • xApp has been authorized to read the data in the database.
| -| Begins when | xApp determines to fetch relevant data as the SDL client from the Near-RT-RIC platform. | -| Step 1 (M) | xApp requests to Near-RT RIC platform to fetch data from database. | -| Step 2 (M) | Near-RT RIC platform fetches xApp required information from database. | -| Step 3 (M) | Near-RT RIC platform sends the requested data or the failure response to specific xApp. | - -``` -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -box "Near-RT RIC" -Collections "xApp" as xApp -``` - -``` - -Participant plt as "Near-RT RIC platform" -end box - -xApp -> plt: 1. Fetch data request -plt -> plt: 2. Fetch related information -plt -> xApp: 3. Fetch data response -@enduml - -``` - -![Sequence diagram for Fetch Data procedure. It shows an xApp lifeline and a Near-RT RIC platform lifeline. The sequence of messages is: 1. Fetch data request from xApp to platform, 2. Fetch related information (self-call on platform), and 3. Fetch data response from platform to xApp.](0b998e3ad8f9d104768642612605cb35_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant plt as Near-RT RIC platform - Note right of plt: Near-RT RIC - xApp->>plt: 1. Fetch data request - plt->>plt: 2. Fetch related information - plt->>xApp: 3. Fetch data response - -``` - -Sequence diagram for Fetch Data procedure. It shows an xApp lifeline and a Near-RT RIC platform lifeline. The sequence of messages is: 1. Fetch data request from xApp to platform, 2. Fetch related information (self-call on platform), and 3. Fetch data response from platform to xApp. - -Figure 9.5.3-1: Fetch Data procedure - -### 9.5.4 Subscribe/Update-Notify procedure - -The Subscribe/Update-Notify procedure in the Near-RT RIC allows the xApp to subscribe to SDL notifications for the summary of authorized data changes. The Near-RT RIC platform will notify the summary of information changes to the xApp, and the xApp may subsequently request updated data through the Fetch Data procedure. - -The notifications contain only summary of changes to the information after the subscription. - -| Use Case Stage | Evolution / Specification | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp subscribes with the Near-RT RIC platform for data changes and receives related notifications. | -| Actors and Roles |
  • xApp: Originator of Subscribe request;
  • Near-RT RIC platform: Response to the request of xApp, and notify the subscribed information to xApp.
| -| Pre-conditions |
  • SDL API services have been registered by Near-RT RIC platform;
  • xApp has successfully registered as a client to the SDL before.
| -| Begins when | xApp determines to subscribe for notifications related to summary of information changes in the Near-RT-RIC platform database. | -| Step 1 (M) | xApp sends the request to Near-RT RIC platform to subscribe for notifications related to summary of SDL information changes. | -| Step 2 (M) | Near-RT RIC platform responds to the xApp subscription. | -| Step 3 (M) | Near-RT RIC platform sends the notification for the subscribed summary of information changes to the xApp. The xApp may further send a request to Near-RT RIC platform to fetch the updated information. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" -Collections "xApp" as xApp -Participant plt as "Near-RT RIC platform" - -``` - -End box - -``` -xApp -> plt: 1. Subscribe information request -plt -> xApp: 2. Subscribe information response -plt -> xApp: 3. Notify information changes -@enduml -``` - -![Sequence diagram titled 'Near-RT RIC' showing the interaction between an xApp and a Near-RT RIC platform. The diagram shows three steps: 1. xApp sends a 'Subscribe information request' to the platform; 2. The platform responds with a 'Subscribe information response'; 3. The platform sends a 'Notify information changes' message to the xApp. The xApp and platform are shown as stacked boxes at the top and bottom of the diagram area.](5ec3284657e4df0df3653dd61d0ecd13_img.jpg) - -Sequence diagram titled 'Near-RT RIC' showing the interaction between an xApp and a Near-RT RIC platform. The diagram shows three steps: 1. xApp sends a 'Subscribe information request' to the platform; 2. The platform responds with a 'Subscribe information response'; 3. The platform sends a 'Notify information changes' message to the xApp. The xApp and platform are shown as stacked boxes at the top and bottom of the diagram area. - -Figure 9.5.4-1: Subscribe/Update-Notify procedure - -### 9.5.5 Store Data procedure - -The Store Data procedure in the Near-RT RIC ensures that the xApp may request Near-RT RIC platform to insert data to the database. - -| Use Case Stage | Evolution / Specification | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp requests to store data in the database. | -| Actors and Roles |
  • xApp: Originator of Store Data request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • SDL API services have been registered by Near-RT RIC platform;
  • xApp has successfully registered as a client to the SDL before;
  • xApp has been authorized to write the data in the database.
| -| Begins when | xApp determines to store relevant data to the database in the Near-RT-RIC platform. | -| Step 1 (M) | xApp sends a request to Near-RT RIC platform to store related information and try to insert data to database. | -| Step 2 (M) | Near-RT RIC platform stores xApp requested information in database. | -| Step 3 (M) | Near-RT RIC platform responds to the xApp, including success and failure operation. | - -``` -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Collections "xApp" as xApp - Participant plt as "Near-RT RIC platform" -End box - -xApp -> plt: 1. Store data request -plt -> plt: 2. Store related data -plt -> xApp: 3. Store data response -@enduml -``` - -![Sequence diagram for Store Data procedure. Lifelines: xApp and Near-RT RIC platform. The diagram shows three steps: 1. Store data request from xApp to platform, 2. Store related data (self-call on platform), and 3. Store data response from platform to xApp.](81a0abf9a79b27cf9d765553216b173c_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant platform as Near-RT RIC platform - Note right of platform: Near-RT RIC - xApp->>platform: 1. Store data request - platform->>platform: 2. Store related data - platform->>xApp: 3. Store data response - -``` - -Sequence diagram for Store Data procedure. Lifelines: xApp and Near-RT RIC platform. The diagram shows three steps: 1. Store data request from xApp to platform, 2. Store related data (self-call on platform), and 3. Store data response from platform to xApp. - -Figure 9.5.5-1: Store Data procedure - -### 9.5.6 Modify Data procedure - -The Modify Data procedure in the Near-RT RIC allows the xApp to request Near-RT RIC platform to update or delete data from database. - -| Use Case Stage | Evolution / Specification | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp intends to modify or delete data stored by the SDL. | -| Actors and Roles |
  • xApp: Originator of Modify Data request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • SDL API services have been registered by Near-RT RIC platform;
  • xApp has successfully registered as a client to the SDL before;
  • xApp has been authorized to write the data in the database.
| -| Begins when | xApp determines to modify relevant data stored by the database in the Near-RT-RIC platform. | -| Step 1 (M) | xApp sends a request to Near-RT RIC platform to modify related information, including update and delete data in database. | -| Step 2 (M) | Near-RT RIC platform modifies or deletes xApp requested information in database. | -| Step 3 (M) | Near-RT RIC platform responds to the xApp, including success and failure operation. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Collections "xApp" as xApp - Participant plt as "Near-RT RIC platform" -End box - -xApp ->plt: 1. Modify data request -plt ->plt: 2. Modify related data -plt -> xApp: 3. Modify data response -@enduml - -``` - -![Sequence diagram for Modify Data procedure. It shows two lifelines: xApp and Near-RT RIC platform, both contained within a 'Near-RT RIC' box. The sequence of messages is: 1. xApp sends a 'Modify data request' to the platform; 2. The platform performs an internal 'Modify related data' operation; 3. The platform sends a 'Modify data response' back to the xApp.](060648daa95345c57f019fc00ad75993_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - Note over xApp, Near-RT RIC platform: Near-RT RIC - xApp->>Near-RT RIC platform: 1. Modify data request - Near-RT RIC platform->>Near-RT RIC platform: 2. Modify related data - Near-RT RIC platform->>xApp: 3. Modify data response - -``` - -Sequence diagram for Modify Data procedure. It shows two lifelines: xApp and Near-RT RIC platform, both contained within a 'Near-RT RIC' box. The sequence of messages is: 1. xApp sends a 'Modify data request' to the platform; 2. The platform performs an internal 'Modify related data' operation; 3. The platform sends a 'Modify data response' back to the xApp. - -Figure 9.5.6-1: Modify Data procedure - -### 9.5.7 Subscribe/Push procedure - -The Subscribe/Push procedure in the Near-RT RIC allows the xApp to subscribe to the Near-RT RIC platform for authorized data in the database. - -The pushes may be used to contain a given set of information, or only the changed part of the information after the subscription. - -| Use Case Stage | Evolution / Specification | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp subscribes with the Near-RT RIC platform for data changes and receives related push messages. | -| Actors and Roles |
  • xApp: Originates the Subscribe request;
  • Near-RT RIC platform: Responds to the xApp request and pushes the subscribed data and meta-data to the xApp.
| -| Pre-conditions |
  • SDL API services have been registered by Near-RT RIC platform;
  • xApp has successfully registered as a client to the SDL.
| -| Begins when | xApp subscribes for push messages related to information in the database in the Near-RT RIC platform. | -| Step 1 (M) | xApp sends the request to Near-RT RIC platform to subscribe for push messages related to information. | -| Step 2 (M) | Near-RT RIC platform responds to the xApp subscription. | -| Step 3 (M) | Near-RT RIC platform sends the push message with data and meta-data for the subscribed information to the xApp. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Collections "xApp" as xApp - Participant plt as "Near-RT RIC platform" -End box - -xApp -> plt: 1. Subscribe information request -plt -> xApp: 2. Subscribe information response -plt -> xApp: 3. Push (data + meta-data) -@enduml - -``` - -![Sequence diagram titled 'Near-RT RIC' showing the Subscribe/Push procedure. It features two 'xApp' lifelines and two 'Near-RT RIC platform' lifelines. The sequence of messages is: 1. Subscribe information request (from top xApp to top platform), 2. Subscribe information response (from top platform to top xApp), and 3. Push (data + meta-data) (from top platform to bottom xApp).](59e29b37c5e332b0be088cde8c4d217e_img.jpg) - -Sequence diagram titled 'Near-RT RIC' showing the Subscribe/Push procedure. It features two 'xApp' lifelines and two 'Near-RT RIC platform' lifelines. The sequence of messages is: 1. Subscribe information request (from top xApp to top platform), 2. Subscribe information response (from top platform to top xApp), and 3. Push (data + meta-data) (from top platform to bottom xApp). - -Figure 9.5.7-1: Subscribe/Push procedure - -### 9.5.7A xApp Shared Data Fetch procedure - -The xApp Shared Data Fetch procedure enables the data consumer (Near-RT RIC platform or an xApp) to fetch specific shared data from the data producer xApp. - -| Use Case Stage | Evolution / Specification | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | Data consumer (Near-RT RIC platform or xApp) fetches shared data from the data producer xApp. | -| Actors and Roles |
  • Data producer xApp;
  • Data consumer: Originator of xApp Shared Data Fetch request, which may be the Near-RT RIC platform or an xApp.
| -| Pre-conditions |
  • Data producer xApp has successfully registered its xApp Data Sharing service with Near-RT RIC platform;
  • Data consumer has discovered the xApp Data Sharing service.
| -| Begins when | The data consumer determines to fetch relevant data from the data producer xApp. | -| Step 1 (M) | The data consumer sends a request to the data producer xApp for specific shared data. | -| Step 2 (M) | The data producer xApp generates the requested data. | -| Step 3 (M) | The data producer xApp responds with the requested data. | - -``` -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -box "Near-RT RIC" -Participant consumer as "Data consumer \n(Near-RT RIC platform or xApp)" -Participant ProducerxApp as "Data producer xApp" -end box - -consumer -> ProducerxApp: 1. xApp Shared Data Fetch request \n(description of requested data) -ProducerxApp --> ProducerxApp: 2. Generate requested data -ProducerxApp -> consumer: 3. xApp Shared Data Fetch response \n(requested data) -@enduml -``` - -![Sequence diagram for xApp Shared Data Fetch procedure. It shows a 'Data consumer (Near-RT RIC platform or xApp)' sending a '1. xApp Shared Data Fetch request (description of requested data)' to a 'Data producer xApp'. The producer responds with '2. Generate requested data' and '3. xApp Shared Data Fetch response (requested data)'.](4c1ea859b93043f2fa17a8fe72fb6176_img.jpg) - -``` - -sequenceDiagram - participant DC as Data consumer (Near-RT RIC platform or xApp) - participant DP as Data producer xApp - Note right of DP: 2. Generate requested data - DC->>DP: 1. xApp Shared Data Fetch request (description of requested data) - DP-->>DC: 3. xApp Shared Data Fetch response (requested data) - -``` - -Sequence diagram for xApp Shared Data Fetch procedure. It shows a 'Data consumer (Near-RT RIC platform or xApp)' sending a '1. xApp Shared Data Fetch request (description of requested data)' to a 'Data producer xApp'. The producer responds with '2. Generate requested data' and '3. xApp Shared Data Fetch response (requested data)'. - -Figure 9.5.7A-1: xApp Shared Data Fetch procedure - -### 9.5.7B Procedures related to xApp Shared Data Subscription and Notification - -#### 9.5.7B.1 Procedures for xApp Shared Data Subscribe/Push - -The xApp Shared Data Subscribe/Push procedures allow the data consumer (Near-RT RIC platform or an xApp) to subscribe to and receive specific shared data from the data producer xApp. - -| Use Case Stage | Evolution / Specification | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | Data consumer (Near-RT RIC platform or xApp) subscribes to and receives shared data from the data producer xApp. | -| Actors and Roles |
  • Data producer xApp;
  • Data consumer: Originator of the xApp Shared Data Subscription request, which may be the Near-RT RIC platform or an xApp.
| -| Pre-conditions |
  • Data producer xApp has successfully registered its xApp Data Sharing service with Near-RT RIC platform;
  • Data consumer has discovered the xApp Data Sharing service.
| -| Begins when | The data consumer determines to subscribe to specific shared data from the data producer xApp. | -| Step 1 (M) | The data consumer sends a subscription request to the data producer xApp for shared data. The request contains the description for the requested data, and the criteria to trigger the data push. | -| Step 2 (M) | The data producer xApp checks whether the data consumer is authorized to access the subscribed data. | -| Step 3 (M) | The data producer xApp accepts the request and stores the subscription record. | -| Step 4 (M) | The data producer xApp responds to the data consumer with the subscription ID. | -| | [LOOP] Step 5 is executed when the criteria to trigger the data push are met. | -| Step 5 (M) | The data producer xApp pushes the subscribed data to the data consumer. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" -Participant consumer as "Data consumer \n(Near-RT RIC platform or xApp)" -Participant ProducerxApp as "Data producer xApp" -End box - -``` - -``` - -consumer -> ProducerxApp: 1. xApp Shared Data Subscription request \n(description of requested -data, criteria to trigger the push) -ProducerxApp -> ProducerxApp: 2. Check authorization -ProducerxApp -> ProducerxApp: 3. Store subscription record -ProducerxApp -> consumer: 4. xApp Shared Data Subscription response \n(subscription ID) -loop Data push is triggered - ProducerxApp -> consumer: 5. xApp Shared Data Push (requested data) -end -@enduml - -``` - -![Sequence diagram illustrating the xApp Shared Data Subscribe/Push procedures. The diagram is contained within a 'Near-RT RIC' frame. It shows two lifelines: 'Data consumer (Near-RT RIC platform or xApp)' and 'Data producer xApp'. The sequence of messages is: 1. xApp Shared Data Subscription request (description of requested data, criteria to trigger the push) from consumer to producer; 2. Check authorization from producer to itself; 3. Store subscription record from producer to itself; 4. xApp Shared Data Subscription response (subscription ID) from producer to consumer; 5. A loop labeled '[Data push is triggered]' containing message 5: xApp Shared Data Push (requested data) from producer to consumer.](17431d8b59408f09df7552d8bdbaa015_img.jpg) - -Sequence diagram illustrating the xApp Shared Data Subscribe/Push procedures. The diagram is contained within a 'Near-RT RIC' frame. It shows two lifelines: 'Data consumer (Near-RT RIC platform or xApp)' and 'Data producer xApp'. The sequence of messages is: 1. xApp Shared Data Subscription request (description of requested data, criteria to trigger the push) from consumer to producer; 2. Check authorization from producer to itself; 3. Store subscription record from producer to itself; 4. xApp Shared Data Subscription response (subscription ID) from producer to consumer; 5. A loop labeled '[Data push is triggered]' containing message 5: xApp Shared Data Push (requested data) from producer to consumer. - -**Figure 9.5.7B.1-1: xApp Shared Data Subscribe/Push procedures** - -#### 9.5.7B.2 xApp Shared Data Subscription Delete procedure - -The xApp Shared Data Subscription Delete procedure allows the data consumer (Near-RT RIC platform or an xApp) to unsubscribe to specific shared data from the data producer xApp. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Data consumer (Near-RT RIC platform or xApp) unsubscribes to shared data from the data producer xApp. | | -| Actors and Roles |
  • Data producer xApp;
  • Data consumer: Originator of the xApp Shared Data Subscription Delete request, which may be the Near-RT RIC platform or an xApp.
| | -| Pre-conditions | The data consumer has subscribed to shared data from the data producer xApp. | | -| Begins when | The data consumer determines to unsubscribe to specific shared data from the data producer xApp. | | -| Step 1 (M) | The data consumer sends a subscription delete request to the data producer xApp. The request contains the subscription ID. | | -| Step 2 (M) | The data producer xApp checks the subscription record associated with the subscription ID and checks whether the data consumer is authorized to unsubscribe. | | -| Step 3 (M) | The data producer xApp deletes the subscription record for the data consumer. | | -| Step 4 (M) | The data producer xApp sends a subscription delete response. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" -Participant consumer as "Data consumer \n(Near-RT RIC platform or xApp)" -Participant ProducerxApp as "Data producer xApp" -End box - -consumer -> ProducerxApp: 1. xApp Shared Data Subscription delete request \n(subscription ID) -ProducerxApp -> ProducerxApp: 2. Check subscription record and authorization -ProducerxApp -> ProducerxApp: 3. Delete the subscription record for the data consumer -ProducerxApp -> consumer: 4. xApp Shared Data Subscription delete response -@enduml - -``` - -![Sequence diagram titled 'Near-RT RIC' showing the interaction between a Data consumer and a Data producer xApp. The Data consumer sends a '1. xApp Shared Data Subscription delete request (subscription ID)' to the Data producer xApp. The Data producer xApp performs internal steps '2. Check subscription record and authorization' and '3. Delete the subscription record for the data consumer', then sends a '4. xApp Shared Data Subscription delete response' back to the Data consumer.](276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg) - -``` - -sequenceDiagram - participant DC as Data consumer (Near-RT RIC platform or xApp) - participant DP as Data producer xApp - Note right of DP: Near-RT RIC - DC->>DP: 1. xApp Shared Data Subscription delete request (subscription ID) - Note right of DP: 2. Check subscription record and authorization - Note right of DP: 3. Delete the subscription record for the data consumer - DP-->>DC: 4. xApp Shared Data Subscription delete response - -``` - -Sequence diagram titled 'Near-RT RIC' showing the interaction between a Data consumer and a Data producer xApp. The Data consumer sends a '1. xApp Shared Data Subscription delete request (subscription ID)' to the Data producer xApp. The Data producer xApp performs internal steps '2. Check subscription record and authorization' and '3. Delete the subscription record for the data consumer', then sends a '4. xApp Shared Data Subscription delete response' back to the Data consumer. - -Figure 9.5.7B.2-1: xApp Shared Data Subscription Delete procedure - -### 9.5.8 Use cases of SDL APIs - -#### 9.5.8.1 Subscribe/Update-Notify for E2NodeInfo and E2NodeList - -The SDL Subscribe/Update-Notify procedure (clause 9.5.4) along with the SDL fetch procedure (clause 9.5.3) may be used for getting notifications and fetching E2 Node related information such as E2NodeList (clause 9.5.9.2) and E2NodeInfo (clause 9.5.9.3) changes (obtained as the result of an E2AP Global Procedure such as: E2 Setup, Reset, E2 Removal, RIC Service Update or E2 Node Configuration Update). - -As noted in clause 9.5.4, notifications will contain only the summary of changes to E2NodeInfo after the subscription. To get the complete state of E2NodeInfo, the xApp may do a fetch. - -| Use Case Stage | Evolution / Specification | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | Inform the xApp about changes to E2 Node information | -| Actors and Roles |
  • E2 Nodes: O-CU, O-DUs supporting the E2 interface.
  • xApps: Requires information about changes to E2 Node information.
  • Near-RT RIC platform:
    • exposing an SDL API to the xApps;
    • Termination of E2 connections.
| -| Pre-conditions |
  • SDL API services have been registered and authorized by Near-RT RIC platform;
  • xApp has successfully registered as a client to the SDL before;
  • xApp has been authorized to read the data in the database.
| -| Begins when | xApp decides it is interested in E2NodeInfo updates. | -| Step 1 (M) | xApp sends request to Near-RT RIC platform to subscribe for notifications related to E2NodeInfo changes. | -| Step 2 (M) | Near-RT RIC platform responds to xApp subscription. | -| Step 3 (M) | E2 Node or Near-RT RIC initiates an E2AP Global procedure (i.e., E2 Setup, Reset, E2 Removal, RIC Service Update or E2 Node Configuration Update). | -| | [OPT] Steps 4-10 are executed if the E2AP Global Procedure succeeds: | -| Step 4 (M) | Near-RT RIC platform updates the Database. | -| Step 5 (M) | Near-RT RIC platform triggers SDL procedure. | -| Step 6 (M) | Near-RT RIC platform retrieves list of xApps that would be interested in this update . | -| | [LOOP] Steps 7-10 are looped for each relevant xApp. | -| Step 7 (M) | Near-RT RIC platform sends a notification of subscribed E2NodeList update or E2NodeInfo update to the xApp which includes the E2NodeID. | -| Step 8 (M) | xApp makes decision on whether to fetch the updated information from the Near-RT RIC platform. | -| | [OPT] Steps 9-10 are executed if the xApp decides that it needs the update: | -| Step 9 (M) | xApp sends a fetch request to the Near-RT RIC platform which includes the E2NodeID. | -| Step 10 (M) | Near-RT RIC platform responds with a fetch response (E2NodeList or E2NodeInfo). | - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid - -box "Near-RT RIC" - Collections "xApp" as xApp - Participant plt as "Near-RT RIC platform" -endbox -Collections "E2 Node" as ran - -xApp -> plt: 1. Subscribe Information Request (Information type, Notify, Filter(O)) -plt -> xApp: 2. Subscribe Information Response -ran <-> plt: 3. <> Global procedure -opt Handling of E2 global procedure succeeds - plt -> plt: 4. Update E2NodeList and/or E2NodeInfo - plt -> plt: 5. Initiate SDL procedure -``` - -``` - -plt -> plt: 6. Retrieve list of xApps relevant for this update -Loop for each xApp in relevant xApps - plt -> xApp: 7. Notification (Information type, Notification unit) - xApp -> xApp: 8. Decide whether to fetch the update from SDL - Opt xApp fetches E2NodeInfo - xApp -> plt: 9. Fetch Request (Information type, Filter) - plt -> xApp: 10. Fetch Response (Information type, Information Unit) - End -End -End -@enduml - -``` - -![Sequence diagram showing the interaction between xApp, Near-RT RIC platform, and E2 Node for E2NodeInfo and E2NodeList procedures. The diagram includes message exchanges for subscription, global procedure handling, and SDL fetches within loops and options.](2b00743506f6a3bbd17af764162dc76d_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - participant E2 Node - - Note over xApp, Near-RT RIC platform: Near-RT RIC - xApp->>Near-RT RIC platform: 1. Subscribe Information Request (Information type, Notify, Filter(O)) - Near-RT RIC platform-->>xApp: 2. Subscribe Information Response - Near-RT RIC platform->>E2 Node: 3. <> Global procedure - - opt Handling of E2 global procedure succeeds - Near-RT RIC platform->>Near-RT RIC platform: 4. Update E2NodeList and/or E2NodeInfo - Near-RT RIC platform->>Near-RT RIC platform: 5. Initiate SDL procedure - Near-RT RIC platform->>Near-RT RIC platform: 6. Retrieve list of xApps relevant for this update - - loop for each xApp in relevant xApps - Near-RT RIC platform->>xApp: 7. Notification (Information type, Notification unit) - xApp->>xApp: 8. Decide whether to fetch the update from SDL - - opt xApp fetches E2NodeInfo - xApp->>Near-RT RIC platform: 9. Fetch Request (Information type, Filter) - Near-RT RIC platform-->>xApp: 10. Fetch Response (Information type, Information Unit) - end - end - end - -``` - -Sequence diagram showing the interaction between xApp, Near-RT RIC platform, and E2 Node for E2NodeInfo and E2NodeList procedures. The diagram includes message exchanges for subscription, global procedure handling, and SDL fetches within loops and options. - -Figure 9.5.8.1-1: Subscribe/Notify procedures for E2NodeInfo and E2NodeList - -#### 9.5.8.2 Subscribe/Push for E2NodeInfo and E2NodeList - -The SDL Subscribe/Push procedure (clause 9.5.7) may be used for getting E2 Node related information pushes such as E2NodeList (clause 9.5.9.2) and E2NodeInfo (clause 9.5.9.3) (obtained as the result of an E2 Global procedure such as E2 Setup, Reset, E2 Removal, RIC Service Update or E2 Node Configuration Update). - -As noted in clause 9.5.7, the pushes may contain only the changed to E2 Node related information after the subscription, or a complete set of E2 Node related information. - -| Use Case Stage | Evolution/Specification | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | Inform the xApp about changes to E2 Node information. | -| Actors and Roles |
  • E2 Nodes: O-CU, O-DUs supporting the E2 interface;
  • xApps: Requires information about changes to E2 Node information;
  • Near-RT RIC platform:
    • exposing an SDL API to the xApps;
    • Termination of E2 node connections.
| -| Pre-conditions |
  • SDL API services have been registered and authorized by Near-RT RIC platform;
  • xApp has successfully registered as a client to the SDL before;
  • xApp has been authorized to read the data in the database.
| -| Begins when | xApp decides it is interested in E2NodeInfo updates. | -| Step 1 (M) | xApp sends request to Near-RT RIC platform to subscribe for pushes related to E2NodeList and/or E2NodeInfo. | -| Step 2 (M) | Near-RT RIC platform responds to xApp subscription. | -| Step 3 (M) | E2 Node or Near-RT RIC initiates an E2AP Global Procedure (i.e., E2 Setup, Reset, E2 Removal, RIC Service Update or E2 Node Configuration Update). | -| | [OPT] Steps 4-7 are executed if the E2AP Global procedure succeeds: | -| Step 4 (M) | Near-RT RIC platform updates the Database. | -| Step 5 (M) | Near-RT RIC platform triggers SDL procedure. | -| Step 6 (M) | Near-RT RIC platform retrieves list of xApps that would be interested in this update. | -| Step 7 (M) | For each relevant xApp, Near-RT RIC platform sends a push of E2NodeList or E2NodeInfo to the xApp which includes the E2NodeID. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam lifelineStrategy solid - -box "Near-RT RIC" -Collections "xApp" as xApp -Participant plt as "Near-RT RIC platform" -endbox -Collections "E2 Node" as ran - -xApp -> plt: 1. Subscribe Information Request (Information type, Push, Filter(0)) -plt -> xApp: 2. Subscribe Information Response -ran -> plt: 3. <> Global Procedure -opt Handling of E2 global procedure succeeds - plt -> plt: 4. Update E2NodeList and/or E2NodeInfo - plt -> plt: 5. Initiate SDL procedure - plt --> plt: 6. Retrieve list of xApps relevant for this update - Loop for each xApp in relevant xApps - plt -> xApp: 7. Push (Information type, Information unit) - End -End -@enduml - -``` - -![Sequence diagram showing Subscribe/Push procedures for E2NodeInfo and E2NodeList. Lifelines: xApp, Near-RT RIC platform, and E2 Node. The process involves subscription, global procedure handling, and subsequent data pushing to relevant xApps.](0b2ee589f5c7802f3d332f421340cae1_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - participant E2 Node - - Note over xApp, Near-RT RIC platform: Near-RT RIC - - xApp->>Near-RT RIC platform: 1. Subscribe Information Request (Information type, Push, Filter(O)) - Near-RT RIC platform-->>xApp: 2. Subscribe Information Response - E2 Node->>Near-RT RIC platform: 3. <> Global Procedure - - opt Handling of E2 global procedure succeeds - Near-RT RIC platform->>Near-RT RIC platform: 4. Update E2NodeList and/or E2NodeInfo - Near-RT RIC platform->>Near-RT RIC platform: 5. Initiate SDL procedure - Near-RT RIC platform-->>xApp: 6. Retrieve list of xApps relevant for this update - - loop for each xApp in relevant xApps - Near-RT RIC platform->>xApp: 7. Push (Information type, Information unit) - end - end - -``` - -Sequence diagram showing Subscribe/Push procedures for E2NodeInfo and E2NodeList. Lifelines: xApp, Near-RT RIC platform, and E2 Node. The process involves subscription, global procedure handling, and subsequent data pushing to relevant xApps. - -Figure 9.5.8.2-1: Subscribe/Push procedures for E2NodeInfo and E2NodeList - -#### 9.5.8.3 xApp data sharing for RAN analytics information exposure - -An xApp may act as a producer of some types of RAI. Such RAI may be exposed to the Near-RT RIC platform, and further exposed via Y1 interface. In this use case, the Near-RT RIC platform uses the xApp Shared Data Subscribe/Push procedures or the xApp Shared Data Fetch procedure to collect RAI from the RAI producer xApp. - -A) using xApp Shared Data Subscribe/Push procedures - -| Use Case Stage | Evolution / Specification | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | Near-RT RIC platform exposes via Y1 interface the RAI produced by the xApp. | -| Actors and Roles |
  • Y1 consumer
  • xApp: Producer of RAI.
  • Near-RT RIC platform, with the following functionalities:
    • Y1 termination;
    • API enablement.
| -| Pre-conditions |
  • RAI producer xApp has registered the API information of its xApp Data Sharing API information using the Enablement APIs;
  • Y1 consumer has been provided with the supported RAI types.
| -| Begins when | Y1 consumer determines to subscribe to specific RAI from the Near-RT RIC. | -| Step 1 (M) | Y1 consumer requests RAI with a Y1 RAI subscription request to Near-RT RIC platform. | -| Step 2 (M) | Near-RT RIC platform decides how to handle the request. | -| | [ALT] Steps 3-10 are executed if Near-RT RIC platform decides to initiate xApp Shared Data Subscribe/Push procedures with the RAI producer xApp. | -| Step 3 (O) | Near-RT RIC platform queries the API information registered by the RAI producer xApp. | -| Step 4 (M) | Near-RT RIC platform forwards the RAI request to the RAI producer xApp with an xApp Shared Data subscription request. | -| Step 5 (M) | RAI producer xApp configures collection of necessary data (e.g., by creating E2 subscriptions and/or A1-EI subscription). | -| Step 6 (M) | RAI producer xApp responds to Near-RT RIC platform with an xApp Shared Data subscription response. | -| Step 7 (M) | Near-RT RIC platform responds to Y1 consumer with a Y1 RAI subscription response, which contains the result in Step 5. | -| | [LOOP] Steps 8-10 are executed when RAI report is needed. | -| Step 8 (M) | RAI producer xApp collects necessary data and generates RAI. | -| Step 9 (M) | RAI producer xApp sends RAI to the Near-RT RIC platform with an xApp Shared Data Push. | -| Step 10 (M) | Near-RT RIC platform forwards the RAI to Y1 consumer. | -| | [ELSE] Steps 11-13 are executed if Near-RT RIC platform decides to handle the request by other means (e.g., reusing an existing xApp Shared Data subscription, or using xApp Shared Data Fetch). | -| Step 11 (M) | Near-RT RIC platform sends the response to Y1 consumer with a Y1 RAI subscription response. | -| | [LOOP] Steps 12-13 are executed when RAI report is needed. | -| Step 12 (M) | Near-RT RIC platform obtains RAI. | -| Step 13 (M) | Near-RT RIC platform forwards the RAI to Y1 consumer. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Participant xApp - Participant plt as "Near-RT RIC platform" -End box -Participant Ylc as "Y1 consumer" - -Ylc -> plt: 1. <> RAI subscription request (description of requested RAI) -plt -> plt: 2. Near-RT RIC platform decides the proper handling -alt Near-RT RIC platform decides to initiate xApp Shared Data Subscribe/Push procedures -opt - plt -> plt: 3. Query API information -end -plt -> xApp: 4. xApp Shared Data subscription request (description of requested RAI) -rnote over plt, xApp #F0F0F0: 5. xApp configures collection of necessary data -xApp -> plt: 6. xApp Shared Data subscription response - -``` - -``` - -plt -> Y1c: 7. <> RAI subscription response -Loop RAI report is needed - rnote over plt, xApp #F0F0F0: 8. xApp collects necessary data and generate RAI - xApp -> plt: 9. xApp Shared Data push (requested RAI) - plt -> Y1c: 10. <> RAI notification (requested RAI) -end -else Near-RT RIC platform decides to handle the request by other means -plt -> Y1c: 11. <> RAI subscription response -Loop RAI report is needed - rnote over plt, xApp #F0F0F0: 12. Near-RT RIC platform obtains RAI - plt -> Y1c: 13. <> RAI notification (requested RAI) -end -end -@enduml - -``` - -![Sequence diagram showing xApp Shared Data Subscribe/Push procedures for RAN analytics information exposure. Lifelines: xApp, Near-RT RIC platform, Y1 consumer. The diagram includes an 'alt' block for platform decision and 'loop' blocks for RAI report handling.](9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg) - -``` - -sequenceDiagram - participant Y1c as Y1 consumer - subgraph Near-RT RIC - participant xApp - participant plt as Near-RT RIC platform - end - Note right of plt: Loop RAI report is needed - Note right of plt: Loop RAI report is needed - - Y1c->>plt: 1. <> RAI subscription request (description of requested RAI) - plt-->>Y1c: 2. Near-RT RIC platform decides the proper handling - - alt Near-RT RIC platform decides to initiate xApp Shared Data Subscribe/Push procedures - opt Query API information - plt-->>plt: 3. Query API information - end - plt->>xApp: 4. xApp Shared Data subscription request (description of requested RAI) - Note right of xApp: 5. xApp configures collection of necessary data - xApp->>plt: 6. xApp Shared Data subscription response - plt->>Y1c: 7. <> RAI subscription response - loop RAI report is needed - Note right of xApp: 8. xApp collects necessary data and generate RAI - xApp->>plt: 9. xApp Shared Data push (requested RAI) - plt->>Y1c: 10. <> RAI notification (requested RAI) - end - else Near-RT RIC platform decides to handle the request by other means - plt->>Y1c: 11. <> RAI subscription response - loop RAI report is needed - Note right of plt: 12. Near-RT RIC platform obtains RAI - plt->>Y1c: 13. <> RAI notification (requested RAI) - end - end - -``` - -Sequence diagram showing xApp Shared Data Subscribe/Push procedures for RAN analytics information exposure. Lifelines: xApp, Near-RT RIC platform, Y1 consumer. The diagram includes an 'alt' block for platform decision and 'loop' blocks for RAI report handling. - -Figure 9.5.8.3-1: xApp Shared Data Subscribe/Push procedures for RAN analytics information exposure - -B) using xApp Shared Data Fetch procedure - -| Use Case Stage | Evolution / Specification | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | Near-RT RIC platform exposes via Y1 interface the RAI produced by the xApp. | -| Actors and Roles |
  • Y1 consumer
  • xApp: Producer of RAI.
  • Near-RT RIC platform, with the following functionalities:
    • Y1 termination;
    • API enablement.
| -| Pre-conditions |
  • RAI producer xApp has registered the API information of its xApp Data Sharing API information using the Enablement APIs;
  • Y1 consumer has been provided with the supported RAI types.
| -| Begins when | Y1 consumer determines to query specific RAI from the Near-RT RIC. | -| Step 1 (M) | Y1 consumer requests RAI with a Y1 RAI query request to Near-RT RIC platform. | -| Step 2 (M) | Near-RT RIC platform decides how to handle the request. | -| | [ALT] Steps 3-7 are executed if Near-RT RIC platform decides to initiate xApp Shared Data Fetch procedure with the RAI producer xApp. | -| Step 3 (O) | Near-RT RIC platform queries the API information registered by the RAI producer xApp. | -| Step 4 (M) | Near-RT RIC platform forwards the RAI request to the RAI producer xApp with an xApp Shared Data Fetch request. | -| Step 5 (M) | RAI producer xApp collects necessary data and generates RAI. | -| Step 6 (M) | RAI producer xApp sends the RAI to Near-RT RIC platform with an xApp Shared Data Fetch response. | -| Step 7 (M) | Near-RT RIC platform forwards the RAI to Y1 consumer with a Y1 RAI query response. | -| | [ELSE] Steps 8-9 are executed if Near-RT RIC platform decides to handle the request by other means (e.g., using/reusing an xApp Shared Data subscription). | -| Step 8 (M) | Near-RT RIC platform obtains RAI. | -| Step 9 (M) | Near-RT RIC platform forwards the RAI to Y1 consumer with a Y1 RAI query response. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Participant xApp - Participant plt as "Near-RT RIC platform" -End box -Participant Ylc as "Y1 consumer" - -Ylc -> plt: 1. <> RAI query request (description of requested RAI) -plt -> plt: 2. Near-RT RIC platform decides the proper handling -alt Near-RT RIC platform decides to initiate xApp Shared Data Fetch procedure - opt - plt -> plt: 3. Query API information - end - plt -> xApp: 4. xApp Shared Data Fetch request (description of requested RAI) - rnote over plt, xApp #F0F0F0: 5. xApp collects necessary data and generates RAI - xApp -> plt: 6. xApp Shared Data fetch response (requested RAI) - plt -> Ylc: 7. <> RAI query response (requested RAI) -else Near-RT RIC platform decides to handle the request by other means - rnote over plt, xApp #F0F0F0: 8. Near-RT RIC platform obtains RAI - plt -> Ylc: 9. <> RAI query response (requested RAI) -end -@enduml - -``` - -![Sequence diagram illustrating the xApp Shared Data Fetch procedure for RAN analytics information exposure. The diagram shows interactions between an xApp, a Near-RT RIC platform, and a Y1 consumer. The process starts with a RAI query request from the Y1 consumer to the Near-RT RIC platform. The platform decides on handling, potentially initiating an xApp Shared Data Fetch procedure. This involves an optional step to query API information, followed by an SDL API request from the platform to the xApp. The xApp collects data and generates a RAI, responding via an SDL API response. Finally, the platform sends a RAI query response to the Y1 consumer. An alternative path shows the platform obtaining the RAI by other means and then responding to the Y1 consumer.](80a44321a02e8a7d638ac9d53e88772c_img.jpg) - -``` - -sequenceDiagram - participant Y1_consumer as Y1 consumer - participant Near-RT_RIC_platform as Near-RT RIC platform - participant xApp - - Note left of Near-RT_RIC_platform: Near-RT RIC - Note right of Y1_consumer: Y1 consumer - - Y1_consumer->>Near-RT_RIC_platform: 1. <> RAI query request (description of requested RAI) - Near-RT_RIC_platform-->>Near-RT_RIC_platform: 2. Near-RT RIC platform decides the proper handling - - alt Near-RT RIC platform decides to initiate xApp Shared Data Fetch procedure - opt Query API information - Near-RT_RIC_platform-->>Near-RT_RIC_platform: 3. Query API information - end - Near-RT_RIC_platform->>xApp: 4. xApp Shared Data Fetch request (description of requested RAI) - Note over xApp: 5. xApp collects necessary data and generates RAI - xApp->>Near-RT_RIC_platform: 6. xApp Shared Data fetch response (requested RAI) - Near-RT_RIC_platform->>Y1_consumer: 7. <> RAI query response (requested RAI) - else Near-RT RIC platform decides to handle the request by other means - Note over Near-RT_RIC_platform: 8. Near-RT RIC platform obtains RAI - Near-RT_RIC_platform->>Y1_consumer: 9. <> RAI query response (requested RAI) - end - -``` - -Sequence diagram illustrating the xApp Shared Data Fetch procedure for RAN analytics information exposure. The diagram shows interactions between an xApp, a Near-RT RIC platform, and a Y1 consumer. The process starts with a RAI query request from the Y1 consumer to the Near-RT RIC platform. The platform decides on handling, potentially initiating an xApp Shared Data Fetch procedure. This involves an optional step to query API information, followed by an SDL API request from the platform to the xApp. The xApp collects data and generates a RAI, responding via an SDL API response. Finally, the platform sends a RAI query response to the Y1 consumer. An alternative path shows the platform obtaining the RAI by other means and then responding to the Y1 consumer. - -**Figure 9.5.8.3-2: xApp Shared Data Fetch procedure for RAN analytics information exposure** - -### 9.5.9 SDL API data structures - -#### 9.5.9.1 Overview - -The following data structures are defined: - -- E2NodeList: List of known E2 Node ID and the associated E2 Node State -- E2NodeInfo: E2 Node component configuration list and RAN function list - -E2NodeList and E2NodeInfo are used to inform xApps of change to E2 Node state and information as the result of E2AP Global Procedures. The relationship between these data structures and E2AP Global Procedures is described in table 9.5.9.1-1. - -Table 9.5.9.1-2 presents the actions that xApp may perform under different E2 Node State conditions. - -NOTE 1: E2AP Error Indication procedure does not result in a change to SDL API data as most error cases are assumed to be handled internally within the Near-RT RIC platform. An appropriate E2 Related API (Failure, Cause) message may be used to inform xApp if required. - -NOTE 2: E2AP Reset procedure handling is assumed to be assisted by an appropriate platform mechanism with the Near-RT RIC first using the appropriate SDL API mechanism (see clause 9.5.8) to inform xApp that a RESET has occurred (i.e., E2 Node State = "Reset") and then a second SDL API mechanism is used to inform xApp that the E2 Node is again available (i.e. E2 Node State = "Connected"). It is assumed that the Near-RT RIC platform will delete all associated subscription records during the period between these two SDL API mechanisms and that xApp will use the information E2 Node is again available (i.e., E2 Node State = "Connected") to trigger any required E2 Subscription (Request) messages to re-establish E2 subscriptions. - -NOTE 3: E2AP E2 Removal procedure handling and E2 link failure handling are assumed to be assisted by an appropriate platform mechanism with the Near-RT RIC using the appropriate SDL API mechanism (see clause 9.5.8) to inform xApp that the E2 Node is not available (i.e., E2 Node State = "Disconnect"). - -**Table 9.5.9.1-1: SDL API handling of E2AP Global procedures** - -| Global procedure | E2NodeList change | E2NodeInfo change | -|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| -| E2 Setup | Add E2NodeList record (E2 Node ID, E2 Node State = "Connected") | Add E2NodeInfo record (E2 Node ID, RAN Function list, E2 Node component configuration list) | -| Reset | Change E2NodeList record (E2 Node State = "Reset").
After using an appropriate Near-RT RIC mechanism, Change E2NodeList record (E2 Node State to "Connected") | - | -| RIC Service Update | - | Add, Modify and/or Remove E2NodeInfo record (E2 Node ID, RAN Function List) | -| E2 Node Configuration Update | - | Add, Modify and/or Remove E2NodeInfo record (E2 Node ID, E2 Node Component configuration list) | -| E2 Removal | Change E2NodeList record (E2 Node State = "Disconnected").
After Delete E2NodeInfo record , Delete E2NodeList record (E2 Node ID) | Delete E2NodeInfo record (E2 Node ID) | -| E2 link failure | Change E2NodeList record (E2 Node State = "Disconnected").
After Delete E2NodeInfo record , Delete E2NodeList record (E2 Node ID) | Delete E2NodeInfo record (E2 Node ID) | - -**Table 9.5.9.1-2: Expected xApp responses to E2 Node State** - -| E2 Node State | xApp actions | -|---------------|-----------------------------------------------------------------------------------------------------------------------------------| -| Connected | Discover E2 Node ID in E2NodeList and obtain E2NodeInfo (after E2 Setup).
Initiate E2 Related APIs (after E2 Setup and Reset). | -| Reset | Delete internal records of ongoing E2 Related API procedures.
Monitor for changes in E2 Node State. | -| Disconnected | Delete internal records of ongoing E2 Related API procedures.
Delete internal records of E2 Node ID. | - -#### 9.5.9.2 E2NodeList - -The E2NodeList data structure contains a list of known E2 Nodes and the associated E2 Node State. Each record contains: - -- E2 Node ID -- E2 Node State ("Connected", "Reset", "Disconnected") - -E2NodeList records may be deleted when the corresponding E2NodeInfo record has been deleted. It is recommended to maintain this record for sufficient time for all xApps to complete clean-up mechanisms. - -#### 9.5.9.3 E2NodeInfo - -The E2NodeInfo data structure contains information on a given E2 Node. Each record contains: - -- E2 Node ID -- List of declared E2 Node component configuration information -- List of declared RAN Functions - -E2NodeInfo records shall be deleted after corresponding E2NodeState is set to "Disconnected" and sufficient time has been allowed for all xApps to complete clean-up mechanisms. - -## 9.6 API Enablement Procedures - -### 9.6.1 API Discovery procedure - -This procedure enables the xApp(s) to discover the available Near-RT RIC APIs. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To allow the xApp to discover which APIs are available and how to access them. | | -| Actors and Roles |
  • xApp: Requester of the available Near-RT RIC APIs.
  • Near-RT RIC platform, with the following functionalities:
    • API Enablement;
    • Database
| | -| Assumptions | For initiating the discovery, the xApp has registered to Near-RT RIC platform and is aware of the API information of the Enablement APIs. | | -| Pre conditions |
  • The xApp is deployed to Near-RT RIC platform.
  • The API information of Enablement APIs has been provided to the xApp (as pre-configuration by SMO or by other means).
  • One or more Near-RT RIC platform services are configured to provide their API information with the API Enablement functionality.
| | -| Begins when | xApps wants to discover the available Near-RT RIC APIs. | | -| Step 1 (M) | xApp sends a API discovery request to the Near-RT RIC platform. It includes the xApp identity and includes query information. Query information may include criteria for discovering matching APIs. | | -| Step 2 (M) | Near-RT RIC platform verifies the identity of the xApp. | | -| Step 3 (M) | Near-RT RIC platform searches the stored Near-RT RIC API(s) information, as per the query information in the discovery request. | | -| Step 4 (M) | Near-RT RIC platform applies the discovery policy and performs filtering of the retrieved Near-RT RIC APIs information. | | -| Step 5 (M) | The Near-RT RIC platform sends a API discovery response to the xApp with the API information about the APIs for which the xApp has the required authorization. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" -Participant xApp as "xApp" -Participant plt as "Near-RT RIC platform" -End box - -plt -> plt: Near-RT RIC platform service available -plt -> plt: Store API information -... - -xApp -> plt: 1. API discovery request -plt -> plt: 2. Near-RT RIC platform verifies the identity of the xApp -plt -> plt: 3. Search stored API information -plt -> plt: 4. Apply discovery policy \nand information filtering -plt -> xApp: 5. API discovery response - -``` - -@endum1 - -![Sequence diagram titled 'Near-RT RIC' showing the API Discovery procedure between an xApp and the Near-RT RIC platform. The sequence starts with the xApp sending an 'API discovery request' to the platform. The platform responds with a series of internal steps: 'Near-RT RIC platform service available', 'Store API information', 'Near-RT RIC platform verifies the identity of the xApp', 'Search stored API information', and 'Apply discovery policy and information filtering'. Finally, the platform sends an 'API discovery response' back to the xApp.](3ec35c497a0765a1a885c85f214b1bef_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - Note right of Near-RT RIC platform: Near-RT RIC platform service available - Note right of Near-RT RIC platform: Store API information - xApp->>Near-RT RIC platform: 1. API discovery request - Note right of Near-RT RIC platform: 2. Near-RT RIC platform verifies the identity of the xApp - Note right of Near-RT RIC platform: 3. Search stored API information - Note right of Near-RT RIC platform: 4. Apply discovery policy and information filtering - Near-RT RIC platform-->>xApp: 5. API discovery response - -``` - -Sequence diagram titled 'Near-RT RIC' showing the API Discovery procedure between an xApp and the Near-RT RIC platform. The sequence starts with the xApp sending an 'API discovery request' to the platform. The platform responds with a series of internal steps: 'Near-RT RIC platform service available', 'Store API information', 'Near-RT RIC platform verifies the identity of the xApp', 'Search stored API information', and 'Apply discovery policy and information filtering'. Finally, the platform sends an 'API discovery response' back to the xApp. - -Figure 9.6.1-1: API Discovery procedure - -### 9.6.2 Procedures related to API Event Subscription and Notification - -In this clause, the procedures for subscription / subscription deletion and API event notification are provided. These procedures allow the xApps to receive information on API related events. - -Such events correspond to Near-RT RIC API related events like the following: - -| Events | Events Description | -|----------------------------------|------------------------------------------------------------------| -| Availability of Near-RT RIC APIs | Availability events of Near-RT RIC APIs (e.g., active, inactive) | -| Near-RT RIC API updated | Events related to change in Near-RT RIC API information | - -#### 9.6.2.1 Procedure for API Event Subscription - -The purpose of this procedure is to enable xApps to subscribe to monitor events related to the provided Near-RT RIC APIs. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To allow the xApp to subscribe to receive Near-RT RIC API related event notifications. | | -| Actors and Roles |
  • xApp: Requester to subscribe to notifications of events related to the Near-RT RIC APIs;
  • Near-RT RIC platform, with the following functionalities:
    • API enablement.
    • Database
| | -| Assumptions |
  • For initiating the subscription, the xApp has registered to RIC platform and is aware of the API information of Enablement APIs. Also, xApp has discovered the provided Near-RT RIC APIs.
| | -| Pre-conditions |
  • The xApp is registered to Near-RT RIC platform;
  • The API information of Enablement APIs has been provided to the xApp (as pre-configuration by SMO);
  • The xApp has discovered the registered Near-RT RIC APIs (see 9.6.1).
| | -| Begins when | xApp has discovered the available Near-RT RIC APIs and wants to subscribe for event notifications. | | -| Step 1 (M) | xApp sends an API event subscription request to the Near-RT RIC platform in order to receive notification of events. This request includes the subscribing xApp identifier as well as the event criteria:
  • Event criteria may include event type information, e.g., API failure event, new API available event, API unavailable event, API version change event, API location change event, etc.
| | -| Step 2 (M) | The Near-RT RIC platform checks whether the xApp is authorized to monitor the requested event(s). | | -| Step 3 (M) | The Near-RT RIC platform stores the approved subscription information. | | -| Step 4 (M) | The Near-RT RIC platform sends an API event subscription response to the xApp. This response indicates the success or failure of the event subscription operation. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Participant xApp as "xApp" - Participant plt as "Near-RT RIC platform" -End box - -xApp -> plt: 1. API event subscription request -plt -> plt: 2. Check authorization for API event subscription -plt -> plt: 3. Store event subscription -plt -> xApp: 4. API event subscription response - -@enduml - -``` - -![Sequence diagram titled 'Near-RT RIC' showing the interaction between an xApp and the Near-RT RIC platform for API event subscription. The sequence consists of four steps: 1. xApp sends an API event subscription request to the platform; 2. The platform checks authorization; 3. The platform stores the subscription; 4. The platform sends a response (success or failure) back to the xApp.](7c95e83c84169180406fac40d27d6e61_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Platform as Near-RT RIC platform - Note over xApp, Platform: Near-RT RIC - xApp->>Platform: 1. API event subscription request - Platform->>Platform: 2. Check authorization for API event subscription - Platform->>Platform: 3. Store event subscription - Platform-->>xApp: 4. API event subscription response (success or failure) - -``` - -Sequence diagram titled 'Near-RT RIC' showing the interaction between an xApp and the Near-RT RIC platform for API event subscription. The sequence consists of four steps: 1. xApp sends an API event subscription request to the platform; 2. The platform checks authorization; 3. The platform stores the subscription; 4. The platform sends a response (success or failure) back to the xApp. - -Figure 9.6.2.1-1: Subscription for API-related events - -#### 9.6.2.2 Procedure for API Event Subscription Delete - -The purpose of this procedure is to enable xApps to un-subscribe from events monitoring related to the provided Near-RT RIC APIs. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To allow the xApp to un-subscribe from Near-RT RIC API related event notifications. | | -| Actors and Roles |
  • xApp: Requester to un-subscribe from monitoring events related to the Near-RT RIC APIs;
  • Near-RT RIC platform, with the following functionalities:
    • API Enablement.
    • Database
| | -| Assumptions | For initiating the subscription delete, the xApp has registered to Near-RT RIC platform and is aware of the API information of the Enablement APIs. Also, xApp has subscribed to events. | | -| Pre-conditions | The xApp has subscribed to Near-RT RIC API related events (see 9.6.2.1). | | -| Begins when | xApp wants to un-subscribe for Near-RT RIC API related events. | | -| Step 1 (M) | xApp sends an API event subscription delete request to the Near-RT RIC platform with the information of the subscribed event and includes the xApp identifier and the event subscription identifier. | | -| Step 2 (M) | The Near-RT RIC platform, upon receiving the API event subscription delete request from the xApp, checks for the API event subscription corresponding to the xApp and further checks if the subscribing entity is authorized to un-subscribe. | | -| Step 3 (M) | Near-RT RIC platform deletes the subscription information for the xApp. | | -| Step 4 (M) | The API Enablement sends an API event subscription delete response to the xApp. This response indicates the success or failure of the event subscription delete operation. | | - -``` -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -``` - -``` - -skinparam lifelineStrategy solid - -Box "Near-RT RIC" -Participant xApp as "xApp" -Participant plt as "Near-RT RIC platform" -End box - -xApp ->plt: 1. API event subscription delete request -plt -> plt: 2. Check authorization for API event subscription -plt -> plt: 3. Delete the record of the API event subscription -plt -> xApp: 4. API event subscription delete response \n(success or failure) - -@enduml - -``` - -![Sequence diagram titled 'Near-RT RIC' showing the interaction between xApp and Near-RT RIC platform for subscription deletion. The diagram shows four steps: 1. xApp sends a request to the platform; 2. The platform checks authorization; 3. The platform deletes the record; 4. The platform sends a response back to xApp.](684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg) - -``` - -sequenceDiagram - box Near-RT RIC - participant xApp - participant plt as Near-RT RIC platform - end - xApp->>plt: 1. API event subscription delete request - plt->>plt: 2. Check authorization for API event subscription - plt->>plt: 3. Delete the record of the API event subscription - plt->>xApp: 4. API event subscription delete response (success or failure) - -``` - -Sequence diagram titled 'Near-RT RIC' showing the interaction between xApp and Near-RT RIC platform for subscription deletion. The diagram shows four steps: 1. xApp sends a request to the platform; 2. The platform checks authorization; 3. The platform deletes the record; 4. The platform sends a response back to xApp. - -**Figure 9.6.2.2-1: Subscription Delete for API-related events** - -#### 9.6.2.3 Procedure for API Event Notification - -This procedure shows sending the event notification to the subscribed xApp, based on a trigger event captured at the Near-RT RIC platform. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To notify the xApp on events related to the Near-RT RIC APIs, based on subscription. | | -| Actors and Roles |
  • xApp: Receiving event notifications based on subscription;
  • Service producer xApp: Initiating API Registration, API Registration update or API Deregistration procedure
  • Near-RT RIC platform, with the following functionalities:
    • API Enablement
    • Database
| | -| Assumptions | For receiving a notification, the xApp has registered to Near-RT RIC platform and has subscribed to events. | | -| Pre-conditions | The xApp has subscribed to Near-RT RIC API related events (see 9.6.2.1). | | -| Begins when | A trigger event criterion is met at the Near-RT RIC platform (i.e., API information update from a Near-RT RIC platform service and/or Service producer xApp). Such criterion has been configured during subscription of the xApp. | | -| Step 1 (M) | Near-RT RIC platform checks corresponding event subscriptions | | -| Step 2 (M) | Near-RT RIC platform generates an event related to APIs, which is to be consumed by the subscribed xApp(s) | | -| Step 3 (M) | The Near-RT RIC platform sends event notifications to all the subscribing xApp(s) that have subscribed for the event matching the criteria. | | -| Step 4 (O) | The xApp may send an event notification acknowledgement to Near-RT RIC platform. It depends on the capabilities of the transport used for notifications whether or not such acknowledgement can be sent. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Collections PxApp as "Service Producer xApp" - Participant xApp as "xApp" - Participant plt as "Near-RT RIC platform" -End box - -PxApp <--> plt: API Registration procedure -PxApp <--> plt: API Registration Update procedure -PxApp <--> plt: API Deregistration procedure -plt -> plt: API information update - -plt -> plt: 1. Check stored event subscription information -plt -> plt: 2. Event notification information generation -plt -> xApp: 3. API Event notification -plt <-- xApp: 4. API Event notification ACK - -@enduml - -``` - -![Sequence diagram titled 'Near-RT RIC' showing API Event Notification. Lifelines: Service Producer xApp, xApp, and Near-RT RIC platform. The diagram shows registration, update, and deregistration procedures, followed by an API information update process involving checking subscriptions, generating notifications, and sending them to the xApp.](8159756d3acf4761a73fa0d263f1d338_img.jpg) - -``` - -sequenceDiagram - participant SP as Service Producer xApp - participant X as xApp - participant NRP as Near-RT RIC platform - - Note over NRP: API information update - NRP->>NRP: 1. Check stored event subscription information - NRP->>NRP: 2. Event notification information generation - NRP->>X: 3. API Event notification - X->>NRP: 4. API Event notification ACK - - Note over SP: - SP->>NRP: API Registration procedure - SP->>NRP: API Registration Update procedure - SP->>NRP: API Deregistration procedure - -``` - -Sequence diagram titled 'Near-RT RIC' showing API Event Notification. Lifelines: Service Producer xApp, xApp, and Near-RT RIC platform. The diagram shows registration, update, and deregistration procedures, followed by an API information update process involving checking subscriptions, generating notifications, and sending them to the xApp. - -Figure 9.6.2.3-1: API Event Notification - -### 9.6.3 Procedures related to API Registration - -#### 9.6.3.1 API Registration procedure - -This procedure enables the xApp to register as a service producer. - -| Use Case Stage | Evolution / Specification | <<Uses>>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------| -| Goal | To allow the xApp to register as a Near-RT RIC API service producer and provide information on how to access the service. | | -| Actors and Roles |
  • Service Producer xApp: Producer of a Near-RT RIC API.
  • xApp: Receiving event notifications based on subscription;
  • Near-RT RIC platform, with the following functionalities:
    • API Enablement;
    • Database
| | -| Assumptions | For initiating the API Registration procedure, the xApp has registered as an xApp to Near-RT RIC platform and is aware of the API information of the Enablement APIs. | | -| Pre conditions |
  • The xApp is deployed to Near-RT RIC platform.
  • The API information of Enablement APIs has been provided to the xApp (as pre-configuration by SMO or by other means).
  • The xApp is configured and authorized to consume API Registration service
| | -| Begins when | xApps wants to register as a producer of a service in the Near RT RIC. | | -| Step 1 (M) | xApp sends an API Registration request to the Near-RT RIC platform. It includes the xApp identity and supported API information. | | -| Step 2 (M) | Near-RT RIC platform verifies the identity of the xApp. | | -| Step 3 (M) | Near-RT RIC platform verifies that the xApp is authorized to act as a Service Producer. | | -| Step 4 (M) | Near-RT RIC platform adds stored API information. | | -| Step 5 (M) | The Near-RT RIC platform sends API Registration response to the xApp. This response indicates the success or failure of the API Registration operation. | | -| Ends with | Near-RT RIC platform may initiate API Event notification procedure towards one or more other xApps that had previously established a corresponding API Event Subscription. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" -Collections xApp as "xApp" -Participant PxApp as "Service Producer xApp" -Participant plt as "Near-RT RIC platform" -End box - -plt -> plt: Near-RT RIC platform service available -... - -PxApp -> plt: 1. API Registration request -plt -> plt: 2. Near-RT RIC platform verifies \nthe identity of the xApp -plt -> plt: 3. Near-RT RIC platform verifies \nthat xApp may act as Service Producer -plt -> plt: 4. Store API information -plt -> PxApp: 5. API Registration response \n(Success or Failure) -... -plt -> xApp: API Event Notification -@enduml - -``` - -![Sequence diagram for API Registration procedure. Lifelines: xApp, Service Producer xApp, and Near-RT RIC platform. The process involves an API Registration request from Service Producer xApp to Near-RT RIC platform, followed by identity and producer verification, API information storage, and a response. An API Event Notification is then sent from the platform to the xApp.](b54b769d67164910c7c5b2a0ea74257b_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Service Producer xApp - participant Near-RT RIC platform - Note right of Near-RT RIC platform: Near-RT RIC platform service available - Service Producer xApp->>Near-RT RIC platform: 1. API Registration request - Near-RT RIC platform-->>Service Producer xApp: 2. Near-RT RIC platform verifies the identity of the xApp - Near-RT RIC platform-->>Service Producer xApp: 3. Near-RT RIC platform verifies that xApp may act as Service Producer - Near-RT RIC platform-->>Service Producer xApp: 4. Store API information - Near-RT RIC platform-->>Service Producer xApp: 5. API Registration response (Success or Failure) - Near-RT RIC platform-->>xApp: API Event Notification - -``` - -Sequence diagram for API Registration procedure. Lifelines: xApp, Service Producer xApp, and Near-RT RIC platform. The process involves an API Registration request from Service Producer xApp to Near-RT RIC platform, followed by identity and producer verification, API information storage, and a response. An API Event Notification is then sent from the platform to the xApp. - -Figure 9.6.3.1-1: API Registration procedure - -#### 9.6.3.2 API Registration Update procedure - -This procedure enables a previously registered xApp service producer to update API information. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To allow the xApp to update provided service and/or information on how to access the services it produces. | | -| Actors and Roles |
  • Service Producer xApp: Producer of a Near-RT RIC API.
  • xApp: Receiving event notifications based on subscription;
  • Near-RT RIC platform, with the following functionalities:
    • API Enablement;
    • Database
| | -| Assumptions | For initiating the API Registration Update procedure, the xApp has registered to Near-RT RIC platform and is aware of the API information of the Enablement APIs. | | -| Pre conditions |
  • The xApp is deployed to Near-RT RIC platform.
  • The API information of Enablement APIs has been provided to the xApp (as pre-configuration by SMO or by other means).
  • The xApp has previously completed API Registration procedure
| | -| Begins when | xApps wants to update information concerning a Near-RT RIC API. | | -| Step 1 (M) | xApp sends an API Registration update request to the Near-RT RIC platform. It includes the xApp identity and updated information on supported API. | | -| Step 2 (M) | Near-RT RIC platform verifies the identity of the xApp. | | -| Step 3 (M) | Near-RT RIC platform searches the stored Near-RT RIC API(s) information. | | -| Step 4 (M) | Near-RT RIC platform updates stored API information | | - -| | | | -|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 5 (M) | The Near-RT RIC platform sends an API Registration Update response to the xApp. This response indicates the success or failure of the API Registration Update operation. | | -| Ends with | Near-RT RIC platform may initiate API Event notification procedure towards one or more other xApps that had previously established a corresponding API Event Subscription. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" -Collections xApp as "xApp" -Participant PxApp as "Service Producer xApp" -Participant plt as "Near-RT RIC platform" -End box - -plt -> plt: Near-RT RIC platform service available -PxApp <-> plt: API Registration procedure - - -PxApp -> plt: 1. API Registration Update request -plt -> plt: 2. Near-RT RIC platform verifies \nthe identity of the xApp -plt -> plt: 3. Search stored API information -plt -> plt: 4. Store updated API information -plt -> PxApp: 5. API Registration Update response \n(Success or Failure) - - -plt -> xApp: API Event Notification - -@enduml - -``` - -![Sequence diagram for API Registration Update procedure. Lifelines: xApp, Service Producer xApp, and Near-RT RIC platform. The diagram shows the interaction between these entities to update API registration information.](cf03eff1218a8cc1be6b05de892162de_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant SP as Service Producer xApp - participant NRP as Near-RT RIC platform - - Note right of NRP: Near-RT RIC platform service available - SP->>NRP: API Registration procedure - Note right of NRP: 1. API Registration Update request - Note right of NRP: 2. Near-RT RIC platform verifies the identity of the xApp - Note right of NRP: 3. Search stored API information - Note right of NRP: 4. Store updated API information - NRP-->>SP: 5. API Registration Update response (Success or Failure) - NRP-->>xApp: API Event Notification - -``` - -Sequence diagram for API Registration Update procedure. Lifelines: xApp, Service Producer xApp, and Near-RT RIC platform. The diagram shows the interaction between these entities to update API registration information. - -Figure 9.6.3.2-1: API Registration Update procedure - -#### 9.6.3.3 API Deregistration procedure - -This procedure enables a previously registered xApp service producer to deregister as a service producer. - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To allow the xApp to deregister as a Near-RT RIC API service producer. | | -| Actors and Roles |
  • Service Producer xApp: Producer of a Near-RT RIC API.
  • xApp: Receiving event notifications based on subscription
  • Near-RT RIC platform, with the following functionalities:
    • API Enablement;
    • Database
| | -| Assumptions | For initiating the API Registration Update procedure, the xApp has registered to Near-RT RIC platform and is aware of the API information of the Enablement APIs. | | -| Pre conditions |
  • The xApp is deployed to Near-RT RIC platform.
  • The API information of Enablement APIs has been provided to the xApp (as pre-configuration by SMO or by other means).
  • The xApp has previously completed API Registration procedure
| | -| Begins when | xApps wants to deregister as a service producer of a Near-RT RIC API. | | -| Step 1 (M) | xApp sends an API Deregistration request to the Near-RT RIC platform. It includes the xApp identity and supported API information. | | -| Step 2 (M) | Near-RT RIC platform verifies the identity of the xApp. | | -| Step 3 (M) | Near-RT RIC platform searches the stored Near-RT RIC API(s) information. | | -| Step 4 (M) | Near-RT RIC platform removes stored API information. | | -| Step 5 (M) | The Near-RT RIC platform sends an API Deregistration response to the xApp. This response indicates the success or failure of the API Deregistration operation. | | -| Ends with | Near-RT RIC platform may initiate API Event notification procedure towards one or more other xApps that had previously established a corresponding API Event Subscription. | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 50 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Collections xApp as "xApp" - Participant PxApp as "Service Producer xApp" - Participant plt as "Near-RT RIC platform" -End box - -plt -> plt: Near-RT RIC platform service available -PxApp <-> plt: API Registration procedure -... - -PxApp -> plt: 1. API Deregistration request -plt -> plt: 2. Near-RT RIC platform verifies \nthe identity of the xApp -plt -> plt: 3. Search stored API information -plt -> plt: 4. Remove API information -plt -> PxApp: 5. API Deregistration response \n(Success or Failure) -... -plt -> xApp: API Event Notification - -@enduml - -``` - -![Sequence diagram for API Deregistration procedure. Lifelines: xApp, Service Producer xApp, and Near-RT RIC platform. The process involves a deregistration request from the Service Producer xApp to the platform, followed by internal platform steps (identity verification, API search, information removal), a response back to the Service Producer xApp, and finally an API event notification sent to the xApp.](3c0be9369e1f99f7f820fda3f9d676e6_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant SP as Service Producer xApp - participant Platform as Near-RT RIC platform - - Note right of Platform: Near-RT RIC platform service available - SP->>Platform: 1. API Deregistration request - Platform->>Platform: 2. Near-RT RIC platform verifies the identity of the xApp - Platform->>Platform: 3. Search stored API information - Platform->>Platform: 4. Remove API information - Platform->>SP: 5. API Deregistration response (Success or Failure) - Platform->>xApp: API Event Notification - -``` - -Sequence diagram for API Deregistration procedure. Lifelines: xApp, Service Producer xApp, and Near-RT RIC platform. The process involves a deregistration request from the Service Producer xApp to the platform, followed by internal platform steps (identity verification, API search, information removal), a response back to the Service Producer xApp, and finally an API event notification sent to the xApp. - -Figure 9.6.3.3-1: API Deregistration procedure - -## 9.7 AI/ML API Procedures - -### 9.7.1 Data Pipelining service procedures - -#### 9.7.1.1 Data Pipelining Job Setup procedure - -The Data Pipelining Job Setup procedure enables an xApp to setup a new data pipelining job in the Near-RT RIC platform. - -| Use Case Stage | Evolution / Specification | -|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp requests to setup a data pipelining job in the Near-RT RIC platform. | -| Actors and Roles |
  • xApp: Originator of data pipelining job setup request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • AI/ML workflow services have been registered by Near-RT RIC platform.
| -| Begins when | xApp determines to setup a Data Pipelining Job in the Near-RT RIC platform. | -| Step 1 (M) | xApp sends a request to Near-RT RIC platform to setup a data pipelining job. | -| Step 2 (M) | Near-RT RIC platform checks whether the originating xApp is allowed to setup the data pipelining job. | -| | [ALT] Step 3 is executed if the originating xApp is not allowed to setup the data pipelining job. | -| Step 3 (M) | A failure is responded to the originating xApp, possibly including appropriate reason. | -| | [ELSE] Steps 4-5 are executed if the originating xApp is allowed to setup the data pipelining job. | -| Step 4 (M) | Near-RT RIC platform create corresponding data pipelining job. | -| Step 5 (M) | Near-RT RIC platform responds success to the originating xApp. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" -Collections "xApp" as xApp -Participant plt as "Near-RT RIC platform" -End box - -autonumber -xApp -> plt: 1. Data Pipelining Job Setup request\n [Data Pipelining Configuration(data processing instruction, etc.)] -plt <-> plt: Validate originating xApp's Data Pipelining Job -alt The originating xApp is NOT allowed to setup Data Pipelining Job -plt -> xApp: Data Pipelining Job Setup RESULT [Failure, Reason] -else The originating xApp is allowed to setup Data Pipelining Job -plt <-> plt: Create Data Pipelining Job -plt -> xApp: Data Pipelining Job Setup RESULT [Success, Data Pipelining Job ID] -end alt -@enduml - -``` - -![Sequence diagram showing the Data Pipelining Job Setup procedure between xApp and Near-RT RIC platform.](90321ffa3cade82e4a57d6250d046c88_img.jpg) - -``` - -sequenceDiagram - participant xApp - box Near-RT RIC - participant plt as Near-RT RIC platform - end - autonumber - xApp->>plt: Data Pipelining Job Setup request [Data Pipelining Configuration(data processing instruction, interface subscription ID, etc.)] - plt->>plt: Validate originating xApp's Data Pipelining Job - alt The originating xApp is NOT allowed to setup Data Pipelining Job - plt->>xApp: Data Pipelining Job Setup RESULT [Failure, Reason] - else The originating xApp is allowed to setup Data Pipelining Job - plt->>plt: Create Data Pipelining Job - plt->>xApp: Data Pipelining Job Setup RESULT [Success, Data Pipelining Job ID] - end - -``` - -Sequence diagram showing the Data Pipelining Job Setup procedure between xApp and Near-RT RIC platform. - -**Figure 9.7.1.1-1: Data Pipelining Job Setup procedure** - -#### 9.7.1.2 Data Pipelining Job Update procedure - -The Data Pipelining Job Update procedure enables an xApp to update a running data pipelining job in the Near-RT RIC platform. - -| Use Case Stage | Evolution / Specification | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp requests to update a data pipelining job in the Near-RT RIC platform. | -| Actors and Roles |
  • xApp: Originator of data pipelining job update request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • AI/ML workflow services have been registered by Near-RT RIC platform;
  • At least one Data Pipelining Job setup by xApp is running in the Near-RT RIC platform.
| -| Begins when | xApp determines to update a Data Pipelining Job in the Near-RT-RIC platform. | -| Step 1 (M) | xApp sends a request to Near-RT RIC platform to update a data pipelining job. | -| Step 2 (M) | Near-RT RIC platform checks whether the originating xApp is allowed to update the requested data pipelining job. | -| | [ALT] Step 3 is executed if the originating xApp is not allowed to update the requested data pipelining job. | -| Step 3 (M) | A failure is responded to the originating xApp, possibly including appropriate reason. | -| | [ELSE] Steps 4-5 are executed if the originating xApp is allowed to update the requested data pipelining job. | -| Step 4 (M) | Near-RT RIC platform updates corresponding data pipelining job. | -| Step 5 (M) | Near-RT RIC platform responds success to the originating xApp. | - -``` -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Collections "xApp" as xApp - Participant plt as "Near-RT RIC platform" -End box -autonumber -xApp -> plt: 1. Data Pipelining Job Update request\n [Data Pipelining Job ID, Data Pipelining Job Update Details] -plt <-> plt: Validate the originating xApp's\n Data Pipelining Job Update request -alt The originating xApp is NOT allowed to Update Data Pipelining Job - plt -> xApp: Data Pipelining Job Update RESULT [Failure, Reason] -else The originating xApp is allowed to update the requested Data Pipelining Job - plt <-> plt: Update Data Pipelining Job - plt -> xApp: Data Pipelining Job Update RESULT [Success] -end alt -@enduml -``` - -![Sequence diagram for Data Pipelining Job Update procedure. Lifelines: xApp and Near-RT RIC platform. The process involves a request, validation, an authorization check (alt), an update action, and a success result.](e2245b4865907ad1259fd155f4beb6cf_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - Note right of Near-RT RIC platform: Near-RT RIC - xApp->>Near-RT RIC platform: 1. Data Pipelining Job Update request [Data Pipelining Job ID, Data Pipelining Job Update Details] - Near-RT RIC platform->>Near-RT RIC platform: 2. Validate the originating xApp's Data Pipelining Job Update request - alt The originating xApp is NOT allowed to Update Data Pipelining Job - Near-RT RIC platform->>xApp: 3. Data Pipelining Job Update RESULT [Failure, Reason] - else The originating xApp is allowed to update the requested Data Pipelining Job - Near-RT RIC platform->>Near-RT RIC platform: 4. Update Data Pipelining Job - Near-RT RIC platform->>xApp: 5. Data Pipelining Job Update RESULT [Success] - end - -``` - -Sequence diagram for Data Pipelining Job Update procedure. Lifelines: xApp and Near-RT RIC platform. The process involves a request, validation, an authorization check (alt), an update action, and a success result. - -Figure 9.7.1.2-1: Data Pipelining Job Update procedure - -#### 9.7.1.3 Data Pipelining Job Delete procedure - -The Data Pipelining Job Delete procedure enables an xApp to delete a running data pipelining job in the Near-RT RIC Platform. - -| Use Case Stage | Evolution / Specification | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp requests to delete a data pipelining job in the Near-RT RIC platform. | -| Actors and Roles |
  • xApp: Originator of data pipelining job delete request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • AI/ML workflow services have been registered by Near-RT RIC platform;
  • At least one data pipelining job setup by xApp is running in the Near-RT RIC platform.
| -| Begins when | xApp determines to delete a data pipelining job in the Near-RT RIC platform. | -| Step 1 (M) | xApp sends a request to Near-RT RIC platform to delete a data pipelining job. | -| Step 2 (M) | Near-RT RIC platform checks whether the originating xApp is allowed to delete the requested data pipelining job | -| | [ALT] Step 3 is executed if the originating xApp is not allowed to delete the requested data pipelining job. | -| Step 3 (M) | A failure is responded to the originating xApp, possibly including appropriate reason. | -| | [ELSE] Steps 4-5 are executed if the originating xApp is allowed to delete the requested data pipelining job. | -| Step 4 (M) | Near-RT RIC platform deletes corresponding data pipelining job. | -| Step 5 (M) | Near-RT RIC platform responds success to the originating xApp. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" -Collections "xApp" as xApp -Participant plt as "Near-RT RIC platform" -End box - -``` - -``` - -autonumber -xApp -> plt: 1. Data Pipelining Job Delete request\n [Data Pipelining Job ID] -plt <-> plt: Check the originating xApp's\npermission to delete the requested Data Pipelining Job -alt The originating xApp is NOT allowed to delete the Data Pipelining Job -plt -> xApp: Data Pipelining Job Delete RESULT [Failure, Reason] -else The originating xApp is allowed to delete the requested Data Pipelining Job -plt <-> plt: Delete Data Pipelining Job -plt -> xApp: Data Pipelining Job Delete RESULT [Success] -end alt -@enduml - -``` - -![Sequence diagram for Data Pipelining Job Delete procedure. Lifelines: xApp and Near-RT RIC platform. The process involves a request from xApp, a permission check by the platform, an alt block for approval or denial, and a final result response.](d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - Note right of Near-RT RIC platform: Near-RT RIC - xApp->>Near-RT RIC platform: 1. Data Pipelining Job Delete request [Data Pipelining Job ID] - Near-RT RIC platform->>Near-RT RIC platform: 2. Check the originating xApp's permission to delete the requested Data Pipelining Job - alt The originating xApp is NOT allowed to delete the Data Pipelining Job - Near-RT RIC platform->>xApp: 3. Data Pipelining Job Delete RESULT [Failure, Reason] - else The originating xApp is allowed to delete the requested Data Pipelining Job - Near-RT RIC platform->>Near-RT RIC platform: 4. Delete Data Pipelining Job - Near-RT RIC platform->>xApp: 5. Data Pipelining Job Delete RESULT [Success] - end - Note left of xApp: Near-RT RIC - -``` - -Sequence diagram for Data Pipelining Job Delete procedure. Lifelines: xApp and Near-RT RIC platform. The process involves a request from xApp, a permission check by the platform, an alt block for approval or denial, and a final result response. - -Figure 9.7.1.3-1: Data Pipelining Job Delete procedure - -#### 9.7.1.4 Data Pipelining Job Query procedure - -The Data Pipelining Job Query procedure enables an xApp to query the status of a running data pipelining job in the Near-RT RIC platform. - -| Use Case Stage | Evolution / Specification | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp requests to query the status of a data pipelining job in the Near-RT RIC platform. | -| Actors and Roles |
  • xApp: Originator of data pipelining job query request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • AI/ML workflow services have been registered by Near-RT RIC platform;
  • At least one data pipelining job setup by xApp is running in the Near-RT RIC platform.
| -| Begins when | xApp determines to query the status of a data pipelining job in the Near-RT RIC platform. | -| Step 1 (M) | xApp sends a request to Near-RT RIC platform to query the status of a data pipelining job. | -| Step 2 (M) | Near-RT RIC platform checks whether the originating xApp is allowed to query the status of the requested data pipelining job. | -| | [ALT] Step 3 is executed if the originating xApp is not allowed to query the status of the requested data pipelining job. | -| Step 3 (M) | A failure is responded to the originating xApp, possibly including appropriate reason. | -| | [ELSE] Steps 4-5 are executed if the originating xApp is allowed to query the status of the requested data pipelining job. | -| Step 4 (M) | Near-RT RIC platform looks up the status of corresponding data pipelining job. | -| Step 5 (M) | Near-RT RIC platform responds success to the originating xApp, including the queried status. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Collections "xApp" as xApp - Participant plt as "Near-RT RIC platform" -End box -autonumber -xApp -> plt: Data Pipelining Job Query request\n[Data Pipelining Job ID] -plt <-> plt: Check the originating xApp's\npermission to query the status \nof the requested Data Pipelining Job -alt The originating xApp is NOT allowed to query the status of the Data Pipelining Job - plt -> xApp: Data Pipelining Job Query RESULT [Failure, Reason] -else The originating xApp is allowed to query the status of the requested Data Pipelining Job - plt <-> plt: Looks up the status of the Data Pipelining Job - plt -> xApp: Data Pipelining Job Query RESULT [Success, Status] -end alt -@enduml - -``` - -![Sequence diagram illustrating the Data Pipelining Job Query procedure. Lifelines: xApp and Near-RT RIC platform. The sequence starts with a request from xApp to platform. The platform then performs an internal check. An 'alt' block titled '[The originating xApp is NOT allowed to query the status of the Data Pipelining Job]' contains a failure response. The 'else' block, '[The originating xApp is allowed to query the status of the requested Data Pipelining Job]', contains an internal lookup followed by a success response.](f4e5a86da5c799372a7c1ea2397dedb7_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant plt as Near-RT RIC platform - Note over xApp, plt: Near-RT RIC - xApp->>plt: 1 Data Pipelining Job Query request [Data Pipelining Job ID] - plt->>plt: 2 Check the originating xApp's permission to query the status of the requested Data Pipelining Job - alt The originating xApp is NOT allowed to query the status of the Data Pipelining Job - plt->>xApp: 3 Data Pipelining Job Query RESULT [Failure, Reason] - else The originating xApp is allowed to query the status of the requested Data Pipelining Job - plt->>plt: 4 Looks up the status of the Data Pipelining Job - plt->>xApp: 5 Data Pipelining Job Query RESULT [Success, Status] - end - -``` - -Sequence diagram illustrating the Data Pipelining Job Query procedure. Lifelines: xApp and Near-RT RIC platform. The sequence starts with a request from xApp to platform. The platform then performs an internal check. An 'alt' block titled '[The originating xApp is NOT allowed to query the status of the Data Pipelining Job]' contains a failure response. The 'else' block, '[The originating xApp is allowed to query the status of the requested Data Pipelining Job]', contains an internal lookup followed by a success response. - -Figure 9.7.1.4-1: Data Pipelining Job Query procedure - -#### 9.7.1.5 Data Pipelining Request and Result Delivery procedure - -The Data Pipelining Request and Result Delivery procedure allows an xApp to request a data pipelining result from Near-RT RIC platform through providing data pipelining input data. - -| Use Case Stage | Evolution / Specification | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp requests to get a data pipelining result from the Near-RT RIC platform. | -| Actors and Roles |
  • xApp: Originator of data pipelining request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • AI/ML workflow services have been registered by Near-RT RIC platform;
  • At least one data pipelining job setup by xApp is running in the Near-RT RIC platform.
| -| Begins when | xApp has new data pipelining input data or address to the new data pipelining input data and determine to use running data pipelining job to generates data pipelining results for xApp. | -| Step 1 (M) | xApp sends Near-RT-RIC platform Data Pipelining request. | -| | [ALT] Step 2-3 are executed if the data pipelining job is configured to provide output data or address of output data in the response. | -| Step 2 (M) | Near-RT-RIC platform generates data pipelining results. | -| Step 3 (M) | Near-RT-RIC platform responds to xApp, with data pipelining result. | -| | [ELSE] Steps 4-6 are executed if the data pipelining job is configured to provide output data or address of output data via the delivery procedure. | -| Step 4 (M) | xApp is responded by the Near-RT RIC platform. | -| Step 5 (M) | Near-RT-RIC platform generates data pipelining results. | -| Step 6 (M) | Near-RT-RIC platform delivers the data pipelining result to the xApp. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid -Autonumber - -Box "Near-RT RIC" -Collections "xApp" as xApp -Participant plt as "Near-RT RIC platform" -End box - -xApp -> plt: Data Pipelining Request [Data Pipelining Job ID, \nData Pipelining Input Data or Address of Data Pipelining Input Data] -Alt The Data Pipelining job is configured to provide Output data or address of Output data in the response - plt -> plt: Generate Data Pipelining Result - plt -> xApp: Data Pipelining Response [Data Pipelining Output Data, or Address of Output Data] -Else The Data Pipelining job is configured to provide Output data or address of Output data via the delivery procedure - plt -> xApp: Data Pipelining Response [Accepted] - plt -> plt: Generate Data Pipelining Result - plt -> xApp: Data Pipelining Result Delivery [Data Pipelining Output Data, or Address of Output Data] -end -@enduml - -``` - -![Sequence diagram for Data Pipelining Request and Result Delivery procedures. Lifelines: xApp and Near-RT RIC platform. The diagram shows two alternative paths for result delivery based on configuration.](ecae674475cecdd0962200a5d1e2591e_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - Note over xApp, Near-RT RIC platform: Near-RT RIC - xApp->>Near-RT RIC platform: 1 Data Pipelining Request [Data Pipelining Job ID, Data Pipelining Input Data or Address of Data Pipelining Input Data] - alt The Data Pipelining job is configured to provide Output data or address of Output data in the response - Near-RT RIC platform-->>Near-RT RIC platform: 2 Generate Data Pipelining Result - Near-RT RIC platform-->>xApp: 3 Data Pipelining Response [Data Pipelining Output Data, or Address of Output Data] - else The Data Pipelining job is configured to provide Output data or address of Output data via the delivery procedure - Near-RT RIC platform-->>xApp: 4 Data Pipelining Response [Accepted] - Near-RT RIC platform-->>Near-RT RIC platform: 5 Generate Data Pipelining Result - Near-RT RIC platform-->>xApp: 6 Data Pipelining Result Delivery [Data Pipelining Output Data, or Address of Output Data] - end - -``` - -Sequence diagram for Data Pipelining Request and Result Delivery procedures. Lifelines: xApp and Near-RT RIC platform. The diagram shows two alternative paths for result delivery based on configuration. - -Figure 9.7.1.5-1: Data Pipelining Request and Result Delivery procedures - -### 9.7.2 Training service procedures - -#### 9.7.2.1 Training Job Setup procedure - -The Training Job Setup procedure enables an xApp to setup a new training job in the Near-RT RIC platform. - -| Use Case Stage | Evolution / Specification | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp requests to setup a training job in the Near-RT RIC platform. | -| Actors and Roles |
  • xApp: Originator of training job setup request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • AI/ML workflow services have been registered by Near-RT RIC platform;
| -| Begins when | xApp determines to setup a training job in the Near-RT RIC platform. | -| Step 1 (M) | xApp sends a request to Near-RT RIC platform to setup a training job. | -| Step 2 (M) | Near-RT RIC platform checks whether the originating xApp is allowed to setup the training job. | -| | [ALT] Step 3 is executed if the originating xApp is not allowed to setup the training job. | -| Step 3 (M) | A failure is responded to the originating xApp, possibly including appropriate reason. | -| | [ELSE] Steps 4-5 are executed if the originating xApp is allowed to setup the training job. | -| Step 4 (M) | Near-RT RIC platform create corresponding training job. | -| Step 5 (M) | Near-RT RIC platform responds success to the originating xApp. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" -Collections "xApp" as xApp -Participant plt as "Near-RT RIC platform" -End box - -autonumber - -``` - -``` - -xApp -> plt: 1. Training Job Setup request\n [AI/ML Model Identifier or AI/ML Model File or -AI/ML Model Address, Training Configuration] -plt <-> plt: Validate originating xApp's training Job -alt The originating xApp is NOT allowed to setup training Job -plt -> xApp: Training Job Setup RESULT [Failure, Reason] -else The originating xApp is allowed to setup Training Job -plt <-> plt: Create Training Job -plt -> xApp: Training Job Setup RESULT [Success, Training Job ID] -end alt -@enduml - -``` - -![Sequence diagram showing the Training Job Setup procedure between an xApp and a Near-RT RIC platform. The process involves a request, validation, an alt block for approval or failure, job creation if approved, and a final success result.](b02ba0b73e95416eb547976f6145b169_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - Note over Near-RT RIC platform: Near-RT RIC - xApp->>Near-RT RIC platform: 1. Training Job Setup request [AI/ML Model Identifier or AI/ML Model File or AI/ML Model Address, Training Configuration] - Near-RT RIC platform->>Near-RT RIC platform: 2. Validate originating xApp's training Job - alt The originating xApp is NOT allowed to setup training Job - Near-RT RIC platform->>xApp: 3. Training Job Setup RESULT [Failure, Reason] - else The originating xApp is allowed to setup Training Job - Near-RT RIC platform->>Near-RT RIC platform: 4. Create Training Job - Near-RT RIC platform->>xApp: 5. Training Job Setup RESULT [Success, Training Job ID] - end - -``` - -Sequence diagram showing the Training Job Setup procedure between an xApp and a Near-RT RIC platform. The process involves a request, validation, an alt block for approval or failure, job creation if approved, and a final success result. - -Figure 9.7.2.1-1: Training Job Setup procedure - -#### 9.7.2.2 Training Job Delete procedure - -The Training Job Delete procedure enables an xApp to delete a running training job in the Near-RT RIC platform. - -| Use Case Stage | Evolution / Specification | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp requests to delete a training job in the Near-RT RIC platform. | -| Actors and Roles |
  • xApp: Originator of training job delete request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • AI/ML workflow services have been registered by Near-RT RIC platform;
  • At least one training job setup by xApp is running in the Near-RT RIC platform.
| -| Begins when | xApp determines to delete a training job in the Near-RT RIC platform. | -| Step 1 (M) | xApp sends a request to Near-RT RIC platform to delete a training job. | -| Step 2 (M) | Near-RT RIC platform checks whether the originating xApp is allowed to delete the requested training job | -| | [ALT] Step 3 is executed if the originating xApp is not allowed to delete the requested training job. | -| Step 3 (M) | A failure is responded to the originating xApp, possibly including appropriate reason. | -| | [ELSE] Steps 4-5 are executed if the originating xApp is allowed to delete the requested training job. | -| Step 4 (M) | Near-RT RIC platform deletes corresponding training job. | -| Step 5 (M) | Near-RT RIC platform responds success to the originating xApp. | - -``` - -@startuml -skin rose - -``` - -``` - -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Collections "xApp" as xApp - Participant plt as "Near-RT RIC platform" -End box -autonumber -xApp -> plt: 1. Training Job Delete request\n [Training Job ID] -plt <-> plt: Check the originating xApp's\npermission to delete the requested Training Job -alt The originating xApp is NOT allowed to delete the Training Job - plt -> xApp: Training Job Delete RESULT [Failure, Reason] -else The originating xApp is allowed to delete the requested Training Job - plt <-> plt: Delete Training Job - plt -> xApp: Training Job Delete RESULT [Success] -end alt -@enduml - -``` - -![Sequence diagram for Training Job Delete procedure. Lifelines: xApp and Near-RT RIC platform. The process involves a request, a permission check, an alt block for approval or denial, and a final result.](710ff83dc4a77abbe489fbf1a462845a_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant plt as Near-RT RIC platform - Note right of plt: Near-RT RIC - xApp->>plt: 1. Training Job Delete request [Training Job ID] - plt->>plt: 2. Check the originating xApp's permission to delete the requested Training Job - alt The originating xApp is NOT allowed to delete the Training Job - plt->>xApp: 3. Training Job Delete RESULT [Failure, Reason] - else The originating xApp is allowed to delete the requested Training Job - plt->>plt: 4. Delete Training Job - plt->>xApp: 5. Training Job Delete RESULT [Success] - end - -``` - -Sequence diagram for Training Job Delete procedure. Lifelines: xApp and Near-RT RIC platform. The process involves a request, a permission check, an alt block for approval or denial, and a final result. - -Figure 9.7.2.2-1: Training Job Delete procedure - -#### 9.7.2.3 Training Job Query procedure - -The Training Job Query procedure enables an xApp to query the status of a running training job in the Near-RT RIC platform. - -| Use Case Stage | Evolution / Specification | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp requests to query the status of a training job in the Near-RT RIC platform. | -| Actors and Roles |
  • xApp: Originator of training job query request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • AI/ML workflow services have been registered by Near-RT RIC platform;
  • At least one training job setup by xApp is running in the Near-RT RIC platform.
| -| Begins when | xApp determines to query the status of a training job in the Near-RT RIC platform. | -| Step 1 (M) | xApp sends a request to Near-RT RIC platform to query the status of a training job. | -| Step 2 (M) | Near-RT RIC platform checks whether the originating xApp is allowed to query the status of the requested training job. | -| | [ALT] Step 3 is executed if the originating xApp is not allowed to query the status of the requested training job. | -| Step 3 (M) | A failure is responded to the originating xApp, possibly including appropriate reason. | -| | [ELSE] Steps 4-5 are executed if the originating xApp is allowed to query the status of the requested training job. | -| Step 4 (M) | Near-RT RIC platform looks up the status of corresponding training job. | -| Step 5 (M) | Near-RT RIC platform responds success to the originating xApp, including the queried status. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" -Collections "xApp" as xApp -Participant plt as "Near-RT RIC platform" -End box -autonumber -xApp -> plt: Training Job Query request\n[Training Job ID] -plt <-> plt: Check the originating xApp's\npermission to query the status \nof the requested Training Job -alt The originating xApp is NOT allowed to query the status of the Training Job -plt -> xApp: Training Job Query RESULT [Failure, Reason] -else The originating xApp is allowed to query the status of the requested Training Job -plt <-> plt: Looks up the status of the Training Job -plt -> xApp: Training Job Query RESULT [Success, Status] -end alt -@enduml - -``` - -![Sequence diagram for Training Job Query procedure. Lifelines: xApp and Near-RT RIC platform. The process involves a query request, permission check, an alt block for 'NOT allowed' (failure) or 'allowed' (success), and a final result response.](e5eedb1e90a22814f090917b3411be8f_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - Note right of Near-RT RIC platform: Near-RT RIC - xApp->>Near-RT RIC platform: 1 Training Job Query request [Training Job ID] - Note right of Near-RT RIC platform: 2 Check the originating xApp's permission to query the status of the requested Training Job - alt The originating xApp is NOT allowed to query the status of the Training Job - Near-RT RIC platform-->>xApp: 3 Training Job Query RESULT [Failure, Reason] - else The originating xApp is allowed to query the status of the requested Training Job - Note right of Near-RT RIC platform: 4 Looks up the status of the Training Job - Near-RT RIC platform-->>xApp: 5 Training Job Query RESULT [Success, Status] - end - Note left of xApp: Near-RT RIC - -``` - -Sequence diagram for Training Job Query procedure. Lifelines: xApp and Near-RT RIC platform. The process involves a query request, permission check, an alt block for 'NOT allowed' (failure) or 'allowed' (success), and a final result response. - -Figure 9.7.2.3-1: Training Job Query procedure - -#### 9.7.2.4 Training Request and Result Delivery procedure - -The Training Request and Result Delivery procedure allows an xApp to request training result of an AI/ML model from Near-RT RIC platform through providing AI/ML model training data. - -| Use Case Stage | Evolution / Specification | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp requests to get a training result from the Near-RT RIC platform. | -| Actors and Roles |
  • xApp: Originator of AI/ML model training request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • AI/ML workflow services have been registered by Near-RT RIC platform;
  • At least one training job setup by xApp is running in the Near-RT RIC platform.
| -| Begins when | Near-RT-RIC platform or xApp has new AI/ML model training data or Address of new AI/ML model training data and determine to use running training job to train AI/ML model for xApp. | -| Step 1 (M) | xApp sends Near-RT-RIC platform training request. | -| | [ALT] Step 2-3 are executed if the training job is configured to provide training result in the response. | -| Step 2 (M) | Near-RT-RIC platform generates training results. | -| Step 3 (M) | Near-RT-RIC platform responds to xApp, with training result. | -| | [ELSE] Steps 4-6 are executed if the training job is configured to provide training result via the delivery procedure. | -| Step 4 (M) | xApp is responded by the Near-RT RIC platform. | -| Step 5 (M) | Near-RT-RIC platform generates training results. | -| Step 6 (M) | Near-RT-RIC platform delivers the training result to xApp. | - -``` -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -``` - -``` - -skinparam lifelineStrategy solid -Autonumber - -Box "Near-RT RIC" - Collections "xApp" as xApp - Participant plt as "Near-RT RIC platform" -End box - -xApp -> plt: Training Request [Training Job ID, AI/ML Model Training Data or Address of AI/ML Model Training Data] -Alt The Training Job is configured to provide Training Result in the response - plt -> plt: Generate Training Result - plt -> xApp: Training Response [Trained AI/ML Model or Trained AI/ML Model Address] -Else The Training Job is configured to provide Training Result via the delivery procedure - plt -> xApp: Training Response [Accepted] - plt -> plt: Generate Training Result - plt -> xApp: Training Result Delivery [Trained AI/ML Model or Trained AI/ML Model Address] -end -@enduml - -``` - -![Sequence diagram showing Training Request and Result Delivery procedures between xApp and Near-RT RIC platform. The diagram includes a 'Near-RT RIC' box containing lifelines for 'xApp' and 'Near-RT RIC platform'. The sequence starts with a 'Training Request' from xApp to the platform. An 'alt' block titled '[The Training Job is configured to provide Training Result in the response]' contains two paths: one where the platform generates the result and returns it, and another where it responds with 'Accepted' and later delivers the result. The second path is under an 'alt' block titled '[The Training Job is configured to provide Training Result via the delivery procedure]'.](b0384c8e0ff826a8116ab2ff67dadc43_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant plt as Near-RT RIC platform - Note over xApp, plt: Near-RT RIC - xApp->>plt: 1 Training Request [Training Job ID, AI/ML Model Training Data or Address of AI/ML Model Training Data] - alt The Training Job is configured to provide Training Result in the response - plt->>plt: 2 Generate Training Result - plt->>xApp: 3 Training Response [Trained AI/ML Model or Trained AI/ML Model Address] - else The Training Job is configured to provide Training Result via the delivery procedure - plt->>xApp: 4 Training Response [Accepted] - plt->>plt: 5 Generate Training Result - plt->>xApp: 6 Training Result Delivery [Trained AI/ML Model or Trained AI/ML Model Address] - end - -``` - -Sequence diagram showing Training Request and Result Delivery procedures between xApp and Near-RT RIC platform. The diagram includes a 'Near-RT RIC' box containing lifelines for 'xApp' and 'Near-RT RIC platform'. The sequence starts with a 'Training Request' from xApp to the platform. An 'alt' block titled '[The Training Job is configured to provide Training Result in the response]' contains two paths: one where the platform generates the result and returns it, and another where it responds with 'Accepted' and later delivers the result. The second path is under an 'alt' block titled '[The Training Job is configured to provide Training Result via the delivery procedure]'. - -Figure 9.7.2.4-1: Training Request and Result Delivery procedures - -### 9.7.3 Inference service procedures - -#### 9.7.3.1 Inference Job Setup procedure - -The Inference Job Setup procedure enables an xApp to setup a new inference job in the Near-RT RIC platform. - -| Use Case Stage | Evolution / Specification | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp requests to setup an inference job in the Near-RT RIC platform. | -| Actors and Roles |
  • xApp: Originator of inference job setup request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • AI/ML workflow services have been registered by Near-RT RIC platform;
| -| Begins when | xApp determines to setup an inference job in the Near-RT-RIC platform. | -| Step 1 (M) | xApp sends a request to Near-RT RIC platform to setup an inference job. | -| Step 2 (M) | Near-RT RIC platform checks whether the originating xApp is allowed to setup inference job. | -| | [ALT] Step 3 is executed if the originating xApp is not allowed to setup inference job. | -| Step 3 (M) | A failure is responded to the originating xApp, possibly including appropriate reason. | -| | [ELSE] Steps 4-5 are executed if the originating xApp is allowed to setup inference job. | -| Step 4 (M) | Near-RT RIC platform create corresponding inference job. | -| Step 5 (M) | Near-RT RIC platform responds success to the originating xApp. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Collections "xApp" as xApp - Participant plt as "Near-RT RIC platform" -End box - -autonumber -xApp -> plt: 1. Inference Job Setup request\n [AI/ML Model Identifier or AI/ML Model File or -AI/ML Model Address, Inference Configuration] -plt <-> plt: Validate originating xApp's Inference Job -alt The originating xApp is NOT allowed to setup Inference Job - plt -> xApp: Inference Job Setup RESULT [Failure, Reason] -else The originating xApp is allowed to setup Inference Job - plt <-> plt: Create Inference Job - plt -> xApp: Inference Job Setup RESULT [Success, Inference Job ID] -end alt -@enduml - -``` - -![Sequence diagram showing the Inference Job Setup procedure between xApp and Near-RT RIC platform. The diagram includes lifelines for xApp and Near-RT RIC platform. The sequence starts with xApp sending a request to the platform. The platform validates the job. An 'alt' block titled '[The originating xApp is NOT allowed to setup Inference Job]' contains a failure response. The 'else' block contains the success path where the platform creates the job and returns a success result.](3d590ad29ecfe728f07432e6fcb59064_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - Note right of Near-RT RIC platform: Near-RT RIC - xApp->>Near-RT RIC platform: 1. Inference Job Setup request [AI/ML Model Identifier or AI/ML Model File or AI/ML Model Address, Inference Configuration] - Near-RT RIC platform->>Near-RT RIC platform: 2 Validate originating xApp's Inference Job - alt The originating xApp is NOT allowed to setup Inference Job - Near-RT RIC platform-->>xApp: 3 Inference Job Setup RESULT [Failure, Reason] - else The originating xApp is allowed to setup Inference Job - Near-RT RIC platform->>Near-RT RIC platform: 4 Create Inference Job - Near-RT RIC platform-->>xApp: 5 Inference Job Setup RESULT [Success, Inference Job ID] - end - -``` - -Sequence diagram showing the Inference Job Setup procedure between xApp and Near-RT RIC platform. The diagram includes lifelines for xApp and Near-RT RIC platform. The sequence starts with xApp sending a request to the platform. The platform validates the job. An 'alt' block titled '[The originating xApp is NOT allowed to setup Inference Job]' contains a failure response. The 'else' block contains the success path where the platform creates the job and returns a success result. - -Figure 9.7.3.1-1: Inference Job Setup procedure - -#### 9.7.3.2 Inference Job Update procedure - -The Inference Job Update procedure enables an xApp to update a running inference job in the Near-RT RIC platform. - -| Use Case Stage | Evolution / Specification | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp requests to update an inference job in the Near-RT RIC platform. | -| Actors and Roles |
  • xApp: Originator of inference job update request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • AI/ML workflow services have been registered by Near-RT RIC platform;
  • At least one inference job setup by xApp is running in the Near-RT RIC platform.
| -| Begins when | xApp determines to update an Inference Job in the Near-RT RIC platform. | -| Step 1 (M) | xApp sends a request to Near-RT RIC platform to update an inference job. | -| Step 2 (M) | Near-RT RIC platform checks whether the originating xApp is allowed to update the requested inference job. | -| | [ALT] Step 3 is executed if the originating xApp is not allowed to update the requested inference job. | -| Step 3 (M) | A failure is responded to the originating xApp, possibly including appropriate reason. | -| | [ELSE] Steps 4-5 are executed if the originating xApp is allowed to update the requested inference job. | -| Step 4 (M) | Near-RT RIC platform updates corresponding inference job. | -| Step 5 (M) | Near-RT RIC platform responds success to the originating xApp. | - -``` -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Collections "xApp" as xApp - Participant plt as "Near-RT RIC platform" -End box -autonumber -xApp -> plt: 1. Inference Job Update request\n [Inference Job ID, Inference Job Update Details] -plt <-> plt: Validate the originating xApp's\n Inference Job Update request -alt The originating xApp is NOT allowed to Update Inference Job - plt -> xApp: Inference Job Update RESULT [Failure, Reason] -else The originating xApp is allowed to update the requested Inference Job - plt <-> plt: Update Inference Job - plt -> xApp: Inference Job Update RESULT [Success] -end alt -@enduml -``` - -![Sequence diagram for Inference Job Update procedure. Lifelines: xApp and Near-RT RIC platform. The process involves sending an update request, validating it, checking permissions via an alt block, and then either failing or updating the job.](d7896dd2d38adf224c3b76cd22d29c10_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - Note right of Near-RT RIC platform: Near-RT RIC - xApp->>Near-RT RIC platform: 1. Inference Job Update request [Inference Job ID, Inference Job Update Details] - Near-RT RIC platform->>Near-RT RIC platform: 2. Validate the originating xApp's Inference Job Update request - alt The originating xApp is NOT allowed to Update Inference Job - Near-RT RIC platform-->>xApp: 3 Inference Job Update RESULT [Failure, Reason] - else The originating xApp is allowed to update the requested Inference Job - Near-RT RIC platform->>Near-RT RIC platform: 4 Update Inference Job - Near-RT RIC platform-->>xApp: 5 Inference Job Update RESULT [Success] - end - Note left of xApp: Near-RT RIC - -``` - -Sequence diagram for Inference Job Update procedure. Lifelines: xApp and Near-RT RIC platform. The process involves sending an update request, validating it, checking permissions via an alt block, and then either failing or updating the job. - -Figure 9.7.3.2-1: Inference Job Update procedure - -#### 9.7.3.3 Inference Job Delete procedure - -The Inference Job Delete procedure enables an xApp to delete a running inference job in the Near-RT RIC platform. - -| Use Case Stage | Evolution / Specification | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp requests to delete an inference job in the Near-RT RIC platform. | -| Actors and Roles |
  • xApp: Originator of inference job delete request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • AI/ML workflow services have been registered by Near-RT RIC platform;
  • At least one inference job setup by xApp is running in the Near-RT RIC platform.
| -| Begins when | xApp determines to delete an inference job in the Near-RT RIC platform. | -| Step 1 (M) | xApp sends a request to Near-RT RIC platform to delete an inference job. | -| Step 2 (M) | Near-RT RIC platform checks whether the originating xApp is allowed to delete the requested inference job. | -| | [ALT] Step 3 is executed if the originating xApp is not allowed to delete the requested inference job. | -| Step 3 (M) | A failure is responded to the originating xApp, possibly including appropriate reason. | -| | [ELSE] Steps 4-5 are executed if the originating xApp is allowed to delete the requested inference job. | -| Step 4 (M) | Near-RT RIC platform deletes corresponding inference job. | -| Step 5 (M) | Near-RT RIC platform responds success to the originating xApp. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid -Box "Near-RT RIC" - -``` - -``` - -Collections “xApp” as xApp -Participant plt as “Near-RT RIC platform” -End box -autonumber -xApp -> plt: 1. Inference Job Delete request\n [Inference Job ID] -plt <-> plt: Check the originating xApp's\npermission to delete the requested Inference Job -alt The originating xApp is NOT allowed to delete the Inference Job -plt -> xApp: Inference Job Delete RESULT [Failure, Reason] -else The originating xApp is allowed to delete the requested Inference Job -plt <-> plt: Delete Inference Job -plt -> xApp: Inference Job Delete RESULT [Success}] -end alt -@enduml - -``` - -![Sequence diagram illustrating the Inference Job Delete procedure. The diagram shows interactions between an xApp and the Near-RT RIC platform. The process involves sending a delete request, checking permissions, and then either returning a failure result or deleting the job and returning a success result based on an alt condition.](6059b0a3a051cc20b414d51a4e412f3e_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant plt as Near-RT RIC platform - Note right of plt: Near-RT RIC - xApp->>plt: 1. Inference Job Delete request [Inference Job ID] - plt->>plt: 2. Check the originating xApp's permission to delete the requested Inference Job - alt The originating xApp is NOT allowed to delete the Inference Job - plt->>xApp: 3. Inference Job Delete RESULT [Failure, Reason] - else The originating xApp is allowed to delete the requested Inference Job - plt->>plt: 4. Delete Inference Job - plt->>xApp: 5. Inference Job Delete RESULT [Success] - end - -``` - -Sequence diagram illustrating the Inference Job Delete procedure. The diagram shows interactions between an xApp and the Near-RT RIC platform. The process involves sending a delete request, checking permissions, and then either returning a failure result or deleting the job and returning a success result based on an alt condition. - -Figure 9.7.3.3-1: Inference Job Delete procedure - -#### 9.7.3.4 Inference Job Query procedure - -The Inference Job Query procedure enables an xApp to query the status of a running inference job in the Near-RT RIC platform. - -| Use Case Stage | Evolution / Specification | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp requests to query the status of an inference job in the Near-RT RIC platform. | -| Actors and Roles |
  • xApp: Originator of inference job query request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • AI/ML workflow services have been registered by Near-RT RIC platform;
  • At least one inference job setup by xApp is running in the Near-RT RIC platform.
| -| Begins when | xApp determines to query the status of an Inference Job in the Near-RT-RIC platform. | -| Step 1 (M) | xApp sends a request to Near-RT RIC platform to query the status of an inference job. | -| Step 2 (M) | Near-RT RIC platform checks whether the originating xApp is allowed to query the status of the requested inference job. | -| | [ALT] Step 3 is executed if the originating xApp is not allowed to query the status of the requested inference job. | -| Step 3 (M) | A failure is responded to the originating xApp, possibly including appropriate reason. | -| | [ELSE] Steps 4-5 are executed if the originating xApp is allowed to query the status of the requested inference job. | -| Step 4 (M) | Near-RT RIC platform looks up the status of corresponding inference job. | -| Step 5 (M) | Near-RT RIC platform responds success to the originating xApp, including the queried status. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Collections "xApp" as xApp - Participant plt as "Near-RT RIC platform" -End box -autonumber -xApp -> plt: Inference Job Query request\n[Inference Job ID] -plt <-> plt: Check the originating xApp's\npermission to query the status of the requested -Inference Job -alt The originating xApp is NOT allowed to query the status of the Inference Job -plt -> xApp: Inference Job Query RESULT [Failure, Reason] -else The originating xApp is allowed to query the status of the requested Inference Job -plt <-> plt: Look up the status of the Inference Job -plt -> xApp: Inference Job Query RESULT [Success, Status] -end alt -@enduml - -``` - -![Sequence diagram for Inference Job Query procedure. Lifelines: xApp and Near-RT RIC platform. The process involves a query request, permission check, an alt block for allowed/not allowed status, and a final result response.](60f844d947ea0bccdd9f64d81d5f8d26_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - Note right of Near-RT RIC platform: Near-RT RIC - xApp->>Near-RT RIC platform: 1 Inference Job Query request [Inference Job ID] - Near-RT RIC platform->>xApp: 2 Check the originating xApp's permission to query the status of the requested Inference Job - alt The originating xApp is NOT allowed to query the status of the Inference Job - Near-RT RIC platform->>xApp: 3 Inference Job Query RESULT [Failure, Reason] - else The originating xApp is allowed to query the status of the requested Inference Job - Near-RT RIC platform->>xApp: 4 Look up the status of the Inference Job - Near-RT RIC platform->>xApp: 5 Inference Job Query RESULT [Success, Status] - end - -``` - -Sequence diagram for Inference Job Query procedure. Lifelines: xApp and Near-RT RIC platform. The process involves a query request, permission check, an alt block for allowed/not allowed status, and a final result response. - -Figure 9.7.3.4-1: Inference Job Query procedure - -#### 9.7.3.5 Inference Request and Result Delivery procedures - -The Inference Request and Result Delivery procedure allows an xApp to request an AI/ML model inference result from Near-RT RIC platform through providing model input data. - -| Use Case Stage | Evolution / Specification | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp requests to get an inference result from the Near-RT RIC platform. | -| Actors and Roles |
  • xApp: Originator of AI/ML model inference request;
  • Near-RT RIC platform: Response to the request of xApp.
| -| Pre-conditions |
  • AI/ML workflow services have been registered by Near-RT RIC platform;
  • At least one inference job setup by xApp is running in the Near-RT RIC platform.
| -| Begins when | Near-RT-RIC platform has new model input data and determine to use running inference job to generates inference results for xApp. | -| Step 1 (M) | xApp sends Near-RT-RIC platform inference request. | -| | [ALT] Step 2-3 are executed if the Inference Job is configured to provide output data in the response. | -| Step 2 (M) | Near-RT-RIC platform generates inference results. | -| Step 3 (M) | Near-RT-RIC platform responds to xApp, with inference result. | -| | [ELSE] Steps 4-6 are executed if the inference job is configured to provide output data via the delivery procedure. | -| Step 4 (M) | xApp is responded by the Near-RT RIC platform. | -| Step 5 (M) | Near-RT-RIC platform generates inference results. | -| Step 6 (M) | Near-RT-RIC platform delivers the inference result to xApp. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid -Autonumber - -Box "Near-RT RIC" -Collections "xApp" as xApp -Participant plt as "Near-RT RIC platform" - -``` - -``` - -End box - -xApp -> plt: Inference Request [Inference Job ID, AI/ML Model Input Data or Address of AI/ML Model Input Data] -Alt The inference job is configured to provide Output Data or Address of Output Data in the response - plt -> plt: Generate Inference Result - plt -> xApp: Inference Response [AI/ML Model Output Data or Address of AI/ML Model Output Data] -Else The inference job is configured to provide Output Data or Address of Output Data via the delivery procedure - plt -> xApp: Inference Response [Accepted] - plt -> plt: Generate Inference Result - plt -> xApp: Inference Result Delivery [AI/ML Model Output Data or Address of AI/ML Model Output Data] -end -@enduml - -``` - -![Sequence diagram titled 'Near-RT RIC' showing the interaction between an xApp and the Near-RT RIC platform. The diagram illustrates two alternative procedures for inference result delivery. In the first alt block, '[The inference job is configured to provide Output Data or Address of Output Data in the response]', the platform generates the result and sends an 'Inference Response' back to the xApp. In the second alt block, '[The inference job is configured to provide Output Data or Address of Output Data via the delivery procedure]', the platform first sends an 'Inference Response [Accepted]' and then later sends the 'Inference Result Delivery'.](137bcfed81ada68ca5162ca5afed35c7_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - Note over Near-RT RIC platform: Near-RT RIC - xApp->>Near-RT RIC platform: 1 Inference Request [Inference Job ID, AI/ML Model Input Data or Address of AI/ML Model Input Data] - alt The inference job is configured to provide Output Data or Address of Output Data in the response - Near-RT RIC platform->>Near-RT RIC platform: 2 Generate Inference Result - Near-RT RIC platform->>xApp: 3 Inference Response [AI/ML Model Output Data or Address of AI/ML Model Output Data] - else The inference job is configured to provide Output Data or Address of Output Data via the delivery procedure - Near-RT RIC platform->>xApp: 4 Inference Response [Accepted] - Near-RT RIC platform->>Near-RT RIC platform: 5 Generate Inference Result - Near-RT RIC platform->>xApp: 6 Inference Result Delivery [AI/ML Model Output Data or Address of AI/ML Model Output Data] - end - -``` - -Sequence diagram titled 'Near-RT RIC' showing the interaction between an xApp and the Near-RT RIC platform. The diagram illustrates two alternative procedures for inference result delivery. In the first alt block, '[The inference job is configured to provide Output Data or Address of Output Data in the response]', the platform generates the result and sends an 'Inference Response' back to the xApp. In the second alt block, '[The inference job is configured to provide Output Data or Address of Output Data via the delivery procedure]', the platform first sends an 'Inference Response [Accepted]' and then later sends the 'Inference Result Delivery'. - -Figure 9.7.3.5-1: Inference Request and Result Delivery procedures - -### 9.7.4 Model Management and Exposure Service procedures - -#### 9.7.4.1 Model Store procedure - -The Model Store procedure in the Near-RT RIC allows an xApp to request to store an AI/ML model in the Near-RT RIC platform. An AI/ML Model is identified by a model identifier. - -| Use Case Stage | Evolution / Specification | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp requests to store an AI/ML model in the Near-RT RIC platform. | -| Actors and Roles |
  • xApp: Originator of Model Store request;
  • Near-RT RIC platform, with the following functionalities:
    • AI/ML support.
| -| Pre-conditions |
  • AI/ML workflow services have been registered by Near-RT RIC platform;
| -| Begins when | xApp determines to store an AI/ML model in the Near-RT RIC platform. | -| Step 1 (M) | xApp sends a request to Near-RT RIC platform to store an AI/ML model. | -| Step 2 (M) | Near-RT RIC platform stores the AI/ML model in an xApp specific space. | -| | [ALT] Step 3 is executed if the platform failed to store the AI/ML model. | -| Step 3 (M) | A failure is responded to the originating xApp, possibly including appropriate reason. | -| | [ELSE] Step 4 is executed if the platform successfully stored the AI/ML model. | -| Step 4 (M) | Near-RT RIC platform responds success to the originating xApp. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Collections "xApp" as xApp - Participant plt as "Near-RT RIC platform" -End box - -xApp -> plt: 1. Model Store request [AI/ML Model Identifier, AI/ML Model File] -plt -> plt: 2. Store requested AI/ML model -alt platform failed to store the AI/ML model - plt -> xApp: 3. Model Store response [Failure, Reason] -else platform successfully stored the AI/ML model - plt -> xApp: 4. Model Store response [Success] -end alt -@enduml - -``` - -![Sequence diagram titled 'Near-RT RIC' showing the Model Store procedure. Lifelines: xApp (top) and Near-RT RIC platform (top), xApp (bottom) and Near-RT RIC platform (bottom). The sequence starts with xApp (top) sending a '1. Model Store request [AI/ML Model Identifier, AI/ML Model File]' to Near-RT RIC platform (top). The platform performs a self-call '2. Store requested AI/ML model'. An 'alt' block titled '[platform failed to store the AI/ML model]' contains two branches: the first branch shows '3. Model Store response [Failure, Reason]' from platform (top) to xApp (bottom); the second branch, labeled '[platform successfully stored the AI/ML model]', shows '4. Model Store response [Success]' from platform (top) to xApp (bottom).](1ff58ab75ff926ead7067453006a75fe_img.jpg) - -Sequence diagram titled 'Near-RT RIC' showing the Model Store procedure. Lifelines: xApp (top) and Near-RT RIC platform (top), xApp (bottom) and Near-RT RIC platform (bottom). The sequence starts with xApp (top) sending a '1. Model Store request [AI/ML Model Identifier, AI/ML Model File]' to Near-RT RIC platform (top). The platform performs a self-call '2. Store requested AI/ML model'. An 'alt' block titled '[platform failed to store the AI/ML model]' contains two branches: the first branch shows '3. Model Store response [Failure, Reason]' from platform (top) to xApp (bottom); the second branch, labeled '[platform successfully stored the AI/ML model]', shows '4. Model Store response [Success]' from platform (top) to xApp (bottom). - -Figure 9.7.4.1-1: Model Store procedure - -#### 9.7.4.2 Stored Model Query procedure - -The Stored Model Query procedure in the Near-RT RIC enables an xApp to query the list of stored AI/ML models in the Near-RT RIC. - -| Use Case Stage | Evolution / Specification | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | An xApp queries the list of stored AI/ML models from the Near-RT RIC. | -| Actors and Roles |
  • • xApp: Originator of Stored Model Query request;
  • • Near-RT RIC platform, with the following functionalities:
    • – AI/ML support.
| -| Pre-conditions |
  • • AI/ML workflow services have been registered with Near-RT RIC platform;
  • • At least one AI/ML model has been stored by xApp in the Near-RT RIC Platform
| -| Begins when | xApp determines to query the list of stored AI/ML models that it has stored from the Near-RT RIC platform. | -| Step 1 (M) | xApp requests to Near-RT RIC platform to query stored AI/ML models that meets provided selection criteria. | -| Step 2 (M) | Near-RT RIC platform fetches xApp queried information. | -| | [ALT] Step 3 is executed if the platform failed to fetch the xApp queried information. | -| Step 3 (M) | A failure is responded to the originating xApp, possibly including appropriate reason. | -| | [ELSE] Step 4 is executed if the platform successfully fetched the xApp queried information. | -| Step 4 (M) | Near-RT RIC platform responds success to the originating xApp, with requested AI/ML model list. | - -``` -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Collections "xApp" as xApp - Participant plt as "Near-RT RIC platform" -End box - -xApp -> plt: 1. Stored Model Query request [Selection Criteria] -plt -> plt: 2. Look up required information -alt platform failed to fetch the xApp queried information - plt -> xApp: 3. Stored Model Query response [Failure, Reason] -else platform successfully fetched the xApp queried information - plt -> xApp: 4. Stored Model Query response [Success, AI/ML Model List] -end alt -@enduml -``` - -![Sequence diagram for Stored Model Query procedure. Lifelines: xApp and Near-RT RIC platform. The process involves a request from xApp to platform, a lookup by platform, and then an alt block for success or failure response.](cc91bf9aed46f8b219ebceaee276d195_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant platform as Near-RT RIC platform - Note over xApp, platform: Near-RT RIC - xApp->>platform: 1. Stored Model Query request [Selection Criteria] - platform-->>platform: 2. Look up required information - alt platform failed to fetch the xApp queried information - platform-->>xApp: 3. Stored Model Query response [Failure, Reason] - else platform successfully fetched the xApp queried information - platform-->>xApp: 4. Stored Model Query response [Success, AI/ML Model List] - end - -``` - -Sequence diagram for Stored Model Query procedure. Lifelines: xApp and Near-RT RIC platform. The process involves a request from xApp to platform, a lookup by platform, and then an alt block for success or failure response. - -Figure 9.7.4.2-1: Stored Model Query procedure - -#### 9.7.4.3 Model Retrieve procedure - -The Model Retrieve procedure in the Near-RT RIC enables an xApp to retrieve an AI/ML model it has stored in the Near-RT RIC. - -| Use Case Stage | Evolution / Specification | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp retrieves an AI/ML model it has stored from the Near-RT RIC platform. | -| Actors and Roles |
  • xApp: Originator of Model Fetch request;
  • Near-RT RIC platform, with the following functionalities:
    • AI/ML support.
| -| Pre-conditions |
  • AI/ML workflow services have been registered with Near-RT RIC platform;
  • At least one AI/ML model has been stored by xApp in the Near-RT RIC Platform
| -| Begins when | xApp determines to retrieve an AI/ML model from the Near-RT-RIC platform. | -| Step 1 (M) | xApp requests to Near-RT RIC platform to retrieve an AI/ML model from the Near-RT-RIC platform. | -| Step 2 (M) | Near-RT RIC platform retrieves xApp required AI/ML model from Near-RT-RIC platform. | -| | [ALT] Step 3 is executed if the platform failed to retrieve the AI/ML model. | -| Step 3 (M) | A failure is responded to the originating xApp, possibly including appropriate reason | -| | [ELSE] Step 4 is executed if the platform successfully retrieved the AI/ML model. | -| Step 4 (M) | Near-RT RIC platform responds success to the originating xApp, with AI/ML Model File. | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Collections "xApp" as xApp - Participant plt as "Near-RT RIC platform" -End box - -xApp -> plt: 1. Model Retrieve request [AI/ML Model Identifier] -plt --> plt: 2. Retrieve requested AI/ML model -alt platform failed to retrieve the AI/ML model - plt --> xApp: 3. Model Retrieve response [Failure, Reason] - -``` - -``` - -else platform successfully retrieved the AI/ML model -plt -> xApp: 4. Model Retrieve response [Success, AI/ML Model File] -end alt -@enduml - -``` - -![Sequence diagram for Model Retrieve procedure. Lifelines: xApp and Near-RT RIC platform. The process involves a request from xApp, a response from platform, an alt block for failure/success, and a final response from platform.](e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant platform as Near-RT RIC platform - Note right of platform: Near-RT RIC - xApp->>platform: 1. Model Retrieve request [AI/ML Model Identifier] - platform-->>xApp: 2. Retrieve requested AI/ML model - alt platform failed to retrieve the AI/ML model: 3. Model Retrieve response [Failure, Reason] - else platform successfully retrieved the AI/ML model: 4. Model Retrieve response [Success, AI/ML Model File] - -``` - -Sequence diagram for Model Retrieve procedure. Lifelines: xApp and Near-RT RIC platform. The process involves a request from xApp, a response from platform, an alt block for failure/success, and a final response from platform. - -Figure 9.7.4.3-1: Model Retrieve procedure - -#### 9.7.4.4 Model Delete procedure - -The Model Delete procedure in the Near-RT RIC allows an xApp to request to Near-RT RIC platform to delete an AI/ML model it has stored from the platform. - -| Use Case Stage | Evolution / Specification | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | xApp intends to delete an AI/ML model it has stored in the Near-RT RIC. | -| Actors and Roles |
  • xApp: Originator of Model Delete request;
  • Near-RT RIC platform, with the following functionalities:
    • AI/ML support.
| -| Pre-conditions |
  • AI/ML workflow services have been registered by Near-RT RIC platform;
  • xApp has already stored the AI/ML model in the Near-RT RIC platform it requests to delete.
| -| Begins when | xApp determines to delete an AI/ML model in the Near-RT-RIC platform. | -| Step 1 (M) | xApp sends a request to Near-RT RIC platform to delete an AI/ML model in the platform. | -| Step 2 (M) | Near-RT RIC platform deletes xApp requested AI/ML model in platform. | -| | [ALT] Step 3 is executed if the platform failed to delete the requested AI/ML model | -| Step 3 (M) | A failure is responded to the originating xApp, possibly including appropriate reason. | -| | [ELSE] Steps 4 are executed if the platform successfully deleted the requested AI/ML model | -| Step 4 (M) | Near-RT RIC platform responds success to the originating xApp | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -Box "Near-RT RIC" - Collections "xApp" as xApp - Participant plt as "Near-RT RIC platform" -End box - -``` - -``` - -xApp -> plt: 1. Model Delete request [AI/ML Model Identifier] -plt -> plt: 2. Delete requested AI/ML model -alt platform failed to delete the requested AI/ML model -plt -> xApp: 3. Model Delete response [Failure, Reason] -else platform successfully deleted the requested AI/ML model -plt -> xApp: 4. Model Delete response [Success] -end alt -@enduml - -``` - -![Sequence diagram illustrating the Model Delete procedure between an xApp and a Near-RT RIC platform. The diagram shows a request, an internal platform action, and an alt block for failure or success responses.](649426750a89fa0e5d7c1736d5cf72c6_img.jpg) - -``` - -sequenceDiagram - participant xApp - participant Near-RT RIC platform - Note over xApp, Near-RT RIC platform: Near-RT RIC - xApp->>Near-RT RIC platform: 1. Model Delete request [AI/ML Model Identifier] - Near-RT RIC platform->>Near-RT RIC platform: 2. Delete requested AI/ML model - alt platform failed to delete the requested AI/ML model - Near-RT RIC platform->>xApp: 3. Model Delete response [Failure, Reason] - else platform successfully deleted the requested AI/ML model - Near-RT RIC platform->>xApp: 4. Model Delete response [Success] - end - -``` - -Sequence diagram illustrating the Model Delete procedure between an xApp and a Near-RT RIC platform. The diagram shows a request, an internal platform action, and an alt block for failure or success responses. - -Figure 9.7.4.4-1: Model Delete procedure - -# Annex A (informative): Potential conflict types among xApps for RRM optimization - -The control target of the radio resource management can be a cell, a UE or a bearer, etc. The control contents of the radio resource management can cover access control, bearer control, handover control, QoS control, resource assignment and so on. The control time span indicates the valid control duration which is expected by the control request. The conflicts of control can be illustrated as below. - -- 1) **Direct Conflicts:** The conflicts can be observed directly by Conflict Mitigation. Some cases are described as below: - - Two or more xApps request different settings for the very same configuration of one or more parameters of a Control Target. Conflict mitigation processes the requests and decides on a resolution. - - The new request from an xApp may conflict with the running configuration resulting from a previous request of another or the same xApp. - - The total requested resources from different xApps may exceed the limitation of the RAN system, e.g., the sum of resources required by the two different xApps may be far beyond the resource limitation of the RAN system. -- 2) **Indirect Conflicts:** The conflicts cannot be observed directly, nevertheless, some dependence among the parameters and resources that the xApps target can be observed. Conflict Mitigation may anticipate the possible conflicts and take actions to mitigate them. For instance, different xApps target different configuration parameters to optimize the same metric according to the respective objective. Even though this will not result in conflicting parameter settings, it may have uncontrollable or inadvertent system impacts. One example of such indirect conflicts can occur when the changes required by one xApp create a system impact which is equivalent to a parameter change targeted by another xApp. E.g., antenna tilts and measurement offsets are different control points, but they both impact the handover boundary. -- 3) **Implicit Conflicts:** The conflicts cannot be observed directly, even the dependence between xApps is not obvious. For instance, different xApps may optimize different metrics and (re-)configure different parameters. Nonetheless, optimizing one metric may have implicit, unwanted, and maybe adversary side effects on one of the metrics optimized by another xApp. E.g., protecting throughput metrics for GBR users may degrade non-GBR metrics or even cell throughput. - -For mitigating these conflicts, different approaches exist: - -- 1) Direct conflicts typically can be mitigated by pre-action coordination, i.e., the xApps or a Conflict Mitigation component needs to make the final determination on whether any specific change is made, or in which order the changes are applied. -- 2) Indirect conflicts can be resolved by post-action verification. Here, the actions are executed and the effects on the target metric are observed. Based on the observations, the system has to decide on potential corrections, e.g., rolling back one of the xApp actions. -- 3) Implicit conflicts are the most difficult to mitigate since these dependencies are difficult or impossible to observe and therefore hard to model in any mitigation scheme. In some cases, it may be possible to design around such conflicts by ensuring that use cases (xApps) target different parameters, thus falling back to approach 2), but preferably, a generic approach to managing such conflicts is established. - -The individual xApp goals are defined by A1 policies, but it is also important to define utility metrics that incorporate the relative importance of each of the metrics targeted by the xApps as well as the importance of the optimization (use case). A Conflict Mitigation function may also use ML approaches, e.g., Reinforcement Learning, to a-priori assess, for each proposed change, the likely probability of degrading a metric versus the potential improvement. - -# Annex B (informative): Example of xApp's workflow - -Exemplified in this annex is a high-level description of an xApp's workflow, which may occur between the xApp and the Near-RT RIC platform after the xApp is instantiated on O-Cloud. Note that some operations may not be performed, and that the sequence and repetitions of the operations may vary from this example, depending on the use cases and the xApp's business logic. - -``` -@startuml -skin rose -skinparam ParticipantPadding 10 -skinparam BoxPadding 5 -skinparam lifelineStrategy solid - -box "Near-RT RIC" -Participant xApp -Participant plt as "Near-RT RIC platform" -Collections others as "Other xApp" -end box - -xApp <-> plt: Registration of xApp with Near-RT RIC platform -xApp <-> plt: Configuration of xApp by the Near-RT RIC platform -xApp <-> plt: Discovery and registration of applicable Near-RT RIC APIs -xApp <--> plt: Retrieval of E2 Node list and state information from the Near-RT RIC platform -xApp <--> plt: AI policy assignment from the Near-RT RIC platform -xApp <--> plt: Data collection from the Near-RT RIC platform -xApp <--> others: Data collection from other xApps -xApp <--> plt: AI/ML operations assisted by the Near-RT RIC platform -xApp <--> plt: Conflict mitigation, and control/optimization for the E2 Node -xApp <--> plt: Data sharing with the Near-RT RIC platform -xApp <--> others: Data sharing with other xApps -xApp <--> plt: Reporting of performance and fault data -... -@enduml -``` - -![Sequence diagram titled 'Near-RT RIC' showing the workflow of an xApp. The diagram features three lifelines: 'xApp' (left), 'Near-RT RIC platform' (middle), and 'Other xApp' (right). The sequence of messages is as follows: 1. xApp sends 'Registration of xApp with Near-RT RIC platform' to the platform. 2. The platform responds with 'Configuration of xApp by the Near-RT RIC platform'. 3. The xApp then sends 'Discovery and registration of applicable Near-RT RIC APIs'. 4. The platform replies with 'Retrieval of E2 Node list and state information from the Near-RT RIC platform'. 5. Next is 'A1 policy assignment from the Near-RT RIC platform'. 6. The xApp sends 'Data collection from the Near-RT RIC platform'. 7. It also sends 'Data collection from other xApps' to the Other xApp. 8. The platform assists with 'AI/ML operations assisted by the Near-RT RIC platform'. 9. The platform handles 'Conflict mitigation, and control/optimization for the E2 Node'. 10. The xApp sends 'Data sharing with the Near-RT RIC platform'. 11. It also sends 'Data sharing with other xApps' to the Other xApp. 12. Finally, the xApp sends 'Reporting of performance and fault data' to the platform.](a4c80b98452e7949d9f8d969dc9cebf7_img.jpg) - -Sequence diagram titled 'Near-RT RIC' showing the workflow of an xApp. The diagram features three lifelines: 'xApp' (left), 'Near-RT RIC platform' (middle), and 'Other xApp' (right). The sequence of messages is as follows: 1. xApp sends 'Registration of xApp with Near-RT RIC platform' to the platform. 2. The platform responds with 'Configuration of xApp by the Near-RT RIC platform'. 3. The xApp then sends 'Discovery and registration of applicable Near-RT RIC APIs'. 4. The platform replies with 'Retrieval of E2 Node list and state information from the Near-RT RIC platform'. 5. Next is 'A1 policy assignment from the Near-RT RIC platform'. 6. The xApp sends 'Data collection from the Near-RT RIC platform'. 7. It also sends 'Data collection from other xApps' to the Other xApp. 8. The platform assists with 'AI/ML operations assisted by the Near-RT RIC platform'. 9. The platform handles 'Conflict mitigation, and control/optimization for the E2 Node'. 10. The xApp sends 'Data sharing with the Near-RT RIC platform'. 11. It also sends 'Data sharing with other xApps' to the Other xApp. 12. Finally, the xApp sends 'Reporting of performance and fault data' to the platform. - -**Figure B-1: Example of xApp's workflow after its instantiation** - -Figure B-1 shows the following operations for the xApp: - -- Registration of xApp with Near-RT RIC platform: This is achieved via the xApp registration procedure in clause 9.4.1. -- Configuration of xApp by the Near-RT RIC platform: This is achieved via the Management API procedures in clause 9.4. -- Discovery and registration of applicable Near-RT RIC APIs: This applies to the Near-RT RIC APIs that are not preconfigured, and is achieved via the API Enablement procedures in clause 9.6. -- Retrieval of E2 Node list and state information from the Near-RT RIC platform: This is achieved via the SDL API procedures in clause 9.5. -- A1 policy assignment from the Near-RT RIC platform: This is achieved via the A1 Policy API procedures in clause 9.2.2. -- Data collection from the Near-RT RIC platform: This is achieved via the E2 related API procedures in clause 9.3.2, the A1-EI API procedures in clause 9.2.3, and the SDL API procedures in clause 9.5. -- Data collection from other xApps: This is achieved via the SDL API procedures in clause 9.5. -- AI/ML operations assisted by the Near-RT RIC platform: This is achieved via the AI/ML API procedures in clause 9.7. -- Conflict mitigation, and control/optimization for the E2 Node: This is achieved via the E2 related API procedures in clause 9.3. -- Data sharing with the Near-RT RIC platform: This is achieved via the SDL API procedures in clause 9.5. -- Data sharing with other xApps: This is achieved via the SDL API procedures in clause 9.5. -- Reporting of performance and fault data: This is achieved via the Management API procedures in clause 9.4. - -NOTE: The xApp's communications with the Near-RT RIC platform and other xApps are protected according to the security requirements specified in WG11. - -# Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2019.11.01 | 00.00.00 | Initial Skeleton | -| 2019.11.11 | 00.00.01 | Edits to Near-RT RIC functions description (Section 6) | -| 2019.11.19 | 00.01.00 | Approved skeleton based on WG3_2019.11.19_CMCC_ORAN-WG3.RIC-ARCH.Skeleton_v2 | -| 2019.12.04 | 00.01.01 | Intermediate version based on WG3_2019-12-2_ATT-CICT-CMCC_CR_nRT-RIC-Arch_Section45_v3 | -| 2019.12.13 | 00.01.02 | Intermediate version based on WG3_2019.12.09_JIO_CR_ORAN-WG3.RICARCH.0_running v00.01.01_v2 | -| 2019.12.20 | 00.01.03 | Intermediate version based on WG3_2019-12_16_CMCC_ATT_CR_nRT-RIC-Arch_Section6_1_v4.1 | -| 2020.01.21 | 00.01.04 | Intermediate version based on | -| 2020.01.22 | 00.01.05 | WG3_2020-1_14_ATT_CR_NearRTRICArchSection 6.docx | -| 2020.02.04 | 00.01.06 | WG3_2020-01-10_Lenovo_CR_NearRTRICArch_section6.2.4_v2.1_xxcmt.docx | -| 2020.02.12 | 00.01.07 | Intermediate version based on | -| 2020.02.12 | 00.01.08 | WG3_2020_01_21_Nokia_CICT_CMCC_CR_near-RT RIC Architecture Merging Conflict Mitigation_v0.1a_clean | -| 2020.02.13 | 00.01.09 | WG3_2020-01-21_Lenovo_CR_NearRTRICArch_section6.3_v1.4_xApp | -| 2020.02.14 | 00.01.10 | Intermediate version based on WG3 TG approval and | -| 2020.02.17 | 01.00.00 | Version number changed to 01.00.00 for WG3 approval | -| 2020.02.24 | 01.00.00 | Editorial corrections collected during WG3 approval process | -| 2020.10.22 | 01.00.01 | Editorial corrections collected from Intel about Non-RT RIC | -| 2020.10.28 | 01.00.02 | The name of API was changed to Near-RT RIC API according to the agreement on TG Conference #33 | -| 2020.11.03 | 01.00.03 | Addition of CR adopted during TG Conference #33 | -| 2020.11.04 | 01.00.04 | "RIC framework" was changed to "RIC platform" according to the agreement on TG Conference #34 | -| 2020.11.06 | 01.00.05 | Addition of CRs adopted during TG Conference #34 | -| 2020.11.08 | 01.01.00 | Editorial corrections collected during WG3 email reflector final review | -| 2020.11.17 | 01.01.00 | Withdraw section 7.7 from RICARCH v1.1 according to the comment during WG3 email reflector final review | -| 2020.11.25 | 01.01.00 | Version 1.1 for Board approval after 2021 copyright update proposed by TSC | -| 2020.12.14 | 02.00.01 | Merged the approved CR CICT-2020.07.28-WG3-CR-xxxx-prdcedures-in-A1-related-APIs-v1.4.1.docx according to the agreement on TG Conference #34. | -| 2021.02.03 | 02.00.02 | Discuss the next step of Section 7.7 from the CR ONF-AO-2020.10.27-WG3-CR-001-Open API design-v03.docx. | -| 2021.02.23 | 02.00.03 | Merged the approved CR NOK-2020.11.26-WG3-CR-0001-RICARCHsection9.x-v6.docx according to the agreement in TG conference #39 | -| 2021.03.02 | 02.00.04 | Deleted section 7.7, updated section 9.1 using the newly agreed CR CICT-2020.07.28-WG3-CR-0002-procedures in A1 related APIs-v2.0.0.docx, removed (M) and (O) for the informative steps in section 9 according to the agreement on TG Conference #40, . | -| 2021.03.05 | 02.00.05 | Addition of API enablement function, and Stage-2 definitions for part of the Near-RT RIC APIs. | -| 2021.03.06 | 02.00 | Incremented version for WG3 vote | -| 2021.03.14 | 02.00 | Editorial updates received before TSC vote | -| 2021.03.16 | 02.00 | Removal of UML code, and editorial updates during TSC vote | -| 2021.05.27 | 02.01.01 | Clean version with UML code | -| 2021.06.15 | 02.01.02 | Incorporated CRs: | -| 2021.10.12 | 02.01.03 | FB.AO-2021.04.23-O-RAN-CR-1001-SDL Subscribe Push-v01.docx | -| 2021.11.08 | 02.01.04 | INT.AO-2021.05.04-WG3-CR-0004-RICARCH-AIMLsupport_v2.docx | -| 2022.04.07 | 02.01.05 | Implemented CRs:
(1) CMCC CR-0002 in ARCH#65; (2) NOK.AO CR-0008 in ARCH#67; (3) NOK.AO CR-0009 in ARCH#67; | -| 2022.05.06 | 02.01.06 | Implemented CRs:
(1) NOK CR-0011 in ARCH#68; (2) NOK CR-0005 in ARCH#68; | - -| | | | -|------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2022.07.15 | 02.01.07 | Implemented CRs:
(1) CICT CR-0005 in ARCH#69; (2) NOK CR-0013 in ARCH#71; (3) CMCC CR-0003 in ARCH#73; (4) CMCC CR-0004 in ARCH#73; | -| 2022.07.22 | 02.01.08 | Editorial updates. | -| 2022.07.29 | 02.01.09 | Editorial updates during WG3 electronic vote. | -| 2022.08.02 | 03.00 | Version incremented as 03.00 for TSC | -| 2022.09.16 | 03.00.00 | Initial baseline | -| 2022.11.11 | 03.00.01 | Addition of CRs:





Minor editorial clean-ups. | -| 2022.11.17 | 03.00.02 | Changes reflecting remarks received during WG3 approval process
- Update copyright year 2023, and release number R003.
- Fix xApp/Near-RT RIC platform in the “Actors and Roles” of tables in 9.4.8 and 9.4.13.
- Fix the labels for a few steps in 9.4.8, 9.4.12 and 9.4.13 as “[informative]” instead of “(M)”.
- Add missing step descriptions in 9.4.8.
- Other minor editorial clean-ups. | -| 2022.11.20 | 04.00 | Version incremented to 04.00 for TSC. | -| 2022.12.13 | 04.00.00 | Initial baseline | -| 2023.03.29 | 04.00.01 | Addition of CRs:
-
-
Minor editorial clean-ups. | -| 2023.07.10 | 04.00.02 | Addition of CRs:
- CMCC-2023.03.31-WG3-CR-0007-RICARCH-Improvement in Section 6-v05.docx
- CMCC.AO-2023.05.08-WG3-CR-0010-Service definitions for Near-RT RIC APIs-v04.docx
Typo fix in the caption of Fig 6.1-1. | -| 2023.07.17 | 04.00.03 | Addition of CR:
- CMCC-2023.06.14-WG3-CR-0011-RICARCH-Fix the use of Near-RT RIC platform and its functionalities in clause 9 -v03.docx
Minor editorial clean-ups. | -| 2023.07.21 | 04.00.04 | Addition of CR:
CMCC-2023.04.18-WG3-CR-0009-AIML Support Function-v05.docx
Updated to new O-RAN TS template. | -| 2023.07.28 | 04.00.05 | Resolution of review comments during WG3 poll. | -| 2023.07.29 | 05.00 | Version increment for TSC approval. | -| 2023.08.08 | 05.00.00 | Initial baseline | -| 2023.11.24 | 05.00.01 | Addition of CRs:
-
-
-
-
-
-
Adding the full change history.
Editorial corrections and improvements. | -| 2024.03.11 | 05.00.02 | Addition of CRs:
- | - -| | | | -|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | |
  • - <CMCC-2024.01.30-WG3-CR-00019-RICARCH-AIML data pipelining services-v02.docx>
  • - <CMCC-2024.01.30-WG3-CR-00018-RICARCH-AIML training services-v02.docx>
  • - <CMCC-2023.09.20-WG3-CR-00016-RICARCH-AIML inference services-v02.docx>
  • - <CMCC-2024.02.05-WG3-CR-00020-RICARCH-Stage 2 enhancements to SDL Information API-v01.docx>
  • - <NOK-2024.02.21-WG3-CR-00021-RICARCH-TimeoutCases-v01.docx>

Editorial corrections and improvements.

| -| 2024.03.21 | 05.00.03 |

Addition of CRs:

  • - <NOK-2024.03.12-WG3-CR-00025-RICARCH-Clause-5,6,6A,7,9-CORRECTIONS-v02.docx>
  • - <NOK-2024.03.12-WG3-CR-00024-RICARCH-AIML data pipelining services-CORRECTIONS-v01.docx>
  • - <NOK-2024.03.12-WG3-CR-00023-RICARCH-AIML training services-CORRECTIONS-v03.docx>
  • - <NOK-2024.03.12-WG3-CR-00022-RICARCH-AIML inference services-CORRECTIONS-v03.docx>
| -| 2024.03.31 | 05.00.04 | Editorial corrections during WG3 review for March 2024 publication train. | -| 2024.04.01 | 06.00 | Version incremented as 06.00 for TSC | -| 2024.08.20 | 06.00.01 |

Addition of CRs:

  • - <CUC-2024.4.9-WG3-CR-0001-RICARCH-some editorial corrections_v01.docx>
  • - <CUC-2024.4.15-WG3-CR-0002-RICARCH-Correct message in E2 Control procedure_v01.docx>
  • - <NOK-2023.11.29-WG3-CR-00020-RICARCH-Terms-v03.docx>
  • - <NOK-2024.04.03-WG3-CR-00026-RICArch OAM requirements_v03.docx>
  • - <CMCC-2023.06.30-WG3-CR-00012-RICARCH-Service definition for A1 Policy API-v03.docx>
  • - <CMCC-2023.09.20-WG3-CR-00015-RICARCH-model management and exposure services-v04.docx>
  • - <NOK-2024.06.05-WG3-CR-00027-RICArch requirement corrections v05.docx>
  • - <CMCC-2024.05.20-WG3-CR-00021-RICARCH-An informative example of xApp's workflow-v05.docx>

Editorial corrections and improvements.

| -| 2024.11.12 | 06.00.02 |

Addition of CRs:

  • - <NEC-2024.10.29-WG3-CR-00034-RICARCH-Add E2 Query-v02.docx>
  • - <NEC-2024.10.29-WG3-CR-00035-RICARCH-Add E2 Subscription Modification-v02.docx>
  • - <NOK-2024.10.15-WG3-CR-00028-RICARCH-ConMit-adding-general-support-descriptions-v03.docx>
  • - <NOK-2024.10.15-WG3-CR-00029-RICARCH-ConMit-adding-E2 Conflict Mitigation Section-v04.docx>
  • - <CMCC-2024.11.13-WG3-CR-00022-RICARCH-Reference cleanups and updates-v01.docx>

Editorial corrections and improvement.

| -| 2024.12.05 | 06.00.03 | Editorial improvements during the WG3 poll. | -| 2024.12.05 | 07.00 | Version incremented to 07.00 for TSC. | -| 2025.10.14 | 07.00.01 |

Addition of CRs:

  • - <NOK-2024.10.15-WG3-CR-00030-RICARCH-ConMit-modifying-E2 Guidance Service-v04.docx>
  • - <CMCC-2025.09.17-WG3-CR-00023-RICARCH-Removing SDL registration procedures-v1.docx>

Editorial corrections and improvement.

| -| 2025.11.13 | 07.00.02 |

Addition of CRs:

  • - <CMCC-2025.10.17-WG3-CR-00025-RICARCH-ODR revisions in Clause 6-v1.docx>
  • - <CMCC-2025.10.17-WG3-CR-00026-RICARCH-ODR revisions in Clause 6A-v2.docx>
  • - <CMCC-2025.10.17-WG3-CR-00027-RICARCH-ODR revisions in Clause 7-v1.docx>
  • - <CMCC-2025.10.17-WG3-CR-00028-RICARCH-ODR revisions in Clause 8-v1.docx>
  • - <CMCC-2025.10.17-WG3-CR-00029-RICARCH-ODR revisions in Clause 9-v2.docx>
  • - <CMCC-2025.10.17-WG3-CR-00024-RICARCH-ODR revisions in Clause 5-v2.docx>

Alignment to latest TS template.
Editorial corrections and improvement.

| - -| | | | -|------------|-------|--------------------------------------| -| 2025.12.08 | 08.00 | Version incremented as 06.00 for TSC | -|------------|-------|--------------------------------------| \ No newline at end of file diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/00504fc688ebcf131ccbeff94dfc9939_img.jpg deleted file mode 100644 index 2b3c6b1a21c0213ec8e1ad164e4d5a82794fd290..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/00504fc688ebcf131ccbeff94dfc9939_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:66d252ef9d968abfbfa65d47d5a5b0b825a311da3d137c5854202f349b52f4ac -size 97954 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/01832e59ebad7ada5e790de6f90cc9b6_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/01832e59ebad7ada5e790de6f90cc9b6_img.jpg deleted file mode 100644 index 7054abd463e760a57635d455fad0099968ef2bfb..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/01832e59ebad7ada5e790de6f90cc9b6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1ec24e77b387f6d11905ce4816f72bac248c76bd5e6ff105e37ba525314bb07a -size 96089 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/042733dc5e8e7f5f30b60adba3266cde_img.jpg deleted file mode 100644 index 0d4a50cbcc3d944bf3b19b1faeda8d230c142674..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/042733dc5e8e7f5f30b60adba3266cde_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4d96de569f515d8793e87fb7b75dd94f6058a793eaa77a56529bf0a15c1df66f -size 107999 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/060648daa95345c57f019fc00ad75993_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/060648daa95345c57f019fc00ad75993_img.jpg deleted file mode 100644 index 1d75b12e4fd87600f6fa94ee164f6d6c28ab97f4..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/060648daa95345c57f019fc00ad75993_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b812ff04900e43ab7e3434b34e95eba0c203440cc45f1e909dc9a0da43fdde3e -size 33569 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/08783c875dd39684fee7f2a40b584c64_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0a65720e640be13541e947c06c7a8c7f_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0b2ee589f5c7802f3d332f421340cae1_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0b2ee589f5c7802f3d332f421340cae1_img.jpg deleted file mode 100644 index de163a8825b252b1778fdf4b73ac3f3273afcc23..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0b2ee589f5c7802f3d332f421340cae1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b1512d9b7754f8fc7525d1df2425579495261fcdd6162293ab52435c614d754b -size 76409 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0b998e3ad8f9d104768642612605cb35_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0b998e3ad8f9d104768642612605cb35_img.jpg deleted file mode 100644 index 613c1015f2e6cc8ebe74856bf5a85b7daa02aafe..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0b998e3ad8f9d104768642612605cb35_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b5f5dc7268e1b5c54b432065a8aa9f63e4c2a4b85f9a2ecf0b2e06d803e87385 -size 35102 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg deleted file mode 100644 index 7d20fad103efba3f22a36a722bc3cda4f0f59a66..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:29bb9d81d94b6c3ecbddfd4f674bf279e7fac909ab52807c32adcb8540b408a4 -size 56007 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/107c8e1abcb7033ad244e30e7a910045_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/107c8e1abcb7033ad244e30e7a910045_img.jpg deleted file mode 100644 index a1a82b48043672a77ea3ad35ddd51bf40c2f630a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/107c8e1abcb7033ad244e30e7a910045_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7cdf7a2779b3f70d9dfd01566ec1bfbd1a165f3491981cffbc333234c0918ee6 -size 143330 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1099a4137017f2d9721d546bbb1e9362_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/110058f0fd9c7ca251db430f6df06b80_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1142ba0197b158bb198186fe8baccc32_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1142ba0197b158bb198186fe8baccc32_img.jpg deleted file mode 100644 index 9e1d8e0e34b880c499e9c524788b882a82c191ab..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1142ba0197b158bb198186fe8baccc32_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b789926c9841cb1dc193c366f0c6ae73bf9d416cdbdadace099a53a7f9546df9 -size 135642 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/11f18bf0233d812ad2604f88f3385d60_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/11f18bf0233d812ad2604f88f3385d60_img.jpg deleted file mode 100644 index 08e27b11343d2ec78574c0d1ffc30c900083482c..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/11f18bf0233d812ad2604f88f3385d60_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8400b0b4ebe558ee583b6bd4388ef53d969b8e85a2e1db32ae8dd44189e42477 -size 58079 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/137bcfed81ada68ca5162ca5afed35c7_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/137bcfed81ada68ca5162ca5afed35c7_img.jpg deleted file mode 100644 index f492af4dc2e8b12b242d8a548ddb2d880e54aacb..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/137bcfed81ada68ca5162ca5afed35c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eebea4ed06c763402d941702689d833df95ce50b1f7a0c985bc55b19e0912787 -size 86462 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/14af8d47efd24c21fddf71b2415b6397_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/153b4763edcf6b16d783052c7ad165f1_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/17431d8b59408f09df7552d8bdbaa015_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/17431d8b59408f09df7552d8bdbaa015_img.jpg deleted file mode 100644 index bd6f5f035755db2726f0f2f5d85a82edecee8a2f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/17431d8b59408f09df7552d8bdbaa015_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:38515b09b47a0ed574478b6d857d67816cf656a77fdf7c746b7d6d16f4dc3d4e -size 67361 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/18d7d8de298d79e7bc87af5217f11203_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/18d7d8de298d79e7bc87af5217f11203_img.jpg deleted file mode 100644 index edb6beec56e0f1a66785cb19acc73b89d74767de..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/18d7d8de298d79e7bc87af5217f11203_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8f892aac7f40d94b8b4b63630287ec841509a0b1cb1606ff54f2ea5b9600a446 -size 89364 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1baaba7a6e54e77197475726c871067d_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1e7157ed1c2b915b5b1823b6ad189038_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1f0d4018f872bfcffec260045c6dd734_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1ff58ab75ff926ead7067453006a75fe_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1ff58ab75ff926ead7067453006a75fe_img.jpg deleted file mode 100644 index 16006543e5524c0dea1324abb185ec9b70137610..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/1ff58ab75ff926ead7067453006a75fe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:631b42565ca60dc356b0cb2e56cb0d7257c14d58bae9b519138f65ce7ed74e4d -size 60843 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/226f5e462c99b71e08dc9abaa5ae260c_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/255efa1d461fc79b4ed367aaec11637f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/255efa1d461fc79b4ed367aaec11637f_img.jpg deleted file mode 100644 index 095afb88960cbd2ef0ebd91c86642553c3981f89..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/255efa1d461fc79b4ed367aaec11637f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:93ceec868c2312d3bd4e4c5e5a799d7ed91b08fc499ea9d670c1988a3909bb2c -size 167595 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg deleted file mode 100644 index 4989c87e2a164514d0ae898bc22c9c0893a4462b..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/276d5f4022bc6b9e4687f9ba4fc7594c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5ad320fe339c83740cb34be5fac9f6340b1755433848abf79eee33f5d3e0ad4e -size 55723 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/29f3760c0230631eb03f67030ef65ed0_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg deleted file mode 100644 index 3cd61879b25c0d668b03577a461e7b4be1392dd8..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:05ff2b284446dc7e88ef3ccedcbc2d47150233a091289cb5f3026905feda7bbb -size 79193 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/2b00743506f6a3bbd17af764162dc76d_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/2b00743506f6a3bbd17af764162dc76d_img.jpg deleted file mode 100644 index 6c055633737bb60ef7cff8a607cb1516c85bc456..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/2b00743506f6a3bbd17af764162dc76d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e114c256af8b34852624847515841ebf254c93e88908c38604db12b075214c98 -size 103827 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3117e1f4e4767bab3f5c7cfaf4804652_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg deleted file mode 100644 index 5ba44e7ace9be9f84e747af759b9f081e8679909..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b873f817b180df2e60c8e33500459b5d90f462980bf24464a2afb28e1ea93b21 -size 110525 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/329c96049bb432e9c2cbda4e224a0c9c_img.jpg deleted file mode 100644 index f0c32d2c0f1052caea31cae7b2dbbf6b3b5854d5..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/329c96049bb432e9c2cbda4e224a0c9c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a5b81aa6ba6a358d46b0406f29fa7c227dc4f900f4dc0be08fe2d8f1519e84c7 -size 138145 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/347010b7ac06d3ae97927fde0f784d7c_img.jpg deleted file mode 100644 index 1fc1bf2b1a38b5e6b4fe30079474307ea40e343c..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/347010b7ac06d3ae97927fde0f784d7c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:65f641f543a465c7494f8c25b6afd7508226bb782c782087e63c260fd7e28890 -size 112211 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/35437f160e157760713aa85be471c3f3_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/35437f160e157760713aa85be471c3f3_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/35437f160e157760713aa85be471c3f3_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg deleted file mode 100644 index 0c4849d48675f0880feb5d352cacfc5bd2d416a0..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/36117e9cb27c58484cd8d3e5f9dc7ac3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f77e814a733f8a3e0a054321160a62452edf73387d4865b6046ec8c3f444b207 -size 23546 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/36e4a08fb5114c98c80f946714cc6c30_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/36fb8f844f936e7a1de4838da774f2f9_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3750b0149a6380885998ab3ca6a8787c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3750b0149a6380885998ab3ca6a8787c_img.jpg deleted file mode 100644 index 83f7cf7656309fea6d4966ec82092476d608a22e..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3750b0149a6380885998ab3ca6a8787c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:148d05a8d5d6c2ed5f8ebb7c01489a3b9ec644acb3b3fc9edafa2ec68c95103f -size 95165 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index b038a0d715eaed6beb3b1b72466eae33705dc022..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0db392b6de38a78cd2a9ab7ecd6c269a7e574aca0c1ccd9f7c68b6a9886b282e -size 4507 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/392a79ccd95e682ccd08f35ab2e64144_img.jpg deleted file mode 100644 index 1a547866dbc08ed2572dcd5b0ff9465bea348250..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/392a79ccd95e682ccd08f35ab2e64144_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5744502342fb723e80ccb8e3d3686d4216625a731670837a01a0d598d2a13995 -size 50627 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg deleted file mode 100644 index 3dafe7d43b51f38bf085befd8821e2d38161fa23..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3b281ef3b6cc5f8ba97cbc011bfaac79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4ae878773b946d45aa5d73ae564a2e5ea09467378e6a1cdc98eea582b8220056 -size 208766 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3b89d812329a65ab156184a40524adf0_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3b89d812329a65ab156184a40524adf0_img.jpg deleted file mode 100644 index 7b709785e7bde6ab0aefde9a9de8aa8821419443..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3b89d812329a65ab156184a40524adf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7fce5ec145d266c60c3b370530b3bedf9dceca212603e3c67667c5ad79226fb7 -size 4577 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3c0be9369e1f99f7f820fda3f9d676e6_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3c0be9369e1f99f7f820fda3f9d676e6_img.jpg deleted file mode 100644 index 599816a75e72b569ec61700847b4a0e724e1cd47..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3c0be9369e1f99f7f820fda3f9d676e6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:597144ae94fe06a8af272cdd022872f75c9387aaab575e493d68e6afcbec379a -size 79572 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3d590ad29ecfe728f07432e6fcb59064_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3d590ad29ecfe728f07432e6fcb59064_img.jpg deleted file mode 100644 index ee96c15422aea0657607e7514b4214a86e3a71cf..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3d590ad29ecfe728f07432e6fcb59064_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f671f4faa04345bde282dffcba11726d4827ef1e03c86feee9ce7b9321ea858c -size 68726 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3ec35c497a0765a1a885c85f214b1bef_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3ec35c497a0765a1a885c85f214b1bef_img.jpg deleted file mode 100644 index efd6a6dad55f2e78dbd9a49f67dc152930e7d4e3..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/3ec35c497a0765a1a885c85f214b1bef_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2bd3a728b1f33393c530a4ade16b6be653401966e98df1e28e0b98cf2c4547b3 -size 65183 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/41aef1f5efab13d4f38f69e86c726062_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/41aef1f5efab13d4f38f69e86c726062_img.jpg deleted file mode 100644 index 8f16c43cee91d6ba0c6965d60686b92c1091a568..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/41aef1f5efab13d4f38f69e86c726062_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:df630e822e2708773fbcbe0e31d0439174107b09f493d5a0706229ae3c92962c -size 119796 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/446c0bd806260f25430cadb01a6786c7_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/481b1f80fc31ebebb30d1f57d31e3af3_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/487c58c79e44e6cf98b6368b6667b9c6_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/487c58c79e44e6cf98b6368b6667b9c6_img.jpg deleted file mode 100644 index d802746dde0d77de166ea1b97c3e50538fa0dba4..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/487c58c79e44e6cf98b6368b6667b9c6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a148c8b2f1dce7fca3a80495609a0c658c92a162056b0ee89b3bce1c7f76fbf2 -size 43867 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/488b6387bc5fe15b9528eca7968a8733_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/4932f76f000f1673ac40baf1419fbb3b_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/49fe8fe978c0f7e73112d231feb377eb_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/49fe8fe978c0f7e73112d231feb377eb_img.jpg deleted file mode 100644 index e3eeb3e7d9bc9053e73d9de6ba6b3f13da0231bd..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/49fe8fe978c0f7e73112d231feb377eb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:938c0e4b994e22a3eaf8bd1b93b0500d20709f85475e0de02af90c5f0932f171 -size 98932 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/4a04896dfb569893fba50729314024f5_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg deleted file mode 100644 index c13e562e349ff6b7ba41a7ca68771d873ff399a2..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:80fea775c0e8e3606aa1ec763f59d190029c8782df75c7950c0bc1836888fc2d -size 50845 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/4f8349df2ca48959fefb7c42b2bc375e_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/56ac11fb9683d7b846fb65c845d80f22_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/59368942873b0c35eef79a7a985025dc_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/59e29b37c5e332b0be088cde8c4d217e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/59e29b37c5e332b0be088cde8c4d217e_img.jpg deleted file mode 100644 index dfc1508aed1ff35b50d6d8983c08e34679ad2865..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/59e29b37c5e332b0be088cde8c4d217e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ef7f7b8330ee2452cc32d770847e4bd466d26cfd320c10e2244abf0ef886118b -size 35756 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/59fcc0e3699f239444841881a2e75da0_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/5ae3023386ee15fae372871afce28865_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/5ec3284657e4df0df3653dd61d0ecd13_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/5ec3284657e4df0df3653dd61d0ecd13_img.jpg deleted file mode 100644 index b74f187f632361e8b234c8d908aa1bbfa5544567..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/5ec3284657e4df0df3653dd61d0ecd13_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:81109948892639b03025f66fe8af1628c189034f363ac1f98fe2dc8c625ee008 -size 36265 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6059b0a3a051cc20b414d51a4e412f3e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6059b0a3a051cc20b414d51a4e412f3e_img.jpg deleted file mode 100644 index c72d45032d205594a1b04407bb6f1a73e475a82b..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6059b0a3a051cc20b414d51a4e412f3e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bf0e82ff89d5c1be58bddeb19c97115d2b9baf9bd35a35f862e5246551b5762d -size 80071 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/60e345365fd1e52e01c91e3fd3cc6515_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/60f844d947ea0bccdd9f64d81d5f8d26_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/60f844d947ea0bccdd9f64d81d5f8d26_img.jpg deleted file mode 100644 index 5a5959d4a46714c87d72000f78605f3561587d7d..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/60f844d947ea0bccdd9f64d81d5f8d26_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b03aec51cf58ec042ea4ae745803eff59823848989b0fd4b4a9803e9f16bb89a -size 78599 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg deleted file mode 100644 index 7ecac0ab406fb718086345ce08bd1df62fdc5f04..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/60ffbad6c0fb7371a57fe8f267d2d141_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f4349aba682253558d6a646a0891d00de05a41b59fdcb0cbd393d2af66fc525f -size 83461 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg deleted file mode 100644 index be832c5ebaabd83408dde9142e6f9c7d2a262b75..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:637a8e7b6f4dbba98312d31a14379abbec6abb19368cf7c6906145920bbf89e7 -size 261426 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/649426750a89fa0e5d7c1736d5cf72c6_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/649426750a89fa0e5d7c1736d5cf72c6_img.jpg deleted file mode 100644 index 6370de61e789a2d5d0963635056aea74afc05cbf..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/649426750a89fa0e5d7c1736d5cf72c6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ffc50a03973f0832bf4b149dd128a10875eb326e0e8269e157986f7b67f1d2c3 -size 72153 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg deleted file mode 100644 index 9a518b1c178f4f666a7755cebdd126f550abaff7..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:736845317ea8e5d9a32a2bae7306cc821fdfb45933e07deda1d5a19a26030d78 -size 105859 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg deleted file mode 100644 index f740f7f0a07a887faedffcee4b9f81081be33950..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/684f7a2cd4ba3346bcaec1f7336f6aa3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f7f32919199e5e673401e059e418df0e9730231eef8e5f4e0603f6ad264530b9 -size 53204 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6a5342571eca4b46338fdfb3c42a8055_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6a9c5a85a12499d60c5a3a75c643b852_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6c8a96787f532bd1fa4719e738cf556f_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/6ff798305e82bdf8233f1381ff9f7c49_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/710ff83dc4a77abbe489fbf1a462845a_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/710ff83dc4a77abbe489fbf1a462845a_img.jpg deleted file mode 100644 index 561cf6aceb5dd55d5202604b1321946a38d735e0..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/710ff83dc4a77abbe489fbf1a462845a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bb025a7dfb12fdd880756562d704424c76d4b78017a7e6b142a06d3686f96334 -size 86823 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/728298e0fbc8de5f3894ce6cb10fb413_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/750b1652a4f4791b84c02aa755a1dedd_img.jpg deleted file mode 100644 index c56ca53ed01561c0a0181cd3ed184f64bafad6ad..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/750b1652a4f4791b84c02aa755a1dedd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:96aa1b4d81225c22328b96d7814770e802afddeb05fcbe7829d9a4ed1fca3c87 -size 63462 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/7c95e83c84169180406fac40d27d6e61_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/7c95e83c84169180406fac40d27d6e61_img.jpg deleted file mode 100644 index 8cc9cced3ba742cf673b756410c5fd66fbf53f5d..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/7c95e83c84169180406fac40d27d6e61_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:11a640d52c3fbca06cdfc56f835759603c6788c622026ac01de90df85e561905 -size 50687 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/7d08458fbe0bd5f306c00c16d68b25f2_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/80a44321a02e8a7d638ac9d53e88772c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/80a44321a02e8a7d638ac9d53e88772c_img.jpg deleted file mode 100644 index d82e4adf02a6a2adacf8bfa43c5a46506de89a9a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/80a44321a02e8a7d638ac9d53e88772c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6295754e3d480cac8a4594197051cc12db59430a90095c88d72f05f5807d6a09 -size 94386 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8159756d3acf4761a73fa0d263f1d338_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8159756d3acf4761a73fa0d263f1d338_img.jpg deleted file mode 100644 index 37c5ea3248ce0b05b1b5e46b0c64480e3b4630e0..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8159756d3acf4761a73fa0d263f1d338_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:67d2432c1a9fc37e1bc589c6154e0805f360fbc7b76f5afd7ed5bce000dd28cc -size 69975 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/81a0abf9a79b27cf9d765553216b173c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/81a0abf9a79b27cf9d765553216b173c_img.jpg deleted file mode 100644 index 31fd2accaeaa71847373d8d13aa5152febbd4c48..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/81a0abf9a79b27cf9d765553216b173c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3333b8df3dc6d935bb1be7e5b2c0115d6978dae6b039e753120535ec0348f9d5 -size 31302 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/81b34087cd6755a80f84a70cf28fba82_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/829cdaf00f7219d70e571064b2b13291_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/834fb96b114b8fdc001625e1ae28e8b1_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/834fb96b114b8fdc001625e1ae28e8b1_img.jpg deleted file mode 100644 index 58c83bce5194417c5029aa5f2c30eeec0298e367..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/834fb96b114b8fdc001625e1ae28e8b1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:47a536749803c7d2c02e90fcf25ce3eacda62b33672f1bfbf4e10f61e20e14f1 -size 138723 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/83ee9f10bd3636e192d68decf7f04cec_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/854df8ad60507803253274673f9062cf_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/89100a6476d1d96f22c192db16502fec_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8b4befaffc5166da571069410e207aea_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8d129c93d18909f0643766f372e9ebf6_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8d138b6bf0be359dc7f079db4899bc41_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8dcca7651accff77ce832523fe2c7e64_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8e0160fd55391f6f2bbdef38ceb6f823_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg deleted file mode 100644 index baf800311baf5ee95fbb413a79450f12a23697ac..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c1c7f7b6ac725f4f0ff9e62078517c240fbb2795d85a3d73543e68a18bc332bf -size 242277 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/90321ffa3cade82e4a57d6250d046c88_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/90321ffa3cade82e4a57d6250d046c88_img.jpg deleted file mode 100644 index c94cc2132dd2f0384ae5222ddd79a6cb5777b5a7..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/90321ffa3cade82e4a57d6250d046c88_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:66656e71f318a8b9cc5185b4d16b45d2d448eaf834fe0d3472f84f0a2e691f6e -size 59806 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9159d999b6514420a64eae80e52f1fd5_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/970a901d8e537da4b6ff719d8931912f_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/990afa9d07fb81cf8760867cb4247a79_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9a2aa33c5d905f8a0646278a48a2e565_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg deleted file mode 100644 index 04f42bfd8e5d5ce6f1d9911fdf620fddea5a0312..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9b39a1d27e49bccd8767e8d5fc0be7fd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:527f7e8ec300dde01b5229f6d8282e1d97bf35d541d7d783abf5d20a99fb9e32 -size 121681 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9b59a11096b85b2bc74c6f653a354e28_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9c7046c19fb32a2d21ac26f5e90a7098_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9cb54072e43a6b6717eb16036a7640a2_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9cb54072e43a6b6717eb16036a7640a2_img.jpg deleted file mode 100644 index e7fcb30b424bb2687371c4e23e6678fabfac2bee..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/9cb54072e43a6b6717eb16036a7640a2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:dce3f81b542b56a15e601846724aff8112f46133aae2f4ef7778fd3901c32761 -size 68394 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg deleted file mode 100644 index ec05b22ff831fcb7b8024daffd21674492988a53..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/a0eb8d30ac11ba97b2733c187b89ff22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:84b4dd0e4e1f892fa528a87bca68cc1e1f0ff7519ce355fb58dd385448631286 -size 39662 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/a28ab03366399b5e0a61445bc57e3724_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/a4c80b98452e7949d9f8d969dc9cebf7_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/a4c80b98452e7949d9f8d969dc9cebf7_img.jpg deleted file mode 100644 index 66deec179ab55b4031ceb21daef270fcaaba5a72..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/a4c80b98452e7949d9f8d969dc9cebf7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8a857955f0af7639f968e63a80426ed84788e48d349e2e942f9a8f463ee9ba96 -size 113243 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/aa05feb33e250a75136ea52816d3c19a_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/af90aabfe3c8c65617da060d82bf99c5_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/af90aabfe3c8c65617da060d82bf99c5_img.jpg deleted file mode 100644 index 2337d016b529796c8abe2734beea892a184809fe..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/af90aabfe3c8c65617da060d82bf99c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b3b129e2d2185c2c94a9ff5ad9998024d6a1f20c84c669e7795c0e0283d51360 -size 44567 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/b02ba0b73e95416eb547976f6145b169_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/b02ba0b73e95416eb547976f6145b169_img.jpg deleted file mode 100644 index 894d13df7914c69a19ef3b967f4a4aff87c83398..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/b02ba0b73e95416eb547976f6145b169_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:88525e943e407c0910fe356701a1fff8f6c5ed9cbd0c6352afe43855619b83e1 -size 70591 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg deleted file mode 100644 index 544c5d6419266e90584d4d109fc52266f373db45..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1f357a4b3d11003875cd898c23090cce0a63c836ade42898b0b8fe974ee7561a -size 79835 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/b3d488012fdceacab867cf24c5efef05_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/b3d488012fdceacab867cf24c5efef05_img.jpg deleted file mode 100644 index 0a472800097cba82e6384d8ac939c3fd7e264f55..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/b3d488012fdceacab867cf24c5efef05_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f2c6b66a0b3098379158bf0c3e7e3d0e431f40868a9eaabeacb949b1d8c7279b -size 41311 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/b54b769d67164910c7c5b2a0ea74257b_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/b54b769d67164910c7c5b2a0ea74257b_img.jpg deleted file mode 100644 index 97874543d9477ea05e6dd5cb9092f4b33fc98a56..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/b54b769d67164910c7c5b2a0ea74257b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7888c013eb6e87cde548572b2ae5fdb114838bb9297cf276d916ef5b899510f8 -size 74602 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/be8d4d130f4e1f103926de61c4bfc23c_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/c0ca823603794512478906b302176bca_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/c0ca823603794512478906b302176bca_img.jpg deleted file mode 100644 index 092e414d1c7af1abb796f2aae4287fd04310a78f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/c0ca823603794512478906b302176bca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:dc3d5d833712dc658ecc5b1507592adb3c6000ab99a2f36e4a44aa60e6f8569a -size 49263 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/c389468860cd886ab9c732473e959f0f_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/c4315e81a5a818379fcf31519a9c2cbe_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/c521036a3eb59673388f5e034f4e6c9f_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/cc91bf9aed46f8b219ebceaee276d195_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/cc91bf9aed46f8b219ebceaee276d195_img.jpg deleted file mode 100644 index fbb05c0712134bc93c0085b4bb1ba380392027a5..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/cc91bf9aed46f8b219ebceaee276d195_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6560a8f3187fa54fc87fae6ab1b05940bcdfa66e7a584a9d68a6ab83b6f846ca -size 66354 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/cf03eff1218a8cc1be6b05de892162de_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/cf03eff1218a8cc1be6b05de892162de_img.jpg deleted file mode 100644 index e47380c8dc89997b78b0c3ed36ee1f06fb0eeca4..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/cf03eff1218a8cc1be6b05de892162de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a44204bc6db24ce2ff7565bf70f64ae4a23290163f2bd455c1d921aeee8051e2 -size 81037 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d04c50badc78d5ba47bf4e352af4a754_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d04c50badc78d5ba47bf4e352af4a754_img.jpg deleted file mode 100644 index bdbe8e72738403d3fe33035f56d3bcdaa37af6a2..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d04c50badc78d5ba47bf4e352af4a754_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d01974096084ac00d4fb3288a7813b12a69daa0516c08e6e1e484e2b6917705e -size 63204 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d1ec9820fe8d23d83e066389a9cd7338_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg deleted file mode 100644 index 2d237181b67d6c3c5880c84a86dddd77d7e88d22..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d22fb161d760fcf9fe3fb7b36f81c6fb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:296f33a9a5fd06d73768aa9883e8bc9e2cc0ae89ef0243c438d8d8020ad869b7 -size 70537 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d2c29dfabebacb6f853683a6c3759320_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d7896dd2d38adf224c3b76cd22d29c10_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d7896dd2d38adf224c3b76cd22d29c10_img.jpg deleted file mode 100644 index 2d82654d6d51056c0cddff423af92c9aa88f62db..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d7896dd2d38adf224c3b76cd22d29c10_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:367f122c4a2b164d9cba733a2066f0b863b5e5e3afd0ddfdab5e4322f4888549 -size 81220 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d79de2dd022d74722a84f1b2ffce691c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d79de2dd022d74722a84f1b2ffce691c_img.jpg deleted file mode 100644 index fcebfd45d087e626ededb6c9f56a6083d766215c..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d79de2dd022d74722a84f1b2ffce691c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:73f124dafe60650c9bffa708d040a142b6c5c13fcc38db33069f6ffd0d18dcb2 -size 123112 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d90d939bcbf43d474efaeeaa335a635c_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/d90f17b29a73eddf151f51effa8912e0_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/da74b0e807fd62f32abdc3c05ffbabf4_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/da8cb3d696f15f2c6de7aff6955d12d3_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/dbd4bab54b57e8d1abf80e3de6471130_img.jpg deleted file mode 100644 index 9f35fb75cf7ba8c8daf488149b2800d47197949f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/dbd4bab54b57e8d1abf80e3de6471130_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:182ee5c8d491f75414985cd39b0f7529f3dea08429ee58ac0275b23238c76425 -size 214071 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index 9a863b394765b18d479d501944f60c148027a95d..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:aeebb8bde371d400db3d90b60ee5b95ef05ccfec1bc00f59e115f62d9778d3fb -size 4523 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/df495bddeb5d8826c7571714e6db1478_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e010d665d27407ff5e238d1c45c1c98f_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e16bfa31d748f4d99ec4ae3d16656926_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e16bfa31d748f4d99ec4ae3d16656926_img.jpg deleted file mode 100644 index 53641711d40a09bee07cd8127d5d642f245b40e5..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e16bfa31d748f4d99ec4ae3d16656926_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fa2d36dd75ef6ae2923ebff68977dc13fa5052e50f4fb9602184625c243d2327 -size 47196 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e1d97826df530020bf86c791d8c7d724_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e2245b4865907ad1259fd155f4beb6cf_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e2245b4865907ad1259fd155f4beb6cf_img.jpg deleted file mode 100644 index 603effb71e76f579cf4bb6399177c83ad122de12..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e2245b4865907ad1259fd155f4beb6cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c55ee1f6a0e1c5e1cc4e231da88917a0e3381a7ee79bd5297de30833d181981 -size 79001 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e2c120be98ede6deb60dd341f5a9803b_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e2c120be98ede6deb60dd341f5a9803b_img.jpg deleted file mode 100644 index a7defbeede966b524780d6456d0c114c56ba5848..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e2c120be98ede6deb60dd341f5a9803b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0c36968ba11aea215b6b1fa39f2cf4bfedf46f470b0bb2177f43a48d427c54ea -size 198879 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e374c531ea6c45899ce8ec331e437bd1_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e5eedb1e90a22814f090917b3411be8f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e5eedb1e90a22814f090917b3411be8f_img.jpg deleted file mode 100644 index 282525d123539a59c131efaa73406c24f2555af2..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e5eedb1e90a22814f090917b3411be8f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:82e81496a6e4a10023cf5810119c6ba27389de0698ef6356210ab1dda5a27539 -size 80401 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e87df69ebd4cd2dbbf6749079e6c057a_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg deleted file mode 100644 index 48f301b0df8f3d6eb027f2057d77227b81b6a66f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:84cff0972e87151af62f0297f4ce969dc930c8a59c6fc05f12171b7822f983cb -size 58540 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/ecae674475cecdd0962200a5d1e2591e_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/ecae674475cecdd0962200a5d1e2591e_img.jpg deleted file mode 100644 index 76d24892cd90551c6b57917051e8bcd5204536f0..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/ecae674475cecdd0962200a5d1e2591e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:28737ca4f3978aa57724346e668d28639ee651673fd9ee63b21aa4ffd66d04ec -size 96187 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/f250ba4162fe40d8ddfd05b74fa48895_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg deleted file mode 100644 index 3bc7265f7439ec6414103c45727ea07d79284f3c..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:74af9cc6390aa542c32607666bcc6551e9d10c75e1ba77175100ba7efe475b74 -size 73698 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/f74adaa1840504407cd4272995426f82_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/f7dbd497160f02888f34fdf243648aa2_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg deleted file mode 100644 index eeb90d11332150e603f7170b7c35c3674a6c64e6..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c548e8ae82657c02e0ca92af5835f7b3e5dcfeeb1911f4db065adc43cd412be7 -size 95064 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/facce731b2dbfae43a8609231a700be1_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/facce731b2dbfae43a8609231a700be1_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/facce731b2dbfae43a8609231a700be1_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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/fc3e2b49a9f850951570e502393b697f_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/fc3e2b49a9f850951570e502393b697f_img.jpg deleted file mode 100644 index c3ac3c38c702a6b8eb8fbfbe91e2957eda5ec8b9..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/fc3e2b49a9f850951570e502393b697f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:46e059e86093eee2e96e34285ee8e44304271d9b8079ebe4400d3028b998c456 -size 43801 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.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/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg deleted file mode 100644 index bbf279f896165174b6699c80f8bb264a34a53f3c..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:806cb86c75dd1f708c0605ccf7b4d9d46fcbb31bca8f244309662e754f303bcd -size 209208 diff --git a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/ffe0fef452a0ae9a20253c319c54e13c_img.jpg deleted file mode 100644 index ce53043dcf7a0255b89a53d7139d5ca5aeb96f65..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.RICARCH-R005-v08.00/images/ffe0fef452a0ae9a20253c319c54e13c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c4b1068ac2a1c1f3c2b2580fdccf745d499c6afc53108be42d370737f2916ba -size 52644 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/doc.md b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/doc.md deleted file mode 100644 index ac86e20d11355c0998fddf1959a69da69ea8ee68..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/doc.md +++ /dev/null @@ -1,4743 +0,0 @@ - - -# --- **O-RAN Work Group 3 (Near-Real-time RAN Intelligent Controller)** - -# **Use Cases and Requirements** - -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.....8 - -3.3 Abbreviations .....9 - -4 Use cases .....9 - -4.1 Traffic steering .....9 - -4.1.1 Background and goal of the use case .....9 - -4.1.2 Entities/resources involved in the use case .....9 - -4.1.3 Solutions .....10 - -4.1.4 Required data .....15 - -4.2 QoS based resource optimization .....17 - -4.2.1 Background and goal of the use case .....17 - -4.2.2 Entities/resources involved in the use case .....17 - -4.2.3 Solutions .....18 - -4.2.4 Required data .....20 - -4.3 RAN slice SLA assurance .....24 - -4.3.1 Background and goal of the use case .....24 - -4.3.2 Entities/resources involved in the use case .....26 - -4.3.3 Solutions .....27 - -4.3.4 Required data .....29 - -4.4 Massive MIMO optimization .....32 - -4.4.1 Background and goal of the use case .....32 - -4.4.2 Entities/resources involved in the use case .....32 - -4.4.3 Solutions .....33 - -4.4.4 Required data .....57 - -4.5 QoE optimization .....65 - -4.5.1 Background and goal of the use case .....65 - -4.5.2 Entities/resources involved in the use case .....65 - -4.5.3 Solutions .....65 - -4.5.4 Required data .....69 - -4.5.5 RAN analytics information exposed by Near-RT RIC .....72 - -4.6 Network energy saving.....73 - -4.6.1 Carrier and cell switch off/on .....74 - -4.6.2 Advanced sleep mode .....79 - -4.6.3 RF channel reconfiguration.....85 - -4.6.4 PRB blanking optimization.....89 - -4.6.5 Deep hibernate .....94 - -4.6.6 Spatial and power domain.....100 - -4.6.7 SSB-less SCell optimization .....105 - -4.6.8 PA power optimization .....109 - -4.7 Interference detection and optimization .....113 - -4.7.1 Background and goal of the use case .....115 - -4.7.2 Entities/resources involved in the use case .....116 - -4.7.3 Solution.....116 - -4.7.4 Required data .....118 - -| | | | -|------------------------|-----------------------------------------------------------|-----| -| 5 | Requirements..... | 121 | -| 5.1 | Functional requirements ..... | 121 | -| 5.1.1 | Near-RT RIC generic functional requirements ..... | 121 | -| 5.1.2 | E2 interface functional requirements ..... | 122 | -| 5.1.3 | RAI exposure interface functional requirements ..... | 131 | -| 5.2 | Non-functional requirements..... | 132 | -| 5.2.1 | Near-RT RIC non-functional requirements ..... | 132 | -| 5.2.2 | E2 interface non-functional requirements..... | 132 | -| Annex A (informative): | Example use cases ..... | 133 | -| A.1 | Example use cases for RAN slice SLA assurance..... | 133 | -| A.1.1 | Downlink and uplink throughput per slice..... | 133 | -| A.1.2 | Guaranteed downlink and uplink throughput per slice ..... | 134 | -| Annex (informative): | Change history/Change request (history) ..... | 135 | - -# --- Foreword - -This Technical Specification (TS) has been produced by WG3 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 WG3 Near-RT RIC Use Cases and Requirements, including E2 interface. - -# --- 1 Scope - -The present document specifies the initial use cases that have been approved within O-RAN WG3. The purpose of the use cases is to help identify requirements for O-RAN defined interfaces and functions, specifically Near-RT RIC functions and E2 interface, eventually leading to formal drafting of interface specifications. For each use case, the document describes the motivation, resources, steps involved, and data requirements. Finally, the requirements clause details the functional and non-functional requirements derived from these use cases. - -# --- 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”, Release 16, October 2020 -- [2] 3GPP TS 23.203: “Policy and Charging Control Architecture”, Release 16, December 2019 -- [3] 3GPP TS 23.501: “System Architecture for the 5G System (5GS)”, Release 16, September 2020 -- [4] 3GPP TS 28.530: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; Concepts, use cases and requirements”, Release 16, December 2020 -- [5] 3GPP TS 28.541: “Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3”, Release 16, November 2020 -- [6] 3GPP TS 28.552: “Technical Specification Group Services and System Aspects; Management and orchestration; 5G performance measurements”, Release 16, September 2020 -- [7] 3GPP TS 32.425: “Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Release 16, January 2020 -- [8] 3GPP TS 36.300: “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2”, Release 16, October 2020 -- [9] 3GPP TS 36.314: “Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 – Measurements”, Release 16, July 2020 -- [10] 3GPP TS 36.321: “Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification”, Release 16, October 2020 -- [11] 3GPP TS 36.331: “Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification”, Release 16, October 2020 -- [12] 3GPP TS 36.423: “Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP)”, Release 16, October 2020 -- [13] 3GPP TS 37.340: “NR; Multi-connectivity; Overall description; Stage-2”, Release 16, October 2020 -- [14] 3GPP TS 38.300: “NR and NG-RAN Overall Description”, Release 16, October 2020 -- [15] 3GPP TS 38.214: “NR; Physical Layer Procedures for Data”, Release 16, October 2020 -- [16] 3GPP TS 38.314: “NR; Layer 2 measurements”, Release 16, October 2020 - -- [17] 3GPP TS 38.321: “NR; Medium Access Control (MAC) protocol specification”, Release 16, October 2020 -- [18] 3GPP TS 38.331: “NR; Radio Resource Control (RRC); Protocol specification”, Release 18, October 2025 -- [19] 3GPP TS 38.423: “NG-RAN; Xn Application Protocol (XnAP)”, Release 16, October 2020 -- [20] 3GPP TS 38.463: “NG-RAN; E1 Application Protocol (E1AP)”, Release 16, October 2020 -- [21] 3GPP TS 38.473: “NG-RAN; F1 Application Protocol (F1AP)”, Release 16, October 2020 -- [22] GSMA: “Generic Network Slice Template Version 4.0”, November 2020 -- [23] Void -- [24] O-RAN.WG2.A1AP: “O-RAN Working Group 2, O-RAN A1 interface: Application Protocol” -- [25] O-RAN.WG3.E2SM-v02.00: “O-RAN Working Group 3, Near-Real-time RAN Intelligent Controller, E2 Service Model (E2SM)” -- [26] 3GPP TS 38.133: “NR; Requirements for support of radio resource management”, Release 16, April 2022 -- [27] 3GPP TS 38.215: “NR; Physical layer measurements”, Release 16, April 2022 -- [28] O-RAN.WG2.Use-Case-Requirements-R004-v10.00: “O-RAN Working Group 2, Non-RT RIC & A1/R1 interface: Use Cases and Requirements” -- [29] O-RAN.WG2.AIML: “O-RAN Working Group 2, AI/ML workflow description and requirements” -- [30] O-RAN.WG1.O-RAN-Architecture-Description-v06.00: “O-RAN Architecture Description” -- [31] 3GPP TS 23.501: “System architecture for the 5G System (5GS); Stage 2”, Release 17, March 2021 -- [32] O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R004-v15.00: “O-RAN Work Group 1 (Use Cases and Overall Architecture), Use Cases Detailed Specification” -- [33] 3GPP TS 28.310: “Management and orchestration; Energy efficiency of 5G”, Release 18, March 2023 -- [34] O-RAN.WG4.CUS.0-R003-v15: “O-RAN Working Group 4, Control, User and Synchronization Plane Specification” -- [35] O-RAN.WG4.MP.0-R003-v15: “O-RAN Working Group 4, Management Plane Specification” -- [36] O-RAN WG3 E2SM-KPM: “O-RAN Work Group 3, Near-Real-time RAN Intelligent Controller, E2 Service Model (E2SM), KPM” -- [37] O-RAN WG3 E2SM-RC: “O-RAN Work Group 3 (WG-3), Near-Real-time RAN Intelligent Controller, E2 Service Model (E2SM), RAN Control” -- [38] Void -- [39] O-RAN.WG4.MP.0-R004-v17.01: “O-RAN Working Group 4, Management Plane Specification” -- [40] 3GPP TS 38.323: “NR; Packet Data Convergence Protocol (PDCP) specification”, Release 17.5, July 2023 -- [41] 3GPP TS 25.321: “Universal Mobile Telecommunications System (UMTS); Medium Access Control (MAC) protocol specification”, Release 17, May 2022 -- [42] O-RAN.WG3.E2SM-RC-R003-v05.00: “O-RAN Work Group 3 (WG-3), Near-Real-time RAN Intelligent Controller, E2 Service Model (E2SM), RAN Control” -- [43] 3GPP TS 38.212: “5G; NR; Multiplexing and channel coding”, Release 16.8.0, January 2022 -- [44] 3GPP TS 28.554: “5G; Management and orchestration; 5G end to end Key Performance Indicators (KPI)”, Release 16, January 2021 -- [45] 3GPP TS 38.211: “5G; NR; Physical channels and modulation”, Release 16, July 2020 -- [46] 3GPP TS 38.912: “5G; Study on New Radio (NR) access technology”, Release 16, July 2020 -- [47] 3GPP TS 38.913: “5G; Study on scenarios and requirements for next generation access technologies”, Release 16, July 2020 -- [48] ORAN-WG10.O1-Interface-v08: “O-RAN Working Group 10, Operations and Maintenance Interface Specification”, July 2022 -- [49] O-RAN.WG1.TS.Use-Cases-Detailed-Specification-R004-v16.00: “O-RAN Work Group 1 (Use Cases and Overall Architecture), Use Cases Detailed Specification” -- [50] O-RAN.WG3.TS.E2SM-CCC-R004: “O-RAN Work Group 3 (WG-3), Near-Real-time RAN Intelligent Controller and E2 interface, E2 Service Model (E2SM) Cell Configuration and Control” - -## 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] O-RAN.WG1.mMIMO-Use-Cases-TR-v01.00: "O-RAN Working Group 1, Massive MIMO Use Cases Technical Report" -- [i.3] 3GPP TR 23.700-40: “Study on enhancement of network slicing; Phase 2”, March 2021 -- [i.4] ORAN-WG1.Use Cases Energy Saving Technical Report R003 v02.00: “O-RAN Work Group 1 (Use Cases and Overall Architecture), Network Energy Saving Use Cases Technical Report” -- [i.5] 3GPP TR 28.813: “Study on new aspects of Energy Efficiency (EE) for 5G”, Release 17, December 2021 -- [i.6] O-RAN.WG1.TR.Use-Cases-Analysis-Report-R004-v16.00: “O-RAN Work Group 1 (Use Cases and Overall Architecture), Use Cases Analysis Report” - -# --- 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the terms and definitions [given in 3GPP TR 21.905 [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 3GPP TR 21.905 [i.1]. - -**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. - -**A1-policy based traffic steering process mode:** An operational mode in which the Near-RT RIC is configured through A1 policy to use traffic steering actions to ensure a more specific notion of network performance (for example, applying to smaller groups of E2 nodes and UEs in the RAN) than that which it ensures in the background traffic steering. - -**Background traffic steering processing mode:** An operational mode in which the Near-RT RIC is configured through O1 to use traffic steering actions to ensure a general background network performance which applies broadly across E2 nodes and UEs in the RAN. - -**Baseline RAN behavior:** The default RAN behavior as configured at the E2 nodes by SMO. - -**E2:** Interface connecting the Near-RT RIC and one or more O-CU-CPs, one or more O-CU-UPs, one or more O-DUs, and one or more O-eNBs. - -**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. - -**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. - -**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 (e.g., UE basis, cell basis) data collection and actions over E2 interface. - -**O-CU** (O-RAN Central Unit): A logical node hosting RRC, SDAP and PDCP protocols. - -**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-eNB** (O-RAN eNB): An eNB or ng-eNB that supports E2 interface. - -**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 orchestration & management entities (orchestration/NMS) and O-RAN managed elements, for operation and management, by which FCAPS management, software management, file management and other similar functions can be achieved. - -**RAN UE group:** Aggregations of UEs whose grouping is set in the E2 nodes through E2 procedures also based on the scope of A1 policies. These groups can then be the target of E2 CONTROL or POLICY messages. - -**Traffic steering action:** The use of a mechanism to alter RAN behavior. Such actions include E2 procedures such as CONTROL and POLICY. - -**Traffic steering inner loop:** The part of the traffic steering processing, triggered by the arrival of periodic TS related KPM (Key Performance Measurement) from E2 node, which includes UE grouping, setting additional data collection from the RAN, as well as selection and execution of one or more optimization actions to enforce traffic steering policies. - -**Traffic steering outer loop:** The part of the traffic steering processing, triggered by the Near-RT RIC setting up or updating traffic steering aware resource optimization procedure based on information from A1 policy setup or update, A1 Enrichment Information (EI) and/or outcome of Near-RT RIC evaluation, which includes the initial configuration (preconditions) and injection of related A1 policies, triggering conditions for TS changes. - -**Traffic steering processing mode:** An operational mode in which either the RAN or the Near-RT RIC is configured to ensure a particular network performance. This performance includes such aspects as cell load and throughput, and it can apply differently to different E2 nodes and UEs. Throughout this process, traffic steering actions are used to fulfill the requirements of this configuration. - -**Traffic steering target:** The intended performance result that is desired from the network, which is configured to Near-RT RIC over O1. - -## 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. 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]. - -| | | -|-------|--------------------------------------| -| KPI | Key Performance Indicator | -| KQI | Key Quality Indicator | -| MBB | Mobile BroadBand | -| PA | Power Amplifier | -| SCell | Secondary Cell | -| SMG | Spatial Multiplexing Group | -| SMO | Service Management and Orchestration | -| SSB | Synchronization Signal Block | - -# --- 4 Use cases - -## 4.1 Traffic steering - -This use case provides the motivation, description, and requirements for Near-RT RIC and E2 interface to support traffic steering, whose end-to-end requirements are specified in [32]. - -### 4.1.1 Background and goal of the use case - -The rapid traffic growth and multiple frequency bands utilized in a commercial network make it challenging to steer the traffic in a balanced distribution. Typical controls are limited to adjusting the cell reselection and handover parameters; and modifying load calculations and cell priorities. - -The goal of Near-RT RIC traffic steering is to interpret the policies received over A1 and to determine the optimum changes it can make towards achieving those goals. It may also leverage the A1 enrichment information. Traffic steering may reuse mechanisms provided by other use cases to effect the changes necessary to achieve its goals. - -More specifically, Near-RT RIC triggers E2 procedure and related control/policies so as to obtain network performance that would fulfill the criteria identified in the A1 policies. - -### 4.1.2 Entities/resources involved in the use case - -- 1) OAM functions in SMO domain: - - Collect necessary measurement metrics from network level measurement report and enrichment data (can acquire data from application) for constructing/training relevant AI/ML models. - - Deploy or update, configure the relevant TS optimization AI/ML models to Near-RT RIC via O1. -- 2) Non-RT RIC in SMO domain: - - Send A1 policies and receive policy feedback to/from Near-RT RIC to drive resource optimization at RAN level. - - E.g., TS targets as specified in O-RAN.WG2.A1AP [24]. - -#### 3) Near-RT RIC: - -- Supports update of AI/ML models from SMO. -- Supports inference, such as traffic prediction, using AI/ML models from Non-RT RIC based on network data, e.g., measurement reports from E2 node. -- Supports interpretation and execution of A1 policies from Non-RT RIC. -- Sends TS resource optimization related policies and commands to E2 node to influence RRM behavior. -- Sends the relevant A1 policy feedback to Non-RT RIC for potential policy update. -- Sends the relevant O1 performance data to OAM functions; these can be used by Non-RT RIC for potential policy update. - -#### 4) E2 node: - -- Supports reporting of UE context, network measurements, and UE measurements to Near-RT RIC over E2 interface. -- Executes policies and commands received from Near-RT RIC over E2 interface. -- Supports network and UE performance report to OAM functions in SMO domain over O1 interface. - -### 4.1.3 Solutions - -In this clause the possible processing modes of traffic steering are described. Three general traffic steering processing modes and the transitions between them are shown in figure 4.1.3-1. - -These modes represent the way the Near-RT RIC (or RAN) operates on a given group of UEs, and not the operation of any component as a whole. As such, the Near-RT RIC, could be operating in both modes 1 and 2 concurrently for different sets of UEs. For example, the transition from mode 0 or 1 to 2 occurs only for a group of UE defined by the A1 policy scope. At the same time, other UE groups may still be handled in mode 0 and/or 1. - -![Diagram showing three traffic steering processing modes: TS Mode 0 (Baseline), TS Mode 1 (Background Near-RT RIC Processing), and TS Mode 2 (A1 Policy based Near-RT RIC Processing). Transitions are triggered by O1 configuration from SMO, O1 configuration removal, A1-P Create Policy from Non-RT RIC, and A1-P Delete Policy.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) - -``` - -graph TD - Mode0[TS Mode 0: Baseline] - Mode1[TS Mode 1: Background Near-RT RIC Processing] - Mode2[TS Mode 2: A1 Policy based Near-RT RIC Processing] - - Mode0 -- "O1 configuration from SMO" --> Mode1 - Mode1 -- "O1 configuration removal" --> Mode0 - Mode0 -- "A1-P Create Policy from Non-RT RIC" --> Mode2 - Mode2 -- "A1-P Delete Policy" --> Mode0 - Mode1 -- "A1-P Delete Policy" --> Mode2 - Mode2 -- "A1-P Create Policy from Non-RT RIC" --> Mode1 - -``` - -Diagram showing three traffic steering processing modes: TS Mode 0 (Baseline), TS Mode 1 (Background Near-RT RIC Processing), and TS Mode 2 (A1 Policy based Near-RT RIC Processing). Transitions are triggered by O1 configuration from SMO, O1 configuration removal, A1-P Create Policy from Non-RT RIC, and A1-P Delete Policy. - -Figure 4.1.3-1: Traffic steering processing modes - -The three processing modes are described in more detail below: - -0. “Baseline” traffic steering behavior: OAM functions in SMO domain uses O1 configuration on one or more E2 node to set up a desired baseline behavior. This also sets up baseline performance monitoring of E2 node by the SMO. In this mode, Near-RT RIC is not involved. -1. “Background” Near-RT RIC processing: OAM functions in SMO domain uses O1 configuration of Near-RT RIC to set up a desired “background Near-RT RIC behavior”. In this mode the Near-RT RIC sets up E2 mechanisms to monitor E2 node and uses traffic steering related E2 mechanisms to achieve the desired background behavior of the set of E2 nodes connected to the Near-RT RIC. -2. “A1-policy based” Near-RT RIC processing: This mode can be entered from either mode 0 or mode 1. Non-RT RIC in SMO domain uses A1-P to specify an A1 guided behavior for a targeted subset of E2 nodes or UEs. If entering this from mode 1, this will have the effect of modifying the existing Near-RT RIC “background” behavior to include a more specific A1 guided behavior. In this mode, the Near-RT RIC can either set up or modify E2 mechanisms used to monitor E2 nodes and will use traffic steering related E2 mechanisms to obtain the desired behavior of some targeted sub-set of E2 nodes or UEs. This mode terminates when the corresponding A1-P policy delete message is received from Non-RT RIC in SMO domain and the system returns to either mode 0 or mode 1, depending on whether or not OAM functions in SMO domain had previously configured the optional Near-RT RIC “background” role (mode 1). - -NOTE: Processing mode 0 is strictly not in scope for WG3. It is described here for completeness and to clearly state what is the starting point prior to the WG2 and WG3 defined mechanisms. - -Processing mode 2 contain an ‘outer loop’ and an ‘inner loop’. In the inner loop, a number of different “E2 mechanism” can be used (policy, report/control or insert/control) towards a number of different target RAN functions in order to either exercise existing RAN mechanisms or modifying their ongoing behavior. The appropriate mechanism and target RAN function would depend upon the RAN function capabilities to support a given E2 mechanism, the A1-P scope and policy, the O1 configuration of the RIC and the performance observed through E2 monitoring. - -#### 4.1.3.1 Near-RT RIC A1-policy based traffic steering - -The context of Near-RT RIC A1-policy based traffic steering is captured in table 4.1.3.1-1. - -**Table 4.1.3.1-1: Near-RT RIC A1-policy based traffic steering** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Drive traffic management in RAN in accordance with defined intents, policies, and enrichment information from the Non-RT RIC using A1 interface. | | -| Actors and Roles |
  • - OAM functions in SMO domain: Performance data and training data collection, AI model management.
  • - Non-RT RIC in SMO domain: Creates and updates A1 policies, AI model training targeting to TS optimization.
  • - Near-RT RIC: Enforces A1 policies and generates RIC CONTROL and/or POLICY.
  • - E2 node: RIC CONTROL and POLICY execution and RIC REPORT creation.

Refer to 4.1.2 for more details.

| | -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - A1, O1 and E2 interface connectivity is established.
  • - A1 policy scope defined.
| | -| Pre-conditions |
  • - Network is operational with default configuration.
  • - OAM functions have configured a baseline measurement configuration and the Non-RT RIC has access to this data.
  • - (optional) OAM functions have configured traffic steering targets in Near-RT RIC through O1 interface.
  • - OAM functions have configured baseline traffic steering parameters in E2 node(s) through O1 interface.
| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| |
  • - (optional) Near-RT RIC has access to the necessary data related to traffic steering from the E2 node by means of a RIC report procedure.
  • - Non-RT RIC analyzes the historical data from RAN 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 non-real-time optimization of configuration and policies.
| | -| Begins when | Non-RT RIC and/or Near-RT RIC perform data evaluation, determine that TS-aware optimization is required to be initiated or updated and establishes target(s). | | -| Step 1 (O) | (Start of outer loop control)
Non-RT RIC evaluates the collected data and A1 policy feedback, if required, and generates or updates the appropriate TS-aware resource optimization policy, such as TS targets, and sends it to Near-RT RIC via A1 interface. | | -| Step 2 (O) | Non-RT RIC sends optional traffic steering related A1 enrichment information. | | -| Step 3 (M) | Based on received A1 policy and/or A1-EI from Non-RT RIC or internal trigger and/or internal evaluation and trigger, Near-RT RIC sets up or updates the TS-aware resource optimization procedure. | | -| Step 4 (M) | Near-RT RIC subscribes to a UE context information and measurement metrics via E2 interface. | | -| Step 5 (M) | (Start of inner loop control)
E2 nodes report the UE context information and E2 measurements via RIC REPORT periodically or event-triggered. | | -| Step 6 (M) | Near-RT RIC evaluates the performance data from E2 nodes (including performance data from different E2 nodes for the same UE) and finds the performance is out of TS targets which are indicated in the A1 policy and/or internal Near-RT RIC TS targets. | | -| Step 7 (M) | Based on the UE context information, E2 measurement metrics (RIC REPORT), and A1 policy, Near-RT RIC may generate new or modify the existing E2 policies and sends them to E2 nodes. Near-RT RIC may also generate control command(s) and send them to E2 node(s) to trigger re-allocation of radio resources so that TS indicators can move back to the limits outlined in the A1 policies.

E2 node functions target of E2 policy and control commands may be:
  • - E-UTRAN-NR dual connectivity
  • - Carrier aggregation
  • - Connected mode mobility
  • - Idle mode mobility
Step 4 to Step 7 may repeat. (End of inner loop control) | | -| Step 8 (O) | If required, Near-RT RIC sends information to the SMO domain using A1 policy feedback and/or O1-PM. The Non-RT RIC may use this information and information collected from E2 nodes using O1-PM as policy feedback to assess the performance of TS optimization function in Near-RT RIC, or to assess the outcome of the applied A1 policies. Subsequently, an A1 policy can be updated.

In parallel, the Near-RT RIC may use available information to assess the performance of TS optimization function in Near-RT RIC, and/or to assess the outcome of the applied A1 policies. Subsequently, Near-RT RIC TS optimization targets can be updated

Step 1 to Step 8 may repeat (End of outer loop control) | | -| Ends when | Non-RT RIC decides to delete TS-aware resource optimization policy and sends the related message or following internal trigger, the Near-RT RIC terminates the TS-aware resource optimization procedure. | | -| Exceptions | None. | | -| Post Conditions | Non-RT RIC continues to collect and monitor TS related measurement data from E2 node.
Near-RT RIC continues to collect and monitor TS related measurement data from E2 node. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Traceability | REQ-Near-RT-RIC-TS-FUN1, REQ-Near-RT-RIC-TS-FUN2, REQ-E2-TS-FUN1, REQ-E2-TS-FUN2, REQ-E2-TS-FUN3, REQ-E2-TS-FUN4, REQ-E2-TS-FUN5, REQ-E2-TS-FUN6, REQ-E2-TS-FUN7, REQ-E2-TS-FUN8, REQ-E2-TS-FUN9, REQ-E2-TS-FUN10 | | - -``` - -@startuml -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Box "Service Management and Orchestration" #gold - Participant OAM as "OAM Functions" - Participant non as "Non-RT RIC" -End box - -Box "O-RAN" #lightpink - Participant near as "Near-RT RIC" - Participant ran as "E2 Node" -End box - -OAM <-> ran : <> RAN Data & Configuration collection -near <-> ran : <> RAN Data & Configuration collection -OAM -> non: TS Performance information -non-->non: (Mode 2) Collected Data Evaluation TS target generation -near-->near: (Mode 1) Collected Data Evaluation TS target generation - -group OUTER LOOP CONTROL - non --> near : 1:(opt.) <> A1 policy setup or update - non --> near : 2: (opt.) <> Traffic steering related A1 Enrichment Information - near -> near : 3: TS optimization set-up or update - near -> ran : 4: <> RIC SUBSCRIPTION REQUEST(UE context & Measurement Metrics) - - group INNER LOOP CONTROL - ran -> near : 5: <> RIC INDICATION (UE context & E2 measurement metrics) - near -> near : 6: TS performance does not fulfill A1 policy requirements - near --> ran : 7: (opt.) <> RIC SUBSCRIPTION REQUEST(REPORT or INSERT [UE measurements & E2-node state]) - near <-- ran : (opt.) <> RIC INDICATION - near --> ran : (opt.) <> RIC CONTROL REQUEST(TS optimization control parameters) - near --> ran : (opt.) <> (opt.) RIC SUBSCRIPTION REQUEST(TS optimization POLICY) - end - - OAM <-- near : (opt.) <> TS Performance information - OAM -> non : TS Performance information - non <-- near : (opt.) <> TS Performance information - non -> non : TS Optimization Performance Evaluation - near -> near : TS Optimization Performance Evaluation -end - -non --> near : (opt.) <> A1 policy delete -near -> near : TS optimization stopped -near-> ran : <> RIC SUBSCRIPTION DELETE -@enduml - -``` - -The overall procedure for Near-RT RIC A1-policy based traffic steering use case is given in figure 4.1.3.1-1. - -![Sequence diagram showing the overall procedure for Near-RT RIC A1-policy based traffic steering use case. The diagram is divided into three main sections: Service Management and Orchestration (yellow), OUTER LOOP CONTROL (white), and INNER LOOP CONTROL (white). Lifelines include OAM Functions, Non-RT RIC, Near-RT RIC, and E2 Node. The process involves RAN data collection, TS target generation (Mode 1 and Mode 2), policy setup, traffic steering enrichment, TS optimization, and performance evaluation loops.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) - -Sequence diagram showing the overall procedure for Near-RT RIC A1-policy based traffic steering use case. The diagram is divided into three main sections: Service Management and Orchestration (yellow), OUTER LOOP CONTROL (white), and INNER LOOP CONTROL (white). Lifelines include OAM Functions, Non-RT RIC, Near-RT RIC, and E2 Node. The process involves RAN data collection, TS target generation (Mode 1 and Mode 2), policy setup, traffic steering enrichment, TS optimization, and performance evaluation loops. - -Figure 4.1.3.1-1: The overall procedure for Near-RT RIC A1-policy based traffic steering use case - -### 4.1.4 Required data - -This clause elaborates the Near-RT RIC and the E2 node capabilities necessary for implementation of the traffic steering use case. The requirements are specified in clause 5. - -#### 4.1.4.1 Control over E2 - -**Mobility control:** Serving cell can be chosen based on the resource status and QoS of the UE(s) targeted by an A1 traffic steering policy. Moreover, load balancing can be achieved to improve the overall network performance. The following procedures can be used for traffic steering: - -- Handover from the source cell to the target cell -- Configuration/reconfiguration of handover restriction list -- Configuration of idle mode mobility parameters -- Enable, disable, or modify CA (as specified in 3GPP TS 38.300 [14], 3GPP TS 36.300 [8], 3GPP TS 38.473 [21], 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]) -- Enable, disable, or modify dual connectivity (as specified in 3GPP TS 38.300 [14], 3GPP TS 36.300 [8], 3GPP TS 37.340 [13], 3GPP TS 38.473 [21], 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]) - -Both RIC POLICY and RIC CONTROL can be used. - -#### 4.1.4.2 UE context information from E2 nodes - -The followings are examples of UE context information identified as required: - -- UE ID (as specified in [32]) -- Slice level: S-NSSAI -- DRB level: e.g., established DRB ID, mapping with QoS flows, etc. -- QoS related: e.g., E-RAB level QoS parameters (4G, NSA) or QoS flow level QoS parameters (NG-RAN). -- UE capabilities: CA and DC capabilities - -For example, UE ID, S-NSSAI, DRB ID, or QCI/5QI can be used to derive the QoS requirements and the resource occupation; the UE capabilities may be required to select the appropriate RRM action (e.g., CA/DC configuration). - -#### 4.1.4.3 Measurements from E2 nodes - -The E2 measurements are necessary for inference and prediction in the Near-RT RIC as the driver for decisions in addition to KPMs. For the traffic steering use case, the Near-RT RIC can translate an A1 policy (relatively static targets) into a flexible selection of controls over E2 (e.g., handover control, DC, CA, idle mode mobility) by taking into account the RAN resource utilization, cell level and the UE level performance, the radio conditions, etc. - -The examples of measurement information identified as required are listed in table 4.1.4.3-1 below. - -**Table 4.1.4.3-1: Measurements from E2 nodes** - -| Measurement Type | Measurement Examples | -|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Cell/SSB area related measurements |
  • - DL/UL Total PRB Usage, Distribution of DL/UL Total PRB Usage, DL/UL GBR PRB Usage, DL/UL non-GBR PRB Usage, RRC Connection Number, Available RRC Connection Capacity Value, Mean and Maximum Number of Active UEs per DRB in the DL/UL, DL/UL Scheduling PDCCH CCE Usage, DL/UL Composite Available Capacity, DL/UL Cell PDCP SDU Data Volume (including secondary RAT usage for EN-DC/MR-DC), Handover success ratio
  • - DL/UL SSB Area Total PRB Usage, DL/UL SSB Area GBR PRB Usage, DL/UL SSB Area non-GBR PRB Usage, SSB Area Capacity Value
  • - DL/UL PRB usage per QCI, DL/UL PRB usage per 5QI, DL/UL PRB usage per slice, Slice Available Capacity Value

As specified in 3GPP TS 32.425 [7], 3GPP TS 28.552 [6], 3GPP TS 36.314 [9], 3GPP TS 38.314 [16], 3GPP TS 38.423 [19], 3GPP TS 38.463 [20] and 3GPP TS 38.473 [21]

| -| E2-node user plane measurements per-UE / UE group |
  • - Average DL/UL throughput
  • - DL/UL PRB usage
  • - DL/UL Scheduled IP throughput
  • - Buffer Status Information (e.g., UL BSR)

As specified in 3GPP TS 32.425 [7], 3GPP TS 28.552[6], 3GPP TS 36.314 [9], 3GPP TS 38.314 [16], 3GPP TS 38.423 [19], 3GPP TS 38.473 [21], 3GPP TS 38.463 [20], 3GPP TS 36.321 [10] and 3GPP TS 38.321 [17]

| -| UE L1/L2/L3 measurements |
  • - RSRP and RSRQ measurements
  • - SINR measurements
  • - CQI/MCS measurements
  • - Location and Velocity measurements

As specified in 3GPP TS 36.331 [11] and 3GPP TS 38.331 [18]

| - -#### 4.1.4.4 E2 node configuration - -Cell level configuration parameters, such as PCI, neighbor relations and related offsets etc. are needed at Near-RT RIC in order to e.g., configure UE measurements monitor cell level performance and manage mobility control (handover and cell reselection) according to the network topology and the related E2 parameters. - -## 4.2 QoS based resource optimization - -This use case provides the background and motivation for the O-RAN architecture to support near real-time QoS aware resource optimization. - -Based on the end-to-end requirements for the QoS based resource optimization use case specified in [32], some high-level functional descriptions and requirements over Near-RT RIC and E2 interface are introduced. - -### 4.2.1 Background and goal of the use case - -The network shall offer means to prioritize resources while preserving the required QoS properties, e.g., reliability, latency, bandwidth requirements, as specified in 3GPP TS 23.203 [2]. Current RAN network coverage and capacity depends on rigorous planning and configuration. However, due to varying nature of traffic demands and radio channels as well as multiple services to co-exist, it is hard to satisfy all QoS requirements simultaneously. - -In summary, it is important for an E2 node to achieve QoS targets as smoothly as possible. The QoS aware resource optimization should provide a refined granularity of radio resource allocation based on varying radio conditions and traffics in order to meet the diverse requirements of reliability, latency, and bandwidth simultaneously. In addition, it should coordinate allocation of radio resources for co-existing multiple services, which may have different priorities, to achieve the optimal utilization of radio resources. - -In case when the network performance data is observed outside the boundary of the defined QoS targets, the Near-RT RIC should be able to trigger re-allocation of radio resources so that the QoS indicators can move back within limits outlined in the A1 policies. - -### 4.2.2 Entities/resources involved in the use case - -#### 1) OAM functions in SMO domain: - -- Collect necessary measurement metrics from network level measurement report and enrichment data (can acquire data from application) for constructing/training relevant AI/ML models. -- Deploy or update, configure the relevant QoS optimization AI/ML models to Near-RT RIC via O1. - -#### 2) Non-RT RIC in SMO domain: - -- Send A1 policies to and receive policy feedback from Near-RT RIC to drive resource optimization at RAN level. -- E.g., QoS targets as specified in 3GPP TS 23.203 [2], such as GFBR, MFBR, priority level, PDB. -- See O-RAN.WG2.A1AP [24] for more information. - -#### 3) Near-RT RIC: - -- Support update of AI/ML models from SMO. -- Support inference, such as QoS prediction, using AI/ML models from Non-RT RIC based on network data, e.g., measurement reports from E2 node. -- Support interpretation and execution of A1 policies from Non-RT RIC. -- Sending QoS resource optimization related policies and commands to E2 node to influence RRM behavior. -- Sending the relevant A1 policy feedback to Non-RT RIC for potential policy update. -- Sending the relevant O1 performance data to OAM functions, can be used by Non-RT RIC for potential policy update. - -#### 4) E2 node: - -- Support reporting of UE context, network measurements, and UE measurements to Near-RT RIC over E2 interface. -- Executes policies and commands received from Near-RT RIC over E2 interface. -- Support network and UE performance report to OAM functions in SMO domain over O1 interface. - -### 4.2.3 Solutions - -The context of QoS based resource optimization use case is captured in table 4.2.3-1. - -**Table 4.2.3-1: QoS based resource optimization use case** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | QoS-aware resource optimization in E2 nodes in accordance with A1 policies and O1 configuration. | | -| Actors and Roles |
  • - OAM functions in SMO domain: Performance data and training data collection, AI model training targeting to QoS optimization.
  • - Non-RT RIC in SMO domain: Creates and updates A1 policies.
  • - Near-RT RIC: Enforces A1 policies and generates RIC CONTROL and/or POLICY.
  • - E2 node: RIC CONTROL and POLICY execution and RIC REPORT creation.
Refer to 4.2.2 for more details. | | -| Assumptions |
  • - All relevant functions and components are instantiated and configured.
  • - A1, O1, E2 interface connectivity is established.
| | -| Pre-conditions |

Network is operational with default configuration.

OAM functions have established RAN data collection, and Non-RT RIC has access to this data.

Non-RT RIC analyzes the history data from RAN and triggers SMO to train the relevant AI/ML models which are deployed or updated in Near-RT RIC via O1 interface.

Non-RT RIC and Near-RT RIC have exchanged capabilities for the support of QoS-aware resource optimization.

| | -| Begins when | QoS-aware optimization policy is required to be initiated or updated. | | -| Step 1 (O) | (Start of outer loop control)
Non-RT RIC evaluates the collected data and A1 policy feedback, if required, and generates or updates the appropriate QoS-aware resource optimization policy, such as QoS targets, and sends it to Near-RT RIC via A1 interface. | | -| Step 2 (M) | When Near-RT RIC receives an A1 policy from Non-RT RIC, Near-RT RIC initiates the corresponding optimization procedure. | | -| Step 3 (M) | (Start of inner loop control)
Near-RT RIC subscribes to a UE context information and measurement metrics via E2 interface. | | -| Step 4 (M) | E2 nodes report the UE context information and E2 measurements via RIC REPORT periodically or event-triggered. | | -| Step 5 (M) | Near-RT RIC evaluates the performance data from E2 nodes (including performance data from different E2 nodes for the same UE) and finds the performance is out of QoS targets which are indicated in the A1 policy. If performance is within the targets, Near-RT RIC keeps monitoring. | | -| Step 6 (M) | Based on the UE context information, E2 measurement metrics (RIC REPORT), and A1 policy, Near-RT RIC may generate new or modify the existing E2 policies and sends them to E2 nodes. Near-RT RIC may also generate control command(s) and send them to E2 node(s) to trigger re-allocation of radio resources so that QoS indicators can move back to the limits outlined in the A1 policies.

Step 3 to Step 6 may repeat. (End of inner loop control)

| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 7 (O) | If required, Near-RT RIC sends policy feedback to Non-RT RIC to assess the performance of QoS optimization function in Near-RT RIC, or to assess the outcome of the applied A1 policies. Subsequently, an A1 policy can be updated.

Step 1 to Step 7 may repeat ( End of outer loop control ) | | -| Ends when | Non-RT RIC decides to delete QoS-aware resource optimization policy and sends the related message to Near-RT RIC. | | -| Exceptions | - | | -| Post Conditions | Non-RT RIC continues to collect and evaluate RAN data related to the QoS-aware optimization use case. | | -| Traceability | REQ-E2-QoS-FUN1, REQ-E2-QoS-FUN2, REQ-E2-QoS-FUN3, REQ-E2-QoS-FUN4, REQ-E2-QoS-FUN5, REQ-E2-QoS-FUN6 | | - -``` - -@startuml -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Box "Service Management and Orchestration" #gold - Participant OF as "OAM Functions" - Participant non as "Non-RT RIC" -End box - -Box "O-RAN" #lightpink - Participant near as "Near-RT RIC" - Participant ran as "E2 Node" -End box - -group OUTER LOOP CONTROL - -ran <-> OF : <> RAN data collection -OF -> non : Collected data -non -> non : Collected data evaluation & QoS target generation -non -> near : <> A1 policy setup or update -near -> near : QoS optimization initiated - -group INNER LOOP CONTROL - near -> ran : <> RIC SUBSCRIPTION REQUEST (UE context and/or Measurement metrics) - ran -> near : <> RIC INDICATION (UE context and/or Measurement metrics) - non -> near : (opt.) <> QoS related A1 Enrichment Information - near -> near : QoS performance monitoring - near -> ran : (opt.) <> RIC SUBSCRIPTION REQUEST (QoS optimization RIC POLICY) - near -> ran : (opt.) <> RIC CONTROL REQUEST (QoS optimization RIC CONTROL) -end - -OF <- near : (opt.) <> QoS optimization related performance information -OF -> non : (opt.) Performance information -non -> non : QoS optimization performance evaluation -end - -non -> near : <> A1 policy delete -near -> ran : <> RIC SUBSCRIPTION DELETE - -@enduml - -``` - -The overall procedure for QoS based resource optimization use case is given in figure 4.2.3-1. - -![Sequence diagram showing the overall procedure for QoS based resource optimization use case. The diagram is divided into two main sections: OUTER LOOP CONTROL and INNER LOOP CONTROL. The participants are Service Management and Orchestration (OAM Functions, non-RTNon-RT RIC), O-RAN (Near-RT RIC, E2 Node). The sequence starts with RAN data collection from E2 Node to non-RTNon-RT RIC, followed by data evaluation and policy setup. The INNER LOOP CONTROL involves RIC subscription and control requests from Near-RT RIC to E2 Node, with optional feedback to non-RTNon-RT RIC. The process concludes with policy deletion and subscription deletion.](5445597cceefaca1ac89e710fe339325_img.jpg) - -``` - -sequenceDiagram - participant SM&O as Service Management and Orchestration - subgraph SM&O - OAM[OAM Functions] - nonRT[non-RTNon-RT RIC] - end - subgraph ORAN [O-RAN] - NearRT[Near-RT RIC] - E2[E2 Node] - end - - Note left of SM&O: OUTER LOOP CONTROL - E2->>nonRT: <> RAN data collection - nonRT-->>OAM: Collected data - OAM-->>nonRT: Collected data evaluation & QoS target generation - nonRT->>NearRT: <> A1 policy setup or update - NearRT-->>E2: QoS optimization initiated - - Note left of SM&O: INNER LOOP CONTROL - NearRT->>E2: <> RIC SUBSCRIPTION REQUEST (UE context and/or Measurement metrics) - E2-->>NearRT: <> RIC INDICATION (UE context and/or Measurement metrics) - NearRT-->>nonRT: (opt) <> QoS related A1 Enrichment Information - NearRT-->>E2: QoS performance monitoring - NearRT->>E2: (opt) <> RIC SUBSCRIPTION REQUEST (QoS optimization RIC POLICY) - NearRT->>E2: (opt) <> RIC CONTROL REQUEST (QoS optimization RIC CONTROL) - - E2-->>nonRT: (opt) <> QoS optimization related performance information - nonRT-->>OAM: (opt) Performance information - OAM-->>nonRT: QoS optimization performance evaluation - nonRT->>NearRT: <> A1 policy delete - NearRT->>E2: <> RIC SUBSCRIPTION DELETE - -``` - -Sequence diagram showing the overall procedure for QoS based resource optimization use case. The diagram is divided into two main sections: OUTER LOOP CONTROL and INNER LOOP CONTROL. The participants are Service Management and Orchestration (OAM Functions, non-RTNon-RT RIC), O-RAN (Near-RT RIC, E2 Node). The sequence starts with RAN data collection from E2 Node to non-RTNon-RT RIC, followed by data evaluation and policy setup. The INNER LOOP CONTROL involves RIC subscription and control requests from Near-RT RIC to E2 Node, with optional feedback to non-RTNon-RT RIC. The process concludes with policy deletion and subscription deletion. - -Figure 4.2.3-1: The overall procedure for QoS based resource optimization use case - -### 4.2.4 Required data - -This clause elaborates the Near-RT RIC and the E2 node capabilities necessary for implementation of the QoS based resource optimization use case. The requirements are specified in clause 5. - -#### 4.2.4.1 Control over E2 - -1) **DRB control:** RB control can be applied for modification of the following QoS properties: - -- DRB QoS modification (as specified in 3GPP TS 38.473 [21] and 3GPP TS 23.501 [3]): The DRB level QoS may be tuned to accommodate A1 policy requirement. -- QoS flow remapping (as specified in 3GPP TS 38.473 [21]): The mapping relationship between QoS flows and DRBs may be adjusted. -- Logical channel reconfiguration (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]): The relevant parameters can be considered, e.g., priority, prioritized bit rate, bucket size duration, etc. -- Radio admission control (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]): DRB admission control such as reject, or release may be applied. -- Modification of dual-connectivity DRB (as specified in 3GPP TS 37.340 [13]): Change of bearer termination point (MN or SN) and/or bearer types (MCG/SCG/split), and control of split ratio for a split bearer. -- Activation and deactivation of packet duplication and configuration of the number of legs in DC, CA, or DC+CA scenarios (as specified in 3GPP TS 36.300 [8] and 3GPP TS 38.300 [14]). - -RIC CONTROL (e.g., request for QoS flow remapping) or RIC POLICY (e.g., DRB admission policy) can be applicable. - -2) **Radio resource allocation**, such as configuration of DRX, semi-persistent scheduling (SPS), or guidance for the scheduling and rate selection in MAC. For example, based on prediction, an E2 policy or control to reconfigure SPS configuration or *ConfiguredGrantConfig* for UL may be generated. - -- DRX reconfiguration (as specified in 3GPP TS 38.473 [21], 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]): Long DRX cycle length, short DRX cycle length as well as short DRX cycle timer can be considered. -- SR periodicity reconfiguration (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]): Both *sr-ProhibitTimer* and *sr-TransMax* can be treated. -- SPS configuration (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]): Both *SPS-Config* (DL) and *ConfiguredGrantConfig* (UL) can be treated. -- Reconfiguration of slice level PRB quota (as specified in 3GPP TS 28.541 [4]) -- Configuration of CQI table with certain target block error rate (as specified in 3GPP TS 38.214 [15]) - -Both RIC POLICY and RIC CONTROL can be used. For example, SPS can be configured via RIC CONTROL; RIC POLICY can be used, e.g., to set the guidance for the scheduler. - -3) **Radio access control**: Depending on operator's policies, deployment scenarios, subscriber profiles, and available services, different criterion will be used in determining which access attempt should be allowed or blocked when congestion occurs in the system, as specified in 3GPP TS 22.261 [1]. For example, access control may be applied to restrict access of other UEs for a specific cell in order to achieve better QoS for some UEs. A cell-level, UE-level, or slice-level access control can be applied. Four categories of radio access control are indicated as below: - -- RACH backoff -- RRC connection reject -- RRC connection release -- Access barring - -Both RIC POLICY and RIC CONTROL can be used. - -4) **Connection mobility control**: For example, a neighbouring cell may be selected for the optimization of QoS of a specific UE. A neighbour handover restriction list may be configured to prevent the UEs from HO to some neighbouring cells in order to guarantee QoS of the UEs served by those neighbouring cells. Or a capacity boosting mechanism can be used to achieve better QoS, e.g., enable CA/DC. - -- Handover from the source cell to the target cell -- Configuration/reconfiguration of handover restriction list -- Enable, disable, or modify CA (as specified in 3GPP TS 38.473 [21], 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]) -- Enable, disable, or modify dual connectivity (as specified in 3GPP TS 38.473 [21], 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]) - -Both RIC POLICY and RIC CONTROL can be used. For the specific requirements and related stage-3 E2SM works, please refer to the traffic steering use case defined in clause 4.1. - -5) **UE transmit power control**: For example, when the uplink interference is too large, it is difficult to achieve the uplink QoS target. In this case, UE transmit power control will be used to adjust the amount of interference to achieve required QoS. Near-RT RIC configures target value of uplink received quality such as received SINR or power at E2 node. E2 node controls the UE power by executing open-loop/closed-loop power control to UE to achieve target value configured by Near-RT RIC. - -- Configuration or modification of target value of uplink received quality such as received SINR or received power at E2 node. - -RIC CONTROL, RIC POLICY can be used. - -NOTE: When the target UEs are at the cell edge, their QoS of uplink can be improved by increasing their transmit power and/or allocating additional resources to the UEs. Hence for UEs at the cell edge, the optimization should consider the impact on serving and neighbour cell. - -#### 4.2.4.2 UE context information from E2 nodes - -The followings are examples of UE context information identified as required: - -- UE ID (as specified in [32]) -- Slice level: S-NSSAI -- DRB level: e.g., established DRB ID, mapping with QoS flows, etc. -- QoS related: e.g., E-RAB level QoS parameters (4G, NSA) or QoS flow level QoS parameters (NG-RAN) -- UE capabilities: CA and DC capabilities -- RLC/MAC/PHY level: e.g., logical channel, DRX, scheduling request, SPS configurations - -For example, UE ID, S-NSSAI, DRB ID, or QCI/5QI can be used for different granularity of controls over E2; an established DRB level information may be needed to change the mapping of QoS flows to a specific DRB or modify DRB attributes; the UE capabilities may be required to make sure if CA/DC can be enabled. - -#### 4.2.4.3 Measurements from E2 nodes - -The E2 measurements are necessary for inference and prediction in the Near-RT RIC as the driver for decisions in addition to KPMs. For the QoS based resource optimization use case, the Near-RT RIC can translate an A1 policy (relatively static targets) into a flexible selection of controls over E2 (e.g., RB control, handover, access control) by taking into account the runtime status in the Near-RT RIC. Therefore, it is required to specify those measurement parameters as possible as needed over E2 interface. - -The examples of UE-level, cell-level, and slice-level measurement information identified as required are listed in table 4.2.4.3-1 below. - -**Table 4.2.4.3-1: Measurements from E2 nodes** - -| Measurement Type | | Measurement Examples | -|------------------|-------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| UE-level | Radio channel info available at DU | 1. CQI (*) | -| | Radio channel info available at CU-CP for serving cell | 1. RSRP (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11])
2. RSRQ (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11])
3. SINR (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11])
See NOTE 1. | -| | Radio channel info available at CU-CP for neighboring cells | 1. RSRP (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11])
2. RSRQ (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11])
3. SINR (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11])
See NOTE 2. | -| | L2 | 1. DL/UL UE PRB usage for data traffic (*)
2. Average DL UE throughput in gNB (*)
3. Distribution of DL UE throughput in gNB (*)
4. Percentage of unrestricted DL UE data volume in gNB (*)
5. Packet Delay and RAN part packet delay components (*)
6. Packet Delay (*)
7. Data volume (per QCI, as specified in 3GPP TS 36.314 [9], clause 4.1.8)
8. DL PDCP occupied buffer size (*)
9. DL unused PDCP buffer size (*)
10. Packet Loss Rate per DRB (as specified in 3GPP TS 38.314 [16], clause 4.2.1.5) and per logical channel (*) | - -| Measurement Type | | Measurement Examples | -|------------------|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Cell-level | L2 |

1. CQI (available at DU; as specified in 3GPP TS 28.552 [6], clause 5.1.1.11.1)

2. MCS Distribution in PDSCH (available at DU; as specified in 3GPP TS 28.552 [6], clause 5.1.1.12.1)

3. DL/UL Total PRB usage (available at DU; as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.1 and 5.1.1.2.2 and in 3GPP TS 32.425 [7], clauses 4.5.3 and 4.5.4)

4. Distribution of DL/UL Total PRB usage (available at DU; as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.3 and 5.1.1.2.4 and in 3GPP TS 32.425 [7], clauses 4.5.10 and 4.5.11)

5. DL/UL PRB used for data traffic (available at DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.5 and 5.1.1.2.7)

6. DL/UL PRB usage for traffic (per QCI, as specified in 3GPP TS 32.425 [7], clauses 4.5.1 and 4.5.2)

7. DL/UL Total available PRB (available at DU; as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.6 and 5.1.1.2.8)

8. DL/UL PRB full utilization (as specified in 3GPP TS 32.425 [7], clauses 4.5.9.1 and 4.5.9.2)

9. Total number of DL/UL TBs (available at DU; split into subcounters per layer at MU-MIMO case, as specified in 3GPP TS 28.552 [6], clauses 5.1.1.7.3 and 5.1.1.7.8 and in 3GPP TS 32.425 [7], clauses 4.5.7.1 and 4.5.7.3)

10. Total error number of DL/UL TBs (available at DU; split into subcounters per layer at MU-MIMO case, as specified in 3GPP TS 28.552 [6], clauses 5.1.1.7.4 and 5.1.1.7.9 and in 3GPP TS 32.425 [7], clauses 4.5.7.2 and 4.5.7.4)

11. Average DL UE throughput in gNB (available at DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.1.3.1)

12. Distribution of DL UE throughput in gNB (available at DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.1.3.2)

13. Percentage of unrestricted DL UE data volume in gNB (available at DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.1.3.5)

14. Packet Delay (available at DU and CU-UP; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.3.3)

15. RAN part packet delay components (as specified in 3GPP TS 38.314 [16], clause 4.2.1.2)

16. Packet Delay (per QCI, as specified in 3GPP TS 36.314 [9], clause 4.1.4)

17. DL/UL Cell PDCP SDU Data Volume (available at CU-UP; per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.2.1 for non-split gNB, clause 5.1.3.6.2 for split gNB; per PLMN ID and per E-RAB QoS profile (QCI, ARP and GBR), as specified in 3GPP TS 32.425 [7], clause 4.4.7)

18. Mean number of Active UEs in the DL/UL per cell (available at DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clauses 5.1.1.23.1 and 5.1.1.23.3)

19. Max number of Active UEs in the DL/UL per cell (available at DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clauses 5.1.1.23.2 and 5.1.1.23.4)

20. Average number of Active UEs (per QCI, as specified in 3GPP TS 32.425 [7], clause 4.4.2)

21. Packet Loss Rate (available at CU-UP or DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and

| - -| Measurement Type | | Measurement Examples | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.3.1)
22. Packet Loss Rate (per QCI, as specified in 3GPP TS 32.425 [7], clause 4.4.4)
23. DL Packet Drop Rate (available at CU-UP or DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.3.2)
24. DL Packet Drop Rate (per QCI, as specified in 3GPP TS 32.425 [7], clause 4.4.3.2) | -| NOTE 1: Include periodical measurement report and/or RRC event trigger measurement report (A1-A6, B1-B2) (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [12]). | | | -| NOTE 2: Include periodical measurement report and/or RRC event trigger measurement report (A1-A6, B1-B2) (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]). | | | - -(\*) Detailed measurement definition will be provided in E2SM specifications. - -## 4.3 RAN slice SLA assurance - -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 as specified in 3GPP TS 22.261 [1]. 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 as specified in 3GPP TS 28.530 [4], especially in RAN side. Exemplary slice performance requirements are specified in terms of throughput, energy efficiency, latency and reliability at a high level in SDOs such as 3GPP TS 22.261 [1] and GSMA [22]. 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 as specified in 3GPP TS 28.552 [6] and information model definitions as specified in 3GPP TS 28.541 [5] 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. - -In the context of the RAN, the SLA assurance parameters sent over the A1 interface help the Near-RT RIC guide the behavior of the E2 nodes (O-CU-UP, O-CU-CP, O-DU). The Non-RT RIC utilizes the slice SLA information and performance metrics to derive the necessary set of A1 policies and sends those to the Near-RT RICs related to a network slice. Each subtending Near-RT RICs uses these A1 policies for further cell-level and/or UE-level policy guidance and/or control action over the E2 interface that affects the cells and/or UEs, involved in the network slice, served by the respective E2 nodes. The combined guidance is handled as one or more A1 policies and/or E2 policies and/or E2 control actions. The intention of the SLA assurance parameters in the RAN context is to provide guidance to the E2 nodes for assuring SLAs of the network slices in the radio access network. - -### 4.3.1 Background and goal of the use case - -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. - -#### **5G core and O-RAN cooperation for SLA enforcement** - -![Diagram showing 5G Core Network and 5G RAN Network components for SLA enforcement. The 5G Core Network includes AMF, UPF, and NSACF. The 5G RAN Network includes Non-RT RIC (SMO), Near RT RICs, and E2 Nodes. Text boxes explain that the 5G Core enforces SLA policy through network-wide behavior, while RAN level guidance is independent of and complements SLA policy enforcement in the 5G Core.](e354b57563dae469c00b412b2abdf765_img.jpg) - -**5G Core Network** - -AMF, UPF - -NSACF - -5G Core enforces SLA policy through network-wide behavior. - -**AMF** – The AMF allows the UE to access slice(s) through S-NSSAI requests and NSACF interaction. - -**NSACF** – The NSACF performs quota checks for admission of UEs to slices. - -**5G RAN Network** - -Non-RT RIC (SMO) - -Near RT RICs - -E2 Nodes - -**RAN & 5GC – RAN level guidance is independent of and complements SLA policy enforcement in the 5G Core (5GC)** - -**Non-RT RIC** – The Non-RT RIC can split the A1 Policy guidance to the Near-RT RICs. - -**Near-RT RICs** – The subtending Near-RT RICs each provide guidance to the E2 Nodes. - -Diagram showing 5G Core Network and 5G RAN Network components for SLA enforcement. The 5G Core Network includes AMF, UPF, and NSACF. The 5G RAN Network includes Non-RT RIC (SMO), Near RT RICs, and E2 Nodes. Text boxes explain that the 5G Core enforces SLA policy through network-wide behavior, while RAN level guidance is independent of and complements SLA policy enforcement in the 5G Core. - -Figure 4.3.1-1: Core & RAN cooperation for SLA enforcement - -The network functions and components that are related with SLA enforcement within 5G Core (5GC) and O-RAN are shown in figure 4.3.1-1. Although the 5GC enforces most of the SLA parameters, the components of the 5GC have a comprehensive view of the entire wireless network but from a core perspective. 3GPP Release 17 introduces the concept of a *Network Slice Admission Control Function* (NSACF). This debuted from the 3GPP TR 23.700-40 [i.3], and normative as specified in 3GPP TS 23.501 [31], clause 5.15.11. The purpose of the NSACF is to enforce some of the slice SLA parameters from a 5G core perspective. While NSACF handles slice-specific user admission control into the network as specified in GSMA NG.116 [22] GST criterion, the AMF allows the UE to access slice(s) through S-NSSAI or NSSAI requests through NSACF interaction. Together, they can perform network-level policy enforcement. However, these components do not have the detailed knowledge of RAN, such as RAN resources usage or where specific UEs are geographically located within a gNB. These 5GC components can perform only at a “network view” and they also do not have control over RAN resources. - -O-RAN SLA assurance is independent of and complements 5GC SLA policy enforcement. Within the RAN, the Near-RT RIC provides unique SLA policy actions within the scope of E2 nodes based on the A1 policy guidance received from the Non-RT RIC. - -#### Non-RT RIC & Near-RT RIC provide RAN guidance for SLA objectives - -![Diagram showing the flow of RAN guidance from 5G RAN Network through Non-RT RIC (SMO) and Near-RT RICs to E2 Nodes. The diagram includes icons for policies, decomposed policies, and E2 nodes. Below the diagram are two text boxes explaining the roles of Non-Real Time RIC and Near-Real Time RIC, and a note about RAN & 5GC guidance.](90ddb84c323b956e2d50a54d3f870566_img.jpg) - -**5G RAN Network** - -**Non-RT RIC (SMO)** → A1 Policy - -**Near-RT RICs** → A1 Policy Decomposed - -**RAN Guidance** → **E2 Nodes** - -**E2 Nodes** - -**Non-Real Time RIC** – The Non-RT RIC obtains SLA assurance policy, translates and if necessary, breaks down the SLA objectives per Near-RT RIC. - -**Near-Real Time RIC** – The subtending Near RT RICs obtain the SLA objectives via A1 policies from the Non-RT RIC. - -**E2 Nodes** – E2 Nodes receive guidance or control from their respective Near-RT RIC. - -**RAN & 5GC** – RAN level guidance is independent of and complements SLA policy enforcement in the 5G Core (5GC) - -Diagram showing the flow of RAN guidance from 5G RAN Network through Non-RT RIC (SMO) and Near-RT RICs to E2 Nodes. The diagram includes icons for policies, decomposed policies, and E2 nodes. Below the diagram are two text boxes explaining the roles of Non-Real Time RIC and Near-Real Time RIC, and a note about RAN & 5GC guidance. - -Figure 4.3.1-2: Non-RT RIC & Near-RT RIC RAN guidance - -As shown in figure 4.3.1-2, the Non-Real Time RIC obtains the SLA parameters from SMO. The Non-RT RIC has a system level view of RAN topology, configuration and performance, so rApps can provide ongoing guidance and decompose SLA objects to the subtending Near-RT RICs. The Non-RT RIC then translates the SLA parameters into SLA objective A1 policies to its subtending Near-RT RIC(s). In some cases, the SLA parameters are already RAN or UE specific. Those SLA parameters would then not need any change in their values and would be “passed-through” to the Near-RT RIC(s) in A1 policies. - -The Near-RT RICs obtain the SLA objectives via A1 policies from the Non-RT RIC. The Near-RT RIC can provide cell-level and/or UE-level guidance or control to the E2 nodes to achieve SLA assurance enforcement at the RAN level. The E2 nodes receive guidance or control from their respective Near-RT RICs. There are parameters as specified in GSMA GST/NEST NG.116 [22], such as the *Downlink and Uplink Throughput Per Network Slice*, that have both core and RAN applicability. - -For example, the *Downlink and Uplink Throughput Per Network Slice* can be used by 5GC network functions; and the Non-RT RIC can calculate *maxUlThptPerSlice* and *maxDlThptPerSlice* parameters in an A1 policy which will then be used by the Near-RT RIC as target values via monitoring E2 node performance and, where required, requesting appropriate E2 services (CONTROL and/or POLICY) to provide guidance to the E2 nodes. - -### 4.3.2 Entities/resources involved in the use case - -- 1) Non-RT RIC: - - a) Retrieve RAN slice SLA target from respective entities such as SMO, NSSMF. - - b) Long term monitoring of RAN slice performance measurements. - - c) Training of potential ML models that will be deployed in Non-RT RIC for slow loop optimization and/or Near-RT RIC for fast loop optimization. - - d) Support deployment and update of AI/ML models into Near-RT RIC. - - e) Receive slice control/slice SLA assurance rApps from SMO. - -- f) Create and update A1 policies based on RAN intent and A1 feedback. - - g) Send A1 policies and enrichment information to Near-RT RIC to drive slice assurance. - - h) Send O1 reconfiguration requests to SMO for slow-loop slice assurance. -- 2) Near-RT RIC: -- a) Near-real-time monitoring of slice specific RAN performance measurements. - - b) Support deployment and execution of the AI/ML models from Non-RT RIC. - - c) Receive slice SLA assurance xApps from SMO. - - d) Support interpretation and execution of policies from Non-RT RIC. - - e) Perform optimized RAN (E2) actions to achieve RAN slice requirements based on O1 configuration, A1 policy, and E2 reports. -- 3) E2 node: -- a) Support slice assurance actions such as slice-aware resource allocation, prioritization, etc. through E2. - - b) Support slice specific performance measurements through O1. - - c) Support slice specific performance reports through E2. - -### 4.3.3 Solutions - -#### 4.3.3.1 RAN slice SLA assurance - -The context of RAN slice SLA assurance is captured in table 4.3.3.1-1. - -**Table 4.3.3.1-1: RAN slice SLA assurance** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | RAN slice SLA assurance | | -| Actors and Roles | SMO functions, Non-RT RIC framework, Near-RT RIC, E2 nodes | | -| Assumptions | All relevant functions and components are instantiated.
A1, O1, E2 interface connectivity is established. | | -| Pre-conditions | Near-RT RIC and Non-RT RIC are instantiated with A1 interface connectivity being established between them.
O1 interfaces are established between SMO and Near-RT RIC, and SMO and E2 nodes.
RAN slice SLA assurance applications have been deployed in Non-RT RIC and Near-RT RIC respectively. | | -| Begins when | A RAN slice is activated, or an operator defined trigger is detected. | | -| Step 1 (M) | OAM functions may configure baseline slice SLA Assurance parameters in E2 node(s) through O1 interface.
OAM functions collect data from E2 node through O1 interface. | | -| Step 2 (M) | RAN slice SLA assurance rApp retrieves relevant information from Non-RT RIC framework, such as active RAN slices (such as active S-NSSAIs, network slice subnet instances, topology), RAN slice SLA information, NF configuration, etc. | | -| Step 3 (M) | RAN slice SLA assurance rApp monitors and evaluates performance of RAN slices which may include detection of possible RAN slice SLA violation. | | -| Step 4 (M) | RAN slice SLA assurance rApp decides to apply A1 policy-based RAN slice SLA assurance considering RAN slice SLA requirements and/or operator-defined RAN intents, EI from external application servers and O1 based long term trends. In addition to these input parameters, A1 feedback from Near-RT RIC, when available, can be utilized for updating existing policies. | | -| Step 5 (M) | (Start of inner loop control)
Near-RT RIC subscribes to a UE context information and measurement metrics via E2 interface. | | -| Step 6 (M) | E2 nodes report the UE context information and E2 measurements via RIC REPORT periodically or event-triggered. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 7 (M) | Near-RT RIC evaluates the performance data from E2 nodes (including performance data from different E2 nodes for the same UE) and finds the performance is out of slice SLA targets which are indicated in the A1 policy and/or internal Near-RT RIC slice SLA targets. | | -| Step 8 (M) | Based on the UE context information, E2 measurement metrics (RIC REPORT), and A1 policy, Near-RT RIC may generate new or modify the existing E2 policies and sends them to E2 nodes.
Near-RT RIC may also generate control command(s) and send them to E2 node(s) to trigger re-allocation of radio resources so that slice SLA indicators can move back to the limits outlined in the A1 policies. | | -| Step 9 (O) | Near-RT RIC may send A1 policy feedback on A1 to the Non-RT RIC. | | -| Step 10 (O) | Non-RT RIC decides to delete slice SLA assurance policy and sends the related message or following internal trigger, the Near-RT RIC terminates the slice SLA Assurance procedure. | | -| Ends when | RAN slice(s) is deactivated or an operator defined trigger is detected. | | -| Exceptions | None identified. | | -| Post Conditions | SLA assurance for RAN slice(s) over a period of time is achieved. | | -| Traceability | | | - -``` - -@startuml -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Box "Service Management and Orchestration" #gold - Participant OF as "OAM Functions" - Participant non as "Non-RT RIC" -End box - -Box "O-RAN" #lightpink - Participant near as "Near-RT RIC" - Participant ran as "E2 Node" -End box - -group OUTER LOOP CONTROL - -ran <-> OF : <> RAN data collection -OF -> non : RAN Slice SLA assurance data - -non -> non : Collected data evaluation and policy creation -non -> near : <> SLA Assurance policy setup or update - -group INNER LOOP CONTROL - near -> ran : <> RIC SUBSCRIPTION REQUEST (REPORT, UE context & Measurement metrics) - ran -> near : <> RIC INDICATION (UE context & Measurement metrics) - - near -> near : Evaluation, possible SLA violation prevention - near -> ran : (opt.) <> RIC SUBSCRIPTION REQUEST (POLICY) - -near -> ran : (opt.) <> RIC CONTROL REQUEST (Slice SLA assurance RIC CONTROL) -end - -non <-- near: (opt.) <> A1 Policy feedback - -end - -``` - -``` - -non --> near: (opt.) <> A1 policy delete -near -> near: (opt.) Slice SLA Assurance stopped -near-> ran: (opt.)<> RIC SUBSCRIPTION DELETE - -@enduml - -``` - -The flow diagram of the RAN slice SLA assurance is given in figure 4.3.3.1-1. - -![Sequence diagram for RAN slice SLA assurance showing interactions between Service Management and Orchestration (OAM Functions, Non-RT RIC), O-RAN (Near-RT RIC, E2 Node), and RAN (OAM Functions, Non-RT RIC). The diagram is divided into OUTER LOOP CONTROL and INNER LOOP CONTROL sections.](474a819357587e34949a3e110ff19b30_img.jpg) - -``` - -sequenceDiagram - participant SM as Service Management and Orchestration - subgraph SM [Service Management and Orchestration] - OAM1[OAM Functions] - NonRT1[Non-RT RIC] - end - subgraph O [O-RAN] - NearRT[Near-RT RIC] - E2[E2 Node] - end - subgraph R [RAN] - OAM2[OAM Functions] - NonRT2[Non-RT RIC] - end - - Note left of SM: OUTER LOOP CONTROL - OAM1->>E2: <> RAN data collection - E2-->>OAM1: RAN Slice SLA assurance data - OAM1->>NonRT1: Collected data evaluation and policy creation - NonRT1->>NearRT: <> SLA Assurance policy setup or update - - Note right of O: INNER LOOP CONTROL - NearRT->>E2: <> RIC SUBSCRIPTION REQUEST (REPORT, UE context & Measurement metrics) - E2-->>NearRT: <> RIC INDICATION (UE context & Measurement metrics) - NearRT->>E2: Evaluation, possible SLA violation prevention - Note right of E2: (opt) <> RIC SUBSCRIPTION REQUEST (POLICY) - Note right of E2: (opt) <> RIC CONTROL REQUEST (Slice SLA assurance RIC CONTROL) - - NonRT1-->>NonRT2: (opt) <> A1 Policy feedback - NonRT1-->>NonRT2: (opt) <> A1 policy delete - - Note right of O: (opt) Slice SLA Assurance stopped - NearRT-->>E2: (opt) Slice SLA Assurance stopped - NearRT-->>E2: (opt) <> RIC SUBSCRIPTION DELETE - -``` - -Sequence diagram for RAN slice SLA assurance showing interactions between Service Management and Orchestration (OAM Functions, Non-RT RIC), O-RAN (Near-RT RIC, E2 Node), and RAN (OAM Functions, Non-RT RIC). The diagram is divided into OUTER LOOP CONTROL and INNER LOOP CONTROL sections. - -Figure 4.3.3.1-1: RAN slice SLA assurance - -### 4.3.4 Required data - -This clause elaborates the Near-RT RIC and the E2 node capabilities necessary for implementation of the slice SLA assurance use case. The requirements are specified in clause 5. - -#### 4.3.4.1 Control over E2 - -- 1) **Radio resource allocation**, such as configuration of slice level PRB quota or per-cell-per-slice/QoS frequency partitions. For example, based on prediction, an E2 policy or control to reconfigure slice level PRB may be generated. Another example is, based on analysis of slice level interference among cells in terms of the reliability requirement, an E2 control to reconfigure frequency partitions may be generated. - - Configuration and/or reconfiguration of slice level PRB quota (as specified in 3GPP TS 28.541 [4]) - - Configuration and/or reconfiguration of per-cell-per-slice/QoS frequency partitions - -Both RIC POLICY and RIC CONTROL can be used. - -- 2) **Radio access control**: Depending on operator's policies, deployment scenarios, subscriber profiles, available services and SLA of slice, different criterion will be used in determining which access attempt should be allowed or blocked when - -congestion occurs in the system, as specified in 3GPP TS 22.261 [1]. For example, access control may be applied to restrict access of other UEs for a specific slice in order to achieve better SLA for some slice. A UE-level, or slice-level access control can be applied. Three categories of radio access control are indicated as below: - -- RRC connection reject -- RRC connection release -- Access barring - -#### 4.3.4.2 UE context information from E2 nodes - -The followings are examples of UE context information identified as required: - -- UE ID -- Slice level: S-NSSAI -- QoS level: 5QI -- UE-level RAN state information -- UE-level PM data - -For example, UE ID, S-NSSAI and 5QI can be used to derive the resource occupation of each slice. - -#### 4.3.4.3 Measurements from E2 nodes - -The E2 measurements are necessary for inference and prediction in the Near-RT RIC as the driver for decisions in addition to KPMs. For the slice SLA assurance use case, the Near-RT RIC can translate an A1 policy (relatively static targets) into a flexible selection of controls over E2 (e.g., PRB control, access control) by taking into account the runtime status in the Near-RT RIC. Therefore, it is required to specify those measurement parameters as possible as needed over E2 interface. - -The examples of cell-level, UE-level, and slice-level measurement information identified as required are listed in table 4.3.4.3-1 below. - -**Table 4.3.4.3-1: Measurements from E2 nodes** - -| Measurement Type | | Measurement Examples | -|------------------|----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Cell-level | L2 |
  1. 1. DL/UL Total PRB usage (available at DU; as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.1 and 5.1.1.2.2 and in 3GPP TS 32.425 [7], clauses 4.5.3 and 4.5.4)
  2. 2. Distribution of DL/UL Total PRB usage (available at DU; as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.3 and 5.1.1.2.4 and in 3GPP TS 32.425 [7], clauses 4.5.10 and 4.5.11)
  3. 3. DL/UL PRB used for data traffic (available at DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.5 and 5.1.1.2.7)
  4. 4. DL/UL Total available PRB (available at DU; as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.6 and 5.1.1.2.8)
  5. 5. Average DL UE throughput in gNB (available at DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.1.3.1)
  6. 6. Distribution of DL UE throughput in gNB (available at DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.1.3.2)
  7. 7. Packet Delay (available at DU and CU-UP; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.3.3)
| - -| Measurement Type | | Measurement Examples | -|------------------|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | |

8. DL/UL Cell PDCP SDU Data Volume (available at CU-UP; per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.2.1 for non-split gNB, clause 5.1.3.6.2 for split gNB; per PLMN ID and per E-RAB QoS profile (QCI, ARP and GBR), as specified in 3GPP TS 32.425 [7], clause 4.4.7)

9. Mean number of Active UEs in the DL/UL per cell (available at DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clauses 5.1.1.23.1 and 5.1.1.23.3)

10. Max number of Active UEs in the DL/UL per cell (available at DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clauses 5.1.1.23.2 and 5.1.1.23.4)

11. Average number of Active UEs (per QCI, as specified in 3GPP TS 32.425 [7], clause 4.4.2)

12. Packet Loss Rate (available at CU-UP or DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.3.1)

13. Packet Loss Rate (per QCI, as specified in 3GPP TS 32.425 [7], clause 4.4.4)

14. DL Packet Drop Rate (available at CU-UP or DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.3.2)

15. DL Packet Drop Rate (per QCI, as specified in 3GPP TS 32.425 [7], clause 4.4.3.2)

16. Wideband CQI distribution (as specified in 3GPP TS 28.552 [6], clause 5.1.1.11.1)

17. SS-RSRP distribution per SSB for serving cell (as specified in 3GPP TS 28.552 [6], clause 5.1.1.22.1)

18. SS-RSRP distribution per SSB for neighbor cell (as specified in 3GPP TS 28.552 [6], clause 5.1.1.22.1)

| -| Slice-level | L2 |

1. DL/UL PRB used for data traffic (as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.5 and 5.1.1.2.7)

2. Average DL UE throughput in gNB (as specified in 3GPP TS 28.552 [6], clause 5.1.1.3.1)

3. Distribution of DL UE throughput in gNB (as specified in 3GPP TS 28.552 [6], clause 5.1.1.3.2)

4. Packet Delay (as specified in 3GPP TS 28.552 [6], clause 5.1.3.3)

5. DL/UL Cell PDCP SDU Data Volume (as specified in 3GPP TS 32.425 [7], clause 4.4.7)

6. Mean number of Active UEs in the DL/UL per cell (as specified in 3GPP TS 28.552 [6], clauses 5.1.1.23.1 and 5.1.1.23.3)

7. Max number of Active UEs in the DL/UL per cell (as specified in 3GPP TS 28.552 [6], clauses 5.1.1.23.2 and 5.1.1.23.4)

8. Packet Loss Rate (as specified in 3GPP TS 28.552 [6], clause 5.1.3.1)

9. DL Packet Drop Rate (as specified in 3GPP TS 28.552 [6], clause 5.1.3.2)

| -| UE-level | L2 |

1. DL/UL PRB used for data traffic (as specified in O-RAN WG3 E2SM-KPM [36])

2. Average DL UE throughput in gNB (as specified in O-RAN WG3 E2SM-KPM [36])

3. Distribution of DL UE throughput in gNB (as specified in O-RAN WG3 E2SM-KPM [36])

4. Packet Delay (as specified in O-RAN WG3 E2SM-KPM [36])

5. DL/UL Cell PDCP SDU Data Volume (as specified in O-RAN WG3 E2SM-KPM [36])

| - -| Measurement Type | | Measurement Examples | -|------------------|--|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | 6. Mean number of Active UEs in the DL/UL per cell (as specified in O-RAN WG3 E2SM-KPM [36])
7. Max number of Active UEs in the DL/UL per cell (as specified in O-RAN WG3 E2SM-KPM [36])
8. Packet Loss Rate (as specified in O-RAN WG3 E2SM-KPM [36])
9. DL Packet Drop Rate (as specified in O-RAN WG3 E2SM-KPM [36])
10. DRB-specific RLC buffer occupancy (as specified in O-RAN WG3 E2SM-RC [37])
11. Serving cell and neighbor cell RRC measurements (as specified in O-RAN WG3 E2SM-RC [37])
12. Number of DRBs and PDU sessions (as specified in O-RAN WG3 E2SM-RC [37])
13. Number of QoS flows and QoS parameters of QoS flows mapped to each DRB (as specified in O-RAN WG3 E2SM-RC [37])
14. Number of HARQ TBs with specific MCS rates (as specified in O-RAN WG3 E2SM-KPM [36])
15. CQI (as specified in O-RAN WG3 E2SM-KPM [36])
16. Serving cell and neighbor cell RSRP (as specified in O-RAN WG3 E2SM-KPM [36]) | - -## 4.4 Massive MIMO optimization - -### 4.4.1 Background and goal of the use case - -Please refer to [i.2] and [32]. - -### 4.4.2 Entities/resources involved in the use case - -NOTE: The AI/ML model training, deployment, and inference described below cannot be applicable for some mMIMO optimization features. - -#### 1) SMO/Non-RT RIC: - -- Retrieve necessary performance indicators, measurement reports and RAN configurations from E2 nodes via the O1 interface for the purpose of AI/ML model training and performance monitoring. - - E.g., the number of supported Non-GoB BF modes in O-DU. -- Collect enrichment information from application servers and associate enrichment information with collected measurements and configurations. -- Perform AI/ML model training and deployment. -- Perform AI/ML model performance monitoring and re-training. -- Send enrichment information to the Near-RT RIC for inference via the A1 interface. - -NOTE: The requirements of SMO/Non-RT RIC are under the scope of WG2. - -#### 2) Near-RT RIC: - -- Support AI/ML model deployment from the Non-RT RIC via the O1/O2 interface. -- Subscribe and retrieve necessary performance and failure indicators, measurement reports, UE context information and RAN configurations from E2 nodes via the E2 interface for the purpose of mMIMO optimization. -- Retrieve enrichment information from Non-RT RIC via the A1 interface, and associate enrichment information with collected measurements and configurations. -- Perform AI/ML model training and inference. -- Perform AI/ML model performance monitoring and re-training. -- Send control or policy message for massive MIMO optimization to E2 nodes via the E2 interface. - -#### 3) E2 nodes: - -- Support reporting of necessary performance indicators, measurement reports, UE context information and RAN configurations with required granularity to SMO/Non-RT RIC via the O1 interface. -- Support reporting of necessary performance and failure indicators, measurement reports, UE context information collection and RAN configurations with required granularity to Near-RT RIC via the E2 interface. -- Execute control/policy message received from the Near-RT RIC via the E2 interface. - -### 4.4.3 Solutions - -#### 4.4.3.1 AI/ML-assisted Non-Grid-of-Beams beamforming optimization - -##### 4.4.3.1.1 Model training in Non-RT RIC - -NOTE: The below table 4.4.3.1.1-1 and figure 4.4.3.1.1-1 are under the scope of WG2. - -The context of AI/ML-assisted Non-GoB BF mode selection in Non-RT RIC – model training, deployment, and update is captured in table 4.4.3.1.1-1. - -**Table 4.4.3.1.1-1: AI/ML-assisted Non-GoB BF mode selection in Non-RT RIC – model training, deployment, and update** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To train an AI/ML model to select the best Non-GoB BF modes given wireless conditions and RAN configuration. | | -| Actors and Roles | SMO, Non-RT RIC, Near-RT RIC, O-DU, Application server | | -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - O1 interface connectivity is established.
| | -| Pre-conditions |
  • - O1 interface is established between SMO and O-DU to enable SMO/Non-RT RIC to obtain the number of supported Non-GoB BF modes and to collect performance measurement data and associated RAN configurations.
  • - A1 interface is established between Non-RT RIC and Near-RT RIC to enable enrichment information transfer.
  • - O-DU supports Non-GoB BF.
| | -| Begins when | Operator specified trigger condition or event is satisfied. | | -| Step 1 (M) | SMO requests the number of supported Non-GoB BF modes in O-DU via the O1 interface. | | -| Step 2 (M) | SMO collects the number of supported Non-GoB BF modes in O-DU via the O1 interface. | | -| Step 3 (M) | Non-RT RIC retrieves collected information. | | -| Step 4 (M) | For each Non-GoB BF mode, SMO requests performance measurement data and associated RAN configurations from O-DU for model training via the O1 interface. | | -| Step 5 (M) | SMO collects required performance measurement data and RAN configurations from O-DU via the O1 interface. | | -| Step 6 (M) | SMO collects enrichment information (e.g., UE mobility and location info.) from application server. | | -| Step 7 (M) | Non-RT RIC retrieves collected data and enrichment information. | | -| Step 8 (M) | For each Non-GoB BF mode, Non-RT RIC associates received enrichment information with measurement data and RAN configurations. | | -| Step 9 (M) | Non-RT RIC performs model training. | | -| Step 10 (M) | Non-RT RIC deploys trained model to the Near-RT RIC via O1 or O2 interface. | | -| Step 11 (M) | For each Non-GoB BF mode, SMO requests performance measurement data from O-DU for performance monitoring via the O1 interface. | | -| Step 12 (M) | For each Non-GoB BF mode, SMO collects performance measurement data from O-DU for performance monitoring via the O1 interface. | | -| Step 13 (M) | SMO collects enrichment information (e.g., UE mobility and location info.) from application server. | | -| Step 14 (M) | Non-RT RIC retrieves collected performance monitoring data and enrichment information. | | -| Step 15 (M) | Non-RT RIC evaluates the performance of deployed AI/ML model. | | -| Step 16 (M) | Non-RT RIC re-trains the model. | | -| Step 17 (M) | Non-RT RIC updates model in the Near-RT RIC via O1 or O2 interface. | | -| Ends when | Operator specified trigger condition or event is satisfied. | | -| Exceptions | None identified. | | -| Post Conditions | Near-RT RIC executes the deployed model for AI/ML-assisted Non-GoB BF. | | -| Traceability | REQ-Non-RT-RIC-FUN1, REQ-Non-RT-RIC-FUN4, REQ-Non-RT-RIC-FUN5, REQ-Non-RT-RIC-FUN9, REQ-A1-FUN2, REQ-Near-RT-RIC-MM-FUN2 | | - -``` -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -``` - -``` - -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 as "Near-RT RIC" - Participant ran as "O-DU" -End box - -Box "External" #lightcyan - Participant "Application Server" as app -End box - -group Data Collection - smo -> ran : <> Request the number of supported Non-GoB BF modes - ran -> smo : <> Collect the number of supported Non-GoB BF modes - smo -> non : Retrieve collected information - - smo -> ran : <> Request measurement data and RAN configurations for each Non-GoB BF mode - ran -> smo : <> Collect measurement data and RAN configurations for each Non-GoB BF mode - app -> smo : Collect enrichment information (e.g., UE location/mobility, etc.) - smo -> non : Retrieve collected data -end - -group AI/ML workflow - non -> non : Associate enrichment information with \n measurements and configurations - non -> non : Train AI/ML models to select \n the best Non-GoB mode - non -> near: <> or <> \n Deploy AI/ML models -end - -group Performance evaluation and optimization - smo -> ran : <> Request measurement data and RAN configurations for each Non-GoB BF mode - ran -> smo : <> Collect measurement data and RAN configurations for each Non-GoB BF mode - app -> smo : Collect enrichment information (e.g., UE location/mobility, etc.) - smo -> non : Retrieve collected data - non -> non : Performance monitoring & evaluation - non -> non : Re-train AI/ML models - non -> near: <> or <> \n Update AI/ML models -end - -@enduml - -``` - -The flow diagram of the AI/ML model training in Non-RT RIC, deployment, and performance monitoring is given in figure 4.4.3.1.1-1. - -![Sequence diagram showing AI/ML model training, deployment, and performance monitoring between Service Management and Orchestration, O-RAN (Near-RT RIC, O-DU), and External (Application Server) components.](1142ba0197b158bb198186fe8baccc32_img.jpg) - -``` - -sequenceDiagram - participant SMO as Service Management and Orchestration - subgraph O-RAN - participant RIC as Near-RT RIC - participant DU as O-DU - end - participant AS as External Application Server - - Note left of SMO: Service Management and Orchestration (Collection & Control, Non-RT RIC) - Note right of AS: External (Application Server) - - Note left of SMO: Data Collection - SMO->>DU: 1 <> Request the number of supported Non-GoB BF modes - DU-->>SMO: 2 <> Collect the number of supported Non-GoB BF modes - SMO->>DU: 3 Retrieve collected information - SMO->>DU: 4 <> Request measurement data and RAN configurations for each Non-GoB BF mode - DU-->>SMO: 5 <> Collect measurement data and RAN configurations for each Non-GoB BF mode - SMO->>AS: 6 Collect enrichment information (e.g., UE location/mobility, etc.) - SMO->>DU: 7 Retrieve collected data - - Note left of SMO: AI/ML workflow - Note right of AS: AI/ML workflow - Note left of SMO: AI/ML workflow - RIC->>RIC: 8 Associate enrichment information with measurements and configurations - RIC->>RIC: 9 Train AI/ML models to select the best Non-GoB mode - RIC->>DU: 10 <> or <> Deploy AI/ML models - - Note left of SMO: Performance evaluation and optimization - SMO->>DU: 11 <> Request measurement data and RAN configurations for each Non-GoB BF mode - DU-->>SMO: 12 <> Collect measurement data and RAN configurations for each Non-GoB BF mode - SMO->>AS: 13 Collect enrichment information (e.g., UE location/mobility, etc.) - SMO->>DU: 14 Retrieve collected data - RIC->>RIC: 15 Performance monitoring & evaluation - RIC->>RIC: 16 Re-train AI/ML models - RIC->>DU: 17 <> or <> Update AI/ML models - -``` - -Sequence diagram showing AI/ML model training, deployment, and performance monitoring between Service Management and Orchestration, O-RAN (Near-RT RIC, O-DU), and External (Application Server) components. - -Figure 4.4.3.1.1-1: AI/ML model training in Non-RT RIC, deployment, and performance monitoring - -##### 4.4.3.1.2 Model training in Near-RT RIC - -The context of AI/ML-assisted Non-GoB BF mode selection – model training in Near-RT RIC, deployment, and update is captured in table 4.4.3.1.2-1. - -**Table 4.4.3.1.2-1: AI/ML-assisted Non-GoB BF mode selection – model training in Near-RT RIC, deployment, and update** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To train an AI/ML model to select the best Non-GoB BF modes given wireless conditions and RAN configuration. | | -| Actors and Roles | SMO, Non-RT RIC, Near-RT RIC, O-DU, Application server | | -| Assumptions | - All relevant functions and components are instantiated. | | -| Pre-conditions | - A1 interface is established between Non-RT RIC and Near-RT RIC to enable enrichment information transfer.
- O-DU supports Non-GoB BF.
- E2 interface is established between Near-RT RIC and O-DU. | | -| Begins when | Operator specified trigger condition or event is satisfied. | | -| Step 1 (M) | Near-RT RIC requests the number of supported Non-GoB BF modes in O-DU via the E2 interface. | | -| Step 2 (M) | Near-RT RIC collects the number of supported Non-GoB BF modes in O-DU via the E2 interface. | | -| Step 3 (M) | For each Non-GoB BF mode, Near-RT RIC requests performance measurement data and associated RAN configurations from O-DU for model training via the E2 interface. | | -| Step 4 (M) | Near-RT RIC collects required performance measurement data and RAN configurations from O-DU via the E2 interface. | | -| Step 5 (M) | Near-RT RIC collects enrichment information (e.g., UE mobility and location info) from Non-RT RIC via the A1 interface. | | -| Step 6 (M) | For each Non-GoB BF mode, Near-RT RIC associates received enrichment information with measurement data and RAN configurations. | | -| Step 7 (M) | Near-RT RIC performs model training. | | -| Step 8 (M) | For each Non-GoB BF mode, Near-RT RIC requests performance measurement data from O-DU for performance monitoring/training updates via the E2 interface. | | -| Step 9 (M) | For each Non-GoB BF mode, Near-RT RIC collects performance measurement data from O-DU for performance monitoring/training updates via the E2 interface. | | -| Step 10 (M) | Near-RT RIC collects enrichment information (e.g., UE mobility and location info) from Non-RT RIC via the A1 interface. | | -| Step 11 (M) | Near-RT RIC evaluates the performance of deployed AI/ML model. | | -| Step 12 (M) | Near-RT RIC re-trains the model. | | -| Ends when | Operator specified trigger condition or event is satisfied. | | -| Exceptions | None identified. | | -| Post Conditions | Near-RT RIC executes the deployed model for AI/ML-assisted Non-GoB BF. | | -| Traceability | REQ-Non-RT-RIC-FUN9, REQ-A1-FUN3, REQ-Near-RT-RIC-MM-FUN1, REQ-Near-RT-RIC-MM-FUN3, REQ-E2-MM-FUN2, REQ-E2-MM-FUN3, REQ-E2-MM-FUN5, REQ-E2-MM-FUN6, REQ-E2-MM-FUN9, REQ-E2-MM-FUN10 | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -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 as "Near-RT RIC" - Participant ran as "O-DU" - -``` - -``` - -End box - -Box "External" #lightcyan - Participant "Application Server" as app -End box - -group Data Collection - near -> ran : <> Request the number of supported Non-GoB BF modes - ran -> near : <> Collect the number of supported Non-GoB BF modes - - near -> ran : <> Request measurement data and RAN configurations for each Non-GoB BF mode - ran -> near : <> Collect measurement data and RAN configurations for each Non-GoB BF mode - non -> near : <> Collect enrichment information (e.g., UE location/mobility, etc.) -end - -group AI/ML workflow - near -> near: Associate enrichment information with \n measurements and configurations - near -> near: Train AI/ML models to select \n the best Non-GoB mode -end - -group Performance evaluation and optimization - near -> ran : <> Request measurement data and RAN configurations for each Non-GoB BF mode - ran -> near: <> Collect measurement data and RAN configurations for each Non-GoB BF mode - non -> near : <> Collect enrichment information (e.g., UE location/mobility, etc.) - near -> near: Performance monitoring & evaluation - near -> near: Re-train AI/ML models -end - -@enduml - -``` - -The flow diagram of the AI/ML model training in Near-RT RIC, deployment, and performance monitoring is given in figure 4.4.3.1.2-1. - -![Sequence diagram showing interactions between Service Management and Orchestration, O-RAN (Near-RT RIC, O-DU), and External (Application Server) for AI/ML model training. The diagram is divided into three phases: Data Collection, AI/ML workflow, and Performance evaluation and optimization. Messages include requests for supported modes, measurement data, enrichment information, association of data, model training, performance monitoring, and re-training.](04cfca33e3fc26513abe649d7474f733_img.jpg) - -``` - -sequenceDiagram - participant SMO as Service Management and Orchestration - subgraph O-RAN - participant RIC as Near-RT RIC - participant DU as O-DU - end - participant AS as External Application Server - - Note left of SMO: Data Collection - RIC->>DU: 1 <> Request the number of supported Non-GoB BF modes - DU-->>RIC: 2 <> Collect the number of supported Non-GoB BF modes - RIC->>DU: 3 <> Request measurement data and RAN configurations for each Non-GoB BF mode - DU-->>RIC: 4 <> Collect measurement data and RAN configurations for each Non-GoB BF mode - SMO->>RIC: 5 <> Collect enrichment information (e.g., UE location/mobility, etc.) - - Note left of RIC: AI/ML workflow - RIC->>RIC: 6 Associate enrichment information with measurements and configurations - RIC->>RIC: 7 Train AI/ML models to select the best Non-GoB mode - - Note left of SMO: Performance evaluation and optimization - RIC->>DU: 8 <> Request measurement data and RAN configurations for each Non-GoB BF mode - DU-->>RIC: 9 <> Collect measurement data and RAN configurations for each Non-GoB BF mode - SMO->>RIC: 10 <> Collect enrichment information (e.g., UE location/mobility, etc.) - RIC->>RIC: 11 Performance monitoring & evaluation - RIC->>RIC: 12 Re-train AI/ML models - -``` - -Sequence diagram showing interactions between Service Management and Orchestration, O-RAN (Near-RT RIC, O-DU), and External (Application Server) for AI/ML model training. The diagram is divided into three phases: Data Collection, AI/ML workflow, and Performance evaluation and optimization. Messages include requests for supported modes, measurement data, enrichment information, association of data, model training, performance monitoring, and re-training. - -Figure 4.4.3.1.2-1: AI/ML model training in Near-RT RIC, deployment, and performance monitoring - -##### 4.4.3.1.3 Model inference - -The context of AI/ML-assisted Non-GoB BF mode selection – model inference is captured in table 4.4.3.1.3-1. - -**Table 4.4.3.1.3-1: AI/ML-assisted Non-GoB BF mode selection – model inference** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To generate Non-GoB control/policy message. | | -| Actors and Roles | SMO, Non-RT RIC, Near-RT RIC, O-DU, Application server | | -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - A1 and E2 interface connectivity are established.
| | -| Pre-conditions |
  • - A1 interface is established between Non-RT RIC and Near-RT RIC to enable enrichment information transfer.
  • - E2 interface is established between Near-RT RIC and O-DU to enable Non-GoB BF mode selection via E2 control/policy message.
  • - O-DU supports Non-GoB BF.
| | -| Begins when | Operator specified trigger condition or event is satisfied. | | -| Step 1 (M) | SMO collects enrichment information (e.g., UE mobility/location info) from application server. | | -| Step 2 (M) | Non-RT RIC retrieves collected enrichment information. | | -| Step 3 (M) | Non-RT RIC sends collected enrichment information to the Near-RT RIC via the A1 interface. | | -| Step 4 (M) | Near-RT RIC requests measurement data and UE context information (e.g., SRS periodicity) from O-DU via the E2 interface. | | -| Step 5 (M) | Near-RT RIC collects measurement data and UE context information (e.g., SRS periodicity) from O-DU via the E2 interface. | | -| Step 6 (M) | Near-RT RIC associates received enrichment information with collected measurement data and UE context information. | | -| Step 7 (M) | Near-RT RIC performs model inference. | | -| Step 8 (M) | Near-RT RIC generates Non-GoB control/policy message based on inferred Non-GoB BF mode selection. | | -| Step 9 (M) | Near-RT RIC sends Non-GoB control/policy message to O-DU via the E2 interface. | | -| Ends when | Operator specified trigger condition or event is satisfied. | | -| Exceptions | None identified. | | -| Post Conditions | Non-RT RIC monitors the performance of AI/ML-assisted Non-GoB BF mode selection in the Near-RT RIC. | | -| Traceability | REQ-Non-RT-RIC-FUN9,
REQ-A1-FUN3,
REQ-Near-RT-RIC-MM-FUN2,
REQ-Near-RT-RIC-MM-FUN3,
REQ-E2-MM-FUN2,
REQ-E2-MM-FUN3,
REQ-E2-MM-FUN5,
REQ-E2-MM-FUN6 | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -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 as "Near-RT RIC" - Participant ran as "O-DU" -End box - -``` - -``` - -Box "External" #lightcyan - Participant "Application Server" as app -End box - -app -> smo : Collect enrichment information (e.g., UE location/mobility, etc.) -smo -> non : Retrieve collected data -non -> near : <> Enrichment information - -group E2 control & Policy - near -> ran : <> Request measurement data \n and UE context information (e.g., SRS periodicity) - ran -> near : <> Collect measurement data \n and UE context information (e.g., SRS periodicity) - near -> near: Associate enrichment information with \n collected measurements and configurations - near -> near : Perform AI/ML model inference - near -> near : Generate Non-GoB control/policy message - near -> ran : <> Non-GoB control/policy message -end - -@enduml - -``` - -The flow diagram of the AI/ML inference is given in figure 4.4.3.1.3-1. - -![Sequence diagram for AI/ML Inference showing interactions between Service Management and Orchestration, O-RAN (Near-RT RIC, E2 control & Policy, O-DU), and External (Application Server).](f5deee2f3301ee351c4008283ffafbb3_img.jpg) - -``` - -sequenceDiagram - participant SM as Service Management and Orchestration - participant O as O-RAN - participant E as External - Note right of O: E2 control & Policy - - Note left of SM: Collection & Control, Non-RT RIC - Note right of O: Near-RT RIC, O-DU - Note right of E: Application Server - - E->>SM: 1 Collect enrichment information (e.g., UE location/mobility, etc.) - SM->>SM: 2 Retrieve collected data - SM->>O: 3 <> Enrichment information - - Note right of O: - O->>O: 4 <> Request measurement data and UE context information (e.g. SRS periodicity) - O->>O: 5 <> Collect measurement data and UE context information (e.g. SRS periodicity) - O->>O: 6 Associate enrichment information with collected measurements and configurations - O->>O: 7 Perform AI/ML model inference - O->>O: 8 Generate Non-GoB control/policy message - O->>O: 9 <> Non-GoB control/policy message - -``` - -Sequence diagram for AI/ML Inference showing interactions between Service Management and Orchestration, O-RAN (Near-RT RIC, E2 control & Policy, O-DU), and External (Application Server). - -Figure 4.4.3.1.3-1: AI/ML Inference - -#### 4.4.3.2 Beam-based Mobility Robustness Optimization (bMRO) - -Beam-based Mobility Robustness Optimization (bMRO) is an autonomous self-optimizing algorithm that improves beam-based inter-cell mobility performance by applying beam-specific HO parameters including Cell Individual Offsets (CIO), Time to Trigger (TTT), T310 counter, etc. on the handover configuration between neighbor cells, based on the analysis of beam-specific mobility-related counters and/or mobility failure events. bMRO is capable to reduce the number of unnecessary handovers, handover failures as well as ping-pong handovers particularly in cells that cover areas with different mobility characteristics. - -Performance, complexity and gain analysis has been provided in O-RAN.WG1.mMIMO-Use-Cases-TR-v01.00 [i.2], clause 3.3. Signaling overhead and complexity (RRC re-configuration, mobility reporting and O-CU reconfiguration messages) can be further reduced by beam grouping in which case beams with similar mobility characteristics comprise a beam group (e.g., group 1: low mobility pedestrian area, group 2: high mobility street). Mobility reports consist of aggregated mobility KPI/PMs (e.g., number of too early HOs, number of too late HOs, number of HO to wrong cell) or individual failure reports with root cause (e.g., too early HO, too late HO, HO to wrong cell) or a combination of the two. Reports are sent per each SSB beam or SSB beam group towards each neighbor cell. Individual mobility failure reports will also be reported per UE to allow UE or UE group-based optimization (besides beam or beam group specific reporting). While aggregated mobility KPIs/PMs are used for slow adaptations (e.g., 5 min), individual failure reports are used for faster adaptations (e.g., 100 ms) or for AI/ML based analysis of failure patterns. Measurement reporting periodicity and measurement type are configurable on a per cell basis considering the tradeoff between gain in mobility performance and associated signaling overhead. Mobility KPIs and failure events are forwarded from the O-CU to the Near-RT RIC, and the Near-RT RIC configures the CIO and the measurement reporting in the O-CUs. CIOs might be beam- or beam group-based and can also be configurable per UE group (e.g., UE type, UE mobility or UE mode such as energy saving mode). - -While AI/ML based approaches are not mandated, AI/ML methods/models can be used i) to build beam groups, to ii) decide on cell individual measurement configuration, to iii) detect changes in mobility characteristics (e.g., traffic jam) that trigger optimization, to iv) group UEs in UE groups as well as v) for the bMRO optimization algorithm itself to calculate the optimal cell individual offsets. In case of dynamic beam pattern optimization, relevant mMIMO beam pattern information shall be available at the Near-RT RIC, e.g., mobility reports might indicate a specific beam pattern. - -The context of Near-RT RIC beam-based mobility robustness optimization – model training and beam grouping is captured in table 4.4.3.2-1. - -**Table 4.4.3.2-1: Near-RT RIC beam-based mobility robustness optimization – model training and beam grouping** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To obtain beam pattern optimization in case of Grid-of-Beam optimization, to train the ML models and to decide on the beam grouping. | | -| Actors and Roles | SMO, Near-RT RIC, E2 node (O-CU) | | -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - O1 and E2 interface connectivity are established.
| | -| Pre-conditions |
  • - Network is operational with default configuration.
  • - (optional) OAM functions have configured bMRO targets in Near-RT RIC through O1 interface.
  • - OAM functions have configured baseline mobility parameters in O-CUs through O1 interface.
  • - O-CUs support reporting of beam-based mobility performance and/or instantaneous mobility failure event reporting.
  • - Near-RT RIC has access to the beam-based mobility performance and/or failure reporting from the E2 node.
| | -| Begins when | Operator specified trigger condition or event is satisfied. | | -| Step 1 (M) | OAM provides ML model to the Near-RT RIC via O1 or O2 interface (e.g., to perform beam grouping, to identify a change in mobility characteristics, to derive optimized mobility reporting configuration and/or to calculate the optimized mobility settings). | | -| Step 2 (M) | Near-RT RIC subscribes to cell change configuration reports from E2 node (O-CU) to obtain mMIMO beam pattern information. | | -| Step 3 (M) | Near-RT RIC obtains cell change configuration reports from E2 node (O-CU) including mMIMO beam pattern information. | | -| Step 4 (M) | Near-RT RIC subscribes to beam based mobility performance and failure reporting via E2 interface. | | -| Step 5 (M) | Near-RT RIC obtains to beam based mobility performance and failure reporting via E2 interface. | | -| Step 6 (M) | Near-RT RIC performs model training. | | -| Step 7 (M) | Near-RT RIC obtains to beam based mobility performance and failure reporting via E2 interface. | | -| Step 8 (M) | Near-RT RIC performs AI/ML based beam grouping algorithm to group beams with similar mobility characteristics based on received mobility reports. | | -| Step 9 (M) | Near-RT RIC generates beam grouping policy message and send policy message to O-CUs via E2 interfaces. | | -| Exceptions | None identified. | | -| Post Conditions | None identified. | | -| Traceability | REQ-Near-RT-RIC-TS-FUN1,
REQ-Near-RT-RIC-TS-FUN2,
REQ-E2-MM-FUN1,
REQ-E2-MM-FUN4,
REQ-E2-MM-FUN5,
REQ-E2-MM-FUN7,
REQ-E2-MM-FUN8 | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "SMO" #gold - Participant SMO as "Operator/SMO" - Participant NON as "Non-RT RIC" -end box - -Box "O-RAN" #lightpink - -``` - -``` - -Participant NearRTRIC as "Near-RT RIC" -Participant ORANnodes as "E2 Nodes" -End box - -group AI/ML Model Training - SMO -> NearRTRIC: <> Initialize/Provide ML Model - NearRTRIC -> ORANnodes: <> RIC SUBSCRIPTION REQUEST (cell configuration report) - ORANnodes -> NearRTRIC: <> RIC INDICATION (cell configuration) - Hnote over NearRTRIC - mMIMO Beam Pattern Information is available - Endhnote - NearRTRIC -> ORANnodes: <> RIC SUBSCRIPTION REQUEST (mobility reports) - ORANnodes -> NearRTRIC: <> RIC INDICATION (mobility reports) - NearRTRIC -> NearRTRIC: AI/ML model training -end - -group Beam grouping - ORANnodes -> NearRTRIC: <> RIC INDICATION (mobility reports) - NearRTRIC -> NearRTRIC: AI/ML model inference(beam grouping) - NearRTRIC -> ORANnodes: <> RIC SUBSCRIPTION REQUEST (beam grouping policy) -end - -@enduml - -``` - -The flow diagram of the procedure for Near-RT RIC beam-based mobility robustness optimization – model training and initial beam grouping is given in figure 4.4.3.2-1. - -![Sequence diagram showing the procedure for Near RT RIC beam-based mobility robustness optimization. It is divided into two main phases: AI/ML Model Training and Beam grouping. The participants are Operator/SMO, Non-RT RIC, Near-RT RIC, and E2 Nodes. The AI/ML Model Training phase involves the SMO providing an ML model to the Near-RT RIC, which then subscribes to cell configuration and mobility reports from E2 Nodes, receives indications, and performs training. The Beam grouping phase involves the Near-RT RIC performing inference on mobility reports and sending a beam grouping policy back to the E2 Nodes.](ddee3e67e0dfc22e25188fa635a19558_img.jpg) - -``` - -sequenceDiagram - participant Operator/SMO - participant Non-RT RIC - participant Near-RT RIC - participant E2 Nodes - - Note left of Operator/SMO: AI/ML Model Training - Operator/SMO->>Near-RT RIC: 1 <> Initialize/Provide ML Model - Near-RT RIC->>E2 Nodes: 2 <> RIC SUBSCRIPTION REQUEST (cell configuration report) - E2 Nodes-->>Near-RT RIC: 3 <> RIC INDICATION (cell configuration) - Note right of Near-RT RIC: mMIMO Beam Pattern Information is available - Near-RT RIC->>E2 Nodes: 4 <> RIC SUBSCRIPTION REQUEST (mobility reports) - E2 Nodes-->>Near-RT RIC: 5 <> RIC INDICATION (mobility reports) - Near-RT RIC->>Near-RT RIC: 6 AI/ML model training - - Note left of Operator/SMO: Beam grouping - E2 Nodes-->>Near-RT RIC: 7 <> RIC INDICATION (mobility reports) - Near-RT RIC->>Near-RT RIC: 8 AI/ML model inference(beam grouping) - Near-RT RIC->>E2 Nodes: 9 <> RIC SUBSCRIPTION REQUEST (beam grouping policy) - -``` - -Sequence diagram showing the procedure for Near RT RIC beam-based mobility robustness optimization. It is divided into two main phases: AI/ML Model Training and Beam grouping. The participants are Operator/SMO, Non-RT RIC, Near-RT RIC, and E2 Nodes. The AI/ML Model Training phase involves the SMO providing an ML model to the Near-RT RIC, which then subscribes to cell configuration and mobility reports from E2 Nodes, receives indications, and performs training. The Beam grouping phase involves the Near-RT RIC performing inference on mobility reports and sending a beam grouping policy back to the E2 Nodes. - -**Figure 4.4.3.2-1: Procedure for Near RT RIC beam-based mobility robustness optimization – model training and initial beam grouping** - -The context of Near-RT RIC beam-based mobility robustness optimization – model inference and mobility optimization is captured in table 4.4.3.2-2. - -**Table 4.4.3.2-2: Near-RT RIC beam-based mobility robustness optimization – model inference and mobility optimization** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Based on evaluation of mobility performance and failure reporting, identify changes in mobility characteristics and derive optimized mobility settings such as CIO, TTT, T310, etc. to optimize beam-based mobility performance between neighbor cells. | | -| Actors and Roles | SMO, Near-RT RIC, E2 node (O-CU) | | -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - O1 and E2 interface connectivity are established.
  • - ML models are trained, and beam groups are defined.
| | -| Pre-conditions |
  • - Network is operational with default configuration.
  • - (optional) OAM functions have configured bMRO targets in Near-RT RIC through O1 interface.
  • - OAM functions have configured baseline mobility parameters in O-CUs through O1 interface.
  • - Near-RT RIC has up-to-date beam pattern information.
  • - O-CUs support reporting of beam-based mobility performance and/or instantaneous mobility failure event reporting.
  • - Near-RT RIC has access to the beam-based mobility performance and/or failure reporting from the E2 node.
| | -| Begins when | Operator specified trigger condition or event is satisfied. | | -| Step 1 (M) | Near-RT RIC subscribes to beam- or beam-group based mobility performance and/or failure reporting via E2 interface for mobility optimization. | | -| Step 2 (M) | Near-RT RIC subscribes to cell configuration reports via E2 interface to get informed about mMIMO beam pattern changes. | | -| Step 3,4,5,6,7 (M) | SMO may trigger mobility optimization by configuration of a new GoB beam pattern in the E2 node (O-CU). Near-RT RIC obtains the cell configuration from E2 node via E2 interface and detects a mMIMO beam pattern change. Based on obtained mobility reports from E2 nodes, AI/ML model inference in the Near-RT RIC derives an updated beam grouping. Near-RT RIC requests to apply an updated beam grouping policy at E2 node (O-CU). | | -| Step 8 (M) | Alternatively, OAM may trigger mobility optimization by operator specified trigger or a new optimization target. | | -| Step 9 (M) | Near-RT RIC obtains to beam- or beam-group based mobility performance and failure reporting via E2 interface for mobility optimization. | | -| Step 10 (M) | Near-RT RIC performs AI/ML based mobility report analysis to detect a change in mobility characteristics and to trigger reconfiguration of mobility reporting and mobility parameter settings. | | -| Step 11 (M) | Near-RT RIC subscribes to updated beam- or beam-group based mobility performance and failure reporting via E2 interface. | | -| Step 12 (M) | Near-RT RIC obtains to beam- or beam-group based mobility performance and failure reporting via E2 interface. | | -| Step 13 (M) | Near-RT RIC performs mobility robustness optimization to update mobility parameter settings. | | -| Step 14 (M) | Near-RT RIC requests to apply an updated beam- or beam-group based mobility parameter policy (e.g., CIO, TTT, T310, etc.) at E2 node (O-CU). | | -| Ends when | Operator specified trigger condition or event is satisfied. | | -| Exceptions | None identified. | | -| Post Conditions | Near-RT RIC monitors the performance of mobility robustness optimization in the Near-RT RIC and initiates ML model retraining if required. | | -| Traceability | REQ-Near-RT-RIC-TS-FUN1,
REQ-Near-RT-RIC-TS-FUN2,
REQ-Near-RT-RIC-TS-FUN3,
REQ-E2-MM-FUN1,
REQ-E2-MM-FUN4,
REQ-E2-MM-FUN5,
REQ-E2-MM-FUN7,
REQ-E2-MM-FUN8 | | - -``` - -@startuml -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "SMO" #gold - Participant SMO as "Operator/SMO" - Participant NON as "Non-RT RIC" -end box - -Box "O-RAN" #lightpink - Participant NearRTRIC as "Near-RT RIC" - Participant ORANnodes as "E2 Nodes" -End box - -group OUTER LOOP CONTROL - NearRTRIC -> ORANnodes: <> RIC SUBSCRIPTION REQUEST (mobility reports) - NearRTRIC -> ORANnodes: <> RIC SUBSCRIPTION REQUEST (cell configuration report) - group alt 1 - SMO -> ORANnodes: <> Optimization Trigger:\nNew GoB configuration - ORANnodes -> NearRTRIC: <> RIC INDICATION (cell configuration) - Hnote over NearRTRIC - mMIMO Beam Pattern Change - Endhnote - ORANnodes -> NearRTRIC: <> RIC INDICATION (mobility reports) - NearRTRIC -> NearRTRIC: AI/ML model inference (beam grouping) - NearRTRIC -> ORANnodes: <> RIC SUBSCRIPTION REQUEST (beam grouping policy) - end - group alt 2 - SMO -> NearRTRIC: <> Optimization Trigger:\nNew optimization target - end - group INNER LOOP CONTROL - ORANnodes -> NearRTRIC: <> RIC INDICATION (mobility reports) - NearRTRIC -> NearRTRIC: AI/ML model inference (optimization trigger) - Hnote over NearRTRIC - Change in mobility characteristics - Endhnote - NearRTRIC -> ORANnodes: <> RIC SUBSCRIPTION REQUEST (mobility reports) - ORANnodes -> NearRTRIC: <> RIC INDICATION (mobility reports) - NearRTRIC -> NearRTRIC: Mobility Robustness Optimization - Hnote over NearRTRIC - Update mobility parameters - Endhnote - NearRTRIC -> ORANnodes: <> RIC SUBSCRIPTION REQUEST (mobility parameter policy) - end -end - -group Performance Monitoring - NearRTRIC -> ORANnodes: <> RIC SUBSCRIPTION REQUEST (mobility reports) - ORANnodes -> NearRTRIC: <> RIC INDICATION (mobility reports) - NearRTRIC -> NearRTRIC: Performance monitoring and evaluation - NearRTRIC -> NearRTRIC: Model retraining and update -end - -@enduml - -``` - -The flow diagram of the procedure for Near-RT RIC beam-based mobility robustness optimization – optimization trigger, model inference and mobility optimization is given in figure 4.4.3.2-2. - -![Sequence diagram showing the procedure for Near-RT RIC beam-based mobility robustness optimization. It involves SMO (Operator/SMO, Non-RT RIC) and O-RAN (Near-RT RIC, E2 Nodes) components. The process includes Outer Loop Control, Inner Loop Control, and Performance Monitoring phases with various RIC messages and model inferences.](e22af684d8e56d4c61e61bb5ddac1087_img.jpg) - -``` - -sequenceDiagram - participant SMO as Operator/SMO - participant NonRT as Non-RT RIC - participant NearRT as Near-RT RIC - participant E2 as E2 Nodes - - rect rgb(255, 255, 255) - Note over NearRT, E2: OUTER LOOP CONTROL - NearRT->>E2: 1 <> RIC SUBSCRIPTION REQUEST (mobility reports) - NearRT->>E2: 2 <> RIC SUBSCRIPTION REQUEST (cell configuration report) - - rect rgb(240, 240, 240) - Note over SMO, E2: alt 1 - SMO->>NearRT: 3 <> Optimization Trigger: New GoB configuration - E2->>NearRT: 4 <> RIC INDICATION (cell configuration) - Note over NearRT, E2: mMIMO Beam Pattern Change - E2->>NearRT: 5 <> RIC INDICATION (mobility reports) - Note right of NearRT: 6 AI/ML model inference (beam grouping) - NearRT->>E2: 7 <> RIC SUBSCRIPTION REQUEST (beam grouping policy) - end - - rect rgb(240, 240, 240) - Note over SMO, NearRT: alt 2 - SMO->>NearRT: 8 <> Optimization Trigger: New optimization target - end - end - - rect rgb(255, 255, 255) - Note over NearRT, E2: INNER LOOP CONTROL - E2->>NearRT: 9 <> RIC INDICATION (mobility reports) - Note right of NearRT: 10 AI/ML model inference (optimization trigger) - Note over NearRT, E2: Change in mobility characteristics - NearRT->>E2: 11 <> RIC SUBSCRIPTION REQUEST (mobility reports) - E2->>NearRT: 12 <> RIC INDICATION (mobility reports) - Note right of NearRT: 13 Mobility Robustness Optimization - Note over NearRT, E2: Update mobility parameters - NearRT->>E2: 14 <> RIC SUBSCRIPTION REQUEST (mobility parameter policy) - end - - rect rgb(255, 255, 255) - Note over NearRT, E2: Performance Monitoring - NearRT->>E2: 15 <> RIC SUBSCRIPTION REQUEST (mobility reports) - E2->>NearRT: 16 <> RIC INDICATION (mobility reports) - Note right of NearRT: 17 Performance monitoring and evaluation - Note right of NearRT: 18 Model retraining and update - end - -``` - -Sequence diagram showing the procedure for Near-RT RIC beam-based mobility robustness optimization. It involves SMO (Operator/SMO, Non-RT RIC) and O-RAN (Near-RT RIC, E2 Nodes) components. The process includes Outer Loop Control, Inner Loop Control, and Performance Monitoring phases with various RIC messages and model inferences. - -**Figure 4.4.3.2-2: Procedure for Near-RT RIC beam-based mobility robustness optimization – optimization trigger, model inference and mobility optimization** - -#### 4.4.3.3 MU-MIMO optimization - -The context of MU-MIMO optimization is captured in table 4.4.3.3-1. - -**Table 4.4.3.3-1: MU-MIMO optimization** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | MU-MIMO optimization using Near-RT RIC control loop. | | -| Actors and Roles | Near-RT RIC: Configures E2 nodes' measurements, collects data from E2 nodes, performs MU-MIMO optimization function, and sends MIMO information to E2 nodes.
E2 nodes: Report measurements to Near-RT RIC and execute received MU-MIMO information. | | -| Assumptions | E2 connectivity is established between Near-RT RIC and E2 nodes.
Network is operational. | | -| Pre-conditions | All relevant functions and components are instantiated. MU-MIMO optimization xApp is deployed with initial configuration.
All relevant subscriptions established on E2 interface. | | -| Begins when | Operator specified trigger condition or event is satisfied. | | -| Step 1 (M) | Near-RT RIC requests cell and UE capabilities and configuration information from E2 node (O-CU). | | -| Step 2 (M) | Near-RT RIC obtains cell and UE capabilities and configuration information from E2 node (O-CU). | | -| Step 3 (M) | Near-RT RIC requests UE connections and RRC states information from E2 node (O-CU). | | -| Step 4 (M) | Near-RT RIC obtains UE connections and RRC states information from E2 node (O-CU). | | -| Step 5 (M) | Near-RT RIC requests reference signals and resource allocation information from E2 node (O-DU). | | -| Step 6 (M) | Near-RT RIC obtains reference signals and resource allocation information from E2 node (O-DU). | | -| Step 7 (M) | Near-RT RIC requests channel measurement and reporting configuration information from E2 node (O-DU). | | -| Step 8 (M) | Near-RT RIC obtains channel measurement and reporting configuration information from E2 node (O-DU). | | -| Step 9 (O) | Near-RT RIC may configure reference signals. | | -| Step 10 (O) | Near-RT RIC may configure channel measurement and reporting. | | -| Step 11 (M) | Near-RT RIC requests served radio bearers configuration information from E2 node (O-CU). | | -| Step 12 (M) | Near-RT RIC requests traffic and channel information from E2 nodes (O-CU, O-DU). | | -| Step 13 (M) | (Start of outer loop control)
Near-RT RIC obtains UE connections and RRC states update from E2 node (O-CU). | | -| Step 14 (M) | Near-RT RIC obtains reference signals and resource allocation update from E2 node (O-CU). | | -| Step 15 (M) | Near-RT RIC obtains channel measurement and reporting configuration update from E2 Node (O-CU) | | -| Step 16 (M) | Near-RT RIC obtains DRB/SRB configuration information from E2 node (O-CU). | | -| Step 17 (O) | Near-RT RIC coordinates scheduling control of active DRB/SRB with E2 node (O-DU). | | -| Step 18 (M) | (Start of inner loop control)
Near-RT RIC obtains traffic and channel information from E2 nodes (O-CU, O-DU). | | -| Step 19 (M) | Near-RT RIC uses the collected information to estimate channels and select UE groupings per ranges of frequency and time resources. | | -| Step 20 (M) | Near-RT RIC calculates scheduling and MIMO parameters (MCS and precoding coefficients for each selection of UEs). | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 21 (M) | Near-RT RIC sends scheduling and optimized MIMO parameters per slot per UE to E2 node (O-DU).
Steps 18 to Step 21 may repeat. (End of inner loop control) | | -| Step 22 (M) | E2 node (O-DU) schedules transmissions using the parameters received from the Near-RT RIC. | | -| Step 23 (O) | Near-RT RIC sends updated reference signals configuration to E2 node (O-DU). | | -| Step 24 (O) | Near-RT RIC sends updated DL channel measurement and reporting configuration to E2 node (O-DU).
Step 13 to Step 24 may repeat. (End of outer loop control) | | -| Ends when | MU-MIMO optimization is deactivated. | | -| Exceptions | None identified. | | -| Post Conditions | The E2 nodes operate using the newly received parameters. | | -| Traceability | REQ-E2-MM-FUN1,
REQ-E2-MM-FUN2,
REQ-E2-MM-FUN5,
REQ-E2-MM-FUN11,
REQ-E2-MM-FUN12,
REQ-E2-MM-FUN13,
REQ-E2-MM-FUN14,
REQ-E2-MM-FUN15 | | - -``` - -@startuml -skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 -Autonumber - -Box "O-RAN" #lightpink - Participant NearRTRIC as "Near-RT RIC" - Participant OCU as "O-CU" - Participant ODU as "O-DU" -End box - -NearRTRIC->>OCU: <> Request cell and UE capabilities and configuration information -OCU->>NearRTRIC: <> Cell and UE capabilities and configuration information -NearRTRIC->>OCU: <> Request UE connections and RRC states information -OCU->>NearRTRIC: <> UE connections and RRC states information -NearRTRIC->>ODU: <> Request reference signals and resource allocation configuration information -ODU->>NearRTRIC: <> Reference signals and resource allocation configuration information -NearRTRIC->>ODU: <> Request channel measurement and reporting configuration information -ODU->>NearRTRIC: <> Channel measurement and reporting configuration information - -group #white opt - NearRTRIC->>ODU: <> Configure reference signals - NearRTRIC->>ODU: <> Configure channel measurement and reporting -end - -NearRTRIC->>OCU: <> Request Served Radio Bearers configuration information -NearRTRIC->>ODU: <> Request traffic and channel information - -group #white MU-MIMO Optimization Loop - OCU->>NearRTRIC: <> UE states and RRC connections update - ODU->>NearRTRIC: <> Reference signals and resource allocation configuration update - ODU->>NearRTRIC: <> Channel measurement and reporting configuration update - OCU->>NearRTRIC: <> DRB/SRB configuration information - group opt - NearRTRIC<->>ODU: <> Coordinate scheduling control of active DRB/SRB - end -end - -``` - -``` -end -group #white Scheduling and MIMO Parameters Calculation Loop - ODU->NearRTRIC: <> Traffic and channel information - NearRTRIC->NearRTRIC: UE selections and Channel estimation - NearRTRIC->NearRTRIC: Scheduling and MIMO parameters calculations - NearRTRIC->ODU: <> Scheduling and optimized MIMO parameters per slot per UE - ODU->ODU: Schedule transmissions using\n received parameters -end -group opt - NearRTRIC->ODU: <> Updated reference signal configuration - NearRTRIC->ODU: <> Updated channel measurement and reporting configuration -end -end@enduml -``` - -The flow diagram of the MU-MIMO optimization is given in figure 4.4.3.3-1. - -![Sequence diagram showing MU-MIMO optimization flow between Near-RT RIC, O-CU, and O-DU. The diagram includes message exchanges for cell/UE capabilities, UE connections, reference signals, channel measurements, and radio bearer configurations. It features two loops: 'MU-MIMO Optimization Loop' and 'Scheduling and MIMO Parameters Calculation Loop'. The O-DU performs scheduling based on received parameters.](8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC - participant O-CU - participant O-DU - - Note right of Near-RT RIC: O-RAN - Near-RT RIC->>O-CU: 1 «E2» Request cell and UE capabilities and configuration information - O-CU-->>Near-RT RIC: 2 «E2» Cell and UE capabilities and configuration information - Near-RT RIC->>O-CU: 3 «E2» Request UE connections and RRC states information - O-CU-->>Near-RT RIC: 4 «E2» UE connections and RRC states information - Near-RT RIC->>O-CU: 5 «E2» Request reference signals and resource allocation configuration information - O-CU-->>Near-RT RIC: 6 «E2» Reference signals and resource allocation configuration information - Near-RT RIC->>O-CU: 7 «E2» Request channel measurement and reporting configuration information - O-CU-->>Near-RT RIC: 8 «E2» Channel measurement and reporting configuration information - - opt - Near-RT RIC->>O-DU: 9 «E2» Configure reference signals - Near-RT RIC->>O-DU: 10 «E2» Configure channel measurement and reporting - end - - Near-RT RIC->>O-CU: 11 «E2» Request Served Radio Bearers configuration information - Near-RT RIC->>O-DU: 12 «E2» Request traffic and channel information - - loop MU-MIMO Optimization Loop - Near-RT RIC->>O-CU: 13 «E2» UE states and RRC connections update - Near-RT RIC->>O-CU: 14 «E2» Reference signals and resource allocation configuration update - Near-RT RIC->>O-CU: 15 «E2» Channel measurement and reporting configuration update - Near-RT RIC->>O-CU: 16 «E2» DRB/SRB configuration information - - opt - Near-RT RIC->>O-DU: 17 «E2» Coordinate scheduling control of active DRB/SRB - end - - loop Scheduling and MIMO Parameters Calculation Loop - Near-RT RIC->>O-CU: 18 «E2» Traffic and channel information - O-CU->>O-CU: 19 UE selections and Channel estimation - O-CU->>O-CU: 20 Scheduling and MIMO parameters calculations - O-CU->>O-DU: 21 «E2» Scheduling and optimized MIMO parameters per slot per UE - O-DU->>O-DU: 22 Schedule transmissions using received parameters - end - - opt - Near-RT RIC->>O-DU: 23 «E2» Updated reference signal configuration - Near-RT RIC->>O-DU: 24 «E2» Updated channel measurement and reporting configuration - end - end - - Note right of Near-RT RIC: O-RAN - -``` - -Sequence diagram showing MU-MIMO optimization flow between Near-RT RIC, O-CU, and O-DU. The diagram includes message exchanges for cell/UE capabilities, UE connections, reference signals, channel measurements, and radio bearer configurations. It features two loops: 'MU-MIMO Optimization Loop' and 'Scheduling and MIMO Parameters Calculation Loop'. The O-DU performs scheduling based on received parameters. - -Figure 4.4.3.3-1: MU-MIMO optimization flow - -#### 4.4.3.4 AI/ML based CSI-RS and DMRS configuration optimization - -This sub-use-case deals with GoB-based massive MIMO transmission (where the sender transmits reference signals for a grid of beams to the receiver), primarily used in FDD systems. - -Based on the relevant configuration by O-CU-CP, the O-DU periodically transmits the channel state information – Reference Signal (CSI-RS) via one or multiple beams per SSB beam that enables UEs to perform channel measurements, estimate the CSI and report the CSI in the uplink to the O-DU, that further enables the O-DU to choose the appropriate UE-specific beamforming - -weights (for transmission in the downlink). This is unlike the non-GoB-based massive MIMO transmission used primarily in TDD systems, which do not involve CSI-based beamforming, but which involve periodic Sounding Reference Signals (SRS) transmission in the uplink by the UE to the O-DU for determining the appropriate UE-specific beamforming weights based on channel reciprocity. Hence, GoB-based massive MIMO transmissions incur a higher overhead due to periodic transmission of CSI-feedback from the UE towards enabling the selection of optimal beamforming weights for the UE. - -Furthermore, based on the relevant configuration by O-CU-CP, the O-DU transmits the Demodulation Reference Signal (DMRS) to each UE that enables the UE to determine the UE-specific beamforming weights to decode the PDSCH (for reception in the downlink), containing the multiplexed MIMO layer data transmissions. The configuration of DMRS plays an important role on the performance of the network, e.g., for a fast-fading channel, an additional DMRS symbol can be provided per slot trading off higher overhead; for higher traffic-load, configuration type 2 can be used trading off frequency domain density; for low-latency KPI requirements, mapping type B can be used, etc. - -In this context, the sub-use-case describes a method to: - -- 1) if necessary, update/modify the configuration of CSI-RS transmission (i.e., number of ports, port allocation over REs in a RB, transmission periodicity, transmission density/number of CSI-RS signal per RB, CSI-RS port to physical antenna port mapping/beamforming weights, number of CSI-RS beams per SS beam, etc.) and configuration of CSI-feedback (i.e., sub-band size, etc.) at non-real time (e.g., every 1 hr) based on the distribution of UE channel and traffic load. -- 2) if necessary, update/modify UE-specific beams indexes (e.g., PMIs when PMI-based beam management is enabled, P2 beamforming-weights/beam-indexes when P1-P2-based beam management is enabled, etc.) for a sequence of slots (i.e., at near-real time) based on the CSI-feedback received from UEs, etc. -- 3) if necessary, update/modify the configuration of DMRS (i.e., number of OFDM symbols carrying DMRS ports per slot, configuration type, etc.) for a sequence of slots (i.e., at near-real time) based on the relevant RAN state information such as CSI-feedback received from UEs, traffic load, etc. - -Towards achieving the goal, this sub-use-case utilizes the Near-Real-Time RAN Intelligent Controller (Near-RT RIC) and the Service Management Orchestration (SMO)/Non-Real-Time RAN Intelligent Controller (Non-RT RIC) framework of O-RAN ecosystem. - -The SMO/Non-RT RIC framework shall update/modify the configurations of CSI-RS transmissions and CSI-feedback reporting at the E2 nodes (e.g., O-DU). - -The Near-RT RIC shall update/modify the UE-specific GoB-based beams and the DMRS configurations at the E2 nodes (e.g., O-DU) for a sequence of slots. - -Specifically, - -- the SMO/Non-RT RIC framework shall train AI/ML models to solve a joint two-stage optimization problem. In the first stage, the configurations of CSI-RS transmission and CSI-feedback reporting are optimized for each cell. In the second stage, the GoB-based UE-specific beams and the configuration of DMRS are optimized for each cell. -- When the training is completed, the SMO/Non-RT RIC framework shall deploy the AI/ML model trained to optimize GoB-based UE-specific beams and DMRS configurations to the Near-RT RIC. -- After that, based on the network dynamics, the SMO/Non-RT RIC framework shall update/modify the configurations of CSI-RS transmissions and CSI-feedback reporting at the E2 nodes (e.g., O-DU). -- Based on the network dynamics and the trained AI/ML model received from the SMO/Non-RT RIC framework, the Near-RT RIC shall update/modify the UE-specific GoB-based beams and the DMRS configurations at the E2 nodes (e.g., O-DU) for a sequence of slots. - -The goal of the optimization is to maximize the target KPIs under the constraints of configuration choices of CSI-RS transmission, CSI-feedback reporting, GoB-based UE-specific beams and DMRS transmission. - -The AI/ML models can exploit the relations of the channel properties and traffic load with the configuration parameters of CSI-RS and DMRS (e.g., relations between doppler-spread and time-domain properties, delay-spread and frequency-domain properties, angular spread and beam directions/indexes, traffic-load and number of ports, etc.) towards maximizing the target KPIs. - -##### 4.4.3.4.1 Entities/resources involved in the use case - -- 1) SMO/Non-RT RIC framework: - -- a) Collect the necessary Configuration (CM) parameters, Performance Measurements (PM), Key Performance Indicators (KPI), and measurement report traces from the E2 nodes (O-CU-CP, O-CU-UP, O-DU, O-eNB) via O1 interface. -- b) Collect the necessary UE-level observation and measurement data from the Near-RT RIC via O1 interface. -- c) Allow the rApp to receive the CMs, PMs, KPIs measurement data (collected via O1) to perform the AI/ML model training towards jointly optimizing i) the configurations of CSI-RS transmission (i.e., number of ports, port allocation over REs in a RB, transmission periodicity, transmission density/number of CSI-RS signal per RB, CSI-RS port to physical antenna port mapping/beamforming weights, etc.) and CSI-feedback reporting (i.e., sub-band size, etc.) which shall be updated/modified in non-real-time and ii) the UE-specific GoB-based beams (i.e., P2 beamforming-weights/beam-indexes when P1-P2-based beam management is enabled, PMI/PMI-RI/PMI-RI-LI when PMI-based beam management is enabled, etc.) and the configurations of DMRS (i.e., configuration type, mapping type, number of symbols carrying DMRS ports per slot, etc.) which shall be updated/modified in near-real-time. -- d) Receive the inferred configurations of CSI-RS transmissions and CSI-feedback reporting from the rApp via R1 interface. -- e) Write/update the optimized configurations of CSI-RS transmissions and CSI-feedback reporting via O1 interface to E2 nodes. -- f) Deploy the trained AI/ML model via O1/O2 interface and/or the enrichment information via A1 interface to the Near-RT RIC to update/modify the UE-specific GoB-based beams and DMRS configurations in near-real-time. - -NOTE: The requirements of SMO/Non-RT RIC framework are under the scope of WG2. - -###### 2) rApps: - -- a) Retrieve the necessary Configuration (CM) parameters, Performance Measurements (PM), Key Performance Indicators (KPI), and measurement report traces pertaining to the E2 nodes and O-RU from the SMO/Non-RT RIC framework via R1 to train AI/ML model. -- b) Train AI/ML model to jointly optimize i) the configurations of CSI-RS transmission and CSI-feedback reporting which shall be updated/modified in non-real-time and ii) the UE-specific GoB-based beams and the DMRS configurations which shall be updated/modified in near-real-time. -- c) Infer the configurations of CSI-RS transmission and CSI-feedback reporting and write/update the inferred configuration to the SMO/Non-RT RIC framework via R1. -- d) Write/update the AI/ML model trained to optimize the UE-specific GoB-based beams and the DMRS configurations to the SMO/Non-RT RIC framework via R1. -- e) Monitor the performance of the respective cells. Upon KPI degradation, initiate rollback to the previous version of the AI/ML model, if any, and/or trigger the AI/ML model retraining. -- f) Execute the inference/control loop periodically or on an event-triggered based. - -NOTE: The requirements of rApps are under the scope of WG2. - -###### 3) Near-RT RIC: - -- a) Subscribe and retrieve DL L1 measurements reported by individual UE such as CSI-feedback containing PMI (in the case of closed-loop MIMO transmission mode) or partial channel feedback (in the case of open-loop MIMO transmission mode, which is available as channel matrix, or its corresponding Eigen vectors of the wireless channel between the E2 node and the UE) over the E2 interface from the E2 nodes. -- b) Process, aggregate and report the UE-level data over O1 interface to the SMO/Non-RT RIC framework. -- c) Retrieve AI/ML model via O1/O2 interface and/or enrichment information via A1 interface from the SMO/Non-RT RIC framework and associate them with collected information over E2 interface (such as, CSI-feedback, etc.) towards inferring the slot-specific GoB-based beams/PMIs per UE and slot-specific DMRS configurations. -- d) Write/update the per-UE slot-specific GoB-based beams/PMIs and slot-specific DMRS configurations for a sequence of slots via E2 interface (to O-DU). -- e) Execute the inference/control loop periodically or on an event-triggered based. - -###### 4) E2 nodes: - -- a) Report the desired performance measurements and KPIs, configuration parameters and CM changes, trace reports and measurements to the SMO/Non-RT RIC framework via the O1 interface. -- b) Report the DL L1 measurements reported by individual UE (such as, CSI-feedback, etc.) to the Near-RT RIC via the E2 interface. - -- c) Receive the optimized CSI-RS transmission and CSI-feedback reporting configurations from the SMO/Non-RT RIC framework via O1 interface and apply the configuration on the O-DU which may further exercise the configuration update on the O-RU. -- d) Receive the per-UE slot-specific GoB-based beams/PMIs and slot-specific DMRS configurations for a sequence of slots from the Near-RT RIC via the E2 interface and apply the configuration on the O-DU which may further exercise the configuration update on the O-RU accordingly. - -##### **4.4.3.4.2 Solutions** - -The context of AI/ML based CSI-RS and DMRS configuration optimization is captured in table 4.4.3.4.2-1. - -**Table 4.4.3.4.2-1: AI/ML based CSI-RS and DMRS configuration optimization** - -| Steps | Details | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | Optimizes the configuration parameters of CSI-RS and DMRS | -| Actors and Roles |
  • - SMO/Non-RT RIC framework: Collects performance data and training data, allows rApp to access the data, receives trained AI/ML model from rApp and deploys the trained model to Near-RT RIC, receives inferred configurations of CSI-RS transmission and CSI-feedback reporting from rApp and writes/updates the inferred configurations to E2 nodes.
  • - rApp: Trains AI/ML model to jointly optimize i) the configurations of CSI-RS transmission and CSI-feedback reporting which shall be updated/modified in non-real-time and ii) the UE-specific GoB-based beams and the DMRS configurations which shall be updated/modified in near-real-time. Infers the configurations of CSI-RS transmission and CSI-feedback reporting.
  • - Near-RT RIC: Infers per-UE slot-specific GoB-based beams/PMIs and slot-specific DMRS configurations for a sequence of slots.
  • - E2 nodes and O-RU: Updates CSI-RS transmission and CSI-feedback reporting parameters as per the recommendation received from the SMO/Non-RT RIC framework. Updates UE-specific GoB beamforming weights and DMRS configurations as per the recommendation received from the Near-RT RIC.
| -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - A1, O1 and E2 interface connectivity is established.
  • - A1 policy scope defined.
| -| Pre-conditions |
  • - Network is operational with default configuration.
  • - SMO/Non-RT RIC framework have configured a baseline measurement configuration and the rApp has access to this data.
  • - Near-RT RIC has access to the necessary data related to DL L1 measurements reported by UEs such as CSI-Feedback containing PMI/RI/LI, CSI-RSRP, CSI-SINR, etc. from the E2 node.
  • - SMO/Non-RT RIC framework analyzes the historical data from RAN 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 non-real-time optimization of configurations.
| -| Begins when | SMO/Non-RT RIC framework and/or Near-RT RIC perform data evaluation, determine that CSI-RS and DMRS optimization is required to be initiated or updated and establishes target(s). | -| Step 1-2 (M) |

(Start of outer loop control)

SMO/Non-RT RIC framework collects the necessary configurations, performance indicators, and measurement reports from E2 nodes and O-RUs via O1 interface.

| - -| Steps | Details | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Step 3 (M) | Near-RT RIC collects DL L1 measurements reported by individual UE such as PMI, RI, LI, CQI, CSI-RSRP, CSI-SINR, SS-RSRP, etc. and DL L1, L2 information such as traffic load of individual UE from E2 node periodically or event-triggered. | -| Step 4-5 (M) | Near RT RIC processes, aggregates and reports the UE-level data over O1 interface to the SMO/Non-RT RIC framework. | -| Step 6 (M) | SMO/Non-RT RIC framework collects the target KPIs data. | -| Step 7 (M) | SMO/Non-RT RIC framework pre-processes the data to feed into the rApp. | -| Step 8-9 (M) | rApp trains AI/ML model. | -| Step 10-12 (M) | SMO/Non-RT RIC framework deploys the trained AI/ML model to Near-RT RIC via O1/O2 interface and sends optional A1 enrichment information such as the history of UE-specific GoB-based beams/PMIs. | -| Step 13-14 (M) | (Start of inner loop control)
SMO/Non-RT RIC framework collects observation, measurement data from E2 nodes and feeds the data to rApps. | -| Step 15-16 (M) | rApp infers the configurations of CSI-RS transmission and CSI-feedback reporting and writes/updates the inferred configurations to SMO/Non-RT RIC framework. | -| Step 17-18 (M) | SMO/Non-RT RIC framework writes/updates the configurations of CSI-RS transmission and CSI-feedback reporting at E2 nodes which further exercise the configuration update on the O-RU. | -| Step 19-20 (M) | E2 nodes report the DL L1 measurements reported by individual UE such as PMI, RI, LI, CQI, CSI-RSRP, CSI-SINR, SS-RSRP, etc. and DL L1, L2 information such as traffic load of individual UE to Near-RT RIC. By associating the measurement data received from E2 nodes with the trained AI/ML model received from SMO/Non-RT RIC framework, Near-RT RIC infers the per-UE slot-specific GoB-based beams/PMIs and slot-specific DMRS configurations. | -| Step 21-22 (M) | Near-RT RIC writes/updates the per-UE slot-specific GoB-based beams/PMIs and slot-specific DMRS configurations for a sequence of slots to E2 nodes via E2 interface.
Step 12 to Step 21 may repeat. (End of inner loop control) | -| Step 23-30 (M) | rApps continuously monitors KPIs in respective cells. In case of unsatisfactory performance, it initiates fallback and requests AI/ML model retraining/update. Then, rApp retrains/updates the respective AI/ML model(s).
Step 1 to Step 29 may repeat. (End of outer loop control) | -| Ends when | Non-RT RIC decides to delete the CSI-RS and DMRS optimization AI/ML model and sends the related message or following internal trigger, the Near-RT RIC terminates the UE-specific beams/PMIs and DMRS optimization procedure. | -| Exceptions | None. | -| Post Conditions | Non-RT RIC continues to collect and monitor the CSI-RS and DMRS optimization related measurement data from E2 node. | -| Traceability | REQ-Near-RT-RIC-MM-FUN1,
REQ-Near-RT-RIC-MM-FUN2, | - -| Steps | Details | -|-------|------------------------------------------------------------------------------------------------------------------------------------------------------| -| | REQ-Near-RT-RIC-MM-FUN3,
REQ-Near-RT-RIC-MM-FUN4,
REQ-E2-MM-FUN1,
REQ-E2-MM-FUN2,
REQ-E2-MM-FUN5,
REQ-E2-MM-FUN11,
REQ-E2-MM-FUN16 | - -``` - -@startuml -Box "Personnel" #lightblue - Actor "Operator" as OPERATOR -End box - -Box "Service Management and Orchestration" #gold - Participant "SMO & Non-RT RIC FW" as SMO - Participant "rApps" as NRTRIC -End box - -Box "O-RAN Nodes" #lightpink - Participant "Near-RT RIC" as RTRIC - Participant "E2-Nodes" as E2NODES - Participant "O-RUs" as ORUs -End box - -Autonumber - -group Data Collection and Pre-Processing - ORUs -> E2NODES : <> Observation, Measurement Data Collection - E2NODES -> SMO : <> Observation, Measurement Data Collection - E2NODES -> RTRIC: <> DL L1 measurements (such as PMI, RI, LI, CQI etc.) \nand DL L1, L2 information (such as, traffic load etc.) of individual UE - RTRIC -> RTRIC : Data processing - RTRIC -> SMO : <> Aggregated and processed UE-level Data - OPERATOR -> SMO : Performance KPI Targets - SMO -> SMO : Data Pre-Processing and AI/ML Training Data Generation -end - -group AI/ML Training - SMO -> NRTRIC : <> AI/ML Training Data - NRTRIC -> NRTRIC : AI/ML Training -end - -group Model Deployment - NRTRIC -> SMO : <> Request to deploy trained AI/ML model - SMO -> RTRIC : <>/<> Deploy AI/ML model - SMO --> RTRIC : <> enrichment information -end - -group Inference Generation -group Inference Generation with Non-Real-Time periodicity - E2NODES -> SMO : <> Observation, Measurement Data Collection - SMO -> NRTRIC : <> Model data - NRTRIC ->NRTRIC : AI/ML Inference - -``` - -``` - - NRTRIC -> SMO : <> CSI-RS transmission and \n CSI-feedback reporting - configurations - SMO -> E2NODES : <> CSI-RS transmission and \n CSI-feedback reporting - configurations - E2NODES -> ORUs : <> Updated O-RU Configurations -end -group Inference Generation with Near-Real-Time periodicity - E2NODES ->RTRIC : <> DL L1 measurements (such as PMI, RI, LI, CQI etc.) \nand DL L1, - L2 information (such as, traffic load etc.) of individual UE - RTRIC -> RTRIC : AI/ML Inference - RTRIC -> E2NODES : <> per-UE slot-specific GoB-based beams/PMIs \nand slot-specific - DMRS configurations for a sequence of slots - E2NODES -> ORUs : <> Updated O-RU Configurations -end -end - -group ML Agent Performance Monitoring - ORUs -> E2NODES : <> Data Collection - E2NODES -> SMO : <> KPIs, Measurement Report, Observations - SMO -> NRTRIC : Performance data - NRTRIC -> NRTRIC : Performance Evaluation -group if - NRTRIC -> SMO : <> Default/Fallback decision/CSI and DMRS Configuration - SMO -> E2NODES : <> Default/Fallback CSI and DMRS Configuration - SMO -> NRTRIC : <> Model retraining and update request - NRTRIC -> NRTRIC : AI/ML Re-Training Trigger -end -end -@enduml - -``` - -The overall procedure for CSI-RS and DMRS optimization for mMIMO GoB beamforming use case is given in figure 4.4.3.4.2-1. - -![Sequence diagram showing the overall procedure for CSI-RS and DMRS optimization for mMIMO GoB beamforming use case. The diagram involves Personnel (Operator), Service Management and Orchestration (SMO & Non-RT RIC FW, rApps), and O-RAN Nodes (Near-RT RIC, E2-Nodes, O-RUs).](255efa1d461fc79b4ed367aaec11637f_img.jpg) - -The sequence diagram illustrates the interaction between the Operator, Service Management and Orchestration (SMO & Non-RT RIC FW, rApps), and O-RAN Nodes (Near-RT RIC, E2-Nodes, O-RUs) for CSI-RS and DMRS optimization. The process is divided into several phases: - -- Data Collection and Pre-Processing:** - - The Operator sends **6 Performance KPI Targets** to the SMO. - - The SMO sends **2 «O1» Observation, Measurement Data Collection** to the Near-RT RIC. - - The Near-RT RIC sends **3 «E2» DL L1 measurements (such as PMI, RI, LI, CQI etc.) and DL L1, L2 information (such as, traffic load etc.) of individual UE** to the E2-Nodes. - - The E2-Nodes perform **4 Data processing**. - - The E2-Nodes send **5 «O1» Aggregated and processed UE-level Data** to the Near-RT RIC. - - The Near-RT RIC performs **7 Data Pre-Processing and AI/ML Training Data Generation**. -- AI/ML Training:** - - The SMO sends **8 «R1» AI/ML Training Data** to the rApps. - - The rApps perform **9 AI/ML Training**. -- Model Deployment:** - - The rApps send **10 «R1» Request to deploy trained AI/ML model** to the Near-RT RIC. - - The Near-RT RIC sends **11 «O1»/«O2» Deploy AI/ML model** to the E2-Nodes. - - The E2-Nodes send **12 «A1» enrichment information** to the Near-RT RIC. -- Inference Generation:** - - Inference Generation with Non-Real-Time periodicity:** - - The SMO sends **13 «O1» Observation, Measurement Data Collection** to the Near-RT RIC. - - The Near-RT RIC sends **14 «R1» Model data** to the rApps. - - The rApps perform **15 AI/ML Inference**. - - The rApps send **16 «R1» CSI-RS transmission and CSI-feedback reporting configurations** to the Near-RT RIC. - - The Near-RT RIC sends **17 «O1» CSI-RS transmission and CSI-feedback reporting configurations** to the E2-Nodes. - - The E2-Nodes send **18 «FH» Updated O-RU Configurations** to the O-RUs. - - Inference Generation with Near-Real-Time periodicity:** - - The E2-Nodes send **19 «E2» DL L1 measurements (such as PMI, RI, LI, CQI etc.) and DL L1, L2 information (such as, traffic load etc.) of individual UE** to the Near-RT RIC. - - The Near-RT RIC performs **20 AI/ML Inference**. - - The Near-RT RIC sends **21 «E2» per UE slot-specific GoB-based beams/PMIs and slot-specific DMRS configurations for a sequence of slots** to the E2-Nodes. - - The E2-Nodes send **22 «FH» Updated O-RU Configurations** to the O-RUs. -- ML Agent Performance Monitoring:** - - The E2-Nodes send **23 «FH» Data Collection** to the Near-RT RIC. - - The Near-RT RIC sends **24 «O1» KPIs, Measurement Report, Observations** to the SMO. - - The SMO sends **25 Performance data** to the rApps. - - The rApps perform **26 Performance Evaluation**. - - If ****: - - The rApps send **27 «R1» Default/Fallback decision/CSI and DMRS Configuration** to the Near-RT RIC. - - The Near-RT RIC sends **28 «O1» Default/Fallback CSI and DMRS Configuration** to the E2-Nodes. - - The E2-Nodes send **29 «R1» Model retraining and update request** to the Near-RT RIC. - - The Near-RT RIC sends **30 AI/ML Re-Training Trigger** to the rApps. - -Sequence diagram showing the overall procedure for CSI-RS and DMRS optimization for mMIMO GoB beamforming use case. The diagram involves Personnel (Operator), Service Management and Orchestration (SMO & Non-RT RIC FW, rApps), and O-RAN Nodes (Near-RT RIC, E2-Nodes, O-RUs). - -Figure 4.4.3.4.2-1: The overall procedure for CSI-RS and DMRS optimization for mMIMO GoB beamforming use case - -### 4.4.4 Required data - -This clause elaborates the Near-RT RIC and the E2 node capabilities necessary for implementation of the massive MIMO optimization use case. The requirements are specified in clause 5. - -#### 4.4.4.1 Control over E2 - -##### *Non-Grid-of-Beams beamforming optimization* - -**Table 4.4.4.1-1: Output data** - -| Output data | | | | | | -|-------------|--------------------|---------------------------------------------------|-------|-----------------------------|------------------------| -| Interface | Source → Target | Name/Description | Units | Config. Period, granularity | New or existing config | -| E2 | Near-RT RIC → O-DU | Non-GoB control/policy (non-GoB beamforming mode) | index | ~per N x 100ms, per UE | New | - -##### *Beam-based mobility robustness optimization* - -**Table 4.4.4.1-2: Output data** - -| Output data | | | | | | -|-------------|--------------------|-------------------------------------------------------|-------|-----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------| -| Interface | Source → Target | Name/Description | Units | Config. Period, granularity | New or existing config | -| E2 | Near-RT RIC → O-CU | Cell Individual Offset (CIO) to a given neighbor cell | dB | ~per N x 100ms, per beam or beam group, per UE group (optional) | As specified in 3GPP TS 38.331 [18], clauses 5.3.5 and 5.5.4

New: beam or beam group, per UE group configuration of CIOs | -| E2 | Near-RT RIC → O-CU | Time To Trigger (TTT) | ms | ~per N x 100ms, per beam or beam group, per UE group (optional) | As specified in 3GPP TS 38.331 [18], clauses 5.3.5 and 6.3.2

New: beam or beam group, per UE group configuration of TTTs | -| E2 | Near-RT RIC → O-CU | UE Timer 310 (T310) | ms | ~per N x 100ms, per beam or beam group, per UE group (optional) | As specified in 3GPP TS 38.331 [18], clauses 5.8.8 and 6.3.2

New: beam or beam group, per UE group configuration of TTTs | - -##### *MU-MIMO optimization* - -**Table 4.4.4.1-3: Output data** - -| Output data | | | | | | -|-------------|--------------------|----------------------------|---------|-----------------------------|---------------------------------------------------| -| Interface | Source → Target | Name/Description | Units | Config. Period, granularity | New or existing config | -| E2 | Near-RT RIC → O-DU | CSI resource configuration | message | ~per N x 100ms, per UE | As specified in 3GPP TS 38.331 [18], clause 6.3.2 | - -| Output data | | | | | | -|-------------|--------------------|------------------------------------|---------|---------------------------------|---------------------------------------------------| -| Interface | Source → Target | Name/Description | Units | Config. Period, granularity | New or existing config | -| E2 | Near-RT RIC → O-DU | CSI report configuration | message | ~ per N x 100ms, per UE | As specified in 3GPP TS 38.331 [18], clause 6.3.2 | -| E2 | Near-RT RIC → O-DU | SRS resource configuration | message | ~ per N x 100ms, per UE | As specified in 3GPP TS 38.331 [18], clause 6.3.2 | -| E2 | Near-RT RIC → O-DU | PDSCH configuration | message | ~ per N x 100ms, per UE per BWP | As specified in 3GPP TS 38.331 [18], clause 6.3.2 | -| E2 | Near-RT RIC → O-DU | MU-MIMO parameters per slot per UE | message | ~ per Nx1ms, per slot per SMG | New | - -##### CSI-RS and DMRS optimization - -Table 4.4.4.1-4: Output data - -| Output data | | | | | | -|-------------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|-----------------------------|------------------------------------------------------------------------------------------| -| Interface | Source → Target | Name/Description | Units | Config. Period, granularity | New or existing config | -| E2 | Near-RT RIC → O-DU | Per-UE slot-specific GoB-based beam configuration (i.e., P2 beamforming-weights/beam-index, PMI, RI, LI, etc.) and slot-specific DMRS configuration (i.e., number of OFDM symbols carrying a DMRS port per slot, mapping type, configuration type, etc.) for a sequence of slots | message | ~per N x 100ms | As specified in 3GPP TS 38.912 [46], clause 8.2.1.6, 3GPP TS 38.211 [45], clause 7.4.1.1 | - -#### 4.4.4.2 UE context information from E2 nodes - - - -Table 4.4.4.2-1: Input data - -| Input data | | | | | | | -|------------|--------------------|------------------|-------|-------------------------------|-------------------------------------------------------------|-------------------------| -| Interface | Source → Target | Name/Description | Units | Reporting Period, granularity | New or existing definition, Existing Specification (Clause) | Applicable sub-features | -| E2 | O-DU → Near-RT RIC | UE ID | | ~per N x 100ms, per UE | As specified in O-RAN.WG3.E2SM-v02.00 [25]
New reporting | Non-GoB | - -| Input data | | | | | | | -|------------|--------------------|-------------------------------------|---------|-------------------------------|-------------------------------------------------------------------------------------------------------------|-------------------------| -| Interface | Source → Target | Name/Description | Units | Reporting Period, granularity | New or existing definition, Existing Specification (Clause) | Applicable sub-features | -| E2 | O-DU → Near-RT RIC | SRS configuration periodicity | slots | ~per N x 100ms, per UE | As specified in 3GPP TS 38.331 [18], clause 6.3.2
"SRS-Config
>periodicityAndOffset"
New reporting | Non-GoB | -| E2 | O-DU → Near-RT RIC | CSI measurement configuration | message | ~per N x 100ms, per UE | As specified in 3GPP TS 38.331 [18], clause 6.3.2
New reporting | mUMO | -| E2 | O-DU → Near-RT RIC | SRS configuration | message | ~per N x 100ms, per UE | As specified in O-RAN.WG3.E2SM-RC-R003-v05.00 [42], clause 8.1.1.17 | mUMO | -| E2 | O-DU → Near-RT RIC | BWP configurations | message | ~per N x 100ms, per UE | As specified in 3GPP TS 38.331 [18], clause 6.3.2
New reporting | mUMO | -| E2 | O-DU → Near-RT RIC | PDSCH of serving cell configuration | message | Infrequent, per UE | As specified in 3GPP TS 38.331 [18], clause 6.3.2
New reporting | mUMO | - -<From O-CU> - -Table 4.4.4.2-2: Input data - -| Input data | | | | | | | -|------------|--------------------|----------------------------------------|---------|-------------------------------|-----------------------------------------------------------------------------------------------------------|-------------------------| -| Interface | Source → Target | Name/Description | Units | Reporting Period, granularity | New or existing definition, Existing Specification (Clause) | Applicable sub-features | -| E2 | O-CU → Near-RT RIC | UE ID and cell ID of RRC connected UEs | | ~per N x 100ms, per UE | As specified in O-RAN.WG3.E2SM-RC-R003-v05.00 [42] | mUMO | -| E2 | O-CU → Near-RT RIC | RRC state change | | ~per N x 100ms, per UE | As specified in O-RAN.WG3.E2SM-RC-R003-v05.00 [42], clause 9.3.37 | mUMO | -| E2 | O-CU → Near-RT RIC | MeasGapConfig | message | ~per N x 100ms, per UE | As specified in 3GPP TS 38.331 [18], clause 6.3.2
New reporting | mUMO | -| E2 | O-CU → Near-RT RIC | Served radio bearer configuration | message | ~per N x 100ms, per UE | As specified in 3GPP TS 38.473 [21], clause 9.2.2.1
3GPP TS 38.331 [18], clause 6.3.2
New reporting | mUMO | -| E2 | O-CU → Near-RT RIC | DRX configuration | message | ~per N x 100ms, per UE | As specified in 3GPP TS 38.331 [18], clause 6.3.2
New reporting | mUMO | -| E2 | O-CU → Near-RT RIC | UE capabilities | message | Infrequent, per UE | As specified in 3GPP TS 38.331 [18], clause 6.3.2
Existing reporting | mUMO | - -#### 4.4.4.3 Measurements from E2 nodes - - - -Table 4.4.4.3-1: Input data - -| Input data | | | | | | | -|------------|--------------------|-------------------------------------------------------------------------------|--------------|-------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Interface | Source → Target | Name/Description | Units | Reporting Period, granularity | New or existing definition, Existing Specification (Clause) | Applicable sub-features | -| E2 | O-DU → Near-RT RIC | RSRP L1 measurement (based on synchronization signal) | dBm | ~per N x 100ms, per UE | As specified in 3GPP TS 38.133 [26], clause 10.1.6
3GPP TS 38.215 [27], clause 5.1.1
New reporting | Non-GoB L1/L2 BM | -| E2 | O-DU → Near-RT RIC | DL L1 SINR measurement (based on synchronization signal) | dB | ~per N x 100ms, per UE | As specified in 3GPP TS 38.133 [26], clause 10.1.16
3GPP TS 38.215 [27], clause 5.1.5
New reporting | Non-GoB L1/L2 BM | -| E2 | O-DU → Near-RT RIC | UL SRS RSRP measurement | dBm | ~per N x 100ms, per UE | As specified in 3GPP TS 38.133 [26], clause 13.3.1
3GPP TS 38.215 [27], clause 5.2.5
New reporting | Non-GoB | -| E2 | O-DU → Near-RT RIC | Average DL UE throughput in gNB with associated non-GoB BF mode and MIMO mode | Kb/s + index | (non real-time for training) | As specified in 3GPP TS 28.552 [6], clause 5.1.1.3.1
New reporting
New component is associated non-GoB BF mode index and MIMO mode (SU/MU) | Non-GoB | -| E2 | O-DU → Near-RT RIC | Average UL UE throughput in gNB with associated non-GoB BF mode and MIMO mode | Kb/s + index | (non real-time for training) | As specified in 3GPP TS 28.552 [6], clause 5.1.1.3.3
New reporting
New component is associated non-GoB BF mode index and MIMO mode (SU/MU) | Non-GoB | -| E2 | O-DU → Near-RT RIC | SRS samples | | ~per N x 1ms, per SRS RE per antenna port | As specified in O-RAN.WG4.CUS.0-R003-v15 [34], clause 8.3.5.2
New reporting | mUMO | -| E2 | O-DU → Near-RT RIC | DL channel quality information (PMI, RI, CQI) | message | ~per N x 10ms, per UE | As specified in 3GPP TS 38.212 [43], clause 6.3
New reporting | mUMO | -| E2 | O-DU → Near-RT RIC | HARQ ACK/NACK/DT X counts | count | ~per N x 10ms, per UE | As specified in 3GPP TS 38.212 [43], clause 6.3
New reporting | mUMO | -| E2 | O-DU → Near-RT RIC | DL RLC buffer status | count | ~per N x 1ms, per DRB per UE | As specified in 3GPP TS 25.321 [41], clause 8.2.2
New reporting | mUMO | - -| Input data | | | | | | | -|------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------|---------|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------|--------------------------| -| Interface | Source → Target | Name/Description | Units | Reporting Period, granularity | New or existing definition, Existing Specification (Clause) | Applicable sub-features | -| E2 | O-DU → Near-RT RIC | MAC timestamped slot number | message | ~per N x 100ms | As specified in 3GPP TS 38.473 [21], clause 9.3.1.171
New reporting | mUMO | -| E2 | O-DU → Near-RT RIC | CSI-feedback, such as cell-specific and CSI-RS-beam-index-specific RSRP, RSRQ, SINR, etc. and SSB-beam-index-specific-RSRP per UE | message | ~per N x 100ms, per UE | As specified in 3GPP TS 38.912 [46], clause 8.2.1.6.3, 3GPP TS 38.331 [18], clause 5.5.5.2, 3GPP TS 38.215 [27], clause 5.1 | CSI and DMRS opt. | -| E2 | O-DU → Near-RT RIC | CSI-feedback, such as precoding matrix indication (PMI), rank indication (RI), layer indication (LI) per UE | message | ~per N x 100ms, per UE | As specified in 3GPP TS 38.912 [46], clause 8.2.1.6.3, 3GPP TS 38.214 [15], clause 5.2 | CSI and DMRS opt. | -| E2 | O-DU → Near-RT RIC | Information about Quasi-Co-Location (QCL) type between SSB and CSI-RS and between CSI-RS and DMRS per UE per cell | message | ~per N x 100ms, per UE | As specified in 3GPP TS 38.214 [15], clause 5.1.5 | CSI and DMRS opt. | -| E2 | O-DU → Near-RT RIC | Traffic load and radio resource utilization per UE per cell | message | ~per N x 100ms, per cell | As specified in 3GPP TS 28.552 [6] | CSI and DMRS opt. | -| E2 | O-DU → Near-RT RIC | DRB-specific PDCP SDU data volume, DRB-specific RLC buffer occupancy and HARQ-specific Transport Block Size volume per UE | message | ~per N x 100ms, per UE | As specified in O-RAN WG3 E2SM-KPM [36], O-RAN WG3 E2SM-RC [37] | CSI and DMRS opt. | - -<From O-CU> - -Table 4.4.4.3-2: Input data - -| Input data | | | | | | | -|------------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|----------------------------------------------------------------|------------------------------------------------------------------|-------------------------| -| Interface | Source → Target | Name/Description | Units | Reporting Period, granularity | New or existing definition, Existing Specification (Clause) | Applicable sub-features | -| E2 | O-CU → Near-RT RIC | Number of too early HOs to a given neighbor cell | count | ~ 1 min, per beam or beam group | As specified in 3GPP TS 28.552 [6], clause 5.1.1.25 | bMRO | -| E2 | O-CU → Near-RT RIC | Number of too late HOs to a given neighbor cell | count | ~ 1 min, per beam or beam group | As specified in 3GPP TS 28.552 [6], clause 5.1.1.25 | bMRO | -| E2 | O-CU → Near-RT RIC | Number of HO to wrong cell to a given neighbor cell | count | ~ 1, per beam or beam group | As specified in 3GPP TS 28.552 [6], clause 5.1.1.25 | bMRO | -| E2 | O-CU → Near-RT RIC | Number of requested legacy HO executions (HO attempts) to a given neighbor cell | count | ~ 1 min, per beam or beam group | As specified in 3GPP TS 28.552 [6], clause 5.1.1.6 | bMRO | -| E2 | O-CU → Near-RT RIC | Number of successful legacy HO executions to a given neighbor cell | count | ~ 1 min, per beam or beam group | As specified in 3GPP TS 28.552 [6], clause 5.1.1.6 | bMRO | -| E2 | O-CU → Near-RT RIC | Number of failed legacy HO executions to a given neighbor cell | count | ~ 1 min, per beam or beam group | As specified in 3GPP TS 28.552 [6], clause 5.1.1.6 | bMRO | -| E2 | O-CU → Near-RT RIC | Mobility failure indication with root cause (too early HO, too late HO, HO to wrong cell; ping-pong HO) and number of requested or number of successful HO executions at the time of failure | message | Instantaneous at failure event, per beam or beam group, per UE | New measurement and new reporting | bMRO | -| E2 | O-CU → Near-RT RIC | PDCP buffer status | count | ~per N x 1ms, per DRB per UE | As specified in 3GPP TS 38.323 [40], clause 5.6
New reporting | mUMO | - -NOTE: Measurements for bMRO to be associated with active beam pattern in case of GoB optimization. - -#### 4.4.4.4 E2 node configuration - - - -Table 4.4.4.4-1: Input data - -| Input data | | | | | | | -|------------|--------------------|-----------------------------------------------|---------|-------------------------------|--------------------------------------------------------------------------------|-------------------------| -| Interface | Source → Target | Name/Description | Units | Reporting Period, granularity | New or existing definition, Existing Specification (Clause) | Applicable sub-features | -| E2 | O-DU → Near-RT RIC | Number of supported non-GoB beamforming modes | count | infrequent event (> hours) | New | Non-GoB | -| E2 | O-DU → Near-RT RIC | O-RU antenna information | message | Infrequent (~hours) | As specified in O-RAN.WG4.MP.0-R003-v15 [35], clause D.3.8
New reporting | mUMO | -| E2 | O-DU → Near-RT RIC | O-DU supported compression methods | message | Infrequent (~hours) | As specified in O-RAN.WG4.CUS.0-R003-v15 [34], clause 7.7.1.2
New reporting | mUMO | - - - -Table 4.4.4.4-2: Input data - -| Input data | | | | | | | -|------------|--------------------|------------------------------|---------|-------------------------------|--------------------------------------------------------------------|-------------------------| -| Interface | Source → Target | Name/Description | Units | Reporting Period, granularity | New or existing definition, Existing Specification (Clause) | Applicable sub-features | -| E2 | O-CU → Near-RT RIC | Served cell information | message | Infrequent (~hours) | As specified in 3GPP TS 38.473 [21], clause 9.3.1.10 | mUMO | -| E2 | O-CU → Near-RT RIC | MIB | message | Infrequent (~hours) | As specified in 3GPP TS 38.331 [18], clause 6.2.2
New reporting | mUMO | -| E2 | O-CU → Near-RT RIC | Serving cell SSB information | message | Infrequent (~hours) | As specified in 3GPP TS 38.331 [18], clause 6.3.2
New reporting | mUMO | - - - -Table 4.4.4.4-3: Output data - -| Output data | | | | | | | -|-------------|--------------------|----------------------------------------------------------------------|-------|-----------------------------|-------------------------------------------------------------|-------------------------| -| Interface | Source → Target | Name/Description | Units | Config. Period, granularity | New or existing definition, Existing Specification (Clause) | Applicable sub-features | -| E2 | Near-RT RIC → O-CU | Beam grouping info (list of beam group IDs with associated beam IDs) | list | infrequent event (> hours) | New | bMRO | - -## 4.5 QoE optimization - -Based on the end-to-end requirements for the QoE optimization use case specified in [32] and in [28], some high-level functional description and requirements over Near-RT RIC and E2 interface are introduced. - -### 4.5.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 can be insufficient to satisfy diversified QoE requirements especially taking into account potentially significant fluctuation of radio transmission capability. It is expected that QoE estimation/prediction can help deal with such uncertainty and improve the efficiency of radio resources, and eventually improve user experience. RAN Analytics Information (RAI) as RAN service can be exposed to RAI service consumers for specific UE (as specified in O-RAN.WG1.O-RAN-Architecture-Description-v06.00 [30], clause 4.5) or for groups of UE (per slice, per cell, per PLMN, etc.). RAI is envisioned to be helpful for the applications to improve the user experience. - -Near-RT RIC and E2 interface are leveraged to support this use case. Measurement data through E2 interface, e.g., cell level data, UE level data, can be acquired and processed via ML algorithms to support traffic recognition, QoE prediction, and QoS enforcement decisions. When requested, the analytics information, e.g., traffic rate, latency, packet loss rate, is exposed to the RAI service consumers to help applications execute logical control. - -### 4.5.2 Entities/resources involved in the use case - -- 1) Near-RT RIC: - - a) Support receiving request or subscription messages from RAI service consumer. - - b) Support receiving network state and UE performance report from RAN. - - c) Support data analysis and executing the AI/ML models to infer RAN analytics information, e.g., QoE prediction, and available bandwidth prediction. - - d) Support exposure RAN analytics information to RAI service consumer. -- 2) RAN: - - a) Support network state and UE performance report with required granularity to Near-RT RIC over E2 interface. -- 3) RAI service consumer: - - a) Request or subscribe to RAN analytics information from the Near-RT RIC. - - b) Support UE identification using data structure as specified in O-RAN.WG1.O-RAN-Architecture-Description-v06.00 [30], clause 4. - -### 4.5.3 Solutions - -#### 4.5.3.0 Introduction - -This clause specifies solution components that can be combined into different solutions. A solution based on E2 control/policy consists of clause 4.5.3.1 and clause 4.5.3.2. Another solution based on RAN analytics information exposure consists of clause 4.5.3.1 and clause 4.5.3.3. - -#### 4.5.3.1 AI/ML model training and distribution - -Overall process shall be as specified in O-RAN.WG2.UCR [28], clause 4.2.3.1, however step 3 would be performed over O2 when and if “image based” ML model deployment option is selected (as specified in O-RAN.WG2.AIML [29], clause 7). - -#### 4.5.3.2 Policy generation and performance evaluation - -Editor's note: to be defined based on requirements as specified in O-RAN.WG2.UCR [28], clause 4.2.3.2. - -#### 4.5.3.3 RAN performance analytics assisted QoE optimization - -RAN performance analytics can be requested by the RAI service consumer using either a request/response solution or a subscription-based solution. - -The context of RAN performance analytics assisted QoE optimization using request/response is captured in table 4.5.3.3-1. - -**Table 4.5.3.3-1: RAN performance analytics assisted QoE optimization using request/response** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Expose RAN analytics information to RAI service consumer for QoE optimization. | | -| Actors and Roles | Near-RT RIC, RAI service consumer, E2 nodes | | -| Assumptions | All relevant functions and components are instantiated.
RAI service consumer has obtained the necessary information to initiate request for QoE related RAI from the Near-RT RIC. | | -| Pre-conditions | QoE related ML models have been deployed in Near-RT RIC.
E2 interface is established to enable collection of measurements from E2 nodes. | | -| Begins when | RAI service consumer decides to request RAN analytics information for QoE optimization. | | -| Step 1 (M) | RAI service consumer requests for QoE related RAN analytics information from Near-RT RIC. | | -| Step 2 (O) | Near-RT RIC initiates measurement data collection from E2 nodes via RIC subscription procedure. See NOTE 1. | | -| Step 3-4 (M) | E2 node sends periodic measurement data to Near-RT RIC, received data is processed and stored. | | -| Step 5 (M) | Near-RT RIC generates the RAN analytics information, using QoE related AI/ML models and collected measurement data. | | -| Step 6 (M) | Near-RT RIC sends the RAN analytics information to RAI service consumer. | | -| Ends when | RAI service consumer receives the RAN analytics information response. | | -| Exceptions | None identified. | | -| Post Conditions | RAI service consumer obtains RAI necessary for QoE optimization.
Near-RT RIC may stop data collection. | | - -NOTE 1: Near-RT RIC may be configured to start collection of measurement data before requested by RAI service consumer. - -``` -@startuml -Skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 - -Box "O-RAN" #lightpink - Participant near as "Near-RT RIC" - Participant ran as "E2 Nodes" -End box -Box "External" #lightcyan - Participant "RAI service consumer" as app -End box - -app -> near : 1. RAI Request for QoE optimization -near --> ran: 2. <> RIC Subscription procedure(Report: Measurements) -``` - -``` - -Loop Data collection - ran -> near : 3. <> RIC Indication (Report) - near -> near : 4. Process and store data -end -near -> near: 5. RAN analytics information generation -near -> app: 6. RAI Response (RAN analytics information) -near <--> ran: <> RIC Subscription Delete procedure(Report: Measurements) - -@enduml - -``` - -The flow diagram of the RAN performance analytics assisted QoE optimization using request/response is given in figure 4.5.3.3.-1. - -![Sequence diagram showing RAN performance analytics assisted QoE optimization using request/response. Lifelines: Near-RT RIC, E2 Nodes (O-RAN), and RAI service consumer (External).](dfafe39c233a62ec8ebd71e42992c14d_img.jpg) - -``` - -sequenceDiagram - box pink O-RAN - participant Near-RT RIC - participant E2 Nodes - end - box lightblue External - participant RAI service consumer - end - - RAI service consumer->>Near-RT RIC: 1. RAI Request for QoE optimization - Near-RT RIC->>E2 Nodes: 2. <> RIC Subscription procedure(Report: Measurements) - loop Data collection - E2 Nodes-->>Near-RT RIC: 3. <> RIC Indication (Report) - Near-RT RIC->>Near-RT RIC: 4. Process and store data - end - Near-RT RIC->>Near-RT RIC: 5. RAN analytics information generation - Near-RT RIC->>RAI service consumer: 6. RAI Response (RAN analytics information) - Near-RT RIC-->>E2 Nodes: <> RIC Subscription Delete procedure(Report: Measurements) - -``` - -Sequence diagram showing RAN performance analytics assisted QoE optimization using request/response. Lifelines: Near-RT RIC, E2 Nodes (O-RAN), and RAI service consumer (External). - -**Figure 4.5.3.3-1: RAN performance analytics assisted QoE optimization using request/response** - -The context of RAN performance analytics assisted QoE optimization using subscription-based solution is captured in table 4.5.3.3-2. - -**Table 4.5.3.3-2: RAN performance analytics assisted QoE optimization using subscription-based solution** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Expose RAN analytics information to RAI service consumer for QoE optimization. | | -| Actors and Roles | Near-RT RIC, RAI service consumer, E2 nodes | | -| Assumptions | All relevant functions and components are instantiated.
RAI service consumer has obtained the necessary information to initiate request for QoE related RAI from the Near-RT RIC. | | -| Pre-conditions | QoE related ML models have been deployed in Near-RT RIC.
E2 interface is established to enable collection of measurements from E2 nodes. | | -| Begins when | RAI service consumer decides to subscribe to reports of RAN analytics information for QoE optimization. | | -| Step 1 (M) | RAI service consumer initiates RAI subscription procedure for QoE related RAN analytics information from Near-RT RIC. | | -| Step 2 (O) | Near-RT RIC may initiate measurement data collection from E2 nodes via RIC subscription procedure. See NOTE 1. | | -| | Steps 3-5 loop with RAI service consumer receiving requested subscription-based reports. | | -| Step 3-4 (M) | E2 node sends periodic measurement data to Near-RT RIC, received data is processed and stored. | | -| Step 5 (M) | Near-RT RIC generates the RAN analytics information, using QoE related AI/ML models and collected measurement data. | | -| Step 6 (M) | Near-RT RIC sends the RAN analytics information to RAI service consumer. | | -| Ends when | RAI service consumer initiates RAI subscription delete procedure. | | -| Exceptions | None identified. | | -| Post Conditions | RAI service consumer obtains RAI necessary for QoE optimization.
Near-RT RIC may stop E2 node data collection. | | - -NOTE 1: Near-RT RIC may be configured to start collection of measurement data before requested by RAI service consumer. - -``` - -@startuml -Skin rose -skinparam ParticipantPadding 5 -skinparam BoxPadding 10 -skinparam defaultFontSize 12 - -Box "O-RAN" #lightpink - Participant near as "Near-RT RIC" - Participant ran as "E2 Nodes" -End box -Box "External" #lightcyan - Participant "RAI service consumer" as app -End box - -app <-> near : 1. RAI Subscription procedure for QoE optimization -near <--> ran: 2. <> RIC Subscription procedure(Report: Measurements) - -Loop Until subscription terminated - Loop Data collection - ran -> near : 3. <> RIC Indication (Report) - near -> near : 4. Process and store data - end - near -> near: 5. RAN analytics information generation - near -> app: 6. RAI Report (RAN analytics information) -end -app <-> near : RAI Subscription Delete procedure -near <--> ran: <> RIC Subscription Delete procedure(Report: Measurements) - -``` - -@endum1 - -The flow diagram of the RAN performance analytics assisted QoE optimization using subscription-based solution is given in figure 4.5.3.3-2. - -![Sequence diagram showing RAN performance analytics assisted QoE optimization using subscription-based solution. The diagram is divided into two main lifelines: O-RAN (containing Near-RT RIC and E2 Nodes) and External (containing RAI service consumer). The process starts with a subscription procedure from Near-RT RIC to RAI service consumer, followed by a subscription procedure from E2 Nodes to Near-RT RIC. A loop labeled '[Until subscription terminated]' contains a nested loop labeled '[Data collection]'. Inside the nested loop, E2 Nodes send an indication to Near-RT RIC, which processes and stores the data, then generates RAN analytics information and sends a report to the RAI service consumer. After the loops, a subscription delete procedure is initiated from Near-RT RIC to RAI service consumer, followed by a subscription delete procedure from E2 Nodes to Near-RT RIC.](331afcb1534110b4c4f6ddf553a0f7e0_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC - participant E2 Nodes - participant RAI service consumer - - Note left of Near-RT RIC: O-RAN - Note right of RAI service consumer: External - - Near-RT RIC->>RAI service consumer: 1. RAI Subscription procedure for QoE optimization - E2 Nodes->>Near-RT RIC: 2. <> RIC Subscription procedure(Report: Measurements) - - loop Until subscription terminated - loop Data collection - E2 Nodes->>Near-RT RIC: 3. <> RIC Indication (Report) - Near-RT RIC->>Near-RT RIC: 4. Process and store data - Near-RT RIC->>Near-RT RIC: 5. RAN analytics information generation - Near-RT RIC->>RAI service consumer: 6. RAI Report (RAN analytics information) - end - end - - Near-RT RIC->>RAI service consumer: RAI Subscription Delete procedure - E2 Nodes->>Near-RT RIC: <> RIC Subscription Delete procedure(Report: Measurements) - -``` - -Sequence diagram showing RAN performance analytics assisted QoE optimization using subscription-based solution. The diagram is divided into two main lifelines: O-RAN (containing Near-RT RIC and E2 Nodes) and External (containing RAI service consumer). The process starts with a subscription procedure from Near-RT RIC to RAI service consumer, followed by a subscription procedure from E2 Nodes to Near-RT RIC. A loop labeled '[Until subscription terminated]' contains a nested loop labeled '[Data collection]'. Inside the nested loop, E2 Nodes send an indication to Near-RT RIC, which processes and stores the data, then generates RAN analytics information and sends a report to the RAI service consumer. After the loops, a subscription delete procedure is initiated from Near-RT RIC to RAI service consumer, followed by a subscription delete procedure from E2 Nodes to Near-RT RIC. - -Figure 4.5.3.3-2: RAN performance analytics assisted QoE optimization using subscription-based solution - -### 4.5.4 Required data - -This clause elaborates the Near-RT RIC and the E2 node capabilities necessary for implementation of the QoE optimization use case, especially for RAN performance analytics. The requirements are specified in clause 5. - -#### 4.5.4.1 UE context information from E2 nodes - -The followings are examples of UE context information identified as required: - -- UE ID -- List of S-NSSAI -- List of QoS related ID, eg., 5QI, QFI - -For example, UE ID, S-NSSAI or QoS related ID can be used to collect, analysis and predict the resource occupation of each user, slice or service, eg. maximum/average throughput, maximum/average latency, average packet loss rate. - -#### 4.5.4.2 Measurements from E2 nodes - -The E2 measurements are necessary for inference and prediction in the Near-RT RIC as the driver for decisions in addition to KPMs. For the QoE optimization use case, especially for RAN performance analytics, the Near-RT RIC receives the request or - -subscription from RAI service consumer and subscribes and receives the measurement data from O-CU/O-DU through E2 interface. Based on it, with QoE related AI/ML models, the Near-RT RIC infers the RAN analytics information, and exposes it to RAI service consumer. - -The examples of cell-level, UE-level, and slice-level measurement information are listed in table 4.5.4.2-1 below. - -**Table 4.5.4.2-1: Measurements from E2 nodes** - -| Measurement Type | | Measurement Examples | -|------------------|----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Cell-level | L2 | 1. MCS Distribution in PDSCH (available at DU; as specified in 3GPP TS 28.552 [6], clause 5.1.1.12.1) | -| | | 2. DL/UL Total PRB usage (available at DU; as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.1 and 5.1.1.2.2 and in 3GPP TS 32.425 [7], clauses 4.5.3 and 4.5.4) | -| | | 3. Distribution of DL/UL Total PRB usage (available at DU; as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.3 and 5.1.1.2.4 and in 3GPP TS 32.425 [7], clauses 4.5.10 and 4.5.11) | -| | | 4. DL/UL PRB used for data traffic (available at DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.5 and 5.1.1.2.7) | -| | | 5. DL/UL PRB usage for traffic (per QCI, as specified in 3GPP TS 32.425 [7], clauses 4.5.1 and 4.5.2) | -| | | 6. DL/UL Total available PRB (available at DU; as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.6 and 5.1.1.2.8) | -| | | 7. DL/UL PRB full utilization (as specified in 3GPP TS 32.425 [7], clauses 4.5.9.1 and 4.5.9.2) | -| | | 8. Total number of DL/UL TBs (available at DU; split into subcounters per layer at MU-MIMO case, as specified in 3GPP TS 28.552 [6], clauses 5.1.1.7.3 and 5.1.1.7.8 and in 3GPP TS 32.425 [7], clauses 4.5.7.1 and 4.5.7.3) | -| | | 9. Total error number of DL/UL TBs (available at DU; split into subcounters per layer at MU-MIMO case, as specified in 3GPP TS 28.552 [6], clauses 5.1.1.7.4 and 5.1.1.7.9 and in 3GPP TS 32.425 [7], clauses 4.5.7.2 and 4.5.7.4) | -| | | 10. Average DL UE throughput in gNB (available at DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.1.3.1) | -| | | 11. Distribution of DL UE throughput in gNB (available at DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.1.3.2) | -| | | 12. Packet Delay (available at DU and CU-UP; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.3.3) | -| | | 13. RAN part packet delay components (as specified in 3GPP TS 38.314 [16], clause 4.2.1.2) | -| | | 14. Packet Delay (per QCI, as specified in 3GPP TS 36.314 [9], clause 4.1.4) | -| | | 15. DL/UL Cell PDCP SDU Data Volume (available at CU-UP; per PLMN ID and per QoS level (mapped 5QI) and per S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.2.1 for non-split gNB, clause 5.1.3.6.2 for split gNB; per | - -| Measurement Type | | Measurement Examples | -|------------------|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | |

PLMN ID and per E-RAB QoS profile (QCI, ARP and GBR), as specified in 3GPP TS 32.425 [7], clause 4.4.7)

16. Mean number of Active UEs in the DL/UL per cell (available at DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clauses 5.1.1.23.1 and 5.1.1.23.3)

17. Max number of Active UEs in the DL/UL per cell (available at DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clauses 5.1.1.23.2 and 5.1.1.23.4)

18. Average number of Active UEs (per QCI, as specified in 3GPP TS 32.425 [7], clause 4.4.2)

19. Packet Loss Rate (available at CU-UP or DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.3.1)

20. Packet Loss Rate (per QCI, as specified in 3GPP TS 32.425 [7], clause 4.4.4)

21. DL Packet Drop Rate (available at CU-UP or DU; optionally split into subcounters per QoS level (mapped 5QI or QCI in NR option 3) and subcounters per supported S-NSSAI, as specified in 3GPP TS 28.552 [6], clause 5.1.3.2)

22. DL Packet Drop Rate (per QCI, as specified in 3GPP TS 32.425 [7], clause 4.4.3.2)

| -| UE-level | Radio channel info in CU-CP |

1. SINR (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11])

2.RSRP (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11])

3.RSRQ (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11])

| -| | L2 |

CQI, MCS

DL/UL UE throughput

DL/UL UE PRB usage

RLC buffer size

RLC occupied buffer

RLC unused buffer

UL/DL MAC rate

Packet Delay

Packet Interval

Packet Jitter, eg. Packet Interval Jitter, Packet Size Jitter

Data volume (per UE, as specified in 3GPP TS 36.314 [9], clause 4.1.8)

Data volume (per UE)

Packet Loss Rate per DRB per UE (as specified in 3GPP TS 38.314 [16], clause 4.2.1.5)

| - -| Measurement Type | | Measurement Examples | -|------------------|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | Block Error Rate
DL Packet Drop Rate
Total number of RLC SDUs/PDUs | -| Slice-level | L2 | DL/UL UE PRB usage
RLC buffer size
RLC occupied buffer
RLC unused buffer
UL/DL MAC rate
Packet Delay
Packet Interval
Packet Jitter, eg. Packet Interval Jitter, Packet Size Jitter
Data volume (per QCI, as specified in 3GPP TS 36.314 [9], clause 4.1.8)
Data volume (per 5QI)
Packet Loss Rate per DRB per UE
Block Error Rate
DL Packet Drop Rate (as specified in 3GPP TS 28.552 [6], clause 5.1.3.2)
Total number of RLC SDUs/PDUs | - -### 4.5.5 RAN analytics information exposed by Near-RT RIC - -Based on the measurements from E2 nodes, with QoE related AI/ML models, the Near-RT RIC infers the RAN analytics information and expose it to RAI service consumer. The exposed RAN analytics information will be helpful for the applications to evaluate network status and execute logic control, e.g., TCP transmission window adjustment, video coding rate selection to improve QoE. - -The examples of RAN analytics information are listed in table 4.5.5-1 below. - -**Table 4.5.5-1: RAN analytics information** - -| Measurement Type | | Measurement Examples | -|------------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| -| UE-level | Predicted RAN performance | 1. Minimum/maximum/average throughput
2. Minimum/maximum/average latency
3. Average packet loss rate
4. QoE prediction | -| | Prediction related information | 1. Confidence
2. Validity period | - -## 4.6 Network energy saving - -This use case provides the motivation, description, and requirements for Near RT RIC and E2 interface to support network energy saving, whose end-to-end requirements are specified in [32]. - -The RAN is responsible for the majority of the Energy Consumption (EC) of a mobile network, and the O-RU consumes the largest part of the energy consumption of the RAN. The rarefaction of fossil fuel-based energy resources and the urgent need to reduce CO2 emissions make energy saving a strategic goal for network operators, in addition to the significant energy related OPEX reduction requirement. - -The ES use cases are divided into sub-use cases, which have different properties, the time scale of the control and the controlled system involved: - -1. Carrier and cell switch off/on -2. RF channel reconfiguration -3. Advanced Sleep Modes - -Energy consumption can be reduced by improving the Energy Efficiency (EE) of the network, and by introducing different Energy Saving (ES) mechanisms. Several ES mechanisms are related to switching off certain components and resources in the network and differ from one another by their time scale. In a longer time-scale of minutes, hours and above, and when the cell load is low, ES can be achieved by switching off one or more carriers or the cell itself. At the same or shorter time-scale, from seconds to minutes, ES can be achieved by switching off RF channels (including possibly array of antennas) of a Massive-MIMO (mMIMO) system. At a shorter time-scale corresponding to a symbol, subframe and frame, Advanced Sleep Modes (ASM) can be considered (see ORAN-WG1.Use Cases Energy Saving Technical Report R003 v02.00 [i.4], 3GPP TR 28.813 [i.5] and 3GPP TS 28.310 [33]). - -4. PRB blanking - -Another mechanism to achieve ES is to apply PRB blanking optimization. Blanking the PRBs saves power in many components in the O-RU due to the reduced input/output power and processing load. PRB blanking also supports interference reduction in a multi-cell environment. PRB blanking optimization is applicable to all three time-scales (longer time-scale of minutes or above, shorter time-scale from seconds to minutes as well as even shorter time-scale corresponding to a symbol, subframe and frame). - -5. Deep hibernate - -A longer time-scale mechanism (minutes to hours) is deep hibernate in which the O-RU enters a deep low-power state with a controlled wake-up as per O-RAN.WG4.MP.0-R003-v15 [35], clause 20.5; the Near-RT RIC orchestrates the decision via E2, while execution uses the WG4 M-plane. - -6. Spatial and power domain - -In 3GPP Release-18 [14], clause 15.4.2.7, Spatial Domain (SD) and Power Domain (PD) adaptations were introduced. These features enable the E2 node to dynamically adjust the number of active antenna elements and transmission power based on UE channel conditions. Near-RT RIC can provide policies or configurations to the E2 node to guide this process in order to save energy. - -7. SSB-less SCell - -3GPP Rel-18 [14], clause 15.4.2.6 introduces the concept of SSB-less Secondary Cell (SCell) activation for carrier aggregation, which allows efficient use of secondary carriers without needing constant synchronization signals. This enhances spectral efficiency and data throughput for users with high demand, without burdening the network with unnecessary signaling. Near-RT RIC can activate SSB-less SCells in appropriate cells to improve spectral efficiency while minimizing power consumption during low-traffic periods. - -8. Power Amplifier (PA) optimization - -The O-RU energy saving could be achieved by optimizing its Power Amplifier (PA) operating region according to the traffic scheduling requirements, to reduce the O-RU power consumption. To facilitate this, the Near-RT RIC analyses various network data and KPIs to prepare policy or configuration changes for the O-DU. The O-DU then applies the changes to O-RU to save energy. - -### 4.6.1 Carrier and cell switch off/on - -#### 4.6.1.1 Background and goal of the use case - -Carrier and cell switch off/on control by the Non-RT or Near-RT RIC can consider overall network energy efficiency instead of local optimization. In addition to the ES optimization in the SMO/Non-RT RIC, optimizing network EC in the Near-RT RIC brings significant gains due to more UE centric, near-real-time intelligent control capabilities with finer granularity. The AI/ML models' functionality in the Near-RT RIC can include prediction of future traffic, user mobility, resource usage, QoS and QoE on a per UE basis and may also predict expected energy efficiency enhancements, resource usage, and network performance for different carrier and cell switching off/on options. Based on the predicted results, optimized ES control actions or policies can be given by the Near-RT RIC to E2 nodes in near-real-time manner to track the dynamic network conditions. ES control also includes preparation actions (before carrier and cells are switched off) and post control actions (after carrier and cells are switched on) such as checking ongoing emergency calls and warning messages, enabling/disabling/modifying carrier aggregation and/or dual connectivity, steering traffic and handing over UEs from source cells/carriers to other cells/carriers, changing MU-MIMO layers, beam scheduling policies and SSB burst configurations etc, which can be handled in the Near-RT RIC by the intelligent and UE centric RAN control capabilities coordinated with the SMO/Non-RT RIC. - -The goal of Near-RT RIC energy saving is to interpret the policies received over A1 and to determine the optimum changes it can make according to these policies. More specifically, Near-RT RIC triggers E2 procedure and related control/policies so as to obtain network performance that would fulfill the criteria identified in the A1 policies. It may also leverage the A1 enrichment information to make more informed decisions. Traffic steering may reuse mechanisms provided by other use cases to affect the changes necessary to achieve its goals. The Near-RT RIC may also work in background processing without the A1 policy guidance from the Non-RT RIC. - -#### 4.6.1.2 Entities/resources involved in the use case - -- 1) Near-RT RIC: - - a) Near-real-time monitoring of energy saving related performance measurements. - - b) Receive energy saving xApps from SMO. - - c) Support interpretation and enforcement of A1 policies from Non-RT RIC. - - d) Support enrichment information via the A1 interface. - - e) Perform optimized RAN (E2) actions to achieve ES requirements based on O1 configuration, A1 policy, A1 enrichment information and E2 reports. -- 2) E2 node: - - a) Support ES optimization actions or policy enforcements via E2. - - b) Support ES related performance measurements through O1. - - c) Support ES related performance reports through E2. - -#### 4.6.1.3 Solution - -There are three general ES processing modes and the transitions between them. The three processing modes, baseline, background and A1 policy-based, as described in clause 4.1.3 for traffic steering use case applies to the energy saving use case as is except that the modes represent the way the Near-RT RIC operates on a given E2 node rather than UE specific. - -The context of ES optimization by carriers and cell switching off/on is captured in table 4.6.1.3-1. - -**Table 4.6.1.3-1: ES optimization by carriers and cell switching off/on** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Drive energy saving cell switching off/on optimization in accordance with RAN OAM configured background behavior (mode 1) or policies information from the Non-RT RIC using A1 interface (mode 2). | | -| Actors and Roles | - Non-RT RIC in SMO domain: Creates and updates A1 policies, provide A1 enrichment information. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| |
  • - Near-RT RIC: Enforces A1 policies and generates RIC CONTROL and/or POLICY.
  • - E2 node: RIC CONTROL and POLICY execution and RIC REPORT creation.

Refer to 4.6.1.2 for more details.

| | -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - A1, O1 and E2 interface connectivity is established.
  • - A1 policy scope defined.
| | -| Pre-conditions |
  • - Network is operational with default configuration.
  • - OAM functions have configured a baseline measurement configuration and the Non-RT RIC has access to this data.
  • - OAM functions have configured baseline traffic steering parameters in E2 node(s) through O1 interface.
  • - (optional) If ES mode 1, OAM functions have configured background ES behavior to the Near-RT RIC through O1 interface.
  • - Non-RT RIC analyzes the historical data from RAN 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 non-real-time optimization of configuration and policies.
| | -| Begins when | Energy saving optimization by cell switching off/on is activated or an operator defined trigger is detected. | | -| Step 1 (O) | (Start of outer loop control)
If ES mode 1, OAM functions collect data from E2 node through O1 interface. | | -| Step 2 (O) | Non-RT RIC retrieve ES related performance data from OAM function. | | -| Step 3 (O) | Non-RT RIC evaluates the collected data and A1 policy feedback, if required, and generates or updates the appropriate ES optimization policy, such as ES targets and carrier/cell switching off/on guidance, etc. | | -| Step 4 (O) | Non-RT RIC sends the ES optimization policy to Near-RT RIC via A1 interface. | | -| Step 5 (O) | Non-RT RIC sends optional ES related A1 enrichment information. | | -| Step 6 (O) | If ES mode 2, Near-RT RIC collects data from E2 node through E2 interface. | | -| Step 7 (O) | Near-RT RIC evaluates the collected data, if required, generates or updates the internal background mode ES optimization targets or policies. | | -| Step 8 (M) | (Start of inner loop control)
Near-RT RIC subscribes to a UE context information and measurement metrics via E2 interface. | | -| Step 9 (M) | E2 nodes report the UE context information and E2 measurements via RIC REPORT periodically or event-triggered. | | -| Step 10 (M) | Near-RT RIC evaluates the performance data from E2 nodes and finds potential improvements to energy efficiency which are indicated in the A1 policy and/or internal Near-RT RIC TS targets. | | -| Step 11 (O) |

Based on the UE context information, E2 measurement metrics (RIC REPORT), and A1 policy, Near-RT RIC may generate new or modify the existing E2 policies and sends them to E2 nodes.

E2 node functions target of E2 policy may be:

  • - E-UTRAN-NR dual connectivity
  • - Carrier aggregation
  • - Connected mode mobility
  • - Idle mode mobility
  • - Radio access control
  • - Cell switching off/on control
| | -| Step 12 (O) |

Near-RT RIC may also generate control command(s) and send them to E2 node(s) to trigger re-allocation of radio resources and switching off/on carrier and cells so that the overall network energy efficiency can be improved.

E2 node functions target of E2 control command may be:

  • - Same as Step 11
| | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | (End of inner loop control) | | -| Step 13 (O) | For ES mode 2, Near RT-RIC may send A1 policy feedback on A1 to the Non-RT RIC.
(End of outer loop control) | | -| Step 14 (O) | Non-RT RIC decides to delete ES optimization policy in case of ES mode 2 and sends the related messages. | | -| Step 15,16 (M) | Following A1 policy deletion (mode 2) or internal trigger (mode 1), the Near-RT RIC terminates the ES optimization procedure and delete the related RIC subscriptions. | | -| Ends when | ES optimization is deactivated, or an operator defined trigger is detected. | | -| Exceptions | None. | | -| Post Conditions | Energy saving over a period of time is achieved. | | -| Traceability | REQ-E2-ES-FUN1, REQ-E2-ES-FUN2, REQ-Near-RT-RIC-ES-FUN1, REQ-Near-RT-RIC-ES-FUN2, REQ-Near-RT-RIC-ES-FUN3 | | - -``` - -@startuml -autonumber -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Box "Service Management and Orchestration" #gold - Participant OAM as "OAM Functions" - Participant non as "Non-RT RIC" -End box - -Box "O-RAN" #lightpink - Participant near as "Near-RT RIC" - Participant ran as "E2 Node" -End box - -group OUTER LOOP CONTROL - - OAM <--> ran : (Mode 2) <> RAN Data collection - OAM --> non: (Mode 2) ES related performance information - non --> non: (Mode 2) Collected data evaluation and policy creation - - non --> near : (Mode 2) <> A1 policy setup or update - non --> near: (opt.) <> ES related A1 enrichment information - near <--> ran: (Mode 1) <> RAN Data collection - near --> near: (Mode 1) Collected data evaluation and policy creation - - group INNER LOOP CONTROL - near -> ran : <> RIC SUBSCRIPTION REQUEST(UE context & measurement metrics) - ran -> near: <> RIC INDICATION (UE context & E2 measurement metrics) - near -> near: Evaluation, potential improvement to energy efficiency - near -> ran : (opt.) <> RIC SUBSCRIPTION REQUEST (ES optimisation POLICY) - near -> ran : (opt.) <> RIC CONTROL REQUEST (ES optimisation RIC CONTROL) - end - - non <-- near: (Mode 2) <> A1 policy feedback - -end - -non --> near: (Mode 2) <> A1 policy delete -near -> near: ES optimization stopped -near-> ran: <> RIC SUBSCRIPTION DELETE - -``` - -@endum1 - -The flow diagram of the ES optimization by carriers and cell switching off/on is given in figure 4.6.1.3-1. - -![Sequence diagram showing ES optimization by carriers and cell switching off/on between Service Management and Orchestration (OAM Functions, Non-RT RIC) and O-RAN (Near-RT RIC, E2 Node).](d9cfc30025244dcd75766061f27ee09f_img.jpg) - -``` - -sequenceDiagram - participant SM as Service Management and Orchestration (OAM Functions, Non-RT RIC) - participant OR as O-RAN (Near-RT RIC, E2 Node) - - Note left of SM: OUTER LOOP CONTROL - SM->>OR: 1 (Mode 2) «O1» RAN Data collection - OR-->>SM: 2 (Mode 2) ES related performance information - SM->>OR: 3 (Mode 2) Collected data evaluation and policy creation - SM->>OR: 4 (Mode 2) «A1» A1 policy setup or update - SM->>OR: 5 (opt) «A1-E1» ES related A1 enrichment information - Note right of OR: INNER LOOP CONTROL - OR->>OR: 6 (Mode 1) «E2» RAN Data collection - OR-->>OR: 7 (Mode 1) Collected data evaluation and policy creation - OR->>OR: 8 «E2» RIC SUBSCRIPTION REQUEST(UE context & measurement metrics) - OR-->>OR: 9 «E2» RIC INDICATION (UE context & E2 measurement metrics) - OR->>OR: 10 Evaluation, potential improvement to energy efficiency - OR->>OR: 11 (opt) «E2» RIC SUBSCRIPTION REQUEST (ES optimisation POLICY) - OR->>OR: 12 (opt) «E2» RIC CONTROL REQUEST (ES optimisation RIC CONTROL) - Note left of SM: OUTER LOOP CONTROL - SM->>OR: 13 (Mode 2) «A1» A1 policy feedback - SM->>OR: 14 (Mode 2) «A1» A1 policy delete - OR-->>OR: 15 ES optimization stopped - OR->>OR: 16 «E2» RIC SUBSCRIPTION DELETE - -``` - -Sequence diagram showing ES optimization by carriers and cell switching off/on between Service Management and Orchestration (OAM Functions, Non-RT RIC) and O-RAN (Near-RT RIC, E2 Node). - -Figure 4.6.1.3-1: ES optimization by carriers and cell switching off/on - -#### 4.6.1.4 Required data - -This clause elaborates the Near-RT RIC and the E2 node capabilities necessary for implementation of the ES carrier and cell switch off/on use case. The requirements are specified in clause 5. - -##### 4.6.1.4.1 Control over E2 - -1) **Radio access control:** Access control may be applied to restrict access of other UEs for a specific cell in order to prepare for switching off the cell to save energy. A cell-level, UE-level, or slice-level access control can be applied. Four categories of radio access control are indicated as below: - -- RACH backoff -- RRC connection reject -- RRC connection release -- Access barring - -Both RIC POLICY and RIC CONTROL can be used. - -2) **Mobility control:** For example, a neighbouring cell may be selected in order to switch off the current serving cell. A neighbour handover restriction list may be configured to prevent the UEs from HO to some neighbour cells in order to reduce traffic load of the neighbour cells and switch them off. - -- Handover from the source cell to the target cell -- Configuration/reconfiguration of handover restriction list -- Configuration of idle mode mobility parameters - -- Enable, disable, or modify CA (as specified in 3GPP TS 38.473 [21], 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]) -- Enable, disable, or modify dual connectivity (as specified in 3GPP TS 38.473 [21], 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]) - -Both RIC POLICY and RIC CONTROL can be used. - -- 3) **Carriers and cell switch off/on control:** Depending on the traffic condition, certain number of carriers and cells can be switched off by the Near-RT RIC by sending guidance to the E2 node when the traffic is low in order to save energy. When the network conditions deteriorate (e.g., congested traffic, frequent handover failure and/or RA failure), carrier/cell switch-on control command could be sent to E2 node in E2 policy/control to activate the cell/carrier from energy saving and hence ensure network performance. - -NOTE: Once E2 node receives the guidance from Near-RT RIC for switching off/on a cell/carrier, it is not expected that the cell/carrier can be switched off immediately. The E2 node can take time to do all necessary actions to prepare for switching off/on the carrier/cell and there is also a delay in O-RU and open fronthaul interface for switching off/on the cell/carrier. However, it is still expected, as specified in [32], that the Near-RT RIC to send this intent to the E2 node to start the process for cell/carrier switching off/on after the network performance and energy efficiency are jointly optimized through for example traffic steering and QoS/QoE optimisation by the Near-RT RIC through 1) and 2). The E2 node (e.g., O-CU-CP) can optionally do traffic steering and OoS optimisation upon receiving this command from the Near-RT RIC before triggering the cell/carrier switching off/on. - -Either RIC POLICY or RIC CONTROL can be used which is not addressed in the present document. - -##### 4.6.1.4.2 UE context information from E2 nodes - -The followings are examples of UE context information identified as required: - -- UE ID (as specified in [32]) -- Slice level: S-NSSAI -- DRB level: e.g., established DRB ID, mapping with QoS flows, etc. -- QoS related: e.g., E-RAB level QoS parameters (4G, NSA) or QoS flow level QoS parameters (NG-RAN) -- UE capabilities: CA and DC capabilities - -For example, UE ID, S-NSSAI, DRB ID, or QCI/5QI can be used to derive the QoS requirements and the resource occupation; the UE capabilities may be required to select the appropriate RRM action (e.g., CA/DC configuration). - -##### 4.6.1.4.3 Measurements from E2 nodes - -The E2 measurements are necessary for inference and prediction in the Near-RT RIC as the driver for decisions in addition to KPMs. For the energy saving carrier and cell switch off/on use case, the Near-RT RIC can translate an A1 policy (relatively static targets) into a flexible selection of controls over E2 (e.g., handover control, DC, CA, idle mode mobility, carrier and cell switching off/on) by taking into account the RAN resource utilization, cell level and the UE level performance, the radio and traffic conditions, QoS and QoE requirements and energy consumption and efficiency etc. - -The examples of measurement information identified as required are listed in table 4.6.1.4.3-1. - -**Table 4.6.1.4.3-1: Measurements from E2 nodes** - -| Measurement Type | Measurement Examples | -|----------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Cell/SSB area related measurements |
  • - DL/UL Total PRB Usage, Distribution of DL/UL Total PRB Usage, DL/UL GBR PRB Usage, DL/UL non-GBR PRB Usage, RRC Connection Number, Available RRC Connection Capacity Value, Mean and Maximum Number of Active UEs per DRB in the DL/UL, DL/UL Scheduling PDCCH CCE Usage, DL/UL Composite Available Capacity, DL/UL Cell PDCP SDU Data Volume (including secondary RAT usage for EN-DC/MR-DC), Handover success ratio
  • - DL/UL SSB Area Total PRB Usage, DL/UL SSB Area GBR PRB Usage, DL/UL SSB Area non-GBR PRB Usage, SSB Area Capacity Value
  • - DL/UL PRB usage per QCI, DL/UL PRB usage per 5QI, DL/UL PRB usage per slice, Slice Available Capacity Value

As specified in 3GPP TS 32.425 [7], 3GPP TS 28.552 [6], 3GPP TS 36.314 [9], 3GPP TS 38.314 [16], 3GPP TS 38.423 [19], 3GPP TS 38.463 [20] and 3GPP TS 38.473 [21]

| -| E2 node user plane measurements per-UE/UE group |
  • - Average DL/UL throughput
  • - DL/UL PRB usage
  • - DL/UL Scheduled IP throughput
  • - Buffer Status Information (e.g., UL BSR)

As specified in 3GPP TS 32.425 [7], 3GPP TS 28.552 [6], 3GPP TS 36.314 [9], 3GPP TS 38.314 [16], 3GPP TS 38.423 [19], 3GPP TS 38.473 [21], 3GPP TS 38.463 [20], 3GPP TS 36.321 [10], 3GPP TS 38.321 [17]

| -| UE L1/L2/L3 measurements |
  • - RSRP and RSRQ measurements
  • - SINR measurements
  • - CQI/MCS measurements
  • - Location and Velocity measurements

As specified in 3GPP TS 36.331 [11] and 3GPP TS 38.331 [18]

| -| Energy consumption measurement | Energy consumption measurement of O-RU
  • - PNF Power Consumption (average/min/max)
  • - PNF Energy Consumption (average/min/max)

As specified in 3GPP TS 28.552 [6]

| -| Mobility and RA related KPIs/measurements of UE/UE group | Mobility and RA related KPIs/measurements from the E2 nodes hosting the target NES cell(s) and/or the neighbour cell(s) to the target NES cell(s)
  • - Handover failure related, e.g., number of handover failures related to MRO
  • - RACH failure related, e.g., distribution of RACH access delay
  • - Radio link failure reports
  • - UE context release related, e.g., number of UE context release requests

As specified in 3GPP TS 36.331 [11], 3GPP TS 38.331 [18], 3GPP 32.425 [7], 3GPP 28.552 [6]

| - -##### 4.6.1.4.4 E2 node configuration - -Cell level configuration parameters in order to configure UE measurements required for traffic steering and QoS/QoE optimization (see clause 4.1.4.4) for optionally preparing for and optimizing network performance and efficiency before cell/carrier switching off/on. - -### 4.6.2 Advanced sleep mode - -#### 4.6.2.1 Background and goal of the use case - -During DL transmission or UL reception, certain O-RU components (e.g., PA, LNA and baseband etc) can be powered off during blank OFDM symbols and slots. For power saving at the symbol level, PA and LNA can be turned off since their transition period (on to off and off to on) can be in a few microseconds (micro sleep). For power saving at slot level, additional HW can be turned off to save more energy if the transition time allowed is in a few milliseconds (light sleep). For power saving at frame level, even more HW can be turned off (e.g., only maintain O-RU M-plane processing) however higher transition delay, in 100 - -msec, is expected. For micro and light sleeps, Near-RT RIC can play important roles which based on AI/ML solutions can help to create more sleeping opportunities in the E2 nodes to save energy by e.g., steering traffic, influencing traffic shaping/scheduling, and adjusting common channel (SS/RS) configurations etc. For deep sleeps, where traffic prediction and more capacity, coverage, accessibility and QoS/QoE impacts awareness is needed because of the long-term traffic interruption (e.g., >100ms), Near-RT RIC is the sensible place to guide the system into deep mode due to the rich UE centric data and AI/ML solutions available in the Near-RT RIC. - -The goal of Near-RT RIC energy saving is to interpret the policies received over A1 and to determine the optimum changes it can make according to these policies. More specifically, Near-RT RIC triggers E2 procedure and related control/policies so as to obtain network performance that would fulfill the criteria identified in the A1 policies. It may also leverage the A1 enrichment information to make more informed decisions. Traffic steering may reuse mechanisms provided by other use cases to affect the changes necessary to achieve its goals. The Near-RT RIC may also work in background processing without the A1 policy guidance from the Non-RT RIC. - -#### 4.6.2.2 Entities/resources involved in the use case - -See clause 4.6.1.2. - -#### 4.6.2.3 Solution - -The three processing modes, baseline (mode 0), background (mode 1) and A1 policy-based (mode 2), as described in clause 4.1.3 for traffic steering use case applies to this use case also as is except that the modes represent the way the Near-RT RIC operates on a given E2 node rather than UE specific. - -The context of energy saving ASM optimization is captured in table 4.6.2.3-1. - -**Table 4.6.2.3-1: Energy saving ASM optimization** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Drive energy saving Advanced Sleep Mode (ASM) optimization in accordance with RAN OAM configured background behavior (ES mode 1) or policies information from the Non-RT RIC using A1 interface (ES mode 2). | | -| Actors and Roles |
  • - Non-RT RIC in SMO domain: Creates and updates A1 policies, provide A1 enrichment information.
  • - Near-RT RIC: Enforces A1 policies and generates RIC CONTROL and/or POLICY.
  • - E2 node: RIC CONTROL and POLICY execution and RIC REPORT creation.

Refer to 4.6.2.2 for more details.

| | -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - A1, O1 and E2 interface connectivity is established.
  • - A1 policy scope defined.
| | -| Pre-conditions |
  • - Network is operational with default configuration.
  • - OAM functions have configured a baseline measurement configuration and the Non-RT RIC has access to this data.
  • - OAM functions have configured baseline ES parameters in E2 node(s) through O1 interface.
  • - (optional) If ES mode 1, OAM functions have configured background ES behavior to the Near-RT RIC through O1 interface.
  • - Non-RT RIC analyzes the historical data from RAN 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 non-real-time optimization of configuration and policies.
| | -| Begins when | Energy saving ASM optimization is activated, or an operator defined trigger is detected. | | -| Step 1 (O) | (Start of outer loop control)
If ES mode 2, OAM functions collects data from E2 node through O1 interface. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Step 2 (O) | Non-RT RIC retrieve ES related performance data from OAM function. | | -| Step 3 (O) | Non-RT RIC evaluates the collected data and A1 policy feedback, if required, and generates or updates the appropriate ES optimization policy, such as energy saving and performance targets and ASM guidance, etc. | | -| Step 4 (O) | Non-RT RIC sends the ES optimization policy to Near-RT RIC via A1 interface. | | -| Step 5 (O) | Non-RT RIC sends optional ES related A1 enrichment information. | | -| Step 6 (O) | If ES mode 1, Near-RT RIC collects data from E2 node through E2 interface. | | -| Step 7 (O) | Near-RT RIC evaluates the collected data, if required, generates, or updates the internal background mode ES optimization targets or policies. | | -| Step 8 (M) | (Start of inner loop control)
Near-RT RIC subscribes to a UE context information and measurement metrics via E2 interface. | | -| Step 9 (M) | E2 nodes report the UE context information and E2 measurements via RIC REPORT periodically or event triggered. | | -| Step 10 (M) | Near-RT RIC evaluates the performance data from E2 nodes and finds potential improvements to energy efficiency which are indicated in the A1 policy and/or internal Near-RT RIC TS targets. | | -| Step 11 (O) | Based on the UE context information, E2 measurement metrics (RIC REPORT), and A1 policy, Near-RT RIC may generate new or modify the existing E2 policies and sends them to E2 nodes.

E2 node functions target of E2 policy may be:
  • - Mobility control
  • - Radio access control
  • - ASM scheduler policy setting
  • - Common channel configurations
  • - Sleep mode configurations
| | -| Step 12 (O) | Near-RT RIC may also generate control command(s) and send them to E2 node(s) to trigger the reconfiguration of radio resources, traffic steering, reconfiguration of common channels and entering/leaving deep sleep mode.

E2 node functions target of E2 control command may be:
  • - Same as Step 11
(End of inner loop control) | | -| Step 13 (O) | For ES mode 2, Near RT-RIC may send A1 policy feedback on A1 to the Non-RT RIC.
(End of outer loop control) | | -| Step 14 (O) | Non-RT RIC decides to delete ES optimization policy in case of ES mode 2 and sends the related messages. | | -| Step 15,16 (M) | Following A1 policy deletion (mode 2) or internal trigger (mode 1), the Near-RT RIC terminates the ES optimization procedure and delete the related RIC subscriptions. | | -| Ends when | ES optimization is deactivated, or an operator defined trigger is detected. | | -| Exceptions | None. | | -| Post Conditions | Energy saving over a period of time is achieved. | | -| Traceability | REQ-Near-RT-RIC-ES-FUN1, REQ-Near-RT-RIC-ES-FUN2, REQ-Near-RT-RIC-ES-FUN4, REQ-E2-ES-FUN2, REQ-E2-ES-FUN3, REQ-E2-ES-FUN4, REQ-E2-ES-FUN5 | | - -``` - -@startuml -autonumber -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Box "Service Management and Orchestration" #gold - Participant OAM as "OAM Functions" - Participant non as "Non-RT RIC" -End box - -Box "O-RAN" #lightpink - Participant near as "Near-RT RIC" - Participant ran as "E2 Node" -End box - -group OUTER LOOP CONTROL - - OAM <--> ran : (Mode 2) <> RAN Data collection - OAM --> non: (Mode 2) ES related performance information - non --> non: (Mode 2) Collected data evaluation and policy creation - - non --> near : (Mode 2) <> A1 policy setup or update - non --> near: (opt.) <> ES related A1 enrichment information - near <--> ran: (Mode 1) <> RAN Data collection - near --> near: (Mode 1) Collected data evaluation and policy creation - - group INNER LOOP CONTROL - near -> ran : <> RIC SUBSCRIPTION REQUEST(UE context & measurement metrics) - ran -> near: <> RIC INDICATION (UE context & E2 measurement metrics) - near -> near: Evaluation, potential improvement to energy efficiency - near -> ran : (opt.) <> RIC SUBSCRIPTION REQUEST (ES optimisation POLICY) - near -> ran : (opt.) <> RIC CONTROL REQUEST (ES optimisation RIC CONTROL) - end - - non <-- near: (Mode 2) <> A1 policy feedback - -end - -non --> near: (Mode 2) <> A1 policy delete -near -> near: ES optimization stopped -near-> ran: <> RIC SUBSCRIPTION DELETE -@enduml - -``` - -The flow diagram of the energy saving ASM optimization is given in figure 4.6.2.3-1. - -![Sequence diagram for Energy saving ASM optimization showing interactions between Service Management and Orchestration (OAM Functions, Non-RT RIC) and O-RAN (Near-RT RIC, E2 Node). The process is divided into Outer Loop Control and Inner Loop Control phases.](b1784a5cbeeb3d9fb9e60b333019c721_img.jpg) - -``` - -sequenceDiagram - participant SM as Service Management and Orchestration - subgraph SM [Service Management and Orchestration] - OAM[OAM Functions] - NonRT[Non-RT RIC] - end - subgraph ORAN [O-RAN] - NearRT[Near-RT RIC] - E2[E2 Node] - end - - Note left of SM: OUTER LOOP CONTROL - SM->>E2: 1 (Mode 2) «O1» RAN Data collection - E2-->>SM: 2 (Mode 2) ES related performance information - SM->>NonRT: 3 (Mode 2) Collected data evaluation and policy creation - NonRT->>E2: 4 (Mode 2) «A1» A1 policy setup or update - E2-->>NonRT: 5 (opt) «A1-E1» ES related A1 enrichment information - Note right of ORAN: INNER LOOP CONTROL - NearRT->>E2: 6 (Mode 1) «E2» RAN Data collection - E2-->>NearRT: 7 (Mode 1) Collected data evaluation and policy creation - NearRT->>E2: 8 «E2» RIC SUBSCRIPTION REQUEST(UE context & measurement metrics) - E2-->>NearRT: 9 «E2» RIC INDICATION (UE context & E2 measurement metrics) - Note right of ORAN: 10 Evaluation, potential improvement to energy efficiency - NearRT->>E2: 11 (opt) «E2» RIC SUBSCRIPTION REQUEST (ES optimisation POLICY) - NearRT->>E2: 12 (opt) «E2» RIC CONTROL REQUEST (ES optimisation RIC CONTROL) - Note right of ORAN: 15 ES optimization stopped - E2-->>NearRT: 16 «E2» RIC SUBSCRIPTION DELETE - NonRT->>E2: 13 (Mode 2) «A1» A1 policy feedback - E2-->>NonRT: 14 (Mode 2) «A1» A1 policy delete - -``` - -Sequence diagram for Energy saving ASM optimization showing interactions between Service Management and Orchestration (OAM Functions, Non-RT RIC) and O-RAN (Near-RT RIC, E2 Node). The process is divided into Outer Loop Control and Inner Loop Control phases. - -Figure 4.6.2.3-1: Energy saving ASM optimization - -#### 4.6.2.4 Required Data - -This clause elaborates the Near-RT RIC and the E2 node capabilities necessary for implementation of the ES ASM use case. The requirements are specified in clause 5. - -##### 4.6.2.4.1 Control over E2 - -1) **Radio access control:** Access control may be applied to restrict access of other UEs for a specific cell in order to create more sleeping opportunities for the cell. A cell-level, UE-level, or slice-level access control can be applied. Four categories of radio access control are indicated as below: - -- RACH backoff -- RRC connection reject -- RRC connection release -- Access barring - -Both RIC POLICY and RIC CONTROL can be used. - -2) **Mobility control:** In order to reduce traffic load to create more sleeping opportunities on the targeted cells, serving cell can be chosen based on the resource status and QoS of the UE(s) and a neighbour handover restriction list may be configured to prevent the UEs from HO to some neighbour cells. The following procedures can be used for mobility control: - -- Handover from the source cell to the target cell -- Configuration/reconfiguration of handover restriction list -- Configuration of idle mode mobility parameters -- Enable, disable, or modify CA (as specified in 3GPP TS 38.473 [21], 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]) -- Enable, disable, or modify dual connectivity (as specified in 3GPP TS 38.473 [21], 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]) - -Both RIC POLICY and RIC CONTROL can be used. - -3) **NES related radio resource control**, such as configuration common channel periodicities and semi-persistent scheduling (SPS) to create more sleep opportunities including the following types of configurations: - -- SR periodicity reconfiguration (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]): Both *sr-ProhibitTimer* and *sr-TransMax* can be treated. -- SPS configuration (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]): Both *SPS-Config* (DL) and *ConfiguredGrantConfig* (UL) can be treated. -- CSI-RS periodicity configurations. -- Common channel periodicity configurations. - -NOTE: UE DTX/DRX slots overwrite the SR and SPS configurations since during DTX/DRX, SR and SPS transmission will be deactivated. SSB periodicity may be reconfigured by the Near-RT RIC (if the capability is exposed by the E2 node) on some cells such that the O-RU can have longer sleep duration which enables deeper sleep (more hardware components can be switched off) to save energy, however, the performance impact to UEs needs to be taken care by the operator and xApp/E2 node vendors. - -Both RIC POLICY and RIC CONTROL can be used. - -4) **ASM mode objectives**: Configuration of ASM mode objectives to the E2 node which can include: - -- Energy saving target, e.g., targeted energy saving in percentage of current average energy consumption or energy saving levels (e.g., maximum energy saving, medium energy saving, maximum performance etc.). -- UE or cell level performance targets, e.g., throughput cap, throughput drop tolerance, latency target. -- Preferred sleep mode, as specified in O-RAN.WG4.MP.0-R003-v15 [35], clause 20.4.1, sleep-mode-type of asm-capability-info. - -Either RIC POLICY or RIC CONTROL can be used. - -NOTE: After the objectives are configured, the E2 node shall try to achieve the objectives, however, whether the objectives can be met depends on the real traffic conditions and E2 node implementations. The E2 node reports if the ASM performance objective is applied and taken into operation. The E2 node also reports the related KPIs, as defined in clause 4.6.1.4.3, for Near-RT RIC to assess the performance changes comparing against the objectives and make further optimisation actions. - -5) **Sleep mode configuration**: Depending on the current and predicted future traffic conditions, the Near-RT RIC may guide O-DU to move the carriers into sleep mode. Following the guidance, O-DU may decide to disable (“move to sleep mode”) array carriers, tx-arrays or rx-arrays or the whole O-RU accordingly via the O-FH C-plane in order to save energy (see O-RAN.WG4.CUS.0-R003-v15 [34], table 7.4.6-7). The guided configurations can include: - -- Indication of the slot numbers, symbol numbers and the conditions for the sleep mode configuration to be applied. -- The sleep mode (as specified in O-RAN.WG4.MP.0-R003-v15 [35], clause 20.4.1, sleep-mode-type of asm-capability-info) to be applied during the sleep period indicated in 1 above. - -Either RIC POLICY or RIC CONTROL can be used. - -NOTE: After the configuration, the E2 node shall try to achieve the configured sleep mode behaviour if the conditions are met, however, it is up to the E2 node to decide when and whether the configuration can be applied depending on the on-going traffic conditions within the E2 node. The E2 node reports if the sleep mode configuration is applied. The E2 node also report the related KPIs, as defined in clause 4.6.1.4.3, for Near-RT RIC to assess the performance changes comparing against the objectives and make further optimisation actions. - -##### 4.6.2.4.2 UE context information from E2 nodes - -See clause 4.6.1.4.2. - -##### 4.6.2.4.3 Measurements from E2 nodes - -See clause 4.6.1.4.3 - -##### 4.6.2.4.4 E2 node configuration - -Cell level configuration parameters in order to configure UE measurements required for traffic steering and QoS/QoE optimization (see clause 4.1.4.4) for creating more sleeping opportunities to save energy while maintaining acceptable performance. - -O-RU and O-DU advanced sleep mode capabilities, as specified in O-RAN.WG4.MP.0-R003-v15 [35], clause 20.4.1, asm-capability-info, along with information about the mapping from cells to sector carriers and to O-RU are retrieved from O-DU in order to generate applicable and optimized energy saving related policies and controls. - -### 4.6.3 RF channel reconfiguration - -#### 4.6.3.1 Background and goal of the use case - -In mobile networks, massive-MIMO array antennas are used to implement beamforming techniques, which boost the cell coverage, capacity, and spectrum efficiency for enhanced mobile broadband services. Due to the massive number of the active antenna elements and RF channels used in the massive-MIMO array, it can consume significantly more energy than conventional antenna solution. The goal of the RF channel reconfiguration energy saving use case is to reduce the power consumption of O-RUs for massive-MIMO by dynamically reconfiguring the number of active Tx/Rx array antenna elements. When the traffic load is low, fewer beams or MU-MIMO spatial layers are needed, therefore, fewer Tx/Rx array antenna elements can be active which can be reconfigured from Near-RT RIC dynamically leading to significant power savings. The number of active antenna element and the antenna element layout also have an impact to the signal coverage and spatial channel orthogonality translating to impact to the UE service of quality, which need to be handled by the Near-RT RIC to avoid the impact to the performance or finding the trade-off between energy saving and performance. - -The goal of Near-RT RIC energy saving is to interpret the policies received over A1 interface. Based on policy and the current or predicted traffic and channel conditions, the Near-RT RIC then derive the best choices for O-RU Tx/Rx array configurations including e.g. number of active antenna element, antenna element layout, SU/MU MIMO layers etc and provide guided configurations to the O-DU. Following the guidance, O-DU may decide to disable (“putting to sleep”) some or all array elements in a tx-array or rx-array (or both) accordingly via the O-FH C-plane in order to save energy (see O-RAN.WG4.CUS.0-R003-v15 [34], clause 7.2.9.2.3). - -#### 4.6.3.2 Entities/resources involved in the use case - -See clause 4.6.1.2. - -#### 4.6.3.3 Solution - -The context of energy saving RF channel reconfiguration optimization is captured in table 4.6.3.3-1. - -**Table 4.6.3.3-1: Energy saving RF channel reconfiguration optimization** - -| Use Case Stage | Evolution / Specification | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | Drive energy saving RF channel reconfiguration optimization in accordance with RAN OAM configured background behavior (ES mode 1) or policies information from the Non-RT RIC using A1 interface (ES mode 2). | -| Actors and Roles |
  • - Non-RT RIC in SMO domain: Creates and updates A1 policies, provide A1 enrichment information.
  • - Near-RT RIC: Enforces A1 policies and generates RIC CONTROL and/or POLICY.
  • - E2 node: RIC CONTROL and POLICY execution and RIC REPORT creation.

Refer to 4.6.3.2 for more details.

| - -| Use Case Stage | Evolution / Specification | -|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - A1, O1 and E2 interface connectivity is established.
  • - A1 policy scope defined.
| -| Pre-conditions |
  • - Network is operational with default configuration.
  • - OAM functions have configured a baseline measurement configuration and the Non-RT RIC has access to this data.
  • - OAM functions have configured baseline ES parameters in E2 node(s) through O1 interface.
  • - (optional) If ES mode 1, OAM functions have configured background ES behavior to the Near-RT RIC through O1 interface.
  • - Non-RT RIC analyzes the historical data from RAN 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 non-real-time optimization of configuration and policies.
| -| Begins when | Energy saving RF channel reconfiguration optimization is activated, or an operator defined trigger is detected. | -| Step 1 (O) | (Start of outer loop control)
If ES mode 2, OAM functions collect data from E2 node through O1 interface. | -| Step 2 (O) | Non-RT RIC retrieve ES related performance data from OAM function. | -| Step 3 (O) | Non-RT RIC evaluates the collected data and A1 policy feedback, if required, and generates or updates the appropriate ES optimization policy, such as energy saving and performance, etc. | -| Step 4 (O) | Non-RT RIC sends the ES optimization policy to Near-RT RIC via A1 interface. | -| Step 5 (O) | Non-RT RIC sends optional ES related A1 enrichment information. | -| Step 6 (O) | If ES mode 1, Near-RT RIC collects data from E2 node through E2 interface. | -| Step 7 (O) | Near-RT RIC evaluates the collected data, if required, generates or updates the internal background mode ES optimization targets or policies. | -| Step 8 (M) | (Start of inner loop control)
Near-RT RIC subscribes to a UE context information and measurement metrics via E2 interface. | -| Step 9 (M) | E2 nodes report the UE context information and E2 measurements via RIC REPORT periodically or event-triggered. | -| Step 10 (M) | Near-RT RIC evaluates the performance data from E2 nodes and finds potential improvements to energy efficiency or potential gap to A1 policy and/or internal Near-RT RIC ES targets. | -| Step 11 (O) | Based on evaluation in Step 10, Near-RT RIC may generate new or modify the existing E2 policies and sends them to E2 nodes.

E2 node functions target of E2 policy may be:
  • - Connected mode mobility
  • - Idle mode mobility
  • - Radio access control
  • - RF channel reconfiguration policy setting
  • - Common channel configurations (SSB, CSI-RS)
  • - TX/RX array configuration change
| -| Step 12 (O) | Near-RT RIC may also generate control command(s) and send them to E2 node(s) to trigger the reconfiguration of radio resources, traffic steering, reconfiguration of common channels and entering/leaving deep sleep mode.

E2 node functions target of E2 control command may be:
  • - Same as Step 11
(End of inner loop control) | -| Step 13 (O) | For ES mode 2, Near RT-RIC may send A1 policy feedback on A1 to the Non-RT RIC.
(End of outer loop control) | -| Step 14 (O) | Non-RT RIC decides to delete ES optimization policy in case of ES mode 2 and sends the related messages. | - -| Use Case Stage | Evolution / Specification | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Step 15,16 (M) | Following A1 policy deletion (mode 2) or internal trigger (mode 1), the Near-RT RIC terminates the ES optimization procedure and delete the related RIC subscriptions. | -| Ends when | ES optimization is deactivated, or an operator defined trigger is detected. | -| Exceptions | None. | -| Post Conditions | Energy saving over a period of time is achieved. | -| Traceability | REQ-Near-RT-RIC-ES-FUN1, REQ-Near-RT-RIC-ES-FUN2, REQ-Near-RT-RIC-ES-FUN3, REQ-Near-RT-RIC-ES-FUN5, REQ-Near-RT-RIC-ES-FUN6, REQ-E2-ES-FUN2, REQ-E2-ES-FUN4, REQ-E2-ES-FUN6, REQ-E2-ES-FUN7 | - -``` - -@startuml -autonumber -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Box "Service Management and Orchestration" #gold - Participant OAM as "OAM Functions" - Participant non as "Non-RT RIC" -End box - -Box "O-RAN" #lightpink - Participant near as "Near-RT RIC" - Participant ran as "E2 Node" -End box - -group OUTER LOOP CONTROL - - OAM <--> ran : (Mode 2) <> RAN Data collection - OAM --> non: (Mode 2) ES related performance information - non --> non: (Mode 2) Collected data evaluation and policy creation - - non --> near : (Mode 2) <> A1 policy setup or update - non --> near: (opt.) <> ES related A1 enrichment information - near <--> ran: (Mode 1) <> RAN Data collection - near --> near: (Mode 1) Collected data evaluation and policy creation - - group INNER LOOP CONTROL - near -> ran : <> RIC SUBSCRIPTION REQUEST(UE context & measurement metrics) - ran -> near: <> RIC INDICATION (UE context & E2 measurement metrics) - near -> near: Evaluation, potential improvement to energy efficiency - near -> ran : (opt.) <> RIC SUBSCRIPTION REQUEST (ES optimisation POLICY) - near -> ran : (opt.) <> RIC CONTROL REQUEST (ES optimisation RIC CONTROL) - end - - non <-- near: (Mode 2) <> A1 policy feedback - -end - -non --> near: (Mode 2) <> A1 policy delete -near -> near: ES optimization stopped -near-> ran: <> RIC SUBSCRIPTION DELETE -@enduml - -``` - -The flow diagram of the energy saving RF channel reconfiguration optimization is given in figure 4.6.3.3-1. - -![Sequence diagram for Energy saving RF channel reconfiguration optimization. The diagram shows interactions between Service Management and Orchestration (OAM Functions, Non-RT RIC) and O-RAN (Near-RT RIC, E2 Node). It is divided into OUTER LOOP CONTROL and INNER LOOP CONTROL. Steps include data collection, policy creation, policy setup, RIC subscription, evaluation, and policy feedback/deletion.](3b11cc18f8ee769d0076c139dbf81ba3_img.jpg) - -``` - -sequenceDiagram - participant SM as Service Management and Orchestration - subgraph SM [Service Management and Orchestration] - OAM[OAM Functions] - NRIC[Non-RT RIC] - end - subgraph ORAN [O-RAN] - NRT[Near-RT RIC] - E2[E2 Node] - end - - Note left of SM: OUTER LOOP CONTROL - NRIC->>E2: 1 (Mode 2) «O1» RAN Data collection - E2-->>NRIC: 2 (Mode 2) ES related performance information - NRIC->>NRT: 3 (Mode 2) Collected data evaluation and policy creation - NRT->>E2: 4 (Mode 2) «A1» A1 policy setup or update - E2-->>NRT: 5 (opt.) «A1-EI» ES related A1 enrichment information - NRT->>E2: 6 (Mode 1) «E2» RAN Data collection - E2-->>NRT: 7 (Mode 1) Collected data evaluation and policy creation - - Note right of ORAN: INNER LOOP CONTROL - NRT->>E2: 8 «E2» RIC SUBSCRIPTION REQUEST(UE context & measurement metrics) - E2-->>NRT: 9 «E2» RIC INDICATION (UE context & E2 measurement metrics) - NRT->>NRT: 10 Evaluation, potential improvement to energy efficiency - NRT->>E2: 11 (opt.) «E2» RIC SUBSCRIPTION REQUEST (ES optimisation POLICY) - E2-->>NRT: 12 (opt.) «E2» RIC CONTROL REQUEST (ES optimisation RIC CONTROL) - - Note left of SM: OUTER LOOP CONTROL - NRIC->>NRT: 13 (Mode 2) «A1» A1 policy feedback - NRT->>E2: 14 (Mode 2) «A1» A1 policy delete - E2-->>NRT: 15 ES optimization stopped - NRT->>E2: 16 «E2» RIC SUBSCRIPTION DELETE - -``` - -Sequence diagram for Energy saving RF channel reconfiguration optimization. The diagram shows interactions between Service Management and Orchestration (OAM Functions, Non-RT RIC) and O-RAN (Near-RT RIC, E2 Node). It is divided into OUTER LOOP CONTROL and INNER LOOP CONTROL. Steps include data collection, policy creation, policy setup, RIC subscription, evaluation, and policy feedback/deletion. - -Figure 4.6.3.3-1: Energy saving RF channel reconfiguration optimization - -#### 4.6.3.4 Required data - -This clause elaborates the Near-RT RIC and the E2 node capabilities necessary for implementation of the ES RF channel reconfiguration use case. The requirements are specified in clause 4. - -##### 4.6.3.4.1 Control over E2 - -- 1) **Radio access control:** See clause 4.6.2.4.1. -- 2) **Mobility control:** See clause 4.6.2.4.1. -- 3) **NES related radio resource control:** See clause 4.6.2.4.1 -- 4) **TRX control performance objectives:** Configuration of TRX control performance objectives to the E2 node which can include: - - Energy saving target, e.g. targeted energy saving in percentage of current average energy consumption or energy saving levels (e.g., maximum energy saving, medium energy saving, maximum performance, etc.). - - UE or cell level performance targets, e.g., throughput cap, throughput drop tolerance, latency target. - -Either RIC POLICY or RIC CONTROL can be used. - -NOTE: After the objectives are configured, the E2 node shall try to achieve the objectives, however, whether the objectives can be met depends on the real traffic conditions and E2 node implementations. The E2 node reports if the TRX control objective is applied and taken into operation. The E2 node also reports the related KPIs, as defined in clause 4.6.1.4.3, for Near-RT RIC to assess the performance changes comparing against the objectives and make further optimisation actions. - -- 5) **TRX control configuration:** Depending upon the current and future traffic predictions, the Near-RT RIC may guide the O-DU to perform O-RU RF channel reconfigurations to reduce the overall power consumption of the O-RU. Following the guidance, O-DU may decide to disable (“putting to sleep”) some or all array elements in a tx-array or rx-array (or both) - -accordingly via the O-FH C-plane in order to save energy (O-RAN.WG4.CUS.0-R003-v15 [34], Table 7.4.6-7). The guided configurations can include: - -- Indication of the slot numbers, symbol numbers and the conditions for the TRX control configuration to be applied. -- Indication of the array elements to be switched off during the period indicated above based on the TRX control capability information reported by the E2 node (O-DU), see clause 4.6.3.4.4. The capability information includes antenna mask values supported by the O-RU, see O-RAN.WG4.MP.0-R003-v17.01 [39], clause 20.3.1, trx-control-capability-info, for more details. -- The sleep mode (see O-RAN.WG4.MP.0-R003-v17.01 [39], clause 20.3.1, sleep-mode-type of trx-control-capability-info) to be applied during the sleep period indicated above. - -Either RIC POLICY or RIC CONTROL can be used. - -NOTE: After the configuration, the E2 node shall try to achieve the configured behaviour if the conditions are met, however, it is up to the E2 node to decide when and whether the configuration can be applied depending on the on-going traffic conditions within the E2 node. The E2 node reports if the TRX control configuration is applied. The E2 node also report the related KPIs, as defined in clause 4.6.1.4.3, for Near-RT RIC to assess the performance changes comparing against the objectives and make further optimisation actions. - -Both RIC POLICY and RIC CONTROL can be used. - -##### 4.6.3.4.2 UE context information from E2 nodes - -See clause 4.6.1.4.2. - -##### 4.6.3.4.3 Measurements from E2 nodes - -See clause 4.6.1.4.3. - -##### 4.6.3.4.4 E2 node configuration - -Cell level configuration parameters in order to configure UE measurements required for traffic steering and QoS/QoE optimization (see clause 4.1.4.4) for creating more RF channel reconfiguration opportunities to save energy while maintaining acceptable performance. - -O-RU and O-DU TRX control capabilities, see O-RAN.WG4.MP.0-R003-v17.01 [39], clause 20.3.1, trx-control-capability-info, along with information about the mapping from cells to sector carriers and to O-RU are retrieved from O-DU in order to generate applicable and optimized energy saving related policies and controls. - -### 4.6.4 PRB blanking optimization - -#### 4.6.4.1 Background and goal of the use case - -Blanking the PRBs saves power in many components in the O-RU due to the reduced input/output power and processing load. In addition, PRB blanking is being supported in clause 8.4.2 of WG4 Control, User and Synchronization Plane Specification as Data blanking [34] to meet objectives such as energy saving. Specifically, in clause 8.4.2.2, it said “PRB blanking is an inherent feature of the frequency-domain-based fronthaul split 7-2x, where unallocated PRBs are not sent across the fronthaul interface to reduce the fronthaul throughput. An unallocated PRB is a PRB with all REs unallocated”. Currently, an O-DU can blank the PRBs during scheduling taking local performance targets such as energy consumption into consideration, and then signal the blanked or activated PRBs to O-RU via C-plane Section Type 1 messages. However, the Near-RT RIC is not able to send configurations/policies regarding PRBs to be blanked to an O-DU to influence the MAC scheduler behaviours for optimizing PRB allocations to meet different performance targets in a network with multiple cells. PRB blanking has also been leveraged to achieve interference optimization in a network with multiple cells as specified in use case 26 of WG1 Use Cases Detailed - -Specification R004 v15.00.01 [49]. PRB blanking optimization by the Near-RT RIC can consider overall network performance improvements for both uplink and downlink including energy efficiency with system-level optimization instead of local-level optimization by an O-DU alone. Furthermore, the AI/ML models' functionality in the Near-RT RIC can include prediction of future traffic, user mobility, resource usage, QoS and QoE on a per UE basis and may also predict expected energy efficiency enhancements, resource usage, network performance and interference reduction for different PRB blanking optimization options. Based on the predicted results, optimized PRBs blanking control actions or policies can be given by the Near-RT RIC to E2 nodes in near-real-time manner. - -The Near-RT RIC sends the two-dimensional (in both frequency and time domains) PRB blanking configurations or policies for uplink and/or downlink to each O-DU to consider for cells of interest in a multi-cell environment based on the evaluation of performance measurements collected and performance targets required. The performance measurements collected include e.g., EC, EE achieved, QoS including throughput and latency as well as interference. The performance targets include e.g., EC, EE, QoS and interference reduction. The Near-RT RIC decides the two-dimensional PRB blanking configurations or policies which include how many PRBs to blank and where those PRBs are in the frequency and time domain based on the trade-off analysis. The O-DU takes the PRB blanking configurations or policies as an input for its scheduler to make final resource allocations decision. - -#### 4.6.4.2 Entities/resources involved in the use case - -- 1) Near-RT RIC: - - a) Receive PRB blanking optimization xApps. - - b) Monitor performance measurements in EE, QoS and interference. - - c) Perform optimized RAN (E2) actions to achieve performance targets based on E2 reports. -- 2) E2 node: - - a) Support PRB blanking optimization actions or policy enforcements via E2. - - b) Support PRB blanking optimization related performance reports through E2. - -#### 4.6.4.3 Solution - -The context of PRB blanking optimization is captured in table 4.6.4.3-1. - -**Table 4.6.4.3-1: PRB blanking optimization to meet performance targets including ES** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Drive PRB blanking optimization in accordance with information from the E2 nodes. | | -| Actors and Roles |
  • - Near-RT RIC: Generates RIC CONTROL and/or POLICY.
  • - E2 node: RIC CONTROL and POLICY execution and RIC REPORT creation.
| | -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - E2 interface connectivity is established.
| | -| Pre-conditions |
  • - Network is operational with default configuration.
| | -| Begins when | PRB blanking optimization for performance targets including ES is activated, or an operator defined trigger is detected. | | -| Step 1 (M) | Near RT RIC generates or updates the appropriate PRB blanking optimization policy such as data to collect as well as performance targets including ES. | | -| Step 2 (M) | Near-RT RIC collects data from E2 node through E2 interface. | | -| Step 3 (M) | Near-RT RIC evaluates the collected data. | | -| Step 4 (M) | Near-RT RIC subscribes to a UE context information and measurement metrics via E2 interface. | | -| Step 5 (M) | E2 nodes report the UE context information and E2 measurements via RIC REPORT or INDICATION. | | -| Step 6 (M) | Near-RT RIC evaluates the data from E2 nodes and finds potential performance improvements including ES which are indicated in the performance targets. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Steps 7, 8 (O) | Near-RT RIC generates two-dimensional PRB blanking optimization control and sends them to E2 node(s) or generates PRB blanking optimization policy so that the overall network performance including ES can be optimized. | | -| Step 9 (M) | PRB blanking optimization is deactivated, or an operator defined trigger is detected. | | -| Step 10 (M) | RIC SUBSCRIPTION DELETE | | -| Ends when | PRB blanking optimization stops. | | -| Exceptions | None. | | -| Post Conditions | PRB blanking optimization over a period of time is achieved. | | -| Traceability | REQ-Near-RT-RIC-ES-FUN7
REQ-E2-QoS-FUN1, REQ-E2-QoS-FUN2, REQ-E2-QoS-FUN3, REQ-E2-QoS-FUN4, QoS-FUN7, QoS-FUN8, REQ-E2-ES-FUN2, REQ-E2-ES-FUN8, REQ-E2-ES-FUN9 | | - -``` - -@startuml -autonumber -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Box "O-RAN" #lightpink - Participant near as "Near-RT RIC" - Participant ran as "E2 Node" -End box - -near -> near: Near RT RIC generates or updates the appropriate PRB blanking optimization policy -near <--> ran: <> RAN Data collection -near --> near: Collected data evaluation - -near -> ran : <> RIC SUBSCRIPTION REQUEST (UE context & measurement metrics) -ran -> near: <> RIC REPORT or INDICATION (UE context & E2 measurement metrics) -near -> near: Evaluation, potential improvement to performance targets include EE -near -> ran : (opt.) <> RIC CONTROL REQUEST (PRB blanking CONTROL) -near -> ran : (opt.) <> RIC SUBSCRIPTION REQUEST (PRB blanking POLICY) - -near -> near: PRB blanking optimization stopped -near-> ran: <> RIC SUBSCRIPTION DELETE -@enduml - -``` - -The flow diagram of the performance targets optimization including ES by PRB blanking optimization is given in figure 4.6.4.3-1. - -![Sequence diagram titled 'O-RAN' showing the interaction between Near-RT RIC and E2 Node for PRB blanking optimization. The sequence includes 10 steps: 1. Near RT RIC generates or updates the appropriate PRB blanking optimization policy; 2. «E2» RAN Data collection; 3. Collected data evaluation; 4. «E2» RIC SUBSCRIPTION REQUEST (UE context & measurement metrics); 5. «E2» RIC REPORT or INDICATION (UE context & E2 measurement metrics); 6. Evaluation, potential improvement to performance targets include EE; 7. (opt.) «E2» RIC CONTROL REQUEST (PRB blanking CONTROL); 8. (opt.) «E2» RIC SUBSCRIPTION REQUEST (PRB blanking POLICY); 9. PRB blanking optimization stopped; 10. «E2» RIC SUBSCRIPTION DELETE.](8a781a0a8c956859f63a1ca7f2bb1644_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC - participant E2 Node - Note over Near-RT RIC: 1 Near RT RIC generates or updates the appropriate PRB blanking optimization policy - Near-RT RIC->>E2 Node: 2 «E2» RAN Data collection - Note over Near-RT RIC: 3 Collected data evaluation - Near-RT RIC->>E2 Node: 4 «E2» RIC SUBSCRIPTION REQUEST (UE context & measurement metrics) - E2 Node-->>Near-RT RIC: 5 «E2» RIC REPORT or INDICATION (UE context & E2 measurement metrics) - Note over Near-RT RIC: 6 Evaluation, potential improvement to performance targets include EE - Near-RT RIC->>E2 Node: 7 (opt.) «E2» RIC CONTROL REQUEST (PRB blanking CONTROL) - Near-RT RIC->>E2 Node: 8 (opt.) «E2» RIC SUBSCRIPTION REQUEST (PRB blanking POLICY) - Note over Near-RT RIC: 9 PRB blanking optimization stopped - Near-RT RIC->>E2 Node: 10 «E2» RIC SUBSCRIPTION DELETE - -``` - -Sequence diagram titled 'O-RAN' showing the interaction between Near-RT RIC and E2 Node for PRB blanking optimization. The sequence includes 10 steps: 1. Near RT RIC generates or updates the appropriate PRB blanking optimization policy; 2. «E2» RAN Data collection; 3. Collected data evaluation; 4. «E2» RIC SUBSCRIPTION REQUEST (UE context & measurement metrics); 5. «E2» RIC REPORT or INDICATION (UE context & E2 measurement metrics); 6. Evaluation, potential improvement to performance targets include EE; 7. (opt.) «E2» RIC CONTROL REQUEST (PRB blanking CONTROL); 8. (opt.) «E2» RIC SUBSCRIPTION REQUEST (PRB blanking POLICY); 9. PRB blanking optimization stopped; 10. «E2» RIC SUBSCRIPTION DELETE. - -Figure 4.6.4.3-1: Performance targets optimization including ES by PRB blanking optimization - -#### 4.6.4.4 Required data - -This clause elaborates the Near-RT RIC and the E2 node capabilities necessary for implementation of the PRB blanking optimization use case. The requirements are specified in clause 5. - -##### 4.6.4.4.1 Control over E2 - -- 1) **Radio resource allocation.** Near-RT RIC provides direct control for PRB blanking configurations to be applied at the E2 node. Configurations at cell level include: - - Configurations of two-dimensional PRBs to be blanked which is defined as configurations of PRB number to be blanked in the frequency domain within a time slot, and in the time domain across time slots. - -Both RIC POLICY and RIC CONTROL can be used. - -- 2) **PRB blanking policy.** Near-RT RIC provides policies to E2 node that describe ES target and other performance related targets the PRB blanking policies should achieve. The targets for performance objectives to the E2 node may include: - - Energy saving target, e.g., targeted energy saving in percentage of current average energy consumption or energy saving levels (e.g., maximum energy saving, medium energy saving, maximum performance, etc.). - - Cell level and UE performance targets, e.g. throughput cap, throughput drop tolerance, latency target. - - Interference reduction target. - - Preferred number of active or blanked PRBs. - -Either RIC POLICY or RIC CONTROL can be used. - -##### 4.6.4.4.2 UE context information from E2 nodes - -The followings are examples of UE context information identified as required: - -- UE ID (as defined in [24]) -- Slice level: S-NSSAI -- DRB level: e.g., established DRB ID, mapping with QoS flows, etc. -- QoS related: e.g., E-RAB Level QoS Parameters (4G, NSA) or QoS Flow Level QoS Parameters (NG-RAN). -- UE capabilities: CA and DC capabilities - -##### 4.6.4.4.3 Measurements from E2 nodes - -The E2 measurements are necessary for inference and prediction in the Near-RT RIC as the driver for decisions in addition to KPMs. For the PRB blanking optimization use case, the Near-RT RIC evaluates performance measurements and performance targets and then produces E2 controls (e.g., PRB blanking configurations or policies) by considering the RAN resource utilization, cell level and the UE level performance, the radio and traffic conditions, QoS and QoE requirements, energy consumption and efficiency and interference, etc. - -The examples of measurement information identified as required are listed in table 4.6.4.4.3-1. - -**Table 4.6.4.4.3-1: Measurements from E2 nodes** - -| Measurement Type | Measurement Examples | -|----------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Cell/SSB area related measurements |
  • - DL/UL Total PRB Usage, Distribution of DL/UL Total PRB Usage, DL/UL GBR PRB Usage, DL/UL non-GBR PRB Usage, RRC Connection Number, Available RRC Connection Capacity Value, Mean and Maximum Number of Active UEs per DRB in the DL/UL, DL/UL Scheduling PDCCH CCE Usage, DL/UL Composite Available Capacity, DL/UL Cell PDCP SDU Data Volume (including secondary RAT usage for EN-DC/MR-DC), Handover success ratio
  • - DL/UL SSB Area Total PRB Usage, DL/UL SSB Area GBR PRB Usage, DL/UL SSB Area non-GBR PRB Usage, SSB Area Capacity Value
  • - DL/UL PRB usage per QCI, DL/UL PRB usage per 5QI, DL/UL PRB usage per slice, Slice Available Capacity Value
  • - UL interference per cell
  • - UL interference per PRB per cell
  • - UL interference per PRB per antenna branch per cell
As specified in 3GPP TS 38.314 [16], 3GPP TS 38.463 [20], 3GPP TS 38.473 [21], 3GPP TS 38.423 [19] | -| E2 node user plane measurements per-UE/UE group |
  • - Average DL/UL throughput
  • - DL/UL PRB usage
  • - DL/UL Scheduled IP throughput
  • - Buffer Status Information (e.g., UL BSR)
As specified in 3GPP TS 28.552 [6], 3GPP TS 38.314 [16], 3GPP TS 38.423 [19], 3GPP TS 38.473 [21], 3GPP TS 38.463 [20], 3GPP TS 38.321 [17] | -| UE L1/L2/L3 measurements |
  • - RSRP, SS-RSRP and RSRQ measurements
  • - SINR measurements
  • - CQI measurements
  • - MCS measurements
  • - Location and Velocity measurements
  • - Timing advance measurements
As specified in 3GPP TS 38.331 [18], 3GPP TS 28.552 [6] | -| Energy consumption measurement | Energy consumption measurement of O-RU
  • - PNF Power Consumption (average/min/max)
  • - PNF Energy Consumption (average/min/max)
As specified in 3GPP TS 28.552 [6] | -| Mobility and RA related KPIs/measurements of UE/UE group | Mobility and RA related KPIs/measurements from the E2 nodes hosting the target NES cell(s) and/or the neighbour cell(s) to the target NES cell(s)
  • - Handover failure related, e.g., number of handover failures related to MRO
  • - RACH failure related, e.g., distribution of RACH access delay
  • - Radio link failure reports
  • - UE context release related, e.g., number of UE context release requests
As specified in 3GPP TS 38.331 [18], 3GPP 28.552 [6] | - -##### 4.6.4.4.4 E2 node configuration - -Cell level configuration parameters are needed at Near-RT RIC to support PRB blanking optimization. - -O-RU and O-DU TRX control capabilities, see O-RAN.WG4.MP.0-R003-v17.01 [39], clause 20.3.1, trx-control-capability-info, along with information about the mapping from cells to sector carriers and to O-RU are retrieved from O-DU to generate applicable and optimized performance including energy saving related policies and controls. - -### 4.6.5 Deep hibernate - -#### 4.6.5.1 Background and goal of the use case - -This use case addresses Network Energy Saving (NES) – Deep hibernate for O-RUs. WG4 defines a standardized deep-hibernate mechanism on the O-RU M-plane that allows an O-RU to enter an extended low-power state with a controlled wake-up. Building on that device-level capability, this use case places the decision of when/where/how long to hibernate under policy-driven, near-real-time control in the RAN via the E2 interface, while keeping all WG4 procedures unchanged. - -Traffic demand in modern RANs exhibits strong spatial and temporal variability. During prolonged low-traffic windows (e.g., night-time, special events), shutting down carriers alone may not deliver sufficient savings. Deep hibernate enables deeper power reduction by suspending M-plane activity on eligible O-RUs for a bounded duration. - -To ensure safe and efficient operation at network scale, the Non-RT RIC (in SMO) provides objectives and constraints as A1 policies. The Near-RT RIC evaluates live measurements and capabilities, determines eligible cells/sectors, and commands deep-hibernate via E2 to the E2 node, which then realizes the action using existing WG4 mechanisms (e.g., invoking the standardized deep-hibernate RPC toward the O-RU after verifying prerequisites such as carrier deactivation). - -The goal of this use case is to reduce RAN energy consumption while maintaining required service levels by: - -- selecting eligible cells/sectors for deep hibernate based on KPIs, coverage/mobility context, and O-RU capability limits (min/max duration, wake behavior); -- enforcing operator intent through A1 policy while allowing either RIC POLICY or RIC CONTROL over E2 to carry the command; -- ensuring guardrails and safety checks (e.g., emergency service protection, active-carrier checks, exclusion areas) before activation, with clear rejection causes when conditions are not met; -- providing state visibility (e.g., “deep-hibernate active”, remaining timer) to the Near-RT RIC for closed-loop coordination and suppression of conflicting actions. - -The scope is limited to orchestration over A1/E2 and closed-loop decisioning in the Near-RT RIC; WG4 M-plane procedures and RPC semantics remain unchanged. Relevant O-RU capabilities (e.g., support for deep hibernate and duration limits) are assumed to be available to the controller. The use case applies irrespective of processing mode baseline (mode 0), background (mode 1) and A1 policy based (mode 2). The use-case implementation in WG3 does not mandate any specific wake-up trigger beyond those already supported by the O-RU. - -#### 4.6.5.2 Entities/resources involved in the use case - -See clause 4.6.1.2. - -#### 4.6.5.3 Solution - -The three processing modes, baseline (mode 0), background (mode 1) and A1 policy based (mode 2), as described in clause 4.1.3 for traffic steering use case applies to this use case also. - -The context of energy saving deep hibernate use case is captured in table 4.6.5.3-1. - -**Table 4.6.5.3-1: Energy saving deep hibernate use case** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Drive energy saving deep hibernate in accordance with RAN OAM configured background behavior (ES mode 1) or policies information from the Non-RT RIC using A1 interface (ES mode 2). | NES | -| Actors and Roles |
  • - Non-RT RIC (SMO): Creates and updates A1 policies; provides A1-EI (optional).
  • - Near-RT RIC: Enforces A1 policies and generates RIC POLICY/CONTROL; consumes capability/state over E2.
  • - E2 node: Executes RIC POLICY/CONTROL and creates RIC INDICATION; retrieves and maintains O-RU deep-hibernate capability (support; min/max hibernateDuration) from the O-RU via WG4 M-plane and exposes capability/state to the Near-RT RIC over E2.

Refer to 4.6.5.2 for more details.

| | -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - A1, O1 and E2 connectivity are established.
  • - A1 policy scope defined
  • - E2 node maintains deep-hibernate capability obtained from the O-RU via WG4 M-plane and can expose it to the Near-RT RIC over E2.
| | - -| | | | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Pre conditions |
  • - Network is operational with default configuration.
  • - OAM functions have configured a baseline measurement configuration and the Non-RT RIC has access to this data.
  • - OAM functions have configured baseline ES parameters in E2 node(s) through O1 interface.
  • - (optional) If ES mode 1, OAM functions have configured background ES behavior to the Near-RT RIC through O1 interface.
  • - Non-RT RIC analyzes the historical data from RAN 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 non-real-time optimization of configuration and policies.
| | -| Begins when | Energy saving deep hibernate optimization is activated, or an operator defined trigger is detected. | | -| Step 1 (O) | (Start of outer loop control)
If ES mode 2, OAM functions collect data from E2 node through O1 interface. | | -| Step 2 (O) | Non-RT RIC retrieves ES related performance data from OAM function. | | -| Step 3 (O) | Non-RT RIC evaluates the collected data and A1 policy feedback, if required, and generates or updates the appropriate ES optimization policy. | | -| Step 4 (O) | Non-RT RIC sends the ES optimization policy to Near-RT RIC via A1 interface. | | -| Step 5 (O) | Non-RT RIC sends optional ES related A1 enrichment information. | | -| Step 6 (O) | If ES mode 1, Near-RT RIC collects data from E2 node through E2 interface. | | -| Step 7 (O) | Near-RT RIC evaluates the collected data, if required, generates, or updates the internal background mode ES optimization targets or policies. | | -| Step 8 (M) | (Start of inner loop control)
Near-RT RIC subscribes to a UE context information, measurement metrics via E2 interface and request deep hibernate capabilities. | | -| Step 9 (M) | E2 nodes report the UE context information, deep hibernate capabilities, and E2 measurements via RIC REPORT periodically or event triggered. | | -| Step 10 (M) | Near-RT RIC evaluates the performance data from E2 nodes and finds potential improvements to energy efficiency which are indicated in the A1 policy and/or internal Near-RT RIC TS targets. | | -| Step 11 (O) | Based on the UE context information, E2 measurement metrics (RIC REPORT), and A1 policy, Near-RT RIC may generate new or modify the existing E2 policies including deep hibernate and sends them to E2 nodes. | | -| Step 12 (O) | Near-RT RIC may also generate preparatory control command(s) such as radio-access and/or mobility controls via E2 RIC POLICY/CONTROL and send them to E2 node(s).
E2 node functions target of E2 control command may be:
  • - Same as Step 11
(End of inner loop control) | | -| Step 13 (O) | For ES mode 2, Near RT-RIC may send A1 policy feedback on A1 to the Non RT-RIC.
(End of outer loop control) | | -| Step 14 (O) | Non-RT RIC decides to delete ES optimization policy in case of ES mode 2 and sends the related messages. | | -| Step 15,16 (M) | Following A1 policy deletion (mode 2) or internal trigger (mode 1), the Near-RT RIC terminates the ES optimization procedure and delete the related RIC subscriptions. | | -| Ends when | Deep-hibernate is deactivated, or an operator-defined termination condition occurs. | | -| Exceptions | None. | | -| Post Conditions | Energy saving over a period of time is achieved. | | -| Traceability | REQ-E2-ES-FUN10 | | - -``` -@startuml -autonumber -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 -``` - -``` - -Box "Service Management and Orchestration" #gold - Participant OAM as "OAM Functions" - Participant non as "Non-RT RIC" -End box - -Box "O-RAN" #lightpink - Participant near as "Near-RT RIC" - Participant ran as "E2 Node" -End box - -group OUTER LOOP CONTROL - - OAM <--> ran : (Mode 2) <> RAN Data collection - OAM --> non: (Mode 2) ES related performance information - non --> non: (Mode 2) Collected data evaluation and policy creation - - non --> near : (Mode 2) <> A1 policy setup or update - non --> near: (opt.) <> ES related A1 enrichment information - near <--> ran: (Mode 1) <> RAN Data collection - near --> near: (Mode 1) Collected data evaluation and policy creation - - group INNER LOOP CONTROL - near -> ran : <> RIC SUBSCRIPTION REQUEST(UE context & DH capability & measurement metrics) - ran -> near: <> RIC INDICATION (UE context & DH capability & E2 measurement metrics) - near -> near: Evaluation, potential improvement to energy efficiency - near -> ran : (opt.) <> RIC SUBSCRIPTION REQUEST (ES optimisation POLICY) - near -> ran : (opt.) <> RIC CONTROL REQUEST (access and/or mobility for ES optimisation) - end - - non <-- near: (Mode 2) <> A1 policy feedback - -end -non --> near: (Mode 2) <> A1 policy delete -near -> near: ES optimization stopped -near-> ran: <> RIC SUBSCRIPTION DELETE -@enduml - -``` - -The flow diagram of the energy saving deep hibernate use case is given in figure 4.6.5.3-1. - -![Sequence diagram for Energy saving deep hibernate. The diagram shows interactions between Service Management and Orchestration (OAM Functions, Non-RT RIC) and O-RAN (Near-RT RIC, E2 Node). It is divided into OUTER LOOP CONTROL and INNER LOOP CONTROL. Messages include RAN data collection, policy creation, policy setup/update, feedback, delete, optimization stopped, and subscription delete.](909726977de6efd2d4df015198a2907b_img.jpg) - -``` - -sequenceDiagram - participant SM as Service Management and Orchestration - subgraph SM [Service Management and Orchestration] - OAM[OAM Functions] - NRT[Non-RT RIC] - end - subgraph ORAN [O-RAN] - NRT2[Near-RT RIC] - E2[E2 Node] - end - - Note left of SM: OUTER LOOP CONTROL - SM->>ORAN: 1 (Mode 2) «O1» RAN Data collection - ORAN-->>SM: 2 (Mode 2) E5 related performance information - SM->>ORAN: 3 (Mode 2) Collected data evaluation and policy creation - SM->>ORAN: 4 (Mode 2) «A1» A1 policy setup or update - SM->>ORAN: 5 (opt.) «A1-E5» E5 related A1 enrichment information - Note right of ORAN: INNER LOOP CONTROL - ORAN->>ORAN: 6 (Mode 1) «E2» RAN Data collection - ORAN-->>ORAN: 7 (Mode 1) Collected data evaluation and policy creation - ORAN->>ORAN: 8 «E2» RIC SUBSCRIPTION REQUEST(UE context & DH capability & measurement metrics) - ORAN-->>ORAN: 9 «E2» RIC INDICATION (UE context & DH capability & E2 measurement metrics) - ORAN-->>ORAN: 10 Evaluation, potential improvement to energy efficiency - ORAN->>ORAN: 11 (opt.) «E2» RIC SUBSCRIPTION REQUEST (ES optimisation POLICY) - ORAN->>ORAN: 12 (opt.) «E2» RIC CONTROL REQUEST (access and/or mobility for ES optimisation) - SM->>ORAN: 13 (Mode 2) «A1» A1 policy feedback - SM->>ORAN: 14 (Mode 2) «A1» A1 policy delete - ORAN-->>ORAN: 15 ES optimization stopped - ORAN->>ORAN: 16 «E2» RIC SUBSCRIPTION DELETE - -``` - -Sequence diagram for Energy saving deep hibernate. The diagram shows interactions between Service Management and Orchestration (OAM Functions, Non-RT RIC) and O-RAN (Near-RT RIC, E2 Node). It is divided into OUTER LOOP CONTROL and INNER LOOP CONTROL. Messages include RAN data collection, policy creation, policy setup/update, feedback, delete, optimization stopped, and subscription delete. - -Figure 4.6.5.3-1: Energy saving deep hibernate - -#### 4.6.5.4 Required data - -This clause elaborates the Near-RT RIC and the E2 node capabilities necessary specifically for implementation of the ES deep hibernate sub-use case. The required input data is specified in table 4.6.5.4-1 and output data specified in table 4.6.5.4-2. - -Table 4.6.5.4-1: Required input data specified for deep hibernate use case - -| Requirement | Category | Parameters / Measurements | Source | Reference | E2SM Reference | Interface | -|-------------------|---------------------------|---------------------------|----------------------------------|------------------------------------------------------------|----------------|-----------| -| Req-4.6.5.4-1-001 | Deep-hibernate capability | deepHibernateSupported | O-DU (from O-RU via WG4 M-plane) | O-RAN.WG4.MP.0-R003-v15 [35], clause 20.5 (Deep-hibernate) | | E2 | -| Req-4.6.5.4-1-002 | Deep-hibernate capability | minHibernateDuration | O-DU (from O-RU via WG4 M-plane) | O-RAN.WG4.MP.0-R003-v15 [35], clause 20.5 (Deep-hibernate) | | E2 | -| Req-4.6.5.4-1-003 | Deep-hibernate capability | maxHibernateDuration | O-DU (from O-RU via WG4 M-plane) | O-RAN.WG4.MP.0-R003-v15 [35], clause 20.5 (Deep-hibernate) | | E2 | - -Table 4.6.5.4-2: Required output data specified for deep hibernate use case - -| Requirement | Category | Parameters / Measurements | Target | Reference | E2SM Reference | Interface | -|-------------------|-----------------------|---------------------------|--------|-------------------------------------------|----------------|-----------| -| Req-4.6.5.4-2-001 | Deep-hibernate policy | hibernateDuration | O-DU | O-RAN.WG4.MP.0-R003-v15 [35], clause 20.5 | | E2 | - -| | | | | | | | -|--------------------------|-----------------------|-----------|------|------------------|--|----| -| | | | | (Deep-hibernate) | | | -| Req-4.6.5.4-2-002 | Deep-hibernate policy | startTime | O-DU | | | E2 | -| Req-4.6.5.4-2-003 | Deep-hibernate policy | endTime | O-DU | | | E2 | - -##### **4.6.5.4.1 Control over E2** - -###### **1) Radio access control (preparatory):** - -Access control may be applied to restrict access of additional UEs in the target scope (cells/sectors mapped to the O-RU) in order to prepare for O-RU deep-hibernate. A cell-level, UE-level, or slice-level access control can be applied. The following categories may be used: - -- RACH backoff -- RRC connection reject -- RRC connection release -- Access barring - -Both RIC POLICY and RIC CONTROL can be used. - -###### **2) Mobility control (preparatory):** - -Mobility may be steered so that active UEs are drained from the target scope prior to deep-hibernate. Examples include: - -- Handover from the source cell to a target neighbour cell -- Configuration/reconfiguration of handover restriction list -- Configuration of idle-mode mobility parameters -- Enable, disable, or modify carrier aggregation -- Enable, disable, or modify dual connectivity - -Both RIC POLICY and RIC CONTROL can be used. - -**3) Deep-hibernate policy/control:** The Near-RT RIC provides, via the E2 interface (RIC POLICY or RIC CONTROL), the intent to place eligible targets into deep-hibernate. The information includes the target scope (cells/sectors), with a given time range as well as an optional guidance for hibernate duration. - -The E2 can apply deep hibernation based on NES objectives, once or multiple times for a given hibernate duration, within the time range. The E2 node uses capability and topology information to validate prerequisites (e.g., carriers switched off) and translates the command into existing WG4 procedures toward the O-RU; result and state changes are reported over E2. - -Upon acceptance, the O-RU sends an activation notification and stops M-plane; it remains inaccessible until the timer expires, at which point it restarts and normal operation resumes. There is no command to wake an O-RU from deep-hibernate. - -##### **4.6.5.4.2 UE context information from E2 nodes** - -See clause 4.6.1.4.2. - -##### **4.6.5.4.3 Measurements from E2 nodes** - -See clause 4.6.1.4.3. - -##### 4.6.5.4.4 E2 node configuration - -The E2 node maintains the O-RU deep-hibernate capability information as defined in [35], clause 20.5 (support indicator and supported minimum/maximum hibernateDuration). The E2 node uses this information to validate prerequisites (e.g., all carriers are off), verify that the requested hibernateDuration is within the supported range and, if not, reject the request with an appropriate cause, and translate RIC POLICY/CONTROL into existing WG4 procedures toward the O-RU. - -### 4.6.6 Spatial and power domain - -#### 4.6.6.1 Background and goal of the use case - -In 3GPP Release-18 [14], clause 15.4.2.7, Spatial Domain (SD) and Power Domain (PD) adaptations were introduced. These features enable the gNB to dynamically adjust the number of active antenna elements and transmission power based on UE channel conditions. In the spatial domain, adaptive control allows antenna elements to be turned on or off depending on demand, while in the power domain, transmission power is adjusted according to the CSI (Channel State Information) reports provided by UEs. These adaptations optimize energy consumption of Transceiver Unit (TXRU) and Power Amplifier (PA) while maintaining service quality. - -Based on the UE traffic, channel and location prediction and knowledge of the O-RU capability info, Near-RT RIC can provide to E2 nodes a list of candidate sub-array patterns and PDSCH power offsets as potential choices. The E2 node then configure the UEs to measure for the candidate choices and select the best sub-array pattern and PDSCH power offset based on the UE measurements. - -Near-RT RIC can also apply traffic steering operation to steer Rel-18 UEs toward specific cells, enabling those cells to operate more efficiently. Or it can steer non-Rel-18 UEs out of cells optimized for power and spatial energy savings to maximize energy savings. - -The goal of Near-RT RIC energy saving is to interpret the policies received over A1 and to determine the optimum changes it can make according to these policies. More specifically, Near-RT RIC triggers E2 procedure and related control/policies so as to obtain network performance that would fulfill the criteria identified in the A1 policies. It may also leverage the A1 enrichment information to make more informed decisions. The Near-RT RIC may also work in background processing without the A1 policy guidance from the Non-RT RIC. - -#### 4.6.6.2 Entities/resources involved in the use case - -See clause 4.6.1.2. - -#### 4.6.6.3 Solution - -The three processing modes, baseline (mode 0), background (mode 1) and A1 policy based (mode 2), as described in clause 4.1.3 for traffic steering use case applies to this use case also. - -The context of energy saving spatial and power domain optimization is captured in table 4.6.6.3-1. - -**Table 4.6.6.3-1: Energy saving spatial and power domain optimization** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Drive energy saving spatial and power domain optimization in accordance with RAN OAM configured background behavior (ES mode 1) or policies information from the Non-RT RIC using A1 interface (ES mode 2). | | -| Actors and Roles |
  • - Non-RT RIC in SMO domain: Creates and updates A1 policies, provide A1 enrichment information.
  • - Near-RT RIC: Enforces A1 policies and generates RIC CONTROL and/or POLICY.
  • - E2 node: RIC CONTROL and POLICY execution and RIC REPORT creation.

Refer to 4.6.6.2 for more details.

| | - -| | | | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - A1, O1 and E2 interface connectivity is established.
  • - A1 policy scope defined.
| | -| Pre conditions |
  • - Network is operational with default configuration.
  • - OAM functions have configured a baseline measurement configuration and the Non-RT RIC has access to this data.
  • - OAM functions have configured baseline ES parameters in E2 node(s) through O1 interface.
  • - (optional) If ES mode 1, OAM functions have configured background ES behavior to the Near-RT RIC through O1 interface.
  • - Non-RT RIC analyzes the historical data from RAN 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 non-real-time optimization of configuration and policies.
| | -| Begins when | Energy saving spatial and power domain optimization is activated, or an operator defined trigger is detected. | | -| Step 1 (O) | (Start of outer loop control)
If ES mode 2, OAM functions collect data from E2 node through O1 interface. | | -| Step 2 (O) | Non-RT RIC retrieves ES related performance data from OAM function. | | -| Step 3 (O) | Non-RT RIC evaluates the collected data and A1 policy feedback, if required, and generates or updates the appropriate ES optimization policy. | | -| Step 4 (O) | Non-RT RIC sends the ES optimization policy to Near-RT RIC via A1 interface. | | -| Step 5 (O) | Non-RT RIC sends optional ES related A1 enrichment information. | | -| Step 6 (O) | If ES mode 1, Near-RT RIC collects data from E2 node through E2 interface. | | -| Step 7 (O) | Near-RT RIC evaluates the collected data, if required, generates, or updates the internal background mode ES optimization targets or policies. | | -| Step 8 (M) | (Start of inner loop control)
Near-RT RIC subscribes to a UE context information and measurement metrics via E2 interface. | | -| Step 9 (M) | E2 nodes report the UE context information and E2 measurements via RIC REPORT periodically or event triggered. | | -| Step 10 (M) | Near-RT RIC evaluates the performance data from E2 nodes and finds potential improvements to energy efficiency which are indicated in the A1 policy and/or internal Near-RT RIC TS targets. | | -| Step 11 (O) | Based on the UE context information, E2 measurement metrics (RIC REPORT), and A1 policy, Near-RT RIC may generate new or modify the existing E2 policies and sends them to E2 nodes.

E2 node functions target of E2 policy may be:
  • - Candidate sub-array patterns
  • - Candidate PDSCH power offset patterns
| | -| Step 12 (O) | Near-RT RIC may also generate control command(s) and send them to E2 node(s).

E2 node functions target of E2 control command may be:
  • - Same as Step 11
(End of inner loop control) | | -| Step 13 (O) | For ES mode 2, Near RT-RIC may send A1 policy feedback on A1 to the Non RT-RIC.
(End of outer loop control) | | -| Step 14 (O) | Non-RT RIC decides to delete ES optimization policy in case of ES mode 2 and sends the related messages. | | -| Step 15,16 (M) | Following A1 policy deletion (mode 2) or internal trigger (mode 1), the Near-RT RIC terminates the ES optimization procedure and deletes the related RIC subscriptions. | | -| Ends when | ES optimization is deactivated, or an operator defined trigger is detected. | | -| Exceptions | None. | | -| Post Conditions | Energy saving over a period of time is achieved. | | -| Traceability | REQ-Near-RT-RIC-ES-FUN8, REQ-E2-ES-FUN11 | | - -``` - -@startuml -autonumber -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Box "Service Management and Orchestration" #gold - Participant OAM as "OAM Functions" - Participant non as "Non-RT RIC" -End box - -Box "O-RAN" #lightpink - Participant near as "Near-RT RIC" - Participant ran as "E2 Node" -End box - -group OUTER LOOP CONTROL - - OAM <--> ran : (Mode 2) <> RAN Data collection - OAM --> non: (Mode 2) ES related performance information - non --> non: (Mode 2) Collected data evaluation and policy creation - - non --> near : (Mode 2) <> A1 policy setup or update - non --> near: (opt.) <> ES related A1 enrichment information - near <--> ran: (Mode 1) <> RAN Data collection - near --> near: (Mode 1) Collected data evaluation and policy creation - - group INNER LOOP CONTROL - near -> ran : <> RIC SUBSCRIPTION REQUEST(UE context & measurement metrics) - ran -> near: <> RIC INDICATION (UE context & E2 measurement metrics) - near -> near: Evaluation, potential improvement to energy efficiency - near -> ran : (opt.) <> RIC SUBSCRIPTION REQUEST (ES optimisation POLICY) - near -> ran : (opt.) <> RIC CONTROL REQUEST (ES optimisation RIC CONTROL) - end - - non <-- near: (Mode 2) <> A1 policy feedback - -end - -non --> near: (Mode 2) <> A1 policy delete -near -> near: ES optimization stopped -near-> ran: <> RIC SUBSCRIPTION DELETE -@enduml - -``` - -The flow diagram of the energy saving spatial and power domain optimization use case is given in figure 4.6.6.3-1. - -![Sequence diagram for Energy saving spatial and power domain optimization. It shows interactions between Service Management and Orchestration (OAM Functions, Non-RT RIC) and O-RAN (Near-RT RIC, E2 Node). The process is divided into OUTER LOOP CONTROL and INNER LOOP CONTROL. Steps include RAN data collection, policy creation, policy setup, evaluation, and optimization control requests.](cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg) - -``` - -sequenceDiagram - participant SM as Service Management and Orchestration - subgraph SM [Service Management and Orchestration] - OAM[OAM Functions] - NonRT[Non-RT RIC] - end - subgraph ORAN [O-RAN] - NearRT[Near-RT RIC] - E2[E2 Node] - end - - Note left of SM: OUTER LOOP CONTROL - SM->>E2: 1 (Mode 2) «O1» RAN Data collection - E2-->>SM: 2 (Mode 2) ES related performance information - SM->>NearRT: 3 (Mode 2) Collected data evaluation and policy creation - NearRT->>E2: 4 (Mode 2) «A1» A1 policy setup or update - E2-->>NearRT: 5 (opt.) «A1-EI» ES related A1 enrichment information - NearRT->>E2: 6 (Mode 1) «E2» RAN Data collection - E2-->>NearRT: 7 (Mode 1) Collected data evaluation and policy creation - - Note left of ORAN: INNER LOOP CONTROL - NearRT->>E2: 8 «E2» RIC SUBSCRIPTION REQUEST(UE context & measurement metrics) - E2-->>NearRT: 9 «E2» RIC INDICATION (UE context & E2 measurement metrics) - NearRT->>E2: 10 Evaluation, potential improvement to energy efficiency - NearRT->>E2: 11 (opt.) «E2» RIC SUBSCRIPTION REQUEST (ES optimisation POLICY) - NearRT->>E2: 12 (opt.) «E2» RIC CONTROL REQUEST (ES optimisation RIC CONTROL) - - SM->>NearRT: 13 (Mode 2) «A1» A1 policy feedback - NearRT->>E2: 14 (Mode 2) «A1» A1 policy delete - E2-->>NearRT: 15 ES optimization stopped - NearRT->>E2: 16 «E2» RIC SUBSCRIPTION DELETE - -``` - -Sequence diagram for Energy saving spatial and power domain optimization. It shows interactions between Service Management and Orchestration (OAM Functions, Non-RT RIC) and O-RAN (Near-RT RIC, E2 Node). The process is divided into OUTER LOOP CONTROL and INNER LOOP CONTROL. Steps include RAN data collection, policy creation, policy setup, evaluation, and optimization control requests. - -Figure 4.6.6.3-1: Energy saving spatial and power domain optimization - -#### 4.6.6.4 Required data - -This clause elaborates the Near-RT RIC and the E2 node capabilities necessary specifically for implementation of the spatial and power domain optimization use case. The required input data is specified in table 4.6.6.4-1 and output data specified in table 4.6.6.4-2. - -Table 4.6.6.4-1: Required input data for spatial and power domain optimization use case - -| Requirement | Category | Parameters / Measurements | Source | Reference | E2SM Reference | Interface | -|-------------------|------------------------|---------------------------------|----------------------------------|--------------------------------------------------------------------------------|------------------------------------------------|-----------| -| Req-4.6.6.4-1-001 | Trx control capability | supportedTrxControlMasks | O-DU (from O-RU via WG4 M-plane) | O-RAN.WG4.MP.0-R003-v15 [35], clause 20.3.1 (supported-trx-control-masks) | O-RAN.WG3.TS.E2SM-CCC-R004 [50], clause 9.3.40 | E2 | -| Req-4.6.6.4-1-002 | Trx control capability | sleepModes | O-DU (from O-RU via WG4 M-plane) | O-RAN.WG4.MP.0-R003-v15 [35], clause 20.3.1 (sleep-modes) | O-RAN.WG3.TS.E2SM-CCC-R004 [50], clause 9.3.40 | E2 | -| Req-4.6.6.4-1-003 | Trx control capability | definedDurationSleepSupported | O-DU (from O-RU via WG4 M-plane) | O-RAN.WG4.MP.0-R003-v15 [35], clause 20.3.1 (defined-duration-sleep-supported) | O-RAN.WG3.TS.E2SM-CCC-R004 [50], clause 9.3.40 | E2 | -| Req-4.6.6.4-1-004 | Trx control capability | undefinedDurationSleepSupported | O-DU (from O-RU via | O-RAN.WG4.MP.0-R003-v15 [35], clause | O-RAN.WG3.TS.E2SM-CCC-R004 [50], clause 9.3.40 | E2 | - -| | | | | | | | -|--------------------------|---------------------------|-------------------------|--------------|---------------------------------------------|--|----| -| | | | WG4 M-plane) | 20.3.1 (undefined-duration-sleep-supported) | | | -| Req-4.6.6.4-1-005 | UE capability information | UECapabilityInformation | O-CU | 3GPP TS 38.331 [18], clause 6.2.2.19 | | E2 | - -**Table 4.6.6.4-2: Required output data for spatial and power domain optimization use case** - -| Requirement | Category | Parameters / Measurements | Target | Reference | E2SM Reference | Interface | -|--------------------------|-----------------------|---------------------------|--------|------------------------------------------|----------------|-----------| -| Req-4.6.6.4-2-001 | CSI report sub-config | CSI-ReportSubConfig | O-CU | 3GPP TS 38.331 [18], CSI-ReportSubConfig | | E2 | - -##### **4.6.6.4.1 Control over E2** - -1) **Radio Access Control:** Access control may be applied to restrict access of non-Rel-18 UEs for a specific cell in order to achieve more energy saving for the cell. A cell-level, UE-level, or slice-level access control can be applied. Four categories of radio access control are indicated as below: - -- RACH Backoff -- RRC Connection Reject -- RRC Connection Release -- Access Barring - -Both RIC POLICY and RIC CONTROL can be used. - -2) **Mobility Control:** Access control may be applied to steer Rel-18 UEs to a specific cell in order to achieve more energy saving for the cell. The following procedures can be used for mobility control: - -- Handover from the source cell to the target cell -- Configuration/reconfiguration of handover restriction list -- Configuration of idle mode mobility parameters -- Enable, disable, or modify CA (3GPP TS 38.473 [21], 3GPP TS 38.331 [18], 3GPP TS 36.331 [11]) -- Enable, disable, or modify dual connectivity (3GPP TS 38.473 [21], 3GPP TS 38.331 [18], 3GPP TS 36.331 [11]) - -Both RIC POLICY and RIC CONTROL can be used. - -3) **Candidate sub-array patterns and PDSCH power offsets:** Based on the UE traffic, channel and location prediction and knowledge of the O-RU capability info, Near-RT RIC can provide to O-CU-CP a list of candidate sub-array patterns and PDSCH power offsets as potential choices for the current conditions. The O-CU-CP can then configure the Rel-18 UEs to measure the CSI for the candidate choices. O-DU can then select the best sub-array pattern and PDSCH power offset for transmission to the UEs based on the CSI measurements. The configurations may include: - -- Candidate subarray patterns to be measured and applied, 3GPP TS 38.331 [18], CSI-ReportSubConfig. -- Candidate PDSCH power offsets to be measured and applied, 3GPP TS 38.331 [18], CSI-ReportSubConfig. - -Either RIC POLICY or RIC CONTROL can be used. - -##### **4.6.6.4.2 UE context information from E2 nodes** - -In addition to clause 4.6.1.4.2, UE capability to support Rel-18 features, 3GPP TS 38.331 [18], clause 6.2.2.19, UECapabilityInformation. - -##### 4.6.6.4.3 Measurements from E2 nodes - -See clause 4.6.1.4.3. - -##### 4.6.6.4.4 E2 node configuration - -Cell level configuration parameters in order to configure UE measurements required for traffic steering and QoS/QoE optimization (see clause 4.1.4.4) for creating more spatial and power domain optimization opportunities to save energy while maintaining acceptable performance. - -O-RU and O-DU TRX control capabilities, see [35], clause 20.3.1, trx-control-capability-info, along with information about the mapping from cells to sector carriers and to O-RU are retrieved from O-DU in order to generate applicable and optimized energy saving related policies and controls. - -### 4.6.7 SSB-less SCell optimization - -#### 4.6.7.1 Background and goal of the use case - -3GPP Rel-18 [14], clause 15.4.2.6 introduces the concept of SSB-less SCell activation for carrier aggregation, which allows efficient use of secondary carriers without needing constant synchronization signals. This enhances spectral efficiency and data throughput for users with high demand, without burdening the network with unnecessary signaling. The SSB-less SCell operation for inter-band CA is designed to enhance energy efficiency while maintaining data throughput in carrier aggregation scenarios. By operating without the need for continuous synchronization signal block (SSB) transmissions, the network can reduce power consumption on secondary cells, particularly in periods of lower traffic demand. The primary goal of this use case is to maximize energy savings without degrading user experience by intelligently enabling and disabling SCells based on real-time traffic demand. - -Based on traffic prediction and A1 policy, Near-RT RIC can activate SSB-less SCells in appropriate cells to improve spectral efficiency while minimizing unnecessary synchronization transmissions, reducing power consumption during low-traffic periods. Near-RT RIC can also apply traffic steering operations to steer Rel-18 UEs toward SSB-less cells, enabling those cells to operate more efficiently. Or it can steer non-Rel-18 UEs out of SSB-less cells to maximize energy savings. - -The goal of Near-RT RIC energy saving is to interpret the policies received over A1 and to determine the optimum changes it can make according to these policies. More specifically, Near-RT RIC triggers E2 procedure and related control/policies so as to obtain network performance that would fulfill the criteria identified in the A1 policies. It may also leverage the A1 enrichment information to make more informed decisions. The Near-RT RIC may also work in background processing without the A1 policy guidance from the Non-RT RIC. - -#### 4.6.7.2 Entities/resources involved in the use case - -See clause 4.6.1.2. - -#### 4.6.7.3 Solution - -The three processing modes, baseline (mode 0), background (mode 1) and A1 policy based (mode 2), as described in clause 4.1.3 for traffic steering use case applies to this use case also. - -The context of energy saving SSB-less SCell optimization is captured in table 4.6.7.3-1. - -**Table 4.6.7.3-1: Energy saving SSB-less SCell optimization** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Drive energy saving SSB-less SCell optimization in accordance with RAN OAM configured background behavior (ES mode 1) or policies information from the Non-RT RIC using A1 interface (ES mode 2). | | -| Actors and Roles | - Non-RT RIC in SMO domain: Creates and updates A1 policies, provide A1 enrichment information. | | - -| | | | -|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |
  • - Near-RT RIC: Enforces A1 policies and generates RIC CONTROL and/or POLICY.
  • - E2 node: RIC CONTROL and POLICY execution and RIC REPORT creation.

Refer to 4.6.7.2 for more details.

| | -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - A1, O1 and E2 interface connectivity is established.
  • - A1 policy scope defined.
| | -| Pre conditions |
  • - Network is operational with default configuration.
  • - OAM functions have configured a baseline measurement configuration and the Non-RT RIC has access to this data.
  • - OAM functions have configured baseline ES parameters in E2 node(s) through O1 interface.
  • - (optional) If ES mode 1, OAM functions have configured background ES behavior to the Near-RT RIC through O1 interface.
  • - Non-RT RIC analyzes the historical data from RAN 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 non-real-time optimization of configuration and policies.
| | -| Begins when | Energy saving SSB-less SCell optimization is activated, or an operator defined trigger is detected. | | -| Step 1 (O) | (Start of outer loop control)
If ES mode 2, OAM functions collect data from E2 node through O1 interface. | | -| Step 2 (O) | Non-RT RIC retrieves ES related performance data from OAM function. | | -| Step 3 (O) | Non-RT RIC evaluates the collected data and A1 policy feedback, if required, and generates or updates the appropriate ES optimization policy. | | -| Step 4 (O) | Non-RT RIC sends the ES optimization policy to Near-RT RIC via A1 interface. | | -| Step 5 (O) | Non-RT RIC sends optional ES related A1 enrichment information. | | -| Step 6 (O) | If ES mode 1, Near-RT RIC collects data from E2 node through E2 interface. | | -| Step 7 (O) | Near-RT RIC evaluates the collected data, if required, generates, or updates the internal background mode ES optimization targets or policies. | | -| Step 8 (M) | (Start of inner loop control)
Near-RT RIC subscribes to a UE context information and measurement metrics via E2 interface. | | -| Step 9 (M) | E2 nodes report the UE context information and E2 measurements via RIC REPORT periodically or event triggered. | | -| Step 10 (M) | Near-RT RIC evaluates the performance data from E2 nodes and finds potential improvements to energy efficiency which are indicated in the A1 policy and/or internal Near-RT RIC TS targets. | | -| Step 11 (O) | Based on the UE context information, E2 measurement metrics (RIC REPORT), and A1 policy, Near-RT RIC may generate new or modify the existing E2 policies and sends them to E2 nodes.

E2 node functions target of E2 policy may be:
  • - Activation or deactivation of SSB-less SCell on specific cells.
| | -| Step 12 (O) | Near-RT RIC may also generate control command(s) and send them to E2 node(s).

E2 node functions target of E2 control command may be:
  • - Same as Step 11

(End of inner loop control)

| | -| Step 13 (O) | For ES mode 2, Near RT-RIC may send A1 policy feedback on A1 to the Non RT-RIC.
(End of outer loop control) | | -| Step 14 (O) | Non-RT RIC decides to delete ES optimization policy in case of ES mode 2 and sends the related messages. | | -| Step 15,16 (M) | Following A1 policy deletion (mode 2) or internal trigger (mode 1), the Near-RT RIC terminates the ES optimization procedure and deletes the related RIC subscriptions. | | -| Ends when | ES optimization is deactivated, or an operator defined trigger is detected. | | - -| | | | -|-----------------|--------------------------------------------------|--| -| Exceptions | None. | | -| Post Conditions | Energy saving over a period of time is achieved. | | -| Traceability | REQ-Near-RT-RIC-ES-FUN9, REQ-E2-ES-FUN12 | | - -``` - -@startuml -autonumber -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Box "Service Management and Orchestration" #gold - Participant OAM as "OAM Functions" - Participant non as "Non-RT RIC" -End box - -Box "O-RAN" #lightpink - Participant near as "Near-RT RIC" - Participant ran as "E2 Node" -End box - -group OUTER LOOP CONTROL - - OAM <--> ran : (Mode 2) <> RAN Data collection - OAM --> non: (Mode 2) ES related performance information - non --> non: (Mode 2) Collected data evaluation and policy creation - - non --> near : (Mode 2) <> A1 policy setup or update - non --> near: (opt.) <> ES related A1 enrichment information - near <--> ran: (Mode 1) <> RAN Data collection - near --> near: (Mode 1) Collected data evaluation and policy creation - - group INNER LOOP CONTROL - near -> ran : <> RIC SUBSCRIPTION REQUEST(UE context & measurement metrics) - ran -> near: <> RIC INDICATION (UE context & E2 measurement metrics) - near -> near: Evaluation, potential improvement to energy efficiency - near -> ran : (opt.) <> RIC SUBSCRIPTION REQUEST (ES optimisation POLICY) - near -> ran : (opt.) <> RIC CONTROL REQUEST (ES optimisation RIC CONTROL) - end - - non <-- near: (Mode 2) <> A1 policy feedback - -end - -non --> near: (Mode 2) <> A1 policy delete -near -> near: ES optimization stopped -near-> ran: <> RIC SUBSCRIPTION DELETE -@enduml - -``` - -The flow diagram of the energy saving SSB-less SCell optimization is given in figure 4.6.7.3-1. - -![Sequence diagram for Energy saving SSB-less SCell optimization. It shows interactions between Service Management and Orchestration (OAM Functions, Non-RT RIC) and O-RAN (Near-RT RIC, E2 Node). The process is divided into OUTER LOOP CONTROL and INNER LOOP CONTROL. Steps include data collection, policy creation, policy setup, evaluation, and optimization control.](3d1817e8551f9c226a5f561108d3b3f9_img.jpg) - -``` - -sequenceDiagram - participant SM&O as Service Management and Orchestration - subgraph SM&O - OAM1[OAM Functions] - NonRT1[Non-RT RIC] - end - subgraph ORAN - NearRT[Near-RT RIC] - E2[E2 Node] - end - - Note left of SM&O: OUTER LOOP CONTROL - OAM1->>NonRT1: 1 (Mode 2) «O1» RAN Data collection - NonRT1->>E2: 2 (Mode 2) ES related performance information - E2-->>NonRT1: 3 (Mode 2) Collected data evaluation and policy creation - NonRT1->>E2: 4 (Mode 2) «A1» A1 policy setup or update - E2-->>NonRT1: 5 (opt) «A1-EI» ES related A1 enrichment information - - Note left of ORAN: INNER LOOP CONTROL - NearRT->>E2: 6 (Mode 1) «E2» RAN Data collection - E2-->>NearRT: 7 (Mode 1) Collected data evaluation and policy creation - NearRT->>E2: 8 «E2» RIC SUBSCRIPTION REQUEST(UE context & measurement metrics) - E2-->>NearRT: 9 «E2» RIC INDICATION (UE context & E2 measurement metrics) - NearRT->>E2: 10 Evaluation, potential improvement to energy efficiency - NearRT->>E2: 11 (opt) «E2» RIC SUBSCRIPTION REQUEST (ES optimisation POLICY) - NearRT->>E2: 12 (opt) «E2» RIC CONTROL REQUEST (ES optimisation RIC CONTROL) - - Note left of SM&O: OUTER LOOP CONTROL - NonRT1->>E2: 13 (Mode 2) «A1» A1 policy feedback - E2-->>NonRT1: 14 (Mode 2) «A1» A1 policy delete - NearRT->>E2: 15 ES optimization stopped - E2-->>NearRT: 16 «E2» RIC SUBSCRIPTION DELETE - -``` - -Sequence diagram for Energy saving SSB-less SCell optimization. It shows interactions between Service Management and Orchestration (OAM Functions, Non-RT RIC) and O-RAN (Near-RT RIC, E2 Node). The process is divided into OUTER LOOP CONTROL and INNER LOOP CONTROL. Steps include data collection, policy creation, policy setup, evaluation, and optimization control. - -Figure 4.6.7.3-1: Energy saving SSB-less SCell optimization - -#### 4.6.7.4 Required data - -This clause elaborates the Near-RT RIC and the E2 node capabilities necessary specifically for implementation of the SSB-less SCell optimization use case. The required input data is specified in table 4.6.7.4-1 and output data specified in table 4.6.7.4-2. - -Table 4.6.7.4-1: Required input data for SSB-less SCell optimization use case - -| Requirement | Category | Parameters / Measurements | Source | Reference | E2SM Reference | Interface | -|-------------------|---------------------------|---------------------------|--------|--------------------------------------|----------------|-----------| -| Req-4.6.7.4-1-001 | UE capability information | UECapabilityInformation | O-CU | 3GPP TS 38.331 [18], clause 6.2.2.19 | | E2 | - -Table 4.6.7.4-2: Required output data for SSB-less SCell optimization use case - -| Requirement | Category | Parameters / Measurements | Target | Reference | E2SM Reference | Interface | -|-------------------|--------------------------------------------------------------|---------------------------|--------|-----------|----------------|-----------| -| Req-4.6.7.4-2-001 | Parameters related to SSB-less SCell activation/deactivation | | O-CU | | | E2 | - -##### 4.6.7.4.1 Control over E2 - -1) **Radio Access Control:** Access control may be applied to restrict access of non-Rel-18 UEs for SSB-less cell in order to achieve more energy saving for the cell. A cell-level, UE-level, or slice-level access control can be applied. Four categories of radio access control are indicated as below: - -- RACH Backoff -- RRC Connection Reject -- RRC Connection Release -- Access Barring - -Both RIC POLICY and RIC CONTROL can be used. - -2) **Mobility Control:** Mobility control may be applied to steer Rel-18 UEs to SSB-less cell in order to achieve more energy saving for the cell. The following procedures can be used for mobility control: - -- Handover from the source cell to the target cell -- Configuration/reconfiguration of handover restriction list -- Configuration of idle mode mobility parameters -- Enable, disable, or modify CA (3GPP TS 38.473 [21], 3GPP TS 38.331 [18], 3GPP TS 36.331 [11]) -- Enable, disable, or modify dual connectivity (3GPP TS 38.473 [21], 3GPP TS 38.331 [18], 3GPP TS 36.331 [11]) - -Both RIC POLICY and RIC CONTROL can be used. - -3) **Activate/deactivate SSB-less SCell:** Based on the traffic prediction and A1 policy, activate/deactivate SSB-less SCell operation in appropriate cells to improve spectral efficiency. The configurations may include: - -- Parameters related to SSB-less SCell activation/deactivation. - -Either RIC POLICY or RIC CONTROL can be used. - -##### 4.6.7.4.2 UE context information from E2 nodes - -In addition to clause 4.6.1.4.2, UE capability to support Rel-18 features, 3GPP TS 38.331 [18], clause 6.2.2.19, UECapabilityInformation. - -##### 4.6.7.4.3 Measurements from E2 nodes - -See clause 4.6.1.4.3. - -##### 4.6.7.4.4 E2 node configuration - -Cell level configuration parameters in order to configure UE measurements required for traffic steering and QoS/QoE optimization (see clause 4.1.4.4) for creating more SSB-less SCell optimization opportunities to save energy while maintaining acceptable performance. - -### 4.6.8 PA power optimization - -#### 4.6.8.1 Background and goal of the use case - -The O-RU energy saving could be achieved by optimizing its Power Amplifier (PA) operating region according to the traffic scheduling requirements, to reduce the O-RU power consumption. To facilitate this, the Near-RT RIC analyses various network data and KPIs to prepare policy or configuration changes for the O-DU. The O-DU then evaluates the conditions specified in the policies or applies the configuration changes provided by the Near-RT RIC. When those conditions are satisfied or based on requested configuration changes, the O-DU configures the maximum output power of the O-RU via fronthaul M-plane or C-plane interface. The O-RU subsequently optimizes its power amplifier parameters according to the configured maximum output power. This could result in a reduction of PA power consumption, thereby achieving energy saving in O-RU and enhance the overall energy efficiency of the O-RAN network. - -The goal of Near-RT RIC energy saving is to interpret the policies received over A1 and to determine the optimum changes it can make according to these policies. More specifically, Near-RT RIC triggers E2 procedure and related control/policies so as to obtain network performance that would fulfill the criteria identified in the A1 policies. It may also leverage the A1 enrichment information to make more informed decisions. The Near-RT RIC may also work in background processing without the A1 policy guidance from the Non-RT RIC. - -#### 4.6.8.2 Entities/resources involved in the use case - -See clause 4.6.1.2. - -#### 4.6.8.3 Solution - -The three processing modes, baseline (mode 0), background (mode 1) and A1 policy based (mode 2), as described in clause 4.1.3 for traffic steering use case applies to this use case also. - -The context of energy saving PA power optimization is captured in table 4.6.8.3-1. - -**Table 4.6.8.3-1: Energy saving PA power optimization** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Drive energy saving PA optimization in accordance with RAN OAM configured background behavior (ES mode 1) or policies information from the Non-RT RIC using A1 interface (ES mode 2). | | -| Actors and Roles |
  • - Non-RT RIC in SMO domain: Creates and updates A1 policies, provide A1 enrichment information.
  • - Near-RT RIC: Enforces A1 policies and generates RIC CONTROL and/or POLICY.
  • - E2 node: RIC CONTROL and POLICY execution and RIC REPORT creation.
Refer to 4.6.8.2 for more details. | | -| Assumptions |
  • - All relevant functions and components are instantiated.
  • - A1, O1 and E2 interface connectivity is established.
  • - A1 policy scope defined.
| | -| Pre conditions |
  • - Network is operational with default configuration.
  • - OAM functions have configured a baseline measurement configuration and the Non-RT RIC has access to this data.
  • - OAM functions have configured baseline ES parameters in E2 node(s) through O1 interface.
  • - (optional) If ES mode 1, OAM functions have configured background ES behavior to the Near-RT RIC through O1 interface.
  • - Non-RT RIC analyzes the historical data from RAN 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 non-real-time optimization of configuration and policies.
| | -| Begins when | Energy saving PA power optimization is activated, or an operator defined trigger is detected. | | -| Step 1 (O) | (Start of outer loop control)
If ES mode 2, OAM functions collect data from E2 node through O1 interface. | | -| Step 2 (O) | Non-RT RIC retrieves ES related performance data from OAM function. | | -| Step 3 (O) | Non-RT RIC evaluates the collected data and A1 policy feedback, if required, and generates or updates the appropriate ES optimization policy. | | -| Step 4 (O) | Non-RT RIC sends the ES optimization policy to Near-RT RIC via A1 interface. | | -| Step 5 (O) | Non-RT RIC sends optional ES related A1 enrichment information. | | -| Step 6 (O) | If ES mode 1, Near-RT RIC collects data from E2 node through E2 interface. | | -| Step 7 (O) | Near-RT RIC evaluates the collected data, if required, generates, or updates the internal background mode ES optimization targets or policies. | | -| Step 8 (M) | (Start of inner loop control)
Near-RT RIC subscribes to a UE context information and measurement metrics via E2 interface. | | -| Step 9 (M) | E2 nodes report the UE context information and E2 measurements via RIC REPORT periodically or event triggered. | | -| Step 10 (M) | Near-RT RIC evaluates the performance data from E2 nodes and finds potential improvements to energy efficiency which are indicated in the A1 policy and/or internal Near-RT RIC TS targets. | | -| Step 11 (O) | Based on the UE context information, E2 measurement metrics (RIC REPORT), and A1 policy, Near-RT RIC may generate new or modify the existing E2 policies and sends them to E2 nodes. | | -| Step 12 (O) | Near-RT RIC may also generate control command(s) and send them to E2 node(s).
E2 node functions target of E2 control command may be: | | - -| | | | -|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | - Same as Step 11

(End of inner loop control) | | -| Step 13 (O) | For ES mode 2, Near RT-RIC may send A1 policy feedback on A1 to the Non RT-RIC.
(End of outer loop control) | | -| Step 14 (O) | Non-RT RIC decides to delete ES optimization policy in case of ES mode 2 and sends the related messages. | | -| Step 15,16 (M) | Following A1 policy deletion (mode 2) or internal trigger (mode 1), the Near-RT RIC terminates the ES optimization procedure and deletes the related RIC subscriptions. | | -| Ends when | ES optimization is deactivated, or an operator defined trigger is detected. | | -| Exceptions | None. | | -| Post Conditions | Energy saving over a period of time is achieved. | | -| Traceability | REQ-E2-ES-FUN13 | | - -``` - -@startuml -autonumber -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Box "Service Management and Orchestration" #gold - Participant OAM as "OAM Functions" - Participant non as "Non-RT RIC" -End box - -Box "O-RAN" #lightpink - Participant near as "Near-RT RIC" - Participant ran as "E2 Node" -End box - -group OUTER LOOP CONTROL - - OAM <--> ran : (Mode 2) <> RAN Data collection - OAM --> non: (Mode 2) ES related performance information - non --> non: (Mode 2) Collected data evaluation and policy creation - - non --> near : (Mode 2) <> A1 policy setup or update - non --> near: (opt.) <> ES related A1 enrichment information - near <--> ran: (Mode 1) <> RAN Data collection - near --> near: (Mode 1) Collected data evaluation and policy creation - - group INNER LOOP CONTROL - near -> ran : <> RIC SUBSCRIPTION REQUEST(UE context & measurement metrics) - ran -> near: <> RIC INDICATION (UE context & E2 measurement metrics) - near -> near: Evaluation, potential improvement to energy efficiency - near -> ran : (opt.) <> RIC SUBSCRIPTION REQUEST (ES optimisation POLICY) - near -> ran : (opt.) <> RIC CONTROL REQUEST (ES optimisation RIC CONTROL) - end - - non <-- near: (Mode 2) <> A1 policy feedback - -end - -non --> near: (Mode 2) <> A1 policy delete -near -> near: ES optimization stopped -near-> ran: <> RIC SUBSCRIPTION DELETE -@enduml - -``` - -The flow diagram of the energy saving PA power optimization is given in figure 4.6.8.3-1. - -![Sequence diagram for Energy saving PA power optimization. It shows interactions between Service Management and Orchestration (OAM Functions, Non-RT RIC) and O-RAN (Near-RT RIC, E2 Node). The process is divided into OUTER LOOP CONTROL and INNER LOOP CONTROL. Steps include RAN data collection, policy creation, policy setup, evaluation, and optimization control requests.](4c1ea859b93043f2fa17a8fe72fb6176_img.jpg) - -``` - -sequenceDiagram - participant SM as Service Management and Orchestration - subgraph SM [Service Management and Orchestration] - OAM[OAM Functions] - NonRT[Non-RT RIC] - end - subgraph ORAN [O-RAN] - NearRT[Near-RT RIC] - E2[E2 Node] - end - - Note left of SM: OUTER LOOP CONTROL - SM->>E2: 1 (Mode 2) «O1» RAN Data collection - E2-->>SM: 2 (Mode 2) ES related performance information - SM->>NearRT: 3 (Mode 2) Collected data evaluation and policy creation - NearRT->>E2: 4 (Mode 2) «A1» A1 policy setup or update - E2-->>SM: 5 (opt.) «A1-EI» ES related A1 enrichment information - Note right of ORAN: INNER LOOP CONTROL - NearRT->>E2: 6 (Mode 1) «E2» RAN Data collection - E2-->>NearRT: 7 (Mode 1) Collected data evaluation and policy creation - NearRT->>E2: 8 «E2» RIC SUBSCRIPTION REQUEST(UE context & measurement metrics) - E2-->>NearRT: 9 «E2» RIC INDICATION (UE context & E2 measurement metrics) - NearRT->>E2: 10 Evaluation, potential improvement to energy efficiency - NearRT->>E2: 11 (opt.) «E2» RIC SUBSCRIPTION REQUEST (ES optimisation POLICY) - NearRT->>E2: 12 (opt.) «E2» RIC CONTROL REQUEST (ES optimisation RIC CONTROL) - E2-->>SM: 13 (Mode 2) «A1» A1 policy feedback - SM->>NearRT: 14 (Mode 2) «A1» A1 policy delete - NearRT->>E2: 15 ES optimization stopped - E2-->>NearRT: 16 «E2» RIC SUBSCRIPTION DELETE - -``` - -Sequence diagram for Energy saving PA power optimization. It shows interactions between Service Management and Orchestration (OAM Functions, Non-RT RIC) and O-RAN (Near-RT RIC, E2 Node). The process is divided into OUTER LOOP CONTROL and INNER LOOP CONTROL. Steps include RAN data collection, policy creation, policy setup, evaluation, and optimization control requests. - -Figure 4.6.8.3-1: Energy saving PA power optimization - -#### 4.6.8.4 Required data - -This clause elaborates the Near-RT RIC and the E2 node capabilities necessary specifically for implementation of the PA power optimization use case. The required input data is specified in table 4.6.8.4-1 and output data specified in table 4.6.8.4-2. - -Table 4.6.8.4-1: Required data for PA power optimization use case - -| Requirement | Category | Parameters / Measurements | Source | Reference | E2SM Reference | Interface | -|-------------------|-----------------------------------------|---------------------------------|----------------------------------|-----------------------------------------------------------------------------------|----------------|-----------| -| Req-4.6.8.4-1-001 | Maximum output power control capability | maxPowerControlMethodsSupported | O-DU (from O-RU via WG4 M-plane) | O-RAN.WG4.MP.0-R003-v15 [35], clause 20.6.1 (max-power-control-methods-supported) | | E2 | -| Req-4.6.8.4-1-002 | Maximum output power control capability | supportedMaxPowerLevel | O-DU (from O-RU via WG4 M-plane) | O-RAN.WG4.MP.0-R003-v15 [35], clause 20.6.1 (supported-max-power-level) | | E2 | - -Table 4.6.8.4-2: Required output data for PA power optimization use case - -| Requirement | Category | Parameters / Measurements | Target | Reference | E2SM Reference | Interface | -|-------------------|------------------------------|------------------------------|--------|-----------|------------------------------------------------|-----------| -| Req-4.6.8.4-2-001 | Total number of blanked PRBs | prbBlankingConfigurationList | O-DU | | O-RAN.WG3.TS.E2SM-CCC-R004 [50], clause 9.3.45 | E2 | -| Req-4.6.8.4-2-002 | Targeted total number | prbBlankingObj | O-DU | | O-RAN.WG3.TS.E2SM- | E2 | - -| | | | | | | | -|--|-----------------------|--|--|--|---------------------------------|--| -| | of
blanked
PRBs | | | | CCC-R004 [50],
clause 9.3.46 | | -|--|-----------------------|--|--|--|---------------------------------|--| - -##### 4.6.8.4.1 Control over E2 - -1) **PA power optimization policy:** Based on the UE traffic, channel and location prediction and knowledge of the O-RU capability info, Near-RT RIC can provide to O-DU policies related PA power optimization such that O-DU can evaluates the conditions specified in the policies and configures the maximum output power of the O-RU via fronthaul M-plane or C-plane interface. To achieve this, the number of scheduled PRBs may be restricted by the O-DU, allowing the O-RU to adapt Power Amplifier (PA) accordingly, see [35], clause 20.6.1. - -Either RIC POLICY or RIC CONTROL can be used. - -##### 4.6.8.4.2 UE context information from E2 nodes - -See clause 4.6.1.4.2. - -##### 4.6.8.4.3 Measurements from E2 nodes - -See clause 4.6.1.4.3. - -##### 4.6.8.4.4 E2 node configuration - -PA power optimization (maximum output power control) related capabilities from the O-RU, see [35], clause 20.6, along with information about the mapping from cells to sector carriers and to O-RU are retrieved from O-DU in order to generate applicable and optimized energy saving related policies and controls. - -## 4.7 Interference detection and optimization - -This use case provides the motivation, description, and requirements for the Near-RT RIC and E2 interface to support interference detection and optimization, whose end-to-end requirements are specified in [49]. - -3GPP LTE and 5G networks are deployed based on the design objective of having a frequency reuse factor of one for the whole network (i.e., all cells in a network use the same frequency) due to limited radio resources. As a result, there is a need to leverage interference management techniques to mitigate inter-cell interference to improve QoS for users, especially at the cell edge. How to detect and then optimize interference is of great importance for cellular wireless networks. - -3GPP specifies multiple categories of interference management techniques to support interference optimization. The first category is based on the principle of inter-cell interference coordination. It has three sub-categories: Inter-Cell Interference Coordination (ICIC), enhanced ICIC (eICIC), and further enhanced ICIC (feICIC) where ICIC works in the frequency domain, eICIC in the time domain and feICIC in the UE domain. - -For ICIC, if the two-dimensional (in frequency and time) RBs for data channels to be scheduled in a cell can be shared and coordinated with other neighboring cells, interference of UEs near the cell edge can be mitigated. ICIC can leverage the following mechanisms. - -- **Restricting scheduling RBs:** The RBs used by a group of users in one geographical area (e.g., in the cell edge) for a cell is not scheduled by the neighboring cells. It is to avoid simultaneous transmission in the cell edge from neighboring cells. -- **Adjustment of the power level on physical channels.** - -ICIC can be implemented in a static or dynamic way. Static ICIC is achieved when the network operator manually manages cell configurations which become overly complex in practical deployments and are typically slow to adapt to changes in the network. Dynamic ICIC is required for fast adaptation of the interference scenarios, and exchange of signaling messages over X2/Xn - -interfaces among neighboring cells to convey scheduling decisions are needed to support interference optimization [12][19]. The ICIC concept was the origin of PRB blanking. - -For UL, the High Interference Indicator (HII) and Overload Indicator (OI) are available [12]. The HII informs the neighboring cells of the RBs to be scheduled for UEs as a proactive mechanism. With this information, the neighboring cells can avoid scheduling the same RBs for the UEs near the interfering cell. The OI informs the neighboring cells of the interference levels received on various two-dimensional resources (low, medium and high) as a reactive mechanism. With this information, the neighboring cells can a) reduce transmit power level, b) not schedule those RBs for UEs near the cell edge or c) not schedule those RBs at all. - -For DL, the Relative Narrowband Transmit Power (RNTP) informs the neighboring cells of the transmit power level per RB, including the RNTP threshold and RNTP bitmap of all RBs [12]. In the RNTP bitmap each bit indicates if the transmit power of an RB would exceed the RNTP threshold. With this information, the power allocation for UEs near the cell edge can be dynamically adjusted in a coordinated way. - -A cell can request load measurements from neighboring cells via Resource Status Reporting where the load measurements include DL and UL PRB usages [19]. - -For eICIC, cells exchange coordinated messages with its neighbors to allow the scheduler to create Almost Blank Subframes (ABS) in the time domain to mitigate interference at the UEs. The ABS contains no data traffic, but common Reference Signals (RSs) are still transmitted. Muted subframes should be avoided in subframes that transmit critical information Critical control channels (including System Information Block [SIB] 1 and paging), and broadcast (Master Information Block [MIB]) information are required in these subframes to avoid radio link failure for legacy UEs. - -For feICIC (also called the terminal-based interference management technique), interference cancellation is implemented at the UE for the critical control physical channels or signals that eICIC cannot handle (e.g., synchronization signals, reference signals, broadcast channel, etc.). - -The second category of interference management is based on carrier aggregation. In carrier aggregation, multiple carriers are aggregated at a cell. There are three types of carrier aggregation. - -- Contiguous aggregation of component carriers in a single band -- Non-contiguous aggregation of component carriers in a single band -- Non-contiguous aggregation of component carriers over multiple bands - -The original goal of carrier aggregation was to improve the data rate (i.e., throughput) for a UE since a UE can utilize multiple frequency carriers to communicate with a cell where the multiple frequency carriers can be from the same spectrum band or different spectrum bands. However, carrier aggregation can also be used as an interference optimization mechanism to improve spectral energy dispersal. - -The third category is based on Coordinated Multipoint (CoMP), which works in the spatial domain. CoMP is for multiple cells to coordinate with each other to jointly transmit and receive information to a single UE. CoMP performs coordinated scheduling and beam forming on a UE to improve performance in an interference environment (by minimizing interference). CoMP is similar to the soft handover concept in Code Division Multiple Access (CDMA). - -To trigger interference optimization, interference detection (including detecting the interference energy, classifying the interference source types, identifying the interference levels, and locating the interference source in terms of a geographical location) is required. In addition to LTE and 5G interference, other non-3GPP types of interference experienced in a 5G network, including internal and external RF interference, also need to be detected and optimized. - -Thanks to the open interface, the virtualization and intelligent functionalities provided by the O-RAN architecture, multi-cell-based collaborative real-time interference detection and optimization schemes can be realized. The operation and performance evaluation for interference detection and optimization in real-time should be conducted based on interference-related data focusing on a specific UE, UE group, RAN slice, PRBs or mMIMO beams, which is the primary target of improvement. The Near-RT RIC ensures optimal radio resource allocation for a UE, UE group, RAN slice, PRBs, and mMIMO beams through the E2 interface to improve the efficiency of radio resource utilization and interference optimization. - -### 4.7.1 Background and goal of the use case - -More background information for interference detection can be found in [49][i.6]. - -Interference detection includes the following steps: - -- Detection of interference energy -- Classification of interference source type -- Identification of the interference level -- Locating an interference source - -The data generated from E2 nodes to support interference detection can be based on the following: - -- per cell (e.g., UL/DL loading per cell, UL interference per cell, UL interference per PRB per cell) -- per sector -- per beam (e.g., UL interference per PRB per antenna branch per cell) -- per direction (e.g., data is from the direction of multiple beams) -- per UE or per group of UEs -- per range (e.g., data is from those UEs within a certain range of a cell) -- per pattern (e.g., uplink RSSIs pattern or uplink PRB interference pattern) - -where data per cell, per sector, per UE or per group of UEs have been supported in the O-RAN WG3 E2SM-KPM [36]. - -The xApps process the data from E2 nodes to support the interference detection objective. Specific data required include: - -1) Network level measurements, including - -a) UE level information: e.g., Channel State Information (CSI) reports including CQI (per UE or per UE slice), Precoding Matrix Indicator (PMI) with beam indicator, layer indication, rank indication as well as SINR, MCS, UL/DL RSRP, SS-RSRP (for serving cell and neighboring cells), SS-SINR, throughput, DU/UL PRB usage, mMIMO beams, Buffer Status Report (BSR), Power Headroom Report (PHR), location, velocity and timing advance. Note that to monitor CSI measurements for supporting channel measurement, channel estimation and interference measurement, E2 control or policy need to allocate cell resources and provide cells information transmission strategy for the serving cell and its intra-frequency neighboring cells for CSI-related RSs including Non-Zero Power (NZP) CSI-RS and CSI Interference Measurement (CSI-IM) containing zero power resource elements [49]. - -b) Cell level information: e.g., DL/UL PRB usage, throughput, uplink interference including UL interference per cell, UL interference per PRB in a cell, and UL interference per PRB of an antenna branch per cell as specified in WG3 UCR use case 6. Note that to support UL interference per PRB in a cell, E2 control or policy needs to send information for the UL PRBs to be monitored. - -2) Received power measurements (i.e., Received Signal Strength Indicators [RSSIs]) from O-RU directly or indirectly via O-DU as specified in [39], clause 21. - -After the xApps achieve the interference detection objective, the xApps determine a combination of the interference optimization mechanisms to achieve the interference optimization objective in real-time. The following is a list of interference optimization mechanisms that manage resources in time, frequency, space and power domains to achieve the objective of interference optimization. - -- Traditional cellular RF design techniques: antenna down-tilt and antenna azimuth orientation -- Traditional cellular RF design technique: transmit power level adjustment at E2 node -- Power control -- PRB blanking - -- Carrier aggregation -- CoMP -- Beam control (including beam muting as beam forming such as beam nulling) - -For background information on the PRB blanking optimization, see clause 4.6.4 PRB blanking optimization. - -Carrier aggregation reduces interference by selecting the carriers with less interference to aggregate. - -CoMP reduces interference by selecting cells that experience less interference. - -Beam muting reduces interference in the spatial domain by muting one or more SSB beams and / or traffic beams in the MIMO Grid of Beams (GoB) mode. - -Beam forming reduces interference in the spatial domain by forming nulls to cancel interference in MIMO GoB and non-GoB modes. - -By analyzing the interference detection results, with the support of AI/ML, the Near-RT RIC sends control and / or policies regarding interference optimization mechanisms to an O-DU to influence the MAC scheduler behaviors for interference optimization in a network with multiple cells. The Near-RT RIC can achieve overall network performance improvements including interference optimization for both uplink and downlink with system-level optimization instead of local-level optimization by an O-DU alone. Furthermore, the AI/ML models' functionality in the Near-RT RIC can include prediction of future traffic, user mobility, resource usage, and QoS/QoE on a per UE basis as well as prediction of network performance and effectiveness of interference reduction for different interference optimization mechanisms. Based on the predicted results, interference optimization control and / or policy can be given by the Near-RT RIC to E2 nodes in a near-real-time manner. - -The interference optimization objective includes performance targets in QoS and interference reduction on a specific UE, UE group, RAN slice, PRBs or mMIMO beams such that the impact of interference on the QoS metric of a specific UE, UE group, RAN slice or cell can be reduced by a certain percentage. One example of the performance targets in QoS is the average DL throughput and UL throughput of the UEs near the cell edge to achieve. One example of performance targets in interference reduction is a 90% interference reduction target for a group of UEs in a cell which means that the average channel quality (e.g., CQI) for the specified group of UEs under interference can be improved by applying interference optimization mechanisms to a 90% level compared to those when there is no interference. - -### 4.7.2 Entities/resources involved in the use case - -- 1) Near-RT RIC: - - a) On-board and run interference detection and optimization xApps. - - b) Near-real-time monitoring of interference detection and optimization related measurements from E2 nodes through E2 interface. - - c) Send controls and / or policies to E2 nodes through E2 interface to achieve the objectives of interference detection and optimization. -- 2) E2 node: - - a) Support interference detection and optimization related measurements and reports through E2 interface. - - b) Support interference detection and optimization actions, configurations and / or policy enforcements from E2 interface. - -### 4.7.3 Solution - -The context of interference detection and optimization is captured in table 4.7.3-1. - -**Table 4.7.3-1: Interference detection and optimization** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Drive interference detection and optimization in accordance with information from the E2 nodes. | | -| Actors and Roles | - Near-RT RIC: Generates RIC CONTROL and / or POLICY. | | - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| | - E2 node: RIC CONTROL and POLICY execution and RIC REPORT creation. | | -| Assumptions | - All relevant functions and components are instantiated.
- E2 interface connectivity is established. | | -| Pre-conditions | - Network is operational with default configuration.
- All relevant subscriptions established on E2 interface. | | -| Begins when | Interference detection and optimization for performance targets, including QoS and interference reduction, is activated or an operator defined trigger is detected. | | -| Step 1 (M) | Near RT RIC generates or updates interference detection and optimization control or policy. | | -| Step 2, 3 (M) | Near-RT RIC sends interference detection control or policy including cell resources to allocate, cells information transmission strategy, and cell resources to be monitored to E2 nodes. | | -| Step 4 (M) | Near-RT RIC collects data from E2 nodes through E2 interface. | | -| Step 5 (M) | Near-RT RIC subscribes to UE context information and measurement metrics via E2 interface. | | -| Step 6 (M) | E2 nodes report the UE context information and E2 measurements via RIC REPORT or INDICATION. | | -| Step 7 (M) | Near-RT RIC evaluates the collected data from E2 nodes and finds potential performance targets improvements including QoS and interference reduction. | | -| Step 8, 9 (M) | Near-RT RIC sends interference optimization control or policy to E2 nodes. | | -| Step 10 (M) | Interference detection and optimization are deactivated, or an operator defined trigger is detected. | | -| Step 11 (M) | Delete all related RIC subscriptions. | | -| Ends when | Interference detection and optimization stops. | | -| Exceptions | None. | | -| Post Conditions | Interference detection and optimization over a period of time is achieved. | | -| Traceability | REQ-Near-RT-RIC-ES-FUN7, REQ-Near-RT-RIC-IDIO-FUN1
REQ-E2-QoS-FUN1, REQ-E2-QoS-FUN2, REQ-E2-QoS-FUN3, REQ-E2-QoS-FUN4, REQ-E2-QoS-FUN5, REQ-E2-QoS-FUN6, REQ-E2-QoS-FUN7, REQ-E2-QoS-FUN8, REQ-E2-ES-FUN8, REQ-E2-ES-FUN9, REQ-E2-IDIO-FUN1, REQ-E2-IDIO-FUN2, REQ-E2-IDIO-FUN3 | | - -``` - -@startuml -autonumber -skinparam ParticipantPadding 4 -skinparam BoxPadding 8 -skinparam defaultFontSize 12 - -Box "O-RAN" #lightpink - Participant near as "Near-RT RIC" - Participant ran as "E2 Node" -End box - -near -> near: Near RT RIC generates or updates interference detection and optimization control or policy -Alt Near-RT RIC uses CONTROL Service for interference detection -near -> ran : <> RIC CONTROL REQUEST (Interference detection CONTROL) -Else Near-RT RIC uses POLICY Service for interference detection -near -> ran : <> RIC SUBSCRIPTION REQUEST (Interference detection POLICY) -end -near <--> ran: <> RAN Data collection -near -> ran : <> RIC SUBSCRIPTION REQUEST (UE context & measurement metrics) -ran -> near: <> RIC REPORT or INDICATION (UE context & E2 measurement metrics) -near -> near: Evaluation, potential improvement to performance targets include QoS and interference reduction -Alt Near-RT RIC uses CONTROL Service for interference optimization -near -> ran : <> RIC CONTROL REQUEST (Interference optimization CONTROL) - -``` - -``` - -Else Near-RT RIC uses POLICY Service for interference optimization -near -> ran : <> RIC SUBSCRIPTION REQUEST (Interference optimization POLICY) -end -near -> near: Interference detection and optimization stopped -near-> ran: <> RIC SUBSCRIPTION DELETE -@enduml - -``` - -The flow diagram of the performance targets optimization by interference detection and optimization is given in figure 4.7.3-1. - -![Sequence diagram titled 'O-RAN' showing interactions between Near-RT RIC and E2 Node. The process involves generating policies, then entering an 'alt' block for interference detection (using CONTROL or POLICY services), followed by data collection and evaluation. Another 'alt' block for interference optimization follows, also using CONTROL or POLICY services. Finally, the process stops and a subscription delete is sent.](4b2dd266b605b2f31a8759f802637301_img.jpg) - -``` - -sequenceDiagram - participant Near-RT RIC - participant E2 Node - Note right of Near-RT RIC: 1 Near RT RIC generates or updates interference detection and optimization control or policy - alt Near-RT RIC uses CONTROL Service for interference detection - Note right of Near-RT RIC: 2 «E2» RIC CONTROL REQUEST (Interference detection CONTROL) - else Near-RT RIC uses POLICY Service for interference detection - Note right of Near-RT RIC: 3 «E2» RIC SUBSCRIPTION REQUEST (Interference detection POLICY) - end - Note right of E2 Node: 4 «E2» RAN Data collection - Note right of E2 Node: 5 «E2» RIC SUBSCRIPTION REQUEST (UE context & measurement metrics) - Note right of E2 Node: 6 «E2» RIC REPORT or INDICATION (UE context & E2 measurement metrics) - Note right of Near-RT RIC: 7 Evaluation, potential improvement to performance targets include QoS and interference reduction - alt Near-RT RIC uses CONTROL Service for interference optimization - Note right of Near-RT RIC: 8 «E2» RIC CONTROL REQUEST (Interference optimization CONTROL) - else Near-RT RIC uses POLICY Service for interference optimization - Note right of Near-RT RIC: 9 «E2» RIC SUBSCRIPTION REQUEST (Interference optimization POLICY) - end - Note right of Near-RT RIC: 10 Interference detection and optimization stopped - Note right of Near-RT RIC: 11 «E2» RIC SUBSCRIPTION DELETE - -``` - -Sequence diagram titled 'O-RAN' showing interactions between Near-RT RIC and E2 Node. The process involves generating policies, then entering an 'alt' block for interference detection (using CONTROL or POLICY services), followed by data collection and evaluation. Another 'alt' block for interference optimization follows, also using CONTROL or POLICY services. Finally, the process stops and a subscription delete is sent. - -Figure 4.7.3-1: Performance targets optimization by interference detection and optimization - -### 4.7.4 Required data - -This clause elaborates the Near-RT RIC and the E2 node capabilities necessary for implementation of the interference detection and optimization use case. The requirements are specified in clause 5. - -#### 4.7.4.1 Control over E2 - -- 1) **Radio resource allocation.** Near-RT RIC provides direct control for interference detection and optimization configurations to be applied at the E2 node. Configurations at the cell level include: - - Configurations for cells resources allocation, cells information transmission strategy, and cell resources to be monitored to enable collection of interference detection related measurements. - - Configurations of PRBs to be blanked in PRB blanking to support interference optimization (see clause 4.6.4 PRB blanking optimization). - -- Configurations of beam index (for both SSB beams and traffic beams) to be muted in beam muting to support interference optimization. -- Configurations of carriers to be aggregated in carrier aggregation to support interference optimization. -- Configurations of cells to be jointly used in CoMP to support interference optimization. - -Both RIC POLICY and RIC CONTROL can be used. - -2) **Interference detection and optimization policy.** Near-RT RIC provides policies to the E2 node including interference detection policies, interference optimization policies, and performance targets the interference optimization policies should achieve. The policies may include: - -- Preferred cells resources allocation, cells information transmission strategy, and cell resources to be monitored to enable collection to enable collection of interference detection related measurements. -- Interference reduction target. -- Cell-level and UE performance targets, e.g. throughput cap, throughput drop tolerance, latency target. -- Preferred number of active or blanked PRBs to support PRB blanking optimization as part of interference optimization. -- Preferred number of active or inactive carriers to support carrier aggregation optimization as part of interference optimization. -- Preferred number of active or inactive cells to support CoMP optimization as part of interference optimization. -- Preferred number of active or muted beams to support beam muting optimization as part of interference optimization. -- Preferred number of nulls to support beam forming optimization as part of interference optimization. - -Either RIC POLICY or RIC CONTROL can be used. - -#### 4.7.4.2 UE context information from E2 nodes - -The following items are examples of UE context information identified as required: - -- UE ID (as defined in [32]) -- Slice level: S-NSSAI -- DRB level: e.g., established DRB ID, mapping with QoS flows, etc. -- QoS related: 5QI -- UE capabilities: CA and DC capabilities -- UE-level RAN state information -- UE-level PM data - -#### 4.7.4.3 Measurements from E2 nodes - -The E2 measurements are necessary to support interference detection and optimization in the Near-RT RIC. For interference detection, the Near-RT RIC collects interference related measurements. The interference related measurements for assessing network interference conditions are evaluated against performance targets for the Near-RT RIC to produce interference optimization control and / or policy. - -The examples of measurements information identified as required are listed in table 4.7.4.3-1. - -**Table 4.7.4.3-1: Measurements from E2 nodes** - -| Measurement Type | Measurement Examples | -|----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Cell/SSB area related measurements |
  • - DL/UL Total PRB Usage, Distribution of DL/UL Total PRB Usage, DL/UL GBR PRB Usage, DL/UL non-GBR PRB Usage, RRC Connection Number, Available RRC Connection Capacity Value, Mean and Maximum Number of Active UEs per DRB in the DL/UL, DL/UL Scheduling PDCCH CCE Usage, DL/UL Composite Available Capacity, DL/UL Cell PDCP SDU Data Volume (including secondary RAT usage for EN-DC/MR-DC), Handover success ratio
  • - DL/UL SSB Area Total PRB Usage, DL/UL SSB Area GBR PRB Usage, DL/UL SSB Area non-GBR PRB Usage, SSB Area Capacity Value
  • - DL/UL PRB usage per QCI, DL/UL PRB usage per 5QI, DL/UL PRB usage per slice, Slice Available Capacity Value
  • - UL interference level per cell
  • - UL interference level per PRB per cell
  • - UL interference level per PRB per antenna branch per cell
  • - Wideband CQI distribution (as specified in 3GPP TS 28.552 [6], clause 5.1.1.11.1)
  • - SS-RSRP distribution per SSB for serving cell (as specified in 3GPP TS 28.552 [6], clause 5.1.1.22.1)
  • - SS-RSRP distribution per SSB for neighbor cell (as specified in 3GPP TS 28.552 [6], clause 5.1.1.22.1)

As specified in 3GPP TS 38.314 [16], 3GPP TS 38.463 [20], 3GPP TS 38.473 [21], 3GPP TS 38.423 [19]

| -| E2 node user plane measurements per-UE/UE group |
  • - Average DL/UL throughput
  • - DL/UL PRB usage
  • - DL/UL Scheduled IP throughput
  • - Buffer Status Information (e.g., UL BSR)

As specified in 3GPP TS 28.552 [6], 3GPP TS 38.314 [16], 3GPP TS 38.423 [19], 3GPP TS 38.473 [21], 3GPP TS 38.463 [20], 3GPP TS 38.321 [17]

| -| UE L1/L2/L3 measurements |
  • - CSI (including CQI) measurements
  • - SINR measurements
  • - MCS measurements
  • - RSRP, RSRQ, SS-RSRP, SS-SINR, SRS-RSRP, CSI-RSRP, CSI-SINR, CSI-RSRQ measurements
  • - Location and Velocity measurements
  • - Timing advance measurements

As specified in 3GPP TS 38.331 [18], 3GPP TS 28.552 [6], 3GPP TS 38.215 [27]

| -| Mobility and RA related KPIs/measurements of UE/UE group |

Mobility and RA related KPIs/measurements from the E2 nodes hosting the target NES cell(s) and/or the neighbour cell(s) to the target NES cell(s)

  • - Handover failure related, e.g., number of handover failures related to MRO
  • - RACH failure related, e.g., distribution of RACH access delay
  • - Radio link failure reports
  • - UE context release related, e.g., number of UE context release requests

As specified in 3GPP TS 38.331 [18], 3GPP 28.552 [6]

| - -#### 4.7.4.4 E2 node configuration - -Cell-level configuration parameters are needed at the Near-RT RIC to, for instance, configure UE measurements required for monitoring cell level performance to support interference detection and optimization. - -# 5 Requirements - -## 5.1 Functional requirements - -### 5.1.1 Near-RT RIC generic functional requirements - -The Near-RT RIC functional requirements are captured in table 5.1.1-1. - -**Table 5.1.1-1: Near-RT RIC functional requirements** - -| REQ | Description | Note | -|---------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| -| REQ-Near-RT-RIC-TS-FUN1 | Near-RT RIC shall be able to use traffic steering-related A1 policies to determine and execute appropriate E2 actions. | | -| REQ-Near-RT-RIC-TS-FUN2 | Near-RT RIC shall be able to use traffic steering-related A1 enrichment information, e.g., the radio finger print information, to determine and execute appropriate E2 actions. | | -| REQ-Near-RT-RIC-MM-FUN1 | Near-RT RIC shall support training of massive MIMO-related models in xApps. | | -| REQ-Near-RT-RIC-MM-FUN2 | Near-RT RIC shall support deployment of massive MIMO-related trained models in xApps . | | -| REQ-Near-RT-RIC-MM-FUN3 | Near-RT RIC shall be able to use massive MIMO-related A1 enrichment information, e.g., location and mobility information, to determine and execute appropriate E2 actions. | | -| REQ-Near-RT-RIC-MM-FUN4 | Near-RT RIC shall be able to collect the observation and measurement data pertaining to CSI-Feedback and traffic load information of UEs, which are subsequently processed, aggregated and reported over O1 interface to the SMO/Non-RT RIC framework. | | -| REQ-Near-RT-RIC-QOE-FUN1 | Near-RT RIC shall be able to generate QoE related RAN analytics information and expose it to RAI service consumer. | | -| REQ-Near-RT-RIC-ES-FUN1 | Near-RT RIC shall be able to use energy saving-related A1 policies and enrichment information, e.g., the radio finger print information, to determine and execute appropriate E2 actions. | | -| REQ-Near-RT-RIC-ES-FUN2 | Near-RT RIC shall be able to trigger necessary energy saving related actions based on the configuration from O1 interface. | | -| REQ-Near-RT-RIC-ES-FUN3 | Near-RT RIC shall be able to handle mobility of users to account for potential coverage loss directly or indirectly via guidance to the E2 node. | | -| REQ-Near-RT-RIC-ES-FUN4 | Near-RT RIC shall be able to handle radio access and mobility controls as described in clause 4.6.2.4.1 to create more ASM sleep opportunities on the targeted cells. | | -| REQ-Near-RT-RIC-ES-FUN5 | Near-RT RIC shall support handling radio access to restrict access of UEs for a specific cell. | | -| REQ-Near-RT-RIC-ES-FUN6 | Near-RT RIC shall support handling mobility control to reduce traffic load. | | -| REQ-Near-RT-RIC-ES-FUN7 | Near-RT RIC shall support PRB blanking optimization to optimize the performance in ES. | | -| REQ-Near-RT-RIC-ES-FUN8 | Near-RT RIC shall be able to handle radio access and mobility controls to steer Rel-18 or non-Rel-18 UEs into or out of cells with spatial and power domain adaptation applied for energy saving. | | -| REQ-Near-RT-RIC-ES-FUN9 | Near-RT RIC shall be able to handle radio access and mobility controls to steer Rel-18 or non-Rel-18 UEs into or out of SSB-less cells for energy saving. | | -| REQ-Near-RT-RIC-IDIO-FUN1 | Near-RT RIC shall support interference detection and optimization to optimize the network performance. | | - -### 5.1.2 E2 interface functional requirements - -The E2 interface functional requirements are captured in table 5.1.2-1. - -**Table 5.1.2-1: E2 interface functional requirements** - -| REQ | Description | Note | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| -| REQ-E2-TS-FUN1 |

E2 shall support retrieval over E2 (read or receive via REPORT) of the following:

  • - Cell level configuration parameters, such as PCI, neighbor relations and related offsets for measurement, cell reselection and handover, etc.

Supported REPORT triggers shall include:

  • - Modification of the configuration parameters
| | -| REQ-E2-TS-FUN2 |

E2 shall support the configuration (including range and granularity) and retrieval of cell/SSB area or slice related measurements in the nomenclature as specified in 3GPP TS 28.552 [6], 3GPP TS 32.425 [7], 3GPP TS 36.314 [9], 3GPP TS 36.423 [12], 3GPP TS 38.314 [16], 3GPP TS 38.423 [19], 3GPP TS 38.463 [20] and 3GPP TS 38.473 [21]. These include:

  • - DL/UL Total PRB Usage, Distribution of DL/UL Total PRB Usage, DL/UL GBR PRB Usage, DL/UL total available PRB, DL/UL non-GBR PRB Usage, RRC Connection Number, Available RRC Connection Capacity Value, Mean and Maximum Number of Active UEs in the DL/UL per DRB, DL/UL Scheduling PDCCH CCE Usage, DL/UL Composite Available Capacity, DL/UL Cell PDCP SDU Data Volume (including secondary RAT usage for EN-DC/MR-DC), Handover success ratio
  • - DL/UL SSB Area Total PRB Usage, DL/UL SSB Area GBR PRB Usage, DL/UL SSB Area non-GBR PRB Usage, SSB Area Capacity Value
  • - DL/UL PRB usage per QCI, DL/UL PRB usage per 5QI, DL/UL PRB usage per slice, Slice Available Capacity Value

See NOTE 1.

Supported REPORT triggers shall include:

  • - Availability of new information e.g., new load measurement generated
  • - Threshold crossing
| | -| REQ-E2-TS-FUN3 |

E2 shall support the configuration and retrieval of E2-node user plane measurements per-UE / UE group, in the nomenclature as specified in 3GPP TS 28.552 [6], 3GPP TS 32.425 [7], 3GPP TS 36.314 [9], 3GPP TS 36.321 [10], 3GPP TS 38.314 [16], 3GPP TS 38.321 [17], 3GPP TS 38.423 [19], 3GPP TS 38.463 [20] and 3GPP TS 38.473 [21], e.g.:

  • - Average DL/UL throughput
  • - DL/UL PRB usage
  • - Buffer Status Information (e.g., UL BSR)

Supported REPORT triggers shall include:

  • - Availability of new information e.g., new load measurement generated
  • - Threshold crossing
| | -| REQ-E2-TS-FUN4 |

E2 shall support the configuration and retrieval of UE L1/L2/L3 measurements reported by individual UE, e.g.:

  • - RSRP and RSRQ measurements
  • - SINR measurements
  • - CQI/MCS measurements

Supported REPORT triggers shall include:

| | - -| REQ | Description | Note | -|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| -| |
  • - Availability of new information e.g., reception of RRC measurement reports.
| | -| REQ-E2-TS-FUN5 |

E2 shall support the control of EN-DC/MR-DC function in E2 nodes, including the configuration of the relevant parameters for EN-DC/MR-DC procedures, e.g.

  • - X2 SgNB addition
  • - X2 SgNB modification
  • - X2 SgNB release
  • - X2 SgNB change
  • - PSCell change
  • - Inter-master node handover

and UE level cell preference guidance for EN-DC/MR-DC, e.g.:

  • - Ordered list of target cells for SgNB addition and change.

INSERT/CONTROL and POLICY shall be supported in order to trigger the operation by a RAN event, as well as REPORT/CONTROL for Near-RT RIC to trigger the operation asynchronously where appropriate

| | -| REQ-E2-TS-FUN6 |

E2 shall support the control of handover function in E2 nodes, including the configuration of the relevant parameters for handover procedures, e.g.:

  • - Intra-frequency/inter-frequency/inter-RAT handover
  • - Intra/inter-eNB/gNB handover

and UE level cell preference guidance for handover, e.g.:

  • - Ordered list of target cells for handover

INSERT/CONTROL and POLICY shall be supported in order to trigger the operation by a RAN event, as well as REPORT/CONTROL for Near-RT RIC to trigger the operation asynchronously where appropriate

| | -| REQ-E2-TS-FUN7 |

E2 shall support the control of carrier aggregation function in E2 nodes, including the configuration of the relevant parameters for CA procedures (e.g., addition, modification and release of a component carrier) and UE level cell preference guidance for CA (e.g., ordered list of target cells for SCell addition/modification)

INSERT/CONTROL and POLICY shall be supported in order to trigger the operation by a RAN event, as well as REPORT/CONTROL for Near-RT RIC to trigger the operation asynchronously

| | -| REQ-E2-TS-FUN8 |

E2 shall support the control of idle mode mobility function in E2 nodes, including the configuration of the relevant parameters for idle mode procedures (e.g., intra-frequency/inter-frequency/inter-RAT cell reselection priority)

INSERT/CONTROL and POLICY shall be supported in order to trigger the operation by a RAN event, as well as REPORT/CONTROL for RIC to trigger the operation asynchronously

| | -| REQ-E2-TS-FUN9 |

E2 shall support the fetching of UE information including e.g.:

  • - UE ID as specified in [32]
  • - S-NSSAI
  • - QCI/5QI,
  • - UE capabilities (DC/CA)
  • - Active DRBs/QoS flows
| | -| REQ-E2-TS-FUN10 |

E2 shall support the configuration and retrieval of measurements related to UE location and velocity that are reported by an individual UE, e.g.:

  • - LocationInfo, CommonLocationInfo
| | - -| REQ | Description | Note | -|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------| -| | Supported REPORT triggers shall include:
- Availability of new information e.g., reception of RRC measurement reports. | | -| REQ-E2-QoS-FUN1 | E2 interface shall support retrieval of the UE context related information from E2 nodes:
  • • UE ID as specified in [32]
  • • Slicing info, such as S-NSSAI
  • • QoS info, such as E-RAB level QoS parameters (4G, NSA) or QoS flow level QoS parameters (NG-RAN)
  • • Radio bearers related info, such as established DRB ID, flow-to-DRB mapping
  • • RLC/MAC/PHY related info, such as LCID, scheduling related parameters
  • • UE capability info, such as CA (carrier aggregation) and DC (dual connectivity) capabilities
| Applicable RIC services:

REPORT | -| REQ-E2-QoS-FUN2 | E2 interface shall support retrieval of the following measurements info from E2 nodes:
  • • UE-level
    • - Radio channel info available at DU: CQI (as specified in 3GPP TS 28.552 [6])
    • - Radio channel info available at CU-CP for serving cell: RSRP, RSRQ, SINR (as specified in 3GPP TS 36.331 [11] and 3GPP TS 38.331 [18]), including from periodical and/or event triggered measurement report (A1-A6, B1-B2).
    • - Radio channel info available at CU-CP for neighboring cells: RSRP, RSRQ, SINR (as specified in 3GPP TS 36.331 [11] and 3GPP TS 38.331 [18]), including from periodical and/or event triggered measurement report (A1-A6, B1-B2).
    • - Layer-2: DL/UL UE PRB used for data traffic, Average DL UE throughput in gNB, Distribution of DL UE throughput in gNB, Percentage of unrestricted DL UE data volume in gNB, Packet Delay and RAN part packet delay components, Packet Delay, Data Volume (as specified in 3GPP TS 36.314 [9]), DL PDCP occupied buffer size, DL unused PDCP buffer size, Packet Loss Rate per DRB (as specified in 3GPP TS 38.314 [16]) and per logical channel
  • • Cell-level
    • - Layer-2: CQI, MCS Distribution in PDSCH, DL/UL Total PRB usage, Distribution of DL/UL Total PRB usage, DL/UL PRB used for data traffic, DL/UL Total available PRB, Total number of DL/UL TBs, Total error number of DL/UL TBs, Average DL UE throughput in gNB, Distribution of DL UE throughput in gNB, Percentage of unrestricted DL UE data volume in gNB, Packet Delay, Mean number of Active UEs in the DL/UL per cell, Max number of Active UEs in the DL/UL per cell (as specified so far in 3GPP TS 28.552 [6]), DL/UL PRB usage for traffic, DL/UL Total PRB usage, Distribution of DL/UL Total PRB usage, DL/UL PRB full utilization, Total number of DL/UL TBs, Total error number of DL/UL TBs, Average number of Active UEs (as specified so far in 3GPP TS 32.425 [7]), RAN part packet delay components (as specified in 3GPP TS 38.314 [16]), Packet Delay (as specified in 3GPP TS 36.314 [9]), DL/UL Cell PDCP SDU Data Volume, Packet Loss Rate, DL Packet Drop Rate (as specified in 3GPP TS 28.552 [6] and 3GPP TS 32.425 [7])
| Applicable RIC services:

REPORT | - -| REQ | Description | Note | -|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| -| REQ-E2-QoS-FUN3 |

E2 interface shall support the control of radio bearer related functions in E2 nodes, including configuration/modification of the following:

  • • DRB QoS (as specified in 3GPP TS 38.473 [21] and 3GPP TS 23.501 [3])
  • • QoS flow mapping (as specified in 3GPP TS 38.473 [21])
  • • Logical channel configuration (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11])
  • • Radio admission control (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11])
  • • Change of bearer termination point (MN or SN) and/or bearer types (MCG/SCG/split) (as specified in 3GPP TS 37.340 [13]); Control of split ratio for a split bearer; Control of packet duplication and number of legs (as specified in 3GPP TS 36.300 [8] and 3GPP TS 38.300 [14])
|

Applicable RIC services:

CONTROL POLICY

| -| REQ-E2-QoS-FUN4 |

E2 interface shall support the control of resource allocation function in E2 nodes, including configuration/modification of the following:

  • • DRX parameters (as specified in 3GPP TS 38.473 [21], 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]) such as long DRX cycle, short DRX cycle, short DRX timer.
  • • SR (scheduling request) periodicity (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]) such as sr-ProhibitTimer, sr-TransMax.
  • • SPS (semi-persistent scheduling) parameters (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]), such as SPS-Config (DL) and ConfiguredGrantConfig (UL)
  • • Slice level PRB quota (as specified in 3GPP TS 28.541 [4])
  • • CQI table (as specified in 3GPP TS 38.214 [15]) with target block error rate
|

Applicable RIC services:

CONTROL POLICY

| -| REQ-E2-QoS-FUN5 |

E2 interface shall support the control of radio access related functions in E2 nodes, including configuration/modification of the following:

  • • Access control (cell-level, UE-level, slice-level), such as RACH backoff, RRC connection reject, RRC connection release, access barring, etc.
|

Applicable RIC services:

CONTROL POLICY

| -| REQ-E2-QoS-FUN6 |

E2 interface shall support the control of mobility management function in E2 nodes, including configuration/modification of the following:

  • • Handover
  • • Handover restriction list
  • • Carrier aggregation (as specified in 3GPP TS 38.473 [21], 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11])
  • • MR-DC, including (NG)EN-DC, NE-DC, NR-DC (as specified in 3GPP TS 38.473 [21], 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11])
|

Applicable RIC services:

CONTROL POLICY

| -| REQ-E2-QoS-FUN7 |

E2 interface shall support the control of uplink power control function in E2 nodes, including configuration/modification of the following:

  • • Target value of uplink received quality such as received SINR or received power at E2 node
|

Applicable RIC services:

CONTROL POLICY

| - -| REQ | Description | Note | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------| -| REQ-E2-QoS-FUN8 | E2 interface shall support retrieval of configuration of uplink transmit power from E2 node:
  • Cell specific transmit power (TS38.331 [19]), PUSCH-ConfigCommon.
  • UE specific transmit power (TS 38.331 [19]), PUSCH-PowerControl.
Target value of uplink received quality such as received SINR or received power at E2 node | Applicable RIC services:

REPORT
QUERY | -| REQ-E2-SLA-FUN1 | E2 shall support retrieval over E2 (read or receive via REPORT) of the following:
  • Cell level and/or slice level configuration parameters
Supported REPORT triggers shall include:
  • Modification of cell level and/or slice configuration parameters
| | -| REQ-E2-SLA-FUN2 | E2 shall support the configuration (including range and granularity) and retrieval of cell or slice related measurements in the nomenclature as specified in 3GPP TS 28.552 [6], 3GPP TS 32.425 [7], 3GPP TS 36.314 [9], 3GPP TS 36.423 [12], 3GPP TS 38.314 [16], 3GPP TS 38.423 [19], 3GPP TS 38.463 [20] and 3GPP TS 38.473 [21]. These include:
  • DL/UL Total PRB Usage, Distribution of DL/UL Total PRB Usage, DL/UL total available PRB, RRC Connection Number, Available RRC Connection Capacity Value, Mean and Maximum Number of Active UEs in the DL/UL per DRB
  • DL/UL PRB usage per slice, Slice Available Capacity Value
Supported REPORT triggers shall include:
  • Availability of new information e.g., new load measurement generated
  • Threshold crossing
| Applicable RIC services:

REPORT | -| REQ-E2-SLA-FUN3 | E2 shall support the fetching of UE information including e.g.:
  • UE ID
  • PLMN, S-NSSAI(s)
  • DRB related information
| Applicable RIC services:

REPORT | -| REQ-E2-SLA-FUN4 | E2 interface shall support the configuration and retrieval of individual UE measurements, including the following:
  • RSRP, RSRQ
  • CQI
| Applicable RIC services:

REPORT | -| REQ-E2-SLA-FUN5 | E2 interface shall support the control of slice resource allocation in E2 nodes, including configuration/modification of the following:
  • Per-slice dedicated PRB allocation percentages for downlink and uplink
  • Per-slice maximum PRB allocation percentages for downlink and uplink
  • Per-UE-per-slice maximum PRB allocation percentages for downlink and uplink
  • Per-slice indication of resource sharing allowance to achieve utilization of unused slice resources by other network slices
  • Per-slice priority values to achieve scheduling prioritization among network slices with different priorities
| Applicable RIC services:

REPORT
CONTROL | -| REQ-E2-SLA-FUN6 | E2 interface shall support the slice-level control of radio resource management related functions in E2 nodes, including the following:
  • Slice based radio admission control
  • Slice based radio bearer control
| Applicable RIC services:

CONTROL
POLICY | -| REQ-E2-MM-FUN1 | E2 shall support retrieval over E2 of the following:
  • Beam level configuration parameters, such as beam pattern information (as specified in 3GPP TS 28.541 [5], clause 4.3.40)
  • O-RU antenna information (as specified in O-RAN.WG4.MP.0-R003-v15 [35], clause D.3.8)
| Applicable RIC services:

REPORT,
QUERY | - -| REQ | Description | Note | -|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------| -| |
  • - O-DU supported compression methods (as specified in O-RAN.WG4.CUS.0-R003-v15 [34], clause 7.7.1.2)
  • - Served cell information (as specified in 3GPP TS 38.473 [21], clause 9.3.1.10)
  • - MIB (as specified in 3GPP TS 38.331 [18], clause 6.2.2)
  • - SSB information of the serving cell (as specified in 3GPP TS 38.331 [18], clause 6.2.2)

Supported REPORT triggers shall include:
Modification of the configuration parameters

| | -| REQ-E2-MM-FUN2 |

E2 shall support retrieval from E2 node of DL L1 measurements reported by individual UE, e.g.:

  • - RSRP-SS measurements (as specified in 3GPP TS 38.133 [26] and 3GPP TS 38.215 [27])
  • - SINR-SS measurements (as specified in 3GPP TS 38.133 [26] and 3GPP TS 38.215 [27])
  • - PMI, RI, CQI (as specified in 3GPP TS 38.212 [43], clause 6.3)
  • - CSI-RSRP, CSI-RSQ, CSI-SINR (as specified in 3GPP TS 38.912 [46], clause 8.1.2.6.3, 3GPP TS 38.331 [18], clause 5.5.5.2, 3GPP TS 38.215 [27], clause 5.1, 3GPP TS 38.214 [15], clause 5.2.2)
  • - QCL type between SSB and CSI-RS (as specified in 3GPP TS 38.214 [15], clause 5.1.5)
  • - QCL type between CSI-RS and DMRS (as specified in 3GPP TS 38.214 [15], clause 5.1.5)

Supported REPORT triggers shall include:
Availability of new information

|

Applicable RIC services:

REPORT

| -| REQ-E2-MM-FUN3 |

E2 shall support retrieval from E2 node of UL L1 measurements reported for individual UE, e.g.:

  • - SRS RSRP measurements (as specified in 3GPP TS 38.133 [26] and 3GPP TS 38.215 [27])

Supported REPORT triggers shall include:
Availability of new information

|

Applicable RIC services:

REPORT

| -| REQ-E2-MM-FUN4 |

E2 shall support retrieval from E2 node of L3 mobility measurements reported per beam/beam group, e.g.:

  • - Number of too early HOs (as specified in 3GPP TS 28.552 [6])
  • - Number of too late HOs (as specified in 3GPP TS 28.552 [6])
  • - Number of HOs to wrong cell (as specified in 3GPP TS 28.552 [6])
  • - Number of requested legacy HO executions (HO attempts) (as specified in 3GPP TS 28.552 [6])
  • - Number of successful legacy HO executions (as specified in 3GPP TS 28.552 [6])
  • - Number of failed legacy HO executions (as specified in 3GPP TS 28.552 [6])
  • - Per UE event mobility failure indication with root cause (too early HO, too late HO, HO to wrong cell) and number of requested or number of successful HO executions at the time of failure

Supported REPORT triggers shall include

  • - For mobility KPIs, periodic reporting

For mobility failure indication, message event trigger

|

Applicable RIC services:

REPORT

| -| REQ-E2-MM-FUN5 |

E2 shall support retrieval of UE context information from E2 node for individual UE, e.g.:

  • - UE ID
  • - UE capabilities (as specified in 3GPP TS 38.331 [18], clause 6.2.2)
|

Applicable RIC services:

REPORT, QUERY

| - -| REQ | Description | Note | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------| -| |
  • - SRS Configuration (as specified in 3GPP TS 38.331 [18], clause 6.2.2)
  • - RRC State
  • - CSI Measurement configuration (as specified in 3GPP TS 38.331 [18], clause 6.3.2)
  • - Measurement Gap configuration (as specified in 3GPP TS 38.331 [18], clause 6.3.2)
  • - BWP DL/UL configurations (as specified in 3GPP TS 38.331 [18], clause 6.3.2)
  • - DRB related info, such as established DRB ID, flow-to-DRB mapping, RLC Mode, LCID (as specified in 3GPP TS 38.473 [21], clause 9.2.2.1)
  • - PDSCH of serving cell configuration (as specified in 3GPP TS 38.331 [18], clause 6.3.2)
  • - DRX Configuration (as specified in 3GPP TS 38.331 [18], clause 6.3.2)

Supported REPORT triggers shall include:
Configuration or reconfiguration of the UE context information

| | -| REQ-E2-MM-FUN6 |

E2 interface shall support the control of beamforming in E2 nodes, including the following:

  • - Configuration of non-Grid of beams beamforming mode, separately for single user- and multi-user MIMO, on a per-UE basis
| Applicable RIC services:

CONTROL POLICY | -| REQ-E2-MM-FUN7 |

E2 interface shall support the control of L3 mobility configuration in E2 nodes, including the following:

Cell Individual Offset (CIO), Time To Trigger (TTT), UE Timer 310 (T310) on a per beam/beam group, per UE/UE group basis (as specified in 3GPP TS 38.331 [18])

| Applicable RIC services:

POLICY | -| REQ-E2-MM-FUN8 |

E2 interface shall support the configuration of beam grouping information in E2 nodes, including the following:

List of beam group IDs with associated beam IDs

| Applicable RIC services:

POLICY | -| REQ-E2-MM-FUN9 |

E2 shall support request and reporting of the number of supported non-GoB BF modes in O-DU

| Applicable RIC services:

QUERY | -| REQ-E2-MM-FUN10 |

E2 shall support retrieval from E2 node of average DL/UL per-UE throughput in gNB with associated non-GoB BF mode and MIMO mode (SU/MU)

| Applicable RIC services:

REPORT | -| REQ-E2-MM-FUN11 |

E2 shall support retrieval from E2 node of DL L1 and L2 information reported for individual UE, e.g.:

  • - PDCP buffer status (as specified in 3GPP TS 38.323 [40], clause 5.6)
  • - RLC buffer status (as specified in 3GPP TS 25.321 [41], clause 8.2.2)
  • - HARQ ACK/NACK/DTX counts
  • - SRS samples
  • - HARQ-specific Transport Block Size volume (as specified in O-RAN WG3 E2SM-KPM [36], O-RAN WG3 E2SM-RC [37])

Supported REPORT triggers shall include:
Periodic with a configured period

| Applicable RIC services:

REPORT | -| REQ-E2-MM-FUN12 |

E2 interface shall support the configuration of individual UE operation, including the following:

  • - CSI resources (as specified in 3GPP TS 38.331 [18], clause 6.3.2)
  • - CSI reports (as specified in 3GPP TS 38.331 [18], clause 6.3.2)
| Applicable RIC services:

CONTROL | - -| REQ | Description | Note | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------| -| |
  • - SRS resources (as specified in 3GPP TS 38.331 [18], clause 6.3.2)
  • - PDSCH (as specified in 3GPP TS 38.331 [18], clause 6.3.2)
| | -| REQ-E2-MM-FUN13 | E2 shall support retrieval over E2 of the following:
  • - Timestamped slot numbers (as specified in 3GPP TS 38.473 [21], clause 9.3.1.171)
  • - Received time and processing time margin of the scheduling control message
Supported REPORT triggers shall include:
Periodic with a configured period | Applicable RIC services:

REPORT | -| REQ-E2-MM-FUN14 | E2 interface shall support the configuration of the active bearers for which the Near-RT RIC will be providing the scheduling parameters | Applicable RIC services:

CONTROL | -| REQ-E2-MM-FUN15 | E2 interface shall support the control of scheduling parameters that enable MU-MIMO transmissions and the relevant MIMO parameters, of latency tolerant traffic per slot per UE. | Applicable RIC services:

CONTROL | -| REQ-E2-MM-FUN16 | E2 interface shall support the control of parameter configurations per-cell basis and per-UE basis for a sequence of slots in E2 nodes, e.g.,
  • - Slot-specific DMRS configurations for a sequence of slots
  • - Per-UE slot-specific GoB-based beam configuration (i.e., P2 beamforming-weights/beam-index, PMI, RI, LI, etc.) for a sequence of slots
| Applicable RIC services:

POLICY | -| REQ-E2-QoE-FUN1 | E2 shall support UE context information including e.g.:
  • - UE ID
  • - List of S-NSSAI
List of QoS related ID, e.g., 5QI, QFI | | -| REQ-E2-QoE-FUN2 | E2 interface shall support retrieval of UE-level or cell-level measurement, including e.g.:
  • • Cell-level:
    • - Layer-2: MCS Distribution in PDSCH (as specified in 3GPP TS 28.552 [6], clause 5.1.1.12.1), DL/UL Total PRB usage (as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.1 and 5.1.1.2.2 and in 3GPP TS 32.425 [7], clauses 4.5.3 and 4.5.4), Distribution of DL/UL Total PRB usage (as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.3 and 5.1.1.2.4 and in 3GPP TS 32.425 [7], clauses 4.5.10 and 4.5.11), DL/UL PRB used for data traffic (as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.5 and 5.1.1.2.7), DL/UL PRB usage for traffic (as specified in 3GPP TS 32.425 [7], clauses 4.5.1 and 4.5.2), DL/UL Total available PRB (as specified in 3GPP TS 28.552 [6], clauses 5.1.1.2.6 and 5.1.1.2.8), DL/UL PRB full utilization (as specified in 3GPP TS 32.425 [7], clauses 4.5.9.1 and 4.5.9.2), Total number of DL/UL TBs (as specified in 3GPP TS 28.552 [6], clauses 5.1.1.7.3 and 5.1.1.7.8 and in 3GPP TS 32.425 [7], clauses 4.5.7.1 and 4.5.7.3), Total error number of DL/UL TBs (as specified in 3GPP TS 28.552 [6], clauses 5.1.1.7.4 and 5.1.1.7.9 and in 3GPP TS 32.425 [7], clauses 4.5.7.2 and 4.5.7.4), Average DL UE throughput in gNB (as specified in 3GPP TS 28.552 [6], clause 5.1.1.3.1), Distribution of DL UE throughput in gNB (as specified in 3GPP TS 28.552 [6], clause 5.1.1.3.2), Packet Delay (as specified in 3GPP TS 28.552 [6], clause 5.1.3.3), RAN part packet delay components (as specified in 3GPP TS 38.314 [16], clause 4.2.1.2), Packet Delay (as specified in 3GPP TS 36.314 [9], clause 4.1.4), DL/UL Cell PDCP SDU Data
| | - -| REQ | Description | Note | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| -| |

Volume (as specified in 3GPP TS 28.552 [6], clause 5.1.2.1 for non-split gNB, clause 5.1.3.6.2 for split gNB; per PLMN ID and per E-RAB QoS profile (QCI, ARP and GBR), as specified in 3GPP TS 32.425 [7], clause 4.4.7), Mean number of Active UEs in the DL/UL per cell (as specified in 3GPP TS 28.552 [6], clauses 5.1.1.23.1 and 5.1.1.23.3), Max number of Active UEs in the DL/UL per cell (as specified in 3GPP TS 28.552 [6], clauses 5.1.1.23.2 and 5.1.1.23.4), Average number of Active UEs (as specified in 3GPP TS 32.425 [7], clause 4.4.2), Packet Loss Rate (as specified in 3GPP TS 28.552 [6], clause 5.1.3.1), Packet Loss Rate (as specified in 3GPP TS 32.425 [7], clause 4.4.4), DL Packet Drop Rate (as specified in 3GPP TS 28.552 [6], clause 5.1.3.2), DL Packet Drop Rate (as specified in 3GPP TS 32.425 [7], clause 4.4.3.2)

  • • UE-level
    • - Radio channel info: SINR (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]), RSRP (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]), RSRQ (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11])
    • - Layer-2: CQI, MCS, DL/UL UE throughput, DL/UL UE PRB usage, RLC buffer size, RLC occupied buffer, RLC unused buffer, UL/DL MAC rate, Packet Delay, Data volume (per UE, as specified in 3GPP TS 36.314 [9], clause 4.1.8 and 3GPP TS 38.314 [16]), Packet Loss Rate per DRB (as specified in 3GPP TS 38.314 [16], clause 4.2.1.5) and per UE, DL Packet Drop Rate, Total number of RLC SDUs/PDUs
  • • Slice-level
    • - Layer-2: DL/UL UE PRB usage, RLC buffer size, RLC occupied buffer, RLC unused buffer, UL/DL MAC rate, Packet Delay, Data volume (per QCI/5QI, as specified in 3GPP TS 36.314 [9], clause 4.1.8 and 3GPP TS 38.314 [16]), Packet Loss Rate per DRB (as specified in 3GPP TS 38.314 [16], clause 4.2.1.5) and per UE, DL Packet Drop Rate (as specified in 3GPP TS 28.552 [6], clause 5.1.3.2), Total number of RLC SDUs/PDUs
| | -| REQ-E2-ES-FUN1 | E2 interface shall support forwarding the guidance of cell and carrier switching off/on from the Near-RT RIC to the E2 node. REPORT/CONTROL shall be supported for Near-RT RIC to trigger the operation asynchronously where appropriate | | -| REQ-E2-ES-FUN2 | E2 interface shall support the configuration and retrieval of energy saving related measurement and cell state information from the E2 Node. | | -| REQ-E2-ES-FUN3 | E2 interface shall support forwarding the guidance of sleep mode configurations as described in 4.6.2.4.1 from the Near-RT RIC to the E2 node. | | -| REQ-E2-ES-FUN4 | E2 interface shall support the control of NES related resource allocation function in E2 nodes including configuration/modification of the following:
  • • SR periodicity reconfiguration (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]): Both sr-ProhibitTimer and sr-TransMax can be treated.
  • • SPS configuration (as specified in 3GPP TS 38.331 [18] and 3GPP TS 36.331 [11]): Both SPS-Config (DL) and ConfiguredGrantConfig (UL) can be treated.
  • • CSI-RS periodicity configuration.
  • • Common channel periodicity configurations.
| | - -| REQ | Description | Note | -|--------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| -| REQ-E2-ES-FUN5 | E2 interface shall support the configuration of energy saving mode objectives from the Near-RT RIC to the E2 node as described in clause 4.6.2.4.1. | | -| REQ-E2-ES-FUN6 | E2 interface shall support configuration of RF channel reconfiguration related NES parameters from the Near-RT RIC to the E2 node which includes:
  • - Indication of the array elements to be switched off during sleep periods based on the TRX control capability information (see O-RAN.WG4.MP.0-R003-v17.01 [39], clause 20.3.1) reported by the E2 node (O-DU).
  • - Indication of the sleep mode (see O-RAN.WG4.MP.0-R003-v17.01 [39], clause 20.3.1, sleep-mode-type of trx-control-capability-info) to be applied during sleep periods.
  • - Indication of the sleep periods, e.g. slot numbers, symbol numbers and the conditions for triggering the sleep period.
| | -| REQ-E2-ES-FUN7 | E2 interface shall support the configuration of RF channel reconfiguration related performance objectives from the Near-RT RIC to the E2 node. The performance objectives can include:
  • - Energy saving target, e.g. targeted energy saving in percentage of current average energy consumption or energy saving levels defined by operator (e.g. maximum energy saving, medium energy saving, maximum performance etc.).
  • - UE or cell level performance targets e.g. throughput cap, throughput drop tolerance, latency target.
| | -| REQ-E2-ES-FUN8 | E2 interface shall support forwarding the guidance of PRB blanking optimization configurations or policies from the Near-RT RIC to the E2 node. | | -| REQ-E2-ES-FUN9 | E2 interface shall support the configuration of PRB blanking optimization related performance objectives from the Near-RT RIC to the E2 node. | | -| REQ-E2-ES-FUN10 | E2 interface shall support forwarding ES policy related to deep hibernate to the E2 node. | | -| REQ-E2-ES-FUN11 | E2 interface shall support forwarding the configurations of candidate sub-array patterns and PDSCH power offsets from the Near-RT RIC to the E2 node. | | -| REQ-E2-ES-FUN12 | E2 interface shall support forwarding the configurations of SSB-less SCell activation/deactivation from the Near-RT RIC to the E2 node. | | -| REQ-E2-ES-FUN13 | E2 interface shall support forwarding policy related to PA optimization to the O-DU. | | -| REQ-E2-IDIO-FUN1 | E2 interface shall support forwarding the guidance of interference detection and optimization control and / or policy from the Near-RT RIC to the E2 node. | | -| REQ-E2-IDIO-FUN2 | E2 interface shall support the configuration of interference detection and optimization objectives from the Near-RT RIC to the E2 node. | | -| REQ-E2-IDIO-FUN3 | E2 interface shall support the configuration and retrieval of interference detection and optimization related measurements and cell state information from the E2 node. | | -| NOTE 1: Time granularity of the measurements is not defined in the present document. | | | - -### 5.1.3 RAI exposure interface functional requirements - -The RAI exposure interface functional requirements are captured in table 5.1.3-1. - -**Table 5.1.3-1: RAI exposure interface functional requirements** - -| REQ | Description | Note | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| -| REQ-RAI-QoE-FUN1 | RAI exposure interface shall support request for QoE related analytics from RAI service consumers, with request scopes including:
  • - List of UE ID
| | -| REQ-RAI-QoE-FUN2 | RAI exposure interface shall support exposure to RAI service consumers the following QoE related information:

Predicted RAN performance
  • - Minimum/maximum/average throughput
  • - Minimum/maximum/average latency
  • - Average packet loss rate
  • - QoE prediction
Prediction related information
  • - Confidence
  • - Validity period
| | - -## 5.2 Non-functional requirements - -### 5.2.1 Near-RT RIC non-functional requirements - -Void - -### 5.2.2 E2 interface non-functional requirements - -Void - -# Annex A (informative): Example use cases - -## A.1 Example use cases for RAN slice SLA assurance - -### A.1.1 Downlink and uplink throughput per slice - -The *Downlink and Uplink Throughput Per Network Slice* are NG.116 attributes used in the definition and deployment of a network slice. They become *maxDlThptPerSlice* and *maxUlThptPerSlice* parameters in A1 polic(ies). The maximum downlink throughput per slice defines the aggregated data rate in the downlink for all UEs together in the network slice. This parameter is defined in GSMA GST NEST NG.116 Downlink throughput per network slice [22], clause 3.4.5. See also 3GPP TS 28.541 [5], clause 6.3.4 which defines the *SliceProfile* that captures some of the parameters from GSMA depending on the slice type. The parameter places an upper limit on the capacity of the slice so that the slice does not over-utilize available network resources and thereby provides a target to guide resource utilization. - -The following explanation describes the relevance to the Near-RT RIC. These attributes are sent by the Non-RT RIC to the Near-RT RIC(s) together with the scope identifier (S-NSSAI) and optional cell list or tracking area list. The Near-RT RICs split the A1 policy guidance from the Non-RT RIC. Thus, the subtending Near-RT RICs each provide guidance to the cells of their E2 nodes (O-DU, O-CU-UP, O-CU-CP) involved in the slice. - -For example, suppose there is an SLA parameter, *Downlink throughput per network slice*, with a value of 600,000 kilobits per second (kbps). The Non-RT RIC in this case has three subtending Near-RT RICs. Then, the Non-RT RIC might split the SLA parameter of 600,000 kbps into three A1 policies: *maxDlThptPerSlice* = 120,000 kbps for Near-RT RIC #1; *maxDlThptPerSlice* = 180,000 kbps for Near-RT RIC #2, and *maxDlThptPerSlice* = 300,000 kbps for Near-RT RIC #3 for the respective slice. This example use case is shown in figure A.1.1-1. - -![Diagram illustrating A1 policy decomposition. At the top, a Non-RT RIC (SMO) provides SLA parameters: Downlink throughput per network slice = 600,000 Kilobits/second. This is decomposed into three A1 Policies: A1 Policy maxDlThptPerSlice = 120,000 kbps for Near-RT RIC #1, A1 Policy maxDlThptPerSlice = 180,000 kbps for Near-RT RIC #2, and A1 Policy maxDlThptPerSlice = 300,000 kbps for Near-RT RIC #3. Each Near-RT RIC is connected to one or more E2 Nodes.](46c9f96273985599bf874713263feb52_img.jpg) - -The diagram shows the flow of A1 policy decomposition. At the top, a **Non-RT RIC (SMO)** icon is shown next to a box labeled **SLA parameters** containing the text **Downlink throughput per network slice = 600,000 Kilobits/second**. Three green arrows point down from this box to three separate **A1 Policy** icons. Each icon contains the text **maxDlThptPerSlice =** followed by a value: **120,000 kbps** for the first, **180,000 kbps** for the second, and **300,000 kbps** for the third. Below each A1 Policy icon is a **Near-RT RIC** icon (labeled #1, #2, and #3 respectively). Below each Near-RT RIC icon is a box labeled **E2 Nodes**. Near-RT RIC #1 is connected to one E2 Nodes box. Near-RT RIC #2 is connected to two E2 Nodes boxes. Near-RT RIC #3 is connected to three E2 Nodes boxes. - -Diagram illustrating A1 policy decomposition. At the top, a Non-RT RIC (SMO) provides SLA parameters: Downlink throughput per network slice = 600,000 Kilobits/second. This is decomposed into three A1 Policies: A1 Policy maxDlThptPerSlice = 120,000 kbps for Near-RT RIC #1, A1 Policy maxDlThptPerSlice = 180,000 kbps for Near-RT RIC #2, and A1 Policy maxDlThptPerSlice = 300,000 kbps for Near-RT RIC #3. Each Near-RT RIC is connected to one or more E2 Nodes. - -Figure A.1.1-1: A1 policy decomposition example - -The consumer of the *maxDlThptPerSlice* and *maxUlThptPerSlice* parameters is the Near-RT RIC via A1 policy. Slice SLA assurance-related xApp(s), within the Near-RT RIC, can apply or utilize this parameter to provide control of throughput - -within the E2 nodes. The xApp(s) can utilize E2 interface to adjust throughput-related RAN parameters, such as adjusting PRB allocation levels. The Near-RT RIC has influence over the operation of cells in a geographical area. The adjustment of the PRB allocation levels in MAC schedulers directly impact the throughput achieved by the slice. Therefore, this parameter at the RAN level influences the throughput. There might be other throughput-related parameters that could be employed, such as MCS, which is left for future study. - -3GPP Release 17 will introduce the concept of a Network Slice Admission Control Function (NSACF), see reference [(TR23.700-40 S2-1908583)] and reference [(TS23.501 v17.1.1 clause 5.15.11)]. The purpose of the NSACF is to enforce some of the slice SLA parameters from a 5G core perspective. The NSACF handles slice-specific user admission control into the network based on NG.116 criterion. However, the NSACF has no knowledge of RAN and RAN resources; thus, it cannot control RAN resources. Therefore, there is no interaction between NSACF and the handling of these parameters by the Near-RT RIC. Thus, the usage of the SLA-related parameters by the Near-RT RIC xApp(s) are in the scope of gNBs and will complement the 5GC SLA enforcement but from the perspective of the RAN. - -### A.1.2 Guaranteed downlink and uplink throughput per slice - -The *Guaranteed Downlink Throughput Quota* and *Guaranteed Uplink Throughput Quota* are attributes used in the definition and deployment of a network slice in NG.116. They are used in A1 policies as *guaDlThptPerSlice* and *guaUlThptPerSlice*. The guaranteed downlink/uplink throughput quota describes the guaranteed throughput or data rate supported by the network slice for the aggregate of all GBR QoS flows in downlink/uplink belonging to the set of all UEs using the network slice. This parameter is defined in GSMA GST NEST NG.116 Downlink/Uplink throughput per network slice [22], clause 3.4.5. See also 3GPP TS 28.541 [5], clause 6.3.4 which defines the *SliceProfile* which captures some of the parameters from GSMA depending on the slice type. The *Maximum UI/DI Throughput per Network Slice* parameters (clause 3.3.3.1.1) place an upper limit on the capacity of the slice while the *Guaranteed UI/DI Throughput Quota* parameters ensure a certain level of throughput. Thus, these two parameters complement each other: one giving a lower bound and the other giving an upper bound. For the upper bound (maximum UI/DI throughput per network slice) this ensures that the slice does not over-utilize available network resources while for the lower bound (guaranteed DI/UI throughput quota) meets a minimum throughput for the slice. - -These attributes are sent by the Non-RT RIC to the Near-RT RIC(s) together with the scope identifier (S-NSSAI) and optional cell list or tracking area list. The Near-RT RICs split the A1 policy guidance from the Non-RT RIC. Thus, the subtending Near-RT RICs each provide guidance to the cells of the E2 nodes (O-DU, O-CU-UP, O-CU-CP) involved in the slice. - -For example, suppose there is an SLA parameter, *Guaranteed Uplink Throughput Quota*, with a value of 1,000,000 kilobits per second (kbps). The Non-RT RIC in this case has three sub-tending Near-RT RICs. Then, the Non-RT RIC might split the SLA parameter of 1,000,000 kbps into three A1 policies: *guaUlThptPerSlice* = 170,000 kbps for Near-RT RIC #1; *guaUlThptPerSlice* = 230,000 kbps for Near-RT RIC #2, and *guaUlThptPerSlice* = 600,000 kbps for Near-RT RIC #3 for the respective slice. - -The consumer of the *guaUlThptPerSlice* and *guaDlThptPerSlice* parameters is the Near-RT RIC via A1 policy. Slice SLA assurance-related xApp(s), within the Near-RT RIC, can apply or utilize this parameter to provide control of and throughput within the E2 nodes (O-CU-UP, O-CU-CP, O-DU). The xApp(s) can utilize E2 interface to adjust throughput-related RAN parameters, such as adjusting PRB allocation levels. The Near-RT RIC has influence over the operation of cells in a geographical area. The adjustment of the PRB allocation levels in MAC schedulers directly impacts the throughput achieved by the slice. Therefore, this parameter at the RAN level influences the throughput. There might be other throughput-related parameters that could be employed, such as MCS, which is left for future study. - -# Annex (informative): Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2020.03.11 | 01.00.00 | Initial template | -| 2020.11.27 | 01.00.01 | First version of WG3 UCR spec, editorial updates for v01.00.01 | -| 2020.11.28 | 01.00.02 | Addition of CR:
- TIM.AO-2020.10.21-WG3-CR-TS-Use-Case-CR-0001-v05-rm (ATT, TIM, INTEL, CMCC, Radisys, CICT, Deutsche Telekom, Nokia), including:
- WG3#53: Agreement of "TIM.AO-2020.05.06-WG3-D-TS_UCR-TextProposal-sect_up_to_3.5.3.2_ATT.docx"
- WG3#55: Agreement of "TIM.AO-2020.05.20-WG3-D-TS_UCR-TextProposal-sect_3.5.3.3_OuterLoop_rev_after_email_disc_(ATT).doc"
- WG3#61: Agreement of "TIM.AO-2020.07.15-WG3-D-TS-Descr+UpdatedRequirements_text-proposal_ATT_CMCC_RSY.docx"; Inclusion of P1 and P3 of INT-2020.07.07-WG3-D-TextProposal-TS-UCR.doc
- WG3#68: Agreement of "TIM.AO-2020.09.23-WG3-D-TS_UCR_text_proposal_CRupdate_CICT+Nokia+DT+ATT+Radysis+Intel.docx"; editorial cleanup
- WG3#vF2F_2020-10: agreement of NOK.AO-2020.10.14-WG3-CR-TS-Use-Case-CR-0002-v02
Editorial updates (sections related to Traffic Steering use case)
Addition of references and definitions | -| 2020.12.07 | 01.00.03 | Addition of CR:
- CICT.AO-2020.10.21-WG3-CR-QoS&QoE-Use-Case-CR-0003-v09 (CICT, CMCC, INTEL)
Editorial updates (sections related to QoS use case)
Additional references | -| 2021.07.01 | 01.00.04 | Final Edits | -| 2021.08.10 | 01.00 | Final version 01.00 | -| 2022.02.04 | 01.00.05 | Initial version towards v02.00, spec number updated to v01.00.05 per new O-RAN spec numbering process (change is made on 2022.07.21)
Addition of CR:
- KDDI.AO-2021.07.26-WG3-CR-0000-Slice SLA Assurance use case-v03 | -| 2022.03.14 | 01.00.06 | Spec number is updated to v01.00.06 per new O-RAN spec numbering process (change is made on 2022.07.21)
Addition of CR:
- JNPR-2022.02.04-WG3-CR-0001-Slice SLA Assurance Additional Requirements-v02 | -| 2022.07.21 | 01.00.07 | Addition of CR:
- INT.AO-2022.04.26-WG3-CR-0018-UCR-mMIMO_runningCR_rev2 | -| 2022.07.21 | 01.00.08 | Update of the document to comply with the new O-RAN Technical Spec template | -| 2022.07.21 | 01.00.09 | All changes accepted, clean version for approval | -| 2022.08.02 | 02.00 | Final version 02.00 | -| 2022.11.08 | 02.00.01 | Initial version towards v03.00
Addition of CR:
- CMCC.AO-2022.06.21-WG3-CR-UCR-RAN Analytics Information Exposure related QoE Optimization Use Case-v4 | -| 2022.11.08 | 02.00.02 | Addition of CR:
- INT-2022.10.28-WG3-CR-0026-UCR-cor mMIMO_non-GoB | -| 2022.11.18 | 03.00 | Final version 03.00 | -| 2023.03.17 | 03.00.01 | Initial version towards v04.00
Addition of CR:
- NOK.AO-2022.01.19-WG3-CR-0001-UCR-RAN Slice SLA Assurance Use Case-v11 | -| 2023.05.03 | 03.00.02 | Addition of CR:
- FJT-2023.01.23-WG3-CR-0002-WG3UCR_Interference_Control-v02 | -| 2023.07.11 | 03.00.03 | Addition of CR: | - -| | | | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | - RMI.AO-2023.04.28-WG3-CR-0001-UCR-Energy saving Cell & Carrier Shutdown Use Case-v07 | -| 2023.07.26 | 03.00.04 | WG3 review comments are addressed, and approval is completed. All changes accepted, clean version. | -| 2023.07.26 | 04.00 | Final version 04.00 | -| 2023.09.20 | 04.00.01 | Initial version towards v05.00
Update of the spec to latest O-RAN TS template except for splitting the references to normative and informative. This split is planned to be made in this release of the document. | -| 2023.09.20 | 04.00.02 | Addition of CR:
- JNPR-2023.09.20-WG3-CR-0021-O-RAN-Use-Cases-Requirements-ODR-References-Section-v01 | -| 2023.09.21 | 04.00.03 | Addition of CR:
- JNPR-2023.09.21-WG3-CR-0022-O-RAN-Use-Cases-Requirements-ODR-References-Update-v01 | -| 2023.09.21 | 04.00.04 | Addition of CR:
- JNPR-2023.09.21-WG3-CR-0023-O-RAN-Use-Case-Requirements-ODR-References-Correction-v01 | -| 2023.11.03 | 04.00.05 | Addition of CR:
- RMI.AO-2023.08.30-WG3-CR-0002-UCR-Energy saving ASM Use Case-v09
Editorial Corrections | -| 2023.11.17 | 04.00.06 | WG3 review comments are addressed, and approval is completed. | -| 2023.11.17 | 04.00.07 | All changes accepted, clean version. | -| 2023.11.17 | 05.00 | Final version 05.00 | -| 2024.02.28 | 05.00.01 | Initial version towards v06.00
Addition of CRs:
- JNPR-2024.02.02-WG3-CR-0024-O-RAN-Use-Cases-Requirements-ODR-References-Wording-v01
- JNPR-2024.02.06-WG3-CR-0025-O-RAN-Use-Cases-Requirements-ODR-Figures-References-Wording-Capital_Letters-Corrections-v01
- JNPR-2024.02.08-WG3-CR-0026-O-RAN-Use-Cases-Requirements-ODR-Tables-References-Wording-Capital_Letters-Corrections-v01
- JNPR-2024.02.09-WG3-CR-0027-O-RAN-Use-Cases-Requirements-ODR-Notes-v01 | -| 2024.03.14 | 05.00.02 | Addition of CRs:
- DELL.AO-2023.08.31-WG3-CR-0003-UCR-Energy saving RF Reconfig Use Case v9
- COT.AO-2023.12.11-WG3-CR-0001-UCR-MU-MIMO-Optimization-v06 | -| 2024.03.30 | 05.00.03 | WG3 review comments are addressed, and approval is completed. | -| 2024.03.30 | 05.00.04 | All changes accepted, clean version. | -| 2024.03.30 | 06.00 | Final version 06.00 | -| 2024.05.16 | 06.00.01 | Initial version towards v07.00
Addition of CRs:
- JNPR-2024.04.20-WG3-CR-0028-O-RAN-Use-Cases-Requirements-ODR-FFS-Concepts-v02
- JNPR-2024.04.22-WG3-CR-0029-O-RAN-Use-Cases-Requirements-ODR-Modal-Verbs_Shall_Shall_not_Should_Should_not_Must_Must_not-v01
- JNPR-2024.04.25-WG3-CR-0030-O-RAN-Use-Cases-Requirements-ODR-Modal-Verbs_Can_Cannot_May_Need_not-v01
- JNPR-2024.04.25-WG3-CR-0031-O-RAN-Use-Cases-Requirements-ODR-Clauses-v01 | -| 2024.06.25 | 06.00.02 | Addition of CR:
- CMCC.AO-2024.05.08-WG3-CR-0004-UCR-Adding measurements in NES use case-v02 | -| 2024.07.11 | 06.00.03 | Addition of CRs:
- JNPR-2024.05.31-WG3-CR-0032-O-RAN-Use-Cases-Requirements-ODR-Capital_Letters-Editorial_Changes-Fixes-v01
- DCM-2024.03.06-WG3-CR-0001-UCR-Addition of Uplink Power Control for QoS-v07 | -| 2024.07.11 | 06.00.04 | Clean version for WG3 approval | - -| | | | -|------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2024.07.25 | 07.00 | Final version 07.00 | -| 2024.11.07 | 07.00.01 | Initial version towards v08.00
Addition of CRs:
- JNPR-2024.08.07-WG3-CR-0033-O-RAN-Use-Cases-Requirements-ODR-References-v01
- MAV-2023-07-31-WG3-UCR-002-mMIMO Feature CSI-RS DMRS Optimization-v06
- MTR.AO-2024.08.29-WG3-CR0001-UCR-Use Case 6-PRB Blanking-public release-v4 | -| 2024.11.14 | 07.00.02 | Updated copyright statement on the cover page and footer to 2025
Editorial changes to align to O-RAN TS template v02.01 | -| 2024.11.21 | 07.00.03 | Addition of CR:
- DTAG-2024.10.22-WG3-CR-0001-Use case numbering-v03
Added 3GPP Release 18 related text to Normative and Informative References clauses
Editorial updates | -| 2024.11.21 | 07.00.04 | Clean version for WG3 approval | -| 2024.12.04 | 07.00.05 | WG3 review comments are addressed, and approval is completed. | -| 2024.12.04 | 07.00.06 | All changes accepted, clean version. | -| 2024.12.04 | 08.00 | Final version 08.00 | -| 2025.06.05 | 08.00.01 | Initial version towards v09.00
Addition of CR:
- MTR.AO-2025.04.07-WG3-CR0004-UCR-Interference Detection and Optimization-v4 | -| 2025.07.08 | 08.00.02 | Editorial corrections
Editorial updates to align to O-RAN TS template v05 | -| 2025.07.08 | 08.00.03 | Clean version for WG3 approval | -| 2025.07.28 | 08.00.04 | WG3 review comments are addressed, and approval is completed. | -| 2025.07.28 | 08.00.05 | All changes accepted, clean version. | -| 2025.07.28 | 09.00 | Final version 09.00 | -| 2025.11.20 | 09.00.01 | Initial version towards v10.00
Addition of CRs:
- NEC.AO-2025.10.29-WG3-CR-0040-UCR-NES Deep-hibernate-v08
- RMI.AO-2025.02.10-WG3-CR-0001-UCR-NES spatial and power domain adaptation use case-v05
- RMI.AO-2025.02.10-WG3-CR-0002-UCR-NES SSB-less scell use case-v05
- RMI.AO-2025.10.07-WG3-CR-0003-UCR-NES PA power optimization-v04
- RMI.AO-2025.02.10-WG3-CR-0004-UCR-NES addition to section 4.6 top level description-v01
Editorial corrections | -| 2025.11.20 | 09.00.02 | Clean version for WG3 approval | -| 2025.12.08 | 10.00 | Final version 10.00 | \ No newline at end of file diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/04cfca33e3fc26513abe649d7474f733_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/04cfca33e3fc26513abe649d7474f733_img.jpg deleted file mode 100644 index 4e11d20e202c3b4465ef4b33c67cab660a28f427..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/04cfca33e3fc26513abe649d7474f733_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:56d7471d788ba6dc1a80e5c960089171c013a0bf3a9671b2584e822c0bd1b9d7 -size 90790 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/06e272c534fab6c7202d1355b043faf6_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/0827b9260fe5458dbe416ebfc78c469e_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 7660273fd6752b973145ab5665b854aa1131dde7..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:78d8bf66638de64ba661ec10f947a99453a76dbd6d4c840306534c902f5a0dad -size 4570 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/0a65720e640be13541e947c06c7a8c7f_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/110058f0fd9c7ca251db430f6df06b80_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/1142ba0197b158bb198186fe8baccc32_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/1142ba0197b158bb198186fe8baccc32_img.jpg deleted file mode 100644 index 600cc45938578c55ec0e583e3e31eab930f69d68..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/1142ba0197b158bb198186fe8baccc32_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ca7a0d4e336aace1061793eff14ea01117f0def963b76ccbdb50dbec38fa1eda -size 156778 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/13249a22bfff48bf6d20110d7228bfcd_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/14af8d47efd24c21fddf71b2415b6397_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/185df94f4a6a5245323255e844a30ec0_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/1baaba7a6e54e77197475726c871067d_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/1eadbbe42cfcac5c0023577110aec5e3_img.jpg deleted file mode 100644 index 7e1df833901911284fd90a0b8065a4571922c844..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/1eadbbe42cfcac5c0023577110aec5e3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2b770ab138063bfb50aee7cdcd09f6022591108039cbb4ab91f93c56c3f7eac1 -size 51064 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/226f5e462c99b71e08dc9abaa5ae260c_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 7660273fd6752b973145ab5665b854aa1131dde7..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:78d8bf66638de64ba661ec10f947a99453a76dbd6d4c840306534c902f5a0dad -size 4570 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/22f30783614672d201275c116a5d8516_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/253600420ae7bd7d0119563b895cbf8a_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/255efa1d461fc79b4ed367aaec11637f_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/255efa1d461fc79b4ed367aaec11637f_img.jpg deleted file mode 100644 index a298110b498b682942e3a31a55b7be0f27e39496..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/255efa1d461fc79b4ed367aaec11637f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d5d73d3d810ce9a9419407d234b5f7014d6c19c330f41011d96f1a5868afacac -size 169478 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index cb5581c7e7c243fb4012659e999432a972a104fa..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a55160079adf9e08a0f1a2bfdf755e7e1f5f91142ae66365b2fdc8f9803bf4b2 -size 4560 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/2c83b9d9c8c8076be3a1de47288c226d_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/3117e1f4e4767bab3f5c7cfaf4804652_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/318db222fae24a59c370fa6471d541b8_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/318db222fae24a59c370fa6471d541b8_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/318db222fae24a59c370fa6471d541b8_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg deleted file mode 100644 index b46c62cb0f6448f83aff5be77679af9bc5a9e4d9..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/331afcb1534110b4c4f6ddf553a0f7e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ce52868647d3604480379018aa231aff7420b4833c5129b2220786adda363ed7 -size 117517 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/35437f160e157760713aa85be471c3f3_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/35437f160e157760713aa85be471c3f3_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/35437f160e157760713aa85be471c3f3_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/38222c3ae003223a67635bfcc6950fbb_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/3a4f4369128594c5db0aa6b853c0666e_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg deleted file mode 100644 index 9e225dd93ca80740e9dde47b99e102d90f9c109e..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/3b11cc18f8ee769d0076c139dbf81ba3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:76f6718d4ebb734f2494c808705708fb0f220f61aac79881668cef6eb6da31c3 -size 96190 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/3d1817e8551f9c226a5f561108d3b3f9_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/3d1817e8551f9c226a5f561108d3b3f9_img.jpg deleted file mode 100644 index 97ce1b3402cd15bf09ac518eaa81e3c3120cf172..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/3d1817e8551f9c226a5f561108d3b3f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ceb7c0bde4a57da4ad27044cb67eebea0b13b6ecd2cda8edba16465b3a8eab3e -size 95446 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/3f727e6c0d6658bc53ea10905c4561dd_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/446c0bd806260f25430cadb01a6786c7_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/46c9f96273985599bf874713263feb52_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/46c9f96273985599bf874713263feb52_img.jpg deleted file mode 100644 index 49e612377601f08356862373a0d022f86d3cb2cf..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/46c9f96273985599bf874713263feb52_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fb6a7bd863794ca39368d82b6034196c49060313ca694b6dc1ca923007d399a9 -size 90127 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/474a819357587e34949a3e110ff19b30_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/474a819357587e34949a3e110ff19b30_img.jpg deleted file mode 100644 index e1afc3593de317f34074530b8d8ab368a6411ac2..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/474a819357587e34949a3e110ff19b30_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:81f34293c2b907bdfb7a02035360d04e210b6194262a8ec40e3f21320b2ce330 -size 95584 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/481b1f80fc31ebebb30d1f57d31e3af3_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/488b6387bc5fe15b9528eca7968a8733_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4a04896dfb569893fba50729314024f5_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4b2dd266b605b2f31a8759f802637301_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4b2dd266b605b2f31a8759f802637301_img.jpg deleted file mode 100644 index 6aa197248615472488dc16457fa581c9d0655847..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4b2dd266b605b2f31a8759f802637301_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9614fa599902bc4f2063cc6c128c44477a6419c8ed632048a8ed0f379617e435 -size 146992 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4b81ac66c571b3118659e4d9f47abb22_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg deleted file mode 100644 index 307e61360cbb67c600f5b5159ce2c5b8bbbee62a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d834ff1dc09f970965375e549c38767ddd4248acb9f5c9d8a372d7decd7c5b00 -size 95908 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/4db00373eb0bec04341ee887235bbfea_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/5009e30a55479d3941af523871208f9d_img.jpg deleted file mode 100644 index bef92370b92f7f62fcf03e62e04f4f2905eeb0df..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/5009e30a55479d3941af523871208f9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:29af4545675cb00eb2790504afe0c0bc329627f1c20c8d6156b2f4290d8d8d75 -size 4502 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/52a225f71b166b0c65c2f29f32a79f7f_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/5445597cceefaca1ac89e710fe339325_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/5445597cceefaca1ac89e710fe339325_img.jpg deleted file mode 100644 index 891f79ad8f1ff64a7d2d0fa20ae6993784d84f41..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/5445597cceefaca1ac89e710fe339325_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053bf6e5db73b9837ae04194e3923866fd5d469bb09afad6c2e6b2d07080e0 -size 105766 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/56ac11fb9683d7b846fb65c845d80f22_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/59368942873b0c35eef79a7a985025dc_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/59fcc0e3699f239444841881a2e75da0_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/5ae3023386ee15fae372871afce28865_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/60d6a326e6061d71ea69c9375ec96631_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/60e345365fd1e52e01c91e3fd3cc6515_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6588b1c7f14069d96744b473ad663248_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6a5342571eca4b46338fdfb3c42a8055_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6a9c5a85a12499d60c5a3a75c643b852_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6b0834ca8cdd18832ed461378d51dcb7_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6c8a96787f532bd1fa4719e738cf556f_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg deleted file mode 100644 index 8ddaf6adc8b455f7d3cc8be540360bcbe788965b..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6d8454e3fdef6561c6f64adf0092e9b9_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg deleted file mode 100644 index b7d2a48dc7c6951fc734dbc51b9c656c083e0f8d..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:79588a7c6038df5acfe7f4f5c666d96afccce314eb4151c24fe6079ba19fb97c -size 116859 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/7a3d4c97055e3021cefb0c5850050bff_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/7c66f12495a47e87f0a0314a0d3a2eff_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/7d08458fbe0bd5f306c00c16d68b25f2_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/81b34087cd6755a80f84a70cf28fba82_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 8ddaf6adc8b455f7d3cc8be540360bcbe788965b..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/83ee9f10bd3636e192d68decf7f04cec_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/854df8ad60507803253274673f9062cf_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8a781a0a8c956859f63a1ca7f2bb1644_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8a781a0a8c956859f63a1ca7f2bb1644_img.jpg deleted file mode 100644 index 07d6da03a7c3533396ba4d151c61b0d2a40b6e1c..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8a781a0a8c956859f63a1ca7f2bb1644_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7ff76ab89658b1dfb55885b1c209aca5e2fae3297d24bc3f0723ddc1061f07b7 -size 94552 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8b4befaffc5166da571069410e207aea_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8d129c93d18909f0643766f372e9ebf6_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8d138b6bf0be359dc7f079db4899bc41_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8dcca7651accff77ce832523fe2c7e64_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg deleted file mode 100644 index ace28fb126c9768573fbbdcb3d7ba08ef024f93f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8f7c0bf0c75a31fee6b0c7392ff57c39_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b34996c437cf326af5e508e054d320459949f72dccfe1f7ece4fee2b6cd3eddf -size 228602 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/8fbe9e67b51710384633b6407d60420d_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/909726977de6efd2d4df015198a2907b_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/909726977de6efd2d4df015198a2907b_img.jpg deleted file mode 100644 index 38f2abb74d62955f65cd088bea2b29d125015732..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/909726977de6efd2d4df015198a2907b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:169c665eabd02b296ffcfe4e38476af79acba6e11e7be4f179c1866415514a6b -size 87050 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/90ddb84c323b956e2d50a54d3f870566_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/90ddb84c323b956e2d50a54d3f870566_img.jpg deleted file mode 100644 index d85d8e7a2c8e89f7b475a8ba3aaaac0ba9e4bb64..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/90ddb84c323b956e2d50a54d3f870566_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:48b91be0be4dd971b5aa7f1bef910ba9f41f4d980cd719219b7c3b1ae4fb4073 -size 141259 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/9156549264d36ead617a1dec7987f970_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/9159d999b6514420a64eae80e52f1fd5_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/970a901d8e537da4b6ff719d8931912f_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/990afa9d07fb81cf8760867cb4247a79_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/9b59a11096b85b2bc74c6f653a354e28_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a28ab03366399b5e0a61445bc57e3724_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a76a30cf23764f0b907220e7c3c70ce1_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a7fcb275d0eed586509a47f4f86a9725_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/a9bb99d15f54792e1c9a14b1e465369a_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/aa05feb33e250a75136ea52816d3c19a_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/aef4390a4629604196222b9ed006a786_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/aef4390a4629604196222b9ed006a786_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/aef4390a4629604196222b9ed006a786_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg deleted file mode 100644 index f38143e5268c8293bd03f9ad34afb59b5c1366ed..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bb423ea3579a0ecc32858ebfde8c1ad47f8c13f1f82e41453fed51971784556d -size 96978 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg deleted file mode 100644 index bef92370b92f7f62fcf03e62e04f4f2905eeb0df..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:29af4545675cb00eb2790504afe0c0bc329627f1c20c8d6156b2f4290d8d8d75 -size 4502 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/be8d4d130f4e1f103926de61c4bfc23c_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/c389468860cd886ab9c732473e959f0f_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/c4315e81a5a818379fcf31519a9c2cbe_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/c521036a3eb59673388f5e034f4e6c9f_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/c5538ac451af9d74926b82278f11fb87_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/cb5f64aa26cee1c05257b7c6bbba7408_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/cb8f0521a69f168a06222045bea81a86_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg deleted file mode 100644 index 307e61360cbb67c600f5b5159ce2c5b8bbbee62a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/cf36ccd7ff79531e18e5b0ab1f0c46d4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d834ff1dc09f970965375e549c38767ddd4248acb9f5c9d8a372d7decd7c5b00 -size 95908 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d0516b99882398c64c90f71c12e808e2_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d1ec9820fe8d23d83e066389a9cd7338_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d2c29dfabebacb6f853683a6c3759320_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d90d939bcbf43d474efaeeaa335a635c_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index 8ddaf6adc8b455f7d3cc8be540360bcbe788965b..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d90f17b29a73eddf151f51effa8912e0_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d9cfc30025244dcd75766061f27ee09f_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d9cfc30025244dcd75766061f27ee09f_img.jpg deleted file mode 100644 index 014192d4b89076229692fb3fe8f6e8a2ee127bfb..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/d9cfc30025244dcd75766061f27ee09f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:725a7865022fd26f755621e1d78411efa0f2d8b3cda0664b069830379bb48518 -size 95418 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/da74b0e807fd62f32abdc3c05ffbabf4_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg deleted file mode 100644 index bef92370b92f7f62fcf03e62e04f4f2905eeb0df..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:29af4545675cb00eb2790504afe0c0bc329627f1c20c8d6156b2f4290d8d8d75 -size 4502 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/ddee3e67e0dfc22e25188fa635a19558_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/ddee3e67e0dfc22e25188fa635a19558_img.jpg deleted file mode 100644 index 2fec90bd388ffa6c2a865dfc713968822e1be9b7..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/ddee3e67e0dfc22e25188fa635a19558_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ecf527778c2c2e43e64c3a4986f7f3e3a3723b3b888430dcb33a7f4bca437cc6 -size 110038 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/dfafe39c233a62ec8ebd71e42992c14d_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/dfafe39c233a62ec8ebd71e42992c14d_img.jpg deleted file mode 100644 index 104982c2f8a6ce90c10f87dcf6b80b2b1d50ae50..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/dfafe39c233a62ec8ebd71e42992c14d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1f7a78319dcef8a239ac75c52641b3014f9da28de4f53e9c2b642e330cd03256 -size 87271 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e010d665d27407ff5e238d1c45c1c98f_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e06de71ced5f7c5e97414f01f39d550c_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e11e3fe4228e889a962514269f5a000b_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg deleted file mode 100644 index 6481fb228bcb10d3d2705c287869912b1c5cd3e8..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2eb295bd4205cce1e7bc31ee6ef1078ed189f26b4d37fba424faf7426565a1f3 -size 207519 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e345315706e3fe633bb6d593246c01bf_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e354b57563dae469c00b412b2abdf765_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e354b57563dae469c00b412b2abdf765_img.jpg deleted file mode 100644 index 67a2e5667341f834aead98fcc656833ff43fcde9..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e354b57563dae469c00b412b2abdf765_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:20df50b5483fac9533b42220e3a34b9e42e4919cac5d3c45f173f8f1d1969daa -size 153011 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e374c531ea6c45899ce8ec331e437bd1_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e3b551138548092502c92a99ebfdb7bc_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e511e373339b5f948f239b19e0c37dd4_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e6eb959227f4726d42277c0f920bedbc_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e87df69ebd4cd2dbbf6749079e6c057a_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/e882a6bdfd0e868314f3a26f536145a3_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/eb08b089f7e59a7e96a8b3c146668d6a_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f250ba4162fe40d8ddfd05b74fa48895_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f3d768b0299c4763bc703b606391c48b_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f5deee2f3301ee351c4008283ffafbb3_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f5deee2f3301ee351c4008283ffafbb3_img.jpg deleted file mode 100644 index a5e382671979a835cc0fb74ec64223677acef766..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f5deee2f3301ee351c4008283ffafbb3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3e231759c22086d74eba7b3c13e857783a261a0e3b0021d7d06e60fb003103 -size 96290 diff --git a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f74adaa1840504407cd4272995426f82_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f7dbd497160f02888f34fdf243648aa2_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg deleted file mode 100644 index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/f929e9fcf3f37d82af20f84f9c8b942a_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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index e8b9624631d343de15dc1c23522e08f9b2eb85d7..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.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/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.UCR-R005-v10.00/images/ff748955b94dcb8337283fbe12baa475_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/doc.md b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/doc.md deleted file mode 100644 index e2f01ea0522c57aa7ceb7c7fe874b3bc41dd2bd2..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/doc.md +++ /dev/null @@ -1,2132 +0,0 @@ - - -# --- **O-RAN Work Group 3 (Near-Real-time RAN Intelligent Controller and E2 Interface)** **Y1 interface: Application Protocol** - -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..... 5 -- Modal verbs terminology ..... 5 -- 1 Scope..... 6 -- 2 References ..... 6 - - 2.1 Normative references ..... 6 - - 2.2 Informative references ..... 6 -- 3 Definition of terms, symbols and abbreviations ..... 7 - - 3.1 Terms ..... 7 - - 3.2 Symbols..... 7 - - 3.3 Abbreviations..... 7 -- 4 General ..... 7 - - 4.1 Introduction..... 7 - - 4.2 Versioning of Y1 service APIs ..... 7 - - 4.2.1 General rules for API version..... 7 - - 4.2.2 Versioning for multiple solutions of a Y1 service API..... 7 - - 4.2.3 Versioning for certain data types ..... 7 -- 5 Usage of solutions ..... 8 - - 5.1 Introduction..... 8 - - 5.2 Usage of HTTP REST with JSON..... 8 - - 5.2.1 General ..... 8 - - 5.2.2 Content type ..... 8 - - 5.2.3 URI structure ..... 8 - - 5.2.3.1 Resource URI structure ..... 8 - - 5.2.4 HTTP headers..... 8 - - 5.2.4.1 General ..... 8 - - 5.2.5 Error handling ..... 9 - - 5.2.5.1 General ..... 9 -- 6 API Definitions for Solution 1 (HTTP REST with JSON)..... 9 - - 6.1 Introduction..... 9 - - 6.2 Y1\_RAI\_Subscription API ..... 9 - - 6.2.1 Introduction ..... 9 - - 6.2.2 Void..... 9 - - 6.2.3 Service operations ..... 9 - - 6.2.3.1 Introduction ..... 9 - - 6.2.3.2 RAI\_Subscribe service operation..... 9 - - 6.2.3.2.1 General ..... 9 - - 6.2.3.2.2 Subscribe to RAI notifications..... 10 - - 6.2.3.2.3 Update subscription for RAI notifications ..... 11 - - 6.2.3.3 RAI\_Unsubscribe service operation..... 12 - - 6.2.3.3.1 General ..... 12 - - 6.2.3.3.2 Unsubscribe from RAI notifications..... 12 - - 6.2.3.4 RAI\_Notify service operation ..... 12 - - 6.2.3.4.1 General ..... 12 - - 6.2.3.4.2 Notify subscribed RAI or termination of subscription ..... 12 - - 6.2.4 Resources ..... 13 - - 6.2.4.1 Resource URI structure ..... 13 - - 6.2.4.2 Resource: All Y1 RAI Subscriptions ..... 14 - - 6.2.4.2.1 Description..... 14 - - 6.2.4.2.2 Resource Definition ..... 14 - - 6.2.4.2.3 Resource Standard Methods ..... 14 - - 6.2.4.2.3.1 HTTP POST ..... 14 - - 6.2.4.2.4 Resource Custom Operations..... 15 - - 6.2.4.3 Resource: Individual Y1 RAI Subscription..... 15 - - 6.2.4.3.1 Description..... 15 - - 6.2.4.3.2 Resource definition ..... 15 - -- 6.2.4.3.3 Resource Standard Methods ..... 15 - - 6.2.4.3.3.1 HTTP DELETE..... 15 - - 6.2.4.3.3.2 HTTP PUT ..... 16 -- 6.2.4.3.4 Resource Custom Operations..... 16 -- 6.2.5 Custom operations without associated resources ..... 16 -- 6.2.6 Notifications ..... 16 - - 6.2.6.1 General ..... 16 - - 6.2.6.2 RAI Notification ..... 17 - - 6.2.6.2.1 Description ..... 17 - - 6.2.6.2.2 Operation Definition ..... 17 - - 6.2.7 Data model..... 17 - - 6.2.7.1 General ..... 17 - - 6.2.7.2 Structured data types ..... 18 - - 6.2.7.2.1 Introduction..... 18 - - 6.2.7.2.2 Type RaiSubscription..... 19 - - 6.2.7.2.3 Type NotificationCriteria ..... 19 - - 6.2.7.2.4 Type RaiNotification ..... 20 - - 6.2.7.2.5 Type RaiReport..... 20 - - 6.2.7.2.6 Type ValidityPeriodRelative..... 21 - - 6.2.7.2.7 Type ValidityPeriod ..... 21 - - 6.2.7.3 Simple data types and enumerations..... 21 - - 6.2.7.3.1 Introduction ..... 21 - - 6.2.7.3.2 Simple data types ..... 21 - - 6.2.7.3.3 Enumeration: NotificationMethod ..... 22 - - 6.2.7.3.4 Enumeration: TerminationCause ..... 22 - - 6.2.8 Error handling ..... 22 - - 6.2.8.1 General ..... 22 - - 6.2.8.2 Protocol Errors..... 22 - - 6.2.8.3 Application Errors ..... 22 -- 6.3 Y1\_RAI\_Query service API..... 22 - - 6.3.1 Introduction ..... 22 - - 6.3.2 Void..... 22 - - 6.3.3 Service operations ..... 22 - - 6.3.3.1 Introduction ..... 22 - - 6.3.3.2 RAI\_Query service operation..... 23 - - 6.3.3.2.1 General ..... 23 - - 6.3.3.2.2 Query RAI..... 23 - - 6.3.4 Resources ..... 24 - - 6.3.4.1 Resource URI structure ..... 24 - - 6.3.4.2 Resource: Y1\_RAI ..... 24 - - 6.3.4.2.1 Description..... 24 - - 6.3.4.2.2 Resource Definition ..... 24 - - 6.3.4.2.3 Resource Standard Methods ..... 25 - - 6.3.4.2.3.1 HTTP GET ..... 25 - - 6.3.5 Custom operations without associated resources ..... 25 - - 6.3.6 Notifications ..... 25 - - 6.3.7 Data model ..... 25 - - 6.3.7.1 General ..... 25 - - 6.3.7.2 Structured data types ..... 26 - - 6.3.7.2.1 Introduction..... 26 - - 6.3.7.2.2 Type RaiQueryResult..... 26 - - 6.3.7.3 Simple data types and enumerations ..... 26 - - 6.3.7.3.1 Introduction ..... 26 - - 6.3.7.3.2 Simple data types ..... 26 - - 6.3.8 Error handling ..... 27 - - 6.3.8.1 General ..... 27 - - 6.3.8.2 Protocol Errors..... 27 - - 6.3.8.3 Application Errors ..... 27 -- Annex A (normative): OpenAPI specification ..... 28** - - A.1 General..... 28 - - A.2 Y1\_RAI\_Subscription API ..... 28 - -A.3 Y1\_RAI\_Query API ..... 35 - -**Annex (informative): Change History ..... 40** - -# Foreword - -This Technical Specification (TS) has been produced by WG3 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 stage3 definition of the application protocols of the Y1 services. - -# 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.WG3.TS.Y1GAP, "Y1 interface: General Aspects and Principles". -- [2] O-RAN.WG3.TS.Y1TD, "Y1 interface: Type Definitions". -- [3] OpenAPI, "OpenAPI 3.1.0 Specification", . -- [4] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format". -- [5] IETF RFC 7807: "Problem Details for HTTP APIs". -- [6] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". -- [7] 3GPP TS 29.122: "T8 reference point for Northbound APIs". -- [8] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". -- [9] O-RAN.WG1.TS.OAD, "O-RAN Architecture Description". -- [10] 3GPP TS 29.501: "Principles and Guidelines for Services Definition". -- [11] Semantic Versioning Specification. Available at . - -## 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] Void - -# 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 [9] 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 [9] 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 [9] and the following apply: - -| | | -|------|--------------------------------------| -| AS | Application Server | -| RAI | RAN Analytics Information | -| SCEF | Service Capability Exposure Function | -| SCS | Services Capability Server | - -# 4 General - -## 4.1 Introduction - -The present document contains the stage-3 specifications for the services identified in Y1GAP [1]. Certain data types, including but not limited to RAI data types are defined in Y1TD [2]. - -One or more solutions in terms of network protocol and data interchange format may be defined for each Y1 service API. The use of a specific solution for a Y1 service API may be preconfigured or selected via negotiation mechanisms between the Near-RT RIC and the Y1 consumer. - -## 4.2 Versioning of Y1 service APIs - -### 4.2.1 General rules for API version - -Each Y1 service API is versioned independently. An API version shall consist of at least 3 fields, following a MAJOR.MINOR.PATCH pattern according to the Semantic Versioning Specification [11] unless specified otherwise. - -EXAMPLE: "1.0.0". - -The basic rules as reproduced from [11] shall apply for incrementing the versions: - -- MAJOR version is incremented if backward incompatible change is made. -- MINOR version is incremented if functional change is made in a backward compatible way. -- PATCH version is incremented if correction is made in a backward compatible way. - -### 4.2.2 Versioning for multiple solutions of a Y1 service API - -For a single Y1 service API, a single version should be kept across all the solutions defined for that API. That means the different solutions for a Y1 service API should evolve simultaneously. - -### 4.2.3 Versioning for certain data types - -The Y1 service APIs are designed in the approach that certain data types are decoupled from the APIs, and such data types may have versions independent from the API version. To that end, the full compatibility for a given solution of a single Y1 service API between Near-RT RIC and Y1 consumer is jointly governed by the API version and the relevant data type version(s). - -# 5 Usage of solutions - -## 5.1 Introduction - -The supported solution is listed in Table 5.1-1. - -**Table 5.1-1: Solutions for Y1 interface** - -| Solution | Clause | -|---------------------------------|--------| -| Solution 1: HTTP REST with JSON | 5.2 | - -## 5.2 Usage of HTTP REST with JSON - -### 5.2.1 General - -The solution of HTTP REST with JSON is introduced in clause 7.2 of Y1GAP [1]. - -The OpenAPI [3] specifications for each Y1 service API with this solution are documented in Annex A. - -### 5.2.2 Content type - -The bodies of HTTP request and successful HTTP responses shall be encoded in JSON format. The MIME media type that shall be used within the related Content-Type header field is "application/json", as defined in IETF RFC 8259 [4], unless specified otherwise. - -The "Problem Details" JSON object used to indicate additional details of the error in a HTTP response body shall be indicated by the content type "application/problem+json", as defined in IETF RFC 7807 [5]. - -### 5.2.3 URI structure - -#### 5.2.3.1 Resource URI structure - -The resource URIs of all Y1 service APIs, unless specified otherwise, shall be structured as: - -**{apiRoot}
//** - -with the following components: - -- The {apiRoot} indicates the scheme, the host name and optional port, and an optional implementation-specific sequence of path segments (starting with "/"). -- The indicates the API name of the service API in an abbreviated form. It is defined in the clause specifying the corresponding Y1 service API. -- The indicates the major version of the service API (see clause 4.2.1) and is defined in the clause specifying the corresponding Y1 service API. -- Each represents a specific resource of the service API. It is defined in the clause specifying the corresponding Y1 service API. - -All resource URIs of the service APIs shall comply with the URI syntax as defined in IETF RFC 3986 [6]. - -### 5.2.4 HTTP headers - -#### 5.2.4.1 General - -The HTTP headers used in [7] shall be supported by all Y1 service APIs with the solution "HTTP REST with JSON", unless specified otherwise. - -### 5.2.5 Error handling - -#### 5.2.5.1 General - -Unless specified otherwise, the HTTP error handling mechanism described in clause 5.2.6 of [7] shall be supported by all Y1 service APIs with the solution "HTTP REST with JSON", with the following replacements: - -- the SCEF is replaced by the Near-RT RIC; and -- the SCS/AS is replaced by the Y1 consumer. - -# 6 API Definitions for Solution 1 (HTTP REST with JSON) - -## 6.1 Introduction - -The Y1 service APIs defined in HTTP REST with JSON are listed in Table 6.1-1. - -**Table 6.1-1: List of Y1 Service APIs** - -| Y1 service API | Clause | API version | | -|---------------------|--------|-------------|--| -| Y1_RAI_Subscription | 6.2 | 1.0.0 | | -| Y1_RAI_Query | 6.3 | 1.0.0 | | - -The data models for the APIs are documented according to the conventions defined in clause 5.2.4 of 3GPP TS 29.501 [10]. - -## 6.2 Y1\_RAI\_Subscription API - -### 6.2.1 Introduction - -The Y1\_RAI\_Subscription API is used to access the Y1\_RAI\_Subscription service. - -The service operations and corresponding API definitions are organized in the following clauses for solution 1. - -### 6.2.2 Void - -### 6.2.3 Service operations - -#### 6.2.3.1 Introduction - -Table 6.2.3.1-1 lists the operations that shall be supported by the Y1\_RAI\_Subscription service for the solution "HTTP REST with JSON". - -**Table 6.2.3.1-1: Operations of the Y1\_RAI\_Subscription service** - -| Service operation name | Description | Initiated by | -|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------| -| RAI_Subscribe | This service operation is used by a Y1 consumer to subscribe or update subscription for RAI notifications.
Periodic or event-triggered notification can be subscribed. | Y1 consumer | -| RAI_Unsubscribe | This service operation is used by a Y1 consumer to unsubscribe from RAI notifications. | Y1 consumer | -| RAI_Notify | This service operation is used by a Near-RT RIC to notify Y1 consumers about subscribed RAI. | Near-RT RIC | - -#### 6.2.3.2 RAI\_Subscribe service operation - -##### 6.2.3.2.1 General - -The RAI\_Subscribe service operation is used by a Y1 consumer to create or update a subscription for RAI notifications from the Near-RT RIC. - -##### 6.2.3.2.2 Subscribe to RAI notifications - -Figure 6.2.3.2.2-1 shows a scenario where the Y1 consumer sends a request to the Near-RT RIC to create a subscription to RAI notifications. The operation is based on HTTP POST. - -``` -@startuml -participant "Y1 consumer" as cons -participant "Near-RT RIC" as prod -cons ->> prod: 1. POST ../subscriptions -prod ->> cons: 2. 201 Created -@enduml -``` - -![Sequence diagram showing the Y1 consumer sending a POST request to the Near-RT RIC for subscriptions, and the RIC responding with a 201 Created status.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) - -``` -sequenceDiagram - participant Y1 consumer - participant Near-RT RIC - Note left of Y1 consumer: Y1 consumer - Note right of Near-RT RIC: Near-RT RIC - Y1 consumer->>Near-RT RIC: 1. POST ../subscriptions - Near-RT RIC-->>Y1 consumer: 2. 201 Created - Note left of Y1 consumer: Y1 consumer - Note right of Near-RT RIC: Near-RT RIC -``` - -Sequence diagram showing the Y1 consumer sending a POST request to the Near-RT RIC for subscriptions, and the RIC responding with a 201 Created status. - -Figure 6.2.3.2.2-1: Y1 consumer subscribes to notifications - -The Y1 consumer shall send an HTTP POST request to the Near-RT RIC with the Resource URL "{apiRoot}/Y1\_RAI\_Subscription//subscriptions" representing the "All Y1 RAI Subscriptions" resource, to create an "Individual Y1 RAI Subscription" resource according to the information in the message. - -NOTE: The path segment "Y1\_RAI\_Subscription" does not follow the related naming convention specified in clause 5.2.4.1 of [7]. The path segment is however kept as currently defined in this specification for backward compatibility considerations. - -The "RaiSubscription" data structure provided in the request body shall include: - -- the type of RAI as the "raiType" attribute; - - the version of the RAI type as the "raiTypeVersion" attribute; - - the target entity/entities of the RAI in the "targetEntities" attribute; - - an URI where to receive the RAI notifications as the "notificationTargetAddress" attribute; - - the timing or the events when the RAI notifications are triggered in the "notificationCriteria" attribute, which shall include: - - the method used to trigger RAI notifications as the "notificationMethod" attribute; - - the time interval between periodic RAI notifications as the "notificationPeriod" attribute, if the "notificationMethod" attribute is set to "PERIODIC"; - - the trigger event that triggers RAI notifications in the "notificationTriggerEvent" attribute, if the "notificationMethod" attribute is set to "EVENT\_TRIGGERED"; -- and may include: -- the expected time of the first RAI notification as the "notificationStartTime" attribute, if the "notificationMethod" attribute is set to "PERIODIC". - -The "RaiSubscription" data structure provided in the request body may include: - -- the expected validity period(s) for the RAI in the "expectedValidityPeriodsRelative" attribute; an expected validity period before the occurrence of a RAI notification refers to statistics for a past time, and an expected validity period after the occurrence of a RAI notification refers to a prediction for a future time. -- the filter parameters to filter RAI contents in the RAI report as the "filterParameters" attribute; - -Upon the reception of the HTTP POST request, the Near-RT RIC shall create the subscription to generate corresponding RAI according to the request, assign a unique subscription ID as "subscriptionId", and store the record. - -If the Near-RT RIC successfully creates an "Individual Y1 RAI Subscription" resource, the Near-RT RIC shall respond with "201 Created" status code, with the message body containing a representation of the created subscription. The response shall include a "Location" HTTP header field which contains the URI of the created subscription, i.e., "{apiRoot}/Y1\_RAI\_Subscription//subscriptions/{subscriptionId}". - -If an error occurs when processing the HTTP POST request, the Near-RT RIC shall send an HTTP error response as specified in clause 6.2.8. In particular, - -- If the necessary data to perform the analysis are unavailable, the Near-RT RIC shall reject the request with a "500 Internal Server Error" status code and a "ProblemDetails" data structure including the "cause" attribute set to "DATA\_UNAVAILABLE". - -##### 6.2.3.2.3 Update subscription for RAI notifications - -Figure 6.2.3.2.3-1 shows a scenario where the Y1 consumer sends a request to the Near-RT RIC to update a subscription to RAI notifications. The operation is based on HTTP PUT. - -``` -@startuml -participant "Y1 consumer" as cons -participant "Near-RT RIC" as prod -cons ->> prod: 1. PUT ../subscriptions/{subscriptionId} -prod -->> cons: 2a. "200 OK" or 2b. "204 No Content" -@enduml -``` - -![Sequence diagram showing the interaction between Y1 consumer and Near-RT RIC for updating a subscription. The Y1 consumer sends a PUT request to the Near-RT RIC, and the Near-RT RIC responds with either a 200 OK or a 204 No Content status code.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) - -``` -sequenceDiagram - participant Y1 consumer - participant Near-RT RIC - Note left of Y1 consumer: Y1 consumer - Y1 consumer->>Near-RT RIC: 1. PUT ../subscriptions/{subscriptionId} - Note right of Near-RT RIC: Near-RT RIC - Near-RT RIC-->>Y1 consumer: 2a. "200 OK" or 2b. "204 No Content" - Note left of Y1 consumer: Y1 consumer - Note right of Near-RT RIC: Near-RT RIC -``` - -Sequence diagram showing the interaction between Y1 consumer and Near-RT RIC for updating a subscription. The Y1 consumer sends a PUT request to the Near-RT RIC, and the Near-RT RIC responds with either a 200 OK or a 204 No Content status code. - -Figure 6.2.3.2.3-1: Y1 consumer updates subscription to notifications - -The Y1 consumer shall send an HTTP PUT request to the Near-RT RIC with the Resource URL "{apiRoot}/Y1\_RAI\_Subscription//subscriptions/{subscriptionId}" representing the "Individual Y1 RAI Subscription" resource, to update that resource identified by the "subscriptionId" field. - -The "RaiSubscription" data structure provided in the request body shall include the same contents as described in clause 6.2.3.2.2. - -Upon the reception of the HTTP PUT request, the Near-RT RIC shall update the subscription according to the request, and store the record. - -If the Near-RT RIC successfully updates the "Individual Y1 RAI Subscription" resource, the Near-RT RIC shall respond with: - -- a "200 OK" status code with the message body containing a representation of the updated subscription; or, -- a "204 No Content" status code. - -If an error occurs when processing the HTTP PUT request, the Near-RT RIC shall send an HTTP error response as specified in clause 6.2.8. In particular, - -- If the necessary data to perform the analysis are unavailable, the Near-RT RIC shall reject the request with a "500 Internal Server Error" status code and a "ProblemDetails" data structure including the "cause" attribute set to "DATA\_UNAVAILABLE". - -#### 6.2.3.3 RAI\_Unsubscribe service operation - -##### 6.2.3.3.1 General - -The RAI\_Unsubscribe service operation is used by an Y1 consumer to delete a subscription for RAI notifications. - -##### 6.2.3.3.2 Unsubscribe from RAI notifications - -Figure 6.2.3.3.2-1 shows a scenario where the Y1 consumer sends a request to the Near-RT RIC to unsubscribe from RAI notifications. The operation is based on HTTP DELETE. - -``` -@startuml -participant "Y1 consumer" as cons -participant "Near-RT RIC" as prod -cons ->> prod: 1. DELETE ../subscriptions/{subscriptionId} -prod ->> cons: 2. 204 No Content -@enduml -``` - -![Sequence diagram showing the interaction between Y1 consumer and Near-RT RIC for unsubscribing. The Y1 consumer sends a DELETE request to the Near-RT RIC, and the Near-RT RIC responds with a 204 No Content status code.](78ffccd66df9bafd96e3e081110d09dd_img.jpg) - -``` -sequenceDiagram - participant Y1 consumer - participant Near-RT RIC - Note left of Y1 consumer: Y1 consumer - Y1 consumer->>Near-RT RIC: 1. DELETE ../subscriptions/{subscriptionId} - Note right of Near-RT RIC: Near-RT RIC - Near-RT RIC-->>Y1 consumer: 2. 204 No Content - Note left of Y1 consumer: Y1 consumer - Note right of Near-RT RIC: Near-RT RIC -``` - -Sequence diagram showing the interaction between Y1 consumer and Near-RT RIC for unsubscribing. The Y1 consumer sends a DELETE request to the Near-RT RIC, and the Near-RT RIC responds with a 204 No Content status code. - -Figure 6.2.3.3.2-1: Y1 consumer unsubscribes from notifications - -The Y1 consumer shall send an HTTP DELETE request to the Near-RT RIC with the resource URI "{apiRoot}/Y1\_RAI\_Subscription//subscriptions/{subscriptionId}" representing the "Individual Y1 RAI Subscription" resource, to delete that resource identified by the "subscriptionId" field. - -The message body shall be empty. - -Upon the reception of the HTTP DELETE request, the Near-RT RIC shall remove the "Individual Y1 RAI Subscription" resource according to the request. - -If the Near-RT RIC successfully removes the "Individual Y1 RAI Subscription" resource, the Near-RT RIC shall respond with "204 No Content" status code. - -If an error occurs when processing the HTTP DELETE request, the Near-RT RIC shall send an HTTP error response as specified in clause 6.2.8. - -#### 6.2.3.4 RAI\_Notify service operation - -##### 6.2.3.4.1 General - -The RAI\_Notify service operation is used by the Near-RT RIC to send RAI notifications to the Y1 consumer, or to terminate the subscription. - -##### 6.2.3.4.2 Notify subscribed RAI or termination of subscription - -Figure 6.2.3.4.2-1 shows a scenario where the Near-RT RIC sends a request to the Y1 Consumer to send RAI notifications or to terminate the subscription. The operation is based on HTTP POST. - -``` -@startuml -participant "Y1 consumer" as prod -participant "Near-RT RIC" as cons -cons ->> prod: 1. POST{notificationTargetAddress} -prod ->> cons: 2. "204 No Content" -@enduml -``` - -![Sequence diagram showing Near-RT RIC sending a POST request to Y1 consumer and receiving a 204 No Content response.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) - -``` - -sequenceDiagram - participant Y1_consumer as Y1 consumer - participant Near_RT_RIC as Near-RT RIC - Near_RT_RIC->>Y1_consumer: 1. POST{notificationTargetAddress} - Y1_consumer-->>Near_RT_RIC: 2. "204 No Content" - -``` - -Sequence diagram showing Near-RT RIC sending a POST request to Y1 consumer and receiving a 204 No Content response. - -**Figure 6.2.3.4.2-1: Y1 consumer notifies the subscribed event** - -The Near-RT RIC shall send an HTTP POST request to the Y1 consumer with "{notificationTargetAddress}" as the resource URL. - -The request shall be triggered according to the notification criteria as the "notificationCriteria" attribute in the subscription request, or when Near-RT RIC determines to terminate the subscription. - -When the request is triggered by the notification criteria, the "RaiNotification" data structure provided in the request body shall include: - -- the subscription ID as the "subscriptionId" attribute; -- the RAI reports in the "raiReports" attribute that, for each RAI report, the "RaiReport" data type shall include: - - the target entity of the RAI report as the "targetEntity" attribute; - - the validity period of the RAI report as the "validityPeriod" attribute; - - the actual RAI contents as the "raiContents" attribute; - and may include: - - the confidence of the RAI report, if the RAI report is a prediction; - - the timestamp when Near-RT RIC generates the RAI report as the "timeStampRaiGeneration" attribute. - -When the request is to terminate the subscription, the "RaiNotification" data structure provided in the request body shall include: - -- the subscription ID as the "subscriptionId" attribute; -- the termination indication as the "raiSubscriptionTerminationIndication" which is set to "TRUE"; - -and may include: - -- the reason for which Near-RT RIC terminates the subscription. - -Upon the reception of the HTTP POST request, the Y1 consumer shall process the information in the message. - -If the Y1 consumer successfully processes the request, the Y1 consumer shall respond with "204 No Content" status code. - -If errors occur when processing the HTTP DELETE request, the Y1 consumer shall send an HTTP error response as specified in clause 6.2.8. - -### 6.2.4 Resources - -#### 6.2.4.1 Resource URI structure - -The resource URI shall have the structure as defined in clause 5.2.3.1 with the following clarifications: - -- The shall be "Y1\_RAI\_Subscription". -- The shall be "v1". -- The shall be set as illustrated in figure 6.2.4.1-1. - -![Resource URI structure diagram showing {apiRoot}/Y1_RAI_Subscription/v1 branching into /subscriptions and then into /{subscriptionId}.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) - -``` - - graph TD - Root["{apiRoot}/Y1_RAI_Subscription/v1"] --> Subscriptions["/subscriptions"] - Subscriptions --> SubscriptionId["/{subscriptionId}"] - -``` - -Resource URI structure diagram showing {apiRoot}/Y1\_RAI\_Subscription/v1 branching into /subscriptions and then into /{subscriptionId}. - -**Figure 6.2.4.1-1: Resource URI structure of the Y1\_RAI\_Subscription API** - -Table 6.2.4.1-1 provides an overview of the resources and applicable HTTP methods for the Y1\_RAI\_Subscription API. - -**Table 6.2.4.1-1: Resources and methods overview** - -| Resource name | API specific resource URI part | HTTP method or custom operation | Description | -|--------------------------------|---------------------------------|---------------------------------|------------------------------------------------------------------------------------| -| All Y1 RAI Subscriptions | /subscriptions | POST | Creates a new Individual Y1 RAI Subscription resource. | -| Individual Y1 RAI Subscription | /subscriptions/{subscriptionId} | DELETE | Deletes an Individual Y1 RAI Subscription resource identified by {subscriptionId}. | -| | | PUT | Updates an existing Individual Y1 RAI Subscription resource. | - -#### 6.2.4.2 Resource: All Y1 RAI Subscriptions - -##### 6.2.4.2.1 Description - -The All Y1 RAI Subscriptions resource represents all subscriptions to the Y1\_RAI\_Subscription service at a given Near-RT RIC. The resource allows a Y1 consumer to create a new Individual Y1 RAI Subscription resource. - -##### 6.2.4.2.2 Resource Definition - -Resource URI: {apiRoot}/Y1\_RAI\_Subscription/v1/subscriptions - -This resource shall support the resource URI variables defined in Table 6.2.4.2.2. - -**Table 6.2.4.2.2-1: Resource URI variables for this resource** - -| Name | Data type | Definition | -|---------|-----------|--------------------| -| apiRoot | string | See clause 5.2.3.1 | - -##### 6.2.4.2.3 Resource Standard Methods - -###### 6.2.4.2.3.1 HTTP POST - -This method shall support the URI query parameters specified in Table 6.2.4.2.3.1-1. - -**Table 6.2.4.2.3.1-1: URI query parameters supported by the POST method on this resource** - -| Name | Data type | P | Cardinality | Description | -|------|-----------|---|-------------|-------------| -| n/a | | | | | - -This method shall support the request data structures specified in Table 6.2.4.2.3.1-2 and the response data structures and response codes specified in Table 6.2.4.2.3.1-3. - -**Table 6.2.4.2.3.1-2: Data structures supported by the POST Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-----------------|---|-------------|-------------------------------------------------------| -| RaiSubscription | M | 1 | Create a new Individual Y1 RAI Subscription resource. | - -**Table 6.2.4.2.3.1-3: Data structures supported by the POST Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|-----------------|---|-------------|---------------------------|----------------------------------------------------------------------------------------------------------------------------| -| RaiSubscription | M | 1 | 201 Created | The creation of an Individual Y1 RAI Subscription resource is confirmed and a representation of that resource is returned. | -| ProblemDetails | O | 0..1 | 500 Internal Server Error | (NOTE 2) | - -NOTE 1: The mandatory HTTP error status codes for the POST method used by [7] also apply. See clause 5.2.5. - -NOTE 2: Failure cases are described in clause 6.2.8. - -**Table 6.2.4.2.3.1-4: Headers supported by the 201 Response Code on this resource** - -| Name | Data type | P | Cardinality | Description | -|----------|-----------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------| -| Location | string | M | 1 | Contains the URI of the newly created resource, according to the structure:
{apiRoot}/Y1_RAI_Subscription/v1/subscriptions/{subscriptionId} | - -##### 6.2.4.2.4 Resource Custom Operations - -Void. - -#### 6.2.4.3 Resource: Individual Y1 RAI Subscription - -##### 6.2.4.3.1 Description - -The Individual Y1 RAI Subscription resource represents a single subscription to the Y1\_RAI\_Subscription service via Y1 interface. - -##### 6.2.4.3.2 Resource definition - -Resource URI: {apiRoot}/Y1\_RAI\_Subscription/v1/subscriptions/{subscriptionId} - -This resource shall support the resource URI variables defined in Table 6.2.4.3.2-1. - -**Table 6.2.4.3.2-1: Resource URI variables for this resource** - -| Name | Data type | Definition | -|----------------|-----------|--------------------------------------------------------------| -| apiRoot | string | See clause 5.2.3.1 | -| subscriptionId | string | Identifies a subscription to the Y1_RAI_Subscription service | - -##### 6.2.4.3.3 Resource Standard Methods - -###### 6.2.4.3.3.1 HTTP DELETE - -This method shall support the URI query parameters specified in Table 6.2.4.3.3.1-1. - -**Table 6.2.4.3.3.1-1: URI query parameters supported by the DELETE method on this resource** - -| Name | Data type | P | Cardinality | Description | -|------|-----------|---|-------------|-------------| -| n/a | | | | | - -This method shall support the request data structures specified in Table 6.2.4.3.3.1-2 and the response data structures and response codes specified in Table 6.2.4.3.3.1-3. - -**Table 6.2.4.3.3.1-2: Data structures supported by the DELETE Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|-------------| -| n/a | | | | - -**Table 6.2.4.3.3.1-3: Data structures supported by the DELETE Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|-----------|---|-------------|----------------|------------------------------------------------------------------------------------------------------| -| n/a | | | 204 No Content | Successful case: The Individual Y1 RAI Subscription resource matching the subscriptionId is deleted. | - -NOTE 1: The mandatory HTTP error status codes for the DELETE method used by [7] also apply. See clause 5.2.5. - -###### 6.2.4.3.3.2 HTTP PUT - -This method shall support the URI query parameters specified in Table 6.2.4.3.3.2-1. - -**Table 6.2.4.3.3.2-1: URI query parameters supported by the PUT method on this resource** - -| Name | Data type | P | Cardinality | Description | -|------|-----------|---|-------------|-------------| -| n/a | | | | | - -This method shall support the request data structures specified in Table 6.2.4.3.3.2-2 and the response data structures and response codes specified in Table 6.2.4.3.3.2-3. - -**Table 6.2.4.3.3.2-2: Data structures supported by the PUT Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-----------------|---|-------------|---------------------------------------------------------------------------| -| RaiSubscription | M | 1 | Parameters to update an existing Individual Y1 RAI Subscription resource. | - -**Table 6.2.4.3.3.2-3: Data structures supported by the PUT Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|-----------------|---|-------------|---------------------------|-------------------------------------------------------------------------------------------------------------------------| -| RaiSubscription | M | 1 | 200 OK | The Individual Y1 RAI Subscription resource is modified successfully and a representation of that resource is returned. | -| n/a | | | 204 No Content | The Individual Y1 RAI Subscription resource is modified successfully. | -| ProblemDetails | O | 0..1 | 500 Internal Server Error | (NOTE 2) | - -NOTE 1: The mandatory HTTP error status codes for the PUT method used by [7] also apply. See clause 5.2.5. -NOTE 2: Failure cases are described in clause 6.2.8. - -##### 6.2.4.3.4 Resource Custom Operations - -Void. - -### 6.2.5 Custom operations without associated resources - -Void. - -### 6.2.6 Notifications - -#### 6.2.6.1 General - -The notifications are summarized in Table 6.2.6.1-1. - -**Table 6.2.6.1-1: Notifications overview** - -| Notification | Callback URI | Mapped HTTP method | Description (service operation) | -|------------------|-----------------------------|--------------------|---------------------------------| -| RAI Notification | {notificationTargetAddress} | POST | RAI_Notify operation. | - -#### **6.2.6.2 RAI Notification** - -##### **6.2.6.2.1 Description** - -The RAI Notification is used by the Near-RT RIC to report RAI to a Y1 consumer that has subscribed to such RAI associated with an Individual Y1 RAI Subscription resource, or to notify termination of the RAI subscription. - -##### **6.2.6.2.2 Operation Definition** - -Callback URI: {notificationTargetAddress} - -The operation shall support the URI variables defined in Table 6.2.6.2.2-1, the request data structures specified in Table 6.2.6.2.2-2 and the response data structure and response codes specified in Table 6.2.6.2.2-3. - -**Table 6.2.6.2.2-1: URI variables** - -| Name | Data type | Definition | -|---------------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------| -| notificationTargetAddress | Uri | The Notification URI as assigned within the Individual Y1 RAI Subscription resource and described within the RAISubscription type. | - -**Table 6.2.6.2.2-2: Data structures supported by the POST Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-----------------|---|-------------|---------------------------------------------------------------| -| RaiNotification | M | 1 | Provides RAI or notifies termination of the RAI subscription. | - -**Table 6.2.6.2.2-3: Data structures supported by the POST Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|-------------------------------------------------------------------------------------------------------------|---|-------------|----------------|-------------------------------------------------------| -| n/a | | | 204 No Content | The RAI Notification is acknowledged by the receiver. | -| NOTE: The mandatory HTTP error status codes for the DELETE method used by [7] also apply. See clause 5.2.5. | | | | | - -### **6.2.7 Data model** - -#### **6.2.7.1 General** - -This clause specifies the application data model. - -Table 6.2.7.1-1 specifies the data types defined for the Y1\_RAI\_Subscription API in this specification. - -**Table 6.2.7.1-1: Y1\_RAI\_Subscription specific data types in this specification** - -| Data type | Clause | Description | Applicability | -|------------------------|-----------|---------------------------------------------------------------------------|---------------| -| NotificationCriteria | 6.2.7.2.3 | Contains the timing or the event that triggers RAI notifications. | | -| NotificationMethod | 6.2.7.3.3 | Represents the method used for RAI notifications. | | -| RaiNotification | 6.2.7.2.4 | Represents an individual occurrence of RAI notification. | | -| RaiReport | 6.2.7.2.5 | Represents a RAI report in a RAI notification. | | -| RaiSubscription | 6.2.7.2.2 | Represents an individual RAI subscription. | | -| TerminationCause | 6.2.7.3.4 | Indicates the cause from the Near-RT RIC to terminate a RAI subscription. | | -| ValidityPeriod | 6.2.7.2.7 | Indicate a validity period in UTC time. | | -| ValidityPeriodRelative | 6.2.7.2.6 | Indicate a validity period relative to a RAI notification. | | - -Table 6.2.7.1-2 specifies the data types re-used by the Y1\_RAI\_Subscription API from other specifications. - -**Table 6.2.7.1-2: Y1\_RAI\_Subscription re-used Data Types** - -| Data type | Reference | Comments | Applicability | -|--------------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------|---------------| -| DateTime | 3GPP TS 29.571 [8] | Identifies the actual date and time. | | -| FilterParameters | Y1TD [2] | Describes the filter(s) used for the RAI contents.
This data type is defined per RAI type. | | -| NotificationTriggerEvent | Y1TD [2] | Contains the event that triggers RAI notifications.
This data type is defined per RAI type. | | -| RAIContents | Y1TD [2] | Contains the actual RAI contents.
This data type is defined per RAI type. | | -| RaiTypeId | Y1TD [2] | Indicates the type of RAI. | | -| RaiTypeVersion | Y1TD [2] | Indicates the version of the RAI type. | | -| TargetEntity | Y1TD [2] | Contains information used to identify a target entity with which a RAI report is associated.
This data type is defined per RAI type. | | - -#### 6.2.7.2 Structured data types - -##### 6.2.7.2.1 Introduction - -This clause defines data structures to be used in resource representations. - -##### 6.2.7.2.2 - -###### Type RaiSubscription - -**Table 6.2.7.2.2-1: Definition of type RaiSubscription** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|---------------------------------|-------------------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| raiType | RaiTypeId | M | 1 | The type of RAI. | | -| raiTypeVersion | RaiTypeVersion | M | 1 | Version of the RAI type. | | -| targetEntities | array(TargetEntity) | M | 1..N | Information that identifies the entity/entities to which the requested RAI is related. | | -| expectedValidityPeriodsRelative | array(ValidityPeriodRelative) | O | 1..N | Represents the expected validity period(s) for the RAI, which is relative to the occurrence of a RAI notification. | | -| filterParameters | FilterParameters | O | 1 | The conditions for filtering RAI contents to be included in a RAI notification. | | -| notificationCriteria | NotificationCriteria | M | 1 | Represents the timing or the events when the RAI notifications are triggered. | | -| notificationTargetAddress | Uri | C | 0..1 | Identifies the recipient of RAI notifications sent by the Near-RT RIC.

This parameter shall be supplied by the Y1 consumer in the HTTP POST requests that create the subscriptions for RAI notifications, and in the HTTP PUT requests that update the subscriptions for RAI notifications. | | - -##### 6.2.7.2.3 - -###### Type NotificationCriteria - -**Table 6.2.7.2.3-1: Definition of type NotificationCriteria** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|--------------------------|--------------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| notificationMethod | NotificationMethod | M | 1 | Represents the notification method, e.g., periodic. | | -| notificationPeriod | integer | C | 0..1 | Indicates the periodicity of RAI notifications, in units of milliseconds.

Shall be present when the "notificationMethod" attribute is set to "PERIODIC". | | -| notificationStartTime | DateTime | O | 0..1 | UTC time indicating the expected time of the first RAI notification.

May be present when the "notificationMethod" attribute is set to "PERIODIC". | | -| notificationTriggerEvent | NotificationTriggerEvent | C | 0..1 | Represents the trigger event for RAI notifications.

Shall be present when notificationMethod is set to "EVENT_TRIGGERED". | | - -##### 6.2.7.2.4 Type RaiNotification - -Table 6.2.7.2.4-1: Definition of type RaiNotification - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|-----------------------|------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| subscriptionId | String | M | 1 | Identifies the RAI subscription with which the RAI notification is associated. | | -| terminationIndication | boolean | C | 0..1 | Indicates the termination of the RAI subscription by the Near-RT RIC.
Shall be present and set to "TRUE" when the Near-RT RIC decides to terminate the subscription. | | -| terminationCause | TerminationCause | O | 0..1 | Indicates the reason why Near-RT RIC terminates the RAI subscription.
May be present when the "terminationIndication" attribute is set to "TRUE". | | -| raiReports | array(RaiReport) | C | 1..N | Represents the RAI reports.
Shall be present when the "terminationIndication" attribute is absent or set to "FALSE". | | - -##### 6.2.7.2.5 Type RaiReport - -Table 6.2.7.2.5-1: Definition of type RaiReport - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|------------------------|----------------|---|-------------|----------------------------------------------------------------------------------------------|---------------| -| targetEntity | TargetEntity | M | 1 | The type of RAI. | | -| validityPeriod | ValidityPeriod | M | 1 | The validity period of the RAI report. | | -| raiContents | RaiContents | M | 1 | Contains the actual RAI contents. | | -| confidence | integer | O | 0..1 | Indicates the confidence of a prediction, in unit of percent.
Minimum = 0. Maximum = 100. | | -| timeStampRaiGeneration | DateTime | O | 0..1 | Indicates the timestamp when the RAI report is generated by the Near-RT RIC. | | - -##### 6.2.7.2.6 Type ValidityPeriodRelative - -**Table 6.2.7.2.6-1: Definition of type ValidityPeriodRelative** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|---------------------|-----------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| startTimeRelative | integer | M | 1 | Indicate the start time of the validity period in a relative manner, which is expressed as a time offset relative to the time of the RAI notification, in units of milliseconds. A negative value means a point of time before the RAI notification, and a positive value means a point of time after the RAI notification. | | -| durationMilliSecond | integer | O | 0..1 | Indicate the duration of validity period, in units of milliseconds. The absence of the attribute means a zero duration, i.e., the RAI is calculated only for the point of time given by the start time of the validity period. | | - -##### 6.2.7.2.7 Type ValidityPeriod - -**Table 6.2.7.2.7-1: Definition of type ValidityPeriod** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|---------------------|-----------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| startTime | DateTime | M | 1 | Indicate the start time of the validity period in UTC time. | | -| durationMilliSecond | integer | O | 0..1 | Indicate the duration of validity period, in units of milliseconds. The absence of the attribute means a zero duration, i.e., the RAI is calculated only for the point of time given by the start time of the validity period. | | - -#### 6.2.7.3 Simple data types and enumerations - -##### 6.2.7.3.1 Introduction - -This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. - -##### 6.2.7.3.2 Simple data types - -The simple data types defined in Table 6.2.7.3.2-1 shall be supported. - -**Table 6.2.7.3.2-1: Simple data types** - -| Type Name | Type Definition | Description | Applicability | -|-----------|-----------------|-------------|---------------| -| n/a | | | | - -##### 6.2.7.3.3 Enumeration: NotificationMethod - -**Table 6.2.7.3.3-1: Enumeration NotificationMethod** - -| Enumeration value | Description | Applicability | -|-------------------|------------------------------------------------------------|---------------| -| PERIODIC | The RAI notifications are sent with certain time interval. | | -| EVENT_TRIGGERED | The RAI notifications are triggered by certain event. | | - -##### 6.2.7.3.4 Enumeration: TerminationCause - -**Table 6.2.7.3.4-1: Enumeration TerminationCause** - -| Enumeration value | Description | Applicability | -|-------------------|----------------------------------------------------------------------------------|---------------| -| UNKNOWN | Indicates the RAI subscription is terminated due to unknown reasons. | | -| OVERLOAD | Indicates the RAI subscription is terminated due to overload in the Near-RT RIC. | | - -### 6.2.8 Error handling - -#### 6.2.8.1 General - -The generic mechanism for error handling is described in clause 5.2.5. In addition, the requirements in the following clause 6.2.8.2 and clause 6.2.8.3 shall be applied. - -#### 6.2.8.2 Protocol Errors - -Void. - -#### 6.2.8.3 Application Errors - -The application errors specific to the Y1\_RAI\_Subscription API are listed in Table 6.2.8.3-1. The Near-RT RIC shall include in the HTTP status code a "ProblemDetails" data structure with the "cause" attribute indicating the application error as listed in Table 6.2.8.3-1. - -**Table 6.2.8.3-1: Application errors** - -| Application Error | HTTP status code | Description | -|-------------------|---------------------------|---------------------------------------------------------------------------------------------------------| -| DATA_UNAVAILABLE | 500 Internal Server Error | Indicates the RAI subscription is rejected since necessary data to perform the analysis is unavailable. | - -## 6.3 Y1\_RAI\_Query service API - -### 6.3.1 Introduction - -The Y1\_RAI\_Query API is used to access the Y1\_RAI\_Query service. - -The service operations and corresponding API definitions are organized in the following clauses for solution 1. - -### 6.3.2 Void - -### 6.3.3 Service operations - -#### 6.3.3.1 Introduction - -Table 6.3.3.1-1 lists the operations supported by the Y1\_RAI\_Query service for the solution "HTTP REST with JSON". - -**Table 6.3.3.1-1: Operations of the Y1\_RAI\_Subscription service** - -| Service operation name | Description | Initiated by | -|------------------------|-----------------------------------------------------------------------------------------|--------------| -| RAI_Query | This service operation is used by a Y1 consumer to query specific RAI from Near-RT RIC. | Y1 consumer | - -#### 6.3.3.2 RAI\_Query service operation - -##### 6.3.3.2.1 General - -The RAI\_Query service operation is used by a Y1 consumer to query specific RAI from the Near-RT RIC. - -##### 6.3.3.2.2 Query RAI - -Figure 6.3.3.2.2-1 shows a scenario where the Y1 consumer sends a request to the Near-RT RIC to query RAI. The operation is based on HTTP GET. - -``` -@startuml -participant "Y1 consumer" as cons -participant "Near-RT RIC" as prod -cons ->> prod : 1. GET ../analytics?query_parameters -prod ->> cons : 2. 200 OK -@enduml -``` - -![Sequence diagram showing the interaction between Y1 consumer and Near-RT RIC. The Y1 consumer sends a GET request to the Near-RT RIC, and the Near-RT RIC responds with a 200 OK status.](f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg) - -``` -sequenceDiagram - participant Y1_consumer as Y1 consumer - participant Near_RT_RIC as Near-RT RIC - Note left of Y1_consumer: Y1 consumer - Y1_consumer->>Near_RT_RIC: 1. GET ../analytics?query_parameters - Note right of Near_RT_RIC: Near-RT RIC - Near_RT_RIC-->>Y1_consumer: 2. 200 OK - Note left of Y1_consumer: Y1 consumer - Note right of Near_RT_RIC: Near-RT RIC -``` - -Sequence diagram showing the interaction between Y1 consumer and Near-RT RIC. The Y1 consumer sends a GET request to the Near-RT RIC, and the Near-RT RIC responds with a 200 OK status. - -**Figure 6.3.3.2.2-1: Y1 consumer query a RAI** - -The Y1 consumer shall send an HTTP GET request to the Near-RT RIC on the resource URI "{apiRoot}/Y1\_RAI\_Query//analytics" representing the "Y1 RAI" resource, to request RAI. - -NOTE: The path segment " Y1\_RAI\_Query " does not follow the related naming convention specified in clause 5.2.4.1 of [7]. The path segment is however kept as currently defined in this specification for backward compatibility considerations. - -The following information shall be provided: - -- the type of RAI as the "raiType" attribute; -- the version of the RAI type as the "raiTypeVersion" attribute; -- the target entity/entities of the RAI in the "targetEntities" attribute. - -The following information may be provided: - -- the expected validity period(s) for the RAI in the "expectedValidityPeriods" attribute; an expected validity period before the occurrence of a RAI query refers to statistics for a past time, and an expected validity period after the occurrence of a RAI query refers to a prediction for a future time. -- the filter parameters to filter RAI contents in the RAI report as the "filterParameters" attribute; - -Upon the reception of the HTTP GET request, the Near-RT RIC shall generate corresponding RAI according to the request. - -If the HTTP request message from the Y1 consumer is accepted, the Near-RT RIC shall respond with "200 OK" status code with the message body containing the RAI with parameters as relevant for the requesting Y1 consumer. The "raiQueryResult" data structure in the response body shall include: - -- the RAI reports in the "raiReports" attribute that, for each RAI report, the "RaiReport" data type shall include: - - the target entity of the RAI report as the "targetEntity" attribute; - - the validity period of the RAI report as the "validityPeriod" attribute; - - the actual RAI contents as the "raiContents" attribute; - and may include: - - the confidence of the RAI report, if the RAI report is a prediction; - - the timestamp when Near-RT RIC generates the RAI report as the "timeStampRaiGeneration" attribute. - -If an error occurs when processing the HTTP POST request, the Near-RT RIC shall send an HTTP error response as specified in clause 6.3.8. In particular, - -- If the necessary data to perform the analysis are unavailable, the Near-RT RIC shall reject the request with a "500 Internal Server Error" status code and a "ProblemDetails" data structure including the "cause" attribute set to "DATA\_UNAVAILABLE". - -### 6.3.4 Resources - -#### 6.3.4.1 Resource URI structure - -The resource URI shall have the structure as defined in clause 5.2.3.1 with the following clarifications: - -- The shall be "Y1\_RAI\_Query". -- The shall be "v1". -- The shall be set as illustrated in figure 6.3.4.1-1. - -![Diagram showing the URI structure {apiRoot}/Y1_RAI_Query/v1 with a callout box pointing to the path part containing /analytics.](d3b5eac55166fc428a223bba5c46961b_img.jpg) - -``` - - {apiRoot}/Y1_RAI_Query/v1 - | - +--- /analytics - -``` - -Diagram showing the URI structure {apiRoot}/Y1\_RAI\_Query/v1 with a callout box pointing to the path part containing /analytics. - -Figure 6.3.4.1-1: Resource URI structure of the Y1\_RAI\_Query API - -Table 6.3.4.1-1 provides an overview of the resources and applicable HTTP methods for the Y1\_RAI\_Query API. - -Table 6.3.4.1-1: Resources and methods overview - -| Resource name | API specific resource URI part | HTTP method or custom operation | Description | -|---------------|--------------------------------|---------------------------------|------------------| -| Y1 RAI | /analytics | GET | Retrieve the RAI | - -#### 6.3.4.2 Resource: Y1 RAI - -##### 6.3.4.2.1 Description - -The Y1 RAI resource represents the RAI to the RAI\_Query Service at a given Near-RT RIC. - -##### 6.3.4.2.2 Resource Definition - -Resource URI: {apiRoot}/Y1\_RAI\_Query/v1/analytics - -This resource shall support the resource URI variables defined in Table 6.3.4.2.2-1. - -**Table 6.3.4.2.2-1: Resource URI variables for this resource** - -| Name | Data type | Definition | -|---------|-----------|--------------------| -| apiRoot | string | See clause 5.2.3.1 | - -##### **6.3.4.2.3 Resource Standard Methods** - -###### **6.3.4.2.3.1 HTTP GET** - -This method shall support the URI query parameters specified in Table 6.3.4.2.3.1-1. - -**Table 6.3.4.2.3.1-1: URI query parameters supported by the GET method on this resource** - -| Name | Data type | P | Cardinality | Description | -|-------------------------|-----------------------|---|-------------|----------------------------------------------------------------------------------------| -| raiType | RaiTypeId | M | 1 | Indicates the type of RAI. | -| raiTypeVersion | RaiTypeVersion | M | 1 | Indicates the version of the RAI type. | -| targetEntities | array(TargetEntity) | M | 1..N | Information that identifies the entity/entities to which the requested RAI is related. | -| expectedValidityPeriods | array(ValidityPeriod) | O | 1..N | Represents the expected validity period(s) for the RAI. | -| filterParameters | FilterParameters | O | 1 | Describes the filter(s) used for the RAI contents. | - -NOTE: The query parameters "raiType", "raiTypeVersion", "targetEntities", "expectedValidityPeriods" and "filterParameters" do not follow the related naming convention specified in clause 5.2.4.1 of [7]. These query parameters are however kept as currently defined in this specification for backward compatibility considerations. - -This method shall support the request data structures specified in Table 6.3.4.2.3.1-2 and the response data structures and response codes specified in Table 6.3.4.2.3.1-3. - -**Table 6.3.4.2.3.1-2: Data structures supported by the GET Request Body on this resource** - -| Data type | P | Cardinality | Description | -|-----------|---|-------------|-------------| -| n/a | | | | - -**Table 6.3.4.2.3.1-3: Data structures supported by the GET Response Body on this resource** - -| Data type | P | Cardinality | Response codes | Description | -|----------------|---|-------------|---------------------------|-------------------------------------------------------------------------------| -| RaiQueryResult | M | 1 | 200 OK | Containing the RAI with parameters as relevant for the requesting Y1 consumer | -| ProblemDetails | O | 0..1 | 500 Internal Server Error | (NOTE 2) | - -NOTE 1: The mandatory HTTP error status codes for the GET method used by [7] also apply. See clause 5.2.5. -NOTE 2: Failure cases are described in clause 6.3.8. - -### **6.3.5 Custom operations without associated resources** - -Void. - -### **6.3.6 Notifications** - -Void. - -### **6.3.7 Data model** - -#### **6.3.7.1 General** - -Table 6.3.7.1-1 specifies the data types defined for the Y1\_RAI\_Query API in this specification. - -**Table 6.3.7.1-1: Y1\_RAI\_Query specific data types in this specification** - -| Data type | Clause | Description | Applicability | -|----------------|-----------|------------------------------------------------------------|---------------| -| RaiQueryResult | 6.3.7.2.2 | Contains the RAI with parameters indicated in the request. | | - -Table 6.3.7.1-2 specifies the data types re-used by the Y1\_RAI\_Query API from other specifications. - -**Table 6.3.7.1-2: Y1\_RAI\_Query re-used Data Types** - -| Data type | Reference | Comments | Applicability | -|------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------|---------------| -| DateTime | 3GPP TS 29.571 [8] | Identifies the actual date and time. | | -| FilterParameters | Y1TD [2] | Describes the filter(s) used for the RAI contents.
This data type is defined per RAI type. | | -| RAIContents | Y1TD [2] | Contains the actual RAI contents.
This data type is defined per RAI type. | | -| RaiReport | 6.2.7.2.5 | Represents a RAI report in a RAI query result. | | -| RaiTypeId | Y1TD [2] | Indicates the type of RAI. | | -| RaiTypeVersion | Y1TD [2] | Indicates the version of the RAI type. | | -| TargetEntity | Y1TD [2] | Contains information used to identify a target entity with which a RAI report is associated.
This data type is defined per RAI type. | | -| ValidityPeriod | 6.2.7.2.7 | Indicate a validity period in UTC time. | | - -#### 6.3.7.2 Structured data types - -##### 6.3.7.2.1 Introduction - -This clause defines data structures to be used in resource representations. - -##### 6.3.7.2.2 Type RaiQueryResult - -**Table 6.3.7.2.2-1: Definition of type RaiResultSet** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|------------------|---|-------------|-----------------------------|---------------| -| raiReports | array(RaiReport) | M | 1..N | Represents the RAI reports. | | - -#### 6.3.7.3 Simple data types and enumerations - -##### 6.3.7.3.1 Introduction - -This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. - -##### 6.3.7.3.2 Simple data types - -The simple data types defined in Table 6.3.7.3.2-1 shall be supported. - -**Table 6.3.7.3.2-1: Simple data types** - -| Type Name | Type Definition | Description | Applicability | -|-----------|-----------------|-------------|---------------| -| n/a | | | | - -### 6.3.8 Error handling - -#### 6.3.8.1 General - -The generic mechanism for error handling is described in clause 5.2.5. In addition, the requirements in the following clauses shall apply. - -#### 6.3.8.2 Protocol Errors - -In the present document, no additional protocol errors are defined for the Y1\_RAI\_Query API. - -#### 6.3.8.3 Application Errors - -The application errors specific to the Y1\_RAI\_Query API are listed in Table 6.3.8.3-1. The Near-RT RIC shall include in the HTTP status code a "ProblemDetails" data structure with the "cause" attribute indicating the application error as listed in Table 6.2.8.3-1. - -**Table 6.3.8.3-1: Application errors** - -| Application Error | HTTP status code | Description | -|-------------------|---------------------------|---------------------------------------------------------------------------------------------------------| -| DATA_UNAVAILABLE | 500 Internal Server Error | Indicates the RAI subscription is rejected since necessary data to perform the analysis is unavailable. | - -# Annex A (normative): OpenAPI specification - -## A.1 General - -This Annex specifies the formal definition of the Y1 service API(s). It consists of OpenAPI documents in YAML format that are based on the OpenAPI Specification [2]. - -## A.2 Y1\_RAI\_Subscription API - -``` - -openapi: 3.1.0 - -info: - title: Y1_RAI_Subscription API - description: | - Y1_RAI_Subscription API as part of Y1 interface. - © 2026, O-RAN ALLIANCE - All rights reserved. - version: "1.0.0" - -externalDocs: - description: O-RAN.WG3.TS.Y1AP-v01.02 - url: 'https://www.o-ran.org/specifications' - -servers: - - url: '{apiRoot}/Y1_RAI_Subscription/v1' - variables: - apiRoot: - default: https://example.com - description: apiRoot as defined in clause 5.2.3 of O-RAN.WG3.Y1AP-v01.02 - -paths: - /subscriptions: - post: - description: Creates a new Individual Y1 RAI Subscription. - operationId: CreateY1RAISubscription - requestBody: - required: true - content: - application/json: - schema: - $ref: '#/components/schemas/RaiSubscription' - responses: - '201': - description: > - The Individual Y1 RAI Subscription resource is created successfully and a - representation of that resource is returned. - content: - application/json: - schema: - $ref: '#/components/schemas/RaiSubscription' - headers: - Location: - description: > - Contains the URI of the newly created resource, according to the structure - {apiRoot}/Y1_RAI_Subscription/v1/subscriptions/{subscriptionId} - required: true - schema: - type: string - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '411': - $ref: '#/components/responses/411' - -``` - -``` - - '413': - $ref: '#/components/responses/413' - '415': - $ref: '#/components/responses/415' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '503': - $ref: '#/components/responses/503' - default: - $ref: '#/components/responses/default' - callbacks: - RAINotification: - '{ $request.body#/notificationTargetAddress }': - post: - requestBody: # contents of the callback message - required: true - content: - application/json: - schema: - $ref: '#/components/schemas/RaiNotification' - responses: - '204': - description: No Content (successful notification) - '307': - $ref: '#/components/responses/307' - '308': - $ref: '#/components/responses/308' - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '411': - $ref: '#/components/responses/411' - '413': - $ref: '#/components/responses/413' - '415': - $ref: '#/components/responses/415' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '503': - $ref: '#/components/responses/503' - default: - $ref: '#/components/responses/default' - -/subscriptionId: - delete: - description: Deletes an Individual Y1 RAI Subscription. - operationId: DeleteY1RAISubscription - parameters: - - name: subscriptionId - in: path - description: Identifier of the Individual Y1 RAI Subscription - required: true - schema: - type: string - responses: - '204': - description: > - The Individual Y1 RAI Subscription resource matching the subscriptionId is deleted. - '307': - $ref: '#/components/responses/307' - '308': - $ref: '#/components/responses/308' - '400': - $ref: '#/components/responses/400' - '401': - -``` - -``` - - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '503': - $ref: '#/components/responses/503' - default: - $ref: '#/components/responses/default' -put: - description: Updates an Individual Y1 RAI Subscription - operationId: UpdateY1RAISubscription - requestBody: - required: true - content: - application/json: - schema: - $ref: '#/components/schemas/RaiSubscription' - parameters: - - name: subscriptionId - in: path - description: Identifier of the Individual Y1 RAI Subscription - required: true - schema: - type: string - responses: - '200': - description: > - The Individual Y1 RAI Subscription resource is updated successfully and a - representation of that resource is returned. - content: - application/json: - schema: - $ref: '#/components/schemas/RaiSubscription' - '204': - description: The Individual Y1 RAI Subscription resource is updated successfully. - '307': - $ref: '#/components/responses/307' - '308': - $ref: '#/components/responses/308' - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - $ref: '#/components/responses/404' - '411': - $ref: '#/components/responses/411' - '413': - $ref: '#/components/responses/413' - '415': - $ref: '#/components/responses/415' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '503': - $ref: '#/components/responses/503' - default: - $ref: '#/components/responses/default' - -components: - schemas: - RaiSubscription: - type: object - description: Represents an Individual RAI Subscription resource. - properties: - raiType: - -``` - -``` - - $ref: '#/components/schemas/RaiTypeId' - raiTypeVersion: - $ref: '#/components/schemas/RaiTypeVersion' - targetEntities: - type: array - items: - $ref: '#/components/schemas/TargetEntity' - minItems: 1 - expectedValidityPeriodsRelative: - type: array - items: - $ref: '#/components/schemas/ValidityPeriodRelative' - filterParameters: - $ref: '#/components/schemas/FilterParameters' - notificationCriteria: - $ref: '#/components/schemas/NotificationCriteria' - notificationTargetAddress: - $ref: '#/components/schemas/Uri' - required: - - raiType - - raiTypeVersion - - notificationCriteria - - targetEntities - -NotificationCriteria: - type: object - description: Contains the timing or event that triggers RAI notifications. - properties: - notificationMethod: - $ref: '#/components/schemas/NotificationMethod' - notificationPeriod: - type: integer - description: Indicates the interval of periodic RAI notifications in units of milliseconds. - notificationStartTime: - $ref: '#/components/schemas/DateTime' - description: Indicates the expected time of the first notification for the periodic RAI -notifications. - notificationTriggerEvent: - $ref: '#/components/schemas/NotificationTriggerEvent' - required: - - notificationMethod - -RaiNotification: - type: object - description: Represents a RAI notification. - properties: - subscriptionId: - type: string - description: > - Identifier of the subscription resource to which the RAI notification - is related. - terminationIndication: - type: boolean - description: When true, indicates the termination of the RAI subscription by the Near-RT RIC. - terminationCause: - $ref: '#/components/schemas/TerminationCause' - raiReports: - type: array - items: - $ref: '#/components/schemas/RaiReport' - minItems: 1 - required: - - subscriptionId - -RaiTypeId: - type: string - description: Indicates the type of RAI. It is defined in Y1TD. - -RaiTypeVersion: - type: string - description: Indicates the version of the RAI type. It is defined in Y1TD. - -RaiContents: - type: object - -``` - -description: Contains the actual RAI contents. It is defined in Y1TD per RAI type. - -### RaiReport: - -type: object -description: Represents a RAI report in a RAI notification. -properties: -targetEntity: -\$ref: '#/components/schemas/TargetEntity' -validityPeriod: -\$ref: '#/components/schemas/ValidityPeriod' -raiContents: -\$ref: '#/components/schemas/RaiContents' -confidence: -type: integer -minimum: 0 -maximum: 100 -description: Indicates the confidence of a prediction, in unit of percent. -timeStampRaiGeneration: -\$ref: '#/components/schemas/DateTime' -description: The date and time when the RAI report is generated. -required: -- targetEntity -- validityPeriod -- raiContents - -### TargetEntity: - -type: object -description: Contains information used to identify a target entity with which a RAI report is associated. It is defined in Y1TD per RAI type. - -### TerminationCause: - -type: string -enum: -- UNKNOWN -- OVERLOAD -description: Indicates the cause from the Near-RT RIC to terminate a RAI subscription. - -### ValidityPeriodRelative: - -type: object -description: Indicate a validity period relative to a RAI notification. -properties: -startTimeRelative: -type: integer -description: Indicate the start time of the validity period in a relative manner, which is expressed as a time offset relative to the time of the RAI notification, in units of milliseconds -durationMilliSecond: -type: integer -description: Indicate the duration of validity period, in units of milliseconds. -required: -- startTimeRelative - -### ValidityPeriod: - -type: object -description: Indicate a validity period in UTC time. -properties: -startTime: -\$ref: '#/components/schemas/DateTime' -durationMilliSecond: -type: integer -description: Indicate the duration of validity period, in units of milliseconds. -required: -- startTime - -### FilterParameters: - -type: object -description: Describes the filter(s) used for the RAI contents. It is defined in Y1TD per RAI type. - -### NotificationMethod: - -type: string -enum: -- PERIODIC -- EVENT\_TRIGGERED -description: Represents the method used for RAI notifications. - -``` - -NotificationTriggerEvent: - type: object - description: Contains the event that triggers RAI notifications. It is defined in Y1TD per RAI type. - -DateTime: - type: string - format: date-time - description: date and time as defined by RFC3339. - -Uri: - type: string - description: string providing an URI formatted according to IETF RFC 3986. - -ProblemDetails: - type: object - properties: - type: - $ref: '#/components/schemas/Uri' - title: - type: string - description: A short, human-readable summary of the problem type. It should not change from -occurrence to occurrence of the problem. - status: - type: integer - description: The HTTP status code for this occurrence of the problem. - detail: - type: string - description: A human-readable explanation specific to this occurrence of the problem. - instance: - $ref: '#/components/schemas/Uri' - cause: - type: string - description: A machine-readable application error cause specific to this occurrence of the -problem. This IE should be present and provide application-related error information, if available. - invalidParams: - type: array - items: - $ref: '#/components/schemas/InvalidParam' - minItems: 1 - description: Description of invalid parameters, for a request rejected due to invalid -parameters. - -InvalidParam: - type: object - properties: - param: - type: string - description: Attribute's name encoded as a JSON Pointer, or header's name. - reason: - type: string - description: A human-readable reason, e.g. "must be a positive integer". - required: - - param - -# -# HTTP Responses -# -responses: - '307': - description: Temporary Redirect - headers: - Location: - description: 'An alternative URI of the resource.' - required: true - schema: - type: string - '308': - description: Permanent Redirect - headers: - Location: - description: 'An alternative URI of the resource.' - required: true - schema: - type: string - '400': - -``` - -``` - description: Bad request - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '401': - description: Unauthorized - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '403': - description: Forbidden - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '404': - description: Not Found - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '406': - description: Not Acceptable - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '409': - description: Conflict - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '411': - description: Length Required - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '412': - description: Precondition Failed - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '413': - description: Payload Too Large - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '414': - description: URI Too Long - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '415': - description: Unsupported Media Type - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '429': - description: Too Many Requests - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '500': - description: Internal Server Error - content: -``` - -``` - -application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -'503': - description: Service Unavailable - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -default: - description: Generic Error - -``` - -## A.3 Y1\_RAI\_Query API - -``` - -openapi: 3.1.0 - -info: - title: Y1_RAI_Query API - description: | - Y1_RAI_Query API as part of Y1 interface. - © 2026, O-RAN ALLIANCE - All rights reserved. - version: "1.0.0" - -externalDocs: - description: O-RAN.WG3.TS.Y1AP-v01.02 - url: 'https://www.o-ran.org/specifications' - -servers: - - url: '{apiRoot}/Y1_RAI_Query/v1' - variables: - apiRoot: - default: https://example.com - description: apiRoot as defined in clause 5.2.3 of O-RAN.WG3.Y1AP-v01.02 - -paths: - /analytics: - get: - description: Retrieve RAI. - operationId: GetY1RAI - parameters: - - name: raiType - in: query - description: Identify the type of RAI. - required: true - schema: - $ref: '#/components/schemas/RaiTypeId' - - name: raiTypeVersion - in: query - description: Identify the version of the RAI type. - required: true - schema: - $ref: '#/components/schemas/RaiTypeVersion' - - name: targetEntities - in: query - description: Identify the entity/entities to which the requested RAI is related. - required: true - schema: - type: array - items: - $ref: '#/components/schemas/TargetEntity' - minItems: 1 - - name: expectedValidityPeriods - in: query - description: Represents the expected validity period(s) for the RAI. - required: false - schema: - type: array - items: - $ref: '#/components/schemas/ValidityPeriod' - - name: filterParameters - in: query - description: Identify the filter(s) used for the RAI contents. - -``` - -``` - - required: false - schema: - $ref: '#/components/schemas/FilterParameters' - responses: - '200': - description: > - Containing the RAI query result with parameters as relevant for the requesting Y1 consumer. - content: - application/json: - schema: - $ref: '#/components/schemas/RaiQueryResult' - '400': - $ref: '#/components/responses/400' - '401': - $ref: '#/components/responses/401' - '403': - $ref: '#/components/responses/403' - '404': - description: Indicates that the Y1 RAI resource does not exist. - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '406': - $ref: '#/components/responses/406' - '414': - $ref: '#/components/responses/414' - '429': - $ref: '#/components/responses/429' - '500': - $ref: '#/components/responses/500' - '503': - $ref: '#/components/responses/503' - default: - $ref: '#/components/responses/default' - -components: - schemas: - RaiQueryResult: - type: object - description: Represents the RAI with parameters as relevant for the requesting Y1 consumer. - properties: - raiReports: - type: array - items: - $ref: '#/components/schemas/RaiReport' - minItems: 1 - required: - - raiReports - - RaiTypeId: - type: string - description: Indicates the type of RAI. It is defined in Y1TD. - - RaiTypeVersion: - type: string - description: Indicates the version of the RAI type. It is defined in Y1TD. - - RaiContents: - type: object - description: Contains the actual RAI contents. It is defined in Y1TD per RAI type. - - RaiReport: - type: object - description: Represents a RAI report in a RAI notification. - properties: - targetEntity: - $ref: '#/components/schemas/TargetEntity' - validityPeriod: - $ref: '#/components/schemas/ValidityPeriod' - raiContents: - $ref: '#/components/schemas/RaiContents' - confidence: - -``` - -``` - - type: integer - minimum: 0 - maximum: 100 - description: Indicates the confidence of a prediction, in unit of percent. - timeStampRaiGeneration: - $ref: '#/components/schemas/DateTime' - description: The date and time when the RAI report is generated. - required: - - targetEntity - - validityPeriod - - raiContents - -FilterParameters: - type: object - description: Describes the filter(s) used for the RAI contents. It is defined in Y1TD per RAI type. - -TargetEntity: - type: object - description: Contains information used to identify a target entity with which a RAI report is -associated. It is defined in Y1TD per RAI type. - -ValidityPeriod: - type: object - description: Indicate a validity period in UTC time. - properties: - startTime: - $ref: '#/components/schemas/DateTime' - durationMilliSecond: - type: integer - description: Indicate the duration of validity period, in units of milliseconds. - required: - - startTime - -DateTime: - type: string - format: date-time - description: date and time as defined by RFC3339. - -Uri: - type: string - description: string providing an URI formatted according to IETF RFC 3986. - -ProblemDetails: - type: object - properties: - type: - $ref: '#/components/schemas/Uri' - title: - type: string - description: A short, human-readable summary of the problem type. It should not change from -occurrence to occurrence of the problem. - status: - type: integer - description: The HTTP status code for this occurrence of the problem. - detail: - type: string - description: A human-readable explanation specific to this occurrence of the problem. - instance: - $ref: '#/components/schemas/Uri' - cause: - type: string - description: A machine-readable application error cause specific to this occurrence of the -problem. This IE should be present and provide application-related error information, if available. - invalidParams: - type: array - items: - $ref: '#/components/schemas/InvalidParam' - minItems: 1 - description: Description of invalid parameters, for a request rejected due to invalid -parameters. - -InvalidParam: - type: object - properties: - -``` - -``` - -param: - type: string - description: Attribute's name encoded as a JSON Pointer, or header's name. -reason: - type: string - description: A human-readable reason, e.g. "must be a positive integer". -required: - - param -# -# HTTP Responses -# -responses: - '307': - description: Temporary Redirect - headers: - Location: - description: 'An alternative URI of the resource.' - required: true - schema: - type: string - '308': - description: Permanent Redirect - headers: - Location: - description: 'An alternative URI of the resource.' - required: true - schema: - type: string - '400': - description: Bad request - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '401': - description: Unauthorized - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '403': - description: Forbidden - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '404': - description: Not Found - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '406': - description: Not Acceptable - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '409': - description: Conflict - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '411': - description: Length Required - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' - '412': - description: Precondition Failed - content: - application/problem+json: - -``` - -``` -schema: - $ref: '#/components/schemas/ProblemDetails' -'413': - description: Payload Too Large - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -'414': - description: URI Too Long - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -'415': - description: Unsupported Media Type - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -'429': - description: Too Many Requests - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -'500': - description: Internal Server Error - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -'503': - description: Service Unavailable - content: - application/problem+json: - schema: - $ref: '#/components/schemas/ProblemDetails' -default: - description: Generic Error -``` - -# Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2023.05.05 | 00.00.01 | Create the skeleton. | -| 2023.10.23 | 00.00.02 | Implemented
CMCC-2023.07.25-WG3-CR-0002-Y1AP-General contents for clause 4 and 5-v02.docx
CMCC-2023.09.04-WG3-CR-0003-Y1AP-Y1_RAI Subscription API-v02.docx
CMCC-2023.10.07-WG3-CR-0004-Y1AP-Y1_RAI Query API-v01.docx
and editorial changes. | -| 2023.10.31 | 00.00.03 | Implemented
CUC-2023.10.27-WG3-CR-0001-Correction-Of-RAI-Notify-v01.docx | -| 2023.11.17 | 00.00.04 | Editorial changes according to the review comments during WG3 poll. | -| 2023.11.18 | 01.00 | Version incremented for publication. | -| 2024.07.08 | 01.00.01 | Implemented
CMCC-2024.05.24-WG3-CR-0005-Y1AP-Editorial corrections for ODR alignment-v01.docx
and editorial changes. | -| 2024.07.22 | 01.00.02 | Editorial changes according to the review comments during WG3 poll. | -| 2024.07.26 | 01.01 | Version incremented for TSC. | -| 2025.11.11 | 01.01.01 | Implemented
CMCC-2025.10.10-WG3-CR-0006-Y1AP-Editing for ODR alignment-v01.docx
and editorial changes. | -| 2025.12.08 | 01.01.02 | Editorial changes according to the review comments during WG3 poll. | -| 2025.12.08 | 01.02 | Version incremented for TSC. | \ No newline at end of file diff --git a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/08783c875dd39684fee7f2a40b584c64_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/11358a9fa9cfdf9faa0e5645ce4336f9_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/185df94f4a6a5245323255e844a30ec0_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/226f5e462c99b71e08dc9abaa5ae260c_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/253600420ae7bd7d0119563b895cbf8a_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/38222c3ae003223a67635bfcc6950fbb_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/3f727e6c0d6658bc53ea10905c4561dd_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg deleted file mode 100644 index 20175171f32a8cb6a16c6c8ff4bf9b6a5e64791e..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8fed5990e919dcc5f8550d7d3c596ecd1f035c062f40e37f877d98023c55037f -size 16747 diff --git a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/4f8349df2ca48959fefb7c42b2bc375e_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/59fcc0e3699f239444841881a2e75da0_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/5ae3023386ee15fae372871afce28865_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/6a5342571eca4b46338fdfb3c42a8055_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/78ffccd66df9bafd96e3e081110d09dd_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/78ffccd66df9bafd96e3e081110d09dd_img.jpg deleted file mode 100644 index 8011c89445548f6bf1af24d6f769534e3d108af2..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/78ffccd66df9bafd96e3e081110d09dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:914f704165383dd210d38d5a63fb049f9e85525e3235a53cf4dff98b3f2f7442 -size 22682 diff --git a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg deleted file mode 100644 index ea6404e990b2a08ec02133a8ffe551a02764e594..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bbdb24de971d0e68015d2c0182bbef747e9f57f57d65db32bdc22f66aef127e8 -size 22835 diff --git a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/7f4320cee12fc1dbb865cc6b67462a91_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/83ee9f10bd3636e192d68decf7f04cec_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/8447c5519e85d7a9e029fbf321da4c4f_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/89100a6476d1d96f22c192db16502fec_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/8d129c93d18909f0643766f372e9ebf6_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/a28ab03366399b5e0a61445bc57e3724_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/a7a2a8be6bea14f9e4740dbb3d24437e_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg deleted file mode 100644 index ae21267aee07424434a5888cb90d06d934be82ff..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d81e7b228a859d8e1b1b4a4e341fedfb51c88be6e00ea4a1fdced424083c02f4 -size 18695 diff --git a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/c389468860cd886ab9c732473e959f0f_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/d3b5eac55166fc428a223bba5c46961b_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/d3b5eac55166fc428a223bba5c46961b_img.jpg deleted file mode 100644 index b87c4396e224065813aed4f935a0f87a48d54d37..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/d3b5eac55166fc428a223bba5c46961b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:78ff1087574fa227938c7f0757faa55916b8dda77b3b163d9043bae82445738d -size 9822 diff --git a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/d879e5f2c388bb87ee9614f63364dcf0_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/da8cb3d696f15f2c6de7aff6955d12d3_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/e511e373339b5f948f239b19e0c37dd4_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/e87df69ebd4cd2dbbf6749079e6c057a_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg deleted file mode 100644 index 5b99c9f770cb7fd2862a5b9ed1f5e32f99ba69b5..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:df855ca2b86969f6b586e5d1d89f3decfc4739f5d9f9e79ff642a107ca2fbfe9 -size 21806 diff --git a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg deleted file mode 100644 index 252b76abe60202bece0c9572c9b6e108200d97ed..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/f0b7aaa539a2f77c98d53ed6c1c2366b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1509ab856d2b8dda704368cbff9860dd1db6def8ef22525479cdce9d0cfa033d -size 24805 diff --git a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/f7dbd497160f02888f34fdf243648aa2_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/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 6bf7a4eeb026fa9751579e14f12f957c1e398688..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1AP-R005-v01.02/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c383a7de2626eae7bb8dcd2578e4d5b598f1267a5990ba41eab855e1024a5839 -size 4517 diff --git a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/doc.md b/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/doc.md deleted file mode 100644 index d04eb1c7eb5820edc3b87549366a867c482ac223..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/doc.md +++ /dev/null @@ -1,410 +0,0 @@ - - -# --- **O-RAN Work Group 3 (Near-Real-time RAN Intelligent Controller and E2 Interface)** - -## **Y1 interface: General Aspects and Principles** - -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. - -# 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 General Aspects ..... 5 - - 4.1 Reference Model for Y1 interface ..... 5 - - 4.2 Y1 interface general principles ..... 5 - - 4.3 Y1 interface specification objectives..... 5 -- 5 Y1 services and operations..... 6 - - 5.1 Introduction..... 6 - - 5.2 Y1\_RAI\_Subscription service ..... 6 - - 5.2.1 General ..... 6 - - 5.2.2 RAI\_Subscribe service operation..... 6 - - 5.2.3 RAI\_Unsubscribe service operation..... 6 - - 5.2.4 RAI\_Notify service operation..... 7 - - 5.3 Y1\_RAI\_Query service ..... 7 - - 5.3.1 General ..... 7 - - 5.3.2 RAI\_Query service operation..... 7 -- 6 Supported information types ..... 8 - - 6.1 Introduction..... 8 - - 6.2 RAI types ..... 8 - - 6.2.1 General ..... 8 - - 6.2.2 RAN performance analytics..... 8 -- 7 Y1 interface protocol structure..... 8 - - 7.1 General..... 8 - - 7.2 Solution 1: HTTP REST with JSON ..... 9 - - 7.2.1 Introduction ..... 9 - - 7.2.2 Network layer..... 9 - - 7.2.3 Transport layer ..... 9 - - 7.2.4 Security..... 9 - - 7.2.5 Application ..... 9 - - 7.2.6 Data interchange..... 10 -- 8 Other Y1 interface specifications..... 10 - - 8.1 Y1 interface: Application Protocol ..... 10 - - 8.2 Y1 interface: Type Definitions ..... 10 -- 9 Other Security aspects..... 10 -- Annex (informative): Change History ..... 11** - -# Foreword - -This Technical Specification (TS) has been produced by WG3 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 stage2 definition of the general aspects and principles of the Y1 interface. - -# 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.WG3.TS.UCR, "Near-Real-time RAN Intelligent Controller, Use Cases and Requirements". -- [3] IETF RFC 9293: "Transmission Control Protocol". -- [4] IETF RFC 5246: "The Transport Layer Security (TLS) Protocol Version 1.2". -- [5] IETF RFC 8446: "The Transport Layer Security (TLS) Protocol Version 1.3". -- [6] IETF RFC 9110: "HTTP Semantics". -- [7] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format". -- [8] IETF RFC 8200: "Internet Protocol, Version 6 (IPv6) Specification". -- [9] IETF RFC 791: "Internet Protocol". -- [10] IETF RFC 9112: "HTTP/1.1". -- [11] IETF RFC 9113: "HTTP/2". -- [12] O-RAN.WG11.TS.SecReqCtlSpecs, "Security Requirements and Controls Specification". -- [13] O-RAN.WG3.TS.Y1AP, "Y1 interface: Application Protocol". -- [14] O-RAN.WG3.TS.Y1TD, "Y1 interface: Type Definitions". - -## 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 3GPP TR 21.905 [i.1] and O-RAN.WG1.TS.OAD [1] 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 [1] 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 [1] and the following apply: - -| | | -|-----|---------------------------| -| RAI | RAN Analytics Information | -|-----|---------------------------| - -# 4 General Aspects - -## 4.1 Reference Model for Y1 interface - -As depicted in Figure 4.1-1, the O-RAN architecture [1] supports authorized consumers, which may be O-RAN or 3GPP NFs, to request RAN analytics information from Near-RT RIC via Y1 interface. - -![Reference Model for Y1 interface diagram showing a Y1 consumer connected to a Near-RT RIC via a Y1 interface.](61374b1b60dadda31f7e83db5cbdde10_img.jpg) - -``` - -graph TD - Y1_consumer[Y1 consumer] --- Y1((Y1)) - Y1 --- Near_RT_RIC[Near-RT RIC] - -``` - -Reference Model for Y1 interface diagram showing a Y1 consumer connected to a Near-RT RIC via a Y1 interface. - -Figure 4.1-1: Reference Model for Y1 interface - -## 4.2 Y1 interface general principles - -The general principles for the specification of the Y1 interface are as follows: - -- The Y1 interface is an open logical interface that enables services to be accessed by authorized consumers; -- The Y1 interface enables a multi-vendor environment and is independent of specific implementations of the Near-RT RIC; -- The Y1 interface is defined in an extensible way that enables new services and data types to be added without needing to change the protocols or the procedures. - -## 4.3 Y1 interface specification objectives - -The Y1 interface shall support the following: - -- inter-connection of Near-RT RIC and Y1 consumers. - -# 5 Y1 services and operations - -## 5.1 Introduction - -Table 5.1-1 illustrates the services that shall be supported on Y1 interface. - -**Table 5.1-1: Services supported on Y1 interface** - -| Service Name | Service Operations | Operation Semantics | -|---------------------|--------------------|---------------------| -| Y1_RAI_Subscription | RAI_Subscribe | Subscribe / Notify | -| | RAI_Unsubscribe | | -| | RAI_Notify | | -| Y1_RAI_Query | RAI_Query | Request / Response | - -## 5.2 Y1\_RAI\_Subscription service - -### 5.2.1 General - -**Service Description:** This service enables Y1 consumer to subscribe/unsubscribe for RAI. - -When the subscription for RAI is accepted by Near-RT RIC, Y1 consumer receives an identifier (Subscription ID) from Near-RT RIC which shall be used to modify or delete this subscription. - -### 5.2.2 RAI\_Subscribe service operation - -**Service operation name:** RAI\_Subscribe. - -**Description:** Y1 consumer subscribes to RAI. - -**The request shall include the following parameters:** - -- RAI type ID: Uniquely identifies the type of RAI; -- Target entity: Information that identifies the entity to which the RAI is related, such as specific UE(s), slice(s), etc.; -- Notification target address: the endpoint for receiving the notification(s) associated with the subscription; -- Notification criteria: indicates the timing or the conditions when the RAI notifications are triggered. - -**The request may include the following parameters:** - -- Filter parameters: The conditions for filtering RAI content to be included in the notification. - -**The response shall include the following parameters:** - -- Subscription ID, if the subscription is accepted; -- Error response, if the subscription is not accepted. - -### 5.2.3 RAI\_Unsubscribe service operation - -**Service operation name:** RAI\_Unsubscribe. - -**Description:** Y1 consumer unsubscribes to RAI. - -**The request shall include the following parameters:** - -- Subscription ID; - -The response shall include the following parameters: - -- Operation execution result. - -### 5.2.4 RAI\_Notify service operation - -**Service operation name:** RAI\_Notify. - -**Description:** Near-RT RIC notifies Y1 consumer of the RAI that has been subscribed to, or termination of the subscription. - -The notification shall include the following parameters: - -- Subscription ID; -- RAI type ID: see clause 5.2.2; - -The notification may include the following parameters: - -- The following parameters, if the notification contains RAI: - - RAI content: The set of attributes that compose a type of RAI, e.g., the longitude/latitude of a hypothetical RAI type “UE Position”; - - Timestamp of RAI generation: The time when the RAI is generated; - - Validity period: The time period for which the RAI is valid; - - Confidence: Probability assertion, if the RAI is a prediction. -- The following parameters, if the notification is to terminate the subscription: - - Subscription termination indication: Indicates by Near-RT RIC that the subscription can no longer be fulfilled. - -The notification acknowledgement shall include the following parameters: - -- Operation execution result. - -## 5.3 Y1\_RAI\_Query service - -### 5.3.1 General - -**Service description:** This service enables Y1 consumer to request and get RAI from Near-RT RIC. - -### 5.3.2 RAI\_Query service operation - -**Service operation name:** RAI\_Query. - -**Description:** Y1 consumer queries RAI. - -The request shall include the following parameters: - -- RAI type ID: see clause 5.2.2; -- Target entity: see clause 5.2.2. - -The request may include the following parameters: - -- Filter parameters: The conditions for filtering RAI content to be included in the response. - -The notification acknowledgement shall include the following parameters: - -- RAI type ID (see clause 5.2.2), if the request is accepted; -- RAI content (see clause 5.2.4), if the request is accepted; - -- Error response, if the request is not accepted. - -The notification acknowledgement may include the following parameters: - -- Timestamp of RAI generation: see clause 5.2.4; -- Validity period: see clause 5.2.4; -- Confidence: see clause 5.2.4. - -# 6 Supported information types - -## 6.1 Introduction - -This clause specifies the information types exposed on Y1 interface. - -## 6.2 RAI types - -### 6.2.1 General - -Table 6.2.1-1 shows the RAI types that may be supported on Y1 interface. - -**Table 6.2.1-1: RAI types supported on Y1 interface** - -| RAI Type ID | Description | -|---------------------------|---------------------------------------------------| -| RAN performance analytics | Statistics or predictions on the RAN performance. | - -### 6.2.2 RAN performance analytics - -With RAN performance analytics, Near-RT RIC provides statistics or predictions on the RAN performance [2]. - -In particular, the following parameter values may be used in a request for this RAI type: - -- Target entity: - - S-NSSAI(s); - - O-RAN UE ID; -- Filter Parameters: - - Subset(s) of analytics of this RAI type; - -# 7 Y1 interface protocol structure - -## 7.1 General - -One or more solutions in terms of network protocol and data interchange format may be supported by Y1 interface, which are listed in Table 7.1-1. The use of a specific solution by the Near-RT RIC and the Y1 consumer may be pre-configured. - -**Table 7.1-1: Solution for Y1 interface** - -| Solution | Clause | -|---------------------------------|--------| -| Solution 1: HTTP REST with JSON | 7.2 | - -## 7.2 Solution 1: HTTP REST with JSON - -### 7.2.1 Introduction - -The protocol stack of this solution is shown on Figure 7.2.1-1: - -- TCP [3] shall be used to provide the communication service at the transport layer; -- TLS [4][5] shall be supported to provide secure HTTP [6] connections; -- HTTP [6] shall be used as application-level protocol; -- JSON format [7] shall be used in the data interchange layer for the transport of documents. - -![Illustration of the Y1 protocol stack showing layers from Data Interchange down to Physical.](dbe553cf16dd14073b89a8263a428664_img.jpg) - -| | | -|------------------|-----------------| -| Data Interchange | JSON | -| Application | HTTP | -| Security | TLS | -| Transport | TCP | -| Network | IP | -| Data link | Data link layer | -| Physical | Physical layer | - -Illustration of the Y1 protocol stack showing layers from Data Interchange down to Physical. - -Figure 7.2.1-1: Illustration of the Y1 protocol stack - -### 7.2.2 Network layer - -IPv6 [8] and/or IPv4 [9] may be used as the network layer. - -### 7.2.3 Transport layer - -TCP [3] shall be used as transport protocol. - -### 7.2.4 Security - -The detailed requirements and protocols for security protection are specified in [12], clauses 5.2.7 and 5.1.3.2. - -### 7.2.5 Application - -As application layer, HTTP/1.1 [10] shall be supported, and HTTP/2 [11] should be supported. The HTTP semantics as defined in [6] shall be supported. - -HTTP over TLS [6] shall be supported. - -HTTP details such as use of standard headers, custom headers, error codes, methods, URIs etc. are specified in Application Protocols for Y1 interface [13]. - -The default TCP port numbers should be used for HTTP operation. - -### 7.2.6 Data interchange - -As a data interchange format, JSON [7] shall be supported. - -# --- 8 Other Y1 interface specifications - -## 8.1 Y1 interface: Application Protocol - -Y1AP [13] specifies the Y1 interface application protocols. - -## 8.2 Y1 interface: Type Definitions - -Y1TD [14] specifies the detailed information types (e.g., RAI types) for Y1 interface. - -# --- 9 Other Security aspects - -Void. - -## Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2023.01.10 | 00.00.01 | Create the skeleton. | -| 2023.03.23 | 00.00.02 | Implemented
CMCC-2023.02.02-WG3-CR-0002-Y1GAP-General Aspects in Section 4-v02.docx
CMCC-2023.02.27-WG3-CR-0003-Y1GAP-Y1 services and [operations] in Section 5-v01.docx | -| 2023.04.18 | 00.00.03 | Implemented
CMCC-2023.03.31-WG3-CR-0004-Y1GAP-Supported information types in Section 6-v04.docx
CMCC-2023.04.10-WG3-CR-0005-Y1GAP- Y1 interface protocol structure in Section 7-v03.docx | -| 2023.10.31 | 00.00.04 | Implemented
CMCC-2023.09.04-WG3-CR-0007-Y1GAP-Modification for the attribute of API-v01.docx
CMCC-2023.06.13-WG3-CR-0006-Y1GAP-Text for security aspects-v02.docx
and editorial changes. | -| 2023.11.17 | 00.00.05 | Editorial changes according to the review comments during WG3 poll. | -| 2023.11.18 | 01.00 | Version incremented for publication. | -| 2024.07.05 | 01.00.01 | Implemented
CMCC-2024.05.10-WG3-CR-0008-Y1GAP-Editorial corrections for ODR alignment-v01.docx
and editorial changes. | -| 2024.07.22 | 01.00.02 | Editorial changes according to the review comments during WG3 poll. | -| 2024.07.26 | 01.01 | Version incremented for TSC. | -| 2025.11.11 | 01.01.01 | Implemented
CMCC-2025.10.10-WG3-CR-0009-Y1GAP-Editing for ODR alignment-v01.docx
and editorial changes. | -| 2025.12.08 | 01.02 | Version incremented for TSC. | \ No newline at end of file diff --git a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/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/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index cd15d3d6f918cc6066ba42ec8f0244ce6a9b6549..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6278d4614448b34b99fb5bad2e01af582cf4a1c21f527994324dae32ed6c0d06 -size 4571 diff --git a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/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/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/61374b1b60dadda31f7e83db5cbdde10_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/61374b1b60dadda31f7e83db5cbdde10_img.jpg deleted file mode 100644 index c0c99c0dee0819ea638c99d5f8ccbfc4b5f25d6c..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/61374b1b60dadda31f7e83db5cbdde10_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03526cf8e80e02bd9a91368d86f7ca8fe713340e34fa529c3d08cbaa57b7996a -size 10087 diff --git a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/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/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/c389468860cd886ab9c732473e959f0f_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/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/dbe553cf16dd14073b89a8263a428664_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/dbe553cf16dd14073b89a8263a428664_img.jpg deleted file mode 100644 index 3a31a252dd924ad1e543407fc7e1a701fc13d122..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/dbe553cf16dd14073b89a8263a428664_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9a8b571dd62be2557f72e0bb3cea6b3fb035d50b70beb8820d28554aa74ba163 -size 28075 diff --git a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/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/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 6bf7a4eeb026fa9751579e14f12f957c1e398688..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1GAP-R005-v01.02/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c383a7de2626eae7bb8dcd2578e4d5b598f1267a5990ba41eab855e1024a5839 -size 4517 diff --git a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/doc.md b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/doc.md deleted file mode 100644 index 6405d2c24f5fa70486030eb08e5be686ddd504a3..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/doc.md +++ /dev/null @@ -1,815 +0,0 @@ - - -# --- **O-RAN Work Group 3 (Near-Real-time RAN Intelligent Controller and E2 Interface)** - -## **Y1 interface: Type Definitions** - -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. - -# 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 General ..... 5 - -4.1 Introduction..... 5 - -5 Basic data types..... 5 - -5.1 Introduction..... 5 - -5.2 Structured data types..... 6 - -5.2.1 Introduction ..... 6 - -5.2.2 Type UeId..... 6 - -5.2.3 Type Distribution ..... 6 - -5.2.4 Type McsDistribution ..... 7 - -5.3 Simple data types and enumerations..... 7 - -5.3.1 Introduction ..... 7 - -5.3.2 Simple data types ..... 7 - -6 RAI specific data types ..... 7 - -6.1 Introduction..... 7 - -6.2 RAI type: RAN performance analytics..... 8 - -6.2.1 Introduction ..... 8 - -6.2.2 Data model ..... 8 - -6.2.2.1 Introduction ..... 8 - -6.2.2.2 Structured data types ..... 8 - -6.2.2.2.1 Introduction..... 8 - -6.2.2.2.2 Type FilterParameters..... 8 - -6.2.2.2.3 Type RaiContents..... 9 - -6.2.2.2.4 Type TargetEntity ..... 12 - -6.2.2.2.5 Type NotificationTriggerEvent..... 12 - -6.2.2.2.6 Type BinRange ..... 12 - -6.2.2.3 Simple data types and enumerations ..... 12 - -6.2.2.3.1 Introduction..... 12 - -6.2.2.3.2 Simple data types ..... 13 - -6.2.2.3.3 Enumeration: AnalyticsAttributeName ..... 13 - -**Annex A (normative): OpenAPI specification ..... 14** - -A.1 General..... 14 - -A.2 RAN performance analytics..... 14 - -**Annex (informative): Change History ..... 19** - -# Foreword - -This Technical Specification (TS) has been produced by WG3 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 stage 3 definition of data types that are applicable in the Y1 interface. - -# 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.WG3.TS.Y1GAP, "Y1 interface: General Aspects and Principles". -- [2] O-RAN.WG3.TS.Y1AP, "Y1 interface: Application Protocol". -- [3] 3GPP TS 38.413: "NG Application Protocol (NGAP)". -- [4] 3GPP TS 29.571: "5G System; Common Data Types for Service Based Interfaces; Stage 3". -- [5] 3GPP TS 28.552: "Management and orchestration; 5G performance measurements". -- [6] O-RAN.WG3.TS.E2SM, "E2 Service Model (E2SM); KPM". -- [7] 3GPP TS 38.314: "NR; Layer 2 Measurements". -- [8] OpenAPI, "OpenAPI 3.1.0 Specification", . -- [9] O-RAN.WG1.TS.OAD, "O-RAN Architecture Description". -- [10] 3GPP TS 38.215: "Physical layer measurements". -- [11] 3GPP TS 29.501: "Principles and Guidelines for Services Definition". - -## 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 3GPP TR 21.905 [i.1], O-RAN.WG1.TS.OAD [9], O-RAN.WG3.TS.Y1GAP [1] and O-RAN.WG3.TS.Y1AP [2] apply. - -## 3.2 Symbols - -For the purposes of the present document, the symbols given in 3GPP TR 21.905 [i.1], O-RAN.WG1.TS.OAD [9], O-RAN.WG3.TS.Y1GAP [1] and O-RAN.WG3.TS.Y1AP [2] 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 [9], O-RAN.WG3.TS.Y1GAP [1] and O-RAN.WG3.TS.Y1AP [2] apply. - -# 4 General - -## 4.1 Introduction - -The data types defined in this document are classified into the following groups: - -- Basic data types for generic usage; -- Data types for RAI. - -The data models for the APIs are documented according to the conventions defined in clause 5.2.4 of 3GPP TS 29.501 [11]. - -# 5 Basic data types - -## 5.1 Introduction - -This clause specifies the basic data types for generic usage. - -Table 5.1-1 summarizes the basic data types defined in this specification. - -**Table 5.1-1: Basic data types defined in this specification** - -| Type Name | Clause | Description | Applicability | -|-----------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| PacketDelay | 5.3.2 | Represents the packet delay. | | -| PacketLossRate | 5.3.2 | Represents the packet loss rate. | | -| UeId | 5.2.2 | Identifies a single UE on the Y1 interface. | | -| Distribution | 5.2.3 | Represents the frequency distribution. | | -| McsDistribution | 5.2.4 | Represents the frequency distribution of MCS for a specific rank indicator and a specific MCS table index (see clause 5.1.1.12.1 and 5.1.1.12.2 of [5]). | | -| Rsrp | 5.3.2 | Represents the RSRP. | | -| Sinr | 5.3.2 | Represents the SINR. | | -| NumLayers | 5.3.2 | Represents the number of MIMO layers. | | -| Bler | 5.3.2 | Represents the BLER. | | - -Table 5.1-2 summarizes the basic data types re-used from other specifications. - -**Table 5.1-2: Reused basic data types** - -| Data type | Reference | Comments | Applicability | -|--------------|--------------------|------------------------------------------------------------------|---------------| -| AmfUeNgapId | 3GPP TS 38.413 [3] | AMF UE NGAP ID. | | -| BitRate | 3GPP TS 29.571 [4] | Bit rate. | | -| Guami | 3GPP TS 29.571 [4] | Globally Unique AMF ID. | | -| Snssai | 3GPP TS 29.571 [4] | S-NSSAI (Single Network Slice Selection Assistance Information). | | -| PduSessionId | 3GPP TS 29.571 [4] | PDU session ID. | | -| Qfi | 3GPP TS 29.571 [4] | QoS Flow ID. | | - -## 5.2 Structured data types - -### 5.2.1 Introduction - -This clause specifies the structured data types. - -### 5.2.2 Type Ueld - -**Table 5.2.2-1: Definition of type Ueld** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-------------|---|-------------|--------------------------------------------------------------------------------------------------------------|---------------| -| amfUeNgapId | AmfUeNgapId | O | 0..1 | AMF UE NGAP ID.
(NOTE 1) | | -| guami | Guami | C | 0..1 | Identify the AMF associated with the AMF UE NGAP ID. Shall be present if "amfUeNgapId" attribute is present. | | - -NOTE 1: The "amfUeNgapId" attribute shall be present as no other UE ID has been defined. - -### 5.2.3 Type Distribution - -**Table 5.2.3-1: Definition of type Distribution** - -| Type Name | Data type | P | Cardinality | Description | Applicability | -|--------------|----------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| distribution | array(integer) | M | 1..N | This attribute represents the frequency distribution. The array corresponds to the bins of the distribution in ascending order, with each element containing the frequency for each bin. | | - -### 5.2.4 Type McsDistribution - -**Table 5.2.4-1: Definition of type McsDistribution** - -| Type Name | Data type | P | Cardinality | Description | Applicability | -|--------------------|--------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| rankIndicatorValue | integer | M | 1 | The value of rank indicator associated with this MCS distribution. See clause 5.1.1.12.1 and 5.1.1.12.2 of [5] for applicable values. | | -| mcsTableIndexValue | integer | M | 1 | The value of MCS table index associated with this MCS distribution. See clause 5.1.1.12.1 and 5.1.1.12.2 of [5] for applicable values. | | -| mcsDistribution | Distribution | C | 0..1 | This attribute represents the actual MCS distribution pertaining to the given rank indicator value and the given MCS table index value. The bins of the distribution represent the MCS values (0-31) in ascending order. This attribute shall be present if at least one bin of the distribution has non-zero value. Otherwise, this attribute shall be absent. | | - -## 5.3 Simple data types and enumerations - -### 5.3.1 Introduction - -This clause specifies the simple data types and the enumerations. - -### 5.3.2 Simple data types - -**Table 5.3.2-1: Simple Data Types** - -| Type Name | Type Definition | Description | -|----------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------| -| PacketDelay | integer | Unsigned integer indicating the packet delay as defined in [3], in units of milliseconds. | -| PacketLossRate | integer | Unsigned integer indicating packet loss rate as defined in [3], in units of tenth of percent.
Minimum = 0. Maximum = 1000. | -| Rsrp | integer | Signed integer indicating RSRP as defined in [9], in units of dBm. | -| Sinr | integer | Signed integer indicating SINR as defined in [9], in units of dB. | -| NumLayers | integer | Unsigned integer indicating the number of MIMO layers, in units of 0.1. | -| Bler | integer | Unsigned integer indicating block error rate, in units of tenth of percent.
Minimum = 0. Maximum = 1000. | - -# 6 RAI specific data types - -## 6.1 Introduction - -The data types for RAI are defined per RAI type as specified in clause 6.2 of [1]. Such data types shall be processed according to the RAI type ID and associated RAI type version in the application protocol messages [2]. - -The RAI types and associated RAI type versions specified in this document are summarized in Table 6.1-1. - -**Table 6.1-1: RAI types and versions** - -| RAI Type ID | Clause | Version | Supported solution sets | -|---------------------------|--------|---------|-------------------------| -| RAN performance analytics | 6.2 | 1.2.0 | JSON | - -Table 6.1-2 summarizes the data types specified per RAI type. - -**Table 6.1-2: RAI type specific data types** - -| Data type | Description | Reference | -|--------------------------|-----------------------------------------------------------------------------------------|-----------| -| RaiTypeId | Indicates the RAI type. | | -| RaiTypeVersion | Indicates the version of the RAI type. | | -| FilterParameters | Describes the filter(s) used for the RAI contents. | | -| RaiContents | Contains the actual RAI. | | -| TargetEntity | Contains information used to identify a target entity with which the RAI is associated. | | -| NotificationTriggerEvent | Describes the event that triggers RAI notifications. | | - -## 6.2 RAI type: RAN performance analytics - -### 6.2.1 Introduction - -This RAI type provides analytics about RAN performance including UE throughput, packet delay, packet loss rate. - -The RAI type ID is "RAN performance analytics". - -The version of the RAI type defined in the present document is "1.2.0". - -### 6.2.2 Data model - -#### 6.2.2.1 Introduction - -The data types dedicated for RAI type "RAN performance analytics" are specified in the following clauses. - -#### 6.2.2.2 Structured data types - -##### 6.2.2.2.1 Introduction - -This clause specifies the structured data types for RAI type "RAN performance analytics". - -##### 6.2.2.2.2 Type FilterParameters - -**Table 6.2.2.2.2-1: Definition of type FilterParameters** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|------------------------|-------------------------------|---|-------------|---------------------------------------------------------------------------------------------------------|---------------| -| analyticsSubsetFilters | array(AnalyticsAttributeName) | O | 1..N | Indicates the subset of attributes in the RAI contents to be reported. | | -| binRangeList | array(BinRange) | O | 1..N | Indicates the list of bin ranges in ascending order used to generate the distribution for RAI contents. | | - -##### 6.2.2.2.3 Type RaiContents - -Table 6.2.2.2.3-1: Definition of type RaiContents - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|--------------------------|----------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| avgRlcThroughput
DI | BitRate | O | 0..1 | The average downlink RLC throughput is defined as the DL Transmitted Data Volume (clause 7.10.1 of [6]) divided by the duration of the validity period, for a specific target entity.
(NOTE 1) | | -| avgRlcThroughput
UI | BitRate | O | 0..1 | The average uplink RLC throughput is defined as the UL Transmitted Data Volume (clause 7.10.2 of [6]) divided by the duration of the validity period, for a specific target entity.
(NOTE 1) | | -| avgPacketDelayDI | PacketDelay | O | 0..1 | The average downlink packet delay is an overall downlink packet delay in RAN that takes into account the packet delay in the CU-UP (clause 5.1.3.3.1 of [5]), on the F1-U interface (clause 5.1.3.3.2 of [5]), in the DU (clause 5.1.3.3.3 of [5]) and on the air interface (clause 5.1.1.1.1 of [5]), for a specific target entity according to the the conversion rule in clause 7.9.0 of [6]. | | -| avgPacketDelayUI | PacketDelay | O | 0..1 | The average uplink packet delay is an overall uplink packet delay in RAN that takes into account the packet delay in the CU-UP (clause 5.1.1.1.5 of [5]), in the DU (clause 5.1.1.1.4 of [5]) and on the air interface (clause 5.1.1.1.3 of [5]), for a specific target entity according to the the conversion rule in clause 7.9.0 of [6].
(NOTE 2) | | -| avgPacketLossRate
eDI | PacketLossRate | O | 0..1 | The average downlink packet loss rate is the overall downlink packet loss rate in RAN that takes into account the packet loss in the CU-UP (clause 5.1.3.2.1 of [5]), on the F1-U interface (clause 5.1.3.1.3 of [5]), in the DU (clause 5.1.3.2.2 of [5]) and on the air interface (clause 4.2.1.5.1 of [7]) during the validity period, for a specific target entity according to the the conversion rule in clause 7.9.0 of [6]. | | - -| | | | | | | -|---------------------|----------------|---|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| avgPacketLossRateUl | PacketLossRate | O | 0..1 | The average uplink packet loss rate is defined as the UL PDCP SDU Loss Rate (clause 5.1.3.1.1 of [5]) during the validity period, for a specific target entity according to the the conversion rule in clause 7.9.0 of [6]. | | -| distPacketDelayDl | Distribution | O | 0..1 | The distribution of DL packet delay between NG-RAN and UE, which is the delay incurred in NG-RAN (including the delay at gNB-CU-UP, on F1-U and on gNB-DU) and the delay over Uu interface (clause 5.1.1.1.6 of [5]), for a specific target entity according to the conversion rule in clause 7.9.0 of [6]. The unit for the bin ranges of the distribution is milliseconds. | | -| distPacketDelayUl | Distribution | O | 0..1 | The distribution of UL packet delay between NG-RAN and UE, which includes the delay occurred in NG-RAN (including the delay at gNB-CU-UP, on F1-U and on gNB-DU) and the delay over Uu interface (excluding the D1 UL PDCP delay occurred in the UE) (clause 5.1.1.1.7.1 of [5]), for a specific target entity according to the conversion rule in clause 7.9.0 of [6]. The unit for the bin ranges of the distribution is milliseconds. | | -| avgRsrpDl | Rsrp | O | 0..1 | The average downlink RSRP is defined as the DL SS-RSRP (clause 7.10.7 of [6]) during the validity period, for a specific target entity. When RSRP is measured for multiple SSBs, the average RSRP value of the SSB with the highest RSRP is used. | | -| avgRsrpUl | Rsrp | O | 0..1 | The average uplink RSRP is defined as the UL SRS-RSRP (clause 7.10.9 of [6]) during the validity period, for a specific target entity. | | -| avgSinrDl | Sinr | O | 0..1 | The average downlink SINR is defined as the DL SS-SINR (clause 7.10.8 of [6]) during the validity period, for a specific target entity. When SINR is measured for multiple SSBs, the average SINR value of the SSB with the highest SINR is used. | | - -| | | | | | | -|-----------------|------------------------|---|------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| -| distMcsDl | array(McsDistribution) | O | 1..N | The distribution(s) of downlink MCS scheduled for PDSCH RB by NG-RAN (clause 5.1.1.12.1 of [5]), for a specific target entity according to the conversion rule in clause 7.9.0 of [6]. | Applicable when MU-MIMO is not used. | -| distMcsUl | array(McsDistribution) | O | 1..N | The distribution(s) of uplink MCS scheduled for PUSCH RB by NG-RAN (clause 5.1.1.12.2 of [5]), for a specific target entity according to the conversion rule in clause 7.9.0 of [6]. | Applicable when MU-MIMO is not used. | -| distMcsMuMimoDl | Distribution | O | 0..1 | The distribution of downlink MCS scheduled for PDSCH RB by NG-RAN in MU-MIMO scenario (clause 5.1.1.12.3 of [5]), for a specific target entity according to the conversion rule in clause 7.9.0 of [6]. The bins represent MCS values (0-31) in ascending order. | Applicable when MU-MIMO is used. | -| distMcsMuMimoUl | Distribution | O | 0..1 | The distribution of uplink MCS scheduled for PUSCH RB by NG-RAN in MU-MIMO scenario (clause 5.1.1.12.4 of [5]), for a specific target entity according to the conversion rule in clause 7.9.0 of [6]. The bins represent MCS values (0-31) in ascending order. | Applicable when MU-MIMO is used. | -| avgNumLayersDl | NumLayers | O | 0..1 | The average number of downlink MIMO layers is defined as the Average value of scheduled MIMO layers per PRB on the DL (clause 5.1.1.30.5 of [5]) during the validity period, for a specific target entity. | | -| avgNumLayersUl | NumLayers | O | 0..1 | The average number of uplink MIMO layers is defined as the Average value of scheduled MIMO layers per PRB on the UL (clause 5.1.1.30.6 of [5]) during the validity period, for a specific target entity. | | -| avgBlerDl | Bler | O | 0..1 | The average downlink BLER is defined as the Total error number of DL TBs (clause 5.1.1.7.4 of [5]) divided by the Total number of DL TBs (clause 5.1.1.7.3 of [5]) during the validity period, for a specific target entity. | | -| avgBlerUl | Bler | O | 0..1 | The average uplink BLER is defined as the Total error number of UL TBs (clause 5.1.1.7.9 of [5]) divided by the Total number of UL TBs (clause 5.1.1.7.8 of [5]) during the validity period, for a specific target entity. | | - -NOTE 1: Different from the measurements in clause 5.1.1.3.1/5.1.1.3.3 of [5], the downlink/uplink average RLC throughput is calculated regardless of data bursts that require one or multiple slots. - -NOTE 2: In the present document, the average uplink packet delay does not include the packet delay on the F1-U interface. - -##### 6.2.2.2.4 Type TargetEntity - -**Table 6.2.2.2.4-1: Definition of type TargetEntity** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|--------------|---|-------------|--------------------------------------|---------------| -| ueId | UeId | O | 0..1 | Indicates a specific UE.
(NOTE 1) | | -| snssai | Snssai | O | 0..1 | Indicate the S-NSSAI. | | -| pduSessionId | PduSessionId | O | 0..1 | Indicates the PDU session ID. | | -| qfi | Qfi | O | 0..1 | Indicates the QoS Flow ID. | | - -The following combination of attributes may be used: - -- ueId: the analytics are on a per-UE basis; -- ueId and snssai: the analytics are on a per-UE-per-slice basis. -- ueId and pduSessionId: the analytics are on a per-UE-per-PDU-session basis. -- ueId, pduSessionId and qfi: the analytics are on a per-UE-per-QoS-flow basis. - -##### 6.2.2.2.5 Type NotificationTriggerEvent - -**Table 6.2.2.2.5-1: Definition of type NotificationTriggerEvent** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-----------|---|-------------|-------------|---------------| -| n/a | | | | (NOTE 1) | | - -##### 6.2.2.2.6 Type BinRange - -**Table 6.2.2.2.6-2: Definition of type BinRange** - -| Attribute name | Data type | P | Cardinality | Description | Applicability | -|----------------|-----------|---|-------------|---------------------------------------------------------------------------------------------------|---------------| -| startValue | integer | M | 1 | Indicates the start value of the bin, which corresponds to "Start Value" in clause 8.3.26 of [6]. | | -| endValue | integer | M | 1 | Indicates the end value of the bin, which corresponds to "End Value" in clause 8.3.26 of [6]. | | - -#### 6.2.2.3 Simple data types and enumerations - -##### 6.2.2.3.1 Introduction - -This clause specifies the simple data types and enumerations for RAI type "RAN performance analytics". - -##### 6.2.2.3.2 Simple data types - -**Table 6.2.2.3.2-1: Simple Data Types** - -| Type Name | Type Definition | Description | -|-----------|-----------------|-------------| -| n/a | | | - -##### 6.2.2.3.3 Enumeration: AnalyticsAttributeName - -**Table 6.2.2.3.3-1: Enumeration AnalyticsAttributeName** - -| Enumeration value | Description | Applicability | -|-------------------------|-------------------------------------------------------------------------------|---------------| -| AVG_RLC_THROUGHPUT_DL | The "avgRlcThroughputDl" attribute for RAI type "RAN performance analytics". | | -| AVG_RLC_THROUGHPUT_UL | The "avgRlcThroughputUl" attribute for RAI type "RAN performance analytics". | | -| AVG_PACKET_DELAY_DL | The "avgPacketDelayDl" attribute for RAI type "RAN performance analytics". | | -| AVG_PACKET_DELAY_UL | The "avgPacketDelayUl" attribute for RAI type "RAN performance analytics". | | -| AVG_PACKET_LOSS_RATE_DL | The "avgPacketLossRateDl" attribute for RAI type "RAN performance analytics". | | -| AVG_PACKET_LOSS_RATE_UL | The "avgPacketLossRateUl" attribute for RAI type "RAN performance analytics". | | -| DIST_PACKET_DELAY_DL | The "distPacketDelayDl" attribute for RAI type "RAN performance analytics". | | -| DIST_PACKET_DELAY_UL | The "distPacketDelayUl" attribute for RAI type "RAN performance analytics". | | -| AVG_RSRP_DL | The "avgRsrpDl" attribute for RAI type "RAN performance analytics". | | -| AVG_RSRP_UL | The "avgRsrpUl" attribute for RAI type "RAN performance analytics". | | -| AVG_SINR_DL | The "avgSinrDl" attribute for RAI type "RAN performance analytics". | | -| DIST_MCS_DL | The "distMcsDl" attribute for RAI type "RAN performance analytics". | | -| DIST_MCS_UL | The "distMcsUl" attribute for RAI type "RAN performance analytics". | | -| DIST_MCS_MU_MIMO_DL | The "distMcsMuMimoDl" attribute for RAI type "RAN performance analytics". | | -| DIST_MCS_MU_MIMO_UL | The "distMcsMuMimoUl" attribute for RAI type "RAN performance analytics". | | -| AVG_NUM_LAYERS_DL | The "avgNumLayersDl" attribute for RAI type "RAN performance analytics". | | -| AVG_NUM_LAYERS_UL | The "avgNumLayersUl" attribute for RAI type "RAN performance analytics". | | -| AVG_BLER_DL | The "avgBlerDl" attribute for RAI type "RAN performance analytics". | | -| AVG_BLER_UL | The "avgBlerUl" attribute for RAI type "RAN performance analytics". | | - -# Annex A (normative): OpenAPI specification - -## A.1 General - -This Annex specifies the formal definition of the Y1 data types in this document. It consists of OpenAPI documents in YAML format that are based on the OpenAPI Specification [8]. - -## A.2 RAN performance analytics - -``` - -openapi: 3.1.0 - -info: - title: Y1 RAI Type RAN performance analytics - description: | - Y1 data types for RAI Type "RAN performance analytics". - © 2026, O-RAN ALLIANCE - All rights reserved. - version: "1.2.0" - -externalDocs: - description: O-RAN.WG3.TS.Y1TD-v03.00 - url: https://www.o-ran.org/specifications - -paths: {} - -components: - schemas: - FilterParameters: - type: object - description: Describes the filter(s) used for the RAI contents. - properties: - analyticsSubsetFilters: - type: array - description: Indicates the subset of attributes in the RAI contents to be reported. - items: - $ref: '#/components/schemas/AnalyticsAttributeName' - binRangeList: - type: array - description: Indicates the list of bin ranges in ascending order used to generate the -distribution for RAI contents. - items: - $ref: '#/components/schemas/BinRange' - - AnalyticsAttributeName: - type: string - enum: - - AVG_RLC_THROUGHPUT_DL - - AVG_RLC_THROUGHPUT_UL - - AVG_PACKET_DELAY_DL - - AVG_PACKET_DELAY_UL - - AVG_PACKET_LOSS_RATE_DL - - AVG_PACKET_LOSS_RATE_UL - - DIST_PACKET_DELAY_DL - - DIST_PACKET_DELAY_UL - - AVG_RSRP_DL - - AVG_RSRP_UL - - AVG_SINR_DL - - DIST_MCS_DL - - DIST_MCS_UL - - DIST_MCS_MU_MIMO_DL - - DIST_MCS_MU_MIMO_UL - - AVG_NUM_LAYERS_DL - - AVG_NUM_LAYERS_UL - - AVG_BLER_DL - - AVG_BLER_UL - description: Indicates an attribute in the RAI contents. - -``` - -``` - -RaiContents: - type: object - description: Contains the actual RAI contents. - properties: - avgRlcThroughputDl: - $ref: '#/components/schemas/BitRate' - description: Indicates the average downlink RLC throughput as described in clause 6.2.2.2.3 of O-RAN.WG3.Y1TD. - avgRlcThroughputUl: - $ref: '#/components/schemas/BitRate' - description: Indicates the average uplink RLC throughput as described in clause 6.2.2.2.3 of O-RAN.WG3.Y1TD. - avgPacketDelayDl: - $ref: '#/components/schemas/PacketDelay' - description: Indicates the averagedownlink packet delay as described in clause 6.2.2.2.3 of O-RAN.WG3.Y1TD. - avgPacketDelayUl: - $ref: '#/components/schemas/PacketDelay' - description: Indicates the averageuplink packet delay as described in clause 6.2.2.2.3 of O-RAN.WG3.Y1TD. - avgPacketLossRateDl: - $ref: '#/components/schemas/PacketLossRate' - description: Indicates the averagedownlink packet loss rate in the air interface as described in clause 6.2.2.2.3 of O-RAN.WG3.Y1TD. - avgPacketLossRateUl: - $ref: '#/components/schemas/PacketLossRate' - description: Indicates the average uplink packet loss rate as described in clause 6.2.2.2.3 of O-RAN.WG3.Y1TD. - distPacketDelayDl: - $ref: '#/components/schemas/Distribution' - description: Indicates the distribution of downlink packet delay as described in clause 6.2.2.2.3 of O-RAN.WG3.Y1TD. - distPacketDelayUl: - $ref: '#/components/schemas/Distribution' - description: Indicates the distribution of uplink packet delay as described in clause 6.2.2.2.3 of O-RAN.WG3.Y1TD. - avgRsrpDl: - $ref: '#/components/schemas/Rsrp' - description: Indicates the average downlink RSRP as described in clause 6.2.2.2.3 of O-RAN.WG3.Y1TD. - avgRsrpUl: - $ref: '#/components/schemas/Rsrp' - description: Indicates the average uplink RSRP as described in clause 6.2.2.2.3 of O-RAN.WG3.Y1TD. - avgSinrDl: - $ref: '#/components/schemas/Sinr' - description: Indicates the average downlink SINR as described in clause 6.2.2.2.3 of O-RAN.WG3.Y1TD. - distMcsDl: - type: array - description: Indicates the distribution(s) of downlink MCS as described in clause 6.2.2.2.3 of O-RAN.WG3.Y1TD. - items: - $ref: '#/components/schemas/McsDistribution' - distMcsUl: - type: array - description: Indicates the distribution(s) of uplink MCS as described in clause 6.2.2.2.3 of O-RAN.WG3.Y1TD. - items: - $ref: '#/components/schemas/McsDistribution' - distMcsMuMimoDl: - $ref: '#/components/schemas/Distribution' - description: Indicates the distribution of downlink MCS in MU-MIMO scenario as described in clause 6.2.2.2.3 of O-RAN.WG3.Y1TD. - distMcsMuMimoUl: - $ref: '#/components/schemas/Distribution' - description: Indicates the distribution of uplink MCS in MU-MIMO scenario as described in clause 6.2.2.2.3 of O-RAN.WG3.Y1TD. - avgNumLayersDl: - $ref: '#/components/schemas/NumLayers' - description: Indicates the average number of downlink MIMO layers as described in clause 6.2.2.2.3 of O-RAN.WG3.Y1TD. - avgNumLayersUl: - $ref: '#/components/schemas/NumLayers' - -``` - -``` - -description: Indicates the average number of uplink MIMO layers as described in clause 6.2.2.2.3 -of O-RAN.WG3.Y1TD. - avgBlerDl: - $ref: '#/components/schemas/Bler' - description: Indicates the average downlink BLER as described in clause 6.2.2.2.3 of O- -RAN.WG3.Y1TD. - avgBlerUl: - $ref: '#/components/schemas/Bler' - description: Indicates the average uplink BLER as described in clause 6.2.2.2.3 of O- -RAN.WG3.Y1TD. - -NotificationTriggerEvent: - type: object - description: Contains the event that triggers RAI notifications. - -BitRate: - type: string - pattern: '^\\d+(\\.\\d+)? (bps|Kbps|Mbps|Gbps|Tbps)$' - description: > - String representing a bit rate prefixes follow the standard symbols from The International - System of Units, and represent x1000 multipliers, with the exception that prefix "K" is - used to represent the standard symbol "k". - -PacketDelay: - type: integer - minimum: 1 - description: Unsigned integer indicating packet delay expressed in milliseconds. - -PacketLossRate: - type: integer - minimum: 0 - maximum: 1000 - description: Unsigned integer indicating packet loss rate expressed in tenth of percent. - -Rsrp: - type: integer - description: Signed integer indicating reference signal received power expressed in dBm. - -Sinr: - type: integer - description: Signed integer indicating signal to noise and interference ratio expressed in dB. - -NumLayers: - type: integer - description: Unsigned integer indicating the number of MIMO layers in units of 0.1. - -Bler: - type: integer - minimum: 0 - maximum: 1000 - description: Unsigned integer indicating block error rate expressed in tenth of percent. - -TargetEntity: - type: object - description: Contains information used to identify a target entity with which the RAI is associated. - properties: - ueId: - $ref: '#/components/schemas/UeId' - snssai: - $ref: '#/components/schemas/Snssai' - pduSessionId: - $ref: '#/components/schemas/PduSessionId' - qfi: - $ref: '#/components/schemas/Qfi' - -UeId: - type: object - description: Indicates a specific UE. - properties: - amfUeNgapId: - $ref: '#/components/schemas/AmfUeNgapId' - guami: - $ref: '#/components/schemas/Guami' - -AmfUeNgapId: - -``` - -``` - -type: integer -description: The AMF UE NGAP ID. -minimum: 0 -maximum: 1099511627775 - -Guami: -type: object -properties: - plmnId: - $ref: '#/components/schemas/PlmnIdNid' - amfId: - $ref: '#/components/schemas/AmfId' -required: -- plmnId -- amfId -description: Globally Unique AMF Identifier constructed out of PLMN, Network and AMF identity. - -PlmnIdNid: -type: object -properties: - mcc: - $ref: '#/components/schemas/Mcc' - mnc: - $ref: '#/components/schemas/Mnc' - nid: - $ref: '#/components/schemas/Nid' -required: -- mcc -- mnc -description: Contains the serving core network operator PLMN ID and, for an SNPN, the NID that -together with the PLMN ID identifies the SNPN. - -Mcc: -type: string -pattern: '^\\d{3}$' -description: Mobile Country Code part of the PLMN, comprising 3 digits, as defined in clause 9.3.3.5 -of 3GPP TS 38.413. - -Mnc: -type: string -pattern: '^\\d{2,3}$' -description: Mobile Network Code part of the PLMN, comprising 2 or 3 digits, as defined in clause -9.3.3.5 of 3GPP TS 38.413. - -Nid: -type: string -pattern: '^[A-Fa-f0-9]{11}$' -description: This represents the Network Identifier, which together with a PLMN ID is used to -identify an SNPN (see 3GPP TS 23.003 and 3GPP TS 23.501 clause 5.30.2.1). - -AmfId: -type: string -pattern: '^[A-Fa-f0-9]{6}$' -description: > - String identifying the AMF ID composed of AMF Region ID (8 bits), AMF Set ID (10 bits) - and AMF Pointer (6 bits) as specified in clause 2.10.1 of 3GPP TS 23.003. It is encoded - as a string of 6 hexadecimal characters (i.e., 24 bits). - -Snssai: -type: object -description: When Snssai needs to be converted to string (e.g. when used in maps as key), the string -shall be composed of one to three digits "sst" optionally followed by "-" and 6 hexadecimal digits "sd". -properties: - sst: - type: integer - minimum: 0 - maximum: 255 - description: > - Unsigned integer, within the range 0 to 255, representing the Slice/Service Type. - It indicates the expected Network Slice behaviour in terms of features and services. - Values 0 to 127 correspond to the standardized SST range. Values 128 to 255 correspond - to the Operator-specific range. See clause 28.4.2 of 3GPP TS 23.003. - Standardized values are defined in clause 5.15.2.2 of 3GPP TS 23.501. - sd: - type: string - -``` - -``` - -pattern: '^[A-Fa-f0-9]{6}$' -description: > - 3-octet string, representing the Slice Differentiator, in hexadecimal representation. - Each character in the string shall take a value of "0" to "9", "a" to "f" or "A" to "F" - and shall represent 4 bits. The most significant character representing the 4 most - significant bits of the SD shall appear first in the string, and the character - representing the 4 least significant bit of the SD shall appear last in the string. - This is an optional parameter that complements the Slice/Service type(s) to allow - to differentiate amongst multiple Network Slices of the same Slice/Service type. - This IE shall be absent if no SD value is associated with the SST. -required: -- sst - -PduSessionId: -type: integer -minimum: 0 -maximum: 255 -description: > - Unsigned integer identifying a PDU session, within the range 0 to 255, as specified in - clause 11.2.3.1b, bits 1 to 8, of 3GPP TS 24.007. If the PDU Session ID is allocated by the - Core Network for UEs not supporting N1 mode, reserved range 64 to 95 is used. PDU Session ID - within the reserved range is only visible in the Core Network. - -Qfi: -type: integer -minimum: 0 -maximum: 63 -description: Unsigned integer identifying a QoS flow, within the range 0 to 63. - -Distribution: -type: array -description: Indicates the frequency distribution. The array corresponds to the bins of the -distribution in ascending order, with each element containing the frequency for each bin. -items: -type: integer - -BinRange: -type: object -description: Indicates the value range of a bin of the distribution. -properties: -startValue: -type: integer -description: Indicates the start value of the bin, which corresponds to "Start Value" defined in -clause 8.3.26 of E2SM KPM. -endValue: -type: integer -description: Indicates the end value of the bin, which corresponds to "End Value" defined in -clause 8.3.26 of E2SM KPM. - -McsDistribution: -type: object -description: Indicates the frequency distribution of MCS for a specific rank indicator and a -specific MCS table index. -properties: -rankIndicatorValue: -type: integer -description: Indicates the value of rank indicator associated with the MCS distribution. -mcsTableIndexValue: -type: integer -description: Indicates the value of MCS table index associated with the MCS distribution. -mcsDistribution: -$ref: '#/components/schemas/Distribution' -description: Indicates the actual MCS distribution pertaining to the given rank indicator value -and the given MCS table index value. - -``` - -# Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2023.09.04 | 00.00.01 | Create the skeleton. | -| 2023.10.24 | 00.00.02 | Implemented
CMCC-2023.09.26-WG3-CR-0002-Y1TD-Basic contents for Y1TD-v02.docx
and editorial changes. | -| 2023.11.17 | 00.00.03 | Editorial changes according to the review comments during WG3 poll. | -| 2023.11.18 | 01.00 | Version incremented for publication. | -| 2024.07.08 | 01.00.01 | Implemented
KDDI-2024.02.15-WG3-CR-0002-Y1TD-Enhancement for delay attributes-v02.docx
KDDI-2024.02.15-WG3-CR-0004-Y1TD-Adding attributes for setting bin ranges for distribution-v02.docx
CMCC-2024.05.27-WG3-CR-0003-Y1TD-Editorial corrections for ODR alignment-v03.docx
and editorial changes. | -| 2024.07.22 | 01.00.02 | Editorial changes according to the review comments during WG3 poll. | -| 2024.07.26 | 01.00.03 | Incremented OpenAPI code version to 1.1.0. | -| 2024.07.26 | 02.00 | Version incremented for TSC. | -| 2025.10.9 | 02.00.01 | Implemented
KDDI-2024.07.30-WG3-CR-0005-Y1TD-Enhancement for QoE Optimization-v06.docx
CMCC-2025.09.22-WG3-CR-0004-Y1TD-Enhancements on Target Entity of RAI-v1.docx
and editorial changes. | -| 2025.11.11 | 02.00.02 | Implemented
CMCC-2025.10.10-WG3-CR-0005-Y1TD-Editing for ODR alignment-v02.docx
and editorial changes. | -| 2025.12.08 | 02.00.03 | Editorial changes according to the review comments during WG3 poll. | -| 2025.12.08 | 03.00 | Version incremented for TSC. | \ No newline at end of file diff --git a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.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/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/185df94f4a6a5245323255e844a30ec0_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/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/226f5e462c99b71e08dc9abaa5ae260c_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/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/253600420ae7bd7d0119563b895cbf8a_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/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.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/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 9a863b394765b18d479d501944f60c148027a95d..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:aeebb8bde371d400db3d90b60ee5b95ef05ccfec1bc00f59e115f62d9778d3fb -size 4523 diff --git a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/83ee9f10bd3636e192d68decf7f04cec_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/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/854df8ad60507803253274673f9062cf_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/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/89100a6476d1d96f22c192db16502fec_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/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/8dcca7651accff77ce832523fe2c7e64_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/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/a28ab03366399b5e0a61445bc57e3724_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/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/c389468860cd886ab9c732473e959f0f_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/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.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/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/e511e373339b5f948f239b19e0c37dd4_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/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 6bf7a4eeb026fa9751579e14f12f957c1e398688..0000000000000000000000000000000000000000 --- a/files/WG3/O-RAN.WG3.TS.Y1TD-R005-v03.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c383a7de2626eae7bb8dcd2578e4d5b598f1267a5990ba41eab855e1024a5839 -size 4517 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/doc.md b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/doc.md deleted file mode 100644 index e90f0278272118389f169e4bae0ed7b0271e47db..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/doc.md +++ /dev/null @@ -1,20037 +0,0 @@ - - -# --- **O-RAN Working Group 4 (Fronthaul Working Group)****Conformance Test Specification** - -Copyright © 2025 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 - -# --- Table of Contents - -| | | | -|-------|--------------------------------|---| -| 1 | Introductory Material..... | 6 | -| 1.1 | Foreword..... | 6 | -| 1.2 | Scope..... | 6 | -| 1.2.1 | General..... | 6 | -| 1.2.2 | U-Plane and C-Plane Scope..... | 6 | -| 1.2.3 | S-Plane..... | 6 | - -| | | | -|-------|-----------------------------------------------------------|----| -| 1.2.4 | Test Requirement Status..... | 7 | -| 1.3 | References..... | 19 | -| 1.4 | Definitions..... | 20 | -| 1.5 | Abbreviations..... | 22 | -| 2 | Test Configuration..... | 23 | -| 2.1 | Test Configuration for O-RU as the Device Under Test..... | 23 | -| 2.2 | Test Configuration for O-DU as the Device Under Test..... | 24 | -| 2.3 | Test Configuration for Shared Cell Configurations..... | 25 | - -| | | | -|---------|----------------------------------------------------------------------|----| -| 2.3.1 | Test Configuration for FHM as the Device Under Test..... | 25 | -| 3 | Conformance Measurements..... | 26 | -| 3.1 | M-Plane Measurements for O-RU..... | 26 | -| 3.1.1 | Transport and Handshake Test Scenarios..... | 26 | -| 3.1.1.1 | Transport and Handshake in IPv4/SSH Environment (positive case)..... | 26 | -| 3.1.1.2 | Transport and Handshake in IPv4/SSH Environment (negative case)..... | 28 | -| 3.1.1.3 | Transport and Handshake in IPv6/SSH Environment (positive case)..... | 29 | -| 3.1.1.4 | Transport and Handshake in IPv6/SSH Environment (negative case)..... | 29 | - -| | | | -|---------|----------------------------------------------------------------------|----| -| 3.1.1.5 | Transport and Handshake in IPv4/TLS Environment (positive case)..... | 29 | -| 3.1.1.6 | Transport and Handshake in IPv4/TLS Environment (negative case)..... | 29 | -| 3.1.1.7 | Transport and Handshake in IPv6/TLS Environment (positive case)..... | 29 | -| 3.1.1.8 | Transport and Handshake in IPv6/TLS Environment (negative case)..... | 29 | -| 3.1.2 | Subscription to Notification..... | 29 | -| 3.1.2.1 | Subscription to NETCONF Event Stream..... | 29 | -| 3.1.3 | M-Plane Connection Supervision..... | 30 | -| 3.1.3.1 | M-Plane connection supervision (positive case)..... | 30 | - -| | | | -|---------|-----------------------------------------------------|----| -| 3.1.3.2 | M-Plane Connection Supervision (negative case)..... | 31 | -| 3.1.4 | Retrieval of O-RU's information elements..... | 32 | -| 3.1.4.1 | Retrieval without Filter Applied..... | 32 | -| 3.1.4.2 | Retrieval with filter applied..... | 33 | -| 3.1.5 | Fault Management..... | 34 | -| 3.1.5.1 | O-RU Alarm Notification Generation..... | 34 | -| 3.1.5.2 | Retrieval of Active Alarm List..... | 35 | -| 3.1.6 | O-RU Software Update..... | 36 | - -| | | | -|---------|----------------------------------------------------------|----| -| 3.1.6.1 | O-RU Software Update and Install (positive case)..... | 36 | -| 3.1.6.2 | O-RU Software Update (negative case)..... | 37 | -| 3.1.7 | O-RU Software Activation..... | 40 | -| 3.1.7.1 | Software Activation without Reset..... | 40 | -| 3.1.7.2 | Supplemental Reset after Software Activation..... | 41 | -| 3.1.8 | Access Control..... | 41 | -| 3.1.8.1 | Sudo on Hybrid M-plane Architecture (positive case)..... | 41 | -| 3.1.8.2 | Access Control Sudo (negative case)..... | 44 | - -| | | | -|----------|----------------------------------------------------------------|----| -| 3.1.8.3 | Access Control NMS (negative case)..... | 45 | -| 3.1.8.4 | Access Control FM-PM (negative case)..... | 46 | -| 3.1.8.5 | Access Control SWM (negative case)..... | 47 | -| 3.1.8.6 | Sudo on Hierarchical M-plane architecture (positive case)..... | 47 | -| 3.1.8.7 | Access Control SMO (negative case)..... | 50 | -| 3.1.8.8 | Access Control Hybrid-ODU (negative case)..... | 51 | -| 3.1.8.9 | Access Control Carrier (negative case)..... | 52 | -| 3.1.8.10 | Access Control change own password..... | 52 | - -- 3.1.9 External Input / Output Ports..... 53 - - 3.1.9.1 External Input Port State Detection.....53 - - 3.1.9.2 External Output Port State Control..... 54 -- 3.1.10 O-RU Configurability..... 56 - - 3.1.10.1 O-RU Configurability Test (positive case)..... 56 - - 3.1.10.2 O-RU Configurability Test (negative case).....58 -- 3.1.11 ALD Communications..... 59 - - 3.1.11.1 ALD Communications Test.....59 - -| | | | -|----------|-----------------------------------------------------------|----| -| 3.1.12 | Log Management..... | 62 | -| 3.1.12.1 | Troubleshooting Test..... | 62 | -| 3.1.12.2 | Trace Test..... | 64 | -| 3.1.13 | Connectivity Check..... | 67 | -| 3.1.13.1 | Ethernet Connectivity Monitoring..... | 67 | -| 3.1.13.2 | UDP Echo Test..... | 68 | -| 3.1.14 | Energy Savings..... | 68 | -| 3.1.14.1 | Carrier Deactivation and Energy Saving Configuration..... | 68 | - -| | | | -|----------|-------------------------------------------------------------------------------------|----| -| 3.1.14.2 | Carrier Activation..... | 69 | -| 3.1.14.3 | Subscription and Reporting of Energy, Power and Environmental (EPE) Statistics..... | 70 | -| 3.1.14.4 | M-Plane based TRX control..... | 72 | -| 3.1.14.5 | Deep-hibernate..... | 76 | -| 3.1.14.6 | Data layer control..... | 77 | -| 3.1a | M-Plane Measurements for O-DU..... | 79 | -| 3.1a.1 | Transport and Handshake Test Scenarios..... | 79 | -| 3.1a.1.1 | Transport and Handshake in IPv4/SSH Environment..... | 79 | - -| | | | -|----------|---------------------------------------------------------|----| -| 3.1a.1.2 | Transport and Handshake in IPv6/SSH Environment..... | 80 | -| 3.1a.1.3 | Transport and Handshake in IPv4/TLS Environment..... | 81 | -| 3.1a.1.4 | Transport and Handshake in IPv6/TLS Environment..... | 81 | -| 3.1a.2 | Subscription to Notifications..... | 81 | -| 3.1a.2.1 | Subscription to NETCONF Event Stream..... | 81 | -| 3.1a.3 | M-Plane Connection Supervision..... | 82 | -| 3.1a.3.1 | M-Plane connection supervision..... | 82 | -| 3.1a.4 | Retrieval of Netconf Server's Information Elements..... | 83 | - -| | | | -|----------|---------------------------------------------------------|----| -| 3.1a.4.1 | Retrieval of Netconf Server's Information Elements..... | 83 | -| 3.1a.5 | Fault Management..... | 84 | -| 3.1a.6 | Software Update..... | 84 | -| 3.1a.6.1 | Software Update and Install..... | 84 | -| 3.1a.7 | Software Activation..... | 86 | -| 3.1a.7.1 | Software Activation..... | 86 | -| 3.1a.8 | Access Control..... | 87 | -| 3.1a.8.1 | Sudo on M-plane Architecture Models..... | 87 | - -- 3.1a.9 Netconf Server Configurability.....88 - - 3.1a.9.1 Netconf Server Configurability Test..... 88 -- 3.1a.10 ALD Communications..... 92 - - 3.1a.10.1 ALD Communications Test.....92 -- 3.1a.11 Log Management..... 95 - - 3.1a.11.1 Troubleshooting Test.....95 - - 3.1a.11.2 Trace Test..... 97 -- 3.1a.12 Connectivity Check.....99 - -| | | | -|-----------|-----------------------------------------|-----| -| 3.1a.12.1 | Ethernet Connectivity Monitoring..... | 99 | -| 3.1a.12.2 | UDP Echo Test..... | 100 | -| 3.1a.13 | Energy Savings..... | 101 | -| 3.1a.13.1 | M-Plane based TRX control..... | 101 | -| 3.1a.13.2 | Deep-hibernate..... | 104 | -| 3.1a.13.3 | Data layer control..... | 106 | -| 3.2 | UC-Plane Measurements O-RU..... | 107 | -| 3.2.1 | UC-Plane Standard Test Definitions..... | 107 | - -| | | | -|---------|--------------------------------------------------------------------|-----| -| 3.2.1.1 | UC-Plane Measurements, O-RU TEST SCENARIO..... | 107 | -| 3.2.2 | Minimum Capabilities of the TER for U-Plane and C-Plane Tests..... | 118 | -| 3.2.2.1 | Signal Analyser..... | 118 | -| 3.2.2.2 | Signal Generator..... | 118 | -| 3.2.2.3 | CUSM-Plane Emulator (CUSM-E)..... | 118 | -| 3.2.3 | FR1 FDD Conducted-Signal Tests..... | 118 | -| 3.2.3.1 | UC-Plane O-RU Scenario Class NR testing Generic (NRG)..... | 118 | -| 3.2.3.2 | UC-Plane O-RU Scenario Class Beamforming (BFM)..... | 165 | - -| | | | -|---------|------------------------------------------------------------|-----| -| 3.2.3.3 | UC-Plane O-RU Scenario Class Compression (CMP)..... | 196 | -| 3.2.3.4 | UC-Plane O-RU Scenario Class Delay Management (DLM)..... | 220 | -| 3.2.3.5 | UC-Plane O-RU Scenario Class Transport (TRN)..... | 228 | -| 3.2.3.6 | UC-Plane O-RU Scenario Class LAA (LAA)..... | 228 | -| 3.2.3.7 | UC-Plane O-RU Scenario Class LTE (LTE)..... | 231 | -| 3.2.3.8 | UC-Plane O-RU Scenario Class Section Type 3 (ST3)..... | 238 | -| 3.2.4 | FR1 FDD Non-conducted OTA Signal Tests..... | 241 | -| 3.2.4.1 | UC-Plane O-RU Scenario Class NR testing Generic (NRG)..... | 241 | - -| | | | -|---------|----------------------------------------------------------|-----| -| 3.2.4.2 | UC-Plane O-RU Scenario Class Beamforming (BFM)..... | 241 | -| 3.2.4.3 | UC-Plane O-RU Scenario Class Compression (CMP)..... | 255 | -| 3.2.4.4 | UC-Plane O-RU Scenario Class Delay Management (DLM)..... | 255 | -| 3.2.4.5 | UC-Plane O-RU Scenario Class Transport (TRN)..... | 255 | -| 3.2.4.6 | UC-Plane O-RU Scenario Class LAA (LAA)..... | 255 | -| 3.2.4.7 | UC-Plane O-RU Scenario Class LTE (LTE)..... | 255 | -| 3.2.4.8 | UC-Plane O-RU Scenario Class Section Type 3 (ST3)..... | 263 | -| 3.2.5 | FR1 TDD Conducted Signal Tests..... | 264 | - -| | | | -|---------|------------------------------------------------------------|-----| -| 3.2.5.1 | UC-Plane O-RU Scenario Class NR testing Generic (NRG)..... | 264 | -| 3.2.5.2 | UC-Plane O-RU Scenario Class Beamforming (BFM)..... | 291 | -| 3.2.5.3 | UC-Plane O-RU Scenario Class Compression (CMP)..... | 319 | -| 3.2.5.4 | UC-Plane O-RU Scenario Class Delay Management (DLM)..... | 341 | -| 3.2.5.5 | UC-Plane O-RU Scenario Class Transport (TRN)..... | 341 | -| 3.2.5.6 | UC-Plane O-RU Scenario Class LAA (LAA)..... | 342 | -| 3.2.5.7 | UC-Plane O-RU Scenario Class LTE (LTE)..... | 342 | -| 3.2.5.8 | UC-Plane O-RU Scenario Class Section Type 3 (ST3)..... | 342 | - -| | | | -|---------|------------------------------------------------------------|-----| -| 3.2.6 | FR1 and FR2 TDD Non-conducted OTA Signal Tests..... | 343 | -| 3.2.6.1 | UC-Plane O-RU Scenario Class NR testing Generic (NRG)..... | 343 | -| 3.2.6.2 | UC-Plane O-RU Scenario Class Beamforming (BFM)..... | 368 | -| 3.2.6.3 | UC-Plane O-RU Scenario Class Compression (CMP)..... | 380 | -| 3.2.6.4 | UC-Plane O-RU Scenario Class Delay Management (DLM)..... | 380 | -| 3.2.6.5 | UC-Plane O-RU Scenario Class Transport (TRN)..... | 380 | -| 3.2.6.6 | UC-Plane O-RU Scenario Class LAA (LAA)..... | 380 | -| 3.2.6.7 | UC-Plane O-RU Scenario Class LTE (LTE)..... | 380 | - -| | | | -|---------|--------------------------------------------------------------------------|-----| -| 3.2.6.8 | UC-Plane O-RU Scenario Class Section Type 3 (ST3)..... | 380 | -| 3.2.7 | Energy Savings..... | 380 | -| 3.2.7.1 | C-Plane based TRX control..... | 381 | -| 3.2.7.2 | Advanced Sleep Mode..... | 390 | -| 3.2.7.3 | Mixed Sleep Modes and Overlapping Commands..... | 399 | -| 3.3 | S-Plane Conformance Tests..... | 405 | -| 3.3.1 | Test Environment..... | 407 | -| 3.3.2 | Functional test of O-RU using ITU-T G.8275.1 profile (LLS-C1/C2/C3)..... | 411 | - -| | | | -|-------|--------------------------------------------------------------------------------------------------------------------------------|-----| -| 3.3.3 | Performance test of O-RU using ITU-T G.8275.1 Profile (LLS-C1/C2/C3)..... | 413 | -| 3.3.4 | Performance test of O-RU using LLS-C4..... | 419 | -| 3.3.5 | Functional test of O-DU Synchronized from ITU-T G.8275.1 profile PRTC/T-GM (LLS-C1/C2/C3/C4)..... | 419 | -| 3.3.6 | Functional test of O-DU Synchronized from Embedded or Local non-PTP PRTC (LLS-C1/C2/C3/C4)..... | 424 | -| 3.3.7 | Performance test of O-DU Synchronized from either Local or Remote PRTC using ITU-T G.8275.1 PTP Profile (LLS-C1/C2/C3/C4)..... | 425 | -| 3.3.8 | Performance test of O-DU Synchronized from Embedded GNSS receiver (LLS-C1/C2/C3/C4)..... | 429 | -| 3.3.9 | Performance test of O-RU using ITU-T G.8275.1 Profile (LLS-C1/C2/C3), additional tests for cascaded O-RUs..... | 430 | - -| | | | -|---------|--------------------------------------------------------------------|-----| -| 3.4 | UC-Plane Measurements O-DU..... | 431 | -| 3.4.1 | UC-Plane Tests..... | 431 | -| 3.4.2 | UC-Plane Standard Test Definitions..... | 431 | -| 3.4.3 | Minimum Capabilities of the TED for U-Plane and C-Plane Tests..... | 431 | -| 3.4.3.1 | Core + O-CU Emulator for Testing a Stand-alone O-DU DUT..... | 431 | -| 3.4.3.2 | Core Emulator for Testing a Combined O-CU + O-DU DUT..... | 432 | -| 3.4.3.3 | X2 Signalling Emulator for NSA..... | 432 | -| 3.2.3.4 | O-RU Emulator..... | 432 | - -| | | | -|---------|------------------------------------------------------------|-----| -| 3.4.3.5 | UE Emulator..... | 432 | -| 3.4.3.6 | Test Configurator through O1 or EMS Interface..... | 432 | -| 3.4.4 | UC-Plane O-DU Test Scenarios..... | 432 | -| 3.4.4.1 | UC-Plane O-DU Scenario Class NR testing Generic (NRG)..... | 432 | -| 3.4.4.2 | UC-Plane O-DU Scenario Class Beamforming (BFM)..... | 433 | -| 3.4.4.3 | UC-Plane O-DU Scenario Class Compression (CMP)..... | 437 | -| 3.4.4.4 | UC-Plane O-DU Scenario Class Delay Management (DLM)..... | 440 | -| 3.5 | Shared-Cell Test Scenarios..... | 441 | - -| | | | -|---------|-------------------------------------------------------------------|-----| -| 3.5.1 | FHM mode Tests..... | 441 | -| 3.5.1.1 | FHM M-Plane Tests..... | 441 | -| 3.5.1.2 | FHM UC-Plane Tests..... | 453 | -| | Annex (informative): Change history/Change request (history)..... | 457 | - -# 1 Introductory Material - -## 1.1 Foreword - -This Technical Specification has been produced by the O-RAN Alliance. - -The contents of the present document are 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 release date and an increase in version number as follows: - -Release x.y.z - -where: - -- x the first digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. (the initial approved document will have x=01). -- y the second digit is incremented when editorial only changes have been incorporated in the document. -- z the third digit included only in working versions of the document indicating incremental changes during the editing process. - -## 1.2 Scope - -### 1.2.1 General - -The present document defines tests that validate the conformance to the protocols defined in [2] for the Lower Layer Split Option 7.2x interface between the O-RU and the O-DU. A guiding principle for these conformance tests is to use only standard interfaces that are defined by the specification [2] or relevant 3GPP specifications. The construction of these tests avoids the requirement for a device to include any special interfaces used solely for the purpose of these tests. - -While these tests are not written to evaluate the performance of an O-DU or O-RU device, some tests require obtaining measurements and evaluating the success or failure of the device to process sample data correctly based on portion of the protocol being tested at the time. - -In general, unless otherwise stated, the tests cover LTE (Stand-Alone), NR Non-Stand-Alone (NSA) and NR Stand-Alone (SA). - -In the main body of this specification (in any “chapter”) the information contained therein is normative meaning binding on any compliant system, unless explicitly described as informative (a capability described as “optional” may or may not be included in a compliant system but if it is included it must comply with the optional capability description). Information contained in an “Annex” to this specification is always informative. - -### 1.2.2 U-Plane and C-Plane Scope - -This version of the Conformance Test specification defines tests which validate the conformance of an O-RU and O-DU. The tests are designed to cover a large number of optional functionalities defined in [2]. Therefore, for any given O-RU implementation, a subset of these tests may not be applicable. It is the responsibility of the tester to understand the applicability of each test to the feature provided by a particular O-RU. - -### 1.2.3 S-Plane - -The Conformance Test specification defines tests for time synchronization of the O-RU and O-DU. The tests defined include both functional and performance tests. Functional tests validate the ability of the O-RU and O-DU to achieve the proper synchronization management state based on a variety of PTP, and optionally SyncE input conditions. Performance tests validate the conformance of the recovered clock for the O-DU or O-RU. - -Concerning the scope of the S-Plane, various synchronization options have been defined in the O-RAN CUS Specification [2] for distributing synchronization to the O-RU (LLS-C1, LLS-C2, LLS-C3 and LLS-C4). Depending on the specific O-RAN deployment being considered not all of them may be relevant. When testing the S-Plane, the tester shall identify which of the test cases are relevant depending on the specific deployment scenarios addressed. As a general guideline the following applies: - -- 1) Direct connection between O-DU and O-RU: - - 1) LLS-C1 is generally the main sync option to be validated. - - 2) LLS-C4 may be considered as alternative or as a complement to C1 -- 2) Synchronization network between O-DU and O-RU - - 3) LLS-C2 for cases where the synchronization is delivered to the O-RU via the O-DU and over the bridged network. In this topology the PRTC synchronizing the O-DU may be local or remote. - - 4) LLS-C3 for cases when the synchronization is distributed to the O-RU without involving the O-DU. In this case one or more PRTC may be remote and may also be local. - - 5) LLS-C4 may be considered as alternative or as a complement to LLS-C2/C3 - -For LLS-C1 and LLS-C2, a local PRTC is either embedded in or co-located with the O-DU. A remote PRTC is located anywhere in the network (backhaul or fronthaul). - -### 1.2.4 Test Requirement Status - -The following tables list each test in this conformance specification and status of the test as MANDATORY or CONDITIONAL MANDATORY or OPTIONAL. Note that tests that are MANDATORY are for those functions of the DUT that by specification are required to be supported. - -Table 1.2.4-1 lists M-Plane tests specifically targeting the protocol conformance of the O-RU, and table 1.2.4-1a describes if an M-Plane test is mandatory conditional mandatory or optional to the O-DU. If a test is MANDATORY, then it shall be included in a conformance test of the DUT. If a test is CONDITIONAL MANDATORY, then it shall be included in a conformance test of DUT if the DUT met the testing condition (e.g., the DUT claims to support the functionality). If a test is OPTIONAL, it is not required to be included in a conformance test of the DUT but it might be included if desired. - -**Table 1.2.4-1 List of O-RU M-Plane Test Scenarios and Status** - -| Test Number | O-RU Test Requirement | Test Description | -|-------------------------|-----------------------|-----------------------------------------------------------------| -| M-Plane for O-RU | | | -| 3.1.1.1 | CONDITIONAL MANDATORY | Transport and Handshake in IPv4/SSH Environment (positive case) | -| 3.1.1.2 | CONDITIONAL MANDATORY | Transport and Handshake in IPv4/SSH Environment (negative case) | -| 3.1.1.3 | CONDITIONAL MANDATORY | Transport and Handshake in IPv6/SSH Environment (positive case) | - -| Test Number | O-RU Test Requirement | Test Description | -|-------------|-----------------------|-----------------------------------------------------------------| -| 3.1.1.4 | CONDITIONAL MANDATORY | Transport and Handshake in IPv6/SSH Environment (negative case) | -| 3.1.1.5 | CONDITIONAL MANDATORY | Transport and Handshake in IPv4/TLS Environment (positive case) | -| 3.1.1.6 | CONDITIONAL MANDATORY | Transport and Handshake in IPv4/TLS Environment (negative case) | -| 3.1.1.7 | CONDITIONAL MANDATORY | Transport and Handshake in IPv6/TLS Environment (positive case) | -| 3.1.1.8 | CONDITIONAL MANDATORY | Transport and Handshake in IPv6/TLS Environment (negative case) | -| 3.1.2.1 | MANDATORY | Subscription to NETCONF Event Stream | -| 3.1.3.1 | MANDATORY | M-Plane Connection Supervision (positive case) | -| 3.1.3.2 | MANDATORY | M-Plane Connection Supervision (negative case) | -| 3.1.4.1 | MANDATORY | Retrieval without Filter Applied | -| 3.1.4.2 | MANDATORY | Retrieval with Filter Applied | -| 3.1.5.1 | MANDATORY | O-RU Alarm Notification Generation | -| 3.1.5.2 | MANDATORY | Retrieval of Active Alarm List | -| 3.1.6.1 | MANDATORY | O-RU Software Update (positive case) | -| 3.1.6.2 | MANDATORY | O-RU Software Update (negative case) | -| 3.1.7.1 | MANDATORY | Software Activation without Reset | -| 3.1.7.2 | MANDATORY | Supplemental Reset after Software Activation | -| 3.1.8.1 | MANDATORY | Sudo on Hybrid M-plane Architecture (positive case) | -| 3.1.8.2 | CONDITIONAL MANDATORY | Access Control Sudo (negative case) | -| 3.1.8.3 | CONDITIONAL MANDATORY | Access Control NMS (negative case) | -| 3.1.8.4 | CONDITIONAL MANDATORY | Access Control FM-PM (negative case) | -| 3.1.8.5 | CONDITIONAL MANDATORY | Access Control SWM (negative case) | -| 3.1.8.6 | MANDATORY | Sudo on Hierarchical M-plane architecture (positive case) | -| 3.1.8.7 | CONDITIONAL MANDATORY | Access Control SMO (negative case) | -| 3.1.8.8 | CONDITIONAL MANDATORY | Access Control Hybrid-ODU (negative case) | -| 3.1.8.9 | CONDITIONAL MANDATORY | Access Control Carrier (negative case) | -| 3.1.8.10 | MANDATORY | Access Control change own password | -| 3.1.9.1 | CONDITIONAL MANDATORY | External Input / Output Ports | -| 3.1.9.2 | CONDITIONAL MANDATORY | External Output Port State Control | -| 3.1.10.1 | MANDATORY | O-RU configurability test (positive case) | -| 3.1.10.2 | MANDATORY | O-RU configurability test (negative case) | -| 3.1.11.1 | CONDITIONAL MANDATORY | ALD Communications Test | -| 3.1.12.1 | MANDATORY | Troubleshooting Test | -| 3.1.12.2 | MANDATORY | Trace Test | - -| Test Number | O-RU Test Requirement | Test Description | -|-------------|-----------------------|--------------------------------------------------------------------------------| -| 3.1.13.1 | CONDITIONAL MANDATORY | Ethernet Connectivity Monitoring | -| 3.1.13.2 | CONDITIONAL MANDATORY | UDP Echo Test | -| 3.1.14.1 | CONDITIONAL MANDATORY | Carrier Deactivation and Energy Saving Configuration | -| 3.1.14.2 | CONDITIONAL MANDATORY | Carrier Activation | -| 3.1.14.3 | CONDITIONAL MANDATORY | Subscription and Reporting of Energy, Power and Environmental (EPE) Statistics | -| 3.1.14.4 | CONDITIONAL MANDATORY | M-plane based TRX control | -| 3.1.14.5 | CONDITIONAL MANDATORY | Deep-hibernate | -| 3.1.14.6 | CONDITIONAL MANDATORY | Data layer control | - -Table 1.2.4-1a List of O-DU M-Plane Test Scenarios and Status - -| Test Number | O-DU Test Requirement | Test Description | -|-------------------------|-----------------------|----------------------------------------------------| -| M-Plane for O-DU | | | -| 3.1a.1.1 | CONDITIONAL MANDATORY | Transport and Handshake in IPv4/SSH Environment | -| 3.1a.1.2 | CONDITIONAL MANDATORY | Transport and Handshake in IPv6/SSH Environment | -| 3.1a.1.3 | CONDITIONAL MANDATORY | Transport and Handshake in IPv4/TLS Environment | -| 3.1a.1.4 | CONDITIONAL MANDATORY | Transport and Handshake in IPv6/TLS Environment | -| 3.1a.2.1 | MANDATORY | Subscription to NETCONF Event Stream | -| 3.1a.3.1 | MANDATORY | M-Plane Connection Supervision | -| 3.1a.4.1 | MANDATORY | Retrieval of Netconf Server's Information Elements | -| 3.1a.6.1 | CONDITIONAL MANDATORY | Software Update and Install | -| 3.1a.7.1 | CONDITIONAL MANDATORY | Software Activation | -| 3.1a.8.1 | CONDITIONAL MANDATORY | Sudo on M-plane Architecture models | -| 3.1a.9.1 | CONDITIONAL MANDATORY | Netconf Server configurability test | -| 3.1a.10.1 | CONDITIONAL MANDATORY | ALD Communications Test | -| 3.1a.11.1 | CONDITIONAL MANDATORY | Troubleshooting Test | -| 3.1a.11.2 | CONDITIONAL MANDATORY | Trace Test | -| 3.1a.12.1 | CONDITIONAL MANDATORY | Ethernet Connectivity Monitoring | -| 3.1a.12.2 | CONDITIONAL MANDATORY | UDP Echo Test | -| 3.1a.13.1 | CONDITIONAL MANDATORY | M-plane based TRX control | -| 3.1a.13.2 | CONDITIONAL MANDATORY | Deep-hibernate | -| 3.1a.13.3 | CONDITIONAL MANDATORY | Data layer control | - -Table 1.2.4-2 List of O-RU UC-Plane Test Scenarios and Status - -| Test Number | O-RU Test Requirement | Test Description | -|--------------------------------------------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------| -| UC-Plane: FR1 FDD Conducted-Signal Tests | | | -| UC-Plane O-RU Scenario Class NR testing Generic (NRG) | | | -| 3.2.3.1.1 | MANDATORY | UC-Plane O-RU Scenario Class NR testing Generic (NRG) | -| 3.2.3.1.2 | MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP DL – Resource allocation | -| 3.2.3.1.3 | MANDATORY | Plane O-RU Base Class FDD Test UL | -| 3.2.3.1.4 | MANDATORY | UC-Plane O-RU Scenario Class Extended using RB Parameter 3GPP DL – Resource Allocation | -| 3.2.3.1.5 | MANDATORY | UC Plane O-RU Scenario Class Extended using RB Parameter 3GPP UL – Resource Allocation | -| 3.2.3.1.6 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using SymInc Parameter 3GPP DL – Resource Allocation | -| 3.2.3.1.7 | CONDITIONAL MANDATORY | UC Plane O-RU Scenario Class Extended using SymInc Parameter 3GPP UL – Resource Allocation | -| 3.2.3.1.8 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using reMask Parameter 3GPP DL – Resource Allocation | -| 3.2.3.1.9 | CONDITIONAL MANDATORY | UC Plane O-RU Scenario Class Extended using reMask Parameter 3GPP UL – Resource Allocation | -| 3.2.3.1.10 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 6 3GPP DL – Resource Allocation | -| 3.2.3.1.11 | CONDITIONAL MANDATORY | UC Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 6 3GPP UL – Resource Allocation | -| 3.2.3.1.12 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Section Extension 10 – Multiple Port Grouping DL – Resource allocation | -| 3.2.3.1.13 | CONDITIONAL MANDATORY | UC Plane O-RU Scenario Class Extended multiple port grouping using section extension 10 UL– Resource Allocation | -| 3.2.3.1.14 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP DL – Resource allocation – Coupling C and U plane via Frequency and Time | -| 3.2.3.1.15 | CONDITIONAL MANDATORY | UC Plane O-RU Base Class FDD Test UL – Coupling C and U plane via time and frequency | -| 3.2.3.1.16 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP DL – Resource allocation – Section Description Priorities | -| 3.2.3.1.17 | N/A | (VOID) | -| 3.2.3.1.18 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 12 3GPP DL – Resource Allocation | -| 3.2.3.1.19 | CONDITIONAL MANDATORY | UC Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 12 3GPP UL – Resource Allocation | -| 3.2.3.1.20 | CONDITIONAL MANDATORY | UC Plane O-RU Base Class FDD Test UL – Static SRS allocation | -| 3.2.3.1.21 | CONDITIONAL MANDATORY | UC Plane O-RU Base Class FDD Test UL – Static PRACH allocation | -| 3.2.3.1.22 | CONDITIONAL MANDATORY | UC Plane O-RU Scenario Class Extended using section extension 13 for frequency hopping UL – Resource Allocation | -| UC-Plane O-RU Scenario Class Beamforming (BFM) | | | -| 3.2.3.2.1 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – No Beamforming | -| 3.2.3.2.2 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – No Beamforming | -| 3.2.3.2.3 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Predefined-beam Beamforming | -| 3.2.3.2.4 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Predefined-beam Beamforming | - -| Test Number | O-RU Test Requirement | Test Description | -|-------------------------------------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------| -| 3.2.3.2.5 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Weight-based Dynamic Beamforming | -| 3.2.3.2.6 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Weight-based Dynamic Beamforming | -| 3.2.3.2.7 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Attribute-based Dynamic Beamforming | -| 3.2.3.2.8 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Attribute-based Dynamic Beamforming | -| 3.2.3.2.9 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Channel-Information-based Beamforming | -| 3.2.3.2.10 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Channel-Information-based Beamforming | -| 3.2.3.2.11 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Flexible Predefined-beam Beamforming | -| 3.2.3.2.12 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Flexible Predefined-beam Beamforming | -| 3.2.3.2.13 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Flexible Real Time Weights Beamforming | -| 3.2.3.2.14 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Flexible Real Time Weights Beamforming | -| 3.2.3.2.15 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Layer nulling Beamforming | -| 3.2.3.2.16 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Layer nulling Beamforming | -| 3.2.3.2.17 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Channel-Information-based Beamforming with mixed numerology | -| 3.2.3.2.18 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Bit masking for antenna mapping in Channel-Information-based Beamforming in uplink direction | -| 3.2.3.2.19 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – User port grouping in Channel-Information-based Beamforming in downlink direction | -| 3.2.3.2.20 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – DMRS based Beamforming | -| 3.2.3.2.21 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – DMRS based Beamforming about Symbol reordering | -| 3.2.3.2.22 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using section extension 24 for DMRS-BF | -| UC-Plane O-RU Scenario Class Compression (CMP) | | | -| 3.2.3.3.2 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Fixed-Point (FP) | -| 3.2.3.3.3 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Floating Point (BFP) | -| 3.2.3.3.4 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Scaling | -| 3.2.3.3.5 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Mu-Law (MLW) | -| 3.2.3.3.6 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Modulation-Compression | -| 3.2.3.3.7 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static (NS) Fixed-Point (FPF) | -| 3.2.3.3.8 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static (NS) Block Floating Point | - -| Test Number | O-RU Test Requirement | Test Description | -|--------------------------------------------------------------|-----------------------|------------------------------------------------------------------------------------------------------------| -| 3.2.3.3.9 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static (NS) Block Scaling (BSC) | -| 3.2.3.3.10 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static (NS) Mu-Law (MLW) | -| 3.2.3.3.11 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) Modulation-Compressed Format | -| 3.2.3.3.12 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Floating Point + Selective RE Format | -| 3.2.3.3.13 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) mod-compr + Selective RE Format | -| 3.2.3.3.14 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) Block Floating Point + Selective RE Format | -| 3.2.3.3.15 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) mod-compr + Selective RE Format | -| UC-Plane O-RU Scenario Class Delay Management (DLM) | | | -| 3.2.3.4.1 | MANDATORY | UC-Plane O-RU Scenario Class DLM Test #1: Downlink – Positive testing | -| 3.2.3.4.2 | MANDATORY | UC-Plane O-RU Scenario Class DLM Test #2: Uplink – Positive testing | -| 3.2.3.4.3 | MANDATORY | UC-Plane O-RU Scenario Class DLM Test #3: Downlink – Negative testing | -| 3.2.3.4.4 | MANDATORY | UC-Plane O-RU Scenario Class DLM Test #4: Uplink – Negative Testing | -| UC-Plane O-RU Scenario Class LAA (LAA) | | | -| 3.2.3.6.1 | CONDITIONAL MANDATORY | CU-DU-LAA-CWM Test #1: LBT PDSCH Configuration and Response | -| UC-Plane O-RU Scenario Class LTE (LTE) | | | -| 3.2.3.7.1 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Base 3GPP DL | -| 3.2.3.7.2 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP DL – Resource Allocation | -| 3.2.3.7.3 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP UL – Resource Allocation | -| 3.2.3.7.4 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using reMask parameter 3GPP DL – Resource allocation | -| 3.2.3.7.5 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class With Precoding (WPR) TxD | -| 3.2.3.7.6 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class With Precoding (WPR) SM | -| UC-Plane O-RU Scenario Class Section Type 3 (ST3) | | | -| 3.2.3.8.1 | MANDATORY | UC-Plane O-RU Scenario Class ST3 Test #1: NR PRACH | -| 3.2.3.8.2 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class ST3 Test #2: LTE PRACH | -| UC-Plane: FR1 FDD Non-conducted OTA Signal Tests | | | -| UC-Plane O-RU Scenario Class NR testing Generic (NRG) | | | -| 3.2.4.1.1 | MANDATORY | UC-Plane O-RU Scenario Class NR testing Generic (NRG) | -| 3.2.4.1.2 | MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP DL – Resource allocation | -| 3.2.4.1.3 | MANDATORY | Plane O-RU Base Class FDD Test UL | - -| Test Number | O-RU Test Requirement | Test Description | -|-------------------------------------------------------|-----------------------|------------------------------------------------------------------------------------------------------------------------------| -| 3.2.4.1.4 | MANDATORY | UC-Plane O-RU Scenario Class Extended using RB Parameter 3GPP DL – Resource Allocation | -| 3.2.4.1.5 | MANDATORY | UC Plane O-RU Scenario Class Extended using RB Parameter 3GPP UL – Resource Allocation | -| 3.2.4.1.6 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using SymInc Parameter 3GPP DL – Resource Allocation | -| 3.2.4.1.7 | CONDITIONAL MANDATORY | UC Plane O-RU Scenario Class Extended using SymInc Parameter 3GPP UL – Resource Allocation | -| 3.2.4.1.8 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using reMask Parameter 3GPP DL – Resource Allocation | -| 3.2.4.1.9 | CONDITIONAL MANDATORY | UC Plane O-RU Scenario Class Extended using reMask Parameter 3GPP UL – Resource Allocation | -| 3.2.4.1.10 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 6 3GPP DL – Resource Allocation | -| 3.2.4.1.11 | CONDITIONAL MANDATORY | UC Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 6 3GPP UL – Resource Allocation | -| 3.2.4.1.12 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Section Extension 10 – Multiple Port Grouping DL – Resource allocation | -| 3.2.4.1.13 | CONDITIONAL MANDATORY | UC Plane O-RU Scenario Class Extended multiple port grouping using section extension 10 UL– Resource Allocation | -| 3.2.4.1.14 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP DL – Resource allocation – Coupling C and U plane via Frequency and Time | -| 3.2.4.1.15 | CONDITIONAL MANDATORY | UC Plane O-RU Base Class FDD Test UL – Coupling C and U plane via time and frequency | -| 3.2.4.1.16 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP DL – Resource allocation – Section Description Priorities | -| 3.2.4.1.17 | CONDITIONAL MANDATORY | UC Plane O-RU Base Class FDD Test UL – Section Description Priorities | -| 3.2.4.1.18 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 12 3GPP DL – Resource Allocation | -| 3.2.4.1.19 | CONDITIONAL MANDATORY | UC Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 12 3GPP UL – Resource Allocation | -| 3.2.4.1.20 | CONDITIONAL MANDATORY | UC Plane O-RU Base Class FDD Test UL – Static SRS allocation | -| 3.2.4.1.21 | CONDITIONAL MANDATORY | UC Plane O-RU Base Class FDD Test UL – Static PRACH allocation | -| 3.2.4.1.22 | CONDITIONAL MANDATORY | UC Plane O-RU Scenario Class Extended using section extension 13 for frequency hopping UL – Resource Allocation | -| UC-Plane O-RU Scenario Class Beamforming (BFM) | | | -| 3.2.4.2.1 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – No Beamforming | -| 3.2.4.2.2 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – No Beamforming | -| 3.2.4.2.3 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Predefined-beam Beamforming | -| 3.2.4.2.4 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Predefined-beam Beamforming | -| 3.2.4.2.5 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Weight-based Dynamic Beamforming | -| 3.2.4.2.6 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Weight-based Dynamic Beamforming | -| 3.2.4.2.7 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Attribute-based Dynamic Beamforming | - -| Test Number | O-RU Test Requirement | Test Description | -|------------------------------------------------------------|-----------------------|------------------------------------------------------------------------------------------------------------| -| 3.2.4.2.8 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Attribute-based Dynamic Beamforming | -| 3.2.4.2.9 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Channel-Information-based Beamforming | -| 3.2.4.2.10 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Channel-Information-based Beamforming | -| UC-Plane O-RU Scenario Class Compression (CMP) | | | -| 3.2.4.3.2 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Fixed-Point (FP) | -| 3.2.4.3.3 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Floating Point (BFP) | -| 3.2.4.3.4 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Scaling | -| 3.2.4.3.5 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Mu-Law (MLW) | -| 3.2.4.3.6 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Modulation-Compression | -| 3.2.4.3.7 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static (NS) Fixed-Point (FPF) | -| 3.2.4.3.8 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static (NS) Block Floating Point | -| 3.2.4.3.9 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static (NS) Block Scaling (BSC) | -| 3.2.4.3.10 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static (NS) Mu-Law (MLW) | -| 3.2.4.3.11 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) Modulation-Compressed Format | -| 3.2.4.3.12 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Floating Point + Selective RE Format | -| 3.2.4.3.13 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) mod-compr + Selective RE Format | -| 3.2.4.3.14 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) Block Floating Point + Selective RE Format | -| 3.2.4.3.15 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) mod-compr + Selective RE Format | -| UC-Plane O-RU Scenario Class Delay Management (DLM) | | | -| 3.2.4.4.1 | MANDATORY | UC-Plane O-RU Scenario Class DLM Test #1: Downlink – Positive testing | -| 3.2.4.4.2 | MANDATORY | UC-Plane O-RU Scenario Class DLM Test #2: Uplink – Positive testing | -| 3.2.4.4.3 | MANDATORY | UC-Plane O-RU Scenario Class DLM Test #3: Downlink – Negative testing | -| 3.2.4.4.4 | MANDATORY | UC-Plane O-RU Scenario Class DLM Test #4: Uplink – Negative Testing | -| UC-Plane O-RU Scenario Class LAA (LAA) | | | -| 3.2.4.6.1 | CONDITIONAL MANDATORY | CU-DU-LAA-CWM Test #1: LBT PDSCH Configuration and Response | -| UC-Plane O-RU Scenario Class LTE (LTE) | | | -| 3.2.4.7.1 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Base 3GPP DL | -| 3.2.4.7.2 | CONDITIONAL | UC-Plane O-RU Scenario Class Extended 3GPP DL – Resource Allocation | - -| Test Number | O-RU Test Requirement | Test Description | -|--------------------------------------------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------| -| | MANDATORY | | -| 3.2.4.7.3 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP UL – Resource Allocation | -| 3.2.4.7.4 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using reMask parameter 3GPP DL – Resource allocation | -| 3.2.4.7.5 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class With Precoding (WPR) TxD | -| 3.2.4.7.6 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class With Precoding (WPR) SM | -| UC-Plane O-RU Scenario Class Section Type 3 (ST3) | | | -| 3.2.4.8.1 | MANDATORY | UC-Plane O-RU Scenario Class ST3 Test #1: NR PRACH | -| 3.2.4.8.2 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class ST3 Test #2: LTE PRACH | -| UC-Plane: FR1 TDD Conducted Signal Tests | | | -| UC-Plane O-RU Scenario Class NR testing Generic (NRG) | | | -| 3.2.5.1.1 | MANDATORY | UC-Plane O-RU Scenario Class Base 3GPP DL/UL | -| 3.2.5.1.2 | MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP DL/UL – Resource Allocation | -| 3.2.5.1.3 | MANDATORY | UC-Plane O-RU Scenario Class Extended using RB parameter 3GPP DL/UL – Resource Allocation | -| 3.2.5.1.4 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using SymInc parameter 3GPP DL/UL – Resource Allocation | -| 3.2.5.1.5 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using reMask parameter 3GPP DL/UL – Resource Allocation | -| 3.2.5.1.6 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 6 3GPP DL/UL – Resource Allocation | -| 3.2.5.1.7 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP DL/UL – Resource Allocation – Coupling C and U plane via time and frequency | -| 3.2.5.1.8 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP DL/UL – Coupling C and U plane via Time and Frequency and Section Description Priorities | -| 3.2.5.1.9 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 12 3GPP DL/UL – Resource Allocation | -| 3.2.5.1.10 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Static SRS Allocation UL – Resource Allocation | -| 3.2.5.1.11 | CONDITIONAL MANDATORY | UC Plane O-RU Base Class TDD Test UL – Static PRACH allocation | -| 3.2.5.1.12 | CONDITIONAL MANDATORY | UC Plane O-RU Scenario Class Extended using section extension 13 for frequency hopping UL/DL – Resource Allocation | -| UC-Plane O-RU Scenario Class Beamforming (BFM) | | | -| 3.2.5.2.1 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – No Beamforming | -| 3.2.5.2.2 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – No Beamforming | -| 3.2.5.2.3 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Predefined-beam Beamforming | -| 3.2.5.2.4 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Predefined-beam Beamforming | -| 3.2.5.2.5 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Weight-based Dynamic Beamforming | - -| Test Number | O-RU Test Requirement | Test Description | -|-------------------------------------------------------|-----------------------|------------------------------------------------------------------------------------------------------------| -| 3.2.5.2.6 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Weight-based Dynamic Beamforming | -| 3.2.5.2.7 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Attribute-based Dynamic Beamforming | -| 3.2.5.2.8 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Attribute-based Dynamic Beamforming | -| 3.2.5.2.9 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Channel-Information-based Beamforming | -| 3.2.5.2.10 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Channel-Information-based Beamforming | -| 3.2.5.2.11 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – DMRS based Beamforming | -| 3.2.5.2.12 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – DMRS based Beamforming about Symbol reordering | -| 3.2.5.2.13 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using section 24 for DMRS-BF | -| 3.2.5.2.14 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class RRM Measurements for DMRS-BF | -| 3.2.5.2.15 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using section extension ST9 for DMRS-BF | -| 3.2.5.2.16 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – DMRS based Beamforming using Frequency offset feedback | -| 3.2.5.2.17 | CONDITIONAL MANDATORY | UC Plane O-RU Scenario Class Extended using section extension 27 for DMRS-BF | -| UC-Plane O-RU Scenario Class Compression (CMP) | | | -| 3.2.5.3.2 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Fixed-Point (FP) | -| 3.2.5.3.3 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Floating Point (BFP) | -| 3.2.5.3.4 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Scaling | -| 3.2.5.3.5 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Mu-Law (MLW) | -| 3.2.5.3.6 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Modulation-Compression | -| 3.2.5.3.7 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static (NS) Fixed-Point (FPF) | -| 3.2.5.3.8 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static (NS) Block Floating Point | -| 3.2.5.3.9 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static (NS) Block Scaling (BSC) | -| 3.2.5.3.10 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static (NS) Mu-Law (MLW) | -| 3.2.5.3.11 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) Modulation-Compressed Format | -| 3.2.5.3.12 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Floating Point + Selective RE Format | -| 3.2.5.3.13 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) mod-compr + Selective RE Format | -| 3.2.5.3.14 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) Block Floating Point + Selective RE Format | -| 3.2.5.3.15 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) mod-compr + Selective RE Format | - -| Test Number | O-RU Test Requirement | Test Description | -|-----------------------------------------------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------| -| UC-Plane O-RU Scenario Class Delay Management (DLM) | | | -| 3.2.5.4.1 | MANDATORY | UC-Plane O-RU Scenario Class DLM Test #1: Downlink – Positive testing | -| 3.2.5.4.2 | MANDATORY | UC-Plane O-RU Scenario Class DLM Test #2: Uplink – Positive testing | -| 3.2.5.4.3 | MANDATORY | UC-Plane O-RU Scenario Class DLM Test #3: Downlink – Negative testing | -| 3.2.5.4.4 | MANDATORY | UC-Plane O-RU Scenario Class DLM Test #4: Uplink – Negative Testing | -| UC-Plane O-RU Scenario Class LAA (LAA) | | | -| 3.2.5.6.1 | CONDITIONAL MANDATORY | CU-DU-LAA-CWM Test #1: LBT PDSCH Configuration and Response | -| UC-Plane O-RU Scenario Class LTE (LTE) | | | -| 3.2.5.7.1 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Base 3GPP DL | -| 3.2.5.7.2 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP DL – Resource Allocation | -| 3.2.5.7.3 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP UL – Resource Allocation | -| 3.2.5.7.4 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using reMask parameter 3GPP DL – Resource allocation | -| 3.2.5.7.5 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class With Precoding (WPR) TxD | -| 3.2.5.7.6 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class With Precoding (WPR) SM | -| UC-Plane O-RU Scenario Class Section Type 3 (ST3) | | | -| 3.2.5.8.1 | MANDATORY | UC-Plane O-RU Scenario Class ST3 Test #1: NR PRACH | -| 3.2.5.8.2 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class ST3 Test #2: LTE PRACH | -| UC-Plane: FR1 and FR2 TDD Non-conducted OTA Signal Tests | | | -| UC-Plane O-RU Scenario Class NR testing Generic (NRG) | | | -| 3.2.6.1.1 | MANDATORY | UC-Plane O-RU Scenario Class Base 3GPP DL/UL | -| 3.2.6.1.2 | MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP DL/UL – Resource Allocation | -| 3.2.6.1.3 | CONDITIONAL MANDATORY | 3.2.6.1.3 UC-Plane O-RU Scenario Class Extended using SymInc parameter 3GPP DL/UL – Resource Allocation | -| 3.2.6.1.4 | CONDITIONAL MANDATORY | 3.2.6.1.4 UC-Plane O-RU Scenario Class Extended using reMask parameter 3GPP DL/UL – Resource Allocation | -| 3.2.6.1.5 | MANDATORY | 3.2.6.1.5 UC-Plane O-RU Scenario Class Extended using RB parameter 3GPP DL/UL – Resource Allocation | -| 3.2.6.1.6 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 6 3GPP DL/UL – Resource Allocation | -| 3.2.6.1.7 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP DL/UL – Resource Allocation – Coupling C and U plane via time and frequency | -| 3.2.6.1.8 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended 3GPP DL/UL – Coupling C and U plane via Time and Frequency and Section Description Priorities | -| 3.2.6.1.9 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 12 3GPP DL/UL – Resource Allocation | -| 3.2.6.1.10 | CONDITIONAL | UC-Plane O-RU Scenario Class Static SRS Allocation UL – Resource | - -| Test Number | O-RU Test Requirement | Test Description | -|-------------------------------------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------| -| | MANDATORY | Allocation | -| 3.2.6.1.11 | CONDITIONAL MANDATORY | UC Plane O-RU Base Class TDD Test UL – Static PRACH allocation | -| 3.2.6.1.12 | CONDITIONAL MANDATORY | UC Plane O-RU Scenario Class Extended using section extension 13 for frequency hopping UL/DL – Resource Allocation | -| UC-Plane O-RU Scenario Class Beamforming (BFM) | | | -| 3.2.6.2.1 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – No Beamforming | -| 3.2.6.2.2 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – No Beamforming | -| 3.2.6.2.3 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Predefined-beam Beamforming | -| 3.2.6.2.4 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Predefined-beam Beamforming | -| 3.2.6.2.5 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Weight-based Dynamic Beamforming | -| 3.2.6.2.6 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Weight-based Dynamic Beamforming | -| 3.2.6.2.7 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Attribute-based Dynamic Beamforming | -| 3.2.6.2.8 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Attribute-based Dynamic Beamforming | -| 3.2.6.2.9 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Channel-Information-based Beamforming | -| 3.2.6.2.10 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Channel-Information-based Beamforming | -| UC-Plane O-RU Scenario Class Compression (CMP) | | | -| 3.2.6.3.2 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Fixed-Point (FP) | -| 3.2.6.3.3 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Floating Point (BFP) | -| 3.2.6.3.4 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Scaling | -| 3.2.6.3.5 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Mu-Law (MLW) | -| 3.2.6.3.6 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (SF) Modulation-Compression | -| 3.2.6.3.7 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static (NS) Fixed-Point (FPF) | -| 3.2.6.3.8 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static (NS) Block Floating Point | -| 3.2.6.3.9 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static (NS) Block Scaling (BSC) | -| 3.2.6.3.10 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static (NS) Mu-Law (MLW) | -| 3.2.6.3.11 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) Modulation-Compressed Format | -| 3.2.6.3.12 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (NS) Block Floating Point + Selective RE Format | -| 3.2.6.3.13 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Static Format (NS) mod-compr + Selective RE Format | - -| Test Number | O-RU Test Requirement | Test Description | -|------------------------------------------------------------|-----------------------|------------------------------------------------------------------------------------------------------------| -| 3.2.6.3.14 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) Block Floating Point + Selective RE Format | -| 3.2.6.3.15 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) mod-compr + Selective RE Format | -| UC-Plane O-RU Scenario Class Delay Management (DLM) | | | -| 3.2.6.4.1 | MANDATORY | UC-Plane O-RU Scenario Class DLM Test #1: Downlink – Positive testing | -| 3.2.6.4.2 | MANDATORY | UC-Plane O-RU Scenario Class DLM Test #2: Uplink – Positive testing | -| 3.2.6.4.3 | MANDATORY | UC-Plane O-RU Scenario Class DLM Test #3: Downlink – Negative testing | -| 3.2.6.4.4 | MANDATORY | UC-Plane O-RU Scenario Class DLM Test #4: Uplink – Negative Testing | -| UC-Plane O-RU Scenario Class LAA (LAA) | | | -| 3.2.6.6.1 | CONDITIONAL MANDATORY | CU-DU-LAA-CWM Test #1: LBT PDSCH Configuration and Response | -| UC-Plane O-RU Scenario Class LTE (LTE) | | | -| 3.2.6.7 | For Future Study | | -| UC-Plane O-RU Scenario Class Section Type 3 (ST3) | | | -| 3.2.6.8.1 | MANDATORY | UC-Plane O-RU Scenario Class ST3 Test #1: NR PRACH | -| 3.2.6.8.2 | CONDITIONAL MANDATORY | UC-Plane O-RU Scenario Class ST3 Test #2: LTE PRACH | -| UC-Plane: Energy Savings | | | -| UC-Plane C-Plane based TRX control | | | -| 3.2.7.1.1 | CONDITIONAL MANDATORY | C-plane based TRX control (defined-duration sleep, guaranteed wake-up duration) | -| 3.2.7.1.2 | CONDITIONAL MANDATORY | C-plane based TRX control (defined-duration sleep, minimum wake-up duration) | -| 3.2.7.1.3 | CONDITIONAL MANDATORY | C-plane based TRX control (undefined-duration sleep, guaranteed wake-up duration) | -| 3.2.7.1.4 | CONDITIONAL MANDATORY | C-plane based TRX control (undefined-duration sleep, minimum wake-up duration) | -| 3.2.7.1.5 | CONDITIONAL MANDATORY | C-plane based TRX control (sleep extension) | -| 3.2.7.1.6 | CONDITIONAL MANDATORY | C-plane based TRX control (Emergency wake-up) | -| UC-Plane Advanced Sleep Mode | | | -| 3.2.7.2.1 | CONDITIONAL MANDATORY | Advanced sleep mode (defined-duration sleep, guaranteed wake-up duration) | -| 3.2.7.2.2 | CONDITIONAL MANDATORY | Advanced sleep mode (defined-duration sleep, minimum wake-up duration) | -| 3.2.7.2.3 | CONDITIONAL MANDATORY | Advanced sleep mode (undefined-duration sleep, guaranteed wake-up duration) | -| 3.2.7.2.4 | CONDITIONAL MANDATORY | Advanced sleep mode (undefined-duration sleep, minimum wake-up duration) | -| 3.2.7.2.5 | CONDITIONAL MANDATORY | Advanced sleep mode (sleep extension) | -| 3.2.7.2.6 | CONDITIONAL MANDATORY | Advanced sleep mode (Emergency wake-up) | - -| Test Number | O-RU Test Requirement | Test Description | -|------------------------------------------------------------|-----------------------|--------------------------------------------------------| -| UC-Plane Mixed sleep modes and overlapping commands | | | -| 3.2.7.3.1 | CONDITIONAL MANDATORY | ASM overlapping commands | -| 3.2.7.3.2 | CONDITIONAL MANDATORY | C-plane based TRX Control overlapping sleep modes | -| 3.2.7.3.3 | CONDITIONAL MANDATORY | ASM and C-Plane based TRX control overlapping commands | - -Table 1.2.4-3 List of O-RU or O-DU S-Plane Test Scenarios and Status - -| Test Number | O-RU or O-DU Test Requirement | Test Description | -|----------------------------------|-------------------------------|---------------------------------------------------------------------------------------------------------------------------| -| S-Plane Conformance Tests | | | -| 3.3.2 | MANDATORY | Functional test of O-RU using ITU-T G.8275.1 Profile (LLS-C1/C2/C3) | -| 3.3.3 | MANDATORY | Performance test of O-RU using ITU-T G.8275.1 Profile (LLS-C1/C2/C3) | -| 3.3.4 | For Future Study | Performance test of O-RU using LLS-C4 | -| 3.3.5 | MANDATORY | Functional test of O-DU Synchronized from ITU-T G.8275.1 profile PRTC/T-GM (LLS-C1/C2/C3/C4) | -| 3.3.6 | CONDITIONAL MANDATORY | Functional test of O-DU Synchronized from Embedded or Local non-PTP PRTC (LLS-C1/C2/C3/C4) | -| 3.3.7 | CONDITIONAL MANDATORY | Performance test of O-DU Synchronized from either Local or Remote PRTC using ITU-T G.8275.1 PTP Profile (LLS-C1/C2/C3/C4) | -| 3.3.8 | CONDITIONAL MANDATORY | Performance test of O-DU Synchronized from Embedded GNSS receiver (LLS-C1/C2/C3/C4) | - -Table 1.2.4-4 List of O-DU UC-Plane Test Scenarios and Status - -| Test Number | O-DU Test Requirement | Test Description | -|-----------------------------------|-----------------------|-----------------------------------------------------------------------------------| -| UC-Plane Measurements O-DU | | | -| 3.4.4.1.1 | MANDATORY | UC-Plane O-DU Scenario Class NR testing Generic (NRG) | -| 3.4.4.1.2 | MANDATORY | UC-Plane O-DU Scenario Class Base CAT-B O-RU | -| 3.4.4.2.1 | MANDATORY | UC-Plane O-DU Scenario Class Beamforming 3GPP – Predefined-beam Beamforming | -| 3.4.4.2.2 | CONDITIONAL MANDATORY | UC-Plane O-DU Scenario Class Beamforming 3GPP – Weight-based Beamforming | -| 3.4.4.2.3 | CONDITIONAL MANDATORY | UC-Plane O-DU Scenario Class Beamforming 3GPP – DMRS-BF-NEQ | -| 3.4.4.2.4 | CONDITIONAL MANDATORY | UC-Plane O-DU Scenario Class Beamforming 3GPP – DMRS-BF-EQ | -| 3.4.4.3.1 | MANDATORY | Static Format Fixed-Point (FP) Uncompressed | -| 3.4.4.3.2 | CONDITIONAL MANDATORY | UC-Plane O-DU Scenario Class Compression (CMP) Static Format Block Floating Point | -| 3.4.4.4.1 | MANDATORY | Delay Management On-time arrival | -| 3.4.4.4.2 | MANDATORY | Delay Management Early Arrival and Late Arrival | - -Table 1.2.4-5 List of FHM Test Scenarios and Status - -| Test Number | FHM Test Requirement | Test Description | -|-------------------------------------------------------|----------------------|-------------------------------------------------------------| -| FHM M-Plane Measurements | | | -| See Table 3.5.1.1-1 for FHM M-Plane Test Requirements | | | -| FHM UC-Plane Measurements | | | -| 3.5.1.2.1 | MANDATORY | UC-Plane FHM Scenario Class Base 3GPP DL Same Cell Scenario | -| 3.5.1.2.2 | MANDATORY | UC-Plane FHM Scenario Class Base 3GPP UL | - -## 1.3 References - -The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - -- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. -- For a specific reference, subsequent revisions do not apply. -- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document. - -- [1] ETSI TR 21.905, “Vocabulary for 3GPP Specifications” -- [2] O-RAN.WG4.TS.CUS.0-R004-v19.00, “Control, User and Synchronization Plane Specification” -- [3] O-RAN WG4 Management Plane Specification version 18.00 -- [4] O-RAN Management Plane Yang Models version 18.00 -- [5] Recommendation ITU-T G.8275.1 (Amendment 2) (03/2018): “Precision time protocol telecom profile for phase/time synchronization with full timing support from the network” -- [6] Recommendation ITU-T G.8275.2 (Amendment 2) (03/2018): Precision time protocol telecom profile for phase/time synchronization with partial timing support from the network” -- [7] Recommendation ITU-T G.8271.1 (Amendment 1) (03/2018): “Network limits for time synchronization in packet networks” -- [8] Recommendation ITU-T G.8271.2 (Amendment 1) (03/2018): “Network limits for time synchronization in packet networks with partial timing support from the network” -- [9] Recommendation ITU-T G.8273(03/2018): “Framework of phase and time clocks” -- [10] Recommendation ITU-T G.8261(08/2013): “Timing and synchronization aspects in packet networks” -- [11] eCPRI Specification v2.0 “Common Public Radio Interface: eCPRI Interface Specification”, May 2019 -- [12] ETSI TS 136.104, “Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception” -- [13] ETSI TS 138.104, “NR; Base Station (BS) radio transmission and reception” -- [14] ETSI TS 136.211, “Evolved Universal Terrestrial Radio Access (E-UTRA) Physical channels and modulation” -- [15] ETSI TS 138.211, “NR; Physical channels and modulation”, (Release 15), 3GPP - -- [16] ETSI TS 136.331, "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC)", Release 15, 3GPP -- [17] ETSI TS 138.331, "NR; Radio Resource Control (RRC); Protocol specification", (Release 15), 3GPP -- [18] ETSI TS 136.141, "Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) conformance testing", (Release 15), 3GPP -- [19] ETSI TS 138.141-1, "NR; Base Station (BS) conformance testing Part 1: Conducted conformance testing (Release 15)", 3GPP -- [20] ETSI TS 138.141-2, "NR; Base Station (BS) conformance testing Part 2: Radiated conformance testing (Release 15)", 3GPP -- [21] ETSI TS 123.401, "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access", 3GPP -- [22] ETSI TS 123.502, "Procedures for the 5G System (5GS)", (Release 15), 3GPP -- [23] ETSI TS 137.340, "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity", (Release 15), 3GPP -- [24] ETSI TS 138.214, "NR; Physical layer procedures for data", (Release 15), 3GPP -- [25] O-RAN WG4 Fronthaul Interoperability Test Specification (IOT) version 07.00 -- [26] Recommendation ITU-T G.827.2/Y.1368.2 (06/2023): "Timing characteristics of telecom boundary clocks and telecom time slave clocks" -- [27] O-RAN WG5 O1 Interface specification for O-DU -- [28] Recommendation ITU-T G.827.3 (10/2020): "Timing characteristics of telecom transparent clocks for use with full timing support from the network" -- [29] Recommendation ITU-T G.8262 (11/2018) "Timing characteristics of a synchronous equipment slave clock" -- [30] Recommendation ITU-T G.8262.1 (11/2022): "Timing characteristics of enhanced synchronous equipment slave clock" -- [31] Recommendation ITU-T G.8271 (03/2020): "Time and phase synchronization aspects of telecommunication networks" -- [32] IEEE Std 1588-2008, "Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems" -- [33] IEEE Std 802.1CM-2018, "Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems" -- [34] Recommendation ITU-T G.703 (04/2016): "Physical/electrical characteristics of hierarchical digital interfaces" -- [35] Recommendation ITU-T G.8272 (11/2018): "Timing characteristics of primary reference time clocks" -- [36] Recommendation ITU-T G.8264 (08/2017): "Distribution of timing information through packet networks" -- [37] Recommendation ITU-T G.803 (03/2000): "Architecture of transport networks based on the synchronous digital hierarchy (SDH)" -- [38] ISO/IEC 13239:2002 "High-level data link control (HDLC) procedures" -- [39] Antenna Interface Standards Group: "Control Interface for Antenna Line Devices", Standard No. AISG v2.0 -- [40] ETSI TS 137 462 V15.2.0 (2020-01), "Iuant interface: Signalling transport" - -## 1.4 Definitions - -For the purposes of the present document, the terms and definitions given in ETSI TR 21.905, “Vocabulary for 3GPP Specifications”[1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in [1] - -| | | -|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 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 | -| DL | DownLink: data flow towards the radiating antenna | -| DMRS-BF-EQ | Demodulation Reference Signal-based beamforming with equalization in the O-RU. | -| DMRS-BF-NEQ | Demodulation Reference Signal-based beamforming without equalization in the O-RU. | -| eNB | eNodeB (applies to LTE) | -| EVM | Error Vector Magnitude – see clause 6.5.2 Modulation quality in ETSI TS 138.104 | -| fm-pm | Fault Management, Performance Management role | -| gNB | gNodeB (applies to NR) | -| M-Plane | Management Plane: refers to non-real-time management operations between the O-DU and the O-RU | -| NETCONF | Network Configuration Protocol. For details see: RFC 6241, “Network Configuration Protocol (NETCONF)”, IETF, June 2011 | -| NSA | Non-Stand-Alone network mode that supports operation of SgNB attached to MeNB | -| O-CU | O-RAN Central Unit – a logical node hosting PDCP, RRC, SDAP and other control functions | -| O-DU | O-RAN Distributed Unit: a logical node hosting RLC/MAC/High-PHY layers based on a lower layer functional split. O-DU in addition hosts an M-Plane instance. | -| O-RU | O-RAN Radio Unit . O-RU in addition hosts M-Plane instance. | -| 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. | -| PDCCH | Physical Downlink Control Channel applies for LTE and NR air interface | -| PBCH | Physical Broadcast Channel applies for LTE and NR air interface | -| SA | Stand-Alone network mode that supports operation of gNB attached to a 5G Core Network | -| SCS | OFDM Sub Carrier Spacing | -| SSB | Synchronization Signal Block, in 5G PBCH and synchronization signal are packaged as a single block | -| subordinate | The term “subordinate” is used as a replacement for “slave” and is consistent with its use in CUS specification. When consensus emerges on how to eliminate the use of the term “slave” in the referenced standards organization, that approach will be applied to this specification | -| sudo | Super-User Do role | -| S-Plane | Synchronization Plane: Data flow for synchronization and timing information between nodes | - -| | | -|-------|----------------------------------------------------------------------------------------------------------------------------------------------------| -| SyncE | Synchronous Ethernet, is an ITU-T standard for computer networking that facilitates distribution of clock signals over the Ethernet physical layer | -| T-BC | Telecom Boundary Clock | -| TWAMP | Two-Way Active Measurement Protocol | -| UDP | User Datagram Protocol | -| UE | User Equipment terminology for a mobile device in LTE and NR | -| UL | UpLink: data flow from the UE towards the core network, that is from the O-RU towards in the O-DU in a Fronthaul context. | - -## 1.5 Abbreviations - -For the purposes of the present document, the following abbreviations 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 | -| CUSM-E | C-Plane, U-Plane, S-Plane and M-plane emulator – test equipment capable of sending and receiving required messages for all of these protocol planes when the Radio Unit is the device under test | -| DL | DownLink: data flow towards the radiating antenna | -| DUT | Device Under Test | -| eNB | e NodeB (applies to LTE) | -| gNB | g NodeB (applies to NR) | -| M-Plane | Management Plane: refers to non-real-time management operations between the O-DU and the O-RU | -| NETCONF | Network Configuration Protocol. For details see RFC 6241, “Network Configuration Protocol (NETCONF)”, IETF, June 2011 | -| O-DU | O-RAN Distributed Unit | -| O-RU | O-RAN Radio Unit | -| SMO | Service Management and Orchestration S-Plane Synchronization Plane: refers to traffic between the O-RU or O-DU to a synchronization controller which is generally an IEEE-1588 Grand Master (however, Grand Master functionality may be embedded in the O-DU). | -| TED | Test Equipment, O-DU – test equipment used to validate the O-DU | -| TER | Test Equipment, O-RU – test equipment used to validate the O-RU | -| UL | UpLink: data flow away from the radiating antenna | -| U-Plane | User Plane: refers to IQ sample data transferred between O-DU and O-RU | - -# 2 Test Configuration - -The conformance tests described in this document require test equipment with specific capabilities to support the testing of each protocol including the M-Plane, U-Plane, C-Plane and S-Plane. In addition, the tests define a specific connectivity between the test equipment and the device under test. This clause describes the test equipment requirements at a high level. Details are included in each test. - -As noted in the introduction in the Scope paragraphs, the initial focus of the M-Plane, C-Plane and U-Plane conformance tests is the O-RU. Version 2.00 and later include S-Plane tests for the O-DU in addition to the S-Plane tests for the O-RU. The initial test configuration description below is focused on the test equipment and configuration required to test the O-RU. O-DU test configuration descriptions for the S-Plane are covered in the S-Plane clause of this document. - -## 2.1 Test Configuration for O-RU as the Device Under Test - -When testing the O-RU, it is connected to test equipment called Test Equipment O-RU (TER). The TER is shown in Figure 2.1-1 below. TER surrounds the DUT and connects to both the fronthaul interface itself and the radio interface. At the radio interface, the TER collects RF signals from the DUT (downlink) and sends RF signals to the DUT receiver (uplink). Thus, the TER is made up of three main components, a CUSM-Plane Emulator (CUSM-E), a signal analyser and a signal generator as shown in Figure 2.1-1. The RF test interface is described in TS 136.141 for LTE, TS 138.141-1 for NR conducted, and TS 138.141-2 for non-conducted tests. The fronthaul interface is standard Ethernet as described above. In this case, the DL data flow is evaluated based on what is received by the signal analyser in the RF domain as radiated by the O-RU, and the UL data flow is evaluated based on what is emitted by the signal generator in the RF domain and received by the CUSM-E. - -When the O-RU is the Device Under Test (DUT), there is Test Equipment, RU (“TER”) that is used to connect to the DUT, run the test and evaluate the test result. - -The Test Equipment, RU (“TER”) provides everything needed to operate the test, including: - -- M-Plane commands to collect O-RU capabilities and configure the O-RU -- Synchronization via G.8275.1 (Mandatory for O-RU) -- C-Plane and U-Plane data flow to the O-RU -- Collection of RF energy to determine if the O-RU reacted correctly to the DL C-Plane and U-Plane data -- Radiation of RF energy to be received by the O-RU (note: this could be actually radiated, or conveyed through multiple RF cabled connections) -- Collection of O-RU UL fronthaul data flows and evaluating it for correctness based on the supplied RF energy to the O-RU antennas or RF connectors - -![Diagram of Test Setup, DUT = O-RU. The diagram shows a large box labeled 'Test Equipment, RU (TER)' containing three main components: 'CUSM-Plane Emulator' at the top, 'Signal Analyser' at the bottom left, and 'Signal Generator' at the bottom right. In the center, a box labeled 'DUT = O-RU' is connected to the CUSM-Plane Emulator via a 'fronthaul connection' (indicated by a double-headed arrow). The DUT is also connected to the Signal Analyser and Signal Generator via 'RF connection or antenna array(s)' (indicated by curved lines representing RF signals).](080a7af02bc47cf21ebfae4e0be39745_img.jpg) - -Diagram of Test Setup, DUT = O-RU. The diagram shows a large box labeled 'Test Equipment, RU (TER)' containing three main components: 'CUSM-Plane Emulator' at the top, 'Signal Analyser' at the bottom left, and 'Signal Generator' at the bottom right. In the center, a box labeled 'DUT = O-RU' is connected to the CUSM-Plane Emulator via a 'fronthaul connection' (indicated by a double-headed arrow). The DUT is also connected to the Signal Analyser and Signal Generator via 'RF connection or antenna array(s)' (indicated by curved lines representing RF signals). - -Figure 2.1-1 Test Setup, DUT = O-RU - -While M-Plane conformance tests do not generally require all the functions shown for a TER in Figure 2.1-1, the intent of this description is to show the general capabilities required for all tests on the O-RU as the DUT including U-Plane, C-Plane and S-Plane tests. If tests are restricted to only the M-Plane, the required test equipment configuration may also refer to Figure 2.1-2. - -When the O-RU is the Device Under Test (DUT), there is Test Equipment, RU (“TER”) that is used to connect to the DUT, run the test and evaluate the test result. - -The M-Plane Conformance Test Equipment, RU (“TER”) provides everything needed to operate the test, including: - -- M-Plane commands to collect O-RU capabilities, configure the O-RU and send all commands needed for the testing of M-plane -- Supply power to the O-RU and measure power consumption. -- Synchronization via G.8275.1 and C-Plane and U-Plane generation -- Collection of RF energy and analysis -- RS-485 sniffer / injector is required to validate the ALD communications protocol and operation of the O-RU for ALD Communications Test. (This test is CONDITIONAL MANDATORY : only needed if the DUT supports ALD port) -- Supplementary circuitry is required to force a change of logical state of input lines and confirm voltage of an output lines for External Input / Output Port Test. (This test is CONDITIONAL MANDATORY : only needed if the DUT supports External Input / Output Port) - -![Figure 2.1-2 M-Plane Test Setup, DUT = O-RU. This block diagram shows the M-Plane Conformance Test Equipment (RU (TER)) connected to the DUT (O-RU). The TER includes a DC or AC Power Supply, Power Meter, Power Supply Unit, and CUSM-Plane Emulator. The O-RU has a Conditional Mandatory External I/O and ALD port, and an RF Connection or Antenna Array(s). The TER also includes Supplementary circuitry, RS-485 Sniffer/injector, and Signal Analyzer connected to the O-RU's External I/O and ALD port.](b44f89b176c971c7dd264c07bfef2c2a_img.jpg) - -Figure 2.1-2 M-Plane Test Setup, DUT = O-RU. This block diagram shows the M-Plane Conformance Test Equipment (RU (TER)) connected to the DUT (O-RU). The TER includes a DC or AC Power Supply, Power Meter, Power Supply Unit, and CUSM-Plane Emulator. The O-RU has a Conditional Mandatory External I/O and ALD port, and an RF Connection or Antenna Array(s). The TER also includes Supplementary circuitry, RS-485 Sniffer/injector, and Signal Analyzer connected to the O-RU's External I/O and ALD port. - -Figure 2.1-2 M-Plane Test Setup, DUT = O-RU - -## 2.2 Test Configuration for O-DU as the Device Under Test - -When testing the open fronthaul interface of the O-DU, it is connected to test equipment called Test Equipment O-DU (TED). The TED is shown below with the following two cases: - -1. Stand-alone O-DU as the DUT – In this case the TED wraps around the O-DU DUT via its F1 interface towards the Core + O-CU Emulator (and additionally X2 signalling emulator in NSA), the front haul interface towards the O-RU+UE Emulator, and the O1 or EMS interface towards the test configuration entity. -2. Combined O-CU+O-DU (from the same vendor) as the DUT - In this case the TED wraps around the combined O-CU + O-DU DUT via the NG (SA) or S1 and X2 (NSA) interfaces towards the Core Emulator (additionally the X2 signalling emulator in NSA), the front haul interface towards the O-RU+UE Emulator, and the O1 or EMS interface towards the test configuration entity. - -![Two block diagrams illustrating test configurations for O-DU. The left diagram, titled 'O-DU DUT', shows the Test Equipment-DU (TED) connected to the O-DU DUT via F1, O1/EMS, and Fronthaul connections. The TED includes a Test Config, Core + O-CU Emulator, X2 Emulator (NSA), and O-RU+UE Emulator. The right diagram, titled 'Combined O-CU+O-DU DUT', shows the TED connected to the combined O-CU + O-DU DUT via NG(SA) or S1 (NSA), X2 (NSA), O1/EMS, and Fronthaul connections. The TED includes a Test Config, Core Emulator, X2 Emulator (NSA), and O-RU+UE Emulator.](30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg) - -Two block diagrams illustrating test configurations for O-DU. The left diagram, titled 'O-DU DUT', shows the Test Equipment-DU (TED) connected to the O-DU DUT via F1, O1/EMS, and Fronthaul connections. The TED includes a Test Config, Core + O-CU Emulator, X2 Emulator (NSA), and O-RU+UE Emulator. The right diagram, titled 'Combined O-CU+O-DU DUT', shows the TED connected to the combined O-CU + O-DU DUT via NG(SA) or S1 (NSA), X2 (NSA), O1/EMS, and Fronthaul connections. The TED includes a Test Config, Core Emulator, X2 Emulator (NSA), and O-RU+UE Emulator. - -**Figure 2.2- 1 Test Setup, DUT = O-DU** - -It is important to note that the tests assume production grade DUTs which should not be placed into any special test modes nor require any special test ports. At the front haul interface, the O-RU+UE Emulator is expected to perform the following functions: - -1. Exchange of front haul data as required to exercise the feature under test. This entails emulating the necessary front haul signals as seen by the O-DU DUT as if it were connected to an actual O-RU with an actual UE (or multiple UEs in the case of beamforming tests) performing an actual connection with the base station. -2. Detailed observation and analysis of the front haul data stream of the O-DU DUT in order to ascertain compliance to the specifications. - -Note that in addition to the C-, U-, and M-plane signals in the fronthaul, this also includes the necessary S-plane for synchronizing the O-DU DUT with the O-RU+UE Emulator. - -Since the O-DU is meant to support various classes of O-RU with different feature sets, e.g. CAT-A or CAT-B, FR1 or FR2, different beamforming methods to multiple UEs, different compression schemes, etc., it is important that the O-RU+UE Emulator has the flexibility to effectively emulate the various scenarios in a robust and repeatable manner in order to test the various features. Similarly, the Core+O-CU emulator (with the addition of an X2 signalling emulator for NSA mode) shall likewise emulate and observe the appropriate signals at the F1 or NG (or S1 and X2 for NSA) interfaces to effectively wrap-around the O-DU or O-CU+O-DU DUT. Note that the Core, O-CU, eNB, O-RU, and UE emulator functionalities required in the TED are those that place the O-DU or O-CU+O-DU DUT into a state that allows it to perform an actual connection(s) to a UE(s) to exercise the various open fronthaul features under test, and are thus not required to fully emulate the full functionality of their commercial equivalents. Conversely, this specification does not preclude the use of the commercial equivalent elements instead of emulators, but must support a level of configurability and repeatability to ensure that the required features in the O-DU front-haul are effectively and repeatably exercised. With use of either node emulators or commercial equivalents, the required test outcomes and reports must be effectively and repeatably reproduced. - -In order to cover the various potential optional features, Section Types, and section extensions for the O-DU DUT, the TED should use the O1 (if available) or EMS interface to provision the O-DU or O-CU+O-DU DUT in order to place it into the appropriate modes to exercise the specific features to test, which is then coordinated with the O-RU+UE Emulator in order to elicit the appropriate front-haul interface behaviour. - -While M-Plane conformance tests do not generally require all the functions shown for a TED in Figure 2.2-1, the intent of this description is to show the general capabilities required for all tests on the O-DU as the DUT including U-Plane, C-Plane and S-Plane tests. If tests are restricted to only the M-Plane, the required test equipment configuration may be simplified. - -## 2.3 Test Configuration for Shared Cell Configurations - -There are two Shared Cell configurations defined as Shared Cell modes in [2]. These configurations are FHM mode and Cascade mode. FHM mode includes a device called the Fronthaul Multiplexor (FHM). The Cascade mode does not include the FHM. - -### 2.3.1 Test Configuration for FHM as the Device Under Test - -When testing the Fronthaul Multiplexor (FHM), it is connected to test equipment called Test Equipment Fronthaul Multiplexor (TEM). The TEM is shown in Figure 2.3-1 below. TEM surrounds the DUT and connects to both the northbound port and southbound ports of FHM. - -At the northbound interface, TEM acts as an O-DU-Emulator, connecting to the DUT through the fronthaul interface, with necessary CUSM-Plane capabilities to conduct the test cases described in clause 3.5 of the present specification. At the southbound interface, TEM acts as O-RU+UE Emulator, emulating multiple O-RUs. In the present specification, only the same cell scenario is considered. The TEM also supports multiple UEs attached to each of the emulated O-RUs. TEM connects to multiple physical ports (a minimum of 3) of the DUT. Each of these physical ports is an eCPRI Ethernet link with necessary CUSM-Plane capabilities to conduct the test cases described in chapter 3.5 of this document. - -![Figure 2.3-1 Test Setup, DUT = FHM. The diagram shows a 'Test equipment FHM (TEM)' box containing an 'O-DU Emulator' and an 'O-RU Emulator + UE Emulator'. The 'O-DU Emulator' is connected to an 'FHM' box. The 'FHM' box is connected to the 'O-RU Emulator + UE Emulator' box via multiple dashed lines, representing multiple physical ports.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) - -``` - -graph TD - subgraph TEM [Test equipment FHM (TEM)] - ODU[O-DU Emulator] - ORU[O-RU Emulator + UE Emulator] - end - ODU --- FHM[FHM] - FHM -.-> ORU - style TEM fill:none,stroke:none - style FHM fill:none,stroke:none - -``` - -Figure 2.3-1 Test Setup, DUT = FHM. The diagram shows a 'Test equipment FHM (TEM)' box containing an 'O-DU Emulator' and an 'O-RU Emulator + UE Emulator'. The 'O-DU Emulator' is connected to an 'FHM' box. The 'FHM' box is connected to the 'O-RU Emulator + UE Emulator' box via multiple dashed lines, representing multiple physical ports. - -Figure 2.3-1 Test Setup, DUT = FHM - -# 3 Conformance Measurements - -## 3.1 M-Plane Measurements for O-RU - -The O-RAN Fronthaul management plane (M-Plane) protocol conformance tests are described in this clause. The M-Plane is based on the NETCONF network element management protocol and YANG data modelling language. The NETCONF protocol uses a client and server model for all exchanges of information and execution of RPCs. Every NETCONF transaction is a 2-way exchange involving the client and the server. An O-DU supports a NETCONF client. An O-RU supports a NETCONF server. A FHM supports a NETCONF server. Any M-Plane conformance test will require both a NETCONF client and a NETCONF server. Because many YANG models are shared by all applicable fronthaul devices including the O-DU, O-RU and FHM, most M-Plane conformance tests apply to all of these fronthaul devices. However, because some YANG models are applicable only with an O-RU as a NETCONF server and some applicable only to a FHM NETCONF server, FHM M-Plane test cases are described within the FHM clauses (clause 3.5.1.1 FHM M-Plane Tests) of the present document. - -The following clauses describe Conformance Tests for the M-Plane for an O-RU as the device under test. Table 1.2.4-1 lists all M-Plane test cases applicable to an O-RU for conformance testing. - -### 3.1.1 Transport and Handshake Test Scenarios - -#### 3.1.1.1 Transport and Handshake in IPv4/SSH Environment (positive case) - -##### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY for an O-RU that declares support for IPv4. - -This scenario validates that the O-RU properly executes the session establishment procedure with VLANs and a DHCPv4 server. This test is applicable to IPv4 environments. - -This scenario corresponds to the following clause in [3]: - -- 6.2 Management Plane Transport aspects -- 6.3 NETCONF Call Home to O-RU Controller(s) - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The O-RU is powered on and has an ethernet connection to the DHCP-server -2. The configured DHCPv4 server is reachable by the O-RU NETCONF Server through the VLAN configured for M-Plane. -3. Default SSH credentials (sudo) are used by both the O-RU NETCONF Server and the TER NETCONF Client -4. IP details for test purposes are pre-defined and fixed (applies to the DHCP server). - -###### b. Procedure - -1. The O-RU NETCONF Server can be preconfigured with no VLAN (known in 802.1Q as native ethernet or an untagged VLAN), a VLAN ID or may optionally perform a VLAN scan by issuing DHCP Discover trying to reach the DHCP Server -2. The O-RU NETCONF Server continues the DHCPv4 procedure on the preconfigured VLAN or first VLAN where the Offer from DHCP Server / Relay is received if the scan method is used -3. O-RU NETCONF Server retrieves IP details and the IP address of the controlling TER NETCONF Client from the DHCP Server. - -NOTE: RFC 2131 is followed for DHCPv4 - -4. The O-RU NETCONF Server establishes TCP connection and performs a Call Home procedure towards the NETCONF Client using the IP details obtained in step 3 -5. The TER NETCONF Client establishes a SSH session with the O-RU NETCONF Server. Proper credentials are used. -6. The O-RU NETCONF Server accepts the SSH session establishment from the TER NETCONF Client -7. The TER NETCONF Client and O-RU NETCONF Server exchange capabilities through NETCONF messages. The following is an abbreviated example of the capabilities exchange. A typical capabilities exchange will have far more parameters included. - -NOTE: RFC 6241 is followed for NETCONF communication. - -``` -Server (O-RU) initiates Hello message . -``` - -``` - - - - urn:ietf:params:netconf:base:1.0 - urn:ietf:params:netconf:base:1.1 - urn:ietf:params:netconf:capability:writable- -running:1.0 - - urn:ietf:params:netconf:capability:notification:1.0 - - urn:ietf:params:netconf:capability:interleave:1.0 - http://org/openroadm/user-mgmt?module=org-openroadm-user-mgmt&revision=2017-12-15 - ..... - - 1 - - -Client (DU) responds with Hello message ... - - - urn:ietf:params:netconf:base:1.0 - urn:ietf:params:netconf:base:1.1 - - - -``` - -##### D. Test Requirement (expected result) - -Test scenario step 7 is performed successfully. - -#### 3.1.1.2 Transport and Handshake in IPv4/SSH Environment (negative case) - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for O-RUTests. - -This scenario validates that the O-RU properly executes the session establishment procedure with VLANs and a DHCPv4 server. This test is applicable to IPv4 environments. Two negative flows are included in this test: - -- The TER NETCONF Client does not trigger a SSH session establishment in reaction to Call Home initiated by THE O-RU NETCONF Server. -- The TER NETCONF Client uses improper credentials when trying to establish a SSH session with the O-RU NETCONF Server. - -This scenario corresponds to the following clause in [3]: - -- 6.2 Management Plane Transport aspects -- 6.3 NETCONF Call Home to O-RU Controller(s) - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -- O-RU is powered on and has an ethernet connection to the DHCP-server -- Configured DHCPv4 server is reachable for O-RU NETCONF Server through the VLAN configured for M-Plane. -- Default SSH credentials (sudo) are used by both O-RU NETCONF Server and NETCONF Client -- IP details for test purposes are pre-defined and fixed (applies to DHCP server). - -###### b. Procedure - -###### i. Flow 1 - -- The O-RU NETCONF Server can be preconfigured with no VLAN (known in 802.1Q as native ethernet or an untagged VLAN), a VLAN ID or may optionally perform a VLAN scan by issuing a DHCP Discover trying to reach DHCP Server -- The O-RU NETCONF Server continues the DHCPv4 procedure on the preconfigured VLAN or first VLAN where the Offer from the DHCP Server / Relay is received if the scan method is used -- The O-RU NETCONF Server retrieves IP details and the IP address of controlling TER NETCONF Client from the DHCP Server. - -NOTE: RFC 2131 is followed for DHCPv4. - -- The O-RU NETCONF Server establishes TCP connection and performs Call Home procedure with the TER NETCONF Client using IP details obtained in step 3 -- The TER NETCONF Client does not initiate the SSH session establishment procedure. -- The O-RU NETCONF Server periodically repeats the Call Home towards TER NETCONF Client. - -###### ii. Flow 2 - -- The O-RU NETCONF Server can be preconfigured with a VLAN ID or may optionally perform a VLAN scan by issuing a DHCP Discover trying to reach the DHCP Server -- The O-RU NETCONF Server continues the DHCPv4 procedure on the preconfigured VLAN or first VLAN where the Offer from the DHCP Server / Relay is received if the scan method is used -- The O-RU NETCONF Server retrieves IP details and the IP address of the controlling TER NETCONF Client from DHCP Server. - -NOTE: RFC 2131 is followed for DHCPv4. - -- The O-RU NETCONF Server establishes a TCP connection and performs the Call Home procedure with the TER NETCONF Client using IP details obtained in step 3 -- The TER NETCONF Client initiates the SSH session establishment procedure with improper credentials. -- Due to the incorrect SSH credentials, the O-RU NETCONF Server rejects the SSH session establishment from the TER NETCONF Client. -- The O-RU NETCONF Server starts periodic Call Home procedure towards the TER NETCONF Client. - -##### D. Test Requirement (expected result) - -- Flow 1: Scenario reaches step 6. The O-RU NETCONF Server falls into Call Home procedure loop. -- Flow 2: Scenario reaches step 7. The O-RU NETCONF Server falls into Call Home procedure loop. - -#### 3.1.1.3 Transport and Handshake in IPv6/SSH Environment (positive case) - -The test description, applicability, entrance criteria, methodology and requirements are the same as in clause 3.1.1.1, Transport and Handshake in IPv4/SSH Environment (positive case). The only difference is that this test is applicable to IPv6 environments including DHCPv6. This test is CONDITIONAL MANDATORY. - -#### 3.1.1.4 Transport and Handshake in IPv6/SSH Environment (negative case) - -The test description, applicability, entrance criteria, methodology and requirements are the same as in clause 3.1.1.2, Transport and Handshake in IPv4/SSH Environment (negative case). The only difference is that this test is applicable to IPv6 environments including DHCPv6. This test is CONDITIONAL MANDATORY. - -#### 3.1.1.5 Transport and Handshake in IPv4/TLS Environment (positive case) - -The test description, applicability, entrance criteria, methodology and requirements are the same as in clause 3.1.1.1, Transport and Handshake in IPv4/SSH Environment (positive case). The only difference is that this test is applicable to IPv4 and TLS environments including DHCPv4. This test is CONDITIONAL MANDATORY. - -#### 3.1.1.6 Transport and Handshake in IPv4/TLS Environment (negative case) - -The test description, applicability, entrance criteria, methodology and requirements are the same as in clause 3.1.1.2, Transport and Handshake in IPv4/SSH Environment (negative case). The only difference is that this test is applicable to IPv4 and TLS environments including DHCPv4. This test is CONDITIONAL MANDATORY. - -#### 3.1.1.7 Transport and Handshake in IPv6/TLS Environment (positive case) - -The test description, applicability, entrance criteria, methodology and requirements are the same as in clause 3.1.1.1, Transport and Handshake in IPv4/SSH Environment (positive case). The only difference is that this test is applicable to IPv6 and TLS environments including DHCPv6. This test is CONDITIONAL MANDATORY. - -#### 3.1.1.8 Transport and Handshake in IPv6/TLS Environment (negative case) - -The test description, applicability, entrance criteria, methodology and requirements are the same as in clause 3.1.1.2, Transport and Handshake in IPv4/SSH Environment (negative case). The only difference is that this test is applicable to IPv6 and TLS environments including DHCPv6. This test is CONDITIONAL MANDATORY. - -### 3.1.2 Subscription to Notification - -#### 3.1.2.1 Subscription to NETCONF Event Stream - -##### A. Test Description and Applicability - -This test is MANDATORY for O-RU. - -This test validates that the O-RU properly handles a NETCONF subscription to the default “NETCONF” event stream. - -This scenario corresponds to the following clause in [3]: - -- 9.1.7 Notification framework. - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed. - -###### **b. Procedure** - -1. The TER NETCONF Client triggers the subscription: - -``` - - - NETCONF - - -``` - -to the O-RU NETCONF Server to subscribe to notifications related to the supervision process. - -NOTE: NETCONF is intentional, meaning that the TER NETCONF Client subscribes to all notifications that the O-RU NETCONF Server can generate (including alarm notifications). - -2. The O-RU NETCONF Server responds with - -``` - - - -``` - -to the TER NETCONF Client. - -NOTE: RFC 6241 is followed for NETCONF communication. - -##### **D. Test Requirement (expected result)** - -Test scenario step 2 is performed successfully. - -### 3.1.3 M-Plane Connection Supervision - -#### 3.1.3.1 M-Plane connection supervision (positive case) - -##### **A. Test Description and Applicability** - -This scenario is MANDATORY for O-RU Tests. - -This test validates that the O-RU manages the connection supervision process correctly. - -This scenario corresponds to the following clause in [3]: - -- 6.7 Monitoring NETCONF connectivity - -##### **B. Test Entrance Criteria** - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU - -##### **C. Test Methodology** - -###### **a. Initial Conditions** - -1. The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed. -2. The test procedure described in 3.1.2.1 is successfully completed. - -###### **b. Procedure** - -1. The O-RU NETCONF Server notification timer expires -2. The O-RU NETCONF Server sends a supervision notification message to the TER NETCONF Client. -Note that the time in this example is shown generically and will be the current time during this test. - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - -``` - -NOTE: For the O-RU that supports feature SUPERVISION-WITH-SESSION-ID, these supervision-notification messages indicate the NETCONF session-id associated with the subscription to the event notification, as specified in clause 6.7 of [3]. - -3. The TER NETCONF Client responds with - -``` - - - 60 - 10 - - -``` - -to the O-RU NETCONF Server. - -4. The O-RU NETCONF Server sends a reply to the TER NETCONF Client - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - -``` - -NOTE: The TER NETCONF Client can change the value of the supervision timer in the supervision watchdog reset message. The O-RU NETCONF server adjusts the timer accordingly if this optional change of the value of the supervision timer is performed. - -5. The O-RU NETCONF Server sends a supervision notification towards the TER NETCONF Client with respect to time-date sent in rpc-reply in step 4. -6. Steps 1 to 5 are looped for a total of 30 iterations including the first pass through steps 1 to 5. - -NOTE: RFC 6241 is followed for NETCONF communication. - -##### **D. Test Requirement (expected result)** - -Test scenario step 6 is performed successfully in all iterations. - -#### 3.1.3.2 M-Plane Connection Supervision (negative case) - -##### A. Test Description and Applicability - -This scenario is MANDATORY for both O-RU Tests. - -This test validates that the O-RU manages the connection supervision process correctly. - -This scenario corresponds to the following clause in [3]: - -- 6.7 Monitoring NETCONF connectivity - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed. -2. The test procedure described in 3.1.2.1 is successfully completed. - -###### b. Procedure - -1. The O-RU NETCONF Server notification timer expires -2. The O-RU NETCONF Server sends a supervision notification message to the TER NETCONF Client -3. The TER NETCONF Client responds with - - - -to the O-RU NETCONF Server. - -4. The O-RU NETCONF Server sends a reply to the TER NETCONF Client - -date-time - -Note that the TER NETCONF Client can change the value of the supervision timer in the supervision watchdog reset message. The O-RU NETCONF server must adjust the timer accordingly if this optional test is performed. - -5. The O-RU NETCONF Server sends a supervision notification towards the TER NETCONF Client with respect to time-date sent in rpc-reply in step 4. -6. The TER NETCONF Client does not issue to the O-RU NETCONF Server and causes the supervision timer to expire on the O-RU. -7. The O-RU NETCONF Server enters the Supervision failure scenario. For details, please see O-RAN M-Plane Specification [3], chapter 14.1. - -##### D. Test Requirement (expected result) - -Test scenario step 7 is performed successfully. - -### 3.1.4 Retrieval of O-RU's information elements - -#### 3.1.4.1 Retrieval without Filter Applied - -##### A. Test Description and Applicability - -This scenario is MANDATORY for O-RU Tests. - -This scenario validates that the O-RU NETCONF Server properly executes a general get command. - -This scenario corresponds to the following clause in [3]: - -- 9.1.2 Retrieve state - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed. - -###### b. Procedure - -1. The TER NETCONF Client triggers towards the O-RU NETCONF Server. -2. The O-RU NETCONF Server responds with where contains all information elements that the O-RU NETCONF Server is able to expose - -##### D. Test Requirement (expected result) - -Test step 2 is performed successfully. - -#### 3.1.4.2 Retrieval with filter applied - -##### A. Test Description and Applicability - -This scenario is MANDATORY for O-RU test. - -This scenario validates that the O-RU NETCONF Server properly executes a get command with a filter applied. - -This scenario corresponds to the following clause in [3]: - -- 6.6 NETCONF capability discovery -- 9.1.2 Retrieve state - -##### B. Minimum Requirements - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) respectively is successfully completed. - -###### b. Procedure - -1. The TER NETCONF Client triggers towards NETCONF Server. The argument contains a regular expression that the O-RU NETCONF Server shall apply as a filter. For example, a filter that filters all low-level-rx-endpoints: - -``` - - - - - - - - - - - - -``` - -2. The O-RU NETCONF Server responds with where contains details for objects as conforming to the (as per the above example filter: all low-level-rx-endpoints) - -##### **D. Test Requirement (expected result)** - -Test step 2 is performed successfully. - -### 3.1.5 Fault Management - -#### 3.1.5.1 O-RU Alarm Notification Generation - -##### **A. Test Description and Applicability** - -This scenario is MANDATORY for O-RU tests and OPTIONAL for O-DU tests. - -This scenario validates that the O-RU NETCONF Server properly sends and alarm notification. - -This scenario corresponds to the following clause in [3]: - -- 11.2 Alarm Notification - -##### **B. Test Entrance Criteria** - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### **C. Test Methodology** - -###### **a. Initial Conditions** - -- i. The test procedure described in clause 3.1.2.1 for Subscription to Notifications is successfully completed. -- ii. Testing with S-plane: Ensure that the alarm for fault id 17 is not already raised in the system. -- iii. Testing without S-plane: Ensure that the alarm for fault id which is triggered using a maintenance tool or debug command is not already raised in system. - -###### **b. Procedure** - -###### **i) Testing with S-Plane:** - -1. The TER NETCONF Client periodically tests O-RU's sync-status until the LOCKED state is reached. - -``` - - - - - - - -``` - -2. Disable the Sync signal on the TER. -3. After a while (time depends on implementation) the O-RU NETCONF SERVER sends a notification for an alarm related to synchronization failure, e.g. alarm 17: No external sync source" or another vendor specific alarm. The format of alarm notification follows RFC5277. Note that the time in this example is shown generically and will be the current time during this test. - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - 17 - sync - - syncE - - MAJOR - false - No external sync source - YYYY-MM-DDTHH:MM:SS.FZ - - -``` - -###### ii) Testing without S-Plane: - -NOTE: Since this validation is for O-RU NETCONF Server properly sending the alarm notification, this is an alternative test method to testing with S-Plane. - -1. Raise alarm notification using vendor specific maintenance tool or debug command. The debug command will generate a pseudo fault in the O-RU. The O-RU will add a new alarm caused by detecting the pseudo fault to the active alarm list and send the alarm notification. - -The O-RU NETCONF SERVER sends a notification for alarm. The format of alarm notification follows RFC5277. Note that the time in this example is shown generically and will be the current time during this test. The details related to fault in this example notification message is shown generically and will be the details for alarm which is triggered using maintenance tool or debug command. - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - 2 - Module - - HW - - CRITICAL -``` - -``` - - false - Unit dangerously overheating - YYYY-MM-DDTHH:MM:SS.FZ - - - -``` - -##### D. Test Requirement (expected result) - -1. With S-plane: Test step 3 is performed successfully. -2. Without S-plane: Test step 2 is performed successfully. - -#### 3.1.5.2 Retrieval of Active Alarm List - -##### A. Test Description and Applicability - -This scenario is MANDATORY for O-RU tests and OPTIONAL for O-DU tests. - -This scenario validates that the O-RU NETCONF Server can send an active alarms list to the TER NETCONF Client. - -This scenario corresponds to the following clause in [3]: - -- 11. Fault Management - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -The test procedure described in clause 3.1.2.1 for Subscription to Notifications is successfully completed. - -###### b. Procedure - -1. The TER NETCONF Client sends the O-RU NETCONF Server a command to get the active-alarm-list. - -``` - - - - - - - - -``` - -2. The O-RU NETCONF Server responds with where contains at least the same alarm as reported in measurement in clause 3.1.5.1 for the procedure with S-Plane or without S-Plane. - -``` - - - - - - 17 - sync - - syncE - - -``` - -``` - - MAJOR - false - No external sync source - YYYY-MM-DDTHH:MM:SS.FZ - - - - - -``` - -NOTE: There can be more than one Active Alarm in the reply from O-RU. The details related to fault in this example notification message is shown generically and will be the details for alarm which is triggered using maintenance tool or debug command. - -##### D. Test Requirement (expected result) - -Test step 2 is performed successfully. - -### 3.1.6 O-RU Software Update - -#### 3.1.6.1 O-RU Software Update and Install (positive case) - -##### A. Test Description and Applicability - -This scenario is MANDATORY for O-RU Tests. - -This test validates that the O-RU can successfully perform a software download and software install procedure. - -This scenario corresponds to the following clause in [3]: - -- 8. Software Management - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedures described in clause 3.1.2.1 and clause 3.1.4.1 is successfully completed. -2. A correct and internally consistent SW package is available for test purposes. -3. The O-RU provides at least one slot available for SW update procedure. The status of this slot is assumed to be {active = False, running = False, access = READ-WRITE} -4. A sFTP/FTPES server is available with an account for the SW update procedure on the TER, using FTPES if the O-RU controller is using NETCONF/TLS to configure the O-RU. - -###### b. Procedure - -1. The TER NETCONF Client triggers . The O-RU NETCONF Server responds with with STARTED - -``` - - - - - sftp://oranuser@192.168.3.13:22/software.zip - - - -``` - -``` - - STARTED - -``` - -2. The O-RU NETCONF Server performs a software download procedure. When the download is completed, the O-RU NETCONF Server sends with status COMPLETED to TER NETCONF Client - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - sftp://oranuser@192.168.3.13:22/software.zip - COMPLETED - - -``` - -3. The TER NETCONF Client triggers informing the O-RU NETCONF Server about the desired slot for installation. This slot must have the attributes active = FALSE, running = FALSE, access = READ-WRITE. The O-RU NETCONF Server responds with with status STARTED. - -``` - - - "SLOT0" - "testpkg" - - -``` - -``` - - STARTED - -``` - -4. The O-RU NETCONF Server examines the downloaded software. The files are error free by design in this test. The O-RU NETCONF Server installs the new software files to the desired slot. -5. The O-RU NETCONF Server sends to the TER NETCONF Client. Field contains the value COMPLETED to indicate the successful installation of software to the desired slot. - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - "SLOT0" - COMPLETED - - -``` - -##### D. Test Requirement (expected result) - -1. Test step 5 completed with notification that indicates successful installation of the downloaded software. - -2. Status of SW slot used for SW installation is set to VALID. Other parameters of software slot shall not be changed. - -#### 3.1.6.2 O-RU Software Update (negative case) - -##### A. Test Description and Applicability - -This scenario is MANDATORY for O-RU tests. - -This scenario corresponds the following chapters in [3]: - -- 8. Software Management - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.2.1 and 3.1.4.1 is successfully completed. -2. A modified software package is available for test purposes (proper content of manifest.xml, but fake/invalid content of software files) -3. The O-RU provides at least one slot available for the software update procedure (status != INVALID, active = False, running = False, access = READ-WRITE) -4. A sFTP/FTPES server is available with an account dedicated for the software update procedure, using FTPES if the O-RU controller is using NETCONF/TLS to configure the O-RU. - -###### b. Procedure - -Based on how the software package is modified, the failure can be related to software-install or software-download, and is implementation dependent. Flow 1 is given for a failure related to software-download and Flow 2 is given for a failure related to software-install. - -###### i. Flow 1 - -1. The TER NETCONF Client triggers . The O-RU NETCONF Server responds with - -``` - - - - sftp://oranuser@192.168.3.13:22/software.zip - - - - - STARTED - -``` - -2. The O-RU NETCONF Server determines that the software file is invalid and sends to the TER NETCONF Client The field is correctly updated with AUTHENTICATION\_ERROR or PROTOCOL\_ERROR or FILE\_NOT\_FOUND or APPLICATION\_ERROR or TIMEOUT. - -``` - - YYYY-MM-DDTHH:MM:SS.FZ -``` - -``` - - - "SLOT0" - APPLICATION_ERROR - - - -``` - -###### ii. Flow 2 - -1. The TER NETCONF Client triggers . The O-RU NETCONF Server responds with - -``` - - - - - sftp://oranuser@192.168.3.13:22/software.zip - - - - - STARTED - - -``` - -2. The O-RU NETCONF Server performs the software download procedure. When the download is complete, the O-RU NETCONF Server sends with status COMPLETED to the TER NETCONF Client - -``` - - - YYYY-MM-DDTHH:MM:SS.FZ - - sftp://oranuser@192.168.3.13:22/software.zip - COMPLETED - - - -``` - -3. The TER NETCONF Client triggers informing the O-RU NETCONF Server about desired slot the software shall be installed to. The O-RU NETCONF Server respond with with status STARTED. - -``` - - - - "SLOT0" - "testpkg" - - - - - STARTED - -``` - -``` - -``` - -4. The O-RU NETCONF Server determines that the software file is invalid and sends to the TER NETCONF Client. The Field is correctly updated with one of the following statuses: FILE\_ERROR or INTEGRITY\_ERROR or APPLICATION\_ERROR. - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - "SLOT0" - FILE_ERROR - - -``` - -##### D. Test Requirement (expected result) - -Flow 1: - -The test scenario reaches step 2. The O-RU NETCONF Server indicates failure with the Software Download procedure. Parameters of the Software Slot, with the exception of the status, shall not be changed. - -Flow 2: - -The test scenario reaches step 4. The O-RU NETCONF Server indicates failure with the Install procedure. The Status of the Software Slot used for software installation is set to its appropriate status. Parameters of the Software Slot, with the exception of the status, shall not be changed. - -### 3.1.7 O-RU Software Activation - -#### 3.1.7.1 Software Activation without Reset - -##### A. Test Description and Applicability - -This scenario is MANDATORY for O-RU Tests. - -This test validates that the O-RU can successfully activate software in a specific slot on the O-RU. - -This scenario corresponds to the following clause in [3]: - -- 8. Software Management - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.6.1 is successfully completed. - -###### b. Procedure - -1. The TER NETCONF Client triggers towards the O-RU NETCONF Server. The name of a slot containing a valid software installation to be activated is provided as a parameter in the RPC. - -``` - - - "SLOT0" - - -``` - -2. The O-RU NETCONF Server responds with . The parameter "status" is set to STARTED. - -``` - - STARTED - -``` - -3. The O-RU NETCONF Server performs a software activation procedure. When the procedure is completed, the O-RU NETCONF Server sends with a status COMPLETED and the slot-name in the activation event corresponds to the slot-name used in the software-activate RPC to the TER NETCONF Client. - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - "SLOT0" - COMPLETED - - -``` - -##### D. Test Requirement (expected result) - -1. In step 3 of this test, the status of the software slot used for software activation is set to VALID and the parameter "active" is set to "True". The parameter "running" remains "False". -2. Status of the software slot containing the software still used by device remains VALID, the parameter "active" is set to False. The parameter "running" is True. - -NOTE: O-RU reset is required to complete SW activation sequence - meaning: to force device to start with the software just activated. - -#### 3.1.7.2 Supplemental Reset after Software Activation - -##### A. Test Description and Applicability - -This scenario is MANDATORY for O-RU tests. - -This test validates that the O-RU can successfully start up with activated software. - -This scenario corresponds to the following clause in [3]: - -- 8. Software Management - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.7.1 is successfully completed. - -###### b. Procedure - -1. The TER NETCONF Client sends `` to the O-RU NETCONF Server. -` ` -2. The O-RU NETCONF Server responds with `rpc-reply`. -`` -3. The O-RU restarts with a new software version running matching the version activated in test 3.1.7.1. - -##### D. Test Requirement (expected result) - -1. In step 3 of this test, the status of the software slot used for software activation remains VALID (it is unchanged) and the parameter "active" remains "True". The parameter "running" is set to True. -2. Status of the software slot containing the previous version of software used by device remains VALID, the parameter "active" remains False. The parameter "running" is set to False. - -### 3.1.8 Access Control - -#### 3.1.8.1 Sudo on Hybrid M-plane Architecture (positive case) - -##### A. Test Description and Applicability - -This scenario is MANDATORY for an O-RU . - -This test validates that user management model can be used to add users to the O-RU - -This scenario corresponds to the following clauses in [3]: - -- 6.4 NETCONF Connection Establishment -- 6.5 NETCONF Access Control - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed. - -###### b. Procedure - -1. The TER NETCONF Client establishes a connection with the O-RU NETCONF Server -2. The TER NETCONF Client configures sudo user account and password using `o-ran-user.mgmt.yang`. - Additionally, if O-RU NETCONF Server supports the multi-operator Shared O-RU feature the TER NETCONF Client configures the carrier user account and password. The 'nms', 'fm-pm', 'swm', 'smo' and 'hybrid-odu' privilege groups can optionally be configured. - -NOTE 1: For new user accounts which are CERTIFICATE, leaf shall not be present. - -NOTE 2: In this message, the user account with "carrier" privileges may be associated with Shared Resource Operator IDs (sro-id), as specified in clause 19 of [3]. - -``` - - - - - - merge - - - - MPLANEUSER0 - PASSWORD - 12345678 - true - - - MPLANEUSER1 - PASSWORD - 12345678 - true - - 22110 - - - - - - - - - -``` - -- The TER NETCONF Client configures user account to group mappings using ietf-netconf-acm.yang for the user accounts created in Step 2. The 'nms', 'fm-pm', 'swm', 'smo' and 'hybrid-odu' privilege groups can be mapped if created in step 2. - -``` - - - - - - merge - - - -``` - -``` - - - sudo - MPLANEUSER0 - - - - carrier - MPLANEUSER1 - - - - - - - - -``` - -4. The O-RU NETCONF Server confirms the operations for the above transactions -5. The TER NETCONF Client retrieves a list of users from O-RU NETCONF Server. The newly created user accounts and mappings are validated. The password leaf shall not be present. - -``` - - - - - report-all - - - - - - - - oranuser - PASSWORD - true - - - xranuser - PASSWORD - true - - - MPLANEUSER0 - PASSWORD - true - - - MPLANEUSER1 - PASSWORD - true - - -``` - -``` - - 22110 - - - - - -``` - -##### D. Test Requirement (expected result) - -Step 5 is correctly validated. - -#### 3.1.8.2 Access Control Sudo (negative case) - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for an O-RU. - -NOTE 1: This test is only valid for “Password authentication” because “account-type CERTIFICATE” does not set . - -This test validates that the O-RU correctly implements NETCONF Access Control security aspects. - -The scenario corresponds to the following clauses in [3]: - -- 6.4 NETCONF Connection Establishment -- 6.5 NETCONF Access Control - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.8.1 is successfully completed. -2. If the O-RU NETCONF Server supports, the multi-operator Shared O-RU feature, the TER NETCONF Client configures the carrier user account and password. The ‘nms’, fm-pm’, swm’, smo’ and ‘hybrid-odu’ privilege groups can optionally be configured. - -###### b. Procedure - -1. The TER NETCONF Client establishes a connection using a user account with sudo privileges. -2. The TER NETCONF Client gets the password leaves from the user-mgmt.yang model. - -``` - - - - - report-all - - - -``` - -3. The O-RU NETCONF Server replies by silently omitting data nodes and their descendants to which the client does not have read access from the message. - -NOTE: In this message, the user account with "carrier" privileges may be associated with Shared Resource Operator IDs (sro-id), as specified in clause 19 of [3]. - -``` - - - - - MPLANEUSER0 - PASSWORD - true - - - MPLANEUSER1 - PASSWORD - true - - 22110 - - - - -``` - -##### D. Test Requirement (expected result) - -Test step 3 is performed successfully. - -#### 3.1.8.3 Access Control NMS (negative case) - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for an O-RU if nms user is created. - -This test validates that the O-RU correctly implements NETCONF Access Control user privileges. - -The scenario corresponds to the following clauses in [3]: - -- 6.5 NETCONF Access Control - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.8.1 is successfully completed. -2. A nms privileged user account is provisioned on the O-RU NETCONF Server. - -###### b. Procedure - -1. The TER NETCONF Client establishes a connection. Instead of using the default SUDO account, the NETCONF Client uses a user account with NMS privileges. -2. The TER NETCONF Client attempts to configure a new user/password account on the NETCONF Server using the user-mgmt.yang model. - -NOTE: For new user accounts which are CERTIFICATE, leaf shall not be configured. - -``` - - - - - - merge - - - - MPLANEUSER - PASSWORD - 12345678 - true - - - - -``` - -3. The NETCONF Server replies rejecting the protocol operation with an "access-denied" error. - -``` - - - protocol - access-denied - error - - -``` - -##### D. Test Requirement (expected result) - -Test step 3 is performed successfully. - -#### 3.1.8.4 Access Control FM-PM (negative case) - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for an O-RU if fm-pm user is created. - -This test validates that the O-RU correctly implements NETCONF Access Control user privileges. - -The scenario corresponds to the following clause in [3]: - -- 6.5 NETCONF Access Control - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.8.1 is successfully completed. - -2. A fm-pm privileged user account is provisioned on the O-RU NETCONF Server. - -###### **b. Procedure** - -1. The TER NETCONF Client establishes a connection. Instead of using the default SUDO account, the NETCONF Client uses a user account with fm-pm privileges. -2. The TER NETCONF Client attempts to configure a new processing-element on the NETCONF Server using the o-ran-processing-element yang model - -``` - - - - - - merge - - ETH-INTERFACE - - HD-BDE_00000600_processing-element01 - - HD-BDE_00000600_uc-vlan0 - - 00:03:A2:0A:00:00 - 2 - 38:AF:D7:D5:CE:9B - - - - - - - -``` - -3. The NETCONF Server replies rejecting the protocol operation with an "access-denied" error. - -``` - - - protocol - access-denied - error - - -``` - -##### **D. Test Requirement (expected result)** - -Test step 3 is performed successfully. - -#### 3.1.8.5 Access Control SWM (negative case) - -##### **A. Test Description and Applicability** - -This scenario is CONDITIONAL MANDATORY for an O-RU if swm user is created. - -This test validates that the O-RU correctly implements NETCONF Access Control user privileges. - -The scenario corresponds to the following clause in [3]: - -- 6.5 NETCONF Access Control - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.8.1 is successfully completed. -2. A swm privileged user account is provisioned on the O-RU NETCONF Server. - -###### b. Procedure - -1. The TER NETCONF Client establishes a connection. Instead of using the default SUDO account, the NETCONF Client uses a user account with swm privileges. -2. The TER NETCONF Client attempts to get the configuration of the o-ran-fm.yang model - -``` - - - report-all - - -``` - -3. The NETCONF Server replies by silently ignoring the read access initiated by the request done in step 2. No error or warning will be reported. - -NOTE: a reply rejecting the protocol operation with an "access-denied" error only occurs for a write request. - -``` - - -``` - -##### D. Test Requirement (expected result) - -Test step 3 is performed successfully. - -#### 3.1.8.6 Sudo on Hierarchical M-plane architecture (positive case) - -##### A. Test Description and Applicability - -This scenario is MANDATORY for an O-RU. - -NOTE: To configure a user account with "carrier" privileges, the O-RU should support the multi-operator shared O-RU feature, as specified in clause 19 of [3]. - -This test validates that user management model can be used to add users to the O-RU - -This scenario corresponds to the following clause in [3]: - -- 6.4 NETCONF Connection Establishment -- 6.5 NETCONF Access Control -- 6.8 Closing a NETCONF Session - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed. - -###### b. Procedure - -1. The TER NETCONF Client establishes connection and creates one or two user accounts depending on the DUT Shared-O-RU capabilities: - - If DUT does not support the multi-operator Shared-O-RU feature, TER NETCONF Client creates one user account, “oranuser2”, using o-ran-user-mgmt.yang. In addition, the messages below related to oranuser3 shall be deleted. - - If the DUT supports the multi-operator Shared-O-RU feature, TER NETCONF Client creates two user accounts, “oranuser2” and “oranuser3”, using o-ran-user-mgmt.yang. - -NOTE 1: For new user accounts which are CERTIFICATE, leaf shall not be present. - -NOTE 2: In this message, the user account with "carrier" privileges may be associated with Shared Resource Operator IDs (sro-id), as specified in clause 19 of [3]. - -``` - - - - merge - - - - oranuser2 - PASSWORD - o-ran-password - true - - - oranuser3 - PASSWORD - 12345678 - true - - - - - -``` - -- ``` - - 22110 - - - - - - -``` -2. The O-RU NETCONF Server confirms the operation - -``` - - - - - -``` - 3. The TER NETCONF Client configures user account to group mappings for the one or two new accounts using ietf-netconf-acm.yang respectively one with “sudo” and one with “carrier” privilege. - -``` - - - - - - - merge - - - - - sudo - oranuser2 - - - carrier - oranuser3 - - - - - - - -``` - 4. The O-RU NETCONF Server confirms the operations for the above transactions. - 5. The TER NETCONF Client retrieves a list of users from O-RU NETCONF Server. The account for the user created in step 1 is validated in this list. The password leaf shall not be present - -``` - - - - - report-all - - - - - - -``` - -``` - - - - oranuser - PASSWORD - true - - - oranuser2 - PASSWORD - true - - - oranuser3 - PASSWORD - true - 22110 - - - - - -``` - -6. The TER NETCONF Client closes the NETCONF session. - -``` - - - - - -``` - -7. The O-RU NETCONF Server establishes a TCP connection and performs the Call Home procedure to the TER NETCONF Client using the same IP and VLAN. -8. The TER NETCONF Client establishes a SSH session / TLS connection towards the NETCONF Server. The user account created in step 1 is used (oranuser2). -9. The O-RU NETCONF Server accepts the SSH session / TLS connection establishment from TER NETCONF Client -10. The TER NETCONF Client and O-RU NETCONF Server exchange capabilities through the NETCONF messages. -11. If the DUT supports the multi-operator Shared-O-RU features, repeat from step 7 to step 10, using oranuser3. - -##### D. Test Requirement (expected result) - -Each step above is correctly validated. - -#### 3.1.8.7 Access Control SMO (negative case) - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for an O-RU if smo user is created. - -This test validates that the O-RU correctly implements NETCONF Access Control user privileges. - -The scenario corresponds to the following clause in [3]: - -- 6.5 NETCONF Access Control - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.8.1 is successfully completed. -2. A smo privileged user account is provisioned on the O-RU NETCONF Server. - -###### b. Procedure - -1. The TER NETCONF Client establishes a connection. Instead of using the default SUDO account, the NETCONF Client uses a user account with smo privileges. -2. The TER NETCONF Client attempts to send rpc supervision-watchdog-reset towards the NETCONF Server using the o-ran-supervision yang model. - -``` - - - 60 - 10 - - -``` - -3. The NETCONF Server replies rejecting the protocol operation with an "access-denied" error. - -``` - - - protocol - access-denied - error - - -``` - -##### D. Test Requirement (expected result) - -Test step 3 is performed successfully. - -#### 3.1.8.8 Access Control Hybrid-ODU (negative case) - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for an O-RU if Hybrid-ODU user is created. - -This test validates that the O-RU correctly implements NETCONF Access Control user privileges. - -The scenario corresponds to the following clause in [3]: - -- 6.5 NETCONF Access Control - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.8.1 is successfully completed. -2. A hybrid-odu privileged user account is provisioned on the O-RU NETCONF Server. - -###### b. Procedure - -1. The TER NETCONF Client establishes a connection. Instead of using the default SUDO account, the NETCONF Client uses a user account with hybrid-odu privileges. -2. The TER NETCONF Client attempts to send rpc retrieve-file-list towards the NETCONF Server using the o-ran-file-management yang model - -``` - - - - O-RAN/log/ - - -``` - -3. The NETCONF Server replies rejecting the protocol operation with an "access-denied" error. - -``` - - - protocol - access-denied - error - - -``` - -##### D. Test Requirement (expected result) - -Test step 3 is performed successfully. - -#### 3.1.8.9 Access Control Carrier (negative case) - -The test description, applicability, entrance criteria, methodology and requirements are the same as in clause 3.1.8.8, Access Control Hybrid-ODU (negative case). - -This test is applicable to the O-RU supporting the multi-operator shared O-RU feature, as specified in clause 19 of [3]. The only difference from clause 3.1.8.8 is this test provisions the carrier privileged user account instead of hybrid-odu user account on the O-RU NETCONF Server. - -This scenario is CONDITIONAL MANDATORY for an O-RU if carrier user is created. - -#### 3.1.8.10 Access Control change own password - -##### A. Test Description and Applicability - -This scenario is MANDATORY for an O-RU. - -NOTE: This test is only valid for “Password authentication” because “account-type CERTIFICATE” does not set . - -This test validates that the user management model can change password for ‘carrier’, ‘swm’, ‘nms’, ‘fm-pm’ access groups. - -This scenario corresponds to the following clauses in [3]: - -- 6.4 NETCONF Connection Establishment -- 6.5 NETCONF Access Control - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.8.1 is successfully completed. - -###### b. Procedure - -1. The TER NETCONF Client establishes connection and changes a password for **carrier** user using o-ran-usermgmt - -``` - - - 12345678 - 23456789 - 23456789 - - -``` -2. The O-RU NETCONF Server confirms the operation - -``` - - Successful - Current user's password is changed successfully - -``` - -3. The TER NETCONF Client closes the NETCONF session. - - -``` - - - -``` -4. The O-RU NETCONF Server establishes a TCP connection and performs the Call Home procedure to the TER NETCONF Client using the same IP and VLAN. -5. The TER NETCONF Client establishes a SSH session towards the NETCONF Server. The user password which is configured in step 1 is used. -6. The O-RU NETCONF Server accepts the SSH session establishment from TER NETCONF Client -7. The TER NETCONF Client and O-RU NETCONF Server exchange capabilities through the NETCONF messages. -8. Repeat this test from step 1 with 'swm', 'nms', 'fm-pm' access groups instead of using 'carrier' access group. - -##### **D. Test Requirement (expected result)** - -Each step above is correctly validated. - -### 3.1.9 External Input / Output Ports - -#### 3.1.9.1 External Input Port State Detection - -##### **A. Test Description and Applicability** - -This scenario is CONDITIONAL MANDATORY. The test is applicable only for O-RUs supporting external input ports. - -This test validates proper handling of logical input ports. - -This scenario corresponds to the following clause in [3]: - -- 14.5.2 External input - -##### **B. Test Entrance Criteria** - -- The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. -- Supplementary circuitry is required to force a change of logical state of input lines belonging to an input port. It is assumed that logical input ports are internally pulled to logical high state by O-RU, therefore supplementary circuitry shall only allow to change the input port to a logical low. To determine a physical input line for this test, one shall read the customer documentation applicable for the O-RU being tested. - -##### **C. Test Methodology** - -###### **a. Initial Conditions** - -1. The test procedure described in clause 3.1.4.1 is successfully completed. - -###### **b. Procedure** - -1. The External Input Ports are left in their normal, default state. For the purposes of this test, these input ports are assumed to be a logical high. -2. The TER NETCONF Client retrieves state of chosen input port by issuing - - -``` - - - -``` - -``` - - - - - - - report-all - - - -``` - -- The O-RU NETCONF Server provides the state of every line-in belonging to the input port under test to the TER NETCONF Client. For all input lines, the state is TRUE, indicating open circuit (no shortage to ground is detected by input lines) - -``` - - - - - - PORT0 - 0 - TRUE - - - - - -``` - -- The TER supplementary circuitry randomly shorts one or more input lines to the ground. Changes shall occur with a periodicity greater than 30 seconds. -- For every change the O-RU NETCONF Server sends notification to the TER NETCONF Client. The notification contains updated states of input lines belonging to the port under test. A state FALSE indicates shortage to ground detected by particular input line. - -``` - -notification xmlns="urn:ietf:params:xml:ns:netconf:notification:1.0"> - YYYY-MM-DDTHH:MM:SS.FZ - - - - PORT0 - FALSE - - - - - -``` - -- This test scenario is looped to step 4 for a total of 10 iterations including the first pass through steps 1 to 4. - -##### D. Test Requirement (expected result) - -Step 5 is correctly validated for each of the total of 10 iterations of the test. - -#### 3.1.9.2 External Output Port State Control - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY. The test is applicable only for O-RUs supporting external output ports. - -This test validates proper handling of logical output ports. - -This scenario corresponds to the following clause in [3]: - -- 14.5.3 External output - -##### B. Test Entrance Criteria - -- The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. -- Supplementary circuitry is required to measure voltage of an output port signal. To determine the mapping of physical output lines to ports, one shall read customer documentation for the O-RU being tested. The definition of voltage levels served by output lines of output ports and the maximum allowed current sourced by single an output line shall be validated against the TER capabilities. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.4.1 is successfully completed. - -###### b. Procedure - -1. The TER NETCONF Client issues : to the O-RU NETCONF Server requesting all output lines belonging to output port to be set to FALSE. - -``` - - - - merge - - - - External-Output-0 - false - - - - - -``` - -2. The O-RU NETCONF Server sets logical LOW state to output lines corresponding to step 1 and responds to TER NETCONF Client with - -``` - - - -``` - -3. The TER supplementary circuitry shows that all output lines of the target output port are set to logical LOW state. - -4. The TER NETCONF Client issues : towards NETCONF Server requesting a random change of states of output lines belonging to target output port. Changes shall occur with a periodicity greater than 30 seconds. - -``` - - - - - merge - - - - External-Output-0 - true - - - - - - -``` - -5. The O-RU NETCONF Server sets the requested states of output lines for the states defined by step 4 and responds to NETCONF Client with . The TER supplementary circuitry validates the change. - -``` - - - - - -``` -6. This test scenario is looped to step 5 for a total of 10 iterations including the first pass through steps 1 to 4. - -##### D. Test Requirement (expected result) - -Step 5 is correctly validated for each of the total of 10 iterations of the test. - -### 3.1.10 O-RU Configurability - -#### 3.1.10.1 O-RU Configurability Test (positive case) - -##### A. Test Description and Applicability - -This scenario is MANDATORY for O-RU Tests. - -This test validates eAxC configuration and validation. The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design. - -This scenario corresponds to the following clauses in [3]: - -- 9 Configuration Management -- 15.2 User plane message routing - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane is operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.4.1 is successfully completed. - -###### b. Procedure - -1. The TER NETCONF Client assigns unique eAxC\_IDs to low-level-rx-endpoints. The same set of eAxC\_IDs is also assigned to low-level-tx-endpoints. The TER NETCONF Client uses . - -NOTE: The following is an example and is expected to vary for different equipment or configurations. - -``` - - - - - - merge - - - - Low-Level-Tx-Endpoint-0 - - STATIC - 14 - 4 - - 193 - NORMAL - 88 - 72 - -3276 - - KHZ_30 - 273 - - - 49152 - 16128 - 240 - 15 - 0 - - ... - Low-Level-Rx-Endpoint-0 - - STATIC - 14 - 4 - - 193 - NORMAL - 88 - 72 - -3276 - - - - -``` - -``` - - KHZ_30 - 273 - - - KHZ_30 - 21 - - - 49152 - 16128 - 240 - 15 - 0 - -false - -... - - - - -``` - -2. The O-RU NETCONF Server responds with a message indicating successful completion of requested procedure - -``` - - - -``` - -- Netconf config change notification is generated from O-RU. This step is conditional mandatory, the condition is to support the capability which allows O-RU Controllers to configure the O-RU to provide notifications of modifications to its YANG datastore. - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - - 2 - oranuser - - running - - /o-ran-uplane-conf:user-plane-configuration - merge - - - -``` - -##### D. Test Requirement (expected result) - -Test step 1, 2 and 3 are performed successfully if the capability that allows O-RU Controllers to configure the O-RU to provide notifications of modifications to its YANG datastore. - -Test step 1 and 2 are performed successfully if the O-RU doesn't provide notifications of modifications to its YANG datastore. - -#### 3.1.10.2 O-RU Configurability Test (negative case) - -##### A. Test Description and Applicability - -This scenario is MANDATORY for O-RU tests. - -The test scenario is intentionally limited to scope that shall be testable without a need to modify test scenario according to O-RU's hardware design. - -This test verifies that the O-RU NETCONF Server supports configurability with validation. - -This scenario corresponds to the following clauses in [3]: - -- 9 Configuration Management -- 15.2 User plane message routing - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.4.1 is successfully completed. - -###### b. Procedure - -1. The TER NETCONF Client assigns eAxC\_IDs to low-level-rx-endpoints. The same eAxC\_ID is assigned to more than one low-level-tx-endpoint or/and more than one low-level-rx-endpoint. The NETCONF Client uses . -2. The O-RU NETCONF Sever responds with the message indicating rejection of the requested procedure. - -##### D. Test Requirement (expected result) - -Test step 2 is performed successfully. - -### 3.1.11 ALD Communications - -#### 3.1.11.1 ALD Communications Test - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for an O-RU equipped with a RET port (regardless of whether this is a raw RS-485 port or OOK modem coupled internally to antenna connector(s)). This scenario shall be performed against each ALD port exposed by the O-RU. - -The purpose of the test is to validate the ALD communications protocol and operation of the O-RU. The following functions are validated in this test. - -- Proper transmission of the content if RPC towards desired ALD port -- Proper calculation of FCS -- Proper application of basic transparency to content to be transmitted -- Proper addition of start / stop flags -- Proper reception of payload injected to ALD port -- Proper removal of start / stop flags -- Proper application of basic transparency to content received from ALD port -- Proper validation of FCS in data received from ALD port. - -This scenario corresponds to the following clause in [3]: - -- 14.4 Operational aspects of Antenna Line Devices - -##### B. Test Entrance Criteria - -- The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. -- It is assumed, that O-RU being a subject of this conformance test scenario is proven to be compliant to the following specifications: - 1. ISO/IEC 13239:2002 “High-level data link control (HDLC) procedures” - 2. ETSI TS 125.460 “UTRAN Iuant Interface: General aspects and principles” - 3. ETSI TS 125.461 ”UTRAN Iuant Interface: Layer 1” - 4. ETSI TS 125.462 ”UTRAN Iuant Interface: Signalling Transport” - 5. ETSI TS 125.466 “UTRAN Iuant Interface: Application Part” - -- The O-RU uses a 9.6 kbps data rate on its ALD port(s) for transmission and reception, regardless of connector supported by particular ALD port. - -##### C. Test Methodology - -As O-RU does not verify correctness of the payload that is exchanged between NETCONF Client and ALD (except FCS for traffic coming from ALD) - any payload can be used in test vector, under condition, that test vectors are compliant to referenced above set of specification documents (e.g. length is not smaller than minimum size of real message). - -RS-485 sniffer / injector is needed for this test. Such a device shall be connected either to O-RU's RS-485 port or to RS-485 port of Smart BiasT connected to O-RU with coaxial cable (depending on O-RU construction) - -Unless not specified otherwise – RS-485 sniffer / injector shall be connected to ALD port corresponding to record “port-id” used in RPC . - -In case O-RU exposes ALD port as antenna port, test environment should utilize Smart BiasT for conversion between OOK modulation at antenna port and RS-485 signalling that RS-485 sniffer / injector can handle. DC voltage for Smart BiasT device shall be provided by O-RU through antenna feeder. - -If not specified otherwise, for test purposes RS-485 sniffer / injector is connected to ALD port which will be addressed in RPC within the scenario. - -As this test is intended to verify O-RU functions and there will be no real ALD connected – compliance to the required HDLC message structure is required, whilst the AISG payload can be artificial (unless otherwise specified in test case). The O-RU does not verify if messaging is correct, hence, for test simplicity and ease of test result verification, artificial test vectors can be used. - -###### a. Initial Conditions - -- a. The test procedure described in clause 3.1.4.1 is successfully completed. - -###### b. Procedure - -###### i. Test Case 1: Transmission towards ALD (positive scenario) - -Scope: CRC calculation, transparency algorithm application, start / stop flag addition, datagram transmission using desired ALD port - -- 1) NETCONF Client sends regular RPC message containing bytes 0x7D and 0x7E in “ald-req-msg” record. -- 2) O-RU calculates FCS, adds it to datagram provided in record “ald-req-msg”, applies basic transparency (replaces every occurrence of byte “0x7E” with two bytes “0x7D 0x5E”, respectively, replace byte “0x7D” with two bytes “0x7D 0x5D”) and add start/stop flags 0x7E. -- 3) O-RU sends payload calculated in step 2 through ALD port mentioned in record “port-id” of RPC. -- 4) RS-485 sniffer / injector receives payload sent by O-RU. Received payload is subject of analysis for scenario success / failure classification - -###### ii. Test Case 1 Test Requirement (expected result) - -Content received by RS-485 listener / injector is compared with content of RPC . - -- a) payload shall be sent by desired ALD port of O-RU -- b) FCS shall be properly calculated -- c) basic transparency shall be properly applied -- d) start / stop flags shall be added to payload that has been received by RS-485 sniffer / injector - -Test scenario is considered as completed with success in case all mentioned above conditions are satisfied. Any deviation means test scenario is failed. - -###### **iii. Test Case 2: Reception from ALD (positive case)** - -Scope: datagram reception, start / stop flag detection and removal, transparency algorithm applications, CRC verification - -NOTE: Test case 2 shall be performed just after Test case 1 so that content injected by RS-485 sniffer / injector is considered by O-RU as ALD's response to message sent towards ALD in Test case 1. Timing between Test case 1 and Test case 2 shall follow 3GPP specifications mentioned above. - -- 1) RS485 sniffer / injector sends properly formatted (start / stop flags, FCS and min / max payload size) message containing strings "0x7D 0x5E" and "0x7D 0x5D" towards O-RU's ALD port used in Test case 1. -- 2) O-RU receives the content. -- 3) O-RU removes start / stop flags, performs basic transparency (replaces "0x7D 0x5E" with "0x7E" and "0x7D 0x5D" with "0x7D"), makes sure if FCS is correct according to content of datagram. -- 4) O-RU sends "ald-resp-msg" towards NETCONF Client. In the response parameter "status" contains value "ACCEPTED". - -###### **iv. Test Case 2 Requirement (expected result)** - -Content received by NETCONF Client is compared with content injected by RS-485 sniffer / injector. - -- a) record "ald-port" shall indicate proper O-RU's ALD port as source of the payload -- b) basic transparency is properly applied -- c) counter of received octets is properly incremented -- d) counters of frames with wrong FCS (CRC) and frames without stop flags are not incremented - -Test scenario is considered as completed with success in case all mentioned above conditions are satisfied. Any deviation means test scenario is failed. - -###### **v. Test Case 3: Reception from ALD (negative case – wrong FCS)** - -Scope: datagram reception, start / stop flag detection and removal, transparency algorithm application, CRC verification - -NOTE: Test case 3 shall be performed just after Test case 1 so that content injected by RS-485 sniffer / injector is considered by O-RU as ALD's response to message sent towards ALD in Test case 1. Timing between Test case 1 and Test case 3 shall follow 3GPP specifications mentioned above. - -- 1) RS-485 sniffer / injector sends message containing wrong FCS towards O-RU's ALD port used in Test case 1. -- 2) O-RU receives the content. -- 3) O-RU removes start / stop flags, performs basic transparency (replaces "0x7D 0x5E" with "0x7E" and "0x7D 0x5D" with "0x7D") and detects, that FCS is incorrect according to content of received datagram. -- 4) O-RU sends "ald-resp-msg" towards NETCONF Client. In the response parameter "status" contains value "ACCEPTED". - -###### **vi. Test Case 3 Requirement (expected result)** - -Content received by NETCONF Client is compared with content injected by RS-485 sniffer / injector. - -- a) record “ald-port” shall indicate proper O-RU’s ALD port as source of the payload -- b) record “ald-resp-msg” is empty -- c) counter of frames without stop flags is not incremented -- d) counter of received octet and counter of frames with wrong FCS (CRC) are incremented - -Test scenario is considered as completed with success in case all mentioned above conditions are satisfied. Any deviation means test scenario is failed. - -###### **vii. Test Case 4: Reception from ALD (negative case – no stop flag)** - -Scope: datagram reception, start / stop flag detection - -NOTE: Test case 4 shall be performed just after Test case 1 so that content injected by RS-485 sniffer / injector is considered by O-RU as ALD’s response to message sent towards ALD in Test case 1. Timing between Test case 1 and Test case 4 shall follow 3GPP specifications mentioned above. - -- 1) RS-485 sniffer / injector sends message not terminated by stop flag “0x7E” towards O-RU’s ALD port used in Test case 1. -- 2) O-RU receives the content. -- 3) O-RU reaches the end of reception window without receiving stop flag that would terminate the datagram. -- 4) O-RU sends “ald-resp-msg” towards NETCONF Client. In the response parameter “status” contains value “ACCEPTED”. - -###### **viii. Test Case 4 Requirement (expected result)** - -Content received by NETCONF Client is compared with content injected by RS-485 sniffer / injector. - -- a) record “ald-port” shall indicate proper O-RU’s ALD port as source of the payload -- b) record “ald-resp-msg” is empty -- c) counter of frames with wrong FCS (CRC) is not incremented -- d) counter of received octets and counter of frames without stop flags are incremented - -Test scenario is considered as completed with success in case all mentioned above conditions are satisfied. Any deviation means test scenario is failed. - -###### **ix. Test case 5: Transmission towards ALD (negative scenario – wrong ALD port)** - -Scope: CRC calculation, transparency algorithm application, start / stop flag addition, datagram transmission using desired ALD port (ports are not used by the same HDLC Primary Device) - -Scenario is applicable only in case O-RU supports more than one ALD port and under condition that ALD ports do not share single modem. - -IMPORTANT: In this scenario RS-485 sniffer / injector shall be connected to ALD port different from than the one indicated in record “port-id” of RPC . - -- 1) NETCONF Client sends regular RPC message. -- 2) O-RU performs the content processing and sends the content towards ALD port that corresponds to content of record “port-id” of RPC -- 3) RS-485 sniffer / injector does not receive payload sent by O-RU. - -###### **x. Test Requirement (expected result)** - -Test scenario is considered as completed with success in case RS-485 sniffer / injector does not receive payload in step 3. Any deviation is considered as failed test case. - -###### **xi. Test case 6: Transmission towards ALD (negative scenario – non-existing ALD port)** - -Scope: datagram reception - -- 1) NETCONF Client sends regular RPC message. Parameter used in RPC does not point to existing ALD port. -- 2) O-RU sends to NETCONF Client. In the response parameter “error-tag” contains value “data-missing”. -- 3) NETCONF Client receives the message as described above. - -###### **xii. Test Requirement (expected result)** - -Test scenario is considered as completed with success in case step 3) is reached. - -### 3.1.12 Log Management - -#### 3.1.12.1 Troubleshooting Test - -##### **A. Test Description and Applicability** - -This scenario is MANDATORY for O-RU Tests. - -This test validates the capability of the O-RU to upload troubleshooting logs including alarm information. - -This scenario corresponds to the following clause in [3]: - -- 14.2.2 Troubleshooting Log Management - -##### **B. Test Entrance Criteria** - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### **C. Test Methodology** - -###### **a. Initial Conditions** - -1. The test procedure described in clauses 3.1.2.1 and 3.1.4.1 is successfully completed. - -###### **b. Procedure** - -1. The TER NETCONF Client sends to the O-RU NETCONF Server. The O-RU NETCONF Server responds with . - -``` - - - - - - - SUCCESS - - -``` - -2. The O-RU NETCONF Server starts generating one or more file(s) containing troubleshooting logs. When the generation of the log file(s) are completed, the O-RU NETCONF Server sends with a list of one or more log file names to the TER NETCONF Client. - -NOTE: It is assumed that the generated log file(s) contains troubleshooting logs related to alarm 17 measured in clause 3.1.5.2 or a vendor specific alarm, but the content and format are not specified. - -``` - - - YYYY-MM-DDTHH:MM:SS.FZ - - o-ran/log/Troubleshootinglog.gz - - - -``` - -3. The TER NETCONF Client sends log-file-name to the O-RU NETCONF Server to start uploading the log file(s). The O-RU NETCONF Server responds with with status SUCCESS. - -``` - - - - o-ran/log/Troubleshootinglog.gz - - sftp://oranuser@192.168.3.13:22/local/log - - 1234 - - - - - - SUCCESS - - -``` - -4. The O-RU NETCONF Server uploads the log file(s) to NETCONF Client by sFTP/FTPES, using FTPES if the O-RU controller is using NETCONF/TLS to configure the O-RU. When file upload is completed, the O-RU NETCONF Server sends with status SUCCESS. - -``` - - - YYYY-MM-DDTHH:MM:SS.FZ - - o-ran/log/Troubleshootinglog.gz - sftp://oranuser@192.168.3.13:22/local/log - - SUCCESS - - - -``` - -##### D. Test Requirement (expected result) - -Test step 4 is performed successfully. - -NOTE: The O-RU vendor may check the contents of the uploaded log file in detail for the reported alarm 17, but as noted, the content and format of troubleshooting logs are not defined. - -#### 3.1.12.2 Trace Test - -##### A. Test Description and Applicability - -This scenario is MANDATORY for O-RU Tests. - -This test validates the capability of the O-RU to upload trace logs. - -This scenario corresponds to the following clause in [3]: - -- 14.3 Trace - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clauses 3.1.2.1 and either 3.1.4.1 or clause 3.1.4.2 are successfully completed. -2. A timer is configured in the TER to wait for the notification from the DUT in step 3, e.g., 15 minutes. - -###### b. Procedure - -1. The TER NETCONF Client sends to the O-RU NETCONF Server. The O-RU NETCONF Server responds with . - -``` - - - - - - - SUCCESS - - -``` - -2. The O-RU NETCONF Server starts generating one or more file(s) containing trace logs. The TER waits for the pre-configured amount of time to receive notification from the DUT. -3. If the generation of the log file(s) are completed, the O-RU NETCONF Server sends and set as false with a list of one or more log file names to the TER NETCONF Client, and the TER receives the notification from the DUT. Otherwise, the test shall jump to step 6. - -NOTE: It is assumed that the generated log file(s) contains trace logs related to O-RU Vendor specific, but the content and format are not specified. - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - o-ran/log/TraceLog.gz - false - - -``` - -4. The TER NETCONF Client sends log-file-name to the O-RU NETCONF Server to start uploading the log file(s). The O-RU NETCONF Server responds with with status SUCCESS. - -``` - - - o-ran/log/TraceLog.gz - sftp:// -oranuser@192.168.3.13:22/local/log - - 1234 - - - - - - SUCCESS - -``` - -5. The O-RU NETCONF Server uploads the log file(s) to NETCONF Client by sFTP/FTPES, using FTPES if the O-RU controller is using NETCONF/TLS to configure the O-RU. When file upload is completed, the O-RU NETCONF Server sends with status SUCCESS. - -``` - -``` - -``` - -YYYY-MM-DDTHH:MM:SS.FZ - - o-ran/log/TraceLog.gz - sftp://oranuser@192.168.3.13:22/local/ -log - SUCCESS - - - -``` - -6. The TER NETCONF Client sends to the O-RU NETCONF Server. The O-RU NETCONF Server responds with . - -``` - - - - - - - SUCCESS - - -``` - -7. The TER NETCONF Client can wait for the notification from the O-RU NETCONF Server. The O-RU NETCONF Server sends and set to true. - -``` - - - YYYY-MM-DDTHH:MM:SS.FZ - - o-ran/log/TraceLog.gz - true - - - -``` - -8. The TER NETCONF Client sends log-file-name to the O-RU NETCONF Server to start uploading the remaining log file(s). The O-RU NETCONF Server responds with with status SUCCESS. - -``` - - - - o-ran/log/TraceLog.gz - sftp:// -oranuser@192.168.3.13:22/local/log - - 1234 - - - - -``` - -``` - - - - - SUCCESS - - -``` - -9. The O-RU NETCONF Server uploads the remaining log file(s) to NETCONF Client by sFTP/FTPES, using FTPES if the O-RU controller is using NETCONF/TLS to configure the O-RU. When file upload is completed, the O-RU NETCONF Server sends with status SUCCESS. - -``` - - - YYYY-MM-DDTHH:MM:SS.FZ - - o-ran/log/TraceLog.gz - sftp://oranuser@192.168.3.13:22/local/ -log - SUCCESS - - - -``` - -##### D. Test Requirement (expected result) - -Test step 9 is performed successfully. If the TER receives the notification from DUT in step 3, then test step 5 is performed successfully. - -NOTE: The O-RU vendor may check the contents of the uploaded log file in detail for the reported trace logs, but as noted, the content and format of trace logs are not defined. - -### 3.1.13 Connectivity Check - -#### 3.1.13.1 Ethernet Connectivity Monitoring - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY if the O-RU supports C-Plane and U-Plane connectivity over Ethernet. - -This test validates the proper operation of LBM on the O-RU. - -This scenario corresponds to the following clauses in [3]: - -- 7.3 C/U Plane VLAN configuration -- 7.5 Definition of processing elements -- 7.6.1 C/U-Plane transport connectivity verification - -##### B. Test Entrance Criteria - -1. The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. -2. Result validation of this test requires TER capabilities such as a network sniffer that allows for traffic analysis over ETH frames between O-RU and TER. - -##### C. Test Methodology - -###### a. Initial Conditions - -The test procedure described in clause 3.1.4.1 is successfully completed. - -###### b. Procedure - -1. The TER NETCONF Client configures the O-RU NETCONF Server with a vlan-id for the C-Plane and U-Plane interfaces. -2. The TER NETCONF Client configures a transport-flow in the O-RU processing element: a combination of VLAN identity, O-DU MAC address and O-RU MAC address. -3. The TER sends loopback message to the O-RU MAC address configured for the processing element. -4. The O-RU sends loopback responses to the O-DU MAC Address of the loopback message. - -##### D. Test Requirement (expected result) - -Packets are sent correctly in step 3 and 4, as validated via the TER. - -#### 3.1.13.2 UDP Echo Test - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY. The test is applicable only if the O-RU supports C-Plane and U-Plane sessions over IP. - -This test validates the proper operation UDP Echo on the O-RU for continuous verification of connectivity. - -This scenario corresponds to the following clauses in [3]: - -- 7.4 O-RU C/U Plane IP Address Assignment -- 7.5 Definition of processing elements -- 7.6 O-DU Verification of C/U Plane Transport Connectivity - -##### B. Test Entrance Criteria - -1. The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. -2. Result validation of this test requires TER capabilities such as a network sniffer that allows for traffic analysis over ETH frames between O-RU and TER. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.4.1 is successfully completed. - -###### b. Procedure - -1. The TER NETCONF Client configures IP information and udppip-flow in the O-RU processing element for the C-Plane and U-Plane communications. -2. The TER NETCONF Client configures the enable-udp-echo leaf = true in the udp-echo YANG model to be enabled operation of the UDP echo server in the O-RU. -3. The TER NETCONF Client sends a UDP datagram to UDP port number:7 of the O-RU NETCONF Server. -4. The O-RU NETCONF Server sends back the UDP datagram to the TER NETCONF Client. -5. The TER NETCONF Client configures the enable-udp-echo leaf = false in the udp-echo YANG model to be disabled operation of the UDP echo server in the O-RU. - -##### **D. Test Requirement (expected result)** - -Packets are sent correctly in step 3 and 4 as validated by the TER with sniffer capability. - -### 3.1.14 Energy Savings - -#### 3.1.14.1 Carrier Deactivation and Energy Saving Configuration - -##### **A. Test Description and Applicability** - -This scenario is CONDITIONAL MANDATORY for O-RU. - -This test validates carrier deactivation and energy saving configuration. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports energy-saving. - -This scenario corresponds to the following clause in [3]: - -- 15.3.2 Activation, deactivation and sleep -- 20.2 Carrier deactivation for energy saving -- 10.2 Measurement activation and de-activation - -##### **B. Test Entrance Criteria** - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### **C. Test Methodology** - -###### **a. Initial Conditions** - -1. The test procedure described in clause 3.1.10.1 is successfully completed so that O-RU is configured to receive, process and output the test signal defined in initial condition 4. -2. Leaf active is ACTIVE in the tx-array-carrier and rx-array-carrier elements for the carriers under test. -3. The TER NETCONF Client subscribes to notifications of the measurement-object power, with the measurement-interval of 60 sec. -4. CUSM Emulator generates proper C/U plane stimulus for 3GPP test waveform with 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in section 3GPP 38.141 -1 NR-FR1-TM1.1 and section 3.2.1.1.5 of this document. If the radio does not support the bandwidth and/or numerology defined here, it will be up to the test developer to modify these parameters in the test waveform to adapt to the O-RU capabilities. - -###### **b. Procedure** - -1. The TER NETCONF Client retrieves subscribed notifications from the O-RU NETCONF Server on the power consumption performance measurement. -2. The TER measures the AC or DC power consumption of the O-RU using power meter. -3. The TER compares the difference between the reported power consumption by the O-RU NETCONF Server and the measured power consumption in step 2 to validate it is within acceptable range, e.g. $\pm 10\%$ . -4. The TER NETCONF Client sets the value of the leaf active at tx-array-carrier element / rx-array-carrier element to INACTIVE. -5. The O-RU NETCONF Server responds with a message indicating successful completion of requested procedure. -6. The TER NETCONF Client waits for at least two continuous Notifications of INACTIVE from the O-RU NETCONF Server to ensure a full cycle of INACTIVE state for power measurements is past. -7. The TER performs the DC or AC power consumption measurement with the power meter. -8. The TER verifies the transmission from the O-RU is turned OFF using a signal analyser. - -9. The TER compares the difference between the reported power consumption by the O-RU NETCONF Server and the measured in step 7 to validate it is within acceptable range, e.g. $\pm 10\%$ . The power consumption should be smaller than the previous one measured in the step 2. -10. The TER NETCONF Client sets the value of the parameter energy-saving-enabled element to TRUE. -11. The O-RU NETCONF Server responds with a message indicating successful completion of requested procedure. -12. The power-state of o-ran-hardware is switched to SLEEPING, indicating the O-RU is in energy saving mode. Check O-RU power-state=SLEEPING. -13. The TER performs the DC or AC power consumption measurement with the power meter. -14. The TER NETCONF Client waits for at least one Notification of Power measurement from the NETCONF Server to ensure a full cycle of power-state=sleeping for power measurement is completed. -15. The TER compares the difference between the reported power consumption by the NETCONF Server and the measured power consumption in step 13 to validate it is within acceptable range, e.g. $\pm 10\%$ . The power consumption measured by the power analyser is expected to be smaller than that measured in the Step 7. - -##### D. Test Requirement (expected result) - -1. The test steps above are performed successfully -2. All validation steps mentioned in step 9 and step 15 are within expected power ranges as per the vendor's O-RU product specifications. - -#### 3.1.14.2 Carrier Activation - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for O-RU. - -This test validates carrier activation from SLEEP state. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings. - -This scenario corresponds to the following clause in [3]: - -- 15.3.2 Activation, deactivation and sleep -- 20.2 Carrier deactivation for energy saving -- 10.2 Measurement activation and de-activation - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in section 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.10.1 is successfully completed so that O-RU is configured to receive, process and output the test signal defined in initial condition 5. -2. Leaf active is either INACTIVE or SLEEP in the tx-array-carrier and rx-array-carrier elements for the carriers under test. -3. Leaf state is either DISABLED (if leaf active is INACTIVE) or READY (if leaf active is SLEEP) in the tx-array-carrier and rx-array-carrier elements for the carriers under test. -4. The TER NETCONF Client subscribes to notifications of the measurement-object power, with the measurement-interval of 60 sec. -5. CUSM Emulator generates proper C/U plane stimulus for 3GPP test waveform with 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1 and clause 3.2.1.1.5 of - -this document. If the radio does not support the bandwidth and/or numerology defined here, it will be up to the test developer to modify these parameters in the test waveform to adapt to the O-RU capabilities. - -###### **b. Procedure** - -1. The TER NETCONF Client retrieves subscribed notifications from the O-RU NETCONF Server on the power consumption performance measurement. -2. The TER measures the AC or DC power consumption of the O-RU using a power meter. -3. The TER compares the difference between the power consumption reported by the O-RU NETCONF Server and the power consumption measured in step 2, validating that it is within an acceptable range, e.g. $\pm 10\%$ . -4. The TER NETCONF Client sets the value of the leaf active at tx-array-carrier element / rx-array-carrier element to ACTIVE. -5. The O-RU NETCONF Server responds with a message indicating successful completion of requested procedure. -6. The TER NETCONF Client waits for at least two continuous Notifications of ACTIVE from the NETCONF Server to ensure a full cycle of ACTIVE state for power measurements is completed. -7. The TER performs the DC or AC power consumption measurement with the power meter. -8. The TER verifies transmission is present from the O-RU and the expected signal (defined in C.a.5) is measured successfully with a signal analyser. -9. The TER compares the difference between the DC or AC power consumption reported by the O-RU NETCONF Server and the DC or AC power consumption measured in step 7, validating that it is within an acceptable range, e.g. $\pm 10\%$ . The power consumption should now be larger than the previous one measured in the step 2. -10. The TER records the time from execution of step 4 to the TER receiving the signal from the O-RU. - -##### **D. Test Requirement (expected result)** - -1. The test steps above are performed successfully. -2. All validation step mentioned in step 9 is within expected power ranges as per the vendor's O-RU product specifications. - -#### 3.1.14.3 Subscription and Reporting of Energy, Power and Environmental (EPE) Statistics - -##### **A. Test Description and Applicability** - -This scenario is CONDITIONAL MANDATORY for O-RU Tests. - -This test validates the Energy, Power and Environmental (EPE) measurement activation/deactivation and collection of measurement results. - -This scenario corresponds to the following clause in [3]: - -- 10.2 Measurement activation and de-activation - -##### **B. Test Entrance Criteria** - -The minimum functions of the TER described in section 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU - -##### **C. Test Methodology** - -###### **a. Initial Conditions** - -1. The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed. - -###### **b. Procedure** - -1. The TER NETCONF Client activates the Energy, Power and Environmental performance measurement via NETCONF to O-RU NETCONF Server with the following parameters and values: - -**Table 3.1.14-1 Configuration Parameters for performance measurement** - -| Parameters | Value | -|----------------------|----------------| -| Measurement-group | Epe-statistics | -| Measurement-object | POWER | -| Report-info | Average | -| Object-unit | O-RAN-RADIO | -| Measurement-interval | 60 sec | -| Active | True | - -2. The O-RU NETCONF Server responds with a message indicating successful completion of requested procedure. -3. The TER NETCONF Client subscribes to measurement group epe-statistics and measurement-object POWER to collect the measurement result by sending NETCONF to NETCONF server in the O-RU. The following is an example: - -``` - - - - - - POWER - - - - - -``` - -4. The O-RU NETCONF Server responds with message indicating successful completion of requested procedure. -5. The O-RU NETCONF Server sends NETCONF notification messages periodically to the client with configured measurement result. -6. TER waits for 5 minutes and then validates that notification messages are generated according to measurement-interval and notification-interval. -7. The TER NETCONF Client deactivates the Energy, Power and Environmental (EPE) performance measurement via NETCONF to O-RU NETCONF Server. -8. The O-RU NETCONF Server stops sending NETCONF notification messages to the client. - -##### D. Test Requirement (expected result) - -1. The test steps above are performed successfully -2. All validation steps above are within expected ranges or correctly match the expected outcome. - -#### 3.1.14.4 M-Plane based TRX control - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for O-RU. The test must be executed if the O-RU supports M-plane based TRX control. - -This test validates M-plane based TRX control. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings. - -This scenario corresponds to the following clause in [3]: - -- 20.3.2 TRX control – M-Plane controlled -- 10.2 Measurement activation and de-activation - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.10.1 is successfully completed so that O-RU is configured to receive, process and output the test signal defined in initial condition 5. -2. The O-RU NETCONF Server exposes the capability to support energy savings. -3. The antenna mask is set to enable all array-elements . -4. The TER NETCONF Client subscribes to notifications of the measurement-object *power*, with the measurement-interval of 60 sec. -5. CUSM Emulator generates proper C/U plane stimulus for 3GPP test waveform with 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1 and clause 3.2.1.1.5 of this document. If the radio does not support the bandwidth and/or numerology defined here, it will be up to the test developer to modify these parameters in the test waveform to adapt to the O-RU capabilities. - -###### b. Procedure - -1. The TER NETCONF Client retrieves subscribed notifications from the O-RU NETCONF Server on the power consumption performance measurement. -2. The TER measures the AC or DC power consumption of the O-RU using power meter. -3. The TER compares the power difference between the reported power consumption by the O-RU NETCONF Server and the measured power consumption in step 2 and validates it is within acceptable range, e.g. $\pm 10\%$ . -4. The TER NETCONF Client sets the value of antenna mask for the [tr]x-array. It is recommended to set at least half of the antenna mask off in order to have more differentiable power changes. - -For the case where the O-RU advertises mplane-supported-trx-control-masks list, RPC edit-config shall be used to configure a specific antenna mask value by specifying a given antenna-bitmask-index for the [tr]x-array using the YANG parameter [tr]x-array-antenna-mask-config. - -EXAMPLE-1: configuration of a given 32-bit tx antenna mask by specifying the antenna-index 1, which points to an antenna mask that has half ones and the other half zeros: - -``` - - - - - - - - - tx-array-1 - - 1 - - - - - - - -``` - -For the case where the O-RU does not advertise mplane-supported-trx-control-masks list for a given [tr]x-array, the RPC edit-config shall be used to configure a specific antenna-bitmask value for the [tr]x-array using the YANG parameter [tr]x-array-antenna-mask-config. - -EXAMPLE-2: configuration of a 32-bit tx antenna mask is shown below: - -``` - - - - - - - - - tx-array-1 - - 1111111100000000000000000011111111 - - - - - - - -``` - -- The O-RU NETCONF Server responds with a message indicating successful completion of requested procedure. - -For Example, - -``` - - - - - -``` - -6. The TER NETCONF Client waits for mplane-trx-control-ant-mask-update notification. - -EXAMPLE-1: mplane-trx-control-ant-mask-update notification by specifying the antenna-index is shown below: - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - tx-array-1 - - tx-array - - 1 - - - -``` - -EXAMPLE-2: mplane-trx-control-ant-mask-update notification by specifying antenna mask is shown below: - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - - tx-array-1 - - tx-array - - 1111111100000000000000000011111111 - - - - -``` - -7. The TER performs the DC or AC power consumption measurement with the power meter. -8. The TER compares the difference between the reported power consumption by the O-RU NETCONF Server and the measured in step 7 to validate it is within acceptable range, e.g. $\pm 10\%$ . The power consumption should be smaller than the previous one measured in the step 2. -9. The TER NETCONF Client resets the value of antenna mask for the [tr]x-array after 15 minutes. For the case where the O-RU advertises mplane-supported-trx-control-masks list, RPC edit-config shall be used to configure a specific antenna mask value by specifying a given antenna-bitmask-index for the [tr]x-array using the YANG parameter [tr]x-array-antenna-mask-config. - -EXAMPLE-1: configuration of a given 32-bit tx antenna mask by specifying the antenna-index 5 which points to all-ones antenna mask: - -``` - - - - - - - - - - -``` - -``` - - tx-array-1 - - 5 - - - - - - - - - -``` - -For the case where the O-RU does not advertise mplane-supported-trx-control-masks list for a given [tr]x-array, the RPC edit-config shall be used to configure a specific antenna-bitmask value for the [tr]x-array using the YANG parameter [tr]x-array-antenna-mask-config. - -EXAMPLE-2: configuration of a 32-bit tx antenna mask is shown below: - -``` - - - - - - - - - - - tx-array-1 - - 11111111111111111111111111111111 - - - - - - - - -``` - -Note : For resetting antenna mask 15 minutes is specified as an example, actual value may depend on O-RU implementation. - -10. The O-RU NETCONF Server responds with a message indicating successful completion of requested procedure. - -For Example, - -``` - - - - - - - -``` - -11. The TER NETCONF Client waits for mplane-trx-control-ant-mask-update notification. - -For Example, - -EXAMPLE-1: mplane-trx-control-ant-mask-update notification by specifying the antenna-index is shown below: - -``` - - - -``` - -``` - -YYYY-MM-DDTHH:MM:SS.FZ - - - tx-array-1 - - tx-array - - 5 - - - -``` - -EXAMPLE-2: `mplane-trx-control-ant-mask-update` notification by specifying antenna mask is shown below: - -``` - - - - YYYY-MM-DDTHH:MM:SS.FZ - - - tx-array-1 - - tx-array - - 11111111111111111111111111111111 - - - - - -``` - -12. The TER performs the DC or AC power consumption measurement with the power meter. -13. The TER verifies the expected signal (defined in C.a.5) is measured successfully with a signal analyser. -14. The TER compares the DC or AC power difference between the reported power consumption by the O-RU NETCONF Server and the measured DC or AC power consumption in step 12 to validate it is within acceptable range, e.g. $\pm 10\%$ . The power consumption should now be larger than the previous one measured in the step 7. - -##### D. Test Requirement (expected result) - -1. Test steps above are performed successfully. -2. All validation steps mentioned in step 8 and step 14 are within expected power ranges as per the vendor's O-RU product specifications. - -#### 3.1.14.5 Deep-hibernate - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for O-RU. The test shall be executed if the O-RU supports deep-hibernate. - -This test validates deep-hibernate. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports energy savings. - -This scenario corresponds to the following clause in [3]: - -- 20.5 Deep-hibernate - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU - -##### C. Test Methodology - -###### a. **Initial Conditions** - -1. The test procedure described in clause 3.1.10.1 is successfully completed so that O-RU is configured to receive, process and output the test signal defined in initial condition 4. -2. The O-RU NETCONF Server exposes the capability to support energy savings including deep-hibernate. -3. The TER NETCONF Client subscribes to notifications of the measurement-object *power*, with the measurement-interval of 60 sec. -4. CUSM Emulator generates proper C/U plane stimulus for 3GPP test waveform with 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1 and clause 3.2.1.1.5 of this document. If the radio does not support the bandwidth and/or numerology defined here, it will be up to the test developer to modify these parameters in the test waveform to adapt to the O-RU capabilities. - -###### a. **Procedure** - -1. The TER NETCONF Client retrieves subscribed notifications from the O-RU NETCONF Server on the power consumption performance measurement. -2. The TER measures the AC or DC power consumption of the O-RU using power meter. -3. The TER compares the power difference between the reported power consumption by the O-RU NETCONF Server and the measured power consumption in step 2 and validates it is within acceptable range, e.g. $\pm 10\%$ . -4. The TER NETCONF Client sends deep-hibernate rpc command. - -For Example, - -``` - - - - - - - - - 15 - - - - - -``` - -NOTE: hibernate-time is between min-hibernate-time-duration and max-hibernate-time-duration if advertised by the O-RU. - -5. The O-RU NETCONF Server responds with a message indicating successful completion of requested procedure. - -For Example, - -``` - - - -``` - -6. The TER NETCONF Client waits for deep-hibernate-activated notification. - -For Example, - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - -``` - -``` - -15 - - - -``` - -7. The O-RU NETCONF Server starts deep-hibernate timer. -8. The TER NETCONF Client sends close-session rpc command. - -For Example, - -``` - - - - - - - -``` - -9. The O-RU NETCONF Server enters deep-hibernate. -10. Half of hibernate time past, the TER performs the DC or AC power consumption measurement with the power meter. The power consumption should now be smaller than the previous one measured in the step 2. -11. The TER verifies the transmission from the O-RU is turned OFF using a signal analyser. -12. The O-RU NETCONF Server restarts after the expiry of hibernate-time. -13. After restart, the TER verifies restart-cause value is DEEP-HIBERNATE-RESTART. -14. After carrier activation, the TER NETCONF Client waits for at least two continuous Notifications of ACTIVE from the O-RU NETCONF Server to ensure a full cycle of ACTIVE state for power measurements is completed. -15. The TER performs the DC or AC power consumption measurement with the power meter. The power consumption should now be larger than the previous one measured in the step 10. -16. The TER verifies transmission is present from the O-RU and the expected signal (defined in C.a.4) is measured successfully with a signal analyser. - -##### D. Test Requirement (expected result) - -1. Test steps above are performed successfully. -2. All validation steps mentioned in step 10 and step 15 are within expected power ranges as per the vendor's O-RU product specifications. - -#### 3.1.14.6 Data layer control - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for O-RU. The test shall be executed if the O-RU supports Data layer control. - -This test validates Data layer control. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings. - -This scenario corresponds to the following clause in [3]: - -- 20.3.3 Data layer control -- 10.2 Measurement activation and de-activation - -##### B. Test Entrance Criteria - -The minimum functions of the TER described in clause 2.1 that support validation of the M-Plane are operational, configured and connected to the O-RU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1.10.1 is successfully completed so that O-RU is configured to receive, process and output the test signal defined in initial condition 4. -2. The O-RU NETCONF Server exposes the capability to support energy savings including Data layer control. -3. The TER NETCONF Client subscribes to notifications of the measurement-object *power*, with the measurement-interval of 60 sec. -4. CUSM Emulator generates proper C/U plane stimulus for 3GPP test waveform with 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1 and clause 3.2.1.1.5 of this document. If the radio does not support the bandwidth and/or numerology defined here, it will be up to the test developer to modify these parameters in the test waveform to adapt to the O-RU capabilities. - -###### a. Procedure - -1. The TER NETCONF Client retrieves subscribed notifications from the O-RU NETCONF Server on the power consumption performance measurement. -2. The TER measures the AC or DC power consumption of the O-RU using power meter. -3. The TER compares the power difference between the reported power consumption by the O-RU NETCONF Server and the measured power consumption in step 2 and validates it is within acceptable range, e.g. $\pm 10\%$ . -4. The TER NETCONF Client turns off data layers by adding energy-sharing-group-id into energy-sharing-groups-disabled leaf-list parameter. - -For Example, - -``` - - - - - - - 4 - - - -``` - -5. The O-RU NETCONF Server responds with a message indicating successful completion of requested procedure. - -For Example, - -``` - - - -``` - -6. The TER NETCONF Client waits for 10 seconds. -7. The TER performs the DC or AC power consumption measurement with the power meter. -8. The TER compares the difference between the reported power consumption by the O-RU NETCONF Server and the measured in step 7 to validate it is within acceptable range, e.g. $\pm 10\%$ . The power consumption should be smaller than the previous one measured in the step 2. -9. The TER NETCONF Client turns on data layers by removing energy-sharing-group-id from energy-sharing-groups-disabled leaf-list parameter after 15 minutes. - -For Example, - -``` - - - - - - - -``` - -``` - -
- - 4 - - - - -``` - -10. The O-RU NETCONF Server responds with a message indicating successful completion of requested procedure. - -For Example, - -``` - - - - - -``` - -11. The TER NETCONF Client waits for data-layer-control-wakeup-notification. - -Example, - -``` - - - - YYYY-MM-DDTHH:MM:SS.FZ - - - - 4 - - - - - -``` - -12. The TER performs the DC or AC power consumption measurement with the power meter. -13. The TER verifies the expected signal (defined in C.a.4) is measured successfully with a signal analyser. -14. The TER compares the DC or AC power difference between the reported power consumption by the O-RU NETCONF Server and the measured DC or AC power consumption in step 12 to validate it is within acceptable range, e.g. $\pm 10\%$ . The power consumption should now be larger than the previous one measured in the step 7. - -##### D. Test Requirement (expected result) - -1. Test steps above are performed successfully. -2. All validation steps mentioned in step 8 and step 14 are within expected power ranges as per the vendor's O-RU product specifications. - -## 3.1a M-Plane Measurements for O-DU - -The O-RAN Fronthaul management plane (M-Plane) protocol conformance tests for O-DU as device under test are described in this clause. Table 1.2.4-1a lists all M-Plane test cases for O-DU. - -### 3.1a.1 Transport and Handshake Test Scenarios - -#### 3.1a.1.1 Transport and Handshake in IPv4/SSH Environment - -##### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY for an O-DU that supports IPv4. - -This scenario validates that the O-DU properly executes the session establishment procedure with TED NETCONF Server. - -This scenario corresponds to the following clause in [3]: - -- 6.2 Management Plane Transport aspects -- 6.3 NETCONF Call Home to O-RU Controller(s) - -##### B. Test Entrance Criteria - -The minimum functions of the TED described in clause 2.2 that support validation of the M-Plane are operational, configured and connected to the O-DU - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The O-DU is powered on. -2. Default SSH credentials (sudo) are used by both the O-DU Netconf Client and the TED NETCONF Server. - -###### b. Procedure - -1. Optional step: The TED NETCONF Server performs the DHCPv4 procedure on the preconfigured VLAN or first VLAN where the Offer from DHCP Server / Relay is received if the scan method is used. -2. The TED NETCONF Server establishes TCP connection and performs a Call Home procedure towards the O-DU NETCONF Client. -3. The O-DU NETCONF Client establishes a SSH session with the TED NETCONF Server. Proper credentials are used. -4. The TED NETCONF Server accepts the SSH session establishment from the O-DU NETCONF Client -5. The O-DU NETCONF Client and TED NETCONF Server exchange capabilities through NETCONF messages. The following is an abbreviated example of the capabilities exchange. A typical capabilities exchange will have far more parameters included. - -NOTE: RFC 6241 is followed for NETCONF communication. - -``` -NETCONF Server (TED) Hello message . - - - urn:ietf:params:netconf:base:1.0 - urn:ietf:params:netconf:base:1.1 - urn:ietf:params:netconf:capability:writable-running:1.0 - - urn:ietf:params:netconf:capability:notification:1.0 - - urn:ietf:params:netconf:capability:interleave:1.0 - http://org/openroadm/user-mgmt?module=org-openroadm-user-mgmt&revision=2017-12-15 - ..... - - 1 - -``` - -``` - -NETCONF Client (DU) Hello message ... - - - urn:ietf:params:netconf:base:1.0 - urn:ietf:params:netconf:base:1.1 - - - -``` - -##### D. Test Requirement (expected result) - -Test scenario step 5 is performed successfully. - -#### 3.1a.1.2 Transport and Handshake in IPv6/SSH Environment - -The test description, applicability, entrance criteria, methodology and requirements are the same as in clause 3.1a.1.1, Transport and Handshake in IPv4/SSH Environment (positive case). The only difference is that this test is applicable to IPv6 environments. This test is CONDITIONAL MANDATORY for O-DU that supports IPv6. - -#### 3.1a.1.3 Transport and Handshake in IPv4/TLS Environment - -The test description, applicability, entrance criteria, methodology and requirements are the same as in clause 3.1a.1.1, Transport and Handshake in IPv4/SSH Environment (positive case). The only difference is that this test is applicable to IPv4 and TLS environments. This test is CONDITIONAL MANDATORY for O-DU that supports IPv4. - -#### 3.1a.1.4 Transport and Handshake in IPv6/TLS Environment - -The test description, applicability, entrance criteria, methodology and requirements are the same as in clause 3.1a.1.1, Transport and Handshake in IPv4/SSH Environment (positive case). The only difference is that this test is applicable to IPv6 and TLS environments. This test is CONDITIONAL MANDATORY for O-DU that supports IPv6. - -### 3.1a.2 Subscription to Notifications - -#### 3.1a.2.1 Subscription to NETCONF Event Stream - -##### A. Test Description and Applicability - -This test is MANDATORY for O-DU. - -This test validates that the O-DU properly subscribes the default “NETCONF” event stream for all notifications, including alarm notifications. - -This scenario corresponds to the following clause in [3]: - -- 9.1.7 Notification framework - -##### B. Test Entrance Criteria - -The minimum functions of the TED described in clause 2.2 that support validation of the M-Plane are operational, configured and connected to the O-DU - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The tests for NETCONF call home, NETCONF connection establishment, and NETCONF capability discovery are successfully completed. The TED NETCONF Server has indicated its support for “Notifications” via the NETCONF Hello message. - -###### b. Procedure - -1. The O-DU NETCONF Client triggers the subscription to the TED NETCONF Server to subscribe to the default “NETCONF” event stream for all notifications that the TED NETCONF Server can generate (including alarm notifications), using either of the following two forms of **create-subscription** RPC: - -``` - - - NETCONF - - -``` - -or - -``` - - - - -``` - -NOTE 1: message-id = “0” in only an example in the above RPC - -NOTE 2: According to RFC 5277, is an optional parameter of **create-subscription**. If it is not present, events in the default NETCONF stream will be sent. - -2. The TED NETCONF Server responds with - -``` - - - -``` - -to the O-DU NETCONF Client. - -NOTE: RFC 6241 is followed for NETCONF communication. - -##### D. Test Requirement (expected result) - -DUT passes this test, if step 1 is performed after all initial conditions are met. - -NOTE: There is no specified timeframe within which the DUT is required to perform step 1 following the fulfilment of all initial conditions. - -### 3.1a.3 M-Plane Connection Supervision - -#### 3.1a.3.1 M-Plane connection supervision - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for an O-DU with appropriate group privileges namely “sudo”, “hybrid-odu”, or “carrier”. - -This test validates that the O-DU handles the connection supervision process correctly. This scenario corresponds to clause 6.7, “Monitoring NETCONF connectivity”, in [3]. - -##### B. Test Entrance Criteria - -The minimum functions of the TED described in clause 2.2 are operational, configured, and connected to the O-DU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The call home procedure and the test case notification subscription are successfully completed. - -###### b. Procedure - -1. The TED NETCONF Server sends a supervision notification message to the O-DU NETCONF Client. -2. The O-DU NETCONF Client sends to the TED NETCONF Server with - -``` - - - 60 - 10 - - -``` - -NOTE 1: The values of parameters are examples of message-id, supervision-notification-interval and guard-timer-overhead. - -NOTE 2: O-DU sends supervision-watchdog-reset rpc before supervision-notification-interval+guard-timer expiry. - -3. The TED NETCONF Server sends a reply to the O-DU NETCONF Client. - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - -``` - -NOTE: The values of parameters are examples of message-id and next-update-at. - -4. Steps 1 to 3 are looped for a total of 30 iterations including the first pass through steps 1 to 3. - -NOTE: RFC 6241 is followed for NETCONF communication. - -##### D. Test Requirement (expected result) - -Test scenario step 4 is performed successfully in all iterations. - -### 3.1a.4 Retrieval of Netconf Server's Information Elements - -#### 3.1a.4.1 Retrieval of Netconf Server's Information Elements - -##### A. Test Description and Applicability - -This scenario is MANDATORY for O-DU. - -This scenario validates that the O-DU properly executes a get command, O-DU can pass this test by executing either of the two cases: 'get without filter' or 'get with filter'. - -This scenario corresponds to the following clause in [3]: - -- 6.6 NETCONF capability discovery -- 9.1.2 Retrieve state - -##### B. Test Entrance Criteria - -The minimum functions of the TED described in clause 2.2 that support validation of the M-Plane are operational, configured and connected to the O-DU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The tests for NETCONF call home, notification subscription and supervision connection are successfully completed. - -###### b. Procedure - -1. The O-DU NETCONF Client triggers either or towards the TED NETCONF Server. - -Case i) Example for get-rpc without filter: - -``` - - - - -``` - -Case ii) Examples for get-rpc with subtree and xpath filters: - -NOTE: The O-DU NETCONF Client uses the get RPC together with sub-tree based and XPATH based to recover particular sub-trees from the TED. - -rpc that filters all low-level-rx-endpoints using subtree filter: - -``` - - - - - - - - - - -``` - -``` - - - - -``` - -With xpath filter: - -``` - - - - - - - -``` - -2. Case i) The TED NETCONF Server responds with where contains all information elements that the TED NETCONF Server is able to expose. -Case ii) The TED NETCONF Server responds with where contains details for objects as conforming to the - -NOTE: O-DU NETCONF Client should not crash for empty data tag from TED NETCONF Server. - -##### D. Test Requirement (expected result) - -Test step 1-2 is performed successfully. - -### 3.1a.5 Fault Management - -This test case is not addressed in the current document. - -### 3.1a.6 Software Update - -#### 3.1a.6.1 Software Update and Install - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for O-DU with appropriate group privileges namely, “sudo”, “nms” or “swm”. - -This test validates that the O-DU can successfully perform a software download and software install procedure. - -This scenario corresponds to the following clause in [3]: - -- 8. Software Management - -##### B. Test Entrance Criteria - -The minimum functions of the TED described in clause 2.2 that support validation of the M-Plane are operational, configured and connected to the O-DU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clauses 3.1a.2.1 and 3.1a.4.1 is successfully completed. -2. A correct and internally consistent SW package is available for test purposes. - -3. The TED NETCONF Server provides at least one slot available for SW update procedure. The status of this slot is {active = false, running = false, access = READ-WRITE} -4. A sFTP/FTPS server is available with an account for the SW update procedure on the O-DU, using FTPS if the NETCONF Server controller is using NETCONF/TLS to configure the TED. -5. TED NETCONF server has not exposed build-content-download. -6. Based on the O-DU implementation, software update and installation may be tested either during the “start-up” procedure (e.g., the TED is not running the desired SW package of the DUT) or alternatively initiated via a manual/automation trigger (e.g., DUT receives a command from the TED). - -###### b. Procedure - -1. The O-DU NETCONF Client triggers . The TED NETCONF Server responds with as STARTED. - -An example rpc for software-download: - -``` - - - - sftp://oranuser@192.168.3.13:22/software.zip - - -``` - -``` - - STARTED - -``` - -2. The TED NETCONF Server performs a software download procedure. When the download is completed, the TED NETCONF Server sends with status COMPLETED to O-DU NETCONF Client - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - sftp://oranuser@192.168.3.13:22/software.zip - COMPLETED - - -``` - -3. The O-DU NETCONF Client triggers informing the TED NETCONF Server about the desired slot for installation. This slot must have the attributes active = FALSE, running = FALSE, access = READ-WRITE. The TED NETCONF Server responds with with status STARTED. - -An example rpc for software-install: - -``` - - - "SLOT0" - "testpkg" - - -``` - -``` - - STARTED - -``` - -4. The TED NETCONF Server sends to the O-DU NETCONF Client. Field contains the value COMPLETED to indicate the successful installation of software to the desired slot. - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - SLOT0 - COMPLETED - - -``` - -##### D. Test Requirement (expected result) - -1. Test steps 1-5 completed successfully, where DU sends software install after software download. - -### 3.1a.7 Software Activation - -#### 3.1a.7.1 Software Activation - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for O-DU with appropriate group privileges namely, “sudo”, “nms” or “swm”. - -This test validates that the O-DU can successfully perform activate software. - -This scenario corresponds to the following clause in [3]: - -- 8. Software Management - -##### B. Test Entrance Criteria - -The minimum functions of the TED described in clause 2.2 that support validation of the M-Plane are operational, configured and connected to the O-DU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1a.6.1 is successfully completed. -2. Based on the O-DU implementation, software activation may be tested either during the “start-up” procedure or alternatively initiated via a manual/automation trigger (e.g., DUT receives a command from the TED). - -###### b. Procedure - -1. The O-DU NETCONF Client triggers towards the TED NETCONF Server. The name of a slot containing a valid software installation to be activated is provided as a parameter in the RPC. - -An example rpc for software-activate - -``` - - - SLOT0 - - -``` - -2. The TED NETCONF Server responds with as STARTED. - -``` - - STARTED - -``` - -3. The TED NETCONF Server sends with a status COMPLETED and the slot-name in the activation event corresponds to the slot-name used in the software-activate RPC to the O-DU NETCONF Client. - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - "SLOT0" - COMPLETED - - -``` - -4. The O-DU NETCONF Client sends to the TED NETCONF Server. - -``` - -``` - -5. The TED NETCONF Server responds with rpc-reply. - -``` - -``` - -##### D. Test Requirement (expected result) - -1. Steps 1-5 are completed successfully - -### 3.1a.8 Access Control - -#### 3.1a.8.1 Sudo on M-plane Architecture Models - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for an O-DU supporting the Hybrid M-plane architecture model with “sudo” or “hybrid-odu” group privileges, or Hierarchical M-plane architecture model with “sudo” privileges. - -This test validates that O-DU can correctly configure users applying the user management model. - -This scenario corresponds to the following clauses in [3]: - -- 6.4 NETCONF Connection Establishment -- 6.5 NETCONF Access Control - -##### B. Test Entrance Criteria - -The minimum functions of the TED described in clause 2.2 that support validation of the M-Plane are operational, configured and connected to the O-DU. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1a.1.1 (IPv4/SSH) or 3.1a.1.3 (IPv6/SSH) or 3.1a.1.5 (IPv4/TLS) or 3.1a.1.7 (IPv6/TLS) is successfully completed. -2. Based on the O-DU implementation, new user account creation may be tested either during “start-up” procedure or alternatively initiated via a manual/automation trigger (e.g., DUT receives a command from the TED) to configure new user accounts. - -###### b. Procedure - -1. The O-DU NETCONF Client establishes a connection with the TED NETCONF Server. -2. The O-DU NETCONF Client configures sudo user account and password using o-ran-user.mgmt.yang. The ‘nms’, ‘fm-pm’, ‘swm’, ‘carrier’ and ‘hybrid-odu’ privilege groups can optionally be configured. - -NOTE 1: For new user accounts which are CERTIFICATE, leaf shall not be present. - -``` - - - - - - merge - - - - MPLANEUSER0 - PASSWORD - 12345678 - true - - - - - - - - - -``` - -3. The O-DU NETCONF Client configures user account to group mappings for the one or two new accounts using ietf-netconf-acm.yang with sudo privilege. The ‘nms’, ‘fm-pm’, ‘swm’, ‘carrier’ and ‘hybrid-odu’ privilege groups can be mapped if created in step 2. - -``` - - - - - - - -``` - -``` - -
- merge - - - - - sudo - MPLANEUSER0 - - - - - - - -``` - -4. The TED NETCONF Server confirms the operations for the above transactions with below rpc-reply - -``` - - - - - -``` - -##### D. Test Requirement (expected result) - -Step 1 to 4 is correctly validated. - -### 3.1a.9 Netconf Server Configurability - -#### 3.1a.9.1 Netconf Server Configurability Test - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for O-DU with either "sudo" or "hybrid-odu" access privileges. - -This test validates that O-DU configures NETCONF Server as per its module-capabilities and user-plane-configuration. - -This scenario corresponds to the following clauses in [3]: - -- 9 Configuration Management -- 15.2 User plane message routing - -##### B. Test Entrance Criteria - -The minimum functions of the TED described in clause 2.2 that support validation of the M-Plane is operational, configured and connected to the O-DU. - -##### C. Test Methodology - -###### a. Initial Condition - -1. The test procedure described in clause 3.1a.4.1 is successfully completed, including retrieval of module-capabilities and uplane-configuration of TED Netconf Server. -2. This test scenario is validated as part of Start-up procedure. -3. The O-DU is configured to setup a cell in the TED. - -4. The TED acts as radio, hence DU creates processing-elements, tx/rx-array-carriers, low-level-tx/rx-endpoints, low-level-tx/rx-links as per module-capabilities and user-plane-configuration of TED. - -###### **b. Procedure** - -The RPCs in below steps are examples and are expected to vary for different equipment or configurations. The number of steps in the procedure might vary depending on the DU implementation of edit-config. - -1. The O-DU NETCONF Client triggers to create VLAN Interface for CU-Plane. - -``` - -rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1"> - - - - - merge - - - - cuplane0 - ianaift:l2vlan - A0:CE:C8:17:7A:41 - 1 - - - - - - -``` - -2. The TED NETCONF Server responds with a ok and Netconf config change notification. - -``` - - - - - - YYYY-MM-DDTHH:MM:SS.FZ - - - 2 - oranuser - - running - - /o-ran-uplane-conf:user-plane-configuration - merge - - - - -``` - -</notification> - -3. The O-DU NETCONF Client triggers to create processing-elements. - -``` - - - - - - merge - - - ETH-INTERFACE - - processing-element01 - - cuplane0 - - A0:CE:C8:17:7A:41 - 1 - 0a:00:27:00:00:0d - - - - - - - -``` - -4. TED NETCONF Server repeats Step-2. - -5. The O-DU NETCONF Client creates low-level-tx/rx-endpoints, e-axc-ids, tx/rx-array-carriers, low-level-tx/rx-links. The O-DU NETCONF Client triggers with configuration data aligned with TED module capabilities and user-plane-configuration data. - -``` - - - - - - merge - - - - low-level-tx-endpoint-0 - - STATIC - 14 - 15 - - - - - - -``` - -``` - -193 -NORMAL -88 -72 --3276 - - KHZ_30 - 273 - - - 49152 - 16128 - 240 - 15 - 0 - - - - low-level-rx-endpoint-0 - - STATIC - 14 - 15 - - 193 - NORMAL - 88 - 72 - -3276 - - KHZ_30 - 273 - - - KHZ_30 - 21 - - - 49152 - 16128 - 240 - 15 - 0 - - false - - - TxArrayCarrier0 - -``` - -``` - - 643334 - 3550000000 - 1000000000 - 28.5 - 2394880 - 360 - - - RxArrayCarrier0 - 643334 - 3550000000 - 1000000000 - 2394880 - 360 - 0.0 - 25600 - - - LowLevelTxLink0 - processing-element01 - TxArrayCarrier0 - Low-Level-Tx-Endpoint-0 - - - LowLevelRxLink0 - processing-element01 - RxArrayCarrier0 - Low-Level-Rx-Endpoint-0 - - - - - - -``` - -6. If the data aligns with the TED NETCONF Server module-capabilities and uplane-configuration, the TED responds with a ok message indicating successful completion of requested procedure. Netconf config change notification is generated from TED NETCONF Server similar to Step-2. - -``` - - - - - -``` - -##### D. Test Requirement (expected result) - -Test steps 1-6 are performed successfully. - -## 3.1a.10 ALD Communications - -#### 3.1a.10.1 ALD Communications Test - -##### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY for O-DU, if the O-DU supports ALD control. - -The purpose of the test is to validate proper RPCs exchange between O-DU and TED NETCONF Server. - -This scenario corresponds to the following clause in [3]: - -- 14.4 Operational aspects of Antenna Line Devices - -##### B. Test Entrance Criteria - -- The minimum functions of the TED described in clause 2.2 that support validation of the M-Plane are operational, configured and connected to the O-DU. -- The TED is compliant with the following specifications: - 1. ISO/IEC 13239:2002 “High-level data link control (HDLC) procedures” - 2. Antenna Interface Standards Group AISG 2.0 (2006): "Control interface for antenna line devices" - 3. 3GPP TS 37.462 (V15.2.0): "Iuant interface: Signalling transport" -- ALD parameters like device type, vendor-code, etc. can be configured in the TED. -- The RPCs and flow might vary according to the O-DU implementation. - -##### C. Test Methodology - -###### a. Initial Conditions - -1. The test procedure described in clause 3.1a.4.1 is successfully completed. -2. A manual/automation trigger (e.g., DUT receives a command from the TED) to initiate ALD procedure. - -###### b. Procedure - -- 1) O-DU NETCONF Client triggers DC voltage on desired ALD ports using rpc to TED NETCONF Server. - -``` - - - - - - merge - - - - port1 - true - - - - - -``` - -``` - -``` - -- 2) TED NETCONF Server responds with rpc-reply - -``` - -``` - -- 3) After DC is turned on, O-DU waits for at least 3s -- 4) O-DU NETCONF Client sends regular RPC messages with “ald-req-msg” record to TED NETCONF Server. -- 5) O-DU NETCONF Client triggers rpc for Device Scan to TED NETCONF Server. - -``` - - - 1 - FFBF81F01001035811150303FF17FF - - -``` - -- 6) TED NETCONF Server responds with as ACCEPTED and a . The ald-resp-msg contains complete unique-id, vendor code and device type of the scanned ALD. (see TS 37.462 for more information) - -``` - - - 1 - ACCEPTED - - 00BF - 81F00F01065859075BCD1506025859040101 - -``` - -- 7) The O-DU NETCONF Client triggers the Address Assignment ALD request RPC to TED NETCONF Server to assign HDLC address to Secondary Device (ALD) (see TS 37.462 for more information) - -``` - - - 1 - FF BF 81 F0 0F 01 06 58 59 07 5b CD 15 06 02 58 59 02 01 17 - - - -``` - -- 8) The TED NETCONF Server responds with Secondary Device information if available and matched with the unique id, vendor code and device type if provided in the ald-req-msg. - -``` - - - 1 - ACCEPTED - 17 BF 81 F0 0B 01 06 58 59 07 5b - CD 15 04 01 01 - - -``` - -``` - - - - -``` - -(Here, HDLC Address 17 has been assigned to ALD with Unique ID: 5859075BCD15 and Device type : 01 which is single-antenna RET) - -- 9) The O-DU NETCONF Client triggers the SNRM RPC to TED NETCONF Server for ALD Link establishment. (See ISO/IEC 13239 for more information) - -``` - - - - 1 - 17 93 - - - -``` - -The TED NETCONF Server responds with UA message with status ACCEPTED. - -``` - - - - 1 - ACCEPTED - 17-CE 73 - - - -``` - -- 10) The O-DU NETCONF Client sends a get information elementary procedure message to get details of the RET device with respective procedure-id. The O-DU NETCONF Client triggers the I-frame RPC to TED NETCONF Server. - -``` - - - - 1 - 17 10 05 00 - - - -``` - -- 11) The TED NETCONF Server responds with Secondary Device/ALD information with status ACCEPTED and ald-resp-msg. - -``` - - - - 1 - ACCEPTED - 17 10 05 01 00 04 58 59 30 31 04 -41 42 30 31 00 00 - - - -``` - -NOTE : common get-information elementary procedure referred from ETSI TS 125 463. - -- 12) O-DU NETCONF Client disconnects the HDLC link established for secondary devices by sending DISC command. (See ISO/IEC 13239 for more information) - -NOTE: There is no time constraint for DU to disconnect the secondary device. - -``` - - - 0 - 17 53 - - -``` - -- 13) TED NETCONF Server responds with UA message with status ACCEPTED. - -``` - - - 0 - ACCEPTED - 17 73 - - -``` - -#### D. Test Requirement (expected result) - -Proper rpcs are exchanged between O-DU NETCONF Client and TED NETCONF Server. - -### 3.1a.11 Log Management - -#### 3.1a.11.1 Troubleshooting Test - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for O-DU that supports troubleshooting log management. - -The test is applicable for DU with appropriate access privileges, namely “sudo”, “nms” or “fm-pm”. - -This test validates the capability of the O-DU to handle troubleshooting logs including alarm information. - -This scenario corresponds to the following clause in [3]: - -- 14.2.2 Troubleshooting Log Management - -##### B. Test Entrance Criteria - -The minimum functions of the TED described in clause 2.2 that support validation of the M-Plane are operational, configured and connected to the O-DU. - -## C. Test Methodology - -### a. Initial Conditions - -1. The test procedure described in clauses 3.1.a.2.1 and 3.1.a.4.1 is successfully completed. -2. A manual/automation trigger (e.g., DUT receives a command from the TED) to initiate troubleshooting log procedure - -### b. Procedure - -1. The O-DU NETCONF Client sends to the TED NETCONF Server. The TED NETCONF Server responds with . - -``` - - - - - - SUCCESS - -``` - -2. The TED NETCONF Server starts generating one or more file(s) containing troubleshooting logs. When the generation of the log file(s) are completed, the TED NETCONF Server sends with a list of one or more log file names to the O-DU NETCONF Client. - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - o-ran/log/Troubleshootinglog.gz - - -``` - -3. The O-DU NETCONF Client sends log-file-name to the TED NETCONF Server to start uploading the log file(s). The TED NETCONF Server responds with with status SUCCESS. - -``` - - - - o-ran/log/Troubleshootinglog.gz - - sftp://oranuser@192.168.3.13:22/local/log - - 1234 - - - - - - SUCCESS - - -``` - -4. The TED NETCONF Server uploads the log file(s) to NETCONF Client by sFTP/FTPES, using FTPES if the NETCONF Server controller is using NETCONF/TLS to configure the TED. When file upload is completed, the TED NETCONF Server sends with status SUCCESS. - -``` - - - YYYY-MM-DDTHH:MM:SS.FZ - - o-ran/log/Troubleshootinglog.gz - sftp://oranuser@192.168.3.13:22/local/log - - SUCCESS - - - -``` - -#### D. Test Requirement (expected result) - -Test steps 1-4 are performed successfully. - -### 3.1a.11.2 Trace Test - -#### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for O-DU that supports trace log management. - -The test is applicable for DU with appropriate access privileges, namely “sudo”, “nms” or “fm-pm”. - -This test validates the capability of the O-DU to handle trace logs. - -This scenario corresponds to the following clause in [3]: - -- 14.3 Trace - -#### B. Test Entrance Criteria - -The minimum functions of the TED described in clause 2.2 that support validation of the M-Plane are operational, configured and connected to the O-DU. - -## C. Test Methodology - -### a. Initial Conditions - -1. The test procedure described in clauses 3.1a.2.1 and 3.1a.4.1 is successfully completed. -2. A manual/automation trigger (e.g., DUT receives a command from the TED) to initiate trace log procedure - -### b. Procedure - -1. The O-DU NETCONF Client sends to the TED NETCONF Server. The TED NETCONF Server responds with . - -``` - - - -``` - -``` - - SUCCESS - -``` - -2. The TED NETCONF Server starts generating one or more file(s) containing trace logs. When the generation of the log file(s) are completed, the TED NETCONF Server sends and set as false with a list of one or more log file names to the O-DU NETCONF Client. - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - o-ran/log/TraceLog.gz - false - - -``` - -3. The O-DU NETCONF Client sends log-file-name to the TED NETCONF Server to start uploading the log file(s). The TED NETCONF Server responds with with status SUCCESS. - -``` - - - o-ran/log/TraceLog.gz - sftp:// - oranuser@192.168.3.13:22/local/log - - 1234 - - - -``` - -``` - - SUCCESS - -``` - -4. The TED NETCONF Server uploads the log file(s) to NETCONF Client by sFTP/FTPES, using FTPES if the NETCONF Server controller is using NETCONF/TLS to configure the TED. When file upload is completed, the TED NETCONF Server sends with status SUCCESS. - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - o-ran/log/TraceLog.gz - sftp://oranuser@192.168.3.13:22/local/ - log - SUCCESS - - -``` - -5. The O-DU NETCONF Client sends to the TED NETCONF Server. The TED NETCONF Server responds with . - -``` - - - -``` - -``` - - SUCCESS - -``` - -6. The O-DU NETCONF Client can wait for the notification from the TED NETCONF Server. The TED NETCONF Server sends and set to true. - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - o-ran/log/TraceLog.gz - true - - -``` - -7. The O-DU NETCONF Client sends log-file-name to the TED NETCONF Server to start uploading the remaining log file(s). The TED NETCONF Server responds with with status SUCCESS. - -``` - - -``` - -``` - - o-ran/log/TraceLog.gz - sftp:// -oranuser@192.168.3.13:22/local/log - - 1234 - - - - - - SUCCESS - - -``` - -8. The TED NETCONF Server uploads the remaining log file(s) to NETCONF Client by sFTP/FTPES, using FTPES if the Netconf Server controller is using NETCONF/TLS to configure the TED. When file upload is completed, the TED NETCONF Server sends with status SUCCESS. - -``` - - - YYYY-MM-DDTHH:MM:SS.FZ - - o-ran/log/TraceLog.gz - sftp://oranuser@192.168.3.13:22/local/ -log - SUCCESS - - - -``` - -#### D. Test Requirement (expected result) - -Test step 1-8 are performed successfully. - -### 3.1a.12 Connectivity Check - -#### 3.1a.12.1 Ethernet Connectivity Monitoring - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY if the O-DU supports C-Plane and U-Plane connectivity over Ethernet. - -This test validates the proper operation of LBM. - -This scenario corresponds to the following clauses in [3]: - -- 7.3 C/U Plane VLAN configuration -- 7.5 Definition of processing elements -- 7.6.1 C/U-Plane transport connectivity verification - -## B. Test Entrance Criteria - -1. The minimum functions of the TED described in clause 2.2 that support validation of the M-Plane are operational, configured and connected to the O-DU. -2. Result validation of this test requires TED capabilities such as a network sniffer that allows for traffic analysis over ETH frames between O-DU and TED. - -## C. Test Methodology - -### a. Initial Conditions - -1. The test procedure described in clauses 3.1a.4.1 and 3.1a.9.1 are successfully completed. -2. Based on the O-DU implementation, Ethernet Connectivity Monitoring may be tested either during the “start-up” procedure or alternatively initiated via a manual/automation trigger (e.g., DUT receives a command from the TED) - -### b. Procedure - -1. The O-DU NETCONF Client configures a transport-flow in the processing element: a combination of VLAN identity, O-DU MAC address and O-RU MAC address. -2. The O-DU sends loopback message to the O-RU (TED) MAC address configured for the processing element. -3. The TED sends loopback responses to the O-DU MAC Address of the loopback message. - -## D. Test Requirement (expected result) - -Packets are sent correctly in step 2 and 3. - -## 3.1a.12.2 UDP Echo Test - -### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY if the O-DU supports C-Plane and U-Plane sessions over IP. - -This test validates the proper operation UDP Echo for continuous verification of connectivity. - -This scenario corresponds to the following clauses in [3]: - -- 7.4 O-RU C/U Plane IP Address Assignment -- 7.5 Definition of processing elements -- 7.6 O-DU Verification of C/U Plane Transport Connectivity - -## B. Test Entrance Criteria - -1. The minimum functions of the TED described in clause 2.2 that support validation of the M-Plane are operational, configured and connected to the O-DU. -2. Result validation of this test requires TED capabilities such as a network sniffer that allows for traffic analysis over ETH frames between O-DU and TED. - -## C. Test Methodology - -### a. Initial Conditions - -1. The test procedure described in clauses 3.1a.4.1 and 3.1a.9.1 are successfully completed. -2. Based on the O-DU implementation, UDP Echo Test may be tested during the “start-up” procedure or alternatively initiated via a manual/automation trigger (e.g., DUT receives a command from the TED). - -### b. Procedure - -1. The O-DU NETCONF Client configures IP information and udpip-flow in the processing element for the C-Plane and U-Plane communications. -2. The O-DU NETCONF Client configures the enable-udp-echo leaf = true in the udp-echo YANG model to be enabled operation of the UDP echo server in the TED. -3. The O-DU NETCONF Client sends a UDP datagram to UDP port number:7 of the TED NETCONF Server. -4. The TED NETCONF Server sends back the UDP datagram to the O-DU NETCONF Client. -5. The O-DU NETCONF Client configures the enable-udp-echo leaf = false in the udp-echo YANG model to be disabled operation of the UDP echo server in the TED - -**D. Test Requirement (expected result)** - -Packets are sent correctly in step 3 and 4. - -### 3.1a.13 Energy Savings - -#### 3.1a.13.1 M-Plane based TRX control - -**A. Test Description and Applicability** - -This scenario is CONDITIONAL MANDATORY for O-DU. The test is executed if the O-DU supports M-Plane based TRX-control. - -This test validates M-plane based TRX control. - -This scenario corresponds to the following clause in [3]: - -- 20.3.2 TRX control – M-Plane controlled -- 10.2 Measurement activation and de-activation - -**B. Test Entrance Criteria** - -The minimum functions of the TED described in clause 2.2 that support validation of the M-Plane are operational, configured and connected to the O-DU - -**C. Test Methodology** - -**a. Initial Conditions .** - -1. The TED NETCONF Server exposes the capability to support energy saving -2. The TED NETCONF Server exposes the capability to support MPLANE-TRX-CONTROL -3. The antenna mask is set to enable all array-elements. -4. A manual/automation trigger (e.g., DUT receives a command from the TED) to initiate M-Plane based TRX Control. - -**b. Procedure** - -1. The O-DU NETCONF client sets the value of antenna mask for the [tr]x-array. It is recommended to set at least half of the antenna mask off in order to have more differentiable power changes. -2. For the case where the TED NETCONF Server advertises mplane-supported-trx-control-masks list, RPC edit-config shall be used to configure a specific antenna mask value by specifying a given antenna-bitmask-index for the [tr]x-array using the YANG parameter [tr]x-array-antenna-mask-config. - -EXAMPLE-1: configuration of a given 32-bit tx antenna mask by specifying the antenna-index 1, which points to an antenna mask that has half ones and the other half zeros: - -``` - - - - - - - - - - tx-array-1 - - 1 - - - - - - - - -``` - -For the case where the TED NETCONF Server does not advertise mplane-supported-trx-control-masks list for a given [tr]x-array, the RPC edit-config shall be used to configure a specific antenna-bitmask value for the [tr]x-array using the YANG parameter [tr]x-array-antenna-mask-config. - -EXAMPLE-2: configuration of a 32-bit tx antenna mask is shown below: - -``` - - - - - - - - - - tx-array-1 - - 1111111100000000000000000011111111 - - - - - - - - -``` - -- The TED NETCONF Server responds with a message indicating successful completion of requested procedure. - -For Example, - -``` - - - - - - - -``` - -4. The O-DU NETCONF Client waits for mplane-trx-control-ant-mask-update notification. - -EXAMPLE-1: mplane-trx-control-ant-mask-update notification by specifying the antenna-index is shown below: - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - tx-array-1 - tx-array - 1 - - -``` - -EXAMPLE-2: mplane-trx-control-ant-mask-update notification by specifying antenna mask is shown below: - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - tx-array-1 - tx-array - 1111111100000000000000000011111111 - - -``` - -5. The O-DU NETCONF client resets the value of antenna mask for the [tr]x-array. - -For the case where the TED NETCONF Server advertises mplane-supported-trx-control-masks list, RPC edit-config shall be used to configure a specific antenna mask value by specifying a given antenna-bitmask-index for the [tr]x-array using the YANG parameter [tr]x-array-antenna-mask-config. - -EXAMPLE-1: configuration of a given 32-bit tx antenna mask by specifying the antenna-index 5 which points to all-ones antenna mask: - -``` - - - - - - - - tx-array-1 -``` - -``` - - 5 - - - - - -``` - -For the case where the TED NETCONF server does not advertise mplane-supported-trx-control-masks list for a given [tr]x-array, the RPC edit-config shall be used to configure a specific antenna-bitmask value for the [tr]x-array using the YANG parameter [tr]x-array-antenna-mask-config. - -EXAMPLE-2: configuration of a 32-bit tx antenna mask is shown below: - -``` - - - - - - - - - - - tx-array-1 - - 11111111111111111111111111111111 - - - - - - -``` - -- The TED NETCONF Server responds with a message indicating successful completion of requested procedure. - -For Example, - -``` - - - - - - - -``` - -- The O-DU NETCONF client waits for mplane-trx-control-ant-mask-update notification. - -For Example, - -EXAMPLE 1: mplane-trx-control-ant-mask-update notification by specifying the antenna-index is shown below: - -``` - - - -``` - -``` - -YYYY-MM-DDTHH:MM:SS.FZ - - tx-array-1 - - tx-array - - 5 - - - -``` - -EXAMPLE-2: `mplane-trx-control-ant-mask-update` notification by specifying antenna mask is shown below: - -``` - - - YYYY-MM-DDTHH:MM:SS.FZ - - tx-array-1 - - tx-array - - 11111111111111111111111111111111 - - - - - -``` - -#### B. Test Requirement (expected result) - -Test steps above are performed successfully. - -### 3.1a.13.2 Deep-hibernate - -#### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for O-DU. The test is executed if the ~~TED/O-RU~~ O-DU supports M-Plane based deep-hibernate control. - -This test validates deep-hibernation. - -This scenario corresponds to the following clause in [3]: - -- 20.5 Deep-hibernate - -#### B. Test Entrance Criteria - -The minimum functions of the TED described in clause 2.2 that support validation of the M-Plane are operational, configured and connected to the O-DU - -#### C. Test Methodology - -##### a. Initial Conditions - -1. The test procedure described in clause 3.1a.9.1 is successfully completed . - -2. The TED NETCONF Server exposes the capability to support energy savings including DEEP-HIBERNATE -3. A manual/automation trigger (e.g., DUT receives a command from the TED) to initiate deep-hibernation procedure. - -**b. Procedure** - -1. The O-DU NETCONF Client sends rpc for module-capabilities. -2. The TED NETCONF Server responds with with module-capabilities data including min-hibernate-time-duration and max-hibernate-time-duration -3. The O-DU NETCONF Client sends deep-hibernate rpc command with a hibernate-time withing the range of TED module-capabilities. - -For Example, - -``` - - - - - - - - - 15 - - - - - - -``` - -4. The TED NETCONF Server responds with a message indicating successful completion of requested procedure. - -For Example, - -``` - - - -``` - -5. The O-DU NETCONF Client waits for deep-hibernate-activated notification. - -For Example, - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - - 15 - - - -``` - -6. The TED NETCONF Server starts deep-hibernate timer. -7. The O-DU NETCONF Client sends close-session rpc command. - -For Example, - -``` - - - -``` - -8. The TED NETCONF Server restarts after the expiry of hibernate-time. -9. After restart, the O-DU Netconf Client verifies restart-cause value is DEEP-HIBERNATE-RESTART. - -#### D. Test Requirement (expected result) - -Test steps above are performed successfully. - -### 3.1a.13.3 Data layer control - -#### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY for O-DU. The test is executed if the O-DU supports M-Plane based Data layer control. - -This test validates Data layer control. - -This scenario corresponds to the following clause in [3]: - -- 20.3.3 Data layer control -- 10.2 Measurement activation and de-activation - -#### B. Test Entrance Criteria - -The minimum functions of the TED described in clause 2.2 that support validation of the M-Plane are operational, configured and connected to the O-DU. - -#### C. Test Methodology - -##### a. Initial Conditions - -1. The test procedure described in clause 3.1a.9.1 is successfully completed -2. The TED NETCONF Server exposes the capability to support energy savings including MPLANE-DATA-LAYER-CONTROL -3. A manual/automation trigger (e.g., DUT receives a command from the TED) to initiate data layer control procedure. - -##### b. Procedure - -1. The O-DU NETCONF Client turns off data layers by adding energy-sharing-group-id into energy-sharing-groups-disabled leaf-list parameter. - -For Example, - -``` - - - - - - - 4 -``` - -``` - - - - - -``` - -2. The TED NETCONF Server updates energy-sharing-groups-disabled and responds with a message indicating successful completion of requested procedure. - -For Example, - -``` - - - - - -``` - -3. The O-DU NETCONF Client waits for 10 seconds. -4. The O-DU NETCONF Client turns on data layers by removing energy-sharing-group-id from energy-sharing-groups-disabled leaf-list parameter - -For Example, - -``` - - - - - - - - 4 - - - - -``` - -5. The TED NETCONF Server responds with a message indicating successful completion of requested procedure. - -For Example, - -``` - - - - - -``` - -6. The O-DU NETCONF Client waits for data-layer-control-wakeup-notification. - -Example, - -``` - - - YYYY-MM-DDTHH:MM:SS.FZ - - 4 - - - -``` - -#### D. Test Requirement (expected result) - -Test steps above are performed successfully. - -## 3.2 UC-Plane Measurements O-RU - -### 3.2.1 UC-Plane Standard Test Definitions - -The following clauses describe test scenarios for equipment implementing the U-Plane and C-Plane O-RAN option 7.2x protocols. - -#### 3.2.1.1 UC-Plane Measurements, O-RU TEST SCENARIO - -In these sets of tests, the Device Under Test (DUT) is the O-RU. - -This document describes conformance tests for 4 scenarios: - -1. Conducted FDD tests for FR1 radios -2. Non-conducted (OTA) FDD tests for FR1 radios -3. Conducted TDD tests for FR1 radios -4. Non-conducted tests for TDD FR1 and FR2 radios - -The O-RU must only be tested for the scenarios that apply to the O-RU capabilities. The fact that there are 4 scenarios defined does not imply that every O-RU must be tested for all scenarios in order to be O-RAN compliant and consequently the O-RU does not have to support all the capabilities required to test all 4 scenarios (i.e. support of FR1, FR2, TDD, FDD, conducted and non-conducted). In other words, depending on whether the O-RU supports capabilities such as FDD, TDD, FR1 and or FR2, only the corresponding scenarios that match the O-RU capabilities will apply. For example, an O-RU that does not have or cannot provide access to antenna ports (or TAB connectors), supports TDD and operates at FR2 bands, the corresponding scenario that the O-RU will need to be tested to be O-RAN conformant is scenario #4 only. Another example, for an O-RU that supports FDD, operates at FR1 bands and has or can provide access to antenna ports (or TAB connectors), scenarios #1 or #2 can apply but only one of the two possible scenarios will be selected to test the O-RU for O-RAN conformance. - -For scenario #1 and #3 above the RF test setup is as described in ETSI TS 138.141-1[NR] and TS 136.141 [LTE]. For scenarios #2 and #4 the RF test setup is as described in TS 138.141-2. Note that O-RAN conformance testing is expected to be “off-line” and not to be run while an O-DU and/or O-RU is operating and serving actual users. The O-RU manufacturer must also make available the same declarations described in ETSI TS 138.141-1, TS 138.141-2 [NR] and TS 136.141 [LTE] Section 4.6. This will determine the radio’s support for multi-carrier operation (e.g. if multi-carrier operation is supported on different connectors) - -Since the purpose of this document is to test O-RAN Fronthaul conformance and not to duplicate 3GPP RF tests, only selected parts of TS 138.141-1, TS 138.141-2 [NR] and TS 136.141 [LTE] will be used for RF testing. These selected test features are only necessary to test whether the O-RU correctly interpreted and generated the O-RAN C-Plane and U-Plane messages correctly. Several testcases require a bandwidth that may not be supported by the O-RU. In such situation, the testcase should be executed by adjusting to a bandwidth that is supported by the O-RU and complies with the channel bandwidth listed in either TS 138.104 clause 5.3.2 for NR or TS 136.104 clause 5.6 for LTE. The adjustment of the bandwidth can be done by reducing the number of physical resource blocks or by selecting another FRC. The bandwidth adjustment may select the minimum bandwidth defined by 3GPP. The adjustment of the bandwidth does not require the execution of the same testcase again with a larger bandwidth. - -There will also be some additions to the test waveforms used in TS 138.141-1, TS 138.141-2 [NR] and TS 136.141 [LTE] to fully exercise the features of the O-RAN Fronthaul protocol. These selected parts and additions are summarized below: - -### 3.2.1.1.1 For scenario #1 (Conducted FDD tests for FR1 radios) - -- For downlink tests for type 1-C radios (radios with antenna port connectors and passive antennas) the test configuration described in TS 138.141-1 D.1.1 will be used. Only a single antenna port will be used unless the test explicitly requires more than one port and the radio supports more than one port. RF test equipment will be connected at the point described in TS 138.141-1 clause 4.2.1. Note that an antenna port is an electrical conducting port that is connected to an array element. -- For uplink tests for type 1-C radios (radios with antenna port connectors and passive antennas) the test configuration described in TS 138.141-1 D.2.1 will be used. Only a single antenna port will be used unless the test explicitly requires more than one port and the radio supports more than one port. RF test equipment will be connected at the point described in TS 138.141-1 clause 4.2.1. Note that an antenna port is an electrical conducting port that is connected to an array element. -- For downlink tests for type 1-H radios (radios with TAB connectors and active antenna systems) the test configuration described in TS 138.141-1 D.3.1 will be used for conducted tests. Only a single TAB connector will be used unless the test explicitly requires more than one connector. RF test equipment will be connected at the point described in TS 138.141-1 clause 4.2.2. Note that a transceiver array boundary (TAB) connector is an electrical conducting port that is connected to an array element via a radio distribution network (RDN). -- For uplink tests for type 1-H radios (radios with TAB connectors and active antenna systems) the test configuration described in TS 138.141-1 D.4.1 will be used for conducted tests. Only a single TAB connector will be used unless the test explicitly requires more than one connector. RF test equipment will be connected at the point described in TS 138.141-1 clause 4.2.2. Note that a transceiver array boundary (TAB) connector is an electrical conducting port that is connected to an array element via a radio distribution network (RDN). -- The basic downlink test will start with the Test model described in NR-FR1-TM1.1 and E-TM1.1. Subsequent tests will adapt this model to test additional features of the O-RAN interface (e.g. Modifying the payload data, blanking some symbols, etc.). Note this test model describes the IQ data contained in the O-RAN packets not the O-RAN specific parameters. This test model will also be augmented with the following O-RAN specific parameters: - -Includes “stock” eAxC values as configured via M-Plane: - -- DU\_Port\_ID: two bits, nominal value 00b -- BandSector: nominal 6 bits, nominal value 000000b -- CC\_ID: nominal 4 bits, nominal value 0000b (most tests invoke only one component carrier) -- RU\_port\_ID: 4 bits, nominal values 0000b through 0011b or to whatever max value needed for a specific test -- If the radio manufacturer declares support for multi-carrier a different eAxC will be assigned for each carrier. Note that most tests described in ETSI TS 138.141-1[NR] and TS 136.141 [LTE] require testing at the bottom, middle and top of the supported bands of the radio. This specification relaxes that requirement because the purpose is to test the fronthaul compliance and not the radio performance. -- **Compression:** Static 16-bit fixed point IQ bitwidth in both DL and UL -- **Beamforming:** no beamforming (beamId = 0x0000), assumed to mean boresight radiation (normal to the antenna surface) at some undetermined beamwidth (recall that beam weight magnitudes must be equal to unity) -- **Transport:** L2 Ethernet, eCPRI with no fragmentation and no QOS -- **Delay Parameters:** The test will be executed with a direct fibre connection to the O-RU and the network delay is considered negligible for the purpose of delay management. Therefore, T12\_min = T12\_max = 0 and T34\_min = T34\_max = 0. - -The radio will report its supported values for: - -- T2a\_min/max\_up -- Ta3\_min/max\_up - -- T2a\_min/max\_cp\_ul -- Tcp\_adv\_dl - -These parameters will be used to calculate the delay windows needed for the delay management tests below. Note that T1a\_min\_up = T2a\_min\_up and T1a\_max\_up = T2a\_max\_up due to the fixed, zero network delay. Similarly, Ta4\_min\_up = Ta3\_min\_up and Ta4\_max\_up = Ta3\_max\_up. Similarly, T1a\_min\_cp\_ul = T2a\_min\_cp\_ul and T1a\_max\_cp\_ul = T2a\_max\_cp\_ul. - -- Uplink tests will start with the basic 3GPP test signal for Fixed Reference Channels for receiver sensitivity and in-channel selectivity as described in ETSI TS 138.141-1[NR] and TS 136.141 [LTE]. All O-RAN specific parameters will be the same as described above for downlink testing. As with downlink testing subsequent tests will build on this basic waveform modifying parameters as needed to exercise O-RAN specific features. -- Uplink tests will be conducted using power levels at least 30dB higher than the power levels used to test 3GPP Receiver sensitivity described in ETSI TS 138.141-1 Table 7.2.5-1[NR] and TS 136.141 [LTE]. This is to ensure a clear signal is received by the O-RU so it can be accurately decoded and demodulated to ensure the correct data was received by the O-DU as was sent by the signal source. Again, the purpose of these tests is to ensure correct operation of the O-RAN fronthaul not to test receiver sensitivity. - -### 3.2.1.1.2 For scenario #2 (Non-conducted OTA FDD tests for FR1 radios) - -- For downlink tests for type 1-H radios that elect to be tested over the air (OTA) rather than conducted, the test configuration is described in TS 138.141-2 E.1.2 where the Test Antenna will be placed inside an OTA chamber and measurements are referenced to the radiated characteristics defined over the air (OTA) at the Radiated Interface Boundary (RIB) defined in TS 138.141-2 4.2-1. The RF analyser test equipment is connected to the Test Antenna and is located outside of the OTA chamber. -- For downlink test for 1-O or 2-O radios (radios with no physical antenna or TAB connectors and consequently only over the air – OTA – measurements are possible) the test configuration is described in TS 138.141-2 E.1.2 where the Test Antenna will be placed inside an OTA chamber and measurements are referenced to the radiated characteristics defined over the air (OTA) at the Radiated Interface Boundary (RIB) defined in TS 138.141-2 4.2-2. The RF analyser test equipment is connected to the Test Antenna and is located outside of the OTA chamber. -- For uplink tests for type 1-H radios that elect to be tested over the air (OTA) rather than conducted, the test configuration is described in TS 138.141-2 E.2.1 where the Test Antenna will be placed inside an OTA chamber and measurements are referenced to the radiated characteristics defined over the air (OTA) at the Radiated Interface Boundary (RIB) defined in TS 138.141-2 4.2-1. The RF generator test equipment is connected to the Test Antenna and is located outside of the OTA chamber. -- For uplink test for 1-O or 2-O radios (radios with no physical antenna or TAB connectors and consequently only over the air (OTA) measurements are possible) the test configuration is described in TS 138.141-2 E.2.1 where the Test Antenna will be placed inside an OTA chamber and measurements are referenced to the radiated characteristics defined over the air (OTA) at the Radiated Interface Boundary (RIB) defined in TS 138.141-2 4.2-2. The RF generator test equipment is connected to the Test Antenna and is located outside of the OTA chamber. -- For downlink tests for LTE radios that elect to be tested over the air (OTA), the test configuration is described in TS 138.141-2 E.1.2 where the Test Antenna will be placed inside an OTA chamber and measurements are referenced to the radiated characteristics defined over the air (OTA) at the Radiated Interface Boundary (RIB) - -defined in TS 138.141-2 4.2-1. The RF analyser test equipment is connected to the Test Antenna and is located out of the OTA chamber. - -- For uplink tests for LTE radios that elect to be tested over the air (OTA), the test configuration is described in TS 138.141-2 E.2.1 where the Test Antenna will be placed inside an OTA chamber and measurements are referenced to the radiated characteristics defined over the air (OTA) at the Radiated Interface Boundary (RIB) defined in TS 138.141-2 4.2-1. The RF generator test equipment is connected to the Test Antenna and is located out of the OTA chamber. -- Note that the chamber shown in TS 138.141-2 E.1.2. and E.2.1. are generic and consequently any OTA chamber could be used, i.e. far field, CATR, near field, reverberation, etc. -- Likewise, depending on the beamforming measurement technology the positioner in TS 138.141-2 E.1.2 and E.2.1. may or may not be needed. -- Furthermore, depending on the beamforming method to be measured more than one test antenna with more than one RF analyser and/or generator ports may also be needed. -- The basic downlink test will start with the Test model described in NR-FR1-TM1.1 and E-TM1.1 in TS 138.141-1 and 36.141 for NR FR1 and LTE radios respectively. Subsequent tests will adapt this model to test additional features of the O-RAN interface (e.g. Modifying the payload data, blanking some symbols, etc.). Note this test model describes the IQ data contained in the O-RAN packets not the O-RAN specific parameters. This test model will also be augmented with the following O-RAN specific parameters: - -Includes “stock” eAxC values as configured via M-Plane: - -- DU\_Port\_ID: two bits, nominal value 00b -- BandSector: nominal 6 bits, nominal value 000000b -- CC\_ID: nominal 4 bits, nominal value 0000b (most tests invoke only one component carrier) -- RU\_port\_ID: 4 bits, nominal values 0000b through 0011b or to whatever max value needed for a specific test -- If the radio manufacturer declares support for multi-carrier a different eAxC will be assigned for each carrier. Note that most tests described in ETSI TS 138.141-2[NR] and TS 136.141 [LTE] require testing at the bottom, middle and top of the supported bands of the radio. This specification relaxes that requirement because the purpose is to test the fronthaul compliance and not the radio performance. -- **Compression:** Static 16-bit fixed point IQ bitwidth in both DL and UL -- **Beamforming:** no beamforming (beamId = 0x0000), assumed to mean boresight radiation (normal to the antenna surface) at some undetermined beamwidth (recall that beam weight magnitudes must be equal to unity) -- **Transport:** L2 Ethernet, eCPRI with no fragmentation and no QOS -- **Delay Parameters:** The test will be executed with a direct fibre connection to the O-RU and the network delay is considered negligible for the purpose of delay management. Therefore, T12\_min = T12\_max = 0 and T34\_min = T34\_max = 0. - -The radio will report its supported values for: - -- T2a\_min/max\_up -- Ta3\_min/max\_up -- T2a\_min/max\_cp\_ul - -- Tcp\_adv\_dl - -These parameters will be used to calculate the delay windows needed for the delay management tests below. Note that T1a\_min\_up = T2a\_min\_up and T1a\_max\_up = T2a\_max\_up due to the fixed, zero network delay. Similarly, Ta4\_min\_up = Ta3\_min\_up and Ta4\_max\_up = Ta3\_max\_up. Similarly, T1a\_min\_cp\_ul = T2a\_min\_cp\_ul and T1a\_max\_cp\_ul = T2a\_max\_cp\_ul. - -- Uplink tests will start with the basic 3GPP test signal for Fixed Reference Channels for receiver sensitivity and in-channel selectivity as described in ETSI TS 138.141-2[NR] and TS 136.141 [LTE]. All O-RAN specific parameters will be the same as described above for downlink testing. As with downlink testing subsequent tests will build on this basic waveform modifying parameters as needed to exercise O-RAN specific features. -- Uplink tests will be radiated using power levels at least 30dB higher than the reference sensitivity power levels used to test 3GPP Receiver sensitivity described in ETSI TS 138.141-2 Table 7.3.5.2-1, Table 7.3.5.2-2 and Table 7.3.5.2-3[NR FR1], Table 7.3.5.3-1 [NR FR2] and TS 136.141 Table 7.2-1 to Table 7.2-12 [LTE]. This is to ensure a clear signal is received by the O-RU so it can be accurately decoded and demodulated to ensure the correct data was received by the O-DU as was sent by the signal source. Again, the purpose of these tests is to ensure correct operation of the O-RAN fronthaul not to test receiver sensitivity. - -### 3.2.1.1.3 For scenario #3 (Conducted TDD Tests for FR1 Radios) - -All provisions of clause 3.2.1.1.1 will apply to FR1 TDD tests however the default test waveform will be a TDD waveform as described in ETSI TS 138.141-1. It will be NR-FR1-TM1.1 (TDD) and G-FR1-A1-5 (SCS30k\_51RB) in the uplink. If the O-RU does not support the UL bandwidth of 51 RB, another FRC test model can be selected. The TDD test model is derived based on the uplink/downlink configurations described in ETSI TS 138.141-1 Table 4.9.2.2.1 using information element *TDD-UL-DL-ConfigCommon* as defined in TS 138.331 for 30 kHz SCS as shown below: - -**Table 3.2.1-1 Configuration Parameters for TDD FR1 Conducted Tests** - -| Field name | | -|----------------------------------------------------|----| -| referenceSubcarrierSpacing (kHz) | 30 | -| Periodicity (ms) for dl-UL-TransmissionPeriodicity | 5 | -| nrofDownlinkSlots | 7 | -| nrofDownlinkSymbols | 6 | -| nrofUplinkSlots | 2 | -| nrofUplinkSymbols | 4 | - -This waveform is shown below: - -![Figure 3.2.1.1-3 NR-FR1-TM1.1 TDD Test Signal. This figure displays four resource grid plots and two text blocks. The top plot shows the Downlink Test Model for FR1 100MHz, μ=1:30kHz, TDD, NR-FR1-TM1.1, with a green background indicating active subcarriers. The middle-left plot shows Downlink resource mapping for DL-SCH1_D (QPSK) with red blocks representing data in symbols 2 and 11. The middle-right plot shows Uplink resource mapping for UL-SCH1_U (QPSK) with red blocks representing data in symbols 2 and 11. The bottom plot shows the Uplink FRG Configuration for FR1 100MHz, G-FR1-A1-5: SCS30k_51RB, TDD, with blue blocks representing active subcarriers. Text blocks for Downlink and Uplink describe the channel types and data distribution across symbols.](aa68758c757955e0598cac82adf6459d_img.jpg) - -Figure 3.2.1.1-3 NR-FR1-TM1.1 TDD Test Signal. This figure displays four resource grid plots and two text blocks. The top plot shows the Downlink Test Model for FR1 100MHz, μ=1:30kHz, TDD, NR-FR1-TM1.1, with a green background indicating active subcarriers. The middle-left plot shows Downlink resource mapping for DL-SCH1\_D (QPSK) with red blocks representing data in symbols 2 and 11. The middle-right plot shows Uplink resource mapping for UL-SCH1\_U (QPSK) with red blocks representing data in symbols 2 and 11. The bottom plot shows the Uplink FRG Configuration for FR1 100MHz, G-FR1-A1-5: SCS30k\_51RB, TDD, with blue blocks representing active subcarriers. Text blocks for Downlink and Uplink describe the channel types and data distribution across symbols. - -Figure 3.2.1.1-3 NR-FR1-TM1.1 TDD Test Signal - -As an alternative to the default test waveform shown in Figure 3.2.1.1-3, it is optional to flexibly use other test waveforms with any TDD configurations allowed by the information element *TDD-UL-DL-ConfigCommon* as defined in TS 138.331 for 30 kHz SCS. The tester should use the 3GPP prescribed waveform as the recommended waveform but has the option to use any TDD configuration in the IOT profiles defined in [25] with the above constraints. - -This test frame consists of a PDCCH in the first two symbols of every downlink slot consisting of 3 PRBs. All the remaining PRBs in the frame consist of Physical Downlink Shared Channel data. This configuration corresponds to stock data section A (clause 3.2.1.1.5 below) in all symbols that do not contain PDCCH channels. Individual tests may call out other stock data sections as needed. If the radio does not support the numerology described in clause 3.2.3.1 the stock test frames can be adapted for smaller numbers of PRBs and should still be used. Symbols number two and eleven contain DMRS signals which are not used to test O-RAN Front Haul capabilities but should be sent to help test equipment synchronize. In the standard test frame, all PDSCH data is set to zeros if not otherwise described in the testcase and PUSCH is set to PN23 sequences. For all tests in this document (except the most basic resource allocation test) the PN23 sequence will be used in both uplink and downlink to allow the test to determine whether test data was put in the correct PRBs and whether the test data was accurately transmitted (or received) by the O-RU under test. - -- For tests for type 1-C and 1-H the test configuration described in TS 138.141-1 for TDD testing will be used. Only a single antenna port will be used unless the test explicitly requires more than one port and the radio supports more than one port. RF test equipment will be connected at the point described in TS 138.141-1. Note that an antenna port is an electrical conducting port that is connected to an array element. -- The test will start with the Test model described above. Subsequent tests will adapt this model to test additional features of the O-RAN interface (e.g. Modifying the payload data, blanking some symbols, etc.). Note this test model describes the IQ data contained in the O-RAN packets not the O-RAN specific parameters. This test model will also be augmented with the following O-RAN specific parameters: - -Includes “stock” eAxC values as configured via M-Plane: - -- DU\_Port\_ID: two bits, nominal value 00b -- BandSector: nominal 6 bits, nominal value 000000b -- CC\_ID: nominal 4 bits, nominal value 0000b (most tests invoke only one component carrier) -- RU\_port\_ID: 4 bits, nominal values 0000b through 0011b or to whatever max value needed for a specific test -- If the radio manufacturer declares support for multi-carrier a different eAxC will be assigned for each carrier. Note that most tests described in ETSI TS 138.141-1[NR] and TS 136.141 [LTE] require testing at the bottom, middle and top of the supported bands of the radio. This specification relaxes that requirement because the purpose is to test the fronthaul compliance and not the radio performance. -- **Compression:** Static 16-bit fixed point IQ bitwidth in both DL and UL -- **Beamforming:** no beamforming (beamId = 0x0000), assumed to mean boresight radiation (normal to the antenna surface) at some undetermined beamwidth (recall that beam weight magnitudes must be equal to unity) -- **Transport:** L2 Ethernet, eCPRI with no fragmentation and no QOS -- **Delay Parameters:** The test will be executed with a direct fibre connection to the O-RU and the network delay is considered negligible for the purpose of delay management. Therefore, T12\_min = T12\_max = 0 and T34\_min = T34\_max = 0. - -The radio will report its supported values for: - -- T2a\_min/max\_up -- Ta3\_min/max\_up -- T2a\_min/max\_cp\_ul -- Tcp\_adv\_dl - -These parameters will be used to calculate the delay windows needed for the delay management tests below. Note that T1a\_min\_up = T2a\_min\_up and T1a\_max\_up = T2a\_max\_up due to the fixed, zero network delay. Similarly, Ta4\_min\_up = Ta3\_min\_up and Ta4\_max\_up = Ta3\_max\_up. Similarly, T1a\_min\_cp\_ul = T2a\_min\_cp\_ul and T1a\_max\_cp\_ul = T2a\_max\_cp\_ul. - -- Uplink tests will start with the basic 3GPP test signal for Fixed Reference Channels for receiver sensitivity and in-channel selectivity as described in ETSI TS 138.141-1[NR] and TS 136.141 [LTE] and described above. All O-RAN specific parameters will be the same as described above for downlink testing. As with downlink testing subsequent tests will build on this basic waveform modifying parameters as needed to exercise O-RAN specific features. -- Uplink tests will be conducted using power levels at least 30dB higher than the power levels used to test 3GPP Receiver sensitivity described in ETSI TS 138.141-1 Table 7.2.5-1[NR] and TS 136.141 [LTE]. This is to ensure a clear signal is received by the O-RU so it can be accurately decoded and demodulated to ensure the correct data was received by the O-DU as was sent by the signal source. Again, the purpose of these tests is to ensure correct operation of the O-RAN fronthaul not to test receiver sensitivity. - -### 3.2.1.1.4 For Scenario #4 (Non-conducted OTA TDD Tests for FR1 and FR2 Radios) - -All provisions of clause 3.2.1.1.2 with respect to OTA methodology will apply to this scenario, except applied to TDD FR1 (1-H, 1-O) and FR2 (2-O) radios. The default test waveform for FR1 will be a TDD waveform as described in Sec. 3.2.1.1.3. The default test waveform for FR2 will be a 100 MHz bandwidth TDD waveform based on NR-FR2-TM1.1 for the downlink, and G-FR2-A1-3 for 120 kHz subcarrier spacing with 66 RBs in the uplink. The TDD test - -model is derived based on the uplink/downlink configurations described in ETSI TS 138.141-2 Table 4.9.2.2-1 using information element *TDD-UL-DL-ConfigCommon* as defined in TS 138.331 as shown below: - -**Table 3.2.1-2 Configuration Parameters for FR2 Radio Testing** - -| Field name | Value | -|----------------------------------------------------|-------| -| referenceSubcarrierSpacing (kHz) | 120 | -| Periodicity (ms) for dl-UL-TransmissionPeriodicity | 1.25 | -| nrofDownlinkSlots | 7 | -| nrofDownlinkSymbols | 6 | -| nrofUplinkSlots | 2 | -| nrofUplinkSymbols | 4 | - -As an alternative to the default test waveform shown in Figure 3.2.1.1-4, it is optional to flexibly use other test waveforms with any TDD configurations allowed by the information element *TDD-UL-DL-ConfigCommon* as defined in TS 138.331. The tester should use the 3GPP prescribed waveform as the recommended waveform but has the option to use any TDD configuration in the IOT profiles defined in [25] with the above constraints. - -This test frame consists of a PDCCH in the first two symbols of every downlink slot consisting of 3 PRBs. All the remaining PRBs in the frame consist of Physical Downlink Shared Channel data. This configuration corresponds to stock data section A (clause 3.2.1.1.5 below) in all symbols that do not contain PDCCH channels. Individual tests may call out other stock data sections as needed. If the radio does not support the numerology described the stock test frames can be adapted for smaller numbers of PRBs and should still be used. Symbols number two and eleven contain DMRS signals which are not used to test O-RAN Front Haul capabilities but should be sent to help test equipment synchronize. In the standard test frame, all PDSCH data is set to zeros if not otherwise mentioned in the testcase and PUSCH is set to PN23 sequences. For all tests in this document (except the most basic resource allocation test) the PN23 sequence will be used in both uplink and downlink to allow the test to determine whether test data was put in the correct PRBs and whether the test data was accurately transmitted (or received) by the O-RU under test. - -- For downlink tests for type 1-H radios that elect to be tested over the air (OTA) rather than conducted, the test configuration is described in TS 138.141-2 E.1.2 where the Test Antenna will be placed inside an OTA chamber and measurements are referenced to the radiated characteristics defined over the air (OTA) at the Radiated Interface Boundary (RIB) defined in TS 138.141-2 4.2-1. The RF analyser test equipment is connected to the Test Antenna and is located outside of the OTA chamber. -- For downlink test for 1-O or 2-O radios (radios with no physical antenna or TAB connectors and consequently only over the air – OTA – measurements are possible) the test configuration is described in TS 138.141-2 E.1.2 where the Test Antenna will be placed inside an OTA chamber and measurements are referenced to the radiated characteristics defined over the air (OTA) at the Radiated Interface Boundary (RIB) defined in TS 138.141-2 4.2-2. The RF analyser test equipment is connected to the Test Antenna and is located outside of the OTA chamber. -- For uplink tests for type 1-H radios that elect to be tested over the air (OTA) rather than conducted, the test configuration is described in TS 138.141-2 E.2.1 where the Test Antenna will be placed inside an OTA chamber and measurements are referenced to the radiated characteristics defined over the air (OTA) at the Radiated Interface Boundary (RIB) defined in TS 138.141-2 4.2-1. The RF generator test equipment is connected to the Test Antenna and is located outside of the OTA chamber. -- For uplink test for 1-O or 2-O radios (radios with no physical antenna or TAB connectors and consequently only over the air (OTA) measurements are possible) the test configuration is described in TS 138.141-2 E.2.1 where the Test Antenna will be placed inside an OTA chamber and measurements are referenced to the radiated characteristics defined over the air (OTA) at the Radiated Interface Boundary (RIB) defined in TS - -138.141-2 4.2-2. The RF generator test equipment is connected to the Test Antenna and is located outside of the OTA chamber. - -- For downlink tests for LTE radios that elect to be tested over the air (OTA), the test configuration is described in TS 138.141-2 E.1.2 where the Test Antenna will be placed inside an OTA chamber and measurements are referenced to the radiated characteristics defined over the air (OTA) at the Radiated Interface Boundary (RIB) defined in TS 138.141-2 4.2-1. The RF analyser test equipment is connected to the Test Antenna and is located out of the OTA chamber. -- For uplink tests for LTE radios that elect to be tested over the air (OTA), the test configuration is described in TS 138.141-2 E.2.1 where the Test Antenna will be placed inside an OTA chamber and measurements are referenced to the radiated characteristics defined over the air (OTA) at the Radiated Interface Boundary (RIB) defined in TS 138.141-2 4.2-1. The RF generator test equipment is connected to the Test Antenna and is located out of the OTA chamber. -- Note that the chamber shown in TS 138.141-2 E.1.2. and E.2.1. are generic and consequently any OTA chamber could be used, i.e. far field, CATR, near field, reverberation, etc. -- Likewise, depending on the beamforming measurement technology the positioner in TS 138.141-2 E.1.2 and E.2.1. may or may not be needed. -- Furthermore, depending on the beamforming method to be measured more than one test antenna with more than one RF analyser and/or generator may also be needed. -- The basic downlink test will start with the Test model described in NR-FR1-TM1.1 and E-TM1.1 in TS 138.141-1 and 36.141 for NR FR1 and LTE radios respectively, and NR-FR2-TM1.1 in TS 138.141-2 for FR2 radios. Subsequent tests will adapt this model to test additional features of the O-RAN interface (e.g. Modifying the payload data, blanking some symbols, etc.). Note this test model describes the IQ data contained in the O-RAN packets not the O-RAN specific parameters. This test model will also be augmented with the following O-RAN specific parameters: - -Includes “stock” eAxC values as configured via M-Plane: - -- DU\_Port\_ID: two bits, nominal value 00b -- BandSector: nominal 6 bits, nominal value 000000b -- CC\_ID: nominal 4 bits, nominal value 0000b (most tests invoke only one component carrier) -- RU\_port\_ID: 4 bits, nominal values 0000b through 0011b or to whatever max value needed for a specific test -- If the radio manufacturer declares support for multi-carrier a different eAxC will be assigned for each carrier. Note that most tests described in ETSI TS 138.141-2[NR] and TS 136.141 [LTE] require testing at the bottom, middle and top of the supported bands of the radio. This specification relaxes that requirement because the purpose is to test the fronthaul compliance and not the radio performance. -- **Compression:** Static 16-bit fixed point IQ bitwidth in both DL and UL -- **Beamforming:** no beamforming (beamId = 0x0000), assumed to mean boresight radiation (normal to the antenna surface) at some undetermined beamwidth (recall that beam weight magnitudes must be equal to unity) -- **Transport:** L2 Ethernet, eCPRI with no fragmentation and no QOS -- **Delay Parameters:** The test will be executed with a direct fibre connection to the O-RU and the network delay is considered negligible for the purpose of delay management. Therefore, T12\_min = T12\_max = 0 and T34\_min = T34\_max = 0. - -The radio will report its supported values for: - -- T2a\_min/max\_up -- Ta3\_min/max\_up - -- T2a\_min/max\_cp\_ul -- Tcp\_adv\_dl - -These parameters will be used to calculate the delay windows needed for the delay management tests below. Note that T1a\_min\_up = T2a\_min\_up and T1a\_max\_up = T2a\_max\_up due to the fixed, zero network delay. Similarly, Ta4\_min\_up = Ta3\_min\_up and Ta4\_max\_up = Ta3\_max\_up. Similarly, T1a\_min\_cp\_ul = T2a\_min\_cp\_ul and T1a\_max\_cp\_ul = T2a\_max\_cp\_ul. - -- Uplink tests will start with the basic 3GPP test signal for Fixed Reference Channels for receiver sensitivity and in-channel selectivity as described in ETSI TS 138.141-2[NR] and TS 136.141 [LTE]. All O-RAN specific parameters will be the same as described above for downlink testing. As with downlink testing subsequent tests will build on this basic waveform modifying parameters as needed to exercise O-RAN specific features. -- Uplink tests will be radiated using power levels at least 30dB higher than the reference sensitivity power levels used to test 3GPP Receiver sensitivity described in ETSI TS 138.141-2 Table 7.3.5.2-1, Table 7.3.5.2-2 and Table 7.3.5.2-3[NR FR1], Table 7.3.5.3-1 [NR FR2] and TS 136.141 Table 7.2-1 to Table 7.2-12 [LTE]. This is to ensure a clear signal is received by the O-RU so it can be accurately decoded and demodulated to ensure the correct data was received by the O-DU as was sent by the signal source. Again, the purpose of these tests is to ensure correct operation of the O-RAN fronthaul not to test receiver sensitivity. - -### 3.2.1.1.5 Test Configuration for the UC-Plane - -The TER shown in Figure 2.1-1 provides M-Plane and S-Plane commands and sequences to correctly set up the O-RU for testing using the fronthaul connection – meaning a criterion and prerequisite for executing all UC-Plane tests is proper operation of the O-RU’s synchronization and M-Plane capabilities. The TER provides the specific C-Plane and U-Plane data flows and collects data from the radiated energy from the O-RU and evaluates based on the collected RF energy whether the O-RU correctly received and interpreted the fronthaul DL data flow. For many tests a single RF detector is satisfactory to detect the radiated signal but for beamforming tests an RF pattern must be measured to validate the correct beam is being generated according to the C-Plane commands and U-Plane data flowing across the fronthaul interface. - -In addition, the TER generates RF energy using the signal generator and feeds it to the O-RU’s antennas (or antenna connectors) which is expected to be used by the O-RU, in conjunction with the C-Plane UL commands sent by the TER over the fronthaul connection, to generate UL data flows on the fronthaul connection which are received and evaluated by the TER. For almost all tests a single RF emitter is satisfactory to generate the radiated signal, even beamforming tests wherein the received power level will validate that the beam main lobe was correctly specified across the fronthaul interface, except for the case of uplink channel-information-based beamforming and DMRS based beamforming tests where multiple RF emitters are needed to emulate multiple uplink spatial streams. - -3GPP-specified tests will be used here to simplify the testing, because such tests will need to be supported by the O-RU anyway for 3GPP conformance testing. The specific test cases identify where this is possible and where changes must be made to adequately test O-RAN features. - -Note that when testing the O-RU for fronthaul interface conformance, much more than the fronthaul interface is being tested, indeed the entire O-RU is under test, including digital and analogue processing having nothing to do with the fronthaul interface. Therefore a “passed” test can be interpreted with some confidence as indicating a properly operating fronthaul interface, but a “failed” test may indicate a problem with the fronthaul interface or with some other operation within the O-RU therefore failed tests may require some troubleshooting. While ETSI TS 138.141-1, TS 138.141-2 [NR] and TS 136.141 [LTE] describes the basic waveform used in these tests it does not describe how the various channels should be put into O-RAN sections. The ETSI TS 138.141-1 NR-FR1-TM1.1 [NR FR1], TS 138.141-2 NR-FR2-TM1.1 [NR FR2], and TS 136.141 E-TM1.1 [LTE] signals are tightly packed with data. All tests will divide that data into “stock” data sections using the sections described below. To expedite the definition and creation of the tests, a set of standard test environments and patterns is defined in this clause. This includes a “stock” arrangement - -of data sections in DL (same is used for UL) which can be used regardless of the specific bandwidth and SCS used in the test. Specifically, there are “stock” 1-symbol, 2-symbol, and 3-symbol data section sets that shall be cited in test definitions (numbered “A” through “F”) that will support various test cases. The test cases are expected to specify the data section definition of a test slot and all slots are expected to follow the same data section definition unless a test specifically states otherwise. In many cases only some symbols within a slot will be subject to testing; the remaining symbols are expected to remain undefined for the test and may have data sections defined according to the normal operation of the O-DU (e.g. set to carry synch or reference signals consistent with LTE or NR). In cases where a specific type of data section cannot be supported by the DUT, then that data section is omitted in the symbol(s) and the corresponding U-Plane data shall be set to zero in DL (and arranged to have no RF power in UL). Figure 3.2.1.1-4 shows the “stock” data section definition. - -![Figure 3.2.1.1-4: Stock Data Section Definition for both DL and UL. The figure illustrates six test configurations (A through F) for PRB (Physical Resource Block) allocation across time symbols. The x-axis represents PRBs up to a maximum of 273. The y-axis lists definitions A-F. Configuration A shows a single continuous section. B shows two sections. C shows two sections with a gap. D shows six distinct sections. E spans two symbols with two sections. F spans three symbols with a complex multi-section arrangement. Colors (yellow, green, blue, pink) differentiate sections. Arrows at the top indicate end-of-symbol boundaries for various Subcarrier Spacings (SCS) and bandwidths. A legend explains that asterisks mark PRBs with reMask not all ones, and white-colored PRBs represent empty PRBs.](9e623456fe8c4de1b2c053331851b210_img.jpg) - -**“stock” data section definitions A-F:** - -PRBs (max=273) - -Arrows mark end-of-symbol for various SCS and bandwidths - -A: 1 section -B: 2 sections -C: 2 sections w/ gap\*\* -D: 6 sections -E: 2 symbols -2 sections -F: 3 symbols -complex - -\* marks PRBs with reMask NOT all ones -\*\* white-colored PRBs represent empty PRBs - -**A: 1 symbol 1 section only : simplest case** -**B: 1 symbol 2 sections : slightly more complex** -**C: 1 symbol 2 sections w/ gap : tests ability to handle data gaps** -**D: 1 symbol many sections : tests single-PRB section, rb bit, use of non-all-ones reMask, many data sections** -**E: 2 symbol 2 sections : tests multi-symbol section, symInc bit** -**F: 3 symbols many sections : tests data gaps, reMask, multi-symbol sections** - -Figure 3.2.1.1-4: Stock Data Section Definition for both DL and UL. The figure illustrates six test configurations (A through F) for PRB (Physical Resource Block) allocation across time symbols. The x-axis represents PRBs up to a maximum of 273. The y-axis lists definitions A-F. Configuration A shows a single continuous section. B shows two sections. C shows two sections with a gap. D shows six distinct sections. E spans two symbols with two sections. F spans three symbols with a complex multi-section arrangement. Colors (yellow, green, blue, pink) differentiate sections. Arrows at the top indicate end-of-symbol boundaries for various Subcarrier Spacings (SCS) and bandwidths. A legend explains that asterisks mark PRBs with reMask not all ones, and white-colored PRBs represent empty PRBs. - -**Figure 3.2.1.1-4 Stock Data Section Definition for both DL and UL** - -There is also “stock” U-Plane data that is PN23 data, representing user data prior to modulation, as specified within ETSI TS 138.141-1[CCITT Recommendation O.151 (10/92): ] which is assumed to start at a frame boundary and be identical in all frames in both DL and UL, unless a specific test states differently. The PN sequence is expected to be running for the duration of the frame for whatever is the bandwidth and SCS (this is different from how the data sections are handled, wherein the data sections are truncated based on the number of PRBs per symbol). However, in many cases only some symbols within a frame will be actually subject to testing (as defined by the specific tests) so will contain the test PN sequence data; the remaining symbols are expected to remain undefined for the test and may contain data according to the normal operation of the O-DU (e.g. set to carry synch or reference signals consistent with LTE or NR). Note that the PN sequence initial value is provided by a seed which may be included as a Test Command parameter. If the parameter is omitted the PN sequence generator will use a “seed” value of all ones. - -For all tests, the test definition shall define the specific slots and symbols subject to test (carrying the “stock” C-Plane data section definition and the “stock” U-Plane data) with the remaining slots and symbols carrying normal 3GPP synch and control data and either allocated user data according to 3GPP or left empty (i.e. no user data allocated). All slots and symbols subject to test are identical in each frame, so tests do not have to wait for a specific frame number and are not expected to reset or otherwise perturb the normal frame number sequence. This is intended to allow the test to disrupt normal O-DU and O-RU operation as little as possible. If there is a specific need to validate the construction of a specific frame or slot of data, a test may elect to zero the test data and leave undefined the data sections for all except - -one slot or frame of data; where this is necessary it will be described in the specific test definition, but this is expected to be an exceptional case. - -### 3.2.1.1.6 Generic Steps for Test Execution, O-RU TEST SCENARIO - -The following are the generic test steps used when testing the O-RU, although specific tests may deviate from this general procedure: - -- 1) Configure the Test Equipment, O-RU (TER) for test execution, which may include defining the specific test to execute. This may also include using a scripting language for describing the test. -- 2) Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- 3) Send appropriate C-Plane and U-Plane DL data flows and collect the O-RU radiated energy (or collect from antenna connectors) using RF detection equipment. -- 4) Evaluate the RF energy pattern from the O-RU to determine if the O-RU correctly received and interpreted the fronthaul C-Plane and U-Plane data flows. In some cases, it also includes decoding and demodulating the RF signal to ensure all UC-Plane messages were interpreted correctly. -- 5) Send appropriate C-Plane messages to define the desired UL U-Plane flow, at the same time cause the RF signal generator to radiate (or feed into antenna connectors) the appropriate RF energy pattern for the test. This also means meeting the appropriate timing windows to allow the O-RU to decode and process the C-Plane messages before the signal generator starts sending RF. -- 6) Collect the O-RU UL data flows on the fronthaul interface and evaluate for correctness; this will generally be U-Plane data only but in limited cases (LAA) may include UL C-Plane messages too. -- 7) Since FDD uplink and TDD tests require tight timing constraints between the components of the TER it is recommended that CUSM emulator signal the RF test equipment when C-Plane signalling has started for a frame. How this signal is used by the RF test equipment to synchronize transmission and reception is implementation dependant. - -## 3.2.2 Minimum Capabilities of the TER for U-Plane and C-Plane Tests - -Since many features of the O-RAN protocol rely on the O-DU instructing the O-RU to put data in specific resource blocks using a specific compression method it is imperative that the test equipment support features that allow comparing data on the fronthaul side with data on the RF side of the radio. - -### 3.2.2.1 Signal Analyser - -- has the capability of decoding and demodulating an RF signal either received over the air or on a conducted interface. This data must be made available for comparison with data sent on the fronthaul interface. -- is able to determine the Phase and amplitude of any signal for beamforming tests. -- Obviously must support the frequency range of the radio being tested. - -### 3.2.2.2 Signal Generator - -- provides software capable of building a correct 5G or LTE waveform. -- Should have the ability to automatically build 3GPP compliant test waveforms and should provide a mechanism for editing the parameters of that waveform. -- is able to be synchronized with the O-DU emulator to ensure proper timing of uplink C-Plane and U-Plane messages -- For beamforming test cases: - - is able to inject beamformed RF signals according to the test requirements. - -- needs to be able to emulate a static channel according to the test requirements. - -### 3.2.2.3 CUSM-Plane Emulator (CUSM-E) - -- is able to extract IQ data from uplink U-Plane messages and demodulate and decode the data to ensure it is the same as what was commanded in the uplink C-Plane messages. -- has the ability to synchronize with the RF signal source. -- Should have the ability to perform as a PTP Master or subordinate depending on the synchronization configuration the radio supports. -- has the ability to accept frequency domain IQ and encapsulate it according to user input on the correct sections. -- For DMRS BF test cases: - - is capable of measuring EVM and BER/BLER measurements of the received signal from DUT (Uplink direction). - - is able to operate with and without Channel Estimation and Equalization over the received signal from DUT (Uplink direction). - -## 3.2.3 FR1 FDD Conducted-Signal Tests - -### 3.2.3.1 UC-Plane O-RU Scenario Class NR testing Generic (NRG) - -Note that all downlink tests in this clause use a 3GPP test wave form with 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1 and clause 3.2.1.1.5 of this document. There are several variations on this test signal depending on the capabilities of the radio. If the radio does not support the numerology used in the example tests as reported in the M-plane it will be up to the test developer to modify their tests to adapt to the radio. This can usually be accomplished by using stock test patterns described above. The test is expected to follow the same spirit as the tests in this document but things like symbol numbers, number of PRBs, etc. may have to be changed. - -All uplink tests in this clause use a 3GPP test waveform described in 38.141-1 clause A1, in particular G-FR1-A1-5 (30 kHz subcarrier spacing, QPSK, 100 MHz BW). As with downlink tests if the radio does not support this signal, it is up to the test developer to modify the parameters of the test without changing the spirit of the test. - -#### 3.2.3.1.1 UC-Plane O-RU Scenario Class Base 3GPP DL - -##### A. Test Description and Applicability - -This test is MANDATORY. - -The purpose of this test is to ensure the radio can meet the most basic downlink requirements for O-RAN fronthaul. Subsequent tests will build on this to exercise additional capabilities of the Fronthaul. - -Using a standard 3GPP NR-FR1-TM1.1 test frame for FDD the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink the standard NR-FR1-TM1.1 signal. This signal is shown below in Figure 3.2.3.1-5. - -### 3GPP NR-FR1-TM1.1 FDD Test Signal - -![Figure 3.2.3.1-5: NR-FR1-TM1.1 FDD Test Signal. The figure contains two main visualizations. On the left, a large grid shows the frequency domain representation of the signal across 273 CRBs (y-axis, 0 to 273) over 20 slots (x-axis, 0 to 20). A legend indicates 'DCI' in red and 'DL-SCH' in green. A zoomed-in view of the first few slots shows the first three PRBs (0, 1, 2) in the first two symbols are red (DCI), while the rest are green (DL-SCH). On the right, a smaller grid titled 'RB Resource Mapping for DL-SCH1 (Modulation = QPSK)' shows subcarriers (0 to 12) over symbols (0 to 13). Red blocks indicate DMRS signals at symbols 2 and 11, while green blocks indicate user data.](240318eb53e18366b06354b765508a8f_img.jpg) - -- All the Physical Downlink Shared Channels (all PRBs that are not DCI) are populated with test data as described in each test case. -- DCI information is the first 3 PRBs in the first 2 symbols of every slot. The DCI data is set to all zeros. -- Each Slot contains downlink data in each symbol except symbols 2 and 11 which contain DMRS signals (Red) and user data as shown in Green. - -Figure 3.2.3.1-5: NR-FR1-TM1.1 FDD Test Signal. The figure contains two main visualizations. On the left, a large grid shows the frequency domain representation of the signal across 273 CRBs (y-axis, 0 to 273) over 20 slots (x-axis, 0 to 20). A legend indicates 'DCI' in red and 'DL-SCH' in green. A zoomed-in view of the first few slots shows the first three PRBs (0, 1, 2) in the first two symbols are red (DCI), while the rest are green (DL-SCH). On the right, a smaller grid titled 'RB Resource Mapping for DL-SCH1 (Modulation = QPSK)' shows subcarriers (0 to 12) over symbols (0 to 13). Red blocks indicate DMRS signals at symbols 2 and 11, while green blocks indicate user data. - -Figure 3.2.3.1-5 NR-FR1-TM1.1 FDD Test Signal - -This test frame consists of a PDCCH in the first two symbols of every slot consisting of 3 PRBs. All the remaining PRBs in the frame consist of Physical Downlink Shared Channel data. This configuration corresponds to stock data section A (clause 3.2.1.1.5 above) in all symbols that do not contain PDCCH channels. If the radio does not support the numerology described in clause 3.2.3.1 the stock test frames can be adapted for smaller numbers of PRBs and should still be used. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame using the default parameters in clause 3.2.1.1.5 of this document (or a similar 3GPP waveform) except only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). As per TM-FR1-TM1.1 all user data in this test will be zeros. - -#### B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described by TM-FR1-TM1.1. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. - -The O-RU must have a conducted antenna port (or TAB connector) to be connected to a signal analyser. It must also support the default parameters defined in clause 3.2.1.1.1 above. - -#### C. Test Methodology - -##### 1. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. - -##### 2. Procedure - -Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe - -the signal. Every symbol should be described by a single section (DL-SCH and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above. If it contains all the same PRB assignments and all zero data, the test passes. - -**3.2.3.1.2 UC-Plane O-RU Scenario Class Extended 3GPP DL – Resource allocation** - -**A. Test Description and Applicability** - -This test is MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink. This test is applicable for Category A and Category B radios (No precoding is required). The test will be conducted therefore there will be no channel distortion or interference. It is mandatory the radio pass this test to be considered O-RAN conformant. - -Using a standard 3GPP NR-FR1-TM1.1 test frame for FDD the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink the standard NR-FR1-TM1.1 signal. This signal is shown below in Figure 3.2.3.1-6. - -![Figure 3.2.3.1-6: 3GPP NR-FR1-TM1.1 FDD Test Signal. The figure shows a screenshot of a signal analysis tool. The main display is a spectrogram showing frequency (0 to 273 MHz) over time (0 to 20 slots). A zoomed-in view on the left shows the first few symbols. On the right, a table titled 'RB Resource Mapping for DL-SCH (Modulation = QPSK)' shows the mapping of resource blocks (RBs) to symbols. The table has columns for Symbol (0-13) and Subcarrier (0-12). Red squares indicate DCI signals, and green squares indicate DL-SCH signals. A list of bullet points explains the signal structure: all PRBs not DCI are populated with test data; DCI is the first 3 PRBs in the first 2 symbols; DCI data is all zeros; each slot contains downlink data except symbols 2 and 11 which contain DMRS signals.](430d6070a68b7787dcbf6ee6237c8c73_img.jpg) - -**3GPP NR-FR1-TM1.1 FDD Test Signal** - -**RB Resource Mapping for DL-SCH (Modulation = QPSK)** - -| Symbol | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | -|---------------|---|---|---|---|---|---|---|---|---|---|----|----|----|----| -| Subcarrier 12 | | | | | | | | | | | | | | | -| Subcarrier 11 | | | | | | | | | | | | | | | -| Subcarrier 10 | | | | | | | | | | | | | | | -| Subcarrier 9 | | | | | | | | | | | | | | | -| Subcarrier 8 | | | | | | | | | | | | | | | -| Subcarrier 7 | | | | | | | | | | | | | | | -| Subcarrier 6 | | | | | | | | | | | | | | | -| Subcarrier 5 | | | | | | | | | | | | | | | -| Subcarrier 4 | | | | | | | | | | | | | | | -| Subcarrier 3 | | | | | | | | | | | | | | | -| Subcarrier 2 | | | | | | | | | | | | | | | -| Subcarrier 1 | | | | | | | | | | | | | | | -| Subcarrier 0 | | | | | | | | | | | | | | | - -- All the Physical Downlink Shared Channels (all PRBs that are not DCI) are populated with test data as described in each test case. -- DCI information is the first 3 PRBs in the first 2 symbols of every slot. The DCI data is set to all zeros. -- Each Slot contains downlink data in each symbol except symbols 2 and 11 which contain DMRS signals (Red) and user data as shown in Green. - -Figure 3.2.3.1-6: 3GPP NR-FR1-TM1.1 FDD Test Signal. The figure shows a screenshot of a signal analysis tool. The main display is a spectrogram showing frequency (0 to 273 MHz) over time (0 to 20 slots). A zoomed-in view on the left shows the first few symbols. On the right, a table titled 'RB Resource Mapping for DL-SCH (Modulation = QPSK)' shows the mapping of resource blocks (RBs) to symbols. The table has columns for Symbol (0-13) and Subcarrier (0-12). Red squares indicate DCI signals, and green squares indicate DL-SCH signals. A list of bullet points explains the signal structure: all PRBs not DCI are populated with test data; DCI is the first 3 PRBs in the first 2 symbols; DCI data is all zeros; each slot contains downlink data except symbols 2 and 11 which contain DMRS signals. - -![Figure 3.2.3.1-6: NR-FR1-TM1.1 FDD Test Signal. A screenshot of a signal analysis tool showing a resource grid. The vertical axis represents subcarriers from 0 to 239, and the horizontal axis represents time in slots from 0 to 20. The grid is filled with green blocks, indicating active resource blocks across the entire bandwidth and time duration.](ddd6e04bb930e25bc5e3cd367a054516_img.jpg) - -Figure 3.2.3.1-6: NR-FR1-TM1.1 FDD Test Signal. A screenshot of a signal analysis tool showing a resource grid. The vertical axis represents subcarriers from 0 to 239, and the horizontal axis represents time in slots from 0 to 20. The grid is filled with green blocks, indicating active resource blocks across the entire bandwidth and time duration. - -Figure 3.2.3.1-6 NR-FR1-TM1.1 FDD Test Signal - -This test frame consists of a PDCCH in the first two symbols of every slot consisting of 3 PRBs. All the remaining PRBs in the frame consist of Physical Downlink Shared Channel data. This test requires non-zero data (PN23 Sequence) to populate all allocated resource blocks. This configuration corresponds to stock data section A in all symbols that do not contain PDCCH channels. - -#### B. Test Entrance Criteria - -The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in section NR-FR1-TM1.1. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. - -#### C. Test Methodology - -##### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. - -##### b. Procedure - -Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal. Every symbol should be described by a single section (DL-SCH and DCI) using Section Type 1 messages. The data in the sections must be a PN23 sequence using an initial seed of all ones. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above. If it contains all the same PRB assignments and data, the test passes. - -### 3.2.3.1.3 UC Plane O-RU Base Class FDD Test UL - -#### A. Test Description and Applicability - -This test is MANDATORY. - -The purpose of this test is to ensure the radio can meet the most basic uplink requirements for O-RAN fronthaul correctly interpreting C-Plane messages and correctly constructing uplink U-Plane messages from an RF signal. Subsequent tests will build on this to exercise additional capabilities of the Fronthaul. - -The test validates that correct uplink operation of the O-RU using 3GPP Reference Sensitivity level definition (clause 7.2 TS 138.141-1) of the Conducted Receiver Characteristic Test (Clause 7 TS 138.141) and power Levels at least 30 dB above Reference Sensitivity power Level described in TS 138.141-1 Table 7.2.5-1. This is to improve the likelihood that all data will be received by the radio correctly since we are not interested in testing receiver sensitivity but only the O-RAN protocol compliance. - -![Figure 3.2.3.1-7: G-FR1-A1-5 Uplink FDD Test Signal. The figure shows two plots. The top plot is a 'Channel Allocation' graph showing CRB for uplink (0 to 273) across 20 slots. A blue band at the bottom represents the UL-SCH. The bottom plot is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' showing subcarriers (0 to 12) across symbols (0 to 13). Red blocks indicate DMRS signals in symbols 2 and 11. A text box on the right explains that all PRBs are populated with test data, there is no UCI or SRS data, and each slot contains uplink data in each symbol except symbols 2 and 11 which contain DMRS signals only.](0510a00adb87ba5f37618c27f528afc5_img.jpg) - -**3GPP G-FR1-A1-5: SCS30k\_51RB 100 MHz Uplink FDD Test Signal** - -Channel Allocation - -CRB for uplink - -273 -250 -228 -206 -183 -161 -139 -117 -94 -72 -50 -27 -5 - -0 2 4 6 8 10 12 14 16 18 20 Slot - -FrameIndex: 0 - -UL-SCH - -RB Resource Mapping for UL-SCH1 (Modulation = QPSK) - -Subcarrier - -12 -11 -10 -9 -8 -7 -6 -5 -4 -3 -2 -1 -0 - -0 1 2 3 4 5 6 7 8 9 10 11 12 13 Symbol - -All the Physical Uplink Shared Channels (all PRBs shown in Blue) are populated with test data as described in each test case. - -- There is no UCI or SRS data -- Each Slot contains uplink data in each symbol except symbols 2 and 11 which contain DMRS signals only as shown in Red. - -Figure 3.2.3.1-7: G-FR1-A1-5 Uplink FDD Test Signal. The figure shows two plots. The top plot is a 'Channel Allocation' graph showing CRB for uplink (0 to 273) across 20 slots. A blue band at the bottom represents the UL-SCH. The bottom plot is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' showing subcarriers (0 to 12) across symbols (0 to 13). Red blocks indicate DMRS signals in symbols 2 and 11. A text box on the right explains that all PRBs are populated with test data, there is no UCI or SRS data, and each slot contains uplink data in each symbol except symbols 2 and 11 which contain DMRS signals only. - -Figure 3.2.3.1-7 G-FR1-A1-5 Uplink FDD Test Signal - -This signal is described by table A.1-1 in ETSI TS 138.141-1 and is referred to as G-FR1-A1-5 with the power increased to up to 30 dB above that described in Table 7.2.5-1. Under those conditions, a 3GPP compliant O-RU should deliver uplink U-Plane information that matches the uplink signal. - -The TER (Test Equipment, O-RU) generates an uplink signal on the antenna connector or TAB connector, together with the corresponding C-Plane messages on the Fronthaul interface. - -The TER will capture the U-Plane messages generated by the DUT and validate whether the payload matches the uplink signal. - -It applies to the O-RAN CUS Specification [2]: - -- Clause 7.4 -- Clause 8.3.2 -- Clause 8.3.3 - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in ETSI TS 138.141-1 clause G-FR1-A1-5. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. Note this - -signal may be changed to any of the 3GPP sensitivity test signals in table A.1-1 in ETSI TS 138.141-1 if the radio does not support the numerology and bandwidth used in this test. The test signal described in this clause will be used if the radio supports that numerology and bandwidth. - -### C. Test Methodology - -Leverage from the well-known payload (PN23 sequence) of the uplink signal to compare it with the payload of the signal communicated on the O-RAN interface. The IQ information is extracted from the U-Plane message and demodulated to retrieve payload. - -#### a: Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal source to the O-RU antenna port and configure the source to transmit the required 3GPP test signal upon receiving a trigger signal from the CUSM-E. The signal source power level should be adjusted to at least 30 dB above the setting used in the 3GPP receiver sensitivity test. - -#### b: Procedure - -- Load uplink test waveform (G-FR1-A1-5 : SCS30k\_51RB) on the RF signal source -- Configure signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that C-Plane messages have been sent. -- Load C-Plane message sequence on Test Equipment O-RU (TER) -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the RF uplink frame after the C-Plane messages have been sent honouring timing windows -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information -- Extract Payload -- Compare payload binary sequences - -### D. Test Requirement (expected result) - -1. The verdict is “Test pass” if the payload binary sequences match between the uplink test frame sent to the DUT and the received U-Plane data from the DUT -2. If any of the test conditions are not true, the verdict for the whole test is "Fail" - -### 3.2.3.1.4 UC-Plane O-RU Scenario Class Extended using RB Parameter 3GPP DL – Resource Allocation - -#### A. Test Description and Applicability - -This test is MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages with the rb parameter set, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink. This test is applicable for Category A and Category B radios (No precoding is required). The test will be conducted therefore there will be no channel distortion or interference. It is mandatory the radio pass this test to be considered O-RAN conformant. - -Using a standard 3GPP NR-FR1-TM1.1 test frame for FDD the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink the standard NR-FR1-TM1.1 signal. This signal is shown below in Figure 3.2.3.1-8. - -![3GPP NR-FR1-TM1.1 FDD Test Signal figure showing a resource grid and a detailed RB mapping for DL-SCH1.](3164cf54c06cbe87b0a432d17eb9417b_img.jpg) - -The figure displays a screenshot of a 3GPP NR-FR1-TM1.1 FDD Test Signal. The main window shows a resource grid for 20 slots, with the y-axis representing CRB for u=1 (0 to 273) and the x-axis representing Slot (0 to 20). A legend indicates that green represents DCI and red represents DL-SCH. A detailed view of the first slot shows the RB Resource Mapping for DL-SCH1 (Modulation = QPSK) across 12 subcarriers (0 to 11) and 13 symbols (0 to 12). Red blocks indicate DL-SCH data, and green blocks indicate DCI. The DCI is located in the first two symbols (0 and 1) across the first 3 PRBs (0, 1, 2). DMRS signals are present in symbols 2 and 11. The remaining PRBs are populated with test data. - -- All the Physical Downlink Shared Channels (all PRBs that are not DCI) are populated with test data as described in each test case. -- DCI information is the first 3 PRBs in the first 2 symbols of every slot. The DCI data is set to all zeros. -- Each Slot contains downlink data in each symbol except symbols 2 and 11 which contain DMRS signals (Red) and user data as shown in Green. - -3GPP NR-FR1-TM1.1 FDD Test Signal figure showing a resource grid and a detailed RB mapping for DL-SCH1. - -Figure 3.2.3.1-8 NR-FR1-TM1.1 FDD Test Signal - -This test frame consists of a PDCCH in the first two symbols of every slot consisting of 3 PRBs. All the remaining PRBs in the frame consist of Physical Downlink Shared Channel data. - -This test requires non-zero data to populate all allocated resource blocks. - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause NR-FR1-TM1.1. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. The signal analyser must have the ability to decode the downlink shared channel. - -**C. Test Methodology** - -**a. Initial Conditions** - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. - -**b. Procedure** - -Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal. Every allocated (see below) symbol should be described by sections (DL-SCH and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Symbol #3 of each slot should be Stock data section “D” as shown in clause 3.2.1.1.5 above. The control plane for symbol #3 will only include PRBs number 5 through 23. C-Plane messages will have the rb bit set to one for this section. All other DL-SCH symbols and PRBs other than PRBs 5-23 will either not contain data (i.e. left empty) or contain user data as defined in the 3GPP NR-FR1-TM1.1 FDD test model. There are two options to conduct the test: - -1. A single data section with the rb bit set and a PN23 sequence sent as shown below: - -![A diagram showing Resource Block (RB) allocation across symbols. The vertical axis shows RB #0, RB #5, and RB #23. The horizontal axis shows Symbol #0, Symbol #3, and Symbol #13. RB #0 is labeled 'PCCH'. RB #23 is labeled 'Either DL-SCH data or No Data'. A dashed box labeled 'DMRS acc. To 3GPP rules' encloses a column of RBs starting from Symbol #3. Inside this box, RB #23 contains green segments labeled 'P', 'N', '2', '3', 'S', 'E', 'Q', 'U' with red 'X' marks over the last four. Other RBs in the box are orange. Arrows point from the green segments to corresponding segments in RB #23. The text 'No Data' is written vertically next to the dashed box. The same 'DMRS acc. To 3GPP rules' label appears on the right side of the box.](a554d5480f9ae091a17e50011afe5968_img.jpg) - -A diagram showing Resource Block (RB) allocation across symbols. The vertical axis shows RB #0, RB #5, and RB #23. The horizontal axis shows Symbol #0, Symbol #3, and Symbol #13. RB #0 is labeled 'PCCH'. RB #23 is labeled 'Either DL-SCH data or No Data'. A dashed box labeled 'DMRS acc. To 3GPP rules' encloses a column of RBs starting from Symbol #3. Inside this box, RB #23 contains green segments labeled 'P', 'N', '2', '3', 'S', 'E', 'Q', 'U' with red 'X' marks over the last four. Other RBs in the box are orange. Arrows point from the green segments to corresponding segments in RB #23. The text 'No Data' is written vertically next to the dashed box. The same 'DMRS acc. To 3GPP rules' label appears on the right side of the box. - -A new PN23 sequence will be started but every other PRB will contain only the odd parts of the PN23 sequence (as shown in green). The other PRBs (shown in orange) will not contain data and will not be sent to the O-RU. Thus, a single data section will be used, and the corresponding U-Plane message will only contain data for the odd PRBs as shown above. The parts of the PN23 sequence not used (shown marked with an X) will be discarded. - -- Two data sections one containing the odd parts of the PN23 sequence and the other containing the even parts as shown below: - -![Diagram showing resource block (RB) allocation for PN23 sequences across symbols. The vertical axis shows RB #0, RB #5, and RB #23. The horizontal axis shows Symbol #0, Symbol #3, and Symbol #13. RB #0 contains PCCH. RB #5 and RB #23 show alternating green and orange blocks representing odd and even parts of the PN23 sequence. A dashed box around Symbol #3 indicates DMRS acc. To 3GPP rules. Vertical text 'Either DL-SCH data or No Data' is present on the left and right sides of the grid. The sequence letters P, N, 2, 3, S, E, Q, U are shown in the green blocks of RB #23.](c355b8056bdd4728357d7d5ed18792ca_img.jpg) - -Diagram showing resource block (RB) allocation for PN23 sequences across symbols. The vertical axis shows RB #0, RB #5, and RB #23. The horizontal axis shows Symbol #0, Symbol #3, and Symbol #13. RB #0 contains PCCH. RB #5 and RB #23 show alternating green and orange blocks representing odd and even parts of the PN23 sequence. A dashed box around Symbol #3 indicates DMRS acc. To 3GPP rules. Vertical text 'Either DL-SCH data or No Data' is present on the left and right sides of the grid. The sequence letters P, N, 2, 3, S, E, Q, U are shown in the green blocks of RB #23. - -A new PN23 sequence will be started but every other PRB in one section will contain only the odd parts of the PN23 sequence (as shown in green). The second data section will contain the even parts of the PN23 sequence. The C-Plane messages for both sections will use the rb bit. The U-Plane messages corresponding to the first data section will contain only the odd parts of the PN23 sequence, the U-Plane message corresponding to the second data section will only contain the even parts. Thus, a continuous PN23 sequence will be sent only in PRBs 5 through 23. - -Additional sections should be included to describe the DCI symbols, Reference Signals and also DL-SCH data (if opted to allocated data for the remaining symbols) as described in 38.141-1. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should only contain the PN23 sequence data in every other PRB in symbol #3 PRBs 5 to 23 if the test is conducted using option #1. -3. The test frame received by the signal analyser should only contain the PN23 sequence data in every PRB in symbol #3 PRBs 5 to 23 if the test is conducted using option #2. - -**3.2.3.1.5 UC Plane O-RU Scenario Class Extended using RB Parameter 3GPP UL – Resource Allocation** - -**A. Test Description and Applicability** - -This test is MANDATORY. - -This test adds the capability of interpreting the rb parameter to the basic uplink test - -Validate correct uplink operation of the O-RU using 3GPP Reference Sensitivity level definition (clause 7.2 TS 138.141-1) of the Conducted Receiver Characteristic Test (clause 7 TS 138.104) and power Levels at least 30 dB above Reference Sensitivity power Level described in TS 138.141-1 Table 7.2.5-1. This is to improve the likelihood that all data will be received by the radio correctly since we are not interested in testing receiver sensitivity but only the O-RAN protocol compliance. - -![Figure 3.2.3.1-9: SCS30k_51RB Uplink FDD Test Signal. The figure shows a screenshot of a radio simulation tool. The top part is a 'Channel Allocation' view showing 51 RBs (CRB indices 23 to 273) allocated for UL-SCH across 20 slots. The bottom part is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' view, which is a grid with Subcarriers (0-12) on the y-axis and Symbols (0-13) on the x-axis. Blue cells represent data, and red cells represent DMRS signals at symbols 2 and 11. A text box on the right explains that all PRBs are populated with test data, there is no UCI or SRS data, and DMRS signals are only present in symbols 2 and 11.](57de85188ce8fa114295d82ff92d8d95_img.jpg) - -Figure 3.2.3.1-9: SCS30k\_51RB Uplink FDD Test Signal. The figure shows a screenshot of a radio simulation tool. The top part is a 'Channel Allocation' view showing 51 RBs (CRB indices 23 to 273) allocated for UL-SCH across 20 slots. The bottom part is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' view, which is a grid with Subcarriers (0-12) on the y-axis and Symbols (0-13) on the x-axis. Blue cells represent data, and red cells represent DMRS signals at symbols 2 and 11. A text box on the right explains that all PRBs are populated with test data, there is no UCI or SRS data, and DMRS signals are only present in symbols 2 and 11. - -Figure 3.2.3.1-9 SCS30k\_51RB Uplink FDD Test Signal - -Using an RF data source, the test equipment will generate a 3GPP test signal as shown in Figure 3.2.3.1-9 above. The radio will demodulate and decode this signal and send frequency domain IQ to the O-DU-Emulator as instructed by the O-DU-emulator using uplink C-Plane messages - -The TER (Test Equipment, O-RU) generates an uplink signal on the antenna connector or TAB connector, together with the corresponding C-Plane messages on the Fronthaul interface. - -The TER will capture the U-Plane messages generated by the DUT and validate if the payload matches with the uplink signal. - -It applies to the O-RAN CUS Specification [2]: - -- Clause 7.4 -- Clause 8.3.2 -- Clause 8.3.3 - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in ETSI TS 138.141-1 clause G-FR1-A1-5. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. The radio must report that it supports the rb parameter. Note this signal may be changed to any of the 3GPP sensitivity test signals in table A.1-1 in ETSI TS 138.141-1 if the radio does not support the numerology and bandwidth used in this test. The test signal described in this clause will be used if the radio supports that numerology and bandwidth. - -## C. Test Methodology - -Leverage from the well-known payload (Pseudo Random sequence) of the uplink signal to compare it with the payload of the signal communicated on the O-RAN interface. The IQ information is extracted from the U-Plane message and demodulated to retrieve payload. - -### a: Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal source to the O-RU antenna port and configure the source to transmit the required 3GPP test signal upon receiving a trigger signal from the CUSM-E. The signal source power level should be adjusted to at least 30 dB above the setting used in the 3GPP receiver sensitivity test. - -### b: Procedure - -- Load uplink test waveform (G-FR1-A1-5 : SCS30k\_51RB) on the RF signal source. Note this signal has a PN23 sequence as user data. -- Configure signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that C-Plane messages have been sent. -- Load C-Plane message sequence on Test Equipment O-RU (TER) – In this test only symbol number 6 will be used and all 51 PRBs will be used. All other symbols will not contain data except required DRMS signals which may be used to synchronize test equipment. There are two options for conducting this test: - 1. A single data section with the rb bit set and a PN23 sequence sent as shown below: - -![Diagram showing Resource Block (RB) mapping for UL-SCH data. The vertical axis represents RBs from #0 to #51. The horizontal axis represents symbols from #0 to #13. A dashed box highlights Symbol #6. In this symbol, odd-numbered PRBs (1, 3, 5, 7, 9, 11, 13, 15, 17, 19, 21, 23, 25, 27, 29, 31, 33, 35, 37, 39, 41, 43, 45, 47, 49, 51) are shown in blue and contain data elements labeled P, N, 2, 3, S, E, Q, U. Even-numbered PRBs (0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50) are shown in orange and contain no data. The sequence elements U, X, X, X, X are marked with red 'X's, indicating they are discarded. The diagram is labeled 'Either UL-SCH data or No Data' and 'DMRS acc. To 3GPP rules'.](10f4e3a2f3c016555ee12a5b556ba834_img.jpg) - -Diagram showing Resource Block (RB) mapping for UL-SCH data. The vertical axis represents RBs from #0 to #51. The horizontal axis represents symbols from #0 to #13. A dashed box highlights Symbol #6. In this symbol, odd-numbered PRBs (1, 3, 5, 7, 9, 11, 13, 15, 17, 19, 21, 23, 25, 27, 29, 31, 33, 35, 37, 39, 41, 43, 45, 47, 49, 51) are shown in blue and contain data elements labeled P, N, 2, 3, S, E, Q, U. Even-numbered PRBs (0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26, 28, 30, 32, 34, 36, 38, 40, 42, 44, 46, 48, 50) are shown in orange and contain no data. The sequence elements U, X, X, X, X are marked with red 'X's, indicating they are discarded. The diagram is labeled 'Either UL-SCH data or No Data' and 'DMRS acc. To 3GPP rules'. - -A new PN23 sequence will be started but every other PRB will contain only the odd parts of the PN23 sequence (as shown in blue). The other PRBs (shown in orange) will not contain data and will not be sent to the O-RU. Thus, a single data section will be used, and the corresponding U-Plane message will only contain data for the odd PRBs as shown above. The parts of the PN23 sequence not used (shown marked with an X) will be discarded. - -- Two data sections one containing the odd parts of the PN23 sequence and the other containing the even parts as shown below: - -![Diagram showing Resource Block (RB) mapping for PN23 sequences across symbols. The vertical axis represents RBs from #0 to #51. The horizontal axis represents symbols #0, #6, and #13. At symbol #6, a dashed box highlights a section where blue and orange blocks represent odd and even parts of a PN23 sequence. Arrows point from these blocks to labels P, N, 2, 3, S, E, Q, U, U. Vertical text 'Either UL-SCH data or No Data' and 'DMRS acc. To 3GPP rules' is present on both sides of the highlighted section.](c6240283e2f65a6d02db47fa4ab0c518_img.jpg) - -Diagram showing Resource Block (RB) mapping for PN23 sequences across symbols. The vertical axis represents RBs from #0 to #51. The horizontal axis represents symbols #0, #6, and #13. At symbol #6, a dashed box highlights a section where blue and orange blocks represent odd and even parts of a PN23 sequence. Arrows point from these blocks to labels P, N, 2, 3, S, E, Q, U, U. Vertical text 'Either UL-SCH data or No Data' and 'DMRS acc. To 3GPP rules' is present on both sides of the highlighted section. - -A new PN23 sequence will be started but every other PRB in one section will contain only the odd parts of the PN23 sequence (as shown in blue). The second data section will contain the even parts of the PN23 sequence (as shown in orange). The C-Plane messages for both sections will use the rb bit. The U-Plane messages corresponding to the first data section will contain only the odd parts of the PN23 sequence, the U-Plane message corresponding to the second data section will only contain the even parts. Thus, a continuous PN23 sequence will be sent only in PRBs 0 through 51. - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and trigger the source to play the RF signal on a frame boundary. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information -- Extract Payload -- Compare payload binary sequences - -**D. Test Requirement (expected result)** - -1. The verdict is “Test pass” if payload binary sequences match between the uplink test frame sent to the DUT and the received U-Plane data from the DUT. In particular symbol #6 should contain either every other PRB of the PN23 sequence or a continuous PN23 sequence in PRBs 0 through 51 depending which test option is chosen. -2. If any of the test conditions is not true, the verdict for the whole test is "Fail". - -### 3.2.3.1.6 UC-Plane O-RU Scenario Class Extended using SymInc Parameter 3GPP DL – Resource Allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages with the SymInc parameter set, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink. This test is applicable for Category A and Category B radios (No precoding is required). The test will be conducted therefore there will be no channel distortion or interference. - -Using a standard 3GPP NR-FR1-TM1.1 test frame for FDD the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink the standard NR-FR1-TM1.1 signal. This signal is shown below in Figure 3.2.3.1-10. - -![Figure 3.2.3.1-10 NR-FR1-TM1.1 FDD Test Signal. The figure shows a screenshot of a radio simulation tool. The main window displays a grid of resource blocks (RBs) over 20 slots, with a legend indicating DCI (green) and DL-SCH (red). A zoomed-in view on the left shows the first two symbols of a slot, highlighting the DCI region. A list of bullet points explains the signal structure: all PRBs not DCI are populated with test data; DCI is the first 3 PRBs in the first 2 symbols, set to all zeros; each slot contains downlink data in each symbol except symbols 2 and 11 which contain DMRS signals (red) and user data as shown in green. An inset graph titled 'RB Resource Mapping for DL-SCH1 (Modulation = QPSK)' shows red blocks representing data in specific subcarriers across symbols.](f6442d68601dfecfe5f7f8a70449a2f7_img.jpg) - -Figure 3.2.3.1-10 NR-FR1-TM1.1 FDD Test Signal. The figure shows a screenshot of a radio simulation tool. The main window displays a grid of resource blocks (RBs) over 20 slots, with a legend indicating DCI (green) and DL-SCH (red). A zoomed-in view on the left shows the first two symbols of a slot, highlighting the DCI region. A list of bullet points explains the signal structure: all PRBs not DCI are populated with test data; DCI is the first 3 PRBs in the first 2 symbols, set to all zeros; each slot contains downlink data in each symbol except symbols 2 and 11 which contain DMRS signals (red) and user data as shown in green. An inset graph titled 'RB Resource Mapping for DL-SCH1 (Modulation = QPSK)' shows red blocks representing data in specific subcarriers across symbols. - -Figure 3.2.3.1-10 NR-FR1-TM1.1 FDD Test Signal - -This test frame consists of a PDCCH in the first two symbols of every slot consisting of 3 PRBs. All the remaining PRBs in the frame consist of Physical Downlink Shared Channel data. - -This test requires to either populate all allocated resource blocks with non-zero data or leave all resource blocks, except for the resource blocks under test, empty or unallocated. In the case of nonzero data allocation, this data will be a PN23 sequence with a seed value of all ones. - -Two symbols will be reserved for testing the SymInc parameter as described below. - -#### B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause NR-FR1-TM1.1. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. - -The Radio must support the SymInc parameter as notified by the M-Plane. The signal analyser must have the ability to decode the downlink shared channel. - -## C. Test Methodology - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. - -### b. Procedure - -Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal. If all symbols have user data allocated, every symbol may be described by either multiple or a single type 1 section (DL-SCH and DCI) except symbols #5 and #6 which will be used for the SymInc test. The data in these sections must be a PN23 sequence using an initial seed of all ones. Each symbol should be a new PN23 sequence, that is PRB 0 should contain the data from a new PN23 sequence for each symbol. No Section Type zero messages will be used for this test. - -Symbols number 5 and 6 should be stock data sections type “E” as shown above. This stock data section consists of two adjacent symbols each containing two sections. The corresponding C-Plane message will contain 4 section IDs in a single C-Plane message describing symbols #5 and #6. The startSymbolId in the application header will be symbol #5. The third section ID for symbol #6 will have the SymInc bit set informing the O-RU that the third section will begin describing symbol #6. - -The corresponding U-Plane messages will be a new PN23 Sequence for each symbol (5 and 6). - -## D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should only contain the same PN23 signals that were sent in the U-Plane. - -### 3.2.3.1.7 UC Plane O-RU Scenario Class Extended using SymInc Parameter 3GPP UL – Resource Allocation - -## A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to add the capability of interpreting the SymInc parameter to the basic uplink test. - -Validate correct uplink operation of the O-RU using 3GPP Reference Sensitivity level definition (Clause 7.2 TS 138.141-1) of the Conducted Receiver Characteristic Test (clause 7 TS 138.141) and power Levels at least 30 dB above Reference Sensitivity power Level described in TS 138.141-1 table 7.2.5-1. This is to improve the likelihood that all data will be received by the radio correctly since we are not interested in testing receiver sensitivity but only the O-RAN protocol compliance. C-Plane messages will contain 4 sections with the SymInc bit set specifying that the radio should increment the current symbol. - -![Figure 3.2.3.1-11: 3GPP G-FR1-A1-5: SCS30k_51RB 100 MHz Uplink FDD Test Signal. The figure consists of two main parts. The top part is a 'Channel Allocation' plot showing CRB for run 1 across 20 slots. The y-axis represents CRB indices from 0 to 273, and the x-axis represents slots from 0 to 20. A blue band labeled 'UL-SCH' is visible from CRB 0 to 51 across all slots. The bottom part is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' plot. The y-axis represents subcarriers from 0 to 12, and the x-axis represents symbols from 0 to 13. Red blocks indicate data in symbols 2 and 11, while blue blocks indicate data in other symbols.](5fb91e7895e390abec542d9328a870ef_img.jpg) - -**3GPP G-FR1-A1-5: SCS30k\_51RB 100 MHz Uplink FDD Test Signal** - -- All the Physical Uplink Shared Channels (all PRBs shown in Blue) are populated with test data as described in each test case. -- There is no UCI or SRS data -- Each Slot contains uplink data in each symbol except symbols 2 and 11 which contain DMRS signals only as shown in Red. - -Figure 3.2.3.1-11: 3GPP G-FR1-A1-5: SCS30k\_51RB 100 MHz Uplink FDD Test Signal. The figure consists of two main parts. The top part is a 'Channel Allocation' plot showing CRB for run 1 across 20 slots. The y-axis represents CRB indices from 0 to 273, and the x-axis represents slots from 0 to 20. A blue band labeled 'UL-SCH' is visible from CRB 0 to 51 across all slots. The bottom part is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' plot. The y-axis represents subcarriers from 0 to 12, and the x-axis represents symbols from 0 to 13. Red blocks indicate data in symbols 2 and 11, while blue blocks indicate data in other symbols. - -**Figure 3.2.3.1-11 G-FR1-A1-5 Uplink FDD Test Signal** - -Using an RF source, the test equipment will generate a 3GPP test signal as shown in Figure 3.2.3.1-11 above. The radio will demodulate and decode this signal and send frequency domain IQ to the O-DU-Emulator as instructed by the O-DU-emulator using uplink C-Plane messages. Note this signal has 20 slots with all symbols populated with only uplink shared data in the only first 51 RBs. For this test, all the symbols except the ones being under test, symbols #5 and #6, may either be left empty/unallocated or be allocated with user data according to the test model above. If the symbols are populated with user data, PN23 data sequence will be used. - -The TER (Test Equipment, O-RU) generates an uplink signal on the antenna connector or TAB connector, together with the corresponding C-Plane messages on the Fronthaul interface. - -The TER will capture the U-Plane messages generated by the DUT and validate if the payload matches with the uplink signal. - -It applies to the O-RAN CUS Specification [2]: - -- Clause 7.4 -- Clause 8.3.2 -- Clause 8.3.3 - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in ETSI TS 138.141-1 clause G-FR1-A1-5. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. The radio must report that it supports the SymInc parameter. Note this signal may be changed to any of the 3GPP sensitivity test signals in table A.1-1 in ETSI TS 138.141-1 if the radio does not support the numerology and bandwidth used in this test. The test signal described in this clause will be used if the radio supports that numerology and bandwidth. - -## C. Test Methodology - -Leverage from the well-known payload (Pseudo Random sequence) of the uplink signal to compare it with the payload of the signal communicated on the O-RAN interface. The IQ information is extracted from the U-Plane message and demodulated to retrieve payload. - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal source to the O-RU antenna port and configure the source to transmit the required 3GPP test signal upon receiving a trigger signal from the CUSM-E. The signal source power level should be adjusted to at least 30 dB above the setting used in the 3GPP receiver sensitivity test. - -### b. Procedure - -- Load uplink test waveform (G-FR1-A1-5 : SCS30k\_51RB, 100 MHz) on the RF signal source. Note this signal has a PN23 sequence as user data. Configure the source to generate a new PN23 sequence in symbols #5 and #6. -- Configure signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that C-Plane messages have been sent. -- Load C-Plane message sequence on Test Equipment O-RU (TER) – Only symbols #5 and #6 in each slot will be used in this test. All other symbols will contain either user data and/or reference signals but will not be considered part of the test. These two symbols will be used to determine whether the radio properly increments the current symbol ID when the SymInc bit is set. The C-Plane message for symbol #5 should have the SymInc bit set. This message should have a third section describing symbol #6 (using the SymInc mechanism). All PRBs in each symbol will be requested (In the example waveform 51 PRBs). -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and trigger the source to play the RF signal on a frame boundary. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information -- Extract Payload -- Compare payload binary sequences - -## D. Test Requirement (expected result) - -1. The verdict is “Test pass” if payload binary sequences match between the uplink test frame sent to the DUT and the received U-Plane data from the DUT. In particular symbols number 5 and 6 should properly contain the correct PN23 sequences that were built by the signal source. -2. If any of the test conditions is not true, the verdict for the whole test is "Fail" - -### 3.2.3.1.8 UC-Plane O-RU Scenario Class Extended using reMask Parameter 3GPP DL – Resource Allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can correctly decode and interpret C-Plane and U-Plane messages putting resource block in the correct place in the transmitted signal using the reMask parameter. In this test stock data section "D" will be used to exercise the reMask, only PRBs 1 through 5 will be used in this test. - -Using a standard 3GPP NR-FR1-TM1.1 test frame for FDD the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink the standard NR-FR1-TM1.1 signal as modified below. This signal is shown below in Figure 3.2.3.1-12: - -![Figure 3.2.3.1-12 NR-FR1-TM1.1 Modification 1. The figure shows a screenshot of a radio signal analysis tool. The main window displays a grid of Resource Blocks (RBs) over 20 slots, with a legend indicating DCI (green) and DL-SCH (red). A zoomed-in view on the left shows the first few RBs. A callout box contains a bulleted list of modifications. An inset graph on the right shows the 'RB Resource Mapping for DL-SCH1 (Modulation = QPSK)' with red blocks representing data in specific subcarriers and symbols.](26e4d6ae09790488a51e9171a1df0357_img.jpg) - -**3GPP NR-FR1-TM1.1 FDD Test Signal** - -- All the Physical Downlink Shared Channels (all PRBs that are not DCI) are populated with test data as described in each test case. -- DCI information is the first 3 PRBs in the first 2 symbols of every slot. The DCI data is set to all zeros. -- Each Slot contains downlink data in each symbol except symbols 2 and 11 which contain DMRS signals (Red) and user data as shown in Green. - -Figure 3.2.3.1-12 NR-FR1-TM1.1 Modification 1. The figure shows a screenshot of a radio signal analysis tool. The main window displays a grid of Resource Blocks (RBs) over 20 slots, with a legend indicating DCI (green) and DL-SCH (red). A zoomed-in view on the left shows the first few RBs. A callout box contains a bulleted list of modifications. An inset graph on the right shows the 'RB Resource Mapping for DL-SCH1 (Modulation = QPSK)' with red blocks representing data in specific subcarriers and symbols. - -**Figure 3.2.3.1-12 NR-FR1-TM1.1 Modification 1** - -This generic 3GPP NR-FR1-TM1.1 test frame consists of a PDCCH in the first two symbols of every slot consisting of 3 PRBs. All the remaining PRBs in the frame consist of Physical Downlink Shared Channel data. - -Resource blocks that are not under test may be filled with non-zero data or may be left unallocated. If filled with non-zero data, a PN23 sequence with a seed value of all ones must be used. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages with the reMask parameter set, transfer U-Plane data into the correct resource elements and transmit this data accurately in the downlink. This test is applicable for Category A and Category B radios (No precoding is required). The test will be conducted therefore there will be no channel distortion or interference. It is mandatory the radio pass this test to be considered O-RAN conformant. - -This test will utilize stock data section D described above. - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause NR-FR1-TM1.1. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. - -The Radio must support the reMask parameter as notified by the M-Plane. The signal analyser must have the ability to decode the downlink shared channel. - -**C. Test Methodology** - -**a. Initial Conditions** - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. - -**b. Procedure** - -Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal as described below. If all symbols have user data allocated, every symbol may be described by type 1 sections (DL-SCH and DCI). Only symbol #2 will be used for the reMask test. The data in this section must be a PN23 sequence using an initial seed of all ones. The first bits of the PN23 will be in PRB1 and continue in consecutive resource elements to the end of PRB5. No Section Type zero messages will be used for this test. The PN23 sequence will be interleaved with DMRS signals as shown below: - -![RB Resource Mapping for DL-SCH1 (Modulation = QPSK) diagram showing subcarriers 0-12 and symbols 0-13. It illustrates the mapping of DMRS and data sections (D, O, U, S, E, Z, N) across resource blocks.](24aa9e96ae01a0c590c2884c7454b7a7_img.jpg) - -The diagram shows the resource mapping for DL-SCH1 with QPSK modulation. The vertical axis represents Subcarriers (0 to 12) and the horizontal axis represents Symbols (0 to 13). - -- **DMRS:** Indicated by a label and arrows pointing to specific resource elements (REs) in symbols 2, 3, 4, 5, 6, 7, 8, and 9 across subcarriers 2, 3, 4, and 5. - -- **Data Sections:** Represented by green horizontal bars in symbol 2: - - -- Section 'D' (DL-SCH) in subcarriers 5-7. -- Section 'O' in subcarriers 5-7. -- Section 'U' in subcarriers 5-7. -- Section 'S' in subcarriers 5-7. -- Section 'E' in subcarriers 5-7. -- Section 'Z' in subcarriers 5-7. -- Section 'N' in subcarriers 5-7. -- A 'New PN23 (init register with all "1")' section in subcarriers 2-4. - - - **Other Symbols:** Symbols 0, 1, 10, 11, 12, and 13 are shown as empty grid cells. Symbols 2-9 have red blocks in subcarriers 0-1 and 10-12. - -RB Resource Mapping for DL-SCH1 (Modulation = QPSK) diagram showing subcarriers 0-12 and symbols 0-13. It illustrates the mapping of DMRS and data sections (D, O, U, S, E, Z, N) across resource blocks. - -Symbol number 2 should be stock data Section Type “D” as shown above. This test will only be using PRBs 1 through 5. The corresponding C-Plane message will contain two section IDs in a single C-Plane message describing symbol #2. The startSymbolId in the application header will be symbol #2. The C-Plane message will have one section with the reMask set to all 101010101010b (only DMRS REs) and another section with the reMask set to all ones. The first section (reMask = 101010101010b) will be for PRB 1 only, the second section will be for PRBs 2-5 and will have an reMask value of all ones. The two sections will have different section IDs. The remainder of the PRBs will not be used and set to zero value. The corresponding U-Plane messages will be a new PN23 Sequence (initial seed is all ones) in PRBs 1 through 5 of symbol #2 alternated with the DMRS signals. The first U-Plane message will correspond to sectionID with reMask set to 101010101010b and will contain one PRB with user data and DMRS signals as shown. The second U-Plane message will correspond to PRBs 2-5 and contain the same alternate data. The purpose of the section ID containing valid data is to ensure the radio sends a signal to synchronize the signal analyser. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should only contain the same PN23 signals that were sent in the U-Plane only for PRBs 2-5. Only DMRS signals should be sent for PRB1. - -### 3.2.3.1.9 UC Plane O-RU Scenario Class Extended using reMask Parameter 3GPP UL – Resource Allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -This test adds the capability of interpreting the reMask parameter to the basic uplink test. - -Validate correct uplink operation of the O-RU using 3GPP Reference Sensitivity level definition (Clause 7.2 TS 138.141-1) of the Conducted Receiver Characteristic Test (clause 7 TS 138.141) and power Levels at least 30 dB above Reference Sensitivity power Level described in TS 138.141-1 Table 7.2.5-1. This is to improve the likelihood that all data will be received by the radio correctly since we are not interested in testing receiver sensitivity but only the O-RAN protocol compliance. - -![Figure 3.2.3.1-13: 3GPP G-FR1-A1-5: SCS30k_51RB 100 MHz Uplink FDD Test Signal. The figure shows a screenshot of a radio simulation tool. The top part is a 'Channel Allocation' view showing a wide frequency band from 0 to 20 MHz with a blue bar representing the UL-SCH signal. The bottom part is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' view, which is a grid with 'Subcarrier' on the y-axis (0-12) and 'Symbol' on the x-axis (0-13). Most cells are blue, with red cells at symbols 2 and 11, representing DMRS signals. Red lines connect the top view to the bottom view. To the right of the grid is a text box with the following content: 'All the Physical Uplink Shared Channels (all PRBs shown in Blue) are populated with test data as described in each test case. • There is no UCI or SRS data • Each Slot contains uplink data in each symbol except symbols 2 and 11 which contain DMRS signals only as shown in Red.'](5b492020399ae8fbcc9714c8d83aebca_img.jpg) - -Figure 3.2.3.1-13: 3GPP G-FR1-A1-5: SCS30k\_51RB 100 MHz Uplink FDD Test Signal. The figure shows a screenshot of a radio simulation tool. The top part is a 'Channel Allocation' view showing a wide frequency band from 0 to 20 MHz with a blue bar representing the UL-SCH signal. The bottom part is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' view, which is a grid with 'Subcarrier' on the y-axis (0-12) and 'Symbol' on the x-axis (0-13). Most cells are blue, with red cells at symbols 2 and 11, representing DMRS signals. Red lines connect the top view to the bottom view. To the right of the grid is a text box with the following content: 'All the Physical Uplink Shared Channels (all PRBs shown in Blue) are populated with test data as described in each test case. • There is no UCI or SRS data • Each Slot contains uplink data in each symbol except symbols 2 and 11 which contain DMRS signals only as shown in Red.' - -Figure 3.2.3.1-13 G-FR1-A1-5 UL FDD Test Signal - -Using an RF source, the test equipment will generate a 3GPP test signal as shown in Figure 3.2.3.1-13 above. The radio will demodulate and decode this signal and send frequency domain IQ to the O-DU-Emulator as instructed by the O-DU-emulator using uplink C-Plane messages as described below. This test might either populate all symbols with non-zero data or leave them unallocated/empty. If symbols are populated, a PN23 sequence with seed all ones will be used. - -The TER (Test Equipment, O-RU) generates an uplink signal on the antenna connector or TAB connector, together with the corresponding C-Plane messages on the Fronthaul interface. - -The TER will capture the U-Plane messages generated by the DUT and validate if the payload matches the uplink signal. - -It applies to the O-RAN CUS Specification [2]: - -- Clause 7.4 -- Clause 8.3.2 -- Clause 8.3.3 - -## B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in ETSI TS 138.141-1 clause G-FR1-A1-5. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. The radio must report that it supports the reMask parameter. Note this signal may be changed to any of the 3GPP sensitivity test signals in table A.1-1 in ETSI TS 138.141-1 if the radio does not support the numerology and bandwidth used in this test. The test signal described in this clause will be used if the radio supports that numerology and bandwidth. - -## C. Test Methodology - -Leverage from the well-known payload PN23 sequence of the uplink signal to compare it with the payload of the signal communicated on the O-RAN interface. The IQ information is extracted from the U-Plane message and demodulated to retrieve payload. - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal source to the O-RU antenna port and configure the source to transmit the required 3GPP test signal upon receiving a trigger signal from the CUSM-E. The signal source power level should be adjusted to at least 30 dB above the setting used in the 3GPP receiver sensitivity test. - -### b: Procedure - -- Load uplink test waveform (G-FR1-A1-5 : SCS30k\_51RB) on the RF signal source. Note this signal will have a PN23 sequence as user data. -- Configure signal source to play the test waveform described below on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that C-Plane messages have been sent. -- Load C-Plane message sequence on Test Equipment O-RU (TER). For symbol #2 only PRBs 1-5 will be sent with the alternating user data and DMRS pattern shown below. Other symbols may be used in this test or be left unallocated (unused). However other symbols containing reference signals may be used to ensure the O-RU can synchronize with the TER. The format of symbol #2 used in this test will be: - -![RB Resource Mapping for UL-SCH2 (Modulation = QPSK)](c3afdf6d44fa08949ae7df7bd616453f_img.jpg) - -The figure shows a resource grid for UL-SCH2 with 12 subcarriers (0-11) on the y-axis and 13 symbols (0-12) on the x-axis. The grid is filled with grey squares. Red squares are located at (Symbol 2, Subcarriers 1-5) and (Symbol 3, Subcarriers 1-5). Green rectangles represent data sections: 'D' at (Symbol 2, Subcarriers 1), 'O' at (Symbol 2, Subcarriers 2-5), 'U' at (Symbol 3, Subcarriers 1), 'S' at (Symbol 3, Subcarriers 2-5), 'E' at (Symbol 4, Subcarriers 1), 'N' at (Symbol 4, Subcarriers 2-5), 'Z' at (Symbol 5, Subcarriers 1), 'A' at (Symbol 5, Subcarriers 2-5), and 'New PN23 (not register with all 1s)' at (Symbol 6, Subcarriers 1-5). DMRS signals are indicated by arrows pointing to (Symbol 7, Subcarriers 1-5). - -RB Resource Mapping for UL-SCH2 (Modulation = QPSK) - -The C-Plane message describing symbol #2 should contain two sections with different section IDs. Only PRBs 1-5 will be used (Matching stock data Section Type “D”). The first section should only describe PRB 1 and have an reMask of 101010101010b. The second section should describe PRBs 2-5 and have an reMask of all ones. The two sections should have different section IDs. - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and trigger the source to play the RF signal on a frame boundary. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information -- Extract Payload -- Compare payload binary sequences - -#### D. Test Requirement (expected result) - -1. The verdict is “Test pass” if payload binary sequences match between the uplink test frame sent to the DUT and the received U-Plane data from the DUT. In particular, there should only be U-Plane messages for PRBs 1-5 with user data and DMRS signals in PRBs 2-5 and only DMRS signals in PRB 1. -2. If any of the test conditions is not true, the verdict for the whole test is "Fail" - -### 3.2.3.1.10 UC-Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 6 3GPP DL – Resource Allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can correctly decode and interpret C-Plane and U-Plane messages putting resource block in the correct place in the transmitted signal using the extension type 6. In this test stock data section definition C will be used to exercise the non-contiguous RB allocation, all 273 PRBs (or the max number of PRBs per symbol for the highest numerology the radio supports) will be used in this test. - -Using a standard 3GPP NR-FR1-TM1.1 test frame for FDD the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink the standard NR-FR1-TM1.1 signal with the modifications described below (supporting non-contiguous PRB allocation). The standard 3GPP NR-FR1-TM1.1 is shown in Figure 3.2.3.1-14 below: - -![Figure 3.2.3.1-14: 3GPP NR-FR1-TM1.1 Test Signal. The figure shows a screenshot of a signal analysis tool. The main window displays a grid of Resource Blocks (RBs) across 20 slots, with RB indices 0 to 273 on the y-axis. A legend indicates DCI is red and DL-SCH is green. A zoomed-in view on the left shows the first few symbols of a slot, with RBs 0, 23, and 46 highlighted. A callout box lists key characteristics: all PRBs not DCI are populated with test data; DCI is the first 3 PRBs in the first 2 symbols, set to zeros; each slot contains downlink data in all symbols except 2 and 11, which contain DMRS signals (red) and user data (green). An inset graph titled 'RB Resource Mapping for DL-SCH1 (Modulation = QPSK)' shows a grid of subcarriers (0-12) vs symbols (0-13), with red blocks representing DMRS in symbols 2 and 11, and green blocks representing user data in other symbols.](8f56eaf659edc57ac74706e8caab9f95_img.jpg) - -**3GPP NR-FR1-TM1.1 FDD Test Signal** - -- All the Physical Downlink Shared Channels (all PRBs that are not DCI) are populated with test data as described in each test case. -- DCI information is the first 3 PRBs in the first 2 symbols of every slot. The DCI data is set to all zeros. -- Each Slot contains downlink data in each symbol except symbols 2 and 11 which contain DMRS signals (Red) and user data as shown in Green. - -Figure 3.2.3.1-14: 3GPP NR-FR1-TM1.1 Test Signal. The figure shows a screenshot of a signal analysis tool. The main window displays a grid of Resource Blocks (RBs) across 20 slots, with RB indices 0 to 273 on the y-axis. A legend indicates DCI is red and DL-SCH is green. A zoomed-in view on the left shows the first few symbols of a slot, with RBs 0, 23, and 46 highlighted. A callout box lists key characteristics: all PRBs not DCI are populated with test data; DCI is the first 3 PRBs in the first 2 symbols, set to zeros; each slot contains downlink data in all symbols except 2 and 11, which contain DMRS signals (red) and user data (green). An inset graph titled 'RB Resource Mapping for DL-SCH1 (Modulation = QPSK)' shows a grid of subcarriers (0-12) vs symbols (0-13), with red blocks representing DMRS in symbols 2 and 11, and green blocks representing user data in other symbols. - -**Figure 3.2.3.1-14 3GPP NR-FR1-TM1.1 Test Signal** - -This generic NR-FR1-TM1.1 test frame consists of a PDCCH in the first two symbols of every slot consisting of 3 PRBs. All the remaining PRBs in the frame consist of Physical Downlink Shared Channel data. - -This test might either populate all symbols with non-zero data or leave them unallocated/empty. If symbols are populated, a PN23 sequence with seed all ones will be used. - -This test will utilize stock data section definition C described above. This data section includes 4 RBs in the first RB group, the second group of 4 RBs are blank and the remainder of the RBGs contain user data. This stock data section will be repeated over three symbols to test the SymbolMask parameter. - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause NR-FR1-TM1.1. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. The Radio must support the extension type 6 as notified by the M-Plane. The signal analyser must have the ability to decode the downlink shared channel. - -**C. Test Methodology** - -**a. Initial Conditions** - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. - -**b. Procedure** - -For this test only symbols number 6 and 7 will be used in each slot. Other symbols may be used in this test or be left unallocated (unused). However other symbols containing reference signals may be used to ensure the O-RU can synchronize with the TER. - -The starting PRB will be zero and number of PRBs will be chosen from one or more columns in Table 3.2.3-1 below. The resource block group size will be 16 based on ETSI TS 138.214 Table 5.1.2.2.1-1 as shown in Table 3.2.3-1 below using configuration 2. - -**Table 3.2.3-1 Resource block group size definition for testing configuration 1 and 2.** - -| Bandwidth Part Size | Configuration 1 | Configuration 2 | -|---------------------|-----------------|-----------------| -| 1 – 36 | 2 | 4 | -| 37 – 72 | 4 | 8 | -| 73 – 144 | 8 | 16 | -| 145 – 275 | 16 | 16 | - -Using the calculations in the O-RAN CUS Specification [2] clause 7.7.6 for the test waveform described above, the ID of the last RBG will be 17, $f(0)$ will be 16, $f(n)$ will be 16 and $f(\text{lastRbgID})$ will be 1 (17 total RBGs). StartPrbc will be zero and numPrbc will be 273. If the radio does not support this numerology the following table will apply. The number of PRBs correspond to Table 3.2.3-2: - -**Table 3.2.3-2 Stock Data Sections.** - -| # PRBs per Symbol (11-79) | | | | | | | | | | | -|---------------------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|---------| -| max PRB/sym | 11 | 24 | 25 | 32 | 50 | 51 | 52 | 65 | 66 | 79 | -| numPRBc | 11 | 24 | 25 | 32 | 50 | 51 | 52 | 65 | 66 | 79 | -| rbgSize | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| lastRbgID | 2 | 5 | 6 | 7 | 6 | 6 | 6 | 8 | 8 | 4 | -| $f(0)$ | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| $f(n)$ | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| F(lastRbgID) | 3 | 4 | 1 | 4 | 2 | 3 | 4 | 1 | 2 | 15 | -| rbgMask (Hex) | 000000
5 | 000003
D | 000007
D | 00000F
D | 000007
D | 000007
D | 000007
D | 00001F
D | 00001F
D | 000001D | - -| # PRBs per Symbol (100-273) | | | | | | | | | | | -|-----------------------------|---------|---------|---------|---------|---------|---------|---------|---------|---------|---------| -| max PRB/sym | 100 | 106 | 107 | 132 | 133 | 135 | 162 | 217 | 270 | 273 | -| numPRBc | 100 | 106 | 107 | 132 | 133 | 135 | 162 | 217 | 270 | 273 | -| rbgSize | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| lastRbgID | 6 | 6 | 6 | 8 | 8 | 8 | 10 | 13 | 16 | 17 | -| $f(0)$ | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| $f(n)$ | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| F(lastRbgID) | 4 | 10 | 11 | 4 | 5 | 7 | 2 | 9 | 14 | 1 | -| rbgMask (Hex) | 000007D | 000007D | 000007D | 00001FD | 00001FD | 00001FD | 00007FD | 0003FFD | 001FFFD | 003FFFD | - -Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal. Every symbol should be described by a single type 1 section (DL-SCH and DCI) except symbols #6 and #7 which will be used for the section extension 6 test. The data in symbol #6 should be a new PN23 sequence starting in the first PRB and continuing to PRB 273 (RBG number 17). Symbol #7 should be - -identical to symbol #6. The rbgMask value should be set to 0x003FFFD and the symbolMask value should be set to 00000011000000b. No Section Type zero messages will be used for this test. - -The O-DU emulator will build a U-Plane message containing the PN23 IQ data for the first 16 PRBs (RBG 0), this message will have the section ID used in the C-Plane message described above. Another U-Plane message will be created using the same section ID but with the PN23 data for RBGs 2-17 in it. The same U-Plane messages will be used for symbol #7. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should only contain the same PN23 signals that were sent in the U-Plane, that is the PN23 sequence in the first 16 PRBs, nothing in the next 16 PRBs and the remainder of the PN23 sequence in RBGs 2-17. - -### 3.2.3.1.11 UC Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 6 3GPP UL – Resource Allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to validate the capability of interpreting the section extension 6, non-contiguous PRB allocation to the basic uplink test. - -Validate correct uplink operation of the O-RU using 3GPP Reference Sensitivity level definition (clause 7.2 ETSI TS 138.141-1) of the Conducted Receiver Characteristic Test (clause 7 ETSI TS 138.141) and power Levels at least 30 dB above Reference Sensitivity power Level described in ETSI TS 138.141-1 Table 7.2.5-1. This is to improve the likelihood that all data will be received by the radio correctly since we are not interested in testing receiver sensitivity but only the O-RAN protocol compliance. C-Plane messages will contain 2 symbols with the same set of non-contiguous PRBs referenced to test both the symbolMask and the rbgMask. - -![Figure 3.2.3.1-15: 3GPP G-FR1-A1-5: SCS30k_51RB 100 MHz Uplink FDD Test Signal. The figure consists of two main parts. The top part is a 'Channel Allocation' plot showing CRB for n1 (0 to 273) on the y-axis and Slot (0 to 20) on the x-axis. A blue band representing UL-SCH is visible from CRB 0 to 51 across all slots. The bottom part is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' plot showing Subcarrier (0 to 12) on the y-axis and Symbol (0 to 13) on the x-axis. Red blocks indicate data in symbols 2 and 11, while blue blocks indicate data in other symbols.](6127ca80a1bc3d6a86b357a6ac43cb98_img.jpg) - -**3GPP G-FR1-A1-5: SCS30k\_51RB 100 MHz Uplink FDD Test Signal** - -- All the Physical Uplink Shared Channels (all PRBs shown in Blue) are populated with test data as described in each test case. -- There is no UCI or SRS data -- Each Slot contains uplink data in each symbol except symbols 2 and 11 which contain DMRS signals only as shown in Red. - -Figure 3.2.3.1-15: 3GPP G-FR1-A1-5: SCS30k\_51RB 100 MHz Uplink FDD Test Signal. The figure consists of two main parts. The top part is a 'Channel Allocation' plot showing CRB for n1 (0 to 273) on the y-axis and Slot (0 to 20) on the x-axis. A blue band representing UL-SCH is visible from CRB 0 to 51 across all slots. The bottom part is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' plot showing Subcarrier (0 to 12) on the y-axis and Symbol (0 to 13) on the x-axis. Red blocks indicate data in symbols 2 and 11, while blue blocks indicate data in other symbols. - -**Figure 3.2.3.1-15 G-FR1-A1-5 UL FDD Test Signal** - -Using an RF source, the test equipment will generate a 3GPP test signal as shown in Figure 3.2.3.1-15 above. The radio will demodulate and decode this signal and send frequency domain IQ to the O-DU-Emulator as instructed by the O-DU-emulator using uplink C-Plane messages containing section extension 6. Note this signal has 20 slots with all symbols populated with only uplink shared data in the only first 51 RBs. The symbols are populated with PN23 data. - -The TER (Test Equipment, O-RU) generates an uplink signal on the antenna connector or TAB connector, together with the corresponding C-Plane messages on the Fronthaul interface. - -The TER will capture the U-Plane messages generated by the DUT and validate if the payload matches with the uplink signal. - -It applies to the O-RAN CUS Specification [2]: - -- Clause 7.4 -- Clause 8.3.2 -- Clause 8.3.3 - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in ETSI TS 138.141-1 clause G-FR1-A1-5. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. The radio must report that it supports section extension type 6, non-contiguous PRB allocations. Note this signal may be changed to any of the 3GPP sensitivity test signals in Table A.1-1 in ETSI TS 138.141-1 if the radio does not support the numerology and bandwidth used in this test. The test signal described in this section will be used if the radio supports that numerology and bandwidth. - -## C. Test Methodology - -Leverage from the well-known payload (Pseudo Random sequence) of the uplink signal to compare it with the payload of the signal communicated on the O-RAN interface. The IQ information is extracted from the U-Plane message and demodulated to retrieve payload. - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal source to the O-RU antenna port and configure the source to transmit the required 3GPP test signal upon receiving a trigger signal from the CUSM-E. The signal source power level should be adjusted to at least 30 dB above the setting used in the 3GPP receiver sensitivity test. - -### b. Procedure - -- Load uplink test waveform (G-FR1-A1-5 : SCS130k\_51RB) on the RF signal source. Note this signal should contain a new PN23 sequence as user data in PRBs 0 through 51 for symbols 6 and 7. The remainder of the test waveform may be left unallocated or allocated as described in 3GPP. -- Configure signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that C-Plane messages have been sent. -- Load C-Plane message sequence on Test Equipment O-RU (TER) – Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal. For this test symbols number 6 and 7 will be used in each slot. The starting PRB will be zero and number of PRBs will be 51. The resource block group size will be 8. Using the calculations in the O-RAN CUS Specification [2], clause 7.7.6, the ID of the last RBG will be 6, f(0) will be 8, f(n) will be 8 and f(lastRbgID) will be 3. StartPrbc will be zero and numPrbc will be 51. - -If symbols other than #6 and #7 are allocated, every symbol should be described by multiple type 1 section (DL-SCH and DCI) except symbols #6 and #7 which will be used for the section extension 6 test. The data in symbol #6 is expected to be a new PN23 sequence starting in the first PRB and continuing to PRB 48 (RBG number 2). Symbol #7 should be identical to symbol #6. The rbgMask value should be set to 0x000007D and the symbolMask value should be set to 00000011000000b. No Section Type zero messages will be used for this test. - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and trigger the source to play the RF signal on a frame boundary. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information -- Extract Payload -- Compare payload binary sequences - -## D. Test Requirement (expected result) - -1. The verdict is “Test pass” if the test frame received by the signal analyser contains the same PN23 signals that were sent in the U-Plane, that is the PN23 sequence in the first 16 PRBs, nothing in the next 16 PRBs and the remainder of the PN23 sequence in RBGs 2 (Next 16 PRBs). -2. If any of the test conditions is not true, the verdict for the whole test is "Fail". - -### 3.2.3.1.12 UC-Plane O-RU Scenario Class Section Extension 10 – Multiple Port Grouping DL – Resource allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages when section extension 10 is supported by the radio, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink. This test is applicable for Category A and Category B radios (No precoding is required). The test will be conducted therefore there will be no channel distortion or interference. Note the purpose of this test is not to test the use of section extension 10 with either section extension 1 or 2 (Real time beam weights or attributes) since these are special conditions. There are four versions of beam groupings: Common Beam, beam matrix indication, beam vector listing and beamId/ueId listing with associated port-list index. Each of these will be tested. The beamforming measurements will be conducted using the method described in clause 3.2.3.2.3 and 3.2.3.2.4 (Predefined beamforming). - -Using a standard 3GPP NR-FR1-TM1.1 test frame for FDD the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink the standard NR-FR1-TM1.1 signal. This signal is shown below in Figure 3.2.3.1-16. - -![Figure 3.2.3.1-16 NR-FR1-TM1.1 FDD Test Signal. The figure contains three main visual elements: 1. A top screenshot of a resource grid showing CRB for u=1 across 20 slots. The y-axis ranges from 0 to 273. A red box highlights the first 3 PRBs (0-2) in the first two symbols of every slot, indicating DCI. 2. A middle-left zoomed-in view of the first few symbols and PRBs, with red circles highlighting the DCI area (first 3 PRBs of first 2 symbols) and the DMRS area (symbols 2 and 11). 3. A middle-right 'RB Resource Mapping for DL-SCH1 (Modulation = QPSK)' grid showing subcarriers 0-11 on the y-axis and symbols 0-13 on the x-axis. Red blocks indicate data in symbols 0 and 1, while green blocks indicate data in other symbols. A central text box provides details about the signal structure.](b7e4791d0f2b4881a99344168f47638b_img.jpg) - -**3GPP NR-FR1-TM1.1 FDD Test Signal** - -- All the Physical Downlink Shared Channels (all PRBs that are not DCI) are populated with test data as described in each test case. -- DCI information is the first 3 PRBs in the first 2 symbols of every slot. The DCI data is set to all zeros. -- Each Slot contains downlink data in each symbol except symbols 2 and 11 which contain DMRS signals (Red) and user data as shown in Green. - -Figure 3.2.3.1-16 NR-FR1-TM1.1 FDD Test Signal. The figure contains three main visual elements: 1. A top screenshot of a resource grid showing CRB for u=1 across 20 slots. The y-axis ranges from 0 to 273. A red box highlights the first 3 PRBs (0-2) in the first two symbols of every slot, indicating DCI. 2. A middle-left zoomed-in view of the first few symbols and PRBs, with red circles highlighting the DCI area (first 3 PRBs of first 2 symbols) and the DMRS area (symbols 2 and 11). 3. A middle-right 'RB Resource Mapping for DL-SCH1 (Modulation = QPSK)' grid showing subcarriers 0-11 on the y-axis and symbols 0-13 on the x-axis. Red blocks indicate data in symbols 0 and 1, while green blocks indicate data in other symbols. A central text box provides details about the signal structure. - -**Figure 3.2.3.1-16 NR-FR1-TM1.1 FDD Test Signal** - -This test frame consists of a PDCCH in the first two symbols of every slot consisting of 3 PRBs. All the remaining PRBs in the frame consist of Physical Downlink Shared Channel data. This test requires non-zero data (PN23 Sequence) to populate all allocated resource blocks. This configuration corresponds to stock data section A in all symbols that do not contain PDCCH channels. - -For this test the O-RU will indicate the default eAxC ID to use indicating this port grouping as well as the number of ports in this grouping, call this value nPG. - -**B. Test Entrance Criteria** - -The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause NR-FR1-TM1.1. It will be for 5G New Radio only. - -There will be numPortc “layers” or eAxCs referred to in the test. That is there will be one C-Plane message referencing the port group eAxC ID obtained from the M-Plane but numPortc U-Plane messages. For Test Case#4, (beamGroupType = 11b, beamId/ueId listing with associated port-list index), O-RU will advertise over M-Plane support for Section Extension 10, beamGroupType = 11b by setting the flag se-10-bgt-11b-supported = TRUE. - -Manufacturers’ must provide their defined list of beam indices and their associated magnitude and phase relation between antenna ports or TAB connectors and/or beam directions with antenna array characteristics. - -## C. Test Methodology - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna ports being tested and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. Use the O-DU emulator control interface to build the appropriate C-Plane message that describes the signal. This message should include section extension 10. Note the test will be performed four times exercising all four beam group types. Every symbol should be described by a single section (DL-SCH and DCI) using Section Type 1 messages. The data in the sections must be a PN23 sequence using an initial seed of all ones. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for each layer (i.e. numPortc repetitions). - -Test case #1 (beamGroupType = 00b, Common Beam): - -For this test the beamGroupType parameter should be set to 00b. It is expected that all layers will be played on the same beam ID and this is the beam ID used in the corresponding C-Plane message. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. Use the signal analyser to decode at least two beams and ensure they are the same. - -Test case #2 (beamGroupType = 01b, beam matrix indication): - -For this test the beamGroupType parameter should be set to 01b. It is expected that all layers will be played on consecutive beam IDs starting with the beam ID in the C-Plane message. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. Use the signal analyser to decode at least two beams and ensure they meet the consecutive beam criteria. - -Test case #3 (beamGroupType = 10b, beam vector listing): - -For this test the beamGroupType parameter should be set to 10b. In this case the section extension should list “numPortc” beam IDs in section extension 10. It is expected that all layers will be played on the beam IDs indicated in the section extension. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. Use the signal analyser to decode at least two beams and ensure they agree with the beam vector listing. - -Test case #4 (beamGroupType = 11b, beamId/ueId listing with associated port-list index): - -For this test the beamGroupType parameter should be set to 11b. With the usage of this beamGroupType, O-DU can pick arbitrary eAxC-ID value(s) from the M-Plane configured port-list and specify the associated beamId/ueId in the section extension. Hence, in this case the section extension should list “numPorte” value equal to the number of “portListIndex” values in the section extension. Each “portListIndex” indicates the index of an eAxC-ID in the port-list. It is expected that only the layers associated with specified “portListIndex” will be played on the beam IDs indicated in the section extension. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. Use the signal analyser to decode at least two beams and ensure they agree with the beam vector listing. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above. -3. If it contains all the same PRB assignments and data, and the beams are measured as described in test cases #1 through #3 above the test passes. - -### 3.2.3.1.13 UC Plane O-RU Scenario Class Extended multiple port grouping using section extension 10 UL– Resource Allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to validate the capability of interpreting the section extension 10, multiple port groupings in the basic uplink test. - -Validate correct uplink operation of the O-RU using 3GPP Reference Sensitivity level definition (Section 7.2 ETSI TS 138.141-1) of the Conducted Receiver Characteristic Test section (Section 7 ETSI TS 138.141) and power Levels at least 30 dB above Reference Sensitivity power Level described in ETSI TS 138.141-1 Table 7.2.5-1. This is to improve the likelihood that all data will be received by the radio correctly since we are not interested in testing receiver sensitivity but only the O-RAN protocol compliance. Note the purpose of this test is not to test the use of section extension 10 with either section extension 1 or 2 (Real time beam weights or attributes) since these are special conditions. There are four versions of beam groupings: Common Beam, beam matrix indication, beam vector listing and beamId/ueId listing with associated port-list index. Each of these will be tested. The beamforming measurements will be conducted using the method described in clause 3.2.3.2.3 and 3.2.3.2.4 (Predefined beamforming). - -Only Section Type 1 messages will be used in this test. - -![Figure 3.2.3.1-17: 3GPP G-FR1-A1-5: SCS30k_51RB 100 MHz Uplink FDD Test Signal. The figure consists of two main parts. The top part is a 'Channel Allocation' plot showing CRB for ur1 across 20 slots, with a blue bar indicating the UL-SCH signal. The bottom part is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' plot showing subcarriers (0-11) across symbols (0-13). Red boxes indicate data in symbols 2 and 11, while blue boxes indicate data in other symbols. A legend on the right explains that all PRBs are populated with test data, there is no UCI or SRS data, and symbols 2 and 11 contain DMRS signals.](ac768d795629007e1bf7c94829aba60b_img.jpg) - -3GPP G-FR1-A1-5: SCS30k\_51RB 100 MHz Uplink FDD Test Signal - -Channel Allocation - -CRB for ur1 - -FrameIndex: 0 - -UL-SCH - -ur1: 20 Slot - -RB Resource Mapping for UL-SCH1 (Modulation = QPSK) - -Subcarrier - -Symbol - -- All the Physical Uplink Shared Channels (all PRBs shown in Blue) are populated with test data as described in each test case. -- There is no UCI or SRS data -- Each Slot contains uplink data in each symbol except symbols 2 and 11 which contain DMRS signals only as shown in Red. - -Figure 3.2.3.1-17: 3GPP G-FR1-A1-5: SCS30k\_51RB 100 MHz Uplink FDD Test Signal. The figure consists of two main parts. The top part is a 'Channel Allocation' plot showing CRB for ur1 across 20 slots, with a blue bar indicating the UL-SCH signal. The bottom part is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' plot showing subcarriers (0-11) across symbols (0-13). Red boxes indicate data in symbols 2 and 11, while blue boxes indicate data in other symbols. A legend on the right explains that all PRBs are populated with test data, there is no UCI or SRS data, and symbols 2 and 11 contain DMRS signals. - -Figure 3.2.3.1-17 G-FR1-A1-5 UL FDD Test Signal - -Using an RF source, the test equipment will generate a 3GPP test signal as shown in Figure 3.2.3.1-17 above. The radio will demodulate and decode this signal and send frequency domain IQ to the O-DU-Emulator as instructed by the O-DU-emulator using uplink C-Plane messages containing section extension 10. Note this signal has 20 slots with all symbols populated with only uplink shared channel data in the only first 51 RBs. The symbols are populated with PN23 data. - -The TER (Test Equipment, O-RU) generates an uplink signal on the antenna connectors or TAB connectors, together with the corresponding C-Plane messages on the Fronthaul interface. - -The TER will capture the U-Plane messages generated by the DUT and validate if the payload matches with the uplink signal. - -It applies to the O-RAN CUS Specification [2]: - -- Clause 7.4 -- Clause 8.3.2 -- Clause 8.3.3 - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in ETSI TS 138.141-1 clause G-FR1-A1-5. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. The radio must report that it supports section extension type 10, multiple port groupings. For Test Case#4, (beamGroupType = 11b, beamId/ueId listing with associated port-list index), O-RU will advertise over M-Plane support for Section Extension 10, beamGroupType = 11b by setting the flag se-10-bgt-11b-supported = TRUE. Note this signal may be changed to any of the 3GPP sensitivity test signals in Table A.1-1 in ETSI TS 138.141-1 if the radio does not support the numerology and bandwidth used in this test. The test signal described in this section will be used if the radio supports that numerology and bandwidth. Manufacturers’ must provide their defined list of beam indices and their associated magnitude and phase relation between antenna ports or TAB connectors and/or beam directions with antenna array characteristics. - -## C. Test Methodology - -Leverage from the well-known payload (Pseudo Random sequence) of the uplink signal to compare it with the payload of the signal communicated on the O-RAN interface. The IQ information is extracted from the U-Plane message and demodulated to retrieve payload. Signals will be applied to connector ports emulating the phase and amplitude corresponding to the associated beam ID direction or phase relationship provided by the manufacturer. - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal source to the O-RU antenna ports that belong to the beam under test and configure the source to transmit the required 3GPP test signal upon receiving a trigger signal from the CUSM-E. Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. The signal source power level should be adjusted to at least 30 dB above the setting used in the 3GPP receiver sensitivity test. Let the DUT and TER to warm to the normal operating temperature within specified range - -### b. Procedure - -- Load uplink test waveform (G-FR1-A1-5 : SCS130k\_51RB) on the RF signal source. Note this signal should contain a new PN23 sequence as user data in PRBs 0 through 51 for symbols 6 and 7. The remainder of the test waveform is as described in 3GPP. -- Configure signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that C-Plane messages have been sent. -- Inject the test signal into the O-RU with the application of an initial set of beamweights, or equivalently magnitude and phase relation, between all the TER ports connected to the antenna ports (or TAB connectors) to emulate the phase and magnitude difference “seen” by the antenna elements under test. For example, initial beamweights could be set to be “all equal” (i.e. no beamforming). -- Load C-Plane message sequence on Test Equipment O-RU (TER) – Use the O-DU emulator control interface to build the appropriate C-Plane message (Single C-Plane message) that describes the signal. For this test symbols number 6 and 7 will be used in each slot. - -Every symbol should be described by a single type 1 section (DL-SCH and DCI) except symbols #6 and #7 which will be used as the payload data. The data in symbol #6 is expected to be a new PN23 sequence starting in the first PRB and continuing to PRB 51. Symbol #7 should be identical to symbol #6. No Section Type zero messages will be used for this test. The C-Plane message should include section extension 10 with numPortc equal to what was received on the M-Plane at startup. The eAxC ID should be the group eAxC ID also received from the M-Plane. Run the test four times using: - -Test Case #1 (beamGroupType = 00b, Common Beam): All layers should have the same beam ID. The signal sent by the source should correspond to the same beam ID. It is expected that the source is connected to at least two port groups to ensure the same beam is being used. - -Test Case #2 (beamGroupType = 01b, beam matrix indication): All layers should have consecutive beam IDs starting with the beam ID in the C-Plane message. The signal sent by the source should correspond to the consecutive beam IDs. It is expected that the source is connected to at least two port groups to ensure the consecutive beams are being used. - -Test Case #3 (beamGroupType = 10b, beam vector listing): All layers will be assigned beam IDs based on the list of beam IDs contained in the section extension. The number of beam IDs must be equal to numPortc. The signal sent by the source should correspond to the signalled beam IDs. It is expected that the source is connected to at least two port groups to ensure that the correct beams are being used. - -Test case #4 (beamGroupType = 11b, beamId/uId listing with associated port-list index): - -For this test the beamGroupType parameter should be set to 11b. With the usage of this beamGroupType, O-DU can pick arbitrary eAxC-ID value(s) from the M-Plane configured port-list and specify the associated beamId/ueId in the section extension. Hence, in this case the section extension should list “numPorts” value equal to the number of “portListIndex” values in the section extension. Each “portListIndex” indicates the index of an eAxC-ID in the port-list. The signal sent by the source should correspond to the signalled beam IDs associated with eAxC-ID indexed by specified “portListIndex”. It is expected that the source is connected to at least two port groups to ensure that the correct beams are being used. - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane message and trigger the source to play the RF signal on a frame boundary. Respect all timing windows. -- Signal the signal source that C-Plane messages have been sent to allow it to start sending RF. Respect all timing windows. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information -- Extract Payload -- Compare payload binary sequences - -#### D. Test Requirement (expected result) - -1. The test frame received by the signal analyser must contain the same PN23 signals that were sent in the U-Plane. -The beamweights or magnitude and phase relation at the antenna ports (or TAB connectors) of the test signal that achieves the best performance (i.e. highest EVM, power, SNR, etc.) should match the manufacturer's declaration of the beam under test. If this is also true, the test passes. - -### 3.2.3.1.14 UC-Plane O-RU Scenario Class Extended 3GPP DL – Resource allocation – Coupling C and U plane via Frequency and Time - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink when the radio reports it supports the option feature of coupling C and U plane messages via frequency and time. This test is applicable for Category A and Category B radios (No precoding is required). The test will be conducted therefore there will be no channel distortion or interference. It is mandatory the radio pass this test if it reports it supports coupling C and U plane via time and frequency. - -Using a standard 3GPP NR-FR1-TM1.1 test frame for FDD the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink the standard NR-FR1-TM1.1 signal. This signal is shown below in Figure 3.2.3.1-18. - -![Figure 3.2.3.1-18: NR-FR1-TM1.1 FDD Test Signal. The figure shows three resource block (RB) mapping diagrams. The top diagram shows the full frame (Slot 0 to 19) with CRB indices 0 to 273. A red box highlights the first two symbols of Slot 0. The middle-left diagram is a zoomed-in view of Slot 0, showing CRB indices 0 to 46. The middle-right diagram shows the RB Resource Mapping for DL-SCH (Modulation = QPSK) for Slot 0, with Subcarriers 0 to 12 on the y-axis and Symbols 0 to 13 on the x-axis. Red blocks indicate DCI in the first two symbols, and green blocks indicate DL-SCH data in the remaining symbols. The bottom diagram shows another frame view with CRB indices 0 to 273.](8ed67838d44c23a50ca30525456d38be_img.jpg) - -**3GPP NR-FR1-TM1.1 FDD Test Signal** - -- All the Physical Downlink Shared Channels (all PRBs that are not DCI) are populated with test data as described in each test case. -- DCI information is the first 3 PRBs in the first 2 symbols of every slot. The DCI data is set to all zeros. -- Each Slot contains downlink data in each symbol except symbols 2 and 11 which contain DMRS signals (Red) and user data as shown in Green. - -Figure 3.2.3.1-18: NR-FR1-TM1.1 FDD Test Signal. The figure shows three resource block (RB) mapping diagrams. The top diagram shows the full frame (Slot 0 to 19) with CRB indices 0 to 273. A red box highlights the first two symbols of Slot 0. The middle-left diagram is a zoomed-in view of Slot 0, showing CRB indices 0 to 46. The middle-right diagram shows the RB Resource Mapping for DL-SCH (Modulation = QPSK) for Slot 0, with Subcarriers 0 to 12 on the y-axis and Symbols 0 to 13 on the x-axis. Red blocks indicate DCI in the first two symbols, and green blocks indicate DL-SCH data in the remaining symbols. The bottom diagram shows another frame view with CRB indices 0 to 273. - -**Figure 3.2.3.1-18 NR-FR1-TM1.1 FDD Test Signal** - -This test frame consists of a PDCCH in the first two symbols of every slot consisting of 3 PRBs. All the remaining PRBs in the frame consist of Physical Downlink Shared Channel data. This test requires non-zero data (PN23 Sequence) to populate all allocated resource blocks. This configuration corresponds to stock data section A in all symbols that do not contain PDCCH channels. - -**B. Test Entrance Criteria** - -The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in section NR-FR1-TM1.1. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. - -**C. Test Methodology** - -**a. Initial Conditions** - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. This test is only applicable if the radio reports it supports coupling C and U plane via time and frequency. - -**b. Procedure** - -Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal. Every symbol should be described by a single section (DL-SCH and DCI) using Section Type 1 messages. The data in the sections must be a PN23 sequence using an initial seed of all ones. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU - -respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -In this test the C-Plane messages will contain valid values in the following fields: - -- EAxC ID -- Datadirection bit (Downlink) -- Frame ID, subframeID, slotID, startSymbolID, and NumSymbol -- SectionID must have a value 4095 -- SymInc, rb reMask and section extension #6 are *not* used in this test - -The U-Plane messages generated by the TER must match those values used in the C-Plane corresponding to the section described in the C-plane but the value of sectionID will be 4095. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above. If it contains all the same PRB assignments and data, the test passes. - -### 3.2.3.1.15 UC-Plane O-RU Base Class FDD Test UL – Coupling C and U plane via time and frequency - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can meet the most basic uplink requirements for O-RAN fronthaul correctly interpreting C-Plane messages and correctly constructing uplink U-Plane messages from an RF signal when the radio reports it supports C and U plane coupling via time and frequency. - -The test validates that correct uplink operation of the O-RU using 3GPP Reference Sensitivity level definition (Clause 7.2 ETSI TS 138.141-1) of the Conducted Receiver Characteristic Test (clause 7 ETSI TS 138.141) and power Levels at least 30 dB above Reference Sensitivity power Level described in ETSI TS 138.141-1 Table 7.2.5-1. This is to improve the likelihood that all data will be received by the radio correctly since we are not interested in testing receiver sensitivity but only the O-RAN protocol compliance. - -![Figure 3.2.3.1-19: 3GPP G-FR1-A1-5: SCS30k_51RB 100 MHz Uplink FDD Test Signal. The figure consists of two main parts. The top part is a 'Channel Allocation' plot showing CRB for u=1 on the y-axis (0 to 250) against Slot on the x-axis (0 to 20). A blue band labeled 'UL-SCH' is visible from CRB 0 to 46 across all slots. The bottom part is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' plot showing Subcarrier on the y-axis (0 to 12) against Symbol on the x-axis (0 to 13). Red blocks representing DMRS signals are located at symbols 2 and 11 across all subcarriers. Blue blocks represent uplink data. To the right of the plots, a list of notes explains that all PRBs are populated with test data, there is no UCI or SRS data, and symbols 2 and 11 contain DMRS signals only.](6a0edaeb8af1f2308513a8f98ce9aaa0_img.jpg) - -**3GPP G-FR1-A1-5: SCS30k\_51RB 100 MHz Uplink FDD Test Signal** - -- All the Physical Uplink Shared Channels (all PRBs shown in Blue) are populated with test data as described in each test case. -- There is no UCI or SRS data -- Each Slot contains uplink data in each symbol except symbols 2 and 11 which contain DMRS signals only as shown in Red. - -Figure 3.2.3.1-19: 3GPP G-FR1-A1-5: SCS30k\_51RB 100 MHz Uplink FDD Test Signal. The figure consists of two main parts. The top part is a 'Channel Allocation' plot showing CRB for u=1 on the y-axis (0 to 250) against Slot on the x-axis (0 to 20). A blue band labeled 'UL-SCH' is visible from CRB 0 to 46 across all slots. The bottom part is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' plot showing Subcarrier on the y-axis (0 to 12) against Symbol on the x-axis (0 to 13). Red blocks representing DMRS signals are located at symbols 2 and 11 across all subcarriers. Blue blocks represent uplink data. To the right of the plots, a list of notes explains that all PRBs are populated with test data, there is no UCI or SRS data, and symbols 2 and 11 contain DMRS signals only. - -**Figure 3.2.3.1-19 G-FR1-A1-5 Uplink FDD Test Signal** - -This signal is described by Table A.1-1 in ETSI TS 138.141-1 and is referred to as G-FR1-A1-5 with the power increased to up to 30 dB above that described in Table 7.2.5-1. Under those conditions, a 3GPP compliant O-RU should deliver uplink U-Plane information that matches the uplink signal. - -The TER (Test Equipment, O-RU) generates an uplink signal on the antenna connector or TAB connector, together with the corresponding C-Plane messages on the Fronthaul interface. - -The TER will capture the U-Plane messages generated by the DUT and validate whether the payload matches the uplink signal. - -It applies to the O-RAN CUS Specification [2]: - -- Clause 7.4 -- Clause 8.3.2 -- Clause 8.3.3 - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The O-RU must indicate it supports coupling C and U plane via time and frequency. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in ETSI TS 138.141-1 clause G-FR1-A1-5. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. Note this signal may be changed to any of the 3GPP sensitivity test signals in Table A.1-1 in ETSI TS 138.141-1 if the radio does not support the numerology and bandwidth used in this test. The test signal described in this clause will be used if the radio supports that numerology and bandwidth. - -**C. Test Methodology** - -Leverage from the well-known payload (PN23 sequence) of the uplink signal to compare it with the payload of the signal communicated on the O-RAN interface. The IQ information is extracted from the U-Plane message and demodulated to retrieve payload. - -#### a: Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal source to the O-RU antenna port and configure the source to transmit the required 3GPP test signal upon receiving a trigger signal from the CUSM-E. The signal source power level should be adjusted to at least 30 dB above the setting used in the 3GPP receiver sensitivity test. - -#### b: Procedure - -- Load uplink test waveform (G-FR1-A1-5 : SCS30k\_51RB) on the RF signal source -- Configure signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that C-Plane messages have been sent. -- Load C-Plane message sequence on Test Equipment O-RU (TER) C-Plane messages will contain valid values in the following fields: - - EAxC ID - - Datadirection bit (Uplink) - - Frame ID, subframeID, slotID, startssymbolID, and NumSymbol - - SectionID must have a value 4095 - - SymInc, rb reMask and section extension #6 are *not* used in this test -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the RF uplink frame after the C-Plane messages have been sent honouring timing windows -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- TER will arrange U-Plane messages according to time and frequency -- Extract IQ information -- Extract Payload -- Compare payload binary sequences - -#### D. Test Requirement (expected result) - -1. The verdict is “Test pass” if the payload binary sequences match between the uplink test frame sent to the DUT and the received U-Plane data from the DUT -2. If any of the test conditions are not true, the verdict for the whole test is "Fail" - -### 3.2.3.1.16 UC- Plane O-RU Scenario Class Extended 3GPP DL – Resource allocation – Section Description Priorities - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink when the radio reports it supports the option feature of coupling C and U plane messages via frequency and time and Section Description Priorities. This test is applicable for Category A and Category B radios (No precoding is required). The test will be conducted therefore there will be no channel distortion or interference. It is mandatory the radio pass this test if it reports it supports coupling C and U plane via time and frequency. Note, there are two versions of this feature: coupling C and U plane messages via frequency and time and Section Description Priorities and - -coupling C and U plane messages via frequency and time and Section Description Priorities (optimized). This test requires both tests to be performed if the radio supports both methods otherwise only one test is to be performed if the radio only supports one of these methods. These methods are listed under test methodology below. - -Using a standard 3GPP NR-FR1-TM1.1 test frame for FDD the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink the standard NR-FR1-TM1.1 signal with exceptions noted in the test procedure. This signal is shown below in Figure 3.2.3.1-20 . - -![Figure 3.2.3.1-20 NR-FR1-TM1.1 FDD Test Signal. The figure displays three resource grid visualizations. The top grid shows the full frame structure with a legend for DCI (green) and DL-SCH (blue). The middle-left grid is a zoomed-in view of the first two symbols of a slot, highlighting the 3 PRBs used for DCI. The middle-right grid shows the RB Resource Mapping for DL-SCH1 (Modulation = QPSK) across 12 subcarriers and 13 symbols, with red blocks indicating data. The bottom grid shows another frame structure view. A central text box lists key characteristics of the test signal.](6ed375302d877b2f8bb27e4d98995b51_img.jpg) - -**3GPP NR-FR1-TM1.1 FDD Test Signal** - -- All the Physical Downlink Shared Channels (all PRBs that are not DCI) are populated with test data as described in each test case. -- DCI information is the first 3 PRBs in the first 2 symbols of every slot. The DCI data is set to all zeros. -- Each Slot contains downlink data in each symbol except symbols 2 and 11 which contain DMRS signals (Red) and user data as shown in Green. - -Figure 3.2.3.1-20 NR-FR1-TM1.1 FDD Test Signal. The figure displays three resource grid visualizations. The top grid shows the full frame structure with a legend for DCI (green) and DL-SCH (blue). The middle-left grid is a zoomed-in view of the first two symbols of a slot, highlighting the 3 PRBs used for DCI. The middle-right grid shows the RB Resource Mapping for DL-SCH1 (Modulation = QPSK) across 12 subcarriers and 13 symbols, with red blocks indicating data. The bottom grid shows another frame structure view. A central text box lists key characteristics of the test signal. - -Figure 3.2.3.1-20 NR-FR1-TM1.1 FDD Test Signal - -This test frame consists of a PDCCH in the first two symbols of every slot consisting of 3 PRBs. All the remaining PRBs in the frame consist of Physical Downlink Shared Channel data. This test requires non-zero data (PN23 Sequence) to populate all allocated resource blocks. This configuration corresponds to stock data section A in all symbols that do not contain PDCCH channels. - -**B. Test Entrance Criteria** - -The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause NR-FR1-TM1.1. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. - -**C. Test Methodology** - -**a. Initial Conditions** - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. This test is only applicable if the radio reports it supports coupling C and U plane via time and frequency and Section Description Priority (including the optimized version). - -**b. Procedure for Coupling C and U plane messages via frequency and time with section priorities** - -Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above and below in the O-DU emulator. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal. Every symbol should be described by a single section (DL-SCH and DCI) using Section Type 1 messages. The data in the sections must be a PN23 sequence using an initial seed of all ones. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -**Table 3.2.3-2 Section Description Priorities.** - -| # | Section ext 6 | priority | symbolMask | start Prbc | numPrbc | reMask | rbgMask | beamId | numSymbol | Note | -|---|---------------|----------|---------------------------------------------------------------------------------------------------------|------------|---------|--------------|------------|--------|-----------|-------------------------------| -| 1 | yes | +1 | 000000000000100 | 0 | 192 | 010001000100 | 0xFFFFFC00 | 1 | 1 | CSI reference signal (CSI-RS) | -| 2 | yes | +1 | 001000000000000 | 0 | 192 | 010001000100 | 0xFFFFFC00 | 2 | 1 | CSI reference signal (CSI-RS) | -| 3 | no | 0 | 111110000000000

Not used in this section without section extension 6. Just shown for information | 0 | 273 | 111111111111 | N/A | 100 | 5 | UE1 | -| 4 | yes | 0 | 000000000001100 | 15 | 32 | 111111111111 | 0x6000000 | 200 | 2 | UE2 | -| 5 | no | 0 | 00000111110000

Not used in this section without section extension 6. Just shown for information | 31 | 48 | 111111111111 | N/A | 300 | 5 | UE3 | -| 6 | no | 0 | 000000000000011

Not used in this section without section extension 6. Just shown for information | 10 | 2 | 111111111111 | N/A | 3 | 2 | Special channel | - -In this test the section configuration will be as shown in Table 3.2.3-2 above. The 6 sections will comprise one slot and this slot will be repeated continuously to synchronize the TER signal analyser. The six sections will be sent on one C-Plane message using C and U plane coupling via time and frequency. The configuration above follows the example given in the CUSM specification. - -The section numbers in the above Table do not represent SectionID numbers but individual sections. Sections #1 and #2 describe hypothetical CSI-RS signals sent in symbols #2 and #11 in each slot. These signals have sub-carriers masked by reMask. The CSI-RS signals generation follows ETSI TS 138.211 V16.2.0 (or after), clause 7.4.1.5 with nID = 0, row 1, N=1 and L=1. These sections use section extension 6 and contain a higher priority than all other sections. - -Section #3 describes PN23 data sent to hypothetical UE #1 it overlaps REs in sections #1 and #2 but has a lower priority so sections #1 and #2 are valid. Since section #3 has contiguous symbols section extension 6 is not needed. - -Section #4 is for hypothetical UE #2. It shares symbol 2 with the CSI-RS signal in Section #1. Since the symbols are not contiguous, it uses section extension 6 but the priority is set to the default 0. - -Section #5 is for hypothetical UE #3 and uses a contiguous set of symbols so section extension 6 is not needed. It does not overlap any other signals. This section is optional because it does not test Section Description Priority. - -Section #6 is a hypothetical special channel using two symbols and does not require section extension 6. This section is also optional. - -U-Plane messages will contain: - -- CSI-RS signals as described by section #1 for symbol #2 -- CSI-RS signals as described by section #2 for symbol #11 -- A new PN23 sequence in each of the last 5 symbols as described in section #3. Note that for symbol #11 the PN sequence will be pierced by the CSI-RS signals. -- A new PN23 sequence for symbol #2 as described by section #4 as well as a new PN sequence for symbol #3. These sequences are only 32 PRBs long and start in PRB 15. The sequence in symbol #2 will be pierced by CSI-RS signals. -- The user data for sections number #5 and #6 are standard PN23 sequences only for these symbols and PRBs described in the Table above. - -#### C. Procedure for Coupling C and U plane messages via frequency and time with section priorities (optimized) - -This test will be identical to the above test with the following exceptions: - -- There will be two C-Plane messages describing the downlink signal to be sent. -- The first two sections listed in the Table above (those with higher priorities) will be repeated in both C-Plane messages and will have a section ID equal to a value between 0 and “max-highest-priority-sections-per-slot” as sent on the M-Plane. -- The other sections will be divided between the two C-Plane messages and not repeated. -- The repeated C-plane message will have the “repetition” bit set to one. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same PRB assignment and data as the signal described above. -3. The beamweights or magnitude and phase relation at the antenna ports (or TAB connectors) of the test signal that achieves the highest performance (i.e. best EVM, power, SNR, etc.) should match with the manufacturer’s declaration of the beam under test that has been assigned to each section described above. The procedure for this beamforming test is the same as test 3.2.3.2.3 (UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Predefined-beam Beamforming). This result is applicable for either or both forms of this test. - -3.2.3.1.17 (VOID) - -3.2.3.1.18 UC-Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation -Section Extension 12 3GPP DL – Resource Allocation - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can correctly decode and interpret C-Plane and U-Plane messages putting resource block in the correct place in the transmitted signal using the extension type 12. In this test stock data section definition C will be used to exercise the non-contiguous RB allocation, all 273 PRBs (or the maximum number of PRBs per symbol for the highest numerology the radio supports) will be used in this test. - -Using a standard 3GPP NR-FR1-TM1.1 test frame for FDD the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink the standard NR-FR1-TM1.1 signal with the modifications described below (supporting non-contiguous PRB allocation). The standard 3GPP NR-FR1-TM1.1 is shown in Figure 3.2.3.1-21 below: - -![Figure 3.2.3.1-21: 3GPP NR-FR1-TM1.1 FDD Test Signal. The figure shows a resource grid for 20 slots. The y-axis represents CRB for u=1, ranging from 0 to 273. The x-axis represents Slot, ranging from 0 to 20. A legend indicates DCI (red) and DL-SCH (green). A callout box on the left shows a zoomed-in view of the first two symbols of a slot, highlighting the DCI region (first 3 PRBs) and the DMRS signals (symbols 2 and 11). A list of bullet points explains the signal structure: all PRBs not DCI are populated with test data; DCI is the first 3 PRBs in the first 2 symbols of every slot, set to zeros; each slot contains downlink data in every symbol except symbols 2 and 11, which contain DMRS signals (Red) and user data (Green). An inset graph titled 'RB Resource Mapping for DL-SCH1 (Modulation = QPSK)' shows the mapping for subcarriers 0-12 across symbols 0-13, with red blocks indicating DCI and green blocks indicating DL-SCH.](8c0ac6780a5e22425c185a15ffe01d7b_img.jpg) - -**3GPP NR-FR1-TM1.1 FDD Test Signal** - -- All the Physical Downlink Shared Channels (all PRBs that are not DCI) are populated with test data as described in each test case. -- DCI information is the first 3 PRBs in the first 2 symbols of every slot. The DCI data is set to all zeros. -- Each Slot contains downlink data in each symbol except symbols 2 and 11 which contain DMRS signals (Red) and user data as shown in Green. - -Figure 3.2.3.1-21: 3GPP NR-FR1-TM1.1 FDD Test Signal. The figure shows a resource grid for 20 slots. The y-axis represents CRB for u=1, ranging from 0 to 273. The x-axis represents Slot, ranging from 0 to 20. A legend indicates DCI (red) and DL-SCH (green). A callout box on the left shows a zoomed-in view of the first two symbols of a slot, highlighting the DCI region (first 3 PRBs) and the DMRS signals (symbols 2 and 11). A list of bullet points explains the signal structure: all PRBs not DCI are populated with test data; DCI is the first 3 PRBs in the first 2 symbols of every slot, set to zeros; each slot contains downlink data in every symbol except symbols 2 and 11, which contain DMRS signals (Red) and user data (Green). An inset graph titled 'RB Resource Mapping for DL-SCH1 (Modulation = QPSK)' shows the mapping for subcarriers 0-12 across symbols 0-13, with red blocks indicating DCI and green blocks indicating DL-SCH. - -**Figure 3.2.3.1-21 3GPP NR-FR1-TM1.1 Test Signal** - -This generic NR-FR1-TM1.1 test frame consists of a PDCCH in the first two symbols of every slot consisting of 3 PRBs. All the remaining PRBs in the frame consist of Physical Downlink Shared Channel data. - -This test requires non-zero data to populate all allocated resource blocks. This data will be a PN23 sequence with a seed value of all ones as described below. - -This test will utilize stock data section definition C described above with the following exception. This data section will include user data in the first RB group, the second group will be blank and the remainder of the RBGs contain user data. This stock data section will be repeated over two symbols to test the SymMask parameter. - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The default test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause NR-FR1-TM1.1. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. The Radio must support the extension type 12 as notified by the M-Plane. The signal analyser must have the ability to decode the downlink shared channel. - -**C. Test Methodology** - -**a. Initial Conditions** - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. - -**b. Procedure** - -For this test only symbols number 6 and 7 will be used in each slot. Other symbols may contain data including reference signals to ensure test equipment can synchronize with the signal. The starting PRB will be zero and number of PRBs will be chosen from one or more columns in Table 3.2.3-4 below. The resource block group size will be 16 based on ETSI TS 138.214 Table 5.1.2.2.1-1 as shown in Table 3.2.3-4 using configuration 2. - -**Table 3.2.3-4 Resource Block Group Size.** - -| Bandwidth Part Size | Configuration 1 | Configuration 2 | -|---------------------|-----------------|-----------------| -| 1 – 36 | 2 | 4 | -| 37 – 72 | 4 | 8 | -| 73 – 144 | 8 | 16 | -| 145 – 275 | 16 | 16 | - -Using the calculations in O-RAN CUS Specification [2], clause 7.7.6, for the test waveform described above, the ID of the last RBG will be 17, f(0) will be 16, f(n) will be 16 and f(lastRbgID) will be 1 (17 total RBGs). StartPrbc will be zero and numPrbc will be 273. If the radio does not support this numerology the following table will apply. The number of PRBs correspond to Table 3.2.3-5: - -**Table 3.2.3-5 Stock Data Sections.** - -| # PRBs per Symbol (11-79) | | | | | | | | | | | -|---------------------------|----|----|----|----|----|----|----|----|----|----| -| max PRB/sym | 11 | 24 | 25 | 32 | 50 | 51 | 52 | 65 | 66 | 79 | -| numPRBc | 11 | 24 | 25 | 32 | 50 | 51 | 52 | 65 | 66 | 79 | -| rbgSize | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| lastRbgID | 2 | 5 | 6 | 7 | 6 | 6 | 6 | 8 | 8 | 4 | -| f(0) | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| f(n) | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| F(lastRbgID) | 3 | 4 | 1 | 4 | 2 | 3 | 4 | 1 | 2 | 15 | - -| # PRBs per Symbol (100-273) | | | | | | | | | | | -|-----------------------------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| -| max PRB/sym | 100 | 106 | 107 | 132 | 133 | 135 | 162 | 217 | 270 | 273 | -| numPRBc | 100 | 106 | 107 | 132 | 133 | 135 | 162 | 217 | 270 | 273 | -| rbgSize | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| lastRbgID | 6 | 6 | 6 | 8 | 8 | 8 | 10 | 13 | 16 | 17 | -| f(0) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| f(n) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| F(lastRbgID) | 4 | 10 | 11 | 4 | 5 | 7 | 2 | 9 | 14 | 1 | - -Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal. Every symbol should be described by a single type 1 section (DL-SCH and DCI) except symbols #6 and #7 which will be used for the section extension 12 test. The data in symbol #6 should be a new PN23 sequence starting in the first PRB and continuing to PRB 273 (RBG number 17). Symbol #7 should be identical to symbol #6. The symMask value should be set to 00000011000000b. No Section Type zero messages will be used for this test. The parameters for the default test signal are shown below: - -![Diagram showing a grid of PRBs across 14 symbols. Symbols 0-5 are blank. Symbols 6 and 7 are split into two rows: the top row is 'Blank' and the bottom row is 'User Data'. Symbols 8-13 are blank. A bracket at the bottom labeled 'symMask' covers all symbols. On the left, a red bracket labeled '241 PRBs - 16 RBGs' covers the main part, and two blue brackets labeled '16 PRB - 1 RGB' point to the two rows of symbol 6 and 7.](2b0332ac7e7e351e0ec7b1cb17d10e23_img.jpg) - -### Section Extension 12 (273 PRBs) - -**Section Header** -startSymbolId = 0 - -**SectionId** -startPrbc = 0 -numPrbc = 16 - -**Section Extension 6** -offStartPrb(1) = 16 -numPrb(1) = 241 - -Grey cells are user data, White cells are unallocated PRBs - -| | | | | | | | | | | | | | | | -|--|----------|----------|----------|----------|----------|----------|----------|----------|----------|----------|-----------|-----------|-----------|-----------| -| | Symbol 0 | Symbol 1 | Symbol 2 | Symbol 3 | Symbol 4 | Symbol 5 | Symbol 6 | Symbol 7 | Symbol 8 | Symbol 9 | Symbol 10 | Symbol 11 | Symbol 12 | Symbol 13 | -| | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | - -241 PRBs – 16 RBGs - -16 PRB – 1 RGB - -16 PRB – 1 RGB - -symMask - -Diagram showing a grid of PRBs across 14 symbols. Symbols 0-5 are blank. Symbols 6 and 7 are split into two rows: the top row is 'Blank' and the bottom row is 'User Data'. Symbols 8-13 are blank. A bracket at the bottom labeled 'symMask' covers all symbols. On the left, a red bracket labeled '241 PRBs - 16 RBGs' covers the main part, and two blue brackets labeled '16 PRB - 1 RGB' point to the two rows of symbol 6 and 7. - -The O-DU emulator will build a U-Plane message containing the PN23 IQ data for the first 16 PRBs (RBG 0), this message will have the section ID used in the C-Plane message described above. Another U-Plane message will be created using the same section ID but with the PN23 data for RBGs 2-17 in it. The same U-Plane messages will be used for symbol #7. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should only contain the same PN23 signals that were sent in the U-Plane, that is the PN23 sequence in the first 16 PRBs, nothing in the next 16 PRBs and the remainder of the PN23 sequence in RBGs 2-17, or the pattern appropriate for the numerology if a different numerology is chosen as noted above. - -3.2.3.1.19 UC Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation -Section Extension 12 3GPP UL – Resource Allocation - -A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to validate the capability of interpreting the section extension 12, non-contiguous PRB allocation to the basic uplink test. - -Validate correct uplink operation of the O-RU using 3GPP Reference Sensitivity level definition (Section 7.2 ETSI TS 138.141-1) of the Conducted Receiver Characteristic Test (clause 7 ETSI TS 138.141) and power Levels at least 30 dB above Reference Sensitivity power Level described in ETSI TS 138.141-1 Table 7.2.5-1. This is to improve the likelihood that all data will be received by the radio correctly since we are not interested in testing receiver sensitivity but only the O-RAN protocol compliance. C-Plane messages will contain 2 symbols with the same set of non-contiguous PRBs referenced to test both the symMask and the offStartPrb parameters. - -![Figure 3.2.3.1-22: G-FR1-A1-5 UL FDD Test Signal. The figure consists of two main parts. The top part is a 'Channel Allocation' graph showing CRB for ul1 (0 to 273) on the y-axis and Slot (0 to 20) on the x-axis. A blue horizontal bar labeled 'UL-SCH' is present across all slots, primarily in the lower CRB range (0 to 46). The bottom part is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' grid. The y-axis is 'Subcarrier' (0 to 12) and the x-axis is 'Symbol' (0 to 13). The grid shows blue cells for data and red cells for DMRS. Red cells are located at subcarriers 2 and 11 for symbols 2 and 11. Blue cells are present in all other grid positions. Red lines connect the subcarriers 2 and 11 in the bottom grid to the corresponding blue bar in the top graph. To the right of the bottom grid is a text box with bullet points explaining the signal structure.](c755e79fe75238688e161b5b9c7ee536_img.jpg) - -**3GPP G-FR1-A1-5: SCS30k\_51RB 100 MHz Uplink FDD Test Signal** - -- All the Physical Uplink Shared Channels (all PRBs shown in Blue) are populated with test data as described in each test case. -- There is no UCI or SRS data -- Each Slot contains uplink data in each symbol except symbols 2 and 11 which contain DMRS signals only as shown in Red. - -Figure 3.2.3.1-22: G-FR1-A1-5 UL FDD Test Signal. The figure consists of two main parts. The top part is a 'Channel Allocation' graph showing CRB for ul1 (0 to 273) on the y-axis and Slot (0 to 20) on the x-axis. A blue horizontal bar labeled 'UL-SCH' is present across all slots, primarily in the lower CRB range (0 to 46). The bottom part is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' grid. The y-axis is 'Subcarrier' (0 to 12) and the x-axis is 'Symbol' (0 to 13). The grid shows blue cells for data and red cells for DMRS. Red cells are located at subcarriers 2 and 11 for symbols 2 and 11. Blue cells are present in all other grid positions. Red lines connect the subcarriers 2 and 11 in the bottom grid to the corresponding blue bar in the top graph. To the right of the bottom grid is a text box with bullet points explaining the signal structure. - -Figure 3.2.3.1-22 G-FR1-A1-5 UL FDD Test Signal - -Using an RF source, the test equipment will generate a 3GPP test signal as shown in Figure 3.2.3.1-22 above. The radio will demodulate and decode this signal and send frequency domain IQ to the O-DU-Emulator as instructed by the O-DU-emulator using uplink C-Plane messages containing section extension 12. Note this signal has 20 slots with all symbols populated with only uplink shared data in the only first 48 RBs. The symbols are populated with PN23 data. - -The TER (Test Equipment, O-RU) generates an uplink signal on the antenna connector or TAB connector, together with the corresponding C-Plane messages on the Fronthaul interface. - -The TER will capture the U-Plane messages generated by the DUT and validate if the payload matches with the uplink signal. - -It applies to the O-RAN CUS Specification [2]: - -- Clause 7.4 -- Clause 8.3.2 -- Clause 8.3.3 - -## B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in section ETSI TS 138.141-1 section G-FR1-A1-5. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. The radio must report that it supports section extension type 12, non-contiguous PRB allocations. Note this signal may be changed to any of the 3GPP sensitivity test signals in Table A.1-1 in ETSI TS 138.141-1 if the radio does not support the numerology and bandwidth used in this test. The test signal described in this section will be used if the radio supports that numerology and bandwidth. - -## C. Test Methodology - -Leverage from the well-known payload (Pseudo Random sequence) of the uplink signal to compare it with the payload of the signal communicated on the O-RAN interface. The IQ information is extracted from the U-Plane message and demodulated to retrieve payload. - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal source to the O-RU antenna port and configure the source to transmit the required 3GPP test signal upon receiving a trigger signal from the CUSM-E. The signal source power level should be adjusted to at least 30 dB above the setting used in the 3GPP receiver sensitivity test. - -### b. Procedure - -- Load uplink test waveform (G-FR1-A1-5 : SCS130k\_51RB) on the RF signal source. Note this signal should contain a new PN23 sequence as user data in PRBs 0 through 50 for symbols 6 and 7. The remainder of the test waveform is as described in 3GPP. -- Configure signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that C-Plane messages have been sent. -- Load C-Plane message sequence on Test Equipment O-RU (TER) – Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal. For this test symbols number 6 and 7 will be used in each slot. The starting PRB will be zero and number of used PRBs will be 48. The resource block group size will be 16. Using the calculations in O-RAN CUS Specification [2] clause 7.7.6, the ID of the last RBG will be 17, $f(0)$ will be 16, $f(n)$ will be 16 and $f(\text{lastRbgID})$ will be 1. Note, if the radio does not support this numerology a suitable replacement can be selected from the Table below: - -Table 3.2.3-6 Stock Data Sections - -| # PRBs per Symbol (11-79) | | | | | | | | | | | -|---------------------------|----|----|----|----|----|----|----|----|----|----| -| max PRB/sym | 11 | 24 | 25 | 32 | 50 | 51 | 52 | 65 | 66 | 79 | -| numPRBc | 11 | 24 | 25 | 32 | 50 | 51 | 52 | 65 | 66 | 79 | -| rbgSize | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| lastRbgID | 2 | 5 | 6 | 7 | 6 | 6 | 6 | 8 | 8 | 4 | -| f(0) | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| f(n) | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| F(lastRbgID) | 3 | 4 | 1 | 4 | 2 | 3 | 4 | 1 | 2 | 15 | - -| # PRBs per Symbol (100-273) | | | | | | | | | | | -|-----------------------------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| -| max PRB/sym | 100 | 106 | 107 | 132 | 133 | 135 | 162 | 217 | 270 | 273 | -| numPRBc | 100 | 106 | 107 | 132 | 133 | 135 | 162 | 217 | 270 | 273 | -| rbgSize | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| lastRbgID | 6 | 6 | 6 | 8 | 8 | 8 | 10 | 13 | 16 | 17 | -| f(0) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| f(n) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| F(lastRbgID) | 4 | 10 | 11 | 4 | 5 | 7 | 2 | 9 | 14 | 1 | - -- A single section ID will describe the non-contiguous resource allocation using section extension 12. The parameters to use for the example wave form are shown below: - -## Section Extension 12 (48 PRBs) - -**Section Header** - -startSymbolId = 0 - -**SectionId** - -startPrbc = 0 - -numPrbc = 16 - -**Section Extension 6** - -offStartPrb(1) = 16 - -numPrb(1) = 16 - -![Diagram of Section Extension 12 (48 PRBs) showing a grid of symbols and PRBs. The grid has 14 columns (Symbol 0 to Symbol 13) and 48 rows. The first 16 columns (Symbol 0 to Symbol 15) are labeled '0' at the bottom, and the next 16 columns (Symbol 16 to Symbol 31) are labeled '1' at the bottom. The first 16 columns are labeled 'Blank' at the top. The next 16 columns are labeled 'Blank' at the top. The last 16 columns are labeled 'Blank' at the top. The first 16 columns are labeled 'User Data' in the middle. The next 16 columns are labeled 'Blank' in the middle. The last 16 columns are labeled 'User Data' in the middle. The first 16 columns are labeled '16 PRB - 1 RGB' on the left. The next 16 columns are labeled '16 PRB - 1 RGB' on the left. The last 16 columns are labeled '16 PRB - 1 RGB' on the left. A bracket at the bottom labeled 'symMask' spans the first 16 columns.](29100fce6dce19cea57712363976bf2c_img.jpg) - -Grey cells are user data, White cells are unallocated PRBs - -Diagram of Section Extension 12 (48 PRBs) showing a grid of symbols and PRBs. The grid has 14 columns (Symbol 0 to Symbol 13) and 48 rows. The first 16 columns (Symbol 0 to Symbol 15) are labeled '0' at the bottom, and the next 16 columns (Symbol 16 to Symbol 31) are labeled '1' at the bottom. The first 16 columns are labeled 'Blank' at the top. The next 16 columns are labeled 'Blank' at the top. The last 16 columns are labeled 'Blank' at the top. The first 16 columns are labeled 'User Data' in the middle. The next 16 columns are labeled 'Blank' in the middle. The last 16 columns are labeled 'User Data' in the middle. The first 16 columns are labeled '16 PRB - 1 RGB' on the left. The next 16 columns are labeled '16 PRB - 1 RGB' on the left. The last 16 columns are labeled '16 PRB - 1 RGB' on the left. A bracket at the bottom labeled 'symMask' spans the first 16 columns. - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and trigger the source to play the RF signal on a frame boundary. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information -- Extract Payload -- Compare payload binary sequences - -**D. Test Requirement (expected result)** - -1. The verdict is “Test pass” if the test frame received by the signal analyser contains the same PN23 signals that were sent in the U-Plane, that is the PN23 sequence in the first 16 PRBs, nothing in the next 16 PRBs and the remainder of the PN23 sequence in RBG 2 (Next 16 PRBs). -2. If any of the test conditions is not true, the verdict for the whole test is "Fail" - -### 3.2.3.1.20 UC Plane O-RU Base Class FDD Test UL – Static SRS allocation - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the O-RU can support static SRS configuration through the M-Plane. This is an uplink only test so there is no corresponding downlink test for FDD. The O-RU must report through the M-Plane that it supports static configuration of SRS. - -The test will have the CUSM emulator configure the O-RU, through the M-Plane, with a section of time/frequency resources reserved for static uplink SRS. The signal source will be programmed to send simulated SRS signals in a - -subset of those resources. The O-RU should receive this SRS signals and pass them through to the CUSM emulator using U-Plane messages. Note, there will be no C-Plane messages sent from the CUSM emulator and the O-RU. The signal generator will signal power levels at least 30 dB above Reference Sensitivity power Level described in TS 138.141-1 Table 7.2.5-1. This is to improve the likelihood that all data will be received by the radio correctly since we are not interested in testing receiver sensitivity but only the O-RAN protocol compliance. - -The placement of the time frequency resources is not specified in this test so it may be placed anywhere in the frame. - -The TER (Test Equipment, O-RU) generates an uplink SRS signal on the antenna connector or TAB connector. The TER will capture the U-Plane messages generated by the DUT and validate whether the payload matches the uplink signal as well as beam characteristics. The metric used to validate that the signal received by the CUSM emulator matches the signal sent by the signal generator will be EVM as described in Annex H.7 of ETSI TS 138.141. While some 3GPP test documents (e.g. ETSI TS 138.521 clause 6.4.2.1.3) suggest treating the EVM requirements for physical Zadoff-Chu sequences such as PRACH the same as QPSK for EVM requirements, this document will decrease the required EVM to the level specified for 64 QAM. The purpose of this is to ensure that there is no chance of false positives where a random, mistaken signal sent by the O-RU closely mimics the test signal used by the TER. Since there are no impairments made to the uplink SRS signal this should be well within the capabilities of the O-RU. - -## B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The O-RU must indicate it supports static SRS allocation. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in ETSI TS 138.141-1 section G-FR1-A1-5. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. Note this signal may be changed to any of the 3GPP sensitivity test signals in Table A.1-1 in ETSI TS 138.141-1 if the radio does not support the numerology and bandwidth used in this test. The test signal described in this clause will be used if the radio supports that numerology and bandwidth. - -## C. Test Methodology - -### a: Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal source to the O-RU antenna port and configure the source to transmit the required SRS test signal upon receiving a trigger signal from the CUSM-E. The signal source power level should be adjusted to at least 30 dB above the setting used in the 3GPP receiver sensitivity test. - -Implicit in this Initial set up is statically configuring O-RU with a section of time/frequency resources for static SRS signals. - -### b: Procedure - -- Build an SRS signal in the signal generator that fits in the preconfigured time frequency resources set in the initial configuration. -- Load the waveform into the signal source: -- Configure signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that signals the start of a frame boundary. -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port connected - -- TER will arrange U-Plane messages according to time and frequency -- Start SRS waveform generation on the signal generator. Ensure the test frame is repeated enough times to generate a statistically significant number of SRS occasions. That is at least 10 occasions. -- Extract IQ information -- Calculate EVM of the SRS signal received by the CUSM emulator to the ideal signal generated by the signal source. Use the method described in ETSI TS 138.141 Annex H.7 to perform the calculation. - -**A. Test Requirement (expected result)** - -1. The verdict is “Test pass” if the calculated EVM is less than 8% as median EVM measured over the minimum number of SRS occasions of at least 10 occasions. -2. If any of the test conditions are not true, the verdict for the whole test is "Fail" - -**3.2.3.1.21 UC Plane O-RU Base Class FDD Test UL – Static PRACH allocation** - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the O-RU can support static PRACH configuration through the M-Plane. This is an uplink only test so there is no corresponding downlink test for FDD. The O-RU must report through the M-Plane capabilities that it supports static configuration of PRACH. The concept is to repeat test 3.2.3.8.1 (5GNR PRACH test) without sending any C-Plane type 3 messages and configuring the O-RU using only the M-Plane. - -TER will setup the signal generator with a PRACH test waveform according to ETSI TS 138.211 clause 6.3.3, ETSI TS 138.141-1 clause 8.4.1 and A.6. The test waveform will contain the same preamble ID for every occasion repeated by following the timing offset scheme specified in the figures 8.4.1.4.2-2 or 8.4.1.4.2-3 ETSI TS 138.141-1 depending on the selected PRACH format. - -This is an example for FR1 – SCS=30 kHz – BW=100MHz – Format A3, on each occasion the time offset of the same preamble index (selected according to Table A.6-1 ETSI TS 138.141.1) is incremented by 100nsec starting from 0 up to 800nsec (9 occasions per frame). Each PRACH occasion is at the beginning of the first nine used sub-frames. The scheme is repeated every frame. - -![Waveform plot showing PRACH signal power over time. The y-axis represents power in dB from -61.44 to 61.44. The x-axis represents time in ms from 0 to 10. There are 9 distinct pulses, each lasting approximately 0.5 ms, starting at 0 ms, 1 ms, 2 ms, 3 ms, 4 ms, 5 ms, 6 ms, 7 ms, and 8 ms. The pulses are labeled 'PRACH' in the legend.](69673317b4a8d0b5a24f33ce299820fb_img.jpg) - -Waveform plot showing PRACH signal power over time. The y-axis represents power in dB from -61.44 to 61.44. The x-axis represents time in ms from 0 to 10. There are 9 distinct pulses, each lasting approximately 0.5 ms, starting at 0 ms, 1 ms, 2 ms, 3 ms, 4 ms, 5 ms, 6 ms, 7 ms, and 8 ms. The pulses are labeled 'PRACH' in the legend. - -| # | Enabled | Power Boosting | Timing Offset | PRACH Format | Preamble Index | Root Sequence Index | Cyclic Shift Index | Frame Offset | Subframe Index | n_RA_t | n_RA_slot | n_RA_f | RA_RNTI | -|---|---------|----------------|---------------|--------------|----------------|---------------------|--------------------|--------------|----------------|--------|-----------|--------|---------| -| 0 | ✓ | 0.00 dB | 0 ns | FormatA3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | -| 1 | ✓ | 0.00 dB | 100 ns | FormatA3 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 15 | -| 2 | ✓ | 0.00 dB | 200 ns | FormatA3 | 0 | 0 | 0 | 0 | 2 | 0 | 0 | 0 | 29 | -| 3 | ✓ | 0.00 dB | 300 ns | FormatA3 | 0 | 0 | 0 | 0 | 3 | 0 | 0 | 0 | 43 | -| 4 | ✓ | 0.00 dB | 400 ns | FormatA3 | 0 | 0 | 0 | 0 | 4 | 0 | 0 | 0 | 57 | -| 5 | ✓ | 0.00 dB | 500 ns | FormatA3 | 0 | 0 | 0 | 0 | 5 | 0 | 0 | 0 | 71 | -| 6 | ✓ | 0.00 dB | 600 ns | FormatA3 | 0 | 0 | 0 | 0 | 6 | 0 | 0 | 0 | 85 | -| 7 | ✓ | 0.00 dB | 700 ns | FormatA3 | 0 | 0 | 0 | 0 | 7 | 0 | 0 | 0 | 99 | -| 8 | ✓ | 0.00 dB | 800 ns | FormatA3 | 0 | 0 | 0 | 0 | 8 | 0 | 0 | 0 | 113 | - -**Figure 3.2.3.1-23 FR1 SCS 30Kz 100MHz Format A3** - -According to the PRACH waveform setting, the TER will generate a corresponding sequence of M-Plane messages which include the following parameters (According to the M-Plane specification): - -grouping static-prach-configuration - -- leaf pattern-period - "Period after which static PRACH patterns are repeated. Unit: number of frames." -- leaf guard-tone-low-re - "Number of REs occupied by the low guard tones." -- leaf num-prach-re - "Number of contiguous PRBs per data section description" -- leaf guard-tone-high-re - "Number of REs occupied by the high guard tones." -- leaf sequence-duration - "Duration of single sequence of the PRACH. Sequence may be considered as 'single PRACH symbol'" -- list prach-patterns - key prach-pattern-id - "Provides a PRACH pattern. Each record in the list represents a single PRACH occasion. Number of list entries cannot exceed max-prach-patterns" - - leaf prach-pattern-id - "Supplementary parameter acting as key for prach-pattern list." - - leaf number-of-repetitions - "This parameter defines number of PRACH repetitions in PRACH occasion, to which the section control is applicable" - - leaf number-of-occasions - "This parameter informs how many consecutive PRACH occasions is described by the PRACH Pattern" - - leaf re-offset – "Offset between the start of the lowest-frequency RE of the lowest frequency PRB and the start of the lowest frequency RE belonging to the PRACH occasion. The re-offset is configured as number of PRACH REs." - - list occasion-parameters – "list of cp-lengths, gp-lengths and beam-ids applicable per each PRACH occasion in PRACH pattern." - -NOTE: the number of records in this list MUST be equal to value of parameter number-of-occasions. - -- leaf occasion-id - "Supplementary parameter acting as key in 'occasion-parameters' list" -- leaf cp-length - "Cyclic prefix length. See CUS-Plane specification for detailed description." -- leaf gp-length - "Guard period length." -- leaf beam-id - "This parameter defines the beam pattern to be applied to the U-Plane data. beamId = 0 means no beamforming operation will be performed." -- leaf frame-number - "This parameter is an index inside the pattern-length, such that PRACH occasion is happening for SFN which fulfils following equation: $[SFN \bmod \text{pattern-length} = \text{frame-id}]$ " -- leaf sub-frame-id - "Identifier of sub-frame of the PRACH occasion. Value is interpreted in the same way as subframeId field in a section description of a C-Plane message." -- leaf time-offset - "This parameter defines the time-offset from the start of the sub-frame to the start of the first Cyclic Prefix of PRACH pattern" - -By the corresponding U-Plane messages in the uplink direction, the TER will try to detect the presence of the corresponding preamble at the expected timing offset and calculate the probability of detection Pd according to the definition in TS38.141-1 clause 8.4.1.1. - -The signal will be exercised at only one O-RU port without adding any external AWGN power level or multipath fading profile and at a power level avoiding detection errors due to poor SNR (rule described in the sub-section C of this scenario class). - -The test will have the CUSM emulator configure the O-RU, through the M-Plane, with a section of time/frequency resources reserved for static uplink PRACH. The default is the PRACH configuration described in 3GPP above but the test may be conducted with changes if the radio does not support those exact configurations. The signal source will be programmed to send simulated PRACH signals in those resources. The O-RU should receive this PRACH signal and pass them through to the CUSM emulator using U-Plane messages. Note, there will be no C-Plane messages sent from the CUSM emulator and the O-RU. - -## B. Test Entrance Criteria - -O-RU must have a conducted antenna port (FR1) or TAB connector. - -By the M-plane, TER will detect all the supported SCSs for PUSCH and PRACH, supported PRACH format, and carrier bandwidths by the O-RU. It is assumed that only one combination of the three above parameters supported by the O-RU is enough to validate the test. TER will choose the format either according to the PRACH Configuration Index in ETSI TS 138.211 clause 6.3.3 Table 6.3.3.2-2 and the available frequency resource, according to the manufacturer declaration item D.103 “PRACH format and SCS” in ETSI TS 138.141-1 or according to the format information obtained by the M-plane in case O-RU implements this feature. TER shall generate M-Plane messages conformant to the selected format. If more formats are claimed, only one shall be selected to reduce the test time, preference will be given to a format specified in Table A.6.1 ETSI TS 138.141. It is assumed that the O-RU manufacturer will support at least one in that Table. For the case of long preambles, it is assumed format 0 is always supported since this is the only one shown in the Table A.6-1 ETSI TS 138.141. - -## C. Test Methodology - -### a: Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal source to the O-RU antenna port and configure the source to transmit the required PRACH test signal upon receiving a trigger signal from the CUSM-E. - -Implicit in this Initial set up is statically configuring O-RU with a section of time/frequency resources for static PRACH signals. - -### b: Procedure - -- Set signal generator power to at least 30 dB above the setting used in the 3GPP receiver sensitivity test described in ETSI TS 138.141-1 clause 7.2.5. -- Set signal generator frequency offset to the central carrier frequency. PRACH will be mapped over frequency according to $msg1-FrequencyStart (n_{RA}^{start})$ parameter equal to 0. PRACH format is set according to what TER has selected from the manufacturer declarations. -- Start PRACH waveform generation on the signal generator. Ensure the test frame is repeated enough times to generate a statistically significant number of PRACH occasions. That is at least 10 occasions. -- TER will perform PRACH detection per each PRACH occasion in each frame sent and compare the result with the expected preamble ID and the expected timing offset. Since the external AWGN and fading generator are not present the time error tolerance should be low, TER will use the time error tolerance in Table 8.4.1.1-1 for AWGN case according to the corresponding PRACH format and PRACH SCS. A counter of successful detections is incremented at every matching. The probability of detection is given by the ratio between that counter and the number of the expected received PRACH occasions within the test time. - -- Repeat the test procedure by setting $msg1-FrequencyStart (n_{RA}^{start})$ parameter to the right edge of the configured carrier bandwidth in order to exercise a different frequency offset number - -**D. Test Requirement (expected result)** - -- Test is pass if the probability of detection is 100% determined across the minimum amount of at least 10 occasions. - -**3.2.3.1.22 UC Plane O-RU Scenario Class Extended using section extension 13 for frequency hopping UL – Resource Allocation** - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to validate the capability of the O-RU to correctly interpret section extension 13, frequency hopping, for the uplink. - -This test will validate correct uplink operation of the O-RU using 3GPP Reference Sensitivity level definition (clause 7.2 ETSI TS 138.141-1) of the Conducted Receiver Characteristic Test (clause 7 ETSI TS 138.141) and power Levels at least 30 dB above Reference Sensitivity power Level described in ETSI TS 138.141-1 Table 7.2.5-1. This is to improve the likelihood that all data will be received by the radio correctly since we are not interested in testing receiver sensitivity but only the O-RAN protocol compliance. C-Plane message will reference 2 symbols using section extension 13. - -![Figure 3.2.3.1-24 G-FR1-A1-5 UL FDD Test Signal. The figure contains two main visual components. The top component is a 'Channel Allocation' plot showing 273 CRBs (0 to 250) across 20 slots. A legend indicates 'UL-SCH' in blue and 'U-PLANS' in red. A solid blue bar at the bottom of the plot (CRBs 0-23) represents the U-PLANS signal. The bottom component is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' plot. The y-axis is 'Subcarrier' (0 to 12) and the x-axis is 'Symbol' (0 to 13). This plot shows a grid where most cells are blue (UL-SCH data), except for symbols 2 and 11 which have red cells (DMRS signals). Red lines connect the top plot to the bottom plot, specifically pointing to the blue and red areas. To the right of the bottom plot is a text box with a bullet list explaining the signal structure.](e2810981fcbd904f97bf30226f60fcbd_img.jpg) - -**3GPP G-FR1-A1-5: SCS30k\_51RB 100 MHz Uplink FDD Test Signal** - -All the Physical Uplink Shared Channels (all PRBs shown in Blue) are populated with test data as described in each test case. - -- There is no UCI or SRS data -- Each Slot contains uplink data in each symbol except symbols 2 and 11 which contain DMRS signals only as shown in Red. - -Figure 3.2.3.1-24 G-FR1-A1-5 UL FDD Test Signal. The figure contains two main visual components. The top component is a 'Channel Allocation' plot showing 273 CRBs (0 to 250) across 20 slots. A legend indicates 'UL-SCH' in blue and 'U-PLANS' in red. A solid blue bar at the bottom of the plot (CRBs 0-23) represents the U-PLANS signal. The bottom component is an 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' plot. The y-axis is 'Subcarrier' (0 to 12) and the x-axis is 'Symbol' (0 to 13). This plot shows a grid where most cells are blue (UL-SCH data), except for symbols 2 and 11 which have red cells (DMRS signals). Red lines connect the top plot to the bottom plot, specifically pointing to the blue and red areas. To the right of the bottom plot is a text box with a bullet list explaining the signal structure. - -**Figure 3.2.3.1-24 G-FR1-A1-5 UL FDD Test Signal** - -Using an RF source, the test equipment will generate a 3GPP test signal as shown in Figure 3.2.3.1-24 above. The radio will demodulate and decode this signal and send frequency domain IQ to the O-DU-Emulator as instructed by the O-DU-emulator using uplink C-Plane messages containing section extension 13. Note this signal has 20 slots with all symbols populated with only uplink shared data in the only first 51 RBs. The symbols are populated with PN23 data. - -The TER (Test Equipment, O-RU) generates an uplink signal on the antenna connector or TAB connector, together with the corresponding C-Plane messages on the Fronthaul interface. - -The TER will capture the U-Plane messages generated by the DUT and validate if the payload matches with the uplink signal. - -It applies to the O-RAN CUS Specification [2]: - -- Clause 7.4 -- Clause 8.3.2 -- Clause 8.3.3 - -## B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in ETSI TS 138.141-1 clause G-FR1-A1-5. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. The radio must report that it supports section extension type 13, frequency hopping. Note this signal may be changed to any of the 3GPP sensitivity test signals in Table A.1-1 in ETSI TS 138.141-1 if the radio does not support the numerology and bandwidth used in this test. The test signal described in this section will be used if the radio supports that numerology and bandwidth. - -## C. Test Methodology - -Leverage from the well-known payload (Pseudo Random sequence) of the uplink signal to compare it with the payload of the signal communicated on the O-RAN interface. The IQ information is extracted from the U-Plane message and demodulated to retrieve payload. - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal source to the O-RU antenna port and configure the source to transmit the required 3GPP test signal upon receiving a trigger signal from the CUSM-E. The signal source power level should be adjusted to at least 30 dB above the setting used in the 3GPP receiver sensitivity test. - -### b. Procedure - -- Load uplink test waveform (G-FR1-A1-5 : SCS130k\_51RB) on the RF signal source. Note this signal should contain a new PN23 sequence as user data in PRBs 0 through 50 for symbol 6 and PRBs 100 through 151 for symbol 7. This will be copied for all 20 slots. The remainder of the test waveform is as described in 3GPP. -- Configure signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that C-Plane messages have been sent. -- Load a C-Plane message on Test Equipment O-RU (TER) – Use the O-DU emulator control interface to build the appropriate C-Plane message that describes this uplink signal. This section should have startSymbolId = 6, numPrbc = 51, and section extension 13 attached. The section extension should have nextSymbolId = 7 and nextStartPrbc = 100. - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and trigger the source to play the RF signal on a frame boundary. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information -- Extract Payload -- Compare payload binary sequences - -**D. Test Requirement (expected result)** - -1. The verdict is “Test pass” if the test frame received by the signal analyser contains two U-Plane messages for this section ID one containing the PN23 sequence for the first 51 PRBs in symbol 6 and PRBs 100 through 151 for symbol #7 containing the PN23 sequence sent by the signal source for those PRBs. - -### 3.2.3.2 UC-Plane O-RU Scenario Class Beamforming (BFM) - -This clause describes the beamforming conformance testing for O-RAN fronthaul interface. The tests do not aim to test the O-RU beamforming performance or capabilities but to test that the O-RU under test focuses the RF energy or sensitivity into a specific direction and with a specific granularity following the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) C-Plane messages. - -Unless stated otherwise in a test case, the following statements apply to all the test cases defined in this clause: - -- It is based on conducted testing with a setup such as described in clause 2.1 and it only applies to O-RU DUTs that have conducted antenna ports or TAB connectors. -- It applies to Category A and Category B O-RU DUTs. -- It applies to LTE and/or 5G New Radio O-RU DUTs. In both cases, precoding is not required in any test case. -- If O-RU DUT supports Analog Beamforming (i.e. time domain beamforming), all the U-Plane test frames are defined by segmenting the Stock Test A: 1 section per symbol. The definition of this Stock Test A can be found in Figure 3.2.1.1-4 and the description accompanying this figure. Each slot shall include multiple sections (one per symbol within the slot) and only one beam at a time (i.e. one beamId at a time) and therefore only one beam can be tested per slot. -- If O-RU DUT supports Digital Beamforming (i.e. frequency domain beamforming), all the U-Plane test frames are defined by segmenting the Stock Test B: 2 sections per symbol definition as shown in Figure 3.2.1.1-4. Each slot shall include multiple sections (two per symbol within the slot) and only one beam per section at a time (i.e. one beamId at a time) and therefore up to two different beams can be tested per slot. -- If O-RU DUT supports multiple polarizations, it is up to the TER to determine if the testing is carried out for each polarization separately or multiple polarizations at the same time. In any case, it is important to guarantee that the correct eAxC\_ID for the correct polarization (or polarizations) is exercised. -- For O-RU DUT that support LTE: - - Downlink tests will use a standard 3GPP E-TM1.1 test frame for FDD (Clause 6.1.1.1 ETSI TS 136.141-1) with 20MHz bandwidth (100 RB) as shown in Figure 3.2.3.2-25. - -![Figure 3.2.3.2-25: E-TM1.1 FDD 20 MHz 100RB. This figure shows a time-frequency grid representing a 20 MHz bandwidth (100 Resource Blocks) over 10 subframes (labeled 0 to 9). The vertical axis represents time in subframes, and the horizontal axis represents frequency in Resource Blocks. The grid is filled with red blocks, with some green blocks indicating specific resource allocations or reference signals. Two small blue squares are visible in the first two subframes.](4a1aafd8c195990968b731cf9acfa68a_img.jpg) - -Figure 3.2.3.2-25: E-TM1.1 FDD 20 MHz 100RB. This figure shows a time-frequency grid representing a 20 MHz bandwidth (100 Resource Blocks) over 10 subframes (labeled 0 to 9). The vertical axis represents time in subframes, and the horizontal axis represents frequency in Resource Blocks. The grid is filled with red blocks, with some green blocks indicating specific resource allocations or reference signals. Two small blue squares are visible in the first two subframes. - -Figure 3.2.3.2-25 E-TM1.1 FDD 20 MHz 100RB - -If 20MHz is not supported by the O-RU DUT, then it will use the highest bandwidth supported by the O-RU DUT. - -- Uplink test will use a standard 3GPP UL RMC Configuration definition for FDD (TS36.521-1) and power levels 30dB above Reference Sensitivity power level with 10MHz bandwidth (100 RB) as shown in Figure 3.2.3.2-26. - -![Figure 3.2.3.2-26 UL RMC FDD 20 MHz 100 RB. A diagram showing a frequency spectrum with 100 Resource Blocks (RBs) represented by red bars. The spectrum is divided into two main bands, 0-99 and 100-199, with a gap between them. The red bars are separated by cyan vertical lines representing subcarriers.](8ce6ab62a04c4eafa11bef389ddd21fd_img.jpg) - -Figure 3.2.3.2-26 UL RMC FDD 20 MHz 100 RB. A diagram showing a frequency spectrum with 100 Resource Blocks (RBs) represented by red bars. The spectrum is divided into two main bands, 0-99 and 100-199, with a gap between them. The red bars are separated by cyan vertical lines representing subcarriers. - -**Figure 3.2.3.2-26 UL RMC FDD 20 MHz 100 RB** - -If 20MHz is not supported by the O-RU DUT, then it will use the highest bandwidth supported by the O-RU DUT. - -- For O-RU DUT that support 5G NR: - - Downlink tests will use a standard 3GPP NR-FR1-TM1.1 test frame for FDD in [19] (clause 4.9.2 TS138.141-1) of the Conducted Transmitter Characteristic Test (clause 6 TS138.141-1) as described in clause 3.2.1.1. The test numerology will be preferably 30kHz subcarrier spacing and 100 MHz Bandwidth. If not supported, then it will use any other supported subcarrier spacing and the highest bandwidth of the O-RU DUT. - - Uplink tests will use a standard 3GPP Reference Sensitivity level definition (clause 7.2 and Annex A TS138.141-1) of the Conducted Receiver Characteristic Test (clause 7 ETSI TS 138.141) and power levels 30dB above Reference Sensitivity power level as described in clause 3.2.1.1. The test numerology will be preferably 30kHz subcarrier spacing and 100 MHz Bandwidth, if supported. Otherwise, it will use any available subcarrier space and the highest bandwidth supported by the O-RU DUT. -- The O-RU DUT: - - supports the default parameters in clause 3.2.1.1.1 of this document. - - has installed current release of shipping software. - - has at least two conducted antenna ports (or TAB connectors) to be connected to a signal analyser. Likewise, it must have at least two conducted antenna ports or TAB connectors to be connected to a signal generator. - - be fully calibrated up to the antenna ports or (TAB connectors) (if needed). It is expected to be calibrated by O-RU vendor prior to testing. -- The TER: - - is capable of carrying out any signal processing required to generate and demodulate 3GPP compliant waveforms. - - is able to calculate or extract beamweights (or magnitude and phase relations) between antenna ports or TAB connectors. Alternatively, and if the O-RU DUT manufacturer provides the list of beam directions supported by the O-RU DUT, TER might calculate or extract the beam direction instead of the beamweights. - - is able to generate and deliver signals with the required beamweights (or magnitude and phase relations) at the antenna ports or TAB connectors. - - is fully calibrated up to the interfaces where is connected to the O-RU DUT antenna ports (or TAB connectors). For that, a known test signal might be either injected by the TER into the O-RU DUT, or internally generated by the O-RU DUT, and the O-RU DUT must not apply any digital or analogue beamweights to the known test signal. One possible method to perform calibration uses injected C-Plane and U-Plane signals from TER into the O-RU and using C-Plane messages with beamID=0. - -- The O-DU emulator of the TER: - - is capable of generating and sending U-Plane messages containing 3GPP test frames following the corresponding Stock sectioning defined above, as well as be capable of capturing U-Plane messages and extracting 3GPP test frames (i.e. IQ data) from the captured U-Plane messages. - - is capable of generating the C-Plane messages for, receiving, extracting and demodulating the 3GPP test frames following the corresponding Stock sectioning defined above. - - For DMRS-BF tests, the TER setup modifications are: - - RF Signal Generator / System which can be a combination of test equipment, or an integrated one, that provides all the testing capabilities needed: - - RF Signal Generator capable of generating wanted signals (3GPP compliant SU-MIMO and MU-MIMO signals). - - RF Signal Generator capable of generating Additive white Gaussian Noise and Interference signals. It can be a single device or multiple devices. - - Beamformer to apply beam weights to each of the signals under tests - - CUSM-Plane emulator with expanded capability: - - is able to operate with and without reference Channel Estimation (CE) and Equalization (EQ) over the received signal from DUT (Uplink direction), -- NOTE: The definition of the reference algorithms used for Channel Estimation and Equalization in the TER are not defined in the present document. -- is capable of measuring and reporting EVM measurements after CE and EQ if receiving unequalised IQ data (when testing O-RU DUT with DMRS-BF-NEQ), or directly from received equalized IQ data (when testing O-RU DUT with DMRS-BF-EQ), - - is capable of measuring and reporting BER and/or BLER measurements of the received signal from DUT (Uplink direction) after demapping and decoding, -- NOTE: The definition of the reference algorithms used for demapping and decoding in the TER are not defined in the present document. -- is capable of parsing ST9 and ST10 messages to extract SINR and RRM measurements. - -![Figure 3.2.3.2-3: Test Equipment set up for testing O-RU DUT with DMRS-BF. The diagram shows the 'Test Equipment, RU (TER) for DMRS-BF' containing three main components: 'CUSM-Plane Emulator', 'DUT = O-RU', and 'RF Signal Generator / System'. The CUSM-Plane Emulator includes a 'Layer de-mapping + decoder' for BER/BLER, 'Channel Estimation + Equalization + Combiner' for EVM, 'SINR Meas.' for SINR, and 'RRM Meas.' for RRM. The DUT = O-RU is connected via FH (Fronthaul) and RF (Radio Frequency) links. The RF Signal Generator / System includes a 'Signal Generator Wanted Test Signals' and 'AWGN & Interference Generator' connected to a 'Beamformer'. The Beamformer output is summed with the test signals and interference before being transmitted to the DUT via RF. The DUT's DMRS-BF signal is received by the Beamformer and then processed by the CUSM-Plane Emulator.](9f5f9afcedaa0d9b7991976f5000865c_img.jpg) - -Figure 3.2.3.2-3: Test Equipment set up for testing O-RU DUT with DMRS-BF. The diagram shows the 'Test Equipment, RU (TER) for DMRS-BF' containing three main components: 'CUSM-Plane Emulator', 'DUT = O-RU', and 'RF Signal Generator / System'. The CUSM-Plane Emulator includes a 'Layer de-mapping + decoder' for BER/BLER, 'Channel Estimation + Equalization + Combiner' for EVM, 'SINR Meas.' for SINR, and 'RRM Meas.' for RRM. The DUT = O-RU is connected via FH (Fronthaul) and RF (Radio Frequency) links. The RF Signal Generator / System includes a 'Signal Generator Wanted Test Signals' and 'AWGN & Interference Generator' connected to a 'Beamformer'. The Beamformer output is summed with the test signals and interference before being transmitted to the DUT via RF. The DUT's DMRS-BF signal is received by the Beamformer and then processed by the CUSM-Plane Emulator. - -Figure 3.2.3.2-3 Test Equipment set up for testing O-RU DUT with DMRS-BF - -- The TER might have less testing ports than the O-RU DUT conducted antenna ports (or TAB connectors) if testing is carried out sequentially; or as many antenna ports as the number of conducted antenna ports (or TAB connectors) under test if testing is carried out simultaneously. -- It is up to the TER on how to extract the beamweights (or magnitude and phase relation) between the antenna ports or TAB connectors, or the beam direction / properties, in order to match it with the manufacturer's declaration. -- The user payload will be generated as PN23 with a seed of all ones. -- It applies to the O-RAN CUS Specification [2]: - - Clause 7.4 - - Clause 8.3.2 - - Clause 8.3.3 - - Clause 12 - - Annex J - -### 3.2.3.2.1 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – No Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with no beamforming (beamId=0x000) and with one spatial stream (single eAxC). - -#### B. Test Entrance Criteria - -- Manufacturers' declaration that defines list of magnitude and phase relation (or beamweights) between antenna ports or TAB connectors and/or beam directions with antenna array characteristics when O-RU DUT is operating with no beamforming. - -#### C. Test Methodology - -##### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal analyser to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -##### b. Procedure - -- a. Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (DL-SCH and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. - -- c. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- d. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. -- e. Extract either the beamweights, or magnitude and phase relation, or beam direction from the measured signal. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The signal relation (i.e. beamweights, or magnitude and phase relation) between antenna ports or TAB connectors, or the extracted beam direction, should match the expected relation, or beam direction, for the expected no beamforming within a tolerance defined by the manufacturer. - -### 3.2.3.2.2 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – No Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with no beamforming (beamId=0x000) and with one spatial stream (single eAxC). - -#### B. Test Entrance Criteria - -- Manufacturers' declaration that defines list of magnitude and phase relation (or beamweights) between antenna ports or TAB connectors and/or beam directions with antenna array characteristics when O-RU DUT is operating with no beamforming. - -#### C. Test Methodology - -##### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal source to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the source with any set-up information needed to allow it to synch and generate the test signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -##### b. Procedure - -- a. Build an appropriate test signal described above in the signal source of the TER. -- b. Inject the test signal into the O-RU with the application of an initial set of beamweights, or equivalently magnitude and phase relation, between all the TER ports connected to the antenna ports (or TAB connectors) to emulate the phase and magnitude difference “seen” by the antenna elements under test. For example, initial beamweights could be set to be “all equal” (i.e. no beamforming). - -- c. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (UL-SCH) using Section Type 1 messages. No Section Type zero messages will be used for this test. -- d. Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. while also triggering the signal source. -- e. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. -- f. Repeat the previous steps but now in step b apply a different set of beamweights or phase relation between all the antenna ports (or TAB connectors) when injecting the test signal into the O-RU. For example, repeating the process for a number of different beamweights will simulate the reception of the test signal from different beam directions. This allows to determine if the O-RU is really focusing the sensitivity to the correct beam direction. - -#### D. Test Requirement (expected result) - -1. The test frame received by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -2. The beamweights or magnitude and phase relation at the antenna ports (or TAB connectors) of the test signal that achieves the highest performance (i.e. best EVM, power, SNR, etc.) should match with the manufacturer's declaration of the phase relation expected for no beamforming. - -### 3.2.3.2.3 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Predefined-beam Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with predefined-beams beamforming (beamId≠0x000) and with one spatial stream (single eAxC). - -The transmitted beam direction is measured for each indexed beam required in this measurement, see below. The measured transmitted direction is compared to manufacturer-designated direction. Transmitted direction could be defined by the phase relation between the antenna ports or TAB connectors under test, or directly by extracting the beam direction. - -The elevation $\theta$ and azimuth $\Phi$ angles are defined as in [2] clause 12.4.2.2 - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Predefined-beam Beamforming conformance test might include multiple tests that the O-RU must comply: - -The test should include the following beams: - -1. A beam with 0 degrees azimuth ( $\Phi$ ) and elevation ( $\theta$ ) angles. -2. A beam with maximum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -3. A beam with maximum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). -4. A beam with minimum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -5. A beam with minimum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). - -If the O-RU only supports one azimuth ( $\Phi$ ) or elevation angle ( $\theta$ ), fewer than 5 beam angles will be measured. - -#### B. Test Entrance Criteria - -- Manufacturers' defined list of beam indices and their associated magnitude and phase relation between antenna ports or TAB connectors and/or beam directions with antenna array characteristics. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal analyser to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. -- Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (DL-SCH and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. -- Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. -- Extract either the beamweights, or magnitude and phase relation, or beam direction from the measured signal. - -## D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The signal relation (i.e. beamweights, or magnitude and phase relation) between antenna ports or TAB connectors, or the extracted beam direction, should match the expected relation, or beam direction, corresponding to the beam under test within a tolerance defined by the manufacturer. - -### 3.2.3.2.4 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Predefined-beam Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with predefined-beams beamforming (beamId≠0x000) and with one spatial stream (single eAxC). - -The same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.2.3 applies, but instead it is related to the uplink direction. - -#### B. Test Entrance Criteria - -- Manufacturers' defined list of beam indices and their associated magnitude and phase relation between antenna ports or TAB connectors and/or beam directions with antenna array characteristics. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal source to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the source with any set-up information needed to allow it to synch and generate the test signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- a. Build an appropriate test signal described above in the signal source of the TER. -- b. Inject the test signal into the O-RU with the application of an initial set of beamweights, or equivalently magnitude and phase relation, between all the TER ports connected to the antenna ports (or TAB connectors) to emulate the phase and magnitude difference "seen" by the antenna elements under test. For example, initial beamweights could be set to be "all equal" (i.e. no beamforming). -- c. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (UL-SCH) using Section Type 1 messages. No Section Type zero messages will be used for this test. -- d. Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. while also triggering the signal source. -- e. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. -- f. Repeat the previous steps but now in step b apply a different set of beamweights or phase relation between all the antenna ports (or TAB connectors) when injecting the test signal into the O-RU. For example, repeating the process for a number of different beamweights will simulate the reception of the test signal from different beam directions. This allows to determine if the O-RU is really focusing the sensitivity to the correct beam direction. - -### D. Test Requirement (expected result) - -1. The test frame received by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -2. The beamweights or magnitude and phase relation at the antenna ports (or TAB connectors) of the test signal that achieves the highest performance (i.e. best EVM, power, SNR, etc.) should match with the manufacturer's declaration of the beam under test. - -### 3.2.3.2.5 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Weight-based Dynamic Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with weight-based dynamic beamforming with one spatial stream (single eAxC). - -The transmitted beam direction is measured for each weighted beam required in this measurement, see below. The measured transmitted direction is compared to manufacturer-designated direction. Transmitted direction could be defined by the phase relation between the antenna ports or TAB connectors under test, or by directly extracting the beam direction. - -The elevation $\theta$ and azimuth $\Phi$ angles are defined as in [2] clause 12.4.2.2: - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Weight-based Dynamic Beamforming conformance test should evaluate the following beams for the O-RU to comply: - -- a. A weight-based beam with 0 degrees azimuth ( $\Phi$ ) and elevation ( $\theta$ ) angles. -- b. A weight-based beam with maximum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -- c. A weight-based beam with maximum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). -- d. A weight-based beam with minimum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -- e. A weight-based beam with minimum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). - -If the O-RU only supports one azimuth ( $\Phi$ ) or elevation angle ( $\theta$ ), fewer than 5 beam angles will be measured. - -The user/tester selects the bitwidth for the mantissa or scaler of the compression method applied to the beams. The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Weight-based Dynamic Beamforming conformance test should also evaluate the following compression methods for each of the supported beams described above (a. to e.) for the O-RU to comply: - -- a. No compression method applied to the beamforming weights. -- b. Block floating point compression method applied to the beamforming weights with the selected number of bit mantissa. -- c. Block scaling compression method applied to the beamforming weights with the selected number of bit scaler. -- d. $\mu$ -law compression method applied to the beamforming weights with the selected number of bit fixed width. -- e. Depending on what type of Beamspace compression the DUT supports, either Beamspace compression method applied to the beamforming weights with the selected number of bit scaler or Beamspace compression method applied to the beamforming weights with the selected number of bit mantissa. - -If the O-RU does not support all the compression methods described above, fewer than 5 compression methods will be measured. - -## B. Test Entrance Criteria - -- Manufacturers' defined list of frequency domain ( $\phi$ ) and or time domain ( $\theta$ ) weights for each supported beam, or alternatively, list of gain and phase relation, or complex beam weights, between antenna ports or TAB connectors for each supported beam. Also, the O-RU needs to report to the O-DU the antenna array characteristics. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal analyser to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- a. Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by one or two sections (DL-SCH and DCI) using Section Type 1 messages, the sections in the first symbol of the slot will contain section extension extType=0x01 to convey the beam weights, it is not required that the next sections contain extension type 1 since the same beam IDs will not change along the slot. If O-RU does not support a field, then its value should be 0x0. No Section Type zero messages will be used for this test. -- c. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- d. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. -- e. Extract either the beamweights, or magnitude and phase relation, or beam direction from the measured signal. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The signal relation (i.e. beamweights, or magnitude and phase relation) between antenna ports or TAB connectors, or the extracted beam direction, should match the expected relation, or beam direction, corresponding to the beam under test within a tolerance defined by the manufacturer. - -**3.2.3.2.6 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Weight-based Dynamic Beamforming** - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with weight-based beamforming and with one spatial stream (single eAxC). - -The same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.2.5 but applies to the uplink direction. - -**B. Test Entrance Criteria** - -- Manufacturers' defined list of frequency domain ( $\phi$ ) and or time domain ( $\theta$ ) weights for each supported beam, or alternatively, list of gain and phase relation, or complex beam weights, between antenna ports or TAB connectors for each supported beam . Also, the O-RU needs to report to the O-DU the antenna array characteristics - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal source to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the source with any set-up information needed to allow it to synch and generate the test signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- Build an appropriate test signal described above in the signal source of the TER. -- Inject the test signal into the O-RU with the application of an initial set of beamweights, or equivalently magnitude and phase relation, between all the TER ports connected to the antenna ports (or TAB connectors) to emulate the phase and magnitude difference “seen” by the antenna elements under test. For example, initial beamweights could be set to be “all equal” (i.e. no beamforming). -- Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by one or two sections (UL-SCH) using Section Type 1 messages, the sections in the first symbol of the slot will contain section extension extType=0x01 to convey the beam weights, it is not required that the next sections contain extension type 1 since the same beam IDs will not change along the slot. If O-RU does not support a field, then its value should be 0x0. No Section Type zero messages will be used for this test. -- Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. while also triggering the signal source. -- Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. -- Repeat the previous steps but now in step b apply a different set of beamweights or phase relation between all the antenna ports (or TAB connectors) when injecting the test signal into the O-RU. For example, repeating the process for a number of different beamweights will simulate the reception of the test signal from different beam directions. This allows to determine if the O-RU is really focusing the sensitivity to the correct beam direction. - -## D. Test Requirement (expected result) - -1. The test frame received by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -2. The beamweights or magnitude and phase relation at the antenna ports (or TAB connectors) of the test signal that achieves the highest performance (i.e. best EVM, power, SNR, etc.) should match with the manufacturer's declaration of the beam under test. - -### 3.2.3.2.7 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Attribute-based Dynamic Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with attributed-based dynamic beamforming with one spatial stream (single eAxC). - -If the O-RU DUT supports Attribute based Dynamic Beamforming, this test is mandatory for the O-RU DUT to be O-RAN conformant. - -The transmitted beam direction and attributes are measured for each attributed beam required in this measurement, see below. The measured transmitted direction and attributes, i.e. pointing azimuth and elevation angles, beamwidths and sidelobe suppression, is compared to manufacturer-designated direction and attributes. - -Transmitted direction and beam attributes are defined by the magnitude and phase relation between the antenna ports or TAB connectors under test, or by directly extracting the beam properties. - -The elevation $\theta$ and azimuth $\Phi$ angles are defined as in [2] clause 12.4.2.2. - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Attribute-based Dynamic Beamforming conformance test should evaluate the following beams for the O-RU to comply: - -- An attribute-based beam with 0 degrees azimuth ( $\Phi$ ) and elevation ( $\theta$ ) angles with any beamwidth and sidelobe suppression supported by the O-RU under this beam direction. -- An attribute-based beam with maximum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ) with the widest beamwidth and lowest sidelobe suppression supported for this specific beam direction. -- An attribute-based beam with maximum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ) with the narrowest beamwidth and highest sidelobe suppression supported for this specific beam direction. -- An attribute-based beam with minimum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ) with the widest beamwidth and lowest sidelobe suppression supported for this specific beam direction. -- An attribute-based beam with minimum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ) with the narrowest beamwidth and highest sidelobe suppression supported for this specific beam direction. - -If the O-RU only supports one azimuth ( $\Phi$ ) or elevation angle ( $\theta$ ), fewer than 5 beam angles and attribute configurations will be measured. - -#### B. Test Entrance Criteria - -- Manufacturers' defined list of supported beam directions (azimuth $\phi$ and elevation $\theta$ angles) attributes that are supported by the O-RU and their associated gain and phase relation, or complex weight, between antenna ports or TAB connectors and/or beam directions with antenna array characteristics. - -#### C. Test Methodology - -##### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. - -- Connect the signal analyser to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -#### b. Procedure - -- a. Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by one or two sections (DL-SCH and DCI) using Section Type 1 messages, the sections in the first symbol of the slot will contain section extension extType=0x02 to convey the beam weights, it is not required that the next sections contain extension type 2 since the same beam IDs will not change along the slot. If O-RU does not support a field, then its value should be 0x0. No Section Type zero messages will be used for this test. -- c. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- d. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. -- e. Extract either the beamweights, or magnitude and phase relation, or beam properties from the measured signal. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The signal relation (i.e. beamweights, or magnitude and phase relation) between antenna ports or TAB connectors, or the extracted beam properties, should match the expected beam properties corresponding to the beam under test within a tolerance defined by the manufacturer. - -### 3.2.3.2.8 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Attribute-based Dynamic Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with attribute-based beamforming with one spatial stream (single eAxC). - -Same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.2.7 but considering uplink direction. - -#### B. Test Entrance Criteria - -- Manufacturers' defined list of supported beam directions (azimuth $\phi$ and elevation $\theta$ angles) attributes that are supported by the O-RU and their associated gain and phase relation, or complex weight, between antenna ports or TAB connectors and/or beam directions with antenna array characteristics - -#### C. Test Methodology - -**a. Initial Conditions** - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal source to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the source with any set-up information needed to allow it to synch and generate the test signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- a. Build an appropriate test signal described above in the signal source of the TER. -- b. Inject the test signal into the O-RU with the application of an initial set of beamweights, or equivalently magnitude and phase relation, between all the TER ports connected to the antenna ports (or TAB connectors) to emulate the phase and magnitude difference “seen” by the antenna elements under test. For example, initial beamweights could be set to be “all equal” (i.e. no beamforming). -- c. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by one or two sections (UL-SCH) using Section Type 1 messages, the sections in the first symbol of the slot will contain section extension extType=0x02 to convey the beam weights, it is not required that the next sections contain extension type 2 since the same beam IDs will not change along the slot. If O-RU does not support a field, then its value should be 0x0. No Section Type zero messages will be used for this test. -- d. Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. while also triggering the signal source. -- e. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. -- f. Repeat the previous steps but now in step b apply a different set of beamweights or magnitude and phase relation between all the antenna ports (or TAB connectors) when injecting the test signal into the O-RU. For example, repeating the process for a number of different sets of beamweights will simulate the reception of the test signal from different beam directions. This allows to determine if the O-RU is really focusing the sensitivity to the correct beam properties. - -**D. Test Requirement (expected result)** - -1. The test frame received by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -2. The beamweights or magnitude and phase relation at the antenna ports (or TAB connectors) of the test signal that achieves the highest performance (i.e. best EVM, power, SNR, etc.) should match with the manufacturer’s declaration of the beam under test. - -**3.2.3.2.9 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Channel-Information-based Beamforming** - -**A. Test Description and Applicability** - -This Test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with channel-information-based beamforming with multiple spatial streams from multiple users (i.e. MU-MIMO). - -For Category A radios, the test is for each polarization separately and consequently either different or same channel models can be defined for each of the polarization. For Category B, same channel might be used for both polarizations and the test might measure each polarization separately. - -The transmitted beam direction is measured for each scenario required in this measurement. The measured transmitted direction is extracted from the decoded received signal in the TER. Transmitted direction is defined by properly receiving a data transmission between the O-RU and the target User Equipment while destroying or heavily attenuating the data transmission between the O-RU and the other User Equipment. - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Channel-Information-based Beamforming conformance test should evaluate the following scenarios for the O-RU to comply and will rely on TER Channel Emulation capabilities as shown in Figure 3.2.3.2-27. - -![Diagram of Test Equipment (RU) (TER) with Channel Emulation Capability. The diagram shows a nested box structure. The outermost box is labeled 'Test Equipment, RU (TER)'. Inside it is a green box containing a red box labeled 'DUT = O-RU'. Inside the DUT box is a 'Precoding Matrix G'. To the left of this matrix are two inputs: 'UE 0 Layer 0' (labeled 'eAxC 0') and 'UE 1 Layer 0' (labeled 'eAxC 1'). An arrow labeled 'M' points from the output of the Precoding Matrix G to a 'Channel Emulator Matrix H'. From the output of the Channel Emulator Matrix H, two arrows point to 'UE 0 Layer 0' (labeled '2') and 'UE 1 Layer 0'.](45902eaeac38a0b8d0e670b205695d13_img.jpg) - -Diagram of Test Equipment (RU) (TER) with Channel Emulation Capability. The diagram shows a nested box structure. The outermost box is labeled 'Test Equipment, RU (TER)'. Inside it is a green box containing a red box labeled 'DUT = O-RU'. Inside the DUT box is a 'Precoding Matrix G'. To the left of this matrix are two inputs: 'UE 0 Layer 0' (labeled 'eAxC 0') and 'UE 1 Layer 0' (labeled 'eAxC 1'). An arrow labeled 'M' points from the output of the Precoding Matrix G to a 'Channel Emulator Matrix H'. From the output of the Channel Emulator Matrix H, two arrows point to 'UE 0 Layer 0' (labeled '2') and 'UE 1 Layer 0'. - -Figure 3.2.3.2-27 TER with Channel Emulation Capability - -- a. A scenario where two spatial streams, or eAxC flows, are generated for two users (one layer each) with $M$ antenna ports or TAB connectors. The O-DU will report to the O-RU via C plane messages an emulated channel estimate. The emulated channel shall model a static channel, with rank not lower than the number of spatial streams, and it shall not be a block-diagonal channel. As an example, a Butler channel model could be implemented as emulated channel. The O-RU will calculate and apply the beamweight matrix in such that the received signal at the users is the same as the generated in the O-DU. It is up to the O-RU on how to calculate the beamforming weights, for example Zero-forcing, regularized zero-forcing / MMSE, etc. - -If O-RU supports Analog Beamforming (Time Domain Beamforming), the test should not apply any analogue beamforming or time domain beamforming. In this case, $M$ is not the number of antenna ports or TAB connectors but the number of TRX channels supported by the O-RU. - -**B. Test Entrance Criteria** - -- The O-RU must have at least two TRX chains with conducted antenna ports (or TAB connectors) to be connected to a signal analyser. - -- The TER equipment must either include a channel emulator between the O-RU antenna ports and the signal analyser or the signal analyser be capable of applying the required channel matrix being emulated between the O-RU and the users. -- Manufacturers' defined list of number of TRX chains and what antenna ports or TAB connectors are connected to each TRX chain. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal analyser to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- a. Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. Every symbol should be described by either one or two sections (DL-SCH and DCI) using Section Type 5 and 6 messages. No Section Type zero messages will be used for this test. -- c. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- d. Capture the test signals and pass them through a channel emulator or apply the signal processing required to emulate the channel under test. -- e. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -## D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. - -### 3.2.3.2.10 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Channel-Information-based Beamforming - -#### A. Test Description and Applicability - -This Test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with channel-information-based beamforming with multiple spatial streams from multiple users (i.e. MU-MIMO). - -Same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.2.10 but considering uplink direction. - -#### B. Test Entrance Criteria - -- The O-RU must have at least two TRX chains with conducted antenna ports (or TAB connectors) to be connected to a signal generator. -- The TER equipment must either include a channel emulator between the O-RU antenna ports and the signal generator or the signal generator be capable of applying the required channel matrix being emulated between the users and the O-RU. -- Manufacturers' defined list of number of TRX chains and what antenna ports or TAB connectors are connected to each TRX chain. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal source to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the source with any set-up information needed to allow it to synch and generate the test signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- a. Build an appropriate test signal described above in the signal source of the TER. -- b. Inject the test signals through a channel emulator or apply the required signal processing to emulate the channel under test. -- c. Inject the resulting test signals into the antenna ports (or TAB connectors). -- d. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (UL-SCH) using Section Type 5 and 6. No Section Type zero messages will be used for this test. -- e. Play the C plane messages to the O-RU respecting timing windows described in clause 2.4. while also triggering the signal source. -- f. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. - -## D. Test Requirement (expected result) - -1. The test frame received by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. - -### 3.2.3.2.11 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Flexible Predefined-beam Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with predefined-beams beamforming (beamId≠0x000) and with one spatial stream (single eAxC) using section extension 11. - -The transmitted beam direction is measured for each indexed beam required in this measurement, see below. The measured transmitted direction is compared to manufacturer-designated direction. Transmitted direction could be - -defined by the phase relation between the antenna ports or TAB connectors under test, or directly by extracting the beam direction. - -The elevation $\theta$ and azimuth $\Phi$ angles are defined as in [2] clause 12.4.2.2: - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Flexible Predefined-beam Beamforming conformance test might include multiple tests that the O-RU must comply. The test should include any two of the following beams: - -1. A beam with maximum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -2. A beam with maximum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). -3. A beam with minimum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -4. A beam with minimum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). - -**B. Test Entrance Criteria** - -- Manufacturers’ defined list of beam indices and their associated magnitude and phase relation between antenna ports or TAB connectors and/or beam directions with antenna array characteristics. - -**C. Test Methodology** - -**a. Initial Conditions** - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal analyser to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- a. Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every slot should be described by one section (DL-SCH and DCI) using Section Type 1 and will contain section extension extType=0x0B to convey the beamIDs for Beam1 and Beam2, i.e. BeamID1 and BeamID2. - -The fields in Section Extension 11 should contain the following values: - -| disableBFWs | RAD | numBundPrb | bfwCompHdr | -|-------------|-----|--------------------------|---------------------| -| 1 | 0 | floor(allocPRBsymbol /2) | (depends on method) | - -| Bundle | bfwCompParam | beamId | -|--------------|---------------------------------|---------| -| PRB bundle 0 | (depends on Compression method) | beamID1 | -| PRB bundle 1 | (depends on Compression method) | beamID2 | - -Where allocPRBsymbol is the number of allocated PRBs per symbol for the Downlink test waveform under a certain Bandwidth and Subcarrier spacing configuration. For example, for a 3GPP NR-FR1-TM1.1 with 100MHz bandwidth and 30kHz subcarrier spacing, the allocPRBsymbol is 273. - -If O-RU does not support a field, then its value should be 0x0. No Section Type zero messages will be used for this test. - -No Section Type zero messages will be used for this test. - -- c. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- d. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. -- e. Extract either the beamweights, or magnitude and phase relation, or beam direction from the measured signal. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The signal relation (i.e. beamweights, or magnitude and phase relation) between antenna ports or TAB connectors, or the extracted beam direction, should match the expected relation, or beam direction, corresponding to the beams under test within a tolerance defined by the manufacturer. - -### 3.2.3.2.12 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Flexible Predefined-beam Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with predefined-beams beamforming (beamId≠0x000) and with one spatial stream (single eAxC) using section extension 11. - -The same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.2.11 applies, but instead it is related to the uplink direction. - -#### B. Test Entrance Criteria - -- Manufacturers' defined list of beam indices and their associated magnitude and phase relation between antenna ports or TAB connectors and/or beam directions with antenna array characteristics. - -#### C. Test Methodology - -##### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal source to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the source with any set-up information needed to allow it to synch and generate the test signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -##### b. Procedure - -- a. Build an appropriate test signal described above in the signal source of the TER. - -- b. Inject the test signal into the O-RU with the application of an initial set of beamweights, or equivalently magnitude and phase relation, between all the TER ports connected to the antenna ports (or TAB connectors) to emulate the phase and magnitude difference “seen” by the antenna elements under test. For example, initial beamweights could be set to be “all equal” (i.e. no beamforming). -- c. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every slot should be described by one section (UL-SCH) using Section Type 1 messages and will contain section extension extType=0x0B to convey the beamIDs for Beam1 and Beam2, i.e. BeamID1 and BeamID2. - -The fields in Section Extension 11 should contain the following values: - -| disableBFWs | RAD | numBundPrb | bfwCompHdr | -|-------------|-----|-------------------------|---------------------| -| 1 | 0 | floor(allocPRBsymbol/2) | (depends on method) | - -| Bundle | bfwCompParam | beamId | -|--------------|---------------------------------|---------| -| PRB bundle 0 | (depends on Compression method) | beamID1 | -| PRB bundle 1 | (depends on Compression method) | beamID2 | - -Where allocPRBsymbol is the number of allocated PRBs per symbol for the Uplink test waveform under a certain Bandwidth and Subcarrier spacing configuration. For example, for a 3GPP G-FR1-A1-5 test waveform with 100MHz bandwidth and 30kHz subcarrier spacing, the allocPRBsymbol is 51. - -If O-RU does not support a field, then its value should be 0x0. No Section Type zero messages will be used for this test. - -No Section Type zero messages will be used for this test. - -- d. Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. while also triggering the signal source. -- e. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. -- f. Repeat the previous steps but now in step b apply a different set of beamweights or phase relation between all the antenna ports (or TAB connectors) when injecting the test signal into the O-RU. For example, repeating the process for a number of different beamweights will simulate the reception of the test signal from different beam directions. This allows to determine if the O-RU is really focusing the sensitivity to the correct beam direction. - -**D. Test Requirement (expected result)** - -- 1. The test frame received by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -- 2. The beamweights or equivalently the magnitude and phase relation at the antenna ports (or TAB connectors) of the test signal that achieves the highest performance (i.e. best EVM, power, SNR, etc.) should match with the manufacturer’s declaration of the beams under test. - -**3.2.3.2.13 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Flexible Real Time Weights Beamforming** - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with flexible weight-based dynamic beamforming with one spatial stream (single eAxC) using section extension 11. - -The transmitted beam direction is measured for each weighted beam required in this measurement, see below. The measured transmitted direction is compared to manufacturer-designated direction. Transmitted direction could be defined by the phase relation between the antenna ports or TAB connectors under test, or by directly extracting the beam direction. - -The elevation $\theta$ and azimuth $\Phi$ angles are defined as in [2] clause 12.4.2.2: - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Flexible Real Time Weights Beamforming conformance test should evaluate any two of following beams (called henceforth Beam1 and Beam2) for the O-RU to comply: - -1. A weight-based beam with maximum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -2. A weight-based beam with maximum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). -3. A weight-based beam with minimum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -4. A weight-based beam with minimum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Flexible Real Time Weights Beamforming conformance test should also evaluate the following compression methods for each of the supported beams described above (a. to e.) for the O-RU to comply: - -1. No compression method applied to the beamforming weights. -2. Block floating point compression method applied to the beamforming weights with 14-bit mantissa. -3. Block scaling compression method applied to the beamforming weights with 14-bit scaler. -4. $\mu$ -law compression method applied to the beamforming weights with 14-bit fixed width. -5. Depending on what type of Beamspace compression the DUT supports, either Beamspace compression method applied to the beamforming weights with 14-bit scaler or Beamspace compression method applied to the beamforming weights with 14-bit mantissa. - -If the O-RU does not support all the compression methods described above, fewer than 5 compression methods will be measured. - -## B. Test Entrance Criteria - -- Manufacturers' defined list of frequency domain ( $\phi$ ) and or time domain ( $\theta$ ) weights for each supported beam, or alternatively, list of gain and phase relation, or complex beam weights, between antenna ports or TAB connectors for each supported beam. Also, the O-RU needs to report to the O-DU the antenna array characteristics. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. - -- Connect the signal analyser to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. -- Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every slot should be described by one section (DL-SCH and DCI) using Section Type 1 and will contain section extension extType=0x0B to convey the beam weights for Beam1 and Beam2. - -The fields in Section Extension 11 should contain the following values: - -| disableBFWs | RAD | numBundPrb | bfwCompHdr | -|-------------|-----|--------------------------|---------------------| -| 0 | 0 | floor(allocPRBsymbol /2) | (depends on method) | - -| Bundle | bfwCompParam | beamId | bfwI / bfwQ | -|--------------|---------------------------------|---------|-------------------| -| PRB bundle 0 | (depends on Compression method) | beamID1 | Weights for Beam1 | -| PRB bundle 1 | (depends on Compression method) | beamID2 | Weights for Beam2 | - -Where allocPRBsymbol is the number of allocated PRBs per symbol for the TM1.1 test waveform under a certain Bandwidth and Subcarrier spacing configuration. For example, for a TM1.1 with 100MHz bandwidth and 30kHz subcarrier spacing, the allocPRBsymbol is 273. - -If O-RU does not support a field, then its value should be 0x0. No Section Type zero messages will be used for this test. - -- Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. -- Extract either the beamweights, or magnitude and phase relation, or beam direction from the measured signal. - -**D. Test Requirement (expected result)** - -- The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -- The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -- The signal relation (i.e. beamweights, or magnitude and phase relation) between antenna ports or TAB connectors, or the extracted beam direction, should match the expected relation, or beam direction, corresponding to the beams under test within a tolerance defined by the manufacturer. - -**3.2.3.2.14 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Flexible Real Time Weights Beamforming** - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with weight-based beamforming and with one spatial stream (single eAxC) using section extension 11. - -The same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.2.13 but applies to the uplink direction. - -**B. Test Entrance Criteria** - -- Manufacturers’ defined list of frequency domain ( $\phi$ ) and or time domain ( $\theta$ ) weights for each supported beam, or alternatively, list of gain and phase relation, or complex beam weights, between antenna ports or TAB connectors for each supported beam. Also, the O-RU needs to report to the O-DU the antenna array characteristics - -**C. Test Methodology** - -**a. Initial Conditions** - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal source to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the source with any set-up information needed to allow it to synch and generate the test signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- Build an appropriate test signal described above in the signal source of the TER. -- Inject the test signal into the O-RU with the application of an initial set of beam weights, or equivalently magnitude and phase relation, between all the TER ports connected to the antenna ports (or TAB connectors) to emulate the phase and magnitude difference “seen” by the antenna elements under test. For example, initial beamweights could be set to be “all equal” (i.e. no beamforming). -- Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every slot should be described by one section (UL-SCH) using Section Type 1 messages and will contain section extension extType=0x0B to convey the beam weights. - -The fields in Section Extension 11 should contain the following values: - -| disableBFWs | RAD | numBundPrb | bfwCompHdr | -|-------------|-----|--------------------------|---------------------| -| 0 | 0 | floor(allocPRBsymbol /2) | (depends on method) | - -| Bundle | bfwCompParam | beamId | bfwl / bfwQ | -|--------------|---------------------------------|---------|-------------------| -| PRB bundle 0 | (depends on Compression method) | beamID1 | Weights for Beam1 | -| PRB bundle 1 | (depends on Compression method) | beamID2 | Weights for Beam2 | - -Where allocPRBsymbol is the number of allocated PRBs per symbol for the TM1.1 test waveform under a certain Bandwidth and Subcarrier spacing configuration. For example, for a TM1.1 with 100MHz bandwidth and 30kHz subcarrier spacing, the allocPRBsymbol is 273. - -If O-RU does not support a field, then its value should be 0x0. No Section Type zero messages will be used for this test. - -- d. Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.1 while also triggering the signal source. -- e. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. -- f. Repeat the previous steps but now in step b apply a different set of beamweights or phase relation between all the antenna ports (or TAB connectors) when injecting the test signal into the O-RU. For example, repeating the process for a number of different beamweights will simulate the reception of the test signal from different beam directions. This allows to determine if the O-RU is really focusing the sensitivity to the correct beam direction. - -#### D. Test Requirement (expected result) - -1. The test frame received by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -2. The beamweights or equivalently the magnitude and phase relation at the antenna ports (or TAB connectors) of the test signal that achieves the highest performance (i.e. best EVM, power, SNR, etc.) should match with the manufacturer's declaration of the beams under test. - -### 3.2.3.2.15 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Layer nulling Beamforming - -#### A. Test Description and Applicability - -This Test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with channel-information-based beamforming with multiple spatial streams from multiple users (i.e. MU-MIMO) with section extension 14. - -For Category A radios, the test is for each polarization separately and consequently either different or same channel models can be defined for each of the polarization. For Category B, same channel might be used for both polarizations and the test might measure each polarization separately. - -The transmitted beam direction is measured for each scenario required in this measurement. The measured transmitted direction is extracted from the decoded received signal in the TER. Transmitted direction is defined by properly receiving a data transmission between the O-RU and the target User Equipment while destroying or heavily attenuating the data transmission between the O-RU and the other User Equipment. - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Layer nulling Beamforming conformance test should evaluate the following scenarios for the O-RU to comply and will rely on TER Channel Emulation capabilities as shown in Figure 3.2.3.2-27. - -- a. The conformance test will contain two test runs where in each of the test runs, the O-DU will indicate to the O-RU that one of the users/layers to be null at a time. For example, first test run will indicate only UE 0 Layer 0 to be null (i.e. null eAxC 0) while the second test run will indicate only UE 1 layer 0 to be null (i.e. null eAxC 1), see Figure 3.2.3.2-28. - -![Figure 3.2.3.2-28 Layer Nulling Beamforming Tests. The diagram shows two test runs. Test Run 1: null eAxC 0. Test Run 2: null eAxC 1. Both runs show a Test Equipment, RU (TER) containing a DUT = O-RU. The O-RU has a Precoding Matrix G and a Channel Emulator Matrix H. In Test Run 1, UE 0 Layer 0 is null (red X) and UE 1 Layer 0 is active (green check). In Test Run 2, UE 0 Layer 0 is active (green check) and UE 1 Layer 0 is null (red X).](0f4dfcf85c881a0574c955f34ef40f02_img.jpg) - -The diagram illustrates two test scenarios for layer nulling beamforming. Both are contained within a 'Test Equipment, RU (TER)' box. Inside, a 'DUT = O-RU' box contains a 'Precoding Matrix $G$ ' and a 'Channel Emulator Matrix $H$ '. The input to the precoding matrix consists of two spatial streams, 'eAxC 0' and 'eAxC 1', coming from 'UE 0 Layer 0' and 'UE 1 Layer 0' respectively. The output of the channel emulator consists of two streams, labeled '2', going to 'UE 0 Layer 0' and 'UE 1 Layer 0'. In 'Test Run 1: null eAxC 0', the output for UE 0 Layer 0 is marked with a red 'X' (null) and the output for UE 1 Layer 0 is marked with a green checkmark (active). In 'Test Run 2: null eAxC 1', the output for UE 0 Layer 0 is marked with a green checkmark (active) and the output for UE 1 Layer 0 is marked with a red 'X' (null). - -Figure 3.2.3.2-28 Layer Nulling Beamforming Tests. The diagram shows two test runs. Test Run 1: null eAxC 0. Test Run 2: null eAxC 1. Both runs show a Test Equipment, RU (TER) containing a DUT = O-RU. The O-RU has a Precoding Matrix G and a Channel Emulator Matrix H. In Test Run 1, UE 0 Layer 0 is null (red X) and UE 1 Layer 0 is active (green check). In Test Run 2, UE 0 Layer 0 is active (green check) and UE 1 Layer 0 is null (red X). - -Figure 3.2.3.2-28 Layer Nulling Beamforming Tests - -- b. A scenario where two spatial streams, or eAxC flows, are generated for two users (one layer each) with $M$ antenna ports or TAB connectors. The O-DU will report to the O-RU via C plane messages using Section Types 5 and Section Types 6 an emulated channel estimate. The emulated channel shall model a static channel, with rank not lower than the number of spatial streams, and it shall not be a block-diagonal channel. As an example, a Butler channel model could be implemented as emulated channel. The O-RU will calculate the beamweight matrix for all layers/users but it will only apply the beamweights to the users/layers that have not been indicated as null by the O-DU emulator. The TER should only receive the non-null user/layers for each of the test runs. It is up to the O-RU on how to calculate the beamforming weights, for example Zero-forcing, regularized zero-forcing / MMSE, etc. - -If O-RU supports Analog Beamforming (Time Domain Beamforming), the test should not apply any analogue beamforming or time domain beamforming. In this case, $M$ is not the number of antenna ports or TAB connectors but the number of TRX channels supported by the O-RU. - -## B. Test Entrance Criteria - -- The O-RU must have at least two TRX chains with conducted antenna ports (or TAB connectors) to be connected to a signal analyser. -- The TER equipment must either include a channel emulator between the O-RU antenna ports and the signal analyser or the signal analyser be capable of applying the required channel matrix being emulated between the O-RU and the users. -- Manufacturers' defined list of number of TRX chains and what antenna ports or TAB connectors are connected to each TRX chain. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal analyser to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. - -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -#### b. Procedure - -- a. Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. Every symbol should be described by either one or two sections (DL-SCH and DCI) using Section Type 5 and 6 messages. Section type 5 messages will contain section extension 14 indicating the nulling of the eAxC to be nullled under this test run. No Section Type zero messages will be used for this test. -- c. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- d. Capture the test signals and pass them through a channel emulator or apply the signal processing required to emulate the channel under test. -- e. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. -- f. Repeat procedure a. to e. for the other eAxC to be nullled (i.e. the remaining eAxC not tested yet). - -#### D. Test Requirement (expected result) - -1. For each of the test runs, the expected signal (i.e. the expected User containing non-nullled eAxC data) is measured by the signal analyser and should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM) -2. For each of the test runs, the non-expected signal (i.e. the non-expected User containing nullled eAxC data) should be measured but no data should be detected (or heavily attenuated) by the signal analyser. -3. For each of the test runs, the expected test frame to be received for each test run by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. - -### 3.2.3.2.16 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Layer nulling Beamforming - -#### A. Test Description and Applicability - -This Test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with channel-information-based beamforming with multiple spatial streams from multiple users (i.e. MU-MIMO) with section extension 14. - -Same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.2.15 but considering uplink direction. - -#### B. Test Entrance Criteria - -- The O-RU must have at least two TRX chains with conducted antenna ports (or TAB connectors) to be connected to a signal generator. -- The TER equipment must either include a channel emulator between the O-RU antenna ports and the signal generator or the signal generator be capable of applying the required channel matrix being emulated between the users and the O-RU. -- Manufacturers' defined list of number of TRX chains and what antenna ports or TAB connectors are connected to each TRX chain. - -#### C. Test Methodology - -#### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal source to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the source with any set-up information needed to allow it to synch and generate the test signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -#### b. Procedure - -- a. Build an appropriate test signal described above in the signal source of the TER. -- b. Inject both test signals, for both Users, through a channel emulator or apply the required signal processing to emulate the channel under test. -- c. Inject the resulting test signals into the antenna ports (or TAB connectors). -- d. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (UL-SCH) using Section Type 5 and 6. Section type 5 messages will contain section extension 14 indicating the nulling of the eAxC to be nulled under this test run. No Section Type zero messages will be used for this test. -- e. Play the C plane messages to the O-RU respecting timing windows described in section 2.4. while also triggering the signal source. -- f. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. -- g. Repeat procedure a. to f. but now null other eAxC to be nulled (i.e. the remaining eAxC not tested yet). - -#### D. Test Requirement (expected result) - -1. For each of the test runs, the expected test frame (i.e. the non-nulled eAxC) received by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -2. For each of the test runs, the non-expected test frame (i.e. the nulled eAxC) received by the TER/O-DU should be measured and confirm that no data or heavily attenuated data is measured. - -### 3.2.3.2.17 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Channel-Information-based Beamforming with mixed numerology - -#### A. Test Description and Applicability - -This Test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with channel-information-based beamforming and mixed numerology in combination with a beam-ID-based beamforming and mixed numerology. - -For Category A radios, the test is for each polarization separately and consequently either different or same channel models can be defined for each of the polarization. For Category B, same channel might be used for both polarizations and the test might measure each polarization separately. - -The two beams share the spectrum equally and the transmitted beam directions for UE-based and beam-ID-based beamforming are either sufficiently separated in space or a guard band can be signalled in between to avoid interference. On each beam, i.e. the beam signalled via beam ID and the beam signalled via UE-ID the testcase emulates a change of the numerology. - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Channel-Information-based Beamforming with mixed numerologies conformance test should evaluate the following scenarios for the O-RU to comply and will rely on TER capabilities as shown in Figure 3.2.3.2-29. - -![Figure 3.2.3.2-29: Test setup for channel information-based beamforming with mixed numerologies. The diagram shows an O-DU connected to a DUT=O-RU via eAxC 0 and eAxC 1. The O-RU contains an O-RU precoding matrix G and two beamforming paths: Beam ID based beamforming and UE ID based beamforming. The output of the O-RU is connected to an RF connection stage, which is then connected to a signal analyser. The signal analyser displays two frequency-time plots: one for 30 kHz SCS and 15 kHz SCS, and another for 30 kHz SCS and 60 kHz SCS.](14af2781d0bd19b98b10672b74daaca2_img.jpg) - -The diagram illustrates the test setup for channel information-based beamforming with mixed numerologies. On the left, an O-DU (Open Distributed Unit) is shown with two output ports labeled eAxC 0 and eAxC 1. These ports are connected to a DUT=O-RU (Device Under Test). Inside the DUT=O-RU, there is an O-RU precoding matrix G, represented by a blue rectangle. Two sets of multipliers (circles with an 'x') are shown, representing the beamforming process. The top set is labeled 'Beam ID based beamforming' and the bottom set is labeled 'UE ID based beamforming'. The outputs of these multipliers are connected to an 'RF connection stage' (blue rectangle). From the RF connection stage, the signal is sent to a signal analyser. The signal analyser displays two frequency-time plots. The top plot shows two sets of frequency resources: one with 30 kHz SCS (Subcarrier Spacing) and another with 15 kHz SCS. The bottom plot shows two sets of frequency resources: one with 30 kHz SCS and another with 60 kHz SCS. The axes are labeled 'Freq' (Frequency) and 'Time'. - -Figure 3.2.3.2-29: Test setup for channel information-based beamforming with mixed numerologies. The diagram shows an O-DU connected to a DUT=O-RU via eAxC 0 and eAxC 1. The O-RU contains an O-RU precoding matrix G and two beamforming paths: Beam ID based beamforming and UE ID based beamforming. The output of the O-RU is connected to an RF connection stage, which is then connected to a signal analyser. The signal analyser displays two frequency-time plots: one for 30 kHz SCS and 15 kHz SCS, and another for 30 kHz SCS and 60 kHz SCS. - -Figure 3.2.3.2-29 Test setup for channel information-based beamforming with mixed numerologies - -- a. A scenario where two spatial streams, or eAxC flows, are generated for two users (one layer each) with M antenna ports or TAB connectors. The O-DU will signal to the O-RU via C plane messages a beam ID based beam and a UE ID based beam that are either sufficiently separated in the spatial domain to avoid interference or a guard band is configured between the frequency domain resources. The two beams share the channel bandwidth in equal parts, depending on the applied numerology. The beam ID beam direction is based on manufacturer declaration and the O-DU may report to the O-RU via C plane messages an emulated channel estimate allowing the computing of the beamweight matrix in such that the received signal at the UE ID based beam is the same as the generated in the O-DU. It is up to the O-RU on how to calculate the beamforming weights, for example Zero-forcing, regularized zero-forcing / MMSE, etc. - -If O-RU supports Analog Beamforming (Time Domain Beamforming), the test should not apply any analogue beamforming or time domain beamforming. In this case, M is not the number of antenna ports or TAB connectors but the number of TRX channels supported by the O-RU. - -## B. Test Entrance Criteria - -- The O-RU must have at least two TRX chains with conducted antenna ports (or TAB connectors) to be connected to a signal analyser. -- The TER equipment must be able to receive the two beams via an RF connection stage. This can for example include a channel emulator between the O-RU antenna ports and the signal analyser or a switch matrix with sufficient decoupling between its connectors. -- Manufacturers' defined list of number of TRX chains and what antenna ports or TAB connectors are connected to each TRX chain. -- Manufacturer provides information about beam ID based beamforming to allow the signalling of the channel information allowing the UE-based beam in a sufficiently separated spatial direction to avoid interference. Alternatively, a guard band can be signalled between the two frequency allocations on each beam. - -## C. Test Methodology - -**a. Initial Conditions** - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal analyser to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- a. Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. Due to the symbol duration dependency on the subcarrier spacing, the section corresponding to 15 kHz SCS covers 2 OFDMA symbols duration, the section corresponding to 30 kHz SCS covers 4 OFDMA symbols and the section corresponding to 60 kHz SCS covers 8 OFDMA symbol duration to have a common measurement time of 1 ms for each numerology. -- c. The C-Plane message schedules two sections separated in the frequency domain at the same time, the channel bandwidth is divided in two sections of equal size. A guard band between the two frequency sections can be configured. One section presents beam ID based beamforming and the simultaneous section presents the UE ID based beamforming. -- d. The O-DU emulator signals Section Type 1 corresponding to beam ID specific beamforming for the measurement duration of 4 OFDMA symbols and 30 kHz SCS. The user plane data is a new PN23 sequence. After the measurement duration of 4 OFDMA symbols, the O-DU emulator signals Section Type 3 with mixed numerology and schedules an SCS of 15 kHz. The scheduling and measurement duration is 2 OFDMA symbols. The user plane data is a new PN23 sequence. The beam ID value is the same in Section Type 1 and Section Type 3 and the occupied bandwidth for both numerologies should match as much as possible. -- e. The O-DU emulator signals Section Type 5 corresponding to the UE ID based beamforming for the measurement duration of 4 OFDMA symbols and 30 kHz SCS. The user plane data is a new PN23 sequence. After the measurement duration of 4 OFDMA symbols, the O-DU emulator signals Section Type 5 with section extension 15 mixed numerology and schedules an SCS of 60 kHz. The scheduling and measurement duration is 8 OFDMA symbols. The user plane data is a new PN23 sequence. The UE ID value is different for the Section Type 5 and Section Type 5 with section extension 15 case, emulating a situation of time domain beamforming to two separate UE IDs. The occupied bandwidth for both consecutive UE ID beams should match as much as possible. -- f. The O-DU emulator may schedule after the two scheduling periods of 1 ms each (4 OFDMA symbols followed by 2 OFDMA for 15 kHz SCS / 8 OFDMA symbols for 60 kHz SCS) another two sections with 30 kHz SCS and Section Type 1 / Section Type 5 scheduling, see Figure 3.2.3.2-30. -- g. Encapsulate the IQ data in U-Plane messages. As described, there will be 4 user plane data section, each one containing a new PN23 sequence. -- h. Capture the test signals and pass them through a channel emulator or apply the signal processing required to receive the two beams generated by the DUT. -- i. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -![Figure 3.2.3.2-30 Test execution details. A diagram showing a 100 MHz bandwidth divided into sections with different numerologies (SCS = 15kHz, 30kHz, 60kHz) and beamforming types (Beam ID based BFW, UE ID based BFW).](f7cdc4fe8e310fe78ec0c3779b361efd_img.jpg) - -The figure illustrates the test execution details for a 100 MHz bandwidth. It is divided into three main sections based on numerology: Single(nominal) numerology (left), mixed numerology (center), and Single(nominal) numerology (right). The top part shows Beam ID based BFW sections, and the bottom part shows UE ID based BFW sections. An optional guard band is indicated between the two beamforming types. - -| Symbol index 15kHz | 0 | | 1 | | 2 | | 3 | | 4 | | 5 | | 6 | | | | -|--------------------|------------------------------|---|---|---|--------------------------------------------|---|---|---|------------------------------|---|----|----|----|----|----|----| -| Symbol index 30kHz | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | | | -| Symbol index 60kHz | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | -| 100 MHz | SCS = 30kHz, Section type 1 | | | | SCS = 15kHz, Section type 3 | | | | SCS = 30kHz, Section type 1 | | | | | | | | -| | SCS = 30kMHz, Section type 5 | | | | Section type 5 + Section extension type 15 | | | | SCS = 30kMHz, Section type 5 | | | | | | | | - -Figure 3.2.3.2-30 Test execution details. A diagram showing a 100 MHz bandwidth divided into sections with different numerologies (SCS = 15kHz, 30kHz, 60kHz) and beamforming types (Beam ID based BFW, UE ID based BFW). - -Figure 3.2.3.2-30 Test execution details - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. - -**3.2.3.2.18 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Bit masking for antenna mapping in Channel-Information-based Beamforming in uplink direction** - -**A. Test Description and Applicability** - -This Test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive properly a basic 3GPP test frame with bit masking signalling an antenna mapping for channel-information-based beamforming in uplink direction. - -The O-DU emulator shall signal antenna port combinations via section extension type 16 as declared by the manufacturer. An uplink signal is fed into the O-RU antenna ports signalled as belonging to the antenna mapping and the received signal should indicate good reception by analysis of EVM and PN pattern matching. In a second analysis, the uplink signal is fed into the O-RU antenna ports that are not signalled as belonging to the antenna mapping and the received signal quality, e.g. EVM should be much worse compared to the proper reception case. The UC-Plane O-RU Scenario Class Beamforming 3GPP UL – bit masking for antenna mapping in Channel-Information-based Beamforming should evaluate the following scenarios for the O-RU to comply and will rely on TER capabilities as shown in Figure 3.2.3.2-31. - -![Figure 3.2.3.2-31: Test setup for channel information-based beamforming with bit masking for antenna mapping in uplink direction. The diagram shows an O-DU connected to a DUT=O-RU. The O-DU sends a 'Section extension type 16 antenna mapping' signal to the O-RU. The O-RU contains an 'O-RU precoding matrix G'. The output of the matrix is split into two antenna groups: 'Antenna group belonging to signaled group' (blue lines) and 'Antenna group not belonging to signaled group' (red lines). Both groups are connected to an 'RF connection stage'.](01f07707259cb0193a962c1eaf725055_img.jpg) - -The diagram illustrates the test setup for channel information-based beamforming with bit masking for antenna mapping in the uplink direction. It is divided into two main sections: 'Test equipment (TER)' and 'DUT=O-RU'. On the left, an 'O-DU' block is shown with a blue arrow pointing to the 'DUT=O-RU' block, labeled 'Section extension type 16 antenna mapping'. Inside the 'DUT=O-RU' block, there is a blue box labeled 'O-RU precoding matrix G'. From this matrix, two sets of lines emerge: a blue set of four lines and a red set of four lines. The blue lines are labeled 'Antenna group belonging to signaled group' and the red lines are labeled 'Antenna group not belonging to signaled group'. Both sets of lines connect to a blue box labeled 'RF connection stage' on the right. - -Figure 3.2.3.2-31: Test setup for channel information-based beamforming with bit masking for antenna mapping in uplink direction. The diagram shows an O-DU connected to a DUT=O-RU. The O-DU sends a 'Section extension type 16 antenna mapping' signal to the O-RU. The O-RU contains an 'O-RU precoding matrix G'. The output of the matrix is split into two antenna groups: 'Antenna group belonging to signaled group' (blue lines) and 'Antenna group not belonging to signaled group' (red lines). Both groups are connected to an 'RF connection stage'. - -Figure 3.2.3.2-31 Test setup for channel information-based beamforming with bit masking for antenna mapping in uplink direction - -## B. Test Entrance Criteria - -- The O-RU must have at least two TRX chains with conducted antenna ports (or TAB connectors) to be connected to a signal generator. -- The TER equipment must be able transmit two uplink signals that are fed into the antenna ports of the O-RU. The feeding of the uplink signal into the antenna ports can be done simultaneously or consecutively. -- The TER may contain a channel emulation stage or a switch matrix to allow the proper connection of the uplink signal with the O-RU antenna port or a consecutive test with manual connection is possible -- Manufacturers' defined list of number of TRX chains and what antenna ports or TAB connectors are connected to each TRX chain. -- Manufacturer provides information about antenna mapping to enable correct signalling via C-plane -- - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal generator to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- a. The uplink signal is described by Table A.1-1 in ETSI TS 138.141-1 and is referred to as G-FR1-A1-5 with the power that is about 30 dB higher as the minimum sensitivity. The data content is a new PN23 sequence in each of the two test steps. - -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. -- c. The O-DU emulator signals via section extension type 16 without section extension 10 the antenna masking dependent on manufacturer declaration. The antenna elements belonging to the signalled antenna mask are identified by the first eAxC value in section extension type 16. -- d. Test step 1: The signal generator uplink signal containing a new PN23 sequence in the FRC G-FR1-A1-5 is connected to the antenna port identified as the first eAxC value corresponding to the situation where the uplink signal is properly connected to the receiving antenna port. The received signal should indicate a good EVM signal quality and the PN23 sequence matches between generator and analyser -- e. Test step 2: A second uplink signal containing a new PN23 sequence in the FRC G-FR1-A1-5 is connected to the antenna port not identified as the first eAxC value in the section extension type 16 message corresponding to the situation where the uplink signal is wrongly connected to the receiving antenna port. The received signal quality should be much worse compared to the signal quality detected in paragraph (d) -- f. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -#### D. Test Requirement (expected result) - -1. For the situation of the uplink signal fed into the first eAxC antenna port signalled as belonging to the antenna mask, the signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received in test step 1 by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The received uplink signal in test step 2 should indicate a EVM not satisfying the 3GPP performance or indicate a PN pattern mismatch - -### 3.2.3.2.19 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – User port grouping in Channel-Information-based Beamforming in downlink direction - -#### A. Test Description and Applicability - -This Test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with UE based antenna port grouping and channel-information-based beamforming. The test emulates a downlink signal with 2 layers belonging to the same UE. Via section extension type 17, the O-DU emulator signals the same UE ID for the two downlink layer signal and the analyser shall indicate a good signal quality. In a second test step, the signal analyser is connected to an antenna port of the O-RU that is not signalled as belonging to the user port group and the received signal quality should be much worse compared to test step 1. - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – user port grouping for antenna mapping in Channel-Information-based Beamforming should evaluate the following scenarios for the O-RU to comply and will rely on TER capabilities as shown in Figure 3.2.3.2-32 - -![Figure 3.2.3.2-32: Test setup for channel information-based beamforming with user port grouping antenna mapping in downlink direction. The diagram shows a Test equipment (TER) containing an O-DU emulator and a DUT=O-RU. The O-DU emulator is connected to the O-RU via a 'Section extension type 17 UE port grouping' interface. The O-RU contains an 'O-RU precoding matrix G' and is connected to an 'RF connection stage' which is then connected to a 'Signal analyzer'. The O-RU outputs are labeled 'UE_ID_A' for Layer 0 and 'UE_ID_B' for Layer 1.](2f272754fa2955088bc0fa508bb65a9d_img.jpg) - -The diagram illustrates the test setup for channel information-based beamforming. It is divided into three main components: Test equipment (TER), DUT=O-RU, and RF connection stage leading to a Signal analyzer. The TER contains an O-DU emulator. A 'Section extension type 17 UE port grouping' interface connects the O-DU emulator to the DUT=O-RU. The DUT=O-RU contains an 'O-RU precoding matrix G'. The O-RU has two output layers: Layer 0 (UE\_ID\_A) and Layer 1 (UE\_ID\_B). These layers are connected to the RF connection stage, which is then connected to a Signal analyzer. - -Figure 3.2.3.2-32: Test setup for channel information-based beamforming with user port grouping antenna mapping in downlink direction. The diagram shows a Test equipment (TER) containing an O-DU emulator and a DUT=O-RU. The O-DU emulator is connected to the O-RU via a 'Section extension type 17 UE port grouping' interface. The O-RU contains an 'O-RU precoding matrix G' and is connected to an 'RF connection stage' which is then connected to a 'Signal analyzer'. The O-RU outputs are labeled 'UE\_ID\_A' for Layer 0 and 'UE\_ID\_B' for Layer 1. - -Figure 3.2.3.2-32 Test setup for channel information-based beamforming with user port grouping antenna mapping in downlink direction - -- a. A scenario where two spatial streams, or eAxC flows, are generated for one user. The antenna configuration of the O-RU has $M$ antenna element rows as of manufacturer declaration and $R < M$ antenna elements will be used to transmit the two layers to the user. The O-DU will signal to the O-RU via C plane messages a UE ID based beam and a user port grouping. The O-DU may report to the O-RU via C plane messages an emulated channel estimate allowing the computing of the beamweight matrix in such that the received signal at the UE ID based beam is the same as the generated in the O-DU. It is up to the O-RU on how do the antenna port grouping and the selection of the number of $R$ antenna element rows and to calculate the beamforming weights, for example Zero-forcing, regularized zero-forcing / MMSE, etc. - -## B. Test Entrance Criteria - -- The O-RU must have at least two TRX chains with conducted antenna ports (or TAB connectors) to be connected to a signal analyser. -- The TER equipment must be able to receive the two layers via an RF connection stage. This can for example include a channel emulator between the O-RU antenna ports and the signal analyser or a switch matrix. -- Manufacturers' defined list of number of TRX chains and what antenna ports or TAB connectors are connected to each TRX chain. -- Manufacturer provides information about antenna mapping to enable correct signalling via C-plane -- - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. - -- Connect the signal analyser to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- a. Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. The user plane data content is a new PN23 for each of the two layers. -- b. The O-DU emulator signals Section Type 5 with section extension type 10 and section extension type 17 corresponding to the UE ID based beamforming. Section extension type 17 indicates the value numUeID for the first user on the two layers dedicated to this user -- c. Test step 1: The O-DU emulator provides a user plane data signal representing two layers with a new PN23 sequence on each layer. The C-Plane signals an antenna port grouping using the section extension type 17. The received signal should indicate a good EVM signal quality and the PN23 sequence matches between generator and analyser on both layers dedicated to the user. -- d. Test step 2: The signal analyser is connected to an antenna port that is not signalled as belonging to the user port group via section extension type 17. This can be done simultaneously to test step 1 or consecutively. The received signal quality should be much worse compared to the signal quality detected in test step 1. -- e. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -**D. Test Requirement (expected result)** - -1. The signal measured on the two layers belonging to the user group port by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The received downlink signal in test step 2 should indicate a EVM not satisfying the 3GPP performance or indicate a PN pattern mismatch - -**3.2.3.2.20 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – DMRS based Beamforming** - -**A. Test Description and Applicability** - -This Test is CONDITIONAL MANDATORY, the condition being O-RUs that support either DMRS-EQ or DMRS-NEQ. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with Demodulation Reference Signal-based beamforming (DMRS-BF) with multiple spatial streams from multiple users (i.e. MU-MIMO) using Section Extension 24 (SE24). - -The UC-Plane O-RU Scenario Class Beamforming 3GPP UL – DMRS based Beamforming conformance test will rely on TER Beamforming capabilities as shown in Figure 3.2.3.2-8. - -![Figure 3.2.3.2-8: TER with Beamforming Capability. This block diagram shows the Test Equipment (RU (TER)) containing a DUT (O-RU) and an RF Signal Generator / System. The DUT (O-RU) contains a DMRS-BF block. The RF Signal Generator / System contains a Signal Generator. The Signal Generator provides input to the DMRS-BF block via a Beamformer. The DMRS-BF block outputs eAxC 0 and eAxC 1 to UE 0 Layer 0 DMRS 0 and UE 1 Layer 0 DMRS 1 respectively. The DMRS-BF block is connected to the Beamformer via M antenna ports. The Beamformer is connected to the Signal Generator via 2 antenna ports.](7aeb1d06016b3a52a1d68ed9518dbbf4_img.jpg) - -Figure 3.2.3.2-8: TER with Beamforming Capability. This block diagram shows the Test Equipment (RU (TER)) containing a DUT (O-RU) and an RF Signal Generator / System. The DUT (O-RU) contains a DMRS-BF block. The RF Signal Generator / System contains a Signal Generator. The Signal Generator provides input to the DMRS-BF block via a Beamformer. The DMRS-BF block outputs eAxC 0 and eAxC 1 to UE 0 Layer 0 DMRS 0 and UE 1 Layer 0 DMRS 1 respectively. The DMRS-BF block is connected to the Beamformer via M antenna ports. The Beamformer is connected to the Signal Generator via 2 antenna ports. - -Figure 3.2.3.2-8 TER with Beamforming Capability - -As defined in introduction of clause 3.2.3.2 UC-Plane O-RU Scenario Class Beamforming, each of the UE layer in Figure 3.2.3.2-8 shall use a standard 3GPP Reference Sensitivity level definition (clause 7.2 and Annex A TS138.141-1) of the Conducted Receiver Characteristic Test (clause 7 ETSI TS 138.141). The power levels shall be at least 30dB above Reference Sensitivity power level as described in clause 3.2.1.1. The test numerology will be preferably 30kHz subcarrier spacing and 100 MHz Bandwidth, if supported. Otherwise, it shall use any available subcarrier space, and the highest bandwidth supported by the O-RU DUT. In addition, the uplink test vector will be generated with UL-SCH in UL slots and allocated to the PRBs 0 to 50 truncated to the carrier bandwidth used for testing. - -![Figure 3.2.3.2-9: Uplink test vector to be generated by RF signal generator for each UE layer. This is a screenshot of a signal waveform display. The y-axis represents amplitude in dB, ranging from -20 to 20. The x-axis represents time in seconds, ranging from 0 to 20. The display shows a solid blue horizontal bar at approximately 0 dB, indicating a constant power level over time.](0b477f992e8c9df386a990881e6c218c_img.jpg) - -Figure 3.2.3.2-9: Uplink test vector to be generated by RF signal generator for each UE layer. This is a screenshot of a signal waveform display. The y-axis represents amplitude in dB, ranging from -20 to 20. The x-axis represents time in seconds, ranging from 0 to 20. The display shows a solid blue horizontal bar at approximately 0 dB, indicating a constant power level over time. - -Figure 3.2.3.2-9 Uplink test vector to be generated by RF signal generator for each UE layer - -Note that this test vector is defined for a Single Input Single Output (SISO) scenario. However, for this test, the test vector is expanded to evaluate the test scenario where two spatial streams, or eAxC flows, are scheduled at the same resource allocation for two users (with one layer each) and with M antenna ports or TAB connectors. The CUSM-Plane emulator will signal to the O-RU via C-plane messages the scheduling of the two ueIds, using Section Type 5 and Section Extension 10 with beamGroupType=10b or beamGroupType=11b depending on O-RU capabilities. - -This test case does not test allocated IPN measurement (MEAS\_IPN\_ALLOC =DISABLED), antenna DMRS SNR (andDmrsSnr=0), transform precoding and self-assembly. The CUSM-Plane emulator shall assign and schedule the ueIds using any supported number of least significant bits of the ueId to indicate the layers within each user. If an O-RU supports ueId persistence, ueId persistence shall not be used “ueId-persistence-enabled=FALSE”. - -The CUSM-Plane emulator will inform the O-RU of the DMRS configurations for the two streams using Section Extension 24 with entryType 1 and 2. The two DMRS configurations are as follows: - -| | UE 0 Layer 0 (DMRS 0) | UE 1 Layer 0 (DMRS 1) | -|-----------------------------------------------------------|-----------------------|-----------------------| -| Ports | 1000 | 1002 | -| scrambling ID (n_{scid}) | 0 | 1 | -| Scrambling ID 0 () | 2 | 3 | -| Scrambling ID 0 () | 4 | 5 | -| DMRS Power Boosting | 3 dB | | -| UL DMRS Configuration | Type 1 | | -| DMRS Duration (maxLength) | len1 (Single Symbol) | | -| DMRS Additional Position (dmrs-AdditionalPosition) | 1+1 (2) | | -| UL Mapping Type | A | | -| l_0 | pos2 | | -| DMRS Uplink Transform Precoding r16 | False | | -| Transform Precoding | False | | - -Same DMRS signal can be used for all available polarizations. Each polarization might be measured separately. - -If O-RU supports any other beamforming, these shall not be exercised and tested. If O-RU supports Analog Beamforming (Time Domain Beamforming), the test should not apply any analogue beamforming or time domain beamforming. In this case, $M$ is not the number of antenna ports or TAB connectors but the number of TRX channels supported by the O-RU. - -There are two layers with two different DMRS configurations to measure in this scenario, two users with one layer each. A successful received layer is defined as properly receiving data transmission at the O-DU emulator side from a corresponding layer transmitted by a User Equipment. This received data transmission shall be successfully received when it matches the DMRS configuration being signalled to the O-RU. - -## B. Test Entrance Criteria - -- The O-RU has at least two TRX chains with conducted antenna ports (or TAB connectors) to be connected to a signal generator. -- The O-RU supports enough entry tables of DMRS configuration to process the test vector and configuration under test. -- The TER equipment either includes a beamformer between the O-RU antenna ports and the UE signal generator or the signal generator be capable of emulating different AoA for different UE. -- The TER equipment is responsible for generating the RF signals for each UE layer as described in Section A, the corresponding matching O-RAN fronthaul traffic with Section ST5, SE10 and SE24 and the configuration of the DUT via M-Plane. -- Manufacturers' defined list of number of TRX chains and what antenna ports or TAB connectors are connected to each TRX chain. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal source to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the source with any set-up information needed to allow it to synch and generate the test signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -#### b. Procedure - -- a. Build an appropriate test signal described in Section A in the signal source of the TER. -- b. Inject the test signals through a beamformer or apply the required signal processing to the layers under test. -- c. Get the resulting test signals ready to be injected into the antenna ports (or TAB connectors). -- d. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test using Section Type 5 with Section Extension 10 and Section Extension 24. -- e. Play the C-plane messages to the O-RU respecting timing windows described in clause 2.4. while also triggering the signal source so the signal is injected into the antenna ports (or TAB connectors). -- f. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U-plane messages to the O-DU emulator. -- g. Allow for the O-DU emulator to capture the U-Plane messages sent by the O-RU and to run the following measurements on the extracted IQ data for each of the users/layers: - - if O-RU implements DMRS-BF-EQ: - - EVM of the received equalized IQ data (no channel estimation and equalization are used in TER). - - BER or BLER of the received equalized IQ data after layer demapping and decoding in the TER. - - -NOTE 1: The measured BER or BLER depends on the algorithms implemented in both the O-RU DUT and the O-DU TER. - -NOTE 2: The algorithms for demapping and decoding to be used in TER are left for future study. - - if O-RU implements DMRS-BF-NEQ: - - EVM of the received non-equalized IQ data after the channel estimation and equalization operation in the TER. - - -NOTE 3: The measured EVM depends on the algorithms implemented in both the O-RU DUT and the O-DU TER. - -NOTE 4: The algorithms for channel estimation and equalization to be used in TER are left for future study. - - BER or BLER of the received non-equalized IQ data after Channel Estimation, equalization, layer demapping and decoding in the TER. - - -NOTE 5: The measured BER or BLER depends on the algorithms implemented in both the O-RU DUT and the O-DU TER. - -NOTE 6: The algorithms for demapping and decoding to be used in TER are left for future study. - - demodulate, decode and extract the payload. - -#### D. Test Requirement (expected result) - -The test frame received by the TER/O-DU emulator for each of the users/layers should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data (payload). - -Report EVM and BER or BLER measured during the test. - -### 3.2.3.2.21 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – DMRS based Beamforming about Symbol reordering - -The FDD conducted test case for DMRS based beamforming about symbol reordering is the same as the test case described in clause 3.2.5.2.12 for the TDD conducted case with the exception that references made to the clause 3.2.5.2.11 shall be replaced to references to the clause 3.2.3.2.20 for this test case. - -### 3.2.3.2.22 UC-Plane O-RU Scenario Class Extended using section extension 24 for DMRS-BF - -The FDD conducted test case for extended DMRS based beamforming using section extension 24 is the same as the test case described in clause 3.2.5.2.13 for the TDD conducted case with the exception that references made to the clause 3.2.5.2.11 shall be replaced to references to the clause 3.2.3.2.20 for this test case. - -### 3.2.3.3 UC-Plane O-RU Scenario Class Compression (CMP) - -Validate the correct implementation and interpretation of mandatory and optional IQ data compression formats described in [2]. Also, evaluate the consistency in U-Plane signalling. - -It applies to the O-RAN CUS Specification [2]: - -- Clause 7.4 -- Clause 7.5.2.10 -- Clause 8.3.3.13 -- Clause 8.3.3.15/16/17 -- Clause 8.3.2 -- Clause 8.3.3 -- Table 10.2-1 -- Annex A -- Annex A.6 - -The objective is primarily to test the protocol, prior to the compression algorithms performance. - -**Signalling:** IQ Compression related fields in UC-Plane messages include: - -- U-Plane IQ data field -- C-Plane udCompHdr (per clause 7.5.2.10 of [2]) -- U-Plane udComphdr (per clause 8.3.3.13 of [2]) -- U-Plane udCompParam (per clause 8.3.3.15 of [2]) - -**Compression:** The current specification [2] includes 7 compression modes, including uncompressed mode (fixed point). Tests should cover each one of these modes - -- fixed-point -- block floating-point -- block scaling -- mu-law -- modulation compression (modulation compression not included in this document) -- Block Floating Point + selective RE sending -- Modulation Compression + selective RE sending - -**IQ Bit Width:** IQ information can be represented using different bit width (1-16 bits). To optimize test time, tests should be performed on a subset of bit widths - -For fixed point, block floating point, block scaling, mu-law compressions the subset of bit widths to be tested are - -- 9 bits -- 14 bits - -For modulation compression bit width 4 is used for the test. - -### 3.2.3.3.1 Overview of Compression Test Methodology - -A common test methodology and structure will be used across all compression test cases. Each one of the test cases will be defined with specific input parameters and expected output values. - -To minimize influence of the Radio's RF performance to the test results, the test methodology will be based on a relative comparison between modulated signal measurements performed on a test frame with uncompressed IQ (fixed 16 bits) and measurements on the same test frame using compressed IQ. The test will verify that the difference between measurements fits within an acceptable range for the test to pass. - -For downlink test, the modulated signal measurement is performed by a signal analyser on the antenna port of the O-RU. - -For uplink measurement, the modulated signal measurement is performed with the IQ extracted from the Uplink U-Plane data sent by the O-RU on the O-RAN interface. - -The following paragraphs in this overview section outline the details of these common test methodologies. - -#### 3.2.3.3.1.1 Test Frame - -The test frames used for compression conformance test will be referred in this document as “**NR-FR1-CMP-TST-FRAME-DL**” Downlink Standard Compression Test frame and “**NR-FR1-CMP-TST-FRAME-UL**” Uplink Standard Compression Test frame. They are 5G NR frames based on the description in clause 3.2.1.1.5 with specific attributes described below. - -The Downlink UC-Plane test stimulus file includes the C-Plane and U-Plane messages that require the O-RU to transmit on the downlink the NR-FR1-CMP-TST-FRAME-DL test frame. - -The Uplink C-Plane test stimulus file includes the C-Plane messages that require the O-RU to provide the uplink U-Plane messages according to the NR-FR1-CMP-TST-FRAME-UL test frame received by the O-RU on its antenna port. - -Signalling and IQ information will be based on various compression schemes - -**Table 3.2.3-7 Stimulus Files for Static Compression Test.** - -| Stimulus File Name | Description | -|----------------------------------------|-----------------------------------------------------------------------------------------------| -| NR-FR1-CMP-TST-FRAME-ST-DL-UNC-16B | Static Downlink Uncompressed (CU-plane) | -| NR-FR1-CMP-TST-FRAME-ST-UL-UNC-16B | Static Uplink Uncompressed (C-plane only) | -| NR-FR1-CMP-TST-FRAME-ST-DL-FPF-9B | Static Downlink Fixed Point 9 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-ST-DL-FPF-14B | Static Downlink Fixed Point 14 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-ST-UL-FPF-9B | Static Uplink Fixed Point 9 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-ST-UL-FPF-14B | Static Uplink Fixed Point 14 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-ST-DL-BFP-9B | Static Downlink Block Floating Point 9 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-ST-DL-BFP-14B | Static Downlink Block Floating Point 14 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-ST-UL-BFP-9B | Static Uplink Block Floating Point 9 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-ST-UL-BFP-14B | Static Uplink Block Floating Point 14 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-ST-DL-BSC-9B | Static Downlink Block Scaling 9 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-ST-DL-BSC-14B | Static Downlink Block Scaling 14 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-ST-UL-BSC-9B | Static Uplink Block Scaling 9 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-ST-UL-BSC-14B | Static Uplink Block Scaling 14 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-ST-DL-MLW-9B | Static Downlink Mu-Law 9 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-ST-DL-MLW-14B | Static Downlink Mu-Law 14 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-ST-UL-MLW-9B | Static Uplink Mu-Law 9 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-ST-UL-MLW-14B | Static Uplink Mu-Law 14 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-ST-DL-MC | Static Downlink Modulation Compression | -| NR-FR1-CMP-TST-FRAME-ST-DL-UNC-BRE-16B | Static Downlink Uncompressed (CU-plane) with both empty and allocated RE in the same symbol | -| NR-FR1-CMP-TST-FRAME-ST-UL-UNC-BRE-16B | Static Uplink Uncompressed (C-plane only) with both empty and allocated RE in the same symbol | -| NR-FR1-CMP-TST-FRAME-ST-DL-BRE-9B | Static Downlink Block Floating Point + Selective RE 9 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-ST-DL-BRE-14B | Static Downlink Block Floating Point + Selective 14 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-ST-UL-BRE-9B | Static Uplink Block Floating Point 9 Bits + Selective RE (C-plane only) | -| NR-FR1-CMP-TST-FRAME-ST-UL-BRE-14B | Static Uplink Block Floating Point 14 Bits + Selective RE (C-plane only) | -| NR-FR1-CMP-TST-FRAME-ST-DL-MRE | Static Downlink Modcomp + Selective RE Compression (CU_plane) | - -**Table 3.2.3-8 Stimulus Files for Non-Static Compression Test** - -| Stimulus File Name | Description | -|----------------------------------------|-----------------------------------------------------------------------------------------------| -| NR-FR1-CMP-TST-FRAME-NS-DL-UNC-16B | Downlink Uncompressed (CU-plane) | -| NR-FR1-CMP-TST-FRAME-NS-UL-UNC-16B | Uplink Uncompressed (C-plane) | -| NR-FR1-CMP-TST-FRAME-NS-DL-FPF-9B | Downlink Fixed Point 9 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-NS-DL-FPF-14B | Downlink Fixed Point 14 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-NS-UL-FPF-9B | Uplink Fixed Point 9 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-NS-UL-FPF-14B | Uplink Fixed Point 14 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-NS-DL-BFP-9B | Downlink Block Floating Point 9 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-NS-DL-BFP-14B | Downlink Block Floating Point 14 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-NS-UL-BFP-9B | Uplink Block Floating Point 9 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-NS-UL-BFP-14B | Uplink Block Floating Point 14 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-NS-DL-BSC-9B | Downlink Block Scaling 9 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-NS-DL-BSC-14B | Downlink Block Scaling 14 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-NS-UL-BSC-9B | Uplink Block Scaling 9 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-NS-UL-BSC-14B | Uplink Block Scaling 14 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-NS-DL-MLW-9B | Downlink Mu-Law 9 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-NS-DL-MLW-14B | Downlink Mu-Law 14 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-NS-UL-MLW-9B | Uplink Mu-Law 9 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-NS-UL-MLW-14B | Uplink Mu-Law 14 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-NS-DL-MC | Non-Static Downlink Modulation Compression | -| NR-FR1-CMP-TST-FRAME-NS-DL-UNC-BRE-16B | Static Downlink Uncompressed (CU-plane) with both empty and allocated RE in the same symbol | -| NR-FR1-CMP-TST-FRAME-NS-UL-UNC-BRE-16B | Static Uplink Uncompressed (C-plane only) with both empty and allocated RE in the same symbol | -| NR-FR1-CMP-TST-FRAME-NS-DL-BRE-9B | Downlink Block Floating Point + Selective RE 9 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-NS-DL-BRE-14B | Downlink Block Floating Point + Selective RE 14 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-NS-UL-BRE-9B | Uplink Block Floating Point + Selective RE 9 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-NS-UL-BRE-14B | Uplink Block Floating Point + Selective RE 14 Bits (C-plane only) | -| NR-FR1-CMP-TST-FRAME-NS-DL-MRE | Downlink Modcomp + Selective RE Compression | - -### 3.2.3.3.1.2 Test Frame Power - -To ensure that the compressed IQ exponent value is properly tested, each symbol of the test frame will include 3 sections with different power levels. The Power levels are relative powers to the first group of PRBs transmitted. Any valid 3GPP power level may be used for the first set of PRBs as long as the power levels of the remaining PRBs are also valid. Figure 3.2.3.3-33 below shows PRB power relative to the first set of PRBs. - -- 0 dB for the bottom third of total PRBs in the symbol (referred as PDSCH0) -- -10 dB for the middle third of total PRBs in the symbol (referred as PDSCH1) -- -20 dB for the upper third of total PRBs in the symbol (referred as PDSCH2) - -The spectrum representation of the frame shown in Figure 3.2.3.3-33 below highlights the various power levels for each group of PRBs within a symbol. - -![Figure 3.2.3.3-33 PRB Spectrum Power Visualization: A spectrum plot showing power levels across a 122.88 MHz span. The y-axis represents power in dB, ranging from -120 dB to 0 dB. The plot shows a green signal with three distinct power levels corresponding to the PRB groups: PDSCH0 (0 dB), PDSCH1 (-10 dB), and PDSCH2 (-20 dB).](9cc404b84df8122128a097d6ada44e3d_img.jpg) - -Figure 3.2.3.3-33 PRB Spectrum Power Visualization: A spectrum plot showing power levels across a 122.88 MHz span. The y-axis represents power in dB, ranging from -120 dB to 0 dB. The plot shows a green signal with three distinct power levels corresponding to the PRB groups: PDSCH0 (0 dB), PDSCH1 (-10 dB), and PDSCH2 (-20 dB). - -Figure 3.2.3.3-33 PRB Spectrum Power Visualization - -3.2.3.3.1.3 Test Frame User data - -To validate that user data has not been impacted by compression, the test payload for the 3 sections is each based on an individual PN23 sequence that will be measured and compared by the test apparatus. - -3.2.3.3.1.4 Test Frame Modulation Scheme - -To maximise coverage on the compressed IQ mantissa value, the test frame will use the highest possible modulation, limited to 256 QAM modulation for downlink. An example measurement is show in Figure 3.2.3.3-34. - -| Name | Enabled | Power | DMRS Port(s) | SlotIndex | Symbol | BWP | PRB Allocation | RNTI | Coding | NDI | RVin... | HARQ ID | MCS | Modulation | Payload | -|-----------|---------|------------|--------------|-----------|--------|---------------|------------------|------|--------|-----|---------|---------|-----|------------|---------| -| DL-SCH1_D | On | 0.00 dB | 0 | 0:17 | 0:13 | BWP1 (SCS30k) | RAType1, 3:89 | 0 | Off | 0 | 0 | 0 | 20 | QAM256 | PN9 | -| DL-SCH2_D | On | -10.00 ... | 0 | 0:17 | 0:13 | BWP1 (SCS30k) | RAType1, 90:179 | 2 | Off | 0 | 0 | 0 | 20 | QAM256 | PN9 | -| DL-SCH3_D | On | -20.00 ... | 0 | 0:17 | 0:13 | BWP1 (SCS30k) | RAType1, 180:272 | 0 | Off | 0 | 0 | 0 | 20 | QAM256 | PN9 | - -Figure 3.2.3.3-34 Example User Data Modulation Validation - -3.2.3.3.1.5 Summary of Required Measurements for Compression Tests - -3 measurements types will be required for downlink tests and 4 measurements will be required for uplink tests. - -- **Power level:** Using the test frames (NR-FR1-CMP-TST-FRAME-DL and NR-FR1-CMP-TST-FRAME-UL) sent twice with both compressed and uncompressed IQ data, power level measurements are performed to validate compression algorithms influence on Exponent (udCompParam). - -The Power level measurements are called: - -- CMP-Uncompressed-Measured-Power-PDSCH0 in dBm -- CMP-Compressed-Measured-Power-PDSCH0 in dBm -- CMP-Uncompressed-Measured-Power-PDSCH1 in dBm -- CMP-Compressed-Measured-Power-PDSCH1 in dBm -- CMP-Uncompressed-Measured-Power-PDSCH2 in dBm -- CMP-Compressed-Measured-Power-PDSCH2 in dBm - -For the test to pass, the difference between measurements should be within an acceptable range, called - -- ACC\_PWR\_PDSCH0 = $\pm 1$ dB - -- ACC\_PWR\_PDSCH1 = $\pm 1$ dB -- ACC\_PWR\_PDSCH2 = $\pm 1$ dB -- -- **EVM:** Using a common test frame sent twice with both compressed and uncompressed IQ data, EVM measurements comparisons between uncompressed IQ and compressed IQ will help validate acceptable compression influence on signal quality. - -These 6 EVM measurements required: - -- CMP-Uncompressed-Measured-EVM-PDSCH0 in % -- CMP-Compressed-Measured-EVM-PDSCH0 in % -- CMP-Uncompressed-Measured-EVM-PDSCH1 in % -- CMP-Compressed-Measured-EVM-PDSCH1 in % -- CMP-Uncompressed-Measured-EVM-PDSCH2 in % -- CMP-Compressed-Measured-EVM-PDSCH2 in % - -For the test to pass, the difference between the compressed and uncompressed measurements for the same PDSCH signal must be within the following range: - -- ACC\_EVM\_PDSCH0 $\leq 4$ percentage points -- ACC\_EVM\_PDSCH1 $\leq 4$ percentage points -- ACC\_EVM\_PDSCH2 $\leq 4$ percentage points - -An example measurement showing both power and EVM is shown below in Figure 3.2.3.3-35. - -![Figure 3.2.3.3-35: Example Compression EVM Measurement. The figure consists of a spectrum plot on the left and a data table on the right. The plot shows a green signal with a power level around -40 dBm across a 96 MHz span centered at 1 GHz. The table provides detailed EVM and power measurements for various channels.](a6e999d9ce095e6092342ba352b60991_img.jpg) - -| Name | EVM (%rms) | Power per RE (dBm) | Modulation | -|-------------|------------|--------------------|------------| -| PDSCH0 | 0.011 | -32.77 | QAM256 | -| PDSCH0_DMRS | 0.010 | -32.78 | QPSK | -| PDSCH1 | 0.011 | -42.78 | QAM256 | -| PDSCH1_DMRS | 0.011 | -42.78 | QPSK | -| PDSCH2 | 0.055 | -52.78 | QAM256 | -| PDSCH2_DMRS | 0.053 | -52.78 | QPSK | -| PDCCH0 | 0.127 | -32.78 | QPSK | -| PDCCH0_DMRS | 0.126 | -32.78 | QPSK | - -Figure 3.2.3.3-35: Example Compression EVM Measurement. The figure consists of a spectrum plot on the left and a data table on the right. The plot shows a green signal with a power level around -40 dBm across a 96 MHz span centered at 1 GHz. The table provides detailed EVM and power measurements for various channels. - -Figure 3.2.3.3-35 Example Compression EVM Measurement - -- **Payload Data Integrity:** comparing user data between the O-RAN test frame and the RF measurement to validate that compression does not influence user data. The User data measurements are called: - - CMP-Uncompressed-BER-PDSCH0 - - CMP-Uncompressed-BER-PDSCH1 - - CMP-Uncompressed-BER-PDSCH2 - - CMP-Compressed-BER-PDSCH0 - - CMP-Compressed-BER-PDSCH1 - - CMP-Compressed-BER-PDSCH2 - -For the data integrity test to pass, the comparison between stimulus payload and the measured payload should be free of any errors (i.e. BER=0). - -- **Presence/Absence of U-Plane Header measurements (uplink only):** to validate that in the U-Plane PRB header, the udCompHeader, “reserved” and udCompParam fields are correctly absent for Static compression mode or present for other compression modes. - -Table 3.2.3-9 describes the measurements required for each compression option in the downlink. - -**Table 3.2.3-9 Measurements Required for Specific Downlink Compression Options.** - -| Downlink | Power Level | EVM | Data Integrity | -|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| -| Uncompressed IQ (fixed 16 bits) | Perform power measurements on the 3 groups of PRBs to create 3 power reference points | Perform EVM measurements on the 3 groups of PRBs to create 3 EVM reference points | N/A | -| Fixed point (< 16 bits fixed IQ) | Perform the test using same test waveforms in compressed mode and check if 3 power measurements are within acceptable range | Perform the test using same test waveforms in compressed mode and check if 3 EVM measurements are within acceptable range | If power level and EVM OK, then verify user data integrity with BER measurement on payload | -| Block floating point | Perform the test using same test waveforms in compressed mode and check if 3 power measurements are within acceptable range | Perform the test using same test waveforms in compressed mode and check if 3 EVM measurements are within acceptable range | If power level and EVM OK, then verify user data integrity with BER measurement on payload | -| Block scaling | Same as above | Same as above | Same as above | -| Mu Law | Same as above | Same as above | Same as above | -| Modulation Compression | Same as above | Same as above | Same as above | -| Block floating point + Selective RE | Same as above | Same as above | Same as above | -| Block scaling + Selective RE | Same as above | Same as above | Same as above | - -**3.2.3.3.1.6 Compression Tests reference table** - -As the same methodology is used across the different compression modes, the conformance test can be viewed as series of instances of the same test structure with different parameter values as shown below in - -**Table 3.2.3-10 Compression Test Reference Table** - -| Test name | DL/UL | Compression | IQ Width | -|-----------------------------------------------------------------|-------|-------------|-------------------| -| UC-Plane O-RU CMP Scenario - Static Format (SF) | | | | -| UC-Plane O-RU CMP Scenario Static Format (SF) Fixed-Point (FPF) | DL | Fixed point | 9 bits
14 bits | - -| | | | | -|--------------------------------------------------------------------------------------|----|---------------------------------------|-------------------| -| | UL | Fixed Point | 9 bits
14 bits | -| UC-Plane O-RU CMP Scenario Static Format (SF) Block Floating Point (BFP) | DL | Block Floating point | 9 bits
14 bits | -| | UL | Block Floating point | 9 bits
14 bits | -| UC-Plane O-RU CMP Scenario Static Format (SF) Block Scaling (BSC) | DL | Block Scaling | 9 bits
14 bits | -| | UL | Block Scaling | 9 bits
4 bits | -| UC-Plane O-RU CMP Scenario Static Format (SF) Mu-Law (MLW) | DL | Mu-Law | 9 bits
14 bits | -| | UL | Mu-Law | 9 bits
14 bits | -| UC-Plane O-RU CMP Scenario Static Format (SF) Modulation Compressed Format | DL | Modulation Compression | N/A | -| UC-Plane O-RU CMP Scenario Static Format Modulation Compressed Format | DL | Block Floating point + Selective RE | 9 bits
14 bits | -| | UL | Block Floating point + Selective RE | 9 bits
14 bits | -| UC-Plane O-RU CMP Scenario Static (ST) mod-compr Format + Selective RE (MRE) | DL | Modulation Compression + Selective RE | 4-bits | -| UC-Plane O-RU CMP Scenario - Non-Static Format Test (NS) | | | | -| UC-Plane O-RU CMP Scenario Non-Static (NS) Fixed-Point (FPF) | DL | Fixed point | 9 bits
14 bits | -| | UL | Fixed Point | 9 bits
14 bits | -| UC-Plane O-RU CMP Scenario Non-Static (NS) Block Floating Point (BFP) | DL | Block Floating point | 9 bits
14 bits | -| | UL | Block Floating point | 9 bits
14 bits | -| UC-Plane O-RU CMP Scenario Non-Static (NS) Block Scaling (BSC) | DL | Block Scaling | 9 bits
14 bits | -| | UL | Block Scaling | 9 bits
4 bits | -| UC-Plane O-DU CMP Scenario Non-Static (NS) Mu-Law (MLW) | DL | Mu-Law | 9 bits
14 bits | -| | UL | Mu-Law | 9 bits
14 bits | -| UC-Plane O-RU CMP Scenario Non-Static (NS) Modulation Compressed Format | DL | Modulation Compression | 4-bits | -| UC-Plane O-RU CMP Scenario Non-Static (NS) Block Floating Point + Selective RE (BRE) | DL | Block Floating point + Selective RE | 9 bits
14 bits | -| | UL | Block Floating point + Selective RE | 9 bits
14 bits | -| UC-Plane O-RU CMP Scenario Non-Static (NS) mod-compr Format + Selective RE (MRE) | DL | Modulation Compression + Selective RE | 4-bits | - -### 3.2.3.3.1.7 Results Analysis - -In general, for each specific Compression Test in this conformance test document, the test will pass if the following conditions are met: - -- Power measurement differences between Uncompressed and Compressed are within acceptable range -- EVM measurement difference between Uncompressed and Compressed are within acceptable range -- Data integrity measurements show no data corruption -- Uplink U-Plane Header measurements exclude fields for static compression - -These test criteria and expected results are summarized below in 3.2.3.3-6. - -**Table 3.2.3-1 Compression Test Acceptance Threshold Criteria** - -| Test name | Test Attributes | | | Acceptance Threshold Criteria | | | -|----------------------------------------------------------------------------------|-----------------|---------------------------------------|----------|----------------------------------------------------------------------|---------------------------------------------------------------------------------|---------| -| | DL UL | Compression | IQ Width | Power difference | EVM difference | BER | -| UC-Plane O-RU CMP Scenario Fixed-Point Format (FPF) | DL | Fixed point | 9 bits | ACC_PWR_PDSCH0 =
ACC_PWR_PDSCH1 =
ACC_PWR_PDSCH2 =
+/- 1 dB | ACC_EVM_PDSCH0 =
ACC_EVM_PDSCH1 =
ACC_EVM_PDSCH2
≤ 4 percentage points | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| | | | 9 bits | | | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| | UL | Fixed Point | 9 bits | | | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| | | | 9 bits | | | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| UC-Plane O-RU CMP Scenario Block Floating Point Compression (BFP) | DL | Block Floating point | 9 bits | Same as above | Same as above | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| | | | 9 bits | | | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| | UL | Block Floating point | 9 bits | | | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| | | | 9 bits | | | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| UC-Plane O-RU CMP Scenario Block Scaling Compression (BSC) | DL | Block Scaling | 9 bits | Same as above | Same as above | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| | | | 9 bits | | | BER = 0 | -| | | | 4 bits | | | BER = 0 | -| | UL | Block Scaling | 9 bits | | | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| | | | 9 bits | | | BER = 0 | -| | | | 4 bits | | | BER = 0 | -| UC-Plane O-DU CMP Scenario Mu-Law Compression (MLW) | DL | Mu-Law | 9 bits | Same as above | Same as above | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| | | | 9 bits | | | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| | UL | Mu-Law | 9 bits | | | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| | | | 9 bits | | | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| UC-Plane O-RU CMP Scenario Modulation Compressed Format | DL | Modulation Compression | 4-bits | Same as above | Same as above | BER = 0 | -| UC-Plane O-RU CMP Scenario Block Floating Point Compression + Selective RE (BRE) | DL | Block Floating point + Selective RE | 9 bits | Same as above | Same as above | BER = 0 | -| | | | 14 bits | Same as above | Same as above | BER = 0 | -| | | | 9 bits | Same as above | Same as above | BER = 0 | -| | | | 14 bits | Same as above | Same as above | BER = 0 | -| | UL | Block Floating point + Selective RE | 9 bits | Same as above | Same as above | BER = 0 | -| | | | 14 bits | Same as above | Same as above | BER = 0 | -| | | | 9 bits | Same as above | Same as above | BER = 0 | -| | | | 14 bits | Same as above | Same as above | BER = 0 | -| UC-Plane O-RU CMP Scenario Modulation Compressed | DL | Modulation Compression + Selective RE | 4-bits | Same as above | Same as above | BER = 0 | - -| | | | | | | | -|-----------------------|--|--|--|--|--|--| -| + Selective RE Format | | | | | | | -|-----------------------|--|--|--|--|--|--| - -### 3.2.3.3.2 UC-Plane O-RU Scenario Class Compression Static Format (SF) Fixed-Point (FP) - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format. - -The purpose of this test is to: - -- Validate correct encoding of IQ data under the following conditions. - - RU Static compression configurations - - Fixed point IQ data format - - Selection of 2 supported bit width: 9 bits, 14 bits - - Uplink / downlink -- Validate that in the U-Plane PRB header, the udCompHeader, “reserved” and udCompParam fields are not present - -#### B. Test Entrance Criteria - -The test uses the setup and methodology described in clause 3.2.1.1. - -#### C. Test Methodology - -##### a. Initial Conditions - -- The O-RU is started -- Fronthaul Ethernet interface configured for communication between TER and the DUT. -- O-RU synchronized with TER using S-Plane -- Communication established between TER and the DUT such that it is possible to exchange U-Plane and C-Plane messages -- signal analyser connected to DUT’s antenna port and setup according to DUT RF output configuration -- signal source connected to DUT’s antenna port and setup according to DUT RF input configuration - -##### b. Procedure - -For each supported bit width (9 bits, 14 bits), the following tests need to be performed: - -###### 1. Downlink test - -- Via the M-Plane or another suitable mechanism, put the O-RU into a static configuration with the downlink configured as follows: no compression, (16 bits) -- Arm signal analyser to capture the next Frame -- Send the “uncompressed” **NR-FR1-CMP-TST-FRAME-ST-DL-UNC-16B** test stimulus file to the DUT -- With the signal analyser, perform the 3 power measurements - - CMP-Uncompressed-Measured-Power-PDSCH0 in dBm - - CMP-Uncompressed-Measured-Power-PDSCH1 in dBm - - CMP-Uncompressed-Measured-Power-PDSCH2 in dBm -- With the signal analyser, perform the 3 EVM measurements - - CMP-Uncompressed-Measured-EVM-PDSCH0 in % - -- CMP-Uncompressed-Measured-EVM-PDSCH1 in % -- CMP-Uncompressed-Measured-EVM-PDSCH2 in % -- With the signal analyser, check Data integrity measurements - - CMP-Uncompressed-BER-PDSCH0 - - CMP-Uncompressed-BER-PDSCH1 - - CMP-Uncompressed-BER-PDSCH2 -- Via the M-Plane or another suitable mechanism, put the O-RU into a static configuration with the downlink configured as follows: Fixed point, 9-bit (then 14 bits) -- Send the “Compressed” **NR-FR1-CMP-TST-FRAME-ST-DL-FPF-9B (then 14B)** test stimulus file to the DUT -- With the signal analyser, perform the 3 power measurements - - CMP-Compressed-Measured-Power-PDSCH0 in dBm - - CMP-Compressed-Measured-Power-PDSCH1 in dBm - - CMP-Compressed-Measured-Power-PDSCH2 in dBm -- With the signal analyser, perform the 3 EVM measurements - - CMP-Compressed-Measured-EVM-PDSCH0 in % - - CMP-Compressed-Measured-EVM-PDSCH1 in % - - CMP-Compressed-Measured-EVM-PDSCH2 in % -- With the signal analyser, check Data integrity measurements - - CMP-Compressed-BER-PDSCH0 - - CMP-Compressed-BER-PDSCH1 - - CMP-Compressed-BER-PDSCH2 -- Verify the following conditions - - Power measurements within acceptable range - - Difference between CMP-Uncompressed-Measured-Power-PDSCH0 and CMP-Compressed-Measured-Power-PDSCH0 is within ACC\_PWR\_PDSCH0 range - - Difference between CMP-Uncompressed-Measured-Power-PDSCH1 and CMP-Compressed-Measured-Power-PDSCH1 is within ACC\_PWR\_PDSCH1 range - - Difference between CMP-Uncompressed-Measured-Power-PDSCH2 and CMP-Compressed-Measured-Power-PDSCH2 is within ACC\_PWR\_PDSCH2 range - - - - EVM measurements within acceptable range - - Difference between CMP-Uncompressed-Measured-EVM-PDSCH0 and CMP-Compressed-Measured-EVM-PDSCH0 is less than ACC\_EVM\_PDSCH0 - - Difference between CMP-Uncompressed-Measured-EVM-PDSCH1 and CMP-Compressed-Measured-EVM-PDSCH1 is less than ACC\_EVM\_PDSCH1 - - Difference between CMP-Uncompressed-Measured-EVM-PDSCH2 and CMP-Compressed-Measured-EVM-PDSCH2 is less than ACC\_EVM\_PDSCH2 - - BER Measurements show no errors - - CMP-Uncompressed-BER-PDSCH0 =0 - - CMP-Uncompressed-BER-PDSCH1 =0 - - CMP-Uncompressed-BER-PDSCH2 =0 - - CMP-Compressed-BER-PDSCH0 =0 - - CMP-Compressed-BER-PDSCH1 =0 - - CMP-Compressed-BER-PDSCH2 =0 - -## 2. Uplink test - -- Via the M-Plane or another suitable mechanism, put the O-RU into a static configuration with the uplink configured as follows: no compression, 16-bit - -- Arm signal source to generate the Frame NR-FR1-CMP-TST-FRAME-UL -- Arm CUSM-E to send the “uncompressed” NR-FR1-CMP-TST-FRAME-ST-UL-UNC-16B test stimulus file to the DUT -- ARM CUSM-E to capture the Uplink U-Plane Data from the DUT -- Launch the test -- Extract IQ information from Capture U-Plane trace -- Using the signal analyser software, perform the 3 power measurements - - CMP-Uncompressed-Measured-Power-PDSCH0 in dBm - - CMP-Uncompressed-Measured-Power-PDSCH1 in dBm - - CMP-Uncompressed-Measured-Power-PDSCH2 in dBm -- Using the signal analyser software, perform the 3 EVM measurements - - CMP-Uncompressed-Measured-EVM-PDSCH0 in % - - CMP-Uncompressed-Measured-EVM-PDSCH1 in % - - CMP-Uncompressed-Measured-EVM-PDSCH2 in % -- Using the signal analyser software, check Data integrity measurements - - CMP-Uncompressed-BER-PDSCH0 - - CMP-Uncompressed-BER-PDSCH1 - - CMP-Uncompressed-BER-PDSCH2 -- Via the M-Plane or another suitable mechanism, put the O-RU into a static configuration with the uplink configured as follows: Fixed point, 9-bit (then 14 bits) -- Arm signal source to generate the Frame NR-FR1-CMP-TST-FRAME-UL -- Arm CUSM-E to send the “Compressed” NR-FR1-CMP-TST-FRAME-ST-UL-FPF-9B test stimulus file to the DUT -- Arm CUSM-E to capture the Uplink U-Plane Data from the DUT -- Launch the test -- Extract IQ information from Capture U-Plane trace -- Using the signal analyser software, perform the 3 power measurements - - CMP-Compressed-Measured-Power-PDSCH0 in dBm - - CMP-Compressed-Measured-Power-PDSCH1 in dBm - - CMP-Compressed-Measured-Power-PDSCH2 in dBm -- Using the signal analyser software, perform the 3 EVM measurements - - CMP-Compressed-Measured-EVM-PDSCH0 in % - - CMP-Compressed-Measured-EVM-PDSCH1 in % - - CMP-Compressed-Measured-EVM-PDSCH2 in % -- Using the signal analyser software, check Data integrity measurements - - CMP-Compressed-BER-PDSCH0 - - CMP-Compressed-BER-PDSCH1 - - CMP-Compressed-BER-PDSCH2 -- Validate correct U-Plane PRB header structure - - U-Plane udComphdr (per clause 8.3.3.13 of [2]) - - U-Plane udCompParam (per clause 8.3.3.15 of [2]) -- Validate that the power measurements within acceptable range - -- Difference between CMP-Uncompressed-Measured-Power-PDSCH0 and CMP-Compressed-Measured-Power-PDSCH0 is within ACC\_PWR\_PDSCH0 range -- Difference between CMP-Uncompressed-Measured-Power-PDSCH1 and CMP-Compressed-Measured-Power-PDSCH1 is within ACC\_PWR\_PDSCH1 range -- -- Difference between CMP-Uncompressed-Measured-Power-PDSCH2 and CMP-Compressed-Measured-Power-PDSCH2 is within ACC\_PWR\_PDSCH2 range -- EVM measurements within acceptable range - - Difference between CMP-Uncompressed-Measured-EVM-PDSCH0 and CMP-Compressed-Measured-EVM-PDSCH0 is less than ACC\_EVM\_PDSCH0 - - Difference between CMP-Uncompressed-Measured-EVM-PDSCH1 and CMP-Compressed-Measured-EVM-PDSCH1 is less than ACC\_EVM\_PDSCH1 - - Difference between CMP-Uncompressed-Measured-EVM-PDSCH2 and CMP-Compressed-Measured-EVM-PDSCH2 is less than ACC\_EVM\_PDSCH2 -- Validate that the BER Measurements show no errors - - CMP-Uncompressed-BER-PDSCH0 = 0 - - CMP-Uncompressed-BER-PDSCH1 = 0 - - CMP-Uncompressed-BER-PDSCH2 = 0 - - CMP-Compressed-BER-PDSCH0 = 0 - - CMP-Compressed-BER-PDSCH1 = 0 - - CMP-Compressed-BER-PDSCH2 = 0 - -#### D. Test Requirement (expected result) - -1. All validation steps above are within expected ranges or correctly match the expected outcome. - -### 3.2.3.3.3 UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Floating Point (BFP) - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format. - -This static format test scenario for Block Floating Point Format will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -#### B. Test Entrance Criteria - -Same as in clause 3.2.3.3.2 for Block floating point formats. - -#### C. Test Methodology - -Same as in clause 3.2.3.3.2 with Static Block Floating Point test patterns - -- NR-FR1-CMP-TST-FRAME-ST-DL-BFP-9B -- NR-FR1-CMP-TST-FRAME-ST-DL-BFP-14B -- NR-FR1-CMP-TST-FRAME-ST-UL-BFP-9B -- NR-FR1-CMP-TST-FRAME-ST-UL-BFP-14B - -#### D. Test Requirement (expected result) - -1. Same as in clause 3.2.3.3.2. - -### 3.2.3.3.4 UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Scaling - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format. - -This static format test scenario for Block Scaling Format will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -#### B. Test Entrance Criteria - -Same as in clause 3.2.3.3.2 for Block Scaling point formats. - -#### C. Test Methodology - -Same as in clause 3.2.3.3.2 with Static Block Scaling test patterns - -- NR-FR1-CMP-TST-FRAME-ST-DL-BSC-9B -- NR-FR1-CMP-TST-FRAME-ST-DL-BSC-14B -- NR-FR1-CMP-TST-FRAME-ST-UL-BSC-9B -- NR-FR1-CMP-TST-FRAME-ST-UL-BSC-14B - -#### D. Test Requirement (expected result) - -Same as in clause 3.2.3.3.2. - -### 3.2.3.3.5 UC-Plane O-RU Scenario Class Compression Static Format (SF) Mu-Law (MLW) - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format. - -This static format test scenario for Mu-Law Format will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -#### B. Test Entrance Criteria - -Same as in clause 3.2.3.3.2 for Mu-Law formats. - -#### C. Test Methodology - -Same as in clause 3.2.3.3.2 with Static Mu-Law test patterns - -- NR-FR1-CMP-TST-FRAME-ST-DL-MLW-9B -- NR-FR1-CMP-TST-FRAME-ST-DL-MLW-14B -- NR-FR1-CMP-TST-FRAME-ST-UL-MLW-9B -- NR-FR1-CMP-TST-FRAME-ST-UL-MLW-14B - -#### D. Test Requirement (expected result) - -Same as in clause 3.2.3.3.2. - -### 3.2.3.3.6 UC-Plane O-RU Scenario Class Compression Static Format (SF) Modulation-Compressed Format - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format. - -This modulation compression format scenario is a static format scenario, based on 3.2.3.3.2 with some important differences - -- The purpose is to validate Radio Unit’s correct interpretation of the Modulation compression parameters used in the Section Extension Type = 4 and/or Section Extension Type 5 , based on the section extensions a radio supports. - -If the O-RU only supports section extension 4 on a given endpoint, then: - -- Section extension 4 shall be used for all symbols containing PDSCH REs and for symbols containing both PDSCH and DMRS REs. - -If the O-RU only supports section extension 5 on a given endpoint, then: - -- Section extension 5 shall be used for all symbols containing PDSCH REs and for symbols containing both PDSCH and DMRS REs. - -If the radio supports 4 and 5 on a given endpoint, then - -- Section extension 4 shall be used for symbols containing only PDSCH REs . -- Section extensions 5 shall be used for symbols containing DMRS + PDSCH REs. - -![Figure 3.2.3.3-4: Section Extension 4 and 5 signalling. A grid showing SubCarrier (0-12) vs Symbol (0-14) for DL-SCH0. A red box highlights 'Section extension 5' at symbol 2, subcarriers 0-12. A grey box highlights 'Section extension 4' for symbols 4-14, subcarriers 0-12.](4bfb6bb23e005e280ded1e8e6c85bc46_img.jpg) - -The figure shows a resource grid for DL-SCH0. The vertical axis is labeled 'SubCarrier' and ranges from 0 to 12. The horizontal axis is labeled 'Symbol' and ranges from 0 to 14. A red rectangle highlights a vertical column at symbol 2, spanning subcarriers 0 to 12, and is labeled 'Section extension 5' in red text below. A grey rectangle highlights the area from symbol 4 to 14, spanning subcarriers 0 to 12, and is labeled 'Section extension 4' in grey text below. The grid cells are mostly green, with some pink cells in the highlighted red box. - -Figure 3.2.3.3-4: Section Extension 4 and 5 signalling. A grid showing SubCarrier (0-12) vs Symbol (0-14) for DL-SCH0. A red box highlights 'Section extension 5' at symbol 2, subcarriers 0-12. A grey box highlights 'Section extension 4' for symbols 4-14, subcarriers 0-12. - -Figure 3.2.3.3-4 Section Extension 4 and 5 signalling - -- When high level modulation is supported by the Device Under Test (DUT), Section Extension Type 5 messages will be tested on the current compression test frame , that includes Mixed MCS test cases where high MCS user data REs and low MCS DMRS signalling data REs are in the same PRB. -- The test will only verify DL correct encoding of IQ information, as the Modulation Compression model is not applicable for uplink -- As the Modulation Compression model does not require IQ bit width to be setup, there is no need to run multiple compression tests for various IQ bit width. - -| Stimulus File Name | Description | -|------------------------------------|-----------------------------------------| -| NR-FR1-CMP-TST-FRAME-ST-DL-UNC-16B | Static Downlink Uncompressed (CU-plane) | -| NR-FR1-CMP-TST-FRAME-ST-DL-MC | Static Downlink Modulation Compression | - -**B. Test Entrance Criteria** - -Same as in clause 3.2.3.3.2. - -**C. Test Methodology** - -Same as in clause 3.2.3.3.2 with Static Modulation Compression test patterns - -- NR-FR1-TDD-CMP-TST-ST-DL-MC - -Note that this test is only applicable to the downlink and therefore should only follow the downlink steps of the referenced test case above. Via the M-Plane or another suitable mechanism, put the O-RU into a static configuration with the downlink configured as follows: Modulation Compression. - -**D. Test Requirement (expected result)** - -All validation steps for the downlink referenced in clause 3.2.3.3.2 are within expected ranges or correctly match the expected outcome. - -**3.2.3.3.7 UC-Plane O-RU Scenario Class Compression Non-Static (NS) Fixed-Point (FPF)****A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format. - -This Fixed-Point Format scenario is a non-static format scenario that will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -**B. Test Entrance Criteria** - -Same as in clause 3.2.3.3.2. - -**C. Test Methodology****a. Initial Conditions** - -- Same as in clause 3.2.3.3.2 Non-Static Fixed-Point test patterns -- Via the M-Plane or another suitable mechanism, disable the O-RU Static IQ and compression format - -**b. Procedure** - -For each supported bit width (9 bits, 14 bits), the following tests need to be performed: - -**1. Downlink test** - -- Arm signal analyser to capture the next Frame -- Send the uncompressed" NR-FR1-CMP-TST-FRAME-NS-DL-UNC-16B test stimulus file to the DUT -- With the signal analyser, perform the 3 power measurements - - CMP-Uncompressed-Measured-Power-PDSCH0 in dBm - - CMP-Uncompressed-Measured-Power-PDSCH1 in dBm - - CMP-Uncompressed-Measured-Power-PDSCH2 in dBm -- With the signal analyser, perform the 3 EVM measurements - - CMP-Uncompressed-Measured-EVM-PDSCH0 in % - - CMP-Uncompressed-Measured-EVM-PDSCH1 in % - - CMP-Uncompressed-Measured-EVM-PDSCH2 in % - -- With the signal analyser, check Data integrity measurements - - CMP-Uncompressed-BER-PDSCH0 - - CMP-Uncompressed-BER-PDSCH1 - - CMP-Uncompressed-BER-PDSCH2 -- Send the “Compressed” NR-FR1-CMP-TST-FRAME-NS-DL-FPF-9B (then 14B) test stimulus file to the DUT -- With the signal analyser, perform the 3 power measurements - - CMP-Compressed-Measured-Power-PDSCH0 in dBm - - CMP-Compressed-Measured-Power-PDSCH1 in dBm - - CMP-Compressed-Measured-Power-PDSCH2 in dBm -- With the signal analyser, perform the 3 EVM measurements - - CMP-Compressed-Measured-EVM-PDSCH0 in % - - CMP-Compressed-Measured-EVM-PDSCH1 in % - - CMP-Compressed-Measured-EVM-PDSCH2 in % -- With the signal analyser, check Data integrity measurements - - CMP-Compressed-BER-PDSCH0 - - CMP-Compressed-BER-PDSCH1 - - CMP-Compressed-BER-PDSCH2 -- Validate that the power measurements within acceptable range - - Difference between CMP-Uncompressed-Measured-Power-PDSCH0 and CMP-Compressed-Measured-Power-PDSCH0 is within ACC\_PWR\_PDSCH0 range - - Difference between CMP-Uncompressed-Measured-Power-PDSCH1 and CMP-Compressed-Measured-Power-PDSCH1 is within ACC\_PWR\_PDSCH1 range - - Difference between CMP-Uncompressed-Measured-Power-PDSCH2 and CMP-Compressed-Measured-Power-PDSCH2 is within ACC\_PWR\_PDSCH2 range -- Validate that the EVM measurements within acceptable range - - Difference between CMP-Uncompressed-Measured-EVM-PDSCH0 and CMP-Compressed-Measured-EVM-PDSCH0 is within ACC\_EVM\_PDSCH0 range - - Difference between CMP-Uncompressed-Measured-EVM-PDSCH1 and CMP-Compressed-Measured-EVM-PDSCH1 is within ACC\_EVM\_PDSCH1 range - - Difference between CMP-Uncompressed-Measured-EVM-PDSCH2 and CMP-Compressed-Measured-EVM-PDSCH2 is within ACC\_EVM\_PDSCH2 range -- Validate that the BER Measurements show no errors - - CMP-Uncompressed-BER-PDSCH0 =0 - - CMP-Uncompressed-BER-PDSCH1 =0 - - CMP-Uncompressed-BER-PDSCH2 =0 - - CMP-Compressed-BER-PDSCH0 =0 - - CMP-Compressed-BER-PDSCH1 =0 - - CMP-Compressed-BER-PDSCH2 =0 - -## 2. Uplink test - -- Arm signal source to generate the Frame NR-FR1-CMP-TST-FRAME-UL - -- Arm CUSM-E to send the “uncompressed” NR-FR1-CMP-TST-FRAME-NS-UL-UNC-16B test stimulus file to the DUT -- Arm CUSM-E to capture the Uplink U-Plane Data from the DUT -- Launch the test -- Extract IQ information from Captured U-Plane trace -- Using the signal analyser software, perform the 3 power measurements - - CMP-Uncompressed-Measured-Power-PDSCH0 in dBm - - CMP-Uncompressed-Measured-Power-PDSCH1 in dBm - - CMP-Uncompressed-Measured-Power-PDSCH2 in dBm -- Using the signal analyser software, perform the 3 EVM measurements - - CMP-Uncompressed-Measured-EVM-PDSCH0 in % - - CMP-Uncompressed-Measured-EVM-PDSCH1 in % - - CMP-Uncompressed-Measured-EVM-PDSCH2 in % -- Using the signal analyser software, check Data integrity measurements - - CMP-Uncompressed-BER-PDSCH0 - - CMP-Uncompressed-BER-PDSCH1 - - CMP-Uncompressed-BER-PDSCH2 -- Via the M-Plane or another suitable mechanism, put the O-RU into a Non-Static configuration -- Arm signal source to generate the Frame NR-FR1-CMP-TST-FRAME-UL -- Arm CUSM-E to send the “Compressed” NR-FR1-CMP-TST-FRAME-NS-UL-CMP-9B (then 14B) test stimulus file to the DUT -- ARM CUSM-E to capture the Uplink U-Plane Data from the DUT -- Launch the test -- Extract IQ information from Captured U-Plane trace -- Using the signal analyser software, perform the 3 power measurements - - CMP-Compressed-Measured-Power-PDSCH0 in dBm - - CMP-Compressed-Measured-Power-PDSCH1 in dBm - - CMP-Compressed-Measured-Power-PDSCH2 in dBm -- Using the signal analyser software, perform the 3 EVM measurements - - CMP-Compressed-Measured-EVM-PDSCH0 in % - - CMP-Compressed-Measured-EVM-PDSCH1 in % - - CMP-Compressed-Measured-EVM-PDSCH2 in % -- Using the signal analyser software, check Data integrity measurements - - CMP-Compressed-BER-PDSCH0 - - CMP-Compressed-BER-PDSCH1 - - CMP-Compressed-BER-PDSCH2 -- Validate correct U-Plane PRB header structure - - U-Plane udComphdr (per clause 8.3.3.13 of [2]) - - U-Plane udCompParam (per clause 8.3.3.15 of [2]) -- Validate that the power measurements within acceptable range - - Difference between CMP-Uncompressed-Measured-Power-PDSCH0 and CMP-Compressed-Measured-Power-PDSCH0 is within ACC\_PWR\_PDSCH0 range. - - Difference between CMP-Uncompressed-Measured-Power-PDSCH1 and CMP-Compressed-Measured-Power-PDSCH1 is within ACC\_PWR\_PDSCH1 range. - -- Difference between CMP-Uncompressed-Measured-Power-PDSCH2 and CMP-Compressed-Measured-Power-PDSCH2 is within ACC\_PWR\_PDSCH2 range. -- Validate that the EVM measurements within acceptable range - - Difference between CMP-Uncompressed-Measured-EVM-PDSCH0 and CMP-Compressed-Measured-EVM-PDSCH0 is less than ACC\_EVM\_PDSCH0 value. - - Difference between CMP-Uncompressed-Measured-EVM-PDSCH1 and CMP-Compressed-Measured-EVM-PDSCH1 is less than ACC\_EVM\_PDSCH1 value. - - Difference between CMP-Uncompressed-Measured-EVM-PDSCH2 and CMP-Compressed-Measured-EVM-PDSCH2 is less than ACC\_EVM\_PDSCH2 value. -- Validate that the BER Measurements show no errors - - CMP-Uncompressed-BER-PDSCH0 = 0 - - CMP-Uncompressed-BER-PDSCH1 = 0 - - CMP-Uncompressed-BER-PDSCH2 = 0 - - CMP-Compressed-BER-PDSCH0 = 0 - - CMP-Compressed-BER-PDSCH1 = 0 - - CMP-Compressed-BER-PDSCH2 = 0 - -#### D. Test Requirement (expected result) - -1. All validation steps above are within expected ranges or correctly match the expected outcome. - -### 3.2.3.3.8 UC-Plane O-RU Scenario Class Compression Non-Static (NS) Block Floating Point - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format. This Block Floating-Point Format scenario is a non-static format scenario that will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -#### B. Test Entrance Criteria - -Same as in clause 3.2.3.3.7 for Block floating point formats. - -#### C. Test Methodology - -Same as in clause 3.2.3.3.7 with Static Block Floating Point test patterns - -- NR-FR1-CMP-TST-FRAME-NS-DL-BFP-9B -- NR-FR1-CMP-TST-FRAME-NS-DL-BFP-14B -- NR-FR1-CMP-TST-FRAME-NS-UL-BFP-9B -- NR-FR1-CMP-TST-FRAME-NS-UL-BFP-14B - -#### D. Test Requirement (expected result) - -Same as in clause 3.2.3.3.7. - -### 3.2.3.3.9 UC-Plane O-RU Scenario Class Compression Non-Static (NS) Block Scaling (BSC) - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format. - -This Block Scaling Format scenario is a dynamic-format scenario that will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -#### **B. Test Entrance Criteria** - -Same as in clause 3.2.3.3.2 for Block Scaling formats. - -#### **C. Test Methodology** - -Same as in clause 3.2.3.3.2 with Static Block Scaling test patterns - -- NR-FR1-CMP-TST-FRAME-NS-DL-BSC-9B -- NR-FR1-CMP-TST-FRAME-NS-DL-BSC-14B -- NR-FR1-CMP-TST-FRAME-NS-UL-BSC-9B -- NR-FR1-CMP-TST-FRAME-NS-UL-BSC-14B - -#### **D. Test Requirement (expected result)** - -1. Same as in clause 3.2.3.3.7. - -### **3.2.3.3.10 UC-Plane O-RU Scenario Class Compression Non-Static (NS) Mu-Law (MLW)** - -#### **A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format. - -This Mu-Law Format scenario is a dynamic-format scenario that will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -#### **B. Test Entrance Criteria** - -Same as in clause 3.2.3.3.2 for Mu-Law formats. - -#### **C. Test Methodology** - -Same as in clause 3.2.3.3.7 with Mu-Law format test patterns - -- NR-FR1-CMP-TST-FRAME-NS-DL-MLW-9B -- NR-FR1-CMP-TST-FRAME-NS-DL-MLW-14B -- NR-FR1-CMP-TST-FRAME-NS-UL-MLW-9B -- NR-FR1-CMP-TST-FRAME-NS-UL-MLW-14B - -#### **D. Test Requirement (expected result)** - -- Same as in clause 3.2.3.3.7. - -### **3.2.3.3.11 UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) Modulation-Compressed Format** - -#### **A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format. - -This modulation compression format scenario is a non-static format scenario, based on 3.2.3.3.2 with some important differences - -- The purpose is to validate Radio Unit’s correct interpretation of the Modulation compression parameters used in the Section Extension Type = 4 and/or Section Extension Type 5 , based on the section extensions a radio supports. - -If the O-RU only supports section extension 4 on a given endpoint, then: - -- Section extension 4 shall be used for all symbols containing PDSCH REs and for symbols containing both PDSCH and DMRS REs. - -If the O-RU only supports section extension 5 on a given endpoint, then: - -- Section extension 5 shall be used for all symbols containing PDSCH REs and for symbols containing both PDSCH and DMRS REs. - -If the radio supports 4 and 5 on a given endpoint, then - -- Section extension 4 shall be used for symbols containing only PDSCH REs . -- Section extensions 5 shall be used for symbols containing DMRS + PDSCH REs. - -![Diagram of DL-SCH0 resource grid showing Section extension 5 (symbols 0-2) and Section extension 4 (symbols 3-14) across 12 subcarriers. A red box highlights the first three symbols (0, 1, 2) as 'Section extension 5', and a grey box highlights the remaining symbols (3-14) as 'Section extension 4'. The grid shows various resource elements (REs) in green and pink.](6da084e1172d878eec926417071b6361_img.jpg) - -Diagram of DL-SCH0 resource grid showing Section extension 5 (symbols 0-2) and Section extension 4 (symbols 3-14) across 12 subcarriers. A red box highlights the first three symbols (0, 1, 2) as 'Section extension 5', and a grey box highlights the remaining symbols (3-14) as 'Section extension 4'. The grid shows various resource elements (REs) in green and pink. - -Figure 3.2.3.3-5 Section Extension 4 and 5 signalling - -- When high level modulation is supported by the Device Under Test (DUT), Section Extension Type 5 messages will be tested on the current compression test frame , that includes Mixed MCS test cases where high MCS user data REs and low MCS DMRS signalling data REs are in the same PRB. -- The test will only verify DL correct encoding of IQ information, as the Modulation Compression model is not applicable for uplink -- As the Modulation Compression model does not require IQ bit width to be setup, there is no need to run multiple compression tests for various IQ bit width. - -| Stimulus File Name | Description | -|------------------------------------|---------------------------------------------| -| NR-FR1-CMP-TST-FRAME-NS-DL-UNC-16B | Non-Static Downlink Uncompressed (CU-plane) | -| NR-FR1-CMP-TST-FRAME-NS-DL-MC | Non-Static Downlink Modulation Compression | - -**B. Test Entrance Criteria** - -Same as in clause 3.2.3.3.2. - -**C. Test Methodology** - -Same as in clause 3.2.3.3.7 with Static Modulation Compression test patterns - -- NR-FR1-TDD-CMP-TST-NS-DL-MC - -Via the M-Plane or another suitable mechanism, put the O-RU into a static configuration with the downlink configured as follow: Modulation Compression - -**D. Test Requirement (expected result)** - -All validation steps above are within expected ranges or correctly match the expected outcome. - -**3.2.3.3.12 UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Floating Point + Selective RE Format** - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format. - -The Block Floating-Point+ Selective RE Format scenario is a static format scenario that will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -For this test scenario, the compression test methodology will be based on the description in clause 3.2.3.3.1. - -However, on top of the test frame requirements from clause 3.2.3.3.1, this test scenario also requires a test frame that MUST include PRBs with a combination of allocated and empty Resource Elements in the same symbol, to verify if the O-RU properly interprets the ReMask value in the udCompParam field (user data compression parameter). The measurements must be performed on the symbols that include a combination of empty and allocated resource elements. - -The recommended DL test frame is based on Type 2 DMRS with 2 DMRS CDM groups without data. The resource mapping model for the Resource Blocks is shown Figure 3.2.3.3-, where both symbols #2 and #11 include a combination of empty and allocated Resources. - -![Figure 3.2.3.3-6: RB Resource Mapping for DL-SCH1 (Modulation = QPSK). The figure is a grid showing resource elements (REs) across 13 symbols (x-axis) and 12 subcarriers (y-axis). Symbols 2 and 11 show a combination of allocated (red) and empty (grey) REs, while other symbols are mostly empty (green).](e96f8adc46a90584fa121570e6e726ca_img.jpg) - -| Symbol | Subcarriers | RE Status | -|--------|-------------|-------------------------------------------------------------------------------------------------------| -| 0 | 0-11 | Empty (Green) | -| 1 | 0-11 | Empty (Green) | -| 2 | 0-11 | Symbol 2: REs 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 are allocated (Red). REs 10, 11 are empty (Grey). | -| 3 | 0-11 | Empty (Green) | -| 4 | 0-11 | Empty (Green) | -| 5 | 0-11 | Empty (Green) | -| 6 | 0-11 | Empty (Green) | -| 7 | 0-11 | Empty (Green) | -| 8 | 0-11 | Empty (Green) | -| 9 | 0-11 | Empty (Green) | -| 10 | 0-11 | Empty (Green) | -| 11 | 0-11 | Symbol 11: REs 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 are allocated (Red). REs 10, 11 are empty (Grey). | -| 12 | 0-11 | Empty (Green) | - -Figure 3.2.3.3-6: RB Resource Mapping for DL-SCH1 (Modulation = QPSK). The figure is a grid showing resource elements (REs) across 13 symbols (x-axis) and 12 subcarriers (y-axis). Symbols 2 and 11 show a combination of allocated (red) and empty (grey) REs, while other symbols are mostly empty (green). - -**Figure 3.2.3.3-6 Frame Format Compression Test Selective RE** - -The uncompressed and compressed test frames are listed in Table 3.2.3-12: - -**Table 3.2.3-12 Stimulus Files for Static Compression Test.** - -| | Stimulus File Name | Description | -|-----------|---------------------------------------|-----------------------------------------------------------------------------------------------| -| B. | NR-FR1-CMP-TST-FRAME-ST-DL-UNC-RE-16B | Static Downlink Uncompressed (CU-plane) with both empty and allocated RE in the same symbol | -| | NR-FR1-CMP-TST-FRAME-ST-UL-UNC-RE-16B | Static Uplink Uncompressed (C-plane only) with both empty and allocated RE in the same symbol | -| | NR-FR1-CMP-TST-FRAME-ST-DL-BRE-9B | Static Downlink Block Floating Point + Selective RE 9 Bits (CU-plane) | -| | NR-FR1-CMP-TST-FRAME-ST-DL-BRE-14B | Static Downlink Block Floating Point + Selective RE 14 Bits (CU-plane) | -| | NR-FR1-CMP-TST-FRAME-ST-UL-BRE-9B | Static Uplink Block Floating Point 9 Bits + Selective RE (C-plane only) | -| | NR-FR1-CMP-TST-FRAME-ST-UL-BRE-14B | Static Uplink Block Floating Point 14 Bits + Selective RE (C-plane only) | - -**Test Entrance Criteria** - -Same as in clause 3.2.3.3.2 for static Block floating point + Selective RE formats. - -**C. Test Methodology** - -Same as in clause 3.2.3.3.2 with Static Block Floating Point + Selective RE test patterns. - -The uncompressed test frames used for this test are - -- NR-FR1-CMP-TST-FRAME-ST-DL-UNC-RE-16B -- NR-FR1-CMP-TST-FRAME-ST-UL-UNC-RE-16B - -The compressed test frames used for this test are - -- NR-FR1-CMP-TST-FRAME-ST-DL-BRE-9B -- NR-FR1-CMP-TST-FRAME-ST-DL-BRE-14B -- NR-FR1-CMP-TST-FRAME-ST-UL-BRE-9B -- NR-FR1-CMP-TST-FRAME-ST-UL-BRE-14B - -**D. Test Requirement (expected result)** - -Same as in clause 3.2.3.3.2. - -**3.2.3.3.13 UC-Plane O-RU Scenario Class Compression Static Format (SF) mod-compr + Selective RE Format** - -**A. Test Description and Applicability** - -This test is CONDITIONAL- MANDATORY and shall be performed if the O-RU supports this compression format. - -This modulation compression + Selective format scenario is a static format scenario, based on clause 3.2.3.3.2 with some important differences - -- The purpose is to validate Radio Unit’s correct interpretation of the Modulation compression parameters used in the Section Extension Type = 4 and Section Extension Type 5 - -- When high level modulation is supported by the Device Under Test (DUT), Section Extension Type 5 messages will be tested on the current compression test frame , that includes Mixed MCS test cases where high MCS user data REs and low MCS DMRS signalling data REs are in the same PRB. -- The test will only verify Downlink correct encoding of IQ information, as the Modulation Compression model is not applicable for uplink -- As the Modulation Compression model does not require IQ bit width to be setup, there is no need to run multiple compression tests for various IQ bit widths. - -On top of the test frame requirements described above , this test scenario requires a test frame that MUST include PRBs with a combination of allocated and empty Resource Elements in the same symbol, to verify if the O-RU properly interprets the ReMask value in the udCompParam field (user data compression parameter). The measurements must be performed on the symbols that include a combination of empty and allocated resource elements. - -The recommended DL test frame is based on Type 2 DMRS with 2 DMRS CDM groups without data. The resource mapping model for the Resource Blocks is shown on the diagram below, where both symbols #2 and #11 include a combination of empty and allocated Resources. - -![RB Resource Mapping for DL-SCH1 (Modulation = QPSK) diagram showing subcarriers 0-12 on the y-axis and symbols 0-13 on the x-axis. Symbols 2 and 11 show a mix of red (allocated) and grey (empty) resource elements across different subcarriers.](39d6fbe28fd2f6af73157212aaf2128b_img.jpg) - -RB Resource Mapping for DL-SCH1 (Modulation = QPSK) diagram showing subcarriers 0-12 on the y-axis and symbols 0-13 on the x-axis. Symbols 2 and 11 show a mix of red (allocated) and grey (empty) resource elements across different subcarriers. - -Figure 3.2.3.3-7 Test Frame Modulation Compression Selective RE - -The uncompressed and compressed test frames are listed in the table below - -Table 3.2.3-13 Test Frame Descriptions Modulation Compression Selective RE. - -| Stimulus File Name | Description | -|---------------------------------------|---------------------------------------------------------------------------------------------| -| NR-FR1-CMP-TST-FRAME-ST-DL-UNC-RE-16B | Static Downlink Uncompressed (CU-plane) with both empty and allocated RE in the same symbol | -| NR-FR1-CMP-TST-FRAME-ST-DL-MRE | Static Downlink Modulation Compression + Selective RE | - -**B. Test Entrance Criteria** - -Same as in clause 3.2.3.3.2. - -**C. Test Methodology** - -Same as in clause 3.2.3.3.2 with Static Modulation Compression test patterns - -The uncompressed test frames used for this test are - -- NR-FR1-CMP-TST-FRAME-ST-DL-UNC-RE-16B - -The compressed test frames used for this test are - -- NR-FR1-CMP-TST-FRAME-ST-DL-MRE - -Via the M-Plane or another suitable mechanism, put the O-RU into a static configuration with the downlink configured as follow: Modulation Compression + Selective RE - -**D. Test Requirement (expected result)** - -Same as in clause 3.2.3.3.2. - -**3.2.3.3.14 UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) Block Floating Point + Selective RE Format** - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format - -This Block Floating-Point+ Selective RE Format scenario is a non-static format scenario that will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -For this test scenario, the compression test methodology will be based on the description in clause 3.2.3.3.1. - -However, on top of the test frame requirements from clause 3.2.3.3.1, this test scenario also requires a test frame that MUST include PRBs with a combination of allocated and empty Resource Elements in the same symbol, to verify if the O-RU properly interprets the sReMask value in the udCompParam field (user data compression parameter). The measurements must be performed on the symbols that include a combination of empty and allocated resource elements. - -The recommended DL test frame is based on Type 2 DMRS with 2 DMRS CDM groups without data. The resource mapping model for the Resource Blocks is shown on the diagram below, where both symbols #2 and #11 include a combination of empty and allocated Resources. - -![RB Resource Mapping for DL-SCH1 (Modulation = QPSK) diagram showing subcarriers 0-12 on the y-axis and symbols 0-13 on the x-axis. Symbols 2 and 11 show a combination of red (allocated) and grey (empty) resource elements across different subcarriers.](62062de3c7147e8ee3829c3504ed156d_img.jpg) - -| Symbol | Subcarriers | Resource Element Status | -|--------|------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| -| 2 | 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12 | Subcarriers 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12: Red (Allocated) for subcarriers 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12 | -| 11 | 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12 | Subcarriers 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12: Red (Allocated) for subcarriers 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12 | - -RB Resource Mapping for DL-SCH1 (Modulation = QPSK) diagram showing subcarriers 0-12 on the y-axis and symbols 0-13 on the x-axis. Symbols 2 and 11 show a combination of red (allocated) and grey (empty) resource elements across different subcarriers. - -**Figure 3.2.3.3-8 Frame Format Compression NS BFP Selective RE** - -The uncompressed and compressed test frames are listed in Table 3.2.3-14. - -**Table 3.2.3-14 Stimulus Files for NS BFP Selective RE Compression Test.** - -| Stimulus File Name | Description | -|---------------------------------------|---------------------------------------------------------------------------------------------------| -| NR-FR1-CMP-TST-FRAME-NS-DL-UNC-RE-16B | Non-Static Downlink Uncompressed (CU-plane) with both empty and allocated RE in the same symbol | -| NR-FR1-CMP-TST-FRAME-NS-UL-UNC-RE-16B | Non-Static Uplink Uncompressed (C-plane only) with both empty and allocated RE in the same symbol | -| NR-FR1-CMP-TST-FRAME-NS-DL-BRE-9B | Non-Static Downlink Block Floating Point + Selective RE 9 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-NS-DL-BRE-14B | Non-Static Downlink Block Floating Point + Selective 14 Bits (CU-plane) | -| NR-FR1-CMP-TST-FRAME-NS-UL-BRE-9B | Non-Static Uplink Block Floating Point 9 Bits + Selective RE (C-plane only) | -| NR-FR1-CMP-TST-FRAME-NS-UL-BRE-14B | Non-Static Uplink Block Floating Point 14 Bits + Selective RE (C-plane only) | - -#### B. Test Entrance Criteria - -Same as in clause 3.2.3.3.2 for Non-Static Block floating point + Selective RE formats. - -#### C. Test Methodology - -Same as in clause 3.2.3.3.7 with Non-Static Block Floating Point + Selective RE test patterns - -The uncompressed test frames used for this test are - -- NR-FR1-CMP-TST-FRAME-NS-DL-UNC-RE-16B -- NR-FR1-CMP-TST-FRAME-NS-UL-UNC-RE-16B - -The compressed test frames used for this test are - -- NR-FR1-CMP-TST-FRAME-NS-DL-BRE-9B -- NR-FR1-CMP-TST-FRAME-NS-DL-BRE-14B -- NR-FR1-CMP-TST-FRAME-NS-UL-BRE-9B -- NR-FR1-CMP-TST-FRAME-NS-UL-BRE-14B - -#### D. Test Requirement (expected result) - -Same as in clause 3.2.3.3.7. - -### 3.2.3.3.15 UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) mod-compr + Selective RE Format - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format - -This Modulation Compression + Selective RE Format scenario is a non-static format scenario that will verify DL correct encoding of IQ information. - -This is the same as 3.2.3.3.13 with Non-Static test frames. When high level modulation is supported by the Device Under Test (DUT), Section Extension Type 5 messages will be tested on the current compression test frame , that includes Mixed MCS test cases where high MCS user data REs and low MCS DMRS signalling data REs are in the same PRB. - -The uncompressed and compressed test frames are listed in Table 3.2.3-15. - -**Table 3.2.3-15 Stimulus Files for NS Mod Comp Selective RE Compression Test.** - -| Stimulus File Name | Description | -|---------------------------------------|-------------------------------------------------------------------------------------------------| -| NR-FR1-CMP-TST-FRAME-NS-DL-UNC-RE-16B | Non-Static Downlink Uncompressed (CU-plane) with both empty and allocated RE in the same symbol | -| NR-FR1-CMP-TST-FRAME-NS-DL-MRE | Non-Static Downlink Modulation Compression + Selective RE | - -**B. Test Entrance Criteria** - -Same as in clause 3.2.3.3.2 for non-static Modulation Compression + Selective RE formats. - -**C. Test Methodology** - -Same as in clause 3.2.3.3.7 with Non-Static Block Floating Point + Selective RE test patterns - -The uncompressed test frames used for this test are - -- NR-FR1-CMP-TST-FRAME-NS-DL-UNC-BRE-16B - -The compressed test frames used for this test are - -- NR-FR1-CMP-TST-FRAME-NS-DL-MRE - -**D. Test Requirement (expected result)** - -Same as in clause 3.2.3.3.7. - -**3.2.3.4 UC-Plane O-RU Scenario Class Delay Management (DLM)** - -This section describes conformance test cases for O-RU Delay Management. - -The test setup for these test cases is shown in clause 2.1. - -When performing the conformance test cases for scenario class Delay Management it does not matter which timing method is used. The different timing methods are described in clause 4.4.3, 4.4.4, 4.4.5 and 4.4.6 of [2] - -Delay Management downlink tests will test whether the O-RU can accurately transmit data when C and U plane messages are received at the extreme ends of their respective reception windows. Uplink tests will test whether the O-RU can accurately transmit received data to the CUSM-E when the CUSM-E transmits uplink C-Plane messages within the correct uplink reception window. It also tests whether the O-RU sends its U-Plane messages within the correct reception window. - -Figure 3.2.3.4-36 shows a simplified timing relation for the C- and U-Plane messages for downlink. - -The size of the control plane reception window on the O-RU will be: $(T2a\_max\_up + Tcp\_adv\_dl) - (T2a\_min\_up + Tcp\_adv\_dl) = C\text{-Plane reception window}$ . The start-point (before $t=0$ ) will be: $T2a\_max\_up + Tcp\_adv\_dl = \text{start of C-Plane transmission window}$ . - -The size of the reception window for the user plane will be: $T2a\_max\_up - T2a\_min\_up$ . The start-point (before $t=0$ ) will be $T2a\_max\_up$ . - -As an example, if the values are set such as $T2a\_max\_up = 264 \mu\text{s}$ , $Tcp\_adv\_dl = 63 \mu\text{s}$ and $T2a\_min\_up = 53 \mu\text{s}$ , then the C-Plane reception window would be $211 \mu\text{s}$ , the start of C-plane transmission window would be $327 \mu\text{s}$ , the U-plane reception window would $211 \mu\text{s}$ and the start of U-plane transmission window would be $264 \mu\text{s}$ . - -![Timing diagram for downlink showing C-plane and U-plane reception windows relative to symbols #12, #13, and #0. It includes labels for TER, O-RU, and various timing parameters like T2a_max_up_dl, T2a_min_up_dl, Tcp_adv_dl, and T2a_max_cp_dl.](f609bd3fda53d5be094991a96addbf84_img.jpg) - -The diagram illustrates the timing for downlink messages. On the left, three blocks represent the network elements: TER, O-RU, and TER. The O-RU is shown with two reception windows: a blue 'Reception window U-Plane DL' and a green 'Reception window C-Plane DL'. The U-plane window starts at $T2a\_max\_up\_dl$ and ends at $T2a\_min\_up\_dl$ . The C-plane window starts at $T2a\_max\_cp\_dl$ and ends at $T2a\_min\_cp\_dl$ . The time difference between the start of the C-plane window and the start of the U-plane window is labeled $Tcp\_adv\_dl$ . A vertical blue line marks $t=0$ . Below the timeline, symbols are indicated: 'symbol #12', 'symbol #13', and 'symbol #0'. Arrows from yellow boxes labeled 'C' and 'U' point to the respective reception windows. - -Timing diagram for downlink showing C-plane and U-plane reception windows relative to symbols #12, #13, and #0. It includes labels for TER, O-RU, and various timing parameters like T2a\_max\_up\_dl, T2a\_min\_up\_dl, Tcp\_adv\_dl, and T2a\_max\_cp\_dl. - -Figure 3.2.3.4-36 Simplified Timing for Downlink - -The Delay Management uplink test cases for the O-RU will test that if the C-Plane fronthaul messages are received with respective reception window then the corresponding U-Plane messages will be sent in the O-RU’s transmission window. - -Figure 3.2.3.4-37 shows a simplified timing relation for the C-Plane and U-Plane messages for uplink. - -Similar to the downlink case, the size of the control plane reception window is $T2a\_max\_cp\_ul - T2a\_min\_cp\_ul$ . The start-point of (before $t=0$ ) of the C-plane reception window is $T2a\_max\_cp\_ul$ . - -The size of the transmission window for the user plane will be: $Ta3\_max\_up - Ta3\_min\_up$ . The start-point (after $t=0$ ) will be $Ta3\_min\_up$ . - -If we follow the same example values as the ones set in the downlink case, the C-plane reception window would be $211 \mu\text{s}$ , the start-point of the C-plane reception window would be $274 \mu\text{s}$ , the U-plane transmission window would be $70 \mu\text{s}$ and the start-point of the U-plane transmission window would be $20 \mu\text{s}$ . - -![Simplified Timing for Uplink diagram showing signal flow between TER, O-RU, and User Equipment (UE) over time. A vertical blue line marks t=0. To the left, three boxes (TER, O-RU, TER) are connected vertically. A yellow box 'C' is shown twice, with an arrow from the top TER pointing to the lower 'C'. From the lower 'C', a green double-headed arrow labeled 'Reception window C-Plane UL' points to a vertical green line. From this line, two green double-headed arrows labeled 'T2a_min_cp_ul' and 'T2a_max_cp_ul' point to the t=0 line. Below the timeline, symbols #12, #13, and #0 are shown in a row. To the right of t=0, two yellow boxes 'U' are shown, with an arrow from the lower 'U' pointing to the upper 'U'. From the upper 'U', two red double-headed arrows labeled 'Ta3_min_up_dl' and 'Ta3_max_up_dl' point to the t=0 line. A red double-headed arrow labeled 'Transmission window U-Plane UL' is shown between the two 'U' boxes. The horizontal axis is labeled 't'.](1fa646088a731bde9ff4c9af87f93d3c_img.jpg) - -Simplified Timing for Uplink diagram showing signal flow between TER, O-RU, and User Equipment (UE) over time. A vertical blue line marks t=0. To the left, three boxes (TER, O-RU, TER) are connected vertically. A yellow box 'C' is shown twice, with an arrow from the top TER pointing to the lower 'C'. From the lower 'C', a green double-headed arrow labeled 'Reception window C-Plane UL' points to a vertical green line. From this line, two green double-headed arrows labeled 'T2a\_min\_cp\_ul' and 'T2a\_max\_cp\_ul' point to the t=0 line. Below the timeline, symbols #12, #13, and #0 are shown in a row. To the right of t=0, two yellow boxes 'U' are shown, with an arrow from the lower 'U' pointing to the upper 'U'. From the upper 'U', two red double-headed arrows labeled 'Ta3\_min\_up\_dl' and 'Ta3\_max\_up\_dl' point to the t=0 line. A red double-headed arrow labeled 'Transmission window U-Plane UL' is shown between the two 'U' boxes. The horizontal axis is labeled 't'. - -Figure 3.2.3.4-37 Simplified Timing for Uplink - -The test frame used for downlink tests will be (by default) will be the 3GPP G-FR1-A1-1 FDD signal shown below in Figure 3.2.3.4-38. If the radio does not support this signal a 3GPP test wave form that the radio supports can be substituted provided there is at least one symbol in each slot available for test traffic. This symbol will be a stock data Section Type “B” described in clause 3.2.1.1.1. This symbol will contain a new PN23 sequence starting in PRB 0 and extending to all the PRBS in the test signal (274 PRBs in the example below). - -![Screenshot of 3GPP NR-FR1-TM1.1 FDD Downlink Test Signal. The main view shows a grid of CRB for u=1 (0 to 273) across 20 slots. A zoomed-in view on the left shows the first few symbols of slot 0, with PRBs 0, 23, and 46 highlighted. A legend indicates DCI (green) and DL-SCH (red). A callout box lists: All PRBs not DCI are populated with test data; DCI is the first 4 PRBs in the first symbol; Each slot contains downlink data except symbols 2 and 11 which contain DMRS. An inset titled 'RB Resource Mapping for DL-SCH1 (Modulation = QPSK)' shows a grid of subcarriers (0-12) vs symbols (0-13) with red blocks indicating data in symbols 0, 1, 3-10, 12, and 13.](185fe49c575cd3bd4aa61943ed41ba37_img.jpg) - -### 3GPP NR-FR1-TM1.1 FDD Downlink Test Signal - -- All the Physical Downlink Shared Channels (all PRBs that are not DCI) are populated with test data as described in each test case. -- DCI information is the first 4 PRBs in the first symbol of every slot. The DCI data is set to all zeros. -- Each Slot contains downlink data in each symbol except symbols 2 and 11 which contain DMRS signals and user data as shown in Red. - -Screenshot of 3GPP NR-FR1-TM1.1 FDD Downlink Test Signal. The main view shows a grid of CRB for u=1 (0 to 273) across 20 slots. A zoomed-in view on the left shows the first few symbols of slot 0, with PRBs 0, 23, and 46 highlighted. A legend indicates DCI (green) and DL-SCH (red). A callout box lists: All PRBs not DCI are populated with test data; DCI is the first 4 PRBs in the first symbol; Each slot contains downlink data except symbols 2 and 11 which contain DMRS. An inset titled 'RB Resource Mapping for DL-SCH1 (Modulation = QPSK)' shows a grid of subcarriers (0-12) vs symbols (0-13) with red blocks indicating data in symbols 0, 1, 3-10, 12, and 13. - -Figure 3.2.3.4-38 FDD Downlink Test Signal for Delay Management Tests - -The test frame used for uplink tests will be (by default) the 3GPP G-FR1-A1-1 FDD signal shown below in Figure 3.2.3.4-39. If the radio does not support this signal a 3GPP test wave form that the radio supports can be substituted provided there is at least one symbol in each slot available for test traffic. This symbol will be a stock data Section Type “B” described in 2.3.1. This symbol will contain a new PN23 sequence starting in PRB 0 and extending to all the PRBS in the test signal (25 PRBS in the example below). - -![Screenshot of 3GPP G-FR1-A1-1: SCS15k_25RB Uplink FDD Test Signal. The main view shows a grid of CRB for u=0 (0 to 160) across 10 slots. A zoomed-in view on the left shows the first few symbols of slot 0, with PRBs 0, 23, and 46 highlighted. A legend indicates UL-SCH (blue). A callout box lists: All PRBs shown in Blue are populated with test data; There is no UCI or SRS data; Each slot contains uplink data in each symbol except symbols 2 and 11 which contain DMRS signals only as shown in Red. An inset titled 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' shows a grid of subcarriers (0-12) vs symbols (0-13) with blue blocks indicating data in symbols 0, 1, 3-10, 12, and 13.](125aeb04c622d45656bd18af1b29af75_img.jpg) - -### 3GPP G-FR1-A1-1: SCS15k\_25RB Uplink FDD Test Signal - -- All the Physical Uplink Shared Channels (all PRBs shown in Blue) are populated with test data as described in each test case. -- There is no UCI or SRS data -- Each Slot contains uplink data in each symbol except symbols 2 and 11 which contain DMRS signals only as shown in Red. - -Screenshot of 3GPP G-FR1-A1-1: SCS15k\_25RB Uplink FDD Test Signal. The main view shows a grid of CRB for u=0 (0 to 160) across 10 slots. A zoomed-in view on the left shows the first few symbols of slot 0, with PRBs 0, 23, and 46 highlighted. A legend indicates UL-SCH (blue). A callout box lists: All PRBs shown in Blue are populated with test data; There is no UCI or SRS data; Each slot contains uplink data in each symbol except symbols 2 and 11 which contain DMRS signals only as shown in Red. An inset titled 'RB Resource Mapping for UL-SCH1 (Modulation = QPSK)' shows a grid of subcarriers (0-12) vs symbols (0-13) with blue blocks indicating data in symbols 0, 1, 3-10, 12, and 13. - -Figure 3.2.3.4-39 Uplink FDD Test Signal for Delay Management Tests - -3.2.3.4.1 UC-Plane O-RU Scenario Class DLM Test #1: Downlink – Positive testing - -A. Test Description and Applicability - -This test is MANDATORY. - -This test case will validate that the timing on the air interface is according to requirements specified in the CUS Specification when the C-Plane and the U-Plane messages are received within the O-RU’s reception windows. - -Four different test cases for downlink can be performed when the expected outcome is positive, i.e. the O-RU shall be able to transmit the received U-Plane-data on the air interface. These are shown in Figure 3.2.3.4-40. Note that in these tests the C-Plane reception window may be applicable to the slot or symbol boundaries depending on the Radio’s capabilities. That is, in some radios, the C-Plane reception window is at the beginning of each slot and all C-Plane messages will be sent at once within this window. Other radios will require C-Plane messages to be sent in a reception window for each symbol, In all cases U-Plane messages will be sent during reception windows corresponding to each symbol regardless of whether the radio has large enough buffers to store U-Plane data for multiple symbols. - -![Figure 3.2.3.4-40 Downlink Positive Test Cases. The figure shows four timing diagrams labeled 1: Early - Early, 2: Early - Late, 3: Late - Early, and 4: Late - Late. Each diagram shows the timing of O-RU reception windows for U-plane and C-plane relative to a t=0 reference. Parameters include T2a_min_up_dl, T2a_max_up_dl, T_cp_adv_dl, T2a_min_cp_dl, and T2a_max_cp_dl.](a66272356c31124486c091940638c76b_img.jpg) - -The figure illustrates four downlink positive test cases for timing alignment. Each case shows the relationship between the O-RU's reception windows for the U-plane and C-plane relative to a reference time $t=0$ . - -- 1: Early - Early**: Both the U-plane and C-plane reception windows are early relative to $t=0$ . The U-plane window is defined by $T2a\_min\_up\_dl$ and $T2a\_max\_up\_dl$ . The C-plane window is defined by $T2a\_min\_cp\_dl$ and $T2a\_max\_cp\_dl$ . The advance time $T_{cp\_adv\_dl}$ is shown. -- 2: Early - Late**: The U-plane reception window is early, while the C-plane reception window is late relative to $t=0$ . -- 3: Late - Early**: The U-plane reception window is late, while the C-plane reception window is early relative to $t=0$ . -- 4: Late - Late**: Both the U-plane and C-plane reception windows are late relative to $t=0$ . - -Figure 3.2.3.4-40 Downlink Positive Test Cases. The figure shows four timing diagrams labeled 1: Early - Early, 2: Early - Late, 3: Late - Early, and 4: Late - Late. Each diagram shows the timing of O-RU reception windows for U-plane and C-plane relative to a t=0 reference. Parameters include T2a\_min\_up\_dl, T2a\_max\_up\_dl, T\_cp\_adv\_dl, T2a\_min\_cp\_dl, and T2a\_max\_cp\_dl. - -Figure 3.2.3.4-40 Downlink Positive Test Cases - -1st case “C-Plane Early – U-Plane Early”; the C-Plane message is received by the O-RU at the beginning of the reception window for the C-Plane messages (indicated with small green box in figure 2.5). The corresponding U-Plane data is received in the beginning of the reception window for the U-Plane messages (indicated with small blue box in figure), i.e. $T_{cp\_adv\_dl}$ later. - -2nd case “C-Plane Early – U-Plane Late”; the C-Plane message is received by the O-RU at the beginning of the reception window for the C-Plane messages. The corresponding U-Plane data is received earliest $T_{cp\_adv\_dl}$ after the C-Plane message i.e. in the end of the U-Plane reception window. - -3rd case “C-Plane Late – U-Plane Early”; the C-Plane message is received by the O-RU at the end of the reception window for the C-Plane messages. The corresponding U-Plane data is received earliest $T_{cp\_adv\_dl}$ after the C-Plane message i.e. in the end of the reception window. - -4th case “C-Plane Late – U-Plane Late”; this case is greyed out in the figure since it will in practice be the same case as number 3, the U-Plane message cannot be received later than it is in case 3. - -## B. Test Entrance Criteria - -The O-RU must have a conducted antenna port (or TAB connector) to be connected to a signal analyser. The reception windows will be calculated and used by the CUSM-E based on the delay parameters reported by the radio on the M-Plane. - -## C. Test Methodology - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the RF signal analyser to the O-RU antenna port. Determine the correct reception windows the radio claims to support using delay management parameters repowered by the radio, - -### b. Procedure - -Configure the CUSM-ECUSM-E to send C-Plane and U-Plane messages so these messages are received within the reception windows for respective plane according to the three cases (1..3) described in Figure 3.2.3.4-40 above. - -NOTE: Make sure that the C-Plane message is received at least $T_{cp\_adv\_dl}$ earlier than the corresponding U-Plane message(s) by the O-RU. - -On the RF-signal-analyser observe the received signal and compare the decoded data on the selected test symbol to the send PN23 sequence for that symbol. - -## D. Pass/Fail Criteria (expected result) - -The test passes if the received data matches the transmitted data. - -### 3.2.3.4.2 UC-Plane O-RU Scenario Class DLM Test #2: Uplink – Positive testing - -#### A. Purpose and Description - -This test is MANDATORY. - -This test case will validate that the transmission of the U-Plane data in uplink direction is transmitted correctly by - -the O-RU within its transmission window. The CUSM-E will send C-Plane messages at both ends of the C-Plane reception window specified by the radio using the M-Plane (Two tests). The C-Plane messages will describe a test frame as shown above. The frame will have one designated symbol in each slot (not containing DMRS information). The C-Plane message will ask the radio to send that symbol's data from each slot. - -After the correct C-Plane messages are sent the CUSM-E will trigger the signal generator to send a valid test signal to the radio's RF port. This signal will contain a new, known PN23 sequence in the same symbol (per slot) designated by the C-Plane messages. - -The positive test outcome for these uplink test cases is that the corresponding U-Plane data for a specific C-Plane message is transmitted within the O-RU's transmission window IF the C-Plane message was received within the O-RU's reception window as shown in Figure 3.2.3.4-41. - -The data will be transmitted to the radio by an external signal generator and the uplink signal will be as described above. The test data sent by the signal generator will contain a known, new PN23 sequence in one symbol of each slot. The CUSM-E will expect to receive the same data for the correct symbol in each slot. - -![Timing diagram showing the relationship between C-Plane and U-Plane messages. A vertical blue line marks t=0. To the left, a box labeled 'O-RU rec. win. C-plane' has its right edge at t=0. Green arrows labeled T2a_min_cp_ul and T2a_max_cp_ul point from the left edge of this box to the t=0 line. To the right, a box labeled 'O-RU tr. win. U-plane' starts at t=0. Red arrows labeled Ta3_min_up_dl and Ta3_max_up_dl point from the t=0 line to the right edge of this box.](a194ad55e5e2b04f07456c3c728fae88_img.jpg) - -Timing diagram showing the relationship between C-Plane and U-Plane messages. A vertical blue line marks t=0. To the left, a box labeled 'O-RU rec. win. C-plane' has its right edge at t=0. Green arrows labeled T2a\_min\_cp\_ul and T2a\_max\_cp\_ul point from the left edge of this box to the t=0 line. To the right, a box labeled 'O-RU tr. win. U-plane' starts at t=0. Red arrows labeled Ta3\_min\_up\_dl and Ta3\_max\_up\_dl point from the t=0 line to the right edge of this box. - -Figure 3.2.3.4-41 Relationship between C-Plane and U-Plane Message - -Two different test cases can be identified for the uplink case. The C-Plane message is received in the beginning of the reception window or at the end of the reception window. These test cases are shown in Figure 3.2.3.4-42 below. - -![Two timing diagrams labeled '1: Early' and '2: Late'. Both have a vertical blue line at t=0 on the right. In '1: Early', the 'O-RU rec. win. C-plane' box is at the far left, with green arrows T2a_min_cp_ul and T2a_max_cp_ul pointing to t=0. In '2: Late', the 'O-RU rec. win. C-plane' box is shifted to the right, closer to t=0, with the same green arrows pointing to t=0.](d212408aecefb1f64e031eb855ea4537_img.jpg) - -Two timing diagrams labeled '1: Early' and '2: Late'. Both have a vertical blue line at t=0 on the right. In '1: Early', the 'O-RU rec. win. C-plane' box is at the far left, with green arrows T2a\_min\_cp\_ul and T2a\_max\_cp\_ul pointing to t=0. In '2: Late', the 'O-RU rec. win. C-plane' box is shifted to the right, closer to t=0, with the same green arrows pointing to t=0. - -Figure 3.2.3.4-42 Early and Late C-Plane Message Test Cases - -1st case “Early”; the C-Plane message is received by the O-RU at the beginning of the reception window for the C-Plane messages (indicated with small green box in figure). - -2nd case “Late”; the C-Plane message is received by the O-RU at the end of the reception window for the C-Plane messages. - -## B. Test Entrance Criteria - -The O-RU must have a conducted antenna port (or TAB connector) to be connected to a signal analyser. - -## C. Test Methodology - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the RF Signal Generator to the O-RU antenna port. - -### b. Procedure - -Configure the CUSM-E to send C-Plane so these messages are received within the reception windows according to the two cases (1..2) described in Figure 3.2.3.4-42 above. After these messages are sent a trigger signal will be sent to the signal generator instructing it to send the correct RF test frame at t=0. - -The CUSM-should receive U-Plane messages on the front haul interface during the uplink transmission window described by the radio over the M-Plane. - -## D. Pass/Fail Criteria (expected result) - -The test case is passed if the correct data is received at CUSM-E in the correct time window. - -### 3.2.3.4.3 UC-Plane O-RU Scenario Class DLM Test #3: Downlink – Negative testing - -#### A. Test Description and Applicability - -This test is MANDATORY. - -This test case will validate that the O-RU will correctly increment relevant M-Plane counters if C-Plane and/or U-Plane messages are not received within the respective O-RU reception windows. - -Negative testing for downlink traffic will verify that the O-RU will correctly increment relevant M-Plane counters if C-Plane and/or U-Plane messages are not received within the respective O-RU reception windows. There are four test cases defined for this Downlink test and are shown in Figure 3.2.3.4-43. The titles on each diagram show the message arrival time relative to the O-RU receive window for the C-Plane and the U-Plane in that order. For instance, test 1: Too Early-OK means the C-Plane message arrived early, outside the O-RU C-Plane receive window and the corresponding U-Plane message arrived correctly within the O-RU U-Plane receive window. - -![Figure 3.2.3.4-43 Downlink Negative Test Cases. The figure contains four sub-diagrams labeled 1 to 4. Each diagram shows the timing of O-RU receive windows for U-plane and C-plane relative to a t=0 reference. Case 1: 'Too Early - OK' shows early arrivals within limits. Case 2: 'OK - Too Early' shows a C-plane message arriving very early. Case 3: 'OK - Too Late' shows a C-plane message arriving very late. Case 4: 'Too Late - OK' shows a U-plane message arriving very late. Timing parameters include T2a_min_up_dl, T2a_max_up_dl, T_cp_adv_dl, T2a_min_cp_dl, and T2a_max_cp_dl.](1a3b66996d112dc11f6fc9e9e696728b_img.jpg) - -Figure 3.2.3.4-43 Downlink Negative Test Cases. The figure contains four sub-diagrams labeled 1 to 4. Each diagram shows the timing of O-RU receive windows for U-plane and C-plane relative to a t=0 reference. Case 1: 'Too Early - OK' shows early arrivals within limits. Case 2: 'OK - Too Early' shows a C-plane message arriving very early. Case 3: 'OK - Too Late' shows a C-plane message arriving very late. Case 4: 'Too Late - OK' shows a U-plane message arriving very late. Timing parameters include T2a\_min\_up\_dl, T2a\_max\_up\_dl, T\_cp\_adv\_dl, T2a\_min\_cp\_dl, and T2a\_max\_cp\_dl. - -Figure 3.2.3.4-43 Downlink Negative Test Cases - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters defined in clause 3.2.2 above, especially the parameters concerning delay management. - -**C. Test Methodology** - -**a. Initial Conditions** - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. - -**b. Procedure** - -Configure the CUSM-ECUSM-E to send C-Plane and U-Plane messages so these messages are received according to the four test cases shown in figure above. - -**D. Test Requirement (expected result)** - -The test case is passed if the M-Plane performance measurement objects in the list “rx-window-measurement-objects” for RX\_EARLY are incremented properly for tests 1 and 2 and RX\_LATE are incremented properly for tests 3 and 4. - -**3.2.3.4.4 UC-Plane O-RU Scenario Class DLM Test #4: Uplink – Negative Testing** - -**A. Test Description and Applicability** - -This test is MANDATORY. - -This test case will validate that the O-RU will correctly increment relevant M-Plane counters if C-Plane and/or U-Plane messages are not received within the respective O-DU reception windows. - -Negative testing for uplink traffic will verify that the O-RU will correctly increment relevant M-Plane counters if C-Plane and/or U-Plane messages are not received within the respective O-DU reception windows. There are four test cases defined for this Downlink test and are shown in Figure 3.2.3.4-44. The titles on each diagram show the message arrival time relative to the O-RU receive window for the C-Plane and the U-Plane in that order. For instance, test 1: Too Early-OK means the C-Plane message arrived early, outside the O-RU C-Plane receive window and the corresponding U-Plane message arrived correctly within the O-RU U-Plane receive window. Negative testing for uplink traffic will verify that the O-RU will not transmit any U-Plane uplink data when C-Plane messages are not received within the window on the O-RU. - -![Figure 3.2.3.4-44 Uplink Negative Test Cases. The diagram shows two test cases: '1: Too Early' and '2: Too Late'. Both show a timeline with a vertical blue line at t=0. In '1: Too Early', a green vertical bar representing a message arrives before the start of the 'O-RU rec. win. C-plane' box. The start of the box is at T2a_min_cp_ul and the end is at T2a_max_cp_ul. In '2: Too Late', the green vertical bar arrives after the end of the 'O-RU rec. win. C-plane' box.](b7636707604e45cc57c71271bc094be1_img.jpg) - -Figure 3.2.3.4-44 Uplink Negative Test Cases. The diagram shows two test cases: '1: Too Early' and '2: Too Late'. Both show a timeline with a vertical blue line at t=0. In '1: Too Early', a green vertical bar representing a message arrives before the start of the 'O-RU rec. win. C-plane' box. The start of the box is at T2a\_min\_cp\_ul and the end is at T2a\_max\_cp\_ul. In '2: Too Late', the green vertical bar arrives after the end of the 'O-RU rec. win. C-plane' box. - -Figure 3.2.3.4-44 Uplink Negative Test Cases - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters defined in clause 3.2.2 above, especially the parameters concerning delay management. - -**C. Test Methodology** - -**a. Initial Conditions** - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. - -**b. Procedure** - -Configure the CUSM-E to send C-Plane messages so these messages are received according to the two test cases shown in figure above. - -**D. Pass/Fail (expected result)** - -The test case is passed if the M-Plane performance measurement objects in the list “rx-window-measurement-objects” for RX\_EARLY and RX\_LATE are incremented properly for test 1 and test 2 respectively. - -### 3.2.3.5 UC-Plane O-RU Scenario Class Transport (TRN) - -This test is for future study. - -### 3.2.3.6 UC-Plane O-RU Scenario Class LAA (LAA) - -The purpose of this clause is to specify LAA test cases to test the compliance of the O-RU to the O-RAN specifications. Although in LAA operation, regular C-Plane and U-Plane messages (used for operation over licensed spectrum as well) are transmitted over the fronthaul interface between the O-DU and O-RU, there exist additional C-Plane messages that are required specifically for LAA operation over unlicensed spectrum. These additional C-Plane messages are based on Section type 7 and are communicated in both UL and DL directions between the O-DU and O-RU. - -The LAA test cases only focus on LAA-related messages and operations. Other testing aspects that are applicable to LAA and non-LAA technologies (e.g. delay management, beamforming, compression, etc.) are not considered in this clause; Please refer to other clauses in the conformance test specification document. - -LAA considered in this clause is based on 3GPP Rel. 13, which only considers downlink transmission on the unlicensed spectrum (i.e. uplink transmission goes on the licensed component carrier). Hence, all the test cases in this clause will consider downlink operation only. This includes DL U-Plane messages and DL/UL C-Plane messages. Note also that UL C-Plane messages only exist in LAA technology. - -The LAA test cases for the O-RU test if the O-RU is capable of conforming with the CUSM-E instructions in terms of: - -- 1) Correctly performing the listen-before-talk (LBT) procedure (i.e. managing the congestion window). -- 2) Timely data transmission based on the spectrum sensing outcome. -- 3) Timely deferring from occupying the spectrum based on the messages received from the O-DU. - -On the other hand, testing O-RU capabilities (e.g. spectrum sensing) is out of scope of this specifications since it's not directly related to the O-RAN fronthaul interface. - -#### 3.2.3.6.1 CU-DU-LAA-CWM Test #1: LBT PDSCH Configuration and Response - -##### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. The test must be executed if the O-RU supports LAA. - -This test validates that the O-RU is capable of the following functions - -- Correctly receiving and interpreting C-Plane messages (Section Type 7 and specifically laaMsgType 0) from the TER to correctly perform LBT. -- Correctly receiving U-Plane data from the TER and correctly processes the data (i.e. drop it or transmit it) based on the LBT outcome. -- Correctly performing LBT and correctly generating C-Plane messages to inform the TER about the LBT outcomes using Section Type 7 and specifically laaMsgType 2. - -This test assumes that the O-RU is capable of processing Section Type 1 C-plane messages and its corresponding U-plane messages. - -It applies to the O-RAN CUS Specification [2]: - -- Clause 7.4 -- Clause 7.5.3.14 -- Clause 7.5.3.15 - -- Clause 7.5.3.16 -- Clause 7.5.3.17 -- Clause 7.5.3.18 -- Clause 7.5.3.19 -- Clause 7.5.3.20 -- Clause 7.5.3.21 -- Clause 7.5.3.22 -- Clause 7.5.3.23 -- Clause 7.5.3.25 -- Clause 7.5.3.27 -- Table 10.2-1 - -The purpose of this test is to: - -- Validate that the O-RU can correctly interpret C-Plane messages by correctly performing LBT. -- Validate that the O-RU can correctly construct the UL C-Plane message as specified in Section Type 7, laaMsgType 2 with the following specialized fields. Specifically, - - Verify the laaMsgLen based on the message content. - - Verify that the lbtHandle parameter in the DL C-Plane message with laaMsgType 0 matches the corresponding lbtHandle parameter in the UL C-Plane message with laaMsgType 2. - - Verify the lbtPdschRes parameter value. Set: {0, 1, 2, 3}. - - Verify the inParSF parameter value. Set: {0, 1} - - Verify the sfStatus parameter value. Set: {0, 1}. - - Verify the sfnSf value. -- Validate that the O-RU can correctly interpret U-Plane data received from the TER. -- Validate that the O-RU can correctly interpret C-Plane messages received from the TER. - -## B. Test Entrance Criteria - -- The O-RU must support LAA -- The O-RU has passed M-Plane conformance and S-Plane conformance testing. -- The O-RU has antenna ports or TAB connectors for TER connections - -## C. Test Methodology - -The test shall be executed by the TER issuing DL C-Plane messages to the O-RU DUT to cause the O-RU to execute LBT. Furthermore, the TER shall issue other U-Plane and C-Plane messages required for data transmission. The TER needs to emulate external interference to allow the O-RU to do LBT and send the LBT outcome to the TER based on the description in clause 7.2.5 of [2] - -### a. Initial Conditions - -- TER (Test Equipment, O-RU) is initialized and configured. -- The O-RU is initialized, synchronized, and configured as normal, except that it shall receive and interpret Test Commands. -- The fronthaul Ethernet interface is up. -- The O-RU is running its usual software, except that it is configured to accept and execute Test Commands to enable O-RU Conformance Testing. -- The TER needs to emulate the external interference (e.g. Wi-Fi, other LAA cells) for the O-RU to execute LBT. - -### b. Procedure - -- DL C-Plane message (LBT\_PDSCH\_REQ): - -- The TER sends DL C-Plane message to configure the DUT (i.e. O-RU) to execute LBT for PDSCH transmission using the configuration parameters in Table 3.2.3-16 below. -- The TER needs to run 4 consecutive LBT trials starting from run index 1 until run index 4. - -**Table 3.2.3-16 LBT\_PDSCH\_REQ Configuration Parameters for Different Runs.** - -| Run Index | laaMsgType | laaMsgLen | lbtHandle | lbtOffset | lbtMode | lbtDeferFactor | lbtBackoffCounter | MCOT | -|-----------|------------|-----------|-----------|-----------|---------|----------------|-------------------|------| -| 1 | 0 | 2 | 65,534 | 0 | 0 | 1 | 2 | 2 | -| 2 | 0 | 2 | 65,535 | 250 | 0 | 1 | 4 | 3 | -| 3 | 0 | 2 | 0 | 500 | 3 | 3 | 8 | 8 | -| 4 | 0 | 2 | 1 | 750 | 3 | 7 | 16 | 10 | - -- DL U-Plane data: - - TER provides U-Plane DL data to the O-RU at the correct time based on clause 5.3.4 in [2] - - TER evaluates the detected U-Plane data for correctness - - Note that multiple U-Plane messages are needed for every “run” (i.e. for every MCOT). Some of these U-Plane messages should get dropped by the TER based on the outcome of the LBT process. -- DL C-Plane (Section type 1): - - TER sends DL C-Plane message to help the DUT interpret the U-Plane data. -- UL C-Plane message (LBT\_PDSCH\_RSP) verification: - - The TER generates RF signal to emulate that the channel is busy for the durations shown in Table 3.2.3-17 below starting from the subframe where LBT is scheduled to start: - -**Table 3.2.3-17 Channel Busy Duration for Different LBT Test Runs.** - -| Run Index | Channel busy duration | -|-----------|----------------------------------------------------| -| 1 | 0 | -| 2 | 2 msecs | -| 3 | 2.5 msec | -| 4 | lbt-timer (see Clause 16.2.2 in the M-plane specs) | - -- TER starts Timeout-Timer “T1”; “T1” is of a suitable length to allow the O-RU to receive the C-Plane and U-Plane messages, process it, and act accordingly (based on the LBT outcome and the description in clause 7.2.5 of [2]) such that timer expiry is a sign of test failure. - -**D. Test Requirement (expected result)** - -- TER detects the U-Plane data at the correct time and for the correct duration based on Table 3.2.3-18 below and clause 7.2.5 of [2]. -- TER correctly detects the LBT response C-Plane messages over the fronthaul interface with results that match the emulated external interference. - -- TER detects the correct operation of the DUT based on the description in clause 7.2.5 of [2] and Table 3.2.3-18 below: - -**Table 3.2.3-18 Expected O-RU Behaviour in LBT Test Cases.** - -| Run Index | Expected behaviour | -|-----------|------------------------------------------------------------------------------------------------------------| -| 1 | Data transmission for 2 msecs starts after finishing initial spectrum sensing. | -| 2 | Data transmission for 3 msecs starts after finishing spectrum sensing for a minimum duration of 2 msecs. | -| 3 | Data transmission for 8 msecs starts after finishing spectrum sensing for a minimum duration of 2.5 msecs. | -| 4 | No Data transmission. LBT should fail. | - -### 3.2.3.7 UC-Plane O-RU Scenario Class LTE (LTE) - -This clause describes applicable LTE conformance test cases for O-RAN fronthaul interface. Since there are plenty of the commonalities between the NR and LTE test cases, this clause makes suitable references to the NR specific test cases clauses for the LTE scenarios whenever possible, as below. - -- LTE UC-Plane O-DU Scenario Class Beamforming (BFM) described in clause 3.2.3.2 -- LTE UC-Plane O-DU Scenario Class Compression (CMP) described in clause 3.2.3.3 -- LTE UC-Plane O-DU Scenario Class Delay Management (DLM) described in clause 3.2.3.4 -- LTE UC-Plane O-DU Scenario Class LAA (LAA) described in clause 3.2.3.6 -- LTE UC-Plane O-DU Scenario Class Section Type 3 described in clause 3.2.3.8 - -Subsequently, LTE-only specific generic test cases are explicitly covered below. One of the key differences applicable for LTE specific test cases as compared to NR is due to the explicit precoding behaviour supported by some of the transmission modes for LTE. - -In particular, for a Category B O-RU to implement precoding for LTE TM2-TM4, specific C-Plane instructions need to be provided to the O-RU from the O-DU. This specific aspect of the O-RAN fronthaul interface is enabled by the section extension = 0x3 described in the CUS Plane specification [2]. - -For all the test cases described in this clause: - -- Downlink tests will use a standard 3GPP E-TM1.1 test frame for FDD (clause 6.1.1.1 ETSI TS 136.141-1) as shown in Figure 3.2.3.7-45. - -![Figure 3.2.3.7-45: 3GPP E-TM1.1 Test Frame for FDD. The diagram shows a sequence of 10 subframes. Each subframe is represented by a red rectangle with a yellow vertical bar on the left side. Within each subframe, there are several thin vertical lines representing resource blocks. Two specific resource blocks are highlighted with small colored rectangles: a green one in the first subframe and a purple one in the fifth subframe.](da4b49e772815583ec294f934b9b83ad_img.jpg) - -Figure 3.2.3.7-45: 3GPP E-TM1.1 Test Frame for FDD. The diagram shows a sequence of 10 subframes. Each subframe is represented by a red rectangle with a yellow vertical bar on the left side. Within each subframe, there are several thin vertical lines representing resource blocks. Two specific resource blocks are highlighted with small colored rectangles: a green one in the first subframe and a purple one in the fifth subframe. - -**Figure 3.2.3.7-45 3GPP E-TM1.1 Test Frame for FDD** - -- Uplink tests will use a standard 3GPP UL FRC Configuration definition for FDD (TS36.521-1) and power levels 30dB above Reference Sensitivity power level as shown in Figure 3.2.3.7-46. - -![Figure 3.2.3.7-46 UL FRC Configuration for FDD: A diagram showing a series of 10 red rectangular blocks representing downlink subframes. Each red block has a thin cyan vertical line on its left side, representing the uplink control region. The blocks are arranged horizontally with small gaps between them.](04455de8d97f1961965642865418543f_img.jpg) - -Figure 3.2.3.7-46 UL FRC Configuration for FDD: A diagram showing a series of 10 red rectangular blocks representing downlink subframes. Each red block has a thin cyan vertical line on its left side, representing the uplink control region. The blocks are arranged horizontally with small gaps between them. - -Figure 3.2.3.7-46 UL FRC Configuration for FDD - -All the downlink tests in this clause use a 3GPP test wave form LTE Test Model 1.1 (E-TM1.1) with 20 MHz Bandwidth as described in ETSI TS 136.141 clause 6.1.1.1. - -There are several variations on this test signal depending on the capabilities of the radio. If for example the radio does not support the bandwidth used in the example tests as reported in the M-plane it will be up to the test developer to modify their tests to adapt to the radio. The test is expected to follow the same spirit as the tests in this document may have to be changed. - -Likewise, all uplink tests in this clause use a 3GPP test waveform described in 36.141 clause A1. As with downlink tests if the radio does not support this signal, it is up to the test developer to modify the parameters of the test without changing the spirit of the test. - -### 3.2.3.7.1 UC-Plane O-RU Scenario Class Base 3GPP DL - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame using the default parameters in clause 3.2.1.1.1 of this document except for only one spatial stream on one antenna will be used. - -This test is applicable for Category A and Category B radios (No precoding is required). As per E-TM1.1 all user data in this test will be zeros. The test will be conducted. - -#### B. Test Entrance Criteria - -- The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The test bandwidth is 20 MHz Bandwidth as described by E-TM1.1. -- The O-RU must have a conducted antenna port to be connected to a signal analyser. -- The signal analyser must have the ability to decode the downlink shared channel. - -#### C. Procedure - -##### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Connect the signal analyser to the O-RU antenna ports or TAB connectors under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -##### b. Procedure - -- Build an appropriate IQ signal describing the E-TM1.1 signal described above in the CUSM-E. -- Use the CUSM-E control interface to build the appropriate C-Plane messages that describe the signal. Every symbol should be described by a single section (DL-SCH and DCI) using Section Type 1 messages. -- The data in the sections must be all zeros. -- No Section Type zero messages will be used for this test. - -- Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above. If it contains all the same PRB assignments and all zero data, the test passes. - -### 3.2.3.7.2 UC-Plane O-RU Scenario Class Extended 3GPP DL – Resource Allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink. - -This test requires non-zero data to populate all allocated resource blocks. This data will be a PN23 sequence with a seed value of all ones. - -This test is applicable for both Category A and Category B radios. - -#### B. Test Entrance Criteria - -- The O-RU must support the default parameters in clause 3.2.1 of this document. The test bandwidth is 20 MHz Bandwidth as described by E-TM1.1. -- The O-RU must have a conducted antenna port to be connected to a signal analyser. -- The signal analyser must have the ability to decode the downlink shared channel. - -#### C. Test Methodology - -##### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Connect the signal analyser to the O-RU antenna ports or TAB connectors under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -##### b. Procedure - -- Build an appropriate IQ signal describing the E-TM1.1 signal described above in the CUSM-E. -- Use the CUSM-E control interface to build the appropriate C-Plane messages that describe the signal. Every symbol should be described by a single section (DL-SCH and DCI) using Section Type 1 messages. -- The data in the sections must be a PN23 sequence using an initial seed of all ones. -- No Section Type zero messages will be used for this test. -- Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -#### D. Test Requirement (expected result) - -- A. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -- B. The test frame received by the signal analyser should be the same as the signal described above. It contains all the same PRB assignments and data the test passes. - -### 3.2.3.7.3 UC-Plane O-RU Scenario Class Extended 3GPP UL – Resource Allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to validate correct uplink operation of the O-RU using 3GPP Reference Sensitivity level definition (Clause 7.2 ETSI TS 136.141) of the Conducted Receiver Characteristic Test (clause 7 ETSI TS 136.104) and power Levels at least 30 dB above Reference Sensitivity power Level described in E-TM1.1. This is to improve the likelihood that all data will be received by the radio correctly since we are not interested in testing receiver sensitivity but only the O-RAN protocol compliance. The data section will be a PN23 sequence with a seed value of all ones. - -Under those conditions, 3GPP compliant O-RU should deliver uplink U-Plane information that matches with the uplink signal. - -The TER (Test Equipment, O-RU) generates an uplink signal on the antenna connector or TAB connector, together with the corresponding C-Plane messages on the Fronthaul interface. The TER will capture the U-Plane messages generated by the DUT and validate if the payload matches with the uplink signal. - -This test is applicable for both Category A and Category B radios. - -It applies to the following O-RAN CUS Specification [2]: - -- Clause 7.4 -- Clause 8.3.2 -- Clause 8.3.3 - -#### B. Test Entrance Criteria - -- The O-RU must support the default parameters in clause 3.2.1 of this document. The test bandwidth is 20 MHz Bandwidth as described by E-TM1.1. -- The O-RU must have a conducted antenna port to be connected to a signal analyser. -- The signal analyser must have the ability to decode the downlink shared channel. -- The Radio must support the reMask parameter as notified by the M-Plane. - -#### C. Test Methodology - -##### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Connect the signal analyser to the O-RU antenna ports or TAB connectors under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Configure the source to transmit the required 3GPP test signal upon receiving a trigger signal from the CUSM-ECUSM-E. The signal source power level should be adjusted to setting used in the 3GPP receiver sensitivity test. - -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- Load uplink test waveform (A1-1) on the RF signal source -- Configure signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the CUSM-E that C-Plane messages have been sent. -- Load C-Plane message sequence on Test Equipment O-RU (TER) -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul messages -- Launch test to simultaneously play RF uplink frame and C-Plane messages -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information -- Extract Payload -- Compare payload binary sequences - -**D. Test Requirement (expected result)** - -1. The verdict is “Test pass” if payload binary sequences match between the uplink test frame sent to the DUT and the received U-Plane data from the DUT -2. If any of the test conditions is not true, the verdict for the whole test is "Fail" -3. If the DUT does not support initial conditions, the test verdict is "Inconclusive" - -**3.2.3.7.4 UC-Plane O-RU Scenario Class Extended using reMask parameter 3GPP DL – Resource allocation** - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages with the reMask parameter set, transfer U-Plane data into the correct resource elements and transmit this data accurately in the downlink. This test is applicable for Category A and Category B radios (No precoding is required). The test will be conducted therefore there will be no channel distortion or interference. It is mandatory the radio pass this test to be considered O-RAN conformant. - -This test requires non-zero data to populate all allocated resource blocks. This data will be a PN23 sequence with a seed value of all ones. This test is applicable for both Category A and Category B radios. - -**B. Test Entrance Criteria** - -- The O-RU must support the default parameters in clause 3.2.1 of this document. The test bandwidth is 20 MHz Bandwidth as described by E-TM1.1. -- The O-RU must have a conducted antenna port to be connected to a signal analyser. -- The signal analyser must have the ability to decode the downlink shared channel. - -**C. Test Methodology** - -**a. Initial Conditions** - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. - -- Connect the signal analyser to the O-RU antenna ports or TAB connectors under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- Build an appropriate IQ signal described above in the CUSM-E. -- Use the CUSM-E control interface to build the appropriate C-Plane messages that describe the signal. -- Every symbol should be described by a single type 1 section (DL-SCH and DCI) except symbols#6 which will be used for the reMask test. -- The data in this section must be a PN23 sequence using an initial seed of all ones. The first bits of the PN23 will be in PRB1 and continue in consecutive resource elements to the end of PRB5. No Section Type zero messages will be used for this test. -- Symbol number #6 should be stock data Section Type “D” as shown above. -- This test will only be using PRBs 1 through 5. The corresponding C-Plane message will contain a section IDs in a single C-Plane message describing symbol #6. -- The startSymbolId in the application header will be symbol #6. -- The C-Plane message will have one section with the reMask set to only the odd number resource elements. The number of PRBs will be 5. The start PRB will be 1. -- The corresponding U-Plane message will be a new PN23 Sequence (initial seed is all ones) in PRBs 1 through 5 of symbol #6. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should only contain the same PN23 signals that were sent in the U-Plane but only every other odd resource element. - -### 3.2.3.7.5 UC-Plane O-RU Scenario Class With Precoding (WPR) TxD - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to validate the correct implementation of transmit diversity of a Category B O-RU with two antenna ports. TxD uses TM2 (transmission Mode 2). For TxD, information for 2 layers is packed into a PRB for transmission from O-DU and are unpacked at the O-RU. TxD precoding is applied based on the C Plane configuration before RF transmission. - -Using a standard E-TM1.1 test frame for FDD the CUSM-E (i.e. O-RAN interface of the TER described in clause 3.2.2) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink the standard E-TM1.1 signal. - -This test is applicable for Category B radios only. - -**B. Test Entrance Criteria** - -- The O-RU must support the default parameters in clause 3.2.1 of this document. The test bandwidth is 20 MHz Bandwidth as described by E-TM1.1. -- The O-RU must have two conducted antenna ports to be connected to a signal analyser. -- The signal analyser must have the ability to decode the downlink shared channel. - -- The O-RU must support the Section Extension ExtType=3 parameter as notified by the M-Plane - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Connect the signal analyser to the O-RU antenna ports or TAB connectors under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- Build an appropriate IQ signal describing the E-TM1.1 signal described above in the CUSM-E. -- Use the CUSM-E control interface to build the appropriate C-Plane messages that describe the signal. -- Every symbol should be described by a single section (DL-SCH and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. -- The test configures two antenna ports hence two beamIDs needed (same beamID for user data and CRS REs). For Antenna Port 0, the beamId is contained in the C-Plane data section header, while the Antenna Ports 1 (“beamIdAP1”) is contained in the ExtType=3. -- Configure different eAxCs are used for each layer -- Configure following parameters in the Section Extension ExtType=3 - - codebookIndex - ‘00000000’ (invalid) - - layerID (Layer ID for DL transmission) - layer ID that are used for DL transmission - - txScheme (transmission scheme) - ‘txD’ - - numLayers (number of layers used for DL transmission) - 0001 (implies 2) - - crsReMask (CRS resource element mask) - - crsSymblNum (CRS symbol number indication) - - crsShift (crsShift used for DL transmission) -- Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.3.4. -- Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -## D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The signal relation between antenna ports or TAB connectors under test should match the expected result for Tx Diversity transmission as specified in ETSI TS 136.141 clause 4.5.1.1. - -### 3.2.3.7.6 UC-Plane O-RU Scenario Class With Precoding (WPR) SM - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to validate the correct implementation of TM3/4 Spatial Multiplexing transmission mode for a Category B O-RU with two antenna ports. For TM3/4 Spatial Multiplexing, information for 2 layers is packed into a PRB for transmission from O-DU and are unpacked at the O-RU, subsequently TM3/4 based precoding is applied based on the C Plane configuration before over the air transmission. - -Using a standard E-TM1.1 test frame for FDD the CUSM-E (i.e. O-RAN interface of the TER described in clause 3.2.2) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink the standard E-TM1.1 signal. - -This test is applicable for Category B radios only. - -## B. Test Entrance Criteria - -- The O-RU must support the default parameters in clause 3.2.1 of this document. The test bandwidth is 20 MHz Bandwidth as described by E-TM1.1. -- The signal analyser must have the ability to decode the downlink shared channel. -- The O-RU must support the Section Extension ExtType=3 parameter as notified by the M-Plane -- The O-RU must have at least two conducted antenna ports (or TAB connectors) to be connected to a signal analyser. -- The TER with connections to the O-RU must be calibrated. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Connect the signal analyser to the O-RU antenna ports or TAB connectors under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- Build an appropriate IQ signal describing the E-TM1.1 signal described above in the CUSM-E. -- Use the CUSM-E control interface to build the appropriate C-Plane messages that describe the signal. -- Every symbol should be described by a single section (DL-SCH and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. -- The test configures two antenna ports. Therefore, two beamIDs are needed. The same beamID is used for user data and CRS REs. - - For Antenna Port 0, the beamId is contained in the C-Plane data section header, while the Antenna Ports 1 (“beamIdAP1”) is contained in the ExtType=3 -- Configure following parameters in the Section Extension ExtType=3 as defined in CUS Plane Specification [2]. - - codebookIndex - indices of the precoder codebook that are used for precoding - - layerID (Layer ID for DL transmission) - layer ID that are used for DL transmission - - txScheme (transmission scheme) – set to Spatial multiplexing (no CDD) - - numLayers (number of layers used for DL transmission) – set to 0001 (implies 2) - - crsReMask (CRS resource element mask) - - crsSymNum (CRS symbol number indication) - - crsShift (crsShift used for DL transmission) - -- Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.3.4. -- Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The signal relation between antenna ports or TAB connectors under test should match the expected result for MIMO transmission as specified in ETSI TS 136.141 clause 4.5.1.1. - -### 3.2.3.8 UC-Plane O-RU Scenario Class Section Type 3 (ST3) - -This clause will specify the test scenarios to validate the correct decoding of C-Plane messages with Section Type 3. The required test setup is shown in clause 2.1, where only a stimulus RF signal is applied. - -#### 3.2.3.8.1 UC-Plane O-RU Scenario Class ST3 Test #1: NR PRACH - -**A. Test Description and Applicability {MANDATORY}** - -This test is MANDATORY. - -This test will validate the correct decoding of C-Plane messages containing Section Type 3 in 5G NR scenario by testing the correct detection of a PRACH signal. - -TER will setup the signal generator with a PRACH test waveform according to ETSI TS 138.211 clause 6.3.3, ETSI TS 138.141-1 clause 8.4.1 and A.6. The test waveform will contain the same preamble ID for every occasion repeated by following the timing offset scheme specified in the figures 8.4.1.4.2-2 or 8.4.1.4.2-3 ETSI TS 138.141-1 depending on the selected PRACH format. - -This is an example for FR1 – SCS=30 kHz – BW=100MHz – Format A3, on each occasion the time offset of the same preamble index (selected according to Table A.6-1 ETSI TS 138.141.1) is incremented by 100nsec starting from 0 up to 800nsec (9 occasions per frame). Each PRACH occasion is at the beginning of the first nine used sub-frames. The scheme is repeated every frame. - -![Waveform plot showing PRACH signal over time (0 to 10 ms) with amplitude in dB (ranging from -61.44 to 46.08). The plot shows a series of pulses corresponding to the PRACH configurations in the table below.](c8ddc7930f09ad09f782605d1c5b5733_img.jpg) - -Waveform plot showing PRACH signal over time (0 to 10 ms) with amplitude in dB (ranging from -61.44 to 46.08). The plot shows a series of pulses corresponding to the PRACH configurations in the table below. - -| # | Enabled | Power Boosting | Timing Offset | PRACH Format | Preamble Index | Root Sequence Index | Cyclic Shift Index | Frame Offset | Subframe Index | n_RA_t | n_RA_slot | n_RA_f | RA_RNTI | -|---|---------|----------------|---------------|--------------|----------------|---------------------|--------------------|--------------|----------------|--------|-----------|--------|---------| -| 0 | ✓ | 0.00 dB | 0 ns | FormatA3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | -| 1 | ✓ | 0.00 dB | 100 ns | FormatA3 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 15 | -| 2 | ✓ | 0.00 dB | 200 ns | FormatA3 | 0 | 0 | 0 | 0 | 2 | 0 | 0 | 0 | 29 | -| 3 | ✓ | 0.00 dB | 300 ns | FormatA3 | 0 | 0 | 0 | 0 | 3 | 0 | 0 | 0 | 43 | -| 4 | ✓ | 0.00 dB | 400 ns | FormatA3 | 0 | 0 | 0 | 0 | 4 | 0 | 0 | 0 | 57 | -| 5 | ✓ | 0.00 dB | 500 ns | FormatA3 | 0 | 0 | 0 | 0 | 5 | 0 | 0 | 0 | 71 | -| 6 | ✓ | 0.00 dB | 600 ns | FormatA3 | 0 | 0 | 0 | 0 | 6 | 0 | 0 | 0 | 85 | -| 7 | ✓ | 0.00 dB | 700 ns | FormatA3 | 0 | 0 | 0 | 0 | 7 | 0 | 0 | 0 | 99 | -| 8 | ✓ | 0.00 dB | 800 ns | FormatA3 | 0 | 0 | 0 | 0 | 8 | 0 | 0 | 0 | 113 | - -Figure 3.2.3.8-47 FR1 SCS 30Kz 100MHz Format A3 - -According to the PRACH waveform setting, the TER will generate a corresponding sequence of C-Plane messages with Section Type 3. By the corresponding U-Plane messages in the uplink direction, the TER will try to detect the presence of the corresponding preamble at the expected timing offset and calculate the probability of detection Pd according to the definition in TS38.141-1 clause 8.4.1.1. - -The signal will be exercised at only one O-RU port without adding any external AWGN power level or multipath fading profile and at a power level avoiding detection errors due to poor SNR (rule described in C of this scenario class). - -**B. Test Entrance Criteria** - -O-RU must have a conducted antenna port (FR1) or TAB connector. - -By the M-plane, TER will detect all the supported SCSs for PUSCH and PRACH, supported PRACH format and carrier bandwidths by the O-RU. To test the correct interpretation of Section Type 3, it is assumed that only one combination of the three above parameters supported by the O-RU is enough to validate the test. TER will choose the format either according to the PRACH Configuration Index in ETSI TS 138.211 clause 6.3.3 Table 6.3.3.2-2 and the available frequency resource, or according to the PRACH Configuration Index in ETSI TS 138.211 clause 6.3.3 Table 6.3.3.2-2, or according to the manufacturer declaration item D.103 “PRACH format and SCS” in ETSI TS 138.141-1 or according to the format information obtained by the M-plane in case O-RU implements this feature. TER shall generate M-Plane messages conformant to the selected format. If more formats are claimed, only one shall be selected to reduce the test time, preference will be given to a format specified in Table A.6.1 ETSI TS 138.141. It is assumed that the O-RU manufacturer will support at least one in that table. For the case of long preambles, it is assumed format 0 is always supported since the only one shown in the Table A.6-1 ETSI TS 138.141. - -**C. Test Methodology** - -**a. Initial Conditions** - -The O-RU is synchronized using G.8275.1. The signal generator is connected to the antenna port under test and synchronized to the same frequency reference of the O-RU. CUSM-E has completed the activation of one carrier on the O-RU port and enabled one endpoint supporting Section Type 3. The endpoint is configured with no data compression. - -## b. Procedure - -1. Set signal generator power to at least 30 dB above the setting used in the 3GPP receiver sensitivity test described in ETSI TS 138.141-1 clause 7.2.5. -2. Set signal generator frequency offset to the central carrier frequency. PRACH will be mapped over frequency according to *msg1-FrequencyStart* ( $n_{\text{RA}}^{\text{start}}$ ) parameter equal to 0. PRACH format is set according to what TER has selected from the manufacturer declarations. -3. Start PRACH waveform generation on the signal generator. Ensure the test frame is repeated enough times to generate a statistically significant number of SRS occasions. That is at least 10 occasions. -4. Configure CUSM-E to generate C-Plane Section Type 3 messages according to the PRACH occasions described in subsection A and by the following approach: - - a. In case of a PRACH format with preamble repetitions or not including preamble repetitions, only one C-Plane message with one section ID is generated per PRACH occasion. O-DU emulator will set “cpLength” field according to TS 138 the format specified in clauses 7.5.2.14 and 4.4.3 of [2]. The “timeOffset” field will be set according to the PRACH occasion position inside the slot and by following the format value specified clauses 7.5.2.12 and 4.4.3 of [2]. - - b. In both scenarios “filterIndex” field is setup based on the PRACH format and according to Table 7.5.2.3-1 of [2] and “beamId” field will set to 0 (no beamforming). -5. TER will perform PRACH detection per each PRACH occasion and compare the result with the expected preamble ID and the expected timing offset. Since the external AWGN and fading generator are not present the time error tolerance should be low, TER will use the time error tolerance in Table 8.4.1.1-1 for AWGN case according to the corresponding PRACH format and PRACH SCS. A counter of successful detections is incremented at every matching. The probability of detection is given by the ratio between that counter and the number of the expected received PRACH occasions within the test time. -6. Repeat the test procedure by setting *msg1-FrequencyStart* ( $n_{\text{RA}}^{\text{start}}$ ) parameter to the right edge of the configured carrier bandwidth in order to exercise a different frequency offset number in Section Type 3. - -## D. Pass/Fail Criteria (expected result) - -1. Test is pass if the probability of detection is 100% determined across the minimum amount of at least 10 occasions. - -### 3.2.3.8.2 UC-Plane O-RU Scenario Class ST3 Test #2: LTE PRACH - -#### A. Test Description and Applicability - -This test is **CONDITIONAL MANDATORY**. - -This test will validate the correct decoding of C-Plane messages containing Section Type 3 in LTE scenario by testing the correct detection of a PRACH signal. - -TER will setup the signal generator with a PRACH test waveform according to ETSI TS 136.211 clause 5.7, ETSI TS 136.141 clause 8.4.1 and A.6. The test waveform will contain the same preamble ID for every occasion repeated by the timing offset scheme specified in the figure 8.4.1.4.2-2 and clause 8.4.1.4.2 ETSI TS 136.141. - -According to the PRACH waveform setting, TER will generate a corresponding sequence of C-Plane messages with Section Type 3. By the corresponding U-Plane messages in the uplink direction, TER will try to detect the presence of the corresponding preamble at the expected timing offset and calculate the probability of detection $P_{d}$ according to the definition in TS36.141 clause 8.4.1.1. - -The signal will be exercised at only one O-RU port without adding any external AWGN power level or multipath fading profile and at a power level avoiding detection errors due to poor SNR (rule described in the sub-section C of this scenario class). - -**B. Test Entrance Criteria** - -O-RU must have a conducted antenna port (FR1) or TAB connector. - -By the M-plane, TER will detect all the supported SCSs for PUSCH and PRACH, supported PRACH format and carrier bandwidths by the O-RU. To test the correct interpretation of Section Type 3, it is assumed that only one combination of the three above parameters supported by the O-RU is enough to validate the test. TER will choose the PRACH format according to the PRACH Configuration Index in ETSI TS 136.211 clause 5.7 Table 5.7.1-2 and the available frequency resource, or according to the PRACH Configuration Index in ETSI TS 136.211 clause 5.7 Table 5.7.1-2, or according to the manufacturer declarations or according to the format information obtained by the M-plane in case O-RU implements this feature. TER shall generate M-Plane messages conformant to the selected format. If more formats are claimed, only one shall be selected to reduce the test time. - -**C. Test Methodology** -**a. Initial Conditions** - -O-RU is synchronized using G.8275.1. signal generator is connected to the antenna port under test and synchronized to the same frequency reference of the O-RU. CUSM-E has completed the activation of one carrier on the O-RU port and enabled one endpoint supporting Section Type 3. The endpoint is configured with no data compression. - -**b. Procedure** - -1. Set signal generator power to at least 30 dB above the setting used in the 3GPP receiver sensitivity test described in ETSI TS 136.141 clause 7.2.5. -2. Set signal generator frequency offset to the central carrier frequency. PRACH will be mapped over frequency according to *prach-FrequencyOffset* ( ) parameter equal to 0. PRACH format is set according to what TER has selected from the manufacturer declarations. -3. Start PRACH waveform generation on the signal generator. Ensure the test frame is repeated enough times to generate a statistically significant number of PRACH occasions. That is at least 10 occasions. -4. Configure CUSM-E to generate C-Plane Section Type 3 messages according to the PRACH occasions described in subsection A and by the following approach: - - a. In case of a PRACH format with preamble repetitions or not including preamble repetitions, only one C-Plane message with one section ID is generated per PRACH occasion. O-DU emulator will set ‐cpLength‐ field according to ETSI TS 138 the format specified in clauses 7.5.2.14 and 4.4.3 of [2]. The ‐timeOffset‐ field will be set according to the PRACH occasion position inside the slot and by following the format value specified clauses 7.5.2.12 and 4.4.3 of [2]. - - b. In both scenarios ‐filterIndex‐ field is setup based on the PRACH format and according to Table 7.5.2.3-1 of [2] and ‐beamId‐ field will set to 0 (no beamforming). -5. The TER will perform PRACH detection per each PRACH occasion and compare the result with the expected preamble ID and the expected timing offset. Since the external AWGN and fading generator are not present, the - -time error tolerance should be low. The TER will use the time error tolerance defined in clause 8.4.1.1 ETSI TS 136.141 for AWGN (1.04usec). On the TER, a counter is incremented for each successful preamble detection. The probability of detection is given by the ratio between that counter and the number of the expected received PRACH occasions within the test time. - -6. Repeat the test procedure by setting parameter of PRACH to the right edge of the configured carrier bandwidth in order to exercise a different frequency offset number in Section Type 3. - -#### D. Pass/Fail Criteria (expected result) - -1. Test is pass if the probability of detection is 100% determined across the minimum amount of at least 10 occasions. - -### 3.2.4 FR1 FDD Non-conducted OTA Signal Tests - -#### 3.2.4.1 UC-Plane O-RU Scenario Class NR testing Generic (NRG) - -The generic tests for FR1 FDD Non-conducted OTA are the same as the tests described in clause 3.2.3. Only the setup for the tests is different reflecting the difference between non-conductive and conductive mode testing. - -#### 3.2.4.2 UC-Plane O-RU Scenario Class Beamforming (BFM) - -This clause describes the beamforming conformance testing for O-RAN fronthaul interface. The tests do not aim to test the O-RU beamforming performance or capabilities but to test that the O-RU under test focuses the RF energy or sensitivity into a specific direction and with a specific granularity following the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) C-Plane messages. - -Unless stated otherwise in a test case, the following statements apply to all the test cases defined in this clause: - -- It is based on Over-the-Air (OTA) testing with a setup such as described in clause 2.1 and it may be applied to any O-RU DUTs, whether the O-RU DUTs have conducted antenna ports or TAB connectors or not. -- It applies to Category A and Category B O-RU DUTs. -- It applies to LTE and/or 5G New Radio O-RU DUTs. In both cases, precoding is not required in any test case. -- If O-RU DUT supports Analog Beamforming (i.e. time domain beamforming), all the U-Plane test frames are defined by segmenting the Stock Test A: 1 section per symbol. The definition of this Stock Test A can be found in Figure 3.2.1.1-4 and the description accompanying this figure. Each slot shall include multiple sections (one per symbol within the slot) and only one beam at a time (i.e. one beamId at a time) and therefore only one beam can be tested per slot. -- If O-RU DUT supports Digital Beamforming (i.e. frequency domain beamforming), all the U-Plane test frames are defined by segmenting the Stock Test B: 2 sections per symbol definition as shown in Figure 3.2.1.1-4. Each slot shall include multiple sections (two per symbol within the slot) and only one beam per section at a time (i.e. one beamId at a time) and therefore up to two different beams can be tested per slot. -- If O-RU DUT supports multiple polarizations, it is up to the TER to determine if the testing is carried out for each polarization separately or multiple polarizations at the same time. In any case, it is important to guarantee that the correct eAxC\_ID for the correct polarization (or polarizations) is exercised. - -- For O-RU DUT that support LTE: - - Downlink tests will use a standard 3GPP E-TM1.1 test frame for FDD (clause 6.1.1.1 TS 136.141) with 20MHz bandwidth (100 RB) as shown in Figure 3.2.4.2-48. - -![Figure 3.2.4.2-48: E-TM1.1 FDD 20 MHz 100RB. This figure shows a time-frequency grid representing a 20 MHz bandwidth (100 Resource Blocks) over 10 subframes (labeled 0 to 9). The vertical axis represents frequency, and the horizontal axis represents time. The grid is filled with red blocks, with some green blocks indicating specific resource elements. Two small blue blocks are visible in the first subframe.](7449b816c06254de475a247cc72a8add_img.jpg) - -Figure 3.2.4.2-48: E-TM1.1 FDD 20 MHz 100RB. This figure shows a time-frequency grid representing a 20 MHz bandwidth (100 Resource Blocks) over 10 subframes (labeled 0 to 9). The vertical axis represents frequency, and the horizontal axis represents time. The grid is filled with red blocks, with some green blocks indicating specific resource elements. Two small blue blocks are visible in the first subframe. - -Figure 3.2.4.2-48 E-TM1.1 FDD 20 MHz 100RB - -If 20MHz is not supported by the O-RU DUT, then it will use the highest bandwidth supported by the O-RU DUT. - -- Uplink test will use a standard 3GPP UL FRC Configuration definition for FDD (TS36.521-1) and power levels at least 30dB above Reference Sensitivity power level with 20MHz bandwidth (100 RB) as shown in Figure 3.2.4.2-49. - -![Figure 3.2.4.2-49: UL FRC FDD 20 MHz 100 RB. This figure shows a time-frequency grid representing a 20 MHz bandwidth (100 Resource Blocks) over 10 subframes (labeled 0 to 9). The vertical axis represents frequency, and the horizontal axis represents time. The grid is filled with red blocks, with vertical cyan lines indicating specific resource elements across all subframes.](c1f9a65a43cd72fb7c887a69778c8e3f_img.jpg) - -Figure 3.2.4.2-49: UL FRC FDD 20 MHz 100 RB. This figure shows a time-frequency grid representing a 20 MHz bandwidth (100 Resource Blocks) over 10 subframes (labeled 0 to 9). The vertical axis represents frequency, and the horizontal axis represents time. The grid is filled with red blocks, with vertical cyan lines indicating specific resource elements across all subframes. - -Figure 3.2.4.2-49 UL FRC FDD 20 MHz 100 RB - -If 20MHz is not supported by the O-RU DUT, then it will use the highest bandwidth supported by the O-RU DUT. - -- For O-RU DUT that support 5G NR: - - Downlink tests will use a standard 3GPP NR-FR1-TM1.1 test frame for FDD in [19] (clause 4.9.2 TS138.141-1) of the Conducted Transmitter Characteristic Test (clause 6 TS138.141-1) as described in clause 3.2.1.1. The test numerology will be preferably 30kHz subcarrier spacing and 100 MHz Bandwidth. If not supported, then it will use any other supported subcarrier spacing and the highest bandwidth of the O-RU DUT. - - Uplink tests will use a standard 3GPP G-FR1-A1-5 Reference Sensitivity level definition (clause 7.2 and Annex A TS138.141-1) of the Conducted Receiver Characteristic Test (clause 7 ETSI TS 138.141) and power levels at least 30dB above Reference Sensitivity power level as described in clause 3.2.1.1. The test numerology will be preferably 30kHz subcarrier spacing and 100 MHz Bandwidth, if supported. Otherwise, it will use any available subcarrier space and the highest bandwidth supported by the O-RU DUT. -- Radiated tests coordinate system is based on the coordinate system defined in clause 12.5.2 of [2]. -- The O-RU DUT must: - - support the default parameters in clause 3.2.1.1.2 of this document. - - have installed current release of shipping software. - - be fully calibrated up to Radiated Interface Boundary (RIB). It is expected to be calibrated by O-RU vendor prior to testing. - -- The TER must: - - be capable of carrying out any signal processing required to generate and demodulate 3GPP compliant waveforms. - - be able to calculate or extract the beam direction via OTA measurements. - - be able to generate and deliver signals with the required beam direction at the RIB point. - - be fully calibrated up to the interface where it interacts with the DUT’s RIB. For that, a known test signal might be either injected by the TER into the O-RU DUT, or internally generated by the O-RU DUT, and the O-RU DUT must not apply any digital or analogue beam direction to the known test signal. One possible method to perform calibration uses injected C-Plane and U-Plane signals from TER into the O-RU and using C-Plane messages with beamID=0. Alternatively, calibration methods for radiated test setups that are described in ETSI TR 137.941 can be used. -- The O-DU emulator of the TER must: - - be capable of generating and sending U-Plane messages containing 3GPP test frames following the corresponding Stock sectioning defined above, as well as be capable of capturing U-Plane messages and extracting 3GPP test frames (i.e. IQ data) from the captured U-Plane messages. - - be capable of generating the C-Plane messages for, receiving, extracting and demodulating the 3GPP test frames following the corresponding Stock sectioning defined above. -- The TER might have a single test antenna if a single beam direction and polarization is measured at a time, or multiple test antennas if multiple beam directions and/or polarizations are measured at the same time. -- It is up to the TER on how to extract the beam direction and beam properties at the DUT’s RIB in order to match it with the manufacturer’s declaration. -- The user payload will be generated as PN23 with a seed of all ones. -- It applies to the following O-RAN CUS Specification [2]: - - Clause 7.4 - - Clause 8.3.2 - - Clause 8.3.3 - - Clause 12 - - Annex J - -### 3.2.4.2.1 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – No Beamforming - -#### B. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with no beamforming (beamId=0x000) and with one spatial stream (single eAxC). - -#### B. Test Entrance Criteria - -- Manufacturers’ declaration that defines list of beam directions when O-RU DUT is operating with no beamforming. - -#### C. Test Methodology - -**a. Initial Conditions** - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.2 and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.2. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.2. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- a. Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (DL-SCH and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. -- c. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.2. -- d. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. -- e. Measure any metric/s that allows for extracting the transmitted beam direction from a single measurement, i.e. transform-based techniques, or take as many measurements as possible of any metric/s from multiple angles, by for example rotating the O-RU, that allows for extracting beam direction from multiple measurement, i.e. beam scanning. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser at the expected transmitted beam direction should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received at the expected transmitted beam direction by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The extracted beam direction is defined as the direction where the best metric/s were measured (i.e. best EVM, power, SNR, etc.) and should match the expected beam direction for the expected no beamforming within a tolerance defined by the manufacturer. - -**3.2.4.2.2 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – No Beamforming****A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with no beamforming (beamId=0x000) and with one spatial stream (single eAxC). - -**B. Test Entrance Criteria** - -- Manufacturers' declaration that defines list of beam directions when O-RU DUT is operating with no beamforming. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.2 and configure the signal source with any set-up information needed to allow it to synch and generate the test signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.2. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.2. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- Build an appropriate test signal described above in the signal source of the TER. -- Inject the test signal into the O-RU with the application of an initial beam direction. This initial beam direction could be the boresight direction of the receiver antenna array. -- Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (UL-SCH) using Section Type 1 messages. No Section Type zero messages will be used for this test. -- Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.2 while also triggering the signal source. -- Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU. -- Allow the O-DU to demodulate, decode and extract the payload and to measure and extract any required metric/s from the received signal that will be used later to determine what is the best received direction. -- Repeat the previous steps but now in step b apply a different beam direction when injecting the test signal into the O-RU. Repeating the process for a number of different beam directions will exercise the reception of the test signal from different beam directions. This allows to determine if the O-RU is really focusing the sensitivity to the correct beam direction. - -### D. Test Requirement (expected result) - -1. The test frame received at the expected beam direction by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -2. The extracted beam direction is defined as the direction where the best metric/s were measured (i.e. best EVM, power, SNR, etc.) and should match the expected beam direction for the expected no beamforming within a tolerance defined by the manufacturer. - -### 3.2.4.2.3 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Predefined-beam Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with predefined-beams beamforming (beamId≠0x000) and with one spatial stream (single eAxC). - -The transmitted beam direction is measured for each indexed beam required in this measurement, see below. The measured transmitted direction is compared to manufacturer-designated direction. Transmitted direction is defined by extracting the beam direction. - -The elevation $\theta$ and azimuth $\Phi$ angles are defined as in clause 12.4.2.2 of [2]. - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Predefined-beam Beamforming conformance test might include multiple tests that the O-RU must comply: - -**a. “Coarse” beamIds test:** - -If O-RU supports and reports beamIds that are defined as coarse granularity (coarse beamIds) to the O-DU emulator, the test should include the following beams: - -1. A beam with 0 degrees azimuth ( $\Phi$ ) and elevation ( $\theta$ ) angles. -2. A beam with maximum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -3. A beam with maximum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). -4. A beam with minimum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -5. A beam with minimum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). - -If the O-RU only supports one azimuth ( $\Phi$ ) or elevation angle ( $\theta$ ), fewer than 5 beam angles will be measured. - -## B. Test Entrance Criteria - -- Manufacturers’ defined list of beam indices and their associated beam directions with antenna array characteristics. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.2 and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.2. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.2. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- a. Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (DL-SCH and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. -- c. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.2. -- d. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -- e. Measure any metric/s that allows for extracting the transmitted beam direction from a single measurement, *i.e.* transform-based techniques, or take as many measurements as possible of any metric/s from multiple angles, by for example rotating the O-RU, that allows for extracting beam direction from multiple measurement, *i.e.* beam scanning. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser at the expected transmitted beam direction should satisfy a basic 3GPP signal performance requirement for this radio category (*i.e.* EVM). -2. The test frame received at the expected transmitted beam direction by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The extracted beam direction is defined as the direction where the best metric/s were measured (*i.e.* best EVM, power, SNR, *etc.*) and should match the expected beam direction for the beam under test within a tolerance defined by the manufacturer. - -**3.2.4.2.4 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Predefined-beam Beamforming** -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with predefined-beams beamforming ( $beamId \neq 0x000$ ) and with one spatial stream (single eAxC). - -The same description and criteria for selecting the beams to be tested applies as in clause 3.2.4.2.3 applies, but instead it is related to the uplink direction. - -**B. Test Entrance Criteria** - -- Manufacturers' defined list of beam indices and their associated beam directions with antenna array characteristics. - -**C. Test Methodology** -**a. Initial Conditions** - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.2 and configure the signal source with any set-up information needed to allow it to synch and generate the test signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.2. -- Align the O-RU to a default initial position, *i.e.* align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.2. -- Let the DUT and TER to warm to the normal operating temperature within specified range - -**b. Procedure** - -- a. Build an appropriate test signal described above in the signal source of the TER. -- b. Inject the test signal into the O-RU with the application of an initial beam direction. This initial beam direction could be the boresight direction of the receiver antenna array. - -- c. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (UL-SCH) using Section Type 1 messages. No Section Type zero messages will be used for this test. -- d. Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.2 while also triggering the signal source. -- e. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU. -- f. Allow the O-DU to demodulate, decode and extract the payload and to measure and extract any required metric/s from the received signal that will be used later to determine what is the best received direction. -- g. Repeat the previous steps but now in step b apply a different beam direction when injecting the test signal into the O-RU. Repeating the process for a number of different beam directions will exercise the reception of the test signal from different beam directions. This allows to determine if the O-RU is really focusing the sensitivity to the correct beam direction. - -#### D. Test Requirement (expected result) - -1. The test frame received at the expected beam direction by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -2. The extracted beam direction is defined as the direction where the best metric/s were measured (i.e. best EVM, power, SNR, etc.) and should match the expected beam direction for the beam under test within a tolerance defined by the manufacturer. - -### 3.2.4.2.5 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Weight-based Dynamic Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with weight-based dynamic beamforming with one spatial stream (single eAxC). - -The transmitted beam direction is measured for each weighted beam required in this measurement, see below. The measured transmitted direction is compared to manufacturer-designated direction. Transmitted direction is defined by extracting the beam direction. - -The elevation $\theta$ and azimuth $\Phi$ angles are defined in clause 12.4.2.2 of [2]. - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Weight-based Dynamic Beamforming conformance test should evaluate the following beams for the O-RU to comply: - -- a. A weight-based beam with 0 degrees azimuth ( $\Phi$ ) and elevation ( $\theta$ ) angles. -- b. A weight-based beam with maximum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -- c. A weight-based beam with maximum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). -- d. A weight-based beam with minimum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -- e. A weight-based beam with minimum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). - -If the O-RU only supports one azimuth ( $\Phi$ ) or elevation angle ( $\theta$ ), fewer than 5 beam angles will be measured. - -The user/tester selects the bitwidth for the mantissa or scaler of the compression method applied to the beams. The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Weight—based Dynamic Beamforming conformance test should also evaluate the following compression methods for each of the supported beams described above (a. to e.) for the O-RU to comply: - -- a. No compression method applied to the beamforming weights. -- b. Block floating point compression method applied to the beamforming weights with the selected number of bit mantissa. -- c. Block scaling compression method applied to the beamforming weights with the selected number of bit scaler. -- d. $\mu$ -law compression method applied to the beamforming weights with the selected number of bit fixed width. -- e. Depending on what type of Beamspace compression the DUT supports, either Beamspace compression method applied to the beamforming weights with the selected number of bit scaler, or Beamspace compression method applied to the beamforming weights with the selected number of bit mantissa. - -If the O-RU does not support all the compression methods described above, fewer than 5 compression methods will be measured. - -## B. Test Entrance Criteria - -- Manufacturers' defined list of frequency domain ( $\phi$ ) and/or time domain ( $\theta$ ) weights and their associated beam directions with antenna array characteristics - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.2 and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.2. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.2. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- a. Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by one or two sections (DL-SCH and DCI) using Section Type 1 messages, the sections in the first symbol of the slot will contain section extension extType=0x01 to convey the beam weights, it is not required that the next sections contain extension type 1 since the same beam IDs will not change along the slot. If O-RU does not support a field, then its value should be 0x0. No Section Type zero messages will be used for this test. -- c. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- d. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -- e. Measure any metric/s that allows for extracting the transmitted beam direction from a single measurement, i.e. transform-based techniques, or take as many measurements as possible of any metric/s from multiple angles, by for example rotating the O-RU, that allows for extracting beam direction from multiple measurement, i.e. beam scanning. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser at the expected transmitted beam direction should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received at the expected transmitted beam direction by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The extracted beam direction is defined as the direction where the best metric/s were measured (i.e. best EVM, power, SNR, etc.) and should match the expected beam direction for the beam under test within a tolerance defined by the manufacturer. - -#### 3.2.4.2.6 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Weight-based Dynamic Beamforming - -##### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with weight-based beamforming and with one spatial stream (single eAxC). - -The same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.2.5 but applies to the uplink direction. - -##### B. Test Entrance Criteria - -- Manufacturers' defined list of frequency domain ( $\phi$ ) and/or time domain ( $\theta$ ) weights and their associated beam directions with antenna array characteristics. - -##### C. Test Methodology - -###### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.2 and configure the signal source with any set-up information needed to allow it to synch and generate the test signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.2. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.2. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -###### b. Procedure - -- a. Build an appropriate test signal described above in the signal source of the TER. -- b. Inject the test signal into the O-RU with the application of an initial beam direction. This initial beam direction could be the boresight direction of the receiver antenna array. - -- c. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by one or two sections (UL-SCH) using Section Type 1 messages, the sections in the first symbol of the slot will contain section extension extType=0x01 to convey the beam weights, it is not required that the next sections contain extension type 1 since the same beam IDs will not change along the slot. If O-RU does not support a field, then its value should be 0x0. No Section Type zero messages will be used for this test. -- d. Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.2 while also triggering the signal source. -- e. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. -- f. Repeat the previous steps but now in step b apply a different beam direction when injecting the test signal into the O-RU. Repeating the process for a number of different beam directions will exercise the reception of the test signal from different beam directions. This allows to determine if the O-RU is really focusing the sensitivity to the correct beam direction. - -#### D. Test Requirement (expected result) - -1. The test frame received at the expected beam direction by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -2. The extracted beam direction is defined as the direction where the best metric/s were measured (i.e. best EVM, power, SNR, etc.) and should match the expected beam direction for the beam under test within a tolerance defined by the manufacturer. - -### 3.2.4.2.7 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Attribute-based Dynamic Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with attributed-based dynamic beamforming with one spatial stream (single eAxC). - -If the O-RU DUT supports Attribute based Dynamic Beamforming, this test is mandatory for the O-RU DUT to be O-RAN conformant. - -The transmitted beam direction and attributes are measured for each attributed beam required in this measurement, see below. The measured transmitted direction and attributes, i.e. pointing azimuth and elevation angles, beamwidths and sidelobe suppression, is compared to manufacturer-designated direction and attributes. Transmitted direction and beam attributes are defined extracting the beam properties. - -The elevation $\theta$ and azimuth $\Phi$ angles are defined as in clause 12.4.2.2 of [2]. - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Attribute-based Dynamic Beamforming conformance test should evaluate the following beams for the O-RU to comply: - -- a. An attribute-based beam with 0 degrees azimuth ( $\Phi$ ) and elevation ( $\theta$ ) angles with any beamwidth and sidelobe suppression supported by the O-RU under this beam direction. -- b. An attribute-based beam with maximum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ) with the widest beamwidth and lowest sidelobe suppression supported for this specific beam direction. -- c. An attribute-based beam with maximum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ) with the narrowest beamwidth and highest sidelobe suppression supported for this specific beam direction. - -- d. An attribute-based beam with minimum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ) with the widest beamwidth and lowest sidelobe suppression supported for this specific beam direction. -- e. An attribute-based beam with minimum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ) with the narrowest beamwidth and highest sidelobe suppression supported for this specific beam direction. - -If the O-RU only supports one azimuth ( $\Phi$ ) or elevation angle ( $\theta$ ), fewer than 5 beam angles and attribute configurations will be measured. - -## B. Test Entrance Criteria - -- Manufacturers' defined list of supported beam attributes that are supported by the O-RU and/or their associated beam directions with antenna array characteristics. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.2 and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.2. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.2. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- a. Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by one or two sections (DL-SCH and DCI) using Section Type 1 messages, the sections in the first symbol of the slot will contain section extension extType=0x02 to convey the beam weights, it is not required that the next sections contain extension type 2 since the same beam IDs will not change along the slot. If O-RU does not support a field, then its value should be 0x0. No Section Type zero messages will be used for this test. -- c. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- d. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. -- e. Measure any metric/s that allows for extracting the transmitted beam attributes from a single measurement, i.e. transform-based techniques, or take as many measurements as possible of any metric/s from multiple angles, by for example rotating the O-RU, that allows for extracting beam attributes from multiple measurement, i.e. beam scanning. - -## D. Test Requirement (expected result) - -- 1. The signal measured at the expected beam direction by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -- 2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. - -- 3. The extracted beam attributes are referenced from the measured beam direction where the best metric/s were measured (i.e. best EVM, power, SNR, etc.) and should match the expected beam direction and attributes for the beam under test within a tolerance defined by the manufacturer. - -### 3.2.4.2.8 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Attribute-based Dynamic Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with attribute-based beamforming with one spatial stream (single eAxC). - -Same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.2.7 but considering uplink direction. - -#### B. Test Entrance Criteria - -- Manufacturers' defined list of supported beam attributes that are supported by the O-RU and/or their associated beam directions with antenna array characteristics. - -#### C. Test Methodology - -##### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.2 and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.2. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.2. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -##### b. Procedure - -- a. Build an appropriate test signal described above in the signal source of the TER. -- b. Inject the test signal into the O-RU with the application of an initial beam direction. This initial beam direction could be the boresight direction of the receiver antenna array. -- c. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by one or two sections (UL-SCH) using Section Type 1 messages, the sections in the first symbol of the slot will contain section extension extType=0x02 to convey the beam weights, it is not required that the next sections contain extension type 2 since the same beam IDs will not change along the slot. If O-RU does not support a field, then its value should be 0x0. No Section Type zero messages will be used for this test. -- d. Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.12 while also triggering the signal source. -- e. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. - -- f. Repeat the previous steps but now in step b apply a different beam direction when injecting the test signal into the O-RU. Repeating the process for a number of different beam directions will exercise the reception of the test signal from different beam directions. This allows to determine if the O-RU is really focusing the sensitivity to the correct beam direction with the correct beam attributes. - -**D. Test Requirement (expected result)** - -1. The test frame received at the expected beam direction by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -2. The extracted beam attributes are referenced from the measured beam direction where the best metric/s were measured (i.e. best EVM, power, SNR, etc.) and should match the expected beam direction and attributes for the beam under test within a tolerance defined by the manufacturer. - -### 3.2.4.2.9 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Channel-Information-based Beamforming - -**A. Test Description and Applicability** - -This Test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with channel-information-based beamforming with multiple spatial streams from multiple users (i.e. MU-MIMO). - -For Category A radios, the test is for each polarization separately and consequently either different or same channel models can be defined for each of the polarization. For Category B, same channel might be used for both polarizations and the test might measure each polarization separately. - -The transmitted beam direction is measured for each scenario required in this measurement. The measured transmitted direction is extracted from the decoded received signal in the TER. Transmitted direction is defined by properly receiving a data transmission between the O-RU and the target User Equipment while destroying or heavily attenuating the data transmission between the O-RU and the other User Equipment. - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Channel-Information-based Beamforming conformance test should evaluate the following scenarios for the O-RU to comply and will rely on TER Channel Emulation capabilities as shown in Figure 3.2.4.2-50. - -![Diagram of Test Equipment, RU (TER) showing a DUT = O-RU connected to multiple UE layers via a Precoding Matrix G.](372a0b094d72de45d94c6c8d52714e9a_img.jpg) - -The diagram illustrates a 'Test Equipment, RU (TER)' setup. It features a central 'DUT = O-RU' block. On the left, two input signals, 'UE 0 Layer 0' (eAxC 0) and 'UE 1 Layer 0' (eAxC 1), enter a 'Precoding Matrix G' block. The output of this matrix is connected to a vertical stack of $M$ antennas, represented by a bracket and three antenna icons. These antennas are shown communicating wirelessly with two user equipment (UE) blocks on the right, labeled 'UE 0 Layer 0' and 'UE 1 Layer 0'. - -Diagram of Test Equipment, RU (TER) showing a DUT = O-RU connected to multiple UE layers via a Precoding Matrix G. - -Figure 3.2.4.2-50 TER with Channel Emulation Capability antennas representing multiple UEs - -A scenario where two spatial streams, or eAxC flows, are generated for two users (one layer each) with $M$ antennas ports or TAB connectors. The O-DU will report to the O-RU via C plane messages an channel estimate , which is the effective channel as seen by the antennas representing the multiple UEs, which are spaced sufficiently such that the O-RU can effectively equalize out the interference between the users. The O-RU will calculate and apply the beamweight matrix in such that the received signal at the users is the same as the generated in the O-DU. It is up to the O-RU on how to calculate the beamforming weights, for example Zero-forcing, regularized zero-forcing / MMSE, etc. - -If O-RU supports Analog Beamforming (Time Domain Beamforming), the test should not apply any analogue beamforming or time domain beamforming. In this case, $M$ is not the number of antennas ports or TAB connectors but the number of TRX channels supported by the O-RU. - -**B. Test Entrance Criteria** - -- The O-RU must have at least two TRX chains with radiating antennas. -- The TER equipment must include 2 antennas with sufficient separation to emulate the 2 users such that the O-RU can equalize out the mutual interference of the users due to the effective MU-MIMO channel. -- Manufacturers’ defined list of number of TRX chains and what antennas are connected to each TRX chain. - -**C. Test Methodology** - -**a. Initial Conditions** - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antennas and TER equipment are calibrated within acceptable tolerance. -- Place the test antennas within the OTA chamber as defined in 3.2.1.1.2 with sufficient separation for effective MU-MIMO beamforming and configure the analyser ports with any setup information needed to synch and demodulate the MU-MIMO transmitted signal - -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.2. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.2. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- a. Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator, with the data symbols for user 1 and user 2 fully overlapping in time and frequency, but with user data initialized using different seeds for the PN23 sequence. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. Every symbol should be described by either one or two sections (DL-SCH and DCI) using Section Type 5 and 6 messages. No Section Type zero messages will be used for this test. -- c. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- d. Capture the test signals and pass them through a channel emulator or apply the signal processing required to emulate the channel under test using the 2 test antennas. -- e. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frames for the 2 users. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser for each of the expected UE – layer - should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser for each of the expected UE – layer - should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. - -**3.2.4.2.10 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Channel-Information-based Beamforming****A. Test Description and Applicability** - -This Test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with channel-information-based beamforming with multiple spatial streams from multiple users (i.e. MU-MIMO). - -Same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.2.10 but considering the uplink direction. - -**B. Test Entrance Criteria** - -- The O-RU must have at least two TRX chains with radiating sensing antennas. -- The TER equipment must include 2 antennas with sufficient separation to emulate the 2 users such that the O-RU can equalize out the mutual interference of the users due to the effective MU-MIMO channel. -- The TER equipment must have at least two probe transmitting antennas to radiate the test signals to the O-RU. -- The TER equipment must either include a channel emulator between the signal generator and the probe transmitting antennas or the signal generator be capable of applying the required channel matrix being emulated between the users and the O-RU. -- Manufacturers' defined list of number of TRX chains and what antennas are connected to each TRX chain. - -**C. Test Methodology****a. Initial Conditions** - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.2 with sufficient separation for effective MU-MIMO beamforming and configure the generator with any set-up information needed to transmit the signals from the 2 UEs. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.2. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.2. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -#### b. Procedure - -- a. Build an appropriate test signal for each of the 2 users as described above in the signal sources of the TER using a different seed to initialize the PN23 data for each user. -- b. Inject the test signals through a channel emulator or apply the required signal processing to emulate the channel under test. -- c. Radiate the resulting test signals over the air into the antennas of the O-RU. -- d. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (UL-SCH) using Section Type 5 and 6. No Section Type zero messages will be used for this test. -- e. Play the C plane messages to the O-RU respecting timing windows described in clause 2.4. while also triggering the signal source. -- f. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload for each of the users. - -#### D. Test Requirement (expected result) - -The test frame received by the TER/O-DU for each of the expected User – layer - should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. - -#### 3.2.4.3 UC-Plane O-RU Scenario Class Compression (CMP) - -The compression tests for FR1 FDD Non-conducted OTA are the same as the tests described in clause 3.2.3.3. Only the setup for the tests is different reflecting the difference between non-conductive and conductive mode testing. - -#### 3.2.4.4 UC-Plane O-RU Scenario Class Delay Management (DLM) - -The delay management tests for FR1 FDD Non-conducted OTA are the same as the tests described in clause 3.2.3.4. Only the setup for the tests is different reflecting the difference between non-conductive and conductive mode testing. - -#### 3.2.4.5 UC-Plane O-RU Scenario Class Transport (TRN) - -This test is for future study. - -#### 3.2.4.6 UC-Plane O-RU Scenario Class LAA (LAA) - -The LAA tests for FR1 FDD Non-conducted OTA are the same as the tests described in clause 3.2.3.6. Only the setup for the tests is different reflecting the difference between non-conductive and conductive mode testing. - -### 3.2.4.7 UC-Plane O-RU Scenario Class LTE (LTE) - -The test description is the same as in clause 3.2.3.7. FR1 FDD Conducted UC-Plane O-RU Scenario Class LTE. - -Only difference is that the test setup is as described in clause 3.2.1.1.2 Non-conducted OTA FDD tests for FR1 radios. - -In addition, depending on the tests, it will require one of the following two setups. - -![Figure 3.2.4.7-51: OTA setup with only a single signal analyser. The diagram shows a 'Test Equipment, RU (TER)' box containing a 'DUT = O-RU' box. On the left, 'UE 0 Layer 0' is connected to the DUT via 'eAxC 0'. On the right, the DUT is connected to 'UE 0 Layer 0' via a wireless signal. The signal path is labeled with '1' and '1'.](67f4bd11d7a8e881b6bab41e3e11d426_img.jpg) - -The diagram illustrates an OTA setup within a 'Test Equipment, RU (TER)' boundary. Inside, a 'DUT = O-RU' is shown. A 'UE 0 Layer 0' on the left connects to the DUT through an 'eAxC 0' interface. On the right, a wireless signal (represented by three curved lines) connects the DUT to another 'UE 0 Layer 0'. Above the wireless signal, there are two '1' labels, one on each side of the signal waves. - -Figure 3.2.4.7-51: OTA setup with only a single signal analyser. The diagram shows a 'Test Equipment, RU (TER)' box containing a 'DUT = O-RU' box. On the left, 'UE 0 Layer 0' is connected to the DUT via 'eAxC 0'. On the right, the DUT is connected to 'UE 0 Layer 0' via a wireless signal. The signal path is labeled with '1' and '1'. - -Figure 3.2.4.7-51 OTA setup with only a single signal analyser - -![Figure 3.2.4.7-52: OTA setup with two signal analysers or signal analyser with two ports. The diagram shows a 'Test Equipment, RU (TER)' box containing a 'DUT = O-RU' box. On the left, 'UE 0 Layer 0' and 'UE 0 Layer 1' are connected to the DUT via 'eAxC 0' and 'eAxC 1' respectively. The DUT contains a 'Precoding' block. On the right, the DUT is connected to 'Decoding' block, which then connects to 'UE 0 Layer 0' and 'UE 0 Layer 1'. The signal path is labeled with '2' and '2'.](710a9cf1a991f4226fbe1e73ea3cb6a6_img.jpg) - -This diagram shows an OTA setup within a 'Test Equipment, RU (TER)' boundary. Inside, a 'DUT = O-RU' box contains a 'Precoding' block. Two inputs, 'UE 0 Layer 0' (via 'eAxC 0') and 'UE 0 Layer 1' (via 'eAxC 1'), enter the 'Precoding' block. A wireless signal (three curved lines) exits the DUT and enters a 'Decoding' block. Above this signal, there are two '2' labels. The 'Decoding' block has two outputs leading to 'UE 0 Layer 0' and 'UE 0 Layer 1'. - -Figure 3.2.4.7-52: OTA setup with two signal analysers or signal analyser with two ports. The diagram shows a 'Test Equipment, RU (TER)' box containing a 'DUT = O-RU' box. On the left, 'UE 0 Layer 0' and 'UE 0 Layer 1' are connected to the DUT via 'eAxC 0' and 'eAxC 1' respectively. The DUT contains a 'Precoding' block. On the right, the DUT is connected to 'Decoding' block, which then connects to 'UE 0 Layer 0' and 'UE 0 Layer 1'. The signal path is labeled with '2' and '2'. - -Figure 3.2.4.7-52 OTA setup with two signal analysers or signal analyser with two ports - -### 3.2.4.7.1 UC-Plane O-RU Scenario Class Base 3GPP DL - -The test description, execution and pass criteria are the same as described in clause 3.2.3.7.1. The only difference is that the test setup is as described in clause 3.2.1.1.2 Non-conducted OTA FDD tests for FR1 radios with a single signal analyser setup as described above in Figure 3.2.4.7-51. - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame using the default parameters in clause 3.2.1.1.1 of this document except for only one spatial stream on one antenna will be used. - -This test is applicable for Category A and Category B radios (No precoding is required). -As per E-TM1.1 all user data in this test will be zeros. The test will be conducted. - -#### B. Test Entrance Criteria - -- The O-RU must support the default parameters in clause 3.2.1.1.1 of this document. The test bandwidth is 20 MHz Bandwidth as described by E-TM1.1. -- The signal analyser must have the ability to decode the downlink shared channel. - -#### C. Procedure - -##### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. 23 -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.2 and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.2. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.2. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -##### b. Procedure - -- Build an appropriate IQ signal describing the E-TM1.1 signal described above in the CUSM-E. -- Use the CUSM-E control interface to build the appropriate C-Plane messages that describe the signal. Every symbol should be described by a single section (DL-SCH and DCI) using Section Type 1 messages. -- The data in the sections must be all zeros sequence. -- No Section Type zero messages will be used for this test. -- Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above. If it contains all the same PRB assignments and all zero data, the test passes. - -### 3.2.4.7.2 UC-Plane O-RU Scenario Class Extended 3GPP DL – Resource Allocation - -The test description, execution and pass criteria are the same as described in clause 3.2.3.7.2. The only difference is that the test setup is as described in clause 3.2.1.1.2 with a single signal analyser setup as described above in Figure 3.2.4.7-51. - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink. - -This test requires non-zero data to populate all allocated resource blocks. This data will be a PN23 sequence with a seed value of all ones. - -This test is applicable for both Category A and Category B radios. - -#### B. Test Entrance Criteria - -- The O-RU must support the default parameters in clause 3.2.1 of this document. The test bandwidth is 20 MHz Bandwidth as described by E-TM1.1. -- The signal analyser must have the ability to decode the downlink shared channel. - -#### C. Test Methodology - -##### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Let the DUT and TER to warm to the normal operating temperature within specified range. -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.2 and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.2. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.2. - -##### b. Procedure - -- Build an appropriate IQ signal describing the E-TM1.1 signal described above in the CUSM-E. -- Use the CUSM-E control interface to build the appropriate C-Plane messages that describe the signal. Every symbol should be described by a single section (DL-SCH and DCI) using Section Type 1 messages. -- The data in the sections must be a PN23 sequence using an initial seed of all ones. -- No Section Type zero messages will be used for this test. -- Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above. It contains all the same PRB assignments and data the test passes. - -### 3.2.4.7.3 UC-Plane O-RU Scenario Class Extended 3GPP UL – Resource Allocation - -The test description, execution and pass criteria are the same as described in clause 3.2.3.7.3. The only difference is that the test setup is as described in clause 3.2.1.1.2 Non-conducted OTA FDD tests for FR1 radios with a single signal analyser setup as described above in Figure 3.2.4.7-51. - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to validate correct uplink operation of the O-RU using 3GPP Reference Sensitivity level definition (clause 7.2 ETSI TS 136.141) of the Conducted Receiver Characteristic Test (clause 7 ETSI TS 136.104) and power levels at least 30 dB above Reference Sensitivity power Level described in E-TM1.1. This is to improve the likelihood that all data will be received by the radio correctly since we are not interested in testing receiver sensitivity but only the O-RAN protocol compliance. - -Under those conditions, 3GPP compliant O-RU should deliver uplink U-Plane information that matches with the uplink signal. - -The TER (Test Equipment, O-RU) generates an uplink signal on the signal generator which is then transmitted over the air via the test antenna, together with the corresponding C-Plane messages on the Fronthaul interface. The TER will capture the U-Plane messages generated by the DUT and validate if the payload matches with the uplink signal. - -This test is applicable for both Category A and Category B radios. - -It applies to the O-RAN CUS Specification [2]: - -- Clause 7.4 -- Clause 8.3.2 -- Clause 8.3.3 - -#### B. Test Entrance Criteria - -- The O-RU must support the default parameters in clause 3.2.1 of this document. The test bandwidth is 20 MHz Bandwidth as described by E-TM1.1. -- The signal analyser must have the ability to decode the downlink shared channel. - -#### C. Test Methodology - -##### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Configure the source to transmit the required 3GPP test signal upon receiving a trigger signal from the CUSM-ECUSM-E. The signal source power level should be adjusted to setting used in the 3GPP receiver sensitivity test. - -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.2 and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.2. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.2. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- Load uplink test waveform (A1-1) on the RF signal source. Number of allocated RB is 6 as in A1-1 and the data content is a PN23 sequence. -- Configure signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the CUSM-E that C-Plane messages have been sent. -- Load C-Plane message sequence on Test Equipment O-RU (TER) -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul messages -- Launch test to simultaneously play RF uplink frame and C-Plane messages -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information -- Extract Payload -- Compare payload binary sequences - -**D. Test Requirement (expected result)** - -1. The verdict is “Test pass” if payload binary sequences match between the uplink test frame sent to the DUT and the received U-Plane data from the DUT -2. If any of the test conditions is not true, the verdict for the whole test is "Fail" -3. If the DUT does not support initial conditions, the test verdict is "Inconclusive" - -**3.2.4.7.4 UC-Plane O-RU Scenario Class Extended using reMask parameter 3GPP DL – Resource allocation** - -The test description, execution and pass criteria are the same as described in clause 3.2.3.7.4. The only difference is that the test setup is as described in clause 3.2.1.1.2 Non-conducted OTA FDD tests for FR1 radios with a single signal analyser setup as described above in Figure 3.2.4.7-51. - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages with the reMask parameter set, transfer U-Plane data into the correct resource elements and transmit this data accurately in the downlink. This test is applicable for Category A and Category B radios (No precoding is required). The test will be conducted therefore there will be no channel distortion or interference. It is mandatory the radio pass this test to be considered O-RAN conformant. - -This test requires non-zero data to populate all allocated resource blocks. This data will be a PN23 sequence with a seed value of all ones. This test is applicable for both Category A and Category B radios. - -**B. Test Entrance Criteria** - -- The O-RU must support the default parameters in clause 3.2.1 of this document. The test bandwidth is 20 MHz Bandwidth as described by E-TM1.1. -- The signal analyser must have the ability to decode the downlink shared channel. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.2 and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.2. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.2. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- Build an appropriate IQ signal describing the E-TM1.1 signal described above in the CUSM-E. -- Use the CUSM-E control interface to build the appropriate C-Plane messages that describe the signal. -- Every symbol should be described by a single type 1 section (DL-SCH and DCI) except symbols#6 which will be used for the reMask test. -- The data in this section must be a PN23 sequence using an initial seed of all ones. The first bits of the PN23 will be in PRB1 and continue in consecutive resource elements to the end of PRB5. No Section Type zero messages will be used for this test. -- Symbol number #6 should be stock data Section Type “D” as shown above. -- This test will only be using PRBs 1 through 5. The corresponding C-Plane message will contain a section IDs in a single C-Plane message describing symbol #6. -- The startSymbolId in the application header will be symbol #6. -- The C-Plane message will have one section with the reMask set to only the odd number resource elements. The number of PRBs will be 4. The start PRB will be 1. -- The corresponding U-Plane message will be a new PN23 Sequence (initial seed is all ones) in PRBs 1 through 5 of symbol #6. - -## D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should only contain the same PN23 signals that were sent in the U-Plane but only every other odd resource element. - -### 3.2.4.7.5 UC-Plane O-RU Scenario Class With Precoding (WPR) TxD - -The test description, execution and pass criteria are the same as described in clause 3.2.3.7.5. The only difference is that the test setup is as described in clause 3.2.1.1.2 Non-conducted OTA FDD tests for FR1 radios with two signal analysers setup as described above in Figure 3.2.4.7-52. - -### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to validate the correct implementation of transmit diversity of a Category B O-RU with two antennas. TxD uses TM2 (transmission Mode 2). For TxD, information for 2 layers is packed into a PRB for transmission from O-DU and are unpacked at the O-RU. TxD precoding is applied based on the C Plane configuration before RF transmission. - -Using a standard E-TM1.1 test frame for FDD the CUSM-E (i.e. O-RAN interface of the TER described in clause 3.2.2) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink the standard E-TM1.1 signal. - -This test is applicable for Category B radios only. - -## B. Test Entrance Criteria - -- The O-RU must support the default parameters in clause 3.2.1 of this document. The test bandwidth is 20 MHz Bandwidth as described by E-TM1.1. -- The O-RU must have at least two TRX chains with radiating antennas. -- The TER equipment must include 2 antennas with sufficient separation. The TER equipment must have at least two probe receiving antennas to receive each individual layer. -- The signal analyser must have the ability to decode the downlink shared channel. -- The O-RU must support the Section Extension ExtType=3 parameter as notified by the M-Plane - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.2 and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.2. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.2. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- Build an appropriate IQ signal describing the E-TM1.1 signal described above in the CUSM-E. the data content is a PN23 sequences starting with an initial seed of ones. -- Use the CUSM-E control interface to build the appropriate C-Plane messages that describe the signal. -- Every symbol should be described by a single section (DL-SCH and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. -- The test configures two antenna ports hence two beamIDs needed (same beamID for user data and CRS REs). For Antenna Port 0, the beamId is contained in the C-Plane data section header, while the Antenna Ports 1 (“beamIdAP1”) is contained in the ExtType=3. -- Configure different eAxCs are used for each layer -- Configure following parameters in the Section Extension ExtType=3 - - codebookIndex - ‘00000000’ (invalid) - -- layerID (Layer ID for DL transmission) - layer ID that are used for DL transmission -- txScheme (transmission scheme) - 'txD' -- numLayers (number of layers used for DL transmission) - 0001 (implies 2) -- crsReMask (CRS resource element mask) -- crsSymblNum (CRS symbol number indication) -- crsShift (crsShift used for DL transmission) -- Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.3.4. -- Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The signal relation between received signal analyser or channels of the signal analyser should match the expected result for Tx Diversity transmission as specified in ETSI TS 136.141 clause 4.5.1.1. - -#### 3.2.4.7.6 UC-Plane O-RU Scenario Class With Precoding (WPR) SM - -The test description, execution and pass criteria are the same as described in clause 3.2.3.7.6. The only difference is that the test setup is as described in clause 3.2.1.1.2 Non-conducted OTA FDD tests for FR1 radios with two signal analysers setup as described above in [Figure 3.2.4.7-52](#). - -##### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to validate the correct implementation of TM3/4 Spatial Multiplexing transmission mode for a Category B O-RU with two antennas. For TM3/4 Spatial Multiplexing, information for 2 layers is packed into a PRB for transmission from O-DU and are unpacked at the O-RU, subsequently TM3/4 based precoding is applied based on the C Plane configuration before over the air transmission. - -Using a standard E-TM1.1 test frame for FDD the CUSM-E (i.e. O-RAN interface of the TER described in clause 3.2.2) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink the standard E-TM1.1 signal. - -This test is applicable for Category B radios only. - -##### B. Test Entrance Criteria - -- The O-RU must support the default parameters in clause 3.2.1 of this document. The test bandwidth is 20 MHz Bandwidth as described by E-TM1.1. -- The signal analyser must have the ability to decode the downlink shared channel. -- The O-RU must have at least two TRX chains with radiating antennas. -- The TER equipment must include 2 antennas with sufficient separation. The TER equipment must have at least two probe receiving antennas to receive each individual layer. -- The TER with connections to the O-RU must be calibrated. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Connect the signal analyser to the O-RU TAB connectors under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.2 and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.2. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.2. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- Build an appropriate IQ signal describing the E-TM1.1 signal described above in the CUSM-E. The data content is a PN23 sequences starting with an initial seed of ones. -- The codeword-to-layer mapping follows Table 6.3.3.2-1 of ETSI TS 136.211 with one codeword to two layer mapping, but does not restrict to use two codeword to two-layer mapping. -- Use the CUSM-E control interface to build the appropriate C-Plane messages that describe the signal. -- Every symbol should be described by a single section (DL-SCH and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. -- The test configures two antenna ports. Therefore, two beamIDs are needed. The same beamID is used for user data and CRS REs. - - For Antenna Port 0, the beamId is contained in the C-Plane data section header, while the Antenna Ports 1 (“beamIdAP1”) is contained in the ExtType=3 -- Configure following parameters in the Section Extension ExtType=3 as defined in CUS Plane Specification [2]. - - codebookIndex - indices of the precoder codebook that are used for precoding - - layerID (Layer ID for DL transmission) - layer ID that are used for DL transmission - - txScheme (transmission scheme) – set to Spatial multiplexing (no CDD) - - numLayers (number of layers used for DL transmission) – set to 0001 (implies 2) - - crsReMask (CRS resource element mask) - - crsSymNum (CRS symbol number indication) - - crsShift (crsShift used for DL transmission) -- Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.3.4. -- Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -## D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23. - -3. The signal relation between the two signal analysers or two channels of the signal analyser should match the expected result for MIMO transmission as specified in ETSI TS 136.141 clause 4.5.1.1. - -#### 3.2.4.8 UC-Plane O-RU Scenario Class Section Type 3 (ST3) - -The Section Type 3 tests for FR1 FDD Non-conducted OTA are the same as the tests described in clause 3.2.3.8 . Only the setup for the tests is different reflecting the difference between non-conductive and conductive mode testing. - -## 3.2.5 FR1 TDD Conducted Signal Tests - -### 3.2.5.1 UC-Plane O-RU Scenario Class NR testing Generic (NRG) - -All TDD tests described in this clause will be combined UL and DL tests (i.e. a single test frame describing both uplink and downlink). The default test frame used in this clause is described in clause 3.2.1.1.3 of this document. There are several variations on this test signal depending on the capabilities of the radio. If the radio does not support the numerology used in the example tests as reported in the M-plane it will be up to the test developer to modify their tests to adapt to the radio. This can usually be accomplished by using stock test patterns described above. The test is expected to follow the same spirit as the tests in this document but things like symbol numbers, number of PRBs, etc. may have to be changed. - -#### 3.2.5.1.1 UC-Plane O-RU Scenario Class Base 3GPP DL/UL - -##### A. Test Description and Applicability - -This test is MANDATORY. - -The purpose of this test is to ensure the radio can meet the most basic uplink and downlink requirements for O-RAN fronthaul using a TDD signal. Subsequent tests will build on this to exercise additional capabilities of the Fronthaul. - -Using the standard TDD test frame described in clause 3.2.1.1.3 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the default signal. - -The purpose of this test is to ensure the radio can transmit and receive a basic 3GPP, TDD test frame using the default parameters in clause 3.2.1.1.5 of this document (or a similar 3GPP waveform) except only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). As per clause 3.2.1.1.3 this test requires all-zero data to populate all allocated resource blocks. This configuration corresponds to stock data section A in all symbols that do not contain PDCCH channels. - -##### B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.3 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described by TM-FR1-TM1.1 in downlink direction and G-FR1-A1-5 (SCS30k\_51RB) in the uplink direction. If the O-RU does not support this bandwidth another 3GPP FRC can be selected. In the test frame, all PDSCH data is set to all zeros and PUSCH is set to all zeros. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. - -The O-RU must have a conducted antenna port (or TAB connector) to be connected to a signal analyser and signal source. It must also support the default parameters defined in clause 3.2.1.1.3 above. - -##### C. Test Methodology - -###### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser and signal source to the O-RU antenna ports and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. - -###### b. Procedure - -Build an appropriate IQ signal describing the signal described above in clause 3.2.1.1.3 in the CUSM emulator. Built the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator - -control interface to build the appropriate C-Plane messages that describe the signal. Every symbol other than the ones used in the test should either be allocated with user data or left unallocated (empty). If allocated with user data, they be described by either a single or multiple sections (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.3. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser in the downlink direction should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received in downlink direction by the signal analyser should be the same as the signal described above. If it contains all the same PRB assignments and all zero data, the test passes. -3. The test frame received in uplink direction by the TER should be the same as the signal described above. If it contains all the same PRB assignments and all zero data, the test passes. - -### 3.2.5.1.2 UC-Plane O-RU Scenario Class Extended 3GPP DL/UL – Resource Allocation - -#### A. Test Description and Applicability - -This test is MANDATORY. - -The purpose of this test is to ensure the radio can meet the extended uplink and downlink requirements for O-RAN fronthaul using a TDD signal. This test modifies the previous test by using a PN23 sequence in all test PDSCH sections. - -Using the standard TDD test frame described in clause 3.2.1.1.3 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the default signal. - -The purpose of this test is to ensure the radio can transmit and receive an extended 3GPP TDD test frame using the default parameters in clause 3.2.1.1.3 of this document (or a similar 3GPP waveform) except only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All downlink user data in this test will be a PN23 sequence and all uplink user data will also be a PN23 sequence. - -#### B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.3 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described by TM-FR1-TM1.1. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. - -The O-RU must have a conducted antenna port (or TAB connector) to be connected to a signal analyser and signal source. It must also support the default parameters defined in clause 3.2.1.1.1 above. - -#### C. Test Methodology - -##### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. - -**b. Procedure** - -Build an appropriate IQ signal describing the signal described above in clause 3.2.1.1.3 in the CUSM emulator. In this case use a PN23 sequence for the downlink shared channel. Build the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the uplink and downlink signals. Every symbol used in the test should be described by a single section (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser in the downlink direction should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser in the downlink direction should be the same as the signal described above. If it contains all the same PRB assignments and PN23 sequence data, the test passes. -3. The test frame received in uplink direction by the TER should be the same as the signal described above. If it contains all the same PRB assignments and PN23 sequence data, the test passes. - -**3.2.5.1.3 UC-Plane O-RU Scenario Class Extended using RB parameter 3GPP DL/UL – Resource Allocation** - -**A. Test Description and Applicability** - -This test is MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages with the rb parameter set, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink and interpret and capture the correct resource blocks in the uplink with the rb parameter set. This test uses a PN23 sequence in all test PDSCH sections. - -Using the standard TDD test frame described in clause 3.2.1.1.3 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the specified signal using the rb bit in both uplink and downlink. - -Only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All downlink user data in this test will be a PN23 sequence and all uplink user data will also be a PN23 sequence. - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.3 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause 3.2.1.1.3. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. - -The O-RU must have a conducted antenna port (or TAB connector) to be connected to a signal analyser. It must also support the default parameters defined in clause 3.2.1.1.1 above. - -## C. Test Methodology - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. Connect the signal source to the O-RU antenna port and configure it as described below. - -### b. Procedure - -Build an appropriate IQ signal describing the signal described above in clause 3.2.1.1.3 in the CUSM emulator. In this case use a PN23 sequence for the downlink shared channel. Build the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the uplink and downlink signals. Every symbol used in the test should be described by a single section (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.3. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -### For the downlink slots and symbols: - -Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal. If symbols other than the ones under test are allocated with user data, every allocated (see below) symbol should be described by sections (DL-SCH and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Symbol #3 of each slot should be Stock data section "D" as shown in clause 3.2.1.1.5 above. The control plane for symbol #3 will only include PRBs number 5 through 23. C-Plane messages will have the rb bit set to one for this section. All other DL-SCH symbols and PRBs other than PRBs 5-23 will not contain data. There are two ways to conduct the test: - -1. A single data section with the rb bit set and a PN23 sequence sent as shown below: - -![A diagram showing Resource Block (RB) allocation across symbols. The vertical axis shows RB #0, RB #5, and RB #23. The horizontal axis shows Symbol #0, Symbol #3, and Symbol #13. RB #0 is labeled 'PCCH'. RB #23 is highlighted with a dashed box and labeled 'No Data'. Arrows from RB #23 point to a sequence of green blocks labeled P, N, 2, 3, S, E, Q, U, followed by an 'X'. The text 'DMRS acc. To 3GPP rules' is present on both sides of the main data section. The text 'Either DL-SCH data or No Data' is present at the beginning and end of the symbol axis.](d6bfc6f00950b27310cac9565aa89839_img.jpg) - -A diagram showing Resource Block (RB) allocation across symbols. The vertical axis shows RB #0, RB #5, and RB #23. The horizontal axis shows Symbol #0, Symbol #3, and Symbol #13. RB #0 is labeled 'PCCH'. RB #23 is highlighted with a dashed box and labeled 'No Data'. Arrows from RB #23 point to a sequence of green blocks labeled P, N, 2, 3, S, E, Q, U, followed by an 'X'. The text 'DMRS acc. To 3GPP rules' is present on both sides of the main data section. The text 'Either DL-SCH data or No Data' is present at the beginning and end of the symbol axis. - -A new PN23 sequence will be started but every other PRB will contain only the odd parts of the PN23 sequence (as shown in green). The other PRBs (shown in orange) will not contain data and will not be sent to the O-RU. Thus, a single data section will be used, and the corresponding U-Plane message will only contain data for the odd PRBs as shown above. The parts of the PN23 sequence not used (shown marked with an X) will be discarded. - -- Two data sections one containing the odd parts of the PN23 sequence and the other containing the even parts as shown below: - -![Diagram showing Resource Block (RB) allocation across symbols. The vertical axis shows RB #0, RB #5, and RB #23. The horizontal axis shows Symbol #0, Symbol #3, and Symbol #13. RB #0 contains PCCH in Symbol #0. RB #5 and RB #23 show data sections starting at Symbol #3. A dashed box labeled 'DMRS acc. To 3GPP rules' is at Symbol #3. Data is shown in green and orange blocks. Labels 'Either DL-SCH data or No Data' are on the left and right. Vertical text 'DMRS acc. To 3GPP rules' is in the middle. Letters P, N, 2, 3, S, E, Q, U are shown in the data blocks.](33af66f0d081ac1bb0133b0238de585a_img.jpg) - -Diagram showing Resource Block (RB) allocation across symbols. The vertical axis shows RB #0, RB #5, and RB #23. The horizontal axis shows Symbol #0, Symbol #3, and Symbol #13. RB #0 contains PCCH in Symbol #0. RB #5 and RB #23 show data sections starting at Symbol #3. A dashed box labeled 'DMRS acc. To 3GPP rules' is at Symbol #3. Data is shown in green and orange blocks. Labels 'Either DL-SCH data or No Data' are on the left and right. Vertical text 'DMRS acc. To 3GPP rules' is in the middle. Letters P, N, 2, 3, S, E, Q, U are shown in the data blocks. - -A new PN23 sequence will be started but every other PRB in one section will contain only the odd parts of the PN23 sequence (as shown in green). The second data section will contain the even parts of the PN23 sequence. The C-Plane messages for both sections will use the rb bit. The U-Plane messages corresponding to the first data section will contain only the odd parts of the PN23 sequence, the U-Plane message corresponding to the second data section will only contain the even parts. Thus, a continuous PN23 sequence will be sent only in PRBs 5 through 23. - -Additional sections should be included to describe the DCI symbols as well as Reference Signals described in 38.141-1 as well as if DL-SCH is allocated for all the symbols other than the one under test (Symbol #3). Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -- **For the uplink sections and symbols:** Load uplink test waveform (G-FR1-A1-5 : SCS30k\_51RB) on the RF signal source. Note this signal has a PN23 sequence as user data. Configure the signal source to play the TDD test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that all C-Plane messages have been sent. Ensure the O-RU and source are synchronized so downlink slots do not conflict with uplink slots. Load C-Plane message sequence on Test Equipment O-RU (TER) – In this test only symbol number 6 will be used and all 51 PRBs will be used. Symbol number 6 will be a guard symbol in the flexible slot if the TDD configuration according to Table 3.2.1.1 is used, so only 2 uplink slots per frame are possible. If needed, another symbol than symbol number 6 can be selected. All other symbols may either contain user data or may be left unallocated except for required DRMS signals which may be used to synchronize test equipment. There are two options for conducting this test: - -1. A single data section with the rb bit set and a PN23 sequence sent as shown below: - -![Diagram showing Resource Block (RB) mapping for symbols #0 to #13. The vertical axis represents RBs from #0 to #51. The horizontal axis represents symbols #0 to #13. A dashed box highlights Symbol #6. In Symbol #6, RBs are divided into orange (odd parts of PN23 sequence) and blue (even parts or data). Arrows point from the blue parts of RBs in Symbol #6 to a sequence of labels: P, N, 2, 3, S, E, Q, U, U. The last four 'U's are marked with a red 'X'. Text 'DMRS acc. To 3GPP rules' is present on both sides of the highlighted symbol. Text 'Either UL-SCH data or No Data' is at the far left and far right. Ellipses indicate more RBs above RB #51 and between RBs in the sequence.](4cc77834b75e6e10bed21fde344bd1f4_img.jpg) - -Diagram showing Resource Block (RB) mapping for symbols #0 to #13. The vertical axis represents RBs from #0 to #51. The horizontal axis represents symbols #0 to #13. A dashed box highlights Symbol #6. In Symbol #6, RBs are divided into orange (odd parts of PN23 sequence) and blue (even parts or data). Arrows point from the blue parts of RBs in Symbol #6 to a sequence of labels: P, N, 2, 3, S, E, Q, U, U. The last four 'U's are marked with a red 'X'. Text 'DMRS acc. To 3GPP rules' is present on both sides of the highlighted symbol. Text 'Either UL-SCH data or No Data' is at the far left and far right. Ellipses indicate more RBs above RB #51 and between RBs in the sequence. - -A new PN23 sequence will be started but every other PRB will contain only the odd parts of the PN23 sequence (as shown in orange). The other PRBs (shown in blue and white) may either have allocated user data and will be sent to the O-RU or may be left unallocated and will not be sent to the O-RU. A single data section will be used for symbol #6, and the corresponding U-Plane message will only contain data for the odd PRBs as shown above. The parts of the PN23 sequence not used (shown marked with an X) will be discarded. - -- Two data sections one containing the odd parts of the PN23 sequence and the other containing the even parts as shown below: - -![Diagram showing Resource Block (RB) mapping for UL-SCH data and DMRS across symbols #0 to #13. The vertical axis represents RBs from #0 to #51. The horizontal axis represents symbols from #0 to #13. A dashed box highlights Symbol #6. The diagram shows alternating blue and orange blocks representing data and DMRS. Labels include 'Either UL-SCH data or No Data', 'DMRS acc. To 3GPP rules', and 'PN 23 S E Q U E N C E'. Arrows indicate the mapping of PN23 sequence parts to specific RBs.](c63537ac964ee56c2797ec477b520c25_img.jpg) - -Diagram showing Resource Block (RB) mapping for UL-SCH data and DMRS across symbols #0 to #13. The vertical axis represents RBs from #0 to #51. The horizontal axis represents symbols from #0 to #13. A dashed box highlights Symbol #6. The diagram shows alternating blue and orange blocks representing data and DMRS. Labels include 'Either UL-SCH data or No Data', 'DMRS acc. To 3GPP rules', and 'PN 23 S E Q U E N C E'. Arrows indicate the mapping of PN23 sequence parts to specific RBs. - -A new PN23 sequence will be started but every other PRB in one section will contain only the odd parts of the PN23 sequence (as shown in green). The second data section will contain the even parts of the PN23 sequence. The C-Plane messages for both sections will use the rb bit. The U-Plane messages corresponding to the first data section will contain only the odd parts of the PN23 sequence, the U-Plane message corresponding to the second data section will only contain the even parts. Thus, a continuous PN23 sequence will be sent only in PRBs 0 through 51 - -**Steps:** - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and the downlink U-Plane messages and trigger the source to play the RF signal on a frame boundary. -- Play messages to the O-RU respecting the timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the frame. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information from the captured U-Plane messages -- Extract IQ information from the signal analyser for downlink slots -- Extract Payload for both signals -- Compare payload binary sequences - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser in the downlink direction should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. (VOID) -3. The test frame received by the signal analyser in the downlink direction should be the same as the signal described above. If it contains all the same PRB assignments and PN23 sequence data, the downlink test passes. -4. The test frame extracted from the uplink U-Plane messages should be the same as the uplink signal described above. If it contains all the same PRB assignments and PN23 sequence data, the uplink test passes. - -### 3.2.5.1.4 UC-Plane O-RU Scenario Class Extended using SymInc parameter 3GPP DL/UL – Resource Allocation - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages with the SymInc parameter set, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink and interpret and capture the correct resource blocks in the uplink with the SymInc parameter set. This test uses a PN23 sequence in all test PDSCH sections. - -Using the standard TDD test frame described in clause 3.2.1.1.3 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the specified signal using the SymInc bit in both uplink and downlink. - -Only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All downlink user data in this test will be a PN23 sequence and all uplink user data will also be a PN23 sequence. - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.3 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause 3.2.1.1.3. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. - -The radio must support the SymInc Parameter as notified by the M-Plane. The signal analyser must have the ability to decode the downlink shared channel. - -**C. Test Methodology****a. Initial Conditions** - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. Connect the signal source to the O-RU antenna port and configure it as described below. - -**b. Procedure** - -Build an appropriate IQ signal describing the signal described above in clause 3.2.1.1.3 in the CUSM emulator. In this case use a PN23 sequence for the downlink shared channel. Build the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the uplink and downlink signals. Every symbol other than the ones used in - -the test should either be allocated with user data or left unallocated (empty). If allocated with user data, they may be described by either a single or multiple sections (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.3. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -**For the downlink slots and symbols:** If the symbols other than the ones under test (symbols #5 and #6) have user data allocated, these symbols should be described by a single or multiple type 1 section (DL-SCH and DCI) except symbols #5 and #6 which will be used for the SymInc test. The data in these sections must be a PN23 sequence using an initial seed of all ones. Each symbol should be a new PN23 sequence, that is PRB 0 should contain the data from a new PN23 sequence for each symbol. Symbols number 5 and 6 should be stock data sections type "E" as shown above. This stock data section consists of two adjacent symbols each containing two sections. The corresponding C-Plane message will contain 4 section IDs in a single C-Plane message describing symbols #5 and #6. The startSymbolId in the application header will be symbol #5. The third section ID for symbol #6 will have the SymInc bit set informing the O-RU that this section will begin describing symbol #6. The corresponding U-Plane messages will be a new PN23 Sequence for each symbol (5 and 6). Additional sections should be included to describe the DCI symbols as well as Reference Signals described in 38.141-1. - -**For the uplink sections and symbols:** Load uplink test waveform (G-FR1-A1-5: SCS30k\_51RB, 100 MHz) on the RF signal source. Note this signal has a PN23 sequence as user data. Configure the source to generate a new PN23 sequence in symbols #5 and #6. Configure the signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that all C-Plane messages have been sent. Ensure the O-RU and source are synchronized so downlink slots do not conflict with uplink slots. Load C-Plane message sequence on Test Equipment O-RU (TER) – Only symbols #5 and #6 in each slot will be used in this test. Symbol number 6 will be a guard symbol in the flexible slot if the TDD configuration according to Table 3.2.1.1 is used, so only 2 uplink slots per frame are possible. If needed, another symbol than symbol number 6 can be selected. All other symbols may either contain reference signals only or data and reference signals but will not be considered part of the test. These two symbols will be used to determine whether the radio properly increments the current symbol ID when the SymInc bit is set. The C-Plane message for symbol #6 should have the SymInc bit set. This message should have a third section describing symbol #6 (using the SymInc mechanism). All PRBs in each symbol will be requested (In the example waveform 51 PRBs). - -#### Steps: - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and the downlink U-Plane messages and trigger the source to play the RF signal on a frame boundary. -- Play messages to the O-RU respecting the timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the frame. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information from the captured U-Plane messages -- Extract IQ information from the signal analyser for downlink slots -- Extract Payload for both signals - -- Compare payload binary sequences - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser in the downlink direction should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. (VOID) -3. The test frame received by the signal analyser in the downlink direction should be the same as the signal described above. If it contains all the same PRB assignments and the correct PN23 data, the downlink test passes. -4. The test frame extracted from the uplink U-Plane messages should be the same as the uplink signal described above. If it contains all the same PRB assignments and correct PN23 data, the uplink test passes. - -### 3.2.5.1.5 UC-Plane O-RU Scenario Class Extended using reMask parameter 3GPP DL/UL – Resource Allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages with the reMask parameter set, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink and interpret and capture the correct resource blocks in the uplink with the reMask parameter set. This test uses a PN23 sequence in all test PDSCH sections. - -Using the standard TDD test frame described in clause 3.2.1.1.3 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the specified signal using the reMask bit in both uplink and downlink. - -Only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All downlink user data in this test will be a PN23 sequence and all uplink user data will also be a PN23 sequence. - -#### B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.3 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause 3.2.1.1.3. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. - -The radio must support the reMask Parameter as notified by the M-Plane. The signal analyser must have the ability to decode the downlink shared channel. - -#### C. Test Methodology - -##### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. Connect the signal source to the O-RU antenna port and configure it as described below. - -##### b. Procedure - -Build an appropriate IQ signal describing the signal described above in clause 3.2.1.1.3 in the CUSM emulator and modified as described below. In this case use a PN23 sequence for the downlink shared channel. Build the appropriate test frame (uplink slots) as described below for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the uplink and downlink signals. Every symbol other than the ones used in the test should either be allocated with user data or left unallocated (empty). If allocated with user data, they will be described by either a single or multiple sections (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.3. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -**For the downlink slots and symbols:** - -Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal as described below. If the symbols other than the ones under test (symbol #2) have user data allocated, these symbols should be described by a single or multiple type 1 sections (DL-SCH and DCI). Only symbol #2 will be used for the reMask test. The data in this section must be a PN23 sequence using an initial seed of all ones. The first bits of the PN23 will be in PRB1 and continue in consecutive resource elements to the end of PRB5. No Section Type zero messages will be used for this test. The PN23 sequence will be interleaved with DMRS signals as shown below: - -![RB Resource Mapping for DL-SCH1 (Modulation = QPSK) diagram showing subcarriers 0-12 on the y-axis and symbols 0-13 on the x-axis. Symbol 2 contains DMRS signals in subcarriers 0-5 and user data in subcarriers 6-12. Symbols 3-12 contain user data in subcarriers 0-5 and DMRS signals in subcarriers 6-12. A 'New PN23 (init register with all 1s)' is shown for symbol 2.](469bffd8c327b2f28e2167fcaca784c6_img.jpg) - -The diagram illustrates the resource mapping for DL-SCH1 with QPSK modulation. The vertical axis represents subcarriers from 0 to 12, and the horizontal axis represents symbols from 0 to 13. In symbol 2, subcarriers 0 through 5 are allocated to DMRS signals (indicated by red blocks), while subcarriers 6 through 12 are allocated to user data (indicated by green blocks labeled 'D'). In symbols 3 through 12, subcarriers 0 through 5 are allocated to user data (green blocks labeled with various characters like 'D', 'G', 'W', 'S', 'E', 'N', 'Z', 'D'), and subcarriers 6 through 12 are allocated to DMRS signals (red blocks). A note at the bottom indicates a 'New PN23 (init register with all 1s)' sequence is used for the user data in symbol 2. - -RB Resource Mapping for DL-SCH1 (Modulation = QPSK) diagram showing subcarriers 0-12 on the y-axis and symbols 0-13 on the x-axis. Symbol 2 contains DMRS signals in subcarriers 0-5 and user data in subcarriers 6-12. Symbols 3-12 contain user data in subcarriers 0-5 and DMRS signals in subcarriers 6-12. A 'New PN23 (init register with all 1s)' is shown for symbol 2. - -Symbol number 2 should be stock data Section Type “D” as shown above. This test will only be using PRBs 1 through 5. The corresponding C-Plane message will contain two section IDs in a single C-Plane message describing symbol #2. The startSymbolId in the application header will be symbol #2. The C-Plane message will have one section with the reMask set to 101010101010b and another section with the reMask set to all ones. The first section (reMask = 101010101010b) will be for PRB 1 only, the second section will be for PRBs 2-5 and will have an reMask value of all ones. The two sections will have different section IDs. - -The corresponding U-Plane messages will be a new PN23 Sequence (initial seed is all ones) in PRBs 1 through 5 of symbol #2 alternated with the DMRS signals. The first U-Plane message will correspond to sectionID with reMask set to 101010101010b and will contain one PRB with user data and DMRS signals as shown. The second U-Plane message will correspond to PRBs 2-5 and will contain the same alternate - -data. The purpose of the section ID containing valid data is to ensure the radio sends a signal to synchronize the signal analyser. - -**For the uplink sections and symbols:** - -Load C-Plane message sequence on Test Equipment O-RU (TER) symbol #2 only PRBs 1-5 will be sent with the alternating user data and DMRS pattern shown below. Other symbols may be used in this test or be left unallocated (unused). However other symbols containing reference signals may be used to ensure the O-RU can synchronize with the TER. The format of symbol #2 used in this test will be: - -![RB Resource Mapping for UL-SCH2 (Modulation = QPSK) diagram showing subcarriers 0-12 and symbols 0-13. It illustrates the mapping of data and DMRS signals for PRBs 1-5 in symbol 2.](6cb7d7986b43faef6866b8bdcb6e4278_img.jpg) - -The diagram shows the resource mapping for UL-SCH2 with QPSK modulation. The vertical axis represents Subcarriers (0 to 12) and the horizontal axis represents Symbols (0 to 13). In Symbol 2, subcarriers 1-12 show an alternating pattern of DMRS (blue) and Data (red). A green sequence labeled "New PN23 (init register with all '1')" is mapped across symbols 6 and 7 for subcarriers 2 through 10, containing the letters P, N, 2, 3, S, E, Q, U. - -| Subcarrier | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | -|------------|-------------|------------|-------------|------------|-------------|------------|-------------|------------|-------------|------------|-------------|------------| -| Type | DMRS (Blue) | Data (Red) | DMRS (Blue) | Data (Red) | DMRS (Blue) | Data (Red) | DMRS (Blue) | Data (Red) | DMRS (Blue) | Data (Red) | DMRS (Blue) | Data (Red) | - -RB Resource Mapping for UL-SCH2 (Modulation = QPSK) diagram showing subcarriers 0-12 and symbols 0-13. It illustrates the mapping of data and DMRS signals for PRBs 1-5 in symbol 2. - -The TER will not request any other symbols from the O-RU in this test unless they are needed by the TER for synchronization. The C-Plane message describing symbol #2 should contain two sections with different section IDs. Only PRBs 1-5 will be used. The first section should only describe PRB 1 and have an reMask of 101010101010b. The second section should describe PRBs 2-5 and have an reMask of all ones. The two sections should have different section IDs. - -**Steps:** - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and the downlink U-Plane messages and trigger the source to play the RF signal on a frame boundary. -- Play messages to the O-RU respecting the timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the frame. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information from the captured U-Plane messages -- Extract IQ information from the signal analyser for downlink slots -- Extract Payload for both signals -- Compare payload binary sequences - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser in the downlink direction should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. (VOID) -3. The test frame received by the signal analyser in the downlink direction should only contain the same PN23 signals that were sent in the U-Plane only for PRBs 2-5. only DMRS signals should be in PRB1. -4. The test frame extracted from the uplink U-Plane messages should be the same as the uplink signal described above. In particular the U-Plane messages for PRBs 2-5 should contain user data as well as DMRS signals while PRB1 should only contain DMRS signals. - -### 3.2.5.1.6 UC-Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 6 3GPP DL/UL – Resource Allocation - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages with section extension 6, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink and interpret and capture the correct resource blocks in the uplink with section extension 6. This test uses a PN23 sequence in all test PDSCH sections. - -Using the standard TDD test frame described in clause 3.2.1.1.3 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the specified signal using section extension 6 in both uplink and downlink. - -In this test stock data section definition C will be used to exercise the non-contiguous RB allocation, all 273 PRBs (51 in the uplink slots) or the max number of PRBs per symbol for the highest numerology the radio supports will be used in this test. - -Only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All downlink user data in this test will be a PN23 sequence and all uplink user data will also be a PN23 sequence. - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.3 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause 3.2.1.1.3. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. - -The radio must support section extension 6 as notified by the M-Plane. The signal analyser must have the ability to decode the downlink shared channel. - -**C. Test Methodology** -**a. Initial Conditions** - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. Connect the signal source to the O-RU antenna port and configure it as described below. - -**b. Procedure** - -Build an appropriate IQ signal describing the signal described above in clause 3.2.1.1.3 in the CUSM emulator. In this case use a PN23 sequence for the downlink shared channel. Build the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the uplink and downlink signals. Every symbol other than the ones used in the test should either be allocated with user data or left unallocated (empty). If allocated with user data, they may be described by either a single or multiple sections (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -**For the downlink slots and symbols:** Only symbols number 6 and 7 will be used in each slot. Other symbols may be used in this test or be left unallocated (unused). However other symbols containing reference signals may be used to ensure the O-RU can synchronize with the TER. The starting PRB will be zero and number of PRBs will be chosen from one or more columns in Table 3.2.5-1 below. The resource block group size will be 16 based on ETSI TS 138.214 Table 5.1.2.2.1-1 as shown in Table 3.2.5-1 below using configuration 2. - -**Table 3.2.5-1 RBG Size.** - -| Bandwidth Part Size | Configuration 1 | Configuration 2 | -|---------------------|-----------------|-----------------| -| 1 – 36 | 2 | 4 | -| 37 – 72 | 4 | 8 | -| 73 – 144 | 8 | 16 | -| 145 – 275 | 16 | 16 | - -Using the calculations in clause 7.7.6 of [2] for the test waveform described above, the ID of the last RBG will be 17, f(0) will be 16, f(n) will be 16 and f(lastRbgID) will be 1 (17 total RBGs). StartPrbc will be zero and numPrbc will be 273. If the radio does not support this numerology the following table will apply. The number of PRBs correspond to Table 3.2.5-2. - -**Table 3.2.5-2 Stock Data Sections.** - -| # PRBs per Symbol (11-79) | | | | | | | | | | | -|---------------------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|---------| -| max PRB/sym | 11 | 24 | 25 | 32 | 50 | 51 | 52 | 65 | 66 | 79 | -| numPRBc | 11 | 24 | 25 | 32 | 50 | 51 | 52 | 65 | 66 | 79 | -| rbgSize | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| lastRbgID | 2 | 5 | 6 | 7 | 6 | 6 | 6 | 8 | 8 | 4 | -| f(0) | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| f(n) | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| f(lastRbgID ) | 3 | 4 | 1 | 4 | 2 | 3 | 4 | 1 | 2 | 15 | -| rbgMask (Hex) | 000000
5 | 000003
D | 000007
D | 00000F
D | 000007
D | 000007
D | 000007
D | 00001F
D | 00001F
D | 000001D | - -| # PRBs per Symbol (100-273) | | | | | | | | | | | -|-----------------------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------| -| max PRB/sym | 100 | 106 | 107 | 132 | 133 | 135 | 162 | 217 | 270 | 273 | -| numPRBc | 100 | 106 | 107 | 132 | 133 | 135 | 162 | 217 | 270 | 273 | -| rbgSize | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| lastRbgID | 6 | 6 | 6 | 8 | 8 | 8 | 10 | 13 | 16 | 17 | -| f(0) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| f(n) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| f(lastRbgID) | 4 | 10 | 11 | 4 | 5 | 7 | 2 | 9 | 14 | 1 | -| rbgMask (Hex) | 000007
D | 000007
D | 000007
D | 00001F
D | 00001F
D | 00001F
D | 00007F
D | 0003FF
D | 001FFF
D | 003FFF
D | - -Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal. If the symbols other than the ones under test (symbol #6 and #7) have user data allocated, these symbols should be described by a single or multiple type 1 section (DL-SCH and DCI) except symbols #6 and #7 which will be used for the section extension 6 test. The data in symbol #6 should be a new PN23 sequence starting in the first PRB and continuing to PRB 273 (RBG number 17). Symbol #7 should be identical to symbol #6. The rbgMask value should be set to 0x003FFFD and the symbolMask value should be set to 00000011000000b. No Section Type zero messages will be used for this test. - -The O-DU emulator will build a U-Plane message containing the PN23 IQ data for the first 16 PRBs (RBG 0), this message will have the section ID used in the C-Plane message described above. Another U-Plane message will be created using the same section ID but with the PN23 data for RBGs 2-17 in it. The same U-Plane messages will be used for symbol #7. - -**For the uplink sections and symbols:** For this test symbols number 6 and 7 will be used in each slot. The starting PRB will be zero and number of PRBs will be 51. The resource block group size will be 8. Using the calculations in clause 7.7.6 of [2], the ID of the last RBG will be 6, f(0) will be 8, f(n) will be 8 and f(lastRbgID) will be 3. Every symbol should be described by a single type 1 section (DL-SCH and DCI) except symbols #6 and #7 which will be used for the section extension 6 test. Symbol number 6 will be a guard symbol in the flexible slot if the TDD configuration according to Table 3.2.1.1 is used, so only 2 uplink slots per frame are possible. If needed, another symbol than symbol number 6 can be selected. The data in symbol #6 is expected to be a new PN23 sequence starting in the first PRB and continuing to PRB 51 (RBG number 6). Symbol #7 should be identical to symbol #6. The rbgMask value should be set to 0x000007D and the symbolMask value should be set to 00000011000000b. No Section Type zero messages will be used for this test. If the radio only supports another numerology see the tables above in the downlink sections and symbols for appropriate modifications. - -#### Steps: - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and the downlink U-Plane messages and trigger the source to play the RF signal on a frame boundary. -- Play messages to the O-RU respecting the timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the frame. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information from the captured U-Plane messages -- Extract IQ information from the signal analyser for downlink slots - -- Extract Payload for both signals -- Compare payload binary sequences - -#### **D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser in the downlink direction should satisfy a basic 3GPP signal performance requirement for this radio category (*i.e.* EVM). -2. (VOID) -3. The test frame received by the signal analyser in the downlink direction should be the same as the signal described above. If it contains all the same PRB assignments and the correct PN23 sequence as data, the downlink test passes. -4. The test frame extracted from the uplink U-Plane messages should be the same as the uplink signal described above. If it contains all the same PRB assignments and the correct PN23 sequence as data, the uplink test passes. - -### **3.2.5.1.7 UC- Plane O-RU Scenario Class Extended 3GPP DL/UL – Resource Allocation – Coupling C and U plane via time and frequency** - -#### **A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can meet the extended uplink and downlink requirements for O-RAN fronthaul using a TDD signal. This test uses time and frequency to couple C-Plane and U-Plane messages. - -Using the standard TDD test frame described in clause 3.2.1.1.3 the O-DU emulator (*i.e.* O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the default signal. - -The purpose of this test is to ensure the radio can transmit and receive an extended 3GPP TDD test frame using the default parameters in clause 3.2.1.1.3 of this document (or a similar 3GPP waveform) except only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All downlink user data in this test will be a PN23 sequence and all uplink user data will also be a PN23 sequence. The radio must report over the M-Plane that it supports C and U plane coupling via time and frequency. - -#### **B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.3 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described by TM-FR1-TM1.1. It will be for 5G New Radio only. The radio must report over the M-Plane that it supports C and U plane coupling via time and frequency. - -The O-RU must have a conducted antenna port (or TAB connector) to be connected to a signal analyser and signal source. It must also support the default parameters defined in clause 3.2.1.1.1 above. - -#### **C. Test Methodology** - -##### ***a. Initial Conditions*** - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. - -**b. Procedure** - -Build an appropriate IQ signal describing the signal described above in clause 3.2.1.1.3 in the CUSM emulator. In this case use a PN23 sequence for the downlink shared channel. Build the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the uplink and downlink signals. Every symbol used in the test should be described by a single section (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. All section IDs in C-Plane messages and downlink U-Plane messages must be 4095. - -C-Plane and Downlink U-Plane messages sent by the TER will have valid values in the following fields: - -- EAxC ID -- Datadirection bit -- Frame ID, subframeID, slotID, startsymbolID, and NumSymbol -- SectionID must have a value 4095 -- SymInc, rb reMask and section extension #6 are *not* used in this test - -It is the responsibility of the TER to properly arrange uplink U-Plane messages using only time and frequency resources. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. All received U-Plane messages must have section ID equal to 4095 -3. The test frame received by the signal analyser should be the same as the signal described above. If it contains all the same PRB assignments and PN23 sequence data, the test passes. - -### 3.2.5.1.8 UC- Plane O-RU Scenario Class Extended 3GPP DL/UL – Coupling C and U plane via Time and Frequency and Section Description Priorities - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to test whether the radio can implement coupling U and C plane via time and frequency and section description priorities requirements for O-RAN fronthaul using a TDD signal. This test combines the FDD, uplink and downlink tests for these same features. Note, there are two versions of this feature: coupling C and U plane messages via frequency and time and Section Description Priorities and coupling C and U plane messages via frequency and time and Section Description Priorities (optimized). This test requires both tests to be performed if the radio supports both methods otherwise only one test is to be performed in the radio only supports one of these methods. These methods are listed under test methodology below. - -Starting with the standard TDD test frame described in clause 3.2.1.1.3 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the signals described below. - -Only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All downlink user data in this test will be a PN23 sequence and all uplink user data will also be a PN23 sequence. - -## B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.3 of this document and those specified below. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described by TM-FR1-TM1.1. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. It will be a TDD signal. - -The O-RU must have a conducted antenna port (or TAB connector) to be connected to a signal analyser and signal source. It must also support the default parameters defined in clause 3.2.1.1.1 above. - -## C. Test Methodology - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. - -### b. Procedure for Coupling C and U plane messages via frequency and time with section priorities - -Build an appropriate C and U plane signals for the signals described below in the CUSM emulator. Every slot used in the test should be described by a single C-Plane message with multiple sections (DL-SCH that are used for the test, DMRS and DCI) using a Section Type 1 message. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -- Downlink procedure: - -**Table 3.2.5-3 Time and Frequency Coupling with Priority TDD DL.** - -| # | Section ext 6 | priority | symbolMask | startPrbc | numPrbc | reMask | rbgMask | beamId | numSymbol | Note | -|---|---------------|----------|---------------------------------------------------------------------------------------------------------|-----------|---------|---------------|------------|--------|-----------|-------------------------------| -| 1 | yes | +1 | 000000000000100 | 0 | 192 | 010001000100 | 0xFFFFFC00 | 1 | 1 | CSI reference signal (CSI-RS) | -| 2 | yes | +1 | 001000000000000 | 0 | 192 | 010001000100 | 0xFFFFFC00 | 2 | 1 | CSI reference signal (CSI-RS) | -| 3 | no | 0 | 111110000000000

Not used in this section without section extension 6. Just shown for information | 0 | 273 | 1111111111111 | N/A | 100 | 5 | UE1 | -| 4 | yes | 0 | 000000000001100 | 15 | 32 | 1111111111111 | 0x6000000 | 200 | 2 | UE2 | -| 5 | no | 0 | 00000111110000

Not used in this section without section extension 6. Just shown for information | 31 | 48 | 1111111111111 | N/A | 300 | 5 | UE3 | -| 6 | no | 0 | 000000000000011

Not used in this section without section extension 6. Just shown for information | 10 | 2 | 1111111111111 | N/A | 3 | 2 | Special channel | - -In this test the section configuration will be as shown in Table 3.2.5-3 above. The 6 sections will comprise one slot and this slot will be repeated continuously in the downlink slots in the TDD frame to synchronize the TER signal analyser. The six sections will be sent on one C-Plane message using C and U plane coupling via time and frequency. The configuration above follows the example given in the CUSM specification. - -The section numbers in the above table do not represent SectionID numbers but individual sections. Sections #1 and #2 describe hypothetical CSI-RS signals sent in symbols #2 and #11 in each slot. These signals have sub-carriers masked by reMask. The CSI-RS signals generation follows ETSI TS 138.211 V16.2.0 (or after), clause 7.4.1.5 with nID = 0, row 1, N=1 and L=1. These sections use section extension 6 and contain a higher priority than all other sections. - -Section #3 describes PN23 data sent to hypothetical UE #1 it overlaps REs in sections #1 and #2 but has a lower priority so sections #1 and #2 are valid. Since section #3 has contiguous symbols section extension 6 is not needed. - -Section #4 is for hypothetical UE #2. It shares symbol 2 with the CSI-RS signal in Section #1. Since the symbols are not contiguous it uses sections extension 6 but the priority is set to the default 0. - -Section #5 is for hypothetical UE #3 and uses a contiguous set of symbols so section extension 6 is not needed. It does not overlap any other signals. It shares symbol 2 with the CSI-RS signal in Section #1. This section is optional because it does not test Section Description Priority. - -Section #6 is a hypothetical special channel using two symbols and does not require section extension 6. This section is also optional. - -U-Plane messages will contain: - -- CSI-RS signals as described by section #1 for symbol #2 -- CSI-RS signals as described by section #2 for symbol #11 -- A new PN23 sequence in each of the last 5 symbols as described in section #3. Note that for symbol #11 the PN sequence will be pierced by the CSI-RS signals. -- A new PN23 sequence for symbol #2 as described by section #4 as well as a new PN sequence for symbol #3. These sequences are only 32 PRBs long and start in PRB 15. The sequence in symbol #2 will be pierced by CSI-RS signals. -- The user data for sections number #5 and #6 are standard PN23 sequences only for these symbols and PRBs described in the table above. - -**c. Procedure for Coupling C and U plane messages via frequency and time with section priorities (optimized)** - -This test will be identical to the above test with the following exceptions: - -- There will be two C-Plane messages describing the uplink and downlink signals to be sent. -- The first two sections listed in the table above (those with higher priorities) will be repeated in both C-Plane messages and will have a section ID equal to a value between 0 and “max-highest-priority-sections-per-slot” as sent on the M-Plane. -- The other sections will be divided between the two C-Plane messages and not repeated. -- The repeated C-plane message will have the “repetition” bit set to one. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser must be the same as the signal described above. It must contain all the same PRB assignments and PN23 sequences. -3. (VOID) -4. The beamweights or magnitude and phase relation at the antenna ports (or TAB connectors) of the test signal that achieves the highest performance (i.e. best EVM, power, SNR, etc.) should match with the manufacturer’s declaration of the beam under test. The procedure for test case 3.2.3.2.3 (UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Predefined-beam Beamforming) should be used. -5. These expected results are applicable for either or both forms of this test. -6. If all of the above results are observed the test passes. - -### 3.2.5.1.9 UC-Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 12 3GPP DL/UL – Resource Allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages with section extension 12, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink and interpret and capture the correct resource blocks in the uplink with section extension 12. This test uses a PN23 sequence in all test PDSCH sections. - -Using the standard TDD test frame described in clause 3.2.1.1.3 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the specified signal using section extension 12 in both uplink and downlink. - -In this test stock data section definition C will be used to exercise the non-contiguous RB allocation, all 273 PRBs (48 of the 51 in the uplink slots) or the max number of PRBs per symbol for the highest numerology the radio supports will be used in this test. - -Only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All downlink user data in this test will be a PN23 sequence and all uplink user data will also be a PN23 sequence. - -#### B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.3 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause 3.2.1.1.3. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. - -The radio must support section extension 12 as notified by the M-Plane. The signal analyser must have the ability to decode the downlink shared channel. - -#### C. Test Methodology - -##### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. Connect the signal source to the O-RU antenna port and configure it as described below. - -##### b. Procedure - -Build an appropriate IQ signal as described above in clause 3.2.1.1.3 in the CUSM emulator. In this case use a PN23 sequence for the downlink shared channel. Build the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the uplink and downlink signals. Every symbol used in the test should be described by a single section (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for - -receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -**For the downlink slots and symbols:** Only symbols number 6 and 7 will be used in each slot. Other symbols may contain data including reference signals to ensure test equipment can synchronize with the signal. The starting PRB will be zero and number of PRBs will be chosen from one or more columns I Table 3.2.5-4 below. The resource block group size will be 16 based on ETSI TS 138.214 Table 5.1.2.2.1-1 as shown in Table 3.2.5-4 below using configuration 2. - -**Table 3.2.5-4 Resource Block Group Size.** - -| Bandwidth Part Size | Configuration 1 | Configuration 2 | -|---------------------|-----------------|-----------------| -| 1 – 36 | 2 | 4 | -| 37 – 72 | 4 | 8 | -| 73 – 144 | 8 | 16 | -| 145 – 275 | 16 | 16 | - -Using the calculations in clause 7.7.6 of [2] for the test waveform described above, the ID of the last RBG will be 17, f(0) will be 16, f(n) will be 16 and f(lastRbgID) will be 1 (17 total RBGs). StartPrbc will be zero and numPrbc will be 273. If the radio does not support this numerology the following table will apply. The number of PRBs correspond to Table 3.2.5-5. - -**Table 3.2.5-5 Stock Data Sections.** - -| # PRBs per Symbol (11-79) | | | | | | | | | | | -|---------------------------|----|----|----|----|----|----|----|----|----|----| -| max PRB/sym | 11 | 24 | 25 | 32 | 50 | 51 | 52 | 65 | 66 | 79 | -| numPRBc | 11 | 24 | 25 | 32 | 50 | 51 | 52 | 65 | 66 | 79 | -| rbgSize | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| lastRbgID | 2 | 5 | 6 | 7 | 6 | 6 | 6 | 8 | 8 | 4 | -| f(0) | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| f(n) | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| f(lastRbgID) | 3 | 4 | 1 | 4 | 2 | 3 | 4 | 1 | 2 | 15 | - -| # PRBs per Symbol (100-273) | | | | | | | | | | | -|-----------------------------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| -| max PRB/sym | 100 | 106 | 107 | 132 | 133 | 135 | 162 | 217 | 270 | 273 | -| numPRBc | 100 | 106 | 107 | 132 | 133 | 135 | 162 | 217 | 270 | 273 | -| rbgSize | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| lastRbgID | 6 | 6 | 6 | 8 | 8 | 8 | 10 | 13 | 16 | 17 | -| f(0) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| f(n) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| f(lastRbgID) | 4 | 10 | 11 | 4 | 5 | 7 | 2 | 9 | 14 | 1 | - -Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal. Every symbol should be described by a single type 1 section (DL-SCH and DCI) except symbols #6 and #7 which will be used for the section extension 12 test. The data in symbol #6 should be a new PN23 sequence starting in the first PRB and continuing to PRB 273 (RBG number 17). Symbol #7 should be identical to symbol #6. The symMask value should be set to 00000011000000b. No Section Type zero - -messages will be used for this test. The relevant parameters for the downlink C-Plane message are shown in Figure 3.2.5.1-53 below: - -![Diagram of downlink C-Plane parameters showing a grid of PRBs across 13 symbols. Symbols 0-5 are blank. Symbols 6 and 7 contain user data in the last 16 PRBs. Symbols 8-13 are blank. A symMask is shown below the symbols. Brackets on the left indicate RBG groupings: 241 PRBs for 16 RBGs, and two separate 16 PRB groups for RBG 0 and RBG 1.](aac1229a97a38498dda01631625b7bdd_img.jpg) - -**Section Extension 12 (273 PRBs)** - -**Section Header** -startSymbolId = 0 - -**SectionId** -startPrbc = 0 -numPrbc = 16 - -**Section Extension 6** -offStartPrb(1) = 16 -numPrb(1) = 241 - -Grey cells are user data, White cells are unallocated PRBs - -| | | | | | | | | | | | | | | | -|--|----------|----------|----------|----------|----------|----------|-----------|-----------|----------|----------|-----------|-----------|-----------|-----------| -| | Symbol 0 | Symbol 1 | Symbol 2 | Symbol 3 | Symbol 4 | Symbol 5 | Symbol 6 | Symbol 7 | Symbol 8 | Symbol 9 | Symbol 10 | Symbol 11 | Symbol 12 | Symbol 13 | -| | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | -| | Blank | Blank | Blank | Blank | Blank | Blank | User Data | User Data | Blank | Blank | Blank | Blank | Blank | Blank | - -symMask - -Diagram of downlink C-Plane parameters showing a grid of PRBs across 13 symbols. Symbols 0-5 are blank. Symbols 6 and 7 contain user data in the last 16 PRBs. Symbols 8-13 are blank. A symMask is shown below the symbols. Brackets on the left indicate RBG groupings: 241 PRBs for 16 RBGs, and two separate 16 PRB groups for RBG 0 and RBG 1. - -**Figure 3.2.5.1-53 Downlink C-Plane Parameters** - -The O-DU emulator will build a U-Plane message containing the PN23 IQ data for the first 16 PRBs (RBG 0), this message will have the section ID used in the C-Plane message described above. Another U-Plane message will be created using the same section ID but with the PN23 data for RBGs 2-17 in it. The same U-Plane messages will be used for symbol #7. - -**For the uplink sections and symbols:** For this test symbols number 6 and 7 will be used in each slot. The starting PRB will be zero and number of PRBs will be 48. The resource block group size will be 16. Using the calculations in clause 7.7.6 of [2], the ID of the last RBG will be 17, f(0) will be 16, f(n) will be 16 and f(lastRbgID) will be 1. - -Every symbol should be described by a single type 1 section (DL-SCH and DCI) except symbols #6 and #7 which will be used for the section extension 6 test. The data in symbol #6 is expected to be a new PN23 sequence starting in the first PRB and continuing to PRB 48 (RBG number 2). Symbol #7 should be identical to symbol #6. The symMask value should be set to 00000011000000b. No Section Type zero messages will be used for this test. If the radio only supports another numerology see the tables above in the downlink sections and symbols for appropriate modifications. The relevant parameters for the uplink C-Plane message are shown in Figure 3.2.5.1-54 below: - -![Diagram of uplink C-plane parameters showing a grid of PRBs across 14 symbols. Symbols 0-5 are blank. Symbols 6-7 contain user data in the last 16 PRBs. Symbols 8-13 are blank. A bracket on the left groups the last 16 PRBs of symbols 6, 7, and 8 as '16 PRB - 1 RGB'. A bracket at the bottom spans all 14 symbols as 'symMask'.](74cab8aa3cac8c33efc20cc187916544_img.jpg) - -### Section Extension 12 (48 PRBs) - -**Section Header** -startSymbolId = 0 - -**SectionId** -startPrbc = 0 -numPrbc = 16 - -**Section Extension 6** -offStartPrb(1) = 16 -numPrb(1) = 16 - -Grey cells are user data, White cells are unallocated PRBs - -| | | | | | | | | | | | | | | | -|-----------------|----------|----------|----------|----------|----------|----------|-----------|-----------|----------|----------|-----------|-----------|-----------|-----------| -| | | | | | | | | | | | | | | | -| | | | | | | Blank | Blank | | | | | | | | -| 16 PRBs – 1 RGB | Blank | Blank | Blank | Blank | Blank | Blank | User Data | User Data | Blank | Blank | Blank | Blank | Blank | | -| 16 PRB – 1 RGB | | | | | | | Blank | Blank | | | | | | | -| 16 PRB – 1 RGB | | | | | | | User Data | User Data | | | | | | | -| | Symbol 0 | Symbol 1 | Symbol 2 | Symbol 3 | Symbol 4 | Symbol 5 | Symbol 6 | Symbol 7 | Symbol 8 | Symbol 9 | Symbol 10 | Symbol 11 | Symbol 12 | Symbol 13 | -| | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | -| | symMask | | | | | | | | | | | | | | - -Diagram of uplink C-plane parameters showing a grid of PRBs across 14 symbols. Symbols 0-5 are blank. Symbols 6-7 contain user data in the last 16 PRBs. Symbols 8-13 are blank. A bracket on the left groups the last 16 PRBs of symbols 6, 7, and 8 as '16 PRB - 1 RGB'. A bracket at the bottom spans all 14 symbols as 'symMask'. - -Figure 3.2.5.1-54 Uplink C-Plane Parameters - -**Steps:** - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and the downlink U-Plane messages and trigger the source to play the RF signal on a frame boundary. -- Play messages to the O-RU respecting the timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the frame. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information from the captured U-Plane messages -- Extract IQ information from the signal analyser for downlink slots -- Extract Payload for both signals -- Compare payload binary sequences - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser in the downlink direction should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. (VOID) -3. The test frame received by the signal analyser in the downlink direction should be the same as the signal described above. If it contains all the same PRB assignments and the correct PN23 sequence as data, the downlink test passes. -4. The test frame extracted from the uplink U-Plane messages should be the same as the uplink signal described above. If it contains all the same PRB assignments and the correct PN23 sequence as data, the uplink test passes. - -### 3.2.5.1.10 UC-Plane O-RU Scenario Class Static SRS Allocation UL – Resource Allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the O-RU can support static SRS configuration through the M-Plane. This is an uplink only test so there is no corresponding downlink test for TDD. The O-RU must report through the M-Plane that it supports static configuration of SRS. - -This test will use the standard TDD test frame described in clause 3.2.1.1. The test will have the CUSM emulator configure the O-RU, through the M-Plane, with a section of time/frequency resources reserved for static uplink SRS, these will be limited to the uplink slots of the TDD frame. The signal source will be programmed to send simulated SRS signals in a subset of those resources. The O-RU should receive this SRS signals and pass them through to the CUSM emulator using U-Plane messages. Note, there will be no C-Plane messages sent from the CUSM emulator and the O-RU. The signal generator will signal power levels at least 30 dB above Reference Sensitivity power Level described in TS 138.141-1 Table 7.2.5-1. This is to improve the likelihood that all data will be received by the radio correctly since we are not interested in testing receiver sensitivity but only the O-RAN protocol compliance. The placement of the time frequency resources is not specified in this test so it may be placed in any uplink slots of the TDD frame. - -The TER (Test Equipment, O-RU) generates an uplink SRS signal on the antenna connector or TAB connector. The TER will capture the U-Plane messages generated by the DUT and validate whether the payload matches the uplink signal as well as beam characteristics. The metric used to validate that the signal received by the CUSM emulator matches the signal sent by the signal generator will be EVM as described in Annex H.7 of ETSI TS 138.141. While some 3GPP test documents (e.g. ETSI TS 138.521 clause 6.4.2.1.3) suggest treating the EVM requirements for physical Zadoff-Chu sequences such as PRACH the same as QPSK for EVM requirements, this document will decrease the required EVM to the level specified for 64 QAM. The purpose of this is to ensure that there is no chance of false positives where a random, mistaken signal sent by the O-RU closely mimics the test signal used by the TER. Since there are no impairments made to the uplink SRS signal this should be well within the capabilities of the O-RU. - -#### B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.3 of this document. The O-RU must indicate it supports static SRS allocation. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. Note - -this signal may be changed to any of the 3GPP sensitivity test signals in ETSI TS 138.141-1 if the radio does not support the numerology and bandwidth used in this test. The test signal described in this clause will be used if the radio supports that numerology and bandwidth. - -## C. Test Methodology - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal source to the O-RU antenna port and configure the source to transmit the required SRS test signal upon receiving a trigger signal from the CUSM-E. The signal source power level should be adjusted to at least 30 dB above the setting used in the 3GPP receiver sensitivity test. - -Implicit in this Initial set up is statically configuring O-RU with a section of time/frequency resources for static SRS signals. - -### b. Procedure - -- Build an SRS signal in the signal generator that fits in the preconfigured time frequency resources set in the initial configuration. -- Load the waveform into the signal source: -- Configure signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that signals the start of a frame boundary. -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port connected -- TER will arrange U-Plane messages according to time and frequency -- Start SRS waveform generation on the signal generator. Ensure the test frame is repeated enough times to generate a statistically significant number of SRS occasions. That is at least 10 occasions. -- Extract IQ information -- Calculate EVM of the SRS signal received by the CUSM emulator to the ideal signal generated by the signal source. Use the method described in ETSI TS 138.141 Annex H.7 to perform the calculation. - -## D. Test Requirement (expected result) - -1. The verdict is “Test pass” if the calculated EVM is less than 8% as median EVM measured over the minimum number of SRS occasions of at least 10 occasions. -2. If any of the test conditions are not true, the verdict for the whole test is "Fail" - -### 3.2.5.1.11 UC Plane O-RU Base Class TDD Test UL – Static PRACH allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the O-RU can support static PRACH configuration through the M-Plane. This is an uplink only test so there is no corresponding downlink test for downlink slots. The O-RU must report through the M-Plane that it supports static configuration of PRACH. The concept is to repeat the spirit of test 3.2.3.8.1 (5GNR PRACH test) without sending any C-Plane type 3 messages and configuring the O-RU using only the M-Plane. - -TER will setup the signal generator with a PRACH test waveform according to ETSI TS 138.211 clause 6.3.3, ETSI TS 138.141-1 clause 8.4.1 and A.6. The test waveform will contain the same preamble ID for every occasion repeated by following the timing offset scheme specified in the figures 8.4.1.4.2-2 or 8.4.1.4.2-3 ETSI TS 138.141-1 depending on the selected PRACH format. - -This is an example for FR1 – SCS=30 kHz – BW=100MHz – Format A3 configuration index 132 (From Table 6.3.3.2-3, unpaired spectrum), on each occasion the time offset of the same preamble index (selected according to Table A.6-1 ETSI TS 138.141.1) is incremented by 100nsec starting from 0 up to 800nsec (9 occasions per frame). Each PRACH occasion is at the beginning of the first nine used sub-frames. The scheme is repeated every frame. The test must be conducted using a PRACH format and configuration index the radio has reported it supports. - -| # | Enabled | Power Boosting | Timing Offset | PRACH Format | Preamble Index | Logical Root Sequence Index (i) | Sequence Number (u) | Cyclic Shift Index (v) | Cyclic Shift (Cv) | Frame Offset | Subframe Index | n_RA_f | n_RA_slot | n_RA_f | Occasion Index | RA_RNTI | -|---|---------|----------------|---------------|--------------|----------------|---------------------------------|---------------------|------------------------|-------------------|--------------|----------------|--------|-----------|--------|----------------|---------| -| 0 | ✓ | 0.00 dB | 0 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 8 | -| 1 | ✓ | 0.00 dB | 100 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 22 | -| 2 | ✓ | 0.00 dB | 200 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 2 | 0 | 0 | 0 | 2 | 36 | -| 3 | ✓ | 0.00 dB | 300 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 3 | 0 | 0 | 0 | 3 | 50 | -| 4 | ✓ | 0.00 dB | 400 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 4 | 0 | 0 | 0 | 4 | 64 | -| 5 | ✓ | 0.00 dB | 500 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 5 | 0 | 0 | 0 | 5 | 78 | -| 6 | ✓ | 0.00 dB | 600 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 6 | 0 | 0 | 0 | 6 | 92 | -| 7 | ✓ | 0.00 dB | 700 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 7 | 0 | 0 | 0 | 7 | 106 | -| 8 | ✓ | 0.00 dB | 800 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 8 | 0 | 0 | 0 | 8 | 120 | - -![A screenshot of a signal analysis tool showing a frequency vs. time plot. The y-axis represents Frequency (MHz) ranging from -61.44 to 61.44. The x-axis represents Time (ms) ranging from 0 to 10. There are several horizontal pink lines representing PRACH signals at different time intervals, corresponding to the timing offsets in the table above. A legend in the top right corner indicates 'PRACH' with a pink square.](e34a4d5cbb54d3807859f61780076592_img.jpg) - -A screenshot of a signal analysis tool showing a frequency vs. time plot. The y-axis represents Frequency (MHz) ranging from -61.44 to 61.44. The x-axis represents Time (ms) ranging from 0 to 10. There are several horizontal pink lines representing PRACH signals at different time intervals, corresponding to the timing offsets in the table above. A legend in the top right corner indicates 'PRACH' with a pink square. - -Figure 3.2.5.1-55 FR1 SCS 30Kz 100MHz Format A3, Unpaired Spectrum, configuration index 132 - -According to the PRACH waveform setting, the TER will generate a corresponding sequence of M-Plane messages which include the following parameters (According to the M-Plane specification and the PRACH configuration index supported): - -- grouping static-prach-configuration -- leaf pattern-period - "Period after which static PRACH patterns are repeated. Unit: number of frames." -- leaf guard-tone-low-re - "Number of REs occupied by the low guard tones." -- leaf num-prach-re - "Number of contiguous PRBs per data section description" -- leaf guard-tone-high-re - "Number of REs occupied by the high guard tones." -- leaf sequence-duration - "Duration of single sequence of the PRACH. Sequence may be considered as "single PRACH symbol"" -- list prach-patterns - key prach-pattern-id - "Provides a PRACH pattern. Each record in the list represents a single PRACH occasion. Number of list entries cannot exceed max-prach-patterns" - - leaf prach-pattern-id - "Supplementary parameter acting as key for prach-pattern list." - - leaf number-of-repetitions - "This parameter defines number of PRACH repetitions in PRACH occasion, to which the section control is applicable" - - leaf number-of-occasions - "This parameter informs how many consecutive PRACH occasions is described by the PRACH Pattern" - - leaf re-offset – "Offset between the start of the lowest-frequency RE of the lowest frequency PRB and the start of the lowest frequency RE belonging to the PRACH occasion. The re-offset is configured as number of PRACH REs." - - list occasion-parameters – "list of cp-lengths, gp-lengths and beam-ids applicable per each PRACH occasion in PRACH pattern." - -**NOTE:** the number of records in this list MUST be equal to value of parameter number-of-occasions. - -- leaf occasion-id - "Supplementary parameter acting as key in *'occasion-parameters'* list" -- leaf cp-length - "Cyclic prefix length. See CUS-Plane specification for detailed description." -- leaf gp-length - "Guard period length." -- leaf beam-id - "This parameter defines the beam pattern to be applied to the U-Plane data. -beamId = 0 means no beamforming operation will be performed." -- leaf frame-number - "This parameter is an index inside the pattern-length, such that PRACH occasion is happening for SFN which fulfils following equation: $[\text{SFN mod pattern-length} = \text{frame-id}]$ " -- leaf sub-frame-id - "Identifier of sub-frame of the PRACH occasion. Value is interpreted in the same way as subframeId field in a section description of a C-Plane message." -- leaf time-offset - "This parameter defines the time-offset from the start of the sub-frame to the start of the first Cyclic Prefix of PRACH pattern" - -By the corresponding U-Plane messages in the uplink direction, the TER will try to detect the presence of the corresponding preamble at the expected timing offset and calculate the probability of detection $P_d$ according to the definition in TS38.141-1 clause 8.4.1.1. - -The signal will be exercised at only one O-RU port without adding any external AWGN power level or multipath fading profile and at a power level avoiding detection errors due to poor SNR (rule described in the sub-section C of this scenario class). - -The test will have the CUSM emulator configure the O-RU, through the M-Plane, with a section of time/frequency resources reserved for static uplink PRACH. The default is the PRACH configuration described in 3GPP above, but the test may be conducted with changes if the radio does not support those exact configurations. The signal source will be programmed to send simulated PRACH signals in those resources. The O-RU should receive this PRACH signal and pass them through to the CUSM emulator using U-Plane messages. Note, there will be no C-Plane messages sent from the CUSM emulator and the O-RU. - -## B. Test Entrance Criteria - -O-RU must have a conducted antenna port (FR1) or TAB connector. - -By the M-plane or by manufacturer declaration, TER will detect all the supported SCSs, FFT sizes and carrier bandwidths by the O-RU. It is assumed that only one combination of the three above parameters supported by the O-RU is enough to validate the test. TER will choose the format either according to the PRACH Configuration Index in ETSI TS 138.211 clause 6.3.3 Table 6.3.3.2-2 and the available frequency resource, or according to the manufacturer declaration item D.103 “PRACH format and SCS” in ETSI TS 138.141-1 or according to the format information obtained by the M-plane in case O-RU implements this feature. TER shall generate M-Plane messages conformant to the selected format. If more formats are claimed, only one shall be selected to reduce the test time, preference will be given to a format specified in Table A.6.1 ETSI TS 138.141. It is assumed that the O-RU manufacturer will support at least one in that table. For the case of long preambles, it is assumed format 0 is always supported since this is the only one shown in the Table A.6-1 ETSI TS 138.141. - -## C. Test Methodology - -### a: Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal source to the O-RU antenna - -port and configure the source to transmit the required PRACH test signal upon receiving a trigger signal from the CUSM-E. - -Implicit in this Initial set up is statically configuring O-RU with a section of time/frequency resources for static PRACH signals. - -**b: Procedure** - -- Set signal generator power to at least 30 dB above the setting used in the 3GPP receiver sensitivity test described in ETSI TS 138.141-1 clause 7.2.5. -- Set signal generator frequency offset to the central carrier frequency. PRACH will be mapped over frequency according to *msg1-FrequencyStart* ( $n_{RA}^{start}$ ) parameter equal to 0. PRACH format is set according to what TER has selected from the manufacturer declarations. -- Start PRACH waveform generation on the signal generator. Ensure the test frame is repeated enough times to generate a statistically significant number of PRACH occasions. That is at least 10 occasions. -- TER will perform PRACH detection per each PRACH occasion in each frame sent and compare the result with the expected preamble ID and the expected timing offset. Since the external AWGN and fading generator are not present the time error tolerance should be low, TER will use the time error tolerance in Table 8.4.1.1-1 for AWGN case according to the corresponding PRACH format and PRACH SCS. A counter of successful detections is incremented at every matching. The probability of detection is given by the ratio between that counter and the number of the expected received PRACH occasions within the test time. -- Repeat the test procedure by setting *msg1-FrequencyStart* ( $n_{RA}^{start}$ ) parameter to the right edge of the configured carrier bandwidth in order to exercise a different frequency offset number - -**D. Test Requirement (expected result)** - -1. Test is pass if the probability of detection is 100% determined across the minimum amount of at least 10 occasions. - -### 3.2.5.1.12 UC Plane O-RU Scenario Class Extended using section extension 13 for frequency hopping UL/DL – Resource Allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to validate the capability of the O-RU to correctly interpret section extension 13, frequency hopping, for the uplink. Note, since frequency hopping is only used in uplink in 5G NR this test will be limited to the uplink slots of the basic TDD signal. - -Using the standard TDD test frame described in clause 3.2.1.1.3 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink of the specified signal using section extension 13 for the uplink. The downlink portion of the test is not part of this test and may be any signal or no downlink signal at all. - -In this test stock data section definition C will be used to exercise the non-contiguous RB allocation, all 273 PRBs (48 of the 51 in the uplink slots) or the max number of PRBs per symbol for the highest numerology the radio supports will be used in this test. - -Only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). - -## B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.3 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause 3.2.1.1.3. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. - -The radio must support section extension 13 as notified by the M-Plane. The signal analyser must have the ability to decode the downlink shared channel. - -## C. Test Methodology - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. Connect the signal source to the O-RU antenna port and configure it as described below. - -### b. Procedure - -Build an appropriate IQ signal as described above in clause 3.2.1.1.3 in the CUSM emulator. In this case use a PN23 sequence for the downlink shared channel. Build the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the uplink and downlink signals. Every symbol used in the test should be described by a single section (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -**For the downlink slots and symbols:** Any signal may be used if needed by the TER or no downlink signal may be used. - -**For the uplink sections and symbols:** Load uplink test waveform (G-FR1-A1-5 : SCS130k\_51RB) on the RF signal source. Note this signal should contain a new PN23 sequence as user data in PRBs 0 through 50 for symbol 6 and PRBs 100 through 151 for symbol 7. This will be copied for all uplink slots. The remainder of the test waveform is as described in 3GPP. Configure signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that C-Plane messages have been sent. Load a C-Plane message on Test Equipment O-RU (TER) – Use the O-DU emulator control interface to build the appropriate C-Plane message that describes this uplink signal. This section should have startSymbolId = 6, numPrbc = 51, and section extension 13 attached. The section extension should have nextSymbolId = 7 and nextStartPrbc = 100. - -### Steps: - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and the downlink U-Plane messages (if needed) and trigger the source to play the RF signal on a frame boundary. -- Play messages to the O-RU respecting the timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to - -demodulate and decode the frame. - -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information from the captured U-Plane messages -- Extract IQ information from the signal analyser for downlink slots (if needed) -- Extract Payload for both signals -- Compare payload binary sequences - -#### D. Test Requirement (expected result) - -1. (VOID) -2. The verdict is “Test pass” if the test frame extracted in the uplink direction-contains two U-Plane messages for this section ID one containing the PN23 sequence for the first 51 PRBs in symbol 6 and PRBs 100 through 151 for symbol #7 containing the PN23 sequence sent by the signal source for those PRBs. - -### 3.2.5.2 UC-Plane O-RU Scenario Class Beamforming (BFM) - -This clause describes the beamforming conformance testing for O-RAN fronthaul interface. The tests do not aim to test the O-RU beamforming performance or capabilities but to test that the O-RU under test focuses the RF energy or sensitivity into a specific direction and with a specific granularity following the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) C-Plane messages. - -Unless stated otherwise in a test case, the following statements apply to all the test cases defined in this clause: - -- It is based on conducted testing with a setup such as described in clause 2.1 and it only applies to O-RU DUTs that have conducted antenna ports or TAB connectors. -- It applies to Category A and Category B O-RU DUTs. -- It applies to LTE and/or 5G New Radio O-RU DUTs. In both cases, precoding is not required in any test case. -- If O-RU DUT supports Analog Beamforming (i.e. time domain beamforming), all the U-Plane test frames are defined by segmenting the Stock Test A: 1 section per symbol. The definition of this Stock Test A can be found in Figure 3.2.1.1-4 and the description accompanying this figure. Each slot shall include multiple sections (one per symbol within the slot) and only one beam at a time (i.e. one beamId at a time) and therefore only one beam can be tested per slot. -- If O-RU DUT supports Digital Beamforming (i.e. frequency domain beamforming), all the U-Plane test frames are defined by segmenting the Stock Test B: 2 sections per symbol definition as shown in Figure 3.2.1.1-4. Each slot shall include multiple sections (two per symbol within the slot) and only one beam per section at a time (i.e. one beamId at a time) and therefore up to two different beams can be tested per slot. -- If O-RU DUT supports multiple polarizations, it is up to the TER to determine if the testing is carried out for each polarization separately or multiple polarizations at the same time. In any case, it is important to guarantee that the correct eAxC\_ID for the correct polarization (or polarizations) is exercised. -- For O-RU DUT that support TDD: - - The tests may use any combination of Downlink and Uplink standard 3GPP LTE test frames found in clause 6.1.1.1 of ETSI TS 136.141-1. - -- For example, the following TDD test waveform could be used for this test: - - 20MHz bandwidth with 100 RBs assigned - - Uplink/Downlink Configuration set to 3 - - Special Subframe Configuration set to 8 - - DwPTS Length set to 11 Symbols - - GP lengths set to 1 Symbol - - UpPTS Length set to 2 Symbols. -- The full test radio frame is shown in Figure 3.2.5.2-56. - -![Figure 3.2.5.2-56: Combined DL and UL TDD 20 MHz 100 RB. The figure shows a time-frequency grid representing a radio frame. The horizontal axis represents time (symbols) and the vertical axis represents frequency (subcarriers). The frame is divided into slots, each containing 14 symbols. The slots are color-coded: red for Downlink (DL), green for Uplink (UL), and grey for Guard Period (GP). The pattern shows a mix of DL and UL slots, with some slots containing both DL and UL symbols separated by a GP. The overall structure is a TDD frame with a specific DL/UL configuration.](c27f535a48e7cdba6653c484181b3e32_img.jpg) - -Figure 3.2.5.2-56: Combined DL and UL TDD 20 MHz 100 RB. The figure shows a time-frequency grid representing a radio frame. The horizontal axis represents time (symbols) and the vertical axis represents frequency (subcarriers). The frame is divided into slots, each containing 14 symbols. The slots are color-coded: red for Downlink (DL), green for Uplink (UL), and grey for Guard Period (GP). The pattern shows a mix of DL and UL slots, with some slots containing both DL and UL symbols separated by a GP. The overall structure is a TDD frame with a specific DL/UL configuration. - -Figure 3.2.5.2-56 Combined DL and UL TDD 20 MHz 100 RB - -If 20MHz is not supported by the O-RU DUT, then it will use the highest bandwidth supported by the O-RU DUT. - -- For O-RU DUT that support 5G NR: - - The tests will use a combination of Downlink and Uplink standard 3GPP 5G NR test frames. See figure. - - The Downlink part of the radio frame will use a standard 3GPP NR-FR1-TM1.1 test frame for TDD in [19] (clause 4.9.2 TS138.141-1) of the Conducted Transmitter Characteristic Test (clause 6 TS138.141-1) as described in clause 3.2.1.1. The test numerology will be preferably 30kHz subcarrier spacing and 100 MHz Bandwidth. If not supported, then it will use any other supported subcarrier spacing and the highest bandwidth of the O-RU DUT. - - The Uplink part of the radio frame will use a standard 3GPP Reference Sensitivity level definition (clause 7.2 and Annex A TS138.141-1) of the Conducted Receiver Characteristic Test (clause 7 ETSI TS 138.141) and power levels at least 30dB above Reference Sensitivity power level as described in clause 3.2.1.1. The test numerology will be preferably 30kHz subcarrier spacing and 100 MHz Bandwidth, if supported. Otherwise, it will use any available subcarrier space and the highest bandwidth supported by the O-RU DUT. - - The Downlink symbols are allocated at slots 0 to 7 and 10 to 17. - - The Uplink symbols are allocated at slots 7 to 9 and 17 to 19. - - Note that slots 7 and 17 have symbols allocated for Downlink, symbols 0 to 5, some other symbols assigned as Guard Period where no signal is transmitted or expected to be received, symbols 6 to 9, and finally some other symbols allocated for Uplink, symbols 10 to 13. -- The O-RU DUT: - - supports the default parameters in clause 3.2.1.1.1 of this document. - - has installed current release of shipping software. - - has at least two conducted antenna ports (or TAB connectors) to be connected to a signal analyser. Likewise, it must have at least two conducted antenna ports or TAB connectors to be connected to a signal generator. - - is fully calibrated up to the antenna ports or (TAB connectors) (if needed). It is expected to be calibrated by O-RU vendor prior to testing. - -- The TER: - - is capable of carrying out any signal processing required to generate and demodulate 3GPP compliant waveforms. - - is able to calculate or extract beamweights (or magnitude and phase relations) between antenna ports or TAB connectors. Alternatively, and if the O-RU DUT manufacturer provides the list of beam directions supported by the O-RU DUT, TER might calculate or extract the beam direction instead of the beamweights. - - is able to generate and deliver signals with the required beamweights (or magnitude and phase relations) at the antenna ports or TAB connectors. - - is fully calibrated up to the interfaces where is connected to the O-RU DUT antenna ports (or TAB connectors). For that, a known test signal might be either injected by the TER into the O-RU DUT, or internally generated by the O-RU DUT, and the O-RU DUT must not apply any digital or analogue beamweights to the known test signal. One possible method to perform calibration uses injected C-Plane and U-Plane signals from TER into the O-RU and using C-Plane messages with beamID=0. -- The O-DU emulator of the TER: - - is capable of generating and sending U-Plane messages containing 3GPP test frames following the corresponding Stock sectioning defined above, as well as be capable of capturing U-Plane messages and extracting 3GPP test frames (i.e. IQ data) from the captured U-Plane messages. - - is capable of generating the C-Plane messages for, receiving, extracting and demodulating the 3GPP test frames following the corresponding Stock sectioning defined above. -- For DMRS-BF tests, the TER setup modifications are: - - RF Signal Generator / System which can be a combination of test equipment, or an integrated one, that provides all the testing capabilities needed: - - RF Signal Generator capable of generating wanted signals (3GPP compliant SU-MIMO and MU-MIMO signals). - - RF Signal Generator capable of generating Additive white Gaussian Noise and Interference signals. It can be a single device or multiple devices. - - Beamformer to apply beam weights to each of the signals under tests - - CUSM-Plane emulator with expanded capability: - - is able to operate with and without reference Channel Estimation (CE) and Equalization (EQ) over the received signal from DUT (Uplink direction). - -NOTE: The definition of the reference algorithms used for Channel Estimation and Equalization in the TER are not specified in the current document. - -- is capable of measuring and reporting EVM measurements after CE and EQ if receiving unequalised IQ data (when testing O-RU DUT with DMRS-BF-NEQ), or directly from received equalized IQ data (when testing O-RU DUT with DMRS-BF-EQ), -- is capable of measuring and reporting BER and/or BLER measurements of the received signal from DUT (Uplink direction) after demapping and decoding, - -NOTE: The definition of the reference algorithms used for demapping and decoding in the TER are not specified in the current document. - -- is capable of parsing ST9 and ST10 messages to extract SINR and RRM measurements. - -![Figure 3.2.5.2-2: Test Equipment set up for testing O-RU DUT with DMRS-BF. The diagram shows a 'Test Equipment, RU (TER) for DMRS-BF' box containing a 'CUSM-Plane Emulator' and an 'RF Signal Generator / System'. The 'CUSM-Plane Emulator' is connected to the 'DUT = O-RU' via 'FH' (Fronthaul) and 'RF' (Radio Frequency) links. The 'RF Signal Generator / System' is connected to the 'DUT' via 'RF' links. The 'CUSM-Plane Emulator' includes a 'Layer de-mapping + decoder' which outputs 'BER' and 'BLER'. It also includes 'Channel Estimation + Equalization + Combiner' which outputs 'EVM', 'SINR', and 'RRM'. The 'RF Signal Generator / System' includes a 'Signal Generator Wanted Test Signals' and an 'AWGN & Interference Generator' which are combined and sent to the 'DUT' via a 'Beamformer'.](230151de787f38fa96749379eafb9f37_img.jpg) - -Figure 3.2.5.2-2: Test Equipment set up for testing O-RU DUT with DMRS-BF. The diagram shows a 'Test Equipment, RU (TER) for DMRS-BF' box containing a 'CUSM-Plane Emulator' and an 'RF Signal Generator / System'. The 'CUSM-Plane Emulator' is connected to the 'DUT = O-RU' via 'FH' (Fronthaul) and 'RF' (Radio Frequency) links. The 'RF Signal Generator / System' is connected to the 'DUT' via 'RF' links. The 'CUSM-Plane Emulator' includes a 'Layer de-mapping + decoder' which outputs 'BER' and 'BLER'. It also includes 'Channel Estimation + Equalization + Combiner' which outputs 'EVM', 'SINR', and 'RRM'. The 'RF Signal Generator / System' includes a 'Signal Generator Wanted Test Signals' and an 'AWGN & Interference Generator' which are combined and sent to the 'DUT' via a 'Beamformer'. - -Figure 3.2.5.2-2 Test Equipment set up for testing O-RU DUT with DMRS-BF - -- The TER might have less testing ports than the O-RU DUT conducted antenna ports (or TAB connectors) if testing is carried out sequentially; or as many antenna ports as the number of conducted antenna ports (or TAB connectors) under test if testing is carried out simultaneously. -- It is up to the TER on how to extract the beamweights (or magnitude and phase relation) between the antenna ports or TAB connectors, or the beam direction / properties, in order to match it with the manufacturer's declaration. -- The user payload will be generated as PN23 with a seed of all ones. -- It applies to the following O-RAN CUS Specification [2]: - - Clause 7.4 - - Clause 8.3.2 - - Clause 8.3.3 - - Clause 12 - - Annex J - -### 3.2.5.2.1 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – No Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with no beamforming (beamId=0x000) and with one spatial stream (single eAxC). - -#### B. Test Entrance Criteria - -- Manufacturers' declaration that defines list of magnitude and phase relation (or beamweights) between antenna ports or TAB connectors and/or beam directions with antenna array characteristics when O-RU DUT is operating with no beamforming. - -#### C. Test Methodology - -**a. Initial Conditions** - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal analyser to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- a. Build an appropriate IQ signal described above in the O-DU emulator. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (DL-SCH and DCI) using Section Type 1 messages. Section type zero messages will be used to signal Guard Period resources in the test waveform. -- c. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause. -- d. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. -- e. Extract either the beamweights, or magnitude and phase relation, or beam direction from the measured signal. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The signal relation (i.e. beamweights, or magnitude and phase relation) between antenna ports or TAB connectors, or the extracted beam direction, should match the expected relation, or beam direction, for the expected no beamforming within a tolerance defined by the manufacturer. - -### 3.2.5.2.2. UC-Plane O-RU Scenario Class Beamforming 3GPP UL – No Beamforming - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with no beamforming (beamId=0x000) and with one spatial stream (single eAxC). - -**B. Test Entrance Criteria** - -- Manufacturers' declaration that defines list of magnitude and phase relation (or beamweights) between antenna ports or TAB connectors and/or beam directions with antenna array characteristics when O-RU DUT is operating with no beamforming. - -**C. Test Methodology** - -**a. Initial Conditions** - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal source to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the source with any set-up information needed to allow it to synch and generate the test signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -#### b. Procedure - -- a. Build an appropriate test signal described above in the signal source of the TER. -- b. Inject the test signal into the O-RU with the application of an initial set of beamweights, or equivalently magnitude and phase relation, between all the TER ports connected to the antenna ports (or TAB connectors) to emulate the phase and magnitude difference “seen” by the antenna elements under test. For example, initial beamweights could be set to be “all equal” (i.e. no beamforming). -- c. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (UL-SCH) using Section Type 1 messages. -- d. Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. while also triggering the signal source. -- e. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. -- f. Repeat the previous steps but now in step b apply a different set of beamweights or phase relation between all the antenna ports (or TAB connectors) when injecting the test signal into the O-RU. For example, repeating the process for a number of different beamweights will simulate the reception of the test signal from different beam directions. This allows to determine if the O-RU is really focusing the sensitivity to the correct beam direction. - -#### D. Test Requirement (expected result) - -1. The test frame received by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -2. The beamweights or magnitude and phase relation at the antenna ports (or TAB connectors) of the test signal that achieves the highest performance (i.e. best EVM, power, SNR, etc.) should match with the manufacturer’s declaration of the phase relation expected for no beamforming. - -### 3.2.5.2.3 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Predefined-beam Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with predefined-beams beamforming (beamId≠0x000) and with one spatial stream (single eAxC). - -The transmitted beam direction is measured for each indexed beam required in this measurement, see below. The measured transmitted direction is compared to manufacturer-designated direction. Transmitted direction could be defined by the phase relation between the antenna ports or TAB connectors under test, or directly by extracting the beam direction. - -Depending on the O-RU beamforming capabilities regarding the ability to generate “coarse”, “fine” and/or “beam groups”, as defined in clause 12.4.2.2 of [2]. - -The elevation $\theta$ and azimuth $\Phi$ angles are defined as in [2] clause 10.4.1.1: - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Predefined-beam Beamforming conformance test might include multiple tests that the O-RU must comply: - -**a. “Coarse” beamIds test:** - -If O-RU supports and reports beamIds that are defined as coarse granularity (coarse beamIds) to the O-DU emulator, the test should include the following beams: - -1. A coarse beam with 0 degrees azimuth ( $\Phi$ ) and elevation ( $\theta$ ) angles. -2. A coarse beam with maximum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -3. A coarse beam with maximum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). -4. A coarse beam with minimum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -5. A coarse beam with minimum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). - -If the O-RU only supports one azimuth ( $\Phi$ ) or elevation angle ( $\theta$ ), fewer than 5 beam angles will be measured. - -**b. “Fine” beamIds test:** - -If O-RU supports and reports beamIds that are defined as fine granularity (fine beamIds) to the O-DU emulator, the test should include the following beams: - -1. A fine beam with 0 degrees azimuth ( $\Phi$ ) and elevation ( $\theta$ ) angles. -2. A fine beam with maximum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -3. A fine beam with maximum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). -4. A fine beam with minimum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -5. A fine beam with minimum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). - -If the O-RU only supports one azimuth or elevation angle, fewer than 5 beam angles will be measured. - -**c. “beam-group” beamIds test:** - -If O-RU supports and reports beamIds that belong to same and different beam-groups to the O-DU emulator, the test should include the following beams: - -1. All beams that belong to a beam-group with 0 degrees azimuth ( $\Phi$ ) or elevation ( $\theta$ ) angles. -2. All beams that belong to a beam-group with maximum supported azimuth angle ( $\Phi$ ). -3. All beams that belong to a beam-group with minimum supported azimuth angle ( $\Phi$ ). -4. All beams that belong to a beam-group with maximum supported elevation angle ( $\theta$ ). -5. All beams that belong to a beam-group with minimum supported elevation angle ( $\theta$ ). - -If the O-RU only supports one azimuth or elevation angle, fewer than 5 beam-groups will be measured. - -## B. Test Entrance Criteria - -- Manufacturers’ defined list of beam indices and their associated magnitude and phase relation between antenna ports or TAB connectors and/or beam directions with antenna array characteristics. - -## C. Test Methodology - -**a. Initial Conditions** - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal analyser to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- a. Build an appropriate IQ signal described above in the O-DU emulator. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (DL-SCH and DCI) using Section Type 1 messages. -- c. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- d. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. -- e. Extract either the beamweights, or magnitude and phase relation, or beam direction from the measured signal. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The signal relation (i.e. beamweights, or magnitude and phase relation) between antenna ports or TAB connectors, or the extracted beam direction, should match the expected relation, or beam direction, corresponding to the beam under test within a tolerance defined by the manufacturer. - -**3.2.5.2.4 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Predefined-beam Beamforming****A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with predefined-beams beamforming (beamId≠0x000) and with one spatial stream (single eAxC). - -The same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.2.3 applies, but instead it is related to the uplink direction. - -**B. Test Entrance Criteria** - -- Manufacturers' defined list of beam indices and their associated magnitude and phase relation between antenna ports or TAB connectors and/or beam directions with antenna array characteristics. - -**C. Test Methodology** - -**a. Initial Conditions** - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal source to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the source with any set-up information needed to allow it to synch and generate the test signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- a. Build an appropriate test signal described above in the signal source of the TER. -- b. Inject the test signal into the O-RU with the application of an initial set of beamweights, or equivalently magnitude and phase relation, between all the TER ports connected to the antenna ports (or TAB connectors) to emulate the phase and magnitude difference “seen” by the antenna elements under test. For example, initial beamweights could be set to be “all equal” (i.e. no beamforming). -- c. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (UL-SCH) using Section Type 1 messages. -- d. Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. while also triggering the signal source. -- e. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. -- f. Repeat the previous steps but now in step b apply a different set of beamweights or phase relation between all the antenna ports (or TAB connectors) when injecting the test signal into the O-RU. For example, repeating the process for a number of different beamweights will simulate the reception of the test signal from different beam directions. This allows to determine if the O-RU is really focusing the sensitivity to the correct beam direction. - -**D. Test Requirement (expected result)** - -1. The test frame received by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -2. The beamweights or magnitude and phase relation at the antenna ports (or TAB connectors) of the test signal that achieves the highest performance (i.e. best EVM, power, SNR, etc.) should match with the manufacturer’s declaration of the beam under test. - -### 3.2.5.2.5 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Weight-based Dynamic Beamforming - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with weight-based dynamic beamforming with one spatial stream (single eAxC). - -The transmitted beam direction is measured for each weighted beam required in this measurement, see below. The measured transmitted direction is compared to manufacturer-designated direction. Transmitted direction could be defined by the phase relation between the antenna ports or TAB connectors under test, or by directly extracting the beam direction. - -The elevation $\theta$ and azimuth $\Phi$ angles are defined in clause 12.4.2.2 of [2]. - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Weight-based Dynamic Beamforming conformance test should evaluate the following beams for the O-RU to comply: - -- a. A weight-based beam with 0 degrees azimuth ( $\Phi$ ) and elevation ( $\theta$ ) angles. -- b. A weight-based beam with maximum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -- c. A weight-based beam with maximum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). -- d. A weight-based beam with minimum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -- e. A weight-based beam with minimum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). - -If the O-RU only supports one azimuth ( $\Phi$ ) or elevation angle ( $\theta$ ), fewer than 5 beam angles will be measured. - -The user/tester selects the bitwidth for the mantissa or scaler of the compression method applied to the beams. The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Weight-based Dynamic Beamforming conformance test should also evaluate the following compression methods for each of the supported beams described above (a. to e.) for the O-RU to comply: - -- a. No compression method applied to the beamforming weights. -- b. Block floating point compression method applied to the beamforming weights with the selected number of bit mantissa. -- c. Block scaling compression method applied to the beamforming weights with the selected number of bit scaler. -- d. $\mu$ -law compression method applied to the beamforming weights with the selected number of bit fixed width. -- e. Depending on what type of Beamspace compression the DUT supports, either Beamspace compression method applied to the beamforming weights with the selected number of bit scaler, or Beamspace compression method applied to the beamforming weights with the selected number of bit mantissa. - -If the O-RU does not support all the compression methods described above, fewer than 5 compression methods will be measured. - -## B. Test Entrance Criteria - -- Manufacturers' defined list of frequency domain ( $\phi$ ) and or time domain ( $\theta$ ) weights for each supported beam, or alternatively, list of gain and phase relation, or complex beam weights, between antenna ports or TAB connectors for each supported beam. Also, the O-RU needs to report to the O-DU the antenna array characteristics. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. - -- Connect the signal analyser to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- Build an appropriate IQ signal described above in the O-DU emulator. -- Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by one or two sections (DL-SCH and DCI) using Section Type 1 messages, the sections in the first symbol of the slot will contain section extension extType=0x01 to convey the beam weights, it is not required that the next sections contain extension type 1 since the same beam IDs will not change along the slot. If O-RU does not support a field, then its value should be 0x0. -- Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. -- Extract either the beamweights, or magnitude and phase relation, or beam direction from the measured signal. - -**D. Test Requirement (expected result)** - -- The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -- The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -- The signal relation (i.e. beamweights, or magnitude and phase relation) between antenna ports or TAB connectors, or the extracted beam direction, should match the expected relation, or beam direction, corresponding to the beam under test within a tolerance defined by the manufacturer. - -**3.2.5.2.6 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Weight-based Dynamic Beamforming** - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with weight-based beamforming and with one spatial stream (single eAxC). - -The same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.2.5 but applies to the uplink direction. - -**B. Test Entrance Criteria** - -- Manufacturers' defined list of frequency domain ( $\phi$ ) and or time domain ( $\theta$ ) weights for each supported beam, or alternatively, list of gain and phase relation, or complex beam weights, between antenna ports or TAB connectors for each supported beam. Also, the O-RU needs to report to the O-DU the antenna array characteristics - -**C. Test Methodology** - -#### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal source to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the source with any set-up information needed to allow it to synch and generate the test signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -#### b. Procedure - -- Build an appropriate test signal described above in the signal source of the TER. -- Inject the test signal into the O-RU with the application of an initial set of beamweights, or equivalently magnitude and phase relation, between all the TER ports connected to the antenna ports (or TAB connectors) to emulate the phase and magnitude difference “seen” by the antenna elements under test. For example, initial beamweights could be set to be “all equal” (i.e. no beamforming). -- Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by one or two sections (UL-SCH) using Section Type 1 messages, the sections in the first symbol of the slot will contain section extension extType=0x01 to convey the beam weights, it is not required that the next sections contain extension type 1 since the same beam IDs will not change along the slot. If O-RU does not support a field, then its value should be 0x0. -- Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. while also triggering the signal source. -- Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. -- Repeat the previous steps but now in step b apply a different set of beamweights or phase relation between all the antenna ports (or TAB connectors) when injecting the test signal into the O-RU. For example, repeating the process for a number of different beamweights will simulate the reception of the test signal from different beam directions. This allows to determine if the O-RU is really focusing the sensitivity to the correct beam direction. - -#### D. Test Requirement (expected result) - -1. The test frame received by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -2. The beamweights or magnitude and phase relation at the antenna ports (or TAB connectors) of the test signal that achieves the highest performance (i.e. best EVM, power, SNR, etc.) should match with the manufacturer’s declaration of the beam under test. - -### 3.2.5.2.7 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Attribute-based Dynamic Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with attributed-based dynamic beamforming with one spatial stream (single eAxC). - -If the O-RU DUT supports Attribute based Dynamic Beamforming, this test is mandatory for the O-RU DUT to be O-RAN conformant. - -The transmitted beam direction and attributes are measured for each attributed beam required in this measurement, see below. The measured transmitted direction and attributes, i.e. pointing azimuth and elevation angles, beamwidths and sidelobe suppression, is compared to manufacturer-designated direction and attributes. Transmitted direction and beam attributes are defined by the magnitude and phase relation between the antenna ports or TAB connectors under test, or by directly extracting the beam properties. - -The elevation $\theta$ and azimuth $\Phi$ angles are defined in clause 12.4.2.2 of [2]. - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Attribute-based Dynamic Beamforming conformance test should evaluate the following beams for the O-RU to comply: - -- a. An attribute-based beam with 0 degrees azimuth ( $\Phi$ ) and elevation ( $\theta$ ) angles with any beamwidth and sidelobe suppression supported by the O-RU under this beam direction. -- b. An attribute-based beam with maximum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ) with the widest beamwidth and lowest sidelobe suppression supported for this specific beam direction. -- c. An attribute-based beam with maximum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ) with the narrowest beamwidth and highest sidelobe suppression supported for this specific beam direction. -- d. An attribute-based beam with minimum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ) with the widest beamwidth and lowest sidelobe suppression supported for this specific beam direction. -- e. An attribute-based beam with minimum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ) with the narrowest beamwidth and highest sidelobe suppression supported for this specific beam direction. - -If the O-RU only supports one azimuth ( $\Phi$ ) or elevation angle ( $\theta$ ), fewer than 5 beam angles and attribute configurations will be measured. - -## B. Test Entrance Criteria - -- Manufacturers' defined list of supported beam directions (azimuth $\phi$ and elevation $\theta$ angles) attributes that are supported by the O-RU and their associated gain and phase relation, or complex weight, between antenna ports or TAB connectors and/or beam directions with antenna array characteristics. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal analyser to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -#### b. Procedure - -- a. Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by one or two sections (DL-SCH and DCI) using Section Type 1 messages, the sections in the first symbol of the slot will contain section extension extType=0x02 to convey the beam weights, it is not required that the next sections contain extension type 2 since the same beam IDs will not change along the slot. If O-RU does not support a field, then its value should be 0x0. -- c. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- d. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. -- e. Extract either the beamweights, or magnitude and phase relation, or beam properties from the measured signal. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The signal relation (i.e. beamweights, or magnitude and phase relation) between antenna ports or TAB connectors, or the extracted beam properties, should match the expected beam properties corresponding to the beam under test within a tolerance defined by the manufacturer. - -### 3.2.5.2.8 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Attribute-based Dynamic Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with attribute-based beamforming with one spatial stream (single eAxC). - -Same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.2.7 but considering uplink direction. - -#### B. Test Entrance Criteria - -- Manufacturers' defined list of supported beam directions (azimuth $\phi$ and elevation $\theta$ angles) attributes that are supported by the O-RU and their associated gain and phase relation, or complex weight, between antenna ports or TAB connectors and/or beam directions with antenna array characteristics - -#### C. Test Methodology - -##### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. - -- Connect the signal source to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the source with any set-up information needed to allow it to synch and generate the test signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- Build an appropriate test signal described above in the signal source of the TER. -- Inject the test signal into the O-RU with the application of an initial set of beamweights, or equivalently magnitude and phase relation, between all the TER ports connected to the antenna ports (or TAB connectors) to emulate the phase and magnitude difference “seen” by the antenna elements under test. For example, initial beamweights could be set to be “all equal” (i.e. no beamforming). -- Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by one or two sections (UL-SCH) using Section Type 1 messages, the sections in the first symbol of the slot will contain section extension extType=0x02 to convey the beam weights, it is not required that the next sections contain extension type 2 since the same beam IDs will not change along the slot. If O-RU does not support a field, then its value should be 0x0. -- Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. while also triggering the signal source. -- Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. -- Repeat the previous steps but now in step b apply a different set of beamweights or magnitude and phase relation between all the antenna ports (or TAB connectors) when injecting the test signal into the O-RU. For example, repeating the process for a number of different sets of beamweights will simulate the reception of the test signal from different beam directions. This allows to determine if the O-RU is really focusing the sensitivity to the correct beam properties. - -**D. Test Requirement (expected result)** - -1. The test frame received by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -2. The beamweights or magnitude and phase relation at the antenna ports (or TAB connectors) of the test signal that achieves the highest performance (i.e. best EVM, power, SNR, etc.) should match with the manufacturer’s declaration of the beam under test. - -**3.2.5.2.9 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Channel-Information-based Beamforming** - -**A. Test Description and Applicability** - -This Test is **CONDITIONAL MANDATORY**. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with channel-information-based beamforming with multiple spatial streams from multiple users (i.e. MU-MIMO). - -For Category A radios, the test is for each polarization separately and consequently either different or same channel models can be defined for each of the polarization. For Category B, same channel might be used for both polarizations and the test might measure each polarization separately. - -The transmitted beam direction is measured for each scenario required in this measurement. The measured transmitted direction is extracted from the decoded received signal in the TER. Transmitted direction is defined by properly receiving a data transmission between the O-RU and the target User Equipment while destroying or heavily attenuating the data transmission between the O-RU and the other User Equipment. - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Channel-Information-based Beamforming conformance test should evaluate the following scenarios for the O-RU to comply and will rely on TER Channel Emulation capabilities as shown in Figure 3.2.5.2-57. - -![Figure 3.2.5.2-57 TER with Channel Emulation Capability](c4ce20d443c5793503265b1f68fe4536_img.jpg) - -The diagram illustrates the Test Equipment (RU (TER)) setup. It consists of nested boxes. The outermost box is labeled 'Test Equipment, RU (TER)'. Inside it is a box representing the 'DUT = O-RU'. Within the DUT box, there is a block for 'Precoding Matrix $G$ '. Two input signals, 'UE 0 Layer 0' and 'UE 1 Layer 0', enter from the left as 'eAxC 0' and 'eAxC 1' into the Precoding Matrix. The output of the Precoding Matrix is labeled with $M$ and passes into a 'Channel Emulator Matrix $H$ '. The output of the Channel Emulator Matrix is labeled with $2$ and results in two output signals: 'UE 0 Layer 0' and 'UE 1 Layer 0' on the right. - -Figure 3.2.5.2-57 TER with Channel Emulation Capability - -Figure 3.2.5.2-57 TER with Channel Emulation Capability - -A scenario where two spatial streams, or eAxC flows, are generated for two users (one layer each) with $M$ antenna ports or TAB connectors. The O-DU will report to the O-RU via C plane messages an emulated channel estimate. The emulated channel shall model a static channel, with rank not lower than the number of spatial streams, and it shall not be a block-diagonal channel. As an example, a Butler channel model could be implemented as emulated channel. The O-RU will calculate and apply the beamweight matrix in such that the received signal at the users is the same as the generated in the O-DU. It is up to the O-RU on how to calculate the beamforming weights, for example Zero-forcing, regularized zero-forcing / MMSE, etc. - -If O-RU supports Analog Beamforming (Time Domain Beamforming), the test should not apply any analogue beamforming or time domain beamforming. In this case, $M$ is not the number of antenna ports or TAB connectors but the number of TRX channels supported by the O-RU. - -## B. Test Entrance Criteria - -- The O-RU must have at least two TRX chains with conducted antenna ports (or TAB connectors) to be connected to a signal analyser. -- The TER equipment must either include a channel emulator between the O-RU antenna ports and the signal analyser or the signal analyser be capable of applying the required channel matrix being emulated between the O-RU and the users. -- Manufacturers' defined list of number of TRX chains and what antenna ports or TAB connectors are connected to each TRX chain. - -## C. Test Methodology - -**a. Initial Conditions** - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal analyser to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- Build an appropriate IQ signal described above in the O-DU emulator. -- Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. Every symbol should be described by either one or two sections (DL-SCH and DCI) using Section Type 5 and 6 messages. -- Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- Capture the test signals and pass them through a channel emulator or apply the signal processing required to emulate the channel under test. -- Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. - -**3.2.5.2.10 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Channel-Information-based Beamforming****A. Test Description and Applicability** - -This Test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with channel-information-based beamforming with multiple spatial streams from multiple users (i.e. MU-MIMO). - -Same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.2.10 but considering uplink direction. - -**B. Test Entrance Criteria** - -- The O-RU must have at least two TRX chains with conducted antenna ports (or TAB connectors) to be connected to a signal generator. -- The TER equipment must either include a channel emulator between the O-RU antenna ports and the signal generator or the signal generator be capable of applying the required channel matrix being emulated between the users and the O-RU. -- Manufacturers' defined list of number of TRX chains and what antenna ports or TAB connectors are connected to each TRX chain. - -**C. Test Methodology** - -**a. Initial Conditions** - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal source to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the source with any set-up information needed to allow it to synch and generate the test signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- Build an appropriate test signal described above in the signal source of the TER. -- Inject the test signals through a channel emulator or apply the required signal processing to emulate the channel under test. -- Inject the resulting test signals into the antenna ports (or TAB connectors). -- Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (UL-SCH) using Section Type 5 and 6. -- Play the C plane messages to the O-RU respecting timing windows described in clause 2.4. while also triggering the signal source. -- Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. - -**D. Test Requirement (expected result)** - -1. The test frame received by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. - -**3.2.5.2.11 UC- Plane O-RU Scenario Class Beamforming 3GPP UL – DMRS based Beamforming****A. Test Description and Applicability** - -This Test is CONDITIONAL MANDATORY, the condition being O-RUs that support either DMRS-EQ or DMRS-NEQ. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with Demodulation Reference Signal-based beamforming (DMRS-BF) with multiple spatial streams from multiple users (i.e. MU-MIMO) using Section Extension 24 (SE24). - -The UC-Plane O-RU Scenario Class Beamforming 3GPP UL – DMRS based Beamforming conformance test will rely on TER Beamforming capabilities as shown in Figure 3.2.5.2-3. - -![Figure 3.2.5.2-3: TER with Beamforming Capability. This block diagram shows the Test Equipment, RU (TER) containing a DUT = O-RU and an RF Signal Generator / System. The DUT contains a DMRS-BF block. The RF Signal Generator / System contains a Signal Generator and a Beamformer. Two UE layers (UE 0 Layer 0 DMRS 0 and UE 1 Layer 0 DMRS 1) are shown. The Signal Generator provides inputs to the Beamformer, which then connects to the DMRS-BF block via M antenna ports. The DMRS-BF block outputs eAxC 0 and eAxC 1 to the UE layers.](f58d0ddf50366f1a6f8965187cae3988_img.jpg) - -Figure 3.2.5.2-3: TER with Beamforming Capability. This block diagram shows the Test Equipment, RU (TER) containing a DUT = O-RU and an RF Signal Generator / System. The DUT contains a DMRS-BF block. The RF Signal Generator / System contains a Signal Generator and a Beamformer. Two UE layers (UE 0 Layer 0 DMRS 0 and UE 1 Layer 0 DMRS 1) are shown. The Signal Generator provides inputs to the Beamformer, which then connects to the DMRS-BF block via M antenna ports. The DMRS-BF block outputs eAxC 0 and eAxC 1 to the UE layers. - -Figure 3.2.5.2-3 TER with Beamforming Capability - -As defined in introduction of clause 3.2.5.2 UC-Plane O-RU Scenario Class Beamforming, each of the UE layer in Figure 3.2.5.2-3 shall use a standard 3GPP Reference Sensitivity level definition (clause 7.2 and Annex A TS138.141-1) of the Conducted Receiver Characteristic Test (clause 7 ETSI TS 138.141). The power levels shall be at least 30dB above Reference Sensitivity power level as described in clause 3.2.1.1. The test numerology will be preferably 30kHz subcarrier spacing and 100 MHz Bandwidth, if supported. Otherwise, it shall use any available subcarrier space, and the highest bandwidth supported by the O-RU DUT. In addition, the uplink test vector will be generated with UL-SCH in UL slots and allocated to the PRBs 0 to 50 truncated to the carrier bandwidth used for testing. - -![Figure 3.2.5.2-4: Example uplink test vector to be generated by RF signal generator for each UE layer. This is a bar chart showing the number of CRBs (μ = 1) across 21 slots. The y-axis ranges from 0 to 273. The x-axis shows slots 0 to 20. The chart indicates that UL-SCH is active in slots 8-10 and 18-20, with a value of approximately 50 CRBs in each of these slots. A legend in the top right corner shows a blue square for UL-SCH.](ea6540d4c2547bccfbbd4774c5b9ae94_img.jpg) - -Figure 3.2.5.2-4: Example uplink test vector to be generated by RF signal generator for each UE layer. This is a bar chart showing the number of CRBs (μ = 1) across 21 slots. The y-axis ranges from 0 to 273. The x-axis shows slots 0 to 20. The chart indicates that UL-SCH is active in slots 8-10 and 18-20, with a value of approximately 50 CRBs in each of these slots. A legend in the top right corner shows a blue square for UL-SCH. - -Figure 3.2.5.2-4 Example uplink test vector to be generated by RF signal generator for each UE layer - -Note that this test vector is defined for a Single Input Single Output (SISO) scenario. However, for this test, the test vector is expanded to evaluate the test scenario where two spatial streams, or eAxC flows, are scheduled at the same resource allocation for two users (with one layer each) and with M antenna ports or TAB connectors. The CUSM-Plane emulator will signal this test vector configuration using SE24 to the O-RU via C-plane messages the scheduling of the two ueIds, using Section Type 5 and Section Extension 10 with beamGroupType=10b or beamGroupType=11b depending on O-RU capabilities. The CUSM-Plane emulator will signal to the O-RU via C-Plane messages the UE symbol allocation as all fourteen symbols per slot. - -This test case does not test allocated IPN measurement (MEAS\_IPN\_ALLOC =DISABLED), antenna DMRS SNR (andDmrsSnr=0), transform precoding and self-assembly. The CUSM-Plane emulator shall assign and schedule the ueIds using any supported number of least significant bits of the ueId to indicate the layers within each user. If an O-RU supports ueId persistence, ueId persistence shall not be used “ueId-persistence-enabled=FALSE”. - -The CUSM-Plane emulator will inform the O-RU of the DMRS configurations for the two streams using Section Extension 24 with entryType 1 and 2. The two DMRS configurations are as follows: - -| | UE 0 Layer 0 (DMRS 0) | UE 1 Layer 0 (DMRS 1) | -|-----------------------------------------------------------|-----------------------|-----------------------| -| Ports | 1000 | 1002 | -| scrambling ID (n_{scid}) | 0 | 1 | -| Scrambling ID 0 () | 2 | 3 | -| Scrambling ID 0 () | 4 | 5 | -| DMRS Power Boosting | 3 dB | | -| UL DMRS Configuration | Type 1 | | -| DMRS Duration (maxLength) | len1 (Single Symbol) | | -| DMRS Additional Position (dmrs-AdditionalPosition) | 1+1 (2) | | -| UL Mapping Type | A | | -| l_0 | pos2 | | -| DMRS Uplink Transform Precoding r16 | False | | -| Transform Precoding | False | | - -Same DMRS signal can be used for all available polarizations. Each polarization might be measured separately. - -If O-RU supports any other beamforming, these shall not be exercised and tested. If O-RU supports Analog Beamforming (Time Domain Beamforming), the test should not apply any analogue beamforming or time domain beamforming. In this case, $M$ is not the number of antenna ports or TAB connectors but the number of TRX channels supported by the O-RU. - -The configuration of DMRS and UE data layers follows configuration in SE 24. For example, there are two layers with two different DMRS configurations to measure in this scenario, two users with one layer each. A successful received layer is defined as properly receiving data transmission at the O-DU emulator side from a corresponding layer transmitted by a User Equipment. This received data transmission shall be successfully received when it matches the DMRS configuration being signalled to the O-RU. - -## B. Test Entrance Criteria - -- The O-RU shall have at least two TRX chains with conducted antenna ports (or TAB connectors) to be connected to a signal generator. -- The O-RU shall support enough entry tables of DMRS configuration to process the test vector and configuration under test. -- The TER equipment shall either include a beamformer between the O-RU antenna ports and the UE signal generator or the signal generator be capable of emulating different AoA for different UE. This AoA should ensure sufficient conditioning / rank of the channel matrix, ensuring that both UE layers can be properly inferred by O-RU during channel estimation and equalization. -- The TER equipment is responsible for generating the RF signals for each UE layer as described in Section A, the corresponding matching O-RAN fronthaul traffic with Section ST5, SE10 and SE24 and the configuration of the DUT via M-Plane. - -- Manufacturers' defined list of number of TRX chains and what antenna ports or TAB connectors are connected to each TRX chain. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -- Connect the signal source to the O-RU antenna ports or TAB connectors that belong to the beam under test and configure the source with any set-up information needed to allow it to synch and generate the test signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- Build an appropriate test signal described in Section A in the signal source of the TER. -- Inject the test signals through a beamformer or apply the required signal processing to the layers under test. -- Get the resulting test signals ready to be injected into the antenna ports (or TAB connectors). -- Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test using Section Type 5 with Section Extension 10 and Section Extension 24. -- Play the C-plane messages to the O-RU respecting timing windows described in clause 2.4. while also triggering the signal source so the signal is injected into the antenna ports (or TAB connectors). -- Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U-plane messages to the O-DU emulator. -- Allow for the O-DU emulator to capture the U-Plane messages sent by the O-RU and to run the following measurements on the extracted IQ data for each of the users/layers: - - if O-RU implements DMRS-BF-EQ: - - EVM of the received equalized IQ data (no channel estimation and equalization are used in TER). - - BER or BLER of the received equalized IQ data after layer demapping and decoding in the TER. -NOTE 1: The measured BER or BLER depends on the algorithms implemented in both the O-RU DUT and the O-DU TER. -NOTE 2: The algorithms for demapping and decoding to be used in TER are left for future study. - - if O-RU implements DMRS-BF-NEQ: - - EVM of the received non-equalized IQ data after the channel estimation and equalization operation in the TER. -NOTE 3: The measured EVM depends on the algorithms implemented in both the O-RU DUT and the O-DU TER. -NOTE 4: The algorithms for channel estimation and equalization to be used in TER are left for future study. - - BER or BLER of the received non-equalized IQ data after Channel Estimation, equalization, layer demapping and decoding in the TER. -NOTE 5: The measured BER or BLER depends on the algorithms implemented in both the O-RU DUT and the O-DU TER. -NOTE 6: The algorithms for demapping and decoding to be used in TER are left for future study. - - demodulate, decode and extract the payload. - -## D. Test Requirement (expected result) - -The test frame received by the TER/O-DU emulator for each of the users/layers should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data (payload before channel encoding in the transmission and after channel decoding in the reception). - -Report EVM and BER or BLER measured during the test. - -### 3.2.5.2.12 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – DMRS based Beamforming about Symbol reordering - -#### A. Test Description and Applicability - -This Test is CONDITIONAL MANDATORY; the test condition is O-RU that support either DMRS-EQ or DMRS-NEQ supports SE 25 and at least one symbol reordering method as well. - -The Section Extension 25 applies to Section Type 5 with dataDirection bit = 0 and uses with Section Extension 24 which provides DMRS configuration information. - -Same description and criteria for selecting the beams to be tested applies as in clause 3.2.5.2.11.A, but considering O-RU supports SE 25 and symbol reordering capability. CUSM-Plane emulator configures symbol reordering method and config-symb-reorder-upSymbId-type based on O-RU capability via M-Plane. - -**Table 3.2.5.2.12-1: O-RAN symbol reordering related features** - -| Feature | O-DU support | O-RU support | Additional Information | -|-------------------------------------------------------------------------------------------|--------------------------|--------------------------|---------------------------------------------------------------------| -| Per-window symbol reordering
When sending of port reduced
DRMS data is enabled | Conditional
Mandatory | Conditional
Mandatory | Condition for O-DU and O-RU: any
reordering method is supported. | -| Per-window symbol reordering
When sending of port reduced
DRMS data is disabled | Optional | Optional | This is relevant to DMRS-BF. | -| Per-section tx-window
reassignment | Optional | Optional | This is relevant to DMRS-BF. | -| U-Plane symbolId interpretation
as on-air symbol number for
symbol reordering | Optional | Optional | This is relevant to DMRS-BF. | -| U-Plane symbolId interpretation
as transmission window number
for symbol reordering | Optional | Optional | This is relevant to DMRS-BF. | -| SE 25 symbol reordering pattern | Optional | Optional | | - -The CUSM-Plane emulator will inform the O-RU of the symbol reordering via M-Plane configurations. Depending on O-RU capability of symbol reordering, there are different TER configured choices. - -The O-RU capability listed as follows: - -**Table 3.2.5.2.12-2: O-RAN symbol reordering capability** - -| O-RU capability | O-RU capability parameters | -|-----------------------------------|-------------------------------------------| -| supported-symb-reorder-capability | PER-TX-WIN-SYMB-REORDER-WITH-DMRS-SENDING | - -| | | -|--------------------------------------------|----------------------------------------------| -| | PER-TX-WIN-SYMB-REORDER-WITHOUT-DMRS-SENDING | -| | PER-SECTION-TX-WINDOW-REASSIGNMENT | -| up-symbolId-type-supported | OVER-AIR-SYMBOL-NUMBER | -| | TRANSMISSION-WINDOW-NUMBER | -| max-num-symbol-reordering-pattern-per-slot | uint16 | -| supported-section-extensions | including SE25 | - -The TER Possible configuration sets listed as follows: - -**Table 3.2.5.2.12-3: TER Possible configuration sets** - -| TER Possible configuration sets | TER configuration parameters | -|---------------------------------|------------------------------------------------| -| Configuration Set 1 | PER-TX-WIN-SYMB-REORDERG | -| | OVER-AIR-SYMBOL-NUMBER | -| | port-reduced-dmrs-data-sending-enabled = TRUE | -| Configuration Set 2 | PER-TX-WIN-SYMB-REORDERG | -| | TRANSMISSION-WINDOW-NUMBER | -| | port-reduced-dmrs-data-sending-enabled = TRUE | -| Configuration Set 3 | PER-TX-WIN-SYMB-REORDERG | -| | TRANSMISSION-WINDOW-NUMBER | -| | port-reduced-dmrs-data-sending-enabled = FALSE | -| Configuration Set 4 | PER-SECTION-TX-WINDOW-REASSIGNMENT | -| | OVER-AIR-SYMBOL-NUMBER | -| | port-reduced-dmrs-data-sending-enabled = FALSE | - -The CUSM-Plane emulator will inform the O-RU specific symbol reordering configurations using Section Extension 25 as follows: - -If TER configured PER-TX-WIN-SYMB-REORDERG (SE25 indicated values corresponding to 14 symbols that are applicable to all layers, U-plane symbolId is interpreted as 'on-air symbol number' or transmission window number based on O-RU capability): - -| | | | | | | | | | | | | | | | -|---|----|---|---|---|---|---|---|---|---|----|----|----|----|----------------------------------------------------------------------------| -| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | OTA symbol number | -| 2 | 11 | 0 | 1 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 12 | 13 | OTA symbol number of the IQ data in U- plane message | -| 2 | 11 | 0 | 1 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 12 | 13 | U- plane symbolId which up- symbolId- type is OVER- AIR- SYMBOL- NUMBER | -| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | U- plane symbolId which up- symbolId- type is TRANSMISSION- WINDOW- NUMBER | - -| Extension Type 25 for Section Id=0 and 1 | | | | | | | | | | -|------------------------------------------|----------------|---|---|-----------------------------------------|---|---|---------|------------|---------| -| 0 (msb) | 1 | 2 | 3 | 4 | 5 | 6 | 7 (lsb) | # of bytes | | -| ef | extType = 0x19 | | | | | | | 1 | Octet N | -| extLen = 0x03 | | | | | | | | 1 | N+1 | -| txWinForOnAirSymbol0 (all layers) = 2 | | | | txWinForOnAirSymbol1 (all layers) = 3 | | | | 1 | N+2 | -| txWinForOnAirSymbol2 (all layers) = 0 | | | | txWinForOnAirSymbol3 (all layers) = 4 | | | | 1 | N+3 | -| ... | | | | | | | | | | -| txWinForOnAirSymbol10 (all layers) = 11 | | | | txWinForOnAirSymbol11 (all layers) = 1 | | | | 1 | N+7 | -| txWinForOnAirSymbol12 (all layers) = 12 | | | | txWinForOnAirSymbol13 (all layers) = 13 | | | | 1 | N+8 | -| Zero pad for 4-byte boundary | | | | | | | | 3 | N+9 | - -If TER configured PER-SECTION-TX-WINDOW-REASSIGNMENT (SE25 indicated values corresponding to 14 symbols that are applicable separately to each layer, U-plane symbolId is interpreted as 'on-air symbol number'): - -| Symbol reordering for UE layer prioritization | | | | | | | | | | | | | | | -|-----------------------------------------------|---|---|---|---|----|----|----|---|---|----|----|----|----|------------------------------------------------------| -| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | OTA symbol number | -| 2 | 0 | 3 | 5 | 7 | 9 | 12 | 2 | 0 | 3 | 5 | 7 | 9 | 12 | OTA symbol number of the IQ data in U- plane message | -| 2 | 0 | 3 | 5 | 7 | 9 | 12 | 2 | 0 | 3 | 5 | 7 | 9 | 12 | U- plane symbolId | -| 11 | 1 | 4 | 6 | 8 | 10 | 13 | 11 | 1 | 4 | 6 | 8 | 10 | 13 | OTA symbol number of the IQ data in U- plane message | -| 11 | 1 | 4 | 6 | 8 | 10 | 13 | 11 | 1 | 4 | 6 | 8 | 10 | 13 | U- plane symbolId | - -Layer#0 for section#0      Layer#1 for section#0 - -| Extension Type 25 for Section Id=0 | | | | | | | | | | -|----------------------------------------------------|----------------|---|---|----------------------------------------------------|---|---|---------|------------|---------| -| 0 (msb) | 1 | 2 | 3 | 4 | 5 | 6 | 7 (lsb) | # of bytes | | -| ef | extType = 0x19 | | | | | | | 1 | Octet N | -| extLen = 0x04 | | | | | | | | 1 | N+1 | -| txWinForOnAirSymbol0 (1 st layer) = 1 | | | | txWinForOnAirSymbol1 (1 st layer) = 1 | | | | 1 | N+2 | -| txWinForOnAirSymbol2 (1 st layer) = 0 | | | | txWinForOnAirSymbol3 (1 st layer) = 2 | | | | 1 | N+3 | -| ... | | | | | | | | | | -| txWinForOnAirSymbol10 (1 st layer) = 5 | | | | txWinForOnAirSymbol11 (1 st layer) = 0 | | | | 1 | N+7 | -| txWinForOnAirSymbol12 (1 st layer) = 6 | | | | txWinForOnAirSymbol13 (1 st layer) = 6 | | | | 1 | N+8 | -| txWinForOnAirSymbol0 (2 nd layer) = 8 | | | | txWinForOnAirSymbol1 (2 nd layer) = 8 | | | | 1 | N+9 | -| txWinForOnAirSymbol2 (2 nd layer) = 7 | | | | txWinForOnAirSymbol3 (2 nd layer) = 9 | | | | 1 | N+10 | -| ... | | | | | | | | | | -| txWinForOnAirSymbol10 (2 nd layer) = 12 | | | | txWinForOnAirSymbol11 (2 nd layer) = 7 | | | | 1 | N+14 | -| txWinForOnAirSymbol12 (2 nd layer) = 13 | | | | txWinForOnAirSymbol13 (2 nd layer) = 13 | | | | 1 | N+15 | - -This test re-uses the test case description from clause 3.2.5.2.11.A. - -### B. Test Entrance Criteria - -For the test entrance criteria see clause 3.2.5.2.11.B - -### C. Test Methodology - -**a. Initial Conditions** - -The initial conditions are the same as in see clause 3.2.5.2.11.C.a with the following additions: - -- Depending on O-RU capability of symbol reordering, there are different TER configured choices (Table 3.2.5.2.12-2: O-RAN symbol reordering capability). -- If symb-reorder-method is PER-SECTION-TX-WINDOW-REASSIGNMENT, use OVER-AIR-SYMBOL-NUMBER as up-SymbolId-type according to CUS specification [2]. - -**b. Procedure** - -The procedure consists of executing the basic test case defined in clause 3.2.5.2.11.C.b modified by applying configurations described in steps below. The clause 3.2.5.2.11.C.b applies with the following modifications: - -- TER shall prepare C-plane message of ST 5 with SE 10, SE 24 and SE 25. The configuration in SE 10, SE 24 and SE 25 shall be compatible with the capabilities reported by the O-RU under test. - -Steps: - -1. If the O-RU reports capability for PER-TX-WIN-SYMB-REORDER-WITH-DMRS-SENDING and OVER-AIR-SYMBOL-NUMBER or list including above capabilities (refer to M-plane leaf-list supported-symb-reorder-capability and up-symbolId-type-supported), execute basic test case with other configuration specified in configuration set 1(Table 3.2.5.2.12-3: TER Possible configuration sets). -2. If the O-RU reports capability for PER-TX-WIN-SYMB-REORDER-WITH-DMRS-SENDING and TRANSMISSION-WINDOW-NUMBER or list including above capabilities (refer to M-plane leaf-list supported-symb-reorder-capability and up-symbolId-type-supported), execute basic test case with other configuration specified in configuration set 2(Table 3.2.5.2.12-3: TER Possible configuration sets). -3. If the O-RU reports capability for PER-TX-WIN-SYMB-REORDER-WITHOUT-DMRS-SENDING and TRANSMISSION-WINDOW-NUMBER or list including above capabilities (refer to M-plane leaf-list supported-symb-reorder-capability and up-symbolId-type-supported), execute basic test case with other configuration specified in configuration set 3(Table 3.2.5.2.12-3: TER Possible configuration sets). -4. If the O-RU reports capability for PER-SECTION-TX-WINDOW-REASSIGNMENT and OVER-AIR-SYMBOL-NUMBER or list including above capabilities (refer to M-plane leaf-list supported-symb-reorder-capability and up-symbolId-type-supported), execute basic test case with other configuration specified in configuration set 4 (Table 3.2.5.2.12-3: TER Possible configuration sets). - -The execution of the test case will trigger the O-RU to handle symbol-reordering method and report reordered U-Plane data according to SE25, and U-Plane symbolId interpretation will base on TER configuration. - -**D. Test Requirement (expected result)** - -The expected result is as in clause 3.2.5.2.11.D with a separate check of U-Plane symbol order is same as SE25 indicating. - -**3.2.5.2.13 UC-Plane O-RU Scenario Class Extended using section extension 24 for DMRS-BF****A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY with the condition the O-RU supports DMRS-BF-EQ or DMRS-BF-NEQ. - -The purpose of this test is to ensure the radio can process SE 24 and process UL signal with DMRS beamforming. - -This test case consists of multiple configurations each with defined preconditions. For the description see clause 3.2.5.2.11.A. - -## B. Test Entrance Criteria - -For the test entrance criteria see clause 3.2.5.2.11.B - -## C. Test Methodology - -### a. Initial Conditions - -The initial conditions are the same as in see clause 3.2.5.2.11.C.a. - -### b. Procedure - -The procedure consists of executing the basic test case defined in clause 3.2.5.2.11.C.b modified by applying various configurations described below. The clause 3.2.5.2.11.C.b applies with the following modifications: - -- TER shall check condition defined for each step. -- TER shall build appropriate signal (following UE and UE's data layer configuration), and C-plane message as specified for given configuration. SE 24 shall be within ST 5 and with SE 10. -- TER shall inject signal emulating ideal channel conditions as well as UE and layer spatial separation with power levels at least 30dB higher than the power levels used to test 3GPP. - -Steps: - -- If the O-RU reports support for SE 24 with entryType = 2 (refer to M-plane leaf-list supported-entry-types), execute basic test case for each configuration specified in configuration set 1. -- If the O-RU reports support for SE 24 with entryType = 3 (refer to M-plane leaf-list supported-entry-types), execute basic test case for each configuration specified in configuration set 2. -- If the O-RU reports support for SE 24 with entryType = 1 and entryType = 2 (refer to M-plane leaf-list supported-entry-types), execute basic test case for each configuration specified in configuration set 3. -- If the O-RU reports support for SE 24 with entryType = 2 and entryType = 3 (refer to M-plane leaf-list supported-entry-types) and multiplexing transform precoding disabled and enabled (refer to M-plane parameter different-transform-precoding-in-user-group-supported = true), execute basic test case for each configuration specified in configuration set 4. -- If the O-RU reports support for persistence of ueId between multiple slots (refer to M-plane feature UEID-PERSISTENCE) and SE 24 with entryType = 2 (refer to M-plane leaf-list supported-entry-types), execute basic test case for the first of parameter values combinations specified in configuration set 1 modified by setting parameter ueIdReset = 1 in the first and every even slot and 0 in other slots in the parameters. -- If the O-RU reports support for ueId persistence over multiple slots (refer to M-plane feature UEID-PERSISTENCE) and SE 24 with entryType = 3 (refer to M-plane leaf-list supported-entry-types), execute basic test case for the first of parameter values combinations specified in configuration set 2 modified by setting parameter ueIdReset = 1 in the first and every even slot and 0 in other slots in the parameters. -- If the O-RU reports support for ueId persistence over multiple slots (refer to M-plane feature UEID-PERSISTENCE) and SE 24 with entryType = 1 and entryType 2 (refer to M-plane leaf-list supported-entry-types), execute basic test case for the configuration specified in configuration set 3 modified by setting parameter ueIdReset = 1 in the first and every even slot and 0 in other slots in the parameters. For slots where ueIdReset = 0 the 2nd entry shall be changed to entryType = 0. -- If the O-RU reports support for ueId persistence over multiple slots (refer to M-plane feature UEID-PERSISTENCE) and SE 24 with entryType = 1 and entryType = 3 (refer to M-plane leaf-list supported-entry-types), execute basic test case for the configuration specified in configuration set 4 modified by - -setting parameter ueIdReset = 1 in the first and every even slot and 0 in other slots in the parameters. For slots where ueIdReset = 0 the 2nd entry shall be change to entryType = 0. - -In principle execution of basic test case in each of the above steps may be performed by TER in parallel provided the O-RU's and TER have capability for multiplexing of different configurations at different, non-overlapping parts of frequency spectrum. - -Configuration Set 1 (entryType 2 - transform precoding disabled): - -- 1 UE with 1 data layer with transform precoding disabled and DMRS configuration matching one provided in SE 24 -- SE 24 with 1 entry with entryType = 2 and the following parameters: - - ueIdReset = 1 - - dmrsSymbolMask = separate configurations for each of values reported as supported by O-RU for transform precoding disabled and other parameters (e.g., dType) fixed to lowest values supported by the O-RU. - - dType = separate configurations for each of values reported as supported by O-RU for transform precoding disabled and other parameters (e.g., dmrsSymbolMask) fixed to lowest values supported by the O-RU. - - dmrsPortNumber, scrambling, nscid, lambda, cdmWithoutData, firstPrb, lastPrb shall have values as per CUS-plane requirements. - -Configuration Set 2 (entryType = 3 - transform precoding enabled): - -- 1 UE with 1 data layer with transform precoding enabled and DMRS configuration matching one provided in SE 24 -- SE 24 with 1 entry with entryType = 3 and the following parameters: - - ueIdReset = 1 - - dmrsSymbolMask = separate configuration for each of values reported as supported by O-RU for transform precoding enabled and other parameters (e.g., lowPaprtype and hoppingMode) fixed to lowest values supported by the O-RU. - - lowPaprtype and hoppingMode = separate configuration for each pair of values reported as supported by O-RU for transform precoding enabled and with other parameters (e.g, dmrsSymbolMask) fixed to lowest values supported by the O-RU. - - dmrsPortNumber, scrambling, nscid, firstPrb, lastPrb shall have values as per CUS-plane requirements. - -Configuration Set 3 (entryType = 1 - reuse of configuration from prior entry for transform precoding disabled): - -- 1 UE with 2 data layers with transform precoding disabled and DMRS configuration matching one provided in SE 24 -- SE 24 with 2 entries: - - a. 1st entry with entryType = 2 and parameters as in the first of parameter values combinations specified in Configuration Set 1. - - b. 2nd entry with entryType = 1 and dmrsPortNumber set to the next consecutive value larger than dmrsPortNumber in 1st entry - -Configuration Set 4 (mix of transform precoding disabled and enabled): - -- 2 UEs with 1 data layer each: - - a. 1st UE with transform precoding disabled and DMRS configuration matching one provided in 1st entry in SE 24 - - b. 2nd UE with transform precoding enabled and DMRS configuration matching one provided in 2nd entry in SE 24 -- SE 24 with 2 entries: - - a. 1st entry with entryType = 2 - - b. 2nd entry with entryType = 3 - - c. Parameters for both entries shall be within the O-RU reported capabilities and shall be mutually compatible i.e. the same dmrsSymbolMask, dType (given explicitly and implied), cdmWithoutData (given explicitly and implied), etc. - -**D. Test Requirement (expected result)** - -The expected result is as in clause 3.2.5.2.11.D with a separate check of the result for each of the configurations used in this test case. - -**3.2.5.2.14 UC-Plane O-RU Scenario Class RRM Measurements for DMRS-BF** - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY according to Table 10.2-1 section “Measurements” in [2]. - -The applicability for the different RRM measurements is summarized in table below. - -| DMRS-BF Type | Measurements | O-RU Applicability | -|--------------|-------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| -| DMRS-BF-EQ | MEAS_UE_TAE
MEAS_UE_LAYER_POWER
MEAS_UE_FREQ_OFFSET
MEAS_IPN_ALLOC
MEAS_IPN_UNALLOC | MANDATORY | -| | MEAS_ANT_DMRS | OPTIONAL | -| DMRS-BF-NEQ | MEAS_UE_TAE | MANDATORY if O-RU does not declare feature DMRS-BF-NEQ_UNALTERED-TAE | -| | MEAS_UE_FREQ_OFFSET | MANDATORY if O-RU does not declare feature DMRS-BF-NEQ_UNALTERED-FREQ-OFFSET | -| | MEAS_UE_LAYER_POWER | MANDATORY for all DMRS-BF-NEQ capable endpoints if any of those supports the RRM measurement. | -| | MEAS_IPN_ALLOC
MEAS_IPN_UNALLOC
MEAS_ANT_DMRS | OPTIONAL | - -The RRM measurements M-Plane capability parameters are: - -*rrm-meas-supported, max-ipn-unalloc-reports-supported, max-ipn-unalloc-symbols-supported, max-ipn-alloc-reports-supported, alloc-ipn-per-dmrs-sym-grp-supported, ta3-min-2g and ta3-max-2g.* - -The RRM measurements M-Plane configuration parameter is: - -*rrm-meas-enabled.* - -The purpose of this test is to verify that the O-RU handles the configuration and reporting of RRM measurements according to CUS specification [2]. The purpose is not to verify that the measurements values calculated by O-RU are correct. - -This test re-uses the test case description from clause 3.2.5.2.11.A. - -**B. Test Entrance Criteria** - -For the test entrance criteria see clause 3.2.5.2.11.B - -**C.1. Test Methodology (UE\_TAE, LAYER\_POWER, FREQ\_OFFSET, ANT\_DMRS\_SNR)** - -**a. Initial Conditions** - -The initial conditions are the same as in see clause 3.2.5.2.11.C.a with the following additions: - -- Depending on which O-RU DMRS-BF type that is tested, different RRM measurements will be supported by the O-RU and enabled by the O-DU. For a description of MEAS\_UE\_TAE, MEAS\_UE\_LAYER\_POWER, MEAS\_UE\_FREQ\_OFFSET and MEAS\_ANT\_DMRS see clauses 9.2.2.1, 9.2.2.2, 9.2.2.3 and 9.2.2.6 in CUS Specification [2]. -- For a DMRS-BF-EQ O-RU: - - Enable measurements MEAS\_UE\_TAE, MEAS\_UE\_LAYER\_POWER and MEAS\_UE\_FREQ\_OFFSET via M-Plane. - - Enable MEAS\_ANT\_DMRS if supported by the O-RU via M-Plane. -For MEAS\_ANT\_DMRS SE24 parameter *antDmrsSnr* needs to be set to 1 for at least one of the user groups. -- For a DMRS-BF-NEQ O-RU: - - Enable MEAS\_UE\_TAE, MEAS\_UE\_LAYER\_POWER, MEAS\_UE\_FREQ\_OFFSET and MEAS\_ANT\_DMRS if supported by the O-RU via M-Plane. -For MEAS\_ANT\_DMRS SE24 parameter *antDmrsSnr* needs to be set to 1 for at least one of the user groups. - -#### b. Procedure - -The procedure consists of executing the basic test case defined in clause 3.2.5.2.11.C.b. - -The execution of the test case will trigger the O-RU to calculate and report the enabled RRM measurements. - -#### D.1. Test Requirement (expected result) - -The expected result is as in clause 3.2.5.2.11.D with a separate check of: - -- The measurements that are enabled are reported to the O-DU. - - For UE\_TAE; one value per UE per slot shall be reported. - - For UE\_LAYER\_POWER; one value per DMRS port per slot shall be reported and power values for all layers of a UE shall be sent in same report, as shown in Table 7.4.12-3 [2]. - - For UE\_FREQ\_OFFSET; one value per UE per slot shall be reported. - - For ANT\_DMRS\_SNR; one value per layer per antenna per slot shall be reported. -- The timing of the measurements reports is according to Figure 4.4.3-7 in the CUS Specification [2] Clause 4.4.3. - -#### C.2. Test Methodology (IPN\_ALLOC) - -##### a. Initial Conditions - -The initial conditions are the same as in see clause 3.2.5.2.11.C.a with the following additions: - -- O-RU support for MEAS\_IPN\_ALLOC depends on both which DMRS-BF type that is tested and on the O-RU's capability. For a description of MEAS\_IPN\_ALLOC see clause 9.2.2.4 in CUS Specification [2]. -- For a DMRS-BF-EQ O-RU: - - Enable measurement MEAS\_IPN\_ALLOC via M-Plane on one rx endpoint that supports the measurement, either a DMRS-BF-endpoint, or an endpoint dedicated for IPN measurement. -- For a DMRS-BF-NEQ O-RU: - - If MEAS\_IPN\_ALLOC is supported by at least one rx endpoint, enable measurement MEAS\_IPN\_ALLOC via M-Plane on one rx endpoint that supports the measurement, either a DMRS-BF-endpoint, or an endpoint dedicated for IPN measurement. -- Parameter *aIpnPerSym* in SE24 shall be set according to the capabilities reported by the O-RU. Each value of *aIpnPerSym* that is supported by the O-RU shall be tested for at least one user group. - -##### b. Procedure - -The procedure consists of executing the basic test case defined in clause 3.2.5.2.11.C.b. - -The execution of the test case will trigger the O-RU to calculate the IPN for the allocated PRBs and send the report back to O-RU according to the setting of *aIpnPerSym* etc. - -## D.2. Test Requirement (expected result) - -The expected result is as in clause 3.2.5.2.11.D with a separate check of: - -- The IPN for allocated PRBs are reported to O-DU. - - IPN\_ALLOC; one value per PRB, either for one symbol, or as an average over multiple symbols depending on O-RU capability and setting of SE24 parameter *aIpnPerSym*. -- Verify that *symbolMask* in report aligns with the request. -- Verify that the eAxC used for the reports corresponds to the rx endpoint that has MEAS\_IPN\_ALLOC enabled. -- The timing of the measurement reports is according to Figure 4.4.3-7 in the CUS Specification [2] Clause 4.4.3. - -## C.3. Test Methodology (IPN\_UNALLOC) - -### a. Initial Conditions - -The initial conditions for measurement of IPN for unallocated PRBs are different compared to other RRM measurements. The trigger for this measurement is the O-DU sending a Section Type 11 to the O-RU. - -- O-RU support for MEAS\_IPN\_UNALLOC depends on both which DMRS-BF type that is tested and on the O-RU's capability. For a description of MEAS\_IPN\_UNALLOC see clause 9.2.2.5 in CUS Specification [2]. -- For a DMRS-BF-EQ O-RU: - - Enable measurement MEAS\_IPN\_UNALLOC via M-Plane on one rx endpoint that supports the measurement. -- For a DMRS-BF-NEQ O-RU: - - If MEAS\_IPN\_UNALLOC is supported by at least one rx endpoint, enable measurement MEAS\_IPN\_ALLOC via M-Plane on one rx endpoint that supports the measurement. - -### b. Procedure - -The O-DU requests IPN for unallocated PRBs by sending a Section Type 11 to the O-RU with eAxC set to same as for the rx endpoint that is enabled for IPN\_UNALLOC measurements. - -## D.3. Test Requirement (expected result) - -The expected result is as in clause 3.2.5.2.11.D with a separate check of: - -- The IPN for unallocated PRBs are reported to O-DU. - - IPN\_UNALLOC; one value per PRB, either for one symbol, or as an average over multiple symbols (controlled via parameter *symbolMask* in ST11). -- The reports shall follow the ST11 request parameter setting when it comes to *symbolMask*, possible existence of Section Extensions 6, 12 and/or 20. -- Verify that the eAxC used for the reports corresponds to the same rx endpoint that is used by SE11, which is an endpoint dedicated for IPN measurement. -- The timing of the measurement reports is according to Figure 4.4.3-7 in the CUS Specification [2] Clause 4.4.3. - -## 3.2.5.2.15 UC-Plane O-RU Scenario Class Extended using section extension ST9 for DMRS-BF - -### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY with condition the O-RU supports DMRS-BF-EQ. - -The purpose of this test is to ensure the O-RU can process M-plane configuration for SINR and send SINR data in ST 9 messages. For further description see clause 3.2.5.2.11.A. - -### B. Test Entrance Criteria - -The test entrance criteria is as described in clause 3.2.5.2.11.B with addition: - -- The O-RU supports DMRS-BF-EQ. - -## C. Test Methodology - -### a. Initial Conditions - -The initial conditions are the same as in clause 3.2.5.2.11.C.a. - -### b. Procedure - -The procedure consists of executing the basic test case defined in clause 3.2.5.2.11.C.b modified by applying various configurations described below. The clause 3.2.5.2.11.C.b applies with the following modifications: - -- TER shall prepare C-plane message of ST 5 with SE 10, SE 24. The configuration in SE 24 shall be compatible with the capabilities reported by the O-RU under test and consist of 1 data layer. -- TER shall build appropriate signal for 1 UEs of rank 1 with DMRS configuration compatible with configuration provided to O-RU in SE 24. -- TER shall inject signal emulating ideal channel conditions with power levels at least 30dB higher than the power levels used to test 3GPP. -- The TER shall configure the O-RU via M-plane for DMRS-BF-EQ reception and configure the selected SINR resolution (both sinr-per-prb and sinr-slot-bitmask) to the first of SINR resolutions reported as supported by the O-RU in supported-sinr-resolutions, set sinr-compression to the first element in supported-sinr-compression-methods reported by the O-RU and set sinr-reference-level-config to value of sinr-reference-level-max reported by the O-RU. The TER shall enable SINR reporting by setting sinr-reporting-enabled = true. - -Steps: - -1. The TER shall execute the basic test case observing ST 9 messages sent by the O-RU. The TER shall collect per UE data layer a summary of received SINR including minimum, maximum and average. - -### D. Test Requirement (expected result) - -The expected result is reception of ST 9 message(s) compliant to the SINR reporting resolution configuration and SINR data format configuration set via M-plane. - -In addition, the test report shall include SINR statistics collected by TER (see step C.b.1). - -## 3.2.5.2.16 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – DMRS based Beamforming using Frequency offset feedback - -### A. Test Description and Applicability - -This Test is CONDITIONAL MANDATORY; the test condition is O-RU that support either DMRS-EQ or DMRS-NEQ supports SE 26. - -The SE 26 is used with Section Type 5 to deliver the UE frequency offset from the O-DU to the O-RU and is valid only when dataDirection bit = 0 and when SE 24 is present and SE 24 precedes SE 26. - -The M-Plane configuration parameter is **sc26-usage-enabled**. - -TER controls the CUSM-Plane emulator to inform the O-RU specific Frequency offset configurations using Section Extension 26 as follows: - -**Table 3.2.5.2.16-1: SE 26 to be used in this conformance test scenario** - -| 0 (msb) | 1 | 2 | 3 | 4 | 5 | 6 | 7 (lsb) | # of bytes | | | | | | | | | -|---------------------------------------|------------------|---|---|---|---|---|---------|------------|---------|--|--|--|--|--|--|--| -| ef | extType = 0x1A | | | | | | | 1 | Octet N | | | | | | | | -| extLen = 0x01 | | | | | | | | 1 | N+1 | | | | | | | | -| reserved | | | | | | | | 1 | N+2 | | | | | | | | -| reserved | numFoFb[6:0] = 2 | | | | | | | 1 | N+3 | | | | | | | | -| 1 st freqOffsetFb = 0x3E8 | | | | | | | | 2 | N+4 | | | | | | | | -| 2 nd freqOffsetFb = 0xFC18 | | | | | | | | 2 | N+6 | | | | | | | | -| zero padding to 4-byte boundary | | | | | | | | var | var | | | | | | | | - -The purpose of this test is to ensure the radio can receive the SE 26 information without generating any errors. There is no attempt to validate that the O-RU applies the frequency offset correctly because O-RU is not required to use the frequency offset received in SE26. Specific frequency offset values are required to be included in the SE 26 message, to ensure uniformity of the testing. Specifically, the values 0x3E8 and 0xFC18 shall be used (see Table 3.2.5.2.16-1), which for SCS = 30 kHz represent positive 500Hz and negative 500Hz. - -This test re-uses the test case description from clause 3.2.5.2.11.A. - -## B. Test Entrance Criteria - -For the test entrance criteria see clause 3.2.5.2.11.B with the following addition: - -- The TER equipment adds control parameters to turn on the SE 26 frequency offset configuration function (create SE 26 and convey to O-RU). Note the frequency offset values provided in SE 26 are fixed values under test. - -## C. Test Methodology - -### a. Initial Conditions - -The initial conditions are the same as in see clause 3.2.5.2.11.C.a with the following addition: - -- O-RU support SE 26 and M-Plane parameter **se26-usage-enabled** = TRUE. - -### b. Procedure - -The procedure consists of executing the basic test case defined in clause 3.2.5.2.11.C.b modified by enabling the SE 26 frequency offset function: - -- DU emulator will create C-Plane message including SE 26, the values in SE 26 are frequency offset values configured by TER. DU emulator will convey C-Plane message ST 5 with SE 10, SE 24 and SE 26 to O-RU. -- Inject the test signals with additional frequency offset for each UE. -- Other procedure is same with basic test case defined in clause 3.2.5.2.11.C.b. Records output result EVM and BER or BLER measured during the test. - -## D. Test Requirement (expected result) - -No fault or error is detected via M-Plane from the O-RU resulting when reception of SE 26. There is no evaluation of the quality of the received signal (EVM, BLER or BER). - -### 3.2.5.2.17 UC Plane O-RU Scenario Class Extended using section extension 27 for DMRS-BF - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY, with condition being O-RU reports support for SE 27. - -The purpose of this test is to ensure the radio can process SE 27 and process UL signal with DMRS beamforming. For further description see clause 3.2.5.2.11.A. This test uses beamforming weight update mechanism of WDBF or predefined beams of PDBF depending on specification provided by the vendor of the O-RU (see also 2nd bullet in 3.2.5.2.17.B). - -#### B. Test Entrance Criteria - -The test entrance criteria is as described in clause 3.2.5.2.11.B with addition: - -- The O-RU supports SE 27. -- The vendor of the O-RU provides set of 2 to 4 beams to be used in the test. The beams in the set are defined by documenting beamforming weights to be used. Alternatively, the vendor may provide two sets of beamId values which identify predefined beams supported by the O-RU: - - a set of N values Bn specified in step 3.2.5.2.17.C.b.2 and - - a set of N consecutive values starting with value B specified in step 3.2.5.2.17.C.b.5. -- The vendor of the O-RU provides parameters for positioning 2 UEs of rank 1 to be used for the test. The positioning is to be specified by angle parameters relative to antenna array (see clause 12.5.2 in CUS-plane [2]). - -#### C. Test Methodology - -##### a. Initial Conditions - -The initial conditions are the same as in see clause 3.2.5.2.11.C.a. - -##### b. Procedure - -The procedure consists of executing the basic test case defined in clause 3.2.5.2.11.C.b modified by applying various configurations described in steps below. The clause 3.2.5.2.11.C.b applies with the following modifications: - -- TER shall prepare C-plane message of ST 5 with SE 10, SE 24 and SE 27. The configuration in SE 10, SE 24 and SE 27 shall be compatible with the capabilities reported by the O-RU under test. -- TER shall build appropriate signal for 2 UEs of rank 1 with DMRS configuration compatible with configuration provided to O-RU in SE 24. -- TER shall inject signal emulating ideal channel conditions with power levels at least 30dB higher than the power levels used to test 3GPP. UE positions shall be as specified by the vendor of the O-RU. - -Steps: - -1. The TER shall select value N such that N is greater or equal the number of beams in the set specified by the O-RU vendor and N is number of beams supported by the O-RU to be commanded via SE 27 (refer to M-plane parameter supported-se-27-num-elements in the list supported-se-27-configurations). -2. The TER shall select set of N values Bn where n = 0, 1, ..., N-1. The values Bn shall not be consecutive and valid beamId values supported by the O-RU. If the vendor of the O-RU provided beamId values as described in clause 3.2.5.2.17.B then the TER shall use the values Bn provided by the vendor. -3. If the vendor of the O-RU provided beamforming weight values described in clause 3.2.5.2.17.B then the TER shall use ST 1 with SE 1 or SE 11 with reMask=0 as described in clause 7.5.3.5 in CUS-plane [2] to associate beamforming weights of the beams specified by the O-RU vendor with beamId = B0, B(N-1), B1, B(N-2), etc. For the remaining Bn values the TER shall associate beamId=Bn with beamforming weights set to 0. -4. The TER shall execute the basic test case modified to include in ST 5 also SE 27 with beamType = 0, numElements = N, beamId = B0, B1, ..., B(N-1). - -5. The TER shall select value B such that for $n = 0, 1, \dots, N-1$ value $B+n$ is a valid beamId value supported by the O-RU and N is number of beams supported by the O-RU to be commanded via SE 27. If the vendor of the O-RU provided beamId values as described in clause 3.2.5.2.17.B then the TER shall use the value B provided by the vendor. -6. If the vendor of the O-RU provided beamforming weight values described in clause 3.2.5.2.17.B then the TER shall use ST 1 with SE 1 or SE 11 with reMask=0 as described in clause 7.5.3.5 in CUS-plane [2] to associate beamforming weights of the beams specified by the O-RU vendor with beamId = B, B+(N-1), B+1, B+(N-2), etc. For the remaining values in range B to B+N-1 the TER shall associate beamId=B+n with beamforming weights set to 0. -7. The TER shall execute the basic test case modified to include in ST 5 also SE 27 with beamType = 1, numElements = N, beamId = B. - -#### D. Test Requirement (expected result) - -The expected result is as in clause 3.2.5.2.11.D with a separate check of the result for each execution of the basic test case in the steps 4 and 7 of the procedure described in clause 3.2.5.2.17.C.b. - -### 3.2.5.3 UC-Plane O-RU Scenario Class Compression (CMP) - -Validate the correct implementation and interpretation of mandatory and optional IQ data compression formats described in [2]. Also, evaluate the consistency in U-Plane signalling. - -It applies to the following O-RAN CUS Specification [2]: - -- Clause 7.4 -- Clause 7.5.2.10 -- Clause 8.3.3.15/16/17 -- Clause 8.3.2 -- Clause 8.3.3 -- Table 10.2-1 -- Annex A.6 -- Annex A.6 Selective RE sending Compression - -The objective is primarily to test the protocol, prior to the compression algorithms performance. - -**Signalling:** IQ Compression related fields in UC-Plane messages include: - -- U-Plane IQ data field -- C-Plane udCompHdr (clause 7.5.2.10 of [2]) -- U-Plane udComphdr (clause 8.3.3.13 of [2]) -- U-Plane udCompParam (clause 8.3.3.15 of [2]) -- Modulation compression parameters used in the Section Extension Type =4 - - csf (constellation shift flag) - - modCompScaler (modulation compression scaler value) - -**Compression:** Current specification includes 7 compression modes, including uncompressed mode (fixed point). Tests should cover each one of these modes - -- fixed-point -- block floating-point -- block scaling -- mu-law -- modulation compression -- Block Floating Point + selective RE sending -- Modulation Compression + selective RE sending - -**IQ Bit Width:** For fixed-point, block floating point, block scaling and mu-law compression, IQ information can be represented using different bit width (1-16 bits). To optimize test time, tests should be performed on a subset of bit widths - -For fixed point, block floating point, block scaling, mu-law compressions the subset of bit widths to be tested are - -- 9 bits -- 14 bits - -For modulation compression bit width 4 is used for the test - -### 3.2.5.3.1 Overview of Compression Test Methodology - -A common test methodology and structure will be used across all compression test cases. Each one of the test cases will be defined with specific input parameters and expected output values. - -To minimize influence of the Radio's RF performance to the test results, the test methodology will be based on a relative comparison between modulated signal measurements performed on a TDD test frame with uncompressed IQ (fixed 16 bits) and measurements on the same test frame using compressed IQ. The test will verify that the difference between measurements fits within an acceptable range for the test to pass. - -For downlink test, the modulated signal measurement is performed by a signal analyser on the antenna port of the O-RU. - -For uplink measurement, the modulated signal measurement is performed with the IQ extracted from the Uplink U-Plane data sent by the O-RU on the O-RAN interface. - -The following paragraphs in this overview clause outline the details of these common test methodologies. - -#### 3.2.5.3.1.1 Test Frame - -TDD test methodology for compression will combine similar downlink and uplink test patterns used for FDD test. The main difference is that uplink and downlink tests are performed simultaneously for TDD. - -The test frames used for compression conformance test will be referred in this document as “**NR-FR1-TDD-CMP-TST-DL**” TDD Downlink Standard Compression Test frame and “**NR-FR1-TDD-CMP-TST-UL**” TDD Uplink Standard Compression Test frame. They are 5G NR frames based on the description in clause 3.2.1.1.3 For scenario #3 (Conducted TDD Tests for FR1 Radios) with specific attributes described below. - -The Downlink UC-Plane test stimulus file includes the C-Plane and U-Plane messages that require the O-RU to transmit on the downlink the NR-FR1-TDD-CMP-TST-DL test frame. - -The Uplink C-Plane test stimulus file includes the C-Plane messages that require the O-RU to provide the uplink U-Plane messages according to the NR-FR1-TDD-CMP-TST-UL test frame received by the O-RU on its antenna port. - -Signalling and IQ information will be based on various compression schemes - -**Table 3.2.5-6 Stimulus Files for Static Compression Tests.** - -| Stimulus File Name | Description | -|----------------------------------------|-----------------------------------------------------------------------------------------------| -| NR-FR1-TDD-CMP-TST-ST-DL-UNC-16B | Static Downlink Uncompressed (CU-plane) | -| NR-FR1-TDD-CMP-TST-ST-UL-UNC-16B | Static Uplink Uncompressed (C-plane only) | -| NR-FR1-TDD-CMP-TST-ST-DL-FPF-9B | Static Downlink Fixed Point 9 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-ST-DL-FPF-14B | Static Downlink Fixed Point 14 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-ST-UL-FPF-9B | Static Uplink Fixed Point 9 Bits (C-plane only) | -| NR-FR1-TDD-CMP-TST-ST-UL-FPF-14B | Static Uplink Fixed Point 14 Bits (C-plane only) | -| NR-FR1-TDD-CMP-TST-ST-DL-BFP-9B | Static Downlink Block Floating Point 9 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-ST-DL-BFP-14B | Static Downlink Block Floating Point 14 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-ST-UL-BFP-9B | Static Uplink Block Floating Point 9 Bits (C-plane only) | -| NR-FR1-TDD-CMP-TST-ST-UL-BFP-14B | Static Uplink Block Floating Point 14 Bits (C-plane only) | -| NR-FR1-TDD-CMP-TST-ST-DL-BSC-9B | Static Downlink Block Scaling 9 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-ST-DL-BSC-14B | Static Downlink Block Scaling 14 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-ST-UL-BSC-9B | Static Uplink Block Scaling 9 Bits (C-plane only) | -| NR-FR1-TDD-CMP-TST-ST-UL-BSC-14B | Static Uplink Block Scaling 14 Bits (C-plane only) | -| NR-FR1-TDD-CMP-TST-ST-DL-MLW-9B | Static Downlink Mu-Law 9 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-ST-DL-MLW-14B | Static Downlink Mu-Law 14 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-ST-UL-MLW-9B | Static Uplink Mu-Law 9 Bits (C-plane only) | -| NR-FR1-TDD-CMP-TST-ST-UL-MLW-14B | Static Uplink Mu-Law 14 Bits (C-plane only) | -| NR-FR1-TDD-CMP-TST-ST-DL-MC | Static Downlink Modulation Compression | -| NR-FR1-TDD -CMP-TST -ST-DL-UNC-BRE-16B | Static Downlink Uncompressed (CU-plane) with both empty and allocated RE in the same symbol | -| NR-FR1-TDD -CMP-TST -ST-UL-UNC-BRE-16B | Static Uplink Uncompressed (C-plane only) with both empty and allocated RE in the same symbol | -| NR-FR1-TDD-CMP-TST-ST-DL-BRE-9B | Static Downlink Block Floating Point + Selective RE 9 Bits (CU-plane) | -| NR-FR1- TDD-CMP-TST-ST-DL-BRE-14B | Static Downlink Block Floating Point + Selective 14 Bits (CU-plane) | -| NR-FR1- TDD-CMP-TST-ST-UL-BRE-9B | Static Uplink Block Floating Point 9 Bits + Selective RE (C-plane only) | -| NR-FR1- TDD-CMP-TST-ST-UL-BRE-14B | Static Uplink Block Floating Point 14 Bits + Selective RE (C-plane only) | -| NR-FR1- TDD-CMP-TST-ST-DL-MRE | Static Downlink Modcomp + Selective RE Compression | - -**Table 3.2.5-7 Stimulus Files for Non-Static Compression Test.** - -| Stimulus File Name | Description | -|---------------------------------------|-----------------------------------------------------------------------------------------------| -| NR-FR1-TDD-CMP-TST-NS-DL-UNC-16B | Downlink Uncompressed (CU-plane) | -| NR-FR1-TDD-CMP-TST-NS-UL-UNC-16B | Uplink Uncompressed (C-plane) | -| NR-FR1-TDD-CMP-TST-NS-DL-FPF-9B | Downlink Fixed Point 9 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-NS-DL-FPF-14B | Downlink Fixed Point 14 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-NS-UL-FPF-9B | Uplink Fixed Point 9 Bits (C-plane only) | -| NR-FR1-TDD-CMP-TST-NS-UL-FPF-14B | Uplink Fixed Point 14 Bits (C-plane only) | -| NR-FR1-TDD-CMP-TST-NS-DL-BFP-9B | Downlink Block Floating Point 9 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-NS-DL-BFP-14B | Downlink Block Floating Point 14 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-NS-UL-BFP-9B | Uplink Block Floating Point 9 Bits (C-plane only) | -| NR-FR1-TDD-CMP-TST-NS-UL-BFP-14B | Uplink Block Floating Point 14 Bits (C-plane only) | -| NR-FR1-TDD-CMP-TST-NS-DL-BSC-9B | Downlink Block Scaling 9 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-NS-DL-BSC-14B | Downlink Block Scaling 14 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-NS-UL-BSC-9B | Uplink Block Scaling 9 Bits (C-plane only) | -| NR-FR1-TDD-CMP-TST-NS-UL-BSC-14B | Uplink Block Scaling 14 Bits (C-plane only) | -| NR-FR1-TDD-CMP-TST-NS-DL-MLW-9B | Downlink Mu-Law 9 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-NS-DL-MLW-14B | Downlink Mu-Law 14 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-NS-UL-MLW-9B | Uplink Mu-Law 9 Bits (C-plane only) | -| NR-FR1-TDD-CMP-TST-NS-UL-MLW-14B | Uplink Mu-Law 14 Bits (C-plane only) | -| NR-FR1-TDD-CMP-TST-NS-DL-MC | Non-Static Downlink Modulation Compression | -| NR-FR1-TDD -CMP-TST -NS-DL-UNC-RE-16B | Static Downlink Uncompressed (CU-plane) with both empty and allocated RE in the same symbol | -| NR-FR1-TDD -CMP-TST -NS-UL-UNC-RE-16B | Static Uplink Uncompressed (C-plane only) with both empty and allocated RE in the same symbol | -| NR-FR1-TDD -CMP-TST -NS-DL-BRE-9B | Downlink Block Floating Point + Selective RE 9 Bits (CU-plane) | -| NR-FR1-TDD -CMP-TST -NS-DL-BRE-14B | Downlink Block Floating Point + Selective RE 14 Bits (CU-plane) + Selective RE | -| NR-FR1-TDD -CMP-TST -NS-UL-BRE-9B | Uplink Block Floating Point + Selective RE 9 Bits (C-plane only) | -| NR-FR1-TDD -CMP-TST -NS-UL-BRE-14B | Uplink Block Floating Point + Selective RE 14 Bits (C-plane only) + Selective RE | -| NR-FR1-TDD -CMP-TST -NS-DL-MRE | Downlink Modcomp + Selective RE Compression | - -### 3.2.5.3.1.2 Test Frame Power - -To ensure that the compressed IQ exponent value is properly tested, each symbol of the test frame will include 3 sections with different power levels. The Power levels are relative powers to the first group of PRBs transmitted. Any valid 3GPP power level may be used for the first set of PRBs as long as the power levels of the remaining PRBs are also valid. Figure 3.2.5.3-58 below shows PRB power relative to the first set of PRBs. - -- 0 dB for the bottom third of total PRBs in the symbol (referred as PDSCH0) -- -10 dB for the middle third of total PRBs in the symbol (referred as PDSCH1) -- -20 dB for the upper third of total PRBs in the symbol (referred as PDSCH2) - -The spectrum representation of the frame shown in Figure 3.2.5.3-58 below highlights the various power levels for each group of PRBs within a symbol. - -![Figure 3.2.5.3-58 PRB Spectrum Power Visualization: A spectrum plot showing power levels in dB across a 122.88 MHz span. The y-axis ranges from -120 dB to 0 dB. The plot shows three distinct power levels for different groups of PRBs: approximately 0 dB for the bottom third, -10 dB for the middle third, and -20 dB for the upper third.](777060de3711edf66fa36de0822c45ce_img.jpg) - -Figure 3.2.5.3-58 PRB Spectrum Power Visualization: A spectrum plot showing power levels in dB across a 122.88 MHz span. The y-axis ranges from -120 dB to 0 dB. The plot shows three distinct power levels for different groups of PRBs: approximately 0 dB for the bottom third, -10 dB for the middle third, and -20 dB for the upper third. - -Figure 3.2.5.3-58 PRB Spectrum Power Visualization - -### 3.2.5.3.1.3 Test Frame User data - -To validate that user data has not been impacted by compression, the test payload for the 3 sections is each based on an individual PN23 sequence that will be measured and compared by the test apparatus. - -### 3.2.5.3.1.4 Test Frame Modulation Scheme - -To maximise coverage on the compressed IQ mantissa value, the test frame will use the highest possible modulation, limited to 256 QAM modulation for downlink. An example measurement is show in Table 3.2.5-8. The data content is a PN23 sequence and the test frame assuming a channel bandwidth of 100 MHz (=273 PRB) is divided into three sections of 91 PRB each. Note that the first section below contains the Coreset in the first 3 PRB according to the 3GPP FRC model. - -Table 3.2.5-8 Example User Data Modulation Validation. - -| Content | No. Alloc | SC Spacing / CP | Slot | Map Type | No. Sym. | Sym. Offset | No. RBs | RB Offset | Settings | Power /dB | -|---------|------------|-----------------|------|----------|----------|-------------|---------|-----------|-----------|-----------| -| PDSCH | Copy To... | 30 kHz NCP | 0(0) | A | 14 | 0 | 88 | 3 | Config... | 0.00 | -| PDSCH | Copy To... | 30 kHz NCP | 0(0) | A | 14 | 0 | 91 | 91 | Config... | -10.00 | -| PDSCH | Copy To... | 30 kHz NCP | 0(0) | A | 14 | 0 | 91 | 182 | Config... | -20.00 | - -### 3.2.5.3.1.5 Summary of Required Measurements for Compression Tests - -3 measurements types will be required for downlink tests and 4 measurements will be required for uplink tests. - -- **Power level:** Using the test frames (NR-FR1-CMP-TST-FRAME-DL and NR-FR1-CMP-TST-FRAME-UL) sent twice with both compressed and uncompressed IQ data, power level measurements are performed to validate compression algorithms influence on Exponent (udCompParam). - -The Power level measurements are called: - -For downlink - -- CMP-Uncompressed-Measured-Power-DL-PDSCH0 in dBm -- CMP-Compressed-Measured-Power-DL-PDSCH0 in dBm -- CMP-Uncompressed-Measured-Power-DL-PDSCH1 in dBm -- CMP-Compressed-Measured-Power-DL-PDSCH1 in dBm -- CMP-Uncompressed-Measured-Power-DL-PDSCH2 in dBm -- CMP-Compressed-Measured-Power-DL-PDSCH2 in dBm - -For Uplink - -- CMP-Uncompressed-Measured-Power-UL-PUSCH0 in dBm -- CMP-Compressed-Measured-Power-UL-PUSCH0 in dBm -- CMP-Uncompressed-Measured-Power-UL-PUSCH1 in dBm -- CMP-Compressed-Measured-Power-UL-PUSCH1 in dBm -- CMP-Uncompressed-Measured-Power-UL-PUSCH2 in dBm -- CMP-Compressed-Measured-Power-UL-PUSCH2 in dBm - -For the test to pass, the difference between compressed and uncompressed measurements should be within an acceptable range, called - -- ACC\_PWR\_PDSCH0 = $\pm 1$ dB -- ACC\_PWR\_PDSCH1 = $\pm 1$ dB -- ACC\_PWR\_PDSCH2 = $\pm 1$ dB -- -- **EVM:** Using a common test frame sent twice with both compressed and uncompressed IQ data, EVM measurements comparisons between uncompressed IQ and compressed IQ will help validate acceptable compression influence on signal quality. - -For downlink these 6 EVM measurements required: - -- CMP-Uncompressed-Measured-EVM-DL-PDSCH0 in % -- CMP-Compressed-Measured-EVM-DL-PDSCH0 in % -- CMP-Uncompressed-Measured-EVM-DL-PDSCH1 in % -- CMP-Compressed-Measured-EVM-DL-PDSCH1 in % -- CMP-Uncompressed-Measured-EVM-DL-PDSCH2 in % -- CMP-Compressed-Measured-EVM-DL-PDSCH2 in % - -For uplink these 6 EVM measurements required: - -- CMP-Uncompressed-Measured-EVM-UL-PUSCH0 in % -- CMP-Compressed-Measured-EVM-UL-PUSCH0 in % -- CMP-Uncompressed-Measured-EVM-UL-PUSCH1 in % -- CMP-Compressed-Measured-EVM-UL-PUSCH1 in % -- CMP-Uncompressed-Measured-EVM-UL-PUSCH2 in % -- CMP-Compressed-Measured-EVM-UL-PUSCH2 in % - -For the test to pass, the difference between the compressed and uncompressed measurements for the same PDSCH signal must be within the following range: - -- ACC\_EVM\_PDSCH0 $\leq 4$ percentage points - -- ACC\_EVM\_PDSCH1 $\leq 4$ percentage points -- ACC\_EVM\_PDSCH2 $\leq 4$ percentage points - -An example measurement showing both power and EVM is shown below in Figure 3.2.5.3-59. - -![Figure 3.2.5.3-59: Example Compression EVM Measurement. The figure consists of two parts: a spectrum analyzer display on the left and a data table on the right. The display shows a green signal spectrum with a center frequency of 1 GHz and a span of 96 MHz. The table provides detailed measurement data for various channels.](f2a9b517e19a3c6379baa7a815c97ca9_img.jpg) - -| Name | EVM (%rms) | Power per RE (dBm) | Modulation | -|-------------|------------|--------------------|------------| -| PDSCH0 | 0.011 | -32.77 | QAM256 | -| PDSCH0_DMRS | 0.010 | -32.78 | QPSK | -| PDSCH1 | 0.011 | -42.78 | QAM256 | -| PDSCH1_DMRS | 0.011 | -42.78 | QPSK | -| PDSCH2 | 0.055 | -52.78 | QAM256 | -| PDSCH2_DMRS | 0.053 | -52.78 | QPSK | -| PDCCH0 | 0.127 | -32.78 | QPSK | -| PDCCH0_DMRS | 0.126 | -32.78 | QPSK | - -Figure 3.2.5.3-59: Example Compression EVM Measurement. The figure consists of two parts: a spectrum analyzer display on the left and a data table on the right. The display shows a green signal spectrum with a center frequency of 1 GHz and a span of 96 MHz. The table provides detailed measurement data for various channels. - -Figure 3.2.5.3-59 Example Compression EVM Measurement - -- **Payload Data Integrity:** comparing user data between the O-RAN test frame and the RF measurement to validate that compression does not influence user data. The User data measurements are called: -For Downlink - -- CMP-Uncompressed-BER-DL-PDSCH0 -- CMP-Uncompressed-BER-DL-PDSCH1 -- CMP-Uncompressed-BER-DL-PDSCH2 -- CMP-Compressed-BER-DL-PDSCH0 -- CMP-Compressed-BER-DL-PDSCH1 -- CMP-Compressed-BER-DL-PDSCH2 - -For Uplink - -- CMP-Uncompressed-BER-UL-PUSCH0 -- CMP-Uncompressed-BER-UL-PUSCH1 -- CMP-Uncompressed-BER-UL-PUSCH2 -- CMP-Compressed-BER-UL-PUSCH0 -- CMP-Compressed-BER-UL-PUSCH1 -- CMP-Compressed-BER-UL-PUSCH2 - -For the data integrity test to pass, the comparison between stimulus payload and the measured payload should be free of any errors (i.e. BER=0). - -- **Presence/Absence of U-Plane Header measurements (uplink only):** to validate that in the U-Plane PRB header, the udCompHeader, “reserved” and udCompParam fields are correctly absent for Static compression mode or present for other compression modes. - -Table 3.2.5-9 below describes the measurements required for each compression option. - -**Table 3.2.5-9 Measurements Required for Specific Downlink Compression Options.** - -| Downlink | Power Level | EVM | Data Integrity | -|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| -| Uncompressed IQ (fixed 16 bits) | Perform power measurements on the 3 groups of PRBs to create 3 power reference points | Perform EVM measurements on the 3 groups of PRBs to create 3 EVM reference points | N/A | -| Fixed point (< 16 bits fixed IQ) | Perform the test using same test waveforms in compressed mode and check if 3 power measurements are within acceptable range | Perform the test using same test waveforms in compressed mode and check if 3 EVM measurements are within acceptable range | If power level and EVM OK, then verify user data integrity with BER measurement on payload | -| Block floating point | Perform the test using same test waveforms in compressed mode and check if 3 power measurements are within acceptable range | Perform the test using same test waveforms in compressed mode and check if 3 EVM measurements are within acceptable range | If power level and EVM OK, then verify user data integrity with BER measurement on payload | -| Block scaling | Same as above | Same as above | Same as above | -| Mu Law | Same as above | Same as above | Same as above | -| Block floating point + Selective RE | Same as above | Same as above | Same as above | -| Block scaling + Selective RE | Same as above | Same as above | Same as above | - -**3.2.5.3.1.6 Compression Tests reference table** - -As the same methodology is used across the different compression modes, the conformance test can be viewed as series of instances of the same test structure with different parameter values as shown below in Table 3.2.5-10. - -**Table 3.2.5-10 Compression Test Reference Table.** - -| Test name | DL/UL | Compression | IQ Width | -|------------------------------------------------------------------------------|-------|----------------------|-------------------| -| TDD UC-Plane O-RU CMP Scenario - Static Format (SF) | | | | -| TDD UC-Plane O-RU CMP Scenario Static Format (SF) Fixed-Point (FPF) | DL | Fixed point | 9 bits
14 bits | -| | UL | Fixed Point | 9 bits
14 bits | -| TDD UC-Plane O-RU CMP Scenario Static Format (SF) Block Floating Point (BFP) | DL | Block Floating point | 9 bits
14 bits | -| | UL | Block Floating point | 9 bits
14 bits | -| TDD UC-Plane O-RU CMP Scenario Static Format (SF) Block Scaling (BSC) | DL | Block Scaling | 9 bits
14 bits | -| | UL | Block Scaling | 9 bits
4 bits | - -| | | | | -|------------------------------------------------------------------------------------------|----|---------------------------------------|-------------------| -| TDD UC-Plane O-RU CMP Scenario Static Format (SF) Mu-Law (MLW) | DL | Mu-Law | 9 bits
14 bits | -| | UL | Mu-Law | 9 bits
14 bits | -| TDD UC-Plane O-RU CMP Scenario Static (SF) Block Floating Point + Selective RE (BRE) | DL | Block Floating point + Selective RE | 9 bits
14 bits | -| | UL | Block Floating point + Selective RE | 9 bits
14 bits | -| TDD UC-Plane O-RU CMP Scenario Static (SF) mod-compr Format + Selective RE (MRE) | DL | Modulation Compression + Selective RE | 4-bits | -| UC-Plane O-RU CMP Scenario - Non-Static Format Test (NS) | | | | -| TDD UC-Plane O-RU CMP Scenario Non-Static (NS) Fixed-Point (FPF) | DL | Fixed point | 9 bits
14 bits | -| | UL | Fixed Point | 9 bits
14 bits | -| TDD UC-Plane O-RU CMP Scenario Non-Static (NS) Block Floating Point (BFP) | DL | Block Floating point | 9 bits
14 bits | -| | UL | Block Floating point | 9 bits
14 bits | -| TDD UC-Plane O-RU CMP Scenario Non-Static (NS) Block Scaling (BSC) | DL | Block Scaling | 9 bits
14 bits | -| | UL | Block Scaling | 9 bits
4 bits | -| TDD UC-Plane O-RU CMP Scenario Non-Static (NS) Mu-Law (MLW) | DL | Mu-Law | 9 bits
14 bits | -| | UL | Mu-Law | 9 bits
14 bits | -| TDD UC-Plane O-RU CMP Scenario Non-Static (NS) Modulation Compressed Format | DL | Modulation Compression | 4-bits | -| TDD UC-Plane O-RU CMP Scenario Non-Static (NS) Block Floating Point + Selective RE (BRE) | DL | Block Floating point + Selective RE | 9 bits
14 bits | -| | UL | Block Floating point + Selective RE | 9 bits
14 bits | -| TDD UC-Plane O-RU CMP Scenario Non-Static (NS) mod-compr Format + Selective RE (MRE) | DL | Modulation Compression + Selective RE | 4-bits | - -### 3.2.5.3.1.7 Results Analysis - -In general, for each specific Compression Test in this conformance test document, the test will pass if the following conditions are met: - -- Power measurement differences between Uncompressed and Compressed are within acceptable range -- EVM measurement difference between Uncompressed and Compressed are within acceptable range -- Data integrity measurements show no data corruption -- Uplink U-Plane Header measurements exclude fields for static compression - -These test criteria and expected results are summarized below in Table 3.2.5-11. - -**Table 3.2.5-11 Compression Test Acceptance Threshold Criteria** - -| Test name | Test Attributes | | | Acceptance Threshold Criteria | | | -|--------------------------------------------------------------------------------------|-----------------|-------------------------------------|----------|----------------------------------------------------------------------|---------------------------------------------------------------------------------|---------| -| | DL
UL | Compression | IQ Width | Power difference | EVM difference | BER | -| TDD UC-Plane O-RU CMP Scenario Fixed-Point Format (FPF) | DL | Fixed point | 9 bits | ACC_PWR_PDSCH0 =
ACC_PWR_PDSCH1 =
ACC_PWR_PDSCH2 =
+/- 1 dB | ACC_EVM_PDSCH0 =
ACC_EVM_PDSCH1 =
ACC_EVM_PDSCH2
≤ 4 percentage points | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| | UL | Fixed Point | 9 bits | | | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| TDD UC-Plane O-RU CMP Scenario Block Floating Point Compression (BFP) | DL | Block Floating point | 9 bits | Same as above | Same as above | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| | UL | Block Floating point | 9 bits | | | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| TDD UC-Plane O-RU CMP Scenario Block Scaling Compression (BSC) | DL | Block Scaling | 9 bits | | | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| | UL | Block Scaling | 9 bits | | | BER = 0 | -| | | | 4 bits | | | BER = 0 | -| TDD UC-Plane O-DU CMP Scenario Mu-Law Compression (MLW) | DL | Mu-Law | 9 bits | | | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| | UL | Mu-Law | 9 bits | | | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| UC-Plane O-RU CMP Scenario Modulation Compressed Format | DL | Modulation Compression | 4-bits | | | BER = 0 | -| TDD UC-Plane O-RU CMP Scenario Block Floating Point Compression + Selective RE (BRE) | DL | Block Floating point + Selective RE | 9 bits | Same as above | Same as above | BER = 0 | -| | | | 14 bits | | | BER = 0 | -| | UL | Block Floating point + Selective RE | 9 bits | Same as above | Same as above | BER = 0 | -| | | | 14 bits | | | BER = 0 | - -| Test name | Test Attributes | | | Acceptance Threshold Criteria | | | -|----------------------------------------------------------------------------|-----------------|---------------------------------------|----------|-------------------------------|----------------|--------| -| | DL UL | Compression | IQ Width | Power difference | EVM difference | BER | -| TDD UC-Plane O-RU CMP Scenario Modulation Compressed + Selective RE Format | DL | Modulation Compression + Selective RE | 4-bits | Same as above | Same as above | BER =0 | - -### 3.2.5.3.2 UC-Plane O-RU Scenario Class Compression Static Format (SF) Fixed-Point (FP) - -#### A. Test Description and Applicability - -This test is CONDITIONALMANDATORY and shall be performed if the O-RU supports this compression format. - -The purpose of this test is to: - -- Validate correct encoding of IQ data under the following conditions. - - RU Static compression configurations - - Fixed point IQ data format - - Selection of 2 supported bit width: 9 bits, 14 bits - - Uplink / downlink -- Validate that in the U-Plane PRB header, the udCompHeader, “reserved” and udCompParam fields are not present - -#### B. Test Entrance Criteria - -The test uses the setup and methodology described in clause 3.2.5.3.1. - -#### C. Test Methodology - -##### a. Initial Conditions - -- The O-RU is started -- Fronthaul Ethernet interface configured for communication between TER and the DUT. -- O-RU synchronized with TER using S-Plane -- Communication established between TER and the DUT such that it is possible to exchange U-Plane and C-Plane messages -- signal analyser connected to DUT’s antenna port and setup according to DUT RF output configuration -- signal source connected to DUT’s antenna port and setup according to DUT RF input configuration - -##### b. Procedure - -For each supported bit width (9 bits, 14 bits), the following tests need to be performed: - -###### 1. Launch Uncompressed Test - -- Via the M-Plane or another suitable mechanism, put the O-RU into a static configuration with the downlink and uplink configured as follows: no compression, (16 bits) -- Arm signal analysers and signal source -- Arm signal analyser to capture the next Frame -- Arm signal source to generate the Frame NR-FR1-CMP-TST-FRAME-UL -- Arm the CUSM emulator to send the TDD O-RAN test frame, including - -- Downlink: CU-plane of “uncompressed” NR-FR1-TDD-CMP-TST-ST-DL-UNC-16B test stimulus file to the DUT -- Uplink: C-plane of “uncompressed” NR-FR1-TDD-CMP-TST-ST-UL-UNC-16B test stimulus file to the DUT -- ARM CUSM-E to capture the Uplink U-Plane Data from the DUT -- Launch the test until: - - RF signal analyser has captured the downlink frame - - CUSM-E has captured the uplink U-plane data - -**2. Uncompressed Downlink Measurements** - -- With the RF signal analyser, perform the 3 power measurements - - CMP-Uncompressed-Measured-Power-DL-PDSCH0 in dBm - - CMP-Uncompressed-Measured-Power-DL-PDSCH1 in dBm - - CMP-Uncompressed-Measured-Power-DL-PDSCH2 in dBm -- With the RF signal analyser, perform the 3 EVM measurements - - CMP-Uncompressed-Measured-EVM-DL-PDSCH0 in % - - CMP-Uncompressed-Measured-EVM-DL-PDSCH1 in % - - CMP-Uncompressed-Measured-EVM-DL-PDSCH2 in % -- With the RF signal analyser, check Data integrity measurements - - CMP-Uncompressed-BER-DL-PDSCH0 - - CMP-Uncompressed-BER-DL-PDSCH1 - - CMP-Uncompressed-BER-DL-PDSCH2 - -**3. Uncompressed Uplink Measurements** - -- Extract IQ information from Capture U-Plane trace of the CUSM-E -- Using the signal analyser software, perform the 3 power measurements - - CMP-Uncompressed-Measured-Power-UL-PDSCH0 in dBm - - CMP-Uncompressed-Measured-Power-UL-PDSCH1 in dBm - - CMP-Uncompressed-Measured-Power-UL-PDSCH2 in dB -- Using the signal analyser software, perform the 3 EVM measurements - - CMP-Uncompressed-Measured-EVM-UL-PDSCH0 in % - - CMP-Uncompressed-Measured-EVM-UL-PDSCH1 in % - - CMP-Uncompressed-Measured-EVM-UL-PDSCH2 in % -- Using the signal analyser software, perform Data integrity measurements - - CMP-Uncompressed-BER-UL-PDSCH0 - - CMP-Uncompressed-BER-UL-PDSCH1 - - CMP-Uncompressed-BER-UL-PDSCH2 - -**4. Launch “compressed” Test** - -- Via the M-Plane or another suitable mechanism, put the O-RU into a static configuration with the downlink and uplink configured as follows: Fixed point, 9-bit (then 14 bits) -- Arm signal analysers and signal sources -- Arm signal analyser to capture the next Frame -- Arm signal source to generate the Frame NR-FR1-CMP-TST-FRAME-UL -- Arm the CUSM emulator to send the TDD O-RAN test frame, including -- Downlink: CU-plane of the “Compressed” NR-FR1-TDD-CMP-TST-ST-DL-FPF-9B (then 14B) test stimulus file to the DUT -- Uplink: CU-plane of the “Compressed” NR-FR1-TDD-CMP-TST-ST-UL-FPF-9B (then 14B) test stimulus file to the DUT -- ARM CUSM-E to capture the Uplink U-Plane Data from the DUT -- Launch the test until: - - RF signal analyser has captured the downlink frame - -- CUSM-E has captured the uplink U-plane data - -## 5. Compressed Downlink Measurements - -- With the signal analyser, perform the 3 power measurements - - CMP-Compressed-Measured-Power-DL-PDSCH0 in dBm - - CMP-Compressed-Measured-Power-DL-PDSCH1 in dBm - - CMP-Compressed-Measured-Power-DL-PDSCH2 in dBm -- With the signal analyser, perform the 3 EVM measurements - - CMP-Compressed-Measured-EVM-DL-PDSCH0 in % - - CMP-Compressed-Measured-EVM-DL-PDSCH1 in % - - CMP-Compressed-Measured-EVM-DL-PDSCH2 in % -- With the signal analyser, check Data integrity measurements - - CMP-Compressed-BER-DL-PDSCH0 - - CMP-Compressed-BER-DL-PDSCH1 - - CMP-Compressed-BER-DL-PDSCH2 - -## 6. Validate Downlink conformance conditions - -- Power measurements within acceptable range -- Difference between CMP-Uncompressed-Measured-Power-DL-PDSCH0 and CMP-Compressed-Measured-Power-DL-PDSCH0 is within ACC\_PWR\_PDSCH0 range -- Difference between CMP-Uncompressed-Measured-Power-DL-PDSCH1 and CMP-Compressed-Measured-Power-DL-PDSCH1 is within ACC\_PWR\_PDSCH1 range -- Difference between CMP-Uncompressed-Measured-Power-DL-PDSCH2 and CMP-Compressed-Measured-Power-DL-PDSCH2 is within ACC\_PWR\_PDSCH2 range -- EVM measurements within acceptable range -- Difference between CMP-Uncompressed-Measured-EVM-DL-PDSCH0 and CMP-Compressed-Measured-EVM-DL-PDSCH0 is less than ACC\_EVM\_PDSCH0 -- Difference between CMP-Uncompressed-Measured-EVM-DL-PDSCH1 and CMP-Compressed-Measured-EVM-DL-PDSCH1 is less than ACC\_EVM\_PDSCH1 -- Difference between CMP-Uncompressed-Measured-EVM-DL-PDSCH2 and CMP-Compressed-Measured-EVM-DL-PDSCH2 is less than ACC\_EVM\_PDSCH2 -- BER Measurements show no errors - - CMP-Uncompressed-BER-DL-PDSCH0 =0 - - CMP-Uncompressed-BER-DL-PDSCH1 =0 - - CMP-Uncompressed-BER-DL-PDSCH2 =0 - - CMP-Compressed-BER-DL-PDSCH0 =0 - - CMP-Compressed-BER-DL-PDSCH1 =0 - - CMP-Compressed-BER-DL-PDSCH2 =0 - -## 7. Compressed Uplink Measurements - -- Extract IQ information from Capture U-Plane trace -- Using the signal analyser software, perform the 3 power measurements - - CMP-Compressed-Measured-Power-UL-PDSCH0 in dBm - - CMP-Compressed-Measured-Power-UL-PDSCH1 in dBm - - CMP-Compressed-Measured-Power-UL-PDSCH2 in dBm -- Using the signal analyser software, perform the 3 EVM measurements - - CMP-Compressed-Measured-EVM-UL-PDSCH0 in % - - CMP-Compressed-Measured-EVM-UL-PDSCH1 in % - - CMP-Compressed-Measured-EVM-UL-PDSCH2 in % -- Using the signal analyser software, check Data integrity measurements - - CMP-Compressed-BER-UL-PDSCH0 - - CMP-Compressed-BER-UL-PDSCH1 - -- CMP-Compressed-BER-UL-PDSCH2 - -#### 8. Validate Uplink conformance conditions - -- Validate correct U-Plane PRB header structure -- U-Plane udComphdr (clause 8.3.3.13 of [2]) -- U-Plane udCompParam (clause 8.3.3.15 of [2]) -- Validate that the power measurements within acceptable range - - Difference between CMP-Uncompressed-Measured-Power-UL-PDSCH0 and CMP-Compressed-Measured-Power-UL-PDSCH0 is within ACC\_PWR\_PDSCH0 range - - Difference between CMP-Uncompressed-Measured-Power-UL-PDSCH1 and CMP-Compressed-Measured-Power-UL\_PDSCH1 is within ACC\_PWR\_PDSCH1 range - - Difference between CMP-Uncompressed-Measured-Power-UL-PDSCH2 and CMP-Compressed-Measured-Power-UL\_PDSCH2 is within ACC\_PWR\_PDSCH2 range -- Validate EVM measurements within acceptable range - - Difference between CMP-Uncompressed-Measured-EVM-UL-PDSCH0 and CMP-Compressed-Measured-EVM-UL-PDSCH0 is less than ACC\_EVM\_PDSCH0 - - Difference between CMP-Uncompressed-Measured-EVM-UL-PDSCH1 and CMP-Compressed-Measured-EVM-UL-PDSCH1 is less than ACC\_EVM\_PDSCH1 - - Difference between CMP-Uncompressed-Measured-EVM-UL-PDSCH2 and CMP-Compressed-Measured-EVM-UL-PDSCH2 is less than ACC\_EVM\_PDSCH2 -- Validate that the BER Measurements show no errors - - CMP-Uncompressed-BER-UL-PDSCH0 = 0 - - CMP-Uncompressed-BER-UL-PDSCH1 = 0 - - CMP-Uncompressed-BER-UL-PDSCH2 = 0 - - CMP-Compressed-BER-UL-PDSCH0 = 0 - - CMP-Compressed-BER-UL-PDSCH1 = 0 - - CMP-Compressed-BER-UL-PDSCH2 = 0 - -#### D. Test Requirement (expected result) - -All validation steps above are within expected ranges or correctly match the expected outcome. - -### 3.2.5.3.3 UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Floating Point (BFP) - -#### A. Test Description and Applicability - -This test is CONDITIONALMANDATORY and shall be performed if the O-RU supports this compression format. This static format test scenario for Block Floating Point Format will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -#### B. Test Entrance Criteria - -Same as in clause 3.2.5.3.2 for Block floating point formats. - -#### C. Test Methodology - -Same as with Static Block Floating Point test patterns - -- NR-FR1-TDD-CMP-TST-ST-DL-BFP-9B -- NR-FR1-TDD-CMP-TST-ST-DL-BFP-14B -- NR-FR1-TDD-CMP-TST-ST-UL-BFP-9B -- NR-FR1-TDD-CMP-TST-ST-UL-BFP-14B - -Via the M-Plane or another suitable mechanism, put the O-RU into a static configuration with the downlink and uplink configured as follows: Block floating Point, 9-bit (then 14 bits) - -**D. Test Requirement (expected result)** - -Same as in clause 3.2.5.3.2. - -**3.2.5.3.4 UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Scaling** - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format. -This static format test scenario for Block Scaling Format will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -**B. Test Entrance Criteria** - -Same as in clause 3.2.5.3.2 for Block Scaling point formats. - -**C. Test Methodology** - -Same as in clause 3.2.5.3.2 with Static Block Floating Point test patterns - -- NR-FR1-TDD-CMP-TST-ST-DL-BSC-9B -- NR-FR1-TDD-CMP-TST-ST-DL-BSC-14B -- NR-FR1-TDD-CMP-TST-ST-UL-BSC-9B -- NR-FR1-TDD-CMP-TST-ST-UL-BSC-14B - -Via the M-Plane or another suitable mechanism, put the O-RU into a static configuration with the downlink and uplink configured as follows: Block Scaling, 9-bit (then 14 bits) - -**D. Test Requirement (expected result)** - -Same as in clause 3.2.5.3.2. - -**3.2.5.3.5 UC-Plane O-RU Scenario Class Compression Static Format (SF) Mu-Law (MLW)** - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format. - -This static format test scenario for Mu-Law Format will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -**B. Test Entrance Criteria** - -Same as in clause 3.2.5.3.2 for Mu-Law formats. - -**C. Test Methodology** - -Same as in clause 3.2.5.3.2 with Static Mu-Law test patterns - -- NR-FR1-TDD-CMP-TST-ST-DL-MLW-9B -- NR-FR1-TDD-CMP-TST-ST-DL-MLW-14B -- NR-FR1-TDD-CMP-TST-ST-UL-MLW-9B -- NR-FR1-TDD-CMP-TST-ST-UL-MLW-14B - -Via the M-Plane or another suitable mechanism, put the O-RU into a static configuration with the downlink and uplink configured as follows: Mu-Law, 9-bit (then 14 bits) - -**D. Test Requirement (expected result)** - -Same as in clause 3.2.5.3.2. - -**3.2.5.3.6 UC-Plane O-RU Scenario Class Compression Static Format (SF) Modulation-Compression** - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format. - -This modulation compression format scenario is a static format scenario, based on clause 3.2.5.3.2 with some important differences - -- The purpose is to validate Radio Unit's correct interpretation of the Modulation compression parameters used in the Section Extension Type =4 and/or Section Extension Type 5, based on the radio support. -If the O-RU only supports section extension 4 on a given endpoint, then: - - Section extension 4 shall be used for all symbols containing PDSCH REs and for symbols containing both PDSCH and DMRS REs. - -If the O-RU only supports section extension 5 on a given endpoint, then: - -- Section extension 5 shall be used for all symbols containing PDSCH REs and for symbols containing both PDSCH and DMRS REs. - -If the radio supports 4 and 5 on a given endpoint, then - -- Section extension 4 shall be used for symbols containing only PDSCH REs . -- Section extensions 5 shall be used for symbols containing DMRS + PDSCH REs. - -![Figure 3.2.5.3-3: A resource grid for DL-SCH0 showing SubCarrier (0-12) vs Symbol (0-14). A red box highlights 'Section extension 5' at symbols 2-3, containing pink blocks. A grey box highlights 'Section extension 4' from symbol 4 to 14, containing green blocks.](81550473b76180b6088795cbfd708d52_img.jpg) - -Figure 3.2.5.3-3: A resource grid for DL-SCH0 showing SubCarrier (0-12) vs Symbol (0-14). A red box highlights 'Section extension 5' at symbols 2-3, containing pink blocks. A grey box highlights 'Section extension 4' from symbol 4 to 14, containing green blocks. - -Figure 3.2.5.3-3 Section Extension 4 and 5 signalling - -- The test will only verify DL correct encoding of IQ information, as the Modulation Compression model is not applicable for uplink -- As the Modulation Compression model does not require IQ bit width to be setup, there is no need to run multiple compression tests for various IQ bit width. -- The CUSM\_E must generate: - -Table 3.2.5-12 SFM Modulation Compression. - -| Stimulus File Name | Description | -|----------------------------------|-----------------------------------------| -| NR-FR1-TDD-CMP-TST-ST-DL-UNC-16B | Static Downlink Uncompressed (CU-plane) | -| NR-FR1-TDD-CMP-TST-ST-DL-MC | Static Downlink Modulation Compression | - -**B. Test Entrance Criteria** - -Same as in clause 3.2.5.3.2. - -**C. Test Methodology** - -Same as in clause 3.2.5.3.2 with Static Modulation Compression test patterns - -- NR-FR1-TDD-CMP-TST-ST-DL-MC - -Via the M-Plane or another suitable mechanism, put the O-RU into a static configuration with the downlink configured as follow: Modulation Compression - -- Validation only of the downlink measurements - -**D. Test Requirement (expected result)** - -All validation steps above are within expected ranges or correctly match the expected outcome. - -### 3.2.5.3.7 UC-Plane O-RU Scenario Class Compression Non-Static (NS) Fixed-Point (FPF) - -#### A. Test Description and Applicability - -This test is CONDITIONALMANDATORY and shall be performed if the O-RU supports this compression format. This Fixed-Point Format scenario is a non-static format scenario that will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -#### B. Test Entrance Criteria - -Same as in clause 3.2.5.3.2. - -#### C. Test Methodology - -Same as in clause 3.2.5.3.2 and clause 3.2.3.3.2 with Non-Static Uncompressed test patterns. - -- NR-FR1-TDD-CMP-TST-NS-DL-UNC-16B -- NR-FR1-TDD-CMP-TST-NS-UL-UNC-16B - -Same as in clause 3.2.3.3.2 with Non-Static Fixed-Point (FPF) test patterns. - -- NR-FR1-TDD-CMP-TST-NS-DL-FPF-9B -- NR-FR1-TDD-CMP-TST-NS-DL-FPF-14B -- NR-FR1-TDD-CMP-TST-NS-UL-FPF-9B -- NR-FR1-TDD-CMP-TST-NS-UL-FPF-14B - -Via the M-Plane or another suitable mechanism, put the O-RU into a non-static configuration with the downlink and uplink configured as follows: Fixed Point, 9-bit (then 14 bits) - -#### D. Test Requirement (expected result) - -All validation steps above are within expected ranges or correctly match the expected outcome. - -### 3.2.5.3.8 UC-Plane O-RU Scenario Class Compression Non-Static (NS) Block Floating Point - -#### A. Test Description and Applicability - -This test is CONDITIONALMANDATORY and shall be performed if the O-RU supports this compression format. This Block Floating-Point Format scenario is a non-static format scenario that will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -#### B. Test Entrance Criteria - -Same as in clause 3.2.5.3.7 for Block floating point formats. - -#### C. Test Methodology - -Same as in clause 3.2.5.3.7 with Non-Static Uncompressed test patterns. - -- NR-FR1-TDD-CMP-TST-NS-DL-UNC-16B -- NR-FR1-TDD-CMP-TST-NS-UL-UNC-16B - -Same as in clause 3.2.5.3.7 with Non-Static Fixed-Point (FPF) test patterns. - -- NR-FR1-TDD-CMP-TST-NS-DL-BFP-9B -- NR-FR1-TDD-CMP-TST-NS-DL-BFP-14B -- NR-FR1-TDD-CMP-TST-NS-UL-BFP-9B - -- NR-FR1-TDD-CMP-TST-NS-UL-BFP-14B - -Via the M-Plane or another suitable mechanism, put the O-RU into a non-static configuration with the downlink and uplink configured as follows: Block Floating Point, 9-bit (then 14 bits) - -#### D. Test Requirement (expected result) - -Same as in clause 3.2.5.3.7. - -### 3.2.5.3.9 UC-Plane O-RU Scenario Class Compression Non-Static (NS) Block Scaling (BSC) - -#### A. Test Description and Applicability - -This test is CONDITIONALMANDATORY and shall be performed if the O-RU supports this compression format. This Block Scaling Format scenario is a dynamic-format scenario that will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -#### B. Test Entrance Criteria - -Same as in clause 3.2.5.3.7 for Block Scaling formats. - -#### C. Test Methodology - -Same as in clause 3.2.5.3.7 with Non-Static Uncompressed test patterns. - -- NR-FR1-TDD-CMP-TST-NS-DL-UNC-16B -- NR-FR1-TDD-CMP-TST-NS-UL-UNC-16B - -Same as in clause 3.2.5.3.7 with Non-Static Fixed-Point (FPF) test patterns. - -- NR-FR1-TDD-CMP-TST-NS-DL-BSC-9B -- NR-FR1-TDD-CMP-TST-NS-DL-BSC-14B -- NR-FR1-TDD-CMP-TST-NS-UL-BSC-9B -- NR-FR1-TDD-CMP-TST-NS-UL-BSC-14B - -Via the M-Plane or another suitable mechanism, put the O-RU into a non-static configuration with the downlink and uplink configured as follows: Block Scaling, 9-bit (then 14 bits) - -#### D. Test Requirement (expected result) - -Same as in clause 3.2.5.3.7. - -### 3.2.5.3.10 UC-Plane O-RU Scenario Class Compression Non-Static (NS) Mu-Law (MLW) - -#### A. Test Description and Applicability - -This test is CONDITIONALMANDATORY and shall be performed if the O-RU supports this compression format. This Mu-Law Format scenario is a dynamic-format scenario that will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -#### B. Test Entrance Criteria - -Same as in clause 3.2.5.3.7 for Mu-Law formats. - -### C. Test Methodology - -Same as in clause 3.2.5.3.7 with Non-Static Uncompressed test patterns. - -- NR-FR1-TDD-CMP-TST-NS-DL-UNC-16B -- NR-FR1-TDD-CMP-TST-NS-UL-UNC-16B - -Same as in clause 3.2.5.3.7 with Non-Static Fixed-Point (FPF) test patterns. - -- NR-FR1-TDD-CMP-TST-NS-DL-MLW-9B -- NR-FR1-TDD-CMP-TST-NS-DL-MLW-14B -- NR-FR1-TDD-CMP-TST-NS-UL-MLW-9B -- NR-FR1-TDD-CMP-TST-NS-UL-MLW-14B - -Via the M-Plane or another suitable mechanism, put the O-RU into a non-static configuration with the downlink and uplink configured as follows: Mu Law, 9-bit (then 14 bits) - -### D. Test Requirement (expected result) - -Same as in clause 3.2.5.3.7. - -## 3.2.5.3.11 UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) Modulation-Compressed Format - -### A. Test Description and Applicability - -This test is **CONDITIONALMANDATORY** and shall be performed if the O-RU supports this compression format. - -This modulation compression format scenario is a non-static format scenario, based on 3.2.4.3.2 with some important differences - -- The purpose is to validate Radio Unit's correct interpretation of the Modulation compression parameters used in the Section Extension Type =4 and/or Section Extension Type 5, based on the radio support. If the O-RU only supports section extension 4 on a given endpoint, then: - - Section extension 4 shall be used for all symbols containing PDSCH REs and for symbols containing both PDSCH and DMRS REs. - -If the O-RU only supports section extension 5 on a given endpoint, then: - -- Section extension 5 shall be used for all symbols containing PDSCH REs and for symbols containing both PDSCH and DMRS REs. - -If the radio supports 4 and 5 on a given endpoint, then - -- Section extension 4 shall be used for symbols containing only PDSCH REs . -- Section extensions 5 shall be used for symbols containing DMRS + PDSCH REs. - -![Figure 3.2.5.3-4: A grid representing DL-SCH0 signaling. The vertical axis is labeled 'SubCarrier' with values 0, 2, 4, 6, 8, 10, 12. The horizontal axis is labeled 'Symbol' with values 0, 2, 4, 6, 8, 10, 12, 14. A red rectangle labeled 'Section extension 5' encloses symbols 2 and 3 across subcarriers 0 to 12. A grey rectangle labeled 'Section extension 4' encloses symbols 4 to 14 across subcarriers 0 to 12. Pink rectangular blocks are located at (Symbol 2, Subcarriers 2, 4, 6, 8, 10) and (Symbol 3, Subcarriers 2, 4, 6, 8, 10).](206b1499a4b866d040aff98bd29a8d17_img.jpg) - -Figure 3.2.5.3-4: A grid representing DL-SCH0 signaling. The vertical axis is labeled 'SubCarrier' with values 0, 2, 4, 6, 8, 10, 12. The horizontal axis is labeled 'Symbol' with values 0, 2, 4, 6, 8, 10, 12, 14. A red rectangle labeled 'Section extension 5' encloses symbols 2 and 3 across subcarriers 0 to 12. A grey rectangle labeled 'Section extension 4' encloses symbols 4 to 14 across subcarriers 0 to 12. Pink rectangular blocks are located at (Symbol 2, Subcarriers 2, 4, 6, 8, 10) and (Symbol 3, Subcarriers 2, 4, 6, 8, 10). - -Figure 3.2.5.3-4 Section Extension 4 and 5 signalling - -- The test will only verify DL correct encoding of IQ information, as the Modulation Compression model is not applicable for uplink -- As the Modulation Compression model does not require IQ bit width to be setup, there is no need to run multiple compression tests for various IQ bit width. -- The CUSM\_E must generate: - -Table 3.2.5-13 Non-static Modulation compression. - -| Stimulus File Name | Description | -|----------------------------------|---------------------------------------------| -| NR-FR1-TDD-CMP-TST-NS-DL-UNC-16B | Non-Static Downlink Uncompressed (CU-plane) | -| NR-FR1-TDD-CMP-TST-NS-DL-MC | Non-Static Downlink Modulation Compression | - -**B. Test Entrance Criteria** - -Same as in clause 3.2.5.3.7. - -**C. Test Methodology** - -Same as in clause 3.2.5.3.7 with Static Modulation Compression test patterns - -- NR-FR1-TDD-CMP-TST-NS-DL-MC - -Via the M-Plane or another suitable mechanism, put the O-RU into a static configuration with the downlink configured as follow: Modulation Compression - -- Validation only of the downlink measurements - -**D. Test Requirement (expected result)** - -All validation steps above are within expected ranges or correctly match the expected outcome. - -### 3.2.5.3.12 UC-Plane O-RU Scenario Class Compression Static Format (SF) Block Floating Point + Selective RE Format - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY and shall be performed if the O-RU supports this compression format - -The Block Floating-Point+ Selective RE Format scenario is a static format scenario that will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. - -For this test scenario, the compression test methodology will be based on the description in clause 3.2.5.3.1 - -However, on top of the test frame requirements from clause 3.2.5.3.1, this test scenario also requires a test frame that MUST include PRBs with a combination of allocated and empty Resource Elements in the same symbol, to verify if the O-RU properly interprets the sReMask value in the udCompParam field (user data compression parameter). The measurements must be performed on the symbols that include a combination of empty and allocated resource elements. - -The recommended test frame is based on Type 2 DMRS with 2 DMRS CDM groups without data. The resource mapping model for the Resource Blocks is shown on the diagram below, where both symbols #2 and #11 include a combination of empty and allocated Resources. - -![RB Resource Mapping for DL-SCH1 (Modulation = QPSK) showing subcarriers 0-12 and symbols 0-13. Symbols 2 and 11 show a combination of red (allocated) and grey (empty) resource elements.](c5ec27fa66024712e34aec3f57c0430c_img.jpg) - -The figure is a grid titled "RB Resource Mapping for DL-SCH1 (Modulation = QPSK)". The vertical axis is labeled "Subcarrier" and ranges from 0 to 12. The horizontal axis is labeled "Symbol" and ranges from 0 to 13. The grid cells are mostly green. In Symbol 2, Subcarriers 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, and 12 are red, while Subcarrier 0 is grey. In Symbol 11, Subcarriers 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, and 12 are red, while Subcarrier 0 is grey. All other cells in the grid are green. - -RB Resource Mapping for DL-SCH1 (Modulation = QPSK) showing subcarriers 0-12 and symbols 0-13. Symbols 2 and 11 show a combination of red (allocated) and grey (empty) resource elements. - -Figure 3.2.5.3-5 Recommended Frame ST BFP + Selective RE - -The uncompressed and compressed test frames are listed in Table 3.2.5-14. - -**Table 3.2.5-14 Stimulus Files for ST BFP + Selective RE.** - -| Stimulus File Name | Description | -|---------------------------------------|-----------------------------------------------------------------------------------------------| -| NR-FR1-TDD -CMP-TST -ST-DL-UNC-RE-16B | Static Downlink Uncompressed (CU-plane) with both empty and allocated RE in the same symbol | -| NR-FR1-TDD -CMP-TST -ST-UL-UNC-RE-16B | Static Uplink Uncompressed (C-plane only) with both empty and allocated RE in the same symbol | -| NR-FR1-TDD-CMP-TST-ST-DL-BRE-9B | Static Downlink Block Floating Point + Selective RE 9 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-ST-DL-BRE-14B | Static Downlink Block Floating Point + Selective RE 14 Bits (CU-plane) | -| NR-FR1-TDD-CMP-TST-ST-UL-BRE-9B | Static Uplink Block Floating Point 9 Bits + Selective RE (C-plane only) | -| NR-FR1-TDD-CMP-TST-ST-UL-BRE-14B | Static Uplink Block Floating Point 14 Bits + Selective RE (C-plane only) | - -**A. Test Entrance Criteria** - -Same as in clause 3.2.3.3.2 for static Block floating point + Selective RE formats. - -**B. Test Methodology** - -Same as in clause 3.2.3.3.2 with Static Block Floating Point + Selective RE test patterns. - -The uncompressed test frames used for this test are - -- NR-FR1-TDD -CMP-TST -ST-DL-UNC-RE-16B -- NR-FR1-TDD -CMP-TST -ST-UL-UNC-RE-16B - -The compressed test frames used for this test are - -- NR-FR1-TDD-CMP-TST-ST-DL-BRE-9B -- NR-FR1-TDD-CMP-TST-ST-DL-BRE-14B -- NR-FR1-TDD-CMP-TST-ST-UL-BRE-9B -- NR-FR1-TDD-CMP-TST-ST-UL-BRE-14B - -**C. Test Requirement (expected result)** - -Same as in clause 3.2.3.3.2. - -**3.2.5.3.13 UC-Plane O-RU Scenario Class Compression Static Format (SF) mod-compr + Selective RE Format** - -**A. Test Description and Applicability** - -This test is CONDITIONALMANDATORY and shall be performed if the O-RU supports this compression format. - -This modulation compression + Selective format scenario is a static format scenario, based on 3.2.3.3.2 with some important differences - -- The purpose is to validate Radio Unit’s correct interpretation of the Modulation compression parameters used in the Section Extension Type =4 - -- The test will only verify Downlink correct encoding of IQ information, as the Modulation Compression model is not applicable for uplink -- As the Modulation Compression model does not require IQ bit width to be setup, there is no need to run multiple compression tests for various IQ bit widths. - -On top of the test frame requirements described above, this test scenario requires a test frame that MUST include PRBs with a combination of allocated and empty Resource Elements in the same symbol, to verify if the O-RU properly interprets the sReMask value in the udCompParam field (user data compression parameter). The measurements must be performed on the symbols that include a combination of empty and allocated resource elements. - -The recommended test frame is based on Type 2 DMRS with 2 DMRS CDM groups without data. The resource mapping model for the Resource Blocks is shown on the diagram below, where both symbols #2 and #11 include a combination of empty and allocated Resources. - -![RB Resource Mapping for DL-SCH1 (Modulation = QPSK) diagram showing subcarriers 0-12 on the y-axis and symbols 0-13 on the x-axis. Resource elements are colored red (allocated) or grey (empty) in symbols 2 and 11.](f2ff13547dd0687104e2b303147769cf_img.jpg) - -| Symbol | Subcarriers | Color | -|--------|--------------|-------| -| 2 | 0, 1, 2, 3 | Red | -| 2 | 4, 5, 6, 7 | Grey | -| 2 | 8, 9, 10, 11 | Red | -| 2 | 12 | Grey | -| 11 | 0, 1, 2, 3 | Red | -| 11 | 4, 5, 6, 7 | Grey | -| 11 | 8, 9, 10, 11 | Red | -| 11 | 12 | Grey | - -RB Resource Mapping for DL-SCH1 (Modulation = QPSK) diagram showing subcarriers 0-12 on the y-axis and symbols 0-13 on the x-axis. Resource elements are colored red (allocated) or grey (empty) in symbols 2 and 11. - -Figure 3.2.5.3-6 Frame Format SF Mod-comp + Selective RE - -The uncompressed and compressed test frames are listed in the table below - -Table 3.2.5-15 Stimulus Files SF Mod-comp Selective RE. - -| Stimulus File Name | Description | -|---------------------------------------|---------------------------------------------------------------------------------------------| -| NR-FR1-TDD -CMP-TST -ST-DL-UNC-RE-16B | Static Downlink Uncompressed (CU-plane) with both empty and allocated RE in the same symbol | -| TDD-NR-FR1-CMP-TST-FRAME-ST-DL-MRE | Static Downlink Modulation Compression + Selective RE | - -**B. Test Entrance Criteria** - -Same as 3.2.5.3.2. - -**C. Test Methodology** - -Same as in clause 3.2.3.3.2 with Static Modulation Compression test patterns - -The uncompressed test frames used for this test are - -- TDD-NR-FR1-CMP-TST-FRAME-ST-DL-UNC-RE-16B - -The compressed test frames used for this test are - -- TDD-NR-FR1-CMP-TST-FRAME-ST-DL-MRE - -Via the M-Plane or another suitable mechanism, put the O-RU into a static configuration with the downlink configured as follow: Modulation Compression + Selective RE - -- D. Test Requirement (expected result)** -Same as in clause 3.2.3.3.2. - -**3.2.5.3.14 UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) Block Floating Point + Selective RE Format** - -**A. Test Description and Applicability** - -This test is CONDITIONALMANDATORY and shall be performed if the O-RU supports this compression format. - -This Block Floating-Point+ Selective RE Format scenario is a non-static format scenario that will verify DL and UL correct encoding of IQ information for 2 supported bit widths: 9 bits or 14 bits. For this test scenario, the compression test methodology will be based on the description in clause 3.2.3.3.1 - -However, on top of the test frame requirements from clause 3.2.3.3.1, this test scenario also requires a test frame that MUST include PRBs with a combination of allocated and empty Resource Elements in the same symbol, to verify if the O-RU properly interprets the sReMask value in the udCompParam field (user data compression parameter). The measurements must be performed on the symbols that include a combination of empty and allocated resource elements. - -A test frame example can be based on Type 2 DMRS with 2 DMRS CDM groups without data. The resource mapping model for the Resource Blocks is shown on the diagram below, where both symbols #2 and #11 include a combination of empty and allocated Resources. - -![RB Resource Mapping for DL-SCH1 (Modulation = QPSK) diagram showing subcarriers 0-13 on the x-axis and symbols 0-12 on the y-axis. Symbols 2 and 11 show a combination of red (allocated) and grey (empty) resource elements.](cf5102cda8bec68df2a5a4a976bfc287_img.jpg) - -RB Resource Mapping for DL-SCH1 (Modulation = QPSK) diagram showing subcarriers 0-13 on the x-axis and symbols 0-12 on the y-axis. Symbols 2 and 11 show a combination of red (allocated) and grey (empty) resource elements. - -**Figure 3.2.5.3-7 Frame Format Comp NS BFP + Selective RE** - -The uncompressed and compressed test frames are listed in the table below. - -**Table 3.2.5-16 Stimulus Files for Comp NS BFP + Selective RE.** - -| Stimulus File Name | Description | -|-------------------------------------------|---------------------------------------------------------------------------------------------------| -| TDD-NR-FR1-CMP-TST-FRAME-NS-DL-UNC-RE-16B | Non-Static Downlink Uncompressed (CU-plane) with both empty and allocated RE in the same symbol | -| TDD-NR-FR1-CMP-TST-FRAME-NS-UL-UNC-RE-16B | Non-Static Uplink Uncompressed (C-plane only) with both empty and allocated RE in the same symbol | - -| | | | -|-----------|----------------------------------------|------------------------------------------------------------------------------| -| B. | TDD-NR-FR1-CMP-TST-FRAME-NS-DL-BRE-9B | Non-Static Downlink Block Floating Point + Selective RE 9 Bits (CU-plane) | -| | TDD-NR-FR1-CMP-TST-FRAME-NS-DL-BRE-14B | Non-Static Downlink Block Floating Point + Selective 14 Bits (CU-plane) | -| | TDD-NR-FR1-CMP-TST-FRAME-NS-UL-BRE-9B | Non-Static Uplink Block Floating Point 9 Bits + Selective RE (C-plane only) | -| | TDD-NR-FR1-CMP-TST-FRAME-NS-UL-BRE-14B | Non-Static Uplink Block Floating Point 14 Bits + Selective RE (C-plane only) | - -**Test Entrance Criteria** - -Same as 3.2.5.3.7 for Non-Static Block floating point + Selective RE formats. - -**C. Test Methodology** - -Same as in clause 3.2.3.3.2 with Non-Static Block Floating Point + Selective RE test patterns - -The uncompressed test frames used for this test are - -- TDD-NR-FR1-CMP-TST-FRAME-NS-DL-UNC-BRE-16B -- TDD-NR-FR1-CMP-TST-FRAME-NS-UL-UNC-BRE-16B - -The compressed test frames used for this test are - -- TDD-NR-FR1-CMP-TST-FRAME-NS-DL-BRE-9B -- TDD-NR-FR1-CMP-TST-FRAME-NS-DL-BRE-14B -- TDD-NR-FR1-CMP-TST-FRAME-NS-UL-BRE-9B -- TDD-NR-FR1-CMP-TST-FRAME-NS-UL-BRE-14B - -**D. Test Requirement (expected result)** - -Same as in clause 3.2.3.3.2. - -**3.2.5.3.15 UC-Plane O-RU Scenario Class Compression Non-Static Format (NS) mod-compr + Selective RE Format** - -**A. Test Description and Applicability** - -This test is CONDITIONALMANDATORY and shall be performed if the O-RU supports this compression format. - -This Modulation Compression + Selective RE Format scenario is a non-static format scenario that will verify DL correct encoding of IQ information. - -This is the same as 3.2.5.3.13 with Non-Static test frames - -The uncompressed and compressed test frames are listed in the table below - -**Table 3.2.5-17 Stimulus File NS Mod Comp Selective RE.** - -| Stimulus File Name | Description | -|---------------------------------------|-------------------------------------------------------------------------------------------------| -| NR-FR1-TDD -CMP-TST -NS-DL-UNC-RE-16B | Non-Static Downlink Uncompressed (CU-plane) with both empty and allocated RE in the same symbol | -| NR-FR1-TDD -CMP-TST -NS-DL-MRE | Non-Static Downlink Modulation Compression + Selective RE | - -#### B. Test Entrance Criteria - -Same as 3.2.5.3.12 for non-static Modulation Compression + Selective RE formats. - -#### C. Test Methodology - -Same as in clause 3.2.3.3.2 with Non-Static Block Floating Point + Selective RE test patterns - -The uncompressed test frames used for this test are - -- NR-FR1-TDD -CMP-TST -NS-DL-UNC-RE-16B - -The compressed test frames used for this test are - -- NR-FR1-TDD -CMP-TST -NS-DL-MRE - -#### D. Test Requirement (expected result) - -Same as in clause 3.2.3.3.2. - -### 3.2.5.4 UC-Plane O-RU Scenario Class Delay Management (DLM) - -The delay management tests for FR1 TDD Conducted are the same as the tests described in clause 3.2.3.4, except that the TDD waveforms are to be used as shown in clause 3.2.1.1.3. The tests for uplink and downlink may be executed independently as described in the corresponding FDD test case for Delay Management or the tester may choose to combine the uplink and downlink tests into a single test. - -### 3.2.5.5 UC-Plane O-RU Scenario Class Transport (TRN) - -This test is for future study. - -### 3.2.5.6 UC-Plane O-RU Scenario Class LAA (LAA) - -The LAA tests for FR1 TDD Conducted are the same as the tests described in clause 3.2.3.6. - -### 3.2.5.7 UC-Plane O-RU Scenario Class LTE (LTE) - -The LTE tests for FR1 TDD Conducted are the same as the tests described in clause 3.2.3.7, except that the TDD waveforms are to be used as shown in Figure 3.2.5.2-56 Combined DL and UL TDD 20 MHz 100 RB. The tests for uplink and downlink may be executed independently as described in the corresponding FDD test case for Delay Management or the tester may choose to combine the uplink and downlink tests into a single test. - -### 3.2.5.8 UC-Plane O-RU Scenario Class Section Type 3 (ST3) - -The Section Type 3 tests for FR1 TDD Conducted are the same as the tests described in clause 3.2.3.8. - -## 3.2.6 FR1 and FR2 TDD Non-conducted OTA Signal Tests - -### 3.2.6.1 UC-Plane O-RU Scenario Class NR testing Generic (NRG) - -All TDD tests described in this clause will be combined UL and DL tests (i.e. a single test frame describing both uplink and downlink). The default test frame used in this clause is described in clause 3.2.1.1.3 of this document for FR1 radios and clause 3.2.1.1.4 for FR2 radios. - -There are several variations on this test signal depending on the capabilities of the radio. If the radio does not support the numerology used in the example tests as reported in the M-plane it will be up to the test developer to modify their tests to adapt to the radio. This can usually be accomplished by using stock test patterns described above. The test is expected to follow the same spirit as the tests in this document but things like symbol numbers, number of PRBs, etc. may have to be changed. - -#### 3.2.6.1.1 UC-Plane O-RU Scenario Class Base 3GPP DL/UL - -##### A. Test Description and Applicability - -This test is MANDATORY. - -The purpose of this test is to ensure the radio can meet the most basic uplink and downlink requirements for O-RAN fronthaul using a TDD signal. Subsequent tests will build on this to exercise additional capabilities of the Fronthaul. - -Using the standard TDD test frame described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2, the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the default signal. - -The purpose of this test is to ensure the radio can transmit and receive a basic 3GPP, TDD test frame using the default parameters in clause 3.2.1.1.5 of this document (or a similar 3GPP waveform) except only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All downlink user data in this test will be an all zeros sequence and all uplink user data will also be an all zeros sequence. - -##### B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described by TM-FR1-TM1.1 for FR1 and 120 kHz subcarrier spacing and 100 MHz bandwidth as described by TM FR2-TM1.1 for FR2. It will be for 5G New Radio only. - -##### C. Test Methodology - -###### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser and signal source to the O-RU antenna ports and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. - -###### b. Procedure - -Build an appropriate IQ signal describing the signal described above in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 in the CUSM emulator. Built the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal. - -Every symbol used in the test should be described by a single section (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser in the downlink direction should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser in the downlink direction shall be the same as the signal described above. If it contains all the same PRB assignments and the all zeros sequence, the test passes. -3. The test frame received in uplink direction by the TER should be the same as the signal described above. If it contains all the same PRB assignments and the all zeros sequence data, the test passes. - -### 3.2.6.1.2 UC-Plane O-RU Scenario Class Extended 3GPP DL/UL – Resource Allocation - -#### A. Test Description and Applicability - -This test is MANDATORY. - -The purpose of this test is to ensure the radio can meet the extended uplink and downlink requirements for O-RAN fronthaul using a TDD signal. This test modifies the previous test by using a PN23 sequence in all test PDSCH sections. - -Using the standard TDD test frame described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the default signal. - -The purpose of this test is to ensure the radio can transmit and receive an extended 3GPP TDD test frame using the default parameters in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 of this document (or a similar 3GPP waveform) except only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All downlink user data in this test will be a PN23 sequence and all uplink user data will also be a PN23 sequence. - -#### B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described by TM-FR1-TM1.1 for FR1 and 120 kHz subcarrier spacing and 100 MHz bandwidth as described by TM FR2-TM1.1 for FR2. It will be for 5G New Radio only. - -#### C. Test Methodology - -##### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. - -**b. Procedure** - -Build an appropriate IQ signal describing the signal described above in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 in the CUSM emulator. In this case use a PN23 sequence for the downlink shared channel. Build the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the uplink and downlink signals. Every symbol used in the test should be described by a single section (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser in the downlink direction should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser in the downlink direction shall be the same as the signal described above. If it contains all the same PRB assignments and the PN23 sequence, the test passes. -3. The test frame received in uplink direction by the TER should be the same as the signal described above. If it contains all the same PRB assignments and PN23 sequence data, the test passes. - -### 3.2.6.1.3 UC-Plane O-RU Scenario Class Extended using SymInc parameter 3GPP DL/UL – Resource Allocation - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages with the SymInc parameter set, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink and interpret and capture the correct resource blocks in the uplink with the SymInc parameter set. This test uses a PN23 sequence in all test PDSCH sections. - -Using the standard TDD test frame described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the specified signal using the SymInc bit in both uplink and downlink. - -Only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All downlink user data in this test will be a PN23 sequence and all uplink user data will also be a PN23 sequence. - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described by TM-FR1-TM1.1 for FR1 and 120 kHz subcarrier spacing and 100 MHz bandwidth as described by TM FR2-TM1.1 for FR2. It will be for 5G New Radio only. - -The radio must support the SymInc Parameter as notified by the M-Plane. The signal analyser must have the ability to decode the downlink shared channel. - -## C. Test Methodology - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. Connect the signal source to the O-RU antenna port and configure it as described below. - -### b. Procedure - -Build an appropriate IQ signal describing the signal described above in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 in the CUSM emulator. In this case use a PN23 sequence for the downlink shared channel. Build the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the uplink and downlink signals. Every symbol used in the test should be described by a single section (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER’s signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -**For the downlink slots and symbols:** Every symbol should be described by a single type 1 section (DL-SCH and DCI) except symbols #5 and #6 which will be used for the SymInc test. The data in these sections must be a PN23 sequence using an initial seed of all ones. Each symbol should be a new PN23 sequence, that is PRB 0 should contain the data from a new PN23 sequence for each symbol. Symbols number 5 and 6 should be stock data sections type “E” as shown above. This stock data section consists of two adjacent symbols each containing two sections. The corresponding C-Plane message will contain 4 section IDs in a single C-Plane message describing symbols #5 and #6. The startSymbolId in the application header will be symbol #5. The second section ID for symbol #5 will have the SymInc bit set informing the O-RU that the next section will begin describing symbol #6. The corresponding U-Plane messages will be a new PN23 sequence for each symbol (5 and 6). Symbol #6 contains PTRS in TM FR2-TM1.1. The data payload should be mapped around the PTRS. Additional sections should be included to describe the DCI symbols as well as Reference Signals described in 38.141-1. - -**For the uplink sections and symbols:** Load uplink test waveform on the RF signal source. Note this signal has a PN23 sequence as user data. Configure the source to generate a new PN23 sequence in symbols #5 and #6. Configure the signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that all C-Plane messages have been sent. Ensure the O-RU and source are synchronized so downlink slots do not conflict with uplink slots. Load C-Plane message sequence on Test Equipment O-RU (TER) – Only symbols #5 and #6 in each slot will be used in this test. All other symbols will contain either reference signals or data but will not be considered part of the test. These two symbols will be used to determine whether the radio properly increments the current symbol ID when the SymInc bit is set. The C-Plane message for symbol #5 should have the SymInc bit set. This message should have a second section describing symbol #6 (using the SymInc mechanism). All PRBs in each symbol will be requested (In the example waveform 51 PRBs). - -**Steps:** - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and the downlink U-Plane messages and trigger the source to play the RF signal on a frame boundary. -- Play messages to the O-RU respecting the timing windows described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the frame. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information from the captured U-Plane messages -- Extract IQ information from the signal analyser for downlink slots -- Extract Payload for both signals -- Compare payload binary sequences - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser in the downlink direction should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. (VOID) -3. The test frame received by the signal analyser in the downlink direction should be the same as the signal described above. If it contains all the same PRB assignments and the correct PN23 data, the downlink test passes. -4. The test frame extracted from the uplink U-Plane messages should be the same as the uplink signal described above. If it contains all the same PRB assignments and correct PN23 data, the uplink test passes. - -**3.2.6.1.4 UC-Plane O-RU Scenario Class Extended using reMask parameter 3GPP DL/UL – Resource Allocation** - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages with the reMask parameter set, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink and interpret and capture the correct resource blocks in the uplink with the reMask parameter set. This test uses a PN23 sequence in all test PDSCH sections. - -Using the standard TDD test frame described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the specified signal using the rb bit in both uplink and downlink. - -Only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All downlink user data in this test will be a PN23 sequence and all uplink user data will also be a PN23 sequence. - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described by TM-FR1-TM1.1 - -for FR1 and 120 kHz subcarrier spacing and 100 MHz bandwidth as described by TM FR2-TM1.1 for FR2. It will be for 5G New Radio only. - -The radio must support the reMask Parameter as notified by the M-Plane. The signal analyser must have the ability to decode the downlink shared channel. - -## C. Test Methodology - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. Connect the signal source to the O-RU antenna port and configure it as described below. - -### b. Procedure - -Build an appropriate IQ signal describing the signal described above in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 in the CUSM emulator. In this case use a PN23 sequence for the downlink shared channel. Build the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the uplink and downlink signals. Every symbol used in the test should be described by a single section (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -**For the downlink slots and symbols:** Symbol number 2 should be stock data Section Type "D" as shown in Figure 3.2.3.1-8. This test will only be using PRBs 1 through 5. The corresponding C-Plane message will contain a section IDs in a single C-Plane message describing symbol #6. The startSymbolId in the application header will be symbol #6. The C-Plane message will have one section with the reMask set to only the odd number resource elements. The number of PRBs will be 5. The start PRB will be 1. - -The corresponding U-Plane message will be a new PN23 Sequence (initial seed is all ones) in PRBs 1 through 5 of symbol #2. - -**For the uplink sections and symbols:** Load C-Plane message sequence on Test Equipment O-RU (TER) symbol #5 in each slot will be used to determine whether the radio properly transmits only every other resource element when the reMask is set. No other symbols will be used in this test, however other symbols containing reference signals should be used to ensure the O-RU can synchronize with the TER. The TER will not request any other symbols from the O-RU in this test. The C-Plane message for symbol #5 should have the reMask set to tell the radio to send only every odd resource element. Only the PRBs 1 through 5 will be used in this section (matching stock data Section Type "D"). The number of PRBs will be 4 and the start PRB will be 1. - -### Steps: - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and the downlink U-Plane messages and trigger the source to play the RF signal on a frame boundary. - -- Play messages to the O-RU respecting the timing windows described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the frame. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information from the captured U-Plane messages -- Extract IQ information from the signal analyser for downlink slots -- Extract Payload for both signals -- Compare payload binary sequences - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser in the downlink direction should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. (VOID) -3. The test frame received by the signal analyser in the downlink direction should be the same as the signal described above. If it contains all the same PRB assignments and the correct PN23 sequence as data, the downlink test passes. -4. The test frame extracted from the uplink U-Plane messages should be the same as the uplink signal described above. If it contains all the same PRB assignments and the correct PN23 sequence as data, the uplink test passes. - -### 3.2.6.1.5 UC-Plane O-RU Scenario Class Extended using RB parameter 3GPP DL/UL – Resource Allocation - -**A. Test Description and Applicability** - -This test is MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages with the rb parameter set, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink and interpret and capture the correct resource blocks in the uplink with the rb parameter set. This test uses a PN23 sequence in all test PDSCH sections. - -Using the standard TDD test frame described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the specified signal using the rb bit in both uplink and downlink. - -Only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All downlink user data in this test will be a PN23 sequence and all uplink user data will also be a PN23 sequence. - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described by TM-FR1-TM1.1 for FR1 and 120 kHz subcarrier spacing and 100 MHz bandwidth as described by TM FR2-TM1.1 for FR2. It will be for 5G New Radio only. - -**C. Test Methodology** -**a. Initial Conditions** - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. Connect the signal source to the O-RU antenna port and configure it as described below. - -**b. Procedure** - -Build an appropriate IQ signal describing the signal described above in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 in the CUSM emulator. In this case use a PN23 sequence for the downlink shared channel. Build the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the uplink and downlink signals. Every symbol used in the test should be described by a single section (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -**For the downlink slots and symbols:** Every allocated (see below) symbol should be described by a single section (DL-SCH and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Symbol #3 of each downlink slot should be Stock data Section Type "D" as shown in clause 3.2.1.1.5 above. The control plane message for symbol #3 will only include PRBs number 5 through 23. This C-Plane message will have the rb bit set to one for this section. All other DL-SCH symbols will not contain data except required reference signals needed to synchronize the signal analyser. Encapsulate the IQ data in U-Plane messages. U-Plane data in symbol #3 will include a new PN23 sequence starting with an initial seed of all ones starting in PRB number 5. Additional sections should be included to describe the DCI symbols as well as Reference Signals described in TS 138.141-1. - -**For the uplink sections and symbols:** Load uplink test waveform on the RF signal source. Note this signal has a PN23 sequence as user data. Configure the signal source to play the TDD test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that all C-Plane messages have been sent. Ensure the O-RU and source are synchronized so downlink slots do not conflict with uplink slots. Load C-Plane message sequence on Test Equipment O-RU (TER) – This C-Plane sequence should describe a single section per uplink symbol (51 RBs per symbol). The C-Plane message for uplink symbol #6 should have the rb bit set. All other sections should have the rb bit set to zero. - -**Steps:** - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and the downlink U-Plane messages and trigger the source to play the RF signal on a frame boundary. -- Play messages to the O-RU respecting the timing windows described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the frame. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information from the captured U-Plane messages -- Extract IQ information from the signal analyser for downlink slots -- Extract Payload for both signals - -- Compare payload binary sequences - -#### **D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser in the downlink direction should satisfy a basic 3GPP signal performance requirement for this radio category (*i.e.* EVM). -2. (VOID) -3. The test frame received by the signal analyser in the downlink direction should be the same as the signal described above. If it contains all the same PRB assignments and PN23 sequence data, the downlink test passes. -4. The test frame extracted from the uplink U-Plane messages shall be the same as the uplink signal described above. If it contains all the same PRB assignments and PN23 sequence data, the uplink test passes. - -### **3.2.6.1.6 UC-Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 6 3GPP DL/UL – Resource Allocation** - -#### **A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages with section extension 6, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink and interpret and capture the correct resource blocks in the uplink with section extension 6. This test uses a PN23 sequence in all test PDSCH sections. - -Using the standard TDD test frame described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 the O-DU emulator (*i.e.* O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the specified signal using section extension 6 in both uplink and downlink. - -In this test stock data section definition C will be used to exercise the non-contiguous RB allocation, all 273 PRBs (51 in the uplink slots) or the max number of PRBs per symbol for the highest numerology the radio supports will be used in this test. - -Only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All downlink user data in this test will be a PN23 sequence and all uplink user data will also be a PN23 sequence. - -#### **B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described by TM-FR1-TM1.1 for FR1 and 120 kHz subcarrier spacing and 100 MHz bandwidth as described by TM FR2-TM1.1 for FR2. It will be for 5G New Radio only. - -The radio must support section extension 6 as notified by the M-Plane. The signal analyser must have the ability to decode the downlink shared channel. - -#### **C. Test Methodology** - -##### **a. Initial Conditions** - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the - -O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. Connect the signal source to the O-RU antenna port and configure it as described below. - -**b. Procedure** - -Build an appropriate IQ signal describing the signal described above in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 in the CUSM emulator. In this case use a PN23 sequence for the downlink shared channel. Build the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the uplink and downlink signals. Every symbol used in the test should be described by a single section (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -**For the downlink slots and symbols:** Only symbols number 6 and 7 will be used in each slot. Symbol #6 contains PTRS in TM FR2-TM1.1. The data payload should be mapped around the PTRS. Other symbols may contain data including reference signals to ensure test equipment can synchronize with the signal. The starting PRB will be zero and number of PRBs will be chosen from one or more columns in Table 3.2.6-1 below. The resource block group size will be 16 based on ETSI TS 138.214 Table 5.1.2.2.1-1 as shown in Table 3.2.6-1 below using configuration 2. - -**3.2.6-1 RBG Group Size.** - -| Bandwidth Part Size | Configuration 1 | Configuration 2 | -|---------------------|-----------------|-----------------| -| 1 – 36 | 2 | 4 | -| 37 – 72 | 4 | 8 | -| 73 – 144 | 8 | 16 | -| 145 – 275 | 16 | 16 | - -Using the calculations in the O-RAN CUS Specification [2], clause 7.7.6 for the FR1 test waveform described above, the ID of the last RBG will be 17, f(0) will be 16, f(n) will be 16 and f(lastRbgID) will be 1 (17 total RBGs), startPrbc will be zero and numPrbc will be 273. For the FR2 test waveform, the ID of the last RBG will be 8, f(0) will be 8, f(n) will be 8 and f(lastRbgID) will be 2 (8 total RBGs), startPrbc will be zero and numPrbc will be 66. If the radio does not support this numerology the following table will apply. The number of PRBs correspond to Table 3.2.6-2: - -### 3.2.6-2 Stock Data Sections. - -| # PRBs per Symbol (11-79) | | | | | | | | | | | -|---------------------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|---------| -| max PRB/sym | 11 | 24 | 25 | 32 | 50 | 51 | 52 | 65 | 66 | 79 | -| numPRBc | 11 | 24 | 25 | 32 | 50 | 51 | 52 | 65 | 66 | 79 | -| rbgSize | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| lastRbgID | 2 | 5 | 6 | 7 | 6 | 6 | 6 | 8 | 8 | 4 | -| f(0) | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| f(n) | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| f(lastRbgID) | 3 | 4 | 1 | 4 | 2 | 3 | 4 | 1 | 2 | 15 | -| rbgMask (Hex) | 000000
5 | 000003
D | 000007
D | 00000F
D | 000007
D | 000007
D | 000007
D | 00001F
D | 00001F
D | 000001D | - -| # PRBs per Symbol (100-273) | | | | | | | | | | | -|-----------------------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------|-------------| -| max PRB/sym | 100 | 106 | 107 | 132 | 133 | 135 | 162 | 217 | 270 | 273 | -| numPRBc | 100 | 106 | 107 | 132 | 133 | 135 | 162 | 217 | 270 | 273 | -| rbgSize | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| lastRbgID | 6 | 6 | 6 | 8 | 8 | 8 | 10 | 13 | 16 | 17 | -| f(0) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| f(n) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| f(lastRbgID) | 4 | 10 | 11 | 4 | 5 | 7 | 2 | 9 | 14 | 1 | -| rbgMask (Hex) | 000007
D | 000007
D | 000007
D | 00001F
D | 00001F
D | 00001F
D | 00007F
D | 0003FF
D | 001FFF
D | 003FFF
D | - -Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal for FR1 or NR-FR2-TM1.1 for FR2 as described above in the O-DU emulator. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal. Every symbol should be described by a single type 1 section (DL-SCH and DCI) except symbols #6 and #7 which will be used for the section extension 6 test. The data in symbol #6 should be a new PN23 sequence starting in the first PRB and continuing to PRB 273 (RBG number 17) for FR1 and PRB 66 (RBG number 8) for FR2. Symbol #7 should be identical to symbol #6. The rbgMask value should be set to 0x3FFFD for FR1 or 0x1FD for FR2, and the symbolMask value should be set to 00000011000000b. No Section Type zero messages will be used for this test. - -The O-DU emulator will build a U-Plane message containing the PN23 IQ data for the first 16 PRBs (RBG 0), this message will have the section ID used in the C-Plane message described above. Another U-Plane message will be created using the same section ID but with the PN23 data for the rest of the RBGs except for RBG 1 in it. The same U-Plane messages will be used for symbol #7. - -**For the uplink sections and symbols:** For this test symbols number 6 and 7 will be used in each slot. For the FR1 waveform, the starting PRB will be zero and number of PRBs will be 51. The resource block group size will be 8. Using the calculations in the O-RAN CUS Specification [2], clause 7.7.6, the ID of the last RBG will be 6, f(0) will be 8, f(n) will be 8 and f(lastRbgID) will be 3. For the FR2 waveform the parameters are similar to the downlink indicated above. - -Every symbol should be described by a single type 1 section (DL-SCH and DCI) except symbols #6 and #7 which will be used for the section extension 6 test. The data in symbol #6 is expected to be a new PN23 - -sequence starting in the first PRB and continuing to PRB 51 (RBG number 6) for FR1 or PRB 66 (RBG number 8 for FR2). Symbol #7 should be identical to symbol #6. The rbgMask value should be set to 0x7D for FR1 and 0x1FD for FR2, and the symbolMask value should be set to 00000011000000b. No Section Type zero messages will be used for this test. If the radio only supports another numerology see the tables above in the downlink sections and symbols for appropriate modifications. - -**Steps:** - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and the downlink U-Plane messages and trigger the source to play the RF signal on a frame boundary. -- Play messages to the O-RU respecting the timing windows described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the frame. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information from the captured U-Plane messages -- Extract IQ information from the signal analyser for downlink slots -- Extract Payload for both signals -- Compare payload binary sequences - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser in the downlink direction should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. (VOID) -3. The test frame received by the signal analyser in the downlink direction should be the same as the signal described above. If it contains all the same PRB assignments and the correct PN23 sequence as data, the downlink test passes. -4. The test frame extracted from the uplink U-Plane messages should be the same as the uplink signal described above. If it contains all the same PRB assignments and the correct PN23 sequence as data, the uplink test passes. - -**3.2.6.1.7 UC- Plane O-RU Scenario Class Extended 3GPP DL/UL – Resource Allocation – Coupling C and U plane via time and frequency** - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can meet the extended uplink and downlink requirements for O-RAN fronthaul using a TDD signal. This test uses time and frequency to couple C-Plane and U-Plane messages. - -Using the standard TDD test frame described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the default signal. - -The purpose of this test is to ensure the radio can transmit and receive an extended 3GPP TDD test frame using the default parameters in clause 3.2.1.1.3 of this document (or a similar 3GPP waveform) except only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is - -required). All downlink user data in this test will be a PN23 sequence and all uplink user data will also be a PN23 sequence. The radio must report over the M-Plane that it supports C and U plane coupling via time and frequency. - -## B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described by TM-FR1-TM1.1 and 120 kHz subcarrier spacing and 100 MHz bandwidth as described by TM FR2-TM1.1 for FR2. It will be for 5G New Radio only. The radio must report over the M-Plane that it supports C and U plane coupling via time and frequency. - -The O-RU must have a conducted antenna port (or TAB connector) to be connected to a signal analyser and signal source. It must also support the default parameters defined in clause 3.2.1.1.1 above. - -## C. Test Methodology - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. - -### b. Procedure - -Build an appropriate IQ signal describing the signal described above in clause 3.2.1.1.3 in the CUSM emulator. In this case use a PN23 sequence for the downlink shared channel. Build the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the uplink and downlink signals. Every symbol used in the test should be described by a single section (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. All section IDs in C-Plane messages and downlink U-Plane messages must be 4095. - -C-Plane and Downlink U-Plane messages sent by the TER will have valid values in the following fields: - -- EAxC ID -- Datadirection bit -- Frame ID, subframeID, slotID, startsymbolID, and NumSymbol -- SectionID must have a value 4095 -- SymInc, rb reMask and section extension #6 are *not* used in this test - -It is the responsibility of the TER to properly arrange uplink U-Plane messages using only time and frequency resources. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. All received U-Plane messages must have section ID equal to 4095 -3. The test frame received by the signal analyser should be the same as the signal described above. If it contains all the same PRB assignments and all zero data, the test passes. - -**3.2.6.1.8 UC- Plane O-RU Scenario Class Extended 3GPP DL/UL – Coupling C and U plane via Time and Frequency and Section Description Priorities****A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to test whether the radio can implement coupling U and C plane via time and frequency and section description priorities requirements for O-RAN fronthaul using a TDD signal. This test combines the FDD, uplink and downlink tests for these same features. Note, there are two versions of this feature: coupling C and U plane messages via frequency and time and Section Description Priorities and coupling C and U plane messages via frequency and time and Section Description Priorities (optimized). This test requires both tests to be performed if the radio supports both methods otherwise only one test is to be performed in the radio only supports one of these methods. These methods are listed under test methodology below. - -Starting with the standard TDD test frame described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the signals described below. - -Only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All downlink user data in this test will be a PN23 sequence and all uplink user data will also be a PN23 sequence. - -**B. Test Entrance Criteria** - -The O-RU must support the default parameters in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 of this document and those specified below. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described by TM-FR1-TM1.1 for FR1 and 120 kHz subcarrier spacing and 100 MHz bandwidth as described by TM FR2-TM1.1 for FR2. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. It will be a TDD signal. - -The O-RU must have a conducted antenna port (or TAB connector) to be connected to a signal analyser and signal source. It must also support the default parameters defined in clause 3.2.1.1.1 above. - -**C. Test Methodology****a. Initial Conditions** - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. - -**b. Procedure for Coupling C and U plane messages via frequency and time with section priorities** - -Build an appropriate C and U plane signals for the signals described below in the CUSM emulator. Every slot used in the test should be described by a single C-Plane message with multiple sections (DL-SCH that are used for the test, DMRS and DCI) using a Section Type 1 message. No Section Type zero messages - -will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -- Downlink procedure: - -**3.2.6-3 Time and Frequency Coupling with Priority TDD DL.** - -| # | Section ext 6 | priority | symbolMask | startPrbc | numPrbc | reMask | rbgMask | beamId | numSymbol | Note | -|---|---------------|----------|--------------------------------------------------------------------------------------------------------|-----------|---------|------------------|-----------|--------|-----------|-------------------------| -| 1 | yes | +1 | 00000000000100 | 0 | 273 | 10101010101
0 | 0xFFFC00 | 1 | 1 | Reference signal (DMRS) | -| 2 | yes | +1 | 00100000000000 | 0 | 273 | 10101010101
0 | 0xFFFC00 | 2 | 1 | Reference signal (DMRS) | -| 3 | no | 0 | 11111000000000

Not used in this section without section extension 6. Just shown for information | 0 | 273 | 11111111111
1 | N/A | 100 | 6 | UE1 | -| 4 | yes | 0 | 00000100000100 | 15 | 32 | 01010101010
1 | 0x6000000 | 200 | 2? | UE2 | -| 5 | no | 0 | 00000011111000

Not used in this section without section extension 6. Just shown for information | 31 | 48 | 11111111111
1 | N/A | 300 | 8 | UE3 | -| 6 | no | 0 | 00000000000001

Not used in this section without section extension 6. Just shown for information | 10 | 2 | 11111111111
1 | N/A | 3 | 1 | Special channel | - -In this test the section configuration will be as shown in Table 3.2.6-3 above. The 6 sections will comprise one slot and this slot will be repeated continuously in the downlink slots in the TDD frame to synchronize the TER signal analyser. The six sections will be sent on one C-Plane message using C and U plane coupling via time and frequency. The configuration above follows the example given in the CUSM specification. - -The section numbers in the above table do not represent SectionID numbers but individual sections. Sections #1 and #2 describe hypothetical DMRS signals sent in symbols #2 and #11 in each slot. These signals have every other subcarrier masked by reMask. This is the same as shown above in the standard NR-FR1-TM1.1 test signal shown above for FR1 or 3.2.1.1.4 for FR2. The DMRS signals in symbol #2 have beam ID 1 and - -symbol #11 have beam ID 2. These sections use section extension 6 and contain a higher priority than all other sections. - -Section #3 describes PN23 data sent to hypothetical UE #1 it overlaps REs in sections #1 and #2 but has a lower priority so sections #1 and #2 are valid. Since section #3 has contiguous symbols section extension 6 is not needed. - -Section #4 is for hypothetical UE #2. It occupies the same symbols as the DMRS signals but uses a different reMask. Since the symbols are not contiguous it uses sections extension 6 but the priority is set to the default 0. - -Section #5 is for hypothetical UE #3 and uses a contiguous set of symbols so section extension 6 is not needed. It does not overlap any other signals. This section is optional because it does not test Section Description Priority. - -Section #6 is a hypothetical special channel using only one symbol and does not require section extension 6. This section is also optional. - -U-Plane messages will contain: - -- DMRS signals for every odd resource element as described by section #1 for symbol #11 -- DMRS signals for every odd resource element as described by section #2 for symbol #2 -- A new PN23 sequence in each of the first 5 symbols as described in section #3. Note that for symbol #2 the PN sequence will be pierced by the DMRS signals. -- A new PN23 sequence for symbol #6 as described by section #4 as well as a new PN sequence for symbol #11. These sequences are only 32 PRBs long and start in PRB 15. The sequence in symbol #11 will be pierced by DMRS signals. -- The user data for sections number #5 and #6 are standard PN23 sequences only for these symbols and PRBs described in the table above. Symbol #6 contains PTRS in TM FR2-TM1.1. The data payload should be mapped around the PTRS. -- Uplink Procedure: -Build the following Uplink C-Plane message. -Start with a standard as G-FR1-A1-5 for FR1 or G-FR2-A3-1 for FR2 waveform. Define the sections shown in Table 3.2.6-4. These sections are described below. - -**3.2.6-4 Time and Frequency Coupling with Priority TDD UL.** - -| # | Section ext 6 | priority | symbolMask | startPrbc | numPrbc | reMask | rbgMask | beamId | numSymbol | Note | -|---|---------------|----------|---------------------------------------------------------------------------------------------|-----------|---------|------------------|------------|--------|-----------|-------------------------| -| 1 | yes | +1 | 000000000000100 | 0 | 273 | 10101010101
0 | 0xFFFFFC00 | 1 | 1 | Reference signal (DMRS) | -| 2 | yes | +1 | 001000000000000 | 0 | 273 | 10101010101
0 | 0xFFFFFC00 | 2 | 1 | Reference signal (DMRS) | -| 3 | no | 0 | 111110000000000

Not used in this section without section extension 6. Just shown for | 64 | 273 | 11111111111
1 | N/A | 100 | 6 | UE1 | - -| | | | | | | | | | | | -|---|-----|---|--------------------------------------------------------------------------------------------------------|----|-----|-------------------|-----------|-----|----|-----------------| -| | | | information | | | | | | | | -| 4 | yes | 0 | 00000100000100 | 64 | 273 | 010101010101
1 | 0x0FFFC00 | 200 | 2? | UE2 | -| 5 | no | 0 | 00000011111000

Not used in this section without section extension 6. Just shown for information | 31 | 48 | 111111111111
1 | N/A | 300 | 8 | UE3 | -| 6 | no | 0 | 00000000000001

Not used in this section without section extension 6. Just shown for information | 10 | 2 | 111111111111
1 | N/A | 3 | 1 | Special channel | - -In this test the section configuration will be as shown in Table 3.2.6-4 above. The 6 sections will comprise one slot and this slot will be repeated to fill the entire frame (i.e. 20 times). The six sections will be sent on one C-Plane message using C and U plane coupling via time and frequency. The configuration above follows the example given in the CUSM specification. - -- The section numbers in the above table do not represent SectionID numbers but individual sections. Sections #1 and #2 describe hypothetical DMRS signals sent in symbols #2 and #11 in each slot. These signals have every other subcarrier masked by reMask. This is the same as shown above in the standard G-FR1-A1-5 test signal shown above with the exception that the DMRS signals continue for all 273 RBs. The DMRS signals in symbol #2 have beam ID 1 and symbol #11 have beam ID 2. These sections use section extension 6 and contain a higher priority than all other sections. -- Section #3 describes PN23 data sent to hypothetical UE #1 it overlaps REs in sections #1 and #2 but has a lower priority so sections #1 and #2 are valid. Since section #3 has contiguous symbols section extension 6 is not needed. Note it starts in PRM 64 (RBG 4) and continues for the remainder of the 273 RBs. -- Section #4 is for hypothetical UE #2. It occupies the same symbols as the DMRS signals but uses a different reMask. Since the symbols are not contiguous it uses sections extension 6 but the priority is set to the default 0. It also starts in RBG 4 (RB 64) and continues to the rest of the 273 RBs. -- Section #5 is for hypothetical UE #3 and uses a contiguous set of symbols so section extension 6 is not needed. It does not overlap any other signals. This section is optional because it does not test Section Description Priority. -- Section #6 is a hypothetical special channel using only one symbol and does not require section extension 6. This section is also optional. -- Load the following waveform into the signal source: - - DMRS signals for every odd resource element as described by section #1 for symbol #11 - - DMRS signals for every odd resource element as described by section #2 for symbol #2 - - A new PN23 sequence in each of the first 5 symbols as described in section #3. Note that for symbol #2 the PN sequence will be pierced by the DMRS signals. - - A new PN23 sequence for symbol #6 as described by section #4 as well as a new PN sequence for symbol #11. These sequences start in PRB 64 and continue to PRB 273. The sequence in symbol #11 will be pierced by DMRS signals. - -- The user data for sections number #5 and #6 are standard PN23 sequences only for these symbols and PRBs described in the table above. -- Configure signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that C-Plane messages have been sent. -- Load C-Plane message described above on Test Equipment O-RU (TER). The C-Plane message will contain valid values in the following fields: - - EAxC ID - - Datadirection bit (Uplink) - - Frame ID, subframeID, slotID, startsymbolID, and NumSymbol - - SectionID must have a value 4095 -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the RF uplink frame after the C-Plane messages have been sent honouring timing windows -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- TER will arrange U-Plane messages according to time and frequency -- Extract IQ information -- Extract Payload -- Compare payload binary sequences - -**c. Procedure for Coupling C and U plane messages via frequency and time with section priorities (optimized)** - -This test will be identical to the above test with the following exceptions: - -- There will be two C-Plane messages describing the uplink and downlink signals to be sent. -- The first two sections listed in the table above (those with higher priorities) will be repeated in both C-Plane messages and will have a section ID equal to a value between 0 and “max-highest-priority-sections-per-slot” as sent on the M-Plane. -- The other sections will be divided between the two C-Plane messages and not repeated. -- The repeated C-plane message will have the “repetition” bit set to one. - -**D. Test Requirement (expected result)** - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser must be the same as the signal described above. It must contain all the same PRB assignments and PN23 sequences. -3. The data received from the O-RU on the uplink U-Plane must match the uplink signal sent to the DUT including all the same PRB assignments and PN23 sequences. -4. The beamweights or magnitude and phase relation at the antenna ports (or TAB connectors) of the test signal that achieves the highest performance (i.e. best EVM, power, SNR, etc.) should match with the manufacturer’s declaration of the beam under test. The procedures for test case 3.2.3.2.4 (UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Predefined-beam Beamforming) and test case 3.2.3.2.3 (UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Predefined-beam Beamforming) should be used. -5. These expected results are applicable for either or both forms of this test. -6. If all of the above results are observed the test passes. - -### 3.2.6.1.9 UC-Plane O-RU Scenario Class Extended using Non-contiguous PRB Allocation Section Extension 12 3GPP DL/UL – Resource Allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can accurately interpret C-Plane resource allocation messages with section extension 12, transfer U-Plane data into the correct resource blocks and transmit this data accurately in the downlink and interpret and capture the correct resource blocks in the uplink with section extension 12. This test uses a PN23 sequence in all test PDSCH sections. - -Using the standard TDD test frame described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the specified signal using section extension 12 in both uplink and downlink. - -In this test stock data section definition C will be used to exercise the non-contiguous RB allocation, all 273 PRBs (48 of the 51 in the uplink slots) or the max number of PRBs per symbol for the highest numerology the radio supports will be used in this test. - -Only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All downlink user data in this test will be a PN23 sequence and all uplink user data will also be a PN23 sequence. - -#### B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 of this document. - -The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described by TM-FR1-TM1.1 for FR1 and 120 kHz subcarrier spacing and 100 MHz bandwidth as described by TM-FR2-TM1.1 for FR2. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. - -The radio must support section extension 12 as notified by the M-Plane. The signal analyser must have the ability to decode the downlink shared channel. - -#### C. Test Methodology - -##### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. Connect the signal source to the O-RU antenna port and configure it as described below. - -##### b. Procedure - -Build an appropriate IQ signal describing the signal described above in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 in the CUSM emulator. In this case use a PN23 sequence for the downlink shared channel. Build the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the uplink and downlink signals. Every symbol used in the test should be described by a single section (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the - -TER’s signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -**For the downlink slots and symbols:** Only symbols number 6 and 7 will be used in each slot. Other symbols may contain data including reference signals to ensure test equipment can synchronize with the signal. The starting PRB will be zero and number of PRBs will be chosen from one or more columns in Table 3.2.6-5 below. The resource block group size will be 16 based on ETSI TS 138.214 Table 5.1.2.2.1-1 as shown in Table 3.2.6-5 below using configuration 2. - -**3.2.6-5 Resource Block Group Size.** - -| Bandwidth Part Size | Configuration 1 | Configuration 2 | -|---------------------|-----------------|-----------------| -| 1 – 36 | 2 | 4 | -| 37 – 72 | 4 | 8 | -| 73 – 144 | 8 | 16 | -| 145 – 275 | 16 | 16 | - -Using the calculations in the O-RAN CUS Specification [2], clause 7.7.6, for the FR1 test waveform described above, the ID of the last RBG will be 17, $f(0)$ will be 16, $f(n)$ will be 16 and $f(lastRbgID)$ will be 1 (17 total RBGs). StartPrbc will be zero and numPrbc will be 273. For the FR2 test waveform, the ID of the last RBG will be 8, $f(0)$ will be 8, $f(n)$ will be 8 and $f(lastRbgID)$ will be 2 (8 total RBGs), startPrbc will be zero and numPrbc will be 66. If the radio does not support this numerology the following table will apply. The number of PRBs correspond to Table 3.2.6-6: - -**3.2.6-6 Stock Data Sections** - -| # PRBs per Symbol (11-79) | | | | | | | | | | | -|---------------------------|----|----|----|----|----|----|----|----|----|----| -| max PRB/sym | 11 | 24 | 25 | 32 | 50 | 51 | 52 | 65 | 66 | 79 | -| numPRBc | 11 | 24 | 25 | 32 | 50 | 51 | 52 | 65 | 66 | 79 | -| rbgSize | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| lastRbgID | 2 | 5 | 6 | 7 | 6 | 6 | 6 | 8 | 8 | 4 | -| f(0) | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| f(n) | 4 | 4 | 4 | 4 | 8 | 8 | 8 | 8 | 8 | 16 | -| f(lastRbgID) | 3 | 4 | 1 | 4 | 2 | 3 | 4 | 1 | 2 | 15 | - -| # PRBs per Symbol (100-273) | | | | | | | | | | | -|-----------------------------|-----|-----|-----|-----|-----|-----|-----|-----|-----|-----| -| max PRB/sym | 100 | 106 | 107 | 132 | 133 | 135 | 162 | 217 | 270 | 273 | -| numPRBc | 100 | 106 | 107 | 132 | 133 | 135 | 162 | 217 | 270 | 273 | -| rbgSize | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| lastRbgID | 6 | 6 | 6 | 8 | 8 | 8 | 10 | 13 | 16 | 17 | -| f(0) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| f(n) | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | 16 | -| f(lastRbgID) | 4 | 10 | 11 | 4 | 5 | 7 | 2 | 9 | 14 | 1 | - -Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal for FR1 or NR-FR2-TM1.1 for FR2 as described above in the O-DU emulator. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal. Every symbol should be described by a single type 1 section (DL-SCH) - -and DCI) except symbols #6 and #7 which will be used for the section extension 12 test. The data in symbol #6 should be a new PN23 sequence starting in the first PRB and continuing to PRB 273 (RBG number 17). Symbol #6 contains PTRS in TM FR2-TM1.1. The data payload should be mapped around the PTRS. Symbol #7 should be identical to symbol #6. The symMask value should be set to 00000011000000b. No Section Type zero messages will be used for this test. The relevant parameters for the downlink C-Plane message are shown in the diagram below: - -![](7fe15d7c926841a22a218599eab4d5b2_img.jpg) - -**Section Extension 12 (273 PRBs)** - -**Section Header** -startSymbolId = 0 - -**SectionId** -startPrbc = 0 -numPrbc = 16 - -**Section Extension 6** -offStartPrb(1) = 16 -numPrb(1) = 241 - -Grey cells are user data, White cells are unallocated PRBs - -| | | | | | | | | | | | | | | | -|-------------------|---------------------------------------------------------------------------|----------|----------|----------|----------|----------|-----------|-----------|----------|----------|-----------|-----------|-----------|-----------| -| | Symbol 0 | Symbol 1 | Symbol 2 | Symbol 3 | Symbol 4 | Symbol 5 | Symbol 6 | Symbol 7 | Symbol 8 | Symbol 9 | Symbol 10 | Symbol 11 | Symbol 12 | Symbol 13 | -| | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | -| 241 PRBs – 16 RBG | Blank | Blank | Blank | Blank | Blank | Blank | User Data | User Data | Blank | Blank | Blank | Blank | Blank | Blank | -| 16 PRB – 1 RBG | | | | | | | Blank | Blank | | | | | | | -| 16 PRB – 1 RBG | | | | | | | User Data | User Data | | | | | | | -| |
symMask | | | | | | | | | | | | | | - -Figure 3.2.5.1-60 Downlink C-Plane Parameters - -The O-DU emulator will build a U-Plane message containing the PN23 IQ data for the first 16 PRBs (RBG 0), this message will have the section ID used in the C-Plane message described above. Another U-Plane message will be created using the same section ID but with the PN23 data for RBGs 2-17 in it. The same U-Plane messages will be used for symbol #7. - -**For the uplink sections and symbols:** For this test symbols number 6 and 7 will be used in each slot. The starting PRB will be zero and number of PRBs will be 48. The resource block group size will be 16. Using the calculations in the O-RAN CUS Specification [2], clause 7.7.6, the ID of the last RBG will be 17, f(0) will be 16, f(n) will be 16 and f(lastRbgID) will be 1. - -Every symbol should be described by a single type 1 section (DL-SCH and DCI) except symbols #6 and #7 which will be used for the section extension 6 test. The data in symbol #6 is expected to be a new PN23 sequence starting in the first PRB and continuing to PRB 48 (RBG number 2). Symbol #7 should be identical to symbol #6. The symMask value should be set to 00000011000000b. No Section Type zero messages will be used for this test. If the radio only supports another numerology see the tables above in the downlink sections and symbols for appropriate modifications. The relevant parameters for the uplink C-Plane message are shown in the diagram below: - -![](560290b4b60884ac78117eb47a302b90_img.jpg) - -### Section Extension 12 (48 PRBs) - -**Section Header** -startSymbolId = 0 - -**SectionId** -startPrbc = 0 -numPrbc = 16 - -**Section Extension 6** -offStartPrb(1) = 16 -numPrb(1) = 16 - -Grey cells are user data, White cells are unallocated PRBs - -| | | | | | | | | | | | | | | | -|-----------------|-------|-------|-------|-------|-------|-------|-----------|-----------|-------|-------|-------|-------|-------|-------| -| | | | | | | | Blank | Blank | | | | | | | -| | Blank | Blank | Blank | Blank | Blank | Blank | | | Blank | Blank | Blank | Blank | Blank | Blank | -| 16 PRBs – 1 RGB | | | | | | | User Data | User Data | | | | | | | -| 16 PRB – 1 RGB | | | | | | | Blank | Blank | | | | | | | -| 16 PRB – 1 RGB | | | | | | | User Data | User Data | | | | | | | -| Symbol | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | -| symMask | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | - -symMask - -Figure 3.2.5.1-61 Uplink C-Plane Parameters - -**Steps:** - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and the downlink U-Plane messages and trigger the source to play the RF signal on a frame boundary. -- Play messages to the O-RU respecting the timing windows described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the frame. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information from the captured U-Plane messages -- Extract IQ information from the signal analyser for downlink slots -- Extract Payload for both signals -- Compare payload binary sequences - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser in the downlink direction should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. (VOID) -3. The test frame received by the signal analyser in the downlink direction should be the same as the signal described above. If it contains all the same PRB assignments and the correct PN23 sequence as data, the downlink test passes. -4. The test frame extracted from the uplink U-Plane messages should be the same as the uplink signal described above. If it contains all the same PRB assignments and the correct PN23 sequence as data, the uplink test passes. - -### 3.2.6.1.10 UC-Plane O-RU Scenario Class Static SRS Allocation UL – Resource Allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the O-RU can support static SRS configuration through the M-Plane. This is an uplink only test so there is no corresponding downlink test for TDD. The O-RU must report through the M-Plane that it supports static configuration of SRS. - -This test will use the standard TDD test frame described in clause 3.2.1.1 for FR1 or 3.2.1.1.4 for FR2. The test will have the CUSM emulator configure the O-RU, through the M-Plane, with a section of time/frequency resources reserved for static uplink SRS, these will be limited to the uplink slots of the TDD frame. The signal source will be programmed to send simulated SRS signals in a subset of those resources. The O-RU should receive this SRS signals and pass them through to the CUSM emulator using U-Plane messages. Note, there will be no C-Plane messages sent from the CUSM emulator and the O-RU. The signal generator will signal power levels at least 30 dB above Reference Sensitivity power Level described in TS 138.141-1 Table 7.2.5-1. This is to improve the likelihood that all data will be received by the radio correctly since we are not interested in testing receiver sensitivity but only the O-RAN protocol compliance. The placement of the time frequency resources is not specified in this test so it may be placed in any uplink slots of the TDD frame. - -The TER (Test Equipment, O-RU) generates an uplink SRS signal on the antenna connector or TAB connector. The TER will capture the U-Plane messages generated by the DUT and validate whether the payload matches the uplink signal as well as beam characteristics. The metric used to validate that the signal received by the CUSM emulator matches the signal sent by the signal generator will be EVM as described in Annex H.7 of ETSI TS 138.141. While some 3GPP test documents (e.g. ETSI TS 138.521 clause 6.4.2.1.3) suggest treating the EVM requirements for physical Zadoff-Chu sequences such as PRACH the same as QPSK for EVM requirements, this document will decrease the required EVM to the level specified for 64 QAM. The purpose of this is to ensure that there is no chance of false positives where a random, mistaken signal sent by the O-RU closely mimics the test signal used by the TER. Since there are no impairments made to the uplink SRS signal this should be well within the capabilities of the O-RU. - -#### B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 of this document. The O-RU must indicate it supports static SRS allocation. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth for FR1 and 120 kHz subcarrier spacing and 100 MHz Bandwidth for FR2. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. Note this signal may be changed to any of the 3GPP sensitivity test signals in ETSI TS 138.141-1 if the radio does not support the - -numerology and bandwidth used in this test. The test signal described in this section will be used if the radio supports that numerology and bandwidth. - -## C. Test Methodology - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal source to the O-RU antenna port and configure the source to transmit the required SRS test signal upon receiving a trigger signal from the CUSM-E. The signal source power level should be adjusted to at least 30 dB above the setting used in the 3GPP receiver sensitivity test. - -Implicit in this Initial set up is statically configuring O-RU with a section of time/frequency resources for statis SRS signals. - -### b. Procedure - -- Build an SRS signal in the signal generator that fits in the preconfigured time frequency resources set in the initial configuration. -- Load the waveform into the signal source: -- Configure signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that signals the start of a frame boundary. -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port connected -- TER will arrange U-Plane messages according to time and frequency -- Start SRS waveform generation on the signal generator. Ensure the test frame is repeated enough times to generate a statistically significant number of SRS occasions. That is at least 10 occasions. -- Extract IQ information -- Calculate EVM of the SRS signal received by the CUSM emulator to the ideal signal generated by the signal source. Use the method described in ETSI TS 138.141 Annex H.7 to perform the calculation. - -## D. Test Requirement (expected result) - -1. The verdict is “Test pass” if the calculated EVM is less than 8% as median EVM measured over the minimum number of SRS occasions of at least 10 occasions. -2. If any of the test conditions are not true, the verdict for the whole test is "Fail" - -### 3.2.6.1.11 UC Plane O-RU Base Class TDD Test UL – Static PRACH allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the O-RU can support static PRACH configuration through the M-Plane. This is an uplink only test so there is no corresponding downlink test for downlink slots. The O-RU must report through the M-Plane that it supports static configuration of PRACH. The concept is to repeat the spirit of test 3.2.3.8.1 (5G NR PRACH test) without sending any C-Plane type 3 messages and configuring the O-RU using only the M-Plane. - -TER will setup the signal generator with a PRACH test waveform according to ETSI TS 138.141-1 clause 8.4.1 and A.6. The test waveform will contain the same preamble ID repeated by following the timing offset scheme specified in the figures 8.4.1.4.2-2 or 8.4.1.4.2-3 ETSI TS 138.141-1 depending on the selected PRACH format. - -This is an example for FR1 – SCS=30 kHz – BW=100MHz – Format A3 configuration index 132 (From Table 6.3.3.2-3, unpaired spectrum), on each occasion the time offset of the same preamble index (selected according to Table A.6-1 ETSI TS 138.141.1) is incremented by 100nsec starting from 0 up to 800nsec (9 occasions per frame). Each PRACH occasion is at the beginning of the first nine used sub-frames. The scheme is repeated every frame. The test must be conducted using a PRACH format and configuration index the radio has reported it supports - -| # | Enabled | Power Boosting | Timing Offset | PRACH Format | Preamble Index | Logical Root Sequence Index (i) | Sequence Number (u) | Cyclic Shift Index (v) | Cyclic Shift (Cv) | Frame Offset | Subframe Index | n_RA_t | n_RA_slot | n_RA_f | Occasion Index | RA_RNTI | -|---|---------|----------------|---------------|--------------|----------------|---------------------------------|---------------------|------------------------|-------------------|--------------|----------------|--------|-----------|--------|----------------|---------| -| 0 | ✓ | 0.00 dB | 0 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 8 | -| 1 | ✓ | 0.00 dB | 100 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 22 | -| 2 | ✓ | 0.00 dB | 200 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 2 | 0 | 0 | 0 | 2 | 36 | -| 3 | ✓ | 0.00 dB | 300 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 3 | 0 | 0 | 0 | 3 | 50 | -| 4 | ✓ | 0.00 dB | 400 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 4 | 0 | 0 | 0 | 4 | 64 | -| 5 | ✓ | 0.00 dB | 500 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 5 | 0 | 0 | 0 | 5 | 78 | -| 6 | ✓ | 0.00 dB | 600 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 6 | 0 | 0 | 0 | 6 | 92 | -| 7 | ✓ | 0.00 dB | 700 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 7 | 0 | 0 | 0 | 7 | 106 | -| 8 | ✓ | 0.00 dB | 800 ns | FormatA3 | 0 | 10 | 6 | 0 | 0 | 0 | 8 | 0 | 0 | 0 | 8 | 120 | - -![A screenshot of a signal analysis tool showing a frequency vs. time plot. The y-axis represents Frequency in MHz, ranging from -61.44 to 61.44. The x-axis represents Time in ms, ranging from 0 to 10. There are several horizontal red lines representing PRACH signals at different time intervals. A legend in the top right corner indicates 'PRACH' with a red square icon.](994a745041d4af5063159f147e990e78_img.jpg) - -A screenshot of a signal analysis tool showing a frequency vs. time plot. The y-axis represents Frequency in MHz, ranging from -61.44 to 61.44. The x-axis represents Time in ms, ranging from 0 to 10. There are several horizontal red lines representing PRACH signals at different time intervals. A legend in the top right corner indicates 'PRACH' with a red square icon. - -Figure 3.2.5.1-62 FR1 SCS 30Kz 100MHz Format A3, Unpaired Spectrum, configuration index 132 - -According to the PRACH waveform setting, the TER will generate a corresponding sequence of M-Plane messages which include the following parameters (According to the M-Plane specification and the PRACH configuration index supported): - -grouping static-prach-configuration - -- leaf pattern-period - "Period after which static PRACH patterns are repeated. Unit: number of frames." -- leaf guard-tone-low-re - "Number of REs occupied by the low guard tones." -- leaf num-prach-re - "Number of contiguous PRBs per data section description“ -- leaf guard-tone-high-re - "Number of REs occupied by the high guard tones.“ -- leaf sequence-duration - "Duration of single sequence of the PRACH. Sequence may be considered as 'single PRACH symbol'" -- list prach-patterns - key prach-pattern-id - "Provides a PRACH pattern. Each record in the list represents a single PRACH occasion. Number of list entries cannot exceed max-prach-patterns“ - - leaf prach-pattern-id - "Supplementary parameter acting as key for prach-pattern list.“ - - leaf number-of-repetitions - "This parameter defines number of PRACH repetitions in PRACH occasion, to which the section control is applicable - - leaf number-of-occasions - "This parameter informs how many consecutive PRACH occasions is described by the PRACH Pattern” - - leaf re-offset – “Offset between the start of the lowest-frequency RE of the lowest frequency PRB and the start of the lowest frequency RE belonging to the PRACH occasion. The re-offset is configured as number of PRACH REs. - - list occasion-parameters – “list of cp-lengths, gp-lengths and beam-ids applicable per each PRACH occasion in PRACH pattern.” - -NOTE: the number of records in this list MUST be equal to value of parameter number-of-occasions. - -- leaf occasion-id - "Supplementary parameter acting as key in 'occasion-parameters' list" -- leaf cp-length - "Cyclic prefix length. See CUS-Plane specification for detailed description." -- leaf gp-length - "Guard period length." -- leaf beam-id - "This parameter defines the beam pattern to be applied to the U-Plane data. beamId = 0 means no beamforming operation will be performed." -- leaf frame-number - "This parameter is an index inside the pattern-length, such that PRACH occasion is happening for SFN which fulfils following equation: [SFN mod pattern-length = frame-id]" -- leaf sub-frame-id - "Identifier of sub-frame of the PRACH occasion. Value is interpreted in the same way as subframeId field in a section description of a C-Plane message." -- leaf time-offset - "This parameter defines the time-offset from the start of the sub-frame to the start of the first Cyclic Prefix of PRACH pattern" - -By the corresponding U-Plane messages in the uplink direction, the TER will try to detect the presence of the corresponding preamble at the expected timing offset and calculate the probability of detection Pd according to the definition in TS38.141-1 clause 8.4.1.1. - -The signal will be exercised at only one O-RU port without adding any external AWGN power level or multipath fading profile and at a power level avoiding detection errors due to poor SNR (rule described in the sub-section C of this scenario class). - -The test will have the CUSM emulator configure the O-RU, through the M-Plane, with a section of time/frequency resources reserved for static uplink PRACH. The default is the PRACH configuration described in 3GPP above, but the test may be conducted with changes if the radio does not support those exact configurations. The signal source will be programmed to send simulated PRACH signals in those resources. The O-RU should receive this PRACH signal and pass them through to the CUSM emulator using U-Plane messages. Note, there will be no C-Plane messages sent from the CUSM emulator and the O-RU. - -## B. Test Entrance Criteria - -O-RU must have a conducted antenna port (FR1) or TAB connector. - -By the M-plane or by manufacturer declaration, TER will detect all the supported SCSs, FFT sizes and carrier bandwidths by the O-RU. It is assumed that only one combination of the three above parameters supported by the O-RU is enough to validate the test. TER shall generate M-Plane messages according to one of the PRACH formats in Table A.6-1 ETSI TS 138.141. TER will choose the format either according to the manufacturer declaration item D.103 “PRACH format and SCS” in ETSI TS 138.141-1 or according to the format information obtained by the M-plane in case O-RU implements this feature. If more formats are claimed, only one shall be selected to reduce the test time, preference will be given to a format specified in Table A.6.1 ETSI TS 138.141. It is assumed that the O-RU manufacturer will support at least one in that table. For the case of long preambles, it is assumed format 0 is always supported since this is the only one shown in the Table A.6-1 ETSI TS 138.141. - -## C. Test Methodology - -### a: Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal source to the O-RU antenna port and configure the source to transmit the required PRACH test signal upon receiving a trigger signal from the CUSM-E. - -Implicit in this Initial set up is statically configuring O-RU with a section of time/frequency resources for static PRACH signals. - -#### b: Procedure - -- Set signal generator power by the following method: - - a. Select SNR from the scenario with two RX antennas and AWGN propagation condition in Table 8.4.1.5-1, 8.4.1.5-2 or 8.4.1.5-3 ETSI TS 138.141-1 depending on the selected SCS and PRACH format. - - b. Select the AWGN power level according to the configured SCS and channel bandwidth in Table 8.4.1.4.2-1 ETSI TS 138.141-1 and 38.141-1 and multiply by the PRACH signal bandwidth. - - c. The output power will be given by the formula $(\text{SNR} + \text{Noise power} - 3\text{dB})$ rounded to the first decimal digit. Extra 3dB are to compensate that SNR and noise power are selected from the two RX ports test case and this test procedure requires only one O-RU port. - -For example, for the FR1 – SCS=30 kHz – BW=100MHz – Format A3 SNR is -13.5dB and noise level is -70.1dBm/98.28MHz. signal generator power = $-13.5\text{dB} - 70.1\text{dBm}/98.28\text{MHz} * (139 * 30\text{ kHz}) - 3\text{dB} = -19.5\text{dBm}$ . - -- Set signal generator frequency offset to the central carrier frequency. PRACH will be mapped over frequency according to $\text{msg1-FrequencyStart} (n_{\text{RA}}^{\text{start}})$ parameter equal to 0. PRACH format is set according to what TER has selected from the manufacturer declarations. -- Start PRACH waveform generation on the signal generator. Ensure the test frame is repeated enough times to generate a statistically significant number of PRACH occasions. That is at least 10 occasions. -- TER will perform PRACH detection per each PRACH occasion in each frame sent and compare the result with the expected preamble ID and the expected timing offset. Since the external AWGN and fading generator are not present the time error tolerance should be low, TER will use the time error tolerance in Table 8.4.1.1-1 for AWGN case according to the corresponding PRACH format and PRACH SCS. A counter of successful detections is incremented at every matching. The probability of detection is given by the ratio between that counter and the number of the expected received PRACH occasions within the test time. -- Repeat the test procedure by setting $\text{msg1-FrequencyStart} (n_{\text{RA}}^{\text{start}})$ parameter to the right edge of the configured carrier bandwidth in order to exercise a different frequency offset number - -#### D. Test Requirement (expected result) - -- a. Test is pass if the probability of detection is 100% determined across the minimum amount of at least 10 occasions. - -### 3.2.6.1.12 UC Plane O-RU Scenario Class Extended using section extension 13 for frequency hopping UL/DL – Resource Allocation - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to validate the capability of the O-RU to correctly interpret section extension 13, frequency hopping, for the uplink. Note, since frequency hopping is only used in uplink in 5G NR this test will be - -limited to the uplink slots of the basic TDD signal. - -Using the standard TDD test frame described in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate C-Plane and U-Plane messages that require the O-RU to transmit on the downlink and uplink the specified signal using section extension 13 in just the uplink downlink. The downlink portion of the test is not part of this test and may be any signal or no downlink signal at all. - -In this test stock data section definition C will be used to exercise the non-contiguous RB allocation, all 273 PRBs (48 of the 51 in the uplink slots) or the max number of PRBs per symbol for the highest numerology the radio supports will be used in this test. - -Only one spatial stream on one antenna will be used. This test is applicable for Category A and Category B radios (No precoding is required). All uplink user data will be a PN23 sequence. - -## B. Test Entrance Criteria - -The O-RU must support the default parameters in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause 3.2.1.1.3 for FR1 and 120 kHz subcarrier spacing and 100 MHz bandwidth as described in clause 3.2.1.1.4 for FR2. It will be for 5G New Radio only. The radio must have conducted antenna ports (FR1) or TAB connectors. - -The radio must support section extension 13 as notified by the M-Plane. The signal analyser must have the ability to decode the downlink shared channel. - -## C. Test Methodology - -### a. Initial Conditions - -Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Connect the signal analyser to the O-RU antenna port and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. Connect the signal source to the O-RU antenna port and configure it as described below. - -### b. Procedure - -Build an appropriate IQ signal as described above in clause 3.2.1.1.3 for FR1 or 3.2.1.1.4 for FR2 in the CUSM emulator. In this case use a PN23 sequence for the downlink shared channel. Build the appropriate test frame (uplink slots) for the signal source. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the uplink and downlink signals. Every symbol used in the test should be described by a single section (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. It will be the responsibility of the TER's signal analyser and source to coordinate downlink and uplink TDD transmissions. The CUSM Emulator of the TER is responsible for receiving uplink U-Plane messages, extracting IQ and decoding it to bits which can be compared to those sent by the signal source. - -**For the downlink slots and symbols:** Any signal may be used if needed by the TER or no downlink signal may be used. - -**For the uplink sections and symbols:** Load uplink test waveform (G-FR1-A1-5: SCS30k\_51RB for FR1 or G-FR2-A3-1: SCS120k\_66RB for FR2) on the RF signal source. Note this signal should contain a new PN23 sequence as user data in PRBs 0 through 50 for symbol 6 and PRBs 100 through 151 for symbol 7. This will be copied for all uplink slots. The remainder of the test waveform is as described in 3GPP. Configure signal source to play test waveforms on 10ms frame boundaries starting when it receives a trigger signal from the O-DU emulator that C-Plane messages have been sent. Load a C-Plane message on Test Equipment O-RU (TER) – Use the O-DU emulator control interface to build the appropriate C-Plane message that describes this uplink signal. This section should have startSymbolId = 6, numPrbc = 51, and section extension 13 attached. The section extension should have nextSymbolId = 7 and nextStartPrbc = 100. - -**Steps:** - -- Arm Test Equipment O-RU (TER) to capture DUT fronthaul Messages -- Launch test to play the C-Plane messages and the downlink U-Plane messages (if needed) and trigger the source to play the RF signal on a frame boundary. -- Play messages to the O-RU respecting the timing windows described in clause 3.2.1.1.1. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the frame. -- Record U-Plane messages from DUT for a complete frame and the eAxC corresponding to the Antenna port -- Extract IQ information from the captured U-Plane messages -- Extract IQ information from the signal analyser for downlink slots (if needed) -- Extract Payload for both signals -- Compare payload binary sequences - -**D. Test Requirement (expected result)** - -1. (VOID) -2. The verdict is “Test pass” if the test frame extracted in the uplink direction contains two U-Plane messages for this section ID one containing the PN23 sequence for the first 51 PRBs in symbol 6 and PRBs 100 through 151 for symbol #7 containing the PN23 sequence sent by the signal source for those PRBs. - -### 3.2.6.2 UC-Plane O-RU Scenario Class Beamforming (BFM) - -This clause describes the beamforming conformance testing for O-RAN fronthaul interface. The tests do not aim to test the O-RU beamforming performance or capabilities but to test that the O-RU under test focuses the RF energy or sensitivity into a specific direction and with a specific granularity following the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) C-Plane messages. - -Unless stated otherwise in a test case, the following statements apply to all the test cases defined in this clause: - -- It is based on Over-the-Air (OTA) testing with a setup such as described in clause 2.1 and it may be applied to any O-RU DUTs, whether the O-RU DUTs have conducted antenna ports or TAB connectors or not. -- Clause 3.2.1.1.2 for scenario #2 non-conducted OTA FDD FR1 radios contains a description of test setups, as mentioned by ETSI TS 137.843 defines various radiated test systems. If not explicitly mentioned, scenario #4 non-conducted OTA TDD tests for FR1 and FR2 radios will inherit those descriptions. -- Additional statements as per clause 3.2.3.2 of the present specification regarding applicability for O-RU Categories, LTE/5G New Radio, Analog Beamforming, Digital Beamforming, and multiple polarizations. -- For an O-RU DUT that support LTE: - - Downlink tests will use a standard 3GPP E-TM1.1 test frame for TDD, based on uplink/downlink configuration 3 and special subframe configuration 8 (clause 6.1.1.1 ETSI TS 136.141) with 20MHz bandwidth (100 RB) as shown in Figure 3.2.6.2-63. - -![Figure 3.2.6.2-63: E-TM1.1 TDD 20 MHz 100RB. A resource grid plot showing OFDM symbols (0 to 20) on the x-axis and Resource Blocks (0 to 100) on the y-axis. The plot shows a mix of green (downlink) and blue (uplink) blocks. Below the plot is a legend for various signal types: PDCH, PBCH, USER1, USER2, USER3, USER4, EPDCCH1, EPDCCH2, EPDCCH3, EPDCCH4, PBCH, MBSFN, REF-PRS, CSI, ZeroTxPower CSI, P-SYNC, S-SYNC, DTX, Dummy, PDCH-SIB1, GP, and Reserved for UL. Below the legend is a configuration table and a subframe configuration diagram.](87e720ac638df8b655bbb374527f6a6f_img.jpg) - -| | | | | -|-------------------------|---|-----------------------------|---| -| TDD UL/DL Configuration | 3 | TDD Special Subframe Config | 8 | -| Number of UpPTS Symbols | 1 | | | - -Subframe configuration: D U U U D D D D D - -Figure 3.2.6.2-63: E-TM1.1 TDD 20 MHz 100RB. A resource grid plot showing OFDM symbols (0 to 20) on the x-axis and Resource Blocks (0 to 100) on the y-axis. The plot shows a mix of green (downlink) and blue (uplink) blocks. Below the plot is a legend for various signal types: PDCH, PBCH, USER1, USER2, USER3, USER4, EPDCCH1, EPDCCH2, EPDCCH3, EPDCCH4, PBCH, MBSFN, REF-PRS, CSI, ZeroTxPower CSI, P-SYNC, S-SYNC, DTX, Dummy, PDCH-SIB1, GP, and Reserved for UL. Below the legend is a configuration table and a subframe configuration diagram. - -Figure 3.2.6.2-63 E-TM1.1 TDD 20 MHz 100RB - -If 20MHz is not supported by the O-RU DUT, then it will use the highest bandwidth supported by the O-RU DUT. - -- Uplink test will use a standard 3GPP UL RMC Configuration definition for TDD (TS36.521-1 Annex A.2.3) and power levels at least 30dB above Reference Sensitivity power level with 20MHz bandwidth (100 RB) as shown in Figure 3.2.6.2-64. - -![Figure 3.2.6.2-64: UL RMC TDD 20 MHz 100 RB. A resource grid plot showing SC-FDMA symbols (0 to 10) on the x-axis and Resource Blocks (0 to 50) on the y-axis. The plot shows a mix of green (downlink) and blue (uplink) blocks. Below the plot is a configuration table and a subframe configuration diagram.](6470c6dbf291c1e9676f0651ca2b38fa_img.jpg) - -| | | | | -|-------------------------|---|-----------------------------|---| -| TDD UL/DL Configuration | 0 | TDD Special Subframe Config | 0 | -| Number of UpPTS Symbols | 1 | | | - -Subframe configuration: D U U U D U U U - -Figure 3.2.6.2-64: UL RMC TDD 20 MHz 100 RB. A resource grid plot showing SC-FDMA symbols (0 to 10) on the x-axis and Resource Blocks (0 to 50) on the y-axis. The plot shows a mix of green (downlink) and blue (uplink) blocks. Below the plot is a configuration table and a subframe configuration diagram. - -Figure 3.2.6.2-64 UL RMC TDD 20 MHz 100 RB. ETSI TS 36.521-1 A.2.3.1.1 - -If 20MHz is not supported by the O-RU DUT, then it will use the highest bandwidth supported by the O-RU DUT. - -- For O-RU DUT that support 5G NR: - - NR FR1 test models described in ETSI TS 138.141-1 are also applicable for *BS type 1-O* conformance testing. FR1 TDD downlink tests will use a standard 3GPP NR-FR1-TM1.1 test frame for TDD. - - FR2 TDD downlink tests will use a standard 3GPP NR-FR2-TM1.1 test frame for TDD in (clause 4.9.2 ETSI TS 138.141-2) of the Radiated Transmitter Characteristic Test (clause 6 ETSI TS 138.141-2) as described in clause 3.2.1.1. The test numerology will be preferably 120kHz subcarrier spacing and 100 MHz Bandwidth, or lower depending on DUT capability. If not supported, then it will use any other supported subcarrier spacing and the highest bandwidth of the O-RU DUT. - - NR FR1 test models described in ETSI TS 138.141-1 are also applicable for *BS type 1-O* conformance testing. FR1 TDD uplink tests will use a standard 3GPP G-FR1\_A1-5\_SCS30kHz\_51RB test frame for TDD. - - FR2 TDD uplink tests will use a standard 3GPP Reference Sensitivity level definition (clause 7.2 and Annex A ETSI TS 138.141-2) of the Radiated Receiver Characteristic Test (clause 7 ETSI TS 138.141-2). The O-RU manufacturer declares a minimum EIS level for the considered OTA sensitivity direction declaration. The power levels inclining from the angle of arrival that should be tested (RoAoA) is at least 30dB above the OSDD EIS Reference Sensitivity power level. The test numerology will be preferably 120kHz subcarrier spacing and 100 MHz Bandwidth based on G-FR2-A1-3 in ETSI TS 138.141-2, or lower depending on DUT capability. Otherwise, it will use any available subcarrier spacing and the highest bandwidth supported by the O-RU DUT. -- Radiated tests coordinate system is based on the coordinate system defined in O-RAN CUS Specification [2], clause 12.5.2. -- The O-RU DUT must: - - support the default parameters in clause 3.2.1.1.2 of this document. - - have installed current release of shipping software. - - be fully calibrated up to Radiated Interface Boundary (RIB) as defined in ETSI TS 138.141-2. It is expected to be calibrated by O-RU vendor prior to testing. -- The TER must: - - be capable of carrying out any signal processing required to generate and demodulate 3GPP compliant waveforms. - - be able to calculate or extract the spherical beam direction via OTA measurements. - - be able to generate and deliver signals with the required beam direction at the RIB point. - - be fully calibrated up to the interface where it interacts with the DUT's RIB. For that, a known test signal might be either injected by the TER into the O-RU DUT, or internally generated by the O-RU DUT, and the O-RU DUT must not apply any digital or analogue beam forming to apply a directional characteristic to the known test signal. One possible method to perform calibration uses injected C-Plane and U-Plane signals from TER into the O-RU and using C-Plane messages with beamID=0. Alternatively, calibration methods for radiated test setups that are described in ETSI TR 137.941 can be used. -- The O-DU emulator of the TER requirements as per clause 3.2.3.2 of the present specification. -- The TER might have a single test antenna if a single beam direction and polarization is measured and an optional positioning method to perform directional radiation measurements sequentially, or multiple test antennas to perform directional radiation measurements and/or polarizations at the same time. -- It is up to the TER on how to extract the beam direction and beam properties at the DUT's RIB in order to match it with the manufacturer's declaration. - -- The user payload will be generated as PN23 with a seed of all ones. -- It applies to the O-RAN CUS Specification [2] as per clause 3.2.3.2 of the present specification. - -### 3.2.6.2.1 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – No Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with no beamforming (beamId=0x000) and with one spatial stream (single eAxC). - -#### B. Test Entrance Criteria - -- Manufacturers' declaration that defines list of beam directions when O-RU DUT is operating with no beamforming. This list serves as indication of the expected transmitted beam direction in below evaluation. - -#### C. Test Methodology - -##### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in clause 3.2.1.1.4 and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in clause 3.2.1.1.4. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in clause 3.2.1.1.4. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -##### b. Procedure - -- Build an appropriate IQ signal describing the NR-FR1-TM1.1 or NR-FR2-TM1.1 signal described above in the O-DU emulator. -- Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (DL-SCH and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. -- Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.3.2.1.1.4. -- Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frame. -- Measure any metric/s that allows for extracting the transmitted beam direction from a single measurement, i.e. transform-based techniques, or take as many measurements as possible of any metric/s from multiple angles, by for example rotating the O-RU, that allows for extracting beam direction from multiple measurement, i.e. beam scanning. - -#### D. Test Requirement (expected result) - -1. The signal measured by the signal analyser at the contemplated transmitted beam direction should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). - -2. The test frame received at the contemplated transmitted beam direction by the signal analyser should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -3. The extracted or measured beam direction is defined as the direction where the best metric/s were measured (i.e. best EVM, power, SNR, etc.) and should match the expected transmitted beam direction for the expected no beamforming within a tolerance defined by the manufacturer. - -### 3.2.6.2.2 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – No Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with no beamforming (beamId=0x000) and with one spatial stream (single eAxC). - -#### B. Test Entrance Criteria - -- Manufacturers' declaration that defines list of beam directions when O-RU DUT is operating with no beamforming. This list serves as indication of the expected receive beam direction in below evaluation. - -#### C. Test Methodology - -##### a. Initial Conditions - -- Initial conditions as per clause 3.2.6.2.1 of the present specification - -##### b. Procedure - -- a. Build an appropriate test signal described above in the signal source of the TER. -- b. Inject the test signal into the O-RU with the application of an initial beam direction. This initial beam direction could be the boresight direction of the receiver antenna array, corresponding to the manufacturers declaration of the expected receive direction. -- c. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (UL-SCH) using Section Type 1 messages. No Section Type zero messages will be used for this test. -- d. Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.3.2.1.1.4 while also triggering the signal source. -- e. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU. -- f. Allow the O-DU to demodulate, decode and extract the payload and to measure and extract any required metric/s from the received signal that will be used later to determine what is the best received direction. -- g. Repeat the previous steps but now in step b apply a different beam direction when injecting the test signal into the O-RU. Repeating the process for a number of different beam directions will exercise the reception of the test signal from different receive beam directions. This allows to determine if the O-RU is really focusing the sensitivity to the correct expected receive beam direction. - -#### D. Test Requirement (expected result) - -1. The test frame received at the contemplated receive beam direction by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -2. The extracted or measured receive beam direction is defined as the direction where the best metric/s were measured (i.e. best EVM, power, SNR, etc.) and should match the expected receive beam direction for the expected no beamforming within a tolerance defined by the manufacturer. - -### 3.2.6.2.3 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Predefined-beam Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with predefined-beams beamforming (beamId $\neq$ 0x000) and with one spatial stream (single eAxC). - -The transmitted beam direction is measured for each indexed beam required in this measurement, see below. The measured transmitted direction is compared to manufacturer-designated direction. Transmitted beam direction is defined by extracting the beam direction from directional measurement samples. - -Depending on the O-RU beamforming capabilities regarding the ability to generate “coarse”, “fine” and/or “beam groups”, as defined in O-RAN CUS Specification [2], clause 12.4.2.2. - -The elevation $\theta$ and azimuth $\Phi$ angles are defined in O-RAN CUS Specification [2], clause 12.4.2.2. - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Predefined-beam Beamforming conformance test might include multiple tests that the O-RU must comply: - -##### a. “Coarse” beamIds test: - -If O-RU supports and reports beamIds that are defined as coarse granularity (coarse beamIds) to the O-DU emulator, the test should include the following beams: - -1. A coarse beam with 0 degrees azimuth ( $\Phi$ ) and elevation ( $\theta$ ) angles. -2. A coarse beam with maximum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -3. A coarse beam with maximum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). -4. A coarse beam with minimum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -5. A coarse beam with minimum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). - -If the O-RU only supports one azimuth ( $\Phi$ ) or elevation angle ( $\theta$ ), fewer than 5 beam angles will be measured. - -##### b. “Fine” beamIds test: - -If O-RU supports and reports beamIds that are defined as fine granularity (fine beamIds) to the O-DU emulator, the test should include the following beams: - -1. A fine beam with 0 degrees azimuth ( $\Phi$ ) and elevation ( $\theta$ ) angles. -2. A fine beam with maximum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -3. A fine beam with maximum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). -4. A fine beam with minimum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -5. A fine beam with minimum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). - -If the O-RU only supports one azimuth or elevation angle, fewer than 5 beam angles will be measured. - -##### c. “beam-group” beamIds test: - -If O-RU supports and reports beamIds that belong to same and different beam-groups to the O-DU emulator, the test should include the following beams: - -1. All beams that belong to a beam-group with 0 degrees azimuth ( $\Phi$ ) or elevation ( $\theta$ ) angles. -2. All beams that belong to a beam-group with maximum supported azimuth angle ( $\Phi$ ). - -3. All beams that belong to a beam-group with minimum supported azimuth angle ( $\Phi$ ). -4. All beams that belong to a beam-group with maximum supported elevation angle ( $\theta$ ). -5. All beams that belong to a beam-group with minimum supported elevation angle ( $\theta$ ). - -If the O-RU only supports one azimuth or elevation angle, fewer than 5 beam-groups will be measured. - -#### **B. Test Entrance Criteria** - -- Manufacturers' defined list of beam indices and their associated beam directions with antenna array characteristics. This list serves as indication of the expected transmitted beam direction in below evaluation. - -#### **C. Test Methodology** - -##### **a. Initial Conditions** - -Initial conditions as per clause 3.2.6.2.1 of the present specification. - -##### **b. Procedure** - -Procedure as per clause 3.2.6.2.1 of the present specification. - -#### **D. Test Requirement (expected result)** - -Test Requirement as per clause 3.2.6.2.1 of the present specification. - -### **3.2.6.2.4 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Predefined-beam Beamforming** - -#### **A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with predefined-beams beamforming (beamId $\neq$ 0x000) and with one spatial stream (single eAxC). - -The same description and criteria for selecting the beams to be tested applies as in clause 3.2.6.2.3 applies, but instead it is related to the uplink direction. - -#### **B. Test Entrance Criteria** - -- Manufacturers' defined list of beam indices and their associated beam directions with antenna array characteristics. This list serves as indication of the expected receive beam direction in below evaluation. - -#### **C. Test Methodology** - -##### **a. Initial Conditions** - -Initial conditions as per clause 3.2.6.2.2 of the present specification - -##### **b. Procedure** - -Procedure as per clause 3.2.6.2.2 of the present specification - -#### **D. Test Requirement (expected result)** - -Test Requirement as per Section 3.2.6.2.2 of the present specification - -### 3.2.6.2.5 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Weight-based Dynamic Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with weight-based dynamic beamforming with one spatial stream (single eAxC). - -The transmitted beam direction is measured for each weighted beam required in this measurement, see below. The measured transmitted direction is compared to manufacturer-designated direction. Transmitted beam direction is obtained by directly extracting the beam direction from the directional samples. - -The elevation $\theta$ and azimuth $\Phi$ angles are defined in O-RAN CUS Specification [2], clause 12.4.2.2. - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Weight-based Dynamic Beamforming conformance test should evaluate the following beams for the O-RU to comply: - -- A weight-based beam with 0 degrees azimuth ( $\Phi$ ) and elevation ( $\theta$ ) angles. -- A weight-based beam with maximum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -- A weight-based beam with maximum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). -- A weight-based beam with minimum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ). -- A weight-based beam with minimum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ). - -If the O-RU only supports one azimuth ( $\Phi$ ) or elevation angle ( $\theta$ ), fewer than 5 beam angles will be measured. - -The user/tester selects the bitwidth for the mantissa or scaler of the compression method applied to the beams. The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Weight-based Dynamic Beamforming conformance test should also evaluate the following compression methods for each of the supported beams described above (a. to e.) for the O-RU to comply: - -- No compression method applied to the beamforming weights. -- Block floating point compression method applied to the beamforming weights with the selected number of bit mantissa. -- Block scaling compression method applied to the beamforming weights with the selected number of bit scaler. -- $\mu$ -law compression method applied to the beamforming weights with the selected number of bit fixed width. -- Beamspace compression method applied to the beamforming weights with the selected number of bit scaler. - -If the O-RU does not support all the compression methods described above, fewer than 5 compression methods will be measured. - -#### B. Test Entrance Criteria - -Manufacturers' defined list of frequency domain ( $\phi$ ) and/or time domain ( $\theta$ ) weights and their associated beam directions with antenna array characteristics - -#### C. Test Methodology - -**a. Initial Conditions** - -Initial conditions as per clause 3.2.6.2.1 of the present specification - -**b. Procedure** - -- a. Build an appropriate IQ signal as per clause 3.2.6.2.1 of the present specification. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by one or two sections (DL-SCH and DCI) using Section Type 1 messages, the sections in the first symbol of the slot will contain section extension extType=0x01 to convey the beam weights, it is not required that the next sections contain extension type 1 since the same beam IDs will not change along the slot. If O-RU does not support a field, then its value should be 0x0. No Section Type zero messages will be used for this test. -- c. Perform additional procedure steps c, d, and e as per clause 3.2.6.2.1 of the present specification. - -**D. Test Requirement (expected result)** - -Test Requirement as per Section 3.2.6.2.1 of the present specification - -**3.2.6.2.6 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Weight-based Dynamic Beamforming****A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with weight-based beamforming and with one spatial stream (single eAxC). - -The same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.2.5 but applies to the uplink direction. - -**B. Test Entrance Criteria** - -Manufacturers' defined list of frequency domain ( $\phi$ ) and/or time domain ( $\theta$ ) weights and their associated beam directions with antenna array characteristics. - -**C. Test Methodology****a. Initial Conditions** - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.3.2.1.1.4 and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.3.2.1.1.4. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.3.2.1.1.4. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -- a. Build an appropriate test signal related to either FR1 or FR2 described above in the signal source of the TER. -- b. Inject the test signal into the O-RU with the application of an initial beam direction as fulfilling the expected spherical RoAoA. For example, initial beam direction could be the boresight of the receive antenna array. -- c. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by one or two sections (UL-SCH) using Section Type 1 messages, the sections in the first symbol of the slot will contain section extension extType=0x01 to convey the beam weights, it is not required that the next sections contain extension type 1 since the same beam IDs will not change along the slot. If O-RU does not support a field, then its value should be 0x0. No Section Type zero messages will be used for this test. -- d. Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. while also triggering the signal source. -- e. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. -- f. Repeat the previous steps but now in step b apply a different inclining beam direction or RoAoA. For example, repeating the process for a number of different beam directions. This allows to determine if the O-RU is really focusing the sensitivity to the correct beam direction. - -#### D. Test Requirement (expected result) - -Test Requirement as per clause 3.2.6.2.2 of the present specification. - -### 3.2.6.2.7 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Attribute-based Dynamic Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with attributed-based dynamic beamforming with one spatial stream (single eAxC). - -If the O-RU DUT supports Attribute based Dynamic Beamforming, this test is mandatory for the O-RU DUT to be O-RAN conformant. - -The transmitted beam direction and attributes are measured for each attributed beam required in this measurement, see below. The measured transmitted direction and attributes, i.e. pointing azimuth and elevation angles, beamwidths and sidelobe suppression, is compared to manufacturer-designated direction and attributes. Transmitted direction and beam attributes are defined by the magnitude and phase relation between the antenna ports or TAB connectors under test, or by directly extracting the beam properties. - -The elevation $\theta$ and azimuth $\Phi$ angles are defined in O-RAN CUS Specification [2], clause 12.4.2.2. - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Attribute-based Dynamic Beamforming conformance test should evaluate the following beams for the O-RU to comply: - -- a. An attribute-based beam with 0 degrees azimuth ( $\Phi$ ) and elevation ( $\theta$ ) angles with any beamwidth and sidelobe suppression supported by the O-RU under this beam direction. -- b. An attribute-based beam with maximum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ) with the widest beamwidth and lowest sidelobe suppression supported for this specific beam direction. -- c. An attribute-based beam with maximum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ) with the narrowest beamwidth and highest sidelobe suppression supported for this specific beam direction. - -- d. An attribute-based beam with minimum supported azimuth angle ( $\Phi$ ) and maximum supported elevation angle ( $\theta$ ) with the widest beamwidth and lowest sidelobe suppression supported for this specific beam direction. -- e. An attribute-based beam with minimum supported azimuth angle ( $\Phi$ ) and minimum supported elevation angle ( $\theta$ ) with the narrowest beamwidth and highest sidelobe suppression supported for this specific beam direction. - -If the O-RU only supports one azimuth ( $\Phi$ ) or elevation angle ( $\theta$ ), fewer than 5 beam angles and attribute configurations will be measured. - -## B. Test Entrance Criteria - -Manufacturers' defined list of frequency domain ( $\phi$ ) and/or time domain ( $\theta$ ) weights and their associated beam directions with antenna array characteristics. - -## C. Test Methodology - -### a. Initial Conditions - -Initial conditions as per clause 3.2.6.2.1 of the present specification. - -### b. Procedure - -- a. Build an appropriate IQ signal describing the NR-FR1-TM1.1 or NR-FR2-TM1.1 signal described above in the O-DU emulator. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by one or two sections (DL-SCH and DCI) using Section Type 1 messages, the sections in the first symbol of the slot will contain section extension extType=0x02 to convey the beam weights, it is not required that the next sections contain extension type 2 since the same beam IDs will not change along the slot. If O-RU does not support a field, then its value should be 0x0. No Section Type zero messages will be used for this test. -- c. Perform steps c, d, and e as per clause 3.2.6.2.1 of the present specification. - -## D. Test Requirement (expected result) - -Test Requirement as per clause 3.2.6.2.1 of the present specification. - -### 3.2.6.2.8 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Attribute-based Dynamic Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with attribute-based beamforming with one spatial stream (single eAxC). - -Same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.2.7 but considering uplink direction. - -#### B. Test Entrance Criteria - -Manufacturers' defined list of frequency domain ( $\phi$ ) and/or time domain ( $\theta$ ) weights and their associated beam directions with antenna array characteristics. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antenna/s and TER equipment is calibrated within acceptable tolerance. -- Place the test antenna/s to a defined position within the OTA chamber as defined in 3.2.1.1.3.2.1.1.4 and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.3.2.1.1.4. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.3.2.1.1.4. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- a. Build an appropriate test signal either related to FR1 or FR2, described above in the signal source of the TER. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by one or two sections (UL-SCH) using Section Type 1 messages, the sections in the first symbol of the slot will contain section extension extType=0x02 to convey the beam weights, it is not required that the next sections contain extension type 2 since the same beam IDs will not change along the slot. If O-RU does not support a field, then its value should be 0x0. No Section Type zero messages will be used for this test. -- c. Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. while also triggering the signal source. -- d. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. -- e. Repeat the previous steps but now in step b apply a different inclining beam direction or RoAoA. For example, repeating the process for a number of different beam directions. This allows the tester to determine if the O-RU is really focusing the sensitivity to the correct beam direction. - -## D. Test Requirement (expected result) - -1. The test frame received by the TER/O-DU should be the same as the signal described above and should contain all the same PRB assignments and all the original PN23 data. -2. The extracted or measured receive beam direction is defined as the direction where the best metric/s were measured (i.e. best EVM, power, SNR, etc.) and should match the expected receive beam direction for the beam under test within a tolerance defined by the manufacturer - -### 3.2.6.2.9 UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Channel-Information-based Beamforming - -#### A. Test Description and Applicability - -This Test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can transmit a basic 3GPP test frame with channel-information-based beamforming with multiple spatial streams from multiple users (i.e. MU-MIMO). - -For Category A radios, the test is for each polarization separately and consequently either different or same channel models can be defined for each of the polarization. For Category B, same channel might be used for both polarizations and the test might measure each polarization separately. - -The transmitted beam direction is measured for each scenario required in this measurement. The measured transmitted direction is extracted from the decoded received signal in the TER. Transmitted direction is defined by properly receiving a data transmission between the O-RU and the target User Equipment while destroying or heavily attenuating the data transmission between the O-RU and the other User Equipment. - -The UC-Plane O-RU Scenario Class Beamforming 3GPP DL – Channel-Information-based Beamforming conformance test should evaluate the following scenarios for the O-RU to comply and will rely on TER Channel Emulation capabilities as shown in Figure 3.2.6.2-65. - -![Diagram of Test Equipment (RU (TER)) showing the DUT (O-RU) connected to multiple UEs via antennas. The DUT contains a Precoding Matrix G. Inputs are UE 0 Layer 0 (eAxC 0) and UE 1 Layer 0 (eAxC 1). Outputs are M antennas connected to UE 0 Layer 0 and UE 1 Layer 0.](3b6fe8cf6869f2ed1d7433b9c5503b38_img.jpg) - -The diagram illustrates the Test Equipment (RU (TER)) setup. It consists of a large green box labeled 'Test Equipment, RU (TER)'. Inside this box is a red box labeled 'DUT = O-RU'. Within the DUT, there is a block labeled 'Precoding Matrix G'. Two inputs, 'UE 0 Layer 0' (eAxC 0) and 'UE 1 Layer 0' (eAxC 1), enter the Precoding Matrix G. The output of the matrix is connected to a vertical stack of M antennas, represented by dots. These antennas are connected to two output boxes labeled 'UE 0 Layer 0' and 'UE 1 Layer 0'. - -Diagram of Test Equipment (RU (TER)) showing the DUT (O-RU) connected to multiple UEs via antennas. The DUT contains a Precoding Matrix G. Inputs are UE 0 Layer 0 (eAxC 0) and UE 1 Layer 0 (eAxC 1). Outputs are M antennas connected to UE 0 Layer 0 and UE 1 Layer 0. - -Figure 3.2.6.2-65 TER with antennas representing multiple UEs - -- b. A scenario where two spatial streams, or eAxC flows, are generated for two users (one layer each) with M antennas ports or TAB connectors. The O-DU will report to the O-RU via C plane messages the channel estimate , which is the effective channel as seen by the antennas representing the multiple UEs, which are spaced sufficiently such that the O-RU can effectively equalize out the interference between the users. The O-RU will calculate and apply the beamweight matrix in such that the received signal at the users is the same as the generated in the O-DU. It is up to the O-RU on how to calculate the beamforming weights, for example Zero-forcing, regularized zero-forcing / MMSE, etc. - -If O-RU supports Analog Beamforming (Time Domain Beamforming), the test should not apply any analogue beamforming or time domain beamforming. In this case, M is not the number of antennas ports or TAB connectors but the number of TRX channels supported by the O-RU. - -## B. Test Entrance Criteria - -- The O-RU must have at least two TRX chains with radiating antennas -- The TER equipment must include 2 antennas with sufficient separation to emulate the 2 users such that the O-RU can equalize out the mutual interference of the users due to the effective MU-MIMO channel. - -- Manufacturers' defined list of number of TRX chains and what antennas are connected to each TRX chain - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antennas and TER equipment are calibrated within acceptable tolerance. -- Place the test antennas within the OTA chamber as defined in 3.2.1.1.4 with sufficient separation for effective MU-MIMO beamforming and configure the analyser ports with any setup information needed to synch and demodulate the MU-MIMO transmitted signal -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.4. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.4. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- a. Build an appropriate IQ signal describing the NR-FR1-TM1.1 signal described above in the O-DU emulator, with the data symbols for user 1 and user 2 fully overlapping in time and frequency, but with user data initialized using different seeds for the PN23 sequence. -- b. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. Every symbol should be described by either one or two sections (DL-SCH and DCI) using Section Type 5 and 6 messages. No Section Type zero messages will be used for this test. -- c. Encapsulate the IQ data in U-Plane messages. Play those messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- d. Capture the test signals and pass them through a channel emulator or apply the signal processing required to emulate the channel under test using the 2 test antennas. -- e. Repeat the entire frame the number of times required to synch the signal analyser and allow it to demodulate and decode the test frames for the 2 users. - -## D. Test Requirement (expected result) - -1. The signal measured by the signal analyser should satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received by the signal analyser for the 2 users should be the same as the signal described above and should contain all the same PRB assignments and all the respective PN23 data. - -## 3.2.6.2.10 UC-Plane O-RU Scenario Class Beamforming 3GPP UL – Channel-Information-based Beamforming - -### A. Test Description and Applicability - -This Test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure the radio can receive a basic 3GPP test frame with channel-information-based beamforming with multiple spatial streams from multiple users (i.e. MU-MIMO). - -Same description and criteria for selecting the beams to be tested applies as in clause 3.2.3.10 and 3.2.6.2.9 but considering the uplink direction. - -### B. Test Entrance Criteria - -- The O-RU must have at least two TRX chains with radiating sensing antennas - - The TER equipment must include 2 antennas with sufficient separation to emulate the 2 users such that the O-RU can equalize out the mutual interference of the users due to the effective MU-MIMO channel. - - The O-RU must have at least two TRX chains with conducted antenna ports (or TAB connectors) to be connected to a signal generator. - - The TER equipment must include 2 antennas with sufficient separation to emulate the 2 users the O-RU need to be able to equalize out the mutual interference of the users due to the effective MU-MIMO channel. -- Manufacturers' defined list of number of TRX chains and what antennas are connected to each TRX chain. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- Ensure that the test antennas and TER equipment are calibrated within acceptable tolerance. -- Place the test antennas within the OTA chamber as defined in 3.2.1.1.4 with sufficient separation for effective MU-MIMO beamforming and configure the generator ports with any setup information needed to transmit the signals from the 2 UEs -- Place the O-RU into a test calibrated point within the OTA chamber as defined in 3.2.1.1.4. -- Align the O-RU to a default initial position, i.e. align the O-RU to the origin of coordinates of the declared coordinate reference point and orientation in the OTA chamber as defined in 3.2.1.1.4. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- a. Build the appropriate test signals for each of the 2 users as described above in the signal source of the TER using a different seed to initialize the PN23 data for each user. -- b. Transmit the test signals over the air with sufficient transmit power according to 3.2.1.1.4 -- c. Use the O-DU emulator control interface to build the appropriate C-Plane messages that describe the signal and the beam under test. Every symbol should be described by either one or two sections (UL-SCH) using Section Type 5 and 6. No Section Type zero messages will be used for this test. -- d. Play the C plane messages to the O-RU respecting timing windows described in clause 2.4. while also triggering the signal source. -- e. Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U-plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload for each of the users. - -## D. Test Requirement (expected result) - -The test frames received by the TER/O-DU should be the same as the signals described above and should contain all the same PRB assignments and all the original PN23 data of the 2 users. - -### 3.2.6.3 UC-Plane O-RU Scenario Class Compression (CMP) - -The compression tests for FR1 and FR2 TDD Non-conducted OTA are the same as the tests described in clause 3.2.5.3 for FR1. For FR2, similar test frames with 120 kHz SCS shall be used in the test. Only the setup for the tests is different reflecting the difference between non-conductive and conductive mode testing. - -### 3.2.6.4 UC-Plane O-RU Scenario Class Delay Management (DLM) - -The delay management tests for FR1 and FR2 TDD Non-conducted OTA are the same as the tests described in clause 3.2.5.4 for FR1. For FR2, similar test frames with 120 kHz SCS shall be used in the test. Only the setup for the tests is - -different reflecting the difference between non-conductive and conductive mode testing. - -### 3.2.6.5 UC-Plane O-RU Scenario Class Transport (TRN) - -This test is for future study. - -### 3.2.6.6 UC-Plane O-RU Scenario Class LAA (LAA) - -The LAA tests for FR1 TDD Non-conducted OTA are the same as the tests described in clause 3.2.5.6. Only the setup for the tests is different reflecting the difference between non-conductive and conductive mode testing. Note that LAA tests are not applicable for the FR2 spectrum. - -### 3.2.6.7 UC-Plane O-RU Scenario Class LTE (LTE) - -This test is for future study. - -### 3.2.6.8 UC-Plane O-RU Scenario Class Section Type 3 (ST3) - -The Section Type 3 tests for FR1 and FR2 TDD Non-conducted OTA are the same as the tests described in clause 3.2.5.8 for FR1. For FR2, similar test frames with 120 kHz SCS shall be used in the test. Only the setup for the tests is different reflecting the difference between non-conductive and conductive mode testing. - -## 3.2.7 Energy Savings - -### 3.2.7.1 C-Plane based TRX control - -#### 3.2.7.1.1 C-Plane based TRX Control (defined-duration sleep, guaranteed wake-up duration) - -#### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY - -The purpose of this test is to ensure O-RU is capable of C-plane based TRX control. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings. - -This scenario corresponds to the following clause in [2]: - -- 7.2.9 Section Type 4: Slot Configuration Control -- 7.3.1 Section Types -- 7.4.6 Section Type 4 elements -- 7.5.2 Application layer, common -- 16 Energy-saving functionality - -following clause in [3]: - -- 20.3.1 TRX control – C-Plane controlled - -#### B. Test Entrance Criteria - -- The O-RU shall support the default parameters of at least one of the scenarios given below, - -| Scenario | Default parameters | -|----------------------------------------|--------------------| -| FR1 FDD Conducted-Signal Tests | clause 3.2.1.1.1 | -| FR1 FDD Non-conducted OTA Signal Tests | clause 3.2.1.1.2 | -| FR1 TDD Conducted Signal Tests | clause 3.2.1.1.3 | -| FR1 TDD Non-conducted OTA Signal Tests | clause 3.2.1.1.4 | - -- The test numerology is 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1. If the O-RU does not support this numerology, any other numerology that the O-RU supports can be used. -- The O-RU shall have a conducted antenna port (or TAB connector) to be connected to a signal analyser, if the O-RU capabilities match scenario defined in clause 3.2.1.1.1 or clause 3.2.1.1.3. - -## C. Test Methodology - -### a. Initial Conditions - -1. Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -2. The O-RU exposes the capability to support energy savings including C-Plane based TRX control (defined-duration sleep, guaranteed wake-up duration) -3. Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -4. Connect the signal generator to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -5. Let the DUT and TER to warm to the normal operating temperature within specified range. - -### a. Procedure - -1. Build an appropriate IQ signal as described above in clause B. Test Entrance Criteria in the CUSM emulator. -2. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. The C-Plane processing and user traffic are enabled. -3. The TER measures the AC or DC power consumption of the O-RU using power meter. -4. The O-DU emulator enables energy savings by signalling Section Type 4 (st4CmdType = 3 for TRX\_CONTROL) by setting "symbolMask" field to 0x3FFF to indicate all symbols in a slot made or kept inactive, "sleepMode" field to indicate sleep mode, "numSlots", "numSlotsExt" field for defined-duration sleep and "antMask" field with "0" in each array element that is to be made or kept inactive. - -NOTE: Defined-duration sleep needs to be greater than the double the wake-up duration. It is recommended to set longer sleep duration, allowing for the power consumption measurements to be made. It is recommended to set at least half of the array elements off (0 indicates off) in the antenna mask to better observe power changes. - -5. The TER waits for a sufficient duration to ensure some or all of the O-RU's antenna array elements have reached sleep condition, for example a duration greater than the wake-up duration. This ensures C-Plane processing and user traffic are disabled for some or all of the O-RU's antenna array elements. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU's antenna array elements have reached sleep condition. - -6. The TER performs the DC or AC power consumption measurement with the power meter. -7. The power consumption should be smaller than the previous one measured in the step 3. - -8. After defined-duration sleep expiry the C-Plane processing and user traffic are enabled. The TER performs the DC or AC power consumption measurement with the power meter. -9. The power consumption should be greater than the previous one measured in the step 6. - -**D. Test Requirement (expected result)** - -1. Test steps above are performed successfully. -2. All validation steps mentioned in step 7 and step 9 are within expected power ranges as per the vendor product specifications. - -**3.2.7.1.2 C-Plane based TRX Control (defined-duration sleep, minimum wake-up duration)** - -**A. Test Description and Applicability** - -This scenario is CONDITIONAL MANDATORY - -The purpose of this test is to ensure O-RU is capable of C-plane based TRX control. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings. - -This scenario corresponds to the following clause in [2]: - -- 7.2.9 Section Type 4: Slot Configuration Control -- 7.3.1 Section Types -- 7.4.6 Section Type 4 elements -- 7.4.10 Section Type 8 elements -- 7.5.2 Application layer, common -- 7.5.3.55 ready -- 16 Energy-saving functionality - -following clause in [3]: - -- 20.3.1 TRX control – C-Plane controlled - -**B. Test Entrance Criteria** - -- The O-RU shall support the default parameters of at least one of the scenarios given below, - -| Scenario | Default parameters | -|----------------------------------------|--------------------| -| FR1 FDD Conducted-Signal Tests | clause 3.2.1.1.1 | -| FR1 FDD Non-conducted OTA Signal Tests | clause 3.2.1.1.2 | -| FR1 TDD Conducted Signal Tests | clause 3.2.1.1.3 | -| FR1 TDD Non-conducted OTA Signal Tests | clause 3.2.1.1.4 | - -- The test numerology is 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1. If the O-RU does not support this numerology, any other numerology that the O-RU supports can be used. -- The O-RU shall have a conducted antenna port (or TAB connector) to be connected to a signal analyser, if the O-RU capabilities match scenario defined in clause 3.2.1.1.1 or clause 3.2.1.1.3. - -**C. Test Methodology** - -**a. Initial Conditions** - -1. Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -2. The O-RU exposes the capability to support energy savings including C-Plane based TRX control (defined-duration sleep, minimum wake-up duration) -3. Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. - -4. Connect the signal generator to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -5. Let the DUT and TER to warm to the normal operating temperature within specified range. - -**a. Procedure** - -1. Build an appropriate IQ signal as described above in clause B. Test Entrance Criteria in the CUSM emulator. -2. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. The C-Plane processing and user traffic are enabled. -3. The TER measures the AC or DC power consumption of the O-RU using power meter. -4. The O-DU emulator enables energy savings by signalling Section Type 4 (st4CmdType = 3 for TRX\_CONTROL) by setting “symbolMask” field to 0x3FFF, “sleepMode” field to indicate sleep mode, “numSlots”, “numSlotsExt” field for defined-duration sleep and “antMask” field with "0" in each array element that is to be made or kept inactive. - -NOTE: Defined-duration sleep needs to be greater than double the wake-up duration. It is recommended to set longer sleep duration, allowing for the power consumption measurements to be made. It is recommended to set at least half of the array elements off (0 indicates off) in the antenna mask to better observe power changes. - -5. The TER waits for a sufficient duration to ensure some or all of the O-RU's antenna array elements have reached sleep condition, for example a duration greater than the wake-up duration. This ensures C-Plane processing and user traffic are disabled for some or all of the O-RU's antenna array elements. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU's antenna array elements have reached sleep condition. - -6. The TER performs the DC or AC power consumption measurement with the power meter. -7. The power consumption should be smaller than the previous one measured in the step 3. -8. The O-RU sends a "ready" message to the O-DU emulator to indicate termination of sleep, by setting ready bit to 1 in Section Type 8 command. -9. After the slotId value mentioned in the Section Type 8 command, the C-Plane processing and user traffic are enabled. The TER performs the DC or AC power consumption measurement with the power meter. -10. The power consumption should be greater than the previous one measured in the step 6. - -**D. Test Requirement (expected result)** - -1. Test steps above are performed successfully. -2. All validation steps mentioned in step 7 and step 10 are within the expected power ranges as per the vendor product specifications. - -**3.2.7.1.3 C-Plane based TRX Control (undefined-duration sleep, guaranteed wake-up duration)** - -**A. Test Description and Applicability** - -This scenario is CONDITIONAL MANDATORY - -The purpose of this test is to ensure O-RU is capable of C-plane based TRX control. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings. - -This scenario corresponds to the following clause in [2]: - -- 7.2.9 Section Type 4: Slot Configuration Control -- 7.3.1 Section Types -- 7.4.6 Section Type 4 elements -- 7.5.2 Application layer, common -- 16 Energy-saving functionality - -following clause in [3]: - -- 20.3.1 TRX control – C-Plane controlled - -**B. Test Entrance Criteria** - -- The O-RU shall support the default parameters of at least one of the scenarios given below, - -| Scenario | Default parameters | -|----------------------------------------|--------------------| -| FR1 FDD Conducted-Signal Tests | clause 3.2.1.1.1 | -| FR1 FDD Non-conducted OTA Signal Tests | clause 3.2.1.1.2 | -| FR1 TDD Conducted Signal Tests | clause 3.2.1.1.3 | -| FR1 TDD Non-conducted OTA Signal Tests | clause 3.2.1.1.4 | - -- The test numerology is 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1. If the O-RU does not support this numerology, any other numerology that the O-RU supports can be used. -- The O-RU shall have a conducted antenna port (or TAB connector) to be connected to a signal analyser, if the O-RU capabilities match scenario defined in clause 3.2.1.1.1 or clause 3.2.1.1.3. - -**C. Test Methodology** - -**a. Initial Conditions** - -1. Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -2. The O-RU exposes the capability to support energy savings including C-Plane based TRX control (undefined-duration sleep, guaranteed wake-up duration) -3. Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -4. Connect the signal generator to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -5. Let the DUT and TER to warm to the normal operating temperature within specified range. - -**a. Procedure** - -1. Build an appropriate IQ signal as described above in clause B. Test Entrance Criteria in the CUSM emulator. -2. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. The C-Plane processing and user traffic are enabled. -3. The TER measures the AC or DC power consumption of the O-RU using power meter. -4. The O-DU emulator enables energy savings by signalling Section Type 4 (st4CmdType = 3 for TRX\_CONTROL) by setting “sleepMode” field to indicate sleep mode, “symbolMask” field to 0x3FFF to indicate all symbols in a slot made or kept inactive, “numSlots” and “numSlotsExt” fields to 0 to indicate undefined-duration sleep and “antMask” field to "0" in each array element that is to be made or kept inactive. - -NOTE: It is recommended to set at least half of the array elements off (0 indicates off) in the antenna mask to better observe power changes. - -5. The TER waits for a sufficient duration to ensure some or all of the O-RU's antenna array elements have reached sleep condition, for example a duration greater than the wake-up duration. This ensures C-Plane processing and user traffic are disabled for some or all of the O-RU's antenna array elements. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU's antenna array elements have reached sleep condition. - -6. The TER performs the DC or AC power consumption measurement with the power meter. -7. The power consumption should be smaller than the previous one measured in the step 3. -8. The O-DU emulator issues a wake-up command by signalling Section Type 4 (st4CmdType = 3 for TRX\_CONTROL) by setting "sleepMode" field to indicate sleep mode, "symbolMask" field to 0x0000 to indicate all symbols in a slot made or kept active, "numSlots" and "numSlotsExt" fields to 0 to indicate undefined-duration sleep and "antMask" field to "1" in each array element that is to be made or kept active. - -NOTE: It is recommended to issue wake-up command after a sufficient duration (for example greater than wake-up duration), allowing for the power consumption measurements to be made. - -9. The TER waits for the time interval of wake-up duration. -10. The C-Plane processing and user traffic are enabled. The TER performs the DC or AC power consumption measurement with the power meter. -11. The power consumption should be greater than the previous one measured in the step 6. - -#### D. Test Requirement (expected result) - -1. Test steps above are performed successfully. -2. All validation steps mentioned in step 7 and step 11 are within the expected power ranges as per the vendor product specifications. - -### 3.2.7.1.4 C-Plane based TRX Control (undefined-duration sleep, minimum wake-up duration) - -#### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY - -The purpose of this test is to ensure O-RU is capable of C-plane based TRX control. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings. - -This scenario corresponds to the following clause in [2]: - -- 7.2.9 Section Type 4: Slot Configuration Control -- 7.3.1 Section Types -- 7.4.6 Section Type 4 elements -- 7.4.10 Section Type 8 elements -- 7.5.2 Application layer, common -- 7.5.3.55 ready -- 16 Energy-saving functionality - -following clause in [3]: - -- 20.3.1 TRX control – C-Plane controlled - -#### B. Test Entrance Criteria - -- The O-RU shall support the default parameters of at least one of the scenarios given below, - -| Scenario | Default parameters | -|----------------------------------------|--------------------| -| FR1 FDD Conducted-Signal Tests | clause 3.2.1.1.1 | -| FR1 FDD Non-conducted OTA Signal Tests | clause 3.2.1.1.2 | -| FR1 TDD Conducted Signal Tests | clause 3.2.1.1.3 | -| FR1 TDD Non-conducted OTA Signal Tests | clause 3.2.1.1.4 | - -- The test numerology is 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1. If the O-RU does not support this numerology, any other numerology that the O-RU supports can be used. -- The O-RU shall have a conducted antenna port (or TAB connector) to be connected to a signal analyser, if the O-RU capabilities match scenario defined in clause 3.2.1.1.1 or clause 3.2.1.1.3 - -## C. Test Methodology - -### a. Initial Conditions - -1. Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -2. The O-RU exposes the capability to support energy savings including C-Plane based TRX control (undefined-duration sleep, minimum wake-up duration) -3. Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -4. Connect the signal generator to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -5. Let the DUT and TER to warm to the normal operating temperature within specified range. - -### a. Procedure - -1. Build an appropriate IQ signal as described above in clause B. Test Entrance Criteria in the CUSM emulator. -2. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. The C-Plane processing and user traffic are enabled. -3. The TER measures the AC or DC power consumption of the O-RU using power meter. -4. The O-DU emulator enables energy savings by signalling Section Type 4 (st4CmdType = 3 for TRX\_CONTROL) by setting “sleepMode” field to indicate sleep mode, “symbolMask” field to 0x3FFF to indicate all symbols in a slot made or kept inactive, “numSlots” and “numSlotsExt” fields to 0, to indicate undefined-duration sleep and “antMask” field to "0" in each array element that is to be made or kept inactive. - -NOTE: It is recommended to set at least half of the array elements off (0 indicates off) in the antenna mask to better observe power changes. - -5. The TER waits for a sufficient duration to ensure some or all of the O-RU’s antenna array elements have reached sleep condition, for example a duration greater than the wake-up duration. This ensures C-Plane processing and user traffic are disabled for some or all of the O-RU’s antenna array elements. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU’s antenna array elements have reached sleep condition. - -6. The TER performs the DC or AC power consumption measurement with the power meter. -7. The power consumption should be smaller than the previous one measured in the step 3. -8. The O-DU emulator issues a wake-up command by signalling Section Type 4 (st4CmdType = 3 for TRX\_CONTROL) by setting “sleepMode” field to indicate sleep mode, “symbolMask” field to 0x0000 to - -indicate all symbols in a slot made or kept active, “numSlots” and “numSlotsExt” fields to 0 to indicate undefined duration sleep and “antMask” field to "1" in each array element that is to be made or kept active. - -NOTE: It is recommended to issue wake-up command after a sufficient duration (for example greater than wake-up duration), allowing for the power consumption measurements to be made. - -9. The O-RU sends a "ready" message to the O-DU emulator to indicate termination of sleep, by setting ready bit to 1 in Section Type 8 command. -10. After the slotId value mentioned in the Section Type 8 command, the C-Plane processing and user traffic are enabled. The TER performs the DC or AC power consumption measurement with the power meter. -11. The power consumption should be greater than the previous one measured in the step 6. - -**D. Test Requirement (expected result)** - -1. Test steps above are performed successfully. -2. All validation steps mentioned in step 7 and step 11 are within the expected power ranges as per the vendor product specifications. - -**3.2.7.1.5 C-Plane based TRX Control (sleep extension)** - -**A. Test Description and Applicability** - -This scenario is CONDITIONAL MANDATORY - -The purpose of this test is to ensure O-RU is capable of C-plane based TRX control that supports sleep extension. The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings. - -This scenario corresponds to the following clause in [2]: - -- 7.2.9 Section Type 4: Slot Configuration Control -- 7.3.1 Section Types -- 7.4.6 Section Type 4 elements -- 7.5.2 Application layer, common -- 16 Energy-saving functionality - -following clause in [3]: - -- 20.3.1 TRX control – C-Plane controlled - -**B. Test Entrance Criteria** - -- The O-RU shall support the default parameters of at least one of the scenarios given below, - -| Scenario | Default parameters | -|----------------------------------------|--------------------| -| FR1 FDD Conducted-Signal Tests | clause 3.2.1.1.1 | -| FR1 FDD Non-conducted OTA Signal Tests | clause 3.2.1.1.2 | -| FR1 TDD Conducted Signal Tests | clause 3.2.1.1.3 | -| FR1 TDD Non-conducted OTA Signal Tests | clause 3.2.1.1.4 | - -- The test numerology is 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause 3GPP 38.141 -1 NR-FR1-TM1.1. If the O-RU does not support this numerology, any other numerology that the O-RU supports can be used. -- The O-RU shall have a conducted antenna port (or TAB connector) to be connected to a signal analyser, if the O-RU capabilities match scenario defined in clause 3.2.1.1.1 or clause 3.2.1.1.3. - -**C. Test Methodology** - -**a. Initial Conditions** - -1. Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -2. The O-RU exposes the capability to support energy savings including C-Plane based TRX control (defined-duration sleep, guaranteed or minimum wake-up duration, sleep extension) -3. Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -4. Connect the signal generator to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -5. Let the DUT and TER to warm to the normal operating temperature within specified range. - -**a. Procedure** - -1. Build an appropriate IQ signal as described above in clause B. Test Entrance Criteria in the CUSM emulator. -2. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. The C-Plane processing and user traffic are enabled. -3. The TER measures the AC or DC power consumption of the O-RU using power meter. -4. The O-DU emulator enables energy savings by signalling Section Type 4 (st4CmdType = 3 for TRX\_CONTROL) by setting “symbolMask” field to 0x3FFF, “sleepMode” field to indicate sleep mode, “numSlots”, “numSlotsExt” field for defined-duration sleep and “antMask” field with "0" in each array element that is to be made or kept inactive. - -NOTE: Defined-duration sleep needs to be greater than double the wake-up duration. It is recommended to set longer sleep duration, allowing for the power consumption measurements to be made. It is recommended to set at least half of the array elements off (0 indicates off) in the antenna mask to better observe power changes. - -5. The TER waits for a sufficient duration to ensure some or all of the O-RU’s antenna array elements have reached sleep condition, for example a duration greater than the wake-up duration. This ensures C-Plane processing and user traffic are disabled for some or all of the O-RU’s antenna array elements. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU’s antenna array elements have reached sleep condition. - -6. The TER performs the DC or AC power consumption measurement with the power meter. -7. The power consumption should be smaller than the previous one measured in the step 3. -8. At the start of wake-up duration, the O-DU emulator sends sleep extension command by signalling Section Type 4 (st4CmdType = 3 for TRX\_CONTROL) by setting “symbolMask” field to 0x3FFF, “sleepMode” field ( any supported sleepMode other than sleep mode 0) for indicating sleep mode, “numSlots”, “numSlotsExt” field for defined-duration sleep and “antMask” field with "0" in each array element that is to be made or kept inactive. - -NOTE: Defined-duration sleep needs to be greater than or equal to the wake-up duration. It is recommended to set longer sleep duration, allowing for the power consumption measurements to be made. It is recommended to set at least half of the array elements off (0 indicates off) in the antenna mask to better observe power changes. - -9. The TER waits for a sufficient duration to ensure some or all of the O-RU’s antenna array elements have reached sleep condition, for example a duration greater than the wake-up duration. This ensures C-Plane processing and user traffic are disabled for some or all of the O-RU’s antenna array elements. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU's antenna array elements have reached sleep condition. - -10. The TER performs the DC or AC power consumption measurement with the power meter. -11. The power consumption should be smaller than the previous one measured in the step 3. -12. After defined-duration sleep expiry , the C-Plane processing and user traffic are enabled. The TER performs the DC or AC power consumption measurement with the power meter. -13. The power consumption should be greater than the previous one measured in the step 6 and step 10. - -**D. Test Requirement (expected result)** - -1. Test steps above are performed successfully. -2. All validation steps mentioned in step 7, step 11 and step 13 are within the expected power ranges as per the vendor product specifications. - -**3.2.7.1.6 C-Plane based TRX Control (Emergency wake-up)** - -**A. Test Description and Applicability** - -This scenario is CONDITIONAL MANDATORY - -The purpose of this test is to ensure O-RU is capable to do Emergency wake-up from C-plane based TRX control. The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings and emergency wake-up. - -This scenario corresponds to the following clause in [2]: - -- 7.2.9 Section Type 4: Slot Configuration Control -- 7.3.1 Section Types -- 7.4.6 Section Type 4 elements -- 7.5.2 Application layer, common -- 16 Energy-saving functionality - -following clause in [3]: - -- 20.3.1.3 Emergency wake-up procedure for TRX control - -**B. Test Entrance Criteria** - -- The O-RU shall support the default parameters of at least one of the scenarios given below, - -| Scenario | Default parameters | -|----------------------------------------|--------------------| -| FR1 FDD Conducted-Signal Tests | clause 3.2.1.1.1 | -| FR1 FDD Non-conducted OTA Signal Tests | clause 3.2.1.1.2 | -| FR1 TDD Conducted Signal Tests | clause 3.2.1.1.3 | -| FR1 TDD Non-conducted OTA Signal Tests | clause 3.2.1.1.4 | - -- The test numerology is 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause 3GPP 38.141 -1 NR-FR1-TM1.1. If the O-RU does not support this numerology, any other numerology that the O-RU supports can be used. -- The O-RU shall have a conducted antenna port (or TAB connector) to be connected to a signal analyser, if the O-RU capabilities match scenario defined in clause 3.2.1.1.1 or clause 3.2.1.1.3. - -**C. Test Methodology** - -**a. Initial Conditions** - -1. Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -2. The O-RU exposes the capability to support energy savings including C-Plane based TRX control (defined-duration sleep, guaranteed wake-up duration, emergency wake-up) - -3. Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -4. Connect the signal generator to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -5. Let the DUT and TER to warm to the normal operating temperature within specified range. - -**a. Procedure** - -1. Build an appropriate IQ signal as described above in clause B. Test Entrance Criteria in the CUSM emulator. -2. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. The C-Plane processing and user traffic are enabled. -3. The TER measures the AC or DC power consumption of the O-RU using power meter. -4. The O-DU emulator enables energy savings by signalling Section Type 4 (st4CmdType = 3 for TRX\_CONTROL) by setting “symbolMask” field to 0x3FFF, “sleepMode” field to indicate sleep mode, “numSlots”, “numSlotsExt” field for defined-duration sleep and “antMask” field with "0" in each array element that is to be made or kept inactive. - -NOTE: Defined-duration sleep needs to be greater than the double the wake-up duration. It is recommended to set longer sleep duration, allowing for the power consumption measurements to be made. It is recommended to set at least half of the array elements off (0 indicates off) in the antenna mask to better observe power changes. - -5. The TER waits for a sufficient duration to ensure some or all of the O-RU’s antenna array elements have reached sleep condition, for example a duration greater than the wake-up duration. This ensures C-Plane processing and user traffic are disabled for some or all of the O-RU’s antenna array elements. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU’s antenna array elements have reached sleep condition. The - -6. TER performs the DC or AC power consumption measurement with the power meter. -7. The power consumption should be smaller than the previous one measured in the step 3. -8. The TER NETCONF client sends a rpc. - -For Example, - -``` - - - - - - - - - - -``` - -9. The O-RU NETCONF Server responds with a message indicating successful completion of requested procedure. - -For Example, - -``` - - - -``` - -- The TER NETCONF Client waits for emergency-wake-up-complete notification , to ensure wake up is complete, the C-Plane processing and user traffic are enabled. -For Example, - -``` - - YYYY-MM-DDTHH:MM:SS.FZ - - -``` - -- The TER performs the DC or AC power consumption measurement with the power meter. -- The power consumption should be greater than the previous one measured in the step 6. - -**D. Test Requirement (expected result)** - -- Test steps above are performed successfully. -- All validation steps mentioned in step 7 and step 12 are within the expected power ranges as per the vendor product specifications. - -**3.2.7.2 Advanced Sleep Mode** - -**3.2.7.2.1 Advanced Sleep Mode (defined-duration sleep, guaranteed wake-up duration)** - -**A. Test Description and Applicability** - -This scenario is CONDITIONAL MANDATORY - -The purpose of this test is to ensure O-RU is capable of advanced sleep mode. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings. - -This scenario corresponds to the following clause in [2]: - -- 7.2.9 Section Type 4: Slot Configuration Control -- 7.3.1 Section Types -- 7.4.6 Section Type 4 elements -- 7.5.2 Application layer, common -- 16 Energy-saving functionality following clause in [3]: -- 20.4 Advanced sleep modes for energy saving - -**B. Test Entrance Criteria** - -- The O-RU shall support the default parameters of at least one of the scenarios given below, - -| Scenario | Default parameters | -|----------------------------------------|--------------------| -| FR1 FDD Conducted-Signal Tests | clause 3.2.1.1.1 | -| FR1 FDD Non-conducted OTA Signal Tests | clause 3.2.1.1.2 | -| FR1 TDD Conducted Signal Tests | clause 3.2.1.1.3 | -| FR1 TDD Non-conducted OTA Signal Tests | clause 3.2.1.1.4 | - -- The test numerology is 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1. If the O-RU does not support this numerology, any other numerology that the O-RU supports can be used. -- The O-RU shall have a conducted antenna port (or TAB connector) to be connected to a signal analyser, if the O-RU capabilities match scenario defined in clause 3.2.1.1.1 or clause 3.2.1.1.3. - -## C. Test Methodology - -### a. Initial Conditions - -1. Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -2. The O-RU exposes the capability to support energy savings including advanced sleep mode for defined-duration sleep, guaranteed wake-up duration. -3. Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports or TAB connectors within acceptable tolerance. -4. Connect the signal generator to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -5. Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -1. Build an appropriate IQ signal as described above in clause B. Test Entrance Criteria in the CUSM emulator. -2. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. The C-Plane processing and user traffic are enabled. -3. The TER measures the AC or DC power consumption of the O-RU using power meter. -4. The O-DU emulator enables energy savings by signalling section type 4 (st4CmdType = 4 for Advanced Sleep Mode) by setting “symbolMask” field to 0x3FFF to indicate all symbols in a slot made or kept inactive, “sleepMode” field to indicate sleep mode, “numSlots” and “numSlotsExt” field for defined-duration sleep. - -NOTE: Defined-duration sleep needs to be greater than the double the wake-up duration. It is recommended to set longer sleep duration, allowing for the power consumption measurements to be made. - -NOTE: It is recommended to set the duration for defined-duration sleep to be greater than the double the wake-up duration. Setting longer sleep duration allows for more appropriate power consumption measurements to be made. - -5. The TER waits for a sufficient duration to ensure all of the O-RU’s antenna array elements have reached sleep condition, for example a duration greater than the “wake-up duration”. This ensures C-Plane processing and user traffic are disabled for all of the O-RU’s antenna array elements. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU’s antenna array elements have reached sleep condition. - -6. The TER performs the DC or AC power consumption measurement with the power meter. -7. The power consumption should be smaller than the previous one measured in the step 3. -8. After defined-duration sleep expiry the C-Plane processing and user traffic are enabled. The TER performs the DC or AC power consumption measurement with the power meter. -9. The power consumption should be greater than the previous one measured in the step 6. - -**D. Test Requirement (expected result)** - -1. Test steps above are performed successfully. -2. All validation steps mentioned in step 7 and step 9 are within expected power ranges as per the vendor product specifications. - -**3.2.7.2.2 Advanced Sleep Mode (defined-duration sleep, minimum wake-up duration)** - -**A. Test Description and Applicability** - -This scenario is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure O-RU is capable of advanced sleep mode. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings. - -This scenario corresponds to the following clause in [2]: - -- 7.2.9 Section Type 4: Slot Configuration Control -- 7.3.1 Section Types -- 7.4.6 Section Type 4 elements -- 7.4.10 Section Type 8 elements -- 7.5.2 Application layer, common -- 7.5.3.55 ready -- 16 Energy-saving functionality following clause in [3]: -- 20.4 Advanced sleep modes for energy saving - -**B. Test Entrance Criteria** - -- The O-RU shall support the default parameters of at least one of the scenarios given below, - -| Scenario | Default parameters | -|----------------------------------------|--------------------| -| FR1 FDD Conducted-Signal Tests | clause 3.2.1.1.1 | -| FR1 FDD Non-conducted OTA Signal Tests | clause 3.2.1.1.2 | -| FR1 TDD Conducted Signal Tests | clause 3.2.1.1.3 | -| FR1 TDD Non-conducted OTA Signal Tests | clause 3.2.1.1.4 | - -- The test numerology is 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1. If the O-RU does not support this numerology, any other numerology that the O-RU supports can be used. -- The O-RU shall have a conducted antenna port (or TAB connector) to be connected to a signal analyser, if the O-RU capabilities match scenario defined in clause 3.2.1.1.1 or clause 3.2.1.1.3. - -**C. Test Methodology** - -**a. Initial Conditions** - -1. Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -2. The O-RU exposes the capability to support energy savings including advanced sleep mode for defined-duration sleep, minimum wake-up duration. -3. Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports or TAB connectors within acceptable tolerance. -4. Connect the signal generator to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -5. Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -1. Build an appropriate IQ signal as described above in clause B. Test Entrance Criteria in the CUSM emulator. -2. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. The C-Plane processing and user traffic are enabled. -3. The TER measures the AC or DC power consumption of the O-RU using power meter. -4. The O-DU emulator enables energy savings by signalling Section Type 4 (st4CmdType = 4 for Advanced Sleep Mode) by setting “symbolMask” field to 0x3FFF, “sleepMode” field to indicate sleep mode, “numSlots” and “numSlotsExt” field for defined-duration sleep. - -NOTE: Defined-duration sleep needs to be greater than double the wake-up duration. It is recommended to set longer sleep duration, allowing for the power consumption measurements to be made. - -5. The TER waits for a sufficient duration to ensure all of the O-RU’s antenna array elements have reached sleep condition, for example a duration greater than the wake-up duration. This ensures C-Plane processing and user traffic are disabled for all of the O-RU’s antenna array elements. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU’s antenna array elements have reached sleep condition. - -6. The TER performs the DC or AC power consumption measurement with the power meter. -7. The power consumption should be smaller than the previous one measured in the step 3. -8. The O-RU sends a "ready" message to the O-DU emulator to indicate termination of sleep, by setting ready bit to 1 in Section Type 8 command. -9. After the slotId value mentioned in the Section Type 8 command, the C-Plane processing and user traffic are enabled. The TER performs the DC or AC power consumption measurement with the power meter. -10. The power consumption should be greater than the previous one measured in the step 6. - -#### D. Test Requirement (expected result) - -1. Test steps above are performed successfully. -2. The validation steps mentioned in step 7 and step 10 are within the expected power ranges as per the vendor product specifications. - -### 3.2.7.2.3 Advanced Sleep Mode (undefined-duration sleep, guaranteed wake-up duration) - -#### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY - -The purpose of this test is to ensure O-RU is capable of advanced sleep mode. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings. - -This scenario corresponds to the following clause in [2]: - -- 7.2.9 Section Type 4: Slot Configuration Control -- 7.3.1 Section Types -- 7.4.6 Section Type 4 elements -- 7.5.2 Application layer, common -- 16 Energy-saving functionality following clause in [3]: -- 20.4 Advanced sleep modes for energy saving - -#### B. Test Entrance Criteria - -- The O-RU shall support the default parameters of at least one of the scenarios given below, - -| Scenario | Default parameters | -|----------------------------------------|--------------------| -| FR1 FDD Conducted-Signal Tests | clause 3.2.1.1.1 | -| FR1 FDD Non-conducted OTA Signal Tests | clause 3.2.1.1.2 | -| FR1 TDD Conducted Signal Tests | clause 3.2.1.1.3 | -| FR1 TDD Non-conducted OTA Signal Tests | clause 3.2.1.1.4 | - -- The test numerology is 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1. If the O-RU does not support this numerology, any other numerology that the O-RU supports can be used. -- The O-RU shall have a conducted antenna port (or TAB connector) to be connected to a signal analyser, if the O-RU capabilities match scenario defined in clause 3.2.1.1.1 or clause 3.2.1.1.3. - -## C. Test Methodology - -### a. Initial Conditions - -1. Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -2. The O-RU exposes the capability to support energy savings including advanced sleep mode for undefined-duration sleep, guaranteed wake-up duration. -3. Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports or TAB connectors within acceptable tolerance. -4. Connect the signal generator to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -5. Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -1. Build an appropriate IQ signal as described above in clause B. Test Entrance Criteria in the CUSM emulator. -2. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. The C-Plane processing and user traffic are enabled. -3. The TER measures the AC or DC power consumption of the O-RU using power meter. -4. The O-DU emulator enables energy savings by signalling Section Type 4 (st4CmdType = 4 for Advanced Sleep Mode) by setting "sleepMode" field to indicate sleep mode, "symbolMask" field to 0x3FFF to indicate all symbols in a slot made or kept inactive, "numSlots" and "numSlotsExt" fields to 0 to indicate undefined-duration sleep. -5. The TER waits for a sufficient duration to ensure all of the O-RU's antenna array elements have reached sleep condition, for example a duration greater than the wake-up duration. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration. This assures the power measurement is done after all of the O-RU's antenna array elements have reached sleep condition. - -6. The TER performs the DC or AC power consumption measurement with the power meter. -7. The power consumption should be smaller than the previous one measured in the step 3. -8. The O-DU emulator issues a wake-up command by signalling Section Type 4 (st4CmdType = 4 for Advanced Sleep Mode) by setting "sleepMode" field to indicate sleep mode, "symbolMask" field to 0x0000 to indicate all symbols in a slot made or kept active, "numSlots" and "numSlotsExt" fields to 0 to indicate undefined-duration sleep. - -NOTE: It is recommended to issue wake-up command after a sufficient duration (for example greater than wake-up duration), allowing for the power consumption measurements to be made. - -9. The TER waits for the time interval of wake-up duration. -10. The C-Plane processing and user traffic are enabled. The TER performs the DC or AC power consumption measurement with the power meter. -11. The power consumption should be greater than the previous one measured in the step 6. - -**D. Test Requirement (expected result)** - -1. Test steps above are performed successfully. -2. The validation steps mentioned in step 7 and step 11 are within the expected power ranges as per the vendor product specifications. - -**3.2.7.2.4 Advanced Sleep Mode (undefined-duration sleep, minimum wake-up duration)** - -**A. Test Description and Applicability** - -This scenario is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure O-RU is capable of advanced sleep mode. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings. - -This scenario corresponds to the following clause in [2]: - -- 7.2.9 Section Type 4: Slot Configuration Control -- 7.3.1 Section Types -- 7.4.6 Section Type 4 elements -- 7.4.10 Section Type 8 elements -- 7.5.2 Application layer, common -- 7.5.3.55 ready -- 16 Energy-saving functionality - -following clause in [3]: - -- 20.4 Advanced sleep modes for energy saving - -**B. Test Entrance Criteria** - -- The O-RU shall support the default parameters of at least one of the scenarios given below, - -| Scenario | Default parameters | -|----------------------------------------|--------------------| -| FR1 FDD Conducted-Signal Tests | clause 3.2.1.1.1 | -| FR1 FDD Non-conducted OTA Signal Tests | clause 3.2.1.1.2 | -| FR1 TDD Conducted Signal Tests | clause 3.2.1.1.3 | -| FR1 TDD Non-conducted OTA Signal Tests | clause 3.2.1.1.4 | - -- The test numerology is 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1. If the O-RU does not support this numerology, any other numerology that the O-RU supports can be used. -- The O-RU shall have a conducted antenna port (or TAB connector) to be connected to a signal analyser, if the O-RU capabilities match scenario defined in clause 3.2.1.1.1 or clause 3.2.1.1.3. - -**C. Test Methodology** - -**a. Initial Conditions** - -1. Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -2. The O-RU exposes the capability to support energy savings including advanced sleep mode for undefined-duration sleep, minimum wake-up duration. -3. Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports or TAB connectors within acceptable tolerance. - -4. Connect the signal generator to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -5. Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -1. Build an appropriate IQ signal as described above in clause B. Test Entrance Criteria in the CUSM emulator. -2. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. The C-Plane processing and user traffic are enabled. -3. The TER measures the AC or DC power consumption of the O-RU using power meter. -4. The O-DU emulator enables energy savings by signalling Section Type 4 (st4CmdType = 4 for Advanced Sleep Mode) by setting "sleepMode" field to indicate sleep mode, "symbolMask" field to 0x3FFF to indicate all symbols in a slot made or kept inactive, "numSlots" and "numSlotsExt" fields to 0, to indicate undefined-duration sleep. -5. The TER waits for a sufficient duration to ensure all of the O-RU's antenna array elements have reached sleep condition, for example a duration greater than the wake-up duration. This ensures C-Plane processing is halted and there is no possibility of user traffic. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU's antenna array elements have reached sleep condition. - -6. The TER performs the DC or AC power consumption measurement with the power meter. -7. The power consumption should be smaller than the previous one measured in the step 3. -8. The O-DU emulator issues a wake-up command by signalling Section Type 4 (st4CmdType = 4 for Advanced Sleep Mode) by setting "sleepMode" field to indicate sleep mode, "symbolMask" field to 0x0000 to indicate all symbols in a slot made or kept active, "numSlots" and "numSlotsExt" fields to 0 to indicate undefined duration sleep. - -NOTE: It is recommended to issue wake-up command after a sufficient duration (for example greater than wake-up duration), allowing for the power consumption measurements to be made. - -9. The O-RU sends a "ready" message to the O-DU emulator to indicate termination of sleep, by setting ready bit to 1 in Section Type 8 command. This enables C-Plane processing and user traffic. -10. After the slotId value mentioned in the Section Type 8 command, the C-Plane processing and user traffic are enabled. The TER performs the DC or AC power consumption measurement with the power meter. -11. The power consumption should be greater than the previous one measured in the step 6. - -**D. Test Requirement (expected result)** - -1. Test steps above are performed successfully. -2. The validation steps mentioned in step 7 and step 11 are within the expected power ranges as per the vendor product specifications. - -### 3.2.7.2.5 Advanced Sleep Mode (sleep extension) - -**A. Test Description and Applicability** - -This scenario is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure O-RU is capable of advanced sleep mode that supports sleep extension. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings. - -This scenario corresponds to the following clause in [2]: - -- 7.2.9 Section Type 4: Slot Configuration Control -- 7.3.1 Section Types -- 7.4.6 Section Type 4 elements -- 7.5.2 Application layer, common -- 16 Energy-saving functionality - -following clause in [3]: - -- 20.4 Advanced sleep modes for energy saving - -**B. Test Entrance Criteria** - -- The O-RU shall support the default parameters of at least one of the scenarios given below, - -| Scenario | Default parameters | -|----------------------------------------|--------------------| -| FR1 FDD Conducted-Signal Tests | clause 3.2.1.1.1 | -| FR1 FDD Non-conducted OTA Signal Tests | clause 3.2.1.1.2 | -| FR1 TDD Conducted Signal Tests | clause 3.2.1.1.3 | -| FR1 TDD Non-conducted OTA Signal Tests | clause 3.2.1.1.4 | - -- The test numerology is 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1. If the O-RU does not support this numerology, any other numerology that the O-RU supports can be used. -- The O-RU shall have a conducted antenna port (or TAB connector) to be connected to a signal analyser, if the O-RU capabilities match scenario defined in clause 3.2.1.1.1 or clause 3.2.1.1.3. - -**C. Test Methodology** - -**a. Initial Conditions** - -1. Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -2. The O-RU exposes the capability to support energy savings including advanced sleep mode for defined-duration sleep, guaranteed or minimum wake-up duration, sleep extensions. -3. Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports or TAB connectors within acceptable tolerance. -4. Connect the signal generator to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -5. Let the DUT and TER to warm to the normal operating temperature within specified range. - -**b. Procedure** - -1. Build an appropriate IQ signal as described above in clause B. Test Entrance Criteria in the CUSM emulator. -2. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. The C-Plane processing and user traffic are enabled. -3. The TER measures the AC or DC power consumption of the O-RU using power meter. -4. The O-DU emulator enables energy savings by signalling section type 4 (st4CmdType = 4 for Advanced Sleep Mode) by setting “symbolMask” field to 0x3FFF, “sleepMode” field to indicate sleep mode, “numSlots” and “numSlotsExt” field for defined-duration sleep. - -NOTE: Defined-duration sleep needs to be greater than double the wake-up duration. It is recommended to set longer sleep duration, allowing for the power consumption measurements to be made. - -5. The TER waits for a sufficient duration to ensure all of the O-RU’s antenna array elements have reached sleep condition, for example a duration greater than the wake-up duration. This ensures C-Plane processing is halted and there is no possibility of user traffic. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU's antenna array elements have reached sleep condition. - -6. The TER performs the DC or AC power consumption measurement with the power meter. -7. The power consumption should be smaller than the previous one measured in the step 3. -8. At the start of wake-up duration, the O-DU emulator sends sleep extension command by signalling section type 4 (st4CmdType = 4 for Advanced Sleep Mode) by setting "symbolMask" field to 0x3FFF, "sleepMode" field (any supported sleepMode other than sleep mode 0) for indicating sleep mode, "numSlots" and "numSlotsExt" field for defined-duration. - -NOTE: Defined-duration sleep needs to be greater than or equal to the wake-up duration. It is recommended to set longer sleep duration, allowing for the power consumption measurements to be made. - -9. The TER waits for a sufficient duration to ensure all of the O-RU's antenna array elements have reached sleep condition, for example a duration greater than the wake-up duration. This ensures C-Plane processing is halted and there is no possibility of user traffic. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU's antenna array elements have reached sleep condition. - -10. The TER performs the DC or AC power consumption measurement with the power meter. -11. The power consumption should be smaller than the previous one measured in the step 3. -12. After defined-duration sleep expiry, the C-Plane processing and user traffic are enabled. The TER performs the DC or AC power consumption measurement with the power meter. -13. The power consumption should be greater than the previous one measured in the step 6 and step 10. - -#### D. Test Requirement (expected result) - -1. Test steps above are performed successfully. -2. The validation steps mentioned in step 7, step 11 and step 13 are within the expected power ranges as per the vendor product specifications. - -### 3.2.7.2.6 Advanced Sleep Mode (Emergency wake-up) - -#### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY - -The purpose of this test is to ensure O-RU is capable to do Emergency wake-up from advanced sleep mode. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings and emergency wake-up. - -This scenario corresponds to the following clause in [2]: - -- 7.2.9 Section Type 4: Slot Configuration Control -- 7.3.1 Section Types -- 7.4.6 Section Type 4 elements -- 7.5.2 Application layer, common -- 16 Energy-saving functionality - -following clause in [3]: - -- 20.4.2 Emergency wake-up procedure for ASM - -## B. Test Entrance Criteria - -- The O-RU shall support the default parameters of at least one of the scenarios given below, - -| Scenario | Default parameters | -|----------------------------------------|--------------------| -| FR1 FDD Conducted-Signal Tests | clause 3.2.1.1.1 | -| FR1 FDD Non-conducted OTA Signal Tests | clause 3.2.1.1.2 | -| FR1 TDD Conducted Signal Tests | clause 3.2.1.1.3 | -| FR1 TDD Non-conducted OTA Signal Tests | clause 3.2.1.1.4 | - -- The test numerology is 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1. If the O-RU does not support this numerology, any other numerology that the O-RU supports can be used. -- The O-RU shall have a conducted antenna port (or TAB connector) to be connected to a signal analyser, if the O-RU capabilities match scenario defined in clause 3.2.1.1.1 or clause 3.2.1.1.3. - -## C. Test Methodology - -### a. Initial Conditions - -- Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -- The O-RU exposes the capability to support energy savings including advanced sleep mode for defined-duration sleep, guaranteed wake-up duration, emergency wake-up. -- Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports or TAB connectors within acceptable tolerance. -- Connect the signal generator to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -- Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -- Build an appropriate IQ signal as described above in clause B. Test Entrance Criteria in the CUSM emulator. -- Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. The C-Plane processing and user traffic are enabled. -- The TER measures the AC or DC power consumption of the O-RU using power meter. -- The O-DU emulator enables energy savings by signalling section type 4 (st4CmdType = 4 for Advanced Sleep Mode) by setting “symbolMask” field to 0x3FFF, “sleepMode” field to indicate sleep mode, “numSlots” and “numSlotsExt” field for defined-duration sleep. - -NOTE: Defined-duration sleep needs to be greater than double the wake-up duration. It is recommended to set longer sleep duration, allowing for the power consumption measurements to be made. - -- The TER waits for a sufficient duration to ensure all of the O-RU's antenna array elements have reached sleep condition, for example a duration greater than the wake-up duration. This ensures C-Plane processing is halted and there is no possibility of user traffic. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU's antenna array elements have reached sleep condition. - -- The TER performs the DC or AC power consumption measurement with the power meter. -- The power consumption should be smaller than the previous one measured in the step 3. -- The TER NETCONF client sends a rpc. - -For Example, - -``` - - - - - - - - - - - - -``` - -9. The O-RU NETCONF Server responds with a message indicating successful completion of requested procedure. - -For Example, - -``` - - - - - -``` - -10. The TER NETCONF Client waits for emergency-wake-up-complete notification, to ensure wake up is complete, the C-Plane processing and user traffic are enabled. - -For Example, - -``` - - - YYYY-MM-DDTHH:MM:SS.FZ - - - -``` - -11. The TER performs the DC or AC power consumption measurement with the power meter. -12. The power consumption should be greater than the previous one measured in the step 6. - -#### D. Test Requirement (expected result) - -1. Test steps above are performed successfully. -2. All The validation steps mentioned in step 7 and step 12 are within the expected power ranges as per the vendor product specifications. - -### 3.2.7.3 Mixed Sleep Modes and Overlapping Commands - -#### 3.2.7.3.1 ASM Overlapping Commands - -##### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure O-RU is capable of ASM commands. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings. - -This scenario corresponds to the following clause in [2]: - -- 7.2.9 Section Type 4: Slot Configuration Control -- 7.3.1 Section Types -- 7.4.6 Section Type 4 elements -- 7.5.2 Application layer, common -- 16 Energy-saving functionality - -following clause in [3]: - -- 20.4 Advanced sleep modes for energy saving - -## B. Test Entrance Criteria - -- The O-RU shall support the default parameters of at least one of the scenarios given below, - -| Scenario | Default parameters | -|----------------------------------------|--------------------| -| FR1 FDD Conducted-Signal Tests | clause 3.2.1.1.1 | -| FR1 FDD Non-conducted OTA Signal Tests | clause 3.2.1.1.2 | -| FR1 TDD Conducted Signal Tests | clause 3.2.1.1.3 | -| FR1 TDD Non-conducted OTA Signal Tests | clause 3.2.1.1.4 | - -- The test numerology is 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1. If the O-RU does not support this numerology, any other numerology that the O-RU supports can be used. -- The O-RU shall have a conducted antenna port (or TAB connector) to be connected to a signal analyser, if the O-RU capabilities match scenario defined in clause 3.2.1.1.1 or clause 3.2.1.1.3. - -## C. Test Methodology - -### a. Initial Conditions - -1. Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -2. The O-RU exposes the capability to support energy savings including advanced sleep mode overlapping commands. -3. Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports (or TAB connectors) within acceptable tolerance. -4. Connect the signal generator to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -5. Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -1. Build an appropriate IQ signal as described above in clause B. Test Entrance Criteria in the CUSM emulator. -2. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. The C-Plane processing and user traffic are enabled. -3. The TER measures the AC or DC power consumption of the O-RU using power meter. -4. The O-DU emulator enables energy savings by signalling Section Type 4 (st4CmdType = 4 for Advanced Sleep Mode) by setting “sleepMode” field to indicate sleep mode, “symbolMask” field to 0x3FFF to indicate all symbols in a slot made or kept inactive, “numSlots” and “numSlotsExt” fields to 0 to indicate undefined-duration sleep. -5. The TER waits for a sufficient duration to ensure all of the O-RU’s antenna array elements have reached sleep condition, for example a duration greater than the wake-up duration. This ensures C-Plane processing is halted and there is no possibility of user traffic. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU's antenna array elements have reached sleep condition. - -6. The TER performs the DC or AC power consumption measurement with the power meter. -7. The power consumption should be smaller than the previous one measured in the step 3. -8. The O-DU emulator sends another ASM command by signalling Section Type 4 (st4CmdType = 4 for Advanced Sleep Mode) by setting "symbolMask" field to 0x3FFF to indicate all symbols in a slot made or kept inactive, "sleepMode" field to indicate sleep mode, "numSlots" and "numSlotsExt" field for defined-duration sleep. Figure 3.2.7.3.1-1 provides an example of overlapping ASM commands. - -NOTE: Defined-duration sleep needs to be greater than double the wake-up duration. It is recommended to set longer sleep duration, allowing for the power consumption measurements to be made. - -9. The TER waits for a sufficient duration to ensure all of the O-RU's antenna array elements have reached sleep condition, for example a duration greater than the "wake-up duration". This ensures C-Plane processing is halted and there is no possibility of user traffic. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU's antenna array elements have reached sleep condition. - -10. The TER performs the DC or AC power consumption measurement with the power meter. -11. The power consumption should be smaller than the previous one measured in the step 3. - -NOTE: This ensures that reception of the new ASM command does not wake up the O-RU but has replaced the previous ASM command sent in step 4. - -12. After defined-duration sleep expiry, the C-Plane processing and user traffic are enabled. The TER performs the DC or AC power consumption measurement with the power meter. -13. The power consumption should be greater than the previous one measured in the step 6 and step 10. - -![Diagram showing two boxes representing ASM commands. The first box is labeled 'ASM command (undefined duration)' and 'Step 4'. The second box is labeled 'ASM command (defined duration)' and 'Step 8'. A blue arrow points from the first box to the second box, indicating a transition or update of the command.](54ec84ddb200e1f5e8999dfd0820b17c_img.jpg) - -Diagram showing two boxes representing ASM commands. The first box is labeled 'ASM command (undefined duration)' and 'Step 4'. The second box is labeled 'ASM command (defined duration)' and 'Step 8'. A blue arrow points from the first box to the second box, indicating a transition or update of the command. - -Figure 3.2.7.3.1-66 Example of overlapping ASM commands - -**D. Test Requirement (expected result)** - -1. Test steps above are performed successfully. -2. The validation steps mentioned in step 7, step 11 and step 13 are within the expected power ranges as per the vendor product specifications. - -**3.2.7.3.2 C-Plane based TRX Control overlapping sleep mode** - -**A. Test Description and Applicability** - -This scenario is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure O-RU is capable of C-plane based TRX control sleep modes. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings. - -This scenario corresponds to the following clause in [2]: - -- 7.2.9 Section Type 4: Slot Configuration Control -- 7.3.1 Section Types -- 7.4.6 Section Type 4 elements -- 7.5.2 Application layer, common -- 16 Energy-saving functionality - -following clause in [3]: - -- 20.3.1 TRX control – C-Plane controlled - -## B. Test Entrance Criteria - -- The O-RU shall support the default parameters of at least one of the scenarios given below, - -| Scenario | Default parameters | -|----------------------------------------|--------------------| -| FR1 FDD Conducted-Signal Tests | clause 3.2.1.1.1 | -| FR1 FDD Non-conducted OTA Signal Tests | clause 3.2.1.1.2 | -| FR1 TDD Conducted Signal Tests | clause 3.2.1.1.3 | -| FR1 TDD Non-conducted OTA Signal Tests | clause 3.2.1.1.4 | - -- The test numerology is 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1. If the O-RU does not support this numerology, any other numerology that the O-RU supports can be used. -- The O-RU shall have a conducted antenna port (or TAB connector) to be connected to a signal analyser, if the O-RU capabilities match scenario defined in clause 3.2.1.1.1 or clause 3.2.1.1.3. - -## C. Test Methodology - -### a. Initial Conditions - -1. Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -2. The O-RU exposes the capability to support energy savings including C-Plane based TRX control overlapping sleep modes commands. -3. Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports or TAB connectors within acceptable tolerance. -4. Connect the signal generator to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -5. Let the DUT and TER to warm to the normal operating temperature within specified range. - -### b. Procedure - -1. Build an appropriate IQ signal as described above in clause B. Test Entrance Criteria in the CUSM emulator. -2. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. The C-Plane processing and user traffic are enabled. -3. The TER measures the AC or DC power consumption of the O-RU using power meter. -4. The O-DU emulator enables energy savings by signalling Section Type 4 (st4CmdType = 3 for TRX\_CONTROL) by setting “sleepMode” field to indicate sleep mode, “symbolMask” field to 0x3FFF to indicate all symbols in a slot made or kept inactive, “numSlots” and “numSlotsExt” fields to 0 to indicate undefined-duration sleep and “antMask” field to "0" for all array elements to place the whole antenna panel to sleep. -5. The TER waits for a sufficient duration to ensure all of the O-RU’s antenna array elements have reached sleep condition, for example a duration greater than the wake-up duration. This ensures C-Plane processing is halted and there is no possibility of user traffic. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU's antenna array elements have reached sleep condition. - -6. The TER performs the DC or AC power consumption measurement with the power meter. -7. The power consumption should be smaller than the previous one measured in the step 3. -8. The O-DU emulator issues a wake-up command to turn on portions of the O-RU's antenna array (for example, top half of the O-RU's antenna array) by signalling Section Type 4 (st4CmdType = 3 for TRX\_CONTROL) by setting "symbolMask" field to 0x0000 to indicate all symbols in a slot made or kept active, "sleepMode" field to indicate sleep mode, "numSlots" and "numSlotsExt" field to 0 to indicate undefined-duration sleep and "antMask" field to "1" in each array element for portions (for example, top half) of the O-RU's antenna array that is to be made or kept active. This ensures the C-Plane processing and user traffic are enabled for portions (for example, top half) of the O-RU's antenna array. - -NOTE: It is recommended to issue wake-up command after sufficient duration (for example greater than wake-up duration), allowing for the power consumption measurements to be made. - -9. The TER performs the DC or AC power consumption measurement with the power meter. -10. The power consumption should be greater than the previous one measured in the step 6. -11. The O-DU emulator issues a wake-up command to turn on remaining portions of the O-RU's antenna array (for example, bottom half of the O-RU's antenna array) by signalling Section Type 4 (st4CmdType = 3 for TRX\_CONTROL) by setting "symbolMask" field to 0x0000 to indicate all symbols in a slot made or kept active, "sleepMode" field to indicate sleep mode, "numSlots" and "numSlotsExt" field to 0 to indicate undefined-duration sleep and "antMask" field to "1" in each array element for remaining portions (for example, bottom half) of the O-RU's antenna array that is to be made or kept active. This ensures the C-Plane processing and user traffic are enabled for remaining portions (for example, bottom half) of the O-RU's antenna array. Figure 3.2.7.3.2-1 provides an example of overlapping C-Plane based TRX control commands. - -NOTE: It is recommended to issue wake-up command after sufficient duration (for example greater than wake-up duration), allowing for the power consumption measurements to be made. - -12. The TER performs the DC or AC power consumption measurement with the power meter. -13. The power consumption should be greater than the previous one measured in the step 6 and step 9. - -![Flowchart showing three steps of TRX Control commands: Step 4 (disable whole antenna array), Step 8 (enable top half), and Step 11 (enable bottom half).](1501d7bdc363cc07e88b48c8fa7d17c4_img.jpg) - -``` - -graph LR - A["TRX Control command (undefined duration) to disable whole of the antenna array elements -Step 4"] --> B["TRX Control command to enable top half of the antenna array elements -Step 8"] - B --> C["TRX Control command to enable bottom half of the antenna array elements -Step 11"] - -``` - -Flowchart showing three steps of TRX Control commands: Step 4 (disable whole antenna array), Step 8 (enable top half), and Step 11 (enable bottom half). - -Figure 3.2.7.3.2-67 Example of overlapping C-Plane based TRX control commands - -**D. Test Requirement (expected result)** - -1. Test steps above are performed successfully. -2. The validation steps mentioned in step 7, step 10 and step 13 are within the expected power ranges as per the vendor product specifications. - -### 3.2.7.3.3 ASM and C-Plane based TRX control overlapping commands - -#### A. Test Description and Applicability - -This scenario is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure O-RU is capable of ASM and C-Plane based TRX control commands. - -The test scenario is intentionally limited in scope to be applicable to any O-RU hardware design that supports Energy Savings. - -This scenario corresponds to the following clause in [2]: - -- 7.2.9 Section Type 4: Slot Configuration Control -- 7.3.1 Section Types -- 7.4.6 Section Type 4 elements -- 7.5.2 Application layer, common -- 16 Energy-saving functionality - -following clause in [3]: - -- 20.3.1 TRX Control – C-Plane controlled -- 20.4 Advanced sleep modes for energy saving - -#### B. Test Entrance Criteria - -- The O-RU shall support the default parameters of at least one of the scenarios given below, - -| Scenario | Default parameters | -|----------------------------------------|--------------------| -| FR1 FDD Conducted-Signal Tests | clause 3.2.1.1.1 | -| FR1 FDD Non-conducted OTA Signal Tests | clause 3.2.1.1.2 | -| FR1 TDD Conducted Signal Tests | clause 3.2.1.1.3 | -| FR1 TDD Non-conducted OTA Signal Tests | clause 3.2.1.1.4 | - -- The test numerology is 30 kHz subcarrier spacing and 100 MHz Bandwidth as described in clause ETSI TS 138.141 -1 NR-FR1-TM1.1. If the O-RU does not support this numerology, any other numerology that the O-RU supports can be used. -- The O-RU shall have a conducted antenna port (or TAB connector) to be connected to a signal analyser, if the O-RU capabilities match scenario defined in clause 3.2.1.1.1 or clause 3.2.1.1.3. - -#### C. Test Methodology - -##### a. Initial Conditions - -1. Configure the O-RU which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. -2. The O-RU exposes the capability to support energy savings including ASM and C-Plane based TRX control overlapping sleep modes commands. -3. Ensure that the RF connections and cables are calibrated so there is phase coherence between the antenna ports or TAB connectors within acceptable tolerance. -4. Connect the signal generator to the O-RU antenna ports or TAB connectors that belong to the scenario under test and configure the analyser with any set-up information needed to allow it to synch and demodulate the transmitted signal. -5. Let the DUT and TER to warm to the normal operating temperature within specified range. - -##### b. Procedure - -1. Build an appropriate IQ signal as described above in clause B. Test Entrance Criteria in the CUSM emulator. -2. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal and the scenario under test. The C-Plane processing and user traffic are enabled. -3. The TER measures the AC or DC power consumption of the O-RU using power meter. - -4. The O-DU emulator enables energy savings by signalling section type 4 (st4CmdType = 3 for TRX\_CONTROL) by setting “symbolMask” field to 0x3FFF, “sleepMode” field to indicate sleep mode, “numSlots”, “numSlotsExt” field for defined-duration sleep and “antMask” field with "0" in half of array element to make half of antenna panel to sleep. - -NOTE: Defined-duration sleep needs to be greater than double the wake-up duration. It is recommended to set longer sleep duration, allowing for the power consumption measurements to be made. It is recommended to set at least half of the array elements off (0 indicates off) in the antenna mask to better observe power changes. - -5. The TER waits for a sufficient duration to ensure some of the O-RU’s antenna arrays have reached sleep condition, for example a duration greater than the “wake-up duration”. This ensures C-Plane processing is halted and there is no possibility of user traffic. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU’s antenna array elements have reached sleep condition. - -6. The TER performs the DC or AC power consumption measurement with the power meter. -7. The power consumption should be smaller than the previous one measured in the step 3. -8. At the start of wake-up duration, the O-DU emulator sends sleep extension command by signalling section type 4 (st4CmdType = 3 for TRX\_CONTROL) by setting “symbolMask” field to 0x3FFF, “sleepMode” field to indicate sleep mode, “numSlots”, “numSlotsExt” fields to 0 for indicating undefined-duration sleep and “antMask” field with "0" in each array element that is to be made or kept inactive. - -NOTE: It is recommended to set at least half of the array elements off (0 indicates off) in the antenna mask to better observe power changes. - -9. The TER waits for a sufficient duration to ensure some of the O-RU’s antenna arrays have reached sleep condition, for example a duration greater than the “wake-up duration”. This ensures C-Plane processing is halted and there is no possibility of user traffic. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration. This assures the power measurement is done after all of the O-RU’s antenna array elements have reached sleep condition. - -10. The TER performs the DC or AC power consumption measurement with the power meter. -11. The power consumption should be smaller than the previous one measured in the step 3. -12. The O-DU emulator enables energy savings by signalling Section Type 4 (st4CmdType = 4 for Advanced Sleep Mode) by setting “symbolMask” field to 0x3FFF to indicate all symbols in a slot made or kept inactive, “sleepMode” field to indicate sleep mode, “numSlots” and “numSlotsExt” field for defined-duration sleep. - -NOTE: Defined-duration sleep needs to be greater than the double the wake-up duration. It is recommended to set longer sleep duration, allowing for the power consumption measurements to be made. - -13. The TER waits for a sufficient duration to ensure all of the O-RU’s antenna array elements have reached sleep condition, for example a duration greater than the “wake-up duration”. This ensures C-Plane processing is halted and there is no possibility of user traffic. - -NOTE: Since go-to-sleep duration is unknown and wake-up duration includes go-to-sleep duration, this assures the power measurement is done after all of the O-RU's antenna array elements have reached sleep condition. - -14. The TER performs the DC or AC power consumption measurement with the power meter. -15. The power consumption should be smaller than the previous one measured in the step 3, step 6 and step 10. -16. After defined-duration sleep expiry, the half of antenna array elements become active. i.e., the C-Plane processing and user traffic are enabled for half of antenna array elements. -17. The TER performs the DC or AC power consumption measurement with the power meter. -18. The power consumption should be smaller than the previous one measured in the step 3, and greater than the step 14. -19. The O-DU emulator disables energy savings by issuing a wake-up command by signalling Section Type 4 (st4CmdType = 3 for TRX\_CONTROL) by setting "sleepMode" field to indicate sleep mode, "symbolMask" field to 0x0000 to indicate all symbols in a slot made or kept active, "numSlots" and "numSlotsExt" fields to 0 to indicate undefined-duration sleep and "antMask" field to "1" in each array element that is to be made or kept active. Figure 3.2.7.3.3-1 provides an example of overlapping C-Plane based TRX control commands and ASM command. -20. The TER waits for the time interval of wake-up duration. This ensures the C-Plane processing and user traffic are enabled. -21. TER performs the DC or AC power consumption measurement with the power meter. -22. The power consumption should be greater than the previous one measured in the step 6, step 14 and step 17. - -![Figure 3.2.7.3.3-68: Example of overlapping C-Plane based TRX control commands and ASM command. The diagram shows a sequence of four steps: Step 4 (TRX Control command (defined duration) to disable half of the antenna array elements), Step 8 (TRX Control command (undefined duration) to disable half of the antenna array elements (same array elements as in Step 4)), Step 12 (ASM command (defined duration) to disable whole of the antenna array elements), and Step 19 (TRX Control command to enable half of the antenna array elements (same array elements as in Step 4)). Arrows indicate the flow from Step 4 to Step 8, Step 8 to Step 12, and Step 12 to Step 19.](6bff2cd340dd09b13b312514bbac613d_img.jpg) - -``` - -graph LR - S4[TRX Control command (defined duration) to disable half of the antenna array elements] --> S8[TRX Control command (undefined duration) to disable half of the antenna array elements (same array elements as in Step 4)] - S8 --> S12[ASM command (defined duration) to disable whole of the antenna array elements] - S12 --> S19[TRX Control command to enable half of the antenna array elements (same array elements as in Step 4)] - -``` - -Figure 3.2.7.3.3-68: Example of overlapping C-Plane based TRX control commands and ASM command. The diagram shows a sequence of four steps: Step 4 (TRX Control command (defined duration) to disable half of the antenna array elements), Step 8 (TRX Control command (undefined duration) to disable half of the antenna array elements (same array elements as in Step 4)), Step 12 (ASM command (defined duration) to disable whole of the antenna array elements), and Step 19 (TRX Control command to enable half of the antenna array elements (same array elements as in Step 4)). Arrows indicate the flow from Step 4 to Step 8, Step 8 to Step 12, and Step 12 to Step 19. - -Figure 3.2.7.3.3-68 Example of overlapping C-Plane based TRX control commands and ASM command - -#### D. Test Requirement (expected result) - -1. Test steps above are performed successfully. -2. The validation steps mentioned in step 7, step 11, step 15, step 18 and step 21 are within the expected power ranges as per the vendor product specifications. - -### 3.3 S-Plane Conformance Tests - -This clause describes tests that are used to validate S-Plane functional and performance conformance of network elements using the O-RAN WG4 fronthaul interface defined in [2] and the O-RAN WG4 M-Plane interface defined in [3]. This version of the conformance specification defines both O-DU and O-RU conformance tests. Future versions of - -this specification will describe additional S-Plane functional and performance conformance tests of other clocks used in the front haul, e.g. PRTC/T-GM, etc. - -S-Plane functionality of the O-RU is determined based on status retrieved from the O-RU using the M-Plane or SMO as appropriate, whereas S-Plane performance is determined by over-the-air (OTA) or conductive (i.e. a cabled electrical connection to the DUT's radio interface) measurements of O-RU synchronization signal. - -S-Plane functionality of the O-DU is determined based on status retrieved from the O-DU using the SMO. SMO methods to configure the O-DU and retrieve status from the O-DU can be any method supported by the O-DU including CLI, NM or WG5 specified protocols. - -The performance of O-DU is determined by time/frequency error measurements on output signals (such as 1PPS, or fronthaul SyncE+PTP master ports in LLS-C1 and LLS-C2). When applicable, O-DU tests are based on ITU-T G.8275.1 [5] profile. ITU-T G.8275.2 [6] is not specifically supported in this document version because this standard does not specify performance criteria and is left for further study. - -O-DU tests consider both local and remote PRTC connections, as shown in Figure 3.3.1-1. The connection type is relevant for performance tests because the input conditions applied to DUT depends on connection types supported: - -An embedded PRTC (e.g. using embedded GNSS receiver, Figure 3.3.1-1a) has no exposed direct O-DU interface, so test stimulus is applied to the Time Reference input (e.g. GNSS RF). - -A local PRTC is collocated with the O-DU and may communicate to O-DU via either a 1PPS and serial link (e.g. ITU-T G.8271 [31] or similar interface, Figure 3.3.1-1b), or an Ethernet interface (PTP and PLFS, Figure 3.3.1-1c). - -A remote PRTC is located anywhere in the network (backhaul or fronthaul) and communicates to O-DU via an Ethernet interface (PTP and PLFS, Figure 3.3.1-1d). - -![Figure 3.3.1-1: Methods to connect PRTC to O-DU. The diagram shows four scenarios: (a) Embedded PRTC with no exposed timing interface; (b) Local PRTC using 1PPS/10MHz/ToD interface; (c) Local PRTC using direct Ethernet connection; (d) Remote PRTC using networked Ethernet connection.](ea5e02b97cd1bd9fe04dcc6a125b9c2e_img.jpg) - -The diagram illustrates four methods to connect a PRTC to an O-DU (DUT): - -- (a) **Embedded PRTC**: A Time Reference (e.g. GNSS) is connected to a PRTC, which is then connected to the DUT (O-DU). A note indicates "No exposed timing interface" for this setup. -- (b) **Local PRTC using 1PPS/10MHz/ToD interface**: A Time Reference (e.g. GNSS) is connected to a PRTC, which is connected to the DUT (O-DU) via a G.703, G.8271 AnnexA, or Proprietary interface. -- (c) **Local PRTC using direct Ethernet connection**: A Time Reference (e.g. GNSS) is connected to a PRTC + T/GM, which is connected to the DUT (O-DU) via a Direct Ethernet with PTP/SyncE connection. -- (d) **Remote PRTC using networked Ethernet connection**: A Time Reference (e.g. GNSS) is connected to a PRTC + T/GM, which is connected to a Switched/Routed Network, which is then connected to the DUT (O-DU) via an Ethernet with PTP/SyncE connection. - -Figure 3.3.1-1: Methods to connect PRTC to O-DU. The diagram shows four scenarios: (a) Embedded PRTC with no exposed timing interface; (b) Local PRTC using 1PPS/10MHz/ToD interface; (c) Local PRTC using direct Ethernet connection; (d) Remote PRTC using networked Ethernet connection. - -Figure 3.3.1-1 Methods to connect PRTC to O-DU - -Both functional and performance tests require the provision of a test equipment i.e. provision of a test setup that includes a CUSM-E which delivers the necessary stimuli as described in clause 3.3.1. - -The S-Plane conformance test suite assumes that the vendor's equipment is conformant and has been tested to meet the requirements of ITU-T G.8275.1 [5] and IEEE1588v2 [32] and other relevant S-Plane standards. Therefore, this document does not attempt to duplicate tests for these standards. - -The below clauses of bullets summarize the test scope in order to validate conformance to the synchronization plane specification referenced by [2] clause 9. - -- General points which apply to testing of both functional and performance aspects of the O-DU and O-RU: - - The tests apply to both 4G (LTE/E-UTRA) and 5G (NR) and are applicable to all O-RAN IOT profiles listed in Annex A - - A CUSM-E is needed to generate the necessary M-plane and S-Plane traffic that includes PTP and possibly SyncE SSM over ESMC. It is synchronized to a time reference. For the O-RU testing a CUSM-E must also generate CU-Plane background traffic. - - Shall be done in the lab at constant temperature - - The CUS specification [2] may in the future support different kinds of Physical Layer Frequency Support (PLFS), however the only fully specified PLFS by the current edition of [2] is SyncE. Thus, these S-Plane tests are defined to include SyncE when required. - - Testing of SyncE is optional and is only valid when the SyncE device which can be driven by a master (e.g. O-RU) makes use of it. Therefore, the related SyncE test cases are optional. -- The following bulleted points apply specifically to functional tests of the O-RU in addition to the general points above, - - For validation of S-Plane, the following are used: - - A CUSM-E sends and receives synchronization information over the fronthaul interface. - - A Measurement Equipment to perform frequency/phase/time measurements from any available synchronization interface. - - DUT's S-Plane reports its state over M-Plane. - - The acceptance criterion for these tests is to comply with specification [2]. -- The following bullets points apply specifically to functional test of the O-DU in addition to the general points above: - - On its input ports, O-DU end application like O-RU may optionally use SyncE along with PTP. However, in the case of an LLS-C1/C2 O-DU acting as ITU-T G.8275.1 [5] SyncE+PTP master, SyncE emission is mandatory on the fronthaul for validation of S-plane: - - The acceptance criterion for these tests is to comply with specification [2]. - - The CUSM-E also provides local time source input signals to the O-DU: - - GNSS RF signals, delivered by a GNSS generator referenced to the local time reference - - PRTC output signals (1PPS + serial link) -- The following bulleted points apply specifically to performance tests for O-RU and O-DU in addition to the general points above. - - These tests are not defined to fully stress the DUT. Rather they are intended to stress the DUT enough to determine that it can properly operate via the defined front haul protocol. - - The thermal profile is not defined. The tests are defined to be run at a constant temperature, but the thermal profile choice and range is left as a decision for the vendor. - - The variable C/U-Plane profile (for example similar to test case 13 shown in figure VI.11 of ITU-T G.8261 [10]) will be defined as part of the work on the future performance tests. - - All performance tests described in this clause assume the following two components in the procedure (test methodology clauses): - - Establishing the necessary M-plane session to bring up the O-RU or if applicable the O-DU and make it ready for transmission of a measurement signal. - - For the O-RU in addition to the M-plane session, the transmission of a test signal necessitates the provision of a CU plane test vector. The test vector needs to have enough information to set up a synchronization channel within the radio frame transmitted over the air. - -- For O-DU performance tests the test cannot be executed unless the O-DU provides an Ethernet port with sync master function and/or a 1PPS output signal. -- The acceptance criterion for the performance tests is to satisfy the 3GPP OTA TAE limits specified in ETSI TS 136.141 [18] for 4G (LTE) and 38.141-2 [20] for 5G (NR), and summarized in eCPRI [11] and ITU-T G.8271 [31]. The conditions applicable to each test will be set out in the relevant clauses below (future work item). OTA TAE limits for MIMO/Tx Diversity are outside the scope of this document because they apply between endpoints belonging to the same O-RU. -- The CUS Specification [2] which follows eCPRI [11] and IEEE802.1 CM [33] recommendation, defines two examples of O-RU types, but these are not strict classes like the T-BC classes specified in ITU-T G.8273.2 [26]. - -### 3.3.1 Test Environment - -The following describes the necessary functions and capabilities of the test equipment in order to perform O-RU or O-DU conformance tests. A diagram of the O-RU test set up shown in Figure 3.3.1-2, and a similar diagram of the O-DU test set up is shown in Figure 3.3.1-3. - -Referring to Figure 3.3.1-2, the stimulus is applied to the O-RU via an Ethernet interface which simulates an O-RAN CUS-Plane protocols by using equipment to generate an O-DU and/or front haul time reference. This interface carries the PTP and SyncE stimulus to test the O-RU and carries M-Plane information to configure DUT and as needed C-Plane and U-Plane information to generate a test signal to measure time accuracy. Performance measurements are made at the radio output. These measurements can be made either over the air (called a non-conductive measurement), or via a cable connection from the radio interface (called conductive measurement). - -Figure 3.3.1-2 applies to LLS-C1/C2/C3 topologies. LLS-C4 topology is for further study. - -![Figure 3.3.1-2: O-RU LLS-C1/C2/C3 Conformance Test Set Up. The diagram shows a test setup for an O-RU. At the top, a 'RU Test Equipment, (R-TE)' is connected to a 'CUSM-Plane Emulator (CUSM-E)'. The CUSM-E contains a 'Time Reference', a 'PTP/SyncE Gen. (T-GM)', an 'Optional SMO', and an 'O-RAN Protocol'. The R-TE is connected to the CUSM-E via a 'Synchronization/Reference Clock' line. The CUSM-E is connected to the 'DUT (O-RU)' via a 'Direct Front Haul Ethernet Test Port'. The DUT (O-RU) contains a 'Clock/Time Reference' and an 'RF' block. The DUT (O-RU) is connected to the R-TE via a '1PPS out, 10MHz out, and/or PTP' line. The DUT (O-RU) is also connected to a 'Radio Interface', which is connected to a 'Signal Extractor'. The Signal Extractor is connected to a 'Performance Measurement' block. The Performance Measurement block is connected to the R-TE. The Signal Extractor is labeled 'extract 1PPS & extract freq.'. A dashed orange line labeled 'PTP/SyncE path' connects the CUSM-E to the DUT (O-RU). A dashed line labeled '1PPS out, Note 1' connects the DUT (O-RU) to the Performance Measurement block.](c886d02f002430c9405c8ecc5650450b_img.jpg) - -Figure 3.3.1-2: O-RU LLS-C1/C2/C3 Conformance Test Set Up. The diagram shows a test setup for an O-RU. At the top, a 'RU Test Equipment, (R-TE)' is connected to a 'CUSM-Plane Emulator (CUSM-E)'. The CUSM-E contains a 'Time Reference', a 'PTP/SyncE Gen. (T-GM)', an 'Optional SMO', and an 'O-RAN Protocol'. The R-TE is connected to the CUSM-E via a 'Synchronization/Reference Clock' line. The CUSM-E is connected to the 'DUT (O-RU)' via a 'Direct Front Haul Ethernet Test Port'. The DUT (O-RU) contains a 'Clock/Time Reference' and an 'RF' block. The DUT (O-RU) is connected to the R-TE via a '1PPS out, 10MHz out, and/or PTP' line. The DUT (O-RU) is also connected to a 'Radio Interface', which is connected to a 'Signal Extractor'. The Signal Extractor is connected to a 'Performance Measurement' block. The Performance Measurement block is connected to the R-TE. The Signal Extractor is labeled 'extract 1PPS & extract freq.'. A dashed orange line labeled 'PTP/SyncE path' connects the CUSM-E to the DUT (O-RU). A dashed line labeled '1PPS out, Note 1' connects the DUT (O-RU) to the Performance Measurement block. - -**Figure 3.3.1-2 O-RU LLS-C1/C2/C3 Conformance Test Set Up** - -NOTE 1: The optional 1 Pulse Per Second (PPS) out signal shown in figure 3.3.1-2 is used only for diagnostic purposes. The 1 PPS signal is not used for a measurement in this conformance test. - -As shown in Figure 3.3.1-3, the O-DU the setup is similar to the O-RU. In addition to the option to supply timing using PTP via Ethernet (like the O-RU), the input stimulus may be applied to the DUT from a directly connected Time Reference which delivers frequency (e.g. SyncE, 10MHz, 1PPS), phase (e.g. 1PPS, 10ms frame boundary) and time (e.g. ToD, PTP) signals. Directly connecting the Time Reference time via a Local Sync Port simulates topology with an O-DU using a Local PRTC Time Reference. Using PTP via an Ethernet Test Port simulates a topology using a Remote PRTC. - -For the O-DU LLS C1/C2 performance tests, the quality of the DUT timing output is measured via the DUT Fronthaul Ethernet Port, which propagates the time and optionally frequency information from the DUT using PTP and optionally SyncE. - -For the O-DU LLS-C3/C4 performance tests the quality of the DUTs timing is measured via a spare Master PTP/SyncE Ethernet Port (if available) or the 1 PPS output (if available). If no spare Master PTP/SyncE Ethernet Port or 1 PPS output port is available, then performance test cannot be executed for LLS-C3/C4 configuration for the O-DU. - -Typically, in LLS-C3/C4, using a 1PPS measurement interface may avoid having to configure an Ethernet port as PTP master for measurement purpose. - -![Figure 3.3.1-3: O-DU LLS-C1/C2/C3/C4 Conformance Test Set Up. The diagram shows a 'DU Test Equipment, (D-TE)' connected to a 'CUSM-Plane Emulator (CUSM-E)*'. The emulator contains an 'Optional NMS/SMO or WG5 M-Plane Interface' and a 'Time Reference' block with 'GNSS Emulator', 'PRTC Emulator', and 'PTP/SyncE Generator (T-GM)'. The 'Time Reference' is connected to the 'DUT (O-DU)' via four labeled paths: (a) GNSS RF Signal, (b) Local Sync Port, (c) Ethernet Test Port, and (d) Management Interface. The 'DUT (O-DU)' has a 'Clock / Time Reference' block and two output ports: '1PPS out (optional)' and 'Ethernet Measurement Port'. Both output ports are connected to a 'Sync Tester (PTP/SyncE and/or 1pps Time Measurement)' which 'extracts 1PPS & extract freq.'. A 'Reference Clock/Synchronization' line with '1pps out, 10MHz out, and/or PTP' is also connected to the 'Sync Tester'.](ec7562b686a99409572119f7aaf7a626_img.jpg) - -Figure 3.3.1-3: O-DU LLS-C1/C2/C3/C4 Conformance Test Set Up. The diagram shows a 'DU Test Equipment, (D-TE)' connected to a 'CUSM-Plane Emulator (CUSM-E)\*'. The emulator contains an 'Optional NMS/SMO or WG5 M-Plane Interface' and a 'Time Reference' block with 'GNSS Emulator', 'PRTC Emulator', and 'PTP/SyncE Generator (T-GM)'. The 'Time Reference' is connected to the 'DUT (O-DU)' via four labeled paths: (a) GNSS RF Signal, (b) Local Sync Port, (c) Ethernet Test Port, and (d) Management Interface. The 'DUT (O-DU)' has a 'Clock / Time Reference' block and two output ports: '1PPS out (optional)' and 'Ethernet Measurement Port'. Both output ports are connected to a 'Sync Tester (PTP/SyncE and/or 1pps Time Measurement)' which 'extracts 1PPS & extract freq.'. A 'Reference Clock/Synchronization' line with '1pps out, 10MHz out, and/or PTP' is also connected to the 'Sync Tester'. - -\* For O-DU S-Plane testing the CUSM emulator need not implement WG4 C-Plane or U-Plane Protocols. - -- ⓐ Embedded PRTC GNSS radio interface. -- ⓑ Local PRTC using Local Sync Port (for example ITU-T G.8271 Annex A) -- ⓒ Local PRTC using PTP and PLFS -- ⓓ Remote PRTC using PTP and PLFS - -Figure 3.3.1-3 O-DU LLS-C1/C2/C3/C4 Conformance Test Set Up with an a) Embedded PRTC, b) Local Sync Port PRTC, c) PRTC over PTP/SyncE - -**CUSM-Plane Emulator:** This function implements various planes (C, U, S, M) to simulate a front haul/transport network connecting to DUT (i.e. O-RU, O-DU). It should be capable of testing S-Plane performance under stress with various noise profiles. S-Plane signals sent to DUT and measurement equipment are traceable to reference signals received from the master time reference. Emulator should generate noise free reference signal for Measurement Equipment and (when required) a noise profile for the DUT. The CUSM-Plane emulator may be composed of multiple components or could be a single component containing all the capabilities listed below. When O-RU is the DUT UC-Plane is needed for O-RU to generate a radio information required to measure timing. For O-DU, CU-Plane functionality is not used since timing is measured directly from an Ethernet or 1PPS test port. - -**Time Reference/S-Plane:** This equipment is the frequency and time reference. It delivers frequency (e.g. SyncE, 10MHz, 1PPS), phase (e.g. 1PPS, 10ms frame boundary) and time (e.g. ToD, PTP) signals to the Sync Tester equipment and to the various simulators/generators listed below. PRTC specified by ITU-T G.8272 [35] is one example in terms of performance. The level of performance for these reference signals should be significantly (by an order of magnitude) - -better than the 3GPP synchronization requirements when absolute limits are measured against the reference clock. The time reference function with the CUSM-Plane emulator is traceable to UTC. The time output is used to synchronize the signal analyser or Test Equipment performing time error measurements. The phase output is used to synchronize the signal analyser or Test Equipment performing time error measurements. - -**PRTC/T-GM:** for testing an O-DU from either local or remote PRTC over Ethernet. It includes a PTP master clock and, when applicable, a SyncE master function that propagate the Time reference and allow adding configured noise patterns. - -**GNSS Emulator:** for testing an O-DU with integrated local PRTC. The GNSS emulator will provide an RF signal to the O-DU. The RF signal emulates a signal received by a GNSS antenna and allows adding configured noise patterns. As an alternative to a GNSS emulator following case is acceptable: the test environment provides the capability to access a GNSS antenna mounted at a suitable location inside the building with line of sight to sufficient number of GNSS satellites (>4). - -**PRTC Emulator:** for testing an O-DU with integrated T-GM, but without an integrated local PRTC: in this case, the test setup needs to provide the following signals to the O-DU: 1PPS (according to ITU-T G.703 [34]), 10MHz, and serial link carrying ToD and PRTC status. There are different ToD formats such as ITU-T G.8271 [31] Annex A and NMEA. The ToD format of the test setup needs to deliver the ToD format supported by the O-DU. This interface allows adding configured noise patterns. - -**SMO:** Responsible for configuring CUSM Plane emulator to send configuration to DUT for the defined conformance tests. - -**M-Plane:** Translate the SMO configuration into the proper M-Plane messages to correctly configure and report status from the DUT. For O-RU testing this is implemented using WG4 M-Plane protocol. For O-DU this is implemented by either using a Network Management System (SMO) which is compatible with the DUT or using a WG5 M-Plane emulator. - -**UC-Plane:** S-Plane tests require the transmission of UC-Plane traffic over the fronthaul, the emulator shall implement the O-RAN UC-Plane protocol and shall send a stock data frame defined in clause 3.2.1.1.5 and shown in Figure 3.2.1.1-4 as UC-Plane messages to DUT O-RU. - -The emulator shall merge all traffic types for transmission over the fronthaul without degrading performance of S-Plane. - -### 3.3.1-1 O-DU LLS-C1/C2/C3 Input Source and Output Source Options . - -| O-DU Input Time Source | Topology and Master Output Time | | | | -|-----------------------------------------------------------------|---------------------------------|------------------|------------|------------| -| | LLS-C1 | LLS-C2 | LLS-C3 | LLS-C4 | -| PTP+SyncE Master from Mid Haul (either Local or Remote PRTC) | Yes – Front Haul | Yes – Front Haul | Yes - None | Yes - None | -| PTP+SyncE Master from Front Haul (Remote PRTC) | NA | NA | Yes - None | Yes - None | -| Local time source, either GNSS RF signals or 1PPS+TOD from PRTC | Yes – Front Haul | Yes – Front Haul | Yes - None | Yes - None | - -**Measurement Equipment:** This equipment is responsible for extracting the desired synchronization information from the test signal transmitted by the DUT, and then measuring this information to determine if the performance is within limits. This could be a single piece of test equipment containing all the capabilities listed below, or it may be created by interconnecting a separate signal analyser and performance measurement system. - -For O-RU testing the following measurement equipment is needed. - -**Signal Extractor:** This equipment demodulates the time reference signal from the O-RU's downlink radio interface. It receives RF signals from the DUT over air or via coaxial interface. - -**Performance Measurement Equipment:** This equipment performs error measurements of the timing and frequency output signals from the Signal Extractor. It uses standard metrics to validate if the measured signal meets the defined limits. - -For O-DU testing the following measurement equipment is used. - -**PTP/SyncE/1pps Measurement Equipment:** This equipment is responsible for extracting the desired synchronization information from the Master PTP/SyncE Ethernet port (e.g. decoding the PTP and/or SyncE sent from DUT master port) or 1PPS output from the DUT (LLS-C3/C4 only), then measuring this information to determine if the performance of the DUT is within limits. - -### 3.3.2 Functional test of O-RU using ITU-T G.8275.1 profile (LLS-C1/C2/C3) - -#### A. Test Description and Applicability - -This test is MANDATORY. - -The purpose of this test is to validate that an O-RU is correctly synchronizing to a CUSM Emulator delivering both PTP and (optionally) SyncE using ITU-T G.8275.1 [5] profile and that the O-RU correctly reports its status to the CUSM Emulator based on the nominal or degraded synchronization conditions generated by CUSM Emulator. - -In Table 3.3.2-1, Table 3.3.2-2 and Table 3.3.2-3, steps 4, 5, and 10 are OPTIONAL. For an O-RU implementation that supports HOLDOVER, depending on the O-RU clock characteristics or assistance of SyncE, the O-RU might remain in the HOLDOVER state for long periods before transitioning to FREERUN. For such O-RUs, waiting for the transition from HOLDOVER to FREERUN can be impractical. Steps 4, 5, and 10 wait for this transition, and treating the steps as optional provides the opportunity to avoid impractical wait times for these tests. - -#### B. Test Entrance Criteria - -O-RU is connected to CUSM Emulator directly. - -O-RU must be operating with the respective SMO or M-Plane properly (as defined in clause 3.2.1.1.5). - -#### C. Test Methodology - -##### a) Initial Conditions - -This test uses the O-RU (DUT), a CUSM-Plane emulator with SMO features to generate stimulus for the O-RU (DUT) and signal analyser to measure the radio interface timing. - -##### b) Procedure - -Three conditions must be tested: - -**Startup:** CUSM-Plane Emulator is configured to act as a clock, with PTP and SyncE ports in passive state (no messages sent) - -**Nominal:** CUSM-E is configured to start acting as a PTP master compliant with the ITU-T G.8275.1 [5] profile advertising LOCKED status with nominal clockClass and clockAccuracy. If SyncE is to be tested CUSM-Plane Emulator is configured to act as a clock, with SyncE ports in master state, compliant to ITU-T G.8264 [36] profile advertising nominal SSM value as specified by ITU-T G.8275.1 [5]. - -**Degraded:** There are two levels of degraded conditions for both PTP and SyncE that can be configured to the CUSM-Emulator. - -The first degradation level is where the CUSM-E is configured to act as a clock, with PTP and SyncE ports in master state, compliant to ITU-T G.8275.1 [5] profile, and sending configured clockClass and/or SSM values within the O-RU’s configured accepted limits via the M-plane. - -The second degradation level is where the same clockClass and/or SSM values are sent by CUSM-E outside the O-RU’s configured accepted limits via the M-plane. - -To cover the all the relevant scenarios the test sequence listed in Table 3.3.2-1 steps through the Startup/Nominal/Degraded states in a sequence. The steps in this table and Table 3.3.2-2 are intended to be exercised in sequential order. Since SyncE is optional, there are two columns, one for PTP status and a second for SyncE. Each of the status items corresponds the conditions defined above. - -**Table 3.3.2-1 O-RU LLS-C1/C2/C3 Functional Conformance Test Steps.** - -| Step | PTP Status: | SyncE Status (if applicable): SSM | -|------|--------------------------------------------------------------------------------|--------------------------------------------------------------| -| 1. | Startup: no clockclass | Startup: no SSM/QL | -| 2. | Nominal clockclass=6 | Nominal QL= (see Note 1) | -| 3. | Degraded clockclass but within the O-RU’s configured accepted range. | Nominal QL= (see Note 1) | -| 4. | Degraded clockclass outside the O-RU’s configured accepted range. (see NOTE 2) | Nominal QL= (see Note 1) | -| 5. | Degraded clockclass outside the O-RU’s configured accepted range. (see NOTE 2) | Degraded QL outside the O-RU’s configured accepted range. | -| 6. | Nominal clockclass=6 | Nominal QL= (see Note 1) | -| 7. | Nominal clockclass=6 | Degraded QL but within the O-RU’s configured accepted range. | -| 8. | Nominal clockclass=6 | Degraded QL outside the O-RU’s configured accepted range. | -| 9. | Nominal clockclass=6 | Nominal QL = (see Note1) | -| 10. | S-Plane lost, no message (see NOTE 2) | S-Plane lost, no message | - -NOTE 1: For SyncE, Nominal QL is what is determined as the best acceptable configured value by the O-RU -NOTE 2: Steps 4, 5, and 10 are optional (see 3.3.2.A). - -**D. Pass Fail Criteria (expected results)** - -The acceptance criterion is that the status reported by the O-RU for the steps defined in above procedure matches the results described in Table 3.3.2-2 for PTP only and Table 3.3.2-3 for PTP and SyncE. The left column indicates the steps defined in Table 3.3.2-1. The second column summarizes the O-RU status from Table 3.3.2-1. The right two columns list the M-plane ptp status parameters that are queried from the test O-RU and their desired value. For PTP clockClass and optional SyncE SSM quality level, the “Received Value” is the one received by the O-RU (except in Startup mode when there is no such received value and the default one is reported). In Table 3.3.2-2 and Table 3.3.2-3, the table’s “ptp clock-class” is obtained from the O-RU by reading the YANG list “sources” (in “sync/ptp-status”), finding the first port with a YANG “state” that matches the corresponding “ptp state” in the table, and returning the YANG “clock-class” of that found port. If no port is found, or if the YANG “state” of the found port is DISABLED, return 255. The clockClass value 255 is not a valid value that can be received from the CUSM-E. - -The O-RU Sync-state, PTP lock state, PTP state, PTP clock-class, SyncE lock-state, SyncE state, SyncE quality-level are defined in the M-Plane specification [3] (chapter 13 Synchronization Aspects) and relevant YANG models. - -**Table 3.3.2-2 O-RU LLS-C1/C2/C3 Functional Conformance Test Results without SyncE.** - -| Step | O-RU PTP Status | sync -state | ptp lock-state | ptp state | ptp clock-class | -|---------|------------------------------------------|-----------------------------------|----------------|-----------|-----------------| -| 1. | Startup | FREE-RUN | UNLOCKED | DISABLED | 255 | -| 2. | Nominal | LOCKED | LOCKED | PARENT | Recvd Value | -| 3. | Degraded, within range | LOCKED | LOCKED | PARENT | Recvd Value | -| 4. – 5. | Degraded, outside range.
(see NOTE 3) | HOLDOVER (Note 1)
then FREERUN | (Note 2) | NOK | Recvd Value | -| 6. – 9. | Nominal | LOCKED | LOCKED | PARENT | Recvd Value | -| 10. | None (disconnected)
(see NOTE 3) | HOLDOVER (Note 1)
then FREERUN | UNLOCKED | DISABLED | 255 | - -NOTE 1: If HOLDOVER is not implemented by O-RU, then O-RU goes directly to FREERUN. - -NOTE 2: According to IEEE1588 [32] an O-RU embedded PTP clock is specified to be LOCKED. However, according to M-Plane specification [3] it could be in either LOCKED or UNLOCKED states. - -NOTE 3: Steps 4, 5, and 10 are optional (see 3.3.2.A). - -**3.3.2-3 O-RU LLS-C1/C2/C3 Functional Conformance Test Results with SyncE.** - -| Step | O-RU PTP and SyncE Status | sync-state | ptp lock-state | ptp state | ptp clock-class | syncE lock-state | syncE state | syncE quality-level | -|------|-------------------------------------------------------------------------------|-----------------------------------------|----------------|-----------|-----------------|------------------|------------------------------|---------------------| -| 1. | Startup | FREE-RUN | UNLOCKED | DISABLED | 255 | UN-LOCKED | DIS-ABLED | Note 1 | -| 2. | PTP: Nominal
SyncE: Nominal | LOCKED | LOCKED | PARENT | Rcvd Value | LOCKED | PARENT or OK | Rcvd Value | -| 3. | PTP: Degraded, within range
SyncE: Nominal | LOCKED | LOCKED | PARENT | Rcvd Value | LOCKED | PARENT or OK | Rcvd Value | -| 4. | PTP: Degraded, outside range.
SyncE: Nominal (see NOTE 5) | HOLDOVER (Note 2) then FREERUN (Note 3) | (Note 4) | NOK | Rcvd Value | LOCKED | PARENT (see NOTE 3 and 5) | Rcvd Value | -| 5. | PTP: Degraded, outside range.
SyncE: Degraded, outside range. (see NOTE 5) | HOLDOVER (Note 2) then FREERUN (Note 3) | (Note 4) | NOK | Rcvd Value | Note 1 | NOK (see NOTE 3 and 5) | Note 1 | -| 6. | PTP: Nominal
SyncE: Nominal | LOCKED | LOCKED | PARENT | Rcvd Value | LOCKED | PARENT or OK | Rcvd Value | -| 7. | PTP: Nominal
SyncE: Degraded, within range. | LOCKED | LOCKED | PARENT | Rcvd Value | LOCKED | PARENT or OK | Rcvd Value | -| 8. | PTP: Nominal
SyncE: Degraded, outside range. | Implementation Specific (Note 3) | LOCKED | PARENT | Rcvd Value | Note 1 | NOK | Note 1 | -| 9. | PTP: Nominal
SyncE: Nominal | LOCKED | LOCKED | PARENT | Rcvd Value | LOCKED | PARENT or OK | Rcvd Value | -| 10. | PTP: None (disconnected)
SyncE: None (disconnected) (see NOTE 5) | HOLDOVER (Note 2) then FREERUN (Note 3) | UNLOCKED | DISABLED | 255 | UN-LOCKED | DIS-ABLED (see NOTE 3 and 5) | Note 1 | - -NOTE 1: This is not specified by CUS-Plane and is implementation dependent. - -NOTE 2: If HOLDOVER (either assisted by SyncE or relying on local oscillator) is not implemented by O-RU, then O-RU goes directly to FREERUN. - -NOTE 3: Depending on O-RU implementation the Sync-state may be LOCKED or HOLDOVER then FREERUN. - -NOTE 4: According to IEEE1588 [32] an O-RU embedded PTP clock is specified to be LOCKED. However, according to M-Plane specification [3] it could be in either LOCKED or UNLOCKED states. - -NOTE 5: Steps 4, 5, and 10 are optional (see 3.3.2.A). - -**3.3.3 Performance test of O-RU using ITU-T G.8275.1 Profile (LLS-C1/C2/C3)** - -**A. Test Description and Applicability** - -This test is MANDATORY. - -This test validates that an O-RU is synchronizing from a CUSM-plane Emulator delivering configured (ideal and normal operating conditions) PTP and (optionally) SyncE. Frequency and time error generated by the O-RU shall be within specified limits. - -Note, when O-RUs implement cascaded O-RU mode see also clause 3.3.9. - -CUS -plane spec lists two classes of O-DU (class A has $\pm 15$ ppb frequency error limit; class B has $\pm 5$ ppb limit). This test applies to the strictest one from O-RU perspective and therefore considers Class An O-DU for LLS-C1, and the worst-case maximum of O-DU class A and B for LLS-C2. The class of O-DU is not a factor in the O-RU input limit for LLS-C3 (see CUS-Plane Specification [2] clause 11.3.2.2), therefore it is not considered. - -## B. Test Entrance Criteria - -O-RU is connected to CUSM-Plane Emulator via direct fibre link(s). - -Conformance Functional test in clause 3.3.2 is successfully passed. - -It is the vendor's responsibility to make sure that limits defined in the test are also met in worse-case field conditions. Thermal testing, PTP PDV tolerance and SyncE jitter/wander tolerance are beyond the scope of this test. - -O-RU shall be operating with the respective SMO or M-Plane properly. (as defined in 3.2.1.1.5) - -## C. Test Methodology - -### a) Initial Conditions - -These tests use the O-RU DUT and a CUSM-Plane emulator with SMO features. - -Frequency and time error are measured on the Air interface at the O-RU output. This is accomplished by utilizing the CUSM-Plane emulator to generate the basic downlink signal according to the “UC-Plane O-RU Scenario Class Base 3GPP DL” applicable to the O-RU under test, i.e. 3.2.3.1.1, 3.2.4.1, 3.2.5.1.1, or 3.2.6.1.1; and the signal analyser performing the appropriate frequency and time error measurements. - -CUSM-Plane Emulator is configured to act as a clock, with PTP ports in master state, compliant to ITU-T G.8275.1 [5] profile advertising LOCKED status with nominal clockClass and clockAccuracy. - -CUSM-Plane Emulator is configured to act as a clock, with SyncE ports in master state, compliant to ITU-T G.8264 [36] profile advertising nominal SSM value. - -The DUT shall have achieved frequency and phase lock prior to starting the test. - -### b) Procedure: - -Unlike the functional test defined in clause 3.3.2, where start-up / nominal / degraded scenarios are tested, only nominal scenarios with ideal and normal operation input noise are tested in this clause. - -- 1) **Ideal:** PTP and SyncE (if used) provide “ideal” O-RU input synchronization with no added noise. -- 2) **Normal Operation:** PTP and SyncE (if used) provide “Within normal operating limits” O-RU inputs as specified in CUS-Plane Specification [2]. - -The CUS requirements and subsequent PTP test patterns specify absolute value for constant time error ( $cTE$ ). Dynamic time error ( $dTE$ ) implicitly varies positive/negative, but $cTE$ does not. It is possible that an O-RU can pass the test with positive $cTE$ , and fail with negative $cTE$ (or vice versa). Therefore, regardless of which method is used for the PTP test pattern, this test shall be performed twice: once with - -the CUSM-Plane Emulator generating positive cTE in the PTP test pattern, and again with the CUSM-Plane Emulator generating negative cTE in the PTP test pattern. The pass/fail criteria are the same for both tests. - -**a) For LLS-C1 PTP is required to simultaneously meet two limits:** - -- a. $\max|TE_L|$ : 1420 ns, -- b. Maximum frequency error (0.1Hz low pass filtered): $\pm 15$ ppb - -**b) For LLS-C2 PTP is required to simultaneously meet two limits:** - -- a. $\max|TE_L|$ : 1420 ns -- b. Maximum frequency error as result of the input noise as per CUS-Plane Specification [2] Table 11.3.2.1-1 expressed as MTIE in Table H.2.4-3, Table H.2.4-4 and Figure H.2.4-4 (MTIE limit at the input to an O-RU, maximum of O-DU class A and B limits, as worst case) - -**c) For LLS-C3 PTP is required to simultaneously meet two limits:** - -- a. $\max|TE_L|$ : $\pm 1100$ ns, according to $\max|TE_L| = 600$ ns specified in ITU-T G.8271.1 [7] clause 7.3.2 (see NOTE 4 in CUS-Plane Specification [2] Table 11.3.2.2-1), increased by 500 ns (also 0.1Hz low-pass filtered) to account for the short holdover period -- b. Frequency error budget allocation according to CUS-Plane Specification [2] Table 11.3.2.2-1, noise input to the O-RU is 126 ns dTE plus 2 ppb. This can be expressed in terms of unfiltered MTIE as shown in Table H.2.5-4 and Figure H.2.5-4 of the CUS-Plane Specification [2]. - -NOTE: Longer holdover periods resulting in a larger MTIE limit for larger observation intervals, might be considered in networks where the time error in normal operation (e.g. due to cTE) is smaller than assumed by ITU-T G.8271.1 [7]. - -**d) For SyncE the following applies:** - -- a. For LLS-C2 and LLS-C3, the noise at the input of the O-RU in Normal Operation is as per ITU-T G.8262 [29] clause 9.1. -- b. If the O-RU implementation supports ITU-T G.8262.1 [30] Level 1 only, the noise at the input of the O-RU would be as per ITU-T G.8262.1 [30] clause 9.1. This is acceptable for cases where the O-RU is expected to be deployed in enhanced synchronous Ethernet networks only. -- c. For the case of LLS-C1 configuration, the synchronous Ethernet wander can be based on the O-DU output, i.e. signal with 15ppb frequency error (that is the worst case as related to class A O-DU). - -NOTE 1: The CUSM-Plane Emulator may be configured to generate the time and frequency error of PTP and SyncE, either simultaneously or sequence. Presenting noise at SyncE and PTP inputs simultaneously represents a more realistic option to verify expected performance in a real network, so this set up is recommended. In this case, the additional noise on SyncE stimulus is expected to not increase the PTP stimulus noise above the specified time error limits. - -NOTE 2: CU and M plane messages do not need to be modified. It has no impact if they are delayed by the time and frequency error applied in this test. - -Two methods are proposed to define the PTP test patterns - -1. In the first method, the time error added to the input signal shall follow a sinusoidal waveform with amplitude (A) and frequency (f). Three such signal frequencies are specified for the test, but intermediate ones can be used for testing. - -For LLS-C1 they need to maintain the following relationship between amplitude and frequency: $A[\text{ns}] = 15[\text{ppb}]/(2*\pi*f[\text{Hz}])$ and simultaneously meet the 2a conditions above. An additional constant time error may be added to the sinusoidal waveform for each frequency, so that the $\max|TE_t|$ reaches the maximum value of 1420 ns: $cTE_{[\text{ns}]} = 1420_{[\text{ns}]} - A_{[\text{ns}]}.$ - -For LLS-C2 they need to meet the conditions in 2b above for MTIE. An additional constant time error may be added to the sinusoidal waveform for each frequency, so that the $\max|TE_t|$ reaches the maximum value of 1420ns: $cTE_{[\text{ns}]} = 1420_{[\text{ns}]} - A_{[\text{ns}]}.$ - -For LLS-C3 they need to generate the worst-case conditions in 2c above for MTIE. An additional constant time error may be added to the sinusoidal waveform for each frequency, so that the maximum time error reaches the maximum value of 1100ns: $cTE_{[\text{ns}]} = 1100_{[\text{ns}]} - A_{[\text{ns}]}.$ - -Testing any higher frequency input noise than the ITU cut-off frequency (0.1Hz) would require considering filtered and unfiltered limits. It is therefore outside the scope of this document and such performance must be validated by vendors and documented in test reports. - -The following Table 3.3.3-1 and Figure 3.3.3-1 show the three sinusoidal time error waveforms to be used for testing each configuration: - -**Table 3.3.3-1 Sine wave amplitude and Time Error Limits for Test Signal.** - -| Frequency | LLS-C1 | LLS-C2 | LLS-C3 | Test | -|-----------|--------|--------|--------|------| -|-----------|--------|--------|--------|------| - -| [Hz] | Sine wave amplitude [ns] | Constant Time Error [ns] | Sine wave amplitude [ns] | Constant Time Error [ns] | Sine wave amplitude [ns] | Constant Time Error [ns] | duration [s] | -|----------|--------------------------|--------------------------|--------------------------|--------------------------|--------------------------|--------------------------|-----------------| -| 0.003362 | 710 | 710 | 833 | 587 | 187 | 913 | 595 (2 periods) | -| 0.010 | 239 | 1181 | 328 | 1092 | 108 | 992 | 500 (5 periods) | -| 0.100 | 24 | 1396 | 78 | 1342 | 68 | 1032 | 50 (5 periods) | - -NOTE: The sine wave amplitudes are zero to peak values. Dynamic time error values (dTE) are peak-to-peak values and equal two times the given sine wave amplitude. - -![Graph titled 'O-RU input sine wave amplitude vs. frequency'. The x-axis is Frequency [Hz] on a logarithmic scale from 0.001 to 0.1. The y-axis is Sine wave amplitude [ns] on a logarithmic scale from 10 to 1000. Three data series are plotted: LLS-C1 (blue circles), LLS-C2 (green circles), and LLS-C3 (orange circles). Data points are labeled with their values: at 0.003362 Hz, LLS-C1 is 833, LLS-C2 is 710, LLS-C3 is 187; at 0.01 Hz, LLS-C1 is 328, LLS-C2 is 239, LLS-C3 is 108; at 0.1 Hz, LLS-C1 is 78, LLS-C2 is 68, LLS-C3 is 24.](799f76c21809a255ae48acbf76a074da_img.jpg) - -Graph titled 'O-RU input sine wave amplitude vs. frequency'. The x-axis is Frequency [Hz] on a logarithmic scale from 0.001 to 0.1. The y-axis is Sine wave amplitude [ns] on a logarithmic scale from 10 to 1000. Three data series are plotted: LLS-C1 (blue circles), LLS-C2 (green circles), and LLS-C3 (orange circles). Data points are labeled with their values: at 0.003362 Hz, LLS-C1 is 833, LLS-C2 is 710, LLS-C3 is 187; at 0.01 Hz, LLS-C1 is 328, LLS-C2 is 239, LLS-C3 is 108; at 0.1 Hz, LLS-C1 is 78, LLS-C2 is 68, LLS-C3 is 24. - -Figure 3.3.3-1 Graph of sine wave amplitude limits for Test Signal - -The transition between the sinusoidal waveforms shall not cause the input noise to exceed the limits defined for the test case. - -- An alternative and more representative method for the O-RU input is to apply a noise pattern that meets the applicable O-DU output or network limit mask. - -For LLS-C1 the noise pattern must meet the conditions in 2a above. This can be expressed in terms of unfiltered MTIE as shown in Table H.2.4.1 and Figure H.2.4-2 ( O-DU Output Class A LLS-C1 (unfiltered) from CUS-Plane specification [2] - -For LLS-C2 the noise pattern must meet the conditions in 2b above. - -For LLS-C3 the noise pattern must meet the conditions in 2c above. - -The method to generate the noise patterns is described in ITU-T G.8273.2 [26]Appendix IX. The advantage of this method is that it is more representative of real network conditions and transients, and therefore a more effective test of the O-RU under emulated network conditions. The pattern can be constructed to include both dTE and cTE consistent with the limits for maximum time error at the input to the O-RU. - -**D. Pass/Fail Criteria (expected results)** - -The results as measured for conducted or non-conducted (OTA) on the Air interface from the two (ideal and normal) conditions specified above shall be less than or equal to the values in Table 3.3.3-2, Table 3.3.3-3: - -1. Ideal Case: - -### 3.3.3-1 Frequency error and time error limits at the Air interface output, Ideal operation case. - -| Requirement | Metric | LLS-C1 & LLS-C2 Limit | LLS-C3 Limit | -|-------------|-------------------------|-----------------------|----------------------| -| a | Maximum frequency error | ±35 ppb (see Note 1) | ±48 ppb (see Note 3) | -| b | Maximum time error | +/-80ns (see Note 2) | +/-80ns (see Note 4) | - -NOTE 1: 3GPP limit 50 ppb – 15ppb = 35 ppb, where 15ppb is the error of a class A O-DU (worst-case). -NOTE 2: 3GPP limit 1500 ns – CUS spec 1420ns = 80 ns, where 1420ns is the error allocated to the O-DU for LLS-C1 and LLS C2 -NOTE 3: 50ppb – 2ppb PRTC holdover = 48ppb (PRTC holdover allowance is removed because the ideal case is not a holdover scenario). At high frequencies, error is mostly generated by the O-RU clock. -NOTE 4: 80ns is the time error budget allocation for the O-RU in CUS specification Table 11.3.2.2-1. - -2. Normal Operation Case: - -### 3.3.3-2 Frequency error and time error limits at the Air interface output, Normal operation case. - -| Requirement | Metric | LLS-C1 & LLS-C2 Limit | LLS-C3 Limit | -|-------------|-------------------------|-----------------------|----------------------------------| -| a | Maximum frequency error | ±50 ppb (3GPP limit) | ±50 ppb (3GPP limit) | -| b | Maximum time error | ±1500ns (3GPP limit) | ±1180 ns (see Note 1 and Note 2) | - -NOTE 1: ±1180 ns limit is based on ITU-T G.8273.2 [26]. Clause 7.3.2, including short holdover periods. -NOTE 2: Use of the remaining budget (e.g. for O-RU holdover or longer network holdover) between this limit and the 3GPP limit of 1500 ns is not within scope of this conformance test. - -As multiple O-RUs are not tested, there is no distinction between relative and absolute time error measurement. - -NOTE: This test as currently defined does not provide any allowances for measurement error. It is left to the tester to factor in any errors based on the test equipment used. Defining the allowed measurement error is for future study. - -When the 1 PPS output is available, an optional diagnostic test can be performed on this interface. This test's results provide an indication of the overall O-RU performance by more easily measuring the capabilities of the O-RU's synchronization implementation. For this test example reference target requirements for the 1PPS output during the two conditions (ideal and normal) have been provided in Table 3.3.3-4 and Table 3.3.3-5. - -1. Ideal Case: - -### 3.3.3-4 Frequency error and time error limits at the 1PPS output, Ideal operation case. - -| Requirement | Metric | LLS-C1 & LLS-C2 Limit | LLS-C3 Limit | -|-------------|-------------------------|-----------------------|----------------------| -| a | Maximum frequency error | ±21 ppb (see Note 1) | ±21 ppb (see Note 3) | -| b | Maximum time | +/-60ns (see Note 2) | +/-60ns (see Note 2) | - -| | error | | | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------|--|--| -|

NOTE 1: This case may require further analysis; a conservative value is currently considered. For the ideal operation case, the RMS accumulation of the MTIE and of the high frequency noise specified in ITU-T G.827.2 [26]. class B clock (40 ns and 70 ns respectively) is used to define the 81 ns plateau. This is then combined with a 21 ppb slope on the shorter observation intervals.

NOTE 2: (3GPP limit 1500 ns – CUS spec 1420ns -20 ns = 60 ns, where 1420ns is the error allocated at the input of the O-RU for LLS-C1 and LLS-C2 (in case of regular O-RU), and 20ns is the time error assumed for the radio part of the O-RU (RF)).

NOTE 3: This is the same value used for LLS-C1 and LLS-C2 (the test set up is identical in the ideal case and it should be possible to assume the same implementation of the O-RU is used for LLS-C3 and LLS-C1/LLS-C2). In principle a worst-case value could be based on Table H.2.5-3 (30ppb), but removing the contribution from the network, that would not be far from the value of 21ppb. Due to that and considering the diagnostic purpose of this test, 21ppb can be applied to LLS-C3.

| | | | - -2. Normal Operation Case: - -**3.3.3-5 Frequency error and time error limits at the 1PPS output, Normal operation case.** - -| Requirement | Metric | LLS-C1 & LLS-C2 Limit | LLS-C3 Limit | -|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------|-----------------------|-----------------------| -| a | Maximum frequency error | ±36 ppb (see Note 1) | ±32 ppb (see Note 3) | -| b | Maximum time error | ±1480ns (see Note 2) | ±1160 ns (see Note 4) | -|

NOTE 1: ((3GPP limit 50 ppb - 14ppb = 36 ppb, where 14ppb is the error assumed for the radio part of the O-RU (RF))

NOTE 2: (3GPP limit – 20 ns allocated to the RF).

NOTE 3: 50 ppb - 18 ppb = 32 ppb (where 18 ppb is the error assumed for the radio part of the O-RU (RF), see table H.2.5-3).

NOTE 4: 1180ns – 20 ns = 1160 ns (where 20 ns is allocated to the RF and 1080 ns is the output in case of Normal operation case).

| | | | - -NOTE: An example method to verify the maximum frequency accuracy of the 1PPS output for the normal and ideal operation is to ensure that the MTIE of the output is below the masks described in Figure 3.3.3-2, Table 3.3.3-6, Table 3.3.3-7, Table 3.3.3-8 and Table 3.3.3-9. - -![Log-log plot of MTIE (ns) vs tau (s) for 1PPS output. The y-axis ranges from 0.1 to 10,000 ns, and the x-axis ranges from 0.1 to 1,000 s. Four curves are shown: Ideal operation (blue solid line), LLS-C1 normal operation (green dashed line), LLS-C2 normal operation (green solid line), and LLS-C3 normal operation (red solid line). The Ideal operation curve is flat at approximately 81 ns. The LLS-C1 curve increases linearly from 21 ns at 1 s to about 2,500 ns at 100 s, then remains constant. The LLS-C2 curve increases linearly from 21 ns at 1 s to about 1,200 ns at 100 s, then remains constant. The LLS-C3 curve increases linearly from 21 ns at 1 s to about 1,200 ns at 100 s, then increases again to about 1,200 ns at 1,000 s.](463543bc9a9a8d87e8a62ea5ec128313_img.jpg) - -Log-log plot of MTIE (ns) vs tau (s) for 1PPS output. The y-axis ranges from 0.1 to 10,000 ns, and the x-axis ranges from 0.1 to 1,000 s. Four curves are shown: Ideal operation (blue solid line), LLS-C1 normal operation (green dashed line), LLS-C2 normal operation (green solid line), and LLS-C3 normal operation (red solid line). The Ideal operation curve is flat at approximately 81 ns. The LLS-C1 curve increases linearly from 21 ns at 1 s to about 2,500 ns at 100 s, then remains constant. The LLS-C2 curve increases linearly from 21 ns at 1 s to about 1,200 ns at 100 s, then remains constant. The LLS-C3 curve increases linearly from 21 ns at 1 s to about 1,200 ns at 100 s, then increases again to about 1,200 ns at 1,000 s. - -Figure 3.3.3-2 1PPS output MTIE, normal and ideal operation case (measured on the unfiltered signal) - -**3.3.3-6 1PPS output MTIE, Ideal operation (measured on the unfiltered signal).** - -| Observation Interval (s) | MTIE limit unfiltered (ns) LLS-C1, LLS-C2 and LLS-C3 | -|--------------------------|------------------------------------------------------| -| $1 < \tau \leq 3.8$ | $21 \tau$ | -| $\tau > 3.8$ | 81 (NOTE 1) | - -NOTE 1: The limit is derived assuming a class B T-TSC in the O-RU with $dTE = \sqrt{dTE_L^2 + dTE_H^2} = \sqrt{40^2 + 70^2} = 81\text{ns}$ - -**3.3.3-7 LLS-C1 1PPS output MTIE limit, Normal operation (measured on the unfiltered signal).** - -| Observation Interval (s) | MTIE limit unfiltered (ns) LLS-C1 | -|--------------------------|-----------------------------------| -| $1 < \tau \leq 82.5$ | $36 \tau$ | -| $\tau > 82.5$ | 2969 (NOTE 1) | - -NOTE 1: The limit is derived from CUS-Plane Specification [2]. Table H.2.4-1 unfiltered LLS-C1 mask adding an assumed class B T-TSC in the O-RU with $dTE = \sqrt{dTE_L^2 + dTE_H^2} = \sqrt{40^2 + 70^2} = 81\text{ns}$ - -**3.3.3-8 LLS-C2 1PPS output MTIE limit, Normal operation (measured on the unfiltered signal).** - -| Observation Interval (s) | MTIE limit unfiltered (ns) LLS-C2 | -|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------| -| $1 < \tau \leq 79$ | $36 \tau$ | -| $\tau > 79$ | 2845 (NOTE 1) | -| NOTE 1: The limit is derived from CUS-Plane Specification [2]. Table H.2.4-4 adding an assumed class B T-TSC in the O-RU with $dTE = \sqrt{dTE_L^2 + dTE_H^2} = \sqrt{40^2 + 70^2} = 81\text{ns}$ | | - -**3.3.3-9 LLS-C3 1PPS output MTIE limit, Normal operation (measured on the unfiltered signal).** - -| Observation Interval (s) | MTIE limit unfiltered (ns) LLS-C3 | -|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------| -| $1 < \tau \leq 6.9\text{ s}$ | $32 \tau$ | -| $6.9\text{ s} < \tau \leq 500\text{ s}$ | $207 + 2 \tau$ | -| $\tau > 500\text{ s}$ | 1207 | -| NOTE 1: The limit is derived from CUS-Plane Specification [2]. Table H.2.5-4 adding an assuming a class B T-TSC in the O-RU with $dTE = \sqrt{dTE_L^2 + dTE_H^2} = \sqrt{40^2 + 70^2} = 81\text{ns}$ | | - -The diagnostic test can be considered passed if values are within these limits. - -The diagnostic test should be considered not passed when the measured values are too close to the pass / fail criteria applicable at the air interface as defined above (point 1 and 2 of the Pass/Fail criteria). The actual criteria should be defined case by case depending on the characteristics of the O-RU under test. O-RU vendors should provide indication on a target performance in this case. - -### 3.3.4 Performance test of O-RU using LLS-C4 - -Testing of the O-RU in an LLS-C4 topology is for future study. - -### 3.3.5 Functional test of O-DU Synchronized from ITU-T G.8275.1 profile PRTC/T-GM (LLS-C1/C2/C3/C4) - -#### A. Test Description and Applicability - -This test is MANDATORY. - -The purpose of this test is to validate that an O-DU is correctly synchronizing to a timing reference delivering by PTP (and optionally SyncE) when using ITU-T G.8275.1 [5] profile and that the O-DU correctly reports its status based on the nominal or degraded synchronization conditions generated by CUSM Emulator. - -This test covers all cases where O-DU is synchronized using the Ethernet interface, whether the PRTC/T-GM is: - -- a. Local (direct link from a co-located equipment): case c in Figure 3.3.1-1 -- b. Remote (network connection from a distant equipment): case d in Figure 3.3.1-1 - -These O-DU functional tests do not consider configurations which have multiple sources. It is assumed the O-DU has only a single synchronization source. Multiple sources such as a Multiport PTP/SyncE are for further study. - -## B. Test Entrance Criteria - -O-DU is connected to the sync stimuli directly as shown in Figure 3.3.1-3 via the Ethernet Test Port. - -## C. Test Methodology - -### a) Initial Conditions - -This test uses the O-DU (DUT), a sync tester setup to generate stimulus for the O-DU (DUT) and retrieve its sync status. For LLS-C1/C2 the fronthaul ports must be enabled as ITU-T G.8275.1 [5] synchronization master. - -### b) Procedure - -Three conditions must be tested: - -**Startup:** The CUSM-E is configured to act as a clock, with PTP and SyncE ports in passive state (no messages sent). - -**Nominal:** The CUSM-E is configured to start acting as either a PTP master compliant with the ITU-T G.8275.1 [5] profile advertising LOCKED status with nominal clockClass and clockAccuracy. If SyncE is to be tested CUSM-E is configured to act as a clock, with SyncE ports in master state, compliant to ITU-T G.8264 [36] profile advertising nominal SSM value as specified by ITU-T G.8275.1 [5]. - -**Degraded:** There are two levels of degraded conditions for both PTP and SyncE that the CUSM-E can be configured to. - -- a. The first degradation level is where the CUSM-E is configured to act as a clock, with PTP and SyncE ports in master state, compliant to ITU-T G.8275.1 [5] profile, and sending configured clockClass and/or SSM values within the O-DU's configured accepted limits via the M-plane. -- b. The second degradation level is where the same clockClass and/or SSM values are sent by CUSM-E outside the O-DU's configured accepted limits. - -To cover the all the relevant PTP functional scenarios the test sequence listed in Table 3.3.5-1 steps through the Startup/Nominal/Degraded states in a sequence. Since SyncE is optional, there are two columns, one for PTP status and a second for SyncE. In this table each of the status items (Startup, Nominal, Degraded) correspond to the conditions defined above. - -**3.3.5-1 O-DU Functional Conformance Test Steps with PTP and SyncE Reference.** - -| Step | PTP Status: | SyncE Status (if applicable): SSM | -|------|----------------------------------------------------------------------|--------------------------------------------------------------| -| 1. | Startup: no clockclass | Startup: no SSM/QL | -| 2. | Nominal clockclass=6 | Nominal QL= (see Note 1) | -| 3. | Degraded clockclass but within the O-DU's configured accepted range. | Nominal QL= (see Note 1) | -| 4. | Degraded clockclass outside the O-DU's configured accepted range. | Nominal QL= (see Note 1) | -| 5. | Degraded clockclass outside the O-DU's configured accepted range. | Degraded QL outside the O-RU's configured accepted range. | -| 6. | Nominal clockclass=6 | Nominal QL= (see Note 1) | -| 7. | Nominal clockclass=6 | Degraded QL but within the O-DU's configured accepted range. | -| 8. | Nominal clockclass=6 | Degraded QL outside the O-DU's configured accepted range. | -| 9. | Nominal clockclass=6 | Nominal QL = (see Note1) | -| 10. | S-Plane lost, no message | S-Plane lost, no message | - -NOTE 1: For SyncE, Nominal QL is what is determined as the best acceptable configured value by the O-DU. - -**D. Pass Fail Criteria (expected results)** - -The acceptance criterion is that the status reported by the O-DU for the steps defined in above procedure matches the results described in the 2 tables which follow, Table 3.3.5-2 and Table 3.3.5-3. The tables cover 2 different use cases. 1) PTP without SyncE, and 2) PTP with SyncE. The test engineer should choose the appropriate table(s) based on the equipment's intended application(s). - -Each of the tables are formatted similarly. The left two columns indicate the procedural steps as defined in Table 3.3.5-1. The right columns list the O-DU status parameters that are defined in the M-Plane specification [3] (chapter 13 Synchronization Aspects) and WG5 YANG Model [27] (o-ran-synchronization yang model). These parameters are queried from the test O-DU and their values should match those listed in the tables. - -When an O-DU's selected time source is PTP and optional SyncE, the parameters to be checked are: Sync-state, PTP sync-source-status, PTP clock-class, SyncE sync-source-status, SyncE quality-level. - -In LLS-C1 and LLS-C2 and regardless of the selected time source, the PTP Master sync-source-status, PTP Master clock class, SyncE Master sync-source-status, and SyncE Master Quality Level shall also be monitored. - -For PTP master clock-class, optional SyncE quality-level and master quality-level, the "Rcvd Value" table entry indicates that the value read should be the same as the one received by the O-DU (except in Startup and Disconnected modes when there is no such received value and the default one is reported). - -In case of local failure in the O-DU then O-DU should use FREERUN mode. - -These tests do not consider configurations which have multiple sources. This is for further study. - -3.3.5-2 O-DU LLS-C1/C2/C3/C4 Functional Conformance Test Results with PTP Reference without SyncE Assistance. - -| Step | O-DU PTP Status | PTP Input Parameters | | | PTP/SyncE Output Parameters (Note 5) | | | | -|---------|--------------------------|--------------------------------|------------------------|-----------------|--------------------------------------|------------------------|---------------------------------|---------------------------| -| | | sync -state | ptp sync-source-status | ptp clock-class | ptp master sync-source-status | ptp master clock-class | sync master sync-source-status | sync master quality-level | -| 1. | Startup | FREERUN | NOT_USABLE | 248 or 255 | NOT_USABLE | 248 | NOT_USABLE | Note 1 | -| 2. | Nominal | LOCKED | IN_USE | Rcvd Value | IN_USE | Rcvd Value | IN_USE | PRC | -| 3. | Degraded, within range | LOCKED | IN_USE | Rcvd Value | IN_USE | Rcvd Value | IN_USE | Note 1 | -| 4. - 5. | Degraded, outside range. | HOLDOVER (Note 2) then FREERUN | NOT_USABLE | Rcvd Value | IN_USE (Note 2) then NOT_USABLE | Notes 1, 4 | IN_USE (Note 2) then NOT_USABLE | Note 1 | -| 6. - 9. | Nominal | LOCKED | IN_USE | Rcvd Value | IN_USE | Rcvd Value | IN_USE | PRC | -| 10. | None (disconnected) | HOLDOVER (Note 2) then FREERUN | NOT_IN_USE | Notes 1, 4 | IN_USE (Note 2) then NOT_USABLE | Notes 1, 4 | IN_USE (Note 2) then NOT_USABLE | Note 1 | - -NOTE 1: This is not specified by CUS-Plane and is implementation dependent. - -NOTE 2: HOLDOVER mode is optional and depends on internal O-DU design. After HOLDOVER (either assisted by SyncE or relying on local oscillator) expires, then the O-DU goes to FREERUN. In CUS-Plane specification [2] the FREERUN state is defined to occur at start up prior to O-DU acquiring LOCK, and it also occurs when O-DU is in HOLDOVER and the reference is no longer within specification. - -NOTE 3: in case of local failure inside the O-DU. - -NOTE 4: as per ITU-T G.8275.1 [5], degraded clockclass values in HOLDOVER may be either, (a) 7, then 140 or 150 or 160, for an O-DU acting as a Grandmaster clock, or (b) 135, then 165 for an O-DU behaving as a Boundary clock. - -NOTE 5: PTP/SyncE output parameters are optional for LLS-C3\C4. SyncE output parameters are optional for LLS-C1 in the case where O-RU does not use SyncE. For LLS-C2 PTP/SyncE Output Parameters are required. - -**3.3.5-3 O-DU LLS-C1/C2/C3/C4 Functional Conformance Test Results with PTP Reference With SyncE Assistance.** - -| Step | O-DU PTP and SyncE Status | PTP/SyncE Input Parameters | | | | | PTP/SyncE Output Parameters
(Note 6) | | | | -|------|---------------------------------------------------------------------------|------------------------------------------|------------------------|-----------------|--------------------------|---------------------|------------------------------------------|------------------------|---------------------------------|----------------------------| -| | | sync -state | ptp sync-source-status | ptp clock-class | syncE sync-source-status | syncE quality-level | ptp master sync-source-status | ptp master clock-class | syncE master sync-source-status | syncE master quality-level | -| 1. | Startup | FREERUN | NOT_USABLE | 248 or 255 | NOT_USABLE | Note 1 | NOT_USABLE | 248 | NOT_USABLE | Note 1 | -| 2. | PTP: Nominal
SyncE: Nominal | LOCKED | IN_USE | Rcvd Value | IN_USE or
USABLE | Rcvd Value | IN_USE | Rcvd Value | IN_USE | Rcvd Value | -| 3. | PTP: Degraded,
in range
SyncE: Nominal | LOCKED | IN_USE | Rcvd Value | IN_USE or
USABLE | Rcvd Value | IN_USE | Rcvd Value | IN_USE | Rcvd Value | -| 4. | PTP: Degraded,
outside range.
SyncE: Nominal | HOLD OVER
(Note 2)
then
FREERUN | NOT_USABLE | Rcvd Value | IN_USE | Rcvd Value | IN_USE
(Note 2)
then
NOT_USABLE | Notes 1, 4 | IN_USE
then
NOT_USABLE | Rcvd Value | -| 5. | PTP: Degraded,
outside range.
SyncE:
Degraded,
outside range. | HOLD OVER
(Note 2)
then
FREERUN | NOT_USABLE | Rcvd Value | NOT_USABLE | Rcvd Value | IN_USE
(Note 2)
then
NOT_USABLE | Notes 1, 4 | IN_USE
then
NOT_USABLE | Rcvd Value | -| 6. | PTP: Nominal
SyncE: Nominal | LOCKED | IN_USE | Rcvd Value | IN_USE or
USABLE | Rcvd Value | IN_USE | Rcvd Value | IN_USE | Rcvd Value | -| 7. | PTP: Nominal
SyncE:
Degraded, in
range. | LOCKED | IN_USE | Rcvd Value | IN_USE or
USABLE | Rcvd Value | IN_USE | Rcvd Value | IN_USE | Rcvd Value | -| 8. | PTP: Nominal
SyncE:
Degraded,
outside range. | Implementation Specific
(Note 5) | IN_USE | Rcvd Value | NOT_USABLE | Note 1 | IN_USE
or (Note 2)
NOT_USABLE | Rcvd Value | Note 1 | Note 1 | -| 9. | PTP: Nominal
SyncE: Nominal | LOCKED | IN_USE | Rcvd Value | IN_USE or
USABLE | Rcvd Value | IN_USE | Rcvd Value | IN_USE | Rcvd Value | -| 10. | PTP: None
(disconnected)
SyncE: None
(disconnected) | HOLDOVER
(Note 2)
then
FREERUN | NOT_IN_USE | Notes 1, 4 | NOT_IN_USE | Note 1 | IN_USE
(Note 2)
then
NOT_USABLE | Notes 1, 4 | IN_USE
then
NOT_USABLE | Note 1 | - -| Step | O-DU PTP and SyncE Status | PTP/SyncE Input Parameters | | | | | PTP/SyncE Output Parameters (Note 6) | | | | -|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------|----------------------------|------------------------|-----------------|--------------------------|---------------------|--------------------------------------|------------------------|---------------------------------|----------------------------| -| | | sync -state | ptp sync-source-status | ptp clock-class | syncE sync-source-status | syncE quality-level | ptp master sync-source-status | ptp master clock-class | syncE master sync-source-status | syncE master quality-level | -| NOTE 1: This is not specified by CUS-Plane and is implementation dependent.
NOTE 2: HOLDOVER mode is optional and depends on internal O-DU design. After HOLDOVER (either assisted by SyncE or relying on local oscillator) expires, then the O-DU goes to FREERUN. In CUS-Plane specification [2] the FREERUN state is defined to occur at start up prior to O-DU acquiring LOCK, and it also occurs when O-DU is in HOLDOVER and the reference is no longer within specification.
NOTE 3: in case of local failure inside the O-DU.
NOTE 4: As per ITU-T G.8275.1 [5], degraded clockclass values in HOLDOVER may be either, (a) 7, then 140 or 150 or 160, for an O-DU acting as a Grandmaster clock, or (b) 135, then 165 for an O-DU behaving as a Boundary clock.
NOTE 5: Depending on O-DU implementation the Sync-state may be LOCKED or “HOLDOVER (Note 2) then FREERUN.”
NOTE 6: PTP/SyncE output parameters are optional for LLS-C3\C4. SyncE output parameters are optional for LLS-C1, in the case where O-RU does not make use of SyncE. For LLS-C2 PTP/SyncE Output Parameters are required. | | | | | | | | | | | - -### 3.3.6 Functional test of O-DU Synchronized from Embedded or Local non-PTP PRTC (LLS-C1/C2/C3/C4) - -#### A. Test Description and Applicability - -This test is CONDITIONAL-MANDATORY. This test is mandatory if the DUT contains: - -- a. Either an O-DU with an embedded local PRTC using a GNSS receiver (see case a in Figure 3.3.1-1) -- b. Or an O-DU connected by a 1PPS + serial interface (e.g. ITU-T G.8271 [31], see case b in Figure 3.3.1-1) to a co-located PRTC provided by the test setup. - -The purpose of this test is to validate that an O-DU is correctly synchronizing to a non-PTP local time source and that the O-DU correctly reports its status based on the nominal or degraded synchronization conditions generated by CUSM Emulator. - -This O-DU functional test does not consider configurations which have multiple time sources. - -#### B. Test Entrance Criteria - -O-DU is connected to the time sync stimuli directly as shown in Figure 3.3.1-3 via the GNSS RF signal or local PRTC output signals. - -#### C. Test Methodology - -##### a) Initial Conditions - -This test uses a time reference, synchronization tester setup and SMO/M-Plane functions to generate stimulus for the O-DU (DUT) and then retrieves the O-DU’s sync status. For LLS-C1/C2 the fronthaul ports must be enabled as an ITU-T G.8275.1 [5] synchronization master. - -##### b) Procedure - -Three conditions must be tested: - -**Startup:** The CUSM-E is configured to act as a clock, with its output signals (either GNSS RF or PRTC ones) not started sending time information to DUT. - -**Nominal:** The CUSM-E is configured to start delivering output signals (either GNSS RF or PRTC ones) in LOCKED status with optimal time and state information. - -**Degraded:** The degraded conditions for GNSS receiver's or PRTC output are not well defined. There are no defined "slightly degraded" or "severely degraded" signal indications. Thus, the indication of a degraded state may be implementation specific. Further, a degraded GNSS scenario is the only condition which causes the O-DU to lose its locked status. - -For GNSS RF signals, one proposal is to simulate the reception of a single satellite with a low signal level. However, all GNSS receivers may not offer the same sensitivity and robustness to this scenario. - -For GNSS-based PRTC output signals, one proposal is to advertise an alarm on poor signal status, but every protocol may have its own alarm mapping - -To cover the all the relevant functional scenarios the test sequence listed in Table 3.3.6-1 steps through the Startup/Nominal/Degraded states in order. In this table each of the status items corresponds to the conditions defined above. - -**3.3.6-1 O-DU Functional Conformance Test Steps with GNSS Reference.** - -| Step | GNSS RF or PRTC output Status | -|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------| -| 1. | Startup Status (and GNSS Acquiring Mode if implemented) Note 1. | -| 2. | Nominal | -| 3. | Degraded, | -| 4. | Nominal | -| 5. | Failed (no signal) | -| NOTE 1: After a power cycle it may take some time for GNSS receiver or PRTC to complete self-survey and progress to Nominal mode. | | - -**D. Pass Fail Criteria (expected results)** - -The acceptance criterion when the O-DU uses GNSS is that the status reported by the O-DU for the steps defined in the above procedure in Table 3.3.6-1 matches the results described in Table 3.3.6-2. The left column of this table indicates the procedural step numbers as defined in Table 3.3.2-8. The second column summarizes the O-DU status for each step. The right 7 columns list the O-DU status parameters as they are defined in the M-Plane specification [3] (chapter 13 Synchronization Aspects) and relevant YANG models. These columns show the required values of the parameters queried from the test O-DU under test. - -When an O-DU's selected time source is GNSS and optional SyncE, the input parameters to be queried are: Sync-state, GNSS sync-source-status, GNSS sync-status. - -Regardless of the selected time source the output parameters which are monitored are the PTP Master sync-source-status, PTP Master clock-class, SyncE Master sync-source-status, and SyncE Master quality-level. Specifically, for LLS-C1 configuration the emission of SyncE by O-DU is only mandatory if O-RU requires it. - -SyncE assistance for GNSS is not considered in this test case and is left for future study. - -### 3.3.6-2 O-DU LLS-C1/C2/C3/C4 Functional Conformance Test Results with GNSS Reference. - -| Step | O-DU GNSS, Status | GNSS Input Parameters | | | PTP/SyncE Output Parameters | | | | -|------|--------------------|---------------------------------|----------------------------|----------------------|-------------------------------------|------------------------|-------------------------------------|---------------------------| -| | | sync-state | gnss sync-source-status | gnss sync-status | ptp master sync-source-status | ptp master clock-class | sync master sync-source-status | sync master quality-level | -| 1. | Startup | FREE RUN | USABLE | ACQUIRING-SYNC | NOT_USABLE | 248 | NOT_USABLE | Note 1 | -| 2. | Nominal | LOCKED | IN_USE | SYNCHRONIZED | IN_USE | 6 | IN_USE | PRC | -| 3. | Degraded | HOLDOVER (Note 2) then FREE RUN | NOT_IN_USE then NOT_USABLE | SYNCHRONIZED | NOT_IN_USE (Note 2) then NOT_USABLE | (Notes 1, 3) | NOT_IN_USE (Note 2) then NOT_USABLE | Note 1 | -| 4. | Nominal | LOCKED | IN_USE | SYNCHRONIZED | IN_USE | 6 | IN_USE | PRC | -| 5. | Failed (no signal) | HOLDOVER (Note 2) then FREE RUN | NOT_IN_USE | ANTENNA-DISCONNECTED | NOT_IN_USE (Note 2) then NOT_USABLE | (Notes 1, 3) | NOT_IN_USE (Note 2) then NOT_USABLE | Note 1 | - -NOTE 1: This is not specified by CUS-Plane and is implementation dependent. -NOTE 2: After HOLDOVER (relying on local oscillator) expires, then O-DU goes to FREE RUN. In CUS-Plane specification the FREE RUN state is defined to occur at start up prior to O-DU acquiring LOCK, and it also occurs when O-DU is in HOLDOVER and the reference is no longer within specification. -NOTE 3: As per ITU-T G.8275.1 [5], degraded clockclass values in HOLDOVER may be 7, then 140 or 150 or 160, for an O-DU acting as a Grandmaster clock. - -### 3.3.7 Performance test of O-DU Synchronized from either Local or Remote PRTC using ITU-T G.8275.1 PTP Profile (LLS-C1/C2/C3/C4) - -#### A. Test Description and Applicability - -This test scope is relevant to LLS-C1 to LLS-C4. - -This test is CONDITIONAL-MANDATORY for O-DUs which support LLS-C1, LLS-C2 and do not only derive their timing information from an embedded PRTC. - -This test is OPTIONAL for O-DUs that only support LLS-C3 or LLS-C4 topology and is dependent on the availability of a measurement point. For equipment that only supports LLS-C3 or LLS-C4, if the measurement point is not available, then the O-DU shall document that this conformance test cannot be performed. - -This test validates that an O-DU correctly synchronizes to incoming S-Plane timing information, from a CUSM-plane Emulator which is emulating: - -- a. Either a local PRTC (using 1PPS+ serial link interface, e.g. ITU-T G.8271 [31], see case b in Figure 3.3.1-1) or local PRTC/T-GM (PTP and optionally SyncE, see case c in Figure 3.3.1-1) and meeting ITU-T G.8271.1 [7] reference point B network limits. -- b. Or a remote PRTC/T-GM (PTP and optionally SyncE, see case d in Figure 3.3.1-1) meeting ITU-T G.8271.1 [7] reference point C network limits. The CUSM-E may be configured to inject normal operating condition noise into the S-Plane timing information. Frequency and time error measured at the output of the O-DU must be within specified limits, which may differ between LLS-C1-C4 configurations. - -As an example, the local reference link may use ITU-T G.8271 [31] Annex A “1PPS+ToD” protocol. - -This test covers the two classes defined by CUS -plane spec for PTP and SyncE for LLS -C1 and LLS -C2 (class A has $\pm 15$ ppb frequency error limit; class B has $\pm 5$ ppb limit). - -Additional tests may be required to verify the capability to support all possible fronthaul network SyncE architectures as per Recommendation ITU-T G.8261 [10] (e.g., for the case of an O-DU clock part of an ITU-T G.803 [37] synchronization reference chain, wander accumulation should be controlled to guarantee that the applicable network limits are met along the chain). The present tests in this subclause do not address these details. - -This test is defined assuming a Full Timing Support (FTS) profile used on all PTP ports of the O-DU. Partial timing support is left for further study. - -The test intent is to exercise S-Plane performance under typical/normal operating condition. The test is not intended to exercise worst case conditions. It is the vendor's responsibility to make sure that limits defined in the test are also met in worse-case field conditions. Variable temperature, PTP PDV tolerance and SyncE jitter/wander tolerance, holdover and transients are beyond the scope of the CUS-Plane specification [2]. - -## B. Test Entrance Criteria - -Conformance Functional test in clause 3.3.5 has successfully passed. - -O-DU is connected to CUSM-Plane Emulator's time reference output interface. - -## C. Test Methodology - -### a) Initial Conditions - -These tests configure the DUT (O-DU) using any available method. The O-DU configuration depends on which LLS-C1-C4 topologies are to be tested and also it depends on whether the PRTC is local or remote. - -For LLS-C1 and LLS-C2 configuration, the test is set up to measure frequency and time error on one of the Ethernet master fronthaul ports of the DUT. - -For LLS-C3 and LLS-C4 configuration, the test is configured to measure time error on a measurement port of the O-DU, typically a 1PPS signal if available or an unused Ethernet port. - -CUSM-Plane Emulator is configured to act as a clock, with PTP ports in master state, compliant to ITU-T G.8275.1 [5] profile advertising LOCKED status with nominal clockClass and clockAccuracy. - -CUSM-Plane Emulator is configured to act as a clock, with SyncE ports in master state, compliant to ITU-T G.8264 [36] profile advertising nominal SSM value. - -CUSM-Plane Emulator is configured to deliver 1PPS and act as a PRTC advertising LOCKED status over its serial link with nominal quality level (whatever protocol is used, ITU-T G.8271 [31] or proprietary). - -Once the DUT has been configured, the DUT shall have achieved frequency and phase lock prior to starting the test. - -**b) Procedure:** - -Unlike the functional test defined in clause 3.3.5, where start-up / nominal / degraded scenarios are tested, only nominal scenarios with *normal* operation input noise are tested in this section. - -- **Normal Operation:** The CUSM-Plane Emulator provides an input stimulus with some added noise that is “within normal operating limits.” O-DU inputs as specified in CUS-Plane Specification [2]. - -The CUS requirements and subsequent PTP test patterns specify absolute value for constant time error ( $|cTE|$ ). Dynamic time error ( $dTE$ ) implicitly varies positive/negative, but $cTE$ does not. It is possible that an O-DU can pass the test with positive $cTE$ , and fail with negative $cTE$ (or vice versa). Therefore, regardless of which method is used for the PTP test pattern, this test shall be performed twice: once with the CUSM-Plane Emulator generating positive $cTE$ in the PTP test pattern, and again with the CUSM-Plane Emulator generating negative $cTE$ in the PTP test pattern. The pass/fail criteria are the same for both tests. - -If SyncE is used for the input stimulus (Figure 3.3.1-1 (c) and (d)), the following applies: - -- The noise is as per ITU-T G.8262 clause 9.1 [29]. -- If the O-DU implementation supports ITU-T G.8262.1 Level 1 only, the noise is as per ITU-T G.8262.1 clause 9.1 [30]. This is acceptable for cases where the O-DU is expected to be deployed in enhanced synchronous Ethernet networks only. - -NOTE: The CUSM-Plane Emulator may be configured to generate time and frequency noise on PTP and SyncE, either simultaneously or sequence. Presenting noise at SyncE and PTP inputs simultaneously represents a more realistic option to verify expected performance in a real network, so this set up is recommended. In this case, the additional noise on SyncE stimulus should not increase the PTP stimulus noise above the specified time error limits. - -Two methods are proposed to define the PTP test patterns: - -1. In the first method, the TEL stimulus is split between dynamic ( $|dTEL|$ ) and constant ( $|cTE|$ ) and is shown in Table 3.3.7-1. The maximum absolute time error ( $\max |TEL|$ ) is - - 1100ns at ITU-T G.8271.1 [7] clause 7.3 reference point C (for remote PRTC/T-GM over PTP) - - 100ns at ITU-T G.8271.1 [7] clause 7.2 reference point B (for both local PRTC/T-GM over PTP, and PRTC over 1PPS+ serial link interface) - -The time error added to the input signal shall follow a sinusoidal waveform with amplitude (A) and frequency (f) as specified in Table 3.3.7-1. Three such signal frequencies are specified for this test, but intermediate ones can be used for testing as well. - -### 3.3.7-1 Remote Timing Input Error Limits for Normal Operation Test (Note 3) - -| Frequency [Hz] | At Reference Point C | | | At Reference Point B | | | Test Duration [s] | -|----------------|--------------------------|----------------------------------|--------------------------|--------------------------|----------------------------------|--------------------------|-------------------| -| | Sine wave amplitude [ns] | Dynamic Time Error [ns] (Note 1) | Constant Time Error [ns] | Sine wave amplitude [ns] | Dynamic Time Error [ns] (Note 2) | Constant Time Error [ns] | | -| 0.003362 | 214 | 428 | 886 | 30 | 60 | 70 | 595 (2 periods) | -| 0.010 | 165 | 330 | 935 | 19 | 38 | 81 | 500 (5 periods) | -| 0.100 | 141 | 282 | 959 | 13 | 26 | 87 | 50 (5 periods) | - -NOTE 1: The dynamic time error values for Point C are derived from the limits defined in ITU-T G.8271.1 [7] Table 7-1 and Figure 7-2. - -NOTE 2: The dynamic time error values for Point B are derived from the limits defined in ITU-T G.8272 [35], Figure 1. - -NOTE 3: The dynamic time error values in the table are given as peak-to-peak values. The sine wave amplitudes are zero to peak values. - -![Graph titled 'O-DU input sine wave amplitude vs. frequency'. The x-axis is Frequency [Hz] on a logarithmic scale from 0.001 to 0.1. The y-axis is Amplitude [ns] on a logarithmic scale from 10 to 1000. Two data series are plotted: 'Sine wave amplitude Point C' (blue dots) and 'Sine wave amplitude Point B' (orange dots). Data points for Point C are (0.003362, 214), (0.01, 165), and (0.1, 141). Data points for Point B are (0.003362, 30), (0.01, 19), and (0.1, 13).](ac776ddad6224ba7e1d9f3c9e39540fb_img.jpg) - -| Frequency [Hz] | Sine wave amplitude Point C [ns] | Sine wave amplitude Point B [ns] | -|----------------|----------------------------------|----------------------------------| -| 0.003362 | 214 | 30 | -| 0.01 | 165 | 19 | -| 0.1 | 141 | 13 | - -Graph titled 'O-DU input sine wave amplitude vs. frequency'. The x-axis is Frequency [Hz] on a logarithmic scale from 0.001 to 0.1. The y-axis is Amplitude [ns] on a logarithmic scale from 10 to 1000. Two data series are plotted: 'Sine wave amplitude Point C' (blue dots) and 'Sine wave amplitude Point B' (orange dots). Data points for Point C are (0.003362, 214), (0.01, 165), and (0.1, 141). Data points for Point B are (0.003362, 30), (0.01, 19), and (0.1, 13). - -3.3.7-1 Graph of sine wave amplitude limits for test signal - -- An alternative and more representative method for reference point C is to apply a noise pattern that meets the network limit mask defined in ITU-T G.8271.1 [7], Table 7-1/Figure 7-2. This method is described in ITU-T G.8273.2 [26] Appendix IX. The advantage of this is that it is more representative of real network conditions and transients, and therefore a more effective test of the O-DU under emulated network conditions. The pattern can be constructed to include both dTE and cTE consistent with the limits for maximum time error at the input to the O-DU. - -#### D. Pass/Fail Criteria (expected results) - -The measured results for Normal Operation shall be less than or equal to these values: - -- Maximum 0.1Hz low pass filtered frequency error for LLS-C1 and LLS-C2 on PTP and SyncE (see Note 1) - - ±15 ppb for class A O-DU - - ±5 ppb for class B O-DU -- Maximum 0.1Hz low pass filtered time error (see Note 1) - - ±1420ns for LLS-C1 on PTP. - -±1325ns for LLS-C2 on PTP. - -±1500ns for LLS-C3 and LLS-C4 on the measurement point (optional) (see Note 5). - -If O-DU acts as PLFS synchronization master, frequency error shall be validated for SyncE output from the O-DU. For information on requirements, refer to 11.3.2 of [2]. - -NOTE 1: An example method to verify this for PTP is to ensure the MTIE of the output is below the masks described in Table H.2.4-1 and Figure H.2.4-2 (for a Class A O-DU) or Table H.2.4-2 and Figure H.2.4-3 (for a Class B O-DU) of [2] - -NOTE 2: This test as currently defined does not provide any allowances for measurement error. It is left to the tester to factor in any errors based on the test equipment used. Defining the allowed measurement error is for future study. - -NOTE 3: If the test for Normal Operation fails, it can be helpful for the CUSM-Plane Emulator to provide an optional diagnostic test for Ideal Operation. The diagnostic test for Ideal Operation provides an ideal O-DU synchronization input, with not implicitly added dynamic or constant time error. Since noise is removed from the input, noise will be removed from the O-DU synchronization output. Removal of the noise can help to diagnose whether the Normal Operation failure was due to the noise, or other factors. The present CUS-Plane specification [2] does not specify requirements for O-DU performance under Ideal Operation. This present document does not specify reference target requirements (i.e. pass/fail criteria) for Ideal Operation. - -NOTE 4: To meet the above requirements on PTP and SyncE a clock with a specific filtering and noise generation capability is required, better than Recommendation ITU-T G.8273.2 [26] and Recommendation ITU-T G.8262 [29] / Recommendation ITU-T G.8262.1 [30] respectively. - -NOTE 5: In addition, in the special LLS-C3 case where the O-DU is part of the LLS-C3 sync chain towards the O-RU, the time error at the O-DU fronthaul ports need to stay inside a suitable portion of the 1100 ns network limits, and the related O-DU clock as per CUS specification [2] is required to comply with ITU-T G.8273.2 [26]. This scenario is not covered in this subclause. - -### 3.3.8 Performance test of O-DU Synchronized from Embedded GNSS receiver (LLS-C1/C2/C3/C4) - -#### A. Test Description and Applicability - -This test scope is relevant to LLS-C1 to LLS-C4. - -This test is **CONDITIONAL-MANDATORY**. This test is mandatory if the DUT contains an O-DU with an embedded local PRTC using a GNSS receiver (see case a in Figure 3.3.1-1). - -This test validates that an O-DU correctly synchronizes to incoming timing information, from a CUSM-plane Emulator which is emulating a GNSS transmitter’s RF signal. The DUT shall contain a GNSS receiver, either embedded within the O-DU, or directly connected to the O-DU. The CUSM-E may be configured to inject either ideal or normal operating condition noise into the timing information. Frequency and time error measured at the output of the O-DU must be within specified limits, which may differ between LLS-C1-C4 configurations. - -NOTE: Configuring the CUSM-E to inject normal operating condition noise is for further study. - -This test covers the two classes defined by CUS -plane spec for LLS -C1 and LLS -C2 (class A has ±15 ppb frequency error limit; class B has ±5 ppb limit). - -The test intent is to exercise S-Plane performance under ideal and a typical/normal operating condition. The test is not intended to exercise worst case conditions. It is the vendor's responsibility to make sure that limits defined in the test are also met in worse-case field conditions. Variable temperature, degraded GNSS reception (degraded sky view, multipath, jamming, spoofing etc.), holdover and transients are beyond the scope of the CUS-Plane specification [2]. - -This test is defined assuming a Full Timing Support (FTS) profile on all PTP ports. Partial timing support is left for further study. - -## B. Test Entrance Criteria - -Conformance Functional test 3.3.6 has successfully passed. - -O-DU is connected to CUSM-Plane Emulator's GNSS time reference RF interface. - -## B. Test Methodology - -### a) Initial Conditions - -These tests configure the DUT (O-DU) using the using any available method. The O-DU configuration depends on which LLS-C1-C4 topologies are to be tested. - -For LLS-C1 and LLS-C2 configuration, the test is set up to measure frequency and time error on one of the Ethernet master fronthaul ports of the DUT. - -For LLS-C3 and LLS-C4 configuration, the test is configured to measure time error on a measurement port of the O-DU, typically a 1PPS signal if available or an unused Ethernet port configured as a PTP master. - -CUSM-Plane Emulator is configured to act as a GNSS transmitter, with time reference which is traceable to UTC. - -Once the DUT has been configured, the DUT shall have achieved frequency and phase lock prior to starting the test. - -### b. Procedure: - -Unlike the functional test defined in clause 3.3.2, where start-up / nominal / degraded scenarios are tested, only nominal scenarios with *ideal* and *normal* operation input noise are tested. The test procedure is the same for both ideal and normal scenarios, the only difference is the noise settings for the timing source. - -- **Ideal Operation:** The time source provides “ideal” O-DU synchronization input with no implicitly added dynamic or constant time error. -- **Normal Operation:** This test is for further study - -## C. Pass/Fail Criteria (expected results) - -The measured results for Ideal and Normal Operation Cases shall be less than or equal to these values: - -- a. Maximum 0.1Hz low pass filtered frequency error for LLS-C1 and LLS-C2 - $\pm 15$ ppb for class A O-DU - $\pm 5$ ppb for class B O-DU -- b. Maximum 0.1Hz low pass filtered time error - $\pm 1420$ ns for LLS-C1. - $\pm 1325$ ns for LLS-C2. - -±1500ns for LLS-C3 and LLS-C4. - -NOTE: This test as currently defined does not provide any allowances for measurement error. It is left to the tester to factor in any errors based on the test equipment used. Defining the allowed measurement error is for future study. - -### 3.3.9 Performance test of O-RU using ITU-T G.8275.1 Profile (LLS-C1/C2/C3), additional tests for cascaded O-RUs - -In addition to tests described in clause 3.3.3, the full validation of an O-RU that is deployed in the synchronization path in cascaded O-RU mode requires the implementation of additional tests. In particular, as per 11.2.2.2 of O-RAN CUS Specification [2], if deployed in this mode, the O-RU shall also implement Recommendation ITU-T G.8273.2 [26], T-BC or Recommendation ITU-T G.8273.3 [28] T-TC. Therefore, further performance testing to ensure conformance to either or both of those recommendations shall be performed in addition to this performance test. - -Details of the additional tests are not yet specified. Until details of the test case to be used are specified in the present document, the tester shall verify proper T-BC and/or T-TC functionality according to ITU-T G.8273.2 [26] and/or ITU-T G.8273.3 [28] utilizing additional test cases that can verify compliance with these Recommendations. These measurement results along with details of the test executed shall be documented in the test report. - -## 3.4 UC-Plane Measurements O-DU - -### 3.4.1 UC-Plane Tests - -This clause describes conformance test scenarios for O-DU equipment implementing the U-Plane and C-Plane O-RAN option 7.2x protocols. In these set of tests, the device under test (DUT) is either a stand-alone O-DU, or a combined O-CU + O-DU from a single vendor. Throughout this clause, we may refer to the DUT generically as the O-DU for brevity, keeping in mind that there are these two potential DUT variants. - -### 3.4.2 UC-Plane Standard Test Definitions - -Clause 2.2 outlines the test configuration for the O-DU tests in this clause and provides an overview of the Test Equipment O-DU (TED) required to conduct the tests. The following are the generic test steps to be used, although specific tests may deviate from this general procedure: - -- 1) Configure the Test Equipment, O-DU (TED) for test execution, which may include defining the specific test to execute. This includes configuring the various components comprising the TED: - - a. Configure the Core Emulator (and O-CU Emulator in the case of a stand-alone O-DU DUT) and the X2 signalling emulator for NSA mode such that it is ready to communicate with the DUT via the appropriate interfaces for the specific test scenario - - b. Configure the O-RU + UE Emulator such that it is ready to communicate to the DUT over the CUSM-planes of the open fronthaul interface for the specific test scenario, which may include configuring the O-RU emulator to emulate a certain type of O-RU, e.g. CAT-A, CAT-B, TDD, FDD; and configuring the UE emulator appropriately such that it can connect to the network for the specific test scenario -- 2) Configure the O-DU DUT via the O1 (if available) or EMS interface to provision the DUT in order to place it into the appropriate modes to exercise the specific scenario and features under test. Note that these should not be special test modes but are instead production modes that are used for provisioning the commercial O-DU to support various deployment configurations -- 3) Instruct the UE Emulator to initiate a connection with the O-DU DUT through the O-RU emulator via the open fronthaul interface and on to the rest of the emulated network via the F1 interface -- 4) Observe that the UE Emulator successfully attaches to the network and has successful data communications in both the downlink and uplink -- 5) Perform detailed observation and analysis of the front haul data stream of the O-DU DUT in order to ascertain compliance to the specifications. - -### 3.4.3 Minimum Capabilities of the TED for U-Plane and C-Plane Tests - -Since many features of the O-RAN protocol rely on the O-DU instructing the O-RU to put data in specific resource blocks using a specific compression method it is imperative that the test equipment support features that allow detailed observation and analysis of the front haul data stream. Furthermore, since the O-DU is meant to support various classes of O-RU with different feature sets, e.g. CAT-A or CAT-B, FR1 or FR2, different beamforming methods to multiple UEs, different compression schemes, etc., it is important that the TED has the flexibility to effectively emulate the various scenarios in a robust and repeatable manner in order to test the various features. As noted in clause 2.2, this specification does not preclude the use of the commercial equivalent elements instead of emulators, but must support a level of configurability and repeatability to ensure that the required features in the O-DU front-haul are effectively and repeatably exercised. With use of either node emulators or commercial equivalents, the required test outcomes and reports must be effectively and repeatably reproduced. The rest of this clause shall assume emulators are used for brevity of description. - -#### 3.4.3.1 Core + O-CU Emulator for Testing a Stand-alone O-DU DUT - -- Must have the capability of emulating and observing the appropriate signals at the F1 interface that enables the O-DU DUT to support connecting with the UE Emulator through the O-RU Emulator via the open front haul -- Must have the capability of supporting the various modes that the O-DU DUT shall be provisioned to via the O1 or EMS interface for the various test cases and scenarios - -#### 3.4.3.2 Core Emulator for Testing a Combined O-CU + O-DU DUT - -- Must have the capability of emulating an EPC (NSA/LTE) or NGC (SA) and observing the appropriate signals at the NG (SA) or S1 (NSA) interface that enables the O-DU DUT to support connecting with the UE Emulator through the O-RU Emulator via the open front haul -- Must have the capability of supporting the various modes that the O-DU DUT shall be provisioned to via the O1 or EMS interface for the various test cases and scenarios - -### 3.4.3.3 X2 Signalling Emulator for NSA - -- Must have the capability of emulating the signalling over the X2 interface to the O-CU Emulator for the case of testing a Stand-alone O-DU DUT, or to the actual O-CU for the case of testing combined O-CU+O-DU DUT, in order to support an NSA connection -- Must have the capability of supporting the various modes that the O-DU DUT shall be provisioned to via the O1 or EMS interface for the various test cases and scenarios - -### 3.2.3.4 O-RU Emulator - -- Must have the capability of emulating various types of O-RUs in order to exercise the various features of the open front haul of the O-DU DUT -- Must be able to be synchronized with the O-DU DUT to ensure proper timing of uplink C-Plane and U-Plane messages -- Must be able to observe and analyse the front haul data stream of the O-DU DUT in order to ascertain compliance to the specifications of the specific test scenario - -### 3.4.3.5 UE Emulator - -- Must have the capability of emulating a UE (or multiple UEs in the case of beamforming tests) that can successfully complete a connection with the O-DU DUT all the way through to the Core Emulator -- Must be able to connect with the O-RU Emulator through a digital or RF interface -- Must be able to observe and analyse the state of the connection and the uplink and downlink throughput in order to ascertain the successful connection with the network through the O-DU DUT - -### 3.4.3.6 Test Configurator through O1 or EMS Interface - -- Must be able to interface with the O1 (if available) or EMS interface of the O-DU DUT -- Must be able to setup test scenarios and coordinate the entities in the TED to perform the required test scenarios - -## 3.4.4 UC-Plane O-DU Test Scenarios - -### 3.4.4.1 UC-Plane O-DU Scenario Class NR testing Generic (NRG) - -The purpose of the tests in this clause are to ensure that the O-DU DUT supports the mandatory open front haul features of the specification as defined in the O-RAN CUS Specification [2], Table 10.2-1. - -#### 3.4.4.1.1 UC-Plane O-DU Scenario Class Base CAT-A O-RU - -##### A. Test Description and Applicability - -This test is MANDATORY. - -The purpose of this test is to ensure that the O-DU can meet the most basic requirements of the O-RAN fronthaul to support connecting with a CAT-A O-RU with no beamforming and 16-bit fixed point IQ format. - -##### B. Test Entrance Criteria - -The O-DU DUT must be provisioned to connect with a CAT-A O-RU for 5G New Radio and be able to synchronize with the O-RU emulator of the TED. The O-DU DUT could use any of the NR profiles for CAT-A O-RU as specified in the Fronthaul Interoperability Test Specification [25] in Annex A.2 (except using 16-bit fixed point IQ format), or any other suitable profile that satisfies the test scenario. - -### C. Test Methodology - -#### 1. Initial Conditions - -Configure the O-DU DUT such that it is ready to accept a UE connection through its interfaces with the appropriate entities in the TED. Configure the O-RU Emulator to be a CAT-A O-RU with no beamforming and 16-bit fixed point IQ format. - -#### 2. Procedure - -- i.* Instruct the UE Emulator to initiate a connection with the O-DU DUT through the O-RU emulator -- ii.* Initiate data transmission on both the downlink and uplink -- iii.* Log and analyse the open front haul data stream between the O-DU DUT and O-RU Emulator including used Section Types and section extensions - -### D. Test Requirement (expected result) - -1. Non-zero data throughput in both uplink and downlink is observed -2. Log of Section Types and section extensions successfully used - -## 3.4.4.1.2 UC-Plane O-DU Scenario Class Base CAT-B O-RU - -### A. Test Description and Applicability - -This test is **MANDATORY**. - -The purpose of this test is to ensure that the O-DU can meet the most basic requirements of the O-RAN fronthaul to support connecting with a CAT-B O-RU with predefined-beam beamforming and 16-bit fixed point IQ format. - -### B. Test Entrance Criteria - -The O-DU DUT must be provisioned to connect with a CAT-B O-RU for 5G New Radio and be able to synchronize with the O-RU emulator of the TED. The O-DU DUT could use any of the NR profiles for a CAT-B O-RU as specified in the Fronthaul Interoperability Test Specification [25], e.g. Annex A.2 (except using 16-bit fixed point IQ format), or any other suitable profile that satisfies the test scenario. - -### C. Test Methodology - -#### a. Initial Conditions - -Configure the O-DU DUT such that it is ready to accept a UE connection through its interfaces with the appropriate entities in the TED. Configure the O-RU Emulator to be a CAT-B O-RU with predefined-beam beamforming and 16-bit fixed point IQ format. - -#### b. Procedure - -- i.* Instruct the UE Emulator to initiate a connection with the O-DU DUT through the O-RU emulator -- ii.* Initiate data transmission on both the downlink and uplink -- iii.* Log and analyse the open front haul data stream between the O-DU DUT and O-RU Emulator including used Section Types and section extensions - -### D. Test Requirement (expected result) - -1. Non-zero data throughput in both uplink and downlink is observed -2. Log of Section Types and section extensions successfully used - -## 3.4.4.2 UC-Plane O-DU Scenario Class Beamforming (BFM) - -This clause describes beamforming conformance tests for O-RAN fronthaul interface on the O-DU. The tests do not aim to test the O-DU beamforming performance or general capabilities. The conformance tests are designed to - -validate that the O-DU correctly describes the Beamforming methods via C-plane messages according to the O-RAN Fronthaul interface spec. The tests are configured following the outline in the clause 2.2 description of the TED. - -As noted earlier in clause 2.2, the O-DU is assumed to be a commercial product that may support a limited set of configurations. Therefore, these beamforming tests will present a suggested method for evaluating protocol conformance. The tester may choose other configurations which also clearly evaluate the conformance of the O-DU to the same protocol syntax and semantics. - -#### 3.4.4.2.1 UC-Plane O-DU Scenario Class Beamforming 3GPP – Predefined-beam Beamforming - -##### **A. Test Description and Applicability** - -This test is **MANDATORY**. - -The purpose of this test is to validate the basic operation of the O-DU DUT when configured to use predefined-beams in an O-RU. - -##### **B. Test Entrance Criteria** - -The O-DU DUT is provisioned to connect with an O-RU for 5G New Radio and be able to synchronize to a common sync source with the O-RU emulator of the TED. The O-DU DUT could use any of the NR BF profiles for O-RU as specified in the Fronthaul Interoperability Test Specification [25] in Annex A.2 (except using 16-bit fixed point IQ format), or any other suitable profile that satisfies the test scenario. - -The O-DU DUT exercises at least two different beams to serve at least two SS Blocks (SSBs) and beam sweeping. The two beams under test, i.e. *beam=A* and *beam=B*, can have neither a vector size of one (i.e. only contains a single beam weight value) nor have identical beam weight values (i.e. no beamforming). Additionally, O-DU DUT cannot assign beamId=0x0000 (i.e. no beamforming) to any of the two beams when sending beamforming information (beamId) to the O-RU emulator. The O-DU might retrieve a list of O-RU beam capabilities to be able to determine what beamIds can be used and supported by the O-RU emulator. The O-DU DUT will use at least any two beamIds to converge beamforming information to the O-RU emulator along with the test vectors (IQ data) containing SSB. - -The O-RU emulator shall be configured to report support for predefined-beam beamforming in the M-Plane capabilities to allow the O-DU DUT to use predefined-beam beamforming. It is assumed that the O-DU can be configured in some way to force the use of predefined-beam beamforming. - -##### **C. Test Methodology** - -###### 1. Initial Conditions - -Configure the O-DU DUT such that it carries out the use of SSBs and beam sweeping through its interfaces with the appropriate entities in the TED. Configure the O-RU Emulator with predefined-beam beamforming and 16-bit fixed point IQ format. - -###### 2. Procedure - -- i. O-DU DUT starts broadcasting procedure and beam sweeping -- ii. Log and analyse the open front haul data stream between the O-DU DUT and O-RU Emulator including used Section Types and section extensions - -##### **D. Test Requirement (expected result)** - -1. Successful decoding of SSBs. -2. Log of at least two different assigned beamIds (i.e. *beamId=A* and *beamId=B*) are used and none of them are beamId=0x0000. -3. (VOID) - -### 3.4.4.2.2 UC-Plane O-DU Scenario Class Beamforming 3GPP – Weight-based Beamforming - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY. - -The purpose of this test is to ensure that the O-DU can meet the most basic requirements of the O-RAN fronthaul to support connecting with an O-RU emulator with weight-based beamforming. This test exercises the beamId field found in the C-plane section descriptions as well as section extension = 1 to converge beamforming information to the O-RU emulator of TED. - -#### B. Test Entrance Criteria - -The O-DU DUT must be provisioned to connect with an O-RU for 5G New Radio and is synchronized with the O-RU emulator of the TED. The O-DU DUT could use any of the NR BF profiles for O-RU as specified in the Fronthaul Interoperability Test Specification [25] in Annex A.2 (except using 16-bit fixed point IQ format), or any other suitable profile that satisfies the test scenario. - -The O-DU must exercise at least two different DL beams. In matrix form, the column dimension of the beam weights, as defined in Section Extension Type 1 defined in the O-RAN CUS Specification [2] clause 7.7.1., corresponds to the number of beamIds, and the row dimension to the number of TRXs of the O-RU emulator. The number of beamIds must be greater than or equal to 2. Additionally, O-DU DUT cannot assign beamId=0x0000 (i.e. no beamforming) to any of the two beams when sending beamforming information to the O-RU emulator. - -The O-DU might retrieve a list of O-RU beam capabilities to be able to generate beam weight vectors (i.e. columns of the beam weight matrix) supported by the O-RU emulator. The O-DU DUT will use at least two beam weight vectors to convey beamforming information to the O-RU emulator along with the test vectors (IQ data). - -The O-RU emulator must be configured to report support for weight-based beamforming in the M-Plane capabilities to allow the O-DU DUT to use weight-based beamforming. It is assumed that the O-DU can be configured in some way to force the use of dynamic weight-based beamforming. - -#### C. Test Methodology - -##### a. Initial Conditions - -Configure the O-DU DUT such that it carries out the broadcasting of common control channels (e.g. SSB) through its interfaces with the appropriate entities in the TED. Configure the O-RU Emulator with weight-based beamforming and 16-bit fixed point IQ format. - -##### b. Procedure - -- i. O-DU DUT starts broadcasting procedure and beam sweeping -- ii. Log and analyse the open front haul data stream between the O-DU DUT and O-RU Emulator including used Section Types and section extensions - -#### D. Test Requirement (expected result) - -1. Successful decoding of one or more SSBs -2. Log of at least two different assigned beamIds (i.e. beamId=A and beamId=B) are used and none of them are beamId=0x0000 -3. Log of at least two different assigned beam weight vectors are used for beam=A and beam=B. - -### 3.4.4.2.3 UC-Plane O-DU Scenario Class Beamforming 3GPP – DMRS-BF-NEQ - -#### A. Test Description and Applicability - -This test is CONDITIONAL MANDATORY for DMRS-BF capable O-DU. - -The purpose of this test is to ensure that the O-DU can meet protocol conformance on the O-RAN fronthaul to support DMRS-based beamforming without equalization in the O-RU (DMRS-BF-NEQ). It will exercise all the mandatory C-plane section types and extensions required for supporting DMRS-BF-NEQ. An overview of the TED for DMRS-BF is provided in figure 3.4.4.2.3-1. - -The O-RU emulator simulates NEQ and EQ outputs when acting as NEQ O-RU and EQ O-RU. It is expected that NEQ O-RU and EQ O-RU outputs are different. - -![Figure 3.4.4.2.3-1 TED for DMRS-BF. The diagram shows the Test Equipment, DU (TED) connected to the O-DU DUT. The TED contains an O-RU Emulator, a Beamformer, and a UE emulator. The O-DU DUT has UE Layer 0 and UE Layer 1. The O-RU Emulator connects to the Beamformer via M Antenna Streams. The Beamformer connects to the UE emulator via UE0 Layer 0 and UE0 Layer 1. The O-RU Emulator also connects to the O-DU DUT via eAxc 0 and eAxc1.](bdd1fc345a009867e50739255be00f90_img.jpg) - -``` - -graph LR - subgraph TED [Test Equipment, DU (TED)] - ORE[O-RU Emulator] - BF[Beamformer] - UE[UE emulator] - ORE <--> |"M Antenna Streams"| BF - BF <--> |"UE0 Layer 0"| UE - BF <--> |"UE0 Layer 1"| UE - end - ODU[O-DU DUT] - ODU --> |"eAxc 0"| ORE - ODU --> |"eAxc1"| ORE - ORE --> |"UE Layer 0"| ODU - ORE --> |"UE Layer 1"| ODU - -``` - -Figure 3.4.4.2.3-1 TED for DMRS-BF. The diagram shows the Test Equipment, DU (TED) connected to the O-DU DUT. The TED contains an O-RU Emulator, a Beamformer, and a UE emulator. The O-DU DUT has UE Layer 0 and UE Layer 1. The O-RU Emulator connects to the Beamformer via M Antenna Streams. The Beamformer connects to the UE emulator via UE0 Layer 0 and UE0 Layer 1. The O-RU Emulator also connects to the O-DU DUT via eAxc 0 and eAxc1. - -Figure 3.4.4.2.3-1 TED for DMRS-BF - -#### B. Test Entrance Criteria - -The O-DU DUT is provisioned to connect with an O-RU emulator for 5G New Radio and is synchronized with the O-RU emulator of the TED. A single UE emulator which can support at least 2 layers is attached to or included within the O-RU emulator. The O-RU emulator supports DMRS-BF-NEQ in the M-Plane capabilities and establishes conditions that will increase the likelihood of the O-DU DUT choosing to enter DMRS-BF mode (e.g. high UL data rate). - -When operating in DMRS-BF mode, the O-DU DUT will convey user group scheduling and multiple port configuration to the O-RU emulator using ST5 and SE10 respectively, where SE10 uses beamGroupType 10b or 11b. The O-DU DUT will convey the DMRS configuration using SE24. The O-RU emulator validates the DMRS configuration sent by the O-DU DUT against the DMRS configuration of the UE emulator. - -If configured, the O-DU DUT may send an ST11 RRM measurement request to the O-RU emulator and receive an ST10 measurement report in response from the O-RU emulator. The O-RU emulator captures and logs the ST10 packets that it sends out in response to the SE24 M-Plane configuration that it receives. - -#### C. Test Methodology - -##### a. Initial Conditions - -Configure the O-DU DUT such that it is ready to accept a UE connection through its interfaces with the appropriate entities in the TED -Configure the O-RU emulator for DMRS-BF-NEQ - -**b. Procedure** - -- i. Start the O-DU DUT and O-RU emulator M-plane setup (advertise and configure) -- ii. O-DU DUT sends C-plane data request with scheduling decision for each user group (ST5) along with DMRS (SE24) and multiple port configuration (SE10) -- iii. O-RU emulator receives PUSCH from UE emulator and sends U-Plane data to the O-DU -- iv. Log and analyse the open fronthaul data stream between the O-DU DUT and O-RU emulator including the used section types and section extensions - -**D. Test Requirement (expected result)** - -1. O-DU DUT successfully decodes PUSCH transmissions (PN9 data payload), verified by NDI bit toggle and no retransmission requests to the UE emulator attached to the O-RU emulator -2. O-RU emulator reports valid DMRS configurations from the O-DU DUT that match the UE emulator configurations -3. All the logged C-plane messages and measurement reports are captured and valid - -### 3.4.4.2.4 UC-Plane O-DU Scenario Class Beamforming 3GPP – DMRS-BF-EQ - -**A. Test Description and Applicability** - -This test is CONDITIONAL MANDATORY for DMRS-BF capable O-DU. - -The purpose of this test is to ensure that the O-DU can meet protocol conformance on the O-RAN fronthaul to support DMRS-based beamforming with equalization in the O-RU (DMRS-BF-EQ). It will exercise all the mandatory C-plane section types and extensions required for supporting DMRS-BF-EQ. An overview of the TED for DMRS-BF is provided in figure 3.4.4.2.3-1. - -The O-RU emulator simulates NEQ and EQ outputs when acting as NEQ O-RU and EQ O-RU. It is expected that NEQ O-RU and EQ O-RU outputs are different. - -**B. Test Entrance Criteria** - -The O-DU DUT is provisioned to connect with an O-RU emulator for 5G New Radio and is synchronized with the O-RU emulator of the TED. A single UE emulator which can support at least 2 layers is attached to or included within the O-RU emulator. The O-RU emulator reports support for both DMRS-BF-EQ in the M-Plane capabilities and establishes conditions that will increase the likelihood of the O-DU DUT choosing to enter DMRS-BF mode (e.g. high UL data rate). - -The O-DU DUT will convey user group scheduling and multiple port configuration to the O-RU emulator using ST5 and SE10 respectively, where SE10 uses beamGroupType 10b or 11b. The O-DU DUT will convey the DMRS configuration and any RRM requests (excluding unallocated IPN) using SE24. The O-RU validates the DMRS configuration sent by the O-DU DUT against the DMRS configuration of the UE emulator. - -If configured, the O-DU DUT sends ST11 RRM measurement requests to the O-RU emulator and receives ST10 measurement reports in response. The O-RU captures and logs the ST10 packets that it sends out in response to the SE24 or ST11 packets that it receives. - -The O-DU DUT can request either SINR reports or port reduced DMRS; as such, the O-RU logs and captures either the SINR data sent via ST9 or the port reduced DMRS data. The O-DU DUT will receive ST9 SINR reports as per the configured M-plane cadence. The tester will select channel conditions for the TED that ensure successful decoding of PUSCH transmissions at the O-DU DUT. - -## C. Test Methodology - -### a. Initial Conditions - -Configure the O-DU DUT such that it is ready to accept a UE connection through its interfaces with the appropriate entities in the TED - -Configure the O-RU emulator for DMRS-BF-EQ - -### b. Procedure - -- i. Start the O-DU DUT and O-RU emulator M-plane setup (advertise and configure) -- ii. O-DU DUT sends C-plane data request with scheduling decision for each user group (ST5) along with DMRS and RRM measurement requests (SE24) and multiple port configuration (SE10) -- iii. O-DU DUT triggers unallocated IPN RRM requests via ST11, if configured, and correctly receives ST10 and ST9 responses -- iv. O-RU emulator receives PUSCH from UE emulator and sends U-Plane data to the O-DU -- v. Log and analyse the open fronthaul data stream between the O-DU DUT and O-RU emulator including the used section types and section extensions - -## D. Test Requirement (expected result) - -1. O-DU DUT successfully decodes PUSCH transmissions (PN9 data payload) from the UE emulator, verified by NDI bit toggle and no retransmission requests to the UE attached to the O-RU emulator. -2. O-RU emulator reports valid DMRS configurations from the O-DU DUT that match the UE configurations. -3. All the logged C-plane messages and measurement reports are captured and valid. - -### 3.4.4.3 UC-Plane O-DU Scenario Class Compression (CMP) - -This clause validates the correct implementation of mandatory and conditional mandatory IQ data compression formats in [2]. - -It applies to the following O-RAN CUS Specification [2]. - -- Clause 7.4 for layout of C-Plane message, in particular Section Type 1 -- Clause 7.5.2.10 for applicability of “udCompHdr” and “reserved” fields -- Clause 8.3.2 for layout of DL/UL Data -- Clause 8.3.3.13/14/15 for applicability of udCompParam - -The objective is to test the mandatory and conditional mandatory compression capabilities of a O-RAN compliant O-DU. These include: - -- Mandatory: Static Fixed-Point Uncompressed 16-bit IQ -- Conditional Mandatory: Static Block floating point compression – 9, 12 & 14-bit mantissa - -#### Overview of Compression Test Methodology - -For both downlink and uplink testing, the test will validate that non-zero user data throughput is achieved in both directions and that the section headers for CU plane in the downlink are consistent with the specification [2]. - -To maximise coverage on the compressed IQ mantissa value, the test frame will use the highest possible modulation supported by the O-DU. The preferred value is 256 QAM modulation for downlink and uplink. - -**Presence/Absence of CU-Plane Header measurements (downlink only):** Validate that the fields udCompHdr, and “reserved” are absent in downlink U-Plane. For Static Block Floating Point Compression, only udCompParam is present in downlink U-Plane. For downlink C-Plane, validate that the udCompHdr is set to 0. - -### 3.4.4.3.1 Static Format Fixed-Point (FP) Uncompressed - -#### A. Test Description and Applicability - -This test is MANDATORY. - -The purpose of this test is to: - -- Validate correct format of Control Plane Section Header - - udCompHdr set to 0x0 -- Validate that in the data section header, udCompHdr, “reserved”, and udCompParam fields are not present -- Validate correct encoding/decoding of IQ data - - Fixed point 16 Bit IQ data format - - Uplink / downlink - -The purpose of this test is to ensure that the O-DU can meet the mandatory requirements of the O-RAN fronthaul to support compression. - -#### B. Test Entrance Criteria - -The O-DU DUT must be provisioned to connect with an O-RU for 5G New Radio and be able to synchronize with the O-RU emulator or real O-RU. The O-DU DUT could use any of the NR profiles as specified in the Fronthaul Interoperability Test Specification [25], Annex A.2. Compression is further adjusted as described below. - -#### C. Test Methodology - -##### a. Initial Conditions - -- Configure the O-DU DUT such that it is ready to accept a UE connection through its interfaces with the appropriate entities in the TED. -- Configure O-DU for 16-bit fixed point IQ format. -- Configure the O-RU Emulator with 16-bit fixed point IQ format. - -##### b. Procedure - -1. Instruct the UE Emulator or UE to initiate a connection with the O-DU DUT through the O-RU emulator or O-RU -2. Initiate data transmission on both the downlink and uplink. -3. Record the total throughput in each direction for comparison in additional test cases. -4. Note any errors reported by the O-RU emulator for downlink compression. Alternatively, using the log information from the O-RU emulator, analyse the open front haul data stream between the O-DU DUT and O-RU Emulator to confirm proper transmission of the downlink U-Plane data with 16-bit fixed point format. -5. Analyse any C-Plane errors reported by the O-RU emulator related to compression or sample the log file to validate compression header information. - -#### D. Test Requirement (expected result) - -1. Validate that the Control Plane Section Header has udCompHdr set to 0x0 -2. Validate that udCompHdr, “reserved” and udCompParam fields are absent in Downlink Data Section Header -3. Non-zero data throughput in both uplink and downlink is observed -4. There are no errors in step 4 of the procedure - -### 3.4.4.3.2 UC-Plane O-DU Scenario Class Compression (CMP) Static Format Block Floating Point - -#### A. Test Description and Applicability - -This test is **CONDITIONALMANDATORY** and shall be performed if the emulated O-RU or real O-RU supports this compression format. -The static format test scenario for Block Floating Point Format will verify DL and UL correct encoding of IQ information for 3 supported bit widths: 9, 14 or 12 bits. - -The purpose of this test is to: - -- Validate correct format of Control Plane Section Header - - udCompHdr set to 0x00 -- Validate that in the data section header, udCompHdr and “reserved” fields are not present -- Validate correct encoding/decoding of IQ data - - 9 bits IQ Data - - 14 bits IQ Data - - 12 bits IQ Data - - Uplink / downlink - -#### B. Test Entrance Criteria - -The O-DU DUT must be provisioned to connect with an O-RU for 5G New Radio and be able to synchronize with the O-RU emulator or real O-RU. The O-DU DUT could use any of the NR profiles as specified in the Fronthaul Interoperability Test Specification [25], Annex A.2. Compression is further adjusted as described below. - -#### C. Test Methodology - -##### a. Initial Conditions - -- Configure the O-DU DUT such that it is ready to accept a UE connection through its interfaces with the appropriate entities in the TED. - -##### b. Procedure - -1. Configure O-DU for 14-bit Static Format BFP Compression. -2. Configure the O-RU for 14-bit Static Format BFP Compression. -3. Instruct the UE Emulator or UE to initiate a connection with the O-DU DUT through the O-RU emulator or O-RU -4. Initiate data transmission on both the downlink and uplink. -5. Record the total throughput in each direction and validate that user data throughput is non-zero. -6. Note any errors reported by the O-RU emulator for downlink compression. Alternatively, using the log information from the O-RU emulator, analyse the open front haul data stream between the O-DU DUT and O-RU Emulator to confirm proper transmission of the downlink U-Plane data. -7. Analyse any C-Plane errors reported by the O-RU emulator related to compression or sample the log file to validate compression header information. -8. Repeat steps 1- 7 with the configuration set to 9 bit Static Format Block Floating Point -9. Repeat steps 1- 7 with the configuration set to 12 bit Static Format Block Floating Point - -#### D. Test Requirement (expected result) - -1. Step 5 in each repetition meet the expected results -2. Steps 6 and 7 for each repetition do not show any errors - -### 3.4.4.4 UC-Plane O-DU Scenario Class Delay Management (DLM) - -#### 3.4.4.4.1 Delay Management On-time arrival - -##### A. Test Description and Applicability - -This test is MANDATORY. - -The purpose of this test is to ensure that the O-DU can meet basic requirements of the O-RAN fronthaul to support configured delay management parameters for transmissions from the O-DU to the O-RU for the C-Plane and U-Plane protocol. To exercise both the downlink O-DU adherence to the configured delay management and the required counters on the O-DU related to delay management in the uplink, a UE in connected mode is required. - -##### B. Test Entrance Criteria - -The O-DU DUT must be provisioned to connect with an O-RU for 5G New Radio and be able to synchronize with the O-RU emulator or real O-RU. The O-DU DUT could use any of the NR profiles as specified in the Fronthaul Interoperability Test Specification [25], Annex A.2. The counters defined in the O-RAN CUS Specification [2], Table 9.1-1, for on-time reception on the O-DU must be supported and accessible. - -##### C. Test Methodology - -###### a. Initial Conditions - -Configure the O-DU DUT such that it is ready to accept a UE connection through its interfaces with the appropriate entities in the TED. Configure the O-RU emulator per the parameters of the chosen IOT profile. Using the M-Plane or other manual methods, configure the delay parameters in the O-RAN CUS Specification [2], Table 4.4.3-1 to achieve proper timing on the O-RU emulator. - -###### b. Procedure - -1. Clear the O-DU delay management receive counters or note the current value. -2. Instruct the UE Emulator to initiate a connection with the O-DU DUT through the O-RU emulator -3. Initiate data transmission on both the downlink and uplink -4. Validate that the O-DU adheres to the downlink delay management parameters using the O-RU emulator receive counters for on-time, early and late arrival for the C-Plane and the U-Plane for the O-RU emulator. Those counters for each configured eAxC might also be validated if supported by the O-RU emulator. -5. Validate that the O-DU receive counters for on-time arrival for the C-Plane and the U-Plane for the O-RU emulator increment as expected and that early and late counters remain unchanged (e.g. 0 if the test started with these counters at 0). - -##### D. Test Requirement (expected result) - -1. O-DU receive (uplink) counters (RX\_ON\_TIME, RX\_EARLY, RX\_LATE, RX\_TOTAL) for the O-RU emulator for the U-Plane are observed. Only RX\_ON\_TIME and RX\_TOTAL should show non-zero values or changed values if the counters could not be cleared. -2. O-RU emulator (downlink) receives counters report that only on-time PDUs are received. No early or late PDUs are received. - -#### 3.4.4.4.2 Delay Management Early Arrival and Late Arrival - -##### A. Test Description and Applicability - -This test is MANDATORY. - -The purpose of this test is to validate the operation of the O-DU delay management receive counters for the C-Plane and U-Plane protocol. To exercise these counters, a UE in connected mode is required. - -## B. Test Entrance Criteria - -The O-DU DUT must be provisioned to connect with an O-RU for 5G New Radio and be able to synchronize with the O-RU emulator or real O-RU. The O-DU DUT could use any of the NR profiles as specified in the Fronthaul Interoperability Test Specification [25], Annex A.2. The counters in the O-RAN CUS Specification [2], Table 9.1-1 for on-time reception on the O-DU must be supported and accessible. - -## C. Test Methodology - -### a. Initial Conditions - -Configure the O-DU DUT such that it is ready to accept a UE connection through its interfaces with the appropriate entities in the TED. Configure the O-RU emulator per the parameters of the chosen IOT profile. Using the M-Plane or other manual methods, for the appropriate step below, configure the delay parameters in the O-RAN CUS Specification [2], Table 4.4.3-1 to force early or late PDU transmission of the U-Plane PDUs to the O-DU. - -### b. Procedure - -1. Clear the O-DU delay management receive counters or note the current value -2. Force the O-RU emulator to send U-Plane PDUs to the O-DU “early” such that they arrive at the O-DU outside the receive window. -3. Instruct the UE Emulator to initiate a connection with the O-DU DUT through the O-RU emulator. -4. Initiate data transmission on both the downlink and uplink -5. Validate that the O-DU counters for RX\_EARLY for U-Plane for the O-RU emulator are incrementing. -6. Clear the O-DU delay management receive counters or note the current value -7. Force the O-RU emulator to send U-Plane PDUs to the O-DU “late” such that they arrive at the O-DU outside the receive window. -8. Instruct the UE Emulator to initiate a connection with the O-DU DUT through the O-RU emulator. -9. Initiate data transmission on both the downlink and uplink -10. Validate that the O-DU counters for RX\_LATE for U-Plane for the O-RU emulator are incrementing. - -## D. Test Requirement (expected result) - -Steps 5 and 10 show the expected counter(s) incremented - -# 3.5 Shared-Cell Test Scenarios - -This clause describes conformance test scenarios for devices supporting Shared-Cell as defined in [2]. In the present document, only devices supporting the Fronthaul Multiplexor (FHM) mode are considered. - -## 3.5.1 FHM mode Tests - -In this set of tests for Shared Cell, the device under test (DUT) is FHM and is connected to Test Equipment Fronthaul Multiplexor (TEM) with multiple O-RU capabilities as described in clause 2.3. - -### 3.5.1.1 FHM M-Plane Tests - -FHM uses the same architecture model defined in clause 5.1.2 of [3]. Therefore, many tests described in this clause are references to previously defined tests in clause 3.1. Table 3.5.1.1-1 summarize all M-Plane tests for the FHM. The table also indicates if the specific test case is a reference to existing tests defined in clause 3.1 and if the target NETCONF server is on the FHM or on a south node. - -**Table 3.5.1.1-1 List of FHM M-plane Test Scenarios and Status.** - -| Test Clause | Clause 3.1 Test Case | FHM Test Requirement Status | M-Plane Server | Test Description | -|-------------|----------------------|-----------------------------|----------------|---------------------------------------------------------------------------| -| 3.5.1.1.1 | 3.1.1.1 | CONDITIONAL MANDATORY | FHM | Transport and Handshake in IPv4/SSH Environment (positive case) | -| 3.5.1.1.2 | 3.1.1.2 | CONDITIONAL MANDATORY | FHM | Transport and Handshake in IPv4/SSH Environment (negative case) | -| 3.5.1.1.3 | 3.1.1.3 | CONDITIONAL MANDATORY | FHM | Transport and Handshake in IPv6/SSH Environment (positive case) | -| 3.5.1.1.4 | 3.1.1.4 | CONDITIONAL MANDATORY | FHM | Transport and Handshake in IPv6/SSH Environment (negative case) | -| 3.5.1.1.5 | 3.1.1.5 | CONDITIONAL MANDATORY | FHM | Transport and Handshake in IPv4/TLS Environment (positive case) | -| 3.5.1.1.6 | 3.1.1.6 | CONDITIONAL MANDATORY | FHM | Transport and Handshake in IPv4/TLS Environment (negative case) | -| 3.5.1.1.7 | 3.1.1.7 | CONDITIONAL MANDATORY | FHM | Transport and Handshake in IPv6/TLS Environment (positive case) | -| 3.5.1.1.8 | 3.1.1.8 | CONDITIONAL MANDATORY | FHM | Transport and Handshake in IPv6/TLS Environment (negative case) | -| 3.5.1.1.9 | N/A | MANDATORY | FHM | Retrieval of FHM Information (positive case) | -| 3.5.1.1.10 | N/A | MANDATORY | FHM | Retrieval of FHM Information (negative case) | -| 3.5.1.1.11 | N/A | MANDATORY | FHM | U-Plane Configuration and Shared Cell Configuration | -| 3.5.1.1.12 | N/A | MANDATORY | South-Node | MPlane Passthrough Uplane Configuration for South Node RU(positive case) | -| 3.5.1.1.13 | N/A | MANDATORY | South-Node | MPlane Passthrough Uplane Configuration for South Node RU (negative case) | -| 3.5.1.1.14 | N/A | MANDATORY | FHM | Performance Management | -| 3.5.1.1.15 | N/A | MANDATORY | FHM | Delay Management | -| 3.5.1.1.16 | 3.1.6.1 | MANDATORY | FHM | Software Update (positive case) | -| 3.5.1.1.17 | 3.1.6.2 | MANDATORY | FHM | Software Update (negative case) | -| 3.5.1.1.18 | 3.1.7.1 | MANDATORY | FHM | Software Activation without Reset | -| 3.5.1.1.19 | 3.1.7.2 | MANDATORY | FHM | Supplemental Reset after Software Activation | -| 3.5.1.1.20 | N/A | MANDATORY | FHM | File Management Operation: Upload | -| 3.5.1.1.21 | N/A | MANDATORY | FHM | File Management Operation: Retrieve the list | -| 3.5.1.1.22 | N/A | MANDATORY | FHM | File Management Operation: Download | -| 3.5.1.1.23 | 3.1.2 | MANDATORY | FHM | Subscription to Notifications | -| 3.5.1.1.24 | 3.1.5.1 | MANDATORY | FHM | O-RU Alarm Notification Generation | -| 3.5.1.1.25 | 3.1.5.2 | MANDATORY | FHM | Retrieval of Active Alarm List | - -| Test Clause | Clause 3.1 Test Case | FHM Test Requirement Status | M-Plane Server | Test Description | -|----------------|----------------------|-----------------------------|----------------|-----------------------------------------------------------| -| 3.5.1.1.2
6 | 3.1.3.1 | CONDITIONAL MANDATORY | FHM | M-Plane Connection Supervision (positive case) | -| 3.5.1.1.2
7 | 3.1.3.2 | CONDITIONAL MANDATORY | FHM | M-Plane Connection Supervision (negative case) | -| 3.5.1.1.2
8 | 3.1.8.1 | CONDITIONAL MANDATORY | FHM | Sudo on Hybrid M-plane Architecture (positive case) | -| 3.5.1.1.2
9 | 3.1.8.2 | CONDITIONAL MANDATORY | FHM | Access Control Sudo (negative case) | -| 3.5.1.1.3
0 | 3.1.8.3 | CONDITIONAL MANDATORY | FHM | Access Control NMS (negative case) | -| 3.5.1.1.3
1 | 3.1.8.4 | CONDITIONAL MANDATORY | FHM | Access Control FM-PM (negative case) | -| 3.5.1.1.3
2 | 3.1.8.5 | CONDITIONAL MANDATORY | FHM | Access Control SWM (negative case) | -| 3.5.1.1.3
3 | 3.1.8.6 | CONDITIONAL MANDATORY | FHM | Sudo on Hierarchical M-plane architecture (positive case) | -| 3.5.1.1.3
4 | 3.1.8.7 | CONDITIONAL MANDATORY | FHM | Access Control SMO (negative case) | -| 3.5.1.1.3
5 | 3.1.8.8 | CONDITIONAL MANDATORY | FHM | Access Control Hybrid-ODU (negative case) | - -### 3.5.1.1.1 Transport and Handshake in IPv4/SSH Environment (positive case) - -This test is CONDITIONAL MANDATORY for a FHM that declares support for IPv4 and SSH. Refer to clause 3.1.1.1 for the test procedure. - -### 3.5.1.1.2 Transport and Handshake in IPv4/SSH Environment (negative case) - -This test is CONDITIONAL MANDATORY for a FHM that declares support for IPv4 and SSH. Refer to clause 3.1.1.2 for the test procedure. - -### 3.5.1.1.3 Transport and Handshake in IPv6/SSH Environment (positive case) - -This test is CONDITIONAL MANDATORY for a FHM that declares support for IPv6 and SSH. Refer to clause 3.1.1.3 for the test procedure. - -### 3.5.1.1.4 Transport and Handshake in IPv6/SSH Environment (negative case) - -This test is CONDITIONAL MANDATORY for a FHM that declares support for IPv6 and SSH. Refer to clause 3.1.1.4 for the test procedure. - -### 3.5.1.1.5 Transport and Handshake in IPv4/TLS Environment (positive case) - -This test is CONDITIONAL MANDATORY for a FHM that declares support for IPv4 and TLS. Refer to clause 3.1.1.5 for the test procedure. - -### 3.5.1.1.6 Transport and Handshake in IPv4/TLS Environment (negative case) - -This test is CONDITIONAL MANDATORY for a FHM that declares support for IPv4 and TLS. Refer to clause 3.1.1.6 for the test procedure. - -### 3.5.1.1.7 Transport and Handshake in IPv6/TLS Environment (positive case) - -This test is CONDITIONAL MANDATORY for a FHM that declares support for IPv6 and TLS. Refer to clause 3.1.1.7 for the test procedure. - -### 3.5.1.1.8 Transport and Handshake in IPv6/TLS Environment (negative case) - -This test is CONDITIONAL MANDATORY for a FHM that declares support for IPv6 and TLS. Refer to clause 3.1.1.8 for the test procedure. - -### 3.5.1.1.9 Retrieval of FHM Information (positive case) - -#### A. Test-Description and Applicability - -This scenario is MANDATORY for FHM tests. - -This scenario corresponds to the following clause in [3]: - -- 17.6.3 Start-up and Installation - -#### B. Test-Entrance Criteria - -The minimum functions of the TEM described in clause 2.3 that support validation of the M-Plane are operational, configured and connected to the FHM. - -#### C. Test-Methodology - -##### a. Initial Condition - -The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed - -##### b. Procedure - -1. The TEM NETCONF Client triggers on ietf-yang-library towards FHM. - -``` - - - - - -``` - -2. The FHM NETCONF Server responds with where contains all the yang modules supported by FHM NETCONF server - -``` - - - - - Lib - - o-ran-shared-cell - 2021-12-01 - urn:o-ran:shared-cell:1.0 - FHM - - - - - -``` - -``` - -
- - - - - -``` - -3. The TEM NETCONF Client triggers on shared-cell-module towards the FHM NETCONF - -``` - - - - - - - 300 - 300 - 300 - - 11 - 11 - - - - - -``` - -#### D. Test Requirement (expected result) - -1. The fetched yang library contains o-ran-shared-cell module indicating that O-RU supports copy and combine function and FHM feature is defined -2. The shared-cell-module-cap container is present in the response from O-RU NETCONF server containing delay management parameters t-copy, t-combine, ta3-prime-max-upper-range, max-number-node-copy-and-combine, max-number-eaxcid-copy, max-number-eaxcid-combine, compression-method-supported. - -### 3.5.1.1.10 Retrieval of FHM Information (negative case) - -#### A. Test-Description and Applicability - -This scenario is MANDATORY for FHM tests. Since FHM doesn't have the capability for transmission and reception of radio signals, Some YANG models are not applicable for FHM, including: - -1. o-ran-ald module -2. o-ran-ald-port module -3. o-ran-laa-operations module -4. o-ran-laa module -5. o-ran-module-cap module -6. o-ran-beamforming module -7. o-ran-uplane-conf module - -The testcases corresponding to these 7 YANG models can be skipped as it is not applicable to FHM. The to the mentioned module will return rpc-error. One example for module-cap is discussed in this testcase. - -This scenario corresponds to the following clause in [3]: - -- 17.6.3 Start-up and Installation - -## B. Test-Entrance Criteria - -The minimum functions of the TEM described in clause 2.3 that support validation of the M-Plane are operational, configured and connected to the FHM. - -## C. Test-Methodology - -### a. Initial Condition - -The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed - -### b. Procedure - -1. The TEM NETCONF Client triggers on urn:o-ran:module-cap towards FHM. - -``` - - - report-all - -``` - -2. The FHM NETCONF Server throws error where contains all the yang modules supported by FHM NETCONF server - -``` - - - Module-not-supported - Module not supported - error - - -``` - -## D. Test Requirement (expected result) - -1. Test Step 2 is performed successfully. - -### 3.5.1.1.11 U-Plane Configuration and Shared Cell Configuration - -#### A. Test-Description and Applicability - -This scenario is MANDATORY for FHM tests. - -This scenario corresponds to the following clause in [3]: - -- 17.6.4 U-Plane Configuration for FHM - -#### B. Test-Entrance Criteria - -The minimum functions of the TEM described in clause 2.3 that support validation of the M-Plane are operational, configured and connected to the FHM. - -#### C. Test-Methodology - -##### a. Initial Conditions - -The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed. - -##### b. Procedure - -1. The TEM NETCONF Client configures the FHM NETCONF Server with a vlan-id for the C-Plane and U-Plane interfaces on the north interface and south interface (with same vlan id value). - -2. The TEM NETCONF Client configures a transport-flow in the FHM north node processing element: a combination of VLAN identity, North node MAC address and FHM MAC address. - -``` - - - - - - merge - - - SHARED-CELL-ETH-INTERFACE - - XXX_north_node_FHM_processing-element01 - - XXX_if_xyz_vlan1 - - A0:CE:C8:17:7A:41 - 1 - 0a:00:27:00:00:09 - - - - - - - -``` - -3. The TEM NETCONF Client configures a transport-flow in the FHM south node processing element: a combination of VLAN identity, South MAC address and FHM MAC address. This step shall be repeated for as any south node O-RUs in the setup with same M-Plane configuration. - -``` - - - - - - merge - - - SHARED-CELL-ETH-INTERFACE - - XXX_south_node_FHM_processing-element01 - - XXX_if_xyz_vlan1 - - A0:CE:C8:17:7A:41 - 1 - 0a:00:27:00:01:10 - - - - - - - -``` - -4. The TEM NETCONF Client configures the FHM with the unique eexc-id value in the shared-cell-copy and shared-cell-combine module of FHM. - -``` - - - - - - - merge - - - - - XXX_shared_copy_set01 - XXX_north_node_FHM_processing-element01 - - XXX_south_node_FHM_processing-element01 - - - 1 - - 0 - 0 - - 1 - - - - - XXX_shared_combine_set01 - XXX_north_node_FHM_processing-element00 - XXX_south_node_FHM_processing-element01 - - - 2 - - - STATIC - 14 - 4 - - 0 - 0 - 0 - - - - - - - - -``` - -5. Enable CU plane monitoring - -**D. Test Requirement (expected result)** - -1. The FHM NETCONF Server confirms the operations for the above transactions -2. Verify that carrier is activated in southern node TEM NETCONF server and C/U plane data flows have commenced. - -### 3.5.1.1.12 M-Plane Passthrough U-Plane Configuration for South Node RU (positive case) - -#### A. Test-Description and Applicability - -This scenario is CONDITIONAL MANDATORY for FHM tests with M-Plane Passthrough. - -#### B. Test-Entrance Criteria - -The minimum functions of the TEM described in clause 2.3 that support validation of the M-Plane are operational, configured and connected to the South Node - -#### C. Test-Methodology - -##### a. Initial Conditions - -The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed - -##### b. Procedure - -1. The TEM Netconf-Server (which act as O-RU) will initiate the test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) and completed successfully. -2. The TEM Netconf Client initiates the test procedure described in clause 3.1.10.1 towards the TEM Netconf Server and completed successfully. - -#### D. Test Requirement (expected result) - -Test Scenario step 2 is performed successfully. - -### 3.5.1.1.13 M-Plane Passthrough U-Plane Configuration for South Node RU (negative case) - -#### A. Test-Description and Applicability - -This scenario is CONDITIONAL MANDATORY for FHM tests with M-Plane Passthrough. - -#### B. Test-Entrance Criteria - -The minimum functions of the TEM described in clause 2.3 that support validation of the M-Plane are operational, configured and connected to the South Node - -#### C. Test-Methodology - -##### a. Initial Conditions - -The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed - -##### b. Procedure - -1. The TEM Netconf-Server (which act as ORU) will initiate the test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) and completed successfully. -2. The TEM Netconf Client initiates the test procedure described in clause 3.1.10.2 towards the TEM Netconf Server and completed successfully. - -#### D. Test Requirement (expected result) - -Test Scenario step 2 is performed successfully. - -### 3.5.1.1.14 Performance Management - -#### A. Test-Description and Applicability - -This scenario is MANDATORY for FHM tests. - -This clause defines specific part of Performance Measurement of shared cell - -This scenario corresponds to the following clause in [3]: - -- 17.4 Performance Management - -#### B. Test-Entrance Criteria - -The minimum functions of the TEM described in clause 2.3 that support validation of the M-Plane are operational, configured and connected to the FHM - -#### C. Test-Methodology - -##### a. Initial Conditions - -The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed - -##### b. Procedure - -1. The TEM NETCONF Client establishes a connection with the FHM NETCONF Server -2. The TEM NETCONF Client sends edit config for transceiver-measurement-object and epe-stats-object. - -``` - - - - - - merge - - - False - TRUE - - sftp://oranuser@192.168.56.1:22/log - - oranuser - - - 300 - 300 - 1200 - - TX_BIAS_COUNT - true - MAXIMUM - MINIMUM - FIRST - LATEST - PORT_NUMBER - LOG_10 - 2 - - - RX_ON_TIME - true - - - - - -``` - -``` - - RU - COUNT - - - - - - -``` - -3. The FHM sends notification message - -``` - - - YYYY-MM-DDTHH:mm:ss - - - TEMPERATURE - YYYY-MM-DDTHH:mm:ss - YYYY-MM-DDTHH:mm:ss - - PORT1 - - 1 - - - - 3 - - - - - - TEMPERATURE - YYYY-MM-DDTHH:mm:ss - YYYY-MM-DDTHH:mm:ss - - O-RAN-HARDWARE - 24 - 42 - - - - - - -``` - -#### D. Test Requirement (expected result) - -The rpc is sent successfully with required parameters and validated via TEM. - -### 3.5.1.1.15 Delay Management - -#### A. Test-Description and Applicability - -This scenario is MANDATORY for FHM tests. - -This test verifies the delay operation between O-DU and furthest (southern-most) O-RU. - -This scenario corresponds to the following clause in [3]: - -- 17.5 Delay Management - -#### B. Test-Entrance Criteria - -The minimum functions of the TEM described in clause 2.3 that support validation of the M-Plane are operational, configured and connected to the FHM - -## C. Test-Methodology - -### a. Initial Conditions - -The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed - -### b. Procedure - -1. The TEM NETCONF Client establishes a connection with the FHM NETCONF Server -2. The TEM NETCONF Client retrieve delay profile using o-ran-delay-management.yang from TEM NETCONF Server. -3. The TEM NETCONF Client send a with ta3-prime-max value of shared-cell-combine container. - -``` - - - - - merge - - - - XXX_shared_combine_set01 - 300 - - - -``` - -4. The FHM will respond with the OK reply to the TEM NETCONF Client. - -``` - - - -``` - -## D. Test Requirement (expected result) - -Test Scenario step 4 is performed successfully. - -### 3.5.1.1.16 Software Update (positive case) - -This test is MANDATORY for an FHM. Refer to clause 3.1.6.1 for the test procedure. - -### 3.5.1.1.17 Software Update (negative case) - -This test is MANDATORY for an FHM. Refer to clause 3.1.6.2 for the test procedure. - -### 3.5.1.1.18 Software Activation without Reset - -This test is MANDATORY for an FHM. Refer to clause 3.1.7.1 for the test procedure. - -### 3.5.1.1.19 Supplemental Reset after Software Activation - -This test is MANDATORY for an FHM. Refer to clause 3.1.7.2 for the test procedure. - -### 3.5.1.1.20 File Management Operation: Upload - -#### A. Test-Description and Applicability - -This scenario is MANDATORY for FHM tests. - -This test verifies the file management operation of the FHM. - -This scenario corresponds to the following clause in [3]: - -- 12.3 File Management Operation: Upload - -#### B. Test-Entrance Criteria - -The functions of the TEM described in clause 2.3 that support validation of the M-Plane are operational, configured and connected to the FHM - -#### C. Test-Methodology - -##### a. Initial Conditions - -The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed. - -##### b. Procedure - -1. The TEM NETCONF Client establishes a connection with the FHM NETCONF Server -2. The TEM NETCONF Client uploads a file using the o-ran-file-management YANG model from the TEM NETCONF Server. -3. The TEM NETCONF Client send towards NETCONF Server - -``` - - - latest.log - sftp://guest@192.168.2.2:22/ - - guest - - - -``` - -4. The FHM will respond with the status reply to the TEM NETCONF Client. - -``` - - SUCCESS - -``` - -5. The NETCONF Server sends notification. - -``` - - YYYY-MM-DDTHH:mm:ss - - latest.log - sftp://guest@192.168.2.2:22/ - SUCCESS - - -``` - -#### D. Test Requirement (expected result) - -Test Scenario step 4 is performed successfully. - -### 3.5.1.1.21 File Management Operation: Retrieve the list - -#### A. Test-Description and Applicability - -This scenario is MANDATORY for FHM tests. - -This test verifies the file management operation of the FHM. - -This scenario corresponds to the following clause in [3]: - -- 12.4 File Management Operation: Retrieve the list - -## B. Test-Entrance Criteria - -The minimum functions of the TEM described in clause 2.3 that support validation of the M-Plane are operational, configured and connected to the FHM - -## C. Test-Methodology - -### a. Initial Conditions - -The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed. - -### b. Procedure - -1. The TEM NETCONF Client establishes a connection with the FHM NETCONF Server -2. The TEM NETCONF Client retrieves the file from TEM NETCONF Server. One or multiple 6 files' information can be retrieved by one retrieve file list operation (use of wildcard is allowed). - -``` - - - - * - - -``` - -3. The FHM will respond with the status reply to the TEM NETCONF Client whether the TEM NETCONF Server accepts the retrieve-file-list request or rejects due to some reason is replied. If rejected, the human readable reject reason is also replied - -``` - - SUCCESS - -``` - -## D. Test Requirement (expected result) - -Test Scenario step 4 is performed successfully. - -## 3.5.1.1.22 File Management Operation: Download - -### A. Test-Description and Applicability - -This scenario is MANDATORY for FHM tests. - -This test verifies the file management operation of the FHM. - -This scenario corresponds to the following clause in [3]: - -- 12.5 File Management Operation: Download - -## B. Test-Entrance Criteria - -The minimum functions of the TEM described in clause 2.3 that support validation of the M-Plane are operational, configured and connected to the FHM - -## C. Test-Methodology - -### a. Initial Conditions - -The test procedure described in clause 3.1.1.1 (IPv4/SSH) or 3.1.1.3 (IPv6/SSH) or 3.1.1.5 (IPv4/TLS) or 3.1.1.7 (IPv6/TLS) is successfully completed - -### b. Procedure - -1. The TEM NETCONF Client establishes a connection with the FHM NETCONF Server - -2. The TEM NETCONF Client sends file download request to TEM NETCONF Server. - -``` - - - . - sftp://guest@192.168.2.2:22/mplane_user_Guide.docx - guest - - -``` - -3. The FHM will respond with the status reply to the TEM NETCONF Client - -``` - - SUCCESS - -``` - -4. The NETCONF Server sends notification. - -``` - - YYYY-MM-DDTHH:mm:ss - - latest.log - sftp://guest@192.168.2.2:22/ - SUCCESS - - -``` - -#### D. Test Requirement (expected result) - -Test Scenario step 4 is performed successfully. - -### 3.5.1.1.23 Subscription to Notifications - -This test is MANDATORY for an FHM. Refer to clause 3.1.2 for the test procedure. - -### 3.5.1.1.24 O-RU Alarm Notification Generation - -This test is MANDATORY for an FHM. Refer to clause 3.1.5.1 for the test procedure. - -### 3.5.1.1.25 Retrieval of Active Alarm List - -This test is MANDATORY for an FHM. Refer to clause 3.1.5.1 for the test procedure - -### 3.5.1.1.26 M-Plane Connection Supervision (positive case) - -This test is CONDITIONAL MANDATORY for an FHM. Refer to clause 3.1.3.1 for the test procedure. - -### 3.5.1.1.27 M-Plane Connection Supervision (negative case) - -This test is CONDITIONAL MANDATORY for an FHM. Refer to clause 3.1.3.2 for the test procedure. - -### 3.5.1.1.28 Sudo on Hybrid M-plane Architecture (positive case) - -This test is CONDITIONAL MANDATORY for an FHM. Refer to clause 3.1.8.1 for the test procedure. - -### 3.5.1.1.29 Access Control Sudo (negative case) - -This test is CONDITIONAL MANDATORY for an FHM. Refer to clause 3.1.8.2 for the test procedure. - -### 3.5.1.1.30 Access Control NMS (negative case) - -This test is CONDITIONAL MANDATORY for an FHM. Refer to clause 3.1.8.3 for the test procedure. - -### 3.5.1.1.31 Access Control FM-PM (negative case) - -This test is CONDITIONAL MANDATORY for an FHM. Refer to clause 3.1.8.4 for the test procedure. - -### 3.5.1.1.32 Access Control SWM (negative case) - -This test is CONDITIONAL MANDATORY for an FHM. Refer to clause 3.1.8.5 for the test procedure. - -### 3.5.1.1.33 Sudo on Hierarchical M-plane architecture (positive case) - -This test is CONDITIONAL MANDATORY for an FHM. Refer to clause 3.1.8.6 for the test procedure. - -### 3.5.1.1.34 Access Control SMO (negative case) - -This test is CONDITIONAL MANDATORY for an FHM. Refer to clause 3.1.8.7 for the test procedure. - -### 3.5.1.1.35 Access Control Hybrid-ODU (negative case) - -This test is CONDITIONAL MANDATORY for an FHM. Refer to clause 3.1.8.8 for the test procedure. - -## 3.5.1.2 FHM UC-Plane Tests - -### 3.5.1.2.1 UC-Plane FHM Scenario Class Base 3GPP DL Same Cell Scenario - -#### A. Test Description and Applicability - -The test is MANDATORY for FHM. - -The purpose of the test is to ensure the FHM can meet the requirement of the DL copy function to retrieve eCPRI messages coming from the north-node as payload of Ethernet frames, copy them (the entire eCPRI message including eCPRI header and eCPRI payload) without any modifications as payload into Ethernet frames and send them towards all of the south-nodes that are configured. - -The FHM is connected to TEM emulating at least two O-RUs as south-nodes that operate as same cell. Each south-node emulated O-RUs must have at least one UE attached to it. - -Using the standard TDD or FDD test frame described in clause 3.2.1.1.3 or 3.2.1.1.1 for FR1 or 3.2.1.1.4 for FR2, the O-DU emulator (i.e. north bound interface of the FHM described in clause 2.3) generates downlink C-Plane and U-Plane messages that require the FHM to transmit towards the south-nodes. This configuration corresponds to stock data section A in all symbols that do not contain PDCCH channels. The remainder of this test description - -assumes the FR1 TDD FHM. While the FHM DUT is generally agnostic to the Frequency Range and other similar radio frame configuration, the FHM tests can be conducted using any of the above test frames. - -#### B. Test Entrance Criteria - -South-node O-RU must support the default parameters in clause 3.2.1.1.3 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz Bandwidth as described by NR-FR1-TM1.1 in downlink direction, appropriate SSB signal shall also be transmitted for UEs in emulated O-RUs to synchronize and decode PDSCH properly. If the O-RU does not support this bandwidth, another 3GPP FRC can be selected. In the test frame, all PDSCH data is set to all zeros. It will be for 5G New Radio only. - -#### C. Test Methodology - -##### a. Initial Conditions - -Configure the south-node emulated O-RUs which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Configure UEs in each emulated O-RUs with appropriate parameters that are needed to allow them to synch and demodulate the downlink signal. - -The O-DU emulator has determined the topology (adjacency relationships) of O-RUs for the shared cell through topology discovery procedure. Then configure the FHM with appropriate shared-cell-copy-uplane-config parameters using M-Plane commands. - -##### b. Procedure - -Build an appropriate IQ signal describing the signal described above in clause 3.2.1.1.3 in the CUSM emulator. Use the CUSM emulator control interface to build the appropriate C-Plane messages that describe the signal. Every symbol other than the ones used in the test shall either be allocated with user data or left unallocated (empty). If allocated with user data, they be described by either a single or multiple sections (DL-SCH that are used for the test, DMRS and DCI) using Section Type 1 messages. No Section Type zero messages will be used for this test. Encapsulate the IQ data in U-Plane messages for downlink slots only. Play those messages to the FHM respecting timing windows described in clause 3.2.1.1.3. Repeat the entire frame the number of times required for emulated UE to synch to the SSB and allow it to demodulate and decode the test frame. - -#### D. Test Requirement (expected result) - -1. The signal measured from the UEs in each south-node emulated O-RU shall satisfy a basic 3GPP signal performance requirement for this radio category (i.e. EVM). -2. The test frame received in downlink direction by the UEs shall be the same as the signal described above. If it contains all the same PRB assignments and all zero data, the test passes. - -### 3.5.1.2.2 UC-Plane FHM Scenario Class Base 3GPP UL - -#### A. Test Description and Applicability - -The test is MANDATORY for FHM. - -The purpose of the test is to ensure the FHM can meet the requirement for the UL combine function to combine IQ data corresponding to the same radio resource element from each south-node O-RU to eCPRI messages for UL U-Plane towards north-node O-DU. - -The FHM will be connected to TEM emulating at least two O-RUs as south-nodes that operate as same cell. Each south-node emulated O-RUs must have at least two UEs attached to it. - -Using the standard TDD or FDD test frame described in clause 3.2.1.1.3, the O-DU emulator (i.e. O-RAN interface of the TER described in clause 2.1) will generate uplink C-Plane that require the FHM to transmit towards the south-nodes. Appropriate SSB signal shall also be transmitted in downlink U plane for UEs supported by emulated O-RUs to synchronize and transmit uplink signals properly. - -For each O-RU, it needs to transmit 2 UL signals in same slot, one PUSCH signal from one UE and one PUCCH signal from the other UE. The definition of the signal can be found from Table 3.5.1.2-1 and Table 3.5.1.2-2 below, the value from both tables can be referred to ETSI TS 138.141 clause 8, Table 8.2.1.4.2-2 and Table 8.3.2.1.4.2-2 with slight changes in accommodation for the purpose of this test. The reason for using PUSCH and PUCCH signals in this test is to exercise UL combine function with different scenarios, i.e. PUSCH from each O-RU does not overlap while PUCCH overlaps. - -### 3.5.1.2-1 PUSCH Parameters for HFM UL Test. - -| PUSCH Parameters | | Value for O-RU 1 | Value for O-RU 2 | | | -|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------|-------------------------------------------------------------------------|------------------|--|--| -| Transform precoding | | Disabled | | | | -| C-RNTI | | 0 | 1 | | | -| Default TDD UL-DL pattern (Note 1) | | 30 kHz SCS:
3D1S1U, S=10D:2G:2U
30 kHz SCS:
7D1S2U, S=6D:4G:4U | | | | -| HARQ | Maximum number of HARQ transmissions | 4 | | | | -| | RV sequence | 0, 2, 3, 1 | | | | -| DM-RS | DM-RS configuration type | 1 | | | | -| | DM-RS duration | single-symbol DM-RS | | | | -| | Additional DM-RS position | pos1 | | | | -| | Number of DM-RS CDM group(s) without data | 2 | | | | -| | Ratio of PUSCH EPRE to DM-RS EPRE | -3 dB | | | | -| | DM-RS port(s) | {0}, {0, 1} | | | | -| | DM-RS sequence generation | $N_{ID}^0=0, n_{SCID}=0$ | | | | -| Time domain resource assignment | PUSCH mapping type | A, B | | | | -| | Start symbol | 0 | | | | -| | Allocation length | 14 | | | | -| Frequency domain resource assignment | RB assignment | 1 - 51 | 52 - 102 | | | -| | Frequency hopping | Disabled | | | | -| TPMI index for 2Tx two-layer spatial multiplexing transmission | | 0 | | | | -| Code block group based PUSCH transmission | | Disabled | | | | -| NOTE 1: The same requirements are applicable to FDD and TDD with different UL-DL patterns. | | | | | | -| NOTE 2: If other combinations of numerology and bandwidth are required to be tested, appropriate PUSCH PRB length and location needs to be selected with the following principles: a) PUSCH from O-RU1 and O-RU2 has the same PRB length, which is between 1/5 and 1/4 of the total bandwidth. b) PUSCH from O-RU1 starts from PRB#1, PUSCH from O-RU1 and O-RU2 needs to be adjacent. | | | | | | - -### 3.5.1.2-1 PUCCH Parameters for HFM UL Test. - -| PUCCH Parameters | Value for O-RU1 | Value for O-RU2 | -|---------------------------------------------------------|-----------------|---------------------------------------| -| C-RNTI | 2 | 3 | -| PUCCH format | | 1 | -| Number of information bits | | 2 | -| Number of PRBs | | 1 | -| Number of symbols | | 14 | -| First PRB prior to frequency hopping | | 0 | -| Intra-slot frequency hopping | | Enabled | -| First PRB after frequency hopping | | The largest PRB index - (nrofPRBs -1) | -| Group and sequence hopping | | Neither | -| Hopping ID | | 0 | -| Initial cyclic shift | | 0 | -| First symbol | | 0 | -| Index of orthogonal cover code ( timeDomainOCC ) | 0 | 1 | - -In this case, PUSCH from each O-RU are using different PRB resource in same slot while PUCCH from each O-RU are using same PRB resource but with different OCC. - -#### B. Test Entrance Criteria - -The south-node O-RU must support the default parameters in clause 3.2.1.1.3 of this document. The test numerology will be 30 kHz subcarrier spacing and 100 MHz. If the O-RU does not support this bandwidth another 3GPP FRC can be selected. In the test frame, all PUSCH data is set to all zeros. It will be for 5G New Radio only. - -#### C. Test Methodology - -##### a. Initial Conditions - -Configure the south-node emulated O-RUs which includes collecting O-RU capabilities, configuring the O-RU for operation using M-Plane commands, and synchronizing the O-RU using G.8275.1. Configure UEs in each emulated O-RUs with appropriate parameters that needed to allow them to synch and transmit uplink signal. - -The O-DU emulator has determined the topology (adjacency relationships) of O-RUs for the shared cell through topology discovery procedure. Then configure the FHM with appropriate shared-cell-combine-uplane-config parameters using M-Plane commands. - -##### b. Procedure - -- Build appropriate test signal for each south-node O-RU as described above in the signal source of the TER. -- Use the O-DU emulator control interface to build the appropriate C-Plane messages for downlink SSB and describe the uplink signal. For uplink, every symbol shall be described by either one or two sections (UL-SCH) using Section Type 1 messages. No Section Type zero messages will be used for this test. -- Play the C plane messages to the O-RU respecting timing windows described in clause 3.2.1.1.1. -- Upon synchronizing to SSB, UE in each emulated O-RU shall transmit uplink signal defined above. -- Repeat the entire frame the number of times required to synch the DUT, allow it to create and send the U-plane messages to the O-DU and for the O-DU to demodulate, decode and extract the payload. - -#### D. Test Requirement (expected result) - -- The test frame received by the TEM/O-DU shall be the same as the signal described above from two O-RUs. -- Both PUSCH and PUCCH from 2 south-node O-RUs can be decoded correctly from TEM/O-DU U-Plane extracted IQ with expected payload. - -## Annex (informative): Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2020.06.02 | 01.00 | Final Version 01.00 | -| 2020.10.25 | 01.00.01 | Integrate VIA-0001, KEY-0003, VIA-0002, KEY-0008 | -| 2020.10.25 | 01.00.02 | Integrate, KEY-0006 | -| 2020.11.01 | 01.00.03 | Integrate KEY-0011, KEY-0004, KEY-0005, SPL-0001 | -| 2020.11.02 | 01.00.04 | Integrate KEY-0007, KEY-0009, VIA.RDS-0001 | -| 2020.11.06 | 02.00 | Address all review comments and finalize release | -| 2021.02.04 | 02.00.06 | Include approved CRs versions 02.00.01-02.00.06: INT-0009, FJT-0002, RNS-0001, VIA-0003 KEY-0010, KEY-0013, DCM-0009, KEY-0014, NEC-0007, NEC-0008, VIA-0004, KEY-0015, KEY-0016, KEY-RNS-0019, KEY-0017, KEY-0018 and add new test cases to the clause 1.2.4 Test Requirement Status table | -| 2021.03.01 | 02.00.07 | Fix missing changes 2 and 3 of CR DCM-0009 and included FJT-0003, NEC-0008. | -| 2021.03.05 | 03.00.00 | All comments addressed and finalized | -| 2021.05.31 | 03.00.01 | Included approved CRs: FJT-0004, XLX-0001, KEY-0019, KEY-0020, KEY-0021, KEY-0022, KEY-0023, KEY-0025 | -| 2021.06.23 | 03.00.02 | Included approved CRs: KEY-0024, KEY-0026, KEY-0027, KEY-0028, NVI-0101, RNS-0002, RNS-0003, RNS-0004, RNS-0005 | -| 2021.07.11 | 04.00.00 | Final version 4 incorporating all comments received after version 03.00.02 | -| 2022.03.08 | 04.00.01 | Includes initial typographical and similar corrections from the review spreadsheet and approved CRs RNS-0006, FJT-0005, RNS-0008, RNS-0009, KEY-0029 KEY-0030 NEC-0013, FJT-0008, KEY-0031, KEY-0032, FJT-0009, FJT-0010, KEY-0030, KEY-0033 | -| 2022.03.15 | 04.00.02 | Includes RNS-0010, FJT-0010 v4, KEY.CMC-0034, comments register items 1-33 | -| 2022.03.20 | 04.00.03 | Includes changes to address comments from FJT and NOK from Comments-Register-CONF-v05.00-r6.xlsx | -| 2022.03.24 | 05.00 | Include comments up to and including comment 56 in the comments register version 8. | -| 2022.07.14 | 05.00.01 | Include CRs KEY-CMCC-0002, KEY-0037, VIA-0005, CAL-0001, VIA-0006, VIA-0007, CAL-0003 and comments register items 1-6 | -| 2022.07.14 | 05.00.02 | Include CRs FJT-0013, NEC-0015, EC-0016, NEC-0017, FJ-0014, RNS-0011, RNS-0012 and comments register items 7-18 | -| 2022.07.15 | 05.00.03 | Include comments register items 19-60 | -| 2022.07.19 | 06.00 | Include comments 61-63 and update to version 06.00 | -| 2022.10.30 | 06.00.01 | Include CRs CAL-0002-r4, KEY-CUC-0001-r4, FJT-0015-r2, FJT-0016, FJT-0017, KEY-0039 | -| 2022.11.03 | 06.00.02 | Include CRs KEY-0040, FJT-0018, VIA-0011 and all comments | -| 2022.11.12 | 07.00 | Final draft review comments included | -| 2023.02.26 | 07.00.01 | Include CRs FJT-0019, FJT-0020, CAL-0004, KEY-0041, KEY-0042, KEY-0043, CAL-0005, KEY-0044, APOP-0003, APOP-0004, FJT-0021 | -| 2023.03.05 | 07.00.02 | KEY-0044-R2, Review comments 1-42 | -| 2023.03.12 | 08.00 | Final review comments | -| 2023.07.13 | 08.00.01 | Include CRs KEY-0045, KEY-0046, KEY-0047, CAL-0006, NOK-0136, | - -| Date | Revision | Description | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------| -| | | KEY-0048, FJT-0027, FJT-0028, FJT-0029, FJT-0030, CAL-0007, CAL-0008 | -| 2023.07.17 | 08.00.02 | Update with comments spreadsheet | -| 2023.07.19 | 09.00 | Update with comments spreadsheet version 6 | -| 2024.03.12 | 09.00.01 | Include CRs NVD-0001, KEY-0049 | -| 2024.03.22 | 10.00 | Updated with all comments from v09.00.01 | -| 2024.06.25 | 10.01 | Include CR NOK-0174 | -| 2024.06.26 | 10.02 | Include CR CAL-0014, ERI-0114, NEC-0027 | -| 2024.06.27 | 10.03 | Include CR NEC-0028, NEC-0029, NEC-0030, NEC-0031, NEC-0032, NEC-0033, NEC-0034, NEC-0035 | -| 2024.07.02 | 10.04 | Update with comments spreadsheet version v1.0 | -| 2024.07.03 | 10.05 | Include CR NOK-0175 | -| 2024.07.12 | 10.06 | Update with comments spreadsheet version v5.0 | -| 2024.07.18 | 10.07 | Update with comments spreadsheet version v8.0 | -| 2024.07.19 | 10.08 | Fix some references in the 3.3.3 chapter. | -| 2024.07.19 | 11.00 | Final version for publication. | -| 2024.11.6 | 11.01 | Include CR NEC-0037, NEC-0038, QCM-0087, KEY-0051, KEY-0055, CAL-0020 | -| 2024.11.11 | 11.02 | Include CR CAL-0021, NOK-0194, KEY-0053, VIA-0012, VIA-0013 | -| 2024.11.12 | 11.03 | Include CR NEC-0040, NEC-0041, NEC-0042, NEC-0043, NEC-0044, NEC-0045, SAM-126, NOK-0197 | -| 2024.11.13 | 11.04 | Include CR NEC-0039, XNET-0001, NOK-0201, ERI-0131 | -| 2024.11.14 | 11.05 | Minor text format edits, changes to list type in D. Sections, changed word "Note :" to "NOTE :". | -| 2024.11.20 | 11.00.06 | Apply editorial changes in the NOK-NEC-Comments-Register-CONF-v11.05_v2.0. Also include CR KEY-0056, SAM-0127, NOK-0198. | -| 2024.11.22 | 11.00.07 | Apply editorial changes in the NOK-NEC-ERI-Comments-Register-CONF-v11.00.06_v3.0. | -| 2024.11.26 | 11.00.08 | Apply editorial changes in the NOK-NEC-ERI-SAM-Comments-Register-CONF-v11.00.06_v4.0. | -| 2024.11.27 | 11.00.09 | Applied latest editorial comments from NOK-NEC-ERI-SAM-Comments-Register-CONF-v11.00.08_v6.0 | -| 2024.11.29 | 12.00 | Final version for publication | -| 2025.02.20 | 12.00.01 | Include CR CAL-0019, CAL-0023, KEY-0057 | -| 2025.03.03 | 12.00.02 | Include CR RMI.AO-0003, DCM.AO-0024, SBKK.AO-0001, KEY-0058, KEY-0059. | -| 2025.03.14 | 12.00.03 | Apply editorial changes in the Comments-Register-CONF-v12.00.03 | -| 2025.03.21 | 13.00 | Final version for publication | -| 2025.06.18 | 13.00.01 | Include CR ERI-0175, NEC-0051, NEC-0052, KEY-0060. | -| 2025.07.01 | 13.00.02 | Include CR KEY-0061 and ERI comments from spreadsheet. | -| 2025.07.02 | 13.00.03 | Include CR KEY-0074 and KEY comments from spreadsheet. | -| 2025.07.07 | 13.00.04 | Include NEC and NOK comments from spreadsheet. | -| 2025.07.09 | 13.00.05 | Include latest editorial comments from spreadsheet. | -| 2025.07.10 | 13.00.06 | Include CR ERI-0184 and ERI-0189. Created new chapter 3.1a for M-Plane Measurements for O-DU. Changed Table 1.2.4-1 accordingly. | -| 2025.07.14 | 13.00.07 | Include latest editorial comments from spreadsheet. | -| 2025.07.15 | 13.00.08 | Included latest editorial comments from the final spreadsheet. | -| 2025.07.18 | 14.00 | Final version for publication. | -| 2025.08.14 | 14.01 | Fixed multiple cross-referencing issues ("clause 0" referencing) across the document. Removed clause 3.2.1.1.2 reference in test case 3.2.3.7.1.B. | - -| Date | Revision | Description | -|------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2025.09.10 | 14.02 | Fixed multiple additional cross-reference issues (“0” references) across the document. Replaced some American English wording for British English equivalent wording to meet drafting rules. Corrected some editorial issues such as extra spaces and extra lines. | -| 2025.11.04 | 14.02.01 | Include CR SAM-0151, KEY-0062, KEY-0064, KEY-0065, KEY-0067, KEY-0071 and KEY-0075. | -| 2025.11.07 | 14.02.02 | Include CR KEY-0068, KEY-0069, KEY-0070, KEY-0072, KEY-0073, KEY-0076 and ERI-0217. | -| 2025.11.17 | 14.02.03 | Included editorial comments from spreadsheet. | -| 2025.11.22 | 15.00 | Final version for publication. Included latest editorial comments from the final spreadsheet | \ No newline at end of file diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/01f07707259cb0193a962c1eaf725055_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/01f07707259cb0193a962c1eaf725055_img.jpg deleted file mode 100644 index 64cd6f3816b3d42b10f3bfce8b153248a26bc16e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/01f07707259cb0193a962c1eaf725055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4149a6ce3340eaa90307b1e3489b55f368c00380a949981c357e84dc390ce9fc -size 74493 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/027a00a3a1cf9593b2532c75b1d05728_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/027a00a3a1cf9593b2532c75b1d05728_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/027a00a3a1cf9593b2532c75b1d05728_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/04455de8d97f1961965642865418543f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/04455de8d97f1961965642865418543f_img.jpg deleted file mode 100644 index 5e18ec3fef61444037c2252999fd0835507e2d40..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/04455de8d97f1961965642865418543f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:deb60d6b5ac53a43bfa0e0aec22d2150dcab6f0f560620fc79e9f23eec0fd965 -size 25125 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0510a00adb87ba5f37618c27f528afc5_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0510a00adb87ba5f37618c27f528afc5_img.jpg deleted file mode 100644 index 0e93504438785bdeee05f27e526176d448035d9c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0510a00adb87ba5f37618c27f528afc5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c4dd92f3b822cc86defb406515b8cdeaab70516bf6bcb18cc43bb70df662b6cd -size 90222 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/059b7281a8b8f88ac86672e2ef822d3e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/059b7281a8b8f88ac86672e2ef822d3e_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/059b7281a8b8f88ac86672e2ef822d3e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/07bae2d456e460215a6b74db040d9b6c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/07bae2d456e460215a6b74db040d9b6c_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/07bae2d456e460215a6b74db040d9b6c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/080a7af02bc47cf21ebfae4e0be39745_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/080a7af02bc47cf21ebfae4e0be39745_img.jpg deleted file mode 100644 index 462a905a98840a87ae93c4837ea59bf228056961..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/080a7af02bc47cf21ebfae4e0be39745_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:819e13f43ff0535d589bdd660cf5afebc118950ebe3b8d3aa48745355c61bc26 -size 28264 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/09032127b49c74c07fdc4e0d5275a115_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/09032127b49c74c07fdc4e0d5275a115_img.jpg deleted file mode 100644 index 944fdccfc52993ebe91c91406d059725091c29d5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/09032127b49c74c07fdc4e0d5275a115_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6cb4d53fe2d2f1e0b1f41eb2671ae57c1cc4708d065eb2fc4f08736872b02788 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/09e41da697fcaa1b598908c21f7452ca_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/09e41da697fcaa1b598908c21f7452ca_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/09e41da697fcaa1b598908c21f7452ca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0a278c1194f7b78236442a1c85cf70b5_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0a278c1194f7b78236442a1c85cf70b5_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0a278c1194f7b78236442a1c85cf70b5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0b477f992e8c9df386a990881e6c218c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0b477f992e8c9df386a990881e6c218c_img.jpg deleted file mode 100644 index d4b547a22f93d7799576c1a65ea0f3f19d9afbbc..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0b477f992e8c9df386a990881e6c218c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8c94bfaf088c98ccfdc4f9272323ada7f302eba949ec8089b8f568e0b288a33e -size 20827 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0c586365841f26a3d201eeefdfe261b8_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0c586365841f26a3d201eeefdfe261b8_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0c586365841f26a3d201eeefdfe261b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0c6aeaf9973cd03cff19dd3f0ca1314e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0c6aeaf9973cd03cff19dd3f0ca1314e_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0c6aeaf9973cd03cff19dd3f0ca1314e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0ca6bc14d1677d1c63937578865b0e21_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0ca6bc14d1677d1c63937578865b0e21_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0ca6bc14d1677d1c63937578865b0e21_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0d2f92b554f88f7f5b03f23faec94dba_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0d2f92b554f88f7f5b03f23faec94dba_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0d2f92b554f88f7f5b03f23faec94dba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0e2a8954ad6cb6a913374fe51484fce5_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0e2a8954ad6cb6a913374fe51484fce5_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0e2a8954ad6cb6a913374fe51484fce5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0e50822d868aa19c8aa37bfb98002a25_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0e50822d868aa19c8aa37bfb98002a25_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0e50822d868aa19c8aa37bfb98002a25_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0e611959485447591664307862231ffd_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0e611959485447591664307862231ffd_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0e611959485447591664307862231ffd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0f4dfcf85c881a0574c955f34ef40f02_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0f4dfcf85c881a0574c955f34ef40f02_img.jpg deleted file mode 100644 index e58c7802a19ff359c4af68f0f91643b0be56dba4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/0f4dfcf85c881a0574c955f34ef40f02_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7707080093e1142af970dbf69167f292256d50dfdc63c393010b472954016846 -size 49771 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/10f4e3a2f3c016555ee12a5b556ba834_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/10f4e3a2f3c016555ee12a5b556ba834_img.jpg deleted file mode 100644 index 3227117578ba71d0361eb75b50edb39387b6dca4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/10f4e3a2f3c016555ee12a5b556ba834_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:67b4dd251dbd0a21a8ee0fde3e56ffe7ad31fcea48474061fc17babdbd8d4298 -size 159401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/116a62c978d6a7d1b7830c1ea13e2993_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/116a62c978d6a7d1b7830c1ea13e2993_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/116a62c978d6a7d1b7830c1ea13e2993_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/118d1daec0d1a3e2a27924fe38e6d3cc_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/118d1daec0d1a3e2a27924fe38e6d3cc_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/118d1daec0d1a3e2a27924fe38e6d3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/11b3d3cc56f71f80a268a31bd42103e9_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/11b3d3cc56f71f80a268a31bd42103e9_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/11b3d3cc56f71f80a268a31bd42103e9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/11cfbe1171c471cd8b2d0604ad5185f2_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/11cfbe1171c471cd8b2d0604ad5185f2_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/11cfbe1171c471cd8b2d0604ad5185f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/125aeb04c622d45656bd18af1b29af75_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/125aeb04c622d45656bd18af1b29af75_img.jpg deleted file mode 100644 index e5a0f090e91eb8e44a4bc85d94a2d5407d72b87d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/125aeb04c622d45656bd18af1b29af75_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bc2ceb46f7addbc53732a1d5dfff775142c64a2b31221f42ac9fb7fbcaf0fdf3 -size 99425 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg deleted file mode 100644 index 437c7cf78526b71e63f7c07b5a0fab087cbd4555..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:66f3213da7377a9eb4bdd467bcecf2c4890129f9dbe81b9220a8e62c45d15e4c -size 4511 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/134b1f0d617209a0436333b9ab6b1ce8_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/134b1f0d617209a0436333b9ab6b1ce8_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/134b1f0d617209a0436333b9ab6b1ce8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/13f3038de69b724b315694e535b7be7a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/13f3038de69b724b315694e535b7be7a_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/13f3038de69b724b315694e535b7be7a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/13fbd97d3a93abb4c723c50966c8cd14_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/13fbd97d3a93abb4c723c50966c8cd14_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/13fbd97d3a93abb4c723c50966c8cd14_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/14af2781d0bd19b98b10672b74daaca2_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/14af2781d0bd19b98b10672b74daaca2_img.jpg deleted file mode 100644 index 387f910e3d6540dbc2c60d2f5f13208447fc334d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/14af2781d0bd19b98b10672b74daaca2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:91b7a56751812d17ca4f521314d9e9d553a3fb5886776879e5344cf140ab3401 -size 70291 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1501d7bdc363cc07e88b48c8fa7d17c4_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1501d7bdc363cc07e88b48c8fa7d17c4_img.jpg deleted file mode 100644 index 36b7238b90b21e359850cd590f4f9993dc0a5ec9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1501d7bdc363cc07e88b48c8fa7d17c4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:606de5984835dac3143f1090670f1c5614fbd853c45874d754333cdc17c7c8a7 -size 27177 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/15574508acc09ee822bfbd5ad0954c5a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/15574508acc09ee822bfbd5ad0954c5a_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/15574508acc09ee822bfbd5ad0954c5a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/16b08981199f29066db206d1e31e6e47_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/16b08981199f29066db206d1e31e6e47_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/16b08981199f29066db206d1e31e6e47_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/173cabf0f07c5a4c069664ded9e6cf85_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/173cabf0f07c5a4c069664ded9e6cf85_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/173cabf0f07c5a4c069664ded9e6cf85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/185fe49c575cd3bd4aa61943ed41ba37_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/185fe49c575cd3bd4aa61943ed41ba37_img.jpg deleted file mode 100644 index c7e0f56b6ba32b6075d2b8a2adcdc5d73a8a9580..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/185fe49c575cd3bd4aa61943ed41ba37_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:cde79407ab7b406c63d0f3033445733bc4b707b05b2823cbbd77987cf1585a84 -size 113419 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1869d74dac030a42b1b3860ebfb7d0c4_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1869d74dac030a42b1b3860ebfb7d0c4_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1869d74dac030a42b1b3860ebfb7d0c4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/189ac86054d2d468016d2091f22dfc5d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/189ac86054d2d468016d2091f22dfc5d_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/189ac86054d2d468016d2091f22dfc5d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/19882a9fbfbe25c951b10a507c786951_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/19882a9fbfbe25c951b10a507c786951_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/19882a9fbfbe25c951b10a507c786951_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1a3b66996d112dc11f6fc9e9e696728b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1a3b66996d112dc11f6fc9e9e696728b_img.jpg deleted file mode 100644 index 19db53e44594a2969fe5a5195233ba77d985ffdc..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1a3b66996d112dc11f6fc9e9e696728b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ef66dd2e676b8085315a73a67d61215ebb1016fa47e1fb86f1ac39d7ed7ef412 -size 111362 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1b7861077e6bb3e95f508e0ceeda5b0e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1b7861077e6bb3e95f508e0ceeda5b0e_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1b7861077e6bb3e95f508e0ceeda5b0e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1baaba7a6e54e77197475726c871067d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1baf92180f2964741688e8215d7183da_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1baf92180f2964741688e8215d7183da_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1baf92180f2964741688e8215d7183da_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1caeb0a2fba40318948c5173cb6d96c7_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1caeb0a2fba40318948c5173cb6d96c7_img.jpg deleted file mode 100644 index 437c7cf78526b71e63f7c07b5a0fab087cbd4555..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1caeb0a2fba40318948c5173cb6d96c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:66f3213da7377a9eb4bdd467bcecf2c4890129f9dbe81b9220a8e62c45d15e4c -size 4511 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1da00d32e4d978dc1064b4d6b74d865c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1da00d32e4d978dc1064b4d6b74d865c_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1da00d32e4d978dc1064b4d6b74d865c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1f68bbbcc01497ed647f4e521eb440c5_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1f68bbbcc01497ed647f4e521eb440c5_img.jpg deleted file mode 100644 index 437c7cf78526b71e63f7c07b5a0fab087cbd4555..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1f68bbbcc01497ed647f4e521eb440c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:66f3213da7377a9eb4bdd467bcecf2c4890129f9dbe81b9220a8e62c45d15e4c -size 4511 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1fa646088a731bde9ff4c9af87f93d3c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1fa646088a731bde9ff4c9af87f93d3c_img.jpg deleted file mode 100644 index 5ead9405b6b28b937562d1f63a0cfe028d30566d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1fa646088a731bde9ff4c9af87f93d3c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03b98e0fb4340df8f86047c8f49ee811a11c74495cefbd2fc89d24e1c16dfcd3 -size 63250 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1ff7828d681947990fac3e7bad35dd86_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1ff7828d681947990fac3e7bad35dd86_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/1ff7828d681947990fac3e7bad35dd86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/206b1499a4b866d040aff98bd29a8d17_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/206b1499a4b866d040aff98bd29a8d17_img.jpg deleted file mode 100644 index 5aa67a38b0f5d7aa4bbf2792e48f1ff8b73d2384..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/206b1499a4b866d040aff98bd29a8d17_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b0a195fde6b6f1a02e071d2f3ff7d1f6fa0bf79fe93a1b8bf6d01e658243d489 -size 49983 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/216c2095d183f87925e91862bc15439a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/216c2095d183f87925e91862bc15439a_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/216c2095d183f87925e91862bc15439a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/21cfcb7e235dba52c53c8cf7b10f36aa_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/21cfcb7e235dba52c53c8cf7b10f36aa_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/21cfcb7e235dba52c53c8cf7b10f36aa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/226bcc7921bff55dc14cac630460ab92_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/226bcc7921bff55dc14cac630460ab92_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/226bcc7921bff55dc14cac630460ab92_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg deleted file mode 100644 index b192513298ebafb100d6d2ab432fe297788b81c1..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:04fc346c7483a681561cf8c8c80f785114e4fcd653ac8e679a31187d61393ba7 -size 4240 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/230151de787f38fa96749379eafb9f37_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/230151de787f38fa96749379eafb9f37_img.jpg deleted file mode 100644 index bebbe1baaba624f2acd3945747348849e11d3875..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/230151de787f38fa96749379eafb9f37_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6ab9aaa655079248937879a9ba2d70a77c70490aaf551953650987333ac5baf7 -size 69212 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/233a8b9743fe86cccae4bfca4aa9a0b0_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/233a8b9743fe86cccae4bfca4aa9a0b0_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/233a8b9743fe86cccae4bfca4aa9a0b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/23b110b75da6b415520918830060195e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/23b110b75da6b415520918830060195e_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/23b110b75da6b415520918830060195e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/240318eb53e18366b06354b765508a8f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/240318eb53e18366b06354b765508a8f_img.jpg deleted file mode 100644 index 269ecfbe762e9a5bba4935b3363f1e0e83facae9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/240318eb53e18366b06354b765508a8f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9e0b0946a85bd8e6b15ae34d41e4c117f82c915e797ccdc8e0e1e24c4a84cf34 -size 92444 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/24a3cc3bc7bd963ec2c4ceaf3e548457_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/24a3cc3bc7bd963ec2c4ceaf3e548457_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/24a3cc3bc7bd963ec2c4ceaf3e548457_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/24aa9e96ae01a0c590c2884c7454b7a7_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/24aa9e96ae01a0c590c2884c7454b7a7_img.jpg deleted file mode 100644 index 246ea30a93fe43b834474e2dc945b990f02e1c1a..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/24aa9e96ae01a0c590c2884c7454b7a7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5b59865414cbe4de8812096c532e27e930f2250fb5326dc85f0747142bb7f106 -size 64686 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/266ed4b8590c3bfce2d6ccf95b143242_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/266ed4b8590c3bfce2d6ccf95b143242_img.jpg deleted file mode 100644 index 4d381e3a98df1b58dead750d31c4a054aa9c2c02..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/266ed4b8590c3bfce2d6ccf95b143242_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e67681bead2455e6b8d8d18030a01b0e2171506b182f72770d3e24ea934be356 -size 4522 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/26e4d6ae09790488a51e9171a1df0357_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/26e4d6ae09790488a51e9171a1df0357_img.jpg deleted file mode 100644 index f6491945bc6692d29fedd48c723170599a1a7863..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/26e4d6ae09790488a51e9171a1df0357_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:74cb87dbfe726e881aa4ab2da4a037ff2fa17a0f0875f20883c28cce6e83c783 -size 88216 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/29100fce6dce19cea57712363976bf2c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/29100fce6dce19cea57712363976bf2c_img.jpg deleted file mode 100644 index 33214e1d7b0845ebce56a0da6cf278afc208a9eb..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/29100fce6dce19cea57712363976bf2c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d07d07fc931d3dddaecf0f15b229288dea79beb8ade91a82238c96a71784aae -size 65283 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2a185522b492253375ed16f0c515c230_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2a185522b492253375ed16f0c515c230_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2a185522b492253375ed16f0c515c230_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2b0332ac7e7e351e0ec7b1cb17d10e23_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2b0332ac7e7e351e0ec7b1cb17d10e23_img.jpg deleted file mode 100644 index 0140a67499bf70930997a1cca85f62d48d0d96c6..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2b0332ac7e7e351e0ec7b1cb17d10e23_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:84640c8c487bcec22aa2aa14e6e74035afe4b11a1572ebd74129d452b856d73a -size 84116 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2b9774757a61bd7a8abe6f79635a7d45_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2b9774757a61bd7a8abe6f79635a7d45_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2b9774757a61bd7a8abe6f79635a7d45_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2c4b84a66cab050595b6ee02d8799bb0_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2c4b84a66cab050595b6ee02d8799bb0_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2c4b84a66cab050595b6ee02d8799bb0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2cf96b55beaa98ebc755c7405b1adbeb_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2cf96b55beaa98ebc755c7405b1adbeb_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2cf96b55beaa98ebc755c7405b1adbeb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2d1bc5eed8281b9364808514bacdb32a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2d1bc5eed8281b9364808514bacdb32a_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2d1bc5eed8281b9364808514bacdb32a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2de65c6883946871f46308ff85ad7faf_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2de65c6883946871f46308ff85ad7faf_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2de65c6883946871f46308ff85ad7faf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2e1d7b4c07a00dd0f26b51558abbe428_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2e1d7b4c07a00dd0f26b51558abbe428_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2e1d7b4c07a00dd0f26b51558abbe428_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2eea01382188b70064fa2818361d89f1_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2eea01382188b70064fa2818361d89f1_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2eea01382188b70064fa2818361d89f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2f272754fa2955088bc0fa508bb65a9d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2f272754fa2955088bc0fa508bb65a9d_img.jpg deleted file mode 100644 index 8cc8cbfd09fb399b48e5bdb562e4ba8404968eea..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2f272754fa2955088bc0fa508bb65a9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d2c2e0aa2d2a3fdf5f40742e6374eca6cf2926caa3f17c1104cc251ca5b2f4bc -size 76293 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2f6073b866a873087bacb1adb0b0852c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2f6073b866a873087bacb1adb0b0852c_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2f6073b866a873087bacb1adb0b0852c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2fcfff451a38d27b4253203bae9c5a48_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2fcfff451a38d27b4253203bae9c5a48_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2fcfff451a38d27b4253203bae9c5a48_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2ffb32ca2d8acda8228f0301aa7f52e0_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2ffb32ca2d8acda8228f0301aa7f52e0_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/2ffb32ca2d8acda8228f0301aa7f52e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/30847fa0912597130bd8bc043a56b683_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/30847fa0912597130bd8bc043a56b683_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/30847fa0912597130bd8bc043a56b683_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg deleted file mode 100644 index 3e9020d6a196c94f2d0cea7289dc67df2429a30d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5931838fe84ec240d13e892a91d28ead2c9c99a588aa19dbefa6b35f655e29fd -size 51145 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3107f66da1c3556cee065608ee86f7e4_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3107f66da1c3556cee065608ee86f7e4_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3107f66da1c3556cee065608ee86f7e4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3164cf54c06cbe87b0a432d17eb9417b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3164cf54c06cbe87b0a432d17eb9417b_img.jpg deleted file mode 100644 index 34b527d66e21581a0284ea4f7426f9ebad910922..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3164cf54c06cbe87b0a432d17eb9417b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5d1345b58d480663b3821601e6a0abfd5d873cd98ced0c5e3228ace568880f38 -size 87736 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/318db222fae24a59c370fa6471d541b8_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/318db222fae24a59c370fa6471d541b8_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/318db222fae24a59c370fa6471d541b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/31a464e0e5a8a9c5d10fd33d2ed26347_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/31a464e0e5a8a9c5d10fd33d2ed26347_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/31a464e0e5a8a9c5d10fd33d2ed26347_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/33af66f0d081ac1bb0133b0238de585a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/33af66f0d081ac1bb0133b0238de585a_img.jpg deleted file mode 100644 index 49f7d6760391264ca80dcc7bd6ca4c92139d5266..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/33af66f0d081ac1bb0133b0238de585a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9c6ff4c60f26b2d57a8b9eb9d19898d8d5dcc88370472439565bd03cfe0ff3a8 -size 202581 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/35037145df6cd8b5520bbfebf46c9433_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/35037145df6cd8b5520bbfebf46c9433_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/35037145df6cd8b5520bbfebf46c9433_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/35437f160e157760713aa85be471c3f3_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/35437f160e157760713aa85be471c3f3_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/35437f160e157760713aa85be471c3f3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/359093c76d121867106328fa8adfe8ff_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/359093c76d121867106328fa8adfe8ff_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/359093c76d121867106328fa8adfe8ff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/365fdce90bacd7a819819a2e05e70403_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/365fdce90bacd7a819819a2e05e70403_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/365fdce90bacd7a819819a2e05e70403_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/366398d17120ce12a2c36b95c54033c5_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/366398d17120ce12a2c36b95c54033c5_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/366398d17120ce12a2c36b95c54033c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/372a0b094d72de45d94c6c8d52714e9a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/372a0b094d72de45d94c6c8d52714e9a_img.jpg deleted file mode 100644 index 89c9fb319dc8759a97877cbb7050b00d69a33e26..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/372a0b094d72de45d94c6c8d52714e9a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8fc703d6fc2ea27f11baab89f19089889e0daae121a2a090e5a6b9ecbc0d30cb -size 43847 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/378417d45871e98cf0371e2dfe49ef55_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/378417d45871e98cf0371e2dfe49ef55_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/378417d45871e98cf0371e2dfe49ef55_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/37d5d6957e175201847002c556b5a29d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/37d5d6957e175201847002c556b5a29d_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/37d5d6957e175201847002c556b5a29d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/37d8d885fed5ec107803a8eeceb71686_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/37d8d885fed5ec107803a8eeceb71686_img.jpg deleted file mode 100644 index 944fdccfc52993ebe91c91406d059725091c29d5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/37d8d885fed5ec107803a8eeceb71686_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6cb4d53fe2d2f1e0b1f41eb2671ae57c1cc4708d065eb2fc4f08736872b02788 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/384d97a0c67bd4f219a452c3cd658684_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/384d97a0c67bd4f219a452c3cd658684_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/384d97a0c67bd4f219a452c3cd658684_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/39d6fbe28fd2f6af73157212aaf2128b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/39d6fbe28fd2f6af73157212aaf2128b_img.jpg deleted file mode 100644 index 26d008f24b4e4bf4e3fe43da944b6066dc1b942e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/39d6fbe28fd2f6af73157212aaf2128b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:07378d5d0d27f81f3e4175c5cb4b6c773540f940f3fa90a3b20094107c81d43e -size 30603 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/39e964ecd6d6a7fd1d783271aa934f23_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/39e964ecd6d6a7fd1d783271aa934f23_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/39e964ecd6d6a7fd1d783271aa934f23_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3a3831d50dc74b7ebbec3e1d96eea588_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3a3831d50dc74b7ebbec3e1d96eea588_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3a3831d50dc74b7ebbec3e1d96eea588_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3b6c4e5a462a828bef2d462df300da37_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3b6c4e5a462a828bef2d462df300da37_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3b6c4e5a462a828bef2d462df300da37_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3b6f513e9cb02e7a2b653f69f9f81873_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3b6f513e9cb02e7a2b653f69f9f81873_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3b6f513e9cb02e7a2b653f69f9f81873_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3b6fe8cf6869f2ed1d7433b9c5503b38_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3b6fe8cf6869f2ed1d7433b9c5503b38_img.jpg deleted file mode 100644 index d2877c159d44885e6b9b26200a760c10fdb50171..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3b6fe8cf6869f2ed1d7433b9c5503b38_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:cbbc520e42804b7f0aa248ee626a45fd21425122771177e541d8d6fa3cbb1ece -size 43918 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3bc1596c96f362d588541b78554df33d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3bc1596c96f362d588541b78554df33d_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3bc1596c96f362d588541b78554df33d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3f86c37cef45524a8c4f74c3a724d945_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3f86c37cef45524a8c4f74c3a724d945_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/3f86c37cef45524a8c4f74c3a724d945_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/40cadfef9d925077fe9ecddbc1d44cc8_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/40cadfef9d925077fe9ecddbc1d44cc8_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/40cadfef9d925077fe9ecddbc1d44cc8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/40e106822047971ea364d73846848ecd_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/40e106822047971ea364d73846848ecd_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/40e106822047971ea364d73846848ecd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/41d2a2a58f53d1013a114da9c02f726e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/41d2a2a58f53d1013a114da9c02f726e_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/41d2a2a58f53d1013a114da9c02f726e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/426342bd710b59091374594dd7d65234_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/426342bd710b59091374594dd7d65234_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/426342bd710b59091374594dd7d65234_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/430d6070a68b7787dcbf6ee6237c8c73_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/430d6070a68b7787dcbf6ee6237c8c73_img.jpg deleted file mode 100644 index 2c3d19845424e97e34a8cc5bfd306c42f78d33de..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/430d6070a68b7787dcbf6ee6237c8c73_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3706643da21f4ad64da22b0b9312a3dc0f56743ceb3ad3c153a760f80a8c0255 -size 86000 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index 437c7cf78526b71e63f7c07b5a0fab087cbd4555..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:66f3213da7377a9eb4bdd467bcecf2c4890129f9dbe81b9220a8e62c45d15e4c -size 4511 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/457ebeb4cc14a22ced51a688af25f7a8_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/457ebeb4cc14a22ced51a688af25f7a8_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/457ebeb4cc14a22ced51a688af25f7a8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/45902eaeac38a0b8d0e670b205695d13_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/45902eaeac38a0b8d0e670b205695d13_img.jpg deleted file mode 100644 index 6d59d115b703cd34639b2a6b89f1284c142d1af1..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/45902eaeac38a0b8d0e670b205695d13_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:73d99de389529ae8fc91f0ef4a0935991dcae03a063ada30ed03a8d1d642a1ee -size 44270 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/45a161027983c0b508f6269c35551968_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/45a161027983c0b508f6269c35551968_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/45a161027983c0b508f6269c35551968_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/463543bc9a9a8d87e8a62ea5ec128313_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/463543bc9a9a8d87e8a62ea5ec128313_img.jpg deleted file mode 100644 index b4d4e23f8c5f8fe88535da2a9be2bf2a97a8e125..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/463543bc9a9a8d87e8a62ea5ec128313_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:aef7235202bd8886db032d26164489faea87bdfdb3756e385c5c56b2828f2d01 -size 93746 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4665bbd9c3079135f242a62a0e931eec_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4665bbd9c3079135f242a62a0e931eec_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4665bbd9c3079135f242a62a0e931eec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/469bffd8c327b2f28e2167fcaca784c6_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/469bffd8c327b2f28e2167fcaca784c6_img.jpg deleted file mode 100644 index c17763fad26a94a99d79bf960848ec28c75cc475..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/469bffd8c327b2f28e2167fcaca784c6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3111f0f812697672faa3cdf26ed918d4444a2b04051e86732a868c110f99bb1a -size 65449 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/47c8f3782d7566332f5685e1b7958b33_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/47c8f3782d7566332f5685e1b7958b33_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/47c8f3782d7566332f5685e1b7958b33_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg deleted file mode 100644 index 437c7cf78526b71e63f7c07b5a0fab087cbd4555..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:66f3213da7377a9eb4bdd467bcecf2c4890129f9dbe81b9220a8e62c45d15e4c -size 4511 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4a0481e8f65937a5833e4894b29fe657_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4a0481e8f65937a5833e4894b29fe657_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4a0481e8f65937a5833e4894b29fe657_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4a1aafd8c195990968b731cf9acfa68a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4a1aafd8c195990968b731cf9acfa68a_img.jpg deleted file mode 100644 index 9a4c9769a12e8eadf60b9ef0201c4e6ef9e53f8f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4a1aafd8c195990968b731cf9acfa68a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4901baba964a67877c8b47945fcc634f355ee80be1ffaaa86d4661ddba0a706d -size 52395 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4b06562dec0d51c18da84c42537b4db2_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4b06562dec0d51c18da84c42537b4db2_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4b06562dec0d51c18da84c42537b4db2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4bfb6bb23e005e280ded1e8e6c85bc46_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4bfb6bb23e005e280ded1e8e6c85bc46_img.jpg deleted file mode 100644 index 4b2f533fffb20a68ffe2ff49c06bba9ca034bd4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4bfb6bb23e005e280ded1e8e6c85bc46_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a38f5aa625dd9c297fef3c7b5b9acbe02a3cbc307ae3882d1d5f149f7b9c569b -size 49394 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4cc77834b75e6e10bed21fde344bd1f4_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4cc77834b75e6e10bed21fde344bd1f4_img.jpg deleted file mode 100644 index 47badff37c184307afcb907e00cc7c191ee11dd6..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4cc77834b75e6e10bed21fde344bd1f4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb1a6e8ae38ed86492d3f2b0d693f009f7b0dae1bf485212883d16e394965816 -size 162576 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4cc9a25425bbb446d58bea5581a5889f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4cc9a25425bbb446d58bea5581a5889f_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4cc9a25425bbb446d58bea5581a5889f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4ced45096fe3cf5adc96ec6b94f07e4f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4ced45096fe3cf5adc96ec6b94f07e4f_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4ced45096fe3cf5adc96ec6b94f07e4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4e58d71a7f0cda1ca24fac1ee80a0c7c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4e58d71a7f0cda1ca24fac1ee80a0c7c_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4e58d71a7f0cda1ca24fac1ee80a0c7c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4f775d2964d3729df9498e4321d1a3f0_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4f775d2964d3729df9498e4321d1a3f0_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/4f775d2964d3729df9498e4321d1a3f0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5009e30a55479d3941af523871208f9d_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5009e30a55479d3941af523871208f9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5374b3619ca88da164423df0b6a532fc_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5374b3619ca88da164423df0b6a532fc_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5374b3619ca88da164423df0b6a532fc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5441c05741f8a35ee5d6673b0b0ebb8b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5441c05741f8a35ee5d6673b0b0ebb8b_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5441c05741f8a35ee5d6673b0b0ebb8b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/54a69b7eddfb3dc9a9312dc3a721bb78_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/54a69b7eddfb3dc9a9312dc3a721bb78_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/54a69b7eddfb3dc9a9312dc3a721bb78_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/54e6016445a458d4c0aef4acc71bb0c8_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/54e6016445a458d4c0aef4acc71bb0c8_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/54e6016445a458d4c0aef4acc71bb0c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/54ec84ddb200e1f5e8999dfd0820b17c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/54ec84ddb200e1f5e8999dfd0820b17c_img.jpg deleted file mode 100644 index fc186e8b9af6bb10a36daadffcf484bf9538bc7a..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/54ec84ddb200e1f5e8999dfd0820b17c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4e5b046f479b9d9fe62abed708f3d7c3d5d6707dbe833f84a5b796ecf9b3b0ca -size 13424 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/55b5faca46291297ac05b4f648e60bcc_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/55b5faca46291297ac05b4f648e60bcc_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/55b5faca46291297ac05b4f648e60bcc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/55c1b9efdb97c2b7dd16b497c5b56d3c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/55c1b9efdb97c2b7dd16b497c5b56d3c_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/55c1b9efdb97c2b7dd16b497c5b56d3c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/560290b4b60884ac78117eb47a302b90_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/560290b4b60884ac78117eb47a302b90_img.jpg deleted file mode 100644 index 9dcbcdb0b09be55e865b1ab6036387d9c89182c0..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/560290b4b60884ac78117eb47a302b90_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b8a7308e26e4d9ef2b2e00de6dfa45f48d1b03d35deaeb5bc8344220ee269a99 -size 89840 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/56e7470adf0d33976ed8cc2f5bc6f0c8_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/56e7470adf0d33976ed8cc2f5bc6f0c8_img.jpg deleted file mode 100644 index 944fdccfc52993ebe91c91406d059725091c29d5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/56e7470adf0d33976ed8cc2f5bc6f0c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6cb4d53fe2d2f1e0b1f41eb2671ae57c1cc4708d065eb2fc4f08736872b02788 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/57de85188ce8fa114295d82ff92d8d95_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/57de85188ce8fa114295d82ff92d8d95_img.jpg deleted file mode 100644 index 0f232c609278cc1c2ea8e92a417f6a2492a4b037..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/57de85188ce8fa114295d82ff92d8d95_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5343be398757e73db5b2447165c05812bab1a59929d2b1545fefb89047494a99 -size 91202 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/59368942873b0c35eef79a7a985025dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5af8606c12edf41f406e56163fed32d9_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5af8606c12edf41f406e56163fed32d9_img.jpg deleted file mode 100644 index 944fdccfc52993ebe91c91406d059725091c29d5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5af8606c12edf41f406e56163fed32d9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6cb4d53fe2d2f1e0b1f41eb2671ae57c1cc4708d065eb2fc4f08736872b02788 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5b492020399ae8fbcc9714c8d83aebca_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5b492020399ae8fbcc9714c8d83aebca_img.jpg deleted file mode 100644 index 75572d7f7162547cba0ae71add0874a1f760ad1c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5b492020399ae8fbcc9714c8d83aebca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:32e1891e34f2756fbcf7dd02b2e7d5105bd23f918087c0f60692937314d6f4d5 -size 89016 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5d75ece2fd1a8b21a9500d131ee744ed_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5d75ece2fd1a8b21a9500d131ee744ed_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5d75ece2fd1a8b21a9500d131ee744ed_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5dad054d1733aea364f0d470778816df_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5dad054d1733aea364f0d470778816df_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5dad054d1733aea364f0d470778816df_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5e185b54d270cd15d1299478a13f1f97_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5e185b54d270cd15d1299478a13f1f97_img.jpg deleted file mode 100644 index 944fdccfc52993ebe91c91406d059725091c29d5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5e185b54d270cd15d1299478a13f1f97_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6cb4d53fe2d2f1e0b1f41eb2671ae57c1cc4708d065eb2fc4f08736872b02788 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5e1bb58c846e83eabe4e20fdba4f0a44_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5e1bb58c846e83eabe4e20fdba4f0a44_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5e1bb58c846e83eabe4e20fdba4f0a44_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5e38bd2f95d0f22ab5091fa99f29ff01_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5e38bd2f95d0f22ab5091fa99f29ff01_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5e38bd2f95d0f22ab5091fa99f29ff01_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5f533a4c9388beded5aba3c037ab7be8_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5f533a4c9388beded5aba3c037ab7be8_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5f533a4c9388beded5aba3c037ab7be8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5f775274defe2a58cc4b4498acd55a6c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5f775274defe2a58cc4b4498acd55a6c_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5f775274defe2a58cc4b4498acd55a6c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5f91fba42d09220b843c28373538928a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5f91fba42d09220b843c28373538928a_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5f91fba42d09220b843c28373538928a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5fb91e7895e390abec542d9328a870ef_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5fb91e7895e390abec542d9328a870ef_img.jpg deleted file mode 100644 index 558cf41ce613830898116e8c7787d2f07d1ec44f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5fb91e7895e390abec542d9328a870ef_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ab2f6d3415f0f38f33565c63d0e98687ab9dade9afd26c389b689f2b191f8284 -size 91154 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5fbe6b9515c3d8f7d2526ca5bfbd012d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5fbe6b9515c3d8f7d2526ca5bfbd012d_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/5fbe6b9515c3d8f7d2526ca5bfbd012d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/600fbaabf10e40148498bda9961511ab_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/600fbaabf10e40148498bda9961511ab_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/600fbaabf10e40148498bda9961511ab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6127ca80a1bc3d6a86b357a6ac43cb98_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6127ca80a1bc3d6a86b357a6ac43cb98_img.jpg deleted file mode 100644 index b50e1b927a3e633e40459a0a6a4c64e50d93c751..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6127ca80a1bc3d6a86b357a6ac43cb98_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c6e146956671e10853f0b672ec4cb31593b957899cbe458243836ee2181f7b0 -size 91425 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/62062de3c7147e8ee3829c3504ed156d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/62062de3c7147e8ee3829c3504ed156d_img.jpg deleted file mode 100644 index 289d104f053186474437c83cdcd50fe004d82bc6..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/62062de3c7147e8ee3829c3504ed156d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b2ed5d26e8ded112b2f9a3d11d44c640f7f9330ada37316f361eea7d99970e71 -size 30880 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/624dbf9b985f5bd85e902ec59b87ba4f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/624dbf9b985f5bd85e902ec59b87ba4f_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/624dbf9b985f5bd85e902ec59b87ba4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg deleted file mode 100644 index 4d381e3a98df1b58dead750d31c4a054aa9c2c02..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e67681bead2455e6b8d8d18030a01b0e2171506b182f72770d3e24ea934be356 -size 4522 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/62616918653bd50bc70542647d4caaed_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/62616918653bd50bc70542647d4caaed_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/62616918653bd50bc70542647d4caaed_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/62bcbcd2d72c7add43fc43355a3d212a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/62bcbcd2d72c7add43fc43355a3d212a_img.jpg deleted file mode 100644 index b6ee752af3018f6fc3c4dc59bb6206a4697636cf..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/62bcbcd2d72c7add43fc43355a3d212a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5baccd44d67eee47cb0261e424f0155a5696ce629bf04511b2739fbf072b9bb9 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/631360156a16ba258241007e2283213d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/631360156a16ba258241007e2283213d_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/631360156a16ba258241007e2283213d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/632cc2990479148d6529d6fe884edae7_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/632cc2990479148d6529d6fe884edae7_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/632cc2990479148d6529d6fe884edae7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/638d4a1e55dbf75a122c4f778258f3cb_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/638d4a1e55dbf75a122c4f778258f3cb_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/638d4a1e55dbf75a122c4f778258f3cb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6425c63a77cee908118f1ebf677de49f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6425c63a77cee908118f1ebf677de49f_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6425c63a77cee908118f1ebf677de49f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6470c6dbf291c1e9676f0651ca2b38fa_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6470c6dbf291c1e9676f0651ca2b38fa_img.jpg deleted file mode 100644 index 4023059362681c9a44917f91b0653c63dafc32a9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6470c6dbf291c1e9676f0651ca2b38fa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:740fca9e0c92b7f5df430e777bce3b135ca37086a1262854aa13a031b66dc0c6 -size 83635 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index 437c7cf78526b71e63f7c07b5a0fab087cbd4555..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6588b1c7f14069d96744b473ad663248_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:66f3213da7377a9eb4bdd467bcecf2c4890129f9dbe81b9220a8e62c45d15e4c -size 4511 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/659769b1f5155b9796f36a9530478860_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/659769b1f5155b9796f36a9530478860_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/659769b1f5155b9796f36a9530478860_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/65cd234286445e716c91a9f734e510d9_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/65cd234286445e716c91a9f734e510d9_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/65cd234286445e716c91a9f734e510d9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/65cf9633846ecab19f1a0b92fa8ecd9a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/65cf9633846ecab19f1a0b92fa8ecd9a_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/65cf9633846ecab19f1a0b92fa8ecd9a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6634b0f090110c6fe467e43030c7a488_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6634b0f090110c6fe467e43030c7a488_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6634b0f090110c6fe467e43030c7a488_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6665298b5cd4fc5f777d91df7863dc6c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6665298b5cd4fc5f777d91df7863dc6c_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6665298b5cd4fc5f777d91df7863dc6c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/671d724633c3474b8092064d750ce939_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/671d724633c3474b8092064d750ce939_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/671d724633c3474b8092064d750ce939_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/67278f2643057da13cf2eeef919a318e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/67278f2643057da13cf2eeef919a318e_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/67278f2643057da13cf2eeef919a318e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/67da7316a30be623c4c053d4d1eff952_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/67da7316a30be623c4c053d4d1eff952_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/67da7316a30be623c4c053d4d1eff952_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/67f4bd11d7a8e881b6bab41e3e11d426_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/67f4bd11d7a8e881b6bab41e3e11d426_img.jpg deleted file mode 100644 index 9f9db00ddfa900474982a0fc448b26c2b677751f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/67f4bd11d7a8e881b6bab41e3e11d426_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1d682ce12374d43cae03ba7d695e0559d72f8361adbd898a82299e611010a5d7 -size 26283 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6883c4a2aeca4cb08a9a7a95faa2645a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6883c4a2aeca4cb08a9a7a95faa2645a_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6883c4a2aeca4cb08a9a7a95faa2645a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/69131308e8da3cf82d210c930fdbf078_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/69131308e8da3cf82d210c930fdbf078_img.jpg deleted file mode 100644 index 4d381e3a98df1b58dead750d31c4a054aa9c2c02..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/69131308e8da3cf82d210c930fdbf078_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e67681bead2455e6b8d8d18030a01b0e2171506b182f72770d3e24ea934be356 -size 4522 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/69673317b4a8d0b5a24f33ce299820fb_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/69673317b4a8d0b5a24f33ce299820fb_img.jpg deleted file mode 100644 index 143fa18a3627c82688e9a7d7d9903667c48ac685..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/69673317b4a8d0b5a24f33ce299820fb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:88bc65ed03e7d7b3e131bf7d3833dc3cbcffb04256866f37efa6abc67706f972 -size 27548 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6a0edaeb8af1f2308513a8f98ce9aaa0_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6a0edaeb8af1f2308513a8f98ce9aaa0_img.jpg deleted file mode 100644 index 558cf41ce613830898116e8c7787d2f07d1ec44f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6a0edaeb8af1f2308513a8f98ce9aaa0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ab2f6d3415f0f38f33565c63d0e98687ab9dade9afd26c389b689f2b191f8284 -size 91154 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6a2e100d305cbbcf8e9e794d39ad9c75_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6a2e100d305cbbcf8e9e794d39ad9c75_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6a2e100d305cbbcf8e9e794d39ad9c75_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6a6be4894ef955ac942e3d7a7d1cf529_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6a6be4894ef955ac942e3d7a7d1cf529_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6a6be4894ef955ac942e3d7a7d1cf529_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6aff07583f1535949164b1e6f4ffd9ee_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6aff07583f1535949164b1e6f4ffd9ee_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6aff07583f1535949164b1e6f4ffd9ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6bff2cd340dd09b13b312514bbac613d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6bff2cd340dd09b13b312514bbac613d_img.jpg deleted file mode 100644 index e77b639c30744333d3328f1d46a997de9ebf7794..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6bff2cd340dd09b13b312514bbac613d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ee83db2a9853761eb812ab3d18ead9a7b6ba5f90481be2d2a191a189933621b1 -size 38979 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6cb7d7986b43faef6866b8bdcb6e4278_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6cb7d7986b43faef6866b8bdcb6e4278_img.jpg deleted file mode 100644 index 4c15812704b395902beb1410921189bffca011e1..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6cb7d7986b43faef6866b8bdcb6e4278_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ce5b310264407d46399210ab2f8837c654c7fd4aab3108566c74882ad7d3144e -size 48286 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6d861d12d3c64df3f625a0a7d7bc11a2_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6d861d12d3c64df3f625a0a7d7bc11a2_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6d861d12d3c64df3f625a0a7d7bc11a2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6da084e1172d878eec926417071b6361_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6da084e1172d878eec926417071b6361_img.jpg deleted file mode 100644 index 5daa3274d91cbbf6daa5566eab3554ed702ee258..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6da084e1172d878eec926417071b6361_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:dd6a76a89f2774a41181aa9039a58625f40fbfdd3f3e0df02575c39b5266f72c -size 49361 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6de50f7240dfad1634aa9ded6b36fffc_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6de50f7240dfad1634aa9ded6b36fffc_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6de50f7240dfad1634aa9ded6b36fffc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6e20e7b94f8042f05a660226090a538e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6e20e7b94f8042f05a660226090a538e_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6e20e7b94f8042f05a660226090a538e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6ed375302d877b2f8bb27e4d98995b51_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6ed375302d877b2f8bb27e4d98995b51_img.jpg deleted file mode 100644 index e84f369e8ced51f8a0ace589576115dee6135afb..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6ed375302d877b2f8bb27e4d98995b51_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bce8d0c856c97b8ddb4b55b761a6dd8de1fb13027bb78701345ebbbb24f61f15 -size 115155 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6f52aa6e2a0da763ca0091b3771d1c25_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6f52aa6e2a0da763ca0091b3771d1c25_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6f52aa6e2a0da763ca0091b3771d1c25_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6faa2c6456db4413927b19b9cbfe4176_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6faa2c6456db4413927b19b9cbfe4176_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6faa2c6456db4413927b19b9cbfe4176_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6fd1b2efc24f6bc630680f8de7c31576_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6fd1b2efc24f6bc630680f8de7c31576_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6fd1b2efc24f6bc630680f8de7c31576_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6fdf990c9cc944ccf5688a804f6ed35c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6fdf990c9cc944ccf5688a804f6ed35c_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/6fdf990c9cc944ccf5688a804f6ed35c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/70dab5b17ce15a319dd531324de9c9fe_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/70dab5b17ce15a319dd531324de9c9fe_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/70dab5b17ce15a319dd531324de9c9fe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/710a9cf1a991f4226fbe1e73ea3cb6a6_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/710a9cf1a991f4226fbe1e73ea3cb6a6_img.jpg deleted file mode 100644 index 8a9e736be2554e08ef8db6cc349a318b42d2ad13..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/710a9cf1a991f4226fbe1e73ea3cb6a6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1ab4a175682a59e3b5e901cc9c579089abd4839f61988f1eaf460411d8436bc8 -size 31952 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/71434cf1fa818750f4b7b14d04fefc70_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/71434cf1fa818750f4b7b14d04fefc70_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/71434cf1fa818750f4b7b14d04fefc70_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7183d7b44e8c46abd64438b3894a0902_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7183d7b44e8c46abd64438b3894a0902_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7183d7b44e8c46abd64438b3894a0902_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/73923a5d4eee13d96aa9bd1622b0976f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/73923a5d4eee13d96aa9bd1622b0976f_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/73923a5d4eee13d96aa9bd1622b0976f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7449b816c06254de475a247cc72a8add_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7449b816c06254de475a247cc72a8add_img.jpg deleted file mode 100644 index 462a77aa6adbcb0a27eabe182ca95896d3ccf542..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7449b816c06254de475a247cc72a8add_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f255077a30aa10283345b6ca8c4f3eae2b96691ecc27b89ffac32612409446e0 -size 51564 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7469f7d890531be66ff585ef273e6c1b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7469f7d890531be66ff585ef273e6c1b_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7469f7d890531be66ff585ef273e6c1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/74cab8aa3cac8c33efc20cc187916544_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/74cab8aa3cac8c33efc20cc187916544_img.jpg deleted file mode 100644 index 14393dbdac2467d3b994cc5c3b7ecefe66b187c4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/74cab8aa3cac8c33efc20cc187916544_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:497e2368fd971b7de12b9ca16e6261227476129dcb3d38b722a65d9c585b551f -size 82536 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/75e91977269ab11e564cb85a58afda1b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/75e91977269ab11e564cb85a58afda1b_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/75e91977269ab11e564cb85a58afda1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/777060de3711edf66fa36de0822c45ce_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/777060de3711edf66fa36de0822c45ce_img.jpg deleted file mode 100644 index aaef2c93d201f85801b03f8f0731749c2737c4b8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/777060de3711edf66fa36de0822c45ce_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f95688e9e1834948cb5dcd1e6c3e596bc54771db7c82e2f677639151164ac011 -size 40200 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/77d11d3a8152805a6323635895fdea41_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/77d11d3a8152805a6323635895fdea41_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/77d11d3a8152805a6323635895fdea41_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/782012363ffb161a84600666895ae6e4_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/782012363ffb161a84600666895ae6e4_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/782012363ffb161a84600666895ae6e4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/799f76c21809a255ae48acbf76a074da_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/799f76c21809a255ae48acbf76a074da_img.jpg deleted file mode 100644 index 099c3671bac89d8d5a57f42d330249d9309d835d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/799f76c21809a255ae48acbf76a074da_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e6d86a63bc71f251771bee82cc9896aa90f6f0993ddeb1ee9f832016cb0cf916 -size 35502 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7aeb1d06016b3a52a1d68ed9518dbbf4_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7aeb1d06016b3a52a1d68ed9518dbbf4_img.jpg deleted file mode 100644 index 2c2e95f396400daec29da3baacc06a9d310bcc7d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7aeb1d06016b3a52a1d68ed9518dbbf4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:28d419b759b036ef19c0e5fc587d59055bcb1a0521ccc640ffbd6be9ce42ed89 -size 50155 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7b0303896a557a9a495591a36349e5f7_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7b0303896a557a9a495591a36349e5f7_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7b0303896a557a9a495591a36349e5f7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7e5c50a0a280f43fa1d8cb1fc5e30a20_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7e5c50a0a280f43fa1d8cb1fc5e30a20_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7e5c50a0a280f43fa1d8cb1fc5e30a20_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7e86b957cd3c33e57d22a8389947ce46_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7e86b957cd3c33e57d22a8389947ce46_img.jpg deleted file mode 100644 index 944fdccfc52993ebe91c91406d059725091c29d5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7e86b957cd3c33e57d22a8389947ce46_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6cb4d53fe2d2f1e0b1f41eb2671ae57c1cc4708d065eb2fc4f08736872b02788 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7fe15d7c926841a22a218599eab4d5b2_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7fe15d7c926841a22a218599eab4d5b2_img.jpg deleted file mode 100644 index e704f9ece180f9c863f149b693724f7a0221ef38..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/7fe15d7c926841a22a218599eab4d5b2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:45fafe43052233cd739c4ba178c037fed1588bdf69c815c120ab975c2af1fd1d -size 77013 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8071f58c3d57408857130711daf9effe_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8071f58c3d57408857130711daf9effe_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8071f58c3d57408857130711daf9effe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/81513bd390d91f2e7a9b865cf50dce69_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/81513bd390d91f2e7a9b865cf50dce69_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/81513bd390d91f2e7a9b865cf50dce69_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/81550473b76180b6088795cbfd708d52_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/81550473b76180b6088795cbfd708d52_img.jpg deleted file mode 100644 index 5aa67a38b0f5d7aa4bbf2792e48f1ff8b73d2384..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/81550473b76180b6088795cbfd708d52_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b0a195fde6b6f1a02e071d2f3ff7d1f6fa0bf79fe93a1b8bf6d01e658243d489 -size 49983 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/82c09fea6b231155303148e9becf7fa9_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/82c09fea6b231155303148e9becf7fa9_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/82c09fea6b231155303148e9becf7fa9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/87755376ccda1904b0f5e60a7dd2c465_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/87755376ccda1904b0f5e60a7dd2c465_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/87755376ccda1904b0f5e60a7dd2c465_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/87e720ac638df8b655bbb374527f6a6f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/87e720ac638df8b655bbb374527f6a6f_img.jpg deleted file mode 100644 index 8e087f1f65a66d9b08b73dcaa64d1a1c0c845eaa..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/87e720ac638df8b655bbb374527f6a6f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2fcbae9900e84533271e2a2390bf219c86846881b00bb9a3cee34e872ba954fd -size 157332 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8a02c1bd6ac8111aead3a70a4aba750e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8a02c1bd6ac8111aead3a70a4aba750e_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8a02c1bd6ac8111aead3a70a4aba750e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8b36c56b042bf3e7ec9b29f35568fe66_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8b36c56b042bf3e7ec9b29f35568fe66_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8b36c56b042bf3e7ec9b29f35568fe66_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8b4befaffc5166da571069410e207aea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8bc5f337659c3a9c11ceb0f0dc82e4f8_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8bc5f337659c3a9c11ceb0f0dc82e4f8_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8bc5f337659c3a9c11ceb0f0dc82e4f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8bd9527f7ae16517a90c44e34ced8589_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8bd9527f7ae16517a90c44e34ced8589_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8bd9527f7ae16517a90c44e34ced8589_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8c0ac6780a5e22425c185a15ffe01d7b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8c0ac6780a5e22425c185a15ffe01d7b_img.jpg deleted file mode 100644 index c9e3144b983ecf3c40dfcef53a33eb70c0c6c35a..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8c0ac6780a5e22425c185a15ffe01d7b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:be7089b7b1a73b7783fdcc53a26a4c19deb3c27f24009b8a52389ffbf27511c8 -size 90340 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8ce6ab62a04c4eafa11bef389ddd21fd_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8ce6ab62a04c4eafa11bef389ddd21fd_img.jpg deleted file mode 100644 index 215c3e9ab762821ea22c8ed0ee4f087bee3d8075..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8ce6ab62a04c4eafa11bef389ddd21fd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:714bff3bdcf433bb5e485948f36c9b8d96c5636cb67a05a522c5b47c16883ef4 -size 32363 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8cf1ef6278dcc5d495a1350cc68ab46d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8cf1ef6278dcc5d495a1350cc68ab46d_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8cf1ef6278dcc5d495a1350cc68ab46d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8ed67838d44c23a50ca30525456d38be_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8ed67838d44c23a50ca30525456d38be_img.jpg deleted file mode 100644 index b5024d92a85b85770cfb14df985c38bb58e2808b..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8ed67838d44c23a50ca30525456d38be_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d9463d303173fee1d9cbbe4f313932355d4ad44ada3dd5d1172a0d3517c34b9d -size 116476 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8f56eaf659edc57ac74706e8caab9f95_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8f56eaf659edc57ac74706e8caab9f95_img.jpg deleted file mode 100644 index 7055f989a2905694ee5f4e9c734c049d2b964b0d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8f56eaf659edc57ac74706e8caab9f95_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d1e9be4c1f63a0f270e1621f0e94d3bb7425059b7804bf655eaf620bacfc941c -size 90313 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/933f4267f9d2b0ece044e7649be53447_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/933f4267f9d2b0ece044e7649be53447_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/933f4267f9d2b0ece044e7649be53447_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/94b678292f1b426e0d16117bb08bfba5_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/94b678292f1b426e0d16117bb08bfba5_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/94b678292f1b426e0d16117bb08bfba5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/957e0a1d31f6b69dcd8a355fd185031a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/957e0a1d31f6b69dcd8a355fd185031a_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/957e0a1d31f6b69dcd8a355fd185031a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/964fc0fd54c825b85166fb5a00aa716d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/964fc0fd54c825b85166fb5a00aa716d_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/964fc0fd54c825b85166fb5a00aa716d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/970df246bd8b45f590e294d25c1bb60a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/970df246bd8b45f590e294d25c1bb60a_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/970df246bd8b45f590e294d25c1bb60a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/98d7c3a3783b091ac41fd87427f1c8e1_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/98d7c3a3783b091ac41fd87427f1c8e1_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/98d7c3a3783b091ac41fd87427f1c8e1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/994a745041d4af5063159f147e990e78_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/994a745041d4af5063159f147e990e78_img.jpg deleted file mode 100644 index 03bfe474466f18d95952a6683ac6b798ffa666a1..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/994a745041d4af5063159f147e990e78_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:326829cbfa0d500d3e7c32351283b68b7b6a75c20b215111f6f1a4e492723be7 -size 32354 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9b3e75266694bdf164036baf1bb25422_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9b3e75266694bdf164036baf1bb25422_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9b3e75266694bdf164036baf1bb25422_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9b5bae50a8a287c353f79cf9b43c8a4a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9b5bae50a8a287c353f79cf9b43c8a4a_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9b5bae50a8a287c353f79cf9b43c8a4a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9b9a55ffe36b80f5500a0e273a77fd1b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9b9a55ffe36b80f5500a0e273a77fd1b_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9b9a55ffe36b80f5500a0e273a77fd1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9bf98e5234e80aa178c89e99397928bf_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9bf98e5234e80aa178c89e99397928bf_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9bf98e5234e80aa178c89e99397928bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9c1b489f9f959fedf0b32924adf2a4dc_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9c1b489f9f959fedf0b32924adf2a4dc_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9c1b489f9f959fedf0b32924adf2a4dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9cc404b84df8122128a097d6ada44e3d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9cc404b84df8122128a097d6ada44e3d_img.jpg deleted file mode 100644 index 0f435834233fc3656d390ad328056d1125f8a0ea..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9cc404b84df8122128a097d6ada44e3d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c75bc1d0dae578b7ad50bf99d0a6a079d7cd5a97b33c610c9f63a5374b3de62 -size 39633 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9e4bce3d0ef8a18588aa58fd3db1cbe3_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9e4bce3d0ef8a18588aa58fd3db1cbe3_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9e4bce3d0ef8a18588aa58fd3db1cbe3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9e623456fe8c4de1b2c053331851b210_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9e623456fe8c4de1b2c053331851b210_img.jpg deleted file mode 100644 index 34349ef592282934f5010c7d734610399b6000fb..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9e623456fe8c4de1b2c053331851b210_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:200f642d2318a517be36c06857b503ce9c5ab5eea7c37a7208aa6092bdc6f019 -size 133429 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9edb9da00a36a0e140e99e072096ee53_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9edb9da00a36a0e140e99e072096ee53_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9edb9da00a36a0e140e99e072096ee53_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9f5f9afcedaa0d9b7991976f5000865c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9f5f9afcedaa0d9b7991976f5000865c_img.jpg deleted file mode 100644 index 566ab4da41d163f2bc2da131cdebca136be42849..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/9f5f9afcedaa0d9b7991976f5000865c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1bd8c755877a093789e404bc0b13ee6a8ccad761d3413a877097d82cbe9b4ff2 -size 72258 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg deleted file mode 100644 index 58741b5096ed64c02d4fb749d3242b16fcb83c42..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:026b96be3c0582711d2f1ae0c231b1a758089a6471f0dbb742c23458333d8ab3 -size 39115 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a0e94fd45c9063825c96352a81b86231_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a0e94fd45c9063825c96352a81b86231_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a0e94fd45c9063825c96352a81b86231_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a194ad55e5e2b04f07456c3c728fae88_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a194ad55e5e2b04f07456c3c728fae88_img.jpg deleted file mode 100644 index e5d27047009866c3942898223836878ef5e23516..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a194ad55e5e2b04f07456c3c728fae88_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f8eac503d8681b298900d9e4250e97b6875ff66525dccb4e21d552aea0363c26 -size 23685 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a305e92507a8f5f322bf6287405db4c6_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a305e92507a8f5f322bf6287405db4c6_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a305e92507a8f5f322bf6287405db4c6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a3144f9447b85aa19cc0a88f603fb688_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a3144f9447b85aa19cc0a88f603fb688_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a3144f9447b85aa19cc0a88f603fb688_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a554d5480f9ae091a17e50011afe5968_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a554d5480f9ae091a17e50011afe5968_img.jpg deleted file mode 100644 index 90c93f26e936a7421636b90a79cfd920cf686854..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a554d5480f9ae091a17e50011afe5968_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2113b5b5d8ec49460a1bcbbff1bb6c63c96eba7e361ac9f615161d8ae241996a -size 204342 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a5f09d21af8c3e909361c622a501c7f2_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a5f09d21af8c3e909361c622a501c7f2_img.jpg deleted file mode 100644 index 7fe906eaf4f874a863f5b0d8777172eb936f2891..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a5f09d21af8c3e909361c622a501c7f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:72004a5db765265dddc89a072935cf047f5b244c2ee2d9afe18080a81aa00f49 -size 4561 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a66272356c31124486c091940638c76b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a66272356c31124486c091940638c76b_img.jpg deleted file mode 100644 index 942772a0ed14dc0181f5a57e7435cb8aef14fb8f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a66272356c31124486c091940638c76b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b27057e6cd707249b2368b99a8c1c212fbd5a1c3392ae48d00e1f088253b2e0d -size 99799 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a6e999d9ce095e6092342ba352b60991_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a6e999d9ce095e6092342ba352b60991_img.jpg deleted file mode 100644 index d9abc46aa2538859ab4be1973aca288b7dae9183..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a6e999d9ce095e6092342ba352b60991_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9b237ebcfd23ba867a97f2ea551c284f1459203e405f62153e265d6d141f81ea -size 47808 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a90eb5fc0985caf25c17075250c86908_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a90eb5fc0985caf25c17075250c86908_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a90eb5fc0985caf25c17075250c86908_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a97b949bc414cb29656b23f9d011698b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a97b949bc414cb29656b23f9d011698b_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a97b949bc414cb29656b23f9d011698b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a9be8b5aa78ae267adfc1152523ec42d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a9be8b5aa78ae267adfc1152523ec42d_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/a9be8b5aa78ae267adfc1152523ec42d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aa5879e72c990f924e434bf9208b0094_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aa5879e72c990f924e434bf9208b0094_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aa5879e72c990f924e434bf9208b0094_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aa68758c757955e0598cac82adf6459d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aa68758c757955e0598cac82adf6459d_img.jpg deleted file mode 100644 index d003e2b005020485b42dab0f5bd9196565d580b1..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aa68758c757955e0598cac82adf6459d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0e93d952cc522ec8ca6fad2f6b110a56e15b6edcab8b0197549000117a8af301 -size 144779 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aac1229a97a38498dda01631625b7bdd_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aac1229a97a38498dda01631625b7bdd_img.jpg deleted file mode 100644 index 0b7b99a378ba1fce3a459df0c96ae6e1a017b04d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aac1229a97a38498dda01631625b7bdd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d0d3e9c2a794e89f5d70940b7e00fb1ec80cb6adf4c1543928d03eb928035d61 -size 77053 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ab0a8becb8f7e5a6443afd86481b2f3f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ab0a8becb8f7e5a6443afd86481b2f3f_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ab0a8becb8f7e5a6443afd86481b2f3f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ab10485552a6ace7e923ba6fbd98f06c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ab10485552a6ace7e923ba6fbd98f06c_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ab10485552a6ace7e923ba6fbd98f06c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ab3d65655ab371f08589985cafc2316d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ab3d65655ab371f08589985cafc2316d_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ab3d65655ab371f08589985cafc2316d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/abdd3f96a1e296c46300f2a326213dc0_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/abdd3f96a1e296c46300f2a326213dc0_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/abdd3f96a1e296c46300f2a326213dc0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ac3e6a6be9b396dd85e9ffa2c248451b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ac3e6a6be9b396dd85e9ffa2c248451b_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ac3e6a6be9b396dd85e9ffa2c248451b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ac768d795629007e1bf7c94829aba60b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ac768d795629007e1bf7c94829aba60b_img.jpg deleted file mode 100644 index b50e1b927a3e633e40459a0a6a4c64e50d93c751..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ac768d795629007e1bf7c94829aba60b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c6e146956671e10853f0b672ec4cb31593b957899cbe458243836ee2181f7b0 -size 91425 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ac776ddad6224ba7e1d9f3c9e39540fb_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ac776ddad6224ba7e1d9f3c9e39540fb_img.jpg deleted file mode 100644 index 40a3c8b78c49cbbdb1c81f9fe3a7928bb8131de2..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ac776ddad6224ba7e1d9f3c9e39540fb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:19b61225edb457a2a8cf2995b69bc2b739756ef09cc54b99517d1ab22c5cef43 -size 36009 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ae213b1a5f3c78cac8dcac242600ee18_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ae213b1a5f3c78cac8dcac242600ee18_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ae213b1a5f3c78cac8dcac242600ee18_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aeb10f7fbb625ece5a0f4f299d759a83_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aeb10f7fbb625ece5a0f4f299d759a83_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aeb10f7fbb625ece5a0f4f299d759a83_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aef4390a4629604196222b9ed006a786_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aef4390a4629604196222b9ed006a786_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/aef4390a4629604196222b9ed006a786_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b149288714c9605e9961c6d9abea8d18_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b149288714c9605e9961c6d9abea8d18_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b149288714c9605e9961c6d9abea8d18_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b2794adf2c4704e192a5644013629a33_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b2794adf2c4704e192a5644013629a33_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b2794adf2c4704e192a5644013629a33_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b323defd3d8e30a4add43c6c501e5b0d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b323defd3d8e30a4add43c6c501e5b0d_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b323defd3d8e30a4add43c6c501e5b0d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b324224acc41e653a93d145e61f98d8c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b324224acc41e653a93d145e61f98d8c_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b324224acc41e653a93d145e61f98d8c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b34b4f64f42215bc2d63d6e4d719b901_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b34b4f64f42215bc2d63d6e4d719b901_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b34b4f64f42215bc2d63d6e4d719b901_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b35607344f83b254efb342f9662e2063_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b35607344f83b254efb342f9662e2063_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b35607344f83b254efb342f9662e2063_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b44f89b176c971c7dd264c07bfef2c2a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b44f89b176c971c7dd264c07bfef2c2a_img.jpg deleted file mode 100644 index 97e62103b82df6779f9d91e8d3ae215d18184a49..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b44f89b176c971c7dd264c07bfef2c2a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c845e15be3344288eecb9803223b0f2325c3a2ac3766ed36cc7aa0930bde595 -size 35654 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b4b9911db50edb56242223cbbdfab597_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b4b9911db50edb56242223cbbdfab597_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b4b9911db50edb56242223cbbdfab597_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b62e6e3b1cbec5de7e750dc0d46bcc79_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b62e6e3b1cbec5de7e750dc0d46bcc79_img.jpg deleted file mode 100644 index 944fdccfc52993ebe91c91406d059725091c29d5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b62e6e3b1cbec5de7e750dc0d46bcc79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6cb4d53fe2d2f1e0b1f41eb2671ae57c1cc4708d065eb2fc4f08736872b02788 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b6c1148ea4ff3481941a4d3937e7028d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b6c1148ea4ff3481941a4d3937e7028d_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b6c1148ea4ff3481941a4d3937e7028d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b6cafcdfab7ca53f640ddc2d2bae5261_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b6cafcdfab7ca53f640ddc2d2bae5261_img.jpg deleted file mode 100644 index 437c7cf78526b71e63f7c07b5a0fab087cbd4555..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b6cafcdfab7ca53f640ddc2d2bae5261_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:66f3213da7377a9eb4bdd467bcecf2c4890129f9dbe81b9220a8e62c45d15e4c -size 4511 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b7636707604e45cc57c71271bc094be1_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b7636707604e45cc57c71271bc094be1_img.jpg deleted file mode 100644 index 434cb058d5ed13a3185ddab39af49e26caa939a9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b7636707604e45cc57c71271bc094be1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d713f1e4aaa205a826f405285e5d911310e21986a141048ce062203e72106576 -size 30799 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b7c458c8f40fa7621871a6777ae65dbb_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b7c458c8f40fa7621871a6777ae65dbb_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b7c458c8f40fa7621871a6777ae65dbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b7e4791d0f2b4881a99344168f47638b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b7e4791d0f2b4881a99344168f47638b_img.jpg deleted file mode 100644 index 2ea74d18e0300150f4856b85ccb4dbb392f11dc2..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b7e4791d0f2b4881a99344168f47638b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2b89c452f7ca750e984c63c950d2c48a7023aba1a0b47d9fcda621856b764be6 -size 117129 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b7e8758ea655fc07d3aadaf2d8408d6e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b7e8758ea655fc07d3aadaf2d8408d6e_img.jpg deleted file mode 100644 index 437c7cf78526b71e63f7c07b5a0fab087cbd4555..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b7e8758ea655fc07d3aadaf2d8408d6e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:66f3213da7377a9eb4bdd467bcecf2c4890129f9dbe81b9220a8e62c45d15e4c -size 4511 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b8c7900f1e7273ecfbc1a09de0261658_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b8c7900f1e7273ecfbc1a09de0261658_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b8c7900f1e7273ecfbc1a09de0261658_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bb9f586190c7197099d25db7df9050af_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bb9f586190c7197099d25db7df9050af_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bb9f586190c7197099d25db7df9050af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bc4568cde39ed422b1f3231304177da0_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bc4568cde39ed422b1f3231304177da0_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bc4568cde39ed422b1f3231304177da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bcae27bc6aeb49b97b6d51dce8d5c1af_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bcae27bc6aeb49b97b6d51dce8d5c1af_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bcae27bc6aeb49b97b6d51dce8d5c1af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bcb0b443fcfea25dcb7005487af9200d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bcb0b443fcfea25dcb7005487af9200d_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bcb0b443fcfea25dcb7005487af9200d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bdd1fc345a009867e50739255be00f90_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bdd1fc345a009867e50739255be00f90_img.jpg deleted file mode 100644 index d7b090ad93db217c16f392d5afe1ba32b5b11d60..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bdd1fc345a009867e50739255be00f90_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f8770fb6bef4911d27a7b5a24a6c113a1b8de82306e98f6a7856ba615025eaab -size 38263 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bed8632f583eed2cac668ede9ae65f45_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bed8632f583eed2cac668ede9ae65f45_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bed8632f583eed2cac668ede9ae65f45_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bfcea196796f3bc23aeb4499b396cab1_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bfcea196796f3bc23aeb4499b396cab1_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/bfcea196796f3bc23aeb4499b396cab1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c075f11b8ee283222cbed999bc5a392c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c075f11b8ee283222cbed999bc5a392c_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c075f11b8ee283222cbed999bc5a392c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c0912cb53f8cc1be7ad8d288f5cb0fd0_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c0912cb53f8cc1be7ad8d288f5cb0fd0_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c0912cb53f8cc1be7ad8d288f5cb0fd0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c1bad47c33e0912b92bee4576d99810d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c1bad47c33e0912b92bee4576d99810d_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c1bad47c33e0912b92bee4576d99810d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c1f9a65a43cd72fb7c887a69778c8e3f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c1f9a65a43cd72fb7c887a69778c8e3f_img.jpg deleted file mode 100644 index 921a4ac152797ebbb5806665c3efcc10a3d4df41..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c1f9a65a43cd72fb7c887a69778c8e3f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0e72f67985df18e2d6d9c9d3c45f12b0435fdfb2135005997bc3b1afaf5b19e5 -size 31706 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c27f535a48e7cdba6653c484181b3e32_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c27f535a48e7cdba6653c484181b3e32_img.jpg deleted file mode 100644 index 9cee64c9e68c0fd00a6e5dce134929cda2a13757..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c27f535a48e7cdba6653c484181b3e32_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:baebe8cdc658a1385c408573f0c3cc8c979166c7a2d4570f5f2b4d7ec19e5fe1 -size 39414 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c2ff6339c62f961f2abd954e987c0082_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c2ff6339c62f961f2abd954e987c0082_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c2ff6339c62f961f2abd954e987c0082_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c355b8056bdd4728357d7d5ed18792ca_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c355b8056bdd4728357d7d5ed18792ca_img.jpg deleted file mode 100644 index 2369345c9ab3071fa5ce8a67a11152a15bed3921..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c355b8056bdd4728357d7d5ed18792ca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2e15b04108bf15ba05840da2e66db534cb688cb7905ab9f2f2dccface9f88627 -size 179651 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c3afdf6d44fa08949ae7df7bd616453f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c3afdf6d44fa08949ae7df7bd616453f_img.jpg deleted file mode 100644 index 123d2ef4be4c17a5d8264004bdb4bad976b5ac3b..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c3afdf6d44fa08949ae7df7bd616453f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:01610f4dc5d9facf85961bc0e8fc7e58e26511ccbc67de07ed5b0bc302a096c6 -size 48826 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c3c2b3eb8e16ab6cd6acdec0fcf82999_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c3c2b3eb8e16ab6cd6acdec0fcf82999_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c3c2b3eb8e16ab6cd6acdec0fcf82999_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c41b4b0e4f4258e3c69ede6717f6dd33_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c41b4b0e4f4258e3c69ede6717f6dd33_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c41b4b0e4f4258e3c69ede6717f6dd33_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c4738e5ac7f134cb42cac8a06858b8ac_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c4738e5ac7f134cb42cac8a06858b8ac_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c4738e5ac7f134cb42cac8a06858b8ac_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c4ce20d443c5793503265b1f68fe4536_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c4ce20d443c5793503265b1f68fe4536_img.jpg deleted file mode 100644 index 3a0984f15076b37bae9dd8523490cdf149de1a12..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c4ce20d443c5793503265b1f68fe4536_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e3e0c31cbd9291c0c1136098026e189c67426cdea81c0051e5e29f1e5de691da -size 42625 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c5ec27fa66024712e34aec3f57c0430c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c5ec27fa66024712e34aec3f57c0430c_img.jpg deleted file mode 100644 index 210fd69f2bd808e1bb0d220df5619a39245d4e74..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c5ec27fa66024712e34aec3f57c0430c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:88d4b558d5f06fcaba7c313aeec921d749b7a127ad1a51a3a5f266499abaa341 -size 30603 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c6240283e2f65a6d02db47fa4ab0c518_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c6240283e2f65a6d02db47fa4ab0c518_img.jpg deleted file mode 100644 index 573ec45f94d6d9a9c13b12b29463834a5f00097e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c6240283e2f65a6d02db47fa4ab0c518_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e726f708e2f9849722a908a41f88c1ac5958899cf62fa41b773ded90da3a3aa2 -size 161760 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c63537ac964ee56c2797ec477b520c25_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c63537ac964ee56c2797ec477b520c25_img.jpg deleted file mode 100644 index 07a75ecd211cc55207243a5c32d8171dc8a52c61..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c63537ac964ee56c2797ec477b520c25_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:407b7b7880f6685abe2b551784d49c19611f707210c27169c378d9e0e2ee858a -size 161760 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c679e0b896c60731688fd5e302dc96b5_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c679e0b896c60731688fd5e302dc96b5_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c679e0b896c60731688fd5e302dc96b5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c6fd5cb542ee6c63f2acd62896ffcc35_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c6fd5cb542ee6c63f2acd62896ffcc35_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c6fd5cb542ee6c63f2acd62896ffcc35_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c6ffc947df5e0a0aee6304d52999ee3b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c6ffc947df5e0a0aee6304d52999ee3b_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c6ffc947df5e0a0aee6304d52999ee3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c755e79fe75238688e161b5b9c7ee536_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c755e79fe75238688e161b5b9c7ee536_img.jpg deleted file mode 100644 index 2060caf719b678f3021c6b9c7c4bd35ee108eb42..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c755e79fe75238688e161b5b9c7ee536_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4b1d1fed88a2f54ea50209e7f70f9aae1b9c49564a8353a92d491cff343ab8db -size 89933 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c886d02f002430c9405c8ecc5650450b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c886d02f002430c9405c8ecc5650450b_img.jpg deleted file mode 100644 index 61f1df603bd5a7d88c6d6efec266a33b253b909f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c886d02f002430c9405c8ecc5650450b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:46d0c2f8e8cd50fadeeaf79e30c84b7ac80ea8bad680a230bace3b58235a43d3 -size 84192 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c8ddc7930f09ad09f782605d1c5b5733_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c8ddc7930f09ad09f782605d1c5b5733_img.jpg deleted file mode 100644 index 711bc5349c587ff7d61a6158dad430301d8d4578..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c8ddc7930f09ad09f782605d1c5b5733_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60b92e129a78a8db535a30224abf4bb211f6834743b22c5924b0ee345632f64d -size 31815 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c95ab75ce8f67ea4200944468d7aea30_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c95ab75ce8f67ea4200944468d7aea30_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c95ab75ce8f67ea4200944468d7aea30_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg deleted file mode 100644 index 944fdccfc52993ebe91c91406d059725091c29d5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6cb4d53fe2d2f1e0b1f41eb2671ae57c1cc4708d065eb2fc4f08736872b02788 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c9b9d380332d98e5579876adfa04eb0f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c9b9d380332d98e5579876adfa04eb0f_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c9b9d380332d98e5579876adfa04eb0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c9c32c022715809003833be0ed198f1c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c9c32c022715809003833be0ed198f1c_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/c9c32c022715809003833be0ed198f1c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cb01dfc2db37c44f7ff39b67b5f9d3da_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cb01dfc2db37c44f7ff39b67b5f9d3da_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cb01dfc2db37c44f7ff39b67b5f9d3da_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cb2d63f57f5430ad7adfdf3149e92bff_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cb2d63f57f5430ad7adfdf3149e92bff_img.jpg deleted file mode 100644 index b192513298ebafb100d6d2ab432fe297788b81c1..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cb2d63f57f5430ad7adfdf3149e92bff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:04fc346c7483a681561cf8c8c80f785114e4fcd653ac8e679a31187d61393ba7 -size 4240 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg deleted file mode 100644 index efbe3f7f842e9c4dd3de63674143b4e1983d9a86..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:504b082290f8efe0baf871cf673a828db18ca9e60bf1ac68ca429888c029dfa8 -size 4480 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cdb7ea1e3072c3b9885c63d496dc7d84_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cdb7ea1e3072c3b9885c63d496dc7d84_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cdb7ea1e3072c3b9885c63d496dc7d84_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ce68ff30159c3788e28d166216807520_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ce68ff30159c3788e28d166216807520_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ce68ff30159c3788e28d166216807520_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cec3dce43502075ea34c4480ec856a66_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cec3dce43502075ea34c4480ec856a66_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cec3dce43502075ea34c4480ec856a66_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cf08e441bafa27592ca7f62e33866b53_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cf08e441bafa27592ca7f62e33866b53_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cf08e441bafa27592ca7f62e33866b53_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cf5102cda8bec68df2a5a4a976bfc287_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cf5102cda8bec68df2a5a4a976bfc287_img.jpg deleted file mode 100644 index d95fbb7baaf5c09681a7252a859929718b126646..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cf5102cda8bec68df2a5a4a976bfc287_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3e0ab4117deeb4048a1ec348d23ac20176c8522eeae596f949272bd43549035b -size 30681 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cf8309144b64cc604254b140a5986dc0_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cf8309144b64cc604254b140a5986dc0_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cf8309144b64cc604254b140a5986dc0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cfc4601b8d1e0773296d4479e218648a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cfc4601b8d1e0773296d4479e218648a_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cfc4601b8d1e0773296d4479e218648a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cfdc9e67430a011b5b142ddef4cace73_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cfdc9e67430a011b5b142ddef4cace73_img.jpg deleted file mode 100644 index 122603e7db110effc13af72da09ae3194365247c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cfdc9e67430a011b5b142ddef4cace73_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cb6e62ab22f63d995d83596278899bda9da976e716f1d9e238ad5fe15d74f4 -size 4482 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cff7a537160dc428a9a77e66cce27775_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cff7a537160dc428a9a77e66cce27775_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/cff7a537160dc428a9a77e66cce27775_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d1092e8a63e409c3c459e1236218f7eb_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d1092e8a63e409c3c459e1236218f7eb_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d1092e8a63e409c3c459e1236218f7eb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d1c239cc875fea808eda1d61ca630fac_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d1c239cc875fea808eda1d61ca630fac_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d1c239cc875fea808eda1d61ca630fac_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d212408aecefb1f64e031eb855ea4537_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d212408aecefb1f64e031eb855ea4537_img.jpg deleted file mode 100644 index 67361af7f0575b83ca882330ab1f1ee35a70a2af..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d212408aecefb1f64e031eb855ea4537_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bb6b50d83ab1f6c4a50c90650081ef8a0d48ee02240077a099d585a2bb7a753e -size 27206 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d53c20c28af383ce49c214cf2603fbc3_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d53c20c28af383ce49c214cf2603fbc3_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d53c20c28af383ce49c214cf2603fbc3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d61f05240c5fba41ccba5287b05df380_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d61f05240c5fba41ccba5287b05df380_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d61f05240c5fba41ccba5287b05df380_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d6bfc6f00950b27310cac9565aa89839_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d6bfc6f00950b27310cac9565aa89839_img.jpg deleted file mode 100644 index 8edd0f1a667d2031e3e12e86d7377da438741941..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d6bfc6f00950b27310cac9565aa89839_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:adaf00e2d62488426a3f5b63eed2116488fe1b654bc1350a3e8fdd86546c7ae9 -size 203836 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d74bbadcdb9933d40a743043ad865c65_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d74bbadcdb9933d40a743043ad865c65_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d74bbadcdb9933d40a743043ad865c65_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d7b324ee9d9caae532ed5e898261c278_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d7b324ee9d9caae532ed5e898261c278_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d7b324ee9d9caae532ed5e898261c278_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d7b50eca959bf7bb5bc7a1e2fda6008b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d7b50eca959bf7bb5bc7a1e2fda6008b_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d7b50eca959bf7bb5bc7a1e2fda6008b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index 944fdccfc52993ebe91c91406d059725091c29d5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6cb4d53fe2d2f1e0b1f41eb2671ae57c1cc4708d065eb2fc4f08736872b02788 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg deleted file mode 100644 index 1f14dce7db50e3abf3462d3c6f5970ca6959c0c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d3021ea68d8cc70268f4c182da730bb775550d4dad5ac6d86ad3d294341bb49 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d98654b856f97c5210b36c88cd3dcf37_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d98654b856f97c5210b36c88cd3dcf37_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/d98654b856f97c5210b36c88cd3dcf37_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/da03733d99ab91ed54613c6799a153ba_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/da03733d99ab91ed54613c6799a153ba_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/da03733d99ab91ed54613c6799a153ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/da4b49e772815583ec294f934b9b83ad_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/da4b49e772815583ec294f934b9b83ad_img.jpg deleted file mode 100644 index 3e4bab1fec119b92508f25b5b65499adb1a9ab61..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/da4b49e772815583ec294f934b9b83ad_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:df9f3835cd37bf91743c899d8af2794e115610bad5d75df9f82e4401a5582c1d -size 39906 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index 437c7cf78526b71e63f7c07b5a0fab087cbd4555..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:66f3213da7377a9eb4bdd467bcecf2c4890129f9dbe81b9220a8e62c45d15e4c -size 4511 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/db17b491805d766560e8c237b84299f1_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/db17b491805d766560e8c237b84299f1_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/db17b491805d766560e8c237b84299f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/dda029be056105746c70a40e80692e58_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/dda029be056105746c70a40e80692e58_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/dda029be056105746c70a40e80692e58_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ddd6e04bb930e25bc5e3cd367a054516_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ddd6e04bb930e25bc5e3cd367a054516_img.jpg deleted file mode 100644 index 3df070635d19a90bdf2810b9750bd3d5ef2af339..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ddd6e04bb930e25bc5e3cd367a054516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c77ad763a0ac866f83b69caaf08e36696a4bd8d03178c90781af84c6925c37a3 -size 28526 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/de35ef8911c5beed69b407fe13b6de3c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/de35ef8911c5beed69b407fe13b6de3c_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/de35ef8911c5beed69b407fe13b6de3c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/df061c76cc6b43c8454b267631d4a585_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/df061c76cc6b43c8454b267631d4a585_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/df061c76cc6b43c8454b267631d4a585_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/df9191bd4b42f03b341734a68b1ba2e3_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/df9191bd4b42f03b341734a68b1ba2e3_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/df9191bd4b42f03b341734a68b1ba2e3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e0228f9fd9d8457847b4602308e3b060_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e0228f9fd9d8457847b4602308e3b060_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e0228f9fd9d8457847b4602308e3b060_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e09cba1dead5ed850ded796657a73b5c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e09cba1dead5ed850ded796657a73b5c_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e09cba1dead5ed850ded796657a73b5c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e0c32e027f49e7404cffe15b93075903_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e0c32e027f49e7404cffe15b93075903_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e0c32e027f49e7404cffe15b93075903_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e21c1cb4c57b5f20293a776cbdb8d31f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e21c1cb4c57b5f20293a776cbdb8d31f_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e21c1cb4c57b5f20293a776cbdb8d31f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e2810981fcbd904f97bf30226f60fcbd_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e2810981fcbd904f97bf30226f60fcbd_img.jpg deleted file mode 100644 index 786b1255791e5f644a0400eed0d25e767a328f32..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e2810981fcbd904f97bf30226f60fcbd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eedd165cfbadc0c1d0f8d385c2927963fc0b8981b2f0333f43c7505e3e1527f5 -size 90804 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e2bef29cdcf149c935e170586b26ae9c_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e2bef29cdcf149c935e170586b26ae9c_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e2bef29cdcf149c935e170586b26ae9c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e34a4d5cbb54d3807859f61780076592_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e34a4d5cbb54d3807859f61780076592_img.jpg deleted file mode 100644 index aa73f8776f3675f7c1e704dc0f7306bbaffa6e06..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e34a4d5cbb54d3807859f61780076592_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e8bc278c6be28d84fc2fa997dfdda879b3b1af513c79eb5d3b9a7ec8bbc0a930 -size 31310 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e5ae1704b289e8de1ee230e6f7200db6_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e5ae1704b289e8de1ee230e6f7200db6_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e5ae1704b289e8de1ee230e6f7200db6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e63b8cb7ecf440e9fa5f83769248f236_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e63b8cb7ecf440e9fa5f83769248f236_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e63b8cb7ecf440e9fa5f83769248f236_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e6c23e0f899f32a95b56e07037f3e6d3_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e6c23e0f899f32a95b56e07037f3e6d3_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e6c23e0f899f32a95b56e07037f3e6d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e7beed289e3bb0399e3188df934dbd85_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e7beed289e3bb0399e3188df934dbd85_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e7beed289e3bb0399e3188df934dbd85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e8edb46e6932fd994c7cbef114ad743a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e8edb46e6932fd994c7cbef114ad743a_img.jpg deleted file mode 100644 index 944fdccfc52993ebe91c91406d059725091c29d5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e8edb46e6932fd994c7cbef114ad743a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6cb4d53fe2d2f1e0b1f41eb2671ae57c1cc4708d065eb2fc4f08736872b02788 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e96f8adc46a90584fa121570e6e726ca_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e96f8adc46a90584fa121570e6e726ca_img.jpg deleted file mode 100644 index 26f3e75bf007c80b9f12d7cbc84dfc7f8d20f7b7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e96f8adc46a90584fa121570e6e726ca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c75e1e86f9e2d2314f44cf915fe548175d65e748aadbb24e290fce838c37c7e9 -size 30183 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e9f27efdab43ce5b3ecbe74f09c4cfe2_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e9f27efdab43ce5b3ecbe74f09c4cfe2_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/e9f27efdab43ce5b3ecbe74f09c4cfe2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ea5e02b97cd1bd9fe04dcc6a125b9c2e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ea5e02b97cd1bd9fe04dcc6a125b9c2e_img.jpg deleted file mode 100644 index 51ab4037795d3f956553eb3bd3ecbf3a187864e0..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ea5e02b97cd1bd9fe04dcc6a125b9c2e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c9c68f7a33ab22bba349024e7b677e21109b6f6e8beff11ffc3202dd33eda18c -size 73576 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ea6540d4c2547bccfbbd4774c5b9ae94_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ea6540d4c2547bccfbbd4774c5b9ae94_img.jpg deleted file mode 100644 index 3437ffc4a33b97c2503fbdc69e23369484107acc..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ea6540d4c2547bccfbbd4774c5b9ae94_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7631b8943a840ff292d61276960af12cea327df82e99d508be92892e296765f -size 23771 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/eb48ed8d7efab7455ebd9f62bb214f33_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/eb48ed8d7efab7455ebd9f62bb214f33_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/eb48ed8d7efab7455ebd9f62bb214f33_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ebf138e9f76230f0b227bbaba67d9699_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ebf138e9f76230f0b227bbaba67d9699_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ebf138e9f76230f0b227bbaba67d9699_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ec433eb7cb78b4d0d6fcb398bbbee89a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ec433eb7cb78b4d0d6fcb398bbbee89a_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ec433eb7cb78b4d0d6fcb398bbbee89a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ec7562b686a99409572119f7aaf7a626_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ec7562b686a99409572119f7aaf7a626_img.jpg deleted file mode 100644 index 345a6f35d2439ef4f5cbcad46ddaecd69321f511..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ec7562b686a99409572119f7aaf7a626_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64eafb2b9aa7e887ef9ae88d5eab8cd1d9c0da8374c9c6ef2c06da90f41a210a -size 98153 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ec8ccddfc249ec9ea81a9173a7fb19d8_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ec8ccddfc249ec9ea81a9173a7fb19d8_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ec8ccddfc249ec9ea81a9173a7fb19d8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ecc17272f7951b956169a2905f5862ea_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ecc17272f7951b956169a2905f5862ea_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ecc17272f7951b956169a2905f5862ea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/eda00580f1bc1ce2aa1e306b85a94dbd_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/eda00580f1bc1ce2aa1e306b85a94dbd_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/eda00580f1bc1ce2aa1e306b85a94dbd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/edeb85bb03178f34a692e6e457b61475_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/edeb85bb03178f34a692e6e457b61475_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/edeb85bb03178f34a692e6e457b61475_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ee5bafe10ff1ed7c138abb928006e86d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ee5bafe10ff1ed7c138abb928006e86d_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ee5bafe10ff1ed7c138abb928006e86d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ee78d993a5565b0f905888c3f904da99_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ee78d993a5565b0f905888c3f904da99_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ee78d993a5565b0f905888c3f904da99_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ee8c1f218854cc10676f0e2a9f3583d2_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ee8c1f218854cc10676f0e2a9f3583d2_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ee8c1f218854cc10676f0e2a9f3583d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f0c19cb19ae7a343d5f9202936fb6073_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f0c19cb19ae7a343d5f9202936fb6073_img.jpg deleted file mode 100644 index 68804ddaa8a186b25fc14ae29175212c97634f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f0c19cb19ae7a343d5f9202936fb6073_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e78da5bc2dc36fa64baa5bef1f16b795bd87eeff3dd2b57dd410544ceb390bc1 -size 4559 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f19f0f73f11a36b497d3c8ef01dff1b5_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f19f0f73f11a36b497d3c8ef01dff1b5_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f19f0f73f11a36b497d3c8ef01dff1b5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f1d870c901879a8a045ece56cc5b1980_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f1d870c901879a8a045ece56cc5b1980_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f1d870c901879a8a045ece56cc5b1980_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f2a9b517e19a3c6379baa7a815c97ca9_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f2a9b517e19a3c6379baa7a815c97ca9_img.jpg deleted file mode 100644 index 550012b818c33f337d3c2fc9600f5b7486c4f66e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f2a9b517e19a3c6379baa7a815c97ca9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:080b15dd55f9db4252bc9d014e9f70af0966dd4a1271556b9929a46d0786bd04 -size 47833 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f2ff13547dd0687104e2b303147769cf_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f2ff13547dd0687104e2b303147769cf_img.jpg deleted file mode 100644 index e06f3ddd2c4ae44d7db4801c43a32abd7ee98856..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f2ff13547dd0687104e2b303147769cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8d0dc19d12f9e42ad3f18d89e0c619ef1e26e93a9a1263f7ab32dfb86c62b127 -size 30706 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f48cf940639a2d36749ccb71f4e3faea_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f48cf940639a2d36749ccb71f4e3faea_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f48cf940639a2d36749ccb71f4e3faea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f54a2a3dde9b823d049845884cbd166a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f54a2a3dde9b823d049845884cbd166a_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f54a2a3dde9b823d049845884cbd166a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f58d0ddf50366f1a6f8965187cae3988_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f58d0ddf50366f1a6f8965187cae3988_img.jpg deleted file mode 100644 index 97f3f8ed87e7fa648248930ca790804d305594bb..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f58d0ddf50366f1a6f8965187cae3988_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15518891cdea48f983178a663dd80d3ba20fec06720e6c3d04aa3ae59e08330b -size 51640 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f609bd3fda53d5be094991a96addbf84_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f609bd3fda53d5be094991a96addbf84_img.jpg deleted file mode 100644 index 1aca55554ac616d746fe6c18d6c4257dec6c254e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f609bd3fda53d5be094991a96addbf84_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fbebd50f93a1880600ceb9d9c3962e05d41776a38f5d263661b1aa4fbb31b966 -size 61279 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f6442d68601dfecfe5f7f8a70449a2f7_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f6442d68601dfecfe5f7f8a70449a2f7_img.jpg deleted file mode 100644 index 293dae0f2b2cabf85d32334de83c917900a49c9b..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f6442d68601dfecfe5f7f8a70449a2f7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:145cacb2273400c51314ac374907401969ca9df93e7d46b242968e5b084d3f86 -size 94968 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f74adaa1840504407cd4272995426f82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f7657cea3c68ae531bb497bba529fc4a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f7657cea3c68ae531bb497bba529fc4a_img.jpg deleted file mode 100644 index 944fdccfc52993ebe91c91406d059725091c29d5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f7657cea3c68ae531bb497bba529fc4a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6cb4d53fe2d2f1e0b1f41eb2671ae57c1cc4708d065eb2fc4f08736872b02788 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f7cdc4fe8e310fe78ec0c3779b361efd_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f7cdc4fe8e310fe78ec0c3779b361efd_img.jpg deleted file mode 100644 index 46b2d59f656940e92a2ffd1d3e145858c02aae63..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f7cdc4fe8e310fe78ec0c3779b361efd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a44d94b725794c1f247c2d84651b88aa9f60723f298ca4598f77914a0659f94f -size 88514 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f92ebf4eb3d62b7dfa401644b0b6e40d_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f92ebf4eb3d62b7dfa401644b0b6e40d_img.jpg deleted file mode 100644 index 96f0958f4563ed88f34b67eda4159b6d35464aa8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f92ebf4eb3d62b7dfa401644b0b6e40d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:774a987d645a356abfc61bb7700d9c85de34eba613f52af825b221d325dde88b -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg deleted file mode 100644 index 7f6f1a395df9b03b978ed5117ea47dc62a670da4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d427ac9fd32dedcdc274176d858380294dfcbdba606f723fdaf219c4a00c1978 -size 4401 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fa9f113a14954a4741c64d911be324e9_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fa9f113a14954a4741c64d911be324e9_img.jpg deleted file mode 100644 index 293084bb1661248e9efb64ffccffd3966cf62c4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fa9f113a14954a4741c64d911be324e9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03a9102860a0dfceab546ed11a2bb8118a86be337732668fdf94ffd2415b1982 -size 4485 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fac227c65a311c313325216dcf59591f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fac227c65a311c313325216dcf59591f_img.jpg deleted file mode 100644 index b192513298ebafb100d6d2ab432fe297788b81c1..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fac227c65a311c313325216dcf59591f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:04fc346c7483a681561cf8c8c80f785114e4fcd653ac8e679a31187d61393ba7 -size 4240 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/facce731b2dbfae43a8609231a700be1_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/facce731b2dbfae43a8609231a700be1_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/facce731b2dbfae43a8609231a700be1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fb53db2423b5ba8ab6dc10dc9f384450_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fb53db2423b5ba8ab6dc10dc9f384450_img.jpg deleted file mode 100644 index 944fdccfc52993ebe91c91406d059725091c29d5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fb53db2423b5ba8ab6dc10dc9f384450_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6cb4d53fe2d2f1e0b1f41eb2671ae57c1cc4708d065eb2fc4f08736872b02788 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fbd10feb132607962f09a7f6bfb69df6_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fbd10feb132607962f09a7f6bfb69df6_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fbd10feb132607962f09a7f6bfb69df6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fbee1b51966e04afd72119133d952535_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fbee1b51966e04afd72119133d952535_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fbee1b51966e04afd72119133d952535_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index e93d8fc303ddec00fd7c477b1c79524a4d046e36..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8ccad9c11942e9b2e9a0217a9cb13cad3d7d00cb638feeddb1b6c4cb5462d8c8 -size 4577 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fdff3385d0aee2b2113ba512b60f194e_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fdff3385d0aee2b2113ba512b60f194e_img.jpg deleted file mode 100644 index f1304f7718138f9187609118649e61e6fb1ce84e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fdff3385d0aee2b2113ba512b60f194e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c9415d61445742e698e36ff7f9782beb337ec70ef12672ebd4f8911b3707ec9 -size 4527 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fe07d230fde7b9a0c4efa6ddb07e8595_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fe07d230fde7b9a0c4efa6ddb07e8595_img.jpg deleted file mode 100644 index b192513298ebafb100d6d2ab432fe297788b81c1..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fe07d230fde7b9a0c4efa6ddb07e8595_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:04fc346c7483a681561cf8c8c80f785114e4fcd653ac8e679a31187d61393ba7 -size 4240 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fe77f3082a0ce5eaa1f8f74877eb10bd_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fe77f3082a0ce5eaa1f8f74877eb10bd_img.jpg deleted file mode 100644 index 5f9121486a6b06029a93dfd88d8b88a81d391223..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fe77f3082a0ce5eaa1f8f74877eb10bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b60817bc0021987c73c38d810cef46bd87a147d22403bedaba8b2f464c0e0001 -size 4495 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fec5f1bac5cf3187f7618d1adb95871f_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fec5f1bac5cf3187f7618d1adb95871f_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fec5f1bac5cf3187f7618d1adb95871f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fec84862918481da1ffbfcd93aab02e3_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fec84862918481da1ffbfcd93aab02e3_img.jpg deleted file mode 100644 index 3f58f0028e069a0e927f502790edde416fc3f381..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/fec84862918481da1ffbfcd93aab02e3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8220076f7c13dc48fd497f919c768a1fecbf966b50465247218372aa541be7d -size 4443 diff --git a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index 6a7b5d700979fb08493635476523c9d7ce27ebc9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.CONF.0-R005-v15.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:708c62a792b4dccf06c3f4430e6d992a62b3bd2047777361e7ba5bea9b27b00c -size 4479 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/doc.md b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/doc.md deleted file mode 100644 index d03bffaabb9c139c22303f6014fc95b879b71bb7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/doc.md +++ /dev/null @@ -1,16503 +0,0 @@ - - -# --- O-RAN Working Group 4 (Open Fronthaul Interfaces WG) - -# Management Plane 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., Buschkauler Weg 27, 53347 Alfter, Germany -Register of Associations, Bonn VR 11238, VAT ID DE321720189 - -# --- Contents - -| | | -|----------------------------------------------------------------------------------------|----| -| Contents..... | 2 | -| Foreword..... | 10 | -| Modal verbs terminology..... | 10 | -| Executive summary..... | 10 | -| 1 Scope..... | 11 | -| 2 References..... | 11 | -| 2.1 Normative references..... | 11 | -| 2.2 Informative references..... | 14 | -| 3 Definition of terms, symbols and abbreviations..... | 15 | -| 3.1 Terms..... | 15 | -| 3.2 Abbreviations..... | 18 | -| 4 General..... | 19 | -| 4.1 Conventions..... | 19 | -| 4.2 Void..... | 19 | -| 4.3 Revision and compatibility handling..... | 19 | -| 4.4 Namespace compatibility handling..... | 21 | -| 5 High level description..... | 21 | -| 5.1 Top level functional description, terminology, including hybrid, hierarchical..... | 21 | -| 5.1.1 Architecture for O-RAN WG4 fronthaul functional split..... | 21 | -| 5.1.2 M-Plane architecture model..... | 22 | -| 5.1.3 Transport network..... | 23 | -| 5.1.4 M-Plane functional description..... | 24 | -| 5.1.5 Transport network considerations..... | 25 | -| 5.2 Interfaces..... | 25 | -| 5.3 YANG module introduction..... | 25 | - -| | | | -|-------|--------------------------------------------------|----| -| 5.4 | Security..... | 26 | -| 5.4.1 | General..... | 26 | -| 5.4.2 | Secure Shell (SSH)..... | 26 | -| 5.4.3 | Transport Layer Security (TLS)..... | 27 | -| 5.4.4 | File Transfer Protocol (SFTP, FTPPeS)..... | 28 | -| 5.4.5 | Representational State Transfer..... | 28 | -| 6 | "Start-up" installation..... | 28 | -| 6.1 | General..... | 28 | -| 6.2 | Management plane transport aspects..... | 32 | -| 6.2.1 | Transport establishment..... | 32 | -| 6.2.2 | O-RU identification in DHCP..... | 35 | -| 6.2.3 | Management plane VLAN discovery aspects..... | 36 | -| 6.2.4 | O-RU management plane IP address assignment..... | 36 | -| 6.2.5 | O-RU controller discovery..... | 37 | -| 6.2.6 | Certificate handling..... | 39 | -| 6.2.7 | Event-Collector discovery..... | 45 | -| 6.2.8 | Static routing of IP traffic..... | 46 | -| 6.3 | NETCONF call home to O-RU controller(s)..... | 47 | -| 6.4 | NETCONF connection establishment..... | 49 | -| 6.4.0 | General..... | 49 | -| 6.4.1 | NETCONF security..... | 49 | -| 6.4.2 | NETCONF authentication..... | 49 | -| 6.4.3 | User account provisioning..... | 50 | -| 6.5 | NETCONF access control..... | 52 | -| 6.6 | NETCONF capability discovery..... | 55 | -| 6.7 | Monitoring NETCONF connectivity..... | 56 | -| 6.8 | Closing a NETCONF session..... | 60 | -| 6.9 | PNF registration..... | 60 | - -| | | | -|--------|------------------------------------------------------------|----| -| 6.9.1 | Introduction..... | 60 | -| 6.9.2 | PNF registration procedure..... | 60 | -| 6.9.3 | Encoding of PNF registration notification..... | 61 | -| 6.10 | On-demand renewal of Call Home procedure..... | 62 | -| 6.11 | TLS sessions and certificate expiry..... | 62 | -| 7 | O-RU to O-DU interface management..... | 63 | -| 7.1 | O-RU interfaces..... | 63 | -| 7.2 | Transceiver..... | 64 | -| 7.2.1 | General..... | 64 | -| 7.2.2 | Transceiver presence change notification..... | 65 | -| 7.3 | C/U-Plane VLAN configuration..... | 66 | -| 7.4 | O-RU C/U-Plane IP address assignment..... | 66 | -| 7.5 | Definition of processing elements..... | 66 | -| 7.6 | O-DU verification of C/U-Plane transport connectivity..... | 67 | -| 7.6.1 | C/U-Plane transport connectivity verification..... | 67 | -| 7.6.2 | Ethernet connectivity monitoring procedure..... | 68 | -| 7.6.3 | IP connectivity monitoring procedure..... | 70 | -| 7.7 | C/U-Plane delay management..... | 70 | -| 7.7.1 | Introduction..... | 70 | -| 7.7.2 | Delay parameters..... | 70 | -| 7.7.3 | Reception window monitoring..... | 71 | -| 7.7.4 | External antenna delay control..... | 71 | -| 7.8 | O-RU adaptive delay capability..... | 72 | -| 7.9 | Measuring transport delay parameters..... | 72 | -| 7.10 | O-RU monitoring of C/U-Plane connectivity..... | 73 | -| 7.11 | Bandwidth management..... | 73 | -| 7.12 | IEEE 802.1X port based access control..... | 73 | -| 7.12.1 | Configuring port based access control..... | 73 | - -| | | | -|--------|-----------------------------------------------------|----| -| 7.12.2 | EAP authentication..... | 74 | -| 7.12.3 | Certificate time validation..... | 74 | -| 7.13 | Media Access Control (MAC) security..... | 75 | -| 7.13.1 | General..... | 75 | -| 7.13.2 | MACsec and MACsec key agreement..... | 75 | -| 7.13.3 | MACsec frame format..... | 75 | -| 7.13.4 | Controlled and uncontrolled port..... | 77 | -| 7.13.5 | MACsec bypass policy..... | 77 | -| 8 | Software management..... | 78 | -| 8.1 | General..... | 78 | -| 8.1.1 | Introduction..... | 78 | -| 8.1.2 | Software slots..... | 78 | -| 8.1.3 | Software management procedures..... | 79 | -| 8.2 | Software build..... | 79 | -| 8.3 | Software package..... | 79 | -| 8.3.1 | Software package name..... | 79 | -| 8.3.2 | File server storage of software package..... | 79 | -| 8.3.3 | Software package content and manifest.xml file..... | 79 | -| 8.4 | Software inventory..... | 81 | -| 8.5 | Download..... | 83 | -| 8.6 | Install..... | 85 | -| 8.7 | Bringing software into operation..... | 87 | -| 8.7.1 | Procedure..... | 87 | -| 8.7.2 | Software activation..... | 87 | -| 8.7.3 | Reset..... | 89 | -| 8.8 | Software update scenario..... | 89 | -| 8.9 | Factory reset..... | 90 | -| 9 | Configuration management..... | 90 | - -- 9.1 Baseline configuration..... 90 - - 9.1.1 NETCONF operations..... 90 - - 9.1.2 Retrieve state..... 90 - - 9.1.3 Modify state..... 91 - - 9.1.4 Retrieve parameters..... 94 - - 9.1.5 Modify parameters..... 95 - - 9.1.6 Deleting parameters..... 96 - - 9.1.7 Notification framework..... 98 - - 9.1.8 Transactions and configuration data validity..... 99 - - 9.1.9 YANG model support for target value configuration and used-value retrieval..... 99 -- 9.2 Framework for optional feature handling..... 100 -- 9.3 M-Plane operational state..... 100 -- 9.4 Notification of updates to configuration datastore..... 101 - - 9.4.1 Introduction..... 101 - - 9.4.2 Subscribing to updates from an O-RU..... 101 -- 9.5 Resetting O-RU..... 101 - - 9.5.1 O-RU reset procedure..... 101 - - 9.5.2 O-RU controller triggered O-RU reset operation..... 101 - - 9.5.3 O-RU controller triggered O-RU reset procedure..... 102 -- 10 Performance management..... 102 - - 10.1 General..... 102 - - 10.2 Measurement configuration, activation and de-activation..... 103 - - 10.3 Collection and reporting of measurement result..... 104 - - 10.3.0 Introduction..... 104 - - 10.3.1 NETCONF process for dynamic subscriptions..... 105 - - 10.3.2 File management process..... 106 - - 10.3.3 Configured subscription process..... 112 -- 11 Fault management..... 113 - -| | | | -|--------|------------------------------------------------------------------------|-----| -| 11.1 | Introduction..... | 113 | -| 11.2 | Alarm notification..... | 113 | -| 11.3 | Manage alarm subscription to NETCONF clients..... | 114 | -| 11.4 | Fault sources..... | 116 | -| 11.5 | Manage alarm notification to event-collector..... | 117 | -| 11.6 | Historical Alarms List..... | 117 | -| 12 | File management..... | 117 | -| 12.1 | Introduction..... | 117 | -| 12.2 | File system structure..... | 118 | -| 12.3 | File management operation: upload..... | 119 | -| 12.4 | File management operation: retrieve file list..... | 120 | -| 12.5 | File management operation: download..... | 121 | -| 13 | Synchronisation aspects..... | 122 | -| 13.1 | Introduction..... | 122 | -| 13.2 | Sync status object..... | 123 | -| 13.3 | Sync capability object..... | 124 | -| 13.4 | PTP configuration..... | 125 | -| 13.4.1 | Introduction..... | 125 | -| 13.4.2 | G.8275.1 specific parameters..... | 126 | -| 13.4.3 | G.8275.2 specific parameters..... | 126 | -| 13.5 | PTP status..... | 126 | -| 13.6 | PLFS/SyncE configuration..... | 127 | -| 13.7 | PLFS/SyncE status..... | 128 | -| 13.8 | GNSS configuration..... | 129 | -| 13.9 | GNSS status..... | 130 | -| 14 | Operations use cases..... | 130 | -| 14.1 | Supervision failure handling and supervision termination handling..... | 130 | -| 14.1.1 | Supervision failure handling..... | 130 | - -14.1.2 Supervision termination handling..... 131 - -14.2 Log management..... 132 - -14.2.1 Introduction..... 132 - -14.2.2 Troubleshooting log management..... 132 - -14.2.3 Security logs..... 137 - -14.3 Trace..... 140 - -14.4 Operational aspects of antenna line devices..... 142 - -14.4.1 Introduction..... 142 - -14.4.2 HDLC interworking..... 142 - -14.4.3 ALD operations..... 143 - -14.5 Operational aspects of external IO..... 145 - -14.5.1 Introduction..... 145 - -14.5.2 External input..... 145 - -14.5.3 External output..... 146 - -14.6 O-RU connectors..... 148 - -14.6.1 Introduction to O-RU connectors..... 148 - -14.6.2 Connectors related to antennas and antenna arrays..... 148 - -14.6.3 Connectors related to other O-RU functions..... 149 - -15 Details of O-RU operations..... 149 - -15.1 Retrieval of O-RU information..... 149 - -15.2 User plane message routing..... 150 - -15.2.1 Introduction..... 150 - -15.2.2 Configurable format for eAxC\_ID..... 150 - -15.2.3 U-Plane endpoint addressing..... 151 - -15.2.4 General configuration scenario..... 152 - -15.3 Carrier configuration..... 155 - -15.3.1 Carrier creation..... 155 - -15.3.2 Activation, deactivation and sleep..... 156 - -15.3.3 Carrier state's relationship to synchronization state..... 160 - -15.4 Beamforming..... 164 - -15.4.1 Beamforming configuration..... 164 - -15.4.2 Pre-defined beamforming configuration..... 165 - -15.4.3 Beamforming configuration update..... 165 - -15.4.4 Tilting pre-defined beams..... 169 - -15.4.5 Dynamic beamforming control option..... 172 - -15.4.6 Multiple beamId tables support..... 172 - -15.5 Antenna calibration..... 173 - -15.5.1 Background..... 173 - -15.5.2 Overall operation..... 174 - -15.5.3 O-RU antenna calibration capability parameter configuration..... 177 - -15.5.4 antenna-calibration-required notification parameters..... 177 - -15.5.5 Start-antenna-calibration RPC request parameters..... 178 - -15.5.6 Example antenna calibration operation..... 178 - -15.5.7 Calibration with multiple timing resource sets..... 181 - -15.5.8 antenna-calibration-multiple-time-resource-params notification parameters..... 181 - -15.6 Static configuration for PRACH and SRS..... 182 - -15.6.1 Background..... 182 - -15.6.2 Static configuration for PRACH processing..... 182 - -15.6.3 Frequency domain configuration..... 182 - -15.6.4 Time domain configuration..... 183 - -15.6.5 Operation..... 185 - -15.6.6 Static configuration for raw SRS processing..... 186 - -15.6.7 Operation..... 186 - -15.7 TDD pattern configuration..... 187 - -15.8 C-Plane message limits..... 188 - -15.9 Advanced endpoint capability report..... 188 - -15.10 U-Plane message limits..... 192 - -| | | | -|---------|---------------------------------------------------------------|-----| -| 15.11 | DRMS-BF capability and configuration management..... | 192 | -| 15.11.1 | Overview..... | 192 | -| 15.11.2 | O-RU advertised capabilities and capacity limits..... | 192 | -| 15.11.3 | O-DU configurations of parameters..... | 194 | -| 15.11.4 | DMRS-BF-EQ target value configuration..... | 194 | -| 15.12 | Description of feature SE10-MEMBER-CANDIDATE-LIST..... | 194 | -| 16 | Licensed assisted access..... | 195 | -| 16.1 | Introduction..... | 195 | -| 16.2 | LAA-initiation process..... | 197 | -| 16.2.1 | LAA module capabilities..... | 197 | -| 16.2.2 | LAA O-RU parameter configuration..... | 198 | -| 16.3 | Carrier selection..... | 199 | -| 16.3.1 | LAA measurements..... | 199 | -| 16.3.2 | LAA carrier frequency configuration..... | 199 | -| 17 | Shared cell..... | 199 | -| 17.1 | Introduction..... | 199 | -| 17.2 | Architecture..... | 199 | -| 17.3 | Start-up and Installation..... | 201 | -| 17.4 | Performance management..... | 206 | -| 17.5 | Delay management..... | 208 | -| 17.6 | Details of O-RU operations for shared cell..... | 209 | -| 17.6.1 | O-RU information for shared cell..... | 209 | -| 17.6.2 | Topology discovery procedure..... | 211 | -| 17.6.3 | Shared cell configuration on transport flow..... | 212 | -| 17.6.4 | U-plane configuration for FHM..... | 216 | -| 17.6.5 | Support of selective transmission and reception function..... | 216 | -| 17.7 | Cascade-FHM mode..... | 217 | -| 17.7.1 | Background..... | 217 | - -17.7.2 Shared cell configuration on cascaded FHMs.....217 - -18 Configured subscriptions..... 218 - -18.1 Introduction.....218 - -18.2 Description.....218 - -18.3 Procedure.....218 - -18.4 Notification encoding..... 219 - -18.5 Notification transport.....220 - -18.6 Monitoring the communications channel between O-RU and Event-Collector.....221 - -18.6.1 Background..... 221 - -18.6.2 Heartbeat encoding.....222 - -18.6.3 Heartbeat control.....222 - -18.6.4 Heartbeat procedure..... 222 - -19 Multi-Operator O-RU Operation.....224 - -19.1 Introduction.....224 - -19.2 High level shared O-RU architecture..... 224 - -19.3 Shared O-RU "start up" procedure.....228 - -19.3.1 NETCONF server user account provisioning for shared resource operators.....228 - -19.3.2 NETCONF call home to shared resource operator O-DUs.....228 - -19.3.3 Enhanced stro-id based NETCONF access control.....228 - -19.3.4 Supervision monitoring between shared O-RU and shared resource operator O-DUs.....235 - -19.4 Shared O-RU interface management..... 235 - -19.4.1 VLAN and IP address management.....235 - -19.4.2 Processing element configuration..... 235 - -19.4.3 Shared resource operator O-DU verification of C/U-Plane transport connectivity.....236 - -19.5 Shared O-RU C/U-Plane delay management..... 236 - -19.5.1 Adaptive delay operation with shared O-RU.....236 - -19.5.2 Measuring transport delay parameters with Shared O-RU.....236 - -19.6 Shared O-RU configuration management..... 236 - -| | | | -|----------|-------------------------------------------------------------------------|-----| -| 19.6.1 | Carrier configuration of the shared O-RU..... | 236 | -| 19.6.2 | Notification of configuration updates to shared resource operators..... | 237 | -| 19.7 | Shared O-RU performance management..... | 237 | -| 19.8 | Shared O-RU fault management..... | 237 | -| 19.9 | Synchronisation aspects of shared O-RU..... | 237 | -| 19.10 | Co-ordinating service impacting procedures..... | 237 | -| 19.10.1 | Reset operation..... | 237 | -| 19.10.2 | Locked administrative state..... | 237 | -| 19.10.3 | Antenna calibration..... | 238 | -| 19.11 | Partitioning of shared O-RU carrier resources..... | 238 | -| 19.11.1 | Partitioning of Shared O-RU advertised resources..... | 238 | -| 19.11.2 | Partitioning of eAxC identities..... | 238 | -| 19.11.3 | Partitioning of links, endpoints and array carriers..... | 238 | -| 19.11.4 | Partitioning of static endpoints..... | 238 | -| 19.11.5 | Shared O-RU beamforming configuration..... | 238 | -| 19.11.6 | Shared O-RU with antenna line devices..... | 239 | -| 19.12 | Example shared O-RU carrier configuration and operation procedure..... | 239 | -| 19.13 | Shared O-RU and LAA operation..... | 240 | -| 19.14 | Shared O-RU operation in combination with shared cell..... | 241 | -| 19.15 | Certificate and trust anchor management..... | 241 | -| 20 | Network energy saving..... | 241 | -| 20.1 | Introduction..... | 241 | -| 20.2 | Carrier deactivation for energy saving..... | 242 | -| 20.2.1 | High level principle of carrier deactivation for energy saving..... | 242 | -| 20.2.2 | Synchronisation aspects for carrier deactivation for energy saving..... | 242 | -| 20.3 | RF channel switch off/on for energy saving..... | 242 | -| 20.3.1 | TRX control – C-Plane controlled..... | 242 | -| 20.3.1.4 | Interaction with M-Plane processing..... | 244 | - -| | | | -|----------------------|------------------------------------------------------------|-----| -| 20.3.2 | TRX control – M-Plane controlled..... | 244 | -| 20.3.3 | Data layer control..... | 247 | -| 20.4 | Advanced sleep modes for energy saving..... | 248 | -| 20.4.1 | ASM module capabilities..... | 248 | -| 20.4.2 | Emergency wake-up procedure for ASM..... | 249 | -| 20.4.3 | Interaction with M-Plane processing..... | 249 | -| 20.5 | Deep-hibernate..... | 249 | -| 20.5.1 | Introduction..... | 249 | -| 20.5.2 | Deep-hibernate module capabilities..... | 249 | -| 20.5.3 | Configuration of deep-hibernate..... | 249 | -| 20.6 | Maximum output power control..... | 251 | -| 20.6.1 | Introduction..... | 251 | -| 20.6.2 | Maximum output power control capability..... | 251 | -| 20.6.3 | Maximum output power control configuration..... | 252 | -| 20.6.4 | Interaction with M-Plane processing..... | 253 | -| 21 | Received power measurements for shared spectrum bands..... | 253 | -| 21.1 | Introduction..... | 253 | -| 21.2 | Measurement Procedure..... | 254 | -| 21.3 | Measurement attributes..... | 254 | -| Annex A (normative): | Common alarm definition..... | 256 | -| A.1 | Introduction..... | 256 | -| Annex B (normative): | Counters..... | 268 | -| B.1 | Counter definition..... | 268 | -| B.1.1 | General..... | 268 | -| B.1.2 | Statistics calculation..... | 271 | -| B.1.3 | Frequency table generation..... | 271 | -| B.2 | Transceiver statistics..... | 272 | -| B.2.1 | Transceiver measurements..... | 272 | - -B.2.2 Statistics calculation.....272 - -B.2.3 Frequency table generation.....273 - -B.3 Rx window statistics.....273 - -B.3.1 Rx window measurement.....273 - -B.4 Tx statistics.....273 - -B.5 Energy, power and environmental statistics.....273 - -B.5.1 Statistics calculation.....273 - -B.5.2 Frequency Table Generation.....274 - -B.6 Symbol RSSI statistics.....274 - -B.6.1 Statistics calculation.....274 - -B.6.2 Frequency Table Generation.....274 - -B.7 Shared cell statistics.....274 - -B.8 Tx antenna statistics.....275 - -B.8.1 Introduction.....275 - -B.8.2 Statistics calculation.....275 - -B.8.3 Frequency Table Generation.....275 - -B.9 TSSI statistics.....275 - -B.9.1 Statistics calculation.....275 - -B.10 RSSI statistics.....275 - -B.10.1 Statistics calculation.....275 - -B.11 Tx output power statistics.....276 - -B.11.1 Statistics calculation.....276 - -B.12 Ethernet statistics.....276 - -B.12.1 Statistics calculation.....276 - -Annex C (informative): Optional multi-vendor functionality.....278 - -C.1 Optional multi-vendor namespace.....278 - -C.2 Optional YANG features.....279 - -C.3 Optional features exposed using O-RAN YANG models.....289 - -| | | -|------------------------------------------------------------------|-----| -| Annex D (informative): YANG module graphical representation..... | 307 | -| D.1 Introduction..... | 307 | -| D.2 System folder..... | 307 | -| D.2.1 o-ran-supervision.yang module..... | 307 | -| D.2.2 o-ran-usermgmt.yang module..... | 307 | -| D.2.3 o-ran-hardware.yang module..... | 308 | -| D.2.4 o-ran-fan.yang module..... | 308 | -| D.2.5 o-ran-fm.yang module..... | 308 | -| D.2.6 o-ran-ves-subscribed-notifications.yang module..... | 309 | -| D.2.7 o-ran-certificates.yang module..... | 309 | -| D.3 Operations folder..... | 310 | -| D.3.1 o-ran-operations.yang module..... | 310 | -| D.3.2 o-ran-file-management.yang module..... | 311 | -| D.3.3 o-ran-software-management.yang module..... | 312 | -| D.3.4 o-ran-lbm.yang module..... | 313 | -| D.3.5 o-ran-udp-echo.yang module..... | 313 | -| D.3.6 o-ran-ecpri-delay.yang module..... | 313 | -| D.3.7 o-ran-performance-management.yang module..... | 314 | -| D.3.8 o-ran-uplane-conf.yang module..... | 325 | -| D.3.9 o-ran-ald module..... | 339 | -| D.3.10 o-ran-troubleshooting module..... | 340 | -| D.3.11 void..... | 340 | -| D.3.12 o-ran-trace module..... | 340 | -| D.3.13 o-ran-ieee802-dot1q-cfm module..... | 340 | -| D.4 Interfaces folder..... | 341 | -| D.4.1 o-ran-interfaces.yang module..... | 341 | -| D.4.2 o-ran-processing-elements.yang module..... | 341 | -| D.4.3 o-ran-transceiver.yang module..... | 343 | - -| | | | -|-------|-------------------------------------------------------------------------------------------|-----| -| D.4.4 | o-ran-mplane-int.yang module..... | 344 | -| D.4.5 | o-ran-dhcp.yang module..... | 344 | -| D.4.6 | o-ran-externalio.yang module..... | 346 | -| D.4.7 | o-ran-ald-port.yang module..... | 347 | -| D.4.8 | o-ran-ethernet-forwarding.yang module..... | 347 | -| D.5 | Sync folder..... | 347 | -| D.5.1 | o-ran-sync.yang module..... | 347 | -| D.6 | Radio folder..... | 349 | -| D.6.1 | o-ran-module-cap.yang module..... | 349 | -| D.6.2 | o-ran-delay-management.yang module..... | 351 | -| D.6.3 | o-ran-beamforming.yang module..... | 351 | -| D.6.4 | o-ran-laa.yang module..... | 358 | -| D.6.5 | o-ran-antenna-calibration.yang module..... | 358 | -| D.6.6 | o-ran-shared-cell.yang module..... | 359 | -| D.6.7 | o-ran-laa-operations.yang module..... | 362 | -| D.6.8 | o-ran-frequency-band-measurement.yang module..... | 362 | -| | Annex E (normative): Corresponding YANG Module Definition..... | 364 | -| | Annex F (informative): Out of scope functionality..... | 366 | -| F.1 | Out of scope functionality..... | 366 | -| | Annex G (informative): o-ran-lbm.yang and o-ran-ieee802-dot1q-cfm.yang co-ordination..... | 367 | -| G.1 | Model structure..... | 367 | -| G.2 | Mapping between models..... | 368 | -| | Annex (informative):..... | 370 | -| | Change history/Change request (history)..... | 370 | - ---- - -## Foreword - -This Technical Specification (TS) has been produced by WG4 of the O-RAN Alliance. - -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. - ---- - -## Executive summary - -The present document defines the Management Plane for the O-RAN Open Fronthaul based on the selected lower-layer split point as defined within the Open Fronthaul Control Plane, User Plane and Synchronisation Plane specification. This Technical Specification is used in combination with a set of associated YANG models to enable operation of an O-RAN alliance defined O-RU. - ---- - -# 1 Scope - -The present document specifies the management plane protocols used over the fronthaul interface linking the O-RU (O-RAN Radio Unit) with other management plane entities, that may include the O-DU (O-RAN Distributed Unit), the O-RAN defined Service Management and Orchestration (SMO) functionality as well as other generic Network Management Systems (NMS). - -The present document contains both stage 2 and stage 3 material. - ---- - -# 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] Void. -- [2] O-RAN ALLIANCE O-RAN-WG4.CUS.0: "Control, User and Synchronisation Plane Specification". -- [3] IETF RFC 6241: "Network Configuration Protocol (NETCONF)". -- [4] IETF RFC 7950: "The YANG 1.1 Data Modeling Language". -- [5] IETF RFC 6242: "Using the NETCONF Protocol over Secure Shell (SSH)". -- [6] IETF RFC 4252: "The Secure Shell (SSH) Authentication Protocol". -- [7] IETF RFC 4253: "The Secure Shell (SSH) Transport Layer Protocol". -- [8] IETF RFC 2132: "DHCP Options and BOOTP Vendor Extensions". -- [9] IETF RFC 3925: "Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)". -- [10] IETF RFC 2131: "Dynamic Host Configuration Protocol". -- [11] IETF RFC 4862: "IPv6 Stateless Address Autoconfiguration". -- [12] Void. -- [13] Void. -- [14] Void. -- [15] IETF RFC 8071: "NETCONF Call Home and RESTCONF Call Home". - -- [16] Small Form Factor Committee SFF-8472v12.1 (2021): "Management Interface for SFP+." -- [17] Void. -- [18] IETF RFC 862: "Echo Protocol". -- [19] Void. -- [20] Void. -- [21] IETF RFC 5277: "NETCONF Event Notifications". -- [22] Recommendation ITU-T G.8275.1 (2022): "Precision time protocol telecom profile for phase/time synchronization with full timing support from the network". -- [23] Recommendation ITU-T G.810 (1996): "Definitions and terminology for synchronization networks". -- [24] IEEE 1588™v2 (2008): "IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems". -- [25] Recommendation ITU-T Y.1731 (2023): "Operation, administration and maintenance (OAM) functions and mechanisms for Ethernet based networks". -- [26] Antenna Interface Standards Group AISG 2.0 (2006): "Control interface for antenna line devices". -- [27] 3GPP TS 37.462 (V15.2.0): "Iuant interface: Signalling transport". -- [28] 3GPP TS 37.466 (V15.5.0): "Iuant interface: Application part". -- [29] Void. -- [30] Recommendation ITU-T X.733 (1992): "Information Technology – Open Systems Interconnection - System Management: Alarm Reporting Function". -- [31] IETF RFC 6187: "X.509v3 Certificates for Secure Shell Authentication". -- [32] 3GPP TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures". -- [33] IETF RFC 4361: "Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)". -- [34] Small Form Factor Committee SFF-8636v2.9.3 (2019): "Specification for Management Interface for Cabled Environment". -- [35] RFC-6470: "Network Configuration Protocol (NETCONF) Base Notifications". -- [36] Void. -- [37] IETF RFC 8639: "Subscription to YANG Notifications". -- [38] IETF RFC 7951: "JSON Encoding of Data Modeled with YANG". -- [39] IETF RFC 5246: "The Transport Layer Security (TLS) Protocol Version 1.2". -- [40] Void. -- [41] IETF RFC 7589: "Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 Authentication", IETF, June 2015. - -- [42] IETF RFC 8446: "The Transport Layer Security (TLS) Protocol Version 1.3". -- [43] Void. -- [44] IETF RFC 4210: "Internet X.509 Public Key Infrastructure Certificate Management Protocol". -- [45] IANA "Transport Layer Security (TLS) Parameters". -- [46] 3GPP TS 33.210: "Network Domain Security (NDS); IP network layer security". -- [47] IETF RFC 5289: "TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM)". -- [48] IETF RFC 5288: "AES Galois Counter Mode (GCM) Cipher Suites for TLS". -- [49] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)". -- [50] IEEE Std 1588™-2019: "Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems". -- [51] 3GPP TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)". -- [52] Void. -- [53] Void. -- [54] IETF RFC 4217: "Securing FTP with TLS". -- [55] IETF RFC 8996: "Deprecating TLS 1.0 and TLS 1.1". -- [56] O-RAN.WG11.TS.SecProtSpec.0 (v14.00) "O-RAN Security Protocols Specifications". -- [57] 3GPP TS 28.552: "5G performance measurements". -- [58] IETF RFC 8415: "Stateless Dynamic Host Configuration Protocol (DHCP) Service for IPv6". -- [59] IETF RFC 8525: "YANG Library". -- [60] 3GPP TS 28.532: "Management and orchestration; Generic management services". -- [61] IETF RFC 4191: "Default Router Preferences and More-Specific Routes". -- [62] IETF RFC 3442: "The Classless Static Route Option for Dynamic Host Configuration Protocol (DHCP) version 4". -- [63] IETF RFC 5656: "Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer". -- [64] IETF RFC 8341: "Network Configuration Access Control Model". -- [65] ISO 13239 (2002): "Information technology -Telecommunications and information exchange between systems -High-level data link control (HDLC) procedures". -- [66] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception". -- [67] IETF RFC 6022: "YANG Module for NETCONF Monitoring". -- [68] IETF RFC 8332: "Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) Protocol". - -- [69] IEEE 802.1Q™ (2018): "IEEE Standard for Local and Metropolitan Area Networks-Bridges and Bridged Networks". -- [70] IEEE 802.1X™ (2020): "IEEE Standard for Local and Metropolitan Area Networks-Port Based Access Control". -- [71] Void. -- [72] 3GPP TS 28.316: "Management and orchestration; Plug and connect; Data formats ". -- [73] O-RAN ALLIANCE ORAN-WG9.XPSAAS.0: "Xhaul Packet Switched Architectures and Solutions". -- [74] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation". -- [75] 3GPP TS 38.211: "NR; Physical channels and modulation". -- [76] Recommendation ITU-T G.8264 Amd1 (03/2018) "Distribution of timing information through packet networks". -- [77] Recommendations ITU-T X.731 (1992): "Information Technology – Open Systems Interconnection - System Management: State Management Function". -- [78] IETF RFC 3396: "Encoding Long Options in DHCPv4". -- [79] IETF RFC 4251: "The Secure Shell (SSH) Protocol Architecture". -- [80] IEEE 802.1CM™ (2018): "Time-Sensitive Networking for Fronthaul". -- [81] Recommendation ITU-T G.781 (2024): "Synchronization layer functions for frequency synchronization based on the physical layer". -- [82] 3GPP TS 28.111-1: "Telecommunication management; Fault Management". -- [83] O-RAN.WG11.TS.SRCS.0 (v14.00) "O-RAN Security Requirements and Controls Specifications". -- [84] IETF RFC 9525: "Service identity in TLS". -- [85] IEEE 802.1AE (2018): "IEEE Standard for Local and Metropolitan Area Networks–Media Access Control (MAC) Security ". -- [86] IETF RFC 9642: "A YANG Data Model for a Keystore". -- [87] IETF RFC 2986: "PKCS #10: Certification Request Syntax Specification Version 1.7". -- [88] 3GPP TS 37.461 (V15.5.0): "Iuant interface: Layer 1". -- [89] IEEE 802.3 (2022): "IEEE Standard for Ethernet". -- [90] IETF RFC 4191: "Default Router Preferences and More-Specific Routes". -- [91] IETF RFC 8344: "A YANG Data Model for IP Management". -- [92] IETF RFC 9640: "YANG Data Types and Groupings for Cryptography". -- [93] IETF RFC 9325: "Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)". - -- [94] IETF RFC 4344: "The Secure Shell (SSH) Transport Layer Encryption Modes". -- [95] IETF RFC 3646: "DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)". -- [96] IETF RFC 9644: "YANG Groupings for SSH Clients and SSH Servers". -- [97] IETF RFC 9645: "YANG Groupings for TLS Clients and TLS Servers". -- [98] Small Form Factor Committee SFF-8690v1.5 (2024): "Tunable SFP+ Memory Map". -- [99] IETF RFC5280: "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile". - -## 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. - -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] [ONAP](#): "VES Event Listener 7.2". -- [i.3] Metro Ethernet Forum MEF.38 (2012): "Service OAM Fault management YANG Modules". -- [i.4] [GitHub](#): "An extensible YANG validator and converter in python". -- [i.5] IETF RFC 1635: "How to Use Anonymous FTP". -- [i.6] O-RAN.WG1.NESUC-R003-v02.00: "Network Energy Saving Use Cases Technical Report". -- [i.7] O-RAN.WG11.Certificate-Management-Framework-TR.0: "Study on Certificate Management Framework". -- [i.8] WINNF-15-P-0047-V1.0.0, "SAS Functional Architecture", Wireless Innovation Forum Spectrum Sharing Committee, 7 September 2015. - ---- - -## 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. - -NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [i.1]. - -**Ad-Hoc O-RU Controller:** O-RU controllers that are not configured by DHCP when O-RU performs M-plane transport resolution and not configured by an O-RU controller using o-ran-mplane-int YANG model. - -NOTE: An O-RU does not perform call home to any Ad-Hoc O-RU Controller. - -**Advanced Sleep Mode (ASM):** Advanced sleep mode is used to achieve energy saving by disabling some fraction of the O-RU's processing for a defined or undefined period of time. - -**alarm:** a representation of an error or failure that requires attention or reaction by an operator or some machine. Alarms have state. Refer to [82] for definition. - -**antenna line:** connection between O-RU and antenna. - -**call home O-RU Controller:** O-RU controllers that are configured by DHCP when O-RU performs M-plane transport resolution as part of start-up installation procedure or that are provisioned by an O-RU controller in o-ran-mplane-int.yang. - -**cascade mode:** Mode of Shared cell which is realized by several O-RUs cascaded in chain topology. - -**Control Plane (C-Plane):** refers specifically to real-time control between O-DU and O-RU, and should not be confused with the UE's control plane - -**data layer control:** Data layer control is used to achieve energy saving in the O-RU through reducing the number of data layers independent of TRX-Control. - -**deep-hibernate:** Deep-hibernate is an O-RU operational mode used to achieve maximum energy saving by disabling all carriers. This also includes turning off the C/U/S/M Plane processing units and functions of the O-RU for a defined time period. This implies that O-RU is powered off with only the deep-hibernate timer running. - -**DownLink (DL):** data flow towards the radiating antenna (generally on the LLS interface). - -**Dense Wavelength Division Multiplexing (DWDM):** method for increasing the bandwidth of optical fibre networks by using multiple wavelengths of light. - -**Event-Collector:** A REST server to which an O-RU supporting NON-PERSISTENT-MPLANE feature can send a JSON notification, for example PNF registration. Event-collectors are configured when O-RU performs M-plane transport resolution as part of start-up installation procedure. - -**extended Antenna-Carrier (eAxC):** data flow for a single antenna (or spatial stream) for a single carrier in a single sector. - -**fault:** the (hypothesized or adjudged) cause for an error or a failure (such as system malfunctions, a defect in system design, a defect in software, or external interference). Refer to [82] for definition. - -**FHM mode:** Mode of Shared cell which is realized by FHM and several O-RUs in star topology. - -**Hierarchical O-DU:** an O-DU that is operated in isolation, or in concert with other O-DUs, e.g., in a shared O-RU deployment, such that the O-DU(s) is(are) solely responsible for the management of the O-RU. - -**High-PHY:** those portions of the PHY processing on the O-DU side of the fronthaul interface, including FEC encode/decode, scrambling, and modulation/demodulation. - -**Hybrid O-DU:** an O-DU that is operated such that it shares the responsibilities for the management of the O-RU with other non-O-DU systems, e.g. SMO. - -**Lower Layer Split (LLS):** Lower Layer Split: logical interface between O-DU and O-RU when using a lower layer (intra-PHY based) functional split. - -**Lower Layer Split Control-plane (LLS-C):** Lower Layer Split Control-plane: logical interface between O-DU and O-RU when using a lower layer functional split. - -**Lower Layer Split Synchronisation-plane (LLS-S):** Lower Layer Split Synchronisation-plane: logical interface between O-DU and O-RU when using a lower layer functional split. - -**Lower Layer Split User-plane (LLS-U):** Lower Layer Split User-plane: logical interface between O-DU and O-RU when using a lower layer functional split. - -**Low-PHY:** those portions of the PHY processing on the O-RU side of the fronthaul interface, including FFT/iFFT, digital beamforming, and PRACH extraction and filtering. - -**Management Plane (M-Plane):** refers to non-real-time management operations between the O-DU and the O-RU. - -**Multi O-DU O-RU:** O-RU that supports the **SHARED-ORU-MULTI-ODU** feature. - -**Multi-Operator O-RU:** An O-RU that supports the **SHARED-ORU-MULTI-OPERATOR** and **SHARED-ORU-MULTI-ODU** features. - -**Network Management System (NMS):** From an Open Fronthaul perspective, a generic Network Management System used to support O-RU operations. - -**north-node:** O-DU or connected O-RU closer to the O-DU for the O-RU. - -EXAMPLE: The cascade O-RU#1 connected to O-RU#2 is north-node for O-RU#2, when O-DU, O-RU#1 and O-RU#2 are in cascade chain topology. The O-DU in star topology connected to an FHM is north-node for the FHM. - -**port:** end of a transport link. - -NOTE 3: In most cases this is an optical port. - -**port number:** A number which identifies a port (see Port). - -NOTE 1: In case of SFP/SFP+ port, port number value is 0 to N-1 where N is number of ports in the device. - -NOTE 2: Numbers 0 to N-1 are assigned to ports in order following order of labels on the device (labels for ports are not necessarily numbers starting from zero). - -**PRACH symbol:** resource in the time domain having the duration of (1/Subcarrier Spacing), following cyclic prefix (excluded) in a PRACH occasion. - -NOTE: Cyclic prefix and one or more of such consecutive PRACH Symbols constitute a PRACH preamble or a NPRACH symbol group defined in 3GPP TS 36.211 [74] and 3GPP TS 38.211 [75]. - -**O-RAN Distributed Unit (O-DU):** logical node hosting PDCP/RLC/MAC/High-PHY layers based on a lower layer functional split. - -**O-RAN Radio Unit (O-RU):** logical node hosting Low-PHY layer and RF processing based on a lower layer functional split. - -NOTE: This is similar to 3GPP's "TRP" or "RRH" but more specific in including the Low-PHY layer (FFT/iFFT, PRACH extraction). - -**O-RU Controller:** network function that is permitted to control the configuration of an O-RU. - -NOTE: Examples of O-RU controllers include, an O-DU, a classical NMS, an O-RAN Service Management and Orchestration function, or other network automation platforms. - -**Security Proxy:** a Security Application Proxy which acts as an intermediary (server/client) between O-RU and management network services, by terminating the application protocols (e.g. NETCONF over TLS/SSH, FTPeS, SFTP etc), in order to authenticate the O-RU and corresponding service in the management network. - -**Service Management and Orchestration (SMO) system:** the O-RAN defined system that is responsible for RAN domain management. - -**shared cell:** operation for the same cell by several O-RUs. - -**shared cell network:** network for several cascade O-RUs in a chain topology or the network for one FHM and several O-RUs in a star topology. - -**shared O-RU Host:** role performed by the NETCONF client associated with the operator of a Multi-Operator O-RU who determines how the resources of a Multi-Operator O-RU are partitioned between Shared Resource Operators. - -**Shared Resource Operator:** role performed by the NETCONF client associated with an operator that utilizes the carrier resources of a Multi-Operator O-RU. - -NOTE 1: The Shared Resource Operator is allocated a Shared Resource Operator identity by the Shared O-RU Host. - -NOTE 2: A NETCONF client of an operator can simultaneously perform the Shared O-RU Host role and the Shared Resource Operator role. Alternatively, a NETCONF client of an operator can only perform the Shared O-RU Host role and not Shared Resource Operator role, in which case the operator corresponds to a neutral host operator. - -**software build:** consistent set of software files used for a specific radio type of a defined HW version. - -NOTE 1: Software build is subject of versioning and maintenance. - -NOTE 2: Software build is contained within a software package. - -**software package:** archive delivered by an O-RU vendor. - -NOTE: It contains one or multiple builds and can be used for one or several radio products. - -**south-node:** connected O-RU far from O-DU for the O-RU. - -EXAMPLE: The cascade O-RU#2 connected to O-RU#1 is south-node for O-RU#1, when O-DU, O-RU#1 and O-RU#2 are in cascade chain topology. The O-RU in star topology connected to an FHM is south-node for the FHM. - -**spatial stream:** data flow on the DL associated with precoded data (may be same as layers or different if there is expansion in the precoding), and on UL associated with the number of outputs from the digital beamforming (sometimes called "beams"). - -**Synchronization Plane (S-Plane):** refers to traffic between the O-RU or O-DU to a synchronization controller which is generally an IEEE-1588 Grand Master (however, Grand Master functionality may be embedded in the O-DU) - -**Synchronization Status Message (SSM):** part of ITU G.781 and G.8264 standards. - -**Transport Endpoint:** for O-RU, it is identified by an O-RU interface name, plus optional alias MAC address or optional IP address and UDP-port. For O-DU, it is identified by O-DU address and optional UDP port. - -**TRX:** refers to the specific processing chain in an O-RU associated with D/A or A/D converters. - -NOTE: Due to digital beamforming the number of TRXs may exceed the number of spatial streams, and due to analogue beamforming, the number of TRXs may be lower than the number of array elements. - -**TRX Control:** TRX control is used to achieve energy saving through disabling one or more O-RU array elements for a defined or undefined period of time. - -**Up-Link (UL):** data flow away from the radiating antenna (generally on the LLS interface). - -**User Plane (U-Plane):** refers to IQ sample data transferred between O-DU and O-RU. - -**Virtual Connection:** a connection between O-RU and O-RU controller. - -NOTE: This connection is established by means of autodetection procedure and is supervised by supervision procedure. - -## 3.2 Abbreviations - -For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [i.1] and the following apply: - -NOTE: 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]. - -| | | -|---------|----------------------------------------------| -| ALD | Antenna Line Device | -| ASM | Advanced Sleep Mode | -| AVP | Average Power | -| CA | Certificate Authority | -| CA/RA | Certificate Authority/Registration Authority | -| CBRS | Citizens Broadband Radio Service | -| CCM | Continuity Check Message | -| CMP | Certificate Management Protocol | -| CRC | Cyclic Redundancy Check | -| CUS | Control/User/Synchronisation | -| DHCP | Dynamic Host Configuration Protocol | -| DMTC | DRS Measurement Timing Configuration | -| DRS | Discovery Reference Signal | -| DSCP | Differentiated Services Code Point | -| DWDM | Dense Wavelength Division Multiplexing | -| EAP | Extensible Authentication Protocol | -| EAPOL | EAP encapsulation over LANs | -| FPGA | Field Programmable Gate Array | -| FHM | FrontHaul Multiplexer | -| FTPES | File Transfer Protocol Explicit-mode Secure | -| GPU | Graphics Processing Unit | -| HDLC | High-level Data Link Control | -| ISS | (MAC layer) Internal Sublayer Service | -| KaY | Key Agreement Entity | -| LAA | Licensed Assisted Access | -| LBM | Loop-Back Message | -| LBR | Loop Back Reply | -| LBT | Listen Before Talk | -| LLS-M | Lower Layer Split Management plane | -| MACsec | Media Access Control Security | -| ME | Maintenance Entity | -| MEP | Maintenance association End Point | -| MKA | MACsec Key Agreement | -| MSS | Maximum Segment Size | -| NACM | NETCONF Access Control Model | -| NAT | Network Address Translation | -| NDM | Non-Delay Managed | -| NETCONF | NETwork CONFigureation Protocol | -| O-DU | O-RAN Distributed Unit | - -NOTE: See clause 3.1. - -| | | -|------|------------------| -| O-RU | O-RAN Radio Unit | -|------|------------------| - -| | | -|--------|-------------------------------------------------------------| -| PAE | Port Access Entity | -| PLFS | Physical Layer Frequency Synchronization | -| PNF | Physical Network Function | -| RET | Remote Electrical Tilt | -| RPC | Remote Procedure Call | -| SAS | Spectrum Access Service | -| SecTAG | MAC Security TAG | -| SecY | MAC Security Entity | -| SFP | Small Form-factor Pluggable | -| sFTP | secure File Transfer Protocol or SSH File Transfer Protocol | -| SLAAC | StateLess Address Auto Configuration | -| SMO | Service Management and Orchestration | -| SRS | Sounding Reference Signal | -| SSH | Secure Shell | -| TEC | ThermoElectric Cooler | -| TLS | Transport Layer Security | -| TRX | Transceiver | -| T-TSC | Telecom Time Subordinate Clock. | - -NOTE: This is what ITU-T standards refer to as a Telecom Time Slave Clock - -| | | -|------|-----------------------------| -| VLAN | Virtual LAN | -| YANG | Yet Another Next Generation | - -## 4 General - -### 4.1 Conventions - -This management plane specification includes cross references to a set of associated YANG models. Text may reference particular YANG leafs, notifications and remote procedure calls (RPCs). In order to assist in readability, all cross references to YANG defined elements will keep the identical case format as defined in the corresponding YANG model, with the font-weight set to **bold**. This convention applies only to text and not to YANG elements embedded into figures. - -If there is any conflict between the YANG models and the accompanying text description in the present document, the definition of the YANG models shall take precedence. - -### 4.2 Void - -### 4.3 Revision and compatibility handling - -The revision statement in the YANG models shall be used to describe future revisions to the models that are backwards compatible, where backwards compatibility changes follow the rules specified in RFC 7950 [4], clause 11. The format of the namespace used in all O-RAN YANG models is "urn:o-ran:"" :"", where the initial used in a newly defined YANG model is "1.0". Where this document makes reference to models, irrespective of their backward compatibility, a generic of "x.y" is used to enable reference to all versions of the namespace for a particular . Backwards incompatible changes shall be addressed by incrementing the number used as part of the model name and namespace and updating the name of the model, effectively creating a new YANG model. Any backwards incompatible change to a model will change the model name - -from .yang to "x".yang, where the value "x" in the model name matches the value of "x" used in the namespace. For example, the first backwards incompatible change to o-ran-ald.yang will be included in the model named o-ran-ald2.yang and a subsequent backwards incompatible change to o-ran-ald2.yang will be included in the model named o-ran-ald3.yang. - -The revision statement in all YANG models shall include a reference statement used to cross-reference to the first version of this document where the corresponding description was introduced. For example, the reference in all revision statements for the initial O-RAN models include cross-reference to "ORAN-WG4.MP.0-v01.00". - -Each time a sub-module is modified, its revision shall be updated as well as the revision of the parent module with the same revision date. An update in the revision of the parent module shall mention the modified sub-module. - -The revision statement of the YANG models shall also include a description which is used to track the versioning of the YANG model. All revision statement descriptions begin with "version "".""."", where , and are used to reflect the version of the YANG model, where: - -- corresponds to the first digit of the O-RAN WG4 management plane specification version where the corresponding description was first introduced, corresponding to in clause 1. -- is incremented when errors in the YANG model have been corrected. -- is incremented only in working versions of the YANG model indicating incremental changes during the editing process. - -An O-RU shall use the **supported-mplane-version** leaf in o-ran-operations YANG model to provide the highest version of the O-RAN.WG4.MP.0 specification that the O-RU is compliant with. An O-RU declaring compliance to a version shall ensure that when its YANG library contains a YANG model listed in Tables E-1 and E-2 specified in the corresponding version of the O-RAN.WG4.MP.0 specification, that the revision statement date of the YANG model is no earlier than the revision date as listed in the corresponding Tables E-1 and E-2 while ensuring backwards compatibility. If an O-RU indicates it supports a particular **supported-mplane-version** and one or more modules in its YANG library have a revision statement later than the date listed in the corresponding Tables E-1 and E-2, then an O-RU controller that supports the later module revision can exercise the functionality introduced in the later revision. - -If M-Plane versions supported by the O-RU controller does not include the O-RU's M-Plane version, or if the module versions supported by the O-RU controller do not include the version of a specific module used by the O-RU, then the O-RU controller shall behave as follows to ensure backward compatibility: - -- In cases where the O-RU YANG module revision is higher than that of the O-RU controller - -O-RU Controllers that receive YANG library information from the O-RU with a module revision that is a higher version than the module revision currently used by the O-RU Controller can assume that models with the same namespace have been updated to ensure backwards compatibility. The O-RU Controller can continue to use its current module version and any unknown schema nodes and/or unknown notifications received from the O-RU, i.e. those introduced in later revisions, should be ignored by the O-RU Controller. - -NOTE 1: This allows an O-RU to be incrementally enhanced with functionality introduced in newer versions of the O-RAN.WG4.MP.0 specification while ensuring backwards compatible operation with O-RU Controllers compliant with the present document. - -- In cases where the O-RU YANG module revision is lower than that of the O-RU controller - -When an O-RU Controller receives YANG library information from the O-RU with a module revision that is a lower version than the module revision supported by the O-RU Controller, the O-RU controller operate towards the O-RU according to the O-RU's model schema that may be acquired from the operation. The O-RU controller shall not operate towards schema nodes that are not supported by the O-RU. - -NOTE 2: An O-RU Controller typically supports several selected interface versions. The set of interface versions supported by the O-RU Controller can be negotiated offline. - -NOTE 3: There have been non-backwards compatibility changes made during the development of earlier versions of the present document. This means that the YANG backwards compatibility rules described above do not accommodate these specific changes. In particular: - -- "ORAN-WG4.MP.0-v05.00" : Switched the mandatory cipher 3DES-CBC to AES128-CTR. -- "ORAN-WG4.MP.0-v06.00" : Switched from all O-RUs required to support IPv4 to enable IPv6 only O-RUs. -- "ORAN-WG4.MP.0-v07.00" : Added data-direction to the **eaxc-measured-result** list. An O-DU compliant to an earlier version of the document will ignore the leaf and not understand whether a counter corresponds to messages with dataDirection bit set to 1 or 0. -- "ORAN-WG4.MP.0-v12.00" : Switched IEEE 802.1X supplicant functionality support in O-RU from recommended to mandatory. -- "ORAN-WG4.MP.0-v16.01" : Added Simple Public Key-based SSH Client authentication by SSH server as an option for default user authentication. -- "ORAN-WG4.MP.0-v17.00" : Switched from importing ietf-crypto-types revision date 2022-12-12 to importing ietf-crypto-types revision date 2024-10-10. YANG features have been renamed in this switch, including: i) feature "p10-based-csrs" in revision date 2022-12-12 is renamed "p10-csr-format" in revision date 2024-10-10, and ii) feature "hidden-keys" in revision date 2022-12-12 is renamed "hidden-private-keys" in revision date 2024-10-10. - -## 4.4 Namespace compatibility handling - -If backwards incompatible changes have been made, the used in the YANG model namespace shall be incremented. Following such changes, an O-RU may include multiple backwards incompatible model names and namespaces in its YANG library, for example "urn:o-ran:""":1.0" and "urn:o-ran:""":2.0". - -The O-RAN Alliance's IPR policy defines terms regarding the modification of O-RAN defined specifications. When such modifications are necessary, the preferred approach for realizing such is for the third-party licensee to publish their own augmentations to the O-RAN defined YANG models and procedures. An O-RU that supports such third-party modifications shall include such model augmentations in its YANG library. Consequently, an O-RU Controller should be prepared to ignore any unknown models, e.g. developed according to such a procedure, as well as ignoring any unknown notifications defined in such models and received by an O-RU Controller that has subscribed to the O-RU's default event stream, as described in clause 9.1.7.2. - -## 5 High level description - -### 5.1 Top level functional description, terminology, including hybrid, hierarchical - -#### 5.1.1 Architecture for O-RAN WG4 fronthaul functional split - -This O-RAN FH specification addresses the lower layer functional split as depicted in Figure 5.1.1-1. Refer to the O-RAN CUS plane specification [2], clause 4.2 for more details on the split architecture. The Lower-Layer Split M-plane (LLS-M) facilitates the initialisation, configuration and management of the O-RU to support the stated functional split. - -![Diagram of O-RAN WG4 FH functional split architecture showing gNB, O-DU, O-RU, and Management System components and their interfaces.](6470d350326789d5306eabcb76533951_img.jpg) - -The diagram illustrates the O-RAN WG4 fronthaul functional split architecture. It shows a gNB containing an O-DU and an O-RU, connected by a fronthaul interface. The O-DU contains RRC, SDAP, PDCP-C, PDCP-U, RLC, MAC, and Higher PHY layers. The O-RU contains Lower PHY and RF Chain layers. The O-RAN CUS-Plane and o-RAN M-Plane are shown as interfaces between the O-DU and O-RU. A Management System is connected to the O-RU via the o-RAN M-Plane. - -Diagram of O-RAN WG4 FH functional split architecture showing gNB, O-DU, O-RU, and Management System components and their interfaces. - -Figure 5.1.1-1: O-RAN WG4 FH functional split - -#### 5.1.2 M-Plane architecture model - -A NETCONF/YANG based M-Plane is used for supporting the management features including "start up" installation, software management, configuration management, performance management, fault management and file management towards the O-RU. The M-Plane supports two architectural models: - -- 1) **Hierarchical model.** As shown on the left side Figure 5.1.2-1, the O-RU is managed entirely by one or more O-DU(s) using a NETCONF based M-Plane interface. -- 2) **Hybrid model.** As shown on the right side of Figure 5.1.2-1, the hybrid architecture enables one or more direct logical interface(s) between management system(s) and O-RU in addition to a logical interface between O-DU and the O-RU. - -In the hybrid model, the accounts of the NETCONF clients connecting to the O-RU shall be configured with one or more privilege groups that reflect the NETCONF client's responsibilities, allowing functions like O-RU software - -management, performance management, configuration management, carrier configuration and fault management to be managed directly by the management system(s). - -NOTE 1: This avoids the situation where a NETCONF client is configured with a privilege group that does not reflect its responsibilities, and where a non-compliant client can configure aspects of an O-RU which are intended to be configured by systems associated with other NETCONF clients. - -A Multi-Operator O-RU shall additionally support M-Plane architecture models which involve one or more O-DUs operated by one or more different Shared Resource Operators. Clause 19.2 describes the high level shared O-RU architecture, including hybrid and hierarchical architecture models for Multi-Operator O-RU operation with one or more different Shared Resource Operators. - -O-DUs managing an O-RU using the hierarchical model are termed "hierarchical O-DUs" and O-DUs managing an O-RU using the hybrid model are termed "hybrid O-DUs". An O-DU may be designed to operate only as a hierarchical O-DU, only as a hybrid O-DU or as both a hierarchical and hybrid O-DU, i.e. when operating with different O-RUs. - -NOTE 2: How an O-DU that is designed to manage an O-RU (either as a hierarchical or hybrid O-DU) is configured to operate in a specific mode with a particular O-RU is outside the scope of the present document. - -In the hybrid model, the O-RU has logical connectivity with the SMO. From a physical network point of view, this connectivity could be via the hybrid O-DU, using one or more of the options described in clause 5.1.5. Direct logical communication between an O-RU and SMO can be enabled via O-RUs being assigned routable IPs or local private IPs resolved by a NAT function in the network. Refer to clause 6 for details how O-RU acquires the IP address of O-DU and SMO for the M-plane communication. As described in clause 6, there is no explicit signalling to indicate that an O-RU is operating in a hierarchical or hybrid configuration. All NETCONF servers supporting this M-Plane specification shall support multiple NETCONF sessions. All O-RUs shall be able to support both hierarchical and hybrid deployment. - -![Figure 5.1.2-1: M-Plane Architecture. The diagram shows two models: Hierarchical M-Plane Model and Hybrid M-Plane Model. Both show management connections between SMOs, O-DUs, and O-RUs using NETCONF.](14252bcd35912bd656e98b16b2ee51c0_img.jpg) - -The diagram illustrates two M-Plane architectures: - -- Hierarchical M-Plane Model:** - - An SMO#1 box contains "O-DU mgmt" and "NETCONF Client". A yellow note points to it stating "O-DU OAM is out of scope of this document". - - SMO#1 is connected via a double-headed arrow to an O-DU#1 box. - - O-DU#1 box contains "O-DU mgmt" and "NETCONF Client". - - O-DU#1 is connected via a double-headed arrow to an "O-RU#1" box. - - The connection between O-DU#1 and "O-RU#1" is labeled with "1..N" near O-DU#1 and "1" near "O-RU#1". - - "O-RU#1" box contains "NETCONF Server". -- Hybrid M-Plane Model:** - - An SMO#2 box contains "O-DU mgmt" and "NETCONF Client". A yellow note points to it stating "O-DU OAM is out of scope of this document". - - SMO#2 is connected via a double-headed arrow to an O-DU#2 box. - - The connection between SMO#2 and O-DU#2 is labeled with "1..N" near SMO#2. - - O-DU#2 box contains "O-DU mgmt" and "NETCONF Client". - - O-DU#2 is connected via a double-headed arrow to an "O-RU#2" box. - - The connection between O-DU#2 and "O-RU#2" is labeled with "1..N" near O-DU#2 and "1" near "O-RU#2". - - "O-RU#2" box contains "NETCONF Server". - -Figure 5.1.2-1: M-Plane Architecture. The diagram shows two models: Hierarchical M-Plane Model and Hybrid M-Plane Model. Both show management connections between SMOs, O-DUs, and O-RUs using NETCONF. - -Figure 5.1.2-1: M-Plane Architecture - -NETCONF/YANG is used as the network element management protocol [3] and data modelling language [4]. Use of such a standardised framework and common modelling language simplifies integration between O-DU and O-RU as well as operator network integration (in terms of running service) in case of elements sharing a common set of capabilities. The framework supports integration of products with differing capabilities enabled by well-defined published data models. NETCONF also natively supports a hybrid architecture which enables multiple clients to subscribe and receive information originating at the NETCONF server in the O-RU. - -### 5.1.3 Transport network - -Based on the transport topology, various modes of network connectivity are possible between O-RU and its peers, for example O-DU and SMO. - -The basic requirement for M-Plane is to have logical connectivity between the O-RU and the elements managing it (O-DU, SMO, or so called "O-RU Controllers") as well as operational network elements such as DHCP server, CA/RA server, file server, etc. See clause 5.1.5 for detail on access technologies. - -The connectivity between the O-DU and SMO is not in scope of the present document. The O-RU shall support either IPv4 or IPv6 and optionally support dual stack (IPv4 and IPv6). - -NOTE: In previous versions of the present document, only IPv4 was mandatory. In order to ensure backwards compatibility with equipment supporting earlier versions of the present document, an operator and vendor can agree to use a common IP version in the O-RU, O-DU and any other O-RU controllers. - -## 5.1.4 M-Plane functional description - -The M-Plane provides the following major functionalities to the O-RU. These features are implemented using the NETCONF provided functions. - -### "Start-up" installation - -During start-up, the O-RU shall acquire its network layer parameters either via static (pre-configured in the O-RU) or dynamically via DHCP or DHCPv6. During this process the O-RU may acquire the IP address of the O-RU controller(s), in which case the O-RU establishes the NETCONF connectivity using the "call home" feature. When the O-RU is operating in an environment which include the O-RAN defined SMO, the O-RU may acquire the IP address of the event-collector(s), in which case the O-RU performs a `pnfRegistration` which triggers the SMO to establish NETCONF connectivity using the information recovered from the `pnfRegistration` procedure. The capability exchange shall be performed between the client and server as part of the initial NETCONF Hello exchanges. Details of these steps are provided in clause 6. - -NOTE 1: The use of "start up" terminology in the present document is distinct from the "start-up" capability used in a NETCONF environment to indicate that a device supports separate running and startup configuration datastores. - -NOTE 2: The O-RU Controller can also be used to configure additional network layer parameters, as described in clause 6.2.1. - -The present document makes specific reference to configuration which is required to be stored in "reset persistent memory". The O-RU shall use this stored configuration as its "startup" configuration. - -### SW management - -The M-Plane is used for software download, installation, validation and activation of new SW when requested by O-RU Controller. The software download is triggered by NETCONF RPC procedures, and the actual software download is performed using sFTP with SSH or FTPES with TLS as specified in RFC 4217 [54]. - -### Configuration management - -Configuration management covers various scenarios like Retrieve Resource State, Modify Resource State, Modify Parameters and Retrieve Parameters. NETCONF **get-config** and **edit-config** RPCs shall be used for configuration parameter retrieval and updates at the O-RU - -### Performance management - -Performance management describes the measurements and counters used to collect data related to O-RU operations. The purpose of Performance Management is optimizing the operation of the O-RU. - -The measurement results are reported by two options: - -- 1) **YANG Notification:** This option uses the stats definition of YANG model per measurement group. In this case, **get** RPC and/or notification are used (see clause 10 for more details). -- 2) **File Upload:** This option uses the file upload procedure defined in clause 12. The measurement results are saved to a data file periodically. - -### Fault Management - -Fault management is used for sending alarm notifications to the NETCONF Client. Fault Management allows alarm notifications to be disabled or enabled as well as alarm subscription. - -### File Management - -File management allows the O-RU Controller to trigger an O-RU to perform upload of files stored on O-RU to O-RU Controller. The O-RU may provide different kinds of files and retrieved files can be used for various purposes. Simultaneous multiple file upload operations can be supported under the same sFTP or FTPES connection between O-RU to O-DU/SMO. - -### 5.1.5 Transport network considerations - -In certain transport deployment, where fronthaul network is isolated. i.e. the O-RU does not have direct connectivity to management services, and the O-RU requires management services that are reachable by the O-DU network element managed infrastructure. The O-DU network element should be required to provide access to those services via its infrastructure. - -Examples of technologies the O-DU network element can use to provide access are: - -- Ethernet Forwarding -- IP Forwarding -- Network Address and Port Translation -- Protocol Relays/Agents e.g., DHCP Relay, DNS Resolver, etc. -- Security Proxy for TLS/SSH protected application protocols, e.g., NETCONF, FTPES, etc. - -NOTE: Administrators of management services should handle the difference between data observed on the wire by the management service and data observed on fronthaul interface, for example O-RU IP address in case of NAPT, O-RU X.509 certificate in case of Security Proxy, etc. - -The O-DU network element is configured to provide access to such services outside fronthaul network. The method to configure O-DU network element is out of scope in this present document. - -## 5.2 Interfaces - -The M-Plane interface is defined between the O-RU Controller and the O-RU. The protocol stack of the M-Plane interface is shown in Figure 5.2-1 below. The transport network layer built on IP transport, SSH/TCP, and TLS, is used to carry the M-Plane message between the O-RU Controller and the O-RU. As an option, the O-RU may support the capability to support asynchronous notifications to be sent using HTTPS. This option enables system optimisation when the O-RU Controller corresponds to the SMO which is operating with a non-persistent NETCONF session to the O-RU. - -![](b54ce9bffd341cd643e196d5f4538829_img.jpg) - -| | | | | | | | | | | | | | | -|----------------|-----|--------------------------------------------|------|--------|------------|-----------------|----------------|----------------|-----------|-------|-------|---------|-----| -| 802.1X | ARP | ICMP | DHCP | NDP | DHCPv6 | MPlane (note 1) | Notif (note 2) | Notif (note 3) | SFTP | FTPES | CMPv2 | UDPECHO | LBM | -| | | | | ICMPv6 | | NETCONF | HTTP | HTTP | | | | | | -| | | | UDP | UDP | SSH or TLS | TLS | SSH | TLS | (opt) TLS | | | | | -| | | IPv4 | IPv6 | TCP | | | | | UDP | | | | | -| | | 802.1Q tagged or (opt) untagged ETH frames | | | | | | | | | | | | -| Physical Layer | | | | | | | | | | | | | | - -NOTE 1: Management Plane Configuration Management - -NOTE 2: Asynchronous Notification over NETCONF - -NOTE 3: Asynchronous Notification over JSON/REST (Optional) - -**Figure 5.2-1: M-plane protocol stack** - -## 5.3 YANG module introduction - -The data models representing the M-Plane are organized as a set of reusable YANG modules. It is also the intent to reuse the publicly available and generic YANG models as much as possible instead of developing customized O-RAN specific modules. Refer to the various clauses, clause D and the repository of YANG models for more details on each of these modules. - -## 5.4 Security - -### 5.4.1 General - -Clause 5.4 specifies the security requirements for the O-RU. The O-RU shall provide end to end security for all OAM procedures. All O-RUs shall support SSH based security described in clause 5.4.2 and TLS based security described in clause 5.4.3. Corresponding file transfer protocols are defined in clause 5.4.4, including SFTP-based transfer over SSH and FTPES-based transfer over TLS. As per requirements in [79] clause 5.3.4.1, all O-RUs should implement robust implementations of SSH and TLS transport protocols. - -NOTE: It is recommended that operators use NETCONF/TLS and FTPES in production networks - -A summary of the mandatory and optional O-RU authentications features is shown in Table 5.4.1-1. - -**Table 5.4.1-1: Mandatory and Optional Features for O-RU Authentication** - -| Protocol | Certificate lifecycle management | PKIX (Public Key Infrastructure with X.509 Certificates) | Simple Public Key | Password-based Authentication | -|--------------------------------------------|-----------------------------------------------------------------------------------------|----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------| -| TLS 1.2 (Mandatory)
TLS 1.3 (Mandatory) | Mandatory to support CMPv2, optional to support vendor certificate lifecycle management | Mandatory to support / Optional to use | not specified for use with TLS | Not specified for use with NETCONF | -| SSHv2 (Mandatory) | Optional to support CMPv2, optional to support vendor certificate lifecycle management | Optional to support/Optional to use | Used for SSH Server authentication by SSH client (RFC 4253 [7]).
Mandatory to support / Optional to use.

Used for SSH Client authentication by SSH server (RFC 4252 [6]).
Optional to support / Optional to use. | Used for SSH Client authentication by SSH server. Mandatory to support / Optional to use | - -## 5.4.2 Secure Shell (SSH) - -The O-RU shall support NETCONF/SSHv2 as specified in RFC 6242 [5]. If there are multiple NETCONF sessions established with a single O-RU, each session should be established over a separate SSH tunnel. - -SSHv2 may be used to perform SSH client authentication, SSH server host authentication, key exchange, encryption, and integrity protection. It also derives a unique session ID that may be used by higher-level protocols. The end point (SSH client) authentication should be done as specified in RFC 4252 [6]. Clause 6.4.2 of the present document describes NETCONF authentication approach. The authentication mechanism and protocol for operators to use are as shown in Table 5.4.1-1. - -SSH algorithms supported by the O-RU are advertised by the O-RU for negotiation are configurable using ssh-transport-params container in o-ran-mplane-int module and stored in reset-persistent memory. - -The configuration capability advertised by the O-RU and provided in ssh-transport-params container shall be used as the default configuration for all the SSH-protocols (NETCONF, SFTP). - -The SSHv2 transport level security (encryption algorithms, data integrity algorithms) shall be as specified in RFC 4253 [7]. If the O-RU supports feature **ietf-ssh-common:algorithm-discovery**, the O-RU shall share the list of supported algorithms in **supported-algorithms/encryption-algorithms** container in the ietf-ssh-common module. If the O-RU supports feature **ietf-ssh-common:transport-params**, the O-RU controller can restrict the set of offered encryption algorithms by providing the configuration in **ssh-transport-params/encryption** list in the o-ran-mplane-int module. The O-RU shall support the mandatory symmetric algorithms for encrypting transferred data as specified in clause 4.1.2.2 of [56], with the following deviation: - -- support for aes256-gcm, aes128-gcm as specified in [93], aes256-ctr and aes192-ctr as specified in [94] are optional for the O-RU to support. - -For data integrity, if the O-RU supports **sshcmm:algorithm-discovery**, the O-RU shall share the list of supported algorithms in container **../supported-algorithms/mac** part of module ietf-ssh-common. If the O-RU supports feature **ietf-ssh-common:transport-params**, the O-RU controller can restrict the set of offered data integrity algorithms by providing the configuration in **../ssh-transport-params/mac** part of module o-ran-mplane-int. The O-RU shall support the mandatory message authentication codes (MACs) specified in clause 4.1.2.4 of [56], with the following deviation: - -- support for hmac-sha2-512-etm, hmac-sha2-512, hmac-sha2-256-etm and umac-128 are optional for the O-RU to support. - -Public key-based host authentication shall be used for authenticating the server by the clients, and username/password-based client authentication shall be done by the server as part of the SSH session establishment as specified in RFC 4253 [7]. If the O-RU supports **ietf-ssh-common:algorithm-discovery**, the O-RU shall share the list of supported algorithms in container **../supported-algorithms/public-key-algorithms** part of module ietf-ssh-common. If the O-RU supports feature **ietf-ssh-common:transport-params**, the O-RU controller can restrict the set of offered host key algorithms by providing the configuration in **../ssh-transport-params/host-key** part of module o-ran-mplane-int. The O-RU shall support the host key algorithms and key exchange methods for securing the Secure Shell (SSH) transport, as specified in clause 10.1 of RFC 5656 [63]. The O-RU shall support the mandatory key agreement algorithms, may support the optional key agreement algorithms and shall not support the prohibited key agreement algorithms, as specified in clause 4.1.2.1 of [56], with the following deviation: - -- support for ssh-ed25519 is optional for the O-RU to support. - -If the O-RU supports **ietf-ssh-common:algorithm-discovery**, the O-RU shall share the list of supported key exchange algorithms in container **../supported-algorithms/key-exchange-algorithms** part of module ietf-ssh-common. If the O-RU supports feature **ietf-ssh-common:transport-params**, the O-RU controller can restrict this list by editing list in **../ssh-transport-params/key-exchange** part of module o-ran-mplane-int. The O-RU shall support the mandatory key - -exchange methods and shall not support the prohibited key exchange methods as specified in clause 4.1.2.3 of [56], with the following deviation: - -- support for diffie-hellman-group-exchange-sha256 and curve25519-sha256 are optional for the O-RU to support. - -The O-RU should support the following host key algorithms as specified in RFC 8332 [68]: - -- rsa-sha2-256 -- rsa-sha2-512 - -In order to ensure backwards compatibility with equipment supporting earlier versions of the present document, a vendor may provide support for other, optional non-broken host key algorithms and key exchange methods. - -NOTE 1: A "non-broken" algorithm is an algorithm without publicly available/published vulnerabilities. - -As an additional option, both client and server may implement authentication based on X.509 certificates. With this option, RSA 2048 bit shall be supported for the Public Key algorithm, aes128-ctr shall be supported for the ciphering algorithm and hmac-sha2-256 shall be supported for integrity algorithm. - -NOTE 2: The vendor and operator need to be prepared to replace integrity and/or ciphering algorithms if the current algorithm in use is compromised or deprecated. - -## 5.4.3 Transport Layer Security (TLS) - -An O-RU shall support Transport Layer Security (TLS) as specified in O-RAN Security Protocols Specifications [56] clause 4.2 to ensure secure and authenticated communication with O-RU Controllers. To be able to setup a mutual TLS (mTLS) connection, both parties need to have an X.509 certificate to show their identities. Clauses 6.2.6.1 and 6.2.6.2 explain how to do certificate enrolment to get a certificate issued from a Certificate Authority of operator choice. Clause 6.2.6.3 explains how vendor-signed certificates can be used, in certain conditions. A Trust Anchor (a CA certificate or a subCA in the certificate chain of the peer certificate) is needed to verify whether a peer certificate is to be trusted. The options for provisioning of Trust Anchors to an O-RU are described in clause 6.2.6.0. - -TLS requirements specified in O-RAN Security Protocols Specifications [56] clause 4.2 shall apply. The specification for TLS 1.3 [42] includes a procedure for negotiating fallback to TLS 1.2 that is mandatory to support. - -The O-RU shall support NETCONF over TLS as specified in RFC 7589 [41]. - -NETCONF server identity shall be as specified in clause 4 of RFC 9525 [84] and NETCONF client identity shall be as specified in clause 7 of RFC 7589 [41]. Each instance of a NETCONF session shall have a separate TLS session. - -When no operator trust anchor(s) have been provisioned in the O-RU, i.e., during the initial bootstrapping of the O-RU, the O-RU shall trust the certificate received on first contact with a TLS peer (Trust on First Use). Once a valid operator trust anchor has been provisioned, as described in clause 6.2.6.0, the O-RU shall validate all peer certificates during TLS authentication. An O-RU shall use a valid certificate issued by an operator PKI and may use a vendor PKI to establish a mutually authenticated TLS connection for secure signalling with an O-RU Controller(s). The O-RU shall prioritize use of the operator certificate when it is available. - -TLS implementations shall comply with the cipher suite requirements defined in clause 4.2.2 of the O-RAN Security Protocols Specifications [56]. TLS implementations shall follow TLS 1.2 and TLS 1.3 profiling defined in clause 4.2.2 of the O-RAN Security Protocols Specifications [56]. - -TLS cipher suites and TLS versions acceptable by O-RU are configurable using **hello-params** container in o-ran-mplane-int.yang module and stored in reset-persistent memory. The configuration provided in this **hello-params** container shall - -be used as the default configuration for all the TLS-protocols (NETCONF, FTPes, HTTPS) which may be refined by a protocol-specific YANG model. - -#### 5.4.4 File Transfer Protocol (SFTP, FTPes) - -An O-RU shall support SFTP based secure file transfer over SSH and FTPES based secure file transfer over TLS. - -Security file transfer requirements specified in O-RAN Security Protocol Specifications [56] clauses 6.2 and 6.3 shall apply. - -#### 5.4.5 Representational State Transfer - -An O-RU may optionally support of JSON/REST transported over HTTPS. - -NOTE: JSON/REST is used by O-RUs supporting the NON-PERSISTENT-MPLANE feature and the configured subscriptions capability described in clause 18. - -HTTPS requirements specified in O-RAN Security Protocol Specifications [56] clause 6.4 shall apply. - ---- - -## 6 "Start-up" installation - -### 6.1 General - -This clause provides the overall start-up mechanism from the power-on of O-RU to available in service. - -**Pre-condition:** - -- Power-ON for O-RU/NETCONF Server or O-RU restart operation. O-RU enables its port(s). -- O-RU controller/NETCONF Client(s) and/or event-collector is/are in operation. -- Physical interface(s) is(are) connected to a compatible Ethernet port. - -**Post-condition:** - -- O-RU is running software from slot with active = TRUE -- O-RU has marked slot with currently used software as running = TRUE -- O-RU is ready for the radio transmission to the air on at least one carrier if packet transmission received from O-DU -- O-RU is ready for the packet transmission to the O-DU if radio reception received at the air on at least one carrier. -- At least one O-RU Controller/NETCONF client with either "sudo" or "hybrid-odu" access privileges can control the carrier configuration of the O-RU/NETCONF server in O-RU. - -![Sequence diagram showing the interaction between O-RU (NETCONF Server), NETCONF Client, and pnfRegistration Event Collector. The sequence includes steps for 802.1X authentication, transport layer initialization, operator PKI enrollment, synchronization, home/pnfRegistration calls, secure connection establishment, capability discovery, schema retrieval, and various management and configuration tasks.](47a7beddcb8a1b7abdca746967e32bb4_img.jpg) - -``` - -sequenceDiagram - participant O-RU as O-RU (NETCONF Server) - participant NETCONF Client - participant pnfRegistration Event Collector - - Note right of O-RU: opt [O-RU performs 802.1X authentication] - Note right of O-RU: 1. Supplicant PAE Enabled - Note right of O-RU: 2. O-RU sends EAPOL-Start followed by EAP dialogue - alt EAP Failure: 3. O-RU provides unauthenticated connectivity - alt EAP Success: 4. O-RU provides authenticated connectivity - Note right of O-RU: 5. Transport Layer Initialization - Note right of O-RU: opt [O-RU enrolls in operator PKI] - Note right of O-RU: 6. O-RU installs operator issued certificate and trust anchor - Note right of O-RU: 7. O-RU re-initializes restart procedure (jump to step 1.) - Note right of O-RU: 8. O-RU begins synchronization to primary reference clock - Note right of O-RU: O-RU calls home and/or performs pnfRegistration - Note right of O-RU: opt [O-RU Discovers NETCONF Call Home server] - Note right of O-RU: 9. O-RU calls home to NETCONF client(s) - Note right of O-RU: opt [O-RU Discovers pnfRegistration Event-Collector] - Note right of O-RU: 10. O-RU registers to Event-Collector - Note right of O-RU: 11. SSH or TLS Secure Connection Established - Note right of O-RU: 12. NETCONF Capability discovery - Note right of O-RU: opt [O-RU supports NETCONF Monitoring] - Note right of O-RU: 13. Retrieval of O-RU schemas - Note right of O-RU: 14. Optional provisioning of new management accounts - Note right of O-RU: 15. Supervision of NETCONF connection - Note right of O-RU: 16. Retrieval of O-RU information - Note right of O-RU: 17. Software management - Note right of O-RU: 18. CU-Plane transport configuration - Note right of O-RU: 19. LBM configuration (CU-Plane transport over ETH) or UDP Echo enabling (CU-Plane transport over IP) - Note right of O-RU: 20. CU-Plane transport connectivity check between O-DU and O-RU - Note right of O-RU: 21. Retrieval of the O-RU Delay Profile - Note right of O-RU: 22. U-plane configuration between O-DU and O-RU - Note right of O-RU: 23. Optional CU-Plane delay measurements between O-DU and O-RU - Note right of O-RU: 24. Fault Management activation - Note right of O-RU: 25. Performance measurement activation (if required at start-up timing) - Note right of O-RU: 26. Retrieval of O-RU state including synchronization information, from O-RU - Note right of O-RU: 27. Configuring the O-RU operational parameters - Note right of O-RU: 28. Service available - -``` - -Sequence diagram showing the interaction between O-RU (NETCONF Server), NETCONF Client, and pnfRegistration Event Collector. The sequence includes steps for 802.1X authentication, transport layer initialization, operator PKI enrollment, synchronization, home/pnfRegistration calls, secure connection establishment, capability discovery, schema retrieval, and various management and configuration tasks. - -**Figure 6.1-1: Overall of Start-Up Installation** - -At the power-on of O-RU or following an O-RU restart, the following procedures are performed, as illustrated in Figure 6.1-1. - -- 1) (opt) Supplicant PAE is enabled on the port(s). -- 2) (opt) The O-RU initiates authentication and attempts to perform an EAP authentication dialogue with a peer Authenticator PAE. - -NOTE 1: This does not limit the ability of an Authenticator PAE to initiate the authentication, as defined in clause 8.1 of [70] - -- 3) (alt) EAP failure results in O-RU providing unauthenticated connectivity. -- 4) (alt) EAP Success results in O-RU providing authenticated connectivity. -- 5) O-RU performs M-Plane transport layer resolution (DHCP, MAC, VLAN, IP, etc.) and recovers IP address(es) of O-RU controller(s) and/or pnfRegistration event-collector. -- 6) (opt) If DHCP response contains CA/RA address information and the O-RU has not already enrolled in the operator PKI, or the certificate issued during previous enrolment has expired, the O-RU attempts to enrol. -- 7) (opt) After installing the operator issued certificate, the O-RU re-initializes its start-up procedure (jump to step 1). -- 8) O-RU begins synchronisation of the O-RU against a Primary Reference Clock. Step 8 may be in parallel with step 5 for some O-RU implementation. -- 9) (opt) O-RU performs NETCONF Call Home to discovered O-RU controller(s). -- 10) (opt) O-RU performs pnfRegistration to discovered event-collector. -- 11) O-RU controller performs SSH or TLS connection establishment. -- 12) O-RU and O-RU controller perform NETCONF capability discovery. -- 13) (opt) O-RU controller retrieves O-RU schemas using RPC [67]. -- 14) O-RU controller performs optional provisioning of new management accounts (typically only performed once during pre-staging). O-RU controller may perform provisioning of certificate-to-NETCONF username mapping information to the O-RU after account provisioning in case certificate-based client authentication is used. O-RU controller may perform provisioning of ordered cipher suite and TLS versions acceptable by O-RU (see **hello-params** container in o-ran-mplane-int.yang module). O-RU controller may perform provisioning of SSH algorithms (Refer to clause 5.4.2) -- 15) O-RU and O-RU controller perform supervision of NETCONF connection. -- 16) O-RU controller performs retrieval of O-RU information. (opt) O-RU controller retrieves O-RU S-Plane information and if necessary, it updates the O-RU's S-Plane configuration. (This step may be started any time after step 15 but needs to be completed before step 28). -- 17) O-RU controller performs SW management. - -NOTE 2: If an O-RU is running with factory default software, the O-RU functionality is permitted to comprise a sub-set of a fully operating O-RU. In such scenarios, it is recommended that the O-RU controller triggers a software update to fully functioning O-RU software. - -- 18) O-DU performs CU-Plane transport configuration. -- 19) (opt) O-DU performs LBM configuration (CU-Plane over ETH) or enables UDP Echo (CU-Plane over IP). -- 20) (opt) O-DU performs initial C/U-Plane transport connectivity checking between O-DU and O-RU. -- 21) O-RU controller retrieves the O-RU delay profile from the O-RU. -- 22) O-RU controller performs U-Plane configuration between O-DU and O-RU. C/U-Plane transport connectivity between O-DU and O-RU is configured as part of this step. -- 23) O-DU optionally performs C/U-Plane delay measurements between O-DU and O-RU if the O-RU supports it. -- 24) O-RU controller performs Fault Management activation by creating a subscription to the YANG notifications defined in the o-ran-fm.yang model. Additionally, the O-RU controller uses the same YANG model to retrieve the list of O-RU's active alarms. See Clause 11 for details. -- 25) O-RU controller activates performance measurement (if required at start-up timing). -- 26) O-RU controller retrieves O-RU state, including synchronisation information, from O-RU. -- 27) O-RU controller configures the O-RU operational parameters. -- 28) Service available. - -Additional Start-up considerations: - -- The synchronisation procedures started in step 8 needs to be completed before service is available. If the O-RU's power-on S-Plane settings are incompatible with the network's S-Plane design, then at step 16 the O-RU controller should reconfigure the O-RU's S-Plane settings. -- Periodic CU-Plane connectivity check is not considered as the part of start-up. Once configured in start-up phase, CU-Plane connectivity check can later be performed periodically and at any time in run-time. -- The details of the above start-up procedure are covered in sub-clauses 6.3 to 6.7. - -Cross Reference to other clauses: - -- The details of 8, 16 and 26. Synchronisation management is described in clause 13. -- The method of 13 and 26 retrieval of O-RU information is described in clause 9. -- The detail of 17. SW management is described in clause 8. -- The detail of 20. C/U-Plane transport connectivity checking between O-DU and O-RU is described in clause 7. -- The detail of 21. Retrieval of the O-RU delay profile and 23. C/U-Plane delay measurements are described in clause 7. -- The detail of 22. U-plane configuration is described in clause 15, and C/U-Plane transportation configuration is described in clause 7. -- The detail of 25. Performance management is described in clause 10. -- The detail of 24. Fault management is described in clause 11. -- The method of 27. Control to make service available is described in clause 15. - -## 6.2 Management plane transport aspects - -### 6.2.1 Transport establishment - -This clause provides the M-plane transport establishment scenario between O-RU and O-RU controller(s), such as O-DU and/or SMO. The transport layer address of M-plane is only the target in this clause. Transport aspects of the C plane and U plane are covered in clause 7. - -**Pre-condition:** - -- Physical interface is connected to a compatible Ethernet port. -- When operating in an environment using call-home, the NETCONF server and NETCONF Client(s) have an identical NETCONF call home port configured, to ensure the NETCONF client listens on the same port used by the NETCONF Server. - -**Post-condition:** - -- Transport Layer address(es) for M-plane are known to O-RU and O-RU controllers. -- O-RU is aware of the physical port(s) for M-plane, e.g. if there are multiple ports in the O-RU. -- O-RU is aware of the VLAN(s) to be used for M-Plane, e.g. if VLANs are used in the transport network. -- Then O-RU is ready to establish TCP connection for NETCONF call home and/or for PNF registration. - -For the transport establishment, there are the following alternatives, as illustrated in Figure 6.2.1-1: - -- Manual transport layer address configuration in O-RU. This configuration contains the addresses for O-RU and NETCONF client(s) and/or the event-collector. The method to manually configure the O-RU is out of scope in the present document. Assuming manual configuration is successful, the NETCONF server shall be able to recover this configured information and use the **client-info** container in the o-ran-mplane-int.yang model to expose this information to a NETCONF client. -- If IPv4 is supported, DHCP server provides O-RU's transport layer address information together with the identity of the NETCONF client and/or the identity of the event-collector. This identity encodes either the transport layer address or FQDN of the NETCONF client or event-collector. If an FQDN is signalled, the O-RU shall use the DNS server address provided by the DHCP server, as specified in RFC 2132 clause 3.8 [8], to recover the IP address corresponding to FQDN of the NETCONF client or event-collector. -- If IPv6 is supported, Stateless Address Auto-Configuration (SLAAC) is used to configure the O-RU's transport address with the DHCPv6 server providing the identity of the NETCONF client and/or event-collector. This identity encodes either the transport layer address or FQDN of the NETCONF client or event-collector. If an FQDN is signalled, the O-RU shall use the DNS server address provided by the DHCPv6 server, as specified in RFC 3646 clause 3 [95], to recover the IP address corresponding to FQDN of the NETCONF client or event-collector. -- A NETCONF Client with suitable privileges can use the ietf-interfaces YANG module augmented by ietf-ip and o-ran-interfaces YANG modules to configure the O-RU's IPv4 and/or IPv6 **ip** address and associated subnet/prefix, together with **port-reference** and optional **vlan-id**. In this case the **origin** parameter from ietf-ip.yang module shall be set to "**static**". Assuming configuration is successful, the NETCONF server shall be able to operate with the configured network layer parameters provided by the NETCONF Client. The NETCONF server shall use the **client-info** container in the o-ran-mplane-int.yang model to expose NETCONF client information to other NETCONF clients. - -NOTE: A NETCONF client can receive a hint as to whether an O-RU supports a particular IP version by using the **get** RPC to recover the list of **interfaces** supported by the O-RU and using the presence of the augmented **ipv4** container or **ipv6** container in the o-ran-interfaces module as an indication that a particular IP version is supported. - -The O-RU uses the o-ran-dhcp.yang model to be able to expose information signalled by the DHCP server. - -![Sequence diagram for Transport Layer Establishment for M-plane. Lifelines: Technician, O-RU (NETCONF Server), Router, DHCP, O-DU or SMO (NETCONF Client). The process includes Manual Configuration and Automatic Configuration (Stateful DHCP, Stateless DHCPv6, and NETCONF Client configured parameters).](f5a5f52bc25d95a7f616290c99e88ae6_img.jpg) - -``` - -sequenceDiagram - participant Technician - participant O-RU as O-RU (NETCONF Server) - participant Router - participant DHCP - participant O-DU as O-DU or SMO (NETCONF Client) - - alt Manual Configuration - Note right of Technician: Manual configuration - else Automatic Configuration - alt Stateful DHCP - opt IPv6 - O-DU->>Router: Router Solicitation - Router-->>O-DU: Router Advertisement - end - O-DU->>DHCP: DHCP Discover/Solicit - DHCP-->>O-DU: DHCP Offer/Advertise -NETCONF Client Identity and/or Event-Collector Information - O-DU->>DHCP: DHCP Request/Request - DHCP-->>O-DU: DHCP ACK/Reply -NETCONF Client Identity and/or Event-Collector Information - else Stateless DHCPv6 - O-DU->>Router: Router Solicitation - Router-->>O-DU: Router Advertisement - Note right of O-DU: Create IPv6 Address - O-DU->>Router: Duplicate Address Detection - O-DU->>DHCP: DHCPv6 Request Information - DHCP-->>O-DU: DHCPv6 Reply -NETCONF Client Identity and/or Event-Collector Information - else Network layer parameters configured by NETCONF Client - O-DU->>O-RU: - O-RU-->>O-DU: - end - end - -``` - -Sequence diagram for Transport Layer Establishment for M-plane. Lifelines: Technician, O-RU (NETCONF Server), Router, DHCP, O-DU or SMO (NETCONF Client). The process includes Manual Configuration and Automatic Configuration (Stateful DHCP, Stateless DHCPv6, and NETCONF Client configured parameters). - -Figure 6.2.1-1: Transport Layer Establishment for M-plane - -Transport Layer interface related information for M-plane contains at least the physical port number, the hardware address of the Ethernet port, VLAN-ID, local IP address, remote IP address, Default Gateway address and Subnet mask. - -In the case of option b) and c), the following clauses are used: - -- O-RU identification in DHCP messages from O-RU (clause 6.2.2). -- VLAN discovery aspect for M-plane (clause 6.2.3). -- IP address assignment to O-RU (clause 6.2.4). -- Discovery of address information of O-RU controller(s) and/or Event-Collector (clause 6.2.5 and/or clause 6.2.7). - -## 6.2.2 O-RU identification in DHCP - -The O-RU shall use the DHCP Vendor Class option(s) with the **vendor-class-data** string within the o-ran-dhcp YANG model or vendor identifying vendor class option with enterprise number and vendor-class-data to identify itself as an O-RU to DHCP servers. When the O-RU supports IPv4, it shall identify itself either 1) use option 60 Vendor Class Identifier, as specified in RFC 2132 [8], OR 2) use option 124 Vendor Identifying Vendor Class Option, as specified in RFC 3925 [9]. When the O-RU supports IPv6, it shall identify itself using the DHCPv6 Vendor Class Option 16. - -O-RU can identify itself with both O-RAN registered IANA Enterprise Number and 3GPP registered Enterprise Number when using option 124 to retrieve O-RU controller, event controller and CA/RA information in DHCPv4 server. If an O-RU intends to get only O-RAN domain information, O-RU can use opt 60 or opt 124 with only O-RAN enterprise number. - -NOTE: To support DHCP server implementations that are limited in their support for multiple instances of the Vendor-Specific Information Options, an operator and vendor can agree to use the O-RAN registered IANA Enterprise Number in DHCPv4/DHCPv6 messages to identify itself to signal the CA/RA server information. - -### DHCPv4 Vendor Class Option: - -- Option: 60 -- Vendor Class Identifier Option 60: string - -The format of the vendor class string shall be configured to one of the following three options: - -- 1) "o-ran-ru2/", e.g. "o-ran-ru2/vendorA". -OR -- 2) "o-ran-ru2//", e.g. "o-ran-ru2/vendorA/ORUAA100". -OR -- 3) "o-ran-ru2///", e.g. "o-ran-ru2/vendorA/ORUAA100/FR1918010111". - -The Vendor Class Identifier should be selected to avoid the likelihood that different vendors select identical strings, e.g. using a vendor namespace registry or ensuring that the identifier includes the information. - -### DHCPv4 Vendor-Identifying Vendor Class Option: - -- Option: 124 -- Enterprise number: O-RAN-alliance 53148 - -- Vendor-Class-Data: the format of the string shall follow the rules defined for the DHCPv4 Vendor Class Option - -#### DHCPv6 Vendor Class Option: - -- Option: 16 -- Enterprise number: O-RAN-alliance 53148 -- Vendor-Class-Data: the format of the string shall follow the rules defined for the DHCPv4 Vendor Class Option - -The DHCP Server may use the information when selecting an address pool from which to allocate an IP address to the O-RU or when selecting which management plane O-RU Controller information to configure in the O-RU. - -### 6.2.3 Management plane VLAN discovery aspects - -The O-RU is connected to one or more Ethernet ports. The transport systems may be realized such that these Ethernet ports is/are configured either as an access port, where untagged Ethernet frames are used, or as a trunk port, where multiple VLANs are configured. During start up, the O-RU is typically unable to immediately determine whether its ports are attached to remote transport equipment configured for access or trunk mode operation. - -Once an O-RU completes its boot-up sequence and Ethernet connectivity is detected on at least one of its Ethernet interfaces, the O-RU starts management plane connection establishment. - -The O-RU shall determine whether it is connected to an access port or a trunk port. In particular, when connected to a trunk port, the O-RU shall additionally determine the VLAN identity/ies used to support the management plane communication(s). The VLAN(s) used to support management plane communications can be identified by the DHCP server replying to the DHCP DISCOVER message, as described in clause 6.2.5, clause 6.2.7 or clause 6.2.6.1. - -NOTE 1: An O-RU which supports IPv6 can infer that a VLAN is not used to support management plane communications if it receives an IPv6 Router Advertisement without either the "managed address configuration" or "other configuration" bits set. - -NOTE 2: Versions prior v12.0 of the present document did not define management plane VLAN discovery based on CA/RA server identity as specified in clause 6.2.6.1. When operating with O-RUs that support an earlier version of this documents, an operator wanting to operate a VLAN that restricts access to production O-RU controllers, e.g. offering sole access to a CA/RA server, can configure a dummy NETCONF client identity to be returned to the O-RU in the DHCP OFFER message. - -If the O-RU does not have previously configured management plane VLAN information, the O-RU shall attempt to discover DHCP servers on all its Ethernet ports using untagged Ethernet frames. - -When the O-RU has been previously configured with management plane VLAN information, the O-RU may use this information to optimize its discovery of the VLAN ID(s) used for management plane connectivity. Previously configured management plane VLAN information includes an O-RU that stores the last VLAN(s) used for management plane connectivity, and/or an O-RU which has been previously configured with a range of management plane VLANs by a NETCONF client using the contents of the **searchable-mplane-access-vlans-info** container that have been stored in reset-persistent memory. The O-RU may use this information to optimize its discovery of the VLAN ID(s) used for management plane connectivity. - -If the O-RU does not receive a DHCP OFFER from a DHCP server using untagged frames, or previously configured VLANs, the O-RU should attempt to contact a DHCP server using the full range of VLAN IDs (1~4094) on all its Ethernet ports. - -The individual VLAN search algorithm used by an O-RU should ensure timely activation of the M-Plane while accommodating scenarios whereby there may be an intermittent or temporary connectivity problem between the O-RU and the DHCP server causing no DHCP response to be received on the M-Plane VLAN. The O-RU should repeatedly search using untagged frames and previously configured VLANs whenever it searches across the full range of VLAN IDs. The O-RU controller is able to recommend the maximum interval between repeatedly scanning for M-Plane connectivity on the untagged and configured VLANs using the **scan-interval** schema node. - -For example, the default **scan-interval** is 60 seconds. If the O-RU takes 1 second to scan an individual VLAN, then after scanning every 60 out of the full range of VLAN IDs, the O-RU should repeat the scan for M-Plane connectivity on untagged and configured VLANs. - -## 6.2.4 O-RU management plane IP address assignment - -Automatic IP address assignment for the O-RU management plane can be achieved using different techniques: - -- 1) IPv4 configuration using DHCPv4, as described in RFC 2131 [10] enables DHCP servers to configure IPv4 network address(es) on the O-RU. An O-RU implementing IPv4 shall support the behaviour specified in clause 6.1 of RFC 4361 [33], using stable DHCPv4 node identifiers in their **dhcp-client-identifier** option. - -A network realized with multiple DHCP servers should ensure that their configurations are coordinated to ensure a common default gateway is provisioned in an O-RU which receives multiple DHCPv4 responses, e.g. when received over different interfaces. - -An O-RU may indicate that it supports configuration of routing information as specified in RFC 3442 [62], enabling static routes to be used by the O-RU when determining how to route uplink packets, e.g. when the O-RU supports multiple interfaces. - -For O-RUs that support IPv6, both stateful and stateless address assignment procedures are supported: - -- 2) IPv6 Stateless Address Auto-Configuration (SLAAC), RFC 4862 [11] enables the O-RU to generate link-local and global addresses. - -A network realized with multiple IPv6-enabled routers that support dynamic address assignment should use the extensions to Router Advertisements as specified in RFC 4191 [61] to configure the preference of the default route prefixes learnt by the O-RU using SLAAC. - -- 3) IPv6 State-full address configuration uses DHCPv6, as specified in RFC 8415 [58] and enables DHCP servers to configure IPv6 network address(es) on the O-RU. DHCPv6 is transported using UDP, using the link-local address on the O-RU and a link-scoped multicast address on the DHCP server. - -NOTE 1: The above does not restrict the realisation of the DHCP server, which can be integrated with the O-DU, can be provided by the transport system, or can be accessed via a relay. - -O-RUs that support more than one network interface should use a different client-identifier on each interface using a combination of Identity Association Unique Identifier and DHCP Unique Identifier, as specified in clause 6.1 of RFC 4361 [33] for DHCPv4 and clause 11 and 12 of RFC 8415 [58] for DHCPv6. - -NOTE 2: An O-RU Controller can learn the particular client identifier(s) used by an O-RU by using the **o-ran-dhcp** YANG model. - -The DHCP server should operate using static bindings, i.e. ensuring an O-RU identified by a particular client hardware address is re-allocated the same management plane IP address, e.g. after performing an O-RU reset procedure. - -The O-RU shall bind operation of its NETCONF server to the assigned IP address. If an IPv6 capable O-RU operates using IPv6 Stateless Address Auto-Configuration (SLAAC), the O-RU shall bind operation of its NETCONF server to at least one configured globally unique IPv6 address. - -## 6.2.5 O-RU controller discovery - -This clause provides how to automatically discover the O-RU Controller address(es). - -O-RUs that have obtained their IPv6 addresses by stateless address auto-configuration, shall use stateless DHCPv6 as specified in RFC 8415 [58], to obtain management plane configuration information. - -Other O-RUs operating using stateful IPv4 or IPv6 address allocations shall obtain management plane configuration information during IP address allocation. - -Other O-RUs which have had their IP address(es) manually configured, shall also have their O-RU Controller(s) manually configured. - -O-RAN defined vendor specific option shall be used to signal all NETCONF client information to the O-RU using option 43 or option 125 for DHCPv4 and option 17 for DHCPv6. The O-RU shall request this option. Multiple instances of NETCONF client information may be signalled, encoded as a sequence of type/length/value fields. The O-RU shall consider these DHCP options as concatenation-requiring-options, as specified in RFC 3396 [78]. - -NOTE: Previous versions of the present document (prior to v15.0) did not require support of RFC3396 [78]. For previous versions, the support for RFC3396 [78] can be agreed between an operator and vendor. - -The definition of the types used within the DHCPv4 option 43, option 125/DHCPv6 Option 17 depends on the vendor-class option reported by the O-RU in its DHCP messages. - -When a legacy O-RU reports its vendor-class using the "o-ran-ru" prefix, the following types are defined: - -- Type: 0x01 - O-RU Controller IP Address -- Type: 0x02 - O-RU Controller Fully Qualified Domain Name - -When the O-RU reports its vendor-class using the "o-ran-ru2" prefix, the following types are defined: - -- Type: 0x81 - O-RU Controller IP Address -- Type: 0x82 - O-RU Controller Fully Qualified Domain Name -- Type: 0x86 - O-RU Call home protocol - -In all cases, the Type is followed by the length, which is the hexadecimal encoding of length of value field in octets, and the Value. - -When Type corresponds to an O-RU Controller IP Address, the value encodes IPv4 address(es) in hexadecimal format. For example, a single server with IPv4 address 198.185.159.144 is encoded in an option 43 or option 125 TLV as - -- Type 0x81 (or x01 for legacy) -- Length: 0x04 -- Value: C6 B9 9F 90 - -When Type corresponds to an O-RU Controller Fully Qualified Domain Name, this encodes the string representation of domain name, using ACSII encoding (i.e. following for encoding used for the domain name in the Host Name DHCP Option 12). For example, a server with FQDN "controller.operator.com" is encoded in an option 43 or option 125 TLV as: - -- Type 0x82 (or x02 for legacy) -- Length: 0x17 - -- Value: 63 6F 6E 74 72 6F 6C 6C 65 72 2E 6F 70 65 72 61 74 6F 72 2E 63 6F 6D - -The format of the DHCPv6 option 17 follows the format of the DHCPv4 encoding, with the additional inclusion of an Enterprise Number prior to the TLV option data. The IANA allocated private enterprise number to be used with DHCPv6 option 17 is 53148. - -When Type corresponds to the call home protocol, the value encodes whether an O-RU shall call home using NETCONF/SSH or NETCONF/TLS using the IANA defined ports as specified in clause 6 of RFC 8071 [15]. If no call home protocol type is provided, the O-RU shall use NETCONF/SSH. The format is encoded as follows: - -- Value 00 - O-RU shall attempt to call home using NETCONF/SSH -- Value 01 - O-RU shall attempt to call home using NETCONF/TLS - -For example, a DHCP server wanting to trigger the call home procedure using NETCONF/TLS encodes the option 43 or option 125 TLV as - -- Type: 0x86 -- Length: 0x01 -- Value: 01 - -NOTE: A previous version of the present document defined the use of OPTION\_V4\_SZTP\_REDIRECT and OPTION\_V6\_SZTP\_REDIRECT DHCP options to allow an O-RU to recover NETCONF Client information. In order to ensure backwards compatibility with equipment supporting earlier versions of the present document, an operator and vendor can agree to continue to use OPTION\_V4\_SZTP\_REDIRECT and/or OPTION\_V6\_SZTP\_REDIRECT DHCP options to recover NETCONF Client information. - -## 6.2.6 Certificate handling - -### 6.2.6.0 Trust anchor provisioning - -An O-RU configured to use TLS shall be provisioned with one or more trust anchor certificates that enable the O-RU to authenticate the peer's certificate chain. The O-RU Controller may provision trust anchors to the O-RU via configuration edit of data modelled via ietf-truststore.yang. - -Before an O-RU can establish a mutual TLS connection with a signalling peer, such as an O-RU Controller, the O-RU shall verify that the peer's certificate can be validated against one of the provisioned trust anchors. To validate against a trust anchor, the O-RU shall be able to be provisioned with one or more trust anchor certificates. The O-RU shall ensure that all trust anchor certificates are stored in reset persistent memory and protected from unauthorised external modification. - -The O-RU shall be able to be provisioned with new trust anchors. Provisioning of trust anchors is done using one of the options in clause 5.3.11 in [83] or through configuration in ietf-truststore. - -The O-RU shall be able to have an existing trust anchor replaced, e.g. because it has expired. The O-RU should support ietf-truststore YANG model to enable an O-RU Controller to manage (read, add, delete) the list of provisioned trust anchors and associated public keys. - -NOTE: If the O-RU is configured for certificate enrolment, the CMPv2 Initialization Response message can be used by the discovered CA/RA server to provision one or more trust anchors to the O-RU. The CA/RA Server identity is configured by the DHCP server using techniques described in clause 6.2.6.1. - -An O-RU shall trust the information that is signed or encrypted using a certificate chain leading to a configured trust anchor. - -When shipped, an O-RU only trusts information that is signed or encrypted using a certificate chain leading to a pre-loaded trust anchor. - -### 6.2.6.1 Certificate enrolment - -The purpose of certificate enrolment is to provision a trusted, unique, and verifiable digital identity in the form of an X.509 certificate to the O-RU issued by an operator approved Public Key Infrastructure (PKI) system (i.e CA/RA). This certificate enables secure, authenticated, and authorized communication between O-RU and other operator-controlled network elements such as the O-DU, SMO, or other services. - -An O-RU shall support certificate enrolment using CMPv2 as specified in RFC 4210 [44] and in clause 4.6 of [56] and one of the options in clause 5.3.9 of [83]. The O-RU shall support obtaining the CA/RA Server address from the DHCP server using vendor specific DHCP options. For IPv4, O-RU shall use DHCP Option 43 as specified in clause 4.2.1 of 3GPP TS 28.316 [72]. For IPv6, O-RU shall use DHCP Option 17 as specified in clause 4.2.2 of 3GPP TS 28.316 [72]. The IANA allocated private enterprise number to be used with DHCPv6 option 17 shall be 53148 (as allocated by IANA to O-RAN Alliance) or 3GPP registered IANA Enterprise Number (10415). The O-RU vendor shall inform operator about which Enterprise Number is being used. - -When an O-RU is configured to enrol for an operator-signed certificate, the transport network solution, as described in clause 5.1.3, shall provide a means to reach the operator approved PKI. - -When the O-RU is required to perform certificate enrolment using CMPv2, and CA/RA server is not accessible by the O-RU otherwise, the O-DU shall provide means for the O-RU to access the operator CA/RA for the O-RU certificate enrolment at the IP address conveyed as described above. Similarly, if the FQDN option is used instead, the O-DU shall provide means for the O-RU to access an operator DNS server in addition, as specified in RFC 2132 clause 3.8 [8] for IPv4 and as specified in RFC 3646 clause 3 [95] for IPv6. The access technologies described in clause 5.1.5 are examples of how such access could be provided. For certificate enrollment another option could be a Registration Authority (RA) function accessible by the O-DU (in the same domain), which is part of the operator PKI. - -An O-RU shall report any discovered CA/RA server address using the o-ran-dhcp YANG model. - -### 6.2.6.2 CMPv2 based certificate enrolment - -This clause outlines the procedure by which an O-RU obtains an operator-signed certificate using the CMPv2 protocol, through a CA/RA server designated by the operator for certificate enrolment. See clause 6.2.2, herein, for the necessary O-RU configuration of the identity (IP or FQDN) of a CA/RA server designated by the operator. The O-RU initiates the enrolment by sending a CMPv2 Initialization Request (IR) message, which is digitally signed using the private key associated with its vendor-signed certificate, also referred to as the vendor credential. - -The O-RU shall support the certificate management framework described in O-RAN Security Requirements and Controls Specifications [83], clause 5.3.9 and O-RAN Security Protocols Specifications [56], clause 4.6. The O-RU shall store the operator issued certificate and corresponding certificate chain in reset persistent memory. Mapping of the obtained operator issued certificate to relevant services shall be done using O-RU configuration via o-ran-certificates.yang. - -The handling of certificates, including certificate profiles, shall follow the rules defined in O-RAN Security Protocols Specifications [56], clause 4.2.3. In addition: - -- When an O-RU has not been provided with information regarding how to generate a certificate signing request, e.g. when the O-RU sends an Initialization Request message to signal the initial certificate enrolment, the O-RU shall generate the certificate signing request populating the Subject Distinguished Name field with a string that includes the O-RU manufacturer's name, model and serial number. - -There are various characters that are not recommended to be used in the Subject Distinguished Name Field, e.g. ":" (colon, hexadecimal character 0x34), "." (period, hexadecimal character 0x2E), "\_" (underscore, hexadecimal character 0x5F), "#" (hash, hexadecimal character 0x23), "£" (pound, hexadecimal character 0xa3), "\*" (asterisk, hexadecimal character 0x2a) or "" (double quote, hexadecimal character 0x22). Manufacturers that include such characters in their name, model and/or serial number should ensure such characters are removed before including in the Subject Distinguished Name Field. - -- In other cases, e.g. when the O-RU receives **csr-info** in an action statement <**generate-csr**> as specified in clause 6.2.6.4.3, the O-RU shall generate the certificate signing request using the provided information. - -When transferring messages to the CA/RA server, the O-RU shall use the "port number of the CA/RA server" and the "path to the CA/RA directory" as signalled using the DHCP options as specified in clause 4.2.3 of 3GPP TS 28.316 [72]. If no DHCP based configuration is received by an O-RU, the O-RU shall use the default port 443 and default directory "/pkix/". As indicated in Annex G of 3GPP TS 33.310 [51], and as the operator root certificate is not pre-provisioned in the O-RU, the O-RU authenticates the IR message using the RA/CA certificates(s) included in the IR message itself. - -When configured to operate with TLS, an O-RU that has a valid certificate issued by an operator PKI shall use this certificate to establish a mutually authenticated TLS connection for secure signalling with its O-RU Controller(s). - -### 6.2.6.3 Operation with vendor-signed certificates - -An O-RU should be provisioned with a unique device vendor-signed certificate and its entire certificate chain up to the root. The vendor-signed certificate serves as an identity for the O-RU during initial bootstrapping. The vendor-signed certificate is used in scenarios throughout the O-RUs life cycle where an operator-signed certificate is not provisioned, as specified in clause 6.2.6.2, or the certificate issued during previous enrolment has expired. - -The vendor-signed certificate can be utilized in operational use cases, such as initial bootstrapping and certificate enrolment. Initial bootstrapping and connectivity to operator network may utilize the vendor-signed certificate with 802.1X port based access control, as described in clause 7.12.2, and NETCONF call-home as described in clause 6.4. Certificate Enrolment via CMPv2 may utilize the vendor-signed certificate, as described in clause 6.2.6.2. - -Life cycle management of a vendor-signed certificate is out of scope for O-RAN standardization. It is recommended that the operator and vendor agree upon the process for life-cycle management of vendor-signed certificates. - -### 6.2.6.4 Certificate lifecycle management - -#### 6.2.6.4.1 Introduction - -An O-RU indicates its support for O-RAN defined certificate lifecycle management by including the ietf-keystore in its YANG library. Clause 6.2.6.4 applies to those O-RUs that support O-RAN defined certificate lifecycle management. The O-RU shall support the life cycle management of certificates as specified in 3GPP TS 33.310 [51] clause 7.2, including the renewal of certificates using CMPv2 before their expiry. The O-RU takes the role of a network element (NE) when following this clause. - -The O-RU shall support configurations for setting the policy for certificates re-issuance using the **cert-lcm-policy** leaf defined in o-ran-certificates.yang. The defined policies are: - -- REISSUE\_ON\_DEMAND -- AUTONOMOUS\_REISSUANCE - -NOTE: The enumeration REISSUE\_ON\_DEMAND refers to the on-demand triggering of the issuance of an additional certificate using the Certification Request/Response exchange, as defined in clauses 5.3.3 and 5.3.4 of RFC4210 [44]. The enumeration AUTONOMOUS\_REISSUANCE refers to the autonomous updating of an existing certificate, using the Key Update Request/Response, as defined in clauses 5.3.5 and 5.3.6 of RFC 4210. - -When configured with a **cert-lcm-policy** set to **REISSUE\_ON\_DEMAND**, the O-RU shall not autonomously initiate certificate re-issuance or re-key procedure. Instead, the O-RU Controller shall be responsible for triggering the initiation of the CMPv2 Certificate Request/Response procedure, as specified in clause 6.2.6.4.3. - -An O-RU shall be configured with **REISSUE\_ON\_DEMAND** for its first certificate renewal and when new csr-info parameters are to be used, and the O-RU Controller may set the **cert-lcm-policy** at any time after the O-RU successfully re-issued its certificate at least once. - -When configured with a **cert-lcm-policy** set to **AUTONOMOUS\_REISSUANCE**, the O-RU shall autonomously initiate certificate re-key procedure, as specified in clause 6.2.6.4.2, upon reaching the configured **renewal-days-before-expiry** days prior to certificate expiration. - -Additionally, the **max-kur-attempts** configuration may be used to limit the number of rekeying attempts the O-RU makes before raising the failure alarm. Likewise, the **max-poll-attempts** configuration may be used to control the number of polling attempts when the **pki-status** of 3 "waiting". - -When the certificates are re-issued, trust anchors may also be updated through provisioning as specified in clause 6.2.6.0. - -#### 6.2.6.4.2 O-RU Autonomous certificate re-issuance - -An O-RU shall support the capability to autonomously trigger certificate replacement by monitoring its own certificates expiry and initiating re-issuance number of days before expiry using **renewal-days-before-expiry** leaf defined in the **oran-certificates.yang** module. - -Upon reaching the re-issuance threshold, the O-RU shall generate a new public/private key pair using the csr information such as the key size and algorithms which was used in the current certificate generation and stored in local persistent storage. Subsequently, it shall create a Key Update Request (kur) message, digitally signed using the existing private key, to authenticate the request. This kur is then submitted as part of the CMPv2 certificate rekeying procedure to the CA/RA server. The **pki-failure-info**, **PKIStatus**, and **pki-free-text** fields may be exposed during the procedure as notifications for consumption by the O-RU controller. This procedure is shown in Figure 6.2.6.4.2-1. - -When the Certificate Re-issuance Failed alarm is raised, the operator should investigate and resolve the issue. How to solve the issue is out of scope of present document. - -![Sequence diagram for Autonomous certificate re-issuance. Lifelines: NETCONF Server (O-RU), CA/RA Server, NETCONF Clients (O-RU Controllers). The process involves key generation, CMPv2 requests and responses, notifications, and polling attempts until a certificate is issued or attempts are exhausted.](789ee0a267b24f34bd1f45313e86c9a4_img.jpg) - -**Sequence Diagram: O-RU Initiated Automatic Certificate Re-issuance** - -**Participants:** NETCONF Server (O-RU), CA/RA Server, NETCONF Clients (O-RU Controllers) - -**Initial Note:** Certificate is renewal-days-before-expiry days from expiration triggering automatic certificate re-issuance and cert-lcm-policy is set to AUTONOMOUS\_REISSUANCE - -**Process Flow:** - -- loop** [until predefined max-kur-attempt reached or kup received] - - [1] Generate new public/private key pair using the O-RU's existing digital signature - - [2] CMPv2: Key Update Request (kur) - - [3] CMPv2: Key Update Response (kup) -- alt** [kup received] - - alt** [PKIStatus==accepted] - - opt** [certificate confirmation] - - [4] CMPv2: Certificate Confirm - - [5] CMPv2: PKI confirm - - Note:** Certificate issued - - [6] KEY\_UPDATE\_REQUEST0 - - alt** [PKIStatus==waiting] - - [7] KEY\_UPDATE\_REQUEST3 - - [8] Poll Request - - loop** [until certificate is issued or number of polling attempts exceeds max-poll-attempts] - - alt** [pending] - - [9] Poll Response checkAfter (seconds) - - [10] POLLING\_REQUEST - - [11] checkAfter timer expires - - [12] Poll Request - - alt** [rekeyed] - - [13] CMPv2: Key Update Response (kup) -- alt** [certificate issued] - - opt** [if certificate issued] - - [14] CMPv2: Certificate Confirm - - [15] CMPv2: PKI Confirm - - Note:** Certificate issued - - [16] KEY\_UPDATE\_REQUEST0 -- alt** [max-poll-attempts reached without re-issuance] - - [17] Certificate Re-issuance Failed -- opt** - - [18] PKIStatusInfo.failInfo - - [19] PKIStatusInfo.statusString -- alt** [PKIStatus==rejection] - - [20] KEY\_UPDATE\_REQUEST2 - - [21] Certificate Re-issuance Failed -- opt** - - [22] PKIStatusInfo.failInfo - - [23] PKIStatusInfo.statusString -- alt** [kup NOT received] - - [24] Certificate Re-issuance Failed -- opt** - - [25] PKIStatusInfo.failInfo - - [26] PKIStatusInfo.statusString - -Sequence diagram for Autonomous certificate re-issuance. Lifelines: NETCONF Server (O-RU), CA/RA Server, NETCONF Clients (O-RU Controllers). The process involves key generation, CMPv2 requests and responses, notifications, and polling attempts until a certificate is issued or attempts are exhausted. - -Figure 6.2.6.4.2-1: Autonomous certificate re-issuance - -#### 6.2.6.4.3 On-demand certificate re-issuance - -An O-RU controller wanting to trigger the re-issuance of an additional certificate to the O-RU shall configure the **cert-lcm-policy** to **REISSUE\_ON\_DEMAND**. The O-RU controller may trigger the issuance of an additional certificate by using the action statement **** from ietf-keystore.yang defined in RFC 9640 [92]. After having responded with a rpc-reply ****, an O-RU receiving the **** shall recover the SubjectPublicKeyInfo from the **csr-info** and trigger the generation of a new key pair. After a new key pair has been generated, the O-RU shall store the csr information in non-volatile storage. The O-RU shall use the **csr-info** to create a certificate signing request, as specified in RFC 2986 [87], which it shall use in a CMPv2 certificate request exchange with the CA/RA server. The procedure is shown in Figure 6.2.6.4.3-1. - -![Sequence diagram for On-Demand Certificate Re-Issuance showing interactions between Netconf Server (O-RU), CA/RA Server, and Netconf Client (O-RU Controller).](a780a960b3f2de2493d5785bedae10ff_img.jpg) - -**On-Demand Certificate Re-Issuance** - -``` - -sequenceDiagram - participant Netconf Server (O-RU) - participant CA/RA Server - participant Netconf Client (O-RU Controller) - - Note right of Netconf Server: [001] REISSUE_ON_DEMAND - Netconf Server->>Netconf Client: [001] - Note right of Netconf Client: [002] - Netconf Client-->>Netconf Server: [002] - - Note left of Netconf Server: O-RU Controller Triggered Certificate Request - Note right of Netconf Server: [003] p10-csr - Netconf Server->>Netconf Client: [003] - Note right of Netconf Client: [004] - Netconf Client-->>Netconf Server: [004] - Note right of Netconf Server: [005] Generate new public/private key pair using SubjectPublicKeyInfo from csr-info - Note right of Netconf Server: [006] CMPv2: Certification Request with CSR structure from - Netconf Server->>CA/RA Server: [006] - Note right of CA/RA Server: [007] CMPv2: Certification Response - CA/RA Server-->>Netconf Server: [007] - - alt PKIStatus accepted - opt certificate confirmation - Note right of Netconf Server: [008] CMPv2: Certificate confirm - Netconf Server->>CA/RA Server: [008] - Note right of CA/RA Server: [009] CMPv2: PKI Confirm - CA/RA Server-->>Netconf Server: [009] - end - Note right of Netconf Server: Certificate issued - Note right of Netconf Server: [010] CERTIFICATION_REQUEST0 - Netconf Server->>Netconf Client: [010] - else PKIStatus waiting - Note right of Netconf Server: [011] CERTIFICATION_REQUEST3 - Netconf Server->>Netconf Client: [011] - Note right of Netconf Server: [012] Poll Request - Netconf Server->>CA/RA Server: [012] - Note right of CA/RA Server: [013] Poll Response checkAfter (seconds) - CA/RA Server-->>Netconf Server: [013] - Note right of Netconf Server: [014] POLLING_REQUEST - Netconf Server->>Netconf Client: [014] - else certificate still pending - loop until certificate is issued - Note right of Netconf Server: [015] checkAfter timer expires - Note right of Netconf Server: [016] Poll Request - Netconf Server->>CA/RA Server: [016] - Note right of CA/RA Server: [017] Poll Response checkAfter (seconds) - CA/RA Server-->>Netconf Server: [017] - Note right of Netconf Server: [018] POLLING_REQUEST - Netconf Server->>Netconf Client: [018] - end - Note right of Netconf Server: [019] checkAfter timer expires - Note right of Netconf Server: [020] Poll Request - Netconf Server->>CA/RA Server: [020] - Note right of CA/RA Server: [021] Certification Response - CA/RA Server-->>Netconf Server: [021] - opt certificate confirmation - Note right of Netconf Server: [022] CMPv2: Certificate confirm - Netconf Server->>CA/RA Server: [022] - Note right of CA/RA Server: [023] CMPv2: PKI Confirm - CA/RA Server-->>Netconf Server: [023] - end - Note right of Netconf Server: Certificate issued - Note right of Netconf Server: [024] POLLING_REQUEST0 - Netconf Server->>Netconf Client: [024] - Note right of Netconf Server: [025] CERTIFICATION_REQUEST0 - Netconf Server->>Netconf Client: [025] - else PKIStatus rejection - Note right of Netconf Server: [026] CERTIFICATION_REQUEST2 - Netconf Server->>Netconf Client: [026] - Note right of Netconf Server: [027] Certificate Request Failed - Netconf Server->>Netconf Client: [027] - end - -``` - -Sequence diagram for On-Demand Certificate Re-Issuance showing interactions between Netconf Server (O-RU), CA/RA Server, and Netconf Client (O-RU Controller). - -Figure 6.2.6.4.3-1: On-demand additional certificate re-issuance - -#### 6.2.6.4.4 Certificate Life Cycle Notifications - -The O-RU shall support configurations for "advance certificate about to expire notification timer" for different severities. - -The O-RU shall notify all the O-RU controller(s) that have subscribed to receive fault ID 39 specified in clause A.1 as follows: - -- With severity as minor **minor-alarm-advance-time** prior to expiry [units days, default: 30]; -- With severity as major **major-alarm-advance-time** prior to expiry [units days, default: 10]; and -- With severity as critical **critical-alarm-advance-time** prior to expiry [units days, default: 2]. - -The O-RU shall notify the subscribing O-RU controller(s) of certificate expiry using fault ID 40 as specified in clause A.1. - -After the O-RU successfully completes the CMPv2 process for certificate issuance, it shall notify all the subscribing O-RU controller(s) by sending a **certificate-lcm** notification. If the triggered certificate issuance process fails, the O-RU shall notify all the subscribing O-RU controller(s) using faults specified in clause A.1. - -#### 6.2.6.4.5 Certificate revocation list checking - -Certificate revocation checking is handled via certificate revocation lists (CRL) that are periodically updated through the processes outlined in RFC 5280 [99] and 3GPP TS 33.310 [52]. Except when operating using Trust On First Use (TOFU), as described in clause 5.4.3, when an O-RU establishes a TLS connection, if any certificate in the peer's certificate chain includes the CRL distribution point extension and the O-RU has no valid corresponding CRL, the O-RU shall download the valid CRL(s) from the CRL distribution point field(s) provided by the associated X.509 certificate(s). The O-RU shall support HTTP and should support LDAP for CRL downloading. At any time, if the O-RU is unable to connect to a signalled CRL distribution point, the O-RU shall raise alarm type 43 as described in Table A.1-1. - -As the O-RU can have long lived TLS connections with one or more O-RU controllers, an O-RU with an existing TLS connection shall use the nextUpdate field associated with the downloaded CRL(s) for the purposes of downloading a new CRL before it expires. The ability to configure the time window before CRL expiry that a new CRL is downloaded is set by the **crl-renewal-time-before-nextupdate** leaf defined in the o-ran-certificates.yang. An O-RU shall attempt to download valid CRL(s), starting from the time epoch of (nextUpdate - **crl-renewal-time-before-nextupdate**). If the O-RU fails to download a valid CRL by the time of nextUpdate, the O-RU shall raise alarm type 44 as described in Table A.1-1. - -NOTE: The algorithm for repeatedly attempting to download CRLs until a valid CRL is successfully downloaded is left to vendor implementation. - -The operations of an O-RU when receiving an indication in an updated CRL that a certificate in the certificate chain associated with an active TLS connection has been revoked after TLS establishment is not defined in the present document. - -The method of certificate revocation is out of scope of the present document. - -### 6.2.7 Event-Collector discovery - -This clause describes how an O-RU automatically discovers the Event-Collector to which it shall send its pnfRegistration notification. The support by an O-RU of PNF Registration to a discovered Event-Collector is optional and hence this clause only applies to those O-RUs that support this optional capability. - -O-RUs that have obtained their IPv6 addresses by stateless address auto-configuration, shall use stateless DHCPv6, as specified in RFC 8415 [58], to obtain Event-Collector information. Other O-RUs operating using stateful IPv4 or IPv6 - -address allocations shall obtain Event-Collector information during IP address allocation. Other O-RUs which have had their IP address(es) manually configured, shall also have their Event-Collector(s) and Event-Collector Notification Format manually configured. - -The O-RU supporting PNF Registration shall be able to recover Event-Collector information using O-RAN defined vendor specific option to signal Event-Collector information to the O-RU using option 43 or option 125 for DHCPv4 and option 17 for DHCPv6. To achieve that, the O-RU shall request the option 43 or option 125 for DHCPv4 and option 17 for DHCPv6 as defined in clause 6.2.5. If the network provides an Event-Collector for the O-RU to send its pnfRegistration notification to, a DHCPv4 server shall respond with option 43 or option 125 if so requested, and a DHCPv6 server shall respond with option 17 if so requested. - -The definition of the types used within the DHCPv4 option 43 or option 125/DHCPv6 Option 17 are as follows: - -- Type: 0x83 – Event-Collector IP Address -- Type: 0x84 – Event-Collector Fully Qualified Domain Name -- Type: 0x85 – Event-Collector Notification Format - -In this version of the present document, the operation of an O-RU when receiving multiple instances of the Event-Collector IP Address and/or Event-Collector FQDN information is not defined. - -In all cases, the Type is followed by the length, which is the hexadecimal encoding of length of value field in octets, and the Value. - -When Type corresponds to an Event-Collector IP Address, the value encodes IPv4 address(es) in hexadecimal format. For example, an Event-Collector with IPv4 address 198.185.159.144 is encoded in an option 43 or option 125 TLV as: - -- Type 0x83 -- Length: 0x04 -- Value: C6 B9 9F 90 - -When Type corresponds to an Event-Collector Fully Qualified Domain Name, this encodes the string representation of domain name, using ACSII encoding (i.e. following for encoding used for the domain name in the Host Name DHCP Option 12). For example, a server with FQDN "collector.operator.com" is encoded in an option 43 or option 125 TLV as: - -- Type 0x84 -- Length: 0x17 -- Value: 63 6F 6C 6C 65 63 74 6F 72 2E 6F 70 65 72 61 74 6F 72 2E 63 6F 6D - -In this version of the present document, the operation of an O-RU when receiving an Event-Collector FQDN that is subsequently resolved by the O-RU to more than one IP address (i.e. returning multiple Address records) is not defined. - -The format of the DHCPv6 option 17 shall follow the format of the DHCPv4 encoding, with the additional inclusion of an Enterprise Number prior to the TLV option data. The IANA allocated private enterprise number to be used with DHCPv6 option 17 is 53148. - -When Type corresponds to an Event-Collector Notification Format, the value shall encode the format the Event-Collector expects to receive asynchronous notifications. In the present document, only a single format is defined: - -- Value 00 - Event-Collector expects the notification to be signalled using the format as specified in the ONAP VES event listener specification [i.2]. - -For example, an Event-Collector expecting the pnfRegistration notification to be signalled using the ONAP defined format is encoded in the option 43 or option 125 TLV as: - -- Type 0x85 -- Length: 0x01 -- Value: 00 - -## 6.2.8 Static routing of IP traffic - -An O-RU may support static routing. This is an optional capability, and this clause only applies to those O-RUs that support static routing. - -An O-RU that supports IPv4 shall support configuration of routing information as specified in RFC 3442 [62] and shall indicate its support of RFC 3442 using the **rfc3442-supported** leaf specified in o-ran-interfaces YANG model. An O-RU that supports IPv6 shall support configuration of default router preferences and more-specific routes as specified in RFC 4191 [90] and shall indicate its support of RFC 4191 using the **rfc4191-supported** leaf specified in o-ran-interfaces YANG model. - -## 6.3 NETCONF call home to O-RU controller(s) - -The O-RU aims to have NETCONF sessions with all of the call home O-RU Controller(s), either discovered using the DHCP options defined in clause 6.2.5, provisioned by an existing NETCONF client, or statically configured. An O-RU controller may attempt to autonomously initiate a NETCONF session with the O-RU, e.g. triggered by the pnfRegistration procedure. In order to support NETCONF clients corresponding to call home O-RU Controllers that either do not attempt to initiate a NETCONF session with the O-RU, or are prevented from doing so, e.g. because of Network Address Translation limitations, the O-RU shall call home to all call home O-RU Controller identities with which it does not already have an active NETCONF session. - -When the O-RU discovers, or is provisioned with, a call home O-RU Controller identity represented as an FQDN, the O-RU shall use DNS to resolve the IP address(es) of the FQDN identity. If as result of the resolution of the O-RU Controller FQDN to IP address, an O-RU receives multiple A and/or AAAA records, the O-RU should cycle through the received IP addresses in the A and/or AAAA records until it is able to establish a NETCONF session with a particular O-RU Controller identity. The O-RU should report the O-RU controller IP address used in the established NETCONF session in the **client-info** container in the o-ran-mplane-int YANG model. As a consequence, the O-RU is expected to have a single M-Plane session established per each O-RU controller's FQDN, regardless how many A/AAAA records were returned by the DNS server for each O-RU Controller FQDN. - -An O-RU that supports more than one network interface shall be able to perform O-RU Controller discovery on each of its network interfaces. If an O-RU recovers identical O-RU controller identity information on multiple network interfaces, then it should select which one out of the multiple interfaces to use for its call home operation. - -NOTE 1: The operation of an O-RU that discovers different O-RU Controller identities on separate network interfaces is not currently defined in the present document. - -If the O-RU is unable to establish a NETCONF session with some of the call home O-RU Controller identities, the O-RU shall use the **re-call-home-no-ssh-timer** to repeatedly re-perform the call home procedure to all call home O-RU Controller identities with which the O-RU does not have an established NETCONF session, cycling through the A and/or AAAA records until it is able to establish a NETCONF session with a particular call home O-RU Controller identity. The same value of timer shall be used, irrespective of whether SSH or TLS is being used to transport the NETCONF session. - -NOTE 2: The O-RU can cache the returned A/AAAA records for a period of time according to the DNS time to live. The setting of the DNS time to live is an operator name server configuration parameter. As an example, if an operator knows in advance of a change in the IP address(es) used by its O-RU controller(s), the operator can configure the name server with a minimum time to live value to ensure O-RUs request the new IP address(es) in a timely fashion. Name server configuration is outside the scope of the present document. - -If the O-RU is unable to trigger the establishment of NETCONF session with at least one call home O-RU Controller after having repeated the call home procedure a total of **max-call-home-attempts** per O-RU Controller, then the O-RU should perform an autonomous reset. - -The O-RU shall call home as specified in clause 4 of RFC 8071 [15] whereby the O-RU (NETCONF Server) initiates a TCP connection to the NETCONF client. When calling home to the NETCONF clients in the container **client-info**, O-RU shall use the port signalled using the RFC 8572 [14] DHCP option or manually configured during installation, and when calling home to the NETCONF clients in the container **configured-client-info**, O-RU shall use the port configured by other NETCONF Client. If no port was signalled or manually configured in the container **client-info**, or not configured in the container **configured-client-info**, O-RU shall use the port configured in **call-home-ssh-port** to indicate that the O-RU uses SSHv2 to secure the NETCONF connection and use the port configured in **call-home-tls-port** to indicate that the O-RU uses TLS to secure the NETCONF connection. If **call-home-ssh-port** does not exist, the O-RU shall use the IANA-assigned port 4334 to indicate that the O-RU uses SSHv2 to secure the NETCONF connection, and if **call-home-tls-port** does not exist, the O-RU shall use the IANA-assigned port 4335 to indicate that the O-RU uses TLS to secure the NETCONF connection. As illustrated in Figure 6.3-1, when the NETCONF client accepts a TCP connection on the allocated port, it shall initiate an SSH session/TLS connection with the NETCONF Server. Using this SSH session/TLS connection, the NETCONF client shall initiate a NETCONF session. - -![Sequence diagram illustrating the NETCONF call home procedure between a NETCONF Server/(O-RU) and a Netconf Client. It includes normal and abnormal procedure flows with steps for TCP, SSH/TLS, and NETCONF Hello/Capabilities exchanges.](cac61a60141d0335b4ae7a081f6b18d4_img.jpg) - -The diagram illustrates the NETCONF call home procedure between a NETCONF Server/(O-RU) and a Netconf Client. It is divided into two main sections: Normal Procedure and Abnormal Procedure. - -**Normal Procedure:** - -- The NETCONF Server/(O-RU) starts a Call Home Timer. -- The NETCONF Server/(O-RU) initiates a TCP connection to the Netconf Client. -- Using the TCP Connection, the NETCONF client initiates an SSH session/TLS connection to the NETCONF Server/(O-RU). -- Using the SSH/TLS connection, the NETCONF client initiates a NETCONF session to the NETCONF Server/(O-RU). -- The NETCONF Server/(O-RU) receives NETCONF Hello/Capabilities from the client. -- The NETCONF Server/(O-RU) sends NETCONF Hello/Capabilities to the client. -- The NETCONF Server/(O-RU) stops the Call Home Timer. - -**Abnormal Procedure:** - -- The NETCONF Server/(O-RU) starts a Call Home Timer. -- The NETCONF Server/(O-RU) initiates a TCP connection to the Netconf Client. -- There are three optional steps, each with a failure path (indicated by an 'X') and a success path: - - - [no TCP]:** The NETCONF Server/(O-RU) sends a TCP SYN/ACK to the client. If this step fails, the procedure continues to the next optional step. - - [no SSH/TLS]:** The NETCONF Server/(O-RU) sends an SSH/TLS message to the client. If this step fails, the procedure continues to the next optional step. - - [no NETCONF]:** The NETCONF Server/(O-RU) sends a NETCONF message to the client. If this step fails, the procedure continues to the next step. - -- If all optional steps fail, the Call Home Timer Expires. -- When the timer expires, the procedure repeats the call home procedure. - -Sequence diagram illustrating the NETCONF call home procedure between a NETCONF Server/(O-RU) and a Netconf Client. It includes normal and abnormal procedure flows with steps for TCP, SSH/TLS, and NETCONF Hello/Capabilities exchanges. - -Figure 6.3-1: Outline of NETCONF call home procedure - -The O-RU shall ensure that a persistent connection to all call-home O-RU controllers is maintained by actively testing the aliveness of the connection. The O-RU should support TLS heartbeat/SSH using the keep-alive mechanism as specified in clause 4.1 of RFC 8071 [15] and may support TCP keep-alive. The establishment of NETCONF client privileges is covered in clause 6.5. - -## 6.4 NETCONF connection establishment - -### 6.4.0 General - -The authentication mechanism and protocol to use are described in Table 5.4.1-1. - -The identity of the NETCONF server (O-RU) shall be verified and authenticated by the NETCONF client according to local policy for authentication described in Table 5.4.1-1 before password-based authentication data or any configuration or state data is sent to or received from the NETCONF server. - -When using SSHv2, public key-based host authentication shall be used for authenticating the server (RFC 4253 [7]) by the clients. In addition, server authentication based on X.509 certificates may also be provided as specified in RFC 6187 [31]. - -When using TLS, X.509 certificate-based authentication shall be used for mutual authentication between the NETCONF client and NETCONF server. - -**NOTE:** SSHv2 based public key-based host authentication requires that the SSH server (O-RU) public keys are provisioned in the NETCONF client (e.g. O-DU and/or SMO). As an alternative, RFC 4251 [79] mentions that "a possible strategy is to only accept a host key without checking the first time a host is connected, save the key in a local database, and compare against that key on all future connections to that host. ". This option simplifies the key management procedure as it does not require to pre-populate them in O-DU/SMO (SSH client) but obviously at the price of degraded security, therefore the support of this option is configurable and left to operator's choice. - -In case the O-RU is not configured to perform certificate enrolment, or enrolment failed the O-RU may use its unique device vendor-signed certificate. The first NETCONF session during start-up installation using the default NETCONF account will in this case be authenticated by the O-RU controller but not by the O-RU, unless the O-RU has been provisioned with trust anchors using one of the options in clause 5.3.11 in [83]. - -If an O-RU is not configured with a valid, non-manufacturer trust anchor, the O-RU may skip the verification of the client certificate exchanged during the mTLS handshake. - -### 6.4.1 NETCONF security - -As specified in clause 5.4, this version of the O-RU Management Plane Specification uses TLS 1.2, TLS 1.3, or SSHv2 for mutual authentication between the NETCONF server (O-RU) and the NETCONF client (O-DU or SMO). - -If multiple NETCONF sessions are established to an O-RU, those sessions shall be established over separate SSH tunnels/TLS connections. - -### 6.4.2 NETCONF authentication - -The authentication mechanism and protocol to use are described in clause 5.4. - -This version of the O-RU Management Plane Specification supports SSHv2 using password authentication method for SSHv2 as specified in clause 8 of RFC 4252 [6] and client authentication based on X.509 certificates as specified in RFC 6187 [31], and TLS 1.2, or TLS 1.3, using X.509 certificate-based authentication. - -The identity of the NETCONF server (O-RU) shall be verified and authenticated by the NETCONF client (O-DU or SMO) according to local policy for authentication described in Table 5.4.1-1 before authentication data or any configuration or state data is sent to or received from the server. - -The identity of the NETCONF client (O-DU or SMO) shall be verified and authenticated by the NETCONF server (O-RU) according to local policy for authentication described in Table 5.4.1-1 to ensure that the incoming NETCONF client request is legitimate before any configuration or state data is sent to or received from the NETCONF client. The server shall also perform NETCONF Access Control Model (NACM) based authorization, as specified in clause 6.5, before accepting any request. - -If authentication is based on X.509 certificates, for the purposes of user authentication, the mapping between certificates and **user-name** is provided by the subjectAltName field of the X.509 certificate, which means that the user name is coded in the subjectAltName. The username is determined from the subjectAltName using the rules as specified in RFC 7589 [41]. For the purposes of NETCONF server authentication, RFC 7589 [41] specifies server identity as specified in clause 4 of RFC 9525 [84]. - -Upon initial system initialisation, the O-RU is configured with a default account. The specific details of the default account are to be agreed between operator and vendor. An example of a default user account for account-type PASSWORD is one with username "oranuser". An example of a default user account for account-type CERTIFICATE is map type "san-rfc822-name" with an rfc822-name of "oranuser@o-ran.org". An example of a default user account for account-type SSHPUBLICKEY is "oranuser". - -The default account may be of account-type PASSWORD, in which case a default password also needs to be defined and configured in the O-RU in alignment with clause 6.4.3.1. The default account may be of account-type SSHPUBLICKEY, in which case the default public key and associated algorithm need to be configured in the O-RU. As the default account may be operator specific, this may require that the O-RU provides facilities to configure securely this default account and cert-to-name mapping list at installation time (i.e. before the O-RU is connected to the O-RU Controller). - -**NOTE:** The account-type SSHPUBLICKEY was first defined in v16.01 of the present document. The support for a default account type SSHPUBLICKEY can be agreed between operator and vendor, depending upon O-RU controller capabilities. - -If user authentication is based on X.509v3 certificate during O-RU plug and play, to support zero touch for the first NETCONF connection, the O-RU shall support the default mapping between certificate and default NETCONF account which maps any authenticated X.509 v3 certificate to this default O-RAN account. The trust anchor for O-RU shall be provisioned automatically with online CA server during O-RU Plug and Play, and it shall be same as the trust anchor of the O-RU Controller(s), thus avoiding the need for manual configuration of the peer trust anchor for O-RU. - -The default account is a member of the "sudo" privilege group (see clause 6.5 for details of groups/privileges) as it is intended to be used to create other accounts, as specified in clause 6.4.3. As the default account credential may be common across different deployments of a vendor's equipment, it is strongly recommended to only use the default account to create other operator specific user accounts on the O-RU. Clause 6.4.3.1 specifies the conditions whereby the creation of a NETCONF server account triggers the automatic disabling of the default account. - -The operator and vendor shall agree how the default account can be determined by a NETCONF client operating in a multi-vendor O-RU environment based on the SSH response message sent by the O-RU. It is recommended that the vendor and operator agree on a particular format of the "SSH-protoversion-softwareversion SP comments CR LF" identification string, as defined in RFC 4253 [7] clause 4.2, used by the SSH Server in the O-RU to identify the O-RU vendor and consequently the default account to be used by the NETCONF client. Upon initial system initialisation, the NETCONF client can authenticate itself to the O-RU using SSH Authentication either with the agreed default username and password or with simple public key. - -If authentication based on X.509 certificates according to [31] is supported by SSH and TLS client and server, the certificates need to be installed at initial system initialisation, or can be obtained through certificate enrolment with operator's PKI (certificate enrolment as defined by 3GPP with CMPv2 protocol between the NE and the operator's CA). - -After having enrolled in an Operator PKI, when establishing a new TLS session using X.509 certificate-based authentication, the O-RU shall select a valid certificate issued by the operator PKI with the longest time to its expiration. - -## 6.4.3 User account provisioning - -### 6.4.3.1 General - -The NETCONF client with suitable privileges may provision user accounts on the O-RU, including the accounts (users) name, password, group (see clause 6.5 for details of groups/privileges) and whether a particular account is enabled or disabled. The provisioning of new accounts is typically performed once during pre-staging, as described in step 14 of Figure 6.1-1. - -- The **name** for the user is a string which should be between 3-32 characters. For account-type PASSWORD, the first character should be a lowercase letter. The remaining characters should be lowercase letters or numbers. For account-type CERTIFICATE or SSHPUBLICKEY, the characters should be lowercase letters, numbers, periods (ASCII code 0x2E) or @ sign (ASCII code 0x40). -- The **account-type** is an enumeration, indicating authentication method such as password, certificate, or simple public key. -- The **password** is a string between 8-128 characters. Allowed characters in the password field include lowercase and uppercase letters, numbers and the special characters: ! \$ % ^ ( ) \_ + ~ { } [ ] . The password leaf is present only for those user accounts associated with password-based authentication. When used, the **password** should follow security best practices as specified in Clause 5.3.7 in O-RAN Security Requirements and Controls Specifications [83]. -- Whether an account is **enabled**. The YANG model ensures that at least one user account is always enabled on the O-RU. -- When the O-RU supports the **SHARED-ORU-MULTI-OPERATOR** feature, the user account may be associated with zero or more Shared Resource Operator IDs (**sro-id**). Clause 19 describes the operation of the **SHARED-ORU-MULTI-OPERATOR** feature in more detail. When an **sro-id** is configured with a user account with "carrier" group/role privileges, the multi-operator shared O-RU feature is enabled. - -The new account information (user **name**, **password**, optional **sro-id**, **account-type** and whether the account is **enabled**) shall be stored in reset-persistent memory in O-RU. - -Each account **name** in o-ran-usermgmt YANG model is identical to the **user-name** used in ietf-netconf-acm YANG model. User account provisioning shall include using the ietf-netconf-acm module to define which **groups** are associated with a particular **user-name** (see clause 6.5 for details of groups/privileges). The definition of a privilege group or set of privilege groups referred to by **name(s)** is(are) intended to match deployment scenarios. For example, the group **name** "sudo" is intended to be used when configured as a NACM group for a **user-name** associated with the NETCONF client of a hierarchical O-DU. Conversely, the group name "hybrid-odu" is intended to be used when configured as a NACM group for a **user-name** associated with the NETCONF client of a hybrid O-DU. - -For client authentication based on certificate or Simple Public Key, no password needs to be provisioned. For certificate based authentication, at time of SSH or TLS connection, user's authorisation is done based on the X.509 certificate's SubjectAltName field that codes the associated account's name. - -When a NETCONF client using the default account is used to successfully commit the configuration for another user account with account privileges "sudo", the NETCONF client should close existing NETCONF session as described in clause 6.8. Then, the O-RU disables the default account and default account stays disabled over the resets. The default account becomes enabled when the O-RU is reset to the factory default software by following the procedures defined in clause 8.8. Any other way to enable the default account is not precluded as O-RU vendor implementation matter. - -NOTE 1: Configuring a new user account with "sudo" privileges enables that account to have full permissions over the o-ran-usermgmt.yang model which then permits that account to create other user accounts on the O-RU's NETCONF server. - -The security principle defined in this clause shall follow those defined for the default account and default mapping, i.e. the O-RU Controller shall create a new mapping. - -NOTE 2: Depending on the EE/CA certificate of the O-RU Controller, the map type can still be specified but with specific fingerprint of the EE/CA certificate or based on SubjectAltName of EE/CA certificate as specified in clause 6.4.2. - -### 6.4.3.2 Certificates to NETCONF usernames mapping list provisioning - -The O-RU controller with suitable privileges may provision list **cert-to-name** to define how certificates are mapped to NETCONF usernames at the O-RU using o-ran-certificates.yang. This list shall be stored in reset persistent memory. Each entry of the mapping list contains a certificate fingerprint, a map-type and optional username. - -- The certificate fingerprint is a digest of NETCONF client end-entry (EE) certificate or a digest of a trusted certificate authority (CA) which is part of the CA certificate chain of the NETCONF client EE certificate in X.509 binary format. From security consideration, it is recommended to use EE certificate fingerprint instead of CA certificate fingerprint. -- The map-type indicates how the NETCONF username associated with the certificate should be determined. O-RU shall support map-types A and B defined in section 7 of RFC 7589 [41]. Support for other map-types is optional. Support for map-type F, "common-name", is deprecated. -- The username name is a NETCONF account's name which is specified only when map-type is 'specified'. - -In case a X.509v3 certificate that is used for client authentication is updated e.g. due to it being close to expiry, the O-RU controller shall update the X.509v3 certificate and if necessary re-provision the cert-to-name entry to O-RU Configuration using o-ran-certificates.yang. - -## 6.5 NETCONF access control - -This clause defines the access control for NETCONF clients. Its motivation is that when multiple NETCONF clients (users) are defined, the NETCONF access control mechanism enables the NETCONF server to limit some operations for one client but allow full access for another client. In particular, for hybrid access configuration as introduced in clause 5, this allows the privileges associated with the NETCONF client in the hybrid O-DU to be distinct and different from the privileges associated with the NETCONF client in the SMO. - -In order to support interoperable access control management, the NETCONF Server shall use the IETF NETCONF Access Control Model as specified in RFC 8341 [64]. - -Currently seven access control **groups** corresponding to different NETCONF client roles are defined and can be mapped to the user-name for a NETCONF session: "sudo", "smo", "hybrid-odu", "carrier", "nms", "fm-pm", and "swm". Table 6.5-1 maps the group/role **name** to different privileges. Privileges are defined per namespace for read "R", write "W" and execute "X" where "X" indicates access privilege to use RPC operations or to subscribe to Notifications. The NACM module is used to store the association between the **groups** and **user-names** and enables a **user-name** to be associated - -with multiple different **groups**. The configuration of the NACM module shall be stored in reset-persistent memory in O-RU. - -During access control procedure, **groups** associated to the user are determined based on **user-name** that an O-RU controller provided or derived from O-RU controller's certificate. The user's access privileges are the combination (union) of the privileges associated with those **groups**. Refer to Table 6.5-1 for privilege details. O-RU shall support access control enforcement procedure defined in RFC 8341 [64] clause 3.4. - -The NETCONF client in the hybrid O-DU should be associated with the "hybrid-odu" privilege group and the NETCONF client in the SMO should be associated with the "smo" privilege group. - -A NETCONF client can perform read operations on the o-ran-usermgmt and ietf-netconf-acm YANG models to determine the group privileges its NETCONF account has been granted. - -When operating with a NETCONF client with user name user-list entry containing a configured sro-id and with "carrier" privileges, e.g. a client operated by a Shared Resource Operator, a Multi-Operator O-RU shall have its read, write and execute privileges for certain models further refined based on the sro-id associated with the name of the NETCONF client as configured using the o-ran-usermgmt YANG model. Further details are described in clause 19. - -**Table 6.5-1: Mapping of account groupings to O-RU module privileges** - -| Module Rules | sudo | nms | fm-pm | swm | smo | hybrid-odu | carrier | -|-------------------------------------------------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|------------------------| -| "urn:o-ran:supervision:x.y" | RWX | --- | --- | --- | RW-
(note 4) | RWX | R-X | -| "urn:o-ran:hardware:x.y" | RWX | RW- | --- | --- | RWX | R-- | R-- | -| "urn:ietf:params:xml:ns:yang:ietf-hardware" | RWX | RWX | R-X | --- | RWX | R-X | R-X | -| "urn:o-ran:user-mgmt:x.y" | RWX
(note 1) | --X
(note 8) | --X
(note 8) | --X
(note 8) | RWX
(note 1) | RWX
(note 1) | --X
(notes 7 and 8) | -| "urn:o-ran:fm: x.y " | R-X | R-X | R-X | --- | R-X | R-X | R-X | -| "urn:o-ran:fan: x.y " | R-- | R-- | R-- | --- | R-- | R-- | R-- | -| "urn:o-ran:sync: x.y " | RWX | RWX | R-- | --- | RWX | R-X | R-X | -| "urn:o-ran:delay: x.y " | RW- | R-- | R-- | --- | R-- | RW- | R-- | -| "urn:o-ran:module-cap: x.y " | RW- | R-- | R-- | --- | R-- | RW- | R-- | -| "urn:o-ran:udpecho: x.y " | RW- | R-- | --- | --- | RW- | R-- | R-- | -| "urn:o-ran:operations: x.y " | RWX | RW- | R-- | --- | RWX | RWX | R-X
(note 10) | -| "urn:o-ran:uplane-conf: x.y " | RWX | RWX | R-- | --- | R-- | RWX | RWX
(note 6) | -| "urn:o-ran:beamforming: x.y" | R-X | R-X | R-- | --- | R-- | R-X | R-- | -| "urn:o-ran:lbm: x.y " | RW- | RW- | R-- | --- | RW- | R-- | R-- | -| "urn:o-ran:software-management: x.y " | R-X | R-X | R-- | R-X | R-X | R-- | R-- | -| "urn:o-ran:file-management: x.y " | R-X | R-X | R-X | --- | R-X | --- | --- | -| " urn:o-ran:message5: x.y " | RW- | R-- | R-- | --- | R-- | RW- | R--
(note 6) | -| "urn:o-ran:performance-management: x.y " | RWX | RWX | RWX | --- | RWX | R-X | R-X
(note 6) | -| "urn:o-ran:transceiver: x.y " | RW- | RW- | R-- | --- | RW- | R-- | R-- | -| "urn:o-ran:externalio: x.y " | RWX | RWX | --- | --- | RWX | R-- | R-- | -| "urn:o-ran:ald-port: x.y " | RWX | RWX | --- | --- | RWX
(note 3) | RWX | --- | -| "urn:o-ran:interfaces: x.y " | RWX | RWX | R-- | --- | RWX | R-- | R-- | -| "urn:ietf:params:xml:ns:yang:ietf-ip" | RW- | RW- | R-- | --- | RW- | R-- | R-- | -| "urn:ietf:params:xml:ns:yang:ietf-interfaces" | RW- | RW- | R-- | --- | RW- | R-- | R-- | -| "urn:o-ran:processing-elements: x.y " | RW- | RW- | R-- | --- | RW- | RW- | R--
(note 6) | -| " urn:o-ran:mplane-interfaces: x.y " | RW- | RW-
(note 2) | R-- | --- | RW- | R-- | R-- | -| "urn:o-ran:dhcp: x.y " | R-- | R-- | R-- | --- | R-- | R-- | R-- | -| "urn:o-ran:ald: x.y" | --X | --- | --- | --- | --X
(note 3) | --X | --- | -| "urn:o-ran:troubleshooting: x.y" | R-X | R-X | R-X | --- | R-X | --- | --- | -| " urn:o-ran:trace: x.y" | R-X | R-X | R-X | --- | R-X | --- | --- | -| "urn:o-ran:laa: x.y " | RW- | RW- | --- | --- | R-- | RW- | R-- | -| "urn:o-ran:laa-operations: x.y " | R-X | --- | --- | --- | --- | R-X | --- | -| "urn:o-ran:antcal: x.y " | RWX | R-- | --- | --- | R-- | RWX | R-X | -| "urn:ietf:params:xml:ns:yang:ietf-netconf-acm" | RW- | R-- | R-- | R-- | RW- | RW- | R-- | -| "urn:ietf:params:xml:ns:yang:ietf-yang-library" | R-X | R-X | R-X | R-X | R-X | R-X | R-X | -| "urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring" | R-X | R-X | R-X | R-X | R-X | R-X | R-X | - -| Module Rules | sudo | nms | fm-pm | swm | smo | hybrid-odu | carrier | -|-------------------------------------------------------------|------------------|------------------|-----------------|-----|------------------|------------------|------------------| -| "urn:ietf:params:xml:ns:yang:ietf-netconf-notifications" | R-X | R-X | R-X | R-X | R-X | R-X | R-X | -| "urn:o-ran:shared-cell:x.y" | RW- | RW- | --- | --- | R-- | RW- | R--
(note 6) | -| "urn:o-ran:ethernet-fwd:x.y" | RW- | RW- | --- | --- | RW- | R-- | R-- | -| "urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications" | --- | --- | --- | --- | RWX | --- | --- | -| "urn:o-ran:ves-sn:x.y" | --- | --- | --- | --- | RW- | --- | --- | -| "urn:ieee:std:802.1X:yang:ieee802-dot1x" | RW- | RW- | R-- | --- | RW- | R-- | R-- | -| "urn:ieee:std:802.1X:yang:ieee802-dot1x-eapol" | RW- | RW- | R-- | --- | RW- | R-- | R-- | -| "urn:ieee:std:802.1Q:yang:ieee802-dot1q-cfm" | RW- | RW- | R-- | --- | RW- | R-- | R-- | -| "urn:o-ran:o-ran-ieee802-dot1q-cfm" | RW- | RW- | R-- | --- | RW- | R-- | R-- | -| "urn:ietf:params:xml:ns:yang:ietf-system" | RW-
(note 5) | RW-
(note 5) | R--
(note 5) | --- | RW-
(note 5) | R--
(note 5) | R--
(note 6) | -| "urn:ietf:params:xml:ns:yang:ietf-truststore" | RW- | R-- | --- | --- | RW- | R-- | R-- | -| "urn:ietf:params:xml:ns:yang:ietf-keystore" | R-X
(note 11) | R-X
(note 11) | --- | --- | R-X
(note 11) | R-X
(note 11) | R--
(note 11) | -| "urn:o-ran:certificates:x.y" | RW- | --- | --- | --- | RW- | RW- | --- | -| "urn:o-ran:frequency-band-measurement:x.y" | R-X | R-- | --- | --- | R-X | R-X | --- | - -NOTE 1: The rule list for "urn:o-ran:user-mgmt:1.0" shall additionally deny reading of the password leaf by any NETCONF client - -NOTE 2: The rule list for "urn:o-ran:mplane-int:1.0" shall additionally deny the writing of the **configured-client-info** container for NETCONF sessions with "nms" group privileges. - -NOTE 3: While the rule list for models related to Antenna Line Devices (ALD) permit SMO configuration privileges, the operation of the current architecture, including requiring the use of regular NETCONF RPCs to tunnel heartbeat messages to the ALD, may limit the scalability of scenarios where the SMO is providing for the ALD Controller function described in clause 14.4. - -NOTE 4: The rule list for "urn:o-ran:supervision:x.y" shall additionally deny writing of the **cu-plane-monitoring** container for NETCONF sessions with "smo" group privileges. - -NOTE 5: The rule list for "urn:ietf:params:xml:ns:yang:ietf-system" shall additionally deny write access to the **clock** container and the **authentication** container and deny read access to the **system-state** container for all group privileges. - -NOTE 6: Clause 19 describes further details of how carrier privileges are refined based on **sro-id** for O-RUs that support the **SHARED-ORU-MULTI-OPERATOR** feature. - -NOTE 7: The carrier rule list prohibits read and write to o-ran-usermgmt YANG model, but allows access to the **sro-id** leaf instance defined in o-ran-usermgmt from different data structures by reference. - -NOTE 8: Execution access privilege applies to chg-password RPC only. - -NOTE 9: Void. - -NOTE 10: Execution access privilege applies to subscription for the notification **emergency-wake-up-complete** and notification **deep-hibernate-activated** only. Privilege to execute the **deep-hibernate** RPC shall be denied. - -NOTE 11: The present document only supports CMPv2 as the method to issue a certificate. An O-RU controller can use the ietf-keystore model to read the installed certificate(s) and/or trigger the generation of a certificate signing request. - -The O-RU shall encode the mappings defined in Table 6.5-1 in the **rule** list in ietf-netconf-acm.yang model. Only Multi-Operator O-RUs are required to support the "carrier" privilege group. The sudo access control group shall be supported by all O-RUs. This rule list shall be unmodifiable by any NETCONF client. O-RU shall use the same model for configuring the mapping between different **user-names** and **groups**. - -NOTE: The operation of an O-RU when using other vendor defined pre-configured **groups** is not defined in the present document. - -## 6.6 NETCONF capability discovery - -The O-RU shall advertise its NETCONF capabilities in the NETCONF Hello message. The Hello message sent by the O-RU shall include the element containing the session ID for the NETCONF session and shall provide an indication of support for standard features defined in NETCONF RFCs as well as support for specific namespaces. - -NETCONF capabilities are exchanged between the O-RU and the NETCONF client(s). Examples of capabilities are specified in clause 8 of RFC 6241 [3] and include the following capability items: - -- Writable-running Capability -- Candidate Configuration Capability and associated Commit operation -- Discard change operation -- Lock and un-lock operations -- Confirmed commit Capability -- Cancel commit operation -- Rollback on error capability -- Validate Capability -- Startup configuration capability -- URL capability -- XPATH capability -- Notifications -- Interleave capability - -O-RUs shall support the "XPATH capability". - -O-RUs shall support "Notifications". - -- O-RUs shall support subscribing to receive event notifications, as specified in clause 2 of RFC5277 [21] -- O-RUs may support dynamic subscriptions to receive event notifications, as specified in clause 2.4 or RFC8639 [37]. - -The use of RPC in the present document can be understood as being equivalent to the RPC for those NETCONF servers and NETCONF clients that support dynamic subscriptions as specified in RFC8639 [37]. - -O-RUs shall support at least one of the following capabilities: - -- "writable-running capability" -- "candidate configuration capability and associated Commit operation". - -In addition, an O-RU that supports "writable-running capability" should support the "rollback on error capability" and an O-RU that supports "candidate configuration capability and associated Commit operation" should support the "confirmed commit capability". - -The NETCONF client uses the **get** RPC together with sub-tree based and XPATH based to recover particular sub-trees from the O-RU. See clause 9 for more information on NETCONF based configuration management. - -In order to avoid interactions between the operation of supervision watchdog timer (see clause 6.7) and the confirmed commit timer (default value set to 600 seconds in RFC 6241 [3]), when using the NETCONF confirmed commit capability, a NETCONF client with "sudo" privileges shall ensure the confirmed-timeout is less than the **supervision-notification-interval** timer (default value 60 seconds in o-ran-supervision.yang). - -## 6.7 Monitoring NETCONF connectivity - -This clause provides description of NETCONF connectivity monitoring for persistent NETCONF session. Additional procedures for O-RUs that support the optional NON-PERSISTENT-MPLANE feature to monitor the communication path between the O-RU and Event-Collector are defined in clause 18.6. - -When having a session with a NETCONF client that has subscribed to receive the **supervision-notification**, the O-RU shall operate watchdog timers (supervision timer and notification timer) to ensure that the session to the NETCONF client is persistent, as illustrated in Figure 6.7-1. The O-RU provides NETCONF Notifications to indicate to remote systems that its management system is operational. - -For the O-RU that supports feature SUPERVISION-WITH-SESSION-ID, these **supervision-notification** messages shall also indicate the NETCONF **session-id** associated with the subscription to the event notification. When subscribing to receive the **supervision-notification**, a NETCONF client may use its own NETCONF session-id in the subscription filter criteria to indicate to the O-RU which **supervision-notification** events the O-RU shall forward to the NETCONF client. The session-id is provided by the NETCONF server to the NETCONF client in the initial Hello exchange, see clause 6.6. - -An O-RU controller that has subscribed to the supervision-notification shall use the RPC to indicate to O-RU the O-RU controller is operational. - -NOTE 1: This supervision is intended to be used with the NETCONF client associated with the operation of the peer to the O-RU's lower layer split and clause 6.5 describes which NETCONF clients have privileges to subscribe to the **supervision-notification**. - -A NETCONF server shall support the operation of individual supervision watchdog timers for each NETCONF client which has subscribed to **supervision-notification**. - -The privileged NETCONF client may enable the operation of the watchdog timers by creating supervision-notification subscription. After operation of watchdog timers is enabled - the timers are considered as running. - -The O-RU shall use two timers, referred generically as watchdog timers, to support the bi-directional monitoring of NETCONF connectivity: - -- Notification timer: - -Value: Equal to **supervision-notification-interval** (default value: 60s) - -Operation: The O-RU sends **supervision-notification** to those NETCONF clients that have subscribed to receive such notifications. The O-RU sends **supervision-notification**, at the latest when the timer expires. The O-RU Controller confirms that NETCONF connectivity to the O-RU is operational by receiving the notification. - -- Supervision timer: - -Value : Equal to **supervision-notification-interval** (default value: 60s) + **guard-timer-overhead** (default value: 10s) - -Operation: The O-RU identifies supervision failure operation when the timer expires. To avoid supervision timer expiration, a NETCONF client who has subscribed to receive the **supervision-notification** should repeatedly reset this supervision timer. Such supervision timer reset is considered by O-RU as confirmation that NETCONF connectivity to the O-RU Controller is operational. - -The O-RU shall enable dedicated watchdog timers for specific NETCONF client when it receives a RPC from a NETCONF client with required privileges. The notification timer shall be started when the O-RU receives a RPC, but how the O-RU treats the supervision timer is up to O-RU's implementation based on the above definition. After the watchdog timers have been enabled, the O-RU shall send **supervision-notification** after the expiry of the notification timer. An O-RU Controller who has subscribed to the **supervision-notification** shall be prepared to receive the notification at any time when the watchdog timers are running. - -A NETCONF client that has triggered operation of watchdog supervision by using the RPC to subscribe to the **supervision-notification** may cancel the subscription by using the RPC, as specified in clause 9.1.7.3. An O-RU receiving a RPC from a NETCONF client for an existing **supervision-notification** shall cease operation of the watchdog supervision with that NETCONF client. - -NOTE 2: In case there are active carriers and watchdog supervision is active, it is not recommended to delete the subscription to the supervision-notification. - -The NETCONF client should send **supervision-watchdog-reset** RPC in order not to cause the Supervision timer to expire, and the O-RU should send next notification timestamp as **next-update-at** in reply. - -NOTE 3: **next-update-at** is just informative. - -In the **supervision-watchdog-reset** RPC, the NETCONF client may configure new values for the watchdog timers using RPC parameters "supervision-notification-interval" and "guard-timer-overhead". When the O-RU receives the **supervision-watchdog-reset** RPC, it shall reset its supervision timer and notification timer. When the watchdog timers are running, the O-RU shall be prepared to receive **supervision-watchdog-reset** RPC at any time - also within supervision timer period. - -The NETCONF client can set new value of watchdog timers without receiving **supervision-notification** from the O-RU. The new values are taken into use immediately with respect to **supervision-watchdog-reset** RPC content. The next notification should be expected not later than at the moment addressed in timestamp provided by RPC reply. - -If another NETCONF client has locked the running configuration, e.g. when operating in hybrid mode of operation, and if the O-RU Controller attempts to configure a new value of the watchdog timer(s) by sending the **supervision-watchdog-reset** RPC, then the RPC operation to reset the watchdog timer will succeed, but the related backend implementation to modify the watchdog timer(s) may fail. In such circumstances, the O-RU may use the **error-message** in the RPC output to indicate to the O-RU Controller that the configuration modification has failed. - -If the supervision timer expires, the O-RU shall enter "supervision failure" condition, as described in clause 14. If all NETCONF sessions to NETCONF clients with "sudo" privileges are closed, the O-RU shall immediately disable operation of the supervision timer. - -![Sequence diagram showing the supervision process between a NETCONF server (O-RU) and a NETCONF client. The process involves subscription, timer management, periodic notifications, failure handling, and session termination.](24ca460ee3381aee781887e9e586ec67_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF client - participant Server as NETCONF server (O-RU) - - Note right of Client: client subscribes to receive the "supervision-notification" event - Client->>Server: - Note left of Server: Notification timer is started with default value (60 sec) - Note left of Server: Supervision timer is started with default value (60 sec + 10 sec) - Server-->>Client: - - loop supervision loop - opt changing default timers (example values used) - Note right of Client: Reset notification timer and supervision timer for NETCONF session. Use values provided in RPC to calculate notification timer and supervision timer. - Client->>Server: (supervision-notification interval = 70, guard-timer-overhead = 15) - Note left of Server: O-RU uses non-default values of watchdog timers - Server-->>Client: date-time - end - - opt regular flow of supervision messages - Note left of Server: Notification timer expires - Server-->>Client: - Note right of Client: NETCONF Client knows O-RU's management system is operational - - opt supervision timer expiry - Note left of Server: supervision timer expiry - Note left of Server: Supervision Failure handling - Client->>Server: - Note left of Server: Reset watchdog timers for NETCONF session - Server-->>Client: date-time - Note left of Server: O-RU knows peer management system is operational - end - end - - opt supervision terminated by NETCONF client - alt close NETCONF session - Client->>Server: - alt kill NETCONF session - Client->>Server: - alt subscription stop time is reached - Note left of Server: Supervision Termination handling - end - end - end - -``` - -The sequence diagram illustrates the supervision process between a NETCONF client and a NETCONF server (O-RU). It begins with the client subscribing to the "supervision-notification" event via a RPC. The server starts a notification timer (default 60 sec) and a supervision timer (default 60 sec + 10 sec), then responds with . A "supervision loop" follows, containing three optional segments: 1) "changing default timers (example values used)" where the client can reset timers with specific values (e.g., interval=70, overhead=15) and the server confirms with . 2) "regular flow of supervision messages" where the notification timer expires, the server sends a , and the client acknowledges the server's operational status. If the supervision timer expires, the client sends a , the server resets timers, and confirms the peer is operational. 3) "supervision terminated by NETCONF client" which includes alternatives for closing the session (), killing the session (), or reaching a subscription stop time, all leading to supervision termination handling. - -Sequence diagram showing the supervision process between a NETCONF server (O-RU) and a NETCONF client. The process involves subscription, timer management, periodic notifications, failure handling, and session termination. - -**Figure 6.7-1: Monitoring NETCONF Connectivity** - -NOTE 4: A NETCONF client can use the **create-subscription** for the single **supervision-notification** event stream, or alternatively subscribe to the default event-stream using additional filter criteria to identify the supervision notification. In order to subscribe to multiple notifications, the appropriate **create-subscription** message is required. Refer to clause 11.3 for the appropriate example of **create-subscription** of multiple notifications. - -Figure 6.7-1 illustrates the O-RU ceasing supervision operation triggered by two options: - -- 1) The supervision timer expires. In such case, the O-RU shall perform Supervision Failure handling as described in clause 14.1.1. -- 2) The NETCONF client terminates the subscription to the **supervision-notification**. The NETCONF client can either close the subscription session, terminate the NETCONF session or wait for the subscription stop time to be reached. In such case the O-RU performs Supervision Termination handling as described in clause 14.1.2. - -## 6.8 Closing a NETCONF session - -A NETCONF client closes an existing NETCONF session by issuing the RPC **close-session** command. The O-RU shall respond and close the SSH session or TLS connection. If the NETCONF client is a Call home O-RU controller, the O-RU shall then re-commence call home procedures, as described in clause 6.3. In case the O-RU is operating in deep-hibernate mode and the hibernate-time timer is operational, as specified in clause 20.5, the O-RU shall suspend call home procedures. - -Under normal operations, it is expected that at least one NETCONF session with "sudo" or "hybrid-odu" privileges are long-lived and used to repeatedly reset the O-RU's supervision watchdog timer for the NETCONF session. NETCONF clients associated with other privilege groups are not required to operate using persistent NETCONF sessions. - -If a NETCONF client has been previously become known to an O-RU by being configured using NETCONF, and the NETCONF client is subsequently removed from the O-RU's configuration, e.g. by a second NETCONF client with "sudo" privileges, the NETCONF server shall force the termination of the NETCONF session to the removed client. - -## 6.9 PNF registration - -### 6.9.1 Introduction - -The support by an O-RU of PNF Registration to a discovered Event-Collector is optional and hence clause 6.9 only applies to those O-RUs that support this optional capability. An O-RU that support pnfRegistration shall also support the Monitoring the Communications Channel between O-RU and Event-Collector as defined in clause 18.6. In case the O-RU is operating in in deep-hibernate mode and the hibernate-time timer is operational, as specified in clause 20.5, the O-RU shall suspend PNF Registration procedures. - -### 6.9.2 PNF registration procedure - -The pnfRegistration notification is a JSON encoded message sent from the O-RU to the discovered Event-Collector using REST/HTTPS. As a pre-condition to performing PNF Registration, the O-RU first receives the Event-Collector information encoded in a DHCP/DHCPv6 option as described in clause 6.2.7. The O-RU shall attempt to establish a HTTP connection to the discovered Event-Collector using TLS to authenticate the connection. It shall then signal the pnfRegistration notification over the HTTP/TLS connection. The sending of the pnfRegistration notification is repeated - -periodically until the SMO establishes a NETCONF session with the O-RU. These procedures are illustrated in Figure 6.9.2-1. - -An O-RU that is performing the PNF registration procedure whilst simultaneously performing the call home procedure described in clause 6.3, shall be able to determine that the SMO has established a NETCONF session with the O-RU. This is identified by the O-RU analysing the source IP address from which the NETCONF originates, based on the assumption that the NETCONF session from the SMO originates from an IP address that is distinct from the IP address(es) of the call home O-RU Controller(s) to which the O-RU is simultaneously performing the call home procedure. - -![Sequence diagram of PNF Registration Procedure. Lifelines: Event-Collector, SMO/(NECTONF Client), DHCP, O-RU/(Event-Producer)/(NETCONF Server). The process starts with Event-Collector discovery (1 DHCP Option 43). Then a loop for periodic sending of pnfRegistration notification (2 Authenticate Connection, 3 pnfRegistration notification). After the loop, pnfRegistration Indication (4) is sent to SMO, which then Establishes NETCONF Session (5) with O-RU. A note indicates that the establishment of NETCONF session ceases repeated sending of pnfRegistration notification.](5bba23cc120ad806779f82df1c01bebf_img.jpg) - -``` - -sequenceDiagram - participant EC as Event-Collector - participant SMO as SMO/(NECTONF Client) - participant DHCP as DHCP - participant O-RU as O-RU/(Event-Producer)/(NETCONF Server) - - Note right of O-RU: Event-Collector discovery - O-RU->>EC: 1 DHCP Option 43 Encoded Event-Collector Information - loop periodic sending of pnfRegistration notification - O-RU->>SMO: 2 <> Authenticate Connection - O-RU->>SMO: 3 <> pnfRegistration notification - end - O-RU->>EC: 4 pnfRegistration Indication - SMO->>O-RU: 5 Establish NETCONF Session - Note right of O-RU: Establishment of NETCONF session ceases repeated sending of pnfRegistration notification - -``` - -Sequence diagram of PNF Registration Procedure. Lifelines: Event-Collector, SMO/(NECTONF Client), DHCP, O-RU/(Event-Producer)/(NETCONF Server). The process starts with Event-Collector discovery (1 DHCP Option 43). Then a loop for periodic sending of pnfRegistration notification (2 Authenticate Connection, 3 pnfRegistration notification). After the loop, pnfRegistration Indication (4) is sent to SMO, which then Establishes NETCONF Session (5) with O-RU. A note indicates that the establishment of NETCONF session ceases repeated sending of pnfRegistration notification. - -Figure 6.9.2-1: PNF Registration Procedure - -The O-RU that exposes presence of feature **PNF-REGISTRATION-ATTEMPTS** should use the **re-pnf-registration-timer** to repeat the PNF registration notification. This activity is repeated by the O-RU until, either: - -- 1) The SMO establishes a new NETCONF session with the O-RU. - -Or, - -- 2) After **max-pnf-registration-attempts** has been reached and a new NETCONF session cannot be established. - -When the O-RU uses the **re-pnf-registration-timer** to repeatedly trigger the PNF registration notification, and the O-RU fails to trigger the PNF registration notification with at least one Event-Collector after completing the PNF Registration procedure a total of **max-pnf-registration-attempts** per Event-Collector, and no other NETCONF sessions exist, the O-RU should perform an autonomous reset. If there remains at least one NETCONF session connected, the O-RU shall repeat pnfRegistration notification periodically until the SMO establishes a NETCONF session with the O-RU. The values of **re-pnf-registration-timer** and **max-pnf-registration-attempts** shall be stored in the O-RU's reset persistent memory. - -Once restarted, the PNF registration process shall continue until M-Plane session is successfully re-established or the counter **max-pnf-registration-attempts** is reached. - -### 6.9.3 Encoding of PNF registration notification - -In the present document, the encoding of the pnfRegistration notification follows the ONAP definition [i.2]. - -The pnfRegistration notification shall include the IP address information necessary for a NETCONF client to establish IP connectivity to the NETCONF Server in the O-RU. - -The contents of the pnfRegistration notification are derived from the O-RU's configuration database using Table 6.9.3-1. An O-RU shall support the **o-ran-hardware.yang** model revision 5.0.0, or later, which defines the schema nodes corresponding to unitFamily and unitType values and the **o-ran-operations.yang** model revision 5.0.0, or later, which defines the schema nodes corresponding to the version of pnfRegistration fields. - -**Table 6.9.3-1: Mapping from O-RU's Operational Data to PnfRegistration fields** - -| PnfRegistration Notification Field | YANG Operational Data | O-RU pnfRegistration requirements | -|------------------------------------|--------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| -| lastServiceDate | /hw:hardware/hw:component/or-hw:last-service-date | The O-RU may include the lastServiceDate field | -| macAddress | /if:interfaces/if:interface/o-ran-int:mac-address | The O-RU may include the macAddress field | -| manufactureDate | /hw:hardware/hw:component/hw:mfg-date | The O-RU may include the manufactureDate field | -| modelNumber | /hw:hardware/hw:component/hw:model-name | The O-RU shall include the modelNumber field | -| oamV4IpAddress | /if:interfaces/if:interface/ip:ipv4/ip:address/ip:ip | When the O-RU has IPv4 address assigned for management plane (as specified in clause 6.2.4), it shall include the oamV4IpAddress field (note 1) | -| oamV6IpAddress | /if:interfaces/if:interface/ip:ipv6/ip:address/ip:ip | When the O-RU has IPv6 address assigned for management plane (as specified in clause 6.2.4), it shall include the oamV6IpAddress field (note 1) | -| pnfRegistrationFields Version | /o-ran-ops:operational-info/o-ran-ops:declarations/o-ran-ops:supported-pnf-registration-fields-version | The O-RU shall include the pnfRegistrationFieldsVersion field | -| serialNumber | /hw:hardware/hw:component/hw:serial-num | The O-RU shall include the serialNumber field | -| softwareVersion | /hw:hardware/hw:component/hw:software-rev | The O-RU shall include the softwareVersion field | -| vendorName | /hw:hardware/hw:component/hw:mfg-name | The O-RU shall include the vendorName field | - -NOTE 1: The PNF registration operation of an O-RU that uses o-ran-mplane-int YANG model to report multiple **m-plane-sub-interfaces** list entries of the same IP address type is not defined in the present document. - -## 6.10 On-demand renewal of Call Home procedure - -The O-RU that exposes presence of feature CALL-HOME-REACTIVATION-SUPPORTED can be triggered to re-activate timed out call-home procedure towards call home O-RU controllers. The RPC sent by any active O-RU controller having necessary permissions shall cause O-RU to re-start call home towards all not actively connected call home O-RU controllers as described in clause 6.3. - -Once restarted, the call home flows shall continue until M-Plane session with lost call home O-RU controller(s) is successfully re-established or until counter max-call-home-attempts is exhausted. - -For every call home O-RU controller for which supervision is recovered in(as) result of RPC , the O-RU shall cancel alarm 35 "Lost O-DU ID based Supervision" when supervision is successfully recovered - -This RPC has no impact on O-RU operations with call home controllers that have M-Plane session established with O-RU. - -In case O-RU is performing call home procedure towards call home O-RU controller, the RPC shall trigger the O-RU to re-initialize its internal counter based on value of node max-call-home-attempts and continues call home procedure. - -## 6.11 TLS sessions and certificate expiry - -After a certificate has been re-issued, an O-RU may continue to use M-Plane sessions (e.g. NETCONF, FTPeS) authenticated using a previously issued, un-expired certificate. New M-Plane sessions shall use the certificate with the longest time to expiration, as described in clause 6.4.2. - -After having received a notification that an O-RU has been re-issued a certificate by the Operator PKI, an O-RU controller should schedule the closing of existing NETCONF session by issuing the RPC close-session command following the procedure specified in clause 6.8. - -NOTE 1: The timing of the scheduled session closing can be arranged to minimize any service impacting effects. - -NOTE 2: The operation of the O-RU when the certificate used to authenticate an on-going M-Plane session expires is not defined. - ---- - -## 7 O-RU to O-DU interface management - -### 7.1 O-RU interfaces - -An O-RU has a number of network interfaces, including Ethernet, VLAN and IP interfaces. This clause describes the management of these network interfaces. - -The O-RU's configuration for its interfaces is defined using the o-ran-interfaces.yang module. This module augments the standard ietf-interfaces.yang and ietf-ip.yang modules. The O-RU's interfaces are built on a layering principle where each interface has a unique **name**. - -All interfaces are referenced by their **port-number** and **name**. The base interface corresponds to the Ethernet interface. These leafs describe the maximum transmission unit (**l2-mtu**), the hardware-address as well as optional alias mac addresses that may be used to transport the CU plane. An O-RU can indicate the maximum Ethernet payload size per O-RU Ethernet interface it supports by using the **maximum-ethernet-payload-size** leaf. The O-RU shall reject any configuration where the Ethernet payload configured using **l2-mtu** for an Ethernet interface exceeds the value of **maximum-ethernet-payload-size**. - -NOTE 1: If an O-RU does not indicate a value of **maximum-ethernet-payload-size** in its operational state, the operator and O-RU vendor can agree on a maximum Ethernet frame size. - -NOTE 2: The definition of the read-only **maximum-ethernet-payload-size** is different from the **l2-mtu** definition. The description in the YANG model defines how to map between the two and Figure 7.1-0a illustrates an example subset of configuration and operational data. - -``` - - - 10Geth0 -``` - -``` - -ianaift:ethernetCsmacd - -true - - - 9014 - - - - 9000 - - - - true - - - - - - -``` - -**Figure 7.1-0a: Example subset of configuration and operational data related Ethernet payload size** - -Additionally, for O-RUs that include the ieee802-dot1x and ietf-system models in their YANG library the /if:interfaces/if:interface/dot1x:pae/dot1x:port-capabilities/dot1x:supp schema node enables an O-RU Controller to configure operation of IEEE 802.1X Port based Access Control, as specified in [70]. - -Above the Ethernet interface are VLAN interfaces. Both Ethernet and VLAN interfaces can support IP interfaces. IP interfaces are defined using the standard ietf-ip.yang model. The O-RU controller can restrict the maximum size of IP packets using the /if:interfaces/if:interface/ip:ipv4/ip:mtu and/or the /if:interfaces/if:interface/ip:ipv6/ip:mtu leaves. Accordingly, each IP interface can have an IPv4 and/or IPv6 interface(s) defined. An O-RU may support the **PER-INT-TCP-MSS** feature that allows an O-RU controller to configure the TCP Maximum Segment Size (MSS). When the O-RU supports the **PER-INT-TCP-MSS** feature, the O-RU shall reject any configuration where the **mss-adjust** leaf for an interface exceeds the value of /ip:mtu configured on the same interface. - -When a value of the **mss-adjust** leaf is configured, an O-RU shall set its value of MSS option to the configured value, independently of any MSS value derived using discovered MTU procedures. Figure 7.1-0b illustrates a subset of configuration data that enables a UDP/IP based CUS-Plane to benefit from 9000 byte payload, compared with the TCP based M-plane that is restricted to a payload of 1500 bytes. - -``` - - - - - - 10Geth0 - - ianaift:ethernetCsmacd - - true - - - - false - - - - - - 9000 - - - - 1460 - - - - - - - - 9000 - - - - 1440 - - - - - - - - - -``` - -**Figure 7.1-0b: Example subset of configuration data related to different IP payload size for CU-Plane and M-Plane** - -The O-RU shall provide operational state associated with the layer 3 configuration of these interfaces, including prefix(es), using the ietf-ip YANG model, and domain name servers and default gateway addresses, using the o-ran-dhcp YANG model. An example of such operational state for the ietf-ip YANG model is shown in Figure 7.1-1. - -``` - - - - true - -
- - 10.10.0.17 - - 255.255.255.0 - - dhcp - -
- -``` - -</ipv4> - -**Figure 7.1-1: Example operational data related to an IP interface** - -Finally, leafs associated with CoS and DSCP marking are defined, enabling independent configuration of CoS and DSCP markings for u-plane, c-plane and m-plane traffic. As a default, all user-plane flows are marked identically by the O-RU. Optionally, the interfaces can be configured to support enhanced user plane marking for up-link traffic whereby different CoS or DSCP values can be configured. This enables individual receive endpoints in the O-RU to be configured with different markings to then enable differentiated handling of up-link flows by the transport system. - -Because the o-ran-interfaces model defines augments to the ietf-interfaces model, the O-RU can leverage the definition of operational state in ietf-interfaces to optionally report packet and byte counts on a per interface basis. A single RPC is defined in the o-ran-interfaces module, to enable these counters to be reset. - -## 7.2 Transceiver - -### 7.2.1 General - -The o-ran-transceiver YANG module is used to define operational state for the pluggable transceiver module (like SFP, SFP+, SFP28, XFP and QSFP, QSFP+, QSFP28, QSFP56). Each transceiver is associated with a unique **interface-name** and **port-number**. Interfaces accessible through the transceiver are provided by the **interface-name**, **interface-names** and **additional-multi-lane-reporting/interface-names** leaves in the o-ran-transceiver YANG module. - -A digital diagnostic monitoring interface for optical transceivers is used to allow access to device operating parameters. As specified in SFF-8472 [16] and SFF-8636 [34], data is typically retrieved from the transceiver module in a file. This file may be obtained from O-RU by the NETCONF client. See clause 9 for more details. - -With QSFP form factor, the optical links may be multi-wavelengths (4xTx & 4xRx) and/or multi-fibres (MPO - Multifibre Parallel Optic). The QSFP digital diagnostic interface as specified in SFF-8636 [34] describes the use of optical lanes and the O-RU interface management defines alarm 29 : "transceiver fault" for all media lanes. - -The byte with offset i (i=0, ..., 511) from the beginning of the file is the byte read from data address i of the transceiver memory at two-wire interface address 0xA0 if i<256, otherwise it is the byte read from data address i-256 of the transceiver memory at two-wire interface address 0xA2. The retrieved data is stored in the file without any conversion in binary format. - -The O-RU stores data from the transceiver module on transceiver module detection during start-up. The data from the transceiver module is saved in the file. A NETCONF client can upload it by using the File Upload procedure defined in clause 12. The O-RU does not synchronise contents of the file with transceiver memory in runtime, therefore bytes representing dynamic information are expected to be outdated. The O-RU does not remove the file on transceiver module removal. If a transceiver module is inserted during File Upload procedure, then the procedure may provide a file with previous content or fail (with failure reason as listed in File Upload procedure). If the O-RU is unable to retrieve the data from the transceiver module or it is not present, then the O-RU does not create the file or removes the file created earlier - -NOTE: File Upload procedure requesting non-existing file will fail. - -The file name shall have the following syntax: - -- sfp\_{portNumber}.sffcap - -where {portNumber} is the value of **port-number** leaf of the corresponding list of port-transceiver data. Examples: sfp\_0.sffcap, sfp\_1.sffcap. - -## 7.2.2 Transceiver presence change notification - -The O-DU may subscribe to transceiver presence change notifications, which report the status of the transceiver presence. The following notification is defined in the YANG model: - -- **transceiver-presence-change** - conveys the **port-transceiver-data** information (transceiver-presence, name, port-number, interface-name). - -The above notification is sent to the subscribed O-RU controllers whenever O-RU detects that presence of a transceiver module has changed, as illustrated in Figure 7.2.2-1. - -![Sequence diagram showing transceiver presence change notification from O-RU to O-RU Controller.](bd50d56ae2c12a92466ba2aea1a78040_img.jpg) - -``` - -sequenceDiagram - participant O-RU as NETCONF Server/ O-RU - participant Controller as NETCONF Client/ O-RU Controller - Note left of O-RU: O-RU detects that the transceiver module is not present any more - O-RU->>Controller: - - false - ... - ... - ... - - - -``` - -The diagram illustrates the flow of a transceiver presence change notification. It starts with a yellow box on the left labeled "NETCONF Server/ O-RU". A note below it states "O-RU detects that the transceiver module is not present any more". A dashed red arrow points from the O-RU to another yellow box on the right labeled "NETCONF Client/ O-RU Controller". Along this arrow, the notification message is shown in XML-like tags: , , false, ..., ..., ..., , and . At the bottom, there are two more yellow boxes: "NETCONF Server/ O-RU" on the left and "NETCONF Client/ O-RU Controller" on the right, connected by a solid red arrow pointing from left to right. - -Sequence diagram showing transceiver presence change notification from O-RU to O-RU Controller. - -Figure 7.2.2-1: Transceiver presence change notification - -## 7.3 C/U-Plane VLAN configuration - -Within the o-ran-interfaces YANG model, each named Ethernet interface includes a leaf to indicate whether VLAN tagging is supported. By default, VLAN tagging shall be enabled on all interfaces. This permits an O-RU to autonomously discover that it is connected to a trunk port, as described in clause 6.2.3. - -When an O-RU is connected to a trunk port, VLANs will also typically be assigned to the C/U plane connections. The VLAN(s) used to support C/U plane transport may be different from the VLAN(s) used to support management plane connectivity. The VLAN assigned to the U-Plane shall be the same as the VLAN assigned to the C-Plane for any given eAxC\_ID. When different VLANs are used, the C/U plane VLANs shall be configured in the O-RU by the NETCONF client. In such circumstances, as defined in o-ran-interfaces, the NETCONF client shall configure separate named interfaces for each active VLAN. This configuration will define a C/U-Plane named VLAN interface as being the **higher-layer-if** reference for the underlying Ethernet interface and the underlying Ethernet interface is defined as being the **lower-layer-if** reference for the named VLAN interface. - -## 7.4 O-RU C/U-Plane IP address assignment - -In this release, the support for C/U plane transport over UDP/IP is optional and hence this clause only applies to those O-RUs that support this optional capability. - -An O-RU that supports C/U plane transport over UDP/IP shall support IPv4 and/or IPv6 based transport. A NETCONF client can receive a hint as to whether an O-RU supports a particular IP version by using the **get** RPC to recover the list of **interfaces** supported by the O-RU and using the presence of the augmented **ipv4** container or **ipv6** container in the o-ran-interfaces YANG module as an indication that a particular IP version is supported. - -The IP interface(s) used to support UDP/IP based C/U plane transport may be different than the IP interface(s) dynamically discovered using the procedures defined in clause 6.2.4. When different IP interface(s) is/are used, the C/U plane IP interfaces shall be configured in the O-RU by the NETCONF client by using the ietf-ip YANG model, as specified in RFC 8344 [91], to configure the **IPv4** container and/or **IPv6** container. When configured by the NETCONF client, this interface shall be configured using either a named Ethernet interface (i.e. where the interface **type** is set to **ianaift:ethernetCsmacd**) and/or a named VLAN interface (i.e. where the interface **type** is set to **ianaift:l2vlan**), depending upon whether VLANs are used to support IP based C/U plane traffic. - -When a separate C/U plane IP interface is configured by the NETCONF client, additionally the NETCONF client may statically configure IP address(es) on this interface. If the NETCONF client does not statically configure an IP address, the O-RU shall be responsible for performing IP address assignment procedures on the configured interfaces. When an O-RU Controller has configured an IP interface with **enabled** set to true, but where the O-RU Controller has not configured a static IP address, the NETCONF client can use the **autoconf** container to control the O-RU's use of autoconfiguration of IPv6 addresses as specified in RFC 8344 [91] by using the **create-global-addresses** parameter. When an **IPv6** container is configured by a NETCONF client with a **create-global-addresses** set to false, the O-RU shall attempt to configure a dynamic IPv6 address using IPv6 State-full address configuration using DHCPv6 as specified in RFC 8415 [58]. When an **IPv4** container is configured by a NETCONF client an IP interface with **enabled** set to true, but where the O-RU Controller has not configured a static IP address, the O-RU shall attempt to configure a dynamic IPv4 address using DHCPv4 as specified in RFC 2131 [10]. - -As specified in clause 6.2.8, an O-RU that supports static routing shall route IP-based C/U plane traffic towards a destination IP address based on its routing table. - -## 7.5 Definition of processing elements - -The CU-plane application needs to be uniquely associated with specific transport flows. This association is achieved by defining an O-RU "processing element" which can then be associated with a particular C/U plane endpoint eAxC ID, as specified in [2] clause 5.4 or delay measurement operation, as specified in [2] clause 4.4.4.4. Unless specified otherwise, a common processing element is required to be configured for the control and user-plane application components associated with any individual eAxC\_ID. - -The O-RU management plane supports different options for defining the transport endpoint identifiers used by a particular processing element (used depending on transport environment), supporting the following 3 options: - -- Processing element definition based on usage of different (alias) MAC addresses; -- Processing element definition based on a combination of VLAN identity and MAC address; and -- Processing element definition based on UDP-ports and IP addresses. - -NOTE: There is no well-defined source port currently allocated by IANA for the o-ran application and hence the NETCONF client can configure this port number in the O-RU. - -A processing element consists of both the local and remote transport endpoints and is used as a logical transport path. The processing element definition includes its element **name** which is then used by other systems to refer to a particular processing element instance. - -The o-ran-interfaces YANG model is used to define feature support for C/U plane transport based on alias MAC addresses and UDP/IP. The exchange of NETCONF capabilities is used to signal which optional capabilities are supported by the O-RU, as described in clause C. - -The o-ran-processing-elements YANG model uses a **processing-elements** container to define a list of processing elements. Each processing element is identified by a unique element **name**. Each processing element references a particular **interface-name** used to support the data flows associated with a particular processing element. Depending upon the type of C/U plane transport session, additionally leafs are configured that specify MAC addresses, and/or VLANs and/or IP addresses and/or UDP ports used to identify a particular processing element. - -If the O-RU reports the capability of supporting feature MULTIPLE-TRANSPORT-SESSION-TYPE, which indicates the O-RU supports multiple transport-session-type, the NETCONF client may configure **processing-elements** with more than one **transport-session-type** to the O-RU, using the list **additional-transport-session-type-elements** with the key **transport-session-type**. When a processing element configured by the list **additional-transport-session-type-elements** is referenced by other modules, the **transport-session-type** shall also be configured as a key to the list **additional-transport-session-type-elements**. - -The O-RU may discard any received CU-plane messages, i.e. eCPRI/IEEE 1914 frames/packets, which are not transported using a configured processing element. - -## 7.6 O-DU verification of C/U-Plane transport connectivity - -### 7.6.1 C/U-Plane transport connectivity verification - -As described above, there will likely be multiple C/U-plane data flows being exchanged between the O-DU and the O-RU. In order to enable checks verifying C/U-Plane end-to-end transport connectivity between the O-DU and O-RU, the O-RU shall support C/U-Plane connectivity verification capabilities using a request/reply function, as illustrated in Figure 7.6.1-1. - -Using that connectivity verification procedure, bi-directional reachability/connectivity verification between transport endpoints can be performed by the O-DU: - -- During O-RU configuration, to validate the transport configuration. -- At runtime to regularly perform bi-directional network connectivity verification. - -The periodicity for bi-directional connectivity verification is usually between 1 and 60 seconds. - -Two different network protocols are defined for performing the bi-directional transport connectivity verification procedure: - -- For C/U sessions over Ethernet: Loop-back Protocol (LBM/LBR) as specified in IEEE 802.1Q-2018 [69]. -- When the O-RU is configured to support C/U sessions over IP: UDP echo, as specified in RFC 862 [18]. - -![Sequence diagram showing C/U Plane Transport Connectivity Verification between O-DU and O-RU. The diagram is split into two alternatives: Layer 2 Connected RU and Layer 3 Connected RU. In the Layer 2 section, the O-DU sends a Loopback Message (LBM) with Transaction ID and Data/Test Pattern TLV to the O-RU, which responds with a Unicast Loopback Response Message (LBR) with the same TLV. A note indicates 'L2 Connection Verified'. In the Layer 3 section, the O-DU sends a Unicast UDP Echo to the O-RU, which responds with a Unicast UDP Echo. A note indicates 'L3 Connection Verified'.](b1784a5cbeeb3d9fb9e60b333019c721_img.jpg) - -``` - -sequenceDiagram - participant O-DU - participant O-RU - alt Layer 2 Connected RU - O-DU->>O-RU: Loopback Message (LBM) -Transaction ID, Data/Test Pattern TLV - O-RU-->>O-DU: Unicast Loopback Response Message (LBR) -Transaction ID, Data/Test Pattern TLV - Note left of O-DU: L2 Connection Verified - alt Layer 3 Connected RU - O-DU->>O-RU: Unicast UDP Echo - O-RU-->>O-DU: Unicast UDP Echo - Note left of O-DU: L3 Connection Verified - -``` - -Sequence diagram showing C/U Plane Transport Connectivity Verification between O-DU and O-RU. The diagram is split into two alternatives: Layer 2 Connected RU and Layer 3 Connected RU. In the Layer 2 section, the O-DU sends a Loopback Message (LBM) with Transaction ID and Data/Test Pattern TLV to the O-RU, which responds with a Unicast Loopback Response Message (LBR) with the same TLV. A note indicates 'L2 Connection Verified'. In the Layer 3 section, the O-DU sends a Unicast UDP Echo to the O-RU, which responds with a Unicast UDP Echo. A note indicates 'L3 Connection Verified'. - -Figure 7.6.1-1: C/U Plane Transport Connectivity Verification - -## 7.6.2 Ethernet connectivity monitoring procedure - -### 7.6.2.1 Transport connectivity verification monitoring Procedure - -When the O-RU and O-DU are operating their C/U sessions transported over Ethernet, the transport connectivity verification checks operate at the Ethernet layer. The protocol for Ethernet connectivity verification shall use the Loop-back Protocol as defined by IEEE 802.1Q-2018 [69]. - -For the purpose of regular connectivity verification, all transport endpoints used for C/U-plane messaging in the fronthaul network shall be configured to be part of the same Maintenance Entity (ME). The O-RU Controller shall configure each O-RU, assigning them the role of a Maintenance association End Point (MEP) for LBM. - -The sending of Loop-back Messages (LBMs) is administratively initiated and stopped in the O-DU. Therefore, sending LBM requests needs to be requested by an administration entity, specifying an Ethernet interface of the O-RU responder. If administratively initiated, the O-DU shall send the LBM request. When sending the LBM request, support for setting the destination MAC address as the unicast MAC address of the specified O-RU Ethernet interface as per IEEE 802.1Q-2018 [67] is mandatory while the support for setting the destination MAC address as the group destination MAC address 01-80-C2-00-00-3x as specified in Recommendation ITU-T Y.1731 [25] clause 7.2.2, where the LSB 4 bits are derived from the md-level configuration in o-ran-lbm.yang, is optional. See also clause 10.1 of Recommendation ITU-T Y.1731 [25]. - -An O-RU that supports LBM configuration using the ieee802-dot1q-cfm YANG model shall include the ieee802-dot1q-cfm model in its YANG library. Such an O-RU can have a common LBM configuration datastore and operational data, exposed by both ieee802-dot1q-cfm and o-ran-lbm YANG models. - -For example, an O-RU can ensure the value of **replies-transmitted** in o-ran-lbm YANG model to be set as identical to that value of **mep-lbr-out** in the ieee802-dot1q-cfm YANG model. - -In case the coordination of LBM configuration happens external to the O-RU, when LBM configuration is inconsistent between two models, the LBM behaviour of the O-RU is not specified by the present document. - -O-RUs that supports ieee802-dot1q-cfm.yang shall support the Notification of Updates to its Configuration Datastore functionality, as specified in clause 9.4. Hence, any NETCONF clients connected to the O-RU may configure subscriptions to receive notifications of modifications to ieee802-dot1q-cfm.yang and/or o-ran-lbm.yang configuration changes. - -### 7.6.2.2 Validating the transport configuration - -After setting up a U/C-plane session between an O-DU and an O-RU, the O-DU can test whether connectivity exists as per the configuration. To achieve that, at the time a transport endpoint becomes operational at an O-RU, it starts an LBM responder application which automatically responds to incoming LBM requests on that transport endpoint. Based on a configuration command the O-DU starts sending out a predefined number of LBM requests to its O-RU(s) at a predefined interval, storing the information received in LBM responses from the O-RU(s) in an internal database. O-RU(s) are identified by both Ethernet MAC address and the CU plane VLAN. - -The O-RU shall be able to respond to Loopback Messages received from different remote Maintenance Association Endpoints, when the destination MAC address is the O-RU's MAC address. The O-RU should respond to Loopback Messages received from different remote Maintenance Association Endpoints, when the destination MAC address is a group destination MAC address as defined in clause 10.1 of [25]. In case the O-RU is operating in deep-hibernate mode and the hibernate-time timer is operational, as specified in clause 20.5, the O-RU may suspend Loopback Message processing. - -In case the configuration of the session is indeed correct, the O-DU should receive LBM responses from the O-RU(s) within a time frame dependent on the network latency and the O-RU's reaction time. If LBMs from the O-RU(s) are being received, the session is determined to be operational. - -### 7.6.2.3 Monitor network connectivity - -After the procedure described in clause 7.6.2.2 has been executed successfully, a further procedure may be executed continuously to maintain the connectivity status. To achieve this the O-DU can continually send out LBM requests at the configured interval. It also keeps track of LBM responses received. - -Based on the LBM responses received the O-DU shall decide on the connectivity status. Connectivity shall be assumed to be available as long as LBM responses from the O-RU(s) are being received at the configured interval. Connectivity shall be assumed not available if no LBM response from the particular O-RU has been received for an interval that is as long as 3 x the configured LBM request interval or longer. - -Optionally, for those O-RUs that advertise support for the ieee802-dot1q-cfm.yang, the O-DU can enable O-RU sending of Connectivity Check Messages (CCM) by configuring **ccm-enabled** to "true" on the O-RU. The O-DU can monitor network connectivity by received CCM message from the O-RU. These CCM messages are sent to a multicast destination address which encodes the maintenance domain level as specified in Table 8-18 of IEEE 802.1Q[67]. - -### 7.6.2.4 Managing ethernet connectivity monitoring procedure - -An O-DU may have one or more Ethernet interfaces that have to support the Ethernet connectivity monitoring procedure. This clause describes the management of this function. The module described here is based on (i.e. a subset of) the mef-cfm module defined by the Metro Ethernet Forum [i.3]. This is to allow for a later extension of the module to the full feature set of mef-cfm. - -The YANG module provided below supports the configuration and fault management of the Loop-back Protocol as defined by IEEE 802.1Q-2018 [69]. - -Derived from MEF CFM YANG, the subset of type definitions is defined as part of the o-ran-lbm.yang. - -## 7.6.3 IP connectivity monitoring procedure - -### 7.6.3.1 Monitoring procedure - -If the O-RU and O-DU are connected using IP (and UDP/IP is being used to transport the C/U plane), these transport connectivity verification checks operate at layer 3. Layer 3 connection verification is based on the O-RU supporting the UDP echo server functionality, as specified in RFC 862 [18]. The NETCONF client should enable the UDP echo server in the O-RU, triggering the O-RU to listen for UDP datagrams on the well-known port 7. When a datagram is received by the O-RU, the data from it is sent back towards the sender, where its receipt can be used to confirm UDP/IP connectivity between the transport endpoints. - -### 7.6.3.2 Managing IP connectivity monitoring procedure - -This clause describes the management of the UDP echo functionality. The NETCONF client uses the **enable-udp-echo** leaf in the udp-echo YANG model to control operation of the UDP echo server in the O-RU. The NETCONF client is able to control the DSCP marking used by the O-RU when it echoes back datagrams using the **dscp-config** leaf. Additionally, the NETCONF client can recover the number of UDP Echo messages sent by the O-RU by using **echo-replies-transmitted** operational state. - -An O-DU may have one or more IP interfaces that have to support the UDP/IP connectivity monitoring procedure. An O-RU with its UDP echo server enabled shall be able to respond to UDP datagrams originated from any valid source IP address. - -## 7.7 C/U-Plane delay management - -### 7.7.1 Introduction - -The Intra-PHY lower layer fronthaul split has the characteristic of a stringent bandwidth and tight latency requirement. The CUS-Plane specification [2] clause 4.4 describes how the propagation delay incurred due to distance between the O-DU and O-RU is an important parameter in defining the optimisation of windowing and receive-side buffering operations. This clause describes the procedures that are used to manage the delay parameters for the fronthaul split. - -### 7.7.2 Delay parameters - -The reference points for delay management are specified in the CUS-Plane Specification [2], clauses 4.4 and 4.7. Important delay parameters related to the operation of the O-RU are referred to as the O-RU delay profile. As the delay characteristics for an O-RU may vary based on air interface properties, a table of the parameters is provided based on a combination of sub-carrier spacing (SCS) and channel bandwidth. Other parameters related to delays to external antennas may vary according to specific tx/rx-array-carriers. These parameters are shown in Table 7.7.2-1. - -**Table 7.7.2-1: Mapping of delay profile parameters** - -| YANG parameter | Delay management parameters in CUS | -|----------------|------------------------------------| -| t2a-min-up | T2a_min_up | -| t2a-max-up | T2a_max_up | -| t2a-min-cp-dl | T2a_min_cp_dl | -| t2a-max-cp-dl | T2a_max_cp_dl | -| tcp-adv-dl | Tcp_adv_dl | -| t-da-offset | Tda | -| ta3-min | Ta3_min | -| ta3-max | Ta3_max | -| t2a-min-cp-ul | T2a_min_cp_ul | -| t2a-max-cp-ul | T2a_max_cp_ul | -| ta3-min-2g | Ta3_min_2g | -| ta3-max-2g | Ta3_max_2g | -| t-au-offset | Tau | -| ta3-min-ack | Ta3_min_ack | -| ta3-max-ack | Ta3_max_ack | - -If the O-RU supports multiple beamforming methods, some beamforming methods can have different delay parameters from others. In this case, the O-RU uses **non-default-ru-delay-profile** to report the additional sets of delay profile values based on a combination of SCS and bandwidth, the O-RU may only report the parameters that differ from **ru-delay-profile**. The delay parameter not reported in the **non-default-ru-delay-profile** uses the default value defined in **ru-delay-profile**. The **delay-profile-id** shall be used to identify additional sets of delay profiles supported by the O-RU in addition to the default delay profile. - -One delay profile may be common for multiple beamforming methods or may be specific to a beamforming method. Multiple BF methods used simultaneously can have the same set of delay profiles identified by the **delay-profile-id**. - -When requested, all O-RUs shall signal the table of statically "pre-defined" values of the above parameters, for different supported combinations of SCS and channel bandwidth over the management plane interface. This will typically occur during the initial start-up phase. - -### 7.7.3 Reception window monitoring - -The O-RU shall monitor operation of its reception window, monitoring the arrival of packets received over the fronthaul interface relative to the earliest and latest allowable times as defined by the values of t2a-max-up, t2a-max-cp-dl and t2a-min-up, t2a-min-cp-dl respectively. - -See clause B.3 for information on reception window counters. - -### 7.7.4 External antenna delay control - -An O-RU may optionally support the external antenna delay control by indicating that it supports the **EXT-ANT-DELAY-CONTROL** feature in its o-ran-wg4-features YANG model. Such an O-RU uses the **ext-ant-delay-capability** schema node in o-ran-module-cap YANG model to indicate to the O-RU Controller the type of external delay configuration supported by the O-RU: - -- PER-O-RU: The O-RU only supports a single value of t-da-offset and a single value of t-au-offset across all tx-array-carriers and rx-array-carriers respectively. - -- PER-ARRAY: The O-RU supports separate values of t-da-offset and t-au-offset across individual tx-arrays and rx-arrays respectively. -- PER-ARRAY-CARRIER: The O-RU supports separate values of t-da-offset and t-au-offset across separate tx-array-carriers and rx-array-carriers respectively. - -## 7.8 O-RU adaptive delay capability - -O-RUs may optionally support the ability to optimize their buffers based on information signalled concerning the configuration of the O-DU, e.g. including the O-DU delay profile, together with transport delay information, which may have been derived by the O-DU by using a delay measurement procedure operated by the O-DU or by other techniques. This clause describes such optional O-RU buffer optimisation functionality. - -The reference parameters are specified in the CUS-Plane Specification [2], clauses 4.4. An O-RU that supports the optional adaptive timing capability shall indicate such to the O-RU Controller client by exchanging NETCONF capabilities, as described in clause 9.2 and clause C indicating that it supports the ADAPTIVE-RU-PROFILE feature. An O-RU Controller may then provide the O-RU with the O-DU delay profile based on a combination of sub-carrier spacing (SCS) and channel bandwidth, as shown in Table 7.8-1. - -**Table 7.8-1: Mapping of O-DU delay profile parameters** - -| YANG parameter | Delay management parameters in CUS | -|----------------|------------------------------------| -| t1a-max-up | T1a_max_up | -| tx-max | TXmax O-DU | -| ta4-max | Ta4_max | -| rx-max | RXmax O-DU | -| t1a-max-cp-dl | T1a_max_cp_dl | - -In addition to the O-DU delay profile, the O-RU-Controller provides the O-RU with the transport network timing parameters, as shown in Table 7.8-2. - -**Table 7.8-2: Mapping of transport delay profile parameters** - -| YANG parameter | Delay management parameters in CUS | -|----------------|------------------------------------| -| t12-min | T12_min | -| t12-max | T12_max | -| t34-min | T34_min | -| t34-max | T34_max | - -As per [2] clause 4.7, the O-RU Controller shall configure values of **t12-max** and **t34-max** as if there is no external delay, i.e. $\tau = T_{da} = 0$ (zero). The O-RU may use this information to adapt its delay profile, ensuring that the inequalities defined in clause B of [2] are still valid - -The O-RU controller should provide this information during the O-RU's start-up procedure. If an O-RU receives the adaptive delay configuration information when operating a carrier, the O-RU shall not adapt its O-RU delay profile until all carriers operating using the O-RU buffers have been disabled. Once an O-RU has adapted its O-RU profile, it shall include the newly adapted timing values when signalling its delay parameters to a NETCONF client. - -## 7.9 Measuring transport delay parameters - -An O-RU may optionally indicate that it supports the eCPRI based measurement of transport delays between O-DU and O-RU. If O-RU supports measured transport delay, it shall implement the protocol as described in the CUS-Plane Specification [2] clause 4.4.4.4. - -An O-RU that supports the eCPRI based delay measurement capability, shall be able to support the operation of delay measurements whenever any processing element has been configured as described in clause 7.5. For each processing element configured, the O-RU shall be able to respond to any messages when received and keep a record of the number of responses, requests and follow-up messages transmitted by the O-RU. - -## 7.10 O-RU monitoring of C/U-Plane connectivity - -The O-RU should monitor the C/U plane connection and should raise an alarm if the logical C/U-plane connection associated with a processing-element fails. The O-RU uses a timer to monitor the C/U plane connection on a per processing-element basis. This timer is enabled only when at least one array-carrier using the processing-element is in the active state and is reset whenever it receives any C/U plane data flows associated with the particular processing-element. Because of the variety of PHY and C/U plane configurations, the O-RU cannot independently determine the minimum frequency of messages across the fronthaul interface. When an O-RU is monitoring the C/U plane, as a default, the O-RU uses a timer value of 160 milliseconds for monitoring the C/U plane connection. An O-RU may indicate that its C/U-plane monitoring timer is configurable, by the presence of the **cu-plane-monitoring** container in the o-ran-supervision.yang model. A NETCONF client can use the **configured-cu-monitoring-interval** leaf to configure the O-RU's timer value, including being able to disable the operation of C/U Plane monitoring. - -If the O-RU supports this timer, then depending on how long the O-DU takes to initiate sending of C/U plane data flows, it is advisable for the NETCONF client to initially disable the operation of the timer before carrier activation. Such an approach avoids the O-RU sending spurious alarm notifications triggered by O-DU delays in initializing the sending of C/U plane data that exceed the default timer value. Once C/U plane data flows have commenced, the NETCONF client can re-configure the timer with the desired value and hence activate monitoring of the C/U plane connectivity by the O-RU. - -## 7.11 Bandwidth management - -An O-RU can indicate the maximum bitrate able to be supported on those interfaces associated with a particular physical port using the optional **nominal-bitrate** leaf in the o-ran-transceiver YANG module. When the sustainable bitrate able to be supported by an O-RU is less than the combined bitrates of all its physical ports, an O-RU can use the optional **interface-grouping** container in the o-ran-interfaces YANG model to define the maximum sustainable rate able to be supported by an **interface-group-id** corresponding to a group of one or more physical interfaces. The same YANG model is used to augment the ietf-interfaces defined **interface** list with the **interface-group-id** to which the interface belongs. - -NOTE: The maximum sustainable bandwidth is calculated over one radio frame, meaning that the peak bandwidth can exceed the defined value over time periods shorter than one radio frame. - -## 7.12 IEEE 802.1X port based access control - -### 7.12.1 Configuring port based access control - -The O-RU shall support IEEE 802.1X port based access control supplicant functionality. - -- NOTE 1: IEEE 802.1X port based authentication is useful in those deployment scenarios where the O-RU is connected to a physically secure point-to-point Ethernet LAN used to transport the fronthaul traffic. -- NOTE 2: A previous version of the present document did not mandate IEEE 802.1X port-based network access control supplicant functionality in the O-RU. Operators that enable IEEE 802.1X authenticator PAE functionality in the fronthaul need to accommodate legacy O-RUs that do not support supplicant PAE functionality. -- NOTE 3: The present document does not define operation of an authenticator PAE in the O-RU. When operating an O-RU in shared cell configuration (i.e. in FHM or cascade mode), operators wanting to benefit from the port based access control supplicant functionality in an O-RU will need to rely on the transport network equipment to implement the authenticator PAE functionality. Clause 17.4 of O-RAN Xhaul Packet Switched Architectures and Solutions [73], requires each port connection from the transport network equipment towards the O-RU supports IEEE 802.1X authenticator functionality. - -O-RUs indicate they support IEEE 802.1X port based access control by including the `ieee802-dot1x` and `ietf-system` models in their YANG library. An O-RU Controller can use the **/sys:system/dot1x:pae-system/dot1x:system-access-control** parameter to enable or disable operation of IEEE 802.1X port based access control. Once configured, an O-RU shall store the `system-access-control` parameter in reset persistent memory. This means that, unless the O-RU has performed a factory reset procedure as described in clause 8.8, the O-RU shall always use the last configured value of `system-access-control` during its next start-up procedure. - -- NOTE 4: The leaf **sys:system/dot1x:pae-system/dot1x:system-access-control** in `ieee802-dot1x` YANG model does not have a default value and hence IEEE 802.1X operation will normally be disabled in factory software. An operator and vendor can agree that an O-RU uses a default value for this leaf in factory software. - -The configuration parameters and operational data related to IEEE 802.1X are defined in the **pae** container defined in the `ieee802-dot1x` YANG model defined augmentation of `ietf-interfaces` YANG model. An O-RU uses the `port-capabilities` container to indicate to an O-RU controller its PAE capabilities on a per-port basis. An O-RU indicates it supports a supplicant on a particular port by setting the `supp` leaf to true. When an O-RU indicates it supports a supplicant, an O-RU controller can use the `supplicant` container to configure authentication timers and re-try behaviour. The O-RU controller can use the **sys:system/dot1x:pae-system/o-ran-cert:credential** container to configure the trust anchor and the client certificate to be used by the supplicant PAE. The O-RU shall store this supplicant and credential configuration in reset persistent memory. - -When using a group destination address for transmitting or receiving EAP encapsulation over LAN (EAPOL) messages, an O-RU including the model **ieee802-dot1x-eapol** in its YANG library shall use the value configured for the PAE using the **eapol-group-address** leaf. In other cases, an O-RU shall use the IEEE Std 802.1X PAE Address, as specified in clause 11.1.1 of IEEE 802.1X [70]. - -## 7.12.2 EAP authentication - -The operation of a successful EAP authentication is described O-RAN Security Requirements Specifications [83], clause 3.2.5.5.3. An O-RU that supports IEEE 802.1X and which has its supplicant functionality enabled shall support EAP-TLS authentication. An O-RU that has a valid operator-signed certificate shall use the certificate in the EAP-TLS authentication. An O-RU that does not have a valid operator-signed certificate shall use its manufacturer installed certificate in the EAP-TLS authentication. - -All O-RUs that have a supplicant enabled shall set their `unauthAllowed` variable to `AuthFail`, as specified in IEEE 802.1X [70], clause 12.5.1. Accordingly, the O-RU's PAE controlled port state machine shall enable unauthenticated connectivity on a port with supplicant enabled only after the EAP authentication procedure has failed. - -NOTE: The PAE authenticator can decide to permit unauthenticated connectivity from an O-RU based on operator determined policy, e.g. based on matching the source Ethernet MAC address used by the Supplicant PAE against a register of O-RU MAC addresses. Such policies and their enforcement are outside the scope of the present document. - -### 7.12.3 Certificate time validation - -Operation of the EAP-TLS method requires the O-RU verify the certificate chain presented by the authenticator PAE, including confirming the certificate's validity periods. O-RUs using IEEE 802.1X port based access control shall be able to verify the certificate validity periods during the EAP-TLS exchange, e.g. by employing a persistent clock or using GNSS-based time synchronisation . - -If the O-RU cannot verify the certificates validity, e.g. because a persistent clock has failed, the EAP authentication procedure will fail. According to clause 7.12.2, this will result in the O-RU providing un-authenticated connectivity. If the O-RU uses a persistent clock for certificate validity checking and detects a persistent clock failure, it shall, as soon as possible, set its clock to the current time recovered from available external sources, e.g. PTP or GNSS. - -NOTE: The scenario corresponding to a failed clock source and resulting O-RU operation using un-authenticated connectivity, is identical to the O-RU operation prior to the introduction of IEEE 802.1X port based access control in version 10 of the present document. - -## 7.13 Media Access Control (MAC) security - -### 7.13.1 General - -Clause 7.13 describes requirements for those O-RUs that support MACsec. The support by an O-RU of MACsec is optional and hence clause 7.13 only applies to those O-RUs that support this optional capability. - -MACsec can be used in scenarios where the O-RU is not connected to a physically secure point-to-point Ethernet LAN. When configured, MACsec is used to secure the communications between the authenticated and authorised MAC Security Entity (SecY) associated with the O-RU's PAE and the SecY in the authenticator PAE. - -The present document places no restrictions on which element hosts the SecY associated with the authenticator PAE function which is a peer of the O-RU's supplicant PAE function. - -### 7.13.2 MACsec and MACsec key agreement - -An O-RU that supports MACsec shall implement MAC Security Entity requirements as specified in clause 5.3 of IEEE 802.1AE [85], MACsec Key Agreement (MKA) functionality for authentication and cryptographic key distribution as specified in clauses 5.10 and 5.11 of IEEE 802.1X [70] and the cipher suite GCM-AES-128, as specified in clause 14.4 of IEEE 802.1AE [85]. - -An O-RU shall indicate it supports MACsec and MKA on a particular interface **name** by setting the following schema nodes to true: - -- **/if:interfaces/if:interface/dot1x:pae/dot1x:port-capabilities/dot1x:macsec,** -- **/if:interfaces/if:interface/dot1x:pae/dot1x:port-capabilities/dot1x:mka** and -- **/if:interfaces/if:interface/dot1x:pae/dot1x:kay/dot1x:macsec/dot1x:capable.** - -When an O-RU Controller configures the value of **/if:interfaces/if:interface/dot1x:pae/dot1x:kay/dot1x:enable** to **True** on an interface, the O-RU shall enable the PAE Supplicant Key Agreement entitY (KaY) on the interface. The - -MACsec format used between the PAE Supplicant SecY and the peer PAE Authenticator SecY shall depend on whether the interface corresponds to the base-interface of an O-RU port, or a VLAN interfaces layered above a base-interface, as specified in clause 7.13.3. - -When the O-RU indicates multiple individual interfaces are MACsec **capable**, the O-RU shall support configuration and operation of multiple instances of the PAE Supplicant SecY on the individual interfaces. - -An O-RU that has a PAE Supplicant SecY configured on a VLAN interface which has secured communication with an authenticator PAE SecY shall be able to simultaneously support the configuration of a PAE Supplicant with IEEE 802.1X on the base-interface, as described in clause 7.12. - -NOTE: Clause 5.2.5.6 of the O-RAN Security Requirements Specifications [83] defines three different MACsec "encryption modes". "LAN mode MACsec" corresponds to configuring the KaY/SecY on an O-RU base interface and configuring an EAPOL group address corresponding to the Nearest non-TPMR Bridge group address, as defined in Table 11-1 of IEEE 802.1X [70]. "MACsec using EDE-CC" mode corresponds to configuring the KaY/SecY on an O-RU VLAN interface and configuring an EAPOL group address corresponding to the EDE-CC PEP Address, as defined in Table 11-1 of IEEE 802.1X [70]. The present document does not specify a solution for the third mode "WAN mode MACsec". - -### 7.13.3 MACsec frame format - -The O-RU shall use the MACsec Ethertype 88-E5 to distinguish secure frames from other insecure frames. When the PAE Supplicant with SecY is configured on an O-RU **base-interface**, the VLAN tag, including the priority field, shall be encapsulated within the secure data portion of the MACsec frame, as illustrated in Figure 7.13.3-1. - -![Diagram of Base interface MACsec Frame structure showing MAC Addresses (Destination Address, Source Address) and Frame-Data (SecTag, Secure Data, ICV) with VLAN and User-Data encapsulation.](572cf014db14c8234f91c07d5a5a28c6_img.jpg) - -The diagram illustrates the structure of a MACsec frame on a base interface. On the left, a box labeled **MAC Addresses** contains two sub-boxes: **Destination Address** and **Source Address**. On the right, a box labeled **Frame-Data** contains three sub-boxes: **SecTag**, **Secure Data**, and **ICV**. Above the **Frame-Data** box, there are three boxes: **MACsec EtherType**, **VLAN**, and **User\_Data**. Arrows indicate the flow of data: **MACsec EtherType** points to **SecTag**; **VLAN** points to **User-Data** (which is inside **Secure Data**); **User\_Data** also points to **User-Data** (inside **Secure Data**); and **Priority** points to **VLAN**. - -Diagram of Base interface MACsec Frame structure showing MAC Addresses (Destination Address, Source Address) and Frame-Data (SecTag, Secure Data, ICV) with VLAN and User-Data encapsulation. - -Figure 7.13.3-1: Base interface MACsec Frame, VLAN TAG and Priority Field. - -When the PAE Supplicant with SecY is configured on an O-RU VLAN interface, i.e. an interface **name** entry which includes a **vlan-id** leaf, the VLAN tag, including the priority field, shall be put in a cleartext VLAN header before the SecTag and shall also include the VLAN header in the secure data, as illustrated in Figure 7.13.3-2. - -![Diagram of a VLAN interface MACsec frame structure. It shows the relationship between MAC Addresses (Destination and Source), VLAN TAG (with Priority), User Data, and the resulting Frame-Data (containing VLAN Tag in clear, SecTag, Secure Data, and ICV).](38d82ffe820e339811b396206f40a201_img.jpg) - -The diagram illustrates the structure of a MACsec frame on a VLAN interface. On the left, a box labeled **MAC Addresses** contains two sub-boxes: **Destination Address** and **Source Address**. On the right, a box labeled **Frame-Data** contains four sub-boxes: **VLAN Tag (in clear)**, **SecTag**, **Secure Data**, and **ICV**. Above the frame, a **Priority** box points to a **VLAN TAG** box. The **VLAN TAG** box points to both the **VLAN Tag (in clear)** box in the frame and a **User Data** box. The **User Data** box points to a **User-Data** box, which in turn points to the **Secure Data** box in the frame. A **MACsec EtherType** box points to the **SecTag** box in the frame. - -Diagram of a VLAN interface MACsec frame structure. It shows the relationship between MAC Addresses (Destination and Source), VLAN TAG (with Priority), User Data, and the resulting Frame-Data (containing VLAN Tag in clear, SecTag, Secure Data, and ICV). - -Figure 7.13.3-2: VLAN interface MACsec Frame, VLAN TAG and Priority Field. - -### 7.13.4 Controlled and uncontrolled port - -The O-RU shall permit simultaneous access to secure MAC layer Internal Sublayer Services (ISS) using the controlled port of the SecY and insecure MAC ISS using the uncontrolled port, as illustrated in Figure 7.13.4-1. - -![Diagram showing simultaneous access to controlled and un-controlled ports. At the top, two yellow circles represent ports: 'Uncontrolled Port attached clients inc. PAE' on the left and 'Controlled Port attached clients' on the right. Red arrows point from each port to a box labeled 'LLC'. From the left 'LLC' box, a red arrow labeled '(Insecure ISS)' points down to a box labeled 'MACsec (SecY)'. From the right 'LLC' box, a red arrow labeled '(Secure ISS)' points down to the same 'MACsec (SecY)' box. From the 'MACsec (SecY)' box, a red arrow labeled '(ISS)' points down to a yellow circle labeled 'LAN MAC'.](8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg) - -Diagram showing simultaneous access to controlled and un-controlled ports. At the top, two yellow circles represent ports: 'Uncontrolled Port attached clients inc. PAE' on the left and 'Controlled Port attached clients' on the right. Red arrows point from each port to a box labeled 'LLC'. From the left 'LLC' box, a red arrow labeled '(Insecure ISS)' points down to a box labeled 'MACsec (SecY)'. From the right 'LLC' box, a red arrow labeled '(Secure ISS)' points down to the same 'MACsec (SecY)' box. From the 'MACsec (SecY)' box, a red arrow labeled '(ISS)' points down to a yellow circle labeled 'LAN MAC'. - -**Figure 7.13.4.-1: Simultaneous access to controlled and un-controlled ports.** - -The O-RU shall permit operation of other protocols and entities that make use of the service provided by the SecY's uncontrolled port to communicate independently of the operation of the MKA state machine. - -### 7.13.5 MACsec bypass policy - -An O-RU may indicate it supports MACsec bypass policies on its base-interface by including the MAC-BYPASS-POLICY in its yang library feature list. This clause applies to those O-RUs that include the feature in their YANG library. - -MACsec bypass policies on the base-interface are defined to allow matching Ethernet frames egressing the O-RU to bypass MACsec protection being applied at the base-interface, instead forwarding the matching frames using the uncontrolled port. Three different types of policies are defined: - -- 1) matching on destination MAC address, -- 2) matching on ethernet type, and -- 3) matching on vlan-id. - -O-RUs supporting MACsec bypass policy shall use the **macsec-bypass-capabilities** container to indicate the type(s) of MACsec bypass policy supported as well as the number of policy elements that can be configured by the O-RU controller. - -For O-RUs that support the **MACSEC-BYPASS-POLICY** feature, an O-RU controller can use the o-ran-interfaces YANG model to configure a base-interface on which it has enabled a SecY with a **macsec-bypass-policy** container. This container allows an O-RU controller to configure the policies to apply to egress packets from the base-interface. - -When an O-RU controller enables a SecY on a base-interface and does not configure a corresponding **macsec-bypass-policy**, all traffic egressing the base-interface shall be protected by MACsec. - -NOTE 1: The **MACSEC-BYPASS-POLICY** feature applies when the SecY is operating at the base-interface. Configuring SecY to operate at the VLAN-ID level automatically establishes MACsec bypass policies based on vlan-id. - -NOTE 2: The **MACSEC-BYPASS-POLICY** feature allows an O-RU controller to configure bypass policies for the PTP Message Ethernet Type (88F7). In such a scenario, an O-RU configured with a physical port with **time-transmitter-only = True** that corresponds to a MACsec enabled base-interface, will use the un-controlled port for all PTP frames egressing the O-RU. - ---- - -## 8 Software management - -### 8.1 General - -#### 8.1.1 Introduction - -The Software Management function provides a set of operations allowing the desired software package or build to be downloaded, files to be installed and slot containing installed software to be activated at O-RU. - -There are two types of software management processing. Some O-RUs expect a software package (in form of a zip file) to be downloaded to O-RU, while other O-RUs expect individual files in a build to be downloaded. - -The O-RUs that do not support download of an archived package and require downloading of individual files in a build can be distinguished by the existence of data node **build-content-download**. For such O-RU, the O-RU controller shall provide remote-file-path of file in the desired build as input for **software-download** RPC. Refer to clause 8.5 for details. - -If the **build-content-download** is not exposed by an O-RU, the O-RU controller shall provide remote-file-path of the software package zip file as input for **software-download** RPC. - -Successful software activation operation does not mean an O-RU is running the just activated software build. An O-RU **reset** RPC is required to trigger the O-RU to take the activated software build into operational use. - -The software management functions involve the O-RU controller subscribing to receive particular YANG notifications from the O-RU. All O-RUs support the NETCONF Create-Subscription method, enabling those notifications to be transported using NETCONF notifications. In addition, those O-RUs that support the optional NON-PERSISTENT-MPLANE feature, the O-RU Controller can create a configured subscription from the O-RU, enabling those notifications to be transported over HTTPS to an Event-Collector as described in clause 18. - -It is also Vendor's responsibility to handle SW Build / package / file integrity check. The O-RU controller shall be able to obtain information contained in the manifest.xml. - -#### 8.1.2 Software slots - -The O-RU provides a set of so called "software slots" or "slots". Each slot provides an independent storage location for a single software build. The number of slots offered by O-RU depends on the device's capabilities. At least two writable slots shall be available at the O-RU for failsafe update operation. If the read-only slot is supported by an O-RU, the software that is present in the read only slot is termed factory default software and can be used in factory reset procedure. Refer to clause 8.9 for detailed information. Presence of read only slot is optional. The software slots are resources - -provided by the O-RU and as such are not the subject of creation and deletion. The size of individual software slots is fixed and determined by the O-RU's vendor and sufficient to accommodate the full software build. - -### 8.1.3 Software management procedures - -Software management procedures are described in clause 8.4, clause 8.5 and clause 8.6. Procedures used in Software Management are covered by o-ran-software-management.yang module. - -## 8.2 Software build - -A single software build is considered as set of internally consistent files compliant within such a build. Replacement of files within a build is prohibited, as this will cause software version incompatibility. Software build is a subject of versioning and maintenance and as such cannot be broken. Whether a file is included in a build is defined in manifest.xml. The manifest.xml enables mapping from radio product type to files. Revision and name of the build in each slot is provided as result by the inventory procedure to ensure visibility of radio software installation status. - -The use of compression and ciphering for the content of the software build is left to vendor implementation. - -## 8.3 Software package - -### 8.3.1 Software package name - -The name of a software package shall conform to the following format: - -"[#NUMBER].EXT" - -Where: - -- *Vendor Code* is a mandatory part which either has two capital characters or 1-5 digits. The vendor code prefix in the software package file name is used to avoid conflict between file names of SW packages provided by different vendors, -- *Vendor Specific Field* is any set of characters allowed in filename. The value shall not include character "\_" (underscore) or "#" (hash). The value can be defined per vendor for the human readable information. Version information is necessary in the *Vendor Specific Field* which defines load version, -- *NUMBER* is optional and used when the software package is split into multiple files, e.g. when a zipped file is split into multi-part zip file - number after "#" indicates the part number of a split file. Numbering starts from 1 and shall be continuous, -- *EXT* is a mandatory part which defines the extension of filename. A vendor provides one or more software packages. - -Each software package shall be compressed by zip. in the file name shall be ".zip". The O-RUs that do not expose **build-content-download** shall support ZIP functionality. For O-RUs that expose **build-content-download**, support of ZIP functionality is implementation dependent. - -### 8.3.2 File server storage of software package - -The operator needs to manage and control which O-RU files will be stored and used in the file server. The software package can be stored on the file server as one or more archived file(s) or as multiple files that are extracted from a - -software package zip file. The O-RU controller triggers the O-RU to download software file from a file server and should ensure that all the files necessary for the O-RU are transferred from the file server to the O-RU. - -### 8.3.3 Software package content and manifest.xml file - -Each software package includes: - -- manifest.xml -- software files - -NOTE: Those software files are intended to be installed on software slot. Those software files are intended to be used for one or several O-RU products. - -An example of archive structure for the software files is: - -``` -../o-ru-sw/version1.0/xxxx -../o-ru-sw/version1.0/yyyy -../o-ru-sw/version2.0/yyyy -../o-ru-sw/version1.5/zzzz -``` - -The content of the manifest.xml file allows to maintain software update process correctly in terms of compatibility between O-RU hardware and software files to be downloaded. The content of the manifest.xml file enables the O-RU controller to trigger the installation of files of a software build designed for device based on different product code. The manifest.xml file is contained in a software package and shall not be ciphered. The format of the manifest.xml file is illustrated below using example data: - -``` - - - /// @version describes version of file format (not the content) - - - - - - - - - - /// @vendor is as reported by O-RU - - /// @code is a regular expression that is checked against productCode reported by O-RU - - /// @name is optional and used for human reading - SHALL NOT be used for other purposes! - - /// @buildId is value of build@id (see below) - - - - - - - - /// @id is index of available builds and corresponds to attribute build-Id in the tag - "product". - - /// @bldName and @bldVersion are used in YANG (build-name, build-version) -``` - -``` - - - - - - /// @fileName and @fileVersion are used in YANG (name, version) - - /// @fileVersion may be used as a handle to identify a specific path used when archiving -different file versions - - /// @path is full path (with name and extension) of a physical file, relative to package -root folder, used in YANG (local-path) - - /// @checksum is used to check file integrity on O-RU side - - - - - - - - - - - - - - - - - - - -``` - -Keywords in manifest.xml example are in **bold**, the keywords shall be strictly followed. - -Correspondence between content of manifest.xml tags, their attributes and content of o-ran-software-management.yang is: - -- XML tag "product", attribute "vendor" corresponds to content leaf "vendor-code", -- XML tag "product", attribute "code" corresponds to content of leaf "product-code", -- XML tag "product", attribute "build-Id" corresponds to content of leaf "build-id", -- XML tag "build", attribute "id" corresponds to leaf "build-id", -- XML tag "build", attribute "bldName" corresponds to content of leaf "build-name", -- XML tag "build", attribute "bldVersion" corresponds to content of leaf "build-version", -- XML tag "file", attribute "fileName" corresponds to content of leaf "name" in list "files", -- XML tag "file", attribute "fileVersion" corresponds to content of leaf "version" in list "files". - -## 8.4 Software inventory - -### Pre-condition: - -- M-Plane NETCONF session established. - -**Post-condition:** - -- NETCONF client successfully collected the software inventory information from NETCONF server. - -![Sequence diagram showing the inventory fetch call flow between a NETCONF Server (O-RU) and a NETCONF Client (O-RU Controller).](e60c2d24a97a2855d98671d27ea43d0f_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client/ (O-RU Controller) - participant Server as NETCONF Server/ (O-RU) - Note right of Client: NETCONF session established. - Note right of Client: Inventory Request - Client->>Server: [1] .. - Note right of Server: Inventory Response - Server->>Client: [2] ... - -``` - -The diagram illustrates the interaction for fetching software inventory. It starts with a note indicating the NETCONF session is established. The Client sends an 'Inventory Request' containing an RPC with a 'get' operation filtered by the 'software-slot' container. The Server responds with an 'Inventory Response' containing an 'rpc-reply' with 'data' that includes the 'software-slot' information. - -Sequence diagram showing the inventory fetch call flow between a NETCONF Server (O-RU) and a NETCONF Client (O-RU Controller). - -**Figure 8.4-1: Inventory fetch call flow** - -Figure 8.4-1 illustrates the operation where Software Inventory is fetched by a NETCONF Client using the NETCONF **get** RPC filtered over the **software-slot** container. The response contains information about each software slot and its contents. - -The following information is provided by software-inventory reply message: - -- name** - name of the software slot (the name is defined by the O-RU vendor) -- status** - status of the software slot. Status of the software in the slot can be - - **VALID** - Slot contains a software build considered as proven valid. - - **INVALID** - software build in the software slot cannot be used by O-RU. The software is considered by the O-RU as damaged (e.g. wrong CRC). Failed software install operation can cause a slot status to change to "Invalid". - - NETCONF client shall not activate a software slot that is invalid. Activation of a software slot containing an invalid software build shall be rejected by O-RU. - - **EMPTY** - software slot does not contain any software files. NETCONF client shall not activate an empty software slot. Activation of an empty software slot shall be rejected by O-RU. -- active** - indicates if the software stored in particular slot is activated at the moment. - -- **True** - software slot is activated. Active::True can be assigned only for slots with status "Valid". At any time, only one slot in the O-RU shall be marked as active::True. The O-RU shall reject activation for software slots with status "Empty" and "Invalid". - - **False** - software slot is not active. -- d) **running** - informs if software stored in particular slot is used at the moment. -- **True** - software slot contains the software build used by the O-RU in its current run. - - **False** - software slot does not contain the software build used by O-RU at the moment. -- e) **access** – informs about access rights for the current slot. -- **READ\_ONLY** – The slot is intended only for factory software. Activation of such software slot means performing a factory reset operation and a return to factory defaults settings. - - **READ\_WRITE** – slot used for updating software. -- f) **product-code** - product code provided by the vendor, specific to the product. -- g) **vendor-code** - unique code of the vendor. -- h) **build-id** - Identity associated with the software build. This id is used to find the appropriate build-version for the product consist of the vendor-code and the product-code. -- i) **build-name** - Name of the software build. -- j) **build-version** - Version of the software build for the product consist of the vendor-code and the product-code. -- k) **files** - list of files in the software slot -- **name** - name of one particular file - - **version** - version of the file - - **local-path** - complete path of the file on local file system - - **integrity** - result of the file integrity check - - **OK** - file integrity is correct - - **NOK** - file is corrupted - -If a slot contains a file with integrity::NOK, the O-RU shall mark the slot with status::INVALID. The content of a software-slot is fully under O-RU's management - including removal of the content occupying the slot (in case the slot is subject of software update procedure), control of file system consistency and so on. The slot content shall not be removed until there is a need for new software to be installed. - -The empty slot parameters shall be as follows: - -**name:** up to vendor, not empty - -**status:** "EMPTY" - -**active:** False - -**running:** False - -**access:** READ\_WRITE - -**product-code:** up to vendor - -**vendor code:** up to vendor - -**build-name:** null (empty string) - -**build-version:** null (empty string) - -**files:** empty list - -## 8.5 Download - -### Pre-condition: - -- M-Plane NETCONF session established. -- O-RU Controller has subscribed to receive **download-event** notifications. -- O-RU controller has validated presence of data node **build-content-download** at O-RU. - -### Post-condition: - -- O-RU has downloaded the file specified and has successfully stored the downloaded file in the O-RU's file system. - -![Sequence diagram showing the software download call flow between a NETCONF Server/Notification Producer (O-RU) and a NETCONF Client/Notification Subscriber (O-RU Controller).](140bd031d724324269168296afd1e04d_img.jpg) - -``` - -sequenceDiagram - participant O-RU as NETCONF Server/ -Notification Producer/ -(O-RU) - participant O-RU-Controller as NETCONF Client/ -Notification Subscriber/ -(O-RU Controller) - - Note right of O-RU-Controller: NETCONF session established and -subscription to receive notifications. -Presence/absence of build-content-download -data node is known. - - O-RU-Controller->>O-RU: [1] - - -.. - - - Note left of O-RU: O-RU replies with proper status -about operation requested - O-RU-->>O-RU-Controller: [2] - -.. - - - Note right of O-RU-Controller: Waits for the notification from O-RU -about the completion of the download - Note left of O-RU: File download completed - O-RU->>O-RU-Controller: [3] - -... - - - -``` - -Sequence diagram showing the software download call flow between a NETCONF Server/Notification Producer (O-RU) and a NETCONF Client/Notification Subscriber (O-RU Controller). - -**Figure 8.5-1: Software download call flow** - -Figure 8.5-1 illustrates the software download call flow. The following types of authentications shall be supported for **software-download**: - -- a) password for RU authentication and list of public keys (see clause 5.4 in the present document) for sFTP server authentication. - -Following types of authentications may be supported for **software-download**: - -- b) X.509 certificate for authentication of FTPES client (O-RU) and FTPES server. - -- c) certificate for both O-RU and sFTP server authentication. - -The **software-download** RPC is used to trigger the downloading of software files to the O-RU. The download shall be performed using either sFTP or FTPES. Based on presence of data node **build-content-download**, O-RU controller shall provide either path to a file in a build or path to a software package file as input to **software-download** RPC. The RPC shall specify the URI of the remote location of the software files using the remote-file-path leaf, where the URI scheme is used to signal whether to use sFTP or FTPES. An O-RU Controller shall only trigger software-download using FTPES if it is using NETCONF/TLS to configure the O-RU. - -The O-RU shall send an immediate rpc-reply message with one of following statuses: - -- a) STARTED – software download operation has been started. -- b) FAILED – software download operation could not be proceeded, reason for failure in error-message. - -The O-RU shall download the file from file server. When the O-RU completes the software download or software download fails, the O-RU shall send the **download-event** notification with one of the following statuses: - -- a) COMPLETED. -- b) AUTHENTICATION\_ERROR - source available, wrong credentials. -- c) PROTOCOL\_ERROR – sFTP or FTPES protocol error. -- d) FILE\_NOT\_FOUND - source not available. -- e) APPLICATION\_ERROR - operation failed due to internal reason. -- f) TIMEOUT - source available, credentials OK, Operation timed out (e.g. source becomes unavailable during ongoing operation). -- g) INTEGRITY\_ERROR – file is corrupted. - -An O-RU that supports integrity check at download shall expose YANG feature **cINTEGRITY-CHECK-AT-SW-DOWNLOAD**". O-DU can enable the feature by configuring type empty parameter **integrity-check-at-download-enabled**. O-RU may send download-event with status **INTEGRITY\_ERROR** when **integrity-check-at-download-enabled** is presented. - -NOTE: O-RU can obtain information of expected checksum either from manifest.xml or from information embedded in the file. - -O-RU controller shall repeat the above procedure until all files which are required by the O-RU have been downloaded to the O-RU. To determine all files needed by O-RU, the O-RU Controller uses content of manifest.xml and relies on presence of data node **build-content-download**. - -## 8.6 Install - -### Pre-condition: - -- M-Plane NETCONF session established. -- At least one software slot with status **active::False** and **running::False** exists in O-RU. -- Software Download has been completed successfully and all files required by the O-RU are available in O-RU. -- O-RU Controller has subscribed to receive **install-event** notifications. - -### Post-condition: - -- O-RU software file(s) is/are installed in the specified target **software-slot**. - -![Sequence diagram showing the software install call flow between a NETCONF Server/Notification Producer (O-RU) and a NETCONF Client/Notification Subscriber (O-RU Controller).](fc3e2b49a9f850951570e502393b697f_img.jpg) - -``` - -sequenceDiagram - participant O-RU as NETCONF Server/ -Notification Producer/ -(O-RU) - participant O-RU-Controller as NETCONF Client/ -Notification Subscriber/ -(O-RU Controller) - - Note right of O-RU-Controller: NETCONF session established and -subscription to receive notifications. - O-RU-Controller->>O-RU: - - [1] .. - - - Note left of O-RU: O-RU replies with proper status -about operation requested - O-RU-->>O-RU-Controller: - - [2] .. - - - Note right of O-RU-Controller: Waits for the notification from O-RU -about the completion of the software-install - Note left of O-RU: O-RU Completes software-install operation - O-RU-->>O-RU-Controller: - - [3] ... - - - -``` - -Sequence diagram showing the software install call flow between a NETCONF Server/Notification Producer (O-RU) and a NETCONF Client/Notification Subscriber (O-RU Controller). - -**Figure 8.6-1: Software install call flow** - -Figure 8.6-1 illustrates the operation where the NETCONF **software-install** RPC is used to install the previously downloaded software (i.e. all necessary) to the specified target **software-slot** on O-RU. - -The list of file-names in install-input shall not be empty. This slot shall have status active::False and running::False. - -The O-RU shall send an immediate rpc-reply message with one of following statuses: - -- STARTED - software install operation has been started. -- FAILED - software install operation could not be proceeded, reason for failure in error-message. - -When O-RU completes the software install or software install procedure fails, the O-RU shall send the **install-event** notification with one of the following statuses: - -- a) COMPLETED - Install procedure is successfully completed. -- b) FILE\_ERROR - operation on the file resulted in in error, disk failure, not enough disk space, incompatible file format -- c) INTEGRITY\_ERROR - file is corrupted. -- d) APPLICATION\_ERROR - operation failed due to internal reason. -- e) TIMEOUT - install operation timed out. - -When the software install commences, the O-RU shall set the slot status to INVALID. After the install procedure finishes, the O-RU shall change the slot status to its appropriate status. O-RU shall not change the status of the slot when the install procedure is ongoing or when it is interrupted (e.g. by spurious reset operation). - -## 8.7 Bringing software into operation - -### 8.7.1 Procedure - -Two steps are required to bring O-RU software into operation. The first step uses RPC **software-activate** to activate software in a slot. The second step, which may be delayed as per operator's decision until a suitable time, uses a **reset** RPC to take the activated software into operation. The information about which slot is active shall be reset persistent. - -NOTE: In certain circumstances, for example when performing a vendor defined O-RU recovery mechanism, the O-RU can start up using other software than the software in active slot before reset (e.g. factory default software). - -### 8.7.2 Software activation - -#### Pre-condition: - -- M-Plane NETCONF session established. -- Software slot to be activated has status VALID. -- O-RU Controller has subscribed to receive **activation-event** notifications. - -#### Post-condition: - -- For activated slot the parameter **active** is set to TRUE. At the same time the parameter **active** for previously operational slot is set to FALSE by the O-RU. Parameter running is not changed for any of O-RU's software slots. This indicates that O-RU is still running software from previously active slot. - -![Sequence diagram showing the software activation call flow between a NETCONF Server/Notification Producer (O-RU) and a NETCONF Client/Notification Subscriber (O-RU Controller). The flow includes session establishment, an RPC request for software activation, an immediate RPC reply, a wait for a notification, completion of the activation process, and finally a notification with the activation status.](6d697ce8828ba75fddee0a1b7767a7ca_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client/Notification Subscriber/(O-RU Controller) - participant Server as NETCONF Server/Notification Producer/(O-RU) - Note right of Client: NETCONF session established and subscription to receive notifications. - Client->>Server: [1] .. - Note left of Server: O-RU replies with proper status about activate operation requested as whether started or failed. - Server->>Client: [2] .. - Note right of Client: Waits for the notification from O-RU about the completion of the activate - Note left of Server: O-RU Completes Activation process. - Server->>Client: [3] ... - -``` - -Sequence diagram showing the software activation call flow between a NETCONF Server/Notification Producer (O-RU) and a NETCONF Client/Notification Subscriber (O-RU Controller). The flow includes session establishment, an RPC request for software activation, an immediate RPC reply, a wait for a notification, completion of the activation process, and finally a notification with the activation status. - -**Figure 8.7.2-1: Software activation call flow.** - -Figure 8.7.2-1 illustrates the operations where the NETCONF **software-activate** RPC is used to activate the software. The name of the software-slot is specified in the activate request. - -The O-RU shall send an immediate rpc-reply message with one of following statuses: - -- a) STARTED - software activation operation has been started. -- b) FAILED - software activation operation could not be proceeded, reason for failure in error-message. - -When the activation is completed, the O-RU shall send the **activation-event** notification with the status of activation. The following status is returned in the **activation-event** notifications. - -- a) COMPLETED - Activation procedure is successfully completed. O-RU can be restarted via NETCONF **reset** rpc for the new software to be activated. -- b) APPLICATION\_ERROR - operation failed due to internal reason. - -Only one software slot can be active at any time. Thus, successful software-activate command sets **active** to true for the slot that was provided in the RPC and O-RU sets **active** to false for the previously active slot. - -### 8.7.3 Reset - -A O-RU reset is required to take the activated software into operation. See clause 9.5 for details of how an O-RU controller can trigger reset operation. - -## 8.8 Software update scenario - -An example scenario of a successful software update procedure can be as follows. - -The present document does not distinguish between a software upgrade and a downgrade. - -- 1) NETCONF client performs a software inventory operation and identifies that an inactive and not-running slot for installing software is available so that it can download and install a software package. -- 2) NETCONF client validates whether the O-RU has data node **build-content-download**. -- 3) In case the O-RU does not expose **build-content-download**, NETCONF client, knowing target SW version, O-RU product type and manifest.xml content, determines the software package zip file(s) to be downloaded. -- 4) In case the O-RU exposes data node **build-content-download**, NETCONF client, knowing target SW version, O-RU product type and manifest.xml content, determines the desired build name, build version and software files in the build to be downloaded. -- 5) NETCONF client using the **software-download** RPC triggers the O-RU to download a file (if several files are required, steps 5-7 need to be performed repeatedly until all files needed by O-RU have been downloaded). -- 6) O-RU sends RPC response that download was started. -- 7) O-RU finishes downloading the file(s) and reports this by sending the **download-event** notification. -- 8) NETCONF client requests installation of the software using **software-install** RPC, and provides the slot name where the software needs to be installed along with a list of filenames to be installed. - -NOTE: list of files to be installed cannot be empty. - -- 9) O-RU sends RPC response that installation was started -- 10) O-RU sets installation slot status to INVALID. -- 11) O-RU installs the software and after successful installation (with checksum control) changes status of the slot to VALID. -- 12) O-RU notifies the notification subscriber that the installation is finished using **install-event** notification. -- 13) NETCONF client requests the O-RU to activate the slot that contains the newly installed software using the **software-activate** rpc. -- 14) O-RU sends RPC response that activation was started. - -- 15) For requested slot, O-RU changes **active** to true and at the same time sets **active** to false for previously active slot. -- 16) O-RU notifies the notification subscriber about activation finished using the **activation-event** notification. -- 17) NETCONF client restarts the O-RU forcing it to use the newly installed and activated software. Refer to clause 9.5 O-RU reset for detailed information. - -## 8.9 Factory reset - -An O-RU that support a read only slot can perform this procedure. O-RU can be reset to the factory default software by activating the software-slot containing the factory default software and initiating NETCONF **reset** RPC. O-RU may clear persistent memory data during factory reset as vendor implementation option. Factory default software may have limited functionality and O-RU that runs on factory default SW will typically require a software update before it can be fully functional (for example carry traffic). Factory default software shall support all functionality needed to perform a software update. - -## 9 Configuration management - -### 9.1 Baseline configuration - -#### 9.1.1 NETCONF operations - -The O-RU shall use the ietf-yang-library mode, as specified in RFC 8525 [59] to signal the namespaces of the YANG models supported by the NETCONF Server. When the O-RU signals it supports the YANG module for NETCONF Monitoring, as specified in RFC 6022 [67], an O-RU Controller shall be able to retrieve the models from the O-RU using the operation. - -Clause 9 describes NETCONF standard operation (edit-config/get-config/get) as specified in clause 7 of RFC 6241 [3] which belongs to the CM in Module to modify/retrieve any parameters in YANG modules. Examples below use o-ran-hardware as an example YANG module. - -The following scenarios are feasible for Configuration Management purposes: - -- 1) 1 phase (modify) operation using writable running datastore. -- 2) 2 phase (modify/commit) operation using candidate datastore. -- 3) 3 phase (modify/commit/confirm) operation using candidate datastore. - -As described in clause 6.6, the NETCONF client can use sub-tree based and XPath based to recover particular sub-trees from the O-RU. When using XPath filtering, the O-RU returns a node-set which matches the criteria expressed in the XPath. An example of a get operation with XPath based filtering is shown in Figure 9.1.1-1. - -``` - - - - - - - -``` - -``` - - - - - -
- -
- -``` - -**Figure 9.1.1-1: Example of filtering based on XPath** - -## 9.1.2 Retrieve state - -O-RU Controller is able to retrieve state which is defined in o-ran-hardware by using NETCONF procedure, as illustrated in Figure 9.1.2-1. - -![Sequence diagram illustrating the Retrieve Resource State process. A NETCONF Client (O-RU Controller) sends a request to a NETCONF Server (O-RU). The O-RU responds with the state of the specified leaf node. The sequence is: [1] , [2] .](7c1ccebd0e8661557a8ffc00cfae58a0_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client/ (O-RU Controller) - participant Server as NETCONF Server/ (O-RU) - Note right of Server: O-RU responds with the state of specified leaf to NETCONF Client. - Client->>Server: [1] - Server-->>Client: [2] - -``` - -Sequence diagram illustrating the Retrieve Resource State process. A NETCONF Client (O-RU Controller) sends a request to a NETCONF Server (O-RU). The O-RU responds with the state of the specified leaf node. The sequence is: [1] , [2] . - -**Figure 9.1.2-1: Retrieve Resource State** - -### Preconditions: - -- O-RU Controller has completed exchange of NETCONF capabilities as part of connection establishment between O-RU and O-RU Controllers. - -### Post conditions: - -- O-RU controller has retrieved O-RU state as per request. - -## 9.1.3 Modify state - -For O-RUs that support the optional hardware-state feature defined in ietf-hardware, the O-RU Controller is able to change state which can be configurable by using NETCONF procedure without reset, as illustrated in Figure 9.1.3-1. - -The configurable state is admin-state defined in o-ran-hardware YANG model. In case of a failure, an error shall be returned. Refer to RFC 6241 [3] Appendix A for error codes. The vendor can define the behaviour after the error occurred. - -The power-state is read-only state defined in o-ran-hardware.yang. This state is only exposed by the O-RUs supporting ENERGYSAVING feature and is used by O-RU to inform if unit is in energy saving state, not in energy saving state or in transition between energy saving state and non-energy saving state. - -![Sequence diagram for Figure 9.1.3-1: Modify Resource State without reset. It shows a NETCONF Client (O-RU Controller) sending an edit-config RPC to a NETCONF Server (O-RU). A note indicates that if object states are changed, the O-RU updates its state. An 'alt' block titled 'Success case' shows an OK response, while a 'Failure case' shows an error response.](ba676d18b6a00f27c5bfaec9eeec20be_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client/ (O-RU Controller) - participant Server as NETCONF Server/ (O-RU) - Note left of Server: If the state of objects are changed from O-RU Controller, the O-RU change the new state. - Client->>Server: [1] <...> - alt Success case - Server-->>Client: [2] - else Failure case - Server-->>Client: [3] - end - -``` - -Sequence diagram for Figure 9.1.3-1: Modify Resource State without reset. It shows a NETCONF Client (O-RU Controller) sending an edit-config RPC to a NETCONF Server (O-RU). A note indicates that if object states are changed, the O-RU updates its state. An 'alt' block titled 'Success case' shows an OK response, while a 'Failure case' shows an error response. - -Figure 9.1.3-1: Modify Resource State without reset - -The followings are the information of state transition for each state. - -**[admin-state]** - -The admin-state transition diagram for the O-RU is illustrated in Figure 9.1.3-2. - -![State transition diagram for Figure 9.1.3-2: Admin State. It shows three states: unlocked, shutting-down, and locked. Transitions from unlocked to shutting-down and from shutting-down to locked are triggered by 'edit-config'. An autonomous trigger transition exists from shutting-down to locked.](86e1f8551d4922ea8fa197f96fe4098b_img.jpg) - -``` - -stateDiagram-v2 - [*] --> unlocked - unlocked --> shutting-down : edit-config - shutting-down --> locked : autonomous trigger - shutting-down --> locked : edit-config - -``` - -State transition diagram for Figure 9.1.3-2: Admin State. It shows three states: unlocked, shutting-down, and locked. Transitions from unlocked to shutting-down and from shutting-down to locked are triggered by 'edit-config'. An autonomous trigger transition exists from shutting-down to locked. - -Figure 9.1.3-2: Admin State - -- locked: This state indicates that any resource activation is prohibited for the O-RU and all resources have been deactivated administratively. The O-RU shall ensure all RF emissions have been shut down. When O-RU's admin state is locked, all its tx-array-carriers and rx-array-carriers parameter **active** are set by NETCONF server autonomously to "INACTIVE" and **state** are "DISABLED". When O-RU's administrative-state is LOCKED, O-RU shall reject NETCONF client's request to set tx-array-carrier and rx-array-carrier parameter active to "ACTIVE". Antenna lines and ALD ports on the O-RU are powered off. O-RU shall reject NETCONF configuration to power on the ALD port and antenna lines. -- shutting-down: That usage is administratively limited to current instances of use. It is optional. For admin state transition using autonomous trigger from shutting-down to state locked, refer to X.731 [77] Figures 5 and 6. - -- unlocked: This state indicates that any resource activation is allowed and any resources can be active. The state "unlocked" is the initial state after the reset of the O-RU. - -**[power-state]** - -The power-state transition diagram for O-RU is presented in Figure 9.1.3-3. This state can be indirectly controlled by editing the parameters **energy-saving-enabled** and **[tr]x-array-carrier::active**, as illustrated in Figure 9.1.3-3. - -![Transition diagram for power-state node showing UNKNOWN, AWAKE, and SLEEPING states with transitions between them.](1187dbd674a100960ed23efa54ccd6c1_img.jpg) - -``` - -stateDiagram-v2 - [*] --> UNKNOWN - UNKNOWN --> AWAKE : edit-config (energy-saving-enabled; [tr]x-array-carrier::active) - UNKNOWN --> SLEEPING : edit-config (energy-saving-enabled; [tr]x-array-carrier::active) - AWAKE --> SLEEPING : edit-config (energy-saving-enabled; [tr]x-array-carrier::active) - -``` - -Transition diagram for power-state node showing UNKNOWN, AWAKE, and SLEEPING states with transitions between them. - -**Figure 9.1.3-3: Transition diagram for power-state node** - -**Figure 9.1.3-4: Void** - -- AWAKE: This value of power-state node indicates that the O-RU is operating normally, i.e. not in energy saving mode. AWAKE is the initial value of power-state node after the reset of the O-RU. AWAKE is power-state of O-RU in case energy-saving-enabled is FALSE or when at least one carrier is active. -- SLEEPING: This value of power-state node indicates that the O-RU is in energy saving mode. M-plane connection and functions are alive whereas other C/U/S functions may be autonomously stopped by the O-RU if there is no active carrier and value of energy-saving-enabled is TRUE - to reduce energy consumption. -- UNKNOWN: This value of power-state node can be exposed by the O-RU e.g. in case the O-RU does not know its power-state value is AWAKE or SLEEPING. This value of power-state node is optional. - -When the value of any of the following states changes, an O-RU supporting feature hardware-state shall send the hardware-state-change notification to the notification subscriber: - -- admin-state, oper-state, usage-state (as specified in ietf-hardware.yang) -- power-state, availability-state (as specified in o-ran-hardware.yang) - -In case of 'oper-state' change, if the O-RU supports the feature **hardware-state**, the O-RU shall send two notifications to the notification subscriber(s): the **hardware-state-change** notification and the **hardware-state-oper-disabled/enabled** notification. - -On receiving the notification, the notification subscriber should read the state by using get RPC operation. - -**[oper-state]** - -O-RU's oper-state is not configurable. It reflects whether the O-RU can provide service or not. - -The oper-state transition diagram for O-RU is presented in Figure 9.1.3-5. - -![O-RU Oper State transition diagram showing 'disabled' and 'enabled' states with transitions 'enable', 'rpc reset', and 'disable'.](59e29b37c5e332b0be088cde8c4d217e_img.jpg) - -``` - -stateDiagram-v2 - [*] --> disabled - disabled --> enabled : enable - enabled --> disabled : disable - enabled --> disabled : rpc reset - -``` - -O-RU Oper State transition diagram showing 'disabled' and 'enabled' states with transitions 'enable', 'rpc reset', and 'disable'. - -Figure 9.1.3-5: Oper State - -enabled: O-RU is partially or fully operational. - -disabled: O-RU is not operational. This is the initial state of oper-state after the reset of the O-RU - -- O-RU Controller is able to reset the O-RU, even if the O-RU state is "disabled" or "enabled". - -**[availability-state]** - -The availability-state transition diagram for the O-RU is presented in Figure 9.1.3-6. - -![O-RU availability State transition diagram showing 'normal', 'degraded', and 'faulty' states with transitions between them.](19499072f755b22d0a231123f75fa477_img.jpg) - -``` - -stateDiagram-v2 - [*] --> normal - normal --> degraded - degraded --> normal - degraded --> faulty - faulty --> degraded - faulty --> normal - -``` - -O-RU availability State transition diagram showing 'normal', 'degraded', and 'faulty' states with transitions between them. - -Figure 9.1.3-6: Availability State - -The availability state is derived from detected and active faults and their impact to O-RU's operation. The availability state is not affected by faults caused by external reasons. - -- normal: There is no fault. -- degraded: When major or critical fault affecting module or any of O-RU's subcomponents (e.g. transmitter) is active. -- faulty: The critical fault affecting whole O-RU is active and O-RU cannot continue any services. - -NOTE: The value of availability-state is not affected by the value of admin-state. - -**[usage-state]** - -The usage-state transition diagram for the O-RU is presented in Figure 9.1.3-7. - -![O-RU usage State transition diagram showing 'idle', 'active', and 'busy' states with transitions between them.](19f90331494ba1e143d915d8d0061942_img.jpg) - -``` - -stateDiagram-v2 - [*] --> idle - idle --> active - active --> idle - active --> busy - busy --> active - busy --> idle - -``` - -O-RU usage State transition diagram showing 'idle', 'active', and 'busy' states with transitions between them. - -Figure 9.1.3-7: usage State - -- idle: No carrier is configured in O-RU. -- active: The carrier(s) is(are) configured in O-RU. - -- busy: No more carrier can be configured in O-RU. - -### 9.1.4 Retrieve parameters - -O-RU Controller is able to retrieve parameters of the YANG module by using NETCONF or procedure, as illustrated in Figure 9.1.4-1. - -![Sequence diagram illustrating the Retrieve Parameters procedure. The diagram shows a NETCONF Client (O-RU Controller) sending a request to a NETCONF Server (O-RU). The request is an containing a element with . The O-RU responds with an containing the requested data. Callouts indicate that the client requests information and the server responds with the required value.](64bec4cd45e47e1976245711f702aca2_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client/ (O-RU Controller) - participant Server as NETCONF Server/ (O-RU) - Note right of Client: O-RU Controller request the information from the O-RU. - Client->>Server: [1] - Note left of Server: O-RU response the value required by O-RU Controller. - Server-->>Client: [2] - -``` - -Sequence diagram illustrating the Retrieve Parameters procedure. The diagram shows a NETCONF Client (O-RU Controller) sending a request to a NETCONF Server (O-RU). The request is an containing a element with . The O-RU responds with an containing the requested data. Callouts indicate that the client requests information and the server responds with the required value. - -Figure 9.1.4-1: Retrieve Parameters - -#### Preconditions: - -- O-RU Controller has completed exchange of NETCONF capabilities as part of connection establishment between O-RU and O-RU Controller(s). - -#### Post conditions: - -- O-RU controller has retrieved O-RU parameters as per or request. - -### 9.1.5 Modify parameters - -Before an O-RU Controller modifies the configuration (candidate or running) of an O-RU, it shall first lock the target configuration. This prevents other NETCONF clients from changing the shared configuration database until the O-RU Controller releases the lock. If another NETCONF client has already locked the configuration datastore, then the O-RU shall respond with a NETCONF error indicating that the requested lock is denied. In such circumstances, the O-RU controller should wait for a period of time before re-attempting to modify the O-RU's configuration. - -O-RU Controller is able to modify parameters of the YANG module by using the NETCONF procedure, as illustrated in Figure 9.1.5-1. - -When supported by an O-RU, the O-RU Controller shall perform any required modify operations **ONLY** on the candidate configuration datastore before committing the validated configuration to the running configuration datastore. When an O-RU does not support the candidate configuration datastore, the O-RU Controller should take extreme care whenever modifying the running configuration datastore as such will likely impact system operation. - -NOTE: Validation of the modified configuration is based on: - -- 1) basic YANG constraints (e.g. min-elements, range, pattern), -- 2) XPATH based YANG constraints (e.g. "leafref", "must" and "when" statements), and -- 3) external code which implements YANG constraints (e.g. defined in O-RAN specifications, YANG description statements, etc.). - -In case of failures, an error shall be returned. Refer to RFC 6241 [3] Appendix A for error codes. - -The vendor can define the behaviour after error occurred. - -![Sequence diagram titled 'Modify Parameters' showing the interaction between a NETCONF Server (O-RU) and a NETCONF Client (O-RU Controller). The client sends an rpc to the server. The server updates the value and then enters an 'alt' block labeled '[Success case]' and '[Failure case]'. In the success case, it returns an . In the failure case, it returns an . Callouts indicate that the client sets parameters and the server updates the value if the request is received.](29997432244f81212ee1e6c94f308f1b_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client/ (O-RU Controller) - participant Server as NETCONF Server/ (O-RU) - Note right of Client: O-RU Controller set parameters of object. - Client->>Server: [1] <...> - Note left of Server: If the value change request is received from O-RU Controller, the O-RU updates the value accordingly - alt Success case: [2] - else Failure case: [3] - end - -``` - -Sequence diagram titled 'Modify Parameters' showing the interaction between a NETCONF Server (O-RU) and a NETCONF Client (O-RU Controller). The client sends an rpc to the server. The server updates the value and then enters an 'alt' block labeled '[Success case]' and '[Failure case]'. In the success case, it returns an . In the failure case, it returns an . Callouts indicate that the client sets parameters and the server updates the value if the request is received. - -**Figure 9.1.5-1: Modify Parameters** - -**Preconditions:** - -- O-RU Controller has completed exchange of NETCONF capabilities as part of connection establishment between the O-RU and O-RU Controller(s). -- O-RU Controller has locked the target configuration. - -**Post conditions:** - -- O-RU controller has retrieved O-RU resource state as per request: - - Success case: The update is confirmed to O-RU Controller. - - Failure case: Failure reason is provided to O-RU Controller - -Sequential processing is assumed. Only a single rpc is allowed at a time. Next rpc shall be performed after previous rpc reply. - -O-RU shall be allowed to reject in case the content is found to be against e.g. functions supported by O-RU - like carrier configured out of band. - -After the modification procedure is complete, the O-RU Controller releases the lock on the target configuration. - -### 9.1.6 Deleting parameters - -Before an O-RU Controller deletes any configuration (candidate or running) of an O-RU, it shall first lock the target configuration. This prevents other NETCONF clients from changing the shared configuration database until the O-RU Controller releases the lock. If another NETCONF client has already locked the configuration datastore, then the O-RU shall respond with a NETCONF error indicating that the requested lock is denied. In such circumstances, the O-RU controller should wait for a period of time before re-attempting to delete the O-RU's configuration. - -O-RU Controller is able to delete parameters of the YANG module by using the NETCONF procedure with the "operation" attribute set to delete, as illustrated in Figure 9.1.6-1. - -If the configuration data does not exist, an element is returned with an value of "data-missing". - -When supported by an O-RU, the O-RU Controller shall perform any required delete operations **ONLY** on the candidate configuration datastore before committing the validated configuration to the running configuration datastore. When an O-RU does not support the candidate configuration datastore, the O-RU Controller should take extreme care whenever modifying the running configuration datastore as such will likely impact system operation. - -![Sequence diagram showing the delete parameters process between a NETCONF Server (O-RU) and a NETCONF Client (O-RU Controller).](41fa90d03d7195caa162c74d289817a4_img.jpg) - -The diagram illustrates the interaction for deleting parameters: - -- Initial State:** The NETCONF Client (O-RU Controller) sends a message "O-RU Controller deletes object." to the NETCONF Server (O-RU). -- Step 1:** The client sends an message to the server. The message structure is: - - -``` - -<...> -``` -- Annotation:** A callout box states: "The configuration data identified by the element containing the operation="delete" attribute is deleted from the configuration." -- Alt Block:** An "alt" block titled "[Success case]" and "[Failure case]" handles the server's response: - - Success case:** The server responds with [2] . - - Failure case:** The server responds with [3] . -- Final State:** The diagram ends with the NETCONF Server (O-RU) and NETCONF Client (O-RU Controller) labels at the bottom. - -Sequence diagram showing the delete parameters process between a NETCONF Server (O-RU) and a NETCONF Client (O-RU Controller). - -Figure 9.1.6-1: Delete Parameters - -**Preconditions:** - -- O-RU Controller has completed exchange of NETCONF capabilities as part of connection establishment between the O-RU and O-RU Controller(s). - -- O-RU Controller has locked the target configuration. - -**Post conditions:** - -- O-RU controller has updated the O-RU resource state as per request: - - Success case: The delete is confirmed to O-RU Controller. - - Failure case: Failure reason is provided to O-RU Controller - -Sequential processing is assumed. Only a single rpc is allowed at a time. Next rpc shall be performed after previous rpc reply. - -Delete Parameters is used to: - -- delete parameters of existing configuration. - -After the delete procedure is complete, the O-RU Controller releases the lock on the target configuration. - -When the O-RU is operating, the O-RU shall not autonomously delete configuration(s) that are created by NETCONF client(s). When the O-RU is restarted, it may lose configuration(s) that are not stored in the reset persistent memory. - -## 9.1.7 Notification framework - -### 9.1.7.1 General - -YANG notifications are used to signal event information to notification subscribers. The present document support two types of subscriptions for receiving YANG notifications: - -- dynamic, which is supported by all O-RUs, and -- configured, which is supported by O-RUs that support the NON-PERSISTENT-MPLANE feature. - -### 9.1.7.2 Event streams - -All O-RUs shall support the default "NETCONF" event stream, as specified in clause 3.2.3 of RFC 5277 [21]. In addition to the default event stream, O-RUs should support the following event streams: - -- "fault-management" used to subscribe to YANG notification events defined in o-ran-fm YANG model. -- "measurement-result-stats" used to subscribe to YANG notification events defined in o-ran-performance-management YANG model. -- "supervision-notification" used to subscribe to YANG notification events defined in o-ran-supervision YANG model. - -### 9.1.7.3 Event stream discovery and subscription - -An O-RU controller discovers the O-RU's ability to process and send event notifications via capability exchange, as defined in clause 3.1 of RFC 5277 [21]. - -The O-RU shall support event stream discovery as defined in clause 3.2.5 of RFC 5277 [21]. Prior to initiating a dynamic subscription to an event stream, an O-RU controller can discover the O-RU's supported event streams. Refer to clause 3.2.5 of RFC 5277 [21] for detail. - -All O-RUs shall support event stream subscription using the RPC specified in clause 2 of RFC 5277 [21]. An O-RU may support event stream subscription using RPC specified in clause 2.4 of RFC8639 [37]. An O-RU indicates it supports by including the ietf-subscribed-notifications YANG model in its YANG library. An O-RU supporting event stream subscription using RPC shall be able to support concurrent operation of and RPCs on separate NETCONF sessions. - -If the O-RU supports the NON-PERSISTENT-MPLANE feature, the O-RU shall maintain the **streams** container as defined in clause 3.1 of RFC 8639 [37]. An O-RU controller supporting RFC 8639 [37] operating with an O-RU that supports the NON-PERSISTENT-MPLANE feature may use the **streams** container to recover the list of available streams supported by the O-RU. - -The O-RU supported event streams can be subscribed using dynamic subscriptions and, for those O-RUs that support the NON-PERSISTENT-MPLANE feature, using configured subscriptions. These are transported using NETCONF and VES respectively. - -- When no parameter is provided at creation of subscription, the default "NETCONF" stream is subscribed. -- The "NETCONF" default event stream can be subscribed to by all O-RU controllers. Events defined in the YANG modules to which the O-RU controller does not have "execute" access privileges, i.e. modules without an "X" in Table 6.5-1, shall be excluded before the events which are sent to the subscriber. -- For non-default streams, the NACM "execute" privileges defined in clause 6.5 shall be used by the O-RU to determine whether an O-RU controller has privileges to establish a subscription to a particular non-default event-stream. - -An O-RU Controller that has used the RPC to subscribe to an event stream may cancel the subscription by using the RPC. An O-RU receiving a RPC for an existing subscription-id shall cease sending notification messages for this subscription. - -## 9.1.8 Transactions and configuration data validity - -An O-RU shall ensure that its configuration datastore has always been updated with any modified configuration before sending the in response to a transaction that is intended to update the O-RU's system configuration. Except when using the o-ran-uplane-conf YANG model to configure the carrier configuration as described in clause 15.3, the O-RU's system implementation of the modification to its running configuration should occur before sending the message. - -In the case of o-ran-uplane-conf YANG model based carrier configuration, because implementation of the carrier activation/deactivation/energy savings can require operation of some closed loop control system, the YANG model defines the following notifications that allow a subscribing O-RU controller to be signalled when a configuration change has been implemented: - -- **tx-array-carriers-state-change**: used to be able to notify subscribers that the changes to a tx-array-carrier have been implemented. -- **rx-array-carriers-state-change**: used to be able to notify subscribers that the changes to an rx-array-carrier have been implemented. -- **data-layer-control-wakeup-notification**: used to be able to notify subscribers that the changes to energy-savings group have been implemented. -- **mplane-trx-control-ant-mask-update**: used to be able to notify subscribers that the changes to the antenna mask have been implemented. - -- **max-power-level-used:** used to indicate max output power level that is used for a tx-array. - -In the above cases, the O-RU may send the before the updated configuration has been implemented. This avoids extended periods of time when the configuration would otherwise be locked while configuration changes are implemented. - -### 9.1.9 YANG model support for target value configuration and used-value retrieval - -An O-RU may support target value configuration which means that the O-DU configures a target value for a configuration and the O-RU returns its used-value which is an approximation of the target value that is suitable for the O-RU. Parameters can have individual restrictions regarding how this approximation or selection shall be done (see relevant clauses describing the parameters in CUS-plane specification). - -The following steps show the general procedure to perform such target value configuration method, as illustrated in Figure 9.1.9-1. - -- 1) The O-DU configures the O-RU using consisting of one or more parameter(s) (e.g. **eq-scale-offset-config**, **sinr-reference-level-config**, etc.) with target value(s). -- 2) The O-RU sets the used-value(s) in corresponding read-only parameter(s) (e.g. **eq-scale-offset-used**, **sinr-reference-level-used**) for the configured target value(s). -- 3) The O-RU replies . -- 4) The O-DU receives the O-RU's rpc reply, which indicates the configuration process in steps 1 and 2 is finished. The used-value(s) of the read-only parameter(s) (e.g. **eq-scale-offset-used**, **sinr-reference-level-used**) are available. -- 5) The O-DU retrieves the used-value(s) from the O-RU using when the O-DU wants, e.g. before carrier activation. -- 6) The O-DU receives the used-value(s) of the read-only parameter(s), so the O-DU is aware of precise value(s) selected and used by the O-RU. - -![Sequence diagram showing the procedure of target value configuration and used-value retrieval between a NETCONF Server/(O-RU) and a Netconf Client/(O-DU).](0b2ee589f5c7802f3d332f421340cae1_img.jpg) - -``` - -sequenceDiagram - participant NETCONF Server/(O-RU) - participant Netconf Client/(O-DU) - Note right of Netconf Client/(O-DU): The NETCONF Client(O-DU) understands used value(s) for RO parameter(s) is(are) available - Note right of Netconf Client/(O-DU): O-DU is aware of the precise value(s) used by O-RU - - Netconf Client/(O-DU)->>NETCONF Server/(O-RU): with target value in RW parameter(s) - NETCONF Server/(O-RU)-->>NETCONF Server/(O-RU): set actually used value(s) in RO parameter(s) - NETCONF Server/(O-RU)-->>Netconf Client/(O-DU): - Netconf Client/(O-DU)->>NETCONF Server/(O-RU): - NETCONF Server/(O-RU)-->>Netconf Client/(O-DU): read-only parameter value(s) returned - -``` - -Sequence diagram showing the procedure of target value configuration and used-value retrieval between a NETCONF Server/(O-RU) and a Netconf Client/(O-DU). - -Figure 9.1.9-1: Procedure of target value configuration and used-value retrieval - -## 9.2 Framework for optional feature handling - -This clause describes the common and optional features about Configuration Management. - -An O-RU may have some features which are not supported by other O-RUs, i.e. optional feature(s). In this case, the O-RU needs to inform the O-RU controller which features the O-RU can provide, and this can be achieved by exchanging NETCONF capabilities. - -Some of the YANG models are optional for the O-RU to support. For example, in this version of the management plane specification, those models associated with External IO and Antenna Line Devices are not essential for the operation of the O-RAN fronthaul interface. Other mandatory models define optional feature capabilities. - -Both the NETCONF Server and NETCONF Client shall use the ietf-yang-library mode, as specified in RFC 8525 [59] to signal the namespaces of the models supported by the NETCONF Server. If an O-RU/NETCONF Server does not return the namespace associated with an optional YANG model, the NETCONF Client determines that the O-RU/NETCONF Server does not support the optional capability associated with the model. - -In addition, for each supported schema, the ietf-yang-library lists the YANG feature names from this module that are supported by the server. The details of optional models and features are defined in clause C. - -## 9.3 M-Plane operational state - -The o-ran-mplane-int YANG model allows the O-RU to report the connectivity to NETCONF clients on a per sub-interface level. The client information shall include the IP address(es) for the client(s) as well as the link-layer address used to forward packets towards the various management plane clients. - -## 9.4 Notification of updates to configuration datastore - -### 9.4.1 Introduction - -This clause defines an optional O-RU capability which allows O-RU Controllers to configure the O-RU to provide notifications of modifications to its YANG datastore. This capability can be used when the O-RU is operating in a hybrid environment with multiple simultaneous NETCONF sessions established to different O-RU controllers. Using this capability, one particular O-RU controller uses the NETCONF notifications functionality as specified in RFC 6470 [35] to enable it to be automatically signalled changes to the O-RU's configuration made by a second O-RU controller. Additionally, if the O-RU supports a vendor specific interface to allow manual configuration, this functionality can also be used to signal such configuration modifications to an O-RU Controller. - -### 9.4.2 Subscribing to updates from an O-RU - -When an O-DU receives an indication from an O-RU that it supports the optional capability to support notification of updates to its configuration data store, as a minimum, it may subscribe to the **netconf-config-change** notification. - -An example event notification is shown in Figure 9.4.2-1, where a notification indicates that the configuration of the O-RU's timezone offset has been modified by a second O-RU controller. - -``` - - 2020-03-01T08:00:14.12Z - - 102 - - nms-user - 1099 - 10.10.10.10 - - running - - /oran-ops:operational-info/oran-ops:clock/oran-ops:timezoneutc-offset - replace - - - -``` - -**Figure 9.4.2-1: Example of a netconf-config-change notification** - -## 9.5 Resetting O-RU - -### 9.5.1 O-RU reset procedure - -An O-RU reset may be triggered by an O-RU controller or autonomously triggered by an O-RU, e.g. as a result of supervision failure specified in clause 14.1.1. - -### 9.5.2 O-RU controller triggered O-RU reset operation - -The reset procedure can be used by an O-RU controller to trigger the reset of the O-RU. The reset of an O-RU shall trigger the O-RU to perform a re-start and follow the procedures defined in clause 6. - -### 9.5.3 O-RU controller triggered O-RU reset procedure - -O-RU Controller is able to trigger the reset of an O-RU by using the **reset** rpc, as illustrated in Figure 9.5.3-1. - -**Pre-condition:** - -- M-Plane connection is established and running between O-RU and O-RU controller. - -**Post-condition:** - -- O-RU performs reset followed by start-up sequence described in clause 6. - -![Sequence diagram showing the O-RU Reset Procedure. It starts with a NETCONF session established between an O-RU (Server) and an O-RU Controller (Client). The Controller sends a RPC request to the Server. The Server responds with a RPC reply. Following the reply, the O-RU re-starts. The diagram ends with the Server and Client boxes at the bottom, indicating the completion of the reset process.](b822771c1a5790feaeecfc439e08bcdd_img.jpg) - -``` - -sequenceDiagram - participant O-RU as NETCONF Server/ (O-RU) - participant Controller as NETCONF Client/ (O-RU Controller) - Note right of Controller: NETCONF session established. - Controller->>O-RU: [1] - O-RU-->>Controller: [2] - Note left of O-RU: O-RU re-starts - -``` - -Sequence diagram showing the O-RU Reset Procedure. It starts with a NETCONF session established between an O-RU (Server) and an O-RU Controller (Client). The Controller sends a RPC request to the Server. The Server responds with a RPC reply. Following the reply, the O-RU re-starts. The diagram ends with the Server and Client boxes at the bottom, indicating the completion of the reset process. - -**Figure 9.5.3-1: O-RU Reset Procedure** - -## 10 Performance management - -### 10.1 General - -This clause provides the description of scenarios related to performance management. It consists of 2 functions. One is for the measurement activation and the other is the collection of measurement results. - -Performance management key concepts: - -**Measurement group:** A group of measurement objects that belong to the same category, e.g. **tx-stats**. Each measurement-group is associated with a measurement-group identifier that is used in file management processing (See clause 10.3.2) - -**Measurement object:** Object on which performance is measured, e.g. **RX\_POWER**, **TX\_POWER**. Only when combined with a report-info, it defines a metric. - -**Object unit:** Granularity to measure the performance per measurement object, e.g. **PORT\_NUMBER**, **EAXC\_ID**. - -**Report info:** Type of the measurement, e.g. **MAXIMUM**, **MINIMUM**. Only when combined with a measurement-object, it defines a metric. - -### 10.2 Measurement configuration, activation and de-activation - -The measurement activation at the start-up installation is described in clause 6. - -This clause provides information about how to configure, activate and de-activate the performance measurement in an O-RU. The performance measurement schema nodes are defined in o-ran-performance-management YANG module. In case of multiple NETCONF clients, only one NETCONF client shall activate/deactivate the measurements in the O-RU. The O-RU shall support those measurements described as mandatory in clause 9.1 of the O-RAN CUS plane specification [2]. - -NOTE 1: The naming convention of schema nodes that report capability for each measurement-group (in container **measurement-capabilities**) uses an abbreviated form of the measurement-group name (enough to uniquely identify the measurement-group), ending with "-objects". e.g. **transceiver-objects**, **rx-window-objects**. - -NOTE 2: The naming convention of schema nodes that are used to configure each measurement-group uses an abbreviated form of the measurement-group name (enough to uniquely identify the measurement-group), ending with "-measurement-objects". e.g. **transceiver-measurement-objects**, **rx-window-measurement-objects**. - -NOTE 3: The naming convention for schema node (list) to define notification content of each measurement-group (as part of notification **measurement-result-stats**) uses measurement-group name, for example, **ethernet-stats**, **tx-output-power-stats**, etc. - -The detail of the **measurement-group(s)**, including **measurement-object(s)**, **object-unit(s)** and **report-info(s)** supported by M-Plane are defined in clause Annex B. - -For each **measurement-group**, at least one of the capabilities may be reported: supported **measurement-object(s)**, supported **report-info(s)** per measurement-object and supported **object-unit(s)** per measurement-object. - -For each active measurement, the NETCONF client shall configure **measurement-interval** per **measurement-group** using respective **measurement-interval** parameter. It defines performance measurement periodicity, e.g. 300, 600, 900 - -seconds. **measurement-objects** belong to a **measurement-group** inherit the **measurement-group measurement-interval**. - -NETCONF client can configure a **measurement-group** with **measurement-objects** belonging to it. For each measurement-object, **object-unit** and **report-info(s)** are configured. For selected **report-info**, the NETCONF Client may configure additional parameters, e.g. function, bin-count, upper-bound, lower-bound. - -Measurement shall be activated using parameter **active** per **measurement-object** when **report-info(s)** and **measurement-interval** for the measurement-object is/are configured. A measurement-object can be activated and deactivated at any time. - -- When different **measurement-group(s)** have intervals with a common factor, the O-RU shall synchronise the boundary of these intervals with this factor, irrespective of when the different **measurement-objects** are activated, as illustrated in Figure 10.2-1. All of start points of the **measurement-intervals** of **measurement-groups** shall be synchronised to zero o'clock mid-night by using an equation {full seconds (hour, minute and second) modulo 'measurement-interval' = 0}, in order to ensure the same start and end of the **measurement-intervals** between O-RUs. For more details see the following illustration. -- The **start-time** and **end-time** indicate the time of measurement start and end for the measurement-object at each measurement-interval. - -![Figure 10.2-1: synchronisation of measurement-interval. The diagram shows a timeline with time markers 00:00:00, T, T+1, T+2, T+3, T+4, and Time. Three measurement objects are shown: measurement-object#A of O-RU#2, measurement-object#B of O-RU#1, and measurement-object#B of O-RU#2. measurement-object#A of O-RU#2 has four intervals: Interval#1 (activated time to T), Interval#2 (T to T+2), Interval#3 (T+2 to T+4), and Interval#4 (T+4 to Deactivated time). measurement-object#B of O-RU#1 and measurement-object#B of O-RU#2 have intervals starting at T+3 and ending at T+4. A bracket labeled 'measurement-interval of measurement-object#A' spans from T+2 to T+4. A bracket labeled 'measurement-interval of measurement-object#B' spans from T+3 to T+4.](d2b4ad9211363b5097662110e1e5774b_img.jpg) - -start and end-time of the measurement-object#A - -- Interval#1: start-time = activated time, end time = T -- Interval#2: start-time = T, end time = T+2 -- Interval#3: start-time = T+2, end time = T+4 -- Interval#4: start-time = T+4, end time = Deactivated time - -Figure 10.2-1: synchronisation of measurement-interval. The diagram shows a timeline with time markers 00:00:00, T, T+1, T+2, T+3, T+4, and Time. Three measurement objects are shown: measurement-object#A of O-RU#2, measurement-object#B of O-RU#1, and measurement-object#B of O-RU#2. measurement-object#A of O-RU#2 has four intervals: Interval#1 (activated time to T), Interval#2 (T to T+2), Interval#3 (T+2 to T+4), and Interval#4 (T+4 to Deactivated time). measurement-object#B of O-RU#1 and measurement-object#B of O-RU#2 have intervals starting at T+3 and ending at T+4. A bracket labeled 'measurement-interval of measurement-object#A' spans from T+2 to T+4. A bracket labeled 'measurement-interval of measurement-object#B' spans from T+3 to T+4. - -Figure 10.2-1: synchronisation of measurement-interval. - -The modification of the configurable parameters (except **active**) for the **measurement-object** shall be allowed only while **active** for the corresponding **measurement-object** has value FALSE. Removal of **measurement-object(s)** from a **measurement-group** configurations (by configuring schema nodes, e.g. **transceiver-measurement-objects**, **rx-window-measurement-objects**, etc.) shall be allowed only when **active** for those intended to be removed measurement-object(s) has value FALSE. - -An O-RU Controller may configure multiple **report-info(s)** for a measurement-object. A metric is defined by a **measurement-object** and a **report-info**. The metric value is re-initialised at the beginning of each measurement-interval. - -For the first **measurement-interval**, due to varying **start-time** (due to varying activation time), if the duration of the first interval is insufficient for the O-RU to calculate valid measurement values, the O-RU may skip sending the measurement report for the first **measurement-interval**. - -## 10.3 Collection and reporting of measurement result - -### 10.3.0 Introduction - -This clause provides the description of scenarios used to collect measurement results. There are three options: - -- 1) NETCONF process: Create-subscription from NETCONF client and NETCONF notification from NETCONF server are used. -- 2) File Management process: File upload mechanism is used to transfer the measurement file from O-RU to configured file server(s) that O-RU can reach to. -- 3) Configured subscription process: Create configured subscription from O-RU as Event-Producer to Event-Collector. - -Methods 1 and 2 are mandatory for the O-RU. Method 3 shall be supported by those O-RUs that support the optional NON-PERSISTENT-MPLANE feature. The method(s) to be used is the matter of NETCONF client. - -In case of multiple NETCONF clients and/or Event-Collectors, the O-RU shall report the same notification-based measurement results to all subscribed NETCONF clients/Event-Collectors, and the O-RU shall upload file-based results to all configured file servers. - -### 10.3.1 NETCONF process for dynamic subscriptions - -This process needs the NETCONF capability: `urn:ietf:params:netconf:capability:notification:1.0`. - -- 1) NETCONF client subscribes to one or more measurement group(s) and/or **measurement-object(s)** to collect the measurement result by sending NETCONF <**create-subscription**> to NETCONF server in the O-RU. In this message, `startTime` and `stopTime` for the notification may be configurable. NETCONF client can configure the **notification-interval** in the performance-management YANG module. -- 2) NETCONF server sends NETCONF notification messages periodically to the client as configured by the **notification-interval**. The NETCONF notification message contains subscribed measurement group(s) and/or **measurement-object(s)**. The **notification-interval** does not need to be same as the **measurement-interval**. The notification timing different from the **measurement-interval** is a matter to O-RU implementation. - -This procedure is described in Figure 10.3.1-1. - -![Sequence diagram showing the NETCONF process of Measurement Result Collection. A NETCONF Client sends a subscription message to a NETCONF Server/(O-RU). A 'notification loop' labeled '[notification loop]' contains a 'loop' with the condition 'every notification-interval'. Inside the loop, the server sends a notification message labeled '[1] ' to the client.](9cf678d634932a43b7f6582878972a5d_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client - participant Server as NETCONF Server/(O-RU) - Note right of Client: client subscribes to receive measurement-result-stats events - loop notification loop - loop every notification-interval - Note right of Server: [1] - Server->>Client: - end - end - -``` - -Sequence diagram showing the NETCONF process of Measurement Result Collection. A NETCONF Client sends a subscription message to a NETCONF Server/(O-RU). A 'notification loop' labeled '[notification loop]' contains a 'loop' with the condition 'every notification-interval'. Inside the loop, the server sends a notification message labeled '[1] ' to the client. - -Figure 10.3.1-1: NETCONF process of Measurement Result Collection - -A NETCONF client may use the **create-subscription** for the single event-stream "**measurement-result-stats**", or alternatively subscribe the default event-stream using additional filter criteria to identify those measurements of interest to the client. In order to subscribe multiple notifications, the appropriate **create-subscription** message is required. Refer to clause 11.3 for the appropriate example of **create-subscription** of multiple notifications. - -In order to terminate the subscription, the NETCONF client shall send **** operation from the subscription session or configuring the **** parameter when the subscription was created. If NETCONF session is terminated by ****, the subscribed notification is terminated as well. - -This procedure is described in Figure 10.3.1-2. - -![Sequence diagram showing the NETCONF process of Measurement Result Collection to end. A NETCONF Client sends an message containing , [1] measurement-result-stats-notification, , and to a NETCONF Server/(O-RU). The server responds with [2] . A note on the server side indicates 'notification is terminated.'](fb73a07d61dc5c47709b9802b894d716_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client - participant Server as NETCONF Server/(O-RU) - Note right of Client: [1] measurement-result-stats-notification - Client->>Server: ... - Note left of Server: [2] - Server->>Client: ... - Note left of Server: notification is terminated. - -``` - -Sequence diagram showing the NETCONF process of Measurement Result Collection to end. A NETCONF Client sends an message containing , [1] measurement-result-stats-notification, , and to a NETCONF Server/(O-RU). The server responds with [2] . A note on the server side indicates 'notification is terminated.' - -Figure 10.3.1-2: NETCONF process of Measurement Result Collection to end - -When **notification-interval** is larger than **measurement-interval**, O-RUs implementing v07.00 or later of the present document may use a single notification that contains multiple stats included in the list such as **multiple-transceiver-measurement-result**, **multiple-rx-window-measurement-result**, **multiple-tx-measurement-result**, **multiple-epe-measurement-result** or **multiple-symbol-rssi-measurement-result** which have consecutive periods indicating **start-time** and **end-time** for the measurement. - -NOTE 2: When multiple measurements stats corresponding to the same measurement-group are available in an O-RU that implements an earlier version of the present document, the O-RU is only able to include a single statistic in the notification. In such circumstances, the O-RU should report the latest available statistic in the notification. - -NOTE 3: An O-RU Controller that implements an earlier version of the present document can ensure that the configuration of **notification-interval** and **measurement-interval** results in only a single measurement statistic corresponding to a specific measurement-group being reported by the O-RU in any one notification. In other cases, the O-RU Controller can use the rules defined in clause 4.3 to ignore the newly introduced schema-nodes for reporting multiple measurements. - -When **notification-interval** is smaller than **measurement-interval**, one notification may not contain the stats which **start-time** and **end-time** are not applicable to the period for the notification. - -For example, when **notification-interval** = 60min, **measurement-interval** for **measurement-object#A** = 30min and **measurement-interval** for **measurement-object#B** = 15min, one notification contains 2 measurement results for **measurement-object#A** with consecutive **start-time** and **end-time**, and 4 measurement results for **measurement-object#B** with consecutive **start-time** and **end-time**. - -For the other example, when **notification-interval** = 15min, **measurement-interval** for **measurement-object#A** = 30min and **measurement-interval** for **measurement-object#B** = 15min, one notification contains one measurement results for **measurement-object#B** but not for **measurement-object#A**. next notification contains both measurements result for **measurement-object#A** and **#B**. - -### 10.3.2 File management process - -NETCONF client needs to configure a parameter of performance measurement YANG module '**enable-file-upload**' to enable or disable the periodic file upload mechanism via NETCONF . Its default is FALSE. - -In addition, the performance measurement YANG module defines **file-upload-interval**, **remote-file-upload-path**, **credentials** information of the file server and **enable-random-file-upload** as configurable parameters. - -Following types of authentications shall be supported for **performance file upload**: - -- Password for RU authentication and list of public keys (see clause 5.4 in the present document) for sFTP server authentication. - -Following types of authentications may be supported for **performance file upload**: - -- X.509 Certificate for FTPES client (O-RU) and FTPES server. -- Certificate for both O-RU and sFTP server authentication. - -When the parameter **enable-file-upload** is set to TRUE, O-RU shall store the performance measurement files in the generic folder in O-RU, i.e. O-RAN/PM/ or o-ran/pm/. Every **file-upload-interval**, O-RU pushes the latest file to upload to the **remote-file-upload-path** of the configured SFTP/FTPES servers if **enable-file-upload** is set to TRUE. Otherwise, the performance measurement file is not created and uploaded. The O-RU shall use the URI scheme of the **remote-file-path** leaf to determine whether to use sFTP or FTPES for the file upload. The number of maximum performance files to be stored in O-RU simultaneously is a matter for O-RU implementation. The O-RU shall manage - -its own storage space by deleting the older files autonomously. An O-RU Controller shall only trigger file upload using FTPES if it is using NETCONF/TLS to configure the O-RU. - -The O-RU shall ensure that the **start-time** and the **end-time** within the name of the performance measurement file are synchronised with the same manner as **measurement-interval** by using **file-upload-interval**. - -If the parameter **enable-random-file-upload** is set to TRUE, the O-RU shall randomize the timing to upload SFTP or FTPES file after the performance measurement file is ready to upload. The randomized timing is an O-RU implementation matter and shall not be later than next **file-upload-interval**. - -The file name of the performance measurement is: - -C\_\_.csv - -- Starting with a capital letter "C". -- Format of <**start-time**> and <**end-time**> can be local time or UTC. - -Local time format is YYYYMMDDHHMM+HHMM, indicating, year, month, day, hour, minute, timezone "+" or "-", hour and minute for the time zone. - -UTC format is YYYYMMDDHHMMZ, indicating, year, month, day, hour, minute and with a special UTC designator ("Z") - -Time zone offset is provided by **timezone-utc-offset** in o-ran-operation.yang. - -- <**name**> in ietf-hardware is used. -- "\_" underscore is located between <**start-time**>, <**end-time**> and <**name**>. -- File extension is "csv" as csv format file. - -Example of measurement file is: - -- C201805181300+0900\_201805181330+0900\_ABC0123456.csv. - -The file format of the performance measurement has following rule: - -- 1) Each line starts with an identifier. The identifier should be used to identify each **measurement-group** defined by its row in Table B.1.1-1, e.g. transceiver-stats should be identified by an identifier of "1", rx-window-stats should be identified by a measurement-group identifier of "2" and tx-measurement-objects should be identified by a measurement-group of "3", etc. - -NOTE 1: The use of the identifier to identify a measurement group is only recommended in order to accommodate an earlier release of the present document where the use of the identifier was ambiguous. - -- 2) After the measurement-object identifier, the name of measurement-object, start-time, end-time are appended. -- 3) Then the **object-unit** and **object-unit-id** are appended, followed by the set of **report-info** are repeated in one line. - -NOTE 2: If the leading identifier is not used to signal a measurement-group, the measurement-group needs to be derived from the **object-unit**. For example, an **object-unit** of "PORT\_NUMBER" is used to identify the transceiver-stats measurement-group, and an **object-unit** of "ianahw:port" is used to identify an epe-statistics measurement group for the ianahw:port hardware class. - -NOTE 3: If a measurement is referenced by multiple **object-units**, each **object-unit** and corresponding **object-unit-id** are appended in turn. - -- 4) When the YANG definition of the measurement-result-grouping includes one or more lists and multiple **report-info** parameters exist per **object-unit**, all of the **report-info** are consecutively listed until the next **object-unit-id**. The order of parameters, such as object-unit-id, report-info and additional information for the report-info, shall be same as the order of those listed in NETCONF notification defined in o-ran-performance-management YANG module. -- 5) When the YANG definition of the measurement-result-grouping includes one or more containers, the container name is included in the **report-info**. - -NOTE 4: In versions prior v13.0 of the present document, the use of the container name in the **report-info** was not defined and hence how such measurement reports were encoded was not specified. - -Example of multiple transceiver measurements on one line is: - -``` -1, RX_POWER, 2018-05-18T13:00:00+09:00, 2018-05-18T13:15:00+09:00, PORT_NUMBER, 0, min, 0.10232, -2018-05-18T13:01:12+09:00, max, 1.5849, 2018-05-18T13:09:54+09:00 -``` - -- Measurement-group identifier: 1 (transceiver-stats) -- Name of **measurement-object**: RX\_POWER -- **start-time**: 2018-05-18T13:00:00+09:00 as measurement **start-time**. -- **end-time**: 2018-05-18T13:30:00+09:00 as measurement **end-time** -- **object-unit**: PORT\_NUMBER -- **object-unit-id**: 0 (Port number 0) -- **Report-Info**: - - Minimum 0.10232 mW Rx input Power measured at 2018-05-18T13:01:12+09:00 - - Maximum 1.589 mW Rx input Power measured at 2018-05-18T13:09:54+09:00 - -Example of multiple rx-window measurement results on one line is: - -``` -2, RX_LATE, 2018-05-18T13:00:00+09:00, 2018-05-18T13:30:00+09:00, EAXC_ID, 0, 123, 1, 153 -``` - -- Measurement-group identifier: 2 (rx-window-stats) -- Name of **measurement-object**: RX\_LATE -- **start-time**: 2018-05-18T13:00:00+09:00 as measurement **start-time**. -- **end-time**: 2018-05-18T13:30:00+09:00 as measurement **end-time** -- **object-unit**: EAXC\_ID -- **object-unit-id**: 0 (EAXC\_ID: 0) -- Count for EAXC\_ID#0 : 123 -- **object-unit-id**: 1 (EAXC\_ID: 1) -- Count for EAXC\_ID#1 : 153 - -Example of hardware class based reporting of epe statistics: - -``` -4, TEMPERATURE, 2018-05-18T13:00:00+09:00, 2018-05-18T13:15:00+09:00, or-hw:O-RU-POWER-AMPLIFIER, -PA1, min, 25, max, 44, avg, 33 -``` - -- Measurement-group identifier: 4 (epe-stats object) -- Name of **measurement-object**: TEMPERATURE -- **start-time**: 2018-05-18T13:00:00+09:00 as measurement **start-time**. -- **end-time**: 2018-05-18T13:30:00+09:00 as measurement **end-time** -- **object-unit**: or-hw:O-RU-POWER-AMPLIFIER (Power amplifier hardware class) -- **object-unit-id**: PA1 (the name associated with a power amplifier) -- **Report-Info**: - - minimum 25 degrees - - maximum 44 degrees - - average 33 degrees - -Example of frequency bin based reporting of multiple symbol RSSI measurements: - -``` -5, ALL-UL-SYMBOLS, 2018-05-18T13:00:00+09:00, 2018-05-18T13:15:00+09:00, RX-ARRAY-CARRIER, RX-ARRAY-CARRIER1, frequency-bin-table, 0, 2046, 1, 9718, 2, 19437, 3, 15345, 4, 4092, 5, 511 -``` - -- Measurement-group identifier: 5 (symbol-rssi-stats object) -- Name of **measurement-object**: ALL-UL-SYMBOLS -- **start-time**: 2018-05-18T13:00:00+09:00 as measurement **start-time**. -- **end-time**: 2018-05-18T13:30:00+09:00 as measurement **end-time** -- **object-unit**: RX-ARRAY-CARRIER -- **object-unit-id**: RX-ARRAY-CARRIER1 (the name associated with rx-array carrier) -- **Report-Info** corresponding to a frequency bin table: - - bin-id 0, value 2046 - - bin-id 1, value 9718 - - bin-id 2, value 19437 - - bin-id 3, value 15345 - - bin-id 4, value 4092 - - bin-id 5, value 511 - -Example of combine reporting requiring multiple object-unit-id values: - -``` -6, RX_UP_UL_COMBINED, 2018-05-18T13:00:00+09:00, 2018-05-18T13:10:00+09:00, TRANSPORT, PROC_ELEMENT1, 123400, PROC_ELEMENT2, 123400 -``` - -- Measurement-group identifier: 6 (shared-cell statistics object) -- Name of **measurement-object**: RX\_UP\_UL\_COMBINED -- **start-time**: 2018-05-18T13:00:00+09:00 as measurement **start-time**. - -- **end-time:** 2018-05-18T13:30:00+09:00 as measurement **end-time** -- **object-unit:** TRANSPORT -- **object-unit-id:** PROC\_ELEMENT1 (Processing element name: "PROC\_ELEMENT1") -- Count for PROC\_ELEMENT1: 123400 -- **object-unit-id:** PROC\_ELEMENT2 (Processing element name: "PROC\_ELEMENT2") -- Count for PROC\_ELEMENT2: 102431 - -Example of frequency bin based reporting of VSWR measurements: - -7, VSWR, 2023-10-02T13:00:00+02:00, 2023-10-02T13:30:00+02:00, ARRAY\_ELEMENT, tx-array1:2, frequency-bin-table, 0, 21, 1, 37, 2, 77, 3, 11, 4, 101, 5, 1 - -- Measurement-group identifier: 7 (tx-antenna-stats object) -- Name of **measurement-object:** VSWR -- **start-time:** 2023-10-02T13:00:00+02:00 as measurement **start-time**. -- **end-time:** 2023-10-02T13:30:00+02:00 as measurement **end-time** -- **object-unit:** ARRAY\_ELEMENT -- **object-unit-id:** tx-array1:2 (an array element k=2 on the tx-array named “tx-array-1”) -- **Report-Info** corresponding to a frequency bin table: - - bin-id 0, value 21 - - bin-id 1, value 37 - - bin-id 2, value 77 - - bin-id 3, value 11 - - bin-id 4, value 101 - - bin-id 5, value 1 - -Example of reporting of TSSI measurements: - -8, TSSI-IQ-POWER-LEVEL, 2023-10-02T13:00:00+02:00, 2023-10-02T13:30:00+02:00, CARRIER\_ARRAY\_ELEMENT, TX-ARRAY-CARRIER1, per-tx-array-element-index-result, tx-array-1:2, avg, -26.93, min, -39.40, max, -16.33 - -- Measurement-group identifier: 8 (tssi-stats-object) -- Name of **measurement-object:** TSSI-IQ-POWER-LEVEL -- **start-time:** 2023-10-02T13:00:00+02:00 as measurement **start-time**. -- **end-time:** 2023-10-02T13:30:00+02:00 as measurement **end-time** -- **object-unit:** CARRIER\_ARRAY\_ELEMENT -- **object-unit-id:** TX-ARRAY-CARRIER1 (the name associated with **tx-array carrier**) -- per-tx-array-element-index-result - -- tx-array-1:2 (an array element k=2 on the tx-array named "tx-array-1") -- **Report-Info:** - - average -26.93 - - minimum -39.40 - - maximum -16.33 - -Example of reporting of RSSI measurements: - -9, RSSI, 2023-10-02T13:00:00+02:00, 2023-10-02T13:30:00+02:00, CARRIER\_ARRAY\_ELEMENT, RX-ARRAY-CARRIER1, per-rx-array-element-index-result, rx-array-1:2, avg, -89.2, min, -106.1, max, -52.8 - -- Measurement-group identifier: 9 (rssi-stats-object) -- Name of **measurement-object**: RSSI -- **start-time**: 2023-10-02T13:00:00+02:00 as measurement **start-time**. -- **end-time**: 2023-10-02T13:30:00+02:00 as measurement **end-time** -- **object-unit**: CARRIER\_ARRAY\_ELEMENT -- **object-unit-id**: RX-ARRAY-CARRIER1 (the name associated with rx-array carrier) -- per-rx-array-element-index-result -- rx-array-1:2 (an array element k=2 on the rx-array named "rx-array-1") -- **Report-Info:** - - average -89.2 - - minimum -106.1 - - maximum -52.8 - -Example of reporting of TX-OUTPUT-POWER measurements: - -10, TX-OUTPUT-POWER, 2024-08-06T13:00:00+02:00, 2024-08-06T13:30:00+02:00, CARRIER\_ARRAY\_ELEMENT, TX-ARRAY-CARRIER1, per-tx-array-element-index-result, tx-array-1:0, avg, 43.01, min, 42.90, max 43.24, tx-array-1:1, avg, 43.03, min, 42.92, max, 43.26 - -- Measurement-group identifier: 10 (tx-output-power-stats-object) -- Name of **measurement-object**: TX-OUTPUT-POWER -- **start-time**: 2024-08-06T13:00:00+02:00 as measurement **start-time**. -- **end-time**: 2024-08-06T13:30:00+02:00 as measurement **end-time** -- **object-unit**: CARRIER\_ARRAY\_ELEMENT -- **object-unit-id**: TX-ARRAY-CARRIER1(the name associated with tx-array-carrier) -- per-tx-array-element-index-result -- tx-array-1:0 (an array element k=0 on the tx-array named "tx-array-1") -- **Report-Info:** - -average 43.01 - -minimum 42.90 - -maximum 43.24 - -- tx-array-1:1 (an array element k=1 on the tx-array named "tx-array-1") - -- **Report-Info:** - -average 43.03 - -minimum 42.92 - -maximum 43.26 - -Example of multiple ethernet measurements on one line is: - -``` -11, RECEIVED-CRC-ERRORED-FRAMES, 2018-05-18T13:00:00+09:00, 2018-05-18T13:15:00+09:00, -ETH_INTERFACE, 10Geth0.100, count, 1499 -``` - -- Measurement-group identifier: 11 (ethernet-stats object) -- Name of **measurement-object**: IN-CRC-ERRORS -- **start-time**: 2018-05-18T13:00:00+09:00 as measurement **start-time**. -- **end-time**: 2018-05-18T13:30:00+09:00 as measurement **end-time** -- **object-unit**: ETH\_INTERFACE -- **object-unit-id**: 10Geth0.100 (Ethernet interface with name 10Geth0.100) -- **Report-Info:** - - Count for 10Geth0.100: 1499. - -When **file-upload-interval** is larger than **measurement-interval**, one performance measurement file may contain multiple lines for the stats which have consecutive periods indicating **start-time** and **end-time** for the measurement. - -When **file-upload-interval** is smaller than **measurement-interval**, one performance measurement file may not contain the line for the stats which **start-time** and **end-time** are not applicable to the period for the performance measurement file. - -For example, when **file-upload-interval** = 60 min, **measurement-interval** for **measurement-object#A** = 30 min and **measurement-interval** for **measurement-object#B** = 15 min, one performance measurement file contains 2 measurement result lines for **measurement-object#A** with consecutive **start-time** and **end-time**, and 4 measurement result lines for **measurement-object#B** with consecutive **start-time** and **end-time** as follows: - -``` -1, RX_POWER, 2018-05-18T13:00:00+09:00, 2018-05-18T13:15:00+09:00, PORT_NUMBER, 0, max, 1.5849, -2018-05-18T13:09:54+09:00 - -1, RX_POWER, 2018-05-18T13:15:00+09:00, 2018-05-18T13:30:00+09:00, PORT_NUMBER, 0, max, 1.4125, -2018-05-18T13:21:08+09:00 - -2, RX_LATE, 2018-05-18T13:00:00+09:00, 2018-05-18T13:30:00+09:00, EAXC_ID, 0, 123, 1, 153 - -1, RX_POWER, 2018-05-18T13:30:00+09:00, 2018-05-18T13:45:00+09:00, -PORT_NUMBER, 0, max, 1.2882, 2018-05-18T13:44:00+09:00 - -1, RX_POWER, 2018-05-18T13:45:00+09:00, 2018-05-18T14:00:00+09:00, -``` - -``` -PORT_NUMBER, 0, max, 1.2022, 2018-05-18T13:49:44+09:00 - -2, RX_LATE, 2018-05-18T13:30:00+09:00, 2018-05-18T14:00:00+09:00, EAXC_ID, 0, 13, 1, 23 -``` - -For the other example, when **file-upload-interval** = 15 min, **measurement-interval** for **measurement-object#A** = 30 min and **measurement-interval** for **measurement-object#B** = 15 min, one performance measurement file contains one measurement result line for **measurement-object#B** but not for **measurement-object#A**. next performance measurement file contains both measurements result for **measurement-object#A** and **#B** as follows: - -``` -C201805181300Z+0900_201805181315+0900_ABC0123456.csv. - -1, RX_POWER, 2018-05-18T13:00:00+09:00, 2018-05-18T13:15:00+09:00, PORT_NUMBER, 0, max, 1.5849, -2018-05-18T13:09:54+09:00 - -C201805181315Z+0900_201805181330+0900_ABC0123456.csv. - -1, RX_POWER, 2018-05-18T13:15:00+09:00, 2018-05-18T13:30:00+09:00, -PORT_NUMBER, 0, max, 1.4125, 2018-05-18T13:21:08+09:00 - -2, RX_LATE, 2018-05-18T13:00:00+09:00, 2018-05-18T13:30:00+09:00, EAXC_ID, 0, 123, 1, 153 -``` - -The performance measurement files stored in O-RAN/PM or o-ran/pm/ can be uploaded on-demand. For the file upload mechanism by on-demand way, **retrieve-file-list** and **file-upload** operations are used. For more detail, refer to clause 12. - -### 10.3.3 Configured subscription process - -This optional process requires the O-RU to support configured subscriptions, as described in clause 18. The structure of the process follows the NETCONF process described in clause 10.3.1. However, instead of sending a NETCONF to the NETCONF server in the O-RU to subscribe to the **measurement-result-stats** notifications, the NETCONF client installs the subscription via configuration of the O-RU's datastore. Based on configured subscriptions, the O-RU sends asynchronous YANG notifications over HTTPS to the configured Event-Collector. - -In order to terminate the subscription, the NETCONF client shall delete the corresponding configuration in the O-RU. Immediately after the subscription is successfully deleted, the O-RU shall send to a subscription state change notification indicating that the subscription has ended to the Event-Collector. - -NOTE: Unlike the NETCONF process described in clause 10.3.1, the subscription to the subscribed notifications is not terminated when the NETCONF session used to establish the subscription is terminated. - ---- - -## 11 Fault management - -### 11.1 Introduction - -Fault management is used to manage active-alarm-list and optionally historical-alarm-list; handle alarm subscription and send alarm notifications to subscribers, which will typically be the NETCONF Client unless the O-RU supports the configured subscription capability, as described in clause 18, when the configured subscriber may be an Event-Collector. - -The NETCONF Server shall manage the **active-alarm-list**. Alarms with **fault-severity** set to WARNING are excluded from this list. When the raise alarm criteria are met, an alarm is raised and it is added to the list; when clear alarm conditions are fulfilled then the alarm is cleared and removed from the **active-alarm-list**. Furthermore, when the element that was the **fault-source** of an alarm is deleted then all related alarms are removed from the **active-alarm-list**. - -Optionally, the NETCONF Server is also responsible for managing the **historical-alarm-list**. Alarms with **fault-severity** set to WARNING are excluded from this list. When an alarm is cleared, it is added to this list with **is-cleared** set to "true". - -The NETCONF Client can read "active-alarm-list" by **get** RPC operation, as illustrated in Figure 11.1-1. - -![Sequence diagram illustrating the 'Read Active Alarms' operation. It shows a NETCONF Client sending a RPC for 'active-alarm-list' to a NETCONF Server/(O-RU), which responds with a containing the 'active-alarm-list' data. A note indicates the session is established before the request.](efcb78ce7df315911219258bc2132f8c_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client - participant Server as NETCONF Server/(O-RU) - Note right of Client: NETCONF session established - Client->>Server: [1] \\active-alarm-list\\ - Server-->>Client: [2] \active-alarm-list\\ - -``` - -Sequence diagram illustrating the 'Read Active Alarms' operation. It shows a NETCONF Client sending a RPC for 'active-alarm-list' to a NETCONF Server/(O-RU), which responds with a containing the 'active-alarm-list' data. A note indicates the session is established before the request. - -Figure 11.1-1: Read Active Alarms - -## 11.2 Alarm notification - -The O-RU shall send `` to a subscriber when the NETCONF Client has established a subscription to alarm notification and: - -- a new alarm is added to active-alarm-list; -- an alarm is removed from the list. - -Removal of alarms from the **active-alarm-list** due to deletion of "fault-source" element is considered as clearing and cause sending of `` to the notification subscriber. This applies to alarms which were explicitly related to the deleted "fault-source" element. The rationale for such is to avoid misalignment between NETCONF Clients when one NETCONF Client deletes an element. - -The O-RU reports in `` only for new active or cancelled alarms, not all active alarms, as illustrated in Figure 11.2-1. - -![Diagram of Alarm Notification flow. It shows two instances of 'O-RU/ (NETCONF Server) (Event-Producer - optional)' and two 'Configured Subscriber' boxes. A yellow callout box indicates that the O-RU detects a state change in an alarm. A dashed red arrow points from the top O-RU to the bottom-right Configured Subscriber, carrying an XML notification: [1] .. .](cf03eff1218a8cc1be6b05de892162de_img.jpg) - -Diagram of Alarm Notification flow. It shows two instances of 'O-RU/ (NETCONF Server) (Event-Producer - optional)' and two 'Configured Subscriber' boxes. A yellow callout box indicates that the O-RU detects a state change in an alarm. A dashed red arrow points from the top O-RU to the bottom-right Configured Subscriber, carrying an XML notification: [1] .. . - -Figure 11.2-1: Alarm Notification - -### 11.3 Manage alarm subscription to NETCONF clients - -The NETCONF Client can "subscribe" to alarm notifications by sending **create-subscription**, as specified in clause 2.1 of RFC 5277 [21], to NETCONF Server. - -RFC 5277 [21] allows below: - -``` - - - - - fault - critical - - - fault - major - - - fault - minor - - - - -``` - -``` - - - - - - - -``` - -NOTE: The NETCONF Client can define the filter for alarm notification base on severity. - -The appropriate example for O-RAN YANG modules for **create-subscription** is as follows: - -- Case 1) NETCONF client subscribes **alarm-notif** filtering **fault-severity**: CRITICAL, MAJOR and MINOR and **measurement-result-stats** filtering **transceiver-stats** and **rx-window-stats** which **measurement-object** is RX\_ON\_TIME only: - -``` - - - - - - - - - - CRITICAL - - - - - - MAJOR - - - - - - MINOR - - - - - - - - - - - - - - RX_ON_TIME - - - - - - - - - - - -``` - -Case 2) NETCONF client subscribes default event stream NETCONF to receive all notifications defined in O-RAN YANG modules: - -``` - - - - - - NETCONF - - - - - -``` - -A high-level view of a NETCONF Client subscribing is shown in Figure 11.3-1. After the NETCONF Client requests a subscription, the server sends an alarm-notif notification to the client when there is any change in the active alarms matching the filter specified in the subscription request. - -![Sequence diagram for Figure 11.3-1: Manage Alarm Notification Subscription Request. It shows a NETCONF Client sending a create-subscription RPC to a NETCONF Server/(O-RU). The server retrieves active alarms and returns an rpc-reply.](3334fcca5dac808f4fd3840aba35bc2e_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client - participant Server as NETCONF Server/(O-RU) - Client->>Server: [1]



- Note left of Server: Retrieves active alarms
corresponding to the
filter settings - Server->>Client: [2] - -``` - -Sequence diagram for Figure 11.3-1: Manage Alarm Notification Subscription Request. It shows a NETCONF Client sending a create-subscription RPC to a NETCONF Server/(O-RU). The server retrieves active alarms and returns an rpc-reply. - -**Figure 11.3-1: Manage Alarm Notification Subscription Request** - -To terminate the subscription, the NETCONF client shall send a `` operation from the subscription's session, as illustrated in Figure 11.3-2. - -![Sequence diagram for Figure 11.3-2: Manage Alarm Notification Subscription Termination. It shows a NETCONF Client sending a close-session RPC to a NETCONF Server/(O-RU).](5efe6377e22b9ab76a19a70da29976b9_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client - participant Server as NETCONF Server/(O-RU) - Client->>Server: [1]

subscribed alarm-notif to be closed

- Note left of Server: notification is terminated. - Server->>Client: [2]
- -``` - -Sequence diagram for Figure 11.3-2: Manage Alarm Notification Subscription Termination. It shows a NETCONF Client sending a close-session RPC to a NETCONF Server/(O-RU). - -**Figure 11.3-2: Terminating an Alarm Notification Subscription** - -## 11.4 Fault sources - -Alarm notifications reported by NETCONF Server contain element "fault-source" which indicates the origin of an alarm. In general values of "fault-source" are derived from names defined as YANG leafs: - -- Source (Examples: fan, module, PA, port) -indicates that origin of the alarm within the O-RU. Value of "fault-source" is derived from element name. -- Source (other than when an element is within the O-RU) - -Value of fault-source may identify the O-RU external resource; for example, antenna line. - -Alarm instance can be identified by value combination of **fault-id**, **fault-source** and **fault-severity**. Alarms with different "fault-id", "fault-source" or "fault-severity" are independent: - -- Multiple alarms with same "fault-id" may be reported with different "fault-source". -- Multiple alarms with same "fault-source" may be reported with different "fault-id". -- Among alarms with same value of **fault-id** and **fault-source** and different value of **fault-severity**, only one of them can be in the **active-alarm-list** at a given time. When an alarm with a "fault-id" and a "fault-source" is reported with a "fault-severity", and there is already an alarm in the **active-alarm-list** with same **fault-id**, **fault-source** value, but with a different **fault-severity**, NETCONF server shall simultaneously add the alarm with new **fault-severity** in **active-alarm-list** and clear the previous alarm with different **fault-severity** by setting **is-cleared** to TRUE and shall remove the alarm with previous **fault-severity** from the **active-alarm-list**. NETCONF server shall notify subscribers of added and removed alarms. - -The range of "fault-id" is separated to common and vendor specific. The common fault-ids are defined in clause A and more numbers may be used in future. The vendor specific range for the fault-id shall be [1000 .. 65535]. - -Alarm notifications reported by the NETCONF Server contain names of the "affected-objects" which indicate elements affected by the fault. In case the origin of the alarm is within the O-RU, other elements than "fault-source" which do not function correctly due to the fault are reported via "affected-objects". In case the origin of the fault is outside of the O-RU, the O-RU elements which do not function correctly due to the fault are reported via "affected-objects". - -## 11.5 Manage alarm notification to event-collector - -This optional capability requires the O-RU to support configured subscriptions, as described in Clause 18. For details for alarm subscription and notification sending to event-collector, refer to Clause 18. - -## 11.6 Historical Alarms List - -The O-RU may optionally support the **historical-alarm-list** container, enabling alarm events with **is-cleared** status is "true" to be captured. The procedures for aging out entries in the **historical-alarms** list based on time and/or memory is left to vendor specific implementation of the O-RU. - -NOTE: The persistence of **historical-alarms** list entries on O-RU upon reset is left to vendor specific implementation - -The NETCONF Client can read **historical-alarm-list** by **get** RPC operation, as illustrated in Figure 11.6-1. - -![Sequence diagram illustrating the read historical alarms operation. It shows a NETCONF Client sending a 'get' RPC for 'historical-alarm-list' to a NETCONF Server/(O-RU), which responds with an 'rpc-reply' containing the data. A note indicates the session is established.](93bd00a00fa28558486f0664550699b1_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client - participant Server as NETCONF Server/(O-RU) - Note right of Client: NETCONF session established - Client->>Server: [1] historical-alarm-list - Server-->>Client: [2] historical-alarm-list - -``` - -Sequence diagram illustrating the read historical alarms operation. It shows a NETCONF Client sending a 'get' RPC for 'historical-alarm-list' to a NETCONF Server/(O-RU), which responds with an 'rpc-reply' containing the data. A note indicates the session is established. - -Figure 11.6-1: Read Historical Alarms - -In case of multiple NETCONF clients and/or Event-Collectors, the O-RU shall report the same notification to all subscribed NETCONF clients/Event-Collectors. - -## 12 File management - -### 12.1 Introduction - -This clause specifies File Management for the O-RU. Following operations are supported as a File Management. - -- upload (see clause 12.3) - -File upload from O-RU to file server triggered by O-RU Controller. - -- retrieve file list (see clause 12.4) - -O-RU Controller retrieves the file list in O-RU. - -- download (see clause 12.5) - -File download from file server to O-RU triggered by O-RU Controller - -NOTE 1: file-download has different purpose with software-download specified in clause 8.5. For example, file-download can be used for Beamforming configuration in clause 15.4. - -File transfers are done with sFTP or FTPES. Following types of authentications shall be supported for **file management**: - -- a) Password for RU authentication and list of public keys (see clause 5.4 in the present document) for sFTP server authentication. -- b) X.509 Certificate for TLS between O-RU and FTPES file server. In addition to the X.509 certificate, the O-RU shall use any configured application password, **appl-password**, to authenticate to the FTPES server for the associated username defined in the **remote-file-path**. - -NOTE 2: The **appl-password** is optional for FTPES server authentication to support scenarios where the username embedded in the **remote-file-path** corresponds to an anonymous account as defined in RFC 1635 [i.5]. - -Following types of authentications may be supported for **file management**: - -- c) Certificate for both O-RU and sFTP server authentication. - -Following other clauses are related with File Management: - -- clause 10.3.2: File management process (can be used for on demand file upload purpose, since clause 10.3.2 covers periodic file upload). -- clause 14.2: Log management. -- clause 14.3: Trace. -- clause 15.4.3: Beamforming configuration update. - -NOTE 3: The file management functions involve the O-RU controller subscribing to receive particular YANG notifications from the O-RU. All O-RUs support the NETCONF Create-Subscription method, enabling those notifications to be transported using NETCONF notifications. In addition, those O-RUs that support the optional NON-PERSISTENT-MPLANE feature, the O-RU Controller can create a configured subscription from the O-RU, enabling those notifications to be transported over HTTPS to an Event-Collector as described in clause 18. - -## 12.2 File system structure - -The file System structure of the O-RU is represented as a logical structure that is used by the file management procedures defined in the rest of this clause. If the O-RU's physical file structure differs from the logical file structure defined below, the O-RU performs the mapping between the two structures. - -The O-RU shall support the standardised logical folders. Prior to version 10.0, the following standardised folders were defined: - -- O-RAN/log/ -- O-RAN/PM/ -- O-RAN/transceiver/ - -And for those O-RU's supporting beamforming - -- O-RAN/beamforming/ - -The folders listed above are inconsistent with the folders used in figures elsewhere in the present document. Because of such inconsistencies, the use of the folders listed above is not preferred. These folders may be subject to removal in a future version of the present document. - -To avoid interoperability issues between case-sensitive and non-case sensitive file systems, the following additional standardised folders are defined and are preferred in the present document: - -- o-ran/log/ - used to store troubleshooting and trace logs -- o-ran/pm/ - used to store performance measurement files -- o-ran/transceiver/ - used to store data recovered from the transceiver module - -and for those O-RUs supporting beamforming: - -- o-ran/beamforming/ - used to store beamforming configuration files - -and for those O-RUs supporting O-RAN defined security logging: - -- o-ran/security/ - used to store security log files - -The O-RU may additionally support vendor defined folders which are out of scope of the present document. - -Versions of the present document prior to v17.0 did not define the standardised folder "o-ran/security/" and consequently O-RUs compliant to versions earlier than v17.0 should use vendor defined folders for supporting security logging functionality. - -## 12.3 File management operation: upload - -This clause describes file upload method from O-RU to the fileserver. sFTP or FTPES is used for File management, and one file can be uploaded by one upload operation. The O-RU Controller triggers file upload operation to O-RU. - -Simultaneous multiple file upload operations can be supported under the same FTP connection between O-RU to the fileserver. If the O-RU has a limitation with regard to the ability to upload files simultaneously, it is allowed that O-RU reports failure notification for the simultaneous upload request which exceeds its capability. The behaviour of O-RU Controller is out of scope when O-RU Controller receives failure notification from the O-RU. - -Following rpc is used for upload operation. - -- rpc: file-upload - - input - - **local-logical-file-path**: the logical path of file to be uploaded (no wildcard is allowed) - - **remote-file-path**: URI of file on the fileserver - - **credentials**: authentication credentials for file server access - - **application-layer-credential**: application layer level authentication credentials for file server access - - output - - **status**: whether O-RU accepted or rejected the upload request - - **reject-reason**: the human readable reason why O-RU rejects the request (only applicable if status is rejected) - -In the rpc-reply, status whether the O-RU receives the upload request or rejects due to some reason (e.g. the number of limitation to upload simultaneously) is replied. If rejected, the human readable reject reason is also replied. - -In notification, the result of the upload process (successfully uploaded or failed upload) is replied in addition to local-logical-file-path and remote-file-path. If failure, the human readable reason is also replied. Figure 12.3-1 shows the file upload sequence diagram. - -![Sequence diagram for File Upload Sequence showing interaction between O-RU and O-RU Controller.](1684f5f8c34bd0ef6e933664d88b9d86_img.jpg) - -``` - -sequenceDiagram - participant Server as NETCONF Server/ Notification producer/ (O-RU) - participant Client as NETCONF Client/ Notification Subscriber/ (O-RU Controller) - Client->>Server: [1] .. - Server-->>Client: [2] .. - Note right of Client: Waits for the notification from O-RU about the completion of the upload - Note left of Server: O-RU Completes upload operation - Server->>Client: [3] .. - -``` - -Sequence diagram for File Upload Sequence showing interaction between O-RU and O-RU Controller. - -Figure 12.3-1: File Upload Sequence - -## 12.4 File management operation: retrieve file list - -This clause describes file retrieve method which the O-RU Controller retrieves the file list from the O-RU. One or multiple files' information can be retrieved by one retrieve file list operation (use of wildcard is allowed). The O-RU Controller triggers the retrieve file list operation from the O-RU. - -The following rpc is used for retrieve file list operation. - -rpc: **retrieve-file-list** - -- input - - logical path: the logical path of files to be retrieved (\* is allowed as wild-card) - - file-name-filter: the files which has the "file name filter" in the file name (\* is allowed as wild-card) -- output - - status: whether O-RU accepted or rejected the retrieve file list request - - reject-reason: the human readable reason why O-RU rejects the request (only applicable if status is rejected) - - file list - -In rpc-reply, status whether the O-RU accepts the retrieve-file-list request or rejects due to some reason is replied. If rejected, the human readable reject reason is also replied. - -Figure 12.4-1 shows the retrieve file list sequence diagram. - -![Sequence diagram for Retrieve File List operation. It shows two pairs of NETCONF Server/Client. The top pair consists of a NETCONF Server (O-RU) and a NETCONF Client (O-RU Controller). The bottom pair also consists of a NETCONF Server (O-RU) and a NETCONF Client (O-RU Controller). The sequence is: 1. The top Client sends an [1].. message to the top Server. 2. The top Server sends a response [2].. to the top Client. 3. The top Client then sends the same [1].. message to the bottom Server. 4. The bottom Server sends a response [2].. to the bottom Client.](ecae674475cecdd0962200a5d1e2591e_img.jpg) - -Sequence diagram for Retrieve File List operation. It shows two pairs of NETCONF Server/Client. The top pair consists of a NETCONF Server (O-RU) and a NETCONF Client (O-RU Controller). The bottom pair also consists of a NETCONF Server (O-RU) and a NETCONF Client (O-RU Controller). The sequence is: 1. The top Client sends an [1].. message to the top Server. 2. The top Server sends a response [2].. to the top Client. 3. The top Client then sends the same [1].. message to the bottom Server. 4. The bottom Server sends a response [2].. to the bottom Client. - -Figure 12.4-1: Retrieve File List Sequence - -## 12.5 File management operation: download - -This clause describes the file download method from O-RU Controller to O-RU. sFTP or FTPES is used for File management, and one file can be downloaded by one download operation. O-RU Controller triggers the file download operation to O-RU. - -Simultaneous multiple file download operations can be supported under the same FTP connection between the O-RU and O-DU/SMO. If the O-RU has the number of limitation to download simultaneously as a capability, it is allowed that the O-RU reports a failure notification for the download request which is larger than the capability. The behaviour of the O-RU Controller is out of scope when O-DU/SMO receives failure notification from O-RU. - -The following rpc is used for download operation. - -rpc: **file-download** - -- input - - local-logical-file-path: the logical path of file to be downloaded (no wildcard is allowed) - - remote-file-path: URI of file on the file server - - **credentials**: authentication credentials for file server access - - **application-layer-credential**: application layer level authentication credentials for file server access -- output - - status: whether O-RU accepted or rejected the download request - - reject-reason: the human readable reason why O-RU rejects the request (only applicable if status is rejected) - -The O-RU shall reject any **file-download** rpc where the **local-logical-file-path** starts with "o-ran/log/", "o-ran/pm/", "o-ran/transceiver/" or "o-ran/security/". - -In rpc-reply, status whether the O-RU receives the download request or rejects due to some reason (e.g. the number of limitation to download simultaneously) is replied. If rejected, the human readable reject reason is also replied. - -In notification, the result of the download process (successfully downloaded or download is failure) is replied in addition to the local-logical-file-path and remote-file-path. If failure, the human readable reason is also replied. Figure 12.5-1 below shows the file download sequence diagram. - -![Sequence diagram for File Download. Lifelines: NETCONF Server/Notification Producer (O-RU) and NETCONF Client/Notification Subscriber (O-RU Controller). The sequence starts with an ... message from the Client to the Server. The Server responds with an ... message. The Server then completes the download operation. Finally, the Server sends a ... message to the Client. A note indicates the Client 'Waits for the notification from O-RU about the completion of the download' between the reply and the notification.](b02ba0b73e95416eb547976f6145b169_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client/Notification Subscriber (O-RU Controller) - participant Server as NETCONF Server/Notification Producer (O-RU) - Note right of Client: Waits for the notification from O-RU about the completion of the download - Note left of Server: O-RU Completes download operation - Client->>Server: [1] ... - Server-->>Client: [2] ... - Note left of Server: O-RU Completes download operation - Server-->>Client: [3] ... - -``` - -Sequence diagram for File Download. Lifelines: NETCONF Server/Notification Producer (O-RU) and NETCONF Client/Notification Subscriber (O-RU Controller). The sequence starts with an ... message from the Client to the Server. The Server responds with an ... message. The Server then completes the download operation. Finally, the Server sends a ... message to the Client. A note indicates the Client 'Waits for the notification from O-RU about the completion of the download' between the reply and the notification. - -Figure 12.5-1: File Download Sequence - -## 13 Synchronisation aspects - -### 13.1 Introduction - -This clause describes the YANG model (**o-ran-sync.yang**) containers that are used for the Management Plane's interactions with various aspects of the time synchronisation of the O-RU. In general, the O-RU shall manage its synchronisation status and select one or more synchronisation input source(s) (based on vendor specific implementation). Additional information regarding the interactions between M-Plane and S-Plane are described in the current specification's clause 15.3.3 and in the CUS-Plane specification [2], clause 11.4. - -The **o-ran-sync.yang** YANG model defines configuration, status and notification containers which are used to enable O-RU controller to recover the state of the O-RU's S-Plane. Before going into the details of each of these an overview of these objects is provided here. - -The YANG model defines several configuration containers. These containers comprise read/write parameters that can be read or set by the O-RU controller. The O-RU controller can read them (to determine O-RU configuration) or set them (to change the O-RU's configuration). These are: - -- PTP Configuration - **ptp-config**: O-RU controller can set or read PTP parameters like PTP Full/Partial timing support profiles, accepted clock classes, and set network address among other parameters - -- PLFS/SyncE Configuration - **sync-config**: This container provides SyncE information such as the acceptable list of SSMs. -- GNSS (Global Network Satellite System) Configuration - **gnss-config**: This container comprises leaves which define whether GNSS can be used, and if so which satellite constellation to use. -- Sync Capability - **sync-capability**: This is a read-only container indicates to the O-RU controller the time accuracy of the T-TSC or T-BC that is integrated into the O-RU. - -The O-RU should store the above synchronisation configuration in reset persistent memory. - -During the start -up installation process (see clause 6.1) the O-RU's default startup configuration settings may allow the O-RU's S-Plane to become operational without any configuration by the O-RU controller. The O-RU uses its default configuration settings to execute the PTP and/or PLFS/SyncE protocols, or GNSS settings to complete the synchronisation process (including optional features such as PER-PORT-PTP-CONFIG, PER-PORT-SYNC-CONFIG, GNSS, ANTI-JAM). During the start-up installation flow the startup settings may be changed. This may be necessary if the default synchronisation settings are incompatible with the network implementation. If the startup configuration requires changes, the O-RU controller first retrieves the synchronisation configuration and status from O-RU, and then the O-RU controller modifies the configuration. The O-RU shall then execute the synchronisation process using the updated settings. Having these settings stored in reset persistent memory typically simplifies subsequent startup flows by enabling O-RU to start up without reconfiguration. - -Once the O-RU is operational, the O-RU controller can subscribe to several synchronisation notifications which report to the O-RU controller the status of the O-RU. The following notifications are defined in the YANG model. - -- **synchronization-state-change** - conveys the **sync-state**. -- **ptp-state-change** - conveys the **ptp-status**. -- **sync-state-change** - If SyncE or another PLFS is used, this conveys the **sync-status** -- **gnss-state-change** - If a O-RU supports GNSS capability, this conveys the **gnss-status**. - -During normal operation, the O-DU should monitor the operational state of the O-RU's S-Plane. This is accomplished by subscribing to receive the **synchronization-state-change** notification. If the O-DU is notified that the O-RU's state has changed to UNLOCKED, the O-DU shall stop sending data to the O-RU and shall ignore any data from that O-RU. Clause 15.3.3 describes in more detail the interactions between S-Plane and M-Plane when synchronisation is lost and when synchronisation is recovered. - -NOTE: Except for possible configuration during the start-up installation process, the synchronisation start-up and reference clock selection are accomplished via S-Plane protocols independent of M-Plane. - -The remainder of this clause describes in more detail the main objects within the configuration, status, and notification containers. However, this clause does not describe all of the leaves/objects within the containers. Some items for example **time-error**, **frequency-error**, **supported-reference-types** are not mentioned in this clause, but are defined and described in o-ran-sync.yang. - -## 13.2 Sync status object - -This **sync-state** container provides synchronisation state of the module. If the O-RU Controller is interested in receiving Synchronization status state information, it may configure a subscription to the **synchronization-state-change** notification from the O-RU. Event notifications will be sent whenever the state of the O-RU synchronisation changes. - -For an O-DU that is communicating with an O-RU, the **synchronization-state-change** notification is the primary mechanism by which the O-DU knows whether the O-RU is synchronised and is ready to transmit/receive when fully - -configured. This notification is the primary mechanism to transfer status information required to implement the flows described in clause 15.3.3. - -The state diagram of O-RU synchronisation is shown in Figure 13.2-1, and is indicated by the following allowed values: - -- **LOCKED:** O-RU is in the locked mode, as defined in Recommendation ITU-T G.810 [23]. -- **HOLDOVER:** O-RU clock is in holdover mode. -- **FREE RUN:** O-RU clock is not locked to an input reference and is not in the holdover mode. - -Figure 13.2-1 illustrated the state transitions. - -The **sync-state** container allows the O-RU to list via an array of the synchronisation sources, called **supported-reference-types**, which it can support. The allowed values are: - -- GNSS -- PTP -- SYNCE - -![State diagram showing transitions between sync_FREERUN, sync_LOCKED, and sync_HOLDOVER states.](82626dc3515144bcff1786f5764fc4c2_img.jpg) - -``` - -stateDiagram-v2 - [*] --> sync_FREERUN : startup - sync_FREERUN --> sync_LOCKED : external sync established - sync_LOCKED --> sync_FREERUN : external sync lost (without HOLDOVER mode) - sync_LOCKED --> sync_HOLDOVER : external sync lost - sync_HOLDOVER --> sync_LOCKED : external sync restored - sync_HOLDOVER --> sync_FREERUN : holdover mode expired - style sync_FREERUN fill:#ffff00,stroke:#ff0000 - style sync_LOCKED fill:#ffff00,stroke:#ff0000 - style sync_HOLDOVER fill:#cccccc,stroke:#ff0000 - -``` - -State diagram showing transitions between sync\_FREERUN, sync\_LOCKED, and sync\_HOLDOVER states. - -NOTE: HOLDOVER mode is optional and depends on internal O-RU design. - -**Figure 13.2-1: Allowed sync state transitions** - -## 13.3 Sync capability object - -The module's synchronisation capability is provided via the sync-t-tsc object. This object indicates the accuracy of the O-RU's derived Telecom Subordinate Clock (T-TSC). For details on the actual capability levels, see clause 11.3 of the O-RAN WG4 CUS plane specification [2]. There are two enumerations possible: - -- CLASS\_B: Regular accuracy (previously referred to class B) for synchronisation is supported by the device as per IEEE 802.1CM [80] clause 6.4.1, Case 1.1. -- ENHANCED: Enhanced accuracy for synchronisation is supported by the device as per IEEE802.1CM [80] clause 6.4.1, Case 1.2. - -Other leaves in this container include: - -- a Boolean called **boundary-clock-supported**, which indicates whether the O-RU supports T-BC profiles defined in ITU-T 8275.1 [22]. -- a Boolean called **extended-ql-tlv-supported**, which indicates whether the O-RU supports the extended Quality Level TLV defined in ITU-T 8264 [76] clause 11.3. - -## 13.4 PTP configuration - -### 13.4.1 Introduction - -The **ptp-config** container contains information about the O-RU's configuration of Precision Time Protocol. This clause describes the definitions of the items contained within **ptp-config**. - -**domain-number:** This parameter indicates the Domain Number for PTP announce messages. Allowed values: 0 ~ 255. - -- Recommendation ITU-T G.8275.1 [22] uses domain numbers in the range 24..43, but the entire range is allowed to ensure flexibility of the M-Plane specification. For Recommendation ITU-T G.8275.2 domain numbers from range 44..63 shall be used. - -default: 24. - -**accepted-clock-classes:** Contains the list of PTP acceptable Clock Classes, sorted in the descending order. - -- The sender shall generate the list of acceptable clock classes. The list shall be sorted in descending order. Each accepted Clock Class value shall appear only once in the list. Depending on implementation, the receiver may interpret the list in either of two ways: - - a) use only the first (i.e. the maximum) item in the list, interpreting it as a threshold value for acceptable clock classes, while ignoring all other items in the list; - - b) use the whole list, interpreting it as an explicit list of acceptable clock classes. - -default: 7, 6 - -**clock-classes:** The PTP Clock Class accepted by the O-RU. Allowed values: 0 ~ 255. - -- Not all values are compliant to [22], but the entire range is allowed in M-plane specification to ensure flexibility. The values can be validated/filtered on the receiver side, if necessary. - -**ptp-profile:** Defines which PTP profile will be used. - -Allowed values: - -- G\_8275\_1 (multicast over Ethernet will be used, see Recommendation ITU-T G.8275.1 [22]) -- G\_8275\_2 (unicast over IP will be used, see Recommendation ITU-T G.8275.2) - -default: G\_8275\_1. - -**delay-asymmetry:** Defines the static phase error in the recovered PTP timing signal to be compensated at the O-RU. The error is defined in units of nanoseconds in the range $\pm 10\,000$ ns. This is a single global value that is common for all the O-RU's ports. As specified in Recommendation ITU-T G.810 [23] and IEEE1588 [24] and [50], the sign of the parameter shall be interpreted as follows: - -- If the phase error to be compensated is negative, then the recovered timing signal shall be advanced by the time interval equal to the configured value to compensate the error. -- If the phase error to be compensated is positive, then the recovered timing signal shall be delayed by the time interval equal to the configured value to compensate the error. - -default: 0 - -Modification of this parameter may have impact on RF transmission but shall occur without unit restart. - -This parameter is optional for support. If the O-RU does not support this value, the O-RU shall use the default value. If the O-RU does not support manual compensation, it shall ignore the parameter setting. - -Granularity of the applied value depends on the architecture and implementation of the system clock, and therefore, may vary across vendors. - -## 13.4.2 G.8275.1 specific parameters - -This container within **ptp-config**, called **g-8275-1-config**, is used when **ptp-profile** is set to G\_8275\_1. When enabled it instantiates **multicast-mac-address**. The parameter defines the destination MAC address, used by the O-RU in the egress PTP messages. This is a common configuration parameter for all G.8275.1 compliant ports of the O-RU. - -Allowed values: - -- FORWARDABLE (means that PTP shall use 01-1B-19-00-00-00 destination MAC address) -- NONFORWARDABLE (means that PTP shall use 01-80-C2-00-00-0E destination MAC address) - -default: FORWARDABLE. - -**sources:** When **PER-PORT-PTP-CONFIG** optional feature is supported, this parameter contains several ITU-T G.8275.1-specific configuration parameters determining optional attributes for each of the physical ports defined by **local-port-number**. Descriptions for these can be found in o-ran-sync.yang. - -- **time-transmitter-only:** (default : FALSE) - -When set to TRUE, this optional parameter forces all PTP ports assigned to the physical port to act only as a TimeTransmitter one, i.e. they cannot be selected as time source for the O-RU. When set to FALSE, the O-RU can determine the port state without this restriction. - -- **not-time-transmitter:** (default : FALSE) - -When set to TRUE, this optional parameter prevents all PTP ports assigned to the physical port from acting as a TimeTransmitter one, i.e. they cannot deliver time from the O-RU. When set to FALSE, the O-RU can determine the port state without this restriction. - -- **local-priority:** (default : 128) - -This optional parameter allows configuring a common local priority for all PTP ports assigned to the physical port, used in the ITU-T G.8275.1 best PTP source selection (ABTCA). The lower the value, the higher the priority. - -**time-transmitter-only** and **not-time-transmitter** shall not be set to TRUE simultaneously. - -### 13.4.3 G.8275.2 specific parameters - -This container, **g-8275-2-config**, within **ptp-config** contains G.8275.2 specific parameters. It is used with **ptp-profile** is set to G\_8275\_2. The full list of fields within this container and their meaning are listed directly in the YANG model. - -**local-ip-port:** The parameter defines local IP address which will be used as a port for receiving ptp signal. - -**master-ip-configuration:** The parameter defines list of IP configuration of devices acting as PTP signal source. - -**local-priority:** The parameter defines local priority or underlying master IP address. - -**ip-address:** This parameter defines master IP address. - -**log-inter-sync-period:** The parameter defines number of sync message during 1 second. - -Allowed values: 0 ~ -7 (this represents the value from 1 message per second to 128 messages per second). - -**log-inter-announce-period:** The parameter defines number of announce message during 1 second - -Allowed values: 0 ~ -3 (this represents the value from 1 message per second to 8 messages per second). - -## 13.5 PTP status - -The PTP Status container is used to collect operational status information of the PTP clock, controlled by the O-RU. The object may be used to display operational information, which facilitates troubleshooting, to the operator. The information in the object shall not be used by the O-DU to autonomously alter its operation. If the O-RU Controller is interested in PTP status, it may configure a subscription to the **ptp-state-change** notification in the O-RU. Notifications will only indicate changes to the lock-state. Before requesting or subscribing to PTP status information, the O-RU Controller shall ensure that PTP is supported by the O-RU by requesting the **supported-reference-types**, as defined in clause 13.2. The following list includes the related parameters of this container. - -**reporting-period:** This parameter defines minimum period in seconds between reports, sent by the O-RU, for parameters in this container. - -default: 10 - -**lock-state:** This parameter indicates whether the integrated clock is synchronising to the reference, recovered from PTP flow. The exact definition when to indicate locked or unlocked is up to specific implementation. - -- **LOCKED:** The integrated clock is synchronising to the reference, recovered from PTP flow. -- **UNLOCKED:** The integrated clock is not synchronising to the reference, recovered from PTP flow. - -**clock-class:** This parameter contains the clock class of the clock, controlled by the O-RU. - -**sources:** This parameter contains several parameters describing the characteristics of PTP sources of the clock, controlled by the O-RU. Descriptions for these can be found in o-ran-sync.yang. - -**state:** This parameter indicates status of the PTP port: - -- **PARENT:** Indicates that the PTP signal from this source is currently used as a synchronisation reference. - -- **OK:** Indicates that the PTP signal from this source can be potentially used as a synchronisation reference, i.e. Announce messages, received from this source, contain acceptable content (**domain-number**, **clock-class**, flags, etc). -- **NOK:** Indicates that the PTP signal from this source cannot be used as a synchronisation reference, i.e. Announce messages, received from this source, contain unacceptable content (domain number, clockclass, flags, etc). -- **DISABLED:** Indicates that PTP connection is not available from this PTP source. - -See the related o-ran-sync YANG Model for additional information on the contents of the ptp-status container. - -## 13.6 PLFS/SyncE configuration - -The CUS-Plane Specification allows for different methods of PLFS (Physical Layer Frequency Synchronisation), however only the use of SyncE is defined in the present document. The **syncE-config** container defines the configuration of SyncE. The following list includes the related parameters of this container. - -**acceptance-list-of-ssm:** The parameter contains the list of SyncE acceptable Synchronisation Status Messages (SSM). - -Allowed values: - -- ePRTC (enhanced Primary Reference Time Clock, note 2) -- PRTC (Primary Reference Time Clock, note 2) -- ePRC (enhanced Primary Reference Clock, note 2) -- PRC (Primary Reference Clock) -- PRS (Primary Reference Source-Stratum 1) -- SSU\_A (Synchronization Supply Unit A) -- SSU\_B (Synchronization Supply Unit B) -- ST2 (Stratum 2) -- ST3 (Stratum 3) -- ST3E (Stratum 3E) -- eEEC (enhanced Ethernet Equipment Clock, note 2) -- EEC1 (Ethernet Equipment Clock 1) -- EEC2 (Ethernet Equipment Clock 2) -- DNU (Do Not Use) -- NONE - -NOTE: These values are ignored when extended-ql-tlv-supported capability is FALSE. - -**ssm-timeout:** The parameter contains the value of maximum duration in seconds for which the actual SSM value may be different than configured values. - -**sources:** When **PER-PORT-SYNCE-CONFIG** optional feature is supported, this parameter contains several ITU-T G.781-specific configuration parameters determining more detailed attributes for each of the physical ports defined by **local-port-number**. Descriptions for these can be found in o-ran-sync.yang. - -- ssm-send-enable: (default : FALSE) - -When set to TRUE, this optional parameter allows all SyncE ports assigned to the physical port to send SSM Quality Level, i.e. it can be used to synchronize downstream clocks. When set to FALSE, the O-RU does not send the SSM Quality Level. - -- local-priority: (default : 0) - -This optional parameter allows configuring a common local priority for all SyncE ports assigned to the physical port, used in the Recommendation ITU-T G.781 [81] best SyncE source selection. The lower the value, the higher the priority, except for value 0 that removes the port from the selection process. - -## 13.7 PLFS/SyncE status - -The **sync-status** container is used to collect operational status information of SyncE reference on a node, controlled by O-RU. If the O-RU Controller is interested in SyncE status, it may configure a subscription to the **sync-state-change** notification in the O-RU. Notifications will only indicate changes to the lock-state. Before requesting or subscribing to SyncE status information, the O-RU Controller shall ensure that SyncE is supported at the O-RU by requesting the supported timing reference types, as defined earlier in clause 13.2. The following list summarizes the related parameters of this container. - -**reporting-period:** This parameter defines minimum period in seconds between reports, sent by the O-RU, for parameters in this container. - -default: 10 - -**lock-state:** This parameter indicates whether the integrated ordinary clock is synchronising to the reference, recovered from the SyncE signal. The exact definition when to indicate locked or unlocked is up to specific implementation. - -- LOCKED:** The integrated ordinary clock is synchronising to the reference, recovered from the SyncE signal. -- UNLOCKED:** The integrated ordinary clock is not synchronising to the reference, recovered from the SyncE signal. - -**sources:** This parameter contains characteristics of SyncE sources of the clock, controlled by the NETCONF Server, and reporting optional attributes for each of the physical ports defined by **local-port-number**. Descriptions for these can be found in o-ran-sync.yang. - -**state:** This parameter indicates status of the SyncE source: - -- PARENT:** Indicates that the SyncE signal from this source is currently used as a synchronisation reference. -- OK:** Indicates that the SyncE signal from this source can be potentially used as a synchronisation reference, i.e. SSM messages, received from this source, contain acceptable clock quality level. -- NOK:** Indicates that the SyncE signal from this source cannot be used as a synchronisation reference, i.e. SSM messages, received from this source, contain unacceptable clock quality level. -- DISABLED:** Indicates that SSMs are not received from this SyncE source. - -**quality-level:** This parameter contains value of the SSM clock quality level, received in SSM messages from the SyncE source. Unit is uint8, e.g. PRC SSM QL is reported as 0x02. - -**ssm-quality-level:** this parameter contains human-readable value of the extended clock quality level, received in SSM messages from the SyncE source. Unit is ssm-code enumeration as specified in clause 13.6 of the present document, e.g. ePRC enhanced SSM QL is reported as ePRC. - -The following optional parameters can also be reported if extended-ql-tlv-supported capability is TRUE, as per Recommendation ITU-T G.8264 [76] clause 11.3. They report what is received on the port in SSM messages from the SyncE source: - -- **enhanced-ssm-code:** Unit is uint8, e.g. ePRC enhanced SSM QL is reported as 0x23. -- **originator-sync-e-clock-id:** this parameter contains the clockIdentity of the originator clock. Unit is uint64, e.g. 0x0123456789ABCDEF. -- **flag0-mixed-eec-eeec:** Boolean meaning mixed EEC/eEEC (i.e. TRUE if at least one of the clocks is not an eEEC; FALSE if all clocks are eEEC). -- **flag1-partial-chain:** Boolean meaning means partial chain (i.e. TRUE , if the TLV has been generated in the middle of the chain and the count of the EEC/eEEC is incomplete, FALSE otherwise). -- **number-of-eeec:** the number of cascaded eEECs from the nearest SSU/PRC/ePRC. Unit is uint8. -- **number-of-eec:** the number of cascaded EECs from the nearest SSU/PRC/ePRC. Unit is uint8. - -See the related **o-ran-sync.yang** YANG Model for the full details. - -## 13.8 GNSS configuration - -The **gnss-config** container defines the configuration of Global Navigation Satellite System (GNSS). The following list summarizes the related parameters of this container. - -**enable:** This parameter defines if GNSS receiver shall be enabled or not. Allowed values: true/false; - -default: false - -**satellite-constellation-list (sic):** This parameter defines list of constellations to be used to acquire synchronisation. - -Allowed values: - -- GPS -- GLONASS -- GALILEO -- BEIDOU - -**polarity:** This parameter defines pulse polarity. - -Allowed values: - -- POSITIVE -- NEGATIVE - -default: POSITIVE - -**cable-delay:** This parameter is used to compensate cable delay. Allowed values: 0 ~ 1000. - -default: 5 - -NOTE: This value is given in ns (nanoseconds) it is recommended to compensate 5ns per each meter of the cable. - -**anti-jam-enable {if feature GNSS-ANTI-JAM}**: This parameter is used to enable or disable anti-jamming. Allowed values: true/false. - -default: false. - -## 13.9 GNSS status - -An O-RU supporting GNSS capability shall use the **gnss-status** container to report the state of its GNSS receiver. If the O-RU Controller is interested in GNSS status, it may configure a subscription to the **gnss-state-change** notification in the O-RU before requesting or subscribing the GNSS status information. Notifications will only provide changes to the **gnss-status**. The O-RU Controller shall ensure that GNSS is supported by the O-RU by requesting supported timing reference types, as defined in clause 13.2. The following list summarizes the related parameters of this container. - -**gnss-status**: This parameter indicates the status of the GNSS receiver: - -- **SYNCHRONIZED**: Indicates that the GNSS receiver is synchronised. -- **ACQUIRING-SYNC**: Indicates the GNSS receiver is functioning correctly, but has not acquired synchronisation -- **ANTENNA-DISCONNECTED**: Indicates the GNSS receiver is reporting that its antenna is disconnected. -- **BOOTING**: Indicates that the GNSS functionality is booting. -- **ANTENNA-SHORT-CIRCUIT**: Indicates that the GNSS receiver is reporting that its antenna is short circuited. - -Additionally, when the GNSS receiver is synchronised, the O-RU can report the following additional information: - -- **satellites-tracked**: The number of satellites being tracked by the O-RU receiver. -- **altitude, latitude and longitude**: The geospatial location reported by the GNSS receiver. - ---- - -## 14 Operations use cases - -### 14.1 Supervision failure handling and supervision termination handling - -#### 14.1.1 Supervision failure handling - -This clause clarifies Supervision Failure Handling and Supervision Termination Handling. - -When Supervision Failure is detected by O-RU, the O-RU shall immediately disable operation of the watchdog timers for the corresponding NETCONF session. O-RU assumes NETCONF session related to failed supervision is no longer valid. O-RU shall terminate this invalid NETCONF session by closing underlying SSH or TLS connection. Then O-RU shall start performing the call home procedure towards the NETCONF client, using the **re-call-home-no-ssh-timer** to repeat the call home attempts. This activity is repeated by the O-RU until, either: - -- 1) A new NETCONF session is established with the original NETCONF client. - -Or, - -- 2) the original NETCONF client is no longer a "call home O-RU Controller" as defined in clause 6.3, e.g. when reperforming DHCP configuration, the O-RU Controller identity corresponding to the NETCONF client is no longer signalled by the DHCP server, and/or the NETCONF client was previously configured using the **configured-client-info** container and this configuration has been deleted. - -Or, - -- 3) After **max-call-home-attempts** has been reached and a new NETCONF session cannot be established with the original NETCONF client. - -Scenario 2 and 3 result in one of the two described cases: - -- Case #1:** The O-RU is still having at least one running and valid NETCONF session with a NETCONF client that has subscribed to receive the **supervision-notification** and where the **per-odu-monitoring** container is not present in the O-RU's configuration. - -The O-RU remains operational and stops performing call home to this O-RU controller. - -- Case #2:** The O-RU does not have running NETCONF session with any NETCONF client that has subscribed to receive the **supervision-notification**. - -The O-RU ceases all radio transmission and performs autonomous reset. - -When an O-RU indicates it supports the **SHARED-ORU-MULTI-ODU** feature, an O-RU Controller can enable supervision operation on a per O-DU identity basis by configuring one or more **odu-id** parameters in the **per-odu-monitoring** container in o-ran-supervision YANG model. When an **odu-id** has been configured in the **per-odu-monitoring** container, the O-RU shall enable operation of watchdog supervision timers (supervision timer and notification timer) on a per **odu-id** basis. When enabled, an O-RU controller that has subscribed to the **supervision-notification** is expected to configure one of the **odu-id** values in the **supervision-watchdog-reset** rpc. Operation of watchdog supervision timers on a per O-DU identity basis does not obviate the O-RU from performing autonomous reset according to the scenario described in case #2 above. - -NOTE: The format of the **odu-id** string is not defined and not interpreted by the shared O-RU. - -- Case #3:** If the supervision timer associated with an **odu-id** expires, the O-RU shall set the **state** leaf of the following array carriers to **DISABLED** and the **active** leaf of the same carriers to **INACTIVE**: - -- Any **tx-array-carriers** list entry including a list of odu-ids containing only expired **odu-id**. -- Any **rx-array-carriers** list entry including a list of odu-ids containing only expired **odu-id**. - -O-RU shall raise an alarm. The specific alarm #35 "Lost O-DU ID based Supervision " is described in clause A. The O-RU sends **tx-array-carriers-state-change** and **rx-array-carriers-state-change** notifications to any notification subscribers. O-RU shall not perform an autonomous reset unless the requirements described in case #2 are met. - -## 14.1.2 Supervision termination handling - -If NETCONF session used for the supervision subscription is terminated by NETCONF client, the O-RU disables operation of the watchdog timers for terminated NETCONF session and starts performing Call Home procedure towards call home O-RU Controllers, following specification in clause 6.3. - -Before terminating its NETCONF session, a NETCONF client that has subscribed to receive supervision notification, should at least de-activate all carriers previously configured by this NETCONF client. Optionally, such a NETCONF client can also remove (full or partial) configuration applied by this NETCONF client to the O-RU. - -If the **per-odu-monitoring** container is not present in the O-RU's configuration, in case when entering Supervision Termination handling, if the O-RU does not have running NETCONF session with any NETCONF client that has subscribed to receive the **supervision-notification**, the O-RU ceases all radio transmission. - -If the **per-odu-monitoring** container is present in the O-RU's configuration, in case when entering Supervision Termination handling, the O-RU deactivates the array carriers associated with the **odu-id** value in its **supervision-watchdog-reset** rpc as specified in clause 14.1.1. - -## 14.2 Log management - -### 14.2.1 Introduction - -There are three type of log managements, troubleshooting log, security log and trace log. They are independent each other. - -Troubleshooting log file contains the logs continuously collected before rpc. Any logs collected after rpc are not contained. - -Trace log file contains the logs continuously collected after rpc. Any logs collected before rpc are not contained. - -Security log files contain logs of security event information. The creation and storage of security log-data by the O-RU shall always be possible, i.e., there is no O-RAN defined procedure for starting or stopping the logging of security events. An O-RU indicates it supports O-RAN defined security logging procedures by including the SECURITY-LOGGING feature in its YANG library. - -### 14.2.2 Troubleshooting log management - -By requesting trouble shooting log files an O-RU controller is able to obtain collected log data files that can be used for troubleshooting purposes. - -The O-RU can provide all possible troubleshooting log files. The contents and log formats are dependent on O-RU implementation. - -The number and size of files provided by O-RU is not restricted but the O-RU may keep the number and size of files reasonably small to allow completion of the whole "Troubleshooting data upload" scenario (all files) within 15 minutes (with target to complete within 3 minutes) - assuming no additional upload restrictions from connectivity bandwidth or file server implementation. It is also recommended to provide more useful files first. - -NOTE 1: The detailed O-RU controller behaviour is not specified. An O-RU controller can continue the scenario till completion past the allowed time or skip requesting further files - -The files should be compressed with compression method indicated by file name extension: - -- .gz (DEFLATE), -- .lz4 (LZ4), -- .xz (LZMA2 - xz utils), -- .zip (DEFLATE - zlib library). - -O-RU shall collect log information. The RPC shall trigger the O-RU to start generating troubleshooting log files containing troubleshooting logs, as illustrated in Figure 14.2.2-1. Completed generation of files shall be indicated by NETCONF server to NETCONF client in form of a notification. - -If an O-RU reports support for the LOG-FILTER feature, then the O-RU Controller may request selected troubleshooting log data to be generated by providing values in the **filter** list in the RPC . In Troubleshooting Data Upload procedure NETCONF Server provides data, which match the provided filters in the **filter** list. - -NOTE 2: If the **filter-type/value** provided in the **filter** list is not supported by the O-RU, the O-RU can either ignore the **filter-type/value**, or reply with a **status** of FAILURE that indicates the failure reason being the non-support of the **filter-type/value**. - -The notification shall be signalled to the notification subscriber after the O-RU has finished generation of all troubleshooting log files, indicating to the subscriber that the troubleshooting log files are ready to be uploaded. - -![Sequence diagram showing the interaction between a NETCONF Server (O-RU) and a NETCONF Client for starting log generation. The client sends an RPC request, the server collects logs and starts generation, and then returns a success reply.](819f1d00e68b342a246b64fa888a97f9_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client - participant Server as NETCONF Server/(O-RU) - Note left of Server: O-RU collects log information - Note left of Server: Start generation of troubleshooting log files - Client->>Server: [1] - Server-->>Client: [2] -SUCCESS - -``` - -Sequence diagram showing the interaction between a NETCONF Server (O-RU) and a NETCONF Client for starting log generation. The client sends an RPC request, the server collects logs and starts generation, and then returns a success reply. - -**Figure 14.2.2-1: Start Generation of Troubleshooting Log Files** - -The O-RU shall include file names for troubleshooting log files in the notification, with illustrative notification contents shown in Figure 14.2.2-2. - -After sending the notification, the O-RU shall stop generating further troubleshooting log files unless a new RPC is triggered. The file transfer for the generated troubleshooting log files shall be handled by the file management defined in Clause 12. - -![Sequence diagram showing NETCONF Server (O-RU) and Notification Subscriber interaction for troubleshooting logs. The diagram includes an 'alt' block with three options: Prior to present document version 10 - option 1 (not preferred), Prior to present document version 10 - option 2 (not preferred), and Present document (preferred). Each option shows a notification message with event-time and log-file-name details.](3220d3a933797114c1ba20d5c4ec093d_img.jpg) - -The troubleshooting log files are generated. - -**alt** [Prior to present document version 10 - option 1, not preferred] - -``` - - - 2021-12-01T18:08:00.00Z - [1] - O-RAN/log/log0001.zip - - -``` - -**alt** [Prior to present document version 10 - option 2, not preferred] - -``` - - - 2021-12-01T18:08:00.00Z - [2] - log0001.zip - - -``` - -**alt** [Present document, preferred] - -``` - - - 2021-12-01T18:08:00.00Z - [3] - o-ran/log/log0001.zip - - -``` - -Sequence diagram showing NETCONF Server (O-RU) and Notification Subscriber interaction for troubleshooting logs. The diagram includes an 'alt' block with three options: Prior to present document version 10 - option 1 (not preferred), Prior to present document version 10 - option 2 (not preferred), and Present document (preferred). Each option shows a notification message with event-time and log-file-name details. - -**Figure 14.2.2-2: Notification Troubleshooting Log Generated** - -NOTE 3: Prior to version 10 of the present document, this document contained inconsistent definition of the **log-file-name** string between Figure 14.2.2-2 and associated YANG models. In present document previously permitted content of node **log-file-name** is considered as not preferred. Not preferred file formats may be subject to removal in a future version of the present document. - -NETCONF client cancels generation of troubleshooting logs files using RPC . The NETCONF client is no longer interested in troubleshooting log files and O-RU does not need to send notification, as illustrated in Figure 14.2.2-3. - -![Sequence diagram showing the interaction between a NETCONF Server/(O-RU) and a NETCONF Client to stop troubleshooting logs. The client sends an message. The server stops log generation and returns an SUCCESS message.](cc91bf9aed46f8b219ebceaee276d195_img.jpg) - -``` -sequenceDiagram - participant Client as NETCONF Client - participant Server as NETCONF Server/(O-RU) - Note left of Server: Generation of troubleshooting log files is stopped. - Client->>Server: [1] - Server-->>Client: [2] SUCCESS -``` - -Sequence diagram showing the interaction between a NETCONF Server/(O-RU) and a NETCONF Client to stop troubleshooting logs. The client sends an message. The server stops log generation and returns an SUCCESS message. - -**Figure 14.2.2-3: Stop Generation of Troubleshooting Logs** - -The overall troubleshooting log behaviour is illustrated in Figure 14.2.2-4. It contains 2 cases, successful notification case with illustrative notification contents and no notification as abnormal case. - -![Sequence diagram showing the interaction between O-RU (NETCONF Server) and NETCONF Client/Notification Subscriber for troubleshooting log collection. The process involves sending an RPC, receiving a SUCCESS status, generating log files, sending a notification with log file names, and then stopping the collection with an RPC.](47702b55f927e2e85ac03e79a7ebe350_img.jpg) - -``` - -sequenceDiagram - participant O-RU as O-RU/ -(NETCONF Server) - participant Client as NETCONF Client/ -Notification Subscriber - - Note left of O-RU: O-RU collects log information - O-RU->>Client: [1] - Note left of O-RU: Start generation of troubleshooting log files - Client-->>O-RU: [2] SUCCESS - - alt successful notification case - Note left of O-RU: The troubleshooting log files are generated - alt Prior to present document version 10 - option 1, not preferred - Note right of O-RU: 2021-12-01T18:08:00.00Z[3] O-RAN/log/log0001.zipO-RAN/log/log0002.zipO-RAN/log/log0003.zip - else Prior to present document version 10 - option 2, not preferred - Note right of O-RU: 2021-12-01T18:08:00.00Z[4] log0001.ziplog0002.ziplog0003.zip - else Present document, preferred - Note right of O-RU: 2021-12-01T18:08:00.00Z[5] o-ran/log/log0001.zipo-ran/log/log0002.zipo-ran/log/log0003.zip - end - Note left of O-RU: Generated troubleshooting log files contain troubleshooting logs collected before triggering of rpc - else no notification sent - O-RU->>Client: [6] - Note left of O-RU: Generation of troubleshooting log files is stopped. - Client-->>O-RU: [7] SUCCESS - end - -``` - -Sequence diagram showing the interaction between O-RU (NETCONF Server) and NETCONF Client/Notification Subscriber for troubleshooting log collection. The process involves sending an RPC, receiving a SUCCESS status, generating log files, sending a notification with log file names, and then stopping the collection with an RPC. - -**Figure 14.2.2-4: Overall Troubleshooting Log behaviour** - -NOTE 4: Prior to version 10 of the present document, this document contained inconsistent definition of the **log-file-name** string between Figure 14.2.2-4 and associated YANG models. In present document previously permitted content of node **log-file-name** is considered as not preferred. Not preferred file formats may be subject to removal in a future version of the present document. - -## 14.2.3 Security logs - -### 14.2.3.1 Security log format - -An O-RU supporting the SECURITY-LOGGING feature shall ensure that the fields of individual security logs comply with the security log field requirements as specified in clause 5.3.8.8 of O-RAN Security Requirements Specifications [83]. The security logging by such an O-RU shall include the events mapped to an O-RAN Network Function in table 5.3.8.11.1-1 of [83]. - -### 14.2.3.2 Security log management - -There is no defined procedure for starting or stopping the logging of security events. The security log data shall be integrity protected and persistently stored in a non-volatile memory. - -An O-RU supporting the SECURITY-LOGGING feature shall support the configuration of log-data rotation functionality. Log-rotation refers to closing a first log file and opening a second new log file. A log file can be closed based on a configured time interval, using the **security-log-max-duration** leaf, and/or a configured maximum size, using the **security-log-max-size** leaf. An O-RU may expose read-only data pertaining to the maximum size of the security log storage media using the leaf **security-folder-memory-size**. - -The O-RU controller should configure log rotation parameters such that the size of a security log file does not exceed the maximum storage available in the O-RU. - -NOTE 1: How the O-RU Controller uses the value of **security-folder-memory-size** and/or other available information to determine the log rotation parameters is out of scope of the present document. - -The O-RU controller can arbitrarily decide to trigger the rotation of the current security log by sending the **rotate-security-log** rpc to the O-RU. An O-RU receiving the **rotate-security-log** rpc shall close the current security log file and open a new security log file. - -When a log file is rotated, the preserved integrity protected log file should be stored. The O-RU shall store the security log files in the o-ran/security/ folder in O-RU. - -NOTE 2: The details of the process used for file integrity protection is out of scope of the present document. The use by an O-RU of an encrypted file systems and/or encrypted folders to protect security logging data at rest are out of scope of the present document. - -The filename name for security logs shall be of the format: - -S\_\_. - -- Starting with a capital letter "S". -- Format of and can be local time or UTC. - -Local time format is YYYYMMDDHHMM+HHMM, indicating, year, month, day, hour, minute, timezone "+" or "-" , hour and minute for the time zone. - -UTC format is YYYYMMDDHHMMZ, indicating, year, month, day, hour, minute and with a special UTC designator ("Z") - -Time zone offset is provided by **timezone-utc-offset** in o-ran-operation.yang. - -- <**name**> in ietf-hardware is used. -- "\_" underscore is located between <**start-time**>, <**end-time**> and <**name**>. -- <**ext**> being the file extension. The extension shall indicate the archiving/encryption/compression method. - -The O-RU Controller shall configure one or more **remote-security-log-upload-path** and associated credential information in the O-RU. Once a security log file is closed, the O-RU shall upload the integrity protected preserved log file to the one or more configured security log servers. After successful upload to at least one server, the O-RU marks the file as being eligible to be overwritten. The O-RU shall send the **security-log-upload-notification** to notification subscribers indicating the output status of the security upload procedure. - -The overall security log procedure is illustrated in Figure 14.3.2-1. - -![Sequence diagram showing the interaction between NETCONF Server(O-RU), NETCONF Client, and Security Log File Server for security log configuration and rotation.](a76fa39f5daf6a026e032495262ed0f6_img.jpg) - -``` - -sequenceDiagram - participant RU as NETCONF Server/(O-RU) - participant Client as NETCONF Client - participant Server as Security Log File Server - - rect rgb(240, 240, 240) - Note over RU, Client: configure security log file servers - Client->>RU: ... - Note left of RU: 1 sftp://admin@operator.com:22/security-logs - RU-->>Client: 2 ... - end - - rect rgb(240, 240, 240) - Note over RU, Client: configure security log file rotation - Client->>RU: 3 ... - RU-->>Client: 4 - Note over RU, Client: 5 Configure trigger security-log-max-size - Note over RU, Client: non-zero value for security-log-max-duration - Note over RU, Client: 6 Configure trigger security-log-max-duration - end - - loop Continual generation of security logs. - rect rgb(240, 240, 240) - Note over RU, Client: triggering security log rotation - alt non-zero timer trigger - Note left of RU: 7 timer expiry triggered log rotation - else log size trigger - Note left of RU: 7 log file exceeds max size triggered log rotation - else RPC triggered rotation - Client->>RU: 7 - RU-->>Client: SUCCESS - end - Note left of RU: 8 O-RU closes, archives and stores security log file - end - - loop upload security log to each configured file Server - alt successful file upload - Note over RU, Server: O-RU completes file upload - RU->>Client: 9 ... - Note left of RU: O-RU marks uploaded security log as able to be overwritten - else unsuccessful file upload - Note over RU, Server: O-RU fails to upload file or remote-security-log-uploads list not configured - RU->>Client: 10 ...FAILURE... - end - end - end - -``` - -Sequence diagram showing the interaction between NETCONF Server(O-RU), NETCONF Client, and Security Log File Server for security log configuration and rotation. - -**Figure 14.2.3-1: Security Log Operations** - -## 14.3 Trace - -By requesting trace log files an O-RU controller is able to get them. Those trace log files contain collected log data files that can be used for trace purposes. - -The O-RU can provide all possible trace log files. The contents and log formats are dependent on O-RU implementation. - -The files should be compressed with compression method indicated by file name extension. - -O-RU shall start collecting the trace logs at the moment of receiving rpc. Notification shall be periodically sent to O-RU controller whenever generated trace log files is(are) ready. File names of newly created log file(s) shall be included in notification. The number and size of files provided by O-RU in a single notification is not restricted but the O-RU may keep the number and size of files reasonably small to allow completion of the whole "Trace data upload" scenario (all files from notification) within 15 minutes (with target to complete within 3 minutes) - assuming no additional upload restrictions from connectivity bandwidth or file server implementation. - -NOTE 1: Timing of creating new group of trace log files is up to O-RU implementation. - -After rpc received from O-RU controller, O-RU shall stop collecting trace logs and start generating trace log files which contain log data already collected after previous notification. - -The overall procedure is shown in Figure 14.3-1, with illustrative notification contents. Figure 14.3-1 shows the O-RU last notification with the is-notification-last::'true' and file names of trace log files being signalled to the notification subscriber. - -The file transfer mechanism for the created trace log files shall be handled by the file management described in clause 12 File management. - -![Sequence diagram showing the interaction between O-RU (NETCONF Server) and NETCONF Client/Notification Subscriber for trace log collection. The process involves starting trace logs, generating log files in a loop, stopping trace logs, and then generating the final part of the log files with notifications.](c355b8056bdd4728357d7d5ed18792ca_img.jpg) - -``` - -sequenceDiagram - participant O-RU as O-RU/ (NETCONF Server) - participant Client as NETCONF Client/ Notification Subscriber - - Note left of O-RU: Collection of trace log is started - O-RU->>Client: [1] - Client-->>O-RU: [2] SUCCESS - - loop log files are generated - Note left of O-RU: Trace log files are generated - alt Prior to present document version 10 - option 1, not preferred - O-RU-->>Client: [3] 2021-12-01T18:08:00.00ZO-RAN/log/trace[part#].zip - else Prior to present document version 10- option 2, not preferred - O-RU-->>Client: [4] 2021-12-01T18:08:00.00Ztrace[part#].zip - else Present document, preferred - O-RU-->>Client: [5] 2021-12-01T18:08:00.00Zo-ran/log/trace[part#].zip - end - Note right of O-RU: Generated trace log files contain trace logs collected - end - - Note left of O-RU: Collection of trace log is stopped - O-RU->>Client: [6] - Client-->>O-RU: [7] SUCCESS - - Note left of O-RU: Generation of last part of trace log files is completed - - alt Prior to present version - option 1, not preferred - O-RU-->>Client: [8] 2021-12-01T18:10:00.00ZO-RAN/log/trace[last-part#].ziptrue - else Prior to present version - option 2, not preferred - O-RU-->>Client: [9] 2021-12-01T18:10:00.00Ztrace[last-part#].ziptrue - else Present version and onwards, preferred - O-RU-->>Client: [10] 2021-12-01T18:10:00.00Zo-ran/log/trace[last-part#].ziptrue - end - -``` - -Sequence diagram showing the interaction between O-RU (NETCONF Server) and NETCONF Client/Notification Subscriber for trace log collection. The process involves starting trace logs, generating log files in a loop, stopping trace logs, and then generating the final part of the log files with notifications. - -**Figure 14.3-1: Overall Trace Log behaviour** - -NOTE 2: Prior to version 10 of the present document, this document contained inconsistent definition of the **log-file-name** string between Figure 14.3-1 and associated YANG models. In present document previously permitted content of node **log-file-name** is considered as not preferred. Not preferred file formats may be subject to removal in a future version of the present document. - -## 14.4 Operational aspects of antenna line devices - -### 14.4.1 Introduction - -An O-RU can connect to one or more external equipment including antenna line devices such as a RET, MultiRET, MHA, RAE and etc. - -- For the communication with antenna line devices, AISG 2.0 protocol [26] as Layer 7 application and HDLC protocol as Layer 2 data link are used. -- HDLC protocol as specified in ISO/IEC 13239 [65]. Detailed information can also be found in 3GPP TS 37.462 [27]. -- AISG 2.0 protocol is standardised by "Control interface for antenna line devices Standard No. AISG v2.0" [26] which is an adaptation of Iuant interface application layer defined in 3GPP TS 37.466 [28]. - -An O-RU may provide one or more ALD ports supporting connection with Antenna Line Devices. Each ALD port shall be able to support more than one ALD (i.e. a chained ALD configuration). - -Through the model O-RU may optionally inform about hardware relation between ALD port and O-RU connector(s) used by specific ALD port. In case more than one O-RU connector is used by single ALD port, O-RU may extend "overcurrent-report" notification by adding exact list of O-RU connectors for which overcurrent condition is detected. - -This clause describes the communication mechanisms based on AISG 2.0 protocol as specified in AISG 2.0 [26]. For communication with external equipment, AISG 2.0 uses Application Part protocols (RETAP, TMAAP etc.) at Layer 7 and HDLC as a Layer 2 datalink protocol. - -### 14.4.2 HDLC interworking - -HDLC protocol is standardised by ISO/IEC 13239 [65]. Detailed information can also be found in 3GPP TS 37.462 [27]. - -NOTE: The assumed HDLC communication speed is 9 600 bits per second. - -In order to handle collision detection in the HDLC branch, an O-RU supporting the ALD functionality shall support the following running counters reported using the corresponding YANG model: - -- Frames with wrong FCS -- Frames without stop flag -- Number of received octets - -For running counters served by the O-RU, both the O-RU and NETCONF Client shall handle wrap-over mechanism in a way, that wrap over zero is not considered as erroneous situation. - -A NETCONF client can recover these counters. From the changes observed in above counters, a NETCONF Client can deduce the presence of a collision on the HDLC bus. Additional diagnostic information may be derived from how these counters are incrementing. - -Additionally, the O-RU implements "RPC Status" to indicate status of last "ald-communication" RPC to requestor. - -- Status - flow control indicator of last requested operation (Status of RPC). - -Prior to any communication with ALD(s), the O-RU shall provide ALDs with DC power. The way of how DC power is managed is out of scope of this interface specification. - -In order to support collision detection and flow control, Figure 14.4.2-1 defines the reference architecture with functional split is defined: - -![Figure 14.4.2-1: ALD Reference Architecture diagram showing the flow of data from Netconf Client to RU and then to Antenna Line Device via HDLC. The RU contains internal processing blocks for FCS, byte stuffing, and flag handling, with a flow control section monitoring for errors.](057e0fadbc74743547d314f6fd0ff686_img.jpg) - -Figure 14.4.2-1: ALD Reference Architecture diagram showing the flow of data from Netconf Client to RU and then to Antenna Line Device via HDLC. The RU contains internal processing blocks for FCS, byte stuffing, and flag handling, with a flow control section monitoring for errors. - -Figure 14.4.2-1: ALD Reference Architecture - -The result of the above architecture is that below mentioned parts of HDLC message are processed by entities as illustrated in Figure 14.4.2-2. - -![](2ff9776a780f30bc64c7a9ef23131cbf_img.jpg) - -| AISG message | | | | | | -|-----------------|---------------------------|--------------------|------------------|-----------------|-----------------| -| Flag
1 octet | ADDR
1 octet | Control
1 octet | INFO
N octets | FCS
2 octets | Flag
1 octet | -| 0x7E | Secondary station address | Control bits | Variable length | CRC | 0x7E | -| HDLC frame | | | | | | - - - -| | | | -|----|----------------|----| -| RU | Netconf Client | RU | -|----|----------------|----| - -Figure 14.4.2-2: Component's responsibility split. - -### 14.4.3 ALD operations - -Figure 14.4.3-1 illustrates the ALD transfer procedure. - -- 1) The NETCONF Client sends RPC to the O-RU. The RPC has following input parameters: - - leaf: **port-id** (uint8) - contains the identity of the ALD port. The O-RU shall output the data to (corresponds to O-RU resources provided to NETCONF Client as inventory information). - -- leaf: **ald-req-msg** (up to 1 200 bytes) - may contain HDLC address, control bits and payload (see: 3GPP TS 37.462 for details). - -The O-RU shall perform HDLC communication with the ALD as specified in [27] clause 4.5 "Message timing". - -- 2) Immediately after the requested payload is sent to the ALD over the desired ALD port, the O-RU switches the ALD port into reception mode. -- 3) Bits received within reception window are formed to octets and inserted as payload into ald-resp-msg. -- 4) The O-RU responds to the NETCONF Client using the message containing following parameters: - - leaf: **port-id** (uint8) - - leaf: **status** - - leaf: **ald-resp-msg** (up to 1 200 bytes) - - leaf: **frames-with-wrong-crc** (4 bytes) - - leaf: **frames-without-stop-flag** (4 bytes) - - leaf: **number-of-received-octets** (4 bytes) - -In case there is no response from the ALD received within the reception window, the record "**ald-resp-msg**" in sent by the O-RU shall be empty. - -- 5) After reception, the O-RU shall wait a minimum of 3ms before the next transmission as per 3GPP TS 37.462, clause 4.5 "Message timing". - -![Sequence diagram showing the interaction between ALD, NETCONF Server/(O-RU), and NETCONF Client. The sequence starts with session establishment and port reporting from the server to the client. The client sends an ald-req-message. The server then performs HDLC messaging with the ALD, switches to reception mode, receives HDLC octets, and sends an ald-resp-msg back to the client. Finally, the server waits 3ms and switches back to ready mode.](7b49a5e2da4a559dce8c167c9203ad8e_img.jpg) - -``` - -sequenceDiagram - participant ALD - participant NETCONF Server/(O-RU) - participant NETCONF Client - - Note right of NETCONF Server/(O-RU): NETCONF session established. - Note right of NETCONF Server/(O-RU): Presence and list of supported ALD ports are reported by O-RU - Note right of NETCONF Client: - Note right of NETCONF Client: - Note right of NETCONF Client: [1] - Note right of NETCONF Client: .. - Note right of NETCONF Client: - - Note left of ALD: HDLC messaging between O-RU and ALD - Note right of NETCONF Server/(O-RU): [2] HDLC message octets with payload from ald-req-msg - Note right of NETCONF Server/(O-RU): Switch to 'reception' mode - - Note left of ALD: [3] HDLC octets - - Note right of NETCONF Server/(O-RU): - Note right of NETCONF Server/(O-RU): - Note right of NETCONF Server/(O-RU): .. - Note right of NETCONF Server/(O-RU): .. - Note right of NETCONF Server/(O-RU): [4] .. - Note right of NETCONF Server/(O-RU): .. - Note right of NETCONF Server/(O-RU): .. - Note right of NETCONF Server/(O-RU): .. - Note right of NETCONF Server/(O-RU): - - Note right of NETCONF Server/(O-RU): [5] after reception, O-RU waits minimum 3ms and switches ALD port to 'ready to send' mode - -``` - -Sequence diagram showing the interaction between ALD, NETCONF Server/(O-RU), and NETCONF Client. The sequence starts with session establishment and port reporting from the server to the client. The client sends an ald-req-message. The server then performs HDLC messaging with the ALD, switches to reception mode, receives HDLC octets, and sends an ald-resp-msg back to the client. Finally, the server waits 3ms and switches back to ready mode. - -**Figure 14.4.3-1: ALD Message Transfer** - -General scenario for HDLC link establishment - -**Precondition:** - -M-Plane connectivity between NETCONF Client and NETCONF Server is successfully established. NETCONF Server reports presence of the supported HDLC Primary Devices. - -**Procedure:** - -- 1) NETCONF Client triggers DC voltage on desired ALD ports using NETCONF RPC. After DC is turned on - NETCONF Client shall wait at least 3 s. -- 2) NETCONF Client performs HDLC bus scan using desired HDLC Primary Device offered by O-RU. -- 3) NETCONF Client determines presence of HDLC Secondary Devices connected to the ALD port. -- 4) NETCONF Client assigns HDLC addresses to desired HDLC Secondary Devices using HDLC Secondary Device unique id obtained from step 3-4 or from other pre-configured sources. -- 5) NETCONF Client initiates link establishment with secondary devices by sending SNRM command and the secondary device answers with UA command which will be used in **ald-resp-msg**. -- 6) NETCONF Client starts polling procedure for every HDLC-addressed Secondary Device. - -NETCONF Client shall skip step 1. in the procedure if **dc-control-support** is reported with value false for the ALD port. NETCONF client may skip step 2 and/or 3 in the procedure. HDLC speed alignment between ALD ports and secondary device(s) that supports multiple speeds is performed prior to step 2, 3, 4. For detail of speed alignment, please refer to [88] clause 4.1. - -**Postcondition:** - -Detected and addressed HDLC Secondary Devices are available for configuration. - -## 14.5 Operational aspects of external IO - -### 14.5.1 Introduction - -An O-RU can connect to one or more input and output ports for external device supervision and control. - -The External IO has the following functions: - -- INPUT: Supervising external devices. -- OUTPUT: Controlling external devices. - -Also, external IO function includes signalling to get the O-RU and O-RU controller in sync, enables port monitoring on the O-RU and provides notification from the O-RU to an O-RU controller, and provides control from an O-RU controller to the O-RU and enables output port controlling on the O-RU. - -The O-RU only implements external IO yang module if the O-RU supports External IO aspect. - -Through the model O-RU may optionally inform about hardware relation between External IO and O-RU connector(s) used by specific External IO. Separate O-RU connectors may be reported for single External IO. - -A change in condition of the external IO shall not affect other O-RU services such as RF transmission / reception behaviour. - -## 14.5.2 External input - -This clause explains single external input line case. For multiple external inputs case, same behaviour for each input shall be processed individually. - -For input, the O-RU and O-RU controller shall support two scenarios, as illustrated in Figure 14.5.2-1. - -- 1) To retrieve input state from O-RU controller and respond the input state from the O-RU to O-RU controller. -- 2) To send notification from the O-RU to O-RU controller when input state is changed. - -The value shall be: - -- TRUE: Circuit is open. -- FALSE: Circuit is closed - -When nothing is connected to the line the value shall be TRUE. - -![Sequence diagram showing the interaction between an O-RU (NETCONF Server) and a NETCONF Client/Notification Subscriber to retrieve external line-in information. The diagram includes an RPC request, an RPC reply, and a notification loop.](933a02975dec3041ee2bb07fdb82c92f_img.jpg) - -``` - -sequenceDiagram - participant O-RU as O-RU (NETCONF Server) - participant Client as NETCONF Client/Notification Subscriber - - Note right of Client: O-RU retrieve external input #0 - Client->>O-RU: - - - - -0 - - - - - -O-RU-->>Client: - - - -0 -true - - - - - -loop notification - Note left of O-RU: O-RU detects that external input has changed state - O-RU->>Client: external-input-change -end - -``` - -Sequence diagram showing the interaction between an O-RU (NETCONF Server) and a NETCONF Client/Notification Subscriber to retrieve external line-in information. The diagram includes an RPC request, an RPC reply, and a notification loop. - -Figure 14.5.2-1: Retrieve external line-in - -### 14.5.3 External output - -This clause explains single external output line case. For multiple external outputs case, same behaviour for each output shall be processed individually. - -For output, the O-RU and O-RU controller shall support two scenarios, as illustrated in Figures 14.5.3-1 and 14.5.3-2. - -- 1) To retrieve output state from O-RU controller and respond the output state from the O-RU to O-RU controller. -- 2) To send edit-config from the O-RU to O-RU controller when output state change is required. - -The value shall be: - -- TRUE: Circuit is open. -- FALSE: Circuit is closed - -The default values shall be TRUE. - -![Sequence diagram showing the interaction between a NETCONF Client and a NETCONF Server (O-RU) to retrieve external line-out information. The client sends a get-config request for port-out 0. The server internally retrieves the output and returns an rpc-reply containing the line-out status as true.](d871d4c53f2d5c336a44d9e2e28fe792_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client - participant Server as NETCONF Server (O-RU) - Note left of Server: O-RU retrieve external output #0 - Client->>Server: - - - - - -0 - - - - - - Server-->>Client: - - - -0 -true - - - - - -``` - -Sequence diagram showing the interaction between a NETCONF Client and a NETCONF Server (O-RU) to retrieve external line-out information. The client sends a get-config request for port-out 0. The server internally retrieves the output and returns an rpc-reply containing the line-out status as true. - -**Figure 14.5.3-1: Retrieve external line-out** - -![Sequence diagram showing NETCONF Client sending an edit-config RPC to a NETCONF Server (O-RU) to control external line-out. The RPC includes a configuration for port-out #0 with line-out set to false. A note indicates the O-RU sets the external output to closed. The server responds with an ok status.](8ac9329cf34ae099200b919cc670223c_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client - participant Server as NETCONF Server (O-RU) - Note left of Server: O-RU set closed external output #0 - Client->>Server: 0false - Server-->>Client: - -``` - -Sequence diagram showing NETCONF Client sending an edit-config RPC to a NETCONF Server (O-RU) to control external line-out. The RPC includes a configuration for port-out #0 with line-out set to false. A note indicates the O-RU sets the external output to closed. The server responds with an ok status. - -Figure 14.5.3-2: Control external line-out - -## 14.6 O-RU connectors - -### 14.6.1 Introduction to O-RU connectors - -The O-RU may indicate presence and label of its physical connectors of specific type. The O-RU connectors can be exposed through o-ran-hardware.yang module as objects of **class** "O-RU-CONNECTOR". In the present document, coaxial antenna connectors serving for antenna feeders and beamforming-calibration lines are introduced. - -### 14.6.2 Connectors related to antennas and antenna arrays - -#### 14.6.2.1 Antenna connectors - -This clause describes usage of antenna connectors related to feeders (used to carry air interface signals between O-RU and external antennas or external antenna arrays) and beamforming calibration lines (used by O-RU i.e. to handle supplementary signals needed for external antenna arrays calibration). - -Exposed O-RU Connectors of **class** "O-RU-ANTENNA-CONNECTOR" are based on **class** "O-RU-CONNECTOR" and are used in o-ran-uplane-conf.yang module to show how feeders and beamforming calibration lines are related to antenna arrays and their array elements. This allows to align configuration with physical cabling that technicians need to connect between O-RU and external physical antenna array. - -## 14.6.2.2 Distinguishable types of antenna connectors - -### 14.6.2.2.1 Feeder - -Exposed O-RU connectors of **class** "O-RU-FEEDER" are based on **class** "O-RU-ANTENNA-CONNECTOR". Objects of this **class** are intended to represent physical connectors for coaxial feeders between O-RU and external antennas or antenna arrays. The feeder connector can be referenced by single array element of specific array, however in case the array element is shared between tx-array and rx-array or by multiband arrays, such O-RU connector is expected to be referenced by each of arrays containing array element fed with RF signals through such connector. - -For this class of O-RU connectors, name shown in the model shall be identical to the label of physical connector visible on the O-RU's enclosure. - -### 14.6.2.2.2 Beamforming calibration - -Exposed O-RU connectors of **class** "O-RU-BF-CAL" are based on **class** "O-RU-ANTENNA-CONNECTOR". Objects of this **class** are intended to represent physical connectors for supplementary coaxial cables used in antenna calibration process for external antenna arrays. The beamforming calibration connector is to be referenced by group of array elements belonging to single array. This is also possible, that there will be references to few groups of array elements belonging to different antenna arrays (e.g. related tx-array and rx-array or arrays for different bands that share array elements). - -For this class of O-RU connectors, name shown in the model shall be identical to the label of physical connector visible on the O-RU's enclosure. - -## 14.6.3 Connectors related to other O-RU functions - -### 14.6.3.1 Overview - -This clause describes usage of other types of O-RU connectors physically available on O-RU's enclosure. - -Exposed O-RU Connectors of **classes** described in this clause are based on **class** "O-RU-CONNECTOR" and are used in o-ran-aldr-port.yang and o-ran-externalio.yang module to show how these connectors are related to internal O-RU elements. - -### 14.6.3.2 RS-485 connectors - -Exposed O-RU connectors of **class** "RS-485" are based on **class** "O-RU-CONNECTOR". Objects of this **class** are intended to represent physical connectors for RS-485 interface used e.g. for communication between O-RU and Antenna Line Devices. - -For this class of O-RU connectors, name shown in the model shall be identical to the label of physical connector visible on the O-RU's enclosure. - -### 14.6.3.3 External IO connectors - -Exposed O-RU connectors of **class** "O-RU-EXTIO" are based on **class** "O-RU-CONNECTOR". Objects of this **class** are intended to represent physical connectors for externally available input / output lines that may optionally be offered by the O-RU. - -For this class of O-RU connectors, name shown in the model shall be identical to the label of physical connector visible on the O-RU's enclosure. - -## 15 Details of O-RU operations - -### 15.1 Retrieval of O-RU information - -This clause provides handling for O-RU controller(s) to retrieve O-RU information from O-RU. The further actions such as SW Management, U-plane configuration and Performance Management use these retrieved O-RU information. - -The following information, for example, can be retrieved from the O-RU: - -hw/hardware/component - -- retrieve **mfg-name** - the name of the O-RU manufacturer -- retrieve **serial-num** -- the serial number of the O-RU -- retrieve **software-rev** - the version of the O-RU software build - -o-ran-hardware/hardware/component/ - -- retrieve **product-code** - the O-RAN defined product code - -o-ran-operations/operational-info/declarations - -- retrieve **supported-mplane-version** - the version of the O-RAN M-Plane interface -- retrieve **supported-cusplane-version** - the version of the O-RAN CUS-Plane interface -- retrieve **supported-header-mechanism** - the type of C/U plane headers supported by the O-RU - -o-ran-operations/operational-state - -- retrieve **restart-cause** – the reason for the last restart - -o-ran-sync/sync - -- retrieve **sync-state** – the synchronisation state of the O-RU - -The detail of O-RU information, see corresponding YANG modules in clause D. - -## 15.2 User plane message routing - -### 15.2.1 Introduction - -The purpose of U-Plane configuration is to define the relationship between U-Plane application endpoints in the O-DU and those in the O-RU. After such relationships are defined, the application endpoints are able to exchange IQ data using the U-Plane application protocol defined in clause 5.4 of [2]. - -#### Precondition: - -- M-Plane connectivity is established between NETCONF Client and NETCONF Server. - -### 15.2.2 Configurable format for eAxC\_ID - -The eAxC\_ID is used by C/U-plane application to manage eCPRI communication between desired C/U-Plane application components in O-DU and O-RU. - -As defined in clause 5.1.3.2.7 of [2], the eAxC\_ID consists of four parameters: DU\_Port\_ID, RU\_Port\_ID, CC\_ID and BandSector\_ID. Order of parameters in eAxC\_ID shall follow definitions in CUS-Plane spec. In this version of the O-RAN WG4 specification, the length of eAxC\_ID is constant and equal to 16 bits. To enable optimal sharing of the 16 bits between these four parameters, the assignment of eAxC\_ID bits to parameters is not fixed. As a consequence, there is a need for NETCONF client to configure the bit assignment to parameters mappings using the M-Plane interface. - -NOTE 1: [2] refers to the eAxC\_ID parameters as DU\_Port\_ID, RU\_Port\_ID, CC\_ID and BandSector\_ID and the present document and associated YANG models refer to the eaxc-id parameters as du-ports, ru-ports, cc-ids and band-sectors. - -To handle flexible bit assignment, configurable bitmasks are defined for each parameter. - -NOTE 2: Flexible configuration means, that bits of eAxC\_ID can be assigned to parameters in runtime. - -Rules to be followed by NETCONF Client when configuring bit assignments: - -- notation used for parameters forming eAxC\_ID is from the LSB. -- each parameter uses consecutive bits. -- each parameter can occupy 0-16 bits. -- single bit of eAxC\_ID cannot be assigned to more than one parameter. - -RPC **edit-config** shall be used to configure bit assignments to O-RU. - -Bit assignment change for parameters related to an existing carrier is not allowed. (Impacted carriers need to be deactivated and deleted prior to any change in eAxC\_ID configuration, and then be subsequently created and activated.) - -An example of bit assignment usage where 3 bits are assigned to the BAND-SECTOR-ID, 3 bits for CC-ID, 7 bit for DU-PORT-ID and 3 bits for RU-PORT-ID is shown below: - -1111111000000000 - -0000000111000000 - -000000000001110000 - -0000000000000111 - -Configuration of **e-axcid** for a given low-level-[tr]x-endpoint requires four bitmask values: **o-du-port-bitmask**, **band-sector-bitmask**, **ccid-bitmask**, and **ru-port-bitmask**. One specific combination of these four bitmask values defines one eAxC\_ID format. An O-RU shall be configured with a single eAxC\_ID format. An O-RU controller may configure different O-RUs with different eAxC\_ID formats. - -## 15.2.3 U-Plane endpoint addressing - -Parameter "eaxc-id" for low-level-tx-endpoint and low-level-rx-endpoint, defined using an unsigned 16-bit integer, shall follow the eaxc-id addressing schema defined in clause 15.2.2. Refer to the eaxc-id parameter description in CUS plane specification clause 5.1.3.2.7 of [2]. - -The NETCONF Client shall assign unique values to the "eaxc\_id" addresses to all low-level-rx-endpoint elements and low-level-tx-endpoint elements, within the O-RU when operating in the same direction (Tx or Rx), even when these operate across different named interfaces of the O-RU. - -More precisely, the same eaxc-id cannot be simultaneously assigned to multiple low-level-rx-endpoints or to multiple and low-level-tx-endpoints. Clarifying eaxc-id assignment by example, and unless otherwise specified, within the same O-RU (considering a $2 \times 2$ MIMO): - -Case 1: Allowed eaxc-id assignment (same antenna ports used for Tx and Rx) - -- low-level-rx-endpoint (name 1) - eaxc-id=1 -- low-level-tx-endpoint (name 1) - eaxc-id=1 -- low-level-rx-endpoint (name 2) - eaxc-id=2 -- low-level-tx-endpoint (name 2) - eaxc-id=2 - -Case 2: Allowed eaxc-id assignment (separate antenna ports used for Tx and Rx) - -- low-level-rx-endpoint (name 1) - eaxc-id=1 -- low-level-tx-endpoint (name 1) - eaxc-id=2 -- low-level-rx-endpoint (name 2) - eaxc-id=3 -- low-level-tx-endpoint (name 2) - eaxc-id=4 - -Case 3: Prohibited eaxc-id assignment (separate antenna ports used for Tx and Rx) - -- low-level-rx-endpoint (name 1) - eaxc-id=1 -- low-level-tx-endpoint (name 1) - eaxc-id=2 -- low-level-rx-endpoint (name 2) - eaxc-id=1 -- low-level-tx-endpoint (name 2) – eaxc-id=2 - -The O-RU shall reject any configuration that corresponds to a prohibited eaxc-id assignment. - -## 15.2.4 General configuration scenario - -Below is the general scenario to be followed by a NETCONF Client in order to properly configure communication between C/U-Plane endpoints in the O-DU and O-RU. - -Operations can be performed in other order (including combining some of them in one request) than provided below assumed the highlighted rules are followed and result (overall configuration) of each request sent by NETCONF Client is valid. - -Selected highlighted rules below: - -- eaxc-id shall be unique for all low-level-[tr]x-endpoints within the O-RU in the same direction (Tx or Rx) and linked with any low-level-rx-link or low-level-tx-link. -- at the moment of creation, every low-level-rx-link shall be linked to an existing rx-array-carrier, an existing low-level-rx-endpoint and an existing processing-element (or an existing transport-qualified-processing-element when the processing element is configured by the list **additional-transport-session-type-elements**). In this latter case, the O-RU shall use the /user-plane-configuration/low-level-rx-links/**transport-qualified-processing-element** schema nodes instead of the /user-plane-configuration/low-level-rx-links/**processing-element** schema node, an O-RU Controller shall still configure the **processing-element** schema node in the **low-level-rx-links** list with a leafref to valid ru-element, but this shall not be used by the O-RU. - -- at the moment of creation, every low-level-tx-link shall be linked to an existing tx-array-carrier, an existing low-level-tx-endpoint and an existing processing-element (or an existing transport-qualified-processing-element when the processing element is configured by the list **additional-transport-session-type-elements**). In this latter case, the O-RU shall use the /user-plane-configuration/low-level-tx-links/**transport-qualified-processing-element** schema nodes instead of the /user-plane-configuration/low-level-tx-links/**processing-element** schema node, an O-RU Controller shall still configure the **processing-element** schema node in the **low-level-tx-links** list with a leafref to valid ru-element, but this shall not be used by the O-RU. - -In the selected highlighted rules, the word "existing" includes nodes created in the same edit-config operation. - -The O-RU shall support configuration of [tr]x-array-carrier(s), low-level-[tr]x-endpoint(s), processing element(s) and low-level-[tr]x-link(s) in the same RPC edit-config. - -The O-RU shall support configuration of [tr]x-array-carrier(s), low-level-[tr]x-endpoint(s), processing element(s) and low-level-[tr]x-link(s) in the separate RPC edit-config(s). - -NOTE: The above requirements are not limited to low-level-[tr]x-link configuration. - -- 1) NETCONF Client determines the presence of following operational data offered by NETCONF Server: - - tx-array(s) - by fetching the list of **tx-arrays** in o-ran-uplane-conf.yang - - rx-array(s) – by fetching the list of **rx-arrays** in o-ran-uplane-conf.yang - - endpoint-type(s) – by fetching list **endpoint-types** in o-ran-uplane-conf.yang - - static-low-level-tx-endpoint element(s) – by fetching the list **static-low-level-tx-endpoints** in o-ran-uplane-conf.yang - - static-low-level-rx-endpoint element(s) – by fetching the list **static-low-level-rx-endpoints** in o-ran-uplane-conf.yang - - endpoint-capacity-sharing-group(s)- by fetching list **endpoint-capacity-sharing-groups** in o-ran-uplane-conf.yang if it is reported - - endpoint-bf-profile-group(s) - by fetching list **endpoint-bf-profile-group** in o-ran-uplane-conf.yang if O-RU supports YANG feature BF-DELAY-PROFILE - - interface(s)– by fetching list of **interfaces** in o-ran-interfaces.yang - - O-RU's connector(s) – by fetching list of **related-o-ru-connectors** (if exist) in o-ran-uplane-conf.yang -- 2) NETCONF Client determines capabilities exposed by **endpoint-type(s)**, **static-low-level-tx-endpoint(s)** and **static-low-level-rx-endpoint(s)**. Additionally, NETCONF Client determines capabilities exposed by **endpoint-capacity-sharing-groups** and specific parameters proprietary to **[tr]x-array(s)**. -- 3) For operational data determined in step 1) NETCONF Client examines the relationship between: - - static-low-level-tx-endpoint(s) and tx-array(s) in o-ran-uplane-conf.yang - - static-low-level-rx-endpoint(s) and rx-array(s) in o-ran-uplane-conf.yang - - endpoint-type and all static-low-level-[tr]x-endpoint(s) of this endpoint-type - - each endpoint-capacity-sharing-group and member static-low-level-[tr]x-endpoint(s) - -- each endpoint-type and all endpoint-bf-profile-group(s) it supports -- each static-low-level-tx-endpoint and interface -- each static-low-level-rx-endpoint and interface -- tx-array(s), rx-array(s) and their elements in o-ran-uplane-conf.yang -- o-ru-connector(s) and [tr]x-array in o-ran-uplane-conf.yang (if available) -- interface(s) and port(s) in ietf-interfaces.yang (with o-ran port-reference augmentation) - -NOTE 2: NETCONF Client retrieves the content of o-ran-beamforming.yang module to obtain knowledge regarding beamforming-related parameters that apply for particular NETCONF Server. This step is optional, as o-ran-beamforming.yang module exists only in case NETCONF Server supports beamforming. Obtained parameters are needed by Netconf Client to perform beamforming control. - -- 4) NETCONF Client determines the endpoint's ability of all supported beamforming methods list and related delay profiles. Information about beamforming method lists supported by endpoints is exposed through parameter **endpoint-bf-profile-group**. If the beamforming method list does not report its associated supported-delay-profile, it uses the default **bandwidth-scs-delay-state** list to find its delay parameter values. Each bf-profile-id is used to identify an endpoint-bf-profile-group which indicates a list of beamforming methods that can be used simultaneously, and delay profiles associated with each list of beamforming methods. When O-RU indicates support for a combination of BF-METHOD(s) and associated delay-profile per endpoint, all endpoints supporting the same combination of BF-METHOD(s) shall advertise the same delay-profile value. Multiple bf-profile-id(s) capabilities can be exposed by **endpoint-types**. -- 5) NETCONF Client determines each static-low-level-rx-endpoint's ability to support non-time managed and/or time managed traffic. Information about managed delayed traffic type supported by an endpoint-type is exposed through parameter **managed-delay-support** (enumeration) and it indicates whether the endpoints of this particular endpoint-type can support time managed traffic (MANAGED), non-time managed traffic (NON\_MANAGED), or both (BOTH). -- 6) NETCONF Client determines and selects static-low-level-rx-endpoint(s) and static-low-level-tx-endpoint(s), that are suitable for the desired O-DU cell configuration to be used for configuring array carriers. - -Example considerations for selection are listed below: - -- Transport aspect: static-low-level-rx-endpoint and static-low-level-tx-endpoint selected should be accessible via the intended interface(s), extra consideration is needed for optional interface restrictions declared by static-low-level-[tr]x-endpoints - - Antenna array: O-DU's intention of which antenna array is going to be used by the O-DU cell related configuration will be input for selection - - Type of traffic: O-DU's intention of type of traffic to be used on endpoint, for example, non-time managed traffic or time managed traffic will be input for selection - - Beamforming type: O-DU's intention for beamforming type to be used for UL and DL will impact selection -- 7) NETCONF Client performs C/U-Plane transport configuration between O-DU and O-RU. NETCONF Client configures **interfaces** and creates processing-elements related to the interfaces offering access to selected endpoints (suitable in terms of capabilities and able to process signals related with desired [tr]x-array) and ports (suitable in terms of capabilities and able to transfer signals from/to a desired interface). Details of configuring **interfaces** and **processing-elements** are described in clause 7. - -- 8) Once transport layer is configured, O-DU may perform initial verification of C/U Plane Transport Connectivity as described in clause 7.6 - with respect to content of list "restricted-interfaces" every selected endpoint is reachable through. -- 9) NETCONF Client creates low-level-tx-endpoints and low-level-rx-endpoints referring to static-low-level-tx-endpoints and static-low-level-rx-endpoints determined and selected in step 6) as suitable for desired array-carrier configuration. NETCONF Client assigns unique eaxc-id(s) values to every created low-level-[tr]x-endpoint. Obtained information from step 2)-5) shall be respected when NETCONF Client configures low-level-[tr]x-endpoints referenced to static-low-level-[tr]x-endpoints by parameter **name**. - -NOTE 3: Uniqueness of eaxc-id is mandatory within the O-RU in the same direction (Tx or Rx) even across interface elements having relationship to low-level-rx-endpoint elements or low-level-tx-endpoint elements. - -In case NETCONF Client wants particular value of eAxC\_ID to be used for non-time managed traffic, NETCONF Client shall assign this eAxC\_ID to parameter "eaxc-id" belonging to low-level-rx-endpoint, that is capable to support non-time managed traffic (as per reference to capabilities exposed by corresponding static-low-level-rx-endpoint corresponding to low-level-rx-endpoint by **name**). - -When assigning eAxC\_ID to a low-level-rx-endpoint, NETCONF Client shall also configure whether the low-level-rx-endpoint is to work in non-time-managed mode (when applicable) or not using **non-time-managed-delay-enabled**. NETCONF client shall not change time management types of a low-level-rx-endpoint in case there is traffic served by the endpoint. Configuration is assumed to be static for run-time. - -When NETCONF server declares that an endpoint supports multiple bf-profile-id(s), NETCONF Client may configure **configured-bf-profile-id** in the list of low-level-[tr]x-endpoint to one of the values reported in **bf-profile-group** reported in the related endpoint-type and the O-RU shall use it. If the NETCONF Client does not configure **configured-bf-profile-id** per endpoint, the O-RU shall use the beamforming method determined by section type supported by endpoint and default delay profile. - -- 10) NETCONF Client creates tx-array-carrier(s) and rx-array-carrier(s). The tx-array-carriers and rx-array-carriers can be configured with **type** set to LTE, NR or DSS-LTE-NR. The configuration of array carrier with type DSS-LTE-NR is only allowed when the O-RU supports Dynamic Spectrum Sharing (DSS) feature as indicated by feature DSS\_LTE\_NR in o-ran-module-cap.yang. If the O-RU indicates it supports the feature DSS\_LTE\_NR but does not support Section Extension 9, then instead of configuring a carrier as DSS-LTE-NR, the O-DU shall configure DSS by using different eAxC ids (i.e. different endpoints) as described in CUS plane specification clause 7.2.6 of [2]. - -**Table 15.2.4-1: Centre Bandwidth Calculation** - -| Type | N RB | Centre of channel bandwidth (same as F REF as defined in clause 5.4.2.1 of 3GPP TS 38.104 Section 5.4.2.1 [66]) | -|------------|------------------------|----------------------------------------------------------------------------------------------------------------------------| -| LTE or DSS | N RB mod2=1 | Between (k-1) RE and k RE of n PRB RB | -| | N RB mod2=0 | Between the highest RE of (n PRB -1) RB and k RE of n PRB RB | -| NR | N RB mod2=1 | Centre of k th RE of n PRB RB | -| | N RB mod2=0 | | - -The parameters k, nPRB and NRB referenced here are specified in Table 5.4.2.2-1 of 3GPP TS 38.104. - -- 11) NETCONF Client creates low-level-[tr]x-link(s) to make relationship between low-level-[tr]x-endpoint(s), [tr]x-array-carriers and processing-elements belonging to transport. Respective TX path and RX path linkage shall be followed. This is illustrated in Figure 15.2.4-1. - -NOTE 4: C/U-Plane traffic can be prioritized by reference **user-plane-uplink-marking** indicated by **low-level-rx-link** in o-ran-uplane-conf.yang. The reference is to o-ran-processing-element.yang, where it is linked to **up-marking-name**. Further the **up-marking-name** points to o-ran-interfaces.yang, where it ends up pointing to priority depending on actually used u-plane transport (either PCP for Ethernet or DSCP for IP). For details regarding priorities see [2], clause 5.3. - -![Diagram showing relations between CU-Plane and carrier management elements. It consists of two boxes: 'transport configuration' and 'u-plane configuration (o-ran-uplane-conf.yang)'. The 'transport configuration' box contains 'iana port (ietf-hardware)', 'ietf-interface (with o-ran augmentations) port-reference', and 'processing-element or transport-qualified-processing-element' with attributes like 'transport-session-type', 'element-name', 'interface-name', 'alias-flow', 'eth-flow', and 'udpip-flow'. The 'u-plane configuration' box contains 'tx-array-carrier', 'low-level-tx-link', 'processing-element tx-array-carrier low-level-tx-endpoint', 'static-low-level-tx-endpoint array', 'low-level-tx-endpoint', 'low-level-rx-link', 'processing-element rx-array-carrier low-level-rx-endpoint', 'static-low-level-rx-endpoint array', 'rx-array-carrier', 'rx-array', and 'relations'. Arrows indicate relationships between these elements with multiplicity indicators like 0..*, 1, 0..2.](313826501fcb4294a5d337702ea35f2d_img.jpg) - -Diagram showing relations between CU-Plane and carrier management elements. It consists of two boxes: 'transport configuration' and 'u-plane configuration (o-ran-uplane-conf.yang)'. The 'transport configuration' box contains 'iana port (ietf-hardware)', 'ietf-interface (with o-ran augmentations) port-reference', and 'processing-element or transport-qualified-processing-element' with attributes like 'transport-session-type', 'element-name', 'interface-name', 'alias-flow', 'eth-flow', and 'udpip-flow'. The 'u-plane configuration' box contains 'tx-array-carrier', 'low-level-tx-link', 'processing-element tx-array-carrier low-level-tx-endpoint', 'static-low-level-tx-endpoint array', 'low-level-tx-endpoint', 'low-level-rx-link', 'processing-element rx-array-carrier low-level-rx-endpoint', 'static-low-level-rx-endpoint array', 'rx-array-carrier', 'rx-array', and 'relations'. Arrows indicate relationships between these elements with multiplicity indicators like 0..\*, 1, 0..2. - -Figure 15.2.4-1: Diagram showing relations between CU-Plane and carrier management elements - -Detailed contents of objects shown in "u-plane configuration" box in Figure 15.2.4-1 are defined in the o-ran-uplane-conf.yang module. - -High level sequences about carrier creation are described in clause 15.3.1. - -## 15.3 Carrier configuration - -### 15.3.1 Carrier creation - -This clause provides high level scenario for carrier creation procedure. Precondition for below steps are steps 1 to 6 from clause 15.2.4. The below steps are covered by steps 7 and 9 to 11 in clause 15.2.4 where those steps are described with more details. - -- 1) NETCONF Client creates the **tx-array-carriers** in relation to the desired **tx-arrays**. - -NOTE 1: Generally the number of **tx-array-carriers** is the same as multiple of the desired number of **tx-arrays** and the number of component carriers. - -- 2) NETCONF Client creates the **rx-array-carriers** in relation to the desired **rx-arrays**. - -NOTE 2: Generally the number of **rx-array-carriers** is the same as multiple of the desired number of **rx-arrays** and the number of component carriers. - -- 3) NETCONF Client creates the **processing-elements** related to **interfaces** offering access to endpoints. - -- 4) NETCONF Client creates low-level-tx-endpoints and low-level-rx-endpoints related to desired static-low-level-tx endpoints and static-low-level-rx-endpoints respectively. -- 5) NETCONF Client creates the **low-level-tx-links** containing relationship to the existing **tx-array-carriers**, **low-level-tx-endpoints** and existing **processing-elements**. -- 6) NETCONF Client creates the **low-level-rx-links** containing the relationship to existing **rx-array-carriers**, **low-level-rx-endpoints** and existing **processing-elements**. - -With the above steps successfully performed, the relationship between C/U-Plane application endpoints at O-DU and O-RU is configured. - -### 15.3.2 Activation, deactivation and sleep - -The NETCONF Client performs activation of a tx/rx-array-carrier by setting the value of the parameter "active" at tx-array-carrier element / rx-array-carrier element to "ACTIVE". - -The NETCONF Client performs deactivation of a tx/rx-array-carrier by setting the value of the parameter "active" at tx-array-carrier element / rx-array-carrier element to "INACTIVE". - -Communication between related U-Plane endpoints is enabled under condition, that for corresponding tx-array-carrier or rx-array-carrier value of parameter "active" is "ACTIVE" and value of parameter "state" is "READY". Otherwise, communication is disabled. - -The NETCONF Client can put the tx-array-carrier / rx-array-carrier to sleep by setting value of parameter "active" in the corresponding tx-array-carrier element / rx-array-carrier element to "SLEEP". - -A particular tx-array-carrier / rx-array-carrier is in sleep mode when value of its parameter "active" is "SLEEP" and value of its parameter "state" is "READY". To save energy, O-RU may disable all elements of tx-array / rx-array associated with the tx-array-carrier / rx-array-carrier in sleep mode provided there is no impact to operation of other tx-array-carriers / rx-array-carriers. This means that, the O-RU may disable tx-array / rx-array elements only if all affected tx-array-carriers / rx-array-carriers (associated with the tx-array / rx-array or any tx-array / rx-array that shares elements with the tx-array / rx-array) are in sleep mode, as defined in this clause. For any newly activated tx-array-carrier / rx-array-carrier, the O-RU shall use the antenna mask (refer to clause 20.3.2), if an antenna mask is configured, for the tx-array / rx-array associated with the tx-array-carrier / rx-array-carrier. - -If a tx-array-carrier / rx-array-carrier is assigned to a tx-array / rx-array all of whose elements are at that time disabled due to sleep mode as defined in this clause, O-RU shall enable all those elements of the tx-array / rx-array to allow carrier activation. - -O-RU shall not autonomously change [tr]x-array-carrier::active to "ACTIVE". - -For detailed description of tx-array-carriers and rx-array-carriers, refer to *description* substatement in YANG models. - -Figure 15.3.2-0a shows the flow for successful carrier activation and illustrates the communication between the O-RU and O-DU during carrier activation procedure. - -![Sequence diagram for Carrier activation between O-DU (NETCONF Client) and O-RU (NETCONF Server). The process involves sending an edit-config to activate carriers, storing the configuration, and then handling state changes (DISABLED to ACTIVE, then BUSY, then READY) through notifications.](6e0f8561f98e81dc4918793f6a884357_img.jpg) - -**Carrier activation** - -``` - -sequenceDiagram - participant O-DU as O-DU -NETCONF Client - participant O-RU as O-RU -NETCONF Server - - Note right of O-RU: State of carriers is: - -INACTIVE -DISABLED - - -INACTIVE -DISABLED - - - Note left of O-DU: edit-config to trigger -array-carrier activation - - O-DU->>O-RU: 1 - - -ACTIVE - - -ACTIVE - - - - - Note right of O-RU: Configuration stored -in datastore - - O-RU->>O-DU: 2 -ACTIVE - - -ACTIVE - - - O-DU->>O-RU: 3 - - - - opt Internal O-RU design uses BUSY state - Note right of O-RU: t/rx-array-carriers -state become BUSY - - O-RU->>O-DU: 4 -BUSY - - -BUSY - - - Note left of O-DU: Notification about -tx-array-carriers and -rx-array-carriers -state change - - O-RU->>O-DU: 5 - - -.. -BUSY - - - -.. -BUSY - - - - Note right of O-RU: O-RU performs internal -procedures to activate -t/rx-array-carriers - - O-RU->>O-DU: 6 carrier activation -internal procedure - - Note right of O-RU: t/rx-array-carriers -state become READY - - O-RU->>O-DU: 7 -READY - - -READY - - - Note left of O-DU: Notification about -tx-array-carriers and -rx-array-carriers -state change - - O-RU->>O-DU: 8 - - -.. -READY - - - -.. -READY - - - end - -``` - -Sequence diagram for Carrier activation between O-DU (NETCONF Client) and O-RU (NETCONF Server). The process involves sending an edit-config to activate carriers, storing the configuration, and then handling state changes (DISABLED to ACTIVE, then BUSY, then READY) through notifications. - -**Figure 15.3.2-0a: Carrier activation sequence** - -Figure 15.3.2-0b shows a flow for carrier deactivation and illustrates the communication between the O-RU and O-DU during carrier deactivation procedure. - -![](d455e47a6d660a3cc29a125a2cbe355b_img.jpg) - -**Carrier deactivation** - -``` - -sequenceDiagram - participant O-DU as O-DU -NETCONF Client - participant O-RU as O-RU -NETCONF Server - - Note right of O-RU: State of carriers is: - -ACTIVE -READY - - -ACTIVE -READY - - - alt NETCONF client triggers deactivation - Note left of O-DU: edit-config to trigger -array-carrier deactivation - O-DU->>O-RU: 1 - - -INACTIVE - - -INACTIVE - - - - Note right of O-RU: Edited configuration stored -in O-RU's datastore - O-RU-->>O-RU: 2 -INACTIVE - - -INACTIVE - - O-RU->>O-DU: 3 - - - else O-RU triggers deactivation autonomously - O-RU-->>O-RU: 4 autonomous deactivation - Note right of O-RU: Exceptionally, -O-RU updates its own -configuration datastore - O-RU-->>O-RU: 5 -INACTIVE - - -INACTIVE - - end - - opt Internal O-RU design uses BUSY state - Note right of O-RU: t/rx-array-carriers -state become BUSY - O-RU-->>O-RU: 6 -BUSY - - -BUSY - - Note left of O-DU: Notification about -tx-array-carriers and -rx-array-carriers -state change - O-RU->>O-DU: 7 - - -... -BUSY - - - - -... -BUSY - - - - end - - O-RU-->>O-RU: 8 stop RF transmission - Note right of O-RU: t/rx-array-carriers -state set autonomously to DISABLED - O-RU-->>O-RU: 9 -DISABLED - - -DISABLED - - Note left of O-DU: Notification about -tx-array-carriers and -rx-array-carriers -state change - O-RU->>O-DU: 10 - - -... -DISABLED - - - - -... -DISABLED - - - - Note left of O-DU: O-DU can determine -whether O-RU has -autonomously updated -its own configuration -datastore - O-DU->>O-RU: 11 information processed and -stop sending traffic to O-RU - - opt O-DU chooses to synchronize its configuration datastore with that of the O-RU - O-DU->>O-RU: 12 - - - - - O-RU->>O-DU: 13 - -O-RU Configuration - - - end - -``` - -**Figure 15.3.2-0b: Carrier deactivation sequence** - -The O-RU may optionally expose parameter **availability-status** for configured [tr]x-array-carrier(s). This **availability-status** parameter is intended to supplement parameter **state**. This allows O-RU to provide the current status about various conditions related to a [tr]x-array-carrier, as shown in Table 15.3.2-1. - -**Table 15.3.2-1: Availability Status** - -| Value of availability-status | Current condition of [tr]x-array-carrier | Notes | -|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| -| (empty) | There are no faults that impact the [tr]x-array-carrier state | | -| FAILED | There is at least one fault related to source internal to O-RU that made the ACTIVE [tr]x-array-carrier to turn to INACTIVE and/or makes INACTIVE [tr]x-array-carrier not able to become ACTIVE. | | -| DEPENDENCY | There is at least one fault related to source external to O-RU that made the ACTIVE [tr]x-array-carrier to turn to INACTIVE and/or makes INACTIVE [tr]x-array-carrier not able to become ACTIVE. | Example of fault related to external source can be the one related to lost synchronisation source. | - -Figure 15.3.2-1 shows possible transitions and values combination to be followed by "active" and "state". Combination or transitions outside of below diagram is not allowed. - -![State transition diagram for carrier parameters. States include carrier_state::DISABLED, carrier_state::BUSY, and carrier_state::READY. Transitions are labeled with O-DU controlled carrier activation/deactivation and O-RU autonomous recovery actions.](88f5a639e0e8bae43a30c7ebe33752e5_img.jpg) - -``` - -stateDiagram-v2 - [*] --> carrier_state::DISABLED - carrier_state::DISABLED --> carrier_state::BUSY - carrier_state::BUSY --> carrier_state::READY - carrier_state::READY --> carrier_state::BUSY - carrier_state::READY --> carrier_state::DISABLED - carrier_state::BUSY --> carrier_state::BUSY - carrier_state::READY --> carrier_state::READY - carrier_state::BUSY --> carrier_state::DISABLED - carrier_state::READY --> carrier_state::DISABLED - -``` - -The diagram illustrates the state transitions for carrier parameters. It consists of three main states: **carrier\_state::DISABLED**, **carrier\_state::BUSY**, and **carrier\_state::READY**. **carrier\_state::DISABLED** contains **carrier\_active::INACTIVE**. **carrier\_state::BUSY** contains **carrier\_active::ACTIVE** and **carrier\_active::INACTIVE**. **carrier\_state::READY** contains **carrier\_active::ACTIVE** and **carrier\_active::SLEEP**. Transitions are labeled with O-DU controlled carrier activation (active->ACTIVE), O-DU controlled carrier deactivation (active->INACTIVE), carrier going to sleep (active->SLEEP), and O-RU autonomous recovery action for faults where carrier deactivation is needed (FAULTY CASE). - -State transition diagram for carrier parameters. States include carrier\_state::DISABLED, carrier\_state::BUSY, and carrier\_state::READY. Transitions are labeled with O-DU controlled carrier activation/deactivation and O-RU autonomous recovery actions. - -**Figure 15.3.2-1: Diagram showing all possible transitions and combination of "active" and "state" parameters** - -NOTE: BUSY state is only available during transition and existence of this state depends on internal O-RU design. - -### 15.3.3 Carrier state's relationship to synchronization state - -#### 15.3.3.1 Synchronization state and carrier state transitions - -The O-RU shall update **tx-array-carrier** and **rx-array-carrier** states based on the O-RU's **sync-state**. The flow chart shown in Figure 15.3.3.1-1 illustrate the possible transitions and associated parameters values for the two array-carrier in the possible synchronization state. When the O-RU implements **HOLDOVER**, **tx-array-carrier** and **rx-array-carrier** possible states and transitions shall be the same for **sync LOCKED** and **HOLDOVER** mode. When O-RU transitions to the **FREE RUN** state the only possible **tx-array-carrier** and **rx-array-carrier** state is **DISABLE/INACTIVE**. Figure 15.3.3.1-1 shows possible transitions and according to parameters value combination. - -![State transition diagram for carrier states based on synchronization states (sync::LOCKED, sync::FREE RUN, sync::HOLDOVER).](60ce0fc249173a32463028d12805feca_img.jpg) - -The diagram illustrates the relationship between synchronization states and carrier states. It is divided into three main sections based on the **sync-state**: - -- sync::LOCKED** (Yellow background): - - carrier\_state::DISABLED** (Yellow header): Contains **carrier\_active::INACTIVE** (Green box). Transitions to **carrier\_state::BUSY** (O-DU controlled carrier activation (active->ACTIVE)) and to **carrier\_state::READY** (O-DU controlled carrier activation (active->ACTIVE)). A red arrow labeled "FAULTY CASE (other than sync) O-RU autonomous recover action" points to this state from **carrier\_active::SLEEP**. - - carrier\_state::BUSY** (Grey header): Contains **carrier\_active::ACTIVE** (Green box) and **carrier\_active::INACTIVE** (Green box). Transitions from **carrier\_active::ACTIVE** to **carrier\_state::READY** (O-DU controlled carrier deactivation (active->INACTIVE)). Transitions from **carrier\_active::INACTIVE** to **carrier\_state::DISABLED** (O-DU controlled carrier activation (active->ACTIVE)). - - carrier\_state::READY** (Yellow header): Contains **carrier\_active::ACTIVE** (Green box) and **carrier\_active::SLEEP** (Green box). Transitions from **carrier\_active::ACTIVE** to **carrier\_active::SLEEP** (O-DU controlled carrier going to sleep (active->SLEEP)). Transitions from **carrier\_active::SLEEP** to **carrier\_active::ACTIVE** (O-DU controlled carrier activation (active->ACTIVE)). -- sync::FREE RUN** (Yellow background): - - carrier\_state::DISABLED** (Yellow header): Contains **carrier\_active::INACTIVE** (Green box). This is the only state in **FREE RUN** mode. -- sync::HOLDOVER** (Grey background): - - States and transitions are identical to the **sync::LOCKED** section. - -Transitions between **sync** states: - -- sync::LOCKED** to **sync::FREE RUN**: "external sync lost (without HOLDOVER mode)" -- sync::FREE RUN** to **sync::LOCKED**: "external time source restored" -- sync::LOCKED** to **sync::HOLDOVER**: "external time source lost" -- sync::HOLDOVER** to **sync::LOCKED**: "external time source restored" -- sync::HOLDOVER** to **sync::FREE RUN**: "Holdover time elapsed" - -State transition diagram for carrier states based on synchronization states (sync::LOCKED, sync::FREE RUN, sync::HOLDOVER). - -Figure 15.3.3.1-1: Combination of tx-array-carrier/rx-array-carrier transitions and allowed states compared to sync state - -When an O-RU changes its synchronization state **sync-state** to FREERUN, it shall perform carrier deactivation of all active **tx-array-carrier(s)** and **rx-array-carrier(s)**. The O-RU shall communicate the **synchronization-state-change**, **tx-array-carriers-state-change** and **rx-array-carriers-state-change** notifications to all notification subscribers. - -The following two sections describe the tx-array-carrier/rx-array-carrier behaviour and O-RU/O-DU communication when synchronization is lost, and when synchronization is restored. - -### 15.3.3.2 Synchronization lost and HOLDOVER mode expired - -Figure 15.3.3.2-1 shows the **tx-array-carrier** and **rx-array-carrier** behaviour and illustrates the communication between the O-RU and O-DU when O-RU lose synchronization and enters to FREERUN mode. The process can be divided into 5 steps as shown in Figure 15.3.3.2-1 and briefly described below. - -- 1) If the O-RU implements the optional HOLDOVER state, once the O-RU detects that it has lost connection to its timing source and its **sync-state** moves to HOLDOVER, the O-RU will send a **synchronization-state-change** notification to one (or more) subscribed O-DU(s) indicating that the O-RU is in HOLDOVER. If the O-RU does not implement HOLDOVER, then this step is skipped. -- 2) After the O-RU HOLDOVER timer expires, or if the O-RU does not implement HOLDOVER, the O-RU moves the **sync-state** to FREERUN. -- 3) The O-RU sends a **synchronization-state-change** notification to all subscribed O-DUs indicating that the O-RU is in FREERUN. -- 4) The O-RU deactivates all active array-carriers, stops RF transmission and ceases sending traffic to O-DU. - -![Sequence diagram showing the 'Synchronisation lost' scenario between an O-RU and an O-DU. The O-RU detects a lost external timing source, switches to HOLDOVER mode, and notifies the O-DU. When HOLDOVER expires, the O-RU changes its sync-state to FREERUN and notifies the O-DU. Finally, the O-RU autonomously deactivates all its carriers.](16c8aea7b68120358abcb5ef6ef3ae0b_img.jpg) - -### Synchronisation lost - -``` - -sequenceDiagram - participant O-RU - participant O-DU - Note left of O-RU: State of carriers is: - -ACTIVE -READY - - -ACTIVE -READY - - Note right of O-RU: Problem happened -external timing source has been lost. - opt When internal clock allows for HOLDOVER mode - Note left of O-RU: Notification about -external timing source lost -and switch device -to HOLDOVER mode - O-RU->>O-DU: - -[1] HOLDOVER - - - Note right of O-RU: Time when internal clock is in HOLDOVER - Note left of O-RU: HOLDOVER expired - end - Note left of O-RU: Notification about -sync-state change - O-RU->>O-DU: [2] sync-state changed to FREERUN - Note left of O-RU: Notification about -sync-state change - O-RU->>O-DU: - -[3] FREERUN - - - Note right of O-RU: [4] O-RU triggers deactivation of all it's carriers autonomously, -For deactivation of a carrier, see figure 15.3.2-0b - -``` - -Sequence diagram showing the 'Synchronisation lost' scenario between an O-RU and an O-DU. The O-RU detects a lost external timing source, switches to HOLDOVER mode, and notifies the O-DU. When HOLDOVER expires, the O-RU changes its sync-state to FREERUN and notifies the O-DU. Finally, the O-RU autonomously deactivates all its carriers. - -Figure 15.3.3.2-1: Synchronisation lost scenario - -### 15.3.3.3 External timing source restored - -Figure 15.3.3.3-1 shows how **tx-array-carrier** and **rx-array-carrier** can be reactivated when external timing source is restored, and it illustrates the communication between O-RU and O-DU to restore operation between O-RU and O-DU. - -The restoration process can be divided into 4 steps as shown in Figure 15.3.3.2-1 and described below. - -- 1) Once the O-RU detects that synchronization has been restored, it changes the sync-state to LOCKED, and then sends a **synchronization-state-change** notification to all subscribed O-DUs. -- 2) The O-RU then waits for the O-DU reaction. -- 3) O-DU triggers activation of all O-RUs carriers. For activation of a carrier, see figure 15.3.2-0a. - -![Sequence diagram showing the restoration process between an O-RU and an O-DU. The O-RU detects restored synchronization, changes its state to LOCKED, and sends a notification to the O-DU. The O-DU then triggers the activation of all carriers for the O-RU.](3893e26cb0b95e076fdc8953d2db0072_img.jpg) - -### Synchronisation restored and carrier reactivation - -``` - -sequenceDiagram - participant O-RU - participant O-DU - Note left of O-RU: State of carriers is: - -INACTIVE -DISABLED - - -INACTIVE -DISABLED - - Note left of O-RU: External timing source restored - Note left of O-RU: Notification about External timing source restored - O-RU->>O-DU: - -[1] LOCKED - - - Note right of O-DU: [2] Waiting O-DU reaction - Note right of O-DU: [3] O-DU triggers activation of all carriers for the O-RU, -For activation of a carrier, see figure 15.3.2-0a - -``` - -Sequence diagram showing the restoration process between an O-RU and an O-DU. The O-RU detects restored synchronization, changes its state to LOCKED, and sends a notification to the O-DU. The O-DU then triggers the activation of all carriers for the O-RU. - -Figure 15.3.3.3-1: Synchronisation restored and carrier reactivation scenario - -## 15.4 Beamforming - -### 15.4.1 Beamforming configuration - -The beamforming functionality allows the O-RU to influence the angle of the main lobe of the signal which is radiated from/received by the O-RU. Beamforming support is optional, and an O-RU shall indicate that it supports such functionality by indicating that it supports the "urn:o-ran:beamforming:x.y" namespace. - -A multi-band capable O-RU shall be able to support independent beamforming configuration on each of its supported **tx-arrays** and/or **rx-arrays** depends on O-RU antenna configuration. - -An O-RU indicates the support of a beamforming mode of operation per endpoint. Endpoints capable of either BF or non-BF operation are distinguished by the capabilities exposed by endpoint-types in endpoint-beam-capacity grouping. - -Arrays capable of BF operation are distinguished by the relation to the endpoints and the reference from o-ran-beamforming yang module. - -## 15.4.2 Pre-defined beamforming configuration - -In case the O-RU supports beamforming, the o-ran-beamforming.yang and o-ran-uplane-conf.yang modules are used to report the pre-defined relationship between supported beams to a NETCONF client. A **capabilities-group** is used to uniquely identify separate **tx-arrays** and/or **rx-arrays** supported by an O-RU with the beamforming configuration referencing the set of **tx-arrays** and **rx-arrays** that are associated with this **capabilities-group**. - -A default service area of the O-RU is determined as the grid of pre-defined beams. When O-RU updates beamforming configuration as described in 15.4.3, the grid of pre-defined beams can be newly defined. In this case, the default service area is changed accordingly. - -O-RU may support new service area by applying tilt-offset to the given default service area in elevation and/or azimuth domains as described in 15.4.3. - -## 15.4.3 Beamforming configuration update - -This clause provides the method to modify and to apply the beamforming configuration (weights, attributes and/or beam properties). The modification of the beamforming information is allowed only if O-RU supports the feature "MODIFY-BF-CONFIG" used for defining the modification of beamforming configuration. - -The beamforming configuration is stored in the O-RU and comes from the O-RU's software, treated in clause 8. The O-RU shall locate the beamforming configuration file in the generic folder, i.e. O-RAN/beamforming/ or o-ran/beamforming/. - -To modify the beamforming configuration, the following steps are applied. - -- 1) NETCONF client can retrieve the file list of the O-RU's folder: O-RAN/beamforming/ or o-ran/beamforming/. -- 2) NETCONF client can trigger the upload of the beamforming configuration file from the O-RU's folder. -- 3) Operator can recover the uploaded file and edit the beamforming configuration file offline. -- 4) NETCONF client can download the file to the original folder. - -The modified beamforming configuration file shall not have the same name as any other file in the folder. Its file name is the matter of implementation. - -The beam properties in o-ran-beamforming YANG module contain **coarse-fine**, **coarse-fine-beam-relation** and **neighbour-beam** for each **beam-id**. This information is received from the O-RU as O-RU's capability at O-RU start-up and typically are used by the scheduler in O-DU. A NETCONF client (O-RU Controller) can modify the beamforming information via file described in this clause. When the beamforming configuration (weight, attribute and beam properties) is modified via file, the configuration of the beam properties list in the o-ran-beamforming YANG module should be modified together via the same file if affected by the modified weight and/or attribute. - -An O-RU supporting the modification of beamforming configuration shall support the storage of at least two beamforming files per **capabilities-group** supported. For each **capabilities-group**, one file corresponds to the pre- - -defined (factory, read-only) beamforming configuration and at least one file corresponds to a modified (read-write) beamforming file. The O-RU has the responsibility to remove existing file and prepares space for new file when the NETCONF client **file-download** rpc is issued. When the O-RU only supports the storage of a single modified (read-write) beamforming file per band of operation, i.e. **number-of-writeable-beamforming-files** (sic) = 1 the **file-download** operation for the modified beamforming configuration needs to be done while neither **tx-array-carriers** nor **rx-array-carriers** are configured in the O-RU to avoid the removal of the modified beamforming configuration file for the current active software. - -If the O-RU supports the capability to store two or more modified beamforming configuration files per band of operation in the O-RU, i.e. **number-of-writeable-beamforming-files** > 1, the NETCONF **file-download** operation can be performed without any timing limitation. That's because the modified beamforming configuration file for the current beamforming configuration can be kept during the **file-download** operation. To apply the new modified beamforming configuration, the following steps are applied: - -- 1) The NETCONF client can download the file to the beamforming folder if the O-RU supports the capability **number-of-writeable-beamforming-files** > 1. -- 2) If the O-RU doesn't support **in-service-bf-update**, the NETCONF client shall deactivate **tx-array-carriers** and **rx-array-carriers** in the U-Plane configuration by setting "INACTIVE" for the **active** parameters if they are ACTIVE. When the supported capability **in-service-bf-update** is advertised by the O-RU, and if the NETCONF client supports the beamforming configuration update in service, the NETCONF client can activate the modified beamforming configuration without deactivating and deleting **tx-array-carriers** and **rx-array-carriers** in the U-Plane configuration. -- 3) Optionally, the NETCONF client shall delete **tx-array-carriers** and **rx-array-carriers** and the capability **in-service-bf-update** shall not be supported, if O-RU does not support the capability **update-bf-non-delete**. -- 4) Alternatively, the NETCONF client can trigger the download of the modified beamforming configuration file to the folder if the O-RU's capability is **number-of-writeable-beamforming-files** = 1. -- 5) Regardless of whether or not to deactivate **tx-array-carriers** and **rx-array-carriers**, the NETCONF client shall activate the modified beamforming configuration by using: - - **activate-beamforming-config-by-capability-group** rpc and selecting the modified beamforming configuration file and the **capabilities-group** for which this modified configuration applies. -- 6) If a NETCONF client subscribes to the notification **capability-group-beamforming-information-update** in advance, the O-RU sends such notification to the notification subscriber. Then the NETCONF client can subsequently retrieve beam properties in o-ran-beamforming YANG module via NETCONF operation. If the O-RU supports **in-service-bf-update** and completes the update beamforming, and the O-RU applies the new update beamforming information to the **tx-array-carriers** and **rx-array-carriers**, the O-RU sends the notification to the NETCONF client that have subscribed to receive the notification. - -NOTE: In service updating of beamforming weights without carrier deactivation entails an uncertainty of beamforming weight usage limited to the time between O-RU sending notifications to the time the NETCONF client receives the notification. This uncertainty could cause an interruption of user data traffic, so should be done with caution. Disabling the active carriers prior to making any configuration changes and then re-enabling the carriers after configuration changes are completed does not involve this uncertainty. - -- 7) Optionally, the NETCONF client shall create **tx-array-carriers** and **rx-array-carriers** again, if the O-RU does not support the capability **update-bf-non-delete**. -- 8) The NETCONF Client shall activate **tx-array-carriers** and **rx-array-carriers** in the U-Plane configuration by setting "ACTIVE" for **active** parameters. If the NETCONF client did not deactivate **tx-array-carriers** and **rx-** - -**array-carriers** (in the step 2 of the procedure), the NETCONF client doesn't need to activate **tx-array-carriers** and **rx-array-carriers**. - -Then the new edited beamforming information is applied to the new **tx-array-carriers** and **rx-array-carriers** in the U-Plane configuration. - -[Abnormal handling] If the O-RU fails to activate the edited beamforming configuration file correctly, i.e. rpc error for rpc **activate-beamforming-config-by-capability-group**, the O-RU shall revert back to the pre-defined/factory beamforming configuration file and report this to the NETCONF client. - -At the **reset** rpc, the beamforming configuration information is switched to the pre-defined beamforming configuration. Even though the reset operation is issued, the O-RU may store the modified beamforming configuration file in the folder, which is not used, if O-RU supports the capability **persistent-bf-files** to store them in the reset-persistent memory. - -The file format of the beamforming configuration is O-RU implementation specific. - -Figures 15.4.3-1 and 15.4.3-2 show two methods to successfully modify the file of beamforming configuration information plus the method how to apply the modified file for beamforming configuration conformation to use. - -![Sequence diagram showing the method to modify the file of beamforming configuration information. It involves a NETCONF Server/(O-RU) and a NETCONF Client. The steps are: 1. Client sends 'retrieve-file-list of the beamforming config information from O-RU' to Server. 2. Server responds with 'file-upload of the beamforming config information from O-RU'. 3. Client performs 'edit beamforming config in the file offline' (shown as an internal step). 4. Client sends 'file-download of the beamforming config information to O-RU' to Server. The diagram uses yellow boxes for messages and dashed lines for the sequence flow.](2411409f3e88d90b892db534d525cfa7_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client - participant Server as NETCONF Server/(O-RU) - Note right of Client: retrieve-file-list of the beamforming config information from O-RU - Client->>Server: retrieve-file-list... - Note right of Server: file-upload of the beamforming config information from O-RU - Server-->>Client: file-upload... - Note right of Client: edit beamforming config in the file offline - Note right of Client: file-download of the beamforming config information to O-RU - Client->>Server: file-download... - -``` - -Sequence diagram showing the method to modify the file of beamforming configuration information. It involves a NETCONF Server/(O-RU) and a NETCONF Client. The steps are: 1. Client sends 'retrieve-file-list of the beamforming config information from O-RU' to Server. 2. Server responds with 'file-upload of the beamforming config information from O-RU'. 3. Client performs 'edit beamforming config in the file offline' (shown as an internal step). 4. Client sends 'file-download of the beamforming config information to O-RU' to Server. The diagram uses yellow boxes for messages and dashed lines for the sequence flow. - -**Figure 15.4.3-1: Method to Modify the File of Beamforming Configuration Information** - -![Sequence diagram showing the interaction between an O-RU/NETCONF Server and a NETCONF Client/Notification Subscriber for beamforming configuration updates.](cfb616f789aa01c087849ad7701e64d7_img.jpg) - -``` - -sequenceDiagram - participant O-RU/NETCONF Server - participant NETCONF Client/Notification Subscriber - - alt number-of-writeable-beam-forming-files > 1 - Note right of O-RU/NETCONF Server: file-download of the beamforming config information to O-RU - opt if in-service-bf-update != TRUE - Note left of NETCONF Client/Notification Subscriber: apply modified beamforming config information in service - NETCONF Client/Notification Subscriber->>O-RU/NETCONF Server: INACTIVE for "tx-array-carriers" and "rx-array-carriers" - O-RU/NETCONF Server-->>NETCONF Client/Notification Subscriber: OK - opt if update-bf-non-delete = FALSE - Note left of NETCONF Client/Notification Subscriber: apply modified beamforming config information in service - NETCONF Client/Notification Subscriber->>O-RU/NETCONF Server: delete "tx-array-carriers" and "rx-array-carriers" - O-RU/NETCONF Server-->>NETCONF Client/Notification Subscriber: OK - alt number-of-writeable-beam-forming-files = 1 - Note right of O-RU/NETCONF Server: file-download of the beamforming config information to O-RU - NETCONF Client/Notification Subscriber->>O-RU/NETCONF Server: "modified file of beamforming config information" "band" - O-RU/NETCONF Server-->>NETCONF Client/Notification Subscriber: OK - opt in-service-bf-update = TRUE - Note left of NETCONF Client/Notification Subscriber: apply modified beamforming config information in service - opt NETCONF client configures subscription to notification of beamforming-information-update - Note right of NETCONF Client/Notification Subscriber: NETCONF client retrieves the beam properties from O-RU by NETCONF operation - NETCONF Client/Notification Subscriber->>O-RU/NETCONF Server: .. - opt if update-bf-non-delete = FALSE - Note left of NETCONF Client/Notification Subscriber: apply modified beamforming config information in service - NETCONF Client/Notification Subscriber->>O-RU/NETCONF Server: create "tx-array-carriers" and "rx-array-carriers" - O-RU/NETCONF Server-->>NETCONF Client/Notification Subscriber: OK - opt if in-service-bf-update != TRUE - Note left of NETCONF Client/Notification Subscriber: apply modified beamforming config information not in service - NETCONF Client/Notification Subscriber->>O-RU/NETCONF Server: ACTIVE for "tx-array-carriers" and "rx-array-carriers" - O-RU/NETCONF Server-->>NETCONF Client/Notification Subscriber: OK - -``` - -Sequence diagram showing the interaction between an O-RU/NETCONF Server and a NETCONF Client/Notification Subscriber for beamforming configuration updates. - -Figure 15.4.3-2: Method to Apply the modified file for Beamforming Configuration Information - -### 15.4.4 Tilting pre-defined beams - -This clause describes the optional capability by which the O-RU's pre-defined beams may be tilted by using the **"BEAM-TILT"** feature defined in the o-ran-beamforming YANG model. This capability is an O-RU specific functionality, enabling adaptation of the service area associated with an O-RU without the need for operation of additional ALDs described in clause 14, or modifying the beamforming configuration using the **"MODIFY-BF-CONFIG"** feature described in clause 15.4.3. - -NOTE 1: The operation of the feature **"BEAM-TILT"** is independent to the operation of the **"MODIFY-BF-CONFIG"**. When the **"MODIFY-BF-CONFIG"** feature is used to define a new default service area, the **"BEAM-TILT"** feature can be used to apply tilt-offsets to the newly defined service area. - -O-RU can change the service area by applying a tilt-offset to the elevation and/or azimuth pointing angles for the pre-defined beams. This feature allows to shift beam characteristic of all predefined-beams in elevation and/or azimuth direction (i.e. changing the service area or sector coverage) while preserving the beam adjacency among the beams within grid of beams. - -NOTE 2: **elevation-tilt-offset-angle** values smaller than 0 represents an up-shift of the default service area towards the zenith (i.e. corresponding to a decrease in zenith angle) and values larger than 0 represent a down-shift of the default service area away from the zenith (i.e. corresponding to an increase in zenith angle). - -Figure 15.4.4-1 shows the sequence diagram for predefined-beam-tilt-offset-information. To shift service area of the O-RU in a different direction, O-RU controller shall check whether the O-RU supports feature BEAM-TILT feature during capabilities negotiation of the NETCONF session. In the case that O-RU supports the **BEAM-TILT** feature, the O-RU shall ensure that at least one of the **elevation-tilt-offset-granularity** and **azimuth-tilt-offset-granularity** is greater than zero value from O-RU. Tilting is a per band operation and hence the parameters are defined per band. If O-RU supports **BEAM-TILT** feature, O-RU controller can configure the values of **elevation-tilt-offset-angle** and/or **azimuth-tilt-offset-angle** and the configuration values should meet the ranges and granularity information retrieved from **predefined-beam-tilt-offset-information**. - -![Sequence diagram showing the interaction between NETCONF Server/(O-RU) and NETCONF Client/(O-DU) for predefined-beam-tilt-offset capability negotiation.](97f6670a8f097f23fe35d62b76d75cf0_img.jpg) - -``` - -sequenceDiagram - participant Server as NETCONF Server/(O-RU) - participant Client as NETCONF Client/(O-DU) - Note over Client: Predefined-beam-tilt-offset capability Request - Client->>Server: [1] .. - Note over Server: Predefined-beam-tilt-offset capability Response - Server->>Client: [2] .... - -``` - -Sequence diagram showing the interaction between NETCONF Server/(O-RU) and NETCONF Client/(O-DU) for predefined-beam-tilt-offset capability negotiation. - -**Figure 15.4.4-1: Sequence diagram for predefined-beam-tilt-offset-information** - -Depending on O-RU's implementation, the O-RU may need some time to complete the change of service area according to the updated **elevation-tilt-offset-angle** and/or **azimuth-tilt-offset-angle** for a particular **band-number**. The O-RU shall report its capability via the parameter, **run-time-tilt-offset-supported**. For O-RU with **run-time-tilt-offset-supported** = *FALSE*, changing the values in **elevation-tilt-offset-angle** and/or **azimuth-tilt-offset-angle** for a specific band shall be allowed only if all **tx-array-carriers/rx-array-carriers** corresponding to the band is *INACTIVE*. When the service area change is completed in O-RU, the O-RU delivers the notification **predefined-beam-tilt-offset-complete** to inform the O-RU Controller which then may request to activate **tx-array-carriers/rx-array-carriers** in O-RU. For O-RU with **run-time-tilt-offset-supported** = *TRUE*, neither changing the state of **tx-array-carriers/rx-array-carriers** nor delivering notification **predefined-beam-tilt-offset-complete** is required. - -![Sequence diagram showing interactions between O-RU/NETCONF Server and NETCONF Client/Notification Subscriber. The diagram includes steps for changing tx-array-carriers to INACTIVE, modifying predefined beam tilt offsets, and then changing tx-array-carriers to ACTIVE.](9a8f8276c7199f1dd9f3754cf60555c6_img.jpg) - -**O-RU/NETCONF Server** **NETCONF Client/Notification Subscriber** - -Change request tx-array-carriers into INACTIVE for the corresponding band-number - -[1] ` - - .. - .. - -` - -Change response tx-array-carriers into INACTIVE for the corresponding band-number - -[2] ` - - .. - .. - -` - -Predefined beam tilt offset change request for the corresponding band-number - -[3] ` - - .. - -` - -Predefined beam tilt offset change response for the corresponding band-number - -[4] ` - - .... - -` - -Re-generating all predefined-beam according to the changed elevation / azimuth angle per band-number in O-RU - -Notification predefined-beam-tilt-offset-complete delivery - -[5] ` - - ... - -` - -Change request tx-array-carriers into ACTIVE for the corresponding band-number - -[6] ` - - .. - .. - -` - -Change response tx-array-carriers into ACTIVE for the corresponding band-number - -[7] ` - - .. - .. - -` - -Sequence diagram showing interactions between O-RU/NETCONF Server and NETCONF Client/Notification Subscriber. The diagram includes steps for changing tx-array-carriers to INACTIVE, modifying predefined beam tilt offsets, and then changing tx-array-carriers to ACTIVE. - -**Figure 15.4.4-2: Procedure for the predefined-beam-tilt-offset** - -## 15.4.5 Dynamic beamforming control option - -As option, O-RU may support dynamic beamforming control mode. Support for this type of beamforming control can be recognized in the case of weights-based dynamic beamforming from value of parameter rt-bf-weights-update-support (TRUE), and in the case of attributes-based dynamic beamforming from the value of parameter beamforming-trough-attributes-supported (TRUE), in o-ran-beamforming.yang module - -In dynamic beamforming control mode DU updates content of lookup table in O-RU using eCPRI C-Plane messages. For details of eCPRI messaging, see ORAN-WG4.CUS specification, clause "Scheduling and Beamforming Commands". - -Dynamically updated content of lookup table is further addressed by DU in the same way as it is done for static beamforming - by requesting particular Beam ID to be applied. - -In case dynamic beamforming control is supported, O-RU indicates following supplementary information using parent leaf "static-properties" in o-ran-beamforming.yang module: - -- beamforming type (frequency domain, time domain, hybrid). -- beamforming weight compression format (optional). -- available range of Beam IDs, that can be dynamically updated by DU. -- supported time and frequency granularity for time domain and hybrid beamforming control. - -NOTE: Neighbourhood relations between beams produced by beam IDs controlled by DU are unknown to O-RU, hence are not exposed. - -In the case of weights-based dynamic beamforming, to properly calculate beamforming weights DU needs to know antenna array geometry. This information DU obtains by reading the content of o-ran-uplane-conf.yang (list of tx-arrays and rx-arrays with their child parameters). Details of beamforming weight calculations are not a subject for M-Plane activity and as such are intentionally not covered in the present document. - -## 15.4.6 Multiple beamId tables support - -### 15.4.6.1 Introduction - -The O-RU may choose to support multiple beamId tables instead of supporting a single global beamId table in the O-RU by advertising O-RU support for M-Plane feature **MULTIPLE-BEAMID-TABLES-SUPPORTED**. The O-DU may choose to enable or disable this feature using the O-DU configurable flag **multiple-beamId-tables-support-enabled**. - -### 15.4.6.1 O-RU advertised parameters and restrictions - -- 1) The maximum number of beamId tables which can be supported by the O-RU is advertised by the O-RU using the parameter **max-beamId-tables-supported** within **ru-capabilities**. - -NOTE: If **max-beamId-tables-supported** is advertised as 1, it implies that O-RU supports single global beamId table. - -- 2) Each beamId table is identified by a unique beamId table index. Multiple beamId tables supported by the O-RU are expected to be linearly indexed from 1 to 255. The list of beamId tables supported are advertised by the - -O-RU using a leaf-list **tx-array-beamId-table-indexes/rx-array-beamId-table-indexes** per capabilities[] list entry per tx-array and per rx-array respectively. - -- 3) The maximum number of entries advertised by the O-RU in the leaf-list **tx-array-beamId-table-indexes/rx-array-beamId-table-indexes** shall be restricted by the O-RU level parameter **max-beamId-tables-supported** advertised by the O-RU which is a global value for the entire O-RU. - -#### 15.4.6.2 O-DU configuration and restrictions - -- 1) When O-DU configures tx-array-carrier and/or rx-array-carrier, O-DU shall associate **configured-tx-beamId-table-index/configured-rx-beamId-table-index** with each tx-array-carrier and/or rx-array-carrier respectively. -- 2) The O-DU configured [tr]x-array-carrier(s) are expected to be configured based on parameters specified in capabilities[] list and hence **configured-[tr]x-beamId-table-index** value used for a given [tr]x-array-carrier is expected to be chosen from leaf-list **[tr]x-array-beamId-table-indexes** advertised by the O-RU per tx-array/rx-array. - -#### 15.4.6.3 Restrictions, assumptions, and other impacts - -- 1) To ensure that legacy single beamId table is also supported by the O-RU after O-DU enables the feature **MULTIPLE-BEAMID-TABLES-SUPPORTED**, the first list entry in **tx-array-beamId-table-indexes/rx-array-beamId-table-indexes** shall always point to default global beamId table which shall be of size 32767. -- 2) O-RU shall use the beamId table configured for the array carrier associated with the endpoint receiving the beamId value in a C-plane message. -- 3) Per beamforming method beamId range is defined separately per beamId table. The new ranges are defined in defined in o-ran-beamforming.yang as a leaf-list parameter **beamforming-params-for-mul-beamId-tables** advertised by the O-RU. The range values **initial-beam-id** and **max-number-of-beam-ids** defined for each beamforming type shall be same for each beamId table supported by the O-RU. Since the first list entry points to the global beamId table, the first entry in **beamforming-params-for-mul-beamId-tables** shall contain ranges for the global beamId table. - -### 15.5 Antenna calibration - -#### 15.5.1 Background - -Some antennas need to be calibrated to ensure their intended performance. Antenna calibration operation is an optional capability whose operation is dependent on O-RU design, i.e. different O-RUs may support different types of calibration, periodic vs on-demand, different calibration duration, short/medium/long, etc. In this clause, a common framework is defined which can accommodate various types of antenna calibration implementations. - -In this framework, the NETCONF client (O-DU) retrieves resource requirements for antenna calibration operation, e.g. timing and number of iterations/steps, from O-RU by getting the **antenna-calibration-capabilities** container defined in the o-ran-antenna-calibration YANG model. The O-DU can subscribe to **antenna-calibration-required** notifications to receive indications from the O-RU that calibration is required. When the O-RU indicates antenna calibration is required, or when the NETCONF Client decides to calibrate the O-RU, the NETCONF Client allocates time resources for antenna calibration and configures them in the O-RU using the **start-antenna-calibration** RPC request. The NETCONF client shall allocate the time resources for the calibration operation ensuring that these meet the minimum time necessary as reported by the O-RU using the **antenna-calibration-capabilities**. When available, the NETCONF client (O-DU) shall ensure that the frequency resources indicated in the **dl-calibration-frequency-chunk** and **ul-** - -**calibration-frequency-chunk** lists in the **antenna-calibration-required** notification are reserved for calibration operation, otherwise the NETCONF client shall consider that the full bandwidth of the carrier is being reserved for calibration operation. - -The O-RU shall perform antenna calibration operation using the time resources allocated in the **start-antenna-calibration** RPC and frequency resources declared in **antenna-calibration-required** notification and shall notify the completion of the antenna calibration operation to the notification subscriber. The O-DU should be configured to not schedule user data using the time frequency resources identified for antenna calibration operation. The O-DU may schedule data during calibration operation using time frequency resources not identified for calibration operation. When the O-DU is scheduling user data during calibration process using resources not used for calibration, it shall only schedule DL user data in DL calibration symbols and UL user data in UL calibration symbols. - -## 15.5.2 Overall operation - -### 15.5.2.1 General - -During the O-RU "start-up" procedure, the NETCONF client (O-DU) retrieves the O-RU's antenna calibration capability information including antenna calibration capability related parameters defined in o-ran-antenna-calibration.yang model. These parameters describe the O-RU's time resource requirements for calibration and the O-RU's capability of performing "self-calibration". The O-RU time resource requirements are described using the parameters **number-of-calibration-symbols-per-block-dl** and **number-of-calibration-symbols-per-block-ul**. One symbol block corresponds to a set of consecutive symbols in time required for the calibration operation, and it is the basic time unit of calibration. Sets of symbol blocks are grouped into one calibration step and the O-RU shall indicate how many symbol blocks constitute one calibration step using the **number-of-calibration-blocks-per-step-dl** and **number-of-calibration-blocks-per-step-ul** parameters. The O-RU indicates these parameters separately for downlink and uplink calibration. The O-RU shall also indicate the minimum time gap required between consecutive symbol block allocations (**interval-between-calibration-blocks**), number of calibration steps needed (**number-of-calibration-steps**) and the minimum required time gap between consecutive calibration step allocations (**interval-between-calibration-steps**). Based on these parameters, the O-DU shall be able to allocate the time resources required for antenna calibration operation meeting the necessary time resources indicated by the O-RU. If the O-RU supports mixed numerology, the highest possible numerology supported by the O-RU shall be used as the common reference per component carrier according to the CUS plane definition for slot indexing with mixed numerologies. - -### 15.5.2.2 Initiation - -Either the O-RU or O-DU may initiate calibration operation. The trigger condition for the O-DU and/or O-RU to initiate calibration is out of scope of the present document. The NETCONF client is assumed to have subscribed to the notifications defined in the o-ran-antenna-calibration YANG model. When an O-RU determines that it needs to perform antenna calibration operation, it notifies the notification subscriber using the notification **antenna-calibration-required**, including a list of frequency ranges corresponding to the minimum frequency resources required for calibration, or, when the O-RU supports the optional O-RU-COORDINATED-ANT-CAL feature, by using the **antenna-calibration-coordinated** notification. - -Upon reception of the **antenna-calibration-required** notification, the O-DU can allocate time frequency resources for calibration and can send the **start-antenna-calibration** RPC request, including the time resource allocation information for the antenna calibration. This operation is referred as 'O-RU initiated antenna calibration' operation. - -When **coordinated-calibration-support** is set to true, this indicates that the O-RU is able to determine a priori the time-frequency resources required for antenna self-calibration and the O-RU uses **antenna-calibration-coordinated** notification to indicate these to the O-DU instead of **antenna-calibration-required** notification. When the coordinated-calibration is supported and permitted, i.e. **coordinated-calibration-support** is true and **coordinated-calibration-allowed** is true, the O-RU may perform a coordinated self-calibration procedure. An O-RU may also report the optional - -capability of configured-preparation-timer-supported which indicates that it supports configuration of the preparedness timer that controls how far in advance of the coordinated self-calibration procedure the O-RU is required to send the notification of impacted resources. If configured by the NETCONF Client, the O-RU shall send the **antenna-calibration-coordinated** notification at least **coordinated-ant-calib-prep-timer** seconds before the operation of the coordinated antenna calibration procedure. If such an optional capability is not supported, the O-RU shall indicate that time-frequency resources are sent to a subscribed O-DU at least 60 seconds before the operation of the coordinated antenna calibration procedure. SFN wrap around will occur multiple times during these 60 seconds, this is handled according to statements in clause 15.5.2.4. - -The O-DU shall not send a **start-antenna-calibration** RPC request when a coordinated antenna calibration period is in progress. The O-RU is allowed to reject such a request if it is received during a coordinated antenna calibration period. An O-DU receiving an **antenna-calibration-coordinated** notification can beneficially use the indicated time-frequency resources to adapt its operation during the antenna calibration operation, e.g. consider the time-frequency resources as reserved for calibration. If no UL and/or DL frequency-chunk lists are provided in the notification, the O-DU may consider the full bandwidth of all configured UL and/or DL carriers reserved for calibration operation. If such U-Plane resources are scheduled by the O-DU, the operation of the O-RU may be degraded, including performance of the calibration procedure and handling of DL and UL U-plane traffic and any associated performance counters. - -The O-DU may also autonomously initiate calibration operation, using the same **start-antenna-calibration** RPC request, i.e. without receiving the **antenna-calibration-required** notification message from O-RU. This operation is referred as 'O-DU initiated antenna calibration' operation. If the O-RU has indicated the need for the calibration through sending the **antenna-calibration-required** notification, the O-DU shall consider that the use of frequency resources indicated using frequency range list within the notification as being affected during the calibration operation and if no frequency list is available, consider the full bandwidth of all configured carriers reserved is affected during calibration. - -After receiving "**start-antenna-calibration** RPC request" (antenna calibration start command), the O-RU shall send an RPC reply (antenna calibration start response) including ACCEPTED status to the NETCONF client, if the O-RU is able to start the calibration operation according to the time resources allocation information in the RPC request. Otherwise, the O-RU shall include a REJECTED status in the RPC reply, with a suitable error reason such as "resource mask mismatch with O-RU antenna calibration capability", "overlapped DL and UL masks", "insufficient memory", "O-RU internal reason" (if no other error reason matches the error condition) etc. If the O-RU does not receive a **start-antenna-calibration** RPC request within 60 seconds after triggering the sending of the first **antenna-calibration-required** notification, the O-RU shall raise a major alarm "Triggering failure of antenna calibration" (see clause A for fault details). After the alarm is raised, the O-RU may resend the **antenna-calibration-required** notification multiple times. The O-RU shall not re-send the **antenna-calibration-required** notification in periods shorter than 60 seconds. - -### 15.5.2.3 Self-calibration operation - -When the alarm "triggering failure of antenna calibration" alarm remains uncanceled, if self-calibration is supported and permitted, i.e. **self-calibration-support** is true and **self-calibration-allowed** is true, the O-RU may perform a self-calibration procedure. The O-RU shall wait a minimum 60 seconds after raising a major alarm and receiving **no start-antenna-calibration** RPC request from the NETCONF client before initiating its self-calibrate procedure. When self-calibration is not supported or not permitted, i.e. **self-calibration-support** is false or **self-calibration-allowed** is false, the O-RU may upgrade the severity of the alarm to critical according to clause 11.4. - -During the self-calibration, i.e. when O-RU exposes **self-calibration-support** with value TRUE and when O-DU sets **self-calibration-allowed** with value TRUE to O-RU, there could be no coordination of time-frequency resources between the O-RU and O-DU. The O-DU can continue to schedule user data during calibration process using the resources identified in **antenna-calibration-required** notification without impacting the operation of the calibration procedure. Scheduled user data will be affected by ongoing calibration procedure. - -#### 15.5.2.4 Calibration completion - -The O-RU shall indicate completion of all types of calibration procedures (i.e. rpc triggered, self-calibration and co-ordinated self-calibration) using the **antenna-calibration-result** notification (Calibration results) to the notification subscriber. If a self-calibration or co-ordinated self-calibration procedure completes but with **status** set to **FAILURE**, the O-RU may upgrade the severity of the alarm to critical. - -In some situations, SFN wrap around may happen causing O-DU and O-RU to interpret the 'start-sfn' parameter to point to different GPS seconds elapsed since GPS epoch. To avoid this situation, the O-DU may decide not to schedule any user-plane data on the calibration time-frequency resources in all SFN cycles until the O-DU receives an **antenna-calibration-result** notification message from the O-RU. Once the calibration is complete, the O-DU schedules user data and sends C/U-Plane message as in normal operation state. - -#### 15.5.2.5 Antenna calibration procedure - -Figure 15.5.2.5-1 shows the overall operation for antenna calibration. - -![Sequence diagram showing the interaction between a NETCONF Server (O-RU) and a NETCONF Client (O-DU) for antenna calibration. The sequence includes: 1. Antenna Calibration capability Information Request (get antenna-calibration-capabilities); 2. Antenna Calibration capability Information Response; 3. Configure Request for Self Antenna Calibration Allowed (edit-config self-calibration-policy); 4. Configure Response for Self Antenna Calibration Allowed; 5. Notification antenna-calibration-required delivery (O-RU initiated); 6. Antenna Calibration Start Request (O-DU initiated); 7. Antenna Calibration Start Response; 8. Notification antenna-calibration-result delivery.](b4cbe4bfe7868be70d1549b983749783_img.jpg) - -``` - -sequenceDiagram - participant NETCONF Server/O-RU - participant NETCONF Client/O-DU - - Note right of NETCONF Client/O-DU: Antenna Calibration capability Information Request - NETCONF Client/O-DU->>NETCONF Server/O-RU: .. [1] - Note left of NETCONF Server/O-RU: Antenna Calibration capability Information Response - NETCONF Server/O-RU->>NETCONF Client/O-DU: [2] .. - Note right of NETCONF Client/O-DU: Configure Request for Self Antenna Calibration Allowed - NETCONF Client/O-DU->>NETCONF Server/O-RU: [3] .. - Note left of NETCONF Server/O-RU: Configure Response for Self Antenna Calibration Allowed - NETCONF Server/O-RU->>NETCONF Client/O-DU: [4] .. - Note right of NETCONF Server/O-RU: Notification antenna-calibration-required delivery (O-RU initiated antenna calibration) - NETCONF Server/O-RU->>NETCONF Client/O-DU: [5] .. - Note left of NETCONF Client/O-DU: Antenna Calibration Start Request (O-DU initiated antenna calibration) - NETCONF Client/O-DU->>NETCONF Server/O-RU: [6] > .. - Note right of NETCONF Server/O-RU: Antenna Calibration Start Response (O-RU will perform antenna calibration) - NETCONF Server/O-RU->>NETCONF Client/O-DU: [7] .. - Note left of NETCONF Server/O-RU: Notification antenna-calibration-result delivery - NETCONF Server/O-RU->>NETCONF Client/O-DU: [8] .. - -``` - -Sequence diagram showing the interaction between a NETCONF Server (O-RU) and a NETCONF Client (O-DU) for antenna calibration. The sequence includes: 1. Antenna Calibration capability Information Request (get antenna-calibration-capabilities); 2. Antenna Calibration capability Information Response; 3. Configure Request for Self Antenna Calibration Allowed (edit-config self-calibration-policy); 4. Configure Response for Self Antenna Calibration Allowed; 5. Notification antenna-calibration-required delivery (O-RU initiated); 6. Antenna Calibration Start Request (O-DU initiated); 7. Antenna Calibration Start Response; 8. Notification antenna-calibration-result delivery. - -**Figure 15.5.2.5-1: Overall of antenna calibration operation** - -### 15.5.3 O-RU antenna calibration capability parameter configuration - -The antenna calibration framework is a generic framework designed to support various vendor specific implementations of O-RU calibration. Therefore, the framework does not describe the details of how the O-RU calibrates its antenna, rather it defines a generic framework with necessary message flows and parameters for ensuring that the time and frequency resources required for calibration are coordinated between the O-DU and O-RU. The following parameters describe the O-RU's time resource needed for calibration. - -- **self-calibration-support:** Boolean value indicates whether O-RU is capable of supporting self-calibration. -- **number-of-calibration-symbols-per-block-dl:** indicates how many consecutive symbols are required for DL antenna calibration operation, i.e. the size of DL Symbol-block. -- **number-of-calibration-symbols-per-block-ul:** indicates how many consecutive symbols are required for UL antenna calibration operation, i.e. the size of UL Symbol-block. -- **interval-between-calibration-blocks:** if a time interval is required between consecutive antenna calibration operation, this indicates the required time value as unit of symbols. A common value is used here for the intervals between DL-DL blocks, UL-UL blocks, DL-UL blocks and UL-DL blocks, which is the largest minimum interval required between any two adjacent calibration blocks. It shall be any value that O-RU implementation requires within this parameter range. -- **number-of-calibration-blocks-per-step-dl:** indicates how many blocks are required for one step of DL antenna calibration operation. -- **number-of-calibration-blocks-per-step-ul:** indicates how many blocks are required for one step of UL antenna calibration operation. -- **interval-between-calibration-steps:** if a time interval is required between consecutive steps of antenna calibration operation, define indicates the required time value as unit of radio frames. It can be any value that the O-RU implementation requires within the defined parameter range. -- **number-of-calibration-steps:** shows how many steps is required for whole DL/UL antenna calibration operation. - -Figure 15.5.3-1 shows the relationship between the various antenna calibration capabilities parameters described above. - -![A diagram showing a light blue rounded rectangle containing a smaller, solid orange rectangle on the left side.](ed12f6b9acb5a2066b16f7a2a6d5e2c1_img.jpg) - -A diagram showing a light blue rounded rectangle containing a smaller, solid orange rectangle on the left side. - -**Figure 15.5.3-1: Relationship among Antenna Calibration Capability parameters** - -### 15.5.4 antenna-calibration-required notification parameters - -If the O-RU initiates the calibration operation, the O-RU notifies the notification subscriber (O-DU) using the **antenna-calibration-required** notification message, including the O-RU's frequency resource requirements. The O-RU is able to indicate non-contiguous frequency "chunks" necessary for calibration using the **dl-calibration-frequency-chunk** and - -**ul-calibration-frequency-chunk** lists. These lists use the parameters below to describe the frequency resources required for calibration: - -- **start-calibration-frequency-dl**: indicates the lowest frequency value in Hz of the frequency range is required for DL antenna calibration operation. -- **end-calibration-frequency-dl**: indicates the highest frequency value in Hz of the frequency range is required for DL antenna calibration operation. -- **start-calibration-frequency-ul**: indicates the lowest frequency value in Hz of the frequency range is required for UL antenna calibration operation. -- **end-calibration-frequency-ul**: indicates the highest frequency value in Hz of the frequency range is required for UL antenna calibration operation. - -## 15.5.5 Start-antenna-calibration RPC request parameters - -The NETCONF Client sends the "**start-antenna-calibration** RPC request" including the time resource allocation parameters. These parameters indicate the exact symbols, slots, and frames that can be used for calibration. - -NOTE: Because the NETCONF Client (O-DU) allocates the time resources for calibration with the knowledge of UL and DL configuration, dynamic TDD operation is implicitly supported. - -The resource allocation information about symbol, slot, and frame are indicated using bitmasks for downlink and uplink calibration separately. The start SFN of the first calibration step is sent to the O-RU to synchronise the calibration starting point at both O-DU and O-RU. When indicated, the O-RU shall use the frequency resources indicated using the frequency ranges in the "NETCONF **antenna-calibration-required** notification" message for calibration. - -Table 15.5.5-1 lists the parameters configured in the O-RU using the "**start-antenna-calibration** RPC request". - -**Table 15.5.5-1: Antenna Calibration Parameters** - -| Parameters | Type / Range | Descriptions | -|-------------------------|--------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| symbol-bitmask-dl | string | Bitmask indicating DL calibration symbol within a calibration slot. First character in the string indicates first symbol, next character in the string indicates second symbol and so on. Value 1 indicates that the symbol is allocated for calibration and 0 means the symbol shall not be used for calibration. | -| symbol-bitmask-ul | string | Bitmask indicating UL calibration symbol within a calibration slot. First character in the string indicates first symbol, next character in the string indicates second symbol and so on. Value 1 indicates that the symbol is allocated for calibration and 0 means the symbol shall not be used for calibration. | -| slot-bitmask-dl | string | Bitmask indicating DL calibration slot within a calibration frame. First character in the string indicates first slot, next character in the string indicates second slot and so on. Value 1 indicates that the slot is allocated for calibration and 0 means the slot shall not be used for calibration. | -| slot-bitmask-ul | string | Bitmask indicating UL calibration slot within a calibration frame. First character in the string indicates first slot, next character in the string indicates second slot and so on. Value 1 indicates that the slot is allocated for calibration and 0 means the slot shall not be used for calibration. | -| frame-bitmask-dl | string | Bitmask indicating DL calibration frame within a calibration step. First character in the string indicates first radio frame equal to the start-SFN, next character in the string indicates the next frame and so on. Value 1 indicates that the frame is allocated for calibration and 0 means the frame shall not be used for calibration. | -| frame-bitmask-ul | string | Bitmask indicating UL calibration frame within a calibration step. First character in the string indicates first radio frame equal to the start-SFN, next character in the string indicates the next frame and so on. Value 1 indicates that the frame is allocated for calibration and 0 means the frame shall not be used for calibration. | -| calibration-step-size | uint8 | Number of frames within a calibration step. | -| calibration-step-number | uint8 | Number of calibration steps. | -| start-sfn | uint16 | SFN number of the first calibration step. | - -### 15.5.6 Example antenna calibration operation - -This clause illustrates an example of antenna calibration operation. For simplicity, the O-RU is the initiator in this example, but either O-RU or O-DU could initiate antenna calibration operation. In this example, the TDD configuration is assumed as shown in Figure 15.5.6-1. - -![Diagram of a TDD configuration showing a sequence of slots: DL, DL, DL, F, UL, DL, DL, DL, F, UL, DL, DL, DL, F, UL, DL, DL, DL, F, UL. Above the sequence, a bracket indicates 'one radio frame: 10ms (20 slots)'.](e211ff0e795ca1dbe9216da5d5a6d950_img.jpg) - -Diagram of a TDD configuration showing a sequence of slots: DL, DL, DL, F, UL, DL, DL, DL, F, UL, DL, DL, DL, F, UL, DL, DL, DL, F, UL. Above the sequence, a bracket indicates 'one radio frame: 10ms (20 slots)'. - -**Figure 15.5.6-1: Example of TDD configuration** - -DL = Downlink slot -UL = Uplink slot -F = Flexible slot - -This example illustrates calibration operation where an O-RU requires DL and UL antenna calibration operation in **o-ran-antenna-calibration.yang** with 2 calibration steps; within each step, 64 DL calibration blocks with 4 continuous DL symbols in each calibration block and 32 UL calibration blocks with 1 continuous UL symbol in each calibration block are required. Between each calibration block, a length of minimum 3 symbols interval is required, and a length of minimum 5 frames interval is required between consecutive calibration steps. - -Once antenna calibration operation is required by the O-RU, an **antenna-calibration-required** notification is sent to the notification subscriber (O-DU), including the O-RU's frequency resources requirement in a list of frequency ranges in Hz, which in this example uses a single chunk of frequencies from 1.8GHz to 1.82GHz. The O-DU considers that the frequency range indicated in the **antenna-calibration-required** notification will be subsequently used during antenna calibration. The O-DU allocates time resources for antenna calibration based on the TDD configuration together with the O-RU DL and UL antenna calibration capability, then configure the antenna calibration using the **start-antenna-calibration** RPC request. In this example, 64 DL calibration blocks in each calibration step are allocated in 4 frames, within each frame, 8 DL slots are allocated and within each DL slot, 2 calibration blocks are allocated for DL calibration. In parallel, 32 UL calibration blocks in each calibration step are allocated in 4 frames, within each frame, 4 UL slots are allocated and within each UL slot, 2 calibration blocks are allocated for UL calibration. To guarantee the interval between 2 calibration steps, the size of each calibration step is set to 10 frames. At least 3 symbols interval between each calibration block is also guaranteed in symbol bitmasks. The O-DU may allocate larger intervals than O-RU requires as shown in this example where a 9 symbols interval is allocated instead of the minimum of 3 symbols after second UL symbol block in all UL calibration slots. - -![Sequence diagram showing message exchange between O-RU and O-DU for antenna calibration. The O-RU sends calibration capability information to the O-DU. The O-DU responds with a NETCONF Antenna Calibration Required message. The O-RU then sends an Antenna Calibration Starts message with various parameters.](9ba478ec5af01fd2fb458d145565198e_img.jpg) - -``` - -sequenceDiagram - participant O-RU - participant O-DU - Note left of O-RU: [M-Plane] Startup: O-RU sends calibration capability information (on O-DU's request) - O-RU->>O-DU: [M-Plane] NETCONF Antenna Calibration Required - Note right of O-DU: (start-calibration-frequency-dl = 1800000000 -end-calibration-frequency-dl = 1820000000 -start-calibration-frequency-ul = 1800000000 -end-calibration-frequency-ul = 1820000000) - O-DU->>O-RU: [M-Plane] Antenna Calibration Starts - Note left of O-RU: (start-SFN = 512 -calibration-step-size = 10 -calibration-step-number = 2 -frame-bitmask-dl = 1110100000 -frame-bitmask-ul = 1111000000 -slot-bitmask-dl = 11100100001110000100 -slot-bitmask-ul = 00001000010000100001 -symbol-bitmask-dl = 11110001111000 -symbol-bitmask-ul = 1000100000000000) - -``` - -Sequence diagram showing message exchange between O-RU and O-DU for antenna calibration. The O-RU sends calibration capability information to the O-DU. The O-DU responds with a NETCONF Antenna Calibration Required message. The O-RU then sends an Antenna Calibration Starts message with various parameters. - -**Figure 15.5.6-2: Example of message exchange** - -![Timing diagram showing 'One Calibration Operation' divided into 'Calibration Step#1' and 'Calibration Step#2'. Below are bitmasks for downlink (dl) and uplink (ul) across frame, slot, and symbol levels. The diagram includes annotations for 'interval-between-calibration-step', 'DL Symbol Block', 'Symbol Block interval allocated for DL', 'UL Symbol Block', and 'Symbol Block Interval allocated for UL'.](da29bcd4ce1277e82e278506d03fec24_img.jpg) - -The figure illustrates the time domain bitmask information from an O-DU for antenna calibration. It shows a sequence of bits for frame, slot, and symbol bitmasks for both downlink (dl) and uplink (ul). The calibration operation is divided into two steps, with a specific interval between them. The bitmasks indicate the active resources for each step. - -| Bitmask Type | Bit Sequence | -|-------------------|-----------------------------------------| -| frame-bitmask-dl | 1 1 1 0 1 0 0 0 0 0 1 1 1 0 1 0 0 0 0 0 | -| slot-bitmask-dl | 1 1 1 0 0 1 0 0 0 0 1 1 1 0 0 0 0 1 0 0 | -| symbol-bitmask-dl | 1 1 1 1 0 0 0 1 1 1 1 0 0 0 | -| frame-bitmask-ul | 1 1 1 1 0 0 0 0 0 0 1 1 1 1 0 0 0 0 0 0 | -| slot-bitmask-ul | 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1 | -| symbol-bitmask-ul | 1 0 0 0 1 0 0 0 0 0 0 0 0 0 | - -Timing diagram showing 'One Calibration Operation' divided into 'Calibration Step#1' and 'Calibration Step#2'. Below are bitmasks for downlink (dl) and uplink (ul) across frame, slot, and symbol levels. The diagram includes annotations for 'interval-between-calibration-step', 'DL Symbol Block', 'Symbol Block interval allocated for DL', 'UL Symbol Block', and 'Symbol Block Interval allocated for UL'. - -Figure 15.5.6-3: Time domain bitmask information from O-DU - -### 15.5.7 Calibration with multiple timing resource sets - -The O-RU may indicate its ability to support multiple time resource configuration sets for antenna calibration by support of the feature O-RU-COORDINATED-ANT-CAL-MULTIPLE-TIME-RESOURCE in o-ran-antenna-calibration.yang module. The feature is intended to extend the antenna calibration framework to support multiple time resources instead of single time resource supported. This capability can be used by the O-RU to specify unique calibration time resources for different calibration types. O-RU which supports this capability, exposes a list of time resources (antenna-calibration-multiple-time-resource-list). O-RU indicates desired set of time resources in 'antenna-calibration-multiple-time-resource' notification using specific value of 'antenna-calibration-time-resource-index' parameter. - -This feature applies to O-RU initiated calibration where O-RU supporting this feature can use new notification 'antenna-calibration-multiple-time-resource' containing the parameter 'antenna-calibration-time-resource-index', defined in clause 15.5.8. Based on the index value in the notification respective antenna calibration time resource values should apply while initiating "start-antenna-calibration RPC request". O-RU can use this calibration feature only in case O-DU configured parameter 'coordinated-calibration-multiple-time-resources-allowed' is set to TRUE. - -NOTE: At any point in time only one calibration timing resources should be indicated the O-RU. - -### 15.5.8 antenna-calibration-multiple-time-resource-params notification parameters - -If the O-RU supports O-RU-COORDINATED-ANT-CAL-MUL-TIMING-RES-CONFIG, to initiate the calibration operation, the O-RU notifies the notification subscriber (O-DU) using the **antenna-calibration-multiple-time-** - -**resource-params** notification message. Remaining parameter list of this notification includes the frequency resources required for calibration same as 'antenna-calibration-required' described in clause 15.5.3: - -- **antenna-calibration-time-resource-index**: key value to index the list 'antenna-calibration-multiple-time-resource-list' based on the calibration duration required by the O-RU. - -## 15.6 Static configuration for PRACH and SRS - -### 15.6.1 Background - -PRACH and raw SRS are periodic. Their location in time and frequency resources is constant for all periods. This makes it feasible to configure PRACH and raw SRS with M-Plane in a sense that handling PRACH and / or raw SRS processing by assigned low-level-rx-endpoints does not require real-time control through C-Plane messages. - -Static configuration of PRACH and SRS with M-Plane needs to cover following aspects: - -- Configuration of frequency resources assigned to PRACH / SRS -- Configuration of time resources assigned to PRACH / SRS (including PRACH / SRS periodicity) -- Configuration of compression, iFFT and SCS -- Assignment of HW resources (low-level-rx-endpoints) for processing of PRACH / SRS - -Static configurations shall be provided to the O-RU as part of carrier configuration - before the configured carrier is activated. Static PRACH / SRS configuration provided for already active carrier shall be rejected by the O-RU. - -NOTE: In case a static-low-level-rx-endpoint exposes parameter **static-config-supported** with value **NONE** - such endpoint does not offer support for static configuration of PRACH nor SRS reception. - -In case the configuration provided to O-RU contains records for TDD pattern(s), PRACH patterns and/or SRS patterns, the O-RU validates consistency between patterns. Configuration where there is collision between patterns detected, shall be rejected by the O-RU. - -### 15.6.2 Static configuration for PRACH processing - -The O-RU exposes its ability to support static PRACH configuration by support of the feature **PRACH-STATIC-CONFIGURATION-SUPPORTED** in o-ran-module-cap.yang module. Presence of this feature means, that at least one of static-low-level-rx-endpoints offered by the O-RU supports static configuration for PRACH. From the model perspective, static PRACH configuration is supported by static-low-level-rx-endpoints having the parameter **static-config-supported** exposed as **PRACH**. Such static-low-level-rx-endpoint can be referenced by low-level-rx-endpoint designated for reception of PRACH. Specific PRACH configuration may be utilized by the low-level-rx-endpoint according to the optional parameter **static-prach-configuration**. - -NOTE: A single low-level-rx-endpoint can only reference to single instance of static-prach-configuration. However, a single static-prach-configuration may be referenced by many low-level-rx-endpoints. - -If parameters related to static PRACH configuration are set by NETCONF Client – real-time C-Plane control for PRACH opportunities shall not be provided to the O-RU, allowing for static configuration to be utilized. - -### 15.6.3 Frequency domain configuration - -The meaning of frequency-related parameters is illustrated using Figure 15.6.3-1. - -NOTE: Parameter offset-to-absolute-frequency-center belongs to low-level-rx-endpoint. - -![Figure 15.6.3-1: Relation between frequency-related parameters of the PRACH occasion. This diagram shows a frequency spectrum with Resource Blocks (RBs) labeled RB #0, ..., RB #96, RB #97, RB #98, and RB #99. PRACH REs are shown as blue blocks, PRACH guard tone REs as yellow blocks, and other REs as grey blocks. Key parameters indicated include startPrbc (the starting RB index), numPrbc (the number of PRACH RBs), re-offset, guard-tone-low-re, num-prach-re, guard-tone-high-re, offset-to-absolute-frequency-center, and F_REF.](e89c5b1964de9c09b6b7012b2de4b1c3_img.jpg) - -Figure 15.6.3-1: Relation between frequency-related parameters of the PRACH occasion. This diagram shows a frequency spectrum with Resource Blocks (RBs) labeled RB #0, ..., RB #96, RB #97, RB #98, and RB #99. PRACH REs are shown as blue blocks, PRACH guard tone REs as yellow blocks, and other REs as grey blocks. Key parameters indicated include startPrbc (the starting RB index), numPrbc (the number of PRACH RBs), re-offset, guard-tone-low-re, num-prach-re, guard-tone-high-re, offset-to-absolute-frequency-center, and F\_REF. - -Figure 15.6.3-1: Relation between frequency-related parameters of the PRACH occasion - -Relations between parameters allow to calculate startPrbc and numPrbc. For details of startPrbc and numPrbc, see O-RAN CUS-Plane Specification [2], clause 7.5.3.4 and 7.5.3.6. - -### 15.6.4 Time domain configuration - -Meaning of parameters is illustrated using Figure 15.6.4-1. - -![Figure 15.6.4-1: Timing-related parameters of single PRACH occasion. This diagram shows the timing of a single PRACH occasion. It includes a time-offset, a PRACH CP (Cyclic Prefix) of length cp-length, two PRACH Symbols of duration symbol-duration, and a PRACH GP (Guard Period) of length gp-length. The total duration is labeled as number-of-repetitions. The time axis is labeled f_n = 0 at the start and time at the end.](acfeac2f7568d6aec4939bac69beb2e5_img.jpg) - -Figure 15.6.4-1: Timing-related parameters of single PRACH occasion. This diagram shows the timing of a single PRACH occasion. It includes a time-offset, a PRACH CP (Cyclic Prefix) of length cp-length, two PRACH Symbols of duration symbol-duration, and a PRACH GP (Guard Period) of length gp-length. The total duration is labeled as number-of-repetitions. The time axis is labeled f\_n = 0 at the start and time at the end. - -Figure 15.6.4-1: Timing-related parameters of single PRACH occasion - -Figure 15.6.4-1 shows a single PRACH occasion containing 2 PRACH Symbols. - -![Figure 15.6.4-2: Timing-related parameters of one PRACH pattern. This diagram shows a PRACH pattern over time. It consists of four pattern-periods. Within each pattern-period, there is a sub-frame x with a time-offset leading to a PRACH occasion (represented by a small group of colored blocks). The time axis is labeled f_n = 0 at the start and end, with intermediate points at f_n = 1 * pattern-period, f_n = 2 * pattern-period, and f_n = 3 * pattern-period.](91348ff0578a2d4d17ab1ce9ff0f8990_img.jpg) - -Figure 15.6.4-2: Timing-related parameters of one PRACH pattern. This diagram shows a PRACH pattern over time. It consists of four pattern-periods. Within each pattern-period, there is a sub-frame x with a time-offset leading to a PRACH occasion (represented by a small group of colored blocks). The time axis is labeled f\_n = 0 at the start and end, with intermediate points at f\_n = 1 \* pattern-period, f\_n = 2 \* pattern-period, and f\_n = 3 \* pattern-period. - -Figure 15.6.4-2: Timing-related parameters of one PRACH pattern - -Figure 15.6.4-2 shows a single PRACH pattern containing two occasions of 2 PRACH Symbols (reuse of occasion shown on figure for single PRACH occasion for simplified view). - -The corresponding parameters for Figure 15.6.4-2 are: ("number-of-prach-occasions" = 2, "number-of-repetitions" = 2) - -NOTE 1: **time-offset** is defined with reference to parameters **frame-number** and **sub-frame-id** under **static-prach-configuration**. This parameter applies for the first occasion of a PRACH pattern. For subsequent occasions of the same PRACH pattern, the O-RU utilizes the parameters **cp-length**, **gp-length** and **beam-id** to determine the time boundaries. The parameters are taken from the list **occasion-parameters** such that, the first occasion uses the first set of elements from the list. Subsequent occasions use consecutive sets of parameters. The number of sets of parameters in this list is equal to value of the parameter **number-of-occasions**. - -One **static-prach-configuration** instance allows to configure a set of PRACH patterns. For a single PRACH configuration, all corresponding PRACH patterns repeat over the period defined by the **pattern-period** parameter for such PRACH configuration. The PRACH patterns of single PRACH configuration shall not overlap in terms of time and frequency. - -At most one PRACH pattern shall start in a subframe (subframes in different frames are distinguished). PRACH pattern shall not cross boundary between subframes except PRACH pattern for long PRACH format with one occasion that spans boundary between subframes. - -An O-RU shall reject any configuration where the number of patterns in single static PRACH configuration exceeds the number exposed by capability parameter **max-prach-patterns** in o-ran-uplane-conf.yang module. - -![Figure 15.6.4-3: Example PRACH configuration formed of two PRACH patterns having different number of PRACH Symbols. The diagram shows two sub-frames, sub-frame x and sub-frame y, each containing five frames. Sub-frame x shows PRACH pattern #1 with 4 repetitions (beam-id #1, #2, #3, #4) and 3 occasions. Sub-frame y shows PRACH pattern #2 with 6 repetitions (beam-id #4, #5, #6, #7, #8, #9) and 2 occasions. Each PRACH symbol is shown with its associated CP and GP.](41bc9383c0d6e910a69e23d465ae5607_img.jpg) - -Figure 15.6.4-3: Example PRACH configuration formed of two PRACH patterns having different number of PRACH Symbols. The diagram shows two sub-frames, sub-frame x and sub-frame y, each containing five frames. Sub-frame x shows PRACH pattern #1 with 4 repetitions (beam-id #1, #2, #3, #4) and 3 occasions. Sub-frame y shows PRACH pattern #2 with 6 repetitions (beam-id #4, #5, #6, #7, #8, #9) and 2 occasions. Each PRACH symbol is shown with its associated CP and GP. - -**Figure 15.6.4-3: Example PRACH configuration formed of two PRACH patterns having different number of PRACH Symbols** - -NOTE 2: PRACH occasions are expanded for visual clarity. - -NOTE 3: Figure 15.6.4-3 shows a theoretical configuration – not necessarily standardised by 3GPP. This is to demonstrate the flexibility of the solution of static PRACH configuration offered by M-Plane configuration. - -The above configuration uses 2 prach-patterns: - -- Pattern #1 is having: number-of-repetitions = 4, number-of-occasions = 3 -- Pattern #2 is having: number-of-repetitions = 6, number-of-occasions = 2 - -For the PRACH configuration shown in Figure 15.6.4-3, the parameter **pattern-period** = 10 as this is the number of frames after which PRACH pattern repeats. - -NOTE 4: Such a static PRACH configuration can be supported by static-low-level-rx-endpoints having parameter **max-prach-patterns** $\geq 2$ as this configuration consists of 2 patterns. - -## 15.6.5 Operation - -Static PRACH configuration shall be set and rx-endpoints shall be linked to it before rx-array-carrier activation. On carrier activation, the O-RU starts receiving RF signals corresponding to the configured **prach-patterns** list. Specifically, the O-RU receives RF signals corresponding to the prach-pattern p when: - -$$\begin{aligned} \text{mod}(\text{ , pattern-period}) &= \text{frame-number}_p \text{ and} \\ &= \text{sub-frame-id}_p \text{ and} \\ t &= \text{time-offset}_p \end{aligned}$$ - -where: - -is the system frame number, - -$\text{mod}(x, y)$ is remainder of division of x by y, - -is the subframe number within system frame , - -$t$ is the time since start of subframe , - -$\text{frame-number}_p$ , $\text{sub-frame-id}_p$ and $\text{time-offset}_p$ are parameters of prach-pattern p, - -**pattern-period** is a parameter of PRACH configuration. - -Offset to the start of pattern periods can be configured either in low-level-rx-endpoint or in static-prach-configuration with **sfn-number** parameter. If the value is provided in static-prach-configuration, then it takes the precedence over the value configured in low-level-rx-endpoint. - -Once the RF signal corresponding to the PRACH Symbol in PRACH occasion is received and processed, the O-RU sends the corresponding IQ values in a U-plane message or messages with header fields set as follows: - -$$\text{frameId} = \text{mod}(\text{floor}(\text{ / pattern-period}) \cdot \text{pattern-period} + \text{frame-number}_p, 256)$$ - -NOTE: This corresponds to value captured when prach-pattern p started) - -$$\text{subframeId} = \text{sub-frame}_p,$$ - -$\text{slotId} = \text{zero-based PRACH occasion number within PRACH pattern,}$ - -$\text{symbolId} = \text{zero-based PRACH Symbol number within PRACH occasion,}$ - -$$\text{sectionId} = 4095,$$ - -$$\text{startPrbu} = \text{floor}((\text{re-offset}_p + \text{guard-tone-low-re}) / 12),$$ - -$$\text{numPrbu} = \text{ceil}((\text{re-offset}_p + \text{guard-tone-low-re} + \text{num-prach-re}) / 12) - \text{startPrbu}.$$ - -Where: - -is the system frame number, - -$\text{mod}(x, y)$ is remainder of division of x by y, - -floor( $x$ ) is largest integer smaller than or equal to $x$ , - -ceil( $x$ ) is smallest integer greater than or equal to $x$ , - -frame-numberp, sub-frame-numberp and re-offsetp are parameters of prach-pattern $p$ . - -pattern-period, guard-tone-low-re and num-prach-re are parameters of PRACH configuration. - -If data section is subdivided due to application level fragmentation, resulting values of startPrbu and numPrbu shall be calculated as per general rules. If multiple PRACH Symbols are scheduled at the same time at different re-offset frequencies, the O-RU shall send corresponding data sections in one U-Plane message following message size restrictions. - -## 15.6.6 Static configuration for raw SRS processing - -The O-RU exposes its ability to support static raw SRS configuration by support of the feature **SRS-STATIC-CONFIGURATION-SUPPORTED** in o-ran-module-cap.yang module. Presence of this feature means, that at least one of static-low-level-rx-endpoints offered by the O-RU supports static configuration for raw SRS reception. From the model perspective, static SRS configuration is supported by static-low-level-rx-endpoints having the parameter **static-config-supported** exposed as **SRS**. Such static-low-level-rx-endpoint can be referenced by a low-level-rx-endpoint designated for reception of SRS. Specific SRS configuration may be utilized by the low-level-rx-endpoint according to the optional parameter **static-srs-configuration**. - -NOTE: A single low-level-rx-endpoint can only reference to single instance of static-srs-configuration. However, a single static-srs-configuration can be referenced by many low-level-rx-endpoints. - -If parameters related to static SRS configuration are set by NETCONF Client – real-time C-Plane control for SRS shall not be provided to the O-RU, allowing for static configuration to be utilized. - -Static SRS configuration is used to configure NDM (Non-Delay Managed) raw SRS (Sounding Reference Signal) patterns in a static manner, such that raw SRS U-Plane traffic can be processed by the O-RU without receiving C-Plane messages conveying real-time raw SRS configuration. Raw SRS may capture non-beamformed (beam-id = 0) or beamformed (beam-id != 0) signals and uses non-delay managed U-Plane messages. - -One **static-srs-configuration** instance allows to configure a set of SRS patterns. For a single SRS configuration, all SRS patterns repeat over the period defined by **pattern-period** parameter for such SRS configuration. SRS patterns corresponding to a single SRS configuration shall not overlap in terms of time and frequency. - -An O-RU shall reject any configuration where the number of patterns in single static SRS configuration exceeds the number exposed by capability parameter **max-srs-patterns** in o-ran-uplane-conf.yang module. - -## 15.6.7 Operation - -Static SRS configuration shall be set and rx-endpoints shall be linked to it before rx-array-carrier activation. On carrier activation, the O-RU starts receiving RF signals corresponding to the configured **srs-patterns** list. Specifically, the O-RU receives RF signal and sends corresponding U-plane messages as if, for each configured srs-pattern $p$ , each rx-endpoint linked with the SRS configuration received C-plane messages with fields: - -``` -dataDirection = 0 (RX), -payloadVersion = 0, -filterIndex = 0, -frameId = mod( , 256 ), -``` - -``` - -subframeId = sub-frame-idp, -slotId = slot-idp, -startSymbolId = start-symbol-idp, -numberOfSections = 1, -sectionId = 4095, -rb = 0, -symInc = 0, -startPrbc = start-prbcp, -numPrbc = num-prbcp, -reMask = 0xFFF, -numSymbol = num-symbolp, -ef=0, -beamId = beam-idp - -``` - -where: - -is the system frame number, - -mod( x, y ) is remainder of division of x by y, - -sub-frame-idp, slot-idp, start-symbol-idp, beam-idp, start-prbcp and num-prbcp are parameters of srs-pattern p. - -## 15.7 TDD pattern configuration - -The O-RU exposes its ability to support TDD pattern configuration by support of the feature **CONFIGURABLE-TDD-PATTERN-SUPPORTED** in o-ran-module-cap.yang module. Presence of this feature means, that at least one of static-low-level-[tr]x-endpoints offered by the O-RU supports configuration for TDD pattern, so that these static-low-level-[tr]x-endpoints can be used (through low-level-[tr]x-endpoints) by [tr]x-array-carriers having configurable TDD pattern assigned. - -Configured TDD pattern shall not be violated by C-Plane and U-Plane messages. In case configuration provided to O-RU contains records for TDD pattern(s), PRACH patterns and/or SRS patterns, O-RU validates consistency between patterns. Configuration where there is collision between patterns detected, shall be rejected by O-RU. - -From the model perspective, configuration for TDD pattern is supported by static-low-level-[tr]x-endpoints having parameter **configurable-tdd-pattern-supported** exposed as **TRUE**. Such static-low-level-[tr]x-endpoint can be respectively referenced by low-level-[tr]x-endpoint designated to serve for [tr]x-array-carrier having preconfigured TDD pattern assigned. Specific configuration of the TDD pattern may be utilized by [tr]x-array-carrier according to the optional parameter **configurable-tdd-pattern**. - -Absence of leaf **configurable-tdd-pattern** at [tr]x-array-carrier means, that such [tr]x-array-carrier has no configurable-tdd-pattern assigned. - -A configurable TDD pattern can be assigned to a [tr]x-array-carrier under the condition, that all static-low-level-[tr]x-endpoints serving such an [tr]x-array-carrier expose value of capability **configurable-tdd-pattern-supported** as **TRUE**. - -A single [tr]x-array-carrier can only reference to single instance of configurable-tdd-pattern. Whereas a single **configurable-tdd-pattern** shall be referenced by all cooperating [tr]x-array-carriers serving for a specific [tr]x-array. Linkage between tx-array-carriers and rx-array-carriers configured to use the same configurable-tdd-pattern shall be assured by the entity responsible for configuration provisioning to O-RU. For example, ensuring that all cooperating [tr]x-array-carriers use static-low-level-[tr]x-endpoints (through low-level-[tr]x-endpoints) having the same value of **tdd-group**. The practical implication of this is that static-low-level-[tr]x-endpoints exposing the same value of parameter **tdd-group** shall be used by low-level-[tr]x-endpoints serving for [tr]x-array-carriers having the same TDD switching points and the same directions to the air interface granted by TDD patterns they are configured to use. - -NOTE 1: M-Plane model allows an O-RU to be configured with more than one TDD patterns. This is capability can be used by O-RUs having more than one [tr]x-array. - -A single TDD pattern configuration consists of list of records. Each single record contains details for frame-offset and direction of signal that shall be applied at the moment a specific frame-offset occurs at air interface. Supported directions are UL (uplink), DL (downlink) and GP (neither uplink nor downlink). - -NOTE 2: Assignment of **configurable-tdd-pattern** to a [tr]x-array-carrier is only possible in case all following conditionals are met: - -- O-RU supports feature CONFIGURABLE-TDD-PATTERN-SUPPORTED. -- all static-low-level-[tr]x-endpoint configured to serve for a specific [tr]x-array-carrier have capability configurable-tdd-pattern set to TRUE. - -## 15.8 C-Plane message limits - -The O-RU exposes its ability to support C-Plane message limits by including support of the feature **CPLANE-MESSAGE-PROCESSING-LIMITS** in o-ran-wg4-features.yang module. Refer to clause 7.8.2.2 of CUS-Plane specification to understand details of this feature. The presence of this feature means, that in addition to an O-RU's "per-endpoint processing limits" e.g. endpoint-section-capacity, endpoint-beam-capacity, endpoint-prb-capacity, an O-RU may also have "per-cplane message limits". To support this feature on a per endpoint basis, a new flag '**cplane-message-processing-limits-required**' is added to '**endpoint-types**' to indicate an endpoint's requirement to support C-Plane message processing limits. The flag shall be set to **true** for the endpoints to which C-Plane message processing limits apply. An additional configuration flag '**cplane-message-processing-limits-enabled**' is added to low-level-[tr]x-endpoints (applicable only for endpoints to which C-Plane limit requirement is exposed by O-RU) to enable the O-DU to use this feature on a per endpoint basis. - -- 1) If the O-DU supports C-Plane message processing limits, it can choose to indicate it adheres to the limits by configuring schema node 'cplane-message-processing-limits-enabled= true'. In such case, the O-DU shall follow limits specified by the parameters, e.g. 'max-beams-per-slot-with-cplane-limits' and 'max-highest-priority-sections-per-slot-with-cplane-limits' when forming C-Plane messages. -- 2) If O-DU does not support C-Plane message processing limits by configuring schema node 'cplane-message-processing-limits-enabled= false' OR O-RU does not indicate it supports the **CPLANE-MESSAGE-PROCESSING-LIMITS** YANG feature, no C-Plane message limits shall apply and O-RU continues to use endpoint capacity limits specified in existing endpoint by per-endpoint limits e.g. endpoint-section-capacity, endpoint-beam-capacity, endpoint-prb-capacity. - -## 15.9 Advanced endpoint capability report - -Both **endpoint-types** and **endpoint-capacity-sharing-groups** provide an optional method for advanced endpoint capability and capacity reporting by using **supported-configuration-combinations**. The report is provided through **supported-configuration-combinations** which allows the O-RU to convey its supported configurations of endpoint - -UL/DL signal transmission/reception and processing as a function of different combinations. In short, the O-RU may report a different processing capacity dependent on a specified set of configurations. This clause describes the data structure of **supported-configuration-combinations** and provides examples of its usage. - -Figure 15.9-1 depicts the data structure in a condensed format. As shown **supported-configuration-combinations** is a three-level list consisting of the levels: **supported-configuration-combinations, set, config**. The parameter **supported-configuration-combinations** will henceforth be referred to as **combination** for the sake of brevity. - -An entry of **config** provides a specific configuration with several parameters to represent the processing capacity of one or more internal components of the O-RU when these are configured to a certain state via endpoint mapping. The parameters **carrier-types** and **center-from-freqoffset** may be omitted to indicate that their value does not affect the O-RU's resource usage, i.e. a wildcard entry. - -An entry of **set** provides a list of one or more **config** entries. The value of **max-overlapping-instances** indicates the number of **config** entries which may be activated simultaneously in time, including multiple activations of the same **config** entry within a **set**. When **max-overlapping-instances** is 1 the O-DU can only utilize one **config** entry from the **set**. Simultaneously overlapping is defined by the DL or UL signals overlapping in time when transmitted or received by the O-RU at the antenna connector. The **config** entries are indirectly activated when the O-RU receives C-plane messages which can be processed by the capabilities reported in those entries. - -NOTE: When Section Type 3 C-plane messages are received the O-RU may rely on fields such as filterIndex, timeOffset, frameStructure and freqOffset to map to internal processing resources. - -An entry of **combination** provides a list of one or more **sets** from which one or more **config** entries (dependent on the value of **max-overlapping-instances** of the specific **set**) may be activated at an overlapping moment in time. At any overlapping moment in time only a single combination entry shall be applied to the O-RU. I.e. **config** entries from different **combination** entries shall not be activated simultaneously. The **combination** entry which the O-DU intends to utilize shall be conveyed to the O-RU via **combination-configuration** as part of the general carrier configuration procedure. Optionally the O-DU may convey its intent to utilize a subset of **sets** and **configs** of the selected **combination** via the same parameter. If the list of configurations is not populated by the O-DU, the O-RU shall assume that the **combination** entry will be utilized to the greatest extent possible. - -In all cases the activation of a particular configuration is performed indirectly by a combination of M-plane configuration and received C-plane messages as they are mapped to the internal processing resources of the O-RU. In cases where conflicts arise between the capabilities of the endpoint conveyed via **supported-configuration-combinations** and other endpoint level capabilities it is the most restrictive capacity restriction option that shall apply. In other words, all applicable restrictions shall be met. - -Once the supported combinations are advertised by the O-RU, the O-DU is expected to comply with a given combination capability advertised by the O-RU. However, if the O-DU for any reason violates the O-RU advertised capabilities, the O-RU shall send an alarm notification, e.g. 'fault-id = 31' to subscribers following the procedures defined in clause 11 and Table A.1-1. - -![A hierarchical diagram showing the structure of configuration combinations. It starts with 'combination[]' at the top, containing a 'set[]' block. The 'set[]' block contains 'max-overlapping-instances' and a 'config[]' block. The 'config[]' block contains a table with parameters.](3eb2c6bfde13eae0df07b28c24d52e5d_img.jpg) - -**combination[]** - -**set[]** - -max-overlapping-instances - -**config[]** - -| | -|--------------------------| -| SCS | -| carrier-types | -| filter-pass-bandwidth | -| max-prb-range | -| center-from-freqoffset | -| supported-filter-indices | - -A hierarchical diagram showing the structure of configuration combinations. It starts with 'combination[]' at the top, containing a 'set[]' block. The 'set[]' block contains 'max-overlapping-instances' and a 'config[]' block. The 'config[]' block contains a table with parameters. - -Figure 15.9-1: Supported configuration combinations group list overview - -The **config** listed parameter **center-from-freqoffset** indicates whether deriving a new carrier center from a C-plane section type 3 message (as defined in [2] clause 15.4.1) is expected to be enabled for the activate configuration. It shall be enabled via the endpoint level parameter **center-from-freqoffset-enabled**. If an endpoint supports this capability, it shall report so by setting **center-from-freqoffset-supported** to TRUE. - -The **config** listed parameter **filter-pass-bandwidth** conveys the maximum size of the passband filter relative to the host carrier center, as defined by **center-of-channel-bandwidth**, and therefore defines the frequency range from which PRBs can be extracted with the endpoint. In turn, the O-DU configures the expected occupied bandwidth to the O-RU via **occupied-bandwidth**, e.g. refer to [2] clause 15.4.1, 15.4.2 and 15.4.3. A list of supported filter pass bandwidths is provided in **supported-filter-pass-bandwidths**. - -The **config** leaf-list parameter **supported-filter-indices** conveys the filter indices supported or intended by the **config**. As an example, the O-RU may use the parameter to restrict an endpoint to only support NB-IoT or a specific NB-IoT channel such as NPUSCH. - -A static-low-level-rx-endpoint intended to support a NB-IoT carrier with an NPUSCH and two NPRACH channels may be conveyed in a single **combination** entry, as illustrated in Figure 15.9-2. - -![Diagram of combination[0] showing two sets (set[0] and set[1]) with their respective configurations. set[0] has max..overlap.=1 and config[0] with scs=15, max-prb-range=1. set[1] has max..overlap.=2 and config[0] with scs=3.75, max-prb-range=4. Callouts explain that one set-config is an endpoint instance and the maximum available configuration is the sum of set[0]config[0] and set[1]config[0]x2.](e010000311ed958dd0bc2b16f8cc23d4_img.jpg) - -**combination[0]** - -**set[0]** max..overlap.=1 - -**config[0]** - -| | | | -|-------------------|-----------------------------|--------------------| -| scs=15 | max-prb-range=1 | filter-..bandwidth | -| carrier-types=lte | center-from-freqoffset=TRUE | | - -**set[1]** max..overlap.=2 - -**config[0]** - -| | | | -|-------------------|-----------------------------|--------------------| -| scs=3.75 | max-prb-range=4 | filter-..bandwidth | -| carrier-types=lte | center-from-freqoffset=TRUE | | - -One set-config is an endpoint instance of configuration/capacity -Multiple instances may be supported with max-overlapping-instances - -**Maximum available configuration:** -set[0]config[0] + set[1]config[0]x2 - -Diagram of combination[0] showing two sets (set[0] and set[1]) with their respective configurations. set[0] has max..overlap.=1 and config[0] with scs=15, max-prb-range=1. set[1] has max..overlap.=2 and config[0] with scs=3.75, max-prb-range=4. Callouts explain that one set-config is an endpoint instance and the maximum available configuration is the sum of set[0]config[0] and set[1]config[0]x2. - -**Figure 15.9-2: Example a static-low-level-rx-endpoint indirectly indicating support for a single NB-IoT carrier support with one NPUSCH and two NPRACH channels** - -A static-low-level-rx-endpoint may additionally support an LTE carrier and PRACH, however, not at the same time as an NB-IoT carrier. In which case, an additional **combination** entry may be listed to convey support for either NB-IoT or an LTE carrier as shown in Figure 15.9-3. - -![Figure 15.9-3: Example A static-low-level-rx-endpoint indirectly indicating support for either a NB-IoT and LTE carrier, however, not both at the same time. The diagram shows two combinations. Combination[0] has two sets: set[0] (max..overlap.=1) with config[0] (scs=15, max-prb-range=1, carrier-types=lte, center-from-freqoffset=TRUE) and set[1] (max..overlap.=2) with config[0] (scs=3.75, max-prb-range=4, carrier-types=lte, center-from-freqoffset=TRUE). Combination[1] has two sets: set[0] (max..overlap.=1) with config[0] (scs=15, max-prb-range=100, carrier-types=lte, center-from-freqoffset=FALSE) and set[1] (max..overlap.=1) with config[0] (scs=1.25, max-prb-range=72, carrier-types=lte, center-from-freqoffset=FALSE) and config[1] (scs=7.5, max-prb-range=14, carrier-types=lte, center-from-freqoffset=FALSE). A callout box points to the center-from-freqoffset=TRUE field in combination[0] set[0] config[0], stating 'Center-from-freq-offset set to TRUE implies NB-IoT due to new indication of carrier center'. A yellow box in the center explains the maximum available configuration: 'set[0]config[0] + set[1]config[0]x2 Or the alternative combination: comb[1]set[0][config[0]+ comb[1]set[1][config[0/1]]'.](29640f9496773db15b016e35bb17d5b8_img.jpg) - -Figure 15.9-3: Example A static-low-level-rx-endpoint indirectly indicating support for either a NB-IoT and LTE carrier, however, not both at the same time. The diagram shows two combinations. Combination[0] has two sets: set[0] (max..overlap.=1) with config[0] (scs=15, max-prb-range=1, carrier-types=lte, center-from-freqoffset=TRUE) and set[1] (max..overlap.=2) with config[0] (scs=3.75, max-prb-range=4, carrier-types=lte, center-from-freqoffset=TRUE). Combination[1] has two sets: set[0] (max..overlap.=1) with config[0] (scs=15, max-prb-range=100, carrier-types=lte, center-from-freqoffset=FALSE) and set[1] (max..overlap.=1) with config[0] (scs=1.25, max-prb-range=72, carrier-types=lte, center-from-freqoffset=FALSE) and config[1] (scs=7.5, max-prb-range=14, carrier-types=lte, center-from-freqoffset=FALSE). A callout box points to the center-from-freqoffset=TRUE field in combination[0] set[0] config[0], stating 'Center-from-freq-offset set to TRUE implies NB-IoT due to new indication of carrier center'. A yellow box in the center explains the maximum available configuration: 'set[0]config[0] + set[1]config[0]x2 Or the alternative combination: comb[1]set[0][config[0]+ comb[1]set[1][config[0/1]]'. - -Figure 15.9-3: Example A static-low-level-rx-endpoint indirectly indicating support for either a NB-IoT and LTE carrier, however, not both at the same time - -Finally, an endpoint capability report may be structured to indicate a large degree of flexibility in terms of active **configs** as illustrated in **combination-1** of Figure 15.9-4 which shows any three combinations of the listed **configs** may be utilized. Whereas **combination-0** can only support a single instance of a 15 kHz channel. - -![Figure 15.9-4: Example A static-low-level-rx-endpoint indirectly indicating support for a NB-IoT carrier with more flexibility in the right-hand side combination. The diagram shows two combinations. Combination[0] is identical to the one in Figure 15.9-3. Combination[1] has a single set, set[0] (max..overlap.=3), which contains two configs: config[0] (scs=15, max-prb-range=1, carrier-types=lte, center-from-freqoffset=TRUE) and config[1] (scs=3.75, max-prb-range=4, carrier-types=lte, center-from-freqoffset=FALSE).](33b37422d7968d2d8e7d3c48fe341a77_img.jpg) - -Figure 15.9-4: Example A static-low-level-rx-endpoint indirectly indicating support for a NB-IoT carrier with more flexibility in the right-hand side combination. The diagram shows two combinations. Combination[0] is identical to the one in Figure 15.9-3. Combination[1] has a single set, set[0] (max..overlap.=3), which contains two configs: config[0] (scs=15, max-prb-range=1, carrier-types=lte, center-from-freqoffset=TRUE) and config[1] (scs=3.75, max-prb-range=4, carrier-types=lte, center-from-freqoffset=FALSE). - -Figure 15.9-4: Example A static-low-level-rx-endpoint indirectly indicating support for a NB-IoT carrier with more flexibility in the right-hand side combination - -## 15.10 U-Plane message limits - -O-RU may indicate that its endpoints have U-Plane message processing limits, as specified in clause 8.5.1 of [2], by including feature **UPLANE-MESSAGE-PROCESSING-LIMITS** in o-ran-wg4-features.yang. The presence of this feature means, an O-RU may expose data node **uplane-message-processing-limits-required** per **static-low-level-tx-endpoint** via **endpoint-types**. **uplane-message-processing-limits-required** indicates whether an endpoint has U-Plane message processing limits or not. - -- 1) If O-DU supports feature **UPLANE-MESSAGE-PROCESSING-LIMITS** and supports the leaf **max-section-headers-per-uplane-message**, it should set **uplane-message-section-header-limit-enabled** to 'true' and should comply with O-RU limit specified by the parameters **max-section-headers-per-uplane-message** when forming U-Plane messages. -- 2) When the O-DU does not configure the leaf **uplane-message-section-header-limit-enabled** to 'true', O-RU shall process the U-Plane messages that exceed the limits even though the O-RU may operate with degraded performance or capacity, (refer to [2] clause 8.5.1 for more details). -- 3) When U-Plane message exceeds the limit reported by O-RU, O-RU may raise alarm to indicate the degraded performance or capacity. For details about alarm notification 'fault-id = 31', refer to Table A.1-1. - -## 15.11 DRMS-BF capability and configuration management - -### 15.11.1 Overview - -The DMRS based beamforming method is beamforming method where the O-RU computes beamforming or beamforming + equalization weights based on DMRS configuration from O-DU. The DMRS-BF feature comprises of new O-RU advertised feature capabilities, O-RU advertised limits and O-DU configurations which are described in detail in the following clauses. - -### 15.11.2 O-RU advertised capabilities and capacity limits - -To support the DMRS based beamforming feature O-RU advertises to the O-DU a set of capability parameters which are mandatory to be supported by the O-RU and few other are optional. To support DMRS-BF new section type, new section extensions and various new functionalities have been added to the fronthaul CUS-Plane specification, each sub-functionality requires the O-RU to advertise a set of capabilities and maximum capacity limits. Below table intends to summarize all the parameters advertised by the O-RU and their scope i.e. at what granularity the parameters are advertised by the O-RU. Refer to the Table C.2-1, feature numbers 67 to 77 and 81 for DMRS-BF related features in o-ran-wg4-features.yang. - -**Table 15.11.2-1: DMRS-BF O-RU advertised capabilities and capacity limits** - -| S.No
(feature
num.param
num) | O-RU advertised DMRS-BF Capability/Limit
parameter name | Scope of parameter | -|---------------------------------------|--------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------| -| 1.1 | rrm-meas-supported | Per endpoint-type | -| 1.2 | max-ipn-unalloc-reports-supported | Per endpoint-type | -| 1.3 | max-ipn-unalloc-symbols-supported | Per endpoint-type | -| 1.4 | max-ipn-alloc-reports-supported | Per endpoint-type | -| 1.5 | alloc-ipn-per-dmrs-sym-grp-supported | Per endpoint-type | -| 2.1 | equalization-data-scaling | O-RU level | -| 2.2 | eq-scale-offset-min | Per endpoint-type | -| 2.3 | eq-scale-offset-max | Per endpoint-type | -| 3.1 | supported-symb-reorder-capability | Per endpoint-type | -| 3.2 | max-num-symbol-reordering-pattern-per-slot | Per endpoint-type | -| 3.3 | up-symbolld-type-supported | Per endpoint-type | -| 4.1 | ta3-min-2g | Per non-default-ru-delay-profile
and ru-delay-profile | -| 4.2 | ta3-max-2g | Per non-default-ru-delay-profile
and ru-delay-profile | -| 5.1 | sinr-reporting-supported | Per endpoint-type | -| 5.2 | supported-sinr-resolutions
sinr-max-data-layers,
sinr-per-prb (listleaf),
sinr-slot-mask (listleaf) | Per endpoint-type | -| 5.3 | sinr-reference-level-min | Per endpoint-type | -| 5.4 | sinr-reference-level-max | Per endpoint-type | -| 5.5 | sinr-compression-method | Per endpoint-type
Per entry in supported-sinr-
compression-methods | -| 5.6 | sinr-bitwidth | Per endpoint-type
Per entry in supported-sinr-
compression-methods | -| 5.7 | sinr-block-size | Per endpoint-type
Per entry in supported-sinr-
compression-methods | -| 6.1 | supported-entry-types | Per endpoint-type | -| 6.2 | max-user-groups-per-slot | Per endpoint-type, per group of
endpoints sharing a capacity | -| 6.3 | max-entries-per-slot | Per endpoint-type, per group of
endpoints sharing a capacity | -| 6.4 | max-dmrs-configs-per-user-group-incl-first-last-prb | Per endpoint-type | -| 6.5 | max-dmrs-configs-per-user-group-excl-first-last-prb | Per endpoint-type | -| 6.6 | dmrs-symbol-mask | Per endpoint-type | -| 6.7 | max-dmrs-ant-port-number | Per dmrs-symbol-mask | -| 6.8 | max-user-data-layers | Per dmrs-symbol-mask | -| 6.9 | list of supported pairs of { low-papr-type and hopping-mode } | Per endpoint-type | -| 6.10 | list of supported pairs of { d-type, pusch-dmrs-muxing-
supported } | Per endpoint-type | -| 6.11 | different-transform-precoding-in-user-group-supported | Per endpoint-type | -| 6.12 | different-cdm-without-data-in-user-group-supported | Per endpoint-type | -| 7.1 | se-10-bgt-11b-supported | Per endpoint-type | -| 7.2 | se10-member-candidate-list | Per endpoint | -| 8 | user-group-self-assembly-mode | Per endpoint-type | -| 9 | continuity-block-sizes-supported | Per endpoint-type | -| 10.1 | ueid-max-layer-bits | O-RU level | - -| | | | -|------|----------------------------------------------|-------------------| -| 10.2 | max-num-ues-supported | O-RU level | -| 10.3 | max-num-ueids | O-RU level | -| 11 | simultaneous-sinr-and-dmrs-sending-supported | Per endpoint-type | -| 12.1 | ue-time-partial-overlap-supported | Per endpoint-type | -| 12.2 | ue-freq-partial-overlap-supported | Per endpoint-type | -| 13 | max-user-groups-per-ue-in-time | Per endpoint-type | - -### 15.11.3 O-DU configurations of parameters - -Following O-RU capability advertisement, the O-DU is required to configure a set of parameters with restrictions on the scope of configuration. Below table intends to summarize all the parameters configured by the O-DU to enable the sub-functionalities/features advertised by the O-RU. Along with the parameter list the table also captures the scope of configuration of all the parameters to be configured by the O-DU. - -**Table 15.11.3-1: DMRS-BF configurations** - -| S.No
(feature
num.param
num) | Configuration parameter | Configuration Scope | -|---------------------------------------|---------------------------------------------|----------------------| -| 1.1 | rrm-meas-enabled | Per endpoint | -| 2.1 | eq-scale-offset-config | Per endpoint | -| 2.2 | eq-scale-offset-used | Per endpoint | -| 3.1 | se26-usage-enabled | Per endpoint | -| 4.1 | config-symb-reorder-method | Per O-RU | -| 4.2 | config-symb-reorder-upSymbl-type | Per O-RU | -| 5.1 | sinr-reporting-enabled | Per endpoint | -| 5.2 | sinr-per-prb | Per endpoint | -| 5.3 | sinr-slot-mask | Per endpoint | -| 5.4 | sinr-reference-level-config | Per endpoint | -| 5.5 | sinr-reference-level-used | Per endpoint | -| 5.6 | sinr-compression-method | Per endpoint | -| 5.7 | sinr-bitwidth | Per endpoint | -| 5.8 | sinr-block-size | Per endpoint | -| 6 | user-group-mode | Per rx-array-carrier | -| 7.1 | continuity-block-size-configured | Per rx-array-carrier | -| 8.1 | ueid-layer-bits-configured | Per O-RU | -| 9.1 | port-reduced-dmrs-data-sending-enabled | Per rx-array-carrier | -| 9.2 | point-a-offset-to-absolute-frequency-center | Per rx-array-carrier | -| 10 | ueid-persistence-enabled | Per O-RU | -| 11 | bf-methods | Per endpoint | - -### 15.11.4 DMRS-BF-EQ target value configuration - -For DMRS-BF-EQ, there are two parameters, **eq-scale-offset-config** (see clause 8.1.3.4 in CUS-plane specification [2]) and **sinr-reference-level-config** (see clause 7.2.11 in CUS-plane specification [2]), that use the method of target value configuration and used-value retrieval described in clause 9.1.9. - -The O-DU configures a target value for each of the parameters **eq-scale-offset-config** and **sinr-reference-level-config** as part of endpoint creation or reconfiguration including these two parameters. It is important for the O-DU to know (with sufficiently high precision) the actual values used, but it is possible that the O-RU cannot implement the target values precisely. The O-RU will instead report and use the value it is able to support but close to the target value. To report the used-values, the O-RU sets the read-only parameters **eq-scale-offset-used** and **sinr-reference-level-used** to the - -values that the O-RU used. The O-DU can retrieve the used-values before carrier activation and will then be aware of the precise value (to the precision of the M-plane data formats for each used-value) used by the O-RU. - -Refer to clause 9.1.9 for procedure details. - -## 15.12 Description of feature SE10-MEMBER-CANDIDATE-LIST - -Support for the feature **SE10-MEMBER-CANDIDATE-LIST** enables the O-RU to explicitly advertise one or multiple entries in the list **se10-member-candidate-[tr]x-lists**. This list is advertised separately for TX endpoints and RX endpoints at the O-RU level. Each **static-low-level-tx-endpoint** and each **static-low-level-rx-endpoint** supporting Section Extension 10 points to one entry from the list **se10-member-candidate-tx-lists/ se10-member-candidate-rx-lists** using the parameter **se10-member-candidate-list** respectively. By virtue of an endpoint belonging to a given **se10-member-candidate-[tr]x-list** entry, the endpoints can be used as member eAxC\_ID entry in the O-DU configured **[tr]x-eaxc-id-group**. Below tables explains the advertisement of shared list by the O-RU and association of shared list entry per endpoint. - -**Table 15.12-1: Example of O-RU level global member list advertisement** - -| se10-member-candidate-rx-lists index | Member static-low-level-rx-endpoint of member-candidates list | -|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 1 | static-low-level-rx-endpoint-1
static-low-level-rx-endpoint-2
static-low-level-rx-endpoint-3
static-low-level-rx-endpoint-4 (note)
static-low-level-rx-endpoint-8 (note) | -| 2 | static-low-level-rx-endpoint-3
static-low-level-rx-endpoint-5
static-low-level-rx-endpoint-6
static-low-level-rx-endpoint-7
static-low-level-rx-endpoint-8 (note)
static-low-level-rx-endpoint-9 | -| NOTE: These endpoints may also be representative endpoints, See table 15.12-2 | | - -**Table 15.12-2: Example of O-RU advertised static-low-level-rx-endpoint and a given member-candidates list association** - -| O-RU advertised representative endpoint (endpoints supporting SE-10) | Associated se10-member-candidate-[tr]x-lists index | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------| -| static-low-level-rx-endpoint-4 | 1 or 2 (note) | -| static-low-level-rx-endpoint-8 | 1 or 2 | -| NOTE: In this example static-low-level-rx-endpoint-4 can represent list se10-member-candidate-rx-lists index 2 but cannot be a member of se10-member-candidate-rx-lists index 2 | | - -Based on **se10-member-candidate-list** declared for endpoint that support Section Extension 10 by the O-RU, the O-DU configures a list **tx/rx-eaxc-id-group**, where each entry of this list comprises of **representative-tx/rx-eaxc-id** as the key/index of the list, where each list entry comprises of a list of **member-tx/rx-eaxc-id** (s) from one specific entry advertised in **se10-member-candidate-list** by the O-RU. - -NOTE: O-DU while configuring a given rx-eaxc-id-group[] entry, the O-DU excludes representative endpoint from the configured member-list - -**Table 15.12-3: Example for O-DU configured representative and associated member list based on O-RU advertised se10-member-candidate-list-ref[]** - -| rx-eaxc-id-group[] indexed by representative-rx-eaxc-id as key | O-DU configured member-rx-eaxc-id within rx-eaxc-id-group[] entry with members picked from se10-member-candidate-list[] list advertised by the O-RU | -|----------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------| -| low-level-rx-endpoint-4 | low-level-rx-endpoint-1
low-level-rx-endpoint-2
low-level-rx-endpoint-3
low-level-rx-endpoint-8 | -| low-level-rx-endpoint-8 | low-level-rx-endpoint-5
low-level-rx-endpoint-6
low-level-rx-endpoint-7
low-level-rx-endpoint-9 | - -## 16 Licensed assisted access - -### 16.1 Introduction - -Licensed-assisted access (LAA) leverages the carrier-aggregation (CA) functionality. With LAA, CA is performed between licensed and unlicensed component carriers (CCs). This enables the LAA system to opportunistically benefit from using unlicensed spectrum (e.g. UNII bands in the 5 GHz spectrum) to enhance the aggregated capacity of the O-RU with the objective of enhancing the downlink throughput. - -Several modifications in the RAN are needed to enable LAA in the O-DU and O-RU such as listen-before-talk (LBT), discontinuous transmission, carrier-selection, discovery reference signal (DRS) transmission, etc. This clause is focused on the LAA-related messages and procedures needed in the M-plane. The C-plane related messages are defined in clause 7.2.5.2 of the CUS-plane spec [2]. - -This version of the M-plane spec supports only LAA based on Rel. 13 of the 3GPP specs, where transmission on the unlicensed spectrum can be done only in the downlink direction. The support of eLAA Rel. 14 (i.e. enabling UL transmission on the unlicensed spectrum) may be included in a later version of the M-plane spec. - -The modifications at M-plane to Support LAA can be summarized as follows: - -- 1) LAA-initiation process: O-DU learns about O-RU capabilities and configures it. - - O-RU LAA Support: The O-RU indicates it supports LAA by including support for the "urn:o-ran:laa:x.y" and "urn:o-ran:laa-operations:x.y" namespaces in its ietf-yang-library model as specified in RFC 8525 [59]. - - O-RU LAA Capability Information: When the LAA feature is enabled, leafs corresponding to LAA-related O-RU capabilities, such as the number of supported LAA SCarriers, maximum LAA buffer size, etc, are conveyed via the M-plane to the O-DU as part of the o-ran-module-cap.yang module. - - O-RU LAA Configuration: The NETCONF client configures the unlicensed LAA component carrier with the LAA-related parameters such as the energy-detection threshold, DRS measurement timing configuration (DMTC) period, etc. as part of the o-ran-uplane-config.yang module. The configuration of the number of LAA SCarriers, multi-carrier type, etc. is performed using the o-ran-laa.yang Module. - -- For explanation of the LAA-initiation process, refer to Figure 6.1-1 in clause 6, where the O-RU LAA capability info is conveyed within the "Retrieval of O-RU information" step, while the O-RU LAA configurations are conveyed in "Configuring the O-RU operational parameters" step in Figure 6.1-1. -- 2) Carrier-selection: Selecting the best channel in the unlicensed band, both initially and dynamically over time, as illustrated in Figure 16.1-1. - -![Sequence diagram showing the Carrier-Selection Call-flow between O-RU and O-DU. The process involves starting measurements, receiving results, and then either reconfiguring the cell (Success Case) or performing measurements later (Failure Case).](38c0f202ad5767f3df428353919fa90a_img.jpg) - -``` - -sequenceDiagram - participant O-RU - participant O-DU - Note right of O-RU: O-RU - Note right of O-DU: O-DU - - O-DU->>O-RU: - O-RU-->>O-DU: - - alt Success Case - Note right of O-RU: [Success Case] - O-RU->>O-DU: TRUE... - Note right of O-DU: O-DU may or may not reconfigure the cell with a new frequency. - O-DU->>O-RU: INACTIVE for "LAA tx-array-carrier(s)" - O-RU-->>O-DU: OK - O-DU->>O-RU: delete "LAA tx-array-carrier(s)" - O-RU-->>O-DU: OK - O-DU->>O-RU: create "LAA tx-array-carrier(s)" - O-RU-->>O-DU: OK - O-DU->>O-RU: ACTIVE for "LAA tx-array-carrier(s)" - O-RU-->>O-DU: OK - else Failure Case - Note right of O-RU: [Failure Case] - O-RU->>O-DU: FALSE ... - Note right of O-DU: O-DU will perform measurements later - end - - Note right of O-RU: [Failure case] - O-RU-->>O-DU: REJECTED - Note right of O-RU: O-RU - Note right of O-DU: O-DU - -``` - -Sequence diagram showing the Carrier-Selection Call-flow between O-RU and O-DU. The process involves starting measurements, receiving results, and then either reconfiguring the cell (Success Case) or performing measurements later (Failure Case). - -Figure 16.1-2: Carrier-Selection Call-flow - -## 16.2 LAA-initiation process - -### 16.2.1 LAA module capabilities - -During LAA-initiation, the O-RU reports its LAA capabilities to the NETCONF client. These capabilities are sent at the start up as part of the o-ran-module-cap.yang module. The attributes included are: - -- 1) **sub-band-frequency-ranges**: The unlicensed sub-bands (e.g. 46A, 46B, etc.) that are supported at the O-RU and their frequency ranges -- 2) **number-of-laa-scarriers** (uint8): Number of LAA SCarriers that the O-RU can support. -- 3) **maximum-laa-buffer-size** (uint16): Maximum O-RU buffer size in Kilobytes (KB) per CC. This parameter is needed at the O-DU to know how much data can be sent in advance and stored at the O-RU to address the LBT uncertainty. -- 4) **maximum-processing-time** (uint16): Maximum O-RU Processing time in microseconds at the O-RU to handle the received/transmitted packets from/to the O-DU. This parameter is needed at the O-DU to determine the time where it needs to send the data to the O-RU. -- 5) **self-configure** (Boolean): Capability to manage the contention window at the O-RU. Based on the CUS-spec, there are two modes of operation for LAA, 1) when the contention window is managed by the O-DU, and 2) when the contention window is managed by the O-RU. This field is set to True if the O-RU can manage the contention window locally. - -### 16.2.2 LAA O-RU parameter configuration - -The second stage of the LAA-initiation process is the configuration message (using RPC edit-config). In this message, the O-DU configures the O-RU with the required parameters in the downlink direction. LAA parameters can be configured by Netconf Client after capability exchange is finished. It can also be sent as needed, to reconfigure the O-RU with new parameters (e.g. **ed-threshold-pdsch**, etc.). The attributes of this message (o-ran-laa.yang Module) include: - -- 1) **number-of-laa-scarriers** (uint8): Number of LAA SCarriers to be used at the O-RU. This number should be less than or equal the number reported by the O-RU in its module capabilities. -- 2) **multi-carrier-type** (Enumeration): This value indicates the list of multi carrier types (A1, A2, B1, B2) as specified in clause 15.1.5 of 3GPP TS 36.213 [32]. -- 3) **multi-carrier-tx** (Boolean): This value indicates whether self-deferral is activated or not. "True" indicates transmission on channel access win (i.e. no self-deferral). "False" indicates mutual transmission on multiple carriers. -- 4) **multi-carrier-freeze** (Boolean): This value indicates if the absence of other technology in the unlicensed band can be guaranteed. This attribute can only be used when the multi-carrier-type is A1. "False" indicates that absence of other technology is not guaranteed. -- 5) **laa-ending-dwpts-supported** (Boolean): This value indicates whether LAA ending in Downlink Pilot Time Slot (DwPTS) is supported. -- 6) **laa-starting-in-second-slot-supported** (Boolean): This value indicates LAA starting in second slot is supported. - -LAA carrier configurations (o-ran-uplane-conf.yang Module) include: - -- 1) **ed-threshold-pdsch** (int8): This value indicates the energy detection (ED) threshold for LBT for PDSCH and for measurements in dBm. -- 2) **ed-threshold-drs** (int8): This value indicates the ED threshold for LBT for DRS in dBm. -- 3) **tx-antenna-ports** (uint8): This value indicates the Tx antenna ports for DRS. -- 4) **transmission-power-for-drs** (int8): This value indicates the offset of CRS power to reference signal power (dB). -- 5) **dmtc-period** (enumeration): This value indicates DMTC period in milliseconds. -- 6) **dmtc-offset** (uint8): This value indicates DMTC offset in Subframes. -- 7) **lbt-timer** (uint16): This value indicates LBT Timer in milliseconds. - -If Self Configure capability is set to "true", the following parameters are also needed to be configured. For every traffic priority class, the O-DU needs to configure maximum CW usage counter. This value indicates the maximum value of counter which shows how many max congestion window value is used for back off number of each priority class traffic. This value, as specified in clause 15.1.3 of 3GPP TS 36.213 [32], is represented as K. Based on the 3GPP specification, this value is selected by O-RU from the set of values {1, 2, ..., 8}. - -## 16.3 Carrier selection - -### 16.3.1 LAA measurements - -The function of the message "**rpc start-measurements**" is to order the O-RU to start measurements. This message can be used for carrier selection initially or dynamically over time. O-RU sends RPC response where status=ACCEPTED (positive case) or REJECTED (negative case). O-RU performs measurement and delivers result with respect to max response time. If result is not ready on time - O-RU sends notification with "measurement-success"=FALSE and with appropriate failure reason. For every configured band, the O-RU informs the NETCONF client whether the measurement was successful or not. For bands with successful measurements, the O-RU reports the occupancy ratio and average RSSI for each channel. For bands with failure measurements, the O-RU includes the reason (e.g. TIMEOUT when the O-RU is not able to finish the measurement for this specific band). - -The occupancy ratio of a given channel is defined as the percentage of the busy duration (i.e. measured signal power is larger than the energy-detection threshold) to the total measurement duration of this specific channel. The energy-detection threshold is specified in the o-ran-uplane-conf.yang module using the **ed-threshold-pdsch** leaf. Note that this threshold is the same as the energy-detection threshold used for LBT for PDSCH transmission. The total measurement duration per channel is specified in o-ran-laa-operation module using the **duration-per-channel** leaf. The range of the occupancy ratio is from 0% (no signal is detected over the total measurement duration per channel) to 100% (i.e. channel was always occupied during measurement). - -The average RSSI of the measured channel is the measured power of this specific channel averaged over the total measurement duration per channel. This parameter is reported to the NETCONF client in dBm and takes a value from the range 0 dBm to -128 dBm. - -### 16.3.2 LAA carrier frequency configuration - -After receiving the measurements, the NETCONF client configures the O-RU with the new channel(s), if needed. To start radio transmission and reception with a new centre frequency, for every component carrier (CC) that needs to be re-configured with a new centre frequency, the O-DU shall first deactivate the TX carrier, delete it, then create a new TX carrier (using the new centre carrier frequency as well as any other new configurations), and then activate the TX - -carrier again to start OTA operation. The procedure for deactivating/deleting/creating/activating the carrier is explained in clause 15.3: Carrier Configuration, in the M-plane specification and elaborated in Figure 15.2.4-1. - -NOTE 1: The creation of LAA carriers is identical to the creation of regular carriers but in the unlicensed bands. O-RU responds to the configuration request with success or failure. - -NOTE 2: The carrier-selection algorithm at the O-DU (i.e. selecting the "best" channel based on the reported measurements from the O-RU) is an implementation issue and is out of the scope of the present document. - ---- - -## 17 Shared cell - -### 17.1 Introduction - -This clause specifies the support of the "Shared Cell" O-RU use case. The features of C/U-Plane aspects are described in clause 13 of [2]. The M-Plane aspects necessary to support Shared Cell are described in this clause 17. - -### 17.2 Architecture - -The NETCONF client (O-RU Controller) establishes M-Plane connection individually to each O-RU, where the O-RUs are operating in either cascade mode or FHM mode, as illustrated in Figure 17.2-1. - -In Figure 17.2-1, solid lines indicate C/U-plane interface and dotted lines indicate M-plane interface. Therefore, from the M-Plane point of view, the same architecture model can be applied as specified in clause 5.1.2. New functionality which is required to be added, together with existing functionality which is required to be enhanced are specified in clauses 17.3 to 17.6. There are no changes to the functionality described in the following clauses and their associated YANG models: - -- Clause 8 : Software management -- Clause 11 : Fault management -- Clause 12 : File management - -A NETCONF client with suitable privileges is able to trigger a reset procedure for each O-RU. It is strongly recommended that when triggering the reset procedures for multiple O-RUs, a NETCONF client should order the procedures such that a reset of an individual O-RU does not affect the operation of other O-RUs operating in either cascade or FHM mode. This can be achieved by correct ordering of the triggering of the reset procedure between the different O-RUs. For example, when triggering a reset involving multiple O-RUs operating in cascade mode, the ordering of the reset trigger sent by the NETCONF client should be done beginning with the last (most-southern) O-RU to the first (most northern) O-RU in chain. In configuration where FHM is used - when FHM reset is needed, O-RUs connected through this FHM should be reset first, then FHM reset can be performed. It is strongly recommended to disable carriers affected by such a reset procedure prior to the triggering of the reset to minimize the impact on C/U-plane traffic as much as possible. In case an O-RU connected through FHM requires to be reset - the reset does not impact to other O-RUs. - -NOTE: There is no difference between Hierarchical M-plane architecture and Hybrid M-plane architecture from the point of reset ordering in either cascade mode (chain topology), or FHM mode (tree topology). - -Using this approach, a NETCONF client can perform software management on multiple O-RUs. Since this procedure may require the reset of the O-RU to update the appropriate software file(s) for the O-RUs, the NETCONF client is - -recommended to order the software management procedures such that the reset procedure issued against one O-RU shall not impact the other O-RUs or FHM. - -![Figure 17.2-1: M-Plane Connection. The diagram shows two modes: Cascade Mode and FHM Mode. In Cascade Mode, an SMO NETCONF Client and an O-DU NETCONF Client are connected to a series of O-RUs (O-RU#1, O-RU#2, ..., O-RU#N) via dashed lines representing NETCONF connections. The O-RUs are connected in a chain via solid lines representing the C/U Plane. In FHM Mode, the SMO and O-DU NETCONF Clients are connected to a central O-RU (FHM) via dashed lines, and the FHM is connected to multiple O-RUs (O-RU#1, O-RU#2, ..., O-RU#N) via solid lines.](5d819f259411162c4e3371915818ae22_img.jpg) - -Figure 17.2-1: M-Plane Connection. The diagram shows two modes: Cascade Mode and FHM Mode. In Cascade Mode, an SMO NETCONF Client and an O-DU NETCONF Client are connected to a series of O-RUs (O-RU#1, O-RU#2, ..., O-RU#N) via dashed lines representing NETCONF connections. The O-RUs are connected in a chain via solid lines representing the C/U Plane. In FHM Mode, the SMO and O-DU NETCONF Clients are connected to a central O-RU (FHM) via dashed lines, and the FHM is connected to multiple O-RUs (O-RU#1, O-RU#2, ..., O-RU#N) via solid lines. - -Figure 17.2-1: M-Plane Connection - -## 17.3 Start-up and Installation - -This clause provides the consideration regarding the shared cell specific additional mechanism for the overall start-up mechanism for "O-RUs with Copy and Combine function" and for "O-RUs without Copy and Combine function". - -Each O-RU establishes M-Plane connection individually to the NETCONF client in the O-RU Controller. The procedures through Transport Layer initialisation (DHCP process and VLAN scanning) and supervision of NETCONF connection are the same as Figure 6.1-1 in clause 6 for both "O-RUs with Copy and Combine function" and "O-RUs without Copy and Combine function". - -For the transport layer initialisation, the following assumptions are made: - -- The order of each O-RU's M-plane establishment is not restricted because of the network transparency at O-RU (FHM and Cascade). - -- For simplification, the network should be configured using a common management plane vlan-id or untagged interface for all O-RUs within one shared cell network managed by same NETCONF client. As a result, the same vlan-id is learned by VLAN scanning by all O-RUs within the shared cell network. - -![Sequence diagram showing NETCONF establishment of the start-up between a NETCONF Client and multiple O-RUs (NETCONF Servers). The process is parallel for each O-RU and includes steps: Transport Layer Initialization, O-RU begins synchronization to primary reference clock, O-RU calls home to NETCONF clients, SSH or TLS Secure Connection Established, NETCONF Capability discovery, Optional provisioning of new management accounts, and Supervision of NETCONF connection.](728a02fe4a04e7f91835147194997cd4_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client - participant O-RU as NETCONF Server (O-RU with or without Copy and Combine) - Note right of O-RU: par [per each O-RU] - Note right of O-RU: sequential for each O-RU - Note right of O-RU: Transport Layer Initialization - Note right of O-RU: O-RU begins synchronization to primary reference clock - Note right of O-RU: O-RU calls home to NETCONF clients - Note right of O-RU: SSH or TLS Secure Connection Established - Note right of O-RU: NETCONF Capability discovery - Note right of O-RU: Optional provisioning of new management accounts - Note right of O-RU: Supervision of NETCONF connection - -``` - -Sequence diagram showing NETCONF establishment of the start-up between a NETCONF Client and multiple O-RUs (NETCONF Servers). The process is parallel for each O-RU and includes steps: Transport Layer Initialization, O-RU begins synchronization to primary reference clock, O-RU calls home to NETCONF clients, SSH or TLS Secure Connection Established, NETCONF Capability discovery, Optional provisioning of new management accounts, and Supervision of NETCONF connection. - -**Figure 17.3-3: NETCONF establishment of the start-up** - -In the step "retrieval of O-RU information", the NETCONF client retrieves the O-RUs' capability from the NETCONF servers by using individual M-plane connection in parallel. The Copy and Combine related capability is defined in clause 17.6.1. - -After the retrieval of O-RU information, the NETCONF client performs the topology discovery procedure in order to discover the topology of NETCONF servers within one shared cell network. (See clause 17.6.2) - -![Sequence diagram for RU information retrieval and topology detection at the start-up. Lifelines: NETCONF Server (O-RU with Copy and Combine), NETCONF Client, NETCONF Server (O-RU without Copy and Combine). The process involves a parallel block for O-RU information retrieval followed by a topology discovery procedure.](f7a1b96924f2d36f5643700fbb7cc2ea_img.jpg) - -``` - -sequenceDiagram - participant S1 as NETCONF Server (O-RU with Copy and Combine) - participant C as NETCONF Client - participant S2 as NETCONF Server (O-RU without Copy and Combine) - Note right of C: [step "O-RUs information retrieval" per each O-RU] - Note right of C: Retrieval of O-RU information - Note left of C: Retrieval of O-RU information - Note right of C: topology discovery procedure - -``` - -Sequence diagram for RU information retrieval and topology detection at the start-up. Lifelines: NETCONF Server (O-RU with Copy and Combine), NETCONF Client, NETCONF Server (O-RU without Copy and Combine). The process involves a parallel block for O-RU information retrieval followed by a topology discovery procedure. - -**Figure 17.3-4: RU information retrieval and topology detection at the start-up** - -The NETCONF client performs software management per O-RU as described in clause 8. - -As described in clause 17.2, as the reset procedure is required during the software management procedure, it is recommended that the NETCONF client resets the O-RU while taking account of the topology of O-RUs and whether a reset of one O-RU will affect other O-RUs in the chain or star topology. - -![Sequence diagram for software management per O-RU. Lifelines: NETCONF Server (O-RU with Copy and Combine), NETCONF Client, NETCONF Server (O-RU without Copy and Combine). The process involves a Software Management message from the client to the first server, followed by another Software Management message from the first server to the second server.](fa849f3297b46a8d257e718ba0720135_img.jpg) - -``` - -sequenceDiagram - participant S1 as NETCONF Server (O-RU with Copy and Combine) - participant C as NETCONF Client - participant S2 as NETCONF Server (O-RU without Copy and Combine) - Note right of C: Software Management - Note left of C: Software Management - -``` - -Sequence diagram for software management per O-RU. Lifelines: NETCONF Server (O-RU with Copy and Combine), NETCONF Client, NETCONF Server (O-RU without Copy and Combine). The process involves a Software Management message from the client to the first server, followed by another Software Management message from the first server to the second server. - -**Figure 17.3-5: Software management per O-RU** - -After the software management steps are completed for all NETCONF servers, the NETCONF client performs shared cell configuration. (See clause 17.6.3.) - -The NETCONF client performs transport configuration, connectivity check configuration, C/U-plane transport connectivity check procedure, Retrieval of the O-RU Delay Profile and U-plane configuration procedures for all O-RUs. - -In this version of the specification, the only processing element definition used for supporting shared cell is the Ethernet-type-flow which is a combination of VLAN identity and MAC address. The vlan-id(s) used for C/U-plane transport-flows is/are common to all O-RUs operating within one shared cell network. - -The Ethernet bridging functionality in an O-RU with Copy and Combine function is able to bridge the Ethernet Loopback messages between the O-DU and other O-RUs configured as part of the shared cell operation. For more details, see clause 17.6.2. - -The u-plane configuration in o-ran-uplane-conf module shall have identical configuration except config-false instances' names and low-level-tx(rx)-endpoints' names for all O-RUs operating within the one shared cell network. The value of gain in tx-array-carriers can be independently configured per O-RU (, i.e. a common value is not mandatory). - -The u-plane configuration in o-ran-uplane-conf module is no longer required for O-RU (FHM). Instead, **shared-cell-copy-uplane-config** and **shared-cell-combine-uplane-config** in o-ran-shared-cell.yang module are used. (See clause 17.6.4) - -NOTE: In this version of the specification, only eCPRI headers are supported for the C/U-Plane protocol (, i.e. support of the IEEE 1914.3 header is not defined). - -![Sequence diagram showing shared cell configuration and u-plane configuration between a NETCONF Client and two types of NETCONF Servers (O-RU with Copy and Combine, and O-RU without Copy and Combine). The diagram is divided into 'for cascade' and 'for FHM' sections with various sequential and parallel blocks for configuration steps.](f75386a4b2a20cebdd81fa18e839be4f_img.jpg) - -The diagram illustrates the interaction for shared cell configuration and u-plane configuration. At the top, three lifelines are shown: **NETCONF Server (O-RU with Copy and Combine)**, **NETCONF Client**, and **NETCONF Server (O-RU without Copy and Combine)**. A **shared cell configuration** message is sent from the first server to the client. - -The main part of the diagram is an **alt** block labeled **[for cascade]**, which contains a **par** block labeled **[per O-RU]**. This **par** block has two branches: - -- sequential for each O-RU**: This branch contains five steps: - - CU-Plane transport configuration - - LBM configuration (CU-Plane transport over ETH) or UDP Echo enabling (CU-Plane transport over IP) - - CU-Plane transport connectivity check between O-DU and O-RU - - Retrieval of the O-RU Delay Profile - - U-plane configuration between O-DU and O-RU -- sequential for cascade O-RU**: This branch contains five steps: - - CU-Plane transport configuration - - LBM configuration(CU-Plane transport over ETH) or UDP Echo enabling (CU-Plane transport over IP) - - CU-Plane transport connectivity check between O-DU and O-RU - - Retrieval of the O-RU Delay Profile - - U-plane configuration between O-DU and O-RU - -Below the **[for cascade]** block is a **[for FHM]** block. It contains a **par** block labeled **[per O-RU (not FHM)]**, which in turn contains a **sequential for each O-RU** block with five steps identical to the first branch above. Below this is a **sequential for FHM** block with six steps: - -- CU-Plane transport configuration -- LBM configuration (CU-Plane transport over ETH) or UDP Echo enabling (CU-Plane transport over IP) -- CU-Plane transport connectivity check between O-DU and O-RU -- Retrieval of the O-RU Delay Profile -- shared cell U-plane configuration between O-DU and O-RU(FHM) - -At the bottom, the same three lifelines are shown again, with the **NETCONF Client** sending messages to both the **NETCONF Server (O-RU with Copy and Combine)** and the **NETCONF Server (O-RU without Copy and Combine)**. - -Sequence diagram showing shared cell configuration and u-plane configuration between a NETCONF Client and two types of NETCONF Servers (O-RU with Copy and Combine, and O-RU without Copy and Combine). The diagram is divided into 'for cascade' and 'for FHM' sections with various sequential and parallel blocks for configuration steps. - -Figure 17.3-4: shared cell configuration and u-plane configuration - -The NETCONF client performs further steps for the regular start-up procedure as described in clause 6. - -![Sequence diagram showing further steps for start-up procedure between a NETCONF Client and a NETCONF Server (O-RU with or without Copy and Combine). The steps are: 1. Optional CU-Plane delay measurements between O-DU and O-RU; 2. Fault Management activation; 3. Performance measurement activation (if required at start-up timing); 4. Retrieval of O-RU state, including synchronization information, from O-RU; 5. Configuring the O-RU operational parameters; 6. Service available.](74b47701fe8a059c632b40e009c57a96_img.jpg) - -``` - -sequenceDiagram - participant Client as NETCONF Client - participant Server as NETCONF Server (O-RU with or without Copy and Combine) - Note over Client, Server: sequential per O-RU - Note over Client, Server: Optional CU-Plane delay measurements between O-DU and O-RU - Note over Client, Server: Fault Management activation - Note over Client, Server: Performance measurement activation (if required at start-up timing) - Note over Client, Server: Retrieval of O-RU state, including synchronization information, from O-RU - Note over Client, Server: Configuring the O-RU operational parameters - Note over Client, Server: Service available - -``` - -Sequence diagram showing further steps for start-up procedure between a NETCONF Client and a NETCONF Server (O-RU with or without Copy and Combine). The steps are: 1. Optional CU-Plane delay measurements between O-DU and O-RU; 2. Fault Management activation; 3. Performance measurement activation (if required at start-up timing); 4. Retrieval of O-RU state, including synchronization information, from O-RU; 5. Configuring the O-RU operational parameters; 6. Service available. - -Figure 17.3-5: further steps for start-up procedure - -## 17.4 Performance management - -This clause provides description of the specific part of Performance Management for shared cell. - -NOTE 1: Clause 9.1 of CUS specification [2] indicates whether a particular performance measurement is mandatory or optional for Cascade/FHM O-RU. - -### transceiver-stats: - -O-RU (Cascade / FHM) has multiple connections to O-DU and O-RU (Cascade/Normal). The baseline O-RU models permit O-RUs to be defined with multiple ports and multiple transceiver modules. Transceiver module is defined by o-ran-transceiver which refers the port-number for these interfaces. Refer to clause 17.6.1 O-RU Information for Shared Cell. In this case, the O-RU (Cascade / FHM) reports **transceiver-stats** per port-number. - -### Rx-window-stats: - -O-RU (Cascade) monitors **rx-window-stats** per eaxc-id, per transport or per hardware component (O-RU) because it receives data flow from the north-node. An FHM has no radio transmission/reception functionality and hence cannot support RX\_ON\_TIME, RX\_EARLY, RX\_LATE, RX\_ON\_TIME\_C, RX\_EARLY\_C, RX\_LATE\_C in rx-window-stats. - -NOTE 2: This version of the specification does support **rx-window-stats** to monitor the downlink reception window and does not support monitoring by an O-RU of the uplink traffic from south-node. - -#### **Tx-stats:** - -O-RU (Cascade / FHM) monitors **tx-stats** per eaxc-id, per transport or per hardware component (O-RU) because it transmits data flow to the north-node. - -NOTE 3: This version of the specification does support **tx-stats** to monitor uplink traffic and does not support monitoring by an O-RU of the downlink traffic to south-node. - -#### **Shared-cell-stats:** - -Cascade O-RU/FHM monitors shared-cell-stats on per TRANSPORT object-unit. - -NOTE 4: Monitoring by an O-RU of the uplink traffic from south-node can be achieved using shared-cell-stats. - -#### **Epe-statistics:** - -O-RU (Cascade / FHM) monitors **epe-statistics** per hardware component. - -#### **Symbol-rssi-stats:** - -O-RU monitors **symbol-rssi-stats** per rx-array-carrier. - -NOTE 5: O-RU without radio transmission/reception capability (FHM) does not support monitoring of **symbol-rssi-stats** - -#### **Tx-antenna-stats:** - -O-RU monitors **tx-antenna-stats** per tx-array element, or connector and band number. - -NOTE 6: O-RU without radio transmission/reception capability (FHM) does not support monitoring of **tx-antenna-stats**. - -#### **Tssi-stats:** - -O-RU monitors **tssi-stats** per carrier\_array\_element. - -NOTE 7: O-RU without radio transmission/reception capability (FHM) does not support monitoring of **tssi-stats-object**. - -#### **Rssi-stats:** - -O-RU monitors **rssi-stats** per carrier\_array\_element. - -NOTE 8: O-RU without radio transmission/reception capability (FHM) does not support monitoring of **rssi-stats-object**. - -#### **Tx-output-power-stats:** - -O-RU monitors **tx-output-power-stats** per tx-array-carrier, tx-array-element, connector, carrier\_array\_element or array-carrier-connector. - -NOTE 9: O-RU without radio transmission/reception capability (FHM) does not support monitoring of **tx-output-power-stats**. - -#### **ethernet-stats:** - -O-RU (Cascade / FHM) has multiple connections to O-DU and O-RU (Cascade/Normal). The baseline O-RU models permit O-RUs to be defined with multiple ethernet ports. Refer to clause 17.6.1 O-RU Information for Shared Cell. In this case, the O-RU (Cascade / FHM) reports **ethernet-stats** per port-number. - -**Table 17.4-1: Measurement-group of O-RU (Cascade / FHM)** - -| Measurement-group | measurement-units | -|------------------------------|-------------------------------------------------------------------------------------------------| -| transceiver-stats | port-number (multiple) | -| rx-window-stats | eaxc-id, transport or hardware component (O-RU) | -| tx-stats | eaxc-id, transport or hardware component (O-RU) | -| shared-cell-stats | transport | -| epe-statistics | hardware component | -| symbol-rssi-stats | rx-array-carrier | -| tx-antenna-stats | tx-array element, or connector and band number | -| tssi-stats | carrier_array_element | -| rssi-stats | carrier_array_element | -| tx-output-power-stats | tx-array-carrier, tx-array-element, connector, carrier-array-element or array-carrier-connector | -| ethernet-stats | ethernet interface name (multiple) | - -For more detail, refer to Table B.1.1-1 Counters definition in clause B. - -## 17.5 Delay management - -In the shared cell environment, the use of O-RU Adaptive Delay capability is not permitted. The O-DU and each O-RU have their own delay parameters and supported transmission window and reception window. Also, the topology of the O-RU configuration can be detected by the topology discovery procedure. - -The O-DU can determine the delay budget between itself and the O-RUs considering the O-RUs' topology and delay parameters and its own transmission window and reception window. During this discovery, the required processing time of the O-RU is also considered. The O-RU processing time includes the copy operation for downlink operation, and the combine operation for uplink operation, and the delay periods for the copy and combine operations are defined as **t-copy** and **t-combine** in o-ran-shared-cell.yang module: - -- **t-copy**: Corresponding to the maximum FHM or cascade O-RU processing delay between receiving an IQ sample over the fronthaul interface from the north-node, coping it and transmitting it over the fronthaul interface to the south-node. -- **t-combine**: Corresponding to the maximum FHM or cascade O-RU processing delay between receiving an IQ sample over the fronthaul interface from the south-node(s), combing them and transmitting it over the fronthaul interface to the north-node. - -Therefore, based on the above information, the O-DU can determine how many O-RUs are configured to operate in a shared cell instance. - -After the delay budget between the O-DU and the furthest (southern-most) O-RU in the chain is determined, multiple O-RUs can be configured to operate in between the O-DU and the furthest O-RU. The time budget between the O-DU and the furthest O-RU is constant and is shared for all O-RUs operating in cascade mode. - -For combine function operation, the O-RU shall await the successful reception of the eCPRI frame(s) from the south-node(s). Once the FHM receives the eCPRI frame from all of the south-nodes, the O-RU (FHM) can perform the combine operation. Once the cascade O-RU receives the eCPRI frame from the south-node, the O-RU can perform the combine operation using the eCPRI frame and received radio information. The maximum time an O-RU is permitted to wait for the required eCPRI frames is set by the **ta3-prime-max** configured by NETCONF client. If the O-RU cannot commence the combination procedure until a time after the configured **ta3-prime-max** minus **t-combine**, e.g. due to the delayed reception of eCPRI frame(s), the O-RU shall discard the delayed eCPRI frames if received and combine other received frames (for FHM mode) or radio information (for Cascade mode). The configurable **ta3-prime-max** shall be equal to or less than **ta3-prime-max-upper-range** which is the capability of O-RU, related to the internal memory for combine operation. The detail for C/U-plane aspects is described in clause 13.4.3 of [2]. - -The **ta3-prime-max** schema node is relevant to the timing on each symbol. The **scs** schema node indicates each symbol timing. The capability of supported SCSes is reported by leaf-list **scs-supported**. Among them the intended SCSes should be informed to FHM/Cascade O-RU as **scs** schema node, associating with eaxc-id. SCS in an eaxc-id can be different from that of another eaxc-id. SCS in an eaxc-id can be also plural. FHM/Cascade O-RU reports the capability of supporting multiple SCS in a single eaxc-id as the feature MULTIPLE-SCS-IN-EAXC, and O-DU should check before configuring multiple SCS in a single eaxc-id. - -- **ta3-prime-max**: The latest time that FHM or cascade O-RU is allowed to send UL U-plane message to north-node relative to reception timing at O-RU antenna. -- **ta3-prime-max-upper-range**: The upper limit for the configurable ta3-prime-max value. This is the capability information of O-RU that comes from the O-RU internal memory for the combine operation. - -Clause 13.5.3 of the CUS specification [2] introduces new parameters for controlling combine operations: - -**t-combine-net**: is the read-only processing delay as the reported by the FHM/Cascade O-RU - -**tx-duration**: is a configurable parameter by O-DU or a calculated parameter by FHM/Cascade O-RU, corresponding to the message transmission duration. - -Where: - -the sum of **t-combine-net** processing delay and the maximum **tx-duration** transmission duration corresponds to the **t-combine** duration. - -NOTE: CUS Plane [2] refers to these parameters as T\_Combine\_net, Tx\_Duration and T\_Comb. - -An FHM/Cascade O-RU can signal to an O-RU Controller that it supports these parameters by indicating it supports the ENHANCED-T-COMBINE YANG feature. The O-DU configures such an FHM/Cascade O-RU to use the new parameters by setting the **enhanced-t-combine-enabled** to 'true'. In this case, the FHM/Cascade O-RU shall use **t-combine-net** and **tx-duration** to calculate the T\_waiting (Refer to 13.5.3 of [2]) instead of **t-combine**. If **enhanced-t-combine-enabled** is set to 'true' and if no value of **tx-duration** is configured by the O-DU, the FHM/Cascade O-RU shall calculate **tx-duration** from **shared-cell-combine-entities**, ensuring that the maximum amount of calculation does not exceed the symbol duration without cyclic prefix designated by **ta3-prime-max**. - -When multiple SCSes are supported by FHM/Cascade O-RU, there are multiple combine delays according to SCSes or configured tx-duration per SCS. This capability may be exposed by FHM/Cascade O-RU through **combine-delay-per-scs**. - -## 17.6 Details of O-RU operations for shared cell - -### 17.6.1 O-RU information for shared cell - -This clause provides the function detail of O-RU operations for a shared cell. - -#### Interfaces to south-node of O-RU with Copy and Combine function - -Cascade O-RU may have one additional transport interface to south-node and FHM may have more than one additional transport interfaces to south-nodes, illustrated in Figure 17.6.1-1. - -![Diagram of transport interfaces in O-RU showing north-node and south-node connections.](b86a5928690177a50c4fe95603ed3988_img.jpg) - -The diagram illustrates the transport interfaces within an O-RU (Radio Unit) and its connections to a north-node and a south-node. The O-RU is represented by a large box labeled "transport interfaces in O-RU". Inside this box, there are two vertical stacks of interface definitions. The left stack represents the interface to the north-node, and the right stack represents the interface to the south-node. Each stack consists of a higher-layer ietf-interface (type=l2vlan) connected to a lower-layer ietf-interface (type=ethernetCsmacd) via a double-headed arrow. The north-node is shown on the left, connected to the lower-layer north interface. The south-node is shown on the right, connected to the lower-layer south interface. Each interface box contains details such as mac-address and port-number. - -Diagram of transport interfaces in O-RU showing north-node and south-node connections. - -Figure 17.6.1-1: Transport Interfaces of both side of O-RU - -Both the interface to north-node and the interface to south-node can be defined by ietf-interface YANG model with **type** = ethernetCsmacd, augmented by o-ran-interface for **mac-address** and **port-number**. Transceiver module is defined by o-ran-transceiver which refers the **port-number** for these interfaces. The maximum number of the interfaces is just the number of physical interfaces within the O-RU. - -NOTE: The present document defines the use of IEEE 802.1X port based access control, as described in clause 7.12. In order to use IEEE 802.1X, a supplicant PAE in an O-RU needs to signal with an authenticator PAE. The present document does not define operation of an authenticator PAE in an O-RU, instead only defining operation of the supplicant PAE functionality. Operators wanting to benefit from IEEE 802.1X when operating a shared cell configuration need to consider which network element(s) is/are responsible for supporting the authenticator PAE function. - -The role of interfaces shall be detected by topology discovery procedure described in clause 17.6.2. - -If the O-RU has any interfaces to south-node and if they are utilized for shared cell scenario, the NETCONF client shall configure the higher layer ietf-interface (**type** = l2vlan) including configuring the corresponding **mac-address** and C/U-plane **vlan-id** configuration for each ietf-interface (**type** = ethernetCsmacd) to south-node, in addition to the higher layer ietf-interface (**type** = l2vlan) configured for the ietf-interface (**type** = ethernetCsmacd) to north-node in clause 7.3. - -If an interface to a south-node is not used for shared cell scenario, the NETCONF client does not need to configure the higher layer ietf-interface (**type** = l2vlan) for it. - -#### Capability of O-RU with Copy and Combine function - -The configuration for Copy and Combine function is defined in the o-ran-shared-cell.yang module. The presence of this yang module signalled in O-RU's YANG library indicates that O-RU can support the copy and combine function. The **shared-cell-module-cap** container includes the information for the internal maximum processing delay for both the copy function and the combine function required for delay management operations. The **shared-cell-module-cap** container also includes the information defining the maximum numbers of copy and combine functions supported. This information is used by the NETCONF client to determine how many south-nodes can be supported and how many eexc-ids can be used for copy and combine procedures. It also contains the information defining the **compression** capability supported by the FHM. It contains **scs-supported** capability of FHM in the present document. - -For the cascade mode, the cascade O-RU shall support normal O-RU operations, i.e. radio transmission and reception. For the FHM mode, the FHM does not have the capability for radio transmission and reception. The o-ran-shared-cell.yang module defines the feature **FHM** to indicate that O-RU acts as FHM and does not have the capability of radio transmission and reception. - -### Yang modules for FHM mode - -Especially for the FHM mode, some of the yang modules are not necessary because the FHM does not have the capability for radio transmission and reception. The following yang modules are not applicable for O-RU (FHM). For more detail, see clause C.1. - -- o-ran-ald module and o-ran-ald-port: Antenna Line device is directly connected to O-RU. -- o-ran-laa-operations and o-ran-laa: out-scope for LAA and radio transmission related only. -- o-ran-module-cap: radio transmission related parameters only. -- o-ran-beamforming: radio transmission (beamforming) specific parameters only. -- o-ran-uplane-conf: radio transmission (uplane configuration) specific parameters only. - -## 17.6.2 Topology discovery procedure - -The O-DU shall determine the topology (adjacency relationships) of O-RUs for the shared cell. In this version of the specification, only Ethernet based transport of C/U sessions for shared cells is supported. The shared cell topology discovery procedure operates at the Ethernet layer, using the LBM/LBR connectivity checking procedure defined in clause 7.6 to fill the Ethernet Forwarding Information Base (FIB), and is based on the O-DU recovering the FIB. The transparent bridge functionality is used in the shared cell capable O-RUs operating in FHM and/or cascade mode. - -In a typical operation, an O-DU performs a two-stage procedure for determining the topology: - -- 1) In a first stage, the O-DU performs Ethernet connectivity monitoring on all discovered O-RU MAC addresses, using the procedures defined in clause 7.6.1. The sending of the Ethernet Loopback responses from the discovered MAC addresses ensures that the transparent bridges in the O-RUs operating in FHM and cascade mode automatically learns the MAC addresses switched through these devices. - -NOTE: In addition to Ethernet connectivity monitoring, DHCP discovery, call home and M-plane connection establishment can also be used to populate information in the FIB and so may be sufficient when an O-RU only has a single port configured for interfacing to its north-node. - -- 2) In a second stage, the O-DU uses the o-ran-ethernet-forwarding.yang module to discover which MAC addresses have been learnt by the Ethernet bridge functionality. The O-DU uses the individual Ethernet forwarding table entries to determine the adjacency relationships. - -If the topology of the cascade architecture does not ensure that Ethernet frames sent between a south-node and a north-node are bridged by an O-RU, the O-DU needs information in addition to the O-RU FIB to perform topology discovery. - -How an O-DU becomes aware that additional information is required, together with the definition of such information, is outside the scope of the present document. - -Figure 17.6.2-1 illustrates an example of the MAC address configuration for a set of O-RUs configured in cascade mode and FHM mode of operations, together with the associated Transparent Bridge FIB tables. - -![Diagram showing Bridge FIB table entries for Cascade Mode and FHM Mode O-RUs connected to an O-DU.](643af12d37ff807bcfea684e7c7abf31_img.jpg) - -The diagram illustrates the MAC address configuration and Bridge FIB table entries for two modes of O-RU operation connected to an O-DU. - -**O-DU:** Contains two MAC addresses: `mac-address/du#1` and `mac-address/du#2`. - -**Cascade Mode:** Contains three O-RUs (O-RU#1, O-RU#2, O-RU#3), all **shared-cell-capable**. Each O-RU has its own Bridge FIB Table and two interface MAC addresses. - -- O-RU#1 (shared-cell-capable):** - - Bridge FIB Table: `port ru#1-1: du#1`, `port ru#1-2: ru#2-1`, `port ru#1-2: ru#3-1` - - Interface MAC addresses: `if:mac-address/ru#1-1` and `if:mac-address/ru#1-2` -- O-RU#2 (shared-cell-capable):** - - Bridge FIB Table: `port ru#2-1: du#1`, `port ru#2-2: ru#3-1` - - Interface MAC addresses: `if:mac-address/ru#2-1` and `if:mac-address/ru#2-2` -- O-RU#3 (shared-cell-capable):** - - Bridge FIB Table: `port ru#3-1: du#1`, `port ru#3-2: ` - - Interface MAC addresses: `if:mac-address/ru#3-1` and `if:mac-address/ru#3-2` - -**FHM Mode:** Contains four O-RUs. O-RU#FHM is **shared-cell-capable**, while O-RU#A, O-RU#B, and O-RU#C are **legacy**. Each O-RU has one interface MAC address. - -- O-RU#FHM (shared-cell-capable):** - - Bridge FIB Table: `port FHM0: du#2`, `port FHM_a: ru#a`, `port FHM_b: ru#b`, `port FHM_c: ru#c` - - Interface MAC address: `if:mac-address/ru#FHM0` -- O-RU#A (legacy):** Interface MAC address: `if:mac-address/ru#a` -- O-RU#B (legacy):** Interface MAC address: `if:mac-address/ru#b` -- O-RU#C (legacy):** Interface MAC address: `if:mac-address/ru#c` - -Diagram showing Bridge FIB table entries for Cascade Mode and FHM Mode O-RUs connected to an O-DU. - -Figure 17.6.2-1: Bridge FIB table entries learned from LBM/LMR connectivity check procedures - -### 17.6.3 Shared cell configuration on transport flow - -Shared cell configuration consists **shared-cell-copy-entities** and **shared-cell-combine-entities**. Both define the **transport-flows** for the processing elements of the interface to north-node and the interface to south-node. The - -container **shared-cell-combine-entities** contains the **ta3-prime-max** and **scs** to be used in delay management as described in clause 17.5. - -As per conventional o-ran-processing-element.yang, the **transport-flow (eth-flow)** of the processing element is a combination of **o-du-mac-address**, **ru-mac-address** and **vlan-id** for legacy **eth-flow**. - -The present document introduces 2 more eth-flow options for shared cell scenario: - -- The **transport-flow** definition for the interface to north-node: **north-eth-flow** is a combination of **north-node-mac-address**, **ru-mac-address** and **vlan-id**. -- The **transport-flow** definition for the interface to south-node: **south-eth-flow** is a combination of **south-node-mac-address**, **ru-mac-address** and **vlan-id**. - -Either legacy **eth-flow** or **north-eth-flow** can be used for last (southern) O-RUs in tree or chain topology. The leaf **o-du-mac-address**, **north-node-mac-address**, **south-node-mac-address** and **ru-mac-address** are configured as follows: - -- For FHM or Cascade O-RU which performs DL Copy function and UL Combine function: - - **north-eth-flow** for the interface to north-node: - - **north-node-mac-address**: MAC address of the north-node (O-DU) - - **ru-mac-address**: MAC address of the interface to north-node in FHM/Cascade O-RU - - **vlan-id** - - **south-eth-flow** for the interface to south-node: - - **south-node-mac-address**: MAC address of the south-node (O-RU) - - **ru-mac-address**: MAC address of the interface to south-node in FHM/Cascade O-RU - - **vlan-id** - -NOTE 1: Same **vlan-id** is configured on both sets of processing elements. - -- For Cascade O-RU in the last node, which doesn't perform DL Copy function and UL Combine function: - - **north-eth-flow** for the interface to north-node: - - **north-node-mac-address**: MAC address of the north-node - - **ru-mac-address**: MAC address of the interface to north-node in O-RU - - **vlan-id** - -or - -——**eth-flow** for the interface to north-node: - -- **o-du-mac-address**: MAC address of the north-node - - **ru-mac-address**: MAC address of the interface to north-node in O-RU - - **vlan-id** -- For O-RU in the last node, but not cascade O-RU: - - eth-flow** for the interface to north-node: - -- **o-du-mac-address**: MAC address of the north-node -- **ru-mac-address**: MAC address of the interface to north-node in O-RU -- **vlan-id** - -Copy and Combine functions are disabled if not configured, meaning the functions are disabled by default. - -Figure 17.6.3-1 illustrates the shared cell configuration and transport configuration. - -![Diagram showing the relation between shared cell configuration and transport configuration. The shared cell configuration contains 'shared-cell-copy-entities' and 'shared-cell-combine-entities'. These point to 'processing-element (north-node)' and 'processing-element (south-node)' in the transport configuration. Each processing element contains fields like 'interface-name', 'north-node-mac-address', 'ru-mac-address', and 'vlan-id'. These elements further connect to 'ietf-interface (type=l2vlan)' and then to 'ietf-interface (type=ethernetCsmacd)' which are connected to 'north-node' and 'south-node' respectively.](e938694881f0eb809f192b1935bd79b4_img.jpg) - -The diagram illustrates the hierarchical relationship between shared cell configuration and transport configuration. At the top, the **shared cell configuration** block contains two entities: **shared-cell-copy-entities** and **shared-cell-combine-entities**. Both entities point to a **processing-element (north-node)** and a **processing-element (south-node)** within the **transport configuration** block. Each processing element contains a list of parameters: **interface-name** (north-eth-flow or south-eth-flow), **north-node-mac-address** (north-node), **ru-mac-address** (interface to north-node or south-node), and **vlan-id**. Below each processing element is a **[vlan of interface to north-node] ietf-interface (type=l2vlan)** or **[vlan of interface to south-node] ietf-interface (type=l2vlan)**. This is further connected to a **[port of interface to north-node] ietf-interface (with o-ran-interface augmentation) (type=ethernetCsmacd)** or **[port of interface to south-node] ietf-interface (with o-ran-interface augmentation) (type=ethernetCsmacd)**. These final interfaces are connected to external **north-node** and **south-node** blocks, each containing an **interface** element. - -Diagram showing the relation between shared cell configuration and transport configuration. The shared cell configuration contains 'shared-cell-copy-entities' and 'shared-cell-combine-entities'. These point to 'processing-element (north-node)' and 'processing-element (south-node)' in the transport configuration. Each processing element contains fields like 'interface-name', 'north-node-mac-address', 'ru-mac-address', and 'vlan-id'. These elements further connect to 'ietf-interface (type=l2vlan)' and then to 'ietf-interface (type=ethernetCsmacd)' which are connected to 'north-node' and 'south-node' respectively. - -Figure 17.6.3-1: Relation of Shared Cell Copy and Combine Entities and Transport Configuration - -For the cascade O-RU, the processing element for north-node shall be connected to the **low-level-[tr]x-links** in u-plane configuration as in Figure 15.2.4-1 in clause 15.2.4. In the FHM, there is no radio transmission, so no **low-level-[tr]x-links** exists. Figure 17.6.3-2 illustrates the example of topology diagram and shared cell copy/combine entities. Each thick blue line indicates the **transport-flow** in the processing element. - -![Figure 17.6.3-2: Example of Topology and Shared cell Copy/Combine entities](0c47111d859618d4b5ab9b334ec3641a_img.jpg) - -The diagram illustrates two network topologies: FHM mode and Cascade mode. -In the top section (FHM mode), an O-DU (north-node) is connected to O-RU#1 (FHM). O-RU#1 contains 'copy' and 'combine' functional blocks. It interfaces with multiple south-nodes: O-RU#2a and O-RU#2b (grouped as Shared cell#1), and O-RU#2x and O-RU#2y (grouped as Shared cell#N). Blue arrows represent transport flows. Single flows from the O-DU are copied in O-RU#1 to multiple south-nodes, and multiple flows from south-nodes are combined in O-RU#1 before being sent to the O-DU. -In the bottom section (Cascade mode), O-RU#0 (north-node) connects to O-RU#1 (cascade), which then connects to O-RU#2 (south-node). O-RU#1 also contains 'copy' and 'combine' blocks to manage the flows between the north and south nodes. -Key labels include: 'north-node-mac-address', 'o-ru-mac-address (interface to north-node)', 'o-ru-mac-address (interface to south-node)', 'south-node-mac-address', and 'u-plane-conf'. - -Figure 17.6.3-2: Example of Topology and Shared cell Copy/Combine entities - -Figure 17.6.3-2: Example of Topology and Shared cell Copy/Combine entities - -The following is the information for this example of topology configuration. - -FHM mode) - -- One **transport-flow** for north-node corresponds to the two **transport-flows** for south-nodes: O-RU#2a and 2b respectively. O-RU#2a and #2b have same u-plane configuration. -- Two **transport-flows** for north-node correspond to the two times two **transport-flows** for south-nodes: O-RU#2x and #2y respectively. O-RU#2x and #2y have same u-plane configuration. - -Cascade mode) - -- Two **transport-flows** for north-node correspond to two **transport-flows** for south-node and own u-plane-configuration. O-RU#1 and O-RU#2 have same u-plane configuration. - -NOTE 2: "two **transport-flows**" above is just the example scenario that two optical physical lines are used for fronthaul connection, which has been supported in the present document. - -The total capacity of the interfaces to north-node for FHM is assumed that required traffic can be transported for multiple shared cells. O-RU Controller shall ensure that the capacity of any link shall not be exceeded due to copy and combine configuration. - -**Information only for the C/U-plane behaviour as the background at COMMON/SELECTIVE-BEAM-ID shared cell copy and combine mode.** - -For the traffic from the north-node to O-RU (FHM / cascade), there are DL C-plane and U-plane traffic and UL C-plane traffic in the transport interface. When operating with **COMMON** shared cell copy and combine mode, all C/U-plane traffic received from north-node is copied and forwarded to the south-node(s). For the traffic from south-node, there is UL U-plane traffic only in each transport interface to south-node. When operating with **COMMON** shared cell copy and combine mode, all U-plane traffic received from the south-node(s) is combined and forwarded to the north-node. It is assumed that common compression mechanism for uplink is configured by M-plane for all O-RUs in one shared cell network. - -When operating with **SELECTIVE-BEAM-ID** shared cell copy and combine mode, some selected C/U-plane traffic received from the north-node are copied and forwarded to the south-node and some selected U-plane traffic received from south-node are combined and forwarded to the north-node. This version of the specification supports **SELECTIVE-BEAM-ID**. - -## 17.6.4 U-plane configuration for FHM - -FHM does not have u-plane configuration defined in o-ran-uplane-conf.yang module. Instead, FHM has shared-cell specific u-plane configuration in **shared-cell-copy-entities/shared-cell-combine-entities** for DL Copy function and UL Combine function, See clause 13.2 of CUS specification [2] for the details of those functions. - -DL Copy function is performed on the received CU-Plane message to make multiple its messages to the specific south nodes. Different eAxC flow can arrive at its specific south node differently, so **transport-flow** is associated with **eaxc-id**, which is unique in **shared-cell-copy-entities** per data direction (DL/UL). The **shared-cell-copy-uplane-config** is the **eaxc-id** list used by DL C-plane, DL U-plane and UL C-plane traffic. - -UL Combine function is performed on the received U-Plane messages from the specific multiple south nodes to make a message to a single north node on the certain timing. Combine function extracts IQ data per RE from U-Plane message and combine multiple IQ data into a single IQ data. The **shared-cell-combine-uplane-config** includes the compression method of the UL U-plane messages from O-RUs within the shared cell network in shared cell combine function. The compression method is configurable per **eaxc-id**. It also contains **downlink-radio-frame-offset**, **downlink-sfn-offset** and **n-ta-offset** to define the uplink timing of t=0 for the configured **ta3-prime-max**. In addition, **number-of-prb** is also contained for the cases that all PRBs in numPrbc are controlled by C-plane message or **tx-duration** is calculated by FHM. - -FHM may have multiple sets of shared cell networks as described in Figure 17.6.3-2. E.g. O-RU#2a and O-RU#2b are one shared cell network. O-RU#2x and O-RU#2y are another shared cell network. These two shared cell networks are separated transport layer level definitions using separate processing-element/transport-flows. Nevertheless, the O-RU Controller shall ensure that the eaxc-id allocation for the shared cell networks shall be unique per link (downlink or uplink) in one O-RU (FHM). NETCONF client (O-RU Controller) shall ensure to allocate unique eaxc-id for O-RU(s) per link within the shared cell network(s) in one O-RU (FHM). - -NOTE 1: **shared-cell-copy-uplane-config** and **shared-cell-combine-uplane-config** are not applicable to the cascade mode. Instead, o-ran-uplane-conf.yang module is applied. - -NOTE 2: If the FHM supports the C/U-plane monitoring timer described in clause 7.10, then depending on how long the O-DU takes to initiate sending of C/U plane data flows, it may be advisable for the NETCONF client to initially disable the operation of the timer for the FHM before carrier activation to O-RUs that are south-nodes for the FHM. Such an approach avoids the FHM sending spurious alarm notifications triggered by O-DU delays in initializing the sending of C/U plane data that exceed the default timer value. Once C/U plane data flows have commenced, the NETCONF client can re-configure the timer with the desired value and hence activate monitoring of the C/U plane connectivity by the FHM. - -### 17.6.5 Support of selective transmission and reception function - -This clause describes M-Plane support for selective transmission and reception function which is specified in clause 13.3 of [2]. There are two things to be introduced for supporting the function from M-Plane perspective: - -- Feature which indicates FHM support for selective transmission and reception function. -- Configuration parameters which indicate the mapping information between global beamId, O-RU(s) and O-RU local beamId. - -If FHM indicates the feature "SELECTIVE-BEAM-ID" to O-DU, O-DU can configure the mapping information between global beamId, O-RU(s) and O-RU local beamId to the FHM to use selective transmission and reception function. For configuring the information, **mapping-table-for-selective-beam-id** is used. - -## 17.7 Cascade-FHM mode - -### 17.7.1 Background - -The introduction of Cascade-FHM mode is described in clause 13.7 of [2]. This clause describes mainly shared cell configuration on cascaded FHMs. For other common parts, like start-up procedures, topology discovery procedure etc., refer to relevant parts in clause 17. In this version of the specification, the maximum level of cascaded FHMs is limited to 2. The first cascade FHM nearest to O-DU is named FHM#1, the second FHM is named FHM#2. - -### 17.7.2 Shared cell configuration on cascaded FHMs - -The NETCONF client shall configure shared cell copy entities and shared cell combine entities on FHM#1 and FHM#2 respectively. - -In Figure 17.7.2-1 there are two types of FHM to FHM traffic: 1) Type 1: the cell of traffic is on O-RUs of both FHM#1 and FHM#2. For example, the Cell#1 of Same cell scenario; 2) Type 2: the cell of traffic is only on O-RUs of FHM#2. For example, the Cell#2 of Two cells Scenario. In this scenario a single SCS per FHM is assumed. When multiple SCS are used in FHM, shared-cell-combine-entities are increased accordingly. - -![Diagram showing two typical cell scenarios in Cascade-FHM mode. The left side shows a 'Same cell scenario' where an O-DU is connected to FHM#1, which is connected to multiple O-RUs (labeled #1) and FHM#2. FHM#2 is also connected to multiple O-RUs (labeled #1). The right side shows a 'Two cells scenario' where an O-DU is connected to FHM#1, which is connected to multiple O-RUs (labeled #1) and FHM#2. FHM#2 is connected to multiple O-RUs (labeled #2). A legend indicates that an oval represents a 'Cell'.](436f157984813b721741946e24a3b76f_img.jpg) - -Diagram showing two typical cell scenarios in Cascade-FHM mode. The left side shows a 'Same cell scenario' where an O-DU is connected to FHM#1, which is connected to multiple O-RUs (labeled #1) and FHM#2. FHM#2 is also connected to multiple O-RUs (labeled #1). The right side shows a 'Two cells scenario' where an O-DU is connected to FHM#1, which is connected to multiple O-RUs (labeled #1) and FHM#2. FHM#2 is connected to multiple O-RUs (labeled #2). A legend indicates that an oval represents a 'Cell'. - -**Figure 17.7.2-1: Typical cell scenarios in Cascade-FHM mode** - -For Type 1, taking Cell#1 of Same cell scenario as example, the shared cell configuration on FHM#1 and FHM#2 are as follows: - -FHM#1: - -- In DL direction, it needs one element of **shared-cell-copy-entities** with one of south nodes connecting to FHM#2 and other south nodes connecting to the O-RUs serving FHM#1, and with north node connecting to O-DU. NETCONF Client selects eaxc-ids carried by the CU-Plane messages who will go to FHM#2 and fills them to eaxc-id list of shared-cell-copy-uplane-config. -- In UL direction, it needs one element of **shared-cell-combine-entities** with one of south nodes connecting to FHM#2 and other south nodes connecting to the O-RUs serving FHM#1, and with north node connecting to O-DU. NETCONF Client selects eaxc-ids carried by the U-Plane messages who are from FHM#2 and fills them to eaxc-id list of shared-cell-combine-uplane-config. - -FHM#2: - -- In DL direction, it needs one element of **shared-cell-copy-entities** with north node connecting to FHM#1 and south nodes connecting to the O-RUs serving FHM#2. NETCONF Client selects eaxc-ids carried by the CU-Plane messages who are from FHM#1 and fills them to eaxc-id list of shared-cell-copy-uplane-config. -- In UL direction, it needs one element of **shared-cell-combine-entities** with north node connecting to FHM#1 and south nodes connecting to the O-RUs serving FHM#2. NETCONF Client selects eaxc-ids carried by the U-Plane messages who will go to FHM#1 and fills them to eaxc-id list of shared-cell-combine-uplane-config. - -For Type 2, taking Cell#2 of Two cells scenario as example, the shared cell configuration on FHM#1 and FHM#2 are as follows: - -FHM#1: - -- In DL or UL direction, existing only one south node which connects to FHM#2 and other steps are no difference with FHM#1 of Type 1; - -NOTE: In Two cells scenario, there will be two elements of shared-cell-copy-entities in DL direction in FHM#1, one is for Cell#1 and another is for Cell#2. Similarly, there will be two elements of shared-cell-combine-entities in UL direction in FHM#1, one is for Cell#1 and another is for Cell#2. - -FHM#2: - -- There is no difference with FHM#2 of Type 1. - -Both FHM#1 and FHM#2 do not need to have u-plane configuration defined in o-ran-uplane-conf.yang module since no radio transmission on the two FHMs. - -## 18 Configured subscriptions - -### 18.1 Introduction - -The support by an O-RU of configured subscriptions is an optional capability, advertised by the O-RU indicating it supports the **ietf-subscribed-notifications** YANG model as specified in RFC 8639 [37] in its YANG library together with the **configured** feature. This capability enables an O-RU Controller to install a subscription via configuration of the O-RU's datastore. Importantly, the lifetime of such a configured subscription is not limited to the lifetime of the NETCONF session used to establish it, enabling a configured subscription to persist even when an O-RU has been temporarily disconnected from the network. An O-RU may store configured subscription information in its reset-persistent memory. - -The **ietf-subscribed-notifications** YANG model defines a transport agnostic mechanism for subscribing to and receiving content from an event stream in an O-RU. An O-RU that supports configured subscriptions shall also support the **encode-json** feature together with the augmentation of the **ietf-subscribed-notifications** YANG model by the **o-ran-ves-subscribed-notifications** YANG model. - -## 18.2 Description - -An O-RU controller can discover the event-streams supported by an O-RU. The O-RU Controller may then establish a configured subscription to a particular event-stream. The same NACM privileges defined in clause 6.5 shall be used by the O-RU in determining whether an O-RU controller has privileges to establish a configured subscription to a particular event-stream. - -Based on configured subscriptions, the O-RU shall send asynchronous notifications over HTTPS to the configured Event-Collector. This capability can be used with any existing YANG notification, e.g. defined in YANG models published by the O-RAN Alliance or imported from other organisations. - -## 18.3 Procedure - -The overall procedure is illustrated in Figure 18.3-1. - -![Sequence diagram showing the message exchange for provisioning a configured notification between an O-RU (NETCONF Server), an O-RU Controller (NETCONF client), and an Event-Collector.](7c09b2c099146ec401150512fbd5e3b1_img.jpg) - -``` - -sequenceDiagram - participant O-RU as O-RU (NETCONF Server) (Event-Producer) - participant O-RU-Controller as O-RU Controller (NETCONF client) - participant Event-Collector as Event-Collector - - Note left of O-RU: YANG Notification triggered - O-RU-Controller->>O-RU: 1 Discover O-RU's event streams - Note right of O-RU: - Note right of O-RU: - Note right of O-RU: ... - Note right of O-RU: - Note right of O-RU: ... - Note right of O-RU: - Note right of O-RU: - Note right of O-RU: - O-RU-->>O-RU-Controller: 2 - O-RU-Controller->>O-RU: 3 - Note right of O-RU: - Note right of O-RU: ... - Note right of O-RU: - O-RU-->>O-RU-Controller: 4 Terminate NETCONF Session - opt - Note right of O-RU: <> subscription-started - Note left of Event-Collector: Event-Collector moved to the "active" state - Note right of O-RU: <> Notification - Note right of Event-Collector: Update Operational-State Database - end - -``` - -Sequence diagram showing the message exchange for provisioning a configured notification between an O-RU (NETCONF Server), an O-RU Controller (NETCONF client), and an Event-Collector. - -Figure 18.3-6: Message sequence exchange for provisioning a configured notification - -### Pre-condition: - -A NETCONF session is established between the O-RU and an O-RU Controller. - -- 1) The O-RU controller gets the **streams** container and discovers the event-streams supported by an O-RU. - -- 2) The O-RU controller uses the "edit-config" RPC to configure a subscription to an event-stream. The RPC includes the **receiver** container augmented with the **notification-recipient** schema node that encodes the URI of the Event-Collector. -- 3) If the O-RU controller has the correct privileges, the O-RU accepts the configured subscription. -- 4) As the lifetime of the configured subscription is not limited by the lifetime of the NETCONF session, the O-RU controller may terminate the NETCONF session without causing the subscription to be suspended. -- 5) After a subscription is successfully established, the O-RU immediately sends a "subscription-started" notification to the Event-Collector, as specified in clause 2.5 of RFC 8639 [37]. -- 6) Upon an event that triggers a YANG notification, the O-RU sends a notification over HTTPS , according to clause 2.5 of RFC8639. - -#### Post-condition: - -The Event-Collector is able to update its operational-state datastore with the information received in the notification. - -## 18.4 Notification encoding - -The O-RU shall support JSON encoding as specified in RFC 7951 [38]. An example notification object generated using the **o-ran-file-management.yang** model and encoded following RFC 7951 [38] is illustrated in Figure 18.4-1. - -``` -{ "ietf-restconf:notification": { - - "eventTime": "2020-11-11T20:20:00Z", - - "o-ran-file-management:file-upload-notification": { - - "local-logical-file-path": "o-ran/pm -/C201805181300+0900_201805181330+0900_ABC0123456.csv", - } -} -``` - -**Figure 18.4-7:Example of a JSON encoded YANG Notification** - -## 18.5 Notification transport - -As described in RFC 8639 [37] clause 2.5.7, an O-RU supporting configured subscriptions shall provide a YANG data model capturing the necessary transport-specific configuration parameters. O-RAN compliant Event-Producers shall support the **o-ran-ves-subscribed-notifications** YANG model. - -For transport, the notification JSON objects encoded according to clause 18.4 are further encapsulated in VES events. In order to enable the notifications sent to the Event-Collector to retain their native notification format/schema as defined in O-RAN, IETF and other YANG models, the ONAP/VES header is used to enable the decoupling of the notification payload from the overall VES event format, as illustrated in Figure 18.4-1. - -The VES common header shall include the following fields: - -- The value of the eventName field shall be set to " ORU-YANG/:". -- The value of the eventID field shall be set to "stdDefined-ORU-YANG-nnnnnnnn", where nnnnnnnn represents the integer key for the event. -- The value of the sourceName and reportingEntityName fields shall both be set to the value of the **ru-instance-id** leaf defined in the o-ran-operations YANG model. - -Figure 18.5-1 illustrates an example of a JSON encoded VES Event Carrying a YANG Notification. - -``` -{ - "event": { - "commonEventHeader": { - "version": "4.1", - "vesEventListenerVersions": "7.2", - "domain": "stdnDefined", - "eventName": "ORU-YANG/o-ran-file-management:file-upload-notification", - "eventID": "stdnDefined-ORU-YANG-000000249", - "sequence": 0, - "priority": "Normal", - "sourceName": "vendorA_ORUAA100_FR1918010111", - "reportingEntityName": "vendorA_ORUAA100_FR1918010111", - "stdnDefinedNamespace": "urn:o-ran:file-management:1.0" - }, - "startEpochMicrosec": 1605126000000000, - "lastEpochMicrosec": 1605126000000000 - } -} -``` - -**Figure 18.5-1:Example of a JSON encoded VES Event Carrying a YANG Notification** - -The VES events carrying the notifications are sent to the Event-Collector over HTTPS with a POST operation following the VES specification [i.2]. The complete protocol stack is illustrated in Figure 18.5-2. - -![Protocol stack diagram showing layers: YANG Notification, VES, HTTP, TLS, TCP/IP](c636e9b650fe8c661dec4486ffc434fd_img.jpg) - -| | -|-------------------| -| YANG Notification | -| VES | -| HTTP | -| TLS | -| TCP/IP | - -Protocol stack diagram showing layers: YANG Notification, VES, HTTP, TLS, TCP/IP - -**Figure 18.5-2: Protocol stack for O-RAN VES transport of YANG notifications** - -## 18.6 Monitoring the communications channel between O-RU and Event-Collector - -### 18.6.1 Background - -An O-RU controller can use the NETCONF monitoring capability described in clause 6.7 to trigger the repeated sending of a **supervision-notification** by the O-RU to a subscribed O-RU Controller to ensure the channel is - -operational and able to transport asynchronous notifications using NETCONF. An equivalent capability is required to be supported by those O-RUs that support configured subscriptions transported using JSON/HTTPS, to enable the monitoring of the communications channel from the O-RU to the Event-Collector. The format of the heartbeat notifications is identical to the Event-Collector Notification Format determined for the operation of pnfRegistration as described in clause 6.2.7, i.e. in this version of the specification, this capability adopts the ONAP defined guidelines for Heartbeat, as defined in [i.2]. - -## 18.6.2 Heartbeat encoding - -The VES common header shall include the following fields: - -- The value of the sourceName and reportingEntityName fields shall both be set to the value of the **ru-instance-id** leaf defined in the o-ran-operations YANG model. - -An example heartbeat encoding is illustrated in Figure 18.6.2-1. - -``` -{ "event": { - "commonEventHeader": { - "version": "4.1", - "vesEventListenerVersions": "7.2", - "domain": "heartbeat", - "eventID": "heartbeat-00000001", - "eventName": "heartbeat-oru", - "sequence": 0, - "priority": "Normal", -``` - -Figure 18.6.2-1: Example of a JSON encoded VES Event Carrying a Heartbeat Notification - -## 18.6.3 Heartbeat control - -Control of the heartbeat does not use the configured subscriptions capability. An O-RU controller configures heartbeat operation using the o-ran-supervision YANG model. An O-RU Controller shall configure the **heartbeat-recipient-id** to the address(es) of the Heartbeat Event-Collector and optionally configure the **heartbeat-interval** leaf to a non-default heartbeat interval. In order to terminate operation of the monitoring the communications channel between O-RU and the Event-Collector, the O-RU Controller shall delete the configuration in the **event-collector-monitoring** container. - -## 18.6.4 Heartbeat procedure - -Figure 18.6.4-1 illustrates the message sequence exchange for heartbeat operation. - -![Sequence diagram showing heartbeat operation between O-RU (NETCONF Server), O-RU Controller (NETCONF client), and Event-Collector. The process involves configuring a heartbeat, starting a timer, and then sending notifications within a loop.](4706a500dbc72fdedc9bee99d7c78df5_img.jpg) - -The diagram illustrates the message sequence exchange for a heartbeat operation between three entities: O-RU (NETCONF Server) (Event-Producer), O-RU Controller (NETCONF client), and Event-Collector. - -**Sequence of Messages:** - -- configure heartbeat**: The O-RU Controller sends an message to the O-RU. The message content is: - - -``` - - - - - - - 1 collector.operator.com - - - - - -``` -- rpc-reply**: The O-RU responds with an message. The O-RU Controller receives it and sends a "Terminate NETCONF Session" message to the O-RU. -- Heatbeat timer is started using default or heartbeatNtfPeriod**: A note indicates the timer starts here. -- loop [heartbeat loop]**: A loop containing the following steps: - - Heartbeat timer expires**: A note indicates the timer expires. - - Heartbeat-Notification**: The O-RU sends a message labeled "4 <> Heartbeat-Notification" to the Event-Collector. - - Event-Collector knows O-RU's management system is operational and communication channel between O-RU and Event-Collector is active**: A note indicates the Event-Collector receives the notification and confirms the channel is active. - -Sequence diagram showing heartbeat operation between O-RU (NETCONF Server), O-RU Controller (NETCONF client), and Event-Collector. The process involves configuring a heartbeat, starting a timer, and then sending notifications within a loop. - -**Figure 18.6.4-1: Message sequence exchange for heartbeat operation** - -In contrast to the monitoring of NETCONF connectivity described in clause 6.7 which define O-RU procedures when monitoring of NETCONF connectivity fails, there is no equivalent O-RU functionality defined if an O-RU determines that monitoring of the communications channel between O-RU and event-collector fails, e.g. if the O-RU is unable to establish a TLS connection to the event-collector. - -Operation of the SMO when it determines that the monitoring of the communications channel between an O-RU and event-collector fails is out of scope of the present document. - ---- - -## 19 Multi-Operator O-RU Operation - -### 19.1 Introduction - -The support by an O-RU of Multi-Operator O-RU operation is an optional capability, advertised by the O-RU indicating it supports the **SHARED-ORU-MULTI-OPERATOR** feature in its **o-ran-wg4-features** YANG model. All O-RUs that support the **SHARED-ORU-MULTI-OPERATOR** feature shall also support the **SHARED-ORU-MULTI-ODU** feature. These capabilities enable an O-RU to connect to multiple O-DUs that belong to different Shared Resource Operators. - -The Multi-Operator O-RU architecture enables a Shared Resource Operator to configure an agreed subset of shared O-RU resources independently from configuration and operating strategies of the other Shared Resource Operators. More specifically, a Shared O-RU Host makes available its shared O-RUs to enable connectivity to the O-DUs of one or more Shared Resource Operators allowing these Shared Resource Operators to configure and control such Shared O-RU. - -NOTE: How a Shared O-RU Host defines the partitioning of shared O-RU resources and communicates that information to a Shared Resource Operator is outside the scope of the present document. - -### 19.2 High level shared O-RU architecture - -When an O-RU is being configured by an independent Shared Resource Operator, a separate O-RU Controller associated with the Shared O-RU Host is required to configure the common aspects of the shared O-RU. Such a deployment is illustrated in Figure 19.2-1. When the Shared O-RU Host also operates an O-DU, the shared O-RU host may operate the M-Plane in either hybrid or hierarchical approach, as illustrated in Figures 19.2-2 and 19.2-3 respectively. In either case, the Shared O-RU Host uses a NETCONF client with "sudo" privileges, as defined in clause 6.5, to configure the shared O-RU. Each Shared Resource Operator uses NETCONF clients with "carrier" privileges that have parallel M-Plane connections with the shared O-RU. - -![Diagram of Shared O-RU M-Plane Architecture showing Operator #1, Operator #2, and a Shared O-RU Host. Operators have SMOs and O-DUs. The Shared O-RU Host has a Shared O-RU Host SMO and a Shared O-RU. Arrows show connections from Operator O-DUs and the Host SMO to the Shared O-RU, with privilege labels like 'carrier privilege', 'sudo privilege', and 'out of scope'.](47ab805b7e6a0b6eb9e379fd8da934fa_img.jpg) - -The diagram illustrates the Shared O-RU M-Plane Architecture. It features three main vertical components: - -- Shared Resource Operator #1:** Contains a **Shared Resource Operator#1 SMO** (with **O-DU Management**) and a **Shared Resource Operator#1 O-DU** (with **O-RU Management** and **NETCONF Client**). A double-headed arrow labeled "out of scope" connects the SMO and O-DU. -- Shared Resource Operator#2:** Contains a **Shared Resource Operator#2 SMO** (with **O-DU Management**) and a **Shared Resource Operator #2 O-DU** (with **O-RU Management** and **NETCONF Client**). A double-headed arrow labeled "out of scope" connects the SMO and O-DU. -- Shared O-RU Host:** Contains a **Shared O-RU Host SMO** (with **NETCONF Client**) and a **Shared O-RU** (with **NETCONF Server**). - -Connections to the **Shared O-RU** (NETCONF Server) are as follows: - -- From **Shared Resource Operator#1 O-DU** (NETCONF Client): A red arrow labeled "carrier privilege". -- From **Shared O-RU Host SMO** (NETCONF Client): A red arrow labeled "sudo privilege". -- From **Shared Resource Operator #2 O-DU** (NETCONF Client): A red arrow labeled "carrier privilege". - -Diagram of Shared O-RU M-Plane Architecture showing Operator #1, Operator #2, and a Shared O-RU Host. Operators have SMOs and O-DUs. The Shared O-RU Host has a Shared O-RU Host SMO and a Shared O-RU. Arrows show connections from Operator O-DUs and the Host SMO to the Shared O-RU, with privilege labels like 'carrier privilege', 'sudo privilege', and 'out of scope'. - -Figure 19.2-1: Shared O-RU M-Plane Architecture where Shared O-RU Host is independent of Shared Resource Operator(s). - -![Diagram of Shared O-RU M-Plane Architecture showing management flows between Shared Resource Operator #1, Shared O-RU Host, and Shared O-RU.](147bfd471cf5feef55178475cec58064_img.jpg) - -``` - -graph TD - subgraph SRO1 [Shared Resource Operator #1] - SMO1[Shared Resource Operator#1 SMO -O-DU Management] - ODU1[Shared Resource Operator#1 O-DU -O-RU Management -NETCONF Client] - SMO1 <-- out of scope --> ODU1 - end - - subgraph SORUH [Shared O-RU Host - additionally acting as Shared Resource Operator -using hybrid management of shared O-RU] - SMOH[Shared O-RU Host SMO -NETCONF Client | O-DU Management] - ODUH[Shared O-RU Host O-DU -O-RU Management -NETCONF Client] - SMOH <-- out of scope --> ODUH - end - - SORU[Shared O-RU -NETCONF Server] - - ODU1 -- carrier privilege --> SORU - SMOH -- sudo privilege --> SORU - ODUH -- hybrid-odu privilege --> SORU - -``` - -Diagram of Shared O-RU M-Plane Architecture showing management flows between Shared Resource Operator #1, Shared O-RU Host, and Shared O-RU. - -Figure 19.2-2: Shared O-RU M-Plane Architecture where the Shared O-RU Host is additionally a Shared Resource Operator managing Shared O-RU using hybrid approach - -![Diagram of Shared O-RU M-Plane Architecture showing two models. The left model shows a standard hierarchy for Shared Resource Operator #1. The right model shows a Shared O-RU Host acting as the operator with hierarchical management. Both show nested boxes for SMO and O-DU management components, with privilege levels (carrier, sudo) indicated for the Shared O-RU.](a5b7735584fef8ef8c84c6755ef27544_img.jpg) - -The diagram illustrates two architectural models for the Shared O-RU M-Plane. -**Left Model: Shared Resource Operator #1** - This model shows a hierarchy for a specific operator. At the top is the **Shared Resource Operator #1 SMO**, which contains an **O-DU Management** box. Below it, separated by a double-headed arrow labeled "out of scope", is the **Shared Resource Operator #1 O-DU**. This O-DU contains an **O-RU Management** box, which in turn contains a **NETCONF Client**. -**Right Model: Shared O-RU Host - additionally acting as Shared Resource Operator using hierarchical management of shared O-RU** - This model shows the **Shared O-RU Host** acting as the operator. It has a similar hierarchy: **Shared O-RU Host SMO** (with **O-DU Management**) at the top, and **Shared O-RU Host O-DU** (with **O-RU Management** and **NETCONF Client**) below it, also separated by an "out of scope" arrow. At the bottom is the **Shared O-RU**, which contains a **NETCONF Server**. Two red arrows point to the Shared O-RU: one from the Operator #1 O-DU labeled "carrier privilege" and another from the Shared O-RU Host O-DU labeled "sudo privilege". - -Diagram of Shared O-RU M-Plane Architecture showing two models. The left model shows a standard hierarchy for Shared Resource Operator #1. The right model shows a Shared O-RU Host acting as the operator with hierarchical management. Both show nested boxes for SMO and O-DU management components, with privilege levels (carrier, sudo) indicated for the Shared O-RU. - -**Figure 19.2-3: Shared O-RU M-Plane Architecture where the Shared O-RU Host is additionally a Shared Resource Operator managing Shared O-RU using hierarchical approach** - -As illustrated in Figures 19.2-1, 19.2-2 and 19.2-3, from an Open Fronthaul perspective, the Shared O-RU is able to be deployed in variety of architectures. - -Clause 5.1.2 requires all O-RUs to support multiple NETCONF sessions, with the number of simultaneous sessions exposed using the **maximum-simultaneous-netconf-sessions** schema node in o-ran-operations YANG model. A Multi-Operator O-RU that is able to support (n) simultaneous NETCONF sessions, shall be able to support (m) Shared Resource Operators, where the cumulative NETCONF sessions operated by the (m) Shared Resource Operators is less than (n). - -## 19.3 Shared O-RU "start up" procedure - -### 19.3.1 NETCONF server user account provisioning for shared resource operators - -The Shared O-RU Host shall use the procedures defined in clause 6.4 and the o-ran-usermgmt YANG model to configure separate user accounts on the shared O-RU's NETCONF server for each Shared Resource Operator. The user account for a Shared Resource Operator that is not also a Shared O-RU Host should only be configured with "carrier" access control group, as defined in clause 6.5. A user account is identified as being associated with a Shared Resource Operator by having one or more configured **sro-ids**. The **sro-id** is allocated by the Shared O-RU Host to the Shared Resource Operator(s) and is used in partitioning shared O-RU resources. - -NOTE 1: How a Shared O-RU Host communicates NETCONF user account information, including sro-id information, to a Shared Resource Operator is outside the scope of the present document. - -NOTE 2: The format of the **sro-id** string is not defined and not interpreted by the shared O-RU. In one example, the operators can agree to use a PLMN-Id corresponding to the Shared Resource Operator as the **sro-id**. - -### 19.3.2 NETCONF call home to shared resource operator O-DUs - -The user account provisioning procedures defined in clauses 6.4.3 and 19.3.1 should be performed before the shared-O-RU calls home to the shared resource operator O-DUs. - -NOTE 1: This avoids the possibility of the shared resource operator using the default account procedures in clause 6.4.2, e.g. by leveraging knowledge of a default account credential that is common across different deployments of a vendor's equipment. - -The procedures defined in clauses 6.2.5 and 6.3 are used by the Shared O-RU Host to trigger the establishment of the NETCONF session with a NETCONF client of the Shared O-RU Host. The Shared O-RU Host can subsequently use the **o-ran-mplane-int** YANG model and the **configured-client-info** container to configure the Multi-Operator O-RU with NETCONF client information corresponding to the individual Shared Resource Operator(s) of the shared O-RU. Standard DHCP-based procedure, as specified in clause 5.1.4, still apply to retrieve NETCONF client information corresponding to the individual Shared Resource Operator(s) of the shared O-RU. - -NOTE 2: How the Shared O-RU Host becomes aware of information to identify the Shared Resource Operator's NETCONF clients to be used with a specific shared O-RU is out of scope of the present document. - -If the O-RU supports static routing as specified in clause 6.2.8, the O-RU shall use its routing table to route the M-Plane traffic towards the Shared Resource operator's O-RU Controller/NETCONF client. - -Following procedures defined in clause 6.3, this will trigger the Multi-Operator O-RU to perform additional call home procedures to any configured clients, which in this scenario will be the NETCONF clients corresponding to individual Shared Resource Operators. - -### 19.3.3 Enhanced sro-id based NETCONF access control - -The resource configuration framework defines particular named list entries in the shared O-RU's configuration that can be allocated to an **sro-id**. The enhanced NACM privileges defined in this clause enable the Shared Resource Operator to configure the shared O-RU's list entries that have been previously configured by the Shared O-RU Host with the shared resource operator's **sro-id**. - -The O-RU NETCONF access control techniques defined in clause 6.5 are enhanced for operation with NETCONF clients corresponding to Shared Resource Operators of a shared O-RU, i.e. those where the user account of the - -NETCONF client has been configured with an **sro-id**. Specifically, the NETCONF access control read permissions for group name "carrier" are further refined for the following YANG models: - -- urn:o-ran:processing-elements:x.y -- urn:o-ran:uplane-conf:x.y -- urn:o-ran:performance-management:x.y -- urn:o-ran:message5:x.y -- urn:o-ran:shared-cell:x.y - -For the above models, the read privileges for specific node-instance-identifiers defined in Table 19.3.3-1 through Table 19.3.3-5 are refined based on the **sro-id**(s) associated with the user account of the NETCONF client. Normal NACM rules shall apply to any node-instance identifier not listed in the table. - -**Table 19.3.3-1: Refined NETCONF Access Control Read Privileges for the "carrier" group with YANG module o-ran:processing-elements:x.y** - -| Restricted node-instance-identifier | Refined privileges for "carrier" group for NETCONF clients with user name user-list entry containing a configured sro-id | -|----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| o-ran-elements:processing-elements/o-ran-elements:ru-elements | A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-elements:processing-elements/o-ran-elements:ru-elements/o-ran-elements:sro-id leaf matches the sro-id of the NETCONF client. | - -**Table 19.3.3-2: Refined NETCONF Access Control Read Privileges for the "carrier" group with YANG module o-ran:uplane-conf:x.y** - -| Restricted node-instance-identifier | Refined privileges for "carrier" group for NETCONF clients with user name user-list entry containing a configured sro-id | -|--------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-tx-links | A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-tx-links/o-ran-uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. | -| o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-rx-links | A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-rx-links/o-ran-uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. | -| o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-tx-endpoints | A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-tx-endpoints/o-ran-uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. | -| o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-rx-endpoints | A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-rx-endpoints/o-ran-uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. | -| o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:tx-array-carriers | A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:tx-array-carriers/o-ran-uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. | -| o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:rx-array-carriers | A NETCONF client with user name user-list entry containing a configured sro-id shall only have read privileges for those list entries where the o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:rx-array-carriers/o-ran-uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. | - -**Table 19.3.3-3: Refined NETCONF Access Control Read Privileges for the "carrier" group with YANG module o-ran:performance-management:x.y** - -| Restricted node-instance-identifier | Refined privileges for "carrier" group for NETCONF clients with user name user-list entry containing a configured stro-id | -|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| o-ran-pm:performance-measurement-objects/o-ran-pm:rx-window-measurement-objects | A NETCONF client with user name user-list entry containing a configured stro-id shall only have read privileges for those list entries where the o-ran-pm:performance-measurement-objects/o-ran-pm:rx-window-measurement-objects/o-ran-pm:tr-measured-result/o-ran-pm:name leaf refers to an o-ran-elements:processing-elements/o-ran-elements:ru-elements list entry where the o-ran-elements:processing-elements/o-ran-elements:ru-elements/o-ran-elements:stro-id leaf represents the stro-id of the NETCONF client or where the o-ran-pm:performance-measurement-objects/o-ran-pm:rx-window-measurement-objects/o-ran-pm:eexc-measured-result/o-ran-pm:eexc-id leaf matches a value of eexcid in the container o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-rx-endpoints/o-ran-uplane-conf:e-exc where the stro-id in o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-rx-endpoints/o-ran-uplane-conf:stro-id matches the stro-id of the NETCONF client or where the o-ran-pm:performance-measurement-objects/o-ran-pm:rx-window-measurement-objects/o-ran-pm:eexc-measured-result/o-ran-pm:eexc-id leaf matches a value of eexcid in the container o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-tx-endpoints/o-ran-uplane-conf:e-exc where the stro-id in o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-tx-endpoints/o-ran-uplane-conf:stro-id matches the stro-id of the NETCONF client. | -| o-ran-pm:performance-measurement-objects/o-ran-pm:tx-measurement-objects | A NETCONF client with user name user-list entry containing a configured stro-id shall only have read privileges for those list entries where the o-ran-pm:performance-measurement-objects/o-ran-pm:tx-measurement-objects/o-ran-pm:tr-measured-result/o-ran-pm:name leaf refers to an o-ran-elements:processing-elements/o-ran-elements:ru-elements list entry where the o-ran-elements:processing-elements/o-ran-elements:ru-elements/o-ran-elements:stro-id leaf represents the stro-id of the NETCONF client or where the o-ran-pm:performance-measurement-objects/o-ran-pm:tx-measurement-objects/o-ran-pm:eexc-measured-result/o-ran-pm:eexc-id leaf matches a value of eexcid in the container o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-rx-endpoints/o-ran-uplane-conf:e-exc where the stro-id in o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-rx-endpoints/o-ran-uplane-conf:stro-id matches the stro-id of the NETCONF client or where the o-ran-pm:performance-measurement-objects/o-ran-pm:tx-measurement-objects/o-ran-pm:eexc-measured-result/o-ran-pm:eexc-id leaf matches a value of eexcid in the container o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-tx-endpoints/o-ran-uplane-conf:e-exc where the stro-id in o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-tx-endpoints/o-ran-uplane-conf:stro-id matches the stro-id of the NETCONF client. | - -NOTE: The enhanced **stro-id** based NACM privileges in Table 19.3.3-3 do not limit the privileges of a NETCONF client associated with an **stro-id** to read Rx and Tx performance management results when the **object-unit-id** is configured as RU. A Shared O-RU Host can exclude such value of **object-unit-id** from the configuration of the o-ran-performance-management YANG model to avoid enabling a first Shared Resource Operator from recovering aggregate O-RU level performance data that may include performance data related to the resources of a second Shared Resource Operator. - -**Table 19.3.3-4: Refined NETCONF Access Control Read Privileges for the "carrier" group with YANG module o-ran:message5.x.y** - -| Restricted node-instance-identifier | Refined privileges for "carrier" group for NETCONF clients with user name user-list entry containing a configured stro-id | -|-------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| o-ran-msg5:ecpri-delay-message/o-ran-msg5:message5-sessions/o-ran-msg5:session-parameters | A NETCONF client with user name user-list entry containing a configured stro-id shall only have read privileges those list entries where the o-ran-msg5:ecpri-delay-message/o-ran-msg5:message5-sessions/o-ran-msg5:session-parameter/o-ran-msg5:processing-element-name leaf refers to an o-ran-elements:processing-elements/o-ran-elements:ru-elements list entry where the o-ran-elements:processing-elements/o-ran-elements:ru-elements/o-ran-elements:stro-id leaf represents the stro-id of the NETCONF client. | - -**Table 19.3.3-5: Refined NETCONF Access Control Read Privileges for the "carrier" group with YANG module o-ran:shared-cell:x.y** - -| Restricted node-instance-identifier | Refined privileges for "carrier" group for NETCONF clients with user name user-list entry containing a configured stro-id | -|--------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| o-ran-sc:shared-cell/o-ran-sc:shared-cell-config/o-ran-sc:shared-cell-copy-entities | A NETCONF client with user name user-list entry containing a configured stro-id shall only have read privileges for those list entries where the o-ran-sc:shared-cell/o-ran-sc:shared-cell-config/o-ran-sc:shared-cell-copy-entities/o-ran-sc:stro-id leaf-list includes the stro-id of the NETCONF client. | -| o-ran-sc:shared-cell/o-ran-sc:shared-cell-config/o-ran-sc:shared-cell-combine-entities | A NETCONF client with user name user-list entry containing a configured stro-id shall only have read privileges for those list entries where the o-ran-sc:shared-cell/o-ran-sc:shared-cell-config/o-ran-sc:shared-cell-combine-entities/o-ran-sc:stro-id leaf-list includes the stro-id of the NETCONF client. | -| o-ran-sc:shared-cell/o-ran-sc:shared-cell-config/o-ran-sc:shared-cell-copy-entities-selective-beam-id | A NETCONF client with user name user-list entry containing a configured stro-id shall only have read privileges for those list entries where the o-ran-sc:shared-cell/o-ran-sc:shared-cell-config/o-ran-sc:shared-cell-copy-entities-selective-beam-id /o-ran-sc:stro-id leaf-list includes the stro-id of the NETCONF client. | -| o-ran-sc:shared-cell/o-ran-sc:shared-cell-config/o-ran-sc:shared-cell-combine-entities-for-selective-beam-id | A NETCONF client with user name user-list entry containing a configured stro-id shall only have read privileges for those list entries where the o-ran-sc:shared-cell/o-ran-sc:shared-cell-config/o-ran-sc:shared-cell-combine-entities-for-selective-beam-id /o-ran-sc:stro-id leaf-list includes the stro-id of the NETCONF client. | - -For example, if the Shared O-RU has been configured to operate with two Shared Resource Operators, **stro-id** "23415" and **stro-id** "23410", then when a NETCONF client of the first Shared Resource Operator attempts to read the processing element configuration of the shared O-RU it can receive a reply as shown Figure 19.3.3-1, where the O-DU of the first Shared Resource Operator has an Ethernet MAC-address of 11:95:a0:af:5f:b9 and VLAN 100 is being used for the control and user-plane traffic between the shared O-RU and the O-DU of the first Shared Resource Operator. - -``` - - - - - element1 - 23415 - -``` - -``` - -10Geth0.100 - - - - 00:e0:fe:00:23:30 - - 100 - - 11:95:a0:af:5f:b9 - - - - - - - - - - - - - -``` - -**Figure 19.3.3-1: example rpc-reply to a first slo-id "23415"** - -Conversely, if the NETCONF client of the second Shared Resource Operator attempts to read the processing element configuration it can receive a reply as shown in Figure 19.3.3-2, where the O-DU of the second Shared Resource Operator has an Ethernet MAC-address of 5a:2a:a7:61:98:f0 and VLAN 200 is being used for the control and user-plane traffic between the Shared O-RU and the O-DU of the second Shared Resource Operator. - -``` - - - - - - - - - - element2 - - 23410 - - - - 10Geth0.200 - - - - 00:e0:fe:00:23:30 - - 200 - - 5a:2a:a7:61:98:f0 - - - - - - - - - - - - - -``` - -**Figure 19.3.3-2: example rpc-reply to a second slo-id "23410"** - -In addition to the enhanced read access privileges, the NETCONF server of the shared O-RU shall implement additional write access privileges for the following YANG model: - -- `urn:o-ran:uplane-conf:x.y` - -For the above model, the write privileges for specific node-instance-identifiers are refined based on the **sro-id** associated with the user account of the NETCONF client, as described in the Table 19.3.3-6. - -**Table 19.3.3-6: Refined NETCONF Access Control Write Privileges for the "carrier" group with YANG module o-ran:uplane-conf:x.y** - -| Restricted node-instance-identifier | Refined privileges for "carrier" group for NETCONF clients with user name user-list entry containing a configured stro-id | -|---------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:low-level-tx-links/o-ran:uplane-conf:name | The NETCONF client shall be prohibited from writing to this schema node for all list entries. | -| o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:low-level-tx-links/o-ran:uplane-conf:stro-id | The NETCONF client shall be prohibited from writing to this schema node for all list entries. | -| o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:low-level-tx-links | A NETCONF client with user name user-list entry containing a configured stro-id shall be prohibited from creating list entries. A NETCONF client with user name user-list entry containing a configured stro-id shall only have write privileges to enable updating of those list entries where the o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:low-level-tx-links/o-ran:uplane-conf:stro-id leaf-list includes the stro-id of the NETCONF client. | -| o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:low-level-rx-links/o-ran:uplane-conf:name | The NETCONF client shall be prohibited from writing to this schema node for all list entries. | -| o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:low-level-rx-links/o-ran:uplane-conf:stro-id | The NETCONF client shall be prohibited from writing to this schema node for all list entries. | -| o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:low-level-rx-links | A NETCONF client with user name user-list entry containing a configured stro-id shall be prohibited from creating list entries. A NETCONF client with user name user-list entry containing a configured stro-id shall only have write privileges to enable updating of those list entries where the o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:low-level-rx-links/o-ran:uplane-conf:stro-id leaf-list includes the stro-id of the NETCONF client. | -| o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:low-level-tx-endpoints/o-ran:uplane-conf:stro-id | The NETCONF client shall be prohibited from writing to this schema node for all list entries. | -| o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:low-level-tx-endpoints | A NETCONF client with user name user-list entry containing a configured stro-id shall be prohibited from creating list entries. A NETCONF client with user name user-list entry containing a configured stro-id shall only have write privileges to enable updating of those list entries where the o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:low-level-tx-endpoints/o-ran:uplane-conf:stro-id leaf-list includes the stro-id of the NETCONF client. | -| o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:low-level-rx-endpoints/o-ran:uplane-conf:stro-id | The NETCONF client shall be prohibited from writing to this schema node for all list entries. | -| o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:low-level-rx-endpoints | A NETCONF client with user name user-list entry containing a configured stro-id shall be prohibited from creating list entries. A NETCONF client with user name user-list entry containing a configured stro-id shall only have write privileges to enable updating of those list entries where the o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:low-level-rx-endpoints/o-ran:uplane-conf:stro-id leaf-list includes the stro-id of the NETCONF client. | - -**Table 19.3.3-7: Refined NETCONF Access Control Write Privileges for the "carrier" group with YANG module o-ran:uplane-conf.x.y (continued)** - -| Restricted node-instance-identifier | Refined privileges for "carrier" group for NETCONF clients with user name user-list entry containing a configured sro-id | -|----------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:tx-array-carriers/o-ran:uplane-conf:sro-id | The NETCONF client shall be prohibited from writing to this schema node for all list entries. | -| o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:tx-array-carriers | A NETCONF client with user name user-list entry containing a configured sro-id shall be prohibited from creating list entries. A NETCONF client with user name user-list entry containing a configured sro-id id shall only have write privileges to enable updating of those list entries where the o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:tx-array-carriers/o-ran:uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. | -| o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:rx-array-carriers/o-ran:uplane-conf:sro-id | The NETCONF client shall be prohibited from writing to this schema node for all list entries. | -| o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:rx-array-carriers | A NETCONF client with user name user-list entry containing a configured sro-id shall be prohibited from creating list entries. A NETCONF client with user name user-list entry containing a configured sro-id id shall only have write privileges to enable updating of those list entries where the o-ran:uplane-conf:user-plane-configuration/o-ran:uplane-conf:rx-array-carriers/o-ran:uplane-conf:sro-id leaf-list includes the sro-id of the NETCONF client. | - -### 19.3.4 Supervision monitoring between shared O-RU and shared resource operator O-DUs - -An O-RU Controller associated with a Shared Resource Operator shall use the per O-DU monitoring capability specified in clause 14.1.1. The Shared O-RU Host shall configure the **per-odu-monitoring** container in o-ran-supervision YANG model with the **sro-id** and **odu-id** values agreed to be used by the Shared Resource Operator. - -## 19.4 Shared O-RU interface management - -### 19.4.1 VLAN and IP address management - -The procedures defined in clauses 7.3 and 7.4 are used by the Shared O-RU Host to manage the VLAN and IP address configuration of the shared O-RU. - -### 19.4.2 Processing element configuration - -The procedures defined in clause 7.5 are used by the Shared O-RU Host to configure the processing elements in the shared O-RU. The optional **sro-id** leaf shall be used by the Shared O-RU Host to configure a particular **ru-elements** list entry as being uniquely associated with a particular Shared Resource Operator. - -NOTE 1: How the Shared O-RU Host becomes aware of information to identify the remote CU-Plane endpoints corresponding to the address(es) used by individual Shared Resource Operator O-DUs for control and user-plane traffic and included in the configuration of an **ru-elements** list entry is out of scope of the present document. - -The Shared Resource Operator O-DU needs to become aware of the local endpoint(s) in the O-RU configured for use in processing element(s) used by a particular Shared Resource Operator. One approach for the Shared Resource Operator O-DU to become aware of such information is for the NETCONF client of the Shared Resource Operator O-DU to subscribe to receive notifications due to updates of the O-RU's configuration datastore, using the techniques described in clause 6.4. - -NOTE 2: Any other approaches by which the operator of a Shared Resource Operator O-DU becomes aware of information related to the configured processing elements is out of scope of the present document. - -### 19.4.3 Shared resource operator O-DU verification of C/U-Plane transport connectivity - -The procedures defined in clause 7.6 are used by the Shared O-RU Host to configure the operation of C/U plane transport connectivity checks. These checks are able to be simultaneously performed between the individual Shared Resource Operator O-DUs and the shared O-RU. A Shared Resource Operator O-DU is able to recover details of the configured Maintenance End Point (MEP) and other necessary information on the Shared O-RU by reading the configuration associated with the **o-ran-lbm** YANG model. - -## 19.5 Shared O-RU C/U-Plane delay management - -### 19.5.1 Adaptive delay operation with shared O-RU - -Clause 14.2 of [2] specifies that the Shared O-RU Host configures shared O-RU aspects related to delay management. When a shared O-RU indicates that it supports the optional **ADAPTIVE-RU-PROFILE** feature, the Shared O-RU Host can decide not to employ such a feature. If the Shared O-RU Host decides to use the **ADAPTIVE-RU-PROFILE** feature, the Shared O-RU Host shall be responsible for configuring the **adaptive-delay-configuration** container. - -NOTE 1: How the Shared O-RU Host determines the parameters to use in the **o-du-delay-profile** container and/or the **transport-delay** container is out of scope of the present document. - -NOTE 2: Operation of the optional O-RU adaptive delay capability defined in clause 7.8 requires carriers to be disabled prior to the O-RU adapting its delay profile. If used by the Shared O-RU Host, how the shared O-RU host co-ordinates disablement of carriers amongst the Shared Resource Operators is out of scope of the present document. - -### 19.5.2 Measuring transport delay parameters with Shared O-RU - -As defined in clause 7.9, an O-RU that supports the optional eCPRI based delay measurement capability shall be able to support simultaneous operation of delay measurements over any configured processing element. Where these processing elements correspond to remote endpoints from different Shared Resource Operator O-DUs, the operation of eCPRI delay measurements will allow each Shared Resource Operator O-DU to recover the necessary timing compensation information from the O-RU. - -## 19.6 Shared O-RU configuration management - -### 19.6.1 Carrier configuration of the shared O-RU - -The "carrier" NACM privileges defined in clauses 6.5 and 19.3.3 prevent a NETCONF client with "carrier" privileges, and whose user account is configured with an **sro-id**, from creating particular named list entries for the following lists: - -- o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-tx-links -- o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-rx-links -- o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-tx-endpoints -- o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:low-level-rx-endpoints -- o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:tx-array-carriers -- o-ran-uplane-conf:user-plane-configuration/o-ran-uplane-conf:rx-array-carriers - -A NETCONF client with "carrier" privileges and whose user account is configured with an **sro-id** shall only be permitted to update list entries after the list entry has been created and configured with a **sro-id** associated with the Shared Resource Operator. - -## 19.6.2 Notification of configuration updates to shared resource operators - -All Multi-Operator O-RUs shall support the Notification of Updates to its Configuration Datastore functionality, as described in clause 9.4. Hence, any Shared Resource Operator may configure subscriptions to receive notifications of modifications to a shared O-RU's datastore, according to the defined NETCONF access control privileges for NETCONF client of the Shared Resource Operator. In particular, such an approach can be used by a Shared Resource Operator to determine when the shared O-RU host has configured **o-ran-uplane-conf** list entries which include the Shared Resource Operator's **sro-id**. - -## 19.7 Shared O-RU performance management - -The NETCONF client of a Shared Resource Operator is identified by using a **user** list entry in **o-ran-usermgmt** YANG model that contains a configured **sro-id**. Such a NETCONF client shall have restricted access privileges to the **o-ran-performance-management** YANG model as described in clause 19.3.3. - -An O-RU supporting the **SHARED-ORU-MULTI-OPERATOR** feature should support the **GRANULARITY-TRANSPORT-MEASUREMENT** and/or the **GRANULARITY-EAXC-ID-MEASUREMENT** features. These allow the O-RU to report **rx-window-measurement-objects** on a per ru-element and/or eaxcid basis, meaning window measurements pertain to the transport flows and/or eaxcids associated with a particular Shared Resource Operator. - -A Shared O-RU Host can configure multiple **remote-file-uploads** list entries corresponding to the individual file servers of different Shared Resource Operators. However, there is currently no role-based access control applied to file management based performance management reporting, as specified in clause 10.3.2. If access to configured measurement results needs to be controlled on a per Shared Resource Operator basis, file management based performance management should not be used. - -## 19.8 Shared O-RU fault management - -There is no role-based access control applied to O-RU fault management. Any NETCONF client, including those corresponding to Shared Resource Operator NETCONF client, are able to recover the **active-alarm-list** from the shared O-RU and are able to subscribe to receive notifications of future alarms as described in clause 11. - -## 19.9 Synchronisation aspects of shared O-RU - -Clause 14.3 of [2] specifies the synchronisation aspects of shared O-RU. Each individual Shared Resource Operator should subscribe to receive the notifications defined in the **o-ran-sync** YANG model. - -## 19.10 Co-ordinating service impacting procedures - -### 19.10.1 Reset operation - -The various procedures required to be performed by Shared O-RU Host may necessitate performing reset of the shared O-RU. The Shared O-RU Host should co-ordinate such procedures with the individual Shared Resource Operators. - -NOTE: How the Shared O-RU Host performs such co-ordination is out of scope of the present document. - -### 19.10.2 Locked administrative state - -The Shared O-RU Host can configure the **admin-state** of the shared O-RU which permits the Shared O-RU Host to set the **admin-state** to **locked**. The Shared O-RU Host should co-ordinate any changes to the **admin-state** of the shared O-RU with the individual Shared Resource Operators. - -NOTE: How the Shared O-RU Host performs such co-ordination is out of scope of the present document. - -### 19.10.3 Antenna calibration - -When the shared O-RU supports antenna calibration, the Shared O-RU Host shall be responsible for co-ordinating the operation of the antenna calibration procedure with individual Shared Resource Operators. - -NOTE: How the Shared O-RU Host performs such co-ordination is out of scope of the present document. - -## 19.11 Partitioning of shared O-RU carrier resources - -### 19.11.1 Partitioning of Shared O-RU advertised resources - -O-RU capabilities as a whole shall be advertised by the O-RU (e.g. parameters defined in o-ran-module-cap.yang, o-ran-beamforming.yang) at start-up to each SRO and Shared O-RU Host. Hence, each SRO sharing the O-RU shall be aware of complete O-RU resources. These O-RU resources shall be partitioned between multiple SROs based on pre-defined agreement (outside the scope of WG4). Each SRO is expected to configure and use its partitioned O-RU resources so that the maximum O-RU capacity is not exceeded. To clarify this with an example, value of parameters 'max-gain' and 'min-gain' in o-ran-uplane-conf YANG model, shall not be exceeded when multiple SROs use the same tx-array for the carriers configured by each of them. - -### 19.11.2 Partitioning of eAxC identities - -The eAxC-IDs shall be unique within the shared O-RU in the same direction (Tx or Rx) even across different processing elements that may correspond to connection to different Shared Resource Operators. The Shared O-RU Host partitions the eAxC-IDs between different Shared Resource Operators. - -NOTE: How the Shared O-RU Host decides on the eAxC-ID partitioning policy and how the partition policy information is signalled to the respective Shared Resource Operators is out of scope of the present document. - -The procedures described in clause 19.6.2 can be used by the Shared O-RU Host to confirm whether a Shared Resource Operator is adhering to the eAxC-ID partitioning policy. - -### 19.11.3 Partitioning of links, endpoints and array carriers - -The Shared O-RU Host creates the list entries for **low-level-tx-links**, **low-level-rx-links**, **low-level-tx-endpoints**, **low-level-rx-endpoints**, **tx-array-carriers** and **rx-array-carriers**, including unique configured **name** and one or more configured **sro-id**. The **sro-id** is used to partition links and array carriers between separate Shared Resource Operators. - -### 19.11.4 Partitioning of static endpoints - -The Shared O-RU Host allocates **static-low-level-rx-endpoints** and **static-low-level-tx-endpoints** to individual Shared Resource Operators. This allocation may take into account Shared Resource Operator requirements related to static configuration for PRACH and SRS as well as TDD pattern configuration. To allocate a **static-low-level-tx-endpoint** to a Shared Resource Operator, the Shared O-RU Host shall configure the **low-level-tx-endpoints** list entry with the name of the **static-low-level-tx-endpoint** and the **sro-id** of the Shared Resource Operator. To allocate a **static-low-level-rx-endpoint** to a Shared Resource Operator, the Shared O-RU Host shall configure a **low-level-rx-endpoints** list entry with the name of the **static-low-level-rx-endpoint** and the **sro-id** of the Shared Resource Operator. - -The procedures described in clause 19.6.2 can be used by the Shared O-RU Host to confirm whether a Shared Resource Operator is adhering to the static endpoint partitioning policy. - -### 19.11.5 Shared O-RU beamforming configuration - -When the shared O-RU supports the o-ran-beamforming YANG model, the allocation of array carrier resources and band configuration to individual Shared Resource Operators will refer to any corresponding static beamforming configuration of the shared O-RU. - -In this version of the specification, the operation of a shared O-RU with **rt-bf-weights-update-support** set to true is not defined. - -### 19.11.6 Shared O-RU with antenna line devices - -When the shared O-RU is connected to one or more antenna line devices as described in clause 14.4, the shared O-RU host shall be responsible for the operation of the antenna line devices. - -NOTE 1: How the details of the configuration of the one or more antenna line devices are shared with the respective Shared Resource Operators is out of scope of the present document. - -The Shared O-RU Host may be required to co-ordinate antenna line operations with the different Shared Resource Operators, e.g. remote electrical tilt. - -NOTE 2: How the Shared O-RU Host coordinates such operations is out of scope of the present document. - -## 19.12 Example shared O-RU carrier configuration and operation procedure - -An example procedure for configuring a shared O-RU is as follows: - -- 1) The Shared O-RU Host is assigned "sudo" privileges. The Shared O-RU Host allocates an **sro-id** to the Shared Resource Operator and creates account(s) for the Shared Resource Operator's NETCONF client(s) on the O-RU's NETCONF server which includes the **sro-id**. The Shared O-RU Host communicates the account information to the Shared Resource Operator. Optionally, the Shared O-RU Host can subscribe to be notified of updates to the O-RU's configuration datastore, using the techniques specified in clause 9.4 - -- 2) The Shared O-RU Host configures the list of **ru-elements** for the Shared Resource Operator based on agreed O-DU transport identifiers. Each such element has the corresponding **sro-id** parameter set to the value allocated to the Shared Resource Operator. - -NOTE 1: How the Shared O-RU Host becomes aware of information to identify the remote CU-Plane endpoints corresponding to the address(es) used by individual Shared Resource Operator O-DUs for control and user-plane traffic and included in the configuration of an **ru-elements** list entry is out of scope of the present document. - -- 3) The Shared O-RU Host creates the **tx-array-carriers** and **rx-array-carriers** list entries in relation to the agreed **tx-arrays** and **rx-arrays** for use by the Shared Resource Operator. Each of the list entries will have the corresponding **sro-id** allocated to the Shared Resource Operator configured in the list of **sro-ids** associated with the array carriers. - -NOTE 2: Configuring the **tx-array-carriers** and **rx-array carriers** list entries includes mandatory leaves which are specific to the Shared Resource Operator's configuration. The Shared O-RU Host can agree with the Shared Resource Operator how it will configure any mandatory parameters in its initial list configuration. - -- 4) The Shared O-RU Host creates **low-level-tx-endpoints** and **low-level-rx-endpoints** related to agreed partitioned **static-low-level-tx endpoints** and **static-low-level-rx-endpoints** respectively. Each of the list entries will have the corresponding **sro-id** allocated to the Shared Resource Operator configured in the list of **sro-ids** associated with the endpoints. - -NOTE 3: Configuring the **low-level-tx-endpoints** and **low-level-rx-endpoints** list entries includes mandatory leaves which are specific to the Shared Resource Operator's configuration. The Shared O-RU Host can agree with the Shared Resource Operator how it will configure any mandatory parameters in its initial configuration. - -NOTE 4: The Shared O-RU Host and the Shared Resource Operator can agree how information describing the list entries created in steps 2, 3 and 4 are to be shared. In one example, information is shared out of band between the two operators. In a second example, the operators can agree that the Shared Resource Operator will use a GET RPC to read the list entries configured by the Shared O-RU Host. Using this second approach, the NACM privileges ensure that the Shared Resource Operator only has permissions to read list entries that have been configured with its **sro-id**. - -- 5) The Shared Resource Operator enters the pre-configured list entry information into its management systems. -- 6) The Shared O-RU Host configures the **configured-client-info** container with IP address(es) of the NETCONF client(s) used by the Shared Resource Operator. This triggers the shared O-RU to call home to the configured client. The Shared Resource Operator uses the shared account information to establish a NETCONF session to the shared O-RU. -- 7) The Shared Resource Operator uses the NETCONF session to complete the configuration of the relevant **o-ran-uplane-conf** defined list entries for **tx-array-carriers**, **rx-array-carriers**, **low-level-tx-endpoints** and **low-level-rx-endpoints**. As the list entries are all configured with the **sro-id** of the Shared Resource Operator, then the NACM privileges described in clause 19.3.3 permit the Shared Resource Operator to over-write the initial mandatory parameters configured by the Shared O-RU Host with its required operational values. If the Shared O-RU Host subscribed to be notified of modifications to the O-RU's configuration store in step 1, then the Shared O-RU Host will be automatically notified of the committed changes to the shared O-RU's configuration by the Shared Resource Operator. -- 8) The Shared O-RU Host can read the modified configuration of the shared O-RU and the information used to determine whether the configuration by the Shared Resource Operator adheres to pre-agreed sharing policies. - -NOTE 5: How to determine whether the configuration adheres to a pre-agreed policy as well as any response triggered by determining that a configuration does not adhere to a pre-agreed policy are not defined in the present document. - -With the above steps successfully performed, the relationship between C/U-Plane application endpoints at Shared Resource Operator's O-DU and shared O-RU is configured. - -- 9) The Shared O-RU Host and Shared Resource Operator can subscribe to receive notifications of O-RU alarms. -- 10) The Shared O-RU Host configures the performance measurements performed by the shared O-RU. - -NOTE 6: The Shared O-RU Host and the Shared Resource Operator can agree how information describing the configured performance measurements are to be shared. In one example, information is shared out of band between the two operators. In a second example, the operators can agree that the Shared Resource Operator will use a GET RPC to read the performance management configuration. Using this second approach, the NACM privileges ensure that the Shared Resource Operator only has permissions to read performance management configuration associated with the **ru-elements** list entries and/or **exacid** values associated with the Shared Resource Operator's **sro-id**. - -- 11) The Shared Resource Operator can subscribe to receive notifications related to the shared O-RU's performance management counters. The NACM privileges defined in clause 19.3.3 restricts the Shared Resource Operator to only be able to recover measurements associated with the **ru-elements** list entries and/or **exacid** values associated with the Shared Resource Operator's **sro-id**. -- 12) The Shared Resource Operator performs carrier activation by setting the value of the parameter "active" at tx-array-carrier element / rx-array-carrier element to "ACTIVE" for those list entries configured with the **sro-id** of the Shared Resource Operator. -- 13) The Shared Resource Operator performs shared resource operator supervision as specified in clause 19.3.4. If an O-RU enters shared resource supervision failure, then as described in clause 19.3.4, the shared O-RU will deactivate any carriers uniquely associated with the **sro-id** of the Shared Resource Operator and raise an alarm notification indicating that it has lost SRO based supervision. - -## 19.13 Shared O-RU and LAA operation - -Operation of M-Plane procedures as specified in clause 16 by a Shared Resource Operator using a NETCONF account with "carrier" privileges is not defined in the present document. - -NOTE: This does not prevent the Shared O-RU Host from configuring LAA operation to operate in combination with its own component carriers. - -## 19.14 Shared O-RU operation in combination with shared cell - -Operation of M-plane procedures as specified in clause 17 by a Shared Resource Operator using a NETCONF account with "carrier" privileges is restricted based on the **sro-id** configured in the **user-list** entry for the NETCONF account. A shared O-RU that indicates it supports the o-ran-shared-cell model in its YANG library shall support the partitioning of copy and combine entities on an **sro-id** basis and limit read access to those list-entries where the configured **sro-id** matches that of the NETCONF account, as specified in clause 19.3.3. - -The present document further restricts all write access to the shared-cell YANG model from NETCONF accounts with user name **user-list** entry containing a configured **sro-id** and "carrier" privileges. As a consequence, the Shared O-RU Host shall be responsible for configuring shared cell copy and combine parameters on behalf of each Shared Resource Operator. - -NOTE: How the Shared O-RU Host co-ordinates the configuration of copy and combine parameters between one or more Shared Resource Operators is outside the scope of the present document. - -## 19.15 Certificate and trust anchor management - -For mTLS, both the client and the server need to have access to a trust anchor to verify the peer. - -NOTE : It is the responsibility of the Shared Resource Operator and Shared O-RU Host to develop Trust Anchor management processes. Such processes are outside the scope of the present document. - -As explained in clause 6.2.6.0, a shared O-RU needs to be able to trace the peer's certificate path to a valid trust anchor. Also, the peer needs to be able to trace the shared O-RU's certificate path to a valid trust anchor. Peers of a shared O-RU include O-RU controllers operated by either the Shared O-RU Host or a Shared Resource Operator (SRO). - -In order to achieve mutual authentication: - -- The shared O-RU shall be enrolled with the Shared O-RU Host PKI as defined in clause 6.2.6.1 and enable new trust anchors to be provisioned as defined in clause 6.2.6.0. -- An O-RU controller operated by the Shared O-RU Host should be enrolled with the Shared O-RU Host PKI and be provided with the trust anchor of the Shared O-RU Host PKI -- An O-RU controller owned by an SRO should be enrolled with that SRO's PKI and provide capabilities to be provisioned with new trust anchors. - -This allows a Shared O-RU Host to install the trust anchor(s) corresponding to SRO PKI(s) involved in the shared O-RU operation. This enables the O-RU to authenticate the O-RU controllers of all SROs and also allows all SROs involved in shared O-RU operation to install the trust anchor of the Shared O-RU Host PKI, enabling the O-RU controllers to authenticate the shared O-RU. - ---- - -## 20 Network energy saving - -### 20.1 Introduction - -This clause describes the requirements and scope of energy savings techniques relevant to the lower layer split M-Plane interface. The following techniques are optionally supported by O-RUs to implement energy savings: - -- Carrier deactivation. -- RF channel switch off/on (C-Plane controlled and M-Plane controlled). -- Advanced sleep modes. -- Deep hibernate. -- Max output power control. - -## 20.2 Carrier deactivation for energy saving - -### 20.2.1 High level principle of carrier deactivation for energy saving - -This clause provides basic description of how an O-RU's carrier can be deactivated to achieve the energy savings within an O-RU. - -In order to achieve the energy saving, NETCONF Client uses the existing parameter [tr]x-array-carrier::**active** to activate or de-activate [tr]x-array-carriers. NETCONF Client configures the parameter to INACTIVE to deactivate specific carrier. This causes the parameter [tr]x-array-carrier::**state** transition to DISABLED (can go through BUSY). In a result, power consumption of O-RU is reduced because O-RU does not need to process C-Plane and U-plane traffic. - -Additionally, when [tr]x-array-carriers are inactive and when **energy-saving-enabled** is set to true, the O-RU may turn off circuitry associated with carrier processing to further reduce power consumption. - -NOTE 1: The actual reduced value of power consumption depends on the O-RU's implementation. - -NOTE 2: Prior to version 14 of the present document, the O-RU operation when **active** is set to SLEEP was not defined. Clause 15.3.2 now defines O-RU operation for such cases. - -NOTE 3: For details about how parameters energy-saving-enabled and [tr]x-array-carrier::**active** interact - see clause 9.1.3 "Modify state". - -### 20.2.2 Synchronisation aspects for carrier deactivation for energy saving - -When **power-state** of o-ran-hardware is SLEEPING, C/U/S functions on O-RU may be stopped to reduce energy consumption. If O-RU stops S-plane function, a certain period which depends on the O-RU implementation will be required to make carrier activation again. NETCONF client should set **energy-saving-enabled** to FALSE to ensure O-RU is ready to immediately activate a carrier. - -## 20.3 RF channel switch off/on for energy saving - -### 20.3.1 TRX control – C-Plane controlled - -#### 20.3.1.1 Introduction - -TRX control via C-Plane messages is used to achieve energy saving through disabling one or more O-RU array elements for a defined or undefined period of time. For example, an O-DU can switch off 32 out of 64 array elements of a massive MIMO antenna array. The TRX control capability is described below. - -#### 20.3.1.2 TRX control module capabilities - -The O-RU exposes the capability to support energy saving through disabling some or all of the O-RU's array elements by including support of the feature **TRX-CONTROL** in its o-ran-wg4-features.yang YANG module. If the feature is supported, then an O-RU controller can use the NETCONF session to recover the associated O-RU TRX control capability information and parameters. These capability attributes are defined for each [tr]x-arrays. These capabilities can be recovered by an O-RU controller at the O-RU start up as part of the o-ran-uplane-conf.yang YANG module operations. The attributes are: - -- 1) **trx-control-capability-info**: A container in o-ran-uplane-conf.yang YANG module with capabilities that are specific to TRX Control for each [tr]x-arrays. The parameters in the container include the following: - -- **supported-trx-control-masks:** A list of TRX control configurations that are supported by the O-RU which are reported with their corresponding **mask-name** and **antenna-mask** values. Refer to the O-RAN CUS plane specification [2], clause 16.2 for more details on the usage of antenna masks. The absence of the list **supported-trx-control-masks** indicates that any combination of antenna mask is supported by the O-RU for a particular [tr]x-array. - - **sleep-mode-type:** This value indicates the sleep modes supported by the O-RU for a particular [tr]x-array as specified in the O-RAN CUS plane specification [2], Table 16.1-1. - - **wake-up-duration:** This value indicates the reported wake-up time (in microseconds) for each individual sleep mode for the TRX(s) corresponding to a particular [tr]x-array. The O-DU can convert the wake-up duration in microseconds to the respective number of slots based on the SCS(s) supported by the O-RU (for more details, refer to O-RAN CUS plane specification [2], clause 16.1). - - **wake-up-duration-guaranteed:** The capability of the O-RU to guarantee the complete wake-up operation or to become active within the duration reported in **wake-up-duration**. The guaranteed wake-up time indicate a wake-up duration that is invariant to any O-RU condition. This field shall be reported as "FALSE" if the O-RU cannot assure the wake-up time, in which case the value reported in **wake-up-duration** is considered as the minimum wake-up duration. For **sleep-mode-type** reported as "SLEEP\_MODE\_0", the **wake-up-duration-guaranteed** shall be reported as "TRUE". Refer to the O-RAN CUS plane specification [2], clause 16.6 for more details on the differences between guaranteed and minimum wake-up durations. - - **defined-duration-sleep-supported:** The capability of the O-RU to support the defined sleep functionality as specified in O-RAN CUS plane specification [2], clause 16.4. - - **undefined-duration-sleep-supported:** The capability of the O-RU to support the un-defined sleep functionality as specified in O-RAN CUS plane specification [2], clause 16.5. -- 2) **energy-saving-capability-common-info:** A container in o-ran-module.cap.yang YANG module used to expose the O-RU capabilities common to both TRX control and advanced sleep modes. The parameters in the container include the following: -- **ST8-ready-message-supported:** The capability of the O-RU to support the "ready" message via Section Type 8 command. This message is used to indicate the O-RU readiness after waking up from a commanded sleep mode having a non-guaranteed wake-up time. Refer to the O-RAN CUS plane specification [2], clauses 7.5.3.55 and 16.6.2 for more details on the ST8 ready command. - - **sleep-duration-extension-supported:** The capability of the O-RU to support the extension of a defined sleep interval. Refer to the O-RAN CUS plane specification [2], clause 16.8 for more details on the sleep extension. - - **emergency-wake-up-command-supported:** The capability of the O-RU to support emergency wake-up procedure. Refer to the clause 20.3.1.3 for more details on the emergency wake-up procedure. - -### 20.3.1.3 Emergency wake-up procedure for TRX control - -This clause describes the optional capability by which the O-RU's CU plane processing units and/or array elements and/or other components that were put to sleep by a TRX Control command (or ASM command) can be woken up by the NETCONF client as specified in O-RAN CUS plane specification [2], clause 16.11. The O-RU exposes this ability to support emergency wake-up by including the leaf **emergency-wake-up-command-supported** in o-ran-module-cap.yang YANG module. - -A NETCONF client can send a RPC in order to wake-up the O-RU's CU plane processing units and/or array elements and/or other components that have been put to sleep by a TRX Control command as illustrated in Figure 20.3.1.3-1. - -In the case of Shared O-RU (O-RUs that support the **SHARED-ORU-MULTI-OPERATOR** feature), only the Shared O-RU Host can send a RPC which may include one or more optional **sro-ids**. Therefore, only the CU plane processing units and/or array elements that are specific to the O-DU that is associated with the received **sro-id** are woken-up. If **sro-id** is not included in the RPC, the O-RU shall wake-up all the CU plane processing units and/or array elements irrespective of the O-DU. - -Subsequently, a notification shall be sent by the O-RU to all subscribed O-DUs when the emergency wake-up procedure is complete, after which the O-DUs may activate carriers (if needed) and then operate the C-Plane and U-Plane to support user traffic. In the case of Shared O-RU (O-RUs that support the **SHARED-ORU-MULTI-OPERATOR** feature), separate notification shall be sent for each **sro-id** received in the RPC. - -![Sequence diagram of Emergency Wake-up Procedure showing interactions between NETCONF Server (O-RU) and NETCONF Client (O-RU Controller).](af01656e21a42c1d856cfb21185cd50e_img.jpg) - -``` - -sequenceDiagram - participant Server as NETCONF Server/ -Notification Producer/ -(O-RU) - participant Client as NETCONF Client/ -Notification Subscriber/ -(O-RU Controller) - - Client->>Server: [1] - - - Server-->>Client: [2] - Note over Server: Wake-up operation is completed. - Server->>Client: [3] - - - -``` - -Sequence diagram of Emergency Wake-up Procedure showing interactions between NETCONF Server (O-RU) and NETCONF Client (O-RU Controller). - -Figure 20.3.1.3-1 Emergency Wake-up Procedure - -### 20.3.1.4 Interaction with M-Plane processing - -An O-RU supporting RF channel switch off/on for energy saving shall be able to disable C/U plane monitoring (see clause 7.10). For example, an O-RU may support the **cu-plane-monitoring** container in its o-ran-supervision.yang model, allowing an O-DU to disable C/U plane monitoring operation. - -Operation of other M-plane procedures, including measuring of transport delay (clause 7.9), C/U plane transport connectivity verification (clause 7.6) and O-RU synchronisation (clause 13) shall not be affected by network energy savings functionality. - -## 20.3.2 TRX control – M-Plane controlled - -### 20.3.2.1 Introduction - -TRX control via M-Plane messages is used to achieve energy saving through disabling one or more O-RU array elements for an undefined period of time (until a next command is received). For example, an O-DU can switch off 32 out of 64 array elements of a massive MIMO antenna array. The TRX control capability and configuration are described in clauses 20.3.2.2 and 20.3.2.3. - -NOTE: Clause 15.3.2 specifies another set of conditions allowing O-RU to save energy by disabling array elements. - -### 20.3.2.2 TRX control capability - -The O-RU exposes the capability to support energy saving through disabling some or all of the O-RU's antenna array elements by including support of the feature **MPLANE-TRX-CONTROL** in its o-ran-wg4-features.yang YANG module. If the feature is supported, then an O-RU controller can use the NETCONF session to recover the associated O-RU TRX control capability information and parameters. These capability attributes are defined for each [tr]x-arrays. These capabilities can be recovered by an O-RU controller at the O-RU start up as part of the o-ran-uplane-conf.yang YANG module operations. The attributes are: - -- 1) **mplane-trx-control-txarr-capability-info:** A container in o-ran-uplane-conf.yang YANG module with capabilities that are specific to TRX Control for each tx-arrays. The parameters in the container include the following: - - **mplane-trx-control-supp-antenna-masks:** A grouping which contains the list **mplane-supported-trx-control-masks**, which is a list of TRX control configurations that are supported by the O-RU which are reported with their corresponding **antenna-mask** values. Refer to the O-RAN CUS plane specification [2], clause 16.2 for more details on the usage of antenna masks. The absence of the list **mplane-supported-trx-control-masks** indicates that any combination of antenna mask is supported by the O-RU for a particular [tr]x-array. If an antenna mask list is present, an all-ones antenna mask shall be included in the list to assure all array elements can be turned on. -- NOTE: If the **mplane-supported-trx-control-masks** contains a single all-ones antenna mask, that means the only valid antenna mask to configure is all array elements activated, meaning the TRX Control capability is not present. -- 2) **mplane-trx-control-rxarr-capability-info:** A container in o-ran-uplane-conf.yang YANG module with capabilities that are specific to TRX Control for each rx-array. The parameters in the container include the following: - - **mplane-trx-control-supp-antenna-masks:** Same as this parameter description within mplane-trx-control-txarr-capability-info above. - -### 20.3.2.3 TRX control configuration - -To support [tr]x-array level O-DU controlled antenna array configuration, new O-RU level node **array-config-group** is introduced. For M-Plane TRX control the node contains two lists **tx-array-antenna-mask-config** and **rx-array-antenna-mask-config**, one each for specifying tx-array and rx-array configuration for TRX control respectively. The list is indexed using **array-name** and contains parameters **antenna-bitmask** and **antenna-bitmask-index**. These two parameters per **tx-array** and **rx-array** list entry may be used by the O-RU controller to perform TRX Control. It is problematic if **TRX Control** commands are issued for sub-arrays of a larger array due to the potential interaction of multiple **TRX Control** commands affecting the same array elements which are part of multiple [tr]x-arrays. Therefore, - -the antenna mask configuration shall be done for the largest tx or rx array that is advertised by the O-RU, not for the **tx-array or rx-array** which is a subset of the largest array (multiple non-overlapping largest arrays are possible). The effect of the configuration command shall be to impact the largest array (whether that largest array has any carriers assigned to it or not). - -For the case where the O-RU advertises **mplane-supported-trx-control-masks** list, RPC **edit-config** shall be used to configure a specific antenna mask value by specifying a given **antenna-bitmask-index** for the [tr]x-array using the YANG parameter **[tr]x-array-antenna-mask-config**. - -EXAMPLE 1: configuration of a given 32-bit tx antenna mask by specifying the antenna-index: - -``` - - tx-array-1 - 1 - -``` - -For the case where the O-RU does not advertise **mplane-supported-trx-control-masks** list for a given [tr]x-array, the RPC **edit-config** shall be used to configure a specific **antenna-bitmask** value for the [tr]x-array using the YANG parameter **[tr]x-array-antenna-mask-config**. - -EXAMPLE 2: configuration of a 32-bit tx antenna mask is shown below: - -``` - - tx-array-1 - 111111110000000000000000000011111111 - -``` - -NOTE: Binary values are encoded with a base-64 encoding (see reference [4]) so the above mask would actually be represented as "/wAA/w==". - -Prior to any M-Plane TRX Control antenna mask or associated antenna index being configured, the value of the antenna mask shall be considered to be all-ones, meaning all array-elements are enabled. - -Because updating an antenna mask via M-Plane is an asynchronous operation, the O-RU shall notify all notification subscribers that the [tr]x-array specific commanded mask or antenna mask index has been implemented, using the **mplane-trx-control-ant-mask-update** notification, as detailed in the Figure 20.3.2.3-1. - -![Sequence diagram for TRX control configuration (M-Plane controlled) between a NETCONF Server (O-RU) and a NETCONF Client (O-RU Controller).](4c1d8ed1a2c9ff9594c1ca4f179a9c33_img.jpg) - -``` - -sequenceDiagram - participant O-RU as NETCONF Server/ (O-RU) - participant O-RU-Controller as NETCONF Client/ (O-RU Controller) - - Note right of O-RU: Antenna bit-mask(s) implemented - - alt O-RU advertises mplane-supported-trx-control-masks list - O-RU->>O-RU-Controller: 1 antenna-bitmask-index - else O-RU does not advertise mplane-supported-trx-control-masks list - O-RU->>O-RU-Controller: 1 antenna-bitmask - end - O-RU-Controller-->>O-RU: 2 - Note left of O-RU: Antenna bit-mask(s) implemented - O-RU->>O-RU-Controller: 3 mplane-trx-control-ant-mask-update - -``` - -The diagram illustrates the interaction for TRX control configuration. It starts with a **NETCONF Client/ (O-RU Controller)** sending an **edit-config** request (Step 1) to the **NETCONF Server/ (O-RU)**. The request is wrapped in an **alt** block titled **[O-RU advertises mplane-supported-trx-control-masks list]**. Inside the alt block, there are two options: - - -- [O-RU advertises mplane-supported-trx-control-masks list]**: The request contains ` 1 antenna-bitmask-index `. -- [O-RU does not advertise mplane-supported-trx-control-masks list]**: The request contains ` 1 antenna-bitmask `. - - The O-RU responds with a **rpc-reply** (Step 2) containing ``. A note on the left indicates **Antenna bit-mask(s) implemented**. Finally, the O-RU sends a **notification** (Step 3) to the client containing ` mplane-trx-control-ant-mask-update `. - -Sequence diagram for TRX control configuration (M-Plane controlled) between a NETCONF Server (O-RU) and a NETCONF Client (O-RU Controller). - -Figure 20.3.2.3-1 – TRX control configuration (M-Plane controlled) - -To reduce unexpected transient related to the turning-off process, the O-DU may send zero-value beamforming weights for any array element to be turned off prior to issuing the edit-config command turning off any array-elements, and may keep them at zero-value while the array-elements are off. - -To reduce unexpected transient related to the turning-on process, the O-DU may send zero-value beamforming weights for any disabled array element to be turned on prior to issuing the edit-config command turning on the array-elements, and may keep them at zero-value until receiving the notification that the new antenna mask activating those array elements is received. - -When TRX Control has disabled all array elements in a [tr]x-array, the O-RU may disable CU-Plane processing associated with all array-carriers using that [tr]x-array, and the O-DU should assume that the CU-Plane processing for those array-carrier has been halted by the O-RU. - -## 20.3.2.4 Interaction with M-Plane processing - -An O-RU supporting M-Plane controlled TRX Control for energy saving shall be able to disable C/U plane monitoring (see clause 7.10). For example, an O-RU may support the **cu-plane-monitoring** container in its o-ran-supervision.yang model, allowing an O-DU to disable C/U plane monitoring operation. - -Operation of other M-plane procedures, including measuring of transport delay (clause 7.9), C/U plane transport connectivity verification (clause 7.6) and O-RU synchronization (clause 13) shall not be affected by this network energy savings feature's functionality. - -### 20.3.2.5 Interaction with C-Plane TRX Control and ASM - -An O-DU using M-Plane TRX Control for energy saving shall be able to also use C-Plane TRX Control when an O-RU supports both. However, the O-DU shall ensure the current M-Plane-commanded antenna mask (using **antenna-mask** or **antenna-index** pointing to O-RU advertised supported antenna mask) is all-ones (all array elements active) prior to issuing any C-Plane TRX Control commands, and the O-DU shall ensure the current C-Plane-commanded antenna mask is all-ones (all array-elements active) prior to issuing any M-Plane TRX Control commands. - -An O-DU using M-Plane TRX Control for energy saving shall be able to also use C-Plane ASM when an O-RU supports both. However, the O-DU shall ensure the current M-Plane-commanded antenna mask is all-ones (all array elements active) prior to issuing any C-Plane ASM commands, and the O-DU shall ensure the current C-Plane-commanded ASM conditions are terminated prior to issuing any M-Plane TRX Control commands. - -NOTE: The antenna mask is considered to be all-ones prior to any M-Plane or C-Plane TRX Control command being issued. - -## 20.3.3 Data layer control - -### 20.3.3.1 Introduction - -Data layer control is used to achieve energy saving through reducing the number of data layers independent of TRX-Control. For example, the energy consumption of an O-RU can be reduced by turning off certain HW components like processing units of FPGA/GPUs or CPU/GPU cores or by running at a lower clock speed along with reduced processing requirements [i.6]. The methodology of data layer control using endpoint switch off/on is described in clause 20.3.3.2. - -### 20.3.3.2 Capability and configuration of data layer control - -This clause provides basic description of how an O-RU's data layers can be reduced to achieve the energy savings within an O-RU. The O-RU exposes the capability to support energy saving by including support of the feature **MPLANE-DATA-LAYER-CONTROL** in its *o-ran-wg4-features.yang* YANG module. The support of this feature means an O-RU shall advertise the data node **energy-sharing-group-id** per *static-low-level-[tr]x-endpoints*. Multiple endpoints that have the same **energy-sharing-group-id** value signifies that these endpoints share common underlying HW components. - -When an O-RU indicates it supports the **MPLANE-DATA-LAYER-CONTROL** feature, a global configuration leaf-list parameter **energy-sharing-groups-disabled** is available in the *o-ran-uplane-conf* YANG model. An O-RU Controller may turn off a group of data layers by adding one or more **energy-sharing-group-id** into the **energy-sharing-groups-disabled** list. When one or more **energy-sharing-group-id** is included in the **energy-sharing-groups-disabled** list, the O-RU shall switch off the underlying HW components common to that **energy-sharing-group-id** thereby resulting in energy savings. If an endpoint has multiple **energy-sharing-group-id**, the underlying HW components associated with the endpoint shall be turned off if any of the **energy-sharing-group-id** corresponding to the endpoint is added to the leaf-list **energy-sharing-groups-disabled**. The O-RU controller shall trigger data layer control only for the energy-sharing-group of endpoints all of whose eAxC-id values are currently not being used by the O-DU (i.e. not referenced, either directly or indirectly, within any CU-plane messages, e.g. by using Section Extension 10). - -An O-RU controller may turn on a group of data layers by removing the **energy-sharing-group-id** from the **energy-sharing-groups-disabled** list. When the **energy-sharing-group-id** is removed from the **energy-sharing-groups-disabled** list, the O-RU shall switch on the underlying HW components common to that **energy-sharing-group-id**. If an endpoint has multiple **energy-sharing-group-id**, the underlying HW components associated with the endpoint shall be turned on only if all the **energy-sharing-group-id** corresponding to the endpoint are removed from the leaf-list - -**energy-sharing-groups-disabled**. Subsequently, when the wake-up procedure is complete a notification shall be sent by the O-RU to all subscribed O-RU controllers as detailed in the Figure 20.3.3.2-1. - -![Sequence diagram showing the data layer control wake-up notification process between an O-RU and an O-RU Controller.](b543946164dcd60756be812898e547e0_img.jpg) - -``` - -sequenceDiagram - participant ORU as NETCONF Server/ -Notification Producer/ -(O-RU) - participant ORUC as NETCONF Client/ -Notification Subscriber/ -(O-RU Controller) - - ORUC->>ORU: [1] - -energy_sharing_group_id - - - ORU-->>ORUC: [2] - Note over ORU: Wake-up operation is completed. - Note over ORU: Notification about wake-up - ORU->>ORUC: [3] - - -energy_sharing_group_id - - - -``` - -Sequence diagram showing the data layer control wake-up notification process between an O-RU and an O-RU Controller. - -Figure 20.3.3.2-1 - Data layer control wake-up notification - -## 20.4 Advanced sleep modes for energy saving - -### 20.4.1 ASM module capabilities - -The O-RU exposes its ability to support energy saving by disabling some part of the processing, which impacts the O-RU's array elements (based on the command scope of the received ST4 message) by including support of the feature **ADVANCED-SLEEP-MODE** in `o-ran-wg4-features.yang` YANG module. If the feature is supported, then an O-RU controller can use the NETCONF session to recover the O-RU ASM capabilities. These capability attributes are defined for each **[tr]x-arrays**. These capabilities can be recovered by an O-RU controller at the O-RU start up as part of the `o-ran-uplane-conf.yang` YANG module. The attributes are: - -- 1) **asm-capability-info:** A container in `o-ran-uplane-conf.yang` YANG module with capabilities that are specific to Advanced sleep modes for each **[tr]x-arrays**. The parameters in the container include the following: - - **sleep-mode-type:** This value indicates the sleep mode supported by the O-RU for a particular **[tr]x-array** as specified in the O-RAN CUS plane specification [2], Table 16.1-1. - - **wake-up-duration:** This value indicates the reported wake-up time (in microseconds) for a particular sleep mode for a particular **[tr]x-array**. The O-DU can convert the wake-up duration in microseconds to - -the respective number of slots based on the SCS(s) supported by the O-RU (for more details, refer to O-RAN CUS plane specification [2], clause 16.1). - -- **wake-up-duration-guaranteed**: The capability of the O-RU to guarantee full wake-up operation within the time reported in **wake-up-duration**. This field shall be reported as "FALSE" if the O-RU cannot assure the wake-up time, in which case the value reported in **wake-up-duration** is considered as the minimum wake-up time. For **sleep-mode-type** reported as "SLEEP\_MODE\_0", the **wake-up-duration-guaranteed** shall be reported as "TRUE". Refer to the O-RAN CUS plane specification [2], clause 16.6 for more details on the differences between guaranteed and minimum wake-up durations. -- **defined-duration-sleep-supported**: The capability of the O-RU to support the defined sleep functionality as specified in O-RAN CUS plane specification [2], clause 16.4. -- **undefined-duration-sleep-supported**: The capability of the O-RU to support the un-defined sleep functionality as specified in O-RAN CUS plane specification [2], clause 16.5. - -NOTE: The leafs sleep-mode-type, wake-up-duration, wake-up-duration-guaranteed, defined-duration-sleep-supported, undefined-duration-sleep-supported defined in this section are distinct from the leafs of the same name defined in clause 20.3.1.2. - -- 2) The container **energy-saving-capability-common-info** as defined in clause 20.3.1.2 is also applicable for ASM. - -## 20.4.2 Emergency wake-up procedure for ASM - -The O-RU shall support emergency wake-up procedure for Advanced sleep modes similar to TRX control as described in clause 20.3.1.3. - -## 20.4.3 Interaction with M-Plane processing - -An O-RU supporting advanced sleep modes for energy saving shall be able to disable C/U plane monitoring (see clause 7.10). For example, an O-RU may support the **cu-plane-monitoring** container in its o-ran-supervision.yang model, allowing an O-DU to disable C/U plane monitoring operation. - -Operation of other M-plane procedures, including measuring of transport delay (clause 7.9), C/U plane transport connectivity verification (clause 7.6) and O-RU synchronisation (clause 13) shall not be affected by network energy savings functionality. - -## 20.5 Deep-hibernate - -### 20.5.1 Introduction - -Deep-hibernate is an O-RU mode used to achieve relatively higher energy saving by disabling all carriers and stopping the C/U/S/M functions and corresponding processing units when compared to power-state defined in clause 9.1.3 or advanced sleep mode defined in clause 20.4. - -### 20.5.2 Deep-hibernate module capabilities - -The O-RU exposes its ability to support deep hibernate functionality by including support of the feature **DEEP-HIBERNATE** in its o-ran-wg4-features.yang YANG module. The support of this feature means an O-RU shall advertise the data node **max-hibernate-time-duration** and optionally advertise data node **min-hibernate-time-duration**. - -## 20.5.3 Configuration of deep-hibernate - -This clause provides description of how deep-hibernate can be activated in the O-RU. - -An O-RU Controller shall send an RPC **** to activate the deep-hibernate in O-RU, which initiates the corresponding timer. The RPC shall include the hibernate-time duration. - -Before the O-DU sends the deep-hibernate RPC, the O-DU shall ensure that all [tr]x-array-carrier(s) shall be deactivated as defined in Figure 15.3.2-0b. If an O-RU receives a **deep-hibernate** RPC while one or more [tr]x-array-carriers are active, then it shall reject the RPC, including in the error-message the reason why deep-hibernation cannot be activated. - -If the **deep-hibernate** RPC is accepted by the O-RU, the O-RU shall cease processing control-plane, user-plane and synchronization plane operations. If accepted, the O-RU shall send a notification to all subscribed O-RU Controllers to indicate the deep-hibernate is activated, where the notification shall also indicate the **hibernate-time**. Upon receiving notification from an O-RU, a subscribed O-RU Controller shall send the RPC **** to the O-RU. The O-RU shall suspend all NETCONF call home operations and/or PNF Registration operations after deep-hibernate mode activated. - -Once all NETCONF sessions are terminated, the M-Plane functions on O-RU shall then be stopped to reduce the further energy consumption and O-RU enters deep-hibernate. The O-RU shall not respond to any incoming NETCONF session while in deep-hibernate mode. - -NOTE: If any NETCONF session is not closed by NETCONF Client then the O-RU behavior is unspecified. - -At the end of **hibernate-time**, the O-RU shall perform a re-start and follow the procedures defined in Figure 6.1-1. Upon restart, the O-RU shall set the **restart-cause** to DEEP-HIBERNATE-RESTART using o-ran-operations.yang YANG module. In case of autonomous O-RU restart while in deep-hibernate mode, e.g. because of some software failure, the O-RU is not expected to continue the deep-hibernate mode. - -In the case the O-RU is operating as a Shared O-RU as described in clause 19, an O-DU operating with "carrier" privileges as defined in Table 6.5-1 shall be prohibited from sending the RPC ****. How the Shared O-RU Host coordinates with other O-DU(s) for the deep-hibernate activation is out of scope of this document. - -![Sequence diagram of Deep hibernate operation between NETCONF Server/ (O-RU) and NETCONF Client/ (O-RU Controller).](6ba886ed1f943623b89bce107f127e61_img.jpg) - -``` - -sequenceDiagram - participant S as NETCONF Server/ (O-RU) - participant C as NETCONF Client/ (O-RU Controller) - C->>S: [1] x minutes - S->>C: [2] - Note over S: C/U/S Plane functions stopped - S->>C: [3] - Note over S: deep-hibernate timer started - C->>S: [4] ... - S->>S: [5] Disable the M-Plane processing units and functions - Note over S: O-RU enters deep-hibernate - S->>S: [6] hibernate-time is reached and O-RU re-starts - -``` - -The diagram illustrates the sequence of operations for a deep hibernate. It begins with the NETCONF Client (O-RU Controller) sending a deep-hibernate request (Step 1) to the NETCONF Server (O-RU). The server responds with an OK (Step 2). Following this, C/U/S Plane functions are stopped. The server then sends a notification (Step 3) that deep-hibernate-activated and starts a deep-hibernate timer. The client sends a close-session request (Step 4). The server then disables the M-Plane processing units and functions (Step 5) and enters deep-hibernate. Finally, after the hibernate-time is reached, the O-RU re-starts (Step 6). - -Sequence diagram of Deep hibernate operation between NETCONF Server/ (O-RU) and NETCONF Client/ (O-RU Controller). - -Figure 20.5.3-1 – Deep hibernate operation - -## 20.6 Maximum output power control - -### 20.6.1 Introduction - -Maximum output power control is an energy saving method used to reduce power consumption in O-RU. To achieve this, the number of scheduled PRBs may be restricted by the O-DU, allowing the O-RU to adapt Power Amplifier (PA) accordingly. - -## 20.6.2 Maximum output power control capability - -The O-RU exposes the capability to save energy through adjusting the maximum tx power by reporting support of the feature **MAX-POWER-CONTROL** in its **o-ran-wg4-features.yang** YANG module. O-RU supporting **MAX-POWER-CONTROL** reports capabilities using following YANG schema nodes: - -- 1) **max-power-control-methods-supported**: The control methods used to define the capabilities supported by the O-RU at two granularities: - - **MAX-POWER-PER-TX-ARRAY-CONTROL**: Enable the O-DU to configure the power reduction for each tx-array. - - **MAX-POWER-PER-TX-ARRAY-CARRIER-CONTROL**: Enables the O-DU to configure the power reduction for each tx-array-carrier. -- 2) **supported-max-power-level**: List of supported maximum output power levels per **tx-array** for energy saving. - - **index**: The leaf indicates the level of maximum output power control. If index = 0, it means this tx-array is in the normal mode. - - **array-max-power-reduction**: The leaf indicates the reduced upper power compared to the rated maximum power per tx-array for the index. For normal mode, this value shall be mapped to 0. - -## 20.6.3 Maximum output power control configuration - -The maximum output power is controlled by the O-RU Controller through configuration of the **max-power-level-index** parameter or **carrier-max-power-reduction**. The O-DU restricts the number of scheduled PRBs upper limit based on network load or predictive analysis, with implementation specifics excluded from this document. - -To control the maximum output power, the O-RU Controller shall configure the **max-power-control-method** value according to the methods exposed by the O-RU in **max-power-control-methods-supported**, **MAX-POWER-PER-TX-ARRAY-CONTROL** or **MAX-POWER-PER-TX-ARRAY-CARRIER-CONTROL**. - -- 1) If method **MAX-POWER-PER-TX-ARRAY-CONTROL** is selected: The O-DU may only configure the **max-power-level-index** if the related tx-array reports **supported-max-power-level**. In this mode, the O-RU controller should select and configure the leaf **max-power-level-index** per tx-array, then the O-RU calculates and applies the corresponding level with **array-max-power-reduction**. The O-RU controller shall also ensure that maximum power level that is scheduled to be transmitted at the tx-array is less than the configured maximum tx power. Refer to the CUS-Plane specification [2] clause 8.1.3.3 for the restrictions on input IQ power level. -- 2) If method **MAX-POWER-PER-TX-ARRAY-CARRIER-CONTROL** is selected: The O-DU may only configure the **carrier-max-power-reduction** if the related tx-array reports **supported-max-power-level**. In this mode, the O-RU controller should configure the power reduction via **carrier-max-power-reduction** per **tx-array-carrier**. Then the O-RU calculates and applies the corresponding **carrier-max-power-reduction** per related **tx-array-carrier**. The O-RU controller shall also ensure that maximum power that is scheduled to be transmitted at the **tx-array-carrier** is less than one scheduled for the configured maximum tx power. Refer to the CUS-Plane specification [2] clause 8.1.3.3 for the restrictions on input IQ power level. - -If any O-RU abnormality or traffic abnormality is detected, O-RU controller can transfer the O-RU from energy saving mode to normal mode through **set max-power-level-index to 0 per tx-array** or **set carrier-max-power-reduction to 0 per tx-array-carrier**, and the O-DU should lift scheduling constraints after maximum power level recovery is completed. - -If the O-DU chooses to retrieve the currently used power-level, the O-DU shall read the read-only **max-power-level-used** parameter. The O-RU shall set this parameter to indicate the currently used energy saving level per **tx-array**, where the default value should be normal mode. - -When the maximum power control procedure has been completed, a notification shall be sent by the O-RU with the current **max-power-level-used** to all subscribed O-RU controllers as detailed in the Figure 20.6.3-1. - -When the O-DU configures **array-max-power-reduction** or **carrier-max-power-reduction** to a new value, then the O-DU shall adhere to the following constraints: - -- 1) If the new value results in increased power reduction, then the O-DU shall reduce the power (e.g., by scheduling less PRBs) for the affected carriers before requesting the new configuration. -- 2) If the new value that results in decreased power reduction, then the O-DU shall not increase the power (e.g., by scheduling more PRBs) for the affected carriers before it received **max-power-level-used** notification. - -The O-RU may not guarantee service performance between reception of a request for configuration of **array-max-power-reduction/carrier-max-power-reduction** to a new value and sending of the **max-power-level-used** notification that signals implementation of the change. - -![Sequence diagram for Maximum power control showing NETCONF interaction between O-RU and O-RU Controller.](17b315c49985d42848e8d673a66dce7f_img.jpg) - -``` - -sequenceDiagram - participant RU as NETCONF Server/ -Notification Producer/ -(O-RU) - participant RUC as NETCONF Client/ -Notification Subscriber/ -(O-RU Controller) - - RUC->>RU: [1] - - - RU-->>RUC: [2] - Note left of RU: Power control completed. - RU->>RUC: [3] - - - -``` - -The diagram shows a sequence of three messages. First, the O-RU Controller (NETCONF Client) sends an RPC to the O-RU (NETCONF Server) to set power reduction parameters. Second, the O-RU responds with an containing . After the power control is completed internally at the O-RU, a third message is sent: a from the O-RU to the O-RU Controller containing the . - -Sequence diagram for Maximum power control showing NETCONF interaction between O-RU and O-RU Controller. - -Figure 20.6.3-1 – Maximum power control - -## 20.6.4 Interaction with M-Plane processing - -In the case of Shared O-RU, if different O-DUs configure **carrier-max-power-reduction** for carriers related to the same **tx-array**, then the values of **carrier-max-power-reduction** can be agreed via offline negotiation, which is outside the scope of the present document. - -## 21 Received power measurements for shared spectrum bands - -### 21.1 Introduction - -There exists some spectrum that is designated as shared spectrum. To improve the sharing experience, received power measurements can be beneficial in understanding the level to which the shared spectrum is being used. Citizens Broadband Radio Service (CBRS) is an example of such a shared spectrum allocation, corresponding to 150MHz of spectrum in the 3.5GHz band (3550 MHz to 3700 MHz) in the United States. CBRS band is lightly licensed and the use is expected to reduce the cost of data transmissions. The CBRS architecture introduces the Spectrum Access System (SAS) function that is responsible for authorisation and manages use of the shared spectrum [i.8]. To help inform the SAS of the wireless environment, the O-RU can optionally support measurements of shared spectrum bands. An O-RU supporting such optional capability shall include the o-ran-frequency-band-measurement model in its YANG library. This clause 21 applies to O-RUs that support this optional capability. - -NOTE: This clause 21 defines the use of NETCONF-based procedures between an O-RU and an O-RU controller for performing measurements of shared spectrum bands. Signalling between the O-RU Controller and the SAS are out of scope of the present document. - -### 21.2 Measurement Procedure - -An O-RU controller can use the **received-power-measurement-request** RPC to trigger the O-RU to start measurements, as illustrated in Figure 21.2-1. - -The O-RU can report its capabilities to the NETCONF client. These capabilities are defined in o-ran-frequency-band-measurement.yang module. The attributes included are: - -- **measurement-bands-supported:** The supported frequency range for which an O-RU can perform the received power measurement. -- **in-service-measurement:** Indicates whether O-RU can support measurements when tx-array carriers are active in measurement band. -- **in-service-measurement-only-carrier-freq:** Indicate an O-RU only support measurement on frequency range as carrier is configured on when **in-service-measurement** is TRUE. -- **supported-measurement-points:** Indicates which measurement point(s) are supported by the O-RU. Defined measurement points are NO\_ARRAY, ONE\_ARRAY and MULTIPLE\_ARRAYS. Depending on the reported measurement points, the O-RU supports measurements without an rx-array name provided (NO\_ARRAY), with a single rx-array name provided (ONE\_ARRAY) and/or with multiple rx-array names provided (MULTIPLE\_ARRAYS). If ONE\_ARRAY or MULTIPLE\_ARRAY is reported by the O-RU, then the O-RU controller shall configure the rx-array name(s) as the measurement point in the **rx-array** leaf-list in the **received-power-measurement-request** rpc. - -![Sequence diagram of CBRS measurement flow between NETCONF Server (O-RU) and NETCONF Client (O-RU Controller). The flow consists of three steps: [1] Request, [2] Reply, and [3] Notification.](c981496dcf94656533f6f8ed68816d76_img.jpg) - -``` - -sequenceDiagram - participant NETCONF Server (O-RU) - participant NETCONF Client (O-RU Controller) - Note right of NETCONF Client: [1] - NETCONF Client->>NETCONF Server: - - .. - - - Note left of NETCONF Server: [2] - NETCONF Server->>NETCONF Client: - - .. - - - Note left of NETCONF Client: [3] - NETCONF Server->>NETCONF Client: - .. - - -``` - -Sequence diagram of CBRS measurement flow between NETCONF Server (O-RU) and NETCONF Client (O-RU Controller). The flow consists of three steps: [1] Request, [2] Reply, and [3] Notification. - -Figure 21.2-8: CBRS measurement flow - -## 21.3 Measurement attributes - -Following received-power-measurement-request rpc is used to trigger the measurement and subsequent notification of the measurement results. - -- rpc: **received-power-measurement-request** - - input - - **measurement-bandwidth**: This is the measurement unit. - - **measurement-start-frequency**: This is the start frequency range requested for measurement. For band n48, the limited range is 3550...3700Mhz. O-RU can report the measurement of continuous spectrum or the limited discontinuous spectrum. When the O-RU does not have a spectrum grant from the CBRS system, received power shall be measured and reported over the entire CBRS band in segments that do not exceed 10 MHz per measurement report. When the O-RU has a spectrum grant from the CBRS system, received power shall be measured and reported over one or more frequency ranges that do not exceed 10 MHz per measurement report. - - **rx-array**: The measurement point for which the O-RU shall provide measurements. The supported values depend on the **supported-measurement-points** capability. If multiple rx-array names are provided, then the rx-arrays shall be allocated in the same sector and for each measurement (identified by **measurement-start-frequency**), only one value of **received-power** shall be reported. - - output - - **status**: whether O-RU accepted or rejected the measure request. - -- **error-message**: The detailed error message when the operation is failed. If the requested range is out of O-RU's Instantaneous BandWidth(IBW) then it can output status as FAILED with a detailed error-message. -- **wait-time**: Declare the expected time for report delivery in notification. -- **measurement-id**: Identify an RPC for one measurement. -- notification: **power-measurement-result** - - **status**: whether O-RU accepted or rejected the measure request. - - **error-message**: The detailed error message when the operation is failed. - - **measurement-id**: Identify an RPC for one measurement. - - **received-power-measurement**: This list indicates the List of RSSI measurements. - -If O-RU controller uses "rpc received-power-measurement-request" to request measurement report, then O-RU performs and reports received power measurements over the **requested-spectrum** band in segments of **measurement-bandwidth** per measurement report. O-RU sends RPC response where status= SUCCEED or FAILED. O-RU performs measurement and delivers result to O-RU controller. O-RU sends **error-message** when **status** = FAILED and with appropriate failure reason. - -For CBRS, O-RU performs the received power measurement in segments with 5 or 10MHz measurement bandwidth per measurement report. The range bounded by measurement-start-frequency as the lower bound and measurement-start-frequency+ measurement-bandwidth as the upper bound expresses the frequency range used in making the measurement. Measurement bandwidth is fixed during each measurement. The possible expression range of the measurement parameter for CBRS is -100 dBm... -25dBm. When the measurement result in O-RU is out of the range: - -- O-RU should report -100 dBm when result is lower than -100dBm. -- O-RU should report -25 dBm when result is higher than -25dBm. - -## Annex A (normative): Common alarm definition - -### A.1 Introduction - -This clause contains common alarms which may be supported. - -Alarms that are not applicable in given HW design or SW configuration shall not be reported. For example, alarms related to fan monitoring are applicable to HW variants with fans. - -In many cases fault detection method is HW specific. It is assumed that fault detection method is reliable to avoid undetected alarms and false alarms. It is also expected that the NETCONF Server is applying mechanisms to avoid unreasonably fast toggling of alarms' state, for example use time filtering. - -The field that are mandatory for alarm-notif notifications are: - -- fault-id; -- fault-source; -- fault-severity; -- is-cleared; and -- event-time. - -The common alarms table has following columns: - -NOTE 1: The table columns do not represent the entire set of alarm fields defined in the o-ran-fm.yang model. - -Fault id - Numerical identifier of fault type of the alarm. This ID shall be used in message (fault-id parameter). - -Fault Name - Name of the fault. It may be used in the **alarm-notif** notification. - -Meaning - Description of alarm, describes high level meaning of the alarm. This field is informative. - -Start condition - Defines conditions that O-RU shall follow for raising the alarm. If specific filtering time is needed, then it shall be defined in this column. - -Cancel condition - Defines conditions that O-RU shall follow for ceasing the alarm. If specific filtering time is needed, then it shall be defined in this column. - -NETCONF Server actions on fault detection - Defines actions of the NETCONF Server when fault has been detected. This field is informative. Word 'None' in this field means no action is expected. - -NETCONF Server actions on fault recovery - Defines actions of NETCONF Server after fault detection determines the fault is recovered. This field is informative. Word 'None' in this field means no action is expected. - -NETCONF Client recovery actions - Describes gNB level recovery actions of the NETCONF Client after alarm has been indicated by NETCONF Server. This field is informative only; actions taken by the NETCONF Client are not restricted nor defined in this document. NETCONF Client recovery action "Reset" refers to NETCONF Client forcing reset of O-RU. - -Source - Defines possible sources of the alarm (fault is localized to this source within O-RU). Alarm sources may directly reference a defined component or may use a predefined textual description. If the fault source can - -be represented by an object in the model, then the YANG instance-identifier should be set as the value. XML format can also be used. The following list provides examples of mapping between fault sources and XML encodings, describing the names of components that may be alarm sources: - -- **Module (hardware component is O-RAN-RADIO):** -- **Fan supervision:** -- **GNSS:** -- **External input:** -- **External output:** -- **ALD port:** -- **Port transceiver:** -- **Ethernet interface:** -- **Processing element:** -- **Low level tx link:** -- **Low level rx link:** -- **Tx array:** -- **Rx array:** -- **Tx array carrier:** -- **O-DU supervision:** -- **Connector (hardware component derived from "O-RU-CONNECTOR"):** -- **Component (hardware component):** - -The following list provides mapping between fault sources and predefined textual descriptions used to define the fault sources: - -- **Antenna line:** *array's name:array element*, where *array's name* follows either **Tx array** or **Rx array** name as defined above and *array element* is an ordinal number defining element within an array (see *k* in clause 12.5.3 Identification and Ordering of Array Elements in [2]). - -EXAMPLE 1: "tx-array-1:0" (alarm on the array element k=0 on the tx-array named "tx-array-1") - -EXAMPLE 2: "rx-array-2:15" (alarm on the array element k=15 on the rx-array named "rx-array-2") - -- **Tx array carrier per antenna line:** *array carrier's name/array's name:array element*, where array carrier's name follows **Tx array carrier** name as defined above, and array's *name* follows Tx array *name* as defined above and array *element* is an ordinal number defining element within an array (see k in clause 12.5.3 Identification and Ordering of Array Elements in [2]). - -EXAMPLE 1: "tx-array-carrier-1/tx-array-1:0" (alarm of tx-array-carrier named "tx-array-carrier-1" on the array element k=0 on tx-array named "tx-array-1" ) - -EXAMPLE 2: "tx-array-carrier-3/tx-array-2:15 " (alarm of tx-array-carrier named “tx-array-carrier-3” on the array element k=15 on tx-array named "tx-array-2" ) - -If an alarm is caused by an external device (fault localized external to the O-RU, e.g. caused by an Antenna Line Device), then fault source may not fit to any of the fault sources described above and additional text in an alarm notification is needed to clearly describe what may be a possible fault source. - -NOTE 2: Alarms, especially those defined in vendor specific range, may use other fault sources, which are not described above. - -Severity - Defines severity of the alarm as specified in ITU X.733 [30]. - -- Critical - sub-unit for which alarm has been generated is not working and cannot be used. -- Major - sub-unit for which alarm has been generated is degraded, it can be used but performance might be degraded. -- Minor - sub-unit for which alarm has been generated is still working. - -Alarm Type - Indicates the type of alarm, where the type of alarm is as specified in 3GPP TS 28.111 [82], Table 7.4.1-1, but where the YANG enumeration of **alarm-type** in o-ran-fm.yang YANG model differs from the YANG **eventType** typedef enumeration in \_3gpp-common-fm.yang YANG model. In text used in column Alarm Type in Table A.1-1: Common O-RU Alarms and in o-ran-fm.yang enumeration **alarm-type** ‘-’ are used while in 3GPP 28.111 Table 7.4.1 row **alarmType** allowed values ‘\_’ are used. For example, O-RAN **alarm-type** enumeration of "COMMUNICATIONS-ALARM" corresponds to a 3GPP **eventType** enumeration of "COMMUNICATIONS\_ALARM".. - -- The table of alarms in clause A includes alarm-type values for the common alarms. - -Table A.1-1: Common O-RU Alarms - -| Fault id | Fault Name | Meaning | Start condition | Cancel condition | NETCONF Server actions on fault detection | NETCONF Server actions on fault recovery | NETCONF Client recovery actions | Source | Severity | Alarm Type | -|----------|-------------------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------|------------------------------------------|---------------------------------|--------|------------------------------------------------------------------|---------------------| -| 1 | Unit temperature is high | Unit temperature is higher than expected. | Unit temperature exceeded HW implementation specific values. | Unit temperature is below HW implementation specific values. | SW implementation specific. | None. | None. | Module | Minor (e.g. above threshold 1) or Major (e.g. above threshold 2) | ENVIRONMENTAL-ALARM | -| 2 | Unit dangerously overheating | Unit temperature is dangerously high. | Unit temperature exceeded HW implementation specific value for reasonably long filtering time (e.g. 1 minute). | Unit temperature is below HW implementation specific value for reasonably long filtering time (e.g. 1 minute).
AND
Ambient temperature is below predefined HW implementation specific value | Unit deactivates all carriers to prevent HW damage. | None. | None. | Module | Critical | ENVIRONMENTAL-ALARM | -| 3 | Ambient temperature violation | Calculated ambient temperature value goes outside the allowed ambient temperature range. | Calculated ambient temperature goes outside the allowed HW specific ambient temperature range. | Calculated ambient temperature not any more outside the allowed HW specific ambient temperature range | SW implementation specific. | None. | None. | Module | Minor | ENVIRONMENTAL-ALARM | - - - -| Fault id | Name | Meaning | Start condition | Cancel condition | NETCONF Server actions on detection | NETCONF Server actions on cancel | NETCONF Client recovery actions | Source | Severity | Alarm Type | -|----------|-----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------|--------------------------------------------------------------------|---------------------------------|-----------------|-----------------------------------------------------------------|--------------------------| -| 4 | Temperature too low | During start-up: The temperature inside the unit is too low. Heating of unit is ongoing. Wait until the alarm is cancelled. During runtime: The temperature inside the module is too low. | Unit temperature is below HW implementation specific value. | Unit temperature is x Celsius above HW implementation specific value. Additionally: cancellation of critical alarm (reported during start-up) is mandatory within x minutes. | HW implementation specific (e.g. enable heating). (note 1) | HW implementation on specific (e.g. disable the heating). (note 2) | None. | Module | Critical during start-up
Minor during runtime | ENVIRONMENTAL-ALARM | -| 5 | Cooling fan broken | Fan(s) do not run. | HW implementation specific. | HW implementation specific. | None. | None. | None. | Fan supervision | Critical (if cooling is severely degraded)
Major (otherwise) | EQUIPMENT-ALARM | -| 6 | No fan detected | Unit cannot identify the used fan type or the fan is not installed at all. | HW implementation specific. | HW implementation specific. | SW implementation specific. | None. | None. | Fan supervision | Minor | EQUIPMENT-ALARM | -| 7 | Tuning failure | A filter has not been able to tune on an appropriate sub-band properly. | HW implementation specific. | HW implementation specific. | None. | None. | None. | Antenna line | Critical | EQUIPMENT-ALARM | -| 8 | Filter unit faulty | Major failure has been detected by the filter. | HW implementation specific. | HW implementation specific. | None. | None. | None. | Antenna line | Critical | EQUIPMENT-ALARM | -| 9 | Transmission quality deteriorated | The TX signal quality may be out of specification limits. | HW and SW implementation specific. | HW and SW implementation specific. | None. | None. | None. | Antenna line | Major | QUALITY-OF-SERVICE-ALARM | - -| Fault id | Name | Meaning | Start condition | Cancel condition | NETCONF Server actions on detection | NETCONF Server actions on cancel | NETCONF Client recovery actions | Source | Severity | Alarm Type | -|----------|-----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|-------------------------------------|----------------------------------|---------------------------------|------------------------|----------|------------------------| -| 10 | RF Module overvoltage protection faulty | Module's overvoltage protection is broken. | HW implementation specific. | None. | None. | None. | None. | Module | Minor | EQUIPMENT-ALARM | -| 11 | Configuring failed | Configuration failed because of a HW or SW fault. | SW or HW fault detected during configuration. | None. | None. | None. | Reset. | Module | Critical | PROCESSING-ERROR-ALARM | -| 12 | Critical file not found | Critical configuration file is missing. | Critical configuration file is detected missing. | None. | None. | None. | Reset. | Module | Critical | PROCESSING-ERROR-ALARM | -| 13 | File not found | Non-critical configuration file is missing. | Non-critical configuration file is detected missing. | None. | None. | None. | None. | Module | Major | PROCESSING-ERROR-ALARM | -| 14 | Configuration file corrupted | conflicting or corrupted configuration data. | conflicting or corrupted configuration data detected. | Unit detects that previously missing file is present. | None. | None. | None. | Module or antenna line | Major | PROCESSING-ERROR-ALARM | -| 15 | Unit out of order | The Unit is out of order because of a software or hardware fault. | HW and SW implementation specific. | HW and SW implementation specific. | None. | None. | Reset. | Module | Critical | EQUIPMENT-ALARM | -| 16 | Unit unidentified | The permanent memory in the module is corrupted and the module product code or serial number is missing, or the module product code is unknown. | Not able to read data from information storage or data is such that module identity or serial number is missing or module identity is unknown. | None. | None. | None. | None. | Module | Major | PROCESSING-ERROR-ALARM | -| 17 | No external sync source | The Unit lost lock to all incoming clocks. | HW implementation specific. | HW implementation specific. | None. | None. | Reset or none. | Module | Major | EQUIPMENT-ALARM | - -| Fault id | Name | Meaning | Start condition | Cancel condition | NETCONF Server actions on detection | NETCONF Server actions on cancel | NETCONF Client recovery actions | Source | Severity | Alarm Type | -|-------------|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------|--------------------------------------------------------------------|---------------------------------|--------------|----------|--------------------------| -| 18 | Synchronisation Error | Unit is out of synchronisation. | HW implementation specific (note 6). | HW implementation specific. | Unit shuts down all RF emission to prevent environment distortion and deactivates all carriers. | None. | Reset or none. | Module | Critical | EQUIPMENT-ALARM | -| 19 | TX out of order | TX path is not usable. | HW implementation specific. | HW implementation specific. | None. | None. | Reset or none. | Antenna line | Critical | EQUIPMENT-ALARM | -| 20 | RX out of order | RX path is not usable. | HW implementation specific. | None. | None. | None. | Reset or none. | Antenna line | Critical | EQUIPMENT-ALARM | -| 21 | Increased BER detected on the optical connection | Increased bit error rate has been detected on the optical link which results in sporadic errors in downlink baseband processing. | HW implementation specific (the detected BER on optical link is degrading RF operation). | HW implementation specific (the detected BER on optical link is not degrading RF operation). | Module Agent starts HW implementation specific recovery to keep the RF operation ongoing. | Module Agent stops HW implementation on specific recovery actions. | None. | Module | Major | QUALITY-OF-SERVICE-ALARM | -| 22 | Post-test failed | Power-on self-test failed at start-up. | HW and SW implementation specific. | None. | Unit reset x times for recovery. | None. | None. | Module | Critical | PROCESSING-ERROR-ALARM | -| 23 | FPGA SW update failed | The FPGA software update has failed. | FPGA SW checksum is not correct match after FPGA SW update is detected. | None. | None. | None. | None. | Module | Major | PROCESSING-ERROR-ALARM | -| 24 (note 3) | Unit blocked | Unit is administratively locked. | Parameter admin-state of the Module element is set to "locked". | Parameter admin-state of the Module Element is set to "unlocked" or "shutting-down" | Refer to clause 9.1.3 for description. | None. | None. | Module | Critical | EQUIPMENT-ALARM | - -| Fault id | Name | Meaning | Start condition | Cancel condition | NETCONF Server actions on detection | NETCONF Server actions on cancel | NETCONF Client recovery actions | Source | Severity | Alarm Type | -|----------|------------------------|--------------------------------------------------------------------------------------------------------------|----------------------------|------------------|-------------------------------------|----------------------------------|---------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------| -| 25 | Reset Requested | Unit detected a transient problem which significantly affects operation that requires a reset as a recovery. | HW implementation specific | None. | None. | None. | Reset. | Module | Critical | EQUIPMENT-ALARM | -| 26 | Power Supply Faulty | Input power to module has fault, unstable or broken. | HW implementation specific | None | None | None | Reset or None | Module | Minor, , Major or Critical | EQUIPMENT-ALARM | -| 27 | Power Amplifier faulty | One or more power amplifiers in module has fault, unstable or broken | HW implementation specific | None | None | None | Reset or None | Tx-array and/or antenna line | Major (Performance of Tx array and/or antenna line is degraded because of power amplifier issue )
Or
Critical (Tx array and/or antenna line is not working because of power amplifier issue ) | EQUIPMENT-ALARM | - -| Fault id | Name | Meaning | Start condition | Cancel condition | NETCONF Server actions on detection | NETCONF Server actions on cancel | NETCONF Client recovery actions | Source | Severity | Alarm Type | -|----------|--------------------------------------------|--------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------|-------------------------------------|----------------------------------|---------------------------------|---------------------------------------------------------------|-------------------------|----------------------| -| 28 | C/U-plane logical Connection faulty | One of logical C/U-plane connection has fault, unstable or broken. | One of C/U-plane processing elements detects the error of C/U-plane connection faulty, (when the O-RU's CU plane monitoring timer expires). | C/U Plane connection recovered, or the carrier related fault source deactivated/removed. | None | None | None or reset. | processing-element | Major | COMMUNICATIONS-ALARM | -| 29 | Transceiver Fault | Unit has detected a transceiver fault | HW and SW implementation specific. | None. | None | None. | None. | Module or port transceiver | Critical | EQUIPMENT-ALARM | -| 30 | Interface Fault | Unit has detected a fault with one of its interfaces | HW and SW implementation specific. | None. | Unit reset x times for recovery. | None. | None. | Module | Major or Critical | EQUIPMENT-ALARM | -| 31 | Unexpected C/U-plane message content fault | C/U-plane message content was faulty for undetermined reason. | C/U-plane detects unexpected message content. | Carrier that uses the fault source is disabled/removed | SW implementation specific | None | None | Specific to low-level-[tr]x-endpoint in the C/U-Plane message | Major, Minor or Warning | COMMUNICATIONS-ALARM | - -| Fault id | Name | Meaning | Start condition | Cancel condition | NETCONF Server actions on detection | NETCONF Server actions on cancel | NETCONF Client recovery actions | Source | Severity | Alarm Type | -|----------|-------------------------------------------|---------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------|------------------------------------------------------------------------------------|----------------------------------|------------------------------------------------------------------------------|--------|--------------------|------------------------| -| 32 | Triggering failure of antenna calibration | O-RU has previously sent a notification antenna-calibration-required and has not received a start-antenna-calibration RPC | Major - O-RU has not received an RPC trigger for start antenna calibration within 60 seconds after triggering the sending of the antenna-calibration-required notification
Critical - After O-RU specific number of repetitions based on O-RU implementation/
Failure of O-RU self-calibration | Arrival of RPC antenna calibration start/Success of O-RU self-calibration | Major-None,
Critical-Reset or None | None | Major -Send RPC antenna calibration start/self-calibration
Critical-Reset | Module | Major/
Critical | PROCESSING-ERROR-ALARM | -| 33 | Dying Gasp | O-RU is suffering from an unrecoverable condition such as power failure | Critical - O-RU is experiencing a dying gasp event | Re-starting of the O-RU, e.g. after power has been restored | HW implementation specific | None | None | Module | Critical | EQUIPMENT-ALARM | -| 34 | Clock source failure | Clock source has failed | O-RU detects clock source failure | HW implementation specific. | set the system clock to the current time recovered from available external sources | None | None | Module | Critical | EQUIPMENT-ALARM | -| 35 | Lost O-DU ID based Supervision | An O-RU has lost supervision from one O-DU (note 4). | Major – carriers associated with the O-DU are disabled. | Re-establishment of NETCONF supervision by O-DU (note 5). | Disable operation of carrier resources associated with O-DU | None | None | odu-id | Major | COMMUNICATIONS-ALARM | - -| Fault id | Name | Meaning | Start condition | Cancel condition | NETCONF Server actions on detection | NETCONF Server actions on cancel | NETCONF Client recovery actions | Source | Severity | Alarm Type | -|----------------|--------------------------------|-----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|-------------------------------------|----------------------------------|---------------------------------|-----------------------------------|--------------------------------------------------------------------------------------------------------------------------|--------------------------| -| 36 | Rx Signal quality deteriorated | The RX signal quality may be out of specification limits. | HW and SW implementation specific. | HW and SW implementation specific. | None. | None. | None. | Antenna line | Major | QUALITY-OF-SERVICE-ALARM | -| 37 | High IQ Power | The IQ Power level is higher than alarm threshold. | Major - O-RU detects IQ-Power value exceeding HW implementation specific limit.

Critical - O-RU detects IQ-Power value exceeding HW implementation specific limit which can cause HW a failure. | tx-array-carrier is deactivated or IQ-Power value falls below threshold. | implementation specific | None. | None. | Tx-array-carrier per antenna line | Major
Critical | COMMUNICATIONS-ALARM | -| 38
(note 7) | VSWR high | VSWR has exceeded threshold limits | VSWR is higher than expected | VSWR is below the specific value | Implementation specific | None | None | Antenna line or Connector | Minor (VSWR exceeds default or configured minor threshold)
Major (VSWR exceeds default or configured major threshold) | EQUIPMENT-ALARM | - -| Fault id | Name | Meaning | Start condition | Cancel condition | NETCONF Server actions on detection | NETCONF Server actions on cancel | NETCONF Client recovery actions | Source | Severity | Alarm Type | -|-------------|-----------------------------|----------------------------------------------------------------------|-----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|------------------------------|--------------------------|-----------------------------------------| -| 39 | Certificate About to Expire | The X.509 certificate used by O-RU for M plane is about to expire. | minor-alarm-advance-time days prior to expiry for Minor alarm. | When Major alarm is raised or when fault ID 40 is raised or when certificate is re-issued and certificate-lcm event generated. | Follow the procedure specified in clause 6.2.6.4.2 or 6.2.6.4.3 depending on the cert-lcm-policy configured. | After the certificate is re-issued, expect closure of existing NETCONF session from NETCONF controller. | NETCONF client shall follow the process defined in clause 6.2.6.4.3 if the configured cert-lcm-policy is REISSUE_ON_DEMAND. | Module | Minor | SECURITY-SERVICE-OR-MECHANISM-VIOLATION | -| | | | major-alarm-advance-time days prior to expiry for Major alarm. | When Critical alarm is raised or when fault ID 40 is raised or when certificate is re-issued and certificate-lcm event generated. | | | | | Major | | -| | | | critical-alarm-advance-time days prior to expiry for Critical alarm. | When fault ID 40 is raised or when certificate is re-issued and certificate-lcm event generated. | | | | | Critical | | -| 40 | Certificate Expired | The X.509 certificate used by O-RU for M plane has expired. | The X.509 certificate used by O-RU for M plane has expired. | When certificate is re-issued and certificate-lcm event generated. | None | None. | NETCONF client shall follow the process defined in clause 6.2.6. | Module | Critical | SECURITY-SERVICE-OR-MECHANISM-VIOLATION | -| 41 (note 8) | Generic Hardware Failure | Unit has detected a fault with one or more of its hardware (modules) | HW and SW implementation specific | HW and SW implementation specific. | HW and SW implementation specific. | Reset or None. | Reset or None. | Module or Component (note 9) | Critical, Major or Minor | EQUIPMENT-ALARM | - -| Fault id | Name | Meaning | Start condition | Cancel condition | NETCONF Server actions on detection | NETCONF Server actions on cancel | NETCONF Client recovery actions | Source | Severity | Alarm Type | -|----------|--------------------------------|-------------------------------------------------------------|-----------------------------------|-----------------------------------|-------------------------------------|----------------------------------|---------------------------------|--------|----------|-----------------------------------------| -| 42 | Certificate Re-issuance Failed | The O-RU failed to rekey the certificate | HW and SW Implementation specific | HW and SW Implementation specific | None | None | None | Module | Critical | SECURITY-SERVICE-OR-MECHANISM-VIOLATION | -| 43 | CRL connection failure | The O-RU can't connect to the CRL distribution point server | HW and SW Implementation specific | HW and SW Implementation specific | None | None | None | Module | Critical | SECURITY-SERVICE-OR-MECHANISM-VIOLATION | -| 44 | CRL past nextUpdate | The time has passed the nextUpdate | HW and SW Implementation specific | HW and SW Implementation Specific | None | None | None | Module | Critical | SECURITY-SERVICE-OR-MECHANISM-VIOLATION | - -NOTE 1: Actions taken shall not interfere with normal unit operation if such is commanded by NETCONF Client. -NOTE 2: Actions taken shall not interfere with normal unit operation if such is commanded by NETCONF Client. -NOTE 3: The **admin-state** is conditioned on the optional **hardware-state** feature. The O-RU can support fault id #24 (Unit blocked) only if it supports optional feature **hardware-state**. -NOTE 4: This alarm is only supported by O-RUs that implement the SHARED-ORU-MULTI-ODU feature. This alarm works per supervision session, meaning the O-RU is expected to report this alarm separately for each lost supervision session. -NOTE 5: Cancellation of this alarm is per each recovered supervision session. -NOTE 6: NETCONF Server shall not report fault id #18 during the initial synchronisation establishment which happens as part of normal start-up procedure as described in clause 6.1 step 8, i.e. O-RU implementations are designed to prevent false alarms during normal start-up. -NOTE 7: VSWR measurements are only valid when transmitted power exceeds a specific value which is either configured by O-RU Controller or predefined by O-RU. -NOTE 8: Specifically defined alarms should be used first, and this alarm should be applied only for undefined hardware failure cases. -NOTE 9: Source module shall be reported unless a more specific hardware component is reported in the component list. More detailed information may be included in the additional-information list. - ---- - -## Annex B (normative): Counters - -### B.1 Counter definition - -#### B.1.1 General - -**Table B.1.1-1: Counters definition** - -| measurement-group identifier | measurement-group | measurement-object | report-info | object-unit | Description | -|------------------------------|-------------------|-------------------------------------|----------------------------------------------------------|-------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 1 | transceiver-stats | RX_POWER | MAXIMUM
MINIMUM
FIRST
LATEST
FREQUENCY_TABLE | PORT_NUMBER | Type decimal64 including 4 fraction-digits for max, min, first and latest. A parameter date-and-time is reported for each additionally. Configurable parameters: function, bin-count, lower-bound, upper-bound are defined. For more detail see clauses B.2.1 and B.2.2. Type uint32 is used for frequency-bin-table. | -| | | RX_POWER_LANE_2 | | | | -| | | RX_POWER_LANE_3 | | | | -| | | RX_POWER_LANE_4 | | | | -| | | TX_POWER | | | | -| | | TX_POWER_LANE_2 | | | | -| | | TX_POWER_LANE_3 | | | | -| | | TX_POWER_LANE_4 | | | | -| | | TX_BIAS_COUNT | | | | -| | | TX_BIAS_COUNT_LANE_2 | | | | -| | | TX_BIAS_COUNT_LANE_3 | | | | -| | | TX_BIAS_COUNT_LANE_4 | | | | -| | | VOLTAGE | | | | -| | | TEMPERATURE | | | | -| | | LASER_TEMPERATURE | | | | -| | | TEC_CURRENT | | | | -| | | TUNED_DWDM_CHANNEL_FREQUENCY_ERROR | | | | -| | | TUNED_DWDM_CHANNEL_WAVELENGTH_ERROR | | | | -| 2 | rx-window-stats | RX_ON_TIME | COUNT | RU, TRANSPORT, or EAXC_ID (note 2, note 3) | Type yang: uint64 is used for the count. When object-unit is EAXC_ID, TRANSPORT is reported as additional parameter for EAXC_ID. | -| | | RX_EARLY | | | | -| | | RX_LATE | | | | -| | | RX_CORRUPT | | | | -| | | RX_DUPL | | | | -| | | RX_TOTAL | | | | -| | | RX_ON_TIME_C | | | | -| | | RX_EARLY_C | | | | -| | | RX_LATE_C | | | | -| | | RX_SEQID_ERR | | | | -| | | RX_SEQID_ERR_C | | | | -| | | RX_ERR_DROP | | | | -| 3 | tx-stats | TX_TOTAL | COUNT | RU, TRANSPORT, EAXC_ID or EAXC_ID_DATA DIRECTION (note 2, note 3) | Type yang: uint64 is used for the count. When object-unit is EAXC_ID, TRANSPORT is reported as additional parameter for EAXC_ID. | -| | | TX_TOTAL_C | | | | - - - -| measurement-group identifier | measurement-group | measurement-object | report-info | object-unit | Description | -|------------------------------|-------------------|--------------------|-----------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 4 | epe-statistics | POWER | MAXIMUM
MINIMUM
AVERAGE
FREQUENCY_TABLE | Hardware component type, e.g. O-RAN-RADIO, O-RU-POWER-AMPLIFIER, O-RU-FPGA, power-supply, fan, cpu | Type decimal64 including 4 fraction-digits for max, min, average .
Power measured using method specified in clause 5.1.1.19 of 3GPP TS 28.552 [57]
Unit of power: watts (W)
Temperature measured using method specified in clause 5.1.1.19 of 3GPP TS 28.552 [57]
Unit of temperature: Celsius
Voltage measured using method as specified in clause 5.1.1.19 of 3GPP TS 28.552 [57]
Unit of voltage: Volts
Current measured using method specified in clause 5.1.1.19 of 3GPP TS 28.552 [57]

Unit of current: Amperes
Type uint32 is used for frequency-bin-table. | -| | | TEMPERATURE | | | | -| | | VOLTAGE | | | | -| | | CURRENT | | | | -| 5 | symbol-rssi-stats | ALL-UL-SYMBOLS | MAXIMUM
MINIMUM
AVERAGE
FREQUENCY-TABLE | RX-ARRAY-CARRIER | Type decimal64 including 1 fraction-digit is used for max, min and avg.
Type uint32 is used for frequency-bin-table. | -| | | CONFIGURED-SYMBOLS | | | | -| 6 | shared-cell-stats | RX_UP_UL | COUNT | TRANSPORT (note 1, note 2) | Type yang: uint64 is used for the count. | -| | | RX_UP_UL_COMBINED | | | | -| 7 | tx-antenna-stats | VSWR | AVERAGE
STD_DEVIATION
MAXIMUM
MAXIMUM_AND_TIME
MINIMUM
MINIMUM_AND_TIME
FIRST
FIRST_AND_TIME
LATEST | ARRAY_ELEMENT or CONNECTOR_BAND | Type decimal64 including 4 fraction-digits for max, min, first, latest, avg and std-deviation. A parameter date-and-time is reported for max, min, first and latest additionally if MAXIMUM_AND_TIME, MINIMUM_AND_TIME, FIRST_AND_TIME or LATEST_AND_TIME | - -| | | | | | | -|--|--|--|--------------------------------------------|--|--------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | LATEST_AN
D_TIME
FREQUENC
Y_TABLE | | report-info was selected.
Configurable parameters: bin-count, lower-bound, upper-bound are defined.
Type uint32 is used for frequency-bin-table. | -|--|--|--|--------------------------------------------|--|--------------------------------------------------------------------------------------------------------------------------------------------------------| - - - -| measurement-group identifier | measurement-group | measurement-object | report-info | object-unit | Description | -|------------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------|-----------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------| -| 8 | tssi-stats | TSSI-IQ-POWER-LEVEL | MAXIMUM
MINIMUM
AVERAGE | CARRIER_AR
RAY_ELEME
NT | Type decimal64 including 2 fraction-digits is used for iq-tssi-level. | -| 9 | rssi-stats | RSSI | MAXIMUM
MINIMUM
AVERAGE | CARRIER_AR
RAY_ELEME
NT
| Type decimal64 including 1 fraction-digit is used for rssi. | -| 10 | tx-output-power-stats | TX_OUTPUT_POWER | MAXIMUM
MINIMUM
AVERAGE | TX-ARRAY-CARRIER,
TX-ARRAY-ELEMENT,
CONNECTOR
,
CARRIER-ARRAY-ELEMENT or
ARRAY-CARRIER-CONNECTOR | Type decimal64 including 2 fraction-digit is used for max, min and avg. | -| 11 | Ethernet-stats | IN-OCTETS
IN-UNICAST-PKTS
IN-BROADCAST-PKTS
IN-MULTICAST-PKTS
IN-DISCARDS
IN-ERRORS
IN-UNKNOWN-PROTOS
IN-CRC-ERRORS
IN-FEC-CORRECTABLE-BLOCKS
IN-FEC-UNCORRECTABLE-BLOCKS
IN-PCS-STATUS-CHANGE-COUNT
OUT-OCTETS
OUT-UNICAST-PKTS
OUT-BROADCAST-PKTS
OUT-MULTICAST-PKTS
OUT-DISCARDS
OUT-ERRORS
IN-FRAMES
IN-UNKNOWN-VLAN-FRAMES
OUT-FRAMES | COUNT | Ethernet interface name | Type yang: unit64 is used for the count. | - -NOTE 1: Clause 10.3.2 indicates how multiple **object-unit-ids** can be used for the **measurement-group** shared-cell-stats. - -NOTE 2: Object-unit TRANSPORT indicates the **name** of **transport-flow** in o-ran-processing-element YANG when used as unit for measurement result. - -NOTE 3: Object-unit EAXC-ID indicates that measurement result shall contain eAxC-id value and additional information **name** for its **transport-flow**. - -## B.1.2 Statistics calculation - -When configured by the NETCONF client, the O-RU captures the value of monitored parameters. Then the O-RU calculates $x = f(s)$ , where $f(s)$ is a function selected for specific statistics instance. The function $f(s)$ can be one of the following: - -$f(s) = s$ , if the **function** is set to RAW or function cannot be configured for the measurement-group - -$f(s) = \text{LOG}_{10}(s)$ , if the **function** is set to LOG\_10 - -Where $\text{LOG}_{10}(s)$ is logarithm with base 10. To avoid issues with infinity, the O-RU assumes that for $s < 10^{-128}$ value of $\text{LOG}_{10}(s)$ is -128. - -The value of $x = f(s)$ is applied to **first**, **latest**, **min** and **max** values; related timestamps are also updated; frequency table is updated as described in clause B.1.3. - -When local measurement interval, which is not same as **measurement-interval** of the **measurement-object**, passes the O-RU captures value of a monitored parameter ( $s$ ). Then the O-RU calculates $x = f(s)$ , where $f$ is a function selected for specific parameter. The local measurement interval is up to the O-RU implementation matter and typically around 10 sec - 60 sec at earliest. - -The value of $x = f(s)$ is applied to latest value; related timestamp is updated. - -The O-RU updates statistics: - -- If $x < \text{min value}$ then $x$ is applied to $\text{min value}$ and related timestamp is updated. -- If $x > \text{max value}$ then $x$ is applied to $\text{max value}$ and related timestamp is updated. -- Value of $x$ is used to update frequency table as described in clause B.1.3 below. - -After updates O-RU waits another interval to elapse. - -## B.1.3 Frequency table generation - -Let $n = \text{bin-count}$ , $a = \text{lower-bound}$ , $b = \text{upper-bound}$ , $x = f(s)$ where $s$ is value of monitored parameter and $f$ is a function selected for statistics (selected via parameter **function** if it can be configured for a measurement-group and $f(s) = s$ otherwise, see also clause B.1.2). - -- If $n = 0$ then frequency table is empty and is not updated. -- If $n > 0$ there are $n$ bins: $h_k$ where $k = 0 \dots n-1$ . Initial value of each bin is zero ( $h_k = 0$ for $k = 0 \dots n-1$ ). -- If $x < a$ then bin $h_0$ is incremented. -- If $b \leq x$ and $n > 1$ then bin $h_{n-1}$ is incremented. -- If $a \leq x$ and $x < b$ and $n > 2$ then bin $h_k$ is incremented for $k$ such that - - $k-1 \leq (n-2) * (x-a) / (b-a) < k$ . - -where the value of a bin should saturate at maximum without overflowing (the value is not incremented above $2^{32}-1$ ). - -Equivalently: - -For $k = 0$ , $h_k$ is a number of values $x$ such that $x < a$ . - -For $k = 1 \dots n-2$ , $h_k$ is a number of values $x$ such that - -$$a + (b-a) * (k-1) / (n-2) \leq x < a + (b-a) * (k) / (n-2).$$ - -For $k = n-1$ , $h_k$ is a number of values $x$ such that $b \leq x$ . - -EXAMPLE: **function** = LOG10, **bin-count** = 14, **lower-bound** = -12, **upper-bound** = 0 - -- parameter value $s = 0$ , $x = f(0) = -128$ , $-128 < -12 = a$ - - $h_0$ is incremented -- parameter value $s = 1e-12$ , -- $x = f(1e-12) = -12$ , $(14 - 2) * (-12 - (-12)) / (0 - (-12)) = 12 * 0 / 12 < 1$ - - $h_1$ is incremented -- parameter value $s = 9.99e^{-12}$ , -- $x = f(9.99e^{-12}) = -11,0004$ , $(14 - 2) * (-11,0004 - (-12)) / (0 - (-12)) = 12 * 0,9996 / 12 < 1$ - - $h_1$ is incremented -- parameter value $s = 1e^{-1}$ , -- $x = f(1e^{-1}) = -1$ , $(14 - 2) * (-1 - (-12)) / (0 - (-12)) = 12 * 11 / 12 < 12$ - - $h_{12}$ is incremented -- parameter value $s = 1$ , $x = f(1) = 0$ , $0 \geq 0 = b$ - - $h_{13}$ is incremented - -## B.2 Transceiver statistics - -### B.2.1 Transceiver measurements - -The transceiver-measurement includes the performance measurement of transceivers as shown in Table B.2.1-1. - -**Table B.2.1-1: Transceiver Measurements** - -| measurement-object | Description | -|-------------------------------------|-----------------------------------------------------------------------------------------| -| RX_POWER | Measured Rx input power in mW for SFP or lane 1 of QSFP. | -| RX_POWER_LANE_2 | Measured Rx input power in mW for lane 2 of QSFP. | -| RX_POWER_LANE_3 | Measured Rx input power in mW for lane 3 of QSFP. | -| RX_POWER_LANE_4 | Measured Rx input power in mW for lane 4 of QSFP. | -| TX_POWER | Measured Tx input power in mW for SFP or lane 1 of QSFP. | -| TX_POWER_LANE_2 | Measured Tx input power in mW for lane 2 of QSFP. | -| TX_POWER_LANE_3 | Measured Tx input power in mW for lane 3 of QSFP. | -| TX_POWER_LANE_4 | Measured Tx input power in mW for lane 4 of QSFP. | -| TX_BIAS_COUNT | Internally measured Tx Bias Current in mA for SFP or lane 1 of QSFP. | -| TX_BIAS_COUNT_LANE_2 | Internally measured Tx Bias Current in mA for lane 2 of QSFP. | -| TX_BIAS_COUNT_LANE_3 | Internally measured Tx Bias Current in mA for lane 3 of QSFP. | -| TX_BIAS_COUNT_LANE_4 | Internally measured Tx Bias Current in mA for lane 4 of QSFP. | -| VOLTAGE | Internally measured transceiver supply voltage in mV. | -| TEMPERATURE | Internally measured optional module temperature in degrees Celsius. | -| LASER_TEMPERATURE | Internally measured optional laser temperature in degrees Celsius. | -| TEC_CURRENT | Internally measured transceiver module TEC current in mA. | -| TUNED_DWDM_CHANNEL_FREQUENCY_ERROR | Internally measured transceiver frequency error in 0.1 GHz, defined in SFF-8690 [98]. | -| TUNED_DWDM_CHANNEL_WAVELENGTH_ERROR | Internally measured transceiver wavelength error in 0.005 nm, defined in SFF-8690 [98]. | - -## B.2.2 Statistics calculation - -See clause B.1.2. - -## B.2.3 Frequency table generation - -See clause B.1.3. - -## B.3 Rx window statistics - -### B.3.1 Rx window measurement - -The rx-window-measurement includes the performance measurement for the reception window according to Table B.3-1. Details of the Rx window measurements are defined in Table 9.1-1 of O-RAN CUS plane specification [2]. - -**Table B.3-1: Rx Window Measurement** - -| measurement-object | Description | -|--------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------| -| RX_ON_TIME | The number of data packets received on time (applies to user data reception window) within the rx-window-measurement-interval | -| RX_EARLY | The number of data packets received too early (applies to user data reception window) within the rx-window-measurement-interval | -| RX_LATE | The number of data packets received too late (applies to user data reception window) within the rx-window-measurement-interval | -| RX_CORRUPT | The number of data and control packets, which is corrupt or whose header is incorrect, received within the rx-window-measurement-interval | -| RX_DUPL | This counter is deprecated | -| RX_TOTAL | The total number of received data and control packets, within the rx-window-measurement-interval | -| RX_ON_TIME_C | The number of control packets, received on time within the rx-window-measurement-interval | -| RX_EARLY_C | The number of control packets, received before the start of reception window within the rx-window-measurement-interval | -| RX_LATE_C | The number of control packets, received after the end of reception window within the rx-window-measurement-interval | -| RX_SEQID_ERR | The number of data packets, received with an erroneous sequence ID within the rx-window-measurement-interval | -| RX_SEQID_ERR_C | The number of control packets, received with an erroneous sequence ID within the rx-window-measurement-interval | -| RX_ERR_DROP | The total number of inbound messages which are discarded by the receiving O-RAN entity for any reason within the rx-window-measurement-interval | - -## B.4 Tx statistics - -The tx-measurements include the measurement according to Table B.4-1. Details of the Tx statistics measurements are defined in Table 9.1-1 of O-RAN CUS plane specification [2]. - -**Table B.4-1: Tx Measurement** - -| measurement-object | Description | -|--------------------|----------------------------------------------------------------------------------------------------------| -| TX_TOTAL | The number of outbound packets (data and control), transmitted within the tx-measurement-interval | -| TX_TOTAL_C | The number of outbound control packets, transmitted within the tx-measurement-interval . | - -## B.5 Energy, power and environmental statistics - -### B.5.1 Statistics calculation - -The epe-statistics include the performance measurement for energy, power and environmental parameters as shown in Table B.5-1. An O-RU shall report its supported measurement objects per hardware component class. - -**Table B.5-1: Energy, Power and Environmental Measurements** - -| measurement-object | Description | -|--------------------|-------------------------------------------------------------------| -| POWER | Value of measured power consumed by identified hardware component | -| TEMPERATURE | Value of measured temperature of identified hardware component | -| VOLTAGE | Value of measured voltage of identified hardware component | -| CURRENT | Value of measured current of identified hardware component | - -## B.5.2 Frequency Table Generation - -Same as clause B.1.3. - -# B.6 Symbol RSSI statistics - -## B.6.1 Statistics calculation - -The symbol-rssi-stats is the time domain RSSI per symbol, the reference point for the TD-RSSI shall be the antenna connector of the O-RU. The value of Received Signal Strength Indicator(RSSI) per rx-array-carrier per configured OFDM symbol is measured. The RSSI shall be calculated as the linear average of the total received power observed in the configured OFDM symbol in the measurement bandwidth from all sources including co-channel serving and non-serving cells, adjacent channel interference, thermal noise, etc. over the total number of array elements of the array. The unit of the reported RSSI is dBm. - -If analogue or hybrid beamforming is enabled, the beamId used for RSSI measurement is: - -- When there is allocation of a beamId in this symbol, O-RU use that beamId for RSSI measurement. -- When there is no allocation of a beamId in this symbol, it is up to O-RU implementation, for example, the O-RU can choose to use a common beamId or use a previous allocated beamId. - -**Table B.6.1-1: Symbol RSSI Measurements** - -| measurement-object | Description | -|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| ALL-UL-SYMBOLS | Measure and report symbol-rssi separately for all UL symbols in every configured number of slots (as defined by 'period' in 'symbol-rssi-measurement-objects'. And the UL symbols are decided by 'configurable-tdd-pattern', 'static-srs-configuration', 'static-prach-configuration', and 'dataDirection' in the C-plane messages. This option is recommended for static TDD case. If this option is used in dynamic TDD case, then O-RU measures only the allocated UL symbols because O-RU may not know 'candidate UL symbols' which are not allocated. | -| CONFIGURED-SYMBOLS | Measure and report symbol-rssi separately for all configured symbols as defined by the leaf-list 'symbol-index'. This can be used for non-dynamic TDD as well as dynamic TDD cases, the O-RU should measure all configured symbols, irrespective of whether the UL symbol is allocated or not. If a c-plane message indicates a symbol within the 'symbol-index' list to be a DL symbol, O-RU shall not measure rssi on this symbol. | - -## B.6.2 Frequency Table Generation - -Same as clause B.1.3. - -## B.7 Shared cell statistics - -The shared cell measurements include the measurement according to Table B.7-1. - -**Table B.7-1: Shared-cell Measurement** - -| measurement-object | Description | -|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| -| RX_UP_UL | The number of received user plane packet in UL data direction corresponding to shared-cell-combine-entities within the shared-cell-measurement-interval | -| RX_UP_UL_COMBINED | The number of user plane packet in UL data direction which are processed by combine functional block within the shared-cell-measurement-interval | - -## B.8 Tx antenna statistics - -### B.8.1 Introduction - -The tx-measurements include the measurement according to Table B.8-1. - -**Table B.8-1: Tx Measurement** - -| measurement-object | Description | -|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| VSWR | The estimated value of VSWR (Voltage Standing Wave Ratio) for tx-array element, or connector and band. In case the value cannot be provided, the value of 0 is used.
VSWR related measurements and counters are useful for monitoring and troubleshooting of radios with external antennas. | - -### B.8.2 Statistics calculation - -Statistics are calculated as defined in clause B.1.2, with the exception that the only permitted function is $f(s) = s$ and parameter **function** is not used. - -### B.8.3 Frequency Table Generation - -Frequency table is generated as defined in clause B.1.3, with the exception that the only permitted function is $f(s) = s$ and parameter **function** is not used. - -## B.9 TSSI statistics - -### B.9.1 Statistics calculation - -The **tssi-stats** is transmit signal power as digital IQ level from baseband per **tx-array-carrier** on the specific **tx-array-element** in tx-array. When digital beamforming is used, TSSI shall indicate the signal power in digital domain after digital beamforming. - -The average TSSI-IQ-POWER-LEVEL shall be calculated as averaged value with the data (N samples of the DL symbols) in specific time duration. The unit of the **tssi-stats** is **dBFS**. - -**Table B.9.1-1: Tx TSSI Measurements** - -| measurement-object | Description | -|---------------------|----------------------------------------------------------------------------------------------------------------------| -| TSSI-IQ-POWER-LEVEL | Measured digital IQ power level for a specific Tx array carrier on the specific tx-array-element in tx-array. | - -## B.10 RSSI statistics - -### B.10.1 Statistics calculation - -The **rssi-stats** is the time domain RSSI per **rx-array-carrier** on the specific **rx-array-element** in **rx-array**. - -When digital beamforming is used, RSSI shall indicate the signal power in digital domain before digital beamforming. Based on the O-RU measured IQ power, the RSSI power is provided as dBm. - -NOTE: The present document does not define RSSI measurements when the O-RU supports analogue beamforming. - -**Table B.10.1-1: Rx RSSI Measurements** - -| measurement-object | Description | -|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------| -| RSSI | Measured RSSI (Received Signal Strength Indication) for each Rx array carrier on the specific array element in decibel-milliwatts (dBm) | - -## B.11 Tx output power statistics - -### B.11.1 Statistics calculation - -**TX\_OUTPUT\_POWER** is measured or estimated as defined in Table B.11.1-2 for different Object Unit. - -The unit of the reported Tx output power is dBm - -**Table B.11.1-1: Tx output power Measurements** - -| measurement-object | Description | -|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| -| TX_OUTPUT_POWER | Measured or estimated value of conducted transmission power for different Tx output power Object Units (as defined in Table B.11.1-2) in dBm. | - -**Table B.11.1-2: Tx output power Object Units** - -| Object unit | Description | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------| -| TX-ARRAY-CARRIER
(note 2) | The estimated tx output power per tx-array-carrier. | -| TX-ARRAY-ELEMENT | The tx output power per tx-array element. | -| CARRIER-ARRAY-ELEMENT
(note 2) | The estimated tx output power per tx array element per tx-array-carrier. | -| CONNECTOR
(note 1) | The tx output power per connector. | -| ARRAY-CARRIER-CONNECTOR
(note 1, note 2) | The estimated tx output power per tx-array-carrier per connector. | -| NOTE 1. Tx output power of connector is only applicable with O-RUs that report connector and using external antenna
NOTE 2. The tx output power per measurement object unit is estimated, may be based on power per tx array element or connector. If multiple tx-array-carriers are configured to the tx-array- element or connector, then the tx output power per measurement object unit may be derived, may be based on the gain of the tx-array-carrier configured via M-plane and tx input IQ power level of each tx-array-carrier on the tx array element or corresponding connector. | | - -## B.12 Ethernet statistics - -### B.12.1 Statistics calculation - -The ethernet-measurement includes the performance measurement of ethernet interface monitoring as shown in Table B.12.1-1. - -**Table B.12.1-1: Ethernet Monitoring Measurements** - -| measurement-object | Description | -|-----------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| IN-OCTETS | The total number of octets received on the interface, including framing characters. | -| IN-UNICAST-PKTS | The number of packets, delivered by this sub-layer to a higher (sub-)layer, that were not addressed to a multicast or broadcast address at this sub-layer. | -| IN-BROADCAST-PKTS | The number of packets, delivered by this sub-layer to a higher (sub-)layer, that were addressed to a broadcast address at this sub-layer. | -| IN-MULTICAST-PKTS | The number of packets, delivered by this sub-layer to a higher (sub-)layer, that were addressed to a multicast address at this sub-layer. For a MAC-layer protocol, this includes both Group and Functional addresses. | -| IN-DISCARDS | The number of inbound packets that were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. | -| IN-ERRORS | The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol. | -| IN-UNKNOWN-PROTOS | The number of packets received via the interface that were discarded because of an unknown or unsupported protocol. | -| IN-CRC-ERRORS | The number of received frames with CRC errors. | -| IN-FEC-CORRECTABLE-BLOCKS | Number of received erroneous blocks which were corrected with application of Forward Error Correction. | -| IN-FEC-UNCORRECTABLE-BLOCKS | Number of received erroneous blocks which could not be corrected with application of Forward Error Correction. | -| IN-PCS-STATUS-CHANGE-COUNT | Number of times PCS (Physical Coding Layer) of the receiver lost its operational state. Operational state of PCS is indicated by PCS_status as defined in clause 49 in [88]. | -| OUT-OCTETS | The total number of octets transmitted out of the interface, including framing characters. | -| OUT-UNICAST-PKTS | The total number of packets that higher-level protocols requested be transmitted and that were not addressed to a multicast or broadcast address at this sub-layer, including those that were discarded or not sent. | -| OUT-BROADCAST-PKTS | The total number of packets that higher-level protocols requested be transmitted and that were addressed to a broadcast address at this sub-layer, including those that were discarded or not sent. | -| OUT-MULTICAST-PKTS | The total number of packets that higher-level protocols requested be transmitted and that were addressed to a multicast address at this sub-layer, including those that were discarded or not sent. For a MAC-layer protocol, this includes both Group and Functional addresses. | -| OUT-DISCARDS | The number of outbound packets that were chosen to be discarded even though no errors had been detected to prevent their being transmitted. One possible reason for discarding such a packet could be to free up buffer space. | -| OUT-ERRORS | The number of outbound packets that could not be transmitted because of errors. | -| IN-FRAMES | The number of frames that are successfully received (receiveOK). This does not include frames received with frame-too-long, FCS, length or alignment errors, or frames lost due to internal MAC sublayer error. | -| IN-UNKNOWN-VLAN-FRAMES | The number of received VLAN-tagged Ethernet frames with VLAN ID not matching with the VLAN ID of any VLAN interface. | -| OUT-FRAMES | The number of frames that are successfully transmitted (transmitOK). | - -## Annex C (informative): Optional multi-vendor functionality - -### C.1 Optional multi-vendor namespace - -Some of the YANG models are optional for the O-RU to support. In this version of the management plane specification, the following YANG models are optional to support. If an O-RU/NETCONF server does not return the namespace associated with an optional YANG model, the NETCONF client can infer that the O-RU does not support the optional capability associated with the model. - -NOTE: Tables C.1-1 and C.1-2 do not apply for factory default software. - -**Table C.1-1: Optional O-RAN Namespace** - -| No | Optional Functionality | Reference | Namespace | -|----|-------------------------------------------------------------|----------------|-------------------------------------------------------------| -| 1 | Antenna Line Device | Clause 14.4 | "urn:o-ran:ald-port:x.y"
"urn:o-ran:ald: x.y" | -| 2 | External IO Port | Clause 14.5 | "urn:o-ran:external-io:x.y" | -| 3 | eCPRI delay measurement | Clause 7.7 | "urn:o-ran:message5:x.y" | -| 4 | UDP Echo functionality for IP based transport verification | Clause 7.6 | "urn:o-ran:udpecho:x.y" | -| 5 | Beamforming | Clause 15.4 | "urn:o-ran:beamforming:x.y" | -| 6 | FAN | - | "urn:o-ran:fan:x.y" | -| 7 | LAA | Clause 16 | "urn:o-ran:laa:x.y"
"urn:o-ran:laa-operations:x.y" | -| 8 | Antenna calibration | Clause 15.5 | "urn:o-ran:antcal: x.y" | -| 9 | Shared cell (common to FHM and Cascade modes) | Clause 17 | "urn:o-ran:shared-cell:x.y"
"urn:o-ran:ethernet-fwd:x.y" | -| 10 | Configured subscription transported using VES common header | Clause 18 | "urn:o-ran:ves-sn:1.0" | -| 11 | Certificates to name mapping | Clause 6.4.3.2 | "urn:o-ran:certificates:1.0" | -| 12 | Received power measurements for shared spectrum bands | Clause 21 | "urn:o-ran:frequency-band-measurement:1.0" | - -**Table C.1-2: Optional Non-O-RAN Namespace** - -| No | Optional Functionality | Reference | Namespace | -|----|----------------------------------------------------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 1 | Notification of Updates to Configuration Datastore | Clause 9.4 | "urn:ietf:params:xml:ns:yang:ietf-netconf-notifications" | -| 2 | Subscribed-Notifications | Clause 9.1.7.3 and Clause 18 | "urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications" | -| 3 | Certificates to name mapping | Clause 6.4.3.2 | " urn:ietf:params:xml:ns:yang:ietf-x509-cert-to-name" | -| 4 | IEEE 802.1X Port based Access Control | Clause 7.12 | "urn:ieee:std:802.1X:yang:ieee802-dot1x"
"urn:ieee:std:802.1Q:yang:ieee802-types"
" urn:ietf:params:xml:ns:yang:iana-crypt-hash"
" urn:ietf:params:xml:ns:yang:ietf-system"
"urn:ieee:std:802.1X:yang:ieee802-dot1x-types" | -| 5 | Trust store | Clause 6.2 | "urn:ietf:params:xml:ns:yang:ietf-truststore" | -| 6 | Continuity Check Message | Clause 7.6 | "urn:ieee:std:802.1Q:yang:ieee802-dot1q-cfm" | -| 7 | O-RU supports configuration of IEEE 802.1X EAPOL destination address | Clause 7.12.1 | "urn:ieee:std:802.1X:yang:ieee802-dot1x-eapol" | - -Whereas the Tables C.1-1 and C.1-2 describe those optional YANG modules associated with optional features, there are also scenarios where support of an optional feature means that previously defined mandatory YANG models become optional. Table C.1-3 describes those optional features that when supported result in YANG models becoming optional. - -**Table C.1-3: Not mandatory O-RAN Namespace for FHM.** - -| No | Optional Functionality | Reference | Namespace | -|----|------------------------|---------------|-----------------------------------------------------------| -| 1 | FHM in shared cell | Clause 17.6.1 | "urn:o-ran:module-cap:x.y"
"urn:o-ran:uplane-conf:x.y" | - -## C.2 Optional YANG features - -Some of the O-RAN defined YANG models define optional feature support using the ability to tag a portion of the model with a feature name. These portions of the model are only valid on O-RUs that indicate they support the specific YANG feature in their YANG library. The definition of the portion of the model tagged with a feature name can include definitions which allow an O-RU Controller to control when a particular O-RU capability associated with a feature tag is activated and/or deactivated. The optional capabilities identified using YANG feature tag names defined in the O-RAN defined YANG models are shown in Table C.2-1 below. - -**Table C.2-1: Optional O-RAN WG4 defined feature support** - -| No | Namespace | YANG Feature Name Tag | Description | Optional Feature Control | -|----|-------------------------------------|-------------------------------------------------|------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 1 | "urn:o-ran:ald-port:x.y" | OVERCURRENT-SUPPORTED | ALD overcurrent reporting | Subscription to over-current notifications | -| 2 | "urn:o-ran:antcal:1.0" | O-RU-COORDINATED-ANT-CAL | O-RU needs user traffic to be co-ordinated from O-DU for antenna calibration | /antenna-calibration/self-calibration-policy/coordinated-calibration-allowed | -| 3 | | O-RU-COORDINATED-ANT-CAL-MULTIPLE-TIME-RESOURCE | Calibration with multiple timing resource sets | /antenna-calibration/self-calibration-policy/coordinated-calibration-multiple-time-resources-allowed | -| 4 | "urn:o-ran:beamforming:x.y" | MODIFY-BF-CONFIG | Dynamic Beamforming Configuration | activate-beamforming-config-by-capability-group remote procedure calls | -| 5 | | BEAM-TILT | Tilting pre-defined beams | modify-predefined-beam-tilt-offset remote procedure call | -| 6 | "urn:o-ran:compression-factors:x.y" | CONFIGURABLE-FS-OFFSET | Configurable FS offset | /user-plane-configuration /low-level-tx-endpoints /compression/fs-offset and/or /user-plane-configuration /low-level-tx-endpoints /compression/dynamic-compression-configuration/fs-offset and/or /user-plane-configuration /low-level-rx-endpoints /compression/fs-offset and/or /user-plane-configuration /low-level-rx-endpoints /compression/dynamic-compression-configuration/fs-offset | -| 7 | "urn:o-ran:delay:x.y" | ADAPTIVE-RU-PROFILE | Adaptive O-RU delay profile | /delay-management/adaptive-delay-configuration | -| 8 | " urn:o-ran:fm:1.0" | HISTORICAL-ALARM-LIST | Historical Alarms List | M-Plane activation not applicable | -| 9 | "urn:o-ran:hardware:x.y" | ENERGYSAVING | O-RU Energy saving | /hardware/component/energy-saving-enabled | -| 10 | "urn:o-ran:interfaces:x.y" | ALIASMAC-BASED-CU-PLANE | Alias MAC address based C/U transport | /processing-elements/ru-elements/transport-flow/aliasmac | -| 11 | | UDPIP-BASED-CU-PLANE | UDP/IP based C/U Transport | /processing-elements/ru-elements/transport-flow/udpip-flow | -| 12 | "urn:o-ran:module-cap:x.y" | CONFIGURABLE-TDD-PATTERN-SUPPORTED | Configurable TDD pattern | /user-plane-configuration/tx-array-carriers/configurable-tdd-pattern and/or /user-plane-configuration/rx-array-carriers/configurable-tdd-pattern | - -| | | | | | -|----|----------------------------------------|--------------------------------------------|----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 13 | | DSS_LTE_NR | Dynamic Spectrum Sharing | /user-plane-configuration/tx-array-carriers/type and/or /user-plane-configuration/rx-array-carriers/type | -| 14 | | EAXC-ID-GROUP-SUPPORTED | EAXC-ID Grouping | /user-plane-configuration/eaxc-id-group-configuration | -| 15 | | LAA | LAA Support | /user-plane-configuration/tx-array-carriers/laa-carrier-configuration | -| 16 | | TRANSPORT-FRAGMENTATION | Transport Fragmentation | M-Plane activation not applicable | -| 17 | | PRACH-STATIC-CONFIGURATION-SUPPORTED | Static configuration of PRACH pattern | /user-plane-configuration/static-prach-configurations | -| 18 | | SRS-STATIC-CONFIGURATION-SUPPORTED | Static configuration of SRS pattern | /user-plane-configuration/static-srs-configurations | -| 19 | "urn:o-ran:performance-management:x.y" | GRANULARITY-EAXC-ID-MEASUREMENT (note 1) | EAXC_ID in rx-window-measurement | /performance-measurement-objects/rx-window-measurement-objects/object-unit | -| 20 | | GRANULARITY-TRANSPORT-MEASUREMENT (note 1) | TRANSPORT in rx-window-measurement | /performance-measurement-objects/rx-window-measurement-objects/object-unit | -| 21 | "urn:o-ran:processing-element:x.y" | SHARED_CELL | Shared cell support | /ru-elements/transport-flow/north-eth-flow and/or /ru-elements/transport-flow/south-eth-flow | -| 22 | "urn:o-ran:shared-cell:x.y" | FHM | FHM support, no capability of radio transmission and reception | /shared-cell/shared-cell-config/shared-cell-copy-combine-mode/shared-cell-copy-entities/shared-cell-copy-uplane-config and /shared-cell/shared-cell-config/shared-cell-copy-combine-mode/shared-cell-copy-entities/shared-cell-combine-uplane-config | -| 23 | | SELECTIVE-BEAM-ID | FHM supports the selective combining function by using beamId | /shared-cell/shared-cell-config/shared-cell-copy-entities-selective-beam-id and /shared-cell/shared-cell-config/shared-cell-combine-entities-for-selective-beam-id | -| 24 | "urn:o-ran:sync:x.y" | ANTI-JAM | GNSS Anti Jamming | /sync/gnss-config/anti-jam-enable | -| 25 | | GNSS | GNSS Support | Not applicable | -| 26 | "urn:o-ran:uplane-conf:x.y" | EAXC-GAIN-CORRECTION | eAxC specific gain correction | /user-plane-configuration/low-level-rx-endpoints/eaxc-gain-correction | -| 27 | | TX-REFERENCE-LEVEL | TX gain reference level control | /user-plane-configuration/tx-array-carriers/reference-level | - -| | | | | | -|----|-------------------------|--------------------------------|------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 28 | "urn:o-ran:wg4feat:1.0" | BEAM-UPDATE-CONTENTION-CONTROL | O-RU requirements for beam weight update for a given beamId, to avoid beam update contentions. | /user-plane-configuration /low-level-tx-endpoints/eexc-gain-correction/beam-update-contention-control-enabled and /user-plane-configuration /low-level-rx-endpoints/eexc-gain-correction/beam-update-contention-control-enabled | -|----|-------------------------|--------------------------------|------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| - -| | | | | -|----|-----------------------------------------|------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 29 | CHANNEL-INFORMATION-COMPRESSION | Compression for channel information in Section Type 6 (indicate at least static compression is supported) | /user-plane-configuration /low-level-tx-endpoints/channel-information-compressions | -| 30 | CHANNEL-INFORMATION-PRB-GROUP | Receiving and processing channel information with PRB group size greater than one | /user-plane-configuration /low-level-tx-endpoints/channel-information-prb-group-configuration | -| 31 | CPLANE-MESSAGE-PROCESSING-LIMITS | C-Plane Message Limits | /user-plane-configuration/low-level-tx-endpoints/cplane-message-processing-limits-enabled and /user-plane-configuration /low-level-rx-endpoints/cplane-message-processing-limits-enabled | -| 32 | UPLANE-ONLY-DL-MODE | O-RU supports U-Plane-only DL mode. | /user-plane-configuration/general-config/uplane-only-dl-mode-enable | -| 33 | DYNAMIC-TRANSMISSION-WINDOW-CONTROL | U-plane transmission window control configuration over C-plane | /user-plane-configuration /low-level-rx-endpoints/transmission-window-control | -| 34 | EXT-ANT-DELAY-CONTROL | O-RU supports external antenna delay control | /user-plane-configuration/tx-array-carriers/t-da-offset and/or /user-plane-configuration/rx-array-carriers/t-au-offset | -| 35 | EXTENDED-PRACH-CONFIGURATION | O-RU is able to support extended number of PRACH patterns and occasions provided by means of static PRACH. | /user-plane-configuration/static-low-level-rx-endpoints/extended-max-prach-patterns
/user-plane-configuration/static-prach-configurations/prach-patterns/prach-pattern-id
/user-plane-configuration/static-prach-configurations/prach-patterns/number-of-occasions
/user-plane-configuration/static-prach-configurations/prach-patterns/occasion-parameters/occasion-id | -| 36 | ENHANCED-T-COMBINE | O-RU can support t-combine-net and tx-duration | /shared-cell/shared-cell-config/enhanced-t-combine-enabled | -| 37 | INDEPENDENT-TRANSMISSION-WINDOW-CONTROL | Independent U-plane transmission window per endpoint | M-Plane activation not applicable | -| 38 | INTEGRITY-CHECK-AT-SW-DOWNLOAD | O-RU can perform integrity check at file download | /software-inventory/integrity-check-at-download-enabled | - -| | | | | | -|----|--|------------------------------------|------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 39 | | MULTIPLE-SCS-IN-EAXC | FHM supports combining for multiple SCS or multiple c-plane-types/frameStructure in a single eAxC-id | /shared-cell/shared-cell-config/multiple-scs-in-eaxc-used | -| 40 | | MULTIPLE-TRANSPORT-SESSION-TYPE | Multiple transport-session-type | /processing-elements/additional-transport-session-type-elements | -| 41 | | NON-PERSISTENT-MPLANE | Optimisations for non-persistent M-Plane | O-RU is configured with an event-collector identity (e.g. using DHCP) | -| 42 | | NON-SCHEDULED-UEID | O-RU endpoint is able to support non-scheduled-ueid | /user-plane-configuration / low-level-tx-endpoints/ non-scheduled-ueid-enabled and/or /user-plane-configuration / low-level-rx-endpoints/ non-scheduled-ueid-enabled | -| 43 | | ORDERED-TRANSMISSION | Ordered transmission | /user-plane-configuration /low-level-rx-endpoints/ordered-transmission | -| 44 | | SE11-WITH-CONTINUITY-BIT-SUPPORT | O-RU is able to support handling 'continuity' bit information in Section Extension 11 | /user-plane-configuration/low-level-tx-endpoints/se-11-continuity-flag-enabled | -| 45 | | SHARED-ORU-MULTI-ODU | O-RU is able to support supervision on a per O-DU basis | /supervision/per-odu-monitoring | -| 46 | | SHARED-ORU-MULTI-OPERATOR | O-RU is able to support operation with multiple shared resource operator O-DUs | /users/user/sro-id | -| 47 | | STATIC-TRANSMISSION-WINDOW-CONTROL | U-plane transmission window control configuration over M-plane | /user-plane-configuration /low-level-rx-endpoints/transmission-window-control | -| 48 | | SUPERVISION-WITH-SESSION-ID | O-RU uses the NETCONF session-id in supervision-notification | Not applicable | -| 49 | | UNIFORMLY-DISTRIBUTED-TRANSMISSION | Transmission of UL U-plane messages distributed uniformly over transmission window | /user-plane-configuration /low-level-rx-endpoints/transmission-type | -| 50 | | UPLANE-MESSAGE-PROCESSING-LIMITS | U-Plane message limits | /user-plane-configuration/general-config/ uplane-message-section-header-limit-enabled | -| 51 | | CALL-HOME-REACTIVATION-SUPPORTED | The O-RU supports on-demand re-start of call home flows towards lost call home O-RU controller (s) | Control not applicable. For details about intended usage, see clause 6.10 "On-demand renewal of Call Home procedure" | - -| | | | | -|----|----------------------------------|---------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 52 | SEQ-ID-CHECKING-CONFIGURABLE | O-RU supports disabling of sequence number checking | /user-plane-configuration/general-config/ seq-id-checking-disabled | -| 53 | TRX-CONTROL | O-RU Energy saving by TRX control via C-Plane | M-Plane activation not applicable. | -| 54 | ADVANCED-SLEEP-MODE | O-RU Energy saving by Advanced sleep mode | M-Plane activation not applicable. | -| 55 | SE23-PRB-BLOCK-MODE-SUPPORT | O-RU supports PRB-BLOCK mode of SE-23 | M-Plane activation not applicable. | -| 56 | MPLANE-DATA-LAYER-CONTROL | O-RU energy saving by data layer control using M-Plane procedures. | M-Plane activation not applicable. | -| 57 | PER-PORT-PTP-CONFIG | ITU-T G.8275.1 PTP profile specific per-port configuration for multi-port O-RUs | M-Plane activation not applicable. | -| 58 | PER-PORT-SYNCE-CONFIG | ITU-T G.781 SYNCE specific per-port configuration for multi-port O-RUs | M-Plane activation not applicable. | -| 59 | PER-INT-TCP-MSS | O-RU supports configuration of the TCP MSS on a per interface level | /if:interfaces/if:interface/ip:ipv4/o-ran-int:tcp/o-ran-int:mss-adjust or /if:interfaces/if:interface/ip:ipv6/o-ran-int:tcp/o-ran-int:mss-adjust | -| 60 | MULTIPLE-BEAMID-TABLES-SUPPORTED | Multiple beamId table support in O-RU | /user-plane-configuration/general-config/ /multiple-beamId-tables-support-enabled | -| 61 | MPLANE-TRX-CONTROL | O-RU Energy saving by TRX control via M-Plane | M-Plane activation not applicable. | -| 62 | DEEP-HIBERNATE | O-RU Supports Energy saving by deep-hibernate. | Activated by the RPC. | -| 63 | PRG-SIZE-SUPP-SE-21-WITH-ST6 | O-RU support for receiving prgSize information when SE 21 is sent with ST 6 | /user-plane-configuration/low-level-tx-endpoints/prg-size-supp-se-21-with-st6-enabled | -| 64 | PRG-SIZE-SUPP-SE-21-WITH-ST5 | O-RU support for receiving prgSize information when SE 21 is sent with ST 5 | /user-plane-configuration/low-level-tx-endpoints/prg-size-supp-se-21-with-st5-enabled | -| 65 | USER-GROUP-OPTIMIZATION | O-RU support for USER-GROUP-OPTIMIZATION | /user-plane-configuration /low-level-tx-endpoints/user-group-optimization-enabled-tx | -| 66 | BF-DELAY-PROFILE | O-RU endpoints support multiple delay profiles based on beamforming methods. | /user-plane-configuration /low-level-tx-endpoints /configured-bf-profile-id and/or /user-plane-configuration /low-level-rx-endpoints / configured-bf-profile-id | -| 67 | CONFIGURABLE-VSWR-THRESHOLDS | O-RU supports configurable VSWR thresholds for VSWR alarm. | /o-ran-uplane-conf:vswr-thresholds | - -| | | | | -|----|----------------------------------------------|---------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------| -| 68 | DMRS-BF-EQ | O-RU supports DMRS-BF-EQ functionality | Feature is activated when a carrier is activated with endpoint that uses beamforming methods DMRS-BF-EQ | -| 69 | DMRS-BF-NEQ | O-RU supports DMRS-BF-NEQ functionality | Feature is activated when a carrier is activated with endpoint that uses beamforming methods DMRS-BF-NEQ | -| 70 | DMRS-BF-NEQ-UNALTERED-FREQ-OFFSET | O-RU supports DMRS-BF-NEQ beamforming without changing frequency offset | M-Plane activation not applicable. | -| 71 | DMRS-BF-NEQ-UNALTERED-TAE | O-RU supports DMRS-BF-NEQ beamforming without changing TAE | M-Plane activation not applicable. | -| 72 | RRM-MEAS-REPORTING | O-RU supports RRM measurement reporting | Feature is activated when any endpoint is configured using rrm-meas-enabled | -| 73 | SE10-MEMBER-CANDIDATE-LIST | O-RU supports indicate candidate list for SE10 supported endpoints | M-Plane activation not applicable. | -| 74 | USER-GROUP-SELF-ASSEMBLY | O-RU support user group self assembly | /user-plane-configuration/rx-array-carrier/user-group-mode | -| 75 | UEID-PERSISTENCE | O-RU supports ue id persistence procedure | /user-plane-configuration/general-config/ueid-persistence-enabled | -| 76 | CONTINUITY-BLOCK-SIZE | O-RU supports one or more values of continuity block sizes | M-Plane activation not applicable. | -| 77 | SELECTED-BF-METHOD-CONFIGURATION | Configuration of BF method(s) by the O-DU | /user-plane-configuration/low-level-tx-endpoints/bf-methods and/or /user-plane-configuration/low-level-rx-endpoints/bf-methods | -| 78 | CLIENT-AUTH-SSH-PUBLIC-KEY | O-RU supports an optional feature to authenticate SSH client via SSHPUBLICKEY method. | /users/user/ssh-public-key and/or chg-ssh-public-key remote procedure call | -| 79 | SE27-ODU-CONTROLLED-DIMENSIONALITY-REDUCTION | O-RU support for O-DU controlled dimensionality reduction using SE27. | /user-plane-configuration/low-level-rx-endpoints/se-27-odu-controlled-dimensionality-reduction-enabled | -| 80 | MACSEC-BYPASS-POLICY | O-RU supports MACsec bypass policies | /if:interfaces/if:interface/o-ran-int:macsec-bypass-policy | -| 81 | POINT-A-OFFSET-TO-ABSOLUTE-FREQUENCY-CENTER | O-RU supports point-a-offset-to-absolute-frequency-center per rx-array-carrier | M-Plane activation not applicable. | -| 82 | SECURITY-LOGGING | O-RU supports O-RAN defined security logging. | M-Plane activation not applicable. | -| 83 | ORU-CONTROL-SINR-TIME-RESOLUTION | O-RU supports O-RU controlled time resolution for SINR reporting | /user-plane-configuration/low-level-rx-endpoints/oru-control-sinr-time-resolution-enabled | - -| | | | | | -|-------------------------------------|--|------------------------------------------------|----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| -| 84 | | DYNAMIC-SINR-PER-PRB | O-RU supports O-DU controlled frequency resolution for SINR reporting | /user-plane-configuration/low-level-rx-endpoints/dynamic-sinr-per-prb-enabled | -| 85 | | TRANSCEIVER-PRESENCE-CHANGE-SUPPORTED | Feature to indicate O-RU support for the transceiver presence change notification capability | M-Plane activation not applicable. | -| 86 | | TRANSCEIVER-ALARM-WARNING-SUPPORTED | O-RU support transceiver operating conditions alarms and warnings capability | M-Plane activation not applicable | -| 87 | | LOG-FILTER | O-RU supports filtering of troubleshooting logs | /start-troubleshooting-logs/input/filter | -| 88 | | FAN-PRESENT-AND-OPERATING-CHANGE-SUPPORTED | O-RU supports the fan present-and-operating change notification capability | Subscription to fan-presence-and-operating-change notification. | -| 89 | | MAX-POWER-CONTROL | O-RU Supports maximum power control | /user-plane-configuration/array-config-container/tx-array-max-power-level-index or /user-plane-configuration/tx-array-carrier/carrier-max-power-reduction | -| 90 | | SHARED-CELL-STATS (note 1) | FHM/Cascade O-RU supported shared-cell-stats measurement | /performance-measurement-objects/shared-cell-measurement-objects | -| 91 | | CYCLIC-DELAY-SUPPORTED | This feature indicates that O-RU supports cyclic delay adjustment. | M-Plane activation not applicable. | -| 92 | | POINT-A-OFFSET-TO-ABSOLUTE-FREQUENCY-CENTER-TX | O-RU supports point-a-offset-to-absolute-frequency-center per tx-array-carrier | M-Plane activation not applicable. | -| NOTE 1. This feature is deprecated. | | | | | - -Some of the O-RAN defined YANG models augment or import models from existing YANG modules which have optional features defined. The optional features defined in these "common" models are shown in the Table C.2-2 below. - -**Table C.2-2: Optional feature support in common models** - -| No | Optional Feature | Namespace | Feature name | -|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------|------------------------------| -| 1 | RFC 6933: Entity MIB | "urn:ietf:params:xml:ns:yang:ietf-hardware" | entity-mib | -| 2 | RFC 4268: Entity State MIB | "urn:ietf:params:xml:ns:yang:ietf-hardware" | hardware-state | -| 3 | RFC 3433: Entity Sensor Management Information Base | "urn:ietf:params:xml:ns:yang:ietf-hardware" | hardware-sensor | -| 4 | O-RU allows user-controlled interfaces to be named arbitrarily | "urn:ietf:params:xml:ns:yang:ietf-interfaces" | arbitrary-names | -| 5 | O-RU supports pre-provisioning of interface configuration, i.e. it is possible to configure an interface whose physical interface hardware is not present on the device | "urn:ietf:params:xml:ns:yang:ietf-interfaces" | pre-provisioning | -| 6 | RFC 2863: The Interfaces Group MIB | "urn:ietf:params:xml:ns:yang:ietf-interfaces" | if-mib | -| 7 | O-RU supports configuring non-contiguous subnet masks | "urn:ietf:params:xml:ns:yang:ietf-ip" | ipv4-non-contiguous-netmasks | -| 8 | O-RU supports privacy extensions for stateless address autoconfiguration in IPv6 | "urn:ietf:params:xml:ns:yang:ietf-ip" | ipv6-privacy-autoconf | -| 9 | O-RU supports configured YANG Notifications | "urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications" | configured | -| 10 | O-RU supports JSON encoding of subscriptions to YANG notifications | "urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications" | encode-json | -| 11 | RFC 9645: O-RU supports TLS hello message parameters configuration | "urn:ietf:params:xml:ns:yang:ietf-tls-common" | hello-params | -| 12 | RFC 9645: O-RU supports the 'supported-algorithms' container for TLS. | "urn:ietf:params:xml:ns:yang:ietf-tls-common" | algorithm-discovery | -| 13 | RFC 9645: TLS Protocol Version 1.2. | "urn:ietf:params:xml:ns:yang:ietf-tls-common" | tls12 | -| 14 | RFC 9645: TLS Protocol Version 1.3. | "urn:ietf:params:xml:ns:yang:ietf-tls-common" | tls13 | -| 15 | RFC 9644: O-RU supports the configuration of SSH transport layer [96]. | "urn:ietf:params:xml:ns:yang:ietf-ssh-common" | transport-params | -| 16 | RFC 9644: O-RU supports the 'supported-algorithms' container for SSH [96]. | "urn:ietf:params:xml:ns:yang:ietf-ssh-common" | algorithm-discovery | -| 17 | RFC 9645: O-RU supports authenticating clients using X.509 certificates [97]. | "urn:ietf:params:xml:ns:yang:ietf-tls-server" | client-auth-x509-cert | -| 18 | RFC 9645: O-RU supports configuration for how to authenticate clients [97]. | "urn:ietf:params:xml:ns:yang:ietf-tls-server" | client-auth-supported | -| 19 | RFC 9645: O-RU supports identifying itself using X.509 certificates [97]. | "urn:ietf:params:xml:ns:yang:ietf-tls-server" | server-ident-x509-cert | -| 20 | RFC 9644: O-RU supports the 'password' authentication type, per RFC 4252, for locally-defined users [96]. | "urn:ietf:params:xml:ns:yang:ietf-ssh-server" | local-user-auth-password | - -| | | | | -|----|------------------------------------------------------------------------------------------------------------|-----------------------------------------------|---------------------------| -| 21 | RFC 9644: O-RU supports the 'publickey' authentication type, per RFC 4252, for locally-defined users [96]. | "urn:ietf:params:xml:ns:yang:ietf-ssh-server" | local-user-auth-publickey | -| 22 | RFC 9644: O-RU supports configuration of local users [96]. | "urn:ietf:params:xml:ns:yang:ietf-ssh-server" | local-users-supported | - -### C.3 Optional features exposed using O-RAN YANG models - -In addition to optional namespaces and optional YANG feature tags specified in O-RU supported namespaces, certain O-RAN defined YANG models include read-only YANG leaf nodes used to be able to indicate support by an O-RU of for certain optional capabilities by the O-RU. - -**Table C.3-1: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:ald-port:x.y YANG model** - -| No | Namespace | Optional Feature | Read-only YANG leaf indicating feature support | Optional Feature Control | -|----|---------------------------|----------------------------------|------------------------------------------------|------------------------------------------| -| 1 | "urn:o-ran:ald-port:x.y " | Control of ALD's DC power supply | /ald-ports-io/ald-port/dc-control-support | /ald-ports-io/ald-port/dc-enabled-status | - -**Table C.3-2: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:antcal:x.y YANG model** - -| No | Namespace | Optional Feature | Read-only YANG leaf indicating feature support | Optional Feature Control | -|----|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------| -| 1 | "urn:o-ran:antcal:x.y" | O-RU is able to perform self calibration | /antenna-calibration/antenna-calibration-capabilities/self-calibration-support | /antenna-calibration/self-calibration-policy/self-calibration-allowed | -| 2 | "urn:o-ran:antcal:x.y" | O-RU supports configuration of the preparedness timer that controls how far in advance of the coordinated self calibration procedure the O-RU is required to send the notification of impacted resources | /antenna-calibration/antenna-calibration-capabilities/configured-preparation-timer-supported | Clause 15.5 defines use when supported. | - -**Table C.3-3: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:beamforming:x.y YANG model** - -| No | Namespace | Optional Feature | Read-only YANG leaf indicating feature support | Optional Feature Control | -|----|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| -| 1 | "urn:o-ran:beamforming:x.y" | O-RU supports the capability to apply the modified beamforming configuration by using rpc activate-beamforming-config-by-capability-group without deletion of tx-array-carriers and rx-array-carriers | /beamforming-config/operational-properties/update-bf-non-delete | activate-beamforming-config-by-capability-group RPC | -| 2 | "urn:o-ran:beamforming:x.y" | O-RU supports the capability to store the modified beamforming configuration file in the reset persistent memory | /beamforming-config/operational-properties/persistent-bf-files | M-Plane activation not applicable | -| 3 | "urn:o-ran:beamforming:x.y" | O-RU supports dynamic beamforming control mode | /beamforming-config/static-properties/rt-bf-weights-update-support | M-Plane activation not applicable. CUS-Plane [2] clause 7.7.1.2 defines use when supported. | -| 4 | "urn:o-ran:beamforming:x.y" | O-RU supports attributes based dynamic beamforming control mode | beamforming-config/beamforming-trough-attributes-supported | M-Plane activation not applicable. CUS-Plane [2] clause 7.7.2.1 defines use when supported. | -| 5 | "urn:o-ran:beamforming:x.y" | O-RU supports beamforming based on UE channel information | beamforming-config/beamforming-trough-ue-channel-info-supported | M-Plane activation not applicable. CUS-Plane [2] clause 7.2.7 defines use when supported. | -| 6 | "urn:o-ran:beamforming:x.y" | O-RU supports dynamic channel information compression | /beamforming-config/ue-specific-beamforming/dynamic-channel-information-compression-supported | M-Plane activation not applicable CUS-Plane [2] clause 7.5.2.15 defines use when supported. | -| 7 | "urn:o-ran:beamforming:x.y" | O-RU support for DMRS-BF-EQ scaling function SCALING-F-1 or SCALING-F-2 | /beamforming-config/dmrs-bf/general/capabilities/equalization-data-scaling | M-Plane activation not applicable. | -| 8 | "urn:o-ran:beamforming:x.y" | O-RU supports the capability to apply the modified beamforming configuration without deactivating of tx-array-carriers and rx-array-carriers | /beamforming-config/operational-properties/in-service-bf-update | activate-beamforming-config RPC or activate-beamforming-config-by-capability-group RPC | - -**Table C.3-4: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:message5:x.y YANG model** - -| No | Namespace | Optional Feature | Read-only YANG leaf indicating feature support | Optional Feature Control | -|----|--------------------------|------------------------------------------------------------------------|------------------------------------------------|--------------------------------------------------------------------------------------------| -| 1 | "urn:o-ran:message5:x.y" | O-RU supports eCPRI message 5 one-step procedure for T34 measurements. | /ecpri-delay-message/one-step-t34-supported | M-Plane activation not applicable CUS-Plane [2] clause 4.4.4.4 defines use when supported. | -| 2 | "urn:o-ran:message5:x.y" | O-RU supports eCPRI message 5 two-step procedure for T34 measurements. | /ecpri-delay-message/two-step-t34-supported | M-Plane activation not applicable CUS-Plane [2] clause 4.4.4.4 defines use when supported. | - -**Table C.3-5: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:hardware:x.y YANG model** - -| No | Namespace | Optional Feature | Read-only YANG leaf indicating feature support | Optional Feature Control | -|----|--------------------------|------------------------------------|------------------------------------------------|-----------------------------------| -| 1 | "urn:o-ran:hardware:x.y" | O-RU supports the dying gasp alarm | /hardware/component/dying-gasp-support | M-Plane activation not applicable | - -**Table C.3-6: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:interfaces:x.y YANG model** - -| No | Namespace | Optional Feature | Read-only YANG leaf indicating feature support | Optional Feature Control | -|----|----------------------------|-------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------|---------------------------------------------------| -| 1 | "urn:o-ran:interfaces:x.y" | O-RU's rate able to be supported by an interface is less than nominal bit rate indicated by its transceiver model | /interfaces/interface-grouping | M-Plane activation not applicable | -| 2 | "urn:o-ran:interfaces:x.y" | O-RU supports MACsec bypass policies based on destination MAC address, ethertype and/or vlan-id | /interfaces/macsec-bypass-capabilities/supported-policy | /interfaces/interface/macsec-bypass-policy/policy | - -**Table C.3-7: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:module-cap:x.y YANG model** - -| No | Namespace | Optional Feature | Read-only YANG leaf indicating feature support | Optional Feature Control | -|----|----------------------------|------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------| -| 1 | "urn:o-ran:module-cap:x.y" | O-RU supports Category B operation – precoding in the O-RU | /module-capability/ru-capabilities/ru-supported-category | M-Plane activation not applicable. CUS-Plane [2] clause 7.2.4 defines use when supported. | -| 2 | "urn:o-ran:module-cap:x.y" | O-RU supports dynamic compression method | /module-capability/ru-capabilities/format-of-iq-sample/dynamic-compression-supported | M-Plane activation not applicable. CUS-Plane[2] clause 7.5.2.10 defines use when supported. | -| 3 | "urn:o-ran:module-cap:x.y" | O-RU supports real-time variable bit with | /module-capability/ru-capabilities/format-of-iq-sample/realtime-variable-bit-width-supported | M-Plane activation not applicable. CUS-Plane[2] clause 7.5.2.10 defines use when supported. | -| 4 | "urn:o-ran:module-cap:x.y" | O-RU supports iq compression methods | O-RU sets the list /module-capability/ru-capabilities/format-of-iq-sample/compression-method-supported with compression methods the O-RU supports. | M-Plane activation not applicable. CUS-Plane[2] clause 8.3.3.13 defines use when supported. | -| 5 | "urn:o-ran:module-cap:x.y" | O-RU supports beamspace compression | O-RU sets a list entry /module-capability/ru-capabilities/format-of-iq-sample/compression-method-supported with compression-method set to "BEAMSPACE" | M-Plane activation not applicable. CUS-Plane[2] clause 8.3.3.13 defines use when supported. | -| 6 | "urn:o-ran:module-cap:x.y" | O-RU supports variable bit width per channel | /module-capability/ru-capabilities/format-of-iq-sample/variable-bit-width-per-channel-supported | M-Plane activation not applicable. CUS-Plane[2] clause 7.5.2.10 defines use when supported. | -| 7 | "urn:o-ran:module-cap:x.y" | O-RU supports symbol number increment command in a C-Plane | /module-capability/ru-capabilities/format-of-iq-sample/syminc-supported | M-Plane activation not applicable. | -| 8 | "urn:o-ran:module-cap:x.y" | O-RU supports regularizationFactor in section type 5 | /module-capability/ru-capabilities/format-of-iq-sample/regularization-factor-se-supported | /user-plane-configuration/general-config/ regularization-factor-se-configured | -| 9 | "urn:o-ran:module-cap:x.y" | O-RU supports little endian | /module-capability/ru-capabilities/format-of-iq-sample/little-endian-supported | /user-plane-configuration/general-config/ little-endian-byte-order | -| 10 | "urn:o-ran:module-cap:x.y" | O-RU requires 4-byte aligned Section Type 6 | /module-capability/ru-capabilities/st6-4byte-alignment-required | M-Plane activation not applicable. CUS-Plane[2] clause 7.3.1 defines use when supported. | -| 11 | "urn:o-ran:module-cap:x.y" | O-RU supports energy saving by transmission blanking | /module-capability/ru-capabilities/energy-saving-by-transmission-blanks | M-Plane activation not applicable. CUS-Plane[2] clause 8.4.2.3 defines use when supported. | - -| | | | | | -|----|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------| -| 12 | "urn:o-ran:module-cap:x.y" | O-RU supports dynamic transport delay management through eCPRI Msg 5 | /module-capability/ru-capabilities/dynamic-transport-delay-management-supported | M-Plane activation not applicable. CUS-Plane[2] clause 4.4.4.4 defines use when supported. | -| 13 | "urn:o-ran:module-cap:x.y" | O-RU expects unique eCPRI sequence id for eAxC_IDs serving for UL and DL for the same Component Carrier | /module-capability/ru-capabilities/support-only-unique-ecpri-seqid-per-eaxc | M-Plane activation not applicable. CUS-Plane[2] defines use when supported. | -| 14 | "urn:o-ran:module-cap:x.y" | O-RU supports coupling of C and U-plane messages by frequency and time | /module-capability/coupling-methods/coupling-via-frequency-and-time | M-Plane activation not applicable. CUS-Plane[2] clause 8.4.1 defines use when supported. | -| 15 | "urn:o-ran:module-cap:x.y" | O-RU supports coupling of C and U-plane messages by frequency and time with priorities | /module-capability/coupling-methods/coupling-via-frequency-and-time-with-priorities | M-Plane activation not applicable. CUS-Plane[2] clause 7.9.7 defines use when supported. | -| 16 | "urn:o-ran:module-cap:x.y" | O-RU supports coupling of C and U-plane messages by frequency and time with priorities optimized | /module-capability/coupling-methods/coupling-via-frequency-and-time-with-priorities-optimized | M-Plane activation not applicable. CUS-Plane[2] clause 7.9.8 defines use when supported. | -| 17 | "urn:o-ran:module-cap:x.y" | O-RU supports optional field udCompLen in U-Plane messages | /module-capability/ud-comp-len-supported | M-Plane activation not applicable. CUS-Plane[2] clause 8.3.3.19 defines use when supported. | -| 18 | "urn:o-ran:module-cap:x.y" | O-RU supports configuration of different t-da-offset on different tx-array-carriers, and different t-au-offset on different rx-array-carriers | /module-capability/ext-ant-delay-capability set to "PER-ARRAY-CARRIER" | M-Plane activation not applicable. CUS-Plane[2] clause 4.7 defines use when supported. | -| 19 | "urn:o-ran:module-cap:x.y" | O-RU supports the configuration of different t-da-offset on different tx-array-carriers only when those tx-array-carriers belong to different tx-arrays | /module-capability/ext-ant-delay-capability set to "PER-ARRAY" | M-Plane activation not applicable. CUS-Plane[2] clause 4.7 defines use when supported. | -| 20 | "urn:o-ran:module-cap:x.y" | O-RU supports the configuration of a common t-da-offset across all tx-array-carriers | /module-capability/ext-ant-delay-capability set to "PER-O-RU" | M-Plane activation not applicable. CUS-Plane[2] clause 4.7 defines use when supported. | -| 21 | "urn:o-ran:module-cap:x.y" | O-RU supports sending NACK feedback if a section extension for ACK/NACK request is received | /module-capability/nack-supported | M-Plane activation not applicable. CUS-Plane[2] defines use when supported. | -| 22 | "urn:o-ran:module-cap:x.y" | O-RU local management of the LAA contention window | /module-capability/band-capabilities/sub-band-info/self-configure | M-Plane activation not applicable. | -| 23 | "urn:o-ran:module-cap:x.y" | O-RU supports Ready message via Section Type 8 | /module-capability/ru-capabilities/energy-saving-capability-common-info/st8- | M-Plane activation not applicable. CUS-Plane[2] clause 16.6.2 | - -| | | | | | -|----|----------------------------|------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| -| | | | ready-command-supported | defines use when supported. | -| 24 | "urn:o-ran:module-cap:x.y" | O-RU supports extension of ongoing sleep interval. | /module-capability/ru-capabilities/energy-saving-capability-common-info/sleep-duration-extension-supported | M-Plane activation not applicable. CUS-Plane [2] clause 16.8 defines use when supported. | -| 25 | "urn:o-ran:module-cap:x.y" | O-RU supports M-Plane Emergency wake-up procedure | /module-capability/ru-capabilities/energy-saving-capability-common-info/emergency-wake-up-command-supported | M-Plane activation not applicable. Clause 20.3.1.3 defines use when supported. | -| 26 | "urn:o-ran:module-cap:x.y" | O-RU supports optional field scs in Section Type 8 | /module-capability/ru-capabilities/st8-scs-supported | M-Plane activation not applicable. CUS-Plane [2] clause 7.5.2.16 defines use when supported. | -| 27 | "urn:o-ran:module-cap:x.y" | O-RU supports receiving non-zero values of bundleOffset in SE11. | /module-capability/ru-capabilities/bundle-offset-in-se11-supported | M-Plane activation not applicable. CUS-Plane [2] clause 7.7.11.10 defines use when supported. | - -**Table C.3-8: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:operations:x.y YANG model** - -| No | Namespace | Optional Feature | Read-only YANG leaf indicating feature support | Optional Feature Control | -|----|----------------------------|-----------------------------|---------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------| -| 1 | "urn:o-ran:operations:x.y" | IEEE 1914.3 header support | /operational-info/declarations/supported-header-mechanism/protocol | M-Plane activation not applicable. CUS-Plane [2] clause 5.1.3.3 defines use when supported. | -| 2 | "urn:o-ran:operations:x.y" | eCPRI Concatenation support | /operational-info/declarations/supported-header-mechanism/ecpri-concatenation-support | M-Plane activation not applicable. CUS-Plane [2] clause 5.1.3.2.4 defines use when supported. | - -**Table C.3-9: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:performance-management:x.y YANG model** - -| No | Namespace | Optional Feature | Read-only YANG leaf indicating feature support | Optional Feature Control | -|----|-----------------------------------------|----------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------| -| 1 | "urn:o-ran:performance-management:x.y" | O-RU supports RX power transceiver measurement | /performance-measurement-objects/measurement-capabilities/transceiver-objects/measurement-object set to "RX_POWER" | /performance-measurement-objects/transceiver-measurement-objects | -| 2 | "urn:o-ran:performance-management:x.y " | O-RU supports TX power transceiver measurement | /performance-measurement-objects/measurement-capabilities/transceiver-objects/measurement-object set to "TX_POWER" | /performance-measurement-objects/transceiver-measurement-objects | -| 3 | "urn:o-ran:performance-management:x.y " | O-RU supports TX Bias Current transceiver measurement | /performance-measurement-objects/measurement-capabilities/transceiver-objects/measurement-object set to "TX_BIAS_COUNT" | /performance-measurement-objects/transceiver-measurement-objects | -| 4 | "urn:o-ran:performance-management:x.y " | O-RU supports transceiver voltage measurement | /performance-measurement-objects/measurement-capabilities/transceiver-objects/measurement-object set to "VOLTAGE" | /performance-measurement-objects/transceiver-measurement-objects | -| 5 | "urn:o-ran:performance-management:x.y " | O-RU supports transceiver module temperature measurement | /performance-measurement-objects/measurement-capabilities/transceiver-objects/measurement-object set to "TEMPERATURE" | /performance-measurement-objects/transceiver-measurement-objects | -| 6 | "urn:o-ran:performance-management:x.y " | O-RU supports RX Window on Time measurement | /performance-measurement-objects/measurement-capabilities/rx-window-objects/measurement-object set to "RX_ON_TIME" | /performance-measurement-objects/rx-window-measurement-objects | -| 7 | "urn:o-ran:performance-management:x.y " | O-RU supports RX Window too early Time measurement | /performance-measurement-objects/measurement-capabilities/rx-window-objects/measurement-object set to "RX_EARLY" | /performance-measurement-objects/rx-window-measurement-objects | -| 8 | "urn:o-ran:performance-management:x.y " | O-RU supports RX Window too late Time measurement | /performance-management-objects/measurement-capabilities/rx-window-objects/measurement-object set to "RX_LATE" | /performance-measurement-objects/rx-window-measurement-objects | -| 9 | "urn:o-ran:performance-management:x.y " | O-RU supports RX Window corrupt measurement | /performance-measurement-objects/measurement-capabilities/rx-window-objects/measurement-object set to | /performance-measurement-objects/rx-window-measurement-objects | - -| | | | | | -|--|--|--|--------------|--| -| | | | "RX_CORRUPT" | | -|--|--|--|--------------|--| - -| | | | | | -|----|-----------------------------------------|-------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------| -| 10 | "urn:o-ran:performance-management:x.y " | O-RU supports RX Window duplicate measurement | /performance-measurement-objects/measurement-capabilities/rx-window-objects/measurement-object set to RX_DUPL | /performance-measurement-objects/rx-window-measurement-objects | -| 11 | "urn:o-ran:performance-management:x.y " | O-RU supports RX Window on Time measurement for control packets | /performance-measurement-objects/measurement-capabilities/rx-window-objects/measurement-object set to "RX_ON_TIME_C" | /performance-measurement-objects/rx-window-measurement-objects | -| 12 | "urn:o-ran:performance-management:x.y " | O-RU supports RX Window too early Time measurement for control packets | /performance-measurement-objects/measurement-capabilities/rx-window-objects/measurement-object set to "RX_EARLY_C" | /performance-measurement-objects/rx-window-measurement-objects | -| 13 | "urn:o-ran:performance-management:x.y " | O-RU supports RX Window too late Time measurement for control packets | /performance-measurement-objects/measurement-capabilities/rx-window-objects/measurement-object set to "RX_LATE_C" | /performance-measurement-objects/rx-window-measurement-objects | -| 14 | "urn:o-ran:performance-management:x.y " | O-RU supports RX Window sequence error measurements | /performance-measurement-objects/measurement-capabilities/rx-window-objects/measurement-object set to "RX_SEQID_ERR" | /performance-measurement-objects/rx-window-measurement-objects | -| 15 | "urn:o-ran:performance-management:x.y " | O-RU supports RX Window sequence error measurements for control packets | /performance-measurement-objects/measurement-capabilities/rx-window-objects/measurement-object set to "RX_SEQID_ERR_C" | /performance-measurement-objects/rx-window-measurement-objects | -| 16 | "urn:o-ran:performance-management:x.y " | O-RU supports RX Window packet drop measurements | /performance-measurement-objects/measurement-capabilities/rx-window-objects/measurement-object set to "RX_ERR_DROP" | /performance-measurement-objects/rx-window-measurement-objects | -| 17 | "urn:o-ran:performance-management:x.y " | O-RU supports TX Window measurements for all outbound packets | /performance-measurement-objects/measurement-capabilities/tx-stats-objects/measurement-object set to "TX_TOTAL" | /performance-measurement-objects/tx-measurement-objects | -| 18 | "urn:o-ran:performance-management:x.y " | O-RU supports TX Window measurements for outbound control packets | /performance-management-objects/measurement-capabilities/tx-stats-objects/measurement-object set to | /performance-measurement-objects/tx-measurement-objects | - -| | | | | | -|--|--|--|--------------|--| -| | | | "TX_TOTAL_C" | | -|--|--|--|--------------|--| - -| | | | | | -|----|-----------------------------------------|------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------| -| 19 | "urn:o-ran:performance-management:x.y " | O-RU supports temperature measurements of specific hardware components | /performance-measurement-objects/measurement-capabilities/epe-stats-objects/measurement-object set to "TEMPERATURE" | /performance-measurement-objects/epe-measurement-objects | -| 20 | "urn:o-ran:performance-management:x.y " | O-RU supports power measurements of specific hardware components | /performance-measurement-objects/measurement-capabilities/epe-stats-objects/measurement-object set to "POWER" | /performance-measurement-objects/epe-measurement-objects | -| 21 | "urn:o-ran:performance-management:x.y " | O-RU supports voltage measurements of specific hardware components | /performance-measurement-objects/measurement-capabilities/epe-stats-objects/measurement-object set to "VOLTAGE" | /performance-measurement-objects/epe-measurement-objects | -| 22 | "urn:o-ran:performance-management:x.y " | O-RU supports current measurements of specific hardware components | /performance-measurement-objects/measurement-capabilities/epe-stats-objects/measurement-object set to "CURRENT" | /performance-measurement-objects/epe-measurement-objects | -| 23 | "urn:o-ran:performance-management:x.y " | O-RU supports VSWR measurements | /performance-measurement-objects/measurement-capabilities/tx-antenna-stats-objects/measurement-object set to "VSWR" | /performance-measurement-objects/tx-antenna-measurement-objects | -| 24 | "urn:o-ran:performance-management:x.y " | O-RU supports transceiver laser temperature measurements | /performance-measurement-objects/measurement-capabilities/transceiver-objects/measurement-object set to "LASER_TEMPERATURE" | /performance-measurement-objects/transceiver-measurement-objects | -| 25 | "urn:o-ran:performance-management:x.y " | O-RU supports transceiver module TEC current measurement | /performance-measurement-objects/measurement-capabilities/transceiver-objects/measurement-object set to "TEC_CURRENT" | /performance-measurement-objects/transceiver-measurement-objects | -| 26 | "urn:o-ran:performance-management:x.y " | O-RU supports RX Window measurements | /performance-measurement-objects/measurement-capabilities/rx-window-objects/measurement-object set to RX_TOTAL | /performance-measurement-objects/rx-window-measurement-objects | -| 27 | "urn:o-ran:performance-management:x.y " | O-RU supports symbol rssi all ul symbols measurement | /performance-measurement-objects/measurement-capabilities/symbol-rssi-stats-objects/measurement-object set to ALL-UL-SYMBOLS | /performance-measurement-objects/symbol-rssi-measurement-objects | -| 28 | "urn:o-ran:performance-management:x.y " | O-RU supports symbol rssi configured symbols | /performance-measurement-objects/ | /performance-measurement-objects/ | - -| | | | | | -|--|-----------------------------|-------------|----------------------------------------------------------------------------------------------------------------|-------------------------------------| -| | ce-
management:
x.y " | measurement | measurement-
capabilities/symbol-rssi-
stats-objects/
measurement-object set to
CONFIGURED-SYMBOLS | symbol-rssi-
measurement-objects | -|--|-----------------------------|-------------|----------------------------------------------------------------------------------------------------------------|-------------------------------------| - -| | | | | | -|----|-----------------------------------------|---------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------| -| 29 | "urn:o-ran:performance-management:x.y " | O-RU supports shared-cell rx up ul measurement | /performance-measurement-objects/measurement-capabilities/shared-cell-stats-objects/measurement-object set to RX_UP_UL | /performance-measurement-objects/shared-cell-measurement-objects | -| 30 | "urn:o-ran:performance-management:x.y " | O-RU supports shared-cell rx up ul combined measurement | /performance-measurement-objects/measurement-capabilities/shared-cell-stats-objects/measurement-object set to RX_UP_UL_COMBINED | /performance-measurement-objects/shared-cell-measurement-objects | -| 31 | "urn:o-ran:performance-management:x.y " | O-RU supports tssi IQ power level measurement | /performance-measurement-objects/measurement-capabilities/tssi-stats-objects/measurement-object set to TSSI-IQ-POWER-LEVEL | /performance-measurement-objects/tssi-measurement-objects | -| 32 | "urn:o-ran:performance-management:x.y " | O-RU supports rssi measurement | /performance-measurement-objects/measurement-capabilities/rssi-stats-objects/measurement-object set to RSSI | /performance-measurement-objects/rssi-measurement-objects | -| 33 | "urn:o-ran:performance-management:x.y " | O-RU supports tx output power measurement | /performance-measurement-objects/measurement-capabilities/tx-output-power-stats-objects/measurement-object set to TX_OUTPUT_POWER | /performance-measurement-objects/tx-output-power-measurement-objects | -| 34 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet in octets measurement | /performance-measurement-objects/measurement-capabilities/ethernet-measurement-objects/measurement-object set to IN-OCTETS | /performance-measurement-objects/ethernet-measurement-objects | -| 35 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet in unicast pkts measurement | /performance-measurement-objects/measurement-capabilities/ethernet-measurement-objects/measurement-object set to IN-UNICAST-PKTS | /performance-measurement-objects/ethernet-measurement-objects | -| 36 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet in broadcast pkts measurement | /performance-measurement-objects/measurement-capabilities/ethernet-measurement-objects/measurement-object set to IN-BROADCAST-PKTS | /performance-measurement-objects/ethernet-measurement-objects | -| 37 | "urn:o-ran:performance-management: | O-RU supports Ethernet in multicast pkts measurement | /performance-management-objects/measurement-capabilities/ethernet- | /performance-measurement-objects/ethernet-measurement- | - -| | | | | | -|--|------|--|------------------------------------------------------------------------|---------| -| | x.y" | | measurement-objects/
measurement-object set to
IN-MULTICAST-PKTS | objects | -|--|------|--|------------------------------------------------------------------------|---------| - -| | | | | | -|----|-----------------------------------------|----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| -| 38 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet in discards measurement | /performance-measurement-objects/measurement-capabilities/ethernet-measurement-objects/measurement-object set to IN-DISCARDS | /performance-measurement-objects/ethernet-measurement-objects | -| 39 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet in errors measurement | /performance-measurement-objects/measurement-capabilities/ethernet-measurement-objects/measurement-object set to IN-ERRORS | /performance-measurement-objects/ethernet-measurement-objects | -| 40 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet in unknown protos measurement | /performance-measurement-objects/measurement-capabilities/ethernet-measurement-objects/measurement-object set to IN-UNKNOWN-PROTOS | /performance-measurement-objects/ethernet-measurement-objects | -| 41 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet in crc errors measurement | /performance-measurement-objects/measurement-capabilities/ethernet-measurement-objects/measurement-object set to IN-CRC-ERRORS | /performance-measurement-objects/ethernet-measurement-objects | -| 42 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet in fec correctable blocks measurement | /performance-measurement-objects/measurement-capabilities/ethernet-measurement-objects/measurement-object set to IN-FEC-CORRECTABLE-BLOCKS | /performance-measurement-objects/ethernet-measurement-objects | -| 43 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet in fec uncorrectable blocks measurement | /performance-measurement-objects/measurement-capabilities/ethernet-measurement-objects/measurement-object set to IN-FEC-UNCORRECTABLE-BLOCKS | /performance-measurement-objects/ethernet-measurement-objects | -| 44 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet in pcs status change count measurement | /performance-measurement-objects/measurement-capabilities/ethernet-measurement-objects/measurement-object set to IN-PCS-STATUS-CHANGE-COUNT | /performance-measurement-objects/ethernet-measurement-objects | -| 45 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet out unicast pkts measurement | /performance-measurement-objects/measurement-capabilities/ethernet-measurement-objects/ | /performance-measurement-objects/ethernet-measurement-objects | - -| | | | | | -|--|--|--|-----------------------------------------|--| -| | | | measurement-object set to
OUT-OCTETS | | -|--|--|--|-----------------------------------------|--| - -| | | | | | -|----|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------| -| 46 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet out unicast pkts measurement | /performance-measurement-objects/measurement-capabilitites/ethernet-measurement-objects/measurement-object set to OUT-UNICAST-PKTS | /performance-measurement-objects/ethernet-measurement-objects | -| 47 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet out broadcast pkts measurement | /performance-measurement-objects/measurement-capabilitites/ethernet-measurement-objects/measurement-object set to OUT-BROADCAST-PKTS | /performance-measurement-objects/ethernet-measurement-objects | -| 48 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet out multicast pkts measurement | /performance-measurement-objects/measurement-capabilitites/ethernet-measurement-objects/measurement-object set to OUT-MULTICAST-PKTS | /performance-measurement-objects/ethernet-measurement-objects | -| 49 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet out discards measurement | /performance-measurement-objects/measurement-capabilitites/ethernet-measurement-objects/measurement-object set to OUT-DISCARDS | /performance-measurement-objects/ethernet-measurement-objects | -| 50 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet out errors measurement | /performance-measurement-objects/measurement-capabilitites/ethernet-measurement-objects/measurement-object set to OUT-ERRORS | /performance-measurement-objects/ethernet-measurement-objects | -| 51 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet interface measurement of successfully received frames | /performance-measurement-objects/measurement-capabilitites/ethernet-objects/measurement-object set to "IN-FRAMES" | /performance-measurement-objects/ethernet-measurement-objects | -| 52 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet interface measurement of received VLAN-tagged frames with VLAN ID not matching with the VLAN ID of any VLAN interface | /performance-measurement-objects/measurement-capabilitites/ethernet-objects/measurement-object set to "IN-UNKNOWN-VLAN-FRAMES" | /performance-measurement-objects/ethernet-measurement-objects | -| 53 | "urn:o-ran:performance-management:x.y " | O-RU supports Ethernet interface measurement of successfully transmitted frames | /performance-measurement-objects/measurement-capabilitites/ethernet-objects/measurement-object set to "OUT-FRAMES" | /performance-measurement-objects/ethernet-measurement-objects | -| 54 | "urn:o-ran:performance-management:x.y " | O-RU supports tuned DWDM channel frequency | /performance-measurement-objects/ | /performance-measurement-objects/ | - -| | | | | | -|----|---------------------------------------------|-------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------| -| | ce-management:
x.y " | error | measurement-capabilities/
transceiver-measurement-objects/measurement-object set to
TUNED_DWDM_CHANNEL_FREQUENCY_ERROR | transceiver-measurement-objects | -| 55 | "urn:o-ran:performance-management:
x.y " | O-RU supports tuned DWDM channel frequency wavelength error | /performance-measurement-objects/
measurement-capabilities/
transceiver-measurement-objects/measurement-object set to
TUNED_DWDM_CHANNEL_WAVELENGTH_ERROR | /performance-measurement-objects/
transceiver-measurement-objects | - -**Table C.3-10: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:shared-cell:x.y YANG model** - -| No | Namespace | Optional Feature | Read-only YANG leaf indicating feature support | Optional Feature Control | -|----|-----------------------------|----------------------------------------------------------------|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------------| -| 1 | "urn:o-ran:shared-cell:x.y" | O-RU supports multi cell operation in shared cell cascade mode | /shared-cell/shared-cell-module-cap/multi-cell-in-cascade-mode-supported | M-Plane activation not applicable. CUS-Plane[2] clause 13.4 defines use when supported. | - -**Table C.3-11: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:software-management:x.y YANG model** - -| No | Namespace | Optional Feature | Read-only YANG leaf indicating feature support | Optional Feature Control | -|----|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------|--------------------------| -| 1 | "urn:o-ran:software-management:
x.y" | O-RU requires separate download procedures to be re-used for downloading individual files in a software build, instead of a single archived package | /software-inventory/build-content-download | software-download rpc | - -**Table C.3-12: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:sync:x.y YANG model** - -| No | Namespace | Optional Feature | Read-only YANG leaf indicating feature support | Optional Feature Control | -|----|----------------------|--------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|------------------------------------| -| 1 | "urn:o-ran:sync:x.y" | O-RU supports PTP | O-RU includes "PTP" enumeration in /sync/sync-status/supported-reference-types list item | /sync/ptp-config | -| 2 | "urn:o-ran:sync:x.y" | O-RU supports Synchronous Ethernet | O-RU includes "SYNCE" enumeration in /sync/sync-status/supported-reference-types list item | /sync/synce-config | -| 3 | "urn:o-ran:sync:x.y" | O-RU supports GNSS | O-RU includes "GNSS" enumeration in /sync/sync-status/supported-reference-types list item | /sync/gnss-config | -| 4 | "urn:o-ran:sync:x.y" | O-RU supports the T-BC profiles in Recommendation ITU-T G.8275.1 | /sync/sync-capability/boundary-clock-supported | M-Plane activation not applicable. | -| 5 | "urn:o-ran:sync:x.y" | O-RU supports enhanced accuracy for sync as per IEEE802.1CM clause 6.4.1 | O-RU sets /sync/sync-capability/sync-t-tsc to "ENHANCED" | M-Plane activation not applicable. | - -**Table C.3-13: Optional features where support is indicated by read-only YANG leaf nodes defined in urn:o-ran:uplane-conf:x.y YANG model** - -| No | Namespace | Optional Feature | Read-only YANG leaf indicating feature support | Optional Feature Control | -|----|-----------------------------|-----------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 1 | "urn:o-ran:uplane-conf:x.y" | Section types supported by the O-RU endpoint | /user-plane-configuration/endpoint-types/supported-section-types/section-type | M-Plane activation not applicable. CUS-Plane [2] clause 7.3.1 defines use when supported. | -| 2 | "urn:o-ran:uplane-conf:x.y" | Section type extensions supported by the O-RU endpoint | /user-plane-configuration/endpoint-types/supported-section-types/supported-section-extensions | M-Plane activation not applicable. CUS-Plane [2] clause 7.3.2 defines use when supported. | -| 3 | "urn:o-ran:uplane-conf:x.y" | Supported frame structures | /user-plane-configuration/endpoint-types/supported-frame-structures | M-Plane activation not applicable. CUS-Plane [2] clause 7.5.2.13 defines use when supported. | -| 4 | "urn:o-ran:uplane-conf:x.y" | O-RU endpoint supports time managed delays | /user-plane-configuration/endpoint-types/managed-delay-support set to "MANAGED" or "BOTH" | /user-plane-configuration/low-level-rx-endpoints/non-time-managed-delay-enabled | -| 5 | "urn:o-ran:uplane-conf:x.y" | O-RU endpoint supports multiple numerologies | /user-plane-configuration/endpoint-types/multiple-numerology-supported set to "true" | M-Plane activation not applicable. CUS-Plane [2] table 7.4-3 defines use when supported. | -| 6 | "urn:o-ran:uplane-conf:x.y" | O-RU endpoint supports non-scheduled-ueid | /user-plane-configuration/endpoint-type/non-scheduled-ueid-supported set to "true" | /user-plane-configuration/low-level-tx-endpoints/non-scheduled-ueid-enabled and/or /user-plane-configuration/low-level-rx-endpoints/non-scheduled-ueid-enabled | -| 7 | "urn:o-ran:uplane-conf:x.y" | O-RU supports defined duration sleep functionality for TRX Control. | user-plane-configuration/tx-arrays/capabilities/supported-energy-saving-capabilities-dl/trx-control-capability-info/defined-duration-sleep-supported
and/or
user-plane-configuration/rx-arrays/capabilities/supported-energy-saving-capabilities-dl/trx-control-capability-info/defined-duration-sleep-supported | M-Plane activation not applicable. CUS-Plane [2] clause 16.4 defines use when supported. | -| 8 | "urn:o-ran:uplane-conf:x.y" | O-RU supports undefined duration sleep functionality for TRX Control. | user-plane-configuration/tx-arrays/capabilities/supported-energy-saving-capabilities-dl/trx-control-capability-info/undefined-duration-sleep-supported
and/or
user-plane-configuration/rx-arrays/capabilities/supported-energy-saving-capabilities-dl/trx-control-capability-info/undefined-duration-sleep-supported | M-Plane activation not applicable. CUS-Plane [2] clause 16.4 defines use when supported. | - -| | | | | | -|--|--|--|--------------------------|--| -| | | | duration-sleep-supported | | -|--|--|--|--------------------------|--| - -| | | | | | -|----|-----------------------------|---------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------| -| 9 | "urn:o-ran:uplane-conf:x.y" | O-RU supports defined duration sleep functionality for ASM. | /user-plane-configuration/tx-arrays/capabilities/supported-energy-saving-capabilities-dl/asm-capability-info/defined-duration-sleep-supported and/or /user-plane-configuration/rx-arrays/capabilities/supported-energy-saving-capabilities-dl/asm-capability-info/defined-duration-sleep-supported | M-Plane activation not applicable. CUS-Plane [2] clause 16.5 defines use when supported. | -| 10 | "urn:o-ran:uplane-conf:x.y" | O-RU supports undefined duration sleep functionality for ASM. | /user-plane-configuration/tx-arrays/capabilities/supported-energy-saving-capabilities-dl/asm-capability-info/undefined-duration-sleep-supported and/or /user-plane-configuration/rx-arrays/capabilities/supported-energy-saving-capabilities-dl/asm-capability-info/undefined-duration-sleep-supported | M-Plane activation not applicable. CUS-Plane [2] clause 16.5 defines use when supported. | -| 11 | "urn:o-ran:uplane-conf:x.y" | O-RU support for USER-GROUP-OPTIMIZATION | /user-plane-configuration/low-level-tx-endpoints/user-group-optimization-enabled-tx | M-Plane activation not applicable. CUS-Plane [2] clause 7.9.14 defines use when supported. | -| 12 | "urn:o-ran:uplane-conf:x.y" | O-RU support for USER-GROUP-OPTIMIZATION | /user-plane-configuration/low-level-rx-endpoints/user-group-optimization-enabled-rx | M-Plane activation not applicable. CUS-Plane [2] clause 7.9.14 defines use when supported. | -| 13 | "urn:o-ran:uplane-conf:x.y" | O-RU Support for Section Extension 10 beamGroupType = 11b | /user-plane-configuration/endpoint-type/se-10-bgt-11b-supported set to "true" | M-Plane activation not applicable. CUS-Plane [2] clause 7.7.10.1 defines use when supported. | -| 14 | "urn:o-ran:uplane-conf:x.y" | SINR reporting for DMRS-BF-EQ | /user-plane-configuration/endpoint-types/sinr-reporting-supported | /user-plane-configuration/low-level-rx-endpoints/sinr-reporting-enabled | -| 15 | "urn:o-ran:uplane-conf:x.y" | User group self-assembly with group id for DMRS-BF | /user-plane-configuration/endpoint-types/user-group-self-assembly-mode | /user-plane-configuration/rx-array-carriers/user-group-mode | -| 16 | "urn:o-ran:uplane-conf:x.y" | O-RU support for frequency offset | /user-plane-configuration/low-level-rx-endpoints/se26-usage-enabled | M-Plane activation not applicable. CUS-Plane [2] clause 7.7.26 defines use when supported. | -| 17 | "urn:o-ran:uplane-conf:x.y" | O-RU support for symbol reordering | /user-plane-configuration/endpoint-types/supported-symb-reorder-capabilities | /user-plane-configuration/general-config/config-symb-reorder-method or /user-plane-configuration/general- | - -| | | | | | -|----|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | config/config-symb-reorder-upSymbld-type | -| 18 | "urn:o-ran:uplane-conf:x.y" | O-RU support for rrm measurements:
MEAS-UE-TAE
MEAS-UE-LAYER-POWER
MEAS-UE-FREQ-OFFSET
MEAS-IPN-ALLOC
MEAS-IPN-UNALLOC
MEAS-ANT-DMRS-SNR
MEAS-UE-POS
MEAS-UE-RADIAL-SPEED
MEAS-POST-EQ-MU-INT | /user-plane-configuration/endpoint-types/rrm-meas-supported | /user-plane-configuration/low-level-rx-endpoints/rrm-meas-enabled
Allowed values:
MEAS-UE-TAE
MEAS-UE-LAYER-POWER
MEAS-UE-FREQ-OFFSET
MEAS-IPN-ALLOC
MEAS-IPN-UNALLOC
MEAS-ANT-DMRS-SNR
MEAS-UE-POS
MEAS-UE-RADIAL-SPEED
MEAS-POST-EQ-MU-INT | -| 19 | "urn:o-ran:uplane-conf:x.y" | O-RU supports SE-20 full PRB puncture with different sectionId | /user-plane-configuration/endpoint-types/se-20-full-prb-puncture-with-different-section-id-supported | M-Plane activation not applicable. | -| 20 | "urn:o-ran:uplane-conf:x.y" | O-RU supports cyclic delay adjustment for PDBF with pre-defined beams. | /user-plane-configuration/endpoint-types/cyclic-delay-adjustment-cap/pdbf-cyclic-delay-supported | M-Plane activation is not needed | -| 21 | "urn:o-ran:uplane-conf:x.y" | O-RU supports invalid Frequency Offset Estimate (FOE) indication | /user-plane-configuration/endpoint-types/invalid-ue-fo-estimate-indication-supported | /user-plane-configuration/low-level-rx-endpoints/ue-foe-in-current-slot-enabled | -| 22 | "urn:o-ran:uplane-conf:x.y" | O-RU supports multi-value SINR report for DFT-s-OFDM | /user-plane-configuration/endpoint-types/sinr-reporting-capabilities/multi-value-dftsofdm-sinr-report-supported | /user-plane-configuration/low-level-rx-endpoints/multi-value-dftsofdm-sinr-report-enabled | - -**Table C.3-14: Optional features where support is indicated by YANG leaf nodes defined in urn:ieee:std:802.1X:yang:ieee802-dot1x YANG model** - -| No | Namespace | Optional Feature | YANG leaf indicating feature support | Optional Feature Control | -|----|------------------------------------------|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------| -| 1 | "urn:ieee:std:802.1X:yang:ieee802-dot1x" | O-RU supports MACsec Key Agreement | /if:interfaces/if:interface/
dot1x:pae/dot1x:port-capabilities/dot1x:mka | /if:interfaces/
if:interface/dot1x:pae/
dot1x:kay:
/dot1x:enable | -| 2 | "urn:ieee:std:802.1X:yang:ieee802-dot1x" | O-RU supports MACsec | /if:interfaces/if:interface/
dot1x:pae/dot1x:port-capabilities/dot1x:macsec
and
/if:interfaces/if:interface/
dot1x:pae/dot1x:kay/
dot1x:macsec/
dot1x:capable | Controlled by enabling MACsec Key Agreement | - -## Annex D (informative): YANG module graphical representation - -### D.1 Introduction - -This clause provides a set of "tree-views" of the modules to provide a simplified graphical representation of the data models. These trees have been automatically generated using the pyang YANG validator tool [i.4]. - -### D.2 System folder - -#### D.2.1 o-ran-supervision.yang module - -The format for the supervision module is provided below. - -``` -module: o-ran-supervision - -+--rw supervision - - +--rw cu-plane-monitoring! - | +--rw configured-cu-monitoring-interval? uint8 - +--rw event-collector-monitoring {or-feat:NON-PERSISTENT-MPLANE}? - | +--rw heartbeat-interval? uint8 - | +--rw heartbeat-recipient-id* event-collector-id - +--rw per-odu-monitoring! {or-feat:SHARED-ORU-MULTI-ODU or or-feat:SHARED-ORU-MULTI-OPERATOR}? - +--rw odu-ids* [odu-id] {or-feat:SHARED-ORU-MULTI-ODU}? - | +--rw odu-id string - +--rw sro-ids-and-odu-ids* [odu-id sro-id] {or-feat:SHARED-ORU-MULTI-ODU and or-feat:SHARED-ORU-MULTI-OPERATOR}? - +--rw odu-id string - +--rw sro-id string - - rpcs: - - +---x supervision-watchdog-reset - +---w input - | +---w supervision-notification-interval? uint16 - | +---w guard-timer-overhead? uint16 - | +---w context {or-feat:SHARED-ORU-MULTI-ODU or or-feat:SHARED-ORU-MULTI-OPERATOR}? - | +---w odu-id? string {or-feat:SHARED-ORU-MULTI-ODU}? -``` - -``` - -| +---w sro-id? -> /or-user:users/user/sro-id {or-feat:SHARED-ORU-MULTI-OPERATOR}? - -+--ro output - - +--ro next-update-at? yang:date-and-time - - +--ro error-message? string - -notifications: - - +---n supervision-notification - - +--ro session-id -> /ncm:netconf-state/sessions/session/session-id {or-feat:SUPERVISION- -WITH-SESSION-ID}? - -``` - -## D.2.2 o-ran-usermgmt.yang module - -The format for the user management module is provided below. - -``` - -module: o-ran-usermgmt - -+--rw users - - +--rw user* [name] - - +--rw name nacm:user-name-type - - +--rw account-type? enumeration - - +--rw password? password-type - - +--rw ssh-public-key {feat:CLIENT-AUTH-SSH-PUBLIC-KEY}? - - | +--rw public-key-format identityref - - | +--rw public-key binary - - +--rw enabled? boolean - - +--rw sro-id* string {feat:SHARED-ORU-MULTI-OPERATOR}? - -rpcs: - - +---x chg-password - - | +---w input - - | | +---w currentPassword password-type - - | | +---w newPassword password-type - - | | +---w newPasswordConfirm password-type - - | +--ro output - - | +--ro status enumeration - - | +--ro status-message? string - - +---x chg-ssh-public-key {feat:CLIENT-AUTH-SSH-PUBLIC-KEY}? - - +---w input - -``` - -``` - -| +---w current-ssh-public-key -| | +---w public-key-format identityref -| | +---w public-key binary -| +---w new-ssh-public-key -| | +---w public-key-format identityref -| | +---w public-key binary -| +---w new-ssh-public-key-confirm -| +---w public-key-format identityref -| +---w public-key binary - -+--ro output - - +--ro status enumeration - +--ro status-message? string - -``` - -## D.2.3 o-ran-hardware.yang module - -The format for the hardware module is provided below. - -``` - -module: o-ran-hardware - - augment /hw:hardware/hw:component: - - +--ro label-content - - | +--ro model-name? boolean - - | +--ro serial-number? boolean - - +--ro product-code string - - +--rw energy-saving-enabled? boolean {ENERGYSAVING}? - - +--ro dying-gasp-support? boolean - - +--rw last-service-date? yang:date-and-time {or-feat:NON-PERSISTENT-MPLANE}? - - augment /hw:hardware/hw:component: - - +--rw o-ran-name -> /hw:hardware/component/name - - augment /hw:hardware/hw:component/hw:state: - - +--ro power-state? energysaving-state {ENERGYSAVING}? - - +--ro availability-state? availability-type - - augment /hw:hardware/hw:component: - - +--ro connector-label? string - - augment /hw:hardware-state-oper-enabled: - - +--ro availability-state? -> /hw:hardware/component/state/o-ran-hw:availability-state - {hw:hardware-state}? - - augment /hw:hardware-state-oper-disabled: - -``` - -``` -+--ro availability-state? -> /hw:hardware/component/state/o-ran-hw:availability-state -{hw:hardware-state}? -``` - -## D.2.4 o-ran-fan.yang module - -The format for the fan module is provided below. - -``` -module: o-ran-fan - - +--ro fan-tray - +--ro fan-state* [name] - +--ro name string - +--ro fan-location? uint8 - +--ro present-and-operating boolean - +--ro vendor-code? uint8 - +--ro fan-speed? percent - +--ro target-speed? uint16 - - notifications: - - +---n fan-presence-and-operating-change {feat:FAN-PRESENT-AND-OPERATING-CHANGE-SUPPORTED}? - +--ro present-and-operating -> /fan-tray/fan-state/present-and-operating - +--ro name -> /fan-tray/fan-state/name - +--ro fan-location? -> /fan-tray/fan-state/fan-location - +--ro vendor-code? -> /fan-tray/fan-state/vendor-code -``` - -## D.2.5 o-ran-fm.yang module - -The format for the fault management module is provided below. - -``` -module: o-ran-fm - - +--ro active-alarm-list - | +--ro active-alarms* [] - | | +--ro fault-id uint16 - | | +--ro fault-source string - | | +--ro affected-objects* [] - | | | +--ro name string - | | | +--ro identifier? yang:xpath1.0 - | | +--ro fault-severity enumeration - | | +--ro is-cleared boolean - | | +--ro fault-text? string -``` - -``` -| +--ro probable-cause? string -| +--ro specific-problem? string -| +--ro proposed-repair-actions? string -| +--ro event-time yang:date-and-time -| +--ro additional-information* [identifier] -| | +--ro identifier string -| | +--ro information? string -| +--ro alarm-type? enumeration -| +--ro fault-name? string - -+--rw historical-alarm-list {HISTORICAL-ALARM-LIST}? - - +--ro historical-alarms* [] - - +--ro fault-id uint16 - +--ro fault-source string - +--ro affected-objects* [] - | +--ro name string - | +--ro identifier? yang:xpath1.0 - +--ro fault-severity enumeration - +--ro is-cleared boolean - +--ro fault-text? string - +--ro probable-cause? string - +--ro specific-problem? string - +--ro proposed-repair-actions? string - +--ro event-time yang:date-and-time - +--ro additional-information* [identifier] - | +--ro identifier string - | +--ro information? string - +--ro alarm-type? enumeration - +--ro fault-name? string - -notifications: - - +---n alarm-notif - - +--ro fault-id uint16 - +--ro fault-source string - +--ro affected-objects* [] -``` - -``` - -| +--ro name string -| +--ro identifier? yang:xpath1.0 -+--ro fault-severity enumeration -+--ro is-cleared boolean -+--ro fault-text? string -+--ro probable-cause? string -+--ro specific-problem? string -+--ro proposed-repair-actions? string -+--ro event-time yang:date-and-time -+--ro additional-information* [identifier] -| +--ro identifier string -| +--ro information? string -+--ro alarm-type? enumeration -+--ro fault-name? string - -``` - -## D.2.6 o-ran-ves-subscribed-notifications.yang module - -The format for the ves subscribed notifications module is provided below. - -``` - -module: o-ran-ves-subscribed-notifications - - augment /sn:subscriptions/sn:subscription/sn:receivers/sn:receiver: - - +--rw notification-recipient inet:uri - -``` - -## D.2.7 o-ran-certificates.yang module - -The format for the certificates module is provided below. - -``` - -module: o-ran-certificates - - +--rw certificate-parameters - - +--rw cert-maps - - | +--rw cert-to-name* [id] - - | +--rw id uint32 - - | +--rw fingerprint x509c2n:tls-fingerprint - - | +--rw map-type identityref - - | +--rw name string - - +--rw cert-expiry-policy - - | +--rw cert-lcm-policy? enumeration - - | +--rw max-kur-attempts? uint16 - -``` - -``` - -| +--rw renewal-days-before-expiry? uint16 -| +--rw max-poll-attempts? uint16 -+--rw crl-policy -| +--rw crl-renewal-time-before-nextupdate? uint16 -+--rw advance-cert-expiry-alarms-config - +--rw minor-alarm-advance-time? uint16 - +--rw major-alarm-advance-time? uint16 - +--rw critical-alarm-advance-time? uint16 - -augment /ietf-sys:system/dot1x:pae-system: - +--rw credential {ietf-ts:certificates}? - +--rw ca-root? -> /ietf-ts:truststore/certificate-bags/certificate-bag/name - +--rw ca-roots* -> /ietf-ts:truststore/certificate-bags/certificate-bag/name - +--rw client-cert? -> /ietf-ks:keystore/asymmetric-keys/asymmetric-key/certificates/certificate/name - -notifications: - +---n certificate-lcm - +--ro certificate-name? -> /ietf-ks:keystore/asymmetric-keys/asymmetric-key/certificates/certificate/name - +--ro cmpv2-procedure enumeration - +--ro pki-status uint8 - +--ro pki-failure-info* uint8 - +--ro pki-free-text? string - -``` - -## D.3 Operations folder - -### D.3.1 o-ran-operations.yang module - -The format for the operations module is provided below. - -``` - -module: o-ran-operations - +--rw operational-info - +--ro declarations - | +--ro ru-instance-id? string - | +--ro supported-mplane-version? version - | +--ro supported-cusplane-version? version - -``` - -``` - -| +--ro supported-header-mechanism* [protocol] -| | +--ro protocol enumeration -| | +--ro ecpri-concatenation-support? boolean -| | +--ro protocol-version? version -| +--ro supported-common-event-header-version? version {or-feat:NON-PERSISTENT-MPLANE}? -| +--ro supported-ves-event-listener-version? version {or-feat:NON-PERSISTENT-MPLANE}? -| +--ro supported-pnf-registration-fields-version? version {or-feat:NON-PERSISTENT-MPLANE}? -| +--ro maximum-simultaneous-netconf-sessions? uint8 - -+--ro operational-state - -| +--ro restart-cause? enumeration -| +--ro restart-datetime? yang:date-and-time -| +--ro current-datetime? yang:date-and-time - -+--rw clock - -| +--rw timezone-name? timezone-name -| +--rw timezone-utc-offset? int16 - -+--rw re-call-home-no-ssh-timer? uint16 - -+--rw max-call-home-attempts? uint8 - -rpcs: - -+---x reset - -+---x restart-call-home {or-feat:CALL-HOME-REACTIVATION-SUPPORTED}? - -+---x emergency-wake-up {or-feat:TRX-CONTROL or or-feat:ADVANCED-SLEEP-MODE}? - -| +---w input - -| | +---w sro-id* -> /or-user:users/user/sro-id {or-feat:SHARED-ORU-MULTI-OPERATOR}? - -| +--ro output - -| +--ro operational-status* [index] - -| | +--ro index uint8 - -| | +--ro sro-id? -> /or-user:users/user/sro-id {or-feat:SHARED-ORU-MULTI-OPERATOR}? - -| | +--ro status? enumeration - -+---x deep-hibernate {or-feat:DEEP-HIBERNATE}? - -| +---w input - -| | +---w hibernate-time uint32 - -| +--ro output - -| +--ro status? enumeration - -``` - -``` - - +--ro error-message? string - -notifications: - - +---n emergency-wake-up-complete {or-feat:TRX-CONTROL or or-feat:ADVANCED-SLEEP-MODE}? - | +--ro sro-id? -> /or-user:users/user/sro-id {or-feat:SHARED-ORU-MULTI-OPERATOR}? - - +---n deep-hibernate-activated {or-feat:DEEP-HIBERNATE}? - +--ro hibernate-time uint32 - -``` - -## D.3.2 o-ran-file-management.yang module - -The format for the file management module is provided below. - -``` - -module: o-ran-file-management - - +--rw file-management - - +--rw security-logging {or-feat:SECURITY-LOGGING}? - - +--ro security-folder-memory-size? uint16 - - +--rw security-log-max-size? uint16 - - +--rw security-log-max-duration? uint16 - - +--rw remote-security-log-uploads* [remote-security-log-upload-path] - - +--rw remote-security-log-upload-path inet:uri - - +--rw (credentials)? - - | +--:(password) - - | | +--rw password! - - | | | +--rw password string - - | | +--rw server - - | | +--rw keys* [algorithm] - - | | | +--rw algorithm asymmetric-key-algorithm-ref - - | | | +--rw public-key? binary - - | +--:(certificate) - - | +--rw certificate! - - +--rw application-layer-credential - - +--rw appl-password? string - -rpcs: - - +---x file-upload - - | +---w input - -``` - -``` -| | +---w local-logical-file-path string -| | +---w remote-file-path string -| | +---w (credentials)? -| | | +--:(password) -| | | | +---w password! -| | | | | +---w password string -| | | | +---w server -| | | | +---w keys* [algorithm] -| | | | | +---w algorithm asymmetric-key-algorithm-ref -| | | | | +---w public-key? binary -| | | +--:(certificate) -| | | +---w certificate! -| | +---w application-layer-credential -| | +---w appl-password? string -| +--ro output -| +--ro status? enumeration -| +--ro reject-reason? string -+---x retrieve-file-list -| +---w input -| | +---w logical-path string -| | +---w file-name-filter? string -| +--ro output -| +--ro status? enumeration -| +--ro reject-reason? string -| +--ro file-list* string -+---x file-download -| +---w input -| | +---w local-logical-file-path string -| | +---w remote-file-path string -| | +---w (credentials)? -| | | +--:(password) -| | | | +---w password! -| | | | | +---w password string -| | | | +---w server -``` - -``` - -| | | | +---w keys* [algorithm] -| | | | +---w algorithm asymmetric-key-algorithm-ref -| | | | +---w public-key? binary -| | | +--:(certificate) -| | | +---w certificate! -| | +---w application-layer-credential -| | +---w appl-password? string -| +---ro output -| +---ro status? enumeration -| +---ro reject-reason? string -+---x rotate-security-log {or-feat:SECURITY-LOGGING}? - +---ro output - +---ro status? enumeration - +---ro reject-reason? string - -notifications: - - +---n file-upload-notification - | +---ro local-logical-file-path string - | +---ro remote-file-path string - | +---ro status? enumeration - | +---ro reject-reason? string - +---n file-download-event - | +---ro local-logical-file-path string - | +---ro remote-file-path string - | +---ro status? enumeration - | +---ro reject-reason? string - +---n security-log-upload-notification - +---ro remote-security-log-upload-path? inet:uri - +---ro status? enumeration - +---ro failure-reason? String - -``` - -### D.3.3 o-ran-software-management.yang module - -The format for the software management module is provided below. - -``` -module: o-ran-software-management -``` - -``` - -+--ro software-inventory - - +--ro software-slot* [name] - - | +--ro name string - | +--ro status enumeration - | +--ro active? boolean - | +--ro running? boolean - | +--ro access? enumeration - | +--ro product-code? -> /hw:hardware/component/o-ran-hw:product-code - | +--ro vendor-code? string - | +--ro build-id? string - | +--ro build-name? string - | +--ro build-version? string - | +--ro files* [name] - - | +--ro name string - | +--ro version? string - | +--ro local-path string - | +--ro integrity? enumeration - - +--ro build-content-download? empty - - +--ro integrity-check-at-download-enabled? empty {or-feat:INTEGRITY-CHECK-AT-SW-DOWNLOAD}? - - rpcs: - - +---x software-download - - | +---w input - - | | +---w remote-file-path inet:uri - | | +---w (credentials)? - - | | | +--:(password) - - | | | | +---w password! - - | | | | | +---w password string - | | | | | +---w server - - | | | | | +---w keys* [algorithm] - - | | | | | | +---w algorithm asymmetric-key-algorithm-ref - | | | | | | +---w public-key? binary - - | | | | +--:(certificate) - - | | | | +---w certificate! - -``` - -``` - -| | +---w application-layer-credential -| | +---w appl-password? string -| +---ro output -| +---ro status enumeration -| +---ro error-message? string -| +---ro notification-timeout? int32 -+---x software-install -| +---w input -| | +---w slot-name -> /software-inventory/software-slot/name -| | +---w file-names* string -| +---ro output -| +---ro status enumeration -| +---ro error-message? string -| +---ro sw-install-timeout? int32 -+---x software-activate -| +---w input -| | +---w slot-name -> /software-inventory/software-slot/name -| +---ro output -| +---ro status enumeration -| +---ro error-message? string -| +---ro notification-timeout? int32 - -notifications: - -+---n download-event -| +---ro file-name string -| +---ro status? enumeration -| +---ro error-message? string -+---n install-event -| +---ro slot-name? -> /software-inventory/software-slot/name -| +---ro status? enumeration -| +---ro error-message? string -+---n activation-event -| +---ro slot-name? -> /software-inventory/software-slot/name -| +---ro status? enumeration - -``` - -``` - -+--ro return-code? uint8 -+--ro error-message? string - -``` - -## D.3.4 o-ran-lbm.yang module - -The format for the (Ethernet) loopback module is provided below. - -``` - -module: o-ran-lbm - - +--rw md-data-definitions - - +--rw maintenance-domain* [id] - +--rw id string - +--rw name? string - +--rw md-level? md-level-type - +--rw maintenance-association* [id] - +--rw id string - +--rw name? string - +--rw component-list* [component-id] - +--rw component-id uint32 - +--rw name? string - +--rw vid* -> /if:interfaces/interface/o-ran-int:vlan-id - +--rw remote-meps* mep-id-type - +--rw maintenance-association-end-point* [mep-identifier] - +--rw mep-identifier mep-id-type - +--rw interface -> /if:interfaces/interface/name - +--rw primary-vid union - +--rw administrative-state boolean - +--ro mac-address? -> /if:interfaces/interface/o-ran-int:mac-address - +--ro loopback - +--ro replies-transmitted yang:counter32 - -``` - -## D.3.5 o-ran-udp-echo.yang module - -The format for the udp echo module is provided below. - -``` - -module: o-ran-udp-echo - - +--rw udp-echo {o-ran-int:UDPIP-BASED-CU-PLANE}? +--rw enable-udp-echo? boolean - +--rw dscp-config? enumeration - +--ro echo-replies-transmitted? uint32 - -``` - -## D.3.6 o-ran-ecpri-delay.yang module - -The format for the ecpri delay management module is provided below. - -``` - -module: o-ran-ecpri-delay - - +--rw ecpri-delay-message - - x--ro ru-compensation - | +--ro tcv2? uint32 - | +--ro tcv1? uint32 - - +--rw enable-message5? boolean - +--ro one-step-t34-supported? boolean - +--ro two-step-t34-supported? boolean - - +--rw message5-sessions - +--rw session-parameters* [session-id] - +--rw session-id uint32 - +--rw processing-element-name? -> /element:processing-elements/ru-elements/name - +--rw transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? - +--rw transport-qualified-processing-element-name? -> /element:processing-elements/additional-transport-session-type-elements[element:transport-session-type = current()/../transport-session-type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? - - +--ro flow-state - +--ro responses-transmitted? uint32 - +--ro requests-transmitted? uint32 - +--ro followups-transmitted? uint32 - -``` - -## D.3.7 o-ran-performance-management.yang module - -The format for the performance management module is provided below. - -``` - -module: o-ran-performance-management - - +--rw performance-measurement-objects - - +--ro measurement-capabilities - | +--ro transceiver-objects* [measurement-object] - | | +--ro measurement-object transceiver-meas-object-type - | | +--ro report-info* transceiver-report-info - | | +--ro function* transceiver-function - | | +--ro max-bin-count? uint16 - -``` - -``` - -| +-ro rx-window-objects* [measurement-object] -| | +-ro measurement-object rx-window-meas-object-type -| | +-ro object-unit* rx-window-object-unit -| +-ro tx-stats-objects* [measurement-object] -| | +-ro measurement-object tx-meas-object-type -| | +-ro object-unit* tx-object-unit -| +-ro epe-stats-objects* [measurement-object] -| | +-ro measurement-object epe-meas-object-type -| | +-ro component-class* identityref -| | +-ro report-info* epe-report-info -| | +-ro max-bin-count? uint16 -| +-ro symbol-rssi-stats-objects* [measurement-object] -| | +-ro measurement-object -> /performance-measurement-objects/symbol-rssi-measurement-objects/measurement-object -| | +-ro report-info* symbol-rssi-report-info -| | +-ro max-bin-count? uint16 -| +-ro shared-cell-stats-objects* [measurement-object] {feat:SHARED-CELL-STATS}? -| | +-ro measurement-object shared-cell-meas-object-type -| +-ro tssi-stats-objects* [measurement-object] -| | +-ro measurement-object tssi-meas-object-type -| | +-ro report-info* tssi-report-info -| +-ro rssi-stats-objects* [measurement-object] -| | +-ro measurement-object rssi-meas-object-type -| | +-ro report-info* rssi-report-info -| +-ro tx-antenna-stats-objects* [measurement-object] -| | +-ro measurement-object tx-antenna-meas-object-type -| | +-ro object-unit* tx-antenna-object-unit -| | +-ro report-info* tx-antenna-report-info -| | +-ro max-bin-count? uint16 -| +-ro tx-output-power-stats-objects* [measurement-object] -| | +-ro measurement-object tx-output-power-meas-object-type -| | +-ro object-unit* tx-output-power-object-unit -| | +-ro report-info* tx-output-power-report-info -| +-ro ethernet-objects* [measurement-object] -| | +-ro measurement-object ethernet-meas-object-type - -``` - -``` - -x--rw enable-SFTP-upload? boolean -+--rw enable-file-upload? boolean -+--rw enable-random-file-upload? boolean - -x--rw remote-SFTP-uploads* [remote-SFTP-upload-path] -| +--rw remote-SFTP-upload-path inet:uri -| +--rw (credentials)? -| | +--:(password) -| | | +--rw password! -| | | | +--rw password string -| | | +--rw server -| | | +--rw keys* [algorithm] -| | | | +--rw algorithm asymmetric-key-algorithm-ref -| | | | +--rw public-key? binary -| | +--:(certificate) -| | +--rw certificate! -| +--rw application-layer-credential -| +--rw appl-password? string - -+--rw remote-file-uploads* [remote-file-upload-path] -| +--rw remote-file-upload-path inet:uri -| +--rw (credentials)? -| | +--:(password) -| | | +--rw password! -| | | | +--rw password string -| | | +--rw server -| | | +--rw keys* [algorithm] -| | | | +--rw algorithm asymmetric-key-algorithm-ref -| | | | +--rw public-key? binary -| | +--:(certificate) -| | +--rw certificate! -| +--rw application-layer-credential -| +--rw appl-password? string - -+--rw transceiver-measurement-interval? uint16 -+--rw epe-measurement-interval? uint16 -+--rw rx-window-measurement-interval? uint16 - -``` - -``` - -+--rw tx-measurement-interval? uint16 -+--rw shared-cell-measurement-interval? uint16 {feat:SHARED-CELL-STATS}? -+--rw symbol-rssi-measurement-interval? uint16 -+--rw tssi-measurement-interval? uint16 -+--rw rssi-measurement-interval? uint16 -+--rw tx-antenna-measurement-interval? uint16 -+--rw tx-output-power-measurement-interval? uint16 -+--rw ethernet-measurement-interval? uint16 -+--rw notification-interval? uint16 -+--rw file-upload-interval? uint16 -x--ro max-bin-count? uint16 -+--rw transceiver-measurement-objects* [measurement-object] -| +--rw measurement-object transceiver-meas-object-type -| +--rw active? boolean -| +--rw report-info* transceiver-report-info -| +--rw object-unit enumeration -| +--rw function? transceiver-function -| +--rw bin-count? uint16 -| +--rw lower-bound? decimal64 -| +--rw upper-bound? decimal64 -| +--ro transceiver-measurement-result* [object-unit-id] -| +--ro object-unit-id -> /if:interfaces/interface/o-ran-int:port-reference/port- -number -| +--ro min -| | +--ro value? decimal64 -| | +--ro time? yang-types:date-and-time -| +--ro max -| | +--ro value? decimal64 -| | +--ro time? yang-types:date-and-time -| +--ro first -| | +--ro value? decimal64 -| | +--ro time? yang-types:date-and-time -| +--ro latest -| | +--ro value? decimal64 -| | +--ro time? yang-types:date-and-time - -``` - -``` - -| x--ro frequeny-table* uint32 -| +--ro frequency-bin-table* [bin-id] -| | +--ro bin-id uint32 -| | +--ro value? uint32 -| -+--rw rx-window-measurement-objects* [measurement-object] -| +--rw measurement-object rx-window-meas-object-type -| +--rw active? boolean -| +--rw object-unit? rx-window-object-unit -| +--rw report-info? enumeration -| +--ro (object-unit-id)? -| +--: (RU) -| | +--ro name? -> /hw:hardware/component/name -| | +--ro count uint64 -| +--: (TRANSPORT) -| | +--ro tr-measured-result* [] -| | +--ro name? -> /o-ran-elements:processing-elements/ru- -elements/name -| | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- -TYPE}? -| | +--ro transport-qualified-name? -> -/o-ran-elements:processing-elements/additional-transport-session-type-elements[o-ran- -elements:transport-session-type = current()/../transport-session-type]/ru-elements/name -{feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? -| | +--ro count uint64 -| +--: (EAXC_ID) -| +--ro eaxc-measured-result* [] -| +--ro eaxc-id? uint16 -| +--ro count uint64 -| +--ro data-direction? enumeration -| +--ro transport-name? -> /o-ran-elements:processing-elements/ru- -elements/name -| +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- -TYPE}? -| +--ro transport-qualified-name? -> -/o-ran-elements:processing-elements/additional-transport-session-type-elements[o-ran- -elements:transport-session-type = current()/../transport-session-type]/ru-elements/name -{feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? -| -+--rw tx-measurement-objects* [measurement-object] -| +--rw measurement-object tx-meas-object-type - -``` - -``` - -| +--rw active? boolean -| +--rw object-unit? tx-object-unit -| +--rw report-info? enumeration -| +--ro (object-unit-id)? -| +--: (RU) -| | +--ro name? -> /hw:hardware/component/name -| | +--ro count uint64 -| +--: (TRANSPORT) -| | +--ro tr-measured-result* [] -| | +--ro name? -> /o-ran-elements:processing-elements/ru- -elements/name -| | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- -TYPE}? -| | +--ro transport-qualified-name? -> -/o-ran-elements:processing-elements/additional-transport-session-type-elements[o-ran- -elements:transport-session-type = current()/../transport-session-type]/ru-elements/name -{feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? -| | +--ro count uint64 -| +--: (EAXC_ID) -| | +--ro eaxc-measured-result* [] -| | +--ro eaxc-id? uint16 -| | +--ro count uint64 -| | +--ro transport-name? -> /o-ran-elements:processing-elements/ru- -elements/name -| | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- -TYPE}? -| | +--ro transport-qualified-name? -> -/o-ran-elements:processing-elements/additional-transport-session-type-elements[o-ran- -elements:transport-session-type = current()/../transport-session-type]/ru-elements/name -{feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? -| +--: (EAXC_ID_DATADIRECTION) -| | +--ro eaxc-datadirection-measured-result* [] -| | +--ro eaxc-id? uint16 -| | +--ro data-direction? enumeration -| | +--ro count uint64 -| | +--ro transport-name? -> /o-ran-elements:processing-elements/ru- -elements/name -| | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- -TYPE}? - -``` - -``` - -| +--ro transport-qualified-name? -> -/o-ran-elements:processing-elements/additional-transport-session-type-elements[o-ran- -elements:transport-session-type = current()]/../transport-session-type]/ru-elements/name -{feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? - - +--rw shared-cell-measurement-objects* [measurement-object] {feat:SHARED-CELL-STATS}? - | - | +--rw measurement-object shared-cell-meas-object-type - | +--rw active? boolean - | +--rw object-unit? enumeration - | +--rw report-info? enumeration - | +--ro (object-unit-id)? - | - | +--: (TRANSPORT) - | - | +--ro pe-measured-result* [processing-elements] - | - | +--ro processing-elements -> -/o-ran-elements:processing-elements/ru-elements/name - | - | +--ro count uint64 - - +--rw epe-measurement-objects* [measurement-object] - | - | +--rw measurement-object epe-meas-object-type - | +--rw active? boolean - | +--rw object-unit? -> /hw:hardware/component/class - | +--rw report-info* epe-report-info - | +--rw bin-count? uint16 - | +--rw lower-bound? decimal64 - | +--rw upper-bound? decimal64 - | x--ro epe-measurement-result* [object-unit-id] - | | - | | +--ro object-unit-id -> /hw:hardware/component/class - | | +--ro min? decimal64 - | | +--ro max? decimal64 - | | +--ro average? decimal64 - | - | +--ro epe-measurement-resultv2* [object-unit-id] - | - | +--ro object-unit-id -> /hw:hardware/component/name - | +--ro min? decimal64 - | +--ro max? decimal64 - | +--ro average? decimal64 - | +--ro frequency-bin-table* [bin-id] - | - | +--ro bin-id uint32 - | +--ro value? uint32 - -``` - -``` - -+--rw symbol-rssi-measurement-objects* [measurement-object] -| -| +--rw measurement-object symbol-rssi-meas-object-type -| +--rw object-unit enumeration -| +--rw per-rx-array-carrier-configuration* [rx-array-carrier] -| | +--rw rx-array-carrier -> /up:user-plane-configuration/rx-array-carriers/name -| | +--rw period? uint16 -| | +--rw symbol-index* uint16 -| | +--rw active? boolean -| | +--rw report-info* symbol-rssi-report-info -| | +--rw bin-count? uint16 -| | +--rw lower-bound? int16 -| | +--rw upper-bound? int16 -| +--ro symbol-rssi-measurement-result* [object-unit-id] -| | +--ro object-unit-id -> /up:user-plane-configuration/rx-array-carriers/name -| | +--ro per-symbol-index-result* [symbol-index] -| | | +--ro symbol-index uint16 -| | | +--ro min -| | | | +--ro value? decimal64 -| | | +--ro max -| | | | +--ro value? decimal64 -| | | +--ro avg -| | | | +--ro value? decimal64 -| | | x--ro frequency-table* uint32 -| | | +--ro frequency-bin-table* [bin-id] -| | | | +--ro bin-id uint32 -| | | | +--ro value? uint32 -| -+--rw tssi-measurement-objects* [measurement-object] -| -| +--rw measurement-object tssi-meas-object-type -| +--rw active? boolean -| +--rw object-unit enumeration -| +--rw report-info* tssi-report-info -| +--ro tssi-measurement-result* [object-unit-id] -| | +--ro object-unit-id -> /up:user-plane-configuration/tx-array-carriers/name -| | +--ro per-tx-array-element-index-result* [tx-array tx-array-element] - -``` - -``` - -| +--ro tx-array -> /up:user-plane-configuration/tx-arrays/name -| +--ro tx-array-element uint32 -| +--ro avg -| | +--ro value? decimal64 -| +--ro min -| | +--ro value? decimal64 -| +--ro max -| +--ro value? decimal64 -+--rw rssi-measurement-objects* [measurement-object] -| +--rw measurement-object rssi-meas-object-type -| +--rw active? boolean -| +--rw object-unit enumeration -| +--rw report-info* rssi-report-info -| +--ro rssi-measurement-result* [object-unit-id] -| +--ro object-unit-id -> /up:user-plane-configuration/rx-array-carriers/name -| +--ro per-rx-array-element-index-result* [rx-array rx-array-element] -| +--ro rx-array -> /up:user-plane-configuration/rx-arrays/name -| +--ro rx-array-element uint32 -| +--ro avg -| | +--ro value? decimal64 -| +--ro min -| | +--ro value? decimal64 -| +--ro max -| +--ro value? decimal64 -+--rw tx-antenna-measurement-objects* [measurement-object] -| +--rw measurement-object tx-antenna-meas-object-type -| +--rw active? boolean -| +--rw report-info* tx-antenna-report-info -| +--rw object-unit tx-antenna-object-unit -| +--rw bin-count? uint16 -| +--rw lower-bound? decimal64 -| +--rw upper-bound? decimal64 -| +--ro (object-unit-id)? -| +--: (ARRAY_ELEMENT) - -``` - -``` - -| | +--ro tx-antenna-measurement-result-array-element* [tx-array tx-array-element] -| | +--ro tx-array -> /up:user-plane-configuration/tx-arrays/name -| | +--ro tx-array-element uint32 -| | +--ro avg -| | | +--ro value? decimal64 -| | +--ro std-deviation -| | | +--ro value? decimal64 -| | +--ro min -| | | +--ro value? decimal64 -| | | +--ro time? yang-types:date-and-time -| | +--ro max -| | | +--ro value? decimal64 -| | | +--ro time? yang-types:date-and-time -| | +--ro first -| | | +--ro value? decimal64 -| | | +--ro time? yang-types:date-and-time -| | +--ro latest -| | | +--ro value? decimal64 -| | | +--ro time? yang-types:date-and-time -| | +--ro frequency-bin-table* [bin-id] -| | +--ro bin-id uint32 -| | +--ro value? uint32 -| +--: (CONNECTOR_BAND) -| -| +--ro tx-antenna-measurement-result-connector-band* [related-o-ru-connector band- -| number] -| -| +--ro related-o-ru-connector -> /hw:hardware/component/name -| -| +--ro band-number -> /mcap:module-capability/band-capabilities/band- -| number -| -| +--ro avg -| -| | +--ro value? decimal64 -| -| +--ro std-deviation -| -| | +--ro value? decimal64 -| -| +--ro min -| -| | +--ro value? decimal64 -| -| | +--ro time? yang-types:date-and-time - -``` - -``` - -| +--ro max -| | +--ro value? decimal64 -| | +--ro time? yang-types:date-and-time -| +--ro first -| | +--ro value? decimal64 -| | +--ro time? yang-types:date-and-time -| +--ro latest -| | +--ro value? decimal64 -| | +--ro time? yang-types:date-and-time -| +--ro frequency-bin-table* [bin-id] -| | +--ro bin-id uint32 -| | +--ro value? uint32 - -+--rw tx-output-power-measurement-objects* [measurement-object] -| +--rw measurement-object tx-output-power- -meas-object-type -| +--rw active? boolean -| +--rw object-unit tx-output-power- -object-unit -| +--rw report-info* tx-output-power- -report-info -| +--ro (object-unit-id)? -| +--: (TX-ARRAY-CARRIER) -| | +--ro tx-output-power-measurement-result-tx-array-carrier* [tx-array-carrier] -| | | +--ro tx-array-carrier -> /up:user-plane-configuration/tx-array-carriers/name -| | +--ro avg -| | | +--ro value? decimal64 -| | +--ro min -| | | +--ro value? decimal64 -| | +--ro max -| | | +--ro value? decimal64 -| +--: (TX-ARRAY-ELEMENT) -| | +--ro tx-output-power-measurement-result-tx-array-element* [tx-array] -| | +--ro tx-array -> /up:user-plane-configuration/tx- -arrays/name -| | +--ro per-tx-array-element-index-result* [tx-array-element] -| | +--ro tx-array-element uint32 - -``` - -``` - -| | +--ro avg -| | | +--ro value? decimal64 -| | +--ro min -| | | +--ro value? decimal64 -| | +--ro max -| | | +--ro value? decimal64 -| | -| +--: (CONNECTOR) -| | +--ro tx-output-power-measurement-result-connector* [related-o-ru-connector] -| | | +--ro related-o-ru-connector -> /hw:hardware/component/name -| | | +--ro avg -| | | | +--ro value? decimal64 -| | | +--ro min -| | | | +--ro value? decimal64 -| | | +--ro max -| | | +--ro value? decimal64 -| | -| +--: (CARRIER-ARRAY-ELEMENT) -| | +--ro tx-output-power-measurement-result-carrier-array-element* [tx-array-carrier] -| | | +--ro tx-array-carrier -> /up:user-plane-configuration/tx- -array-carriers/name -| | | +--ro per-tx-array-element-index-result* [tx-array tx-array-element] -| | | +--ro tx-array -> /up:user-plane-configuration/tx-arrays/name -| | | +--ro tx-array-element uint32 -| | | +--ro avg -| | | | +--ro value? decimal64 -| | | +--ro min -| | | | +--ro value? decimal64 -| | | +--ro max -| | | +--ro value? decimal64 -| | -| +--: (ARRAY-CARRIER-CONNECTOR) -| +--ro tx-output-power-measurement-result-carrier-connector* [tx-array-carrier] -| +--ro tx-array-carrier -> /up:user-plane-configuration/tx- -array-carriers/name -| +--ro per-tx-array-connector-index-result* [related-o-ru-connector] -| +--ro related-o-ru-connector -> /hw:hardware/component/name -| +--ro avg - -``` - -``` - -| | +--ro value? decimal64 -| +--ro min -| | +--ro value? decimal64 -| +--ro max -| +--ro value? decimal64 -+--rw ethernet-measurement-objects* [measurement-object] - +--rw measurement-object ethernet-meas-object-type - +--rw active? boolean - +--rw report-info* ethernet-report-info - +--rw object-unit enumeration - +--ro ethernet-measurement-result* [object-unit-id] - +--ro object-unit-id -> /if:interfaces/interface/name - +--ro count? uint64 - -notifications: - - +---n measurement-result-stats - +--ro transceiver-stats* [measurement-object] - | +--ro measurement-object -> -/performance-measurement-objects/transceiver-measurement-objects/measurement-object - | +--ro start-time? yang-types:date-and-time - | +--ro end-time? yang-types:date-and-time - | +--ro transceiver-measurement-result* [object-unit-id] - | | +--ro object-unit-id -> /if:interfaces/interface/o-ran-int:port-reference/port- -number - | | +--ro min - | | | +--ro value? decimal64 - | | | +--ro time? yang-types:date-and-time - | | +--ro max - | | | +--ro value? decimal64 - | | | +--ro time? yang-types:date-and-time - | | +--ro first - | | | +--ro value? decimal64 - | | | +--ro time? yang-types:date-and-time - | | +--ro latest - | | | +--ro value? decimal64 - -``` - -``` - -| | | +--ro time? yang-types:date-and-time -| | x--ro frequeny-table* uint32 -| | +--ro frequency-bin-table* [bin-id] -| | +--ro bin-id uint32 -| | +--ro value? uint32 -| +--ro multiple-transceiver-measurement-result* [] -| +--ro start-time? yang-types:date-and-time -| +--ro end-time? yang-types:date-and-time -| +--ro transceiver-measurement-result* [object-unit-id] -| +--ro object-unit-id -> -/if:interfaces/interface/o-ran-int:port-reference/port-number -| +--ro min -| | +--ro value? decimal64 -| | +--ro time? yang-types:date-and-time -| +--ro max -| | +--ro value? decimal64 -| | +--ro time? yang-types:date-and-time -| +--ro first -| | +--ro value? decimal64 -| | +--ro time? yang-types:date-and-time -| +--ro latest -| | +--ro value? decimal64 -| | +--ro time? yang-types:date-and-time -| x--ro frequeny-table* uint32 -| +--ro frequency-bin-table* [bin-id] -| +--ro bin-id uint32 -| +--ro value? uint32 -+--ro rx-window-stats* [measurement-object] -| +--ro measurement-object -> /performance-measurement-objects/rx- -window-measurement-objects/measurement-object -| +--ro start-time? yang-types:date-and-time -| +--ro end-time? yang-types:date-and-time -| +--ro (object-unit-id)? -| | +--:(RU) -| | | +--ro name? -> /hw:hardware/component/name - -``` - -``` - -| | | +--ro count uint64 -| | +--:(TRANSPORT) -| | | +--ro tr-measured-result* [] -| | | +--ro name? -> /o-ran-elements:processing-elements/ru- -elements/name -| | | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- -TYPE}? -| | | +--ro transport-qualified-name? -> -/o-ran-elements:processing-elements/additional-transport-session-type-elements[o-ran- -elements:transport-session-type = current()/../transport-session-type]/ru-elements/name -{feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? -| | | +--ro count uint64 -| | +--:(EAXC_ID) -| | +--ro eaxc-measured-result* [] -| | +--ro eaxc-id? uint16 -| | +--ro count uint64 -| | +--ro data-direction? enumeration -| | +--ro transport-name? -> /o-ran-elements:processing-elements/ru- -elements/name -| | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- -TYPE}? -| | +--ro transport-qualified-name? -> -/o-ran-elements:processing-elements/additional-transport-session-type-elements[o-ran- -elements:transport-session-type = current()/../transport-session-type]/ru-elements/name -{feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? -| +--ro multiple-rx-window-measurement-result* [] -| +--ro start-time? yang-types:date-and-time -| +--ro end-time? yang-types:date-and-time -| +--ro (object-unit-id)? -| +--:(RU) -| | +--ro name? -> /hw:hardware/component/name -| | +--ro count uint64 -| | +--:(TRANSPORT) -| | +--ro tr-measured-result* [] -| | | +--ro name? -> /o-ran-elements:processing-elements/ru- -elements/name -| | | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT- -SESSION-TYPE}? -| | | +--ro transport-qualified-name? -> -/o-ran-elements:processing-elements/additional-transport-session-type-elements[o-ran- - -``` - -``` - -elements:transport-session-type = current()/../transport-session-type]/ru-elements/name -{feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? - -| | +--ro count uint64 -| +---:(EAXC_ID) -| +--ro eaxc-measured-result* [] -| +--ro eaxc-id? uint16 -| +--ro count uint64 -| +--ro data-direction? enumeration -| +--ro transport-name? -> /o-ran-elements:processing-elements/ru-elements/name -| +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? -| +--ro transport-qualified-name? -> /o-ran-elements:processing-elements/additional-transport-session-type-elements[o-ran-elements:transport-session-type = current()/../transport-session-type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? - -+--ro tx-stats* [measurement-object] - -| +--ro measurement-object -> /performance-measurement-objects/tx-measurement-objects/measurement-object -| +--ro start-time? yang-types:date-and-time -| +--ro end-time? yang-types:date-and-time -| +--ro (object-unit-id)? -| | +---:(RU) -| | | +--ro name? -> /hw:hardware/component/name -| | | +--ro count uint64 -| | +---:(TRANSPORT) -| | | +--ro tr-measured-result* [] -| | | +--ro name? -> /o-ran-elements:processing-elements/ru-elements/name -| | | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? -| | | +--ro transport-qualified-name? -> /o-ran-elements:processing-elements/additional-transport-session-type-elements[o-ran-elements:transport-session-type = current()/../transport-session-type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? -| | | +--ro count uint64 -| | +---:(EAXC_ID) -| | | +--ro eaxc-measured-result* [] -| | | +--ro eaxc-id? uint16 -| | | +--ro count uint64 - -``` - -``` - -| | | +---ro transport-name? -> /o-ran-elements:processing-elements/ru- -elements/name - -| | | +---ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- -TYPE}? - -| | | +---ro transport-qualified-name? -> -/o-ran-elements:processing-elements/additional-transport-session-type-elements[o-ran- -elements:transport-session-type = current()/../transport-session-type]/ru-elements/name -{feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? - -| | +---:(EAXC_ID_DATADIRECTION) -| | +---ro eaxc-datadirection-measured-result* [] -| | +---ro eaxc-id? uint16 -| | +---ro data-direction? enumeration -| | +---ro count uint64 -| | +---ro transport-name? -> /o-ran-elements:processing-elements/ru- -elements/name - -| | +---ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT-SESSION- -TYPE}? - -| | +---ro transport-qualified-name? -> -/o-ran-elements:processing-elements/additional-transport-session-type-elements[o-ran- -elements:transport-session-type = current()/../transport-session-type]/ru-elements/name -{feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? - -| +---ro multiple-tx-measurement-result* [] -| +---ro start-time? yang-types:date-and-time -| +---ro end-time? yang-types:date-and-time -| +---ro (object-unit-id)? -| +---:(RU) -| | +---ro name? -> /hw:hardware/component/name -| | +---ro count uint64 -| +---:(TRANSPORT) -| | +---ro tr-measured-result* [] -| | +---ro name? -> /o-ran-elements:processing-elements/ru- -elements/name -| | +---ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT- -SESSION-TYPE}? -| | +---ro transport-qualified-name? -> -/o-ran-elements:processing-elements/additional-transport-session-type-elements[o-ran- -elements:transport-session-type = current()/../transport-session-type]/ru-elements/name -{feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? -| | +---ro count uint64 -| +---:(EAXC_ID) -| | +---ro eaxc-measured-result* [] - -``` - -``` - -| | +--ro eaxc-id? uint16 -| | +--ro count uint64 -| | +--ro transport-name? -> /o-ran-elements:processing-elements/ru- -elements/name -| | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT- -SESSION-TYPE}? -| | +--ro transport-qualified-name? -> -/o-ran-elements:processing-elements/additional-transport-session-type-elements[o-ran- -elements:transport-session-type = current()]/../transport-session-type]/ru-elements/name -{feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? -| +---: (EAXC_ID_DATADIRECTION) -| +--ro eaxc-datadirection-measured-result* [] -| | +--ro eaxc-id? uint16 -| | +--ro data-direction? enumeration -| | +--ro count uint64 -| | +--ro transport-name? -> /o-ran-elements:processing-elements/ru- -elements/name -| | +--ro transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT- -SESSION-TYPE}? -| | +--ro transport-qualified-name? -> -/o-ran-elements:processing-elements/additional-transport-session-type-elements[o-ran- -elements:transport-session-type = current()]/../transport-session-type]/ru-elements/name -{feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? -x--ro epe-stats -| +--ro start-time? yang-types:date-and-time -| +--ro end-time? yang-types:date-and-time -| x--ro epe-measurement-result* [object-unit-id] -| | +--ro object-unit-id -> /hw:hardware/component/class -| | +--ro min? decimal64 -| | +--ro max? decimal64 -| | +--ro average? decimal64 -| +--ro epe-measurement-resultv2* [object-unit-id] -| | +--ro object-unit-id -> /hw:hardware/component/name -| | +--ro min? decimal64 -| | +--ro max? decimal64 -| | +--ro average? decimal64 -| | +--ro frequency-bin-table* [bin-id] -| | | +--ro bin-id uint32 -| | | +--ro value? uint32 - -``` - -``` - -+--ro epe-statistics* [measurement-object] - -| +--ro measurement-object -> /performance-measurement-objects/epe- -measurement-objects/measurement-object - -| +--ro start-time? yang-types:date-and-time - -| +--ro end-time? yang-types:date-and-time - -| x--ro epe-measurement-result* [object-unit-id] - -| | +--ro object-unit-id -> /hw:hardware/component/class - -| | +--ro min? decimal64 - -| | +--ro max? decimal64 - -| | +--ro average? decimal64 - -| +--ro epe-measurement-resultv2* [object-unit-id] - -| | +--ro object-unit-id -> /hw:hardware/component/name - -| | +--ro min? decimal64 - -| | +--ro max? decimal64 - -| | +--ro average? decimal64 - -| | +--ro frequency-bin-table* [bin-id] - -| | | +--ro bin-id uint32 - -| | | +--ro value? uint32 - -| +--ro multiple-epe-measurement-result* [] - -| | +--ro start-time? yang-types:date-and-time - -| | +--ro end-time? yang-types:date-and-time - -| | x--ro epe-measurement-result* [object-unit-id] - -| | | +--ro object-unit-id -> /hw:hardware/component/class - -| | | +--ro min? decimal64 - -| | | +--ro max? decimal64 - -| | | +--ro average? decimal64 - -| | +--ro epe-measurement-resultv2* [object-unit-id] - -| | | +--ro object-unit-id -> /hw:hardware/component/name - -| | | +--ro min? decimal64 - -| | | +--ro max? decimal64 - -| | | +--ro average? decimal64 - -| | | +--ro frequency-bin-table* [bin-id] - -| | | | +--ro bin-id uint32 - -| | | | +--ro value? uint32 - -+--ro symbol-rssi-stats* [measurement-object] - -``` - -``` - -| +--ro measurement-object -> -/performance-measurement-objects/symbol-rssi-measurement-objects/measurement-object -| +--ro start-time? yang-types:date-and-time -| +--ro end-time? yang-types:date-and-time -| +--ro symbol-rssi-measurement-result* [object-unit-id] -| | +--ro object-unit-id -> /up:user-plane-configuration/rx-array-carriers/name -| | +--ro per-symbol-index-result* [symbol-index] -| | | +--ro symbol-index uint16 -| | | +--ro min -| | | | +--ro value? decimal64 -| | | +--ro max -| | | | +--ro value? decimal64 -| | | +--ro avg -| | | | +--ro value? decimal64 -| | | x--ro frequency-table* uint32 -| | | +--ro frequency-bin-table* [bin-id] -| | | | +--ro bin-id uint32 -| | | | +--ro value? uint32 -| +--ro multiple-symbol-rssi-measurement-result* [] -| | +--ro start-time? yang-types:date-and-time -| | +--ro end-time? yang-types:date-and-time -| | +--ro symbol-rssi-measurement-result* [object-unit-id] -| | | +--ro object-unit-id -> -/up:user-plane-configuration/rx-array-carriers/name -| | | +--ro per-symbol-index-result* [symbol-index] -| | | | +--ro symbol-index uint16 -| | | | +--ro min -| | | | | +--ro value? decimal64 -| | | | +--ro max -| | | | | +--ro value? decimal64 -| | | | +--ro avg -| | | | | +--ro value? decimal64 -| | | | x--ro frequency-table* uint32 -| | | | +--ro frequency-bin-table* [bin-id] -| | | | | +--ro bin-id uint32 - -``` - -``` - -| +--ro value? uint32 - -+--ro shared-cell-stats* [measurement-object] {feat:SHARED-CELL-STATS}? - -| +--ro measurement-object -> -/performance-measurement-objects/shared-cell-measurement-objects/measurement-object - -| +--ro multiple-shared-cell-measurement-result* [] - -| | +--ro start-time? yang-types:date-and-time - -| | +--ro end-time? yang-types:date-and-time - -| | +--ro (object-unit-id)? - -| | +--: (TRANSPORT) - -| | | +--ro pe-measured-result* [processing-elements] - -| | | | +--ro processing-elements -> /o-ran-elements:processing-elements/ru- -elements/name - -| | | | +--ro count uint64 - -+--ro tssi-stats* [measurement-object] - -| +--ro measurement-object -> /performance-measurement-objects/tssi-measurement- -objects/measurement-object - -| +--ro tssi-measurement-result* [] - -| | +--ro start-time? yang-types:date-and-time - -| | +--ro end-time? yang-types:date-and-time - -| | +--ro tssi-measurement-result* [object-unit-id] - -| | | +--ro object-unit-id -> /up:user-plane-configuration/tx-array- -carriers/name - -| | | +--ro per-tx-array-element-index-result* [tx-array tx-array-element] - -| | | | +--ro tx-array -> /up:user-plane-configuration/tx-arrays/name - -| | | | +--ro tx-array-element uint32 - -| | | | +--ro avg - -| | | | | +--ro value? decimal64 - -| | | | +--ro min - -| | | | | +--ro value? decimal64 - -| | | | +--ro max - -| | | | | +--ro value? decimal64 - -+--ro rssi-stats* [measurement-object] - -| +--ro measurement-object -> /performance-measurement-objects/rssi-measurement- -objects/measurement-object - -| +--ro rssi-measurement-result* [] - -| | +--ro start-time? yang-types:date-and-time - -| | +--ro end-time? yang-types:date-and-time - -``` - -``` - -| +--ro rssi-measurement-result* [object-unit-id] -| -| +--ro object-unit-id -> /up:user-plane-configuration/rx-array-carriers/name -| -| +--ro per-rx-array-element-index-result* [rx-array rx-array-element] -| -| +--ro rx-array -> /up:user-plane-configuration/rx-arrays/name -| -| +--ro rx-array-element uint32 -| -| +--ro avg -| -| | +--ro value? decimal64 -| -| +--ro min -| -| | +--ro value? decimal64 -| -| +--ro max -| -| +--ro value? decimal64 -| -+--ro tx-antenna-stats* [measurement-object] -| -| +--ro measurement-object -> /performance-measurement-objects/tx-antenna-measurement-objects/measurement-object -| -| +--ro tx-antenna-measurement-result* [] -| -| +--ro start-time? yang-types:date-and-time -| -| +--ro end-time? yang-types:date-and-time -| -| +--ro (object-unit-id)? -| -| +---: (ARRAY_ELEMENT) -| -| | +--ro tx-antenna-measurement-result-array-element* [tx-array tx-array-element] -| -| | +--ro tx-array -> /up:user-plane-configuration/tx-arrays/name -| -| | +--ro tx-array-element uint32 -| -| | +--ro avg -| -| | | +--ro value? decimal64 -| -| | +--ro std-deviation -| -| | | +--ro value? decimal64 -| -| | +--ro min -| -| | | +--ro value? decimal64 -| -| | | +--ro time? yang-types:date-and-time -| -| | +--ro max -| -| | | +--ro value? decimal64 -| -| | | +--ro time? yang-types:date-and-time -| -| | +--ro first -| -| | | +--ro value? decimal64 - -``` - -``` - -| | | +--ro time? yang-types:date-and-time -| | +--ro latest -| | | +--ro value? decimal64 -| | | +--ro time? yang-types:date-and-time -| | +--ro frequency-bin-table* [bin-id] -| | | +--ro bin-id uint32 -| | | +--ro value? uint32 -| +--:(CONNECTOR_BAND) -| +--ro tx-antenna-measurement-result-connector-band* [related-o-ru-connector band- -number] -| | +--ro related-o-ru-connector -> /hw:hardware/component/name -| | +--ro band-number -> -/mcap:module-capability/band-capabilities/band-number -| | +--ro avg -| | | +--ro value? decimal64 -| | +--ro std-deviation -| | | +--ro value? decimal64 -| | +--ro min -| | | +--ro value? decimal64 -| | | +--ro time? yang-types:date-and-time -| | +--ro max -| | | +--ro value? decimal64 -| | | +--ro time? yang-types:date-and-time -| | +--ro first -| | | +--ro value? decimal64 -| | | +--ro time? yang-types:date-and-time -| | +--ro latest -| | | +--ro value? decimal64 -| | | +--ro time? yang-types:date-and-time -| | +--ro frequency-bin-table* [bin-id] -| | | +--ro bin-id uint32 -| | | +--ro value? uint32 -+--ro tx-output-power-stats* [measurement-object] -| +--ro measurement-object -> /performance-measurement-objects/tx-output- -power-measurement-objects/measurement-object -| +--ro tx-output-power-measurement-result* [] - -``` - -``` - -| +--ro start-time? yang- -types:date-and-time -| +--ro end-time? yang- -types:date-and-time -| +--ro (object-unit-id)? -| +---: (TX-ARRAY-CARRIER) -| | +--ro tx-output-power-measurement-result-tx-array-carrier* [tx-array-carrier] -| | +--ro tx-array-carrier --> -/up:user-plane-configuration/tx-array-carriers/name -| | +--ro avg -| | | +--ro value? decimal64 -| | +--ro min -| | | +--ro value? decimal64 -| | +--ro max -| | | +--ro value? decimal64 -| +---: (TX-ARRAY-ELEMENT) -| | +--ro tx-output-power-measurement-result-tx-array-element* [tx-array] -| | +--ro tx-array --> /up:user-plane-configuration/tx- -arrays/name -| | +--ro per-tx-array-element-index-result* [tx-array-element] -| | | +--ro tx-array-element uint32 -| | | +--ro avg -| | | | +--ro value? decimal64 -| | | +--ro min -| | | | +--ro value? decimal64 -| | | +--ro max -| | | | +--ro value? decimal64 -| +---: (CONNECTOR) -| | +--ro tx-output-power-measurement-result-connector* [related-o-ru-connector] -| | +--ro related-o-ru-connector --> /hw:hardware/component/name -| | +--ro avg -| | | +--ro value? decimal64 -| | +--ro min -| | | +--ro value? decimal64 -| | +--ro max -| | | +--ro value? decimal64 - -``` - -``` - -| +---: (CARRIER-ARRAY-ELEMENT) -| -| | +---ro tx-output-power-measurement-result-carrier-array-element* [tx-array- -carrier] -| -| | +---ro tx-array-carrier -> /up:user-plane-configuration/tx- -array-carriers/name -| -| | +---ro per-tx-array-element-index-result* [tx-array tx-array-element] -| -| | | +---ro tx-array -> /up:user-plane-configuration/tx-arrays/name -| -| | | +---ro tx-array-element uint32 -| -| | | +---ro avg -| -| | | | +---ro value? decimal64 -| -| | | +---ro min -| -| | | | +---ro value? decimal64 -| -| | | +---ro max -| -| | | +---ro value? decimal64 -| -| +---: (ARRAY-CARRIER-CONNECTOR) -| -| +---ro tx-output-power-measurement-result-carrier-connector* [tx-array-carrier] -| -| +---ro tx-array-carrier -> -/up:user-plane-configuration/tx-array-carriers/name -| -| +---ro per-tx-array-connector-index-result* [related-o-ru-connector] -| -| | +---ro related-o-ru-connector -> /hw:hardware/component/name -| -| | +---ro avg -| -| | | +---ro value? decimal64 -| -| | +---ro min -| -| | | +---ro value? decimal64 -| -| | +---ro max -| -| | +---ro value? decimal64 -| -+---ro ethernet-stats* [measurement-object] -| -+---ro measurement-object -> /performance-measurement-objects/ethernet- -measurement-objects/measurement-object -| -+---ro ethernet-measurement-results* [] -| -+---ro start-time? yang-types:date-and-time -| -+---ro end-time? yang-types:date-and-time -| -+---ro ethernet-measurement-result* [object-unit-id] -| -+---ro object-unit-id -> /if:interfaces/interface/name -| -+---ro count? uint64 - -``` - -## D.3.8 o-ran-uplane-conf.yang module - -The format for the userplane configuration module is provided below. - -``` - -module: o-ran-uplane-conf - - +--rw user-plane-configuration - - +--rw low-level-tx-links* [name] - - | +--rw name string - - | +--rw sro-id? -> /or-user:users/user/sro-id {feat:SHARED- -ORU-MULTI-OPERATOR}? - - | +--rw processing-element -> /o-ran-pe:processing-elements/ru- -elements/name - - | +--rw transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT- -SESSION-TYPE}? - - | +--rw transport-qualified-processing-element? -> /o-ran-pe:processing-elements/additional- -transport-session-type-elements[o-ran-pe:transport-session-type = current()]/../transport-session- -type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? - - | +--rw tx-array-carrier -> /user-plane-configuration/tx-array- -carriers/name - - | +--rw low-level-tx-endpoint -> /user-plane-configuration/low-level-tx- -endpoints/name - - +--rw low-level-rx-links* [name] - - | +--rw name string - - | +--rw sro-id? -> /or-user:users/user/sro-id {feat:SHARED- -ORU-MULTI-OPERATOR}? - - | +--rw processing-element -> /o-ran-pe:processing-elements/ru- -elements/name - - | +--rw transport-session-type? enumeration {feat:MULTIPLE-TRANSPORT- -SESSION-TYPE}? - - | +--rw transport-qualified-processing-element? -> /o-ran-pe:processing-elements/additional- -transport-session-type-elements[o-ran-pe:transport-session-type = current()]/../transport-session- -type]/ru-elements/name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? - - | +--rw rx-array-carrier -> /user-plane-configuration/rx-array- -carriers/name - - | +--rw low-level-rx-endpoint -> /user-plane-configuration/low-level-rx- -endpoints/name - - | +--rw user-plane-uplink-marking? -> /o-ran-pe:processing-elements/enhanced- -uplane-mapping/uplane-mapping/up-marking-name - - | +--rw enhanced-user-plane-uplink-marking? -> /o-ran-pe:processing-elements/additional- -transport-session-type-elements[o-ran-pe:transport-session-type = current()]/../transport-session- -type]/enhanced-uplane-mapping/uplane-mapping/up-marking-name {feat:MULTIPLE-TRANSPORT-SESSION-TYPE}? - - +--ro endpoint-types* [id] - - | +--ro id uint16 - - | +--ro supported-section-types* [section-type] - -``` - -``` - -| | +--ro section-type uint8 -| | +--ro supported-section-extensions* uint8 -| +--ro st4-supported-commands* [st4-command-type] {feat:ST4-SLOT-CONFIG-MSG-SUPPORT}? -| | +--ro st4-command-type enumeration -| | +--ro st4-command-scope-params* [cmd-scope] -| | | +--ro cmd-scope enumeration -| | | +--ro st4-reception-bitmask? uint16 -| x--ro st4-reception-mask* [cmd-scope] {feat:ST4-SLOT-CONFIG-MSG-SUPPORT}? -| | +--ro cmd-scope enumeration -| | +--ro st4-reception-bitmask? uint16 -| +--ro supported-frame-structures* uint8 -| +--ro managed-delay-support? enumeration -| +--ro multiple-numerology-supported? boolean -| +--ro max-numerology-change-duration? uint16 -| +--ro max-control-sections-per-data-section? uint8 -| +--ro max-sections-per-symbol? uint16 -| +--ro max-sections-per-slot? uint16 -| +--ro max-highest-priority-sections-per-slot? uint16 -| x--ro max-remasks-per-section-id? uint8 -| +--ro max-uplane-section-header-per-symbol? uint16 -| +--ro max-uplane-section-header-per-slot? uint16 -| +--ro max-beams-per-symbol? uint16 -| +--ro max-beams-per-slot? uint16 -| +--ro max-total-beamids-per-symbol? uint16 -| +--ro max-total-beamids-per-slot? uint16 -| +--ro max-beams-per-symbol-multiple-beamid-tables? uint32 - {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? -| +--ro max-beams-per-slot-multiple-beamid-tables? uint32 - {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? -| +--ro max-total-beamids-per-symbol-multiple-beamid-tables? uint32 - {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? -| +--ro max-total-beamids-per-slot-multiple-beamid-tables? uint32 - {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? -| +--ro max-beam-updates-per-slot? uint16 -| +--ro max-beam-updates-per-symbol? uint16 -| +--ro max-prb-per-symbol? uint16 - -``` - -``` - -| +--ro max-prb-ranges-per-symbol? uint32 -| +--ro max-mcscaleremask-per-prb? uint16 -| +--ro max-prb-ranges-per-sec-ext-12? uint16 -| +--ro max-freq-hops-per-sec-ext-13? uint16 -| +--ro max-prb-blks-per-sec-ext-23? uint16 {feat:SE23- -PRB-BLOCK-MODE-SUPPORT}? -| -| +--ro prb-capacity-allocation-granularity* uint16 -| -| +--ro max-numerologies-per-symbol? uint16 -| -| +--ro static-transmission-window-control-supported? boolean -{feat:STATIC-TRANSMISSION-WINDOW-CONTROL}? -| -| +--ro uniformly-distributed-transmission-supported? boolean -{feat:STATIC-TRANSMISSION-WINDOW-CONTROL and feat:UNIFORMLY-DISTRIBUTED-TRANSMISSION}? -| -| +--ro ordered-transmission-supported? boolean -{feat:ORDERED-TRANSMISSION}? -| -| +--ro dynamic-transmission-window-control-supported? boolean -{feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL}? -| -| +--ro dynamic-transmission-window-control-per-section-supported? boolean -{feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL}? -| -| +--ro dynamic-uniformly-distributed-transmission-supported? boolean -{feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL and feat:UNIFORMLY-DISTRIBUTED-TRANSMISSION}? -| -| +--ro dynamic-uniformly-distributed-transmission-per-section-supported? boolean -| -| +--ro transmission-buffering-capacity* [] {feat:STATIC-TRANSMISSION-WINDOW-CONTROL or -feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL}? -| -| | +--ro iq-bitwidth? uint8 -| -| | +--ro compression-type compression-type-def -| -| | x--ro bitwidth? uint8 -| -| | +--ro compression-method? compression-method-def -| -| | x--ro (compression-format)? -| -| | | +--: (no-compresison) -| -| | | +--: (block-floating-point) -| -| | | | +--ro exponent? uint8 -| -| | | +--: (block-floating-point-selective-re-sending) -| -| | | | +--ro sres-exponent? uint8 -| -| | | +--: (block-scaling) -| -| | | | +--ro block-scalar? uint8 -| -| | | +--: (u-law) -| -| | | | +--ro comp-bit-width? uint8 -| -| | | | +--ro comp-shift? uint8 - -``` - -``` - -| | | +--: (beam-space-compression) -| | | | +--ro active-beam-space-coeficient-mask* uint8 -| | | | +--ro block-scaler? uint8 -| | | +--: (modulation-compression) -| | | | +--ro csf? uint8 -| | | | +--ro mod-comp-scaler? uint16 -| | | +--: (modulation-compression-selective-re-sending) -| | | | +--ro sres-csf? uint8 -| | | | +--ro sres-mod-comp-scaler? uint16 -| | +--ro max-buffered-prbs? uint32 -| | +--ro max-buffered-symbols? uint32 -| +--ro cplane-message-processing-limits-required? boolean -{feat:CPLANE-MESSAGE-PROCESSING-LIMITS}? -| +--ro max-beams-per-cplane-message? uint16 -{feat:CPLANE-MESSAGE-PROCESSING-LIMITS}? -| +--ro max-highest-priority-sec-per-cplane-message? uint16 -{feat:CPLANE-MESSAGE-PROCESSING-LIMITS}? -| +--ro max-beams-per-slot-with-cplane-limits? uint16 -{feat:CPLANE-MESSAGE-PROCESSING-LIMITS}? -| +--ro max-highest-priority-sections-per-slot-with-cplane-limits? uint16 -{feat:CPLANE-MESSAGE-PROCESSING-LIMITS}? -| +--ro max-num-se22-per-cplane-message? uint16 -{feat:CPLANE-MESSAGE-PROCESSING-LIMITS}? -| +--ro max-prb-ranges-per-hp-section-sec-ext-12? uint16 -{feat:CPLANE-MESSAGE-PROCESSING-LIMITS}? -| +--ro uplane-message-processing-limits-required? boolean -{feat:UPLANE-MESSAGE-PROCESSING-LIMITS}? -| +--ro max-section-headers-per-uplane-message? uint16 -{feat:UPLANE-MESSAGE-PROCESSING-LIMITS, feat:UPLANE-MESSAGE-PROCESSING-LIMITS}? -| +--ro beam-update-contention-control-limits-required? boolean -{feat:BEAM-UPDATE-CONTENTION-CONTROL}? -| +--ro max-beams-per-symbol-with-beam-contention-control? uint16 {feat:BEAM-UPDATE-CONTENTION-CONTROL}? -| +--ro max-beams-updates-per-symbol-with-beam-contention-control? uint16 {feat:BEAM-UPDATE-CONTENTION-CONTROL}? -| +--ro max-ack-nack-per-symbol? uint16 -| +--ro non-scheduled-ueid-supported? boolean {feat:NON-SCHEDULED-UEID}? -| +--ro se11-continuity-flag-supported? boolean -{feat:SE11-WITH-CONTINUITY-BIT-SUPPORT}? - -``` - -``` - -| +--ro se-23-prb-block-mode-supported? boolean -{feat:SE23-PRB-BLOCK-MODE-SUPPORT}? - -| +--ro user-group-optimization-supported? boolean -{feat:USER-GROUP-OPTIMIZATION}? - -| +--ro se-20-multi-sd-punc-pattern-supported? boolean -{feat:SE20-MULTI-SD-PUNC-PATTERN-SUPPORT}? - -| +--ro supported-configuration-combinations* [combination-id] -| | +--ro combination-id uint32 -| | +--ro set* [set-id] -| | | +--ro set-id uint32 -| | | +--ro max-overlapping-instances? uint32 -| | | +--ro config* [config-id] -| | | | +--ro config-id uint32 -| | | | +--ro scs* mcap:scs-config-type -| | | | +--ro carrier-types* enumeration -| | | | +--ro filter-pass-bandwidth? uint64 -| | | | +--ro max-prb-range? uint32 -| | | | +--ro center-from-freqoffset? boolean -| | | | +--ro supported-filter-indices* uint32 -| +--ro center-from-freqoffset-supported? boolean -| +--ro supported-filter-indices* uint32 -| +--ro bf-profile-group* -> /user-plane- -configuration/endpoint-bf-profile-group/bf-profile-id {feat:BF-DELAY-PROFILE}? - -| +--ro supported-pass-band-for-filterindex09-per-scs* [scs] -| | +--ro scs mcap:scs-config-type -| | +--ro supported-max-num-msg-for-filterindex0x9-per-scs? uint16 -| | +--ro filter-bandwidth* uint64 -| +--ro se24-dmrs-capabilities {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? -| | +--ro supported-entry-types* uint8 -| | +--ro ue-time-partial-overlap-supported? boolean -| | +--ro ue-freq-partial-overlap-supported? boolean -| | +--ro max-user-groups-per-ue-in-time? uint16 -| | +--ro different-transform-precoding-in-user-group-supported? boolean -| | +--ro different-cdm-without-data-in-user-group-supported? boolean -| | +--ro max-dmrs-configs-per-user-group-incl-first-last-prb? uint32 -| | +--ro max-dmrs-configs-per-user-group-excl-first-last-prb? uint32 - -``` - -``` - -| | +--ro max-user-groups-per-slot? uint32 -| | +--ro max-entries-per-slot? uint32 -| | +--ro max-meas-ue-pos-per-slot? uint8 {feat:RRM-MEAS- -REPORTING}? -| | +--ro transform-precoding-enabled -| | | +--ro dmrs-mask-capability* [id] -| | | | +--ro id uint16 -| | | | +--ro dmrs-symbol-mask* uint16 -| | | | +--ro max-dmrs-ant-port-number? uint32 -| | | | +--ro max-user-data-layers? uint32 -| | | +--ro low-papr-config* [id] -| | | | +--ro id uint16 -| | | | +--ro low-papr-type? uint16 -| | | | +--ro hopping-mode? uint16 -| | +--ro transform-precoding-disabled -| | | +--ro dmrs-mask-capability* [id] -| | | | +--ro id uint16 -| | | | +--ro dmrs-symbol-mask* uint16 -| | | | +--ro max-dmrs-ant-port-number? uint32 -| | | | +--ro max-user-data-layers? uint32 -| | | +--ro dmrs-config* [id] -| | | | +--ro id uint16 -| | | | +--ro d-type? uint16 -| | | | +--ro pusch-dmrs-muxing-supported? boolean -| | +--ro sinr-reporting-supported? boolean -{feat:DMRS-BF-EQ}? -| | +--ro sinr-reporting-capabilities {feat:DMRS-BF-EQ}? -| | +--ro simultaneous-sinr-and-dmrs-sending-supported? boolean -| | +--ro oru-control-sinr-time-resolution-supported? boolean {feat:ORU-CONTROL-SINR- -TIME-RESOLUTION}? -| | +--ro supported-sinr-resolutions* [id] -| | | +--ro id uint16 -| | | +--ro sinr-max-data-layers? uint8 -| | | +--ro sinr-per-prb* uint8 -| | | +--ro sinr-slot-mask* uint16 -| | +--ro supported-sinr-reference-level - -``` - -``` - -| | | +--ro sinr-reference-level-min? decimal64 -| | | +--ro sinr-reference-level-max? decimal64 -| | +--ro supported-sinr-compression-methods* [id] -| | | +--ro id uint16 -| | | +--ro sinr-bitwidth? uint8 -| | | +--ro sinr-compression-method? sinr-compression-method-def -| | | +--ro sinr-block-size? uint8 -| | +--ro dynamic-sinr-per-prb-supported? boolean {feat:DYNAMIC-SINR-PER-PRB}? -| | +--ro diff-freq-resolutions-supported? boolean {feat:DYNAMIC-SINR-PER-PRB}? -| | +--ro multi-value-dftsofdm-sinr-report-supported? boolean {feat:DMRS-BF-EQ}? -| | +--ro supported-symb-reorder-capabilities {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? -| | | +--ro supported-symb-reorder-capability* symb-reorder-capability -| | | +--ro max-num-symbol-reordering-pattern-per-slot? uint16 -| | | +--ro up-symbolId-type-supported* up-SymbolId-type -| +--ro supported-user-group-self-assembly-modes* user-group-self-assembly-mode {feat:USER-GROUP-SELF-ASSEMBLY}? -| +--ro continuity-block-sizes-supported* uint16 { (feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ) and feat:CONTINUITY-BLOCK-SIZE }? -| +--ro eq-scale-offset-min? decimal64 {feat:DMRS-BF-EQ}? -| +--ro eq-scale-offset-max? decimal64 {feat:DMRS-BF-EQ}? -| +--ro rrm-meas-supported* rrm-meas-types {feat:RRM-MEAS-REPORTING}? -| +--ro max-ipn-unalloc-reports-supported? uint16 {feat:RRM-MEAS-REPORTING}? -| +--ro max-ipn-unalloc-symbols-supported? uint16 {feat:RRM-MEAS-REPORTING}? -| +--ro max-ipn-alloc-reports-supported? uint16 {feat:RRM-MEAS-REPORTING}? -| +--ro alloc-ipn-per-dmrs-sym-grp-supported* uint8 {feat:RRM-MEAS-REPORTING}? -| +--ro se-10-bgt-11b-supported? boolean -| +--ro se-27-odu-controlled-dimensionality-reduction-supported* enumeration {feat:SE27-ODU-CONTROLLED-DIMENSIONALITY-REDUCTION}? -| +--ro se-27-omission-when-enabled-supported? boolean {feat:SE27-ODU-CONTROLLED-DIMENSIONALITY-REDUCTION}? -| +--ro supported-se-27-configurations* [number-of-ue-data-layers] {feat:SE27-ODU-CONTROLLED-DIMENSIONALITY-REDUCTION}? - -``` - -``` - -| | +--ro number-of-ue-data-layers uint16 -| | +--ro supported-se-27-num-elements* uint16 -| +--ro se-20-full-prb-puncture-with-different-section-id-supported? boolean -| +--ro cyclic-delay-adjustment-cap {feat:CYCLIC-DELAY-SUPPORTED}? -| | +--ro pdbf-cyclic-delay-supported? boolean -| | +--ro cyclic-delay-scg-period-combination-supported* [cyclic-delay-scg-size] -| | | +--ro cyclic-delay-scg-size uint8 -| | | +--ro cyclic-delay-phase-ramp-period-numsc-supported* uint16 -| | +--ro min-cyclic-delay-scg-phase-step? int8 -| | +--ro max-cyclic-delay-scg-phase-step? int8 -| +--ro mu-interference-measurement-prb-blk-sizes-supported* uint16 {feat:RRM-MEAS-REPORTING}? -| +--ro ue-foe-in-current-slot-supported? boolean {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? - -+--rw transmission-window-schedules* [id] {feat:STATIC-TRANSMISSION-WINDOW-CONTROL}? -| +--rw id uint16 -| +--rw schedule* [symbol] -| | +--rw symbol uint16 -| | +--rw offset? uint16 - -+--ro endpoint-capacity-sharing-groups* [id] -| +--ro id uint16 -| +--ro max-control-sections-per-data-section? uint8 -| +--ro max-sections-per-symbol? uint16 -| +--ro max-sections-per-slot? uint16 -| +--ro max-highest-priority-sections-per-slot? uint16 -| x--ro max-remasks-per-section-id? uint8 -| +--ro max-uplane-section-header-per-symbol? uint16 -| +--ro max-uplane-section-header-per-slot? uint16 -| +--ro max-beams-per-symbol? uint16 -| +--ro max-beams-per-slot? uint16 -| +--ro max-total-beamids-per-symbol? uint16 -| +--ro max-total-beamids-per-slot? uint16 -| +--ro max-beams-per-symbol-multiple-beamid-tables? uint32 {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? -| +--ro max-beams-per-slot-multiple-beamid-tables? uint32 {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? - -``` - -``` - -| +--ro max-total-beamids-per-symbol-multiple-beamid-tables? uint32 {feat:MULTIPLE- -BEAMID-TABLES-SUPPORTED}? - -| +--ro max-total-beamids-per-slot-multiple-beamid-tables? uint32 {feat:MULTIPLE- -BEAMID-TABLES-SUPPORTED}? - -| +--ro max-beam-updates-per-slot? uint16 -| +--ro max-beam-updates-per-symbol? uint16 -| +--ro max-prb-per-symbol? uint16 -| +--ro max-prb-ranges-per-symbol? uint32 -| +--ro max-numerologies-per-symbol? uint16 -| +--ro max-mcsaleremask-per-prb? uint16 -| +--ro max-prb-ranges-per-sec-ext-12? uint16 -| +--ro max-freq-hops-per-sec-ext-13? uint16 -| +--ro max-prb-blks-per-sec-ext-23? uint16 {feat:SE23-PRB- -BLOCK-MODE-SUPPORT}? - -| +--ro max-endpoints? uint16 -| +--ro max-managed-delay-endpoints? uint16 -| +--ro max-non-managed-delay-endpoints? uint16 - -| +--ro transmission-buffering-capacity* [] {feat:STATIC-TRANSMISSION-WINDOW-CONTROL or -feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL}? - -| | +--ro iq-bitwidth? uint8 -| | +--ro compression-type compression-type-def -| | x--ro bitwidth? uint8 -| | +--ro compression-method? compression-method-def -| | x--ro (compression-format)? -| | | +--:(no-compresison) -| | | +--:(block-floating-point) -| | | | +--ro exponent? uint8 -| | | +--:(block-floating-point-selective-re-sending) -| | | | +--ro sres-exponent? uint8 -| | | +--:(block-scaling) -| | | | +--ro block-scalar? uint8 -| | | +--:(u-law) -| | | | +--ro comp-bit-width? uint8 -| | | | +--ro comp-shift? uint8 -| | | +--:(beam-space-compression) -| | | | +--ro active-beam-space-coeficient-mask* uint8 - -``` - -``` - -| | | | +--ro block-scaler? uint8 -| | | +--:(modulation-compression) -| | | | +--ro csf? uint8 -| | | | +--ro mod-comp-scaler? uint16 -| | | +--:(modulation-compression-selective-re-sending) -| | | | +--ro sres-csf? uint8 -| | | | +--ro sres-mod-comp-scaler? uint16 -| | +--ro max-buffered-prbs? uint32 -| | +--ro max-buffered-symbols? uint32 -| +--ro max-beams-per-cplane-message? uint16 {feat:CPLANE- -MESSAGE-PROCESSING-LIMITS}? -| +--ro max-highest-priority-sec-per-cplane-message? uint16 {feat:CPLANE- -MESSAGE-PROCESSING-LIMITS}? -| +--ro max-beams-per-slot-with-cplane-limits? uint16 {feat:CPLANE- -MESSAGE-PROCESSING-LIMITS}? -| +--ro max-highest-priority-sections-per-slot-with-cplane-limits? uint16 {feat:CPLANE- -MESSAGE-PROCESSING-LIMITS}? -| +--ro max-num-se22-per-cplane-message? uint16 {feat:CPLANE- -MESSAGE-PROCESSING-LIMITS}? -| +--ro max-prb-ranges-per-hp-section-sec-ext-12? uint16 {feat:CPLANE- -MESSAGE-PROCESSING-LIMITS}? -| +--ro max-ack-nack-per-symbol? uint16 -| +--ro supported-configuration-combinations* [combination-id] -| | +--ro combination-id uint32 -| | +--ro set* [set-id] -| | | +--ro set-id uint32 -| | | +--ro max-overlapping-instances? uint32 -| | | +--ro config* [config-id] -| | | | +--ro config-id uint32 -| | | | +--ro scs* mcap:scs-config-type -| | | | +--ro carrier-types* enumeration -| | | | +--ro filter-pass-bandwidth? uint64 -| | | | +--ro max-prb-range? uint32 -| | | | +--ro center-from-freqoffset? boolean -| | | | +--ro supported-filter-indices* uint32 -| +--ro center-from-freqoffset-supported? boolean -| +--ro se24-dmrs-capabilities {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? - -``` - -``` - -| +--ro max-user-groups-per-slot? uint32 -| +--ro max-entries-per-slot? uint32 -| +--ro max-meas-ue-pos-per-slot? uint8 {feat:RRM-MEAS-REPORTING}? - -+--ro endpoint-prach-group* [id] -| +--ro id uint16 -| +--ro supported-prach-preamble-formats* prach-preamble-format - -+--ro supported-compression-method-sets* [id] -| +--ro id uint16 -| +--ro compression-method-supported* [] -| -| +--ro iq-bitwidth? uint8 -| +--ro compression-method? compression-method-def -| x--ro (compression-format)? -| | +--:(no-compresison) -| | +--:(block-floating-point) -| | | +--ro exponent? uint8 -| | +--:(block-floating-point-selective-re-sending) -| | | +--ro sres-exponent? uint8 -| | +--:(block-scaling) -| | | +--ro block-scalar? uint8 -| | +--:(u-law) -| | | +--ro comp-bit-width? uint8 -| | | +--ro comp-shift? uint8 -| | +--:(beam-space-compression) -| | | +--ro active-beam-space-coeficient-mask* uint8 -| | | +--ro block-scaler? uint8 -| | +--:(modulation-compression) -| | | +--ro csf? uint8 -| | | +--ro mod-comp-scaler? uint16 -| | +--:(modulation-compression-selective-re-sending) -| | | +--ro sres-csf? uint8 -| | | +--ro sres-mod-comp-scaler? uint16 -| -| +--ro fs-offset* uint8 {cf:CONFIGURABLE-FS-OFFSET}? - -+--ro static-low-level-tx-endpoints* [name] -| +--ro name string - -``` - -``` - -| +-ro restricted-interfaces* -> /if:interfaces/interface/name -| +-ro array -> /user-plane-configuration/tx-arrays/name -| +-ro endpoint-type? -> ../../endpoint-types/id -| +-ro capacity-sharing-groups* -> ../../endpoint-capacity-sharing-groups/id -| +-ro supported-reference-level* [id] {TX-REFERENCE-LEVEL}? -| | +-ro id uint16 -| | +-ro min decimal64 -| | +-ro max decimal64 -| +-ro compression -| | +-ro dynamic-compression-supported? boolean -| | +-ro realtime-variable-bit-width-supported? boolean -| | +-ro supported-compression-set-id? -> ../../..//supported-compression-method-sets/id -| +-ro configurable-tdd-pattern-supported? boolean {mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED}? -| +-ro tdd-group? uint8 -| +-ro energy-sharing-group-id* uint8 {feat:MPLANE-DATA-LAYER-CONTROL}? -| +-ro sel0-member-candidate-list? -> /user-plane-configuration/sel0-member-candidate-tx-lists/id {feat:SEL0-MEMBER-CANDIDATE-LIST}? -| -+-ro static-low-level-rx-endpoints* [name] -| +-ro name string -| +-ro restricted-interfaces* -> /if:interfaces/interface/name -| +-ro array -> /user-plane-configuration/rx-arrays/name -| +-ro endpoint-type? -> ../../endpoint-types/id -| +-ro capacity-sharing-groups* -> ../../endpoint-capacity-sharing-groups/id -| +-ro prach-group? -> ../../endpoint-prach-group/id -| +-ro compression -| | +-ro dynamic-compression-supported? boolean -| | +-ro realtime-variable-bit-width-supported? boolean -| | +-ro supported-compression-set-id? -> ../../..//supported-compression-method-sets/id -| +-ro static-config-supported? enumeration -| +-ro max-prach-patterns? uint8 -| +-ro extended-max-prach-patterns? uint32 {feat:EXTENDED-PRACH-CONFIGURATION}? -| +-ro max-srs-patterns? uint8 -| +-ro configurable-tdd-pattern-supported? boolean {mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED}? - -``` - -``` - -| +-ro tdd-group? uint8 -| +-ro transmission-order? uint32 {feat:ORDERED-TRANSMISSION}? -| +-ro transmission-order-group? uint32 {feat:ORDERED-TRANSMISSION}? -| +-ro energy-sharing-group-id* uint8 {feat:MPLANE-DATA-LAYER-CONTROL}? -| +-ro sel0-member-candidate-list? -> /user-plane-configuration/sel0-member- -candidate-rx-lists/id {feat:SEL0-MEMBER-CANDIDATE-LIST}? - - +-rw low-level-tx-endpoints* [name] - - | +-rw name -> /user-plane-configuration/static- -low-level-tx-endpoints/name - - | +-rw sro-id? -> /or-user:users/user/sro-id -{feat:SHARED-ORU-MULTI-OPERATOR}? - - | +-rw compression! - - | | +-rw iq-bitwidth? uint8 - | | +-rw compression-type compression-type-def - | | x--rw bitwidth? uint8 - | | +-rw compression-method? compression-method-def - | | x--rw (compression-format)? - - | | | +--:(no-compresison) - - | | | +--:(block-floating-point) - - | | | | +-rw exponent? uint8 - | | | +--:(block-floating-point-selective-re-sending) - - | | | | +-rw sres-exponent? uint8 - | | | +--:(block-scaling) - - | | | | +-rw block-scalar? uint8 - | | | +--:(u-law) - - | | | | +-rw comp-bit-width? uint8 - | | | | +-rw comp-shift? uint8 - | | | +--:(beam-space-compression) - - | | | | +-rw active-beam-space-coeficient-mask* uint8 - | | | | +-rw block-scaler? uint8 - | | | +--:(modulation-compression) - - | | | | +-rw csf? uint8 - | | | | +-rw mod-comp-scaler? uint16 - | | | +--:(modulation-compression-selective-re-sending) - - | | | | +-rw sres-csf? uint8 - | | | | +-rw sres-mod-comp-scaler? uint16 - -``` - -``` - -| | +--rw fs-offset? uint8 {cf:CONFIGURABLE-FS-OFFSET}? -| | +--rw dynamic-compression-configuration* [id] -| | | +--rw id uint16 -| | | +--rw iq-bitwidth? uint8 -| | | +--rw compression-method? compression-method-def -| | | +--rw fs-offset? uint8 {cf:CONFIGURABLE-FS-OFFSET}? -| | | x--rw channel-information-iq-bitwidth? uint8 -| | +--rw channel-information-bitwidth? uint8 -| | +--rw channel-information-compressions* [id] {feat:CHANNEL-INFORMATION-COMPRESSION}? -| | | +--rw id uint16 -| | | +--rw channel-information-compression-method? cf:ci-compression-method-def -| | | +--rw iq-bitwidth? uint8 -| | +--rw bf-weights-compressions* [id] -| | | +--rw id uint16 -| | | +--rw bf-weights-compression? cf:bf-compression-method-def -| | | +--rw iq-bitwidth? uint8 -| +--rw frame-structure? uint8 -| +--rw cp-type? enumeration -| +--rw cp-length uint16 -| +--rw cp-length-other uint16 -| +--rw offset-to-absolute-frequency-center int32 -| +--rw number-of-prb-per-scs* [scs] -| | +--rw scs mcap:scs-config-type -| | +--rw number-of-prb uint16 -| +--rw e-axcid -| | +--rw o-du-port-bitmask uint16 -| | +--rw band-sector-bitmask uint16 -| | +--rw ccid-bitmask uint16 -| | +--rw ru-port-bitmask uint16 -| | +--rw eaxc-id uint16 -| +--rw coupling-to? -> /mcap:module-capability/ru- -capabilities/coupling-methods/coupling-via-frequency-and-time -| | +--rw coupling-method? enumeration -| +--rw configurable-tdd-pattern-supported? -> /user-plane-configuration/static- -low-level-tx-endpoints[name=current()/../name]/configurable-tdd-pattern-supported -{mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED}? - -``` - -``` - -| +--rw cplane-message-processing-limits-enabled? boolean {feat:CPLANE-MESSAGE-PROCESSING-LIMITS}? - -| +--rw uplane-message-section-header-limit-enabled? boolean {feat:UPLANE-MESSAGE-PROCESSING-LIMITS}? - -| +--rw beam-update-contention-control-enabled? boolean {feat:BEAM-UPDATE-CONTENTION-CONTROL}? - -| +--rw channel-information-prb-group-configuration {feat:CHANNEL-INFORMATION-PRB-GROUP}? - -| | +--rw enable-ci-prb-group? boolean - -| | +--rw ci-prb-group-size? uint8 - -| +--rw non-scheduled-ueid-enabled? boolean {feat:NON-SCHEDULED-UEID}? - -| +--rw se-11-continuity-flag-enabled? boolean {feat:SE11-WITH-CONTINUITY-BIT-SUPPORT}? - -| +--rw prg-size-supp-se-21-with-st6-enabled? boolean {feat:PRG-SIZE-SUPP-SE-21-WITH-ST6}? - -| +--rw prg-size-supp-se-21-with-st5-enabled? boolean {feat:PRG-SIZE-SUPP-SE-21-WITH-ST5}? - -| +--rw user-group-optimization-enabled-tx? boolean {feat:USER-GROUP-OPTIMIZATION}? - -| +--rw se-20-multi-sd-punc-pattern-enabled-tx? boolean {feat:SE20-MULTI-SD-PUNC-PATTERN-SUPPORT,feat:USER-GROUP-OPTIMIZATION}? - -| +--rw combination-configuration - -| | +--rw endpoint-type? -> /user-plane-configuration/static-low-level-tx-endpoints[name=current()/../../../../name]/endpoint-type - -| | +--rw combination-id? -> /user-plane-configuration/endpoint-types[id = current()/../endpoint-type]/supported-configuration-combinations/combination-id - -| | +--rw configurations* [id] - -| | | +--rw id uint32 - -| | | +--rw set-id? -> /user-plane-configuration/endpoint-types[id = current()/../../../../endpoint-type]/supported-configuration-combinations[combination-id = current()/../../../../combination-id]/set/set-id - -| | | +--rw config-id? -> /user-plane-configuration/endpoint-types[id = current()/../../../../endpoint-type]/supported-configuration-combinations[combination-id = current()/../../../../combination-id]/set[set-id = current()/../set-id]/config/config-id - -| +--rw configured-bf-profile-id? -> /user-plane-configuration/endpoint-types/bf-profile-group {feat:BF-DELAY-PROFILE}? - -| +--rw bf-methods* beamforming-method-type {feat:SELECTED-BF-METHOD-CONFIGURATION and feat:BF-DELAY-PROFILE}? - -| +--rw cyclic-delay-scg-period-combination* [cyclic-delay-scg-size] {feat:CYCLIC-DELAY-SUPPORTED}? - -| | +--rw cyclic-delay-scg-size uint8 - -| | +--rw cyclic-delay-phase-ramp-period-numsc? uint16 - -+--rw low-level-rx-endpoints* [name] - -``` - -``` - -| +--rw name -> /user-plane- -configuration/static-low-level-rx-endpoints/name - -| +--rw sro-id? -> /or-user:users/user/sro-id -{feat:SHARED-ORU-MULTI-OPERATOR}? - -| +--rw compression! - -| | +--rw iq-bitwidth? uint8 -| | +--rw compression-type compression-type-def -| | x--rw bitwidth? uint8 -| | +--rw compression-method? compression-method-def -| | x--rw (compression-format)? - -| | | +--:(no-compresison) - -| | | +--:(block-floating-point) - -| | | | +--rw exponent? uint8 -| | | +--:(block-floating-point-selective-re-sending) - -| | | | +--rw sres-exponent? uint8 -| | | +--:(block-scaling) - -| | | | +--rw block-scalar? uint8 -| | | +--:(u-law) - -| | | | +--rw comp-bit-width? uint8 -| | | | +--rw comp-shift? uint8 -| | | +--:(beam-space-compression) - -| | | | +--rw active-beam-space-coeficient-mask* uint8 -| | | | +--rw block-scaler? uint8 -| | | +--:(modulation-compression) - -| | | | +--rw csf? uint8 -| | | | +--rw mod-comp-scaler? uint16 -| | | +--:(modulation-compression-selective-re-sending) - -| | | | +--rw sres-csf? uint8 -| | | | +--rw sres-mod-comp-scaler? uint16 -| | +--rw fs-offset? uint8 {cf:CONFIGURABLE-FS-OFFSET}? - -| | +--rw dynamic-compression-configuration* [id] - -| | | +--rw id uint16 -| | | +--rw iq-bitwidth? uint8 -| | | +--rw compression-method? compression-method-def -| | | +--rw fs-offset? uint8 {cf:CONFIGURABLE-FS-OFFSET}? - -``` - -``` - -| | +--rw bf-weights-compressions* [id] -| | +--rw id uint16 -| | +--rw bf-weights-compression? cf:bf-compression-method-def -| | +--rw iq-bitwidth? uint8 -| +--rw frame-structure? uint8 -| +--rw cp-type? enumeration -| +--rw cp-length uint16 -| +--rw cp-length-other uint16 -| +--rw offset-to-absolute-frequency-center int32 -| +--rw number-of-prb-per-scs* [scs] -| | +--rw scs mcap:scs-config-type -| | +--rw number-of-prb uint16 -| +--rw ul-fft-sampling-offsets* [scs] -| | +--rw scs mcap:scs-config-type -| | +--rw ul-fft-sampling-offset? uint16 -| +--rw e-axcid -| | +--rw o-du-port-bitmask uint16 -| | +--rw band-sector-bitmask uint16 -| | +--rw ccid-bitmask uint16 -| | +--rw ru-port-bitmask uint16 -| | +--rw eexc-id uint16 -| +--rw eexc-gain-correction? decimal64 {EAXC-GAIN- -CORRECTION}? -| +--rw non-time-managed-delay-enabled? boolean -| +--rw coupling-to? -> -/mcap:module-capability/ru-capabilities/coupling-methods/coupling-via-frequency-and-time -| +--rw coupling-method? enumeration -| +--rw static-config-supported? -> /user-plane- -configuration/static-low-level-rx-endpoints[name=current()/..]/static-config-supported -| +--rw static-prach-configuration? -> /user-plane- -configuration/static-prach-configurations/static-prach-config-id {mcap:PRACH-STATIC-CONFIGURATION- -SUPPORTED}? -| +--rw static-srs-configuration? -> /user-plane- -configuration/static-srs-configurations/static-srs-config-id {mcap:SRS-STATIC-CONFIGURATION- -SUPPORTED}? -| +--rw configurable-tdd-pattern-supported? -> /user-plane- -configuration/static-low-level-rx-endpoints[name=current()/..]/configurable-tdd-pattern- -supported {mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED}? - -``` - -``` - -| +-rw transmission-window-control? enumeration {feat:STATIC-TRANSMISSION-WINDOW-CONTROL or feat:DYNAMIC-TRANSMISSION-WINDOW-CONTROL}? - -| +-rw transmission-window-schedule? union {feat:STATIC-TRANSMISSION-WINDOW-CONTROL}? - -| +-rw transmission-window-offset? uint16 {feat:STATIC-TRANSMISSION-WINDOW-CONTROL}? - -| +-rw transmission-window-size? uint16 {feat:STATIC-TRANSMISSION-WINDOW-CONTROL}? - -| +-rw transmission-type? enumeration {feat:STATIC-TRANSMISSION-WINDOW-CONTROL and feat:UNIFORMLY-DISTRIBUTED-TRANSMISSION}? - -| +-rw ordered-transmission? boolean {feat:ORDERED-TRANSMISSION}? - -| +-rw cplane-message-processing-limits-enabled? boolean {feat:CPLANE-MESSAGE-PROCESSING-LIMITS}? - -| +-rw beam-update-contention-control-enabled? boolean {feat:BEAM-UPDATE-CONTENTION-CONTROL}? - -| +-rw non-scheduled-ueid-enabled? boolean {feat:NON-SCHEDULED-UEID}? - -| +-rw center-from-freqoffset-enabled? boolean - -| +-rw user-group-optimization-enabled-rx? boolean {feat:USER-GROUP-OPTIMIZATION}? - -| +-rw se-20-multi-sd-punc-pattern-enabled-rx? boolean {feat:SE20-MULTI-SD-PUNC-PATTERN-SUPPORT,feat:USER-GROUP-OPTIMIZATION}? - -| +-rw combination-configuration - -| | +-rw endpoint-type? -> /user-plane-configuration/static-low-level-rx-endpoints[name=current()/..../name]/endpoint-type - -| | +-rw combination-id? -> /user-plane-configuration/endpoint-types[id = current()/../endpoint-type]/supported-configuration-combinations/combination-id - -| | +-rw configurations* [id] - -| | | +-rw id uint32 - -| | | +-rw set-id? -> /user-plane-configuration/endpoint-types[id = current()/..../endpoint-type]/supported-configuration-combinations[combination-id = current()/..../combination-id]/set/set-id - -| | | +-rw config-id? -> /user-plane-configuration/endpoint-types[id = current()/..../endpoint-type]/supported-configuration-combinations[combination-id = current()/..../combination-id]/set[set-id = current()/../set-id]/config/config-id - -| +-rw configured-bf-profile-id? -> /user-plane-configuration/endpoint-types/bf-profile-group {feat:BF-DELAY-PROFILE}? - -| +-rw sinr-reporting-enabled? boolean {feat:DMRS-BF-EQ}? - -| +-rw oru-control-sinr-time-resolution-enabled? boolean {feat:ORU-CONTROL-SINR-TIME-RESOLUTION}? - -| +-rw sinr-reporting-configuration {feat:DMRS-BF-EQ}? - -| | +-rw sinr-resolution - -``` - -``` - -| | | +---rw sinr-per-prb? uint8 -| | | +---rw sinr-slot-mask? uint16 -| | | +---rw sinr-slot-masks* [sinr-slot-mask-id] {feat:ORU-CONTROL-SINR-TIME-RESOLUTION}? -| | | +---rw sinr-slot-mask-id uint8 -| | | +---rw sinr-slot-mask? uint16 -| | +---rw sinr-compression -| | +---rw sinr-bitwidth? uint8 -| | +---rw sinr-compression-method? sinr-compression-method-def -| | +---rw sinr-block-size? uint8 -| | +---rw sinr-reference-level-config? decimal64 -| | +---ro sinr-reference-level-used? decimal64 -| +---rw dynamic-sinr-per-prb-enabled? boolean {feat:DYNAMIC-SINR- -PER-PRB}? -| +---rw multi-value-dftsofdm-sinr-report-enabled? boolean {feat:DMRS-BF-EQ}? -| +---rw se26-usage-enabled? boolean -| +---rw bf-methods* beamforming-method-type -{feat:SELECTED-BF-METHOD-CONFIGURATION and feat:BF-DELAY-PROFILE}? -| +---rw eq-scale-offset-config? decimal64 {feat:DMRS-BF-EQ}? -| +---ro eq-scale-offset-used? decimal64 {feat:DMRS-BF-EQ}? -| +---rw rrm-meas-enabled* rrm-meas-types {feat:RRM- -MEAS-REPORTING}? -| +---rw ue-foe-in-current-slot-enabled? boolean {(feat:DMRS-BF-EQ or -feat:DMRS-BF-NEQ) and feat:RRM-MEAS-REPORTING}? -| +---rw se-27-odu-controlled-dimensionality-reduction-enabled? enumeration {feat:SE27-ODU- -CONTROLLED-DIMENSIONALITY-REDUCTION}? -| +---rw se-27-num-elements? uint16 {feat:SE27-ODU- -CONTROLLED-DIMENSIONALITY-REDUCTION}? -| +---rw mu-interference-measurement-prb-blk-size? uint16 {feat:RRM-MEAS- -REPORTING}? - -+---rw tx-array-carriers* [name] -| +---rw name string -| +---rw odu-ids* [odu-id] {feat:SHARED-ORU-MULTI-ODU}? -| | +---rw odu-id string -| +---rw sro-ids-and-odu-ids* [odu-id sro-id] {feat:SHARED-ORU-MULTI-ODU and feat:SHARED-ORU- -MULTI-OPERATOR}? -| | +---rw odu-id string -| | +---rw sro-id string -| x---rw absolute-frequency-center? uint32 - -``` - -``` - -| +--rw center-of-channel-bandwidth uint64 -| +--rw channel-bandwidth uint64 -| +--rw active? enumeration -| +--ro state enumeration -| +--ro availability-status* o-ran-cmn:availability-status -| +--rw type? enumeration -| +--ro duplex-scheme? enumeration -| -| x--rw rw-duplex-scheme? -> /user-plane-configuration/tx-array- -carriers[name=current()/../name]/duplex-scheme -| -| x--rw rw-type? -> /user-plane-configuration/tx-array- -carriers[name=current()/../name]/type -| -| +--rw occupied-bandwidth -| | +--rw lower-bound? uint64 -| | +--rw upper-bound? uint64 -| -| +--rw configured-tx-beamid-table-index? uint8 {feat:MULTIPLE-BEAMID-TABLES- -SUPPORTED}? -| -| +--rw band-number? -> /mcap:module-capability/band- -capabilities/band-number {mcap:LAA}? -| -| x--rw lte-tdd-frame -| | +--rw subframe-assignment enumeration -| | +--rw special-subframe-pattern enumeration -| -| +--rw laa-carrier-configuration {mcap:LAA}? -| | +--rw ed-threshold-pdsch? int8 -| | +--rw ed-threshold-drs? int8 -| | +--rw tx-antenna-ports? uint8 -| | +--rw transmission-power-for-drs? int8 -| | +--rw dmtc-period? enumeration -| | +--rw dmtc-offset? uint8 -| | +--rw lbt-timer? uint16 -| | -| | +--rw max-cw-usage-counter* [priority] -| | | +--rw priority enumeration -| | | +--rw counter-value? uint8 -| -| +--rw gain decimal64 -| +--rw carrier-max-power-reduction? decimal64 {feat:MAX-POWER-CONTROL}? -| +--rw downlink-radio-frame-offset uint32 -| +--rw downlink-sfn-offset int16 - -``` - -``` - -| +--rw t-da-offset? uint32 {feat:EXT-ANT-DELAY-CONTROL}? -| +--rw reference-level? decimal64 {TX-REFERENCE-LEVEL}? -| +--rw configurable-tdd-pattern? -> -/user-plane-configuration/configurable-tdd-patterns/tdd-pattern-id {mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED}? - -| +--rw crb-to-prb-grid-offset? uint16 {feat:PRG-SIZE-SUPP-SE-21-WITH-ST6 or feat:PRG-SIZE-SUPP-SE-21-WITH-ST5}? - -| +--rw point-a-offset-to-absolute-frequency-center? int32 {feat:CYCLIC-DELAY-SUPPORTED and feat:POINT-A-OFFSET-TO-ABSOLUTE-FREQUENCY-CENTER-TX}? - - +--rw rx-array-carriers* [name] - | +--rw name string - | +--rw odu-ids* [odu-id] {feat:SHARED-ORU-MULTI-ODU}? - | | +--rw odu-id string - | +--rw sro-ids-and-odu-ids* [odu-id sro-id] {feat:SHARED-ORU-MULTI-ODU and feat:SHARED-ORU-MULTI-OPERATOR}? - | | +--rw odu-id string - | | +--rw sro-id string - | x--rw absolute-frequency-center? uint32 - | +--rw center-of-channel-bandwidth uint64 - | +--rw channel-bandwidth uint64 - | +--rw active? enumeration - | +--ro state enumeration - | +--ro availability-status* o-ran-cmn:availability-status - | +--rw type? enumeration - | +--ro duplex-scheme? enumeration - | +--rw occupied-bandwidth - | | +--rw lower-bound? uint64 - | | +--rw upper-bound? uint64 - | +--rw configured-rx-beamid-table-index? uint8 {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? - - | +--rw downlink-radio-frame-offset uint32 - | +--rw downlink-sfn-offset int16 - | +--rw gain-correction decimal64 - | +--rw n-ta-offset uint32 - | +--rw t-au-offset? uint32 {feat:EXT-ANT-DELAY-CONTROL}? - | +--rw configurable-tdd-pattern? -> -/user-plane-configuration/configurable-tdd-patterns/tdd-pattern-id {mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED}? - -``` - -``` - -| +--rw user-group-mode? enumeration {feat:USER-GROUP-SELF-ASSEMBLY}? - -| +--rw point-a-offset-to-absolute-frequency-center? int32 {(feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ) and feat:POINT-A-OFFSET-TO-ABSOLUTE-FREQUENCY-CENTER}? - -| +--rw continuity-block-size-configured? uint8 {(feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ) and feat:CONTINUITY-BLOCK-SIZE}? - -| +--rw port-reduced-dmrs-data-sending-enabled? boolean {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? - - +--ro tx-arrays* [name] - | +--ro name string - | +--ro number-of-rows uint16 - | +--ro number-of-columns uint16 - | +--ro number-of-array-layers uint8 - | +--ro horizontal-spacing? decimal64 - | +--ro vertical-spacing? decimal64 - | +--ro normal-vector-direction - | | +--ro azimuth-angle? decimal64 - | | +--ro zenith-angle? decimal64 - | +--ro leftmost-bottom-array-element-position - | | +--ro x? decimal64 - | | +--ro y? decimal64 - | | +--ro z? decimal64 - | +--ro polarisations* [p] - | | +--ro p uint8 - | | +--ro polarisation polarisation_type - | +--ro band-number -> /mcap:module-capability/band-capabilities/band-number - | +--ro related-o-ru-connectors* [name] - | | +--ro name -> /hw:hardware/component/name - | | +--ro array-element-id* uint16 - | +--ro min-gain? decimal64 - | +--ro max-gain decimal64 - | +--ro supported-max-power-level* [index] {feat:MAX-POWER-CONTROL}? - | | +--ro index uint8 - | | +--ro array-max-power-reduction? decimal64 - | +--ro max-power-level-used? uint8 {feat:MAX-POWER-CONTROL}? - | +--ro independent-power-budget boolean - -``` - -``` - -| +--ro capabilities* [] -| | +--ro max-supported-frequency-dl? uint64 -| | +--ro min-supported-frequency-dl? uint64 -| | +--ro max-supported-bandwidth-dl? uint64 -| | +--ro max-num-carriers-dl? uint32 -| | +--ro max-carrier-bandwidth-dl? uint64 -| | +--ro min-carrier-bandwidth-dl? uint64 -| | +--ro supported-technology-dl* enumeration -| | +--ro supported-filter-pass-bandwidths-dl -| | | +--ro supported-filter-pass-bandwidths* [id] -| | | | +--ro id uint32 -| | | | +--ro type? enumeration -| | | | +--ro carrier-bandwidth? uint64 -| | | | +--ro filter-pass-bandwidth? uint64 -| | +--ro tx-array-beamid-table-indexes* uint8 {or-feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? -| | +--ro supported-energy-saving-capabilities-dl -| | +--ro trx-control-capability-info {feat:TRX-CONTROL}? -| | | +--ro supported-trx-control-masks* [index] -| | | | +--ro index uint8 -| | | | +--ro mask-name? string -| | | | +--ro antenna-mask? binary -| | | +--ro sleep-modes* [sleep-mode-type] -| | | | +--ro sleep-mode-type enumeration -| | | | +--ro wake-up-duration? uint32 -| | | | +--ro wake-up-duration-guaranteed? boolean -| | | | +--ro defined-duration-sleep-supported? boolean -| | | | +--ro undefined-duration-sleep-supported? boolean -| | +--ro asm-capability-info {feat:ADVANCED-SLEEP-MODE}? -| | | +--ro sleep-modes* [sleep-mode-type] -| | | | +--ro sleep-mode-type enumeration -| | | | +--ro wake-up-duration? uint32 -| | | | +--ro wake-up-duration-guaranteed? boolean -| | | | +--ro defined-duration-sleep-supported? boolean -| | | | +--ro undefined-duration-sleep-supported? boolean - -``` - -``` - -| +--ro mplane-trx-control-txarr-capability-info {feat:MPLANE-TRX-CONTROL}? -| +--ro mplane-supported-trx-control-masks* [index] -| +--ro index uint8 -| +--ro antenna-mask? binary -| -| +--ro rx-arrays* [name] -| +--ro name string -| +--ro number-of-rows uint16 -| +--ro number-of-columns uint16 -| +--ro number-of-array-layers uint8 -| +--ro horizontal-spacing? decimal64 -| +--ro vertical-spacing? decimal64 -| +--ro normal-vector-direction -| | +--ro azimuth-angle? decimal64 -| | +--ro zenith-angle? decimal64 -| +--ro leftmost-bottom-array-element-position -| | +--ro x? decimal64 -| | +--ro y? decimal64 -| | +--ro z? decimal64 -| +--ro polarisations* [p] -| | +--ro p uint8 -| | +--ro polarisation polarisation_type -| -| +--ro band-number -> /mcap:module-capability/band-capabilities/band-number -| -| +--ro related-o-ru-connectors* [name] -| | +--ro name -> /hw:hardware/component/name -| | +--ro array-element-id* uint16 -| -| +--ro gain-correction-range -| | +--ro max decimal64 -| | +--ro min decimal64 -| -| +--ro capabilities* [] -| | +--ro max-supported-frequency-ul? uint64 -| | +--ro min-supported-frequency-ul? uint64 -| | +--ro max-supported-bandwidth-ul? uint64 -| | +--ro max-num-carriers-ul? uint32 -| | +--ro max-carrier-bandwidth-ul? uint64 - -``` - -``` - -| | +--ro min-carrier-bandwidth-ul? uint64 -| | +--ro supported-technology-ul* enumeration -| | +--ro supported-filter-pass-bandwidths-ul -| | | +--ro supported-filter-pass-bandwidths* [id] -| | | +--ro id uint32 -| | | +--ro type? enumeration -| | | +--ro carrier-bandwidth? uint64 -| | | +--ro filter-pass-bandwidth? uint64 -| | +--ro rx-array-beamid-table-indexes* uint8 {or-feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? -| | +--ro supported-energy-saving-capabilities-ul -| | +--ro trx-control-capability-info {feat:TRX-CONTROL}? -| | | +--ro supported-trx-control-masks* [index] -| | | | +--ro index uint8 -| | | | +--ro mask-name? string -| | | | +--ro antenna-mask? binary -| | | +--ro sleep-modes* [sleep-mode-type] -| | | | +--ro sleep-mode-type enumeration -| | | | +--ro wake-up-duration? uint32 -| | | | +--ro wake-up-duration-guaranteed? boolean -| | | +--ro defined-duration-sleep-supported? boolean -| | | +--ro undefined-duration-sleep-supported? boolean -| | +--ro asm-capability-info {feat:ADVANCED-SLEEP-MODE}? -| | +--ro sleep-modes* [sleep-mode-type] -| | | +--ro sleep-mode-type enumeration -| | | +--ro wake-up-duration? uint32 -| | | +--ro wake-up-duration-guaranteed? boolean -| | +--ro defined-duration-sleep-supported? boolean -| | +--ro undefined-duration-sleep-supported? boolean -| +--ro mplane-trx-control-rxarr-capability-info {feat:MPLANE-TRX-CONTROL}? -| +--ro mplane-supported-trx-control-masks* [index] -| +--ro index uint8 -| +--ro antenna-mask? binary -+--ro relations* [entity] -| +--ro entity uint16 - -``` - -``` - -| +-ro array1 -| | +-ro (antenna-type)? -| | +-:(tx) -| | | +-ro tx-array-name? -> /user-plane-configuration/tx-arrays/name -| | +-:(rx) -| | +-ro rx-array-name? -> /user-plane-configuration/rx-arrays/name -| +-ro array2 -| | +-ro (antenna-type)? -| | +-:(tx) -| | | +-ro tx-array-name? -> /user-plane-configuration/tx-arrays/name -| | +-:(rx) -| | +-ro rx-array-name? -> /user-plane-configuration/rx-arrays/name -| +-ro types* [relation-type] -| +-ro relation-type enumeration -| +-ro pairs* [element-array1] -| +-ro element-array1 uint16 -| +-ro element-array2? uint16 - -+-rw eexc-id-group-configuration {mcap:EEXC-ID-GROUP-SUPPORTED}? - -| +-rw max-num-tx-eexc-id-groups? -> /mcap:module-capability/ru-capabilities/eexcid- -grouping-capabilities/max-num-tx-eexc-id-groups - -| +-rw max-num-tx-eexc-ids-per-group? -> /mcap:module-capability/ru-capabilities/eexcid- -grouping-capabilities/max-num-tx-eexc-ids-per-group - -| +-rw max-num-rx-eexc-id-groups? -> /mcap:module-capability/ru-capabilities/eexcid- -grouping-capabilities/max-num-rx-eexc-id-groups - -| +-rw max-num-rx-eexc-ids-per-group? -> /mcap:module-capability/ru-capabilities/eexcid- -grouping-capabilities/max-num-rx-eexc-ids-per-group - -| +-rw tx-eexc-id-group* [representative-tx-eexc-id] -| | +-rw representative-tx-eexc-id uint16 -| | +-rw member-tx-eexc-id* uint16 - -| +-rw rx-eexc-id-group* [representative-rx-eexc-id] -| +-rw representative-rx-eexc-id uint16 -| +-rw member-rx-eexc-id* uint16 - -+-rw static-prach-configurations* [static-prach-config-id] {mcap:PRACH-STATIC-CONFIGURATION- -SUPPORTED}? - -| +-rw static-prach-config-id uint8 -| +-rw sfn-offset? uint32 -| +-rw pattern-period uint16 - -``` - -``` - -| +--rw guard-tone-low-re uint32 -| +--rw num-prach-re uint32 -| +--rw guard-tone-high-re uint32 -| +--rw sequence-duration uint32 -| +--rw prach-patterns* [prach-pattern-id] -| +--rw prach-pattern-id uint32 -| +--rw number-of-repetitions uint8 -| +--rw number-of-occasions uint32 -| +--rw re-offset uint32 -| +--rw occasion-parameters* [occasion-id] -| | +--rw occasion-id uint32 -| | +--rw cp-length uint16 -| | +--rw gp-length? uint16 -| | +--rw beam-id uint16 -| +--rw frame-number uint16 -| +--rw sub-frame-id uint16 -| +--rw time-offset uint16 - -+--rw static-srs-configurations* [static-srs-config-id] {mcap:SRS-STATIC-CONFIGURATION-SUPPORTED}? - -| +--rw static-srs-config-id uint8 -| +--rw pattern-period uint16 -| +--rw srs-patterns* [srs-pattern-id] -| +--rw srs-pattern-id uint16 -| +--rw sub-frame-id uint16 -| +--rw slot-id uint16 -| +--rw start-symbol-id uint16 -| +--rw beam-id uint16 -| +--rw num-symbol uint16 -| +--rw start-prbc uint16 -| +--rw num-prbc uint16 - -+--rw configurable-tdd-patterns* [tdd-pattern-id] {mcap:CONFIGURABLE-TDD-PATTERN-SUPPORTED}? - -| +--rw tdd-pattern-id uint8 -| +--rw switching-points* [switching-point-id] -| +--rw switching-point-id uint16 -| +--rw direction enumeration - -``` - -``` - -| +--rw frame-offset uint32 - - +--ro endpoint-bf-profile-group* [bf-profile-id] {feat:BF-DELAY-PROFILE}? - - | +--ro bf-profile-id uint16 - - | +--ro supported-bf-methods* beamforming-method-type - - | +--ro supported-delay-profile? -> -/or-dm:delay-management/non-default-ru-delay-profile/delay-profile-id - - +--ro se10-member-candidate-tx-lists* [id] {feat:SE10-MEMBER-CANDIDATE-LIST}? - - | +--ro id uint8 - - | +--ro member-candidates* -> /user-plane-configuration/static-low-level-tx-endpoints/name - - +--ro se10-member-candidate-rx-lists* [id] {feat:SE10-MEMBER-CANDIDATE-LIST}? - - | +--ro id uint8 - - | +--ro member-candidates* -> /user-plane-configuration/static-low-level-rx-endpoints/name - - +--ro max-power-control-methods-supported* max-power-control-methods {feat:MAX-POWER-CONTROL}? - - +--rw general-config - - | +--rw regularization-factor-se-configured? boolean - - | +--rw little-endian-byte-order? boolean - - | +--rw uplane-only-dl-mode-enable? boolean {feat:UPLANE-ONLY-DL-MODE}? - - | +--rw st4-for-time-domain-beamforming-weights-enabled? boolean {feat:ST4-SLOT-CONFIG-MSG-SUPPORT}? - - | +--rw seq-id-checking-disabled? boolean {feat:SEQ-ID-CHECKING-CONFIGURABLE}? - - | +--rw multiple-beamId-tables-support-enabled? boolean {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? - - | +--rw energy-sharing-groups-disabled* uint8 {feat:MPLANE-DATA-LAYER-CONTROL}? - - | +--rw config-symb-reorder-method? symb-reorder-method {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? - - | +--rw config-symb-reorder-upSymbId-type? -> ../../endpoint-types/supported-symb-reorder-capabilities/up-symbolId-type-supported {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? - - | +--rw ueid-persistence-enabled? boolean {feat:UEID-PERSISTENCE}? - - | +--rw ueid-layer-bits-configured? uint8 {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? - - | +--rw vswr-thresholds {feat:CONFIGURABLE-VSWR-THRESHOLDS}? - - | | +--ro default-vswr-thresholds - - | | | +--ro default-vswr-minor-threshold? decimal64 - - | | | +--ro default-vswr-major-threshold? decimal64 - - | | +--ro vswr-thresholds-range - - | | | +--ro min? decimal64 - -``` - -``` - -| | | +--ro max? decimal64 -| | +--rw configurable-vswr-thresholds -| | +--rw global-vswr-monitoring-trigger-power? decimal64 -| | +--rw global-vswr-minor-threshold? decimal64 -| | +--rw global-vswr-major-threshold? decimal64 -| | +--rw vswr-threshold-per-tx-array-element* [tx-array-name array-element] -| | +--rw tx-array-name -> /user-plane-configuration/tx-arrays/name -| | +--rw array-element uint16 -| | +--rw vswr-minor-threshold? decimal64 -| | +--rw vswr-major-threshold? decimal64 -| | +--rw vswr-monitoring-trigger-power? decimal64 -| +--rw max-power-control-method? max-power-control-methods -{feat:MAX-POWER-CONTROL}? - - +--rw tx-array-antenna-mask-config* [array-name] {feat:MPLANE-TRX-CONTROL}? - | +--rw array-name -> /user-plane-configuration/tx-arrays/name - | +--rw antenna-bitmask? binary - | +--rw antenna-bitmask-index? uint8 - - +--rw rx-array-antenna-mask-config* [array-name] {feat:MPLANE-TRX-CONTROL}? - | +--rw array-name -> /user-plane-configuration/rx-arrays/name - | +--rw antenna-bitmask? binary - | +--rw antenna-bitmask-index? uint8 - - +--rw array-config - +--rw max-power-control-config* [array-name] {feat:MAX-POWER-CONTROL}? - +--rw array-name -> /user-plane-configuration/tx-arrays/name - +--rw max-power-level-index? -> /user-plane-configuration/tx-arrays[name = -current()/..array-name]/supported-max-power-level/index - -notifications: - - +---n tx-array-carriers-state-change - | +--ro tx-array-carriers* [name] - | +--ro name -> /user-plane-configuration/tx-array-carriers/name - | +--ro state? -> /user-plane-configuration/tx-array-carriers/state - | +--ro availability-status? -> /user-plane-configuration/tx-array-carriers/availability- -status - - +---n rx-array-carriers-state-change - | +--ro rx-array-carriers* [name] - -``` - -``` - -| +--ro name -> /user-plane-configuration/rx-array-carriers/name -| +--ro state? -> /user-plane-configuration/rx-array-carriers/state -| +--ro availability-status? -> /user-plane-configuration/rx-array-carriers/availability- -status -| -| +---n data-layer-control-wakeup-notification {feat:MPLANE-DATA-LAYER-CONTROL}? -| | +--ro energy-sharing-group* uint8 -| -| +---n mplane-trx-control-ant-mask-update {feat:MPLANE-TRX-CONTROL}? -| | +--ro array-name? union -| | +--ro array-type? enumeration -| | +--ro updated-antenna-mask? binary -| | +--ro updated-antenna-mask-index? uint8 -| -| +---n max-power-update {feat:MAX-POWER-CONTROL}? -| | +--ro max-power-level-used? uint8 -| | -| +--ro array-name* -> /user-plane-configuration/tx-arrays/name - -``` - -## D.3.9 o-ran-ald module - -The format for the ald module is provided below. - -``` - -module: o-ran-ald - - rpcs: - - +---x ald-communication - - +---w input - - | +---w port-id -> /ap:ald-ports-io/ald-port/port-id - - | +---w ald-req-msg? binary - - +--ro output - - +--ro port-id -> /ap:ald-ports-io/ald-port/port-id - - +--ro status enumeration - - +--ro error-message? string - - +--ro ald-resp-msg? binary - - +--ro frames-with-wrong-crc? uint32 - - +--ro frames-without-stop-flag? uint32 - - +--ro number-of-received-octets? uint32 - -``` - -## D.3.10 o-ran-troubleshooting module - -The format for the troubleshooting module is provided below. - -``` -module: o-ran-troubleshooting - - rpcs: - - +---x start-troubleshooting-logs - - | +---w input - - | | +---w filter* [filter-type] {feat:LOG-FILTER}? - - | | | +---w filter-type identityref - - | | | +---w value* string - - | +---ro output - - | | +---ro status? enumeration - - | | +---ro failure-reason? string - - +---x stop-troubleshooting-logs - - | +---ro output - - | | +---ro status? enumeration - - | | +---ro failure-reason? string - - notifications: - - +---n troubleshooting-log-generated - - | +---ro log-file-name* string -``` - -## D.3.11 void - -## D.3.12 o-ran-trace module - -The format for the trace operations module is provided below. - -``` -module: o-ran-trace - - rpcs: - - +---x start-trace-logs - - | +---ro output - - | | +---ro status? enumeration - - | | +---ro failure-reason? string -``` - -``` - -+---x stop-trace-logs - +--ro output - +--ro status? enumeration - +--ro failure-reason? string - - notifications: - - +---n trace-log-generated - +--ro log-file-name* string - +--ro is-notification-last? Boolean - -``` - -## D.3.13 o-ran-ieee802-dot1q-cfm module - -The format for the o-ran-ieee802-dot1q-cfm module is provided below. - -``` - -module: o-ran-ieee802-dot1q-cfm - - augment /dot1q-cfm:cfm/dot1q-cfm:maintenance-group/dot1q-cfm:mep: - - +--rw interface? if:interface-ref - - +--rw primary-vid? -> /if:interfaces/interface/o-ran-int:vlan-id - -``` - -## D.4 Interfaces folder - -### D.4.1 o-ran-interfaces.yang module - -The format for the interfaces module is provided below. - -``` - -module: o-ran-interfaces - - augment /if:interfaces/if:interface/ip:ipv4: - - +--rw m-plane-marking? inet:dscp - - augment /if:interfaces/if:interface/ip:ipv6: - - +--rw m-plane-marking? inet:dscp - - augment /if:interfaces/if:interface/ip:ipv4: - - +--rw tcp! {feat:PER-INT-TCP-MSS}? - - +--rw mss-adjust? mss - - augment /if:interfaces/if:interface/ip:ipv6: - - +--rw tcp! {feat:PER-INT-TCP-MSS}? - - +--rw mss-adjust? mss - -``` - -``` - -augment /if:interfaces/if:interface/ip:ipv4: - - +--rw diffserv-markings {UDPIP-BASED-CU-PLANE}? - - +--rw u-plane-marking? inet:dscp - +--rw c-plane-marking? inet:dscp - +--rw s-plane-marking? inet:dscp - +--rw other-marking? inet:dscp - +--rw enhanced-uplane-markings* [up-marking-name] - - +--rw up-marking-name string - +--rw enhanced-marking? inet:dscp - -augment /if:interfaces/if:interface/ip:ipv6: - - +--rw diffserv-markings {UDPIP-BASED-CU-PLANE}? - - +--rw u-plane-marking? inet:dscp - +--rw c-plane-marking? inet:dscp - +--rw s-plane-marking? inet:dscp - +--rw other-marking? inet:dscp - +--rw enhanced-uplane-markings* [up-marking-name] - - +--rw up-marking-name string - +--rw enhanced-marking? inet:dscp - -rpcs: - - +---x reset-interface-counters - -``` - -## D.4.2 o-ran-processing-elements.yang module - -The format for the processing element module is provided below. - -``` - -module: o-ran-processing-element - - +--rw processing-elements - - +--ro maximum-number-of-transport-flows? uint16 - +--rw transport-session-type? enumeration - +--rw enhanced-uplane-mapping! - - | +--rw uplane-mapping* [up-marking-name] - - | +--rw up-marking-name string - | +--rw (up-markings)? - - | +--:(ethernet) - - | | +--rw up-cos-name? -> - -/if:interfaces/interface/o-ran-int:class-of-service/enhanced-uplane-markings/up-marking-name - -``` - -``` - -| +--:(ipv4) -| | +--rw upv4-dscp-name? -> /if:interfaces/interface/ip:ipv4/o-ran-int:diffserv- -markings/enhanced-uplane-markings/up-marking-name {o-ran-int:UDPIP-BASED-CU-PLANE}? - -| +--:(ipv6) -| | +--rw upv6-dscp-name? -> /if:interfaces/interface/ip:ipv6/o-ran-int:diffserv- -markings/enhanced-uplane-markings/up-marking-name {o-ran-int:UDPIP-BASED-CU-PLANE}? - -| +--rw ru-elements* [name] -| | +--rw name string -| | +--rw sro-id? -> /or-user:users/user/sro-id {feat:SHARED-ORU-MULTI-OPERATOR}? -| | +--rw transport-flow -| | | +--rw interface-name? -> /if:interfaces/interface/name -| | | +--rw aliasmac-flow {o-ran-int:ALIASMAC-BASED-CU-PLANE}? -| | | | +--rw ruAliasmac-address -> /if:interfaces/interface[if:name = -current()/../../../../interface-name]/o-ran-int:alias-macs -| | | | +--rw vlan-id? -> /if:interfaces/interface[if:name = -current()/../../../../interface-name]/o-ran-int:vlan-id -| | | | +--rw o-du-mac-address yang:mac-address -| | | | +--rw eth-flow -| | | | +--rw ru-mac-address -> /if:interfaces/interface[if:name = -current()/../../../../interface-name]/o-ran-int:mac-address -| | | | +--rw vlan-id -> /if:interfaces/interface[if:name = -current()/../../../../interface-name]/o-ran-int:vlan-id -| | | | +--rw o-du-mac-address yang:mac-address -| | | | +--rw udpip-flow -| | | | | +--rw (address) -| | | | | | +--:(ru-ipv4-address) -| | | | | | | +--rw ru-ipv4-address? -> /if:interfaces/interface[if:name = -current()/../../../../interface-name]/ip:ipv4/address/ip -| | | | | | +--:(ru-ipv6-address) -| | | | | | | +--rw ru-ipv6-address? -> /if:interfaces/interface[if:name = -current()/../../../../interface-name]/ip:ipv6/address/ip -| | | | | +--rw o-du-ip-address inet:ip-address -| | | | | +--rw ru-ephemeral-udp-port inet:port-number -| | | | | +--rw o-du-ephemeral-udp-port inet:port-number -| | | | | +--rw ecpri-destination-udp inet:port-number -| | | | | +--rw north-eth-flow {SHARED_CELL}? -| | | | | +--rw ru-mac-address? -> /if:interfaces/interface[if:name = -current()/../../../../interface-name]/o-ran-int:mac-address - -``` - -``` - -| | +--rw vlan-id? -> /if:interfaces/interface[if:name = -current()/../../../../interface-name]/o-ran-int:vlan-id - -| | +--rw north-node-mac-address? yang:mac-address - -| +--rw south-eth-flow {SHARED_CELL}? - -| +--rw ru-mac-address? -> /if:interfaces/interface[if:name = -current()/../../../../interface-name]/o-ran-int:mac-address - -| +--rw vlan-id? -> /if:interfaces/interface[if:name = -current()/../../../../interface-name]/o-ran-int:vlan-id - -| +--rw south-node-mac-address? yang:mac-address - - +--rw additional-transport-session-type-elements* [transport-session-type] {feat:MULTIPLE- -TRANSPORT-SESSION-TYPE}? - - +--rw transport-session-type enumeration - - +--rw enhanced-uplane-mapping! - - | +--rw uplane-mapping* [up-marking-name] - - | +--rw up-marking-name string - - | +--rw (up-markings)? - - | +--:(ethernet) - - | | +--rw up-cos-name? -> -/if:interfaces/interface/o-ran-int:class-of-service/enhanced-uplane-markings/up-marking-name - - | +--:(ipv4) - - | | +--rw upv4-dscp-name? -> /if:interfaces/interface/ip:ipv4/o-ran-int:diffserv- -markings/enhanced-uplane-markings/up-marking-name - - | +--:(ipv6) - - | | +--rw upv6-dscp-name? -> /if:interfaces/interface/ip:ipv6/o-ran-int:diffserv- -markings/enhanced-uplane-markings/up-marking-name - - +--rw ru-elements* [name] - - +--rw name string - - +--rw sro-id? -> /or-user:users/user/sro-id {feat:SHARED-ORU-MULTI-OPERATOR}? - - +--rw transport-flow - - +--rw interface-name? -> /if:interfaces/interface/name - - +--rw aliasmac-flow {o-ran-int:ALIASMAC-BASED-CU-PLANE}? - - | +--rw ruAliasMacAddress -> /if:interfaces/interface[if:name = -current()/../../../../interface-name]/o-ran-int:alias-macs - - | +--rw vlan-id? -> /if:interfaces/interface[if:name = -current()/../../../../interface-name]/o-ran-int:vlan-id - - | +--rw o-du-mac-address yang:mac-address - - +--rw eth-flow - - | +--rw ru-mac-address -> /if:interfaces/interface[if:name = -current()/../../../../interface-name]/o-ran-int:mac-address - -``` - -``` - -| +--rw vlan-id -> /if:interfaces/interface[if:name = -current()/../..//interface-name]/o-ran-int:vlan-id - -| +--rw o-du-mac-address yang:mac-address - -+--rw udpip-flow - -+--rw (address) - -| +--:(ru-ipv4-address) - -| | +--rw ru-ipv4-address? -> /if:interfaces/interface[if:name = -current()/../..//interface-name]/ip:ipv4/address/ip - -| +--:(ru-ipv6-address) - -| | +--rw ru-ipv6-address? -> /if:interfaces/interface[if:name = -current()/../..//interface-name]/ip:ipv6/address/ip - -+--rw o-du-ip-address inet:ip-address - -+--rw ru-ephemeral-udp-port inet:port-number - -+--rw o-du-ephemeral-udp-port inet:port-number - -+--rw ecpri-destination-udp inet:port-number - -``` - -## D.4.3 o-ran-transceiver.yang module - -The format for the (SFP) transceiver module is provided below. - -``` - -module: o-ran-transceiver - -+--rw port-transceivers - -+--rw port-transceiver-data* [interface-name port-number] - -+--rw interface-name -> /if:interfaces/interface/name - -+--rw port-number -> /if:interfaces/interface[if:name = -current()/../..//interface-name]/o-ran-int:port-reference/port-number - -+--rw interface-names* -> /if:interfaces/interface/name - -+--rw name? string - -+--ro present boolean - -+--ro vendor-id? string - -+--ro vendor-part? string - -+--ro vendor-rev? string - -+--ro serial-no? string - -+--ro SFF8472-compliance-code? enumeration - -+--ro connector-type? enumeration - -+--ro identifier? enumeration - -+--ro nominal-bitrate? uint32 - -+--ro low-bitrate-margin? uint8 - -``` - -``` - -+--ro high-bitrate-margin? uint8 -+--ro rx-power-type? enumeration -+--ro rx-power? decimal64 -+--ro tx-power? decimal64 -+--ro tx-bias-current? decimal64 -+--ro voltage? decimal64 -+--ro temperature? decimal64 -+--ro laser-temperature? decimal64 -+--ro transceiver-not-supported? empty -+--ro tec-current? decimal64 -+--ro tunable-transceiver-info -| +--ro dwdm-tuning-capability? boolean -| +--ro dwdm-self-tuning-capability? boolean -| +--ro dwdm-first-channel-frequency? uint32 -| +--ro dwdm-last-channel-frequency? uint32 -| +--ro dwdm-minimum-grid-spacing? uint32 -| +--ro dwdm-channel-configuration-method? enumeration -| +--ro self-tuning-in-progress? boolean -| +--ro tuned-dwdm-channel-wavelength? uint32 -| +--ro tuned-dwdm-channel-frequency-error? uint32 -| +--ro tuned-dwdm-channel-wavelength-error? uint32 -| +--ro tc-fault? boolean -+--ro alarm-warning-thresholds* [meas-type] {or-feat:TRANSCEIVER-ALARM-WARNING-SUPPORTED}? -| +--ro meas-type transceiver-meas-type -| +--ro thresholds* [threshold-type] -| +--ro threshold-type transceiver-alarm-warning-thresh-type -| +--ro threshold-value? decimal64 -+--ro alarm-warning-states* [meas-type] {or-feat:TRANSCEIVER-ALARM-WARNING-SUPPORTED}? -| +--ro meas-type transceiver-meas-type -| +--ro state? transceiver-alarm-warning-state -+--ro additional-multi-lane-reporting* [lane] -| +--ro lane uint8 -| +--ro interface-names* -> /if:interfaces/interface/name -| +--ro rx-power? decimal64 - -``` - -``` - - +--ro tx-bias-current? decimal64 - - +--ro tx-power? decimal64 - -notifications: - - +---n transceiver-presence-change {or-feat:TRANSCEIVER-PRESENCE-CHANGE-SUPPORTED}? - - | +--ro transceiver-presence -> /port-transceivers/port-transceiver-data/present - | +--ro interface-name -> /port-transceivers/port-transceiver-data/interface-name - | +--ro port-number -> /port-transceivers/port-transceiver-data/port-number - | +--ro name? -> /port-transceivers/port-transceiver-data/name - - +---n transceiver-alarm-warning-notif {or-feat:TRANSCEIVER-ALARM-WARNING-SUPPORTED}? - - +--ro port-transceiver-alarm-warning-changes* [interface-name port-number] - - | +--ro interface-name -> /port-transceivers/port-transceiver-data/interface-name - | +--ro port-number -> /port-transceivers/port-transceiver-data/port-number - | +--ro name? -> /port-transceivers/port-transceiver-data/name - - | +--ro alarm-warning-states* [meas-type] - - | +--ro meas-type -> - | /port-transceivers/port-transceiver-data/alarm-warning-states/meas-type - - | +--ro state -> - | /port-transceivers/port-transceiver-data/alarm-warning-states/state - -``` - -## D.4.4 o-ran-mplane-int.yang module - -The format for the management plane interface module is provided below. - -``` - -module: o-ran-mplane-int - - +--rw mplane-info - - | +--rw searchable-mplane-access-vlans-info - - | | +--rw searchable-access-vlans* vlan-id - | | +--rw vlan-range - - | | | +--rw lowest-vlan-id? vlan-id - | | | +--rw highest-vlan-id? vlan-id - | | +--rw scan-interval? uint16 - - | +--rw m-plane-interfaces - - | | +--rw m-plane-sub-interfaces* [interface-name sub-interface] - - | | | +--rw interface-name -> /if:interfaces/interface/name - - | | | +--rw sub-interface -> /if:interfaces/interface[if:name = current()/../interface-name]/o-ran-int:vlan-id - - | | | +--ro client-info - -``` - -``` - -| | +--ro mplane-ipv4-info* [mplane-ipv4] -| | | +--ro mplane-ipv4 inet:ipv4-address -| | | +--ro port? inet:port-number -| | +--ro mplane-ipv6-info* [mplane-ipv6] -| | | +--ro mplane-ipv6 inet:ipv6-address -| | | +--ro port? inet:port-number -| | +--ro mplane-fqdn-info* [mplane-fqdn] -| | | +--ro mplane-fqdn inet:domain-name -| | | +--ro port? inet:port-number -| | x--ro mplane-fqdn* inet:domain-name -| +--rw m-plane-ssh-ports -| | +--rw call-home-ssh-port? inet:port-number -| | +--rw server-ssh-port? inet:port-number -| +--rw m-plane-tls-ports -| | +--rw call-home-tls-port? inet:port-number -| | +--rw server-tls-port? inet:port-number -+--rw configured-client-info -| +--rw mplane-ipv4-info* [mplane-ipv4] -| | +--rw mplane-ipv4 inet:ipv4-address -| | +--rw port? inet:port-number -| +--rw mplane-ipv6-info* [mplane-ipv6] -| | +--rw mplane-ipv6 inet:ipv6-address -| | +--rw port? inet:port-number -| +--rw mplane-fqdn-info* [mplane-fqdn] -| | +--rw mplane-fqdn inet:domain-name -| | +--rw port? inet:port-number -| x--rw mplane-fqdn* inet:domain-name -+--rw hello-params {tlscmn:hello-params}? -| +--rw tls-versions -| | +--rw min? identityref -| | +--rw max? identityref -| +--rw cipher-suites -| | +--rw cipher-suite* tlscsa:tls-cipher-suite-algorithm -+--rw ssh-transport-params {sshcmn:transport-params}? - -``` - -``` - -+--rw host-key -| +--rw host-key-alg* ssh-public-key-algorithm -+--rw key-exchange -| +--rw key-exchange-alg* ssh-key-exchange-algorithm -+--rw encryption -| +--rw encryption-alg* ssh-encryption-algorithm -+--rw mac -| +--rw mac-alg* ssh-mac-algorithm - -``` - -## D.4.5 o-ran-dhcp.yang module - -The format for the dhcp module is provided below. - -``` - -module: o-ran-dhcp -+--ro dhcp - +--ro interfaces* [interface] - | +--ro interface if:interface-ref - | +--ro dhcpv4 - | | +--ro client-id? string - | | +--ro type-code? uint16 - | | +--ro (duid-type)? - | | | +--:(duid-llt) - | | | | +--ro duid-llt-hardware-type? uint16 - | | | | +--ro duid-llt-time? yang:timeticks - | | | | +--ro duid-llt-link-layer-address? yang:mac-address - | | | +--:(duid-en) - | | | | +--ro duid-en-enterprise-number? uint32 - | | | | +--ro duid-en-identifier? string - | | | +--:(duid-ll) - | | | | +--ro duid-ll-hardware-type? uint16 - | | | | +--ro duid-ll-link-layer-address? yang:mac-address - | | | +--:(duid-uuid) - | | | | +--ro uuid? yang:uuid - | | | +--:(duid-unstructured) - | | | +--ro data? binary - -``` - -``` - -| | +--ro active-duid? binary -| | +--ro identity-association -| | | +--ro iaid? uint32 -| | | +--ro ia-type? string -| | +--ro dhcp-server-identifier? inet:ip-address -| | +--ro domain-name? string -| | +--ro domain-name-servers* inet:ip-address -| | +--ro interface-mtu? uint32 -| | +--ro default-gateways* inet:ip-address -| | +--ro netconf-clients* [client] -| | | +--ro client netconf-client-id -| | | +--ro optional-port? inet:port-number -| | +--ro ca-ra-servers* [servers] -| | | +--ro servers ca-ra-server-id -| | | +--ro port-number? inet:port-number -| | | +--ro ca-ra-path? string -| | | +--ro subject-name? string -| | | +--ro protocol? enumeration -| | +--ro segw* [gateways] -| | | +--ro gateways segw-id -| | +--ro event-collectors* event-collector-id {or-feat:NON-PERSISTENT- -MPLANE}? -| | +--ro event-collector-format? enumeration {or-feat:NON-PERSISTENT-MPLANE}? -| +--ro dhcpv6 -| x--ro dhcp-client-identifier -| | +--ro type-code? uint16 -| | +--ro (duid-type)? -| | +--:(duid-llt) -| | | +--ro duid-llt-hardware-type? uint16 -| | | +--ro duid-llt-time? yang:timeticks -| | | +--ro duid-llt-link-layer-addr? yang:mac-address -| | +--:(duid-en) -| | | +--ro duid-en-enterprise-number? uint32 -| | | +--ro duid-en-identifier? string -| | +--:(duid-ll) - -``` - -``` - -| | | +--ro duid-ll-hardware-type? uint16 -| | | +--ro duid-ll-link-layer-addr? yang:mac-address -| | +--:(duid-uuid) -| | | +--ro uuid? yang:uuid -| | +--:(duid-unknown) -| | +--ro data? binary -| +--ro dhcpv6-client-identifier -| | +--ro type-code? uint16 -| | +--ro (duid-type)? -| | +--:(duid-llt) -| | | +--ro duid-llt-hardware-type? uint16 -| | | +--ro duid-llt-time? yang:timeticks -| | | +--ro duid-llt-link-layer-address? yang:mac-address -| | +--:(duid-en) -| | | +--ro duid-en-enterprise-number? uint32 -| | | +--ro duid-en-identifier? string -| | +--:(duid-ll) -| | | +--ro duid-ll-hardware-type? uint16 -| | | +--ro duid-ll-link-layer-address? yang:mac-address -| | +--:(duid-uuid) -| | | +--ro uuid? yang:uuid -| | +--:(duid-unstructured) -| | | +--ro data? binary -| | +--ro active-duid? binary -| | +--ro identity-association -| | +--ro iaid? uint32 -| | +--ro ia-type? string -| x--ro dhcp-server-identifier -| | +--ro type-code? uint16 -| | +--ro (duid-type)? -| | +--:(duid-llt) -| | | +--ro duid-llt-hardware-type? uint16 -| | | +--ro duid-llt-time? yang:timeticks -| | | +--ro duid-llt-link-layer-addr? yang:mac-address - -``` - -``` - -| | +--:(duid-en) -| | | +--ro duid-en-enterprise-number? uint32 -| | | +--ro duid-en-identifier? string -| | +--:(duid-ll) -| | | +--ro duid-ll-hardware-type? uint16 -| | | +--ro duid-ll-link-layer-addr? yang:mac-address -| | +--:(duid-uuid) -| | | +--ro uuid? yang:uuid -| | +--:(duid-unknown) -| | +--ro data? binary -| +--ro dhcpv6-server-identifier -| | +--ro type-code? uint16 -| | +--ro (duid-type)? -| | | +--:(duid-llt) -| | | | +--ro duid-llt-hardware-type? uint16 -| | | | +--ro duid-llt-time? yang:timeticks -| | | | +--ro duid-llt-link-layer-address? yang:mac-address -| | | +--:(duid-en) -| | | | +--ro duid-en-enterprise-number? uint32 -| | | | +--ro duid-en-identifier? string -| | | +--:(duid-ll) -| | | | +--ro duid-ll-hardware-type? uint16 -| | | | +--ro duid-ll-link-layer-address? yang:mac-address -| | | +--:(duid-uuid) -| | | | +--ro uuid? yang:uuid -| | | +--:(duid-unstructured) -| | | +--ro data? binary -| | +--ro active-duid? binary -| +--ro domain-name? string -| +--ro domain-name-servers* inet:ip-address -| +--ro netconf-clients* [client] -| | +--ro client netconf-client-id -| | +--ro optional-port? inet:port-number -| +--ro ca-ra-servers* [servers] - -``` - -``` - -| | +--ro servers ca-ra-server-id -| | +--ro port-number? inet:port-number -| | +--ro ca-ra-path? string -| | +--ro subject-name? string -| | +--ro protocol? enumeration -| +--ro segw* [gateways] -| | +--ro gateways segw-id -| +--ro event-collectors* event-collector-id {or-feat:NON-PERSISTENT-MPLANE}? -| +--ro event-collector-format? enumeration {or-feat:NON-PERSISTENT-MPLANE}? - -+--ro m-plane-dhcp - x--ro private-enterprise-number? uint16 - +--ro private-enterprise-num? uint32 - +--ro vendor-class-data? string - -``` - -## D.4.6 o-ran-externalio.yang module - -The format for the external input/output module is provided below. - -``` - -module: o-ran-externalio - -+--rw external-io - +--ro input* [name] - | +--ro name string - | +--ro port-in? uint8 - | +--ro line-in? boolean - | +--ro related-o-ru-connector? -> /hw:hardware/component/name - - +--ro output* [name] - | +--ro name string - | +--ro port-out uint8 - | +--ro related-o-ru-connector? -> /hw:hardware/component/name - - +--rw output-setting* [name] - +--rw name -> /external-io/output/name - +--rw line-out? boolean - -notifications: - +---n external-input-change - +--ro current-input-notification - +--ro external-input* [name] - -``` - -``` - -+--ro name -> /external-io/input/name -+--ro io-port? -> /external-io/input/port-in -+--ro line-in? -> /external-io/input/line-in - -``` - -## D.4.7 o-ran-ald-port.yang module - -The format for the Antenna Line Device module is provided below - -``` - -module: o-ran-ald-port - - +--rw ald-ports-io - +--ro over-current-supported? boolean - +--ro ald-port* [name] - | +--ro name string - | +--ro port-id uint8 - | +--ro dc-control-support boolean - | +--ro dc-enabled-status? boolean - | +--ro supported-connector enumeration - | +--ro related-o-ru-connectors* -> /hw:hardware/component/name - +--rw ald-port-dc-control* [name] - +--rw name -> /ald-ports-io/ald-port/name - +--rw dc-enabled? boolean - - notifications: - - +---n overcurrent-report {OVERCURRENT-SUPPORTED}? - | +--ro overload-condition - | +--ro overloaded-ports* -> /ald-ports-io/ald-port/name - | +--ro related-o-ru-connectors* -> /hw:hardware/component/name - +---n dc-enabled-status-change - +--ro ald-port* [name] - +--ro name -> /ald-ports-io/ald-port/name - +--ro dc-enabled-status? -> /ald-ports-io/ald-port/dc-enabled-status - -``` - -## D.4.8 o-ran-ethernet-forwarding.yang module - -The format for the module o-ran Ethernet forwarding is provided below. - -``` - -module: o-ran-ethernet-forwarding - - +--rw ethernet-forwarding-table - -``` - -``` - -+--rw aging-time? uint32 - -+--ro filtering-entry* [address vlan-id] - +--ro address yang:mac-address - +--ro vlan-id uint16 - +--ro port-map* [port-ref] - +--ro port-ref -> /if:interfaces/interface/or-if:port-reference/port-number - -``` - -## D.5 Sync folder - -### D.5.1 o-ran-sync.yang module - -The format for the synchronisation module is provided below. - -``` - -module: o-ran-sync - -+--rw sync - -+--ro sync-status -| +--ro sync-state enumeration -| +--ro time-error? decimal64 -| +--ro frequency-error? decimal64 -| +--ro supported-reference-types* [item] -| +--ro item enumeration - -+--ro sync-capability -| +--ro sync-t-tsc? enumeration -| +--ro boundary-clock-supported? boolean -| +--ro extended-ql-tlv-supported? boolean - -+--rw ptp-config -| +--rw domain-number? uint8 -| +--rw accepted-clock-classes* [clock-classes] -| | +--rw clock-classes uint8 -| +--rw ptp-profile? enumeration -| +--rw delay-asymmetry? int16 -| +--rw g-8275-1-config -| | +--rw multicast-mac-address? enumeration -| | x--rw delay-asymmetry? int16 -| | +--rw sources* [local-port-number] {or-feat:PER-PORT-PTP-CONFIG}? - -``` - -``` - -| | +--rw local-port-number -> -/if:interfaces/interface/o-ran-int:port-reference/port-number - -| | +--rw time-transmitter-only? boolean -| | +--rw not-time-transmitter? boolean -| | +--rw local-priority? uint8 -| +--rw g-8275-2-config -| +--rw local-ip-port? -> /if:interfaces/interface/name -| +--rw master-ip-configuration* [local-priority] -| | +--rw local-priority uint8 -| | +--rw ip-address? string -| +--rw log-inter-sync-period? int8 -| +--rw log-inter-announce-period? int8 - -+--rw ptp-status -| +--rw reporting-period? uint8 -| +--ro lock-state? enumeration -| +--ro clock-class? uint8 -| +--ro clock-identity? string -| +--ro partial-timing-supported? boolean -| +--ro sources* [local-port-number] -| | +--ro local-port-number -> /if:interfaces/interface/o-ran-int:port-reference/port-number -| +--ro state? enumeration -| +--ro two-step-flag? boolean -| +--ro leap61? boolean -| +--ro leap59? boolean -| +--ro current-utc-offset-valid? boolean -| +--ro ptp-timescale? boolean -| +--ro time-traceable? boolean -| +--ro frequency-traceable? boolean -| +--ro source-clock-identity? string -| +--ro source-port-number? uint16 -| +--ro current-utc-offset? int16 -| +--ro priority1? uint8 -| +--ro clock-class? uint8 -| +--ro clock-accuracy? uint8 - -``` - -``` - -| +--ro offset-scaled-log-variance? uint16 -| +--ro priority2? uint8 -| +--ro grandmaster-clock-identity? string -| +--ro steps-removed? uint16 -| +--ro time-source? uint8 -+--rw synce-config -| +--rw acceptance-list-of-ssm* ssm-code -| +--rw ssm-timeout? uint16 -| +--rw sources* [local-port-number] {or-feat:PER-PORT-SYNCE-CONFIG}? -| +--rw local-port-number -> /if:interfaces/interface/o-ran-int:port-reference/port- -number -| +--rw ssm-send-enable? boolean -| +--rw local-priority? uint8 -+--rw synce-status -| +--rw reporting-period? uint8 -| +--ro lock-state? enumeration -| +--ro sources* [local-port-number] -| +--ro local-port-number -> -/if:interfaces/interface/o-ran-int:port-reference/port-number -| +--ro state? enumeration -| +--ro quality-level? uint8 -| +--ro enhanced-ssm-code? uint8 -| +--ro ssm-quality-level? ssm-code -| +--ro originator-synce-clock-id? string -| +--ro flag0-mixed-eec-eeec? boolean -| +--ro flag1-partial-chain? boolean -| +--ro number-of-eeec? uint8 -| +--ro number-of-eec? uint8 -+--rw gnss-config {GNSS}? -| +--rw enable? boolean -| +--rw satellite-constellation-list* enumeration -| +--rw polarity? enumeration -| +--rw cable-delay? uint16 -| +--rw anti-jam-enable? boolean {ANTI-JAM}? -+--rw gnss-status {GNSS}? - -``` - -``` - - +--rw reporting-period? uint8 - +--ro name? string - +--ro gnss-sync-status? enumeration - +--ro gnss-data - +--ro satellites-tracked? uint8 - +--ro location - | +--ro altitude? int64 - | +--ro latitude? geographic-coordinate-degree - | +--ro longitude? geographic-coordinate-degree - +--ro gnss-rx-time-error? decimal64 - - notifications: - +---n synchronization-state-change - | +--ro sync-state? -> /sync/sync-status/sync-state - +---n ptp-state-change - | +--ro ptp-state? -> /sync/ptp-status/lock-state - +---n synce-state-change - | +--ro synce-state? -> /sync/synce-status/lock-state - +---n gnss-state-change {GNSS}? - +--ro gnss-state? -> /sync/gnss-status/gnss-sync-status - -``` - -## D.6 Radio folder - -### D.6.1 o-ran-module-cap.yang module - -The format for the module capabilities module is provided below. - -``` - -module: o-ran-module-cap - - +--rw module-capability - +--ro ru-capabilities - | +--ro ru-supported-category? enumeration - | x--ro number-of-ru-ports? uint8 - | +--ro number-of-ru-ports-ul? uint8 - | +--ro number-of-ru-ports-dl? uint8 - | +--ro extended-number-of-ru-ports-ul? uint16 - | +--ro extended-number-of-ru-ports-dl? uint16 - -``` - -``` - -| +--ro number-of-spatial-streams? uint8 -| +--ro number-of-spatial-streams-dl? uint8 -| +--ro number-of-spatial-streams-ul? uint8 -| +--ro max-num-bands? uint16 -| x--ro max-power-per-pa-antenna? decimal64 -| x--ro min-power-per-pa-antenna? decimal64 -| +--ro fronthaul-split-option? uint8 -| +--ro format-of-iq-sample -| | +--ro dynamic-compression-supported? boolean -| | +--ro realtime-variable-bit-width-supported? boolean -| | +--ro compression-method-supported* [] -| | | +--ro iq-bitwidth? uint8 -| | | +--ro compression-type compression-type-def -| | | x--ro bitwidth? uint8 -| | | +--ro compression-method? compression-method-def -| | | x--ro (compression-format)? -| | | | +--:(no-compression) -| | | | +--:(block-floating-point) -| | | | | +--ro exponent? uint8 -| | | | +--:(block-floating-point-selective-re-sending) -| | | | | +--ro sres-exponent? uint8 -| | | | +--:(block-scaling) -| | | | | +--ro block-scalar? uint8 -| | | | +--:(u-law) -| | | | | +--ro comp-bit-width? uint8 -| | | | | +--ro comp-shift? uint8 -| | | | +--:(beam-space-compression) -| | | | | +--ro active-beam-space-coefficient-mask* uint8 -| | | | | +--ro block-scaler? uint8 -| | | | +--:(modulation-compression) -| | | | | +--ro csf? uint8 -| | | | | +--ro mod-comp-scaler? uint16 -| | | | +--:(modulation-compression-selective-re-sending) -| | | | | +--ro sres-csf? uint8 - -``` - -``` - -| | | | +--ro sres-mod-comp-scaler? uint16 -| | | +--ro fs-offset* uint8 {cf:CONFIGURABLE-FS-OFFSET}? -| | +--ro variable-bit-width-per-channel-supported? boolean -| | +--ro syminc-supported? boolean -| | +--ro regularization-factor-se-supported? boolean -| | +--ro little-endian-supported? boolean -| | +--ro st6-4byte-alignment-required? boolean -| | +--ro se6-rb-bit-supported? boolean -| +--ro ul-mixed-num-required-guard-rbs* [scs-a scs-b] -| | +--ro scs-a scs-config-type -| | +--ro scs-b scs-config-type -| | +--ro number-of-guard-rbs-ul? uint8 -| +--ro dl-mixed-num-required-guard-rbs* [scs-a scs-b] -| | +--ro scs-a scs-config-type -| | +--ro scs-b scs-config-type -| | +--ro number-of-guard-rbs-dl? uint8 -| +--ro energy-saving-by-transmission-blanks boolean -| +--ro eaxcid-grouping-capabilities {o-ran-module-cap:EAXC-ID-GROUP-SUPPORTED}? -| | +--ro max-num-tx-eaxc-id-groups? uint8 -| | +--ro max-num-tx-eaxc-ids-per-group? uint8 -| | +--ro max-num-rx-eaxc-id-groups? uint8 -| | +--ro max-num-rx-eaxc-ids-per-group? uint8 -| +--ro dynamic-transport-delay-management-supported boolean -| +--ro support-only-unique-ecpri-seqid-per-eaxc? boolean -| +--ro coupling-methods -| | +--ro coupling-via-frequency-and-time? boolean -| | +--ro coupling-via-frequency-and-time-with-priorities? boolean -| | +--ro coupling-via-frequency-and-time-with-priorities-optimized? boolean -| +--ro ud-comp-len-supported? boolean -| +--ro ext-ant-delay-capability? enumeration {or-feat:EXT-ANT-DELAY-CONTROL}? -| +--ro nack-supported? boolean -| +--ro st8-scs-supported? boolean -| +--ro energy-saving-capability-common-info {or-feat:TRX-CONTROL or or-feat:ADVANCED-SLEEP-MODE}? - -``` - -``` - -| | +--ro st8-ready-message-supported? boolean -| | +--ro sleep-duration-extension-supported? boolean -| | +--ro emergency-wake-up-command-supported? boolean -| +--ro bundle-offset-in-sell-supported? boolean -| +--ro max-beamId-tables-supported? uint8 {or-feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? -| +--ro min-hibernate-time-duration? uint32 {or-feat:DEEP-HIBERNATE}? -| +--ro max-hibernate-time-duration uint32 {or-feat:DEEP-HIBERNATE}? -+--ro band-capabilities* [band-number] -| +--ro band-number uint16 -| +--ro sub-band-info {o-ran-module-cap:LAA}? -| | +--ro sub-band-frequency-ranges* [sub-band] -| | | +--ro sub-band sub-band-string -| | | +--ro max-supported-frequency-dl? uint64 -| | | +--ro min-supported-frequency-dl? uint64 -| | +--ro number-of-laa-scariiers? uint8 -| | +--ro maximum-laa-buffer-size? uint16 -| | +--ro maximum-processing-time? uint16 -| | +--ro self-configure? boolean -| +--ro max-supported-frequency-dl? uint64 -| +--ro min-supported-frequency-dl? uint64 -| +--ro max-supported-bandwidth-dl? uint64 -| +--ro max-num-carriers-dl? uint32 -| +--ro max-carrier-bandwidth-dl? uint64 -| +--ro min-carrier-bandwidth-dl? uint64 -| +--ro supported-technology-dl* enumeration -| +--ro supported-filter-pass-bandwidths-dl -| | +--ro supported-filter-pass-bandwidths* [id] -| | | +--ro id uint32 -| | | +--ro type? enumeration -| | | +--ro carrier-bandwidth? uint64 -| | | +--ro filter-pass-bandwidth? uint64 -| +--ro tx-array-beamId-table-indexes* uint8 {or-feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? -| +--ro max-supported-frequency-ul? uint64 - -``` - -``` - -| +--ro min-supported-frequency-ul? uint64 -| +--ro max-supported-bandwidth-ul? uint64 -| +--ro max-num-carriers-ul? uint32 -| +--ro max-carrier-bandwidth-ul? uint64 -| +--ro min-carrier-bandwidth-ul? uint64 -| +--ro supported-technology-ul* enumeration -| +--ro supported-filter-pass-bandwidths-ul -| | +--ro supported-filter-pass-bandwidths* [id] -| | +--ro id uint32 -| | +--ro type? enumeration -| | +--ro carrier-bandwidth? uint64 -| | +--ro filter-pass-bandwidth? uint64 -| +--ro rx-array-beamid-table-indexes* uint8 {or-feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? -| -| +--ro max-num-component-carriers? uint8 -| x--ro max-num-bands? uint16 -| +--ro max-num-sectors? uint8 -| x--ro max-power-per-antenna? decimal64 -| x--ro min-power-per-antenna? decimal64 -| x--ro codebook-configuration_ng? uint8 -| x--ro codebook-configuration_n1? uint8 -| x--ro codebook-configuration_n2? uint8 - -+--rw rw-sub-band-info {o-ran-module-cap:LAA}? - - +--rw rw-number-of-laa-scarriers? -> -/module-capability/band-capabilities/sub-band-info/number-of-laa-scarriers - - +--rw rw-self-configure? -> -/module-capability/band-capabilities/sub-band-info/self-configure - -``` - -## D.6.2 o-ran-delay-management.yang module - -The format for the delay management module is provided below. - -``` - -module: o-ran-delay-management - - +--rw delay-management - - +--rw bandwidth-scs-delay-state* [bandwidth subcarrier-spacing] - | +--rw bandwidth bandwidth - | +--rw subcarrier-spacing uint32 - | +--ro ru-delay-profile - -``` - -``` - -| +--ro t2a-min-up uint32 -| +--ro t2a-max-up uint32 -| +--ro t2a-min-cp-dl uint32 -| +--ro t2a-max-cp-dl uint32 -| +--ro tcp-adv-dl uint32 -| +--ro ta3-min uint32 -| +--ro ta3-max uint32 -| +--ro t2a-min-cp-ul uint32 -| +--ro t2a-max-cp-ul uint32 -| +--ro ta3-min-ack? int32 -| +--ro ta3-max-ack? int32 -| +--ro ta3-min-2g? uint32 {feat:RRM-MEAS-REPORTING}? -| +--ro ta3-max-2g? uint32 {feat:RRM-MEAS-REPORTING}? - -+--rw non-default-ru-delay-profile* [delay-profile-id] {feat:BF-DELAY-PROFILE}? -| +--rw delay-profile-id uint16 -| +--rw non-default-bandwidth-scs-delay-state* [bandwidth subcarrier-spacing] -| +--rw bandwidth bandwidth -| +--rw subcarrier-spacing uint32 -| +--ro non-default-ru-delay-profile -| +--ro t2a-min-up? uint32 -| +--ro t2a-max-up? uint32 -| +--ro t2a-min-cp-dl? uint32 -| +--ro t2a-max-cp-dl? uint32 -| +--ro tcp-adv-dl? uint32 -| +--ro ta3-min? uint32 -| +--ro ta3-max? uint32 -| +--ro t2a-min-cp-ul? uint32 -| +--ro t2a-max-cp-ul? uint32 -| +--ro ta3-min-ack? int32 -| +--ro ta3-max-ack? int32 -| +--ro ta3-min-2g? uint32 {feat:RRM-MEAS-REPORTING}? -| +--ro ta3-max-2g? uint32 {feat:RRM-MEAS-REPORTING}? - -+--rw adaptive-delay-configuration {ADAPTIVE-RU-PROFILE}? -| +--rw bandwidth-scs-delay-state* [bandwidth subcarrier-spacing] - -``` - -``` - -| | +--rw bandwidth bandwidth -| | +--rw subcarrier-spacing uint32 -| | +--rw o-du-delay-profile -| | +--rw tla-max-up? uint32 -| | +--rw tx-max? uint32 -| | +--rw ta4-max? uint32 -| | +--rw rx-max? uint32 -| | +--rw tla-max-cp-dl? uint32 -| +--rw transport-delay -| +--rw t12-min? uint32 -| +--rw t12-max? uint32 -| +--rw t34-min? uint32 -| +--rw t34-max? uint32 -+--rw beam-context-gap-period? uint16 - -``` - -## D.6.3 o-ran-beamforming.yang module - -The format for the beamforming module is provided below. - -``` - -module: o-ran-beamforming - - +--ro beamforming-config - - x--ro per-band-config* [band-number] - - | +--ro band-number -> /mcap:module-capability/band-capabilities/band-number - | +--ro tx-array* -> /up:user-plane-configuration/tx-arrays/name - | +--ro rx-array* -> /up:user-plane-configuration/rx-arrays/name - | +--ro static-properties - - | | +--ro rt-bf-weights-update-support? boolean - | | +--ro (beamforming-type)? - - | | | +--:(frequency) - - | | | | +--ro frequency-domain-beams - - | | | | +--ro max-number-of-beam-ids uint16 - | | | | +--ro initial-beam-id uint16 - | | | | +--ro iq-bitwidth? uint8 - | | | | +--ro compression-type compression-type-def - | | | | x--ro bitwidth? uint8 - | | | | +--ro compression-method? bf-compression-method-def - -``` - -``` - -| | | | x--ro (compression-format)? -| | | | | +--:(no-compresison) -| | | | | +--:(block-floating-point) -| | | | | | +--ro exponent? uint8 -| | | | | +--:(block-floating-point-selective-re-sending) -| | | | | | +--ro sres-exponent? uint8 -| | | | | +--:(block-scaling) -| | | | | | +--ro block-scalar? uint8 -| | | | | +--:(u-law) -| | | | | | +--ro comp-bit-width? uint8 -| | | | | | +--ro comp-shift? uint8 -| | | | | +--:(beam-space-compression) -| | | | | | +--ro active-beam-space-coeficient-mask* uint8 -| | | | | | +--ro block-scaler? uint8 -| | | | | +--:(modulation-compression) -| | | | | | +--ro csf? uint8 -| | | | | | +--ro mod-comp-scaler? uint16 -| | | | | +--:(modulation-compression-selective-re-sending) -| | | | | | +--ro sres-csf? uint8 -| | | | | | +--ro sres-mod-comp-scaler? uint16 -| | | | +--ro additional-compression-method-supported* [] -| | | | | +--ro iq-bitwidth? uint8 -| | | | | +--ro compression-type compression-type-def -| | | | | x--ro bitwidth? uint8 -| | | | | +--ro compression-method? bf-compression-method-def -| | | | | x--ro (compression-format)? -| | | | | +--:(no-compresison) -| | | | | +--:(block-floating-point) -| | | | | | +--ro exponent? uint8 -| | | | | +--:(block-floating-point-selective-re-sending) -| | | | | | +--ro sres-exponent? uint8 -| | | | | +--:(block-scaling) -| | | | | | +--ro block-scalar? uint8 -| | | | | +--:(u-law) - -``` - -``` - -| | | | | | +--ro comp-bit-width? uint8 -| | | | | | +--ro comp-shift? uint8 -| | | | | +--:(beam-space-compression) -| | | | | | +--ro active-beam-space-coeficient-mask* uint8 -| | | | | | +--ro block-scaler? uint8 -| | | | | +--:(modulation-compression) -| | | | | | +--ro csf? uint8 -| | | | | | +--ro mod-comp-scaler? uint16 -| | | | | +--:(modulation-compression-selective-re-sending) -| | | | | | +--ro sres-csf? uint8 -| | | | | | +--ro sres-mod-comp-scaler? uint16 -| | | | +--ro beamforming-params-for-mul-beamId-tables* [] {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? -| | | | | +--ro max-number-of-beam-ids uint16 -| | | | | +--ro initial-beam-id uint16 -| | | +--:(time) -| | | | +--ro time-domain-beams -| | | | | +--ro max-number-of-beam-ids uint16 -| | | | | +--ro initial-beam-id uint16 -| | | | | +--ro frequency-granularity enumeration -| | | | | +--ro time-granularity enumeration -| | | | | +--ro iq-bitwidth? uint8 -| | | | | +--ro compression-type compression-type-def -| | | | | x--ro bitwidth? uint8 -| | | | | +--ro compression-method? bf-compression-method-def -| | | | | x--ro (compression-format)? -| | | | | | +--:(no-compresison) -| | | | | | +--:(block-floating-point) -| | | | | | | +--ro exponent? uint8 -| | | | | | +--:(block-floating-point-selective-re-sending) -| | | | | | | +--ro sres-exponent? uint8 -| | | | | | +--:(block-scaling) -| | | | | | | +--ro block-scalar? uint8 -| | | | | | +--:(u-law) -| | | | | | +--ro comp-bit-width? uint8 - -``` - -``` - -| | | | | | +--ro comp-shift? uint8 -| | | | | +--:(beam-space-compression) -| | | | | | +--ro active-beam-space-coeficient-mask* uint8 -| | | | | | +--ro block-scaler? uint8 -| | | | | +--:(modulation-compression) -| | | | | | +--ro csf? uint8 -| | | | | | +--ro mod-comp-scaler? uint16 -| | | | | +--:(modulation-compression-selective-re-sending) -| | | | | | +--ro sres-csf? uint8 -| | | | | | +--ro sres-mod-comp-scaler? uint16 -| | | | +--ro additional-compression-method-supported* [] -| | | | | | +--ro iq-bitwidth? uint8 -| | | | | | +--ro compression-type compression-type-def -| | | | | | x--ro bitwidth? uint8 -| | | | | | +--ro compression-method? bf-compression-method-def -| | | | | | x--ro (compression-format)? -| | | | | | +--:(no-compresison) -| | | | | | +--:(block-floating-point) -| | | | | | | +--ro exponent? uint8 -| | | | | | +--:(block-floating-point-selective-re-sending) -| | | | | | | +--ro sres-exponent? uint8 -| | | | | | +--:(block-scaling) -| | | | | | | +--ro block-scaler? uint8 -| | | | | | +--:(u-law) -| | | | | | | +--ro comp-bit-width? uint8 -| | | | | | | +--ro comp-shift? uint8 -| | | | | | +--:(beam-space-compression) -| | | | | | | +--ro active-beam-space-coeficient-mask* uint8 -| | | | | | | +--ro block-scaler? uint8 -| | | | | | +--:(modulation-compression) -| | | | | | | +--ro csf? uint8 -| | | | | | | +--ro mod-comp-scaler? uint16 -| | | | | | +--:(modulation-compression-selective-re-sending) -| | | | | | +--ro sres-csf? uint8 - -``` - -``` - -| | | | | +--ro sres-mod-comp-scaler? uint16 -| | | | +--ro beamforming-params-for-mul-beamId-tables* [] {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? -| | | | | +--ro max-number-of-beam-ids uint16 -| | | | | +--ro initial-beam-id uint16 -| | | +--:(hybrid) -| | | +--ro hybrid-beams -| | | | +--ro max-number-of-beam-ids uint16 -| | | | +--ro initial-beam-id uint16 -| | | | +--ro frequency-granularity enumeration -| | | | +--ro time-granularity enumeration -| | | | +--ro iq-bitwidth? uint8 -| | | | +--ro compression-type compression-type-def -| | | | x--ro bitwidth? uint8 -| | | | +--ro compression-method? bf-compression-method-def -| | | | x--ro (compression-format)? -| | | | | +--:(no-compression) -| | | | | +--:(block-floating-point) -| | | | | | +--ro exponent? uint8 -| | | | | +--:(block-floating-point-selective-re-sending) -| | | | | | +--ro sres-exponent? uint8 -| | | | | +--:(block-scaling) -| | | | | | +--ro block-scaler? uint8 -| | | | | +--:(u-law) -| | | | | | +--ro comp-bit-width? uint8 -| | | | | | +--ro comp-shift? uint8 -| | | | | +--:(beam-space-compression) -| | | | | | +--ro active-beam-space-coeficient-mask* uint8 -| | | | | | +--ro block-scaler? uint8 -| | | | | +--:(modulation-compression) -| | | | | | +--ro csf? uint8 -| | | | | | +--ro mod-comp-scaler? uint16 -| | | | | +--:(modulation-compression-selective-re-sending) -| | | | | | +--ro sres-csf? uint8 -| | | | | +--ro sres-mod-comp-scaler? uint16 - -``` - -``` - -| | | +--ro additional-compression-method-supported* [] -| | | | +--ro iq-bitwidth? uint8 -| | | | +--ro compression-type compression-type-def -| | | | x--ro bitwidth? uint8 -| | | | +--ro compression-method? bf-compression-method-def -| | | | x--ro (compression-format)? -| | | | +--: (no-compression) -| | | | +--: (block-floating-point) -| | | | | +--ro exponent? uint8 -| | | | +--: (block-floating-point-selective-re-sending) -| | | | | +--ro sres-exponent? uint8 -| | | | +--: (block-scaling) -| | | | | +--ro block-scalar? uint8 -| | | | +--: (u-law) -| | | | | +--ro comp-bit-width? uint8 -| | | | | +--ro comp-shift? uint8 -| | | | +--: (beam-space-compression) -| | | | | +--ro active-beam-space-coeficient-mask* uint8 -| | | | | +--ro block-scaler? uint8 -| | | | +--: (modulation-compression) -| | | | | +--ro csf? uint8 -| | | | | +--ro mod-comp-scaler? uint16 -| | | | +--: (modulation-compression-selective-re-sending) -| | | | | +--ro sres-csf? uint8 -| | | | | +--ro sres-mod-comp-scaler? uint16 -| | | +--ro beamforming-params-for-mul-beamid-tables* [] {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? -| | | | +--ro max-number-of-beam-ids uint16 -| | | | +--ro initial-beam-id uint16 -| | | +--ro fd-weights-mapping* [fd-weight-number] -| | | | +--ro fd-weight-number uint16 -| | | | +--ro array-elements* uint16 -| | | x--ro number-of-beams? uint16 -| | | +--ro p-dash? uint16 -| | | +--ro beam-information - -``` - -``` - -| +--ro number-of-beamforming-properties? uint16 -| +--ro beamforming-properties* [beam-id] -| +--ro beam-id uint16 -| +--ro beamforming-property -| +--ro beam-type? enumeration -| +--ro beam-group-id? uint16 -| x--ro coarse-fine-beam-relation* beam-reference -| x--ro neighbour-beams* beam-reference -| +--ro coarse-fine-beam-capability-based-relation* beam-capabilities-reference -| +--ro neighbour-beams-capability-based* beam-capabilities-reference -+--ro capabilities-groups* [capabilities-group] -| +--ro capabilities-group uint16 -| +--ro band-number? -> /mcap:module-capability/band-capabilities/band-number -| +--ro tx-array* -> /up:user-plane-configuration/tx-arrays/name -| +--ro rx-array* -> /up:user-plane-configuration/rx-arrays/name -| +--ro static-properties -| | +--ro rt-bf-weights-update-support? boolean -| | +--ro (beamforming-type)? -| | | +--:(frequency) -| | | | +--ro frequency-domain-beams -| | | | +--ro max-number-of-beam-ids uint16 -| | | | +--ro initial-beam-id uint16 -| | | | +--ro iq-bitwidth? uint8 -| | | | +--ro compression-type compression-type-def -| | | | x--ro bitwidth? uint8 -| | | | +--ro compression-method? bf-compression-method-def -| | | | x--ro (compression-format)? -| | | | | +--:(no-compresison) -| | | | | +--:(block-floating-point) -| | | | | | +--ro exponent? uint8 -| | | | | +--:(block-floating-point-selective-re-sending) -| | | | | | +--ro sres-exponent? uint8 -| | | | | +--:(block-scaling) -| | | | | | +--ro block-scalar? uint8 - -``` - -``` - -| | | | | +--:(u-law) -| | | | | | +--ro comp-bit-width? uint8 -| | | | | | +--ro comp-shift? uint8 -| | | | | +--:(beam-space-compression) -| | | | | | +--ro active-beam-space-coeficient-mask* uint8 -| | | | | | +--ro block-scaler? uint8 -| | | | | +--:(modulation-compression) -| | | | | | +--ro csf? uint8 -| | | | | | +--ro mod-comp-scaler? uint16 -| | | | | +--:(modulation-compression-selective-re-sending) -| | | | | | +--ro sres-csf? uint8 -| | | | | | +--ro sres-mod-comp-scaler? uint16 -| | | | | +--ro additional-compression-method-supported* [] -| | | | | | +--ro iq-bitwidth? uint8 -| | | | | | +--ro compression-type compression-type-def -| | | | | | x--ro bitwidth? uint8 -| | | | | | +--ro compression-method? bf-compression-method-def -| | | | | | x--ro (compression-format)? -| | | | | | +--:(no-compresison) -| | | | | | +--:(block-floating-point) -| | | | | | | +--ro exponent? uint8 -| | | | | | +--:(block-floating-point-selective-re-sending) -| | | | | | | +--ro sres-exponent? uint8 -| | | | | | +--:(block-scaling) -| | | | | | | +--ro block-scaler? uint8 -| | | | | | +--:(u-law) -| | | | | | | +--ro comp-bit-width? uint8 -| | | | | | | +--ro comp-shift? uint8 -| | | | | | +--:(beam-space-compression) -| | | | | | | +--ro active-beam-space-coeficient-mask* uint8 -| | | | | | | +--ro block-scaler? uint8 -| | | | | | +--:(modulation-compression) -| | | | | | | +--ro csf? uint8 -| | | | | | | +--ro mod-comp-scaler? uint16 - -``` - -``` - -| | | | | +--:(modulation-compression-selective-re-sending) -| | | | | +--ro sres-csf? uint8 -| | | | | +--ro sres-mod-comp-scaler? uint16 -| | | | +--ro beamforming-params-for-mul-beamid-tables* [] {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? -| | | | | +--ro max-number-of-beam-ids uint16 -| | | | | +--ro initial-beam-id uint16 -| | | +--:(time) -| | | | +--ro time-domain-beams -| | | | | +--ro max-number-of-beam-ids uint16 -| | | | | +--ro initial-beam-id uint16 -| | | | | +--ro frequency-granularity enumeration -| | | | | +--ro time-granularity enumeration -| | | | | +--ro iq-bitwidth? uint8 -| | | | | +--ro compression-type compression-type-def -| | | | | x--ro bitwidth? uint8 -| | | | | +--ro compression-method? bf-compression-method-def -| | | | | x--ro (compression-format)? -| | | | | | +--:(no-compresison) -| | | | | | +--:(block-floating-point) -| | | | | | | +--ro exponent? uint8 -| | | | | | +--:(block-floating-point-selective-re-sending) -| | | | | | | +--ro sres-exponent? uint8 -| | | | | | +--:(block-scaling) -| | | | | | | +--ro block-scaler? uint8 -| | | | | | +--:(u-law) -| | | | | | | +--ro comp-bit-width? uint8 -| | | | | | | +--ro comp-shift? uint8 -| | | | | | +--:(beam-space-compression) -| | | | | | | +--ro active-beam-space-coeficient-mask* uint8 -| | | | | | | +--ro block-scaler? uint8 -| | | | | | +--:(modulation-compression) -| | | | | | | +--ro csf? uint8 -| | | | | | | +--ro mod-comp-scaler? uint16 -| | | | | +--:(modulation-compression-selective-re-sending) - -``` - -``` - -| | | | | +--ro sres-csf? uint8 -| | | | | +--ro sres-mod-comp-scaler? uint16 -| | | | +--ro additional-compression-method-supported* [] -| | | | | +--ro iq-bitwidth? uint8 -| | | | | +--ro compression-type compression-type-def -| | | | | x--ro bitwidth? uint8 -| | | | | +--ro compression-method? bf-compression-method-def -| | | | | x--ro (compression-format)? -| | | | | +--:(no-compresison) -| | | | | +--:(block-floating-point) -| | | | | | +--ro exponent? uint8 -| | | | | +--:(block-floating-point-selective-re-sending) -| | | | | | +--ro sres-exponent? uint8 -| | | | | +--:(block-scaling) -| | | | | | +--ro block-scaler? uint8 -| | | | | +--:(u-law) -| | | | | | +--ro comp-bit-width? uint8 -| | | | | | +--ro comp-shift? uint8 -| | | | | +--:(beam-space-compression) -| | | | | | +--ro active-beam-space-coeficient-mask* uint8 -| | | | | | +--ro block-scaler? uint8 -| | | | | +--:(modulation-compression) -| | | | | | +--ro csf? uint8 -| | | | | | +--ro mod-comp-scaler? uint16 -| | | | | +--:(modulation-compression-selective-re-sending) -| | | | | +--ro sres-csf? uint8 -| | | | | +--ro sres-mod-comp-scaler? uint16 -| | | | +--ro beamforming-params-for-mul-beamid-tables* [] {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? -| | | | | +--ro max-number-of-beam-ids uint16 -| | | | | +--ro initial-beam-id uint16 -| | | +--:(hybrid) -| | | | +--ro hybrid-beams -| | | | | +--ro max-number-of-beam-ids uint16 -| | | | | +--ro initial-beam-id uint16 - -``` - -``` - -| | | +---ro frequency-granularity enumeration -| | | +---ro time-granularity enumeration -| | | +---ro iq-bitwidth? uint8 -| | | +---ro compression-type compression-type-def -| | | x---ro bitwidth? uint8 -| | | +---ro compression-method? bf-compression-method-def -| | | x---ro (compression-format)? -| | | | +---: (no-compression) -| | | | +---: (block-floating-point) -| | | | | +---ro exponent? uint8 -| | | | +---: (block-floating-point-selective-re-sending) -| | | | | +---ro sres-exponent? uint8 -| | | | +---: (block-scaling) -| | | | | +---ro block-scalar? uint8 -| | | | +---: (u-law) -| | | | | +---ro comp-bit-width? uint8 -| | | | | +---ro comp-shift? uint8 -| | | | +---: (beam-space-compression) -| | | | | +---ro active-beam-space-coeficient-mask* uint8 -| | | | | +---ro block-scaler? uint8 -| | | | +---: (modulation-compression) -| | | | | +---ro csf? uint8 -| | | | | +---ro mod-comp-scaler? uint16 -| | | | +---: (modulation-compression-selective-re-sending) -| | | | | +---ro sres-csf? uint8 -| | | | | +---ro sres-mod-comp-scaler? uint16 -| | | +---ro additional-compression-method-supported* [] -| | | | +---ro iq-bitwidth? uint8 -| | | | +---ro compression-type compression-type-def -| | | | x---ro bitwidth? uint8 -| | | | +---ro compression-method? bf-compression-method-def -| | | | x---ro (compression-format)? -| | | | | +---: (no-compression) -| | | | | +---: (block-floating-point) - -``` - -``` - -| | | | | +--ro exponent? uint8 -| | | | | +--: (block-floating-point-selective-re-sending) -| | | | | | +--ro sres-exponent? uint8 -| | | | | +--: (block-scaling) -| | | | | | +--ro block-scalar? uint8 -| | | | | +--: (u-law) -| | | | | | +--ro comp-bit-width? uint8 -| | | | | | +--ro comp-shift? uint8 -| | | | | +--: (beam-space-compression) -| | | | | | +--ro active-beam-space-coeficient-mask* uint8 -| | | | | | +--ro block-scaler? uint8 -| | | | | +--: (modulation-compression) -| | | | | | +--ro csf? uint8 -| | | | | | +--ro mod-comp-scaler? uint16 -| | | | | +--: (modulation-compression-selective-re-sending) -| | | | | +--ro sres-csf? uint8 -| | | | | +--ro sres-mod-comp-scaler? uint16 -| | | +--ro beamforming-params-for-mul-beamid-tables* [] {feat:MULTIPLE-BEAMID-TABLES-SUPPORTED}? -| | | | | +--ro max-number-of-beam-ids uint16 -| | | | | +--ro initial-beam-id uint16 -| | | | | +--ro fd-weights-mapping* [fd-weight-number] -| | | | | | +--ro fd-weight-number uint16 -| | | | | | +--ro array-elements* uint16 -| | | x--ro number-of-beams? uint16 -| | | +--ro p-dash? uint16 -| | +--ro beam-information -| | | +--ro number-of-beamforming-properties? uint16 -| | | +--ro beamforming-properties* [beam-id] -| | | | +--ro beam-id uint16 -| | | | +--ro beamforming-property -| | | | | +--ro beam-type? enumeration -| | | | | +--ro beam-group-id? uint16 -| | | | | x--ro coarse-fine-beam-relation* beam-reference -| | | | | x--ro neighbour-beams* beam-reference - -``` - -``` - -| +--ro coarse-fine-beam-capability-based-relation* beam-capabilities-reference -| +--ro neighbour-beams-capability-based* beam-capabilities-reference - -+--ro ue-specific-beamforming! -| x--ro max-number-of-ues? uint8 -| +--ro max-number-of-ues-15bit? uint16 -| +--ro channel-information-compression-method-supported* cf:ci-compression-method-def -{feat:CHANNEL-INFORMATION-COMPRESSION}? - -| +--ro dynamic-channel-information-compression-supported? boolean {feat:CHANNEL-INFORMATION-COMPRESSION}? - -+--ro operational-properties {MODIFY-BF-CONFIG}? -| +--ro number-of-writeable-beamforming-files uint8 -| +--ro update-bf-non-delete? boolean -| +--ro persistent-bf-files? boolean -| +--ro in-service-bf-update? boolean - -+--ro dmrs-bf-general-capabilities {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? -| +--ro equalization-data-scaling? EQ-SCALING-FUNCTION-TYPE {feat:DMRS-BF-EQ}? -| +--ro max-num-ues-supported? uint16 {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? -| +--ro ueid-max-layer-bits? uint8 {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? -| +--ro max-num-ueids? uint16 {feat:DMRS-BF-EQ or feat:DMRS-BF-NEQ}? - -+--ro beamforming-trough-attributes-supported? boolean -+--ro beamforming-trough-ue-channel-info-supported? boolean - -+--ro beam-tilt {BEAM-TILT}? -| +--ro predefined-beam-tilt-offset-information* [capabilities-group] -| | +--ro capabilities-group -> /beamforming-config/capabilities-groups/capabilities-group -| | +--ro elevation-tilt-offset-granularity uint8 -| | +--ro azimuth-tilt-offset-granularity uint8 -| | +--ro minimum-supported-elevation-tilt-offset int16 -| | +--ro maximum-supported-elevation-tilt-offset int16 -| | +--ro minimum-supported-azimuth-tilt-offset int16 -| | +--ro maximum-supported-azimuth-tilt-offset int16 -| | +--ro run-time-tilt-offset-supported boolean -| +--ro predefined-beam-tilt-state* [capabilities-group] -| | +--ro capabilities-group -> /beamforming-config/capabilities-groups/capabilities-group -| +--ro elevation-tilt-offset-angle int16 - -``` - -``` - - +--ro azimuth-tilt-offset-angle int16 - - rpcs: - - x---x activate-beamforming-config {MODIFY-BF-CONFIG}? - - | +---w input - - | | +---w beamforming-config-file string - - | | +---w band-number? -> /mcap:module-capability/band-capabilities/band-number - - | +---ro output - - | +---ro status enumeration - - | +---ro error-message? string - - x---x activate-beamforming-config-by-capability-group {MODIFY-BF-CONFIG}? - - | +---w input - - | | +---w beamforming-config-file string - - | | +---w capabilities-group -> /beamforming-config/capabilities-groups/capabilities-group - - | +---ro output - - | +---ro status enumeration - - | +---ro error-message? string - - x---x modify-predefined-beam-tilt-offset {BEAM-TILT}? - - | +---w input - - | | +---w predefined-beam-tilt-offset* [capabilities-group] {BEAM-TILT}? - - | | +---w capabilities-group -> /beamforming-config/capabilities-groups/capabilities-group - - | | +---w elevation-tilt-offset-angle? int16 - - | | +---w azimuth-tilt-offset-angle? int16 - - | +---ro output - - | +---ro status enumeration - - | +---ro error-message? string - - notifications: - - x---n beamforming-information-update - - | +---ro band-number? -> /mcap:module-capability/band-capabilities/band-number - - +---n capability-group-beamforming-information-update - - | +---ro capabilities-group -> /beamforming-config/capabilities-groups/capabilities-group - - +---n predefined-beam-tilt-offset-complete {BEAM-TILT}? - -``` - -``` - - +--ro predefined-beam-tilt-state* [capabilities-group] - +--ro capabilities-group -> -/beamforming-config/capabilities-groups/capabilities-group - - +--ro elevation-tilt-offset-angle int16 - - +--ro azimuth-tilt-offset-angle int16 - -``` - -## D.6.4 o-ran-laa.yang module - -The format for the LAA module is provided below. - -``` - -module: o-ran-laa - - +--rw laa-config! - - +--rw number-of-laa-scarrriers? uint8 - - +--rw multi-carrier-type? enumeration - - +--rw multi-carrier-tx? boolean - - +--rw multi-carrier-freeze? boolean - - +--rw laa-ending-dwpts-supported? boolean - - +--rw laa-starting-in-second-slot-supported? boolean - -``` - -## D.6.5 o-ran-antenna-calibration.yang module - -The format for the antenna calibration module is provided below. - -``` - -module: o-ran-antenna-calibration - - +--rw antenna-calibration - - +--ro antenna-calibration-capabilities - - | +--ro self-calibration-support? boolean - - | +--ro coordinated-calibration-support? boolean {O-RU-COORDINATED-ANT-CAL}? - - | +--ro number-of-calibration-symbols-per-block-dl uint8 - - | +--ro number-of-calibration-symbols-per-block-ul uint8 - - | +--ro interval-between-calibration-blocks? uint8 - - | +--ro number-of-calibration-blocks-per-step-dl uint8 - - | +--ro number-of-calibration-blocks-per-step-ul uint8 - - | +--ro interval-between-calibration-steps? uint8 - - | +--ro number-of-calibration-steps uint8 - - | +--ro calibration-period? uint16 {O-RU-COORDINATED-ANT-CAL}? - - | +--ro configured-preparation-timer-supported? boolean {O-RU-COORDINATED-ANT-CAL}? - - +--rw self-calibration-policy - -``` - -``` - -| +--rw self-calibration-allowed? boolean -| +--rw coordinated-calibration-allowed? boolean {O-RU-COORDINATED-ANT-CAL}? -| +--rw coordinated-ant-calib-prep-timer? uint8 {O-RU-COORDINATED-ANT-CAL}? -| +--rw coordinated-calibration-multiple-time-resources-allowed? boolean {O-RU-COORDINATED-ANT-CAL and O-RU-COORDINATED-ANT-CAL-MULTIPLE-TIME-RESOURCE}? - - +--ro antenna-calibration-multiple-time-resource {O-RU-COORDINATED-ANT-CAL and O-RU-COORDINATED-ANT-CAL-MULTIPLE-TIME-RESOURCE}? - - +--ro antenna-calibration-multiple-time-resource-list* [antenna-calibration-time-resource-index] - - +--ro number-of-calibration-symbols-per-block-dl uint8 - +--ro number-of-calibration-symbols-per-block-ul uint8 - +--ro interval-between-calibration-blocks? uint8 - +--ro number-of-calibration-blocks-per-step-dl uint8 - +--ro number-of-calibration-blocks-per-step-ul uint8 - +--ro interval-between-calibration-steps? uint8 - +--ro number-of-calibration-steps uint8 - +--ro calibration-period? uint16 {O-RU-COORDINATED-ANT-CAL}? - +--ro antenna-calibration-time-resource-index uint8 - -``` - -rpcs: - -``` - -+---x start-antenna-calibration - - +---w input - - | +---w symbol-bitmask-dl string - | +---w symbol-bitmask-ul string - | +---w slot-bitmask-dl string - | +---w slot-bitmask-ul string - | +---w frame-bitmask-dl string - | +---w frame-bitmask-ul string - | +---w calibration-step-size uint8 - | +---w calibration-step-number uint8 - | +---w start-sfn uint16 - - +--ro output - - +--ro status enumeration - - +--ro error-message? string - -``` - -## notifications: - -``` - -+---n antenna-calibration-required - -| +--ro dl-calibration-frequency-chunk* [] -| | +--ro start-calibration-frequency-dl? uint64 -| | +--ro end-calibration-frequency-dl? uint64 -| +--ro ul-calibration-frequency-chunk* [] -| | +--ro start-calibration-frequency-ul? uint64 -| | +--ro end-calibration-frequency-ul? uint64 - -+---n antenna-calibration-coordinated {O-RU-COORDINATED-ANT-CAL}? - -| +--ro dl-calibration-frequency-chunk* [] -| | +--ro start-calibration-frequency-dl? uint64 -| | +--ro end-calibration-frequency-dl? uint64 -| +--ro ul-calibration-frequency-chunk* [] -| | +--ro start-calibration-frequency-ul? uint64 -| | +--ro end-calibration-frequency-ul? uint64 -| +--ro symbol-bitmask-dl string -| +--ro symbol-bitmask-ul string -| +--ro slot-bitmask-dl string -| +--ro slot-bitmask-ul string -| +--ro frame-bitmask-dl string -| +--ro frame-bitmask-ul string -| +--ro calibration-step-size uint8 -| +--ro calibration-step-number uint8 -| +--ro start-sfn uint16 - -+---n antenna-calibration-result - -| +--ro status enumeration -| +--ro detailed-reason? string - -+---n antenna-calibration-multiple-time-resource-params {O-RU-COORDINATED-ANT-CAL and O-RU-COORDINATED-ANT-CAL-MULTIPLE-TIME-RESOURCE}? - -| +--ro antenna-calibration-time-resource-index? uint8 -| -| +--ro dl-calibration-frequency-chunk* [] -| | +--ro start-calibration-frequency-dl? uint64 -| | +--ro end-calibration-frequency-dl? uint64 -| -| +--ro ul-calibration-frequency-chunk* [] -| -| +--ro start-calibration-frequency-ul? uint64 - -``` - -``` - -+--ro end-calibration-frequency-ul? uint64 - -``` - -## D.6.6 o-ran-shared-cell.yang module - -The format for the module o-ran shared cell is provided below. - -``` - -module: o-ran-shared-cell - - +--rw shared-cell - +--ro shared-cell-module-cap - | +--ro t-copy uint32 - | +--ro t-combine uint32 - | +--ro t-combine-net? uint32 - | +--ro scs-supported* o-ran-cmn:scs-config-type {FHM}? - | +--ro combine-delay-per-scs* [scs] - | | +--ro scs o-ran-cmn:scs-config-type - | | +--ro t-combine-net? uint32 - | | +--ro t-combine? uint32 - | +--ro ta3-prime-max-upper-range uint32 - | +--ro max-number-node-copy-and-combine uint8 - | +--ro max-number-eaxcid-copy uint8 - | +--ro max-number-eaxcid-combine uint8 - | +--ro copy-combine-capacity-per-port* [port-number] - | | +--ro port-number -> /if:interfaces/interface/o-ran-int:port-reference/port-number - | | +--ro copy-combine-capacity-type-id? -> ../../copy-combine-capacity-type/id - | +--ro copy-combine-capacity-type* [id] - | | +--ro id uint8 - | | +--ro max-num-of-nodes-combine-in-port? uint8 - | | +--ro max-num-of-eaxc-id-combine-in-port? uint16 - | +--ro eaxc-id-group-capabilities {FHM}? - | | +--ro max-num-rx-eaxc-id-groups? uint8 - | | +--ro max-num-rx-eaxc-ids-per-group? uint8 - | +--ro compression-method-supported* [] {FHM}? - | | +--ro iq-bitwidth? uint8 - | | +--ro compression-type compression-type-def - | | x--ro bitwidth? uint8 - | | +--ro compression-method? compression-method-def - -``` - -``` - -| | x--ro (compression-format)? -| | +--:(no-compresison) -| | +--:(block-floating-point) -| | | +--ro exponent? uint8 -| | +--:(block-floating-point-selective-re-sending) -| | | +--ro sres-exponent? uint8 -| | +--:(block-scaling) -| | | +--ro block-scalar? uint8 -| | +--:(u-law) -| | | +--ro comp-bit-width? uint8 -| | | +--ro comp-shift? uint8 -| | +--:(beam-space-compression) -| | | +--ro active-beam-space-coeficient-mask* uint8 -| | | +--ro block-scaler? uint8 -| | +--:(modulation-compression) -| | | +--ro csf? uint8 -| | | +--ro mod-comp-scaler? uint16 -| | +--:(modulation-compression-selective-re-sending) -| | | +--ro sres-csf? uint8 -| | | +--ro sres-mod-comp-scaler? uint16 -| +--ro multi-cell-in-cascade-mode-supported? boolean - -+--rw shared-cell-config - +--rw (shared-cell-copy-combine-mode)? - | +--:(COMMON) - | | +--rw shared-cell-copy-entities* [name] - | | | +--rw name string - | | | +--rw odu-id? string {feat:SHARED-ORU-MULTI-ODU}? - | | | +--rw sro-id? -> /or-user:users/user/sro-id {feat:SHARED-ORU-MULTI-OPERATOR}? - | | | +--rw north-node-processing-element? -> /o-ran-pe:processing-elements/ru-elements/name - | | | +--rw south-node-processing-elements* -> /o-ran-pe:processing-elements/ru-elements/name - | | | +--rw shared-cell-copy-uplane-config {FHM}? - | | | | +--rw tx-eaxc-id* [eaxc-id] - | | | | | +--rw eaxc-id uint16 - -``` - -``` - -| | | +--rw rx-eaxc-id* [eaxc-id] -| | | | +--rw eaxc-id uint16 -| | | x--rw downlink-radio-frame-offset? uint32 -| | | x--rw downlink-sfn-offset? int16 -| | +--rw shared-cell-combine-entities* [name] -| | | +--rw name string -| | | +--rw odu-id? string {feat:SHARED-ORU-MULTI-ODU}? -| | | +--rw sro-id? -> /or-user:users/user/sro-id -{feat:SHARED-ORU-MULTI-OPERATOR}? -| | +--rw north-node-processing-element? -> /o-ran-pe:processing-elements/ru- -elements/name -| | +--rw south-node-processing-elements* -> /o-ran-pe:processing-elements/ru- -elements/name -| | +--rw scs? o-ran-cmn:scs-config-type -| | +--rw ta3-prime-max? uint32 -| | +--rw tx-duration? uint32 -| | +--rw shared-cell-combine-uplane-config {FHM}? -| | | +--rw rx-eaxc-id* [eaxc-id] -| | | | +--rw eaxc-id uint16 -| | | | +--rw number-of-prb? uint16 -| | | | +--rw cp-ul-section-type* enumeration -| | | | +--rw compression-method -| | | | | +--rw iq-bitwidth? uint8 -| | | | | +--rw compression-type compression-type-def -| | | | | x--rw bitwidth? uint8 -| | | | | +--rw compression-method? compression-method-def -| | | | | x--rw (compression-format)? -| | | | | +--:(no-compression) -| | | | | +--:(block-floating-point) -| | | | | | +--rw exponent? uint8 -| | | | | +--:(block-floating-point-selective-re-sending) -| | | | | | +--rw sres-exponent? uint8 -| | | | | +--:(block-scaling) -| | | | | | +--rw block-scalar? uint8 -| | | | | +--:(u-law) -| | | | | | +--rw comp-bit-width? uint8 - -``` - -``` - -| | | | +--rw comp-shift? uint8 -| | | +--:(beam-space-compression) -| | | | +--rw active-beam-space-coeficient-mask* uint8 -| | | | +--rw block-scaler? uint8 -| | | +--:(modulation-compression) -| | | | +--rw csf? uint8 -| | | | +--rw mod-comp-scaler? uint16 -| | | +--:(modulation-compression-selective-re-sending) -| | | | +--rw sres-csf? uint8 -| | | | +--rw sres-mod-comp-scaler? uint16 -| | +--rw downlink-radio-frame-offset uint32 -| | +--rw downlink-sfn-offset int16 -| | +--rw n-ta-offset uint32 -| | x--rw number-of-prb uint16 -| +--:(SELECTIVE-BEAM-ID) {FHM and SELECTIVE-BEAM-ID}? -| +--rw shared-cell-copy-entities-selective-beam-id* [name] -| | +--rw name string -| | +--rw odu-id? string {feat:SHARED-ORU-MULTI-ODU}? -| | +--rw sro-id? -> /or-user:users/user/sro-id -{feat:SHARED-ORU-MULTI-OPERATOR}? -| | +--rw north-node-processing-element? -> /o-ran-pe:processing-elements/ru- -elements/name -| | +--rw south-node-processing-elements* -> /o-ran-pe:processing-elements/ru- -elements/name -| | +--rw mapping-table-for-selective-beam-id* [global-beam-id south-node-processing- -elements] -| | | +--rw global-beam-id uint16 -| | | +--rw south-node-processing-elements -> /o-ran-pe:processing-elements/ru- -elements/name -| | | +--rw local-beam-id? uint16 -| | +--rw shared-cell-copy-uplane-config {FHM}? -| | | +--rw tx-eexc-id* [eexc-id] -| | | | +--rw eexc-id uint16 -| | | +--rw rx-eexc-id* [eexc-id] -| | | | +--rw eexc-id uint16 -| | | x--rw downlink-radio-frame-offset? uint32 -| | | x--rw downlink-sfn-offset? int16 - -``` - -``` - -| +---rw shared-cell-combine-entities-for-selective-beam-id* [name] -| -| +---rw name string -| -| +---rw odu-id? string {feat:SHARED-ORU-MULTI-ODU}? -| -| +---rw sro-id? -> /or-user:users/user/sro-id -{feat:SHARED-ORU-MULTI-OPERATOR}? -| -| +---rw north-node-processing-element? -> /o-ran-pe:processing-elements/ru- -elements/name -| -| +---rw south-node-processing-elements* -> /o-ran-pe:processing-elements/ru- -elements/name -| -| +---rw scs? o-ran-cmn:scs-config-type -| -| +---rw ta3-prime-max? uint32 -| -| +---rw tx-duration? uint32 -| -| +---rw shared-cell-combine-uplane-config {FHM}? -| -| +---rw rx-eexc-id* [eexc-id] -| -| | +---rw eexc-id uint16 -| -| | +---rw number-of-prb? uint16 -| -| | +---rw cp-ul-section-type* enumeration -| -| | +---rw compression-method -| -| | +---rw iq-bitwidth? uint8 -| -| | +---rw compression-type compression-type-def -| -| | x---rw bitwidth? uint8 -| -| | +---rw compression-method? compression-method-def -| -| | x---rw (compression-format)? -| -| | +---:(no-compression) -| -| | +---:(block-floating-point) -| -| | | +---rw exponent? uint8 -| -| | +---:(block-floating-point-selective-re-sending) -| -| | | +---rw sres-exponent? uint8 -| -| | +---:(block-scaling) -| -| | | +---rw block-scalar? uint8 -| -| | +---:(u-law) -| -| | | +---rw comp-bit-width? uint8 -| -| | | +---rw comp-shift? uint8 -| -| | +---:(beam-space-compression) -| -| | | +---rw active-beam-space-coeficient-mask* uint8 -| -| | | +---rw block-scaler? uint8 - -``` - -``` - -| | +--:(modulation-compression) -| | | +--rw csf? uint8 -| | | +--rw mod-comp-scaler? uint16 -| | +--:(modulation-compression-selective-re-sending) -| | | +--rw sres-csf? uint8 -| | | +--rw sres-mod-comp-scaler? uint16 -| | +--rw downlink-radio-frame-offset uint32 -| | +--rw downlink-sfn-offset int16 -| | +--rw n-ta-offset uint32 -| | x--rw number-of-prb uint16 -| +--rw max-num-rx-eaxc-ids-per-group? -> /shared-cell/shared-cell-module-cap/eaxc-id-group-capabilities/max-num-rx-eaxc-ids-per-group {FHM}? -| +--rw max-num-rx-eaxc-id-groups? -> /shared-cell/shared-cell-module-cap/eaxc-id-group-capabilities/max-num-rx-eaxc-id-groups {FHM}? -| +--rw rx-eaxc-id-group* [representative-rx-eaxc-id] {FHM}? -| | +--rw representative-rx-eaxc-id uint16 -| | +--rw member-rx-eaxc-id* uint16 -| +--rw enhanced-t-combine-enabled? boolean {feat:ENHANCED-T-COMBINE}? -| +--rw multiple-scs-in-eaxc-used? boolean {feat:MULTIPLE-SCS-IN-EAXC}? - -``` - -## D.6.7 o-ran-laa-operations.yang module - -The format for the LAA operations module is provided below. - -``` - -rpcs: - rpcs: - +---x start-measurements {mcap:LAA}? - +---w input - | +---w band-config* [band-number] - | | +---w band-number band-num - | | +---w channel-center-frequency* uint16 - | +---w duration-per-channel? uint16 - | +---w maximum-response-time? uint16 - +---ro output - +---ro band-config* [band-number] - +---ro band-number band-num - -``` - -``` - - +--ro carrier-center-frequency* uint16 - +--ro status? enumeration - +--ro error-message? string - -notifications: - - +---n measurement-result {mcap:LAA}? - +--ro band-result* [band-number] - +--ro band-number band-num - +--ro measurement-success? boolean - +--ro failure-message? enumeration - +--ro channel-result* [measured-channel] - +--ro measured-channel uint16 - +--ro occupancy-ratio? uint8 - +--ro average-rssi? int8 - -``` - -## D.6.8 o-ran-frequency-band-measurement.yang module - -The format for the frequency band measurement module is provided below. - -``` - -module: o-ran-frequency-band-measurement - - +--ro measurement-capability - +--ro measurement-bands-supported* [measurement-band-num] - | +--ro measurement-band-num uint8 - | +--ro frequencys-range-supported* [lower-frequency] - | | +--ro lower-frequency uint32 - | | +--ro upper-frequency? uint32 - | +--ro measurement-bandwidth* measurement-bandwidth - +--ro in-service-measurement? boolean - +--ro in-service-measurement-only-carrier-freq? boolean - +--ro supported-measurement-points* enumeration - - rpcs: - - +---x received-power-measurement-request - +---w input - | +---w measurement-bandwidth measurement-bandwidth - -``` - -``` -| +---w measurement-start-frequency* uint32 -| +---w rx-array* -> /up:user-plane-configuration/rx-arrays/name - -+--ro output - +--ro status enumeration - +--ro error-message? string - +--ro wait-time? uint32 - +--ro measurement-id? uint8 - -notifications: - -+---n power-measurement-result - +--ro status enumeration - +--ro error-message? string - +--ro received-power-measurement* [measurement-frequency] - | +--ro measurement-frequency uint32 - | +--ro measurement-bandwidth measurement-bandwidth - | +--ro received-power? decimal64 - +--ro measurement-id? uint8 -``` - ---- - -# Annex E (normative): Corresponding YANG Module Definition - -The definitions for each method and resource defined in the clauses of the present document include normative references to schema nodes, notifications and remote procedure calls (RPCs) defined in a set of corresponding YANG models. The YANG models for present document are available in the file O-RAN.WG4.TS.MP-YANGs-R005-v20.00.zip which can be downloaded from the O-RAN Alliance website . - -If there is any conflict between the schema nodes, notifications and remote procedure calls (RPCs) defined in the YANG models and the accompanying description in the present document, the definition of the YANG models shall take precedence. - -Table E-1 lists all of the O-RAN Alliance YANG models included in the O-RAN.WG4.TS.MP-YANGs-R005-v20.00.zip file and their corresponding version numbers and revision dates. - -**Table E-1: O-RAN Alliance defined YANG model versions to be used with this present document.** - -| YANG Module Name | Namespace | Revision Date | Description Version | -|------------------------------------|------------------------------------------|----------------------|----------------------------| -| o-ran-ald | urn:o-ran:ald:1.0 | 2021-12-01 | 1.2.0 | -| o-ran-ald-port | urn:o-ran:ald-port:1.0 | 2025-04-14 | 13.2.0 | -| o-ran-beamforming | urn:o-ran:beamforming:1.0 | 2025-04-14 | 17.1.0 | -| o-ran-antenna-calibration | urn:o-ran:antcal:1.0 | 2024-04-15 | 7.2.0 | -| o-ran-certificates | urn:o-ran:certificates:1.0 | 2025-12-22 | 20.0.0 | -| o-ran-common-identity-refs | urn:o-ran:wg1identityref:1.0 | 2022-08-15 | 1.0.0 | -| o-ran-common-yang-types | urn:o-ran:common-yang-types:1.0 | 2025-04-14 | 3.0.0 | -| o-ran-compression-factors | urn:o-ran:compression-factors:1.0 | 2025-04-14 | 16.1.0 | -| o-ran-delay-management | urn:o-ran:delay:1.0 | 2025-04-14 | 16.1.0 | -| o-ran-dhcp | urn:o-ran:dhcp:1.0 | 2024-08-12 | 10.1.0 | -| o-ran-ecpri-delay | urn:o-ran:message5:1.0 | 2024-12-23 | 17.0.0 | -| o-ran-ethernet-forwarding | urn:o-ran:ethernet-fwd:1.0 | 2021-12-01 | 3.1.0 | -| o-ran-externalio | urn:o-ran:external-io:1.0 | 2023-08-14 | 13.0.0 | -| o-ran-fan | urn:o-ran:fan:1.0 | 2025-08-11 | 19.0.0 | -| o-ran-file-management | urn:o-ran:file-management:1.0 | 2024-12-23 | 17.0.0 | -| o-ran-fm | urn:o-ran:fm:1.0 | 2024-08-12 | 15.1.0 | -| o-ran-frequency-band-measurement | urn:o-ran:frequency-band-measurement:1.0 | 2024-08-12 | 16.0.0 | -| o-ran-hardware | urn:o-ran:hardware:1.0 | 2025-04-14 | 18.0.0 | -| o-ran-ieee802-dot1q-cfm | urn:o-ran:o-ran-ieee802-dot1q-cfm:1.0 | 2023-04-10 | 12.0.0 | -| o-ran-interfaces | urn:o-ran:interfaces:1.0 | 2025-12-22 | 20.0.0 | -| o-ran-laa | urn:o-ran:laa:1.0 | 2022-08-15 | 1.2.0 | -| o-ran-laa-operations | urn:o-ran:laa-operations:1.0 | 2023-08-14 | 13.0.0 | -| o-ran-lbm | urn:o-ran:lbm:1.0 | 2024-08-12 | 1.4.0 | -| o-ran-module-cap | urn:o-ran:module-cap:1.0 | 2025-04-14 | 18.0.0 | -| o-ran-mplane-int | urn:o-ran:mplane-interfaces:1.0 | 2025-12-22 | 20.0.0 | -| o-ran-operations | urn:o-ran:operations:1.0 | 2024-12-23 | 15.1.0 | -| o-ran-performance-management | urn:o-ran:performance-management:1.0 | 2025-12-22 | 20.0.0 | -| o-ran-processing-element | urn:o-ran:processing-element:1.0 | 2024-12-23 | 10.1.0 | -| o-ran-shared-cell | urn:o-ran:shared-cell:1.0 | 2024-12-23 | 17.0.0 | -| o-ran-software-management | urn:o-ran:software-management:1.0 | 2025-08-11 | 11.2.0 | -| o-ran-supervision | urn:o-ran:supervision:1.0 | 2021-12-05 | 11.0.0 | -| o-ran-sync | urn:o-ran:sync:1.0 | 2025-08-11 | 15.1.0 | -| o-ran-trace | urn:o-ran:trace:1.0 | 2022-08-15 | 1.2.0 | -| o-ran-transceiver | urn:o-ran:transceiver:1.0 | 2025-12-22 | 20.0.0 | -| o-ran-troubleshooting | urn:o-ran:troubleshooting:1.0 | 2025-04-14 | 18.0.0 | -| o-ran-udp-echo | urn:o-ran:udpecho:1.0 | 2019-02-04 | 1.0.0 | -| o-ran-uplane-conf | urn:o-ran:uplane-conf:1.0 | 2025-12-22 | 20.0.0 | -| o-ran-usermgmt | urn:o-ran:user-mgmt:1.0 | 2024-08-12 | 16.0.0 | -| o-ran-ves-subscribed-notifications | urn:o-ran:ves-sn:1.0 | 2020-12-10 | 5.0.0 | -| o-ran-wg4-features | urn:o-ran:wg4feat:1.0 | 2025-12-22 | 20.0.0 | - -Table E-2 lists all of the externally defined YANG models and their corresponding revision dates. These are not included in the O-RAN.WG4.TS.MP-YANGs-R005-v20.00.zip file. - -**Table E-2: Externally defined YANG model versions to be used with the present document.** - -| YANG Module Name | Namespace | Revision Date | -|-------------------------------|-----------------------------------------------------------|----------------------| -| iana-crypt-hash | urn:ietf:params:xml:ns:yang:iana-crypt-hash | 2014-08-06 | -| iana-hardware | urn:ietf:params:xml:ns:yang:iana-hardware | 2018-03-13 | -| iana-if-type | urn:ietf:params:xml:ns:yang:iana-if-type | 2017-01-19 | -| iana-tls-cipher-suite-algs | urn:ietf:params:xml:ns:yang:iana-tls-cipher-suite-algs | 2024-10-16 | -| iana-ssh-encryption-algs | urn:ietf:params:xml:ns:yang:iana-ssh-encryption-algs | 2024-10-16 | -| iana-ssh-key-exchange-algs | urn:ietf:params:xml:ns:yang:iana-ssh-key-exchange-algs | 2024-10-16 | -| iana-ssh-mac-algs | urn:ietf:params:xml:ns:yang:iana-ssh-mac-algs | 2024-10-16 | -| iana-ssh-public-key-algs | urn:ietf:params:xml:ns:yang:iana-ssh-public-key-algs | 2024-10-16 | -| ieee802-dot1x | urn:ieee:std:802.1X:yang:ieee802-dot1x | 2020-02-18 | -| ieee802-dot1x-types | urn:ieee:std:802.1X:yang:ieee802-dot1x-types | 2020-02-18 | -| ieee802-dot1x-eapol | urn:ieee:std:802.1X:yang:ieee802-dot1x-eapol | 2022-05-25 | -| ieee802-types | urn:ieee:std:802.1Q:yang:ieee802-types | 2020-06-04 | -| ietf-crypto-types | urn:ietf:params:xml:ns:yang:ietf-crypto-types | 2024-10-10 | -| ietf-datastores | urn:ietf:params:xml:ns:yang:ietf-datastores | 2018-02-14 | -| ietf-dhcpv6-common | urn:ietf:params:xml:ns:yang:ietf-dhcpv6-common | 2021-01-29 | -| ietf-dhcpv6-types | urn:ietf:params:xml:ns:yang:ietf-dhcpv6-types | 2018-09-04 | -| ietf-hardware | urn:ietf:params:xml:ns:yang:ietf-hardware | 2018-03-13 | -| ietf-inet-types | urn:ietf:params:xml:ns:yang:ietf-inet-types | 2013-07-15 | -| ietf-interfaces | urn:ietf:params:xml:ns:yang:ietf-interfaces | 2018-02-20 | -| ietf-ip | urn:ietf:params:xml:ns:yang:ietf-ip | 2018-02-22 | -| ietf-keystore | urn:ietf:params:xml:ns:yang:ietf-keystore | 2024-10-10 | -| ietf-netconf | urn:ietf:params:xml:ns:netconf:base:1.0 | 2011-06-01 | -| ietf-netconf-acm | urn:ietf:params:xml:ns:yang:ietf-netconf-acm | 2018-02-14 | -| ietf-netconf-monitoring | urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring | 2010-10-04 | -| ietf-netconf-notifications | urn:ietf:params:xml:ns:yang:ietf-netconf-notifications | 2012-02-06 | -| ietf-network-instance | urn:ietf:params:xml:ns:yang:ietf-network-instance | 2019-01-21 | -| ietf-restconf | urn:ietf:params:xml:ns:yang:ietf-restconf | 2017-01-26 | -| ietf-subscribed-notifications | urn:ietf:params:xml:ns:yang:ietf-subscribed-notifications | 2019-09-09 | -| ietf-system | urn:ietf:params:xml:ns:yang:ietf-system | 2014-08-06 | -| ietf-ssh-common | urn:ietf:params:xml:ns:yang:ietf-ssh-common | 2024-10-10 | -| ietf-ssh-server | urn:ietf:params:xml:ns:yang:ietf-ssh-server | 2024-10-10 | -| ietf-tls-common | urn:ietf:params:xml:ns:yang:ietf-tls-common | 2024-10-10 | -| ietf-tls-server | urn:ietf:params:xml:ns:yang:ietf-tls-server | 2024-10-10 | -| ietf-truststore | urn:ietf:params:xml:ns:yang:ietf-truststore | 2024-10-10 | -| ietf-yang-library | urn:ietf:params:xml:ns:yang:ietf-yang-library | 2019-01-04 | -| ietf-yang-schema-mount | urn:ietf:params:xml:ns:yang:ietf-yang-schema-mount | 2019-01-14 | -| ietf-yang-types | urn:ietf:params:xml:ns:yang:ietf-yang-types | 2013-07-15 | -| ietf-x509-cert-to-name | urn:ietf:params:xml:ns:yang:ietf-x509-cert-to-name | 2014-12-10 | -| ieee802-dot1q-cfm | urn:ieee:std:802.1Q:yang:ieee802-dot1q-cfm | 2022-01-19 | -| ieee802-dot1q-cfm-types | urn:ieee:std:802.1Q:yang:ieee802-dot1q-cfm-types | 2020-06-04 | -| ieee802-dot1q-types | urn:ieee:std:802.1Q:yang:ieee802-dot1q-types | 2020-06-04 | - -NOTE: Use of ietf-dhcpv6-types with a revision date of 2018-09-04 is deprecated. The reference to ietf-dhcpv6-common with a revision date of 2021-01-29 will be superseded once the corresponding RFCs are published. - ---- - -## Annex F (informative): Out of scope functionality - -### F.1 Out of scope functionality - -The present document does not include specific functions that, during the specification definition process, have been highlighted as useful enhancements. The list of identified functionalities is shown below. This can be used to prioritize future specification work within O-RAN Alliance. - -- 1) Beam Id field interpretation for various types of beamforming. -- 2) Redundancy and failover scenario. -- 3) Shared cell support for IP-defined flows. -- 4) Enhancements to better align with O-RAN Alliance O1 specification. -- 5) Shared cell topology discovery for architectures that do not ensure Ethernet frames sent between a south-node and a north-node are bridged by an O-RU. -- 6) Void. -- 7) Dynamic sharing of O-RU carriers between multiple O-DUs. -- 8) Enhanced adaptive delay operation that allows O-RU delay adaptation without requiring active carriers to be disabled. -- 9) The role of a Shared Resource Operator's SMO when operating with a multi-operator O-RU operated by a third party Shared O-RU Host. - -## Annex G (informative): o-ran-lbm.yang and o-ran-ieee802-dot1q-cfm.yang co-ordination - -### G.1 Model structure - -In o-ran-lbm.yang model, the YANG structure is illustrated in Figure G-1: - -![Figure G-1: o-ran-lbm YANG structure diagram](880668411e1ba0cfd367413b7cb706cf_img.jpg) - -The diagram illustrates the hierarchical structure of the o-ran-lbm.yang YANG model. It consists of nested boxes representing the hierarchy: - -- maintenance-domain** (outermost box) - - maintenance-association** (middle box) - - component-list** (inner box) - - remote-meps** (innermost box) - - maintenance-association-endpoints** (innermost box) - -Figure G-1: o-ran-lbm YANG structure diagram - -Figure G-1: o-ran-lbm YANG structure - -In contrast, the ieee-802-dot1q-cfm YANG model has the structure illustrated in Figure G-2 - -![Figure G-2: ieee-802-dot1q-cfm YANG structure diagram](c557fa1bd8f95590281c8ba61b175740_img.jpg) - -The diagram illustrates the hierarchical structure of the ieee-802-dot1q-cfm.yang YANG model. It consists of two separate hierarchical structures: - -- maintenance-domain** (left structure) - - maintenance-association(s)** (inner box) - - maintenance-association-mep** (innermost box) -- maintenance-group** (right structure) - - meps** (inner box) - - mep-db** (innermost box) - - interface, vid** (innermost box) - -Figure G-2: ieee-802-dot1q-cfm YANG structure diagram - -Figure G-2: ieee-802-dot1q-cfm YANG structure - -The ieee802-dot1q-cfm.yang model is not standalone model. It needs to be extended to work with ieee-dot1q-cfm-bridge model or some equivalent. In o-ran-ieee802-dot1q-cfm.yang, **interface** and **primary-vid** are used to map to o-ran-interfaces (where an l2vlan interface implicitly maps to an IEEE 802.1Q bridge equivalent). - -In both models, the maintenance association endpoint (mep) is mapped to a l2vlan interface (bridge interface) and the l2vlan interface is mapped to a bridge equivalent. In the /cfm/maintenance-group/mep, **interface** and **primary-vid** represents an ieee equivalent bridge instance. Association towards an ieee equivalent bridge is represented by parameter on MEP in maintenance -group. - -In o-ran-lbm.yang model, **remote-meps** and **maintenance-association-end-points** are defined on the same level under schema node **component-list**. **Remote-meps** contains MEP IDs that are in the MA but are located remotely (opposite to local) and **maintenance-association-endpoint** contains mep configurations. - -In ieee-802-dot1q-cfm model, information of meps is in two lists, **maintenance-domain** and **maintenance-group**. - -The ieee-802-dot1q-cfm **maintenance-association-mep** list contains **mep-ids** for all configured meps that are in the MA. The **mep** list in **maintenance-group** list has mep configurations for example mac address, enable parameter etc. And in ieee-802-dot1q-cfm model, each mep contains a **mep-db** list used to store information of its remote-meps. In ieee-802-dot1q, if a maintenance-group is defined, remote MEP state machine is instantiated to all remote MEPs that are presented in **maintenance-association-mep** list (that is active). - -## G.2 Mapping between models - -To map the a o-ran-lbm.yang configuration to ieee-802-dot1q-cfm, the level of **component** which represent a bridge will be mapped to ieee equivalent bridge instance which is represented by the combination of value **interface** and **primary-vid**. The **remote-meps** leaf-list in o-ran-lbm.yang will be mapped to the **maintenance-association-mep** list in ieee-802-dot1q-cfm model. - -To map the a o-ran-lbm.yang configuration to ieee-802-dot1q-cfm, **maintenance-group** will be generated for each MD, MA combination. **maintenance-association-end-point** configuration in o-ran-lbm.yang will be mapped as /**maintenance-group/MEP** in ieee-802-dot1q-cfm model, as illustrated in Tables G-1, G-2, G-3, and G-4 describe the mapping between the two YANG schemas. - -**Table G-1 High level relationship between o-ran-lbm.yang and ieee-802-dot1q-cfm.yang** - -| Model: o-ran-lbm.yang | Model: ieee-802-dot1q-cfm.yang | Comment | -|-----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------|---------------------------------------------------------------------| -| /md-data-definition/maintenance-domain | /cfm/maintenance-domain | | -| /md-data-definition/maintenance-domain/maintenance-association | /cfm/maintenance-domain/maintenance-association | | -| /md-data-definition/maintenance-domain/maintenance-association/component-list | To parameter interface and vid in /cfm/maintenance-group/mep | | -| /md-data-definition/maintenance-domain/maintenance-association/component-list/Remote-meps | /cfm/maintenance-domain/maintenance-association/maintenance-association-mep | The local mep ids in lbm model need to be added as well. | -| /md-data-definition/maintenance-domain/maintenance-association/component-list/maintenance-association-end-point | /cfm/maintenance-group/mep | For each MD MA combination, a new maintenance-group can be created. | - -**Table G-2 Mapping between maintenance-domain in o-ran-lbm.yang and ieee-802-dot1q-cfm.yang** - -| List: /md-data-definition/maintenance-domain | List: /cfm/maintenance-domain | Comment | -|----------------------------------------------|-------------------------------|---------| -| id | md-id | | -| name | md-name | | -| md-level | md-level | | - -**Table G-3 Mapping between maintenance-association lists in o-ran-lbm.yang and ieee-802-dot1q-cfm.yang** - -| /md-data-definition/maintenance-domain/maintenance-association | | /cfm/maintenance-domain/maintenance-association | Comment | -|----------------------------------------------------------------|------------------------------|----------------------------------------------------------------------------|------------| -| parameter | sub-parameter | parameter | | -| id | | ma-id | | -| name | | ma-name | | -| Component-list | | | Not mapped | -| | Component-id | | Not mapped | -| | name | /cfm/maintenance-group/mep/interface | | -| | vid | /cfm/maintenance-group/mep/vid | | -| | Remote-meps | cfm/maintenance-domain/maintenance-association/maintenance-association-mep | | -| | Maintenance-association-meps | /cfm/maintenance-group/mep | | - -**Table G-4 Mapping MEP configuration between o-ran-lbm.yang and ieee-802-dot1q-cfm.yang** - -| /md-data-definiton/
maintenance-domain/
maintenance-association
/component-list
/maintenance-association-
end-point
| | /cfm/maintenance-group/
mep
| Comment | -|------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|----------------------------------------|-----------------------------| -| parameter | sub-parameter | parameter | | -| Mep-identifier | | mep-id | | -| interface | | interface | Augmented in ieee-dot1q-cfm | -| Primary-vid | | vid | Augmented in ieee-dot1q-cfm | -| Administrative-state | | enabled | | -| Mac-address | | Mac-address | | -| loopback | | N/A | | -| | Reply-transmitted | State/mep-lbr-out | | - -## Annex (informative): - -### Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2019.03.11 | 01.00 | Summary:
First published version based on import of xRAN M-Plane | -| 2019.07.03 | 02.00 | Summary:
Bug fixes and correction to v01.00
Addition of new functionality, including:
  • - Beam tilting
  • - Antenna calibration
  • - CU plane monitoring
  • - Trace
  • - 3GPP MV PnP support
  • - QSFP
| -| 2020.04.17 | 03.00 | Summary:
Bug fixes and correction to v02.00
  • - NACM table
  • - Clarifications on CU plane monitoring
  • - Clarification of allowed sync state transitions
  • - Corrections on overall Start-Up operation
Addition of new functionality, including:
  • - Shared cell
  • - Dying Gasp
  • - PM Counters
  • - Config Notification
  • - Hybrid Health Warning
  • - Dynamic Spectrum Sharing
  • - Grouping of eAxC-IDs
  • - Energy, Power and Environmental statistics
| -| 2020.08.10 | 04.00 | Summary:
Bug fixes and correction to v03.00:
  • - Removing reference to Component eAxC references
  • - Correcting YANG references for Non-Delay Managed Traffic
  • - Correcting YANG references for enhanced U-Plane markings
  • - Correcting YANG references in tables B.3 and C.3
  • - Clarify that validation of configuration is based on criteria which includes definitions in this document
  • - Clarification of supervision
Addition of new functionality, including:
  • - Enabling static configuration of PRACH or SRS
  • - Supporting flexible TDD pattern configuration
  • - To allow for different delay management parameters for C and U-plane
  • - New sync capabilities for reporting estimated time and frequency errors
  • - New capability to define compression on an endpoint basis
  • - New optional feature - configurable full-scale offset
  • - New optional feature - eAxC specific gain correction
  • - New optional feature - TX gain reference level control
| - -| Date | Revision | Description | -|------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2020.12.10 | 05.00 | Summary:
Bug fixes and correction to v04.00:
  • - Clarify operation of default account for certificate access
  • - Clarify operation of supervision in lock state
  • - Clarify PRACH patterns
  • - Fixing copy/paste errors in the S-plane PTP status definitions
  • - Corrected omissions from optional feature table
  • - Clarify centre bandwidth parameter
  • - Replace previous NMS terms with SMO
  • - Corrections to C/U plane monitoring for FHM
Addition of new functionality, including:
  • - New NACM permissions for SMO and hybrid O-DU
  • - New optional feature for performing pnfRegistration
  • - New optional feature for configured YANG subscriptions sent over JSON/REST
  • - Updating mandatory cipher to AES128-CTR
  • - Bandwidth management to avoid over-subscription of O-RU resources
  • - Shared cell with selective Tx/Rx using Beam ID
  • - Cascaded FHM Operation
  • - New capability to support co-ordinated (self) antenna calibration
| -| 2021.03.22 | 06.00 | Summary:
Bug fixes and correction to v05.00:
  • - Clarify operation of non-persistent M-Plane
  • - Clarify operation of Software Management
  • - Clarify operation of VLAN-IDs for C- and U-Plane
  • - Clarify eaxc-id assignment
  • - Clarify connectivity checks operation
  • - Clarify procedures for deleting configuration
  • - Clarify plug and play certificate aspects
Addition of new functionality, including:
  • - Optional support of NETCONF/TLS
  • - Supporting IPv6 only O-RUs
| -| 2021.07.26 | 07.00 | Summary:
Bug fixes and correction to v06.00:
  • - Clarify operation of configured subscriptions
  • - Clarify username syntax
  • - Correction to log management sequence diagrams
  • - Clarify delay management operation
  • - Clarify DHCP operation
  • - Clarify operation of antenna calibration
  • - Correct errors in text that describes low-level-[tr]x-endpoint creation
  • - Clarify modify parameter section
  • - Clarify revision and namespace compatibility handling
  • - Clarify certificate enrolment
  • - Clarify non-persistent operation with software management
  • - Clarify Fault Management Activation
  • - Correction to enable multiple measurements to be included in a notification
  • - Clarify operation of NETCONF supervision with multiple NETCONF clients
Addition of new functionality, including:
  • - External antenna delay handling
  • - Optional capability to optimize VLAN discovery
  • - Capability to support C-Plane limits for packet processing
  • - FTPES based file transfer
  • - TD-RSSI measurement capability
  • - EPE measurements for current and voltage
  • - Configurable timer for co-ordinated antenna calibration
  • - Enhanced antenna calibration using different resource sets
| - -| Date | Revision | Description | -|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2021.10.19 | 07.00.01 | Merge of CRs: CIS-032, CIS-033, CIS-034 | -| 2021.10.28 | 07.01 | Updates to align with ETSI PAS Process | -| 2021.10.25 | 07.01.01 | Merge of CRs: MAV-028, CIS-030, HST-001, CIS-036, SAM-065, SAM-066, SAM-064, CIS-031, SAM-059, NOK-082 | -| 2021.12.01 | 08.00 | Summary:
Bug fixes and correction to v07.01:
  • - Deprecate leaf-list(frequency-table) and to add a new list(frequency-bin-table)
  • - Correction for C-plane message limits
  • - Antenna Calibration schema node reference corrections
  • - Clarification for fault ID 24
  • - DHCP Clarifications
  • - Clarifications to log management
  • - Adding SCS information for FHM Combine operations
  • - Shared cell performance management corrections
Addition of new functionality, including:
  • - Introduction of alarm-type
  • - Enable IANA Private Enterprise Number to be used as Vendor Code in software management
  • - Boundary Clock function
  • - Capability for supporting multi cell operation
  • - Compression support for Section Type 6
  • - Mandatory support of TLS, PKIX, and FTPES
  • - Supporting multiple transport session types simultaneously
  • - Shared cell enhancements introducing t-combine-net and tx-duration
| -| 2021.12.15 | 08.00.01 | Merge of CRs: CIS-038, CIS-039 | -| 2022.03.01 | 08.00.02 | Merge of CRs: FJT-006, SAM-077, NOK-087, CIS-041, CIS-042, INT-019, CIS-040, ERI-041 | -| 2022.03.09 | 08.00.03 | Merge of CRs: FJT-007, CIS-044, CIS-043, ERI-038 | -| 2022.03.16 | 08.00.04 | Merge of CRs: NOK-105, ERI-039, NOK-100m NOK-102, STL-001, ALS-005 | -| 2022.04.18 | 09.00 | Summary:
Bug fixes and correction to v08.00:
  • - Updates to align with new O-RAN template
  • - Updates to references to align with DFT guidelines
  • - Clarify rejection of invalid configuration
  • - Alignment of eventName field and "remote-file-path" format
  • - Clarification of handling of an O-RU capable of BF and non-BF modes
  • - Update clause cases
  • - Correction Clarification of S-Plane interactions with M-Plane during Startup, and Loss/Recovery of Synchronisation
  • - Normative Reference to YANG models
  • - Clarify NACM and user management
  • - Clarify NETCONF monitoring and <get-schema>
  • - Reset handling clarification
  • - NETCONF event stream clarification
  • - Software Management Clarification
  • - SSH and SFTP host key clarification
  • - SFTP host key correction
Addition of new functionality, including:
  • - New feature flag for O-RU to indicate support of 4-Byte aligned section type 6
  • - New build-content-download leaf and associated software management definition
  • - New list for historical alarms
  • - Defining loopback message to group destination address
| -| 2022.06.29 | 09.00.01 | Merge of CRs: SYM-0006, NOK-0107, NOK-0101, ERI-0047, FJT-0011, ERI-0052, SAM-0085, FJT-0012, NOK-0090, NOK-0099 | -| 2022.07.06 | 09.00.02 | Merge of CRs: NOK-0113, CIS-0046, ERI-0050, NOK-0109, CIS-0050, CIS-0049, | - -| Date | Revision | Description | -|------|----------|-------------| -| | | SAM-0086 | - -| Date | Revision | Description | -|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2022.07.13 | 09.00.03 | Merge of CRs: NOK-0116, CIS-0047, CIS-0048 | -| 2022.07.14 | 09.00.04 | Merge of CRs: QCM-0040, ERI-0054, ERI-0049 | -| 2022.07.18 | 09.00.05 | Addressing all review comments received | -| 2022.08.15 | 10.00 | Summary:
Bug fixes and correction to v09.00:
  • - Clarify contradicting statements with regard to TLS 1.2
  • - Array element fault source and fault source improvements
  • - Software management clarification
  • - Correction for module privileges
  • - Persistence of configured subscription
  • - Correction for O-RU call home port
  • - Clarify operation of filter based on xpath
  • - Clarify operation with factory default software
  • - Clarification to path definition for file management
  • - Remove LAA "capability" option from Table C.3-1
  • - Password for FTPES server
  • - Call home with multiple A/AAAA records
  • - PKI Clarifications
  • - Hybrid management clarifications
Addition of new functionality, including:
  • - Identifying default NETCONF accounts
  • - Introduction of O-RU connectors
  • - Configuration to map from certificates to NETCONF usernames
  • - Update SFP compliance codes
  • - DHCPv4 Client DUID/IAID definition
  • - IEEE 802.1X Port based access control
  • - Shared O-RU
| -| 2022.10.12 | 10.00.01 | Merge of CRs: ERI-0061, QCM-0046 | -| 2022.10.21 | 10.00.02 | Merge of CRs: ETR-0015, NOK-0122, CIS-0058, CIS-0053, CIS-0052, CIS-0051, NOK-0118, ERI-0064, NOK-0121 | -| 2022.11.01 | 10.00.03 | Merge of CRs: ERI-0063, ERI-0060, ADI-0001, NEC-0018, NOK-0120, ERI-0065 | -| 2022.11.03 | 10.00.04 | Merge of CR: CIS-0055 | -| 2022.11.07 | 10.00.05 | Merge of CR: CIS-0060 | -| 2022.12.05 | 11.00 | Bug fixes and correction to v10.00:
  • - Correcting hardware access privileges for SMO
  • - Correct fault ID 31 cancel condition and source
  • - Correct o-ran-laa YANG tree
  • - Add voltage and current EPE stats to Annex B.5
  • - Deprecation of power parameters for shared O-RU
  • - Annex C.2 and C.3 reformat tables
  • - Future topics annex
  • - Clarification for handling of multiple interfaces per optical port
  • - Clarify writable-running datastore
  • - Clarification for PM measurement objects modification
  • - Energy saving state clarification
  • - Clarification of active parameter
  • - Adding IEEE 802.1X recommendation
Addition of new functionality, including:
  • - U-Plane-only DL mode
  • - SW build level file integrity check
  • - Session supervision with session-id
  • - Network energy savings
| -| 2023.02.17 | 11.00.01 | Merge of CRs: NOK-0130, CIS-0061, ATT-0011, CIS-0065, SOL-0013, FJT-0022, FJT-0023, NOK-0119, ERI-0070, NOK-0123, ADI-0005, CIS-0064 | -| 2023.02.23 | 11.00.02 | Merge of CRs: SOL-0016, FJT-0024, SAM-0095, CIS-0067 | - -| Date | Revision | Description | -|------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2023.03.02 | 11.00.03 | Merge of CRs: SAM-0084, MAV-0031, CIS-0066, CIS-0062 | -| 2023.03.08 | 11.00.04 | Merge of CRs: CIS-0068, SAM-0096, ERI-0055, ERI-0067 | -| 2023.04.10 | 12.00 | Summary:
Bug fixes and correction to v11.00:
  • - Correct inconsistency in clause 9.1.3
  • - Update reference to DHCPv6 Options
  • - Remove import of ietf-crypto-types@2019-04-29
  • - Confirmation of backwards compatibility
  • - Clarification of the accounts name
  • - DHCP options clarification
  • - Clarify default operation of 802.1X
  • - Correction Radio Timing for Copy
  • - Correction to shared cell counters
  • - Clarification of PRACH repetition
  • - Clarified operational state for layer 3 configuration
  • - Remove erroneous use of SZTP
Addition of new functionality, including:
  • - 802.1X as Mandatory
  • - Add supported SCSes of FHM
  • - Allow all NETCONF clients to change their own password
  • - NB IoT
  • - Advanced endpoint capability reporting for NB-IoT & other scenarios
  • - Allow CA/RA server on non-production VLAN
  • - Introduce ietf-truststore YANG model
  • - Introduce SE11-WITH-CONTINUITY-BIT-SUPPORT
  • - Addition of feature non-scheduled-ueid
  • - Continuity Check Message support
  • - U-plane message processing limits
| -| 2023.06.26 | 12.00.01 | Merge of CRs: MAV-0033, CIS-0072, ERI-0083, ERI-0084, NOK-0135, CIS-0073, NOK-0140, FJT-0031, CIS-0071, ERI-0079, ERI-0080, MAV-0034 | -| 2023.07.04 | 12.00.02 | Merge of CRs: ERI-0077, NOK-0137, ERI-0082 | -| 2023.07.10 | 12.00.03 | Review comment corrections | -| 2023.07.12 | 12.00.04 | Merge of CRs: SOL-0022, ERI-0085, NEC-0023 | -| 2023.07.14 | 12.00.05 | Updating YANG trees | -| 2023.07.17 | 12.00.06 | Addressing comment spreadsheets | -| 2023.07.19 | 12.00.07 | Template updates | -| 2023.08.14 | 13.00 | Summary:
Bug fixes and correction to v12.00:
  • - Correction of feature name NON-PERSISTENT-MPLANE
  • - Clarifying multiple instances of "is responsible"
  • - Improve M-Plane stack illustration
  • - Correct LBM terminology
  • - Correction to CSV file format definitions
  • - Keep alive for call home O-RU controllers
  • - Clarify alarm dependency
  • - Clarify carrier state's relationship to synchronisation state
Addition of new functionality, including:
  • - Add optional Major severity for alarm 1
  • - Call home re-activation
  • - Add optional Power Amplifier critical severity to alarm #27
  • - New availability status for [tr]x-array-carriers
  • - O-RU connectors for ALD ports and External IO ports
  • - Combine delays per SCS
  • - Disabling sequence number handling
  • - Enhanced Network Energy Savings functionality
| -| 2023.10.24 | 13.00.01 | Merge of CRs: MAV-0032, CIS-0074, CIS-0075, ERI-0086, CIS-0076 | - -| Date | Revision | Description | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2023.11.01 | 13.00.02 | Merge of CRs: ERI-0091, ERI-0092 | -| 2023.11.06 | 13.00.03 | Merge of CRs: CIS-0078, SOL-0014, NEC-0025, SAM-0105 | -| 2023.11.07 | 13.00.04 | Merge of CRs: ERI-0090, NOK-0152 | -| 2023.12.11 | 14.00 | Summary:
Bug fixes and correction to v13.00:
  • - Reformat table 6.9.3-1
  • - Align Table B.1-1 with YANG Model
  • - Clarify the information which software slot is active is reset persistent
  • - Clarification for TAC level energy saving
  • - Model name and namespace clarifications
  • - C/U Plane Monitoring Clarification
  • - Fault management clarifications
Addition of new functionality, including:
  • - New alarm for Rx signal quality
  • - Adding ietf-netconf to imported folder
  • - New feature SE23-PRB-BLOCK-MODE-SUPPORT
  • - Performance Counter for Shared Cell
  • - Energy saving by Data Layer Control
  • - bundleOffset in SE 11
| -| 2024.02.26 | 14.00.01 | Merge of CRs: NOK-0157, NOK-0155, NOK-0144, ERI-0097, ERI-0101, CIS-0077, ERI-0089, NOK-0145, CIS-0081 | -| 2024.03.04 | 14.00.02 | Merge of CRs: QCM-0067, CIS-0079, NOK-0158, QCM-0064, ERI-0094, RMI-0001 | -| 2024.03.11 | 14.00.03 | Merge of CRs: SAM-0117, NOK-0165, CIS-0083, ERI-0093, NOK-0150, QCM-0076, SAM-0099 | -| 2024.03.18 | 14.00.05 | Merge of CR: CIS-0085 | -| 2024.04.15 | 15.00 | Summary:
Bug fixes and correction to v14.00:
  • - SWM Installation status enum fix
  • - Clarify port transceiver source for alarm 29
  • - Clarify user and certificate persistent information
  • - Correct cross reference to CUS-Plane DSS clause
  • - Clarify carrier activation deactivation sequence
  • - Clarifying NETCONF transaction operation
  • - PM parameter handling
  • - Lock O-RU clarifications
  • - Clarifying array element terminology
  • - Handling long DHCP options
Addition of new functionality, including:
  • - Per-port S-plane configuration of a multi-port O-RU
  • - O-RU payload frame size per ethernet interface
  • - Extended QL TLV Support
  • - O-RU TCP MSS Configuration
  • - Multiple beamId table support
  • - M-Plane TRX Control energy savings
  • - Deep hibernate energy savings
  • - PRG size feature
  • - Adding frequency-table support with EPE-Statistics
  • - VSWR performance management reporting
  • - MU-MIMO user group optimization feature
  • - Delay profile per beamforming method
| -| 2024.04.15 | 15.00.01 | Merge of CR: CIS-0085 | -| 2024.06.17 | 15.00.02 | Merge of CRs: CIS-0086, NOK-0169, CIS-0093, CIS-0092 | -| 2024.06.27 | 15.00.03 | Merge of CRs: SAM-0120, ERI-0106, MAV-0038 | -| 2024.07.01 | 15.00.04 | Merge of CRs: DCM-0023, ERI-0112, NOK-0180, ERI-0111, MAV-0037, QCM-0080, QCM-0082, ERI-0120 | - -| Date | Revision | Description | -|------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2024.07.03 | 15.00.05 | Merge of CRs: CIS-0087, CIS-0089, CIS-0091, SAM-0116 | -| 2024.07.09 | 15.00.06 | Merge of CRs: DELL-0002, SAM-0115, SAM-0119, CIS-0094, NOK-0185, SAM-0118, CIS-0090, SYM-0006 | -| 2024.08.29 | 16.01 | Summary:
Bug fixes and correction to v15.00:
  • - ETSI cleanup editorials
  • - Clarify interface connection
  • - Clarification on update of network layers parameters via NETCONF
  • - Trust store revision
  • - Clarifying transport endpoints
  • - Clarify alarm 28
  • - Clarify alarm 18
  • - Clarify vendor certificate and trust anchor handling
  • - Clarify certificate and trust anchor management for shared O-RU
  • - Clarify fault management Clause A
  • - CMPv2 clarification
  • - Clarify RFC 5277 and RFC 8639 subscriptions
Addition of new functionality, including:
  • - PAE credential definition
  • - High IQ Alarm
  • - VSWR Alarm
  • - DRMS-BF
  • - SE-10 feature SE10-MEMBER-CANDIDATE-LIST
  • - Target value configuration and used-value retrieval
  • - Configuring IEEE 802.1X addressing
  • - RSSI measurements when operating in shared spectrum.
  • - Simple Public Key Method for SSH Client Authentication
  • - TSSI Measurements
  • - RSSI Measurements
  • - Section Extension 27 for O-DU controlled dimensionality reduction
  • - In service beamforming configuration update
  • - MACsec
  • - Certificate lifecycle management
| -| 2024.11.06 | 16.01.01 | Merge of CRs: CIS-0095, ERI-0119, CIS-0098, CIS-0099, ERI-0128, DCM-0024, MAV-0043, ATT-0001, CIS-0103, SAM-0125, MAV-0035, NOK-0186, NOK-0196 | -| 2024.11.19 | 16.01.02 | Merge of CRs: MAV-0040, MAV-0042, ERI-0117, CIS-0096, ERI-0130 | -| 2024.11.20 | 16.01.03 | Merge of CRs: CIS-0097, SAM-0129, SOL-0038 | -| 2024.11.21 | 16.01.04 | Merge of CRs: CIS-0101, ERI-0124 | -| 2024.11.25 | 16.01.05 | Merge of CRs: ERI-0129, NOK-0191, NOK-0190 | -| 2024.12.23 | 17.00 | Summary:
Bug fixes and correction to v16.01:
  • - British English corrections
  • - Carrier general configuration
  • - Backwards compatible clarification
  • - Revision handling
  • - Remove S-plane performance requirements
  • - Correction of the sync state change descriptions
  • - Correction to feature flag name for dying gasp alarm
  • - Correction to step numbers in Cross Reference
  • - Clarification of temperature measurements for transceivers
  • - Remove case SELECTIVE from shared cell mode configuration
  • - hardware-state-change clarification
  • - Deprecate per-band-config list related RPC and Notification
  • - Clarify ALD operations
| - -| Date | Revision | Description | -|------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | |
  • - Hybrid and hierarchical clarifications
  • - Shared cell clarifications
  • - Clarify U-Plane configuration steps
  • - Clarify carrier availability status

Addition of new functionality, including:

  • - Add a generic hardware failure alarm to M-Plane
  • - Add TX output power statistics to M-Plane
  • - O-RAN defined security logging
  • - Dynamic SINR reporting resolution
  • - Switched to importing RFC 9640, 9641, 9642 instead of Internet-Drafts
  • - New transceiver measurement for thermoelectric cooler (TEC) current
  • - New Ethernet statistics counters
| - -| Date | Revision | Description | -|------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2024.01.27 | 17.01 | Summary:
Bug fixes and correction to v17.00:
  • - Aligned all 3GPP References
| -| 2025.03.03 | 17.01.01 | Merge of CRs: ERI-0114, ERI-0144, NEC-0048, QCM-0090, QCM-0088, RMI-0002, QCM-0089, NEC-0049 | -| 2025.03.11 | 17.01.02 | Merge of CRs: ERI-0155, NOK-0206, NOK-0205, SAM-0136, FJT-0033, CIS-0100, NOK-0209 | -| 2025.03.17 | 17.01.03 | Merge of CRs: CIS-0104 | -| 2025.04.14 | 18.00 | Summary:
Bug fixes and correction to v17.01:
  • - Correcting sync parameter naming
  • - Correcting carrier management figure
  • - Correcting mismatch in file management RPC YANG parameters
  • - Clarify sending of notifications when 'oper-state' changed
  • - Clarify measurement results in first measurement interval
  • - Clarify TRX control activation
  • - Clarify supervision monitoring
  • - Correct mismatch in o-ran-performance-management features
  • - Clarify alarm type enumerations
  • - Correct delay parameter table
  • - Correct description of TX_TOTAL_C
  • - Clarification of static routing
Addition of new functionality, including:
  • - Notification of the transceiver presence change
  • - Transceiver operating limits thresholds and notifications
  • - Filtering of troubleshooting log files
| -| 2025.06.18 | 18.00.01 | Merge of CRs: NOK-0212, NOK-0225, NOK-0200, DEL-003, SAM-0143 | -| 2025.06.25 | 18.00.02 | Merge of CRs: SAM-0132, NOK-0227, CIS-0108 | -| 2025.07.02 | 18.00.03 | Merge of CRs: CIS-0107, ERI-0179, ERI-0192, SAM-0132, SAM-0148, SAM-0150 | -| 2025.07.07 | 18.00.04 | Merge of CRs: NOK-0229 | -| 2025.07.16 | 18.00.07 | Merge of CRs: ERI-0191 | -| 2025.08.11 | 19.00 | Summary:
Bug fixes and correction to v18.00:
  • - Fix of the RX_CORRUPT definition
  • - Software management install bugfix
  • - YANG parameter name corrections
  • - Table C.3-9 corrections
  • - Clarification of certificate subject in CSR
  • - Clarifying statements of fact
  • - Clarify configuration and activation of PM measurement
  • - Adding missed feature SHARED-CELL-STATS to Table C.2-1
Addition of new functionality, including:
  • - Fan present and operating change notification
  • - Configurable TLS Server Hello message
  • - Max output power control for energy saving
  • - SE-20 full PRB puncture with different sectionId
  • - Adding object unit data-direction to tx-stats
  • - Additional Ethernet counters
  • - Cyclic delay adjustment
| -| 2025.11.04 | 19.00.01 | Merge of CRs: CIS-0100, ERI-0193, NOK-0223, ERI-0158, CIS-0111, NOK-0230, ERI-0208, NOK-0241, NOK-0242, NOK-0240, ERI-0205, CIS-0109, ERI-0215, | - -| Date | Revision | Description | -|------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | SAM-0158, ERI-0200, ERI-0201, ERI-0211, NOK-0238, NOK-0239, NOK-0234, SAM-0153, ERI-0202, NOK-0237 | -| 2025.11.06 | 19.00.02 | Merge of CRs: ATT-0002, ATT-0004, DELL-0004, SAM-0157, ERI-0199, DCM-0025 | -| 2025.11.11 | 19.00.03 | Merge of CRs: ERI-0214, NOK-0245, ERI-0197, ERI-0213, CIS-0112, ERI-0196
Addressing comment spreadsheets from ATT, CIS, NOK, QCM and NEC
Updated YANG model revision statements from merged PRs
Updated YANG trees from merged PRs | -| 2025.11.20 | 19.00.04 | Addressing comment spreadsheets from ERI, SAM and CIS | -| 2025.12.22 | 20.00 | Summary:
Bug fixes and correction to v19.00:
  • - Correct missing MEAS-UE-RADIAL-SPEED and MEAS-UE-POS features
  • - Clarify maximum simultaneous eAxC ID formats
  • - Address ETSI PAS comments
  • - admin-state and availability-state dependency clarification
  • - Correct ALD DC enabling
  • - Performance measurement statistics calculation cleanup
  • - Clarify CMPv2/HTTPS
  • - Align password definitions
  • - Update to history table format
  • - Clarifications to delete carrier operations
  • - Correct cross references to CUS-plane specification
  • - Clarify Trust Anchor Provisioning
  • - Clarify operation with vendor signed certificates
  • - Clarify TLS Certificate handling
  • - Corrections in performance management
  • - Clarification of low-level link creation
  • - Correction of PM format examples
  • - Clarification of handling different M-Plane versions
  • - Clarify certificate enrolment requirements
  • - Clarify NETCONF authorisation
Addition of new functionality, including:
  • - Introduce sub-module handling
  • - Add new feature POINT-A-OFFSET-TO-ABSOLUTE-FREQUENCY-CENTER-TX
  • - Switch TLS1.3 to be mandatory
  • - Configurable SSH algorithms
  • - Import IETF Features for SSH and TLS Servers
  • - Self-tunable transceiver diagnostics
  • - O-RU autonomous re-keying
  • - CRL checking requirements
  • - re-pnf-registration-timer
  • - invalid FOE indication
  • - MU interference level RRM measurement
  • - capability for single value SINR report for DFT-sOFDM
| \ No newline at end of file diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/029a2a023e47a2cc5c60079e523926c5_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/029a2a023e47a2cc5c60079e523926c5_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/029a2a023e47a2cc5c60079e523926c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/041486a30f2434ca0821ab7bed8e6492_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/041486a30f2434ca0821ab7bed8e6492_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/041486a30f2434ca0821ab7bed8e6492_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/04d4594dc10c551faa95bf8551462dcd_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/04d4594dc10c551faa95bf8551462dcd_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/04d4594dc10c551faa95bf8551462dcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/057e0fadbc74743547d314f6fd0ff686_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/057e0fadbc74743547d314f6fd0ff686_img.jpg deleted file mode 100644 index 97cf29a42302c621a6c8e65824449f1666978055..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/057e0fadbc74743547d314f6fd0ff686_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6ce69247c4c6cc0e33dcc75ba92534ea1b29399fc1b777b1ae1660dcade2ffb -size 62220 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/07bae2d456e460215a6b74db040d9b6c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/07bae2d456e460215a6b74db040d9b6c_img.jpg deleted file mode 100644 index 0c19ef0e90e589bb41a601e000e132335bcb51fd..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/07bae2d456e460215a6b74db040d9b6c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33f10d53d3566b5efe501303035c228c4977dbc0e20f49304b887f2270d499a0 -size 4501 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/09032127b49c74c07fdc4e0d5275a115_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/09032127b49c74c07fdc4e0d5275a115_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/09032127b49c74c07fdc4e0d5275a115_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/09e41da697fcaa1b598908c21f7452ca_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/09e41da697fcaa1b598908c21f7452ca_img.jpg deleted file mode 100644 index 5ea9ae9194f7b34b2cc65cfadbc793ea1665fdee..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/09e41da697fcaa1b598908c21f7452ca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2a4b269f41327c108671a0dc91ce78a790dbc91b34a39bd88709c7e4474a7073 -size 4436 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/09fcf056902487318885284a6b43b08c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/09fcf056902487318885284a6b43b08c_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/09fcf056902487318885284a6b43b08c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0a278c1194f7b78236442a1c85cf70b5_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0a278c1194f7b78236442a1c85cf70b5_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0a278c1194f7b78236442a1c85cf70b5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0b2ee589f5c7802f3d332f421340cae1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0b2ee589f5c7802f3d332f421340cae1_img.jpg deleted file mode 100644 index fc894343a114cb3b8fcd5d139b28897965a3a634..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0b2ee589f5c7802f3d332f421340cae1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4091f6e52449aed9957535621ae9ddae00e79c88ee89b2672f779d647ab01283 -size 78538 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0c47111d859618d4b5ab9b334ec3641a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0c47111d859618d4b5ab9b334ec3641a_img.jpg deleted file mode 100644 index c02cde79dc2fa4020df107798ba2d129a87679f3..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0c47111d859618d4b5ab9b334ec3641a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ca96e6a0cf2a09b88fa07b7b0a72840f95d6383d918e9552ab5b08b0f6b649e6 -size 115419 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0c586365841f26a3d201eeefdfe261b8_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0c586365841f26a3d201eeefdfe261b8_img.jpg deleted file mode 100644 index 141fbdc62d6a7c4f6feda1bfe8c44d950c04af96..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0c586365841f26a3d201eeefdfe261b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:db39ee763a9352985e7ffff991041a5361b07b2854780b51e34840f4adc5b3e0 -size 4549 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0c6aeaf9973cd03cff19dd3f0ca1314e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0c6aeaf9973cd03cff19dd3f0ca1314e_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0c6aeaf9973cd03cff19dd3f0ca1314e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0d2f92b554f88f7f5b03f23faec94dba_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0d2f92b554f88f7f5b03f23faec94dba_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0d2f92b554f88f7f5b03f23faec94dba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0e2a8954ad6cb6a913374fe51484fce5_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0e2a8954ad6cb6a913374fe51484fce5_img.jpg deleted file mode 100644 index 3958b370033dc226f3c9a0d438dab3d2f904116f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0e2a8954ad6cb6a913374fe51484fce5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:48340866d655b0d262ab777be51a55e312f28653170e4471e336927d006eb452 -size 4538 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg deleted file mode 100644 index 69c38152e6b37636269ff84c6b134abd4d23df11..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5e2d6130933e4456bf3525ddcc61a4ca253305637f4c5c8d7f35a5033c4fdae2 -size 4529 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0e50822d868aa19c8aa37bfb98002a25_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0e50822d868aa19c8aa37bfb98002a25_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/0e50822d868aa19c8aa37bfb98002a25_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/116a62c978d6a7d1b7830c1ea13e2993_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/116a62c978d6a7d1b7830c1ea13e2993_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/116a62c978d6a7d1b7830c1ea13e2993_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1187dbd674a100960ed23efa54ccd6c1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1187dbd674a100960ed23efa54ccd6c1_img.jpg deleted file mode 100644 index c04f0a20fd8ed8370951e1a209bf8f9871fe8b87..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1187dbd674a100960ed23efa54ccd6c1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8a0403355f1dacab8092fb8c08e46d24a36ccfddbdeef43778df9369d2cb240e -size 21082 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/118d1daec0d1a3e2a27924fe38e6d3cc_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/118d1daec0d1a3e2a27924fe38e6d3cc_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/118d1daec0d1a3e2a27924fe38e6d3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/11b3d3cc56f71f80a268a31bd42103e9_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/11b3d3cc56f71f80a268a31bd42103e9_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/11b3d3cc56f71f80a268a31bd42103e9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/11cfbe1171c471cd8b2d0604ad5185f2_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/11cfbe1171c471cd8b2d0604ad5185f2_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/11cfbe1171c471cd8b2d0604ad5185f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/134b1f0d617209a0436333b9ab6b1ce8_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/134b1f0d617209a0436333b9ab6b1ce8_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/134b1f0d617209a0436333b9ab6b1ce8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/13fbd97d3a93abb4c723c50966c8cd14_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/13fbd97d3a93abb4c723c50966c8cd14_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/13fbd97d3a93abb4c723c50966c8cd14_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/140bd031d724324269168296afd1e04d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/140bd031d724324269168296afd1e04d_img.jpg deleted file mode 100644 index 2e1f0e462a5f979c69b73d09a868fe1c46cc4d34..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/140bd031d724324269168296afd1e04d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:315ba261933723d1858751d8272d5000ffa683f41a009c1c4c7bc0031ebccf74 -size 136450 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg deleted file mode 100644 index 79107074226b15365fa8835c4321d9eb0167ee77..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/14252bcd35912bd656e98b16b2ee51c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0e78be6dedbad5674d7673bb5b02c8bb44eb83c36f642a137635d2a47d8fcc7d -size 80617 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/147bfd471cf5feef55178475cec58064_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/147bfd471cf5feef55178475cec58064_img.jpg deleted file mode 100644 index 783c581434f3c49b1ec7b7eb3890988c49cc49c7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/147bfd471cf5feef55178475cec58064_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3a6bbe65fb6d9d0d48d39430909f2756496ec59fffaf23ae8d8beac822270e91 -size 114735 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/15574508acc09ee822bfbd5ad0954c5a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/15574508acc09ee822bfbd5ad0954c5a_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/15574508acc09ee822bfbd5ad0954c5a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1684f5f8c34bd0ef6e933664d88b9d86_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1684f5f8c34bd0ef6e933664d88b9d86_img.jpg deleted file mode 100644 index bde9a25227acc70b62b74221bb464b54f646d36d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1684f5f8c34bd0ef6e933664d88b9d86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bc7a1f500a58ca5c6160070c8772b5b4a6852f2dc95c96519a5069b90af722c4 -size 68107 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/16b08981199f29066db206d1e31e6e47_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/16b08981199f29066db206d1e31e6e47_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/16b08981199f29066db206d1e31e6e47_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/16c8aea7b68120358abcb5ef6ef3ae0b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/16c8aea7b68120358abcb5ef6ef3ae0b_img.jpg deleted file mode 100644 index 5426f9e8ad8d0f7afeba8205bd64337951f92d08..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/16c8aea7b68120358abcb5ef6ef3ae0b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:acfc618ea369791b0da56ecf5469c884cd2d82f36ae8c7512db1ced78386123b -size 158302 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1719fcc6ce45d9a31c81c3bc46a72d03_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1719fcc6ce45d9a31c81c3bc46a72d03_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1719fcc6ce45d9a31c81c3bc46a72d03_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/17b315c49985d42848e8d673a66dce7f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/17b315c49985d42848e8d673a66dce7f_img.jpg deleted file mode 100644 index 7136bddf3cce4137296fba0069cf9ef8a5145400..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/17b315c49985d42848e8d673a66dce7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:158e88a27a596f6adc2debded5137e284c9e6c9d7b81b2211b3b57b1ff064da3 -size 73482 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1869d74dac030a42b1b3860ebfb7d0c4_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1869d74dac030a42b1b3860ebfb7d0c4_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1869d74dac030a42b1b3860ebfb7d0c4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/189ac86054d2d468016d2091f22dfc5d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/189ac86054d2d468016d2091f22dfc5d_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/189ac86054d2d468016d2091f22dfc5d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/19499072f755b22d0a231123f75fa477_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/19499072f755b22d0a231123f75fa477_img.jpg deleted file mode 100644 index c870c35372a20add21e1150de162b370a627c63c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/19499072f755b22d0a231123f75fa477_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:17489c14533b3512990f979fede32a31972dba97ea7229fa70f4a9145826ab03 -size 14505 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/19882a9fbfbe25c951b10a507c786951_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/19882a9fbfbe25c951b10a507c786951_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/19882a9fbfbe25c951b10a507c786951_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/19f90331494ba1e143d915d8d0061942_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/19f90331494ba1e143d915d8d0061942_img.jpg deleted file mode 100644 index 34c8ba17cd20c9c48e849a40f08939076a4ffdd6..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/19f90331494ba1e143d915d8d0061942_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ce156cfbe0a9d14776b415461fec279ee1ef17de2ed0dc33e8bb9297b3f9a351 -size 11124 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1a264eeb01c7e3f33a65cb202a5dee36_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1a264eeb01c7e3f33a65cb202a5dee36_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1a264eeb01c7e3f33a65cb202a5dee36_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1b7861077e6bb3e95f508e0ceeda5b0e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1b7861077e6bb3e95f508e0ceeda5b0e_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1b7861077e6bb3e95f508e0ceeda5b0e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1d7348fac9ef4446e3f7e5f0e15c007b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1d7348fac9ef4446e3f7e5f0e15c007b_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1d7348fac9ef4446e3f7e5f0e15c007b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1ff7828d681947990fac3e7bad35dd86_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1ff7828d681947990fac3e7bad35dd86_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/1ff7828d681947990fac3e7bad35dd86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/21023d70b19c3181ccce4390ea153e38_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/21023d70b19c3181ccce4390ea153e38_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/21023d70b19c3181ccce4390ea153e38_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/21b431575d18ed23db9ef488c8dec706_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/21b431575d18ed23db9ef488c8dec706_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/21b431575d18ed23db9ef488c8dec706_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/21cfcb7e235dba52c53c8cf7b10f36aa_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/21cfcb7e235dba52c53c8cf7b10f36aa_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/21cfcb7e235dba52c53c8cf7b10f36aa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/226bcc7921bff55dc14cac630460ab92_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/226bcc7921bff55dc14cac630460ab92_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/226bcc7921bff55dc14cac630460ab92_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/233a8b9743fe86cccae4bfca4aa9a0b0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/233a8b9743fe86cccae4bfca4aa9a0b0_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/233a8b9743fe86cccae4bfca4aa9a0b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/23b110b75da6b415520918830060195e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/23b110b75da6b415520918830060195e_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/23b110b75da6b415520918830060195e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2411409f3e88d90b892db534d525cfa7_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2411409f3e88d90b892db534d525cfa7_img.jpg deleted file mode 100644 index 3d5680628c7b7bfec6dd276c6272929c1a9f3e74..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2411409f3e88d90b892db534d525cfa7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f3edf1302fd1c226fb85c66b929d4968609735fc6d67c8ac273dbed8156686fc -size 59530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/24a3cc3bc7bd963ec2c4ceaf3e548457_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/24a3cc3bc7bd963ec2c4ceaf3e548457_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/24a3cc3bc7bd963ec2c4ceaf3e548457_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/24ca460ee3381aee781887e9e586ec67_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/24ca460ee3381aee781887e9e586ec67_img.jpg deleted file mode 100644 index 72cc318f87c0303dfcc6f480aa3fe4e357ae7b23..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/24ca460ee3381aee781887e9e586ec67_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:26a355ff575c40fdc2e3600092c2dd138f6a5370763fc7ac0836ce0ed73988a8 -size 187483 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/266ed4b8590c3bfce2d6ccf95b143242_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/266ed4b8590c3bfce2d6ccf95b143242_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/266ed4b8590c3bfce2d6ccf95b143242_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/26f0c643a3e0c8034b16008c351b5b65_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/26f0c643a3e0c8034b16008c351b5b65_img.jpg deleted file mode 100644 index 3958b370033dc226f3c9a0d438dab3d2f904116f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/26f0c643a3e0c8034b16008c351b5b65_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:48340866d655b0d262ab777be51a55e312f28653170e4471e336927d006eb452 -size 4538 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/29640f9496773db15b016e35bb17d5b8_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/29640f9496773db15b016e35bb17d5b8_img.jpg deleted file mode 100644 index 4d8dd78df3e15758c3346d0dd866a88225aeedb0..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/29640f9496773db15b016e35bb17d5b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ae9610211f981254d16af21b56fe885f932146432de16ee29eb136a971062381 -size 122510 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2981200c3b8faff326c7ace0c91f0687_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2981200c3b8faff326c7ace0c91f0687_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2981200c3b8faff326c7ace0c91f0687_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/29997432244f81212ee1e6c94f308f1b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/29997432244f81212ee1e6c94f308f1b_img.jpg deleted file mode 100644 index 8f276b3601ff7a79ef2d48140e6f566258ed9e45..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/29997432244f81212ee1e6c94f308f1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eadaff582848447af0442d405049dbb417ba69b1715ed750a4d01a1772785e31 -size 82871 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2a185522b492253375ed16f0c515c230_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2a185522b492253375ed16f0c515c230_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2a185522b492253375ed16f0c515c230_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2aa10298301ca8b4025898fa7fdbc3df_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2aa10298301ca8b4025898fa7fdbc3df_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2aa10298301ca8b4025898fa7fdbc3df_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2b9774757a61bd7a8abe6f79635a7d45_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2b9774757a61bd7a8abe6f79635a7d45_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2b9774757a61bd7a8abe6f79635a7d45_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2c4b84a66cab050595b6ee02d8799bb0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2c4b84a66cab050595b6ee02d8799bb0_img.jpg deleted file mode 100644 index 3958b370033dc226f3c9a0d438dab3d2f904116f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2c4b84a66cab050595b6ee02d8799bb0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:48340866d655b0d262ab777be51a55e312f28653170e4471e336927d006eb452 -size 4538 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2cf96b55beaa98ebc755c7405b1adbeb_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2cf96b55beaa98ebc755c7405b1adbeb_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2cf96b55beaa98ebc755c7405b1adbeb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2d1bc5eed8281b9364808514bacdb32a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2d1bc5eed8281b9364808514bacdb32a_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2d1bc5eed8281b9364808514bacdb32a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2de65c6883946871f46308ff85ad7faf_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2de65c6883946871f46308ff85ad7faf_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2de65c6883946871f46308ff85ad7faf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2e1d7b4c07a00dd0f26b51558abbe428_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2e1d7b4c07a00dd0f26b51558abbe428_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2e1d7b4c07a00dd0f26b51558abbe428_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2f6073b866a873087bacb1adb0b0852c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2f6073b866a873087bacb1adb0b0852c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2f6073b866a873087bacb1adb0b0852c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2f983ce3451ef9194e19e72e0ad04c83_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2f983ce3451ef9194e19e72e0ad04c83_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2f983ce3451ef9194e19e72e0ad04c83_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2fcfff451a38d27b4253203bae9c5a48_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2fcfff451a38d27b4253203bae9c5a48_img.jpg deleted file mode 100644 index 69c38152e6b37636269ff84c6b134abd4d23df11..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2fcfff451a38d27b4253203bae9c5a48_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5e2d6130933e4456bf3525ddcc61a4ca253305637f4c5c8d7f35a5033c4fdae2 -size 4529 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2fdf2dbffaf6ea606624441e4574c011_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2fdf2dbffaf6ea606624441e4574c011_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2fdf2dbffaf6ea606624441e4574c011_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2ff9776a780f30bc64c7a9ef23131cbf_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2ff9776a780f30bc64c7a9ef23131cbf_img.jpg deleted file mode 100644 index fb9d548df27feb4e64d5f4c998e8ceb94d6a1a1f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2ff9776a780f30bc64c7a9ef23131cbf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e13040b8f84961355b325bbcac9c54a30f14f36b469c7678a8f58da0fbe0c3c7 -size 36218 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2ffb32ca2d8acda8228f0301aa7f52e0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2ffb32ca2d8acda8228f0301aa7f52e0_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/2ffb32ca2d8acda8228f0301aa7f52e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3107f66da1c3556cee065608ee86f7e4_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3107f66da1c3556cee065608ee86f7e4_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3107f66da1c3556cee065608ee86f7e4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/313826501fcb4294a5d337702ea35f2d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/313826501fcb4294a5d337702ea35f2d_img.jpg deleted file mode 100644 index f223e0d34b27d9dfdce101748d91ebfb6a6a4c65..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/313826501fcb4294a5d337702ea35f2d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ab2394509898c23482f8218edb879250fff4171809ace4598b438c27c464d767 -size 79508 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/318db222fae24a59c370fa6471d541b8_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/318db222fae24a59c370fa6471d541b8_img.jpg deleted file mode 100644 index e9ec69d7f23516aafc596a5b6daff2451ab472be..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/318db222fae24a59c370fa6471d541b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:11b123539ca24ee88134d082227dd0cc5de7f0949e03a4fadf45d178534b2379 -size 4464 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/31a464e0e5a8a9c5d10fd33d2ed26347_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/31a464e0e5a8a9c5d10fd33d2ed26347_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/31a464e0e5a8a9c5d10fd33d2ed26347_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/320bb6a0e7b3cc0803a15b231b3bc311_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/320bb6a0e7b3cc0803a15b231b3bc311_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/320bb6a0e7b3cc0803a15b231b3bc311_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3220d3a933797114c1ba20d5c4ec093d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3220d3a933797114c1ba20d5c4ec093d_img.jpg deleted file mode 100644 index 2b8852f3b0337d5fdf15791ebd401e3a858c76ea..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3220d3a933797114c1ba20d5c4ec093d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:35656fa792821918495abeb1866cec273ad4b25756bb21762afa29d72770983b -size 131347 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3334fcca5dac808f4fd3840aba35bc2e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3334fcca5dac808f4fd3840aba35bc2e_img.jpg deleted file mode 100644 index db62b939d54d1b415d87eedb638d967b0e8bc3ca..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3334fcca5dac808f4fd3840aba35bc2e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:79e274ecf707ec77a4d7b6477325d9fd2c51ce81a083a51d6eaba1706ae3a2c1 -size 48292 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/33b37422d7968d2d8e7d3c48fe341a77_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/33b37422d7968d2d8e7d3c48fe341a77_img.jpg deleted file mode 100644 index 2ef4f5f3ced15ee448cc709196c22f1d208ad7d2..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/33b37422d7968d2d8e7d3c48fe341a77_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8e707dc181647b654fab29125ded85db6fd1eda222dedbf5bf55f47aac22570 -size 75976 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/35037145df6cd8b5520bbfebf46c9433_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/35037145df6cd8b5520bbfebf46c9433_img.jpg deleted file mode 100644 index 9dd91170838b73c05fd43cd85377afa1c0db744e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/35037145df6cd8b5520bbfebf46c9433_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1bde40b47c85da389f8c8023e1e8c820623f52023afaeecedfb19c296cf2adb2 -size 4574 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/359093c76d121867106328fa8adfe8ff_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/359093c76d121867106328fa8adfe8ff_img.jpg deleted file mode 100644 index 8067cdd92222b9ac47691aea2d9dca2bdfab8987..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/359093c76d121867106328fa8adfe8ff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:00243a672b340f4c34ba13699c8524a72881a215cd0da1effc150987d9804dfa -size 4648 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/366398d17120ce12a2c36b95c54033c5_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/366398d17120ce12a2c36b95c54033c5_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/366398d17120ce12a2c36b95c54033c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/378417d45871e98cf0371e2dfe49ef55_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/378417d45871e98cf0371e2dfe49ef55_img.jpg deleted file mode 100644 index bf238570411b2c3c4801758e0b4fee8375ccb9f4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/378417d45871e98cf0371e2dfe49ef55_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef39b9b0dadf1b084c8b8bc63a0ff7d1585b6d745ca12ad8368f11082cad5a0 -size 4493 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/37d5d6957e175201847002c556b5a29d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/37d5d6957e175201847002c556b5a29d_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/37d5d6957e175201847002c556b5a29d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/37d8d885fed5ec107803a8eeceb71686_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/37d8d885fed5ec107803a8eeceb71686_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/37d8d885fed5ec107803a8eeceb71686_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/384d97a0c67bd4f219a452c3cd658684_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/384d97a0c67bd4f219a452c3cd658684_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/384d97a0c67bd4f219a452c3cd658684_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3893e26cb0b95e076fdc8953d2db0072_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3893e26cb0b95e076fdc8953d2db0072_img.jpg deleted file mode 100644 index fef284255abf5e1f5943499dae44dea76e570dcd..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3893e26cb0b95e076fdc8953d2db0072_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5a4d02e8616fa1e70b3df9a187d753bb1676a1e0b15125702c4e6b8157e031ce -size 102250 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/38c0f202ad5767f3df428353919fa90a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/38c0f202ad5767f3df428353919fa90a_img.jpg deleted file mode 100644 index 35fc441c9c6eb0d3bc64623ebfe27b7ab9450a36..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/38c0f202ad5767f3df428353919fa90a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a7a98e80b5bf6271b455800de79c97c0e3a2abeef0ebe160b6b5c6a8b4b40c54 -size 183688 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/38d82ffe820e339811b396206f40a201_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/38d82ffe820e339811b396206f40a201_img.jpg deleted file mode 100644 index 0a1253d07d0c8e5fa78e3c643e900feefa0db2d5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/38d82ffe820e339811b396206f40a201_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4dba9429dfcaf86ab143891cecc1a9be4e0b33cd9dc48ebd2feae529ce62a0d0 -size 44012 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/39e964ecd6d6a7fd1d783271aa934f23_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/39e964ecd6d6a7fd1d783271aa934f23_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/39e964ecd6d6a7fd1d783271aa934f23_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3a3831d50dc74b7ebbec3e1d96eea588_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3a3831d50dc74b7ebbec3e1d96eea588_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3a3831d50dc74b7ebbec3e1d96eea588_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3b6c4e5a462a828bef2d462df300da37_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3b6c4e5a462a828bef2d462df300da37_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3b6c4e5a462a828bef2d462df300da37_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3b6f513e9cb02e7a2b653f69f9f81873_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3b6f513e9cb02e7a2b653f69f9f81873_img.jpg deleted file mode 100644 index 69c38152e6b37636269ff84c6b134abd4d23df11..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3b6f513e9cb02e7a2b653f69f9f81873_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5e2d6130933e4456bf3525ddcc61a4ca253305637f4c5c8d7f35a5033c4fdae2 -size 4529 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3b89d812329a65ab156184a40524adf0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3b89d812329a65ab156184a40524adf0_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3b89d812329a65ab156184a40524adf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3bc1596c96f362d588541b78554df33d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3bc1596c96f362d588541b78554df33d_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3bc1596c96f362d588541b78554df33d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3cf773bd0581c54adb3aea51556f70b9_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3cf773bd0581c54adb3aea51556f70b9_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3cf773bd0581c54adb3aea51556f70b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3eb2c6bfde13eae0df07b28c24d52e5d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3eb2c6bfde13eae0df07b28c24d52e5d_img.jpg deleted file mode 100644 index 1f03c50c35c653c96546da2bd481b032f99a2ff7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3eb2c6bfde13eae0df07b28c24d52e5d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4ee46ca7cd935d112bb4722bfb7c0695edf0f6567401624fdcaa196dea7afd3c -size 54208 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/40cadfef9d925077fe9ecddbc1d44cc8_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/40cadfef9d925077fe9ecddbc1d44cc8_img.jpg deleted file mode 100644 index 9dd91170838b73c05fd43cd85377afa1c0db744e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/40cadfef9d925077fe9ecddbc1d44cc8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1bde40b47c85da389f8c8023e1e8c820623f52023afaeecedfb19c296cf2adb2 -size 4574 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/40e106822047971ea364d73846848ecd_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/40e106822047971ea364d73846848ecd_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/40e106822047971ea364d73846848ecd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/41bc9383c0d6e910a69e23d465ae5607_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/41bc9383c0d6e910a69e23d465ae5607_img.jpg deleted file mode 100644 index 80de2b173e57c62fed530e49b02dfc9dc6ac0d91..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/41bc9383c0d6e910a69e23d465ae5607_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b07f70a2dd5627e5272354ed2a06ae7b84d7022689d1e35ba20950fdc3f9d4b0 -size 113621 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/41d2a2a58f53d1013a114da9c02f726e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/41d2a2a58f53d1013a114da9c02f726e_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/41d2a2a58f53d1013a114da9c02f726e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/41fa90d03d7195caa162c74d289817a4_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/41fa90d03d7195caa162c74d289817a4_img.jpg deleted file mode 100644 index 5f83753a0fe4b435cdd765754c2deb190401bbcf..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/41fa90d03d7195caa162c74d289817a4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ab18c472753906fd426ec2665ceaf75cfd661b2992b1e564c54039add5000e81 -size 93873 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/426342bd710b59091374594dd7d65234_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/426342bd710b59091374594dd7d65234_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/426342bd710b59091374594dd7d65234_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4312b91d86300ea45d4ed0884648d447_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4312b91d86300ea45d4ed0884648d447_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4312b91d86300ea45d4ed0884648d447_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/436f157984813b721741946e24a3b76f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/436f157984813b721741946e24a3b76f_img.jpg deleted file mode 100644 index 9a8fcaa78caf86ee35526aaea9cf7c838b759019..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/436f157984813b721741946e24a3b76f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:771317d43a07cf814bbe82692308c48805941a433681b93fea23dc730ca54e89 -size 39642 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/457ebeb4cc14a22ced51a688af25f7a8_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/457ebeb4cc14a22ced51a688af25f7a8_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/457ebeb4cc14a22ced51a688af25f7a8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/45a161027983c0b508f6269c35551968_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/45a161027983c0b508f6269c35551968_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/45a161027983c0b508f6269c35551968_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4665bbd9c3079135f242a62a0e931eec_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4665bbd9c3079135f242a62a0e931eec_img.jpg deleted file mode 100644 index 0c19ef0e90e589bb41a601e000e132335bcb51fd..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4665bbd9c3079135f242a62a0e931eec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33f10d53d3566b5efe501303035c228c4977dbc0e20f49304b887f2270d499a0 -size 4501 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4706a500dbc72fdedc9bee99d7c78df5_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4706a500dbc72fdedc9bee99d7c78df5_img.jpg deleted file mode 100644 index e5c0d9ffe520486d0821eb1de188522ba9ec7be6..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4706a500dbc72fdedc9bee99d7c78df5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c4aaa9f16be269d06c7d5640ef627016ce63b38fb796901e3708a98119ba7af -size 135977 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/47702b55f927e2e85ac03e79a7ebe350_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/47702b55f927e2e85ac03e79a7ebe350_img.jpg deleted file mode 100644 index a59ae19fa56cf2107602c61e965177d3ab7b8e29..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/47702b55f927e2e85ac03e79a7ebe350_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:16bdea8a5b26c9a54da723b5196140c5fc367787b5d04c460dddd03ef272390e -size 195941 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/47a7beddcb8a1b7abdca746967e32bb4_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/47a7beddcb8a1b7abdca746967e32bb4_img.jpg deleted file mode 100644 index af830915b37f007261523eb9b78116eaea80b3c0..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/47a7beddcb8a1b7abdca746967e32bb4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ae019d1b722b88785d1d65165962e20d2b57a79a63c6c5c2cafdc1bf662d7bdd -size 169644 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/47ab805b7e6a0b6eb9e379fd8da934fa_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/47ab805b7e6a0b6eb9e379fd8da934fa_img.jpg deleted file mode 100644 index b9e6999118b1bfdb3a8ed02a28a4d618f81e79e1..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/47ab805b7e6a0b6eb9e379fd8da934fa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:05b130d3ab9636f36b45e6663f4552e60ed60f9ac36e008a04a98b20ce789f9e -size 129200 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/47c8f3782d7566332f5685e1b7958b33_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/47c8f3782d7566332f5685e1b7958b33_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/47c8f3782d7566332f5685e1b7958b33_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/496e5dfc146af6bcc2b3bc2eaf82826c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/496e5dfc146af6bcc2b3bc2eaf82826c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/496e5dfc146af6bcc2b3bc2eaf82826c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4a0481e8f65937a5833e4894b29fe657_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4a0481e8f65937a5833e4894b29fe657_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4a0481e8f65937a5833e4894b29fe657_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4b06562dec0d51c18da84c42537b4db2_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4b06562dec0d51c18da84c42537b4db2_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4b06562dec0d51c18da84c42537b4db2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4c1d8ed1a2c9ff9594c1ca4f179a9c33_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4c1d8ed1a2c9ff9594c1ca4f179a9c33_img.jpg deleted file mode 100644 index 52a99527c22bc7395852d5b649d60789f1067211..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4c1d8ed1a2c9ff9594c1ca4f179a9c33_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d0e196691d4e732ed44ec224c61ede50bf0f981195a52ed3ec457509ed304494 -size 89862 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4ced45096fe3cf5adc96ec6b94f07e4f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4ced45096fe3cf5adc96ec6b94f07e4f_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4ced45096fe3cf5adc96ec6b94f07e4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4e58d71a7f0cda1ca24fac1ee80a0c7c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4e58d71a7f0cda1ca24fac1ee80a0c7c_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4e58d71a7f0cda1ca24fac1ee80a0c7c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4ecfb2f8adee0634d48422a73bd1a491_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4ecfb2f8adee0634d48422a73bd1a491_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4ecfb2f8adee0634d48422a73bd1a491_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4f775d2964d3729df9498e4321d1a3f0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4f775d2964d3729df9498e4321d1a3f0_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4f775d2964d3729df9498e4321d1a3f0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5374b3619ca88da164423df0b6a532fc_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5374b3619ca88da164423df0b6a532fc_img.jpg deleted file mode 100644 index 5ea9ae9194f7b34b2cc65cfadbc793ea1665fdee..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5374b3619ca88da164423df0b6a532fc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2a4b269f41327c108671a0dc91ce78a790dbc91b34a39bd88709c7e4474a7073 -size 4436 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5441c05741f8a35ee5d6673b0b0ebb8b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5441c05741f8a35ee5d6673b0b0ebb8b_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5441c05741f8a35ee5d6673b0b0ebb8b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/54a69b7eddfb3dc9a9312dc3a721bb78_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/54a69b7eddfb3dc9a9312dc3a721bb78_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/54a69b7eddfb3dc9a9312dc3a721bb78_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/54e6016445a458d4c0aef4acc71bb0c8_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/54e6016445a458d4c0aef4acc71bb0c8_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/54e6016445a458d4c0aef4acc71bb0c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/55b5faca46291297ac05b4f648e60bcc_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/55b5faca46291297ac05b4f648e60bcc_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/55b5faca46291297ac05b4f648e60bcc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/55c1b9efdb97c2b7dd16b497c5b56d3c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/55c1b9efdb97c2b7dd16b497c5b56d3c_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/55c1b9efdb97c2b7dd16b497c5b56d3c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/568031aac86c633aab96b734dba3835e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/568031aac86c633aab96b734dba3835e_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/568031aac86c633aab96b734dba3835e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/56c8fcd83f1ab2e62033a1f6e7cfa3a1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/56c8fcd83f1ab2e62033a1f6e7cfa3a1_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/56c8fcd83f1ab2e62033a1f6e7cfa3a1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/572cf014db14c8234f91c07d5a5a28c6_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/572cf014db14c8234f91c07d5a5a28c6_img.jpg deleted file mode 100644 index 1e7a02c427bc0a65028b639f8a0402c94f3d6798..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/572cf014db14c8234f91c07d5a5a28c6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:38e65a167e4339cd95bef738c530c6fd0ca99a1799971fd359f8b77ba820a3cc -size 45847 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/58a8190bc204c7bf623394f3fd0fa968_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/58a8190bc204c7bf623394f3fd0fa968_img.jpg deleted file mode 100644 index b2d939c7bdaf79460b70fb1b47a3136345857974..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/58a8190bc204c7bf623394f3fd0fa968_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a9b23268c433144113a9336fa7b0685ee4cfb58e05546a8e6f0609efe79cc477 -size 4551 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/59e29b37c5e332b0be088cde8c4d217e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/59e29b37c5e332b0be088cde8c4d217e_img.jpg deleted file mode 100644 index 90e21bf8f02901e4bee574cc9e5e4ae88f606898..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/59e29b37c5e332b0be088cde8c4d217e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d51e7c2cd957b04abaf73d9f10b44cc26050528a41137edbc8914915e1cb4351 -size 13162 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5bba23cc120ad806779f82df1c01bebf_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5bba23cc120ad806779f82df1c01bebf_img.jpg deleted file mode 100644 index 263f72769c465bc1ba68f3b327c1e707b745deaa..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5bba23cc120ad806779f82df1c01bebf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8d0b19c44b5b91180312929b84763d07f3a35da9fcc586d1d00a03063c0be3f2 -size 102967 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5d819f259411162c4e3371915818ae22_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5d819f259411162c4e3371915818ae22_img.jpg deleted file mode 100644 index d090e0f958621f32bec21e656e112bd137a30ab2..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5d819f259411162c4e3371915818ae22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e7a720d62fb6466cef72a5ac0b2d97c22aea1ed99aaeceb59cda1767fd808f0b -size 84896 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5e185b54d270cd15d1299478a13f1f97_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5e185b54d270cd15d1299478a13f1f97_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5e185b54d270cd15d1299478a13f1f97_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5e38bd2f95d0f22ab5091fa99f29ff01_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5e38bd2f95d0f22ab5091fa99f29ff01_img.jpg deleted file mode 100644 index 69c38152e6b37636269ff84c6b134abd4d23df11..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5e38bd2f95d0f22ab5091fa99f29ff01_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5e2d6130933e4456bf3525ddcc61a4ca253305637f4c5c8d7f35a5033c4fdae2 -size 4529 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5efe6377e22b9ab76a19a70da29976b9_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5efe6377e22b9ab76a19a70da29976b9_img.jpg deleted file mode 100644 index c2b907fac7904f26a9041142bcda3193e5d405fb..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5efe6377e22b9ab76a19a70da29976b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e1aae34069d27726ae7a27d49b491cc308e657e7f213c5ea4b96094cd26f3ebc -size 44379 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5f775274defe2a58cc4b4498acd55a6c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5f775274defe2a58cc4b4498acd55a6c_img.jpg deleted file mode 100644 index e862f131a41db4ccb076cd05946d4a534a16866c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5f775274defe2a58cc4b4498acd55a6c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d1bf470e8c63cc3b3d7901d8b3d258ea5fa27acca8be2ab00fe448cf66bc5754 -size 4616 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5f91fba42d09220b843c28373538928a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5f91fba42d09220b843c28373538928a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5f91fba42d09220b843c28373538928a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5fa61cb21e87cecbe7049420f633a811_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5fa61cb21e87cecbe7049420f633a811_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/5fa61cb21e87cecbe7049420f633a811_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/600fbaabf10e40148498bda9961511ab_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/600fbaabf10e40148498bda9961511ab_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/600fbaabf10e40148498bda9961511ab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/60ce0fc249173a32463028d12805feca_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/60ce0fc249173a32463028d12805feca_img.jpg deleted file mode 100644 index b415cc08d0352c5ee9a4e5b0715c26e89305f09c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/60ce0fc249173a32463028d12805feca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:70c3e09cc625229f86a88c51637c21995f26a314793ee77a5e517115bf585067 -size 213442 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/624dbf9b985f5bd85e902ec59b87ba4f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/624dbf9b985f5bd85e902ec59b87ba4f_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/624dbf9b985f5bd85e902ec59b87ba4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/62616918653bd50bc70542647d4caaed_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/62616918653bd50bc70542647d4caaed_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/62616918653bd50bc70542647d4caaed_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/62bcbcd2d72c7add43fc43355a3d212a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/62bcbcd2d72c7add43fc43355a3d212a_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/62bcbcd2d72c7add43fc43355a3d212a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/631360156a16ba258241007e2283213d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/631360156a16ba258241007e2283213d_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/631360156a16ba258241007e2283213d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/638d4a1e55dbf75a122c4f778258f3cb_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/638d4a1e55dbf75a122c4f778258f3cb_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/638d4a1e55dbf75a122c4f778258f3cb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/643af12d37ff807bcfea684e7c7abf31_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/643af12d37ff807bcfea684e7c7abf31_img.jpg deleted file mode 100644 index 288062f526f9927f0ea516bd0920b38618f2f335..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/643af12d37ff807bcfea684e7c7abf31_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:98be73bef732deb6a6ee6d7e9e456124c450a1d61a6f083e00110069ecbc1da2 -size 127181 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6470d350326789d5306eabcb76533951_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6470d350326789d5306eabcb76533951_img.jpg deleted file mode 100644 index 3efa9d65aa6ad90ce61929e5785b8d70c2bc58db..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6470d350326789d5306eabcb76533951_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2c096ca56e585de9d647405fd5143500bf2e91ee8e3cdbdb3e79b99dd09fe799 -size 62702 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/64bec4cd45e47e1976245711f702aca2_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/64bec4cd45e47e1976245711f702aca2_img.jpg deleted file mode 100644 index 99e060353336e9cbca3ee0531296e9d41fc050f0..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/64bec4cd45e47e1976245711f702aca2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ddebdcfe4ad4875bda02232431271b8a9d82a0e55ddd5fbbab1c1f49ffa25811 -size 60349 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/654cccb64b578f1e4a7d09b7ee5626b5_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/654cccb64b578f1e4a7d09b7ee5626b5_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/654cccb64b578f1e4a7d09b7ee5626b5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6588b1c7f14069d96744b473ad663248_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/65cd234286445e716c91a9f734e510d9_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/65cd234286445e716c91a9f734e510d9_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/65cd234286445e716c91a9f734e510d9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/65cf9633846ecab19f1a0b92fa8ecd9a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/65cf9633846ecab19f1a0b92fa8ecd9a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/65cf9633846ecab19f1a0b92fa8ecd9a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6634b0f090110c6fe467e43030c7a488_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6634b0f090110c6fe467e43030c7a488_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6634b0f090110c6fe467e43030c7a488_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6665298b5cd4fc5f777d91df7863dc6c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6665298b5cd4fc5f777d91df7863dc6c_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6665298b5cd4fc5f777d91df7863dc6c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/671d724633c3474b8092064d750ce939_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/671d724633c3474b8092064d750ce939_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/671d724633c3474b8092064d750ce939_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/67da7316a30be623c4c053d4d1eff952_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/67da7316a30be623c4c053d4d1eff952_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/67da7316a30be623c4c053d4d1eff952_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/686705f78594bdc18af4f9cb04b455e0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/686705f78594bdc18af4f9cb04b455e0_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/686705f78594bdc18af4f9cb04b455e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6883c4a2aeca4cb08a9a7a95faa2645a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6883c4a2aeca4cb08a9a7a95faa2645a_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6883c4a2aeca4cb08a9a7a95faa2645a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6a2e100d305cbbcf8e9e794d39ad9c75_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6a2e100d305cbbcf8e9e794d39ad9c75_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6a2e100d305cbbcf8e9e794d39ad9c75_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6a6be4894ef955ac942e3d7a7d1cf529_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6a6be4894ef955ac942e3d7a7d1cf529_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6a6be4894ef955ac942e3d7a7d1cf529_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6aff07583f1535949164b1e6f4ffd9ee_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6aff07583f1535949164b1e6f4ffd9ee_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6aff07583f1535949164b1e6f4ffd9ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6b1e3597147ab3d3e747185d6505a8ef_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6b1e3597147ab3d3e747185d6505a8ef_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6b1e3597147ab3d3e747185d6505a8ef_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6ba886ed1f943623b89bce107f127e61_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6ba886ed1f943623b89bce107f127e61_img.jpg deleted file mode 100644 index 345200aea812872836a289f0ce022c82cad16d42..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6ba886ed1f943623b89bce107f127e61_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0378df14ae84557fd523af4bfc04ede82381ff91ac20f48db8275be222efe4a1 -size 95151 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg deleted file mode 100644 index 4db3d5252406ff2ce57fbe565bae426ea8ddba88..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6d697ce8828ba75fddee0a1b7767a7ca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e57d1bc8d6a58d1c604bf5cbba59577f7bf5d0a848907888cd2452824bb66bb7 -size 122692 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6da08196de6831d44259c8a25e416c2d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6da08196de6831d44259c8a25e416c2d_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6da08196de6831d44259c8a25e416c2d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6e0f8561f98e81dc4918793f6a884357_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6e0f8561f98e81dc4918793f6a884357_img.jpg deleted file mode 100644 index 8a55bf0badc444b03d6d8afec4aecf980094d22e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6e0f8561f98e81dc4918793f6a884357_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2b60c36d9bbc1bcd72969b20cf592f01f185fc135b0ed29dd0ba8eea6acbed6a -size 141654 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6e20e7b94f8042f05a660226090a538e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6e20e7b94f8042f05a660226090a538e_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6e20e7b94f8042f05a660226090a538e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6f52aa6e2a0da763ca0091b3771d1c25_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6f52aa6e2a0da763ca0091b3771d1c25_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6f52aa6e2a0da763ca0091b3771d1c25_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6faa2c6456db4413927b19b9cbfe4176_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6faa2c6456db4413927b19b9cbfe4176_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6faa2c6456db4413927b19b9cbfe4176_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6fd1b2efc24f6bc630680f8de7c31576_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6fd1b2efc24f6bc630680f8de7c31576_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6fd1b2efc24f6bc630680f8de7c31576_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6fdf990c9cc944ccf5688a804f6ed35c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6fdf990c9cc944ccf5688a804f6ed35c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6fdf990c9cc944ccf5688a804f6ed35c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/70dab5b17ce15a319dd531324de9c9fe_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/70dab5b17ce15a319dd531324de9c9fe_img.jpg deleted file mode 100644 index 87c83cb7f96859c226439032f95aec50a67da67b..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/70dab5b17ce15a319dd531324de9c9fe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:37b694c775790bff74133ee0166fc7e3ee5889e8a117d89da2998abacb1bcb1b -size 4538 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7183d7b44e8c46abd64438b3894a0902_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7183d7b44e8c46abd64438b3894a0902_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7183d7b44e8c46abd64438b3894a0902_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/728a02fe4a04e7f91835147194997cd4_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/728a02fe4a04e7f91835147194997cd4_img.jpg deleted file mode 100644 index 7a37f1e277934d1e781e604fbda91a28336993b5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/728a02fe4a04e7f91835147194997cd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:04e22ddfa67d1d8642b49b739f10d2533b289e8aa7a74615238a160941eb4fef -size 135515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/73923a5d4eee13d96aa9bd1622b0976f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/73923a5d4eee13d96aa9bd1622b0976f_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/73923a5d4eee13d96aa9bd1622b0976f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7469f7d890531be66ff585ef273e6c1b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7469f7d890531be66ff585ef273e6c1b_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7469f7d890531be66ff585ef273e6c1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/74b47701fe8a059c632b40e009c57a96_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/74b47701fe8a059c632b40e009c57a96_img.jpg deleted file mode 100644 index 24d977e3b347e3b9c5ff55e75ed215215cc98b82..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/74b47701fe8a059c632b40e009c57a96_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:99e4fddb74726c2903b89f602833e17e1a03833c4591d6050ec07dd4a9972e2f -size 120891 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/75e91977269ab11e564cb85a58afda1b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/75e91977269ab11e564cb85a58afda1b_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/75e91977269ab11e564cb85a58afda1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/775e52e123d544d7749813722a13e82f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/775e52e123d544d7749813722a13e82f_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/775e52e123d544d7749813722a13e82f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/77d11d3a8152805a6323635895fdea41_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/77d11d3a8152805a6323635895fdea41_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/77d11d3a8152805a6323635895fdea41_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/782012363ffb161a84600666895ae6e4_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/782012363ffb161a84600666895ae6e4_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/782012363ffb161a84600666895ae6e4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/789ee0a267b24f34bd1f45313e86c9a4_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/789ee0a267b24f34bd1f45313e86c9a4_img.jpg deleted file mode 100644 index 5f3c7180af018140c6c52dfbc3ee0cb685f02609..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/789ee0a267b24f34bd1f45313e86c9a4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d693f303acb7acd6f878b36b55efc7a733e1dbae320298f939581ea3dd35c14a -size 291852 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/78cc63c311cd723d756e4d38fc16ed2a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/78cc63c311cd723d756e4d38fc16ed2a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/78cc63c311cd723d756e4d38fc16ed2a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg deleted file mode 100644 index bf238570411b2c3c4801758e0b4fee8375ccb9f4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef39b9b0dadf1b084c8b8bc63a0ff7d1585b6d745ca12ad8368f11082cad5a0 -size 4493 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7b0303896a557a9a495591a36349e5f7_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7b0303896a557a9a495591a36349e5f7_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7b0303896a557a9a495591a36349e5f7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7b49a5e2da4a559dce8c167c9203ad8e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7b49a5e2da4a559dce8c167c9203ad8e_img.jpg deleted file mode 100644 index 4992c9e6a15c7f137c03e4f3617a94d32531a300..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7b49a5e2da4a559dce8c167c9203ad8e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1ce165a7b51e25e42f58dd3f2c375e128f4ce51edbe853a5833cc14ab188adc1 -size 103136 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7c09b2c099146ec401150512fbd5e3b1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7c09b2c099146ec401150512fbd5e3b1_img.jpg deleted file mode 100644 index a81e124fc1ef6643666dbf24071d9dba2b9650cd..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7c09b2c099146ec401150512fbd5e3b1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:86f2a5cc59bdaf8258d01115f0eba0ed1f32059fdc51763838865d301009057c -size 75261 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7c1ccebd0e8661557a8ffc00cfae58a0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7c1ccebd0e8661557a8ffc00cfae58a0_img.jpg deleted file mode 100644 index 0d9616e841ce4d75ab754e57a26295c390432bfa..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7c1ccebd0e8661557a8ffc00cfae58a0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:096a86d80b42f5a738d7665d511cec60ef08cfdfe0738aa156ae08bc2f1ddace -size 49180 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7e5c50a0a280f43fa1d8cb1fc5e30a20_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7e5c50a0a280f43fa1d8cb1fc5e30a20_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7e5c50a0a280f43fa1d8cb1fc5e30a20_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8071f58c3d57408857130711daf9effe_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8071f58c3d57408857130711daf9effe_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8071f58c3d57408857130711daf9effe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/81513bd390d91f2e7a9b865cf50dce69_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/81513bd390d91f2e7a9b865cf50dce69_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/81513bd390d91f2e7a9b865cf50dce69_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/819f1d00e68b342a246b64fa888a97f9_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/819f1d00e68b342a246b64fa888a97f9_img.jpg deleted file mode 100644 index 3a93e73648b01723280a09ceb7b0e2315d670f23..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/819f1d00e68b342a246b64fa888a97f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6205540d67752a82d9b2cd0515c801e9eaa11dcc21bf7db33af468d662a61051 -size 56785 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/82626dc3515144bcff1786f5764fc4c2_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/82626dc3515144bcff1786f5764fc4c2_img.jpg deleted file mode 100644 index c86ac4bac3c69e70f97b26d7573cf75aa9a92eb4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/82626dc3515144bcff1786f5764fc4c2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7105d36540445b81a332623810fba6311404888c088f45e216667cfc81f2e786 -size 48230 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/854df8ad60507803253274673f9062cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/86e1f8551d4922ea8fa197f96fe4098b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/86e1f8551d4922ea8fa197f96fe4098b_img.jpg deleted file mode 100644 index 6cb34c61ac73d1ae88f2f033b6b561477d514ecc..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/86e1f8551d4922ea8fa197f96fe4098b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:55695849e8efc3dd2849f6924cfb757c61e5379dd7809e51435ef70fe12b5cf6 -size 26296 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/87755376ccda1904b0f5e60a7dd2c465_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/87755376ccda1904b0f5e60a7dd2c465_img.jpg deleted file mode 100644 index 9dd91170838b73c05fd43cd85377afa1c0db744e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/87755376ccda1904b0f5e60a7dd2c465_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1bde40b47c85da389f8c8023e1e8c820623f52023afaeecedfb19c296cf2adb2 -size 4574 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/880668411e1ba0cfd367413b7cb706cf_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/880668411e1ba0cfd367413b7cb706cf_img.jpg deleted file mode 100644 index 28f12e26a0899f46569fb3bb9d07ebb72440b98a..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/880668411e1ba0cfd367413b7cb706cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6d98dd14e41a2664e831ccf1a544b9ed7ed1760dee35cfde6328d637bc300169 -size 41999 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/88f5a639e0e8bae43a30c7ebe33752e5_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/88f5a639e0e8bae43a30c7ebe33752e5_img.jpg deleted file mode 100644 index fbaf939c691489087ba0a23754ec442d1a69f71d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/88f5a639e0e8bae43a30c7ebe33752e5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4e3c17e53098ca937adf6f41929b282f6b659da73656f522416b0928bf5760f5 -size 90851 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8a02c1bd6ac8111aead3a70a4aba750e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8a02c1bd6ac8111aead3a70a4aba750e_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8a02c1bd6ac8111aead3a70a4aba750e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8ac9329cf34ae099200b919cc670223c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8ac9329cf34ae099200b919cc670223c_img.jpg deleted file mode 100644 index 0e2810b1a554a3fa181de818eb905ca10d57a9f6..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8ac9329cf34ae099200b919cc670223c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:25a835efe6976883dba0cea307a5ba469e7d0bdfa992e612f316d8e9a41a827c -size 60060 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8b36c56b042bf3e7ec9b29f35568fe66_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8b36c56b042bf3e7ec9b29f35568fe66_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8b36c56b042bf3e7ec9b29f35568fe66_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8b4befaffc5166da571069410e207aea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg deleted file mode 100644 index a71800404a6607a410485acc2ba7a658933b0001..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:31527d1b23af5b3a00f09d12aa16c1f2a8735efc879ab5e3a079b30491b895fe -size 35914 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8bd9527f7ae16517a90c44e34ced8589_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8bd9527f7ae16517a90c44e34ced8589_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8bd9527f7ae16517a90c44e34ced8589_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8becef26f03c7a4b80768cf8100e0951_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8becef26f03c7a4b80768cf8100e0951_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8becef26f03c7a4b80768cf8100e0951_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8cf3db894a4e83dbac8b094528b24430_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8cf3db894a4e83dbac8b094528b24430_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8cf3db894a4e83dbac8b094528b24430_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/91348ff0578a2d4d17ab1ce9ff0f8990_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/91348ff0578a2d4d17ab1ce9ff0f8990_img.jpg deleted file mode 100644 index 14a37993c47ec9427c0e22b9d312327b196acb85..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/91348ff0578a2d4d17ab1ce9ff0f8990_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0b18708da785c9898700308fffd665d4f73456f7af5689ef910c8ce9643a7ad2 -size 36451 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/92e0feed183e6643329e6c9d933b50f1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/92e0feed183e6643329e6c9d933b50f1_img.jpg deleted file mode 100644 index f6810e1beca7b9f166b8f87d9694c36866f5f50a..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/92e0feed183e6643329e6c9d933b50f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95f1083d6e62ab468ec376639d4636af3ee2b0ac5283fd84b67c8d1685caf89b -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/933a02975dec3041ee2bb07fdb82c92f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/933a02975dec3041ee2bb07fdb82c92f_img.jpg deleted file mode 100644 index c8f1e2777e4f1b45a75b20278bbf26df4f900bc1..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/933a02975dec3041ee2bb07fdb82c92f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f59b1816272ee06d48a4f81c7f70a0e1812c50b5d6dc083b27c01cec11b57d8 -size 99146 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/933f4267f9d2b0ece044e7649be53447_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/933f4267f9d2b0ece044e7649be53447_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/933f4267f9d2b0ece044e7649be53447_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/93bd00a00fa28558486f0664550699b1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/93bd00a00fa28558486f0664550699b1_img.jpg deleted file mode 100644 index 7dcb27e8b2c8f6a1d03a4cd213246730de6316a5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/93bd00a00fa28558486f0664550699b1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1d10fd1b9c87508a1ded8c891d8ff55a77fe029a94c1ca592a9fe1f68b941f0c -size 43786 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/94b678292f1b426e0d16117bb08bfba5_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/94b678292f1b426e0d16117bb08bfba5_img.jpg deleted file mode 100644 index 69c38152e6b37636269ff84c6b134abd4d23df11..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/94b678292f1b426e0d16117bb08bfba5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5e2d6130933e4456bf3525ddcc61a4ca253305637f4c5c8d7f35a5033c4fdae2 -size 4529 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/957e0a1d31f6b69dcd8a355fd185031a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/957e0a1d31f6b69dcd8a355fd185031a_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/957e0a1d31f6b69dcd8a355fd185031a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/964fc0fd54c825b85166fb5a00aa716d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/964fc0fd54c825b85166fb5a00aa716d_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/964fc0fd54c825b85166fb5a00aa716d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index e32dff5973d703d9c268b2c57ee52fba01755283..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3b12e715836cf0f3c6d44bb401046aa0f23085096fc1cb57e59d16b9324db3f2 -size 4533 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/970df246bd8b45f590e294d25c1bb60a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/970df246bd8b45f590e294d25c1bb60a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/970df246bd8b45f590e294d25c1bb60a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/97f6670a8f097f23fe35d62b76d75cf0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/97f6670a8f097f23fe35d62b76d75cf0_img.jpg deleted file mode 100644 index 5b8ab6478da608be8cbceee4162740ef6bf029e0..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/97f6670a8f097f23fe35d62b76d75cf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:73e3818fa00c7ae24940c31519f61ab3c73c6d6c321a46609d5ea8b9d2f7a34c -size 71352 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/98d7c3a3783b091ac41fd87427f1c8e1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/98d7c3a3783b091ac41fd87427f1c8e1_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/98d7c3a3783b091ac41fd87427f1c8e1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9a8f8276c7199f1dd9f3754cf60555c6_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9a8f8276c7199f1dd9f3754cf60555c6_img.jpg deleted file mode 100644 index 87bf372b49641b128e62697ad712ed5209eb84f3..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9a8f8276c7199f1dd9f3754cf60555c6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ab1ff8e85c9f5d81e3f063bd78b3dbe330eb82bddf70af7d4bb8acffa96bb9b8 -size 180512 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9b5bae50a8a287c353f79cf9b43c8a4a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9b5bae50a8a287c353f79cf9b43c8a4a_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9b5bae50a8a287c353f79cf9b43c8a4a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9ba478ec5af01fd2fb458d145565198e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9ba478ec5af01fd2fb458d145565198e_img.jpg deleted file mode 100644 index accc404d8f7b42eb4c307f6316bae39b25f2b4cd..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9ba478ec5af01fd2fb458d145565198e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:119a78a90a161019b5ea9fc906d868cad19bb6aeb81026deb34ae42d9086dfa2 -size 115154 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9bf98e5234e80aa178c89e99397928bf_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9bf98e5234e80aa178c89e99397928bf_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9bf98e5234e80aa178c89e99397928bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9c1b489f9f959fedf0b32924adf2a4dc_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9c1b489f9f959fedf0b32924adf2a4dc_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9c1b489f9f959fedf0b32924adf2a4dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9cf678d634932a43b7f6582878972a5d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9cf678d634932a43b7f6582878972a5d_img.jpg deleted file mode 100644 index 8d123a2bf8aeb8631db158b7ad397f6927500942..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9cf678d634932a43b7f6582878972a5d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:93bbed9b65f816c54918633405d875bfa9369b6a279f4528f01085f9632aa0cb -size 48361 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9e4bce3d0ef8a18588aa58fd3db1cbe3_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9e4bce3d0ef8a18588aa58fd3db1cbe3_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9e4bce3d0ef8a18588aa58fd3db1cbe3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9edb9da00a36a0e140e99e072096ee53_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9edb9da00a36a0e140e99e072096ee53_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/9edb9da00a36a0e140e99e072096ee53_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a3144f9447b85aa19cc0a88f603fb688_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a3144f9447b85aa19cc0a88f603fb688_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a3144f9447b85aa19cc0a88f603fb688_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a5b7735584fef8ef8c84c6755ef27544_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a5b7735584fef8ef8c84c6755ef27544_img.jpg deleted file mode 100644 index d34a980dbcdb0b03b0467c926d8f080ce47194c3..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a5b7735584fef8ef8c84c6755ef27544_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:99f2cfebeb03af5a48c82c2a55f0626a12798ce55e9a936893ecaa00fe17730c -size 108234 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a5f09d21af8c3e909361c622a501c7f2_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a5f09d21af8c3e909361c622a501c7f2_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a5f09d21af8c3e909361c622a501c7f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a76fa39f5daf6a026e032495262ed0f6_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a76fa39f5daf6a026e032495262ed0f6_img.jpg deleted file mode 100644 index 8f364705ca25610ae0e05d2df3b1c533c7fdb1f2..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a76fa39f5daf6a026e032495262ed0f6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f09dedd4bb4b35235d93be5a676ba1712f935b6020e39858b456fd6397e57129 -size 179970 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a780a960b3f2de2493d5785bedae10ff_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a780a960b3f2de2493d5785bedae10ff_img.jpg deleted file mode 100644 index dfb20d594cbb0db5595ba69f971375248fe56cb9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a780a960b3f2de2493d5785bedae10ff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ce7c6b44545bd7638e4122d554854a9d32888a33953b8ce64930ce3230324f23 -size 279932 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index ef5a30696a923c73078098a69c253b840afd49bf..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4740293d46a2fbf93ce3520b8ec7ea20bdcd1e5e9a26dee8c3689d70c1cb038f -size 4545 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 9dd91170838b73c05fd43cd85377afa1c0db744e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1bde40b47c85da389f8c8023e1e8c820623f52023afaeecedfb19c296cf2adb2 -size 4574 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a90eb5fc0985caf25c17075250c86908_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a90eb5fc0985caf25c17075250c86908_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a90eb5fc0985caf25c17075250c86908_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a9be8b5aa78ae267adfc1152523ec42d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a9be8b5aa78ae267adfc1152523ec42d_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a9be8b5aa78ae267adfc1152523ec42d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/aa5879e72c990f924e434bf9208b0094_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/aa5879e72c990f924e434bf9208b0094_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/aa5879e72c990f924e434bf9208b0094_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ab0a8becb8f7e5a6443afd86481b2f3f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ab0a8becb8f7e5a6443afd86481b2f3f_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ab0a8becb8f7e5a6443afd86481b2f3f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ab3d65655ab371f08589985cafc2316d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ab3d65655ab371f08589985cafc2316d_img.jpg deleted file mode 100644 index 3958b370033dc226f3c9a0d438dab3d2f904116f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ab3d65655ab371f08589985cafc2316d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:48340866d655b0d262ab777be51a55e312f28653170e4471e336927d006eb452 -size 4538 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ab56946aacb4682bb58d2c3e64a9c59e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ab56946aacb4682bb58d2c3e64a9c59e_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ab56946aacb4682bb58d2c3e64a9c59e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/abdd3f96a1e296c46300f2a326213dc0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/abdd3f96a1e296c46300f2a326213dc0_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/abdd3f96a1e296c46300f2a326213dc0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ac1c0fb704fa8fc69e7934267bc074d4_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ac1c0fb704fa8fc69e7934267bc074d4_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ac1c0fb704fa8fc69e7934267bc074d4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/acfeac2f7568d6aec4939bac69beb2e5_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/acfeac2f7568d6aec4939bac69beb2e5_img.jpg deleted file mode 100644 index d76381dfa7e6c397faf175d11bd7265ce0b10b69..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/acfeac2f7568d6aec4939bac69beb2e5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:694dc40725b13b3071fcc1243664de963d9690953b131a0fc0c9908eb727086b -size 37791 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/af01656e21a42c1d856cfb21185cd50e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/af01656e21a42c1d856cfb21185cd50e_img.jpg deleted file mode 100644 index 8fe15dbbde971d270388aec3caa3abbff74b2804..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/af01656e21a42c1d856cfb21185cd50e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:df164ef3461e0571d983d81c3b55d8df06fbbe01f304f06d6e30af6a66f3a932 -size 67642 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b02ba0b73e95416eb547976f6145b169_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b02ba0b73e95416eb547976f6145b169_img.jpg deleted file mode 100644 index f4e84fb9db9166f32adca8bdd35e72df4c4682c2..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b02ba0b73e95416eb547976f6145b169_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:41bb0d4c3b2f854427e9ec1a86b224b308a02fe353127e616be5645a86d32af7 -size 73407 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg deleted file mode 100644 index 80ca4475d790ccda6d74289fe5243b4dae9fa0b8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9b5e15b84a02ddcd65cffcca1307ab11b1ae1c44519910a4dec7496f1f77f906 -size 69068 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b1fe142ff4f5589424237da7b11b41b6_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b1fe142ff4f5589424237da7b11b41b6_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b1fe142ff4f5589424237da7b11b41b6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b324224acc41e653a93d145e61f98d8c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b324224acc41e653a93d145e61f98d8c_img.jpg deleted file mode 100644 index 141fbdc62d6a7c4f6feda1bfe8c44d950c04af96..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b324224acc41e653a93d145e61f98d8c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:db39ee763a9352985e7ffff991041a5361b07b2854780b51e34840f4adc5b3e0 -size 4549 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b34b4f64f42215bc2d63d6e4d719b901_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b34b4f64f42215bc2d63d6e4d719b901_img.jpg deleted file mode 100644 index 141fbdc62d6a7c4f6feda1bfe8c44d950c04af96..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b34b4f64f42215bc2d63d6e4d719b901_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:db39ee763a9352985e7ffff991041a5361b07b2854780b51e34840f4adc5b3e0 -size 4549 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b35607344f83b254efb342f9662e2063_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b35607344f83b254efb342f9662e2063_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b35607344f83b254efb342f9662e2063_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b4b9911db50edb56242223cbbdfab597_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b4b9911db50edb56242223cbbdfab597_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b4b9911db50edb56242223cbbdfab597_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b4cbe4bfe7868be70d1549b983749783_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b4cbe4bfe7868be70d1549b983749783_img.jpg deleted file mode 100644 index db6dee01f210a3b58e25a62b48b97c28613fd2bd..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b4cbe4bfe7868be70d1549b983749783_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c8cfe392e83ada2f3ffb6b3c98658fe84a6d017638ee290c92f5f507d5ce07e -size 169778 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b543946164dcd60756be812898e547e0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b543946164dcd60756be812898e547e0_img.jpg deleted file mode 100644 index 43480a20730d3ef084f0afc8e0832afb740c2a64..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b543946164dcd60756be812898e547e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d34f29bac764cecf75e01ecfa215bdcf7f922f09d171672aed71f6381b2bf82 -size 97382 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b54ce9bffd341cd643e196d5f4538829_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b54ce9bffd341cd643e196d5f4538829_img.jpg deleted file mode 100644 index 992983e5224b8ba617c00bd2774a89fb28179212..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b54ce9bffd341cd643e196d5f4538829_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c098b3b994b79bc38128542037bde962e9978e940b3ccab0e457ab60202c4761 -size 50796 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b62e6e3b1cbec5de7e750dc0d46bcc79_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b62e6e3b1cbec5de7e750dc0d46bcc79_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b62e6e3b1cbec5de7e750dc0d46bcc79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b6c1148ea4ff3481941a4d3937e7028d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b6c1148ea4ff3481941a4d3937e7028d_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b6c1148ea4ff3481941a4d3937e7028d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b6cafcdfab7ca53f640ddc2d2bae5261_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b6cafcdfab7ca53f640ddc2d2bae5261_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b6cafcdfab7ca53f640ddc2d2bae5261_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b7c458c8f40fa7621871a6777ae65dbb_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b7c458c8f40fa7621871a6777ae65dbb_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b7c458c8f40fa7621871a6777ae65dbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b7deb15a64425aa7a86d391b2f4c848f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b7deb15a64425aa7a86d391b2f4c848f_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b7deb15a64425aa7a86d391b2f4c848f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b7e8758ea655fc07d3aadaf2d8408d6e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b7e8758ea655fc07d3aadaf2d8408d6e_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b7e8758ea655fc07d3aadaf2d8408d6e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b822771c1a5790feaeecfc439e08bcdd_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b822771c1a5790feaeecfc439e08bcdd_img.jpg deleted file mode 100644 index 09777675a04e05e5cf7ea42d5a11b9837eb9a56f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b822771c1a5790feaeecfc439e08bcdd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:30319e8f56d014f996f2db98928bd80fcf12f5777edb8c62c7deb324fbdf50f6 -size 46436 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b86a5928690177a50c4fe95603ed3988_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b86a5928690177a50c4fe95603ed3988_img.jpg deleted file mode 100644 index ccb3ff70ad055bce2232f182bd2ec16beddc73d6..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b86a5928690177a50c4fe95603ed3988_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5955765a8ff8886831752f3063a6a2ccfaa86e02238cd53476df11d467788b98 -size 77905 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b8c7900f1e7273ecfbc1a09de0261658_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b8c7900f1e7273ecfbc1a09de0261658_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b8c7900f1e7273ecfbc1a09de0261658_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg deleted file mode 100644 index 1e05e440247c0d9e9f09431b3fdbdc3e1acc1b8e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ba676d18b6a00f27c5bfaec9eeec20be_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f4d1f898ea86dcfccf662ab8e51d9ddff31a2e2b8fd75c90c7148130a0284b9f -size 72903 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bb9f586190c7197099d25db7df9050af_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bb9f586190c7197099d25db7df9050af_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bb9f586190c7197099d25db7df9050af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bc4568cde39ed422b1f3231304177da0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bc4568cde39ed422b1f3231304177da0_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bc4568cde39ed422b1f3231304177da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bcae27bc6aeb49b97b6d51dce8d5c1af_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bcae27bc6aeb49b97b6d51dce8d5c1af_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bcae27bc6aeb49b97b6d51dce8d5c1af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bcb0b443fcfea25dcb7005487af9200d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bcb0b443fcfea25dcb7005487af9200d_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bcb0b443fcfea25dcb7005487af9200d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bd50d56ae2c12a92466ba2aea1a78040_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bd50d56ae2c12a92466ba2aea1a78040_img.jpg deleted file mode 100644 index e302cd0088e0996f10c2c45933531b4bf320ccae..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bd50d56ae2c12a92466ba2aea1a78040_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0c2d1ff60e063816397aaa1d86322eacae94be49f92011f202bd0651dc6bc1d8 -size 64991 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bdcfd1ae573f069075086d7759e45c15_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bdcfd1ae573f069075086d7759e45c15_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bdcfd1ae573f069075086d7759e45c15_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bec099e513efaa5246b7005bfccbd8f6_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bec099e513efaa5246b7005bfccbd8f6_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/bec099e513efaa5246b7005bfccbd8f6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c075f11b8ee283222cbed999bc5a392c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c075f11b8ee283222cbed999bc5a392c_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c075f11b8ee283222cbed999bc5a392c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c0912cb53f8cc1be7ad8d288f5cb0fd0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c0912cb53f8cc1be7ad8d288f5cb0fd0_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c0912cb53f8cc1be7ad8d288f5cb0fd0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c18b9d7d4dc149266c9bf688a50497a5_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c18b9d7d4dc149266c9bf688a50497a5_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c18b9d7d4dc149266c9bf688a50497a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c1bad47c33e0912b92bee4576d99810d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c1bad47c33e0912b92bee4576d99810d_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c1bad47c33e0912b92bee4576d99810d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c2ff6339c62f961f2abd954e987c0082_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c2ff6339c62f961f2abd954e987c0082_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c2ff6339c62f961f2abd954e987c0082_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c31c76c7661af89c477351308864b2ea_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c31c76c7661af89c477351308864b2ea_img.jpg deleted file mode 100644 index 141fbdc62d6a7c4f6feda1bfe8c44d950c04af96..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c31c76c7661af89c477351308864b2ea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:db39ee763a9352985e7ffff991041a5361b07b2854780b51e34840f4adc5b3e0 -size 4549 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c355b8056bdd4728357d7d5ed18792ca_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c355b8056bdd4728357d7d5ed18792ca_img.jpg deleted file mode 100644 index fba02fdf79d39988d50759b1675640219b8057bb..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c355b8056bdd4728357d7d5ed18792ca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:07e71b861bea5821cf5e84484ba6e8edfc3c885f40495154cea648a29916036f -size 204916 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c3c2b3eb8e16ab6cd6acdec0fcf82999_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c3c2b3eb8e16ab6cd6acdec0fcf82999_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c3c2b3eb8e16ab6cd6acdec0fcf82999_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c41b4b0e4f4258e3c69ede6717f6dd33_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c41b4b0e4f4258e3c69ede6717f6dd33_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c41b4b0e4f4258e3c69ede6717f6dd33_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c4738e5ac7f134cb42cac8a06858b8ac_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c4738e5ac7f134cb42cac8a06858b8ac_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c4738e5ac7f134cb42cac8a06858b8ac_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index bf238570411b2c3c4801758e0b4fee8375ccb9f4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef39b9b0dadf1b084c8b8bc63a0ff7d1585b6d745ca12ad8368f11082cad5a0 -size 4493 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c557fa1bd8f95590281c8ba61b175740_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c557fa1bd8f95590281c8ba61b175740_img.jpg deleted file mode 100644 index 64e2be3fd6d813c5c230efc502ba25802e1db4e4..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c557fa1bd8f95590281c8ba61b175740_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:21c8fdd1e9d07de76cef0fb6e2d32cd1fde62b15a5e18d9fe0edd696440d9d15 -size 43433 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c636e9b650fe8c661dec4486ffc434fd_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c636e9b650fe8c661dec4486ffc434fd_img.jpg deleted file mode 100644 index 195cca97dc33d2b9cc8a3dbe65aad36449cd8b71..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c636e9b650fe8c661dec4486ffc434fd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b43d10e3808bd355daf8983ce77e9abc0f02b33ba25bcbaf471046480d623412 -size 7797 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c64cb9cea0b6a1d33fd640041210d38c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c64cb9cea0b6a1d33fd640041210d38c_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c64cb9cea0b6a1d33fd640041210d38c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c6fd5cb542ee6c63f2acd62896ffcc35_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c6fd5cb542ee6c63f2acd62896ffcc35_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c6fd5cb542ee6c63f2acd62896ffcc35_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c6ffc947df5e0a0aee6304d52999ee3b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c6ffc947df5e0a0aee6304d52999ee3b_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c6ffc947df5e0a0aee6304d52999ee3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c76f518c4d95210969837b001e52d73b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c76f518c4d95210969837b001e52d73b_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c76f518c4d95210969837b001e52d73b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c95ab75ce8f67ea4200944468d7aea30_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c95ab75ce8f67ea4200944468d7aea30_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c95ab75ce8f67ea4200944468d7aea30_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c981496dcf94656533f6f8ed68816d76_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c981496dcf94656533f6f8ed68816d76_img.jpg deleted file mode 100644 index ab48d5c9fa0171692254389af4e353ab8500c0a1..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c981496dcf94656533f6f8ed68816d76_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8cf2aecad1bbe2c1f4146fffcd6442e3cf3bd299e725ec0b882d76087020c643 -size 78549 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c9b9d380332d98e5579876adfa04eb0f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c9b9d380332d98e5579876adfa04eb0f_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c9b9d380332d98e5579876adfa04eb0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c9c32c022715809003833be0ed198f1c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c9c32c022715809003833be0ed198f1c_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/c9c32c022715809003833be0ed198f1c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cac61a60141d0335b4ae7a081f6b18d4_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cac61a60141d0335b4ae7a081f6b18d4_img.jpg deleted file mode 100644 index f7013593facfab24a8a104c1a7013d9404d918c8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cac61a60141d0335b4ae7a081f6b18d4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:09aa5d3f6f47926e840254515488e69b67ad901ea507e8185f02bfdc56540265 -size 128779 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cb01dfc2db37c44f7ff39b67b5f9d3da_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cb01dfc2db37c44f7ff39b67b5f9d3da_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cb01dfc2db37c44f7ff39b67b5f9d3da_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cc91bf9aed46f8b219ebceaee276d195_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cc91bf9aed46f8b219ebceaee276d195_img.jpg deleted file mode 100644 index 70a8907ee4212f6311abf1168c156efabcd680ed..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cc91bf9aed46f8b219ebceaee276d195_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c74023f111f70738d8b70a5b602111b6c52a90f251355fbcf8a9fff62638d6d1 -size 51295 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cdb7ea1e3072c3b9885c63d496dc7d84_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cdb7ea1e3072c3b9885c63d496dc7d84_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cdb7ea1e3072c3b9885c63d496dc7d84_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg deleted file mode 100644 index c0d28e0771dffbb7293f568d0a206ee0702851ec..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c42e69b9c49eab5d2429054ac554d3c3dbaf3d2c2b7f5bcb89075cd1728faa6a -size 4505 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ce68ff30159c3788e28d166216807520_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ce68ff30159c3788e28d166216807520_img.jpg deleted file mode 100644 index 141fbdc62d6a7c4f6feda1bfe8c44d950c04af96..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ce68ff30159c3788e28d166216807520_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:db39ee763a9352985e7ffff991041a5361b07b2854780b51e34840f4adc5b3e0 -size 4549 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ce98da47ddd68c059657e5cfeeb6beef_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ce98da47ddd68c059657e5cfeeb6beef_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ce98da47ddd68c059657e5cfeeb6beef_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cec3dce43502075ea34c4480ec856a66_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cec3dce43502075ea34c4480ec856a66_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cec3dce43502075ea34c4480ec856a66_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cf03eff1218a8cc1be6b05de892162de_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cf03eff1218a8cc1be6b05de892162de_img.jpg deleted file mode 100644 index 6bf9c427a45587b509eba09420cf09c8aa667f16..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cf03eff1218a8cc1be6b05de892162de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:09d4e8444878b61e55434d51ac007389cc94c8877d13c5621de106d96b7e471e -size 60706 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cf08e441bafa27592ca7f62e33866b53_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cf08e441bafa27592ca7f62e33866b53_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cf08e441bafa27592ca7f62e33866b53_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cf8309144b64cc604254b140a5986dc0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cf8309144b64cc604254b140a5986dc0_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cf8309144b64cc604254b140a5986dc0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cfb616f789aa01c087849ad7701e64d7_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cfb616f789aa01c087849ad7701e64d7_img.jpg deleted file mode 100644 index 417561732aac10dad087e15e194aa76d58d655d1..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cfb616f789aa01c087849ad7701e64d7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7db8ec5ba17e2cdaa098108ef0c1f780d524e71a0c36260a9b948ae0263b2eed -size 203317 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cfc4601b8d1e0773296d4479e218648a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cfc4601b8d1e0773296d4479e218648a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/cfc4601b8d1e0773296d4479e218648a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d175930b7519b8f2f801b636dcce54c8_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d175930b7519b8f2f801b636dcce54c8_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d175930b7519b8f2f801b636dcce54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d1c239cc875fea808eda1d61ca630fac_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d1c239cc875fea808eda1d61ca630fac_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d1c239cc875fea808eda1d61ca630fac_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d28fc4e34c0ef03d0d9264b1ba27ebe2_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d28fc4e34c0ef03d0d9264b1ba27ebe2_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d28fc4e34c0ef03d0d9264b1ba27ebe2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d2b4ad9211363b5097662110e1e5774b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d2b4ad9211363b5097662110e1e5774b_img.jpg deleted file mode 100644 index 3e714442c30cc933cbe38fbb9606af33be5a1c85..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d2b4ad9211363b5097662110e1e5774b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2ae7d9ab6cc8325ba0b75a66fbfb25d024c780161a88edc17d714342cf39d7d3 -size 44227 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d3846f400737fcc7508ce3611705486a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d3846f400737fcc7508ce3611705486a_img.jpg deleted file mode 100644 index 141fbdc62d6a7c4f6feda1bfe8c44d950c04af96..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d3846f400737fcc7508ce3611705486a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:db39ee763a9352985e7ffff991041a5361b07b2854780b51e34840f4adc5b3e0 -size 4549 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d455e47a6d660a3cc29a125a2cbe355b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d455e47a6d660a3cc29a125a2cbe355b_img.jpg deleted file mode 100644 index 28989ffd2f8ea64bfee2c417414f78fcb9b87eea..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d455e47a6d660a3cc29a125a2cbe355b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0434754cf9b2e0876957bfa7042b3812b9d63fcdda5e22ae7bef5dae6a752d46 -size 131699 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d53c20c28af383ce49c214cf2603fbc3_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d53c20c28af383ce49c214cf2603fbc3_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d53c20c28af383ce49c214cf2603fbc3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d74bbadcdb9933d40a743043ad865c65_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d74bbadcdb9933d40a743043ad865c65_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d74bbadcdb9933d40a743043ad865c65_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d7b324ee9d9caae532ed5e898261c278_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d7b324ee9d9caae532ed5e898261c278_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d7b324ee9d9caae532ed5e898261c278_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d7b50eca959bf7bb5bc7a1e2fda6008b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d7b50eca959bf7bb5bc7a1e2fda6008b_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d7b50eca959bf7bb5bc7a1e2fda6008b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d809da419492e18bada207fd4e79bba1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d809da419492e18bada207fd4e79bba1_img.jpg deleted file mode 100644 index 69c38152e6b37636269ff84c6b134abd4d23df11..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d809da419492e18bada207fd4e79bba1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5e2d6130933e4456bf3525ddcc61a4ca253305637f4c5c8d7f35a5033c4fdae2 -size 4529 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d809dd2cb221ce06a3226cb75e31d75d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d809dd2cb221ce06a3226cb75e31d75d_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d809dd2cb221ce06a3226cb75e31d75d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d871d4c53f2d5c336a44d9e2e28fe792_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d871d4c53f2d5c336a44d9e2e28fe792_img.jpg deleted file mode 100644 index 8c6f4597bab4e149808246c224893cf61f7ba7e9..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d871d4c53f2d5c336a44d9e2e28fe792_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1f350411b36a0e417e358f18ad7bd518068c3584a128fcb5e84fb7b9a11452ef -size 72177 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d98654b856f97c5210b36c88cd3dcf37_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d98654b856f97c5210b36c88cd3dcf37_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/d98654b856f97c5210b36c88cd3dcf37_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/da03733d99ab91ed54613c6799a153ba_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/da03733d99ab91ed54613c6799a153ba_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/da03733d99ab91ed54613c6799a153ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/da29bcd4ce1277e82e278506d03fec24_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/da29bcd4ce1277e82e278506d03fec24_img.jpg deleted file mode 100644 index 1d215c43698ab68f0ecb31a83bb468ecebb9d58d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/da29bcd4ce1277e82e278506d03fec24_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:219577c3ec05331c9b8a7c0191e10d0674dcb65bd15281b8ef1f699961ca8f9c -size 111915 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/db17b491805d766560e8c237b84299f1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/db17b491805d766560e8c237b84299f1_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/db17b491805d766560e8c237b84299f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/dda029be056105746c70a40e80692e58_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/dda029be056105746c70a40e80692e58_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/dda029be056105746c70a40e80692e58_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ddcaa42bc4cc7e6a8ae2695e5cbaf790_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ddcaa42bc4cc7e6a8ae2695e5cbaf790_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ddcaa42bc4cc7e6a8ae2695e5cbaf790_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/de35ef8911c5beed69b407fe13b6de3c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/de35ef8911c5beed69b407fe13b6de3c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/de35ef8911c5beed69b407fe13b6de3c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e010000311ed958dd0bc2b16f8cc23d4_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e010000311ed958dd0bc2b16f8cc23d4_img.jpg deleted file mode 100644 index b96fc375711969a4f4020cd46b2c25453d86b214..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e010000311ed958dd0bc2b16f8cc23d4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d62161a8e64c15b0f221ef819f10d7db4590934d0fd52ba81f7ce648dd66b553 -size 98987 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e0228f9fd9d8457847b4602308e3b060_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e0228f9fd9d8457847b4602308e3b060_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e0228f9fd9d8457847b4602308e3b060_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e0c32e027f49e7404cffe15b93075903_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e0c32e027f49e7404cffe15b93075903_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e0c32e027f49e7404cffe15b93075903_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e211ff0e795ca1dbe9216da5d5a6d950_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e211ff0e795ca1dbe9216da5d5a6d950_img.jpg deleted file mode 100644 index b1cfc0fb6efcf4b6a310bb469ade22e1fa046038..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e211ff0e795ca1dbe9216da5d5a6d950_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:239b0638ac3a06b457d6576f134a888ee0d021add066ee3cf7474ad57e9dbed5 -size 16328 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e21c1cb4c57b5f20293a776cbdb8d31f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e21c1cb4c57b5f20293a776cbdb8d31f_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e21c1cb4c57b5f20293a776cbdb8d31f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e2bef29cdcf149c935e170586b26ae9c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e2bef29cdcf149c935e170586b26ae9c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e2bef29cdcf149c935e170586b26ae9c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg deleted file mode 100644 index 69c38152e6b37636269ff84c6b134abd4d23df11..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5e2d6130933e4456bf3525ddcc61a4ca253305637f4c5c8d7f35a5033c4fdae2 -size 4529 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e60c2d24a97a2855d98671d27ea43d0f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e60c2d24a97a2855d98671d27ea43d0f_img.jpg deleted file mode 100644 index 970c0ac33c6f6252dc11a429ebc5464eccb47726..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e60c2d24a97a2855d98671d27ea43d0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d31589de5233ea019f38d1f3640673bbe89131908e5bc8cfbbe59d5b1f1600c4 -size 63421 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e63b8cb7ecf440e9fa5f83769248f236_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e63b8cb7ecf440e9fa5f83769248f236_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e63b8cb7ecf440e9fa5f83769248f236_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e7b5a7456650ca93650c140cc9a7cab1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e7b5a7456650ca93650c140cc9a7cab1_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e7b5a7456650ca93650c140cc9a7cab1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e7beed289e3bb0399e3188df934dbd85_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e7beed289e3bb0399e3188df934dbd85_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e7beed289e3bb0399e3188df934dbd85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e88514a46354e0a227f104f25530288e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e88514a46354e0a227f104f25530288e_img.jpg deleted file mode 100644 index d07ab5db52c0115400276f7da5761c088457dbf7..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e88514a46354e0a227f104f25530288e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:40d6bfd79c36ef254322b77d3a4ea16e0c0fedde61e015fe4d3afb55e843c86a -size 4528 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e89c5b1964de9c09b6b7012b2de4b1c3_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e89c5b1964de9c09b6b7012b2de4b1c3_img.jpg deleted file mode 100644 index c3d65f5f1fadc6e43cb04f9fbbcd97c4373d67d0..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e89c5b1964de9c09b6b7012b2de4b1c3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4603fbe49267be93e3f3b8a41fbebc7b5747399cb97e95304563b71b72878cf6 -size 46621 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e8edb46e6932fd994c7cbef114ad743a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e8edb46e6932fd994c7cbef114ad743a_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e8edb46e6932fd994c7cbef114ad743a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e938694881f0eb809f192b1935bd79b4_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e938694881f0eb809f192b1935bd79b4_img.jpg deleted file mode 100644 index 0c95fad7b279414e2ea04f1f27a56884508bddf8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e938694881f0eb809f192b1935bd79b4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:05ae7ff25f65cc52651de09b32893e6d570efc8cc17bb00004259dc79aaf9b3e -size 123883 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/eb48ed8d7efab7455ebd9f62bb214f33_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/eb48ed8d7efab7455ebd9f62bb214f33_img.jpg deleted file mode 100644 index e32dff5973d703d9c268b2c57ee52fba01755283..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/eb48ed8d7efab7455ebd9f62bb214f33_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3b12e715836cf0f3c6d44bb401046aa0f23085096fc1cb57e59d16b9324db3f2 -size 4533 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ebf138e9f76230f0b227bbaba67d9699_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ebf138e9f76230f0b227bbaba67d9699_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ebf138e9f76230f0b227bbaba67d9699_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ec8ccddfc249ec9ea81a9173a7fb19d8_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ec8ccddfc249ec9ea81a9173a7fb19d8_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ec8ccddfc249ec9ea81a9173a7fb19d8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ecae674475cecdd0962200a5d1e2591e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ecae674475cecdd0962200a5d1e2591e_img.jpg deleted file mode 100644 index a02bc7a689270242fb0c8c8e072e1afe4f19ef2d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ecae674475cecdd0962200a5d1e2591e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:02b8c353e15dfea9f5c89450dcd5883b025ab6d9273007255f5b071f57307af9 -size 35431 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ecc17272f7951b956169a2905f5862ea_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ecc17272f7951b956169a2905f5862ea_img.jpg deleted file mode 100644 index a63fd0b02ae06b7927ed6d9a1071390890e641f5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ecc17272f7951b956169a2905f5862ea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe6dbcce980f5cd86ae32fee30c8d45d669475253ec27a5d6eb9035ac2502bbd -size 4613 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ed12f6b9acb5a2066b16f7a2a6d5e2c1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ed12f6b9acb5a2066b16f7a2a6d5e2c1_img.jpg deleted file mode 100644 index 6b2ecfc226e548956eaec4fff13fcec40472c410..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ed12f6b9acb5a2066b16f7a2a6d5e2c1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7595105affd15b77108b4624969d4b6acb33a4fb5477552572f9cca06987a917 -size 7578 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/eda00580f1bc1ce2aa1e306b85a94dbd_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/eda00580f1bc1ce2aa1e306b85a94dbd_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/eda00580f1bc1ce2aa1e306b85a94dbd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/edcab60b3c92e05a58f7411ce1d16288_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/edcab60b3c92e05a58f7411ce1d16288_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/edcab60b3c92e05a58f7411ce1d16288_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ee5bafe10ff1ed7c138abb928006e86d_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ee5bafe10ff1ed7c138abb928006e86d_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ee5bafe10ff1ed7c138abb928006e86d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ee78d993a5565b0f905888c3f904da99_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ee78d993a5565b0f905888c3f904da99_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ee78d993a5565b0f905888c3f904da99_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ee8c1f218854cc10676f0e2a9f3583d2_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ee8c1f218854cc10676f0e2a9f3583d2_img.jpg deleted file mode 100644 index 69c38152e6b37636269ff84c6b134abd4d23df11..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ee8c1f218854cc10676f0e2a9f3583d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5e2d6130933e4456bf3525ddcc61a4ca253305637f4c5c8d7f35a5033c4fdae2 -size 4529 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/efcb78ce7df315911219258bc2132f8c_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/efcb78ce7df315911219258bc2132f8c_img.jpg deleted file mode 100644 index 18e7be649b6d3459bda46d471573086cadb73cc0..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/efcb78ce7df315911219258bc2132f8c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b0576a8722e862e47967722c2c8cbbff9d0c2f5e88e1e3b1345e6398daf3dac1 -size 40992 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f0c19cb19ae7a343d5f9202936fb6073_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f0c19cb19ae7a343d5f9202936fb6073_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f0c19cb19ae7a343d5f9202936fb6073_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f19f0f73f11a36b497d3c8ef01dff1b5_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f19f0f73f11a36b497d3c8ef01dff1b5_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f19f0f73f11a36b497d3c8ef01dff1b5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f1d870c901879a8a045ece56cc5b1980_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f1d870c901879a8a045ece56cc5b1980_img.jpg deleted file mode 100644 index 8e87d98c7765c0b34e523157f361350f979c98e8..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f1d870c901879a8a045ece56cc5b1980_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a9b2d6396605ea11947ffd62bc1cfa76bcf474ca2bd8ed34f657a61487116a1c -size 4550 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f3d3e0a60abdafe4358260627581113a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f3d3e0a60abdafe4358260627581113a_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f3d3e0a60abdafe4358260627581113a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index 69c38152e6b37636269ff84c6b134abd4d23df11..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5e2d6130933e4456bf3525ddcc61a4ca253305637f4c5c8d7f35a5033c4fdae2 -size 4529 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f48cf940639a2d36749ccb71f4e3faea_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f48cf940639a2d36749ccb71f4e3faea_img.jpg deleted file mode 100644 index e42257e5822a3cf76d5038dd346016480a196b73..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f48cf940639a2d36749ccb71f4e3faea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7e86f48c15d433b8454f30992d635b629b21ec82d73ad687662ebcf7c5f477 -size 4525 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f54a2a3dde9b823d049845884cbd166a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f54a2a3dde9b823d049845884cbd166a_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f54a2a3dde9b823d049845884cbd166a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f55d491cfb2497e8becc9cf1fc6be4c8_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f55d491cfb2497e8becc9cf1fc6be4c8_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f55d491cfb2497e8becc9cf1fc6be4c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg deleted file mode 100644 index f9b9aaccaf25777106114d888450a4b9a1511d1e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fac851b45bcb7d7bf6d3c88d44e464241719dacf97095e8281f72a34748edcc3 -size 170048 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f74adaa1840504407cd4272995426f82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f75386a4b2a20cebdd81fa18e839be4f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f75386a4b2a20cebdd81fa18e839be4f_img.jpg deleted file mode 100644 index a000bbb2bf21ca50dba6f1e55dd1ebd34a46fb4d..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f75386a4b2a20cebdd81fa18e839be4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ce882079a2eaaf97a7b36d0aa9fc7ad401bd14d9d5dac9b866a396eff0185446 -size 310392 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f7a1b96924f2d36f5643700fbb7cc2ea_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f7a1b96924f2d36f5643700fbb7cc2ea_img.jpg deleted file mode 100644 index 553e835c315903bcdd2795d1d51fe0e710739f4e..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f7a1b96924f2d36f5643700fbb7cc2ea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e2a78eda186beca0020d758425da410b1134445df658bdac4fd0552dfd9ed8bc -size 103737 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fa849f3297b46a8d257e718ba0720135_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fa849f3297b46a8d257e718ba0720135_img.jpg deleted file mode 100644 index 52123ea4d17cd9e297c1829a74a1a1a044ba1785..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fa849f3297b46a8d257e718ba0720135_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:df5ff6491e433e44cf6047abc4ef880e546a4627283a5a2b6cf9e59f4bfad9a5 -size 72707 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fa9f113a14954a4741c64d911be324e9_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fa9f113a14954a4741c64d911be324e9_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fa9f113a14954a4741c64d911be324e9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fabe931a97ba32b2e81af497e57033f1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fabe931a97ba32b2e81af497e57033f1_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fabe931a97ba32b2e81af497e57033f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/facce731b2dbfae43a8609231a700be1_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/facce731b2dbfae43a8609231a700be1_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/facce731b2dbfae43a8609231a700be1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fb53db2423b5ba8ab6dc10dc9f384450_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fb53db2423b5ba8ab6dc10dc9f384450_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fb53db2423b5ba8ab6dc10dc9f384450_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fb73a07d61dc5c47709b9802b894d716_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fb73a07d61dc5c47709b9802b894d716_img.jpg deleted file mode 100644 index c4b0dd79aa095c35fa2f9c7edc68d82adb750386..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fb73a07d61dc5c47709b9802b894d716_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3deb24903ebb1ae3a16e3e86dece45cb3a94bda9920049e561c315e8ca2ddc67 -size 48474 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fbd10feb132607962f09a7f6bfb69df6_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fbd10feb132607962f09a7f6bfb69df6_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fbd10feb132607962f09a7f6bfb69df6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fbee1b51966e04afd72119133d952535_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fbee1b51966e04afd72119133d952535_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fbee1b51966e04afd72119133d952535_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fc3e2b49a9f850951570e502393b697f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fc3e2b49a9f850951570e502393b697f_img.jpg deleted file mode 100644 index b7fcc63e83919d9e2b436f6a26cce3269782553c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fc3e2b49a9f850951570e502393b697f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2287f010643d7add6c956c09ce54673625ce2b5b471b17dc49e8a6dc0ab54524 -size 122118 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 57842b0349bd33ea7a2c39ae2f7d6548646450d5..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bbf7d89f9fc9bdcae61bc8efea3545da79b29264b690fbc360f6ea47d62f4fc7 -size 4511 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fdff3385d0aee2b2113ba512b60f194e_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fdff3385d0aee2b2113ba512b60f194e_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fdff3385d0aee2b2113ba512b60f194e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fe77f3082a0ce5eaa1f8f74877eb10bd_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fe77f3082a0ce5eaa1f8f74877eb10bd_img.jpg deleted file mode 100644 index 141fbdc62d6a7c4f6feda1bfe8c44d950c04af96..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fe77f3082a0ce5eaa1f8f74877eb10bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:db39ee763a9352985e7ffff991041a5361b07b2854780b51e34840f4adc5b3e0 -size 4549 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fec5f1bac5cf3187f7618d1adb95871f_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fec5f1bac5cf3187f7618d1adb95871f_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/fec5f1bac5cf3187f7618d1adb95871f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ff81d88ebb5c5673a41bbcf9e41f6763_img.jpg b/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ff81d88ebb5c5673a41bbcf9e41f6763_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG4/O-RAN.WG4.TS.MP.0-R005-v20.00/images/ff81d88ebb5c5673a41bbcf9e41f6763_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/doc.md b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/doc.md deleted file mode 100644 index 2c35b693833a6ba2173e08b2e2f9b0d7c9a0a432..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/doc.md +++ /dev/null @@ -1,543 +0,0 @@ - - -![O-RAN ALLIANCE logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) - -The logo for the O-RAN ALLIANCE, featuring a colorful circular icon to the left of the text "O-RAN" in blue, with "ALLIANCE" in smaller blue letters underneath. - -O-RAN ALLIANCE logo - -# --- **O-RAN Work Group 5 ( Open F1/W1/E1/X2/Xn/D2 interfaces )** - -## **D2 Interface: O&M Requirements** - -Copyright © 2025 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 - -- List of figures ..... 3 -- List of tables ..... 3 -- Foreword..... 4 -- Modal verbs terminology ..... 4 -- Executive summary ..... 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 ..... 7 -- 3.1 Terms ..... 7 -- 3.2 Symbols..... 7 -- 3.3 Abbreviations..... 7 -- 4 Configuration Parameters..... 8 -- 4.1 Parameter Name and Description ..... 8 -- 4.1.1 TimingList..... 8 -- 4.1.5 Cell List..... 10 -- 5 Performance Measurement..... 10 -- Annex A (informative): Flow Diagram for D2-c and D2-u ..... 11 -- Annex (informative): Change history/Change request (history) ..... 17 - -# --- List of figures - -Figure 1: D2 interface between O-DUs connected to same O-CU-CP and O-CU-UP..... 5 -Figure 2: D2-c protocol architecture..... 5 -Figure 3: D2-u protocol architecture..... 6 -Figure 4: T1, T2, T3 Parameters relationship with respect to SCell OTA slot..... 9 -Figure 5: D2CP Interface Management Function..... 13 -Figure 6: D2CP UE management functions..... 15 -Figure 7: D2UP messages..... 16 - -# --- List of tables - -Table 1: Counters for D2 interface ..... 10 - -# Foreword - -This Technical Specification (TS) has been produced by WG5 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. - -# Executive summary - -D2 interface, defined by O-RAN Alliance, connects a pair of O-DUs (O-RAN Distributed Units). D2 interface plays an essential role in supporting various use cases for enhancing the user experience and efficient use of spectral resources such as inter O-DU carrier aggregation. - -The present document outlines the configuration parameters required for establishment and functioning of D2 interface. Existing O1 interface towards O-DU shall be used by SMO to configure these parameters. SMO can define the counters and KPIs as mentioned in the present document for monitoring the D2 interface. - -# Introduction - -D2 interface is introduced between the O-DUs to support control and user data exchange. Figure 5.1-2 in O-RAN WG1.OAD [1] shows the D2 interface in O-RAN architecture. - -O-DUs connected via D2 interface can be connected to same or different O-CU-CPs and O-CU-UPs. Figure 1 adopted from O-RAN WG5.D2.GAP Figure 4.2-1, shows the cases where all the O-DUs are connected to same O-CU-CP and O-CU-UP. D2-c indicates the control part of D2 interface while D2-u is the user plane part. - -![Figure 1: D2 interface between O-DUs connected to same O-CU-CP and O-CU-UP. The diagram shows an O-CU-UP1 connected to an O-CU-CP1 via an E1 interface. O-CU-CP1 is connected to three O-DUs (O-DU1, O-DU2, O-DUn) via F1-c interfaces. O-CU-UP1 is connected to the same O-DUs via F1-u interfaces. Each O-DU is connected to an O-RU (O-RU1, O-RU2, O-RU3) via an Open FH interface. D2-c/D2-u interfaces are shown between O-DU1 and O-DU2, and between O-DU2 and O-DUn.](e394c2b5c61344f6a12397f430086072_img.jpg) - -Figure 1: D2 interface between O-DUs connected to same O-CU-CP and O-CU-UP. The diagram shows an O-CU-UP1 connected to an O-CU-CP1 via an E1 interface. O-CU-CP1 is connected to three O-DUs (O-DU1, O-DU2, O-DUn) via F1-c interfaces. O-CU-UP1 is connected to the same O-DUs via F1-u interfaces. Each O-DU is connected to an O-RU (O-RU1, O-RU2, O-RU3) via an Open FH interface. D2-c/D2-u interfaces are shown between O-DU1 and O-DU2, and between O-DU2 and O-DUn. - -Figure 1: D2 interface between O-DUs connected to same O-CU-CP and O-CU-UP - -Transport protocol for D2-c is SCTP over IP similar to the F1-c protocol architecture. Figure 2 shows the protocol architecture for D2-c part as defined in D2 GAP specification [2]. Application protocol for D2-c is named as D2CP which provides signalling aspects of D2 interface such as D2 interface setup, reconfiguration and other UE associated procedures. - -![Figure 2: D2-c protocol architecture. The diagram shows a stack of protocols for the Control Plane. At the top is the Application layer containing D2CP. Below it is a horizontal line representing the SCTP layer. Below SCTP are the Transport Network layers: IP, Data Link Layer, and Physical Layer.](f76f0f5dfff2511b51f6b875867c029f_img.jpg) - -Figure 2: D2-c protocol architecture. The diagram shows a stack of protocols for the Control Plane. At the top is the Application layer containing D2CP. Below it is a horizontal line representing the SCTP layer. Below SCTP are the Transport Network layers: IP, Data Link Layer, and Physical Layer. - -Figure 2: D2-c protocol architecture - -D2-u messages are transported by UDP over IP similar to F1-u protocol architecture (except GTP). The latency requirement for D2-u ( within 200us one way) is much lower compared to F1-u. Between a pair of O-DU nodes, one or more UDP ports may be used for D2-u. Figure 3 shows the D2-u protocol architecture as defined in D2 GAP specification [2]. D2UP is the application protocol defined for supporting D2-u functionality. It is used to exchange user level data and other critical control information for handling the user data such as PUCCH allocation information, transfer of CSI and HARQ feedback from UE etc. - -![Figure 3: D2-u protocol architecture diagram showing layers: Application layer (D2UP), Transport network layer (UDP, IP, Data link layer, Physical layer) separated by a central interface symbol.](a7d78d22e465dea388b31d0739f9d0cd_img.jpg) - -The diagram illustrates the D2-u protocol architecture. At the top, the 'Application layer' contains a box labeled 'D2UP'. Below this is a horizontal line with a circle and a cross inside, representing an interface. Below the interface, the 'Transport network layer' is shown as a stack of four boxes: 'UDP', 'IP', 'Data link layer', and 'Physical layer'. - -Figure 3: D2-u protocol architecture diagram showing layers: Application layer (D2UP), Transport network layer (UDP, IP, Data link layer, Physical layer) separated by a central interface symbol. - -Figure 3: D2-u protocol architecture - -# 1 Scope - -The present document specifies the counters and configuration parameters requirements for D2 interface. Parameters can be configured by SMO to O-DU via O1 interface for D2 interface functioning. - -# 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.WG5.TS.D2-GAP: "D2 Interface: General Aspects and Principles". - -## 2.2 Informative references - -References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. 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: - -**beam:** main lobe of a radiation pattern from an AAS BS - -NOTE: For certain AAS BS antenna array, there may be more than one beam. - -**carrier aggregation:** aggregation of two or more NR or E-UTRA component carriers in order to support wider transmission bandwidths - -**D2 interface:** The inter O-DU interface to enable multi-vendor carrier aggregation in NR is named as D2 according to WG1 ATG definitions. - -**PCell O-DU:** O-DU, where the PCell is configured for a UE to support inter O-DU carrier aggregation. - -**pO-DU:** O-DU, where the PCell is configured for a UE to support inter O-DU carrier aggregation. This is same as PCell O-DU used in the D2 GAP specifications. - -**SCell O-DU:** O-DU, where only SCell(s) are configured for a UE to support inter O-DU carrier aggregation. - -**sO-DU:** O-DU, where only SCell(s) are configured for a UE to support inter O-DU carrier aggregation. This is same as SCell O-DU used in the D2 GAP specifications. - -## 3.2 Symbols - -For the purposes of the present document, the symbols [given in [i.1] and the following] apply: - -$N_{RB}$ Transmission bandwidth configuration, expressed in units of resource blocks (for E-UTRA) - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given in [i.1] and the following apply: - -| | | -|------------|-----------------------------------------| -| AAS | Active Antenna System | -| CRNTI | Cell Radio Network Temporary Identifier | -| CA | Carrier Aggregation | -| D2-c | D2 Control plane interface | -| D2CP | D2 Control plane Protocol | -| D2-u | D2 User Plane interface | -| D2UP | D2 User Plane Protocol | -| DL | Downlink | -| gNB | g NodeB | -| MAC | Medium Access Control | -| O-CU-CP | O-RAN Central Unit – Control Plane | -| O-CU-UP | O-RAN Central Unit – User Plane | -| O-DU | O-RAN Distributed Unit | -| OTA | Over-the-Air | -| O-RU | O-RAN Radio Unit | -| PCell O-DU | Primary cell O-DU | -| PCI | Physical Cell Identity | -| PDCCH | Physical downlink control channel | -| PUSCH | Physical downlink shared channel | - -| | | -|------------|--------------------------------------| -| PUCCH | Physical uplink control channel | -| RTT | Round Trip Time | -| SCell O-DU | Secondary cell O-DU | -| SCTP | Stream Control Transmission Protocol | -| TB | Transport block | -| UE | User Equipment | - -# --- 4 Configuration Parameters - -## 4.1 Parameter Name and Description - -### 4.1.1 TimingList - -This is a list of timing information for the self and peer O-DUs. First entry in the list contains information for the O-DU where configuration is done. All other entries shall be set as per the peer O-DUs information. Order in this list shall be same as the D2-c IP Address and SCTP port Num as defined in clause 4.1.5. - -#### 4.1.1.1 T1 - -This parameter as shown in Figure 4, with reference to a given OTA slot, indicates the minimum time required by SCell O-DU to process and transmit data to a UE once data is received from PCell O-DU on D2 interface. It is defined in microseconds. If the DL DATA TRANSFER and PUCCH RESOURCE TRANSFER for a given OTA slot arrives later than this time, SCell O-DU may not transmit the data to the UE in the OTA indicated. - -#### 4.1.1.2 T2 - -This parameter as shown in Figure 4, with reference to a given OTA slot in DL DATA REQUIRED message, indicates the minimum time required by PCell O-DU to process and respond to DL DATA REQUIRED message, and subsequent transmission of data in the OTA slot. It is defined in microseconds. If PCell O-DU receives the DL DATA REQUIRED message later than T2 time, it returns failure to SCell O-DU in PUCCH RESOURCE TRANSFER message. - -#### 4.1.1.3 T3 - -This parameter as shown in Figure 4, indicates the latest time by which pO-DU may send a DL SCHEDULING REQUEST message requesting scheduling for a given OTA slot. It is defined in microseconds. If DL SCHEDULING REQUEST message contains slot range lesser than T3, sO-DU shall ignore the received DL SCHEDULING REQUEST message. sO-DU shall consider the slots that are greater than T3 as valid slots for scheduling the UEs. - -![Timing diagram showing the relationship between DL Scheduling Request, DL Data Required, and DL Data Transfer messages relative to the SCell OTA slot. It defines deadlines T1, T2, and T3 for these messages. T1 is the deadline for DL DATA TRANSFER/PUCCH RESOURCE TRANSFER. T2 is the deadline for DL DATA REQUIRED. T3 is the deadline for DL SCHEDULING REQUEST. The diagram also shows the flow of data from the sDU to the pDU and finally to the UE via PDCCH/PDSCH at TA=0.](562f471e8153729557e6a4ee6343c32c_img.jpg) - -The diagram illustrates the timing constraints for downlink (DL) data transfer in an O-RAN system. It shows two horizontal timelines representing the sDU (top) and pDU (bottom) over a series of slots. - -Key events and deadlines: - -• **DL SCHEDULING REQUEST**: Sent from sDU to pDU. Deadline **T3** is defined as $T1 + RTT/2 + xx + RTT/2 + yy$ . - -• **DL DATA REQUIRED**: Sent from sDU to pDU. Deadline **T2** is defined as $T1 + RTT/2 + xx$ . A note indicates: "If DL DATA TRANSFER message arrives late, it cannot be". - -• **DL DATA TRANSFER**: Sent from sDU to pDU. Deadline **T1** is the deadline for DL DATA TRANSFER/PUCCH RESOURCE TRANSFER to allow sO-DU time to transmit to UE. - -• **On-air antenna transmission for the slot**: Occurs at **$T_A = 0$** on the sDU timeline, resulting in transmission via **PDCCH/PDSCH** to the UE. - -The relationship between deadlines is given as $|T1| < |T2| < |T3|$ . - -Timing diagram showing the relationship between DL Scheduling Request, DL Data Required, and DL Data Transfer messages relative to the SCell OTA slot. It defines deadlines T1, T2, and T3 for these messages. T1 is the deadline for DL DATA TRANSFER/PUCCH RESOURCE TRANSFER. T2 is the deadline for DL DATA REQUIRED. T3 is the deadline for DL SCHEDULING REQUEST. The diagram also shows the flow of data from the sDU to the pDU and finally to the UE via PDCCH/PDSCH at TA=0. - -Figure 4: T1, T2, T3 Parameters relationship with respect to SCell OTA slot - -NOTE 1: xx, yy in figure 4 indicates the processing time taken by pO-DU and sO-DU for the received messages respectively. - -NOTE 2: $T_A = 0$ in the figure 4 indicates the SCell time where PDCCH/PDSCH is transmitted to UE by sO-DU. - -### 4.1.1 Start CRNTI - -This parameter defines the start CRNTI assigned to each O-DU that supports D2 interface. O-DU may allocate the CRNTI from Start CRNTI till CRNTI Range to the UEs attached to this O-DU. - -NOTE: It is FFS if configuration of Start CRNTI is optional or mandatory. - -### 4.1.2 CRNTI Range - -This parameter defines the range of CRNTI assigned to each O-DU connected via D2 interface. O-DU may allocate the CRNTIs from this range starting from Start CRNTI, to the UEs attached to this O-DU. - -NOTE: It is FFS if configuration of CRNTI Range is optional or mandatory. - -### 4.1.3 D2-c IP Address and SCTP port Num - -This is a configuration list defines the IP address and SCTP port number for the D2-c interface of local O-DU and its peer O-DUs. The first entry in the list indicates the IP address and SCTP port number for the O-DU where configuration is applied. All subsequent entries provide the corresponding details for peer O-DUs with which D2 connections can be established. These IP addresses and port numbers shall be used by local O-DU to establish the SCTP connection with peer O-DUs. - -### 4.1.4 Self D2-u IP Address and port Num - -These parameters define the configuration of the IP address and UDP port number used for establishing the D2-u interface. The specified IP address and UDP port number corresponds to the O-DU where configuration is applied. This information is conveyed to the peer O-DU in D2 SETUP REQUEST/RESPONSE message. This may be a list of IP addresses and port numbers to support multiple endpoints. - -### 4.1.5 Cell List - -This is a list of cells supported by an O-DU that can also support inter O-DU CA via D2 interface. For each entry in the list, the following parameters will be specified: - -#### 4.1.4.1 Cell ID - -PCI for the cell that supports D2 interface for inter O-DU CA. - -#### 4.1.4.2 CA Type - -For each cell that supports inter DU CA, it indicates whether cell supports DL\_ONLY CA, NONE. - -### 4.1.8 T\_clearTB - -This parameter specifies the maximum duration for which the SCell O-DU retains the transport Block (TB) for retransmission following a HARQ failure. The timer is reset when the SCell O-DU receives a DL SCHEDULING REQUEST message indicating retransmission request. Once the timer expires, the HARQ process becomes available for a new transmission, with the NDI bit toggled. - -# 5 Performance Measurement - -The Table 1 lists the O-RAN O1 defined performance measurements related to D2 Interface. - -For complete measurement details, refer WG10 O1 PMeas specification [xx] - -**Table 1: Counters for D2 interface** - -| Measurement Category | Measurements | Description | -|----------------------------------------|-----------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| General Packet measurements | Transmitted D2-C messages | This counter provides the number of the transmitted D2-c messages.
The measurement is calculated per Cell basis.
It shall also be provided on per O-DU basis. | -| | Received D2-C messages | This counter provides the number of the received D2-c messages.
The measurement is calculated per Cell basis.
It shall also be provided on per O-DU basis. | -| C-Plane procedure related measurements | Inter O-DU SCell addition | This counter provides the number of the SCell addition triggered in a O-DU.
The measurement is calculated per O-DU basis. | -| | Inter O-DU SCell addition failure | This counter provides the number of the SCell addition failure in a O-DU. | - -| | | | -|----------------------------------|-------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | The measurement is calculated per O-DU basis | -| U-Plane PDU related measurements | Transmitted DL User Data PDUs | This counter provides the total number of DL DATA TRANSFER message containing DL User data for new transmission.
The measurement is calculated per cell basis. | -| | Received DL User Data PDUs | This counter provides the received total number DL DATA TRANSFER message that contains DL User data for new transmission.
The measurement is calculated per cell basis | -| | Transmitted DL User Data Volume | This counter provides the total bytes (Only new transmission) that are transmitted by PCell O-DU over D2 interface.
The measurement is calculated per cell basis | -| | Received DL User Data Volume | This counter provides the total bytes (Only new transmission) that are received by SCell O-DU over D2 interface.
The measurement is calculated per cell basis | -| | Request for retransmission of DL User Data PDUs | This counter provides the total count of DL SCHEDULING REQUEST messages that are transmitted by PCell O-DU over D2 interface for requesting the retransmission of DL data by SCell O-DU.
The measurement is calculated per cell basis | -| | Retransmitted DL User Data PDUs | This counter provides the total number of DL SCHEDULING REQUEST messages that successfully triggered the retransmission for the UE.
The measurement is calculated per cell basis | -| | Retransmitted DL User Data volume | This counter provides the total bytes that are triggered by PCell O-DU over D2 interface that needs retransmission by SCell O-DU to UE?
The measurement is calculated per SCell basis | -| | DL User PDUs discarded due to delayed reception | This counter provides the total count of all the D2 messages that did not satisfy the T1/T2/T3 timers criteria and hence discarded.
The measurement is calculated per cell basis | - -## Annex A (informative): Flow Diagram for D2-c and D2-u - -Figure 5 indicates the D2CP global messages. These messages are exchanged between O-DUs irrespective of presence of any UE. - -``` -@startuml -Skinparam titleBorderRoundCorner 25 -skinparam titleBorderThickness 2 -skinparam titleBorderColor red -skinparam titleBackgroundColor Coral -skinparam titleFontSize 20 -participant DU1 as "O-DU1" -participant DU2 as "O-DU2" -Note over DU1: O-DU1 is initiating the connection -DU1->DU2 : D2 SETUP REQUEST (\n O-DU1 Cell list, cell Capability etc) -group#Gold #LightBlue Success -DU2->DU1: D2 SETUP RESPONSE (\n O-DU2 Cell list, cell Capability etc) -Note over DU1 : If cells are locked, unlocked or overloaded \nor any other scenario causing -update in Cell config. -DU1->DU2 : D2 CONFIGURATION UPDATE -DU2->DU1 : D2 CONFIGURATION UPDATE ACKNOWLEDGE -Note over DU2: Based on the received cause in Configuration Update, \n context for UEs in that -cell can be released. -Note over DU1: Decides to bring down D2 connection gracefully -DU1->DU2: D2 RELEASE REQUEST -DU2->DU1: D2 RELEASE RESPONSE -Note over DU1, DU2: D2 connection is released. \nAll the D2 contexts is cleared. SCTP -connection is released.\nNo further message exchange over D2 connection. -else #LightPink Failure -DU2->DU1: D2 SETUP FAILURE -End -@enduml -``` - -![Sequence diagram for D2CP Interface Management Function between O-DU1 and O-DU2. The diagram shows a 'Success' path (D2 SETUP REQUEST, D2 SETUP RESPONSE, D2 CONFIGURATION UPDATE, D2 CONFIGURATION UPDATE ACKNOWLEDGE, D2 RELEASE REQUEST, D2 RELEASE RESPONSE) and a 'Failure' path (D2 SETUP FAILURE). Callouts explain the logic, such as O-DU1 initiating the connection, handling cell configurations, and releasing UE contexts.](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) - -``` - -sequenceDiagram - participant O-DU1 - participant O-DU2 - Note left of O-DU1: O-DU1 is initiating the connection - O-DU1->>O-DU2: D2 SETUP REQUEST (O-DU1 Cell list, cell Capability etc) - Note right of O-DU2: Success - O-DU2-->>O-DU1: D2 SETUP RESPONSE (O-DU2 Cell list, cell Capability etc) - Note left of O-DU1: If cells are locked, unlocked or overloaded or any other scenario causing update in Cell config. - O-DU1->>O-DU2: D2 CONFIGURATION UPDATE - O-DU2-->>O-DU1: D2 CONFIGURATION UPDATE ACKNOWLEDGE - Note right of O-DU2: Based on the received cause in Configuration Update, context for UEs in that cell can be released. - Note left of O-DU1: Decides to bring down D2 connection gracefully - O-DU1->>O-DU2: D2 RELEASE REQUEST - O-DU2-->>O-DU1: D2 RELEASE RESPONSE - Note right of O-DU2: D2 connection is released. All the D2 contexts is cleared. SCTP connection is released. No further message exchange over D2 connection. - Note right of O-DU2: [Failure] - O-DU2-->>O-DU1: D2 SETUP FAILURE - -``` - -Sequence diagram for D2CP Interface Management Function between O-DU1 and O-DU2. The diagram shows a 'Success' path (D2 SETUP REQUEST, D2 SETUP RESPONSE, D2 CONFIGURATION UPDATE, D2 CONFIGURATION UPDATE ACKNOWLEDGE, D2 RELEASE REQUEST, D2 RELEASE RESPONSE) and a 'Failure' path (D2 SETUP FAILURE). Callouts explain the logic, such as O-DU1 initiating the connection, handling cell configurations, and releasing UE contexts. - -Figure 5: D2CP Interface Management Function - -Figure 6 indicates the D2CP messages that are exchanged for establishing/releasing or modifying the D2 UE context in SCell O-DU. - -``` - -@startuml -Skinparam titleBorderRoundCorner 25 -skinparam titleBorderThickness 2 -skinparam titleBorderColor red -skinparam titleBackgroundColor Coral -skinparam titleFontSize 20 -participant CU as "O-CU-CP" -participant pDU as "PCell O-DU" -participant sDU as "SCell O-DU" -participant UE -Note over pDU, sDU: D2 connection is up and running -group #lightpink "First UE Addition from a SCell O-DU" -CU->> pDU: UE CONTEXT SETUP/MODIFICATION REQUEST -pDU ->>sDU : UE ADDITION REQUEST -sDU->> pDU: UE ADDITION RESPONSE - -``` - -``` - -pDU ->CU: UE CONTEXT SETUP/MODIFICATION RESPONSE -end -group #lightblue "Addition of more SCells or modification in existing SCells for a UE" -CU-> pDU: UE CONTEXT MODIFICATION REQUEST -pDU ->sDU : UE MODIFICATION REQUEST -sDU-> pDU: UE MODIFICATION RESPONSE -pDU ->CU: UE CONTEXT MODIFICATION RESPONSE (status) -end -CU->UE: RRC Reconfiguration Request (via F1 procedure) -UE->pDU: RRC Reconfiguration Complete -pDU->sDU: UE RECONFIGURATION COMPLETE -group #lightyellow SCell O-DU is unable to handle UE for a SCELL -sDU-> pDU: UE MODIFICATION INDICATION -end -group #lightgreen "Either CU decides to release SCell or UE is Released - UE release function" -CU-> pDU: UE CONTEXT MODIFICATION/RELEASE -pDU ->sDU: UE DELETION REQUEST -sDU-> pDU: UE DELETION RESPONSE -End -@enduml - -``` - -![Sequence diagram showing UE context management between O-CU-CP, PCell O-DU, SCell O-DU, and UE. The diagram is divided into four color-coded sections: 'First UE Addition from a SCell O-DU' (pink), 'Addition of more SCells or modification in existing SCells for a UE' (light blue), 'SCell O-DU is unable to handle UE for a SCELL' (light yellow), and 'Either CU decides to release SCell or UE is Released - UE release function' (light green). A note at the top indicates 'D2 connection is up and running'.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg) - -The sequence diagram illustrates the interaction between four entities: O-CU-CP, PCell O-DU, SCell O-DU, and UE. A note at the top indicates that the D2 connection is up and running. - -**Section 1: "First UE Addition from a SCell O-DU" (Pink)** - -- O-CU-CP sends a **UE CONTEXT SETUP/MODIFICATION REQUEST** to PCell O-DU. -- PCell O-DU sends a **UE ADDITION REQUEST** to SCell O-DU. -- SCell O-DU sends a **UE ADDITION RESPONSE** to PCell O-DU. -- PCell O-DU sends a **UE CONTEXT SETUP/MODIFICATION RESPONSE** to O-CU-CP. - -**Section 2: "Addition of more SCells or modification in existing SCells for a UE" (Light Blue)** - -- O-CU-CP sends a **UE CONTEXT MODIFICATION REQUEST** to PCell O-DU. -- PCell O-DU sends a **UE MODIFICATION REQUEST** to SCell O-DU. -- SCell O-DU sends a **UE MODIFICATION RESPONSE** to PCell O-DU. -- PCell O-DU sends a **UE CONTEXT MODIFICATION RESPONSE (status)** to O-CU-CP. - -**Section 3: RRC Reconfiguration** - -- O-CU-CP sends an **RRR Reconfiguration Request (via F1 procedure)** to UE. -- UE sends an **RRR Reconfiguration Complete** to PCell O-DU. -- PCell O-DU sends a **UE RECONFIGURATION COMPLETE** to SCell O-DU. - -**Section 4: "SCell O-DU is unable to handle UE for a SCELL" (Light Yellow)** - -- SCell O-DU sends a **UE MODIFICATION INDICATION** to PCell O-DU. - -**Section 5: "Either CU decides to release SCell or UE is Released - UE release function" (Light Green)** - -- O-CU-CP sends a **UE CONTEXT MODIFICATION/RELEASE** to PCell O-DU. -- PCell O-DU sends a **UE DELETION REQUEST** to SCell O-DU. -- SCell O-DU sends a **UE DELETION RESPONSE** to PCell O-DU. - -Sequence diagram showing UE context management between O-CU-CP, PCell O-DU, SCell O-DU, and UE. The diagram is divided into four color-coded sections: 'First UE Addition from a SCell O-DU' (pink), 'Addition of more SCells or modification in existing SCells for a UE' (light blue), 'SCell O-DU is unable to handle UE for a SCELL' (light yellow), and 'Either CU decides to release SCell or UE is Released - UE release function' (light green). A note at the top indicates 'D2 connection is up and running'. - -Figure 6: D2CP UE management functions - -Figure 7 captures the messages that will be exchanged over D2 interface for transferring the user data. These messages are exchanged over UDP/IP transport protocols. - -``` - -@startuml -Skinparam titleBorderRoundCorner 15 -skinparam titleBorderThickness 2 -skinparam titleBorderColor red -skinparam titleBackgroundColor Coral -skinparam titleFontSize 30 -participant pDU as "PCell O-DU" -participant sDU as "SCell O-DU" -Note over pDU : DL Data Received from O-CU-UP -Group CSI report -Note over pDU : Receives CSI Indication \nfor the SCell from UE. -pDU->sDU : UCI TRANSFER (CSI, etc.) -end - -Note over pDU: PCell O-DU determines the user data size. it requests \n the SCell O-DU to -schedule the UE in a requested slot range. -Group User Data Transfer -Note over pDU: PCell O-DU may send asynchronously many DL SCHEDULE REQUEST messages \nwith -different user data size and may also extend the slot range -pDU->sDU : DL SCHEDULING REQUEST (Requested User Data size, requested slot range, CSI, etc.) -Note over sDU: SCell O-DU determines the data size and slot it can schedule \n and sends that -to the PCell O-DU -sDU->pDU: DL DATA REQUIRED (Scheduled user data size, selected slot) -Note over sDU: The SCell O-DU may send asynchronously many DL DATA REQUIRED \n messages for -different selected slots -Note Over pDU: Allocates PUCCH resources for the selected slot -pDU->sDU : PUCCH RESOURCE TRANSFER(K1, DAI, etc.) -Note over pDU: PCell O-DU sends the user data TB matching \nthe scheduled size received from -the SCell O-DU -pDU->sDU: DL DATA TRANSFER(User Data TB, etc.) -end - -Group HARQ control, CSI report, TB Clearing -Note over pDU: UE has sent HARQ feedback or CSI report and/or PCell O-DU indicates clearing of -a TB -pDU -> sDU : UCI TRANSFER (HARQ feedback,CSI,TB Clear-flag, etc.) -end -@enduml - -``` - -![Sequence diagram showing D2UP messages between PCell O-DU and SCell O-DU. The diagram is divided into three sections: CSI report, User Data Transfer, and HARQ control, CSI report, TB Clearing. It details the exchange of messages like UCI TRANSFER, DL SCHEDULING REQUEST, DL DATA REQUIRED, PUCCH RESOURCE TRANSFER, and DL DATA TRANSFER with associated notes on data sizes and slot ranges.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) - -``` - -sequenceDiagram - participant PCell O-DU - participant SCell O-DU - - Note left of PCell: DL Data Received from O-CU-UP - Note right of PCell: CSI report - Receives CSI Indication for the SCell from UE. - PCell->>SCell: UCI TRANSFER (CSI, etc.) - Note left of PCell: PCell O-DU determines the user data size. it requests the SCell O-DU to schedule the UE in a requested slot range. - Note right of PCell: User Data Transfer - PCell O-DU may send asynchronously many DL SCHEDULE REQUEST messages with different user data size and may also extend the slot range - PCell->>SCell: DL SCHEDULING REQUEST (Requested User Data size, requested slot range, CSI, etc.) - Note right of SCell: SCell O-DU determines the data size and slot it can schedule and sends that to the PCell O-DU - SCell->>PCell: DL DATA REQUIRED (Scheduled user data size, selected slot) - Note right of SCell: The SCell O-DU may send asynchronously many DL DATA REQUIRED messages for different selected slots - Note left of PCell: Allocates PUCCH resources for the selected slot - PCell->>SCell: PUCCH RESOURCE TRANSFER(K1, DAI, etc.) - Note left of PCell: PCell O-DU sends the user data TB matching the scheduled size received from the SCell O-DU - PCell->>SCell: DL DATA TRANSFER(User Data TB, etc.) - Note right of PCell: HARQ control, CSI report, TB Clearing - UE has sent HARQ feedback or CSI report and/or PCell O-DU indicates clearing of a TB - PCell->>SCell: UCI TRANSFER (HARQ feedback,CSI,TB Clear-flag, etc.) - -``` - -Sequence diagram showing D2UP messages between PCell O-DU and SCell O-DU. The diagram is divided into three sections: CSI report, User Data Transfer, and HARQ control, CSI report, TB Clearing. It details the exchange of messages like UCI TRANSFER, DL SCHEDULING REQUEST, DL DATA REQUIRED, PUCCH RESOURCE TRANSFER, and DL DATA TRANSFER with associated notes on data sizes and slot ranges. - -Figure 7: D2UP messages - -## --- Annex (informative): Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|----------------------------------------------------------------------------| -| 2025.07.22 | 01.00.00 | Initial Version | -| 2025.10.15 | 00.00.01 | Incorporated CRs MAV-0021 | -| 2025.11.10 | 00.00.02 | Incorporated Review comments | -| 2025.11.13 | 00.00.03 | Incorporated Review comments | -| 2025.11.14 | 00.00.04 | Incorporated review comments | -| 2025.11.17 | 00.00.05 | Spec renamed. Incorporated review comments | -| 2025.11.18 | 00.00.06 | Editorial corrections. Some more clarification added for few of the fields | \ No newline at end of file diff --git a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.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/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg deleted file mode 100644 index 9b7dcaed3d403f280f6c076db43198875082b140..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:efabf6ed8f25852d978064ad88bc98f1e3739a80182fc9cfe49c142367b57bea -size 135780 diff --git a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/185df94f4a6a5245323255e844a30ec0_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/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg deleted file mode 100644 index b15fb6854be85483aca923ff59aea82a22504bf5..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:712947c5f55dc376c9c9178b9efcbd72f592d416b1757b5665efde0a8e7a54b3 -size 4569 diff --git a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.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/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/562f471e8153729557e6a4ee6343c32c_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/562f471e8153729557e6a4ee6343c32c_img.jpg deleted file mode 100644 index 013cecc5c185c741a1223005bc60e54332d91b27..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/562f471e8153729557e6a4ee6343c32c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f9831166fa4f92a87c7f2777f89890bd5e7e854a89fb5decf66ec3c4b6e30b33 -size 91241 diff --git a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 364df5703e2728ce466bd0737dc228958c42f689..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1d4f853812c3a1f9820c9d5711d2b089e78052b458d9c8f7021b4cf74759092f -size 4611 diff --git a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg deleted file mode 100644 index 3f91b94c46cce08cadd4cd4cd2fa390d84e14eac..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/a33da0f14e456f92539ce3e9b7d81f9a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:87add0d4bd3ea47a0fcfcfd37d39bc9f02b439817d234a12f4de2ebec610f818 -size 180821 diff --git a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/a7d78d22e465dea388b31d0739f9d0cd_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/a7d78d22e465dea388b31d0739f9d0cd_img.jpg deleted file mode 100644 index 297e8afd8474ccffb2142e628f5edf1aa7ac7625..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/a7d78d22e465dea388b31d0739f9d0cd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8794edce80c68a130c37ecdcc76cb8cc9370b3eea949717398aa6cc7397cfc97 -size 21833 diff --git a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.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/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/e394c2b5c61344f6a12397f430086072_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/e394c2b5c61344f6a12397f430086072_img.jpg deleted file mode 100644 index 6c48aeb8fc2d1affd90b12a6ed3651c1ca4a21d2..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/e394c2b5c61344f6a12397f430086072_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d55d14fd0b0ca866586af98ea1ad43f3a863307f7e8c04a509dcdb140a093b12 -size 56665 diff --git a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/e511e373339b5f948f239b19e0c37dd4_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/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg deleted file mode 100644 index 5736d392f4f3fdfdaadda4605bc5e0fa2beddb23..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2c0835a1035a1afebc89f4c7aca91ca0c9a3744fe6057de2b2f038e0e82994b1 -size 136616 diff --git a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/f76f0f5dfff2511b51f6b875867c029f_img.jpg b/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/f76f0f5dfff2511b51f6b875867c029f_img.jpg deleted file mode 100644 index 5cd2795aad2c6f666c91153964650b9ad09cfb43..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS-D2-O&MRequirements-R005_v01.00/images/f76f0f5dfff2511b51f6b875867c029f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:405c8b5d65706bbbb3717855849c9bee89a9b093fa36daf90addf7b7eba49743 -size 26840 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/doc.md b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/doc.md deleted file mode 100644 index 5897697c40bb67ada3cf18742855248928f9d331..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/doc.md +++ /dev/null @@ -1,4148 +0,0 @@ - - -# --- **O-RAN Work Group 5 (Open F1/W1/E1/X2/Xn/D2 interfaces)****D2 Interface: D2 Application Protocol (D2AP)** - -Copyright © 2025 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 - -| | | -|--------------------------------------------------------------------------|----| -| Contents ..... | 2 | -| List of figures ..... | 4 | -| List of tables ..... | 4 | -| Foreword..... | 5 | -| Modal verbs terminology ..... | 5 | -| 1 Scope..... | 6 | -| 2 References ..... | 6 | -| 2.1 Normative references ..... | 6 | -| 2.2 Informative references ..... | 7 | -| 3 Definition of terms, symbols and abbreviations ..... | 7 | -| 3.1 Terms ..... | 7 | -| 3.2 Symbols..... | 8 | -| 3.3 Abbreviations ..... | 8 | -| 4 Interface principles and characteristics ..... | 9 | -| 4.1 Procedure specification principles ..... | 9 | -| 4.2 Forwards and backwards compatibility ..... | 9 | -| 4.3 Specification notations..... | 9 | -| 5 D2 Control Plane protocol ..... | 10 | -| 5.1 D2CP services..... | 10 | -| 5.2 D2CP Functions ..... | 10 | -| 5.3 D2CP procedures ..... | 10 | -| 5.3.1 Interface Management procedures ..... | 10 | -| 5.3.2 UE Management procedures..... | 14 | -| 5.4 Elements of D2CP Communication..... | 18 | -| 5.4.1 General ..... | 18 | -| 5.4.2 Message Functional Definition and Content..... | 19 | -| 5.4.3 Information Element Definitions ..... | 33 | -| 5.4.4 Message and Information Element Abstract Syntax (with ASN.1) ..... | 44 | -| 5.4.5 Message Transfer Syntax ..... | 66 | -| 5.4.6 Timers..... | 66 | -| 6 D2 User Plane protocol ..... | 67 | -| 6.1 D2UP services..... | 67 | -| 6.2 D2UP Functions ..... | 67 | -| 6.3 D2UP Procedures..... | 67 | -| 6.3.1 Downlink data transfer ..... | 67 | -| 6.3.2 UCI Transfer ..... | 71 | -| 6.4 Elements of D2UP Communication..... | 72 | -| 6.4.1 General ..... | 72 | -| 6.4.2 Message Format for the D2UP..... | 72 | -| 6.4.3 Coding of information elements in frames..... | 77 | -| Annex A (informative): Examples for DL SCHEDULING REQUEST ..... | 85 | -| A.1: New Data transmission: ..... | 85 | -| A.2: Retransmission..... | 87 | -| A.3: New Data transmission and retransmission (Both)..... | 88 | -| Annex (informative): Change history/Change request (history) ..... | 90 | - -# --- List of figures - -| | | -|--------------------------------------------------------------------------------------|----| -| Figure 5.3.1.1-1: D2 Setup, successful operation ..... | 11 | -| Figure 5.3.1.1-2: D2 Setup, unsuccessful operation ..... | 11 | -| Figure 5.3.1.2-1: D2 Configuration Update, successful operation ..... | 12 | -| Figure 5.3.1.2-2: D2 Configuration Update, unsuccessful operation ..... | 12 | -| Figure 5.3.1.3-1: D2 Release ..... | 13 | -| Figure 5.3.1.4-1: D2 Error Indication initiated by O-DU1 ..... | 13 | -| Figure 5.3.1.4-2: D2 Error Indication initiated by O-DU2 ..... | 14 | -| Figure 5.3.2.1-1: UE Addition Procedure ..... | 14 | -| Figure 5.3.2.2-1: UE Modification Update procedure ..... | 16 | -| Figure 5.3.2.3-1: UE Modification Indication procedure ..... | 17 | -| Figure 5.3.2.4-1: UE Reconfiguration Complete procedure ..... | 18 | -| Figure 5.3.2.5-1: UE Deletion procedure ..... | 18 | -| Figure 6.3.1.1-1: DL scheduling request ..... | 68 | -| Figure 6.3.1.2-1: DL data required ..... | 69 | -| Figure 6.3.1.3-1: DL data transfer ..... | 70 | -| Figure 6.3.1.4-1: PUCCH resource transfer ..... | 70 | -| Figure 6.3.2-1: UCI transfer ..... | 71 | -| Figure 6.4.1-1: Example frame format for D2UP ..... | 72 | -| Figure 6.4.2-1: D2-u header ..... | 73 | -| Figure 6.4.2.1-1: DL SCHEDULING REQUEST message format ..... | 74 | -| Figure 6.4.2.2-1: DL DATA REQUIRED message format ..... | 75 | -| Figure 6.4.2.3-1: DL DATA TRANSFER message format ..... | 75 | -| Figure 6.4.2.4-1: PUCCH RESOURCE TRANSFER message format ..... | 76 | -| Figure 6.4.2.5-1: UCI TRANSFER message format ..... | 76 | -| Figure A.1-1: DL SCHEDULING REQUEST with newTx with SlotType as SlotRange ..... | 86 | -| Figure A.1-2: DL SCHEDULING REQUEST with newTx with SlotType as SlotMask ..... | 87 | -| Figure A.2-1: DL SCHEDULING REQUEST for retransmission ..... | 88 | -| Figure A.3-1: DL SCHEDULING REQUEST for transmission and retransmission (Both) ..... | 90 | - -# --- List of tables - -| | | -|-----------------------------------|----| -| Table 6.4.3.3-1: Message ID ..... | 76 | -|-----------------------------------|----| - -# --- Foreword - -This Technical Specification (TS) has been produced by WG5 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 focus of the present document is to specify the stage 3 details of the D2 interface for supporting inter O-DU NR carrier aggregation. The present specification covers the procedures, messages and IEs for establishment and functioning of D2 interface that includes D2 interface bring up procedures, UE addition and configuration, control and user plane information exchange across O-DUs. - -# 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. - -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.WG5.TS.D2GAP: "D2 Interface: General Aspects and Principles". -- [3] 3GPP TS 38.413 V18.6.0: "NG-RAN; NG Application Protocol (NGAP)". -- [4] 3GPP TS 38.401 V18.6.0: "5G; NG-RAN; Architecture description ". -- [5] 3GPP TS 38.331 V18.6.0: "5G; NG-RAN; Radio Resource Control (RRC)". -- [6] 3GPP TS 38.473 V18.6.0: "5G; NG-RAN; F1 Application Protocol (F1AP)". -- [7] 3GPP TS 38.133 V18.10.0: "5G; NG-RAN; Requirements for support of radio resource management". -- [8] 3GPP TS 25.921: "Guidelines and principles for protocol description and error handling". -- [9] IETF RFC 4960: "Stream Control Transmission Protocol". -- [10] IETF RFC 8200 (2017-07): "Internet Protocol, Version 6 (IPv6) Specification". -- [11] IETF RFC 791 (1981-09): "Internet Protocol". -- [12] ITU-T Recommendation X.691 (2002-07): "Information technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER) ". -- [13] ITU-T Recommendation X.680 (2002-07): "Information technology – Abstract Syntax Notation One (ASN.1): Specification of basic notation". -- [14] ITU-T Recommendation X.681 (2002-07): "Information technology – Abstract Syntax Notation One (ASN.1): Information object specification". -- [15] 3GPP TS 23.003 V18.6.0: "Numbering, addressing and identification". -- [16] 3GPP TS 23.501 V18.11.0: "System Architecture for the 5G System". -- [17] 3GPP TS 38.213 V18.7.0: "Physical layer procedures for control". -- [18] 3GPP TS 38.212 V18.7.0: "Physical layer procedures for control". - -- [19] 3GPP TS 29.281 V18.4.0: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)". -- [20] 3GPP TS 38.321 V18.7.0: "Medium Access Control (MAC) protocol specification". - -## 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. - -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: - -**carrier aggregation:** aggregation of two or more NR or E-UTRA component carriers in order to support wider transmission bandwidths - -**PCell O-DU:** O-DU, where the PCell is configured for a UE to support inter O-DU carrier aggregation. - -**pO-DU:** O-DU, where the PCell is configured for a UE to support inter O-DU carrier aggregation. This is same as PCell O-DU used in the D2 GAP specifications. - -**SCell O-DU:** O-DU, where only SCell(s) are configured for a UE to support inter O-DU carrier aggregation. - -**sO-DU:** O-DU, where only SCell(s) are configured for a UE to support inter O-DU carrier aggregation. This is same as SCell O-DU used in the D2 GAP specifications. - -**Elementary Procedure:** D2CP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between the O-DUs. These Elementary Procedures are defined separately and are intended to be used to build up complete sequences in a flexible manner. If the independence between some EPs is restricted, it is described under the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked independently of each other as standalone procedures, which can be active in parallel. An EP consists of an initiating message and possibly a response message. - -Two kinds of EPs are used: - -- Class 1: Elementary Procedures with response (success and/or failure). -- Class 2: Elementary Procedures without response. - -For Class 1 EPs, the types of responses can be as follows: - -Successful: - -- A signaling message explicitly indicates that the elementary procedure successfully completed with the receipt of the response. - -Unsuccessful: - -- A signaling message explicitly indicates that the EP failed. -- On time supervision expiry (i.e., absence of expected response). - -Successful and Unsuccessful: - -- One signaling message reports both a successful and unsuccessful outcome for the different included requests. The response message used is the one defined for successful outcome. - -Class 2 EPs are considered always successful. - -## 3.2 Symbols - -For the purposes of the present document, the symbols [given in [i.1] and the following] apply: - -| | | -|----------|----------------------------------------------------------------------------------------------------------------------| -| $N_{RB}$ | Transmission bandwidth configuration, expressed in units of resource blocks (for E-UTRA) | -|----------|----------------------------------------------------------------------------------------------------------------------| - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given in [i.1] and the following] apply: - -| | | -|---------|--------------------------------------| -| 3GPP | 3rd Generation Partnership Project | -| ASN.1 | Abstract Syntax Notation One | -| CM | Configuration Management | -| D2AP | D2 Application Protocol | -| D2-c | D2 Control plane interface | -| D2CP | D2 Control Protocol | -| D2-u | D2 User Plane interface | -| D2UP | D2 User Plane Protocol | -| gNB | gNodeB (applies to NR) | -| IP | Internet Protocol | -| MAC | Medium Access Control | -| NF | Network Function | -| NGRAN | Next Generation Radio Access Network | -| NR | New Radio | -| 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-RAN | Open Radio Access Network | -| O-RU | O-RAN Radio Unit | -| PCell | Primary Cell | -| RAN | Radio Access Network | -| RLC | Radio Link Control | -| SCell | Secondary Cell | -| SCTP | Stream Control Transmission Protocol | -| SMO | Service Management and Orchestration | -| TR | Technical Report | -| TRS | Trace Recording Session | -| TS | Technical Specification | - -# 4 Interface principles and characteristics - -## 4.1 Procedure specification principles - -The principle for specifying the procedure logic is to specify the functional behaviour of the terminating node exactly and completely. Any rule that specifies the behaviour of the originating node shall be possible to be verified with information that is visible within the system. - -The following specification principles have been applied for the procedure text in clause 5.3 - -- The procedure text discriminates between: - - 1) Functionality which "shall" be executed - -The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the initiating message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value. - -- 2) Functionality which "shall, if supported" be executed - -The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality. - -- Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. - -## 4.2 Forwards and backwards compatibility - -The forward and backward compatibility of the D2CP protocol is assured by a mechanism where all current and future messages, and IEs or groups of related IEs, include ID and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version. - -For D2UP protocol extension fields are added in the messages to support forward and backward compatibility. - -## 4.3 Specification notations - -For the purposes of the present document, the following notations apply: - -- | | | -|-----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Procedure | When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word "procedure", e.g. D2 Setup procedure. | -| Message | When referring to a message in the specification the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. D2 SETUP REQUEST message. | - -- IE When referring to an information element (IE) in the specification the *Information Element Name* is written with the first letters in each word in upper case characters and all letters in Italic font followed by the abbreviation "IE", e.g. *D2 UE ID IE*. -- Value of an IE When referring to the value of an information element (IE) in the specification the "Value" is written as it is specified in the specification enclosed by quotation marks, e.g. "Value". - -# 5 D2 Control Plane protocol - -## 5.1 D2CP services - -D2CP provides the signalling services between the peer O-DUs which are required to fulfil the D2CP functions described in clause 5.2. D2CP services are divided into two groups: - -- Non UE-associated services: They are related to the whole D2 interface instance between the O-DUs utilising a non UE-associated signalling connection. -- UE-associated services: They are related to a UE. D2CP functions that provide these services are associated with a UE-associated signalling connection that is maintained for the UEs in question. - -Unless explicitly indicated in the procedure specification, at any instance in time one protocol endpoint shall have a maximum of one ongoing D2CP procedure related to a certain UE. - -## 5.2 D2CP Functions - -D2CP functions are defined in O-RAN.WG5.TS.D2GAP[2]. - -## 5.3 D2CP procedures - -### 5.3.1 Interface Management procedures - -#### 5.3.1.1 D2 Setup - -The purpose of the D2 Setup procedure is to establish connection with peer O-DUs and exchange the cell level information to interoperate on the D2 interface. This procedure is the first D2 procedure triggered for the D2-C interface after a TNL association has become operational. - -The procedure uses non-UE associated signalling. - -This procedure erases any existing D2 related application data associated with the pair of O-DUs in both the nodes and replaces it by the one received. This procedure also re-initialises the D2 UE-related contexts (if any) and erases all related signalling connections in the two nodes. - -![Sequence diagram showing D2 Setup procedure between O-DU1 and O-DU2. O-DU1 sends a D2 SETUP REQUEST to O-DU2, and O-DU2 responds with a D2 SETUP RESPONSE.](a92b1fdf37a74b707e9f03087c8f1377_img.jpg) - -``` - -sequenceDiagram - participant O-DU1 - participant O-DU2 - Note left of O-DU1: - O-DU1->>O-DU2: D2 SETUP REQUEST - Note right of O-DU2: - O-DU2-->>O-DU1: D2 SETUP RESPONSE - Note left of O-DU1: - -``` - -Sequence diagram showing D2 Setup procedure between O-DU1 and O-DU2. O-DU1 sends a D2 SETUP REQUEST to O-DU2, and O-DU2 responds with a D2 SETUP RESPONSE. - -**Figure 5.3.1.1-1: D2 Setup, successful operation** - -As shown in Figure 5.3.1.1-1, the O-DU1 initiates the procedure by sending a D2 SETUP REQUEST message including the cell information to the O-DU2. The O-DU2 responds with a D2 SETUP RESPONSE message including the cell information. - -The received *Served Cell List* IE in D2 SETUP REQUEST and D2 SETUP RESPONSE messages contains the list of respective SCells for inter O-DU CA. It is stored in receiving node and used for the duration of the operational TNL association. After successful completion of this procedure, the D2 interface is operational and other D2 messages may be exchanged. - -The O-DU1 and O-DU2 may share *Start CRNTI* and *End CRNTI* for the UEs in D2 SETUP REQUEST and D2 SETUP RESPONSE messages. - -The O-DUs exchange the *D2U Info List* IE containing the information for D2-U communication. IP Address and UDP port number to be used for D2-U message exchange in respective O-DUs is specified in D2 SETUP REQUEST and D2 SETUP RESPONSE messages. Receiver O-DU shall use the received IP address and UDP port number while sending D2-U messages to other O-DU. - -*D2U PV List* IE, received in D2 SETUP REQUEST message indicates the D2 protocol version supported by O-DU1. If O-DU2 supports any protocol version from the list in descending order, it shall include the selected protocol version in *D2U PV List* IE while sending D2 SETUP RESPONSE message. - -The O-DUs stores the *T\_clearTB* timer value exchanged in the D2 SETUP REQUEST and D2 SETUP RESPONSE messages. This timer is used during D2-U procedures. Receiver node shall use *T\_ClearTB* IE when it is operating as sO-DU for the UEs. - -![Sequence diagram showing D2 Setup, unsuccessful operation. O-DU1 sends a D2 SETUP REQUEST to O-DU2, and O-DU2 responds with a D2 SETUP FAILURE message.](1eadbbe42cfcac5c0023577110aec5e3_img.jpg) - -``` - -sequenceDiagram - participant O-DU1 - participant O-DU2 - Note left of O-DU1: - O-DU1->>O-DU2: D2 SETUP REQUEST - Note right of O-DU2: - O-DU2-->>O-DU1: D2 SETUP FAILURE - Note left of O-DU1: - -``` - -Sequence diagram showing D2 Setup, unsuccessful operation. O-DU1 sends a D2 SETUP REQUEST to O-DU2, and O-DU2 responds with a D2 SETUP FAILURE message. - -**Figure 5.3.1.1-2: D2 Setup, unsuccessful operation** - -If the O-DU2 cannot accept the setup, it shall respond with a D2 SETUP FAILURE message with *Cause* IE filled with appropriate cause as shown in Figure 5.3.1.1-2. - -If the O-DU2 does not support any of the protocol version indicated in the *D2U PV List* IE, procedure will be considered as failure, and D2 SETUP FAILURE message shall be sent to O-DU1 with cause set as “Protocol Version Not supported”. - -If the D2 SETUP FAILURE message includes the *Time to wait* IE, the O-DU1 shall wait at least for the indicated time before reinitiating the D2 setup towards the O-DU2. - -If the O-DU1 does not receive either D2 SETUP RESPONSE message or D2 SETUP FAILURE message, the O-DU1 may reinitiate the D2 Setup procedure towards the same O-DU node, provided that the content of the new D2 SETUP REQUEST message is identical to the content of the previously unacknowledged D2 SETUP REQUEST message. - -If the O-DU1 receives a D2 SETUP REQUEST message from the peer entity on the same D2 interface: - -- In case the O-DU1 answers with a D2 SETUP RESPONSE message and receives a subsequent D2 SETUP FAILURE, the O-DU1 node shall consider the D2 interface as non operational and the procedure as unsuccessfully terminated. -- In case the O-DU1 answers with a D2 SETUP FAILURE message and receives a subsequent D2 SETUP RESPONSE message, the O-DU1 shall ignore the D2 SETUP RESPONSE message and consider the D2 interface as non operational. - -#### 5.3.1.2 D2 Configuration Update - -The purpose of the D2 Configuration update procedure is to update the cell configuration in peer O-DU. This procedure may be triggered by any O-DU in case of modification in configuration of existing cells, release of any existing cell or addition of new cell. The procedure uses non-UE associated signalling. - -In Figure 5.3.1.2-1, O-DU1 is shown as the triggering node for successful completion of configuration update procedure. - -![Sequence diagram for successful D2 Configuration Update. O-DU1 sends a D2 CONFIGURATION UPDATE message to O-DU2, and O-DU2 responds with a D2 CONFIGURATION UPDATE ACKNOWLEDGE message.](7e670a2b556b53ea9002dfff3a420e08_img.jpg) - -``` - -sequenceDiagram - participant O-DU1 - participant O-DU2 - Note left of O-DU1: - O-DU1->>O-DU2: D2 CONFIGURATION UPDATE - Note right of O-DU2: - O-DU2-->>O-DU1: D2 CONFIGURATION UPDATE ACKNOWLEDGE - Note left of O-DU1: - -``` - -Sequence diagram for successful D2 Configuration Update. O-DU1 sends a D2 CONFIGURATION UPDATE message to O-DU2, and O-DU2 responds with a D2 CONFIGURATION UPDATE ACKNOWLEDGE message. - -Figure 5.3.1.2-1: D2 Configuration Update, successful operation - -The O-DU1 initiates the procedure by sending a D2 CONFIGURATION UPDATE message to the O-DU2 with the configuration that needs to be updated. The O-DU2 responds with a D2 CONFIGURATION UPDATE ACKNOWLEDGE message to confirm that it has successfully updated the configuration data. - -The updated configuration data shall be stored in both nodes and used as long as there is an operational TNL association or until any further update is performed. - -If the *Served Cell To Add Item* IE is contained in the D2 CONFIGURATION UPDATE message, the O-DU2 shall store the information for newly added cell. - -If the *Served Cells To Modify Item* IE is contained in the D2 CONFIGURATION UPDATE message, the O-DU2 shall modify information of existing cell indicated by *Old NR CGI* IE according to the updated information received in the message. - -If the *Served Cells To Delete Item* IE is contained in the D2 CONFIGURATION UPDATE message, the O-DU2 shall delete the cell information indicated by *Old NR CGI* IE. - -The responding node, O-DU2 shall include, within the *Updated Cells Item* IE of the D2 CONFIGURATION UPDATE ACKNOWLEDGE message, all cells that were listed in the *Served Cell To Add Item* and *Served Cells To Modify Item* IEs of the D2 CONFIGURATION UPDATE message. For each cell, the *Result* IE within the *Updated Cells Item* IE shall indicate the outcome of the configuration update procedure, explicitly denoting success or failure. - -Cells specified in the *Served Cells To Delete Item* IE of the D2 CONFIGURATION UPDATE message shall not be included in the D2 CONFIGURATION UPDATE ACKNOWLEDGE message. - -![Sequence diagram for unsuccessful D2 Configuration Update. O-DU1 sends a D2 CONFIGURATION UPDATE message to O-DU2, and O-DU2 responds with a D2 CONFIGURATION UPDATE FAILURE message.](536951b2bbd94325ae266d8d1363df8f_img.jpg) - -``` - -sequenceDiagram - participant O-DU1 - participant O-DU2 - Note left of O-DU1: - O-DU1->>O-DU2: D2 CONFIGURATION UPDATE - Note right of O-DU2: - O-DU2-->>O-DU1: D2 CONFIGURATION UPDATE FAILURE - Note left of O-DU1: - -``` - -Sequence diagram for unsuccessful D2 Configuration Update. O-DU1 sends a D2 CONFIGURATION UPDATE message to O-DU2, and O-DU2 responds with a D2 CONFIGURATION UPDATE FAILURE message. - -Figure 5.3.1.2-2: D2 Configuration Update, unsuccessful operation - -If the O-DU2 cannot accept the update, or if reconfiguration fails for all the cells, it shall respond with a D2 CONFIGURATION UPDATE FAILURE message with *Cause* IE filled with appropriate cause as shown in Figure 5.3.1.2-2. - -If the D2 CONIFGURATION UPDATE FAILURE message includes the *Time to wait* IE, the O-DU1 shall wait at least for the indicated time before reinitiating the D2 CONFIGURAITON UPDATE message towards the same O-DU2. - -#### 5.3.1.3 D2 Release - -The purpose of the D2 Release procedure is to trigger the release of the D2 connection between a pair of O-DUs and erase all D2 application-level data. - -The procedure uses non-UE-associated signaling. - -In Figure 5.3.1.3-1, O-DU1 is shown as the triggering node. - -![Sequence diagram for D2 Release procedure. O-DU1 sends a D2 RELEASE REQUEST to O-DU2, and O-DU2 responds with a D2 RELEASE RESPONSE.](7f17c430b9598e4d748a8041457810b3_img.jpg) - -``` - -sequenceDiagram - participant O-DU1 - participant O-DU2 - O-DU1->>O-DU2: D2 RELEASE REQUEST - O-DU2-->>O-DU1: D2 RELEASE RESPONSE - -``` - -Sequence diagram for D2 Release procedure. O-DU1 sends a D2 RELEASE REQUEST to O-DU2, and O-DU2 responds with a D2 RELEASE RESPONSE. - -Figure 5.3.1.3-1: D2 Release - -O-DU1 initiates the procedure by sending the D2 RELEASE REQUEST message to O-DU2. O-DU1 shall include the cause IE that triggered the release of D2 connection. Upon reception of the D2 RELEASE REQUEST message the O-DU2 shall remove all resources associated with that D2 connection and all D2 application-level data. The O-DU2 shall reply with the D2 RELEASE RESPONSE message. After receiving the D2 RELEASE RESPONSE message, the O-DU1 shall initiate removal of the TNL association towards O-DU2 and shall remove all resources associated with that D2 connection and all D2 application-level data. - -#### 5.3.1.4 Error Indication - -The Error Indication procedure is initiated by an D2 ERROR INDICATION message sent from the receiving node, in order to report detected errors in one incoming message, provided they cannot be reported by an appropriate failure message. - -Figure 5.3.1.4-1 indicates the Error Indication procedure initiated by O-DU1. It can be initiated by O-DU2 as shown in Figure 5.3.1.4-2 in case error is detected on the reception of message from O-DU2. - -![Sequence diagram for D2 Error Indication initiated by O-DU1. O-DU1 sends a D2 ERROR INDICATION message to O-DU2.](af6be343f0c0a8f155f965dcf337b8af_img.jpg) - -``` - -sequenceDiagram - participant O-DU1 - participant O-DU2 - O-DU1->>O-DU2: D2 ERROR INDICATION - -``` - -Sequence diagram for D2 Error Indication initiated by O-DU1. O-DU1 sends a D2 ERROR INDICATION message to O-DU2. - -Figure 5.3.1.4-1: D2 Error Indication initiated by O-DU1 - -![Sequence diagram showing D2 ERROR INDICATION from O-DU2 to O-DU1](eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg) - -``` - -sequenceDiagram - participant O-DU2 - participant O-DU1 - Note left of O-DU1: - Note right of O-DU2: - O-DU2->>O-DU1: D2 ERROR INDICATION - -``` - -Sequence diagram showing D2 ERROR INDICATION from O-DU2 to O-DU1 - -Figure 5.3.1.4-2: D2 Error Indication initiated by O-DU2 - -When the conditions as mentioned below are fulfilled, the Error Indication procedure is initiated by the D2 ERROR INDICATION message sent from the receiving node. The D2 ERROR INDICATION message shall contain the *Cause* IE - -- In case of Abstract Syntax Error, the cause shall be set to “Abstract Syntax Error”. The *Transaction ID* IE shall indicate the message that triggered the Error scenario. -- In case of Logical Error in a response message of a Class 1 procedure, or failure to comprehend *Transaction ID* IE from a received message, the procedure shall be considered as unsuccessfully terminated or not terminated (e.g., transaction ID unknown in response message), and local error handling shall be initiated - -### 5.3.2 UE Management procedures - -#### 5.3.2.1 UE Addition - -The purpose of the UE Addition procedure, as shown in Figure 5.3.2.1-1, is to establish the D2 UE context in the sO-DU by adding one or more of its cells as SCells for the UEs mentioned in the UE ADDITION REQUEST message. The procedure uses UE-associated signalling. The pO-DU initiates the procedure by sending UE ADDITION REQUEST message to sO-DU if it is able to allocate PUCCH resources to receive the CSI information for new SCell. sO-DU responds back with UE ADDITION RESPONSE message with the information on success or failure of SCell(s) addition for the UE(s) mentioned in the message. - -![Sequence diagram showing UE Addition Procedure from pO-DU to sO-DU](e9d825d87c5f85c8dba0664eace96ef4_img.jpg) - -``` - -sequenceDiagram - participant pO-DU - participant sO-DU - Note left of pO-DU: - Note right of sO-DU: - pO-DU->>sO-DU: UE ADDITION REQUEST - sO-DU-->>pO-DU: UE ADDITION RESPONSE - -``` - -Sequence diagram showing UE Addition Procedure from pO-DU to sO-DU - -Figure 5.3.2.1-1: UE Addition Procedure - -If sO-DU accepts the request for at least one of candidate SCell(s) listed in *SCell To Be Added List* IE for the UE(s) present in *UE To Be Added Item* IE, it establishes the D2 UE context for the UE(s) and stores the *D2 UE ID* and *C-RNTI*. Association between a UE and D2 UE ID does not change unless D2 UE context is deleted. - -If the *DRX-Config* IE is contained in the UE ADDITION REQUEST message, the sO-DU shall use the provided value from the pO-DU. - -If the *MeasGapConfig* IE is contained in the UE ADDITION REQUEST message, the sO-DU shall use the provided value from the pO-DU. - -If the *servingCellMO* IE in *P O-DU to S O-DU SCell Information* IE is included in the UE ADDITION REQUEST message, the sO-DU shall configure *servingCellMO* for the indicated SCell accordingly. - -The *maxMIMO-LayersDL-PerDU* IE specifies the maximum number of DL MIMO layers that can be configured by the sO-DU across all the SCells for a given UE. If the *maxMIMO-LayersDL* IE in the *P O-DU to S O-DU SCell Information* is present, each SCell shall not configure the DL MIMO layers exceeding the value indicated by this IE. The cumulative number of configured DL MIMO layers across all SCells within the sO-DU shall not surpass the *maxMIMO-LayersDL-PerDU* IE value. In case of absence of *maxMIMO-LayersDL* IE in the *P O-DU to S O-DU SCell Information*, sO-DU can decide to configure DL MIMO layers in each of the SCells configured for the UE. The sO-DU shall report the total number of layers allocated for each SCell for the UE using the *maxMIMO-LayersUsedDL* IE in the *S O-DU to P O-DU SCell Information* while sending UE ADDITION RESPONSE message. - -NOTE: The pO-DU is responsible for ensuring that the configuration provided to the sO-DU for maximum MIMO layers for downlink is in accordance with the network specified UE configuration (such as band combination). - -sO-DU shall use *ReportConfigType* IE that contains the PUCCH allocation and CSI report slot configuration for the SCell, while forming the *CSI-ReportConfig* IE. *CSI-ReportConfig* IE shall be sent back to pO-DU which is finally sent to UE in RRC Reconfiguration message. - -sO-DU shall respond back for each D2 UE ID with corresponding entry in *UE Added List* or *UE Failed To Add List* IE in UE ADDITION RESPONSE message. - -The sO-DU shall report to the pO-DU, in the UE ADDITION RESPONSE message, the result of all the successful UE addition in the following way: - -- D2 UE ID shall be added in *UE Added List* IE identified by *D2 UE ID* and *C-RNTI* IEs. -- A list of SCells for the UE that is successfully added shall be included in *SCell Added List* IE. -- SCell configuration as defined in 3GPP TS38.331 [5] for each of the successfully added SCell shall be included in *SCellConfig* IE in *S O-DU to P O-DU SCell Information*. -- If periodic CSI reporting is configured on the SCell, the expected periodic CSI report size for each of the successful added SCell is included in *PeriodicCsiReportSize* IE in *S O-DU to P O-DU SCell Information* IE. -- A list of LCs for each SCell that is successfully added shall be included in *LC Added List* IE. -- A list of LCs which failed to be added shall be included in the *LC Failed to Add List* IE. Cause shall be added to convey the failure reason. -- SCell(s) that failed to be added in sO-DU, shall be included in the *SCells Failed to Add List* IE. Cause shall be added to convey the failure reason. D2-u procedure shall not take place for these SCell(s). - -If none of the SCell for a UE(s) is added by the sO-DU, the sO-DU shall reply with the UE ADDITION RESPONSE message listing the failed UE(s) in the *UE Failed To Add List* IE for each corresponding D2 UE ID. Cause IE shall indicate the cause of failure for UE addition procedure. - -#### 5.3.2.2 UE Modification Update - -The purpose of the UE modification update procedure is to modify the established D2 UE Context(s) in sO-DU. As shown in figure 5.3.2.2-1, pO-DU may initiate this procedure to add a new SCell(s) if it is able to allocate PUCCH resources to receive the CSI information for new SCell or delete or modify configuration of an already added SCell(s) for the UE. Configuration update for multiple UEs, each one identified by D2 UE ID, may be performed in single UE MODIFICATION REQUEST message. - -Upon reception of the UE MODIFICATION REQUEST message, the sO-DU shall perform the modifications for each UE(s), and reports the outcome in the UE MODIFICATION RESPONSE message as shown in Figure 5.3.2.2-1. - -![Sequence diagram showing the UE Modification Update procedure. A PCell O-DU sends a UE MODIFICATION REQUEST message to an SCell O-DU. The SCell O-DU responds with a UE MODIFICATION RESPONSE message back to the PCell O-DU.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) - -``` - -sequenceDiagram - participant PCell O-DU - participant SCell O-DU - Note left of PCell O-DU: - PCell O-DU->>SCell O-DU: UE MODIFICATION REQUEST - SCell O-DU-->>PCell O-DU: UE MODIFICATION RESPONSE - Note right of SCell O-DU: - -``` - -Sequence diagram showing the UE Modification Update procedure. A PCell O-DU sends a UE MODIFICATION REQUEST message to an SCell O-DU. The SCell O-DU responds with a UE MODIFICATION RESPONSE message back to the PCell O-DU. - -Figure 5.3.2.2-1: UE Modification Update procedure - -The sO-DU shall consider *UE To Be Modified List* IE as a list of candidate UE(s) identified by *D2 UE ID* IE that are requested for modification in the UE MODIFICATION REQUEST message. sO-DU shall store the received *C-RNTI* in *D2 UE Context* of each UE. - -If the *SCell To AddMod Item* IE is contained in the UE MODIFICATION REQUEST message, the sO-DU shall consider *SCell To Be AddMod Item* IE as a list of candidates SCell(s) to be added or modified for the UE. If the *servingCellMO* IE is included in the UE MODIFICATION REQUEST message, the sO-DU shall use it as needed for the indicated SCell. - -If the *UE-CapabilityRAT-ContainerList* IE is included in the UE MODIFICATION REQUEST message, the sO-DU shall take this information into account for UE specific configurations. - -The *maxMIMO-LayersDL-PerDU* IE specifies the maximum number of DL MIMO layers that can be configured by the sO-DU across all the SCells for a given UE. If the *maxMIMO-LayersDL* IE in the *P O-DU to S O-DU SCell Information* is present, each SCell shall not configure the DL MIMO layers exceeding the value indicated by this IE. The cumulative number of configured DL MIMO layers across all SCells within the sO-DU shall not surpass the *maxMIMO-LayersDL-PerDU* IE value. In case of absence of *maxMIMO-LayersDL* IE in the *P O-DU to S O-DU SCell Information*, sO-DU can decide to configure DL MIMO layers in each of the SCells configured for a UE. The sO-DU shall report the total number of layers allocated for each SCell for the UE using the *maxMIMO-LayersUsedDL* IE in the *S O-DU to P O-DU SCell Information* while sending UE MODIFICATION RESPONSE message. - -NOTE: The pO-DU is responsible for ensuring that the configuration provided to the sO-DU for maximum MIMO layers for downlink is in accordance with the specified UE configuration (such as band combination). - -sO-DU shall use *ReportConfigType* IE that contains the PUCCH allocation, CSI report slot configuration for the SCell, while forming the *CSI-ReportConfig* IE. *CSI-ReportConfig* IE shall be sent back to pO-DU which is finally sent to UE in the RRC Reconfiguration message. - -If the *DRX-Config* IE is contained in the UE MODIFICATION REQUEST message, the sO-DU shall use the provided value from the pO-DU. - -If the *LC To Be AddMod Item* IE is contained in the UE MODIFICATION REQUEST message, the sO-DU shall add or update the QoS config and NSSAI information for each of the LCID. - -If the *LC To Be Delete Item* IE is contained in the UE MODIFICATION REQUEST message, the sO-DU shall release the LCs mentioned. No response shall be sent for these LCs. - -If the *SCells To Be Delete Item* IE is contained in the UE MODIFICATION REQUEST message, the sO-DU shall release the SCell(s) for the UE. No Response shall be sent for these SCells. sO-DU shall not handle any of D2-u messages that are received for the released SCell(s). - -The sO-DU shall report to the pO-DU, in the UE MODIFICATION RESPONSE message, the result of all the UEs that are requested for modification by the UE MODIFICATION REQUEST message in the following way: - -- The UE(s) identified by *D2 UE ID* IE that is(are) successfully modified shall be included in *UE Modified List* IE. Various IEs shall be filled as mentioned below: - - SCell(s) for each UE that is successfully added or modified shall be included in *SCell Updated List* IE. - -- SCell configuration as defined in 3GPP TS 38.331 [5] for each of the successfully added SCell shall be included in *SCellConfig* IE. - - If periodic CSI reporting is configured on the SCell, the expected periodic CSI report size for each of the successful added SCell shall be included in *PeriodicCsiReportSize* IE in *S O-DU to P O-DU SCell Information* IE. -- SCell(s) that failed to be added or modified, shall be included in the *SCells Failed to AddMod List* IE. *Cause* IE shall mention the cause of failure. SCell(s) that failed shall not be used for any D2-c or D2-u message exchange between pO-DU and sO-DU until it is successfully added. - - SCell(s) present in *SCell To Be Deleted List* IE shall not be included in the *SCell Failed To AddMod List*. - - LC(s) that is(are) successfully added or modified shall be included in *LC Updated List* IE. - - LCs which failed to be added or modified shall be included in the *LC Failed to AddMod List* IE. *Cause* IE shall mention the cause of failure. - - LC(s) present in *LC To Be Deleted List* IE shall not be included in the *LC Failed to AddMod List*. -- sO-DU shall include the *D2 UE ID* and *C-RNTI* IE for the UE(s) in *UE Failed To Mod List* IE, for which none of the modification is accepted that was provided in the UE MODIFICATION REQUEST message. - -#### 5.3.2.3 UE Modification Indication - -The purpose of the UE Modification Indication procedure is to notify the pO-DU that sO-DU is unable to handle certain resources (e.g., SCell(s), Logical Channel(s), or UE context) for a UE(s), and hence these resources shall not be used for any further D2-u communication until reconfigured again. - -As shown in Figure 5.3.2.3-1, the sO-DU initiates the procedure by sending UE MODIFICATION INDICATION message to pO-DU. - -![Diagram of UE Modification Indication procedure. It shows two vertical lifelines: PCell O-DU on the left and SCell O-DU on the right. A horizontal arrow labeled 'UE MODIFICATION INDICATION' points from the SCell O-DU lifeline to the PCell O-DU lifeline. Both lifelines end in a solid black rectangle at the bottom.](41a438d7e4adc17c3a4005e7c9500091_img.jpg) - -Diagram of UE Modification Indication procedure. It shows two vertical lifelines: PCell O-DU on the left and SCell O-DU on the right. A horizontal arrow labeled 'UE MODIFICATION INDICATION' points from the SCell O-DU lifeline to the PCell O-DU lifeline. Both lifelines end in a solid black rectangle at the bottom. - -Figure 5.3.2.3-1: UE Modification Indication procedure - -If *UE To Be Updated List* IE is contained in the message, the pO-DU shall consider this list as a candidate UE(s) identified by *D2 UE ID* IE, that are notified for modification in the UE MODIFICATION INDICATION message. - -- If the *SCell To Be Released Item* IE is contained in the UE MODIFICATION INDICATION message, the pO-DU shall remove the SCell(s) from the D2 UE Context. pO-DU may initiate SCell Deactivation procedure towards UE. Later if pO-DU decides to add the same SCell again, it may trigger UE Addition or Modification Procedure for adding the SCell. *Cause* IE shall indicate the reason of release. -- If the *LCs To Be Released List* IE is contained in the UE MODIFICATION INDICATION message, the pO-DU shall remove the LC information for the UE from D2 UE Context. These LCs shall not be considered while scheduling data on the sO-DU. *Cause* IE shall indicate the reason of release. - -If *UE To Be Released List* IE is contained in the message, pO-DU shall remove the D2 UE context for the UE(s) identified by *D2 UE ID* IE. No further communication for the UE(s) shall take place with sO-DU until the UE is added again by the UE Addition procedure. - -#### 5.3.2.4 UE Reconfiguration Complete - -The purpose of the UE Reconfiguration Complete procedure is to notify the sO-DU that the UE has successfully completed an RRC Reconfiguration procedure where SCells that were configured in sO-DU are updated. - -As shown in Figure 5.3.2.4-1, pO-DU shall initiate the UE RECONFIGURATION COMPLETE message to sO-DU. *UEReconfigList* IE shall include the *D2 UE ID* and *C-RNTI* of UE(s) for which pO-DU has received RRC Reconfiguration complete from UE. - -![Sequence diagram for UE Reconfiguration Complete procedure. It shows two vertical lifelines: PCell O-DU and SCell O-DU. A horizontal arrow labeled 'UE RECONFIGURATION COMPLETE' points from the PCell O-DU lifeline to the SCell O-DU lifeline. Both lifelines have a solid black bar at the bottom.](33a8f3f01dfa8bce75d23017855a13c5_img.jpg) - -Sequence diagram for UE Reconfiguration Complete procedure. It shows two vertical lifelines: PCell O-DU and SCell O-DU. A horizontal arrow labeled 'UE RECONFIGURATION COMPLETE' points from the PCell O-DU lifeline to the SCell O-DU lifeline. Both lifelines have a solid black bar at the bottom. - -Figure 5.3.2.4-1: UE Reconfiguration Complete procedure - -#### 5.3.2.5 UE Deletion - -The purpose of the UE Deletion procedure is to delete the D2 UE Context. This procedure erases any existing UE related information in sO-DU. - -As shown in Figure 5.3.2.5-1, the pO-DU initiates the procedure by sending UE DELETION REQUEST to sO-DU. - -![Sequence diagram for UE Deletion procedure. It shows two vertical lifelines: PCell O-DU and SCell O-DU. A horizontal arrow labeled 'UE DELETION REQUEST' points from the PCell O-DU lifeline to the SCell O-DU lifeline. A return arrow labeled 'UE DELETION RESPONSE' points from the SCell O-DU lifeline back to the PCell O-DU lifeline. Both lifelines have a solid black bar at the bottom.](90ee16ccc0ad16aeca48087797d7b07f_img.jpg) - -Sequence diagram for UE Deletion procedure. It shows two vertical lifelines: PCell O-DU and SCell O-DU. A horizontal arrow labeled 'UE DELETION REQUEST' points from the PCell O-DU lifeline to the SCell O-DU lifeline. A return arrow labeled 'UE DELETION RESPONSE' points from the SCell O-DU lifeline back to the PCell O-DU lifeline. Both lifelines have a solid black bar at the bottom. - -Figure 5.3.2.5-1: UE Deletion procedure - -The sO-DU shall consider the UE(s) identified by *D2 UE ID* IE included in *UE To Be Deleted List* IE to delete the D2 UE context. sO-DU sends UE DELETION RESPONSE to pO-DU. Any ongoing D2-u procedure will be deleted for the UE and no new procedure will take place until UE is added again. - -## 5.4 Elements of D2CP Communication - -### 5.4.1 General - -Subclauses 5.4.2 and 5.4.3 present the D2CP message and IE definitions in tabular format. The corresponding ASN.1 definition is presented in subclause 5.4.4. In case there is contradiction between the tabular format and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional IEs, where the tabular format shall take precedence. - -The messages have been defined in accordance to the guidelines specified in TR 25.921 [8]. - -When specifying IEs which are to be represented by bitstrings, if not otherwise specifically stated in the semantics description of the concerned IE or elsewhere, the following principle applies with regards to the ordering of bits: - -- The first bit (leftmost bit) contains the most significant bit (MSB); -- The last bit (rightmost bit) contains the least significant bit (LSB); -- When importing bitstrings from other specifications, the first bit of the bitstring contains the first bit of the concerned information; - -The following attributes are used for the tabular description of the messages and information elements: Presence, Range Criticality and Assigned Criticality. Their definition and use can be found in TS 38.413 [3]. - -### 5.4.2 Message Functional Definition and Content - -#### 5.4.2.1 Interface management functions - -##### 5.4.2.1.1 D2 SETUP REQUEST - -This message is sent by the O-DU1 to transfer information associated to a D2-c connection. - -Direction: O-DU1 → O-DU2 - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | -|---------------------------|----------|-------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------|-------------|----------------------| -| Message Type | M | | 5.4.3.1 | | YES | reject | -| Transaction ID | M | | 5.4.3.2 | | YES | reject | -| Source O-DU ID | M | | 5.4.3.4 | | YES | reject | -| Target O-DU ID | M | | 5.4.3.4 | | YES | reject | -| Served Cell List | M | | | List of SCells configured in the O-DU for inter O-DU CA | YES | reject | -| >Served Cell Item | | 1 .. | | | | | -| >>Served Cell Information | M | | | This IE contains cell configuration information of a cell in the O-DU as defined in 38.473 [6] section 9.3.1.10 | - | - | -| >>CA Type | M | | 5.4.3.29 | | YES | reject | -| >>Start CRNTI | O | | 5.4.3.6 | This IE indicates the Start of C-RNTI that will be assigned to the UEs for which PCell is configured on this O-DU | | | -| >>End CRNTI | O | | 5.4.3.6 | This IE indicates the end of C-RNTI that will be assigned to the UEs for which PCell is configured on this O-DU. | | | -| D2U Info List | M | | | | YES | reject | -| >D2U Info Item | | 1 .. | | | | | -| >>D2U UDP Info List | M | | | List indicating the IP address and UDP port number for D2-u message exchange | YES | reject | -| >>>D2U UDP Info Item | | 1 .. | | | | | - -| | | | | | | | -|----------------------|---|-----------------------|--------------------------------|----------------------------------------------------------------------------------------------|-----|--------| -| >>>>IP Address | M | | BIT STRING (SIZE(1..160, ...)) | The IPv4 or IPv6 address of the O-DU1 that shall be used for D2-u communication with O-DU2.. | | | -| >>>>UDP port number | M | | BIT STRING (SIZE(16)) | The UDP port number of O-DU1 that shall be used for D2-u communication with O-DU2. | | | -| >>D2U PV List | M | | | | YES | reject | -| >>>D2U PV Item | | 1 .. | | | | | -| >>>>Protocol Version | M | | 5.4.3.13 | | | | -| >>T_ClearTB | M | | 5.4.3.31 | | YES | reject | - -##### 5.4.2.1.2 D2 SETUP RESPONSE - -This message is sent by the O-DU2 to transfer information associated to a D2-C connection. - -Direction: O-DU2 → O-DU1 - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | -|---------------------------|----------|-------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------|-------------|----------------------| -| Message Type | M | | 5.4.3.1 | | YES | reject | -| Transaction ID | M | | 5.4.3.2 | | YES | reject | -| Source O-DU ID | M | | 5.4.3.4 | | YES | reject | -| Target O-DU ID | M | | 5.4.3.4 | | YES | reject | -| Served Cell List | M | | | List of SCells configured in the O-DU for inter O-DU CA | YES | reject | -| >Served Cell Item | | 1 .. | | | | | -| >>Served Cell Information | M | | | This IE contains cell configuration information of a cell in the O-DU as defined in 38.473 [6] section 9.3.1.10 | - | - | -| >>CA Type | M | | 5.4.3.29 | | YES | reject | -| >>Start CRNTI | O | | 5.4.3.6 | This IE indicates the Start of C-RNTI that will be assigned to the UEs for which PCell is configured on this O-DU | | | -| >>End CRNTI | O | | 5.4.3.6 | This IE indicates the end of C-RNTI that will be assigned to the UEs for which PCell is configured on this O-DU. | | | -| D2U Info List | M | | | | YES | reject | -| >D2U Info Item | | 1 .. | | | | | -| >>D2U UDP Info List | M | | | List indicating the IP address and UDP port number for D2-u message exchange | YES | reject | -| >>>D2U UDP Info Item | | 1 .. | | | | | - -| | | | | | | | -|----------------------|---|-----------------------|--------------------------------------------|---------------------------------------------------------------------------------------------|-----|--------| -| >>>>IP Address | M | | BIT STRING (SIZE(1..160, ...)) | The IPv4 or IPv6 address of the O-DU2 that shall be used for D2-U communication with O-DU1. | | | -| >>>>UDP port number | M | | BIT STRING (SIZE(16)) | The UDP port number of O-DU2 that shall be used for D2-U communication with O-DU1. | | | -| >>D2U PV List | M | | | | YES | reject | -| >>>D2U PV Item | | 1 .. | | | | | -| >>>>Protocol Version | M | | 5.4.3.13 | | | | -| >>T_ClearTB | M | | 5.4.3. 31 | | YES | reject | - -##### 5.4.2.1.3 D2 SETUP FAILURE - -This message is sent by the O-DU2 to indicate D2 Setup failure. - -Direction: O-DU2 → O-DU1 - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | -|----------------|----------|-------|--------------------------------------------|-----------------------|-------------|----------------------| -| Message Type | M | | 5.4.3.1 | | YES | reject | -| Transaction ID | M | | 5.4.3.2 | | YES | reject | -| Source O-DU ID | M | | 5.4.3.4 | | YES | reject | -| Target O-DU ID | M | | 5.4.3.4 | | YES | reject | -| Cause | M | | 5.4.3.3 | | YES | ignore | -| Time to wait | O | | 5.4.3. 30 | | YES | ignore | - -##### 5.4.2.1.4 D2 CONFIGURATION UPDATE - -This message is sent by the O-DU1 to transfer updated information for a D2-C interface connection. - -Direction: O-DU1 → O-DU2 - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | -|------------------------------|----------|------------------------------|-----------------------|-----------------------------------------------------------------------------------------------------------------|-------------|----------------------| -| Message Type | M | | 5.4.3.1 | | YES | reject | -| Transaction ID | M | | 5.4.3.2 | | YES | reject | -| Source O-DU ID | M | | 5.4.3.4 | | YES | reject | -| Target O-DU ID | M | | 5.4.3.4 | | YES | reject | -| Served Cell To Add List | | 0..1 | | List of cells configured in the O-DU | YES | reject | -| >Served Cells To Add Item | | 1..
| | | EACH | reject | -| >>Served Cell Information | M | | | This IE contains cell configuration information of a cell in the O-DU as defined in 38.473 [6] section 9.3.1.10 | - | - | -| >>CA Type | M | | 5.4.3.29 | | YES | reject | -| >>Start CRNTI | O | | 5.4.3.6 | Start of CRNTI used for this O-DU | | | -| >>End CRNTI | O | | 5.4.3.6 | End of CRNTI used for this O-DU | | | -| Served Cell To Modify List | | 0..1 | | List of cells configured in the O-DU | YES | reject | -| >Served Cells To Modify Item | | 1 .. <
| | | EACH | reject | -| >>Old NR CGI | M | | 5.4.3.7 | | | | -| >>Served Cell Information | M | | | This IE contains cell configuration information of a cell in the O-DU as defined in 38.473 [6] section 9.3.1.10 | | | -| >>CA Type | M | | 5.4.3.29 | | YES | reject | -| >>Start CRNTI | O | | 5.4.3.6 | Start of CRNTI used for this O-DU | | | -| >>End CRNTI | O | | 5.4.3.6 | End of CRNTI used for this O-DU | | | -| Served Cell To Delete List | | 0..1 | | Complete list of deleted cells served by O-DU | YES | reject | -| >Served Cells To Delete Item | | 1 .. <
| | | EACH | reject | -| >>Old NR CGI | M | | 5.4.3.7 | | | | - -##### 5.4.2.1.5 D2 CONFIGURATION UPDATE ACKNOWLEDGE - -This message is sent by the O-DU2 to transfer information associated to a D2-c interface connection. - -Direction: O-DU2 → O-DU1 - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | -|---------------------|----------|---------------------------|-----------------------|------------------------------------------------------------------------|-------------|----------------------| -| Message Type | M | | 5.4.3.1 | | YES | reject | -| Transaction ID | M | | 5.4.3.2 | | YES | reject | -| Source O-DU ID | M | | 5.4.3.4 | | YES | reject | -| Target O-DU ID | M | | 5.4.3.4 | | YES | reject | -| Updated Cell List | | 0..1 | | List of SCells configured in the O-DU for inter O-DU CA | YES | reject | -| >Updated Cells Item | | 1..
| | | EACH | reject | -| >>NR CGI | M | | 5.4.3.7 | | - | - | -| >>NR PCI | O | INTEGER
(0..1007) | | Physical Cell ID | YES | reject | -| >>Result | M | | 5.4.3.8 | Indicates if configuration update for the cell is successful or failed | YES | reject | - -##### 5.4.2.1.6 D2 CONFIGURATION UPDATE FAILURE - -This message is sent by the O-DU2 to indicate D2 Configuration Update failure. - -Direction: O-DU2 → O-DU1 - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | -|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| -| Message Type | M | | 5.4.3.1 | | YES | reject | -| Transaction ID | M | | 5.4.3.2 | | YES | reject | -| Source O-DU ID | M | | 5.4.3.4 | | YES | reject | -| Target O-DU ID | M | | 5.4.3.4 | | YES | reject | -| Cause | M | | 5.4.3.3 | | YES | ignore | -| Time to wait | O | | 5.4.3.30 | | YES | ignore | - -##### 5.4.2.1.7 D2 RELEASE REQUEST - -This message is sent by the O-DU1 to the O-DU2. - -Direction: O-DU1 → O-DU2 - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | -|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| -| Message Type | M | | 5.4.3.1 | | YES | Reject | -| Transaction ID | M | | 5.4.3.2 | | YES | Reject | -| Source O-DU ID | M | | 5.4.3.4 | | YES | Reject | -| Target O-DU ID | M | | 5.4.3.4 | | YES | Reject | -| cause | M | | 5.4.3.3 | | YES | Ignore | - -##### 5.4.2.1.8 D2 RELEASE RESPONSE - -This message is sent by the O-DU2 to the O-DU1. - -Direction: O-DU2 → O-DU1 - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | Criticality | Assigned Criticality | -|----------------|----------|-------|-----------------------|-----------------------|-------------|----------------------| -| Message Type | M | | 5.4.3.1 | | YES | Reject | -| Transaction ID | M | | 5.4.3.2 | | YES | Reject | -| Source O-DU ID | M | | 5.4.3.4 | | YES | Reject | -| Target O-DU ID | M | | 5.4.3.4 | | YES | Reject | - -##### 5.4.2.1.9 D2 ERROR INDICATION - -This message is sent by both the O-DUs and is used to indicate that some error has been detected in the node. - -Direction: O-DU1 → O-DU2 - -| IE/Group Name | Presence | Range | IE Type and reference | Semantics Description | Assigned Criticality | -|----------------|----------|-------|-----------------------|---------------------------------------------------------|----------------------| -| Message Type | M | | 5.4.3.1 | | reject | -| Transaction ID | M | | 5.4.3.2 | | Reject | -| Source O-DU ID | M | | 5.4.3.4 | | Reject | -| Target O-DU ID | M | | 5.4.3.4 | | Reject | -| Cause | M | | | Indicates the cause that triggered the Error Indication | Reject | - -#### 5.4.2.2 UE management functions - -##### 5.4.2.2.1 UE ADDITION REQUEST - -This message is sent from pO-DU to add the SCell(s) from sO-DU for the listed UEs. - -Direction: pO-DU → sO-DU. - -| IE/Group Name | Presence | Range | IE Type and reference | Semantics Description | Assigned Criticality | -|----------------|----------|-------|-----------------------|--------------------------------------------------------------------|----------------------| -| Message Type | M | | 5.4.3.1 | | reject | -| Transaction ID | M | | 5.4.3.2 | | Reject | -| Source O-DU ID | M | | 5.4.3.4 | This is same as gNB-DU-ID as defined in 38.473 [6] clause 9.3.1.9. | Reject | -| Target O-DU ID | M | | 5.4.3.4 | This is same as gNB-DU-ID as defined in 38.473 [6] clause 9.3.1.9. | Reject | - -| | | | | | | -|-----------------------------------------|---|-------------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| -| UE To Be Added List | | 1 | | List of UEs for which request is received | Reject | -| > UE To Be Added Item | | 1 .. | | | ignore | -| >> C-RNTI | M | | 5.4.3.6 | | | -| >> D2 UE ID | M | | 5.4.3.5 | | | -| >> maxMIMO-LayersDL-PerDU | M | | INTEGER (1..32) | indicates the maximum number of DL MIMO layers that can be configured for a UE in the sO-DU. If there are multiple SCells configured for the UE in the sO-DU, total layers across all the SCells shall not exceed this value. | ignore | -| >> UE-CapabilityRATContainerList | M | | OCTET STRING | This IE consists of the UE-CapabilityRATContainerList, as defined in TS 38.331 [5]. | Reject | -| >> SCells To Be Added List | | 1 | | List of SCells that has to be added. | Reject | -| >>> SCell To Be Added Item | | 1 .. | | | ignore | -| >>>> P O-DU to S O-DU SCell Information | M | | 5.4.3.15 | | | -| >>MeasGapConfig | O | | OCTET STRING | MeasGapConfig as defined in 3GPP TS 38.331 [5]. | ignore | -| >>DRX-Config | O | | OCTET STRING | DRX-Config, as defined in 3GPP TS 38.331 [5]. | ignore | -| >>LC To Be Added List | | 1 | | List of LCs which can be added for SCell | reject | -| >>>LC To Be Added Item | | 1 .. | | | ignore | -| >>>>LCID | M | | 5.4.3.10 | LC Identifier as defined in 3GPP TS 38.473 [6] clause 9.3.1.35 | | -| >>>> QoS Information | M | | 5.4.3.22 | | | -| >>>>S-NSSAI | M | | 5.3.4.21 | Corresponds to S-NSSAI as defined in 3GPP TS 38.473 [6] clause 9.3.1.38 | | - -##### 5.4.2.2.2 UE ADDITION RESPONSE - -This message is sent from sO-DU to pO-DU as a response to UE ADDITION REQUEST message. This message is sent for both success and failure scenario. - -Direction: sO-DU → pO-DU - -| IE/Group Name | Presence | Range | IE Type and reference | Semantics Description | Assigned Criticality | -|-----------------------------------------|----------|---------------------------|-----------------------|----------------------------------------------------------------------------|----------------------| -| Message Type | M | | 5.4.3.1 | | reject | -| Transaction ID | M | | 5.4.3.2 | | Reject | -| Source O-DU ID | M | | 5.4.3.4 | This is same as gNB-DU-ID as defined in 3GPP TS 38.473 [6] clause 9.3.1.9. | Reject | -| Target O-DU ID | M | | 5.4.3.4 | This is same as gNB-DU-ID as defined in 3GPP TS 38.473 [6] clause 9.3.1.9. | Reject | -| UE Added List | | 0..1 | | List of UEs that are added successfully | ignore | -| > UE Added Item | | 1 .. < maxInterDUUEs > | | | ignore | -| >> C-RNTI | M | | 5.4.3.6 | | | -| >> D2 UE ID | M | | 5.4.3.5 | | | -| >> SCells Added List | | 0..1 | | List of SCells that is successfully added. | Reject | -| >>> SCell Added Item | | 1 .. < maxInterDUSCells > | | | ignore | -| >>>> S O-DU to P O-DU SCell Information | M | | 5.4.3.17 | | | -| >>LC Added List | | LCList | 5.4.3.11 | List of LCs which are added successfully | reject | -| >>LC Failed To Add List | | LC Release List | 5.4.3.12 | | reject | -| >>SCell Failed To Add List | | SCell Release List | 5.4.3.16 | | reject | -| UE Failed To Add List | | UE Release List | 5.4.3.19 | | ignore | - -##### 5.4.2.2.3 UE DELETION REQUEST - -pO-DU initiates the message to delete the D2 UE context from sO-DU for the listed UEs. - -Direction: pO-DU → sO-DU - -| IE/Group Name | Presence | Range | IE Type and reference | Semantics Description | Assigned Criticality | -|-----------------------|----------|---------|-----------------------|--------------------------------------------------------------------|----------------------| -| Message Type | M | | 5.4.3.1 | | reject | -| Transaction ID | M | | 5.4.3.2 | | Reject | -| Source O-DU ID | M | | 5.4.3.4 | This is same as gNB-DU-ID as defined in 38.473 [6] clause 9.3.1.9. | Reject | -| Target O-DU ID | M | | 5.4.3.4 | This is same as gNB-DU-ID as defined in 38.473 [6] clause 9.3.1.9. | Reject | -| UE To Be Deleted List | M | UE List | 5.4.3.18 | List of UEs for which request is received | Reject | - -##### 5.4.2.2.4 UE DELETION RESPONSE - -sO-DU triggers UE DELETION RESPONSE message to respond back to UE DELETION REQUEST. - -Direction: sO-DU → pO-DU - -| IE/Group Name | Presence | Range | IE Type and reference | Semantics Description | Assigned Criticality | -|----------------|----------|-------|-----------------------|--------------------------------------------------------------------|----------------------| -| Message Type | M | | 5.4.3.1 | | reject | -| Transaction ID | M | | 5.4.3.2 | | Reject | -| Source O-DU ID | M | | 5.4.3.4 | This is same as gNB-DU-ID as defined in 38.473 [6] clause 9.3.1.9. | Reject | -| Target O-DU ID | M | | 5.4.3.4 | This is same as gNB-DU-ID as defined in 38.473 [6] clause 9.3.1.9. | Reject | - -##### 5.4.2.2.5 UE MODIFICATION REQUEST - -This message is sent from pO-DU to add a new SCell or modify or delete the existing SCell from sO-DU. - -Direction: pO-DU → sO-DU. - -| IE/Group Name | Presence | Range | IE Type and reference | Semantics Description | Assigned Criticality | -|---------------|----------|-------|-----------------------|-----------------------|----------------------| -|---------------|----------|-------|-----------------------|-----------------------|----------------------| - -| | | | | | | -|-----------------------------------------|---|---------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------| -| Message Type | M | | 5.4.3.1 | | reject | -| Transaction ID | M | | 5.4.3.2 | | Reject | -| Source O-DU ID | M | | 5.4.3.4 | This is same as gNB-DU-ID as defined in 38.473 [6] clause 9.3.1.9. | Reject | -| Target O-DU ID | M | | 5.4.3.4 | This is same as gNB-DU-ID as defined in 38.473 [6] clause 9.3.1.9. | Reject | -| UE To Be Modified List | | 1 | | List of UEs for which request is received | Reject | -| > UE To Be Modified Item | | 1 .. < maxInterDUUEs > | | | ignore | -| >> C-RNTI | M | | 5.4.3.6 | | | -| >> D2 UE ID | M | | 5.4.3.5 | | | -| >> maxMIMO-LayersDL-PerDU | M | | 5.4.3.28 | This IE indicates the maxMIMO-Layers that can be supported for a UE in the sO-DU. If there are multiple SCells configured for the UE, total layers across all the SCells shall not exceed this value | reject | -| >> UE-CapabilityRATContainerList | O | | OCTET STRING | Same as defined in 38.331 [5] | ignore | -| >> SCells To AddMod List | | 0..1 | | List of SCells that has to be added. | Reject | -| >>> SCell To AddMod Item | | 1 .. < maxInterDUSCells > | | | ignore | -| >>>> P O-DU to S O-DU SCell Information | M | | 5.4.3.14 | | | -| >>MeasGapConfig | O | | OCTET STRING | Corresponds to MeasGapConfig IE as defined in 38.331 [5] | ignore | -| >>DRX-Config | O | | OCTET STRING | Corresponds to DRX-Config IE as defined in 38.331 [5] | ignore | -| >>LC To Be AddMod List | | 0..1 | | List of LCs which can be added for SCell | reject | -| >>>LC To Be AddMod Item | | 1 .. < maxLCs > | | | ignore | -| >>>>LCID | M | | 5.4.3.10 | LC Identifier | | -| >>>> QoS Information | M | | 5.4.3.21 | | | - -| | | | | | | -|----------------------------|---|------------|----------|---------------------------------------------|--------| -| >>>>S-NSSAI | M | | 5.3.4.20 | | | -| >>LC To Be Deleted List | | LC List | 5.4.3.11 | List of LCs which need to be deleted for UE | reject | -| >>SCell To Be Deleted List | | SCell List | 5.4.3.15 | List of SCells which need to be released. | reject | - -##### 5.4.2.2.6 UE MODIFICATION RESPONSE - -This message is sent from sO-DU to pO-DU as a response to UE MODIFICATION REQUEST message. This message contains all the UEs, SCells and LCs that are successfully modified. List of failed UEs, SCells , LCs are also included in the message - -Direction: sO-DU → pO-DU. - -| IE/Group Name | Presence | Range | IE Type and reference | Semantics Description | Assigned Criticality | -|-----------------------------------------|----------|-------------------------|--------------------------|--------------------------------------------------------------------|----------------------| -| Message Type | M | | 5.4.3.1 | | reject | -| Transaction ID | M | | 5.4.3.2 | | Reject | -| Source O-DU ID | M | | 5.4.3.4 | This is same as gNB-DU-ID as defined in 38.473 [6] clause 9.3.1.9. | Reject | -| Target O-DU ID | M | | 5.4.3.4 | This is same as gNB-DU-ID as defined in 38.473 [6] clause 9.3.1.9. | Reject | -| UE Modified List | | 0..1 | | List of modified UEs | ignore | -| > UE Modified Item | | 1 .. | | | | -| >> C-RNTI | M | | 5.4.3.6 | | | -| >> D2 UE ID | M | | 5.4.3.5 | | | -| >> SCells Updated List | | 0..1 | | List of modified SCells. | Reject | -| >>> SCell Updated Item | | 1 .. | | | ignore | -| >>>> S O-DU to P O-DU SCell Information | M | | 5.4.3.17 | | | -| >>LC Updated List | | 0..1 | LCList 5.4.3.11 | List of modified LCs. | reject | -| >>LC Failed To AddMod List | | 0..1 | LC Release List 5.4.3.12 | List of LCs which failed to be modified. | reject | - -| | | | | | | -|-------------------------------|--|------|-----------------------------|--------------------------------------------|--------| -| >>SCell Failed To AddMod List | | 0..1 | SCell Release List 5.4.3.16 | List of SCells which failed to be modified | reject | -| UE Failed To Mod List | | 0..1 | UE Release List 5.4.3.19 | List of UE failed to be Modified. | ignore | - -##### 5.4.2.2.7 UE RECONFIGURATION COMPLETE - -pO-DU initiates this message towards SCell O\_DU to inform the reception of RRC Reconfiguration Complete message from UE for SCell addition. - -Direction: pO-DU → sO-DU - -| IE/Group Name | Presence | Range | IE Type and reference | Semantics Description | Assigned Criticality | -|------------------|----------|-------|---------------------------|--------------------------------------------------------------------|----------------------| -| Message Type | M | | 5.4.3.1 | | reject | -| Transaction ID | M | | 5.4.3.2 | | Reject | -| Source O-DU ID | M | | 5.4.3.4 | This is same as gNB-DU-ID as defined in 38.473 [6] clause 9.3.1.9. | Reject | -| Target O-DU ID | M | | 5.4.3.4 | This is same as gNB-DU-ID as defined in 38.473 [6] clause 9.3.1.9. | Reject | -| UE Reconfig List | M | | UE Reconfig List 5.4.3.27 | List of UEs for which reconfiguration complete message is received | Reject | - -##### 5.4.2.2.8 UE MODIFICATION INDICATION - -sO-DU initiates this message to inform pO-DU about release of some of the SCells or LCs or UEs between a pair of O-DUs. - -Direction: sO-DU → pO-DU - -| IE/Group Name | Presence | Range | IE Type and reference | Semantics Description | Assigned Criticality | -|-----------------------|----------|-------|-----------------------|--------------------------------------------------------------------|----------------------| -| Message Type | M | | 5.4.3.1 | | reject | -| Transaction ID | M | | 5.4.3.2 | | Reject | -| Source O-DU ID | M | | 5.4.3.4 | This is same as gNB-DU-ID as defined in 38.473 [6] clause 9.3.1.9. | Reject | -| Target O-DU ID | M | | 5.4.3.4 | This is same as gNB-DU-ID as defined in 38.473 [6] clause 9.3.1.9. | Reject | -| UE To Be Updated List | | 0..1 | | List of UEs for which request is received | Reject | - -| | | | | | | -|------------------------------|---|-----------------------|-----------------------------|------------------------------------|--------| -| > UE To Be Updated Item | | 1 .. < maxInterDUUEs> | | | ignore | -| >> C-RNTI | M | | 5.4.3.6 | | | -| >> D2 UE ID | M | | 5.4.3.5 | | | -| >>SCells To Be Released List | | 0..1 | SCell Release List 5.4.3.16 | List of SCells which are released. | ignore | -| >>LC To Be Released List | | 0..1 | LC Release List 5.4.3.12 | List of LCs which are released | ignore | -| UE To Be Released List | | 0..1 | UE Release List 5.4.3.19 | List of UEs that are released | ignore | - -### 5.4.3 Information Element Definitions - -#### 5.4.3.1 Message Type - -The *Message Type* IE uniquely identifies the message being sent. It is mandatory for all messages. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|-------|----------------------------------------------------------------------------|-----------------------| -| Message Type | | | | | -| >Procedure Code | M | | INTEGER (0..255) | | -| >Type of Message | M | | CHOICE (Initiating Message, Successful Outcome, Unsuccessful Outcome, ...) | | - -#### 5.4.3.2 Transaction ID - -The *Transaction ID* IE uniquely identifies a procedure among all ongoing parallel procedures of the same type initiated by the same protocol peer - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|----------------|----------|-------|-----------------------|-----------------------| -| Transaction ID | M | | INTEGER (0..255, ...) | | - -#### 5.4.3.3 Cause - -The purpose of the *Cause* IE is to indicate the reason for a particular event for the D2 protocol. - -| IE/Group Name | Presence | Range | IE Type and Reference | Semantics Description | -|---------------|----------|-------|-----------------------------------------------------------------------------|-----------------------| -| Cause | M | | ENUMERATED (Unspecified, SCell Down, UE Not Allowed, Cell Overload ... etc) | | - -| Protocol cause | Meaning | -|-----------------------------------------------------|----------------------------------------------------------------------------------------------------------------------| -| Abstract Syntax Error (Reject) | The received message included an abstract syntax error and the concerning criticality indicated “reject”. | -| Abstract Syntax Error (Ignore And Notify) | The received message included an abstract syntax error and the concerning criticality indicated “ignore and notify”. | -| Message Not Compatible With Receiver State | The received message was not compatible with the receiver state. | -| Semantic Error | The received message included a semantic error. | -| Abstract Syntax Error (Falsely Constructed Message) | The received message contained IEs or IE groups in wrong order or with too many occurrences. | -| Unspecified | Sent when none of the above cause values applies but still the cause is Protocol related. | -| SCell Down | SCell is down in DU | -| UE Not Allowed | Admission control failed in DU for some reason | -| Cell Overload | Cell is overloaded hence can not handle anymore UE. | -| CQI Failure | CQI is not received for configured duration by sO-DU hence releasing the SCell. | -| HARQ Failure | HARQ Feedback is not received for the configured duration | -| PV Not supported | Protocol version is not supported | -| UDP Port Invalid | UDP port information exchanged in UDP info is not supported. | -| Success | | - -#### 5.4.3.4 O-DU ID - -The *O-DU ID* IE uniquely identifies the O-DU at least within a O-CU. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|--------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| O-DU ID | M | | INTEGER
(0 .. 2 36 -1) | The O-DU ID is independently configured from cell identifiers, i.e. no connection between O-DU ID and cell identifiers. It is same as gNB-DU-ID as defined in 38.473 [6] clause 9.3.1.9 | - -#### 5.4.3.5 D2 UE ID - -The *D2 UE ID* IE uniquely identifies the UE association over the D2 interface between a pair of O-DU. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|--------------------------------------|-----------------------| -| D2 UE ID | M | | INTEGER
(0 .. 2 16 -1) | | - -#### 5.4.3.6 C-RNTI - -The *C-RNTI* IE is the UE identifier used between O-DU and UE. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|--------------------------------------|------------------------------------------| -| C-RNTI | M | | INTEGER
(0 .. 2 32 -1) | As defined in 38.473 [6] clause 9.3.1.32 | - -#### 5.4.3.7 NR CGI - -The NR Cell Global Identifier (*NR CGI* IE) is used to globally identify a cell. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|-------|--------------------------|-------------------------------------------------------| -| PLMN Identity | M | | 5.4.3.9 | Same as defined in 3GPP TS 38.473 [6] clause 9.3.1.14 | -| NR Cell Identity | M | | BIT STRING
(SIZE(36)) | | - -#### 5.4.3.8 Result - -This IE indicates the outcome of a procedure whether it is success or failure. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|---------------------------------------|-----------------------| -| Result | M | | ENUMERATED
(Success, Failure, ...) | | - -#### 5.4.3.9 PLMN Identity - -This information element indicates the PLMN Identity. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| PLMN Identity | M | | OCTET STRING (SIZE(3)) |
  • - digits 0 to 9, encoded 0000 to 1001,
  • - 1111 used as filler digit, two digits per octet,
  • - bits 4 to 1 of octet n encoding digit 2n-1
  • - bits 8 to 5 of octet n encoding digit 2n
  • -The PLMN identity consists of 3 digits from MCC followed by either
    • -a filler digit plus 2 digits from MNC (in case of 2 digit MNC) or
    • -3 digits from MNC (in case of a 3 digit MNC).
| - -#### 5.4.3.10 LCID - -This IE uniquely identifies a LC for a UE. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|---------------------------------------------------------------------------------| -| LCID | M | | INTEGER (1..32) | Corresponds to the LogicalChannelIdentity defined in 3GPP TS 38.331 [5]. | - -#### 5.4.3.11 LCList - -This IE indicates the list of LCs - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|---------------|-----------------------|---------------------------------------------------------------------------------| -| LC List Item IEs | | 1 .. | | | -| LCID | M | | 5.4.3.10 | Corresponds to the LogicalChannelIdentity defined in 3GPP TS 38.331 [5]. | - -#### 5.4.3.12 LC Release List - -This IE indicates the list of LCs that are failed to be added or modified. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|---------------|-----------------------|---------------------------------------------------------------------------------| -| LC List Item IEs | | 1 .. | | | -| >LCID | M | | 5.4.3.10 | Corresponds to the LogicalChannelIdentity defined in 3GPP TS 38.331 [5]. | -| >Cause | M | | 5.4.3.3 | | - -#### 5.4.3.13 Protocol Version - -This IE uniquely identifies the D2-u protocol version value. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|-------|-----------------------|-----------------------| -| Protocol Version | M | | INTEGER (0..16) | D2 Protocol version | - -#### 5.4.3.14 P O-DU to S O-DU SCell Information - -This IE contains the SCell information passed from pO-DU to sO-DU. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|-----------------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| SCell ID | M | INTEGER (0 .. 2 36 -1) | NR CGI 5.4.3.7 | The NR Cell Global Identifier (NR CGI) is used to globally identify a SCell. It is same as defined in 38.473 [6] clause 9.3.1.12. This shall contain the same value as received from O-CU. | -| SCellIndex | M | INTEGER (1..31) | | Index for the SCell as received from O-CU. This is same as defined in 38.331 [5] clause 6.3.2. | -| servingCellMO | O | INTEGER (1..64) | | as specified in 38.331 [5] clause 6.3.2 | -| maxMIMO-LayersDL | O | | 5.4.3.28 | | -| reportConfigType | M | OCTET STRING | | This IE shall be encoded as specified 3GPP TS 38.331 [5] clause 6.3.2.

In the present document only Periodic CSI reporting is supported. | - -#### 5.4.3.15 SCell List - -This IE indicates the list of SCells. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------|----------|-----------------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| SCell List Item IEs | | 1 .. < maxInterDUSCells > | | | -| >SCell ID | M | INTEGER (0 .. 2 36 -1) | NR CGI 5.4.3.7 | The NR Cell Global Identifier (NR CGI) is used to globally identify a SCell. It is same as defined in 38.473[6] clause 9.3.1.12. This shall contain the same value as received from O-CU. | -| >SCellIndex | M | INTEGER (1..31) | | Index for the SCell as received from O-CU. This is same as defined in 38.331 [5] clause 6.3.2. | - -#### 5.4.3.16 SCell Release List - -This IE indicates the list of SCells that needs to be released. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------|----------|-----------------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| SCell List Item IEs | | 1 .. < maxInterDUSCells > | | | -| >SCell ID | M | INTEGER (0 .. 2 36 -1) | NR CGI 5.4.3.7 | The NR Cell Global Identifier (NR CGI) is used to globally identify a SCell. It is same as defined in 38.473[6] clause 9.3.1.12. This shall contain the same value as received from O-CU. | -| >SCellIndex | M | INTEGER (1..31) | | Index for the SCell as received from O-CU. This is same as defined in 38.331 [5] clause 6.3.2. | -| >Cause | M | | 5.4.3.3 | | - -#### 5.4.3.17 S O-DU to P O-DU SCell Information - -This IE contains the SCell configuration information passed from sO-DU to pO-DU. This information will be sent to UE by pO-DU. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-----------------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| SCell ID | M | INTEGER (0 .. 2 36 -1) | NR CGI 5.4.3.7 | The NR Cell Global Identifier (NR CGI) is used to globally identify a SCell. It is same as defined in 38.473[6] clause 9.3.1.12. This shall contain the same value as received from O-CU. | - -| | | | | | -|-----------------------|---|-------------------------|--|------------------------------------------------------------------------------------------------| -| SCellIndex | M | INTEGER (1..31) | | Index for the SCell as received from O-CU. This is same as defined in 38.331 [5] clause 6.3.2. | -| SCellConfig | M | OCTET STRING | | Corresponds to SCellConfig, as defined in 3GPP TS 38.331 [5] clause 6.3.2. | -| maxMIMO-LayersUsedDL | M | 5.4.3.28 | | Indicates the maxMIMO-layers used for the UE in the SCell | -| CSI-ReportConfig | M | OCTET STRING | | Same as CSI-ReportConfig as defined in 38.331 | -| PeriodicCsiReportSize | O | INTEGER (1... 3000,...) | | The unit is: bits

This IE shall be present if CSI-Report Type is Periodic. | - -#### 5.4.3.18 UE List - -This IE indicates the list of UEs. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|------------------------|-----------------------|---------------------------------------------------------------------------------| -| UE List Item IEs | | 1 .. < maxInterDUUEs > | | | -| >C-RNTI | M | | C-RNTI 5.4.3.6 | Corresponds to the C-RNTI defined in 3GPP TS 38.473 [6] clause 9.3.1.32. | -| >D2 UE ID | M | | 5.4.3.5 | | - -#### 5.4.3.19 UE Release List - -This IE indicates the list of UEs that needs to be released or that are released. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|------------------------|-----------------------|---------------------------------------------------------------------------------| -| UE List Item IEs | | 1 .. < maxInterDUUEs > | | | -| >C-RNTI | M | | C-RNTI 5.4.3.6 | Corresponds to the C-RNTI defined in 3GPP TS 38.473 [6] clause 9.3.1.32. | -| >D2 UE ID | M | | 5.4.3.5 | | -| >Cause | M | | 5.4.3.3 | | - -#### 5.4.3.20 S-NSSAI - -This IE indicates the S-NSSAI as defined in TS 23.003 [15]. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|-----------------------| -|---------------|----------|-------|-----------------------|-----------------------| - -| | | | | | -|-----|---|------------------------|--|--| -| SST | M | OCTET STRING (SIZE(1)) | | | -| SD | O | OCTET STRING (SIZE(3)) | | | - -#### 5.4.3.21 QoS Information - -This IE uniquely defines the QoS parameter for each LC identified by LCID for a UE. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------------------------------|----------|-------|--------------------------------------------------|-----------------------------------------------------------------------| -| nr5QI | M | | INTEGER (0..255) | This IE contains the standardized 5QI as specified in TS 23.501 [16]. | -| NG-RAN Allocation and Retention Priority | M | | 5.3.4.28 | This IE is same as defined in 3GPP TS 38.473 [6] clause 9.3.1.48 | -| qoSPriorityLevel | M | | INTEGER (1..127) | For details see 3GPP TS 23.501 [16] | -| packetDelayBudget | M | | 5.4.3.24 | For details see 3GPP TS 23.501 [16] | -| packetErrorRate | M | | 5.4.3.23 | For details see 3GPP TS 23.501 [16] | -| delayCritical | M | | ENUMERATE D {delay-critical, non-delay-critical} | For details see 3GPP TS 23.501 [16] | -| GBR QoS Flow Information | O | | 5.3.4.26 | This is same as defined in 3GPP TS 38.473 [6] clause 9.3.1.46 | - -#### 5.4.3.22 Packet Error Rate - -This IE indicates the packet error rate for a LCID. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------|------------------------------------------------------------------------------------------| -| Scaler | M | | INTEGER (0..9, ...) | The packet error rate is expressed as Scalar x 10 -k where k is the Exponent. | -| Exponent | M | | INTEGER (0..9, ...) | | - -#### 5.4.3.23 Packet Delay Budget - -This IE indicates the packet delay budget for a LCID. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------|----------|-------|------------------------|------------------------------------------------------------------------------------------| -| Packet Delay Budget | M | | INTEGER (0..1023, ...) | Upper bound value for the delay that a packet may experience expressed in unit of 0.5ms. | - -#### 5.4.3.24 NG-RAN Allocation and Retention Priority - -This IE specifies the relative importance of a LCID for allocation and retention of NG-RAN resources. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------------------|----------|-------|---------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Priority Level | M | | INTEGER (0..15) | Desc.: This IE defines the relative importance of a resource request (see TS 23.501 [16]).
Usage: Values are ordered in decreasing order of priority, i.e., with 1 as the highest priority and 15 as the lowest priority. Further usage is defined in TS 23.501 [16]. | -| Pre-emption Capability | M | | ENUMERATED (shall not trigger pre-emption, may trigger pre-emption) | Desc.: This IE indicates the pre-emption capability of the request on other QoS flows (see TS 23.501 [16]).
Usage: The QoS flow shall not pre-empt other QoS flows or, the QoS flow may pre-empt other QoS flows. Note: The Pre-emption Capability indicator applies to the allocation of resources for a QoS flow and as such it provides the trigger to the pre-emption procedures/processes of the NG-RAN node. | -| Pre-emption Vulnerability | M | | ENUMERATED (not preemptable, pre-emptable) | Desc.: This IE indicates the vulnerability of the QoS flow to pre-emption of other QoS flows (see TS 23.501 [16]).
Usage: The QoS flow shall not be pre-empted by other QoS flows or the QoS flow may be pre-empted by other QoS flows. Note: The Pre-emption Vulnerability indicator applies for the entire duration of the QoS flow, unless modified and as such indicates whether the QoS flow is a target of the preemption procedures/processes of the NG-RAN node. | - -#### 5.4.3.25 GBR QoS Flow Information - -This IE indicates QoS parameters for a LCID that is configured for GBR QoS flow or GBR bearer for downlink and uplink. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|-----------------------------------|----------|-------|-----------------------|-------------------------------------------------------------------------------------------------------------------------| -| Maximum Flow Bit Rate Downlink | M | | BitRate
5.3.4.27 | Maximum Bit Rate in DL. Details in TS 23.501 [16]. | -| Maximum Flow Bit Rate Uplink | M | | BitRate
5.3.4.27 | Maximum Bit Rate in UL. Details in TS 23.501 [16]. | -| Guaranteed Flow Bit Rate Downlink | M | | BitRate
5.3.4.27 | Guaranteed Bit Rate (provided there is data to deliver) in DL. Details in TS 23.501 [16]. | -| Guaranteed Flow Bit Rate Uplink | M | | BitRate
5.3.4.27 | Guaranteed Bit Rate (provided there is data to deliver). Details in TS 23.501 [16]. | -| Maximum Packet Loss Rate Downlink | O | | INTEGER(0..1000) | Indicates the maximum rate for lost packets that can be tolerated in the downlink direction. Details in TS 23.501 [16]. | -| Maximum Packet Loss Rate Uplink | O | | INTEGER(0..1000) | Indicates the maximum rate for lost packets that can be tolerated in the uplink direction. Details in TS 23.501 [16]. | - -#### 5.4.3.26 BitRate - -This IE indicates the number of bits delivered by NG-RAN in UL or to NG-RAN in DL within a period of time, divided by the duration of the period. It is used, for example, to indicate the maximum or guaranteed bit rate for a LCID configured for a GBR QoS flow, or an aggregated maximum bit rate. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-----------------------------------------|-----------------------| -| Bit Rate | M | | INTEGER (0...
4,000,000,000,000,...) | The unit is: bit/s | - -#### 5.4.3.27 UE Reconfig List - -This IE indicates the list of UEs. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|------------------|----------|---------------------------|-----------------------|------------------------------------------------------------------------------------------------| -| UE List Item IEs | | 1 .. < maxInterDUUEs
> | | | -| >C-RNTI | M | | C-RNTI
5.4.3.6 | Corresponds to the
C-RNTI
defined in 3GPP TS
38.473 [6] clause 9.3.1.32. | -| >D2 UE ID | M | | 5.4.3.5 | | -| >SCell List | C | SCell List | 5.3.4.16 | This IE shall be present if
UE List is encoded in UE
RECONFIGURATION
COMPLETE message | - -#### 5.4.3.28 maxMIMO-Layers - -This IE indicates the maximum DL MIMO layers. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|----------------|----------|-------|-----------------------|--------------------------------------------------------------------------| -| maxMIMO-Layers | M | | INTEGER
( 1...16) | This is same as
maxMIMO-Layers as
defined in 3GPP TS
38.331 [5] | - -#### 5.4.3.29 CA Type - -This IE indicates CA type supported by the cell. In the present version of specification, only DL CA is supported. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|-------------------------|-----------------------| -| CA Type | M | | ENUMERATED
(DL, ...) | | - -#### 5.4.3.30 Time to wait - -This IE defines the minimum wait time for O-DU before retrying the message. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|------------------------------------------------------|--------------------------------------| -| Time to wait | O | | ENUMERATED
(1s, 2s, 5s, 10s, 20s, 60s, 120s, ...) | Indicates the time value in seconds. | - -#### 5.4.3.31 T\_ClearTB - -This IE is used in D2-U procedure for retransmission of the data. Once data is transmitted on SCell, T\_ClearTB timer shall be started. The timer is stopped either on successful HARQ feedback, or on reception of DL SCHEDULING REQUEST message containing the retransmission request for same HARQ PID for the same UE in same SCell. On expiry of T\_ClearTB, sO-DU shall Clear the HARQ process and make the HARQ PID available for next transmission with toggled NDI bit. - -| IE/Group Name | Presence | Range | IE type and reference | Semantics description | -|---------------|----------|-------|------------------------------------------------------|---------------------------------| -| T_ClearTB | M | | ENUMERATED
(ms1, ms2, ms5, ms10, ms20, ms60, ...) | Indicates the time value in ms. | - -### 5.4.4 Message and Information Element Abstract Syntax (with ASN.1) - -#### 5.4.4.1 General - -D2CP ASN.1 definition conforms to ITU-T Recommendation X.691 [12], ITU-T Recommendation X.680 [13] and ITUT Recommendation X.681 [14]. - -The ASN.1 definition specifies the structure and content of D2-C messages. D2CP messages can contain any IEs specified in the object set definitions for that message without the order or number of occurrences being restricted by ASN.1. However, for this version of the standard, a sending entity shall construct aD2-C message according to the PDU definitions module and with the following additional rules: - -- IEs shall be ordered (in an IE container) in the order they appear in object set definitions. -- Object set definitions specify how many times IEs may appear. An IE shall appear exactly once if the presence field in an object has value "mandatory". An IE may appear at most once if the presence field in an object has value "optional" or "conditional". If in a tabular format there is multiplicity specified for an IE (i.e., an IE list) then in the corresponding ASN.1 definition the list definition is separated into two parts. The first part defines an IE container list where the list elements reside. The second part defines list elements. The IE container list appears as an IE of its own. For this version of the standard an IE container list may contain only one kind of list elements. - -NOTE: In the above "IE" means an IE in the object set with an explicit ID. If one IE needs to appear more than once in one object set, then the different occurrences will have different IE IDs. - -If a D2CP message that is not constructed as defined above is received, this shall be considered as Abstract Syntax Error, and the message shall be handled as defined for Abstract Syntax Error. - -#### 5.4.4.2 Usage of private message mechanism for non-standard use - -The private message mechanism for non-standard use is not defined for D2CP messages. - -#### 5.4.4.3 Elementary Procedure Definitions - -``` --- ASN1START --- ***** --- --- Elementary Procedure definitions --- ***** - -D2CP-PDU-Descriptions { - itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) - ngran-access (22) modules (3) d2cp (4) version1 (1) d2cp-PDU-Descriptions (0)} - -DEFINITIONS AUTOMATIC TAGS ::= - -BEGIN - --- ***** --- --- IE parameter types from other modules. --- --- ***** - -IMPORTS - Criticality, - ProcedureCode - -FROM D2CP-CommonDataTypes - - D2ErrorIndication, - D2SetupRequest, - D2SetupResponse, - D2SetupFailure, - D2ConfigurationUpdate, - D2ConfigurationUpdateAcknowledge, - D2ConfigurationUpdateFailure, - D2ReleaseRequest, - D2ReleaseResponse, - UEAdditionRequest, - UEAdditionResponse, - UEDeletionRequest, - UEDeletionResponse, - UEModificationRequest, - UEModificationResponse, - UEModificationIndication, - UEReconfigurationComplete - -FROM D2CP-PDU-Contents - - id-d2errorIndication, - id-d2Setup, - id-d2ConfigurationUpdate, - id-d2Release, - id-uEAddition, - id-uEDeletion, - id-uEModificationUpdate, - id-uEModificationIndication, - id-uEReconfigurationComplete - -FROM D2CP-Constants; - --- ***** --- --- Interface Elementary Procedure Class --- --- ***** - -D2CP-ELEMENTARY-PROCEDURE ::= CLASS { - &InitiatingMessage , - &SuccessfulOutcome OPTIONAL, - &UnsuccessfulOutcome OPTIONAL, - &procedureCode ProcedureCode UNIQUE, - &criticality Criticality DEFAULT ignore -``` - -``` - -} -WITH SYNTAX { - INITIATING MESSAGE &InitiatingMessage - [SUCCESSFUL OUTCOME &SuccessfulOutcome] - [UNSUCCESSFUL OUTCOME &UnsuccessfulOutcome] - PROCEDURE CODE &procedureCode - [CRITICALITY &criticality] -} - --- ***** --- --- Interface PDU Definition --- --- ***** - -D2CP-PDU ::= CHOICE { - initiatingMessage InitiatingMessage, - successfulOutcome SuccessfulOutcome, - unsuccessfulOutcome UnsuccessfulOutcome, - ... -} - -InitiatingMessage ::= SEQUENCE { - procedureCode D2CP-ELEMENTARY-PROCEDURE.&procedureCode ({D2CP-ELEMENTARY-PROCEDURES}), - criticality D2CP-ELEMENTARY-PROCEDURE.&criticality ({D2CP-ELEMENTARY-PROCEDURES}{@procedureCode}), - value D2CP-ELEMENTARY-PROCEDURE.&InitiatingMessage ({D2CP-ELEMENTARY-PROCEDURES}{@procedureCode}) -} - -SuccessfulOutcome ::= SEQUENCE { - procedureCode D2CP-ELEMENTARY-PROCEDURE.&procedureCode ({D2CP-ELEMENTARY-PROCEDURES}), - criticality D2CP-ELEMENTARY-PROCEDURE.&criticality ({D2CP-ELEMENTARY-PROCEDURES}{@procedureCode}), - value D2CP-ELEMENTARY-PROCEDURE.&SuccessfulOutcome ({D2CP-ELEMENTARY-PROCEDURES}{@procedureCode}) -} - -UnsuccessfulOutcome ::= SEQUENCE { - procedureCode D2CP-ELEMENTARY-PROCEDURE.&procedureCode ({D2CP-ELEMENTARY-PROCEDURES}), - criticality D2CP-ELEMENTARY-PROCEDURE.&criticality ({D2CP-ELEMENTARY-PROCEDURES}{@procedureCode}), - value D2CP-ELEMENTARY-PROCEDURE.&UnsuccessfulOutcome ({D2CP-ELEMENTARY-PROCEDURES}{@procedureCode}) -} - --- ***** --- --- Interface Elementary Procedure List --- --- ***** - -D2CP-ELEMENTARY-PROCEDURES D2CP-ELEMENTARY-PROCEDURE ::= { -D2CP-ELEMENTARY-PROCEDURES-CLASS-1 | -D2CP-ELEMENTARY-PROCEDURES-CLASS-2, -... -} - -D2CP-ELEMENTARY-PROCEDURES-CLASS-1 D2CP-ELEMENTARY-PROCEDURE ::= { - d2Setup | - d2ConfigurationUpdate | - d2Release | - uEAddition | - uEDeletion | - uEModificationUpdate, - ... -} - -D2CP-ELEMENTARY-PROCEDURES-CLASS-2 D2CP-ELEMENTARY-PROCEDURE ::= { - d2ErrorIndication | - uEModificationIndication | - uEReconfigurationComplete, - ... -} - --- ***** --- - -``` - -``` --- Interface Elementary Procedures --- --- ***** -d2errorIndication D2CP-ELEMENTARY-PROCEDURE ::= { - INITIATING MESSAGE D2ErrorIndication - PROCEDURE CODE id-d2errorIndication - CRITICALITY ignore -} - -d2Setup D2CP-ELEMENTARY-PROCEDURE ::= { - INITIATING MESSAGE D2SetupRequest - SUCCESSFUL OUTCOME D2SetupResponse - UNSUCCESSFUL OUTCOME D2SetupFailure - PROCEDURE CODE id-d2Setup - CRITICALITY reject -} - -d2ConfigurationUpdate D2CP-ELEMENTARY-PROCEDURE ::= { - INITIATING MESSAGE D2ConfigurationUpdate - SUCCESSFUL OUTCOME D2ConfigurationUpdateAcknowledge - UNSUCCESSFUL OUTCOME D2ConfigurationUpdateFailure - PROCEDURE CODE id-d2ConfigurationUpdate - CRITICALITY reject -} - -d2Release D2CP-ELEMENTARY-PROCEDURE ::= { - INITIATING MESSAGE D2ReleaseRequest - SUCCESSFUL OUTCOME D2ReleaseResponse - PROCEDURE CODE id-d2Release - CRITICALITY reject -} - -uEAddition D2CP-ELEMENTARY-PROCEDURE ::= { - INITIATING MESSAGE UEAdditionRequest - SUCCESSFUL OUTCOME UEAdditionResponse - PROCEDURE CODE id-uEAddition - CRITICALITY reject -} - -uEDeletion D2CP-ELEMENTARY-PROCEDURE ::= { - INITIATING MESSAGE UEDeletionRequest - SUCCESSFUL OUTCOME UEDeletionResponse - PROCEDURE CODE id-uEDeletion - CRITICALITY reject -} - -uEModificationUpdate D2CP-ELEMENTARY-PROCEDURE ::= { - INITIATING MESSAGE UEModificationRequest - SUCCESSFUL OUTCOME UEModificationResponse - PROCEDURE CODE id-uEModificationUpdate - CRITICALITY reject -} - -uEModificationIndication D2CP-ELEMENTARY-PROCEDURE ::= { - INITIATING MESSAGE UEModificationIndication - PROCEDURE CODE id-uEModificationIndication - CRITICALITY reject -} - -uEReconfigurationComplete D2CP-ELEMENTARY-PROCEDURE ::= { - INITIATING MESSAGE UEReconfigurationComplete - PROCEDURE CODE id-uEReconfigurationComplete - CRITICALITY ignore -} - -END --- ASN1STOP -``` - -#### 5.4.4.4 PDU Definitions - -``` --- ASN1START -``` - -``` --- ***** --- --- PDU definitions for D2CP. --- ***** - -D2CP-PDU-Contents { - itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) - ngran-access (22) modules (3) d2cp (4) version1 (1) d2cp-PDU-Contents (1) } - -DEFINITIONS AUTOMATIC TAGS ::= - -BEGIN - --- ***** --- --- IE parameter types from other modules. --- --- ***** -IMPORTS - Cause, - D2U-Info-Item, - O-DU-ID, - SCell-Release-Item, - Served-Cell-Item, - ServedCellToMod-Item, - ServedCellToRel-Item, - TimeToWait, - TransactionID, - UE-Added-Item, - UE-Item, - UE-List, - UE-Modified-Item, - UE-Reconfig-List, - UE-Release-List, - UE-Release-Item, - UE-To-Be-Added-Item, - UE-ToBeModified-Item, - UE-ToBeUpdated-Item, - UpdatedCell-Item - -FROM D2CP-IEs - - ProtocolExtensionContainer{}, - ProtocolIE-Container{}, - ProtocolIE-ContainerList{}, - ProtocolIE-ContainerPair{}, - ProtocolIE-ContainerPairList{}, - ProtocolIE-SingleContainer{}, - D2CP-PROTOCOL-EXTENSION, - D2CP-PROTOCOL-IES, - D2CP-PROTOCOL-IES-PAIR - -FROM D2CP-Containers - - id-Cause, - id-D2U-Info-List, - id-D2U-Info-Item, - id-TimeToWait, - id-TransactionID, - id-Served-Cell-List, - id-Served-Cell-Item, - id-ServedCellToAdd-List, - id-ServedCellToMod-List, - id-ServedCellToMod-Item, - id-ServedCellToRel-List, - id-ServedCellToRel-Item, - id-Source-O-DU-ID, - id-Target-O-DU-ID, - id-UE-Added-Item, - id-UE-Added-List, - id-UE-Reconfig-List, - id-UE-Failed-To-Add-List, - id-UE-To-Be-Added-Item, - id-UE-To-Be-Added-List, - id-UE-FailedToAddMod-List, -``` - -``` - -id-UE-List, -id-UE-Reconfig-List, -id-UE-Item, -id-UE-Modified-List, -id-UE-Modified-Item, -id-UE-ToBeDeleted-List, -id-UE-ToBeReleased-List, -id-UE-ToBeModified-List, -id-UE-ToBeModified-Item, -id-UE-ToBeUpdated-List, -id-UE-ToBeUpdated-Item, -id-UpdatedCell-List, -id-UpdatedCell-Item, - -maxInterDUUEs, -maxInterDUSCells, -maxLCs, -maxSupportedD2U, -maxSupportedPV - -FROM D2CP-Constants; - --- ***** --- --- ERROR INDICATION ELEMENTARY PROCEDURE --- --- ***** --- ***** --- --- Error Indication --- --- ***** -D2ErrorIndication ::= SEQUENCE { - protocolIEs ProtocolIE-Container {D2ErrorIndicationIEs}, - ... -} -D2ErrorIndicationIEs D2CP-PROTOCOL-IES ::= { - { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory } | - { ID id-Source-O-DU-ID CRITICALITY ignore TYPE O-DU-ID PRESENCE optional } | - { ID id-Target-O-DU-ID CRITICALITY ignore TYPE O-DU-ID PRESENCE optional } | - { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE optional }, - ... -} - --- ***** --- --- D2 Setup ELEMENTARY PROCEDURE --- --- ***** --- ***** --- --- D2 SETUP REQUEST --- --- ***** -D2SetupRequest ::= SEQUENCE { - protocolIEs ProtocolIE-Container { D2SetupRequestIEs }, - ... -} - -D2SetupRequestIEs D2CP-PROTOCOL-IES ::= { - { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory } | - { ID id-Source-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory } | - { ID id-Target-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory } | - { ID id-Served-Cell-List CRITICALITY reject TYPE Served-Cell-List PRESENCE mandatory } | - { ID id-D2U-Info-List CRITICALITY reject TYPE D2U-Info-List PRESENCE mandatory }, - ... -} - -Served-Cell-List ::= SEQUENCE (SIZE(1.. maxInterDUSCells)) OF ProtocolIE-SingleContainer { { Served-Cell-ItemIEs } } - -Served-Cell-ItemIEs D2CP-PROTOCOL-IES ::= { - { ID id-Served-Cell-Item CRITICALITY reject TYPE Served-Cell-Item PRESENCE mandatory }, - ... -} - -``` - -``` - -D2U-Info-List ::= SEQUENCE (SIZE(1.. maxSupportedD2U)) OF ProtocolIE-SingleContainer { { D2U-Info-ItemIEs} -} - -D2U-Info-ItemIEs D2CP-PROTOCOL-IES ::= { - { ID id-D2U-Info-Item CRITICALITY reject TYPE D2U-Info-Item PRESENCE mandatory }, - ... -} - - --- D2 SETUP RESPONSE - - -D2SetupResponse ::= SEQUENCE { - protocolIEs ProtocolIE-Container { { D2SetupResponseIEs} }, - ... -} -D2SetupResponseIEs D2CP-PROTOCOL-IES ::= { - { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| - { ID id-Source-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-Target-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-Served-Cell-List CRITICALITY reject TYPE Served-Cell-List PRESENCE optional }| - { ID id-D2U-Info-List CRITICALITY reject TYPE D2U-Info-List PRESENCE mandatory }, - ... -} - - --- D2 SETUP FAILURE - - -D2SetupFailure ::= SEQUENCE { - protocolIEs ProtocolIE-Container { { D2SetupFailureIEs} }, - ... -} -D2SetupFailureIEs D2CP-PROTOCOL-IES ::= { - { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| - { ID id-Source-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-Target-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| - { ID id-TimeToWait CRITICALITY ignore TYPE TimeToWait PRESENCE optional }, - ... -} - - --- D2 Configuration Update ELEMENTARY PROCEDURE - - - --- D2 CONFIGURATION UPDATE - - -D2ConfigurationUpdate ::= SEQUENCE { - protocolIEs ProtocolIE-Container { { D2ConfigurationUpdateIEs} }, - ... -} - -D2ConfigurationUpdateIEs D2CP-PROTOCOL-IES ::= { - { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| - { ID id-Source-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-Target-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-ServedCellToAdd-List CRITICALITY reject TYPE Served-Cell-List PRESENCE optional }| - { ID id-ServedCellToMod-List CRITICALITY reject TYPE ServedCellToMod-List PRESENCE optional }| - { ID id-ServedCellToRel-List CRITICALITY reject TYPE ServedCellToRel-List PRESENCE optional }, - ... -} - -ServedCellToMod-List ::= SEQUENCE (SIZE(1.. maxInterDUSCells)) OF ProtocolIE-SingleContainer { { ServedCellToMod-ItemIEs} } - -ServedCellToMod-ItemIEs D2CP-PROTOCOL-IES ::= { - { ID id-ServedCellToMod-Item CRITICALITY reject TYPE ServedCellToMod-Item PRESENCE mandatory }, - ... -} - -``` - -``` -... -} - -ServedCellToRel-List ::= SEQUENCE (SIZE(1.. maxInterDUSCells)) OF ProtocolIE-SingleContainer { { -ServedCellToRel-ItemIEs } } - -ServedCellToRel-ItemIEs D2CP-PROTOCOL-IES ::= { -{ ID id-ServedCellToRel-Item CRITICALITY reject TYPE ServedCellToRel-Item PRESENCE mandatory }, -... -} - --- --- D2 CONFIGURATION UPDATE ACKNOWLEDGE --- - -D2ConfigurationUpdateAcknowledge ::= SEQUENCE { -protocolIEs ProtocolIE-Container { { D2ConfigurationUpdateAcknowledgeIEs } }, -... -} -D2ConfigurationUpdateAcknowledgeIEs D2CP-PROTOCOL-IES ::= { -{ ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| -{ ID id-Source-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| -{ ID id-Target-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| -{ ID id-UpdatedCell-List CRITICALITY reject TYPE UpdatedCell-List PRESENCE optional }, -... -} - -UpdatedCell-List ::= SEQUENCE (SIZE(1.. maxInterDUSCells)) OF ProtocolIE-SingleContainer { { UpdatedCell- -ItemIEs } } -UpdatedCell-ItemIEs D2CP-PROTOCOL-IES ::= { -{ ID id-UpdatedCell-Item CRITICALITY reject TYPE UpdatedCell-Item PRESENCE mandatory }, -... -} - - --- --- D2 CONFIGURATION UPDATE FAILURE --- - -D2ConfigurationUpdateFailure ::= SEQUENCE { -protocolIEs ProtocolIE-Container { { D2ConfigurationUpdateFailureIEs } }, -... -} -D2ConfigurationUpdateFailureIEs D2CP-PROTOCOL-IES ::= { -{ ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| -{ ID id-Source-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| -{ ID id-Target-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| -{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| -{ ID id-TimeToWait CRITICALITY ignore TYPE TimeToWait PRESENCE optional }, -... -} - - --- --- D2 Release ELEMENTARY PROCEDURE --- - - --- --- D2 RELEASE REQUEST --- - -D2ReleaseRequest ::= SEQUENCE { -protocolIEs ProtocolIE-Container { { D2ReleaseRequestIEs } }, -... -} -D2ReleaseRequestIEs D2CP-PROTOCOL-IES ::= { -{ ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| -{ ID id-Source-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| -{ ID id-Target-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| -{ ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, -... -} - -``` - -``` --- --- D2 RELEASE RESPONSE --- --- ***** -D2ReleaseResponse ::= SEQUENCE { - protocolIEs ProtocolIE-Container { { D2ReleaseResponseIEs} }, - ... -} - -D2ReleaseResponseIEs D2CP-PROTOCOL-IES ::= { - { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| - { ID id-Source-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-Target-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }, - ... -} - --- ***** --- --- UE Addition ELEMENTARY PROCEDURE --- --- ***** --- ***** --- --- UE ADDITION REQUEST --- --- ***** -UEAdditionRequest ::= SEQUENCE { - protocolIEs ProtocolIE-Container { { UEAdditionRequestIEs} }, - ... -} - -UEAdditionRequestIEs D2CP-PROTOCOL-IES ::= { - { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| - { ID id-Source-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-Target-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-UE-To-Be-Added-List CRITICALITY reject TYPE UE-To-Be-Added-List PRESENCE mandatory }, - ... -} - -UE-To-Be-Added-List ::= SEQUENCE (SIZE(1.. maxInterDUUEs)) OF ProtocolIE-SingleContainer { { UE-To-Be-Added-ItemIEs} } - -UE-To-Be-Added-ItemIEs D2CP-PROTOCOL-IES ::= { - { ID id-UE-To-Be-Added-Item CRITICALITY reject TYPE UE-To-Be-Added-Item PRESENCE mandatory }, - ... -} --- ***** --- --- UE ADDITION RESPONSE --- --- ***** -UEAdditionResponse ::= SEQUENCE { - protocolIEs ProtocolIE-Container { { UEAdditionResponseIEs} }, - ... -} - -UEAdditionResponseIEs D2CP-PROTOCOL-IES ::= { - { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| - { ID id-Source-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-Target-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-UE-Added-List CRITICALITY ignore TYPE UE-Added-List PRESENCE optional }| - { ID id-UE-Failed-To-Add-List CRITICALITY ignore TYPE UE-Release-List PRESENCE optional }, - ... -} - -UE-Added-List ::= SEQUENCE (SIZE(1.. maxInterDUUEs)) OF ProtocolIE-SingleContainer { { UE-Added-ItemIEs} } - -UE-Added-ItemIEs D2CP-PROTOCOL-IES ::= { - { ID id-UE-Added-Item CRITICALITY reject TYPE UE-Added-Item PRESENCE mandatory }, - ... -} - --- ***** --- --- UE Deletion ELEMENTARY PROCEDURE --- --- ***** --- ***** -``` - -``` --- UE DELETION Request --- --- ***** -UEDeletionRequest ::= SEQUENCE { - protocolIEs ProtocolIE-Container {{ UEDeletionRequestIEs}}, - ... -} - -UEDeletionRequestIEs D2CP-PROTOCOL-IES ::= { - { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| - { ID id-Source-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-Target-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-UE-ToBeDeleted-List CRITICALITY reject TYPE UE-List PRESENCE mandatory }, - ... -} - --- ***** --- --- UE DELETION RESPONSE --- --- ***** -UEDeletionResponse ::= SEQUENCE { - protocolIEs ProtocolIE-Container { { UEDeletionResponseIEs} }, - ... -} -UEDeletionResponseIEs D2CP-PROTOCOL-IES ::= { - { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| - { ID id-Source-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-Target-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }, - ... -} - --- ***** --- --- UE Modification ELEMENTARY PROCEDURE --- --- ***** --- ***** --- --- UE MODIFICATION REQUEST --- --- ***** -UEModificationRequest ::= SEQUENCE { - protocolIEs ProtocolIE-Container { { UEModificationRequestIEs} }, - ... -} -UEModificationRequestIEs D2CP-PROTOCOL-IES ::= { - { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| - { ID id-Source-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-Target-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-UE-ToBeModified-List CRITICALITY reject TYPE UE-ToBeModified-List PRESENCE mandatory }, - ... -} -UE-ToBeModified-List ::= SEQUENCE (SIZE(1.. maxInterDUUEs)) OF ProtocolIE-SingleContainer { { UE-ToBeModified-ItemIEs} } -UE-ToBeModified-ItemIEs D2CP-PROTOCOL-IES ::= { - {ID id-UE-ToBeModified-Item CRITICALITY ignore TYPE UE-ToBeModified-Item PRESENCE mandatory }, - ... -} - --- ***** --- --- UE MODIFICATION RESPONSE --- --- ***** -UEModificationResponse ::= SEQUENCE { - protocolIEs ProtocolIE-Container { { UEModificationResponseIEs} }, - ... -} - -UEModificationResponseIEs D2CP-PROTOCOL-IES ::= { - { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| - { ID id-Source-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-Target-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| -``` - -``` - -{ ID id-UE-Modified-List CRITICALITY ignore TYPE UE-Modified-List PRESENCE optional }| -{ ID id-UE-FailedToAddMod-List CRITICALITY ignore TYPE UE-Release-List PRESENCE optional }, -... -} - -UE-Modified-List ::= SEQUENCE (SIZE (1.. maxInterDUUEs)) OF ProtocolIE-SingleContainer { { UE-Modified-ItemIEs} } -UE-Modified-ItemIEs D2CP-PROTOCOL-IES ::= { - { ID id-UE-Modified-Item CRITICALITY ignore TYPE UE-Modified-Item PRESENCE mandatory }, - ... -} - - - - UE MODIFICATION INDICATION - - -UEModificationIndication ::= SEQUENCE { - protocolIEs ProtocolIE-Container { { UEModificationIndicationIEs} }, - ... -} - -UEModificationIndicationIEs D2CP-PROTOCOL-IES ::= { - { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| - { ID id-Source-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-Target-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-UE-ToBeUpdated-List CRITICALITY ignore TYPE UE-ToBeUpdated-List PRESENCE optional }| - { ID id-UE-ToBeReleased-List CRITICALITY ignore TYPE UE-Release-List PRESENCE optional }, - ... -} - -UE-ToBeUpdated-List ::= SEQUENCE (SIZE (1.. maxInterDUUEs)) OF ProtocolIE-SingleContainer { { UE-ToBeUpdated-ItemIEs } } - -UE-ToBeUpdated-ItemIEs D2CP-PROTOCOL-IES ::= { - { ID id-UE-ToBeUpdated-Item CRITICALITY reject TYPE UE-ToBeUpdated-Item PRESENCE mandatory }, - ... -} - - - - UE Reconfiguration ELEMENTARY PROCEDURE - - - - - UE RECONFIGURATION COMPLETE - - -UEReconfigurationComplete ::= SEQUENCE { - protocolIEs ProtocolIE-Container { { UEReconfigurationCompleteIEs} }, - ... -} - -UEReconfigurationCompleteIEs D2CP-PROTOCOL-IES ::= { - { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| - { ID id-Source-O-DU-ID CRITICALITY reject TYPE O-DU-ID PRESENCE mandatory }| - { ID id-Target-O-DU-ID CRITICALITY ignore TYPE O-DU-ID PRESENCE mandatory }| - { ID id-UE-Reconfig-List CRITICALITY reject TYPE UE-Reconfig-List PRESENCE mandatory }, - ... -} - -END --- ASN1STOP - -``` - -#### 5.4.4.5 Information Element Definitions - -``` - --- ASN1START - - - Information Element Definitions - - -D2CP-IEs { - -``` - -itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) ngran-access (22) modules (3) d2cp (4) -version1 (1) d2cp-IEs (2) } - -DEFINITIONS AUTOMATIC TAGS ::= - -BEGIN - -IMPORTS - -Criticality, -ProcedureCode, -ProtocolIE-ID - -FROM D2CP-CommonDataTypes - -maxInterDUUEs, -maxInterDUSCells, -maxLCs, -maxSupportedD2U, -maxSupportedPV - -FROM D2CP-Constants - -ProtocolExtensionContainer{}, -D2CP-PROTOCOL-EXTENSION, -ProtocolIE-SingleContainer{}, -D2CP-PROTOCOL-IES - -FROM D2CP-Containers; - ---A - ---B - -BitRate ::= INTEGER (0..40000000000000, ...) - ---C - -Cause ::= ENUMERATED { - abstract-syntax-error-reject, - abstract-syntax-error-ignore-and-notify, - message-not-compatible-with-receiver-state, - semantic-error, - abstract-syntax-error-falsely-constructed-message, - unspecified, - scell-down, - ue-not-allowed, - cell-overload, - cqi-failure, - harq-failure, - pv-notsupported, - udp-invalidinfo, - success, - ... -} - -CAType ::= ENUMERATED {dl, ...} - -C-RNTI ::= INTEGER (0..65535, ...) - ---D - -D2UEID ::= INTEGER (0..maxInterDUUEs, ...) - -DRX-Config ::= OCTET STRING - -D2U-Info-Item ::= SEQUENCE { - d2u-udp-info D2U-UDP-Info-List, - pvList ProtocolVersion-List, - t-clearTB T-ClearTB, - iE-Extensions ProtocolExtensionContainer { { D2U-Info-Item-ExtIEs } } OPTIONAL, - ... -} - -``` - -} -D2U-Info-Item-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { - -} - -D2U-UDP-Info-List ::= SEQUENCE (SIZE (1.. maxSupportedD2U)) OF D2U-UDP-Info-Item - -D2U-UDP-Info-Item ::= SEQUENCE { - d2u-ip TransportLayerAddress, - d2u-port PortNum, - iE-Extensions ProtocolExtensionContainer { { D2U-UDP-Info-Item-ExtIEs } } OPTIONAL, - -} - -D2U-UDP-Info-Item-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { - -} - -``` - ---E - ---F - ---G - -``` - -GBR-QoSFlowInformation ::= SEQUENCE { - maxFlowBitRateDownlink BitRate, - maxFlowBitRateUplink BitRate, - guaranteedFlowBitRateDownlink BitRate, - guaranteedFlowBitRateUplink BitRate, - maxPacketLossRateDownlink INTEGER(0..1000) OPTIONAL, - maxPacketLossRateUplink INTEGER(0..1000) OPTIONAL, - iE-Extensions ProtocolExtensionContainer { { GBR-QoSFlowInformation-ExtIEs } } OPTIONAL, - -} - -GBR-QoSFlowInformation-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { - -} - -``` - ---H - ---I - ---J - ---K - ---L - -``` - -LCID ::= INTEGER (1..32, ) - -LC-Info-List ::= SEQUENCE (SIZE (1..maxLCs)) OF LC-Info-Item - -LC-Info-Item ::= SEQUENCE { - LCID LCID, - qosInformation QoSInformation, - sNSSAI SNSSAI, - iE-Extensions ProtocolExtensionContainer { { LC-Info-ItemExtIEs } } OPTIONAL, - -} - -LC-Info-ItemExtIEs D2CP-PROTOCOL-EXTENSION ::= { - -} - -LC-List ::= SEQUENCE (SIZE (1..maxLCs)) OF LC-Item - -LC-Item ::= SEQUENCE { - LCID LCID, - iE-Extensions ProtocolExtensionContainer { { LC-ItemExtIEs } } OPTIONAL, -} - -``` - -``` - ... -} - -LC-ItemExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} - -LC-Release-List ::= SEQUENCE (SIZE(1..maxLCs)) OF LC-Release-Item -LC-Release-Item ::= SEQUENCE { - lCID LCID, - cause Cause, - iE-Extensions ProtocolExtensionContainer { { LC-Release-ItemExtIEs } } OPTIONAL, - ... -} - -LC-Release-ItemExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} -``` - -##### --M - -``` -MaxMIMO-Layers ::= INTEGER (1..16, ...) - -MeasGapConfig ::= OCTET STRING -``` - -##### --N - -``` -NGRANAllocationAndRetentionPriority ::= SEQUENCE { - priorityLevel PriorityLevel, - pre-emptionCapability Pre-emptionCapability, - pre-emptionVulnerability Pre-emptionVulnerability, - iE-Extensions ProtocolExtensionContainer { {NGRANAllocationAndRetentionPriority-ExtIEs} } OPTIONAL, - ... -} -NGRANAllocationAndRetentionPriority-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} - -NRCellIdentity ::= BIT STRING (SIZE(36)) - -NRCGI ::= SEQUENCE { - pLMN-Identity PLMN-Identity, - nRCellIdentity NRCellIdentity, - iE-Extensions ProtocolExtensionContainer { {NRCGI-ExtIEs} } OPTIONAL, - ... -} -NRCGI-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} - -NRPCI ::= INTEGER(0..1007) -``` - -##### --O - -``` -O-DU-ID ::= INTEGER (0..68719476735) -``` - -##### --P - -``` -PacketDelayBudget ::= INTEGER (0..1023, ...) - -PacketErrorRate ::= SEQUENCE { - pER-Scalar PER-Scalar, - pER-Exponent PER-Exponent, - iE-Extensions ProtocolExtensionContainer { {PacketErrorRate-ExtIEs} } OPTIONAL, - ... -} -``` - -``` - -PacketErrorRate-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} -PER-Scalar ::= INTEGER (0..9, ...) -PER-Exponent ::= INTEGER (0..9, ...) -PeriodicCqiReportSize ::= INTEGER (1..50, ...) -PLMN-Identity ::= OCTET STRING (SIZE(3)) -PortNum ::= BIT STRING (SIZE (16)) -Pre-emptionCapability ::= ENUMERATED { - shall-not-trigger-pre-emption, - may-trigger-pre-emption -} -Pre-emptionVulnerability ::= ENUMERATED { - not-pre-emptable, - pre-emptable -} -PriorityLevel ::= INTEGER { spare (0), highest (1), lowest (14), no-priority (15) } (0..15) -ProtocolVersion-List ::= SEQUENCE (SIZE (1.. maxSupportedPV)) OF ProtocolVersion-Item -ProtocolVersion-Item ::= SEQUENCE { - pv INTEGER (0..255), - iE-Extensions ProtocolExtensionContainer { { ProtocolVersion-Item-ExtIEs } } OPTIONAL, - ... -} -ProtocolVersion-Item-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} - -P-O-DU-To-S-O-DU-SCell-Information ::= SEQUENCE { - sCellID NRCGI, - sCellIndex SCellIndex, - servingCellMO ServingCellMO OPTIONAL, - maxMIMO-LayersDL MaxMIMO-Layers OPTIONAL, - reportConfigType OCTET STRING, - iE-Extensions ProtocolExtensionContainer { { P-O-DU-To-S-O-DU-SCell-Information-ExtIEs } } OPTIONAL, - ... -} - -P-O-DU-To-S-O-DU-SCell-Information-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} - -``` - -##### --Q - -``` - -QoSInformation ::= SEQUENCE { - nr5QI INTEGER (0..255, ...), - nGRANAllocationRetentionPriority NGRANAllocationAndRetentionPriority, - qosPriorityLevel INTEGER (1..127), - packetDelayBudget PacketDelayBudget, - packetErrorRate PacketErrorRate, - delayCritical ENUMERATED {delay-critical, non-delay-critical}, - gbrQoSInfo GBR-QoSFlowInformation OPTIONAL, - iE-Extensions ProtocolExtensionContainer { { QoSInformation-ExtIEs } } OPTIONAL, - ... -} -QoSInformation-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} - -``` - -##### --R - -Result ::= ENUMERATED {success, failure}--S - -``` - -S-O-DU-To-P-O-DU-SCell-Information ::= SEQUENCE { - sCellID NRCGI, - sCellIndex SCellIndex, - sCellConfig SCellConfig, - maxMIMO-LayersUsedDL MaxMIMO-Layers, - periodicCqiReportSize PeriodicCqiReportSize OPTIONAL, - csi-ReportConfig OCTET STRING, - iE-Extensions ProtocolExtensionContainer { { S-O-DU-To-P-O-DU-SCell-Information-ExtIEs } } OPTIONAL, - ... -} - -S-O-DU-To-P-O-DU-SCell-Information-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} - -SCell-Added-List ::= SEQUENCE (SIZE(1..maxInterDUSCells)) OF SCell-Added-Item - -SCell-Added-Item ::= SEQUENCE { - sO-DU-to-pO-DU-SCell-Information S-O-DU-To-P-O-DU-SCell-Information, - iE-Extensions ProtocolExtensionContainer { { SCell-Added-ItemExtIEs } } OPTIONAL, - ... -} - -SCell-Added-ItemExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} - -SCellConfig ::= OCTET STRING - -SCellIndex ::= INTEGER (1..31, ...) - -SCell-List ::= SEQUENCE (SIZE(1..maxInterDUSCells)) OF SCell-Item - -SCell-Item ::= SEQUENCE { - sCellID NRCGI, - sCellIndex SCellIndex, - iE-Extensions ProtocolExtensionContainer { { SCell-ItemExtIEs } } OPTIONAL, - ... -} - -SCell-ItemExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} - -SCell-Info-List ::= SEQUENCE { - pO-DU-To-sO-DU-SCell-Information P-O-DU-To-S-O-DU-SCell-Information, - iE-Extensions ProtocolExtensionContainer { { SCell-Info-ListExtIEs } } OPTIONAL, - ... -} - -SCell-Info-ListExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} - -SCell-Release-List ::= SEQUENCE (SIZE(1..maxInterDUSCells)) OF SCell-Release-Item - -SCell-Release-Item ::= SEQUENCE { - sCellID NRCGI, - sCellIndex SCellIndex, - cause Cause, - iE-Extensions ProtocolExtensionContainer { { SCell-Release-ItemExtIEs } } OPTIONAL, - ... -} - -SCell-Release-ItemExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} - -ServingCellMO ::= INTEGER (1..64, ...) - -Served-Cell-Item ::= SEQUENCE{ - servedCellInformation OCTET STRING, -} - -``` - -``` - -caType CAType, -startCRNTI C-RNTI, -endCRNTI C-RNTI, -iE-Extensions ProtocolExtensionContainer { { Served-Cell-Item-ExtIEs } } OPTIONAL, -... -} -Served-Cell-Item-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { -... -} - -ServedCellToMod-Item ::= SEQUENCE{ - oldNRCGI NRCGI, - servedCellInformation OCTET STRING, - caType CAType, - startCRNTI C-RNTI, - endCRNTI C-RNTI, - iE-Extensions ProtocolExtensionContainer { { ServedCellToMod-Item-ExtIEs } } OPTIONAL, - ... -} -ServedCellToMod-Item-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { -... -} - -ServedCellToRel-Item ::= SEQUENCE{ - nrCGI NRCGI, - iE-Extensions ProtocolExtensionContainer { { ServedCellToRel-Item-ExtIEs } } OPTIONAL, - ... -} -ServedCellToRel-Item-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { -... -} - -SNSSAI ::= SEQUENCE { - sST OCTET STRING (SIZE(1)), - sD OCTET STRING (SIZE(3)) OPTIONAL , - iE-Extensions ProtocolExtensionContainer { { SNSSAI-ExtIEs } } OPTIONAL, - ... -} - -SNSSAI-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { -... -} - ---T - -T-ClearTB ::= ENUMERATED { ms1, ms2, ms5, ms10, ms20, ms60, ...} - -TimeToWait ::= ENUMERATED { s1, s2, s5, s10, s20, s60, s120, ...} - -TransactionID ::= INTEGER (0..255, ...) - -TransportLayerAddress ::= BIT STRING (SIZE(1..160, ...)) - ---U - -UE-Added-Item ::= SEQUENCE { - cRNTI C-RNTI, - d2UEID D2UEID, - sCellAddedList SCell-Added-List , - lcAddedList LC-List, - lcFailedToAddList LC-Release-List, - sCellFailedToAddList SCell-Release-List, - iE-Extensions ProtocolExtensionContainer { { UE-Added-Item-ExtIEs } } OPTIONAL, - ... -} - -UE-Added-Item-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { -... -} - -UE-List ::= SEQUENCE (SIZE(1..maxInterDUUEs)) OF UE-Item - -UE-Item ::= SEQUENCE { - cRNTI C-RNTI, - -``` - -``` - -d2UEID D2UEID, -iE-Extensions ProtocolExtensionContainer { { UE-ItemExtIEs } } OPTIONAL, -... -} - -UE-ItemExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} - -UE-Reconfig-List ::= SEQUENCE (SIZE(1..maxInterDUUEs)) OF UE-Reconfig-Item - -UE-Reconfig-Item ::= SEQUENCE { - cRNTI C-RNTI, - d2UEID D2UEID, - sCellList SCell-List, - iE-Extensions ProtocolExtensionContainer { { UE-Reconfig-ItemExtIEs } } OPTIONAL, - ... -} - -UE-Reconfig-ItemExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} - -UE-Modified-Item ::= SEQUENCE { - cRNTI C-RNTI, - d2UEID D2UEID, - sCellUpdatedList SCell-Added-List OPTIONAL, - lcUpdatedList LC-List OPTIONAL, - lcFailedToAddModList LC-Release-List OPTIONAL, - sCellFailedToAddModList SCell-Release-List OPTIONAL, - iE-Extensions ProtocolExtensionContainer { { UE-Modified-Item-ExtIEs } } OPTIONAL, - ... -} - -UE-Modified-Item-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} - -UE-Release-List ::= SEQUENCE (SIZE(1..maxInterDUUEs)) OF UE-Release-Item - -UE-Release-Item ::= SEQUENCE { - cRNTI C-RNTI, - d2UEID D2UEID, - cause Cause, - iE-Extensions ProtocolExtensionContainer { { UE-Release-ItemExtIEs } } OPTIONAL, - ... -} - -UE-Release-ItemExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} - -UE-To-Be-Added-Item ::= SEQUENCE { - cRNTI C-RNTI, - d2UEID D2UEID, - maxMIMO-LayersDL-PerDU INTEGER (1..32, ...), - uE-CapabilityRATContainerList UE-CapabilityRATContainerList, - sCellToBeAddedList SCell-Info-List, - measGapConfig MeasGapConfig OPTIONAL, - drx-Config DRX-Config OPTIONAL, - lcToBeAddedList LC-Info-List, - iE-Extensions ProtocolExtensionContainer { { UE-To-Be-Added-Item-ExtIEs } } OPTIONAL, - ... -} - -UE-To-Be-Added-Item-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... -} - -UE-ToBeModified-Item ::= SEQUENCE { - cRNTI C-RNTI, - d2UEID D2UEID, - maxMIMO-LayersDL-PerDU MaxMIMO-Layers, - uE-CapabilityRATContainerList UE-CapabilityRATContainerList OPTIONAL, - sCellToAddModList SCell-Info-List OPTIONAL, -} - -``` - -``` - - measGapConfig MeasGapConfig OPTIONAL, - drx-Config DRX-Config OPTIONAL, - lcToAddModList LC-Info-List OPTIONAL, - lcToDeleteList LC-List OPTIONAL, - sCellToDeleteList SCell-List OPTIONAL, - iE-Extensions ProtocolExtensionContainer { { UE-ToBeModified-Item-ExtIEs} } OPTIONAL, - ... - } - - UE-ToBeModified-Item-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... - } - - UE-ToBeUpdated-Item ::= SEQUENCE { - CRNTI C-RNTI, - d2UEID D2UEID, - sCellToBeReleasedList SCell-Release-List OPTIONAL, - lcToBeReleasedList LC-Release-List OPTIONAL, - iE-Extensions ProtocolExtensionContainer { { UE-ToBeUpdated-Item-ExtIEs} } OPTIONAL, - ... - } - - UE-ToBeUpdated-Item-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... - } - - UE-CapabilityRATContainerList ::= OCTET STRING - - UpdatedCell-Item ::= SEQUENCE{ - nRCGI NRCGI, - nrPCI NRPCI OPTIONAL, - result Result, - iE-Extensions ProtocolExtensionContainer { { UpdatedCell-Item-ExtIEs} } OPTIONAL, - ... - } - - UpdatedCell-Item-ExtIEs D2CP-PROTOCOL-EXTENSION ::= { - ... - } - ---V - ---W - ---X - ---Y - ---Z - -END --- ASN1STOP - -``` - -#### 5.4.4.6 Common Definitions - -``` - --- ASN1START - --- --- Common definitions --- - - -D2CP-CommonDataTypes { - itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) - ngran-access (22) modules (3) d2cp (4) version1 (1) d2cp-CommonDataTypes (3) } - -DEFINITIONS AUTOMATIC TAGS ::= - -BEGIN - -``` - -``` --- ***** --- --- Extension constants --- --- ***** -maxProtocolExtensions INTEGER := 65535 -maxProtocolIEs INTEGER := 65535 - --- ***** --- --- Common Data Types --- --- ***** - -Criticality := ENUMERATED { reject, ignore, notify } - -Presence := ENUMERATED { optional, conditional, mandatory } - -ProcedureCode := INTEGER (0..255) - -ProtocolExtensionID := INTEGER (0..maxProtocolExtensions) - -ProtocolIE-ID := INTEGER (0..maxProtocolIEs) - -END --- ASN1STOP -``` - -#### 5.4.4.7 Constant Definitions - -``` --- ASN1START --- ***** --- --- Constant definitions --- --- ***** -D2CP-Constants { - itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) - ngran-access (22) modules (3) d2cp (4) version1 (1) d2cp-Constants (4) } - -DEFINITIONS AUTOMATIC TAGS ::= - -BEGIN - -IMPORTS - ProcedureCode, - ProtocolIE-ID -FROM D2CP-CommonDataTypes; - --- ***** --- --- Elementary Procedures --- --- ***** -id-d2Setup ProcedureCode := 0 -id-d2ErrorIndication ProcedureCode := 1 -id-d2ConfigurationUpdate ProcedureCode := 2 -id-d2Release ProcedureCode := 3 -id-uEAddition ProcedureCode := 4 -id-uEDeletion ProcedureCode := 5 -id-uEModificationUpdate ProcedureCode := 6 -id-uEModificationIndication ProcedureCode := 7 -id-uEReconfigurationComplete ProcedureCode := 8 - --- ***** --- --- Lists --- --- ***** -maxInterDUUEs INTEGER := 65535 -maxInterDUSCells INTEGER := 32 -maxLCs INTEGER := 255 -maxSupportedD2U INTEGER := 255 -maxSupportedPV INTEGER := 16 -``` - -``` --- ***** --- --- IEs --- --- ***** -id-Cause ProtocolIE-ID ::= 0 -id-D2U-Info-List ProtocolIE-ID ::= 1 -id-D2U-Info-Item ProtocolIE-ID ::= 2 -id-Source-O-DU-ID ProtocolIE-ID ::= 3 -id-Target-O-DU-ID ProtocolIE-ID ::= 4 -id-TransactionID ProtocolIE-ID ::= 5 -id-Served-Cell-Item ProtocolIE-ID ::= 6 -id-Served-Cell-List ProtocolIE-ID ::= 7 -id-ServedCellToAdd-Item ProtocolIE-ID ::= 8 -id-ServedCellToAdd-List ProtocolIE-ID ::= 9 -id-ServedCellToMod-Item ProtocolIE-ID ::= 10 -id-ServedCellToMod-List ProtocolIE-ID ::= 11 -id-ServedCellToRel-Item ProtocolIE-ID ::= 12 -id-ServedCellToRel-List ProtocolIE-ID ::= 13 -id-UE-Added-Item ProtocolIE-ID ::= 14 -id-UE-Added-List ProtocolIE-ID ::= 15 -id-UE-Failed-To-Add-Item ProtocolIE-ID ::= 16 -id-UE-Failed-To-Add-List ProtocolIE-ID ::= 17 -id-UE-FailedToAddMod-List ProtocolIE-ID ::= 18 -id-UE-Item ProtocolIE-ID ::= 19 -id-UE-List ProtocolIE-ID ::= 20 -id-UE-Modified-Item ProtocolIE-ID ::= 21 -id-UE-Modified-List ProtocolIE-ID ::= 22 -id-UE-To-Be-Added-Item ProtocolIE-ID ::= 23 -id-UE-To-Be-Added-List ProtocolIE-ID ::= 24 -id-UE-ToBeDeleted-List ProtocolIE-ID ::= 25 -id-UE-ToBeModified-Item ProtocolIE-ID ::= 26 -id-UE-ToBeModified-List ProtocolIE-ID ::= 27 -id-UE-ToBeUpdated-Item ProtocolIE-ID ::= 28 -id-UE-ToBeUpdated-List ProtocolIE-ID ::= 29 -id-UE-ToBeReleased-List ProtocolIE-ID ::= 30 -id-UE-Reconfig-List ProtocolIE-ID ::= 31 -id-UpdatedCell-Item ProtocolIE-ID ::= 32 -id-UpdatedCell-List ProtocolIE-ID ::= 33 -id-TimeToWait ProtocolIE-ID ::= 34 - -END --- ASN1STOP -``` - -#### 5.4.4.8 Container Definitions - -``` --- ASN1START --- ***** --- --- Container definitions --- --- ***** -D2CP-Containers { - itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) - ngran-access (22) modules (3) d2cp (4) version1 (1) d2cp-Containers (5) } - -DEFINITIONS AUTOMATIC TAGS ::= - -BEGIN --- ***** --- --- IE parameter types from other modules. --- --- ***** - -IMPORTS - maxProtocolExtensions, - maxProtocolIEs, - Criticality, - Presence, - ProtocolIE-ID, - ProtocolExtensionID -FROM D2CP-CommonDataTypes; -``` - -``` --- ***** --- --- Class Definition for Protocol IEs --- --- ***** -D2CP-PROTOCOL-IES ::= CLASS { - &id ProtocolIE-ID UNIQUE, - &criticality Criticality, - &Value, - &presence Presence -} -WITH SYNTAX { - ID &id - CRITICALITY &criticality - TYPE &Value - PRESENCE &presence -} - --- ***** --- --- Class Definition for Protocol IEs --- --- ***** - -D2CP-PROTOCOL-IES-PAIR ::= CLASS { - &id ProtocolIE-ID UNIQUE, - &firstCriticality Criticality, - &FirstValue, - &secondCriticality Criticality, - &SecondValue, - &presence Presence -} -WITH SYNTAX { - ID &id - FIRST CRITICALITY &firstCriticality - FIRST TYPE &FirstValue - SECOND CRITICALITY &secondCriticality - SECOND TYPE &SecondValue - PRESENCE &presence -} - --- ***** --- --- Class Definition for Protocol Extensions --- --- ***** -D2CP-PROTOCOL-EXTENSION ::= CLASS { - &id ProtocolExtensionID UNIQUE, - &criticality Criticality, - &Extension, - &presence Presence -} -WITH SYNTAX { - ID &id - CRITICALITY &criticality - EXTENSION &Extension - PRESENCE &presence -} - --- ***** --- --- Container for Protocol IEs --- --- ***** -ProtocolIE-Container {D2CP-PROTOCOL-IES : IEsSetParam} ::= - SEQUENCE (SIZE (0..maxProtocolIEs)) OF - ProtocolIE-Field {{IEsSetParam}} - -ProtocolIE-SingleContainer {D2CP-PROTOCOL-IES : IEsSetParam} ::= - ProtocolIE-Field {{IEsSetParam}} - -ProtocolIE-Field {D2CP-PROTOCOL-IES : IEsSetParam} ::= SEQUENCE { - id D2CP-PROTOCOL-IES.&id {{IEsSetParam}}, - criticality D2CP-PROTOCOL-IES.&criticality {{IEsSetParam}{@id}}, - value D2CP-PROTOCOL-IES.&Value {{IEsSetParam}{@id}} -``` - -``` - -} - - --- --- Container for Protocol IE Pairs --- - -ProtocolIE-ContainerPair {D2CP-PROTOCOL-IES-PAIR : IEsSetParam} ::= -SEQUENCE (SIZE (0..maxProtocolIEs)) OF -ProtocolIE-FieldPair {{IEsSetParam}} - -ProtocolIE-FieldPair {D2CP-PROTOCOL-IES-PAIR : IEsSetParam} ::= SEQUENCE { -id D2CP-PROTOCOL-IES-PAIR.&id ({IEsSetParam}), -firstCriticality D2CP-PROTOCOL-IES-PAIR.&firstCriticality ({IEsSetParam}{@id}), -firstValue D2CP-PROTOCOL-IES-PAIR.&FirstValue ({IEsSetParam}{@id}), -secondCriticality D2CP-PROTOCOL-IES-PAIR.&secondCriticality ({IEsSetParam}{@id}), -secondValue D2CP-PROTOCOL-IES-PAIR.&SecondValue ({IEsSetParam}{@id}) -} - - --- --- Container Lists for Protocol IE Containers --- - - -ProtocolIE-ContainerList {INTEGER : lowerBound, INTEGER : upperBound, D2CP-PROTOCOL-IES : IEsSetParam} ::= -SEQUENCE (SIZE (lowerBound..upperBound)) OF -ProtocolIE-Container {{IEsSetParam}} - -ProtocolIE-ContainerPairList {INTEGER : lowerBound, INTEGER : upperBound, D2CP-PROTOCOL-IES-PAIR : -IEsSetParam} ::= -SEQUENCE (SIZE (lowerBound..upperBound)) OF -ProtocolIE-ContainerPair {{IEsSetParam}} - - --- --- Container for Protocol Extensions --- - -ProtocolExtensionContainer {D2CP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= -SEQUENCE (SIZE (1..maxProtocolExtensions)) OF -ProtocolExtensionField {{ExtensionSetParam}} - -ProtocolExtensionField {D2CP-PROTOCOL-EXTENSION : ExtensionSetParam} ::= SEQUENCE { -id D2CP-PROTOCOL-EXTENSION.&id ({ExtensionSetParam}), -criticality D2CP-PROTOCOL-EXTENSION.&criticality ({ExtensionSetParam}{@id}), -extensionValue D2CP-PROTOCOL-EXTENSION.&Extension ({ExtensionSetParam}{@id}) -} - - - -END --- ASN1STOP -``` - -### 5.4.5 Message Transfer Syntax - -D2CP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant as transfer syntax, as specified in ITU-T Rec. X.691 [12]. - -### 5.4.6 Timers - -# 6 D2 User Plane protocol - -## 6.1 D2UP services - -The following services are provided by the D2UP protocol: - -- Provision of D2 sequence number information for user data request and transfer between SCell O-DU and PCell O-DU. -- Request of new user data or retransmission scheduling on SCell O-DU along with the slot Range where UE can be scheduled in SCell O-DU. -- Request for data transfer along with information on allocated DL channel (PDSCH & PDCCH) resources on the SCell(s) -- Provision of sharing PUCCH resource allocation with SCell O-DU. -- Information of clearing the MAC TB stored in SCell O-DU once data is transmitted to UE successfully. -- Information of clearing the MAC TB once PCell O-DU decides not to continue with further transmission -- sharing of the Uplink Control Information received from UE. - -## 6.2 D2UP Functions - -The functions of D2UP are described in TS O-RAN.WG5.TS.D2GAP [2]. - -## 6.3 D2UP Procedures - -### 6.3.1 Downlink data transfer - -#### 6.3.1.1 DL Scheduling Request - -The purpose of the DL SCHEDULING REQUEST message as shown in Figure 6.3.1.1-1, is to request sO-DU to schedule the UE for transmission of the new data or retransmission of the data that is already transmitted on SCell. This message may also be used for releasing the earlier used HARQ process, if pO-DU decides to abort the retransmission, or to extend the slot range for UE scheduling in sO-DU. pO-DU sends asynchronous requests to the sO-DU including the cumulated data size in the *Buffer Length* IE, that may be scheduled by the sO-DU. - -pO-DU may share information for multiple UEs and multiple SCells in a single DL SCHEDULING REQUEST message. - -If the pO-DU triggers DL SCHEDULING REQUEST message for a D2 UE ID before reception of DL DATA REQUIRED message for the same D2 UE ID, it shall set *D2 Sched SN* IE to 0. Otherwise *D2 Sched SN* shall be set to the value of D2 Sched SN received in the latest DL DATA REQUIRED message for the UE from sO-DU. - -![Sequence diagram showing a DL SCHEDULING REQUEST message from PCell O-DU to SCell O-DU.](935075de5250cfe8aa0fb9d65d63dde5_img.jpg) - -``` - -sequenceDiagram - participant PCell O-DU - participant SCell O-DU - Note left of PCell O-DU: - PCell O-DU->>SCell O-DU: DL SCHEDULING REQUEST - Note right of SCell O-DU: - -``` - -Sequence diagram showing a DL SCHEDULING REQUEST message from PCell O-DU to SCell O-DU. - -Figure 6.3.1.1-1: DL scheduling request - -sO-DU may use *D2 UE data size* IE to determine the size of information for each UE, identified by *D2 UE ID* IE, that is received in DL SCHEDULING REQUEST message. - -If the *DT* IE indicates “reTx”: - -- If *HARQCount* IE is not set to zero, *HARQStatus* IE for each *HARQ PID* indicates the cause of HARQ failure. sO-DU shall initiate the retransmission, subject to the allowed range of slots as specified by the *SlotOffset* and *SlotRange* IE, on all the HARQ processes identified by *HARQ PID* for all the SCells that are included in the message and identified by *SCellIndex* IE as defined in 3GPP TS 38.331 clause 6.3.2 [5]. If *clearTB* IE is set to TRUE, sO-DU shall delete the stored MAC TB and reuse the HARQ process for further new data transmission. -- If *HARQCount* IE is received as zero, sO-DU shall consider the received message to increase the range of slots, as specified in *SlotRange* IE, for the retransmission. - -If the *DT* IE indicates “newTx”: - -- If *LCCount* IE is not set to 0, the sO-DU shall determine the SCells using *SCell Bitmap* IE, where data transmission may be scheduled for the UE. *Buffer length* IE shall be used to determine the size of data for each *LCID* that needs to be scheduled in SCells. The sO-DU, if it can schedule the UE within the slots as mentioned in *SlotRange/SlotMask*, shall allocate the HARQ PID and request for PUCCH resources from pO-DU by triggering DL DATA REQUIRED message. -- If *LCCount* IE is received as 0, sO-DU shall interpret the received message to increase the range of slots, as specified in *SlotRange/SlotMask* IE, for UE scheduling of new transmissions. - -If the *DT* IE indicates “Both”: - -- DL SCHEDULING REQUEST message shall contain IEs applicable for both reTx and newTx. -- All the conditions listed above for reTx and newTx shall be applicable. - -In case sO-DU is unable to schedule the UE in allowed slot range, sO-DU shall discard all the DL SCHEDULING REQUEST that were received for this slot range. - -#### 6.3.1.2 DL Data Required - -DL DATA REQUIRED message, as shown in Figure 6.3.1.2-1, is used by sO-DU to request the MAC TB and PUCCH resources from pO-DU in case of successful scheduling of the UEs on SCell. - -This message may encode information about multiple D2 UE ID. pO-DU may use the *D2 UE data size* to determine the size of the received message for each D2 UEID. - -sO-DU shall manage the sequence number per UE. The sequence number shall be incremented by 1 each time a DL DATA REQUIRED message for a UE is sent by the same sO-DU. *D2 Sched SN* IE shall be set to the value of sequence number. - -If *DT* IE is set to “reTx”, sO-DU shall set the *LCCount* to 0 and *LCID* and *Buffer length* IE shall not be included in the message. sO-DU shall not set the *DT* IE as “Both”. - -![Diagram showing a DL DATA REQUIRED message being sent from an SCell O-DU to a PCell O-DU. The PCell O-DU is on the left and the SCell O-DU is on the right. A blue arrow labeled 'DL DATA REQUIRED' points from the SCell O-DU to the PCell O-DU.](343e05a9fd8a8c8743428fa4ae6e2736_img.jpg) - -``` - -graph LR - SCell[SCell O-DU] -- "DL DATA REQUIRED" --> PCell[PCell O-DU] - -``` - -Diagram showing a DL DATA REQUIRED message being sent from an SCell O-DU to a PCell O-DU. The PCell O-DU is on the left and the SCell O-DU is on the right. A blue arrow labeled 'DL DATA REQUIRED' points from the SCell O-DU to the PCell O-DU. - -Figure 6.3.1.2-1: DL data required - -pO-DU shall use the *SCellIndex* IE to identify each SCell where UE is scheduled for transmission with MAC TB of size indicated in *TBSize* IE. *OTA Slot/ SFN*, *HARQ PID* and *PDCCH start symbol* IEs for each of SCell shall be used by pO-DU to allocate the PUCCH resources. If pO-DU encounters any kind of failure (PUCCH resource allocation failure or any other failure), it shall send PUCCH RESOURCE TRANSFER message with *result* IE set to Failure. DL DATA TRANSFER message shall not be sent in this case. - -If *MACCEPresent* IE is set to TRUE, pO-DU shall include all the MAC CEs indicated by *MACCECount* while forming the MAC TB. *MAC CE Length* and *MAC CE Data* IEs indicate the length of MAC CE and MAC CE data. pO-DU shall use “*FV*” IE to identify the MAC CE type, whether fixed length or variable length. MAC TB encoding will be done according to 3GPP TS 38.321[20]. - -If *DT* IE is set to “newTx”: - -- pO-DU shall use the *Buffer Length* IE to determine the size of data for each LC, identified by *LCID*, that is scheduled for transmission. -- *HARQ PID* shall be set as the one allocated by the sO-DU for transmission of the data. - -If *DT* IE is set to “reTx”: - -- *LCID* and *Buffer length* IE shall be considered as not present in the message and next octet shall be read as Extension octet if present. -- *HARQ PID* shall be set as the one that was used during initial transmission and received from pO-DU in DL SCHEDULING REQUEST. - -#### 6.3.1.3 DL Data Transfer - -As shown in Figure 6.3.1.3-1, DL DATA TRANSFER message is used by pO-DU to transfer the MAC TB to sO-DU for transmission to UE on the specified *OTA slot / OTA SFN* corresponding to SCell where data is scheduled in sO-DU. This message contains MAC TB for a UE scheduled on a SCell. If pO-DU encounters any kind of failure (PUCCH resource allocation failure or any other failure), it shall not send DL DATA TRANSFER message. pO-DU may segment the MAC TB into multiple segments depending on the MAC TB size. - -![Sequence diagram showing DL DATA TRANSFER from PCell O-DU to SCell O-DU.](e2b7490a3455c66c85db12872c78fcc3_img.jpg) - -``` - -sequenceDiagram - participant PCell O-DU - participant SCell O-DU - Note left of PCell O-DU: - PCell O-DU->>SCell O-DU: DL DATA TRANSFER - Note right of SCell O-DU: - -``` - -Sequence diagram showing DL DATA TRANSFER from PCell O-DU to SCell O-DU. - -Figure 6.3.1.3-1: DL data transfer - -sO-DU may use the *D2 UE data size* to determine the size of the received message for the UE identified by *D2 UE ID*, for which segments are received. sO-DU uses *D2 Sched SN* and *OTA Slot/OTA SFN* for mapping the DL DATA REQUIRED and DL DATA TRANSFER message on a SCell identified by *SCellIndex*. - -sO-DU shall determine the number of segments belonging to a single MAC TB using *Total Segment count* IE. sO-DU shall concatenate the data mentioned in *TBSegment* IE for each segment to form a MAC TB using *Segment SN*, *Segment Offset* and *Segment Length* IE. - -sO-DU stores the complete MAC TB for retransmission purposes. sO-DU shall delete the MAC TB and reuse the HARQ PID for new transmission in the following conditions: - -- Reception of successful transmission indication (HARQ feedback) from pO-DU -- Reception of *ClearTB* IE set to TRUE from pO-DU. -- If none of the above conditions are met and for new transmission in the following conditions - - *T\_TBClear* timer expires. - -#### 6.3.1.4 PUCCH Resource Transfer - -PUCCH RESOURCE TRANSFER message, as shown in Figure 6.3.1.4-1, is used by pO-DU to share the allocated PUCCH resources with sO-DU. - -![Sequence diagram showing PUCCH RESOURCE TRANSFER from PCell O-DU to SCell O-DU.](0ff19975027a3c5177519975f9af055f_img.jpg) - -``` - -sequenceDiagram - participant PCell O-DU - participant SCell O-DU - Note left of PCell O-DU: - PCell O-DU->>SCell O-DU: PUCCH RESOURCE TRANSFER - Note right of SCell O-DU: - -``` - -Sequence diagram showing PUCCH RESOURCE TRANSFER from PCell O-DU to SCell O-DU. - -Figure 6.3.1.4-1: PUCCH resource transfer - -If information for multiple UEs is encoded in the message as indicated by *D2 UE Count* IE, sO-DU uses the *D2 UE data size* to determine the size of information for each UE identified by *D2 UE ID* for which information is received in PUCCH RESOURCE TRANSFER message. - -*D2 Sched SN*, *OTA Slot/ OTA SFN* is used by sO-DU to map the allocated PUCCH resources for the SCell(s) identified by *SCellIndex* as defined in 3GPP TS 38.331[5] clause 6.3.2, with the corresponding DL DATA REQUIRED message. - -### 6.3.2 UCI Transfer - -As shown in Figure 6.3.2-1, UCI Transfer procedure is used by pO-DU to send the received UCI information from UE to sO-DU. pO-DU shares CSI information or HARQ feedback using UCI TRANSFER message. - -If CSI data for multiple SCells are multiplexed, pO-DU shall parse the CSI information intended for the SCells configured in the sO-DU for the UE as defined in 3GPP TS 38.212[18] clause 6.3.1.1.2. The raw data per cell shall be sent in *CSI Data* IE to sO-DU. - -![Diagram showing the UCI TRANSFER message flow from PCell O-DU to SCell O-DU.](9b9262a549828579ab904148450734f6_img.jpg) - -``` - -sequenceDiagram - participant PCell O-DU - participant SCell O-DU - Note left of PCell O-DU: UE sends UCI to PCell O-DU - PCell O-DU->>SCell O-DU: UCI TRANSFER - Note right of SCell O-DU: sO-DU receives UCI - -``` - -Diagram showing the UCI TRANSFER message flow from PCell O-DU to SCell O-DU. - -Figure 6.3.2-1: UCI transfer - -If information for multiple UEs is encoded in the message as indicated by *D2 UE Count* IE, sO-DU may use *D2 UE data size* to determine the size of information for each of UE identified by *D2 UE ID*. *SCell data size* IE may be used to parse the information for each SCell identified by *SCellIndex* IE. - -If *CSIStatus* is set to “Not Present”, “Failure”, or “DTX”: - -- sO-DU shall consider that CSI data is not present in the UCI TRANSFER message and value of *CSI Data Length* shall be considered as 0. -- Octets containing *CSI Data* IE shall not be present in the message. - -If *CSIStatus* is set to “Present”: - -- sO-DU reads the *CSI Data Length* and interprets the *CSI Data* to determine the reported CQI, RI, L1-RSRP, PMI etc as defined in 3GPP TS 38.213[17] clause 9.2 and 9.3. - -If *HARQCount* is encoded as 0, sO-DU shall interpret that HARQ feedback is not present in the message. Otherwise *HARQCount* specifies the number of HARQ processes for which HARQ feedback is present in the received message. For each HARQ process identified by *HARQ PID* IE, - -If *HARQStatus* is set to “Ack”: - -- sO-DU shall interpret it as successful reception of data by UE. -- sO-DU shall clean up the HARQ process and may use it for further new data transmission for the same UE. *ClearTB* IE is ignored for this scenario. - -If *HARQStatus* is set to “DTX” or “Nack”: - -- sO-DU shall handle the received negative HARQ feedback. -- If *ClearTB* IE is set to TRUE, sO-DU deletes the TB and shall use the *HARQ PID* for the new data transmission with toggled NDI bit. -- If *ClearTB* is set to FALSE, sO-DU shall continue storing data and start the *T\_ClearTB* timer. sO-DU waits for DL SCHEDULING REQUEST for triggering the retransmission. On reception of DL SCHEDULING REQUEST *T\_ClearTB* timer shall be stopped. - -If DL SCHEDULING REQUEST indicating retransmission request is not received until expiry of T\_ClearTB timer, sO-DU deletes the TB and shall use the HARQ PID for the new data transmission with toggled NDI bit. - -## 6.4 Elements of D2UP Communication - -### 6.4.1 General - -In the present document the structure of D2UP frames is specified by using figures similar to Figure 6.4.1-1. - -| Bits | | | | | | | | Octets | | | | | | | | -|-------------------|---|---|---|--------------|---------|---|---|--------|--|--|--|--|--|--|--| -| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | | -| Field 1 | | | | Field 2 | | | | 1 | | | | | | | | -| Field 3 | | | | | Field 4 | | | | | | | | | | | -| Field 4 continues | | | | spare | | | | | | | | | | | | -| spare | | | | Field 5 | | | | | | | | | | | | -| Field 6 | | | | | | | | | | | | | | | | -| Field 6 continues | | | | Padding bits | | | | | | | | | | | | -| Future extension | | | | | | | | | | | | | | | | -| padding | | | | | | | | | | | | | | | | - -Figure 6.4.1-1: Example frame format for D2UP - -Unless otherwise indicated, fields which consist of multiple bits within an octet have the most significant bit located at the highest bit position of the field (according to the bit numbers indicated above frame in Figure 6.4.1-1). In addition, if a field spans several octets, most significant bits are located in lower numbered octets (right of frame in Figure 6.4.1-1). - -The frame is transmitted starting from the lowest numbered octet. Within each octet, the bits are sent according to decreasing bit position (bit position 7 first). - -Bits labelled "Spare or Reserved" should be set to "0" by the sender and should not be checked by the receiver. - -The header part of the frame is always an integer number of octets. The payload part is octet aligned (by adding 'Padding Bits' when needed). The total size of the frame shall not exceed 1018 octets (see TS 29.281 [19]). - -The receiver should be able to remove an additional Future Extension field that may be present. See description of Future Extension field in A.1. - -### 6.4.2 Message Format for the D2UP - -All D2-u messages begin with a common header as shown in Figure 6.4.2-1. - -| Bits | | | | | | | | Number of octets | -|------|---|---|---|----------------|---|---|---|------------------| -| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | -| PV | | | | Application ID | | | | 1 | - -| | | -|--------------|---| -| Message Type | 1 | -|--------------|---| - -Figure 6.4.2-1: D2-u header - -#### 6.4.2.1 DL SCHEDULING REQUEST - -This message format is used by pO-DU to sO-DU to request DL scheduling for a UE(s). It also conveys the information of allowed slots where UE can be scheduled in SCell(s). - -This message also can be used to increase the range of slots where UE can be scheduled in SCell - -This message is used to request both new data scheduling and for re-transmission scheduling on sO-DU. - -*SCellCount* and *SCellIndex* IEs in octet 8 are relevant only for retransmission scenarios. These fields shall not be considered for new transmission. - -IEs listed in octets 13-24 or 28 are related to new transmission of the data. If DT is set to “newTx” or “Both”, Octets 13 - 23 shall be present in the message and convey information associated for new data transmission requests. These octets are not present otherwise. - -IEs listed in octets 8-12 except DT IE, are related to re-transmission of the data. If DT is set to “reTx” or “Both”, octets 8-12 shall be present in the message and convey information associated for HARQ status and retransmission requests. These octets are not present, otherwise. - -If *SlotType* IE is set to 1, bits 0-3 in the same octet and the next 4 octets shall be considered for indicating the SlotMask. If SlotType is set to 0, bits 0-3 in the octet shall be reserved and next octet (1 octet) shall be used to determine the range of slots. - -*SlotOffset/SlotRange/SlotMask* IEs received in latest DL SCHEDULING REQUEST shall be applied immediately. Slot configuration received in earlier DL SCHEDULING REQUEST shall be overwritten with the newly received one. - -Figure 6.4.2.1-1 shows the message format for DL SCHEDULING REQUEST message - -| Bits | | | | | | | | Number of octets | Octet No | | | | -|--------------------|------------|---|-----------|-------------------|----|---------|---|------------------|-------------|--|--|--| -| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | -| D2 UE Count | | | | | | | | 1 | 1 | | | | -| D2 UE ID | | | | | | | | 2 | 2 | | | | -| D2 Sched SN | | | | | | | | 2 | 4 | | | | -| D2 UE data size | | | | | | | | 2 | 6 | | | | -| DT | SCellCount | | | | E1 | | | 1 | 8 | | | | -| SCellIndex | | | | | | | | 1 | 9 | | | | -| SlotOffset | | | SlotRange | | | | | 1 | 10 | | | | -| HARQCount | | | | R | R | R | R | 1 | 11 | | | | -| HARQ PID | | | | HARQStatus | | ClearTB | | 1 | 12 | | | | -| SlotType | SlotOffset | | | Reserved/SlotMask | | | | 1 | 13 | | | | -| SlotRange/SlotMask | | | | | | | | 1 or 4 | 14 or 14-17 | | | | - -| | | | | | | -|------------------|----|---|---|---|----------------| -| SCell Bitmap | | | | 4 | 15-18 or 18-21 | -| LCCount | E2 | R | R | 1 | 19 or 22 | -| LCID | | | | 1 | 20 or 23 | -| Buffer Length | | | | 3 | 21-24 or 24-26 | -| Extension Octet1 | | | | 1 | 24 or 27 | -| Extension Octet2 | | | | 1 | 25 or 28 | - -Figure 6.4.2.1-1: DL SCHEDULING REQUEST message format - -#### 6.4.2.2 DL DATA REQUIRED - -sO-DU uses this message format to request MAC TB and/or PUCCH resources for the transmission on a SCell in response to a DL SCHEDULING REQUEST message. - -Figure 6.4.2.2-1 shows the DL DATA REQUIRED message - -| Bits | | | | | | | | Number of octets | | | | | | | | -|--------------------|-------------|---------|---|----|---|--------------------|---------|------------------|--|--|--|--|--|--|--| -| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | | -| D2 UE Count | | | | | | | | 1 | | | | | | | | -| D2 UE ID | | | | | | | | 2 | | | | | | | | -| D2 Sched SN | | | | | | | | 2 | | | | | | | | -| TotalPendingBO | | | | | | | | 4 | | | | | | | | -| D2 UE data size | | | | | | | | 2 | | | | | | | | -| SCellCount | | | | E1 | R | R | | 1 | | | | | | | | -| SCellIndex | | | | | | | | 1 | | | | | | | | -| TBSize | | | | | | | | 3 | | | | | | | | -| MACCE Present | MACCECount | | | | R | R | R | 1 | | | | | | | | -| FV | MACCELength | | | | | | | 1 | | | | | | | | -| MAC CE Data | | | | | | | | MACCElength | | | | | | | | -| OTA SFN | | | | | | | | 1 | | | | | | | | -| OTA SFN | OTA Slot | | | | | | | 1 | | | | | | | | -| OTA Slot | HARQ PID | | | | | PDCCH Start Symbol | | 1 | | | | | | | | -| PDCCH Start Symbol | Curr MCS | | | | | | Curr RI | 1 | | | | | | | | -| Curr RI | DT | LCCount | | | | | | 1 | | | | | | | | -| LCID | | | | | | | | 1 | | | | | | | | -| Buffer Length | | | | | | | | 3 | | | | | | | | - -| | | -|-----------------|---| -| Extension Octet | 1 | -|-----------------|---| - -Figure 6.4.2.2-1: DL DATA REQUIRED message format - -#### 6.4.2.3 DL DATA TRANSFER - -Message format shown in Figure 6.4.2.3-1 is used by pO-DU to share the MAC TB as requested by sO-DU in DL DATA REQUIRED message. This format is used for new data transmission. - -| Bits | | | | | | | | Number of octets | | | -|---------------------|----------|---|---|---|---|---|---|------------------|--|--| -| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | -| D2 UE data size | | | | | | | | 2 | | | -| D2 UE ID | | | | | | | | 2 | | | -| D2 Sched SN | | | | | | | | 2 | | | -| SCellIndex | | | | | | | | 1 | | | -| OTA SFN | | | | | | | | 1 | | | -| OTA SFN | OTA Slot | | | | | | | 1 | | | -| OTA Slot | E1 | R | R | R | R | | | 1 | | | -| TBSize | | | | | | | | 3 | | | -| Total Segment count | | | | | | | | 1 | | | -| Segment SN | | | | | | | | 1 | | | -| Segment Offset | | | | | | | | 3 | | | -| Segment Length | | | | | | | | 2 | | | -| TBSegment | | | | | | | | n | | | -| Extension Octet | | | | | | | | 1 | | | - -Figure 6.4.2.3-1: DL DATA TRANSFER message format - -#### 6.4.2.4 PUCCH RESOURCE TRANSFER - -Message format in Figure 6.4.2.4-1 is used by pO-DU to transfer the allocated PUCCH resources to sO-DU in response of DL DATA REQUIRED message. sO-DU shall use the information while encoding the DCI message to send to the UE for scheduling DL data. - -If PUCCH allocation in pO-DU is not successful in response to a DL DATA REQUIRED message for a D2 UE ID, the result field shall be set as “Failure” and subsequent fields may be filled with 0 by pO-DU. sO-DU shall ignore these fields. - -| Bits | | | | | | | | Number of octets | -|-------------|---|---|---|---|---|---|---|------------------| -| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | -| D2 UE Count | | | | | | | | 1 | - -| | | | | -|-----------------|------------|------|---| -| D2 UE ID | | | 2 | -| D2 Sched SN | | | 2 | -| D2 UE data size | | | 2 | -| OTA SFN | | | 1 | -| OTA SFN | OTA Slot | | 1 | -| OTA Slot | SCellCount | E1 | 1 | -| SCellIndex | | | 1 | -| Result | cDAI | K1 | 1 | -| PUCCH Rsrc Ind | | tDAI | 1 | -| Extension Octet | | | 1 | - -Figure 6.4.2.4-1: PUCCH RESOURCE TRANSFER message format - -#### 6.4.2.5 UCI TRANSFER - -UCI Transfer message format as shown in Figure 6.4.2.5-1 is used by pO-DU to send the received CSI or HARQ feedback information from UE which are intended for sO-DU. - -This message format is also used to clear the HARQ process and stored TB in sO-DU if PCell aborts the retransmission in sO-DU. - -| Bits | | | | | | | | Number of octets | | | | | -|-----------------|---|-----------------|---|------------|---|---------|---|------------------|--|--|--|--| -| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | -| D2 UE Count | | | | | | | | 1 | | | | | -| D2 UE ID | | | | | | | | 2 | | | | | -| D2 UE data size | | | | | | | | 2 | | | | | -| ScellCount | | | | E1 | | R | | 1 | | | | | -| ScellIndex | | | | | | | | 1 | | | | | -| SCell data size | | | | | | | | 1 | | | | | -| CSIStatus | | CSI Data Length | | | | | | 1 | | | | | -| CSI Data | | | | | | | | CSI Data Length | | | | | -| HARQCount | | | | R | | R | | 1 | | | | | -| HARQ PID | | | | HARQStatus | | ClearTB | | 1 | | | | | -| HARQ PID | | | | HARQStatus | | ClearTB | | 1 | | | | | -| Extension Octet | | | | | | | | 1 | | | | | - -Figure 6.4.2.5-1: UCI TRANSFER message format - -### 6.4.3 Coding of information elements in frames - -#### 6.4.3.1 PV: Protocol version - -**Description:** Protocol version indicates the D2-u protocol version. In the present document, version 1 is used. - -**Value range:** 1-15. 0 is reserved. - -**Field length:** 4 bits - -#### 6.4.3.2 Application ID - -**Description:** Indicates the application that is using the D2 interface. In the present document, D2 interface is used for supporting Inter O-DU CA. - -**Value range:** 1-15. 0 is reserved. 1 is defined for Inter O-DU CA. - -**Field length:** 4 bits - -#### 6.4.3.3 Message Type - -**Description:** Indicates the D2-U message IDs as mentioned in . - -**Value Range:** 0-255 - -**Field Value:** Table 6.4.3.3-1 below defines all the message type defined for D2-u. - -**Table 6.4.3.3-1: Message ID** - -| Message ID | Name | -|------------|-------------------------| -| 1 | DL SCHEDULING REQUEST. | -| 2 | DL DATA REQUIRED | -| 3 | DL DATA TRANSFER | -| 4 | PUCCH RESOURCE TRANSFER | -| 5 | UCI TRANSFER | -| 0 & 6-255 | Reserved | - -#### 6.4.3.4 D2 UE Count - -**Description:** Indicates the number of D2 UE IDs for which information is encoded in a message. - -**Value range:** 1-255. - -**Field length:** 8 bits - -#### 6.4.3.5 D2 UE ID - -**Description:** Unique number to identify the UE in the pO-DU and sO-DU. pO-DU assigns D2 UE ID to a UE using UE ADDITION REQUEST message and it does not change until UE is released. - -**Value range:** 0-65535 - -**Field length:** 16 bits - -#### 6.4.3.6 D2 Sched SN - -**Description:** Sequence number per UE which is generated by sO-DU for each DL DATA REQUIRED message. pO-DU returns the same value in each of the DL DATA TRANSFER and PUCCH RESOURCE TRANSFER messages associated with DL DATA REQUIRED message. DL SCHEDULING REQUEST message encodes the D2 Sched SN as the one last received in DL DATA REQUIRED message. - -**Value range:** 1-65535. 0 is used in DL SCHEDULING REQUEST message when it is sent before receiving any DL DATA REQUIRED message. - -**Field length:** 16 bits - -#### 6.4.3.7 D2 UE data size - -**Description:** Indicates the size of information in octets or bytes for each UE received that is encoded in D2 message . - -**Value range:** 1-9000 - -**Field length:** 16 bits - -#### 6.4.3.8 SCellCount - -**Description:** Count of SCells for which information is encoded in the message - -**Value range:** 1-15 - -**Field length:** 4 bits - -#### 6.4.3.9 SCellIndex - -**Description:** Index of SCell as defined in 3GPP TS 38.331 clause 6.3.2[5]. - -**Value range:** 1-31 - -**Field length:** 8 bits - -#### 6.4.3.10 SCellBitmap - -**Description:** Each bit indicates the SCellIndex of the cell where UE is allowed to be scheduled for inter O-DU CA in sO-DU. Bit position indicates the SCellIndex as defined in 3GPP TS 38.331 clause 6.3.2[5]. For example bit position 0 is for PCell. Bit Position 1 indicates SCell with SCellIndex 1 and so on. Value at the bit position indicates whether a UE is allowed to be scheduled on the SCell or not. - -Bit value 1: UE is allowed to be scheduled on the SCell with SCellIndex as bit position. - -Bit value 0: UE is not allowed to be scheduled on the SCell with SCellIndex as bit position. - -**Value range:** 0x00000002 – 0xffffffe. - -**Field length:** 32 bits - -#### 6.4.3.11 SlotType - -**Description:** Indicates if SlotRange or SlotMask is encoded for UE scheduling in sO-DU. If SlotType indicates presence of SlotRange, the least significant four bits in the octet carrying SlotType are reserved. - -0: indicates that SlotRange is configured . SlotRange is defined in section 6.4.3.13. - -1: indicates that SlotMask is configured for UE scheduling. SlotMask is 36 bit field as defined in section 6.4.3.14 - -**Value range:** 0-1 - -**Field length:** 1 bit - -#### 6.4.3.12 SlotOffset - -**Description:** Indicates the slot offset for UE scheduling with respect to receiver slot. sO-DU shall schedule UE after slot offset only. If value received is 0, it means, UE shall be considered for scheduling from next slot onwards. This is set as per the highest sub carrier spacing among all the SCells configured for the UE in sO-DU. - -**Value range:** 0-7 - -**Field length:** 3 bits - -#### 6.4.3.13 SlotRange - -**Description:** Continuous range of slots in SCell starting from SlotOffset where UE can be scheduled by the sO-DU. This is configurable parameter. This is set as per the highest sub carrier spacing among all the SCells configured for the UE in sO-DU. - -**Value range:** 1-50 ( for new transmission) and 1- 31(for retransmission) - -**Field length:** 5 bits for retransmission and 8 bits for new transmission. - -#### 6.4.3.14 SlotMask - -**Description:** Indicates the slots starting from SlotOffset where UE can be scheduled in SCell. Either Slot Range or Slot Mask will be present which is indicated by Slot Type. Each bit indicates the slot where UE can be scheduled by sO-DU. This is set as per the highest sub carrier spacing among all the SCells configured for the UE in sO-DU. - -EXAMPLE 1: SlotOffset = 0, SlotMask = 0x01 indicates UE can be scheduled in SCell only in next slot in which the message is received. - -EXAMPLE 2: SlotOffset = 1, SlotMask = 0x01 indicates that UE can only be scheduled in SCell in slot number 2 if message is received in slot #0. - -EXAMPLE 3: SlotOffset = 1, SlotRange = 10 indicates that UE can only be scheduled in SCell from slot number 2 until slot number 12, if message is received in slot #0. - -**Value range:** 1-36 - -**Field length:** 36 bits - -#### 6.4.3.15 TotalPendingBO - -**Description:** Indicates the total pending BO at the sO-DU per UE basis. This field contains the value of total BO pending at the sO-DU while sending the DL DATA REQUIRED message. Total pending BO will be calculated in sO-DU based on the BO received in latest DL SCHEDULING REQUEST. Size of scheduled data will be subtracted from this BO while calculating the TotalPendingBO. Primary O-DU may use this information to determine the pending data size in sO-DU. 0xFFFFFFFF indicates that field TotalPendingBO information is not encoded by sO-DU hence does not contain a valid value to be used. - -**Value range:** 0- 0xFFFFFFFF - -**Field length:** 32 bits - -#### 6.4.3.16 TBSize - -**Description:** Indicates the total MAC TB size scheduled for transmission by SCell in a sO-DU. pO-DU shall form the TB of size indicated by TBSize and send it to sO-DU. If MAC CE Data is present, it shall be included while forming the MAC TB for transmission. - -**Value range:** 1- 600000 bytes. All other values are reserved. - -**Field length:** 24 bits - -#### 6.4.3.17 MACCEPresent - -**Description:** Flag indicates whether MAC CE is present in the message or not. - -MACCEPresent = 0 : MAC CE field is not present. - -MACCEPresent = 1: MAC CE field is present. - -**Value range:** 0-1 - -**Field length:** 1 bit - -#### 6.4.3.18 MACCECount - -**Description:** This field indicates the number of MAC CEs that are present in the message. These MAC CEs are used by pO-DU while forming the TB as per the TBSize sent by sO-DU. value 0 means, MAC CE is not present in the message. - -**Value range:** 0-15 - -**Field length:** 4 bits - -#### 6.4.3.19 FV - -**Description:** Flag indicating whether MAC CE is of fixed length or variable length. - -NOTE: pO-DU uses this information when forming the MAC TB in accordance with 3GPP MAC TS 38.321[20] - -FV = 0 : Fixed length MAC CE. - -FV = 1 : Variable length MAC CE - -**Value range:** 0-1 - -**Field length:** 1 bit - -#### 6.4.3.20 MACCELength - -**Description:** Indicates the length of MAC CE field in bytes. - -**Value range:** 1-127 - -**Field length:** 7 bits - -#### 6.4.3.21 MACCEData - -**Description:** Data containing the MAC CE of size MACCELength. - -**Field length:** As per MACCELength - -#### 6.4.3.22 OTA SFN - -**Description:** Sub frame number where PDCCH transmission is scheduled for UE by sO-DU with respect to a given SCell. - -**Value range:** 0 - 1023 - -**Field length:** 10 bit - -#### 6.4.3.23 OTA Slot - -**Description:** Slot number where PDCCH transmission is scheduled for UE by sO-DU with respect to a given SCell. - -**Value range:** 0-160. All other values are reserved. - -**Field length:** 8 bits - -#### 6.4.3.24 PDCCH Start Symbol - -**Description:** Start symbol of PDCCH where DCI is scheduled for a UE by a SCell of a sO-DU. This information is used by pO-DU while allocating the PUCCH resources for SCells. - -**Value range:** 0-13. 14 and 15 is reserved value. - -**Field length:** 4 bits - -#### 6.4.3.25 CurrRI - -**Description:** Rank Indicator used in the SCell of the sO-DU for the UE where UE is scheduled. - -**Value range:** 0-7. 0 indicates that RI is 8. - -**Field length:** 3 bits - -#### 6.4.3.26 CurrMCS - -**Description:** MCS used in the SCell of the sO-DU for the UE where UE is scheduled. - -**Value range:** 0-28 - -**Field length:** 5 bits - -#### 6.4.3.27 DT: Data Type - -**Description:** Indicates Whether message contains information for new data transmission or for retransmission or for both. - -DT= 0 : newTx - -DT=1: reTx - -DT=2: Both. It means message contains information for both new transmission as well as for retransmission. This value cannot be encoded in DL DATA REQUIRED message. - -**Value range:** 0-2. 3 is reserved in present document. - -**Field length:** 2 bits - -#### 6.4.3.28 LCCount - -**Description:** This field indicates the number of logical channels (LCs) for which information is encoded in the message. - -**Value range:** 0-15. - -**Field length:** 4 bits - -#### 6.4.3.29 LCID - -**Description:** Indicates the logical channel identity for which information is encoded in the message. This is same ID as defined in 3GPP TS 38.321[20] clause 6.2.1 - -**Value range:** as specified in 3GPP TS 38.321 [20] clause 6.2.1. - -**Field length:** 8 bits - -#### 6.4.3.30 Buffer Length - -**Description:** Indicates the length of buffer in octets for each LCID that can be scheduled on SCell(s). - -**Value range:** 1- 1200000 - -**Field length:** 24 bits - -#### 6.4.3.31 Total Segment Count - -**Description:** Indicates the total number of D2 segments that are formed out of MAC TB as specified by TBSize in DL DATA REQUIRED message. - -**Value range:** 1-255 - -**Field length:** 8 bits - -#### 6.4.3.32 Segment SN - -**Description:** Sequence number of D2 message that contains the segments of a MAC TB if it was segmented by pO-DU. - -**Value range:** 1- Total Segment Count - -**Field length:** 8 bits - -#### 6.4.3.33 Segment Offset - -**Description:** Indicates the offset in octets of received D2 segment in the MAC TB to form the complete TB. - -**Value range:** 1- 600000 - -**Field length:** 24 bits - -#### 6.4.3.34 Segment Length - -**Description:** it is the number of octets in a segment encoded in TBSegment field. - -**Value range:** 1- 9000 - -**Field length:** 16 bits - -#### 6.4.3.35 TBSegment - -**Description:** Field containing MAC TB segment that is scheduled for transmission on SCell. - -**Field length:** Segment Length bytes - -#### 6.4.3.36 Result - -**Description:** Indicates the status of PUCCH allocation by pO-DU. On reception of DL DATA REQUIRED messages, if pO-DU is unable to allocate PUCCH resources or due to any other failure, unable to send data to sO-DU, result flag can be set to false. sO-DU will not transmit to the UE in corresponding SCell on the OTA SFN/Slot. - -Result = 1: PUCCH allocation is successful - -Result = 0 – Failure at pO-DU hence no data transmission to the UE in corresponding SCell on the OTA SFN/Slot. Other values are reserved in the present document. - -**Value range:** 0-1 - -**Field length:** 2 bits - -#### 6.4.3.37 cDAI: counter Downlink Assignment Index - -**Description:** Indicates the counter downlink assignment index as defined in 3GPP TS 38.213[17] clause 9.1.3 that need to be encoded in DCI message. - -**Value range:** 0- 4 - -**Field length:** 3 bits - -#### 6.4.3.38 tDAI: Total Downlink Assignment Index - -**Description:** Indicates the total downlink assignment index as defined in 3GPP TS 38.213[17] clause 9.1.3 on the OTA slot/SFN. This information is sent to UE in DCI message. - -**Value range:** 0- 4 - -**Field length:** 3 bits - -#### 6.4.3.39 K1 - -**Description:** Indicates the slot difference between PDSCH reception and PUCCH transmission by the UE as defined in 3GPP TS 38.213[17] clause 9.2.3. - -**Value range:** 1-8 - -**Field length:** 3 bits - -#### 6.4.3.40 PUCCH Rsrc Ind - -**Description:** PUCCH Resource indication as defined in 3GPP TS 38.213[17] clause 9.2.3. - -**Field length:** 5 bits - -#### 6.4.3.41 SCell data size - -**Description:** indicates the size of control data in octet or bytes for each SCell. - -**Field length:** 8 bits - -#### 6.4.3.42 HARQCount - -**Description:** This field indicates the number of HARQ processes for which information is encoded in the message. - -**Value range:** 0- 15. - -**Field length:** 4 bits - -#### 6.4.3.43 HARQ PID - -**Description:** Indicates the HARQ PID as defined in 3GPP TS 38.212 [18] clause 7.3.1.2, for which information is encoded in the message. . HARQ PID is not released until MAC TB is successfully received by the UE or retransmission is aborted. - -**Value range:** 0-15 - -**Field length:** 4 bits - -#### 6.4.3.44 HARQStatus - -**Description:** Indicates the HARQ feedback status. It can be ACK, NACK, DTX depending on received feedback from UE or if nothing is received on the scheduled slot. - -HARQStatus = 0 (ACK) - -HARQStatus = 1 (NACK) - -HARQStatus = 2 (DTX) - -**Value range:** 0-2 - -**Field length:** 2 bits - -#### 6.4.3.45 ClearTB - -**Description:** Flag indicates to sO-DU if stored TB for HARQ PID has to be cleared. pO-DU sets the value to 1 on reception of HARQ ACK or in case of aborting the retransmission on the SCell. - -ClearTB = 1 : Delete the MAC TB stored in sO-DU and clear the HARQ PID. - -ClearTB = 0 : MAC TB continued to be stored in sO-DU. - -**Value range:** 0-1. - -**Field length:** 2 bits - -#### 6.4.3.46 CSIStatus - -**Description:** Indicates the status of CSI data in the D2 message. - -CSIStatus = 0 : Success, CSI data is present. - -CSIStatus = 1 : CRC failure or CSI decoding failure. In this case CSI Length is set to 0 and CSI data is not present. - -CSIStatus = 2 : DTX at the OTA Slot/SFN where CSI data was scheduled. In this case CSI Length is set to 0 and CSI data is not present. - -**Value range:** 0-2 - -**Field length:** 2 bits - -#### 6.4.3.47 CSI Data Length - -**Description:** Indicates the length of CSI data in octets or bytes in the D2 message for specified SCell of a D2 UE ID. - -**Value range:** 0- 63 bytes. - -**Field length:** 6 bits - -#### 6.4.3.48 CSI Data - -**Description:** The raw CSI data for the SCell as received from UE containing information such as CQI, CRI, RI, PMI information as defined in 3GPP TS 38.213[17] clause 9.2.5. - -**Field length:** CSI Data Length bytes - -#### 6.4.3.49 E1 - -**Description:** This bit indicates the presence of extension octet in all the messages. - -E1 = 0: Extension octet is not present in the message. - -E1 = 1 : Extension Octet ( In DL SCHEDULING REQUEST, Extension Octet 1) field per UE per SCell is present in the message - -E1 = 2 : Extension Octet ( In DL SCHEDULING REQUEST, Extension Octet 1) field per UE is present in the message - -**Field length:** 2bits - -#### 6.4.3.50 E2 - -**Description:** This field indicates the presence of extension octet2 in D2 messages. This is per UE information. - -E2 =0: Extension octet2 is not present in the message. - -E2 =1: Extension Octet2 is present. - -**Field length:** 2 bits - -#### 6.4.3.51 Extension Octet/ Extension Octet1/ Extension Octet2 - -**Description:** This is an octet which can be used in future if any extension is required in the message. Its present is decided by E1/E2 field. - -**Field length:** 8 bits - -# Annex A (informative): Examples for DL SCHEDULING REQUEST - -## A.1: New Data transmission: - -Figure A.1-1 mentions the fields that shall be present if DT is set to newTx. Following are the assumptions in this example: - -- In this example, information for 2 UEs are encoded with D2 UE ID as 1 and 2. -- First scheduling request for D2 UE ID 1 is sent before reception of DL DATA REQUIRED from sO-DU. For D2 UE ID 2, it is assumed that DL DATA REQUIRED with D2 Sched SN =1 is received. -- There is single SCell present for the D2 UE ID 1 in sO-DU and SCellIndex is 1 for the SCell. -- There are 2 SCells configured in sO-DU for D2 UE ID 2 with SCellIndex 1 and 2 for each of the SCell. -- SlotType is set to SlotRange for both the UEs. -- Each UE has 1 logical channel configured with LCID =4. - -| Bits | | | | | | | | No Of Octets | | | | | | | | | | | -|---------------------------|---------------|----------------|---|----------|-------|---|---|--------------|--|--|--|--|--|--|--|--|--|--| -| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | | | | | -| D2 UE Count =2 | | | | | | | | 1 | | | | | | | | | | | -| D2 UE ID =1 | | | | | | | | 2 | | | | | | | | | | | -| D2 Sched SN = 0 | | | | | | | | 2 | | | | | | | | | | | -| D2 UE data size =12 | | | | | | | | 2 | | | | | | | | | | | -| DT = 0 | | SCellCount = 0 | | | E1 =0 | | | 1 | | | | | | | | | | | -| SlotType = 0 | SlotOffset =2 | | | Reserved | | | | 1 | | | | | | | | | | | -| SlotRange | | | | | | | | 1 | | | | | | | | | | | -| SCell Bitmap = 0x00000001 | | | | | | | | 4 | | | | | | | | | | | - -| | | | | | | | | | | | -|---------------------------|---------------|----------|-------|---|---|--|--|--|--|--| -| LCCount =1 | | E2 =0 | R | R | 1 | | | | | | -| LCID = 4 | | | | | 1 | | | | | | -| Buffer Length = x | | | | | 3 | | | | | | -| D2 UE ID =2 | | | | | 2 | | | | | | -| D2 Sched SN = 1 | | | | | 2 | | | | | | -| D2 UE data size =12 | | | | | 2 | | | | | | -| DT = 0 | SCellCount =0 | | E1 =0 | | 1 | | | | | | -| SlotType = 0 | SlotOffset =2 | Reserved | | | 1 | | | | | | -| SlotRange | | | | | 1 | | | | | | -| SCell Bitmap = 0x00000011 | | | | | 4 | | | | | | -| LCCount =1 | | E2 =0 | R | R | 1 | | | | | | -| LCID = 4 | | | | | 1 | | | | | | -| Buffer Length =y | | | | | 3 | | | | | | - -Figure A.1-1: DL SCHEDULING REQUEST with newTx with SlotType as SlotRange - -NOTE: Buffer Length x and y in the above table indicates the size of data that can be scheduled in SCells as mentioned in SCell Bitmap for the UE configured in sO-DU. - -Following are the assumptions in Figure A.1-2 for newTx: - -- In this example, information for 2 UEs are encoded with D2 UE ID as 1 and 2. -- Scheduling request for D2 UE ID 1 is sent before reception of DL DATA REQUIRED from sO-DU. For D2 UE ID 2, it is assumed that DL DATA REQUIRED with D2 Sched SN =1 is received. -- There is single SCell present for the D2 UE ID 1 in sO-DU and SCellIndex is 1 for the SCell. -- There are 2 SCells configured in sO-DU for D2 UE ID 2 with SCellIndex 1 and 2 for each of the SCell. -- SlotType is set to SlotMask for both the UEs. -- Each UE has 1 logical channel configured with LCID =4. - -| Bits | | | | | | | | No Of Octets | -|---------------------|----------------|---|---|-------|---|---|---|--------------| -| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | -| D2 UE Count =2 | | | | | | | | 1 | -| D2 UE ID =1 | | | | | | | | 2 | -| D2 Sched SN = 0 | | | | | | | | 2 | -| D2 UE data size =15 | | | | | | | | 2 | -| DT = 0 | SCellCount = 0 | | | E1 =0 | | | | 1 | - -| | | | | | | | -|---------------------------|---------------|----------|---|---|--|--| -| SlotType = 1 | SlotOffset =2 | SlotMask | | 1 | | | -| SlotMask | | | | 4 | | | -| SCell Bitmap = 0x00000001 | | | | 4 | | | -| LCCount =1 | E2 =0 | R | R | 1 | | | -| LCID =4 | | | | 1 | | | -| Buffer Length =x | | | | 3 | | | -| D2 UE ID =2 | | | | 2 | | | -| D2 Sched SN = 1 | | | | 2 | | | -| D2 UE data size = 15 | | | | 2 | | | -| DT = 0 | SCellCount =0 | E1 =0 | | 1 | | | -| SlotType = 0 | SlotOffset =2 | SlotMask | | 1 | | | -| SlotMask | | | | 4 | | | -| SCell Bitmap = 0x00000003 | | | | 4 | | | -| LCCount =1 | E2 =0 | R | R | 1 | | | -| LCID =4 | | | | 1 | | | -| Buffer Length =y | | | | 3 | | | - -Figure A.1-2: DL SCHEDULING REQUEST with newTx with SlotType as SlotMask - -NOTE: Buffer Length x and y in the above table indicates the size of data that can be scheduled in SCells as mentioned in SCell Bitmap for the UE configured in sO-DU. - -## A.2: Retransmission - -Figure A.2-1 indicates the fields that shall be present if DT is set to reTx . Following are the assumptions in this example: - -- Information for 2 UEs are encoded with D2 UE ID as 1 and 2. -- There is single SCell present for both the UEs with SCellIndex = 1. -- Each UE has status of 2 HARQ processes with PID 1 and 2. -- For UE 1, status is Nack for both the HARQ PIDs. For PID 1, ClearTB is set while for other it is not set. -- For UE 2, status for HARQ PID 1 is Ack while for HARQ PID 2 it is Nack with ClearTB not set. - -| Bits | | | | | | | | No Of Octets | -|----------------|---|---|---|---|---|---|---|--------------| -| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | -| D2 UE Count =2 | | | | | | | | 1 | - -| | | | | | | | | | | | | -|---------------------|----------------|---|-------------|-------|--|---|--|--|--|--|--| -| D2 UE ID=1 | | | | | | 2 | | | | | | -| D2 Sched SN | | | | | | 2 | | | | | | -| D2 UE data size = 6 | | | | | | 2 | | | | | | -| DT = 1 (reTx) | SCellCount = 1 | | | E1 =0 | | 1 | | | | | | -| SCellIndex = 1 | | | | | | 1 | | | | | | -| SlotOffset | SlotRange | | | | | 1 | | | | | | -| HARQCount =2 | R | R | R | R | | 1 | | | | | | -| HARQ PID =1 | HARQStatus = 1 | | ClearTB =1 | | | 1 | | | | | | -| HARQ PID =2 | HARQStatus = 1 | | ClearTB =0 | | | 1 | | | | | | -| D2 UE ID=2 | | | | | | 2 | | | | | | -| D2 Sched SN | | | | | | 2 | | | | | | -| D2 UE data size = 6 | | | | | | 2 | | | | | | -| DT = 1 (reTx) | SCellCount = 1 | | | E1 =0 | | 1 | | | | | | -| SCellIndex = 1 | | | | | | 1 | | | | | | -| SlotOffset | SlotRange | | | | | 1 | | | | | | -| HARQCount = 2 | R | R | R | R | | 1 | | | | | | -| HARQ PID =1 | HARQStatus = 0 | | ClearTB = 1 | | | 1 | | | | | | -| HARQ PID =2 | HARQStatus = 1 | | ClearTB = 0 | | | 1 | | | | | | - -Figure A.2-1: DL SCHEDULING REQUEST for retransmission - -## A.3: New Data transmission and retransmission (Both) - -Figure A.3-1 indicates the fields that shall be present if DT is set to Both. Following are the assumptions in this example: - -- Information for 2 UEs are encoded with D2 UE ID as 1 and 2. -- For D2 UE ID 1 scheduling request is sent before reception of DL DATA REQUIRED from sO-DU. For D2 UE ID 2, it is assumed that DL DATA REQUIRED with D2 Sched SN =1 is received. -- There are 2 SCells with SCellIndex 1 and 2 configured in sO-DU for both the UEs. -- There are one Logical channel encoded for each UE with LCID = 4. -- For D2 UE ID 1, SCellIndex 1 is containing the retransmission information while SCellIndex 2 is containing the information for new transmission. -- For D2 UE ID 2, both the SCells has retransmission data while SCellIndex 1 is having new transmission data information as well. -- SlotType is set to SlotRange for both the D2 UE ID 1 and SlotType is set to SlotMask for D2 UE ID 2. - -| Bits | | | | | | | | Number of Octets | | | | | | | | | | -|---------------------------|----------------|---|-----------|----------------|---|-------------|---|------------------|--|--|--|--|--|--|--|--|--| -| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | | | | | | | | | | | -| D2 UE Count = 2 | | | | | | | | 1 | | | | | | | | | | -| D2 UE ID =1 | | | | | | | | 2 | | | | | | | | | | -| D2 Sched SN | | | | | | | | 2 | | | | | | | | | | -| D2 UE data size = 16 | | | | | | | | 2 | | | | | | | | | | -| DT = 2 (Both) | SCellCount = 1 | | | | | E1 =0 | | 1 | | | | | | | | | | -| SCellIndex =1 | | | | | | | | 1 | | | | | | | | | | -| SlotOffset | | | SlotRange | | | | | 1 | | | | | | | | | | -| HARQCount = 1 | | | | R | R | R | R | 1 | | | | | | | | | | -| HARQ PID =1 | | | | HARQStatus = 1 | | ClearTB =0 | | 1 | | | | | | | | | | -| SlotType = 0 | SlotOffset | | | Reserved | | | | 1 | | | | | | | | | | -| SlotRange | | | | | | | | 1 | | | | | | | | | | -| SCell Bitmap = 0x00000002 | | | | | | | | 4 | | | | | | | | | | -| LCCount = 1 | | | | E2 | | R | R | 1 | | | | | | | | | | -| LCID = 4 | | | | | | | | 1 | | | | | | | | | | -| Buffer Length = x | | | | | | | | 3 | | | | | | | | | | -| D2 UE ID =2 | | | | | | | | 2 | | | | | | | | | | -| D2 Sched SN | | | | | | | | 2 | | | | | | | | | | -| D2 UE data size = 23 | | | | | | | | 2 | | | | | | | | | | -| DT = 2 (Both) | SCellCount = 2 | | | | | E1 =0 | | 1 | | | | | | | | | | -| SCellIndex =1 | | | | | | | | 1 | | | | | | | | | | -| SlotOffset | | | SlotRange | | | | | 1 | | | | | | | | | | -| HARQCount = 1 | | | | R | R | R | R | 1 | | | | | | | | | | -| HARQ PID = 1 | | | | HARQStatus = 1 | | ClearTB =0 | | 1 | | | | | | | | | | -| SCellIndex =2 | | | | | | | | 1 | | | | | | | | | | -| SlotOffset | | | SlotRange | | | | | 1 | | | | | | | | | | -| HARQCount = | | | | R | R | R | R | 1 | | | | | | | | | | -| HARQ PID = 1 | | | | HARQStatus = 1 | | ClearTB = 0 | | 1 | | | | | | | | | | -| SlotType = 1 | SlotOffset | | | SlotMask | | | | 1 | | | | | | | | | | - -| | | | | | -|---------------------------|--------|---|---|---| -| SlotMask | | | | 4 | -| SCell Bitmap = 0x00000001 | | | | 4 | -| LCCount = 1 | E2 = 0 | R | R | 1 | -| LCID = 1 | | | | 1 | -| Buffer Length = y | | | | 3 | - -**Figure A.3-1: DL SCHEDULING REQUEST for transmission and retransmission (Both)** - -**NOTE:** Buffer Length x and y in the above table indicates the size of data that can be scheduled in SCells as mentioned in SCell Bitmap for the UE configured in sO-DU. - -# --- Annex (informative): Change history/Change request (history) - -| Date | Revision | Description | -|------------|-----------|---------------------------------------------------------------------| -| 23-10-2025 | 00.00.001 | CRs MAV-0015, MAV-0016, MAV-0017 and MAV-0022 are merged. | -| 30-10-2025 | 00.00.002 | CRs NEC-0110, NEC-0111, NEC-0112, MAV-0026 and MAV-0025 are merged. | -| 30-10-2025 | 00.00.003 | Incorporated review comments provided during F2F meeting | -| 06.11.2025 | 00.00.004 | Incorporated review comments shared by NEC and Ericsson | -| 13.11.2025 | 00.00.005 | Incorporated review comments shared by KDDI and Ericsson | -| 17.11.2025 | 00.00.006 | Examples in Annex A is added for DL SCHEDULING REQUEST | -| 25.11.2025 | 00.00.007 | Incorporates all the comments. | \ No newline at end of file diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/0827b9260fe5458dbe416ebfc78c469e_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/08783c875dd39684fee7f2a40b584c64_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/0ff19975027a3c5177519975f9af055f_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/0ff19975027a3c5177519975f9af055f_img.jpg deleted file mode 100644 index 2d3d15cdd07853b525b96b90c6e75666b5f5c6e4..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/0ff19975027a3c5177519975f9af055f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:139bb97c1cef1a005e3d299864b37dd69ccd80bf3649b3c1b39c392d8dae884a -size 16195 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/1099a4137017f2d9721d546bbb1e9362_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/14af8d47efd24c21fddf71b2415b6397_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/185df94f4a6a5245323255e844a30ec0_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/1baaba7a6e54e77197475726c871067d_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/1eadbbe42cfcac5c0023577110aec5e3_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/1eadbbe42cfcac5c0023577110aec5e3_img.jpg deleted file mode 100644 index f65b7e3985e0793b9276f9bdd99c4498a74029c2..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/1eadbbe42cfcac5c0023577110aec5e3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9b7aadf40acf548f10e36cc6ffa267fa29cdf664f00c4bbe98bb29b481039f52 -size 17416 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/22af211207188ebc64d7b60ca052b367_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/22f30783614672d201275c116a5d8516_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/253600420ae7bd7d0119563b895cbf8a_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/29f3760c0230631eb03f67030ef65ed0_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/33a8f3f01dfa8bce75d23017855a13c5_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/33a8f3f01dfa8bce75d23017855a13c5_img.jpg deleted file mode 100644 index f43b14ac5e84ccb5557155607b865deda211aa36..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/33a8f3f01dfa8bce75d23017855a13c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:51c22f6df39050c665f7b0521cd6c8064e9bb991fb9ed523b515acf43687fae7 -size 15982 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg deleted file mode 100644 index c335f9e9db0952c74c9db245154e560a5437b234..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/343e05a9fd8a8c8743428fa4ae6e2736_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ce20f1efe6a4f0c1767a475b1140e2a7e1cef823c9d1c26834107e95d7f084c7 -size 13590 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/36fb8f844f936e7a1de4838da774f2f9_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/38866d3f212726e1c8e92001ca0dd6f8_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/3f727e6c0d6658bc53ea10905c4561dd_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/41a438d7e4adc17c3a4005e7c9500091_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/41a438d7e4adc17c3a4005e7c9500091_img.jpg deleted file mode 100644 index c5a90d195a8061b8b9e98302bc54745c7ea0b2cc..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/41a438d7e4adc17c3a4005e7c9500091_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3bbc94900e351fdb5371f50a230a935b0d66ee60bbe8c9285a61459fcc5ebccb -size 15725 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/446c0bd806260f25430cadb01a6786c7_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/4a04896dfb569893fba50729314024f5_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index f3a71b98fcfc274b0603208cc5e23601d7fc924a..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:84a0e505aa8e8fcec39c03736b466858a7c1ef91abe309cdd2974ee18257e23b -size 4531 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/536951b2bbd94325ae266d8d1363df8f_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/536951b2bbd94325ae266d8d1363df8f_img.jpg deleted file mode 100644 index e6e18343b656ddef3e22d9285ae438e20c1a4114..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/536951b2bbd94325ae266d8d1363df8f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9162b6629f7264f08240f17f5c89634774389613f4a9ec8df28316f5ea19e5b3 -size 26956 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/56ac11fb9683d7b846fb65c845d80f22_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index f3a71b98fcfc274b0603208cc5e23601d7fc924a..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:84a0e505aa8e8fcec39c03736b466858a7c1ef91abe309cdd2974ee18257e23b -size 4531 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/5ae3023386ee15fae372871afce28865_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/60e345365fd1e52e01c91e3fd3cc6515_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/6588b1c7f14069d96744b473ad663248_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/79898de98da3367d0ea9beef38f5c01c_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7d08458fbe0bd5f306c00c16d68b25f2_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7e670a2b556b53ea9002dfff3a420e08_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7e670a2b556b53ea9002dfff3a420e08_img.jpg deleted file mode 100644 index de1fa3204d7252209ce4f3976069524f3760baaa..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7e670a2b556b53ea9002dfff3a420e08_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a89cc165cdabb7d1c96ab64b102a4e93e01ccd3841b733ad2fd61097d21f0ea3 -size 27210 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7efae06af3af43ffe5d4b956a679cf54_img.jpg deleted file mode 100644 index 56a78796f263f663d985e19f8fda70e8f668220a..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7efae06af3af43ffe5d4b956a679cf54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9edc62e4efece2717dc221076f824e6e1a4490dd15d58924760676ee120d5915 -size 22210 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7f17c430b9598e4d748a8041457810b3_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7f17c430b9598e4d748a8041457810b3_img.jpg deleted file mode 100644 index 2b9947fa0b4e38c9637ef3becc547888ba0e8bce..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7f17c430b9598e4d748a8041457810b3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:af6787356ba49e640c0cb7be964eb0201b748b1004ca6da281a15a057878ee9d -size 19135 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/7f4320cee12fc1dbb865cc6b67462a91_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index f3a71b98fcfc274b0603208cc5e23601d7fc924a..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:84a0e505aa8e8fcec39c03736b466858a7c1ef91abe309cdd2974ee18257e23b -size 4531 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/83ee9f10bd3636e192d68decf7f04cec_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/8447c5519e85d7a9e029fbf321da4c4f_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/854df8ad60507803253274673f9062cf_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/89100a6476d1d96f22c192db16502fec_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/8b4befaffc5166da571069410e207aea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/8d129c93d18909f0643766f372e9ebf6_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/8dcca7651accff77ce832523fe2c7e64_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/90ee16ccc0ad16aeca48087797d7b07f_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/90ee16ccc0ad16aeca48087797d7b07f_img.jpg deleted file mode 100644 index 91dfcbd402287599dd549baa6faaf8710c872f63..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/90ee16ccc0ad16aeca48087797d7b07f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8bbad565c02a45835cbb80e83dd827ce7cc5c67246d8023872bc5fc0d3b898a3 -size 21221 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/9156549264d36ead617a1dec7987f970_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/935075de5250cfe8aa0fb9d65d63dde5_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/935075de5250cfe8aa0fb9d65d63dde5_img.jpg deleted file mode 100644 index 17b625c420f1174fb2a79a18451ef701a57c613c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/935075de5250cfe8aa0fb9d65d63dde5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8deff9a640709e6529dba9ab5add8633f3ac5446c22a06bd9fc54c7a97ef0fe9 -size 16868 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/970a901d8e537da4b6ff719d8931912f_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/9a6ff2584005112f32fbd551cb6f0591_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/9b59a11096b85b2bc74c6f653a354e28_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/9b9262a549828579ab904148450734f6_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/9b9262a549828579ab904148450734f6_img.jpg deleted file mode 100644 index 5bac2e02f8b7ba299f61402cb16d2f40d298cc54..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/9b9262a549828579ab904148450734f6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f2e16499188934e9491f49dffb2aa996a1af2617fbe06ff76c001c3aa6b82c05 -size 14274 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/a76a30cf23764f0b907220e7c3c70ce1_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/a92b1fdf37a74b707e9f03087c8f1377_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/a92b1fdf37a74b707e9f03087c8f1377_img.jpg deleted file mode 100644 index 03a328c778eb0825bd8696f70a120c8827e9c912..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/a92b1fdf37a74b707e9f03087c8f1377_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6b167e14cb70ad3971d3d44fe2d66d6e7374fc8ab490c6fcca381601f357b1e5 -size 16550 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/af6be343f0c0a8f155f965dcf337b8af_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/af6be343f0c0a8f155f965dcf337b8af_img.jpg deleted file mode 100644 index ac0bdaedea5410e80469d8b1709e75ad518b3ad1..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/af6be343f0c0a8f155f965dcf337b8af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a29595609bb41c3b3834f8ff29a077616ce17b8acadb8f1bc14f1cde9777074f -size 14297 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/be8d4d130f4e1f103926de61c4bfc23c_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/c389468860cd886ab9c732473e959f0f_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/c4315e81a5a818379fcf31519a9c2cbe_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/cb5f64aa26cee1c05257b7c6bbba7408_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d0516b99882398c64c90f71c12e808e2_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d2c29dfabebacb6f853683a6c3759320_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 7b709785e7bde6ab0aefde9a9de8aa8821419443..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7fce5ec145d266c60c3b370530b3bedf9dceca212603e3c67667c5ad79226fb7 -size 4577 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d90d939bcbf43d474efaeeaa335a635c_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/d90f17b29a73eddf151f51effa8912e0_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/da74b0e807fd62f32abdc3c05ffbabf4_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e2b7490a3455c66c85db12872c78fcc3_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e2b7490a3455c66c85db12872c78fcc3_img.jpg deleted file mode 100644 index 6706c195852067b197555b1e114fca0d50b9726d..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e2b7490a3455c66c85db12872c78fcc3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f0c56ac54603fc53513648d127ea719ae8f42a551eec9f47e6215572685e92d8 -size 13246 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e32e1bcf367a284cc7a4186056810d22_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e511e373339b5f948f239b19e0c37dd4_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e87df69ebd4cd2dbbf6749079e6c057a_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e882a6bdfd0e868314f3a26f536145a3_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e9d825d87c5f85c8dba0664eace96ef4_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e9d825d87c5f85c8dba0664eace96ef4_img.jpg deleted file mode 100644 index b8cc6b1bc6641d72f7c4a4a28499f2b5557ad0ba..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/e9d825d87c5f85c8dba0664eace96ef4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:468992543838a7e80e9032aceec2c14ee60e338921e693e575938744fd15603d -size 19561 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg deleted file mode 100644 index d85487a66eaca6a1292f7dd8c8165f81074a3229..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c42952cacf177bcc33589541f096aff1189ac1408015dabcf6aea67d2696f3f0 -size 16680 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/f250ba4162fe40d8ddfd05b74fa48895_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/f3d768b0299c4763bc703b606391c48b_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/f74adaa1840504407cd4272995426f82_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/f7dbd497160f02888f34fdf243648aa2_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/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 6ddfd874b5ed2c388a8b254cfcd05e592358b5aa..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-0.R005-v01.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ad7f44660e1bb603ef631a89bb564221b18b6191e6c692017cac5241d7812c28 -size 4558 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/doc.md b/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/doc.md deleted file mode 100644 index e648c355c5f25e5db84e1b326a485bb41c3b244e..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/doc.md +++ /dev/null @@ -1,159 +0,0 @@ - - -![O-RAN ALLIANCE logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) - -The logo for the O-RAN ALLIANCE, featuring a colorful circular icon to the left of the text "O-RAN" in blue, with "ALLIANCE" in smaller blue letters underneath. - -O-RAN ALLIANCE logo - -# --- **O-RAN Work Group 5 D2AP TS Errata** - -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 -- 3 Definition of terms, symbols and abbreviations ..... 4 - - 3.1 Terms ..... 4 - - 3.2 Symbols..... 4 - - 3.3 Abbreviations..... 4 -- 4 Correction of OID for D2CP..... 4 -- Change history/Change request (history)..... 5 - -## --- Foreword - -This Errata Document has been produced by WG5 of the O-RAN ALLIANCE e.V. - -## --- 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 is an informative document that describes the modifications done in D2 AP Technical Specification v01.00. - -## --- 2 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. - -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 document is corrected in the content the present document. - -[1] O-RAN WG5: O-RAN.WG5.TS.D2AP-0.R005-v01.00.docx - -## --- 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -Void - -## 3.2 Symbols - -Void - -## 3.3 Abbreviations - -OID Object Identifier - -## --- 4 Correction of OID for D2CP - -OID information in clauses 5.4.4.3, 5.4.4.4, 5.4.4.5, 5.4.4.6, 5.4.4.7, 5.4.4.8 of the D2AP specification [1] is incorrect. In the D2 AP TS [1] ASN.1 definitions are specifying OID as itu-t and etsi which is incorrect for O-RAN specified interfaces and ASN.1 definitions. Following corrections are made to the above referenced clauses in D2 AP TS [1]: - -**Clause 5.4.4.3:** Text in bold in D2CP-PDU-Descriptions is corrected with the text in Red font color below. - -D2CP-PDU-Descriptions { -**itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) ngran-access (22) modules (3) d2cp (4) version1 (1) d2cp-** -**PDU-Descriptions (0)}** - -D2CP-PDU-Descriptions { -**iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 53148 d2(6) version1 (1) d2cp(1) d2cp-PDU-** -**Descriptions(0) }** - -**Clause 5.4.4.4:** Text in bold in PDU Contents is corrected with the text in Red font color below. - -``` -D2CP-PDU-Contents { -itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) ngran-access (22) modules (3) d2cp (4) version1 (1) d2cp- -PDU-Contents (1) } -``` - -``` -D2CP-PDU-Contents { -iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 53148 d2(6) version1 (1) d2cp(1) d2cp-PDU- -Contents(1) } -``` - -**Clause 5.4.4.5:** Text in bold in D2CP IE definitions is corrected with the text in Red font color below. - -``` -D2CP-IEs { -itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) ngran-access (22) modules (3) d2cp (4) version1 (1) d2cp- -IEs (2) } -``` - -``` -D2CP-IEs { -iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 53148 d2(6) version1 (1) d2cp(1) d2cp-IEs(2) } -``` - -**Clause 5.4.4.6:** Text in bold in D2CP commonDataTypes is corrected with the text in Red font color below. - -``` -D2CP-CommonDataTypes { -itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) ngran-access (22) modules (3) d2cp (4) version1 (1) d2cp- -CommonDataTypes (3) } -``` - -``` -D2CP-CommonDataTypes { -iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 53148 d2(6) version1 (1) d2cp(1) d2cp- -CommonDataTypes(3) } -``` - -**Clause 5.4.4.7:** Text in bold in D2 constant is corrected with the text in Red font color below. - -``` -D2CP-Constants { -itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) ngran-access (22) modules (3) d2cp (4) version1 (1) d2cp- -Constants (4) } -``` - -``` -D2CP-Constants { -iso (1) identified-organization (3) dod (6) internet (1) private (4) enterprise (1) 53148 d2 (6) version1 (1) d2cp (1) d2cp- -Constants (4) } -``` - -**Clause 5.4.4.8:** Text in bold in D2CP containers is corrected with the text in Red font color below. - -``` -D2CP-Containers { -itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) ngran-access (22) modules (3) d2cp (4) version1 (1) d2cp- -Containers (5) } -``` - -``` -D2CP-Containers { -iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 53148 d2(6) version1 (1) d2cp(1) d2cp- -Containers(5) } -``` - -## --- Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|-----------------| -| 2026.01.20 | 01 | Initial version | -| | | | -| | | | -| | | | \ No newline at end of file diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index d83db742d4f4a5686db46fba51a8978b3d55350c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:118a75afce84048742b1a083a2cf669dbfd2b8c692dcd080b99beca4ce23ac9f -size 4538 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg deleted file mode 100644 index 26663e840d1231f4cfc8954b48b331e6df4e0f97..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1ed3d336da53efdeba919c288a9b781e3a43804b605efb12fc0ae48cf11c4522 -size 4711 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/38222c3ae003223a67635bfcc6950fbb_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/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index a2190b07af57e6c2117f13a0cf84c7a17ad54ecf..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea8dba2225671c21fb89754dc6606a9991857eb384b6799a2abd7ae6312d4f41 -size 4574 diff --git a/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2AP-R005-v01.00-ERR01-v01.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/doc.md b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/doc.md deleted file mode 100644 index 98621be6cdbb34619241471d8865d51dca2fef29..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/doc.md +++ /dev/null @@ -1,850 +0,0 @@ - - -# --- **O-RAN Open F1/W1/E1/X2/Xn/D2 Interfaces Working Group****D2 Interface: General Aspects and Principles** - -Copyright © 2025 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 - -| | | | -|----|----------------------------------------------------------|----| -| 1 | Contents | | -| 2 | List of figures ..... | 4 | -| 3 | List of tables ..... | 4 | -| 4 | Foreword..... | 5 | -| 5 | Modal verbs terminology ..... | 5 | -| 6 | 1 Scope..... | 6 | -| 7 | 2 References ..... | 6 | -| 8 | 2.1 Normative references ..... | 6 | -| 9 | 2.2 Informative references ..... | 6 | -| 10 | 3 Definition of terms, symbols and abbreviations ..... | 7 | -| 11 | 3.1 Terms ..... | 7 | -| 12 | 3.2 Symbols..... | 7 | -| 13 | 3.3 Abbreviations..... | 7 | -| 14 | 4 General aspects..... | 7 | -| 15 | 4.1 D2 interface general principles ..... | 7 | -| 16 | 4.2 D2 interface within O-RAN architecture..... | 8 | -| 17 | 4.3 Functional split for PCell O-DU and SCell O-DU ..... | 9 | -| 18 | 4.4 D2 interface specification objectives..... | 9 | -| 19 | 4.5 D2 interface capabilities ..... | 9 | -| 20 | 5 Functions of the D2 interface..... | 10 | -| 21 | 5.1 General..... | 10 | -| 22 | 5.2 D2-c function ..... | 10 | -| 23 | 5.2.1 Interface management function..... | 10 | -| 24 | 5.2.2 UE management function..... | 13 | -| 25 | 5.3 D2-u function..... | 14 | -| 26 | 5.3.1 D2-u general principles ..... | 14 | -| 27 | 5.3.2 Transfer of user data..... | 15 | -| 28 | 6 Procedures of the D2 interface..... | 16 | -| 29 | 6.1 Control plane procedures ..... | 16 | -| 30 | 6.1.1 Interface management procedures..... | 17 | -| 31 | 6.1.2 UE management procedures..... | 17 | -| 32 | 6.2 User plane procedures..... | 18 | -| 33 | 6.2.1 Downlink data transfer ..... | 18 | -| 34 | 6.2.2 UCI Transfer ..... | 18 | -| 35 | 7 D2 application protocol structure..... | 18 | -| 36 | 7.1 D2 control plane protocol (D2-c)..... | 18 | -| 37 | 7.2 D2 user plane protocol (D2-u)..... | 19 | -| 38 | 8 D2 interface transport requirements..... | 19 | -| 39 | 9 D2 interface management and configuration aspects..... | 20 | -| 40 | 10 D2 interface security requirements ..... | 20 | -| 41 | Annex A (informative): Deployment options..... | 20 | -| 42 | A.1 General deployment considerations ..... | 20 | -| 43 | A.2 Deployment model A: Co-located deployments..... | 20 | -| 44 | A.3 Deployment model B: Non-co-located deployments..... | 22 | -| 45 | Annex B (informative): D2 interface Implications ..... | 23 | -| 46 | B.1 O-CU-CP/O-CU-UP ..... | 23 | -| 47 | B.2 Synchronization Requirements ..... | 23 | - -1 Annex (informative): Change history..... 24 -2 - -# --- 3 List of figures - -4 Figure 4.2-1: D2 Interface for Intra CU inter DU carrier aggregation ..... 7 -5 Figure 4.3-1: User Data exchange for inter O-DU DL CA (PUSCH not shown)..... 8 -6 Figure 5.2.1-1: Interface Management Function ..... 11 -7 Figure 5.2.2-1: UE Management Function ..... 13 -8 Figure 5.3.2-1: Transfer of user data and scheduling control information ..... 15 -9 Figure 7.1-1: Interface Protocol structure for D2-c ..... 17 -10 Figure 7.2-1: Protocol stack for D2-u ..... 18 -11 Figure A.2-1: Addition of co-located O-RU and O-DU ..... 20 -12 Figure A.2-2: Addition of co-located O-RU and O-DU connected with different O-CU-UPs ..... 20 -13 Figure A.3-1: Addition of non co-located O-RU and O-DU ..... 21 -14 Figure A.3-2: Addition of non-co-located O-RU and O-DU connected with different O-CU-UPs..... 22 -15 - -# --- 16 List of tables - -17 Table 6.1-1: D2-c Procedures ..... 16 -18 -19 -20 - -# --- Foreword - -This Technical Specification (TS) has been produced by WG5 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 general aspects and principles of the D2 interface. D2 is a point-to-point interface interconnecting two O-DUs to enable NR carrier aggregation. The O-DUs are connected to the same O-CU-CP. PCell in this document refers to SpCell as defined in 3GPP TS 37.340 [5]. - -# 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. - -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.WG9.XTRP-REQ-v01.00: "Xhaul Transport Requirements". -- [3] O-RAN.WG4.CUS.0-v09.00: "Control, User and Synchronization Plane Specification" -- [4] O-RAN.WG9.XTRP-SYN.0-v03.00: "Synchronization Architecture and Solution Specification" -- [5] 3GPP TS 37.340 V18.6.0: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2". -- [6] 3GPP TS 38.401 V18.6.0: "5G; NG-RAN; Architecture description " -- [7] 3GPP TS 38.133 V18.10.0: "5G; NG-RAN; Requirements for support of radio resource management" -- [8] 3GPP TS 38.323 V18.5.0: "5G; NG-RAN; Packet Data Convergence Protocol (PDCP) specification" -- [9] IETF RFC 4960: "Stream Control Transmission Protocol". -- [10] IETF RFC 8200 (2017-07): "Internet Protocol, Version 6 (IPv6) Specification" -- [11] IETF RFC 791 (1981-09): "Internet Protocol". - -## 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. - -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] O-RAN.WG1.TR.SA-MVD-R004-v03.00: "Spectrum Aggregation for Multi-Vendor Deployments" -- [i.3] 3GPP TS 38.473 V18.6.0: "5G; NG-RAN; F1 Application Protocol (F1AP)" - -# --- 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: - -**carrier aggregation:** aggregation of two or more NR or E-UTRA component carriers in order to support wider transmission bandwidths - -**D2 interface:** The inter O-DU interface to enable multi-vendor carrier aggregation in NR is named as D2 according to WG1 ATG definitions. - -**PCell O-DU:** O-DU, where the PCell is configured for a UE to support inter O-DU carrier aggregation. - -**SCell O-DU:** O-DU, where only SCell(s) are configured for a UE to support inter O-DU carrier aggregation. - -## 3.2 Symbols - -Void - -## 3.3 Abbreviations - -For the purposes of the present document, the abbreviations given in [i.1] and the following apply: - -| | | -|---------|--------------------------------------| -| D2-c | D2 Control plane interface | -| D2CP | D2 Control Protocol | -| D2-u | D2 User Plane interface | -| D2UP | D2 User Plane Protocol | -| DL | Downlink | -| HARQ | Hybrid Automatic Repeat Request | -| MAC | Medium Access Control | -| MNO | Mobile Network Operator | -| 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-RU | O-RAN Radio Unit | -| PDCCH | Physical downlink control channel | -| PUCCH | Physical uplink control channel | -| PUSCH | Physical uplink shared channel | -| RLC | Radio Link Control | -| SCTP | Stream Control Transmission Protocol | -| SMO | Service Management and Orchestration | -| TB | Transport Block | -| UE | User Equipment | - -# --- 4 General aspects - -## 4.1 D2 interface general principles - -The general principles for the specification of the D2 interface are as follows: - -- the D2 interface is open; -- the D2 interface supports the exchange of signalling information between the endpoints. In addition, the interface supports data transmission to the respective endpoints; -- the D2 is a point-to-point interface between the endpoints on two O-DUs. A point-to-point logical interface should be feasible even in the absence of a physical direct connection between the two O-DUs; -- the D2 interface supports control plane (D2-c) and user plane (D2-u) separation; -- the D2 interface enables exchange of UE associated information and non-UE associated information; -- the D2 interface is designed in a future proof way to fulfil new requirements, and services; -- the D2 interface supports NR carrier aggregation of carriers configured in different O-DU nodes. The schedulers in the O-DUs operate independently of each other; - -## 4.2 D2 interface within O-RAN architecture - -O-DUs can be interconnected by the D2 interface. Figure 4.2-1 shows the D2 interface in the O-RAN WG1.OAD Figure 5.1-2 [1]. In the present document, O-DUs interconnected by the D2 interface are connected to a single O-CU-CP as shown in Figure 4.2-1. - -NOTE: O-DUs interconnected by the D2 interface can be connected to different O-CU-UP. Figure 4.2-1 shows the connection between O-DUs connected to a single O-CU-CP. - -![Diagram of D2 Interface for Intra CU inter DU carrier aggregation. It shows an O-CU-CP1 connected to multiple O-DUs (O-DU1, O-DU2, O-DUn) via F1-c interfaces. Each O-DU is connected to an O-RU (O-RU1, O-RU2, O-RU3) via an Open FH interface. The O-DUs are interconnected by D2-c/D2-u interfaces. An O-CU-UP1 is connected to the O-CU-CP1 via an E1 interface and to the O-DUs via F1-u interfaces.](0236eff05bcb8f3a343ea7933aaa306b_img.jpg) - -``` - -graph TD - OCUUP1[O-CU-UP1] -- E1 --- OCUCP1[O-CU-CP1] - OCUCP1 -- F1-c --- ODU1[O-DU1] - OCUCP1 -- F1-c --- ODU2[O-DU2] - OCUCP1 -- F1-c --- ODUn[O-DUn] - ODU1 -- D2-c/D2-u --- ODU2 - ODU2 -- D2-c/D2-u --- ODUn - ODU1 -- Open FH --- ORU1[O-RU1] - ODU2 -- Open FH --- ORU2[O-RU2] - ODUn -- Open FH --- ORU3[O-RU3] - OCUUP1 -- F1-u --- ODU1 - OCUUP1 -- F1-u --- ODU2 - OCUUP1 -- F1-u --- ODUn - OCUUP1 -- F1-u --- OCUCP1 - -``` - -Diagram of D2 Interface for Intra CU inter DU carrier aggregation. It shows an O-CU-CP1 connected to multiple O-DUs (O-DU1, O-DU2, O-DUn) via F1-c interfaces. Each O-DU is connected to an O-RU (O-RU1, O-RU2, O-RU3) via an Open FH interface. The O-DUs are interconnected by D2-c/D2-u interfaces. An O-CU-UP1 is connected to the O-CU-CP1 via an E1 interface and to the O-DUs via F1-u interfaces. - -**Figure 4.2-1: D2 Interface for Intra CU inter DU carrier aggregation** - -The D2 interface is a logical interface connecting two O-DUs for supporting inter O-DU carrier aggregation. A pair of O-DUs can be connected with each other by the D2 interface. - -F1 (F1-c, F1-u) and E1 are logical 3GPP interfaces, whose protocols, termination points and cardinalities are specified in 3GPP TS 38.401 [6]. Open FH is O-RAN defined interface as specified in O-RAN WG4.CUS [3]. - -Using D2 interface, the O-DUs are able to exchange user data and control information to support inter O-DU carrier aggregation. Configuration for establishment and functioning of D2 interface (for example peer O-DU IP address etc) is provided to O-DU by SMO over O1 interface, or by other means such as local node configuration. - -## 4.3 Functional split for PCell O-DU and SCell O-DU - -The functional split in the PCell and SCell O-DU for supporting inter O-DU DL CA is as follows: - -- The user data and control information message exchange take place at MAC level. -- Single RLC per UE resides in the PCell O-DU as shown in Figure 4.3-1. -- For supporting DL CA using D2 interface PUCCH allocation and reception of PUCCH data from UE is performed by the PCell O-DU for both PCell and SCells. The PCell O-DU shares the received information with the SCell O-DU as shown in Figure 4.3-1 - -![Diagram showing the functional split for PCell O-DU and SCell O-DU. The PCell O-DU contains RLC, MAC, and PHY layers. The SCell O-DU contains MAC and PHY layers. The UE is shown at the bottom. Data flow: RLC in PCell O-DU sends DL Data to its MAC. The PCell MAC sends DL Data to the SCell MAC via the D2 interface. The PCell MAC also sends PUCCH to the SCell MAC. The PCell PHY sends PDSCH to the UE. The SCell PHY sends PDSCH to the UE. The UE sends PDCCH to the PCell PHY. The PCell PHY sends PUCCH to the UE. The SCell PHY sends PDCCH to the UE.](c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg) - -Diagram showing the functional split for PCell O-DU and SCell O-DU. The PCell O-DU contains RLC, MAC, and PHY layers. The SCell O-DU contains MAC and PHY layers. The UE is shown at the bottom. Data flow: RLC in PCell O-DU sends DL Data to its MAC. The PCell MAC sends DL Data to the SCell MAC via the D2 interface. The PCell MAC also sends PUCCH to the SCell MAC. The PCell PHY sends PDSCH to the UE. The SCell PHY sends PDSCH to the UE. The UE sends PDCCH to the PCell PHY. The PCell PHY sends PUCCH to the UE. The SCell PHY sends PDCCH to the UE. - -Figure 4.3-1: User Data exchange for inter O-DU DL CA (PUSCH not shown) - -## 4.4 D2 interface specification objectives - -The D2 interface specifications facilitate the following: - -- inter connection between two O-DUs. -- inter O-DU carrier aggregation by exchanging user and control information between O-DUs. - -## 4.5 D2 interface capabilities - -The D2 interface supports: - -- procedures to establish, maintain and release D2 connection between two O-DUs. -- procedures to establish, maintain and release D2 context for storing the UE information across O-DUs for supporting inter O-DU CA. -- procedures to exchange user data and control data across O-DUs to support the inter O-DU CA. - -# 5 Functions of the D2 interface - -## 5.1 General - -The D2 interface provides connectivity between O-DUs to facilitate inter O-DU carrier aggregation. Its functionality is divided into two parts: control plane (D2-c) and user plane(D2-u). The following clauses describe the functions supported over D2-c and D2-u. - -## 5.2 D2-c function - -### 5.2.1 Interface management function - -The D2 setup function allows for the initial setup of a D2 connection between two O-DUs, including exchange of the cell-level data. Configuration of the D2 interface endpoints can be managed by the SMO to O-DU via the O1 interface. D2 configuration can also be provided through node specific O&M systems. The D2 setup can be initiated by any O-DU that successfully completes the cell setup procedure. During this process, both the originating and destined O-DUs share cell capabilities, for example sub-carrier spacing, duplexing methods, and TDD DL-UL configurations etc. If received O-DU is unable to accept the D2 connection, D2 SETUP FAILURE is sent back to the transmitting O-DU. - -Once the D2 connection is established, any changes for the cells used for inter O-DU CA, such as a cell being locked, cell unlocked, overloaded or changes to cell configuration (including cell addition and removal) are communicated to its peer O-DU using the D2 configuration update function. If cell status is changed to locked or disabled, context for all the UEs configured for inter O-DU CA in that SCell is released. - -D2 release function is used to remove the D2 connection between the two O-DUs, so that all the related resources between the two O-DUs are cleared. - -The error indication function is used by the O-DU to indicate to the peer O-DU that an error has occurred. For example, if parsing of D2 CONFIGURATION UPDATE ACKNOWLEDGE or D2 SETUP RESPONSE fails, O-DU can inform the peer O-DU about the failure using error indication function. - -Figure 5.2.1-1 shows the interface management functions. - -``` -@startuml -Skinparam titleBorderRoundCorner 25 -skinparam titleBorderThickness 2 -skinparam titleBorderColor red -skinparam titleBackgroundColor Coral -skinparam titleFontSize 20 -participant DU1 as "O-DU1" -participant DU2 as "O-DU2" -Note over DU1: O-DU1 is initiating the connection -DU1->>DU2 : D2 SETUP REQUEST (\n O-DU1 Cell list, cell Capability etc) -group#Gold #LightBlue Success -DU2->>DU1: D2 SETUP RESPONSE (\n O-DU2 Cell list, cell Capability etc) -Note over DU1 : If cells are locked, unlocked or overloaded \nor any other scenario causing -update in Cell config. -DU1->>DU2 : D2 CONFIGURATION UPDATE -DU2->>DU1 : D2 CONFIGURATION UPDATE ACKNOWLEDGE -Note over DU2: Based on the received cause in Configuration Update, \n context for UEs in that -cell can be released. -Note over DU1: Decides to bring down D2 connection gracefully -DU1->>DU2: D2 RELEASE REQUEST -DU2->>DU1: D2 RELEASE RESPONSE -Note over DU1, DU2: D2 connection is released. \nAll the D2 contexts is cleared. SCTP -connection is released.\nNo further message exchange over D2 connection. -else #LightPink Failure -``` - -``` -1 DU2->DU1: D2 SETUP FAILURE -2 Else #lightgreen Error -3 DU2->DU1: D2 SETUP RESPONSE -4 group #lightyellow Error in response parsing at DU1 -5 DU1->DU2: D2 ERROR INDICATION -6 Note over DU1, DU2: D2 connection is not established -7 else #lightcyan Error in configuration update -8 DU1->DU2: D2 CONFIGURATION UPDATE -9 DU2->DU1: D2 ERROR INDICATION -10 end -11 End -12 @enduml -``` - -![Sequence diagram for Interface Management Function between O-DU1 and O-DU2. The diagram is divided into Success, Failure, and Error sections. It shows message exchanges for D2 SETUP, CONFIGURATION UPDATE, and RELEASE. Success path includes setup, optional configuration update, and graceful release. Failure path shows a setup failure. Error path shows parsing or configuration update errors leading to error indications.](e9314c83043183351ed74908e9bf2f90_img.jpg) - -``` - -sequenceDiagram - participant O-DU1 - participant O-DU2 - Note left of O-DU1: O-DU1 is initiating the connection - O-DU1->>O-DU2: D2 SETUP REQUEST (O-DU1 Cell list, cell Capability etc) - Note right of O-DU2: Success - O-DU2-->>O-DU1: D2 SETUP RESPONSE (O-DU2 Cell list, cell Capability etc) - Note left of O-DU1: If cells are locked, unlocked or overloaded or any other scenario causing update in Cell config. - O-DU1->>O-DU2: D2 CONFIGURATION UPDATE - O-DU2-->>O-DU1: D2 CONFIGURATION UPDATE ACKNOWLEDGE - Note right of O-DU2: Based on the received cause in Configuration Update, context for UEs in that cell can be released. - Note left of O-DU1: Decides to bring down D2 connection gracefully - O-DU1->>O-DU2: D2 RELEASE REQUEST - O-DU2-->>O-DU1: D2 RELEASE RESPONSE - Note left of O-DU1: D2 connection is released. All the D2 contexts is cleared. SCTP connection is released. No further message exchange over D2 connection. - Note right of O-DU2: [Failure] - O-DU2-->>O-DU1: D2 SETUP FAILURE - Note right of O-DU2: [Error] - O-DU2-->>O-DU1: D2 SETUP RESPONSE - Note left of O-DU1: Error in response parsing at DU1 - O-DU1->>O-DU2: D2 ERROR INDICATION - Note left of O-DU1: D2 connection is not established - Note left of O-DU1: [Error in configuration update] - O-DU1->>O-DU2: D2 CONFIGURATION UPDATE - O-DU2-->>O-DU1: D2 ERROR INDICATION - -``` - -Sequence diagram for Interface Management Function between O-DU1 and O-DU2. The diagram is divided into Success, Failure, and Error sections. It shows message exchanges for D2 SETUP, CONFIGURATION UPDATE, and RELEASE. Success path includes setup, optional configuration update, and graceful release. Failure path shows a setup failure. Error path shows parsing or configuration update errors leading to error indications. - -Figure 5.2.1-1: Interface Management Function - -1 -2 - -### 5.2.2 UE management function - -The UE management function supports the establishment and modification of D2 context for SCells for a UE. These functions include establishment, modification and release of the SCells in PCell and SCell O-DUs. The procedures include addition, deletion or modification of a SCell for a UE in the O-DUs. - -The establishment of UE addition is initiated by the PCell O-DU. It is accepted or rejected by the SCell O-DU based on the admission control criteria for example resource availability, loading etc. Upon reception of successful addition response for the UE from the SCell O-DU, the PCell O-DU sends UE Context Setup/Modification response to O-CU-CP. RRC Reconfiguration procedure is triggered towards UE for SCell addition. Once RRC Reconfiguration Complete is received from UE, the PCell O-DU sends the UE Reconfiguration Completion message to the SCell O-DU. - -The modification of SCell configuration for a UE is initiated by the PCell O-DU. If an SCell for a UE is already configured in the SCell O-DU, PCell O-DU can use modification function to add another SCell. The modification function is also used by the PCell O-DU to update any of the UE configuration parameters for example change of security key, UL configuration, DRX cycle, change of measurement gap, PDU session add/rel/mod (QoS flow add/rel, 5QI Change), DRB etc in the SCell O-DU. If multiple SCells are configured in an SCell O-DU for a UE, this function can also be used to release some of the SCells. - -PCell O-DU uses UE deletion function to release the D2 UE context in the SCell O-DU. This function can be used if UE is released in the PCell O-DU or all the SCells in an SCell O-DU are deleted for a UE. Upon successful completion, the UE information for the SCell is cleared in the SCell O-DU. - -SCell O-DU uses the modification indication function to indicate the release of a D2 UE context or release of a SCell(s)/LC(s) for a D2 UE context. This can be triggered due to any scenario taking place in SCell O-DU for example overloading, or any other reason. In case of SCell(s) release for a UE, SCell information from D2 UE Context for that SCell is released. The PCell O-DU releases the corresponding SCell reference (D2 UE Context) for the UE for which the message is received. PCell O-DU stops any ongoing D2-u activity on the SCell that is released by the UE modification indication function. PCell O-DU does not schedule any data on the SCell that is released. - -Figure 5.2.2-1 captures the UE management functions. - -``` -@startuml -Skinparam titleBorderRoundCorner 25 -skinparam titleBorderThickness 2 -skinparam titleBorderColor red -skinparam titleBackgroundColor Coral -skinparam titleFontSize 20 -participant CU as "O-CU-CP" -participant pDU as "PCell O-DU" -participant sDU as "SCell O-DU" -participant UE -Note over pDU, sDU: D2-c connection is up and running -group #lightpink "First UE Addition from a SCell O-DU" -CU-> pDU: UE CONTEXT SETUP/MODIFICATION REQUEST -pDU ->sDU : UE ADDITION REQUEST -sDU-> pDU: UE ADDITION RESPONSE -pDU ->CU: UE CONTEXT SETUP/MODIFICATION RESPONSE -end -group #lightblue "Addition of more SCells or modification in existing SCells for a UE" -CU-> pDU: UE CONTEXT MODIFICATION REQUEST -pDU ->sDU : UE MODIFICATION REQUEST -sDU-> pDU: UE MODIFICATION RESPONSE -pDU ->CU: UE CONTEXT MODIFICATION RESPONSE (status) -end -CU->UE: RRC Reconfiguration Request (via F1 procedure) -UE->pDU: RRC Reconfiguration Complete -pDU->sDU: UE RECONFIGURATION COMPLETE -group #lightyellow SCell O-DU is unable to handle UE for a SCELL -sDU-> pDU: UE MODIFICATION INDICATION (Cause) -end -group #lightgreen "Either CU decides to release SCell or UE is Released - UE release function" -CU-> pDU: UE CONTEXT MODIFICATION/RELEASE -pDU ->sDU: UE DELETION REQUEST -end -``` - -1 -2 -3 - -``` -sDU-> pDU: UE DELETION RESPONSE -End -@enduml -``` - -![Sequence diagram for UE Management Function showing interactions between O-CU-CP, PCell O-DU, SCell O-DU, and UE. The diagram includes sections for 'First UE Addition from a SCell O-DU', 'Addition of more SCells or modification in existing SCells for a UE', and 'Either CU decides to release SCell or UE is Released - UE release function'.](cab0834804fb031b43865554cc8d06ab_img.jpg) - -The sequence diagram illustrates the UE Management Function across four lifelines: O-CU-CP, PCell O-DU, SCell O-DU, and UE. A note at the top indicates 'D2-c connection is up and running'. - -**Sequence of Interactions:** - -- "First UE Addition from a SCell O-DU"** (Pink background): - - O-CU-CP sends a **UE CONTEXT SETUP/MODIFICATION REQUEST** to PCell O-DU. - - PCell O-DU sends a **UE ADDITION REQUEST** to SCell O-DU. - - SCell O-DU responds with a **UE ADDITION RESPONSE** to PCell O-DU. - - PCell O-DU sends a **UE CONTEXT SETUP/MODIFICATION RESPONSE** back to O-CU-CP. -- "Addition of more SCells or modification in existing SCells for a UE"** (Blue background): - - O-CU-CP sends a **UE CONTEXT MODIFICATION REQUEST** to PCell O-DU. - - PCell O-DU sends a **UE MODIFICATION REQUEST** to SCell O-DU. - - SCell O-DU responds with a **UE MODIFICATION RESPONSE** to PCell O-DU. - - PCell O-DU sends a **UE CONTEXT MODIFICATION RESPONSE (status)** back to O-CU-CP. -- Following the blue section, O-CU-CP sends an **RRC Reconfiguration Request (via F1 procedure)** to the UE. -- The UE responds with an **RRC Reconfiguration Complete** message to PCell O-DU. -- PCell O-DU then sends a **UE RECONFIGURATION COMPLETE** message to SCell O-DU. -- If the **"SCell O-DU is unable to handle UE for a SCELL"** (Yellow background), SCell O-DU sends a **UE MODIFICATION INDICATION (Cause)** to PCell O-DU. -- Finally, in the **"Either CU decides to release SCell or UE is Released - UE release function"** (Green background): - - O-CU-CP sends a **UE CONTEXT MODIFICATION/RELEASE** to PCell O-DU. - - PCell O-DU sends a **UE DELETION REQUEST** to SCell O-DU. - - SCell O-DU responds with a **UE DELETION RESPONSE** to PCell O-DU. - -Sequence diagram for UE Management Function showing interactions between O-CU-CP, PCell O-DU, SCell O-DU, and UE. The diagram includes sections for 'First UE Addition from a SCell O-DU', 'Addition of more SCells or modification in existing SCells for a UE', and 'Either CU decides to release SCell or UE is Released - UE release function'. - -4 -5 -6 - -Figure 5.2.2-1: UE Management Function - -7 -8 -9 - -## 5.3 D2-u function - -### 5.3.1 D2-u general principles - -The following principles apply to D2-u for inter O-DU DL carrier aggregation. - -- The PCell O-DU requests the SCell O-DU to schedule new user data and/or retransmissions due to HARQ feedback for the UE indicating a range of time slots, where data can be scheduled by the SCell O-DU. The range is configurable. -- Data retransmission due to HARQ feedback is executed in the same node where the first transmission was executed. The SCell O-DU stores the TB until retransmission is successful or the HARQ process is cleared by the PCell O-DU. -- CSI-RS transmission for a UE that is added by D2 interface is triggered when an SCell is added for the UE. - -### 5.3.2 Transfer of user data - -Transfer of user data comprises of two functions, the data transfer function and the UCI transfer function. - -The data transfer function allows the transfer of user data between O-DUs to support inter O-DU carrier aggregation. For DL CA, PCell O-DU sends the user data to SCell O-DU. - -The data transfer function consists of procedures that allow the exchange of user data, scheduling related information (range of slots) and associated control information between PCell O-DU and SCell O-DU for supporting inter O-DU CA. - -The PCell O-DU may initiate a procedure to request the SCell O-DU to schedule a user data transmission or to schedule a HARQ retransmission for a particular UE. With each request the PCell O-DU also indicates the range of slots which can be used by the SCell O-DU to schedule new user data or HARQ retransmission. The PCell O-DU may also provide the CSI information to the SCell O-DU. The PCell O-DU may send one or more scheduling requests. - -The SCell O-DU may reply with the scheduled user data size and/or scheduled HARQ retransmission, as well as the air interface timing details (i.e. slot number). The SCell O-DU may send one or more replies to the PCell O-DU. - -Requests from the PCell O-DU and replies from the SCell O-DU are sent asynchronously. - -The PCell O-DU may send the user data matching the scheduled user data size together with the needed PUCCH information to the SCell O-DU. - -The UCI transfer function enables the PCell O-DU to share CSI reports and/or HARQ feedback to the SCell O-DU. The PCell O-DU may also send a TB clear-flag to indicate that no more re-transmission is needed for a particular HARQ process. Upon reception of the TB clear-flag the SCell O-DU may delete the TB buffer and reuse the HARQ process ID for a new user data transmission. - -Figure 5.3.2-1 captures the flow control of user data exchange over D2 connection. - -``` -@startuml -Skinparam titleBorderRoundCorner 15 -skinparam titleBorderThickness 2 -skinparam titleBorderColor red -skinparam titleBackgroundColor Coral -skinparam titleFontSize 30 -participant pDU as "PCell O-DU" -participant sDU as "SCell O-DU" -Note over pDU : DL Data Received from O-CU-UP -Group CSI report -Note over pDU : Receives CSI Indication \nfor the SCell from UE. -pDU->sDU : UCI TRANSFER (CSI, etc.) -end - -Note over pDU: PCell O-DU determines the user data size. it requests \n the SCell O-DU to -schedule the UE in a requested slot range. -Group User Data Transfer -Note over pDU: PCell O-DU may send asynchronously many DL SCHEDULE REQUEST messages \nwith -different user data size and may also extend the slot range -pDU->sDU : DL SCHEDULING REQUEST (Requested User Data size, requested slot range, CSI, etc.) -Note over sDU: SCell O-DU determines the data size and slot it can schedule \n and sends that -to the PCell O-DU -sDU->pDU: DL DATA REQUIRED (Scheduled user data size, selected slot) -Note over sDU: The SCell O-DU may send asynchronously many DL DATA REQUIRED \n messages for -different selected slots -``` - -``` - -1 Note Over pDU: Allocates PUCCH resources for the selected slot -2 pDU->sDU : PUCCH RESOURCE TRANSFER(K1, DAI, etc.) -3 Note over pDU: PCell O-DU sends the user data TB matching \nthe scheduled size received from -4 the SCell O-DU -5 pDU->sDU: DL DATA TRANSFER(User Data TB, etc.) -6 end -7 -8 Group HARQ control, CSI report, TB Clearing -9 Note over pDU: UE has sent HARQ feedback or CSI report and/or PCell O-DU indicates clearing of -10 a TB -11 pDU -> sDU : UCI TRANSFER (HARQ feedback,CSI,TB Clear-flag, etc.) -12 end -13 @enduml - -``` - -![Sequence diagram showing the transfer of user data and scheduling control information between PCell O-DU and SCell O-DU. The diagram is divided into three main sections: CSI report, User Data Transfer, and HARQ control, CSI report, TB Clearing. The CSI report section shows the PCell O-DU receiving a CSI report from the UE and transferring it to the SCell O-DU. The User Data Transfer section shows the PCell O-DU sending a DL SCHEDULING REQUEST to the SCell O-DU, which then responds with DL DATA REQUIRED. The PCell O-DU then allocates PUCCH resources and sends the user data TB to the SCell O-DU. The HARQ control, CSI report, TB Clearing section shows the UE sending HARQ feedback or CSI report to the PCell O-DU, which then transfers it to the SCell O-DU.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) - -``` - -sequenceDiagram - participant UE - participant PCell O-DU - participant SCell O-DU - - Note left of PCell O-DU: DL Data Received from O-CU-UP - Note left of PCell O-DU: CSI report - Note left of PCell O-DU: Receives CSI Indication for the SCell from UE. - PCell O-DU->>SCell O-DU: UCI TRANSFER (CSI, etc.) - - Note left of PCell O-DU: PCell O-DU determines the user data size, it requests the SCell O-DU to schedule the UE in a requested slot range. - Note left of PCell O-DU: User Data Transfer - Note left of PCell O-DU: PCell O-DU may send asynchronously many DL SCHEDULE REQUEST messages with different user data size and may also extend the slot range - PCell O-DU->>SCell O-DU: DL SCHEDULING REQUEST (Requested User Data size, requested slot range, CSI, etc.) - Note right of SCell O-DU: SCell O-DU determines the data size and slot it can schedule and sends that to the PCell O-DU - SCell O-DU->>PCell O-DU: DL DATA REQUIRED (Scheduled user data size, selected slot) - Note right of SCell O-DU: The SCell O-DU may send asynchronously many DL DATA REQUIRED messages for different selected slots - Note left of PCell O-DU: Allocates PUCCH resources for the selected slot - PCell O-DU->>SCell O-DU: PUCCH RESOURCE TRANSFER(K1, DAI, etc.) - Note left of PCell O-DU: PCell O-DU sends the user data TB matching the scheduled size received from the SCell O-DU - PCell O-DU->>SCell O-DU: DL DATA TRANSFER(User Data TB, etc.) - - Note left of PCell O-DU: HARQ control, CSI report, TB Clearing - Note left of PCell O-DU: UE has sent HARQ feedback or CSI report and/or PCell O-DU indicates clearing of a TB - PCell O-DU->>SCell O-DU: UCI TRANSFER (HARQ feedback,CSI,TB Clear-flag, etc.) - -``` - -Sequence diagram showing the transfer of user data and scheduling control information between PCell O-DU and SCell O-DU. The diagram is divided into three main sections: CSI report, User Data Transfer, and HARQ control, CSI report, TB Clearing. The CSI report section shows the PCell O-DU receiving a CSI report from the UE and transferring it to the SCell O-DU. The User Data Transfer section shows the PCell O-DU sending a DL SCHEDULING REQUEST to the SCell O-DU, which then responds with DL DATA REQUIRED. The PCell O-DU then allocates PUCCH resources and sends the user data TB to the SCell O-DU. The HARQ control, CSI report, TB Clearing section shows the UE sending HARQ feedback or CSI report to the PCell O-DU, which then transfers it to the SCell O-DU. - -Figure 5.3.2-1: Transfer of user data and scheduling control information - -# 6 Procedures of the D2 interface - -## 6.1 Control plane procedures - -Table 6.1-1 below captures all the procedures defined for D2-c interface. - -1 - -Table 6.1-1: D2-c Procedures - -| Procedure | Initiating Message | Successful Outcome | Unsuccessful Outcome | -|------------------------------------|------------------------------------|-------------------------------------|---------------------------------| -| | | Response Message | Failure Message | -| D2 Setup | D2 SETUP REQUEST | D2 SETUP RESPONSE | D2 SETUP FAILURE | -| D2 Configuration Update | D2 CONFIGURATION UPDATE | D2 CONFIGURATION UPDATE ACKNOWLEDGE | D2 CONFIGURATION UPDATE FAILURE | -| D2 Release | D2 RELEASE REQUEST | D2 RELEASE RESPONSE | | -| Error Indication | D2 ERROR INDICATION | | | -| UE Addition | UE ADDITION REQUEST | UE ADDITION RESPONSE | | -| UE Modification Update | UE MODIFICATION REQUEST | UE MODIFICATION RESPONSE | | -| UE Reconfiguration Complete | UE RECONFIGURATION COMPLETE | | | -| UE Modification Indication | UE MODIFICATION INDICATION (Cause) | | | -| UE Deletion | UE DELETION REQUEST | UE DELETION RESPONSE | | - -2 - -3 - -###### 4 6.1.1 Interface management procedures - -5 The D2 Interface management procedures are listed below: - -- 6 - D2 Setup procedure -- 7 - D2 Configuration Update procedure -- 8 - Error Indication -- 9 - D2 Release procedure - -###### 10 6.1.2 UE management procedures - -11 The D2 UE management procedures are listed below: - -- 12 - UE Addition procedure -- 13 - UE Modification Update procedure -- 14 - UE Modification Indication procedure -- 15 - UE Reconfiguration Complete -- 16 - UE Deletion procedure - -17 - -## 6.2 User plane procedures - -### 6.2.1 Downlink data transfer - -Transfer of user data and associated scheduling control information related messages are listed below: - -- DL SCHEDULING REQUEST -- DL DATA REQUIRED -- DL DATA TRANSFER -- PUCCH RESOURCE TRANSFER - -### 6.2.2 UCI Transfer - -- UCI TRANSFER - -# 7 D2 application protocol structure - -## 7.1 D2 control plane protocol (D2-c) - -Figure 7.1-1 shows the protocol structure of D2-c. The application layer signalling protocol is referred to as D2CP - -![Diagram of D2 control plane protocol structure showing layers: D2CP, SCTP, IP, Data Link Layer, and Physical Layer.](b0d4609bc46c2d88a8318706bb5321f7_img.jpg) - -The diagram illustrates the protocol stack for the D2 control plane (D2-c). At the top, a box labeled 'D2CP' is shown, with the label 'Control Plane' above it. Below the 'D2CP' box is a horizontal line with an oval in the center, representing an interface. Below this interface is a stack of four boxes representing the transport and network layers: 'SCTP', 'IP', 'Data Link Layer', and 'Physical Layer'. To the left of this stack, the labels 'Radio Network' and 'Transport Network' are present, with 'Radio Network' aligned with the D2CP layer and 'Transport Network' aligned with the SCTP, IP, Data Link Layer, and Physical Layer stack. - -Diagram of D2 control plane protocol structure showing layers: D2CP, SCTP, IP, Data Link Layer, and Physical Layer. - -**Figure 7.1-1: Interface Protocol structure for D2-c** - -The Transport Network Layer is based on IP transport, comprising the SCTP on top of IP. SCTP (IETF RFC 4960 [9]) shall be supported as the transport layer of D2-c control bearer (D2CP). SCTP refers to the Stream Control Transmission Protocol developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP network. There shall be only one SCTP association established between two O-DUs. No SCTP Destination Port number value was assigned by IANA for the D2CP protocol and so networks shall rely on O-DU configuration to select a suitable port number. - -The application layer signalling protocol is referred to as D2CP (D2 Control Protocol). The Payload Protocol Identifier assigned by IANA to be used by SCTP for the application layer protocol D2CP is 71. This value is to be used for all deployment configurations described in the present document. The byte order of the Payload Protocol Identifier shall be big-endian. The O-DUs shall support a configuration with a single SCTP association per O-DU pair. - -The support of any suitable Data Link Layer protocol, e.g. PPP, Ethernet, etc., shall not be prevented. - -1 The O-DUs shall support IPv6 (IETF RFC 8200 [10]) and/or IPv4 (IETF RFC 791 [11]). The IP layer of D2-c only supports - 2 point-to-point transmission for delivering D2CP message. - -3 Between two O-DUs connected by D2 interface: - -- 4 - A single pair of stream identifiers shall be reserved over the SCTP association for the sole use of D2CP elementary - 5 procedures for D2 interface management. -- 6 - At least one pair of stream identifiers shall be reserved for the sole use of D2CP elementary procedures are utilized - 7 for D2 UE management signalling. However, a few pairs (i.e. more than one) should be reserved. -- 8 - For a single UE-associated signalling, the O-DU shall use one SCTP association and one SCTP stream, and the - 9 association/stream should not be changed during the communication of the UE-associated signalling. - -10 - -###### 11 7.2 D2 user plane protocol (D2-u) - -12 Figure 7.2-1 shows the protocol stack for D2-u. - -13 - -![Protocol stack for D2-u diagram](3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg) - -The diagram illustrates the protocol stack for D2-u. It consists of several layers stacked vertically. At the top is the 'Application layer' containing a box labeled 'D2UP'. Below this is a horizontal line with a circle in the center, representing a protocol interface. Below the interface is the 'Transport network layer', which contains three stacked boxes: 'UDP', 'IP', and 'Data link layer'. At the very bottom is the 'Physical layer' box. - -Protocol stack for D2-u diagram - -14 - -15 - -**Figure 7.2-1: Protocol stack for D2-u** - -16 The D2UP (D2 user plane protocol) messages are transported by UDP over IP. Between a pair of O-DU nodes, one or more - 17 UDP ports may be used for D2-u. - -###### --- 18 8 D2 interface transport requirements - -19 The D2 interface is specified to accommodate the latency class High75, High100 & High200 as described in O-RAN - 20 WG9.XTRP [2], section 7.2. D2 interface can also function when using High500 latency but it may have impact on - 21 performance. - -###### --- 22 9 D2 interface management and configuration aspects - -23 The configuration for establishing and functioning of D2 interface is provided by SMO via O1 interface or manually or via - 24 node specific OAM to O-DUs. Parameters such as IP addresses of peer O-DUs, support of CA (DL, both or None) for each cell - 25 in O-DU are needed for functioning of D2 interface. - -26 NOTE: Detailed definition of configuration parameters will be in O1 specification. - -# 10 D2 interface security requirements - -1 -2 Authentication and authorization of O-DUs that exchange control or data information over D2 interface shall be supported. -3 Existing security algorithm for example IPSec can be used to protect the D2 interface. User data exchanged over D2 interface -4 is protected by PDCP (Packet Data Convergence Protocol) [8]. - -5 NOTE: Security requirement for protecting the D2 interface will be defined in security specifications. - -# 6 Annex A (informative): Deployment options - -###### 7 A.1 General deployment considerations - -## 8 A.2 Deployment model A: Co-located deployments - -9 This model considers the deployment scenarios where relevant O-RAN NFs for carrier aggregation are co-located at a cell site. -10 O-RAN NFs may be supporting the same or different band/duplexing capability. - -11 In this deployment scenario, depicted in Figure A.2-1 and Figure A.2-2, the MNO may deploy a new O-RU and O-DU to add a -12 new frequency band to the existing infrastructure. The O-DUs will be connected to the single O-CU-CP. The O-DUs can be -13 connected to the multiple O-CU-UPs as shown in Figure A.2-2. O-DUs are connected by D2 interface to support the inter O- -14 DU carrier aggregation. - -![Diagram of deployment model A showing O-CU-UP connected to multiple O-DUs and O-RUs at a cell site, all connected to a UE.](327ba94498e3381cf08eb41e3fd3d77f_img.jpg) - -The diagram illustrates a network architecture for deployment model A. At the top, an 'O-CU-UP' block is connected to an 'NG' interface. This block is enclosed in a dashed box labeled 'Centralized Location'. Below it, two 'F1' interfaces connect the 'O-CU-UP' to two separate 'O-DU' blocks, 'O-DU1' and 'O-DUn'. These 'O-DU' blocks are located within a dashed box labeled 'Cell Site 1'. A horizontal orange line labeled 'D2' connects 'O-DU1' and 'O-DUn'. Below 'O-DU1', two 'O-RU' blocks, 'O-RU1' and 'O-RU2', are connected via 'O-FH' interfaces. Similarly, below 'O-DUn', an 'O-RU' block labeled 'O-RUn' is connected via an 'O-FH' interface. All 'O-RU' blocks ('O-RU1', 'O-RU2', and 'O-RUn') are connected to a single 'UE' (User Equipment) block at the bottom. The 'O-RU' blocks and the 'UE' are also within the 'Cell Site 1' dashed box. - -Diagram of deployment model A showing O-CU-UP connected to multiple O-DUs and O-RUs at a cell site, all connected to a UE. - -16 Figure A.2-1: Addition of co-located O-RU and O-DU - -1 - -![Figure A.2-2: Addition of co-located O-RU and O-DU connected with different O-CU-UPs. The diagram shows a 'Centralized Location' containing O-CU-CP and O-CU-UP connected via E1. O-CU-CP connects to O-DU1 via F1-C. O-CU-UP connects to O-DU1 via F1-U and to O-DUn via F1-U. O-DU1 and O-DUn are connected via D2. O-DU1 connects to O-RU1 and O-RU2 via O-FH. O-DUn connects to O-RUn via O-FH. All O-RUs connect to a UE. NG-C and NG-U interfaces are shown at the top.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) - -Figure A.2-2: Addition of co-located O-RU and O-DU connected with different O-CU-UPs. The diagram shows a 'Centralized Location' containing O-CU-CP and O-CU-UP connected via E1. O-CU-CP connects to O-DU1 via F1-C. O-CU-UP connects to O-DU1 via F1-U and to O-DUn via F1-U. O-DU1 and O-DUn are connected via D2. O-DU1 connects to O-RU1 and O-RU2 via O-FH. O-DUn connects to O-RUn via O-FH. All O-RUs connect to a UE. NG-C and NG-U interfaces are shown at the top. - -2 - -Figure A.2-2: Addition of co-located O-RU and O-DU connected with different O-CU-UPs - -3 - -## A.3 Deployment model B: Non-co-located deployments - -4 - -This model considers the deployment scenarios where aggregated frequencies are served by equipment that are not co-located at a cell site. O-CU-CP/O-CU-UP might be residing at a centralized location while O-DUs may be located at cell site or at a centralized location. - -5 - -6 - -7 - -In this deployment scenario, depicted in Figure A.3-1 and Figure A.3-2, the MNO may deploy a new O-RU and O-DU to add a new frequency band, that is not co-located with other O-RUs and O-DUs serving the same geographic area. The O-DUs will be connected to the single O-CU-CP. The O-DUs can be connected to the multiple O-CU-UPs as shown in Figure A.3-2. O-DUs are connected by D2 interface to support the inter O-DU carrier aggregation. - -8 - -9 - -10 - -11 - -![Figure A.3-1: Addition of non co-located O-RU and O-DU. The diagram shows a 'Centralized Location' with O-CU-UP connected to NG. O-CU-UP connects to O-DU1 and O-DUn via F1. O-DU1 and O-DUn are connected via D2. O-DU1 is at 'Cell Site' and connects to O-RU1 and O-RU2 via O-FH. O-DUn is at 'Cell Site 2' and connects to O-RUn via O-FH. O-RU1, O-RU2, and O-RUn all connect to a UE. The area with O-RU1 and O-RU2 is labeled 'Co-located', and the area with O-RUn is labeled 'Non-co-located'.](2a9f9c6f1dc9e5b232d69c43882c83ab_img.jpg) - -Figure A.3-1: Addition of non co-located O-RU and O-DU. The diagram shows a 'Centralized Location' with O-CU-UP connected to NG. O-CU-UP connects to O-DU1 and O-DUn via F1. O-DU1 and O-DUn are connected via D2. O-DU1 is at 'Cell Site' and connects to O-RU1 and O-RU2 via O-FH. O-DUn is at 'Cell Site 2' and connects to O-RUn via O-FH. O-RU1, O-RU2, and O-RUn all connect to a UE. The area with O-RU1 and O-RU2 is labeled 'Co-located', and the area with O-RUn is labeled 'Non-co-located'. - -12 - -13 - -Figure A.3-1: Addition of non co-located O-RU and O-DU - -14 - -15 - -![Diagram showing the addition of non-co-located O-RU and O-DU connected with different O-CU-UPs. The diagram illustrates a Centralized Location containing O-CU-CP and O-CU-UP connected via E1. O-CU-CP connects to O-DU1 in Cell Site 1 via F1-C. O-CU-UP connects to O-DUn in Cell Site 2 via F1-U. O-DU1 and O-DUn are connected via D2. O-DU1 connects to O-RU1 and O-RU2 (Co-located) via O-FH. O-DUn connects to O-RUn (Non-co-located) via O-FH. All O-RUs connect to a UE. Dashed blue lines indicate F1-U connections from O-CU-UP to O-DU1 and O-DUn.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) - -Diagram showing the addition of non-co-located O-RU and O-DU connected with different O-CU-UPs. The diagram illustrates a Centralized Location containing O-CU-CP and O-CU-UP connected via E1. O-CU-CP connects to O-DU1 in Cell Site 1 via F1-C. O-CU-UP connects to O-DUn in Cell Site 2 via F1-U. O-DU1 and O-DUn are connected via D2. O-DU1 connects to O-RU1 and O-RU2 (Co-located) via O-FH. O-DUn connects to O-RUn (Non-co-located) via O-FH. All O-RUs connect to a UE. Dashed blue lines indicate F1-U connections from O-CU-UP to O-DU1 and O-DUn. - -Figure A.3-2: Addition of non-co-located O-RU and O-DU connected with different O-CU-UPs - -# Annex B (informative): D2 interface Implications - -## B.1 O-CU-CP/O-CU-UP - -- O-CU-CP will be able to add, delete or modify the SCells from peer O-DUs, connected by D2 interface and to same O-CU-CP, in UE Context Request/Modification procedures. -- No impact on O-CU-UP is expected. - -## B.2 Synchronization Requirements - -Existing synchronization requirement specified in O-RAN WG9.XTRP [4] section 6.3.3 is sufficient to meet the carrier aggregation requirement as mentioned in 3GPP 38.133 [7]. - -1 - -# --- Annex (informative): Change history - -2 - -3 - -| Date | Revision | Description | -|------------|-----------|--------------------------------------------------------------------------------------------------------| -| 2024.11.24 | 00.01 | Initial skeleton created | -| 2025.01.30 | 00.02 | Incorporated MAV CR 006 and MAV CR 007 | -| 2025.02.25 | 00.03 | Incorporated MAV CR 0009, MAV CR 0010, MAV CR 0013, ERI CR 0133, ERI CR 0131, NEC CR 0103, MAV CR 0011 | -| 2025.03.06 | 00.04 | Editorial corrections and review comment incorporation | -| 2025.03.06 | 00.05 | Inclusion of SCTP Protocol payload identified for D2 | -| 2025.03.07 | 00.06 | Inclusion of CR ERI-0134 and editorial corrections | -| 2025.03.08 | 00.07 | Inclusion of CR MAV-0008 and making all the figures similar | -| 2025.03.10 | 00.08 | Updated review comments | -| 2025.03.12 | 00.09 | Review comments incorporated | -| 2025.03.12 | 00.10 | Review comments incorporated | -| 2025.03.13 | 00.11 | Figure Center aligned, History on new page and reference correction | -| 2025.03.28 | 01.00 | Resolved all the comments. Specification is approved by WG as TS 01.00 | -| 2025.06.05 | 01.00.01 | Incorporated ERI CR 137, ERI CR 139 and ERI CR 145 | -| 2025.06.13 | 01.00.02 | Incorporated review comments | -| 2025.06.19 | 01.00.03 | Incorporated review comments | -| 2025.06.25 | 01.00.04 | Incorporated review comments | -| 2025.06.26 | 01.00.05 | Incorporated review comments | -| 2025.07.02 | 01.00.06 | Updated the references section as per new O-RAN template | -| 2025.07.07 | 02.00 | Resolved all the comments. Specification is approved by WG as TS 02.00 | -| 2025.10.27 | 02.00.001 | Incorporated MAV-0020 CR | -| 2025.11.13 | 02.00.002 | Incorporated review comments | -| 2025.11.18 | 02.00.003 | Incorporated review comments | - -4 - -5 - -6 \ No newline at end of file diff --git a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/0236eff05bcb8f3a343ea7933aaa306b_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/0236eff05bcb8f3a343ea7933aaa306b_img.jpg deleted file mode 100644 index a2b58e4a4bf8040772b9e1a1ef4fb685e6bd8835..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/0236eff05bcb8f3a343ea7933aaa306b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3357c08167294d23bba134c8fa108a05e21baa50f9b79d8c8c5ffc846bd733a0 -size 59470 diff --git a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/08783c875dd39684fee7f2a40b584c64_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/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_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/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/185df94f4a6a5245323255e844a30ec0_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/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/253600420ae7bd7d0119563b895cbf8a_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/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/2a9f9c6f1dc9e5b232d69c43882c83ab_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/2a9f9c6f1dc9e5b232d69c43882c83ab_img.jpg deleted file mode 100644 index 4bc073cdaf1679a16cd2aba3b2bd24d4abed54e3..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/2a9f9c6f1dc9e5b232d69c43882c83ab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6b9c9f61dbd6cb092401990dbd057d52151fb7d0a2487d1db6f21f9bf08fa68d -size 47354 diff --git a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/327ba94498e3381cf08eb41e3fd3d77f_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/327ba94498e3381cf08eb41e3fd3d77f_img.jpg deleted file mode 100644 index 0c0a927b7385a7e12f6dcfae718673efd4b05475..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/327ba94498e3381cf08eb41e3fd3d77f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c2f25724e04b56bff8f1f6d0fbbffb5350b68e4d087eaca4c52f9f220503ee3 -size 51637 diff --git a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/38222c3ae003223a67635bfcc6950fbb_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/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg deleted file mode 100644 index 24403a203dcb4019a205b07f56e392e8acf68906..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/3fa8bfee86764e3c3a1a6fbbe61bbd52_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b896eaf55ddd8f6d67aa2b372f86a79aedadf51718078b69f4d1f161e860eead -size 21943 diff --git a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.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/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/7efae06af3af43ffe5d4b956a679cf54_img.jpg deleted file mode 100644 index 4bcd56121a06f68ab2682501959056972949bfab..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/7efae06af3af43ffe5d4b956a679cf54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ed4e8a40da732f4a4f226213f0d8c355a87f831bc1e511de197b9ff65348d9e -size 137020 diff --git a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg deleted file mode 100644 index 8b049d075553c7376df9ac0c6a14c110ec0f161a..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:62614373b98641c45b3b8dcd68ab8598f985432d43f80fab406324ec5ddafc25 -size 54916 diff --git a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/854df8ad60507803253274673f9062cf_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/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/89100a6476d1d96f22c192db16502fec_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/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/a28ab03366399b5e0a61445bc57e3724_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/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/b0d4609bc46c2d88a8318706bb5321f7_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/b0d4609bc46c2d88a8318706bb5321f7_img.jpg deleted file mode 100644 index a010dda235938cd1c6334b2e7762115096067565..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/b0d4609bc46c2d88a8318706bb5321f7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ca2f70a79a9ef6eb4425de47db98dcd5abaa90462689bc14062f0e91a09f6b54 -size 23286 diff --git a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg deleted file mode 100644 index 73650c1553da56767f4a48f15c18c46d24970133..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/c0e88e4bd3a209b66ee7cb67e1cec2be_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8158cd9a4a8c8c230a9c0d0c8ede649c5b45497d85fd0939c8eab2daed2e0eac -size 59260 diff --git a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg deleted file mode 100644 index 93bd4a6413efd01f210f7c1109edaea018ac4656..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f45e2f60c56c6aefb215413cd241562457a29f983715bbff8ac68d9e6ef58cec -size 73883 diff --git a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/cab0834804fb031b43865554cc8d06ab_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/cab0834804fb031b43865554cc8d06ab_img.jpg deleted file mode 100644 index 760144b014e67b0131aee63fac492ea512d4ddbe..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/cab0834804fb031b43865554cc8d06ab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6ada35bc06aa7f6b579324c12fb4a32a93c09e584a0bd657ba9299ef698446b4 -size 177390 diff --git a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.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/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/e511e373339b5f948f239b19e0c37dd4_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/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg deleted file mode 100644 index 982596be0bcd2a75644295d39b205558c3ae5381..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0d7a8ee96ef104a97f03eb70830a2a40a12c917c3b8c5a16d26f5393bba70691 -size 195143 diff --git a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.D2GAP.0-R005-v03.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/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/doc.md b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/doc.md deleted file mode 100644 index fa02486869f46a97d843242ff59612bf1d30e47f..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/doc.md +++ /dev/null @@ -1,18011 +0,0 @@ - - -![O-RAN ALLIANCE logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) - -The logo for the O-RAN ALLIANCE, featuring a colorful circular icon to the left of the text "O-RAN" in blue, with "ALLIANCE" in smaller blue letters underneath. - -O-RAN ALLIANCE logo - -# --- **O-RAN Work Group 5 (F1/W1/E1/X2/Xn/D2 Interfaces Work Group)** - -# **Interoperability Test Specification (IOT)** - -Copyright © 2025 by 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. - -# Contents - -| | | -|-------------------------------------------------------------------------------------------------------------|----| -| Chapter 1 Introductory Material..... | 7 | -| 1.1 Foreword..... | 7 | -| 1.1a Modal verbs terminology..... | 7 | -| 1.2 Scope..... | 7 | -| 1.2.1 General..... | 7 | -| 1.2.2 Applicability to O-RAN interoperability badging procedures..... | 7 | -| 1.3 References..... | 8 | -| 1.3.1 Normative references..... | 8 | -| 1.3.2 Informative references..... | 9 | -| 1.4 Definition of terms, symbols and abbreviations..... | 9 | -| 1.4.1 Terms..... | 9 | -| 1.4.1a Symbols..... | 9 | -| 1.4.2 Abbreviations..... | 9 | -| Chapter 2 Interoperability Measurements..... | 10 | -| 2.1 Interoperability Test Definitions..... | 10 | -| 2.1.1 Test Configurations..... | 10 | -| 2.1.1.1 Device Under Test (DUT) and System Under Test (SUT)..... | 10 | -| 2.1.1.2 Testing Tools..... | 12 | -| 2.1.1.3 Assumptions..... | 20 | -| 2.1.1.4 Specifications to be used for testing..... | 21 | -| 2.1.1.5 Standard Test Configuration..... | 21 | -| 2.2 X2 Interoperability Test Cases..... | 21 | -| 2.2.1 X2 C-Plane IOT Test Cases..... | 23 | -| 2.2.1.1 EN-DC X2 Setup (eNB initiated)..... | 23 | -| 2.2.1.2 EN-DC X2 Setup (en-gNB initiated)..... | 24 | -| 2.2.1.3 Reset (eNB initiated)..... | 25 | -| 2.2.1.4 Reset (en-gNB initiated)..... | 26 | -| 2.2.1.5 Partial Reset (MeNB initiated)..... | 27 | -| 2.2.1.6 Partial Reset (en-gNB initiated)..... | 28 | -| 2.2.1.7 Secondary Node Addition (Option 3x)..... | 29 | -| 2.2.1.8 Secondary Node Release (MN initiated, Option 3x)..... | 32 | -| 2.2.1.9 Secondary Node Release (SN initiated, Option 3x)..... | 34 | -| 2.2.1.10 Secondary Node Change (MN initiated, Option 3x)..... | 36 | -| 2.2.1.11 Secondary Node Change (SN initiated, Option 3x)..... | 38 | -| 2.2.1.12 Inter-Master Node Handover (without SN Change, Option 3x)..... | 41 | -| 2.2.1.13 Master Node to eNB Change..... | 43 | -| 2.2.1.14 PCell change (Intra MN) (MN initiated)..... | 45 | -| 2.2.1.15 PSCell Change using SRB1 for RRC Reconfiguration – full configuration option..... | 48 | -| 2.2.1.16 PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option..... | 50 | -| 2.2.1.17 Served NR cell information Update (en-gNB initiated)..... | 52 | -| 2.2.1.18 Security Key Change (MN initiated)..... | 54 | -| 2.2.1.19 Measurement Gap Coordination Procedure (MN initiated)..... | 56 | -| 2.2.1.20 Measurement Gap Coordination for per FR1 or per UE gap Procedure (SN initiated)..... | 58 | -| 2.2.1.21 Measurement Gap Coordination for per FR2 gap (with MN involvement) Procedure (SN initiated)..... | 60 | -| 2.2.1.22 UL Configuration Update Procedure (SN initiated)..... | 62 | -| 2.2.1.23 Addition of SN terminated split bearer (MN initiated)..... | 64 | -| 2.2.1.24 Removal of SN terminated split bearer (MN initiated)..... | 67 | -| 2.2.1.25 Bearer type change from SN terminated split bearer to SN terminated MCG bearer (MN initiated)..... | 69 | -| 2.2.1.26 Bearer type change from SN terminated MCG bearer to SN terminated split bearer (MN initiated)..... | 71 | -| 2.2.1.27 Bearer type change from SN terminated split bearer to SN terminated MCG bearer (SN initiated)..... | 74 | -| 2.2.1.28 E-UTRA - NR Cell Resource Coordination (MN initiated, Option 3x/3a)..... | 76 | -| 2.2.1.29 E-UTRA - NR Cell Resource Coordination (SN initiated, Option 3x/3a)..... | 78 | - -| | | | -|----------|------------------------------------------------------------------------------------------------------------|-----| -| 2.2.1.30 | Allowed Band Combination list update (MN initiated)..... | 79 | -| 2.2.1.31 | Configured Band Combination update by PSCell/SCell change (SN initiated)..... | 81 | -| 2.2.1.32 | SCG config query (MN initiated)..... | 82 | -| 2.2.1.33 | Full Reconfiguration (SN initiated)..... | 83 | -| 2.2.1.34 | UE measurement transfer..... | 85 | -| 2.2.1.35 | Inter-Master Node Handover (with SN change, option 3x)..... | 87 | -| 2.2.1.36 | EN-DC Resource Status Reporting Initiation..... | 90 | -| 2.2.1.37 | EN-DC Resource Status Reporting..... | 91 | -| 2.2.1.38 | Change of QCI (MN initiated)..... | 93 | -| 2.2.1.39 | Measurement ID Coordination (MN initiated)..... | 94 | -| 2.2.1.40 | DRB ID change/Security Key change (SN initiated)..... | 96 | -| 2.2.1.41 | Measurement ID Coordination (SN initiated)..... | 98 | -| 2.2.2 | X2 U-Plane IOT Test Cases..... | 100 | -| 2.2.2.1 | Node behaviour of the corresponding node with RLC-AM and/or RLC-UM..... | 100 | -| 2.2.2.2 | General for Elements for the NR user plane protocols with RLC-AM and/or RLC-UM..... | 102 | -| 2.2.2.3 | Report Polling with RLC-AM and/or RLC-UM..... | 104 | -| 2.2.2.4 | Buffer discard indication with RLC-AM and/or RLC-UM..... | 106 | -| 2.2.2.5 | User data existence flag with RLC-AM and/or RLC-UM..... | 108 | -| 2.2.2.6 | Assistance Information Report polling with RLC-AM and/or RLC-UM..... | 109 | -| 2.2.2.7 | Radio quality assistance information with RLC-AM and/or RLC-UM..... | 111 | -| 2.2.2.8 | DL report NR PDCP PDU SN with RLC-AM..... | 113 | -| 2.3 | F1 Interoperability Test Cases..... | 114 | -| 2.3.1 | F1 C-Plane IOT Test Cases..... | 119 | -| 2.3.1.1 | Partial Reset (MeNB initiated)..... | 119 | -| 2.3.1.2 | Secondary Node Addition (Option 3x)..... | 120 | -| 2.3.1.3 | Secondary Node Release (MN initiated, Option 3x)..... | 122 | -| 2.3.1.4 | Secondary Node Release (SN initiated, Option 3x)..... | 124 | -| 2.3.1.5 | Secondary Node Change (MN initiated, Option 3x)..... | 126 | -| 2.3.1.6 | Secondary Node Change (SN initiated, Option 3x)..... | 128 | -| 2.3.1.7 | Inter-Master Node Handover (without SN Change, Option 3x)..... | 130 | -| 2.3.1.8 | Master Node to eNB Change..... | 132 | -| 2.3.1.9 | PSCell Change using SRB1 for RRC Reconfiguration – full configuration option (Inter gNB-DU scenario)..... | 134 | -| 2.3.1.10 | PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option (Inter gNB-DU scenario)..... | 135 | -| 2.3.1.11 | Intra gNB-DU PSCell Change using SRB1 for RRC Reconfiguration..... | 137 | -| 2.3.1.12 | F1 Setup for EN-DC..... | 139 | -| 2.3.1.13 | gNB-DU Configuration Update for EN-DC..... | 140 | -| 2.3.1.14 | gNB-CU Configuration Update for EN-DC..... | 142 | -| 2.3.1.15 | F1 Setup for NR Stand-Alone..... | 143 | -| 2.3.1.16 | gNB-DU Configuration Update for NR Stand-Alone..... | 144 | -| 2.3.1.17 | gNB-CU Configuration Update for NR Stand-Alone..... | 146 | -| 2.3.1.18 | Paging (CN-initiated)..... | 147 | -| 2.3.1.19 | UE context creation (service request)..... | 148 | -| 2.3.1.20 | UE context creation (registration request)..... | 149 | -| 2.3.1.21 | UE Context Release..... | 150 | -| 2.3.1.22 | gNB-CU Initiated UE Context Modification (SCell to be setup/removed)..... | 153 | -| 2.3.1.23 | gNB-CU Initiated UE Context Modification (DRB to be setup)..... | 155 | -| 2.3.1.24 | gNB-CU Initiated UE Context Modification (DRB to be released)..... | 156 | -| 2.3.1.25 | Reset (gNB-DU initiated) for EN-DC..... | 157 | -| 2.3.1.26 | Reset (gNB-CU initiated) for EN-DC..... | 159 | -| 2.3.1.27 | Partial Reset (gNB-DU initiated) for EN-DC..... | 160 | -| 2.3.1.28 | Partial Reset (gNB-CU initiated) for EN-DC..... | 162 | -| 2.3.1.29 | Reset (gNB-CU initiated) for NR Stand-Alone..... | 163 | -| 2.3.1.30 | Reset (gNB-DU initiated) for NR Stand-Alone..... | 164 | -| 2.3.1.31 | Intra gNB-DU, Intra Cell Handover..... | 165 | -| 2.3.1.32 | Intra gNB-DU, Inter Cell Handover..... | 167 | -| 2.3.1.33 | Inter gNB-DU Handover..... | 168 | -| 2.3.1.34 | Inter RAT Handover to LTE..... | 170 | - -- 2.3.1.35 RRC Connection Re-establishment (Intra gNB-DU)..... 172 -- 2.3.1.36 RRC Connection Re-establishment (Inter gNB-DU)..... 173 -- 2.3.1.37 RRC connected to RRC inactive..... 175 -- 2.3.1.38 RRC inactive to RRC connected, Intra gNB-CU..... 176 -- 2.3.1.39 S-NG-RAN Node Addition procedure..... 178 -- 2.3.1.40 Resource Status Reporting Initiation..... 179 -- 2.3.1.41 Resource Status Reporting..... 180 -- 2.3.1.42 Inter-Master Node Handover (with SN Change, Option 3x)..... 181 -- 2.3.1.43 Allowed Band Combination list update (MN initiated)..... 183 -- 2.3.1.44 SCG config query (MN initiated) for EN-DC..... 184 -- 2.3.1.45 gNB-DU initiated UE Context Modification (DRB to be released)..... 186 -- 2.3.1.46 Inter RAT Handover to NR..... 187 -- 2.3.1.47 gNB-CU initiated UE Context Modification (DRX cycle activation/deactivation)..... 189 -- 2.3.1.48 gNB-CU initiated UE Context Modification (DRB to be modified)..... 191 -- 2.3.1.49 M-NG-RAN node initiated SN modification..... 192 -- 2.3.1.50 NG-RAN Node Configuration Update..... 208 -- 2.3.1.51 Write-Replace Warning..... 209 -- 2.3.1.52 System Information Delivery for NR Stand-Alone..... 210 -- 2.3.1.53 S-NG-RAN node initiated SN modification with MN involvement..... 211 -- 2.3.1.54 Master Node to gNB Change..... 222 -- 2.3.1.55 Inter-Master Node Handover Without SN Change for NR-DC..... 224 -- 2.3.1.56 SN Initiated SN Change for NR-DC..... 226 -- 2.3.1.57 MN initiated SN Change..... 228 -- 2.3.1.58 Full Reconfiguration (SN initiated)..... 229 -- 2.3.1.59 Change of QCI (MN initiated)..... 231 -- 2.3.1.60 Security Key change (MN initiated) for EN-DC..... 232 -- 2.3.1.61 UL Configuration Update Procedure (SN initiated)..... 234 -- 2.3.1.62 Void..... 235 -- 2.3.1.63 RRC connection re-establishment (inter gNB-CU)..... 236 -- 2.3.1.64 gNB-CU initiated UE Context Modification (UE AMBR (for UL) modification)..... 237 -- 2.3.1.65 Inter gNB Handover for SA..... 239 -- 2.3.1.66 S-NG-RAN node Initiated SN modification without MN involvement..... 240 -- 2.3.1.67 M-NG-RAN node initiated S-NG-RAN Node Release without keeping UE..... 247 -- 2.3.1.68 M-NG-RAN node initiated S-NG-RAN Node Release with keeping UE..... 249 -- 2.3.1.69 S-NG-RAN node initiated S-NG-RAN Node Release..... 250 -- 2.3.1.70 PDU Session Establishment..... 252 -- 2.3.1.71 RRC Inactive to RRC Connected, Inter gNB-CU..... 254 -- 2.3.1.72 Measurement ID Coordination (MN initiated)..... 256 -- 2.3.1.73 New QoS Flow with Explicit NAS Signalling..... 257 -- 2.3.1.74 PCell change (Intra MN) (MN initiated)..... 259 -- 2.3.1.75 DRB ID change/Security Key change (SN initiated)..... 260 -- 2.3.1.76 Measurement ID Coordination (SN initiated)..... 262 -- 2.3.1.77 Release of QoS Flow with Explicit Signalling..... 263 -- 2.3.1.78 PDU session establishment after signalling-only connection..... 265 -- 2.3.1.79 Inter-Master Node Handover with SN Change for NR-DC..... 266 -- 2.3.1.80 gNB-DU initiated UE Context Modification (DRB to be modified)..... 268 -- 2.3.1.81 Addition of SN terminated split bearer (MN initiated)..... 270 -- 2.3.1.82 Removal of SN terminated split bearer (MN initiated)..... 271 -- 2.3.1.83 Registration update without Follow-on request..... 273 -- 2.3.1.84 Measurement Gap Coordination Procedure (MN initiated)..... 274 -- 2.3.1.85 Measurement Gap Coordination for per FR1 or per UE gap Procedure (SN initiated)..... 276 -- 2.3.1.86 Intra gNB-DU Handover with L1/L2 Triggered Mobility (LTM)..... 277 -- 2.3.1.87 Intra gNB-DU PSCell Change using SRB3 for RRC Reconfiguration..... 279 -- 2.3.1.88 Inter gNB-DU PSCell Change using SRB3 for RRC Reconfiguration..... 281 -- 2.3.2 F1 U-Plane IOT Test Cases..... 283 - - 2.3.2.1 Node behaviour of the corresponding node for EN-DC with RLC-AM and/or RLC-UM..... 283 - - 2.3.2.2 Node behaviour of the corresponding node for SA with RLC-AM and/or RLC-UM..... 285 - - 2.3.2.3 Node behaviour of the corresponding node for NR-DC with RLC-AM and/or RLC-UM..... 286 - -| | | | -|----------|-----------------------------------------------------------------------------------------------|-----| -| 2.3.2.4 | General for Elements for the NR user plane protocols for EN-DC with RLC-AM and/or RLC-UM..... | 289 | -| 2.3.2.5 | General for Elements for the NR user plane protocols for SA with RLC-AM and/or RLC-UM..... | 292 | -| 2.3.2.6 | General for Elements for the NR user plane protocols for NR-DC with RLC-AM and/or RLC-UM..... | 294 | -| 2.3.2.7 | Report Polling for EN-DC with RLC-AM and/or RLC-UM..... | 298 | -| 2.3.2.8 | Report Polling for SA with RLC-AM and/or RLC-UM..... | 300 | -| 2.3.2.9 | Report Polling for NR-DC with RLC-AM and/or RLC-UM..... | 302 | -| 2.3.2.10 | Buffer discard indication for EN-DC with RLC-AM and/or RLC-UM..... | 305 | -| 2.3.2.11 | Buffer discard indication for SA with RLC-AM and/or RLC-UM..... | 307 | -| 2.3.2.12 | Buffer discard indication for NR-DC with RLC-AM and/or RLC-UM..... | 309 | -| 2.3.2.13 | User data existence flag for EN-DC with RLC-AM and/or RLC-UM..... | 311 | -| 2.3.2.14 | User data existence flag for SA with RLC-AM and/or RLC-UM..... | 313 | -| 2.3.2.15 | User data existence flag for NR-DC with RLC-AM and/or RLC-UM..... | 314 | -| 2.3.2.16 | Assistance Information Report polling for EN-DC with RLC-AM and/or RLC-UM..... | 316 | -| 2.3.2.17 | Assistance Information Report polling for SA with RLC-AM and/or RLC-UM..... | 318 | -| 2.3.2.18 | Assistance Information Report polling for NR-DC with RLC-AM and/or RLC-UM..... | 319 | -| 2.3.2.19 | Radio quality assistance information for EN-DC with RLC-AM and/or RLC-UM..... | 321 | -| 2.3.2.20 | Radio quality assistance information for SA with RLC-AM and/or RLC-UM..... | 323 | -| 2.3.2.21 | Radio quality assistance information for NR-DC with RLC-AM and/or RLC-UM..... | 325 | -| 2.3.2.22 | DL report NR PDCP PDU SN for EN-DC with RLC-AM..... | 327 | -| 2.3.2.23 | DL report NR PDCP PDU SN for SA with RLC-AM..... | 329 | -| 2.3.2.24 | DL report NR PDCP PDU SN for NR-DC with RLC-AM..... | 330 | -| 2.4 | Xn Interoperability Test Cases..... | 331 | -| 2.4.1 | Xn C-Plane IOT Test Cases..... | 334 | -| 2.4.1.1 | Xn Setup..... | 334 | -| 2.4.1.2 | Inter gNB Handover..... | 334 | -| 2.4.1.3 | S-NG-RAN Node Addition..... | 336 | -| 2.4.1.4 | M-NG-RAN node initiated SN modification..... | 339 | -| 2.4.1.5 | S-NG-RAN node initiated SN modification with MN involvement..... | 355 | -| 2.4.1.6 | S-NG-RAN node initiated SN modification without MN involvement..... | 368 | -| 2.4.1.7 | M-NG-RAN node initiated S-NG-RAN node Release without keeping UE..... | 374 | -| 2.4.1.8 | M-NG-RAN node initiated S-NG-RAN node Release with keeping UE..... | 376 | -| 2.4.1.9 | S-NG-RAN node initiated S-NG-RAN node Release..... | 378 | -| 2.4.1.10 | Resource Status Reporting Initiation..... | 380 | -| 2.4.1.11 | Resource Status Reporting..... | 381 | -| 2.4.1.12 | Master Node to gNB Change..... | 382 | -| 2.4.1.13 | Reset..... | 384 | -| 2.4.1.14 | Inter-Master Node Handover (Without SN Change)..... | 386 | -| 2.4.1.15 | Secondary Node Change (SN initiated)..... | 388 | -| 2.4.1.16 | NG-RAN Node Configuration Update..... | 390 | -| 2.4.1.17 | UE measurement transfer..... | 391 | -| 2.4.1.18 | MN initiated SN Change..... | 393 | -| 2.4.1.19 | RRc connection re-establishment (inter gNB-CU)..... | 395 | -| 2.4.1.20 | RRc Inactive to RRc Connected, Inter gNB-CU..... | 397 | -| 2.4.1.21 | Measurement Gap Coordination Procedure (MN initiated)..... | 399 | -| 2.4.1.22 | SN initiated Activity Notification..... | 400 | -| 2.4.1.23 | Inter-Master Node Handover (with SN Change)..... | 402 | -| 2.4.1.24 | Intra Master Node, intra gNB-DU intra Cell handover with Secondary Node change..... | 405 | -| 2.4.1.25 | Intra Master Node, intra gNB-DU inter Cell handover with Secondary Node change..... | 407 | -| 2.4.1.26 | Intra Master Node, inter gNB-DU handover with Secondary Node change..... | 409 | -| 2.4.2 | Xn U-Plane IOT Test Cases..... | 411 | -| 2.4.2.1 | Node behaviour of the corresponding node with RLC-AM and/or RLC-UM..... | 411 | -| 2.4.2.2 | General for Elements for the NR user plane protocols with RLC-AM and/or RLC-UM..... | 413 | -| 2.4.2.3 | Report Polling with RLC-AM and/or RLC-UM..... | 416 | -| 2.4.2.4 | Buffer discard indication with RLC-AM and/or RLC-UM..... | 418 | -| 2.4.2.5 | User data existence flag with RLC-AM and/or RLC-UM..... | 420 | -| 2.4.2.6 | Assistance Information Report polling with RLC-AM and/or RLC-UM..... | 421 | -| 2.4.2.7 | Radio quality assistance information with RLC-AM and/or RLC-UM..... | 423 | - -2.4.2.8 DL report NR PDCP PDU SN with RLC-AM..... 425 -Annex (informative)..... 427 - -# Chapter 1 Introductory Material - -## 1.1 Foreword - -This Technical Specification (TS) has been produced by WG5 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, ie, 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. - -### 1.1a 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.2 Scope - -### 1.2.1 General - -The present document specifies the interoperability testing (IOT) for the radio access network nodes from different vendors connected using the X2, F1 and Xn interfaces implemented in accordance with the NR C-Plane [2] and U-Plane [3] profiles. - -In this version of the specification: - -- X2 interoperability testing is focused on the eNB and en-gNB as the Devices under Tests (DUTs) -- F1 interoperability testing is focused on the en-gNB consisting of the gNB-CU and gNB-DU as the DUTs and also the gNB consisting of the same elements -- Xn interoperability testing is focused on the gNBs as the DUTs - -In case an SUT component DUT is replaced by a test tool or by a node emulator (see section 2.1.1.1), messages captured at standardised interfaces in the test configuration may be used to check compliance of a DUT against that part of the applicable technical standards exercised by the IOT TCs for that configuration. In such SUT configurations, interoperability between DUTs from different vendors cannot be tested. - -### 1.2.2 Applicability to O-RAN interoperability badging procedures - -The interoperability between network functions may be tested and verified by various activities between different DUT vendors. The outcome of such activities is documented in a test report and a badge may be awarded, according to the procedures described in [16]. - -This specification contains test cases that are applicable to one or several network configurations. Network configurations depend on the connected core network type (EPC or 5GC), on the selected radio access technology (LTE and NR) and on the (en-)gNB node architecture, ie, split into (en-)gNB-CU and (en-)gNB-DU or non-split (en-)gNB. Interoperability test activities and resulting reports and badges for the interfaces X2, Xn and F1, respectively, may refer to the below six network configurations: - -- NSA (EN-DC), non-split architecture -- NSA (EN-DC), split architecture -- SA, non-split architecture -- SA, split architecture -- SA including NR-DC, non-split architecture -- SA including NR-DC, split architecture - -The test cases applicable to one or more network configurations are mandatory to ensure interoperability between DUTs. The mapping table below contains the applicability of test cases to the above mentioned network configurations. Some few test cases which require availability of, for example, specific spectrum resources may be omitted from interoperability test activities. - -![Icon representing a mapping table, showing a green 'X' and a list icon.](af54a0b30d50f3f8620b331cdc59ae3a_img.jpg) - -Icon representing a mapping table, showing a green 'X' and a list icon. - -TC-mapping-toN -W-Configurations - -## 1.3 References - -### 1.3.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] Void -- [2] O-RAN.WG5.TS.C.1-v15.00 “NR C-Plane profile” -- [3] O-RAN.WG5.TS.U.0-v07.00 “NR U-Plane profile” -- [4] O-RAN.WG1.TS.OAD “RAN Architecture Description” -- [5] O-RAN.WG4.CUS.0-v04.00 “Control, User and Synchronization Specification” -- [6] O-RAN.WG5.Transport.0-v01.00 “Transport Specification” -- [7] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)" -- [8] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access" -- [9] 3GPP TS 36.211: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation" - -- [10] 3GPP TS 38.211: "NR; Physical channels and modulation" -- [11] 3GPP TS 38.214: "NR; Physical layer procedures for data" -- [12] 3GPP TS 36.423: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP)" -- [13] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification" -- [14] 3GPP TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification" -- [15] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)" -- [16] O-RAN.TIFG.Cert-Badge.0-v06.00 “Certification and Badging Processes and Procedures” -- [17] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification" -- [18] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification" - -### 1.3.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. - -- [i1] 3GPP TR 21.905: “Vocabulary for 3GPP Specifications” - -## 1.4 Definition of terms, symbols and abbreviations - -### 1.4.1 Terms - -For the purposes of the present document, the terms and given in 3GPP TR 21.905 [i1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [i1]. - -#### 1.4.1a Symbols - -- - -### 1.4.2 Abbreviations - -Abbreviations used in this specification refer to the ones defined in the referenced 3GPP specifications and WG5 specifications. - -# Chapter 2 Interoperability Measurements - -## 2.1 Interoperability Test Definitions - -### 2.1.1 Test Configurations - -Interoperability testing is performed to prove that the end-to-end functionality between the radio access network nodes is as per specified in the O-RAN NR C-Plane [2] and U-Plane [3] profiles specifications on which these components are based. This requires system level testing of the radio access network nodes requiring interoperability testing as an integrated system. - -Figure 2-1 shows the EN-DC Overall Architecture [2]. The en-gNB may consist of a gNB-CU and one or more gNB-DU(s). A gNB-CU and a gNB-DU is connected via the F1 interface. - -![Diagram of EN-DC Overall Architecture showing connections between MME/S-GW, en-gNB, and eNB nodes.](c2fc2621e8206d24427b56bcb2398fc0_img.jpg) - -The diagram illustrates the EN-DC Overall Architecture. At the top, two grey boxes represent the MME/S-GW. Below them, the EPC (Evolved Packet Core) is indicated by a bracket. The E-UTRAN (Evolved UTRAN) is also indicated by a bracket and contains three radio nodes: an en-gNB (top), and two eNBs (bottom). The en-gNB is shown as a composite node containing a gNB-CU and a gNB-DU connected by an F1 interface. Connections are as follows: - - -- S1-U (dashed green lines) from MME/S-GW to en-gNB and eNBs. -- S1 (solid green lines) from MME/S-GW to en-gNB and eNBs. -- X2-U (dashed green lines) between en-gNB and eNBs. -- X2 (solid blue lines) between en-gNB and eNBs, and between the two eNBs. - -Diagram of EN-DC Overall Architecture showing connections between MME/S-GW, en-gNB, and eNB nodes. - -Figure 2-1: EN-DC Overall Architecture - -Figure 2-2 shows the NG-RAN Overall Architecture [2]. - -![Diagram of NG-RAN Overall Architecture showing connections between AMF/UPF, gNB, and ng-eNB nodes.](b0211cee4b20034939d883ac0d70f696_img.jpg) - -The diagram illustrates the NG-RAN Overall Architecture. At the top, two grey boxes represent the AMF/UPF. Below them, the 5GC (5G Core) is indicated by a bracket. The NG-RAN (Next Generation RAN) is also indicated by a bracket and contains four radio nodes: two gNBs (top) and two ng-eNBs (bottom). Connections are as follows: - - -- NG (solid green lines) from AMF/UPF to gNBs and ng-eNBs. -- Xn (solid blue lines) between gNBs and ng-eNBs, and between the two ng-eNBs. - -Diagram of NG-RAN Overall Architecture showing connections between AMF/UPF, gNB, and ng-eNB nodes. - -Figure 2-2: NG-RAN Overall Architecture - -#### 2.1.1.1 Device Under Test (DUT) and System Under Test (SUT) - -The case where the DUTs for X2, F1 and Xn interoperability tests are provided by different vendors is the focus of this document, but the case where both are from the same vendor is also valid. - -Table 2-1 summarizes the DUTs and SUTs for X2, F1 and Xn interoperability testing scenarios. - -| IOT Interface | DUTs | | SUT | -|---------------|--------|--------|--------------------------------------------| -| | NE1 | NE2 | NE1, NE2 and interconnecting IOT Interface | -| X2 | eNB | en-gNB | eNB, en-gNB and X2 | -| F1 | gNB-CU | gNB-DU | gNB-CU, gNB-DU and F1 | -| Xn | gNB | gNB | gNB, gNB and Xn | - -NE: Network Element as per defined in [i1] - -**Table 2-1: DUTs and SUTs for X2, F1 and Xn Interoperability Testing** - -The test configurations will involve defining the cardinality between the X DUT NE1(s) and Y DUT NE2(s) as part of the test scenario which will determine the configuration required. The simplest test configuration involves a single DUT NE1 and a single DUT NE2 ie, X=Y=1. - -Figure 2-3, 2-4 and 2-5 show the SUT configurations for X2, F1 and Xn interoperability testing, respectively. - -External physical connections between the X DUT NE1(s) and Y DUT NE2(s) are out of scope of this specification. - -![Figure 2-3: SUT configuration for X2 IOT. A 'System Test' box contains two DUTs, DUT(eNB) and DUT(en-gNB), connected by a line labeled X:Y. Below the line is a double-headed arrow labeled X2 IOT. The entire box is labeled 'System Under Test (SUT)'.](8e14350b4b669119a3bdfca7869110ca_img.jpg) - -Figure 2-3: SUT configuration for X2 IOT. A 'System Test' box contains two DUTs, DUT(eNB) and DUT(en-gNB), connected by a line labeled X:Y. Below the line is a double-headed arrow labeled X2 IOT. The entire box is labeled 'System Under Test (SUT)'. - -**Figure 2-3: SUT configuration for X2 IOT** - -![Figure 2-4: SUT configuration for F1 IOT (for en-gNB or gNB). A 'System Test' box contains a dashed rectangle labeled (en-)gNB. Inside, DUT(gNB-CU) and DUT(gNB-DU) are connected by a vertical line labeled F1. To the left of the dashed box is a vertical double-headed arrow labeled X:Y. The box is labeled 'System Under Test (SUT)'.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) - -Figure 2-4: SUT configuration for F1 IOT (for en-gNB or gNB). A 'System Test' box contains a dashed rectangle labeled (en-)gNB. Inside, DUT(gNB-CU) and DUT(gNB-DU) are connected by a vertical line labeled F1. To the left of the dashed box is a vertical double-headed arrow labeled X:Y. The box is labeled 'System Under Test (SUT)'. - -**Figure 2-4: SUT configuration for F1 IOT (for en-gNB or gNB)** - -![Figure 2-5: SUT configurations for Xn IOT. A 'System Test' box contains two DUTs, DUT(gNB) and DUT(gNB), connected by a line labeled X:Y. Below the line is a double-headed arrow labeled Xn IOT. The entire box is labeled 'System Under Test (SUT)'.](b3c108e7145f2017957569d06ea359cb_img.jpg) - -Figure 2-5: SUT configurations for Xn IOT. A 'System Test' box contains two DUTs, DUT(gNB) and DUT(gNB), connected by a line labeled X:Y. Below the line is a double-headed arrow labeled Xn IOT. The entire box is labeled 'System Under Test (SUT)'. - -**Figure 2-5: SUT configurations for Xn IOT** - -#### 2.1.1.2 Testing Tools - -One of the key objectives of interoperability testing is to validate the functionality of production grade DUTs. Hence it is important to ensure that the DUTs are not negatively impacted with the utilization of internal functions solely to support interoperability testing, ie, DUTs are not expected to be testing tools when deployed in production networks and therefore DUTs should not be used as testing tools during interoperability tests. - -Interoperability tests are performed with a set of testing tools which are used to both apply active stimulus and as well as passive monitoring and measurements of the DUTs. - -##### 2.1.1.2.1 Testing Tools Summary - -Table 2-2 shows a summary listing of the testing tools and the requirements of each of these testing tools for X2, F1 and Xn interfaces interoperability testing. - -| No. | Testing tool | Requirements | X2 IOT | F1 IOT | Xn IOT | -|-----|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|--------|--------| -| 1 | Test UEs and/or UE emulator | Required: used to support all test cases which require UE interactions.
Optional: used to help simplify test results analysis | Yes | Yes | Yes | -| 2 | Core or Core emulator | Required: used to terminate Test UEs and/or UE emulator NAS protocol and to support core network procedures required for RAN testing. | Yes | Yes | Yes | -| 3 | eNB or eNB emulator | Required: used to support Master Node (eNB) to eNB change test case for X2 interoperability testing. Noting that the Master Node (eNB) is the DUT while the eNB or eNB emulator is used to support the test case.

Required: used to support F1 interoperability testing of the gNB-CU and gNB-DU with both DUTs belonging to the en-gNB. | Yes | Yes | No | -| 4 | Application Test Server | Required: used for user plane transfer test(s) between the Application Test Server and Test UEs and/or UE emulator. | Yes | Yes | Yes | -| 5 | Protocol Analyzer | Required: used for test results verification and troubleshooting purposes. | Yes | Yes | Yes | -| 6 | Network Impairment Emulator | Required: used for test cases which require selective packet discards over the X2, F1 and Xn interface for X2, F1 and Xn interoperability testing, respectively. | Yes | Yes | Yes | -| 7 | O-DU & O-RU emulator | Optional: used to help simplify connectivity to the en-gNB and gNB with F1 split for X2 and Xn interoperability testing, respectively.

The O-DU & O-RU emulator belong to the en-gNB and gNB functionality in the X2 and Xn interoperability test scenarios, respectively. | Yes | No | Yes | -| 8 | O-RU emulator | Optional: used to help simplify connectivity to | Yes | Yes | Yes | - -| | | | | | | -|----|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|-----|-----| -| | |

the eNB and en-gNB with Open fronthaul (OFH) split for X2 interoperability testing; gNB-DU and gNB with OFH split for F1 and Xn interoperability testing, respectively.

The O-RU emulator belongs to the eNB and en-gNB functionality in the X2 interoperability test scenario.

The O-RU emulator belongs to the gNB-DU and gNB functionality in the F1 and Xn interoperability test scenarios, respectively.

| | | | -| 9 | Test results and KPIs reporting | Optional: used to help simplify test results analysis. | Yes | Yes | Yes | -| 10 | Test UE logging tool | Optional: used to help simplify test results analysis. | Yes | Yes | Yes | - -**Table 2-2: Testing Tools Summary and Applicability to X2, F1 and Xn Interoperability Testing** - -##### 2.1.1.2.2 Testing Tools Details - -This section describes details of the testing tools listed in Table 2-2. - -In any test configuration that illustrates a DU, as an option as noted in Table 2-2, that DU may be substituted by O-DU and O-RU functions. Such substitution has no effect on the 3GPP interfaces that are the sole target of this specification. In all such cases the O-RU function may be performed by real or emulated equipment (No. 8 in Table 2-2). Additionally, where the F1 interface is not the object of the test, both O-DU and O-RU functions may be performed by an emulator (No 7 in Table 2-2). - -Given that the objective of this test specification is to validate the interoperability between the radio access network nodes over the X2, F1 and Xn interface and protocols, the test setup can be simplified if there can be alternative means of connecting the Test UEs and/or UE emulator to the DUTs namely the eNB, en-gNB and gNB in the various interoperability test setups. This can be accomplished if the DU or DU emulator is connected via cable to the UE or UE emulator where that DU can optionally be an O-DU and O-RU or respective emulator. - -###### Active stimulus testing tools - -This paragraph shows details of active stimulus testing tools for X2, F1 and Xn interfaces interoperability testing. - -NOTE: The number allocated to each testing tool below corresponds to the number on the list in Table 2-2. - -- **No. 1: Test UEs and/or UE emulator:** used to generate stateful UE connections and traffic to validate the DUTs implementation of the X2, F1 and Xn interface protocols as these are stimulated by the 3GPP upper layer protocols: - - Required so that the DUTs do not need to be put into a “test mode” which does not happen in live deployments - - Test UEs and UE emulator will be required to support EN-DC operations for X2 and F1 interoperability testing. Test UEs and UE emulator will be required to support Standalone (SA) mode for Xn interoperability testing - - Test UEs will require SIM cards which are pre-provisioned with subscriber profiles. UEs used for testing can be simpler to setup but given that these Test UEs are designed as commercial UEs with possibly certain diagnostic functions enabled for logging purposes, they are limited in terms of configurability - -- o UE emulator will require SIM profile configuration with the subscriber's profiles. UE emulator can be used in test scenarios which require multiple UE sessions, more flexibility and configurability to help drive test scenarios -- o RF connection between the Test UEs or UE emulator with the DUTs namely the eNB, en-gNB and gNB will be either through cabled connection or Over-The-Air (OTA) -- **No. 2: Core or Core emulator:** used to terminate stateful NAS sessions with Test UEs and/or UE emulator and stateful S1 or NG sessions with the DUTs: - - o Required so that the DUTs do not need to be put into a “test mode” which does not happen in live deployments - - o Core or Core emulator will be required to support EPC with EN-DC capabilities for X2 and F1 interoperability testing. Core or Core emulator will be required to support 5GC with SA capabilities for Xn and F1 interoperability testing - - o External physical connection between Core or Core emulator and eNB, en-gNB and gNB is out of scope of this specification -- **No. 4: Application Test Server:** An endpoint application test traffic emulator which can be used to originate and/or terminate various traffic streams to or from the Test UEs or UE emulator, respectively. It may provide one or more of these options: - - o Stateful traffic, eg, TCP, TWAMP - - o Stateless traffic, eg, UDP - - o Required to place traffic load on the DUT - - o External physical connection between Application Test Server and Core or Core emulator is out of scope of the specification - -Active stimulus testing tools are connected to DUTs. The following describes the interoperability test setup for X2, F1, and Xn. - -###### X2 IOT Setup - -Figure 2-6 shows the test setup for X2 interoperability testing with the DUTs eNB, en-gNB and their connections to active stimulus testing tools No. 1, 2, and 4. - -![Diagram of WG5 Interoperability Test (IOT) System Test Setup for X2. The diagram shows a central 'SUT' (System Under Test) box containing an 'eNB' and an 'en-gNB' connected by an 'X2' interface. Above the SUT, an 'Apps Test Server' and an 'EPC (EN-DC) (Emulator)' are connected via a 'Cabled (Ethernet)' connection. Below the SUT, a 'UE (EN-DC) (Emulator)' is connected via an 'RF (Cabled or OTA)' connection. The entire setup is labeled 'WG5 Interoperability Test (IOT) System Test Setup for X2'. A legend at the bottom identifies the 'DUT' (Device Under Test) and 'Test Equipment (actual or emulator)'.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) - -Diagram of WG5 Interoperability Test (IOT) System Test Setup for X2. The diagram shows a central 'SUT' (System Under Test) box containing an 'eNB' and an 'en-gNB' connected by an 'X2' interface. Above the SUT, an 'Apps Test Server' and an 'EPC (EN-DC) (Emulator)' are connected via a 'Cabled (Ethernet)' connection. Below the SUT, a 'UE (EN-DC) (Emulator)' is connected via an 'RF (Cabled or OTA)' connection. The entire setup is labeled 'WG5 Interoperability Test (IOT) System Test Setup for X2'. A legend at the bottom identifies the 'DUT' (Device Under Test) and 'Test Equipment (actual or emulator)'. - -Figure 2-6: X2 IOT setup - -In addition to the above active stimulus testing tools, the following testing tools are also used for certain X2 IOT tests. - -- **No. 3: eNB or eNB emulator:** used to support Master Node (eNB) (DUT) to eNB change test case: - - Required so that the Master Node (eNB) which is the DUT does not need to be put into a “test mode” which does not happen in live deployments - - External physical connection between eNB or eNB emulator and Master Node (eNB) is out of scope of this specification -- **No. 6: Network Impairment Emulator:** used to create impairments such as packet discards over the network interfaces. This emulator is connected in an in-line mode such as between the eNB and en-gNB over the X2 interface - -###### **F1 IOT setup (EN-DC)** - -Figure 2-7 shows the test setup for F1 interoperability testing with the en-gNB consisting of DUTs gNB-CU, gNB-DU and their connections to active stimulus testing tools No. 1, 2, and 4. - -![WG5 Interoperability Test (IOT) System Test Setup for en-gNB F1 diagram](9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg) - -The diagram illustrates the test setup for F1 interoperability testing. A central dashed box labeled 'WG5 Interoperability Test (IOT) System Test Setup for en-gNB F1' contains the following components: - - -- Apps Test Server** and **EPC (EN-DC) (Emulator)** are connected to a **Cabled (Ethernet)** interface. -- The **Cabled (Ethernet)** interface is connected to an **eNB**. -- The **eNB** is connected to the **SUT** (System Under Test) via an **X2** interface. -- The **SUT** is an **en-gNB** containing a **gNB-CU** and a **gNB-DU** connected by an **F1** interface. -- An **IOT** (Interoperability Test) tool is connected to the **F1** interface between the gNB-CU and gNB-DU. -- The **gNB-DU** is connected to a **RF (Cabled or OTA)** interface. -- The **RF (Cabled or OTA)** interface is connected to a **UE (EN-DC) (Emulator)**. - - Below the dashed box, a legend indicates that the **DUT** (Device Under Test) is represented by a blue box, and **Test Equipment (actual or emulator)** is represented by a grey box. - -WG5 Interoperability Test (IOT) System Test Setup for en-gNB F1 diagram - -**Figure 2-7: F1 IOT setup** - -In addition to the above active stimulus testing tools, following testing tools are also used for certain F1 IOT tests. - -- **No. 3: eNB or eNB emulator:** used to support F1 interoperability testing of the gNB-CU and gNB-DU with both DUTs belonging to the en-gNB: - - Required so that the DUTs (gNB-CU, gNB-DU) do not need to be put into a “test mode” which does not happen in live deployments - - External physical connection between the eNB or the eNB emulator and the gNB-CU is out of scope of this specification -- **No. 6: Network Impairment Emulator:** used to create impairments such as packet discards over the network interfaces. This emulator is connected in an in-line mode such as between the gNB-CU and gNB-DU over the F1 interface - -###### **F1 IOT setup (SA)** - -Figure 2-7a shows the test setup for F1 interoperability testing with the gNB consisting of DUTs gNB-CU, gNB-DU and their connections to active stimulus testing tools No. 1, 2, and 4. - -![Figure 2-7a: F1 IOT setup diagram](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) - -**WG5 Interoperability Test (IOT) System Test Setup for gNB F1** - -``` - -+-----------------------------------------------------------------+ -| Apps Test Server | -| 5GC (Emulator) | -+-----------------------------------------------------------------+ - | (Cabled Ethernet) -+-------|---------------------------------------------------------+ -| SUT | gNB | -| | +-----------------------------------------------------+ | -| | | gNB-CU | | -| | +-----------------------------------------------------+ | -| | | F1 | | -| | +-----------------------------------------------------+ | -| | | gNB-DU | | -| | +-----------------------------------------------------+ | -+-------|---------------------------------------------------------+ - | (RF Cabled or OTA) -+-----------------------------------------------------------------+ -| UE (SA) (Emulator) | -+-----------------------------------------------------------------+ - -Legend: -[Blue Box] = DUT -[Grey Box] = Test Equipment (actual or emulator) - -``` - -Figure 2-7a: F1 IOT setup diagram - -**Figure 2-7a: F1 IOT setup** - -In addition to the above active stimulus testing tools, following testing tools are also used for certain F1 IOT tests. - -- **No. 6: Network Impairment Emulator:** used to create impairments such as packet discards over the network interfaces. This emulator is connected in an in-line mode such as between the gNB-CU and gNB-DU over the F1 interface - -###### **F1 IOT setup (NR-DC)** - -Figure 2-7b shows the test setup for F1 interoperability testing with the MgNB and SgNB consisting of DUTs gNB-CU, gNB-DU and their connections to active stimulus testing tools No. 1, 2, and 4. - -![Figure 2-7b: F1 IOT setup diagram for NR-DC](b90144cfbb81a2d610d920240fda689d_img.jpg) - -**WG5 Interoperability Test (IOT) System Test Setup for NR-DC F1** - -``` - -+-----------------------------------------------------------------+ -| Apps Test Server | -| 5GC (Emulator) | -+-----------------------------------------------------------------+ - | (Cabled Ethernet) -+-------|---------------------------------------------------------+ -| SUT | MgNB SUT | SgNB | -| | +----------+ +----------+ | -| | | MgNB-CU |------- Xn -------| SgNB-CU | | -| | +----------+ +----------+ | -| | | F1 | F1 | -| | +----------+ +----------+ | -| | | MgNB-DU | | SgNB-DU | | -| | +----------+ +----------+ | -+-------|----------------------------------|----------------------+ - | (RF Cabled or OTA) | (RF Cabled or OTA) -+-----------------------------------------------------------------+ -| UE (NR-DC) (Emulator) | -+-----------------------------------------------------------------+ - -Legend: -[Blue Box] = DUT -[Grey Box] = Test Equipment (actual or emulator) - -``` - -Figure 2-7b: F1 IOT setup diagram for NR-DC - -**Figure 2-7b: F1 IOT setup** - -In addition to the above active stimulus testing tools, following testing tools are also used for certain F1 IOT tests. - -- **No. 6: Network Impairment Emulator:** used to create impairments such as packet discards over the network interfaces. This emulator is connected in an in-line mode such as between the gNB-CU and gNB-DU over the F1 interface - -###### Xn IOT setup - -Figure 2-8 shows the test setup for Xn interoperability testing with the gNBs (DUTs) and their connections to active stimulus testing tools No. 1, 2, and 4. - -![WG5 Interoperability Test (IOT) System Test Setup for Xn diagram](df82d77a0d2637cbf2da9ea920a554fa_img.jpg) - -The diagram illustrates the 'WG5 Interoperability Test (IOT) System Test Setup for Xn'. It features a central 'SUT' (System Under Test) box containing two 'gNB' units connected by an 'Xn' interface. Above the gNBs, an 'Apps Test Server' and a '5GC (Emulator)' are connected via a 'Cabled (Ethernet)' link. Below the gNBs, a 'UE (SA) (Emulator)' is connected via an 'RF (Cabled or OTA)' link. The entire setup is labeled as 'Test Equipment (actual or emulator)'. The 'DUT' (Device Under Test) is indicated at the bottom. - -WG5 Interoperability Test (IOT) System Test Setup for Xn diagram - -Figure 2-8: Xn IOT setup - -In addition to the above active stimulus testing tools, the following testing tools are also used for certain Xn IOT tests. - -- **No. 6: Network Impairment Emulator:** used to create impairments such as packet discards over the network interfaces. This emulator is connected in an in-line mode such as between the gNB(s) and gNB(s) over the Xn interface - -Figure 2-9: VOID - -Figure 2-10: VOID - -Figure 2-11: VOID - -Figure 2-12: VOID - -Figure 2-12a: VOID - -Figure 2-13: VOID - -###### Passive monitoring and measurements testing tools - -This paragraph shows details of passive monitoring and measurements testing tools for X2, F1 and Xn interfaces interoperability testing. - -NOTE: The number allocated to each testing tool below corresponds to the number on the list in Table 2-2. - -- **No. 5: Protocol Analyzer:** used for protocol analysis and measurements of X2 and Xn interfaces C-Plane and U-Plane protocols; S1-U and NG-U interface protocols, and F1 interface C-Plane and U-Plane protocols: - - Test case validation and troubleshooting purposes which can help with test setup validation and root cause analysis for test cases which fail - - Monitoring traffic from the X2, F1, Xn, S1-U and NG-U interfaces typically through a tap or span port. Taps are typically preferred as span ports are less reliable but can be used if taps are not readily available in the test lab. Connectivity specifics (eg, number of 10/25/40/100 GE) is out of scope of this specification - -NOTE: If IPsec encryption (non-Null) is applied to the X2, F1, Xn, S1-U and NG-U interfaces, the Protocol Analyzer cannot be used to reliably analyze the procedures and protocols exchanged over these interfaces. Decryption of IPsec protected traffic for lab testing purpose can be possible but processing intensive particularly when dealing with dynamic security parameters - -- No.1 and 10 Test UE logging tool and/or UE emulator: used to produce measurements and logs: - - Measurements and KPIs logs for test case validation and reporting - - Diagnostics logs for troubleshooting purposes which can help with test setup validation and root cause analysis for failed test cases - - Diagnostics mode shall be enabled on the Test UEs for diagnostic logging purposes. Device logging tools shall be connected to the Test UEs for logging purposes - - UEs used for testing can be simpler to setup but given that these Test UEs are designed as commercial UEs, they are limited in terms of diagnostic logging capabilities due to limited processing and buffer space - - UE emulator can be used in test scenarios which require extensive diagnostics capabilities -- **No. 9: Test results and KPIs reporting** which can be provided through one or more of these options: - - UE logging tools which are connected to the Test UEs - - UE emulator reporting dashboard typically built in as part of the UE emulator solution - - External dashboard and reporting applications - -Passive monitoring and measurements testing tools are also connected to DUTs. Followings describe interoperability test setup for X2, F1, and Xn. - -###### X2 IOT setup - -Figure 2-14 shows the test setup for X2 interoperability testing with Passive measurements tools indicated. - -![Diagram of WG5 Interoperability Test (IOT) System Test Setup for X2. The diagram shows a 'SUT' (System Under Test) box containing an 'eNB' and an 'en-gNB' connected by an 'X2' interface. A 'Protocol Analyzer' is connected to the 'X2' interface. Above the SUT, an 'Apps Test Server' and an 'EPC (EN-DC) (Emulator)' are connected to the 'eNB'. Below the SUT, a 'Test Results & KPIs Logging' unit and a 'UE (EN-DC) (Emulator)' are connected to the 'eNB'. The 'eNB' and 'UE (EN-DC) (Emulator)' are part of the 'DUT' (Device Under Test). The 'DUT' is connected to 'Test Equipment (actual or emulator)'. The 'Protocol Analyzer' is also connected to the 'Test Results & KPIs Logging' unit.](77464a47f104d0d647b2414591137b64_img.jpg) - -Diagram of WG5 Interoperability Test (IOT) System Test Setup for X2. The diagram shows a 'SUT' (System Under Test) box containing an 'eNB' and an 'en-gNB' connected by an 'X2' interface. A 'Protocol Analyzer' is connected to the 'X2' interface. Above the SUT, an 'Apps Test Server' and an 'EPC (EN-DC) (Emulator)' are connected to the 'eNB'. Below the SUT, a 'Test Results & KPIs Logging' unit and a 'UE (EN-DC) (Emulator)' are connected to the 'eNB'. The 'eNB' and 'UE (EN-DC) (Emulator)' are part of the 'DUT' (Device Under Test). The 'DUT' is connected to 'Test Equipment (actual or emulator)'. The 'Protocol Analyzer' is also connected to the 'Test Results & KPIs Logging' unit. - -Figure 2-14: X2 IOT setup with Passive Measurement tools - -###### F1 IOT setup (EN-DC) - -Figure 2-15 shows the test setup for F1 interoperability testing with Passive measurements tools indicated for en-gNB scenarios. - -![Diagram of F1 IOT setup for en-gNB F1. The diagram shows a System Test Setup for en-gNB F1. It includes an Apps Test Server, EPC (EN-DC) (Emulator), eNB, SUT (en-gNB) containing gNB-CU and gNB-DU connected via F1, and UE (EN-DC) (Emulator). A Protocol Analyzer is connected to the eNB and the SUT. Test Results & KPIs Logging is connected to the Protocol Analyzer. The legend indicates DUT (blue) and Test Equipment (actual or emulator) (grey).](10781f43062bf3e9601a1e086710556c_img.jpg) - -**WG5 Interoperability Test (IOT) System Test Setup for en-gNB F1** - -The diagram shows a test architecture. At the top are grey boxes for "Apps Test Server" and "EPC (EN-DC) (Emulator)". Below them is a grey box for "eNB" connected to the EPC via a dashed line. To the right is a blue-outlined box labeled "SUT" containing "en-gNB", which further contains "gNB-CU" and "gNB-DU" connected by an "F1" interface with a double-headed arrow labeled "IOT". The eNB and SUT are connected via an "X2" interface. A grey box labeled "Protocol Analyzer" has solid lines connecting to the eNB-EPC link, the X2 interface, and the F1 interface. At the bottom, a grey box for "UE (EN-DC) (Emulator)" is connected to the eNB and SUT via dashed lines. A "Test Results & KPIs Logging" box is connected to the Protocol Analyzer and the UE Emulator. A legend at the bottom defines blue as "DUT" and grey as "Test Equipment (actual or emulator)". - -Diagram of F1 IOT setup for en-gNB F1. The diagram shows a System Test Setup for en-gNB F1. It includes an Apps Test Server, EPC (EN-DC) (Emulator), eNB, SUT (en-gNB) containing gNB-CU and gNB-DU connected via F1, and UE (EN-DC) (Emulator). A Protocol Analyzer is connected to the eNB and the SUT. Test Results & KPIs Logging is connected to the Protocol Analyzer. The legend indicates DUT (blue) and Test Equipment (actual or emulator) (grey). - -**Figure 2-15: F1 IOT setup with Passive measurements tools** - -###### F1 IOT Setup (SA) - -Figure 2-15a shows the test setup for F1 interoperability testing with Passive measurements tools indicated for gNB scenarios. - -![Diagram of F1 IOT setup for gNB. The diagram shows a System Test Setup for en-gNB F1. It includes an Apps Test Server, EPC (EN-DC) (Emulator), SUT (gNB) containing gNB-CU and gNB-DU connected via F1, and UE (SA) (Emulator). A Protocol Analyzer is connected to the SUT. Test Results & KPIs Logging is connected to the Protocol Analyzer. The legend indicates DUT (blue) and Test Equipment (actual or emulator) (grey).](40f30e4d577a17052f8b1e6dc802a0d8_img.jpg) - -**WG5 Interoperability Test (IOT) System Test Setup for en-gNB F1** - -This diagram is similar to Figure 2-15 but for Standalone (SA) mode. It features grey boxes for "Apps Test Server" and "EPC (EN-DC) (Emulator)" at the top. The "SUT" box is labeled "gNB" and contains "gNB-CU" and "gNB-DU" connected by an "F1" interface with an "IOT" measurement point. The SUT is connected to the EPC. A "Protocol Analyzer" is connected to the EPC-SUT link and the F1 interface. At the bottom, a grey box for "UE (SA) (Emulator)" is connected to the SUT. "Test Results & KPIs Logging" is connected to the Protocol Analyzer and the UE Emulator. The legend defines blue as "DUT" and grey as "Test Equipment (actual or emulator)". - -Diagram of F1 IOT setup for gNB. The diagram shows a System Test Setup for en-gNB F1. It includes an Apps Test Server, EPC (EN-DC) (Emulator), SUT (gNB) containing gNB-CU and gNB-DU connected via F1, and UE (SA) (Emulator). A Protocol Analyzer is connected to the SUT. Test Results & KPIs Logging is connected to the Protocol Analyzer. The legend indicates DUT (blue) and Test Equipment (actual or emulator) (grey). - -**Figure 2-15a: F1 IOT setup with Passive measurements tools gNB** - -###### Xn IOT setup - -Figure 2-16 shows the test setup for Xn interoperability testing with Passive measurements tools indicated. - -![Diagram of WG5 Interoperability Test (IOT) System Test Setup for Xn. The diagram shows a central 'SUT' (System Under Test) box containing two 'gNB' units connected by an 'Xn' interface. An 'IOT' (Interoperability Test) tool is connected to the Xn interface. Above the SUT, a '5GC (Emulator)' and an 'Apps Test Server' are connected to the gNBs. A 'Protocol Analyzer' is connected to the gNBs. Below the SUT, a 'UE (SA) (Emulator)' is connected to the gNBs. The entire setup is connected to 'Test Results & KPIs Logging'. Below the SUT box, a 'DUT' (Device Under Test) and 'Test Equipment (actual or emulator)' are shown.](523ab7b925beb555f88b2e1e1336974f_img.jpg) - -Diagram of WG5 Interoperability Test (IOT) System Test Setup for Xn. The diagram shows a central 'SUT' (System Under Test) box containing two 'gNB' units connected by an 'Xn' interface. An 'IOT' (Interoperability Test) tool is connected to the Xn interface. Above the SUT, a '5GC (Emulator)' and an 'Apps Test Server' are connected to the gNBs. A 'Protocol Analyzer' is connected to the gNBs. Below the SUT, a 'UE (SA) (Emulator)' is connected to the gNBs. The entire setup is connected to 'Test Results & KPIs Logging'. Below the SUT box, a 'DUT' (Device Under Test) and 'Test Equipment (actual or emulator)' are shown. - -Figure 2-16: Xn IOT setup with Passive measurement tools - -#### 2.1.1.3 Assumptions - -In this version of the specification, the following assumptions apply: - -1. **Management Plane** - DUTs are in service and running in normal operating state. M-Plane interactions between the DUTs and Service Management and Orchestration (SMO) are out of scope in this version of the specification. -2. **Synchronization Plane** - all the components including the DUTs and the Testing Tools are required to be synchronized to a common system time and master time source unless otherwise stated. S-Plane test setup details are out of scope in this version of the specification. -3. **Transport Plane** – transport aspects between the DUTs and between the DUTs to the Test Equipment are out of scope in this version of the specification, but the WG5 Transport Specification [6] can be used as a reference. Examples of transport aspects include Physical Connectivity Interface (eg, connectivity rates), Data Link Layer Interface (layer 2 eg, VLAN, QoS marking), Network Layer Interface (layer 3 eg, IP version), (layer 4 eg, SCTP), Security (eg, IPsec). -4. All wireline transport interfaces conform to ideal conditions (no impairments). -5. All wireless connections (air interface) conform to ideal conditions (no impairments) unless otherwise stated in test cases which may have requirements to impair the wireless connections in order to stimulate handover scenarios for example. -6. All wireless connections conform to ideal conditions (no impairments) and adopt 3GPP approaches for “ideal” RF environment test setup. -7. All DUTs comply with the same version or compatible versions of the O-RAN WG5 C-Plane [2] and U-Plane [3] profiles. -8. All elements in the interoperability test and the supporting test environment, where 3GPP support is relevant, comply with the same version or compatible versions of the 3GPP Specifications. - -#### 2.1.1.4 Specifications to be used for testing - -In this version of the specification, the following sets of specifications and releases/versions shall be supported - -- O-RAN WG5: - - NR C-Plane profile [2] - - NR U-Plane profile [3] -- 3GPP - - 3GPP Release and Version as listed in O-RAN WG5 NR C-Plane [2] and U-Plane [3] profiles specifications. It is important to ensure that all DUTs and Testing Tools use compatible release/version of the 3GPP specifications. - -#### 2.1.1.5 Standard Test Configuration - -Most interoperability tests will use a standard test configuration although individual tests are expected to deviate from this in some way. By defining the standard test configuration, an understanding of how the test setup is configured can be gained, thereafter examining individual tests can reveal the specific deviations from the standard test configuration and these specific deviations will be specified in each of the test cases - -1. The standard test setup involves a single DUT NE1 and a single DUT NE2 with DUT NE1 and DUT NE2 as specified in Table 2-1 in accordance with the interoperability test interfaces. Test cases which require more than a single DUT NE1 or DUT NE2 will specify the number of DUT NE1 and DUT NE2 required as part of the test case. -2. IPsec encryption of the interface(s) under test is optional. If IPsec encryption with non-NULL encryption is enabled as part of the test setup, it would not be possible to perform test verification using the Protocol Analyzer without the Protocol Analyzer performing IPsec decryption. Details about IPsec decryption is out of scope of this specification. - -## 2.2 X2 Interoperability Test Cases - -The following set of X2 IOT cases are defined in this version of the specification. - -| Test Case | Reference to O-RAN NR C-Plane profile [2] | -|--------------------------------------------------|-------------------------------------------| -| EN-DC X2 Setup (eNB initiated) | 4.1.1.1 | -| EN-DC X2 Setup (en-gNB initiated) | 4.1.1.2 | -| Reset (eNB initiated) | 4.1.2.1 | -| Reset (en-gNB initiated) | 4.1.2.2 | -| Partial Reset (MeNB initiated) | 4.1.4.1 | -| Partial Reset (en-gNB initiated) | 4.1.4.2 | -| Secondary Node Addition (Option 3x) | 5.1.1 | -| Secondary Node Release (MN initiated, Option 3x) | 5.2.1 | -| Secondary Node Release (SN initiated, Option 3x) | 5.2.2 | - -| | | -|-----------------------------------------------------------------------------------------------|---------| -| Secondary Node Change (MN initiated, Option 3x) | 5.3.1 | -| Secondary Node Change (SN initiated, Option 3x) | 5.3.2 | -| Inter-Master Node Handover (without SN Change, Option 3x) | 5.4.1 | -| Master Node to eNB Change | 5.5.1 | -| PCell change (Intra MN) (MN initiated) | 5.6.1 | -| PSCell Change using SRB1 for RRC Reconfiguration – full configuration option | 5.6.15 | -| PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option | 5.6.16 | -| Served NR cell information Update (en-gNB initiated) | 4.1.3.1 | -| Security Key Change Procedure (MN initiated) | 5.6.5 | -| Measurement Gap Coordination Procedure (MN initiated) | 5.6.6 | -| Measurement Gap Coordination for per FR1 or per UE gap Procedure (SN initiated) | 5.6.7 | -| Measurement Gap Coordination for per FR2 gap (with MN involvement) Procedure (SN initiated) | 5.6.8 | -| UL Configuration Update Procedure (SN initiated) | 5.6.9 | -| Addition of SN terminated split bearer (MN initiated) | 5.6.10 | -| Removal of SN terminated split bearer (MN initiated) | 5.6.11 | -| Bearer type change from SN terminated split bearer to SN terminated MCG bearer (MN initiated) | 5.6.12 | -| Bearer type change from SN terminated MCG bearer to SN terminated split bearer (MN initiated) | 5.6.13 | -| Bearer type change from SN terminated split bearer to SN terminated MCG bearer (SN initiated) | 5.6.14 | -| E-UTRA - NR Cell Resource Coordination (MN initiated, Option 3x/3a) | 5.8.1 | -| E-UTRA - NR Cell Resource Coordination (SN initiated, Option 3x/3a) | 5.8.2 | -| Allowed Band Combination list update (MN initiated) | 5.6.2 | -| Configured Band Combination update by PSCell/SCell change (SN initiated) | 5.6.3 | -| SCG config query (MN initiated) | 5.6.4 | -| Full Reconfiguration (SN initiated) | 5.6.22 | -| UE measurement transfer | 5.7.1 | -| Inter-Master Node Handover | 5.4.2 | -| EN-DC Resource Status Reporting Initiation | 4.1.8.1 | -| EN-DC Resource Status Reporting | 4.1.8.2 | -| Change of QCI (MN initiated) | 5.6.23 | -| Measurement ID Coordination (MN initiated) | 5.6.24 | - -| | | -|--------------------------------------------------|--------| -| | | -| DRB ID change/Security Key change (SN initiated) | 5.6.21 | -| Measurement ID Coordination (SN initiated) | 5.6.25 | - -**Table 2-3: IOT Test Cases for X2 implemented in accordance with the NR C-Plane [2] profile** - -| Test Case | Reference to O-RAN NR U-Plane profile [3] | -|--------------------------------------------------------------------------------|-------------------------------------------| -| Node behaviour of the corresponding node with RLC-AM and/or RLC-UM | 4.1.1.1 | -| General for Elements for the NR user plane protocols with RLC-AM and/or RLC-UM | 4.1.2.1 | -| Report polling with RLC-AM and/or RLC-UM | 4.1.2.2 | -| Buffer discard Indication with RLC-AM and/or RLC-UM | 4.1.2.3 | -| User data existence flag with RLC-AM and/or RLC-UM | 4.1.2.4 | -| Assistance Information Report Polling Flag with RLC-AM and/or RLC-UM | 4.1.2.5 | -| Radio quality assistance information with RLC-AM and/or RLC-UM | 4.1.2.6 | -| DL report NR PDCP PDU SN with RLC-AM | 4.1.2.7 | - -**Table 2-4: IOT Test Cases for X2 implemented in accordance with the NR U-Plane [3] profile** - -The initial test conditions which are common to all X2 test cases are listed below while the test case specific deviations of the initial test conditions will be specified in each of the test cases: - -- eNB(s) and en-gNB(s) are running in normal operating state -- eNB(s) and en-gNB(s) are physically and logically connected -- Core or Core emulator (EPC with EN-DC capabilities) is physically connected to eNB(s) and en-gNB(s) -- S1 Setup procedure specified in 3GPP TS 36.413 [7] has been completed with the Core or Core emulator -- Protocol Analyzer is physically connected to the X2 and S1-U link(s) - -### 2.2.1 X2 C-Plane IOT Test Cases - -#### 2.2.1.1 EN-DC X2 Setup (eNB initiated) - -## 2.2.1.1.1 Test Purpose - -The purpose of this test case is to verify that the MN (eNB) initiated EN-DC X2 Setup procedure with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.1.1.1. - -#### 2.2.1.1.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 4.1.1.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UE (emulator) NAS protocol - -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -#### 2.2.1.1.3 Initial Conditions - -- An SCTP association is successfully established between the two SCTP endpoints (SCTP initiation procedure has taken place before or is taking place with execution of this test case) - -#### 2.2.1.1.4 Procedure - -1. Initiate the EN-DC X2 Setup procedure in MN (eNB). - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. O&M command in eNB to enable X2 interface - -2. Observe the Protocol Analyzer X2 logs. - -#### 2.2.1.1.5 Expected Results and Log Observation - -##### 2.2.1.1.5.1 Expected Results - -The EN-DC X2 Setup procedure is successfully completed. - -##### 2.2.1.1.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 4.1.1.1.1/4.1.1.1.2. - -#### 2.2.1.2 EN-DC X2 Setup (en-gNB initiated) - -##### 2.2.1.2.1 Test Purpose - -The purpose of this test case is to verify that the SN (en-gNB) initiated EN-DC X2 Setup procedure with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.1.1.2. - -##### 2.2.1.2.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 4.1.1.2 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UE (emulator) NAS protocol -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -##### 2.2.1.2.3 Initial Conditions - -- An SCTP association is successfully established between the two SCTP endpoints (SCTP initiation procedure has taken place before or is taking place with execution of this test case) - -##### 2.2.1.2.4 Procedure - -1. Initiate the EN-DC X2 Setup procedure in SN (en-gNB). - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- O&M command in en-gNB to enable X2 interface - -2. Observe the Protocol Analyzer X2 logs. - -#### 2.2.1.2.5 Expected Results and Log Observation - -##### 2.2.1.2.5.1 Expected Results - -The EN-DC X2 Setup procedure is successfully completed. - -##### 2.2.1.2.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 4.1.1.2.1/4.1.1.2.2. - -#### 2.2.1.3 Reset (eNB initiated) - -##### 2.2.1.3.1 Test Purpose - -The purpose of this test case is to verify that the MN (eNB) initiated Reset procedure with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.1.2.1. - -##### 2.2.1.3.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB. - -Testing tools which are required for this test scenario: - -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UE (emulator) NAS protocol -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -##### 2.2.1.3.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] - -##### 2.2.1.3.4 Procedure - -1. Initiate the X2 Reset procedure in MN (eNB). - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. O&M command to deactivate all cells serving UEs in MN which will initiate reset procedure to en-gNB - -2. Observe the Protocol Analyzer X2 link logs. - -#### 2.2.1.3.5 Expected Results and Log Observation - -##### 2.2.1.3.5.1 Expected Results - -The Reset (eNB initiated) procedure is successfully completed. - -##### 2.2.1.3.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 4.1.2.1.1/4.1.2.1.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “RESET RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -#### 2.2.1.4 Reset (en-gNB initiated) - -##### 2.2.1.4.1 Test Purpose - -The purpose of this test case is to verify that the SN (en-gNB) initiated Reset procedure with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.1.2.2. - -##### 2.2.1.4.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB. - -Testing tools which are required for this test scenario: - -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UE (emulator) NAS protocol -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -##### 2.2.1.4.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] - -##### 2.2.1.4.4 Procedure - -1. Initiate the X2 Reset procedure in SN (en-gNB). - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. O&M command to deactivate all cells serving UEs in SN, which will initiate reset procedure to eNB -2. Observe the Protocol Analyzer X2 link logs. - -##### 2.2.1.4.5 Expected Results and Log Observation - -###### 2.2.1.4.5.1 Expected Results - -The Reset (en-gNB initiated) procedure is successfully completed. - -###### 2.2.1.4.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 4.1.2.2.1/4.1.2.2.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “RESET RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -## 2.2.1.5 Partial Reset (MeNB initiated) - -### 2.2.1.5.1 Test Purpose - -The purpose of this test case is to verify that the MeNB initiated Partial Reset procedure with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.1.4.1. - -### 2.2.1.5.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UEs or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol, and to support Path Switch, Bearer Modification and Secondary RAT Data Usage Report -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -### 2.2.1.5.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- At least one UE context exists in en-gNB -- Multiple Test UEs or emulated UEs have registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UEs or emulated UEs are within the coverage area of the SN cell and Secondary Node Addition procedure (eg, SN terminated split bearer) has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.2.1.5.4 Procedure - -1. Perform the MeNB initiated Partial Reset procedure over X2 for a part of the Test UEs or emulated UEs. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation. One method is to use O&M command in the eNB in order to deactivate a few cells serving UEs. -2. Observe the Protocol Analyzer X2 link logs and Test UE or UE emulator logs. - -### 2.2.1.5.5 Expected Results and Log Observation - -#### 2.2.1.5.5.1 Expected Results - -The MeNB initiated Partial Reset procedure is successfully completed. - -The selected UE contexts are successfully released in the en-gNB and data transfer on the en-gNB side between the Application Test Server and the Test UE or UE emulator has ended. - -#### 2.2.1.5.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 4.1.4.1.1/4.1.4.1.2. - -- Logs recorded in the Test UE or UE emulator shows: - - After the end of Step 1, Test UE or UE emulator does NOT receive any data which is transmitted from en-gNB - -#### 2.2.1.6 Partial Reset (en-gNB initiated) - -##### 2.2.1.6.1 Test Purpose - -The purpose of this test case is to verify that the en-gNB initiated Partial Reset procedure with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.1.4.2. - -##### 2.2.1.6.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UEs or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol, and to support Path Switch, Bearer Modification and Secondary RAT Data Usage Report -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -##### 2.2.1.6.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- At least one UE context exists in MeNB -- Multiple Test UEs or emulated UEs have registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] have been successfully completed -- Test UEs or emulated UEs are within the coverage area of the SN cell and Secondary Node Addition procedure (eg, SN terminated split bearer) has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -##### 2.2.1.6.4 Procedure - -1. Perform the en-gNB initiated Partial Reset procedure over X2 for a part of the Test UEs or emulated UEs. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation. One method is to use O&M command in the en-gNB in order to deactivate a few cells serving UEs. -2. Observe the Protocol Analyzer X2 link logs and Test UE or UE emulator logs. - -### 2.2.1.6.5 Expected Results and Log Observation - -#### 2.2.1.6.5.1 Expected Results - -The en-gNB initiated Partial Reset procedure is successfully completed. - -The selected UE contexts are successfully released in the MeNB and data transfer on the MeNB side between the Application Test Server and the Test UE or UE has ended. - -#### 2.2.1.6.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 4.1.4.2.1/4.1.4.2.2. - -- Logs recorded in the Test UE or UE emulator shows: -- After the end of Step 1, Test UE or UE emulator does NOT receive any data which is transmitted from MeNB - -### 2.2.1.7 Secondary Node Addition (Option 3x) - -#### 2.2.1.7.1 Test Purpose - -The purpose of this test case is to verify that the Secondary Node Addition (Option 3x) procedure with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.1.1. - -#### 2.2.1.7.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.1.1 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform Secondary Node Addition procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content, S1-U UP content - -#### 2.2.1.7.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary node has not yet been added to the Test UE or UE emulator -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -#### 2.2.1.7.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the Secondary Node Addition (Option 3x) procedure. This involves observing that the user plane data forwarded from the eNB to the en-gNB over the X2 interface during the Secondary Node Addition (Option 3x) procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates which are high enough for the eNB to start buffering user plane downlink data prior to the addition of the en-gNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -2. Perform Secondary Node Addition (Option 3x) procedure - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the en-gNB cell. In this specific case, the en-gNB cell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the SgNB Addition Request procedure. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during Split Bearer(s) operation in EN-DC Option 3x configuration. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -### 2.2.1.7.5 Expected Results and Log Observation - -#### 2.2.1.7.5.1 Expected Results - -The Secondary Node Addition (Option 3x) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.2.1.7.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in NR C-Plane profile specification [2] Sections 5.1.1.1/5.1.1.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “E-RABs Not Admitted List” in “SGNB ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “SGNB ADDITION REQUEST ACKNOWLEDGE” -- “Configuration rejected” in “SGNB RECONFIGURATION COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs which are: - - o Forwarded to the Test UE or emulated UE from the eNB towards the en-gNB via their corresponding established DL Forwarding GTP Tunnels, is correctly received by the Test UE or emulated UE via the NR RAT - - o Transmitted to the Test UE or emulated UE from the en-gNB to the eNB, via the established MeNB DL GTP Tunnels, is correctly received by the Test UE or emulated UE via the LTE RAT - -Note: this test verification process does not impose a requirement for the en-gNB to transmit the user plane data which it has received from the eNB (as part of the downlink data forwarding procedure) to the Test UE or emulated UE via the eNB and LTE RAT, but rather it is to verify the correct operation of the transmit operation via the eNB and the LTE RAT when it is used by the en-gNB. - -- Regarding the downlink U-Plane data generated in step 4: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT or NR RAT is recorded in the S1 logs - - o All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs - -## 2.2.1.8 Secondary Node Release (MN initiated, Option 3x) - -### 2.2.1.8.1 Test Purpose - -The purpose of this test case is to verify that the MN (eNB) initiated SgNB Release procedure with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.2.1. - -### 2.2.1.8.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.2.1 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Secondary Node Release (MN initiated, Option 3x) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and S1 procedural flows and content - -### 2.2.1.8.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.2.1.8.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the Secondary Node Release (MN Initiated, Option 3x) procedure. This involves observing that the user plane data forwarded from the en-gNB to the eNB over the X2 interface during the Secondary Node Release (MN Initiated, Option 3x) procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -2. One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates high enough for the en-gNB to start buffering user plane downlink data prior to the release of the en-gNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the - -maximum Layer 1 Radio data rate in the LTE RAT and the NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -3. Perform Secondary Node Release Procedure from MN (eNB) side - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- Provoke a Radio Link Failure in SCG, so MN receives SCG Failure Information NR message from the UE. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the en-gNB cell. In this specific case, the en-gNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger the Radio link failure scenario. - -4. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -5. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Secondary Node Release Procedure. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -6. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -## 2.2.1.8.5 Expected Results and Log Observation - -### 2.2.1.8.5.1 Expected Results - -The Secondary Node Release procedure is successfully completed. - -All the data generated is correctly received by UE after the release procedure. - -### 2.2.1.8.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 5.2.1.1/5.2.1.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB RELEASE REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 3 and in step 5: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs (ie, all U-Plane data forwarded from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 3 and in step 5: - - o All U-Plane data transmitted by the Test UE or UE emulator via LTE respectively NR RAT is recorded in the S1 logs - -## 2.2.1.9 Secondary Node Release (SN initiated, Option 3x) - -### 2.2.1.9.1 Test Purpose - -The purpose of this test case is to verify that the SN (en-gNB) initiated SgNB Release procedure with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.2.2. - -### 2.2.1.9.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.2.2 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Secondary Node Release (SN initiated, Option 3x) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and S1 procedural flows and content - -### 2.2.1.9.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.2.1.9.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the Secondary Node Release (SN Initiated, Option 3x) procedure. This involves observing that the user plane data forwarded from the en-gNB to the eNB over the X2 interface during the Secondary Node Release (SN Initiated, Option 3x) procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates high enough for the en-gNB to start buffering user plane downlink data prior to the release of the en-gNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the - -maximum Layer 1 Radio data rate in the LTE RAT and the NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform Secondary Node Release Procedure from SN (en-gNB) side - -A few examples of how this procedure can be performed (or triggered) are listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Block NR cell in en-gNB. One method is to use O&M command in the en-gNB to block the NR cell -- b. Provoke conditions in a way that the SN detects that the RLC exceeds its maximum downlink retransmission. One method is to vary the channel conditions between the SN and the Test UE or UE emulator so that the emulated interference can be significant enough to increase RLC retransmissions to exceed the maximum downlink retransmission level - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Secondary Node Release Procedure. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -### 2.2.1.9.5 Expected Results and Log Observation - -#### 2.2.1.9.5.1 Expected Results - -The Secondary Node Release procedure is successfully completed. - -All the data generated is correctly received by UE after the release procedure. - -#### 2.2.1.9.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 5.2.2.1/5.2.2.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB RELEASE CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs (ie, all U-Plane data forwarded from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via LTE respectively NR RAT is recorded in the S1 logs - -## 2.2.1.10 Secondary Node Change (MN initiated, Option 3x) - -### 2.2.1.10.1 Test Purpose - -The purpose of this test case is to verify that the MN (eNB) initiated SgNB Change procedure with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.3.1. - -### 2.2.1.10.2 Minimum Requirements - -DUTs: Single eNB and two en-gNB (Source en-gNB – S-SN, Target en-gNB – T-SN): - -- DUTs shall apply the parameter condition specified in 5.3.1 of the NR C-Plane profile specification [2] -- The coverage of eNB cell (MN), Source en-gNB cell (S-SN) and Target en-gNB cell (T-SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Secondary Node Change procedure (MN initiated, Option 3x) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both X2 and S1 links procedural flows and content - -### 2.2.1.10.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNBs according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the eNB cell and S-SN cell -- Secondary Node Addition (Option 3x) procedure between the eNB and S-SN has been successfully completed according to NR C-Plane profile specification [2] -- Secondary Node is Source en-gNB cell (S-SN) at the start of this procedure -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.2.1.10.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the Secondary Node Change (MN Initiated, Option 3x) procedure. This involves observing that the user plane data forwarded from the source en-gNB to the eNB and from the eNB to the target en-gNB over the X2 interface during the Secondary Node Change (MN Initiated, Option 3x) procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates which are high enough for the source en-gNB to start buffering user plane downlink data prior to the change of the en-gNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform Secondary Node Change Procedure from MN (eNB) side - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the Source en-gNB cell (S-SN) and the Target en-gNB cell (T-SN) simultaneously. In this specific case, the Source en-gNB cell (S-SN) can start off with low attenuation applied which is subsequently increased. At the same time, the Target en-gNB cell (T-SN) can start off with high attenuation applied which is subsequently lowered to a level which can trigger the Secondary Node Change procedure. - -3. Stop data transfer from the Application Test Server to the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during Split Bearer(s) operation in EN-DC Option 3x configuration. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -## 2.2.1.10.5 Expected Results and Log Observation - -### 2.2.1.10.5.1 Expected Results - -The Secondary Node Change procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -### 2.2.1.10.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 5.3.1.1/5.3.1.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “E-RABs Not Admitted List” in “SGNB ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “SGNB ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “SGNB RELEASE REQUEST ACKNOWLEDGE” -- “Configuration rejected” in “SGNB RECONFIGURATION COMPLETE” - -the test result shall be determined to be 'successful with remarks'. - -X2 and S1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the S1 logs is correctly received by the Test UE or emulated UE via LTE RAT or NR RAT - - All U-Plane data recorded in the X2 logs which are: - - Forwarded to the Test UE or emulated UE from the source en-gNB towards the eNB and from the eNB towards the target en-gNB, via their corresponding established DL Forwarding GTP Tunnels, is correctly received by the Test UE or emulated UE via the NR RAT - - Transmitted to the Test UE or emulated UE from the target en-gNB to the eNB, via the established MeNB DL GTP Tunnels, is correctly received by the Test UE or emulated UE via the LTE RAT - -Note: this test verification process does not impose a requirement for the target en-gNB to transmit the user plane data which it has received from the eNB (as part of the downlink data forwarding procedure) to the Test UE or emulated UE via the eNB and LTE RAT, but rather it is to verify the correct operation of the transmit operation via the eNB and the LTE RAT when it is used by the target en-gNB - - - All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from target en-gNB to eNB) is correctly received by the Test UE or emulated UE via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT or NR RAT is recorded in the S1 logs - - All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT (ie, all U-Plane data to be transferred from eNB to target en-gNB) is recorded in the X2 logs - -## 2.2.1.11 Secondary Node Change (SN initiated, Option 3x) - -### 2.2.1.11.1 Test Purpose - -The purpose of this test case is to verify that the SN (en-gNB) initiated SgNB Change procedure with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.3.2. - -### 2.2.1.11.2 Minimum Requirements - -DUTs: Single eNB and two en-gNB (Source en-gNB – S-SN, Target en-gNB – T-SN): - -- DUTs shall apply the parameter condition specified in 5.3.2 of the NR C-Plane profile specification [2] -- The coverage of eNB cell (MN), Source en-gNB cell (S-SN) and Target en-gNB cell (T-SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Secondary Node Change procedure (MN initiated, Option 3x) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both X2 and S1 links procedural flows and content - -### 2.2.1.11.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 Setup procedure has been successfully completed between the eNB and en-gNBs according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the eNB cell and S-SN cell -- Secondary Node Addition (Option 3x) procedure between the eNB and S-SN has been successfully completed according to NR C-Plane profile specification [2] -- Secondary Node is Source en-gNB cell (S-SN) at the start of this procedure -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.2.1.11.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the Secondary Node Change (SN Initiated, Option 3x) procedure. This involves observing that the user plane data forwarded from the source en-gNB to the eNB and from the eNB to the target en-gNB over the X2 interface during the Secondary Node Change (SN Initiated, Option 3x) procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates which are high enough for the source en-gNB to start buffering user plane downlink data prior to the change of the en-gNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and the NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10], 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform Secondary Node Change Procedure from Source en-gNB cell (S-SN) and Target en-gNB cell (T-SN) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Move the Test UE or UE emulator from the coverage area of Source en-gNB cell (S-SN) towards Target en-gNB cell (T-SN). One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the Source en-gNB cell (S-SN) and the Target en-gNB cell (T-SN) simultaneously. In this specific case, the Source en-gNB cell (S-SN) can start off with low attenuation applied which is subsequently increased. At the same time, the Target en-gNB cell (T-SN) can start off with high attenuation applied which is subsequently lowered to a level which can trigger the SN change procedure from S-SN to T-SN. - -3. Stop data transfer from the Application Test Server to the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during Split Bearer(s) operation in EN-DC Option 3x configuration. This involves observing that the user plane data - -transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs. - -### 2.2.1.11.5 Expected Results and Log Observation - -#### 2.2.1.11.5.1 Expected Results - -The Secondary Node Change procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.2.1.11.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 5.3.2.1/5.3.2.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “E-RABs Not Admitted List” in “SGNB ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “SGNB ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “SGNB CHANGE CONFIRM” -- “Configuration rejected” in “SGNB RECONFIGURATION COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or emulated UE via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs which are: - - o Forwarded to the Test UE or emulated UE from the source en-gNB towards the eNB and from the eNB towards the target en-gNB, via their corresponding established DL Forwarding GTP Tunnels, is correctly received by the Test UE or emulated UE via the NR RAT - - o Transmitted to the Test UE or emulated UE from the target en-gNB to the eNB, via the established MeNB DL GTP Tunnels, is correctly received by the Test UE or emulated UE via the LTE RAT - -Note: this test verification process does not impose a requirement for the target en-gNB to transmit the user plane data which it has received from the eNB (as part of the downlink data forwarding procedure) to the Test UE or emulated UE via the eNB and LTE RAT, but rather it is to verify the correct operation of the transmit operation via the eNB and the LTE RAT when it is used by the target en-gNB. - -- o All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from target en-gNB to eNB) is correctly received by the Test UE or emulated UE via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - -- o All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT or NR RAT is recorded in the S1 logs -- o All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT (ie, all U-Plane data to be transferred from eNB to target en-gNB) is recorded in the X2 logs - -## 2.2.1.12 Inter-Master Node Handover (without SN Change, Option 3x) - -### 2.2.1.12.1 Test Purpose - -The purpose of this test case is to verify that the Inter-Master Node Handover (without SN Change, Option 3x) procedure with two eNBs and en-gNB from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.4.1. - -### 2.2.1.12.2 Minimum Requirements - -DUTs: Two eNBs (Source eNB – S-MN, Target eNB – T-MN) and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.4.1 of the NR C-Plane profile specification [2] -- The coverage of Source eNB cell and en-gNB cell overlap -- The coverage of Target eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Inter-Master Node Handover procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe all three X2 links procedural flows and content - -### 2.2.1.12.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between both the source eNB and en-gNB, and the target eNB and en-gNB according to the NR C-Plane profile specification [2] -- X2 setup procedure between the source eNB and target eNB specified in 3GPP TS 36.423 [12] has been successfully completed -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the Source eNB cell (S-MN) and en-gNB cell -- Secondary Node Addition (Option 3x) procedure between the Source eNB (S-MN) and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.2.1.12.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during the Inter-Master Node Handover (without SN Change, Option 3x) procedure. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -2. Perform Inter-Master Node Handover (without SN Change, Option 3x) procedure from source eNB (S-MN), target eNB (T-MN) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. The Test UE or UE emulator sends a Measurement Report to the source eNB (S-MN). One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and source eNB (S-MN) and the target eNB (T-MN) simultaneously. In this specific case, the source eNB (S-MN) cell can start off with low attenuation applied which is subsequently increased. At the same time, the target eNB (T-MN) cell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the measurement report to be sent to the source eNB (S-MN). -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during Split Bearer(s) operation in EN-DC Option 3x configuration. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -## 2.2.1.12.5 Expected Results and Log Observation - -### 2.2.1.12.5.1 Expected Results - -The Inter-Master Node Handover (without SN Change, Option 3x) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -### 2.2.1.12.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in NR C-Plane profile specification [2] Sections 5.4.1.1/5.4.1.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “E-RABs Not Admitted List” in “SGNB ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “SGNB ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “SGNB RELEASE REQUEST ACKNOWLEDGE” -- “Configuration rejected” in “SGNB RECONFIGURATION COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or emulated UE via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to source eNB after step 2 and from en-gNB to target eNB in step 4) is correctly received by the Test UE or emulated UE via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT or NR RAT is recorded in the S1 logs - - o All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT (ie, all U-Plane data to be transferred from source eNB to en-gNB after step 2 and target eNB to en-gNB in step 4) is recorded in the X2 logs - -## 2.2.1.13 Master Node to eNB Change - -### 2.2.1.13.1 Test Purpose - -The purpose of this test case is to verify that the Master Node to eNB Change procedure with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.5.1. - -### 2.2.1.13.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.5.1 of the NR C-Plane profile specification [2] -- The coverage of Source eNB cell (S-MN), Target eNB cell (T-MN) and en-gNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Master Node to eNB Change procedure -- Target eNB or Target eNB emulator: used to perform Master Node to eNB Change procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol, and to support Path Switch, Bearer Modification and Secondary RAT Data Usage Report -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content and, S1-U UP content - -### 2.2.1.13.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- X2 setup procedure between the source eNB and target eNB or target eNB emulator specified in 3GPP TS 36.423 [12] has been successfully completed -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the Source eNB cell (S-MN) and SN cell -- Secondary Node Addition (Option 3x) procedure between the Source eNB (S-MN) and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Then SCG configuration query has been completed if needed - -#### 2.2.1.13.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the Master Node to eNB Change procedure. This involves observing that the user plane data forwarded from the en-gNB to the source eNB over the X2 interface during the Master Node to eNB Change procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates which are high enough for the en-gNB to start buffering user plane downlink data prior to the release of the en-gNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -2. Perform the Master Node to eNB Change Procedure - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. The handover to Target eNB is decided by the Master Node based on the Measurement Report sent from the Test UE or UE emulator. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and Master Node cell and the eNB cell simultaneously. In this specific case, the Master Node cell can start off with low attenuation applied which is subsequently increased. At the same time, the eNB cell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the Master Node to eNB Change procedure. - -3. Stop data transfer from the Application Test Server to the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during MCG Bearer(s) operation. This involves observing that the user plane data transferred in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer - -1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -### 2.2.1.13.5 Expected Results and Log Observation - -#### 2.2.1.13.5.1 Expected Results - -The Master Node to eNB Change Procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.2.1.13.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in NR C-Plane profile specification [2] Sections 5.5.1.1/5.5.1.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB RELEASE REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the S1 logs is correctly received by the Test UE or emulated UE via LTE RAT or NR RAT - - All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to source eNB in step 1, en-gNB to source eNB to target eNB after step 2) is correctly received by the Test UE or emulated UE via LTE RAT, no U-Plane data recorded in the X2 logs in step 4 -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT or NR RAT is recorded in the S1 logs - - All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT or NR RAT (ie, all U-Plane data to be transferred from source eNB to en-gNB in step 1, from source eNB to target eNB and en-gNB to source eNB to target eNB after step 2) is recorded in the X2 logs, no U-Plane data recorded in the X2 logs in step 4 - -### 2.2.1.14 PCell change (Intra MN) (MN initiated) - -#### 2.2.1.14.1 Test Purpose - -The purpose of this test case is to verify that the PCell change (Intra MN) (MN initiated) procedure with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.6.1. - -#### 2.2.1.14.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.1 of the NR C-Plane profile specification [2] -- eNB has at least 2 Cells configured and in operation -- The coverage of Intra-eNB source cell and en-gNB cell overlap -- The coverage of Intra-eNB target cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform PCell change (Intra MN) (MN initiated) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content, S1-U UP content - -#### 2.2.1.14.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the eNB Source cell and SN cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -#### 2.2.1.14.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during the PCell change (Intra MN) (MN initiated) procedure. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission function (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -2. Perform PCell change (Intra MN) procedure on the MN (eNB) side - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Make use of programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the MN Source Cell and the Target Cell simultaneously. In this specific case, the MN Source Cell can start off with low attenuation applied which is subsequently increased. At the same - -time, the Target Cell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the handover from the Source Cell to the Target Cell. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during Split Bearer(s) operation in EN-DC Option 3x configuration. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -#### 2.2.1.14.5 Expected Results and Log Observation - -##### 2.2.1.14.5.1 Expected Results - -The PCell change (Intra MN) (MN initiated) procedure is successfully completed and data transfer between the Application Test Server and the Test UE or UE emulator is not interrupted throughout the test case execution. - -##### 2.2.1.14.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 5.6.1.1/5.6.1.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” -- “Configuration rejected” in “SGNB RECONFIGURATION COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after Step 2 and generated in Step 4: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or emulated UE via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from SN en-gNB to MN eNB in step 1 and after step 2 and in step 4) is correctly received by the Test UE or emulated UE via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after Step 2 and in Step 4: - - o All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT or NR RAT is recorded in the S1 logs - - o All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT (ie, all U-Plane data to be transferred from MN eNB to SN en-gNB in step 1 and after step 2 and in step 4) is recorded in the X2 logs - -## 2.2.1.15 PSCell Change using SRB1 for RRC Reconfiguration – full configuration option - -### 2.2.1.15.1 Test Purpose - -The purpose of this test case is to verify that the PSCell Change using SRB1 for RRC Reconfiguration – full configuration option procedure with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.6.15. - -### 2.2.1.15.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.15 of NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cells overlap -- en-gNB has at least 2 Cells configured and in operation - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform PSCell Change using SRB1 for RRC Reconfiguration procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -### 2.2.1.15.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 Setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and one SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.2.1.15.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during the PSCell Change using SRB1 for RRC Reconfiguration (full configuration) procedure. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -2. Perform PSCell Change using SRB1 for RRC Reconfiguration – full configuration option procedure - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. The condition by which UE sends an ULInformationTransferMRDC message to the MN depends on the configuration done by MN. Still, we can create a situation where PSCell Change occurs. There should be at least two en-gNB cells within the coverage of a cell under eNB. The first cell under en-gNB which is PSCell and the second cell under en-gNB which is not PSCell. If the tester manually degrades the radio quality of the first en-gNB cell this can be the trigger of the PSCell Change procedure. - -One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the first en-gNB cell. In this specific case, the first en-gNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger the PSCell Change procedure. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during Split Bearer(s) operation in EN-DC Option 3x configuration. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs. - -## 2.2.1.15.5 Expected Results and Log Observation - -### 2.2.1.15.5.1 Expected Results - -The PSCell Change using SRB1 for RRC Reconfiguration – full configuration option procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -### 2.2.1.15.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in NR C-Plane profile specification [2] Sections 5.6.15.1/5.6.15.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “SGNB MODIFICATION CONFIRM” - -the test result shall be determined to be 'successful with remarks'. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the S1 logs is correctly received by the Test UE or emulated UE via LTE RAT or NR RAT - - All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to eNB) is correctly received by the Test UE or emulated UE via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT or NR RAT is recorded in the S1 logs - - All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs - -## 2.2.1.16 PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option - -### 2.2.1.16.1 Test Purpose - -The purpose of this test case is to verify that the PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option procedure with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.6.16. - -### 2.2.1.16.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.16 of NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cells overlap -- en-gNB has at least 2 Cells configured and in operation - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform PSCell Change using SRB1 for RRC Reconfiguration procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and contents - -### 2.2.1.16.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the eNB cell and one en-gNB cell - -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -#### 2.2.1.16.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during the PSCell Change using SRB1 for RRC Reconfiguration (delta configuration) procedure. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -2. Perform PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option procedure - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. The condition by which UE sends an ULInformationTransferMRDC message to the MN depends on the configuration done by MN. Still, we can create a situation where PSCell Change occurs. There should be at least two en-gNB cells within the coverage of a cell under eNB. The first cell under en-gNB which is PSCell and the second cell under en-gNB which is not PSCell. If the tester manually degrades the radio quality of the first en-gNB cell, this can be the trigger of the PSCell Change procedure. - -One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the first en-gNB cell. In this specific case, the first en-gNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger the PSCell Change procedure. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during Split Bearer(s) operation in EN-DC Option 3x configuration. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data) or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -### 2.2.1.16.5 Expected Results and Log Observation - -#### 2.2.1.16.5.1 Expected Results - -The PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.2.1.16.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in NR C-Plane profile specification [2] Sections 5.6.16.1/5.6.16.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or emulated UE via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to eNB) is correctly received by the Test UE or emulated UE via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT or NR RAT is recorded in the S1 logs - - o All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs - -### 2.2.1.17 Served NR cell information Update (en-gNB initiated) - -#### 2.2.1.17.1 Test Purpose - -The purpose of this test case is to verify that the SN (en-gNB) initiated Served NR cell Update procedure, with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.1.3.1. - -#### 2.2.1.17.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 4.1.3.1 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cells overlap -- en-gNB has at least 2 Cells configured and in operation - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform Secondary Node Addition procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol - -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc.) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -### 2.2.1.17.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.2.1.17.4 Procedure - -1. Perform Served NR cell information Update (en-gNB initiated) procedure for served NR cells to Delete - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell failure. One method is to use O&M command in the en-gNB in order to make one of en-gNB cell failure status - -2. Perform a procedure to observe that the en-gNB cell deleted in step 1 is not enabled for EN-DC PSCell or SCell - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To make use of programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the en-gNB cell performing as PSCell and the en-gNB cell deleted in step 1 simultaneously. In this specific case, the en-gNB cell performing as PSCell can start off with low attenuation applied which is subsequently increased. At the same time, the en-gNB cell deleted in step 1 can start off with high attenuation applied which is subsequently lowered to a level which can trigger PSCell Change procedure. - -Note that although PSCell Change procedure is listed as an example in this step, it does not mean this test case verifies correct PSCell Change procedure (The test case of PSCell Change procedure is specified in 2.2.1.15 and 2.2.1.16 in this specification). - -3. Perform Served NR cell information Update (en-gNB initiated) procedure for served NR cells to Add - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate recovery from cell failure. One method is to use O&M command in the en-gNB in order to make the en-gNB cell deleted in step 1 recover from failure status - -4. Perform a procedure to observe that the en-gNB cell added in step 3 is enabled for EN-DC PSCell or SCell - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To make use of programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the en-gNB cell performing as PSCell and the en-gNB cell added in step 3 - -simultaneously. In this specific case, the en-gNB cell performing as PSCell can start off with low attenuation applied which is subsequently increased. At the same time, the en-gNB cell added in step 3 can start off with high attenuation applied which is subsequently lowered to a level which can trigger PSCell Change procedure. - -- b. In case that PSCell is not configured to test UE or UE emulator after step 2, to trigger Secondary Node addition procedure in order to configure the en-gNB cell recovered in step 3 as PSCell -5. Perform Served NR cell information Update (en-gNB initiated) procedure for served NR cells to Modify - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. NR PCI information of the en-gNB cell is changed. One method is to use O&M command in the en-gNB in order to change the NR PCI -6. Perform a procedure to observe the information modified in step 5 - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. In case that NR PCI information of the en-gNB cell is changed in step 5, to make test UE or UE emulator send Measurement Report including NR PCI information of the en-gNB cell. -7. Observe the Protocol Analyzer X2 link logs and Test UE or UE emulator logs - -#### 2.2.1.17.5 Expected Results and Log Observation - -##### 2.2.1.17.5.1 Expected Results - -The Served NR cell information Update (en-gNB initiated) is successfully completed in each case, ie, to Add, to Modify, and to Delete case. - -##### 2.2.1.17.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.1.3.1.1/4.1.3.1.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “EN-DC CONFIGURATION UPDATE ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -Test UE or UE emulator logs show that: - -- In step 2, the en-gNB cell deleted in step 1 is not enabled for EN-DC PSCell or SCell -- In step 4, the en-gNB cell added in step 3 is enabled for EN-DC PSCell or SCell -- In step 6, the information modified in step 5 is included - -#### 2.2.1.18 Security Key Change (MN initiated) - -##### 2.2.1.18.1 Test Purpose - -The purpose of this test case is to verify that the MN (eNB) initiated Security Key Change procedure, with MN (eNB) and SN (en-gNB) from different vendors, can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.6.5. - -### 2.2.1.18.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.5 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform MN initiated Security Key Change procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc.) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -### 2.2.1.18.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.2.1.18.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform Security Key Change procedure (MN initiated) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Perform PCell Change (Intra MN) (MN initiated) procedure (See step 2 in 2.2.1.14.4) - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Security Key Change procedure. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -#### 2.2.1.18.5 Expected Results and Log Observation - -##### 2.2.1.18.5.1 Expected Results - -The Security Key Change procedure (MN initiated) is successfully completed. - -##### 2.2.1.18.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.5.1/5.6.5.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -S1 and X2 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- After step 2 the updated security key is applied in UE: - - An example of how to observe the updated security key is to check the UE emulator log. The exact method to observe the updated security key is out of scope of this specification -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data which is recorded in the S1 logs, but is not recorded in X2 logs, is correctly received in the PDCP layer or higher layer by the Test UE or emulated UE via LTE RAT or NR RAT. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT or NR RAT is recorded in the S1 logs - -#### 2.2.1.19 Measurement Gap Coordination Procedure (MN initiated) - -##### 2.2.1.19.1 Test Purpose - -The purpose of this test case is to verify that the Measurement Gap Coordination Procedure (MN initiated) with eNB and en-gNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 5.6.6. - -##### 2.2.1.19.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.6 of NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Measurement Gap Coordination Procedure (MN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol - -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -### 2.2.1.19.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and service request procedure specified in 3GPP TS 23.401 [7] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.2.1.19.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during the Measurement Gap Coordination procedure. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -2. Perform Measurement Gap Coordination Procedure (MN initiated) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT - -- a. An eNB receives Measurement Report from UE - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during Split Bearer(s) operation in EN-DC Option 3x configuration. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data) or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer - -1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -#### 2.2.1.19.5 Expected Results and Log observation - -##### 2.2.1.19.5.1 Expected Results - -The Measurement Gap Coordination Procedure (MN initiated) is successfully completed. - -##### 2.2.1.19.5.2 Log observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in NR C-Plane profile specification [2] Sections 5.6.6.1/5.6.6.2. - -If any of the following listed IEs is observed in the X2 logs. - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” -- “Configuration rejected” in “SGNB RECONFIGURATION COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT or NR RAT is recorded in the S1 logs - - o All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs - -#### 2.2.1.20 Measurement Gap Coordination for per FR1 or per UE gap Procedure (SN initiated) - -##### 2.2.1.20.1 Test Purpose - -The purpose of this test case is to verify that the Measurement Gap Coordination for per FR1 or per UE gap Procedure (SN initiated) with eNB and en-gNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 5.6.7. - -##### 2.2.1.20.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.7 of NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Measurement Gap Coordination for per FR1 or per UE gap Procedure (SN initiated) - -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -### 2.2.1.20.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and service request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.2.1.20.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during the Measurement Gap Coordination for per FR1 or per UE gap procedure. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -2. Perform Measurement Gap Coordination for per FR1 or per UE gap Procedure (SN initiated) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. An en-gNB receive X2AP: RRC TRANSFER as specified in 5.7.1 of NR C-Plane profile specification [2] - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during Split Bearer(s) operation in EN-DC Option 3x configuration. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data) or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer X2 logs - -#### 2.2.1.20.5 Expected Results and Log observation - -##### 2.2.1.20.5.1 Expected Results - -The Measurement Gap Coordination for per FR1 or per UE gap Procedure (SN initiated) is successfully completed. - -##### 2.2.1.20.5.2 Log observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in NR C-Plane profile specification [2] Sections 5.6.7.1/5.6.7.2. - -If any of the following listed IEs is observed in the X2 logs. - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “SGNB MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT or NR RAT is recorded in the S1 logs - - o All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs - -#### 2.2.1.21 Measurement Gap Coordination for per FR2 gap (with MN involvement) Procedure (SN initiated) - -##### 2.2.1.21.1 Test Purpose - -The purpose of this test case is to verify that the Measurement Gap Coordination for per FR2 gap (with MN involvement) Procedure (SN initiated) with eNB and en-gNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 5.6.8. - -##### 2.2.1.21.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.8 of NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Measurement Gap Coordination for per FR2 gap (with MN involvement) Procedure (SN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -#### 2.2.1.21.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and service request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.2.1.21.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during the Measurement Gap Coordination per FR2 gap procedure. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -2. Perform Measurement Gap Coordination for per FR2 gap (with MN involvement) Procedure (SN initiated) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. An en-gNB receives X2AP: RRC TRANSFER as specified in 5.7.1 of NR C-Plane profile specification [2] - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during Split Bearer(s) operation in EN-DC Option 3x configuration. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data) or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -#### 2.2.1.21.5 Expected Results and Log observation - -##### 2.2.1.21.5.1 Expected Results - -The Measurement Gap Coordination for per FR2 gap (with MN involvement) Procedure (SN initiated) is successfully completed. - -##### 2.2.1.21.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in NR C-Plane profile specification [2] Sections 5.6.8.1/5.6.8.2. - -If any of the following listed IEs is observed in the X2 logs. - -- “Criticality Diagnostics” in “SGNB MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT or NR RAT is recorded in the S1 logs - - All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs - -#### 2.2.1.22 UL Configuration Update Procedure (SN initiated) - -##### 2.2.1.22.1 Test Purpose - -The purpose of this test case is to verify that the SN (en-gNB) initiated UL Configuration Update procedure with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 5.6.9. - -##### 2.2.1.22.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.9 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform Secondary Node Addition procedure and Secondary Node Modification procedure (SN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content, S1-U UP content - -### 2.2.1.22.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cell -- Secondary Node Addition (eg, SN terminated split bearer) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.2.1.22.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Perform UL Configuration Update procedure (SN initiated) for the purpose of changing from share to only of the UL Configuration IE - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT - -- a. Use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the en-gNB cell to degrade the radio quality of the en-gNB cell. And to make use of O&M command in SN side to change from share to only of the UL configuration IE. -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during Split Bearer(s) operation in EN-DC Option 3x configuration. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -### 2.2.1.22.5 Expected Results and Log Observation - -#### 2.2.1.22.5.1 Expected Results - -The UL Configuration Update Procedure (SN initiated) is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -### 2.2.1.22.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.9.1/5.6.9.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB MODIFICATION COFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - All U-Plane data recorded in the X2 logs is correctly received by the Test UE or UE emulator via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT is recorded in the S1 logs - - All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs - -### 2.2.1.23 Addition of SN terminated split bearer (MN initiated) - -#### 2.2.1.23.1 Test Purpose - -The purpose of this test case is to verify that the MN (eNB) initiated Secondary Node Modification procedure to perform addition of SN terminated split bearer with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.6.10. - -#### 2.2.1.23.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.10 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform Secondary Node Addition procedure and Secondary Node Modification procedure (MN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc.) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content, S1-U UP content - -#### 2.2.1.23.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB (MN) and en-gNB (SN) according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.2.1.23.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during the Secondary Node Modification (MN Initiated, addition of SN terminated split bearer) procedure. This involves observing that the user plane data transferred over the X2 interface in both directions during the Secondary Node Modification (MN Initiated, addition of SN terminated split bearer) procedure can be received successfully by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the LTE RAT is to transfer user plane data at data rates high enough for the eNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -2. Perform Secondary Node Modification with addition of SN terminated split bearer procedure from MN (eNB) side - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. Trigger from Core or Core emulator (EPC with EN-DC capabilities) to add a new E-RAB for this Test UE or UE emulator - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds on the new bearer - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly on the newly established SN terminated split bearer in above step 2. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -### 2.2.1.23.5 Expected Results and Log Observation - -#### 2.2.1.23.5.1 Expected Results - -The Secondary Node Modification procedure (MN initiated) with addition of SN terminated split bearer procedure is successfully completed. - -#### 2.2.1.23.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.10.1/5.6.10.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” -- “Configuration rejected” in “SGNB RECONFIGURATION COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and step 2: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT - - o Forwarded to the Test UE or emulated UE from the eNB towards the en-gNB via their corresponding established DL Forwarding GTP Tunnels if data forward is used, is correctly received by the Test UE or emulated UE via the NR RAT - - o Transmitted to the Test UE or emulated UE from the en-gNB to the eNB, via the established MeNB DL GTP Tunnels, is correctly received by the Test UE or emulated UE via the LTE RAT - -Note: this test verification process does not impose a requirement for the en-gNB to transmit the user plane data which it has received from the eNB (as part of the downlink data forwarding procedure) to the Test UE or emulated UE via the eNB and LTE RAT, but rather it is to verify the correct operation of the transmit operation via the eNB and the LTE RAT when it is used by the en-gNB. - -- Regarding the downlink U-Plane data generated in step 4: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT -- Regarding the uplink U-Plane data generated in step 1, after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT or NR RAT is recorded in the S1 logs - - o All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs - -## 2.2.1.24 Removal of SN terminated split bearer (MN initiated) - -### 2.2.1.24.1 Test Purpose - -The purpose of this test case is to verify that the MN (eNB) initiated Secondary Node Modification procedure to perform removal of SN terminated split bearer with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.6.11. - -### 2.2.1.24.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.11 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform Secondary Node Addition procedure and Secondary Node Modification procedure (MN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc.) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content, S1-U UP content - -### 2.2.1.24.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB (MN) and en-gNB (SN) according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure which, including at least two SN terminated split bearers between the eNB and en-gNB, has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.2.1.24.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during the Secondary Node Modification (MN Initiated, Removal of SN terminated split bearer) procedure. This involves observing that the user plane data transferred between the en-gNB to the eNB over the X2 interface during the Secondary Node Modification (MN Initiated, Removal of SN terminated split bearer) procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform Secondary Node Modification with removal of SN terminated split bearer from MN (eNB) side - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Trigger from Core or Core emulator (EPC with EN-DC capabilities) to delete the E-RAB bearer on the established with split bearer for this Test UE or UE emulator - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds on the remaining bearer - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after removal of Split Bearer(s) operation with Secondary Node Modification procedure. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the LTE RAT is to transfer user plane data at data rates high enough for the eNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -## 2.2.1.24.5 Expected Results and Log Observation - -### 2.2.1.24.5.1 Expected Results - -The Secondary Node Modification procedure (MN initiated) with removal of SN terminated split bearer procedure is successfully completed - -### 2.2.1.24.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.11.1/5.6.11.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and step 2: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and step 2: - - o All U-Plane data sent from the Test UE or UE emulator via LTE RAT or NR RAT is recorded in the S1 logs - -- o All U-Plane data sent from the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs -- Regarding the downlink U-Plane data generated in step 4: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT in case of EN-DC operation with SN terminated split bearer -- Regarding the uplink U-Plane data generated in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT or NR RAT is recorded in the S1 logs - - o All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs in case of EN-DC operation with SN terminated split bearer - -## 2.2.1.25 Bearer type change from SN terminated split bearer to SN terminated MCG bearer (MN initiated) - -### 2.2.1.25.1 Test Purpose - -The purpose of this test case is to verify that the MN (eNB) initiated Secondary Node Modification procedure to perform bearer type change from SN terminated split bearer to SN terminated MCG bearer with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.6.12. - -### 2.2.1.25.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.12 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform Secondary Node Addition procedure and Secondary Node Modification procedure (MN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc.) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content, S1-U UP content - -### 2.2.1.25.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB (MN) and en-gNB (SN) according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell - -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (eg, SN terminated split bearer) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.2.1.25.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during bearer type change operation from SN terminated split bearer to SN terminated MCG bearer. It is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform Secondary Node Modification procedure from MN (eNB) side to trigger the bearer type change from SN terminated split bearer to SN terminated MCG bearer - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the en-gNB cell. In this specific case, the en-gNB cell (SN) can start off with low attenuation applied which is subsequently increased to a level in case of the eNB cell (MN) without changes to trigger Secondary Node Modification procedure. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly in case of SN terminated MCG bearer configuration. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the MCG Bearer(s) usage of the LTE RAT is to transfer user plane data at data rates high enough for the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs. - -#### 2.2.1.25.5 Expected Results and Log Observation - -##### 2.2.1.25.5.1 Expected Results - -The Bearer type change from SN terminated split bearer to SN terminated MCG bearer (MN initiated) is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -### 2.2.1.25.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.12.1/5.6.12.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and step 2: - - All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - All U-Plane data recorded in the X2 logs (ie, all U-Plane data forwarded from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT -- Regarding the downlink U-Plane data generated in step 1 and step 2: - - All U-Plane data sent from the Test UE or UE emulator via LTE RAT or NR RAT is recorded in the S1 logs - - All U-Plane data sent from the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs -- Regarding the downlink U-Plane data generated in step 4: - - All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT - - All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT -- Regarding the uplink U-Plane data generated in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT is recorded in the S1 logs - - All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs - -### 2.2.1.26 Bearer type change from SN terminated MCG bearer to SN terminated split bearer (MN initiated) - -#### 2.2.1.26.1 Test Purpose - -The purpose of this test case is to verify that the MN (eNB) initiated Secondary Node Modification procedure to perform bearer type change from SN terminated MCG bearer to SN terminated split bearer with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.6.13. - -#### 2.2.1.26.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.13 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform Secondary Node Addition procedure and Secondary Node Modification procedure (MN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc.) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content, S1-U UP content - -### 2.2.1.26.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB (MN) and en-gNB (SN) according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (eg, SN terminated MCG bearer) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.2.1.26.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during bearer type change operation from SN terminated split bearer to SN terminated MCG bearer (MN initiated). It is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -One method to stimulate the MCG Bearer(s) usage of the LTE is to transfer user plane data at data rates high enough for the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -2. Perform Secondary Node Modification procedure from MN (eNB) side to trigger the bearer type change from SN terminated MCG bearer to SN terminated split bearer - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the en-gNB cell. In this specific case, the en-gNB cell can start off with high attenuation applied which is subsequently reduced to a level in case of the eNB cell (MN) without changes to trigger Secondary Node Modification procedure. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly in case of SN terminated MCG bearer configuration. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs. - -## 2.2.1.26.5 Expected Results and Log Observation - -### 2.2.1.26.5.1 Expected Results - -The Bearer type change from SN terminated split bearer to SN terminated MCG bearer (MN initiated) is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -### 2.2.1.26.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.13.1/5.6.13.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and step 2: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT - - o All U-Plane data recorded in the X2 logs (ie, all U-Plane data transmission from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and step 2: - - o All U-Plane data sent from the Test UE or UE emulator via LTE RAT or NR RAT is recorded in the S1 logs - - o All U-Plane data sent from the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 log -- Regarding the downlink U-Plane data generated in step 4: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT -- Regarding the uplink U-Plane data generated in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT or NR RAT is recorded in the S1 logs - - o All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs - -## 2.2.1.27 Bearer type change from SN terminated split bearer to SN terminated MCG bearer (SN initiated) - -### 2.2.1.27.1 Test Purpose - -The purpose of this test case is to verify that the SN (en-gNB) initiated Secondary Node Modification procedure to perform bearer type change from SN terminated split bearer to SN terminated MCG bearer with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.6.14. - -### 2.2.1.27.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.14 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform Secondary Node Addition procedure and Secondary Node Modification procedure (SN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc.) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content, S1-U UP content - -### 2.2.1.27.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB (MN) and en-gNB (SN) according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (eg, SN terminated split bearer) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.2.1.27.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during bearer type change operation from SN terminated split bearer to SN terminated MCG bearer (SN initiated). It is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform Secondary Node Modification procedure from SN (en-gNB) side to trigger the bearer type change from SN terminated split bearer to SN terminated MCG bearer - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Block the en-gNB cell (SN). One method is to use O&M command in the en-gNB to block the NR cell -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly in case of SN terminated MCG bearer configuration. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the MCG Bearer(s) usage of the LTE is to transfer user plane data at data rates high enough for the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -## 2.2.1.27.5 Expected Results and Log Observation - -### 2.2.1.27.5.1 Expected Results - -The Bearer type change from SN terminated split bearer to SN terminated MCG bearer (SN initiated) is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -### 2.2.1.27.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.14.1/5.6.14.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and step 2: - - All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - All U-Plane data recorded in the X2 logs (ie, all U-Plane data transmission from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and step 2: - - All U-Plane data sent from the Test UE or UE emulator via LTE RAT or NR RAT is recorded in the S1 logs - - All U-Plane data sent from the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs - -- Regarding the downlink U-Plane data generated in step 4: - - All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT - - All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT -- Regarding the uplink U-Plane data generated in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT is recorded in the S1 logs - - All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs - -The message flow and IEs for “Bearer type change from SN terminated split bearer to SN terminated MCG bearer (SN initiated) – X2 message flow, successful operation” are specified in the NR C-Plane profile specification [2] Sections 5.6.14.1/5.6.14.2. - -## 2.2.1.28 E-UTRA - NR Cell Resource Coordination (MN initiated, Option 3x/3a) - -### 2.2.1.28.1 Test Purpose - -The purpose of this test case is to verify that the E-UTRA - NR Cell Resource Coordination procedure from MN (eNB) side to request the exchange the DSS information between MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.8.1. - -### 2.2.1.28.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.8.1 of the NR C-Plane profile specification [2] -- The coverage of eNB cell (MN) and en-gNB cell (SN) overlap -- The MN (eNB) cell and SN (en-gNB) cell are same frequency band - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc.) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -### 2.2.1.28.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Enable the Dynamic Spectrum Sharing in MN (eNB) cell and SN (en-gNB) cell -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed - -- Secondary Node Addition (eg, SN terminated split bearer or SN terminated SCG bearer) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.2.1.28.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly for SN terminated split bearer or SN terminated SCG bearer. - -2. Perform the E-UTRA - NR Cell Resource Coordination procedure from MN (eNB) side to trigger the coordination of radio resource allocation between MN (eNB) and SN (en-gNB) that are sharing spectrum - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Increase the load of eNB cell (MN), eg, using more Test UE or UE emulator to send/receive traffic. The MN (eNB) requests more resources from SN (en-gNB) to serve the Test UE or UE emulator via LTE RAT. -3. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -#### 2.2.1.28.5 Expected Results and Log Observation - -##### 2.2.1.28.5.1 Expected Results - -The E-UTRA - NR Cell Resource Coordination procedure (MN initiated) with the coordination of radio resource allocation between MN (eNB) and SN (en-gNB) that are sharing spectrum executed successfully, and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.2.1.28.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.8.1.1/5.8.1.2. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and step 2: - - All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - All U-Plane data recorded in the X2 logs is correctly received by the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from en-gNB to eNB) is recorded in the X2 logs in case of EN-DC operation with SN terminated split bearer -- Regarding the uplink U-Plane data generated in step 1 and step 2: - - All U-Plane data sent from the Test UE or UE emulator via LTE RAT or NR RAT is recorded in the S1 logs - - All U-Plane data sent from the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs in case of EN-DC operation with SN terminated split bearer - -## 2.2.1.29 E-UTRA - NR Cell Resource Coordination (SN initiated, Option 3x/3a) - -### 2.2.1.29.1 Test Purpose - -The purpose of this test case is to verify that the E-UTRA - NR Cell Resource Coordination procedure from SN (en-gNB) side to request the exchange the DSS information between MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.8.2. - -### 2.2.1.29.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.8.2 of the NR C-Plane profile specification [2] -- The coverage of eNB cell (MN) and en-gNB cell (SN) overlap -- The MN (eNB) cell and SN (en-gNB) cell are same frequency band - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc.) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -### 2.2.1.29.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Enable the Dynamic Spectrum Sharing in MN (eNB) cell and SN (en-gNB) cell -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (eg, SN terminated split bearer or SN terminated SCG bearer) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.2.1.29.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly for SN terminated split bearer or SN terminated SCG bearer. - -2. Perform the E-UTRA - NR Cell Resource Coordination procedure from SN (en-gNB) side to trigger the coordination of radio resource allocation between MN (eNB) and SN (en-gNB) that are sharing spectrum - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Increase the load of en-gNB cell (SN), eg, using more Test UE or UE emulator to send/receive traffic. The SN (en-gNB) requests more resources from MN (eNB) to serve the Test UE or UE emulator via NR RAT. -3. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -## 2.2.1.29.5 Expected Results and Log Observation - -### 2.2.1.29.5.1 Expected Results - -The E-UTRA - NR Cell Resource Coordination procedure (SN initiated) with the coordination of radio resource allocation between MN (eNB) and SN (en-gNB) that are sharing spectrum executed successfully, and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -### 2.2.1.29.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.8.2.1/5.8.2.2. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and step 2: - - All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - All U-Plane data recorded in the X2 logs is correctly received by the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from en-gNB to eNB) in case of EN-DC operation with SN terminated split bearer -- Regarding the uplink U-Plane data generated in step 1 and step 2: - - All U-Plane data sent from the Test UE or UE emulator via LTE RAT or NR RAT is recorded in the S1 logs - - All U-Plane data sent from the Test UE or UE emulator via NR RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs in case of EN-DC operation with SN terminated split bearer - -## 2.2.1.30 Allowed Band Combination list update (MN initiated) - -### 2.2.1.30.1 Test Purpose - -The purpose of this test case is to verify that the MN (eNB) initiated Allowed Band Combination list update procedure with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.6.2. - -### 2.2.1.30.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.2 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform MN initiated Allowed Band Combination list update procedure - -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -### 2.2.1.30.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.2.1.30.4 Procedure - -1. Perform Allowed Band Combination list update procedure (MN initiated) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. The condition by which eNB update an allowedBC-ListMRDC to the en-gNB depends on the eNB implementation. Still, we can create a situation where Allowed Band Combination list update occurs. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the eNB SCell. In this specific case, the retained multiple LTE SCells are deleted and the eNB causes Band Combination list to be updated. - -2. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -### 2.2.1.30.5 Expected Results and Log Observation - -#### 2.2.1.30.5.1 Expected Results - -The Allowed Band Combination list update (MN initiated) procedure is successfully completed. - -#### 2.2.1.30.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.2.1/5.6.2.2. - -If any of the following listed IEs is observed in the X2 log. - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -X2 logs recorded in the Protocol Analyzer show that: - -- After step 1 the updated allowedBC-ListMRDC is applied in en-gNB: - - o An example of how to observe the updated allowedBC-ListMRDC is to check X2 log. The exact method to observe the updated allowedBC-ListMRDC is out of scope of this specification. - -## 2.2.1.3.1 Configured Band Combination update by PSCell/SCell change (SN initiated) - -### 2.2.1.3.1.1 Test Purpose - -The purpose of this test case is to verify that the SN (en-gNB) initiated Configured Band Combination update by PSCell/SCell change procedure with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] section 5.6.3. - -### 2.2.1.3.1.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.3 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform SN initiated Configured Band Combination update by PSCell/SCell change procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -### 2.2.1.3.1.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.2.1.3.1.4 Procedure - -1. Perform Configured Band Combination update by PSCell/SCell change procedure (SN initiated) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Perform PSCell Change using SRB3 for RRC Reconfiguration procedure is completed and selectedBandCombination is updated -2. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -### 2.2.1.3.1.5 Expected Results and Log Observation - -#### 2.2.1.3.1.5.1 Expected Results - -The Configured Band Combination update by PSCell/SCell change (SN initiated) procedure is successfully completed. - -#### 2.2.1.3.1.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.3.1/5.6.3.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -X2 logs recorded in the Protocol Analyzer show that: - -- After step 1 the updated selectedBandCombination is applied in eNB: - - An example of how to observe the updated selectedBandCombination is to check X2 log. The exact method to observe the updated selectedBandCombination is out of scope of this specification. - -## 2.2.1.32 SCG config query (MN initiated) - -### 2.2.1.32.1 Test Purpose - -The purpose of this test case is to verify that the MN (eNB) initiated SCG config query procedure with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.6.4. - -### 2.2.1.32.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.4 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform MN initiated SCG config query procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -### 2.2.1.32.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.2.1.32.4 Procedure - -1. Perform SCG config query procedure (MN initiated) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Perform Secondary Node Change (MN initiated, Option 3x) procedure (See step 2 in 2.2.1.10.4). This test method requires the addition of the following to the initial conditions. - -en-gNB emulator: used to perform Secondary Node Change (MN initiated, Optional 3x) procedure. - -2. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -### 2.2.1.32.5 Expected Results and Log Observation - -#### 2.2.1.32.5.1 Expected Results - -The SCG config query procedure is successfully completed. - -#### 2.2.1.32.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.4.1/5.6.4.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -X2 logs recorded in the Protocol Analyzer show that: - -- After step 1 the scg-CellGroupConfig and/or scg-RB-Config is applied in eNB: - - An example of how to observe the scg-CellGroupConfig and/or scg-RB-Config is to check X2 log. The exact method to observe the SCG configuration Query is out of scope of this specification - -### 2.2.1.33 Full Reconfiguration (SN initiated) - -#### 2.2.1.33.1 Test Purpose - -The purpose of this test case is to verify that the SN (en-gNB) initiated Full Reconfiguration procedure with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.6.22. - -#### 2.2.1.33.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.22 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform SN initiated Full Reconfiguration procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc.) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -#### 2.2.1.33.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -#### 2.2.1.33.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform Full Reconfiguration procedure (SN initiated) to reset PDCP COUNT using full reconfiguration option in case of PDCP Count wrap around - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Perform data transfer between the Application Test Server and the Test UE or UE emulator and cause PDCP count to reset -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful PDCP COUNT reset. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -#### 2.2.1.33.5 Expected Results and Log Observation - -##### 2.2.1.33.5.1 Expected Results - -The Full Reconfiguration procedure (SN initiated) is successfully completed - -##### 2.2.1.33.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.22.1/5.6.22.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “SGNB MODIFICATION CONFIRM” - -the test result shall be determined to be 'successful with remarks'. - -S1 and X2 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the S1 logs is correctly received by the Test UE or emulated UE via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT or NR RAT is recorded in the S1 logs - -### 2.2.1.34 UE measurement transfer - -#### 2.2.1.34.1 Test Purpose - -The purpose of this test case is to verify that the UE measurement transfer procedure with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.7.1. - -#### 2.2.1.34.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.7.1 of NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cells overlap -- en-gNB has at least 2 cells configured and in operation - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform UE measurement transfer procedure using ULInformationTransferMRDC message -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -#### 2.2.1.34.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 Setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and one of SN (en-gNB) cells -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -#### 2.2.1.34.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during the UE measurement transfer procedure. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform UE measurement transfer procedure - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. The condition by which UE sends an ULInformationTransferMRDC message to the MN depends on the configuration done by MN. Still, we can create a situation where UE measurement transfer occurs. There should be at least two en-gNB cells within the coverage of a cell under eNB. The first cell under en-gNB which is PSCell and the second cell under en-gNB which is not PSCell. If the tester manually degrades the radio quality of the first en-gNB cell this can be the trigger of the UE measurement transfer procedure. - -One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the first en-gNB cell. In this specific case, the first en-gNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger the UE measurement transfer procedure. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful UE measurement transfer procedure. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -#### 2.2.1.34.5 Expected Results and Log Observation - -##### 2.2.1.34.5.1 Expected Results - -The UE measurement transfer procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.2.1.34.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in NR C-Plane profile specification [2] Sections 5.7.1.1/5.7.1.2. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to eNB) is correctly received by the Test UE or emulated UE via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT or NR RAT is recorded in the S1 logs - - All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs - -## 2.2.1.35 Inter-Master Node Handover (with SN change, option 3x) - -### 2.2.1.35.1 Test Purpose - -The purpose of this test case is to verify that the Inter-Master Node Handover (with SN Change, Option 3x) procedure with two eNBs and two en-gNBs from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.4.2.1. - -### 2.2.1.35.2 Minimum Requirements - -DUTs: Two eNBs (Source eNB – S-MN, Target eNB – T-MN) and two en-gNBs (Source gNB – S-SN, Target gNB – T-SN): - -- DUTs shall apply the parameter condition specified in 5.4.2 of the NR C-Plane profile specification [2] -- The coverage of Source eNB cell (S-MN) overlaps with Target eNB cell (T-MN) and Source en-gNB cell (S-SN) -- The coverage of Target eNB cell (T-MN) overlaps with Target en-gNB cell (T-SN) - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Inter-Master Node Handover with Secondary Node Change procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe all three X2 links procedural flows and content - -### 2.2.1.35.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNBs according to the NR C-Plane profile specification [2] -- X2 setup procedure between the source eNB and target eNB specified in 3GPP TS 36.423 [12] has been successfully completed - -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the Source eNB cell (S-MN) and en-gNB (S-SN) cell -- Secondary Node Addition (Option 3x) procedure between the Source eNB (S-MN) and en-gNB (S-SN) has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is ongoing (via the LTE and NR RATs) - -#### 2.2.1.35.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the Inter-Master Node Handover procedure. - -This involves observing that the user plane data forwarded from the source en-gNB to the target en-gNB, optionally via the source and/or target eNB over the X2 interface during the Inter-Master Node Handover procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates which are high enough for the source en-gNB to start buffering user plane downlink data prior to the change of the en-gNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform Inter-Master Node Handover (with SN Change, Option 3x) procedure from source eNB (S-MN) to target eNB (T-MN) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. The Test UE or UE emulator sends a Measurement Report to the source eNB (S-MN). One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and source eNB (S-MN) and the target eNB (T-MN) simultaneously. In this specific case, the source eNB (S-MN) cell can start off with low attenuation applied which is subsequently increased. At the same time, the target eNB (T-MN) cell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the measurement report to be sent to the source eNB (S-MN). - - b. The target eNB (T-MN) decides to change the Secondary Node, the target eNB (T-MN) sends the SgNB Addition Request to the target gNB (T-SN). -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during Split Bearer(s) operation in EN-DC Option 3x configuration. This involves observing that the user plane data transferred over the X2 in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -### 2.2.1.35.5 Expected Results and Log Observation - -#### 2.2.1.35.5.1 Expected Results - -The Inter-Master Node Handover with Secondary Node Change procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.2.1.35.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flow specified in NR C-Plane profile specification [2] Sections 5.4.2.1/5.4.2.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “E-RABs Not Admitted List” in “SGNB ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “SGNB ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “SGNB RELEASE REQUEST ACKNOWLEDGE” -- “Configuration rejected” in “SGNB RECONFIGURATION COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or emulated UE via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs which are: - - o Forwarded to the Test UE or emulated UE from the source en-gNB towards the source eNB and from the source eNB towards the target en-gNB through target eNB, via their corresponding established DL Forwarding GTP Tunnels, is correctly received by the Test UE or emulated UE via the NR RAT - - o Transmitted to the Test UE or emulated UE from the target en-gNB to the target eNB, via the established MeNB DL GTP Tunnels, is correctly received by the Test UE or emulated UE via the LTE RAT - -Note: this test verification process does not impose a requirement for the target en-gNB to transmit the user plane data which it has received from the target eNB (as part of the downlink data forwarding procedure) to the Test UE or emulated UE via the source eNB and LTE RAT, but rather it is to verify the correct operation of the transmit operation via the target eNB and the LTE RAT when it is used by the target en-gNB. - -- Regarding the downlink U-Plane data generated in step 4: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or emulated UE via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from target en-gNB to target eNB) is correctly received by the Test UE or emulated UE via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT or NR RAT is recorded in the S1 logs - -- o All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT (ie, all U-Plane data to be transferred from source eNB to source en-gNB in step 1 and target eNB to target en-gNB in step 4) is recorded in the X2 logs - -### 2.2.1.36 EN-DC Resource Status Reporting Initiation - -#### 2.2.1.36.1 Test Purpose - -The purpose of this test case is to verify that the Resource Status Reporting Initiation procedure with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.1.8.1. - -#### 2.2.1.36.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB. - -Testing tools which are required for this test scenario: - -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UE (emulator) NAS protocol -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -#### 2.2.1.36.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] - -#### 2.2.1.36.4 Procedure - -1. Perform the EN-DC Resource Status Reporting Initiation procedure to start a measurement in the source node - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One method is to use O&M command in the source node in order to initiate the Resource Status Reporting Initiation procedure to start the measurement. - -Note: In step 1, the source node and the target node have the following two cases: - -Case 1) The source node is the eNB and the target node is the en-gNB. - -Case 2) The source node is the en-gNB and the target node is the eNB. - -2. Perform the EN-DC Resource Status Reporting Initiation procedure to add cells to report for a measurement in the source node - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One method is to use O&M command in the source node in order to initiate the Resource Status Reporting Initiation procedure to add cells to the measurement. - -Note: The same case as step 1 needs to be performed. - -3. Perform the Resource Status Reporting Initiation procedure to stop a measurement in the source node - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One method is to use O&M command in the source node in order to initiate the Resource Status Reporting Initiation procedure to stop the measurement. - -Note: The same case as step 1 needs to be performed. - -Note: Repeat step 1 to step 3 with a different case from the case performed above. - -4. Observe the Protocol Analyzer X2 logs - -### 2.2.1.36.5 Expected Results and Log Observation - -#### 2.2.1.36.5.1 Expected Results - -The start of the measurement in the target node (Case 1) en-gNB, (Case 2) eNB) is successfully completed by performing the EN-DC Resource Status Reporting Initiation procedure from the source node (Case 1) eNB, (Case 2) en-gNB) in step 1. - -The cell addition for the measurement in the target node (Case 1) en-gNB, (Case 2) eNB) initiated in step 1 is successfully completed by performing the EN-DC Resource Status Reporting Initiation procedure from the source node (Case 1) eNB, (Case 2) en-gNB) in step 2. - -The stop of the measurement in the target node (Case 1) en-gNB, (Case 2) eNB) is successfully completed by performing the Resource Status Reporting Initiation procedure from the source node (Case 1) eNB, (Case 2) en-gNB) in step 3. - -#### 2.2.1.36.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.1.8.1.1/4.1.8.1.2.1/4.1.8.1.2.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “EN-DC RESOURCE STATUS RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -### 2.2.1.37 EN-DC Resource Status Reporting - -#### 2.2.1.37.1 Test Purpose - -The purpose of this test case is to verify that the Resource Status Reporting procedure with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.1.8.2. - -#### 2.2.1.37.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB. - -Testing tools which are required for this test scenario: - -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UE (emulator) NAS protocol -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -#### 2.2.1.37.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] - -#### 2.2.1.37.4 Procedure - -1. Perform the EN-DC Resource Status Reporting procedure from the en-gNB to report the result of on-going load measurements - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Perform the EN-DC Resource Status Reporting Initiation procedure from the eNB (See case 1 of step 1 in 2.2.1.36.4) - -Note: How to perform the specific procedures for the traffic load are out of scope of this specification. - -2. Perform the EN-DC Resource Status Reporting procedure from the eNB to report the result of on-going load measurements - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Perform the EN-DC Resource Status Reporting Initiation procedure from the en-gNB (See case 2 of step 1 in 2.2.1.36.4) - -Note: How to perform the specific procedures for the traffic load are out of scope of this specification. - -3. Observe the Protocol Analyzer X2 logs - -#### 2.2.1.37.5 Expected Results and Log Observation - -##### 2.2.1.37.5.1 Expected Results - -The EN-DC Resource Status Reporting procedure from the en-gNB in step 1 is successfully completed. - -The EN-DC Resource Status Reporting procedure from the eNB in step 2 is successfully completed. - -##### 2.2.1.37.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.1.8.2.1/4.1.8.2.2.1/4.1.8.2.2.2. - -#### 2.2.1.38 Change of QCI (MN initiated) - -##### 2.2.1.38.1 Test Purpose - -The purpose of this test case is to verify that the eNB node initiated modify QCI (and/or ARP) of the SN terminated split bearer procedure with eNB and en-gNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 5.6.23. - -##### 2.2.1.38.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply parameter condition specified in 5.6.23 of the NR C-Plane profile specification [2] -- The coverage of eNB cell (MN) overlaps with en-gNB cell (SN) - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and EN-DC: used to perform MN initiated Secondary Node Modification -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UE (emulator) NAS protocol - -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -### 2.2.1.38.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.2.1.38.4 Procedures - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator using an E-RAB from an existing LTE bearer - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform change of QCI (MN initiated) procedure - -The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT - -- a. Change the QCI used in step 1 - -One method is to trigger Core or Core emulator (MME) to change the QCI of the ERAB of an existing LTE bearer. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds using E-RAB with changed QCI - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful change of QCI procedure (MN initiated). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs - -### 2.2.1.38.5 Expected Results and Log Observation - -#### 2.2.1.38.5.1 Expected Results - -The change of QCI procedure (MN initiated) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -### 2.2.1.38.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer and the Test UE or UE emulator are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.23.1/5.6.23.2. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the U-Plane data transmission. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the C-Plane: - - Check that step 2 QCI in IE “Full E-RAB Level QoS Parameters” in IE “E-RABs To Be Modified List” included in message “SGNB MODIFICATION REQUEST” performs correctly -- Regarding the downlink U-Plane data generated in step1, after step 2 and in step 4: - - All U-Plane data recorded in the S1 and X2 logs is correctly received by the Test UE or UE emulator. - - Check that the data is flowing using the new QCI in step 4 -- Regarding the uplink U-Plane data generated in step1, after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator is recorded in the S1 and X2 logs - - Check that the data is flowing using the new QCI in step 4 - -### 2.2.1.39 Measurement ID Coordination (MN initiated) - -#### 2.2.1.39.1 Test Purpose - -The purpose of this test case is to verify that the Measurement ID Coordination (MN initiated) with eNB and en-gNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] section 5.6.24. - -#### 2.2.1.39.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.24 of NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Measurement ID Coordination procedure (MN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -#### 2.2.1.39.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and service request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.2.1. 39.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. -2. Perform Measurement ID Coordination procedure (MN initiated) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of the scope of this specification and is left up to the implementation of the DUT. - -- a. An eNB sends maximum number of measurement identities to en-gNB. One method is to use O&M command in the eNB to send for measurement identities to en-gNB. -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator. - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the UE context was modified. - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs. - -### 2.2.1. 39.5 Expected Results and Log observation - -#### 2.2.1. 39.5.1 Expected Results - -The Measurement ID Coordination procedure (MN initiated) is successfully completed. - -#### 2.2.1. 39.5.2 Log observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in NR C-Plane profile specification [2] Sections 5.6.24.1/5.6.24.2. - -If any of the following listed IEs is observed in the X2 logs. - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” -- “Configuration rejected” in “SGNB RECONFIGURATION COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT - -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT or NR RAT is recorded in the S1 logs - - All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs - -## 2.2.1.40 DRB ID change/Security Key change (SN initiated) - -### 2.2.1.40.1 Test Purpose - -The purpose of this test case is to verify that the SN (en-gNB) initiated DRB ID change/Security Key change procedure with MN (eNB) and SN (en-gNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 5.6.21. - -### 2.2.1.40.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.21 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform SN (en-gNB) initiated DRB ID change/Security Key change procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc.) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -### 2.2.1.40.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.2.1.40.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the UE or UE emulator. - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform SN initiated DRB ID change/Security Key change procedure. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Perform data transfer between the Application Test Server and the Test UE or UE emulator to increment the PDCP Count. This may trigger either a DRB ID change in case of PDCP Count wrap around, or a Security Key change in case of PDCP Count wrap around prevention. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator. - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful DRB ID change/Security Key change. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs. - -#### 2.2.1.40.5 Expected Results and Log Observation - -##### 2.2.1.40.5.1 Expected Results - -The SN (en-gNB) initiated DRB ID change/Security Key change procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.2.1.40.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.21.1/5.6.21.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “SGNB MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -S1 and X2 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- • After step 2 the updated security key is applied in UE or UE emulator in case of Security Key change procedure: - - o An example of how to observe the updated security key is to check the UE emulator log. The exact method to observe the updated security key is out of scope of this specification -- • Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or emulated UE via LTE RAT or NR RAT -- • Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - -- o All U-Plane data transmitted by the Test UE or emulated UE via LTE RAT or NR RAT is recorded in the S1 logs - -#### 2.2.1.4.1 Measurement ID Coordination (SN initiated) - -##### 2.2.1.4.1.1 Test Purpose - -The purpose of this test case is to verify that the Measurement ID Coordination (SN initiated) with eNB and en-gNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] section 5.6.25. - -##### 2.2.1.4.1.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply the parameter condition specified in 5.6.25 of NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Measurement ID Coordination procedure (SN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and content - -##### 2.2.1.4.1.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and service request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -##### 2.2.1.4.1.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. -2. Perform Measurement ID Coordination procedure (SN initiated) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of the scope of this specification and is left up to the implementation of the DUT. - -- a. An en-gNB requests eNB for new maximum number of measurement identities. eNB responds with measurement identities to en-gNB. One method is to use O&M command in the en-gNB to request for measurement identities to eNB. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator. -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Measurement ID Coordination (SN initiated). - -5. Observe the Protocol Analyzer S1 and X2 logs and Test UE or UE emulator logs. - -#### 2.2.1.41.5 Expected Results and Log observation - -##### 2.2.1.41.5.1 Expected Results - -The Measurement ID Coordination procedure (SN initiated) is successfully completed. - -##### 2.2.1.41.5.2 Log observation - -X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in NR C-Plane profile specification [2] Sections 5.6.25.1/5.6.25.2. - -If any of the following listed IEs is observed in the X2 logs. - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “SGNB MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -X2 and S1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the S1 logs is correctly received by the Test UE or UE emulator via LTE RAT or NR RAT - - o All U-Plane data recorded in the X2 logs (ie, all U-Plane data transferred from en-gNB to eNB) is correctly received by the Test UE or UE emulator via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT or NR RAT is recorded in the S1 logs - - o All U-Plane data transmitted by the Test UE or UE emulator via LTE RAT (ie, all U-Plane data to be transferred from eNB to en-gNB) is recorded in the X2 logs - -## 2.2.2 X2 U-Plane IOT Test Cases - -### 2.2.2.1 Node behaviour of the corresponding node with RLC-AM and/or RLC-UM - -#### 2.2.2.1.1 Test Purpose - -The purpose of this test case is to verify that the behaviour of the corresponding node procedure with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.1.1. - -Note: The test cases for the behaviour of the corresponding node sending DDS when events lost packet detection and stop scheduling for the data bearer occur are included in the chapter 2.2.2.3. - -#### 2.2.2.1.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and contents - -### 2.2.2.1.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transmission has not been performed via the NR RAT, eg, keeping Option 3x with NR radio quality low enough - -Note: This test case is used to verify that the eNB does not discard any of its buffered packets in events such as Radio Link Outage over the LTE RAT unless it receives discard indication from the higher layers or from the en-gNB hosting NR PDCP, such as the buffer discard indication from the en-gNB. This initial condition ensures that en-gNB does not send the buffer discard indication to the eNB. - -### 2.2.2.1.4 Procedure - -1. Perform data transfer from the Application Test Server to the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for eNB to buffer the downlink data. The exact data rate that is generated is not specified, but it is up to eNB vendor implementation. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Trigger radio link outage on the LTE RAT. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To move the Test UE or UE emulator away from the coverage of the eNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the eNB cell. In this specific case, the eNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. - -3. Trigger radio link resume on the LTE RAT. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To move the Test UE or UE emulator back within the coverage of the eNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the eNB cell. In this specific case, the eNB cell can start off with high attenuation applied which is subsequently decreased to a level which can trigger radio link resume condition. -4. Stop data transfer from the Application Test Server to the Test UE or UE emulator. - 5. Observe the Protocol Analyzer X2 logs and Test UE or UE emulator logs. - -### 2.2.2.1.5 Expected Results and Log Observation - -#### 2.2.2.1.5.1 Expected Results - -The behaviour of eNB is aligned with the requirement specified in Section 4.1.1.1 of NR U-Plane profile specification [3]. - -#### 2.2.2.1.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.1.1 and the following should be observed: - -- eNB sends DDDS message which includes the *Cause Value* IE with value '1', '3' or '4' to en-gNB after step 2 -- eNB sends DDDS message which includes the *Cause Value* IE with value '2', '5' or '6' to en-gNB after step 3 - -Note: these are to confirm if the Radio Link Outage operation has been performed. - -- Logs recorded in the Test UE or UE emulator are aligned with the NR U-Plane profile specification [3] Section 4.1.1.1 and the following should be observed: - - After the end of step 2 and before the start of step 3, Test UE or UE emulator does NOT receive any data which is transmitted from eNB in step 1 - - After step 3, Test UE or UE emulator receives all the data which is transmitted from eNB before triggering Radio Link Outage in step 1 - -### 2.2.2.2 General for Elements for the NR user plane protocols with RLC-AM and/or RLC-UM - -#### 2.2.2.2.1 Test Purpose - -The purpose of this test case is to verify that the general behaviour with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.1. - -#### 2.2.2.2.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and contents -- Network Impairment Emulator: used to discard selected packets transmitted via the X2 link - -### 2.2.2.2.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Network Impairment Emulator is physically connected in-line to the X2 link between the eNB and en-gNB -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cell -- Data transmission has not been performed via the LTE RAT - -Note: the intention of this is to make a condition where any of the optional fields in DDDS has no available value. - -### 2.2.2.2.4 Procedure - -1. Trigger Secondary Node Addition procedure - -Note: the intention of this step is to have the eNB send DDDS which does not include any of the optional fields as the corresponding value is not yet available. - -2. Perform data transfer from the Application Test Server to the Test UE or UE emulator until the end of step 6. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, meaningful to verify that the user plane transmission operates correctly. - -Note: the intention of this step is to make a situation where the values of *Highest Transmitted NR PDCP Sequence Number IE* and *Highest Successfully Delivered NR PDCP Sequence Number IE* in DDDS are valid. - -3. After the Application Test Server starts to transmit downlink data, drop some packets sent from the en-gNB to eNB via X2 link by using the Network Impairment Emulator inserted in-line in the X2 link - -Note: the intention of this step is to make a situation where the value of *Lost Packet Report IE* is valid. - -4. Trigger the en-gNB to send Downlink User Data PDU(s) including *Retransmission flag IE* with '1' to eNB - -Note: the intention of this step is to make a situation where the value of *Highest Retransmitted NR PDCP Sequence Number IE* and *Highest Successfully Delivered Retransmitted NR PDCP Sequence Number IE* is valid. - -The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -5. Trigger radio link outage condition in the eNB at least once - -Note: the intention of this step is to make a situation where the value of *Cause Value IE* is valid. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. To gradually move the Test UE or UE emulator away from the coverage of the eNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the eNB cell. In this specific case, the eNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. -6. Stop scheduling in the eNB - -Note: the intention of this step is to create a situation where the value of *Final Frame Indication* IE is valid. - -The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -7. Observe the Protocol Analyzer X2 logs and Test UE or UE emulator logs - -## 2.2.2.2.5 Expected Results and Log Observation - -### 2.2.2.2.5.1 Expected Results - -The behaviour of eNB and en-gNB is aligned with the requirement specified in Section 4.1.2.1 of NR U-Plane profile specification [3]. - -### 2.2.2.2.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.1 and the following should be observed: - -- The DDDSs captured during step 1 have the following IEs with the value '0': - - Highest Transmitted NR PDCP SN Ind IE - - Highest Delivered NR PDCP SN Ind IE - - Final Frame Indication IE - - Lost Packet Report IE - - Highest Retransmitted NR PDCP SN Ind IE - - Highest Delivered Retransmitted NR PDCP SN Ind IE - - Cause Report IE -- One or more DDDSs captured after the beginning of the step 2 have one or both of the following IEs with the value '1': - - Highest Transmitted NR PDCP SN Ind IE - - Highest Delivered NR PDCP SN Ind IE -- One or more DDDSs captured after the beginning of the step 3 have *Lost Packet Report* IE with the value '1' -- One or more DDDSs captured after the beginning of the step 4 have one or both of the following IEs with the value '1': - - Highest Retransmitted NR PDCP SN Ind IE - - Highest Delivered Retransmitted NR PDCP SN Ind IE -- One or more DDDSs captured after the beginning of the step 5 have *Cause Report* IE with the value '1' and *Cause value* IE with the value '1', '3', or '4' -- One or more DDDSs captured after the beginning of the step 6 have *Final Frame Indication* IE with the value '1' - -### 2.2.2.3 Report Polling with RLC-AM and/or RLC-UM - -#### 2.2.2.3.1 Test Purpose - -The purpose of this test case is to verify that the Report Polling procedure with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.2. - -#### 2.2.2.3.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and contents -- Network Impairment Emulator: used to discard selected packets transmitted via the X2 link - -#### 2.2.2.3.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Network Impairment Emulator is physically connected in-line to the X2 link between the eNB and en-gNB -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cell -- Secondary Node Addition (Option 3x) procedure between eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.2.2.3.4 Procedure - -1. Perform data transfer from the Application Test Server to the Test UE or UE emulator until the end of step 5. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, to meaningfully verify that the user plane transmission operates correctly. - -Send Downlink User Data PDU(s) including *Report polling* IE with '1' from en-gNB to eNB at least once. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. en-gNB transmits some data packets to eNB (ie, step 1) -2. Drop some packets sent from en-gNB to eNB via X2 link by using the Network Impairment Emulator inserted in-line in the X2 link. - -Note: the intention of this step is to make a situation where “Lost packet detection” occurs in eNB. - -3. Trigger radio link outage condition in the eNB. - -Note: the intention of this step is to make a situation where “Radio link outage” occurs in eNB. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To gradually move the Test UE or UE emulator away from the coverage of the eNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the eNB cell. In this specific case, the eNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. -4. Trigger radio link resume condition on LTE RAT. -5. Stop scheduling in the eNB. - -Note: the intention of this step is to make a situation where “Stop scheduling for the data bearer” occurs in eNB. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stop downlink data transmission -6. Observe the Protocol Analyzer X2 logs and Test UE or UE emulator logs. - -### 2.2.2.3.5 Expected Results and Log Observation - -#### 2.2.2.3.5.1 Expected Results - -The use of Report Polling function is aligned with the requirement specified in Section 4.1.2.2 of NR U-Plane profile specification [3]. - -#### 2.2.2.3.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.2 and the following should be observed: - -- After the beginning of step 2: - - en-gNB sends eNB one or more Downlink User Data PDU(s) including *Report polling* IE with the value ‘1’ - - eNB sends en-gNB DDDS as soon as possible after receiving the corresponding Downlink User Data PDU(s) -- After the beginning of step 3, eNB sends en-gNB DDDS where following IEs show the dropped packets: - - Start of lost NR-U Sequence Number range IE(s) - - End of lost NR-U Sequence Number range IE(s) -- After the beginning of step 4, eNB sends en-gNB DDDS including *Cause Value* IE with the value ‘1’, ‘3’ or ‘4’ -- After the beginning of step 6, eNB sends en-gNB DDDS including *Final Frame Indication* IE with the value ‘1’, and then eNB does not send en-gNB DDDS including any updated instance of the following IEs - - Highest successfully delivered NR PDCP Sequence Number IE - -- o Highest transmitted NR PDCP Sequence Number IE -- o Highest successfully delivered retransmitted NR PDCP Sequence Number IE -- o Highest retransmitted NR PDCP Sequence Number IE - -## 2.2.2.4 Buffer discard indication with RLC-AM and/or RLC-UM - -### 2.2.2.4.1 Test Purpose - -The purpose of this test case is to verify that the use of the *DL Discard Blocks* IE and the *DL Flush IE* with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.3. - -### 2.2.2.4.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and contents - -### 2.2.2.4.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cell -- Secondary Node Addition (Option 3x) procedure between eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.2.2.4.4 Procedure - -1. Perform data transfer from the Application Test Server to the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for eNB to buffer the downlink data. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). -2. en-gNB to send the DL User Data message which includes the *DL Discard Blocks* IE with value '1'. - -Note: the purpose of this step is to indicate from en-gNB to eNB to discard NR PDCP PDUs. It is up to en-gNB implementation when to initiate this step. Specific test procedure needs to be considered taking into account the en-gNB implementation. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Tester sets small value in "discardTimer" in order that this timer expires before the en-gNB receives acknowledgement of the transmitted data from the eNB -3. en-gNB to send the DL User Data message which includes the *DL Flush* IE with value '1'. - -Note: the purpose of this step is to indicate from en-gNB to eNB to discard NR PDCP PDUs. It is up to en-gNB implementation when to initiate this step. Specific test procedure needs to be considered taking into account the en-gNB implementation. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Tester sets small value in "discardTimer" in order that this timer expires before the en-gNB receives acknowledgement of the transmitted data from the eNB -4. Observe the Protocol Analyzer X2 logs and Test UE or UE emulator logs. - -#### 2.2.2.4.5 Expected Results and Log Observation - -##### 2.2.2.4.5.1 Expected Results - -The use of *DL Discard Blocks* IE and the *DL Flush* IE is aligned with the requirement specified in Section 4.1.2.3 of NR U-Plane profile specification [3]. - -##### 2.2.2.4.5.2 Log Observation - -Logs Recorded in the Protocol Analyzer and the Test UE or emulated UE show that: - -- NR PDCP PDUs, which are indicated to be discarded in the DL User Data message in step 2, are NOT received by the Test UE or emulated UE - -Note: the NR PDCP PDUs to be discarded is indicated by the following IEs in the DL User Data message: - -- o en-gNB DL discard Number of blocks - - o DL discard NR PDCP PDU SN start - - o Discarded Block size present -- NR PDCP PDUs, which are indicated to be discarded in the DL User Data message in step 3, are NOT received by the Test UE or emulated UE. - -Note: the NR PDCP PDUs to be discarded is indicated by the following IEs in the DL User Data message: - -- o DL discard NR PDCP PDU SN present - -#### 2.2.2.5 User data existence flag with RLC-AM and/or RLC-UM - -##### 2.2.2.5.1 Test Purpose - -The purpose of this test case is to verify en-gNB's notification to the eNB of the existence of user data, but without using the *User data existence flag* IE, with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.4. - -Note: This feature is needed when the eNB does not support the *User data existence flag* IE eg, in the case when the eNB is designed to be compliant with older versions of the 3GPP specifications which do not support this IE. - -### 2.2.2.5.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of eNB cell and en-gNB cell overlap -- en-gNB shall activate the feature which is specified in Section 4.1.2.4 of NR U-Plane profile [3] - -Note: How to activate this feature is up to en-gNB implementation. One example is to activate it via M-Plane. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and contents - -### 2.2.2.5.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cell -- Secondary Node Addition (Option 3x) procedure between eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.2.2.5.4 Procedure - -1. Perform data transfer from the Application Test Server to the Test UE or UE emulator via X2. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, to meaningfully verify that the user plane transmission operates correctly. - -Note: the intention of this step is to avoid expiring some timers in eNB which monitor the activity of user data transfer (eg, DRX inactivity timer, UE inactive timer, etc). - -2. Decrease the amount of user data to be transmitted from the Application Test Server to the Test UE or UE emulator so that the user data can be transmitted via NR RAT only. With this condition perform data transmission for 60 seconds. - -Note: the intention of this step is to create a situation where the en-gNB sends actual user data to the eNB even when the amount of user data is small enough to be sent via the NR RAT only. In this test scenario, the NR RAT radio condition need not be ideal but shall be good enough to ensure that all user data can be transmitted through the NR RAT only. - -3. Stop data transfer. - -4. Observe the Protocol Analyzer X2 logs and Test UE or UE emulator logs. - -#### 2.2.2.5.5 Expected Results and Log Observation - -##### 2.2.2.5.5.1 Expected Results - -The behaviour of en-gNB is aligned with the requirement specified in Section 4.1.2.4 of NR U-Plane profile [3]. - -##### 2.2.2.5.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.4 and the following should be observed: - -- NR PDCP PDU is sent from en-gNB to eNB, which is frequently enough NOT to expire the timers described in the note in step 1 - -Note: The required frequency is up to eNB implementation, ie, the value of the timers used in the eNB. - -As a result of above, logs recorded in the Test UE or UE emulator shows: - -- Test UE or UE emulator keeps RRC\_Connected state without expiring DRX inactivity timer in LTE RAT as specified in 3GPP TS 36.331 [13] and 3GPP TS 36.321 [14], from the beginning of step 2 till before step 3 - -#### 2.2.2.6 Assistance Information Report polling with RLC-AM and/or RLC-UM - -##### 2.2.2.6.1 Test Purpose - -The purpose of this test case is to verify the use of the Assistance Information Report polling flag with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.5. - -##### 2.2.2.6.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and contents - -##### 2.2.2.6.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] - -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cell -- Secondary Node Addition (Option 3x) procedure between eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.2.2.6.4 Procedure - -1. Send Downlink User Data PDU(s) from en-gNB to eNB with *Assistance Information Report polling Flag* IE whose value is set to '1'. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. Send the Downlink User Data PDU(s) immediately after completing the Secondary Node Addition (Option 3x) procedure -2. Observe the Protocol Analyzer X2 logs and Test UE or UE emulator logs. - -#### 2.2.2.6.5 Expected Results and Log Observation - -##### 2.2.2.6.5.1 Expected Results - -The use of the Assistance Information Report polling flag is aligned to the requirement specified in Section 4.1.2.5 of NR U-Plane profile [3]. - -##### 2.2.2.6.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.5 and the following should be observed: - -- In step 1, one or more Downlink User Data PDU(s) sent by the en-gNB to the eNB include *Assistance Information Report polling Flag* IE with the value '1' -- After receiving the corresponding Downlink User Data PDU(s), AID is sent by the eNB to the en-gNB - -#### 2.2.2.7 Radio quality assistance information with RLC-AM and/or RLC-UM - -##### 2.2.2.7.1 Test Purpose - -The purpose of this test case is to verify the use of the *Radio quality assistance information* IE with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.6. - -##### 2.2.2.7.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of eNB cell and en-gNB cell overlap -- eNB shall be configured with the Assistance Information Type(s) to be reported in the AID message via M-Plane. In this version of the specification the following Assistance Information Types can be configured to be reported: - -- o '0'=UNKNOWN - -- o '1'=Average CQI -- o '2'=Average HARQ Failure -- o '3'=Average HARQ Retransmissions -- o '4'= DL Radio Quality Index -- o '5'= UL Radio Quality Index -- o '6'= Power Headroom Report - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and contents - -### 2.2.2.7.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cell -- Secondary Node Addition (Option 3x) procedure between eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.2.2.7.4 Procedure - -1. Send Downlink User Data PDU(s) from en-gNB to eNB with *Assistance Information Report polling Flag* IE whose value is set to '1'. This procedure shall be performed before the assistance information to be reported by the eNB becomes available. - -Note: the intention of this step is to create a situation where the eNB does not report the assistance information due to unavailability of the information. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Send the Downlink User Data PDU(s) immediately after completing the Secondary Node Addition (Option 3x) procedure -2. Create conditions which can help the eNB gather the information/measurements required for its configured Assistance Information Types. - -An example of how these conditions can be created is listed below. The exact method to create these conditions is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Send DL user data via LTE RAT so that eNB can obtain eg, CQI/HARQ ACK/Power headroom report from Test UE or UE emulator. - -3. Send Downlink User Data PDU(s) from en-gNB to eNB with Assistance Information Report polling Flag IE whose value is set to '1'. -4. Observe the Protocol Analyzer X2 logs and Test UE or UE emulator logs. - -#### 2.2.2.7.5 Expected Results and Log Observation - -##### 2.2.2.7.5.1 Expected Results - -The use of the *Radio quality assistance information* IE is aligned with the requirement specified in Section 4.1.2.6 of NR U-Plane profile [3]. - -##### 2.2.2.7.5.2 Log Observation - -X2 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.6 and the following should be observed: - -- After step 1, eNB sends the Assistance Information Data message to en-gNB, where the value of *Assistance Information Indication* IE is '0' - -Note: the intention is to validate that any configured assistance information is not reported at this moment. - -- After step 3, eNB sends the Assistance Information Data message to en-gNB, where *Assistance Information Type* IE, *Number of octets for Radio Quality Assistance Information Fields* IE, and *Radio Quality Assistance Information* IE corresponding to the configured assistance information are included - -Note: the intention is to validate that all the configured assistance information is reported. - -Note: it is not expected that any assistance information which is not configured to be reported via M-Plane is included in the AID message. - -#### 2.2.2.8 DL report NR PDCP PDU SN with RLC-AM - -##### 2.2.2.8.1 Test Purpose - -The purpose of this test case is to verify that the use of the DL report NR PDCP PDU SN IE with eNB and en-gNB from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.7. - -##### 2.2.2.8.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB: - -- DUTs shall apply RLC-AM specified in NR U-Plane profile specification [3] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 procedural flows and contents - -##### 2.2.2.8.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cell -- Secondary Node Addition (Option 3x) procedure between eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -**2.2.2.8.4 Procedure** - -1. Perform data transfer from the Application Test Server to the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, to meaningfully verify that the user plane transmission operates correctly. -2. Send the DL User Data message which includes the DL report NR PDCP PDU SN IE from en-gNB to eNB. -3. Observe the Protocol Analyzer X2 logs. - -**2.2.2.8.5 Expected Results and Log Observation** - -**2.2.2.8.5.1 Expected Results** - -The use of DL report NR PDCP PDU SN IE is aligned with the requirement specified in Section 4.1.2.7 of NR U-Plane profile specification [3]. - -**2.2.2.8.5.2 Log Observation** - -Logs Recorded in the Protocol Analyzer show that: - -- After beginning of step 2: - - eNB sends en-gNB DDDS including Highest successfully delivered NR PDCP Sequence Number IE with the value same as the value indicated by DL report NR PDCP PDU SN IE. - - eNB sends en-gNB DDDS as soon as possible only when all PDCP PDU SNs up to this DL report NR PDCP PDU have been successfully delivered in-sequence. - -## **2.3 F1 Interoperability Test Cases** - -The following set of F1 IOT cases are defined in this version of the specification. - -| Test Case | Reference to O-RAN NR C-Plane profile [2] | -|--------------------------------------------------|-------------------------------------------| -| Partial Reset (MeNB initiated) | 4.1.4.1 | -| Secondary Node Addition (Option 3x) | 5.1.1 | -| Secondary Node Release (MN initiated, Option 3x) | 5.2.1 | -| Secondary Node Release (SN initiated, Option 3x) | 5.2.2 | -| Secondary Node Change (MN initiated, Option 3x) | 5.3.1 | -| Secondary Node Change (SN initiated, Option 3x) | 5.3.2 | - -| | | -|-------------------------------------------------------------------------------|---------| -| | | -| Inter-Master Node Handover (without SN Change, Option 3x) | 5.4.1 | -| Master Node to eNB Change | 5.5.1 | -| PSCell Change using SRB1 for RRC Reconfiguration – full configuration option | 5.6.15 | -| PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option | 5.6.16 | -| Intra gNB-DU PSCell Change using SRB1 for RRC Reconfiguration | 5.6.17 | -| Inter gNB-DU PSCell Change using SRB3 for RRC Reconfiguration | 5.6.18 | -| Intra gNB-DU PSCell Change using SRB3 for RRC Reconfiguration | 5.6.19 | -| F1 Setup for EN-DC | 4.1.5.1 | -| gNB-DU Configuration Update for EN-DC | 4.1.6.1 | -| gNB-CU Configuration Update for EN-DC | 4.1.7.1 | -| F1 Setup for NR Stand-Alone | 4.2.3.1 | -| gNB-DU Configuration Update for NR Stand-Alone | 4.2.4.1 | -| gNB-CU Configuration Update for NR Stand-Alone | 4.2.5.1 | -| Paging (CN-initiated) | 4.2.6 | -| UE context creation (service request) | 6.1.1 | -| UE context creation (registration request) | 6.1.2 | -| Registration Update without Follow-on request | 6.1.3.2 | -| gNB-DU Initiated UE Context Release | 6.2.1 | -| gNB-CU Initiated UE Context Release | 6.2.2 | -| gNB-CU Initiated UE Context Modification (SCell to be setup/removed) | 6.3.1.1 | -| gNB-CU Initiated UE Context Modification (DRB to be setup) | 6.3.1.2 | -| gNB-CU Initiated UE Context Modification (DRB to be released) | 6.3.1.3 | -| Reset (gNB-DU initiated) for EN-DC | 4.1.2.3 | -| Reset (gNB-CU initiated) for EN-DC | 4.1.2.4 | -| Partial Reset (gNB-DU initiated) for EN-DC | 4.1.4.3 | -| Partial Reset (gNB-CU initiated) for EN-DC | 4.1.4.4 | -| Reset (gNB-CU initiated) for NR Stand-Alone | 4.2.2.3 | -| Reset (gNB-DU initiated) for NR Stand-Alone | 4.2.2.4 | -| Intra gNB-DU, Intra Cell Handover | 6.5.1 | -| Intra gNB-DU, Inter Cell Handover | 6.5.2 | -| Inter gNB-DU Handover | 6.5.3 | - -| | | -|------------------------------------------------------------------------------------------|-----------| -| Intra gNB-DU Handover with L1/L2 Triggered Mobility (LTM) | 6.5.4 | -| Inter RAT HO to LTE | 6.8.1 | -| RRC Connection Re-establishment (Intra gNB-DU) | 6.10.1 | -| RRC Connection Re-establishment (Inter gNB-DU) | 6.10.2 | -| RRC connected to RRC inactive | 6.9.1 | -| RRC inactive to RRC connected, Intra gNB-CU | 6.9.2 | -| RRC inactive to RRC connected, Inter gNB-CU | 6.9.3 | -| S-NG-RAN Node Addition procedure | 7.1.1 | -| Resource Status Reporting Initiation | 4.2.9.1 | -| Resource Status Reporting | 4.2.9.2 | -| Inter-Master Node Handover (With SN Change, Option 3x) | 5.4.2 | -| Allowed Band Combination list update (MN initiated) | 5.6.2 | -| SCG config query (MN initiated) for EN-DC | 5.6.4 | -| gNB-DU initiated UE Context Modification (DRB to be released) | 6.3.2.1 | -| gNB-DU initiated UE Context Modification (DRB to be modified) | 6.3.2.2 | -| Inter RAT HO to NR | 6.8.2 | -| gNB-CU initiated UE Context Modification: DRX cycle activation/deactivation | 6.3.1.4 | -| gNB-CU initiated UE Context Modification: DRB to be modified | 6.3.1.6 | -| M-NG-RAN node initiated SN modification: PDU Session Addition | 7.2.1.1 | -| M-NG-RAN node initiated SN modification: PDU Session Release | 7.2.1.2 | -| M-NG-RAN node initiated SN modification: PDU Session Modification with QoS flow addition | 7.2.1.3.1 | -| M-NG-RAN node initiated SN modification: PDU Session Modification with QoS flow release | 7.2.1.3.2 | -| M-NG-RAN node initiated SN modification: PDU Session Modification with 5QI change | 7.2.1.3.3 | -| M-NG-RAN node initiated SN modification: Security Key change | 7.2.1.4 | -| SCG Configuration Query for NR-DC | 7.2.1.5 | -| Allowed Band Combination list update | 7.2.1.6 | -| PCell Change (Intra-MN) | 7.2.1.7 | -| NG-RAN Node Configuration Update | 4.2.8.1 | -| Write-Replace Warning | 4.2.7 | -| System Information Delivery for NR Stand-Alone | 6.11.1 | -| S-NG-RAN node initiated SN modification with MN involvement: Security Key | 7.2.2.3 | - -| | | -|-----------------------------------------------------------------------------------------------------------------------------------|-----------| -| change | | -| S-NG-RAN node initiated SN modification with MN involvement: PSCell change, Intra gNB-DU | 7.2.2.4 | -| S-NG-RAN node initiated SN modification with MN involvement: PSCell change, Inter gNB-DU | 7.2.2.5 | -| S-NG-RAN node initiated SN modification with MN involvement: UL Configuration Update | 7.2.2.6 | -| S-NG-RAN node initiated SN modification with MN involvement: Measurement Gap Coordination Procedure (SN initiated) | 7.2.2.7 | -| S-NG-RAN node initiated SN modification with MN involvement: CellGroupConfig change (SN-DU initiated) | 7.2.2.8 | -| Master Node to gNB Change | 7.6.1 | -| Inter-Master Node Handover Without SN Change for NR-DC | 7.7.1 | -| Inter-Master Node Handover with SN Change for NR-DC | 7.7.2 | -| SN Initiated SN Change | 7.8.1 | -| MN Initiated SN Change | 7.8.2 | -| Full Reconfiguration (SN initiated) | 5.6.22 | -| Change of QCI (MN initiated) | 5.6.23 | -| Measurement ID Coordination (MN initiated) | 5.6.24 | -| Security Key change (MN initiated) for EN-DC | 5.6.5 | -| Measurement Gap Coordination procedure (MN initiated) | 5.6.6 | -| Measurement Gap Coordination for per FR1 or per UE gap Procedure (SN initiated) | 5.6.7 | -| Measurement Gap Coordination for per FR2 gap (with MN involvement) Procedure (SN initiated) | 5.6.8 | -| Measurement Gap Coordination for per FR2 gap (without MN involvement) Procedure (SN initiated) | 5.6.8a | -| UL Configuration Update Procedure (SN initiated) | 5.6.9 | -| Addition of SN terminated split bearer (MN initiated) | 5.6.10 | -| Removal of SN terminated split bearer (MN initiated) | 5.6.11 | -| RRC connection re-establishment (inter gNB-CU) | 6.10.4 | -| gNB-CU initiated UE Context Modification (UE AMBR (for UL) modification) | 6.3.1.7 | -| Inter gNB Handover for SA | 6.4.1 | -| S-NG-RAN node Initiated SN modification without MN involvement: SRB3 not supported: SN Modification – SCell(s) Addition / Release | 7.2.3.1.1 | - -| | | -|-----------------------------------------------------------------------------------------------------------------------|-----------| -| S-NG-RAN node Initiated SN modification without MN involvement: SRB3 supported: Intra gNB-DU PSCell Change using SRB3 | 7.2.3.2.1 | -| S-NG-RAN node initiated SN modification without MN involvement: SRB3 supported: Inter gNB-DU PSCell Change using SRB3 | 7.2.3.2.2 | -| M-NG-RAN node initiated S-NG-RAN Node Release without keeping UE | 7.3.1 | -| M-NG-RAN node initiated S-NG-RAN Node Release with keeping UE | 7.3.2 | -| S-NG-RAN node initiated S-NG-RAN Node Release | 7.3.3 | -| PDU Session Establishment | 6.3.3.1 | -| New QoS Flow with Explicit NAS Signalling | 6.3.3.2 | -| Measurement Gap Coordination Procedure (MN initiated) | 7.2.1.8 | -| PCell change (Intra MN) (MN initiated) | 5.6.1 | -| DRB ID change/Security Key change (SN initiated) | 5.6.21 | -| Measurement ID Coordination (SN initiated) | 5.6.25 | -| Release of QoS Flow with Explicit Signalling | 6.3.3.3 | -| PDU session establishment after signalling-only connection | 6.12 | - -**Table 2-5: IOT Test Cases for F1 implemented in accordance with the NR C-Plane [2] profile** - -| Test Case | Reference to O-RAN NR U-Plane profile [3] | -|-----------------------------------------------------------------------------------------|-------------------------------------------| -| Node behaviour of the corresponding node for EN-DC with RLC-AM and/or RLC-UM | 4.1.1.1 | -| Node behaviour of the corresponding node for SA with RLC-AM and/or RLC-UM | 4.1.1.1 | -| Node behaviour of the corresponding node for NR-DC with RLC-AM and/or RLC-UM | 4.1.1.1 | -| General for Elements for the NR user plane protocol for EN-DC with RLC-AM and/or RLC-UM | 4.1.2.1 | -| General for Elements for the NR user plane protocol for SA with RLC-AM and/or RLC-UM | 4.1.2.1 | -| General for Elements for the NR user plane protocol for NR-DC with RLC-AM and/or RLC-UM | 4.1.2.1 | -| Report Polling for EN-DC with RLC-AM and/or RLC-UM | 4.1.2.2 | -| Report Polling for SA with RLC-AM and/or RLC-UM | 4.1.2.2 | -| Report Polling for NR-DC with RLC-AM and/or RLC-UM | 4.1.2.2 | -| Buffer discard indication for EN-DC with RLC-AM and/or RLC-UM | 4.1.2.3 | -| Buffer discard indication for SA with RLC-AM and/or RLC-UM | 4.1.2.3 | -| Buffer discard indication for NR-DC with RLC-AM and/or RLC-UM | 4.1.2.3 | - -| | | -|---------------------------------------------------------------------------|---------| -| User data existence flag for EN-DC with RLC-AM and/or RLC-UM | 4.1.2.4 | -| User data existence flag for SA with RLC-AM and/or RLC-UM | 4.1.2.4 | -| User data existence flag for NR-DC with RLC-AM and/or RLC-UM | 4.1.2.4 | -| Assistance Information Report polling for EN-DC with RLC-AM and/or RLC-UM | 4.1.2.5 | -| Assistance Information Report polling for SA with RLC-AM and/or RLC-UM | 4.1.2.5 | -| Assistance Information Report polling for NR-DC with RLC-AM and/or RLC-UM | 4.1.2.5 | -| Radio quality assistance information for EN-DC with RLC-AM and/or RLC-UM | 4.1.2.6 | -| Radio quality assistance information for SA with RLC-AM and/or RLC-UM | 4.1.2.6 | -| Radio quality assistance information for NR-DC with RLC-AM and/or RLC-UM | 4.1.2.6 | -| DL report NR PDCP PDU SN for F1 | 4.1.2.7 | -| DL report NR PDCP PDU SN for SA with RLC-AM | 4.1.2.7 | -| DL report NR PDCP PDU SN for NR-DC with RLC-AM | 4.1.2.7 | - -**Table 2-5b: IOT Test Cases for F1 implemented in accordance with the NR U-Plane [3] profile** - -The initial test conditions which are common to all F1 test cases are listed below: - -Initial test conditions for scenarios with an EPC: - -- gNB-CU(s) and gNB-DU(s) are running in normal operating state -- gNB-CU(s) and gNB-DU(s) are physically and logically connected -- Core or Core emulator (EPC with EN-DC capabilities) is physically connected to the en-gNB(s) -- S1 Setup procedure specified in 3GPP TS 36.413 [7] has been completed with the Core or Core emulator -- EN-DC X2 setup procedure has been successfully completed between the eNB or eNB emulator and the en-gNB according to the NR C-Plane profile specification [2] -- Protocol Analyzer is physically connected to the X2, F1 and S1-U link(s) - -Initial test conditions for scenarios with a 5GC: - -- gNB-CU(s) and gNB-DU(s) are running in normal operating state -- gNB-CU(s) and gNB-DU(s) are physically and logically connected -- Core or Core emulator (5GC capabilities) is physically connected to the gNB(s) -- NG Setup procedure specified in 3GPP TS 38.413 [15] has been completed with the Core or Core emulator -- Protocol Analyzer is physically connected to the F1 and NG-U link(s) - -Test case specific deviations of the initial test conditions will be specified in each of the test cases. - -## 2.3.1 F1 C-Plane IOT Test Cases - -### 2.3.1.1 Partial Reset (MeNB initiated) - -#### 2.3.1.1.1 Test Purpose - -The purpose of this test case is to verify that the MeNB initiated Partial Reset Procedure leads to a correct interworking between gNB-CU and gNB-DU from different vendors using Reset procedure; conforming to the NR C-Plane profile specification [2] Section 4.1.4.1. This test case is on top of the X2 part of the MeNB initiated Partial Reset Procedure described in Section 2.2.1.5. - -#### 2.3.1.1.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator: used to perform MeNB initiated Partial Reset procedure -- Test UEs or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol, and to support Path Switch, Bearer Modification and Secondary RAT Data Usage Report -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and content - -#### 2.3.1.1.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup Procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Multiple Test UEs or emulated UEs have registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UEs or emulated UEs are within the coverage area of the SN cell, and Secondary Node Addition (eg, SN terminated split bearer) procedure has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -#### 2.3.1.1.4 Procedure - -1. Perform the MeNB initiated Partial Reset Procedure over X2 Step 1 described in Section 2.2.1.5.4. - -Note: the intention of this step is to perform not only the X2 part of the MeNB initiated Partial Reset Procedure but also trigger the F1 signaling, that is Reset Procedure over F1 with gNB-CU and gNB-DU. - -2. Observe the Protocol Analyzer X2 and F1 link logs. - -### 2.3.1.1.5 Expected Results and Log Observation - -#### 2.3.1.1.5.1 Expected Results - -The MeNB initiated Partial Reset Procedure is successfully completed. - -The part of the UE contexts affected by the MeNB initiated Partial Reset procedure is successfully released in the gNB-CU and data transfer between the Application Test Server and the Test UE or UE emulator has ended. - -#### 2.3.1.1.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.1.4.1.3/4.1.4.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “RESET ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -### 2.3.1.2 Secondary Node Addition (Option 3x) - -#### 2.3.1.2.1 Test Purpose - -The purpose of this test case is to verify that a Secondary Node Addition (Option 3x) procedure received by gNB-CU leads to correct interworking between gNB-CU and gNB-DU from different vendors using on F1 UE Context Setup procedures; conforming to the NR C-Plane profile specification [2] Section 5.1.1. This test case is on top of the X2 part of the Secondary Node Addition (Option 3x) procedure described in Section 2.2.1.7. - -#### 2.3.1.2.2 Minimum Requirements - -The minimum requirements described in Section 2.2.1.13.2. - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.1.1 of the NR C-Plane profile specification [2] -- The coverage of eNB cell (MN) and en-gNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Secondary Node Addition procedure -- eNB or eNB emulator: used to perform Secondary Node Addition (Option 3x) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and contents and S1-U UP contents - -#### 2.3.1.2.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary node has not yet been added to the Test UE or UE emulator - -#### 2.3.1.2.4 Procedure - -1. Perform data transfer in both directions as described in step 1 (except for Note) in Section 2.2.1.7.4 -2. Perform the Secondary Node Addition (Option 3x) Procedure described in NR C-Plane profile specification [2] Section 5.1.1.3 -3. Stop data transfer as described in step 3 in Section 2.2.1.7.4 -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.7.4 -5. Observe the Protocol Analyzer S1, X2 and F1 logs and Test UE or UE emulator logs - -#### 2.3.1.2.5 Expected Results and Log Observation - -##### 2.3.1.2.5.1 Expected Results - -The UE Context Setup procedure over F1 is successfully completed. - -The Secondary Node Addition (Option 3x) Procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.2.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.1.1.3/5.1.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4 in Section 2.3.1.2.4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4 in Section 2.3.1.2.4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -#### 2.3.1.3 Secondary Node Release (MN initiated, Option 3x) - -##### 2.3.1.3.1 Test Purpose - -The purpose of this test case is to verify that the UE Context Modification and UE Context Release Procedure with en-gNB-CU and en-gNB-DU from different vendors, triggered with MN (eNB) initiated SgNB Release procedure, can be - -successfully completed, conforming to the NR C-Plane profile specification [2] Section 5.2.1. This test case complements the X2-only test case addressing the corresponding F1 aspects. - -### 2.3.1.3.2 Minimum Requirements - -DUTs: Single en-gNB-CU and single en-gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.2.1 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Secondary Node Release (MN initiated, Option 3x) procedure -- eNB or eNB emulator: used to perform Secondary Node Release (MN initiated, Option 3x) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe F1 and X2 procedural flows and content - -### 2.3.1.3.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the en-gNB-CU and en-gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.3.1.3.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates which are high enough for the en-gNB to start buffering user plane downlink data prior to the release of the en-gNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT and the NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform Secondary Node Release Procedure from MN (eNB) side. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Provoke a Radio Link Failure in SCG so MN receives SCG Failure Information NR message from the UE. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the en-gNB cell. In this specific case, the en-gNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger the Radio link failure scenario. -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Secondary Node Release Procedure in both directions between the Test UE or UE emulator and the Application Test Server. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer F1, S1 and X2 logs and Test UE or UE emulator logs. - -### **2.3.1.3.5 Expected Results and Log Observation** - -#### **2.3.1.3.5.1 Expected Results** - -The F1 UE Context Modification and UE Context Release Procedure are successfully completed. - -The Secondary Node Release procedure is successfully completed. - -#### **2.3.1.3.5.2 Log Observation** - -F1 and X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.2.1.3/5.2.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 and X2 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 and X2 logs is correctly received by the Test UE or UE emulator via NR respectively NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 and X2 logs is correctly received by the Test UE or UE emulator via NR respectively LTE RAT - -### **2.3.1.4 Secondary Node Release (SN initiated, Option 3x)** - -#### **2.3.1.4.1 Test Purpose** - -The purpose of this test case is to verify that the UE Context Modification and UE Context Release Procedure with en-gNB-CU and en-gNB-DU from different vendors, triggered with SN (en-gNB) initiated SgNB Release procedure, can - -be successfully completed, conforming to the NR C-Plane profile specification [2] Section 5.2.2. This test case complements the X2-only test case addressing the corresponding F1 aspects. - -#### 2.3.1.4.2 Minimum Requirements - -DUTs: Single en-gNB-CU and single en-gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.2.2 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Secondary Node Release (SN initiated, Option 3x) procedure -- eNB or eNB emulator: used to perform Secondary Node Release (SN initiated, Option 3x) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe F1 and X2 procedural flows and content - -#### 2.3.1.4.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the en-gNB-CU and en-gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- F1 UE Context Setup procedure between en-gNB-CU and en-gNB-DU, triggered together with Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.3.1.4.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates which are high enough for the en-gNB to start buffering user plane downlink data prior to the release of the en-gNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT and the NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform Secondary Node Release Procedure from SN (en-gNB) side. - -A few examples of how this procedure can be performed (or triggered) are listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Block NR cell in en-gNB. One method is to use O&M command in the en-gNB to block the NR cell. - -- b. Provoke conditions in a way that the SN detects that the RLC exceeds its maximum downlink retransmission. One method is to vary the channel conditions between the SN and the Test UE or UE emulator as such the emulated interferences can be significant enough to increase RLC retransmissions to exceed the maximum downlink retransmission level. -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Secondary Node Release Procedure in both directions between the Test UE or UE emulator and the Application Test Server. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the LTE RAT, which is calculated based on 3GPP TS 36.211 [9] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer F1, S1 and X2 logs and Test UE or UE emulator logs. - -#### 2.3.1.4.5 Expected Results and Log Observation - -##### 2.3.1.4.5.1 Expected Results - -The F1 UE Context Modification and UE Context Release Procedure are successfully completed. - -The Secondary Node Release procedure is successfully completed. - -##### 2.3.1.4.5.2 Log Observation - -F1 and X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.2.2.1/5.2.2.2. - -If any of the following listed IEs is observed in the X2 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 and X2 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 and X2 logs is correctly received by the Test UE or UE emulator via NR respectively LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 and X2 logs is correctly received by the Test UE or UE emulator via NR respectively LTE RAT - -#### 2.3.1.5 Secondary Node Change (MN initiated, Option 3x) - -##### 2.3.1.5.1 Test Purpose - -The purpose of this test case is to verify that the F1 UE Context Setup, UE Context Modification and UE Context Release Procedure with en-gNB-CU and en-gNB-DU from different vendors, triggered with MN (eNB) initiated SgNB Change procedure, can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 5.3.1.4. This test case complements the X2-only test case addressing the corresponding F1 aspects. - -### 2.3.1.5.2 Minimum Requirements - -DUTs: Two en-gNB-CU (S-SN-CU, T-SN-CU) and two en-gNB-DU (S-SN-DU, T-SN-DU): - -- DUTs shall apply the parameter condition specified in 5.3.1 of the NR C-Plane profile specification [2] -- coverage of eNB cell (MN), Source en-gNB cell (S-SN) and Target en-gNB cell (T-SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Secondary Node Change procedure (MN initiated, Option 3x) -- eNB or eNB emulator: used to perform Secondary Node Change procedure (MN initiated, Option 3x) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both X2 and F1 links procedural flows and content, S1-U UP content - -### 2.3.1.5.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNBs according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the en-gNB-CUs and en-gNB-DUs according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the eNB cell and S-SN cell -- F1 UE Context Setup procedure between S-SN-CU and S-SN-DU, triggered with Secondary Node Addition (Option 3x) procedure between the eNB and S-SN has been successfully completed according to NR C-Plane profile specification [2] -- Secondary Node is Source en-gNB cell (S-SN) at the start of this procedure -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.3.1.5.4 Procedure - -1. Perform data transfer in the both directions between the Application Test Server and the Test UE or UE emulator. -2. Perform Secondary Node Change Procedure from MN (eNB) side. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the Source en-gNB cell (S-SN) and the Target en-gNB cell (T-SN) simultaneously. In this specific case, the Source en-gNB cell (S-SN) can start off with low attenuation - -applied which is subsequently increased. At the same time, the Target en-gNB cell (T-SN) can start off with high attenuation applied which is subsequently lowered to a level which can trigger the Secondary Node Change procedure. - -3. Stop the data transfer in the downlink direction between the Application Test Server and the Test UE or UE emulator. -4. Perform data transfer in the uplink direction between the Test UE or UE emulator and the Application Test Server. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Secondary Node Change Procedure in both directions between the Test UE or UE emulator and the Application Test Server. - -One method to stimulate the Split Bearer(s) usage of both the LTE and NR RATs is to transfer user plane data at data rates which are high enough for the en-gNB to start distributing user plane data to the eNB via the X2 interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer F1, S1 and X2 logs and Test UE or UE emulator logs. - -### 2.3.1.5.5 Expected Results and Log Observation - -#### 2.3.1.5.5.1 Expected Results - -The F1 UE Context Setup, UE Context Modification and UE Context Release Procedure are successfully completed. - -The Secondary Node Change procedure is successfully completed. - -Data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.5.5.2 Log Observation - -F1 and X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.3.1.3/5.3.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 and X2 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 and X2 logs is correctly received by the Test UE or UE emulator via NR respectively LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 and X2 logs is correctly received by the Test UE or UE emulator via NR respectively LTE RAT - -### 2.3.1.6 Secondary Node Change (SN initiated, Option 3x) - -#### 2.3.1.6.1 Test Purpose - -The purpose of this test case is to verify that the F1 UE Context Setup, UE Context Modification and UE Context Release Procedure with en-gNB-CU and en-gNB-DU from different vendors, triggered with SN (en-gNB) initiated SgNB Change procedure, can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 5.3.2.4. This test case complements the X2-only test case addressing the corresponding F1 aspects. - -#### 2.3.1.6.2 Minimum Requirements - -DUTs: Two en-gNB-CU (S-SN-CU, T-SN-CU) and two en-gNB-DU (S-SN-CU, T-SN-CU): - -- DUTs shall apply the parameter condition specified in 5.3.2 of the NR C-Plane profile specification [2] -- The coverage of eNB cell (MN), Source en-gNB cell (S-SN) and Target en-gNB cell (T-SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Secondary Node Change procedure (MN initiated, Option 3x) -- eNB or eNB emulator: used to perform Secondary Node Change procedure (SN initiated, Option 3x) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both X2 and F1 links procedural flows and content, S1-U UP content - -#### 2.3.1.6.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 Setup procedure has been successfully completed between the eNB and en-gNBs according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the en-gNB-CUs and en-gNB-DUs according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the eNB cell and S-SN cell -- F1 UE Context Setup procedure between S-SN-CU and S-SN-DU, triggered with Secondary Node Addition (Option 3x) procedure between the eNB and S-SN has been successfully completed according to NR C-Plane profile specification [2] -- Secondary Node is Source en-gNB cell (S-SN) at the start of this procedure -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -#### 2.3.1.6.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. -2. Perform Secondary Node Change Procedure from Source en-gNB cell (S-SN) and Target en-gNB cell (T-SN). - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Move the Test UE or UE emulator from the coverage area of Source en-gNB cell (S-SN) towards Target en-gNB cell (T-SN). One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the Source en-gNB cell (S-SN) and the Target en-gNB cell (T-SN) simultaneously. In this specific case, the Source en-gNB cell (S-SN) can start off with low attenuation applied which is subsequently increased. At the same time, the Target en-gNB cell (T-SN) can start off with high attenuation applied which is subsequently lowered to a level which can trigger the SN change procedure from S-SN to T-SN. Observe that data transfer from the Application Test Server to the Test UE or UE emulator is ongoing after Secondary Node Change. -3. Stop the data transfer in the downlink direction between the Application Test Server and the Test UE or UE emulator. - 4. Perform data transfer in the uplink direction between the Test UE or UE emulator and the Application Test Server. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Secondary Node Change Procedure in both directions between the Test UE or UE emulator and the Application Test Server. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer F1, S1 and X2 logs and Test UE or UE emulator logs. - -### 2.3.1.6.5 Expected Results and Log Observation - -#### 2.3.1.6.5.1 Expected Results - -The F1 UE Context Setup, UE Context Modification and UE Context Release Procedure are successfully completed. - -The Secondary Node Change procedure is successfully completed. - -Data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.6.5.2 Log Observation - -F1 and X2 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.3.2.3/5.3.2.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 and X2 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 and X2 logs is correctly received by the Test UE or UE emulator via NR respectively LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - -- o All U-Plane data recorded in the F1 and X2 logs is correctly received by the Test UE or UE emulator via NR respectively LTE RAT - -### 2.3.1.7 Inter-Master Node Handover (without SN Change, Option 3x) - -#### 2.3.1.7.1 Test Purpose - -The purpose of this test case is to verify that an Inter-Master Node Handover (without SN Change, Option 3x) procedure received by gNB-CU leads to correct interworking between gNB-CU and gNB-DU from different vendors using on F1 UE Context Modification procedures; conforming to the NR C-Plane profile specification [2] Section 5.4.1. This test case is on top of the X2 part of the Inter-Master Node Handover (without SN Change, Option 3x) procedure described in Section 2.2.1.12. - -#### 2.3.1.7.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.4.1 of the NR C-Plane profile specification [2] -- The coverage of Source eNB cell and en-gNB cell overlap -- The coverage of Target eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform Inter-Master Node Handover (without SN Change, Option 3x) procedure -- eNB or eNB emulator: used to perform Inter-Master Node Handover (without SN Change, Option 3x) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and contents and S1-U UP contents - -#### 2.3.1.7.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- X2 setup procedure between the source eNB and target eNB specified in 3GPP TS 36.423 [12] has been successfully completed -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the Source eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.3.1.7.4 Procedure - -1. Perform data transfer in the both directions as described in step 1 (except for Note) in Section 2.2.1.12.4 -2. Perform the X2 part of Inter-Master Node Handover (without SN Change, Option 3x) procedures as described in NR C-Plane profile specification [2] Section 5.4.1.3 -3. Stop data transfer as described in step 3 in Section 2.2.1.12.4 -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.12.4. -5. Observe the Protocol Analyzer S1, X2 and F1 logs and Test UE or UE emulator logs. - -#### 2.3.1.7.5 Expected Results and Log Observation - -##### 2.3.1.7.5.1 Expected Results - -The UE Context Modification procedure over F1 is successfully completed. - -The Inter-Master Node Handover (without SN Change, Option 3x) procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.7.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.4.1.3/5.4.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4 in Section 2.3.1.7.4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4 in Section 2.3.1.7.4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -#### 2.3.1.8 Master Node to eNB Change - -##### 2.3.1.8.1 Test Purpose - -The purpose of this test case is to verify that the Master Node to eNB Change Procedure leads to a correct interworking between gNB-CU and gNB-DU from different vendors using UE Context Modification and UE Context Release procedure, conforming the NR C-Plane profile specification [2] Section 5.5.1. This test case is on top of the X2 part of the Master Node to eNB Change Procedure described in Section 2.2.1.13. - -##### 2.3.1.8.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.5.1 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario. - -- eNB or eNB emulator: used to perform Master Node to eNB Change procedure -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Master Node to eNB Change procedure -- Target eNB or Target eNB emulator: used to perform Master Node to eNB Change procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol, and to support Path Switch, Bearer Modification and Secondary RAT Data Usage Report -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and content, and S1-U UP content - -### 2.3.1.8.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- X2 setup procedure between the source eNB and target eNB or target eNB emulator specified in 3GPP TS 36.423 [12] has been successfully completed -- F1 setup Procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the Source eNB cell (S-MN) and SN cell -- Secondary Node Addition (Option 3x) procedure between the Source eNB (S-MN) and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Then SCG configuration query has been completed if needed - -### 2.3.1.8.4 Procedure - -1. Perform the Master Node to eNB Change Procedure Steps 1 – 2 described in Section 2.2.1.13.4. - -Note: the intention of this step is to perform not only the X2 part of the Master Node to eNB Change Procedure but also trigger to perform the F1 signaling, that is UE Context Modification Procedure and the UE Context Release Procedure with gNB-CU and gNB-DU. - -2. Perform the X2 part of Master Node to eNB Change Procedure Steps 3 – 4 described in Section 2.2.1.13.4. -3. Observe the Protocol Analyzer X2 and F1 link logs, and Test UE or UE emulator logs. - -### 2.3.1.8.5 Expected Results and Log Observation - -#### 2.3.1.8.5.1 Expected Results - -The UE Context Modification Procedure and the UE Context Release Procedure over F1 are successfully completed. - -The Master Node to eNB Change Procedure over F1 is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -### **2.3.1.8.5.2 Log Observation** - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.5.1.3/5.5.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in Step 1 and after Step 2 and in Step 4 in Section 2.2.1.13.4: - - All U-Plane data recorded in the F1 logs in Step 1 and after Step 2 is correctly received by the Test UE or emulated UE via NR RAT, no U-Plane data recorded in the F1 logs in Step 4 -- Regarding the uplink U-Plane data generated in Step 1 and after Step 2 and in Step 4 in Section 2.2.1.13.4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT in Step 1 and after Step 2 is recorded in the F1 logs, no U-Plane data recorded in the F1 logs in Step 4 - -### **2.3.1.9 PSCell Change using SRB1 for RRC Reconfiguration – full configuration option (Inter gNB-DU scenario)** - -#### **2.3.1.9.1 Test Purpose** - -The purpose of this test case is to verify that a PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option procedure received by gNB-CU leads to correct interworking between gNB-CU and gNB-DU from different vendors using F1 UE Context Setup procedure, F1 UE Context Modification procedure, and F1 UE Context Release procedure; conforming to the NR C-Plane profile specification [2] Section 5.6.15. This test case is on top of the X2 part of the PSCell Change using SRB1 for RRC Reconfiguration – full configuration option procedure described in Section 2.2.1.15. - -#### **2.3.1.9.2 Minimum Requirements** - -DUTs: Single gNB-CU and two gNB-DUs (Source gNB-DU, Target gNB-DU): - -- DUTs shall apply the parameter condition specified in 5.6.15 of the NR C-Plane profile specification [2] -- en-gNB has at least 2 Cells configured and in operation - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform PSCell Change using SRB1 for RRC Reconfiguration – full configuration option (Inter gNB-DU scenario) procedure -- eNB or eNB emulator: used to perform PSCell Change using SRB1 for RRC Reconfiguration – full configuration option (Inter gNB-DU scenario) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and contents and S1-U UP contents - -### 2.3.1.9.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the eNB cell and the en-gNB cells - -### 2.3.1.9.4 Procedure - -1. Perform data transfer in both downlinks directions as described in step 1 (except for Note) in Section 2.2.1.15.4 -2. Perform the PSCell Change using SRB1 for RRC Reconfiguration – full configuration option procedures described in NR C-Plane profile specification [2] Section 5.6.15.3 -3. Stop data transfer as described in step 3 in Section 2.2.1.15.4 -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.15.4 -5. Observe the Protocol Analyzer S1, X2 and F1 logs and Test UE or UE emulator logs - -### 2.3.1.9.5 Expected Results and Log Observation - -#### 2.3.1.9.5.1 Expected Results - -The UL RRC Message Transfer is successfully transmitted. - -The UE Context Setup, UE Context Modification and UE Context Release procedure over F1 is successfully completed. - -The PSCell Change using SRB1 for RRC Reconfiguration – full configuration option procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.9.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.15.3/5.6.15.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and 4 in Section 2.3.1.9.4: - -- o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4 in Section 2.3.1.9.4: - - o All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.10 PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option (Inter gNB-DU scenario) - -#### 2.3.1.10.1 Test Purpose - -The purpose of this test case is to verify that a PSCell Change, using SRB1 for RRC Reconfiguration – delta configuration option procedure, received by gNB-CU leads to correct interworking between gNB-CU and gNB-DU from different vendors using F1 UE Context Setup procedure, F1 UE Context Modification procedure and F1 UE Context Release procedure; conforming to the NR C-Plane profile specification [2] Section 5.6.16. This test case is on top of the X2 part of the PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option procedure described in Section 2.2.1.16. - -#### 2.3.1.10.2 Minimum Requirements - -DUTs: Single gNB-CU and two gNB-DUs (Source gNB-DU, Target gNB-DU): - -- DUTs shall apply the parameter condition specified in 5.6.16 of the NR C-Plane profile specification [2] -- en-gNB has at least 2 cells configured and in operation - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform PSCell Change using SRB1 for RRC Reconfiguration - delta config option (Inter gNB-DU scenario) procedure -- eNB or eNB emulator: used to perform PSCell Change using SRB1 for RRC Reconfiguration - delta config option (Inter gNB-DU scenario) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and contents and S1-U UP contents - -#### 2.3.1.10.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions is applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -- Test UE or UE emulator is within the coverage area of the eNB cell and the en-gNB cells - -#### 2.3.1.10.4 Procedure - -1. Perform data transfer in both directions as described in step 1 (except for Note) in Section 2.2.1.16.4 -2. Perform the PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option procedures described in NR C-Plane profile specification [2] Section 5.6.16.3 -3. Stop data transfer as described in step 3 in Section 2.2.1.16.4 -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.16.4. -5. Observe the Protocol Analyzer S1, X2 and F1 logs and Test UE or UE emulator logs. - -#### 2.3.1.10.5 Expected Results and Log Observation - -##### 2.3.1.10.5.1 Expected Results - -The UL RRC Message Transfer is successfully transmitted. - -The UE Context Setup, UE Context Modification and UE Context Release procedure over F1 is successfully completed. - -The PSCell Change using SRB1 for RRC Reconfiguration – delta configuration option procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.10.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.16.3/5.6.16.4 - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4 in Section 2.3.1.10.4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4 in Section 2.3.1.10.4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -#### 2.3.1.11 Intra gNB-DU PSCell Change using SRB1 for RRC Reconfiguration - -##### 2.3.1.11.1 Test Purpose - -The purpose of this test case is to verify that an Intra gNB-DU PSCell Change using SRB1 for RRC Reconfiguration procedure received by gNB-CU leads to correct interworking between gNB-CU and gNB-DU from different vendors using F1 UE Context Modification procedures; conforming to the NR C-Plane profile specification [2] Section 5.6.17. - -##### 2.3.1.11.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.17 of NR C-Plane profile specification [2] -- Single gNB-CU and single gNB-DU have at least 2 Cells configured and in operation - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Intra gNB-DU PSCell Change using SRB1 for RRC Reconfiguration procedure -- eNB or eNB emulator: used to perform Intra gNB-DU PSCell Change using SRB1 for RRC Reconfiguration procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and content - -### 2.3.1.11.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 Setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the eNB cell and the en-gNB cells - -### 2.3.1.11.4 Procedure - -1. Perform data transfer in both directions as described in step 1 (except for Note) in Section 2.2.1.15.4 -2. Perform the Intra gNB-DU PSCell Change using SRB1 for RRC Reconfiguration procedures described NR C-Plane profile specification [2] Section 5.6.17.1 -3. Stop data transfer as described in step 3 in Section 2.2.1.15.4 -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.15.4 -5. Observe the Protocol Analyzer S1, X2 and F1 logs and Test UE or UE emulator logs - -### 2.3.1.11.5 Expected Results and Log Observation - -#### 2.3.1.11.5.1 Expected Results - -The UL RRC Message Transfer is successfully transmitted. - -The UE Context Modification procedure over F1 is successfully completed. - -The Intra gNB-DU PSCell Change using SRB1 for RRC Reconfiguration Procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -### 2.3.1.11.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.17.3/5.6.17.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4 in Section 2.3.1.11.4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4 in Section 2.3.1.11.4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.12 F1 Setup for EN-DC - -#### 2.3.1.12.1 Test Purpose - -The purpose of this test case is to verify that the F1 Setup procedure between gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.1.5.1. - -#### 2.3.1.12.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 4.1.5.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol. -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -#### 2.3.1.12.3 Initial Conditions - -- A SCTP association is successfully established between the two SCTP endpoints (SCTP initiation procedure has taken place before or is taking place with execution of this test case) - -#### 2.3.1.12.4 Procedure - -1. Initiate the F1 Setup procedure in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. O&M command in gNB-DU to enable F1 interface -2. This step is executed optionally. The gNB-DU initiates gNB-DU Configuration Update procedure for cell activation if gNB-CU requests gNB-DU to activate cells via F1 SETUP RESPONSE message in order to test OPT1 procedure specified in NR C-Plane profile specification [2] Section 4.1.5.1.1. In this step, all cells or a part of cells requested are activated. If a part of cells requested are activated in this step, the rest cells may be activated by OPT 2 procedure specified in NR C-Plane profile specification [2] Section 4.1.5.1.1 -3. This step is executed optionally. The gNB-CU initiates gNB-CU Configuration Update procedure for cell activation if gNB-CU requests gNB-DU to activate cells which have been reported by F1 SETUP REQUEST - -message sometime after it sent F1 SETUP RESPONSE message in order to test OPT2 procedure specified in NR C-Plane profile specification [2] Section 4.1.5.1.1. Since this step can be independently done from step 2, the cells to be activated in this step may be different from those of step 2. - -4. Observe the Protocol Analyzer F1 link logs - -### 2.3.1.12.5 Expected Results and Log Observation - -#### 2.3.1.12.5.1 Expected Results - -The F1 Setup procedure is successfully completed. - -The gNB-DU Configuration Update procedure is successfully completed if gNB-CU requests gNB-DU to activate cells via F1 SETUP RESPONSE message. - -The gNB-CU Configuration Update procedure is successfully completed if gNB-CU requests gNB-DU to activate cells which have been reported by F1 SETUP REQUEST message sometime after it sent F1 SETUP RESPONSE message. - -#### 2.3.1.12.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 4.1.5.1.1/4.1.5.1.2. - -### 2.3.1.13 gNB-DU Configuration Update for EN-DC - -#### 2.3.1.13.1 Test Purpose - -The purpose of this test case is to verify that the gNB-DU Configuration Update procedure between gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.1.6.1. - -#### 2.3.1.13.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 4.1.6.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol. -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -#### 2.3.1.13.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] - -#### 2.3.1.13.4 Procedure - -1. Perform the gNB-DU Configuration Update procedure to add cells in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate recovery from cell failure. One method is to use O&M command in the gNB-DU in order to make the gNB-DU's cell recover after the transition to its cell failure status. - -2. Perform the gNB-DU Configuration Update procedure to delete cells in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell failure. One method is to use O&M command in the gNB-DU in order to make gNB-DU's cell failure status. - -3. Perform the gNB-DU Configuration Update procedure to modify cells in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation, then change NR PCI information of the deactivated cells. One method is to use O&M command in the gNB-DU in order to deactivate cells and change the NR PCI. - -4. Perform the gNB-DU Configuration Update procedure to activate cells in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell activation. One method is to use O&M command in the gNB-DU in order to activate cells. - -The cell activation is successfully completed by gNB-DU Configuration Update procedure in this step. If the gNB-CU requests the gNB-DU to activate cells via GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, then the gNB-DU will trigger additional GNB-DU CONFIGURATION UPDATE procedure to inform the Service Status for activated cells (OPT1) specified in NR C-Plane profile specification [2] Section 4.1.6.1.1. - -5. Perform the gNB-DU Configuration Update procedure to deactivate cells in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation. One method is to use O&M command in the gNB-DU in order to deactivate cells. - -6. Perform the gNB-DU Configuration Update procedure to inform the Service Status in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate the Service Status of the cell from "In-Service" to "Out-Of-Service". One method is to use O&M command in the gNB-DU in order to change the Service Status from "In-Service" to "Out-Of-Service". - -7. Observe the Protocol Analyzer F1 link logs. - -### 2.3.1.13.5 Expected Results and Log Observation - -#### 2.3.1.13.5.1 Expected Results - -The cell addition is successfully completed by gNB-DU Configuration Update procedure in step 1. - -The cell deletion is successfully completed by gNB-DU Configuration Update procedure in step 2. - -The cell modification is successfully completed by gNB-DU Configuration Update procedure in step 3. - -The cell activation is successfully completed by gNB-DU Configuration Update procedure in step 4. Informing the service status for additionally activated cells may be successfully completed by gNB-DU Configuration Update procedure in this step. - -The cell deactivation is successfully completed by gNB-DU Configuration Update procedure in step 5. - -Informing the service status is successfully completed by gNB-DU Configuration Update procedure in step 6. - -#### 2.3.1.13.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 4.1.6.1.1/4.1.6.1.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE” - -the test result shall be determined to be *‘successful with remarks’*. - -### 2.3.1.14 gNB-CU Configuration Update for EN-DC - -#### 2.3.1.14.1 Test Purpose - -The purpose of this test case is to verify that the gNB-CU Configuration Update procedure between gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.1.7.1. - -#### 2.3.1.14.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 4.1.7.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol. -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -#### 2.3.1.14.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] - -#### 2.3.1.14.4 Procedure - -1. Perform the gNB-CU Configuration Update procedure to activate cells in gNB-DU. - - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - - - a. Stimulate cell activation. One method is to use O&M command in the gNB-CU in order to activate cells. -2. Perform the gNB-CU Configuration Update procedure to deactivate cells in gNB-DU. - - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - - - a. Stimulate cell deactivation. One method is to use O&M command in the gNB-CU in order to deactivate cells. -3. Perform the gNB-CU Configuration Update procedure to add TNL association in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate TNL association addition. One method is to use O&M command in the gNB-CU in order to add TNL association. -4. Perform the gNB-CU Configuration Update procedure to modify TNL association in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate TNL association modification. One method is to use O&M command in the gNB-CU in order to change TNL association usage. -5. Perform the gNB-CU Configuration Update procedure to delete TNL association in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate TNL association deletion. One method is to use O&M command in the gNB-CU in order to delete TNL association. -6. Observe the Protocol Analyzer F1 link logs. - -#### 2.3.1.14.5 Expected Results and Log Observation - -##### 2.3.1.14.5.1 Expected Results - -The cell activation is successfully completed by gNB-CU Configuration Update procedure in step 1. Informing the service status for activated cells may be successfully completed by gNB-DU Configuration Update procedure in this step. - -The cell deactivation is successfully completed by gNB-CU Configuration Update procedure in step 2. - -The TNL association addition is successfully completed by gNB-CU Configuration Update procedure in step 3. - -The TNL association modification is successfully completed by gNB-CU Configuration Update procedure in step 4. - -The TNL association deletion is successfully completed by gNB-CU Configuration Update procedure in step 5. - -##### 2.3.1.14.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 4.1.7.1.1/4.1.7.1.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -#### 2.3.1.15 F1 Setup for NR Stand-Alone - -##### 2.3.1.15.1 Test Purpose - -The purpose of this test case is to verify that the F1 Setup procedure between gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.2.3.1. - -##### 2.3.1.15.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 4.2.3.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol. -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -#### 2.3.1.15.3 Initial Conditions - -- A SCTP association is successfully established between the two SCTP endpoints (SCTP initiation procedure has taken place before or is taking place with execution of this test case) - -#### 2.3.1.15.4 Procedure - -1. Initiate the F1 Setup procedure in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. O&M command in gNB-DU to enable F1 interface -2. This step is executed optionally. The gNB-DU initiates gNB-DU Configuration Update procedure for cell activation if gNB-CU requests gNB-DU to activate cells via F1 SETUP RESPONSE message in order to test OPT1 procedure specified in NR C-Plane profile specification [2] Section 4.2.3.1.1. In this step, all cells or a part of cells requested are activated. If a some of cells requested are activated in this step, the remaining cells may be activated by OPT 2 procedure specified in NR C-Plane profile specification [2] Section 4.2.3.1.1. - 3. This step is executed optionally. The gNB-CU initiates gNB-CU Configuration Update procedure for cell activation if gNB-CU requests gNB-DU to activate cells which have been reported by F1 SETUP REQUEST message sometime after it sent F1 SETUP RESPONSE message in order to test OPT2 procedure specified in NR C-Plane profile specification [2] Section 4.2.3.1.1. Since this step can be independently done from step 2, the cells to be activated in this step may be different from those of step 2. - 4. Observe the Protocol Analyzer F1 link logs - -#### 2.3.1.15.5 Expected Results and Log Observation - -##### 2.3.1.15.5.1 Expected Results - -The F1 Setup procedure is successfully completed. - -The gNB-DU Configuration Update procedure is successfully completed if gNB-CU requests gNB-DU to activate cells via F1 SETUP RESPONSE message. - -The gNB-CU Configuration Update procedure is successfully completed if gNB-CU requests gNB-DU to activate cells which have been reported by F1 SETUP REQUEST message sometime after it sends F1 SETUP RESPONSE message. - -##### 2.3.1.15.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 4.2.3.1.1/4.2.3.1.2. - -#### 2.3.1.16 gNB-DU Configuration Update for NR Stand-Alone - -##### 2.3.1.16.1 Test Purpose - -The purpose of this test case is to verify that the gNB-DU Configuration Update procedure between gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.2.4.1. - -### 2.3.1.16.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 4.2.4.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol. -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -### 2.3.1.16.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] - -### 2.3.1.16.4 Procedure - -1. Perform the gNB-DU Configuration Update procedure to add cells in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate recovery from cell failure. One method is to use O&M command in the gNB-DU in order to make the gNB-DU's cell recover after the transition to its cell failure status. - -2. Perform the gNB-DU Configuration Update procedure to delete cells in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell failure. One method is to use O&M command in the gNB-DU in order to make gNB-DU's cell failure status. - -3. Perform the gNB-DU Configuration Update procedure to inform the Service Status in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate the Service Status of the cell from "In-Service" to "Out-Of-Service". One method is to use O&M command in the gNB-DU in order to change the Service Status from "In-Service" to "Out-Of-Service". - -4. Perform the gNB-DU Configuration Update procedure to modify cells in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation, then change NR PCI information of the deactivated cells. One method is to use O&M command in the gNB-DU in order to deactivate cells and change the NR PCI. - -5. Observe the Protocol Analyzer F1 link logs. - -### 2.3.1.16.5 Expected Results and Log Observation - -#### 2.3.1.16.5.1 Expected Results - -The cell addition is successfully completed by gNB-DU Configuration Update procedure in step 1. - -The cell deletion is successfully completed by gNB-DU Configuration Update procedure in step 2. - -Informing the service status is successfully completed by gNB-DU Configuration Update procedure in step 3. - -The cell modification is successfully completed by gNB-DU Configuration Update procedure in step 4. - -### 2.3.1.16.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 4.2.4.1.1/4.2.4.1.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -## 2.3.1.17 gNB-CU Configuration Update for NR Stand-Alone - -### 2.3.1.17.1 Test Purpose - -The purpose of this test case is to verify that the gNB-CU Configuration Update procedure between gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.2.5.1. - -### 2.3.1.17.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 4.2.5.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol. -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -### 2.3.1.17.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] - -### 2.3.1.17.4 Procedure - -1. Perform the gNB-CU Configuration Update procedure to activate cells in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell activation. One method is to use O&M command in the gNB-CU in order to activate cells. - -2. Perform the gNB-CU Configuration Update procedure to deactivate cells in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation. One method is to use O&M command in the gNB-CU in order to deactivate cells. -3. Perform the gNB-CU Configuration Update procedure to update of gNB-CU generated SIB information. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate change the SIB information. One method is to use O&M command in the gNB-CU in order to change the SIB information. -4. Perform the gNB-CU Configuration Update procedure to bar the cells of gNB-DU managed by the gNB-CU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cells barring. One method is to use O&M command in the gNB-CU in order to make gNB-DU's cells barring. -5. Observe the Protocol Analyzer F1 link logs. - -### 2.3.1.17.5 Expected Results and Log Observation - -#### 2.3.1.17.5.1 Expected Results - -In step 1, after the gNB-DU sent GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE, GNB-DU CONFIGURATION UPDATE and GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE are observed to activate cells. - -In step 2, GNB-CU CONFIGURATION UPDATE and GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE are observed to deactivate cells. - -In step 3, GNB-CU CONFIGURATION UPDATE with updated SIB information is observed. - -In step 4, GNB-CU CONFIGURATION UPDATE with modified Cell barring informing is observed. - -#### 2.3.1.17.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 4.2.5.1.1/4.2.5.1.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -### 2.3.1.18 Paging (CN-initiated) - -#### 2.3.1.18.1 Test Purpose - -The purpose of this test case is to verify that the Paging (CN-initiated) procedure between gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.2.6.1. - -#### 2.3.1.18.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 4.2.6.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -### 2.3.1.18.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure specified in NR C-Plane profile specification [2] Section 6.1.2 has been successfully completed - -### 2.3.1.18.4 Procedure - -1. Initiate Paging procedure from Core or Core emulator (5GC capabilities) to page a UE in RRC-IDLE state. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Initiate data transfer from Core or Core emulator (5GC capabilities) to UE in CM-IDLE state. - -2. Observe the Protocol Analyzer F1 link logs. - -### 2.3.1.18.5 Expected Results and Log Observation - -#### 2.3.1.18.5.1 Expected Results - -The Paging procedure is successfully completed. - -In step 2, the Paging message is observed to page the UE. - -#### 2.3.1.18.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 4.2.6.1/4.2.6.2. - -### 2.3.1.19 UE context creation (service request) - -#### 2.3.1.19.1 Test Purpose - -The purpose of this test case is to verify that the UE initiated Service Request procedure leads to a correct interworking between gNB-CU and gNB-DU from different vendors using the UE Context Setup procedure, conforming to the NR C-Plane profile specification [2] Section 6.1.1 - -#### 2.3.1.19.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 6.1.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -### 2.3.1.19.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure specified in NR C-Plane profile specification [2] Section 6.1.2 has been successfully completed - -### 2.3.1.19.4 Procedure - -1. Initiate Service Request procedure from UE or UE emulator - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Initiate data transfer from a UE in CM-IDLE state Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Stop data transfer between the Application Test Server and the Test UE or UE emulator - 3. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after UE context was created. - -4. Observe the Protocol Analyzer F1 logs - -### 2.3.1.19.5 Expected Results and Log Observation - -#### 2.3.1.19.5.1 Expected Results - -The F1 UE Context Setup procedure is successfully completed. - -The service request procedure is successfully performed, a PDU session and DRB are established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible. - -#### 2.3.1.19.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.1.1.2/6.1.1.3. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated after step 1 a. and in step 4: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or emulated UE and the Application Test Server, respectively - -## 2.3.1.20 UE context creation (registration request) - -### 2.3.1.20.1 Test Purpose - -The purpose of this test case is to verify that the UE initiated Initial Registration Request procedure can be performed successfully with gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] Section 6.1.2. - -### 2.3.1.20.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 6.1.2 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -### 2.3.1.20.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- The F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has not registered to the network - -### 2.3.1.20.4 Procedure - -1. Initiate Initial Registration Request procedure from UE or UE emulator - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Switch on a powered-off UE -2. Observe the Protocol Analyzer F1 logs - -### 2.3.1.20.5 Expected Results and Log Observation - -#### 2.3.1.20.5.1 Expected Results - -The F1 procedure as specified in the NR C-Plane profile specification [2] Section 6.1.2.2 is successfully completed. - -The Initial registration procedure is successfully completed, and a new UE context is created in NG-RAN for signaling only connection. - -#### 2.3.1.20.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.1.2.2/6.1.2.3. - -### 2.3.1.21 UE Context Release - -#### 2.3.1.21.1 gNB-DU Initiated UE Context Release - -##### 2.3.1.21.1.1 Test Purpose - -The purpose of this test case is to verify that the gNB-DU initiated UE Context Release Procedure is successfully performed between gNB-DU and gNB-CU from different vendors, conforming to the NR C-Plane profile specification [2] Section 6.2.1. - -##### 2.3.1.21.1.2 Minimum Requirements - -DUTs: Single gNB-DU and single gNB-CU: - -- DUTs shall apply the parameter condition specified in 6.2.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to perform gNB-DU initiated UE Context Release -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -##### 2.3.1.21.1.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- The F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network and a PDU session has been established, ie, Registration procedure specified in NR C-Plane profile specification [2] Section 6.1.2 has been successfully completed - -##### 2.3.1.21.1.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros) - -2. Initiate gNB-DU initiated UE Context Release procedure from UE or UE emulator. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Simulate radio link failure by increasing the attenuation of gNB cell. - -3. Observe the Protocol Analyzer F1 logs. - -#### 2.3.1.21.1.5 Expected Results and Log Observation - -##### 2.3.1.21.1.5.1 Expected Results - -The F1 gNB-DU initiated UE Context Release procedure is performed successfully. - -##### 2.3.1.21.1.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.2.1.1/6.2.1.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator and the Application Test server, respectively. - -### 2.3.1.21.2 gNB-CU Initiated UE Context Release - -#### 2.3.1.21.2.1 Test Purpose - -The purpose of this test case is to verify that the UE Context Release Procedure is successfully performed between gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] Section 6.2.2 - -#### 2.3.1.21.2.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 6.2.2 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (5GC capabilities and optional EPC capabilities for EPS services): used to terminate UEs (emulator) NAS protocol -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol, data transmission/reception and optional IMS services with EPS Fallback -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -#### 2.3.1.21.2.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- The F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network and a PDU session has been established, ie, Registration procedure specified in NR C-Plane profile specification [2] Section 6.1.2 has been successfully completed - -#### 2.3.1.21.2.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros) - -2. Initiate UE Context Release procedure from UE or UE emulator - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Power off the Test UE or UE emulator or - - b. Turn on flight-mode in Test UE (or UE emulator) or - - c. Delete subscriber in AMF or - - d. Initiate an IMS voice or emergency call with fallback to EPS -3. Observe the Protocol Analyzer F1 logs - -### 2.3.1.21.2.5 Expected Results and Log Observation - -#### 2.3.1.21.2.5.1 Expected Results - -The F1 UE Context Release procedure is successfully completed. - -The NGAP UE Context Release procedure is successfully completed, NG-AP signaling connection and associated User Plane connections are released - -#### 2.3.1.21.2.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.2.2.1/6.2.2.2 - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator and the Application Test server, respectively - -### 2.3.1.22 gNB–CU Initiated UE Context Modification (SCell to be setup/removed) - -#### 2.3.1.22.1 Test Purpose - -The purpose of this test case is to verify that the UE Context Modification procedure to setup or remove SCell(s) for a UE can be performed successfully between gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] Section 6.3.1.1. - -#### 2.3.1.22.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU, PCell and SCell(s) are available and configured for Carrier Aggregation: - -- DUTs shall apply the parameter condition specified in 6.3.1.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of Carrier Aggregation: used to perform UE Context Modification procedure for SCell(s) setup or release. -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol. -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -#### 2.3.1.22.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- The F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure specified in NR C-Plane profile specification [2] Section 6.1.2 has been successfully completed -- The service request procedure, as specified in NR C-Plane profile specification [2] Section 6.1.1, is successfully performed, a DRB is established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible -- Test UE or UE emulator is within the coverage area of the PCell - -#### 2.3.1.22.4 Procedure - -1. Perform data transfer in the both directions between the Application Test Server and the Test UE or UE emulator. -2. Initiate UE Context Modification procedure for SCell(s) setup - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Move the Test UE or UE emulator under the coverage area of the SCell, while still remaining under the coverage area of the PCell, eg. by making use of variable attenuators. In this specific case, the SCell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the UE Context Modification Procedure for SCell Setup, eg, after Event A1 reporting from UE. -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the UE context was modified. - -5. After expiration of at least 10 seconds, perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -6. Initiate UE Context Modification procedure for SCell(s) removal - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Move the Test UE or UE emulator away from the coverage area of the SCell, while still remaining under the coverage area of the PCell, eg, by making use of variable attenuators. In this specific case, the SCell can start low attenuation applied which is subsequently increased to a level which can trigger the UE Context Modification Procedure for SCell Removal, eg, after Event A2 reporting from UE. -7. Stop data transfer between the Application Test Server and the Test UE or UE emulator - 8. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. -- Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the UE context was modified. -9. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs - -### 2.3.1.22.5 Expected Results and Log Observation - -#### 2.3.1.22.5.1 Expected Results - -Data transfer is still ongoing after step 4 and after step 9. - -#### 2.3.1.22.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.3.1.1/6.3.1.1.1. - -If any of the following listed IEs is observed in the F1 logs: - -- “SCell Failed To Setup List” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1 and after step 2 and in step 4 as well in step 5 and after step 6 and in step 8: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator - -### 2.3.1.23 gNB–CU Initiated UE Context Modification (DRB to be setup) - -#### 2.3.1.23.1 Test Purpose - -The purpose of this test case is to verify that the UE Context Modification procedure to setup a DRB for a UE can be performed successfully between gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] Section 6.3.1.2. - -#### 2.3.1.23.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 6.3.1.2/6.3.1.2.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to perform UE Context Modification procedure for DRB setup -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -#### 2.3.1.23.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- The F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure specified in NR C-Plane profile specification [2] Section 6.1.2 has been successfully completed -- Test UE or UE emulator is within the coverage area of the PCell - -- The service request procedure, as specified in NR C-Plane profile specification [2] Section 6.1.1, is successfully performed, a DRB is established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible - -#### 2.3.1.23.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Initiate UE Context Modification procedure for DRB setup - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Add another DRB to the UE by requesting another service, eg, Video streaming, resulting in a PDU Session Resource Setup or Modification Request - 3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. -- Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the UE context was modified. -5. Observe the Protocol Analyzer F1 logs - -#### 2.3.1.23.5 Expected Results and Log Observation - -##### 2.3.1.23.5.1 Expected Results - -The F1 UE Context Modification procedure for DRB setup to UE is performed successfully. - -Data transfer is possible using the newly established DRB. - -##### 2.3.1.23.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.3.1.2/6.3.1.2.1. - -If any of the following listed IEs is observed in the F1 log - -- “DRB Failed To Setup List” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator and the Application Test Server, respectively. - -#### 2.3.1.24 gNB–CU Initiated UE Context Modification (DRB to be released) - -##### 2.3.1.24.1 Test Purpose - -The purpose of this test case is to verify that the UE Context Modification procedure to release a DRB for a UE can be performed successfully between gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] Section 6.3.1.3. - -### 2.3.1.24.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 6.3.1.3/6.3.1.3.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to perform UE Context Modification procedure for DRB setup -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -### 2.3.1.24.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- The F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, the registration procedure specified in NR C-Plane profile specification [2] Section 6.1.2 has been successfully completed -- Test UE or UE emulator is within the coverage area of the PCell -- The service request procedure, as specified in NR C-Plane profile specification [2] Section 6.1.1, is successfully performed, at least two DRBs are established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible - -### 2.3.1.24.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Initiate UE Context Modification procedure for DRB release - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Remove one of at least two established DRBs from the UE by releasing one service, eg, Video streaming, resulting in a PDU Session Resource Release or Modification Request -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the UE context was modified - -5. Observe the Protocol Analyzer F1 logs - -### 2.3.1.24.5 Expected Results and Log Observation - -#### 2.3.1.24.5.1 Expected Results - -The F1 UE Context Modification procedure for DRB release to UE is performed successfully. - -Data transfer is possible using the remaining DRB. - -### 2.3.1.24.5.2 Log Observation - -F1 (and NG) logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.3.1.3/6.3.1.3.1. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator and the Application Test Server, respectively - -### 2.3.1.25 Reset (gNB-DU initiated) for EN-DC - -#### 2.3.1.25.1 Test Purpose - -The purpose of this test case is to verify that the gNB-DU initiated Reset procedure with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.1.2.3. - -#### 2.3.1.25.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU. - -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator: used to perform en-gNB initiated Partial Reset or Reset procedure -- Test UEs or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UE (emulator) NAS protocol -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and content - -#### 2.3.1.25.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Multiple Test UEs or emulated UEs have registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UEs or emulated UEs are within the coverage area of the SN cell, and Secondary Node Addition (eg, SN terminated split bearer) procedure has been successfully completed according to NR C-Plane profile specification [2] - -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -#### 2.3.1.25.4 Procedure - -1. Perform the gNB-DU initiated Reset procedure over F1 to indicate the release of all allocated UE contexts. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation. One method is to use O&M command in the gNB-DU in order to deactivate all cells serving UEs. - -Note: After the Step1, one of the following procedures may occur: - -Case1) If part of UE associations over the X2 interface are affected by the gNB-DU initiated Reset procedure over F1, then the en-gNB initiated Partial Reset procedure over X2 described in Section 2.2.1.6 - -Case2) If all of UE associations over the X2 interface are affected by the gNB-DU initiated Reset procedure over F1, then the en-gNB initiated Reset procedure over X2 described in Section 2.2.1.4. Then up to implementation, either PARTIAL RESET REQUIRED message over X2 or RESET REQUEST message over X2 is sent from the gNB-CU. PARTIAL RESET CONFIRM message over X2 or RESET RESPONSE message over X2 is sent from the eNB accordingly. - -2. Observe the Protocol Analyzer X2 and F1 link logs. - -#### 2.3.1.25.5 Expected Results and Log Observation - -##### 2.3.1.25.5.1 Expected Results - -The gNB-DU initiated Reset procedure is successfully completed. - -All of the UE contexts affected by the gNB-DU initiated Reset procedure are successfully released in the gNB-CU and data transfer between the Application Test Server and the Test UE or UE emulator has ended. - -##### 2.3.1.25.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.1.2.3.1/4.1.2.3.2. - -If any of the following listed IEs is observed in the F1 logs - -- “Criticality Diagnostics” in “RESET ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -#### 2.3.1.26 Reset (gNB-CU initiated) for EN-DC - -##### 2.3.1.26.1 Test Purpose - -The purpose of this test case is to verify that the gNB-CU initiated Reset procedure with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.1.2.4. - -##### 2.3.1.26.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU. - -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator: used to perform en-gNB initiated Reset procedure -- Test UEs or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UE (emulator) NAS protocol -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and content - -### 2.3.1.26.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Multiple Test UEs or emulated UEs have registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UEs or emulated UEs are within the coverage area of the SN cell, and Secondary Node Addition (eg, SN terminated split bearer) procedure has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.3.1.26.4 Procedure - -1. Perform the gNB-CU initiated Reset procedure over X2 to indicate the release of all allocated UE contexts. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation. One method is to use O&M command in the gNB-CU in order to deactivate all cells serving UEs. - -Note: After Step1, the gNB-CU performs Reset procedure over F1 to all of UE associations over the F1 interface affected by the gNB-CU initiated Reset procedure over X2. - -2. Observe the Protocol Analyzer F1 and X2 link logs. - -### 2.3.1.26.5 Expected Results and Log Observation - -#### 2.3.1.26.5.1 Expected Results - -The gNB-CU initiated Reset procedure is successfully completed. - -All of the UE contexts affected by the gNB-CU initiated Reset procedure is successfully released in the gNB-CU and data transfer between the Application Test Server and the Test UE or UE emulator has ended. - -#### 2.3.1.26.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.1.2.4.1/4.1.2.4.2. - -If any of the following listed IEs is observed in the F1 logs - -- “Criticality Diagnostics” in “RESET ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -### 2.3.1.27 Partial Reset (gNB-DU initiated) for EN-DC - -#### 2.3.1.27.1 Test Purpose - -The purpose of this test case is to verify that the gNB-DU initiated Partial Reset procedure with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.1.4.3. - -#### 2.3.1.27.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU. - -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator: used to perform en-gNB initiated Partial Reset procedure -- Test UEs or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UE (emulator) NAS protocol -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and content - -#### 2.3.1.27.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Multiple Test UEs or emulated UEs have registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UEs or emulated UEs are within the coverage area of the SN cell, and Secondary Node Addition (eg, SN terminated split bearer) procedure has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -#### 2.3.1.27.4 Procedure - -1. Perform the gNB-DU initiated Partial Reset procedure over F1 to indicate the release of a part of allocated UE contexts. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation. One method is to use O&M command in the gNB-DU in order to deactivate a few cells serving UEs. - -Note: After Step1, the gNB-CU performs Partial Reset procedure over X2 to the part of UE association over the X2 interface affected by the gNB-DU initiated Partial Reset procedure over F1. - -2. Observe the Protocol Analyzer F1 and X2 link logs. - -### 2.3.1.27.5 Expected Results and Log Observation - -#### 2.3.1.27.5.1 Expected Results - -The gNB-DU initiated Partial Reset procedure is successfully completed. - -The part of the UE contexts affected by the gNB-DU initiated Partial Reset procedure is successfully released in the gNB-CU and data transfer between the Application Test Server and the Test UE or UE emulator has ended. - -#### 2.3.1.27.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.1.4.3.1/4.1.4.3.2. - -If any of the following listed IEs is observed in the F1 logs - -- “Criticality Diagnostics” in “RESET ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -### 2.3.1.28 Partial Reset (gNB-CU initiated) for EN-DC - -#### 2.3.1.28.1 Test Purpose - -The purpose of this test case is to verify that the gNB-CU initiated Partial Reset procedure with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.1.4.4. - -#### 2.3.1.28.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU. - -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator: used to perform en-gNB initiated Partial Reset procedure -- Test UEs or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UE (emulator) NAS protocol -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and content - -#### 2.3.1.28.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] - -- Multiple Test UEs or emulated UEs have registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UEs or emulated UEs are within the coverage area of the SN cell, and Secondary Node Addition (eg, SN terminated split bearer) procedure has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -#### 2.3.1.28.4 Procedure - -1. Perform the gNB-CU initiated Partial Reset procedure over X2 to indicate the release of a part of allocated UE contexts. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation. One method is to use O&M command in the gNB-CU in order to deactivate a few cells serving UEs. - -NOTE: After Step1, the gNB-CU performs Reset procedure over F1 to the part of UE association over the F1 interface affected by the gNB-CU initiated Partial Reset procedure over X2. - -2. Observe the Protocol Analyzer F1 and X2 link logs. - -#### 2.3.1.28.5 Expected Results and Log Observation - -##### 2.3.1.28.5.1 Expected Results - -The gNB-CU initiated Partial Reset procedure is successfully completed. - -The part of the UE contexts affected by the gNB-CU initiated Partial Reset procedure is successfully released in the gNB-CU and data transfer between the Application Test Server and the Test UE or UE emulator has ended. - -##### 2.3.1.28.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.1.4.4.1/4.1.4.4.2. - -If any of the following listed IEs is observed in the F1 logs - -- “Criticality Diagnostics” in “RESET ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -#### 2.3.1.29 Reset (gNB-CU initiated) for NR Stand-Alone - -##### 2.3.1.29.1 Test Purpose - -The purpose of this test case is to verify that the gNB-CU initiated Reset procedure with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.2.2.3. - -##### 2.3.1.29.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU. - -Testing tools which are required for this test scenario: - -- Test UEs or UE emulator which is capable of supporting NR: used to terminate NAS/AS protocol and data transmission/reception - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -### 2.3.1.29.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Multiple Test UEs or emulated UEs have registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Data transfer between the Application Test Server and Test UE or UE emulator is possible - -### 2.3.1.29.4 Procedure - -1. Perform the gNB-CU initiated Reset procedure over F1 to indicate the release of all allocated UE contexts. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation. One method is to use O&M command in the gNB-CU in order to deactivate all cells serving UEs. - -2. Perform the gNB-CU initiated Reset procedure over F1 to indicate the release of a part of allocated UE contexts. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation. One method is to use O&M command in the gNB-CU in order to deactivate a few cells serving UEs. - -3. Observe the Protocol Analyzer F1 link logs. - -### 2.3.1.29.5 Expected Results and Log Observation - -#### 2.3.1.29.5.1 Expected Results - -The reset is successfully completed by Reset (gNB-CU initiated) procedure in step1. All of the UE contexts affected by the gNB-CU initiated Reset procedure are successfully released in the gNB-CU and data transfer between the Application Test Server and the Test UE or UE emulator has ended. - -The partial reset is successfully completed by Reset (gNB-CU initiated) procedure in step2. The part of the UE contexts affected by the gNB-CU initiated Reset procedure is successfully released in the gNB-CU and data transfer between the Application Test Server and the Test UE or UE emulator has ended. - -#### 2.3.1.29.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.2.2.3.1/4.2.2.3.2.1/4.2.2.3.2.2. - -If any of the following listed IEs is observed in the F1 logs - -- “Criticality Diagnostics” in “RESET ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -### 2.3.1.30 Reset (gNB-DU initiated) for NR Stand-Alone - -#### 2.3.1.30.1 Test Purpose - -The purpose of this test case is to verify that the gNB-DU initiated Reset procedure with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.2.2.4. - -#### 2.3.1.30.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU. - -Testing tools which are required for this test scenario: - -- Test UEs or UE emulator which is capable of supporting NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -#### 2.3.1.30.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Multiple Test UEs or emulated UEs have registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Data transfer between the Application Test Server and Test UE or UE emulator is possible - -#### 2.3.1.30.4 Procedure - -1. Perform the gNB-DU initiated Reset procedure over F1 to indicate the release of all allocated UE contexts. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation. One method is to use O&M command in the gNB-DU in order to deactivate all cells serving UEs. - -2. Perform the gNB-DU initiated Reset procedure over F1 to indicate the release of a part of allocated UE contexts. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation. One method is to use O&M command in the gNB-DU in order to deactivate a few cells serving UEs. - -3. Observe the Protocol Analyzer F1 link logs. - -#### 2.3.1.30.5 Expected Results and Log Observation - -##### 2.3.1.30.5.1 Expected Results - -The reset is successfully completed by Reset (gNB-DU initiated) procedure in step 1. All of the UE contexts affected by the gNB-DU initiated Reset procedure are successfully released in the gNB-CU and data transfer between the Application Test Server and the Test UE or UE emulator has ended. - -The partial reset is successfully completed by Reset (gNB-DU initiated) procedure in step2. The part of the UE contexts affected by the gNB-DU initiated Reset procedure is successfully released in the gNB-CU and data transfer between the Application Test Server and the Test UE or UE emulator has ended. - -#### 2.3.1.30.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.2.2.4.1/4.2.2.4.2.1/4.2.2.4.2.2. - -If any of the following listed IEs is observed in the F1 logs - -- “Criticality Diagnostics” in “RESET ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -### 2.3.1.31 Intra gNB-DU, Intra Cell Handover - -#### 2.3.1.31.1 Test Purpose - -The purpose of this test case is to verify that Intra gNB-DU, Intra Cell Handover procedure can be successfully completed between gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] Section 6.5.1 (section 6.5.1.1 for alternative 1 or section 6.5.1.3 for alternative 2). - -#### 2.3.1.31.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU. - -DUTs shall apply the parameter condition specified in 6.5.1 of the NR C-Plane profile specification [2]. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to perform Intra gNB-DU, Intra Cell Handover -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe F1 procedural flows and Content - -#### 2.3.1.31.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Data transfer between the Application Test Server and Test UE or UE emulator is possible - -#### 2.3.1.31.4 Procedure - -1. Perform data transfer in the both directions between the Application Test Server and the Test UE or UE emulator -2. Perform Intra gNB-DU, Intra cell handover - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Perform Security Key update by AMF by setting "Security Key" IE in NGAP: UE CONTEXT MODIFICATION REQUEST on Core emulator -3. Stop data transfer between the Application Test Server and Test UE or UE emulator -4. Perform data transfer in both directions between the Application test Server and Test UE or UE emulator for 10 seconds -5. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs - -### **2.3.1.31.5 Expected Results and Log Observation** - -#### **2.3.1.31.5.1 Expected Results** - -Intra gNB-DU, Intra Cell Handover procedure is successfully completed. - -Data transfer is still ongoing. - -#### **2.3.1.31.5.2 Log Observation** - -F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 6.5.1.1/6.5.1.2 or 6.5.1.3/6.5.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- ‘‘Criticality Diagnostics’’ in ‘‘UE CONTEXT MODIFICATION RESPONSE’’ - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4 - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4 - - o All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### **2.3.1.32 Intra gNB-DU, Inter Cell Handover** - -#### **2.3.1.32.1 Test Purpose** - -The purpose of this test case is to verify that the Intra gNB-DU, Inter Cell Handover between gNB-CU and gNB-DU from different vendors can successfully be completed, conforming to the NR C-Plane profile specification [2] Section 6.5.2 (section 6.5.2.1 for alternative 1 or section 6.5.2.3 for alternative 2) - -#### **2.3.1.32.2 Minimum Requirements** - -DUTs: Single gNB-CU and single gNB-DU, - -- DUTs shall apply the parameter condition specified in 6.5.2.2 of the NR C-Plane profile specification [2] -- The coverage of source cell and target cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to perform Intra gNB-DU, Inter Cell Handover. -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol. - -- Protocol Analyzer: used to record and observe F1 procedural flows and content -- Application Test Server: used to originate and terminate application layer traffic (*eg*, UDP, TWAMP, etc) and provide application layer processing on the network side - -### 2.3.1.32.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, *ie*, Registration procedure and the Service Request procedure specified in NR C-Plane profile specification [2] Section 6.1.1 has been successfully completed. At least one DRB is established and data transfer from the Application Test Server to the Test UE or UE emulator and *vice versa* is possible. -- Test UE or UE emulator is within the coverage area of the source Cell - -### 2.3.1.32.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. -2. Initiate inter cell mobility, resulting in UE Context Modification procedure with PSCell inclusion - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Move the Test UE or UE emulator from the coverage area of the serving Cell under the coverage area of the target Cell *eg*. by making use of variable attenuators. In this specific case, the serving cell can start with low attenuation, the target cell can start off with high attenuation applied which is subsequently changed up to a level which can trigger the UE Context Modification Procedure with PSCell inclusion *eg*, after Event A4 reporting from UE. -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. -- Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the UE context was modified. -5. Observe the Protocol Analyzer F1 logs - -### 2.3.1.32.5 Expected Results and Log Observation - -#### 2.3.1.32.5.1 Expected Results - -The Intra gNB-DU, Inter Cell Handover procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and *vice versa* is ongoing/possible. - -#### 2.3.1.32.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.5.2.1/6.5.2.2 or 6.5.2.3/6.5.2.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator and the Application Test Server, respectively - -### 2.3.1.33 Inter gNB-DU Handover - -#### 2.3.1.33.1 Test Purpose - -The purpose of this test case is to verify that the Inter gNB-DU Handover between gNB-CU and gNB-DU from different vendors can successfully be completed, conforming to the NR C-Plane profile specification [2] Section 6.5.3 - -#### 2.3.1.33.2 Minimum Requirements - -DUTs: Single gNB-CU and two gNB-DU (Source gNB-DU, Target gNB-DU): - -- DUTs shall apply the parameter condition specified in 6.5.3.1/6.5.3.2 of the NR C-Plane profile specification [2] -- The coverage of source cell and target cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to perform Inter gNB-DU, Inter Cell Handover -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -#### 2.3.1.33.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and all gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and the Service Request procedure specified in NR C-Plane profile specification [2] Section 6.1.1 has been successfully completed. At least one DRB is established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible. -- Test UE or UE emulator is within the coverage area of the source Cell - -#### 2.3.1.33.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Initiate inter cell mobility - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Move the Test UE or UE emulator from the coverage area of the serving Cell under the coverage area of the target Cell eg. by making use of variable attenuators. In this specific case, the serving cell can start with low attenuation, the target cell can start off with high attenuation applied which is - -subsequently changed up to a level which can trigger the UE Context Setup Procedure towards the target gNB-DU *eg*, after Event A4 reporting from UE. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the UE context was modified. - -5. Observe the Protocol Analyzer F1 logs - -### 2.3.1.33.5 Expected Results and Log Observation - -#### 2.3.1.33.5.1 Expected Results - -The Inter gNB-DU Handover procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.33.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.5.3.1/6.5.3.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE, MODIFICATION RESPONSE or RELEASE RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator UE and the Application Test Server, respectively - -### 2.3.1.34 Inter RAT Handover to LTE - -#### 2.3.1.34.1 Test Purpose - -The purpose of this test case is to verify that the Inter RAT Handover to LTE procedure, triggered by the UE Context Modification Procedure (containing Mobility from NR Command) between gNB-CU and gNB-DU from different vendors, can successfully be completed, conforming to the NR C-Plane profile specification [2] Section 6.8.1 - -#### 2.3.1.34.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU - -- DUTs shall apply the parameter condition specified in 6.8.1.1/6.8.1.2 of the NR C-Plane profile specification [2] -- The coverage of source en-gNB cell and target eNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to perform Intra gNB-DU, Inter Cell Handover. -- eNB or eNB emulator: used to perform Inter RAT Handover to LTE procedure - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol. -- Protocol Analyzer: used to record and observe F1 and NG procedural flows and content -- Application Test Server: used to originate and terminate application layer traffic (*eg*, UDP, TWAMP, etc) and provide application layer processing on the network side - -### 2.3.1.34.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and all gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, *ie*, Registration procedure and the Service Request procedure specified in NR C-Plane profile specification [2] Section 6.1.1 has been successfully completed. At least one DRB is established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible. -- Test UE or UE emulator is within the coverage area of the source en-gNB Cell - -### 2.3.1.34.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. -2. Initiate inter RAT mobility - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Move the Test UE or UE emulator from the coverage area of the serving en-gNB Cell under the coverage area of the target eNB Cell *eg*. by making use of variable attenuators. In this specific case, the serving cell can start with low attenuation, the target cell can start off with high attenuation applied which is subsequently changed up to a level which can trigger the Handover Required message towards the AMF and the UE Context Modification Procedure (containing Mobility from NR Command) towards the gNB-DU *eg*, after Event B1 reporting from UE. -3. Stop the data transfer between the Application Test Server and the Test UE or UE emulator. - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -*Note:* it is a requirement for this test case to validate that the user plane transmission operates correctly during that inter RTA handover procedure. This involves observing that the user plane data transferred in both directions is successfully received by the Test UE or UE emulator and by the Application Test Server. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer F1 logs - -### 2.3.1.34.5 Expected Results and Log Observation - -#### 2.3.1.34.5.1 Expected Results - -The Inter RAT HO to LTE procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -### 2.3.1.34.5.2 Log Observation - -F1 and NG logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.8.1.1/6.8.1.2 - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” or “UE CONTEXT RELEASE RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 and NG logs is correctly received by the Test UE or UE emulator via NR respectively LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 and NG logs is correctly received by the Test UE or UE emulator via NR respectively LTE RAT - -### 2.3.1.35 RRC Connection Re-establishment (Intra gNB-DU) - -#### 2.3.1.35.1 Test Purpose - -The purpose of this test case is to verify that the RRC Connection Re-establishment (Intra gNB-DU) procedure can be successfully completed between gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] Section 6.10.1. - -#### 2.3.1.35.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU. - -- DUTs shall apply the parameter condition specified in 6.10.1 of the NR C-Plane profile specification [2]. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to perform the RRC connection Re-establishment (Intra gNB-DU). -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol. -- Protocol Analyzer: used to record and observe F1 procedural flows and Content. - -#### 2.3.1.35.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2]. -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed. - -#### 2.3.1.35.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -2. Perform Intra gNB-DU, Inter Cell Handover procedure from source gNB cell to target gNB cell - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT - -- a. The Test UE or UE emulator sends a Measurement Report to the source gNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and source gNB cell and the target gNB cell simultaneously. In this specific case, the source gNB cell can start off with low attenuation applied which is subsequently increased. At the same time, the target gNB cell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the measurement report to be sent to the source gNB. - -3. Perform RRC Connection Re-establishment (Intra gNB-DU) by triggering Handover failure - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT - -- a. Simulate radio link failure by increasing the attenuation of target gNB cell when Handover execution is in progress -4. Stop data transfer between the Application Test Server and Test UE or UE emulator -5. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds -6. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs. - -### 2.3.1.35.5 Expected Results and Log Observation - -#### 2.3.1.35.5.1 Expected Results - -The RRC Connection Re-establishment (Intra gNB-DU) procedure is successfully completed and the UE is successfully connected to source gNB DU cell. - -#### 2.3.1.35.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 6.10.1.1/6.10.1.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE Context Modification Response” - -the test results shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 3 and in step 5 - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or emulated UE -- Regarding the downlink U-Plane data generated in step 1 and after step 3 and in step 5 - - o All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.36 RRC Connection Re-establishment (Inter gNB-DU) - -#### 2.3.1.36.1 Test Purpose - -The purpose of this test case is to verify that RRC Connection Re-establishment (Inter gNB-DU) procedure can be successfully completed with gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] Section 6.10.2. - -### 2.3.1.36.2 Minimum Requirements - -DUTs: Single gNB-CU and Two gNB-DU (Source gNB-DU to Target gNB-DU). - -- DUTs shall apply the parameter condition specified in 6.10.2 of the NR C-Plane profile specification [2]. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to perform the RRC connection Re-establishment (Inter gNB-DU). -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol. -- Protocol Analyzer: used to record and observe F1 procedural flows and Content. - -### 2.3.1.36.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2]. -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed. - -### 2.3.1.36.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Perform Inter gNB-DU Handover procedure from source gNB-DU to target gNB-DU - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT - -- a. The Test UE or UE emulator sends a Measurement Report to the source gNB-DU. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and source gNB-DU and the target gNB-DU simultaneously. In this specific case, the source gNB-DU can start off with low attenuation applied which is subsequently increased. At the same time, the target gNB-DU can start off with high attenuation applied which is subsequently lowered to a level which can trigger the measurement report to be sent to the source gNB-DU. - -3. Perform RRC Connection Re-establishment (Inter gNB-DU) by triggering Handover failure - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT - -- a. Simulate radio link failure by increasing the attenuation of Target gNB-DU. - -4. Stop data transfer between the Application Test Server and Test UE or UE emulator -5. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds -6. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs - -### 2.3.1.36.5 Expected Results and Log Observation - -#### 2.3.1.36.5.1 Expected Results - -The RRC Connection Re-establishment (Inter gNB-DU) procedure is successfully completed and the UE is successfully connected to Target gNB-DU. - -### 2.3.1.36.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 6.10.2.1/6.10.2.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE Context Modification Response” - -the test results shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 3 and in step 5: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or emulated UE -- Regarding the uplink U-Plane data generated in step 1 and after step 3 and in step 5: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.37 RRC connected to RRC inactive - -#### 2.3.1.37.1 Test Purpose - -The purpose of this test case is to verify that the RRC connected to RRC inactive procedure between gNB-CU and gNB-DU from different vendors, performed with a UE Context Release procedure, can successfully be completed, conforming to the NR C-Plane profile specification [2] Section 6.9.1 - -#### 2.3.1.37.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU - -- DUTs shall apply the parameter condition specified in 6.9.1.1/6.9.1.2 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to perform RRC connected to RRC inactive procedure. -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol. -- Protocol Analyzer: used to record and observe F1 procedural flows and content -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc.) and provide application layer processing on the network side - -#### 2.3.1.37.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and all gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and the Service Request procedure specified in NR C-Plane profile specification [2] Section 6.1.1 has been successfully completed. At least one DRB is established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible. - -#### 2.3.1.37.4 Procedure - -1. While the UE or UE emulator is in RRC connected state, perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros - -2. Initiate RRC connected to RRC inactive procedure - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Stop any data transfer in the uplink and downlink direction in the Test UE or UE emulator and in the Application Test Server. - - b. Wait for inactivity detection in gNB-CU. The inactivity detection is controlled by a timer with an expiration value that is dependent on the gNB-CU vendor implementation. After timer expiry, the RRC connected to RRC inactive procedure is initiated by gNB-CU with a UE Context Release Command message. -3. Observe the Protocol Analyzer F1 logs - -#### 2.3.1.37.5 Expected Results and Log Observation - -##### 2.3.1.37.5.1 Expected Results - -The RRC connected to RRC inactive procedure is successfully completed when the UE Context between gNB-CU and gNB-DU is released and the RRC connection between the UE or UE Emulator and the gNB-DU is suspended. - -##### 2.3.1.37.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.9.1.1/6.9.1.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator and the Application Test server, respectively - -#### 2.3.1.38 RRC inactive to RRC connected, Intra gNB-CU - -##### 2.3.1.38.1 Test Purpose - -The purpose of this test case is to verify that the RRC inactive to RRC connected procedure between gNB-CU and gNB-DU from different vendors, performed with a UE Context Setup procedure, can successfully be completed, conforming to the NR C-Plane profile specification [2] Section 6.9.2. - -##### 2.3.1.38.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU - -- DUTs shall apply the parameter condition specified in 6.9.2.1/6.9.2.2 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to perform RRC inactive to RRC connected procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc.) and provide application layer processing on the network side - -### 2.3.1.38.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and the gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and the Service Request procedure specified in NR C-Plane profile specification [2] Section 6.1.1 has been successfully completed. At least one DRB is established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible. -- Data transfer in the uplink and downlink direction towards/from the Test UE or UE emulator is omitted for a period of time. The UE or UE emulator is in RRC inactive state - -### 2.3.1.38.4 Procedure - -1. Initiate RRC inactive to RRC connected procedure - -Two examples of how this procedure can be performed (or triggered) are listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Perform data transfer in the uplink direction from the Test UE or UE emulator towards the Application Test Server - -The RRC inactive to RRC connected procedure is initiated by gNB-CU with UE Context Setup procedure after receiving Initial UL RRC message from UE (RRC resume) via gNB-DU - -- b. As an alternative, perform data transfer in the downlink direction from the Application Test Server towards the Test UE or UE emulator - -Paging procedure is initiated by gNB-CU, before the procedure as described under example a. is started - -2. Stop data transfer between the Application Test Server and the Test UE or UE emulator -3. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds before the RRC connection times out. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the RRC connection was established - -4. Observe the Protocol Analyzer F1 logs - -### 2.3.1.38.5 Expected Results and Log Observation - -#### 2.3.1.38.5.1 Expected Results - -The RRC inactive to RRC connected procedure is successfully completed when the UE Context between gNB-CU and gNB-DU is established and the RRC connection between the UE or UE Emulator and the gNB-DU is resumed. - -#### 2.3.1.38.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.9.2.1/6.9.2.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1 and in step 3: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator and the Application Test server, respectively. - -### 2.3.1.39 S-NG-RAN Node Addition procedure - -#### 2.3.1.39.1 Test Purpose - -The purpose of this test case is to verify that the S-NG RAN Node Addition procedure received by gNB-CU leads to correct interworking between gNB-CU and gNB-DU from different vendors using on F1 UE Context Setup procedures; conforming to the NR C-Plane profile specification [2] Section 7.1.1. This test case is on top of the Xn part of the Secondary Node Addition procedure described in Section 2.4.1.3. - -#### 2.3.1.39.2 Minimum Requirements - -DUTs: Two gNBs (Each gNB with Single gNB-CU and single gNB-DU): - -- DUTs shall apply the parameter condition specified in 7.1.1 of the NR C-Plane profile specification [2] -- The coverages of MgNB cell and SgNB cell overlap each other - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN Node Addition -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol. -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and contents - -#### 2.3.1.39.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Data transfer between the application test server and Test UE or UE emulator is possible - -#### 2.3.1.39.4 Procedure - -1. Perform data transfer in both directions as described in step 1 (except for Note) in Section 2.4.1.3.4 -2. Perform S-NG-RAN Node Addition procedure as described in step 2 in Section 2.4.1.3.4 -3. Stop data transfer as described in step 3 in Section 2.4.1.3.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.3.4. -5. Observe the Protocol Analyzer NG, Xn and F1 logs and Test UE or UE emulator logs. - -#### 2.3.1.39.5 Expected Results and Log Observation - -##### 2.3.1.39.5.1 Expected Results - -The UE Context Setup procedure over F1 is successfully completed. - -The Secondary Node Addition Procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.39.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.1.1.3/7.1.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4 in Section 2.3.1.39.4: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4 in Section 2.3.1.39.4: - - o All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs - -## 2.3.1.40 Resource Status Reporting Initiation - -### 2.3.1.40.1 Test Purpose - -The purpose of this test case is to verify that the Resource Status Reporting Initiation procedure with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.2.9.1. - -### 2.3.1.40.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -Testing tools which are required for this test scenario: - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -### 2.3.1.40.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] - -### 2.3.1.40.4 Procedure - -1. Perform the Resource Status Reporting Initiation procedure to start a measurement in gNB-CU - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One method is to use O&M command in the gNB-CU in order to initiate the Resource Status Reporting Initiation procedure to start the measurement. - -2. Perform the Resource Status Reporting Initiation procedure to add cells to report for a measurement in gNB-CU - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One method is to use O&M command in the gNB-CU in order to initiate the Resource Status Reporting Initiation procedure to add cells to the measurement. - -3. Perform the Resource Status Reporting Initiation procedure to stop a measurement in gNB-CU - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One method is to use O&M command in the gNB-CU in order to initiate the Resource Status Reporting Initiation procedure to stop the measurement - -4. Observe the Protocol Analyzer F1 logs - -### 2.3.1.40.5 Expected Results and Log Observation - -#### 2.3.1.40.5.1 Expected Results - -The start of the measurement is successfully completed by performing the Resource Status Reporting Initiation procedure in step1. - -The cell addition for the measurement initiated in step1 is successfully completed by performing the Resource Status Reporting Initiation procedure in step2. - -The stop of the measurement is successfully completed by performing the Resource Status Reporting Initiation procedure in step3. - -#### 2.3.1.40.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.2.9.1.3/4.2.9.1.4. - -If any of the following listed IEs is observed in the F1 logs - -- “Criticality Diagnostics” in “RESOURCE STATUS RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -### 2.3.1.41 Resource Status Reporting - -#### 2.3.1.41.1 Test Purpose - -The purpose of this test case is to verify that the Resource Status Reporting procedure with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.2.9.2. - -#### 2.3.1.41.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -Testing tools which are required for this test scenario: - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -#### 2.3.1.41.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] - -#### 2.3.1.41.4 Procedure - -1. Perform the Resource Status Reporting procedure from the gNB-DU to report the result of on-going load measurements - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Perform the Resource Status Reporting Initiation procedure (See step 1 in 2.3.1.40.4) - -Note: How to perform the specific procedures for the traffic load are out of scope of this specification. - -2. Observe the Protocol Analyzer F1 logs. - -#### 2.3.1.41.5 Expected Results and Log Observation - -##### 2.3.1.41.5.1 Expected Results - -The Resource Status Reporting procedure is successfully completed. - -### 2.3.1.41.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.2.9.2.3/4.2.9.2.4. - -### 2.3.1.42 Inter-Master Node Handover (with SN Change, Option 3x) - -#### 2.3.1.42.1 Test Purpose - -The purpose of this test case is to verify that an Inter-Master Node Handover (with SN Change, Option 3x) procedure leads to correct interworking between gNB-CU and gNB-DU from different vendors using F1 UE Context Setup, UE Context Modification and UE Context Release procedures, can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 5.4.2.3. This test case is on top of the X2 part of the Inter-Master Node Handover (with SN Change, Option 3x) procedure described in Section 2.2.1.35. - -#### 2.3.1.42.2 Minimum Requirements - -DUTs: Two en-gNB-CU (S-SN-CU, T-SN-CU) and two en-gNB-DU (S-SN-DU, T-SN-DU): - -- DUTs shall apply the parameter condition specified in 5.4.2 of the NR C-Plane profile specification [2] -- The coverage of Source eNB cell (S-MN) overlaps with Target eNB cell (T-MN) and Source en-gNB cell (S-SN) -- The coverage of Target eNB cell (T-MN) overlaps with Target en-gNB cell (T-SN) - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Inter-Master Node Handover (with SN Change, Option 3x) procedure -- eNB or eNB emulator: used to perform Inter-Master Node Handover (with SN Change, Option 3x) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and contents and S1-U UP contents - -#### 2.3.1.42.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNBs according to the NR C-Plane profile specification [2] -- X2 setup procedure between the source eNB and target eNB specified in 3GPP TS 36.423 [12] has been successfully completed -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed - -- Test UE or UE emulator is within the coverage area of the source eNB cell and S-SN cell -- F1 UE Context Setup procedure between S-SN-CU and S-SN-DU, triggered with Secondary Node Addition (Option 3x) procedure between the source eNB and S-SN has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is ongoing (via the LTE and NR RATs) - -#### 2.3.1.42.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Perform the X2 part of Inter-Master Node Handover (with SN Change, Option 3x) procedures as described in step 2 in Section 2.2.1.35.4 -3. Stop data transfer between the Application Test Server and Test UE or UE emulator -3. Perform data transfer in both directions as described step 4 in Section 2.2.1.35.4 -5. Observe the Protocol Analyzer F1, S1 and X2 logs and Test UE or UE emulator logs - -#### 2.3.1.42.5 Expected Results and Log Observation - -##### 2.3.1.42.5.1 Expected Results - -The F1 UE Context Setup, UE Context Modification, and UE Context Release procedure are successfully completed. - -The Secondary Node Change procedure is successfully completed. - -The Inter-Master Node Handover (with SN Change, Option 3x) procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.42.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.4.2.3/5.4.2.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4 in Section 2.3.1.42.4: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4 in Section 2.3.1.42.4: - - o All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.4.3 Allowed Band Combination list update (MN initiated) - -#### 2.3.1.4.3.1 Test Purpose - -The purpose of this test case is to verify that the Allowed Band Combination list update procedure (MN initiated) received by gNB-CU leads to correct interworking between gNB-CU and gNB-DU from different vendors using on F1 UE Context Modification procedure; conforming to the NR C-Plane profile specification [2] Section 5.6.2. This test case is on top of the X2 part of the Allowed Band Combination list update (MN initiated) procedure described in Section 2.2.1.30. - -#### 2.3.1.4.3.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.2 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator: used to perform Allowed Band Combination list update procedure (MN initiated) -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform Allowed Band Combination list update procedure (MN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and content - -#### 2.3.1.4.3.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.3.1.4.3.4 Procedure - -1. Perform Allowed Band Combination list update procedure (MN initiated) as described in step 1 in Section 2.2.1.30.4. -2. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs. - -#### 2.3.1.4.3.5 Expected Results and Log Observation - -##### 2.3.1.4.3.5.1 Expected Results - -The UE Context Modification procedure over F1 is successfully completed. - -The Allowed Band Combination list update procedure (MN initiated) is successfully completed. - -### 2.3.1.43.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.2.3/5.6.2.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer show that: - -- After step 1 the updated allowedBC-ListMRDC is applied in gNB-DU - - An example of how to observe the updated allowedBC-ListMRDC is to check F1 log. The exact method to observe the updated allowedBC-ListMRDC is out of scope of this specification. - -### 2.3.1.44 SCG config query (MN initiated) for EN-DC - -#### 2.3.1.44.1 Test Purpose - -The purpose of this test case is to verify that the SCG config query procedure (MN initiated) received by gNB-CU leads to correct interworking between gNB-CU and gNB-DU from different vendors using on F1 UE Context Modification procedure; conforming to the NR C-Plane profile specification [2] Section 5.6.4. This test case is on top of the X2 part of the SCG config query (MN initiated) procedure described in Section 2.2.1.32. - -#### 2.3.1.44.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.4 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator: used to perform SCG config query procedure (MN initiated) -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform MN initiated SCG config query procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and content - -#### 2.3.1.44.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed - -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.3.1.44.4 Procedure - -1. Perform SCG config query procedure (MN initiated) as described in step 1 in Section 2.2.1.32.4 -2. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs - -#### 2.3.1.44.5 Expected Results and Log Observation - -##### 2.3.1.44.5.1 Expected Results - -The UE Context Modification procedure over F1 is successfully completed. - -The SCG config query procedure (MN initiated) is successfully completed. - -##### 2.3.1.44.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.4.3/5.6.4.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer show that: - -- After step 1 the CellGroupConfig is applied in gNB-CU: - - An example of how to observe the CellGroupConfig is to check F1 log. The exact method to observe the SCG configuration Query is out of scope of this specification - -#### 2.3.1.45 gNB-DU initiated UE Context Modification (DRB to be released) - -##### 2.3.1.45.1 Test Purpose - -The purpose of this test case is to verify that the gNB-DU initiated UE Context Modification procedure to release DRB for a UE can be performed successfully between gNB-DU and gNB-CU from different vendors, conforming to the NR C-Plane profile specification [2] Section 6.3.2.1. - -##### 2.3.1.45.2 Minimum Requirements - -DUTs: Single gNB-DU and single gNB-CU: - -- DUTs shall apply the parameter condition specified in 6.3.2.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to perform gNB-DU initiated UE Context Modification procedure for DRB release -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -##### 2.3.1.45.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- The F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, the registration procedure specified in NR C-Plane profile specification [2] Section 6.1.2 has been successfully completed -- Test UE or UE emulator is within the coverage area of the PCell -- The service request procedure, as specified in NR C-Plane profile specification [2] Sections 6.3.2.1/6.3.2.1.1, is successfully performed, at least two DRBs are established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible - -#### 2.3.1.45.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Initiate gNB-DU initiated UE Context Modification procedure for DRB release - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Remove one of at least two established DRBs from the UE by simulating radio link failure by increasing the attenuation of gNB-DU -3. Stop the data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds -5. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs - -#### 2.3.1.45.5 Expected Results and Log Observation - -##### 2.3.1.45.5.1 Expected Results - -The F1 gNB-DU initiated UE Context Modification procedure for DRB release to UE is performed successfully. - -##### 2.3.1.45.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.3.2.1/6.3.2.1.1. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION CONFIRM” or “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or emulated UE -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.46 Inter RAT Handover to NR - -#### 2.3.1.46.1 Test Purpose - -The purpose of this test case is to verify that the Inter RAT Handover to NR procedure, triggered by the UE Context setup Request between gNB-CU and gNB-DU from different vendors, can successfully be completed, conforming to the NR C-Plane profile specification [2] Section 6.8.2 - -#### 2.3.1.46.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU - -- DUTs shall apply the parameter condition specified in 6.8.2 of the NR C-Plane profile specification [2] -- The coverage of source eNB cell and target en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Inter RAT Handover to NR -- eNB or eNB emulator: used to perform Inter RAT Handover to NR procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -#### 2.3.1.46.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions - -The following list of initial conditions are applicable for this specific test case: - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or emulated UE have registered to the LTE network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the source eNB Cell and target en-gNB Cell -- Data transfer between the Application Test Server and Test UE or UE emulator is on-going (via LTE RAT) - -#### 2.3.1.46.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the Inter RAT Handover to NR procedure. - -This involves observing that the user plane data forwarded from the eNB to the en-gNB, over the X2 interface during the Inter RAT Handover to NR procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates which are high enough for the eNB to start buffering user plane downlink data prior to the change of the eNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -## 2. Initiate inter RAT mobility - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Move the Test UE or UE emulator from the coverage area of the serving eNB Cell under the coverage area of the target en-gNB Cell eg. by making use of variable attenuators. In this specific case, the source eNB cell can start off with low attenuation applied which is subsequently increased. At the same time, the target gNB cell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the Handover Request message from AMF and the UE Context Setup Request towards the gNB-DU. -3. Stop data transfer between the Application Test Server and Test UE or UE emulator - 4. Perform data transfer in both directions between the Application test Server and Test UE or UE emulator for 10 seconds - 5. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs - -### 2.3.1.46.5 Expected Results and Log Observation - -#### 2.3.1.46.5.1 Expected Results - -The Inter RAT Handover to NR procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.46.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.8.2.1/6.8.2.2 - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4 - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or emulated UE via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.47 gNB-CU initiated UE Context Modification (DRX cycle activation/deactivation) - -#### 2.3.1.47.1 Test Purpose - -The purpose of this test case is to verify that the UE Context Modification procedure for DRX cycle activation/deactivation for a UE can be performed successfully between gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] Section 6.3.1.4. - -### 2.3.1.47.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 6.3.1.4 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to perform UE Context Modification procedure for DRB setup -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -### 2.3.1.47.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- The F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, the registration procedure specified in NR C-Plane profile specification [2] Section 6.1.2 has been successfully completed -- Test UE or UE emulator is within the coverage area of the Cell - -### 2.3.1.47.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Initiate UE Context Modification procedure for DRX activation - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. One method is to use O&M command in the gNB-CU in order to activate C-DRX for a specific UE or service -- b. Perform a new UE Context Setup procedure with UE or UE emulator for a service which is configured for C-DRX activated - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the UE context was modified. - -5. After expiration of at least 10 seconds, perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -6. Initiate UE Context Modification procedure for DRX deactivation - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. One method is to use O&M command in the gNB-CU in order to deactivate C-DRX for a specific UE or service - -- b. Add another DRB to the UE by requesting another service, which is configured for C-DRX deactivation -7. Stop data transfer between the Application Test Server and the Test UE or UE emulator - 8. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. -- Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the UE context was modified. -9. Observe the Protocol Analyzer F1 logs - -### 2.3.1.47.5 Expected Results and Log Observation - -#### 2.3.1.47.5.1 Expected Results - -After step 1 the F1 UE Context Modification procedure for DRX activation to UE is performed successfully. - -After step 2 the F1 UE Context Modification procedure for DRX deactivation to UE is performed successfully. - -Data transfer is possible. - -#### 2.3.1.47.5.2 Log Observation - -F1 (and NG) logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.3.1 and 6.3.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1 and after step 2 and in step 4 as well in step 5 and after step 6 and in step 8: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator and the Application Test Server, respectively - -### 2.3.1.48 gNB-CU initiated UE Context Modification (DRB to be modified) - -#### 2.3.1.48.1 Test Purpose - -The purpose of this test case is to verify that the gNB-CU initiated UE Context Modification procedure to modify DRB for a UE can be performed successfully between gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] Section 6.3.1.6. - -#### 2.3.1.48.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 6.3.1.6 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to perform UE Context Modification procedure for DRB modification -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -### 2.3.1.48.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- The F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, the registration procedure specified in NR C-Plane profile specification [2] Section 6.1.2 has been successfully completed -- Test UE or UE emulator is within the coverage area of the PCell -- The service request procedure, as specified in NR C-Plane profile specification [2] Section 6.1.1, is successfully performed, a DRBs is established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible - -### 2.3.1.48.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. -2. Initiate UE Context Modification procedure for DRB modification. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Modify an existing 'Non-dynamic 5QI' for a DRB configured in Core emulator (AMF) for the UE, resulting in a PDU Session Resource Modification Request. -3. Stop the data transfer between the Application Test Server and the Test UE or UE emulator. - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - 5. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs. - -### 2.3.1.48.5 Expected Results and Log Observation - -#### 2.3.1.48.5.1 Expected Results - -The F1 UE Context Modification procedure for DRB modification to UE is performed successfully. - -Data transfer is possible using the modified DRB. - -#### 2.3.1.48.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.3.1.6/6.3.1.6.1. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or emulated UE -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.49 M-NG-RAN node initiated SN modification - -#### 2.3.1.49.1 PDU Session Addition - -##### 2.3.1.49.1.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated SN modification (PDU Session Addition) procedure with gNB-CU and gNB-DU from different vendors using F1 UE Context Modification procedure can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.1.1. This test case is on top of the Xn part of the M-NG-RAN node initiated SN modification (PDU Session Addition) procedure described in Section 2.4.1.4.1. - -##### 2.3.1.49.1.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell and SgNB cell overlap each other - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated SN modification (PDU Session Addition) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content - -##### 2.3.1.49.1.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB - -##### 2.3.1.49.1.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.4.1.4. -2. Perform M-NG-RAN node initiated SN modification (PDU Session Addition) procedure as described in step 2 in Section 2.4.1.4.1.4. -3. Stop data transfer as described in step 3 in Section 2.4.1.4.1.4. - -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.4.1.4. -5. Observe the Protocol Analyzer NG, Xn and F1 logs and Test UE or UE emulator logs. - -### 2.3.1.49.1.5 Expected Results and Log Observation - -#### 2.3.1.49.1.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The M-NG-RAN node initiated SN modification (PDU Session Addition) procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.49.1.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.1.3/7.2.1.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs - -### 2.3.1.49.2 PDU Session Release - -#### 2.3.1.49.2.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated SN modification (PDU Session Release) procedure with gNB-CU and gNB-DU from different vendors using F1 UE Context Modification procedure can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.1.2. This test case is on top of the Xn part of the M-NG-RAN node initiated SN modification (PDU Session Release) procedure described in Section 2.4.1.4.2. - -#### 2.3.1.49.2.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell and SgNB cell overlap each other - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated SN modification (PDU Session Release) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content -- At least two PDU Sessions exist to a Test UE or UE emulator in the NW - -### 2.3.1.49.2.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- At least two PDU Sessions exist to a Test UE or UE emulator in the NW - -### 2.3.1.49.2.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.4.2.4. -2. Perform M-NG-RAN node initiated SN modification (PDU Session Release) procedure as described in step 2 in Section 2.4.1.4.2.4. -3. Stop data transfer as described in step 3 in Section 2.4.1.4.2.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.4.2.4. -5. Observe the Protocol Analyzer NG, Xn and F1 logs and Test UE or UE emulator logs. - -### 2.3.1.49.2.5 Expected Results and Log Observation - -#### 2.3.1.49.2.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The M-NG-RAN node initiated SN modification (PDU Session Release) procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.49.2.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.2.3/7.2.1.2.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 after step 2 and in step 4: - -- o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs - -### 2.3.1.49.3 PDU Session Modification - -#### 2.3.1.49.3.1 PDU Session Modification with QoS flow addition - -##### 2.3.1.49.3.1.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow addition) procedure with gNB-CU and gNB-DU from different vendors using F1 UE Context Modification procedure can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.1.3.1. This test case is on top of the Xn part of the M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow addition) procedure described in Section 2.4.1.4.4.1. - -##### 2.3.1.49.3.1.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell and SgNB cell overlap each other - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow addition) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content - -##### 2.3.1.49.3.1.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB - -### 2.3.1.49.3.1.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.4.4.1.4 -2. Perform M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow addition) procedure as described in step 2 in Section 2.4.1.4.4.1.4 -3. Stop data transfer as described in step 3 in Section 2.4.1.4.4.1.4 -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.4.4.1.4 -5. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs - -### 2.3.1.49.3.1.5 Expected Results and Log Observation - -#### 2.3.1.49.3.1.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow addition) procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.49.3.1.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.3.1.3/7.2.1.3.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs - -### 2.3.1.49.3.2 PDU Session Modification with QoS flow release - -#### 2.3.1.49.3.2.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow release) procedure with gNB-CU and gNB-DU from different vendors using F1 UE Context Modification procedure can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.1.3.2. This test case is on top of the Xn part of the M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow release) procedure described in Section 2.4.1.4.4.2. - -#### 2.3.1.49.3.2.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell and SgNB cell overlap each other - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow release) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content -- At least two QoS flows exist to a PDU Session - -### 2.3.1.49.3.2.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- At least two QoS flows exist to a Test UE or UE emulator in the NW - -### 2.3.1.49.3.2.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.4.4.2.4 -2. Perform M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow release) procedure as described in step 2 in Section 2.4.1.4.4.2.4 -3. Stop data transfer as described in step 3 in Section 2.4.1.4.4.2.4 -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.4.4.2.4 -5. Observe the Protocol Analyzer NG, Xn and F1 logs and Test UE or UE emulator logs - -### 2.3.1.49.3.2.5 Expected Results and Log Observation - -#### 2.3.1.49.3.2.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow release) procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -### 2.3.1.49.3.2.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.3.2.3/7.2.1.3.2.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs - -### 2.3.1.49.3.3 PDU Session Modification with 5QI change - -#### 2.3.1.49.3.3.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated SN modification (PDU Session Modification with 5QI change to modify a 5QI (and/or ARP) of the SN terminated split bearer for an existing PDU Session) procedure with gNB-CU and gNB-DU from different vendors using F1 UE Context Modification procedure can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.1.3.3. - -This test case is on top of the Xn part of the M-NG-RAN node initiated SN modification (PDU Session Modification with 5QI change) procedure described in Section 2.4.1.4.8. - -#### 2.3.1.49.3.3.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell and SgNB cell overlap each other - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated SN modification (PDU Session Addition) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content - -#### 2.3.1.49.3.3.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] - -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB - -#### 2.3.1.49.3.3.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.4.8.4. -2. Perform M-NG-RAN node initiated SN modification (PDU Session Modification with 5QI change) procedure as described in step 2 in Section 2.4.1.4.8.4. -3. Stop data transfer as described in step 3 in Section 2.4.1.4.8.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.4.8.4. -5. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -#### 2.3.1.49.3.3.5 Expected Results and Log Observation - -##### 2.3.1.49.3.3.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The M-NG-RAN node initiated SN modification (PDU Session Modification with 5qi change) procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.49.3.3.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.3.3.3/7.2.1.3.3.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- After step 2 the modified 5QI is applied: - -An example of how to observe the 5QI change of the SN terminated split QoS flow from an existing PDU Session is provided below in bullet a. The exact method to observe the changed 5QI is out of scope of this specification - -- a. Check the following two points - - o Check that step 2 (5QI changed with IE “DRB To Be Modified List” included in the messages “UE Context Modification Request”) performs correctly - - o Check that the data is flowing using the QoS flow with the new 5QI in step 4 -- Regarding the downlink U-Plane data generated in step 1, after step 2 and in step 4: - -- o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB. -- Regarding the uplink U-Plane data generated in step 1, after step 2 and step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs - -#### 2.3.1.49.4 Security Key change - -##### 2.3.1.49.4.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated SN modification (Security Key change) procedure with gNB-CU and gNB-DU from different vendors using F1 UE Context Modification procedure can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.1.4. This test case is on top of the Xn part of the M-NG-RAN node initiated SN modification (Security Key change) procedure described in Section 2.4.1.4.3. - -##### 2.3.1.49.4.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell and SgNB cell overlap each other - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated SN modification (Security Key change) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content - -##### 2.3.1.49.4.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB - -#### 2.3.1.49.4.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.4.3.4 -2. Perform M-NG-RAN node initiated SN modification (PDU Session Modification with Security Key change) procedure as described in step 2 in Section 2.4.1.4.3.4 -3. Stop data transfer as described in step 3 in Section 2.4.1.4.3.4 -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.4.3.4 -5. Observe the Protocol Analyzer NG, Xn and F1 logs and Test UE or UE emulator logs - -#### 2.3.1.49.4.5 Expected Results and Log Observation - -##### 2.3.1.49.4.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The M-NG-RAN node initiated SN modification (Security Key change) procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.49.4.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.4.3/7.2.1.4.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB -- Regarding the uplink U-Plane data generated in in step 1 and after step 2 and step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs - -#### 2.3.1.49.5 SCG Configuration Query for NR-DC - -##### 2.3.1.49.5.1 Test Purpose - -The purpose of this test case is to verify that the SCG Configuration Query procedure processing by gNB-CU in both M-gNB and S-gNB leads to correct interworking between gNB-CU and gNB-DU from different vendors using on F1 UE Context Modification procedure; conforming to the NR C-Plane profile specification [2] Section 7.2.1.5. This test case is on top of the Xn part of the SCG Configuration Query procedure described in Section 2.4.1.4.5. - -##### 2.3.1.49.5.2 Minimum Requirements - -DUTs: Two gNBs (Each gNB with Single gNB-CU and single gNB-DU): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- The coverages of MgNB cell and SgNB cell overlap each other - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform SCG Configuration Query procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe Xn and F1 procedural flows and content - -#### 2.3.1.49.5.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU in both MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- S-NG -RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.3.1.49.5.4 Procedure - -1. Perform SCG Configuration Query procedure as described in step 1 in Section 2.4.1.4.5.4 -2. Observe the Protocol Analyzer Xn and F1 logs - -#### 2.3.1.49.5.5 Expected Results and Log Observation - -##### 2.3.1.49.5.5.1 Expected Results - -The UE Context Modification procedure over F1 in both M-gNB and S-gNB is successfully completed. - -The SCG Configuration Query procedure is successfully completed. - -##### 2.3.1.49.5.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.5.3/7.2.1.5.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer show that: - -- “After step 1 the CellGroupConfig is applied in gNB-CU of both MgNB and SgNB: - - An example of how to observe the CellGroupConfig is to check F1 log. The exact method to observe the CellGroupConfig is out of scope of this specification. - -### 2.3.1.49.6 Allowed Band Combination list update - -#### 2.3.1.49.6.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated SN modification (Allowed Band Combination list update) procedure with gNB-CU and gNB-DU from different vendors using on F1 UE Context Modification procedure; conforming to the NR C-Plane profile specification [2] Section 7.2.1.6. This test case is on top of the Xn part of the M-NG-RAN node initiated SN modification (Allowed Band Combination list update) procedure described in Section 2.4.1.4.6. - -#### 2.3.1.49.6.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated SN modification (Allowed Band Combination list update) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content - -#### 2.3.1.49.6.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.3.1.49.6.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.4.6.4. -2. Perform M-NG-RAN node initiated SN modification (Allowed Band Combination list update) procedure as described in step 2 in Section 2.4.1.4.6.4. -3. Stop data transfer as described in step 3 in Section 2.4.1.4.6.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.4.6.4. - -5. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -### 2.3.1.49.6.5 Expected Results and Log Observation - -#### 2.3.1.49.6.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The M-NG-RAN node initiated SN modification (Allowed Band Combination list update) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.49.6.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.6.3/7.2.1.6.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- After step 2 the updated allowedBC-ListMRDC is applied in SgNB-DU: - - An example of how to observe the updated allowedBC-ListMRDC is to check F1 log. The exact method to observe the updated allowedBC-ListMRDC is out of scope of this specification. -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs. - -### 2.3.1.49.7 PCell Change (Intra-MN) - -#### 2.3.1.49.7.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated SN modification (PCell Change (Intra-MN)) procedure with gNB-CU and gNB-DU from different vendors using on F1 UE Context Modification procedure; conforming to the NR C-Plane profile specification [2] Section 7.2.1.7. This test case is on top of the Xn part of the M-NG-RAN node initiated SN modification (PCell Change (Intra-MN)) procedure described in Section 2.4.1.4.7. - -#### 2.3.1.49.7.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- MgNB cell (MN) has at least 2 cells configured and in operation -- The coverage of Intra-MgNB primary cell (MN) and SgNB cell (SN) overlap -- The coverage of Intra-MgNB serving cell and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated SN modification (PCell Change (Intra-MN)) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content - -### 2.3.1.49.7.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure has between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.3.1.49.7.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.4.7.4. -2. Perform M-NG-RAN node initiated SN modification (PCell Change (Intra-MN)) procedure as described in step 2 in Section 2.4.1.4.7.4. -3. Stop data transfer as described in step 3 in Section 2.4.1.4.7.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.4.7.4. -5. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -### 2.3.1.49.7.5 Expected Results and Log Observation - -#### 2.3.1.49.7.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The M-NG-RAN node initiated SN modification (PCell Change (Intra-MN)) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.49.7.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.7.3/7.2.1.7.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be 'successful with remarks'. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs. - -### 2.3.1.49.8 Measurement Gap Coordination Procedure (MN initiated) - -#### 2.3.1.49.8.1 Test Purpose - -The purpose of this test case is to verify that the MgNB initiated measurement gap coordination procedure with gNB-CU and gNB-DU from different vendors using the F1 UE Context Modification procedure can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.1.8. This test case is on top of the Xn part of the MgNB node initiated SN modification (Measurement Gap Coordination Procedure (MN initiated)) procedure described in Section 2.4.1.21. - -#### 2.3.1.49.8.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU resembling an MN, SgNB-CU and SgNB-DU resembling an SN): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to trigger the measurement report procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content - -#### 2.3.1.49.8.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2], for both MgNB and SgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible - -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.3.1.49.8.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.21.4. -2. Perform MgNB node initiated SN modification (Measurement Gap Coordination (MN-initiated)) procedure as described in step 2 in Section 2.4.1.21.4. -3. Stop data transfer as described in step 3 in Section 2.4.1.21.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.21.4. -5. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -#### 2.3.1.49.8.5 Expected Results and Log Observation - -##### 2.3.1.49.8.5.1 Expected Results - -The UE Context Modification procedures are successfully completed. - -The MgNB node initiated SN modification (Measurement Gap Coordination Procedure (MN initiated)) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.49.8.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.8.3/7.2.1.8.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via SgNB and MgNB. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via SgNB and MgNB is recorded in the F1 logs. - -#### 2.3.1.50 NG-RAN Node Configuration Update - -##### 2.3.1.50.1 Test Purpose - -The purpose of this test case is to verify that the NG-RAN Node Configuration Update procedure, to update application-level configuration data between two NG-RAN nodes, can successfully be completed between gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] Section 4.2.8.1. This test case complements the Xn-only test case (2.4.1.16) addressing the corresponding F1 aspects. - -##### 2.3.1.50.2 Minimum Requirements - -DUTs: gNB-CU, and gNB-DU - -- DUTs shall apply the parameter condition specified in 4.2.8.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- gNB or gNB emulator -- Protocol Analyzer: used to record and observe F1 and Xn procedural flows and content - -### 2.3.1.50.3 Initial Conditions - -Refer to Section 2.3 and 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and the gNB-DU according to the NR C-Plane profile specification [2] -- Xn Setup procedure has been successfully completed between the gNB-CU and gNB or gNB emulator according to the NR C-Plane profile specification [2] - -### 2.3.1.50.4 Procedure - -1. Perform NG-RAN Node Configuration Update procedure as described in Section 2.4.1.16.4 step 1 to step 4 in the corresponding Xn only test case -2. Observe the Protocol Analyzer F1 and Xn logs - -### 2.3.1.50.5 Expected Results and Log Observation - -#### 2.3.1.50.5.1 Expected Results - -The F1 gNB-DU Configuration Update procedure, respectively the F1 gNB-CU Configuration Update procedure are successfully completed each time after step 1 – step 4. - -The NG-RAN Node Configuration Update procedure on Xn is successfully completed each time after step 1 – step 4. - -#### 2.3.1.50.5.2 Log Observation - -F1 and Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.2.8.1.3 and 4.2.8.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -### 2.3.1.51 Write-Replace Warning - -#### 2.3.1.51.1 Test Purpose - -The purpose of this test case is to verify that the Write-Replace Warning procedure between gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.2.7.1. - -#### 2.3.1.51.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to perform Write-Replace Warning (System Information and Short Message) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -### 2.3.1.51.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure specified in NR C-Plane profile specification [2] Section 6.1.2 has been successfully completed - -### 2.3.1.51.4 Procedure - -1. Initiate Write-Replace Warning procedure from Core or Core emulator (5GC capabilities). - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Perform Write-Replace Warning by AMF by setting “Warning Area List” IE to broadcast in part of cells of gNB-DU to at least one cell in NGAP: WRITE-REPLACE WARNING REQUEST on Core emulator. -- b. Perform Write-Replace Warning by AMF by not setting “Warning Area List” IE to broadcast in all cells of gNB-DU in NGAP: WRITE-REPLACE WARNING REQUEST on Core emulator. - -2. Observe the Protocol Analyzer F1 link logs. - -### 2.3.1.51.5 Expected Results and Log Observation - -#### 2.3.1.51.5.1 Expected Results - -The Write-Replace Warning procedure is successfully completed. - -#### 2.3.1.51.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 4.2.7.1.1/4.2.7.1.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “WRITE-REPLACE WARNING RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -### 2.3.1.52 System Information Delivery for NR Stand-Alone - -#### 2.3.1.52.1 Test Purpose - -The purpose of this test case is to verify that the System Information Delivery procedure between gNB-CU and gNB-DU from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 6.11.1. - -### 2.3.1.52.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 6.11.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol. -- Protocol Analyzer: used to record and observe F1 procedural flows and content -- Test UE or UE emulator capable of supporting NR and NR-DC: used to receive broadcast information - -### 2.3.1.52.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] - -### 2.3.1.52.4 Procedure - -1. Perform the System Information Delivery procedure. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One method is to use O&M command in the gNB-CU to change any Other SI (SIB2 – SIB9), eg. SIB Type2: Cell re-selection information common for intra-frequency, inter-frequency and/or inter-RAT cell re-selection. Depending on DUT implementation cell lock/unlock may be required. - -### 2.3.1.52.5 Expected Results and Log Observations - -#### 2.3.1.52.5.1 Expected Results - -The System Information Delivery procedure is successfully completed. - -Other SI messages are mapped to BCCH logical channel and either periodically broadcast on DL-SCH or broadcast on-demand on DL-SCH (ie, upon request from UEs in RRC\_IDLE or RRC\_INACTIVE) or sent with dedicated RRC messages on DL-SCH to UEs in RRC\_CONNECTED. - -#### 2.3.1.52.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.11.1.1/6.11.1.2. - -### 2.3.1.53 S-NG-RAN node initiated SN modification with MN involvement - -#### 2.3.1.53.1 UL Configuration Update - -##### 2.3.1.53.1.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification with MN involvement (UL Configuration Update) procedure with gNB-CU and gNB-DU from different vendors using F1 UE Context Modification procedure can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.2.6. This test case is on top of the Xn part of the S-NG-RAN node initiated SN modification with MN involvement (UL Configuration Update) procedure described in Section 2.4.1.5.3. - -### 2.3.1.53.1.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply the parameter condition specified in 7.2.2 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell and SgNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated SN modification with MN involvement (UL Configuration Update) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content - -### 2.3.1.53.1.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification - -### 2.3.1.53.1.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.5.3.4. -2. Perform UL Configuration Update procedure (SN initiated) as described in step 2 in Section 2.4.1.5.3.4. -3. Stop data transfer as described in step 3 in Section 2.4.1.5.3.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.5.3.4. -5. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -### 2.3.1.53.1.5 Expected Results and Log Observation - -#### 2.3.1.53.1.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The S-NG-RAN node initiated SN modification with MN involvement (UL Configuration Update) procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -### 2.3.1.53.1.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.2.6.3/7.2.2.6.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs - -### 2.3.1.53.2 PSCell change, Intra gNB-DU - -#### 2.3.1.53.2.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Intra gNB-DU) procedure with gNB-CU and gNB-DU from different vendors by applying the UE Context Modification procedure on the F1 interface can be successfully completed, conforming to the NR C-plane profile specification [2] section 7.2.2.4. This test case is on top of the Xn part of the S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Intra gNB-DU) procedure described in Section 2.4.1.5.4. - -#### 2.3.1.53.2.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU, SgNB-CU and SgNB-DU): - -- DUTs shall apply the parameter condition specified in 7.2.2.4 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell and SgNB cell overlap -- SgNB-DU has at least 2 Cells configured and in operation - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Intra gNB-DU) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content - -#### 2.3.1.53.2.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the Application Test Server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.3.1.53.2.4 Procedure - -1. Perform data transfer in both downlinks directions as described in step 1 in Section 2.4.1.5.4.4 -2. Perform S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Intra gNB-DU) as described in step 2 in Section 2.4.1.5.4.4 -3. Stop data transfer as described in step 3 in Section 2.4.1.5.4.4 -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.5.4.4 -5. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -#### 2.3.1.53.2.5 Expected Results and Log Observation - -##### 2.3.1.53.2.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Intra gNB-DU) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.53.2.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.2.4.3/7.2.2.4.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs. - -### 2.3.1.53.3 PSCell change, Inter gNB-DU - -#### 2.3.1.53.3.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Inter gNB-DU) procedure with gNB-CU and gNB-DU from different vendors by applying the UE Context Modification procedure on the F1 interface can be successfully completed, conforming to the NR C-plane profile specification [2] section 7.2.2.5. This test case is on top of the Xn part of the S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Inter gNB-DU) procedure described in Section 2.4.1.5.5. - -#### 2.3.1.53.3.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU, SgNB-CU and two SgNB-DUs (Source gNB-DU, Target gNB-DU)): - -- DUTs shall apply the parameter condition specified in 7.2.2.5 of the NR C-Plane profile specification [2] -- The cells of the source and target SgNB-DUs overlap as well as the cell(s) of the MgNB-DU -- SgNB has at least 2 Cells configured to Source SgNB-DU and Target SgNB-DU and in operation - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Inter gNB-DU) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content - -#### 2.3.1.53.3.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the Application Test Server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.3.1.53.3.4 Procedure - -1. Perform data transfer in both downlinks directions as described in step 1 in Section 2.4.1.5.5.4 -2. Perform S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Inter gNB-DU) as described in step 2 in Section 2.4.1.5.5.4 -3. Stop data transfer as described in step 3 in Section 2.4.1.5.5.4 - -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.5.5.4 -5. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -### 2.3.1.53.3.5 Expected Results and Log Observation - -#### 2.3.1.53.3.5.1 Expected Results - -The F1 UE Context Setup, UE Context Modification and UE Context Release procedure are successfully completed. - -The S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Inter gNB-DU) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.53.3.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.2.5.3/7.2.2.5.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs. - -### 2.3.1.53.4 Security Key change - -#### 2.3.1.53.4.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification with MN involvement (Security Key change) procedure with gNB-CU and gNB-DU from different vendors, confirming to the NR C-Plane profile specification [2] Section 7.2.2.3. This test case is on top of the Xn part of the S-NG-RAN node initiated SN modification with MN involvement (Security Key change) procedure described in Section 2.4.1.5.2. - -#### 2.3.1.53.4.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply the parameter condition specified in 7.2.2.3 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated SN modification with MN involvement (Security Key change) procedure - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -#### 2.3.1.53.4.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible - -#### 2.3.1.53.4.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.5.2.4. -2. Perform S-NG-RAN node initiated SN modification with MN involvement (Security Key change) as described in step 2 in Section 2.4.1.5.2.4. -3. Stop data transfer as described in step 3 in Section 2.4.1.5.2.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.5.2.4. -5. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -#### 2.3.1.53.4.5 Expected Results and Log Observation - -##### 2.3.1.53.4.5.1 Expected Results - -The UE Context Modification procedure and UE Context Release procedure are successfully completed. - -The S-NG-RAN node initiated SN modification with MN involvement (Security Key change) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.53.4.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.2.3.3/7.2.2.3.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “DRB Failed to be Modified List” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be 'successful with remarks'. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- After step 2 the updated security key is applied in Test UE or UE emulator: - - An example of how to observe the updated security key is to check the UE emulator log. The exact method to observe the updated security key is out of scope of this specification -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs - -### 2.3.1.53.5 CellGroupConfig change (SN-DU initiated) - -#### 2.3.1.53.5.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification with MN involvement (CellGroupConfig change (SN-DU initiated)) procedure with gNB-CU and gNB-DU from different vendors, confirming to the NR C-Plane profile specification [2] Section 7.2.2.8. This test case is on top of the Xn part of the S-NG-RAN node initiated SN modification with MN involvement (CellGroupConfig change (SN-DU initiated)) procedure described in Section 2.4.1.5.7. - -#### 2.3.1.53.5.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply the parameter condition specified in 7.2.2.8 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated SN modification with MN involvement (CellGroupConfig change (SN-DU initiated)) procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -#### 2.3.1.53.5.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB - -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible - -#### 2.3.1.53.5.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.5.7.4. -2. Perform S-NG-RAN node initiated SN modification with MN involvement (CellGroupConfig change (SN-DU initiated)) as described in step 2 in Section 2.4.1.5.7.4. -3. Stop data transfer as described in step 3 in Section 2.4.1.5.7.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.5.7.4. -5. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -#### 2.3.1.53.5.5 Expected Results and Log Observation - -##### 2.3.1.53.5.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The S-NG-RAN node initiated SN modification with MN involvement (CellGroupConfig change (SN-DU initiated)) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.53.5.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.2.8.3/7.2.2.8.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs - -#### 2.3.1.53.6 Measurement Gap Coordination Procedure (SN initiated) - -##### 2.3.1.53.6.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification with MN involvement (Measurement gap coordination) procedure with gNB-CU and gNB-DU from different vendors by applying the UE Context Modification procedure on the F1 interface can be successfully completed, conforming to the NR C-plane - -profile specification [2] section 7.2.2.7. This test case is on top of the Xn part of the S-NG-RAN node initiated SN modification with MN involvement (Measurement gap coordination) procedure described in Section 2.4.1.5.6. - -### 2.3.1.53.6.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU, SgNB-CU and SgNB-DU): - -- DUTs shall apply the parameter condition specified in 7.2.2.7 of the NR C-Plane profile specification [2] -- The coverage of MgNB and SgNB cells overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to trigger the UE measurement transfer procedure using Measurement Report message and perform S-NG-RAN node initiated SN modification with MN involvement (Measurement gap coordination) procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the core network, ie, 5GC side -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content - -### 2.3.1.53.6.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- The Test UE or UE emulator is within the coverage area of the MgNB and of the SgNB cells -- The Test UE or UE emulator has registered to the network, ie, Registration procedure and the Service Request procedure specified in NR C-Plane profile specification [2] Section 6.1.1 has been successfully completed -- The S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the application test server and test UE or UE emulator is possible - -### 2.3.1.53.6.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.5.6.4. -2. Perform S-NG-RAN node initiated SN modification with MN involvement (Measurement gap coordination) procedure as described in step 2 in Section 2.4.1.5.6.4. -3. Stop data transfer as described in step 3 in Section 2.4.1.5.6.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.5.6.4. -5. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -### 2.3.1.53.6.5 Expected Results and Log Observation - -#### 2.3.1.53.6.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The S-NG-RAN node initiated SN modification with MN involvement (Measurement gap coordination) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.53.6.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.2.7.3/7.2.2.7.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.53.7 Measurement Gap Coordination for per FR2 gap (with MN involvement) Procedure (SN initiated) - -#### 2.3.1.53.7.1 Test Purpose - -The purpose of this test case is to verify that the Measurement Gap Coordination for per FR2 gap (with MN involvement) procedure (SN initiated) with gNB-CU and gNB-DU from different vendors by applying the UE Context Modification procedure on the F1 interface can be successfully completed, conforming to the NR C-plane profile specification [2] section 5.6.8. This test case is on top of the X2 part of the Measurement Gap Coordination procedure (MN initiated) described in Section 2.2.1.21. - -#### 2.3.1.53.7.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.8 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator: used to perform Measurement Gap Coordination for per FR2 gap (with MN involvement) procedure (SN initiated) -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Measurement Gap Coordination for per FR2 gap (with MN involvement) Procedure (SN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol - -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both X2 and F1 procedural flows and content - -### 2.3.1.53.7.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.3.1.53.7.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.2.1.21.4. -2. Perform Measurement Gap Coordination for per FR2 gap (with MN involvement) procedure (SN initiated) as described in step 2 in Section 2.2.1.21.4. -3. Stop data transfer as described in step 3 in Section 2.2.1.21.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.21.4. -5. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs. - -### 2.3.1.53.7.5 Expected Results and Log Observation - -#### 2.3.1.53.7.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The Measurement Gap Coordination for per FR2 gap (with MN involvement) procedure (SN initiated) is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.53.7.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.8.3/5.6.8.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -## 2.3.1.54 Master Node to gNB Change - -### 2.3.1.54.1 Test Purpose - -The purpose of this test case is to verify that the Master Node to gNB Change Procedure leads to a correct interworking between gNB-CU and gNB-DU from different vendors using UE Context Modification and UE Context Release procedure, conforming to the NR C-Plane profile specification [2] Section 7.6.1. This test case is on top of the Xn part of the Master Node to gNB Change Procedure described in Section 2.4.1.12. - -### 2.3.1.54.2 Minimum Requirements - -DUTs: Three gNBs (Each gNB with single gNB-CU and single gNB-DU): - -- DUTs shall apply the parameter condition specified in 7.6.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (S-MN), SgNB cell (S-SN) and T-gNB cell (T-SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform Master Node to gNB Change procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol, and to support Path Switch, Bearer Modification and Secondary RAT Data Usage Report -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn and F1 procedural flows and content - -### 2.3.1.54.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB, SgNB and T-gNB according to the NR C-Plane profile specification [2] -- The F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for MgNB, SgNB and T-gNB -- Test UE or UE emulator has registered to the network, ie, the registration procedure specified in NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification - -#### 2.3.1.54.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. -2. Perform the Master Node to gNB Change Procedure as described in step 2 in Section 2.4.1.12.4. - -Note: the intention of this step is to perform not only the Xn part of the Master Node to gNB Change Procedure but also trigger to perform the F1 signaling, that is UE Context Modification Procedure and the UE Context Release Procedure with gNB-CU and gNB-DU. - -3. Stop data transfer as described in step 3 in Section 2.4.1.12.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.12.4. -5. Observe the Protocol Analyzer NG, Xn and F1 logs, and Test UE or UE emulator logs. - -#### 2.3.1.54.5 Expected Results and Log Observation - -##### 2.3.1.54.5.1 Expected Results - -The UE Context Setup Procedure, UE Context Modification Procedure and the UE Context Release Procedure over F1 are successfully completed. - -The Master Node to gNB Change Procedure over F1 is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.54.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 7.6.1.3/7.6.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4 in Section 2.3.1.54.4: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB or T-gNB -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4 in Section 2.3.1.54.4: - - o All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB or T-gNB is recorded in the F1 logs - -#### 2.3.1.55 Inter-Master Node Handover Without SN Change for NR-DC - -##### 2.3.1.55.1 Test Purpose - -The purpose of this test case is to verify that an Inter-Master Node Handover (Without SN Change) Procedure received by gNB-CU leads to correct interworking between gNB-CU and gNB-DU from different vendors using F1 UE Context Modification and UE Context Release procedures can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.7.1. This test case is on top of the Xn part of Inter-Master Node Handover (Without SN Change) Procedure as described in Section 2.4.1.14. - -### 2.3.1.55.2 Minimum Requirements - -DUTs: Three gNB CUs (S-MN-CU, SN-CU and T-MN-CU) and three gNB DUs (S-MN-DU, SN-DU and T-MN-DU): - -- DUTs shall apply the parameter condition specified in 7.7.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (S-MN) and SgNB cell (SN) overlap -- The coverage of T-gNB cell (T-MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform Inter-Master Node Handover (Without SN Change) procedure -- Core or Core emulator (5GC): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 link procedural flows and content, and NG-U UP contents - -### 2.3.1.55.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB, SgNB and T-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for MgNB, SgNB and T-gNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and/or Service Request procedure specified in NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell (S-MN) and SgNB cell (SN) -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB (S-MN) and SgNB (SN) has been successfully completed according to NR C-Plane profile specification - -### 2.3.1.55.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Perform the Xn part of Inter-Master Node Handover (without SN Change) Procedure as described in step 2 of Section 2.4.1.14.4 -3. Stop data transfer as described in step 3 in Section 2.4.1.14.4 -4. Perform data transfer in both directions as described in step 4 of Section 2.4.1.14.4 -5. Observe the Protocol Analyzer NG, Xn and F1 logs and Test UE or UE emulator logs - -### 2.3.1.55.5 Expected Results and Log Observation - -#### 2.3.1.55.5.1 Expected Results - -The UE Context Setup Procedure, UE Context Modification Procedure and the UE Context Release Procedure over F1 are successfully completed. - -The Inter-Master Node Handover (Without SN Change) Procedure over F1 is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.55.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.7.1.3/7.7.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB or T-gNB -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB or T-gNB is recorded in the F1 logs - -### 2.3.1.56 SN Initiated SN Change for NR-DC - -#### 2.3.1.56.1 Test Purpose - -The purpose of this test case is to verify that the F1 UE Context Setup, UE Context Modification and UE Context Release Procedure with gNB-CU and gNB-DU from different vendors, triggered with S-NG-RAN initiated Secondary Node Change procedure can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.8.1. This test case is on top of the Xn part of the Secondary Node Change (SN initiated) procedure as described in Section 2.4.1.15. - -#### 2.3.1.56.2 Minimum Requirements - -DUTs: Three gNB CUs (MN-CU, S-SN-CU and T-SN-CU) and three gNB DUs (MN-DU, S-SN-DU and T-SN-DU): - -- DUTs shall apply the parameter condition specified in 7.8.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN), SgNB cell (S-SN) and T-gNB cell (T-SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR-DC: used to perform Secondary Node Change procedure (SN initiated) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol - -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 links procedural flows and content, NG-U UP contents - -### 2.3.1.56.3 Initial Conditions - -Refer to Section 2.3 for F1 related the standard list of initial conditions. Besides refer to Section 2.4 for Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB, SgNB and T-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CUs and gNB-DUs according to the NR C-Plane profile specification [2] for MgNB, SgNB and T-gNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and/or Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- F1 UE Context Setup procedure between S-SN-CU and S-SN-DU, triggered with Secondary Node Addition procedure between the MN and S-SN has been successfully completed according to NR C-Plane profile specification [2] -- Secondary Node is Source gNB (S-SN) at the start of this procedure -- Data transfer between the application test server and Test UE or UE emulator is possible (via NR RATs) - -### 2.3.1.56.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. -2. Perform Secondary Node Change Procedure from Source gNB cell (S-SN) to Target gNB cell (T-SN) as described in step 2 of Section 2.4.1.15.4. -3. Stop data transfer as described in step 3 in Section 2.4.1.15.4. -4. Perform data transfer in both directions as described in step 4 Section 2.4.1.15.4. -5. Observe the Protocol Analyzer F1, NG and Xn logs and Test UE or UE emulator logs. - -### 2.3.1.56.5 Expected Results and Log Observation - -#### 2.3.1.56.5.1 Expected Results - -The F1 UE Context Setup, UE Context Modification and UE Context Release Procedure are successfully completed. - -The Secondary Node Change procedure is successfully completed. - -Data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.56.5.2 Log Observation - -F1 and Xn logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 7.8.1.3/7.8.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB or T-gNB -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB or T-gNB is recorded in the F1 logs - -## 2.3.1.57 MN initiated SN Change - -### 2.3.1.57.1 Test Purpose - -The purpose of this test case is to verify that the F1 UE Context Setup, UE Context Modification and UE Context Release Procedure with gNB-CU and gNB-DU from different vendors, triggered with M-NG-RAN initiated Secondary Node Change procedure, can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.8.2. This test case is on top of the Xn part of the MN initiated SN Change procedure described in Section 2.4.1.18. - -### 2.3.1.57.2 Minimum Requirements - -DUTs: Three gNB-CUs (MN-CU, S-SN-CU, T-SN-CU) and three gNB-DUs (MN-DU, S-SN-DU, T-SN-DU): - -- DUTs shall apply the parameter condition specified in 7.8.2 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN), SgNB cell (S-SN) and T-gNB cell (T-SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR-DC: used to perform Secondary Node Change procedure (MN initiated) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 links procedural flows and content, NG-U UP content - -### 2.3.1.57.3 Initial Conditions - -Refer to Section 2.3 for F1 related the standard list of initial conditions. Besides refer to Section 2.4 for Xn related list of initial conditions. The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB, SgNB and T-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CUs and gNB-DUs according to the NR C-Plane profile specification [2] for MgNB, SgNB and T-gNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and/or Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell - -- F1 UE Context Setup procedure between S-SN-CU and S-SN-DU, triggered with Secondary Node Addition procedure between the MN and S-SN has been successfully completed according to NR C-Plane profile specification [2] -- Secondary Node is Source gNB (S-SN) at the start of this procedure -- Data transfer between the application test server and Test UE or UE emulator is possible (via NR RAT's) - -#### 2.3.1.57.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator as described in step 1 of Section 2.4.1.18.4 -2. Perform Secondary Node Change Procedure from Source gNB cell (S-SN) to Target gNB cell (T-SN) as described in step 2 of Section 2.4.1.18.4 -3. Stop data transfer as described in step 3 of Section 2.4.1.18.4 -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds as described in step 4 of Section 2.4.1.18.4 -5. Observe the Protocol Analyzer F1, NG and Xn logs and Test UE or UE emulator logs. - -#### 2.3.1.57.5 Expected Results and Log Observation - -##### 2.3.1.57.5.1 Expected Results - -The F1 UE Context Setup, UE Context Modification and UE Context Release Procedure are successfully completed. - -The Secondary Node Change procedure is successfully completed. - -Data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.57.5.2 Log Observation - -F1 and Xn logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 7.8.2.3/7.8.2.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB or T-gNB -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB or T-gNB is recorded in the F1 logs - -### 2.3.1.58 Full Reconfiguration (SN initiated) - -#### 2.3.1.58.1 Test Purpose - -The purpose of this test case is to verify that the Full Reconfiguration procedure (SN initiated) received by gNB-CU leads to correct interworking between gNB-CU and gNB-DU from different vendors, confirming to the NR C-Plane profile specification [2] Section 5.6.22. - -#### 2.3.1.58.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.22 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator used to perform en-gNB initiated Full Reconfiguration procedure -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform Full Reconfiguration procedure (SN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe both X2 and F1 procedural flows and content -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -#### 2.3.1.58.3 Initial Conditions - -- Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. -- The following list of initial conditions are applicable for this specific test case: -- EN-DC X2 Setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -#### 2.3.1.58.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.2.1.33.4. -2. Perform Full Reconfiguration procedure (SN initiated) as described in step 2 in Section 2.2.1.33.4. -3. Stop data transfer as described in step 3 in Section 2.2.1.33.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.33.4. - -5. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs. - -### 2.3.1.58.5 Expected Results and Log Observation - -#### 2.3.1.58.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The Full Reconfiguration procedure (SN initiated) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.58.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.22.3/5.6.22.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.59 Change of QCI (MN initiated) - -#### 2.3.1.59.1 Test Purpose - -The purpose of this test case is to verify that the eNB node initiated modify QCI (and/or ARP) of the SN terminated split bearer procedure with eNB and en-gNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 5.6.23. - -This test case is on top of the X2 part of the Change of QCI (MN initiated) procedure described in Section 2.2.1.38. - -#### 2.3.1.59.2 Minimum Requirements - -DUTs: Single eNB and single en-gNB. - -- DUTs shall apply parameter condition specified in 5.6.23 of the NR C-Plane profile specification [2] -- The coverage of eNB cell (MN) overlaps with en-gNB cell (SN) - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and EN-DC: used to perform MN initiated Secondary Node Modification -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UE (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and content - -### 2.3.1.59.3 Initial Conditions - -Refer to Section 2.2 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.3.1.59.4 Procedures - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator using an E-RAB from an existing LTE bearer -2. Perform change of QCI (MN initiated) procedure as described in step 2 in Section 2.2.1.38.4 -3. Stop data transfer as described in step 3 in Section 2.2.1.38.4 -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.38.4 -5. Observe the Protocol Analyzer F1 and Test UE or UE emulator logs - -### 2.3.1.59.5 Expected Results and Log Observation - -#### 2.3.1.59.5.1 Expected Results - -The change of QCI procedure (MN initiated) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.59.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.23.3/5.6.23.4. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the U-Plane data transmission. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “SGNB MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the C-Plane: - - Check that step 2 QCI in the IE “E-UTRAN QoS” in the IE “DRB To Be Modified List” included in the message “UE CONTEXT MODIFICATION REQUEST” performs correctly -- Regarding the downlink U-Plane data generated in step1, after step 2 and in step 4: - - Check that the data is flowing using the new QCI in step 4 - -- Regarding the uplink U-Plane data generated in step 1, after step 2 and in step 4: - - Check that the data is flowing using the new QCI in step 4 - -### 2.3.1.60 Security Key change (MN initiated) for EN-DC - -#### 2.3.1.60.1 Test Purpose - -The purpose of this test case is to verify that the Security Key change procedure (MN initiated) for EN-DC received by gNB-CU leads to correct interworking between gNB-CU and gNB-DU from different vendors, confirming to the NR C-Plane profile specification [2] Section 5.6.5. - -#### 2.3.1.60.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.5 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator used to perform Security Key change (MN initiated) procedure -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform Security Key change procedure (MN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe both X2 and F1 procedural flows and content -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -#### 2.3.1.60.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 Setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -#### 2.3.1.60.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.2.1.18.4. - -2. Perform Security Key change procedure (MN initiated) as described in step 2 in Section 2.2.1.18.4. -3. Stop data transfer as described in step 3 in Section 2.2.1.18.4. -4. Perform data transfer in both directions as describe in step 4 in Section 2.2.1.18.4. -5. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs. - -### 2.3.1.60.5 Expected Results and Log Observation - -#### 2.3.1.60.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The Security Key change procedure (MN initiated) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.60.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.5.3/5.6.5.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- After step 2 the updated security key is applied in UE: - - An example of how to observe the updated security key is to check the UE emulator log. The exact method to observe the updated security key is out of scope of this specification. -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.61 UL Configuration Update Procedure (SN initiated) - -#### 2.3.1.61.1 Test Purpose - -The purpose of this test case is to verify that the UL Configuration Update procedure (SN initiated) received by gNB-CU leads to correct interworking between gNB-CU and gNB-DU from different vendors, confirming to the NR C-Plane profile specification [2] Section 5.6.9. - -#### 2.3.1.61.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.9 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator used to perform en-gNB initiated UL Configuration Update procedure - -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform UL Configuration Update procedure (SN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe both X2 and F1 procedural flows and content -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -### 2.3.1.61.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 Setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.3.1.61.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.2.1.22.4. -2. Perform UL Configuration Update procedure (SN initiated) as described in step 2 in Section 2.2.1.22.4. -3. Stop data transfer as described in step 3 in Section 2.2.1.22.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.22.4. -5. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs. - -### 2.3.1.61.5 Expected Results and Log Observation - -#### 2.3.1.61.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The UL Configuration Update procedure (SN initiated) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.61.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.9.3/5.6.9.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be 'successful with remarks'. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.62 Void - -### 2.3.1.63 RRC connection re-establishment (inter gNB-CU) - -#### 2.3.1.63.1 Test Purpose - -The purpose of this test case is to verify that the RRC connection re-establishment procedure between gNB-CU and gNB-DU from different vendors, can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 6.10.4. This test case is on top of the Xn part of the RRC connection re-establishment (inter gNB-CU) procedure described in Section 2.4.1.19. - -#### 2.3.1.63.2 Minimum Requirements - -DUTs: Two gNBs, each with a single gNB-CU and single gNB-DU. A Target gNB (TgNB-CU and TgNB-DU) and Source gNB (SgNB-CU and SgNB-DU): - -- DUTs shall apply the parameter condition specified in 6.10.4 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform RRC connection re-establishment -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn and F1 link procedural flows and content, as well as NG-U UP content - -#### 2.3.1.63.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions and to Section 2.4 the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the TgNB and SgNB according to the NR C-Plane profile specification [2] -- The F1 Setup procedure has been successfully completed between the TgNB-CU and TgNB-DU as well as between SgNB-CU and SgNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of SgNB-DU cell - -- Data transfer between the application test server and Test UE or UE emulator is possible - -#### 2.3.1.63.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Perform the RRC connection re-establishment procedure as described in step 2 and 3 in Section 2.4.1.19.4. - -Note: the intention of this step is to perform not only the Xn part of the RRC connection re-establishment Procedure but also trigger to perform the F1 signaling, that is UE UL/DL RRC Message Transfer procedure, UE Context Setup Procedure and UE Context Modification Procedure between SgNB-CU and SgNB-DU and between TgNB-CU and TgNB-DU. - -3. Stop data transfer between the Application Test Server and Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds -5. Observe the Protocol Analyzer NG, Xn and F1 logs and Test UE or UE emulator logs - -#### 2.3.1.63.5 Expected Results and Log Observation - -##### 2.3.1.63.5.1 Expected Results - -The UE UL/DL RRC Message Transfer procedure, UE Context Setup Procedure and UE Context Modification Procedure over F1 are successfully completed. - -The RRC connection re-establishment procedure over F1 is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.63.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 6.10.4.3 and 6.10.4.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1 and after step 3 and in step 5: - - All U-Plane data recorded in the NG and F1 logs is correctly received by the Test UE or UE emulator and the Application Test Server, respectively. - -#### 2.3.1.64 gNB-CU initiated UE Context Modification (UE AMBR (for UL) modification) - -##### 2.3.1.64.1 Test Purpose - -The purpose of this test case is to verify that the gNB-CU initiated UE Context Modification (UE AMBR (for UL) modification) procedure can be successfully completed between gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] Section 6.3.1.7. - -### 2.3.1.64.2 Minimum Requirements - -DUTs: single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in Section 6.3.1.7 of the NR C-Plane profile specification [2]. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to perform UE Context Modification procedure for UE AMBR (for UL) modification. -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol. -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc.) and provide application layer processing on the network side. -- Protocol Analyzer: used to record and observe F1 procedural flows and contents. - -### 2.3.1.64.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- The F1 setup procedure has been successfully completed between gNB-CU and gNB-DU according to the NR C-Plane profile specification [2]. -- Test UE or UE emulator has registered to the network, ie, the registration procedure specified in NR C-Plane profile specification [2] Section 6.1.2 has been successfully completed. -- Test UE or UE emulator is within the coverage area of the PCell. -- The service request procedure, as specified in NR C-Plane profile specification [2] Section 6.1.1, is successfully performed, a DRBs is established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible. - -### 2.3.1.64.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. -2. Perform the gNB-CU initiated UE context modification procedure for UE AMBR (for UL) modification. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Trigger from Core or Core emulator (5GC capabilities) to send a new UE AMBR for UL for this Test UE or UE emulator. -3. Stop the data transfer in both directions between Application Test Server and the Test UE or UE emulator. - 4. Perform data transfer in both directions between the Application Test Server and Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the UE context was modified. For example, in this test case the UE UL transmission rate should be less than or equal to UE AMBR given by AMF. - -5. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs. - -### 2.3.1.64.5 Expected Results and Log Observation - -#### 2.3.1.64.5.1 Expected Results - -The F1 UE Context Modification Procedure for UE AMBR (for UL) modification is performed successfully. - -Data transfer is possible using the new UE AMBR in UL. - -The uplink data transmitted by UE is limited by the UE AMBR given by AMF. - -#### 2.3.1.64.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.3.1.7/6.3.1.7.1. - -If any of the following listed IEs is observed in F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator and the Application Test Server, respectively. - -### 2.3.1.65 Inter gNB Handover for SA - -#### 2.3.1.65.1 Test Purpose - -The purpose of this test case is to verify that the Inter gNB Handover for SA procedure received by gNB-CU leads to correct interworking between gNB-CU and gNB-DU from different vendors, confirming to the NR C-Plane profile specification [2] Section 6.4.1. - -#### 2.3.1.65.2 Minimum Requirements - -DUTs: Two gNBs (Each gNB with Single gNB-CU and single gNB-DU): - -- DUTs shall apply the parameter condition specified in 6.4.1 of the NR C-Plane profile specification [2] -- The coverage of SgNB cell and TgNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to perform Inter gNB Handover procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -#### 2.3.1.65.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the SgNB and TgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both SgNB and TgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the SgNB cell -- Data transfer between the Application Test Server and Test UE or UE emulator is possible - -#### 2.3.1.65.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.2.4. -2. Perform Inter gNB Handover procedure as described in step 2 in Section 2.4.1.2.4. -3. Stop data transfer as described in step 3 in Section 2.4.1.2.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.2.4. -5. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -#### 2.3.1.65.5 Expected Results and Log Observation - -##### 2.3.1.65.5.1 Expected Results - -The UE Context Modification, UE Context Setup, and UE Context Release procedure is successfully completed. - -The Inter gNB Handover procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.65.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 6.4.1.3/6.4.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via SgNB or TgNB -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via SgNB or TgNB is recorded in the F1 logs - -### 2.3.1.66 S-NG-RAN node Initiated SN modification without MN involvement - -#### 2.3.1.66.1 SRB3 supported - -##### 2.3.1.66.1.1 Intra gNB-DU PSCell Change using SRB3 - -###### 2.3.1.66.1.1.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Intra gNB-DU PSCell Change using SRB3)) procedure with gNB-CU and gNB-DU from different vendors using F1 UE Context Modification procedure can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.3.2.1. This test case is on top of the Xn part of the S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Intra gNB-DU PSCell Change using SRB3)) procedure described in Section 2.4.1.6.2.1. - -###### 2.3.1.66.1.1.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply the parameter condition specified in 7.2.3 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell and SgNB cells overlap. -- SgNB has at least 2 Cells configured and in operation. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Intra gNB-DU PSCell Change using SRB3)) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol. -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side. -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content. - -###### 2.3.1.66.1.1.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB. -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed. -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell. -- Data transfer between the Application Test Server and Test UE or UE emulator is possible. -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification. - -### 2.3.1.66.1.1.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.6.2.1.4 -2. Perform the Intra gNB-DU PSCell Change using SRB3 procedure as described in step 2 in Section 2.4.1.6.2.1.4. -3. Stop the data transfer between the Application Test server and Test UE or UE emulator. -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.6.2.1.4 -5. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -### 2.3.1.66.1.1.5 Expected Results and Log Observation - -#### 2.3.1.66.1.1.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Intra gNB-DU PSCell Change using SRB3)) procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.66.1.1.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.3.2.1.3/7.2.3.2.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs. - -### 2.3.1.66.1.2 Inter gNB-DU PSCell Change using SRB3 - -#### 2.3.1.66.1.2.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Inter gNB-DU PSCell Change using SRB3)) procedure with gNB-CU and gNB-DU from different vendors using F1 UE Context Setup and UE Context Modification procedure can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.3.2.2. This test case is on top of the Xn part of the S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Inter gNB-DU PSCell Change using SRB3)) procedure described in Section 2.4.1.6.2.2. - -#### 2.3.1.66.1.2.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN), (SgNB-CU, Source SgNB-DU and Target SgNB-DU – SN): - -- DUTs shall apply the parameter condition specified in 7.2.3/7.2.3.2 of the NR C-Plane profile specification [2] -- SgNB has at least 2 Cells configured to Source SgNB-DU and Target SgNB-DU and in operation -- The cells of the source and target SgNB-DUs overlap as well as the cell(s) of the MgNB-DU - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Inter gNB-DU PSCell Change using SRB3)) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content - -### 2.3.1.66.1.2.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the Application Test Server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification - -### 2.3.1.66.1.2.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.6.2.2.4 -2. Perform the Inter gNB-DU PSCell Change using SRB3 procedure as described in step 2 in Section 2.4.1.6.2.2.4 -3. Stop the data transfer between the Application Test server and Test UE or UE emulator -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.6.2.2.4 -5. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs - -### 2.3.1.66.1.2.5 Expected Results and Log Observation - -#### 2.3.1.66.1.2.5.1 Expected Results - -The F1 UE Context Setup, UE Context Modification and UE Context Release procedure are successfully completed. - -The S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Inter gNB-DU PSCell Change using SRB3)) procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -### 2.3.1.66.1.2.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.3.2.2.3/7.2.3.2.2.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs - -### 2.3.1.66.1.3 Measurement Gap Coordination for per FR2 gap (without MN involvement) Procedure (SN initiated) - -#### 2.3.1.66.1.3.1 Test Purpose - -The purpose of this test case is to verify that the Measurement Gap Coordination for per FR2 gap (without MN involvement) procedure (SN initiated) with gNB-CU and gNB-DU from different vendors by applying the UE Context Modification procedure on the F1 interface can be successfully completed, conforming to the NR C-plane profile specification [2] section 5.6.8a. - -#### 2.3.1.66.1.3.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.8a of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap -- The en-gNB configures at least one FR2 cell to act as a candidate for UE measurement. - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator: used to perform Measurement Gap Coordination for per FR2 gap (without MN involvement) procedure (SN initiated) -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Measurement Gap Coordination for per FR2 gap (without MN involvement) procedure (SN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both X2 and F1 procedural flows and content - -### 2.3.1.66.1.3.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB, including the configuration of SRB3, has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -### 2.3.1.66.1.3.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Perform Measurement Gap Coordination for per FR2 gap (without MN involvement) procedure (SN initiated) - - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - - - a. The gNB-CU receives *F1AP: UL RRC Message Transfer* from UE (NR Measurement Report) via the gNB-DU indicating serving SN cell quality degradation. This NR Measurement Report may trigger the gNB-CU to initiate Measurement Gap Coordination for per FR2 gap. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the gNB-DU cell. In this specific case, the gNB-DU cell can start off with low attenuation applied which is subsequently increased to a level that triggers the UE to send the NR measurement report to the gNB-CU (via the gNB-DU). -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds -5. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs. - -### 2.3.1.66.1.3.5 Expected Results and Log Observation - -#### 2.3.1.66.1.3.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The Measurement Gap Coordination for per FR2 gap (without MN involvement) procedure (SN initiated) is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.66.1.3.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.8a.1/5.6.8a.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.66.2 SRB3 not supported - -#### 2.3.1.66.2.1 SN Modification – SCell(s) Addition / Release - -##### 2.3.1.66.2.1.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification without MN involvement (SRB3 not supported (SCell(s) Addition / Release)) procedure with gNB-CU and gNB-DU from different vendors using the F1 UE Context Modification procedure can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.3.1.1. - -##### 2.3.1.66.2.1.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply the parameter condition specified in 7.2.3/7.2.3.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell and SgNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated SN modification without MN involvement (SRB3 not supported (SN Modification – SCell(s) Addition / Release)) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol. -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side. -- Protocol Analyzer: used to record and observe both Xn and F1 procedural flows and content. - -##### 2.3.1.66.2.1.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB. - -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed. -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell. -- Data transfer between the Application Test Server and Test UE or UE emulator is possible. -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2]. - -#### 2.3.1.66.2.1.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.6.1.1.4. -2. Perform the S-NG-RAN node initiated SN modification without MN involvement (SRB3 not supported (SN Modification – SCell Addition)) as described in step 2 in Section 2.4.1.6.1.1.4. -3. Stop the data transfer between the Application Test server and Test UE or UE emulator. -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.6.1.1.4. -5. Perform S-NG-RAN node initiated SN modification without MN involvement (SRB3 not supported (SN Modification – SCell Release)) as described in step 5 in Section 2.4.1.6.1.1.4. -6. Stop the data transfer between the Application Test server and Test UE or UE emulator. -7. Perform data transfer in both directions as described in step 7 in Section 2.4.1.6.1.1.4. -8. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -#### 2.3.1.66.2.1.5 Expected Results and Log Observation - -##### 2.3.1.66.2.1.5.1 Expected Results - -The UE Context Modification procedure(s) is(are) successfully completed for either of the below listed use cases: - -- SCell Addition (step 2) -- SCell Release (step 5) - -The S-NG-RAN node initiated SN modification without MN involvement (SRB3 not supported (SCell(s) Addition / Release)) procedure is successfully completed. All the data generated is correctly received by Test UE or UE emulator after the addition and release procedures. - -The test case is considered as being successful if any of the above listed use cases are successfully completed. - -##### 2.3.1.66.2.1.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.3.1.1.3/7.2.3.1.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - -- o All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs. -- Regarding the downlink U-Plane data generated after step 5 and in step 7: - - o All U-Plane data recorded in the F1 log is correctly received by the Test UE or UE emulator via MgNB or SgNB. -- Regarding the uplink U-Plane data generated after step 5 and in step 7: - - o All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs. - -### 2.3.1.67 M-NG-RAN node initiated S-NG-RAN Node Release without keeping UE - -#### 2.3.1.67.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated S-NG-RAN node Release without keeping UE procedure with gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] Section 7.3.1. This test case is on top of the Xn part of the M-NG-RAN node initiated S-NG-RAN node Release without keeping UE procedure described in Section 2.4.1.7. - -#### 2.3.1.67.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU, SgNB-CU and SgNB-DU): - -- DUTs shall apply the parameter condition specified in 7.3.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell and SgNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated S-NG-RAN node Release without keeping UE -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe Xn and F1 procedural flows and content -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -#### 2.3.1.67.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification - -- Data transfer between the Application Test Server and Test UE or UE emulator is possible - -#### 2.3.1.67.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.7.4. -2. Perform M-NG-RAN node initiated S-NG-RAN node Release without keeping UE as described in step 2 in Section 2.4.1.7.4. -3. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -#### 2.3.1.67.5 Expected Results and Log Observation - -##### 2.3.1.67.5.1 Expected Results - -The UE Context Modification procedure and UE Context Release procedure are successfully completed. - -The M-NG-RAN node initiated S-NG-RAN node Release without keeping UE procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.67.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.3.1.3/7.3.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB. -- Regarding the uplink U-Plane data generated in step 1: - - o All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs - -#### 2.3.1.68 M-NG-RAN node initiated S-NG-RAN Node Release with keeping UE - -##### 2.3.1.68.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated S-NG-RAN node Release with keeping UE procedure with gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] Section 7.3.2. This test case is on top of the Xn part of the M-NG-RAN node initiated S-NG-RAN node Release with keeping UE procedure described in Section 2.4.1.8. - -##### 2.3.1.68.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU, SgNB-CU and SgNB-DU): - -- DUTs shall apply the parameter condition specified in 7.3.2 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell and SgNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated S-NG-RAN node Release with keeping UE -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe Xn and F1 procedural flows and content -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -### 2.3.1.68.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification -- Data transfer between the Application Test Server and Test UE or UE emulator is possible - -### 2.3.1.68.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.4.1.8.4. -2. Perform M-NG-RAN node initiated S-NG-RAN node Release with keeping UE as described in step 2 in Section 2.4.1.8.4. -3. Stop the data transfer between the Application Test server and Test UE or UE emulator. -4. Perform data transfer in both directions as described in step 4 in Section 2.4.1.8.4 -5. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -### 2.3.1.68.5 Expected Results and Log Observation - -#### 2.3.1.68.5.1 Expected Results - -The UE Context Modification procedure and UE Context Release procedure are successfully completed. - -The M-NG-RAN node initiated S-NG-RAN node Release with keeping UE procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.68.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.3.2.3/7.3.2.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB. -- Regarding the uplink U-Plane data generated in step 1 and after 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs - -## 2.3.1.69 S-NG-RAN node initiated S-NG-RAN Node Release - -### 2.3.1.69.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated S-NG-RAN node Release procedure with gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] Section 7.3.3. This test case is on top of the Xn part of the S-NG-RAN node initiated S-NG-RAN node Release procedure described in Section 2.4.1.9. - -### 2.3.1.69.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU, SgNB-CU and SgNB-DU): - -- DUTs shall apply the parameter condition specified in 7.3.3 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell and SgNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated S-NG-RAN node Release -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe Xn and F1 procedural flows and content -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -### 2.3.1.69.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell - -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification -- Data transfer between the Application Test Server and Test UE or UE emulator is possible - -#### 2.3.1.69.4 Procedure - -There are two options for this procedure, as shown in Figure 7.3.3.1-1 in the NR C-Plane profile specification [2]. - -OPT 1 (with keeping UE case) is below: - -1. Perform data transfer in both directions as described in step 1 of OPT 1 in Section 2.4.1.9.4. -2. Perform S-NG-RAN node initiated S-NG-RAN node Release as described in step 2 of OPT 1 in Section 2.4.1.9.4. -3. Stop the data transfer between the Application Test server and Test UE or UE emulator. -4. Perform data transfer in both directions as described in step 4 of OPT 1 in Section 2.4.1.9.4 -5. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -OPT 2 (without keeping UE case) is below: - -1. Perform data transfer in both directions as described in step 1 of OPT 2 in Section 2.4.1.9.4. -2. Perform S-NG-RAN node initiated S-NG-RAN node Release as described in step 2 of OPT 2 in Section 2.4.1.9.4. -3. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -#### 2.3.1.69.5 Expected Results and Log Observation - -##### 2.3.1.69.5.1 Expected Results - -The UE Context Modification procedure and UE Context Release procedure are successfully completed. - -The S-NG-RAN node initiated S-NG-RAN node Release procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.69.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.3.3.3/7.3.3.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -OPT 1 (with keeping UE case) is below: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB. -- Regarding the uplink U-Plane data generated in step 1 and after 2 and in step 4: - -- o All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs - -OPT 2 (without keeping UE case) is below: - -- Regarding the downlink U-Plane data generated in step 1: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via MgNB or SgNB. -- Regarding the uplink U-Plane data generated in step 1: - - o All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the F1 logs - -### 2.3.1.70 PDU Session Establishment - -#### 2.3.1.70.1 Test Purpose - -The purpose of this test case is to verify that the establishment of an additional PDU Session using the F1 UE Context Modification procedure can be performed successfully between gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] Section 6.3.3.1 - -#### 2.3.1.70.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 6.3.3.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to perform an additional PDU Session Establishment procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the core network, ie, 5GC side -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -#### 2.3.1.70.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- The F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure specified in NR C-Plane profile specification [2] Section 6.1.2 has been successfully completed -- Test UE or UE emulator is within the coverage area of the PCell -- The service request procedure, as specified in NR C-Plane profile specification [2] Section 6.1.1, is successfully performed, a PDU Session with at least one DRB is established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible - -#### 2.3.1.70.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Initiate UE Context Modification procedure for DRB setup by establishment of an additional PDU session - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Add another PDU Session with at least one DRB by requesting another service, eg, Video streaming, resulting in a PDU Session Resource Setup -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the UE context was modified. - -5. Observe the Protocol Analyzer F1 logs - -### 2.3.1.70.5 Expected Results and Log Observation - -#### 2.3.1.70.5.1 Expected Results - -The PDU Session Establishment procedure is completed successfully. - -The F1 UE Context Modification procedure for DRB setup to UE is performed successfully, and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible using the newly established DRB. - -#### 2.3.1.70.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Section 6.3.3.1.1/6.3.3.1.2. - -If any of the following listed IEs is observed in the F1 log - -- “DRB Failed To Setup List” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1 and after step 2 and in step 4: - -All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator and the Application Test Server, respectively. - -### 2.3.1.71 RRC Inactive to RRC Connected, Inter gNB-CU - -#### 2.3.1.71.1 Test Purpose - -The purpose of this test case is to verify that the state change procedure from RRC inactive to RRC connected between two pairs of gNB-CUs and gNB-DUs from different vendors, can be successfully completed, performed with the UE Context Setup procedure and with the UE Context Modification procedure, conforming to the NR C-Plane profile specification [2] Section 6.9.3. This TC expands the TC specified in 2.4.1.20 with the F1 interface conformance. - -#### 2.3.1.71.2 Minimum Requirements - -DUTs: A Receiving gNB and a Last Serving gNB, each with a single gNB-CU and a gNB-DU from different vendors: - -- DUTs shall apply the parameter condition specified in 6.9.3 of the NR C-Plane profile specification [2] -- The coverages of the two gNBs cells overlap each other. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to trigger the RRC state transition procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the core network, ie, 5GC side -- Protocol Analyzer: used to record and observe both F1 and Xn procedural flows and content - -### **2.3.1.71.3 Initial Conditions** - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU of both the Receiving gNB and the Last Serving gNB, according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and the Service Request procedure specified in NR C-Plane profile specification [2] Section 6.1.1 has been successfully completed. At least one DRB is established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible. -- Data transfer in the uplink and downlink direction towards/ and from the Test UE or UE emulator is omitted for a period of time. The UE or UE emulator is in RRC inactive state. - -The UE or UE emulator is moved from the cell of the Last Serving gNB to the cell of the Receiving gNB. That can be done eg, by increasing the attenuation of the Last Serving gNB cell and by lowering the attenuation of the Receiving gNB cell. - -### **2.3.1.71.4 Procedure** - -1. Perform RRC state change procedure as specified in section 2.4.1.20 -2. Stop data transfer between the Application Test Server and the Test UE or UE emulator -3. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds before the RRC connection times out. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the RRC connection was established - -4. Observe the Protocol Analyzer F1 and Xn logs and Test UE or UE emulator logs - -### **2.3.1.71.5 Expected Results and Log Observation** - -#### **2.3.1.71.5.1 Expected Results** - -The RRC Inactive to RRC Connected state change procedure with the UE Context Modification and the UE Context Setup procedures between gNB-CUs and gNB-DUs of the Receiving gNB and of the Last Serving gNB, respectively, are completed successfully. Data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible. - -#### **2.3.1.71.5.2 Log Observation** - -F1 and Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 6.9.3.3/6.9.3.4. - -If any of the following listed IEs is observed in the F1 log - -- “SRB failed to setup list” in “UE CONTEXT SETUP RESPONSE” - -- “DRB failed to setup list” in “UE CONTEXT SETUP RESPONSE” -- “SCell failed to setup list” in “UE CONTEXT SETUP RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE”, -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE”, - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and step 3: - - All U-Plane data which is recorded in the F1 logs is correctly received by the Test UE or emulated UE -- Regarding the uplink U-Plane data generated in step 1 and step 3: - - All U-Plane data transmitted by the Test UE or emulated UE is recorded in the F1 logs - -## 2.3.1.72 Measurement ID Coordination (MN initiated) - -### 2.3.1.72.1 Test Purpose - -The purpose of this test case is to verify that the Measurement ID Coordination (MN initiated) using the F1 UE Context Modification procedure can be successfully completed between gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] section 5.6.24. This test case is on top of the X2 part of the Measurement ID Coordination (MN initiated) procedure as described in section 2.2.1.39. - -### 2.3.1.72.2 Minimum Requirements - -DUTs: Single en-gNB-CU and single en-gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.24 of NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator: used to perform Measurement ID Coordination (MN initiated) procedure -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Measurement ID Coordination procedure (MN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both X2 and F1 procedural flows and content - -### 2.3.1.72.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] - -- Test UE or UE emulator has registered to the network, ie, Attach procedure and service request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.3.1.72.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.2.1.39.4. -2. Perform Measurement ID Coordination procedure (MN initiated) as described in step 2 in Section 2.2.1.39.4. -3. Stop data transfer as described in step 3 in Section 2.2.1.39.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.39.4. -5. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs. - -#### 2.3.1.72.5 Expected Results and Log observation - -##### 2.3.1.72.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The Measurement ID Coordination procedure (MN initiated) is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.72.5.2 Log observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.24.3/5.6.24.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -#### 2.3.1.73 New QoS Flow with Explicit NAS Signalling - -##### 2.3.1.73.1 Test Purpose - -The purpose of this test case is to verify that the addition of new QoS flow with explicit NAS signalling using the F1 UE Context Modification procedure can be successfully completed between gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] section 6.3.3.2. - -##### 2.3.1.73.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 6.3.3.2 of NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to perform the addition of new QoS flow with explicit NAS signalling procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both F1 procedural flows and content - -### 2.3.1.73.3 Initial Conditions - -Refer to Section 2.3 for F1 related standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure specified in NR C-Plane profile specification [2] Section 6.1.2 has been successfully completed -- Test UE or UE emulator is within the coverage area of the PCell -- The service request procedure, as specified in NR C-Plane profile specification [2] Section 6.1.1, is successfully performed, a DRB is established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible - -### 2.3.1.73.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Initiate UE Context Modification procedure for establishing a new DRB to add a new QoS flow - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Add another DRB to UE to add a new QoS flow by requesting another service, eg, Video streaming, resulting in a PDU Session Resource Modification - 3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. -- Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the UE context was modified. -5. Observe the Protocol Analyzer F1 logs - -### 2.3.1.73.5 Expected Results and Log Observation - -#### 2.3.1.73.5.1 Expected Results - -The addition of new QoS flow with explicit NAS signalling procedure is completed successfully. - -The F1 UE Context Modification procedure for DRB setup to UE is performed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible using the newly established DRB. - -### 2.3.1.73.5.2 Log observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 6.3.3.2.1/6.3.3.2.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “DRB Failed To Setup List” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1 (through existing DRBs) and after step 2 and in step 4 (through existing and new DRBs): - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator and the Application Test Server, respectively. - -### 2.3.1.74 PCell change (Intra MN) (MN initiated) - -#### 2.3.1.74.1 Test Purpose - -The purpose of this test case is to verify that the PCell change (Intra MN) (MN initiated) procedure with gNB-CU and gNB-DU from different vendors by applying the UE Context Modification procedure on the F1 interface can be successfully completed, conforming to the NR C-plane profile specification [2] section 5.6.1. This test case is on top of the X2 part of the PCell change (Intra MN) (MN initiated) procedure described in Section 2.2.1.14. - -#### 2.3.1.74.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.1 of the NR C-Plane profile specification [2] -- eNB has at least 2 Cells configured and in operation -- The coverage of Intra-eNB source cell and en-gNB cell overlap -- The coverage of Intra-eNB target cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator: used to perform PCell change (Intra MN) (MN initiated) procedure -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform PCell change (Intra MN) (MN initiated) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc.) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both X2 and F1 procedural flows and content - -#### 2.3.1.74.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -#### 2.3.1.74.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.2.1.14.4. -2. Perform PCell change (Intra MN) (MN initiated) procedure as described in step 2 in Section 2.2.1.14.4. -3. Stop data transfer as described in step 3 in Section 2.2.1.14.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.14.4. -5. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs. - -#### 2.3.1.74.5 Expected Results and Log Observation - -##### 2.3.1.74.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The PCell change (Intra MN) (MN initiated) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.74.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.1.3/5.6.1.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “DRB Failed to be Modified List” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.75 DRB ID change/Security Key change (SN initiated) - -#### 2.3.1.75.1 Test Purpose - -The purpose of this test case is to verify that the SN (en-gNB) initiated DRB ID change/Security Key change procedure with gNB-CU and gNB-DU from different vendors by applying the UE Context Modification procedure on the F1 interface can be successfully completed, conforming to the NR C-plane profile specification [2] section 5.6.21. This test case is on top of the X2 part of the SN (en-gNB) initiated DRB ID change procedure described in Section 2.2.1.40. - -#### 2.3.1.75.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.21 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator: used to perform SN (en-gNB) initiated DRB ID change/Security Key change procedure -- Test UE or UE emulator which is capable of supporting for both LTE and NR: used to perform SN (en-gNB) initiated DRB ID change/Security Key change procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc.) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both X2 and F1 procedural flows and content - -#### 2.3.1.75.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -#### 2.3.1.75.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.2.1.40.4. -2. Perform SN initiated DRB ID change/Security Key change procedure as described in step 2 in Section 2.2.1.40.4. -3. Stop data transfer as described in step 3 in Section 2.2.1.40.4. - -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.40.4. -5. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs. - -### 2.3.1.75.5 Expected Results and Log Observation - -#### 2.3.1.75.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The SN initiated DRB ID change/Security Key change procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.75.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.21.3/5.6.21.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “DRB Failed to be Setup List” in “UE CONTEXT MODIFICATION RESPONSE” -- “DRB Failed to be Modified List” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.76 Measurement ID Coordination (SN initiated) - -#### 2.3.1.76.1 Test Purpose - -The purpose of this test case is to verify that the Measurement ID Coordination (SN initiated) using the F1 UE Context Modification procedure can be successfully completed between gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] section 5.6.25. This test case is on top of the X2 part of the Measurement ID Coordination (SN initiated) procedure as described in section 2.2.1.41. - -#### 2.3.1.76.2 Minimum Requirements - -DUTs: Single en-gNB-CU and single en-gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.25 of NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator: used to perform Measurement ID Coordination (SN initiated) procedure -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Measurement ID Coordination procedure (SN initiated) - -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both X2 and F1 procedural flows and content - -### 2.3.1.76.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and service request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.3.1.76.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.2.1.41.4. -2. Perform Measurement ID Coordination procedure (SN initiated) as described in step 2 in Section 2.2.1.41.4. -3. Stop data transfer as described in step 3 in Section 2.2.1.41.4. -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.41.4. -5. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs. - -### 2.3.1.76.5 Expected Results and Log observation - -#### 2.3.1.76.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The Measurement ID Coordination procedure (SN initiated) is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.76.5.2 Log observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.25.3/5.6.25.4. - -If any of the following listed IEs is observed in the F1 logs: - -- ‘‘Criticality Diagnostics’’ in ‘‘UE CONTEXT MODIFICATION RESPONSE’’ - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - -- o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.77 Release of QoS Flow with Explicit Signalling - -#### 2.3.1.77.1 Test Purpose - -The purpose of this test case is to verify that the release of QoS flow with explicit signalling using the F1 UE Context Modification procedure can be successfully completed between gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] section 6.3.3.3. - -#### 2.3.1.77.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 6.3.3.3 of NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to perform the release of QoS flow with explicit signalling procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both F1 procedural flows and content - -#### 2.3.1.77.3 Initial Conditions - -Refer to Section 2.3 for F1 related standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure specified in NR C-Plane profile specification [2] Section 6.1.2 has been successfully completed -- Test UE or UE emulator is within the coverage area of the PCell -- The service request procedure, as specified in NR C-Plane profile specification [2] Section 6.1.1, is successfully performed, at least two DRBs with one QoS flow each are established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible - -#### 2.3.1.77.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. -2. Initiate UE Context Modification procedure for releasing an existing DRB. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Remove one of at least two established DRBs from UE to release an existing QoS flow, by releasing one service, eg, Video streaming, resulting in a PDU Session Resource Modification. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator. -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the UE context was modified. - -5. Observe the Protocol Analyzer F1 logs - -### 2.3.1.77.5 Expected Results and Log Observation - -#### 2.3.1.77.5.1 Expected Results - -The release of QoS flow with explicit signalling procedure is completed successfully. - -The F1 UE Context Modification procedure for DRB release to UE is performed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible using the remaining DRB. - -#### 2.3.1.77.5.2 Log observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 6.3.3.3.1/6.3.3.3.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “DRB Failed to be Modified List” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator and the Application Test Server, respectively. - -### 2.3.1.78 PDU session establishment after signalling-only connection - -#### 2.3.1.78.1 Test Purpose - -The purpose of this test case is to verify that the PDU session establishment after signalling-only connection using the F1 UE Context Setup and UE Context Modification procedure can be successfully completed between gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] section 6.12. - -#### 2.3.1.78.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 6.12 of NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to perform the PDU session establishment after signalling-only connection procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -- Protocol Analyzer: used to record and observe both F1 procedural flows and content - -### 2.3.1.78.3 Initial Conditions - -Refer to Section 2.3 for F1 related standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure specified in NR C-Plane profile specification [2] Section 6.1.2 has been successfully completed - -### 2.3.1.78.4 Procedure - -1. Initiate PDU session establishment procedure from UE or UE emulator. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Perform UL activity from UE side by streaming video, browsing internet, etc. -2. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the UE context was created. - -3. Observe the Protocol Analyzer F1 logs. - -### 2.3.1.78.5 Expected Results and Log Observation - -#### 2.3.1.78.5.1 Expected Results - -The F1 procedure as specified in the NR C-Plane profile specification [2] Section 6.12.1 to create a PDU session after signalling-only connection is successfully completed. - -#### 2.3.1.78.5.2 Log observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 6.12.1/6.12.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “SRB failed to setup list” in “UE CONTEXT SETUP RESPONSE” -- “DRB failed to setup list” in “UE CONTEXT SETUP RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 2: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator and the Application Test Server, respectively. - -## 2.3.1.79 Inter-Master Node Handover with SN Change for NR-DC - -### 2.3.1.79.1 Test Purpose - -The purpose of this test case is to verify that the F1 UE Context Setup, UE Context Modification and UE Context Release procedures with gNB-CU and gNB-DU from different vendors, triggered with an Inter-Master Node Handover (with SN Change) procedure can be successfully completed, conforming to the NR C-Plane profile specification [2] section 7.7.2. This test case is on top of the Xn part of Inter-Master Node Handover (with SN Change) procedure as described in section 2.4.1.23. - -### 2.3.1.79.2 Minimum Requirements - -DUTs: Four gNB CUs (S-MN-CU, S-SN-CU, T-SN-CU and T-MN-CU) and Four gNB DUs (S-MN-DU, S-SN-DU, T-SN-DU and T-MN-DU): - -- DUTs shall apply the parameter condition specified in 7.7.2 of the NR C-Plane profile specification [2] -- The coverage of Source Master gNB cell (S-MN) overlaps with Target Master gNB cell (T-MN) and Source Secondary gNB cell (S-SN) -- The coverage of Target Master gNB cell (T-MN) overlaps with Target Secondary gNB cell (T-SN) -- The coverage of Source Secondary gNB cell (S-SN) do not overlap with Target Secondary gNB cell (T-SN) - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform Inter-Master Node Handover (with SN Change) procedure -- Core or Core emulator (5GC): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn and F1 link procedural flows and content, and NG-U UP contents - -### 2.3.1.79.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the S-MN, T-MN, S-SN and T-SN according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for S-MN, T-MN, S-SN and T-SN -- Test UE or UE emulator has registered to the network, ie, Registration procedure and/or Service Request procedure specified in NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the Source Master gNB cell (S-MN) and Source Secondary gNB cell (S-SN) -- Data transfer between the application test server and Test UE or UE emulator is possible -- F1 UE Context Setup procedure between S-SN-CU and S-SN-DU, triggered with Secondary Node Addition procedure between the S-MN and S-SN has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.3.1.79.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. -2. Perform the Xn part of Inter-Master Node Handover (with SN Change) procedure as described in step 2 of Section 2.4.1.23.4. - -Note: the intention of this step is to perform not only the Xn part of the Inter-Master Node Handover (with SN change) procedure but also trigger to perform the F1 signaling, that is UE Context Setup, UE Context Modification and UE Context Release procedures with gNB-CUs and gNB-DUs. - -3. Stop data transfer as described in step 3 in Section 2.4.1.23.4. -4. Perform data transfer in both directions as described in step 4 of Section 2.4.1.23.4. -5. Observe the Protocol Analyzer NG, Xn and F1 logs and Test UE or UE emulator logs. - -#### 2.3.1.79.5 Expected Results and Log Observation - -##### 2.3.1.79.5.1 Expected Results - -The UE Context Setup procedure, UE Context Modification procedure and the UE Context Release procedure over F1 are successfully completed. - -The Inter-Master Node Handover (with SN Change) procedure over F1 is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.79.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.7.2.3/7.7.2.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “SRB failed to setup list” in “UE CONTEXT SETUP RESPONSE” -- “DRB failed to setup list” in “UE CONTEXT SETUP RESPONSE” -- “SCell failed to setup list” in “UE CONTEXT SETUP RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT SETUP RESPONSE”, -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via S-MN or T-MN or S-SN or T-SN -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via S-MN or T-MN or S-SN or T-SN is recorded in the F1 logs - -### 2.3.1.80 gNB-DU initiated UE Context Modification (DRB to be modified) - -#### 2.3.1.80.1 Test Purpose - -The purpose of this test case is to verify that the gNB-DU initiated UE Context Modification procedure to modify DRB for a UE can be performed successfully between gNB-DU and gNB-CU from different vendors, conforming to the NR C-Plane profile specification [2] section 6.3.2.2. - -#### 2.3.1.80.2 Minimum Requirements - -DUTs: Single gNB-DU and single gNB-CU, PCell and SCell(s) are available and configured for PDCP Carrier Aggregation duplication: - -- DUTs shall apply the parameter condition specified in 6.3.2.2 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of PDCP Carrier Aggregation duplication: used to perform UE Context Modification procedure for DRB modification -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the core network, ie, 5GC side -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -#### 2.3.1.80.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- The F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and the Service Request procedure specified in NR C-Plane profile specification [2] Section 6.1.1 has been successfully completed. At least one DRB is established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible. -- Test UE or UE emulator is within the coverage area of the PCell and SCell - -#### 2.3.1.80.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. -2. Initiate gNB-DU initiated UE Context Modification procedure for DRB modification - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator, PCell and SCell. In this specific case, the PCell and SCell can start off with low attenuation applied which is subsequently increased to a level which can trigger the PDCP CA duplication procedure with the PCell and SCell. -3. Stop the data transfer between the Application Test Server and the Test UE or UE emulator. - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the UE context was modified. - -5. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs. - -### 2.3.1.80.5 Expected Results and Log Observation - -#### 2.3.1.80.5.1 Expected Results - -The F1 gNB-DU initiated UE Context Modification procedure for DRB modification to UE is performed successfully. - -#### 2.3.1.80.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.3.2.2/6.3.2.2.1. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION CONFIRM” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or emulated UE. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs. - -### 2.3.1.81 Addition of SN terminated split bearer (MN initiated) - -#### 2.3.1.81.1 Test Purpose - -The purpose of this test case is to verify that the Addition of SN terminated split bearer (MN initiated) procedure with gNB-CU and gNB-DU from different vendors, confirming to the NR C-Plane profile specification [2] Section 5.6.10. This test case is on top of the X2 part of the Addition of SN terminated split bearer (MN initiated) procedure described in Section 2.2.1.23. - -#### 2.3.1.81.2 Minimum Requirements - -DUTs: Single en-gNB-CU and single en-gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.10 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Secondary Node Addition procedure and Secondary Node Modification procedure (MN initiated) -- eNB or eNB emulator: used to perform Secondary Node Modification procedure (MN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and contents and S1-U UP contents - -### 2.3.1.81.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB (MN) and en-gNB (SN) according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] - -### 2.3.1.81.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.2.1.23.4 -2. Perform Secondary Node Modification with addition of SN terminated split bearer procedure (MN initiated) as described in step 2 in Section 2.2.1.23.4 -3. Stop data transfer as described in step 3 in Section 2.2.1.23.4 -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.23.4 -5. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs - -### 2.3.1.81.5 Expected Results and Log Observation - -#### 2.3.1.81.5.1 Expected Results - -The UE Context Modification procedures are successfully completed. - -The Secondary Node Modification procedure (MN initiated) with addition of SN terminated split bearer procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.81.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.10.3/5.6.10.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT - -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -## 2.3.1.82 Removal of SN terminated split bearer (MN initiated) - -### 2.3.1.82.1 Test Purpose - -The purpose of this test case is to verify that the Removal of SN terminated split bearer (MN initiated) procedure with gNB-CU and gNB-DU from different vendors, confirming to the NR C-Plane profile specification [2] Section 5.6.11. This test case is on top of the X2 part of the Addition of SN terminated split bearer (MN initiated) procedure described in Section 2.2.1.24. - -### 2.3.1.82.2 Minimum Requirements - -DUTs: Single en-gNB-CU and single en-gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.11 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Secondary Node Addition procedure and Secondary Node Modification procedure (MN initiated) -- eNB or eNB emulator: used to perform Secondary Node Modification procedure (MN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and contents and S1-U UP contents - -### 2.3.1.82.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB (MN) and en-gNB (SN) according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure, which including at least two SN terminated split bearers between the eNB and en-gNB, has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] - -### 2.3.1.82.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.2.1.24.4 -2. Perform Secondary Node Modification with removal of SN terminated split bearer procedure (MN initiated) as described in step 2 in Section 2.2.1.24.4 -3. Stop data transfer as described in step 3 in Section 2.2.1.24.4 -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.24.4 -5. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs - -### 2.3.1.82.5 Expected Results and Log Observation - -#### 2.3.1.82.5.1 Expected Results - -The UE Context Modification procedures are successfully completed. - -The Secondary Node Modification procedure (MN initiated) with removal of SN terminated split bearer procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.82.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.11.3/5.6.11.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.83 Registration update without Follow-on request - -#### 2.3.1.83.1 Test Purpose - -The purpose of this test case is to verify that the UE Registration Update without Follow-on procedure can be performed successfully with gNB-CU and gNB-DU from different vendors, conforming to the NR C-Plane profile specification [2] section 6.1.3.2 - -#### 2.3.1.83.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 6.1.3.2 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol - -- Protocol Analyzer: used to record and observe F1 procedural flows and content - -### 2.3.1.83.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- The F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Initial Registration procedure specified in NR C-Plane profile specification [2] Section 6.1.3.2 has been successfully completed - -### 2.3.1.83.4 Procedure - -1. Initiate Registration update without Follow-on request Initial Registration Request procedure from UE or UE emulator - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification - -- a. Let the registration timer in the UE (emulator) expire with no user plane traffic activity, to test the Registration Update without Follow-on procedure - -2. Observe the Protocol Analyzer F1 logs - -### 2.3.1.83.5 Expected Results and Log Observation - -#### 2.3.1.83.5.1 Expected Results - -The F1 procedure as specified in the NR C-Plane profile specification [2] Section 6.1.32.2.1 is successfully completed. - -#### 2.3.1.83.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.1.3.2.1/6.1.3.2.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -### 2.3.1.84 Measurement Gap Coordination Procedure (MN initiated) - -#### 2.3.1.84.1 Test Purpose - -The purpose of this test case is to verify that the Measurement Gap Coordination procedure (MN initiated) with gNB-CU and gNB-DU from different vendors by applying the UE Context Modification procedure on the F1 interface can be successfully completed, conforming to the NR C-plane profile specification [2] section 5.6.6. This test case is on top of the X2 part of the Measurement Gap Coordination procedure (MN initiated) described in Section 2.2.1.19. - -#### 2.3.1.84.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.6 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator: used to perform Measurement Gap Coordination procedure (MN initiated) -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Measurement Gap Coordination procedure (MN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both X2 and F1 procedural flows and content - -#### 2.3.1.84.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -#### 2.3.1.84.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.2.1.19.4 -2. Perform Measurement Gap Coordination procedure (MN initiated) as described in step 2 in Section 2.2.1.19.4 -3. Stop data transfer as described in step 3 in Section 2.2.1.19.4 -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.19.4 -5. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs - -#### 2.3.1.84.5 Expected Results and Log Observation - -##### 2.3.1.84.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The Measurement Gap Coordination procedure (MN initiated) is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.84.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.6.3/5.6.6.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -### 2.3.1.85 Measurement Gap Coordination for per FR1 or per UE gap Procedure (SN initiated) - -#### 2.3.1.85.1 Test Purpose - -The purpose of this test case is to verify that the Measurement Gap Coordination for per FR1 or per UE gap Procedure (SN initiated) with gNB-CU and gNB-DU from different vendors by applying the UE Context Modification procedure on the F1 interface can be successfully completed, conforming to the NR C-plane profile specification [2] section 5.6.7. This test case is on top of the X2 part of the Measurement Gap Coordination for per FR1 or per UE gap Procedure (SN initiated) described in Section 2.2.1.20. - -#### 2.3.1.85.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.7 of the NR C-Plane profile specification [2] -- The coverage of eNB cell and en-gNB cell overlap - -Testing tools which are required for this test scenario: - -- eNB or eNB emulator: used to perform Measurement Gap Coordination for per FR1 or per UE gap Procedure (SN initiated) -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Measurement Gap Coordination for per FR1 or per UE gap Procedure (SN initiated) -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both X2 and F1 procedural flows and content - -#### 2.3.1.85.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] - -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the Application Test Server and Test UE or UE emulator is possible (via the LTE and NR RATs) - -#### 2.3.1.85.4 Procedure - -1. Perform data transfer in both directions as described in step 1 in Section 2.2.1.20.4 -2. Perform Measurement Gap Coordination for per FR1 or per UE gap Procedure (SN initiated) as described in step 2 in Section 2.2.1.20.4 -3. Stop data transfer as described in step 3 in Section 2.2.1.20.4 -4. Perform data transfer in both directions as described in step 4 in Section 2.2.1.20.4 -5. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs - -#### 2.3.1.85.5 Expected Results and Log Observation - -##### 2.3.1.85.5.1 Expected Results - -The UE Context Modification procedure is successfully completed. - -The Measurement Gap Coordination for per FR1 or per UE gap Procedure (SN initiated) is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.85.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.7.3/5.6.7.4. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs - -#### 2.3.1.86 Intra gNB-DU Handover with L1/L2 Triggered Mobility (LTM) - -##### 2.3.1.86.1 Test Purpose - -The purpose of this test case is to verify that the Intra gNB-DU handover with L1/L2 triggered mobility between gNB-CU and gNB-DU from different vendors can successfully be completed, conforming to the NR C-Plane profile specification [2] Section 6.5.4. - -### 2.3.1.86.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU, - -- DUTs shall apply the parameter condition specified in 6.5.4 of the NR C-Plane profile specification [2] -- The coverage of source cell and target cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to perform Intra gNB-DU, Inter Cell Handover. -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol. -- Protocol Analyzer: used to record and observe F1 procedural flows and content -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -### 2.3.1.86.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 Setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and the Service Request procedure specified in NR C-Plane profile specification [2] Section 6.1.1 has been successfully completed. At least one DRB is established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible. -- Test UE or UE emulator is within the coverage area of the source cell - -### 2.3.1.86.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. -2. Initiate inter cell mobility involving UE Context Modification procedures as preparation for L1/L2 triggered cell switch from the serving to the target cell. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Move the Test UE or UE emulator from the coverage area of the serving Cell under the coverage area of the target Cell eg, by making use of variable attenuators. In this specific case, the serving cell can start with low attenuation, the target cell can start off with high attenuation applied, which is subsequently changed up to a level which can trigger the UE Context Modification Procedure with preparation of the target cell for L1/L2 triggered mobility. The attenuation of the serving cell can be further increased until a level is reached that triggers the Cell Switch procedure towards the UE. - 3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. -- Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the UE context was modified. -5. Observe the Protocol Analyzer F1 logs - -### 2.3.1.86.5 Expected Results and Log Observation - -#### 2.3.1.86.5.1 Expected Results - -The Intra gNB-DU Handover with L1/L2 trigger procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -#### 2.3.1.86.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 6.5.4.1/6.5.4.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1 and after step 2 and in step 4: - -All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator and the Application Test Server, respectively - -### 2.3.1.87 Intra gNB-DU PSCell Change using SRB3 for RRC Reconfiguration - -#### 2.3.1.87.1 Test Purpose - -The purpose of this test case is to verify that an Intra gNB-DU PSCell Change using SRB3 for RRC Reconfiguration procedure received by gNB-CU leads to correct interworking between gNB-CU and gNB-DU from different vendors using F1 UE Context Modification procedures; conforming to the NR C-Plane profile specification [2] Section 5.6.19. - -#### 2.3.1.87.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply the parameter condition specified in 5.6.19 of the NR C-Plane profile specification [2] -- en-gNB has at least 2 Cells configured and in operation - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Intra gNB-DU PSCell Change using SRB3 for RRC Reconfiguration procedure -- eNB or eNB emulator: used to perform Intra gNB-DU PSCell Change using SRB3 for RRC Reconfiguration procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe F1 procedural flow and content - -#### 2.3.1.87.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 Setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cells -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cells -- Data transfer between the Application Test Server and Test UE or UE emulator is possible - -#### 2.3.1.87.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Perform the Intra gNB-DU PSCell Change using SRB3 for RRC Reconfiguration - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT - -- a. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the source PSCell and the target PSCell in en-gNB simultaneously. In this specific case, the source PSCell can start off with low attenuation applied which is subsequently increased. At the same time, the target PSCell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the Intra gNB-DU PSCell Change procedure. -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds -5. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs - -#### 2.3.1.87.5 Expected Results and Log Observation - -##### 2.3.1.87.5.1 Expected Results - -The UL RRC Message Transfer is successfully transmitted. - -The UE Context Modification procedures over F1 are successfully completed. - -The Intra gNB-DU PSCell Change using SRB3 for RRC Reconfiguration procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.87.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.19.1/5.6.19.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “SCell Failed to Setup List” in “UE CONTEXT MODIFICATION RESPONSE” -- DRB Failed to be Modified List in “UE CONTEXT MODIFICATION RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -The result of the handling where gNB-DU sends "Resource Coordination Transfer Container" to the gNB-CU in UE CONTEXT MODIFICATION RESPONSE need not to be verified here because the X2 part verification is out scope of this test case. Instead, it can be verified in Section 2.2.1.16. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs. - -### 2.3.1.88 Inter gNB-DU PSCell Change using SRB3 for RRC Reconfiguration - -#### 2.3.1.88.1 Test Purpose - -The purpose of this test case is to verify that an Inter gNB-DU PSCell Change using SRB3 for RRC Reconfiguration procedure received by gNB-CU leads to correct interworking between gNB-CU and gNB-DUs from different vendors using F1 UE Context Setup, F1 UE Context Modification and F1 UE Context Release procedures; conforming to the NR C-Plane profile specification [2] Section 5.6.18. - -#### 2.3.1.88.2 Minimum Requirements - -DUTs: Single gNB-CU and two gNB-DUs (Source gNB-DU, Target gNB-DU): - -- DUTs shall apply the parameter condition specified in 5.6.18 of the NR C-Plane profile specification [2] -- en-gNB has at least 2 Cells configured and are in operation - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to perform Inter gNB-DU PSCell Change using SRB3 for RRC Reconfiguration procedure -- eNB or eNB emulator: used to perform Inter gNB-DU PSCell Change using SRB3 for RRC Reconfiguration procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe F1 procedural flow and content - -#### 2.3.1.88.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DUs according to the NR C-Plane profile specification [2] - -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cells -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Data transfer between the Application Test Server and Test UE or UE emulator is possible - -#### 2.3.1.88.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Perform the Inter gNB-DU PSCell Change using SRB3 for RRC Reconfiguration - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT - -- a. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the source PSCell and the target PSCell in en-gNB simultaneously. In this specific case, the source PSCell can start off with low attenuation applied which is subsequently increased. At the same time, the target PSCell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the Inter gNB-DU PSCell Change procedure. -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds -5. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs - -#### 2.3.1.88.5 Expected Results and Log Observation - -##### 2.3.1.88.5.1 Expected Results - -The UL RRC Message Transfer is successfully transmitted. - -The UE Context Setup procedure for target gNB-DU, UE Context Modification and UE Context Release procedures for source gNB-DU over F1 are successfully completed. - -The Inter gNB-DU PSCell Change using SRB3 for RRC Reconfiguration procedure is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.3.1.88.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 5.6.18.1/5.6.18.2. - -If any of the following listed IEs is observed in the F1 logs: - -- “Criticality Diagnostics” in “UE CONTEXT MODIFICATION RESPONSE” -- “SRB Failed to Setup List” in “UE CONTEXT SETUP RESPONSE” -- “DRB Failed to Setup List” in “UE CONTEXT SETUP RESPONSE” -- “SCell Failed to Setup List” in “UE CONTEXT SETUP RESPONSE” -- “Criticality Diagnostics” in “UE CONTEXT RELEASE COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -The result of the handling where gNB-DU sends “Resource Coordination Transfer Container” to the gNB-CU in UE CONTEXT SETUP RESPONSE need not to be verified here because the X2 part verification is out of scope for this test case. Instead, it can be verified in Section 2.2.1.16. - -F1 logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the F1 logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the F1 logs. - -## 2.3.2 F1 U-Plane IOT Test Cases - -### 2.3.2.1 Node behaviour of the corresponding node for EN-DC with RLC-AM and/or RLC-UM - -#### 2.3.2.1.1 Test Purpose - -The purpose of this test case is to verify that the behaviour of the corresponding node procedure for EN-DC with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.1.1. - -Note: The test cases for the behaviour of the corresponding node sending DDDS when events lost packet detection and stop scheduling for the data bearer occur are included in the chapter 2.3.2.7. - -#### 2.3.2.1.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of eNB cell (MN) and en-gNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- eNB or eNB emulator: used to perform Secondary Node Addition (Option 3x) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and contents - -#### 2.3.2.1.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the MN (eNB) cell and SN (en-gNB) cell - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been successfully completed -- Secondary Node Addition (Option 3x) procedure between the eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transmission has not been performed via the NR RAT, eg, keeping Option 3x with NR radio quality low enough - -Note: This test case is used to verify that the eNB does not discard any of its buffered packets in events such as Radio Link Outage over the LTE RAT unless it receives discard indication from the higher layers or from the en-gNB hosting NR PDCP, such as the buffer discard indication from the en-gNB. This initial condition ensures that en-gNB does not send the buffer discard indication to the eNB. - -#### 2.3.2.1.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for gNB-DU to buffer the downlink data. The exact data rate that is generated is not specified, but it is up to gNB-DU vendor implementation. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). -2. Trigger radio link outage on the gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To move the Test UE or UE emulator away from the coverage of the gNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the gNB cell. In this specific case, the gNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. - -3. Trigger radio link resume on the gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To move the Test UE or UE emulator back within the coverage of the gNB-DU. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the eNB cell. In this specific case, the eNB cell can start off with high attenuation applied which is subsequently decreased to a level which can trigger radio link resume condition. - -4. Stop data transfer from the Application Test Server to the Test UE or UE emulator. -5. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs. - -#### 2.3.2.1.5 Expected Results and Log Observation - -##### 2.3.2.1.5.1 Expected Results - -The behaviour of gNB-DU is aligned with the requirement specified in Section 4.1.1.1 of NR U-Plane profile specification [3]. - -##### 2.3.2.1.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.1.1 and the following should be observed: - -- gNB-DU sends DDDS message which includes the *Cause Value IE* with value '1', '3' or '4' to gNB-CU after step 2 -- gNB-DU sends DDDS message which includes the *Cause Value IE* with value '2', '5' or '6' to gNB-CU after step 3 -- Note: these are to confirm if the Radio Link Outage operation has been performed. -- Logs recorded in the Test UE or UE emulator are aligned with the NR U-Plane profile specification [3] Section 4.1.1.1 and the following should be observed: - - After the end of step 2 and before the start of step 3, Test UE or UE emulator does NOT receive any data which is transmitted from gNB-DU in step 1 - - After step 3, Test UE or UE emulator receives all the data which is transmitted from gNB-DU before triggering Radio Link Outage in step 1 - -## 2.3.2.2 Node behaviour of the corresponding node for SA with RLC-AM and/or RLC-UM - -### 2.3.2.2.1 Test Purpose - -The purpose of this test case is to verify that the behaviour of the corresponding node procedure for SA with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.1.1. - -Note: The test cases for the behaviour of the corresponding node sending DDDS when events lost packet detection and stop scheduling for the data bearer occur are included in the chapter 2.3.2.8. - -### 2.3.2.2.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe F1 procedural flows and contents - -### 2.3.2.2.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed - -#### 2.3.2.2.4 Procedure - -1. Perform data transfer in both directions the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for gNB-DU to buffer the downlink data. The exact data rate that is generated is not specified, but it is up to gNB-DU vendor implementation. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). -2. Trigger radio link outage on the gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To move the Test UE or UE emulator away from the coverage of the gNB-DU. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the eNB cell. In this specific case, the eNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. - -3. Trigger radio link resume on the gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To move the Test UE or UE emulator back within the coverage of the gNB-DU. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the eNB cell. In this specific case, the eNB cell can start off with high attenuation applied which is subsequently decreased to a level which can trigger radio link resume condition. - -4. Stop data transfer from the Application Test Server to the Test UE or UE emulator. -5. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs. - -#### 2.3.2.2.5 Expected Results and Log Observation - -##### 2.3.2.1.5.1 Expected Results - -The behaviour of gNB-DU is aligned with the requirement specified in Section 4.1.1.1 of NR U-Plane profile specification [3]. - -##### 2.3.2.2.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.1.1 and the following should be observed: - -- gNB-DU sends DDDS message which includes the Cause Value IE with value '1', '3' or '4' to gNB-CU after step 2 -- gNB-DU sends DDDS message which includes the Cause Value IE with value '2', '5' or '6' to gNB-DU after step 3 - -Note: these are to confirm if the Radio Link Outage operation has been performed. - -- Logs recorded in the Test UE or UE emulator are aligned with the NR U-Plane profile specification [3] Section 4.1.1.1 and the following should be observed: -- After the end of step 2 and before the start of step 3, Test UE or UE emulator does NOT receive any data which is transmitted from gNB-DU in step 1 -- After step 3, Test UE or UE emulator receives all the data which is transmitted from gNB-DU before triggering Radio Link Outage in step 1 - -### 2.3.2.3 Node behaviour of the corresponding node for NR-DC with RLC-AM and/or RLC-UM - -#### 2.3.2.3.1 Test Purpose - -The purpose of this test case is to verify that the behaviour of the corresponding node procedure for NR-DC with gNB-CU and gNB-DU from different vendors can be successfully completed, conforming to the NR U-Plane profile specification [3] Section 4.1.1.1. - -Note: The test cases for the behaviour of the corresponding node sending DDDS when events lost packet detection and stop scheduling for the data bearer occur are included in the chapter 2.3.2.9. - -#### 2.3.2.3.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap each other - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn and F1 procedural flows and contents - -#### 2.3.2.3.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transmission has not been performed via the MgNB, eg, keeping SN terminated split bearer with NR radio quality low enough - -Note: This test case is used to verify that the MgNB does not discard any of its buffered packets in events such as Radio Link Outage over the MgNB unless it receives discard indication from the higher layers or from the SgNB hosting NR PDCP, such as the buffer discard indication from the SgNB. This initial condition ensures that the SgNB does not send the buffer discard indication to the MgNB. - -### 2.3.2.3.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for MgNB to buffer the downlink data. The exact data rate that is generated is not specified, but it is up to MgNB node vendor implementation. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). -2. Trigger radio link outage on the MgNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To move the Test UE or UE emulator away from the coverage of the MgNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the MgNB cell. In this specific case, the MgNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. - -3. Trigger radio link resume on the MgNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To move the Test UE or UE emulator back within the coverage of the MgNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the MgNB cell. In this specific case, the MgNB cell can start off with high attenuation applied which is subsequently decreased to a level which can trigger radio link resume condition. - -4. Stop data transfer from the Application Test Server to the Test UE or UE emulator. -5. Perform data transfer from the Application Test Server to the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for MgNB to buffer the downlink data. The exact data rate that is generated is not specified, but it is up to MgNB node vendor implementation. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). -6. Trigger radio link outage on the SgNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To move the Test UE or UE emulator away from the coverage of the SgNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the SgNB cell. In this specific case, the SgNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. - -7. Trigger radio link resume on the SgNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To move the Test UE or UE emulator back within the coverage of the SgNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the SgNB cell. In this specific case, the SgNB cell can start off with high attenuation applied which is subsequently decreased to a level which can trigger radio link resume condition. - -8. Stop data transfer from the Application Test Server to the Test UE or UE emulator. -9. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -### 2.3.2.3.5 Expected Results and Log Observation - -#### 2.3.2.3.5.1 Expected Results - -The behaviour of the corresponding node is aligned with the requirement specified in Section 4.1.1.1 of NR U-Plane profile specification [3]. - -#### 2.3.2.3.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.1.1 and the following should be observed: - -- MgNB-DU sends DDDS message which includes the *Cause Value IE* with value '1', '3' or '4' to the MgNB-CU after step 2 -- MgNB-DU sends DDDS message which includes the *Cause Value IE* with value '2', '5' or '6' to the MgNB-CU after step 3 - -Note: these are to confirm if the Radio Link Outage of MgNB operation has been performed. - -- Logs recorded in the Test UE or UE emulator are aligned with the NR U-Plane profile specification [3] Section 4.1.1.1 and the following should be observed: - - After the end of step 2 and before the start of step 3, Test UE or UE emulator does NOT receive any data which is transmitted from MgNB-DU in step 1 - - After step 3, Test UE or UE emulator receives all the data which is transmitted from MgNB-DU before triggering Radio Link Outage in step 1 - - After the end of step 2 and before the start of step 3, MgNB does NOT receive any data which is transmitted from SgNB in step 1 - - After step 3, MgNB receives all the data which is transmitted from SgNB before triggering Radio Link Outage in step 1 - - SgNB-DU sends DDDS message which includes the *Cause Value IE* with value '1', '3' or '4' to the SgNB-CU after step 6 - - SgNB-DU sends DDDS message which includes the *Cause Value IE* with value '2', '5' or '6' to the SgNB-CU after step 7 - -Note: these are to confirm if the Radio Link Outage of SgNB operation has been performed. - -- Logs recorded in the Test UE or UE emulator are aligned with the NR U-Plane profile specification [3] Section 4.1.1.1 and the following should be observed: - - After the end of step 6 and before the start of step 7, Test UE or UE emulator does NOT receive any data which is transmitted from SgNB-DU in step 5 - - After step 7, Test UE or UE emulator receives all the data which is transmitted from SgNB-DU before triggering Radio Link Outage in step 5 - -### 2.3.2.4 General for Elements for the NR user plane protocols for EN-DC with RLC-AM and/or RLC-UM - -#### 2.3.2.4.1 Test Purpose - -The purpose of this test case is to verify that the general behaviour for EN-DC with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.1. - -#### 2.3.2.4.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of eNB cell (MN) cell and en-gNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- eNB or eNB emulator: used to perform Secondary Node Addition (Option 3x) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and contents -- Network Impairment Emulator: used to discard selected packets transmitted via the X2 link - -#### 2.3.2.4.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Network Impairment Emulator is physically connected in-line to the F1 link between the gNB-CU and gNB-DU -- EN-DC X2 setup procedure has been successfully completed between the MN (eNB) and SN (en-gNB) according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cell -- Data transmission has not been performed via the MgNB - -Note: the intention of this is to make a condition where any of the optional fields in DDDS has no available value. - -#### 2.3.2.4.4 Procedure - -1. Trigger Secondary Node Addition procedure - -Note: the intention of this step is to have the gNB-DU send DDDS which does not include any of the optional fields as the corresponding value is not yet available. - -2. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator until the end of step 6. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, meaningful to verify that the user plane transmission operates correctly. - -Note: the intention of this step is to make a situation where the values of Highest Transmitted *NR PDCP Sequence Number IE* and Highest Successfully Delivered *NR PDCP Sequence Number IE* in DDDS are valid. - -3. After the Application Test Server starts to transmit downlink data, drop some packets sent from the gNB-CU to gNB-DU via F1 link by using the Network Impairment Emulator inserted in-line in the F1 link - -Note: the intention of this step is to make a situation where the value of *Lost Packet Report IE* is valid. - -4. Trigger the gNB-CU to send Downlink User Data PDU(s) including Retransmission flag IE with '1' to gNB-DU - -Note: the intention of this step is to make a situation where the value of Highest Retransmitted *NR PDCP Sequence Number IE* and Highest Successfully Delivered Retransmitted *NR PDCP Sequence Number IE* is valid. - -The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -5. Trigger radio link outage condition in the gNB-DU at least once - -Note: the intention of this step is to make a situation where the value of *Cause Value IE* is valid. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. To gradually move the Test UE or UE emulator away from the coverage of the en-gNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the en-gNB cell. In this specific case, the en-gNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. - -6. Stop scheduling in the gNB-DU - -Note: the intention of this step is to create a situation where the value of *Final Frame Indication IE* is valid. - -The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -7. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs - -### 2.3.2.4.5 Expected Results and Log Observation - -#### 2.3.2.4.5.1 Expected Results - -The behaviour of gNB-CU and gNB-DU is aligned with the requirement specified in Section 4.1.2.1 of NR U-Plane profile specification [3]. - -#### 2.3.2.4.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.1 and the following should be observed: - -- The DDDSs captured during step 1 have the following IEs with the value '0': - - o Highest Transmitted *NR PDCP SN Ind IE* - - o Highest Delivered *NR PDCP SN Ind IE* - - o Final Frame Indication IE - - o Lost Packet Report IE - - o Highest Retransmitted *NR PDCP SN Ind IE* - - o Highest Delivered Retransmitted *NR PDCP SN Ind IE* - - o Cause Report IE - -- One or more DDDSs captured after the beginning of the step 2 have one or both of the following IEs with the value '1': - - Highest Transmitted NR PDCP SN Ind IE - - Highest Delivered NR PDCP SN Ind IE -- One or more DDDSs captured after the beginning of the step 3 have Lost Packet Report IE with the value '1' -- One or more DDDSs captured after the beginning of the step 4 have one or both of the following IEs with the value '1': - - Highest Retransmitted NR PDCP SN Ind IE - - Highest Delivered Retransmitted NR PDCP SN Ind IE -- One or more DDDSs captured after the beginning of the step 5 have Cause Report IE with the value '1' and Cause value IE with the value '1', '3', or '4' -- One or more DDDSs captured after the beginning of the step 6 have Final Frame Indication IE with the value '1' - -### 2.3.2.5 General for Elements for the NR user plane protocols for SA with RLC-AM and/or RLC-UM - -#### 2.3.2.5.1 Test Purpose - -The purpose of this test case is to verify that the general behaviour for SA with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.1. - -#### 2.3.2.5.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe F1 procedural flows and contents -- Network Impairment Emulator: used to discard selected packets transmitted via the F1 link - -#### 2.3.2.5.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Network Impairment Emulator is physically connected in-line to the F1 link between the gNB-CU and gNB-DU - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed - -#### 2.3.2.5.4 Procedure - -1. Initiate Service Request procedure from UE or UE emulator - -Note: the intention of this step is to have the gNB-DU send DDDS which does not include any of the optional fields as the corresponding value is not yet available. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Initiate data transfer from a UE in CM-IDLE state - -2. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator until the end of step 6. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, meaningful to verify that the user plane transmission operates correctly. - -Note: the intention of this step is to make a situation where the values of *Highest Transmitted NR PDCP Sequence Number IE* and *Highest Successfully Delivered NR PDCP Sequence Number IE* in DDDS are valid. - -3. After the Application Test Server starts to transmit downlink data, drop some packets sent from the gNB-CU to gNB-DU via F1 link by using the Network Impairment Emulator inserted in-line in the F1 link - -Note: the intention of this step is to make a situation where the value of *Lost Packet Report IE* is valid. - -4. Trigger the gNB-CU to send Downlink User Data PDU(s) including Retransmission flag IE with '1' to gNB-DU - -Note: the intention of this step is to make a situation where the value of *Highest Retransmitted NR PDCP Sequence Number IE* and *Highest Successfully Delivered Retransmitted NR PDCP Sequence Number IE* is valid. - -The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -5. Trigger radio link outage condition in the gNB-DU at least once - -Note: the intention of this step is to make a situation where the value of *Cause Value IE* is valid. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. To gradually move the Test UE or UE emulator away from the coverage of the gNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the gNB cell. In this specific case, the gNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. - -6. Stop scheduling in the gNB-DU - -Note: the intention of this step is to create a situation where the value of *Final Frame Indication IE* is valid. - -The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -7. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs - -### 2.3.2.5.5 Expected Results and Log Observation - -#### 2.3.2.5.5.1 Expected Results - -The behaviour of gNB-CU and gNB-DU is aligned with the requirement specified in Section 4.1.2.1 of NR U-Plane profile specification [3]. - -#### 2.3.2.5.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.1 and the following should be observed: - -- The DDDSs captured during step 1 have the following IEs with the value ‘0’: - - Highest Transmitted NR PDCP SN Ind IE - - Highest Delivered NR PDCP SN Ind IE - - Final Frame Indication IE - - Lost Packet Report IE - - Highest Retransmitted NR PDCP SN Ind IE - - Highest Delivered Retransmitted NR PDCP SN Ind IE - - Cause Report IE -- One or more DDDSs captured after the beginning of the step 2 have one or both of the following IEs with the value ‘1’: - - Highest Transmitted NR PDCP SN Ind IE - - Highest Delivered NR PDCP SN Ind IE -- One or more DDDSs captured after the beginning of the step 3 have *Lost Packet Report IE* with the value ‘1’ -- One or more DDDSs captured after the beginning of the step 4 have one or both of the following IEs with the value ‘1’: - - Highest Retransmitted NR PDCP SN Ind IE - - Highest Delivered Retransmitted NR PDCP SN Ind IE -- One or more DDDSs captured after the beginning of the step 5 have *Cause Report IE* with the value ‘1’ and *Cause value IE* with the value ‘1’, ‘3’, or ‘4’ -- One or more DDDSs captured after the beginning of the step 6 have *Final Frame Indication IE* with the value ‘1’ - -### 2.3.2.6 General for Elements for the NR user plane protocols for NR-DC with RLC-AM and/or RLC-UM - -#### 2.3.2.6.1 Test Purpose - -The purpose of this test case is to verify that the general behaviour for NR-DC with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.1. - -#### 2.3.2.6.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of MgNB cell (MN) cell and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn and F1 procedural flows and contents -- Network Impairment Emulator: used to discard selected packets transmitted via the Xn link - -### 2.3.2.6.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Network Impairment Emulator is physically connected in-line to the F1 link between the gNB-CU and gNB-DU -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transmission has not been performed via the MgNB - -Note: the intention of this is to make a condition where any of the optional fields in DDDS has no available value. - -### 2.3.2.6.4 Procedure - -1. Trigger S-NG-RAN Node Addition procedure - -Note: the intention of this step is to have the SgNB-DU send DDDS which does not include any of the optional fields as the corresponding value is not yet available. - -2. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator until the end of step 6. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, meaningful to verify that the user plane transmission operates correctly. - -Note: the intention of this step is to make a situation where the values of Highest Transmitted NR PDCP Sequence Number IE and Highest Successfully Delivered NR PDCP Sequence Number IE in DDDS are valid. - -3. After the Application Test Server starts to transmit downlink data, drop some packets sent from the SgNB-CU to SgNB-DU via F1 link by using the Network Impairment Emulator inserted in-line in the F1 link - -Note: the intention of this step is to make a situation where the value of Lost Packet Report IE is valid. - -4. Trigger the SgNB-CU to send Downlink User Data PDU(s) including Retransmission flag IE with '1' to SgNB-DU - -Note: the intention of this step is to make a situation where the value of Highest Retransmitted NR PDCP Sequence Number IE and Highest Successfully Delivered Retransmitted NR PDCP Sequence Number IE is valid. - -The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -5. Trigger radio link outage condition in the SgNB-DU at least once - -Note: the intention of this step is to make a situation where the value of Cause Value IE is valid. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. To gradually move the Test UE or UE emulator away from the coverage of the SgNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the SgNB cell. In this specific case, the SgNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. - -6. Stop scheduling in the SgNB-DU - -Note: the intention of this step is to create a situation where the value of Final Frame Indication IE is valid. - -The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -7. Trigger radio link resume on the SgNB-DU. - -8. After the Application Test Server starts to transmit downlink data, drop some packets sent from the MgNB-CU to MgNB-DU via F1 link by using the Network Impairment Emulator inserted in-line in the F1 link - -Note: the intention of this step is to make a situation where the value of *Lost Packet Report IE* is valid. - -9. Trigger the MgNB-CU to send Downlink User Data PDU(s) including *Retransmission flag IE* with '1' to SgNB-DU - -Note: the intention of this step is to make a situation where the value of *Highest Retransmitted NR PDCP Sequence Number IE* and *Highest Successfully Delivered Retransmitted NR PDCP Sequence Number IE* is valid. - -The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -10. Trigger radio link outage condition in the MgNB-DU at least once - -Note: the intention of this step is to make a situation where the value of Cause Value IE is valid. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. To gradually move the Test UE or UE emulator away from the coverage of the MgNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the MgNB cell. In this specific case, the MgNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. - -11. Stop scheduling in the MgNB-DU - -Note: the intention of this step is to create a situation where the value of Final Frame Indication IE is valid. - -The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -12. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs - -### 2.3.2.6.5 Expected Results and Log Observation - -#### 2.3.2.6.5.1 Expected Results - -The behaviour of gNB-CU and gNB-DU is aligned with the requirement specified in Section 4.1.2.1 of NR U-Plane profile specification [3]. - -#### 2.3.2.6.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.1 and the following should be observed: - -- The DDDSs of SgNB-CU captured during step 1 have the following IEs with the value '0': - - o Highest Transmitted NR PDCP SN Ind IE - - o Highest Delivered NR PDCP SN Ind IE - - o Final Frame Indication IE - - o Lost Packet Report IE - - o Highest Retransmitted NR PDCP SN Ind IE - - o Highest Delivered Retransmitted NR PDCP SN Ind IE - - o Cause Report IE -- One or more DDDSs of SgNB-CU captured after the beginning of the step 2 have one or both of the following IEs with the value '1': - - o Highest Transmitted NR PDCP SN Ind IE - - o Highest Delivered NR PDCP SN Ind IE -- One or more DDDSs of SgNB-CU captured after the beginning of the step 3 have *Lost Packet Report IE* with the value '1' -- One or more DDDSs of SgNB-CU captured after the beginning of the step 4 have one or both of the following IEs with the value '1': - - o Highest Retransmitted NR PDCP SN Ind IE - - o Highest Delivered Retransmitted NR PDCP SN Ind IE -- One or more DDDSs of SgNB-CU captured after the beginning of the step 5 have *Cause Report IE* with the value '1' and Cause value IE with the value '1', '3', or '4' -- One or more DDDSs of SgNB-CU captured after the beginning of the step 6 have *Final Frame Indication IE* with the value '1' -- One or more DDDSs of MgNB-CU captured after the beginning of the step 2 have one or both of the following IEs with the value '1': - - o Highest Transmitted NR PDCP SN Ind IE - - o Highest Delivered NR PDCP SN Ind IE -- One or more DDDSs of MgNB-CU captured after the beginning of the step 8 have *Lost Packet Report IE* with the value '1' -- One or more DDDSs of MgNB-CU captured after the beginning of the step 9 have one or both of the following IEs with the value '1': - -- o Highest Retransmitted NR PDCP SN Ind IE - - o Highest Delivered Retransmitted NR PDCP SN Ind IE -- One or more DDDSs of MgNB-CU captured after the beginning of the step 10 have *Cause Report IE* with the value '1' and Cause value IE with the value '1', '3', or '4' -- One or more DDDSs of MgNB-CU captured after the beginning of the step 11 have *Final Frame Indication IE* with the value '1' - -### 2.3.2.7 Report Polling for EN-DC with RLC-AM and/or RLC-UM - -#### 2.3.2.7.1 Test Purpose - -The purpose of this test case is to verify that the Report Polling procedure for EN-DC with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.2. - -#### 2.3.2.7.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of eNB cell (MN) and en-gNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- eNB or eNB emulator: used to perform Secondary Node Addition (Option 3x) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and contents -- Network Impairment Emulator: used to discard selected packets transmitted via the F1 link - -#### 2.3.2.7.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Network Impairment Emulator is physically connected in-line to the F1 link between the gNB-CU and gNB-DU -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] - -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cell -- Secondary Node Addition (Option 3x) procedure between eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.3.2.7.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator until the end of step 5. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, to meaningfully verify that the user plane transmission operates correctly. -2. Send Downlink User Data PDU(s) including *Report polling IE* with '1' from gNB-CU to gNB-DU at least once. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. gNB-CU transmits some data packets to gNB-DU (ie, step 1) - -3. Drop some packets sent from gNB-CU to gNB-DU via F1 link by using the Network Impairment Emulator inserted in-line in the F1 link. - -Note: the intention of this step is to make a situation where “Lost packet detection” occurs in gNB-DU. - -4. Trigger radio link outage condition in the gNB-DU. - -Note: the intention of this step is to make a situation where “Radio link outage” occurs in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To gradually move the Test UE or UE emulator away from the coverage of the gNB-DU. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the gNB-DU cell. In this specific case, the gNB-DU cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. - -5. Trigger radio link resume condition on gNB-DU. - -6. Stop scheduling in the gNB-DU. - -Note: the intention of this step is to make a situation where “Stop scheduling for the data bearer” occurs in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stop downlink data transmission - -7. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs. - -#### 2.3.2.7.5 Expected Results and Log Observation - -##### 2.3.2.7.5.1 Expected Results - -The use of Report Polling function is aligned with the requirement specified in Section 4.1.2.2 of NR U-Plane profile specification [3]. - -### 2.3.2.7.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.2 and the following should be observed: - -- After the beginning of step 2: - - gNB-CU sends gNB-DU one or more Downlink User Data PDU(s) including Report polling IE with the value '1' - - gNB-CU sends gNB-DU DDDS as soon as possible after receiving the corresponding Downlink User Data PDU(s) -- After the beginning of step 3, gNB-DU sends gNB-CU DDDS where following IEs show the dropped packets: - - Start of lost NR-U Sequence Number range IE(s) - - End of lost NR-U Sequence Number range IE(s) -- After the beginning of step 4, gNB-DU sends gNB-CU DDDS including *Cause Value IE* with the value '1', '3' or '4' -- After the beginning of step 6, gNB-DU sends gNB-CU DDDS including *Final Frame Indication IE* with the value '1', and then gNB-DU does not send gNB-CU DDDS including any updated instance of the following IEs - - Highest successfully delivered NR PDCP Sequence Number IE - - Highest transmitted NR PDCP Sequence Number IE - - Highest successfully delivered retransmitted NR PDCP Sequence Number IE - - Highest retransmitted NR PDCP Sequence Number IE - -### 2.3.2.8 Report Polling for SA with RLC-AM and/or RLC-UM - -#### 2.3.2.8.1 Test Purpose - -The purpose of this test case is to verify that the Report Polling procedure for SA with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.2. - -#### 2.3.2.8.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe F1 procedural flows and contents - -- Network Impairment Emulator: used to discard selected packets transmitted via the F1 link - -### 2.3.2.8.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Network Impairment Emulator is physically connected in-line to the F1 link between the gNB-CU and gNB-DU -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed - -### 2.3.2.8.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator until the end of step 5. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, to meaningfully verify that the user plane transmission operates correctly. -2. Send Downlink User Data PDU(s) including *Report polling IE* with '1' from gNB-CU to gNB-DU at least once. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. gNB-CU transmits some data packets to gNB-DU (ie, step 1) - -3. Drop some packets sent from gNB-CU to gNB-DU via F1 link by using the Network Impairment Emulator inserted in-line in the F1 link. - -Note: the intention of this step is to make a situation where “Lost packet detection” occurs in gNB-DU. - -4. Trigger radio link outage condition in the gNB-DU. - -Note: the intention of this step is to make a situation where “Radio link outage” occurs in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To gradually move the Test UE or UE emulator away from the coverage of the gNB-DU. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the gNB-DU cell. In this specific case, the gNB-DU cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. - -5. Trigger radio link resume condition on gNB-DU. - -6. Stop scheduling in the gNB-DU. - -Note: the intention of this step is to make a situation where “Stop scheduling for the data bearer” occurs in gNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stop downlink data transmission - -7. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs. - -### 2.3.2.8.5 Expected Results and Log Observation - -#### 2.3.2.8.5.1 Expected Results - -The use of Report Polling function is aligned with the requirement specified in Section 4.1.2.2 of NR U-Plane profile specification [3]. - -#### 2.3.2.8.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.2 and the following should be observed: - -- After the beginning of step 2: - - gNB-CU sends gNB-DU one or more Downlink User Data PDU(s) including Report polling IE with the value '1' - - gNB-CU sends gNB-DU DDDS as soon as possible after receiving the corresponding Downlink User Data PDU(s) -- After the beginning of step 3, gNB-DU sends gNB-CU DDDS where following IEs show the dropped packets: - - Start of lost NR-U Sequence Number range IE(s) - - End of lost NR-U Sequence Number range IE(s) -- After the beginning of step 4, gNB-DU sends gNB-CU DDDS including *Cause Value IE* with the value '1', '3' or '4' -- After the beginning of step 6, gNB-DU sends gNB-CU DDDS including *Final Frame Indication IE* with the value '1', and then gNB-DU does not send gNB-CU DDDS including any updated instance of the following IEs - - Highest successfully delivered NR PDCP Sequence Number IE - - Highest transmitted NR PDCP Sequence Number IE - - Highest successfully delivered retransmitted NR PDCP Sequence Number IE - - Highest retransmitted NR PDCP Sequence Number IE - -### 2.3.2.9 Report Polling for NR-DC with RLC-AM and/or RLC-UM - -#### 2.3.2.9.1 Test Purpose - -The purpose of this test case is to verify that the Report Polling procedure for NR-DC with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.2. - -#### 2.3.2.9.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. -- The coverage of MgNB cell (MN) cell and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn and F1 procedural flows and contents -- Network Impairment Emulator: used to discard selected packets transmitted via the F1 link - -### 2.3.2.9.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Network Impairment Emulator is physically connected in-line to the F1 link between the gNB-CU and gNB-DU -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.3.2.9.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator until the end of step 5. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, to meaningfully verify that the user plane transmission operates correctly. -2. Send Downlink User Data PDU(s) including *Report polling IE* with '1' from MgNB-CU to MgNB-DU at least once. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. MgNB-CU transmits some data packets to MgNB-DU (ie, step 1) - -3. Drop some packets sent from MgNB-CU to MgNB-DU via F1 link by using the Network Impairment Emulator inserted in-line in the F1 link. - -Note: the intention of this step is to make a situation where “Lost packet detection” occurs in MgNB-DU. - -4. Trigger radio link outage condition in the MgNB-DU. - -Note: the intention of this step is to make a situation where “Radio link outage” occurs in MgNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To gradually move the Test UE or UE emulator away from the coverage of the MgNB-DU. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the MgNB-DU cell. In this specific case, the gNB-DU cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. -5. Trigger radio link resume condition on MgNB-DU. -6. Stop scheduling in the MgNB-DU. - -Note: the intention of this step is to make a situation where “Stop scheduling for the data bearer” occurs in MgNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stop downlink data transmission -7. Restart scheduling in the MgNB-DU -8. Send Downlink User Data PDU(s) including *Report polling IE* with ‘1’ from SgNB-CU to SgNB-DU at least once. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. SgNB-CU transmits some data packets to SgNB-DU (ie, step 1) -9. Drop some packets sent from SgNB-CU to SgNB-DU via F1 link by using the Network Impairment Emulator inserted in-line in the F1 link. - -Note: the intention of this step is to make a situation where “Lost packet detection” occurs in SgNB-DU. - -10. Trigger radio link outage condition in the SgNB-DU. - -Note: the intention of this step is to make a situation where “Radio link outage” occurs in SgNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To gradually move the Test UE or UE emulator away from the coverage of the SgNB-DU. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the SgNB-DU cell. In this specific case, the SgNB-DU cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. -11. Trigger radio link resume condition on SgNB-DU. -12. Stop scheduling in the SgNB-DU. - -Note: the intention of this step is to make a situation where “Stop scheduling for the data bearer” occurs in SgNB-DU. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stop downlink data transmission -13. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs. - -### 2.3.2.9.5 Expected Results and Log Observation - -#### 2.3.2.9.5.1 Expected Results - -The use of Report Polling function is aligned with the requirement specified in Section 4.1.2.2 of NR U-Plane profile specification [3]. - -#### 2.3.2.9.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.2 and the following should be observed: - -- After the beginning of step 2: - - MgNB-CU sends MgNB-DU one or more Downlink User Data PDU(s) including Report polling IE with the value '1' - - MgNB-CU sends gNB-DU DDDS as soon as possible after receiving the corresponding Downlink User Data PDU(s) -- After the beginning of step 3, MgNB-DU sends MgNB-CU DDDS where following IEs show the dropped packets: - - Start of lost NR-U Sequence Number range IE(s) - - End of lost NR-U Sequence Number range IE(s) -- After the beginning of step 4, MgNB-DU sends MgNB-CU DDDS including *Cause Value IE* with the value '1', '3' or '4' -- After the beginning of step 6, MgNB-DU sends MgNB-CU DDDS including *Final Frame Indication IE* with the value '1', and then MgNB-DU does not send MgNB-CU DDDS including any updated instance of the following IEs - - Highest successfully delivered NR PDCP Sequence Number IE - - Highest transmitted NR PDCP Sequence Number IE - - Highest successfully delivered retransmitted NR PDCP Sequence Number IE - - Highest retransmitted NR PDCP Sequence Number IE -- After the beginning of step 9: - - SgNB-CU sends MgNB-DU one or more Downlink User Data PDU(s) including Report polling IE with the value '1' - - SgNB-CU sends MgNB-DU DDDS as soon as possible after receiving the corresponding Downlink User Data PDU(s) -- After the beginning of step 10, MgNB-DU sends MgNB-CU DDDS where following IEs show the dropped packets: - - Start of lost NR-U Sequence Number range IE(s) - - End of lost NR-U Sequence Number range IE(s) -- After the beginning of step 11, SgNB-DU sends SgNB-CU DDDS including *Cause Value IE* with the value '1', '3' or '4' -- After the beginning of step 13, gNB-DU sends SgNB-CU DDDS including *Final Frame Indication IE* with the value '1', and then SgNB-DU does not send SgNB-CU DDDS including any updated instance of the following IEs - - Highest successfully delivered NR PDCP Sequence Number IE - - Highest transmitted NR PDCP Sequence Number IE - -- o Highest successfully delivered retransmitted NR PDCP Sequence Number IE -- o Highest retransmitted NR PDCP Sequence Number IE - -## 2.3.2.10 Buffer discard indication for EN-DC with RLC-AM and/or RLC-UM - -### 2.3.2.10.1 Test Purpose - -The purpose of this test case is to verify that the use of the *DL Discard Blocks IE* and the *DL Flush IE* for EN-DC case with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.3. - -### 2.3.2.10.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of eNB cell (MN) cell and en-gNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- eNB or eNB emulator: used to perform Secondary Node Addition (Option 3x) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and contents - -### 2.3.2.10.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the MN (eNB) and SN (en-gNB) according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cell -- Secondary Node Addition (Option 3x) procedure between eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.3.2.10.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for gNB-DU to - -buffer the downlink data. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. gNB-CU to send the DL User Data message which includes the *DL Discard Blocks IE* with value '1'. - -Note: the purpose of this step is to indicate from gNB-CU to gNB-DU to discard NR PDCP PDUs. It is up to gNB-CU implementation when to initiate this step. Specific test procedure needs to be considered taking into account the gNB-CU implementation. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Tester sets small value in "discardTimer" in order that this timer expires before the gNB-CU receives acknowledgement of the transmitted data from the gNB-DU - -3. gNB-CU to send the DL User Data message which includes the *DL Flush IE* with value '1'. - -Note: the purpose of this step is to indicate from gNB-CU to gNB-DU to discard NR PDCP PDUs. It is up to gNB-CU implementation when to initiate this step. Specific test procedure needs to be considered taking into account the gNB-CU implementation. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Tester sets small value in "discardTimer" in order that this timer expires before the gNB-CU receives acknowledgement of the transmitted data from the gNB-DU - -4. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs. - -### 2.3.2.10.5 Expected Results and Log Observation - -#### 2.3.2.10.5.1 Expected Results - -The use of DL Discard Blocks IE and the DL Flush IE is aligned with the requirement specified in Section 4.1.2.3 of NR U-Plane profile specification [3]. - -#### 2.3.2.10.5.2 Log Observation - -Logs Recorded in the Protocol Analyzer and the Test UE or emulated UE show that: - -- NR PDCP PDUs, which are indicated to be discarded in the DL User Data message in step 2, are NOT received by the Test UE or emulated UE - -Note: the NR PDCP PDUs to be discarded is indicated by the following IEs in the DL User Data message: - -- o gNB-CU DL discard Number of blocks - - o DL discard NR PDCP PDU SN start - - o Discarded Block size present -- NR PDCP PDUs, which are indicated to be discarded in the DL User Data message in step 3, are NOT received by the Test UE or emulated UE. - - o DL discard NR PDCP PDU SN present - -### 2.3.2.11 Buffer discard indication for SA with RLC-AM and/or RLC-UM - -#### 2.3.2.11.1 Test Purpose - -The purpose of this test case is to verify that the use of the DL Discard Blocks IE and the DL Flush IE for SA case with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.3. - -#### 2.3.2.11.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe F1 procedural flows and contents - -#### 2.3.2.11.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed - -#### 2.3.2.11.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for gNB-DU to buffer the downlink data. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). -2. gNB-CU to send the DL User Data message which includes the *DL Discard Blocks IE* with value '1'. - -Note: the purpose of this step is to indicate from gNB-CU to gNB-DU to discard NR PDCP PDUs. It is up to gNB-CU implementation when to initiate this step. Specific test procedure needs to be considered taking into account the gNB-CU implementation. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Tester sets small value in "discardTimer" in order that this timer expires before the gNB-CU receives acknowledgement of the transmitted data from the gNB-DU -3. gNB-CU to send the DL User Data message which includes the *DL Flush IE* with value '1'. - -Note: the purpose of this step is to indicate from gNB-CU to gNB-DU to discard NR PDCP PDUs. It is up to gNB-CU implementation when to initiate this step. Specific test procedure needs to be considered taking into account the gNB-CU implementation. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Tester sets small value in "discardTimer" in order that this timer expires before the gNB-CU receives acknowledgement of the transmitted data from the gNB-DU -4. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs. - -### 2.3.2.11.5 Expected Results and Log Observation - -#### 2.3.2.11.5.1 Expected Results - -The use of *DL Discard Blocks IE* and the *DL Flush IE* is aligned with the requirement specified in Section 4.1.2.3 of NR U-Plane profile specification [3]. - -#### 2.3.2.11.5.2 Log Observation - -Logs Recorded in the Protocol Analyzer and the Test UE or emulated UE show that: - -- NR PDCP PDUs, which are indicated to be discarded in the DL User Data message in step 2, are NOT received by the Test UE or emulated UE - -Note: the NR PDCP PDUs to be discarded is indicated by the following IEs in the DL User Data message: - -- o gNB-CU DL discard Number of blocks - - o DL discard NR PDCP PDU SN start - - o Discarded Block size present -- NR PDCP PDUs, which are indicated to be discarded in the DL User Data message in step 3, are NOT received by the Test UE or emulated UE. - -Note: the NR PDCP PDUs to be discarded is indicated by the following IEs in the DL User Data message: - -- o DL discard NR PDCP PDU SN present - -### 2.3.2.12 Buffer discard indication for NR-DC with RLC-AM and/or RLC-UM - -#### 2.3.2.12.1 Test Purpose - -The purpose of this test case is to verify that the use of the *DL Discard Blocks IE* and the *DL Flush IE* for NR-DC case with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.3. - -#### 2.3.2.12.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of MgNB cell (MN) cell and SgNB cell (SN) overlap -- Testing tools which are required for this test scenario: - -Test UE or UE emulator which is capable of supporting NR and NR-DC: used to terminate NAS/AS protocol and data transmission/reception - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn and F1 procedural flows and contents - -#### 2.3.2.12.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.3.2.12.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for gNB-DU to buffer the downlink data. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). -2. MgNB-CU to send the DL User Data message which includes the *DL Discard Blocks IE* with value '1'. - -Note: the purpose of this step is to indicate from MgNB-CU to MgNB-DU to discard NR PDCP PDUs. It is up to MgNB-CU implementation when to initiate this step. Specific test procedure needs to be considered taking into account the MgNB-CU implementation. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Tester sets small value in "discardTimer" in order that this timer expires before the MgNB-CU receives acknowledgement of the transmitted data from the MgNB-DU - -3. MgNB-CU to send the DL User Data message which includes the *DL Flush IE* with value '1'. - -Note: the purpose of this step is to indicate from MgNB-CU to MgNB-DU to discard NR PDCP PDUs. It is up to MgNB-CU implementation when to initiate this step. Specific test procedure needs to be considered taking into account the MgNB-CU implementation. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Tester sets small value in "discardTimer" in order that this timer expires before the MgNB-CU receives acknowledgement of the transmitted data from the MgNB-DU - -4. SgNB-CU to send the DL User Data message which includes the *DL Discard Blocks IE* with value '1'. - -Note: the purpose of this step is to indicate from MgNB-CU to SgNB-DU to discard NR PDCP PDUs. It is up to SgNB-CU implementation when to initiate this step. Specific test procedure needs to be considered taking into account the SgNB-CU implementation. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Tester sets small value in "discardTimer" in order that this timer expires before the SgNB-CU receives acknowledgement of the transmitted data from the SgNB-DU -5. SgNB-CU to send the DL User Data message which includes the DL Flush IE with value '1'. - -Note: the purpose of this step is to indicate from SgNB-CU to gNB-DU to discard NR PDCP PDUs. It is up to SgNB-CU implementation when to initiate this step. Specific test procedure needs to be considered taking into account the SgNB-CU implementation. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Tester sets small value in "discardTimer" in order that this timer expires before the SgNB-CU receives acknowledgement of the transmitted data from the SgNB-DU -6. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -### 2.3.2.12.5 Expected Results and Log Observation - -#### 2.3.2.12.5.1 Expected Results - -The use of DL Discard Blocks IE and the DL Flush IE is aligned with the requirement specified in Section 4.1.2.3 of NR U-Plane profile specification [3]. - -#### 2.3.2.12.5.2 Log Observation - -Logs Recorded in the Protocol Analyzer and the Test UE or emulated UE show that: - -- NR PDCP PDUs of MgNB, which are indicated to be discarded in the DL User Data message in step 2, are NOT received by the Test UE or emulated UE - -Note: the NR PDCP PDUs to be discarded is indicated by the following IEs in the DL User Data message: - -- o gNB-CU DL discard Number of blocks -- o DL discard NR PDCP PDU SN start -- o Discarded Block size present - -- NR PDCP PDUs of MgNB, which are indicated to be discarded in the DL User Data message in step 3, are NOT received by the Test UE or emulated UE. - -Note: the NR PDCP PDUs to be discarded is indicated by the following IEs in the DL User Data message: - -- o DL discard NR PDCP PDU SN present - -- NR PDCP PDUs of SgNB, which are indicated to be discarded in the DL User Data message in step 4, are NOT received by the Test UE or emulated UE - -Note: the NR PDCP PDUs to be discarded is indicated by the following IEs in the DL User Data message: - -- o gNB-CU DL discard Number of blocks -- o DL discard NR PDCP PDU SN start -- o Discarded Block size present - -- NR PDCP PDUs of SgNB, which are indicated to be discarded in the DL User Data message in step 5, are NOT received by the Test UE or emulated UE. - -Note: the NR PDCP PDUs to be discarded is indicated by the following IEs in the DL User Data message: - -- o discard NR PDCP PDU SN present - -## 2.3.2.13 User data existence flag for EN-DC with RLC-AM and/or RLC-UM - -### 2.3.2.13.1 Test Purpose - -The purpose of this test case is to verify gNB-CU's notification to the gNB-DU of the existence of user data, but without using the User data existence flag IE, with gNB-DU and gNB-CU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.4. - -Note: This feature is needed when the gNB-DU does not support the User data existence flag IE eg, in the case when the gNB-DU is designed to be compliant with older versions of the 3GPP specifications which do not support this IE. - -### 2.3.2.13.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of eNB cell (MN) cell and en-gNB cell (SN) overlap -- gNB-CU shall activate the feature which is specified in Section 4.1.2.4 of NR U-Plane profile [3] - -Note: How to activate this feature is up to gNB-CU implementation. One example is to activate it via M-Plane. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- eNB or eNB emulator: used to perform Secondary Node Addition (Option 3x) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and contents - -### 2.3.2.13.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cell - -- Secondary Node Addition (Option 3x) procedure between eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.3.2.13.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator via X2. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, to meaningfully verify that the user plane transmission operates correctly. - -Note: the intention of this step is to avoid expiring some timers in eNB which monitor the activity of user data transfer (eg, DRX inactivity timer, UE inactive timer, etc). - -2. Decrease the amount of user data to be transmitted in both directions between the Application Test Server and the Test UE or UE emulator so that the user data can be transmitted via LTE RAT only. With this condition perform data transmission for appropriate time over drx-InactivityTimer. - -Note: the intention of this step is to create a situation where the en-gNB sends actual user data to the eNB even when the amount of user data is small enough to be sent via the LTE RAT only. In this test scenario, the LTE RAT radio condition need not be ideal but shall be good enough to ensure that all user data can be transmitted through the LTE RAT only. - -3. Stop data transfer. -4. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator log - -#### 2.3.2.13.5 Expected Results and Log Observation - -##### 2.3.2.13.5.1 Expected Results - -The behaviour of gNB-CU is aligned with the requirement specified in Section 4.1.2.4 of NR U-Plane profile [3]. - -##### 2.3.2.13.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.4 and the following should be observed: - -- NR PDCP PDU is sent from gNB-CU to gNB-DU, which is frequently enough NOT to expire the timers described in the note in step 1 - -Note: The required frequency is up to gNB implementation, ie, the value of the timers used in the gNB. - -As a result of above, logs recorded in the Test UE or UE emulator shows: - -- Test UE or UE emulator keeps RRC Connected state without expiring DRX inactivity timer as specified in 3GPP TS 36.331 [13] and 3GPP TS 36.321 [14], from the beginning of step 2 till before step 3 - -#### 2.3.2.14 User data existence flag for SA with RLC-AM and/or RLC-UM - -##### 2.3.2.14.1 Test Purpose - -The purpose of this test case is to verify gNB-CU's notification to the gNB-DU of the existence of user data, but without using the User data existence flag IE, with gNB-DU and gNB-CU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.4. - -Note: This feature is needed when the gNB-DU does not support the User data existence flag IE eg, in the case when the gNB-DU is designed to be compliant with older versions of the 3GPP specifications which do not support this IE. - -##### 2.3.2.14.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- gNB-CU shall activate the feature which is specified in Section 4.1.2.4 of NR U-Plane profile [3] - -Note: How to activate this feature is up to gNB-CU implementation. One example is to activate it via M-Plane. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe F1 procedural flows and contents - -### 2.3.2.14.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed - -### 2.3.2.14.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, to meaningfully verify that the user plane transmission operates correctly. - -Note: the intention of this step is to avoid expiring some timers in gNB which monitor the activity of user data transfer (eg, DRX inactivity timer, UE inactive timer, etc). - -2. Stop data transfer for appropriate time over drx-InactivityTimer. -3. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator log - -### 2.3.2.14.5 Expected Results and Log Observation - -#### 2.3.2.14.5.1 Expected Results - -The behaviour of gNB-CU is aligned with the requirement specified in Section 4.1.2.4 of NR U-Plane profile [3]. - -#### 2.3.2.14.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.4 and the following should be observed: - -- NR PDCP PDU is sent from gNB-CU to gNB-DU, which is frequently enough NOT to expire the timers described in the note in step 1 - -Note: The required frequency is up to gNB implementation, ie, the value of the timers used in the gNB. - -As a result of above, logs recorded in the Test UE or UE emulator shows: - -- Test UE or UE emulator keeps RRC Connected state without expiring DRX inactivity timer as specified in 3GPP TS 38.331 [17] and 3GPP TS 38.321 [18], from the beginning of step 2 till before step 3 - -## 2.3.2.15 User data existence flag for NR-DC with RLC-AM and/or RLC-UM - -### 2.3.2.15.1 Test Purpose - -The purpose of this test case is to verify gNB-CU's notification to the gNB-DU of the existence of user data, but without using the User data existence flag IE, with gNB-DU and gNB-CU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.4. - -Note: This feature is needed when the gNB-DU does not support the User data existence flag IE eg, in the case when the gNB-DU is designed to be compliant with older versions of the 3GPP specifications which do not support this IE. - -### 2.3.2.15.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings - -- The coverage of MgNB cell (MN) cell and SgNB cell (SN) overlap -- gNB-CU shall activate the feature which is specified in Section 4.1.2.4 of NR U-Plane profile [3] - -Note: How to activate this feature is up to gNB-CU implementation. One example is to activate it via M-Plane. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn and F1 procedural flows and contents - -### 2.3.2.15.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.3.2.15.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator via Xn. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, to meaningfully verify that the user plane transmission operates correctly. - -Note: the intention of this step is to avoid expiring some timers in MgNB and SgNB which monitor the activity of user data transfer (eg, DRX inactivity timer, UE inactive timer, etc). - -2. Decrease the amount of user data to be transmitted in both directions between the Application Test Server and the Test UE or UE emulator so that the user data can be transmitted via SgNB only. With this condition perform data transmission for appropriate time over drx-InactivityTimer of MgNB. - -Note: the intention of this step is to create a situation where the SgNB sends actual user data to the MgNB even when the amount of user data is small enough to be sent via the SgNB only. In this test scenario, the SgNB radio condition need not be ideal but shall be good enough to ensure that all user data can be transmitted through the SgNB only. - -3. Increase the amount of user data to be transmitted from the Application Test Server to the Test UE or UE emulator (return to the amount of normal user data) - -4. Decrease the amount of user data to be transmitted in both directions between the Application Test Server and the Test UE or UE emulator so that the user data can be transmitted via MgNB only. With this condition perform data transmission for appropriate time over drx-InactivityTimer of SgNB. - -Note: the intention of this step is to create a situation where the MgNB sends actual user data to the SgNB even when the amount of user data is small enough to be sent via the MgNB only. In this test scenario, the MgNB radio condition need not be ideal but shall be good enough to ensure that all user data can be transmitted through the MgNB only. - -5. Stop data transfer. -6. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator log - -#### 2.3.2.15.5 Expected Results and Log Observation - -##### 2.3.2.15.5.1 Expected Results - -The behaviour of gNB-CU and gNB-DU is aligned with the requirement specified in Section 4.1.2.4 of NR U-Plane profile [3]. - -##### 2.3.2.15.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.4 and the following should be observed: - -- NR PDCP PDU is sent from MgNB-CU to MgNB-DU, which is frequently enough NOT to expire the timers described in the note in step 1 - -Note: The required frequency is up to MgNB implementation, ie, the value of the timers used in the MgNB. - -- NR PDCP PDU is sent from SgNB-CU to SgNB-DU, which is frequently enough NOT to expire the timers described in the note in step 3 - -Note: The required frequency is up to SgNB implementation, ie, the value of the timers used in the SgNB. - -As a result of above, logs recorded in the Test UE or UE emulator shows: - -- Test UE or UE emulator keeps RRC Connected state without expiring DRX inactivity timer as specified in 3GPP TS 38.331 [xx] and 3GPP TS 38.321 [xx], from the beginning of step 2 till before step 5 - -## 2.3.2.16 Assistance Information Report polling for EN-DC with RLC-AM and/or RLC-UM - -### 2.3.2.16.1 Test Purpose - -The purpose of this test case is to verify the use of the Assistance Information Report polling flag for EN-DC with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.5. - -### 2.3.2.16.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of eNB cell (MN) and en-gNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception eNB or eNB emulator: used to perform Secondary Node Addition (Option 3x) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and contents - -### 2.3.2.16.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cell -- Secondary Node Addition (Option 3x) procedure between eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.3.2.16.4 Procedure - -1. Send Downlink User Data PDU(s) from gNB-CU to gNB-DU with Assistance Information Report polling Flag IE whose value is set to '1'. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. Send the Downlink User Data PDU(s) immediately after completing the Secondary Node Addition (Option 3x) procedure - -2. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for gNB-DU to buffer the downlink data. The exact data rate that is generated is not specified, but it is up to gNB-DU node vendor implementation. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). -3. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs. - -### 2.3.2.16.5 Expected Results and Log Observation - -#### 2.3.2.16.5.1 Expected Results - -The use of the Assistance Information Report polling flag is aligned to the requirement specified in Section 4.1.2.5 of NR U-Plane profile [3]. - -#### 2.3.2.16.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.5 and the following should be observed: - -- In step 1, one or more Downlink User Data PDU(s) sent by the gNB-CU to the gNB-DU include Assistance Information Report polling Flag IE with the value '1' -- After receiving the corresponding Downlink User Data PDU(s), AID is sent by the gNB-DU to the gNB-CU - -### 2.3.2.17 Assistance Information Report polling for SA with RLC-AM and/or RLC-UM - -#### 2.3.2.17.1 Test Purpose - -The purpose of this test case is to verify the use of the Assistance Information Report polling flag for SA with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.5. - -#### 2.3.2.17.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe F1 procedural flows and contents - -#### 2.3.2.17.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed - -#### 2.3.2.17.4 Procedure - -1. Send Downlink User Data PDU(s) from gNB-CU to gNB-DU with Assistance Information Report polling Flag IE whose value is set to '1'. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. Initiate Service Request procedure from UE or UE emulator -2. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for gNB-DU to buffer the downlink data. The exact data rate that is generated is not specified, but it is up to gNB-DU node vendor implementation. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - 3. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs. - -#### 2.3.2.17.5 Expected Results and Log Observation - -##### 2.3.2.17.5.1 Expected Results - -The use of the Assistance Information Report polling flag is aligned to the requirement specified in Section 4.1.2.5 of NR U-Plane profile [3]. - -##### 2.3.2.17.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.5 and the following should be observed: - -- In step 1, one or more Downlink User Data PDU(s) sent by the gNB-CU to the gNB-DU include *Assistance Information Report polling Flag IE* with the value '1' -- After receiving the corresponding Downlink User Data PDU(s), AID is sent by the gNB-DU to the gNB-CU - -#### 2.3.2.18 Assistance Information Report polling for NR-DC with RLC-AM and/or RLC-UM - -##### 2.3.2.18.1 Test Purpose - -The purpose of this test case is to verify the use of the Assistance Information Report polling flag for NR-DC with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.5. - -##### 2.3.2.18.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of MgNB cell (MN) cell and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to terminate NAS/AS protocol and data transmission/reception Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn and F1 procedural flows and contents - -### 2.3.2.18.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.3.2.18.4 Procedure - -1. Send Downlink User Data PDU(s) from SgNB-CU to SgNB-DU with *Assistance Information Report polling Flag IE* whose value is set to '1'. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. Send the Downlink User Data PDU(s) immediately after completing the S-NG-RAN NODE ADDITION procedure - -2. Send Downlink User Data PDU(s) from MgNB-CU to MgNB-DU with *Assistance Information Report polling Flag IE* whose value is set to '1'. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for MgNB-DU and SgNB-DU to buffer the downlink data. The exact data rate that is generated is not specified, but it is up to MgNB-DU and SgNB-DU node vendor implementation. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -3. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -### 2.3.2.18.5 Expected Results and Log Observation - -#### 2.3.2.18.5.1 Expected Results - -The use of the Assistance Information Report polling flag is aligned to the requirement specified in Section 4.1.2.5 of NR U-Plane profile [3]. - -#### 2.3.2.18.5.2 Log Observation - -Xn and F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.5 and the following should be observed: - -- In step 1, one or more Downlink User Data PDU(s) sent by the SgNB-CU to the SgNB-DU include *Assistance Information Report polling Flag IE* with the value '1' -- After receiving the corresponding Downlink User Data PDU(s), AID is sent by the SgNB-DU to the SgNB-CU -- In step 2, one or more Downlink User Data PDU(s) sent by the MgNB-CU to the MgNB-DU include *Assistance Information Report polling Flag IE* with the value '1' -- After receiving the corresponding Downlink User Data PDU(s), AID is sent by the MgNB-DU to the MgNB-CU - -### 2.3.2.19 Radio quality assistance information for EN-DC with RLC-AM and/or RLC-UM - -#### 2.3.2.19.1 Test Purpose - -The purpose of this test case is to verify the use of the Radio quality assistance information IE for EN-DC with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.6. - -#### 2.3.2.19.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of eNB cell (MN) and en-gNB cell (SN) overlap -- gNB-DU shall be configured with the Assistance Information Type(s) to be reported in the AID message via M-Plane. In this version of the specification the following Assistance Information Types can be configured to be reported: - - o '0'=UNKNOWN - - o '1'=Average CQI - - o '2'=Average HARQ Failure - - o '3'=Average HARQ Retransmissions - - o '4'= DL Radio Quality Index - - o '5'= UL Radio Quality Index - - o '6'= Power Headroom Report - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- eNB or eNB emulator: used to perform Secondary Node Addition (Option 3x) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and contents - -### 2.3.2.19.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the eNB and en-gNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cell -- Secondary Node Addition (Option 3x) procedure between eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.3.2.19.4 Procedure - -1. Send Downlink User Data PDU(s) from gNB-CU to gNB-DU with *Assistance Information Report polling Flag IE* whose value is set to '1'. This procedure shall be performed before the assistance information to be reported by the gNB-DU becomes available. - -Note: the intention of this step is to create a situation where the gNB-DU does not report the assistance information due to unavailability of the information. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Send the Downlink User Data PDU(s) immediately after completing the Secondary Node Addition (Option 3x) procedure -2. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for gNB-DU to buffer the downlink data. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). -3. Create conditions which can help the gNB-DU gather the information/measurements required for its configured Assistance Information Types. - -An example of how these conditions can be created is listed below. The exact method to create these conditions is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Send DL user data so that gNB-DU can obtain eg, CQI/HARQ ACK/Power headroom report from Test UE or UE emulator. - -4. Send Downlink User Data PDU(s) from gNB-CU to gNB-DU *with Assistance Information Report polling Flag IE* whose value is set to '1'. -5. Observe the Protocol Analyzer X2 and F1 logs and Test UE or UE emulator logs. - -### 2.3.2.19.5 Expected Results and Log Observation - -#### 2.3.2.19.5.1 Expected Results - -The use of the Radio quality assistance information IE is aligned with the requirement specified in Section 4.1.2.6 of NR U-Plane profile [3]. - -#### 2.3.2.19.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.6 and the following should be observed: - -- After step 1, gNB-DU sends the Assistance Information Data message to gNB-CU, where the value of *Assistance Information Indication IE* is '0' - -Note: the intention is to validate that any configured assistance information is not reported at this moment. - -- After step 3, gNB-DU sends the Assistance Information Data message to gNB-CU, where *Assistance Information Type IE*, Number of octets for *Radio Quality Assistance Information Fields IE*, and *Radio Quality Assistance Information IE* corresponding to the configured assistance information are included - -Note: the intention is to validate that all the configured assistance information is reported. - -Note: it is not expected that any assistance information which is not configured to be reported via M-Plane is included in the AID message. - -### 2.3.2.20 Radio quality assistance information for SA with RLC-AM and/or RLC-UM - -#### 2.3.2.20.1 Test Purpose - -The purpose of this test case is to verify the use of the Radio quality assistance information IE for SA with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.6. - -#### 2.3.2.20.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- gNB-DU shall be configured with the Assistance Information Type(s) to be reported in the AID message via M-Plane. In this version of the specification the following Assistance Information Types can be configured to be reported: - -- o '0'=UNKNOWN -- o '1'=Average CQI -- o '2'=Average HARQ Failure -- o '3'=Average HARQ Retransmissions -- o '4'= DL Radio Quality Index -- o '5'= UL Radio Quality Index - -- o '6'= Power Headroom Report - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe F1 procedural flows and contents - -### 2.3.2.20.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed - -### 2.3.2.20.4 Procedure - -1. Send Downlink User Data PDU(s) from gNB-CU to gNB-DU with *Assistance Information Report polling Flag IE* whose value is set to '1'. This procedure shall be performed before the assistance information to be reported by the gNB-DU becomes available. - -Note: the intention of this step is to create a situation where the gNB-DU does not report the assistance information due to unavailability of the information. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Initiate Service Request procedure from UE or UE emulator -2. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for gNB-DU to buffer the downlink data. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - 3. Create conditions which can help the gNB-DU gather the information/measurements required for its configured Assistance Information Types. - -An example of how these conditions can be created is listed below. The exact method to create these conditions is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Send DL user data so that gNB-DU can obtain eg, CQI/HARQ ACK/Power headroom report from Test UE or UE emulator. -4. Send Downlink User Data PDU(s) from gNB-CU to gNB-DU with *Assistance Information Report polling Flag IE* whose value is set to '1'. - 5. Observe the Protocol Analyzer F1 logs and Test UE or UE emulator logs. - -### 2.3.2.20.5 Expected Results and Log Observation - -#### 2.3.2.20.5.1 Expected Results - -The use of the Radio quality assistance information IE is aligned with the requirement specified in Section 4.1.2.6 of NR U-Plane profile [3]. - -#### 2.3.2.20.5.2 Log Observation - -F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.6 and the following should be observed: - -- After step 1, gNB-DU sends the Assistance Information Data message to gNB-CU, where the value of *Assistance Information Indication IE* is '0' - -Note: the intention is to validate that any configured assistance information is not reported at this moment. - -- After step 3, gNB-DU sends the Assistance Information Data message to gNB-CU, where *Assistance Information Type IE*, Number of octets for *Radio Quality Assistance Information Fields IE*, and *Radio Quality Assistance Information IE* corresponding to the configured assistance information are included - -Note: the intention is to validate that all the configured assistance information is reported. - -Note: it is not expected that any assistance information which is not configured to be reported via M-Plane is included in the AID message. - -### 2.3.2.21 Radio quality assistance information for NR-DC with RLC-AM and/or RLC-UM - -#### 2.3.2.21.1 Test Purpose - -The purpose of this test case is to verify the use of the *Radio quality assistance information IE* for NR-DC with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.6. - -#### 2.3.2.21.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of MgNB cell (MN) cell and SgNB cell (SN) overlap -- gNB-DU shall be configured with the Assistance Information Type(s) to be reported in the AID message via M-Plane. In this version of the specification the following Assistance Information Types can be configured to be reported: - - o '0'=UNKNOWN - - o '1'=Average CQI - - o '2'=Average HARQ Failure - - o '3'=Average HARQ Retransmissions - - o '4'= DL Radio Quality Index - - o '5'= UL Radio Quality Index - - o '6'= Power Headroom Report - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn and F1 procedural flows and contents - -### 2.3.2.21.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.3.2.21.4 Procedure - -1. Send Downlink User Data PDU(s) from SgNB-CU to SgNB-DU with *Assistance Information Report polling Flag IE* whose value is set to '1'. This procedure shall be performed before the assistance information to be reported by the SgNB-DU becomes available. - -Note: the intention of this step is to create a situation where the SgNB-DU does not report the assistance information due to unavailability of the information. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Send the Downlink User Data PDU(s) immediately after completing the Secondary Node Addition (Option 3x) procedure -2. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for SgNB-DU to buffer the downlink data. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - 3. Create conditions which can help the SgNB-DU gather the information/measurements required for its configured Assistance Information Types. - -An example of how these conditions can be created is listed below. The exact method to create these conditions is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Send DL user data so that SgNB-DU can obtain eg, CQI/HARQ ACK/Power headroom report from Test UE or UE emulator. -4. Send Downlink User Data PDU(s) from SgNB-CU to SgNB-DU with *Assistance Information Report polling Flag IE* whose value is set to '1'. - -5. Create conditions which can help the MgNB-DU gather the information/measurements required for its configured Assistance Information Types. - -An example of how these conditions can be created is listed below. The exact method to create these conditions is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Send DL user data so that MgNB-DU can obtain eg, CQI/HARQ ACK/Power headroom report from Test UE or UE emulator. -6. Send Downlink User Data PDU(s) from MgNB-CU to MgNB-DU with *Assistance Information Report polling Flag IE* whose value is set to '1'. - 7. Observe the Protocol Analyzer Xn and F1 logs and Test UE or UE emulator logs. - -### 2.3.2.21.5 Expected Results and Log Observation - -#### 2.3.2.21.5.1 Expected Results - -The use of the Radio quality assistance information IE is aligned with the requirement specified in Section 4.1.2.6 of NR U-Plane profile [3]. - -#### 2.3.2.21.5.2 Log Observation - -X2 and F1 logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.6 and the following should be observed: - -- After step 1, SgNB-DU sends the Assistance Information Data message to SgNB-CU, where the value of *Assistance Information Indication IE* is '0' - -Note: the intention is to validate that any configured assistance information is not reported at this moment. - -- After step 3, SgNB-DU sends the Assistance Information Data message to SgNB-CU, where *Assistance Information Type IE*, Number of octets for *Radio Quality Assistance Information Fields IE*, and *Radio Quality Assistance Information IE* corresponding to the configured assistance information are included - -Note: the intention is to validate that all the configured assistance information is reported. - -Note: it is not expected that any assistance information which is not configured to be reported via M-Plane is included in the AID message. - -- After step 5, MgNB-DU sends the Assistance Information Data message to MgNB-CU, where *Assistance Information Type IE*, Number of octets for *Radio Quality Assistance Information Fields IE*, and *Radio Quality Assistance Information IE* corresponding to the configured assistance information are included - -Note: the intention is to validate that all the configured assistance information is reported. - -Note: it is not expected that any assistance information which is not configured to be reported via M-Plane is included in the AID message. - -### 2.3.2.22 DL report NR PDCP PDU SN for EN-DC with RLC-AM - -#### 2.3.2.22.1 Test Purpose - -The purpose of this test case is to verify that the use of the DL report NR PDCP PDU SN IE for EN-DC with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.7. - -#### 2.3.2.22.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply RLC-AM specified in NR U-Plane profile specification [3] -- The coverage of eNB cell (MN) and en-gNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting both LTE and NR: used to terminate NAS/AS protocol and data transmission/reception -- eNB or eNB emulator: used to perform Secondary Node Addition (Option 3x) procedure -- Core or Core emulator (EPC with EN-DC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe X2 and F1 procedural flows and contents - -### 2.3.2.22.3 Initial Conditions - -Refer to Section 2.3 for the F1 related list of initial conditions. Besides, refer to Section 2.2 for the X2 related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- EN-DC X2 setup procedure has been successfully completed between the MN (eNB) and SN (en-gNB) according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Attach procedure and Service Request procedure specified in 3GPP TS 23.401 [8] has been completed -- Test UE or UE emulator is within the coverage area of the eNB cell and en-gNB cell -- Secondary Node Addition (Option 3x) procedure between eNB and en-gNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.3.2.22.4 Procedure - -1. Perform data transfer from the Application Test Server to the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, to meaningfully verify that the user plane transmission operates correctly. -2. Send the DL User Data message which includes the DL report NR PDCP PDU SN IE from gNB-CU to gNB-DU. -3. Observe the Protocol Analyzer X2 and F1 logs. - -### 2.3.2.22.5 Expected Results and Log Observation - -#### 2.3.2.22.5.1 Expected Results - -The use of DL report NR PDCP PDU SN IE is aligned with the requirement specified in Section 4.1.2.7 of NR U-Plane profile specification [3]. - -#### 2.3.2.22.5.2 Log Observation - -Logs Recorded in the Protocol Analyzer show that: - -- After beginning of step 2: - -- o gNB-DU sends gNB-CU DDDS including Highest successfully delivered NR PDCP Sequence Number IE with the value same as the value indicated by DL report NR PDCP PDU SN IE. -- o gNB-DU sends gNB-CU DDDS as soon as possible only when all PDCP PDU SNs up to this DL report NR PDCP PDU have been successfully delivered in-sequence. - -### 2.3.2.23 DL report NR PDCP PDU SN for SA with RLC-AM - -#### 2.3.2.23.1 Test Purpose - -The purpose of this test case is to verify that the use of the DL report NR PDCP PDU SN IE for SA with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.7. - -#### 2.3.2.23.2 Minimum Requirements - -DUTs: Single gNB-CU and single gNB-DU: - -- DUTs shall apply RLC-AM specified in NR U-Plane profile specification [3] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe F1 procedural flows and contents - -#### 2.3.2.23.3 Initial Conditions - -Refer to Section 2.3 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed - -#### 2.3.2.23.4 Procedure - -1. Perform data transfer from the Application Test Server to the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, to meaningfully verify that the user plane transmission operates correctly. -2. Send the DL User Data message which includes the DL report NR PDCP PDU SN IE from gNB-CU to gNB-DU. -3. Observe the Protocol Analyzer F1 logs. - -#### 2.3.2.23.5 Expected Results and Log Observation - -##### 2.3.2.23.5.1 Expected Results - -The use of DL report NR PDCP PDU SN IE is aligned with the requirement specified in Section 4.1.2.7 of NR U-Plane profile specification [3]. - -### 2.3.2.23.5.2 Log Observation - -Logs Recorded in the Protocol Analyzer show that: - -- After beginning of step 2: - - gNB-DU sends gNB-CU DDDS including Highest successfully delivered NR PDCP Sequence Number IE with the value same as the value indicated by DL report NR PDCP PDU SN IE. - - gNB-DU sends gNB-CU DDDS as soon as possible only when all PDCP PDU SNs up to this DL report NR PDCP PDU have been successfully delivered in-sequence. - -### 2.3.2.24 DL report NR PDCP PDU SN for NR-DC with RLC-AM - -#### 2.3.2.24.1 Test Purpose - -The purpose of this test case is to verify that the use of the DL report NR PDCP PDU SN IE for NR-DC with gNB-CU and gNB-DU from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.7. - -#### 2.3.2.24.2 Minimum Requirements - -DUTs: Two gNBs (MgNB-CU and MgNB-DU – MN, SgNB-CU and SgNB-DU – SN): - -- DUTs shall apply RLC-AM specified in NR U-Plane profile specification [3] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn and F1 procedural flows and contents - -#### 2.3.2.24.3 Initial Conditions - -Refer to Section 2.3 for the F1 related standard list of initial conditions. Besides, refer to Section 2.4 for the Xn related list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- F1 setup procedure has been successfully completed between the gNB-CU and gNB-DU according to the NR C-Plane profile specification [2] for both MgNB and SgNB -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.3.2.24.4 Procedure - -1. Perform data transfer from the Application Test Server to the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, to meaningfully verify that the user plane transmission operates correctly. -2. Send the DL User Data message which includes the DL report NR PDCP PDU SN IE from MgNB-CU to MgNB-DU. -3. Send the DL User Data message which includes the DL report NR PDCP PDU SN IE from SgNB-CU to SgNB-DU. -4. Observe the Protocol Analyzer Xn and F1 logs. - -### 2.3.2.24.5 Expected Results and Log Observation - -#### 2.3.2.24.5.1 Expected Results - -The use of DL report NR PDCP PDU SN IE is aligned with the requirement specified in Section 4.1.2.7 of NR U-Plane profile specification [3]. - -#### 2.3.2.24.5.2 Log Observation - -Logs Recorded in the Protocol Analyzer show that: - -- After beginning of step 2: - - MgNB-DU sends MgNB-CU DDDS including Highest successfully delivered NR PDCP Sequence Number IE with the value same as the value indicated by DL report NR PDCP PDU SN IE. - - MgNB-DU sends MgNB-CU DDDS as soon as possible only when all PDCP PDU SNs up to this DL report NR PDCP PDU have been successfully delivered in-sequence. -- After beginning of step 3: - - SgNB-DU sends SgNB-CU DDDS including Highest successfully delivered NR PDCP Sequence Number IE with the value same as the value indicated by DL report NR PDCP PDU SN IE. - - SgNB-DU sends SgNB-CU DDDS as soon as possible only when all PDCP PDU SNs up to this DL report NR PDCP PDU have been successfully delivered in-sequence. - -## 2.4 Xn Interoperability Test Cases - -The following set of Xn IOT cases are defined in this version of the specification. - -| Test Case | Reference to O-RAN NR C-Plane profile [2] | -|---------------------------------------------------------------|-------------------------------------------| -| Xn Setup | 4.2.1 | -| Inter gNB HO | 6.4.1 | -| S-NG-RAN Node Addition | 7.1.1 | -| M-NG-RAN node initiated SN modification: PDU Session Addition | 7.2.1.1 | -| M-NG-RAN node initiated SN modification: PDU Session Release | 7.2.1.2 | -| M-NG-RAN node initiated SN modification: Security Key Change | 7.2.1.4 | - -| | | -|-----------------------------------------------------------------------------------------------------------------------------------|-----------| -| M-NG-RAN node initiated SN modification: PDU Session Modification with QoS flow addition | 7.2.1.3.1 | -| M-NG-RAN node initiated SN modification: PDU Session Modification with QoS flow release | 7.2.1.3.2 | -| M-NG-RAN node initiated SN modification: SCG Configuration Query | 7.2.1.5 | -| M-NG-RAN node initiated SN modification: Allowed Band Combination list update | 7.2.1.6 | -| M-NG-RAN node initiated SN modification: PCell Change (Intra-MN) | 7.2.1.7 | -| M-NG-RAN node initiated SN modification: PDU Session Modification with 5QI change | 7.2.1.3.3 | -| S-NG-RAN node initiated SN modification with MN involvement: PDU Session Release | 7.2.2.2 | -| S-NG-RAN node initiated SN modification with MN involvement: Security Key change | 7.2.2.3 | -| S-NG-RAN node initiated SN modification with MN involvement: PSCell change, Intra gNB-DU | 7.2.2.4 | -| S-NG-RAN node initiated SN modification with MN involvement: PSCell change, Inter gNB-DU | 7.2.2.5 | -| S-NG-RAN node initiated SN modification with MN involvement: UL Configuration Update | 7.2.2.6 | -| Measurement Gap Coordination Procedure (SN initiated) | 7.2.2.7 | -| CellGroupConfig change (SN-DU initiated) | 7.2.2.8 | -| S-NG-RAN node initiated SN modification without MN involvement: SRB3 not supported: SN Modification – SCell(s) Addition / Release | 7.2.3.1.1 | -| S-NG-RAN node initiated SN modification without MN involvement: SRB3 supported: Intra gNB-DU PSCell Change using SRB3 | 7.2.3.2.1 | -| S-NG-RAN node initiated SN modification without MN involvement: SRB3 supported: Inter gNB-DU PSCell Change using SRB3 | 7.2.3.2.2 | -| M-NG-RAN node initiated S-NG-RAN node Release without keeping UE | 7.3.1 | -| M-NG-RAN node initiated S-NG-RAN node Release with keeping UE | 7.3.2 | -| S-NG-RAN node initiated S-NG-RAN node Release | 7.3.3 | -| Resource Status Reporting Initiation | 4.2.9.1 | -| Resource Status Reporting | 4.2.9.2 | -| Master Node to gNB Change | 7.6.1 | -| Reset | 4.2.2 | -| Inter-Master Node Handover (Without SN Change) | 7.7.1 | -| Inter-Master Node Handover (with SN Change) | 7.7.2 | -| Secondary Node Change (SN initiated) | 7.8.1 | - -| | | -|---------------------------------------------------------------------------------|---------| -| | | -| NG-RAN Node Configuration Update | 4.2.8.1 | -| UE measurement transfer | 7.5.1 | -| MN Initiated SN Change | 7.8.2 | -| RRC connection re-establishment (inter gNB-CU) | 6.10.4 | -| RRC Inactive to RRC Connected, Inter gNB-CU | 6.9.3 | -| Measurement Gap Coordination Procedure (MN initiated) | 7.2.1.8 | -| SN initiated Activity Notification | 7.9.1 | -| Intra Master Node, intra gNB-DU, intra cell handover with Secondary Node change | 7.10.1 | -| Intra Master Node, intra gNB-DU, inter cell handover with Secondary Node change | 7.10.2 | -| Intra Master Node, inter gNB-DU handover with Secondary Node change | 7.10.3 | - -**Table 2-6: IOT Test Cases for Xn implemented in accordance with the NR C-Plane [2] profile** - -| Test Case | Reference to O-RAN NR U-Plane profile [3] | -|--------------------------------------------------------------------------------|-------------------------------------------| -| Node behaviour of the corresponding node with RLC-AM and/or RLC-UM | 4.1.1.1 | -| General for Elements for the NR user plane protocols with RLC-AM and/or RLC-UM | 4.1.2.1 | -| Report polling with RLC-AM and/or RLC-UM | 4.1.2.2 | -| Buffer discard Indication with RLC-AM and/or RLC-UM | 4.1.2.3 | -| User data existence flag with RLC-AM and/or RLC-UM | 4.1.2.4 | -| Assistance Information Report Polling Flag with RLC-AM and/or RLC-UM | 4.1.2.5 | -| Radio quality assistance information with RLC-AM and/or RLC-UM | 4.1.2.6 | -| DL report NR PDCP PDU SN with RLC-AM | 4.1.2.7 | - -**Table 2-7: IOT Test Cases for Xn implemented in accordance with the NR U-Plane [3] profile** - -The initial test conditions which are common to all Xn test cases are listed below while the test case specific deviations of the initial test conditions will be specified in each of the test cases: - -- The gNBs are running in normal operating state -- The gNBs are physically and logically connected -- Core or Core emulator (5GC capabilities) is physically connected to the gNB(s) -- NG Setup procedure specified in 3GPP TS 38.413 [15] has been completed with the Core or Core emulator -- Protocol Analyzer is physically connected to the Xn link(s) - -## 2.4.1 Xn C-Plane IOT Test Cases - -### 2.4.1.1 Xn Setup - -#### 2.4.1.1.1 Test Purpose - -The purpose of this test case is to verify that the Xn Setup procedure with gNB1 and gNB2 from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.2.1. - -#### 2.4.1.1.2 Minimum Requirements - -DUTs: Two gNBs: - -- DUTs shall apply the parameter condition specified in 4.2.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe Xn procedural flows and content - -#### 2.4.1.1.3 Initial Conditions - -- An SCTP association is successfully established between the two SCTP endpoints (SCTP initiation procedure has taken place before or is taking place with execution of this test case) - -#### 2.4.1.1.4 Procedure - -1. Initiate the Xn Setup procedure in gNB1 - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. O&M command in gNB1 to enable Xn interface - -2. Observe the Protocol Analyzer Xn logs - -#### 2.4.1.1.5 Expected Results and Log Observation - -##### 2.4.1.1.5.1 Expected Results - -The Xn Setup procedure is successfully completed. - -##### 2.4.1.1.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.2.1.1/4.2.1.2. - -### 2.4.1.2 Inter gNB Handover - -#### 2.4.1.2.1 Test Purpose - -The purpose of this test case is to verify that the Inter gNB Handover procedure with source gNB and target gNB from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 6.4.1. - -#### 2.4.1.2.2 Minimum Requirements - -DUTs: Two gNBs (Source gNB and Target gNB): - -- DUTs shall apply the parameter condition specified in 6.4.1 of the NR C-Plane profile specification [2] -- The coverage of source gNB cell and target gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to perform Inter gNB Handover -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -#### 2.4.1.2.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the source gNB and target gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator is within the coverage area of the source gNB cell -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Data transfer between the Application Test Server and Test UE or UE emulator is possible - -#### 2.4.1.2.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the Inter gNB Handover procedure. This involves observing that the user plane data forwarded from the source gNB to the target gNB over the Xn interface during the Inter gNB Handover procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates which are high enough for the source gNB to start buffering user plane downlink data prior to the Inter gNB Handover. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10], 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform Inter gNB Handover Procedure from Source gNB cell to Target gNB cell - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Move the Test UE or UE emulator from the coverage area of source gNB cell towards target gNB cell. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the source gNB cell and the target gNB cell simultaneously. In this specific case, the source gNB cell can start off with low attenuation applied which is subsequently increased. At the same time, the target gNB cell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the Inter gNB Handover. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Inter gNB Handover Procedure. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10], 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.2.5 Expected Results and Log Observation - -##### 2.4.1.2.5.1 Expected Results - -The Inter gNB Handover procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.4.1.2.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 6.4.1.1/6.4.1.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “HANDOVER REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator via the source gNB cell and target gNB cell. - - All U-Plane data recorded in the Xn logs (ie, all U-Plane data forwarded from source gNB to target gNB after step 2) is correctly received by the Test UE or UE emulator. No U-Plane data recorded in the Xn in step 4. -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or emulated UE via the target gNB cell is recorded in the NG logs - -#### 2.4.1.3 S-NG-RAN Node Addition - -##### 2.4.1.3.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN Node Addition procedure with two gNBs, hereafter MgNB and SgNB respectively, from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.1.1. - -##### 2.4.1.3.2 Minimum Requirements - -DUTs: MgNB and SgNB: - -- DUTs shall apply the parameter condition specified in 7.1.1 of the NR C-Plane profile specification [2] -- The coverages of MgNB cell and SgNB cell overlap each other. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN Node Addition -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -#### 2.4.1.3.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible - -#### 2.4.1.3.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator via MgNB - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the S-NG-RAN Node Addition procedure. This involves observing that the user plane data forwarded from the MgNB to the SgNB over the Xn interface during the S-NG-RAN Node Addition procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates which are high enough for the MgNB to start buffering user plane downlink data prior to the addition of the SgNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate, which is calculated based on 3GPP TS 38.211 [10] using the RAN parameters used in this test). - -2. Perform S-NG-RAN Node Addition procedure - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the SgNB cell. In this specific case, the SgNB cell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the S-NG-RAN Node Addition procedure. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during SN terminated Split Bearer(s) operation in NR-DC. This involves observing that the user plane data transferred - -over the Xn in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -One method to stimulate the SN terminated Split Bearer(s) usage of both MgNB and SgNB is to transfer user plane data at data rates high enough for the SgNB to start distributing user plane data to the gNB via the Xn interface. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in both MgNB and SgNB, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.3.5 Expected Results and Log Observation - -##### 2.4.1.3.5.1 Expected Results - -The S-NG-RAN Node Addition procedure is successfully completed. - -##### 2.4.1.3.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.1.1.1/7.1.1.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “QoS Flows Not Admitted List” in “S-NODE ADDITION REQUEST ACKNOWLEDGE” -- “PDU Session Resource Not Admitted List” in “S-NODE ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “S-NODE ADDITION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2: - - o All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator via the MgNB or the SgNB - - o All U-Plane data recorded in the Xn logs which are: - - o Forwarded to the Test UE or UE emulator from the MgNB towards the SgNB via their corresponding established DL Forwarding GTP Tunnels, is correctly received by the Test UE or UE emulator - - o Transmitted to the Test UE or UE emulator from the SgNB to the MgNB, via the established MgNB DL GTP Tunnels, is correctly received by the Test UE or UE emulator via MgNB - -Note: this test verification process does not impose a requirement for the SgNB to transmit the user plane data which it has received from the MgNB (as part of the downlink data forwarding procedure) to the Test UE or UE emulator via the MgNB, but rather it is to verify the correct operation of the transmit operation via MgNB when it is used by the SgNB. - -- Regarding the downlink U-Plane data generated in step 4: - - o All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator via MgNB or SgNB - - o All U-Plane data recorded in the Xn logs (ie, all U-Plane data transferred from SgNB to MgNB) is correctly received by the Test UE or UE emulator via MgNB -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - -- o All U-Plane data transmitted by the Test UE or UE emulator via MgNB or SgNB is recorded in the NG logs -- o All U-Plane data transmitted by the Test UE or UE emulator via MgNB (ie, all U-Plane data to be transferred from MgNB to SgNB) is recorded in the Xn logs - -#### 2.4.1.4 M-NG-RAN node initiated SN modification - -##### 2.4.1.4.1 PDU Session Addition - -###### 2.4.1.4.1.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated SN modification (PDU Session Addition) procedure with MgNB and SgNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.1.1. - -###### 2.4.1.4.1.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.2.1.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated SN modification (PDU Session Addition) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -###### 2.4.1.4.1.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification - -###### 2.4.1.4.1.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator using existing PDU Session - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform M-NG-RAN node initiated SN modification (PDU Session Addition) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Add the PDU Session. One of the possible methods can be to trigger from Test UE or UE emulator or Core or Core emulator (5GC capabilities) in order to add the PDU Session - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds using new PDU Session - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful M-NG-RAN node initiated SN modification (PDU Session Addition). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.4.1.5 Expected Results and Log Observation - -##### 2.4.1.4.1.5.1 Expected Results - -The M-NG-RAN node initiated SN modification (PDU Session Addition) procedure is successfully completed. - -##### 2.4.1.4.1.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.1.1/7.2.1.1.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- After step 2 the added PDU Session is applied: - - o An example of how to observe the PDU Session Addition is to check UE emulator and Core emulator log. The exact method to observe the added PDU Session is out of scope of this specification -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the NG logs is correctly received by the Test UE or emulated UE -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs - -#### 2.4.1.4.2 PDU Session Release - -##### 2.4.1.4.2.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated SN modification (PDU Session Release) procedure with MgNB and SgNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.1.2. - -##### 2.4.1.4.2.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.1.1.2 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated SN modification (PDU Session Release) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content -- At least two PDU Session exists to a Test UE or UE emulator in the NW - -##### 2.4.1.4.2.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification -- At least two PDU Sessions exists to a Test UE or UE emulator in the NW - -##### 2.4.1.4.2.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator using two PDU Sessions - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform M-NG-RAN node initiated SN modification (PDU Session Release) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Release one of PDU Session. One of the possible methods can be to trigger from Test UE or UE emulator or Core or Core emulator (5GC capabilities) in order to release the PDU Session -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds using remaining PDU Session - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful M-NG-RAN node initiated SN modification (PDU Session Release). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.4.2.5 Expected Results and Log Observation - -##### 2.4.1.4.2.5.1 Expected Results - -The M-NG-RAN node initiated SN modification (PDU Session Release) procedure is successfully completed. - -##### 2.4.1.4.2.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.2.1/7.2.1.2.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- After step 2 the Released PDU Session is not applied: - - o An example of how to observe the PDU Session Release is to check the following three points. The exact method to observe the released PDU Session is out of scope of this specification - - o Check that data is flowing the two PDU Sessions before step 2 - - o Check that step 2 (PDU Session Release procedure) performs correctly - - o Check that the data is flowing using the remaining PDU Session in step 4 -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the NG logs is correctly received by the Test UE or emulated UE. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs - -#### 2.4.1.4.3 Security Key change - -##### 2.4.1.4.3.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated SN modification (Security Key change) procedure with MgNB and SgNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.1.4. - -##### 2.4.1.4.3.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.2.1.4 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated SN modification (Security Key change) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -##### 2.4.1.4.3.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification - -##### 2.4.1.4.3.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros) - -2. Perform M-NG-RAN node initiated SN modification (Security Key change) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Perform Intra-gNB-CU handover (M-NG-RAN node initiated) procedure - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful M-NG-RAN node initiated SN modification (Security Key change). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.4.3.5 Expected Results and Log Observation - -##### 2.4.1.4.3.5.1 Expected Results - -The M-NG-RAN node initiated SN modification (Security Key change) procedure is successfully completed. - -##### 2.4.1.4.3.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.4.1/7.2.1.4.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- After step 2 the updated security key is applied in Test UE or UE emulator: - - An example of how to observe the updated security key is to check the UE emulator log. The exact method to observe the updated security key is out of scope of this specification -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data which is recorded in the NG logs, but is not recorded in Xn logs, is correctly received in the PDCP layer or higher layer by the Test UE or emulated UE. - - All U-Plane data recorded in the X2 logs is correctly received by the Test UE or emulated UE via LTE RAT -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs - -#### 2.4.1.4.4 PDU Session Modification - -##### 2.4.1.4.4.1 PDU Session Modification with QoS flow addition - -###### 2.4.1.4.4.1.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow addition) procedure with MgNB and SgNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.1.3.1. - -###### 2.4.1.4.4.1.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow addition) -- Core or Core emulator (5GC): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -#### 2.4.1.4.4.1.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case. - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- UE or UE emulator has registered to the network, ie, Registration procedure and/or Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification - -#### 2.4.1.4.4.1.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow addition) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Add the QoS flow. One of the possible methods can be to trigger from Test UE or UE emulator or Core or Core emulator (5GC capabilities) in order to add the QoS flow - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful M-NG-RAN node initiated SN modification (PDU Session Modification with QoS addition). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer - -1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.4.4.1.5 Expected Results and Log Observation - -##### 2.4.1.4.4.1.5.1 Expected Results - -The M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow addition) procedure is successfully completed. - -##### 2.4.1.4.4.1.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.3.1.1/7.2.1.3.1.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION REQUEST ACKNOWLEDGE” - -The test result shall be determined to be ‘successful with remarks’. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- After step 2 the added QoS flow is applied: - - An example of how to observe the QoS flow addition is to check the following two points. The exact method to observe the added QoS flow is out of scope of this specification - - Check that step 2 (QoS flow addition procedure) performs correctly - - Check that the data is flowing using the two QoS flows in step 4 -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the NG logs is correctly received by the Test UE or emulated UE. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs - -#### 2.4.1.4.4.2 PDU Session Modification with QoS flow release - -##### 2.4.1.4.4.2.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow release) procedure with MgNB and SgNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.1.3.2. - -##### 2.4.1.4.4.2.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow release) -- Core or Core emulator (5GC): used to terminate UEs (emulator) NAS protocol - -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content -- At least two QoS flows exists to a PDU Session - -#### 2.4.1.4.4.2.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- UE or UE emulator has registered to the network, ie, Registration procedure and/or Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile -- At least two QoS flows exists to a Test UE or UE emulator in the NW - -#### 2.4.1.4.4.2.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator using two QoS flows - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow release) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Release the QoS flow. One of the possible methods can be to trigger from Test UE or UE emulator or Core or Core emulator (5GC capabilities) in order to release the QoS flow - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds using remaining QoS flow - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful M-NG-RAN node initiated SN modification (PDU Session Modification with QoS release). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.4.4.2.5 Expected Results and Log Observation - -##### 2.4.1.4.4.2.5.1 Expected Results - -The M-NG-RAN node initiated SN modification (PDU Session Modification with QoS flow release) procedure is successfully completed. - -##### 2.4.1.4.4.2.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.3.2.1/7.2.1.3.2.2. - -The test result shall be determined to be Partial Success if any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION REQUEST ACKNOWLEDGE” - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- After step 2 the Released QoS flow is not applied: - - An example of how to observe the QoS flow release is to check the following three points. The exact method to observe the released QoS flow is out of scope of this specification - - Check that data is flowing the two QoS flows before step 2 - - Check that step 2 (QoS flow release procedure) performs correctly - - Check that the data is flowing using the remaining QoS flow in step 4 -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the NG logs is correctly received by the Test UE or emulated UE -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs - -#### 2.4.1.4.5 SCG Configuration Query - -##### 2.4.1.4.5.1 Test Purpose - -The purpose of this test case is to verify that the SCG Configuration Query procedure with MgNB and SgNB from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 7.2.1.5. - -##### 2.4.1.4.5.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- The coverages of MgNB cell and SgNB cell overlap each other - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform SCG Configuration Query procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe Xn procedural flows and content - -#### 2.4.1.4.5.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.4.1.4.5.4 Procedure - -1. Perform SCG Configuration Query procedure - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Perform Inter-Master Node handover without Secondary Node change procedure (See step 1 in 2.4.1.14.4). - -This test method requires the addition of the following to the initial conditions: - -- o gNB emulator: used to perform Inter-Master Node handover without Secondary Node change procedure - -2. Observe the Protocol Analyzer Xn logs - -#### 2.4.1.4.5.5 Expected Results and Log Observation - -##### 2.4.1.4.5.5.1 Expected Results - -The SCG Configuration Query procedure is successfully completed. - -##### 2.4.1.4.5.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.5.1/7.2.1.5.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -Xn logs recorded in the Protocol Analyzer show that: - -- “After step 1 the scg-CellGroupConfig and/or scg-RB-Config is applied in MgNB: - - o An example of how to observe the scg-CellGroupConfig and/or scg-RB-Config is to check Xn log. The exact method to observe the scg-CellGroupConfig and/or scg-RB-Config is out of scope of this specification. - -#### 2.4.1.4.6 Allowed Band Combination list update - -##### 2.4.1.4.6.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated SN modification (Allowed Band Combination list update) procedure with MgNB and SgNB from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 7.2.1.6. - -##### 2.4.1.4.6.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated SN modification (Allowed Band Combination list update) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -##### 2.4.1.4.6.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -##### 2.4.1.4.6.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform M-NG-RAN node initiated SN modification (Allowed Band Combination list update). - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. The condition by which MgNB update an allowedBC-ListMRDC to the SgNB depends on the MgNB implementation. Still, we can create a situation where Allowed Band Combination list update occurs. One of the possible methods programmable attenuators to simulate varying channel conditions - -between the Test UE or UE emulator and the MgNB SCell. In this specific case, the retained multiple NR SCells are deleted and the MgNB causes Band Combination list to be updated. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator. -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful M-NG-RAN node initiated SN modification (Allowed Band Combination list update). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs. - -#### 2.4.1.4.6.5 Expected Results and Log Observation - -##### 2.4.1.4.6.5.1 Expected Results - -The M-NG-RAN node initiated SN modification (Allowed Band Combination list update) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.4.1.4.6.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.6.1/7.2.1.6.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- After step 2 the updated allowedBC-ListMRDC is applied in SgNB: - - An example of how to observe the updated allowedBC-ListMRDC is to check Xn log. The exact method to observe the updated allowedBC-ListMRDC is out of scope of this specification. -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data which is recorded in the NG logs is correctly received by the Test UE or emulated UE -- Regarding the uplink U-Plane data generated in step 1 after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or emulated UE is recorded in the NG logs - -#### 2.4.1.4.7 PCell Change (Intra-MN) - -##### 2.4.1.4.7.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated SN modification (PCell Change (Intra-MN)) procedure with MgNB and SgNB from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 7.2.1.7. - -#### 2.4.1.4.7.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- MgNB cell (MN) has at least 2 cells configured and in operation -- The coverage of Intra-MgNB primary cell (MN) and SgNB cell (SN) overlap -- The coverage of Intra-MgNB serving cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated SN modification (PCell Change (Intra-MN)) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -#### 2.4.1.4.7.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure has between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.4.1.4.7.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform M-NG-RAN node initiated SN modification (PCell Change (Intra-MN)) on the MgNB side. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Make use of programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the MgNB primary cell and the serving cell simultaneously. In this specific case, the MgNB primary cell can start off with low attenuation applied which is subsequently increased. At the same time, the serving cell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the handover from the primary cell to the serving cell. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator. - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful M-NG-RAN node initiated SN modification (PCell Change (Intra-MN)). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs. - -#### 2.4.1.4.7.5 Expected Results and Log Observation - -##### 2.4.1.4.7.5.1 Expected Results - -The M-NG-RAN node initiated SN modification (PCell Change (Intra-MN)) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.4.1.4.7.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer and the Test UE or UE emulator are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.7.1/7.2.1.7.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data which is recorded in the NG logs is correctly received by the Test UE or emulated UE -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or emulated UE is recorded in the NG logs - -#### 2.4.1.4.8 PDU Session Modification with 5QI change - -##### 2.4.1.4.8.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated SN modification (PDU Session Modification with 5QI change to modify a 5QI (and/or ARP) of the SN terminated split QoS flow from an existing PDU Session) procedure with MgNB and SgNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.1.3.3. - -##### 2.4.1.4.8.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated SN modification (PDU Session Modification) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -#### 2.4.1.4.8.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.4.1.4.8.4 Procedures - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator using an SN terminated split QoS flow from an existing PDU Session - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform M-NG-RAN node initiated SN modification (PDU Session Modification with 5QI change) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Change the 5QI of the QoS flow used in step 1. - -One of the possible methods can be to trigger from Core or Core emulator (5GC capabilities) in order to change the 5QI of the SN terminated split QoS flow of an existing PDU Session (eg, PCF initiated SM Policy Association Modification upon Application Function request) - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds using SN terminated split QoS flow with changed 5QI - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful M-NG-RAN node initiated SN modification (PDU Session Modification with 5qi change). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.4.8.5 Expected Results and Log Observation - -##### 2.4.1.4.8.5.1 Expected Results - -The M-NG-RAN node initiated SN modification (PDU Session Modification with 5QI change) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.4.1.4.8.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer and the Test UE or UE emulator are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.3.3.1/7.2.1.3.3.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- After step 2 the modified 5QI is applied: - -An example of how to observe the 5QI change of the SN terminated split QoS flow from an existing PDU Session is listed below. The exact method to observe the changed 5QI is out of scope of this specification - -Check the following two points - -- Check that step 2 (5QI change with IE “QoS Flows To Be Modified List” included in message “S-Node Modification Request”) performs correctly - - Check that the data is flowing using the QoS flow with the new 5QI in step 4 -- Regarding the downlink U-Plane data generated in step1, after step 2 and in step 4: - - All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator. - - Regarding the uplink U-Plane data generated in step1, after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs - -#### 2.4.1.5 S-NG-RAN node initiated SN modification with MN involvement - -##### 2.4.1.5.1 PDU Session Release - -###### 2.4.1.5.1.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification with MN involvement (PDU Session Release) procedure with MgNB and SgNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.2.2. - -###### 2.4.1.5.1.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.2.2.2 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated SN modification with MN involvement (PDU Session Release) - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content -- At least two PDU Sessions exists to a Test UE or UE emulator in the NW. - -#### 2.4.1.5.1.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] -- At least two PDU Sessions exists to a Test UE or UE emulator in the NW - -#### 2.4.1.5.1.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator using two PDU Sessions - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform S-NG-RAN node initiated SN modification (PDU Session Release) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Release one of PDU Session. One of the possible methods can be to trigger from Test UE or UE emulator or Core or Core emulator (5GC capabilities) in order to release the PDU Session - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds using remaining PDU Session. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful S-NG-RAN node initiated SN modification with MN involvement (PDU Session Release). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.5.1.5 Expected Results and Log Observation - -##### 2.4.1.5.1.5.1 Expected Results - -The S-NG-RAN node initiated SN modification with MN involvement (PDU Session Release) procedure is successfully completed. - -##### 2.4.1.5.1.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.2.2.1/7.2.2.2.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- After step 2 the Released PDU Session is not applied: - - An example of how to observe the PDU Session Release is to check the following three points. The exact method to observe the released PDU Session is out of scope of this specification - - ☞ Check that data is flowing the two PDU Sessions before step 2 - - ☞ Check that step 2 (PDU Session Release procedure) performs correctly - - ☞ Check that the data is flowing using the remaining PDU Session in step 4 -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the NG logs is correctly received by the Test UE or emulated UE -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs - -#### 2.4.1.5.2 Security Key change - -##### 2.4.1.5.2.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification with MN involvement (Security Key change) procedure with MgNB and SgNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.2.3. - -##### 2.4.1.5.2.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.2.2.3 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated SN modification with MN involvement (Security Key change) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -#### 2.4.1.5.2.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.4.1.5.2.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros) - -2. Perform S-NG-RAN node initiated SN modification with MN involvement (Security Key change) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Perform Intra-gNB-CU handover (M-NG-RAN node initiated) procedure - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds using new PDU Session - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful S-NG-RAN node initiated SN modification with MN involvement (Security Key change). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.5.2.5 Expected Results and Log Observation - -##### 2.4.1.5.2.5.1 Expected Results - -The S-NG-RAN node initiated SN modification with MN involvement (Security Key change) procedure is successfully completed. - -##### 2.4.1.5.2.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.2.3.1/7.2.2.3.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- After step 2 the updated security key is applied in Test UE or UE emulator: - - An example of how to observe the updated security key is to check the UE emulator log. The exact method to observe the updated security key is out of scope of this specification -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data which is recorded in the NG logs, but is not recorded in Xn logs, is correctly received in the PDCP layer or higher layer by the Test UE or emulated UE -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs - -#### 2.4.1.5.3 UL Configuration Update - -##### 2.4.1.5.3.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification with MN involvement (UL Configuration Update) procedure with MN and SN from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.2.6. - -##### 2.4.1.5.3.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.2.2 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated SN modification with MN involvement (UL Configuration Update) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -##### 2.4.1.5.3.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed - -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.4.1.5.3.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform UL Configuration Update procedure (SN initiated). - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the SgNB cell. One method is to degrade the radio quality of the SgNB cell and use an O&M command on the SN side to change the UL configuration IE from “shared”, indicating the UL scheduling is performed at both SgNB and MgNB, to “only”, indicating the UL scheduling is performed at the SgNB. - -DC-based PDCP duplication may be optionally activated or deactivated based on the radio quality of the SgNB cell; degrading the radio quality can activate it, while improving it can deactivate it. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator. -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful S-NG-RAN node initiated SN modification with MN involvement (UL Configuration Update). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs. - -#### 2.4.1.5.3.5 Expected Results and Log Observation - -##### 2.4.1.5.3.5.1 Expected Results - -The S-NG-RAN node initiated SN modification with MN involvement (UL Configuration Update) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.4.1.5.3.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.2.6.1/7.2.2.6.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data which is recorded in the NG logs is correctly received by the Test UE or emulated UE -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or emulated UE is recorded in the NG logs - -#### 2.4.1.5.4 PSCell change, Intra gNB-DU - -##### 2.4.1.5.4.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Intra gNB-DU) procedure with MgNB and SgNB from different vendors can be successfully completed, confirming to the NR C-Plane profile specification [2] Section 7.2.2.4. - -##### 2.4.1.5.4.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.2.2.4 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap -- SgNB-DU has at least 2 Cells configured and in operation - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Intra gNB-DU) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -##### 2.4.1.5.4.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the Application Test Server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.4.1.5.4.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the UE or UE emulator. - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Intra gNB-DU). - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Make use of programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the Source PSCell and the Target PSCell simultaneously. In this specific case, the Source PSCell can start off with low attenuation applied which is subsequently increased. At the same time, the Target PSCell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the PSCell change. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator. - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Intra gNB-DU). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs. - -#### 2.4.1.5.4.5 Expected Results and Log Observation - -##### 2.4.1.5.4.5.1 Expected Results - -The S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Intra gNB-DU) procedure is successfully completed. - -##### 2.4.1.5.4.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.2.4.1/7.2.2.4.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “S-NODE MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs - -#### 2.4.1.5.5 PSCell change, Inter gNB-DU - -##### 2.4.1.5.5.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Inter gNB-DU) procedure with MgNB and SgNB from different vendors can be successfully completed, confirming to the NR C-Plane profile specification [2] Section 7.2.2.5. - -##### 2.4.1.5.5.2 Minimum Requirements - -DUTs: Two gNBs (MgNB, SgNB): - -- DUTs shall apply the parameter condition specified in 7.2.2.5 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell and SgNB cell overlap -- SgNB has at least 2 Cells configured and in operation - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Inter gNB-DU) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -##### 2.4.1.5.5.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the Application Test Server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -##### 2.4.1.5.5.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the UE or UE emulator. - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Inter gNB-DU). - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Make use of programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the Source PSCell and the Target PSCell in SgNB simultaneously. In this specific case, the Source PSCell can start off with low attenuation applied which is subsequently increased. At the same time, the Target PSCell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the PSCell change. -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator. - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Inter gNB-DU). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs. - -#### 2.4.1.5.5.5 Expected Results and Log Observation - -##### 2.4.1.5.5.5.1 Expected Results - -The S-NG-RAN node initiated SN modification with MN involvement (PSCell change, Inter gNB-DU) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.4.1.5.5.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.2.5.1/7.2.2.5.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “S-NODE MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs - -#### 2.4.1.5.6 Measurement Gap Coordination Procedure (SN initiated) - -##### 2.4.1.5.6.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification with MN involvement (Measurement gap coordination) procedure with MgNB and SgNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.2.7. - -##### 2.4.1.5.6.2 Minimum Requirements - -DUTs: Master gNB (MgNB) and Secondary gNB (SgNB): - -- DUTs shall apply the parameter condition specified in 7.2.2.7 of the NR C-Plane profile specification [2] -- The coverage of MgNB and SgNB cells overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to trigger the UE measurement transfer procedure using Measurement Report message and perform S-NG-RAN node initiated SN modification with MN involvement (Measurement gap coordination) procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the core network, ie, 5GC side -- Protocol Analyzer: used to record and observe Xn procedural flows and content, and NG-U UP content - -#### 2.4.1.5.6.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- The Test UE or UE emulator is within the coverage area of the MgNB and of the SgNB cells -- The test UE or UE emulator has registered to the network, ie, Registration procedure and the Service Request procedure specified in NR C-Plane profile specification [2] Section 6.1.1 has been successfully completed. -- The S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the application test server and test UE or UE emulator is possible - -#### 2.4.1.5.6.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during the S-NG-RAN node initiated SN modification with MN involvement (Measurement gap coordination) procedure. It is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform S-NG-RAN node initiated SN modification with MN involvement (Measurement gap coordination) procedure - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. An SgNB receives a UE measurement transfer as specified in 7.5.1 of NR C-Plane profile specification [2]. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful S-NG-RAN node initiated SN modification with MN involvement (Measurement gap coordination) procedure. - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.5.6.5 Expected Results and Log Observation - -##### 2.4.1.5.6.5.1 Expected Results - -The S-NG-RAN node initiated SN modification with MN involvement (Measurement gap coordination) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.4.1.5.6.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.2.7.1/7.2.2.7.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “S-NODE MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs - -#### 2.4.1.5.7 CellGroupConfig change (SN-DU initiated) - -##### 2.4.1.5.7.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification with MN involvement (CellGroupConfig change (SN-DU initiated)) procedure with MgNB and SgNB from different vendors, confirming to the NR C-Plane profile specification [2] Section 7.2.2.8. - -##### 2.4.1.5.7.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.2.2.8 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated SN modification with MN involvement (CellGroupConfig change (SN-DU initiated)) procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol - -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side - -#### 2.4.1.5.7.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.4.1.5.7.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros) - -2. Perform S-NG-RAN node initiated SN modification with MN involvement (CellGroupConfig change (SN-DU initiated)) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Perform waveform switching when the UE is in an area with poor coverage in the SCG - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful S-NG-RAN node initiated SN modification with MN involvement (CellGroupConfig change (SN-DU initiated)). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.5.7.5 Expected Results and Log Observation - -##### 2.4.1.5.7.5.1 Expected Results - -The S-NG-RAN node initiated SN modification with MN involvement (CellGroupConfig change (SN-DU initiated)) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible - -#### 2.4.1.5.67.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.2.8.1/7.2.2.8.2. - -If any of the following listed IEs is observed in the Xn logs: - -“Criticality Diagnostics” in “S-NODE MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - -- o All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator. - -Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - -- o All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs. - -#### 2.4.1.6 S-NG-RAN node initiated SN modification without MN involvement - -##### 2.4.1.6.1 SRB3 not supported - -###### 2.4.1.6.1.1 SN Modification – SCell(s) Addition / Release - -###### 2.4.1.6.1.1.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification without MN involvement (SRB3 not supported (SCell(s) Addition / Release)) procedure with MgNB and SgNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.3.1.1. - -###### 2.4.1.6.1.1.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.2.3.1.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR: used to perform S-NG-RAN node initiated SN modification without MN involvement (SRB3 not supported (SN Modification – SCell(s) Addition / Release)) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -###### 2.4.1.6.1.1.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.4.1.6.1.1.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform S-NG-RAN node initiated SN modification without MN involvement (SRB3 not supported (SN Modification – SCell Addition)) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the SN cell. In this specific case, the candidate SCell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the SCell Addition using the Measurement results. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful S-NG-RAN node initiated SN modification without MN involvement (SRB3 not supported (SN Modification – SCell Addition)). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -5. Perform S-NG-RAN node initiated SN modification without MN involvement (SRB3 not supported (SN Modification – SCell Release)) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One possible method is to use one of the programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the SN SCell. In this specific case, the candidate SCell can start off with low attenuation applied which is subsequently increased to a level which can trigger the SCell Release using the Measurement results. The Measurement report is sent by MN via RRC Transfer procedure. It is defined in the 5.7.1 of the NR C-Plane profile specification [2]. - -6. Stop data transfer between the Application Test Server and the Test UE or UE emulator -7. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful S-NG-RAN node initiated SN modification without MN involvement (SRB3 not supported (SN Modification – SCell Release)). - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -8. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.6.1.1.5 Expected Results and Log Observation - -##### 2.4.1.6.1.1.5.1 Expected Results - -The S-NG-RAN node initiated SN modification without MN involvement (SRB3 not supported (SCell(s) Addition / Release)) procedure is successfully completed. All the data generated is correctly received by Test UE or UE emulator after the addition and release procedures. - -##### 2.4.1.6.1.1.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.3.1.1.1/7.2.3.1.1.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the NG log is correctly received by the Test UE or UE emulator. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs -- Regarding the downlink U-Plane data generated after step 5 and in step 7: - - o All U-Plane data recorded in the NG log is correctly received by the Test UE or UE emulator. -- Regarding the uplink U-Plane data generated after step 5 and in step 7: - - o All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs - -#### 2.4.1.6.2 SRB3 supported - -##### 2.4.1.6.2.1 Intra gNB-DU PSCell Change using SRB3 - -###### 2.4.1.6.2.1.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Intra gNB-DU PSCell Change using SRB3)) procedure with MN and SN from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.3.2.1. - -###### 2.4.1.6.2.1.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in Sections 7.2.3/7.2.3.2 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cells (SN) overlap. -- SgNB has at least 2 Cells configured and in operation. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Intra gNB-DU PSCell Change using SRB3)). -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol. -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side. -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content. - -#### 2.4.1.6.2.1.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions is applicable for this specific test case. - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed. -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell. -- Data transfer between the application test server and Test UE or UE emulator is possible. -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2]. - -#### 2.4.1.6.2.1.4 Procedure - -1. Perform the data transfer in both directions between the Application Test Server and Test UE or UE emulator. -2. Perform the S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Intra gNB-DU PSCell Change using SRB3)). - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. There should be at least two SgNB cells within the coverage of a cell under MgNB. The first cell under SgNB which is PSCell and the second cell under SgNB which is not PSCell. If the tester manually degrades the radio quality of the first SgNB cell this can be the trigger of the PSCell Change procedure. - -One possible method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the first SgNB cell. In this specific case, the first SgNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger the Intra gNB-DU PSCell Change procedure. - -3. Stop data transfer between the Application Test Server and Test UE or UE emulator. - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Intra gNB-DU PSCell Change using SRB3)) in both directions between the Test UE or UE emulator and the Application Test Server. - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs. - -#### 2.4.1.6.2.1.5 Expected Results and Log Observation - -##### 2.4.1.6.2.1.5.1 Expected Results - -The S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Intra gNB-DU PSCell Change using SRB3)) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.4.1.6.2.1.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.3.2.1.1/7.2.3.2.1.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the NG log is correctly received by the Test UE or UE emulator. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs. - -#### 2.4.1.6.2.2 Inter gNB-DU PSCell Change using SRB3 - -##### 2.4.1.6.2.2.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Inter gNB-DU PSCell Change using SRB3)) procedure with MgNB and SgNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.2.3.2.2. - -##### 2.4.1.6.2.2.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in Sections 7.2.3/7.2.3.2 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cells (SN) overlap -- SgNB has at least 2 Cells configured and in operation - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Inter gNB-DU PSCell Change using SRB3)). -- Core or Core emulator (5GC): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -#### 2.4.1.6.2.2.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and/or Service Request procedure specified in NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cells -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.4.1.6.2.2.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Perform the S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Inter gNB-DU PSCell Change using SRB3)) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT - -- a. One possible method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the source PSCell and the target PSCell in SgNB simultaneously. In this specific case, the source PSCell can start off with low attenuation applied which is subsequently increased. At the same time, the target PSCell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the Inter gNB-DU PSCell Change procedure -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - 4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Inter gNB-DU PSCell Change using SRB3)). This involves observing that the user plane data transferred in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] using the RAN parameters used in this test) - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.6.2.2.5 Expected Results and Log Observation - -##### 2.4.1.6.2.2.5.1 Expected Results - -The S-NG-RAN node initiated SN modification without MN involvement (SRB3 supported (Inter gNB-DU PSCell Change using SRB3)) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.4.1.6.2.2.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.3.2.2.1/7.2.3.2.2.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE MODIFICATION CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or emulated UE is recorded in the NG logs - -#### 2.4.1.7 M-NG-RAN node initiated S-NG-RAN node Release without keeping UE - -##### 2.4.1.7.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated S-NG-RAN node Release without keeping UE procedure with MN (MgNB) and SN (SgNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 7.3.1. - -##### 2.4.1.7.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.3.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated S-NG-RAN node Release without keeping UE -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn procedural flows and content - -##### 2.4.1.7.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.4.1.7.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform M-NG-RAN node initiated S-NG-RAN node Release without keeping UE - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One possible method is to use O&M command in 5GC or MN side to trigger UE context release - -3. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.7.5 Expected Results and Log observation - -##### 2.4.1.7.5.1 Expected Results - -The M-NG-RAN node initiated S-NG-RAN node Release without keeping UE procedure is successfully completed. All the data generated is correctly received by UE after release procedure. - -##### 2.4.1.7.5.2 Log observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.3.1.1/7.3.1.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE RELEASE REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1: - - o All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator -- Regarding the uplink U-Plane data generated in step 1: - - o All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs - -## 2.4.1.8 M-NG-RAN node initiated S-NG-RAN node Release with keeping UE - -### 2.4.1.8.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN node initiated S-NG-RAN node Release with keeping UE procedure with MN (MgNB) and SN (SgNB) from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.3.2. - -### 2.4.1.8.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.3.2 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform M-NG-RAN node initiated S-NG-RAN node Release with keeping UE -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn procedural flows and content - -### 2.4.1.8.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.4.1.8.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the M-NG-RAN node initiated S-NG-RAN node Release with keeping UE procedure. This involves observing that the user plane data forwarded from the SgNB to the MgNB over the Xn interface during the M-NG-RAN node initiated S-NG-RAN node Release with keeping UE procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates high enough for the SgNB to start buffering user plane downlink data prior to the release of the SgNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the - -maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform M-NG-RAN node initiated S-NG-RAN node Release with keeping UE - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Provoke a Radio Link Failure in SCG, so MgNB receives SCGFailureInformation message from the UE. One possible method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the SgNB cell. In this specific case, the SgNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger the Radio link failure scenario. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful M-NG-RAN node initiated S-NG-RAN node Release with keeping UE. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.8.5 Expected Results and Log observation - -##### 2.4.1.8.5.1 Expected Results - -The M-NG-RAN node initiated S-NG-RAN node Release with keeping UE procedure is successfully completed. All the data generated is correctly received by UE after release procedure. - -##### 2.4.1.8.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.3.2.1/7.3.2.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE RELEASE REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator - - o All U-Plane data recorded in the Xn logs (ie, all U-Plane data forwarded from SgNB to MgNB in step 1, from SgNB to MgNB after step 2) is correctly received by the Test UE or UE emulator. No U-Plane data recorded in the Xn in step 4. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs - -## 2.4.1.9 S-NG-RAN node initiated S-NG-RAN node Release - -### 2.4.1.9.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN node initiated S-NG-RAN node Release procedure with MN (MgNB) and SN (SgNB) from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.3.3. - -### 2.4.1.9.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.3.3 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform S-NG-RAN node initiated S-NG-RAN node Release -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn procedural flows and content - -### 2.4.1.9.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.4.1.9.4 Procedure - -There are two options for this procedure, as shown in Figure 7.3.3.1-1 in the NR C-Plane profile specification [2]. - -OPT 1 (with keeping UE case) is below: - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the S-NG-RAN node initiated S-NG-RAN node Release procedure. This involves observing that the user plane data forwarded from the SgNB to the MgNB over the Xn interface during the S-NG-RAN node initiated S-NG-RAN node Release procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates high enough for the SgNB to start buffering user plane downlink data prior to the release of the SgNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform S-NG-RAN node initiated S-NG-RAN node Release - -A few examples of how this procedure can be performed (or triggered) are listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- Block cell in SgNB. One method is to use O&M command in the SgNB to block the cell -- Provoke conditions in a way that the SgNB detects that the RLC exceeds its maximum downlink retransmission. One method is to vary the channel conditions between the SgNB and the Test UE or UE emulator so that the emulated interference can be significant enough to increase RLC retransmissions to exceed the maximum downlink retransmission level - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 second. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful S-NG-RAN node initiated S-NG-RAN node Release. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -OPT 2 (without keeping UE case) is below: - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform S-NG-RAN node initiated S-NG-RAN node Release - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- One method is to use O&M command in 5GC or MN side to trigger UE context release - -3. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.9.5 Expected Results and Log observation - -##### 2.4.1.9.5.1 Expected Results - -The S-NG-RAN node initiated S-NG-RAN node Release procedure is successfully completed. All the data generated is correctly received by UE after release procedure. - -##### 2.4.1.9.5.2 Log observation - -Xn logs recorded in the Protocol Analyzer and the Test UE or UE emulator are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.3.3.1/7.3.3.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “S-NODE RELEASE CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1: - - All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator - - All U-Plane data recorded in the Xn logs (ie, all U-Plane data forwarded from SgNB to MgNB) is correctly received by the Test UE or UE emulator - -In OPT1, NG logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 3: - - All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator -- Regarding the uplink U-Plane data generated in step 3: - - All U-Plane data transmitted by the Test UE or UE emulator is recorded in the NG logs - -## 2.4.1.10 Resource Status Reporting Initiation - -### 2.4.1.10.1 Test Purpose - -The purpose of this test case is to verify that the Resource Status Reporting Initiation procedure with gNB1 and gNB2 from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.2.9.1. - -### 2.4.1.10.2 Minimum Requirements - -DUTs: Two gNBs: - -Testing tools which are required for this test scenario: - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe Xn procedural flows and content - -### 2.4.1.10.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case - -- Xn Setup procedure has been successfully completed between the gNB1 and gNB2 according to the NR C-Plane profile specification [2] - -### 2.4.1.10.4 Procedure - -1. Perform the Resource Status Reporting Initiation procedure to start a measurement in gNB1 - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One method is to use O&M command in the gNB1 in order to initiate the Resource Status Reporting Initiation procedure to start the measurement -2. Perform the Resource Status Reporting Initiation procedure to add cells to report for a measurement in gNB1 - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One method is to use O&M command in the gNB1 in order to initiate the Resource Status Reporting Initiation procedure to add cells to the measurement -3. Perform the Resource Status Reporting Initiation procedure to stop a measurement in gNB1. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. One possible method is to use O&M command in the gNB1 in order to initiate the Resource Status Reporting Initiation procedure to stop the measurement -4. Observe the Protocol Analyzer Xn logs - -#### 2.4.1.10.5 Expected Results and Log Observation - -##### 2.4.1.10.5.1 Expected Results - -The start of the measurement is successfully completed by performing the Resource Status Reporting Initiation procedure in step1. - -The cell addition for the measurement initiated in step1 is successfully completed by performing the Resource Status Reporting Initiation procedure in step2. - -The stop of the measurement is successfully completed by performing the Resource Status Reporting Initiation procedure in step3. - -##### 2.4.1.10.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.2.9.1.1/4.2.9.1.2. - -If any of the following listed IEs is observed in the Xn logs - -- “Criticality Diagnostics” in “RESOURCE STATUS RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -#### 2.4.1.11 Resource Status Reporting - -##### 2.4.1.11.1 Test Purpose - -The purpose of this test case is to verify that the Resource Status Reporting procedure with gNB1 and gNB2 from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.2.9.2. - -##### 2.4.1.11.2 Minimum Requirements - -DUTs: Two gNBs: - -Testing tools which are required for this test scenario: - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe Xn procedural flows and content - -##### 2.4.1.11.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the gNB1 and gNB2 according to the NR C-Plane profile specification [2] - -#### 2.4.1.11.4 Procedure - -1. Perform the Resource Status Reporting procedure from the gNB2 to report the result of on-going load measurements - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Perform the Resource Status Reporting Initiation procedure (See step 1 in 2.4.1.10.4) - -Note: How to perform the specific procedures for the traffic load are out of scope of this specification. - -2. Observe the Protocol Analyzer Xn logs - -#### 2.4.1.11.5 Expected Results and Log Observation - -##### 2.4.1.11.5.1 Expected Results - -The Resource Status Reporting procedure is successfully completed. - -##### 2.4.1.11.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.2.9.2.1/4.2.9.2.2. - -#### 2.4.1.12 Master Node to gNB Change - -##### 2.4.1.12.1 Test Purpose - -The purpose of this test case is to verify that the Master Node to gNB Change procedure with MgNB, SgNB and T-gNB from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 7.6.1. - -##### 2.4.1.12.2 Minimum Requirements - -DUTs: Three gNBs (MgNB – S-MN, SgNB – S-SN, T-gNB): - -- DUTs shall apply the parameter condition specified in 7.6.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (S-MN), SgNB cell (S-SN) and T-gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform Master Node to gNB Change -- Core or Core emulator (5GC): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -##### 2.4.1.12.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB, SgNB and T-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and/or Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification - -#### 2.4.1.12.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the Master Node to gNB Change procedure. This involves observing that the user plane data forwarded from the SgNB to the MgNB over the Xn interface during the Master Node to gNB Change procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates high enough for the SgNB to start buffering user plane downlink data prior to the release of the SgNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform the Master Node to gNB Change - -A few examples of how this procedure can be performed (or triggered) are listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. The handover to T-gNB is decided by the Master Node based on the Measurement Report sent from the Test UE or UE emulator. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and Master Node cell and the T-gNB cell simultaneously. In this specific case, the Master Node cell can start off with low attenuation applied which is subsequently increased. At the same time, the T-gNB cell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the Master Node to gNB Change procedure. - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator - -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Master Node to gNB Change. This involves observing that the user plane data transferred in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.12.5 Expected Results and Log Observation - -##### 2.4.1.12.5.1 Expected Results - -The Master Node to gNB Change procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.4.1.12.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.6.1.1/7.6.1.2. - -The test result shall be determined to be Partial Success if any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “HADOVER REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “S-NODE RELEASE REQUEST ACKNOWLEDGE” - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator - - All U-Plane data recorded in the Xn logs (ie, all U-Plane data forwarded from SgNB to MgNB in step 1, from SgNB to MgNB after step 2, from MgNB to T-gNB after step 2) is correctly received by the Test UE or UE emulator. No U-Plane data recorded in the Xn logs in step 4. -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or emulated UE is recorded in the NG logs - -#### 2.4.1.13 Reset - -##### 2.4.1.13.1 Test Purpose - -The purpose of this test case is to verify that the Reset procedure with gNB1 and gNB2 from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 4.2.2. - -##### 2.4.1.13.2 Minimum Requirements - -DUTs: Two gNBs - -- The coverage of gNB1 cell and gNB2 cells overlap - -Testing tools which are required for this test scenario: - -- Test UEs or UE emulator which is capable of supporting NR: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe Xn procedural flows and content - -##### 2.4.1.13.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the gNB1 and gNB2 according to the NR C-Plane profile specification [2] -- Multiple Test UEs or emulated UEs have registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the gNB1 cell and gNB2 cell -- Data transfer between the Application Test Server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the gNB1 and gNB2 been successfully completed - -#### 2.4.1.13.4 Procedure - -1. Perform the gNB1 initiated Reset procedure over Xn to indicate the release of all allocated UE contexts - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation. One possible method is to use O&M command in the gNB1 to deactivate all cells serving UEs - -2. Perform the gNB1 initiated Reset procedure over Xn to indicate the release of a part of allocated UE contexts - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation. One method is to use O&M command in the gNB1 in order to deactivate few cells serving UEs - -3. Observe the Protocol Analyzer Xn link logs - -#### 2.4.1.13.5 Expected Results and Log Observation - -##### 2.4.1.13.5.1 Expected Results - -The reset is successfully completed by the gNB1 initiated Reset procedure in step 1. All of the UE contexts affected by the gNB1 initiated Reset procedure is successfully released in the gNB2 and data transfer between the Application Test Server and the Test UE or UE emulator has ended. - -The partial reset is successfully completed by the gNB1 initiated Reset procedure in step 2. The part of the UE contexts affected by the gNB1 initiated Reset procedure is successfully released in the gNB2 and data transfer between the Application Test Server and the Test UE or UE emulator has ended. - -##### 2.4.1.13.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.2.2.1/4.2.2.2.1/4.2.2.2.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “RESET ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -#### 2.4.1.14 Inter-Master Node Handover (Without SN Change) - -##### 2.4.1.14.1 Test Purpose - -The purpose of this test case is to verify that an Inter-Master Node Handover (Without SN Change) procedure with three gNBs from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 7.7.1. - -#### 2.4.1.14.2 Minimum Requirements - -DUTs: Three gNBs (Source gNB (S-MN), Secondary gNB (SN), Target gNB (T-MN)): - -DUTs shall apply the parameter condition specified in 7.7.1 of the NR C-Plane profile specification [2] - -- The coverage of Source gNB cell and Secondary gNB cell overlap -- The coverage of Target gNB cell and Secondary gNB cell overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform Inter-Master Node Handover (Without SN Change) procedure -- Core or Core emulator (5GC): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -#### 2.4.1.14.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the S-MN, SN and T-MN according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and/or Service Request procedure specified in NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the Source gNB cell (S-MN) and Secondary gNB cell (SN) -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the Source gNB (S-MN) and Secondary gNB (SN) has been successfully completed according to NR C-Plane profile specification - -#### 2.4.1.14.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the Inter-Master Node Handover procedure. - -This involves observing that the user plane data forwarded from the source en-gNB to the target en-gNB, over the Xn interface during the Inter-Master Node Handover procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates which are high enough for the source en-gNB to start buffering user plane downlink data prior to the change of the en-gNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in both the LTE RAT and NR RAT, which is calculated based on 3GPP TS 36.211 [9], 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform Inter-Master Node Handover (without SN Change) procedure from source gNB (S-MN) to target gNB (T-MN). - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. The Test UE or UE emulator sends a Measurement Report to the source gNB (S-MN). One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and source gNB (S-MN) and the target gNB (T-MN) simultaneously. In this specific case, the source gNB (S-MN) cell can start off with low attenuation applied which is subsequently increased. At the same time, the target gNB (T-MN) cell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the measurement report to be sent to the source gNB (S-MN). -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Inter-Master Node Handover (Without SN Change) procedure. This involves observing that the user plane data transferred in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.14.5 Expected Results and Log Observation - -##### 2.4.1.14.5.1 Expected Results - -The Inter-Master Node Handover (Without SN Change) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.4.1.14.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.7.1.1/7.7.1.2. - -The test result shall be determined to be Partial Success if any of the following listed IEs is observed in the Xn logs: - -- “PDU Session Resources Not Admitted List” in “SGNB ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “SGNB ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “SGNB RELEASE REQUEST ACKNOWLEDGE” -- “Configuration rejected” in “SGNB RECONFIGURATION COMPLETE” - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator - - o All U-Plane data recorded in the Xn logs (ie, all U-Plane data forwarded from S-MN to T-MN) is correctly received by the Test UE or UE emulator -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - -- o All U-Plane data transmitted by the Test UE or emulated UE is recorded in the NG logs -- o All U-Plane data transmitted by the Test UE or UE emulator is recorded in the Xn logs (ie, all U-Plane data forwarded from T-MN to S-MN) is recorded in the Xn logs - -## 2.4.1.15 Secondary Node Change (SN initiated) - -### 2.4.1.15.1 Test Purpose - -The purpose of this test case is to verify that the S-NG-RAN initiated Secondary Node Change procedure with MgNB, SgNB and T-gNB from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 7.8.1. - -### 2.4.1.15.2 Minimum Requirements - -DUTs: Three gNBs (Master gNB (MN), Source gNB (S-SN), Target gNB (T-SN)): - -- DUTs shall apply the parameter condition specified in 7.8.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN), SgNB cell (S-SN) and T-gNB cell (T-SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR-DC: used to perform Secondary Node Change procedure (SN initiated) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn links procedural flows and content, NG-U UP content - -### 2.4.1.15.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB, SgNB and T-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and/or Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification -- Secondary Node is Source gNB (S-SN) at the start of this procedure -- Data transfer between the application test server and Test UE or UE emulator is possible (via NR RAT's) - -### 2.4.1.15.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the Secondary Node Change procedure (SN initiated). This involves observing that the user plane data forwarded from the Source gNB (S-SN) to the Master gNB (MN) and from the Master gNB - -(MN) to the Target gNB (T-SN) over the Xn interface during the Secondary Node Change procedure (SN initiated) can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates high enough for the Source gNB to start buffering user plane downlink data prior to the release of the Source gNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform Secondary Node Change Procedure from Source gNB cell (S-SN) to Target gNB cell (T-SN) - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Move the Test UE or UE emulator from the coverage area of Source gNB cell (S-SN) towards Target gNB cell (T-SN). One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the Source gNB cell (S-SN) and the Target gNB cell (T-SN) simultaneously. In this specific case, the Source gNB cell (S-SN) can start off with low attenuation applied which is subsequently increased. At the same time, the Target gNB cell (T-SN) can start off with high attenuation applied which is subsequently lowered to a level which can trigger the SN change procedure from S-SN to T-SN. -3. Stop data transfer between the Application Test Server to the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Secondary Node Change procedure (SN initiated). This involves observing that the user plane data transferred in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.15.5 Expected Results and Log Observation - -##### 2.4.1.15.5.1 Expected Results - -The Secondary Node Change procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.4.1.15.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 7.8.1.1/7.8.1.2. - -If any of the following listed IEs is observed in the Xn logs - -- “PDU Session Resources Not Admitted List” in “S-NODE ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “S-NODE ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “S-NODE CHANGE CONFIRM” - -the test result shall be determined to be ‘successful with remarks’. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator - - All U-Plane data recorded in the Xn logs (ie, all U-Plane data forwarded from Source gNB to MgNB to Target gNB after step 2 and from Target gNB to MgNB in step 4) is correctly received by the Test UE or UE emulator -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or emulated UE is recorded in the NG logs - - All U-Plane data transmitted by the Test UE or emulated UE is recorded in the Xn logs (ie, all U-Plane data forwarded from MgNB to Source gNB after step 2 and from MgNB to Target gNB in step 4) - -## 2.4.1.16 NG-RAN Node Configuration Update - -### 2.4.1.16.1 Test Purpose - -The purpose of this test case is to verify that the NG-RAN Node Configuration Update procedure, used to update application-level configuration data, between two NG-RAN over the Xn-C interface, with gNB1 and gNB2 from different vendors can successfully be completed, conforming to the NR C-Plane profile specification [2] Section 4.2.8.1 - -### 2.4.1.16.2 Minimum Requirements - -DUTs: Two gNBs: - -- DUTs shall apply the parameter condition specified in 4.2.8.1 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Protocol Analyzer: used to record and observe Xn procedural flows and content - -### 2.4.1.16.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the gNB1 and gNB2 according to the NR C-Plane profile specification [2] - -### 2.4.1.16.4 Procedure - -1. Initiate NG-RAN Node Configuration Update procedure to add cell(s) in gNB1 - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell activation. One method is to use O&M command in the gNB1 in order to activate cells. - -2. Initiate NG-RAN Node Configuration Update procedure to modify cell(s) in gNB1 - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell modification. One method is to use O&M command in the gNB1 in order to modify cells, eg, change DL Transmission Bandwidth. - -3. Initiate NG-RAN Node Configuration Update procedure to delete cell(s) in gNB1 - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deletion. One method is to use O&M command in the gNB1 in order to delete cells. - -4. Initiate NG-RAN Node Configuration Update procedure to deactivate cell(s) in gNB1 - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stimulate cell deactivation. One method is to use O&M command in the gNB1 in order to deactivate cells. - -5. Observe the Protocol Analyzer Xn logs. - -#### 2.4.1.16.5 Expected Results and Log Observation - -##### 2.4.1.16.5.1 Expected Results - -The NG-RAN Node Configuration Update procedure is successfully completed each time after step 1 – step 4. - -##### 2.4.1.16.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 4.2.8.1.1/4.2.8.1.2 - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -#### 2.4.1.17 UE measurement transfer - -##### 2.4.1.17.1 Test Purpose - -The purpose of this test case is to verify that the UE measurement transfer procedure with MN (MgNB) and SN (SgNB) from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 7.5.1. - -##### 2.4.1.17.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply the parameter condition specified in 7.5.1 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN), SgNB cell (SN) overlap -- SN has at least 2 cells configured and in operation - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform UE measurement transfer procedure using MeasurementReport message -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn procedural flows and content - -#### 2.4.1.17.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and/or Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and one of SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the application test server and Test UE or UE emulator is possible (via NR RATs) - -#### 2.4.1.17.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly during the UE measurement transfer procedure. This involves observing that the user plane data transferred over the Xn in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform UE measurement transfer procedure - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. The condition by which UE sends a MeasurementReport message to the MN depends on the configuration done by MN. Still, we can create a situation where UE measurement transfer occurs. There should be at least two SN cells within the coverage of a cell under MN. The first cell under SN which is PSCell and the second cell under SN which is not PSCell. If the tester manually degrades the radio quality of the first SN cell this can be the trigger of the UE measurement transfer procedure. - -One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the first SN cell. In this specific case, the first SN cell can start off with low attenuation applied which is subsequently increased to a level which can trigger the UE measurement transfer procedure. - -3. Observe the Protocol Analyzer Xn logs and Test UE or UE emulator logs. - -#### 2.4.1.17.5 Expected Results and Log Observation - -##### 2.4.1.17.5.1 Expected Results - -The UE measurement transfer procedure is successfully completed. - -##### 2.4.1.17.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 7.5.1.1/7.5.1.2. - -NG logs recorded in the Protocol Analyzer and the Test UE or UE emulator show that: - -- Regarding the downlink U-Plane data generated in step 1: - - All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator via NR RAT -- Regarding the downlink U-Plane data generated in step 1: - - All U-Plane data transmitted by the Test UE or UE emulator via NR RAT is recorded in the NG logs - -#### 2.4.1.18 MN initiated SN Change - -##### 2.4.1.18.1 Test Purpose - -The purpose of this test case is to verify that the M-NG-RAN initiated Secondary Node Change procedure with MgNB, SgNB and T-gNB from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] Section 7.8.2. - -##### 2.4.1.18.2 Minimum Requirements - -DUTs: Three gNBs (Master gNB (MN), Source gNB (S-SN), Target gNB (T-SN)): - -- DUTs shall apply the parameter condition specified in 7.8.2 of the NR C-Plane profile specification [2] -- The coverage of MgNB cell (MN), SgNB cell (S-SN) and T-gNB cell (T-SN) overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR-DC: used to perform Secondary Node Change procedure (MN initiated) -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn links procedural flows and content, NG-U UP content - -##### 2.4.1.18.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB, SgNB and T-gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and/or Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification -- Secondary Node is Source gNB (S-SN) at the start of this procedure -- Data transfer between the application test server and Test UE or UE emulator is possible - -##### 2.4.1.18.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the Secondary Node Change procedure (MN initiated). This involves observing that the user plane data forwarded from the Source gNB (S-SN) to the Master gNB (MN) and from the Master gNB (MN) to the Target gNB (T-SN) over the Xn interface during the Secondary Node Change procedure (MN initiated) can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates high enough for the Source gNB to start buffering user plane downlink data prior to the release of the Source gNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform Secondary Node Change Procedure from Source gNB cell (S-SN) to Target gNB cell (T-SN). - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Move the Test UE or UE emulator from the coverage area of Source gNB cell (S-SN) towards Target gNB cell (T-SN). One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the Source gNB cell (S-SN) and the Target gNB cell (T-SN) simultaneously. In this specific case, the Source gNB cell (S-SN) can start off with low attenuation applied which is subsequently increased. At the same time, the Target gNB cell (T-SN) can start off with high attenuation applied which is subsequently lowered to a level which can trigger the SN change procedure from S-SN to T-SN. -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator. -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Secondary Node Change procedure (MN initiated). This involves observing that the user plane data transferred in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs. - -#### 2.4.1.18.5 Expected Results and Log Observation - -##### 2.4.1.18.5.1 Expected Results - -The Secondary Node Change procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.4.1.18.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flow specified in the NR C-Plane profile specification [2] Sections 7.8.2.1/7.8.2.2. - -If any of the following listed IEs is observed in the Xn logs - -- “PDU Session Resources Not Admitted List” in “S-NODE ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “S-NODE ADDITION REQUEST ACKNOWLEDGE” - -- “QoS Flows Not Admitted List” in “S-NODE ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “S-NODE RELEASE REQUEST ACKNOWLEDGE” -- “Configuration rejected by the M-NG-RAN node” in “S-NODE RECONFIGURATION COMPLETE” - -the test result shall be determined to be ‘successful with remarks’. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator - - All U-Plane data recorded in the Xn logs (ie, all U-Plane data forwarded from Source gNB to MgNB to Target gNB after step 2 and from Target gNB to MgNB in step 5) is correctly received by the Test UE or UE emulator -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or UE is recorded in the NG logs - - All U-Plane data transmitted by the Test UE or emulated UE is recorded in the Xn logs (ie, all U-Plane data forwarded from MgNB to Source gNB after step 2 and from MgNB to Target gNB in step 5) - -## 2.4.1.19 RRC connection re-establishment (inter gNB-CU) - -### 2.4.1.19.1 Test Purpose - -The purpose of this test case is to verify that the RRC connection re-establishment procedure with two gNBs, hereafter Target gNB and Source gNB respectively, from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] Section 6.10.4. - -### 2.4.1.19.2 Minimum Requirements - -DUTs: Target gNB and Source gNB (TgNB and SgNB): - -- DUTs shall apply the parameter condition specified in 6.10.4 of the NR C-Plane profile specification [2] - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform RRC connection re-establishment -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -### 2.4.1.19.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the source gNB and target gNB according to the NR C-Plane profile specification [2] - -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of SgNB cell -- Data transfer between the application test server and Test UE or UE emulator is possible - -#### 2.4.1.19.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator -2. Perform Inter gNB Handover procedure from SgNB to TgNB - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT - -- a. The Test UE or UE emulator sends a Measurement Report to the SgNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and SgNB and the TgNB simultaneously. In this specific case, the SgNB can start off with low attenuation applied which is subsequently increased. At the same time, the TgNB can start off with high attenuation applied which is subsequently lowered to a level which can trigger the measurement report to be sent to the SgNB. - -3. Perform RRC Connection Re-establishment by triggering handover failure - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT - -- a. Simulate radio link failure by increasing the attenuation of the TgNB. - -4. Stop data transfer between the Application Test Server and Test UE or UE emulator -5. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds -6. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.19.5 Expected Results and Log Observation - -##### 2.4.1.19.5.1 Expected Results - -The RRC connection re-establishment procedure is successfully completed. - -##### 2.4.1.19.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 6.10.4.1 and 6.10.4.2. - -If any of the following listed IEs is observed in the Xn logs: - -- “Criticality Diagnostics” in “RETRIEVE UE CONTEXT RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the uplink and downlink U-Plane data generated in step 1 and after step 3 and in step 5: - - o All U-Plane data recorded in the NG and Xn logs is correctly received by the Test UE or UE emulator and the Application Test Server, respectively. - -## 2.4.1.20 RRC Inactive to RRC Connected, Inter gNB-CU - -### 2.4.1.20.1 Test Purpose - -The purpose of this test case is to verify that the state change procedure from RRC inactive to RRC connected between two gNBs from different vendors can successfully be completed by performing the Retrieve UE Context procedure, conforming to the NR C-Plane profile specification [2] Section 6.9.3. - -### 2.4.1.20.2 Minimum Requirements - -DUTs: Receiving gNB and Last Serving gNB: - -- DUTs shall apply the parameter condition specified in 6.9.3 of the NR C-Plane profile specification [2] -- The coverages of Receiving gNB and Last Serving gNB cells overlap each other. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to trigger the RRC state transition procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the core network, ie, 5GC side -- Protocol Analyzer: used to record and observe Xn procedural flows and content, and NG-U UP content - -### 2.4.1.20.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the Receiving gNB and Last Serving gNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and the Service Request procedure specified in NR C-Plane profile specification [2] Section 6.1.1 has been successfully completed. At least one DRB is established and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible. -- Data transfer in the uplink and downlink direction towards/from the Test UE or UE emulator is omitted for a period of time. The UE or UE emulator is in RRC inactive state. - -The UE or UE emulator is moved from the cell of the Last Serving gNB to the cell of the Receiving gNB. That can be done eg, by increasing the attenuation of the Last Serving gNB cell and by lowering the attenuation of the Receiving gNB cell. - -### 2.4.1.20.4 Procedure - -1. Initiate RRC inactive to RRC connected procedure - -Two examples of how this procedure can be performed (or triggered) are listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification. - -- a. Perform data transfer in the uplink direction from the Test UE or UE emulator towards the Application Test Server - -The RRC inactive to RRC connected procedure is initiated by the UE sending a RRCResumeRequest to the Receiving gNB. - -- b. Perform data transfer in the downlink direction from the Application Test Server towards the Test UE or UE emulator - -Paging procedure is initiated by the Receiving gNB and the UE triggers RRC inactive to RRC connected by sending a RRCResumeRequest to the Receiving gNB. - -2. Stop data transfer between the Application Test Server and the Test UE or UE emulator -3. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds before the RRC connection times out. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the RRC connection was established - -4. Observe the Protocol Analyzer Xn logs - -#### 2.4.1.20.5 Expected Results and Log Observation - -##### 2.4.1.20.5.1 Expected Results - -The RRC Inactive to RRC Connected state change procedure between two gNBs is completed successfully, performed with Retrieve UE Context procedure., Data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible. - -##### 2.4.1.20.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 6.9.3.1/6.9.3.2. - -If any of the following listed IEs is observed in the Xn log - -- “Criticality Diagnostics” in “RETRIEVE UE CONTEXT RESPONSE” - -the test result shall be determined to be ‘successful with remarks’. - -NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and step 3: - - All U-Plane data which is recorded in the NG logs is correctly received by the Test UE or emulated UE -- Regarding the uplink U-Plane data generated in step 1 and step 3: - - All U-Plane data transmitted by the Test UE or emulated UE is recorded in the NG logs - -#### 2.4.1.21 Measurement Gap Coordination Procedure (MN initiated) - -##### 2.4.1.21.1 Test Purpose - -The purpose of this test case is to verify that the MgNB initiated measurement gap coordination procedure between two gNBs from different vendors can successfully be completed by performing the S-Node Modification procedure, conforming to the NR C-Plane profile specification [2] Section 7.2.1.8. - -##### 2.4.1.21.2 Minimum Requirements - -DUTs: Master gNB (MgNB) and Secondary gNB (SgNB): - -- DUTs shall apply the parameter condition specified in 7.2.1 of the NR C-Plane profile specification [2] -- The coverage of Master gNB and Secondary gNB cells overlap. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to trigger the measurement report procedure - -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the core network, ie, 5GC side -- Protocol Analyzer: used to record and observe Xn procedural flows and content, and NG-U UP content - -#### 2.4.1.21.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- The Test UE or UE emulator is within the coverage area of the MgNB and of the SgNB cells -- The test UE or UE emulator has registered to the network, ie, Registration procedure and the Service Request procedure specified in NR C-Plane profile specification [2] Section 6.1.1 has been successfully completed. -- The S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the application test server and test UE or UE emulator is possible - -#### 2.4.1.21.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the Measurement Gap Coordination procedure. This involves observing that the user plane data forwarded from the SgNB to the MgNB over the Xn interface during the Measurement Gap Coordination procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates high enough for the SgNB to start buffering user plane downlink data prior to the release of the SgNB. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). -2. Perform the measurement gap coordination procedure - - -An example of how this procedure can be performed (or triggered) are listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - - - a. The MgNB receives a measurement report from the test UE or UE emulator -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the RRC reconfiguration was completed -5. Observe the Protocol Analyzer Xn, NG logs and the Test UE or UE emulator logs - -#### 2.4.1.21.5 Expected Results and Log Observation - -##### 2.4.1.21.5.1 Expected Results - -The measurement gap coordination procedure between two gNBs is completed successfully, performed with the S-Node Modification procedure. Data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible. - -##### 2.4.1.21.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.2.1.8.1/7.2.1.8.2. - -If any of the following listed IEs is observed in the Xn log - -- “Criticality Diagnostics” in “S-NODE MODIFICATION REQUEST ACKNOWLEDGE” - -the test result shall be determined to be ‘successful with remarks’. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink and uplink U-Plane data generated in step 1, during step 2 and in step 4: - - All U-Plane data which is recorded in the NG logs is correctly received by the Test UE or emulated UE and the application server, respectively - - All U-Plane data recorded in the Xn logs (ie, all U-Plane transferred between SgNB to MgNB is correctly received by the Test UE or UE emulator and the application server, respectively. - -#### 2.4.1.22 SN initiated Activity Notification - -##### 2.4.1.22.1 Test Purpose - -The purpose of this test case is to verify that the SgNB initiated S-Node Activity Notification procedure between two gNBs from different vendors can successfully be completed, conforming to the NR C-Plane profile specification [2] Section 7.9.1. - -##### 2.4.1.22.2 Minimum Requirements - -DUTs: Master gNB (MgNB) and Secondary gNB (SgNB): - -- DUTs shall apply the parameter condition specified in 7.9.1 of the NR C-Plane profile specification [2] -- The coverage of Master gNB and Secondary gNB cells overlap. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator: used to start and stop user data transfer and initiate the Activity Notification procedure -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the core network, ie, 5GC side -- Protocol Analyzer: used to record and observe Xn procedural flows and content, and NG-U UP content - -##### 2.4.1.22.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- The Test UE or UE emulator is within the coverage area of the MgNB and of the SgNB cells -- The test UE or UE emulator has registered to the network, ie, Registration procedure and the Service Request procedure specified in NR C-Plane profile specification [2] Section 6.1.1 has been successfully completed. -- The S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transfer between the application test server and test UE or UE emulator is possible - -#### 2.4.1.22.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform the activity notification procedure – inactivity indication - -An example of how this procedure can be performed (or triggered) are listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. The UE or UE emulator stops user traffic to/from the Application Test Server until the activity supervision timer in the SgNB expires - -Possible procedures as a result of this step are: - -- i. MgNB releases the SgNB node by means of the S-Node Release procedure -- ii. MgNB does not take any action -- iii. MgNB suspends SCG resources by means of the S-Node Modification procedure - -3. Perform the activity notification procedure – re-activated indication - -Step 3 is applicable only when in step 2 the procedure results are ii or iii. - -An example of how this procedure can be performed (or triggered) are listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. The UE or UE emulator resumes user traffic to/from the Application Test Server for at least 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly after the Activity Notification with re-activation is completed - -4. Observe the Protocol Analyzer Xn, NG logs and the Test UE or UE emulator logs - -#### 2.4.1.22.5 Expected Results and Log Observation - -##### 2.4.1.22.5.1 Expected Results - -The Activity Notification procedure between two gNBs is completed successfully and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is possible. - -Procedure step 2 and optionally step 3 (see section 2.4.1.22.4) may result in one of the below listed outcomes. Any of the outcomes is considered to be a successful TC completion. However, step 3 may not be applicable, as specified in section 2.4.1.22.4, in which case the TC is considered to be successful if step 2 only is executed. - -- step 2: - - a. MgNB releases the SgNB node by means of the S-Node Release procedure - - b. MgNB does not take any action - - c. MgNB suspends SCG resources by means of the S-Node Modification procedure -- step 3: - - a. MgNB does not take any action when step 2 resulted in outcome b. - - b. MgNB resumes SCG resources by means of the S-Node Modification procedure, when step 2 resulted in outcome c. - -#### 2.4.1.22.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.9.1. - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink and uplink U-Plane data generated in step 1, and in step 3: - - All U-Plane data which is recorded in the NG logs is correctly received by the Test UE or emulated UE and the application server, respectively - - All U-Plane data recorded in the Xn logs (ie, all U-Plane transferred between SgNB and MgNB) is correctly received by the Test UE or UE emulator and the application server, respectively. - -#### 2.4.1.23 Inter-Master Node Handover (with SN Change) - -##### 2.4.1.23.1 Test Purpose - -The purpose of this test case is to verify that an Inter-Master Node Handover (with SN Change) procedure with four gNBs from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] section 7.7.2. - -##### 2.4.1.23.2 Minimum Requirements - -DUTs: Four gNBs (Source Master gNB (S-MN), Target Master gNB (T-MN), Source Secondary gNB (S-SN), Target Secondary gNB (T-SN)): - -- DUTs shall apply the parameter condition specified in 7.7.2 of the NR C-Plane profile specification [2] -- The coverage of Source Master gNB cell (S-MN) overlaps with Target Master gNB cell (T-MN) and Source Secondary gNB cell (S-SN) -- The coverage of Target Master gNB cell (T-MN) overlaps with Target Secondary gNB cell (T-SN) -- The coverage of Source Secondary gNB cell (S-SN) do not overlap with Target Secondary gNB cell (T-SN) - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform Inter-Master Node Handover (with SN Change) procedure -- Core or Core emulator (5GC): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -### 2.4.1.23.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the S-MN, T-MN, S-SN and T-SN according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and/or Service Request procedure specified in NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the Source Master gNB cell (S-MN) and Source Secondary gNB cell (S-SN) -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the Source Master gNB (S-MN) and Source Secondary gNB (S-SN) has been successfully completed according to NR C-Plane profile specification - -### 2.4.1.23.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -Note: it is a requirement for this test case to validate that the user plane downlink data forwarding function operates correctly during the Inter-Master Node Handover procedure. - -This involves observing that the user plane data forwarded from the source gNB to the target gNB, over the Xn interface during the Inter-Master Node Handover procedure can be received successfully by the Test UE or UE emulator without seeing any packet losses. - -One method to stimulate the user plane downlink data forwarding function is to transfer user plane data at data rates which are high enough for the source gNB to start buffering user plane downlink data prior to the Inter-Master Node Handover. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane downlink data forwarding function (for example, it could correspond to the maximum Layer 1 Radio data rate in NR RAT, which is calculated based on 3GPP TS 38.211 [10] and 3GPP TS 38.214 [11] using the RAN parameters used in this test). - -2. Perform Inter-Master Node Handover (with SN Change) procedure from Source Master gNB (S-MN) to Target Master gNB (T-MN). - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. The Test UE or UE emulator sends a Measurement Report to the Source Master gNB (S-MN). One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and Source Master gNB (S-MN) and the Target Master gNB (T-MN) simultaneously. In this specific case, the Source Master gNB (S-MN) cell can start off with low attenuation applied which is subsequently increased. At the same time, the Target Master gNB (T-MN) cell can start off with high attenuation applied which is subsequently lowered to a level which can trigger the measurement report to be sent to the Source Master gNB (S-MN). - -The Target Master gNB (T-MN) decides to change the Secondary Node if the S-SN cell do not overlap with T-SN cell. Therefore, the T-MN sends the S-Node Addition Request to Target Secondary gNB (T-SN). - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator. -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Inter-Master Node Handover (with SN Change) procedure. This involves observing that the user plane data transferred in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs. - -#### 2.4.1.23.5 Expected Results and Log Observation - -##### 2.4.1.23.5.1 Expected Results - -The Inter-Master Node Handover (with SN Change) procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.4.1.23.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.7.2.1/7.7.2.2. - -The test result shall be determined to be Partial Success if any of the following listed IEs is observed in the Xn logs: - -- “PDU Session Resources Not Admitted List” in “S-NODE ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “S-NODE ADDITION REQUEST ACKNOWLEDGE” -- “PDU Session Resources Not Admitted List” in “HANDOVER REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “HANDOVER REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “S-NODE RELEASE REQUEST ACKNOWLEDGE” -- “Configuration rejected” in “S-NODE RECONFIGURATION COMPLETE” - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator - - o All U-Plane data recorded in the Xn logs (ie, all U-Plane data forwarded from S-MN to T-MN) is correctly received by the Test UE or UE emulator -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or emulated UE is recorded in the NG logs - - o All U-Plane data transmitted by the Test UE or UE emulator is recorded in the Xn logs (ie, all U-Plane data forwarded from T-MN to S-MN) is recorded in the Xn logs - -#### 2.4.1.24 Intra Master Node, intra gNB-DU intra Cell handover with Secondary Node change - -##### 2.4.1.24.1 Test Purpose - -The purpose of this test case is to verify that an Intra-Master Node Intra cell Handover procedure with SN change between gNBs from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] section 7.10.1. - -#### 2.4.1.24.2 Minimum Requirements - -DUTs: Two gNBs (Master gNB (MN), Secondary gNB (SN)): - -Note: to execute this test case there may be two SN DUTs used, a source SN and a target SN. When one SN DUT only is used, that single SN is serving both as source and target SN. - -- DUTs shall apply the parameter condition specified in 7.10.1 of the NR C-Plane profile specification [2] -- The coverage of the primary cell of the MN and the cell of the SN overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform Intra-Master Node Handover (with SN Change) procedure -- Core or Core emulator (5GC): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -#### 2.4.1.24.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MN and SN according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and/or Service Request procedure specified in NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the Master gNB cell (MN) and Secondary gNB cell (SN) -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the Master gNB (MN) and Secondary gNB (SN) has been successfully completed according to NR C-Plane profile specification - -#### 2.4.1.24.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros) - -2. Perform the MN intra-DU handover with SN Change procedure - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT - -- a. Establish and release many DRBs consecutively to use-up DRB-IDs until the max number of DRB-IDs per security key is reached (the exact max number is implementation dependent). When the max number is reached a new security key is assigned by performing and intra-cell HO - -The Master gNB (MN) decides to change the SN Secondary Node even if the primary MN cell overlaps with the cell of the SN - -Note: When one SN DUT only is used, that single SN is serving both as source and target SN - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Intra-Master Node Handover (with SN Change) procedure. This involves observing that the user plane data transferred in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] using the RAN parameters used in this test) - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs - -#### 2.4.1.24.5 Expected Results and Log Observation - -##### 2.4.1.24.5.1 Expected Results - -The Intra-Master Node Intra-DU Handover with SN Change procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.4.1.24.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.10.12.1/7.10.12.2. - -The test result shall be determined to be Partial Success if any of the following listed IEs is observed in the Xn logs: - -- “PDU Session Resources Not Admitted List” in “S-NODE ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “S-NODE ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “S-NODE RELEASE REQUEST ACKNOWLEDGE” -- “Configuration rejected” in “S-NODE RECONFIGURATION COMPLETE” - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator - - o All U-Plane data recorded in the Xn logs (ie, all U-Plane data forwarded from S-MN to T-MN) is correctly received by the Test UE or UE emulator -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data transmitted by the Test UE or emulated UE is recorded in the NG logs - - o All U-Plane data transmitted by the Test UE or UE emulator is recorded in the Xn logs (ie, all U-Plane data forwarded from T-MN to S-MN) is recorded in the Xn logs - -## 2.4.1.25 Intra Master Node, intra gNB-DU inter Cell handover with Secondary Node change - -### 2.4.1.25.1 Test Purpose - -The purpose of this test case is to verify that an Intra-Master Node Intra-DU Handover procedure with SN change between gNBs from different vendors can be successfully completed; conforming to the NR C-Plane profile specification [2] section 7.10.2. - -### 2.4.1.25.2 Minimum Requirements - -DUTs: Two gNBs (Master gNB (MN), Secondary gNB (SN)): - -Note: to execute this test case there may be two SN DUTs used, a source SN and a target SN. When one SN DUT only is used, that single SN is serving both as source and target SN. - -- DUTs shall apply the parameter condition specified in 7.10.1 of the NR C-Plane profile specification [2] -- The coverage of the primary cell of the MN and the cell of the SN overlap -- The coverage of the serving cell of the MN and the cell of the SN overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform Intra-Master Node Handover (with SN Change) procedure -- Core or Core emulator (5GC): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content - -### 2.4.1.25.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MN and SN according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and/or Service Request procedure specified in NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the Master gNB cell (MN) and Secondary gNB cell (SN) -- Data transfer between the application test server and Test UE or UE emulator is possible -- S-NG-RAN NODE ADDITION procedure between the Master gNB (MN) and Secondary gNB (SN) has been successfully completed according to NR C-Plane profile specification - -### 2.4.1.25.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform the MN intra-DU handover with SN Change procedure. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Make use of programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the primary cell and the serving cell of the MN simultaneously. In this specific case, the attenuation of the MN primary cell can start with a low value which is subsequently increased. At the same time, the serving cell of the MN can start with high attenuation level which is subsequently lowered to a level which can trigger the handover from the primary cell to the serving cell within the MN. - -The Master gNB (MN) decides to change the Secondary Node even if the secondary MN cell overlaps with the cell of the SN. - -Note: When one SN DUT only is used, that single SN is serving both as source and target SN - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator. -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Intra-Master Node Handover (with SN Change) procedure. This involves observing that the user plane data transferred in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs. - -#### 2.4.1.25.5 Expected Results and Log Observation - -##### 2.4.1.25.5.1 Expected Results - -The Intra-Master Node Intra-DU Handover with SN Change procedure is successfully completed and data transfer from the Application Test Server to the Test UE or UE emulator and vice versa is ongoing/possible. - -##### 2.4.1.25.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.10.2.1/7.10.2.2. - -The test result shall be determined to be Partial Success if any of the following listed IEs is observed in the Xn logs: - -- ‘PDU Session Resources Not Admitted List’ in ‘S-NODE ADDITION REQUEST ACKNOWLEDGE’ -- ‘Criticality Diagnostics’ in ‘S-NODE ADDITION REQUEST ACKNOWLEDGE’ -- ‘Criticality Diagnostics’ in ‘S-NODE RELEASE REQUEST ACKNOWLEDGE’ -- ‘Configuration rejected’ in ‘S-NODE RECONFIGURATION COMPLETE’ - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - o All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator - - o All U-Plane data recorded in the Xn logs is correctly received by the Test UE or UE emulator - -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or emulated UE is recorded in the NG logs - - All U-Plane data transmitted by the Test UE or UE emulator is recorded in the Xn logs is recorded in the Xn logs - -## 2.4.1.26 Intra Master Node, inter gNB-DU handover with Secondary Node change - -### 2.4.1.26.1 Test Purpose - -The purpose of this test case is to verify that an Intra-Master Node Inter-DU Handover procedure with SN change between gNBs from different vendors can be successfully completed, conforming to the NR C-Plane profile specification [2] section 7.10.3. - -### 2.4.1.26.2 Minimum Requirements - -DUTs: Two gNBs (Master gNB (MN), Secondary gNB (SN)): - -Note 1: To execute this test case there may be two SN DUTs used, a source SN and a target SN. When one SN DUT only is used, that single SN is serving both as source and target SN. - -Note 2: For the execution of this test case the MN should be composed of a gNB-DU hosting the primary cell and another gNB-DU hosting the serving cell. F1 interfaces and respective profiles are not part of this test case. - -- DUTs shall apply the parameter condition specified in 7.10.1 of the NR C-Plane profile specification [2] -- The coverage of the primary cell of the MN and the cell of the SN overlap -- The coverage of the serving cell of the MN and the cell of the SN overlap - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to perform Intra-Master Node Handover (with SN Change) procedure -- Core or Core emulator (5GC): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe both Xn link procedural flows and content, and NG-U UP content. - -### 2.4.1.26.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MN and SN according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and/or Service Request procedure specified in NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the Master gNB cell (MN) and Secondary gNB cell (SN) -- Data transfer between the application test server and Test UE or UE emulator is possible - -- S-NG-RAN NODE ADDITION procedure between the Master gNB (MN) and Secondary gNB (SN) has been successfully completed according to NR C-Plane profile specification - -#### 2.4.1.26.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. - -It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - -2. Perform the MN inter-DU handover with SN Change procedure. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Make use of programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the primary cell and the serving cell of the MN simultaneously. In this specific case, the attenuation of the MN primary cell can start with a low value which is subsequently increased. At the same time, the serving cell of the MN can start with high attenuation level which is subsequently lowered to a level which can trigger the handover from the primary cell to the serving cell within the MN. - -The Master gNB (MN) decides to change the Secondary Node even if the secondary MN cell overlaps with the cell of the SN. - -Note: When one SN DUT only is used, that single SN is serving both as source and target SN - -3. Stop data transfer between the Application Test Server and the Test UE or UE emulator. -4. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator for 10 seconds. - -Note: it is a requirement for this test case to validate that the user plane transmission operates correctly as a result of successful Intra-Master Node Handover (with SN Change) procedure. This involves observing that the user plane data transferred in both directions is successfully received by the Test UE or UE emulator (DL data), or by the Application Test Server (UL data) without seeing any packet losses. - -The exact data rate which is required to be generated is not specified but it is recommended that the data rate is high enough to verify the user plane data transmission (for example, it could correspond to the maximum Layer 1 Radio data rate in the NR RAT, which is calculated based on 3GPP TS 38.211 [10] using the RAN parameters used in this test). - -5. Observe the Protocol Analyzer NG and Xn logs and Test UE or UE emulator logs. - -#### 2.4.1.26.5 Expected Results and Log Observation - -##### 2.4.1.26.5.1 Expected Results - -The handover procedure as specified in NR C-Plane profile specification [2] section 7.10.3 is completed successfully. - -Xn logs recorded in the Protocol Analyzer are aligned with the message flows specified in the NR C-Plane profile specification [2] Sections 7.10.3.1/7.10.3.2. - -##### 2.4.1.26.5.2 Log Observation - -The test result shall be determined to be Partial Success if any of the following listed IEs is observed in the Xn logs: - -- “PDU Session Resources Not Admitted List” in “S-NODE ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “S-NODE ADDITION REQUEST ACKNOWLEDGE” -- “Criticality Diagnostics” in “S-NODE RELEASE REQUEST ACKNOWLEDGE” - -- “Configuration rejected” in “S-NODE RECONFIGURATION COMPLETE” - -Xn and NG logs recorded in the Protocol Analyzer and Test UE or UE emulator logs show that: - -- Regarding the downlink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data recorded in the NG logs is correctly received by the Test UE or UE emulator - - All U-Plane data recorded in the Xn logs is correctly received by the Test UE or UE emulator -- Regarding the uplink U-Plane data generated in step 1 and after step 2 and in step 4: - - All U-Plane data transmitted by the Test UE or emulated UE is recorded in the NG logs - - All U-Plane data transmitted by the Test UE or UE emulator is recorded in the Xn logs is recorded in the Xn logs - -## 2.4.2 Xn U-Plane IOT Test Cases - -### 2.4.2.1 Node behaviour of the corresponding node with RLC-AM and/or RLC-UM - -#### 2.4.2.1.1 Test Purpose - -The purpose of this test case is to verify that the behaviour of the corresponding node procedure with gNB1 and gNB2 from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.1.1. - -Note: The test cases for the behaviour of the corresponding node sending DDDS when events lost packet detection and stop scheduling for the data bearer occur are included in the chapter 2.4.2.3. - -#### 2.4.2.1.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply RLC nodes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap each other - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn procedural flows and contents - -#### 2.4.2.1.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] - -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] -- Data transmission has not been performed via the MgNB, eg, keeping SN terminated split bearer with NR radio quality low enough - -Note: This test case is used to verify that the MgNB does not discard any of its buffered packets in events such as Radio Link Outage over the MgNB unless it receives discard indication from the higher layers or from the SgNB hosting NR PDCP, such as the buffer discard indication from the SgNB. This initial condition ensures that the SgNB does not send the buffer discard indication to the MgNB. - -#### 2.4.2.1.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for MgNB to buffer the downlink data. The exact data rate that is generated is not specified, but it is up to MgNB node vendor implementation. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). -2. Trigger radio link outage on the MgNB. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To move the Test UE or UE emulator away from the coverage of the MgNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the MgNB cell. In this specific case, the MgNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. - -3. Trigger radio link resume on the MgNB. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To move the Test UE or UE emulator back within the coverage of the MgNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the MgNB cell. In this specific case, the MgNB cell can start off with high attenuation applied which is subsequently decreased to a level which can trigger radio link resume condition. - -4. Stop data transfer. -5. Observe the Protocol Analyzer Xn logs and Test UE or UE emulator logs. - -#### 2.4.2.1.5 Expected Results and Log Observation - -##### 2.4.2.1.5.1 Expected Results - -The behaviour of the corresponding node is aligned with the requirement specified in Section 4.1.1.1 of NR U-Plane profile specification [3]. - -##### 2.4.2.1.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.1.1 and the following should be observed: - -- MgNB sends DDDS message which includes the *Cause Value* IE with value '1', '3' or '4' to SgNB after step 2 - -- MgNB sends DDDS message which includes the *Cause Value* IE with value '2', '5' or '6' to SgNB after step 3 - -Note: these are to confirm if the Radio Link Outage operation has been performed. - -- Logs recorded in the Test UE or UE emulator are aligned with the NR U-Plane profile specification [3] Section 4.1.1.1 and the following should be observed: -- After the end of step 2 and before the start of step 3, Test UE or UE emulator does NOT receive any data which is transmitted from MgNB in step 1 -- After step 3, Test UE or UE emulator receives all the data which is transmitted from MgNB before triggering Radio Link Outage in step 1 - -## 2.4.2.2 General for Elements for the NR user plane protocols with RLC-AM and/or RLC-UM - -### 2.4.2.2.1 Test Purpose - -The purpose of this test case is to verify that the general behaviour with MgNB and SgNB from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.1. - -### 2.4.2.2.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap each other - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn procedural flows and contents -- Network Impairment Emulator: used to discard selected packets transmitted via the Xn link - -### 2.4.2.2.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Network Impairment Emulator is physically connected in-line to the Xn link between the MgNB and SgNB -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell - -- Data transmission has not been performed via the MgNB - -Note: the intention of this is to make a condition where any of the optional fields in DDDS has no available value. - -#### 2.4.2.2.4 Procedure - -1. Trigger S-NG-RAN NODE ADDITION procedure - -Note: the intention of this step is to have the MgNB send DDDS which does not include any of the optional fields as the corresponding value is not yet available. - -2. Perform data transfer in both direction between the Application Test Server and the Test UE or UE emulator until the end of step 6. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, meaningful to verify that the user plane transmission operates correctly. - -Note: the intention of this step is to make a situation where the values of Highest Transmitted NR PDCP Sequence Number IE and Highest Successfully Delivered NR PDCP Sequence Number IE in DDDS are valid. - -3. After the Application Test Server starts to transmit downlink data, drop some packets sent from the SgNB to MgNB via Xn link by using the Network Impairment Emulator inserted in-line in the Xn link - -Note: the intention of this step is to make a situation where the value of *Lost Packet Report* IE is valid. - -4. Trigger the SgNB to send Downlink User Data PDU(s) including *Retransmission flag* IE with '1' to MgNB - -Note: the intention of this step is to make a situation where the value of *Highest Retransmitted NR PDCP Sequence Number* IE and *Highest Successfully Delivered Retransmitted NR PDCP Sequence Number* IE is valid. - -The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -5. Trigger radio link outage condition in the MgNB at least once - -Note: the intention of this step is to make a situation where the value of *Cause Value* IE is valid. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. To gradually move the Test UE or UE emulator away from the coverage of the MgNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the MgNB cell. In this specific case, the MgNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. - -6. Stop scheduling in the MgNB - -Note: the intention of this step is to create a situation where the value of *Final Frame Indication* IE is valid. - -The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -7. Observe the Protocol Analyzer Xn logs and Test UE or UE emulator logs - -#### 2.4.2.2.5 Expected Results and Log Observation - -##### 2.4.2.2.5.1 Expected Results - -The behaviour of MgNB and SgNB is aligned with the requirement specified in Section 4.1.2.1 of NR U-Plane profile specification [3]. - -#### 2.4.2.2.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.1 and the following should be observed: - -- The DDDSs captured during step 1 have the following IEs with the value ‘0’: - - o Highest Transmitted NR PDCP SN Ind IE - - o Highest Delivered NR PDCP SN Ind IE - - o Final Frame Indication IE - - o Lost Packet Report IE - - o Highest Retransmitted NR PDCP SN Ind IE - - o Highest Delivered Retransmitted NR PDCP SN Ind IE - - o Cause Report IE -- One or more DDDSs captured after the beginning of the step 2 have one or both of the following IEs with the value ‘1’: - - o Highest Transmitted NR PDCP SN Ind IE - - o Highest Delivered NR PDCP SN Ind IE -- One or more DDDSs captured after the beginning of the step 3 have *Lost Packet Report* IE with the value ‘1’ -- One or more DDDSs captured after the beginning of the step 4 have one or both of the following IEs with the value ‘1’: - - o Highest Retransmitted NR PDCP SN Ind IE - - o Highest Delivered Retransmitted NR PDCP SN Ind IE -- One or more DDDSs captured after the beginning of the step 5 have *Cause Report* IE with the value ‘1’ and *Cause value* IE with the value ‘1’, ‘3’, or ‘4’ -- One or more DDDSs captured after the beginning of the step 6 have *Final Frame Indication* IE with the value ‘1’ - -#### 2.4.2.3 Report Polling with RLC-AM and/or RLC-UM - -##### 2.4.2.3.1 Test Purpose - -The purpose of this test case is to verify that the Report Polling procedure with MgNB and SgNB from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.2. - -##### 2.4.2.3.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap each other - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn procedural flows and contents -- Network Impairment Emulator: used to discard selected packets transmitted via the Xn link - -#### 2.4.2.3.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Network Impairment Emulator is physically connected in-line to the Xn link between the MgNB and SgNB -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.4.2.3.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator until the end of step 5. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, to meaningfully verify that the user plane transmission operates correctly. -2. Send Downlink User Data PDU(s) including *Report polling* IE with '1' from SgNB to MgNB at least once. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. SgNB transmits some data packets to MgNB (ie, step 1) -3. Drop some packets sent from SgNB to MgNB via Xn link by using the Network Impairment Emulator inserted in-line in the Xn link. - -Note: the intention of this step is to make a situation where “Lost packet detection” occurs in MgNB. - -4. Trigger radio link outage condition in the MgNB. - -Note: the intention of this step is to make a situation where “Radio link outage” occurs in MgNB. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. To gradually move the Test UE or UE emulator away from the coverage of the MgNB. One method is to use programmable attenuators to simulate varying channel conditions between the Test UE or UE emulator and the MgNB cell. In this specific case, the MgNB cell can start off with low attenuation applied which is subsequently increased to a level which can trigger radio link outage condition. -5. Trigger radio link resume condition on MgNB. - -6. Stop scheduling in the MgNB. - -Note: the intention of this step is to make a situation where “Stop scheduling for the data bearer” occurs in MgNB. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Stop downlink data transmission -7. Observe the Protocol Analyzer Xn logs and Test UE or UE emulator logs. - -#### 2.4.2.3.5 Expected Results and Log Observation - -##### 2.4.2.3.5.1 Expected Results - -The use of Report Polling function is aligned with the requirement specified in Section 4.1.2.2 of NR U-Plane profile specification [3]. - -##### 2.4.2.3.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.2 and the following should be observed: - -- After the beginning of step 2: - - SgNB sends MgNB one or more Downlink User Data PDU(s) including *Report polling* IE with the value ‘1’ - - MgNB sends SgNB DDDS as soon as possible after receiving the corresponding Downlink User Data PDU(s) -- After the beginning of step 3, MgNB sends SgNB DDDS where following IEs show the dropped packets: - - Start of lost NR-U Sequence Number range IE(s) - - End of lost NR-U Sequence Number range IE(s) -- After the beginning of step 4, MgNB sends SgNB DDDS including *Cause Value* IE with the value ‘1’, ‘3’ or ‘4’ -- After the beginning of step 6, MgNB sends SgNB DDDS including *Final Frame Indication* IE with the value ‘1’, and then MgNB does not send SgNB DDDS including any updated instance of the following IEs - - Highest successfully delivered NR PDCP Sequence Number IE - - Highest transmitted NR PDCP Sequence Number IE - - Highest successfully delivered retransmitted NR PDCP Sequence Number IE - - Highest retransmitted NR PDCP Sequence Number IE - -#### 2.4.2.4 Buffer discard indication with RLC-AM and/or RLC-UM - -##### 2.4.2.4.1 Test Purpose - -The purpose of this test case is to verify that the use of the *DL Discard Blocks* IE and the *DL Flush IE* with gNB1 and gNB2 from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.3. - -##### 2.4.2.4.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap each other - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn procedural flows and contents - -#### 2.4.2.4.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.4.2.4.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for MgNB to buffer the downlink data. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). -2. SgNB to send the DL User Data message which includes the *DL Discard Blocks* IE with value '1'. - -Note: the purpose of this step is to indicate from SgNB to MgNB to discard NR PDCP PDUs. It is up to SgNB implementation when to initiate this step. Specific test procedure needs to be considered taking into account the SgNB implementation. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Tester sets small value in "discardTimer" in order that this timer expires before the SgNB receives acknowledgement of the transmitted data from the MgNB - -3. SgNB to send the DL User Data message which includes the *DL Flush* IE with value '1'. - -Note: the purpose of this step is to indicate from SgNB to MgNB to discard NR PDCP PDUs. It is up to SgNB implementation when to initiate this step. Specific test procedure needs to be considered taking into account the SgNB implementation. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Tester sets small value in "discardTimer" in order that this timer expires before the SgNB receives acknowledgement of the transmitted data from the MgNB -4. Observe the Protocol Analyzer Xn logs and Test UE or UE emulator logs. - -#### 2.4.2.4.5 Expected Results and Log Observation - -##### 2.4.2.4.5.1 Expected Results - -The use of *DL Discard Blocks* IE and the *DL Flush* IE is aligned with the requirement specified in Section 4.1.2.3 of NR U-Plane profile specification [3]. - -##### 2.4.2.4.5.2 Log Observation - -Logs Recorded in the Protocol Analyzer and the Test UE or emulated UE show that: - -- NR PDCP PDUs, which are indicated to be discarded in the DL User Data message in step 2, are NOT received by the Test UE or emulated UE - -Note: the NR PDCP PDUs to be discarded is indicated by the following IEs in the DL User Data message: - -- o SgNB DL discard Number of blocks - - o DL discard NR PDCP PDU SN start - - o Discarded Block size present -- NR PDCP PDUs, which are indicated to be discarded in the DL User Data message in step 3, are NOT received by the Test UE or emulated UE. - -Note: the NR PDCP PDUs to be discarded is indicated by the following IEs in the DL User Data message: - -- o DL discard NR PDCP PDU SN present - -#### 2.4.2.5 User data existence flag with RLC-AM and/or RLC-UM - -##### 2.4.2.5.1 Test Purpose - -The purpose of this test case is to verify SgNB's notification to the MgNB of the existence of user data, but without using the *User data existence flag* IE, with MgNB and SgNB from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.4. - -Note: This feature is needed when the MgNB does not support the *User data existence flag* IE eg, in the case when the MgNB is designed to be compliant with older versions of the 3GPP specifications which do not support this IE. - -##### 2.4.2.5.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap each other -- SgNB shall activate the feature which is specified in Section 4.1.2.4 of NR U-Plane profile [3] - -Note: How to activate this feature is up to SgNB implementation. One example is to activate it via M-Plane. - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn procedural flows and contents - -#### 2.4.2.5.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.4.2.5.4 Procedure - -1. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator via Xn. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, to meaningfully verify that the user plane transmission operates correctly. - -Note: the intention of this step is to avoid expiring some timers in MgNB which monitor the activity of user data transfer (eg, DRX inactivity timer, UE inactive timer, etc). - -2. Decrease the amount of user data to be transmitted in both directions the Application Test Server and the Test UE or UE emulator so that the user data can be transmitted via SgNB only. With this condition perform data transmission for 60 seconds. - -Note: the intention of this step is to create a situation where the SgNB sends actual user data to the MgNB even when the amount of user data is small enough to be sent via the SgNB only. In this test scenario, the SgNB radio condition need not be ideal but shall be good enough to ensure that all user data can be transmitted through the MgNB only. - -3. Stop data transfer. -4. Observe the Protocol Analyzer Xn logs and Test UE or UE emulator logs. - -#### 2.4.2.5.5 Expected Results and Log Observation - -##### 2.4.2.5.5.1 Expected Results - -The behaviour of SgNB is aligned with the requirement specified in Section 4.1.2.4 of NR U-Plane profile [3]. - -##### 2.4.2.5.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.4 and the following should be observed: - -- NR PDCP PDU is sent from SgNB to MgNB, which is frequently enough NOT to expire the timers described in the note in step 1 - -Note: The required frequency is up to MgNB implementation, ie, the value of the timers used in the MgNB. - -As a result of above, logs recorded in the Test UE or UE emulator shows: - -- Test UE or UE emulator keeps RRC Connected state without expiring DRX inactivity timer in MgNB as specified in 3GPP TS 38.331 [17] and 3GPP TS 38.321 [18], from the beginning of step 2 till before step 3 - -## 2.4.2.6 Assistance Information Report polling with RLC-AM and/or RLC-UM - -### 2.4.2.6.1 Test Purpose - -The purpose of this test case is to verify the use of the Assistance Information Report polling flag with MgNB and SgNB from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.5. - -### 2.4.2.6.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap each other - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn procedural flows and contents - -### 2.4.2.6.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -### 2.4.2.6.4 Procedure - -1. Send Downlink User Data PDU(s) from SgNB to MgNB with *Assistance Information Report polling Flag* IE whose value is set to '1'. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT: - -- a. Send the Downlink User Data PDU(s) immediately after completing the S-NG-RAN NODE ADDITION procedure -2. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for MgNB to buffer the downlink data. The exact data rate that is generated is not specified, but it is up to MgNB node vendor implementation. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). -3. Observe the Protocol Analyzer Xn logs and Test UE or UE emulator logs. - -#### 2.4.2.6.5 Expected Results and Log Observation - -##### 2.4.2.6.5.1 Expected Results - -The use of the Assistance Information Report polling flag is aligned to the requirement specified in Section 4.1.2.5 of NR U-Plane profile [3]. - -##### 2.4.2.6.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.5 and the following should be observed: - -- In step 1, one or more Downlink User Data PDU(s) sent by the SgNB to the MgNB include *Assistance Information Report polling Flag* IE with the value '1' -- After receiving the corresponding Downlink User Data PDU(s), AID is sent by the MgNB to the SgNB - -#### 2.4.2.7 Radio quality assistance information with RLC-AM and/or RLC-UM - -##### 2.4.2.7.1 Test Purpose - -The purpose of this test case is to verify the use of the *Radio quality assistance information* IE with MgNB and SgNB from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.6. - -##### 2.4.2.7.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply RLC modes specified in NR U-Plane profile specification [3] - -Note: In case both RLC-AM and RLC-UM is to be tested, this test case must be executed twice, with respective RLC settings. - -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap each other -- MgNB shall be configured with the Assistance Information Type(s) to be reported in the AID message via M-Plane. In this version of the specification the following Assistance Information Types can be configured to be reported: - - o '0'=UNKNOWN - - o '1'=Average CQI - - o '2'=Average HARQ Failure - - o '3'=Average HARQ Retransmissions - - o '4'= DL Radio Quality Index - - o '5'= UL Radio Quality Index - -- o '6'= Power Headroom Report - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application Test Server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn procedural flows and contents - -#### 2.4.2.7.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.4.2.7.4 Procedure - -1. Send Downlink User Data PDU(s) from SgNB to MgNB with *Assistance Information Report polling Flag* IE whose value is set to '1'. This procedure shall be performed before the assistance information to be reported by the MgNB becomes available. - -Note: the intention of this step is to create a situation where the MgNB does not report the assistance information due to unavailability of the information. - -An example of how this procedure can be performed (or triggered) is listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Send the Downlink User Data PDU(s) immediately after completing the S-NG-RAN NODE ADDITION procedure -2. Perform data transfer in both directions between the Application Test Server and the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough for MgNB to buffer the downlink data. It should be noted that this test case does not specify the test data pattern generated by the Application Test Server, but it is recommended that the test data pattern should include some level of randomness (ie, avoiding all zeros). - 3. Create conditions which can help the MgNB gather the information/measurements required for its configured Assistance Information Types. - -An example of how these conditions can be created is listed below. The exact method to create these conditions is out of scope of this specification and is left up to the implementation of the DUT. - -- a. Send DL user data via MgNB so that MgNB can obtain eg, CQI/HARQ ACK/Power headroom report from Test UE or UE emulator. -4. Send Downlink User Data PDU(s) from SgNB to MgNB with *Assistance Information Report polling Flag* IE whose value is set to '1'. - -5. Observe the Protocol Analyzer Xn logs and Test UE or UE emulator logs. - -#### 2.4.2.7.5 Expected Results and Log Observation - -##### 2.4.2.7.5.1 Expected Results - -The use of the *Radio quality assistance information* IE is aligned with the requirement specified in Section 4.1.2.6 of NR U-Plane profile [3]. - -##### 2.4.2.7.5.2 Log Observation - -Xn logs recorded in the Protocol Analyzer are aligned with the NR U-Plane profile specification [3] Section 4.1.2.6 and the following should be observed: - -- After step 1, MgNB sends the Assistance Information Data message to SgNB, where the value of *Assistance Information Indication* IE is '0' - -Note: the intention is to validate that any configured assistance information is not reported at this moment. - -- After step 3, MgNB sends the Assistance Information Data message to SgNB, where *Assistance Information Type* IE, *Number of octets for Radio Quality Assistance Information Fields* IE, and *Radio Quality Assistance Information* IE corresponding to the configured assistance information are included - -Note: the intention is to validate that all the configured assistance information is reported. - -Note: it is not expected that any assistance information which is not configured to be reported via M-Plane is included in the AID message. - -#### 2.4.2.8 DL report NR PDCP PDU SN with RLC-AM - -##### 2.4.2.8.1 Test Purpose - -The purpose of this test case is to verify that the use of the DL report NR PDCP PDU SN IE with MgNB and SgNB from different vendors can be successfully completed; conforming to the NR U-Plane profile specification [3] Section 4.1.2.7. - -##### 2.4.2.8.2 Minimum Requirements - -DUTs: Two gNBs (MgNB – MN, SgNB – SN): - -- DUTs shall apply RLC-AM specified in NR U-Plane profile specification [3] -- The coverage of MgNB cell (MN) and SgNB cell (SN) overlap each other - -Testing tools which are required for this test scenario: - -- Test UE or UE emulator which is capable of supporting NR and NR-DC: used to terminate NAS/AS protocol and data transmission/reception -- Core or Core emulator (5GC capabilities): used to terminate UEs (emulator) NAS protocol -- Application test server: used to originate and terminate application layer traffic (eg, UDP, TWAMP, etc) and provide application layer processing on the network side -- Protocol Analyzer: used to record and observe Xn procedural flows and contents - -##### 2.4.2.8.3 Initial Conditions - -Refer to Section 2.4 for the standard list of initial conditions. - -The following list of initial conditions are applicable for this specific test case: - -- Xn Setup procedure has been successfully completed between the MgNB and SgNB according to the NR C-Plane profile specification [2] -- Test UE or UE emulator has registered to the network, ie, Registration procedure and Service Request procedure specified in the NR C-Plane profile specification [2] has been successfully completed -- Test UE or UE emulator is within the coverage area of the MgNB cell and SgNB cell -- S-NG-RAN NODE ADDITION procedure between the MgNB and SgNB has been successfully completed according to NR C-Plane profile specification [2] - -#### 2.4.2.8.4 Procedure - -1. Perform data transfer from the Application Test Server to the Test UE or UE emulator. The Application Test Server generates and transmits downlink data with data size large enough to achieve a sustained data rate over time, to meaningfully verify that the user plane transmission operates correctly. -2. Send the DL User Data message which includes the DL report NR PDCP PDU SN IE from SgNB to MgNB. -3. Observe the Protocol Analyzer Xn logs. - -#### 2.4.2.8.5 Expected Results and Log Observation - -##### 2.4.2.8.5.1 Expected Results - -The use of DL report NR PDCP PDU SN IE is aligned with the requirement specified in Section 4.1.2.7 of NR U-Plane profile specification [3]. - -##### 2.4.2.8.5.2 Log Observation - -Logs Recorded in the Protocol Analyzer show that: - -- After beginning of step 2: - - MgNB sends SgNB DDDS including Highest successfully delivered NR PDCP Sequence Number IE with the value same as the value indicated by DL report NR PDCP PDU SN IE. - - MgNB sends SgNB DDDS as soon as possible only when all PDCP PDU SNs up to this DL report NR PDCP PDU have been successfully delivered in-sequence. - -## Annex (informative) - -| Date | Revision | Description | -|------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2020.04.29 | 01.00 | First published version | -| 2021.03.05 | 02.00 | Addition of F1 test cases and minor editorial corrections | -| 2021.11.03 | 03.00 | Addition of more X2, F1, and Xn test cases and minor editorial corrections | -| 2022.03.23 | 04.00 | Corrections, clarifications, and minor editorial corrections | -| 2022.07.15 | 05.00 | Addition of more X2, F1, and Xn test cases and minor editorial corrections. Removal of Annex ZZZ | -| 2022.11.04 | 06.00 | Addition of more X2, F1, and Xn test cases and minor editorial corrections | -| 2023.03.10 | 07.00 | Addition of network configurations for badging, addition of more X2, F1, and Xn test cases and minor editorial corrections | -| 2023.07.17 | 08.00 | Addition of network configurations for badging, addition of more X2, F1, and Xn test cases and minor editorial corrections | -| 2023.11.16 | 09.00 | Alignment of UP data handling description across all test cases, clarification of text and figures referring to O-DU/O-CU, and minor editorial corrections. | -| 2024.03.13 | 10.00 | Addition of more X2, F1, and Xn test cases and minor editorial corrections. | -| 2024.07.11 | 11.00 | Addition of more X2, F1, and Xn test cases and minor editorial corrections. | -| 2024.11.21 | 12.00 | Addition of more X2, F1, and Xn test cases and minor editorial corrections. | -| 2025.03.12 | 13.00 | Addition of more X2, F1, and Xn test cases and minor editorial corrections. | -| 2025.06.08 | 14.00 | Addition of more X2, F1, and Xn test cases and minor editorial corrections. | -| 2025.11.19 | 15.00 | Addition of more X2, F1, and Xn test cases and minor editorial corrections. | \ No newline at end of file diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/029a2a023e47a2cc5c60079e523926c5_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/029a2a023e47a2cc5c60079e523926c5_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/029a2a023e47a2cc5c60079e523926c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/07bae2d456e460215a6b74db040d9b6c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/07bae2d456e460215a6b74db040d9b6c_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/07bae2d456e460215a6b74db040d9b6c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 5ea9ae9194f7b34b2cc65cfadbc793ea1665fdee..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2a4b269f41327c108671a0dc91ce78a790dbc91b34a39bd88709c7e4474a7073 -size 4436 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/09032127b49c74c07fdc4e0d5275a115_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/09032127b49c74c07fdc4e0d5275a115_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/09032127b49c74c07fdc4e0d5275a115_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/09fcf056902487318885284a6b43b08c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/09fcf056902487318885284a6b43b08c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/09fcf056902487318885284a6b43b08c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0a278c1194f7b78236442a1c85cf70b5_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0a278c1194f7b78236442a1c85cf70b5_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0a278c1194f7b78236442a1c85cf70b5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0c6aeaf9973cd03cff19dd3f0ca1314e_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0c6aeaf9973cd03cff19dd3f0ca1314e_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0c6aeaf9973cd03cff19dd3f0ca1314e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0d2f92b554f88f7f5b03f23faec94dba_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0d2f92b554f88f7f5b03f23faec94dba_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0d2f92b554f88f7f5b03f23faec94dba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0e2a8954ad6cb6a913374fe51484fce5_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0e2a8954ad6cb6a913374fe51484fce5_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0e2a8954ad6cb6a913374fe51484fce5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0e50822d868aa19c8aa37bfb98002a25_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0e50822d868aa19c8aa37bfb98002a25_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0e50822d868aa19c8aa37bfb98002a25_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0e611959485447591664307862231ffd_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0e611959485447591664307862231ffd_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0e611959485447591664307862231ffd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg deleted file mode 100644 index 6f9465ca57833a6e98ea7a7b98eeebf9f98b0330..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6ee05abdb53516b6fc675f0dd9867e0a3064775853ab1aa41643090fe32bf417 -size 49054 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/10781f43062bf3e9601a1e086710556c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/10781f43062bf3e9601a1e086710556c_img.jpg deleted file mode 100644 index 938e8bc96289942a34e481b43010cda3d7ae2713..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/10781f43062bf3e9601a1e086710556c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9caef40895120521230439a0f44e9fac936cad54741f81fd573a3ea5945d9b4f -size 52121 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/116a62c978d6a7d1b7830c1ea13e2993_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/116a62c978d6a7d1b7830c1ea13e2993_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/116a62c978d6a7d1b7830c1ea13e2993_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/11b3d3cc56f71f80a268a31bd42103e9_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/11b3d3cc56f71f80a268a31bd42103e9_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/11b3d3cc56f71f80a268a31bd42103e9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/11cfbe1171c471cd8b2d0604ad5185f2_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/11cfbe1171c471cd8b2d0604ad5185f2_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/11cfbe1171c471cd8b2d0604ad5185f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/134b1f0d617209a0436333b9ab6b1ce8_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/134b1f0d617209a0436333b9ab6b1ce8_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/134b1f0d617209a0436333b9ab6b1ce8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/13fbd97d3a93abb4c723c50966c8cd14_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/13fbd97d3a93abb4c723c50966c8cd14_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/13fbd97d3a93abb4c723c50966c8cd14_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/15574508acc09ee822bfbd5ad0954c5a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/15574508acc09ee822bfbd5ad0954c5a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/15574508acc09ee822bfbd5ad0954c5a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/16b08981199f29066db206d1e31e6e47_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/16b08981199f29066db206d1e31e6e47_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/16b08981199f29066db206d1e31e6e47_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1719fcc6ce45d9a31c81c3bc46a72d03_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1719fcc6ce45d9a31c81c3bc46a72d03_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1719fcc6ce45d9a31c81c3bc46a72d03_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/19882a9fbfbe25c951b10a507c786951_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/19882a9fbfbe25c951b10a507c786951_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/19882a9fbfbe25c951b10a507c786951_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1a264eeb01c7e3f33a65cb202a5dee36_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1a264eeb01c7e3f33a65cb202a5dee36_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1a264eeb01c7e3f33a65cb202a5dee36_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1b5a812c8aa20fd5cba28e97001d32de_img.jpg deleted file mode 100644 index 6f43c5297271709ef80d13dbe78b24bbba5b25bc..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1b5a812c8aa20fd5cba28e97001d32de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b58332e563e79e042ea734dbc1d8426ec0dd95293bce7ed09d84026fcd7c5ed7 -size 44341 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1baaba7a6e54e77197475726c871067d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1baf92180f2964741688e8215d7183da_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1baf92180f2964741688e8215d7183da_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1baf92180f2964741688e8215d7183da_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1d7348fac9ef4446e3f7e5f0e15c007b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1d7348fac9ef4446e3f7e5f0e15c007b_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1d7348fac9ef4446e3f7e5f0e15c007b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1d92d4ad55f2aa411dc849438982f26b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1da00d32e4d978dc1064b4d6b74d865c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1da00d32e4d978dc1064b4d6b74d865c_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1da00d32e4d978dc1064b4d6b74d865c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg deleted file mode 100644 index bf238570411b2c3c4801758e0b4fee8375ccb9f4..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef39b9b0dadf1b084c8b8bc63a0ff7d1585b6d745ca12ad8368f11082cad5a0 -size 4493 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1ff7828d681947990fac3e7bad35dd86_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1ff7828d681947990fac3e7bad35dd86_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/1ff7828d681947990fac3e7bad35dd86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/21023d70b19c3181ccce4390ea153e38_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/21023d70b19c3181ccce4390ea153e38_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/21023d70b19c3181ccce4390ea153e38_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/21b431575d18ed23db9ef488c8dec706_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/21b431575d18ed23db9ef488c8dec706_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/21b431575d18ed23db9ef488c8dec706_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/21cfcb7e235dba52c53c8cf7b10f36aa_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/21cfcb7e235dba52c53c8cf7b10f36aa_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/21cfcb7e235dba52c53c8cf7b10f36aa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/226bcc7921bff55dc14cac630460ab92_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/226bcc7921bff55dc14cac630460ab92_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/226bcc7921bff55dc14cac630460ab92_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/233a8b9743fe86cccae4bfca4aa9a0b0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/233a8b9743fe86cccae4bfca4aa9a0b0_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/233a8b9743fe86cccae4bfca4aa9a0b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/23b110b75da6b415520918830060195e_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/23b110b75da6b415520918830060195e_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/23b110b75da6b415520918830060195e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/24a3cc3bc7bd963ec2c4ceaf3e548457_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/24a3cc3bc7bd963ec2c4ceaf3e548457_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/24a3cc3bc7bd963ec2c4ceaf3e548457_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2576e074afbb2a591f07da0fe1987ff1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/266ed4b8590c3bfce2d6ccf95b143242_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/266ed4b8590c3bfce2d6ccf95b143242_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/266ed4b8590c3bfce2d6ccf95b143242_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/26f0c643a3e0c8034b16008c351b5b65_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/26f0c643a3e0c8034b16008c351b5b65_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/26f0c643a3e0c8034b16008c351b5b65_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2981200c3b8faff326c7ace0c91f0687_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2981200c3b8faff326c7ace0c91f0687_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2981200c3b8faff326c7ace0c91f0687_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2a185522b492253375ed16f0c515c230_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2a185522b492253375ed16f0c515c230_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2a185522b492253375ed16f0c515c230_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2aa10298301ca8b4025898fa7fdbc3df_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2aa10298301ca8b4025898fa7fdbc3df_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2aa10298301ca8b4025898fa7fdbc3df_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2c4b84a66cab050595b6ee02d8799bb0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2c4b84a66cab050595b6ee02d8799bb0_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2c4b84a66cab050595b6ee02d8799bb0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2c83b9d9c8c8076be3a1de47288c226d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2cf96b55beaa98ebc755c7405b1adbeb_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2cf96b55beaa98ebc755c7405b1adbeb_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2cf96b55beaa98ebc755c7405b1adbeb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2d1bc5eed8281b9364808514bacdb32a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2d1bc5eed8281b9364808514bacdb32a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2d1bc5eed8281b9364808514bacdb32a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2de65c6883946871f46308ff85ad7faf_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2de65c6883946871f46308ff85ad7faf_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2de65c6883946871f46308ff85ad7faf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg deleted file mode 100644 index 85a5b844171ef09626460f6d5203e14c621ce1fa..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fc2daa762e732cbfd53f92e8078203d6069b1b646f155f1df58168265a7ec070 -size 4606 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2e1d7b4c07a00dd0f26b51558abbe428_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2e1d7b4c07a00dd0f26b51558abbe428_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2e1d7b4c07a00dd0f26b51558abbe428_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2eea01382188b70064fa2818361d89f1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2eea01382188b70064fa2818361d89f1_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2eea01382188b70064fa2818361d89f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2fdf2dbffaf6ea606624441e4574c011_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2fdf2dbffaf6ea606624441e4574c011_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2fdf2dbffaf6ea606624441e4574c011_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2ffb32ca2d8acda8228f0301aa7f52e0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2ffb32ca2d8acda8228f0301aa7f52e0_img.jpg deleted file mode 100644 index bf238570411b2c3c4801758e0b4fee8375ccb9f4..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/2ffb32ca2d8acda8228f0301aa7f52e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef39b9b0dadf1b084c8b8bc63a0ff7d1585b6d745ca12ad8368f11082cad5a0 -size 4493 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3107f66da1c3556cee065608ee86f7e4_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3107f66da1c3556cee065608ee86f7e4_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3107f66da1c3556cee065608ee86f7e4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/318db222fae24a59c370fa6471d541b8_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/318db222fae24a59c370fa6471d541b8_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/318db222fae24a59c370fa6471d541b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/320bb6a0e7b3cc0803a15b231b3bc311_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/320bb6a0e7b3cc0803a15b231b3bc311_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/320bb6a0e7b3cc0803a15b231b3bc311_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/35037145df6cd8b5520bbfebf46c9433_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/35037145df6cd8b5520bbfebf46c9433_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/35037145df6cd8b5520bbfebf46c9433_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3528025ccb41158288b224ec5444b962_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3528025ccb41158288b224ec5444b962_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3528025ccb41158288b224ec5444b962_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/35437f160e157760713aa85be471c3f3_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/35437f160e157760713aa85be471c3f3_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/35437f160e157760713aa85be471c3f3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/359093c76d121867106328fa8adfe8ff_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/359093c76d121867106328fa8adfe8ff_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/359093c76d121867106328fa8adfe8ff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/365fdce90bacd7a819819a2e05e70403_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/365fdce90bacd7a819819a2e05e70403_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/365fdce90bacd7a819819a2e05e70403_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/366398d17120ce12a2c36b95c54033c5_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/366398d17120ce12a2c36b95c54033c5_img.jpg deleted file mode 100644 index 4ab3429da8234fa93eff3bce092a8f0622563043..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/366398d17120ce12a2c36b95c54033c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ccc514f007b7dd779781344d60995b7fd2725a2c6a535e8ffbcc27f35e55b10d -size 4258 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg deleted file mode 100644 index 938fd786025063a9c6794111fb69bd77335965cb..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:212b63a89a9aca91bc3cfde6374ccfac83928c957707deb22ff82d98204b63cc -size 4519 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/378417d45871e98cf0371e2dfe49ef55_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/378417d45871e98cf0371e2dfe49ef55_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/378417d45871e98cf0371e2dfe49ef55_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/37d5d6957e175201847002c556b5a29d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/37d5d6957e175201847002c556b5a29d_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/37d5d6957e175201847002c556b5a29d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/37d8d885fed5ec107803a8eeceb71686_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/37d8d885fed5ec107803a8eeceb71686_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/37d8d885fed5ec107803a8eeceb71686_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 5ea9ae9194f7b34b2cc65cfadbc793ea1665fdee..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2a4b269f41327c108671a0dc91ce78a790dbc91b34a39bd88709c7e4474a7073 -size 4436 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/384d97a0c67bd4f219a452c3cd658684_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/384d97a0c67bd4f219a452c3cd658684_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/384d97a0c67bd4f219a452c3cd658684_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/39e964ecd6d6a7fd1d783271aa934f23_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/39e964ecd6d6a7fd1d783271aa934f23_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/39e964ecd6d6a7fd1d783271aa934f23_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3a3831d50dc74b7ebbec3e1d96eea588_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3a3831d50dc74b7ebbec3e1d96eea588_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3a3831d50dc74b7ebbec3e1d96eea588_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3b6f513e9cb02e7a2b653f69f9f81873_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3b6f513e9cb02e7a2b653f69f9f81873_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3b6f513e9cb02e7a2b653f69f9f81873_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3b89d812329a65ab156184a40524adf0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3b89d812329a65ab156184a40524adf0_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3b89d812329a65ab156184a40524adf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3cf773bd0581c54adb3aea51556f70b9_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3cf773bd0581c54adb3aea51556f70b9_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3cf773bd0581c54adb3aea51556f70b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/40cadfef9d925077fe9ecddbc1d44cc8_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/40cadfef9d925077fe9ecddbc1d44cc8_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/40cadfef9d925077fe9ecddbc1d44cc8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/40e106822047971ea364d73846848ecd_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/40e106822047971ea364d73846848ecd_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/40e106822047971ea364d73846848ecd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg deleted file mode 100644 index 88487158cbb200522db710ad2fcbc124b0838158..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/40f30e4d577a17052f8b1e6dc802a0d8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d25b7c8366dd1c867030e336033e9cbc81c7d1991003a4c252ec35ac08a821e -size 47183 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/426342bd710b59091374594dd7d65234_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/426342bd710b59091374594dd7d65234_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/426342bd710b59091374594dd7d65234_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/457ebeb4cc14a22ced51a688af25f7a8_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/457ebeb4cc14a22ced51a688af25f7a8_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/457ebeb4cc14a22ced51a688af25f7a8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/45a161027983c0b508f6269c35551968_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/45a161027983c0b508f6269c35551968_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/45a161027983c0b508f6269c35551968_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4665bbd9c3079135f242a62a0e931eec_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4665bbd9c3079135f242a62a0e931eec_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4665bbd9c3079135f242a62a0e931eec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/47c8f3782d7566332f5685e1b7958b33_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/47c8f3782d7566332f5685e1b7958b33_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/47c8f3782d7566332f5685e1b7958b33_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/496e5dfc146af6bcc2b3bc2eaf82826c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/496e5dfc146af6bcc2b3bc2eaf82826c_img.jpg deleted file mode 100644 index 938fd786025063a9c6794111fb69bd77335965cb..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/496e5dfc146af6bcc2b3bc2eaf82826c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:212b63a89a9aca91bc3cfde6374ccfac83928c957707deb22ff82d98204b63cc -size 4519 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4ced45096fe3cf5adc96ec6b94f07e4f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4ced45096fe3cf5adc96ec6b94f07e4f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4ced45096fe3cf5adc96ec6b94f07e4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index 938fd786025063a9c6794111fb69bd77335965cb..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:212b63a89a9aca91bc3cfde6374ccfac83928c957707deb22ff82d98204b63cc -size 4519 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4e58d71a7f0cda1ca24fac1ee80a0c7c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4e58d71a7f0cda1ca24fac1ee80a0c7c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4e58d71a7f0cda1ca24fac1ee80a0c7c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4ecfb2f8adee0634d48422a73bd1a491_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4ecfb2f8adee0634d48422a73bd1a491_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4ecfb2f8adee0634d48422a73bd1a491_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5009e30a55479d3941af523871208f9d_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5009e30a55479d3941af523871208f9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/523ab7b925beb555f88b2e1e1336974f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/523ab7b925beb555f88b2e1e1336974f_img.jpg deleted file mode 100644 index a0983fe2edf522dbd76197ba7f72ac032c8e90cb..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/523ab7b925beb555f88b2e1e1336974f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ea639e9014a21a11f33dee28690b69c431690b79d7089e6c37c60444f05b3d00 -size 39640 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5441c05741f8a35ee5d6673b0b0ebb8b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5441c05741f8a35ee5d6673b0b0ebb8b_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5441c05741f8a35ee5d6673b0b0ebb8b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/54e6016445a458d4c0aef4acc71bb0c8_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/54e6016445a458d4c0aef4acc71bb0c8_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/54e6016445a458d4c0aef4acc71bb0c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/55b5faca46291297ac05b4f648e60bcc_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/55b5faca46291297ac05b4f648e60bcc_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/55b5faca46291297ac05b4f648e60bcc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/55c1b9efdb97c2b7dd16b497c5b56d3c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/55c1b9efdb97c2b7dd16b497c5b56d3c_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/55c1b9efdb97c2b7dd16b497c5b56d3c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/568031aac86c633aab96b734dba3835e_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/568031aac86c633aab96b734dba3835e_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/568031aac86c633aab96b734dba3835e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/56c8fcd83f1ab2e62033a1f6e7cfa3a1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/56c8fcd83f1ab2e62033a1f6e7cfa3a1_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/56c8fcd83f1ab2e62033a1f6e7cfa3a1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/58a8190bc204c7bf623394f3fd0fa968_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/58a8190bc204c7bf623394f3fd0fa968_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/58a8190bc204c7bf623394f3fd0fa968_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/59368942873b0c35eef79a7a985025dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5e185b54d270cd15d1299478a13f1f97_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5e185b54d270cd15d1299478a13f1f97_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5e185b54d270cd15d1299478a13f1f97_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5e38bd2f95d0f22ab5091fa99f29ff01_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5e38bd2f95d0f22ab5091fa99f29ff01_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5e38bd2f95d0f22ab5091fa99f29ff01_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5f533a4c9388beded5aba3c037ab7be8_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5f533a4c9388beded5aba3c037ab7be8_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5f533a4c9388beded5aba3c037ab7be8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5f775274defe2a58cc4b4498acd55a6c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5f775274defe2a58cc4b4498acd55a6c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5f775274defe2a58cc4b4498acd55a6c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5fa61cb21e87cecbe7049420f633a811_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5fa61cb21e87cecbe7049420f633a811_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5fa61cb21e87cecbe7049420f633a811_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5fbe6b9515c3d8f7d2526ca5bfbd012d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5fbe6b9515c3d8f7d2526ca5bfbd012d_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/5fbe6b9515c3d8f7d2526ca5bfbd012d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/600fbaabf10e40148498bda9961511ab_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/600fbaabf10e40148498bda9961511ab_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/600fbaabf10e40148498bda9961511ab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/61539d9502aced9814cd56cc609f419b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/61539d9502aced9814cd56cc609f419b_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/61539d9502aced9814cd56cc609f419b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/624dbf9b985f5bd85e902ec59b87ba4f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/624dbf9b985f5bd85e902ec59b87ba4f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/624dbf9b985f5bd85e902ec59b87ba4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6254e6ff201e39d022a590c8b6e3de2b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/631360156a16ba258241007e2283213d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/631360156a16ba258241007e2283213d_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/631360156a16ba258241007e2283213d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/638d4a1e55dbf75a122c4f778258f3cb_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/638d4a1e55dbf75a122c4f778258f3cb_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/638d4a1e55dbf75a122c4f778258f3cb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/654cccb64b578f1e4a7d09b7ee5626b5_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/654cccb64b578f1e4a7d09b7ee5626b5_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/654cccb64b578f1e4a7d09b7ee5626b5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6588b1c7f14069d96744b473ad663248_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/65cd234286445e716c91a9f734e510d9_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/65cd234286445e716c91a9f734e510d9_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/65cd234286445e716c91a9f734e510d9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/65cf9633846ecab19f1a0b92fa8ecd9a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/65cf9633846ecab19f1a0b92fa8ecd9a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/65cf9633846ecab19f1a0b92fa8ecd9a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/67da7316a30be623c4c053d4d1eff952_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/67da7316a30be623c4c053d4d1eff952_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/67da7316a30be623c4c053d4d1eff952_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/67fd5cc2c3bec87e3a06d5ad92744560_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/67fd5cc2c3bec87e3a06d5ad92744560_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/67fd5cc2c3bec87e3a06d5ad92744560_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg deleted file mode 100644 index bf238570411b2c3c4801758e0b4fee8375ccb9f4..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef39b9b0dadf1b084c8b8bc63a0ff7d1585b6d745ca12ad8368f11082cad5a0 -size 4493 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/686705f78594bdc18af4f9cb04b455e0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/686705f78594bdc18af4f9cb04b455e0_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/686705f78594bdc18af4f9cb04b455e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6883c4a2aeca4cb08a9a7a95faa2645a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6883c4a2aeca4cb08a9a7a95faa2645a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6883c4a2aeca4cb08a9a7a95faa2645a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6983ff962c0a32659de18c30790e1519_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6983ff962c0a32659de18c30790e1519_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6983ff962c0a32659de18c30790e1519_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6a2e100d305cbbcf8e9e794d39ad9c75_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6a2e100d305cbbcf8e9e794d39ad9c75_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6a2e100d305cbbcf8e9e794d39ad9c75_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6da08196de6831d44259c8a25e416c2d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6da08196de6831d44259c8a25e416c2d_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6da08196de6831d44259c8a25e416c2d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6f52aa6e2a0da763ca0091b3771d1c25_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6f52aa6e2a0da763ca0091b3771d1c25_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6f52aa6e2a0da763ca0091b3771d1c25_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6faa2c6456db4413927b19b9cbfe4176_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6faa2c6456db4413927b19b9cbfe4176_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6faa2c6456db4413927b19b9cbfe4176_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6fd1b2efc24f6bc630680f8de7c31576_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6fd1b2efc24f6bc630680f8de7c31576_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6fd1b2efc24f6bc630680f8de7c31576_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6fdf990c9cc944ccf5688a804f6ed35c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6fdf990c9cc944ccf5688a804f6ed35c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6fdf990c9cc944ccf5688a804f6ed35c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/70dab5b17ce15a319dd531324de9c9fe_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/70dab5b17ce15a319dd531324de9c9fe_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/70dab5b17ce15a319dd531324de9c9fe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7183d7b44e8c46abd64438b3894a0902_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7183d7b44e8c46abd64438b3894a0902_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7183d7b44e8c46abd64438b3894a0902_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7469f7d890531be66ff585ef273e6c1b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7469f7d890531be66ff585ef273e6c1b_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7469f7d890531be66ff585ef273e6c1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/75e91977269ab11e564cb85a58afda1b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/75e91977269ab11e564cb85a58afda1b_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/75e91977269ab11e564cb85a58afda1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/76fb24764e6c9c644b30056855c81aa5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/77464a47f104d0d647b2414591137b64_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/77464a47f104d0d647b2414591137b64_img.jpg deleted file mode 100644 index 2c1d5fa4d158156e866e41a5007faa66d56802f8..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/77464a47f104d0d647b2414591137b64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:39c1edfa6d5dce2171e85baf5688dc2ff5e4cb406e0b216ab23dd55f7d7fcca6 -size 45627 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/775e52e123d544d7749813722a13e82f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/775e52e123d544d7749813722a13e82f_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/775e52e123d544d7749813722a13e82f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/782012363ffb161a84600666895ae6e4_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/782012363ffb161a84600666895ae6e4_img.jpg deleted file mode 100644 index bf238570411b2c3c4801758e0b4fee8375ccb9f4..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/782012363ffb161a84600666895ae6e4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef39b9b0dadf1b084c8b8bc63a0ff7d1585b6d745ca12ad8368f11082cad5a0 -size 4493 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 141fbdc62d6a7c4f6feda1bfe8c44d950c04af96..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:db39ee763a9352985e7ffff991041a5361b07b2854780b51e34840f4adc5b3e0 -size 4549 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg deleted file mode 100644 index cc226d47b008150f3d8402a44fdaec646651963c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:80ae20069d033c9eef87dc62cb7d3df87d88429a94235ec7819b6697206c799f -size 15452 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7e86b957cd3c33e57d22a8389947ce46_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7e86b957cd3c33e57d22a8389947ce46_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7e86b957cd3c33e57d22a8389947ce46_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/81513bd390d91f2e7a9b865cf50dce69_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/81513bd390d91f2e7a9b865cf50dce69_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/81513bd390d91f2e7a9b865cf50dce69_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/87755376ccda1904b0f5e60a7dd2c465_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/87755376ccda1904b0f5e60a7dd2c465_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/87755376ccda1904b0f5e60a7dd2c465_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8a02c1bd6ac8111aead3a70a4aba750e_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8a02c1bd6ac8111aead3a70a4aba750e_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8a02c1bd6ac8111aead3a70a4aba750e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8b36c56b042bf3e7ec9b29f35568fe66_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8b36c56b042bf3e7ec9b29f35568fe66_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8b36c56b042bf3e7ec9b29f35568fe66_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8b4befaffc5166da571069410e207aea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8bd9527f7ae16517a90c44e34ced8589_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8bd9527f7ae16517a90c44e34ced8589_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8bd9527f7ae16517a90c44e34ced8589_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8becef26f03c7a4b80768cf8100e0951_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8becef26f03c7a4b80768cf8100e0951_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8becef26f03c7a4b80768cf8100e0951_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8cf3db894a4e83dbac8b094528b24430_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8cf3db894a4e83dbac8b094528b24430_img.jpg deleted file mode 100644 index 938fd786025063a9c6794111fb69bd77335965cb..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8cf3db894a4e83dbac8b094528b24430_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:212b63a89a9aca91bc3cfde6374ccfac83928c957707deb22ff82d98204b63cc -size 4519 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8e14350b4b669119a3bdfca7869110ca_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8e14350b4b669119a3bdfca7869110ca_img.jpg deleted file mode 100644 index 115a8dd85a77eb912312e04aff592b5a6c6d0266..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8e14350b4b669119a3bdfca7869110ca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:793415538f7c29cc1ca42c5b06f90221613cdff6300de5e619b41092f3e66d40 -size 11762 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/901b345e560dfa29a2c7967f95bd54bb_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/901b345e560dfa29a2c7967f95bd54bb_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/901b345e560dfa29a2c7967f95bd54bb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/92e0feed183e6643329e6c9d933b50f1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/92e0feed183e6643329e6c9d933b50f1_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/92e0feed183e6643329e6c9d933b50f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/92eab1c7ce3162be3f7dabe7a3035249_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/933f4267f9d2b0ece044e7649be53447_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/933f4267f9d2b0ece044e7649be53447_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/933f4267f9d2b0ece044e7649be53447_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/94b678292f1b426e0d16117bb08bfba5_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/94b678292f1b426e0d16117bb08bfba5_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/94b678292f1b426e0d16117bb08bfba5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/957e0a1d31f6b69dcd8a355fd185031a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/957e0a1d31f6b69dcd8a355fd185031a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/957e0a1d31f6b69dcd8a355fd185031a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/964fc0fd54c825b85166fb5a00aa716d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/964fc0fd54c825b85166fb5a00aa716d_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/964fc0fd54c825b85166fb5a00aa716d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/970df246bd8b45f590e294d25c1bb60a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/970df246bd8b45f590e294d25c1bb60a_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/970df246bd8b45f590e294d25c1bb60a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/98d7c3a3783b091ac41fd87427f1c8e1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/98d7c3a3783b091ac41fd87427f1c8e1_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/98d7c3a3783b091ac41fd87427f1c8e1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9b3e75266694bdf164036baf1bb25422_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9b3e75266694bdf164036baf1bb25422_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9b3e75266694bdf164036baf1bb25422_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9b5bae50a8a287c353f79cf9b43c8a4a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9b5bae50a8a287c353f79cf9b43c8a4a_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9b5bae50a8a287c353f79cf9b43c8a4a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg deleted file mode 100644 index 37e16ee533fed81b009e241b32c8780acb3bd4d9..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9b6b5924b48bf2fd5f347f88f06f45b3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2bf25a43ab79b1e78f2895cb58f1959b7ff54e45818d5adeadfa859a0b4a5831 -size 50977 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9ba81901bf408ed950fce012b4890b1d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9e4bce3d0ef8a18588aa58fd3db1cbe3_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9e4bce3d0ef8a18588aa58fd3db1cbe3_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9e4bce3d0ef8a18588aa58fd3db1cbe3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9edb9da00a36a0e140e99e072096ee53_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9edb9da00a36a0e140e99e072096ee53_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/9edb9da00a36a0e140e99e072096ee53_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a3144f9447b85aa19cc0a88f603fb688_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a3144f9447b85aa19cc0a88f603fb688_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a3144f9447b85aa19cc0a88f603fb688_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a5f09d21af8c3e909361c622a501c7f2_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a5f09d21af8c3e909361c622a501c7f2_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a5f09d21af8c3e909361c622a501c7f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a90eb5fc0985caf25c17075250c86908_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a90eb5fc0985caf25c17075250c86908_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a90eb5fc0985caf25c17075250c86908_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a93f84544e1dc2029d8b41292b8b5c03_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a93f84544e1dc2029d8b41292b8b5c03_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a93f84544e1dc2029d8b41292b8b5c03_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ab56946aacb4682bb58d2c3e64a9c59e_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ab56946aacb4682bb58d2c3e64a9c59e_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ab56946aacb4682bb58d2c3e64a9c59e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/abdd3f96a1e296c46300f2a326213dc0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/abdd3f96a1e296c46300f2a326213dc0_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/abdd3f96a1e296c46300f2a326213dc0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ac1c0fb704fa8fc69e7934267bc074d4_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ac1c0fb704fa8fc69e7934267bc074d4_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ac1c0fb704fa8fc69e7934267bc074d4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/aef4390a4629604196222b9ed006a786_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/aef4390a4629604196222b9ed006a786_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/aef4390a4629604196222b9ed006a786_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/af54a0b30d50f3f8620b331cdc59ae3a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/af54a0b30d50f3f8620b331cdc59ae3a_img.jpg deleted file mode 100644 index c54e114281d1c93b9937b4c5743e15f2ad6b44fb..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/af54a0b30d50f3f8620b331cdc59ae3a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ca2a045ed1d6d32df2c638c4d9108391580309fd9bb4ffa368afdc6e8c85a95e -size 1361 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b0211cee4b20034939d883ac0d70f696_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b0211cee4b20034939d883ac0d70f696_img.jpg deleted file mode 100644 index cef66212f310d41ec39ba4fb70fca641b4839ac7..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b0211cee4b20034939d883ac0d70f696_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1e2f4dbe0d7f81915e101c658def27b21681640bbaa3b79339c70bda370c7c20 -size 30877 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b1fe142ff4f5589424237da7b11b41b6_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b1fe142ff4f5589424237da7b11b41b6_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b1fe142ff4f5589424237da7b11b41b6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b323defd3d8e30a4add43c6c501e5b0d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b323defd3d8e30a4add43c6c501e5b0d_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b323defd3d8e30a4add43c6c501e5b0d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b324224acc41e653a93d145e61f98d8c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b324224acc41e653a93d145e61f98d8c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b324224acc41e653a93d145e61f98d8c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b3c108e7145f2017957569d06ea359cb_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b3c108e7145f2017957569d06ea359cb_img.jpg deleted file mode 100644 index 3916ee2349e661afb23c2f9f907026310876aaf4..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b3c108e7145f2017957569d06ea359cb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3aa463851bf65006991f2f510113fea9a73e388f02e6ad4e11ae7c3777b20c06 -size 11490 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b62e6e3b1cbec5de7e750dc0d46bcc79_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b62e6e3b1cbec5de7e750dc0d46bcc79_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b62e6e3b1cbec5de7e750dc0d46bcc79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b6cafcdfab7ca53f640ddc2d2bae5261_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b6cafcdfab7ca53f640ddc2d2bae5261_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b6cafcdfab7ca53f640ddc2d2bae5261_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b7deb15a64425aa7a86d391b2f4c848f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b7deb15a64425aa7a86d391b2f4c848f_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b7deb15a64425aa7a86d391b2f4c848f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b90144cfbb81a2d610d920240fda689d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b90144cfbb81a2d610d920240fda689d_img.jpg deleted file mode 100644 index fe2d20cd7dbd8bbac310b1ae2e4102bb2b3396bb..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b90144cfbb81a2d610d920240fda689d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ccd1851c3af2bd7e9e1b5078e3e471de3a422593fa8d7ce900ede09be57c1a09 -size 62446 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/b9335fb94d07a154a00c3c63aaa36096_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bb9f586190c7197099d25db7df9050af_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bb9f586190c7197099d25db7df9050af_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bb9f586190c7197099d25db7df9050af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bc4568cde39ed422b1f3231304177da0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bc4568cde39ed422b1f3231304177da0_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bc4568cde39ed422b1f3231304177da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bcae27bc6aeb49b97b6d51dce8d5c1af_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bcae27bc6aeb49b97b6d51dce8d5c1af_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bcae27bc6aeb49b97b6d51dce8d5c1af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bcb0b443fcfea25dcb7005487af9200d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bcb0b443fcfea25dcb7005487af9200d_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bcb0b443fcfea25dcb7005487af9200d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bd74854ea023b9c189707fa35cdd37ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bdcfd1ae573f069075086d7759e45c15_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bdcfd1ae573f069075086d7759e45c15_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bdcfd1ae573f069075086d7759e45c15_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bec099e513efaa5246b7005bfccbd8f6_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bec099e513efaa5246b7005bfccbd8f6_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bec099e513efaa5246b7005bfccbd8f6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bfcea196796f3bc23aeb4499b396cab1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bfcea196796f3bc23aeb4499b396cab1_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/bfcea196796f3bc23aeb4499b396cab1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c04d640f7b0cf74f8e1a1bfa8ebbde29_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c075f11b8ee283222cbed999bc5a392c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c075f11b8ee283222cbed999bc5a392c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c075f11b8ee283222cbed999bc5a392c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c0912cb53f8cc1be7ad8d288f5cb0fd0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c0912cb53f8cc1be7ad8d288f5cb0fd0_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c0912cb53f8cc1be7ad8d288f5cb0fd0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c18b9d7d4dc149266c9bf688a50497a5_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c18b9d7d4dc149266c9bf688a50497a5_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c18b9d7d4dc149266c9bf688a50497a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c2fc2621e8206d24427b56bcb2398fc0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c2fc2621e8206d24427b56bcb2398fc0_img.jpg deleted file mode 100644 index 64a04418fde9d71c4322f4d39590f2c2617c300a..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c2fc2621e8206d24427b56bcb2398fc0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c65a3ba0cecd6fa813602a6f2074a20c0ab3c0fcc3147bb9c9e1768f41140490 -size 33940 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c2ff6339c62f961f2abd954e987c0082_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c2ff6339c62f961f2abd954e987c0082_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c2ff6339c62f961f2abd954e987c0082_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c3c2b3eb8e16ab6cd6acdec0fcf82999_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c3c2b3eb8e16ab6cd6acdec0fcf82999_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c3c2b3eb8e16ab6cd6acdec0fcf82999_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c4738e5ac7f134cb42cac8a06858b8ac_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c4738e5ac7f134cb42cac8a06858b8ac_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c4738e5ac7f134cb42cac8a06858b8ac_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c5eb42ed730ecb12621fc63444830d4b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c5eb42ed730ecb12621fc63444830d4b_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c5eb42ed730ecb12621fc63444830d4b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c6fd5cb542ee6c63f2acd62896ffcc35_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c6fd5cb542ee6c63f2acd62896ffcc35_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c6fd5cb542ee6c63f2acd62896ffcc35_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c6ffc947df5e0a0aee6304d52999ee3b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c6ffc947df5e0a0aee6304d52999ee3b_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c6ffc947df5e0a0aee6304d52999ee3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c76f518c4d95210969837b001e52d73b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c76f518c4d95210969837b001e52d73b_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c76f518c4d95210969837b001e52d73b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c95ab75ce8f67ea4200944468d7aea30_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c95ab75ce8f67ea4200944468d7aea30_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c95ab75ce8f67ea4200944468d7aea30_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/c964194b41a0636cf95ab198c9196bcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cb01dfc2db37c44f7ff39b67b5f9d3da_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cb01dfc2db37c44f7ff39b67b5f9d3da_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cb01dfc2db37c44f7ff39b67b5f9d3da_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cd9d31fecf784261aecb1220c3fe10a5_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cd9d31fecf784261aecb1220c3fe10a5_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cd9d31fecf784261aecb1220c3fe10a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cdb7ea1e3072c3b9885c63d496dc7d84_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cdb7ea1e3072c3b9885c63d496dc7d84_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cdb7ea1e3072c3b9885c63d496dc7d84_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ce68ff30159c3788e28d166216807520_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ce68ff30159c3788e28d166216807520_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ce68ff30159c3788e28d166216807520_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ce98da47ddd68c059657e5cfeeb6beef_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ce98da47ddd68c059657e5cfeeb6beef_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ce98da47ddd68c059657e5cfeeb6beef_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cec3dce43502075ea34c4480ec856a66_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cec3dce43502075ea34c4480ec856a66_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cec3dce43502075ea34c4480ec856a66_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cf08e441bafa27592ca7f62e33866b53_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cf08e441bafa27592ca7f62e33866b53_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cf08e441bafa27592ca7f62e33866b53_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cf8309144b64cc604254b140a5986dc0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cf8309144b64cc604254b140a5986dc0_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/cf8309144b64cc604254b140a5986dc0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d175930b7519b8f2f801b636dcce54c8_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d175930b7519b8f2f801b636dcce54c8_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d175930b7519b8f2f801b636dcce54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d1c239cc875fea808eda1d61ca630fac_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d1c239cc875fea808eda1d61ca630fac_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d1c239cc875fea808eda1d61ca630fac_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d35a80e3faed208324083399568c7461_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d35a80e3faed208324083399568c7461_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d35a80e3faed208324083399568c7461_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d3846f400737fcc7508ce3611705486a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d3846f400737fcc7508ce3611705486a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d3846f400737fcc7508ce3611705486a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d53c20c28af383ce49c214cf2603fbc3_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d53c20c28af383ce49c214cf2603fbc3_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d53c20c28af383ce49c214cf2603fbc3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d5a832cb05eb9106e3139f2c68ba9dc4_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d5a832cb05eb9106e3139f2c68ba9dc4_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d5a832cb05eb9106e3139f2c68ba9dc4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d74bbadcdb9933d40a743043ad865c65_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d74bbadcdb9933d40a743043ad865c65_img.jpg deleted file mode 100644 index bf238570411b2c3c4801758e0b4fee8375ccb9f4..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d74bbadcdb9933d40a743043ad865c65_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef39b9b0dadf1b084c8b8bc63a0ff7d1585b6d745ca12ad8368f11082cad5a0 -size 4493 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d7b324ee9d9caae532ed5e898261c278_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d7b324ee9d9caae532ed5e898261c278_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d7b324ee9d9caae532ed5e898261c278_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d7b50eca959bf7bb5bc7a1e2fda6008b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d7b50eca959bf7bb5bc7a1e2fda6008b_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d7b50eca959bf7bb5bc7a1e2fda6008b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d7c4779f679cb390727824a9896ecb5f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d7cfea99678a163f260c6ecfba27ce8d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d7cfea99678a163f260c6ecfba27ce8d_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d7cfea99678a163f260c6ecfba27ce8d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d809da419492e18bada207fd4e79bba1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d809da419492e18bada207fd4e79bba1_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d809da419492e18bada207fd4e79bba1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/da03733d99ab91ed54613c6799a153ba_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/da03733d99ab91ed54613c6799a153ba_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/da03733d99ab91ed54613c6799a153ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/db17b491805d766560e8c237b84299f1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/db17b491805d766560e8c237b84299f1_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/db17b491805d766560e8c237b84299f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/dda029be056105746c70a40e80692e58_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/dda029be056105746c70a40e80692e58_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/dda029be056105746c70a40e80692e58_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ddcaa42bc4cc7e6a8ae2695e5cbaf790_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ddcaa42bc4cc7e6a8ae2695e5cbaf790_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ddcaa42bc4cc7e6a8ae2695e5cbaf790_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/de35ef8911c5beed69b407fe13b6de3c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/de35ef8911c5beed69b407fe13b6de3c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/de35ef8911c5beed69b407fe13b6de3c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/df061c76cc6b43c8454b267631d4a585_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/df061c76cc6b43c8454b267631d4a585_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/df061c76cc6b43c8454b267631d4a585_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/df82d77a0d2637cbf2da9ea920a554fa_img.jpg deleted file mode 100644 index 8741bad9706e88357a5bbd64af5061eb621b10a0..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/df82d77a0d2637cbf2da9ea920a554fa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c0f5531166c76985b0537921095ed8b8c4811ee69c4158328b50d93ccc1d07c7 -size 44189 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e0c32e027f49e7404cffe15b93075903_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e0c32e027f49e7404cffe15b93075903_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e0c32e027f49e7404cffe15b93075903_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e21c1cb4c57b5f20293a776cbdb8d31f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e21c1cb4c57b5f20293a776cbdb8d31f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e21c1cb4c57b5f20293a776cbdb8d31f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e2bef29cdcf149c935e170586b26ae9c_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e2bef29cdcf149c935e170586b26ae9c_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e2bef29cdcf149c935e170586b26ae9c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 5ea9ae9194f7b34b2cc65cfadbc793ea1665fdee..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2a4b269f41327c108671a0dc91ce78a790dbc91b34a39bd88709c7e4474a7073 -size 4436 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg deleted file mode 100644 index 0a32a8958f6109ad4aaf4852df296ab34550726c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c7cfaa421bb3fc788e7f1750166e5842ca41043783a220a87e4c283205ae72f7 -size 4438 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e390f5f3b3b1bf44f4179e1e284ec9b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 5ea9ae9194f7b34b2cc65cfadbc793ea1665fdee..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2a4b269f41327c108671a0dc91ce78a790dbc91b34a39bd88709c7e4474a7073 -size 4436 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e63b8cb7ecf440e9fa5f83769248f236_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e63b8cb7ecf440e9fa5f83769248f236_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e63b8cb7ecf440e9fa5f83769248f236_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg deleted file mode 100644 index ca8d1c1bbd9b82bdedb5e854afbe0eba6af38f14..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5967355e2b3522ae6773b7e493aed406da6d4c1374c9123c71295a9480609f26 -size 4518 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e7b5a7456650ca93650c140cc9a7cab1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e7b5a7456650ca93650c140cc9a7cab1_img.jpg deleted file mode 100644 index 03b4f87ee471a945b944f38ebf9eedd414ceff4f..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e7b5a7456650ca93650c140cc9a7cab1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:173bf2386fa9fb74caf2cfd73ba2aa8dc616cffbcf1655776ea6022855fc001a -size 4515 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e7beed289e3bb0399e3188df934dbd85_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e7beed289e3bb0399e3188df934dbd85_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e7beed289e3bb0399e3188df934dbd85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e8411aa566660d595a395a2f41d1f009_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e88514a46354e0a227f104f25530288e_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e88514a46354e0a227f104f25530288e_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e88514a46354e0a227f104f25530288e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e8edb46e6932fd994c7cbef114ad743a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e8edb46e6932fd994c7cbef114ad743a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e8edb46e6932fd994c7cbef114ad743a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e9f27efdab43ce5b3ecbe74f09c4cfe2_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e9f27efdab43ce5b3ecbe74f09c4cfe2_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/e9f27efdab43ce5b3ecbe74f09c4cfe2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/eb48ed8d7efab7455ebd9f62bb214f33_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/eb48ed8d7efab7455ebd9f62bb214f33_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/eb48ed8d7efab7455ebd9f62bb214f33_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ecc17272f7951b956169a2905f5862ea_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ecc17272f7951b956169a2905f5862ea_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ecc17272f7951b956169a2905f5862ea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/eda00580f1bc1ce2aa1e306b85a94dbd_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/eda00580f1bc1ce2aa1e306b85a94dbd_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/eda00580f1bc1ce2aa1e306b85a94dbd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/edcab60b3c92e05a58f7411ce1d16288_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/edcab60b3c92e05a58f7411ce1d16288_img.jpg deleted file mode 100644 index 938fd786025063a9c6794111fb69bd77335965cb..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/edcab60b3c92e05a58f7411ce1d16288_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:212b63a89a9aca91bc3cfde6374ccfac83928c957707deb22ff82d98204b63cc -size 4519 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ee5bafe10ff1ed7c138abb928006e86d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ee5bafe10ff1ed7c138abb928006e86d_img.jpg deleted file mode 100644 index 7146cbf09fac2302955ac865c80323fa8a21b338..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ee5bafe10ff1ed7c138abb928006e86d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fba919a7ce74e565f077bf31e78091383ee678492a94d861dee90574d093529a -size 4530 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ee78d993a5565b0f905888c3f904da99_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ee78d993a5565b0f905888c3f904da99_img.jpg deleted file mode 100644 index bf238570411b2c3c4801758e0b4fee8375ccb9f4..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ee78d993a5565b0f905888c3f904da99_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef39b9b0dadf1b084c8b8bc63a0ff7d1585b6d745ca12ad8368f11082cad5a0 -size 4493 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ef484b2179ee14c86e53e9f5b3c0d848_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f0c19cb19ae7a343d5f9202936fb6073_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f0c19cb19ae7a343d5f9202936fb6073_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f0c19cb19ae7a343d5f9202936fb6073_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f19f0f73f11a36b497d3c8ef01dff1b5_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f19f0f73f11a36b497d3c8ef01dff1b5_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f19f0f73f11a36b497d3c8ef01dff1b5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f1d870c901879a8a045ece56cc5b1980_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f1d870c901879a8a045ece56cc5b1980_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f1d870c901879a8a045ece56cc5b1980_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f3d3e0a60abdafe4358260627581113a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f3d3e0a60abdafe4358260627581113a_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f3d3e0a60abdafe4358260627581113a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg deleted file mode 100644 index 0636bd76d0593ab345ffc1f96be61672a780d953..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95b8b8d26b1fc9b6ef98cc04993f493035ce83f81517cf3f90266b219db6eca0 -size 4461 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f54a2a3dde9b823d049845884cbd166a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f54a2a3dde9b823d049845884cbd166a_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f54a2a3dde9b823d049845884cbd166a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f74adaa1840504407cd4272995426f82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f92ebf4eb3d62b7dfa401644b0b6e40d_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f92ebf4eb3d62b7dfa401644b0b6e40d_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f92ebf4eb3d62b7dfa401644b0b6e40d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fa9f113a14954a4741c64d911be324e9_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fa9f113a14954a4741c64d911be324e9_img.jpg deleted file mode 100644 index c56d64e92a7ca1a6ce8bb14ee8e154d92e8e5dec..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fa9f113a14954a4741c64d911be324e9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:62390c9f3f9def1f9fba0b9adc45dc37d0f1af294902b7abda3a738e2dcef52f -size 4522 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fabe931a97ba32b2e81af497e57033f1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fabe931a97ba32b2e81af497e57033f1_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fabe931a97ba32b2e81af497e57033f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fac227c65a311c313325216dcf59591f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fac227c65a311c313325216dcf59591f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fac227c65a311c313325216dcf59591f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/facce731b2dbfae43a8609231a700be1_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/facce731b2dbfae43a8609231a700be1_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/facce731b2dbfae43a8609231a700be1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fb53db2423b5ba8ab6dc10dc9f384450_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fb53db2423b5ba8ab6dc10dc9f384450_img.jpg deleted file mode 100644 index d3bf508a5988b6ab8ffc5e3ba6170601d061ef8c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fb53db2423b5ba8ab6dc10dc9f384450_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61ef066a4169764eca2098843631cc9a3b333a09f2445b051983805e3baa115 -size 4532 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fbd10feb132607962f09a7f6bfb69df6_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fbd10feb132607962f09a7f6bfb69df6_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fbd10feb132607962f09a7f6bfb69df6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fbee1b51966e04afd72119133d952535_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fbee1b51966e04afd72119133d952535_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fbee1b51966e04afd72119133d952535_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fe07d230fde7b9a0c4efa6ddb07e8595_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fe07d230fde7b9a0c4efa6ddb07e8595_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fe07d230fde7b9a0c4efa6ddb07e8595_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fe77f3082a0ce5eaa1f8f74877eb10bd_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fe77f3082a0ce5eaa1f8f74877eb10bd_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fe77f3082a0ce5eaa1f8f74877eb10bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fec5f1bac5cf3187f7618d1adb95871f_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fec5f1bac5cf3187f7618d1adb95871f_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/fec5f1bac5cf3187f7618d1adb95871f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index af04cc77ff5483c3cbdc302b15170c357f5b874c..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b26e91c0f704df9c8c02baed58d8bc83494bbde1da00021d9767b1c052c8225 -size 4524 diff --git a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ff81d88ebb5c5673a41bbcf9e41f6763_img.jpg b/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ff81d88ebb5c5673a41bbcf9e41f6763_img.jpg deleted file mode 100644 index be59f3871b1e9cdac868bc0305e56a47e1e23566..0000000000000000000000000000000000000000 --- a/files/WG5/O-RAN.WG5.TS.IOT.0-R005-v15.00/images/ff81d88ebb5c5673a41bbcf9e41f6763_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60c64a05d30c847e6433a623cc40d8b0f8256c4f1a2bb156d7372cd79a84447a -size 4572 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/doc.md b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/doc.md deleted file mode 100644 index 522390bd6de027b36783b8d0256c9056c294da83..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/doc.md +++ /dev/null @@ -1,585 +0,0 @@ - - -# **O-RAN Work Group 6****O-Cloud Interoperability Test (IOT) 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., Buschkauler Weg 27, 53347 Alfter, Germany - -Register of Associations, Bonn VR 11238, VAT ID DE321720189 - -# Contents - -| | | -|-------------------------------------------------------------------------------|----| -| List of Figures..... | 4 | -| List of tables ..... | 4 | -| 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 ..... | 6 | -| 3.1 Terms ..... | 6 | -| 3.2 Abbreviations..... | 7 | -| 4 Testing methodology ..... | 7 | -| 4.1 System under test..... | 7 | -| 4.2 Test method ..... | 10 | -| 4.2.1 Objective ..... | 10 | -| 4.2.2 Testing Tools and set-up ..... | 10 | -| 4.2.3 Testing procedure..... | 10 | -| 4.2.4 Statistics and analysis of key indicators ..... | 11 | -| 5 Notification API IOT..... | 11 | -| 5.1 General..... | 11 | -| 5.2 Test Configuration ..... | 11 | -| 5.2.1 System Under Test requirements ..... | 11 | -| 5.2.2 Test Tools and Simulators capabilities..... | 12 | -| 5.3 Test Cases ..... | 12 | -| 5.3.1 Push mode event notification ..... | 12 | -| 5.3.2 Pull mode event notification ..... | 13 | -| 6 AAL Interface IOT ..... | 14 | -| 6.1 General..... | 14 | -| 6.2 Test Configuration ..... | 14 | -| 6.2.1 System Under Test requirements ..... | 14 | -| 6.2.2 Test Tools and Simulators capabilities..... | 14 | -| 6.3 Test Cases ..... | 14 | -| 7 O2 Interface IOT ..... | 14 | -| 7.1 General..... | 14 | -| 7.2 Test Configuration ..... | 15 | -| 7.2.1 System Under Test requirements ..... | 15 | -| 7.2.2 Test Tools and Simulators capabilities..... | 15 | -| 7.3 O2 IMS Test ..... | 15 | -| 7.3.1 General..... | 15 | -| 7.3.2 Case 1 ..... | 15 | -| 7.4 O2 DMS Test..... | 16 | -| 7.4.1 General..... | 16 | -| 7.4.2 O2 DMS ETSI NFV Profile Test ..... | 16 | -| 7.4.3 O2 DMS Kubernetes Profile Test ..... | 16 | -| Annex A (normative): Checklist for Cases applies to O-Cloud technologies..... | 17 | -| A.1 O-Cloud technologies ..... | 17 | - -| | | | -|-----|----------------------------------------------------|----| -| A.2 | Cloud Technology Applicability of test cases ..... | 17 | -| A.3 | Case Traceability ..... | 17 | - -# --- List of figures - -| | | -|-------------------------------------------------------------------------------------|----| -| Figure 4.1-1: SUT configuration for Notification APIs IOT ..... | 8 | -| Figure 4.1-2: SUT configuration for AAL interface IOT (AALI-C-Mgmt Interface) ..... | 9 | -| Figure 4.1-3: SUT configurations for AALI IOT(AALI-C-App/AALI-P) ..... | 9 | -| Figure 4.1-4: SUT configurations for O2 IMS IOT ..... | 9 | -| Figure 4.1-5: SUT configurations for O2 DMS IOT ..... | 10 | -| Figure 5.2-1: Configuration of O-Cloud Notification API IOT ..... | 12 | -| Figure 7.3.2.1-1: O2 IMS IOT SUT ..... | 15 | - -# --- List of tables - -| | | -|---------------------------------------------------------------------------------|----| -| Table 4.1-1: O-Cloud IOT and corresponding Interfaces/APIs, DUTs and SUTs ..... | 8 | -| Table A.2-1: O-Cloud Technology Applicability of Test Cases ..... | 17 | -| Table A.3-1: Case Traceability ..... | 17 | - -# Foreword - -This Technical Specification (TS) has been produced by WG6 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 specifies O-Cloud Interoperability testing (IOT) in accordance with O-RAN specified interfaces as defined in [3], [4], [9], [10] and [11] which includes O-Cloud Notification API, AAL and O2. - -# 1 Scope - -The present document specifies IOT testing for O-Cloud and peer device(s) or system(s) from different vendors connected by O-Cloud Interfaces/APIs. This document will specify the SUTs, testing methodology and the IOT test cases over O-Cloud Notification API, AAL O2 IMS and DMS interface. - -# 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. - -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.O-RAN Architecture Description-v06.00, Technical Specification. -- [2] Void -- [3] O-RAN.WG6.O-Cloud Notification API-v03: “O-Cloud Notification API Specification for Event Consumers”. -- [4] O-RAN.WG6.AAL-Common-API-R003-v05.00: “[AAL Common API TS](#)” -- [5] O-RAN.WG6.AAL-GaNP-R003-v07.00: “[AAL General Aspects and Principles TS](#)” -- [6] Void -- [7] Void -- [8] Void -- [9] O-RAN.WG6.TS.O2IMS-INTERFACE-R004-v08.00: “O2ims Interface Specification” -- [10] O-RAN.WG6.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R004-v08.0: “O2dms Interface Specification: Profile based on ETSI NFV Protocol and Data Models” -- [11] O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R003-v05.00: “O2dms Interface Specification: Kubernetes Native API Profile for Containerized NFs” -- [12] O-RAN.WG6.ORCH-USE-CASES-R004-v12.00: “Cloudification and Orchestration Use Cases” -- [13] O-RAN.WG6.TS.O-CLOUD-INTF-CONF-R004-v04.01 - -## 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. - -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. - -# 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [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 3GPP TR 21.905 [i.1]. - -**O-Cloud** This refers to a collection of O-Cloud Resource Pools at one or more location and the software to manage Nodes and Deployments hosted on them. An O-Cloud will include functionality to support - -both Deployment-plane and Management services. The O-Cloud provides a single logical reference point for all O-Cloud Resource Pools within the O-Cloud boundary. - -| | | -|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| O-CU | O-RAN Centralized Unit – a logical node hosting PDCP, RRC, SDAP and other control functions. | -| 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). | - -## 3.2 Abbreviations - -For the purposes of this document, the abbreviations given in 3GPP TR 21.905 [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 3GPP TR 21.905 [i.1]. - -| | | -|-------------|-------------------------------------------------------------| -| 3GPP | Third Generation Partnership Project | -| AAL | Acceleration Abstraction Layer | -| AALI-C | Acceleration Abstraction Layer Interface-Common | -| AALI-C-Mgmt | Acceleration Abstraction Layer Interface-Common-Management | -| AALI-C-App | Acceleration Abstraction Layer Interface-Common-Application | -| AALI-P | Acceleration Abstraction Layer Interface-Profile | -| API | Application Programming Interface | -| CPU | Central Processing Unit | -| CU | Centralized Unit as defined by 3GPP | -| DU | Distributed Unit as defined by 3GPP | -| DUT | Device Under Test | -| EC | Event Producer | -| EP | Event Consumer | -| HAM | Hardware Acceleration Manager | -| IMS | Infrastructure Management Services | -| IOT | Interoperability Test | -| O-Cloud | O-RAN Cloud Platform | -| O-CU | O-RAN Centralized Unit | -| O-DU | O-RAN Distributed Unit | -| O-RU | O-RAN Radio Unit | -| OS | Operating System | -| PTP | Precision Time Protocol | -| RAN | Radio Access Network | -| RIC | RAN Intelligent Controller | -| SMO | Service Management and Orchestration | -| SUT | System Under Test | -| TS | Technical Specification | -| vCPU | Virtual CPU | -| VM | Virtual Machine | -| WG | Working Group | - -# 4 Testing methodology - -## 4.1 System under test - -Interoperability testing is performed to validate the end-to-end functionality between the O-Cloud and peer devices or systems from different vendors connected by interfaces as defined in [3], [4], [9], [10] and [11]. This document primarily focuses on scenarios where the System Under Test (SUT) for interoperability testing is comprised of different Device Under Test (DUTs) and its interconnecting IOT interface. SUT for O-Cloud IOT refers to the O-Cloud platform, peer devices, and interfaces provided by O-Cloud, as illustrated in Figure 5.1-1 of O-RAN WG1 O-RAN Architecture Description, Clause 5.1[1] and Architecture Diagram in Figure 4.2-1 of O-RAN WG6 AAL GAnP, Clause 4.2 [5]. O-Cloud provides following APIs and Interfaces: - -- O2ims interface as described in O-RAN.WG6.TS.O2IMS-INTERFACE [8]. O2dms interface as described in O- - -RAN.WG6.O2DMS-INTERFACE-ETSI-NFV-PROFILE [9] for NF Deployments. - -- O2dms interface as described in O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE [10] for NF Deployments. -- O-Cloud Notification API, as described in O-RAN.WG6.O-Cloud Notification API.[1]. -- AAL interface, as described in O-RAN.WG6.AAL-Common-API [4]. - -Test scenarios encompass O-Cloud Notification API IOT, AAL interface IOT and O2 interface IOT as shown in Table 4.1-1, which summarizes the scope of O-Cloud IOT, and corresponding SUTs and DUTs for different test cases which can include Security, Synchronization, Error Handling, Rest Resource verification etc over the interfaces mentioned in the table below. - -**Table 4.1-1: O-Cloud IOT and corresponding Interfaces/APIs, DUTs and SUTs** - -| Test | Interface/API | DUTs | | SUT | -|-----------------------|-----------------------------------|------------------------------|---------------------------------|---------------------------------------------------------------------------------| -| | | Device1 | Device2 | Device1, Device2 and interconnecting IOT Interface | -| Notification APIs IOT | Notification APIs | O-Cloud | O-CU/O-DU | O-Cloud, O-CU/O-DU, Notification APIs | -| AAL Interface IOT | AAL Interface (AALI-C-App/AALI-P) | AAL implementation (O-Cloud) | AAL Application (O-CU/O-DU/...) | AAL implementation(O-Cloud), AAL Application, AAL Interface (AALI-C-App/AALI-P) | -| | AAL Interface (AALI-M) | O-Cloud (IMS) | AAL HAM | O-Cloud (IMS), AAL HAM, AAL Interface (AALI-M) | -| O2 Interface IOT | O2IMS Interface | O-Cloud (IMS) | SMO | O-Cloud, SMO, O2IMS | -| | O2DMS Interface | O-Cloud (DMS) | SMO | O-Cloud, SMO, O2DMS | - -The test configurations will involve defining the device pair and interface/API as part of the test scenario. The following figures show the high level SUT configurations for those IOT respectively. - -![SUT configuration for Notification APIs IOT diagram showing O-Cloud (DUT) and Application(O-CU/O-DU) (DUT) connected via Notification APIs and IOT.](e1a0d046fbe7f28f5e93a47091851747_img.jpg) - -``` - -graph LR - subgraph SUT - DUT1[O-Cloud (DUT)] -- "Notification APIs" --> DUT2["Application(O-CU/O-DU) (DUT)"] - DUT1 <--> |"IOT"| DUT2 - end - -``` - -SUT configuration for Notification APIs IOT diagram showing O-Cloud (DUT) and Application(O-CU/O-DU) (DUT) connected via Notification APIs and IOT. - -**Figure 4.1-1: SUT configuration for Notification APIs IOT** - -![Figure 4.1-2: SUT configuration for AAL interface IOT (AALI-C-Mgmt Interface). The diagram shows a System Under Test (SUT) containing an IMS (DUT) and an AAL HAM (DUT) connected via an AALI-M interface. A bidirectional IOT (Interconnect) is shown between the two components, and the entire setup is labeled O-Cloud.](562f471e8153729557e6a4ee6343c32c_img.jpg) - -The diagram illustrates the SUT configuration for the AAL interface IOT (AALI-C-Mgmt Interface). It features a dashed box labeled 'SUT' containing two yellow rectangular blocks: 'IMS (DUT)' on the left and 'AAL HAM (DUT)' on the right. These two blocks are connected by a horizontal line labeled 'AALI-M'. Below this connection, a large double-headed arrow labeled 'IOT' spans between the two blocks. At the bottom of the dashed box, the text 'O-Cloud' is present. - -Figure 4.1-2: SUT configuration for AAL interface IOT (AALI-C-Mgmt Interface). The diagram shows a System Under Test (SUT) containing an IMS (DUT) and an AAL HAM (DUT) connected via an AALI-M interface. A bidirectional IOT (Interconnect) is shown between the two components, and the entire setup is labeled O-Cloud. - -Figure 4.1-2: SUT configuration for AAL interface IOT (AALI-C-Mgmt Interface) - -![Figure 4.1-3: SUT configurations for AALI IOT(AALI-C-App/AALI-P). The diagram shows a System Under Test (SUT) containing an AAL impl. (DUT) and an AAL application (O-CU/O-DU/RIC/...) (DUT) connected via an AALI-C-App/AALI-P interface. A bidirectional IOT (Interconnect) is shown between the two components, and the entire setup is labeled O-Cloud.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) - -The diagram illustrates the SUT configurations for the AALI IOT (AALI-C-App/AALI-P). It features a dashed box labeled 'SUT' containing two yellow rectangular blocks: 'AAL impl. (DUT)' on the left and 'AAL application (O-CU/O-DU/RIC/...) (DUT)' on the right. These two blocks are connected by a horizontal line labeled 'AALI-C-App/AALI-P'. Below this connection, a large double-headed arrow labeled 'IOT' spans between the two blocks. At the bottom of the dashed box, the text 'O-Cloud' is present. - -Figure 4.1-3: SUT configurations for AALI IOT(AALI-C-App/AALI-P). The diagram shows a System Under Test (SUT) containing an AAL impl. (DUT) and an AAL application (O-CU/O-DU/RIC/...) (DUT) connected via an AALI-C-App/AALI-P interface. A bidirectional IOT (Interconnect) is shown between the two components, and the entire setup is labeled O-Cloud. - -Figure 4.1-3: SUT configurations for AALI IOT(AALI-C-App/AALI-P) - -![Figure 4.1-4: SUT configurations for O2 IMS IOT. The diagram shows a System Under Test (SUT) containing an O-Cloud (DUT) and an SMO (DUT) connected via an O2 IMS interface. A bidirectional IOT (Interconnect) is shown between the two components.](dbe553cf16dd14073b89a8263a428664_img.jpg) - -The diagram illustrates the SUT configurations for the O2 IMS IOT. It features a solid box labeled 'SUT' containing two yellow rectangular blocks: 'O-Cloud (DUT)' on the left and 'SMO (DUT)' on the right. These two blocks are connected by a horizontal line labeled 'O2 IMS'. Below this connection, a large double-headed arrow labeled 'IOT' spans between the two blocks. - -Figure 4.1-4: SUT configurations for O2 IMS IOT. The diagram shows a System Under Test (SUT) containing an O-Cloud (DUT) and an SMO (DUT) connected via an O2 IMS interface. A bidirectional IOT (Interconnect) is shown between the two components. - -Figure 4.1-4: SUT configurations for O2 IMS IOT - -![Diagram of SUT configurations for O2 DMS IOT. The diagram shows a System Under Test (SUT) box containing two yellow boxes: 'O-Cloud (DUT)' on the left and 'SMO (DUT)' on the right. A single-headed arrow labeled 'O2 DMS' points from the O-Cloud (DUT) to the SMO (DUT). Below this, a double-headed arrow labeled 'IOT' spans between the two DUTs, indicating bidirectional communication.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) - -Diagram of SUT configurations for O2 DMS IOT. The diagram shows a System Under Test (SUT) box containing two yellow boxes: 'O-Cloud (DUT)' on the left and 'SMO (DUT)' on the right. A single-headed arrow labeled 'O2 DMS' points from the O-Cloud (DUT) to the SMO (DUT). Below this, a double-headed arrow labeled 'IOT' spans between the two DUTs, indicating bidirectional communication. - -**Figure 4.1-5: SUT configurations for O2 DMS IOT** - -The test configurations for each specific test scenario will be detailed in their corresponding test clauses. - -## 4.2 Test method - -### 4.2.1 Objective - -O-Cloud IOT test focus on verifying the functional correctness between device peers. Performance test and security test are not in the scope. - -To validate the functionality of production grade DUTs, it is important that the DUTs are not negatively impacted with the utilization of internal functions, so the Device in production environment should not be used for test. - -The DUTs are used as black boxes for positive testing, negative testing, abnormal testing, etc. - -### 4.2.2 Testing Tools and set-up - -Interoperability tests are performed with a set of testing tools which are used to both apply active stimulus and as well as monitoring and measurements of the DUTs. Non-DUT devices or corresponding emulation tools can be used as active stimulus during the test. Passive monitoring and measurement tools can be used to watch the status of DUTs, collect the information exchanges, and capture the logs during the test. - -There is no constrain on the number of DUTs, but there shall be at least one for each DUT. DUTs shall be connected by corresponding interface before the test. - -For each test is differ from others, the suggested tools and the set-up are be detailed in the corresponding configuration section of each test. - -### 4.2.3 Testing procedure - -In adherence to the specifications, the System Under Test (SUT) and the test tool are meticulously configured and connected to the device, strictly following the predefined conditions for each test case. - -The test steps outlined in the test case are executed sequentially. - -The tester is responsible for diligently documenting crucial test information during and after the testing process, enabling - -detailed comparisons and analyses against the expected outcomes. - -It is crucial to note that each test case remains independent of one another. - -### 4.2.4 Statistics and analysis of key indicators - -The test execution adheres to the predefined conditions and procedures specified in the test case. - -During the testing process, the tester may capture and record test result, including success or failure, along with corresponding metric data, such as throughput, latency, and device volume. - -The expected test results serve as the benchmark for evaluating the test success. If the actual test results align with the expected outcomes, the test is considered successful. - -# 5 Notification API IOT - -## 5.1 General - -The main objective is to test the interoperability of different vendors' O-CU/O-DU with O-Cloud using notification-related APIs. This includes both push and pull modes for event notifications. - -As stated in Section 4.1, the SUT (System Under Test) for the Notification IOT test includes components such as O-Cloud and O-CU/O-DU/SMO. - -Each IOT test case offers a test purpose, test entrance criteria, initialization conditions, test procedure, and expected results. - -The main test scenarios covered are as follows: - -- 1) Functional test of O-Cloud and O-CU/O-DU using notification subscription, query, deletion and event notification API. -- 2) Functional test of O-Cloud and O-CU/O-DU using notification pull API. - -## 5.2 Test Configuration - -### 5.2.1 System Under Test requirements - -As shown in 5.2-1, the System Under Test (SUT) for the O-Cloud Notification IOT test consists of individual O-CU or O-DU components, along with the O-Cloud, which provides the notification framework. The notification framework includes an API producer; O-CU/O-DU act as consumers. O-Cloud, serving as an event generator, provides APIs to consumers for utilizing these events. These APIs can be used for subscribing to events, unsubscribing, querying subscriptions, and communicating with consumers using pull/push modes. - -At least one O-CU/O-DU and one O-Cloud is required for this test. O-CU/O-DU and O-Cloud are connected through network, and O-CU/O-DU is configured with the endpoint of notification API for the communication. - -Additionally, O-Cloud may need to support traffic mirroring for Protocol Analyzer to capture the requests and responses for analysing. - -![Figure 5.2-1: Configuration of O-Cloud Notification API IOT. The diagram shows an O-Cloud system containing an API Producer, a Notification Framework Implementation, and a Notification Framework. The API Producer and Notification Framework Implementation are connected by a double-headed arrow. The Notification Framework Implementation is connected to a stack of green boxes labeled 'Resource'. The Notification Framework is connected to the API Producer and the Notification Framework Implementation. The O-Cloud system is connected to a stack of grey boxes labeled 'O-CU/O-DU'. The O-CU/O-DU sends 'Queries/Subscribes' to the API Producer and receives 'Notification Push/Pull' from the Notification Framework. A 'Protocol Analyzer' is shown outside the O-Cloud, connected to the O-CU/O-DU by a dashed double-headed arrow.](042733dc5e8e7f5f30b60adba3266cde_img.jpg) - -Figure 5.2-1: Configuration of O-Cloud Notification API IOT. The diagram shows an O-Cloud system containing an API Producer, a Notification Framework Implementation, and a Notification Framework. The API Producer and Notification Framework Implementation are connected by a double-headed arrow. The Notification Framework Implementation is connected to a stack of green boxes labeled 'Resource'. The Notification Framework is connected to the API Producer and the Notification Framework Implementation. The O-Cloud system is connected to a stack of grey boxes labeled 'O-CU/O-DU'. The O-CU/O-DU sends 'Queries/Subscribes' to the API Producer and receives 'Notification Push/Pull' from the Notification Framework. A 'Protocol Analyzer' is shown outside the O-Cloud, connected to the O-CU/O-DU by a dashed double-headed arrow. - -**Figure 5.2-1: Configuration of O-Cloud Notification API IOT** - -### 5.2.2 Test Tools and Simulators capabilities - -A summary of the recommended testing tools for functional testing is shown as following: - -Protocol Analyzer is required for recording and validating Notification API functionary message sequences and contents and issuing of verdicts related to the procedures in the test cases and thereby enabling determination of the DUTs level of interoperability. - -## 5.3 Test Cases - -### 5.3.1 Push mode event notification - -#### 5.3.1.1 Test Purpose - -The purpose of this test case is to confirm that O-CU/O-DU, irrespective of the vendor, can manage the subscription resource and receive event notifications from O-Cloud. - -This test is conditional mandatory; for push mode, this case applies. - -#### 5.3.1.2 Test Entrance Criteria - -- 1) DUTs: O-CU/O-DU and O-Cloud. -- 2) CU/O-DU supports push mode Event Notification. -- 3) O-Cloud supports push mode Event Notification. - -#### 5.3.1.3 Initial conditions - -- 1) Protocol Analyzer has started. -- 2) Configure the O-Cloud or the network between the O-CU/O-DU and O-Cloud so that Protocol Analyzer can capture the messages between DUTs, as needed. -- 3) Activate the Protocol Analyzer to capture and decode Notification API message flows between the DUTs. - -#### 5.3.1.4 Procedure - -Step 1. Initiate a subscription procedure of the event notifications from O-CU/O-DU. - -Step 2. Initiate a query procedure from O-CU/O-DU, to get the list of subscription resources, check the output. - -Step 3. Initiate a query procedure from O-CU/O-DU, to get a specific subscription resource, check the output. - -Step 4. Trigger a subscribed event. - -Step 5. Initiate a delete procedure from O-CU/O-DU, to delete a specific subscription resource, check the output. - -Step 6. Check the message flow recorded by Protocol Analyzer for interoperability verification. - -Example of how those procedures can be performed (or triggered) are listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUTs: - -- a. O&M command in O-CU/O-DU to enable the subscription, query and deletion, for Step 1, 2, 3, 5, or to trig an event for Step 4. -- b. Reboot/restart O-CU/O-DU if O-CU/O-DU subscribes the notification automatically, for Step 1. -- c. Change the Synchronization status of the compute node if O-CU/O-DU subscribes the Synchronization Event, for Step 4. - -#### 5.3.1.5 Expected Results - -Successful completion of the test steps with interoperable communication between O-CU/O-DU and O-Cloud with the output as expected. - -Examine the message flow specified in O-RAN.O-Cloud Notification API [3] Section 4 and 5: - -In Step 1, a POST request from O-CU/O-DU to O-Cloud and a response from O-Cloud to O-CU/O-DU shall be present and be followed with a sanity check of the notification endpoint if communication to the notification endpoint is successful. - -In Step 2, 3 and 5, a Get request and a response shall be present. - -In Step 4, a notification of the event to O-CU/O-DU from O-Cloud shall be present. - -### 5.3.2 Pull mode event notification - -#### 5.3.2.1 Test Purpose - -The purpose of this test case is to verify O-CU/O-DU from a vendor different from O-Cloud can pull the event from Notification API Producer as specified in O-RAN.WG6.O-Cloud Notification API [3] clause 6. - -This test is conditional mandatory; for pull mode, this case applies. - -#### 5.3.2.2 Test Entrance Criteria - -- 1) DUTs: O-CU/O-DU and O-Cloud. -- 2) CU/O-DU has the capability to initiate an Event query, and the O-Cloud supports to response to the query requests. -- 3) O-Cloud supports pull mode Event Notification. - -#### 5.3.2.3 Initial conditions - -- 1) Protocol Analyzer has started. -- 2) Configure the O-Cloud or the network between the O-CU/O-DU and O-Cloud so that the Protocol Analyzer can capture the messages between DUTs. -- 3) Activate the Protocol Analyzer to capture and decode Notification API message flows between the DUTs. - -#### 5.3.2.4 Procedure - -Step 1. Initiate an event pull procedure from O-CU/O-DU. - -Step 2. Check the message flow recorded by Protocol Analyzer. - -Example of how those procedures can be performed (or triggered) are listed below. The exact method to perform (or trigger) this procedure is out of scope of this specification and is left up to the implementation of the DUTs: - -- a. O&M command in O-CU/O-DU to initiate the pulling. -- b. O-CU/O-DU pulls events periodically, without human intervention. - -#### 5.3.2.5 Expected Results - -The procedures are successfully completed during the test. - -Examine the message flow specified in O-RAN.WG6.O-Cloud Notification API [3] clause 6: a GET request from O-CU/O-DU to O-Cloud and a response from O-Cloud to O-CU/O-DU shall be present. - -# 6 AAL Interface IOT - -## 6.1 General - -NOTE: The interoperability tests for the AAL interface have not been specified in this present document version. Future versions of the present document are expected to specify these interoperability tests. - -## 6.2 Test Configuration - -### 6.2.1 System Under Test requirements - -### 6.2.2 Test Tools and Simulators capabilities - -## 6.3 Test Cases - -# 7 O2 Interface IOT - -## 7.1 General - -NOTE: The interoperability tests for the O2 interface have not been specified in this present document version. Future versions of the present document are expected to specify these interoperability tests. - -## 7.2 Test Configuration - -### 7.2.1 System Under Test requirements - -### 7.2.2 Test Tools and Simulators capabilities - -## 7.3 O2 IMS Test - -### 7.3.1 General - -The main objective of these O2IMS IOT tests is to validate the interoperability of IMS and FOCOM(SMO) over the O2 interface involving the use cases in ORAN WG6.ORCH-USE-CASES, clause 3 [12]. This can include orchestration use cases which have completed the Stage 3 specifications for O2IMS in ORAN WG6.TS.O2IMS-INTERFACE [9]. Some examples include fault use cases such as alarm subscription, notification or performance use cases such as performance management job creation in compliance with ORAN WG6.TS.O2IMS-INTERFACE [9] and O-Cloud Interface Conformance Test Specification ORAN WG6.TS.O-CLOUD-INTF-CONF [13]. - -### 7.3.2 Test Configurations - -#### 7.3.2.1 System Under Test (SUT) Requirements - -![Diagram of the O2 IMS IOT System Under Test (SUT). It shows two main components: SMO (System Management and Orchestration) and O-Cloud. SMO contains a FOCOM (Fault and Configuration Management) block. O-Cloud contains an IMS (Information Management System) block and a Fault Simulator block. A solid line labeled 'O2 IMS' connects the FOCOM block in SMO to the IMS block in O-Cloud. A dashed line connects the IMS block to the Fault Simulator block.](70de8885bd7de15723aaad5eb5c5febf_img.jpg) - -``` - -graph LR - subgraph SMO - FOCOM[FOCOM] - end - subgraph O-Cloud - IMS[IMS] - FS[Fault Simulator] - IMS -.-> FS - end - FOCOM ---|O2 IMS| IMS - -``` - -Diagram of the O2 IMS IOT System Under Test (SUT). It shows two main components: SMO (System Management and Orchestration) and O-Cloud. SMO contains a FOCOM (Fault and Configuration Management) block. O-Cloud contains an IMS (Information Management System) block and a Fault Simulator block. A solid line labeled 'O2 IMS' connects the FOCOM block in SMO to the IMS block in O-Cloud. A dashed line connects the IMS block to the Fault Simulator block. - -Figure 7.3.2.1-1 O2 IMS IOT SUT - -As shown in Figure 7.3.2.1-1, the system under test for the O-Cloud IMS IOT consist of FOCOM and IMS interconnected via O2ims interface which supports the O2ims API defined in [9]. The testing environment should include one FOCOM and one IMS to test interoperability from the same or different vendors. - -#### 7.3.2.2 Test Tools and Simulators Capabilities - -The following tools and simulator capabilities are recommended to effectively validate O2ims test cases - -- Fault injection simulator to simulate hardware and software failures in O-Cloud to trigger certain alarm conditions - -## 7.4 O2 DMS Test - -### 7.4.1 General - -### 7.4.2 O2 DMS ETSI NFV Profile Test - -#### 7.4.2.1 Test configuration - -#### 7.4.2.2 Test case 1 - -### 7.4.3 O2 DMS Kubernetes Profile Test - -#### 7.4.3.1 Test configuration - -#### 7.4.3.2 Test case 1 - -# Annex A (normative): Checklist for Cases applies to O-Cloud technologies - -Here give lists of cases applied to each O-Cloud technology. - -## A.1 O-Cloud technologies - -This specification covers following O-Cloud technologies: - -- VMs only -- Containers only -- Containers in VMs - -## A.2 Cloud Technology Applicability of test cases - -Cases marked with Y apply to the corresponding cloud technologies should be executed. - -**Table 0-2: O-Cloud Technology Applicability of Test Cases** - -| Test | Case Title | VMs only | Containers only | Containers in VMs | -|-------------------------------|------------------------|----------|-----------------|-------------------| -| O-Cloud Notification API Test | Push mode notification | Y | Y | Y | -| | Pull mode notification | Y | Y | Y | - -## A.3 Case Traceability - -**Table 0-3: Case Traceability** - -| Test | Test case | Reference | Requirement | -|-------------------------------|------------------------|-----------------------------------------------|---------------------------------------------------| -| O-Cloud Notification API Test | Push mode notification | [3] O-RAN.WG6.O-Cloud Notification API-v03.00 | 4.1.2.1
4.1.2.2
4.1.3.1
4.1.3.2
5.1.1 | -| | Pull mode notification | [3] O-RAN.WG6.O-Cloud Notification API-v03.00 | 6.1.1 | - -# Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2023.07.10 | 00.00.01 | Create initial version of O-Cloud IOT spec, with skeleton. | -| 2023.09.24 | 00.00.02 | Resolve comment, updated for WG6 review. | -| 2023.11.2 | 00.00.03 | Implemented CRs LNV-001 and LNV-002, baseline for review. | -| 2023.11.14 | 00.00.04 | Resolve comments, update Notification API test cases descriptions by merging cases into pull mode notification and push mode notification, and annex A | -| 2023.11.17 | 00.00.05 | Resolve comments, Baseline for WG voting 00.00.05 | -| 2023.11.17 | 01.00 | Final Version submitted to TSC | -| 2024.11.24 | 01.01 | Updates for the introduction, testing methodology, references and diagrams to focus on WG6 O2 specifications and the interfaces specified by WG6. | -| 2024.11.26 | 01.02 | Editorial Changes | -| 2024.12.03 | 01.03 | Editorial Changes | -| 2024.12.09 | 02.00 | Final Version Submitted to TSC | -| 2025.03.17 | 02.00.01 | DOCOMO provided Future Work Items #24, #25, #26 for IOT spec in Nov train 2024.
This version addresses item #24 and #25.
November 2024 Bugs & Future Work Items - Cloudification and Orchestration Workgroup
- Confluence
- 1 st change re-phrase Introduction section to include [9],[10],[11] and remove [1]. By this change the sentence refers “interface specs” only.
- 2 nd change replace [8] as “Void” because this CR delete sentence which refers [8]. (And this sentence only refers [8])
- 2 nd change add [9] for O2ims interfaced reference
- 2 nd change add [10],[11] for O2dms interface reference
- 3 rd change divide O2 interface into O2ims and O2dms because O2 interface is collection of O2ims interface and O2dms interface
- 3 rd change delete “O-RAN.WG6.AAL-GAnP” because it is not interface specification | -| 2025.03.20 | 02.00.02 | Editorial changes and Change History. | -| 2025.03.27 | 02.01 | Final Version submitted to TSC | -| 2025.07.09 | 02.01.01 | Included the O2 IMS IOT SUT requirements and test tool configurations in the section 7.3 of the version 02.01.01 for voting in WG6 and Update the normative references section to include WG6 Orchestration use spec[12] and WG6 Conformance IOT spec[13] | -| 2025.07.17 | 02.01.02 | Editorial changes | -| 2025.07.18 | 02.02 | Final Version submitted to TSC | -| 2025.11.19 | 02.02.01 | Implemented CR DCM-0002. | -| 2025.11.25 | 02.02.02 | Editorial updates based on review comments. | -| 2025.11.28 | 02.03 | Final Version submitted to TSC. | \ No newline at end of file diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/042733dc5e8e7f5f30b60adba3266cde_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/042733dc5e8e7f5f30b60adba3266cde_img.jpg deleted file mode 100644 index 8485c02993b01f84e8590e80e9391527cfd4a6d6..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/042733dc5e8e7f5f30b60adba3266cde_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9a093c9851800562a5ba20578934d2fa3d250b4b0955c1be7d2f5280a744ffd2 -size 26646 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index a63793a81465ede483030ac7c6b3b7d7cf00d8b3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7ca6288e77a15b07446f8f90cd18169fd9572f61d923ea262c7786cf137e2e86 -size 4550 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 1b6bbe2dc6233424565f595d3557f052e4ae8f6d..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a3a07596cb69a17a11b43d0a55d14b61b4b4227b6a83b36083af80e69ada2d0c -size 4513 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 5e1cf78899d51be3f2059361bf85cd3607741123..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e7cadbc3198632db753aaf22368a828b4fe6abb124c2c58c45dede71c14370d9 -size 4562 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 1b6bbe2dc6233424565f595d3557f052e4ae8f6d..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a3a07596cb69a17a11b43d0a55d14b61b4b4227b6a83b36083af80e69ada2d0c -size 4513 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/562f471e8153729557e6a4ee6343c32c_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/562f471e8153729557e6a4ee6343c32c_img.jpg deleted file mode 100644 index 7b64aaaf565e89bc7e9be98feb015a7c74c0dc59..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/562f471e8153729557e6a4ee6343c32c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4fe75b19951bf26eca60047ff56dee7cc4c324268e65d9a4101a1fe85a31fb37 -size 23353 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/70de8885bd7de15723aaad5eb5c5febf_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/70de8885bd7de15723aaad5eb5c5febf_img.jpg deleted file mode 100644 index a87b3fe8d93a59a54d051b58fd824e2f2a1aca6e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/70de8885bd7de15723aaad5eb5c5febf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b65a24882d5fc99bcb74fbe99c0e832a3d8d7fb11a43ad79d3f41ac519fee4ce -size 25166 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index a96faa30848266de8715faf12c131fe4567676c3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bcb9bb0924f7902608942f13c72e076ea1c6143ef0a5534ef3b99ca1c572e056 -size 4466 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/7a0db9703b68b3d06cdaeefc084c0006_img.jpg deleted file mode 100644 index 398408819a92cea20bd31237c5590dcfbd4d1a23..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/7a0db9703b68b3d06cdaeefc084c0006_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:50c7ed109e39c5d3818ac546ad03286783d2582d8a4ac6e6c077f8dee93e9175 -size 28322 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 1b6bbe2dc6233424565f595d3557f052e4ae8f6d..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a3a07596cb69a17a11b43d0a55d14b61b4b4227b6a83b36083af80e69ada2d0c -size 4513 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index a96faa30848266de8715faf12c131fe4567676c3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/854df8ad60507803253274673f9062cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bcb9bb0924f7902608942f13c72e076ea1c6143ef0a5534ef3b99ca1c572e056 -size 4466 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index a96faa30848266de8715faf12c131fe4567676c3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bcb9bb0924f7902608942f13c72e076ea1c6143ef0a5534ef3b99ca1c572e056 -size 4466 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index a96faa30848266de8715faf12c131fe4567676c3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bcb9bb0924f7902608942f13c72e076ea1c6143ef0a5534ef3b99ca1c572e056 -size 4466 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 1b6bbe2dc6233424565f595d3557f052e4ae8f6d..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a3a07596cb69a17a11b43d0a55d14b61b4b4227b6a83b36083af80e69ada2d0c -size 4513 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index a96faa30848266de8715faf12c131fe4567676c3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bcb9bb0924f7902608942f13c72e076ea1c6143ef0a5534ef3b99ca1c572e056 -size 4466 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg deleted file mode 100644 index 40e9f73f16e173ce565b36f6b9bbb11cd2e2a2f2..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:48d8a597e0be3cb5e8e7e305725f4a80cbe7b31aa35eab53819b328ca0e38896 -size 17960 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 1b6bbe2dc6233424565f595d3557f052e4ae8f6d..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a3a07596cb69a17a11b43d0a55d14b61b4b4227b6a83b36083af80e69ada2d0c -size 4513 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/dbe553cf16dd14073b89a8263a428664_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/dbe553cf16dd14073b89a8263a428664_img.jpg deleted file mode 100644 index fe147fde3ba40977185e5e1ac51bde604262f5c8..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/dbe553cf16dd14073b89a8263a428664_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d9933047b6a2cde4b952846f2775ec6dfc8c7c5f5cc0882c96a24826176db872 -size 18029 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/e1a0d046fbe7f28f5e93a47091851747_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/e1a0d046fbe7f28f5e93a47091851747_img.jpg deleted file mode 100644 index 8c427043c814d0650fcc204417e655fd69133565..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/e1a0d046fbe7f28f5e93a47091851747_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6d7d2b7e3cf7a15ef31ee11af6d18fa4582fc85c716fedecc3e764f70bd36b2d -size 19985 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 7b199fa112e401abed899e23ce4ec108fbfdca37..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:856067084bd18e7ed956a37b626638ecc86d8ffe4d5a155cbf160f3c13371051 -size 4573 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index a96faa30848266de8715faf12c131fe4567676c3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bcb9bb0924f7902608942f13c72e076ea1c6143ef0a5534ef3b99ca1c572e056 -size 4466 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index df6f3e9410a67ddd70e6a47977298b6342f0a5b7..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ab10c4694b2f6927d8f63f09fd5f33dd83f967aa939676a6d7510cbc34b718cf -size 4514 diff --git a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index b5ae4ba8a78f7be4ea4b67809204d89fffadbc35..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O-CLOUD-IOT-R005-v02.03/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0e353b1c2e90ef9a53ac3e6362a34721dedc9036283424181bc7cef459a82c6a -size 4554 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/doc.md b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/doc.md deleted file mode 100644 index 0b706aae8566c35fc7687bd9e5e014e5c8b8a3d7..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/doc.md +++ /dev/null @@ -1,1007 +0,0 @@ - - -## **O-RAN Working Group 6** - -# **O2dms Interface Specification: Kubernetes Native API Profile for Containerized NFs** --- - -# Contents - -| | | -|-----------------------------------------------------------------|----| -| Contents..... | 2 | -| 1 Introduction ..... | 3 | -| 1.1 Scope ..... | 3 | -| 1.2 References..... | 3 | -| 1.3 Definitions and Abbreviations ..... | 3 | -| 1.3.1 Definitions..... | 3 | -| 1.3.2 Abbreviations ..... | 3 | -| 2 O2dms Service Overview..... | 5 | -| 2.1 Overview ..... | 5 | -| 2.2 Supported Use Cases ..... | 5 | -| 3 O2dms Service Definitions ..... | 6 | -| 3.1 General..... | 6 | -| 3.1.1 The O2dms Services Supported ..... | 6 | -| 3.1.2 Instantiate NF Deployment ..... | 6 | -| 3.1.3 Terminate NF Deployment..... | 8 | -| 3.1.4 Heal NF Deployment ..... | 10 | -| 3.1.5 Software Upgrade of NF Deployment..... | 12 | -| 3.1.6 Scale NF Deployment ..... | 13 | -| 4 O2dms Service Definitions for Kubernetes..... | 16 | -| 4.1 General..... | 16 | -| 4.2 Referenced Cloud-Native APIs and Data Model Solutions ..... | 16 | -| 4.2.1 Kubernetes API overview ..... | 16 | -| 4.3 Referenced K8s resource objects ..... | 17 | -| 4.3.1 Kubernetes Native Namespace Scoped Resource Objects ..... | 18 | -| 4.3.2 Kubernetes Native Cluster Scoped Resource Objects ..... | 33 | -| Annex (informative): Change History ..... | 34 | - -# 1 Introduction - -## 1.1 Scope - -This Technical Specification has been produced by the O-RAN.org. - -The contents of the present document are subject to continuing work within O-RAN WG6 and may change following formal O-RAN approval. Should the O-RAN.org modify the contents of the present document, it will be re-released by O-RAN Alliance with an identifying change of release date and an increase in version number as follows: - -Release x.y.z - -where: - -- x the first digit is incremented for all changes of substance, i.e., technical enhancements, corrections, updates, etc. (the initial approved document will have x=01). -- y the second digit is incremented when editorial only changes have been incorporated in the document. -- z the third digit included only in working versions of the document indicating incremental changes during the editing process. - -This document defines O-RAN O-Cloud DMS interface functions and protocols for the O-RAN O2 interface. The document studies the functions conveyed over the interface, including management functions, procedures, operations, and corresponding solutions, and identifies existing standards and industry work that can serve as a basis for O-RAN work. - -## 1.2 References - -The following documents contain provisions which, through reference in this text, constitute provisions of this specification (see also ). - -- [1] 3GPP TR 21.905, Vocabulary for 3GPP Specifications -- [2] O-RAN WG6, Orchestration Use Case and Requirements for O-RAN Virtualized RAN -- [3] O-RAN WG6, Cloud Architecture and Deployment Scenarios for O-RAN Virtualized RAN -- [4] O-RAN WG6, O-RAN O2 General Aspects and Principles Specification -- [5] Kubernetes® API, online -- [6] Kubernetes® API Conventions, online - -NOTE: Kubernetes® and K8s® are registered trademarks of the Linux Foundation, in the United States and other countries. O-RAN is not affiliated with, endorsed, or sponsored by the Linux Foundation. - -## 1.3 Definitions and Abbreviations - -### 1.3.1 Definitions - -### 1.3.2 Abbreviations - -For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] 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 [1]. - -| | | -|-----|-----------------------------------| -| DMS | Deployment Management Services | -| API | Application Programming Interface | - -| | | -|------|--------------------------------------| -| HPA | HorizontalPodAutoscaler | -| RBAC | Role Based Access Control | -| SMO | Service Management and Orchestration | -| NFO | Network Function Orchestration | - -# 2 O2dms Service Overview - -## 2.1 Overview - -This document specifies NF Deployment lifecycle management services offered over the O2dms interface using the Kubernetes native APIs, objects, and data model. The relationship with O2ims services is also described whenever applicable (e.g., provisioning of Kubernetes labels in an O-Cloud Kubernetes cluster by SMO to enable matching the NF Deployment's requirements with the capabilities of the Kubernetes cluster). - -The O2dms Kubernetes profile exposes a set of capabilities of the Kubernetes native “API Server” function to the SMO and enables the reuse of Kubernetes native API procedures and data model (Kubernetes resource manifests). As depicted in Figure 2.1-1, the O2dms Kubernetes profile exposes one O2dms interface instance per one Kubernetes cluster to the SMO and the interface is terminated by the API Server component of Kubernetes native control plane. The address and access credentials required for communication with the Kubernetes API Server component are assumed to be available to the SMO. - -![Diagram showing the SMO connected to the API Server within a Kubernetes cluster via the O2dms interface.](ca5566458a134032dd860e88fdaa0d2b_img.jpg) - -``` - -graph TD - SMO[SMO] --- O2dms[O2dms] - subgraph K8s_cluster [Kubernetes ® cluster] - API_Server[API Server] - end - O2dms --- API_Server - -``` - -Diagram showing the SMO connected to the API Server within a Kubernetes cluster via the O2dms interface. - -Figure 2.1-1 - -## 2.2 Supported Use Cases - -The list of orchestration use-cases specified in [2] needs to be supported using O2dms capabilities for NF Deployment lifecycle management. This version of the O2dms Kubernetes profile supports the following use cases aligned with [2] based on Kubernetes native APIs and resource objects. - -- Instantiate NF Deployment on a Kubernetes cluster: This O2dms capability enables the SMO to instantiate an NF Deployment on a target Kubernetes cluster using the Kubernetes native resource objects (e.g., Deployments, StatefulSets, ConfigMaps, etc.). The set of Kubernetes native resource objects profiled in clause 4.3 of the present document may be used for NF Deployment. -- Terminate NF Deployment on a Kubernetes cluster: This O2dms capability enables the SMO to terminate an NF Deployment on a target Kubernetes cluster by deleting all the Kubernetes native resource objects belonging to that NF Deployment from the target Kubernetes cluster. -- Heal NF Deployment on a Kubernetes cluster: This O2dms capability enables the SMO to recover an NF Deployment from failures on a Kubernetes cluster. The SMO may trigger the NF Deployment recovery by creating, modifying, and/or deleting K8s native resource objects belonging to that NF Deployment. -- Software Upgrade of NF Deployment on a Kubernetes cluster: This O2dms capability enables the SMO to upgrade the software version of an NF Deployment running on a Kubernetes cluster. -- Scale NF Deployment on a Kubernetes cluster: This O2dms capability enables the SMO to elastically scale the NF Deployment's service capacity to the service demands. Additional Kubernetes resources may be allocated to or deallocated from an NF Deployment as part of this use case. - -# 3 O2dms Service Definitions - -## 3.1 General - -This section provides details of the O2dms interface capabilities for NF Deployment lifecycle management exposed to the SMO using the O2dms Kubernetes profile. The O2dms Kubernetes profile exposes a REST based interface to the SMO from the API Server function of Kubernetes native control plane. The protocol stack used by O2dms Kubernetes profile for secure communication between the SMO and the target Kubernetes cluster is depicted in Figure 3.1-1. This protocol stack enables a secure transfer of the Kubernetes native API resource manifests from the SMO to the target Kubernetes cluster. - -![Diagram showing the protocol stack for O2dms Kubernetes profile between SMO and O-Cloud. Both sides have identical stacks: K8S JSON/YAML Manifests, HTTPS, TCP, IP, L2, and L1.](573c8f9e728e343b6864e1070c14b8cf_img.jpg) - -| SMO | O-Cloud | -|-------------------------|-------------------------| -| K8S JSON/YAML Manifests | K8S JSON/YAML Manifests | -| HTTPS | HTTPS | -| TCP | TCP | -| IP | IP | -| L2 | L2 | -| L1 | L1 | - -Diagram showing the protocol stack for O2dms Kubernetes profile between SMO and O-Cloud. Both sides have identical stacks: K8S JSON/YAML Manifests, HTTPS, TCP, IP, L2, and L1. - -Figure 3.1-1: Illustration of the protocol stack used by O2dms Kubernetes profile - -### 3.1.1 The O2dms Services Supported - -In this specification, the Kubernetes native APIs provide all the required capabilities to the SMO for NF Deployment lifecycle management in a Kubernetes cluster. The Kubernetes native APIs are exposed by the API Server function of the Kubernetes native control plane and is the common denominator for the SMO to manage containerized workloads on Kubernetes based O-Clouds. - -The Kubernetes API Server exposes a REST based interface, offering CRUD (Create, Read, Update, Delete) operations using Kubernetes native resource manifests. Aligned with this REST interface, the ORAN WG6 use cases captured in [2] for lifecycle management of NF Deployments are realized by using the API Server’s supported operations (CRUD) and data model (Kubernetes native resource manifests). - -### 3.1.2 Instantiate NF Deployment - -The instantiate NF Deployment use case enables the SMO to start the execution of a NF Deployment on a Kubernetes cluster that meets the NF Deployment’s execution requirements. In the O2dms Kubernetes profile, the instantiate NF Deployment use case is realized by secured transfer of the Kubernetes native resource manifests of the Kubernetes native resource objects from the SMO to the API Server function in the target Kubernetes cluster. An NF Deployment is usually composed of different Kubernetes native resource objects (e.g., Deployments, ConfigMaps, etc.) and a secured transfer of all Kubernetes manifests is required for successful completion of the instantiate NF Deployment use case. - -Figure 3.1.2-1 exemplifies the instantiate NF Deployment use case flow as per O2dms Kubernetes profile aligned with the NF Deployment instantiation use case in [2]. - -![Sequence diagram for NF Deployment Instantiation showing interactions between SMO, NFO, K8s API Server, and K8s worker node.](a738993919a50143787084ee7ce6e2f2_img.jpg) - -The diagram illustrates the sequence of operations for NF Deployment Instantiation. It begins with a yellow box labeled 'PRECONDITIONS' listing: 'SMO is active and running normally', 'K8s cluster is active and running normally', and 'SMO and K8s API Server connectivity is established'. A horizontal line separates this from the main sequence. The sequence starts with a box 'Use case: Instantiate NF Deployment on K8s cluster'. Step 1 is 'Instantiate NF Deployment trigger' from SMO to NFO. A note indicates 'NFO gets the NF Deployment artifacts (e.g., ASD, Helm Charts) and generates parameterized K8s resource manifests'. A loop box titled '[Until all K8s resource objects are created on the K8s cluster]' contains steps 2, 3, and 4. Step 2 is '[O2dms] «HTTP POST» Create K8s resource object' from NFO to K8s API Server. Step 3 is 'Create K8s resource object' from K8s API Server to K8s worker node. Step 4 is '[O2dms] «HTTP 201» CREATED' from K8s API Server to NFO. A note indicates 'K8s API Server notifies the worker node(s) to start workload execution'. Another note indicates 'K8s worker fetches the container image(s) and starts its execution'. A note indicates 'NFO checks the status of NF Deployment instantiation via O2dms'. A horizontal line separates this from the end sequence. The sequence ends with a box 'End Instantiate NF Deployment on K8s Cluster'. - -``` -sequenceDiagram - participant SMO - participant NFO - participant K8s_API_Server as K8s API Server - participant K8s_worker_node as K8s worker node - - Note right of SMO: PRECONDITIONS: -SMO is active and running normally -K8s cluster is active and running normally -SMO and K8s API Server connectivity is established - - Note right of SMO: Use case: Instantiate NF Deployment on K8s cluster - - SMO->>NFO: 1 Instantiate NF Deployment trigger - Note left of NFO: NFO gets the NF Deployment artifacts -(e.g., ASD, Helm Charts) and generates -parameterized K8s resource manifests - - loop Until all K8s resource objects are created on the K8s cluster - NFO->>K8s_API_Server: 2 [O2dms] «HTTP POST» Create K8s resource object - K8s_API_Server->>K8s_worker_node: 3 Create K8s resource object - K8s_API_Server->>NFO: 4 [O2dms] «HTTP 201» CREATED - end - - Note right of K8s_API_Server: K8s API Server notifies the worker -node(s) to start workload execution - - Note right of K8s_worker_node: K8s worker fetches the -container image(s) and -starts its execution - - Note left of NFO: NFO checks the status of NF -Deployment instantiation via O2dms - - Note right of SMO: End Instantiate NF Deployment on K8s Cluster -``` - -Sequence diagram for NF Deployment Instantiation showing interactions between SMO, NFO, K8s API Server, and K8s worker node. - -Figure 3.1.2-1: NF Deployment Instantiation - -**Table 3.1.2-1: Instantiate NF Deployment Use Case** - -| Use Case Stage | Evolution/Specification | -|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Use Case | Instantiate NF Deployment on a selected Kubernetes cluster | -| Goal | The goal of this use case is to instantiate an NF Deployment on a Kubernetes cluster that has been selected by the SMO to host that NF Deployment | -| Actors and roles |
  • - NFO: The NFO initiates the NF Deployment instantiation process
  • - Kubernetes API Server: O2dms termination point in Kubernetes cluster
| -| Preconditions |
  • - NFO is active and running normally
  • - Kubernetes API server is accessible via O2dms interface
| -| Begins when | The SMO decides to instantiate an NF Deployment on a Kubernetes cluster | -| Step 1 (M) | A request to instantiate a new NF Deployment is received by the NFO from an authorised NFO service consumer (e.g., rApp) with an identifier for the NF Deployment. (NOTE 1, NOTE 2) | -| Step 2 (M) | The NFO sends the Kubernetes native resource manifests to the API Server function in the chosen Kubernetes cluster using O2dms interface by making an HTTP POST call(s) to the respective resource URL with the Kubernetes resource manifest as payload. | -| Step 3 (M) | The API Server function authenticates the request and validates the resource manifests and creates the respective resource objects in the Kubernetes cluster. (NOTE 3, NOTE 4) | -| Step 4 (M) | The API Server responds to the NFO by acknowledging the creation of the requested resource objects in the Kubernetes cluster. (NOTE 5) | -| Ends when | This use case ends when the NF Deployment is up and running in the chosen Kubernetes cluster. | -| NOTE 1: The NF Deployment identifier provided is used by the NFO to get related artifacts for that NF Deployment (e.g., ASD, Helm Charts).
NOTE 2: The NFO generates parameterized Kubernetes native resource manifests from the NF Deployment artifacts (e.g., ASD, Helm Charts).
NOTE 3: The creation of a Kubernetes resource object results in an internal notification to the worker nodes that the NF Deployment resources need to be instantiated.
NOTE 4: A worker node responsible for the workload execution fetches the container images from the image registry specified in the Kubernetes resource manifests files and starts its execution on that node.
NOTE 5: There may be a delay between the Success response from the API Server to the NFO and the actual execution of the containerized workload on the Kubernetes cluster due to several reasons including, for example, the time it takes to pull the container images from the registry, the allocation of the resources to the container and the initialization of the application inside the containers. The NFO may check the status of the NF Deployment instantiation via O2dms to validate successful instantiation of the NF Deployment. | | - -### 3.1.3 Terminate NF Deployment - -The terminate NF Deployment use case requires the SMO to stop the execution of a NF Deployment on a Kubernetes cluster and release all resources that are used by that NF Deployment. In the O2dms Kubernetes profile, the terminate NF Deployment use case is realized by deleting all Kubernetes native resource objects belonging to the NF Deployment from the Kubernetes cluster that is running the NF Deployment. Figure 3.1.3-1 exemplifies the terminate NF Deployment use case flow in O2dms Kubernetes profile aligned with the NF Deployment termination use case in [2]. - -![Sequence diagram for NF Deployment Termination. Lifelines: SMO (NFO), Kubernetes cluster (K8s API Server, K8s worker node). The process involves triggering termination, deleting resource objects via an O2dms loop, and finally checking the termination status.](562f471e8153729557e6a4ee6343c32c_img.jpg) - -**PRECONDITIONS:** - SMO is active and running normally - K8s cluster is active and running normally - SMO and K8s API Server connectivity is established - -**Use case: Terminate NF Deployment on K8s cluster** - -- 1** Terminate NF Deployment trigger (NFO to NFO) -- The NFO determines the K8s resources to be deleted for the NF Deployment -- loop** [Until all K8s resource objects are deleted on the K8s cluster] - - 2** [O2dms] «HTTP DELETE» Delete K8s resource object (NFO to K8s API Server) - - 3** Delete K8s resource objects (K8s API Server to K8s worker node) - - 4** [O2dms] «HTTP 200» OK (K8s API Server to NFO) -- K8s API Server notifies the worker node(s) to terminate the workload execution -- K8s worker stops the container process and releases resources -- SMO checks the status of NF Deployment termination via O2dms - -**End of Terminate NF Deployment on K8s Cluster** - -Sequence diagram for NF Deployment Termination. Lifelines: SMO (NFO), Kubernetes cluster (K8s API Server, K8s worker node). The process involves triggering termination, deleting resource objects via an O2dms loop, and finally checking the termination status. - -Figure 3.1.3-1: NF Deployment Termination - -**Table 3.1.3-1: Terminate NF Deployment Use Case** - -| Use Case Stage | Evolution/Specification | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Use Case | Terminate NF Deployment on a selected Kubernetes cluster | -| Goal | The goal of this use case is to terminate an NF Deployment on a Kubernetes cluster that is hosting it and release all resources used by that NF Deployment | -| Actors and roles |
  • - NFO: The NFO executes the NF Deployment termination process
  • - Kubernetes API Server: O2dms termination point in Kubernetes cluster
| -| Preconditions |
  • - NFO is active and running normally
  • - Kubernetes cluster is running normally
  • - Kubernetes API server is accessible via O2dms interface
| -| Begins when | The SMO decides to terminate an NF Deployment on a Kubernetes cluster | -| Step 1 (M) | A request to terminate an NF Deployment is received by the NFO with an identifier for that workload. (NOTE 1, NOTE 2) | -| Step 2 (M) | The NFO requests the deletion of all Kubernetes resource objects belonging to the NF Deployment from the API Server function in the target Kubernetes cluster by sending HTTP DELETE request(s) to the respective resource URL. | -| Step 3 (M) | The API Server function authenticates the request and deletes the requested resource objects from the Kubernetes cluster. (NOTE 3, NOTE 4) | -| Step 4 (M) | The API Server responds to the NFO by informing it about the resource objects that have been deleted from Kubernetes cluster. (NOTE 5) | -| Ends when | This use case ends when an NF Deployment running in a Kubernetes cluster is terminated, and all resources used by that NF Deployment are released. | - -NOTE 1: The SMO may use the provided NF Deployment instance identifier for determining the Kubernetes cluster running that NF Deployment instance. -NOTE 2: The NFO determines all the Kubernetes resources objects that collectively represent the NF Deployment in the target Kubernetes cluster. -NOTE 3: The deletion of a Kubernetes resource object results in an internal notification to the worker nodes to release any resources used by the terminated NF Deployment. -NOTE 4: The Kubernetes worker nodes automatically stop the execution of any workloads for which the Kubernetes native resource objects have been deleted from the Kubernetes cluster. -NOTE 5: There may be a delay between the Success response from the API Server to the SMO and the actual termination of NF Deployment and release of resources in the Kubernetes cluster. The NFO may check the status of the NF Deployment termination via O2dms to validate successful termination of the NF Deployment. - -### 3.1.4 Heal NF Deployment - -Recovery of an NF Deployment from failures is documented in [2] clause 3.6.2, which describes an NF Deployment level healing use case based on either auto-healing support in the O-Cloud platform or SMO triggered healing over O2dms interface. Based on these healing triggers, the use case describes corrective actions that can be taken for NF Deployment healing in the O-Cloud such as restarting, replacing and/or reallocating O-Cloud resources belonging to the NF Deployment. This section describes the NF Deployment level healing use case for healing NF Deployments on a K8s cluster using O2dms K8s profile. - -#### 3.1.4.1 Auto Healing of NF Deployment in a Kubernetes cluster - -Auto-healing of NF Deployment refers to the intrinsic capabilities of the O-Cloud platform to monitor the workloads and initiate corrective actions automatically when runtime errors/faults are detected by the O-Cloud platform. The Kubernetes platform provides auto-healing features based on continuous monitoring of the running containerized workloads (e.g., Pods) using liveness checks at the application layer. A workload designed for Kubernetes is expected to pass these liveness checks to be considered as healthy workload running in the K8s cluster. If the liveness checks fail for a workload, the Kubernetes control plane automatically replaces the failing workload with a new copy. - -When the restart and replacement mechanics of Kubernetes auto-healing process are not sufficient for the full recovery of the NF Deployment, the SMO may trigger NF Deployment healing using O2dms interface. - -#### 3.1.4.2 SMO triggered Healing of NF Deployment in a Kubernetes cluster - -Based on monitoring of the NF Deployment using O2 interface, the SMO may detect the need and decide to heal an NF Deployment using O2dms interface. This SMO triggered healing over O2dms may occur independently from any auto-healing features running in the O-Cloud platform for healing NF Deployment. In the O2dms K8s profile, the SMO triggered NF Deployment healing is realized by creating, modifying and/or deleting K8s native resource objects belonging to the NF Deployment experiencing failures. Figure 3.1.4-1 exemplifies the SMO triggered healing of NF Deployment using the O2dms K8s profile. - -![Sequence diagram showing SMO triggered NF Deployment Healing on a K8s cluster. Lifelines: SMO (NFO) and Kubernetes based O-Cloud (K8s API Server). The process involves identifying resources, then optionally creating, modifying, or deleting K8s resources via O2dms HTTP requests, followed by API server processing and final status checking.](d26959f4514c26ca19c3d6f00da85956_img.jpg) - -``` - -sequenceDiagram - participant SMO as SMO (NFO) - participant K8s as Kubernetes based O-Cloud (K8s API Server) - - Note right of SMO: Use case: SMO triggered NF Deployment Healing on a K8s® cluster - - SMO->>SMO: 1 NF Deployment healing trigger - Note left of SMO: NFO identifies the resources to be healed for the NF Deployment - - opt K8s resources to be created - loop Until all required K8s resources are created - SMO->>K8s: 2 [O2dms] «HTTP POST» Create K8s resource object - Note right of K8s: 3 Create K8s resource object - K8s-->>SMO: 4 [O2dms] «HTTP 201» CREATED - end - end - - opt K8s resources to be modified - loop Until all required K8s resources are updated - SMO->>K8s: 5 [O2dms] «HTTP PUT/PATCH» Update K8s resource object - Note right of K8s: 6 Update K8s resource object - K8s-->>SMO: 7 [O2dms] «HTTP 200» OK - end - end - - opt K8s resources to be deleted - loop Until all required K8s resource are deleted - SMO->>K8s: 8 [O2dms] «HTTP DELETE» Delete K8s resource object - Note right of K8s: 9 Delete K8s resource object - K8s-->>SMO: 10 [O2dms] «HTTP 200» OK - end - end - - Note right of K8s: K8s API Server notifies the worker nodes to process the updated resources and heal the NF deployment workload - - Note left of SMO: NFO checks the status of NF Deployment via O2dms - - Note right of SMO: End: SMO triggered NF Deployment Healing on a K8s® Cluster - -``` - -Sequence diagram showing SMO triggered NF Deployment Healing on a K8s cluster. Lifelines: SMO (NFO) and Kubernetes based O-Cloud (K8s API Server). The process involves identifying resources, then optionally creating, modifying, or deleting K8s resources via O2dms HTTP requests, followed by API server processing and final status checking. - -Figure 3.1.4-1 NF Deployment Healing - -**Table 3.1.4-1 Heal NF Deployment Use Case** - -| Use Case Stage | Evolution/Specification | -|-----------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Use Case | Healing of an NF Deployment on a Kubernetes cluster | -| Goal | The goal of this use case is to heal an NF Deployment by the SMO using O2dms K8s profile | -| Actors and roles |
  • - NFO: The NFO executes the NF Deployment healing process
  • - Kubernetes API Server: O2dms termination point in Kubernetes cluster
| -| Preconditions | The NF Deployment has been previously instantiated by the SMO | -| Begins when | The SMO decides to heal an NF Deployment on a Kubernetes cluster | -| Step 1 | The NFO receives a request to initiate NF Deployment healing e.g., from an rApp. (NOTE) | -| Step 2, 3, 4 | If the NFO decides to heal the NF Deployment by creating additional K8s resource objects, it shall send the new K8s resource manifests using HTTP POST request(s) to the K8s API server (2). The K8s API server will create the new resource objects (3) and informs the NFO about the resource object creation (4). | -| Step 5, 6, 7 | If the NFO decides to heal the NF Deployment by modifying its K8s resource objects, it shall send updated K8s resource manifests using HTTP PUT/PATCH request(s) to the K8s API server (5). The K8s API server will update the NF Deployment resource objects (6) and informs the NFO about the resource object updates (7). | -| Step 8, 9, 10 | If the NFO decides to heal the NF Deployment by deleting some of the K8s resource objects belong to the NF Deployment, it shall delete those K8s resource objects using HTTP DELETE request(s) to the K8s API server (8). The K8s API server will delete the requested resource objects (9) and informs the NFO about the resource object deletion (10). | -| Ends when | This use case ends when the NF Deployment running in a Kubernetes cluster is recovered from failures. | -| NOTE: The NFO determines the K8s resource objects belonging to the NF Deployment requiring updates (CRUD operations) for healing the NF Deployment. | | - -### 3.1.5 Software Upgrade of NF Deployment - -This section describes the use case for SMO managed software upgrade of an NF Deployment and its realization based on O2dms K8s API profile. - -#### 3.1.5.1 Build-and-Replace Software Upgrade - -This section illustrates a build-and-replace NF Deployment upgrade approach in which an NF Deployment using old software version is replaced by a new and independently deployed instance using newer software version. This approach utilizes a graceful or soft upgrade where the old NF Deployment is not removed from a K8s cluster until this can be done without disrupting existing traffic that the NF Deployment supports. - -Upon receiving a request to upgrade software of a particular NF Deployment, the SMO instantiates a new NF Deployment according to the procedure described in section 3.1.2 (Instantiate NF Deployment). The new instance is created independently and uses newer software version of the NF Deployment. If an exception occurs during the instantiation step that causes the new NF Deployment not to be created successfully, the operation is rolled back and further actions aborted i.e., the new NF Deployment instance is removed, and the old NF Deployment continues to provide service as before. - -After the new NF Deployment instantiation is successful, the SMO may trigger further actions e.g., O1 configuration of parts of the NF related to the NF Deployment. Once the new NF Deployment is up and running, the old NF Deployment is terminated according to the procedure described in section 3.1.3 (Terminate NF Deployment). - -### 3.1.6 Scale NF Deployment - -#### 3.1.6.1 Overview - -The Scale NF Deployment use case concerns allocation of additional or deallocation of existing K8s resources to/from an NF Deployment. This enables the SMO to increase or decrease the NF Deployment's service capacity to the required service level. The allocation or deallocation of resources for scaling and subsequent change in NF Deployment service level happens within the bounds of resources available in the K8s cluster running that NF Deployment. In the O2dms K8s profile, Scale NF Deployment may be realized either by SMO managed scaling or by automatic scaling in the K8s cluster. These approaches enable different types of scaling such as scale-out, scale-in, scale-up, and scale-down of NF Deployment. - -#### 3.1.6.2 SMO managed scale - -The SMO may initiate scaling of NF Deployment by creating new or updating the existing K8s resources belonging to that NF Deployment in the K8s cluster. The SMO may explicitly set parameters for K8s workload resources of the NF Deployment (e.g., Deployments, StatefulSets) or manage K8s HorizontalPodAutoscaler (HPA) resource (see clause 4.3.1.4) for auto-scaling. These approaches to scaling may manifest in the following ways: - -- SMO setting min/max replica count values for the HPA resource belonging to an NF Deployment. See clause 3.1.6.3 for HPA resource. -- SMO setting explicit replica counts values for K8s workload resource e.g., Deployments, Statefulsets. -- SMO creating new or updating existing NF Deployment resources for which K8s auto-scaling does not apply e.g., storage, networking etc. - -Scale NF Deployment in a K8s cluster may result in allocation/deallocation of K8s resources related to compute, storage, networking, acceleration, etc. As part of the SMO managed scaling, K8s resources belonging to one or multiple DeploymentItems in the NF Deployment ASD package may be updated (e.g., executing a “helm upgrade” with updated lifecycle parameter values for one or multiple helm charts in the ASD package). - -Figure 3.1.6.2-1 exemplifies the SMO managed scaling of NF Deployment using the O2dms K8s profile. - -![Sequence diagram for 'Scale NF Deployment' between SMO (NFO) and Kubernetes based O-Cloud (K8s API Server).](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) - -The sequence diagram illustrates the interaction for scaling an NF deployment. It begins with a horizontal line labeled "SMO triggered Scale NF Deployment". - -- Step 1:** An arrow labeled "1 Trigger to Scale NF Deployment" points from the SMO (NFO) to the K8s API Server. -- Callout:** A note from the SMO indicates: "SMO generates new or updates the existing NF Deployment resources in the K8s cluster". -- Alt Block:** An "alt" block titled "[K8s resources to be created]" contains a "loop" block titled "[Until all required K8s resources are created]". - - Step 2:** An arrow labeled "2 [O2dms] «HTTP POST» Create K8s resource object" points from the SMO to the K8s API Server. - - Step 3:** A self-call arrow labeled "3 Create K8s resource" is on the K8s API Server lifeline. - - Step 4:** An arrow labeled "4 «HTTP 200» OK" points from the K8s API Server back to the SMO. -- Alt Block:** A second "alt" block titled "[K8s resources to be updated]" contains a "loop" block titled "[Until all required K8s resources are updated]". - - Step 5:** An arrow labeled "5 [O2dms] «HTTP PUT/PATCH» Update K8s resource object" points from the SMO to the K8s API Server. - - Step 6:** A self-call arrow labeled "6 Update K8s resource" is on the K8s API Server lifeline. - - Step 7:** An arrow labeled "7 «HTTP 200» OK" points from the K8s API Server back to the SMO. -- Callout:** A note from the K8s API Server indicates: "K8s API Server notifies the worker nodes in the cluster to scale the NF Deployment resources". -- End:** The sequence concludes with a horizontal line labeled "End of SMO triggered Scale NF Deployment". - -Sequence diagram for 'Scale NF Deployment' between SMO (NFO) and Kubernetes based O-Cloud (K8s API Server). - -Figure 3.1.6.2-1 Scale NF Deployment - -Table 3.1.6.2-1 Scale NF Deployment Use Case - -| Use Case Stage | Evolution/Specification | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Use Case | Scale NF Deployment on a Kubernetes cluster to desired service level. | -| Goal | The goal of this use case is to scale an NF Deployment to a desired service level by the SMO using O2dms K8s profile. | -| Actors and roles |
  • - SMO: The SMO initiates the scaling of NF Deployment.
  • - Kubernetes API Server: O2dms termination point in Kubernetes cluster.
| -| Preconditions | The NF Deployment has been previously instantiated by the SMO. | -| Begins when | The SMO decides to scale an NF Deployment on a K8s cluster. | -| Step 1 | The SMO receives a trigger to scale an NF Deployment to a new service level. | -| (Alt choice) | The SMO decides to scale the NF Deployment by creating additional K8s resources. The additional resources may belong to one or multiple of the DeploymentItems specified in the ASD package of the NF Deployment. | -| Step 2 (M) | The SMO sends new K8s native resource objects using HTTP POST request(s) to the K8s API server. | -| Step 3 (M) | The K8s API server creates the new K8s resources for the NF Deployment. | -| Step 4 (M) | The K8s API server informs the SMO about resource creation. | -| (Alt choice) | The SMO decides to scale an NF Deployment by updating/modifying its existing resources in the K8s cluster. | -| Step 5 (M) | The SMO sends updated K8s resource objects using HTTP PUT/PATCH request(s) to the K8s API server. | -| Step 6 (M) | The K8s API server updates the NF Deployment resources for scaling the workload. | -| Step 7 (M) | The K8s API server informs the SMO about the resource updates. | -| Ends when | This use case ends when the NF Deployment running in a Kubernetes cluster is scaled to the desired service level. | - -#### 3.1.6.3 Kubernetes autoscaling - -K8s inherently supports automatic scaling of workloads based on autoscaling triggers specified for K8s workload resources such as K8s Deployments and StatefulSets. The K8s HorizontalPodAutoscaler resource (see clause 4.3.1.4) may be used to specify minimum and maximum replica count for K8s Pods belonging to an NF Deployment. The HorizontalPodAutoscaler resources may be created as part of NF Deployment instantiation process or as part of a later update. - -To scale an NF Deployment and increase/decrease its service capacity, the K8s cluster running the NF Deployment will automatically create new K8s Pods or reduce the number of existing Pods in the K8s cluster. These changes in the number of Pods are governed by specified minimum and maximum replica count numbers in the HPA resource and resource availability in the K8s cluster. Autoscaling of the NF Deployment resources is performed by K8s within the bounds of the HPA resources. The criteria based on which Kubernetes decides when to invoke automatic scaling or how the autoscaling is achieved are outside the scope of the present document. - -# 4 O2dms Service Definitions for Kubernetes - -## 4.1 General - -The O2dms profile for Kubernetes is based on the usage of Kubernetes native APIs and data model as O2dms interface. Kubernetes offers a native REST based, secured interface with a large set of cluster-scoped and namespace-scoped resource objects as data model. This chapter provides the details of these K8s native APIs and data model. - -## 4.2 Referenced Cloud-Native APIs and Data Model Solutions - -### 4.2.1 Kubernetes API overview - -At high-level, the Kubernetes API [4] structure has a grouping of the managed K8s resource objects which represent K8s resource categories. The generic concepts are introduced regarding the data model of the managed K8s resource objects in Kubernetes. - -#### 4.2.1.1 API Structure - -The Kubernetes API [4] managed objects represent a concrete instance of a K8s resource type on the Kubernetes cluster. Kubernetes leverages standard RESTful terminology to describe the API concepts: - -- A K8s resource is a single instance of a K8s resource type (Note: Throughout this document, to distinguish a "resource" in context of Kubernetes from the "resources" used in a different O-RAN context, this will now be called a "K8s resource") -- A K8s resource type is the name used in the URL -- All K8s resource types have a representation in JSON (their object schema) which is called a kind -- A list of instances of a K8s resource type is known as a collection - -All K8s resource types are either scoped by the Kubernetes cluster (e.g., /apis/GROUP/VERSION/\*) or to a namespace (e.g., /apis/GROUP/VERSION/namespaces/NAMESPACE/\*). - -##### 4.2.1.1.1 API Verbs - -API verbs GET, CREATE, UPDATE, PATCH, DELETE and PROXY support single K8s resources only. These verbs with single K8s resource support have no support for submitting multiple K8s resources together in an ordered or unordered list or transaction. API verbs LIST and WATCH support getting multiple K8s resources, and DELETECOLLECTION supports deleting multiple K8s resources. - -##### 4.2.1.1.2 K8s resource Objects - -The Kubernetes API [4] supports read and write operations on the K8s resource objects via a Kubernetes API endpoint. Kubernetes differentiates the following categories of K8s resource objects managed via their APIs: - -- Workloads: objects used to manage and run OS containers on the Kubernetes cluster. -- Discovery & Loadbalancing: objects used to inter-connect the workloads into externally accessible, load-balanced services. -- Configuration & Storage: objects used to inject initialization data into the containerized applications, and to persist data that is external to the OS containers. -- Cluster: objects define how the Kubernetes cluster itself is configured. -- Metadata: objects used to configure the behavior of other K8s resources within the Kubernetes cluster. - -Note: There are some Kubernetes resource objects (e.g., ClusterRoles, CustomResourceDefinitions, StorageClasses etc.) which the SMO may manage separately from the containerized workload resource management. These are FFS. - -#### 4.2.1.2 Data model concepts - -The K8s resource objects are modelled with individual object schemas. All K8s resource objects typically have 3 components: - -- **K8s resource ObjectMeta:** The metadata about the K8s resource object, such as its name, type, api version, annotations, and labels. This schema, which is common to all K8s resource types, contains fields that maybe updated both by the SMO and the Kubernetes cluster's internal control plane. -- **K8s resourceSpec:** It is defined by the SMO and describes the desired state of system concerning the K8s resource object. Specified when creating or modifying a K8s resource object is requested. -- **K8s resourceStatus:** Provided by the Kubernetes cluster's internal control plane and represents the current state of the system concerning the K8s resource object. - -#### 4.2.1.3 O2dms Procedures - -The following are the list of Kubernetes procedures supported by the O2dms: - -- **CREATE:** The CREATE procedure enables the SMO to instantiate a workload on the target Kubernetes cluster. This procedure requires a namespace and a specified K8s resource type. -- **READ:** - - **GET:** The GET procedure enables the SMO to retrieve and read a specified workload from a target Kubernetes cluster. This procedure requires a namespace, a specified K8s resource type, and the name of the K8s resource. - - **LIST:** The LIST procedure enables the SMO to list or watch a specified workload type from a target Kubernetes cluster. This procedure requires a namespace and a specified K8s resource type. -- **UPDATE:** - - **PATCH:** The PATCH procedure enables the SMO to partially update a workload in a Kubernetes cluster. This procedure requires a namespace, a specified K8s resource type, and the name of the K8s resource. - - **REPLACE:** The REPLACE procedure enables the SMO to replace a workload in a target Kubernetes cluster. This procedure requires a namespace, a specified K8s resource type, the name of the K8s resource. -- **DELETE:** The DELETE procedure enables the SMO to terminate a workload(s) in a target Kubernetes cluster. This procedure requires a namespace, a specified K8s resource type, and the name of the K8s resource. - -## 4.3 Referenced K8s resource objects - -The Kubernetes APIs and resource objects are fully specified by the open-source Kubernetes project and this document adopts those definitions, APIs, and resource objects [5]. For the purposes of this document, the terms and definitions for Kubernetes API resource objects given in [5] would apply. This section provides details of relevant K8s APIs and resource objects along with recommended use and constraints, if any. - -### 4.3.1 Kubernetes Native Namespace Scoped Resource Objects - -#### 4.3.1.1 Kubernetes native workload resources - -##### 4.3.1.1.1 Pod - -A Pod is the smallest and most basic deployable unit of functionality in a K8s cluster. A Pod resource represents a single instance of one or multiple containers that are scheduled and run on a single worker node in a K8s cluster. The containers in a Pod are managed as a single unit and share the Pod’s networking and storage resources. - -Table 4.3.1.1.1-1 provides details of the standard K8s Pod resource specification. - -**Table 4.3.1.1.1-1: Pod resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the Pod resource. | -| kind | string | Represents the REST resource for Pod resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the Pod resource [6]. | -| spec | PodSpec | Specifies the desired behavior of the Pod resource. | -| status | PodStatus | Represents the most recent observed status of the Pod resource. | - -Table 4.3.1.1.1-2 provides relevant K8s Pod resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a K8s Pod resource in a chosen K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.1.1-2 with K8s standard query and body parameters for Pod resource included in the HTTP request [5]. - -**Table 4.3.1.1.1-2: Pod resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant Pod Resource URIs | Supported HTTP Methods | -|-----------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /api/v1/namespaces/{namespace}/pods |
  • • POST: Create a Pod resource in the specified namespace
  • • GET: List or watch Pod resources in the namespace
  • • DELETE: Delete all Pods resources from the namespace
| -| /api/v1/namespaces/{namespace}/pods/{name} |
  • • PUT: Replace the Pod resource in the namespace
  • • PATCH: Partial update the Pod resource in the namespace
  • • DELETE: Delete the Pod resource from the namespace
  • • GET: Get status of the Pod resource in the namespace
| -| /api/v1/namespaces/{namespace}/pods/{name}/eviction |
  • • POST: Terminate the running Pod instance
| - -**NOTE:** A Pod resource should not be created directly via O2dms because a Pod resource created directly is not managed by K8s control plane and it cannot repair or replace itself. A Pod resources should be created through K8s controller resources instead (e.g., Deployment, Job, Statefulset). - -##### 4.3.1.1.2 Deployment - -A K8s deployment resource is used for running one or multiple identical stateless Pods in a K8s cluster. A Deployment resource ensures that the desired number of replicas of a Pod are running at any given time by replacing any failed or unresponsive Pod instances. The Deployment resource object contains the Pod resource template which specifies the details of the Pods to be created and instantiated on K8s worker node/s. Deployment resource is generally used for running stateless applications in K8s clusters since it does not provide a unique identity to the Pods it manages. - -Table 4.3.1.1.2-1 provides details of the standard K8s Deployment resource specification. - -**Table 4.3.1.1.2-1: Deployment resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the Deployment resource. | -| kind | string | Represents the REST resource for Deployment resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the Deployment resource [6]. | -| spec | DeploymentSpec | Specifies the desired behavior of the Deployment resource. | -| status | DeploymentStatus | Represents the most recent observed status of the Deployment resource. | - -Table 4.3.1.1.2-2 provides relevant K8s Deployment resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a K8s Deployment resource in a chosen K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.1.2-2 with K8s standard query and body parameters for Deployment resource included in the HTTP request [5]. - -**Table 4.3.1.1.2-2: Deployment resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant Deployment Resource URIs | Supported HTTP Methods | -|---------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /apis/apps/v1/namespaces/{namespace}/deployments |
  • POST: Create a Deployment resource in the specified namespace
  • GET: List or watch Deployment resources in the namespace
  • DELETE: Delete all Deployment resources from the namespace
| -| /apis/apps/v1/namespaces/{namespace}/deployments/{name} |
  • PUT: Replace the Deployment resource in the namespace
  • PATCH: Partial update the Deployment resource in the namespace
  • DELETE: Delete the Deployment resource from the namespace
  • GET: Read the Deployment resource in the namespace
| - -NOTE: The creation of a Deployment resource in a K8s cluster also results in the creation of the K8s ReplicaSet resource in the same cluster. The ReplicaSet resource ensures that the number of Pods running in the cluster are equal to the number requested in the Deployment resource. A Deployment resource should be used instead of creating the ReplicaSet resource directly. The K8s Deployment resource fully substitutes the ReplicaSet functions and should be used in most cases. - -##### 4.3.1.1.3 StatefulSet - -A K8s statefulset resource is used for running one or multiple stateful Pods that maintain unique and persistent identities and hostnames during their lifetime. The Pods belonging to a StatefulSet resource are created from the same Pod spec but maintain their individual identities across any rescheduling events caused by Pod failures. In addition, statefulsets provide an ordered and graceful deployment and scaling of Pods in K8s clusters. By default, the Pod deployment for statefulsets is done in sequential order and termination in reverse order but this behavior can be overridden. For state persistency, StatefulSet resources are generally paired with persistent storage volumes and this paired relationship is maintained across Pod rescheduling events. - -Table 4.3.1.1.3-1 provides details of the standard K8s StatefulSet resource specification. - -**Table 4.3.1.1.3-1: StatefulSet resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the StatefulSet resource. | -| kind | string | Represents the REST resource for StatefulSet resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the StatefulSet resource [6]. | -| spec | StatefulSetSpec | Specifies the desired identities of the Pods in the StatefulSet resource. | -| status | StatefulSetStatus | Represents the most recent observed status of the Pods in the StatefulSet. | - -Table 4.3.1.1.3-2 provides relevant K8s StatefulSet resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a K8s StatefulSet resource in a chosen K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.1.3-2 with K8s standard query and body parameters for StatefulSet resource included in the HTTP request [5]. - -**Table 4.3.1.1.3-2: StatefulSet resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant StatefulSet Resource URIs | Supported HTTP Methods | -|----------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /apis/apps/v1/namespaces/{namespace}/statefulsets |
  • POST: Create a StatefulSet resource in the specified namespace
  • GET: List or watch all StatefulSet resources in the namespace
  • DELETE: Delete all StatefulSet resources from the namespace
| -| /apis/apps/v1/namespaces/{namespace}/statefulsets/{name} |
  • PUT: Replace the StatefulSet resource in the namespace
  • PATCH: Partial update the StatefulSet resource in the namespace
  • DELETE: Delete the StatefulSet resource from the namespace
  • GET: Read the StatefulSet resource in the namespace
| - -##### **4.3.1.1.4 DaemonSet** - -A K8s DaemonSet resource is used for running a Pod instance on all or a subset of the worker nodes in a K8s cluster. If the cluster scales up or down i.e., worker nodes are added or removed from the cluster, the daemonset Pods are scaled accordingly to ensure that one Pod per worker node requirement is met. - -Table 4.3.1.1.4-1 provides details of the standard K8s DaemonSet resource specification. - -**Table 4.3.1.1.4-1: DaemonSet resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the DaemonSet resource. | -| kind | string | Represents the REST resource for DaemonSet resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the DaemonSet resource [6]. | -| spec | DaemonSetSpec | Specifies the desired behavior of the DaemonSet resource. | -| status | DaemonSetStatus | Represents the most recent observed status of the DaemonSet resource. | - -Table 4.3.1.1.4-2 provides relevant K8s DaemonSet resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a K8s DaemonSet resource in a K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.1.4-2 with K8s standard query and body parameters for DaemonSet resource included in the HTTP request [5]. - -**Table 4.3.1.1.4-2: DaemonSet resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant DaemonSet Resource URIs | Supported HTTP Methods | -|--------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /apis/apps/v1/namespaces/{namespace}/daemonsets |
  • POST: Create a DaemonSet resource in specified namespace
  • GET: List or watch all DaemonSet resources in the namespace
  • DELETE: Delete all DaemonSet resources from the namespace
| -| /apis/apps/v1/namespaces/{namespace}/daemonsets/{name} |
  • PUT: Replace the DaemonSet resource in the namespace
  • PATCH: Partial update the DaemonSet resource in the namespace
  • DELETE: Delete the DaemonSet resource from the namespace
  • GET: Read the DaemonSet resource in the namespace
| - -##### 4.3.1.1.5 Job - -A K8s Job resource is used for running workloads in K8s clusters that run to completion and are terminated after completion. A Job resource can create one or more Pods and execute them until a specified number of Jobs are successfully terminated. A Job resource tracks successful completions of Pod executions and upon reaching the desired number of completions, the Job is considered complete. - -Table 4.3.1.1.5-1 provides details of the standard K8s Job resource specification. - -**Table 4.3.1.1.5-1: Job resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the Job resource. | -| kind | string | Represents the REST resource for Job resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the Job resource [6]. | -| spec | JobSpec | Specifies the desired behavior of the Job resource. | -| status | JobStatus | Represents the most recent observed status of the Job resource. | - -Table 4.3.1.1.5-2 provides relevant K8s Job resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a Job resource in a chosen K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.1.5-2 with K8s standard query and body parameters for Job resource included in the HTTP request [5]. - -**Table 4.3.1.1.5-2: Job resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant Job Resource URIs | Supported HTTP Methods | -|---------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /apis/batch/v1/namespaces/{namespace}/jobs |
  • POST: Create a Job resource in specified namespace
  • GET: List or watch all Job resources in the namespace
  • DELETE: Delete all Job resources from the namespace
| -| /apis/batch/v1/namespaces/{namespace}/jobs/{name} |
  • PUT: Replace the Job resource in the namespace
  • PATCH: Partial update the Job resource in the namespace
  • DELETE: Delete the Job resource from the namespace
  • GET: Read the Job resource in the namespace
| - -##### 4.3.1.1.6 CronJob - -A K8s CronJob resource is used for running K8s Jobs on a pre-defined time schedule provided in Linux/Unix Cron format. The time schedule of the CronJob resource follows the timezone set for the K8s native kube-controller-manager function. - -Table 4.3.1.1.6-1 provides details of the standard K8s CronJob resource specification. - -**Table 4.3.1.1.6-1: CronJob resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the CronJob resource. | -| kind | string | Represents the REST resource for CronJob resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the CronJob resource [6]. | -| spec | CronJobSpec | Specifies the desired behavior of the CronJob resource. | -| status | CronJobStatus | Represents the most recent observed status of the CronJob resource. | - -Table 4.3.1.1.6-2 provides relevant K8s CronJob resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a CronJob resource in a chosen K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.1.6-2 with K8s standard query and body parameters for CronJob resource included in the HTTP request [5]. - -**Table 4.3.1.1.6-2: CronJob resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant CronJob Resource URIs | Supported HTTP Methods | -|-------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /apis/batch/v1/namespaces/{namespace}/cronjobs |
  • • POST: Create a CronJob resource in specified namespace
  • • GET: List or watch all CronJob resources in the namespace
  • • DELETE: Delete all CronJob resources from the namespace
| -| /apis/batch/v1/namespaces/{namespace}/cronjobs/{name} |
  • • PUT: Replace the CronJob resource in the namespace
  • • PATCH: Partial update the CronJob resource in the namespace
  • • DELETE: Delete the CronJob resource from the namespace
  • • GET: Read the CronJob resource in the namespace
| - -#### 4.3.1.2 Kubernetes native discovery and load balancing resources - -##### 4.3.1.2.1 Service - -A K8s Service resource is used for exposing a containerized workload/application running in a K8s cluster to internal and external clients. The Service resource also abstracts the ephemeral nature of Pods and containers by creating a constant point of entry to the group of Pods that provide the same functionality. Each Service gets an IP address and port number that does not change during the lifetime of the Service resource in the K8s cluster. In addition, the Service resource provides load-balancing across all Pod instances that provide the same functionality. Kubernetes supports five types of Service resources identified as ClusterIP, NodePort, LoadBalancer, ExternalName and Headless Service with ClusterIP being the default Service type. - -Table 4.3.1.2.1-1 provides details of the standard K8s Service resource specification. - -**Table 4.3.1.2.1-1: K8s Service resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the Service resource. | -| kind | string | Represents the REST resource for Service resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the Service resource [6] | -| spec | ServiceSpec | Specifies the desired behavior and type of the Service resource | -| status | ServiceStatus | Read only. Represents the most recent observed status of the Service resource | - -Table 4.3.1.2.1-2 provides relevant K8s Service resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a Service resource in a chosen K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.2.1-2 with K8s standard query and body parameters for Service resource included in the HTTP request [5]. - -**Table 4.3.1.2.1-2: K8s Service resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant Service Resource URIs | Supported HTTP Methods | -|------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /api/v1/namespaces/{namespace}/services |
  • • POST: Create a Service resource in the specified namespace
  • • GET: List or watch all Service resources in the namespace
  • • DELETE: Delete all Service resources from the namespace
| -| /api/v1/namespaces/{namespace}/services/{name} |
  • • PUT: Replace the Service resource in the namespace
  • • PATCH: Partial update the Service resource in the namespace
  • • DELETE: Delete the Service resource from the namespace
  • • GET: Read the Service resource in the namespace
| - -##### 4.3.1.2.2 Ingress - -A K8s Ingress resource is used for defining HTTP(s) routing rules that control external access to applications running inside the K8s cluster. A K8s Ingress resource can be associated with one or more K8s Service resources (each of which can expose a different set of Pods) and offers load-balancing and SSL termination features. The Ingress resource can assign a specific externally reachable URL to each Service resource associated with it. - -Table 4.3.1.2.2-1 provides details of the standard K8s Ingress resource specification. - -**Table 4.3.1.2.2-1: K8s Ingress resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the Ingress resource. | -| kind | string | Represents the REST resource for Ingress resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the Ingress resource [6] | -| spec | IngressSpec | Specifies the desired behavior of the Ingress resource | -| status | IngressStatus | Represents the most recent observed status of the Ingress resource | - -Table 4.3.1.2.2-2 provides relevant K8s Ingress resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage an Ingress resource in a chosen K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.2.2-2 with K8s standard query and body parameters for Ingress resource included in the HTTP request [5]. - -**Table 4.3.1.2.2-2: K8s Ingress resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant Ingress Resource URIs | Supported HTTP Methods | -|--------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses |
  • POST: Create an Ingress resource in the specified namespace
  • GET: List or watch all Ingress resources in the namespace
  • DELETE: Delete all Ingress resources from the namespace
| -| /apis/networking.k8s.io/v1/namespaces/{namespace}/ingresses/{name} |
  • PUT: Replace the Ingress resource in the namespace
  • PATCH: Partial update the Ingress resource in the namespace
  • DELETE: Delete the Ingress resource from the namespace
  • GET: Read the specified Ingress resource in the namespace
| - -NOTE: For an Ingress resource to work, an Ingress controller (i.e., an additional controller to the default K8s controllers) shall be running inside the K8s cluster. K8s does not offer a default ingress controller and leaves the choice of ingress controller to the cluster administrator. In the ORAN context, the K8s cluster may have a default ingress controller installed at the time of cluster creation, or the SMO may decide to extend the K8s cluster with any specific ingress controller after cluster creation using O2dms interface. - -##### 4.3.1.2.3 NetworkPolicy - -A K8s NetworkPolicy resource is used to control traffic flow to/from a K8s workloads at the IP address or port level using ingress and egress rules. These rules may apply to other K8s Pods, Namespaces, or generic IP blocks to restrict or allow traffic from these entities. Selectors and IP blocks (CIDR ranges) are used to enforce the NetworkPolicy constraints specified in the NetworkPolicy resource specification. - -Table 4.3.1.2.3-1 provides details of the standard K8s NetworkPolicy resource specification. - -Table 4.3.1.2.3-1: NetworkPolicy resource specification [5] - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the NetworkPolicy resource. | -| kind | string | Represents the REST resource for NetworkPolicy. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the NetworkPolicy resource [6] | -| spec | NetworkPolicySpec | Specifies the desired behavior of the NetworkPolicy resource and the ingress and/or egress traffic rules to be enforced in the cluster. | -| status | NetworkPolicyStatus | Describes the current state of the NetworkPolicy | - -Table 4.3.1.2.3-2 provides relevant K8s NetworkPolicy resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a K8s NetworkPolicy resource in a K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.2.3-2 with K8s standard query and body parameters for NetworkPolicy resource included in the HTTP request [5]. - -Table 4.3.1.2.3-2: NetworkPolicy resource URIs and HTTP methods supported using O2dms K8s profile - -| Relevant NetworkPolicy Resource URIs | Supported HTTP Methods | -|--------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies |
  • POST: Create a new NetworkPolicy resource in the specified namespace
  • GET: List or watch all NetworkPolicy resources in the namespace
  • DELETE: Delete all NetworkPolicy resources from the namespace
| -| /apis/networking.k8s.io/v1/namespaces/{namespace}/networkpolicies/{name} |
  • PUT: Replace the NetworkPolicy resource in the namespace
  • PATCH: Partial update the NetworkPolicy resource in the namespace
  • DELETE: Delete the NetworkPolicy resource from the namespace
  • GET: Read the NetworkPolicy resource in the namespace
| - -NOTE: The functionality of the NetworkPolicy resource depends on the presence of a compatible K8s network plugin that supports K8s network policies. Without a supporting network plugin, the NetworkPolicy resource creation will have no impact on the ingress and egress traffic to/from a K8s workload. - -#### 4.3.1.3 Kubernetes native storage and workload configuration resources - -##### 4.3.1.3.1 ConfigMap - -A K8s ConfigMap resource is used for storing non-confidential data in the form of key-value pairs that can be read as runtime configurations by Pods in a K8s cluster. ConfigMap resource can be used to store configuration files, environment variables or command line arguments for workloads to use at runtime. A ConfigMap resource decouples the workload containers from environment specific configuration data thereby making the K8s Pods easily portable across the worker nodes in a K8s cluster. The data stored in a ConfigMap cannot exceed 1 MiB. - -Table 4.3.1.3.1-1 provides details of the standard K8s ConfigMap resource specification. - -Table 4.3.1.3.1-1: K8s ConfigMap resource specification [5] - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the ConfigMap resource. | -| kind | string | Represents the REST resource for ConfigMap resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the ConfigMap resource [6] | -| data | object | Contains the configuration data in key-value pairs. Keys shall be alphanumeric characters and '-', '_', or '.'. Values shall be UTF-8 byte sequence. Keys in the data field shall not overlap with keys in binaryData field to pass validation checks at ConfigMap creation time. | -| binaryData | object | Contains binary data in key-value pairs. Keys shall be alphanumeric characters and '-', '_', or '.'. Values can contain byte sequences that are not in UTF-8 range. Keys in the binaryData field shall not overlap with keys in the data field to pass validation checks at ConfigMap creation time. | -| immutable | boolean | When true, the data stored in the ConfigMap cannot be updated. When false, the data can be modified at any time. | - -Table 4.3.1.3.1-2 provides relevant K8s ConfigMap resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage an ConfigMap resource in a chosen K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.3.1-2 with K8s standard query and body parameters for ConfigMap resource included in the HTTP request [5]. - -**Table 4.3.1.3.1-2: K8s ConfigMap resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant ConfigMap Resource URIs | Supported HTTP Methods | -|--------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /api/v1/namespaces/{namespace}/configmaps |
  • POST: Create a ConfigMap resource in the specified namespace
  • GET: List or watch all ConfigMap resources in the namespace
  • DELETE: Delete all ConfigMap resources from the namespace
| -| /api/v1/namespaces/{namespace}/configmaps/{name} |
  • PUT: Replace the ConfigMap resource in the namespace
  • PATCH: Partial update the ConfigMap resource in the namespace
  • DELETE: Delete the ConfigMap resource from the namespace
  • GET: Read the specified ConfigMap resource in the namespace
| - -##### 4.3.1.3.2 Secret - -A K8s Secret resource is used for storing sensitive or confidential data in key value pairs format. Secrets are like ConfigMaps but specifically intended to be used for storing confidential data such as passwords, OAuth tokens, SSH keys etc. By default, data stored in Secrets is not encrypted in a K8s cluster. - -Table 4.3.1.3.2-1 provides details of the standard K8s Secret resource specification. - -**Table 4.3.1.3.2-1: K8s Secret resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the Secret resource. | -| kind | string | Represents the REST resource for Secret resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the Secret resource [6] | -| data | object | Contains the secret data in key-value pairs. Keys shall be alphanumeric characters and '-', '_', or '.'. Values are serialized form of the secret data specified as base64 encoded string. | -| stringData | object | Contains non-binary secret data in string form. | -| immutable | boolean | When true, the data stored in the ConfigMap cannot be updated. When false, the data can be modified at any time. | -| type | String | A non-constrained string value. Used to facilitate programmatic handling of secret data. Defaults to Opaque (arbitrary user-defined data) | - -Table 4.3.1.3.2-2 provides relevant K8s Secret resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a Secret resource in a chosen K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.3.2-2 with K8s standard query and body parameters for Secret resource included in the HTTP request [5]. - -**Table 4.3.1.3.2-2: K8s Secret resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant Secret Resource URIs | Supported HTTP Methods | -|-----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /api/v1/namespaces/{namespace}/secrets |
  • • POST: Create a Secret resource in the specified namespace
  • • GET: List or watch all Secret resources in the namespace
  • • DELETE: Delete all Secret resources from the namespace
| -| /api/v1/namespaces/{namespace}/secrets/{name} |
  • • PUT: Replace the Secret resource in the namespace
  • • PATCH: Partial update the Secret resource in the namespace
  • • DELETE: Delete the Secret resource from the namespace
  • • GET: Read the specified Secret resource in the namespace
| - -##### **4.3.1.3.3 PersistentVolumeClaim** - -The K8s PersistentVolumeClaim resource is used for requesting and claiming a K8s PersistentVolume resource. The PersistentVolume may pre-exist in the K8s cluster or created dynamically in response to the creation of PersistentVolumeClaim resource. A PersistentVolumeClaim provides a way to request a persistent storage for Pods without knowing the underlying storage technology. Pods can use PersistentVolumeClaims as volumes and mount them as part of the Pod specification. - -Table 4.3.1.3.3-1 provides details of the standard K8s PersistentVolumeClaim resource specification. - -**Table 4.3.1.3.3-1: K8s PersistentVolumeClaim resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the PersistentVolumeClaim resource. | -| kind | string | Represents the REST resource for PersistentVolumeClaim resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the PersistentVolumeClaim resource [6] | -| spec | PersistentVolumeClaimSpec | Specifies the desired characteristics of the persistent volume requested for the Pod. | -| status | PersistentVolumeClaimStatus | Read only. Represents the most recent observed status of the PersistentVolumeClaim resource. | - -Table 4.3.1.3.3-2 provides relevant K8s PersistentVolumeClaim resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a PersistentVolumeClaim resource in a chosen K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.3.3-2 with K8s standard query and body parameters for PersistentVolumeClaim resource included in the HTTP request [5]. - -**Table 4.3.1.3.3-2: K8s PersistentVolumeClaim resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant PersistentVolumeClaim Resource URIs | Supported HTTP Methods | -|--------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /api/v1/namespaces/{namespace}/persistentvolumeclaims |
  • • POST: Create a PersistentVolumeClaim resource in the specified namespace
  • • GET: List or watch all PersistentVolumeClaim resources in the namespace
  • • DELETE: Delete all PersistentVolumeClaim resources from the namespace
| -| /api/v1/namespaces/{namespace}/persistentvolumeclaims/{name} |
  • • PUT: Replace the PersistentVolumeClaim resource in the namespace
  • • PATCH: Partial update the PersistentVolumeClaim resource in the namespace
  • • DELETE: Delete the PersistentVolumeClaim resource from the namespace
  • • GET: Read the PersistentVolumeClaim resource in the namespace
| - -#### 4.3.1.4 Kubernetes native metadata and cluster configuration resources - -##### 4.3.1.4.1 LimitRange - -A K8s LimitRange resource is used to set constraints on the resource utilization of Pods and containers in a namespace. By default, a container can use as much compute resources as it needs in the namespace and that can lead to resource contention problems among Pods and containers that share the namespace and may belong to different priority classes. A LimitRange resource can enforce defaults or min-max values for different resources in the namespace (e.g., CPU, memory, storage) at Pod or container level. - -Table 4.3.1.4.1-1 provides details of the standard K8s LimitRange resource specification. - -**Table 4.3.1.4.1-1: K8s LimitRange resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the LimitRange resource. | -| kind | string | Represents the REST resource for LimitRange resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the LimitRange resource [6] | -| spec | LimitRangeSpec | Specifies the limits that will be enforced on resources in a namespace. | - -Table 4.3.1.4.1-2 provides relevant K8s LimitRange resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a LimitRange resource in a chosen K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.4.1-2 with K8s standard query and body parameters for LimitRange resource included in the HTTP request [5]. - -**Table 4.3.1.4.1-2: K8s LimitRange resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant LimitRange Resource URIs | Supported HTTP Methods | -|---------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /api/v1/namespaces/{namespace}/limitranges |
  • POST: Create a LimitRange resource in the specified namespace
  • GET: List or watch all LimitRange resources in the namespace
  • DELETE: Delete all LimitRange resources from the namespace
| -| /api/v1/namespaces/{namespace}/limitranges/{name} |
  • PUT: Replace the LimitRange resource in the namespace
  • PATCH: Partial update the LimitRange resource in the namespace
  • DELETE: Delete the LimitRange resource from the namespace
  • GET: Read the LimitRange resource in the namespace
| - -##### 4.3.1.4.2 ResourceQuota - -A K8s ResourceQuota resource is used to set limits on the total/aggregate resource consumption in a namespace. A ResourceQuota object can specify limits for other K8s resource objects (by resource type) and compute resources (e.g., memory, CPU, storage). A single K8s namespace can have multiple ResourceQuota resources with unique names for limiting different types of namespace scoped resources. The ResourceQuota specified limits are enforced at K8s resource creation time and have no impact on existing Pods and resources in the namespace. - -Table 4.3.1.4.2-1 provides details of the standard K8s ResourceQuota resource specification. - -**Table 4.3.1.4.2-1: ResourceQuota resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the ResourceQuota resource. | -| kind | string | Represents the REST resource for ResourceQuota. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the ResourceQuota resource [6] | -| spec | ResourceQuotaSpec | Specifies the desired quota of K8s resource objects and/or compute resources imposed on the namespace | -| status | ResourceQuotaStatus | Defines the actual enforced quota and its current usage | - -Table 4.3.1.4.2-2 provides relevant K8s ResourceQuota resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a K8s ResourceQuota resource in a K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.4.2-2 with K8s standard query and body parameters for ResourceQuota resource included in the HTTP request [5]. - -**Table 4.3.1.4.2-2: ResourceQuota resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant ResourceQuota Resource URIs | Supported HTTP Methods | -|------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /api/v1/namespaces/{namespace}/resourcequotas |
  • POST: Create a new ResourceQuota resource in the specified namespace
  • GET: List or watch all ResourceQuota resources in the namespace
  • DELETE: Delete all ResourceQuota resources from the namespace
| -| /api/v1/namespaces/{namespace}/resourcequotas/{name} |
  • PUT: Replace the ResourceQuota resource in the namespace
  • PATCH: Partial update the ResourceQuota resource in the namespace
  • DELETE: Delete the ResourceQuota resource from the namespace
  • GET: Read the ResourceQuota resource in the namespace
| - -##### 4.3.1.4.3 HorizontalPodAutoscaler - -A K8s HorizontalPodAutoscaler resource is used to automatically scale up or down, the number of Pod instances belonging to a workload resource that supports horizontal scaling (e.g., Deployments and StatefulSets). The scale-up and scale-down levels are controlled by defined minimum and maximum values in the HorizontalPodAutoscaler resource. The HorizontalPodAutoscaler resource works by changing the “scale” property of a workload resource e.g., Deployment, based on observed metrics such as CPU and Memory utilization. - -NOTE: For the K8s cluster to horizontally scale a workload based on the metrics specified in the K8s HorizontalPodAutoscaler resource, it should have a metrics collection service running in the cluster. - -Table 4.3.1.4.3-1 provides details of the standard K8s HorizontalPodAutoscaler resource specification. - -**Table 4.3.1.4.3-1: HorizontalPodAutoscaler resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the HorizontalPodAutoscaler resource. | -| kind | string | Represents the REST resource for HorizontalPodAutoscaler resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the HorizontalPodAutoscaler resource [6]. | -| spec | HorizontalPodAutoscalerSpec | Specifies the min-max replica count and behavior of the HorizontalPodAutoscaler resource. | -| status | HorizontalPodAutoscalerStatus | Represents the most recent observed status of the HorizontalPodAutoscaler resource. | - -Table 4.3.1.4.3-2 provides relevant K8s HorizontalPodAutoscaler resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a K8s HorizontalPodAutoscaler resource in a chosen K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.4.3-2 with K8s standard query and body parameters for HorizontalPodAutoscaler resource included in the HTTP request [5]. - -**Table 4.3.1.4.3-2: HorizontalPodAutoscaler resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant HorizontalPodAutoscaler Resource URIs | Supported HTTP Methods | -|-----------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /apis/autoscaling/v2/namespaces/{namespace}/horizontalpodautoscalers |
  • • POST: Create a HorizontalPodAutoscaler resource in the specified namespace
  • • GET: List or watch HorizontalPodAutoscaler resources in the namespace
  • • DELETE: Delete all HorizontalPodAutoscaler resources from the namespace
| -| /apis/autoscaling/v2/namespaces/{namespace}/horizontalpodautoscalers/{name} |
  • • PUT: Replace the HorizontalPodAutoscaler resource in the namespace
  • • PATCH: Partial update the HorizontalPodAutoscaler resource in the namespace
  • • DELETE: Delete the HorizontalPodAutoscaler resource from the namespace
  • • GET: Read the HorizontalPodAutoscaler resource in the namespace
| - -##### 4.3.1.4.4 PodDisruptionBudget - -A K8s PodDisruptionBudget resource is used to ensure that a specific number of Pod instances belonging to a workload resource (e.g., Deployments, StatefulSets) are available in the cluster in a healthy running state in the event of planned or unplanned Pod disruptions. A K8s PodDisruptionBudget resource ensures that the application or service offered by the Pods remains available in the event of concurrent disruptions due to Pod termination events. The number of healthy Pod instances required during disruption events can be specified as a minimum-available or maximum-unavailable number. - -Table 4.3.1.4.4-1 provides details of the standard K8s PodDisruptionBudget resource specification. - -**Table 4.3.1.4.4-1: PodDisruptionBudget resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the PodDisruptionBudget resource. | -| kind | string | Represents the REST resource for PodDisruptionBudget resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the PodDisruptionBudget resource [6]. | -| spec | PodDisruptionBudgetSpec | Specifies the desired behavior of PodDisruptionBudget resource. | -| status | PodDisruptionBudgetStatus | Represents the most recent observed status of the PodDisruptionBudget resource. | - -Table 4.3.1.4.4-2 provides relevant K8s PodDisruptionBudget resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a K8s PodDisruptionBudget resource in a chosen K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.4.4-2 with K8s standard query and body parameters for PodDisruptionBudget resource included in the HTTP request [5]. - -**Table 4.3.1.4.4-2: PodDisruptionBudget resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant PodDisruptionBudget Resource URIs | Supported HTTP Methods | -|--------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets |
  • • POST: Create a PodDisruptionBudget resource in the specified namespace
  • • GET: List or watch PodDisruptionBudget resources in the namespace
  • • DELETE: Delete all PodDisruptionBudget resources from the namespace
| -| /apis/policy/v1/namespaces/{namespace}/poddisruptionbudgets/{name} |
  • • PUT: Replace the PodDisruptionBudget resource in the namespace
  • • PATCH: Partial update the PodDisruptionBudget resource in the namespace
  • • DELETE: Delete the PodDisruptionBudget resource from the namespace
  • • GET: Read the PodDisruptionBudget resource in the namespace
| - -##### 4.3.1.4.5 ServiceAccount - -A K8s ServiceAccount is a namespace scoped resource that provides a distinct identity that can be authenticated and authorized. Other K8s objects such as Pods can use the ServiceAccount’s associated credentials to identify as that ServiceAccount. Permissions can be granted within the K8s cluster to a ServiceAccount’s holder via authorization methods such as Role Based Access Control (RBAC). - -Table 4.3.1.4.5-1 provides details of the standard K8s ServiceAccount resource specification. - -**Table 4.3.1.4.5-1: K8s ServiceAccount resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|------------------------------|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the ServiceAccount resource. | -| kind | string | Represents the REST resource for ServiceAccount resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the ServiceAccount resource [6]. | -| automountServiceAccountToken | boolean | Indicates if the pod using this ServiceAccount should have an API token mounted automatically. | -| imagePullSecrets | List [LocalObjectReference] | List of references to secrets in the namespace that can be used for pulling images in the pods that use this ServiceAccount. | -| secrets | List [ObjectReference] | List of secrets in the same namespace that pods using this ServiceAccount are allowed to use. | - -Table 4.3.1.4.5-2 provides relevant K8s ServiceAccount resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a ServiceAccount resource in a chosen K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.4.5-2 with K8s standard query and body parameters for ServiceAccount resource included in the HTTP request [5]. - -**Table 4.3.1.4.5-2: K8s ServiceAccount resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant ServiceAccount Resource URIs | Supported HTTP Methods | -|------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /api/v1/namespaces/{namespace}/serviceaccounts |
  • POST: Create a ServiceAccount resource in the specified namespace
  • GET: List ServiceAccount resources in the given namespace
  • DELETE: Delete collection of ServiceAccount resources from the given namespace
| -| /api/v1/namespaces/{namespace}/serviceaccount/{name} |
  • PUT: Replace the named ServiceAccount resource in the given namespace
  • PATCH: Partial update the named ServiceAccount resource in the given namespace
  • DELETE: Delete the named ServiceAccount resource from the given namespace
  • GET: Read the named ServiceAccount resource in the given namespace
| - -##### 4.3.1.4.6 Role - -A K8s Role is a namespace scoped resource that provides a logical grouping of policy rules. A policy rule determines what a bearer of that role, in this instance the Role resource, is allowed to do in the namespace. K8s resources such as Pods can reference a Role using RoleBinding (see clause 4.3.1.4.7) which enable that Pod to perform actions conforming to the policy rules of the Role. - -Table 4.3.1.4.6-1 provides details of the standard K8s Role resource specification. - -**Table 4.3.1.4.6-1: K8s Role resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the Role resource. | -| kind | string | Represents the REST resource for Role resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the Role resource [6]. | -| rules | List [PolicyRule] | Contains the list of PolicyRules associated with the role. | - -Table 4.3.1.4.6-2 provides relevant K8s Role resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a Role resource in a chosen K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.4.6-2 with K8s standard query and body parameters for Role resource included in the HTTP request [5]. - -**Table 4.3.1.4.6-2: K8s Role resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant ServiceAccount Resource URIs | Supported HTTP Methods | -|------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles |
  • POST: Create a Role resource in the given namespace
  • GET: List Role resources in the given namespace
  • DELETE: Delete collection of Role resources in the given namespace
| -| /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/roles/{name} |
  • PUT: Replace the named Role resource in the given namespace
  • PATCH: Partial update the named Role resource in the given namespace
  • DELETE: Delete the named Role resource in the given namespace
  • GET: Read the named Role resource in the given namespace
| - -##### 4.3.1.4.7 RoleBinding - -A K8s RoleBinding is a namespace scoped resource that is used to reference a Role and binds that role to a list of subjects. A subject is a reference to an object in the namespace e.g., a ServiceAccount, to which the role applies. A RoleBinding only affects objects in the same namespace. - -Table 4.3.1.4.7-1 provides details of the standard K8s RoleBinding resource specification. - -**Table 4.3.1.4.7-1: K8s RoleBinding resource specification [5]** - -| Resource Field | Resource Field Type | Resource Field Description | -|----------------|---------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiVersion | string | Defines the versioned schema of the RoleBinding resource. | -| kind | string | Represents the REST resource for RoleBinding resource. The K8s API Server may infer this from the endpoint the client submits the request to. The value cannot be updated. | -| metadata | ObjectMeta | Standard metadata of the RoleBinding resource [6]. | -| roleRef | RoleRef | Contains reference to a Role in the namespace. This field is immutable. | -| Subjects | List [Subject] | List of Subjects. A subject holds a reference to the object the role applies to. | - -Table 4.3.1.4.7-2 provides relevant K8s RoleBinding resource URIs and supported HTTP methods using O2dms interface. For the SMO to lifecycle manage a RoleBinding resource in a chosen K8s cluster using O2dms K8s profile, it shall use the URIs, and HTTP methods listed in Table 4.3.1.4.7-2 with K8s standard query and body parameters for RoleBinding resource included in the HTTP request [5]. - -**Table 4.3.1.4.7-2: K8s RoleBinding resource URIs and HTTP methods supported using O2dms K8s profile** - -| Relevant ServiceAccount Resource URIs | Supported HTTP Methods | -|-------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings |
  • POST: Create a RoleBinding resource in the given namespace
  • GET: List RoleBinding resources in the given namespace
  • DELETE: Delete collection of RoleBinding resources in the given namespace
| -| /apis/rbac.authorization.k8s.io/v1/namespaces/{namespace}/rolebindings/{name} |
  • PUT: Replace the named RoleBinding resource in the given namespace
  • PATCH: Partial update the named RoleBinding resource in the given namespace
  • DELETE: Delete the named RoleBinding resource in the given namespace
  • GET: Read the named RoleBinding resource in the given namespace
| - -### 4.3.2 Kubernetes Native Cluster Scoped Resource Objects - -The Kubernetes native cluster scoped resource objects are not included in the present version of the document. - -# Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|-------------------------------------------------------------------------------------------| -| 2022.03.28 | 01.00 | Final version 01.00 | -| 2022.07.26 | 02.00 | Final version 02.00 | -| 2023.03.24 | 03.00 | Final version 03.00 | -| 2023.07.31 | 04.00 | Final version 04.00 | -| 2024.03.19 | 04.00.01 | Implemented CRs ERI-0026, ERI-0028 | -| 2024.04.01 | 05.00 | Final version 05.00 | -| 2025.03.14 | 05.00.01 | Implemented CRs ERI-0060, ERI-0061, ERI-0062, ERI-0063, and additional rapporteur updates | -| 2025.03.19 | 05.00.02 | Updates made based on review comments | -| 2025.03.19 | 05.00.03 | Updates made based on review comments | -| 2025.03.26 | 06.00 | Final version 06.00 | -| 2025.11.20 | 06.00.01 | Implemented CR ERI-0087 | -| 2025.11.28 | 06.00.02 | Updates made based on review comments | -| 2025.11.28 | 07.00 | Final version 07.00 | \ No newline at end of file diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 022e87bb71372a7b6538215f2499319d726c6c51..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a9ff00a222f00dccfb1d05935f62869d2fc3b19ae53459cec9615bdf7fa2fce8 -size 3875 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 5573e6eb8e16d8b6dcd2ab04900f1bbadca2db92..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:07d85c8d8455dd1d432a4c876a9c5e5e32c2db3b125b5d1da4dc3597c9a89213 -size 3895 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 5573e6eb8e16d8b6dcd2ab04900f1bbadca2db92..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:07d85c8d8455dd1d432a4c876a9c5e5e32c2db3b125b5d1da4dc3597c9a89213 -size 3895 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index a37a1aebc218083615c26d03b53f8e0870607afe..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3d950b260aeb2e9d432bb2c494db8b8b9a1e4cfd00599de674c30540052bf1a1 -size 3901 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 4af59d8e8aa00d083b9a628182c7344a716c8921..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e2d947f60c9c61fa962852f91d7777af08a177160dd8c6167724ef5000c99755 -size 3958 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg deleted file mode 100644 index b4a840953db6f6c0da0c2d6f1b79dd08dd678e3a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c0dcfb8efb99dbb407def7461f8bd2724a9d5ed92f269548dfb08d7ad1eed14 -size 121643 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 8d4af7af6f97ed9d06f4202eedc3fb3669b12033..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3819c22741753857d090b72b5497407df3e246ab79514e2c140d5af1c8bcc7 -size 3887 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/562f471e8153729557e6a4ee6343c32c_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/562f471e8153729557e6a4ee6343c32c_img.jpg deleted file mode 100644 index 9eec7d8d0a30ab0d2b5a4b2ae43fa472c62eb851..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/562f471e8153729557e6a4ee6343c32c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:94b112b46ac9938574b154f66e3d2b1674b016c1efe576f8e1e301a6f716ce34 -size 130808 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/573c8f9e728e343b6864e1070c14b8cf_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/573c8f9e728e343b6864e1070c14b8cf_img.jpg deleted file mode 100644 index 412db0151532396dfb33fb8f57498bd31dd97e07..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/573c8f9e728e343b6864e1070c14b8cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:73aa3eb10ce113251b50bb09b08faf3183446fe1b7029eb64984bce73529f434 -size 25635 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index 41e3870380037e7c442e703303e85a207c149a9e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f7a7bba3177faf97967936ef45e1884f92ebc90d289a8773473b1ddd4c20ff99 -size 4017 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 022e87bb71372a7b6538215f2499319d726c6c51..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a9ff00a222f00dccfb1d05935f62869d2fc3b19ae53459cec9615bdf7fa2fce8 -size 3875 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 8d4af7af6f97ed9d06f4202eedc3fb3669b12033..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3819c22741753857d090b72b5497407df3e246ab79514e2c140d5af1c8bcc7 -size 3887 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/a738993919a50143787084ee7ce6e2f2_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/a738993919a50143787084ee7ce6e2f2_img.jpg deleted file mode 100644 index 90386d9e65f06526437aa5ec6cf715fa944f9dca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/a738993919a50143787084ee7ce6e2f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:53ded235b71175e5eb9bc9e01019f2d7b979fb81904b185dc443dedd9602979e -size 129723 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 5573e6eb8e16d8b6dcd2ab04900f1bbadca2db92..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:07d85c8d8455dd1d432a4c876a9c5e5e32c2db3b125b5d1da4dc3597c9a89213 -size 3895 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/ca5566458a134032dd860e88fdaa0d2b_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/ca5566458a134032dd860e88fdaa0d2b_img.jpg deleted file mode 100644 index faa68908824dd5b0b15d3e18f4f132b639d402c0..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/ca5566458a134032dd860e88fdaa0d2b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5210e5684dd63714a532a7f3d86acb5b4f74d73ee039bcb30a3ee2fe7a14fce6 -size 15148 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/d26959f4514c26ca19c3d6f00da85956_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/d26959f4514c26ca19c3d6f00da85956_img.jpg deleted file mode 100644 index 673a5d446c09d09a739dea562ebbd7b7b3d76ba3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/d26959f4514c26ca19c3d6f00da85956_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7aacb84d9878748ca862178d11644ebc7bb9bdd07cc9ba25ef38932d5722f6ff -size 194768 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 8d4af7af6f97ed9d06f4202eedc3fb3669b12033..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3819c22741753857d090b72b5497407df3e246ab79514e2c140d5af1c8bcc7 -size 3887 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 90e28037e184fb3c0c977a4ae14ef8a6a2ef6c5e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:df4e1f868ba79d5c03d4c5802d7959558fc1aa6137de60a1692cf3005d5f54b9 -size 3954 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 8d4af7af6f97ed9d06f4202eedc3fb3669b12033..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3819c22741753857d090b72b5497407df3e246ab79514e2c140d5af1c8bcc7 -size 3887 diff --git a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 17b401151b664884e232d208bb976526140222ae..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.O2DMS-INTERFACE-K8S-PROFILE-R005-v07.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d3c469867494b31e8fc3a7696dc9f40d64652859adfad5e087530f91cc5dd63d -size 3984 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/doc.md b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/doc.md deleted file mode 100644 index 7c2020813ac69fbaf481bb0bdba2d9a96dd1cf20..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/doc.md +++ /dev/null @@ -1,6930 +0,0 @@ - - -# **O-RAN Working Group 6 Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN** --- - -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 - -# Table of Contents - -- Table of Contents .....2 -- Table of Figures.....4 -- Foreword.....5 -- Modal verbs terminology .....5 -- 1. Scope.....6 - - 1.1 References..... 7 - - 1.2 Definition of Terms, Symbols and Abbreviations ..... 8 - - 1.2.1 Terms ..... 8 - - 1.2.2 Abbreviations..... 8 -- 2 Objectives.....9 - - 2.1 Context and Relationship to other WG6 and O-RAN Work..... 9 - - 2.2 Objectives of this Document..... 9 - - 2.3 Relationship to O-RAN OAM Architecture ..... 10 - - 2.4 Functional Description of O-RAN Cloud Infrastructure..... 10 -- 3 Orchestration Use Cases.....10 - - 3.1 O-Cloud Basic Use Cases ..... 11 - - 3.1.1 O-Cloud Pre-Deployment Processing Use Case ..... 12 - - 3.1.2 O-Cloud Platform Software Installation Use Case..... 14 - - 3.1.3 O-Cloud Registration and Initialization Use Case ..... 16 - - 3.1.4 O-Cloud Inventory Update Use Case ..... 18 - - 3.1.5 Hardware Infrastructure Scaling of O-Cloud Post Deployment..... 20 - - 3.1.6 O-Cloud Platform Software Update Use Case ..... 21 - - 3.1.7 Functional Status Query Use Case ..... 23 - - 3.1.8 Functional Status Update Use Case..... 26 - - 3.1.9 IMS Software Update Use Case..... 28 - - 3.1.10 DMS Software Update Use Case ..... 32 - - 3.1.11 Query Information Use Case..... 35 - - 3.2 Network Function Basic Use Cases ..... 39 - - 3.2.1 NF Deployment Instantiation ..... 39 - - 3.2.2 NF Deployment Scale Out ..... 41 - - 3.2.3 NF Deployment Scale In ..... 42 - - 3.2.4 NF Deployment Software Modification..... 44 - - 3.2.5 NF Deployment Termination ..... 46 - - 3.3 Near-RT RIC/xAPP Use Cases..... 48 - - 3.3.1 Configure O-Cloud for Near-RT RIC ..... 48 - - 3.3.2 Deploy xAPP in Near-RT RIC..... 50 - - 3.4 Multi-vendor network provisioning in a mixed PNF/VNF environment..... 53 - - 3.5 Reconfiguration of O-RAN Virtual Network Function(s) ..... 53 - - 3.5.1 High Level Description ..... 53 - - 3.5.2 Sequence Description..... 54 - - 3.5.3 UML sequence diagram ..... 55 - - 3.6 Recovery Use Cases..... 56 - - 3.6.1 Introduction..... 56 - - 3.6.2 Network Function Deployment Level Healing Use Case..... 57 - - 3.6.3 O-Cloud Node Level Healing Use Case..... 59 - - 3.6.4 O-Cloud Node Backup Use Cases..... 61 - - 3.7 Fault Use Cases..... 68 - - 3.7.1 Alarm Subscription Use Case..... 68 - -| | | | -|--------|--------------------------------------------------------------------------------------------------------------------|-----| -| 3.7.2 | Alarm Notification Use Case ..... | 70 | -| 3.7.3 | Alarm Query Use Case..... | 74 | -| 3.7.4 | IMS Alarm Subscription Query Use Case..... | 76 | -| 3.7.5 | IMS Alarm Subscription Delete Use Case ..... | 79 | -| 3.7.6 | Alarm Synchronization Use Case..... | 82 | -| 3.7.7 | Alarm Acknowledge/Clear Use Case..... | 84 | -| 3.7.8 | Log Query ..... | 88 | -| 3.7.9 | Alarm Dictionary Discovery Use Case ..... | 94 | -| 3.7.10 | Logging Configuration Use Case ..... | 97 | -| 3.7.11 | Alarm List Configuration Use Case ..... | 100 | -| 3.7.12 | Alarm Suppression Use Case ..... | 103 | -| 3.7.13 | Alarm Purge Use Case ..... | 111 | -| 3.7.14 | Log Discovery Use Case ..... | 117 | -| 3.8 | Performance Use Cases ..... | 119 | -| 3.8.1 | Performance Measurement Job Creation Use Case..... | 119 | -| 3.8.2 | Performance Management Subscription Use Case..... | 122 | -| 3.8.3 | Performance Measurement Event Notification Reporting Use Case..... | 125 | -| 3.8.4 | Performance Measurement Streaming Reporting Use Case..... | 129 | -| 3.8.5 | Performance Measurement File Reporting Use Case ..... | 137 | -| 3.8.6 | Performance Measurement Job Query Use Case ..... | 142 | -| 3.8.7 | Performance Measurement Job Delete Use Case ..... | 144 | -| 3.8.8 | Performance Measurement Job Update Use Case ..... | 148 | -| 3.8.9 | Performance Measurement Job Suspend Use Case..... | 152 | -| 3.8.10 | Performance Measurement Job Resume Use Case..... | 156 | -| 3.8.11 | Performance Management Dictionary Discovery IMS Use Case ..... | 159 | -| 3.8.12 | Performance Management Subscription Query (IMS) Use Case ..... | 163 | -| 3.8.13 | Performance Management Subscription Update (IMS) Use Case..... | 167 | -| 3.8.14 | Performance Management Subscription Delete (IMS) Use Case..... | 170 | -| 3.8.15 | Performance Management Configuration Use Case ..... | 174 | -| 3.9 | VLAN Management Use Cases ..... | 177 | -| 3.9.1 | VLAN Allocation Use Case ..... | 177 | -| 3.9.2 | VLAN Deallocation Use Case ..... | 179 | -| 3.10 | Network Slicing Use Cases..... | 181 | -| 3.10.1 | Network Slice Creation Use Case ..... | 181 | -| 3.10.2 | Network Slice Deletion Use Case ..... | 185 | -| 3.11 | Provisioning Use Cases ..... | 186 | -| 3.11.1 | Network Resource Provisioning for base O-Cloud Site Network Use Case ..... | 186 | -| 3.11.2 | Create O-Cloud Node Cluster Use Cases..... | 188 | -| 3.11.3 | Delete O-Cloud Node Cluster Use Cases..... | 199 | -| 3.11.4 | Update O-Cloud Node Cluster Use Cases..... | 204 | -| 3.11.5 | Provisioning of Infrastructure Resources using Managed Infrastructure Template ..... | 213 | -| 3.11.6 | Networking Infrastructure Provisioning Use Cases ..... | 222 | -| 3.11.7 | O-Cloud Managed Infrastructure Template Discovery Use Case ..... | 226 | -| 3.11.8 | Provisioning of an O-Cloud Node Cluster and Infrastructure Resources using a Managed Infrastructure Template ..... | 228 | -| 3.12 | Resource Optimization Use Cases ..... | 238 | -| 3.12.1 | Introduction ..... | 238 | -| 3.12.2 | O-Cloud Drain Node Use Case ..... | 238 | -| 3.12.3 | O-Cloud Cordon and Uncordon Use Case ..... | 240 | -| 3.13 | Heartbeat Monitoring Use Cases ..... | 244 | -| 3.13.1 | Heartbeat Subscription Use Case ..... | 244 | -| 4 | Orchestration Requirements ..... | 247 | -| 4.1 | General Requirements..... | 247 | -| 4.2 | Orchestration Requirements Relating to O1 ..... | 249 | -| 4.3 | Orchestration Requirements Relating to O2 ..... | 250 | -| 4.4 | Requirements Relating to NF Deployment Descriptor ..... | 259 | - -| | | -|----------------------------------------------------------------------|-----| -| Annex A (Informative): Terminology Used in O-Cloud Requirements..... | 260 | -| Annex (Informative): Change History..... | 261 | - -# Table of Figures - -| | | -|-----------------------------------------------------------------------------------------------------|-----| -| Figure 2-1: Relationship of this Document to Scenario Documents and O-RAN Management Documents..... | 9 | -| Figure 2-2: O-RAN Architecture and Management Interfaces ..... | 10 | -| Figure 3-1: O-Cloud Pre-Deployment Processing..... | 14 | -| Figure 3-2: Platform Software Installation ..... | 16 | -| Figure 3-3: O-Cloud Deployment Processing..... | 18 | -| Figure 3-4: O-Cloud Inventory Update..... | 19 | -| Figure 3-5: Hardware Infrastructure Scaling ..... | 21 | -| Figure 3-6: O-Cloud Platform Software Update..... | 23 | -| Figure 3-7: O-Cloud Functional Status Query..... | 26 | -| Figure 3-8: O-Cloud Functional Status Update ..... | 28 | -| Figure 3-9: IMS Software Update ..... | 31 | -| Figure 3-10: DMS Software Update..... | 35 | -| Figure 3-11: Query Information ..... | 38 | -| Figure 3-12: NF Deployment Instantiation..... | 40 | -| Figure 3-13: NF Deployment Scale Out ..... | 42 | -| Figure 3-14: NF Deployment Scale In..... | 44 | -| Figure 3-15: NF Deployment Software Modification..... | 46 | -| Figure 3-16: NF Deployment Termination..... | 48 | -| Figure 3-17: Configure O-Cloud for Near-RT RIC ..... | 50 | -| Figure 3-18: Deploy xAPP ..... | 53 | -| Figure 3-19: Reconfiguration..... | 55 | -| Figure 3-20: Remote System Reset of legacy xNB by OSS ..... | 57 | -| Figure 3-21: NF Deployment level recovery ..... | 59 | -| Figure 3-22: O-Cloud Node level recovery ..... | 61 | -| Figure 3-23: O-Cloud Node Backup Creation..... | 64 | -| Figure 3-24: Criteria-based O-Cloud Node Backup Creation..... | 66 | -| Figure 3-25: O-Cloud Node Backup Query..... | 67 | -| Figure 3-26: Alarm Subscription ..... | 70 | -| Figure 3-27: Alarm Notification ..... | 73 | -| Figure 3-28: Alarm Query ..... | 76 | -| Figure 3-29: IMS Alarm Subscription Query ..... | 79 | -| Figure 3-30: IMS Alarm Subscription Deletion ..... | 81 | -| Figure 3-31: Alarm Synchronization ..... | 84 | -| Figure 3-32: Alarm Acknowledge/Clear ..... | 88 | -| Figure 3-33: Log Query ..... | 93 | -| Figure 3-34: Alarm Dictionary Discovery..... | 97 | -| Figure 3-35: Logging Configuration..... | 100 | -| Figure 3-36: Alarm List Configuration..... | 103 | -| Figure 3-37: Operator/SMO-Initiated Alarm Suppression ..... | 108 | -| Figure 3-38: IMS-Initiated Alarm Suppression ..... | 111 | -| Figure 3-39: Alarm Purge ..... | 116 | -| Figure 3-40: Discovery O-Cloud Logs ..... | 119 | -| Figure 3-41: PM Job Creation ..... | 121 | -| Figure 3-42: PM Data and PM Subscription..... | 122 | -| Figure 3-43: PM Subscription..... | 125 | -| Figure 3-44: Performance Measurement Event Notification Reporting ..... | 129 | -| Figure 3-45: Performance Measurement Streaming Reporting for WebSocket Based Streaming ..... | 134 | -| Figure 3-46: Performance Measurement Streaming Reporting for Message Bus Based Streaming..... | 137 | -| Figure 3-47: Performance Measurement File Reporting ..... | 141 | -| Figure 3-48: PM Job Query ..... | 144 | -| Figure 3-49: PM Job Delete..... | 148 | - -| | | -|----------------------------------------------------------------------------------------------------------------|-----| -| Figure 3-50: PM Job Update..... | 152 | -| Figure 3-51: PM Job Suspend..... | 156 | -| Figure 3-52: PM Job Resume ..... | 159 | -| Figure 3-53: PM Dictionary Discovery ..... | 163 | -| Figure 3-54: PM Subscription Query..... | 166 | -| Figure 3-55: PM Subscription Update ..... | 170 | -| Figure 3-56: PM Subscription Delete ..... | 173 | -| Figure 3-57: PM Configuration ..... | 177 | -| Figure 3-58: VLAN Allocation..... | 179 | -| Figure 3-59: VLAN Deallocation ..... | 180 | -| Figure 3-60: Network Slice Creation ..... | 184 | -| Figure 3-61: Network Slice Deletion..... | 186 | -| Figure 3-62: Network Resource Provisioning for base O-Cloud Site Network..... | 188 | -| Figure 3-63: Create Kubernetes (K8s) Cluster ..... | 193 | -| Figure 3-64: Create O-Cloud Node Cluster using Managed Infrastructure Template ..... | 198 | -| Figure 3-65: Delete Kubernetes (K8s) Cluster ..... | 201 | -| Figure 3-66: Delete O-Cloud Node Cluster Created Using Managed Infrastructure Template ..... | 204 | -| Figure 3-67: Update O-Cloud Node Cluster ..... | 208 | -| Figure 3-68: Update O-Cloud Node Cluster using Managed Infrastructure Template ..... | 212 | -| Figure 3-69: Create Infrastructure Resources using Managed Infrastructure Template ..... | 217 | -| Figure 3-70: Update Infrastructure Resources using Managed Infrastructure Template ..... | 221 | -| Figure 3-71: Basic connectivity scenarios ..... | 222 | -| Figure 3-72: Examples of Networking Infrastructure Provisioning..... | 223 | -| Figure 3-73: Create Networking Infrastructure across O-Cloud Sites with a Managed Infrastructure Template..... | 226 | -| Figure 3-74: Discovery O-Cloud Managed Infrastructure Templates ..... | 228 | -| Figure 3-75: Create a Node Cluster and Infrastructure Resources using MIT..... | 233 | -| Figure 3-76: Update a Node Cluster and Infrastructure Resources using MIT..... | 238 | -| Figure 3-77: O-Cloud Node Draining..... | 240 | -| Figure 3-78: Node Cordon and Uncordon ..... | 243 | -| Figure 3-79: Heartbeat Subscription..... | 246 | - -# Foreword - -This Technical Specification (TS) has been produced by O-RAN Alliance. - -# 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 contents of the present document are 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. - -The present document specifies cloudification and orchestration use cases and requirements for O-RAN. - -## 1.1 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. - -NOTE: While any hyperlinks included in this clause were valid at the time of publication, O-RAN cannot guarantee their long term validity. - -- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in Release 16. - -The following documents contain provisions which, through reference in this text, constitute provisions of this specification. - -- [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". -- [2] ETSI GS NFV 003 V1.4.1, "Terminology for Main Concepts in NFV" -- [3] O-RAN-WG1-O-RAN-Architecture-Description, "O-RAN Architecture Description" -- [4] O-RAN White Paper: "O-RAN: Towards an Open and Smart RAN", October 2018. -- [5] O-RAN.WG10.OAM-Architecture: "O-RAN Operations and Maintenance Architecture". -- [6] O-RAN.WG10.O1-Interface: "O-RAN Operations and Maintenance Interface Specification". -- [7] O-RAN-WG6.CAD: "Cloud Architecture and Deployment Scenarios for O-RAN Virtualized RAN". -- [8] O-RAN-WG2.UCR, "Use Case and Requirements Specification" -- [9] O-RAN-WG6.O2-GA&P: "O2 General Aspects and Principles" -- [10] O-RAN.WG3.RICARCH: "Near-RT RIC Architecture" -- [11] O-RAN-WG6.AAL-GAnP: "O-RAN O-Cloud Acceleration Abstraction Layer" -- [12] ETSI GS NFV-SOL 015 V1.2.1 (2020-12): "Specification of Patterns and Conventions for RESTful NFV-MANO APIs" -- [13] ETSI 3GPP TS 29.501 V16.5.0 (2020-09): "Principles and Guidelines for Services Definition; Stage 3" -- [14] O-RAN.WG1.Slicing-Architecture: "O-RAN Working Group 1 Slicing Architecture" -- [15] ITU-T Recommendation X.731, "Information technology - Open Systems Interconnection - Systems management: State management function", January 1992 -- [16] ETSI GS NFV-IFA 013 V4.2.2 (2021-06): "Network Functions Virtualisation (NFV) Release 4; Management and Orchestration; Os-Ma-Nfvo reference point – Interface and Information Model Specification" -- [17] O-RAN.WG6.O2IMS-INTERFACE: "O-RAN O2ims Interface Specification" -- [18] O-RAN.SFG.O-RAN-Security-Requirements-Specifications: "O-RAN Security Requirements Specification" -- [19] ETSI GS NFV-IFA 032 V4.3.1 (2022-06): "Network Functions Virtualisation (NFV) Release 4; Management and Orchestration; Interface and Information Model Specification for Multi-Site Connectivity Services" -- [20] 3GPP TS 28.622 "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)" -- [21] IETF RFC 5424 "The Syslog Protocol", March 2009 -- [22] IETF RFC 8632 "A YANG Data Model for Alarm Management" September 2019 ISSN: 2070-1721 - -- [23] O-RAN WG6 “O-Cloud Information Model” -- [24] ETSI GS NFV-SOL 003: Network Functions Virtualisation (NFV) Release 5; Protocols and Data Models; RESTful protocols specification for the Or-Vnfm Reference Point -- [25] 3GPP TS28.532: “Management and orchestration; Generic management services” -- [26] 3GPP TS23.501: “System architecture for the 5G System (5GS); Stage 2” -- [27] 3GPP TS23.502: “Procedures for the 5G System (5GS); Stage 2” -- [28] ETSI IFA-008: “Management and Orchestration; Ve-Vnfm reference point -Interface and Information Model Specification” - -## 1.2 Definition of Terms, Symbols and Abbreviations - -### 1.2.1 Terms - -For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. - -| | | -|------------------|-------------------------------------------------------------------------------------------------| -| Cloudified NF | A RAN Network Function software that is deployed in the O-Cloud via one or more NF Deployments. | -| NF Deployment | A software deployment on O-Cloud resources that realizes all or part of a Cloudified NF. | -| Managed Function | Refer to the 3GPP TS28.622 [20]. | -| Managed Element | Refer to the 3GPP TS28.622 [20]. | - -### 1.2.2 Abbreviations - -For the purposes of this document, the abbreviations given in 3GPP TR 21.905 [1] 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 [1]. - -| | | -|---------|-------------------------------------------------| -| 3GPP | Third Generation Partnership Project | -| 5G | Fifth-Generation Mobile Communications | -| CNF | Containerized Network Function | -| DMS | O-Cloud Deployment Management Services | -| FOCOM | Federated O-Cloud Orchestration & Management | -| IM | Information Model | -| IMS | O-Cloud Infrastructure Management Services | -| LCM | Life Cycle Management | -| NF | Network Function | -| NFO | Network Function Orchestration | -| NFVI | Network Function Virtualization Infrastructure | -| O-CU | O-RAN Central Unit as defined by O-RAN ALLIANCE | -| O-CU-CP | O-CU Control Plane | -| O-CU-UP | O-CU User Plane | -| O-DU | O-RAN Distributed Unit (uses Lower-level Split) | -| O-RU | O-RAN Radio Unit | -| PM Job | Performance Measurement Job | -| PNF | Physical Network Function | -| RAN | Radio Access Network | -| SMO | Service Management and Orchestration Framework | -| VIM | Virtual Infrastructure Manager | -| VNF | Virtual Network Function | - - - -This document defines end-to-end use cases in clause 3 and specifies OAM-related general and interface requirements in clause 4 to support the O-RAN architecture. - -## 2.3 Relationship to O-RAN OAM Architecture - -This document follows the high-level O-RAN OAM Architecture defined in O-RAN WG10. The high-level OAM Architecture is given below in Figure 2-2 as taken from [3] but focusing on OAM interfaces O1 and O2 only. - -![Figure 2-2: O-RAN Architecture and Management Interfaces. The diagram shows the Service Management and Orchestration Framework (SMO) at the top, connected to an External system providing enrichment data to the SMO. The SMO contains a Non-RT RIC. Below the SMO is the O-RAN Network Functions block, which contains a Near-RT RIC. The Near-RT RIC is connected to the O-Cloud and the O-RU. The O-Cloud is connected to the O-RU. The O-RU is connected to the NG-Core. The NG-Core is connected to the O-RAN Network Functions. The O-RAN Network Functions are connected to the O-Cloud via an O-Cloud Notification interface. The O-RAN Network Functions are connected to the O-RU via an Open Fronthaul M-Plane interface. The O-RAN Network Functions are connected to the NG-Core via an NG interface. The O-RAN Network Functions are connected to the SMO via O1 and O2 interfaces. The Non-RT RIC is connected to the Near-RT RIC via an A1 interface. The legend indicates that O-RAN Defined Interfaces are shown in purple, 3GPP Defined Interfaces are shown in orange, and Interfaces out of scope for O-RAN are shown in black.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) - -Figure 2-2: O-RAN Architecture and Management Interfaces. The diagram shows the Service Management and Orchestration Framework (SMO) at the top, connected to an External system providing enrichment data to the SMO. The SMO contains a Non-RT RIC. Below the SMO is the O-RAN Network Functions block, which contains a Near-RT RIC. The Near-RT RIC is connected to the O-Cloud and the O-RU. The O-Cloud is connected to the O-RU. The O-RU is connected to the NG-Core. The NG-Core is connected to the O-RAN Network Functions. The O-RAN Network Functions are connected to the O-Cloud via an O-Cloud Notification interface. The O-RAN Network Functions are connected to the O-RU via an Open Fronthaul M-Plane interface. The O-RAN Network Functions are connected to the NG-Core via an NG interface. The O-RAN Network Functions are connected to the SMO via O1 and O2 interfaces. The Non-RT RIC is connected to the Near-RT RIC via an A1 interface. The legend indicates that O-RAN Defined Interfaces are shown in purple, 3GPP Defined Interfaces are shown in orange, and Interfaces out of scope for O-RAN are shown in black. - -Figure 2-2: O-RAN Architecture and Management Interfaces - -The Use Cases in this document describe the use of the O1 and O2 interfaces for orchestration within an O-RAN. - -## 2.4 Functional Description of O-RAN Cloud Infrastructure - -This document uses terminology for O-Cloud components taken from the Cloud Architecture and Deployment Scenarios for O-RAN virtualized RAN Specification [7], and O2 General Aspects and Principles [9], including the O-Cloud Node, IMS and DMS. - -# 3 Orchestration Use Cases - -These Use Cases focus on the private cloud case where the cloud is managed by the operator. Applicability to the public cloud case is for further study. - -The present document provides Use Cases related to Network Function, O-Cloud, SMO and Near-RT RIC. At a high level, the use cases cover similar functionality/scope applicable to O-Cloud and O-Cloud-based Network Functions, such as: - -- Instantiation and deployment of O-Cloud and Network Functions -- Updating of O-Cloud and Network Functions -- Scaling of O-Cloud and Network Functions - -Instantiation and deployment of O-Cloud in the O-RAN is triggered by the “Service Request” towards SMO and a sequential process involving the use cases described in clauses 3.1.1, 3.1.2, 3.1.3. The instantiation of Network Function is described in clause 3.2.1. - -Updating of O-Cloud and Network Function can be performed independently and be triggered by the SMO as described in clauses 3.1.6 and 3.2.4, respectively. - -Scaling of Network Function is triggered by the SMO as described in clause 3.2.2 (for the scaling out) and clause 3.2.3 (for the scaling in). Scaling of O-Cloud is described in clause 3.1.5. - -The roles and actors described in Table 3-1 are used in the use case descriptions. - -**Table 3-1: Description of actors and roles used in the use cases.** - -| Actor/Role | Description | -|------------------------------------------|-----------------------------------------------------------------------------------| -| RAN Planner | Operator planning area deployment of RAN. | -| Cloud Planner | Operator planning O-Cloud instance. | -| Cloud Installation Project Manager | Operator designing each O-Cloud instance. | -| O-Cloud Vendor | Provider of the O-Cloud software. | -| Network Function Install Project Manager | Operator designing each Network Function instance. | -| Network operator | Operator operating operator's network. | -| Cloud Installer | Operator installing O-Cloud Node | -| Cloud Maintainer | Operator that operates and manages O-Cloud Nodes | -| SMO | See [3]. SMO is further divided into FOCOM, NFO and OAM Functions. | -| IMS | See [9] | -| DMS | See [9] | -| O-Cloud Node(s) | See [7] | -| Near-RT RIC | See [3] | -| xAPP | See [10] | -| Network Function (Application) | Network Function that is instantiated and managed. | -| Network Controller | Entity responsible for managing, controlling and setting up network connectivity. | - -NOTE 1: The UML® Sequence Diagrams in the use cases follow the template defined in the OAM Architecture [5] Appendix B. An arrow with dashed lines is used to indicate a synchronous return message. - -NOTE 2: UML® is a registered trademark of the Object Management Group, in the United States and other countries. O-RAN is not affiliated with, endorsed or sponsored by the Object Management Group. - -There might be various situations where the IMS software or its data store itself has become corrupt. In this situation, the IMS as a producer entity might not be able to perform its functions over the O2ims interface. This problem applies to all the following use cases. Ways or strategies of how to recover or react to a non-functional IMS will be covered in the Loss of O2ims of Management Link Use Case [NOTE 3: use case to be added in future]. - -For all the following use cases, there are common messaging framework errors and exceptions that can occur. For example, if a response message is never received because of a network outage, it is expected that eventually the system will time out. These standard code responses will apply to all the following use cases and are not mentioned explicitly as separate exceptions within the use cases. - -For all the following use cases, it is possible that the IMS is processing a request while another new request operating on the same objects arrives from the same or another authorized entity. This is a race condition. A race condition can occur either at the management level (SMO), or at the transaction level (O2ims or O2dms Interface). For example, a PM subscription query request is being processed by the IMS and while the IMS is processing that operation, a new PM subscription query request arrives. NOTE 4: This would be resolved in the management implementation (SMO) or in the stage 3 (O2ims or O2dms interface) implementation. Some possible solution implementations are a semaphore flag (managing entity side) that only allows one entity to access the resources at a time. Another possible implementation is a “currency” field that would be a token mechanism that can be used to identify transactions. - -## 3.1 O-Cloud Basic Use Cases - -Cloud Platforms are identified in order for the SMO to take advantage of them. In traditional data center clouds these have been manually or externally added to the SMO for homing of NF deployments since the numbers are typically low from hundreds of cloud regions to even several thousand. However, in the case of edge clouds the number of deployments scale into the 10K to 100K range, in which case this process needs to more closely resemble the way RAN elements are “discovered”. Even in this latter case, the rationale for edge clouds is for specific performance requirements, therefore not all edge clouds are equivalent. This Use Case describes how the SMO discovers and manages a cloud implementation that meets the O-RAN specifications as described in the Cloud Architecture and - -Deployment Scenarios for O-RAN virtualized RAN [7]. Such a cloud instance is generally referred to as an O-Cloud which is comprised of O-Cloud Nodes (Compute, Storage, and Network), dedicated resources for the O-Cloud. - -This group of Use Cases includes the following: - -- Pre-processing where before the O-Cloud is activated the SMO is configured with the identity of the O-Cloud so that registration can be done -- Basic platform software installation by the SMO and IMS -- O-Cloud deployment processing where the O-Cloud registers with SMO and has its identity and software version checked -- Capabilities Exchange where the SMO either queries for O-Cloud capabilities or is notified autonomously that there has been a change in O-Cloud capabilities -- O-Cloud hardware upgrade where a new O-Cloud Node is added -- O-Cloud software update where the platform software version is upgraded or downgraded in the O-Cloud - -The end result of the group of use cases is an active O-Cloud registered with SMO and ready for the deployment of Network Functions. - -NOTE 1: Where Personnel are shown as part of the Use Case, the roles and terminology used are given for purposes of illustration only. - -NOTE 2: Regarding security and authentication of an entity that interacts with the IMS, which typically the FOCOM in the SMO, the topic of security and authentication will be addressed by the O-RAN security focus group (SFG). A common solution which affects all the following use cases will be studied and specified by the SFG. This is currently FFS. When these are better understood, each of the following use cases will be updated to reflect the security & authentication requirements. - -### 3.1.1 O-Cloud Pre-Deployment Processing Use Case - -#### 3.1.1.1 High Level Description - -This Use Case describes the SMO being configured to add an O-Cloud into its inventory prior to the O-Cloud itself being activated and attempting to register with the SMO. - -The Use Case assumes that this will be part of a sequence of “Service Requests” to the SMO, one for the deployment of the O-Cloud and one for the Network Function(s) that will run on that O-Cloud instance. In the latter request, information is assumed to be present on the NF Service Requests to identify the O-Cloud instance, as described in a later Use Case. - -NOTE: In some cases, there could potentially be a single “Service Request” to SMO containing information about both the O-Cloud and Network Function(s) that will run on that O-Cloud instance, but this is not covered in the Use Case. - -#### 3.1.1.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | SMO creates an object in its Inventory and generates Global O-Cloud ID that is provided as input to the O-Cloud genesis and used in the O-Cloud Registration (see 3.1.3 O-Cloud Registration and Initialization Use Case). | 3.1.3 | -| Actors and Roles | RAN Planner
Cloud Planner
Cloud Installation Project Manager
SMO | | -| Assumptions | | | -| Preconditions | 1) SMO is available.
2) The cloud blueprint (see Annex A of the present specification) is available to the Cloud Installation Project Manager, which has been created based on the requirements from the RAN Buildout Plan of Record. | | -| Begins when | Decision to deploy an O-Cloud to support RAN growth/coverage has been made jointly by the RAN Planner and the Cloud Planner | | -| Step 1 (M) | Cloud Installation Project Manager issues a “service request” to the SMO to update its Inventory, i.e., indicate that a new O-Cloud is to be inventoried. | | -| Step 2 (M) | SMO generates Global O-Cloud ID, and creates an inventory record with the Global O-Cloud ID. The Global O-Cloud ID represents a globally unique identifier for the new O-Cloud instance by the SMO and for handling the registration process. | | -| Step 3 (M) | SMO confirms update to Cloud Installation Project Manager. | | -| Ends when | SMO has updated inventory with the Global O-Cloud ID of the planned O-Cloud. | | -| Exceptions | None identified. | | -| Post Conditions | SMO has created an inventory record with the Global O-Cloud ID for the planned O-Cloud. | | -| Traceability | REQ-ORC-GEN1; REQ-ORC-GEN2 | | - -#### 3.1.1.3 UML sequence diagram - -![Sequence diagram for O-Cloud Pre-Deployment Processing. Lifelines: RAN Planner, Cloud Planner, Cloud Installation Project Manager (Personnel), and Service Management & Orchestration Framework. The process involves sending a RAN Buildout Plan of Record and a Cloud build request (cloud blueprint) to the framework, followed by a 'Cloud Pre-Install' phase. The framework then sends a service request [01], creates an object in inventory and generates a Global O-Cloud ID [02], and confirms the inventory update [03] to the Cloud Installation Project Manager, ending the use case.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) - -``` - -sequenceDiagram - actor RAN Planner - actor Cloud Planner - actor CIPM as Cloud Installation Project Manager - participant SMO as Service Management & Orchestration Framework - - Note right of CIPM: RAN Buildout Plan of Record - Note right of CIPM: Cloud build request (cloud blueprint) - - Note over RAN Planner, Cloud Planner, CIPM: Cloud Pre-Install - - CIPM->>SMO: [01] Service request - SMO-->>SMO: [02] Create object in Inventory and generate Global O-Cloud ID - SMO-->>CIPM: [03] Confirm Inventory update - - Note over RAN Planner, Cloud Planner, CIPM: End Use Case - -``` - -Sequence diagram for O-Cloud Pre-Deployment Processing. Lifelines: RAN Planner, Cloud Planner, Cloud Installation Project Manager (Personnel), and Service Management & Orchestration Framework. The process involves sending a RAN Buildout Plan of Record and a Cloud build request (cloud blueprint) to the framework, followed by a 'Cloud Pre-Install' phase. The framework then sends a service request [01], creates an object in inventory and generates a Global O-Cloud ID [02], and confirms the inventory update [03] to the Cloud Installation Project Manager, ending the use case. - -Figure 3-1: O-Cloud Pre-Deployment Processing - -### 3.1.2 O-Cloud Platform Software Installation Use Case - -#### 3.1.2.1 High Level Description - -The Use Case describes the deployment of the O-Cloud and installation of O-Cloud Platform Software on an O-Cloud Node. The Cloud Installer begins the installation by installing the hardware for the O-Cloud Nodes and notifying SMO to begin Cloud Build. SMO then loads O-Cloud Platform Software on a first O-Cloud Node in the O-Cloud, which then brings up any additional O-Cloud Nodes in the O-Cloud. - -During activation of other O-Cloud Nodes, the O-Cloud Management Plane activates IMS, which then notifies the SMO of its availability. The SMO then sends IMS the required set of O-Cloud Node Roles and Personalities to support. The IMS loads necessary basic software for O-Cloud onto the other O-Cloud Nodes and also configures and activates one or more DMSs. - -It is assumed that hardware to deploy O-Cloud Management Software is pre-configured and ready. Network connectivity between O-Cloud network gateways(s) and SMO is assumed to be ready, as per the “O-Cloud Pre-Deployment Processing Use Case” described in clause 3.1.1. - -For O-Cloud resources managed by a Hardware Accelerator Manager (HAM), which is defined in O-RAN WG6.AAL-GaNP [11], Clause 3.1, the IMS informs the HAM what SW artifacts to be installed and activated for HWA resources managed by that HAM. The HAM is responsible for obtaining, installing and activating the SW artifacts. For further information, see O-RAN WG6.AAL-GaNP [11], Clause 4.2.1. - -#### 3.1.2.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <> | -|----------------|---------------------------|----------| -|----------------|---------------------------|----------| - -| | | Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| Goal | The O-Cloud is initialized and communicating with the SMO. | | -| Actors and Roles | Cloud Installation Project Manager:
Cloud Installer:
SMO: FOCOM
IMS
DMS
O-Cloud Node
Network Controller | | -| Assumptions | 1) Through some means (e.g., manual installation), an application will be loaded to the O-Cloud, that application at minimum having the following abilities:
  1. Having knowledge of its own O-Cloud ID, IP address, the IP address endpoint or url of the SMO and any necessary security keys or passwords for communication using O2.
  2. Being able to communicate at least the IMS Address endpoint and Cloud Id of this O-Cloud instance.
  3. Being able to generate a registration event to the SMO including its Cloud ID.
  4. Being able to process requests to load SW onto an O-Cloud Node in the O-Cloud
| | -| Preconditions | 1) SMO is available
2) Network connectivity exists between the O-Cloud and SMO
3) SMO has basic software for the O-Cloud available for download
4) SMO holds inventory that includes the O-Cloud ID for the O-Cloud. | | -| Begins when | Work order triggers O-Cloud installation processing. | | -| Step 1, 2 (M) | Cloud Installation Project Manager generates a work order to the Cloud Installer for the new O-Cloud;
Cloud Installer installs the new O-Cloud Nodes, sets up connectivity of the O-Cloud Nodes to the O-Cloud network gateway(s) (e.g., with Network Controller) and responds to Cloud Installation Project Manager | | -| Step 3 (M) | Cloud Installer notifies SMO of the new O-Cloud Build. (NOTE 1) | | -| Step 4 (M) | SMO loads basic software for O-Cloud on the first O-Cloud Node;
First O-Cloud Node then brings up additional O-Cloud Nodes in the O-Cloud including IMS. (NOTE 2) | | -| Step 5 (O) | If network connectivity has not been established between O-Cloud Nodes and with transport network via O-Cloud Gateway, IMS performs the network resource provisioning for the base O-Cloud Site Network, realized on the O-Cloud Site Network Fabric, providing infrastructure-level network connectivity for the O-Cloud Node(s), which means the configuration of O-Cloud Node(s) and if necessary, configuration of the O-Cloud Network Fabric for L2 level connectivity and O-Cloud Gateway for L3 level connectivity. (NOTE 3) | | -| Step 6 (M) | IMS loads basic O-Cloud software onto the other O-Cloud Nodes, activates DMS and creates SW inventory. | | -| Ends when | O-Cloud has IMS and DMS activated and has created SW inventory. | | -| Exceptions | None identified | | -| Post Conditions | O-Cloud software has been installed. In addition, network resources for the O-Cloud Site Network providing infrastructure-level connectivity have been provisioned and network connectivity has been established between O-Cloud Nodes and with transport network via O-Cloud Gateway.

O-Cloud ready to register with SMO, with information to connect to SMO and activated IMS with SW inventory and activated DMS(s). | | -| Traceability | REQ-ORC-GEN3; REQ-ORC-GEN4; REQ-ORC-GEN5; REQ-ORC-O2-1; REQ-ORC-O2-2; REQ-ORC-O2-45; REQ-ORC-O2-46 | | - -- NOTE 1: Cloud Installer shall provide SMO with information to connect with the new O-Cloud Build, including the target O-Cloud Node in the O-Cloud and identity of the basic software for O-Cloud to be loaded on the O-Cloud -- NOTE 2: Details of how the IMS and other O-Cloud Nodes are brought up are specific to the O-Cloud implementation. -- NOTE 3: Network resource provisioning for the O-Cloud Site Network can be also performed independently as described in clause 3.11.1. - -#### 3.1.2.3 UML sequence diagram - -![UML sequence diagram for Platform Software Installation. Lifelines: Personnel (Cloud Installation Project Manager, Cloud Installer), Service Management & Orchestration Framework (FOCOM), O-Cloud (IMS). The sequence includes Cloud HW Infrastructure Installation, Cloud Software Install, and End Use Case phases. It details the interaction between personnel, FOCOM, and IMS to install and configure the O-Cloud.](16152cf1d84aea10848758f51a91ff6a_img.jpg) - -``` - -sequenceDiagram - actor PM as Cloud Installation Project Manager - actor CI as Cloud Installer - participant FOCOM as Service Management & Orchestration Framework - participant IMS as O-Cloud - - Note right of FOCOM: Cloud HW Infrastructure Installation - PM->>CI: 1 Work order (Cloud Info) - Note right of CI: Installer Installs new O-Cloud - CI->>PM: 2 Inform about O-Cloud been installed - - Note right of FOCOM: Cloud Software Install - CI->>FOCOM: 3 Inform about O-Cloud Build - FOCOM->>IMS: 4 Load first O-Cloud Node - Note right of IMS: First O-Cloud Node in the O-Cloud brings up additional O-Cloud Nodes. - Note right of IMS: O-Cloud Node requests software image boot from IMS. IMS sends image load to O-Cloud Node. O-Cloud Node notifies when booted. IMS sends config to O-Cloud Node. - - opt If network resource for base O-Cloud Site Network has not been provisioned - IMS->>FOCOM: 5 Perform base O-Cloud Site Network provisioning - Note right of FOCOM: IMS performs the O-Cloud Site NW provisioning to enable O-Cloud Site Network Fabric resources for the base O-Cloud Site Network and if necessary, specific configuration on the O-Cloud Site Network Fabric and O-Cloud Site Gateway. - end - - FOCOM->>IMS: 6 IMS configures and activates DMS and creates SW inventory - - Note right of FOCOM: End Use Case - -``` - -UML sequence diagram for Platform Software Installation. Lifelines: Personnel (Cloud Installation Project Manager, Cloud Installer), Service Management & Orchestration Framework (FOCOM), O-Cloud (IMS). The sequence includes Cloud HW Infrastructure Installation, Cloud Software Install, and End Use Case phases. It details the interaction between personnel, FOCOM, and IMS to install and configure the O-Cloud. - -Figure 3-2: Platform Software Installation - -### 3.1.3 O-Cloud Registration and Initialization Use Case - -#### 3.1.3.1 High Level Description - -This Use Case describes the sequence for registration and initialization of the newly deployed O-Cloud. The SMO queries the O-Cloud for its SW inventory, checks to see if this requires any updates, configures the O-Cloud and queries the O-Cloud for available DMS. Following this sequence, the O-Cloud is available for NF deployments to be instantiated. - -#### 3.1.3.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | O-Cloud is initialized and registered with the SMO, ready for NF deployments to be instantiated. | | -| Actors and Roles | SMO: FOCOM
IMS
DMS
O-Cloud Node | | -| Assumptions | None | | -| Preconditions | 1) SMO and O-Cloud IMS are available
2) Network connectivity exists between O-Cloud and SMO and between all nodes of O-Cloud. All O-cloud nodes are preconfigured for the O-Cloud.
3) SMO has been configured with O-Cloud ID in its inventory and is ready for O-Cloud registration | | -| Begins when | IMS and DMS are ready to register O-Cloud to accept new NF deployments | | -| Step 1 (M) | IMS initiates the O2 O-Cloud Registration Process using O2ims services (for details see [9]) | | -| Step 2-3 (M) | SMO queries IMS for current SW inventory, and IMS responds with SW inventory data. | | -| Step 4-5 (ALT) | SMO checks SW inventory.
1) If SW inventory does not match required inventory:
a. SMO executes software update (see clauses 3.1.6, 3.1.9 and 3.1.10)
b. IMS installs new software, activates and notifies SMO it is available
c. return to Step 2
2) If SW inventory matches the required inventory, continue to next Step | | -| Step 6 (M) | SMO configures O-Cloud using O2 | | -| Step 7-9 (M) | SMO queries O-Cloud to discover and Inventory new DMS using O2 Infrastructure Inventory Services [9]
O-Cloud returns list of new O-Cloud Deployment Management Services end points.
NOTE: O-Cloud Inventory Services may provide additional information such as a Cloud Inventory reference. | | -| Step 10-12 (M) | For each DMS, SMO retrieves DMS capabilities using O-Cloud Inventory Update (see clause 3.1.4) and registers DMS in its inventory. | | -| Ends when | O-Cloud has registered with SMO and SMO has checked software version, configuration, and available DMS | | -| Exceptions | O-Cloud ID not found in inventory | | -| Post Conditions | O-Cloud ready to support new NF deployments | | -| Traceability | REQ-ORC-GEN6; REQ-ORC-GEN7; REQ-ORC-GEN8; REQ-ORC-GEN9; REQ-ORC-O2-3; REQ-ORC-O2-4; REQ-ORC-O2-5; REQ-ORC-O2-6 | | - -#### 3.1.3.3 UML sequence diagram - -![Sequence diagram titled 'O-Cloud Deployment Processing' showing interactions between Personnel (Cloud Installation Project Mgr, Cloud Installer), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS).](dfe556fea00682b09a59427aaf72051c_img.jpg) - -The sequence diagram illustrates the O-Cloud Deployment Processing. It features three lifelines: Personnel (with actors Cloud Installation Project Mgr and Cloud Installer), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The process begins with the IMS sending a message '1 Update SMO inventory with IMSServiceURI' to FOCOM. FOCOM then initiates discovery of the O-Cloud inventory. Subsequent messages include '2 Query SW inventory', '3 OK (O-Cloud SW Version Data)', '4 Download new software' (within an 'alt' block for mismatched inventory), '5 (O-Cloud SW version data)', '6 Configure Infrastructure Monitoring (CM/FM/PM)', '7 Query Infrastructure inventory', '8 Query O-Cloud for available DMSs', and '9 OK (DMS list)'. A 'loop' block labeled '[foreach DMS]' contains '10 retrieve DMS Data (deploymentManagerId)', '11 OK (IEP, Capabilities, Capacities, etc.)', and '12 Register DMSs'. The process concludes with 'End Use Case' and 'SMO updates inventory throughout the above processing'. - -Sequence diagram titled 'O-Cloud Deployment Processing' showing interactions between Personnel (Cloud Installation Project Mgr, Cloud Installer), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). - -Figure 3-3: O-Cloud Deployment Processing - -### 3.1.4 O-Cloud Inventory Update Use Case - -#### 3.1.4.1 High Level Description - -This Use Case describes the procedure for the SMO and O-Cloud to update inventory information about its type and current capabilities using O2 Infrastructure Inventory Services [9], including resource build configurations (aka “flavors”), capacity, utilization and availability. This procedure is invoked initially at deployment of the O-Cloud and can be invoked at later times to identify changes in the capabilities of the O-Cloud. Two patterns are possible, one using query/response from the SMO in order to get current inventory, e.g., before instantiating a new NF deployment and one triggered by autonomous indications from the O-Cloud when there has been a change in inventory status. - -#### 3.1.4.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | O-Cloud is initialized and communicating with the SMO, ready for deployments to be instantiated. | | -| Actors and Roles | SMO: FOCOM
IMS | | -| Assumptions | Notification Event has been configured into the IMS by the SMO | | -| Preconditions | 1) SMO is available
2) O-Cloud has been installed and activated
3) SMO has registered O-Cloud and software version in its inventory | | -| Begins when | 1) SMO is deploying or scaling up a new O-cloud or
2) SMO determines that it needs to query O-cloud to determine if O-Cloud can support a new NF deployment or
3) Capabilities change has occurred in the O-cloud and SMO has previously subscribed to notification of capability changes. | | -| Step 1,2 (ALT) | In the Query/Response pattern, the SMO uses O2 Inventory Services to update its inventory record for the O-Cloud IMS/DMS capabilities. IMS responds with what it supports | | -| Step 3 (ALT) | In the Event Notification pattern, using O2 O-Cloud Monitoring Services [9] IMS sends notification event to the SMO due to a change in inventory | | -| Ends when | SMO receives up-to-date capabilities information from IMS and updates the O-Cloud inventory record | | -| Exceptions | None identified | | -| Post Conditions | SMO holds updated inventory | | -| Traceability | REQ-ORC-GEN10; REQ-ORC-GEN11; REQ-ORC-GEN12; REQ-ORC-GEN13; REQ-ORC-O2-7; REQ-ORC-O2-8 | | - -#### 3.1.4.3 UML sequence diagram - -![UML sequence diagram for O-Cloud Inventory Update. Lifelines: FOCOM (Service Management & Orchestration Framework) and IMS (O-Cloud Platform). The diagram shows two patterns: Query/Response and Even Notification. In the Query/Response pattern, FOCOM sends a 'Query O-Cloud Info' message to IMS, and IMS returns 'OK (IMS/DMS Data)'. A note indicates that the data includes capabilities, capacities, allocations, reservations, and availabilities. In the Even Notification pattern, IMS sends a 'Notify O-Cloud inventory change' message to FOCOM. A note indicates that FOCOM can process this information. The sequence ends with 'End Use Case'.](898fb89a50d9ec1dfb4e425c816976a7_img.jpg) - -``` - -sequenceDiagram - participant FOCOM as FOCOM (Service Management & Orchestration Framework) - participant IMS as IMS (O-Cloud Platform) - - Note right of IMS: Capabilities (Flavors, Artifact Types, Resource Types, etc.), Capacities, Allocations, Reservations, Availabilities in terms of flavors are all Attribute of the IMS/DMS inventory record and returned as IMS/DMS Data. - - Note left of FOCOM: SMO can process the inventory changes information from the message - - FOCOM->>IMS: 1 <> Query O-Cloud Info (resourcePoolID/deploymentManagerID) - IMS-->>FOCOM: 2 <> OK. (IMS/DMS Data) - - Note right of IMS: End Use Case - - IMS-->>FOCOM: 3 <> Notify O-Cloud inventory change (IMS/DMS Data) - -``` - -UML sequence diagram for O-Cloud Inventory Update. Lifelines: FOCOM (Service Management & Orchestration Framework) and IMS (O-Cloud Platform). The diagram shows two patterns: Query/Response and Even Notification. In the Query/Response pattern, FOCOM sends a 'Query O-Cloud Info' message to IMS, and IMS returns 'OK (IMS/DMS Data)'. A note indicates that the data includes capabilities, capacities, allocations, reservations, and availabilities. In the Even Notification pattern, IMS sends a 'Notify O-Cloud inventory change' message to FOCOM. A note indicates that FOCOM can process this information. The sequence ends with 'End Use Case'. - -Figure 3-4: O-Cloud Inventory Update - -### 3.1.5 Hardware Infrastructure Scaling of O-Cloud Post Deployment - -#### 3.1.5.1 High Level Description - -After the initial deployment of an O-Cloud, it may be necessary to scale up resources. In this use case, we examine how the SMO will discover and manage a new O-Cloud Node that has been cabled and powered up to be part of an existing O-Cloud. - -#### 3.1.5.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Additional O-Cloud Nodes are powered on for an existing O-Cloud; O-Cloud initializes new O-Cloud Node and communicates the presence of additional resources to SMO. | | -| Actors and Roles | Cloud Planner
Cloud Installer
SMO/ FOCOM
IMS
O-Cloud Node | | -| Assumptions | 1) Notification Event has been configured into the IMS by the SMO
2) The additional O-Cloud Node is cabled to be part of the existing O-Cloud at the site | | -| Preconditions | 1) SMO is available
2) O-Cloud is operational and known to SMO
3) Network connectivity exists between the O-Cloud and the SMO
4) Network connectivity exists between the new O-Cloud Node and IMS
5) Cloud Installer knows (from Cloud Planner) the need to add O-Cloud Node(s) to the existing O-Cloud
6) IMS has been configured with the O-Cloud blueprint for the new O-Cloud Node | | -| Begins when | Decision to add additional resources to an existing O-Cloud has been made and new O-Cloud Node is installed and powered on. | | -| Step 1 (M) | New O-Cloud Node interacts with IMS to get basic software for O-Cloud load and configuration | | -| Step 2 (M) | SMO executes the O-Cloud Inventory Update procedure (clause 3.1.4), in this use case using the Event Notification Pattern, IMS informs SMO of change in inventory due to the new O-Cloud Node and SMO updates its inventory record with the information in the notification. | | -| Ends when | O-Cloud has added new O-Cloud Node | | -| Exceptions | None identified | | -| Post Conditions | Additional O-Cloud Node is available in O-Cloud.
SMO holds updated inventory. | | -| Traceability | REQ-ORC-GEN14; REQ-ORC-GEN15; REQ-ORC-O2-8 | | - -#### 3.1.5.3 UML sequence diagram - -![UML sequence diagram for Hardware Infrastructure Scaling. Lifelines: Personnel (Cloud Planner, Cloud Installer), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The sequence shows the installation of a new O-Cloud node, its booting and configuration by the IMS, notification of the inventory change to the FOCOM, and the subsequent inventory update by the SMO.](79e1709a7317ead45379cbb8ff3ba802_img.jpg) - -``` - -sequenceDiagram - actor Cloud Planner - actor Cloud Installer - participant FOCOM as Service Management & Orchestration Framework - participant IMS as O-Cloud Platform - - Note right of Cloud Installer: Cloud Installer installs new O-Cloud Node - Cloud Installer->>IMS: - Note right of IMS: New Node requests software image boot from IMS -IMS sends image load to O-Cloud Node -O-Cloud Node notifies when booted -IMS sends config to O-Cloud Node - IMS-->>FOCOM: 2 <> Notify O-Cloud Inventory Change (New O-Cloud Node Available) - Note right of FOCOM: SMO executes O-Cloud Inventory Update (clause 3.1.4) - FOCOM-->>IMS: 1 New O-Cloud Node(s) added - Note right of FOCOM: End Use Case - -``` - -UML sequence diagram for Hardware Infrastructure Scaling. Lifelines: Personnel (Cloud Planner, Cloud Installer), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The sequence shows the installation of a new O-Cloud node, its booting and configuration by the IMS, notification of the inventory change to the FOCOM, and the subsequent inventory update by the SMO. - -Figure 3-5: Hardware Infrastructure Scaling - -### 3.1.6 O-Cloud Platform Software Update Use Case - -#### 3.1.6.1 High Level Description - -Edge clouds deployments can range in the 10K to 100K range across an operator network. Rolling O-Cloud software updates (upgrades and downgrades) need to be performed without service disruption for both VM and container-based workloads. Across a region, it may be necessary to update all edge O-Clouds in a serial fashion in order to minimize potential disruptions or in a parallel fashion where a set amount of edge O-Clouds in a region are simultaneously updated. Compute and storage nodes of individual edge O-Clouds can also be updated in a serial or parallel hitless fashion. Within an individual O-Cloud, the IMS migrates Network Function deployments from the affected O-Cloud Nodes before the software update in order to avoid service disruption (in this use case, it is assumed that IMS does this autonomously). From an SMO perspective, offloading the update strategy of an edge O-Cloud to a regional and local controller substantially reduces the update complexity. - -Fault handling of an O-Cloud update is critical. Individual nodes can fail during the update process and may need to be replaced. Rolling back of the update prior to a successful completion shall also be supported. - -In this use case, we examine how the SMO will update a single O-Cloud. It is assumed that the software update does not affect the IMS itself, and that the IMS is capable of performing the software update and migrating NF deployments from the affected O-Cloud Nodes without affecting active services. - -For O-Cloud resources managed by a Hardware Accelerator Manager (HAM), which is defined in O-RAN WG6.AAL-GAnP [11], Clause 3.1, the IMS informs the HAM what SW artifacts to be updated for HWA resources managed by that HAM. The HAM is responsible for obtaining and updating the SW artifacts. For further information, see O-RAN WG6.AAL-GAnP [11], Clause 4.2.1. - -#### 3.1.6.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Update (upgrade or downgrade) the platform software of an existing O-Cloud | | -| Actors and Roles | Cloud Maintainer
SMO: FOCOM/OAM Functions
IMS
O-Cloud Node | | -| Assumptions | Software update to O-Cloud is available
IMS supports software update, including software update rollback mechanism, and NF deployment migration | | -| Preconditions | 1) SMO is available
2) O-Cloud is operational and known to SMO
3) Affected O-Cloud Nodes have no NF deployments running or NF deployments can be migrated to other O-Cloud Nodes.
4) O-Cloud Node spare resources are available at the O-Cloud in order to support NF deployment migration during the update process. | | -| Begins when | Decision to update the platform software is made. | | -| Step 1 (M) | Cloud Maintainer requests that SMO update platform software on an existing O-Cloud instance. Cloud Maintainer can specify the version of software to be upgraded or downgraded. | | -| Step 2,3 (M) | SMO triggers software download and validation procedure at the O-Cloud using O2 Software Management Services | | -| Step 4-6 (M) | IMS gets software package of the requested version from SMO and validates internally;
IMS notifies SMO that software download is complete | | -| Step 7-8 (M) | SMO requests pre-check procedure be done by IMS to determine if software update is acceptable or not acceptable;
IMS responds with pre-check response | | -| Step 9-10 (M) | If the pre-check indicates update is acceptable:
1) SMO directs IMS to activate the software update;
2) IMS determines the update process (software parts to update, points of control for rolling back, etc.) before starting the software update;
3) IMS migrates NF deployments from affected O-Cloud Nodes – note original requirements for these NF deployments shall continue to be met;
4) IMS updates software image (e.g., hypervisor) on the affected O-Cloud Nodes;
5) IMS checks the request from SMO; if restart is required, IMS performs restart.

If the pre-check indicates update is not acceptable, stop update procedure and SMO returns failure response to O-Cloud operator. | | -| Step 11-13 (ALT) | IMS determines that O-Cloud Node has updated software and is in running state;
IMS updates its SW inventory. IMS notifies SMO that O-Cloud software has been updated and SMO updates its inventory. | | -| Step 14-15 (ALT) | In case of software update failure, IMS rolls back to the original version (the version which was running before initiating the software update).
IMS notifies SMO that IMS failed in O-Cloud software update. | | -| Step 16 (M) | The O-Cloud Software Update response is returned to O-Cloud operator by SMO. | | -| Ends when | SUCCESS: O-Cloud has updated software successfully.
FAILURE: The O-Cloud software has been rolled back to the original version. | | -| Exceptions | Software update is not acceptable, in which case update does not proceed.
The O-Cloud software has been rolled back to the original version. | | -| Post Conditions | SUCCESS: (1) SMO holds updated inventory
(2) O-Cloud running with updated O-Cloud software
(3) IMS holds updated SW inventory
FAILURE: The O-Cloud software has been rolled back to the original version. | | -| Traceability | REQ-ORC-GEN16; REQ-ORC-GEN17; REQ-ORC-02-9 | | - -#### 3.1.6.3 UML sequence diagram - -![UML sequence diagram for O-Cloud Platform Software Update. Lifelines: Cloud Maintainer (actor), Service Management & Orchestration Framework (FOCOM, OAM Function), and O-Cloud Platform (IMS). The sequence shows a software update request, file download, validation, pre-check, activation, and a successful or failed update path with inventory updates and backups.](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg) - -``` - -sequenceDiagram - actor Cloud Maintainer - participant FOCOM - participant OAM Function - participant IMS - - Note right of FOCOM: O-Cloud Software Update - - Cloud Maintainer->>FOCOM: 1 O-Cloud Basic Software Update (upgrade or downgrade) request (SW version) - FOCOM->>IMS: 2 <> Download software of requested version (SW Package, CallbackURI) - IMS-->>FOCOM: 3 <> Accepted - - loop for each file in the SW Package - FOCOM->>IMS: 4 Get file - IMS-->>FOCOM: 5 Validate file - end - - IMS-->>FOCOM: 6 <> (IN_PROGRESS:SW Package Download Complete) - Note left of FOCOM: SMO can process the inventory changes information from the message - FOCOM->>IMS: 7 <> SW update pre-check request - IMS-->>FOCOM: 8 <> SW update pre-check response - FOCOM->>IMS: 9 <> Activate SW update - Note right of IMS: Check if update will cause reset - Note right of IMS: IMS creates backup of current software - Note right of IMS: 10 Optional update image - Note right of IMS: The IMS migrates NF deployments from affected O-Cloud Node. The IMS directs the O-Cloud Node to update image. - Note right of IMS: O-Cloud Software Updated - - alt Successful SW Update - Note right of IMS: O-Cloud Node now running - IMS-->>FOCOM: 11 Update SW Inventory with O-Cloud update - FOCOM-->>IMS: 12 <> (COMPLETE:O-Cloud SW version data) - Note left of FOCOM: SMO can process the inventory changes information from the message - FOCOM->>FOCOM: 13 Update inventory - else Exception: SW Update failed - Note right of IMS: 14. Rollback of O-Cloud software to the original/prior version from backup - IMS-->>FOCOM: 15 <> (Failure:O-Cloud SW version data) - end - - FOCOM-->>Cloud Maintainer: 16 O-Cloud Basic Software Update response - Note right of IMS: 16. IMS creates backup of updated software (optional) - - Note right of FOCOM: End Use Case - -``` - -UML sequence diagram for O-Cloud Platform Software Update. Lifelines: Cloud Maintainer (actor), Service Management & Orchestration Framework (FOCOM, OAM Function), and O-Cloud Platform (IMS). The sequence shows a software update request, file download, validation, pre-check, activation, and a successful or failed update path with inventory updates and backups. - -Figure 3-6: O-Cloud Platform Software Update - -### 3.1.7 Functional Status Query Use Case - -#### 3.1.7.1 High Level Description - -The purpose of the functional status query use case is to allow for the request of state and status information from the O-Cloud. Standardized state and status information can be found in ITU-T X.731 (see reference [15]). While X.731 concepts originate in a wireless RAN context, they are useful and applicable to the management and reporting of O-Cloud resources. - -NOTE 1: For an operator to indicate something is in maintenance, the Administrative State Attribute (from X.731) values of “locked” and “shutting down” could be used. - -NOTE 2: For an operator to indicate something is undergoing test, the Availability Status attribute (X.731) “in test” and the Control Status Attribute (X.731) “subject to test” and “reserved for test” could be used. - -For example, an operator wants to see that things are “healthy” and operating with no faults. They could issue a functional status query on the O-Cloud; and the query would return an operational state of “*enabled*” with no alarm status of “*alarm outstanding*” for all resources. - -#### 3.1.7.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal |

The goal of this use case is to inform an operator, SMO user, or entity of the functional status of the O-Cloud Resources.

This allows a user to query states and their attending status. The supported states of the O-Cloud Resources are: Operational, Administrative, and Usage. Each of the states have status attributes associated with them: alarm status, procedural status, availability status, control status, standby status and unknown status. The full description is defined in ITU-T X.731 TMN reference [15].

Some logical resources: the O-Cloud in aggregate, and O-Cloud resource pools, which are a collection of resources may or may not have a status.

The three status indicators above give a sense of the current performance and current fault situation for the O-Cloud resource.

Status can be requested by the SMO to the O-Cloud IMS. Furthermore, the API can be used by any entity.

The Status query also has query criteria that is evaluated when resolving the query request.

| | -| Actors and Roles |

O-Cloud Operator – The O-Cloud operator is a user that is interested in getting functional status query results.

SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer of the status query service.

IMS – The IMS within the O-Cloud is used to represent any provider of the functional status query service.

| | -| Assumptions |

A requesting entity does not need a subscription of any kind to query for Status.

| | -| Preconditions |

The O-Cloud is operational.

The FOCOM (SMO) has connectivity to IMS.

Security authorization, and privilege access has been established between the FOCOM (SMO) and IMS.

| | -| Begins when |

This use case begins when either of the following two situations happens:

  1. The O-Cloud Operator initiates a functional status query for an O-Cloud resource.
  2. The SMO initiates a functional status query

NOTE 1: while not depicted in the flow, any other entity with the proper credentials can initiate a functional status query of the O-Cloud resource.

| | -| Step 1.1 (ALT) |

FUNCTIONAL STATUS QUERY INITIATED FROM OPERATOR – A status query is initiated from the Operator to the FOCOM (SMO) with functional status query criteria that specifies what type of O-Cloud resource states and state values the operator is interested in.

| | -| Step 1.2 (ALT) |

FUNCTIONAL STATUS QUERY INITIATED FROM SMO – A status query may also be initiated from the FOCOM (SMO) directly with functional status query criteria that specifies what type of O-Cloud resource states and state values to retrieve from the IMS.

| | -| Step 2 (M) |

FUNCTIONAL STATUS QUERY REQUEST FROM FOCOM TO IMS – A status query is processed by the FOCOM (SMO) towards the IMS in the O-Cloud with the functional status query criteria.

| | -| Step 3 (ALT) |

SUCCESSFUL STATUS RESPONSE – The response is returned for the functional status query with state status content matching the status query criteria.

NOTE 2: A functional status query on the O-Cloud resource with no status criteria will return a successful status for the full-service object.

| | - -| | | | -|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 4 (ALT) | STATUS OBJECT NOT FOUND – This is an alt step. This is an exception case for the Functional Status Query basic case. In this situation, the service object to be queried was not found. A “status not found” response is sent to the subscriber. For example, a status query was performed on a non-existent O-Cloud resource. | | -| Step 5 (ALT) | STATUS NO CONTENT – This is an alt step. This is an exception case for the Functional Status Query basic case. In this situation, the evaluation of the query parameters returned no content (an empty set). A “no content” response is sent to the subscriber. For example, if the given criteria [(only operational state = disabled) and (only operational state= operational)] would never return any result. | | -| Step 6 (ALT) | STATUS OTHER QUERY FAILURE – This is an alt step. This exception case occurs when the Functional Status Query encounters a problem that is not defined as part of this scenario. | | -| Step 7 (O) | OPERATOR FUNCTIONAL STATUS QUERY RESPONSE – This is an optional step. When the situation requires that a response to the operator is needed, the Functional Status Query response is returned to the requester with the status query information matching the criteria given in the request. | | -| Ends when | This scenario ends at any of the ALT cases, or with a successful Functional Status Query response. | | -| Exceptions | This use case can encounter three basic alternate cases.
OBJECT NOT FOUND – The first a Functional Status query is attempted on a non-existent O-Cloud resource.
NO CONTENT – The second alternate case is a “No Content” case where the Query parameters return an empty set.
OTHER QUERY FAILURE – A problem occurs that is not defined as part of this use case. | | -| Post-conditions | SUCCESS: Functional Status information is returned successfully matching the criteria in the functional status query request.
FAILURE: An exception notification has been issued. | | -| Traceability | REQ-ORC-02-19, REQ-ORC-02-20 | | - -#### 3.1.7.3 UML Sequence Diagram - -![UML Sequence Diagram for O-Cloud Functional Status Query. Lifelines: Personnel (O-Cloud SMO operator), Service Management & Orchestration Framework - Subscriber (FOCOM), and O-Cloud Platform (IMS/DMS) - Publisher (IMS). The sequence starts with an optional '1.1 Functional Status Query' from Personnel to FOCOM, followed by '1.2 Functional Status Query (optional)' from FOCOM to itself. Then '2 Functional Status Query Request' from FOCOM to IMS. An alt block 'Successful Functional Status Query' contains: '3 Functional Status query response' from IMS to FOCOM; exceptions: '4 Object not found', '5 Query has no Content', and '6 Other query Failure' from IMS to FOCOM. Finally, '7 Functional Status Query Response (Optional)' from FOCOM to Personnel, ending with 'End IMS Functional Status Query'.](90ddb84c323b956e2d50a54d3f870566_img.jpg) - -UML Sequence Diagram for O-Cloud Functional Status Query. Lifelines: Personnel (O-Cloud SMO operator), Service Management & Orchestration Framework - Subscriber (FOCOM), and O-Cloud Platform (IMS/DMS) - Publisher (IMS). The sequence starts with an optional '1.1 Functional Status Query' from Personnel to FOCOM, followed by '1.2 Functional Status Query (optional)' from FOCOM to itself. Then '2 Functional Status Query Request' from FOCOM to IMS. An alt block 'Successful Functional Status Query' contains: '3 Functional Status query response' from IMS to FOCOM; exceptions: '4 Object not found', '5 Query has no Content', and '6 Other query Failure' from IMS to FOCOM. Finally, '7 Functional Status Query Response (Optional)' from FOCOM to Personnel, ending with 'End IMS Functional Status Query'. - -Figure 3-7: O-Cloud Functional Status Query - -### 3.1.8 Functional Status Update Use Case - -#### 3.1.8.1 High Level Description - -The purpose of the functional status update use case is to update the state and status of the O-Cloud Resources. - -#### 3.1.8.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal |

The goal of this use case is to allow SMO to request to update the functional status of the O-Cloud Resources.

This allows a user to update the state and status information of the O-Cloud Resources.

NOTE 1: Some logical resources: the O-Cloud in aggregate, and O-Cloud Resource pools, which are a collection of resources may or may not have a status.

NOTE 2: The state indicators give a sense of the current performance and current fault situation for the O-Cloud Resource.

Status update can be requested by the SMO (FOCOM) to the O-Cloud IMS. Furthermore, the API can be used by any entity.

| | - -| | | | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Actors and Roles |

O-Cloud Operator – A Cloud Service Provider (CSP) or entity using the SMO.

FOCOM/SMO – The FOCOM within the SMO is used in this use case to represent the initiator of the Functional Status Update request.

IMS – The IMS in the O-Cloud responds to the Functional Status Update request.

NOTE 3: It is assumed in the use case flow that managed objects refer to underlying O-Cloud Resources, so the interactions are shown towards the IMS. The use case could be revisited in future versions of the present document once additional analysis on the impacts of functional status update is done on various types of managed objects, e.g., objects managed by the DMS.

| | -| Assumptions | | | -| Preconditions |

O-CLOUD OPERATIONAL - The O-Cloud is operational.

CONNECTIVITY - The SMO (FOCOM) has connectivity to IMS.

SECURITY - Security authorization, and privilege access has been established between the SMO (FOCOM) and IMS.

| | -| Begins when |

This use case begins when either of the following two situations happens:

  1. 1. The O-Cloud Operator initiates a functional status update for an O-Cloud Resource.
  2. 2. The SMO initiates a functional status update.

NOTE 4: while not depicted in the flow, any other entity with the proper credentials can initiate a functional status update of the O-Cloud Resource.

| | -| Step 1.1 (ALT) | FUNCTIONAL STATUS UPDATE INITIATED FROM OPERATOR – A status update is initiated from the Operator to the SMO (FOCOM). | | -| Step 1.2 (ALT) | FUNCTIONAL STATUS UPDATE INITIATED FROM SMO – A status update is initiated from the SMO (FOCOM) directly. | | -| Step 2 (M) | FUNCTIONAL STATUS UPDATE REQUEST FROM FOCOM TO IMS – A status update request is sent by the SMO (FOCOM) to the IMS. IMS updates the status of O-Cloud Resources. | | -| Step 3 (ALT) | SUCCESSFUL STATUS RESPONSE – The response is returned to the SMO (FOCOM) for the functional status update. | | -| Step 4 (ALT) | STATUS OBJECT NOT FOUND – This is an alt step. This is an exception case for the Functional Status Update basic case. In this situation, the managed object to be updated was not found. An “object not found” response is sent to the SMO (FOCOM). For example, a status update was requested to be performed on a non-existent O-Cloud Resource. | | -| Step 5 (ALT) | STATUS OTHER UPDATE FAILURE – This is an alt step. This exception case occurs when the Functional Status Update encounters a problem that is not defined as part of this scenario. An “other update failure” response is sent to the SMO (FOCOM). | | -| Step 6 (O) | OPERATOR FUNCTIONAL STATUS UPDATE RESPONSE – This is an optional step. When the situation requires that a response to the O-Cloud Operator is needed, the Functional Status Update response is returned to the requester by the SMO (FOCOM). | | -| Ends when | This scenario ends at any of the ALT cases, or with a successful Functional Status Update response. | | -| Exceptions |

This use case can encounter two basic exception cases.

OBJECT NOT FOUND – The first a functional status update is attempted on a non-existent O-Cloud Resource.

OTHER UPDATE FAILURE – A problem occurs that is not defined as part of this use case.

| | -| Post-conditions |

SUCCESS: Functional Status is updated successfully.

FAILURE: An exception notification has been issued.

| | -| Traceability | REQ-ORC-O2-50, REQ-ORC-O2-51 | | - -#### 3.1.8.3 UML Sequence Diagram - -![UML Sequence Diagram for O-Cloud Functional Status Update. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS/DMS) (IMS). The sequence starts with 'IMS Functional Status Update' from FOCOM to IMS. An 'alt' block '[Functional Status Update]' contains optional messages 1.1 and 1.2 between Operator and FOCOM. Message 2 is 'Functional Status Update Request' from FOCOM to IMS, with a note 'IMS updates the status of O-Cloud Resources.'. An 'alt' block '[Successful Functional Status Update]' contains messages 3, 4, and 5 from IMS to FOCOM. Message 6 is 'Functional Status Update Response (Optional)' from FOCOM to Operator. The sequence ends with 'End IMS Functional Status Update' from FOCOM to IMS.](9c1d3678db4a12d5864cb2a4def1135d_img.jpg) - -``` - -sequenceDiagram - actor Operator as O-Cloud Operator - participant FOCOM as Service Management & Orchestration Framework (FOCOM) - participant IMS as O-Cloud Platform (IMS/DMS) (IMS) - - Note over FOCOM: IMS Functional Status Update - alt Functional Status Update: 1.1 Functional Status Update (optional) / 1.2 Functional Status Update (optional) - Note right of IMS: IMS updates the status of O-Cloud Resources. - FOCOM->>IMS: 2 Functional Status Update Request - alt Successful Functional Status Update: 3 Functional status update response / 4 Object not found / 5 Other update failure - FOCOM-->>Operator: 6 Functional Status Update Response (Optional) - Note over FOCOM: End IMS Functional Status Update - -``` - -UML Sequence Diagram for O-Cloud Functional Status Update. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS/DMS) (IMS). The sequence starts with 'IMS Functional Status Update' from FOCOM to IMS. An 'alt' block '[Functional Status Update]' contains optional messages 1.1 and 1.2 between Operator and FOCOM. Message 2 is 'Functional Status Update Request' from FOCOM to IMS, with a note 'IMS updates the status of O-Cloud Resources.'. An 'alt' block '[Successful Functional Status Update]' contains messages 3, 4, and 5 from IMS to FOCOM. Message 6 is 'Functional Status Update Response (Optional)' from FOCOM to Operator. The sequence ends with 'End IMS Functional Status Update' from FOCOM to IMS. - -Figure 3-8: O-Cloud Functional Status Update - -### 3.1.9 IMS Software Update Use Case - -#### 3.1.9.1 High Level Description - -This use case focuses on the update of IMS software. For the O-Cloud Platform Software update, please see 3.1.6. - -#### 3.1.9.2 Sequence Description - -| Use Case Stage | Evolution / Specification | >>Uses<<
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Update the O-Cloud IMS software. | | -| Actors and Roles | O-Cloud Operator
SMO: FOCOM Functions
IMS | | -| Assumptions | Software updates to O-Cloud IMS are available.
IMS supports software update. | | -| Preconditions | 1) SMO is available
2) O-Cloud is operational and known to SMO
3) Required IMS software image(s) are available in SMO (details on how IMS obtains the image(s) are FFS) | | - -| | | | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | 4) The IMS is healthy | | -| Begins when | Decision to update the O-Cloud IMS software is made. | | -| Step 1 (M) | O-Cloud Operator requests that SMO update O-Cloud IMS software version. | | -| Step 2-3 (M) | SMO (FOCOM) queries IMS for current SW inventory, and IMS responds with SW inventory data. | | -| Step 4 (OPT) | If SW inventory does not match required inventory:
- SMO (FOCOM) triggers software download and validation procedure at the O-Cloud. | | -| Step 5 (M) | The IMS triggers the download of the requested software version image(s)
NOTE: IMS gets requested software package from the SMO (either using push or pull mechanism). | | -| Step 6.1(ALT) | IMS notifies SMO (FOCOM) that valid software is now available | | -| Step 6.2 (ALT) | ALT EXCEPTION: Requested IMS software version could not be downloaded
IMS notifies SMO (FOCOM) that requested software could not be downloaded | | -| Step 6.3 (ALT) | SMO (FOCOM) notifies the O-Cloud Operator that the IMS Software Update was unsuccessful | | -| Step 7 (M) | SMO (FOCOM) requests pre-check procedure be done by IMS to determine if requested software update is acceptable or not. | | -| Step 8 (M) | The IMS performs the pre-check on requested software version | | -| Step 9.1 (ALT) | IMS responds to indicate that requested update is acceptable. | | -| Step 9.2 (ALT) | ALT EXCEPTION: Requested IMS software version is not acceptable
IMS notifies SMO (FOCOM) that requested IMS software version is not acceptable | | -| Step 9.3 (ALT) | SMO (FOCOM) notifies the O-Cloud Operator that the requested IMS Software Update was unsuccessful | | -| Step 10 (M) | If the pre-check indicates update is acceptable SMO (FOCOM) directs IMS to activate the software update. | | -| Step 11 (M) | The IMS:
- Ensures its specific update conditions are met
- Performs the update
- Performs its specific testing procedure(s) | | -| Step 12.1 (ALT) | IMS updates the O-Cloud Software Inventory | | -| Step 12.2 (ALT) | IMS notifies SMO (FOCOM) that the Software Update procedure was performed successfully | | -| Step 12.3 (ALT) | ALT EXCEPTION: Activation of requested software failed
During the Update procedure, IMS encounters some failure and rolls back any update(s) made.
IMS notifies SMO (FOCOM) that the IMS Software Update procedure was unsuccessful | | - -| | | | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 13 (M) | SMO (FOCOM) sends O-Cloud Software Update response | | -| Ends when | IMS software update has been performed successfully or when one of the Exception cases have been encountered | | -| Exceptions |

Requested IMS software version could not be downloaded – This exception is encountered when the requested software could not be downloaded by IMS

Requested IMS software version is not acceptable – This exception is encountered when the IMS determines that the downloaded software version is not acceptable

Activation of requested software failed - This exception is encountered when the IMS encounters an error during the Update procedure

| | -| Post Conditions |

Update is successful:

  • - O-Cloud running with the requested IMS software version.
  • - IMS holds updated SW inventory.
  • - SMO holds updated inventory.

An Exception occurred:

  • - O-Cloud is running with the same IMS software version as at onset of the Use Case
| | -| Traceability | [REQ-ORC-O2-75], [REQ-ORC-O2-76] | | - -#### 3.1.9.3 UML Sequence Diagram - -![UML Sequence Diagram for IMS Software Update. Lifelines: Personnel (O-Cloud Operator), SMO (FOCOM), and O-Cloud Platform (IMS). The sequence includes: 1. O-Cloud Software Update request (SW version) from Operator to FOCOM; 2. Query Software Inventory from FOCOM to IMS; 3. OK (O-Cloud SW Version Data) from IMS to FOCOM; 4. Download requested Software version image(s) from FOCOM to IMS (opt: Requested Software version image(s) not in the O-Cloud Inventory); 5. IMS triggers download; 6.1/6.2: Notify valid software is now available / Notify requested software could not be downloaded (alt: Download successful / Download unsuccessful); 6.3: O-Cloud Software Update response (unsuccessful) from FOCOM to Operator; 7. SW update pre-check request from FOCOM to IMS; 8. IMS performs pre-check; 9.1/9.2: SW update pre-check response (successful / unsuccessful) (alt: Pre-check successful / Pre-check unsuccessful); 9.3: O-Cloud Software Update response (unsuccessful) from FOCOM to Operator; 10. Activate Software update from FOCOM to IMS; 11. IMS performs update (note: The IMS: - Ensures its specific update conditions are met - Performs the update - Performs its specific testing procedure(s)); 12.1/12.2/12.3: IMS updates O-Cloud Software Inventory / Activate Software update response (successful / unsuccessful) (alt: Software Update performed successfully / Error encountered during Update); 13. O-Cloud Software Update response from FOCOM to Operator; End of the Use Case.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) - -``` - -sequenceDiagram - actor Personnel as O-Cloud Operator - participant SMO as FOCOM - participant O-Cloud Platform as IMS - - Note right of SMO: O-Cloud Management Plane Software Update - - Personnel->>SMO: 1 O-Cloud Software Update request (SW version) - - Note right of SMO: IMS SW Image Binaries Synchronization - - SMO->>O-Cloud Platform: 2 «O2» Query Software Inventory - O-Cloud Platform-->>SMO: 3 «O2» OK (O-Cloud SW Version Data) - - opt Requested Software version image(s) not in the O-Cloud Inventory - SMO->>O-Cloud Platform: 4 «O2» Download requested Software version image(s) - O-Cloud Platform-->>O-Cloud Platform: 5 IMS triggers download - alt Download successful - O-Cloud Platform-->>SMO: 6.1 «O2» Notify valid software is now available - else Download unsuccessful - O-Cloud Platform-->>SMO: 6.2 «O2» Notify requested software could not be downloaded - end - SMO-->>Personnel: 6.3 O-Cloud Software Update response (unsuccessful) - end - - Note right of SMO: IMS SW Images Deployment - - Note right of SMO: Determine if software update is acceptable for the IMS or not - - SMO->>O-Cloud Platform: 7 «O2» SW update pre-check request - O-Cloud Platform-->>O-Cloud Platform: 8 IMS performs pre-check - - alt Pre-check successful - O-Cloud Platform-->>SMO: 9.1 «O2» SW update pre-check response (successful) - Note right of O-Cloud Platform: IMS determines that software update is acceptable - else Pre-check unsuccessful - O-Cloud Platform-->>SMO: 9.2 «O2» SW update pre-check response (unsuccessful) - Note right of O-Cloud Platform: IMS determines that software update is not acceptable - end - SMO-->>Personnel: 9.3 O-Cloud Software Update response (unsuccessful) - - SMO->>O-Cloud Platform: 10 «O2» Activate Software update - O-Cloud Platform-->>O-Cloud Platform: 11 IMS performs update - Note right of O-Cloud Platform: The IMS: -- Ensures its specific update conditions are met -- Performs the update -- Performs its specific testing procedure(s) - - alt Software Update performed successfully - O-Cloud Platform-->>SMO: 12.1 IMS updates O-Cloud Software Inventory - O-Cloud Platform-->>SMO: 12.2 «O2» Activate Software update response (successful) - else Error encountered during Update - Note right of O-Cloud Platform: The IMS encounters some failure and update is rolled back - O-Cloud Platform-->>SMO: 12.3 «O2» Activate Software update response (unsuccessful) - end - - SMO-->>Personnel: 13 O-Cloud Software Update response - - Note right of SMO: End of the Use Case - -``` - -UML Sequence Diagram for IMS Software Update. Lifelines: Personnel (O-Cloud Operator), SMO (FOCOM), and O-Cloud Platform (IMS). The sequence includes: 1. O-Cloud Software Update request (SW version) from Operator to FOCOM; 2. Query Software Inventory from FOCOM to IMS; 3. OK (O-Cloud SW Version Data) from IMS to FOCOM; 4. Download requested Software version image(s) from FOCOM to IMS (opt: Requested Software version image(s) not in the O-Cloud Inventory); 5. IMS triggers download; 6.1/6.2: Notify valid software is now available / Notify requested software could not be downloaded (alt: Download successful / Download unsuccessful); 6.3: O-Cloud Software Update response (unsuccessful) from FOCOM to Operator; 7. SW update pre-check request from FOCOM to IMS; 8. IMS performs pre-check; 9.1/9.2: SW update pre-check response (successful / unsuccessful) (alt: Pre-check successful / Pre-check unsuccessful); 9.3: O-Cloud Software Update response (unsuccessful) from FOCOM to Operator; 10. Activate Software update from FOCOM to IMS; 11. IMS performs update (note: The IMS: - Ensures its specific update conditions are met - Performs the update - Performs its specific testing procedure(s)); 12.1/12.2/12.3: IMS updates O-Cloud Software Inventory / Activate Software update response (successful / unsuccessful) (alt: Software Update performed successfully / Error encountered during Update); 13. O-Cloud Software Update response from FOCOM to Operator; End of the Use Case. - -Figure 3-9: IMS Software Update - -### 3.1.10 DMS Software Update Use Case - -#### 3.1.10.1 High Level Description - -This use case focuses on the update (upgrade/downgrade) of a DMS software within an O-Cloud. For the O-Cloud platform upgrade (e.g., Kubernetes), please see 3.1.6. - -#### 3.1.10.2 Sequence Description - -| Use Case Stage | Evolution / Specification | >>Uses<<
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Software Update (upgrade/downgrade) of a DMS within an O-Cloud. | | -| Actors and Roles | O-Cloud Operator
SMO: FOCOM Functions
IMS
A DMS within the O-Cloud | | -| Assumptions | IMS supports update (upgrade/downgrade) of a DMS software within the O-Cloud | | -| Preconditions | 1. SMO is available
2. O-Cloud is operational and known to SMO
3. Required DMS software is available
4. The IMS is healthy | | -| Begins when | Decision to update the software of a DMS within an O-Cloud is made. | | -| Step 1 (M) | O-Cloud Operator requests that SMO updates the software version of a DMS within an O-Cloud. | | -| Step 2-3 (M) | SMO (FOCOM) queries IMS for current SW inventory, and IMS responds with SW inventory data. | | -| Step 4 (OPT) | If SW inventory does not match required inventory:
SMO (FOCOM) provides the software version information to the IMS. | | -| Step 5 (M) | When the SMO (FOCOM) has not provided the actual software image(s), the IMS obtains the requested DMS software version image(s). | | -| Step 6.1(ALT) | IMS notifies SMO (FOCOM) that requested software is now available | | -| Step 6.2 (ALT) | ALT EXCEPTION: Requested DMS software version could not be obtained
IMS notifies SMO (FOCOM) that requested DMS software could not be obtained | | -| Step 6.3 (ALT) | SMO (FOCOM) notifies the O-Cloud Operator that the DMS Software Update was unsuccessful | | -| Step 7 (M) | SMO (FOCOM) requests pre-check procedure be done by IMS to determine if requested DMS software update is acceptable or not. | | -| Step 8 (M) | The IMS performs the pre-check on requested DMS software version | | -| Step 9.1 (ALT) | IMS responds to indicate that requested DMS update is acceptable. | | - -| | | | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 9.2 (ALT) | ALT EXCEPTION: Requested DMS software version is not acceptable
IMS notifies SMO (FOCOM) that requested DMS software version is not acceptable | | -| Step 9.3 (ALT) | SMO (FOCOM) notifies the O-Cloud Operator that the requested DMS Software Update was unsuccessful | | -| Step 10 (M) | If the pre-check indicates update is acceptable, SMO (FOCOM) directs IMS to install the new software. | | -| Step 11 (M) | The IMS allocates needed resources (if necessary) and installs the requested DMS software
The IMS:
- Marks the DMS as modified
- Performs its specific testing procedure(s)
The updated DMS performs basic testing (e.g., pre-flight checks) | | -| Step 12.1(ALT) | IMS updates the O-Cloud SW inventory | | -| Step 12.2 (O) | IMS sends Inventory Change Notification if SMO (FOCOM) has subscribed | | -| Step 12.3(ALT) | IMS notifies SMO (FOCOM) that the DMS Software Update procedure was performed successfully | | -| Step 12.4 (ALT) | ALT EXCEPTION: Activation of requested software failed
During the Update procedure, IMS encounters some failure and rolls back any update(s) made.
IMS notifies SMO (FOCOM) that the DMS Software Update procedure was unsuccessful | | -| Step 13 (M) | SMO (FOCOM) sends O-Cloud Software Update response | | -| Ends when | DMS software update has been performed successfully or when one of the Exception cases have been encountered | | -| Exceptions | Requested DMS software version could not be obtained – This exception is encountered when the requested DMS software could not be obtained by IMS
Requested DMS software version is not acceptable – This exception is encountered when the IMS determines that the DMS software version is not acceptable
Activation of requested software failed - This exception is encountered when the IMS encounters an error during the DMS Update procedure | | -| Post Conditions | Update is successful:
- O-Cloud is running with the updated DMS active with the requested software version.
- IMS holds updated SW inventory.
- SMO holds updated inventory.
An Exception occurred:
O-Cloud is running with the same DMS software version as at onset of the Use Case | | - -| | | | -|--------------|----------------------------------|--| -| Traceability | [REQ-ORC-O2-79], [REQ-ORC-O2-80] | | -|--------------|----------------------------------|--| - -#### 3.1.10.3 UML Sequence Diagram - -![UML Sequence diagram for O-Cloud Management Plane Software Update. Lifelines: Personnel (O-Cloud Operator), SMO (FOCOM), IMS, DMS. The diagram shows the interaction for software updates, including inventory checks, pre-checks, and deployment steps with various success and error handling paths.](b51423b6c049f5b5fcde42e50b58f18b_img.jpg) - -``` - -sequenceDiagram - actor Personnel as O-Cloud Operator - participant SMO as FOCOM - participant IMS - participant DMS - - Note over SMO, IMS: O-Cloud Management Plane Software Update - - Personnel->>SMO: [01] O-Cloud Software Update request - - Note over IMS, DMS: DMS SW Image Binaries Synchronization - - SMO->>IMS: [02] <> Query O-Cloud SW inventory - IMS-->>SMO: [03] <> OK (SW inventory) - - opt Requested Software version image(s) not in the O-Cloud Inventory - SMO->>IMS: [04] <> Software version information - IMS->>IMS: [05] IMS obtains the requested software - alt Software obtained successfully - IMS-->>SMO: 6.1 <> Notify software is now available - else Unable to obtain software - IMS-->>SMO: 6.2 <> Notify requested software could not be obtained - end - SMO-->>Personnel: 6.3 O-Cloud Software Update response (unsuccessful) - end - - Note over SMO, DMS: DMS SW Images Deployment - - Note right of SMO: Determine if software update is acceptable for the IMS or not - SMO->>IMS: 7 <> SW update pre-check request - IMS->>IMS: 8 IMS performs pre-check - - alt Pre-check successful - Note right of IMS: IMS determines that software update is acceptable - IMS-->>SMO: 9.1 <> SW update pre-check response (successful) - else Pre-check unsuccessful - Note right of IMS: IMS determines that software update is not acceptable - IMS-->>SMO: 9.2 <> SW update pre-check response (unsuccessful) - SMO-->>Personnel: 9.3 O-Cloud Software Update response (unsuccessful) - end - - SMO->>IMS: 10 <> Install Software - Note right of IMS: IMS ensures specific update conditions are met and performs the deployment - IMS->>DMS: 11 Allocate needed resources and install software - Note right of IMS: The IMS: -- Marks the DMS as modified -- Performs its specific testing procedure(s) - Note right of DMS: The DMS performs its own specific testing (e.g., pre-flight checks) - - alt Software Update performed successfully - Note right of IMS: The IMS determines that the software update was successful. - IMS-->>SMO: 12.1 IMS updates O-Cloud SW Inventory - opt Subscription exists for change in Inventory - IMS-->>SMO: 12.2 <> InventoryChange Notification - end - IMS-->>SMO: 12.3 <> Activate Software update response (successful) - else Error encountered during Update - Note right of IMS: The IMS determines that a failure is encountered and the IMS rolls back the DMS update - IMS-->>SMO: 12.4 <> Activate Software update response (unsuccessful) - end - - SMO-->>Personnel: 13 O-Cloud Software Update response - - Note over SMO, IMS: End of the Use Case - -``` - -UML Sequence diagram for O-Cloud Management Plane Software Update. Lifelines: Personnel (O-Cloud Operator), SMO (FOCOM), IMS, DMS. The diagram shows the interaction for software updates, including inventory checks, pre-checks, and deployment steps with various success and error handling paths. - -Figure 3-10: DMS Software Update - -### 3.1.11 Query Information Use Case - -#### 3.1.11.1 High Level Description - -This is an O-Cloud basic use case that governs the behavior and flow for getting readable attributes of objects in the O2 Information Model by a qualified entity. The entity would usually be the SMO or O-Cloud Operator; however, it could also be another authorized user/technician, or authorized management function. The Query Information Use Case enables an authorized consumer to query and retrieve various information related to the O-Cloud infrastructure and its resources. - -The Query filter identifies a set of objects of interest for the Query operation. If no filter is given with the Query, then all objects are qualified, and the Query would return information on all objects. The attribute selector within the Query request is used to indicate the attributes that are of interest from the set of objects identified in the filter. If no attribute selector is specified, then the Query response returns all information of the qualified objects given in the filter. - -NOTE: The Query operation could return attributes of the Read/Write property that is read-only, read & write but not write-only. - -There are existing Query use cases in this document that act on specific objects in the information model. This Query Information use case describes the overall behavior applicable to query use cases. - -#### 3.1.11.2 Sequence Description - -| Use Case Stage | Evolution / Specification | >>Uses<< | -|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| -| Use Case Title | Query Information Use Case | | -| Goal |

The goal of the Query Information Use Case is the following:

  • - To return information on objects of interest specified in the Query filter within the Query Information request. If the Query filter contains both objects that do and do not exist, then the request will return information only for those objects that do exist.
  • - To return all information on all objects if no objects are specified in the Query filter within the Query Information request.
  • - To return read-only and read & write attribute value(s) of objects of interest specified in the attribute selector within the Query Information request. If the attribute selector contains both attributes that do and do not exist, then the request will return information only for the attribute(s) that do exist. NOTE 1: queries for write-only attributes are not honored.
  • - To return all attribute value(s) of object(s) of interest if no attribute selector is specified within the Query Information request.
  • - To Provide a framework for Query Information that applies to all APIs.
| | -| Actors and Roles |

Cloud Operator – The Cloud operator is a consumer (or entity) using or interfacing with the SMO (FOCOM).

SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer of the Query information response.

IMS – The IMS within the O-Cloud processes the Query Information request and receives the request over the O2ims interface.

| | -| Assumptions | There are no assumptions for this use case | | - -| | | | -|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Preconditions |

Connectivity – The Subscriber has connectivity to the publisher by some mechanism.

O-Cloud Operational – The O-Cloud is installed, operating, and registered with the SMO.

Privilege – The consumer identification and privileges of a SMO user have been verified to be able to perform O2 operations.

| | -| Begins when |

The use case begins when:

  • (1) An operator at the SMO wishes to query for information in the O-Cloud, or
  • (2) A management entity, typically the SMO, autonomously wishes to query for information in the O-Cloud
| | -| Step 1.1 (ALT) |

QUERY INFORMATION REQUEST INITIATED FROM OPERATOR (ALT) –

The authorized entities initiate a Query Information request with a query filter and an attribute selector. An authorized entity would usually be the O-Cloud Operator; however, it could also be another authorized management function.

The query filter specifies the objects of interest for the Query Information request.

The attribute selector specifies the relevant attributes for the objects of interest.

| | -| Step 1.2 (ALT) |

QUERY INFORMATION REQUEST INITIATED FROM SMO (ALT) –

The SMO autonomously initiates a Query Information request with a query filter and an attribute selector.

The query filter specifies the objects of interest for the Query Information request.

The attribute selector specifies the relevant attributes for the objects of interest.

| | -| Step 2 (M) |

QUERY INFORMATION REQUEST OVER O2 INTERFACE –

Either the Operator initiated, or the SMO autonomously initiated a Query Information Request from Steps 1.1 or 1.2 which both result in a Query Information Request over the O2 interface.

Connection authentication is verified by the IMS. The IMS process the Query Information request.

| | -| Step 3 (ALT) |

IMS PROCESSES REQUEST

The IMS authenticates the connection. The IMS processes the Query Information request.

SUCCESSFUL QUERY INFORMATION –

If the Query Information operation was successful, the IMS passes to FOCOM (SMO) the results matching the Query filter and attribute selector in the Query Information request. See the goals (above) for how the filter and selector are expected to work.

NOTE 2: If the attribute selector requests for a write-only attribute, this would be a valid query information request, but it would not return a value (see the goals above). It would be left to implementation on the specific behavior.

| | -| Step 4 (ALT) |

EXCEPTION: QUERY WITH NO EXISTING OBJECTS OR ATTRIBUTES (ALT)

| | - -| | | | -|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | This exception is encountered when a Query Information request specifies objects and attributes that do not exist. There are no objects that match in the query filter and/or there are no attributes that match in the attribute selector. | | -| Step 5 (ALT) | EXCEPTION: QUERY WITH NO EXISTING OBJECTS OR ATTRIBUTES (ALT)
The SMO returns to the requesting entity that a query with no existing objects or attributes exception was encountered. | | -| Step 6 (ALT) | The IMS encountered an unexpected condition, such as an internal software fault.
EXCEPTION: UNEXPECTED CONDITION (ALT) –
If possible, the IMS returns to FOCOM (SMO) that it has encountered an unexpected condition (software fault). | | -| Step 7 (ALT) | EXCEPTION: UNEXPECTED CONDITION (ALT) –
A response is sent to the requesting entity from the SMO, that the IMS encountered an unexpected condition processing the request.
The Use Case ends. | | -| Step 8 (ALT) | QUERY INFORMATION RESPONSE
The SMO returns to the requesting entity a Query Information response with the results matching the Query filter and attribute selector in the Query Information request. See the goals (above) for how the filter and selector are expected to work.
This step is a matching to step 1.1 | | -| Ends when | This Use Case ends when the Query Information operation has either successfully been accomplished or one of the two exception cases have been encountered. | | -| Exceptions | EXCEPTION: QUERY WITH NO EXISTING OBJECTS OR ATTRIBUTES
This exception is encountered when a Query Information request specifies objects and attributes that do not exist. An exception notification will be returned; and the use case will end this this situation.
EXCEPTION: UNEXPECTED CONDITION
The IMS encountered an unexpected condition, such as an internal software fault. An exception notification will be returned; and the use case will end this this situation. | | -| Post-conditions | SUCCESS – The requests objects and requested attributes from the Query filter and attribute selector respectively are enclosed in the Query Information response back to the requesting entity or the SMO if the request was autonomously initiated by the SMO.
FAILURE – The request was not able to be completed. No other “clean up” needs to occur. An exception notification has been issued. | | -| Traceability | [REQ-ORC-O2-3], [REQ-ORC-O2-96] | | - -#### 3.1.11.3 UML Sequence Diagram - -![UML Sequence Diagram for 'Query Information' use case. Lifelines: Cloud Operator (Personnel), FOCOM (Service Management & Orchestration Framework - Subscriber), and IMS (O-Cloud Platform - Publisher). The sequence involves a request from Cloud Operator to FOCOM, then to IMS, followed by a response back through FOCOM to Cloud Operator. It includes preconditions, an optional request initiation block, and two exception blocks for non-existing objects and unexpected conditions.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) - -**PRECONDITIONS:** - SMO has connectivity to O-Cloud - O-Cloud has registered its IMS with the SMO - The identification & privileges of a SMO user has been verified - -**Query Information Use Case** - -**opt** [Query Information Request Initiated] - 1.1 Query Information Request (Cloud Operator → FOCOM) - 1.2 Query Information Request (FOCOM → FOCOM self-call) - -2 <> Query Information Request (FOCOM → IMS) - Note: Connection authentication is verified - Note: IMS processes the Query Information request - -**alt** [Successful Query Information] - 3 <> Query Information Response (IMS → FOCOM) - -**[Exception: Query had only non-existing objects/attributes]** - 4 <> No existing objects or attributes (IMS → FOCOM) - 5 No existing objects or attributes (FOCOM → Cloud Operator) - Note: Use Case Ends - -**[Exception: Unexpected condition]** - Note: IMS encountered unexpected condition - 6 <> Unexpected condition (IMS → FOCOM) - 7 Unexpected condition (FOCOM → Cloud Operator) - Note: Use Case Ends - -8 Query Information Response (FOCOM → Cloud Operator) - -**End Query Information Use Case** - -UML Sequence Diagram for 'Query Information' use case. Lifelines: Cloud Operator (Personnel), FOCOM (Service Management & Orchestration Framework - Subscriber), and IMS (O-Cloud Platform - Publisher). The sequence involves a request from Cloud Operator to FOCOM, then to IMS, followed by a response back through FOCOM to Cloud Operator. It includes preconditions, an optional request initiation block, and two exception blocks for non-existing objects and unexpected conditions. - -Figure 3-11: Query Information - -## 3.2 Network Function Basic Use Cases - -### 3.2.1 NF Deployment Instantiation - -#### 3.2.1.1 High Level Description - -This Use Case describes the instantiation of a new NF Deployment on an O-Cloud. - -The following Use Case adopts terms from the high-level model described in Clause 4 of the OAM Architecture [5]. For definition purposes the terms adopted are defined below. However, if the definition is in conflict with the OAM Architecture, then the OAM Architecture will supersede these definitions. - -**DeploymentDescriptor:** The Deployment Descriptor describes a deployment option that has been validated by the Solution Provider of the application. The Deployment Descriptor contains design-time information and data that describes an application and that is used by the SMO for the deployment of the application workload. - -The NF Deployment instantiation on the O-Cloud may be part of a larger procedure instantiating multiple NF Deployments and of multiple connected Cloudified NFs, in which case the SMO will coordinate the timing of instantiation across O-Clouds and O-Cloud Nodes, the configuration of transport needed between O-Cloud Nodes and other requirements such as addressing and security used for connecting the Network Functions. - -The NF Deployment instantiation can also be performed in the context of an upgrade of a Cloudified NF. - -#### 3.2.1.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Instantiate an NF Deployment on the O-Cloud. | | -| Actors and Roles | NFO – Network Function Orchestration
DMS – Deployment Management Services | | -| Assumptions | 1) The DMS is aware of the capabilities of provisioned O-Cloud Node Cluster(s) and is able to select resources (e.g., O-Cloud Node/Site NW) that meet NF Deployment requirements. | | -| Preconditions | 1) SMO is available.
2) The O-Cloud instance has been installed successfully as per “O-Cloud Deployment Processing” use case.
3) NF Deployment package has been onboarded onto the SMO. The NF Deployment package contains a DeploymentDescriptor that provides the deployment and resource requirements for the NF Deployment.
4) The DeploymentDescriptor for the NF Deployment has been selected and runtime variables for the selected DeploymentDescriptor are determined.
5) Homing of the NF Deployment has been determined based on the infrastructure requirements in the DeploymentDescriptor and the specific absolute homing requirements (e.g., target O-Cloud) or relative constraints (e.g., affinities/anti-affinities). See note 1.
6) The O-Cloud Node Cluster has been provisioned (through the IMS) with capabilities required for the NF Deployments.
7) The DMS in the O-Cloud is available and connected to the SMO. | | -| Begins when | New NF Deployment is determined to be deployed on the O-Cloud. | | -| Step 1 (M) | NFO requests the DMS to instantiate the new NF Deployment. See note 2. | | -| Step 2 (M) | DMS allocates the resources according to the NF Deployment requirements (e.g., allocates O-Cloud Nodes from the O-Cloud Node Cluster that meet NF Deployment requirements such as CPU resources, multiple network interfaces, time-sync support, etc.). | | - -| | | | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | During the NF Deployment instantiation, initial configuration based on NFO's provided configuration values can take place, e.g., to enable NF Deployment connectivity. | | -| Step 3 (M) | NFO receives information about the NF Deployment instantiation completion. | | -| Ends when | NF Deployment has been instantiated on the O-Cloud. | | -| Exceptions | None identified. | | -| Post Conditions | NFO updates the composition of the Cloudified NF based on the NF Deployment instantiation, and Cloudified NF Registration follows (O-RAN WG10.O1-Interface [6], clause 6.10.1, which is out of scope for the present use case). | | -| Traceability | REQ-ORC-GEN18; REQ-ORC-GEN19; REQ-ORC-GEN20; REQ-ORC-O1-1; REQ-ORC-O2-10; REQ-DESC-1, REQ-DESC-2, REQ-DESC-3, REQ-ORC-GEN20a, REQ-ORC-GEN20b | | - -NOTE 1: This can range from a trivial exercise (e.g., the NF Deployment Request identifies the target O-Cloud by Cloud Id) to a highly complex exercise (if the SMO were to determine an appropriate vacant O-Cloud instance based on homing policies such as latency tolerance, NF Deployment requirements to cloud capability matching, etc.). - -NOTE 2: It is not precluded that one or multiple interactions between the NFO and DMS are performed for the NF Deployment instantiation. - -#### 3.2.1.3 UML sequence diagram - -![UML sequence diagram for NF Deployment Instantiation. Lifelines: Service Management & Orchestration Framework (NFO) and O-Cloud Platform (DMS). The sequence starts with a PRECONDITION: Homing of the NF Deployment has been determined based on infrastructure requirements in the DeploymentDescriptor and other information in the SMO. The main interaction is 'Instantiate NF Deployment' from NFO to DMS. A note indicates that multiple interactions between NFO and DMS are not precluded. Step 1: NFO sends '1 «O2» O2dms NF Deployment instantiation request' to DMS. Step 2: DMS performs 'Allocate resource according to NF Deployment request' (self-call). Step 3: DMS sends '3 «O2» O2dms NF Deployment instantiation response' back to NFO. The sequence ends with 'End of Use Case'.](f5deee2f3301ee351c4008283ffafbb3_img.jpg) - -``` - -sequenceDiagram - participant NFO as Service Management & Orchestration Framework (NFO) - participant DMS as O-Cloud Platform (DMS) - - Note right of NFO: PRECONDITION: -Homing of the NF Deployment has been determined based on infrastructure requirements in the DeploymentDescriptor and other information in the SMO. - - Note right of NFO: It is not precluded that one or multiple interactions between the NFO and DMS are performed for the NF Deployment instantiation. - - NFO->>DMS: 1 «O2» O2dms NF Deployment instantiation request - Note right of DMS: Allocate resource according to NF Deployment request - DMS-->>NFO: 3 «O2» O2dms NF Deployment instantiation response - - Note right of NFO: End of Use Case - -``` - -UML sequence diagram for NF Deployment Instantiation. Lifelines: Service Management & Orchestration Framework (NFO) and O-Cloud Platform (DMS). The sequence starts with a PRECONDITION: Homing of the NF Deployment has been determined based on infrastructure requirements in the DeploymentDescriptor and other information in the SMO. The main interaction is 'Instantiate NF Deployment' from NFO to DMS. A note indicates that multiple interactions between NFO and DMS are not precluded. Step 1: NFO sends '1 «O2» O2dms NF Deployment instantiation request' to DMS. Step 2: DMS performs 'Allocate resource according to NF Deployment request' (self-call). Step 3: DMS sends '3 «O2» O2dms NF Deployment instantiation response' back to NFO. The sequence ends with 'End of Use Case'. - -Figure 3-12: NF Deployment Instantiation - -### 3.2.2 NF Deployment Scale Out - -#### 3.2.2.1 High Level Description - -This use case describes an SMO initiated scale out of an NF Deployment in order to expand its capacity. This results in horizontal elasticity as allocating additional resources to the NF Deployment enables it to provide its functionality at the desired performance and capacity level. - -NOTE: An NF Deployment is part of a Cloudified NF, thus expanding the capacity of the NF Deployment consequently also expands the capacity of a Cloudified NF. - -#### 3.2.2.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To allocate additional resources to an NF Deployment on the O-Cloud to meet its service demands. | | -| Actors and Roles | SMO: NFO
DMS
NF Deployment | | -| Assumptions | 1) SMO has collected the necessary information to scale out the NF Deployment e.g., information from NF Deployment descriptor.
2) The NFO receives a trigger to scale out an NF Deployment.
3) NF Deployment monitoring is operational. | | -| Preconditions | 1) SMO is available
2) The DMS in the O-Cloud is available and connected to the SMO.
3) NF Deployment is instantiated. | | -| Begins when | SMO determines that scale out is needed and triggers the NFO to begin NF Deployment scale out. | | -| Step 1 (M) | The NFO requests the DMS to scale out the NF Deployment by providing updated scaling information. | | -| Step 2 (M) | The DMS scales the NF Deployment as per the received request by allocating the required resources to the NF Deployment. | | -| Step 3 (M) | The DMS informs the NFO that the NF Deployment scaling was performed successfully. | | -| Ends when | NF Deployment has been scaled out on the O-Cloud. | | -| Exceptions | DMS cannot allocate the required resources to scale out the NF Deployment. | | -| Post Conditions | If needed, reconfiguration of the NF Deployment may occur via the Cloudified NF and O1. | | -| Traceability | REQ-ORC-GEN22, REQ-ORC-GEN20a | | - -#### 3.2.2.3 UML sequence diagram - -![Sequence diagram for NF Deployment Scale Out between Service Management & Orchestration Framework (NFO) and O-Cloud Platform (DMS).](1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg) - -The diagram illustrates the interaction for 'Scale Out NF Deployment'. It features two lifelines: 'Service Management & Orchestration Framework' (NFO) on the left and 'O-Cloud Platform' (DMS) on the right. The sequence begins with a solid arrow labeled '1 «O2» O2dms NF Deployment scale out request' from NFO to DMS. A callout box states: 'It is not precluded that one or multiple interactions between the NFO and DMS are performed for the NF Deployment scale out.' Following the request, the DMS lifeline has a self-call labeled '2 Allocate resources according to Scale Out request'. Finally, a dashed return arrow labeled '3 «O2» O2dms NF Deployment scale out response' goes from DMS back to NFO. The sequence concludes with a box labeled 'End of Use Case'. - -Sequence diagram for NF Deployment Scale Out between Service Management & Orchestration Framework (NFO) and O-Cloud Platform (DMS). - -Figure 3-13: NF Deployment Scale Out - -### 3.2.3 NF Deployment Scale In - -#### 3.2.3.1 High Level Description - -This Use Case describes an SMO initiated scale in of an NF Deployment in order to reduce its capacity to the desired level. This results in horizontal elasticity and allows the NF Deployment to consume only the resources it needs based on the level of demand. - -#### 3.2.3.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To deallocate O-Cloud resources from an NF Deployment to reduce its capacity to the desired level. | | -| Actors and Roles | SMO: NFO
DMS
NF Deployment | | -| Assumptions | 1) SMO has collected the necessary information to scale in the NF Deployment e.g., information from NF Deployment descriptor.
2) The NFO receives a trigger to scale in an NF Deployment.
3) NF Deployment monitoring is operational. | | -| Preconditions | 1) SMO is available
2) The DMS in the O-Cloud is available and connected to the SMO.
3) The NF Deployment is instantiated. | | -| Begins when | SMO determines that NF Deployment scale in is needed and triggers the NFO to begin NF Deployment Scale In. | | -| Step 1 (M) | The NFO requests the DMS to scale in the NF Deployment by providing updated scaling information. | | -| Step 2 (M) | The DMS scales the NF Deployment as per the received request by deallocating resources from the NF Deployment. | | -| Step 3 (M) | The DMS informs the NFO that the NF Deployment scaling was performed successfully. | | -| Ends when | NF Deployment has been scaled in on the O-Cloud. | | -| Exceptions | DMS cannot deallocate the resources to scale in the NF Deployment. | | -| Post Conditions | If needed, reconfiguration of the NF Deployment may occur via the Cloudified NF and O1. | | -| Traceability | REQ-ORC-GEN23, REQ-ORC-GEN20a | | - -#### 3.2.3.3 UML sequence diagram - -![Sequence diagram for NF Deployment Scale In. Lifelines: Service Management & Orchestration Framework (NFO) and O-Cloud Platform (DMS). The process starts with 'Scale In NF Deployment', followed by a note about multiple interactions. Step 1: NFO sends '«O2» O2dms NF Deployment scale in request' to DMS. Step 2: DMS performs 'Deallocate resources according to Scale In request'. Step 3: DMS sends '«O2» O2dms NF Deployment scale in response' back to NFO. The process ends with 'End of Use Case'.](f5a5f52bc25d95a7f616290c99e88ae6_img.jpg) - -Sequence diagram for NF Deployment Scale In. Lifelines: Service Management & Orchestration Framework (NFO) and O-Cloud Platform (DMS). The process starts with 'Scale In NF Deployment', followed by a note about multiple interactions. Step 1: NFO sends '«O2» O2dms NF Deployment scale in request' to DMS. Step 2: DMS performs 'Deallocate resources according to Scale In request'. Step 3: DMS sends '«O2» O2dms NF Deployment scale in response' back to NFO. The process ends with 'End of Use Case'. - -Figure 3-14: NF Deployment Scale In - -### 3.2.4 NF Deployment Software Modification - -#### 3.2.4.1 Introduction - -NF Deployment software modification Use Case describes SMO-managed modification (upgrade or downgrade) to the software of the NF Deployment. - -Various approaches, such as build and replace, canary, blue-green, rolling deployment, and more complex scenarios can be used to minimize the risk of traffic loss and ensure smooth transitions during the NF Deployment software modification process. - -#### 3.2.4.2 Build and Replace Approach for NF Deployment Software Modification - -##### 3.2.4.2.1 High Level Description - -This Use Case describes SMO-managed modification (upgrade or downgrade) to the software of the NF Deployment implementing a build and replace approach. - -This approach utilizes a graceful or soft upgrade or downgrade where the existing NF Deployment is not deleted until a desired NF Deployment instance can substitute its functionality. - -##### 3.2.4.2.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------|-------------------------| -| Goal | To modify (upgrade or downgrade) the software version of a NF Deployment to the desired one. | | -| Actors and Roles | NFO
DMS | | - -| | | | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------| -| Assumptions | 1) The NF Deployment running in the O-Cloud has a software version different than the one desired in SMO. | | -| Preconditions | 1) SMO is available.
2) O-Cloud is available.
3) The DMS in the O-Cloud is available and connected to the SMO.
4) The existing (to be replaced) NF Deployment has been deployed.
5) The desired version of the NF Deployment software is available on the O-Cloud software image repository.
6) The O-Cloud platform has enough resources to support the instantiation and operation of the NF Deployment. | | -| Begins when | NF Deployment is determined to be modified on the O-Cloud with a desired software version. | | -| Step 1 (M) | NFO instantiates the desired NF Deployment (see clause 3.2.1).
NFO verifies if the desired NF Deployment is properly instantiated. | 3.2.1 NF Deployment Instantiation | -| Step 2.1 (ALT) | If the desired NF Deployment is behaving as expected, NFO triggers termination of the existing NF Deployment (see clause 3.2.5). | 3.2.5 NF Deployment Termination | -| Step 2.2 (ALT) | If there is a problem with the desired NF Deployment, NFO triggers termination of the desired NF Deployment (see clause 3.2.5). | 3.2.5 NF Deployment Termination | -| Ends when | The NF Deployment software has been modified to the desired version substituting the functionality of the existing NF Deployment. | | -| Exceptions | 1) Errors are encountered by the DMS or NFO on the desired NF Deployment software that trigger the rollback of the operation. | | -| Post Conditions | NF Deployment is changed to desired software version. | | -| Traceability | REQ-ORC-GEN33, REQ-ORC-GEN34, REQ-ORC-GEN35, REQ-ORC-GEN20a | | - -##### 3.2.4.2.3 UML sequence diagram - -![UML sequence diagram for NF Deployment Software Modification. Lifelines: NFO (Service Management & Orchestration Framework) and DMS (O-Cloud Platform). The diagram shows a 'Build and Replace Approach for NF Deployment Software Modification'. It includes a note stating that multiple interactions between NFO and DMS are possible. The process involves: 1. Instantiation (ref: O-Cloud NF Deployment Instantiation Use Case (Clause 3.2.1)) where the NFO sends a message '1 Instantiate the desired NF Deployment on O-Cloud' to the DMS. 2. A verification step: 'Verify that the desired NF Deployment is successfully instantiated'. 3. An alt block '[Desired NF Deployment instance is working as expected]' containing a 'Termination' block (ref: O-Cloud NF Deployment Termination Use Case (Clause 3.2.5)) with message '2.1 Terminate existing NF Deployment on O-Cloud'. 4. An alt block '[Problems with instantiation of the desired NF Deployment]' containing a 'Termination' block (ref: O-Cloud NF Deployment Termination Use Case (Clause 3.2.5)) with message '2.2 Terminate desired NF Deployment on O-Cloud'. The diagram ends with 'End of Use Case'.](4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg) - -UML sequence diagram for NF Deployment Software Modification. Lifelines: NFO (Service Management & Orchestration Framework) and DMS (O-Cloud Platform). The diagram shows a 'Build and Replace Approach for NF Deployment Software Modification'. It includes a note stating that multiple interactions between NFO and DMS are possible. The process involves: 1. Instantiation (ref: O-Cloud NF Deployment Instantiation Use Case (Clause 3.2.1)) where the NFO sends a message '1 Instantiate the desired NF Deployment on O-Cloud' to the DMS. 2. A verification step: 'Verify that the desired NF Deployment is successfully instantiated'. 3. An alt block '[Desired NF Deployment instance is working as expected]' containing a 'Termination' block (ref: O-Cloud NF Deployment Termination Use Case (Clause 3.2.5)) with message '2.1 Terminate existing NF Deployment on O-Cloud'. 4. An alt block '[Problems with instantiation of the desired NF Deployment]' containing a 'Termination' block (ref: O-Cloud NF Deployment Termination Use Case (Clause 3.2.5)) with message '2.2 Terminate desired NF Deployment on O-Cloud'. The diagram ends with 'End of Use Case'. - -Figure 3-15: NF Deployment Software Modification - -### 3.2.5 NF Deployment Termination - -#### 3.2.5.1 High Level Description - -This Use Case describes the termination of a NF Deployment on an O-Cloud, and response to the SMO once the termination of resources for the NF Deployment has been completed. - -#### 3.2.5.2 Sequence description - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | To terminate NF Deployment that has been instantiated in the O-Cloud. | | -| Actors and Roles | NFO
DMS | | -| Assumptions | 1) The SMO has identified the NF Deployment to be terminated.
2) The NF Deployment to be terminated does not provide services. | | -| Pre-condition | 1) SMO is available.
2) NF Deployment is instantiated.
3) The DMS in the O-Cloud is available and connected to the SMO. | | -| Begins when | Existing NF Deployment is determined to be terminated on the O-Cloud. | | -| Step 1 (M) | The NFO requests the DMS to terminate the NF Deployment by providing relevant information e.g. NF Deployment identifier. | | -| Step 2 (M) | The DMS terminates the NF Deployment and deallocates the O-Cloud resources assigned to that NF Deployment. | | -| Step 3 (M) | The DMS informs the NFO about the NF Deployment termination result. | | -| Ends when | NF Deployment in the O-Cloud has been terminated. | | -| Exceptions | DMS cannot terminate the requested NF Deployment due to, e.g. incorrect NF Deployment identifier, internal O-Cloud error, etc. | | -| Post Conditions | Termination is successful:
- NF Deployment has been terminated.
An Exception occurred:
- O-Cloud did not terminate NF Deployment. | | -| Traceability | REQ-ORC-O2-11 | | - -#### 3.2.5.3 UML sequence diagram - -![UML sequence diagram for NF Deployment Termination. Lifelines: Service Management & Orchestration Framework (NFO) and O-Cloud Platform (DMS). The sequence starts with a message '1 <> Terminate the NF Deployment' from NFO to DMS. A note indicates that multiple interactions may occur. The DMS then performs internal steps (2 NF Deployment termination) and sends a response '3 <> NF Deployment termination response' back to the NFO. The sequence ends with 'End of Use Case'.](69e5f1993021af230d08c08aac97d9df_img.jpg) - -``` - -sequenceDiagram - participant NFO as Service Management & Orchestration Framework (NFO) - participant DMS as O-Cloud Platform (DMS) - Note right of NFO: It is not precluded that one or multiple interactions between the NFO and DMS are performed for the NF Deployment termination. - NFO->>DMS: 1 «O2» Terminate the NF Deployment - Note right of DMS: The DMS determines the O-Cloud resources to deallocate for terminating the NF Deployment. - DMS->>DMS: 2 NF Deployment termination - DMS-->>NFO: 3 «O2» NF Deployment termination response - Note right of NFO: End of Use Case - -``` - -UML sequence diagram for NF Deployment Termination. Lifelines: Service Management & Orchestration Framework (NFO) and O-Cloud Platform (DMS). The sequence starts with a message '1 <> Terminate the NF Deployment' from NFO to DMS. A note indicates that multiple interactions may occur. The DMS then performs internal steps (2 NF Deployment termination) and sends a response '3 <> NF Deployment termination response' back to the NFO. The sequence ends with 'End of Use Case'. - -**Figure 3-16: NF Deployment Termination** - -## 3.3 Near-RT RIC/xAPP Use Cases - -### 3.3.1 Configure O-Cloud for Near-RT RIC - -#### 3.3.1.1 High Level Description - -This Use Case defines an optional procedure using Custom Resources to configure a Kubernetes O-Cloud to support the Near-RT RIC function by using, as an example, the Kubernetes® Custom Resource Definitions (CRD). - -NOTE 1: Similar procedure may be used for O-Cloud configuration for other functions as well. - -NOTE 2: Kubernetes® and K8s® are registered trademarks of the Linux Foundation, in the United States and other countries. O-RAN is not affiliated with, endorsed or sponsored by the Linux Foundation. - -The Near-RT RIC may require a Custom Resource to ensure proper lifecycle management of the near-RT RIC and its xAPPs. This capability has to be added to the O-Cloud prior to a near-RT RIC service deployment. There are multiple ways to add a custom resource. For example, Custom Resource Definitions (CRD) is easier and requires no programming. Another possibility is to use API Aggregation which requires programming but is more flexible in terms of API behaviors. Both options require a "service" in Kubernetes to be deployed. The following example illustrates the CRD initial installation. - -#### 3.3.1.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Enable the cloud to advertise to the SMO that it supports a Near-RT RIC deployment. | | -| Actors and Roles | Cloud Installation Project Manager
SMO: NFO
DMS | | -| Assumptions | O-Cloud is Kubernetes based and an instance of the Near-RT RIC Custom Resource Definition has not been previously installed | | -| Preconditions | 1) SMO is available
2) O-Cloud is available
3) Near-RT RIC Service Type Descriptor has been onboarded to the SMO | | -| Begins when | Cloud Installation Project Manager identifies that the O-Cloud is intended to support the deployment of a Near-RT RIC | | -| Step 1 (M) | Cloud Install Project Manager makes request to SMO to deploy the CRD Service to an O-Cloud enabling it to support Near-RT RIC deployments | | -| Step 2 (M) | The SMO decomposes the service request and identifies all O-Clouds to be enabled. | | -| Steps 3-5 | These steps are repeated for each O-Cloud to be enabled. | | -| Step 3 (M) | SMO request O-Cloud to create the CRD (Deploy Service) | | -| Step 4 (M) | DMS returns status update when created | | -| Step 5 (M) | The SMO recognizes that the O-Cloud can now support Near-RT RIC deployments and updates the O-Cloud Capabilities using the O-Cloud Inventory Update process in clause 3.1.4. | | -| Step 6 (M) | The SMO informs the Cloud Installation Project Manager of the overall success or failure of the request. | | -| Exceptions | O-Cloud cannot support CRD Service deployment or deployment fails. Deployment is cancelled and SMO is notified of failure. SMO informs Project Manager. | | -| Post Conditions | O-Cloud can support Near-RT RIC deployments.
SMO holds updated inventory. | | -| Traceability | | | - -#### 3.3.1.3 UML Sequence Diagram - -![UML Sequence Diagram for 'Configure O-Cloud for Near-RT RIC'. Lifelines: Personnel (Cloud Install Project Mgr), Service Management & Orchestration Framework (NFO), and O-Cloud Platform (DMS). The sequence includes steps: 1 Service Request, 2 determine homing, 3 deploy CRD Service, 4 notify CRD Service created, 5 Update Inventory, 6 Status (Success). It also includes sections for Building Block Identity, Assumptions, and Begin/End Building Block markers.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) - -**Building Block Identity & Legend** - -**Building Block : Configure Kubernetes Cloud for Near-RT RIC** - Orchestration Use Cases and Requirements for O-RAN Virtualized RAN - O-RAN-WG6.Orchestration-v03.00; section 3.1.3 - -**Assumptions and Prerequisites** - -near-RT RIC Custom Resource Definition Service Package has been onboarded to the SMO and is available for deployment. - O-Cloud is Kubernetes based and an instance of the near-RT RIC Custom Resource Definition **HAS NOT** been previously installed - Enablement of O-Cloud to host near-RT RIC deployments has been approved by operations and all conflicts has been resolved - -**Begin Building Block** - -``` - -sequenceDiagram - actor Personnel as Cloud Install Project Mgr - participant NFO as Service Management & Orchestration Framework - participant DMS as O-Cloud Platform - - Note right of NFO: The SMO determines which O-Cloud(s) to enable as identified by the Project Manager - - Personnel->>NFO: 1 Service Request - NFO->>NFO: 2 determine homing - loop for each O-Cloud to be near-RT RIC enabled - NFO->>DMS: 3 <> deploy CRD Service - DMS->>NFO: 4 <> notify CRD Service created - Note right of NFO: 5 Update Inventory for O-Cloud to indicate new Capability - end - NFO-->>Personnel: 6 Status (Success) - -``` - -**End Use Case** - -UML Sequence Diagram for 'Configure O-Cloud for Near-RT RIC'. Lifelines: Personnel (Cloud Install Project Mgr), Service Management & Orchestration Framework (NFO), and O-Cloud Platform (DMS). The sequence includes steps: 1 Service Request, 2 determine homing, 3 deploy CRD Service, 4 notify CRD Service created, 5 Update Inventory, 6 Status (Success). It also includes sections for Building Block Identity, Assumptions, and Begin/End Building Block markers. - -Figure 3-17: Configure O-Cloud for Near-RT RIC - -### 3.3.2 Deploy xAPP in Near-RT RIC - -#### 3.3.2.1 High Level Description - -xAPPs are developed independent of the near-RT RIC in which they execute. This Use Case describes how an xAPP is instantiated and associated with a near-RT RIC. - -#### 3.3.2.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | xAPP deployment is instantiated on Near-RT RIC, resulting in enhanced capabilities. Configuration and communication between xAPP and SMO is mediated by the ME containing the Near-RT RIC MF. | | -| Actors and Roles | xAPP Install Project Manager
NFO – Network Function Orchestration
OAM Functions
DMS – Deployment Management Services
Near-RT RIC
xAPP | | -| Assumptions | The “Service Request” to the SMO for the new xAPP(s) may include information for the SMO to use for homing purposes, such as desired xAPP or xAPP type(s) associated with O-Cloud or RIC Instance | | -| Preconditions | 1) SMO is available
2) The O-Cloud instance has been installed successfully as per “O-Cloud Deployment Processing” use case.
3) Near-RT RIC NF has been deployed successfully on the O-Cloud instance and has been activated and has connected to the SMO using O1
4) xAPP has been onboarded onto the SMO containing an xAPP descriptor that provides the deployment requirements for the xAPP.
5) No MOI exists for the xAPP in the Near-RT RIC
6) xAPP Install Project Manager has selected a deployment option from the Run Time Library and determined runtime variables for the selected option | | -| Begins when | New xAPP(s) are to be instantiated on a Near-RT RIC hosted on an O-Cloud | | -| Step 1 (M) | Network Function Install Project Manager makes request to SMO to deploy new xAPP(s) on the Near-RT RIC | | -| Step 2 (M) | The SMO decomposes the service request and identifies all xAPPs to be deployed and the order in which they should be deployed. | | -| Steps 3-15 | These steps are repeated for each xAPP to be deployed as part of the service request. | | -| Step 3 (M) | The SMO determines which O-Cloud and Near-RT RIC Instance to deploy the xAPP to. This can be done using Policies which match operator input or other more complex homing policies or can be explicitly identified by the Project Manager. | | -| Step 4 (O) | If SMO needs additional deployment-related information for the template override, e.g., the Near-RT RIC API NodePort assignment, SMO uses O1 to retrieve configuration data from the Near-RT RIC, otherwise SMO uses internal stored data | | -| Step 5 (M) | 1) SMO maps known RIC variables to xAPP variables to allow RIC and xAPP to interoperate and fills in the xAPP configuration with assigned values.
2) SMO uses config information to determine template override parameters for xAPP and create an override file (see Note) | | -| Step 6 (M) | For each xAPP Deployment of the xAPP, steps 6 - 10 take place: SMO retrieves the CloudNativeDescriptor from the Run Time Library for the current xAPP Deployment. | | -| Step 7 (M) | SMO directs the O-Cloud DMS using O2 to create the xAPP Deployment | | -| Step 8 (M) | DMS allocates the resources according to the xAPP Deployment request. During xAPP Deployment instantiation, initial SMO connectivity configuration can take place. | | -| Step 9 (M) | DMS returns notification to SMO over O2 indicating that the xAPP deployment has been created and the Deployment ID | | -| Step 10 (M) | SMO updates its xAPP inventory with the received Deployment ID | | -| Steps 11-14 (M) | The xAPP reads its initial configuration. Once complete, xAPP registers with the Near-RT RIC and exchanges its schemas and initial configuration as needed. Near-RT RIC uses this information to create and populate the xAPP MOI(s), including configuring E2 subscriptions, A1 Policies supported, A1 Enrichment Subscriptions, and inter xAPP data sharing. | | - -| | | | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 15 (O) | If the SMO has previously subscribed to CM notifications from the Near-RT RIC, then the Near-RT RIC sends SMO notification of an MOI create event. Note SMO will restart a new Netconf session to receive an update on Near-RT RIC capabilities including the newly deployed xAPP | | -| Steps 16 (M) | The SMO informs the Network Function Install Project Manager of the overall success or failure of the request. | | -| Ends when | xAPP(s) have been instantiated on the O-Cloud and configured by the SMO via the Near-RT RIC | | -| Exceptions | MOI Creation fails – Near RT RIC notifies SMO and SMO informs Network Function Install Project Manager
xAPP Deploy fails – DMS notifies SMO and SMO informs Network Function Install Project Manager | | -| Post Conditions | xAPP is instantiated and incorporated under near-RT RIC management.
SMO holds updated inventory that includes “deployment ID”
Near-RT RIC holds MOI of the xAPP. | | -| Traceability | REQ-ORC-GEN19, REQ-ORC-O1-2, REQ-ORC-O2-4 | | - -NOTE: Information could be, for example, RIC namespace, IP address or ports needed to access RIC services, as determined by WG3 - -#### 3.3.2.3 UML Sequence Diagram - -![UML Sequence Diagram for Deploy xAPP. Lifelines: Personnel (xAPP Install Project Mgr), Service Management & Orchestration Framework (Run Time Library, NFO, OAM Functions), O-Cloud Platform (DMS), and O-RAN (near-RT RIC, xAPP). The sequence shows the deployment process from request to status update, including homing, configuration, and resource allocation steps.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) - -``` - -sequenceDiagram - actor Personnel as xAPP Install Project Mgr - participant SMO as Service Management & Orchestration Framework - participant OCP as O-Cloud Platform - participant ORAN as O-RAN - - Note right of SMO: Run Time Library, NFO, OAM Functions - Note right of OCP: DMS - Note right of ORAN: near-RT RIC, xAPP - - Personnel->>SMO: 1 Deployment Request - SMO->>SMO: 2 Decompose and determine sequence - Note right of SMO: The SMO determines the correct sequence for deploying the xAPPs - loop for each xAPP to be deployed - SMO->>SMO: 3 Determine homing - Note right of SMO: The SMO determines on which RIC/O-Cloud to deploy this/these xAPP(s). This can be explicitly identified by the Operations Personnel or via homing policies - opt SMO needs additional information from Near-RT RIC - SMO->>ORAN: 4 <> get-config - Note right of SMO: SMO maps known RIC variables to xAPP variables to allow RIC and xAPP to interoperate, and fills in the xAPP configuration with assigned values. - end - SMO->>SMO: 5 SMO uses RIC/xAPP config to create template override parameters. - loop foreach xAPP Deployment - SMO->>SMO: 6 Get CloudNativeDescriptor for xAPP Deployment - SMO->>OCP: 7 <> xAPP Deployment Request (CloudDescriptor, RuntimeVariables) - OCP->>ORAN: 8 Allocate resource according to xAPP Deployment request - ORAN->>SMO: 9 notify xAPP Deployment instantiation is completed (DeploymentID) - Note right of SMO: Once complete, SMO updates its xAPP inventory record with the Deployment ID from the O-Cloud - SMO->>SMO: 10 - Note right of ORAN: xAPP reads its initial configuration - ORAN->>ORAN: 11 - ORAN->>ORAN: 12 Register (RTE Descriptor) - ORAN->>ORAN: 13 xAPP exchanges schemas and initial config with RIC - Note right of ORAN: The Near-RT RIC configures E2 subscriptions, A1 Policies supported, A1 Enrichment Subscriptions, and inter xAPP data sharing. - ORAN->>ORAN: 14 RIC creates and populates xAPP MOI - alt if SMO has subscribed to CM Notifications then - SMO->>ORAN: 15 <> MOI Create Event - end - end - end - SMO->>Personnel: 16 xAPP Deployment status (Success) - Note right of SMO: Run Time Library, NFO, OAM Functions - Note right of OCP: DMS - Note right of ORAN: near-RT RIC, xAPP - actor Personnel as xAPP Install Project Mgr - -``` - -UML Sequence Diagram for Deploy xAPP. Lifelines: Personnel (xAPP Install Project Mgr), Service Management & Orchestration Framework (Run Time Library, NFO, OAM Functions), O-Cloud Platform (DMS), and O-RAN (near-RT RIC, xAPP). The sequence shows the deployment process from request to status update, including homing, configuration, and resource allocation steps. - -Figure 3-18: Deploy xAPP - -## 3.4 Multi-vendor network provisioning in a mixed PNF/VNF environment - -A Use Case description of multi-vendor provisioning of an O-RAN service can be found in the O-RAN OAM Architecture specification [5]. - -## 3.5 Reconfiguration of O-RAN Virtual Network Function(s) - -### 3.5.1 High Level Description - -A common orchestration request is the reconfiguration of one or a set of cloud-based O-RAN Virtual Network Functions in order to affect the behavior of the RAN. The action taken could be, for example, to re-optimize network traffic patterns or update the load balancing of traffic across the RAN network. The trigger for this action could be any - -number of events such as non-real time traffic analysis by the Non-RT RIC, or input from non-RAN sources such as upcoming natural events or scheduled human events. - -In such cases the SMO will either be told or determine by its own analysis which Virtual Network Functions need reconfiguration and in which order this is done if multiple Virtual Network Functions are involved. If a problem develops during reconfiguration then SMO may optionally invoke a fallback procedure to revert the Virtual Network Functions to their original configuration. As in reconfiguration of PNFs, O1 Interface [6] Provisioning Management is used. - -NOTE: There may be a need for SMO to initially reroute traffic away from the affected Virtual Network Functions and subsequently revert traffic to the original patterns. This could be done by using Network Function Reconfiguration on adjacent Network Functions that send or receive information from the affected Network Functions. - -### 3.5.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Reconfigure O-RAN Virtual Network Functions based on the need to modify RAN network behavior, for example re-optimize traffic patterns or load balance traffic in response to new conditions. | | -| Actors and Roles | SMO: OAM Functions
SMO/Non-RT RIC: source point for RAN policy control function
Other RAN Elements: O-CU, O-DU | | -| Assumptions |
  1. 1) All relevant functions and components are instantiated.
  2. 2) O1 interface connectivity is established with RAN elements.
  3. 3) SMO will reconfigure transport as needed to accommodate traffic rerouting, reconfigured network functions and traffic reversion
| | -| Preconditions |
  1. 1) Network is operational.
  2. 2) SMO has established the data collection and sharing process, and SMO/Non-RT RIC has access to this data.
  3. 3) Trigger conditions for reconfiguration are set in the SMO/Non-RT RIC, e.g., by the network operator.
| | -| Begins when | SMO/Non-RT RIC analyses performance data or other inputs and determines that reconfiguration of RAN network functions is required. | | -| Step 1 (M) | SMO/Non-RT RIC request NF reconfiguration. SMO/OAM Functions determines an order of reconfiguration across affected RAN network functions. | | -| Step 2-4 (M) | SMO performs relevant configuration updates in RAN over O1 interface for each network function that needs to be reconfigured, in an order determined by SMO or specified to SMO. Detailed procedures for O1 provisioning follow [6] section 2.1. | | -| Step 5-7 (M) | SMO determines via notification from the affected network functions that reconfiguration has been successful | | -| Step 8 (M) | SMO/Non-RT RIC monitors the performance of the RAN following reconfiguration by collecting and monitoring the relevant performance KPIs and counters using O1 | | -| Step 9-11 (O) | If a fallback procedure has been identified by SMO and it determines that reconfiguration has not been successful, SMO initiates fallback by configuring the affected network functions back to their original configuration. | | -| Ends when | The SMO/Non-RT RIC verifies that the O-RAN Virtual Network Function's performance monitoring conforms to the reconfiguration. | | -| Exceptions | None identified | | -| Post Conditions | O-RAN Virtual Network Functions have been reconfigured.
SMO/Non-RT RIC continues to monitor the performance of the RAN by collecting and monitoring the relevant performance KPIs and counters using O1 | | -| Traceability | REQ-ORC-GEN21; REQ-ORC-O1-2 | | - -### 3.5.3 UML sequence diagram - -![UML sequence diagram for Reconfiguration. Lifelines: Service Management and Orchestration Framework (OAM Functions, Non-RT RIC), O-Cloud (DMS), O-RAN (O-CU, O-DU 1, O-DU N). The diagram shows a process starting with a request for NF reconfiguration, followed by an analysis, a reconfiguration procedure, performance monitoring, and an optional fallback procedure.](9e8ebf03cae78f4f81b697548c2d7250_img.jpg) - -``` - -sequenceDiagram - participant SMF as Service Management and Orchestration Framework - subgraph SMF [Service Management and Orchestration Framework] - OAM[OAM Functions] - RIC[Non-RT RIC] - end - subgraph OC [O-Cloud] - DMS[DMS] - end - subgraph ORAN [O-RAN] - OCU[O-CU] - ODU1[O-DU 1] - ODUN[O-DU N] - end - - Note right of RIC: Non-RT RIC analyses RAN and non-RAN data and determines reconfiguration is needed - RIC->>OAM: 1 Request NF reconfiguration - Note over SMF: NF Reconfiguration Procedure - Note left of OAM: OAM Functions determines an order of NF reconfiguration across affected RAN NF. - Note over SMF: For all NFs in set to be reconfigured - Note right of RIC: Reconfigure NF set in order - detailed procedures follow O1 spec [6] - RIC->>OCU: 2 <> Parameter configuration update - RIC->>ODU1: 3 <> Parameter configuration update - RIC->>ODUN: 4 <> Parameter configuration update - Note over SMF: SMO monitors resulting performance of RAN - RIC->>OAM: 5 <> Data collection - RIC->>OAM: 6 <> Data collection - RIC->>OAM: 7 <> Data collection - Note right of RIC: SMO/Non-RT RIC analyzes RAN and non-RAN data - RIC->>RIC: 8 Evaluation - Note over SMF: Optional Fallback Procedure - Note over SMF: opt fallback - Note right of RIC: Fallback NF set to previous config - RIC->>OCU: 9 <> Parameter configuration update - RIC->>ODU1: 10 <> Parameter configuration update - RIC->>ODUN: 11 <> Parameter configuration update - -``` - -UML sequence diagram for Reconfiguration. Lifelines: Service Management and Orchestration Framework (OAM Functions, Non-RT RIC), O-Cloud (DMS), O-RAN (O-CU, O-DU 1, O-DU N). The diagram shows a process starting with a request for NF reconfiguration, followed by an analysis, a reconfiguration procedure, performance monitoring, and an optional fallback procedure. - -Figure 3-19: Reconfiguration - -## 3.6 Recovery Use Cases - -### 3.6.1 Introduction - -When an operator experiences problems with an O-Cloud NF Deployment(s), O-Cloud Node(s), or O-Cloud instance, it is possible for the operator to initiate a recovery at different levels of the O-Cloud. - -These can include the following: - -#### 1. Application-level healing - -This causes an application within an NF on the O-Cloud to be healed on operator request, and is accomplished through the O1 interface between SMO and the associated NF. Typically, the network operator tries to execute the Application level healing as part of recovering from NF's application failures via O1. - -The Application level healing is out of scope of the present document since it is foreseen that the interactions are only on the O1 interface. - -#### 2. NF Deployment level healing (refer to clause 3.6.2) - -Another level of healing is by acting upon the NF Deployments (e.g., workloads in Kubernetes case) that realize an NF instance, where either the network operator can execute the NF Deployment level healing via O2dms, or the O-Cloud internal deployment management functions can execute built-in or configured procedures for auto-healing of the NF Deployment, e.g., based on workload monitoring in O-Cloud. - -When the healing of an NF Deployment within an O-Cloud is triggered via an operator request, it is accomplished through the O2dms interface between SMO and the DMS responsible for the deployment management services of the NF Deployment of concern. - -In the case of auto-healing, the DMS may automatically trigger healing of the NF Deployment, where no operator request over O2dms interface is necessary. - -#### 3. O-Cloud Node level healing (refer to clause 3.6.3) - -This causes one or more O-Cloud Nodes within an O-Cloud to be healed on operator request, and is accomplished through the O2ims interface between SMO and the IMS responsible for infrastructure management services for that O-Cloud Node. This can be used as part of recovery of the resources within the O-Cloud, i.e., the O-Cloud Node level healing. It is also possible that IMS executes built-in or configured procedures for auto-healing of the O-Cloud Node. This level of healing needs extra trigger considerations because it can affect multiple NFs running on the O-Cloud Node(s). For instance, "draining" the O-Cloud Node (i.e., migrating the NF deployments out from the affected O-Cloud Node) and/or setting the O-Cloud Node into maintenance mode can be done before requesting the O-Cloud Node healing. Related NF deployment requirements from the NF deployment descriptor and cloud native descriptors that are available to the O-Cloud DMS are taken into consideration as part of the O-Cloud Node healing (e.g., graceful evacuation of Pods based on Pod disruption budgets set for that NF). - -In the case of auto-healing, the IMS may automatically trigger healing of the O-Cloud Node, where no operator requires over O2ims interface is necessary. - -#### 4. O-Cloud instance level healing - -This causes an O-Cloud instance to be healed on operator request. This last level of healing, i.e., O-Cloud instance level healing, can be seen as a last resort action and it needs extra trigger considerations because it can affect multiple NFs and O-Cloud Nodes residing in the O-Cloud instance. - -*Editor's Note: It is for further study whether this can be accomplished through the O2 interface.* - -The ordering or which one of the healings to use or execute is up to network operator policies, e.g., in some cases a cascading might be tried, while in other cases the operator might decide to activate a specific healing without cascading among them. - -For illustrative purposes, the following is explanation about typical system reset cases in legacy deployments. In legacy deployment cases, when the xNB experiences some issue at the software level, e.g., the software on the xNB is not responding to the operations of the remote management tool due to possible software failures, "physical hardware" level reset is performed to re-gain software level control. For performing this action, typically an OSS sends a "system reset" signal to the target xNB. This procedure is necessary to reset the system (CU and DU) in xNB without performing a "manual intervention" at the radio antenna site, e.g., "personnel pushing power button". Figure 3-16 illustrates an - -example of remote system reset in the legacy deployment case. System reset does not apply in exactly the same way for recovery of NF and O-Cloud systems but healing at different levels can be supported using O2 as described above. - -![Sequence diagram showing OSS sending 'Not responding' and 'Hardware reset' messages to xNB. The xNB is divided into 'software' and 'hardware' sections. A red starburst labeled 'Failure' is on the software section.](7ed5d5770331f31ade15439a21c31425_img.jpg) - -``` - -sequenceDiagram - participant OSS - participant xNB - Note right of xNB: Failure (software) - OSS->>xNB: Not responding - xNB-->>OSS: - OSS->>xNB: Hardware reset - xNB-->>OSS: - -``` - -Sequence diagram showing OSS sending 'Not responding' and 'Hardware reset' messages to xNB. The xNB is divided into 'software' and 'hardware' sections. A red starburst labeled 'Failure' is on the software section. - -Figure 3-20: Remote System Reset of legacy xNB by OSS - -### 3.6.2 Network Function Deployment Level Healing Use Case - -#### 3.6.2.1 High Level Description - -Depending on the O-Cloud technology, in some cases the capability of auto-healing of the NF deployments is available intrinsically in the O-Cloud platform. In that case, the NF deployment requirements from the NF deployment descriptors and cloud native descriptors are taken into account together with the runtime state of the NF Deployment in O-Cloud, to activate the NF Deployment auto-healing process. - -When such O-Cloud DMS capability is not available or there is a need for an operator triggered recovery as one or more O-RAN NF(s) is (are) experiencing some failure, and the error could not be fixed by using the O1 interface services, then as a possible step, the network operator could trigger SMO to request the DMS to perform an NF Deployment level healing to attempt to fix the problem. - -The healing of an NF Deployment may be performed via different means depending on the type of resources required for the NF Deployment (e.g., VM or container). For instance, both in VM-based and container-based NF Deployments, the capability to restart the VM or OS Container/Pod can be leveraged. The NF Deployment could be restarted (stop and start), or its associated resources be reallocated/replaced on the same or different O-Cloud Nodes. - -NOTE: Alternatively, if the O-Cloud cannot perform the healing, new NF Deployment instances can be created on O-Cloud Nodes with resources of equivalent characteristics and profile as defined in that NF deployment descriptors and cloud native descriptors. This can be performed in the context of service recovery, not a healing of a specific NF Deployment. - -This use case describes the procedure to attempt to heal specific NF Deployments using the O2dms interface services. - -#### 3.6.2.2 Sequence description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|---------------------------|-------------------------| -|----------------|---------------------------|-------------------------| - -| | | | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Goal | SMO and DMS attempt to fix the failure on O-RAN NF's responsiveness, via the O2 interface by requesting the healing of the associated NF Deployments. | | -| Actors and Roles | Network Operator
SMO: NFO/OAM Functions
DMS
NF Deployment | | -| Assumptions | 1) Notification Event has been configured in the DMS by the SMO to inform SMO of issues with NF deployments
2) NF does not respond on O1
3) SMO can be aware of NF Deployments failures, e.g., via notifications (see 1)) | | -| Preconditions | 1) SMO is available
2) The O-Cloud has been installed and activated and is known to SMO
3) The O2 interface exists between the O-Cloud and SMO and is functional. | | -| Begins when | This use case begins when either of the following two situations happens:
1. Network operations has determined, either by explicit request or via some network operation policies , to trigger the NF Deployment level healing and SMO has a work order with the specific set of NF Deployments to heal.
2. DMS detects some faults with NF Deployment and triggers auto-healing | | -| Step 1.1 (ALT) | SMO requests to the DMS using O2dms services to heal one or more NF Deployments. | | -| Step 1.2 (ALT) | DMS initiates auto-healing | | -| Step 2(O) | If SMO has previously subscribed to the status update of the NF Deployment, DMS notifies SMO of the start of healing.

NOTE 1: The notification may be sent in both cases before SMO-initiated healing and auto-healing. | | -| Step 3 (M) | The DMS performs the healing of the NF Deployments indicated in the request or determined via auto-healing.

NOTE 2: Step 3 can be looped for each NF Deployments to heal.
NOTE 3: Regarding the “healing” mechanisms, see also description in clause 3.6.2.1. | | -| Step 4 (O) | STATUS UPDATE NOTIFICATION – When the situation requires that a NF Deployment status change notification to the SMO is needed, the NF Deployment status change notification is returned to the SMO by the DMS.

NOTE 4: The notification may be sent in both cases after SMO initiated healing and auto-healing. | | -| Ends when | Healing of NF Deployment(s) is completed. | | -| Exceptions | None identified. | | -| Post Conditions | NF Deployments have been healed. | | -| Traceability | REQ-ORC-02-12, REQ-ORC-02-77 | | - -#### 3.6.2.3 UML sequence diagram - -![UML sequence diagram for NF Deployment level recovery. Lifelines: Personnel (Network Operator), Service Management & Orchestration Framework (NFO), and O-Cloud Platform (DMS). The process involves SMO initiate healing, auto-healing, and optional status updates.](9b1ec0090070bdf52ea28763b8d52477_img.jpg) - -``` - -sequenceDiagram - actor Network Operator as Network Operator - participant NFO as Service Management & Orchestration Framework (NFO) - participant DMS as O-Cloud Platform (DMS) - - Note right of NFO: NF Deployment Healing - - alt SMO Initiate Healing: Operator triggers via SMO, NF Deployment Healing for one or More NF Deployments - NFO->>DMS: 1.1 <> Heal NF Deployment(s) - Note right of DMS: DMS processes request. - Note right of DMS: 1.2 Auto-healing Trigger - else Auto-healing - end - - Note right of NFO: 2 (Optional) NF Deployment status update notification (Healing start) - Note right of DMS: loop for each NF Deployment to be healed - Note right of DMS: 3 DMS heals NF Deployment - end - Note right of NFO: 4 (Optional) NF Deployment status update notification (Success/Failure) - - Note right of NFO: End Use Case - -``` - -UML sequence diagram for NF Deployment level recovery. Lifelines: Personnel (Network Operator), Service Management & Orchestration Framework (NFO), and O-Cloud Platform (DMS). The process involves SMO initiate healing, auto-healing, and optional status updates. - -Figure 3-21:NF Deployment level recovery - -### 3.6.3 O-Cloud Node Level Healing Use Case - -#### 3.6.3.1 High Level Description - -Depending on the O-Cloud technology, in some cases the capability of auto-healing of the O-Cloud Nodes is available intrinsically in the O-Cloud platform. - -When such O-Cloud IMS capability is not available or there is a need for an operator triggered recovery as one or more O-RAN NF(s) is (are) experiencing some failure, and the error could not be fixed by using the O1 or O2dms interface services, then as a possible step, the network operator could trigger SMO to request the IMS to perform an O-Cloud Node level healing to attempt to fix the problem. In addition, certain events received by SMO about malfunctioning O-Cloud Node resources could indicate or trigger the need to heal those resources, even in the case that such resource is not actually being allocated for running the whole or part of an O-RAN NF. - -The healing of an O-Cloud Node may be performed via different means. For instance, the O-Cloud Node could be restarted (stop and start the node) or reallocated to use other O-Cloud Resources or O-Cloud Infrastructure resources. - -This use case describes the procedure to attempt to heal specific O-Cloud Nodes using the O2ims interface services. This procedure can be invoked when some faults are identified that could be resolved by healing O-Cloud Nodes. - -#### 3.6.3.2 Sequence description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | SMO and IMS attempt to fix the failure on O-RAN NF's responsiveness via O1 interface by requesting the healing of O-Cloud Nodes. | | -| Actors and Roles | Network Operator
SMO: FOCOM
IMS
O-Cloud Node | | - -| | | | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Assumptions | 1) Notification Event has been configured in the IMS by the SMO
2) NF does not respond on O1
3) SMO can be aware of O-Cloud Nodes failures | | -| Preconditions | 1) SMO is available
2) The O-Cloud has been installed and activated and is known to SMO
3) Network connectivity exists between the O-Cloud and SMO | | -| Begins when | This use case begins when either of the following two situations happens:
1. Work order from the network operator triggers the O-Cloud Node level healing. The work order can indicate a specific set of O-Cloud Nodes.
2. IMS detects some faults with O-Cloud Node and triggers auto-healing. | | -| Step 1.1 (ALT) | SMO sends a request to the IMS using O2ims services to heal one or more O-Cloud Nodes. | | -| Step 1.2 (ALT) | IMS initiates auto-healing | | -| Step 2 (O) | If SMO has previously subscribed to the status update of the O-Cloud Node. IMS notifies the start of healing.

NOTE 1: The notification may be sent in both cases before SMO initiated healing and auto-healing. | | -| Step 3 (M) | The IMS performs the healing of the O-Cloud Nodes indicated in the request.

NOTE 2: Steps 3 and 4 can be looped for each O-Cloud Nodes to heal.
NOTE 3: NF Deployments running on the O-Cloud Node may need to be healed in conjunction with the O-Cloud Node healing. | | -| Step 4 (O) | NF Deployments are reallocated as needed. | | -| Step 5 (O) | STATUS UPDATE NOTIFICATION – When the situation requires that an O-Cloud Node status change notification to the SMO is needed, the O-Cloud Node status change notification is returned to the SMO by the IMS.

NOTE 4: The notification may be sent in both cases after SMO initiated healing and auto-healing. | | -| Ends when | Healing of the O-Cloud Node is completed. | | -| Exceptions | None identified. | | -| Post Conditions | O-Cloud Nodes have been healed. | | -| Traceability | REQ-ORC-O2-13, REQ-ORC-O2-78 | | - -#### 3.6.3.3 UML sequence diagram - -![UML sequence diagram for O-Cloud Node level recovery. Lifelines: Personnel (Network Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The diagram shows an 'O-Cloud Node Healing' use case with an 'alt' block for 'SMO Initiate Healing' and 'IMS Autonomous Healing'. It includes message exchanges for healing requests, status updates, and a loop for healing each node.](65e8c0628536d6d4245e9ab46ba070c3_img.jpg) - -``` - -sequenceDiagram - actor Network Operator as Network Operator - participant FOCOM as Service Management & Orchestration Framework (FOCOM) - participant IMS as O-Cloud Platform (IMS) - - Note right of FOCOM: O-Cloud Node Healing - - alt SMO Initiate Healing: Operator triggers via SMO O-Cloud Node Healing for one or More O-Cloud Nodes - FOCOM->>IMS: 1.1 <> Heal O-Cloud Node(s) - Note right of IMS: IMS processes request. - else IMS Autonomous Healing: - IMS->>IMS: 1.2 Auto-healing Trigger - end - - Note right of FOCOM: End Use Case - - FOCOM->>IMS: 2 (Optional) O-Cloud Node status update notification (Healing start) - - loop for each O-Cloud Node to be healed - IMS->>IMS: 3 IMS heals O-Cloud Node - IMS->>IMS: 4 NF Deployment reallocated as needed - end - - FOCOM->>IMS: 5 (Optional) O-Cloud Node status update notification (Success/Failure) - -``` - -UML sequence diagram for O-Cloud Node level recovery. Lifelines: Personnel (Network Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The diagram shows an 'O-Cloud Node Healing' use case with an 'alt' block for 'SMO Initiate Healing' and 'IMS Autonomous Healing'. It includes message exchanges for healing requests, status updates, and a loop for healing each node. - -Figure 3-22: O-Cloud Node level recovery - -### 3.6.4 O-Cloud Node Backup Use Cases - -#### 3.6.4.1 Introduction - -The use cases introduced in clause 3.6.4 concern about O-Cloud Node backup. - -When an O-Cloud Node experiences some failure, the O-Cloud Node can be healed by restarting or reallocating the O-Cloud Node on other O-Cloud Resources, as described in the O-Cloud Node Level Healing Use Case, clause 3.6.3 of the present document. In order to reallocate an O-Cloud Node, information and current state data about the O-Cloud Node is necessary. This is referred in the following as "O-Cloud Node backup". - -The O-Cloud Node backup might be automatically created by the O-Cloud based on certain policy or configuration. In other cases, O-Cloud Operator might explicitly request to create an O-Cloud Node backup. - -The following set of use cases describe the procedure to create an O-Cloud Node backup initiated by O-Cloud Operator, SMO, or IMS based on backup criteria. - -SMO can specify the information to backup within the O-Cloud Node Backup request. The specific items to backup for each O-Cloud Node could differ based on implementation, but in all cases, it needs to contain the necessary items for restoration and rollback. The followings are the examples of information and data to be backed up: - -- Running configurations of O-Cloud Node, or -- O-Cloud inventory information (such as its type, capabilities, and resource build configurations, for example, a reference to the Initiation Configuration Set (ICS) that has been used for O-Cloud Node initialization) as described in O-Cloud Inventory Update Use Case, clause 3.1.4, or -- O-Cloud blueprint of the functionality and resources as described in [REQ-ORC-GEN14]. - -It is useful to create a backup before update in order to be able to rollback to the original state in case of a failure during the update procedure. In addition to the backup before update, automatic or periodic backup is also useful to restore the - -latest information in case of unexpected failure of O-Cloud Node. The probable triggers to create an O-Cloud Node Backup are: - -- after initialization of new O-Cloud Node, -- before software update on O-Cloud Node for rollback in case of update failure, -- before reconfiguration of O-Cloud Node for fallback in case of problem during reconfiguration, -- on a request from O-Cloud Operator, -- periodical backup timer (done in case of unexpected failure of O-Cloud Node), and -- automatic backup based on backup criteria configured on the IMS. - -NOTE 1: It is not a mandatory procedure to create a backup after O-Cloud Node initialization or before O-Cloud Node update. - -SMO can configure the backup criteria on the IMS such as backup target, interval, threshold, and trigger for automatic/periodic backup. - -O-Cloud Node backup can be initiated by the O-Cloud Operator and SMO. O-Cloud Node backup can be also initiated by IMS based on backup criteria. O-Cloud Operator can query the backup status of O-Cloud Node or backed-up O-Cloud Node information itself by using the O-Cloud Node Backup Query Use Case (see clause 3.6.4.4). - -In the following, clause 3.6.4.2 describes the O-Cloud Node backup creation initiated by O-Cloud Operator or SMO. Clause 3.6.4.3 describes the backup criteria configuration on the IMS and O-Cloud Node backup creation based on the backup criteria. And finally, clause 3.6.4.4 describes the O-Cloud Node backup query. - -NOTE 2: O-Cloud Node backup request and O-Cloud Node backup criteria configuration by SMO provide the means to SMO and O-Cloud Operator to control the backup process considering aspects beyond the current status of the O-Cloud, e.g., network wide level management, etc. However, it is also possible that IMS can have pre-configured or perform by design O-Cloud Node backups by itself. - -NOTE 3: The present use case considers only aspects of backup applied to O-Cloud Nodes. However, backup processes can also be applicable to other O-Cloud components and resources. How the use case could be further evolved or related to other use cases of backing up other O-Cloud components is not handled in the present document version, and it might be considered in future ones to realize a broader concept of O-Cloud Backup. - -NOTE 4: Requirements for these use cases are for further study in future train. - -#### 3.6.4.2 O-Cloud Node Backup Creation Use Case - -##### 3.6.4.2.1 High Level Description - -This use case describes the creation of an O-Cloud Node backup triggered by the O-Cloud Operator or SMO. - -##### 3.6.4.2.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Create an O-Cloud Node backup, i.e., a backup of specified information on an existing O-Cloud Node. | | -| Actors and Roles | O-Cloud Operator – The O-Cloud Operator is an entity interfacing with the SMO.
SMO: FOCOM – The FOCOM within the SMO is the consumer that will request the O-Cloud Node backup.
IMS – The IMS processes the request of O-Cloud Node backup. | | -| Assumptions | IMS supports backup mechanism without affecting related NF deployments and consumed O-Cloud resources. | | -| Pre-conditions | 1) SMO is available
2) The O-Cloud has been installed and activated and is known to SMO | | - -| | | | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | 3) Network connectivity exists between the O-Cloud and SMO
4) Privilege - The consumer identification and privileges have been verified to be able to perform O2 operations | | -| Begins when | This use case begins in either of these two cases:
1. The O-Cloud Operator initiates an O-Cloud Node backup creation request
2. The SMO initiates an O-Cloud Node backup creation request | | -| Step 1.1 (ALT) | BACKUP CREATION INITIATED BY OPERATOR – An O-Cloud Node backup creation request is initiated from the O-Cloud Operator towards SMO. O-Cloud Operator can specify the information to backup. | | -| Step 1.2 (ALT) | BACKUP CREATION INITIATED BY SMO – An O-Cloud Node backup creation is initiated by the SMO. | | -| Step 2 (M) | BACKUP CREATION REQUEST - The O-Cloud Node backup creation request is composed by the SMO and sent to the IMS. | | -| Step 3 (M) | IMS PROCESSES BACKUP CREATION REQUEST - The IMS processes the backup creation request. The IMS creates a backup of the requested O-Cloud Node information. | | -| Step 4.1 (ALT) | BACKUP SUCCESS – The backup creation was successfully performed by the IMS without any issues. A success response is returned to the SMO by the IMS. The response can include information about the backup that has been performed, such as time of backup, backed-up version, etc. | | -| Step 4.2 (ALT) | EXCEPTION: UNEXPECTED CONDITION – The IMS might not be able to comply to the request. A response is sent from the IMS to the SMO. | | -| Step 5 (M) | BACKUP CREATION RESPONSE – If the backup creation request has been initiated by the O-Cloud Operator, a backup creation response is sent back to the requesting entity. The response can include information about the backup that has been performed, such as time of backup, backed-up version, etc. | | -| Ends when | The O-Cloud Node backup has been created successfully or when IMS encounters an unexpected condition. | | -| Exceptions | IMS was unable to create a backup of the O-Cloud Node due to unexpected conditions. | | -| Post-conditions | SUCCESS: The O-Cloud Node backup is created and a response to the backup creation request is sent to the requesting entity.
FAILURE: The exception response has been sent to the requesting entity. | | -| Traceability | The requirement traceability is not present in this document version. | | - -##### 3.6.4.2.3 UML Sequence Diagram - -![UML Sequence Diagram for O-Cloud Node Backup Creation. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The sequence starts with an alt block '[Operator Initiate Backup Creation]' containing message 1.1 'Backup Creation Request' from Operator to FOCOM, and message 1.2 'Backup Creation Trigger' from FOCOM to FOCOM. This is followed by message 2 'Backup Creation Request' from FOCOM to IMS, and message 3 'IMS Processes Backup Creation Request' as a self-call on IMS. An alt block '[Successful Backup Creation]' contains message 4.1 'Backup Status (Success)' from IMS to FOCOM and message 4.2 'Unexpected Condition' from IMS to FOCOM (labeled as 'Failure Case'). Finally, message 5 'Backup Creation Response' is sent from FOCOM to Operator, and the sequence ends with 'End O-Cloud Node Backup Creation Use Case'.](575d7d345b3ec04393bb2ec720ebabca_img.jpg) - -UML Sequence Diagram for O-Cloud Node Backup Creation. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The sequence starts with an alt block '[Operator Initiate Backup Creation]' containing message 1.1 'Backup Creation Request' from Operator to FOCOM, and message 1.2 'Backup Creation Trigger' from FOCOM to FOCOM. This is followed by message 2 'Backup Creation Request' from FOCOM to IMS, and message 3 'IMS Processes Backup Creation Request' as a self-call on IMS. An alt block '[Successful Backup Creation]' contains message 4.1 'Backup Status (Success)' from IMS to FOCOM and message 4.2 'Unexpected Condition' from IMS to FOCOM (labeled as 'Failure Case'). Finally, message 5 'Backup Creation Response' is sent from FOCOM to Operator, and the sequence ends with 'End O-Cloud Node Backup Creation Use Case'. - -Figure 3-23: O-Cloud Node Backup Creation - -#### 3.6.4.3 Criteria-Based O-Cloud Node Backup Creation Use Case - -##### 3.6.4.3.1 High Level Description - -This use case describes the criteria-based backup of O-Cloud Node information, i.e., the IMS triggers the O-Cloud Node backup creation automatically based on some configured backup criteria. It also describes how the SMO can configure the backup criteria on the IMS for automatic or periodic backups. - -By configuring the backup criteria, SMO can specify the backup target, backup interval/threshold/trigger, and retention period. The backup criteria can also include an endpoint to notify the result of criteria-based backup. Authorization policy for updating the backup criteria can be included in the backup criteria. - -##### 3.6.4.3.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Create an O-Cloud Node backup, i.e., backup of specified information on an existing O-Cloud Node, based on configured backup criteria. | | -| Actors and Roles | O-Cloud Operator – The O-Cloud Operator is an entity interfacing with the SMO. | | - -| | | | -|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

SMO: FOCOM – The FOCOM within the SMO is the entity that will configure the O-Cloud Node backup criteria on the IMS.

IMS – The IMS processes the request for configuration of O-Cloud Node backup criteria. It also initiates the O-Cloud Node backup creation based on the backup criteria.

| | -| Assumptions | IMS supports backup mechanism without affecting related NF deployments and consumed O-Cloud resources. | | -| Preconditions |
  1. 1) SMO is available
  2. 2) The O-Cloud has been installed and activated and is known to SMO
  3. 3) Network connectivity exists between the O-Cloud and SMO
  4. 4) Privilege - The consumer identification and privileges have been verified to be able to perform O2 operations
| | -| Begins when | This use case begins when the O-Cloud Operator initiates a backup criteria configuration request. | | -| BACKUP CRITERIA CONFIGURATION Steps | | | -| Step 1 (M) | BACKUP CRITERIA CONFIGURATION REQUEST – An O-Cloud Node backup criteria configuration request is initiated from the O-Cloud Operator towards SMO. The request includes backup criteria to be configured on the IMS. | | -| Step 2 (M) | BACKUP CRITERIA CONFIGURATION REQUEST – The O-Cloud Node backup criteria configuration request is sent from the SMO towards IMS. The request includes backup criteria to be configured on the IMS. | | -| Step 3 (M) |

IMS PROCESSES BACKUP CRITERIA CONFIGURATION - IMS processes the backup criteria configuration request. The IMS configures the backup criteria for automatic/periodic backup of O-Cloud Node.

The backup criteria configuration can either:

  • - be newly set up, e.g., by providing the necessary backup criteria
  • - be updated, e.g., to update existing backup criteria

The backup criteria can include the backup target, interval, threshold, trigger, retention period, an endpoint to notify about events related to the backup.

| | -| Step 4.1 (ALT) | BACKUP CRITERIA CONFIGURATION SUCCESS – The backup criteria was successfully configured on the IMS without any issues. A success response is returned to the SMO by the IMS. | | -| Step 4.2 (ALT) | EXCEPTION: UNEXPECTED CONDITION – The IMS might not be able to comply to the request. A response is sent from the IMS to the SMO. | | -| Step 5 (M) | BACKUP CRITERIA CONFIGURATION RESPONSE – A backup criteria configuration response is sent back to the requesting entity. | | -| CRITERIA-BASED BACKUP CREATION Steps | | | -| Step 6 (M) | BACKUP CREATION TRIGGER BASED ON CRITERIA – IMS triggers an O-Cloud Node backup based on configured criteria. | | -| Step 7 (M) | IMS CREATE BACKUP - The IMS creates a backup of O-Cloud Node information. | | -| Step 8.1 (ALT) | BACKUP SUCCESS – The backup creation was successfully performed by the IMS without any issues. A notification can be sent from the IMS to the SMO to notify that the new backup of O-Cloud Node has been created based on backup criteria. The notification is mandatory if the backup criteria include an endpoint to notify. | | -| Step 8.2 (ALT) | EXCEPTION: UNEXPECTED CONDITION – The IMS might not be able to comply to the request. A notification is sent from the IMS to the SMO to notify that the criteria-based O-Cloud Node backup has failed. The notification is mandatory if the backup criteria include an endpoint to notify. | | -| Ends when | O-Cloud Node backup criteria has been configured successfully and O-Cloud Node backup has been created successfully or when IMS encounters an unexpected condition. | | -| Exceptions |
  1. (1) IMS was unable to configure backup criteria due to unexpected conditions.
  2. (2) IMS was unable to create a backup of O-Cloud Node based on backup criteria due to unexpected conditions.
| | -| Post-conditions |

SUCCESS: O-Cloud backup criteria is configured and O-Cloud Node backup is created.

FAILURE: The exception response has been sent to the SMO.

| | -| Traceability | The requirement traceability is not present in this document version. | | - -##### 3.6.4.3.3 UML Sequence Diagram - -![UML Sequence Diagram for Criteria-based O-Cloud Node Backup Creation. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The sequence involves configuring backup criteria and then creating a backup based on those criteria, with success and failure handling.](fcc757566216206ceddbd6c775e8db02_img.jpg) - -``` - -sequenceDiagram - actor Personnel as O-Cloud Operator - participant FOCOM as FOCOM - participant IMS as IMS - - Note right of FOCOM: Criteria-based O-Cloud Node Backup Creation Use Case - - Note right of FOCOM: O-Cloud Node Backup Criteria Configuration - - Personnel->>FOCOM: 1 O-Cloud Node Backup Criteria Configuration Request - FOCOM->>IMS: 2 O-Cloud Node Backup Criteria Configuration Request - Note right of IMS: 3 IMS Configures Backup Criteria such as backup target, interval, retention period, etc. - alt Successful Backup Criteria Configuration: 4.1 Backup Criteria Configuration Status (Success) - else Exception: Unexpected Condition: 4.2 Unexpected Condition - end - FOCOM->>Personnel: 5 Backup Criteria Configuration Response - - Note right of FOCOM: Criteria-based O-Cloud Node Backup Creation - - FOCOM->>IMS: 6 O-Cloud Node Backup Creation Based on backup criteria - Note right of IMS: 7 IMS Creates O-Cloud Node Backup - alt Successful Backup: 8.1 Notify O-Cloud Node Backup Created - else Exception: Backup Failed: 8.2 Notify O-Cloud Node Backup Failed - end - Note right of FOCOM: End Criteria-based O-Cloud Node Backup Creation Use Case - -``` - -UML Sequence Diagram for Criteria-based O-Cloud Node Backup Creation. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The sequence involves configuring backup criteria and then creating a backup based on those criteria, with success and failure handling. - -Figure 3-24: Criteria-based O-Cloud Node Backup Creation - -#### 3.6.4.4 O-Cloud Node Backup Query Use Case - -##### 3.6.4.4.1 High Level Description - -This use case concerns the query of O-Cloud Node backup information. O-Cloud Operator can query the backup status of O-Cloud Node (such as time of backup, backed-up version) or backed-up O-Cloud Node information itself (such as backed-up software and status of O-Cloud Node) based on query filtering criteria. - -##### 3.6.4.4.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Query information of one or more O-Cloud Node backups. | | -| Actors and Roles | O-Cloud Operator – The O-Cloud Operator is an entity interfacing with the SMO.
SMO: FOCOM – The FOCOM within the SMO is the consumer that will query the O-Cloud Node backup information.
IMS – The IMS processes the request to query information about the O-Cloud Node backup. | | -| Assumptions | No assumptions. | | -| Pre conditions | 1) SMO is available
2) The O-Cloud has been installed and activated and is known to SMO
3) Network connectivity exists between the O-Cloud and SMO
4) Privilege - The consumer identification and privileges have been verified to be able to perform O2 operations | | -| Begins when | This use case begins when the O-Cloud Operator initiates an O-Cloud Node backup query. | | - -| | | | -|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 1 (M) | BACKUP QUERY REQUEST – A request to query backup information is initiated from the O-Cloud Operator towards SMO. O-Cloud Operator can declare query filter to indicate the information to query. | | -| Step 2 (M) | BACKUP QUERY REQUEST – A request to query backup information is sent from the SMO towards IMS. The request can include query filter to indicate the information to query. | | -| Step 3.1 (ALT) | BACKUP QUERY SUCCESS – The query of backup information is successfully processed by the IMS without any issues. The requested backup information of the O-Cloud Node(s) is returned to the SMO by the IMS. | | -| Step 3.2 (ALT) | EXCEPTION: UNEXPECTED CONDITION – The IMS might not be able to comply to the request. A response is sent from the IMS to the SMO. | | -| Step 4 (M) | BACKUP QUERY RESPONSE – A response about the query of backup information is sent back to the requesting entity. The response includes the requested information of the O-Cloud Node backup as specified by the request. | | -| Ends when | O-Cloud Node backup information has been returned to the requesting entity successfully or when IMS encounters an unexpected condition. | | -| Exceptions | IMS was unable to return a target O-Cloud Node backup information due to unexpected conditions. | | -| Post-conditions | SUCCESS: O-Cloud Node backup information has been returned to the requesting entity.
FAILURE: The exception response has been sent to the requesting entity. | | -| Traceability | The requirement traceability is not present in this document version. | | - -##### 3.6.4.4.3 UML Sequence Diagram - -![UML Sequence Diagram for O-Cloud Node Backup Query. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The sequence starts with the Operator sending a '1 O-Cloud Node Backup Query Request' to FOCOM. FOCOM then sends a '2 O-Cloud Node Backup Query Request' to IMS. An 'alt' block titled '[Successful Backup Query]' contains two options: '3.1 O-Cloud Node Backup Query Response (O-Cloud Node Backup Information)' from IMS to FOCOM, and '3.2 Unexpected Condition' from IMS to FOCOM. Finally, FOCOM sends a '4 O-Cloud Node Backup Query Response (O-Cloud Node Backup Information)' back to the Operator. The sequence ends with 'End O-Cloud Node Backup Query'.](dfafe39c233a62ec8ebd71e42992c14d_img.jpg) - -``` - -sequenceDiagram - actor Operator as O-Cloud Operator - participant FOCOM as Service Management & Orchestration Framework (FOCOM) - participant IMS as O-Cloud Platform (IMS) - - Note right of FOCOM: O-Cloud Node Backup Query - - Operator->>FOCOM: 1 O-Cloud Node Backup Query Request - FOCOM->>IMS: 2 O-Cloud Node Backup Query Request - - alt Successful Backup Query: 3.1 O-Cloud Node Backup Query Response (O-Cloud Node Backup Information) - IMS-->>FOCOM: 3.1 O-Cloud Node Backup Query Response (O-Cloud Node Backup Information) - alt Exception: Unexpected Condition: 3.2 Unexpected Condition - IMS-->>FOCOM: 3.2 Unexpected Condition - end - - FOCOM-->>Operator: 4 O-Cloud Node Backup Query Response (O-Cloud Node Backup Information) - - Note right of FOCOM: End O-Cloud Node Backup Query - -``` - -UML Sequence Diagram for O-Cloud Node Backup Query. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The sequence starts with the Operator sending a '1 O-Cloud Node Backup Query Request' to FOCOM. FOCOM then sends a '2 O-Cloud Node Backup Query Request' to IMS. An 'alt' block titled '[Successful Backup Query]' contains two options: '3.1 O-Cloud Node Backup Query Response (O-Cloud Node Backup Information)' from IMS to FOCOM, and '3.2 Unexpected Condition' from IMS to FOCOM. Finally, FOCOM sends a '4 O-Cloud Node Backup Query Response (O-Cloud Node Backup Information)' back to the Operator. The sequence ends with 'End O-Cloud Node Backup Query'. - -Figure 3-25: O-Cloud Node Backup Query - -## 3.7 Fault Use Cases - -### 3.7.1 Alarm Subscription Use Case - -#### 3.7.1.1 High Level Description - -This Use Case supports IMS Alarm Event Subscription as described in ETSI Sol15 Clause 5.9 [12] as a pattern, 3GPP TS29.501-G50 [13]. - -An alarm subscription allows for one or more consumers to receive alarm event notifications. This is accomplished by the potential subscriber(s) issuing a subscription to the publisher of alarm events. - -#### 3.7.1.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | This use case describes a flow where one or more consumers to receive alarm event notifications can issue a subscription to IMS which publishes alarm events.
Each SUBSCRIBER has a consumer subscription identifier . There is one consumer subscription identifier per subscription. It doesn't have to be unique for that subscription. The consumer subscription identifier is a character string that can be associated with meta-data within the SMO. | | -| Actors and Roles | Alarm Event Subscriber (1..n) [e.g. SMO, could be a Proxy].
Alarm Event Publisher [e.g., IMS, DMS] | | -| Assumptions | There can be multiple subscribers to a single publisher. The subscriber-publisher cardinality is not enforced nor monitored.

Each subscription is associated with one subscriber. Each subscription provides information about a single endpoint for receiving alarm related notifications. Thus, there cannot be multiple endpoints for sending alarm related notifications from a single subscription.

The subscriber may not be the ultimate consumer of notifications. The subscriber is not necessarily the same entity as the endpoint for notifications. | | -| Preconditions | Operational Subscriber [1..n], Publisher.

Connectivity (Precondition) – The Subscriber has connectivity to the publisher by some mechanism. The mechanism by which the subscriber achieves connectivity to the publisher is out of the scope of this Use Case.

O-Cloud is installed, operating, and registered with SMO.

Privilege – The consumer identification and privileges of an SMO user have been verified to be able to perform O2 operations. | | -| Begins when | The use case is triggered when a subscriber wishes to:
(1) NOTIFICATION – A subscriber wishes to be notified of O-Cloud Faults
(2) ALARM SUBSCRIPTION CHANGE – To change the characteristics of an alarm subscription a user would need to create a new alarm subscription followed by deleting the previous alarm subscription. This is done because there is no alarm subscription update procedure. The sequence is recommended to ensure that no alarms are missed during these two independent operations.
(3) TRIGGER - An O-Cloud operator may also initiate a subscription. | | -| Step 1 (M) | NOTIFICATION CRITERIA – This gives a notification criterion which initiates the subscription. | | -| Step 2 (M) | SUBSCRIPTION – The subscriber sends an alarm event subscription TO the publisher. The subscription includes the Consumer Subscription Identifier | | -| Step 3 (M) | CALLBACK NOTIFICATION CHECK (Should) – A Reachability Check can be performed between the subscriber and publisher. This is a connectivity and authorization check. This check is optional. However, it is recommended that a reachability check is performed. This step should be performed; though it is stated as optional in ETSI SOL00015. | | - -| | | | -|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 4 (M) | (ALT) REACHABILITY SUCCESS – This step indicates that the reachability check has passed successfully. | | -| Step 5 (M) | (ALT) REACHABILITY FAILURE – This step indicates that the reachability check has failed. | | -| Step 6 (M) | (ALT) Subscription Denied (FAILURE) – The IMS has failed the reachability check. IMS will proceed to deny the subscription. | | -| Step 7 (M) | (ALT) SUBSCRIPTION STATUS (FAILURE) – If the reachability check has failed, the subscription status will indicate a failure. The use case will end at this point. This is a return to Step 2. | | -| Step 8 (M) | SUBSCRIPTION ACKNOWLEDGE – The publisher indicates a subscription acknowledge. This essentially indicates a success for the subscription. (Optional) The consumer subscription identifier may be passed back in the subscription acknowledge. | | -| Step 9 (M) | SUBSCRIPTION STATUS (SUCCESS) – A subscription status will indicate a success back to cloud operator. This is a return to Step 1. | | -| Ends when | This use case ends when a subscription status has been sent successfully or on one of the failure cases, when there was a subscription failure. | | -| Exceptions | FAIL CASE 1: FAILURE INDICATION - The Subscription acknowledge indicates a failure.
FAIL CASE 2: CONNECTIVITY ISSUE - Can't reach the publisher.
EXCEPTION CASE 1: NON-SEQUITUR FILTER – The specified filter for the subscription has been formulated such that no alarms would ever be sent. For example, if a filter specified to give [( all severity = major ) and ( all severity = not major )] would never return any alarms.
ALTERNATE CASE 1: VALIDITY CHECK (Optional) – A validity check confirms the reachability of the callback endpoint, checking that the publisher has permission to reach the consumer through a TLS connection. If a validity check is performed AND it fails, this would lead to Fail Case 2 (Connectivity Issue). | | -| Post Conditions | (1) The publisher has the subscriber call-back (a fully qualified URL) and it is persisted.
(2) The publisher has created its own internal association for subscription which includes the consumer subscription identifier, the call-back URL and filter criteria. | | -| Traceability | REQ-ORC-02-21, REQ-ORC-02-22 | | - -#### 3.7.1.3 UML sequence diagram - -![UML sequence diagram for IMS Alarm Event Subscription Use Case. Lifelines: Personnel (Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows the interaction for subscribing to alarm events, including preconditions, a reachability test, and success/failure paths.](0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg) - -**Preconditions:** - SMO has connectivity to O-Cloud - O-Cloud has registered its IMS with the SMO - The identification & privileges of a SMO user has been verified - -**IMS Alarm Event Subscription Use Case** - -- Notification Criteria (Cloud Operator → FOCOM) -- Subscription (FOCOM → IMS) *Subscription has consumer subscription identifier.* -- Callback Reachability Check (Should) (FOCOM → IMS) -- Success (IMS → FOCOM) -- Failure (IMS → FOCOM) *Failure Case* -- Subscription Denied (Failure) (IMS → FOCOM) -- Subscription Status (Failure) (FOCOM → Cloud Operator) *Use Case Ends* -- Subscription Acknowledge (IMS → FOCOM) *Subscription Entry is created* -- Subscription Status (Success) (FOCOM → Cloud Operator) - -**End Use Case** - -UML sequence diagram for IMS Alarm Event Subscription Use Case. Lifelines: Personnel (Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows the interaction for subscribing to alarm events, including preconditions, a reachability test, and success/failure paths. - -Figure 3-26: Alarm Subscription - -### 3.7.2 Alarm Notification Use Case - -#### 3.7.2.1 High Level Description - -This Use Case supports Alarm Notification(s) by the alarm publisher (IMS). A condition occurs on an O-Cloud resource which causes the current alarm list to change. This triggers an evaluation of the alarm subscription criteria by the publisher (IMS). If deemed relevant by the subscription criteria, the alarm is sent to the subscription endpoint. The alarm is sent in an alarm notification which is an event that carries the details of these relevant alarms. Alarm notifications are sent from a publisher to subscriber(s). See the Alarm subscription use case for more details on Alarm subscriptions. - -When the fault(s) that caused an alarm has been cleared, the IMS determines which alarm to be cleared, clears the alarm, logs the alarm clearance, and reports it to alarm subscriber (FOCOM). - -#### 3.7.2.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal |

This use case describes the series of actions that occur when a O-Cloud resource encounters a fault that eventually results in an alarm being published by the Alarm Event Publisher (IMS).

All faults are logged by the O-Cloud. Note that simple devices may not have the ability to log their faults, hence the O-Cloud would log faults for them. Log management is an area of LCM/FCAPS.

| | -| Actors and Roles |

O-Cloud Resource – This is a resource in the O-Cloud that encounters a fault. See WG6 O2 CADS [7] for definition of an O-Cloud Resource.

Alarm Event Publisher – The IMS is the owner of the O-Cloud alarms. The IMS raises the Alarm. The IMS may use other internal functions to help determine whether faults should become alarms. The O-Cloud or O-Cloud resource might remediate a fault obviating the need to raise an alarm.

Alarm Event Subscriber (1..n) – This entity has subscribed to the publisher successfully. For the IMS case, it would be the FOCOM.

| | -| Assumptions |

There can be multiple subscribers (SMOs) to a single publisher (IMS).

Each subscription is associated with a particular subscriber. You do not get multiple endpoints for multiple consumers of it. The subscriber could be a proxy.

A fault is an error that the O-Cloud resource detects. All faults should be stored and logged in the O-Cloud resource. An Alarm is a notification to an end user of a problem that might need their attention. Note that not all faults need to be raised and reported as alarms from the publisher.

| | -| Preconditions |

The subscriber has successfully completed an alarm event subscription (Use Case)

| | -| Begins when |

This use case begins in one of two cases:

  1. 1. A fault or fault clearance is detected or reported from an O-Cloud resource.
  2. 2. Alarm has been cleared.
| | -| Step 1.1 (M) |

FAULT 1 DETECTED – An O-Cloud resource encounters failure #1, or fault #1 is detected.

| | -| Step 1.2 (M) |

FAULT 2 DETECTED – That O-Cloud resource also detects another fault: failure #2, or fault #2.

| | -| Step 1.3 (M) |

FAULT LOGGED – The O-Cloud resource logs both the faults. Fault #1 and Fault #2 are logged internally to the resource.

| | -| Step 2 (O) |

ALARM ANALYSIS (OPTIONAL) – The O-Cloud itself remediates faults if possible. For example, the resource or O-Cloud may resolve fault 1. The O-Cloud evaluates what faults should become alarms. For example, it may determine that fault 2 should be raised as an alarm and not fault 1. Analysis is done to determine if the fault(s) should become alarms. The O-Cloud or O-Cloud resource might remediate a fault obviating the need to raise an alarm. The O-Cloud implementer decides what O-Cloud resource faults should become alarms.

| | -| Step 3 (O) |

ALARM ENRICHMENT & CORRELATION (OPTIONAL) – Alarm analysis might be performed. Alarm correlation might be performed as described in the O2 GA&P [9].

| | - -| | | | -|--------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------| -| Step 4 (O) | ALARM ESCALATION (OPTIONAL) – Alarm escalation might be performed as described in the O2 GA&P [9]. | | -| Step 5 (M) | ALARM LOGGED – The IMS logs all alarm(s). | | -| Step 6 (M) | ALARM FILTERING & PUBLISHING – Alarm Filters are evaluated. If the alarm is not filtered by the subscription criteria, the Alarm is published by the alarm event publisher (IMS) for any subscriber. The Alarm is then reported to the FOCOM subscriber. This use case flow illustrates that even though multiple faults were raised on an O-Cloud resource only one alarm was raised in this case. Either success or failure of the alarm notification should be logged. | | -| Step 7.1-7.2 (ALT) | FAULT CLEARED AND LOGGED – An O-Cloud resource fault(s) has been cleared and the O-Cloud resource logs the fault(s) clearance. | | -| Step 8 (M) | ALARM ANALYSIS –The IMS determines which alarm to be cleared by the fault clearance. | | -| Step 9 (O) | ALARM CORRELATION (OPTIONAL) – Alarm correlation might be performed as described in the O2 GA&P [9]. | | -| ALT | ALARM CLEARANCE BY SMO OR IMS REQUEST – The Alarm is cleared by FOCOM or IMS using the Alarm Acknowledge/Clear Use Case.
One of the following sets of steps is used;
(1) For SMO-initiated Alarm clearance, Step 2 Alarm Clear Request of SMO-initiated Alarm Clear case in Alarm Acknowledge/Clear Use Case
(2) For IMS-initiated Alarm clearance, Step 1 Autonomously Initiated Alarm Clear of IMS-initiated Alarm Clear case in Alarm Acknowledge/Clear Use Case | 3.7.7 Alarm Acknowledge/Clear Use Case | -| Step 10 (M) | ALARM CLEARANCE LOGGED – The IMS logs all alarm clearances. | | -| Step 11 (ALT) | ALARM CLEARANCE REPORTED – The Alarm clearance is published by the alarm event publisher (IMS) for any subscriber. The Alarm clearance is then reported to the FOCOM subscriber. | | -| ALT | EXCEPTION: UNEXPECTED CONDITION – The IMS might not be able to process the Alarm Clearance Notification operation. No notification to the SMO is possible for the failure case. | | -| Ends when | This use case ends when the Alarm Notification has been sent, or on one of the error cases. | | -| Exceptions | (Alt 1) – Faults are filtered by the O-Cloud. For example, fault 1 has been resolved/filtered, and only fault 2 is reported.
(Alt 2) – IMS filters on what should be reported, and in this example, alarm 2 passed the filter so it is reported. | | -| Post Conditions | Alarms that pass filters are published to subscribers with a valid subscription. | | -| Traceability | REQ-ORC-O2-16 | | - -#### 3.7.2.3 UML sequence diagram - -![UML sequence diagram for Alarm Notification Use Case. Lifelines: Service Management & Orchestration Framework (Subscriber) with FOCOM; O-Cloud Platform (Publisher) with IMS, OC Resource, and CPM. The diagram shows the interaction for alarm notification and clearance, including fault raising, logging, analysis, correlation, escalation, and final reporting to the subscriber.](347010b7ac06d3ae97927fde0f784d7c_img.jpg) - -**Service Management & Orchestration Framework (Subscriber)** -FOCOM - -**O-Cloud Platform (Publisher)** -IMS, OC Resource, CPM - -Precondition: Subscriber (SMO) has registered to IMS Publisher - -**Alarm Notification Use Case** - -1.1 Fault1 Raised -1.2 Fault2 Raised -1.3 Faults Logged - -Fault1 and Fault2 are evaluated and determined if they should be alarms to be reported. -Fault correlation may be performed. - -alt [if a Fault is alarmable] - -2 Alarm Analysis (Optional) -3 Alarm Correlation (Optional) -4 Alarm Escalation (Optional) -5 Alarm Logged - -alt [Evaluate Subscriptions] - -Alarm is not filtered by subscription criteria. Therefore notification is sent. - -6 Alarm reported to FOCOM Subscriber - -**Alarm Notification (Clearance)** - -alt [Alarm Clearance by Fault Clearance] - -7.1 Fault Cleared -7.2 Fault Clearance Logged - -8 Alarm Analysis -9 Alarm Correlation (Optional) - -[Alarm Clearance by SMO or IMS Request] - -ref Alarm Acknowledge/Clear Use Case -Step 2 Alarm Clear Request of SMO-initiated Alarm Clear case -or Step 1 Autonomously Initiated Alarm Clear of IMS-initiated Alarm Clear case -in Alarm Acknowledge/Clear Use Case - -10 Alarm Clearance Logged - -alt [Alarm Clearance Reported] - -11 Alarm Clearance reported to FOCOM Subscriber - -[Exception: Unexpected Condition] - -No Notification is possible for failure case - -**End Alarm Notification Use Case** - -UML sequence diagram for Alarm Notification Use Case. Lifelines: Service Management & Orchestration Framework (Subscriber) with FOCOM; O-Cloud Platform (Publisher) with IMS, OC Resource, and CPM. The diagram shows the interaction for alarm notification and clearance, including fault raising, logging, analysis, correlation, escalation, and final reporting to the subscriber. - -Figure 3-27: Alarm Notification - -### 3.7.3 Alarm Query Use Case - -#### 3.7.3.1 High Level Description - -This Use Case supports Alarm Query (Alarm History) for O2ims. Alarm query allows for the SMO to query for specific kinds of alarms or groups of alarms based on the alarm query criteria. This is useful for an operator to investigate, track, or debug a system. - -#### 3.7.3.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal |

This Use Case describes the query for alarm(s) from resources. The SMO queries for specific kinds of alarms or groups of alarms through query criteria. Alarms are managed by the O-Cloud and this use case allows a user (SMO) to request for a set of alarms based on the query criteria.

The alarm query criteria specify the alarm characteristics which are to be matched by IMS alarms to be returned as an alarm query results.

In the IMS case, A fault query is a message which is expecting a response message from the IMS which matches the query criteria. FOCOM (SMO) queries the IMS for alarms over O2ims.

Alarm queries within certain periods of time can be used for reconciliation. Combinations of alarm queries can be used for analysis.

An “alarm status” for all the O-Cloud resources can be accomplished by an alarm query with a criterion of “all O-Cloud resources” and “all alarms” (on those resources).

| | -| Actors and Roles |

SMO – The FOCOM within the SMO is used in this use case to represent any consumer of the query service.

IMS – The IMS within the O-Cloud is used to represent any provider of the query service.

| | -| Assumptions |

The NFO (SMO) can query for alarms WITHOUT an alarm subscription to the IMS.

There is no relationship between an alarm subscription's filter criteria and an alarm query's criteria.

| | -| Preconditions |

SMO has connectivity to IMS/DMS.

Privilege – The consumer identification and privileges of an SMO user have been verified to be able to perform O2 operations.

| | -| Begins when | This use case begins when the cloud operator at the SMO (subscriber) initiates an Alarm Query. | | -| Step 1.1 (O) | (Alt) ALARM QUERY INITIATED FROM OPERATOR – An alarm query is initiated from the Operator to the FOCOM with query criteria that specifies what type of alarms the operator is interested in. | | -| Step 1.2 (O) | (Alt) ALARM QUERY INITIATED FROM SMO – An alarm query may also be initiated from the FOCOM (SMO) with query criteria that specifies what type of alarms to retrieve from the IMS. | | -| Step 2 (M) | ALARM QUERY FROM FOCOM TO IMS – An alarm query is processed by the FOCOM (SMO) towards the IMS in the O-Cloud with the alarm query criteria. | | - -| | | | -|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 3 (M) |

(ALT) SUCCESSFUL ALARM RESPONSE – The response is returned in response for the Alarm Query with alarm content matching the alarm query criteria.

NOTE 1: An alarm query on an O-Cloud resource with no alarms will return a successful alarm response with a null set of alarms.

NOTE 2: To get historical alarms the cloud operator would just perform an alarm query with the appropriate criteria. For example, an alarm query with the criteria to request for all alarms with cleared status would return historical alarms based on the retention policy of the alarm list.

| | -| Step 4 (M) |

(ALT) ALARM OBJECT NOT FOUND – This is an alt step. This is an exception case for the Alarm Query basic case. In this situation, the alarm that was to be queried was not found. A “alarm not found” response is sent to the subscriber. For example, an alarm query was performed on a non-existent O-Cloud resource.

| | -| Step 5 (M) |

(ALT) ALARM NO CONTENT – This is an alt step. This is an exception case for the Alarm Query basic case. In this situation, the query parameters returned no content (an empty set). A “no content” response is sent to the subscriber. For example, if the given criteria [(all severity = major) and (all severity = not major)] would never return any alarms.

| | -| Step 6 (M) |

(ALT) ALARM OTHER QUERY FAILURE – This is an alt step. This exception case occurs when the Alarm Query encounters a problem that is not defined as part of this scenario.

| | -| Ends when |

This scenario ends at any of the ALT cases, or with a successful Alarm Query response.

| | -| Exceptions |

This use case can encounter three basic alternate cases.

OBJECT NOT FOUND - The first an alarm query is attempted on a non-existent O-Cloud resource.

NO CONTENT - The second alternate case is a “No Content” case where the Query parameters return an empty set.

OTHER QUERY FAILURE – A problem occurs that is not defined as part of this use case.

| | -| Post Conditions |

Alarms are returned matching the criteria in the query have been returned

| | -| Traceability |

REQ-ORC-02-17, REQ-ORC-02-18

| | - -#### 3.7.3.3 UML sequence diagram - -![UML sequence diagram for Alarm Query. Lifelines: Personnel (O-Cloud SMO operator), Service Management & Orchestration Framework - Subscriber (FOCOM), and O-Cloud Platform (IMS/DMS) - Publisher (IMS). The sequence starts with Preconditions, followed by IMS Alarm Query, an alt block for Query (optional), an alt block for Successful Query (4 Alarm Response) and Exceptions (5-7), and finally End IMS Alarm Query.](0931f3e098bd4539041de11c50cec2d2_img.jpg) - -``` - -sequenceDiagram - actor Personnel as O-Cloud SMO operator - participant FOCOM as Service Management & Orchestration Framework - Subscriber - participant IMS as O-Cloud Platform (IMS/DMS) - Publisher - - Note right of FOCOM: PRECONDITIONS: -SMO has connectivity to O-Cloud -O-Cloud has registered its IMS with the SMO -The identification & privileges of a SMO user has been verified - - Note over FOCOM, IMS: IMS Alarm Query - - alt Query: 1 Alarm Query (optional) - FOCOM->>FOCOM: 2 Alarm Query (optional) - end - - FOCOM->>IMS: 3 Alarm Query - - alt Successful Query: 4 Alarm Response - IMS-->>FOCOM: 4 Alarm Response - else Exception: Query criteria returns elements not found - IMS-->>FOCOM: 5 Alarm Object Not Found - else Exception: Non-sequitur alarm query - IMS-->>FOCOM: 6 Alarm No Content - else Exception: Other failure conditions - IMS-->>FOCOM: 7 Alarm Other Query Failure - end - - Note over FOCOM, IMS: End IMS Alarm Query - -``` - -UML sequence diagram for Alarm Query. Lifelines: Personnel (O-Cloud SMO operator), Service Management & Orchestration Framework - Subscriber (FOCOM), and O-Cloud Platform (IMS/DMS) - Publisher (IMS). The sequence starts with Preconditions, followed by IMS Alarm Query, an alt block for Query (optional), an alt block for Successful Query (4 Alarm Response) and Exceptions (5-7), and finally End IMS Alarm Query. - -Figure 3-28: Alarm Query - -### 3.7.4 IMS Alarm Subscription Query Use Case - -#### 3.7.4.1 High Level Description - -This use case is about the Management of Alarm Subscriptions; in particular, the query service operation. The create and delete of an Alarm Subscription is documented in separate use cases. This use case only concerns the query of an Alarm Subscription. Query (cf. query-response) and Read (cf. CRUD operations) are synonymous in this situation. - -The query of an Alarm Subscription is the ability of an authorized entity to get the details of an Alarm Subscription including its criteria. An entity here would usually be the SMO or O-Cloud Operator; however, it could also be another authorized user/technician, or authorized management function. Typically, an entity would perform a subscription query to cross-check their alarm subscription. Though, it could also be utilized for management purposes as well. - -#### 3.7.4.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal |

An entity (typically the SMO), desires to query the Alarm Subscription(s) from the IMS. Hence, this use case will describe the query of Alarm Subscription(s). Query (cf. query-response) and Read (cf. CRUD operations) are synonymous in this situation.

NOTE 1: An entity may be any authorized user or authorized management function.

NOTE 2: This use case is one in a series of use cases related to alarm subscription management (CRD operations). The create and delete Alarm Subscription operations are described in other use cases.

NOTE 3: The IMS could have more than one alarm subscription. This use case covers the query of one or multiple alarm subscription(s).

| | -| Actors and Roles |

O-Cloud Operator – The O-Cloud operator is a user that is interested in getting alarm subscription query results.

SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer of the alarm subscription query service.

IMS – The IMS within the O-Cloud is used to represent any provider of the alarm subscription status query service.

| | -| Assumptions |

There are no assumptions.

| | -| Preconditions |

Connectivity – The Subscriber has connectivity to the publisher by some mechanism. The mechanism by which the subscriber achieves connectivity to the publisher is out of the scope of this Use Case.

O-Cloud Operational – The O-Cloud is installed, operating, and registered with the SMO.

Privilege – The consumer identification and privileges of a SMO user have been verified to be able to perform O2 operations.

| | -| Begins when |

QUERY SUBSCRIPTION – The use case begins when an operator at the SMO wishes to query the alarm subscription(s).

| | -| Step 1 (M) |

QUERY ALARM SUBSCRIPTION REQUEST – The O-Cloud operator initiates a query for alarm subscription(s) with query criteria.

| | -| Step 2 (M) |

QUERY ALARM SUBSCRIPTION REQUEST – The query subscriber subscription request is issued from FOCOM (SMO) to the publisher (IMS) with query criteria.

NOTE 4: The query criteria could include the Consumer Subscription Identifier(s).

| | -| Step 3 (ALT) |

SUCCESSFUL ALARM SUBSCRIPTION QUERY – A connection authentication is verified by the publisher (IMS). This is a standard type of check and a standard response would be issued in this case. The query request operation is processed by the publisher. If the query request results in alarm subscription(s) matching the query criteria, then a success response is sent to FOCOM (SMO).

| | -| Step 4 (ALT) |

EXCEPTION: QUERY OF NON-EXISTING ALARM SUBSCRIPTION – If the query operation results in no alarm subscription that matches the query criteria, then an alarm subscription not found is issued back to the requestor.

For example, if a consumer subscription identifier does not match any alarm subscription, this exception would be encountered.

| | - -| | | | -|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 5 (ALT) | EXCEPTION: Unexpected Condition – The IMS might not be able to comply to the request. There might have been a software issue trying to process the alarm subscription query request. | | -| Step 6 (M) | QUERY ALARM SUBSCRIPTION RESPONSE – The result of the Alarm Subscription Query is communicated from FOCOM back to O-Cloud operator. This is a return/response for Step 1. | | -| Ends when | This Use Case ends under two cases:

EXCEPTION CASE – The use case ends when there an exception case is encountered. For example, when a requestor tries to perform a query operation on a non-existent alarm subscription.

QUERY OPERATION SUCCEEDS – The use case will end if the query operation of alarm subscription successfully completed. | | -| Exceptions | EXCEPTION CASE: NON-EXISTENT SUBSCRIPTION – The query operation requesting a non-existent alarm subscription.

EXCEPTION CASE: Unexpected Condition – The IMS might not be able to comply to the alarm subscription query request. In this case, the unexpected condition exception is encountered. | | -| Post-conditions | SUCCESS: The alarm subscription has been returned to the requestor (O-Cloud operator)

FAILURE: An exception notification of a non-existent subscription has been issued. | | -| Traceability | REQ-ORC-O2-21, REQ-ORC-O2-22, REQ-ORC-O2-15 | | - -#### 3.7.4.3 UML Sequence Diagram - -![UML Sequence Diagram for Alarm Subscription Query Use Case. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows the interaction flow from the operator to FOCOM, then to IMS, with an alt block for Successful Query, Exception: Query of a non-existent Alarm Subscription, and Exception: Unexpected Condition, followed by a return response.](1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg) - -``` - -sequenceDiagram - actor O-Cloud Operator as O-Cloud Operator - participant FOCOM as Service Management & Orchestration Framework (Subscriber) (FOCOM) - participant IMS as O-Cloud Platform (Publisher) (IMS) - - Note right of FOCOM: PRECONDITIONS: -SMO has connectivity to O-Cloud -O-Cloud has registered its IMS with the SMO -The identification & privileges of a SMO user has been verified - - Note over FOCOM: Alarm Subscription Query Use Case - - O-Cloud Operator->>FOCOM: 1 Query Alarm Subscription - FOCOM->>IMS: 2 Query Alarm Subscription - Note right of IMS: Connection authentication is verified - Note right of IMS: Subscription operation is processed - - alt Successful Query - IMS-->>FOCOM: 3 Query Subscription Status (Success) - else Exception: Query of a non-existent Alarm Subscription - IMS-->>FOCOM: 4 Alarm Subscription Not Found - else Exception: Unexpected Condition - IMS-->>FOCOM: 5 Unexpected Condition - end - - FOCOM-->>O-Cloud Operator: 6 Query Alarm Subscription Response - - Note over FOCOM: End Alarm Subscription Query Use Case - -``` - -UML Sequence Diagram for Alarm Subscription Query Use Case. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows the interaction flow from the operator to FOCOM, then to IMS, with an alt block for Successful Query, Exception: Query of a non-existent Alarm Subscription, and Exception: Unexpected Condition, followed by a return response. - -Figure 3-29: IMS Alarm Subscription Query - -### 3.7.5 IMS Alarm Subscription Delete Use Case - -#### 3.7.5.1 High Level Description - -This use case is about the Management of Alarm Subscriptions; in particular, the delete service operation. The create and query of an Alarm Subscription is documented in separate use cases. This use case only concerns the delete of an Alarm Subscription. - -The delete of an Alarm Subscription is the ability of an authorized entity to delete an Alarm Subscription at the IMS. It is also possible to delete all alarm subscriptions associated with the consumer subscription identifier. An entity here would usually be the SMO; however, it could also be another authorized user/technician, or authorized management function. - -There is no update operation for an Alarm Subscription. To accomplish an update, an entity would need to first delete a subscription and then create a subscription with the desired subscription criteria. - -Any subscription operations that change a subscription shall be logged. Therefore, the delete and create of an alarm subscription shall also be logged. The logging occurs at the O-Cloud IMS. - -#### 3.7.5.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal |

An entity (typically the SMO), desires to delete an Alarm Subscription in the IMS. Hence, this use case will describe the delete of an Alarm Subscription.

NOTE 1: An entity may be any authorized user or authorized management function).

NOTE 2: This use case is one in a series of use cases related to alarm subscription management (CRD operations). The Alarm Subscription Create and Alarm Subscription Query operations are described in other sister use cases.

| | -| Actors and Roles |

O-Cloud Operator – The O-Cloud operator is a user that is interested in deleting an alarm subscription.

SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any entity interested in deleting an alarm subscription.

IMS – The IMS within the O-Cloud is used to represent any owner of the alarm subscription.

| | -| Assumptions |

The entity that owns the alarm subscription owns the security associated with the alarm subscription. This would be FFS to resolve.

| | -| Preconditions |

Connectivity – The IMS and FOCOM has connectivity to each other.

O-Cloud Operational – The O-Cloud is installed, operating, and registered with the SMO.

Privilege - The SMO user identification and privileges have been verified to access the delete alarm subscription API.

| | -| Begins when |

The use case begins when an operator at the SMO wishes to delete an existing subscription

| | -| Step 1 (M) |

Delete Alarm Subscription Request – A request to delete an alarm subscription(s) is initiated by an authorized entity towards the FOCOM.

NOTE 3: The request may also delete all alarm subscriptions associated with the consumer subscription identifier.

| | - -| | | | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 2 (M) | Delete Alarm Subscription Request – A request to delete an alarm subscription(s) is processed by the FOCOM. Privileges are verified. Then, if allowed, FOCOM initiates a request towards the IMS. | | -| Step 3 (ALT) | EXCEPTION: Alarm Subscription Not Found – Alarm subscriptions are searched to see if it exists at the IMS. If they do not exist, then the IMS responds with an alarm subscription not found. | | -| Step 4 (M) | Alarm Subscription Not Found – An alarm subscription not found is returned to the requestor by the SMO. In this situation, the Use case ends. | | -| Step 5 (ALT) | EXCEPTION: Privilege Not Found – The IMS verifies that the requestor has the privilege to delete the alarm subscription. If privilege check fails, then the IMS responds with an unauthorized request.

NOTE 4: The details about how the IMS verifies that the user has the authentication (privilege) to delete an alarm subscription is FFS.

NOTE 5: The Alarm Subscription identifier is an identifier associated with the Alarm Subscription which is created and associated by the IMS. Additionally, an Alarm Subscription also has a Consumer Subscription Identifier which is the owner of that Alarm Subscription. See the Alarm Subscription Use Case to see how these are used. | | -| Step 6 (M) | EXCEPTION: Privilege Not Found – The SMO sends an unauthorized request is returned to the requestor. In this situation, the Use case ends. | | -| Step 7 (ALT) | EXCEPTION: Unexpected Condition – The IMS might not be able to comply to the request. There might have been a software issue trying to process the alarm subscription query request. The IMS informs the SMO of the response. | | -| Step 8 (M) | EXCEPTION: Unexpected Condition – A response is sent to the requesting entity from the SMO, that the IMS encountered an unexpected condition processing the request. The Use Case ends. | | -| Step 9 (ALT) | Delete Subscription Success – The IMS processes the delete alarm subscription operation. A response is sent from the IMS to the SMO. | | -| Step 10 (M) | Delete Alarm Subscription Response – The delete alarm subscription response is sent to the requestor. | | -| Ends when | The Use Case Ends when either an alarm subscription deletion has successfully been accomplished or one of the three alt & exception cases have been encountered. | | -| Exceptions | Alarm Subscription Not Found – If the requested alarm subscription to be deleted is not found, this alt case is encountered.

Privilege Not Found – If the requestor does not have the proper privilege to delete the alarm subscription this exception is encountered.

Unexpected Condition – The IMS might not be able to comply to the request. | | -| Post-conditions | SUCCESS: The requested alarm subscription to be deleted has been removed at the IMS.

FAILURE: The request was not able to be completed, and either the alarm subscription was not deleted, or it never existed in the first place. | | -| Traceability | REQ-ORC-O2-23, REQ-ORC-O2-24, REQ-ORC-O2-15 | | - -#### 3.7.5.3 UML Sequence Diagram - -![UML Sequence Diagram for IMS Alarm Subscription Deletion. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The sequence includes a request for deletion, a check for the subscription, privilege checks, and handling of exceptions or success status.](2f587210e4f97c32758c5972e2e83d20_img.jpg) - -**PRECONDITIONS:** -SMO has connectivity to O-Cloud -O-Cloud has registered its IMS with the SMO -The identification & privileges of a SMO user has been verified - -**Sequence:** - -- 1 Delete Alarm Subscription Request (O-Cloud Operator to FOCOM) -- 2 Delete Alarm Subscription Request (FOCOM to IMS) -- Find Alarm Subscription (IMS internal) -- alt: [Delete a non-existent Alarm Subscription] - - 3 Alarm Subscription Not Found (IMS to FOCOM) - - 4 Alarm Subscription Not Found (FOCOM to O-Cloud Operator) - - Use Case Ends -- Privilege check (IMS internal) -- alt: [Privilege Check Fail] - - 5 Unauthorized Request (IMS to FOCOM) - - 6 Unauthorized Request (FOCOM to O-Cloud Operator) - - Use Case Ends -- Delete Subscription operation is processed (IMS internal) -- alt: [Exception: Unexpected Condition] - - 7 Unexpected Condition (IMS to FOCOM) - - 8 Unexpected Condition (FOCOM to O-Cloud Operator) - - Use Case Ends -- 9 Delete Subscription Status(Success) (IMS to FOCOM) -- 10 Delete Subscription Status (Success) (FOCOM to O-Cloud Operator) - -**End Delete Alarm Subscription Use Case** - -UML Sequence Diagram for IMS Alarm Subscription Deletion. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The sequence includes a request for deletion, a check for the subscription, privilege checks, and handling of exceptions or success status. - -Figure 3-30: IMS Alarm Subscription Deletion - -### 3.7.6 Alarm Synchronization Use Case - -#### 3.7.6.1 High Level Description - -This use case is for Alarm Synchronization. This is a special case, though commonly employed situation, for Alarm Query. - -Alarm Synchronization is an Alarm Query on all the alarms of interest. Synchronization is just an alarm query operation with a specific query for all alarm changes within a specific time frame. - -The Alarm Synchronization result is the same as a “Get Alarm List” with the entire list requested. - -Alarm synchronization may be performed on demand left up to the consumer when to issue the operation. - -One example of where alarm synchronization would be used is a situation where the communication link between the client (such as the SMO) and source of truth (such as the O-Cloud) might become disconnected or disrupted. In this case, the client will want to synchronize with the source of truth after a connect is re-established. - -A situation might arise such that during the time of disconnection between the O-Cloud and the management layer (FOCOM/SMO), an alarm appeared and was cleared. From the Alarm Query Use case: to get historical alarms, the cloud operator would just perform an alarm query with the appropriate criteria. For example, an alarm query with the criteria to request for all alarms with cleared status would return the historical alarms based on the retention policy of the alarm list. Thus, to perform an Alarm Synchronization for alarm with a long communication outage time an operator could perform this type of operation to synchronize historical alarm lists as well. - -#### 3.7.6.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal |

There are many potential situations where a client and source of truth might become disconnected or disrupted. In this case, the client will need to synchronize with the source of truth after it is able to reconnect.

The Alarm synchronization is a Query on all the active alarms or all alarms of interest.

For example, network fault might prevent communication between the FOCOM/SMO (client), IMS and the O-Cloud infrastructure resources. By the time connectivity has been restored, many new alarm conditions might have arisen and logged. This would motivate the FOCOM/SMO to resynchronize to get the current alarms again. A variety of mechanisms might be used to trigger alarm resynchronization. It might also trigger an upload of the most recent alarm logs.

| | -| Actors and Roles |

O-Cloud Operator – A Cloud Service Provider (CSP) or entity using the SMO.

FOCOM/SMO – The FOCOM within the SMO is used in this use case to represent any consumer of the alarm notification service.

IMS – The IMS in the O-Cloud is the publisher

| | -| Assumptions |

Each subscription is associated with a particular subscriber. You do not get multiple endpoints for multiple consumers of it. Furthermore, the subscriber could be a proxy.

NOTE 1: As per the GA&P basic concepts, the O-Cloud is the source of truth for the alarms.

| | -| Preconditions |

CONNECTIVITY: SMO has connectivity to IMS in O-Cloud.

SUBSCRIPTION: The subscription Use Case has been successfully executed resulting in the subscriber having a subscription to IMS alarm notifications.

| | - -| | | | -|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

NOTE 2: there might have previously been a network disruption between the SMO and IMS, but that connection has been restored.

Privilege – The consumer identification and privileges of an SMO user have been verified to be able to perform O2 operations.

| | -| Begins when |

This use case begins when in one of three cases:

  1. 1. When the cloud operator at the SMO (subscriber) initiates an Alarm Synchronization operation.
  2. 2. When the SMO initiates an alarm synchronization.

Or when the IMS has determined that an alarm synchronization should be performed.

| | -| Step 1.1 (ALT) |

ALARM QUERY – An alarm synchronization request is initiated from the O-Cloud Operator towards SMO. The alarm synchronization operation is a query for all alarms of interest.

| | -| Step 1.2 (ALT) |

ALARM QUERY – An automatically initiated alarm synchronization from the SMO (FOCOM) towards IMS. Some service in the SMO would trigger this operation. The alarm synchronization operation is a query for all alarms of interest.

| | -| (REF) |

ALARM QUERY – Steps 2-6 of the alarm Query Use Case are performed with a filter of “return all alarms of interest”. (See the Alarm Query Use Case for more details).

The Alarm Query occurs FROM the FOCOM (SMO) TOWARDS the IMS.

| | -| Step 2 (M) |

CORRELATE DATA – The response from the IMS is received by the SMO. The SMO performs a correlation between the alarm data that it has with the alarm data it received from the IMS to identify and resolve discrepancies.

| | -| IMS Initiated alarm synchronization | | | -| Step 3 (M) |

IMS INITIATE SYNCHRONIZATION – An automatically initiated request to perform an alarm synchronization operation is generated from the IMS towards the SMO (FOCOM). Some condition or service in the IMS has determined that an alarm synchronization should be performed.

| | -| (REF) |

ALARM QUERY – Steps 2-6 of the alarm Query Use Case are performed with a filter of “return all alarms of interest”. (See the Alarm Query Use Case for more details).

The Alarm Query occurs FROM the FOCOM (SMO) TOWARDS the IMS.

| | -| Step 4 (M) |

CORRELATE DATA – The response from the IMS is received by the SMO. The SMO performs a correlation between the alarm data that it has with the alarm data it received from the IMS to identify and resolve discrepancies.

| | -| Ends when |

This use Case ends when an exception case is encountered, or the alarm query has been successfully performed.

No new end conditions come with this use case. See the Alarm Query Use Case for more details on the exception cases.

| | -| Exceptions |

Typically, when an alarm synchronization is performed, it will perform a query on all the alarms of interest.

The “object not found” and “alarm no content” are exceptions that would not be expected to be encountered performing this use case. The only exception might be “ALARM OTHER QUERY FAILURE”. It might be possible that these other exceptions might be encountered in rare circumstances. See the Alarm Query Use Case for more details.

| | -| Post-conditions |

SUCCESS: Alarms are returned matching the criteria in the query have been returned.

| | - -| | | | -|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | In this case, all alarms of interest have been received.

FAILURE: An exception has been encountered and the use case ends with an exception response. | | -| Traceability | REQ-ORC-O2-25, REQ-ORC-O2-26 | | - -#### 3.7.6.3 UML Sequence Diagram - -![UML Sequence Diagram for Alarm Synchronization. Lifelines: Personnel (O-Cloud SMO operator), Service Management & Orchestration Framework - Subscriber (FOCOM), and O-Cloud Platform (IMS/DMS) - Publisher (IMS). The diagram shows two paths for alarm synchronization: operator-initiated and IMS-initiated, both involving an alarm query use case and data correlation.](64cda8ce20067bc360ce2f3a5c9352b7_img.jpg) - -``` - -sequenceDiagram - actor Personnel as O-Cloud SMO operator - participant FOCOM as Service Management & Orchestration Framework - Subscriber - participant IMS as O-Cloud Platform (IMS/DMS) - Publisher - - Note right of FOCOM: PRECONDITIONS: -SMO has connectivity to O-Cloud -O-Cloud has registered its IMS with the SMO -The identification & privileges of a SMO user has been verified - - Note over FOCOM: IMS Alarm Synchronization - - alt Alarm Synchronization: Operator Initiated - Note left of FOCOM: 1.1 Operator Initiated Synchronization (optional) - FOCOM->>FOCOM: 1.2 Automatically Initiated Synchronization (optional) - end - - ref Alarm Query Use Case (steps 2 - 6) with Filter of "Return all alarms of interest" - FOCOM->>IMS: 2 Correlate Alarm Data with IMS Response - IMS-->>FOCOM: - end - - Note over FOCOM: IMS initiated Alarm Synchronization - - FOCOM->>IMS: 3 Initiate an Alarm Synchronization - - ref Alarm Query Use Case (steps 2 - 6) with Filter of "Return all alarms of interest" - FOCOM->>IMS: 4 Correlate Alarm Data with IMS Response - IMS-->>FOCOM: - end - - Note over FOCOM: End IMS Alarm Synchronization - -``` - -UML Sequence Diagram for Alarm Synchronization. Lifelines: Personnel (O-Cloud SMO operator), Service Management & Orchestration Framework - Subscriber (FOCOM), and O-Cloud Platform (IMS/DMS) - Publisher (IMS). The diagram shows two paths for alarm synchronization: operator-initiated and IMS-initiated, both involving an alarm query use case and data correlation. - -Figure 3-31: Alarm Synchronization - -### 3.7.7 Alarm Acknowledge/Clear Use Case - -#### 3.7.7.1 High Level Description - -This Use Case relates to Alarm Supervision. It is expected that some O-Cloud infrastructure resources can experience alarm conditions that need to be managed or cleared. - -This use case is used for a management entity to acknowledge or request for alarm(s) to be cleared. It is also used for the IMS to clear alarm(s) autonomously. It is expected that some resources could have some alarms that can be manually cleared while other alarms would be automatically cleared. - -Acknowledgement of alarms means that a resource type has defined alarms that may require further human intervention; and that the acknowledge function allows an entity to recognize that the condition exists, and that further action might need to be taken. - -Some alarms, based on the resource type, may have alarms that can be manually cleared after they have been raised. - -#### 3.7.7.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|---------------------------|-------------------------| -|----------------|---------------------------|-------------------------| - -| | | | -|-------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------| -| Goal | This use case related to alarm acknowledge and alarm clear. Alarms can either be automatically or manually cleared.
This use case deals with clearing of O-Cloud alarms manually by a managing entity.
Acknowledge alarms allows for the IMS to track a state change related to an alarm condition that requires acknowledgement. | | -| Actors and Roles | O-Cloud Operator – A Cloud Service Provider (CSP) or entity using the SMO.
FOCOM (SMO) – The FOCOM within the SMO is used in this use case to represent any consumer of the alarm notification service.
IMS – The IMS in the O-Cloud is the publisher. The source of truth for the alarm request to be acknowledged or cleared. | | -| Assumptions | The SMO is subscribed to notifications from the IMS related to fault management such as clear alarm notifications. | 3.7.1 Alarm Subscription Use Case | -| Preconditions | Connectivity – SMO has connectivity to IMS in O-Cloud.
Registered – O-Cloud has registered its IMS with the SMO.
Privilege – The consumer identification & privileges of an SMO user has been verified to be able to perform O2 operations. | | -| Begins when | This use case begins when in one of two cases:
  1. The O-Cloud operator initiates an alarm acknowledge / clear request.
  2. The FOCOM (SMO) initiates an alarm acknowledge / clear request.
| | -| Operator/SMO-INITIATED ALARM ACKNOWLEDGE/CLEAR Steps | | | -| Step 1.1 (ALT) | ALARM ACKNOWLEDGE/CLEAR INITIATED – An alarm acknowledge/clear request is initiated from the O-Cloud Operator towards FOCOM (SMO). The alarm acknowledge/clear operation will request for one or more alarm(s) that are present at the O-Cloud Operator to be either acknowledged or cleared.
NOTE 1: Either Step 1.1 or Step 1.2 is performed. | | -| Step 1.2 (ALT) | ALARM ACKNOWLEDGE/CLEAR INITIATED – An alarm acknowledge/clear request is initiated by the FOCOM (SMO) to the IMS. The alarm acknowledge/clear operation will request for one or more alarm(s) that are present at the FOCOM to be either acknowledged or cleared.
NOTE 2: Either Step 1.1 or Step 1.2 is performed. | | -| Step 2 (M) | ALARM ACKNOWLEDGE/CLEAR REQUEST – An alarm acknowledge/clear request is composed and sent to the IMS. | | -| Step 3 (M) | IMS PERFORMS ALARM ACKNOWLEDGE/CLEAR – The IMS performs the alarm acknowledge/clear on the O-Cloud alarms. The IMS is the manager of O-Cloud alarms. | | -| Step 4 (ALT) | ALARM ACKNOWLEDGE/CLEAR SUCCESS – The alarm acknowledge/clear operation was successfully performed by the IMS without any issues. A success response is returned to the FOCOM by the IMS.
For an alarm clear success – the IMS has cleared the alarm.
For an alarm acknowledge success – the IMS has registered the acknowledgement of the alarm; but the alarm remains present. | | -| Step 5 (ALT) | EXCEPTION: ALARM NOT FOUND – If the alarm acknowledge/clear operation was requested on an alarm that does not exist at the IMS, then an alarm not found is returned to FOCOM.
NOTE 3: This means that the FOCOM or O-Cloud Operator has the alarm present, but a mismatch has occurred between them and the IMS. In this case, an Alarm Synchronization operation might be appropriate. It might also require additional human intervention to rectify the problem. | | -| Step 6 (ALT) | EXCEPTION: UNEXPECTED CONDITION – The IMS might not be able to comply to the request, or there is an issue with the IMS interworking with the O-Cloud resource such that it is not able to perform the alarm/events acknowledge/clear operation. A response is sent from the IMS to the SMO.
NOTE 4: It is expected that the IMS will clear its alarm. Subsequently, it will try to clear the fault associated with the alarm on the actual O-Cloud resource. If that operation fails, an unexpected condition will result.
NOTE 5: The implementation should as far as possible, try to give a response to indicate if it is necessary to acknowledge / clear the alarm again, and what state the resource would be left in. | | -| Step 7 (O) | ALARM ACKNOWLEDGE/CLEAR STATUS RESPONSE – An alarm acknowledge/clear status response is sent back to the requesting entity. The Use Case ends. | | - -| | | | -|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------| -| Step 8 (O) | ALARM ACKNOWLEDGE/CLEAR NOTIFICATION – After alarm acknowledge/clear, an alarm acknowledge/clear notification may be sent to the FOCOM by the IMS using the Alarm Notification Use Case. | 3.7.2 Alarm Notification Use Case | -| IMS-INITIATED ALARM CLEAR Steps | | | -| Step 1 (M) | ALARM CLEAR INITIATED – An alarm clear is initiated by the IMS. | | -| ALT | ALARM CLEAR NOTIFICATION – The alarm clear operation was successfully performed by the IMS without any issues. An alarm clear notification is sent to the FOCOM by the IMS using the Alarm Notification Use Case. | 3.7.2 Alarm Notification Use Case | -| ALT | EXCEPTION: UNEXPECTED CONDITION – The IMS might not be able to process the Alarm Clear operation. No notification to the SMO is possible for the failure case. | | -| Ends when | This use case ends if the Alarm is not found, or the IMS encounters an unexpected condition, or a successful alarm acknowledge/clear has been performed and Alarm Acknowledge / Clear Notification is sent to the FOCOM by the IMS. | | -| Exceptions | ALARM NOT FOUND – if the request alarm(s) to be acknowledge/clear are not present at the IMS, this exception is encountered.
UNEXPECTED CONDITION – If the IMS was unable to perform the alarm acknowledge/clear operation, this exception is encountered. | | -| Post-conditions | SUCCESS:(1) Response to the Alarm Acknowledge & Clear request is sent to the requesting entity (2) (clear) The alarm(s) at the O-Cloud have been cleared. (3) (acknowledge) The alarm(s) at the O-Cloud have been acknowledge. (4) Alarm Acknowledge / Clear Notification is sent to the FOCOM.
FAILURE:(1) One of the exception responses has been sent to the requesting entity (see above). (2) Depending on the exception, the alarm may still exist at the O-Cloud/IMS. | | -| Traceability | REQ-ORC-O2-27, REQ-ORC-O2-28, REQ-ORC-O2-29, REQ-ORC-O2-30 | | - -#### 3.7.7.3 UML Sequence Diagram - -![UML Sequence Diagram for Alarm Acknowledge/Clear. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS).](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) - -``` - -sequenceDiagram - participant Operator as Personnel (O-Cloud Operator) - participant SMO as Service Management & Orchestration Framework (Subscriber) (FOCOM) - participant IMS as O-Cloud Platform (Publisher) (IMS) - - Note over Operator, IMS: PRECONDITIONS: -SMO has connectivity to O-Cloud -O-Cloud has registered its IMS with the SMO -The identification & privileges of a SMO user has been verified - - rect rgb(240, 240, 240) - Note over Operator, IMS: Operator/SMO-initiated Alarm Acknowledge / Clear Use Case - alt Alarm Acknowledge / Clear - Operator-->>SMO: 1.1 Operator Initiated Alarm Acknowledge / Clear (optional) - SMO-->>SMO: 1.2 Automatically Initiated Alarm Acknowledge / Clear (optional) - end - SMO->>IMS: 2 Alarm Acknowledge / Clear Request - Note right of IMS: IMS Processes -3 Alarm Acknowledge / Clear Request - alt Successful Alarm Acknowledge / Clear - IMS-->>SMO: 4 Alarm Acknowledge / Clear Status (Success) - else Exception: Acknowledge / Clear of a non-existent Alarm Condition - IMS-->>SMO: 5 Alarm Not Found - else Exception: Unexpected Condition - IMS-->>SMO: 6 Unexpected Condition - end - SMO-->>Operator: 7 Alarm Acknowledge / Clear Status Response - opt ref [Alarm Notification Use Case] - IMS-->>SMO: 8 Alarm Acknowledge / Clear Notification - end - Note over Operator, IMS: End Operator/SMO-initiated Alarm Acknowledge / Clear Use Case - end - - rect rgb(240, 240, 240) - Note over Operator, IMS: IMS-initiated Alarm Clear Use Case - IMS->>IMS: 1 Autonomously Initiated Alarm Clear - alt Successful Alarm Clear - opt ref Alarm Notification Use Case - Note over SMO, IMS: Step 10 - Step 11 Alarm Clearance Report of Alarm Notification Use Case - end - else Exception: Unexpected Condition - Note over SMO, IMS: No Notification is possible for failure case - end - Note over Operator, IMS: End IMS-initiated Alarm Clear Use Case - end - -``` - -UML Sequence Diagram for Alarm Acknowledge/Clear. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). - -Figure 3-32: Alarm Acknowledge/Clear - -### 3.7.8 Log Query - -#### 3.7.8.1 High Level Description - -This use case describes log query. Logs could be queried by the SMO to the IMS via O2. A user, application, or entity can query for logs that are available in the Cloud: both O-Cloud (exposed /IMS) and Cloud Infrastructure. Any log kept in the Cloud infrastructure might be queried through a user interface client or file transfer client such as CLI, SSH2, SFTP; this would be implementation specific. - -There are three basic kinds of logs that might be kept within the Cloud (both exposed O-Cloud and Cloud infrastructure): - -**ALARM LOGS** – Alarm logs are a record of the alarms that have been raised by the IMS. The IMS keeps and produces an Alarm Log. It is expected that the IMS logs every alarm that it sends to the FOCOM (SMO). Faults are transformed into Alarms by the IMS. Alarm Logs are exposed in an O-Cloud to northbound entities. - -**FAULT LOGS** – Faults are kept in the Cloud infrastructure. Faults are raised by a Cloud Infrastructure Resource. Faults are transformed into alarms by the IMS. Thus, not every fault is an alarm. Not all faults are necessarily logged, and the Cloud Infrastructure Resource may keep fault log(s). The creation and operation of Fault Logs is up to implementation. Disclaimer: some implementations could combine Fault and Debug logs together. Fault logs are not necessarily exposed to northbound entities. - -**DEBUG LOGS** – The creation and operation of Debug Logs is up to implementation. They might be able to be turned off. The log level would typically be configurable (at the source, middle, and end user level). For example, a typical implementation may use syslog (defined in RFC5424 [21]) which defines a “log level” to show informational (most detail), trace, warnings, errors, to critical (least detail) messages. Disclaimer: some implementations could combine Fault logs and Debug logs together. Debug logs are not necessarily exposed to northbound entities. - -**OTHER LOGS** – There may be other logs besides Alarm, Fault and Debug logs that might be kept in the O-Cloud. This would be left to implementation. - -The conclusion of this use case may provide either: - -- Pull Case – A consumer retrieve the log(s) after being given an endpoint, or -- Push Case – The producer gives a consumer log(s) that match input criteria. - -Because this is left to implementation, this use case will address both types as alternate flows. For example, an endpoint might be an IP address, where a user, application, or entity could then use a file transfer client to get logs from. When it is an endpoint, it can have data related to the endpoint not just an IP address. - -NOTE: the SMO will likely need to be able to inter-operate with different and sometimes legacy IMS implementations. It is expected that the SMO would need to be able to support both paradigms: one where the IMS returns Log Files from a Log Query request and another where the IMS returns an endpoint and then for the SMO to later fetch Log Files. - -#### 3.7.8.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Log Query Use Case | | -| Goal |

This use case deals with the query of the Logs kept in the O-Cloud.

This use case has three basic goals:

  1. 1. RETRIEVE LOGS – It allows an entity to query for logs based on the request query filter. For example, you could ask for all the alarms and faults in the O-Cloud or ask for all the faults within a certain timeframe, or query for log entries that are occurring frequently. This use case concerns the retrieval and reading of logs within the O-Cloud that are present and managed by the IMS.
  2. 2. SYSTEM PROBING – To emulate a “get status” an operator or entity could query for logged faults and alarms that have not been cleared.
  3. 3. ASSISTING INVESTIGATIONS – Logs are typically used to assist in investigations. (NOTE 1)

The IMS may store Faults and Debug Logs, however this would be implementation specific. (NOTE 2)

| | - -| | | | -|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Actors and Roles |

O-Cloud Operator – A Cloud Service Provider (CSP) or entity using the SMO.

FOCOM (SMO) – The FOCOM within the SMO is used in this use case to represent any consumer of Logs in the O-Cloud.

IMS – The IMS in the O-Cloud creates Logs. (NOTE 3)

| | -| Assumptions |

All faults are logged by the O-Cloud. Note that simple devices may not have the ability to log their faults, hence the O-Cloud would log faults for them.

Log events have a severity and source associated with them.

Logs are not kept indefinitely. Logs will be retained based on the configurable retention period attribute. Also, an expiry method attribute allows for an implementation to communicate how log rotation can be handled; however, implementation specific rotation would also be supported.

| | -| Preconditions |

Connectivity – SMO has connectivity to IMS in O-Cloud.

Registered – O-Cloud has registered its IMS with the SMO.

Privilege – The consumer identification & privileges of an SMO user has been verified to be able to perform O2 operations.

| | -| Begins when |

This use case begins when an entity, typically an O-Cloud operator, wishes to get a log, get a status from logs, or start an investigation that involves logs.

| | -| Step 1 (M) |

LOG QUERY REQUEST – The Log Query Request comes from the O-Cloud Operator to the SMO (FOCOM).

The Log Query Request contains filters that indicate the logs the consumer is interested in. For example, these filters may include the date (ranges), types of logs, types of events, log level (severity), and device(s)/resource(s) or types of resources. Valid values for types of logs for use in this filter may be determined from clause 3.7.14 Log Discovery Use Case.

| | -| Step 2 (M) |

LOG QUERY REQUEST – The Log Query Request goes from the SMO (FOCOM) to the IMS in the O-Cloud to be processed.

The connection authentication is verified. The Log Query request matching the request filter is processed by the IMS.

| | -| |

There are two sets of alternate steps:

Alt 1 – steps 3.1, 3.2, and 3.3. This describes a Log Query that returns Log files.

Alt 2 – steps 4.1, 4.2, and 4.3. This describes a Log Query that just returns an endpoint for a requesting entity to then retrieve files later.

Only one of the Alt series of steps will be used in any given cloud implementation. They are both equivalently viable options.

| | -| Step 3.1 (ALT) |

REQUESTED LOG FILES RETURNED –

This is a successful case, where the Log Query request results in the return of Log files that match the request filter. (NOTE 4)

| | -| Step 3.2 (ALT) |

EXCEPTION: NON-EXISTENT LOGS –

This exception occurs when the Log Query filter results in no data. An object not found is returned.

For example, as from the Step 3.1 example, a request for Logs on the 4th day where there was no log data would result in a non-existent logs exception. (NOTE 5)

| | - -| | | | -|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 3.3 (ALT) |

EXCEPTION: NO CONTENT –

In this exception, the evaluation of the Log Query filter returned no content (an empty set). A “no content” response is sent to the subscriber.

For example, a filter which asks for all logs within the last 7 days, and all logs not within the last 7 days would be a null request.

| | -| Step 3.4 (ALT) |

EXCEPTION: FILE UNAVAILABLE FOR IMS PARSING –

In this exception the Log Files exist, however, the records are not available for IMS parsing or retrieval. This might happen because the Log File is not under the management of the IMS.

For example, the log(s) might be in a remote location or in an unknown format. In the former case, a consumer could get an endpoint in order to retrieve the log(s) of interest. In the latter case it would be left to a consumer how to interpret the log(s) of interest.

| | -| Step 4.1 (ALT) |

END POINT RETURNED –

This is a successful case, where the Log Query request results in an endpoint being returned, where an entity can then later retrieve the Log files that match the request filter.

| | -| Step 4.2 (ALT) |

FILE RETRIEVAL

The consumer, after successfully getting an endpoint from the producer, can then later retrieve the Log file(s) matching the request filter.

The specific method by which the consumer obtains the Log file(s) is left up to implementation. (NOTE 6)

| | -| Step 4.3 (ALT) |

EXCEPTION: ENDPOINT UNREACHABLE

This exception occurs when the consumer attempts to reach the endpoint (in Step 4.2), however, it is unable to reach the provided endpoint from Step 4.1. (NOTE 7)

| | -| Step 4.4 (ALT) |

EXCEPTION: NON-EXISTENT LOGS –

This exception occurs when the Log Query filter results in no data (no files). An object not found is returned.

The use case ends with this failure case.

| | -| Step 4.5 (ALT) |

EXCEPTION: NO CONTENT –

In this exception, the evaluation of the Log Query filter returned no content (an empty set). A “no content” response is sent to the consumer.

For example, a filter which asks for all logs within the last 7 days, and all logs not within the last 7 days would be a null request.

The use case ends with this failure case.

| | -| Step 5 (M) |

QUERY STATUS RESPONSE - A query status response is sent back to the requesting entity.

| | -| Ends when |

This scenario ends when any of the exception cases are encountered, or with one of the two successful Log Query responses (Step 3.1 or Step 4.1).

| | -| Exceptions |

This use case can encounter four exception (alternate) cases that apply to each of the two sets of Log Query paradigms:

| | - -| | | | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

EXCEPTION: NON-EXISTENT LOGS – The first exception is a Log Query request that results in a non-existent log. In this case, an object not found is returned and the use case ends.

EXCEPTION: NO CONTENT – The second type of exception case is a “No Content” case, where the Log Query filter returns an empty set. The use case ends with this failure case.

EXCEPTION: ENDPOINT UNREACHABLE – This exception occurs when the consumer attempts to reach the endpoint. However, it is unable to reach the provided endpoint.

EXCEPTION: FILE UNAVAILABLE FOR IMS PARSING – In this exception the Log Files exist, however, the records are not available for IMS parsing or retrieval. This might happen because the Log File is not under the management of the IMS.

| | -| Post-conditions |

SUCCESSFUL – In a successful post-condition, either the requested Log(s) matching the request filter are returned or an endpoint is provided for a requesting entity to retrieve logs.

FAILURE – In a failure case, one of the exception cases described above was encountered. A corresponding error is returned to the requesting entity.

| | -| Traceability | REQ-ORC-02-33, REQ-ORC-02-34, REQ-ORC-02-35, REQ-ORC-02-36, REQ-ORC-GEN36 | | -|

NOTE 1: The IMS shall store Alarm Logs. Log management is an area of LCM/FCAPS. 3GPP uses the term “Alarms list”.

NOTE 2: see GA&P basic concepts, not all faults are transformed into Alarms.

NOTE 3: the O-Cloud infrastructure resources may also create fault and debug logs.

NOTE 4: In the successful case, it is possible that some Logs matching filter could be returned. For example, a request for Logs in the past week for which there were no logs on the 4th day would still successfully return logs for 6 of the 7 days.

NOTE 5: Absolutely no data (non-existent logs exception) is different than returning some data (success).

NOTE 6: The endpoint for the consumer is not likely to be the O2ims endpoint but another endpoint within the O-Cloud.

NOTE 7: The server or networking implementation will create the error.

| | | - -#### 3.7.8.3 UML Sequence Diagram - -![UML Sequence Diagram for Log Query use case. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The sequence starts with a 'Log Query Request' from the operator to FOCOM, which then sends a 'Log Query Request' to IMS. IMS verifies authentication and processes the query. FOCOM then handles the response through two alternative paths (Alt 1 and Alt 2), each with success and failure cases, before returning the 'Query Status' to the operator.](11f18bf0233d812ad2604f88f3385d60_img.jpg) - -**PRECONDITIONS:** -SMO has connectivity to O-Cloud -O-Cloud has registered its IMS with the SMO -The identification & privileges of a SMO user has been verified - -**Begin Log Query Use Case** - -1 Log Query Request (O-Cloud Operator → FOCOM) - -2 Log Query Request (FOCOM → IMS) - -Connection authentication is verified (IMS) - -Log Query matching request filter is processed (IMS) - -**alt [Alt 1 Successful Query]** - -3.1 Requested Log file(s) returned (Success) (IMS → FOCOM) - -[Exception: Non-existent Logs] -Failure Case: 3.2 Requested Logs not found (IMS → FOCOM) -Use Case Ends - -[Exception: No Content] -Failure Case: 3.3 No content (IMS → FOCOM) -Use Case Ends - -[Exception: File unavailable for IMS parsing] -Failure Case: 3.4 File unavailable for IMS parsing (IMS → FOCOM) -Use Case Ends - -**alt [Alt 2 Successful Query]** - -4.1 Endpoint returned (Success) (IMS → FOCOM) - -4.2 File Retrieval (FOCOM → IMS) - -[Exception: Endpoint Unreachable] -Failure Case: 4.3 Endpoint Unreachable (IMS → FOCOM) -Use Case Ends - -[Exception: Non-existent Logs] -Failure Case: 4.4 Requested Logs Not Found (IMS → FOCOM) -Use Case Ends - -[Exception: No Content] -Failure Case: 4.5 No content (IMS → FOCOM) -Use Case Ends - -5 Query Status (FOCOM → O-Cloud Operator) - -**End Log Query Use Case** - -UML Sequence Diagram for Log Query use case. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The sequence starts with a 'Log Query Request' from the operator to FOCOM, which then sends a 'Log Query Request' to IMS. IMS verifies authentication and processes the query. FOCOM then handles the response through two alternative paths (Alt 1 and Alt 2), each with success and failure cases, before returning the 'Query Status' to the operator. - -Figure 3-33: Log Query - -### 3.7.9 Alarm Dictionary Discovery Use Case - -#### 3.7.9.1 High Level Description - -When a new O-Cloud Resource Type is discovered in the O-Cloud infrastructure either on O-Cloud genesis or during run-time, the IMS would inform FOCOM (SMO) about that new Resource Type so that the appropriate corresponding alarm dictionary can be identified. NOTE: every version of a Resource has its own Resource Type and thus an Alarm Dictionary associated with it. - -It is expected that the SMO would have already onboarded the associated Resource Type before it is discovered by the O-Cloud infrastructure, as described in O2 IMS Specification [17]. The four situations where an alarm dictionary could be discovered are: - -- a. **SOFTWARE UPDATE** – A software update creates a new resource type with its attendant alarm dictionary in inventory. Existing resources can either remain pointing to the existing Resource Type or be software updated to the newly loaded Resource Type. Each Resource Type has its own unique alarm dictionary associated with it at the SMO. -- b. **QUERY & SYNCHRONIZATION** – A query service may also result in the discovery of new Resource Types in the O-Cloud infrastructure. Additionally, the initial synchronization of the model between the O-Cloud and management system (SMO) may result in the discovery of Resource Types to be managed. Each Resource Type has its own unique alarm dictionary associated with it. -- c. **NEW RESOURCES ADDED** – New objects have been added to the O-Cloud infrastructure. Subsequently, new Resource Types corresponding to those new objects may be added which then may result in an Infrastructure Inventory Event being generated to a consumer (FOCOM/SMO) or subscriber. Each Resource Type has its own unique alarm dictionary associated with it. -- d. **IMS LIFE CYCLE SOFTWARE UPDATE** – When the software of the O-Cloud is updated new Resource Types can be discovered. - -There are two possible ways the IMS gets the Alarm Dictionary. The SMO might update the IMS with the Alarm Dictionary. In another method, the IMS might get the Alarm Dictionary from the O-Cloud Resource (or external proxy for the resource). See the Resource Type Onboarding LCM Use Case for more details. The source of truth is in the cloud for Cloud Resource types. - -#### 3.7.9.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Alarm Dictionary Discovery (IMS) | | -| Goal |

The primary goal of this use case is where the consumer (SMO) adds an alarm dictionary corresponding to a new discovered Resource Type in the O-Cloud infrastructure.

A consequence is that the consumer (SMO) has a corresponding alarm dictionary that corresponds to every Resource Type that would emit alarms. The triggers for this use case revolve around insuring that consistency.

| | -| Actors and Roles |

O-Cloud Operator – The O-Cloud operator is a consumer (or entity) using or interfacing with the SMO (FOCOM).

SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer of this use case.

IMS – The IMS within the O-Cloud is used to represent any provider of the responses to the use case triggers.

| | -| Assumptions | No Assumptions | | - -| | | | -|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Preconditions |

Connectivity – The producer has connectivity to the consumer by some mechanism. The mechanism by which the subscriber achieves connectivity to the publisher is out of the scope of this Use Case.

O-Cloud Operational – The O-Cloud is installed, operating, and registered with the SMO.

Privilege – The consumer identification and privileges of an SMO user has been verified to be able to perform O2 operations.

Alarm Dictionaries Onboarded – Alarm Dictionar(ies) are onboarded with the Resource Type definition(s) into the O-Cloud Infrastructure Inventory. This is performed by software in the O-Cloud that manages Resource Types.

| | -| Begins when |

There are four triggers that invokes this Use Case:

Software update of an O-Cloud Resource – When software is updated for an O-Cloud Infrastructure Resource(s), a new Resource Type might be discovered which will trigger this use case.

New Resources deployed – When new Resources are deployed to the O-Cloud Infrastructure, it may cause new Resource Types to be discovered which would subsequently trigger this use case.

Query Infrastructure Inventory – A Query Infrastructure Inventory for a Resource Type triggers this use case. One place this occurs is in O-Cloud Registration & Initialization during O-Cloud genesis, the consumer performs a Query Infrastructure Inventory. The consumer then gets the alarm dictionaries for all of the Resource Types discovered during genesis. See the O-Cloud Registration & Initialization use case.

IMS Life Cycle Software Update – When the software of the O-Cloud is updated new Resource Types can be discovered which will trigger this use case.

| | -| Step 1 (M) |

Resource Type Record Created - A new Resource Type record is created during O-Cloud onboarding which is when an Alarm dictionary corresponding to that Resource Type is onboarded within the O-Cloud (see pre-conditions).

These triggers cause a new Resource Type record to be created:

Software update of an O-Cloud Resource – When software is updated for an O-Cloud Infrastructure Resource(s), a new Resource Type is created.

IMS Life Cycle Software Update – When the software of the O-Cloud is updated new Resource Types record is created.

New Resources deployed – When new Resources are deployed to the O-Cloud Infrastructure, it may cause new Resource Type to be created.

These two triggers would cause a new Resource Type record to be discovered by SMO:

Query Infrastructure Inventory – A Query Infrastructure Inventory for a Resource Type is discovered for a previously created Resource Type record.

Infrastructure Inventory Notification – A Infrastructure Inventory notification from the O-Cloud to the subscriber, the IMS will send a copy of the Resource Type record.

| | -| Step 2 (ALT) |

O-Cloud Infrastructure Inventory Event Notification (Alt) –

Step 2 occurs if a subscription already exists and the Step 1 triggers for creation of new Resource Type(s) or discovery of Resource Type(s). An O-Cloud Infrastructure Inventory Event Notification is sent from the IMS in the O-Cloud over O2ims interface to the consumer, FOCOM/SMO to communicate the Resource Type(s) information.

NOTE 1: For the definition of the InfrastructureInventoryEventNotification see Reference [17].

| | -| Step 3 (ALT) |

Query O-Cloud Info Request –

| | - -| | | | -|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | The consumer, FOCOM/SMO, can send a request to Query the O-Cloud for inventory information. This request will result in the SMO discovering new Resource Type(s). | | -| Step 4 (ALT) |

Query O-Cloud Info Response –

The producer, IMS processes the Query request and returns any new Resource Types that have been discovered for a previously created Resource Type record.

NOTE 2: Upon receipt, the consumer, SMO, is expected to associate the new Alarm Dictionaries with the newly discovered Resource Types. The Resource Type object contains the Alarm Dictionary associate with the Resource ID or vendor make & model data.

| | -| Step 5 (M) |

Alarm Dictionary associated –

It is expected that the consumer, SMO, will associate the Alarm Dictionar(ies) for the new Resource Type(s) sent by the IMS.

NOTE 3: The consumer, SMO, will likely aggregate all the Alarm Dictionaries across the O-Clouds that it has purview to. This is implementation specific.

NOTE 4: (error case) If a Resource Type raises alarms, then there is an Alarm Dictionary, but it was not loaded (due to error), for this use case, the IMS will indicate there is no dictionary for this Resource Type. If later, an alarm is sent for that resource instance with a missing Alarm Dictionary, a user will have to debug and load the Alarm Dictionary post facto.

| | -| Ends when | This use case end when the consumer has associated new Alarm Dictionar(ies) to newly create or discovered Resource Type(s). | | -| Exceptions | None | | -| Post-conditions |

Success – Upon successful execution of the use case, the consumer, SMO, associates new Alarm Dictionar(ies) to newly discovered or created Resource Type(s).

Failure – No failure cases

| | -| Traceability | [REQ-ORC-52], [REQ-ORC-O2-53] | | - -#### 3.7.9.3 UML Sequence Diagram - -![UML Sequence Diagram for Alarm Dictionary Discovery Use Case. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows the interaction for discovering new resource types, including preconditions, trigger conditions, and message exchanges between FOCOM and IMS.](0dfdff10c725fe9c332b07ade9d23a5e_img.jpg) - -**PRECONDITIONS:** - SMO has connectivity to O-Cloud - O-Cloud has registered its IMS with the SMO - The identification & privileges of a SMO user has been verified - -**TRIGGER CONDITION:** - (1) Software update of O-Cloud Resource -or- - (2) LCM objects of new Resource deployed to O-Cloud -or- - (3) Resynchronization of inventory between SMO & IMS -or- - (4) IMS Life Cycle Software Update - Result: new O-Cloud Infrastructure Resource Types added - -**Sequence of Messages:** - 1. New Resource Type record is created (IMS self-call) - 2. <> O-Cloud Infrastructure Inventory Event Notification (IMS to FOCOM) - 3. <> Query O-Cloud Info Request (Success) (FOCOM to IMS) - 4. <> Query O-Cloud Info Response (Success) (IMS to FOCOM) - 5. Alarm Dictionary associated for new Resource Types (FOCOM self-call) - -**Alt: Subscription exists for new Resource Types** - [Query / Polling for Inventory Changes] - -**Notes:** - - Software update and LCM onboarding occurs (q.v. other use cases) - - 1 New Resource Type record is created - -UML Sequence Diagram for Alarm Dictionary Discovery Use Case. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows the interaction for discovering new resource types, including preconditions, trigger conditions, and message exchanges between FOCOM and IMS. - -Figure 3-34: Alarm Dictionary Discovery - -### 3.7.10 Logging Configuration Use Case - -#### 3.7.10.1 High Level Description - -The Logging Configuration use case defines how IMS administrates, provisions, and configures Logging Management for logs that reside in the O-Cloud generated by O-Cloud Resources. It is related to the Log Query (IMS) Use Case [see Clause 3.7.8 above] because it sets the behavior how IMS handles the management of logging that underpins the Log Query use case. This Use case will cover Logging Configuration. Some examples of Logging Configuration: the configuration of the retention period, the activation of logging, logging rotation of older logs (FIFO), and setting log levels. - -Logging Configuration can apply to all the various types of logs kept in the O-Cloud including Alarm, Fault and Debug logs. The direct Logging Configuration toward specific types of logs are implementation specific. - -There are Cloud native implementations for storing logs produced from O-Cloud Infrastructure resources. O-Cloud Resources could be physical or logical (see [9]). The Logging Configuration use case should apply to O-Cloud - -Resources in a uniform way but should also account for those Cloud specific implementations. For example, the use of logging level by the IMS may not have a perfect “mapping” to a log level from a O-Cloud Infrastructure resource’s log. - -#### 3.7.10.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Logging Configuration Use Case | | -| Goal |

The goal of this use case is to allow IMS to administrate, provision, and configure logs that reside in the O-Cloud generated by O-Cloud Resources. The direct Logging Configuration toward specific types of logs are implementation specific. The following examples are some Logging Configuration operations that might be requested by an entity:

  • - Configure the retention period of logs
  • - Activate logging
  • - Configure logging rotation (e.g. FIFO retention method)
  • - Configure Log Levels where appropriate.

NOTE: The GA&P describes the triggers for writing Log entries; these are implementation dependent. Some implementations may also use Logging Configuration to define the associated specific Log writing triggers.

| | -| Actors and Roles |

O-Cloud Operator – The O-Cloud Operator is a consumer (or entity) using or interfacing with the SMO (FOCOM).

SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any entity that wants to manage logs.

IMS – The IMS within the O-Cloud processes the Logging Configuration requests as an actor.

| | -| Assumptions |

Not all O-Cloud Resources will support logging levels. If an O-Cloud Resource produces logs, but does not support the concept of Log Levels, that O-Cloud Resource will just behave as if there is one level. Essentially a binary “on” or “off”.

| | -| Preconditions |

Connectivity – The producer has connectivity to the consumer by some mechanism. The mechanism by which the subscriber achieves connectivity to the publisher is out of the scope of this Use Case.

O-Cloud Operational & Registered – The O-Cloud is installed, operating, and has registered its IMS with the SMO.

Privilege – The consumer identification and privileges have been verified to be able to perform O2 operations, such as Logging Configuration.

Logs Identified – the consumer has identified specific logs to be configured (see clauses 3.7.14 Log Discovery Use Case)

| | -| Begins when |

An entity wants to perform Logging Configuration activities such as administrating, provisioning, and configuring how logging works.

| | -| Step 1 (M) |

Logging Configuration Operation
An entity, or O-Cloud Operator requests for Logging Configuration operation such as any of the following:

  • - Configure the retention period of logs
  • - Activate logging
  • - Configure logging rotation (e.g. FIFO retention method)
  • - Configure Log Levels where appropriate.
| | - -| | | | -|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 2 (M) | Logging Configuration Operation The Logging Configuration operation of Step 1 goes from the FOCOM to the IMS over the O2 IMS interface. | | -| Step 3.1 (ALT) | Logging Configuration Success
In the successful case, the result of the Logging Configuration operation is returned to the requestor, typically the SMO (FOCOM). | | -| Step 3.2 (ALT) | Exception: Invalid Configuration
In this exception case, the entity or O-Cloud Operator has requested for a setting or operation that is invalid, outside the bounds of its allowed limits, or not understood by the IMS Logging Management framework.
Because this is an atomic request, and not a transactional request, the operation will either fail or succeed. That is, an entity does not send multiple operations together in a single request. | | -| Step 3.3 (M) | Logging Configuration Operation Status
The Logging Configuration Operation Status is returned to the O-Cloud Operator or entity from the SMO (FOCOM) with the result of the Logging Configuration operation. That status would include any associated information with the operation or exception codes. | | -| Ends when | This use case ends when the Logging Configuration Operation has been successfully performed or has encountered an exception. | | -| Exceptions | This use case has invalid configuration as an exception. This might occur if an entity tries to request for a configuration value that is outside the bounds of its allowed limits. | | -| Post-conditions | Success – Upon successful execution of the use case, the requesting entity is informed of the results of the Logging Configuration operation.
Failure – If the invalid configuration exception has been encountered, no values are changed; and it is expected that the O-Cloud IMS will continue to behave as before. A failure result is sent to the requestor. | | -| Traceability | [REQ-ORC-O2-54], [REQ-ORC-O2-55] | | - -#### 3.7.10.3 UML Sequence Diagram - -![Sequence diagram for Logging Configuration Use Case showing interactions between Cloud Operator, FOCOM, and IMS.](d79de2dd022d74722a84f1b2ffce691c_img.jpg) - -``` - -sequenceDiagram - participant CO as Personnel -Cloud Operator - participant FOCOM as Service Management & Orchestration -Framework (Subscriber) -FOCOM - participant IMS as O-Cloud Platform (Publisher) -IMS - - Note over CO, IMS: PRECONDITIONS: -SMO has connectivity to O-Cloud -O-Cloud has registered its IMS with the SMO -The identification & privileges of a SMO user has been verified - - rect rgb(255, 255, 255) - Note over FOCOM: Begin Logging Configuration Use Case - CO->>FOCOM: 1 Logging Configuration Operation - FOCOM->>IMS: 2 Logging Configuration Operation - Note right of IMS: Logging configuration -attributes are applied - - alt Successful Configuration - IMS-->>FOCOM: 3.1 Logging Configuration(Success) - else Invalid Configuration - Note over FOCOM, IMS: Failure Case - IMS-->>FOCOM: 3.2 Invalid Configuration value - end - - FOCOM-->>CO: 3.3 Logging Configuration Operation Status - Note over FOCOM: End Logging Configuration Use Case - rect - -``` - -Sequence diagram for Logging Configuration Use Case showing interactions between Cloud Operator, FOCOM, and IMS. - -Figure 3-35: Logging Configuration - -### 3.7.11 Alarm List Configuration Use Case - -#### 3.7.11.1 High Level Description - -This use case describes how the Alarm List is configured through a service operation. The SMO, or an authorized entity can request to configure the behavior of Alarm List Management at the IMS. - -Faults are errors that an O-Cloud infrastructure resource detects (and stores). The fault is sent to the IMS. The IMS performs the task of sending alarm notifications to an end user (SMO or subscribing entity) and mapping the incoming faults to alarms. The IMS keeps all the current alarms in an alarm list. The request to configure the Alarm List is sent from the FOCOM towards the IMS. The request has attributes which describe the Alarm List properties to be adjusted. The Retention Period of alarms and Extension attributes can be changed by the Alarm List Configuration operation. After the Retention Period expires, alarms in the alarm list would be purged or archived based on alarm policy. For example, the Alarm List configuration request could have an attribute to specify to Retention Period by the IMS for 72 hours. Another operation to configure the Alarm List behavior could adjust the optional value(s) in the Extension attribute list of the Alarm List. Additional extensions attributes in the Alarm List Configuration request could change other aspects of Alarm List Management behavior by the IMS. This would allow for implementation specific behavior. For example, an Alarm List extension attribute might cause certain types of alarms from a certain compute node resource to be purged or archived after a certain period of time or based on triggers. Other extension attributes might define overflow behavior, or alarm list composition handling. - -#### 3.7.11.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|----------------|-----------------------------------|-------------------------| -| Use Case Title | Alarm List Configuration Use Case | | - -| | | | -|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| -| Goal |

The goals for this use case are to allow for a consumer (SMO) or requesting entity to configure the Alarm List attributes:

  1. 1. The request can change the Alarm List retention per Resource Type
  2. 2. The request could change the additional extension attributes to adjust other aspects of Alarm List management.

Note: The IMS behavior of what happens to the alarms after the Retention Period expires depends on alarm list retention policy. Alarm list retention policy could be altered by the additional extension attribute(s). What happens to alarms currently in the Alarm List when an Alarm List Configuration request arrives is also up to Alarm list retention policy.

Note: It would be implementation specific the kind of alarm list retention policy that would be employed and whether there would be a default behavior.

Note: See the Purge of Alarms Use Case.

| Purge of Alarms Use Case | -| Actors and Roles |

O-Cloud Operator – The O-Cloud Operator is a consumer (or entity) using or interfacing with the SMO (FOCOM).

SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer of this use case.

IMS – The IMS within the O-Cloud is used to represent any provider of the responses to the use case triggers.

| | -| Assumptions | There are no assumptions. | | -| Preconditions |

Connectivity – The producer has connectivity to the consumer by some mechanism. The mechanism by which the subscriber achieves connectivity to the publisher is out of the scope of this Use Case.

O-Cloud Operational & Registered – The O-Cloud is installed, operating, and registered with the SMO.

Privilege – The consumer identification and privileges of a SMO user have been verified to be able to perform O2 operations.

Note: it is possible that the IMS currently has no alarms in its Alarm List. It is ok to invoke this use case with an empty Alarm List

| | -| Begins when | This use case begins when an entity or operator requests for configuration of Alarm List management operations. | | -| Step 1 (M) |

ALARM LIST CONFIGURATION REQUEST

An entity, or O-Cloud Operator requests for an Alarm List Configuration to the SMO.

The Alarm List Configuration request contains the Resource Types that should be affected by the update. The request may apply to the entire Alarm List as well. The alarm Retention Period per Resource Type(s) are given in the request and additional extension attributes to adjust other aspects of Alarm List Management can also be included in the request.

| | -| Step 2 (M) |

ALARM LIST CONFIGURATION REQUEST

The Alarm List Configuration request is sent from the SMO (or entity) to IMS in the O-Cloud. IMS processes the Alarm List Configuration request by adjusting the Retention Period(s) from the request.

NOTE: The SMO may perform prechecks on the Alarm List Configuration request based on implementation. For example, the SMO may check that the Retention Period is within a valid range, or that the Resource Types are valid.

| | -| Step 3.1 (ALT) | ALARM LIST CONFIGURATION RESPONSE | | - -| | | | -|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

The IMS in the O-Cloud provides a response to the Alarm List Configuration request. See also the Alarm List Management Query Use Case [to be addressed in future].

Note: The Alarm List Configuration response will likely include the updated value(s) of the Alarm List, though this is implementation specific.

| | -| Step 3.2 (ALT) |

EXCEPTION: INVALID SETTING
If the Alarm List Configuration request had a syntactic error, the IMS would encounter this exception.

Note: Specific IMS implementations can support additional extension attributes and define their expected settings and syntax.

An exception will be returned in the Alarm List Configuration response.

| | -| Step 3.3 (ALT) |

EXCEPTION: NON-EXISTING RESOURCE TYPE
If the Alarm List Configuration request applies to resource type (and not to the entire Alarm List), and specified operations are for non-existing resource types, the IMS would encounter this exception.

An exception will be returned in the Alarm List Configuration response.

| | -| Step 4 (M) |

ALARM LIST CONFIGURATION RESPONSE
The SMO provides a response for the Alarm List Configuration request to a requesting operator or entity.

| | -| Ends when | This use case ends when the Alarm List Configuration request has been successfully completed, or an exception has been encountered. | | -| Exceptions |

INVALID SETTING – There was an invalid setting or syntactic error for the Alarm List Configuration request.

NON-EXISTING RESOURCE TYPE – For Alarm List Configuration requests that apply to resource types (and not the entire Alarm List), if the request was trying to apply a change to a non-existing Resource Type this exception would be encountered.

| | -| Post-conditions |

SUCCESS – The requested Alarm List Configuration Retention Periods have been updated. There are no additional actions that need to be taken.

FAILURE – There are no additional actions that need to be taken.

| | -| Traceability | [REQ-ORC-O2-73], [REQ-ORC-O2-74] | | - -#### 3.7.11.3 UML Sequence Diagram - -![UML Sequence Diagram for Alarm List Configuration. Lifelines: Cloud Operator (Personnel), Service Management & Orchestration Framework (Subscriber) with FOCOM, and O-Cloud Platform (Publisher) with IMS. The sequence starts with a request from Cloud Operator to FOCOM, followed by FOCOM to IMS. IMS processes the request. An alt block titled '[Successful Command]' contains three possible responses from IMS to FOCOM: 3.1 success, 3.2 invalid settings (Failure Case), or 3.3 non-existing resource type (Failure Case). Finally, FOCOM sends a response back to the Cloud Operator. Preconditions include SMO connectivity to O-Cloud, IMS registration, and user verification. The diagram is framed by 'Begin Alarm List Configuration Use Case' and 'End Alarm List Configuration Use Case' blocks.](fc3e2b49a9f850951570e502393b697f_img.jpg) - -``` - -sequenceDiagram - actor Cloud Operator - participant FOCOM as Service Management & Orchestration Framework (Subscriber) -FOCOM - participant IMS as O-Cloud Platform (Publisher) -IMS - - Note right of FOCOM: PRECONDITIONS: -SMO has connectivity to O-Cloud -O-Cloud has registered its IMS with the SMO -The identification & privileges of a SMO user has been verified - - Note over FOCOM: Begin Alarm List Configuration Use Case - - Cloud Operator->>FOCOM: 1 Alarm List Configuration request - FOCOM->>IMS: 2 Alarm List Configuration request - Note right of IMS: IMS processes Alarm List Configuration request - - alt Successful Command: 3.1 Alarm List Configuration response(success) - else Exception: Invalid Settings: Failure Case: 3.2 Setting(s) in request are invalid - else Exception: Non-existing resource type: Failure Case: 3.3 Non-existing resource type - end - - FOCOM->>Cloud Operator: 4 Alarm List Configuration response - - Note over FOCOM: End Alarm List Configuration Use Case - -``` - -UML Sequence Diagram for Alarm List Configuration. Lifelines: Cloud Operator (Personnel), Service Management & Orchestration Framework (Subscriber) with FOCOM, and O-Cloud Platform (Publisher) with IMS. The sequence starts with a request from Cloud Operator to FOCOM, followed by FOCOM to IMS. IMS processes the request. An alt block titled '[Successful Command]' contains three possible responses from IMS to FOCOM: 3.1 success, 3.2 invalid settings (Failure Case), or 3.3 non-existing resource type (Failure Case). Finally, FOCOM sends a response back to the Cloud Operator. Preconditions include SMO connectivity to O-Cloud, IMS registration, and user verification. The diagram is framed by 'Begin Alarm List Configuration Use Case' and 'End Alarm List Configuration Use Case' blocks. - -Figure 3-36: Alarm List Configuration - -### 3.7.12 Alarm Suppression Use Case - -#### 3.7.12.1 Introduction - -This use case supports Alarm Suppression for O2ims. Alarm Suppression allows for the IMS to suppress alarm notification from the IMS to the SMO. This is useful to avoid alarm floods caused by disasters or maintenance work. - -The suppression policy such as type of alarms to be suppressed can be configured with an Alarm Suppression request order. Other suppression criteria, such as suppression level, suppression period, and suppression deactivation policy, can be configured, too. The suppression timer and threshold to activate Alarm Suppression may be configured via an Alarm Suppression request order. The Alarm Suppression criteria can be configured by the SMO or the IMS itself. - -The IMS can initiate Alarm Suppression autonomously, for example, in the situation where the O2ims link between the SMO and the IMS is overloaded and the SMO is unable to send the Alarm Suppression request via the O2ims link, or in the situation where there is a loss of communication on the O2ims link. SMO can deactivate the IMS-initiated Alarm Suppression. IMS can also deactivate the SMO-initiated Alarm Suppression. - -This use case covers the four operations of Alarm Suppression, which are - -- 1) Activation of Alarm Suppression -- 2) Query of Alarm Suppression criteria and status - -- 3) Update of Alarm Suppression criteria -- 4) Deactivation of Alarm Suppression - -O-Cloud Operator or the SMO can initiate all of the four operations, Alarm Suppression Activation, Query, Update, and Deactivation. The IMS can initiate the three operations, Alarm Suppression Activation, Update, and Deactivation. - -##### 1. Alarm Suppression Activation - -The Alarm Suppression Activation request is sent from the SMO to the IMS to activate Alarm Suppression. After processing the activation request, the IMS responds to the SMO with Alarm Suppression Activation status (success or failure). The IMS may include the configured Alarm Suppression criteria and status. - -The IMS may also activate Alarm Suppression by configuring Alarm Suppression criteria autonomously. In that case, the activation of Alarm Suppression should be informed to the SMO with the configured Alarm Suppression criteria and status. - -NOTE: If an alarm suppression timer or threshold is configured by Alarm Suppression Activation operation, the alarm suppression triggered by the timer or threshold needs to be notified to the SMO. - -##### 2. Alarm Suppression Query - -The SMO can query the Alarm Suppression status (such as active/inactive) and criteria. The IMS responds to the request with the current Alarm Suppression criteria and status. - -##### 3. Alarm Suppression Update - -The SMO can request to update the Alarm Suppression criteria. The Alarm Suppression Update request from the SMO to the IMS includes the order that describes how to change the Alarm Suppression criteria that the IMS keeps. After processing the update request, the IMS responds to the SMO with Alarm Suppression Update status (success or failure). The IMS may include the updated Alarm Suppression criteria and status. - -The IMS may also update Alarm Suppression by updating Alarm Suppression criteria autonomously. In that case, the update of Alarm Suppression should be informed to the SMO with the updated Alarm Suppression criteria and status. - -##### 4. Alarm Suppression Deactivation - -When the SMO sends an Alarm Suppression Deactivation request to the IMS, the IMS responds to the request with Alarm Suppression Deactivation status (success or failure). - -The IMS may also deactivate Alarm Suppression by removing Alarm Suppression criteria. In that case, the deactivation of Alarm Suppression should be informed to the SMO. - -Once the Alarm Suppression is deactivated, the SMO or IMS can trigger the Alarm Synchronization as documented in the Alarm Synchronization Use Case [see Clause 3.7.6] for the suppressed alarms to synchronize and reconcile the state of alarms between IMS and SMO. - -NOTE: If an alarm suppression is deactivated by the suppression deactivation policy, the policy-based alarm suppression deactivation needs to be notified to the SMO. - -How the IMS implements the Alarm Suppression is via the use of policies. How these policies are managed are described in the Alarm List Configuration Use Case [See 3.7.11]. - -Different kind of alarms could be raised with the same root cause by different entities. Some intelligence needs to identify a root cause of those alarms and correlate them. With such an alarm correlation, alarms can be suppressed efficiently. - -NOTE: How to control the Alarm Suppression with some kind of intelligence is out of scope of this use case. - -Section 3.7.12.2 describes the Operator/SMO-initiated Alarm Suppression Activation, Query, Update, and Deactivation. Section 3.7.12.3 describes the IMS-initiated Alarm Suppression Activation, Update, and Deactivation. - -#### 3.7.12.2 Operator/SMO-initiated Alarm Suppression - -##### 3.7.12.2.1 High Level Description - -This use case supports the Operator/SMO-initiated Alarm Suppression. It allows for the SMO to request the IMS to suppress alarm notification, query the suppression criteria and status, update the suppression criteria, and deactivate alarm suppression. - -##### 3.7.12.2.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The goal for this use case is to allow for the SMO to request suppression of alarm notification, query the suppression criteria and status, update the suppression criteria, and deactivate alarm suppression via O2ims. | | -| Actors and Roles | O-Cloud Operator – The O-Cloud Operator is an entity interfacing with the SMO.
FOCOM (SMO) – The FOCOM within the SMO is used in this use case to represent any consumer of this use case.
IMS – The IMS in the O-Cloud is the publisher. The owner of the alarms to be suppressed. The IMS is responsible for transforming faults received from O-Cloud Resource into alarms. It would suppress alarms based on its alarm suppression criteria. | | -| Assumptions | It is expected that the fault originating from the source of truth, the O-Cloud Resource, is still raised to the IMS. It is expected that the O-Cloud Resource faults would be logged. The IMS has no expectation that the O-Cloud Resources suppress the faults. The IMS would also perform the transformation of the fault into an alarm (as normal), and record that an alarm occurred. | | -| Preconditions | Connectivity – SMO has connectivity to IMS in O-Cloud.
Registered – O-Cloud has registered its IMS with the SMO.
Privileges – The identification & privileges of a SMO user has been verified. | | -| Begins when | This use case begins in one of two cases:
1. The O-Cloud Operator initiates an Alarm Suppression Activation, Query, Update, or Deactivation request.
2. The SMO initiates an Alarm Suppression Activation, Query, Update, or Deactivation request. | | -| | ALARM SUPPRESSION ACTIVATION Steps | | -| Activation: Step 1.1 (ALT) | ALARM SUPPRESSION ACTIVATION INITIATED BY OPERATOR – An Alarm Suppression Activation request is initiated from the O-Cloud Operator towards SMO. | | -| Activation: Step 1.2 (ALT) | ALARM SUPPRESSION ACTIVATION INITIATED BY SMO – An Alarm Suppression Activation is initiated by the SMO. | | -| Activation: Step 2 (M) | ALARM SUPPRESSION ACTIVATION REQUEST – An Alarm Suppression Activation request is composed by the SMO and sent to the IMS. | | -| Activation: Step 3 (M) | IMS PROCESSES ALARM SUPPRESSION ACTIVATION – The IMS processes the Alarm Suppression Activation request. The IMS has activated Alarm Suppression or set the policy to activate the Alarm Suppression based on the suppression order in the Alarm Suppression Activation Request. | | -| Activation: Step 4.1 (ALT) | ALARM SUPPRESSION ACTIVATION SUCCESS – The Alarm Suppression Activation operation was successfully performed by the IMS without any issues. A success response is returned to the SMO by the IMS. The response may include the configured Alarm Suppression criteria. | | -| Activation: Step 4.2 (ALT) | EXCEPTION: UNEXPECTED CONDITION – The IMS might not be able to comply to the request. A response is sent from the IMS to the SMO. | | -| Activation: Step 5 (O) | ALARM SUPPRESSION ACTIVATION RESPONSE – An Alarm Suppression Activation response is sent back to the requesting entity. The response may include the configured Alarm Suppression criteria. | | -| | ALARM SUPPRESSION QUERY Steps | | -| Query: Step 1.1 (ALT) | ALARM SUPPRESSION QUERY INITIATED BY OPERATOR – An Alarm Suppression Query request is initiated from the O-Cloud Operator towards SMO. | | -| Query: Step 1.2 (ALT) | ALARM SUPPRESSION QUERY INITIATED BY SMO – An Alarm Suppression Query is initiated by the SMO. | | - -| | | | -|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| -| Query: Step 2 (M) | ALARM SUPPRESSION QUERY REQUEST – An Alarm Suppression Query request is composed by the SMO and sent to the IMS. | | -| Query: Step 3 (M) | IMS PROCESSES ALARM SUPPRESSION QUERY – The IMS processes the Alarm Suppression Query request. | | -| Query: Step 4.1 (ALT) | ALARM SUPPRESSION QUERY SUCCESS – The Alarm Suppression Query operation was successfully processed by the IMS without any issues. Alarm Suppression status is returned to the SMO by the IMS. The response includes the current Alarm Suppression criteria. | | -| Query: Step 4.2 (ALT) | EXCEPTION: UNEXPECTED CONDITION – The IMS might not be able to comply to the request. A response is sent from the IMS to the SMO. | | -| Query: Step 5 (O) | ALARM SUPPRESSION QUERY RESPONSE – An Alarm Suppression status response is sent back to the requesting entity. The response includes the current Alarm Suppression criteria. | | -| | ALARM SUPPRESSION UPDATE Steps | | -| Update: Step 1.1 (ALT) | ALARM SUPPRESSION UPDATE INITIATED BY OPERATOR – An Alarm Suppression Update request is initiated from the O-Cloud Operator towards SMO.
The Alarm Suppression Update request includes the order that describes how to change the Alarm Suppression criteria in the IMS. | | -| Update: Step 1.2 (ALT) | ALARM SUPPRESSION UPDATE INITIATED BY SMO – An Alarm Suppression Update is initiated by the SMO. | | -| Update: Step 2 (M) | ALARM SUPPRESSION UPDATE REQUEST – An Alarm Suppression Update request is composed by the SMO and sent to the IMS. The request includes the order that describes how to change the Alarm Suppression criteria in the IMS. | | -| Update: Step 3 (M) | IMS PROCESSES ALARM SUPPRESSION UPDATE – The IMS processes the Alarm Suppression Update request. The IMS has updated the Alarm Suppression criteria. | | -| Update: Step 4.1 (ALT) | ALARM SUPPRESSION UPDATE SUCCESS – The Alarm Suppression Update operation was successfully performed by the IMS without any issues. A success response is returned to the SMO by the IMS. The response may include the updated Alarm Suppression criteria. | | -| Update: Step 4.2 (ALT) | EXCEPTION: UNEXPECTED CONDITION – The IMS might not be able to comply to the request. A response is sent from the IMS to the SMO. | | -| Update: Step 5 (O) | ALARM SUPPRESSION UPDATE RESPONSE – An Alarm Suppression Update response is sent back to the requesting entity. The response may include the updated Alarm Suppression criteria. | | -| | ALARM SUPPRESSION DEACTIVATION Steps | | -| Deactivation: Step 1.1 (ALT) | ALARM SUPPRESSION DEACTIVATION INITIATED BY OPERATOR – An Alarm Suppression Deactivation request is initiated from the O-Cloud Operator towards SMO. | | -| Deactivation: Step 1.2 (ALT) | ALARM SUPPRESSION DEACTIVATION INITIATED BY SMO – An Alarm Suppression Deactivation is initiated by the SMO. | | -| Deactivation: Step 2 (M) | ALARM SUPPRESSION DEACTIVATION REQUEST – An Alarm Suppression Deactivation request is composed by the SMO and sent to the IMS. | | -| Deactivation: Step 3 (M) | IMS PROCESSES ALARM SUPPRESSION DEACTIVATION – The IMS processes the Alarm Suppression Deactivation request. The IMS has deactivated the Alarm Suppression. | | -| Deactivation: Step 4.1 (ALT) | ALARM SUPPRESSION DEACTIVATION SUCCESS – The Alarm Suppression Deactivation operation was successfully performed by the IMS without any issues. A success response is returned to the SMO by the IMS. | | -| Deactivation: Step 4.2 (ALT) | EXCEPTION: UNEXPECTED CONDITION – The IMS might not be able to comply to the request. A response is sent from the IMS to the SMO. | | -| Deactivation: Step 5 (O) | ALARM SUPPRESSION DEACTIVATION RESPONSE – An Alarm Suppression Deactivation response is sent back to the requesting entity. | | -| Deactivation: Step 6 (O) | ALARM LIST SYNCHRONIZATION – After deactivation of Alarm Suppression, the Alarm Synchronization Use Case may be invoked to synchronize alarm status in SMO and IMS. | 3.7.6 Alarm Synchronization Use Case | - -| | | | -|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Ends when | This use case ends if the IMS encounters an unexpected condition, or a successful Alarm Suppression Activation / Query / Update / Deactivation operation has been performed. | | -| Exceptions | UNEXPECTED CONDITION – If the IMS was unable to perform the Alarm Suppression Activation / Query / Update / Deactivation operation, this exception is encountered. | | -| Post-conditions |

SUCCESS:

(1) Response to the Alarm Suppression Activation / Query / Update / Deactivation request is sent to the requesting entity.

(2) For Alarm Suppression Activation, the alarm notification has been suppressed based on the suppression criteria.

For the Alarm Suppression Query, the suppression criteria have been returned to the SMO.

For the Alarm Suppression Update, the suppression criteria have been updated.

For the Alarm Suppression Deactivation, alarm notification has no longer suppressed and alarm status between SMO and IMS are synchronized.

FAILURE: The exception response has been sent to the requesting entity (see above).

| | -| Traceability | REQ-ORC-O2-81, REQ-ORC-O2-82 | | - -##### 3.7.12.2.3 UML Sequence Diagram - -![UML Sequence Diagram for Operator/SMO-Initiated Alarm Suppression. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows four use cases: Activation, Query, Update, and Deactivation, each with alt blocks for operator/SMO initiation and success/exception handling. A reference block for Alarm Synchronization is also present.](69467ece0a576b4c2ec3e0c89ba61527_img.jpg) - -**PRECONDITIONS:** - SMO has connectivity to O-Cloud - O-Cloud has registered its IMS with the SMO - The identification & privileges of a SMO user has been verified - -**Operator/SMO-initiated Alarm Suppression Activation Use Case** - -**alt** [Operator Initiate Alarm Suppression Activation] - 1.1 Alarm Suppression Activation request -**[SMO Initiate Alarm Suppression Activation]** - 1.2 Alarm Suppression Activation Trigger - 2 Alarm Suppression Activation request - 3. IMS Processes Alarm Suppression Activation request -**alt** [Successful Alarm Suppression Activation] - 4.1 Alarm Suppression Activation Status (Success) -**[Exception: Unexpected Condition]** -**Failure Case** 4.2 Unexpected Condition - 5 Alarm Suppression Activation Response - -**End Operator/SMO-initiated Alarm Suppression Activation Use Case** - -**Operator/SMO-initiated Alarm Suppression Query Use Case** - -**alt** [Operator Initiate Alarm Suppression Query] - 1.1 Alarm Suppression Query request -**[SMO Initiate Alarm Suppression Query]** - 1.2 Alarm Suppression Query Trigger - 2 Alarm Suppression Query request - 3. IMS Processes Alarm Suppression Query request -**alt** [Successful Alarm Suppression Query] - 4.1 Alarm Suppression status (such as active/inactive) returned with current criteria -**[Exception: Unexpected Condition]** -**Failure Case** 4.2 Unexpected Condition - 5 Alarm Suppression status (such as active/inactive) returned with current criteria - -**End Operator/SMO-initiated Alarm Suppression Query Use Case** - -**Operator/SMO-initiated Alarm Suppression Update Use Case** - -**alt** [Operator Initiate Alarm Suppression Update] - 1.1 Alarm Suppression Update request -**[SMO Initiate Alarm Suppression Update]** - 1.2 Alarm Suppression Update Trigger - 2 Alarm Suppression Update request - 3. IMS Processes Alarm Suppression Update request -**alt** [Successful Alarm Suppression Update] - 4.1 Alarm Suppression Update Status (Success) -**[Exception: Unexpected Condition]** -**Failure Case** 4.2 Unexpected Condition - 5 Alarm Suppression Update Response - -**End Operator/SMO-initiated Alarm Suppression Update Use Case** - -**Operator/SMO-initiated Alarm Suppression Deactivation Use Case** - -**alt** [Operator Initiate Alarm Suppression Deactivation] - 1.1 Alarm Suppression Deactivation request -**[SMO Initiate Alarm Suppression Deactivation]** - 1.2 Alarm Suppression Deactivation Trigger - 2 Alarm Suppression Deactivation request - 3. IMS Processes Alarm Suppression Deactivation request -**alt** [Successful Alarm Suppression Deactivation] - 4.1 Alarm Suppression Deactivation Status (Success) -**[Exception: Unexpected Condition]** -**Failure Case** 4.2 Unexpected Condition - 5 Alarm Suppression Deactivation Response -**ref** 6. Alarm Synchronization Use Case - -**End Operator/SMO-initiated Alarm Suppression Deactivation Use Case** - -UML Sequence Diagram for Operator/SMO-Initiated Alarm Suppression. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows four use cases: Activation, Query, Update, and Deactivation, each with alt blocks for operator/SMO initiation and success/exception handling. A reference block for Alarm Synchronization is also present. - -Figure 3-37: Operator/SMO-Initiated Alarm Suppression - -#### 3.7.12.3 IMS-initiated Alarm Suppression - -##### 3.7.12.3.1 High Level Description - -This use case supports the IMS-initiated Alarm Suppression. It allows for the IMS to initiate the suppression of alarm notification from IMS to SMO, update of the suppression criteria, and deactivation of alarm suppression. - -##### 3.7.12.3.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------| -| Goal | The goal for this use case is to allow for the IMS to suppress alarm notification, update the suppression criteria, and deactivate alarm suppression. | | -| Actors and Roles | O-Cloud Operator – The O-Cloud Operator is an entity interfacing with the SMO.
FOCOM (SMO) – The FOCOM within the SMO is used in this use case to represent a receiver of notifications.
IMS – The IMS in the O-Cloud is the publisher. The owner of the alarms to be suppressed. The IMS is responsible for transforming faults received from O-Cloud Resource into alarms. It would suppress alarms based on its alarm suppression criteria. | | -| Assumptions | It is expected that the fault originating from the source of truth, the O-Cloud Resource, is still raised to the IMS. It is expected that the O-Cloud Resource faults would be logged. The IMS has no expectation that the O-Cloud Resources suppress the faults. The IMS would also perform the transformation of the fault into an alarm (as normal), and record that an alarm occurred. | | -| Preconditions | Connectivity – SMO has connectivity to IMS in O-Cloud.
Registered – O-Cloud has registered its IMS with the SMO.
Privileges – The identification & privileges of a SMO user has been verified. | | -| Begins when | This use case begins when the IMS initiates an Alarm Suppression Activation, Update, or Deactivation operation. | | -| | ALARM SUPPRESSION ACTIVATION Steps | | -| Activation: Step 1 (M) | ALARM SUPPRESSION ACTIVATION INITIATED – An Alarm Suppression Activation is initiated by the IMS. | | -| Activation: Step 2.1 (ALT) | ALARM SUPPRESSION ACTIVATION NOTIFICATION – The Alarm Suppression Activation operation was successfully performed by the IMS without any issues. An Alarm Suppression status change notification is sent to the SMO by the IMS. The response includes the configured Alarm Suppression criteria. | | -| Activation: Step 2.2 (ALT) | EXCEPTION: UNEXPECTED CONDITION – The IMS might not be able to process the Alarm Suppression Activation operation. No notification to the SMO is necessary for the failure case. | | -| | ALARM SUPPRESSION UPDATE Steps | | -| Update: Step 1 (M) | ALARM SUPPRESSION UPDATE INITIATED – An Alarm Suppression Update is initiated by the IMS. | | -| Update: Step 2.1 (ALT) | ALARM SUPPRESSION UPDATE NOTIFICATION – The Alarm Suppression Update operation was successfully performed by the IMS without any issues. An Alarm Suppression status change notification is sent to the SMO by the IMS. The response includes the updated Alarm Suppression criteria. | | -| Update: Step 2.2 (ALT) | EXCEPTION: UNEXPECTED CONDITION – The IMS might not be able to process the Alarm Suppression Update operation. No notification to the SMO is necessary for the failure case. | | -| | ALARM SUPPRESSION DEACTIVATION Steps | | -| Deactivation: Step 1 (M) | ALARM SUPPRESSION DEACTIVATION INITIATED – An Alarm Suppression Deactivation is initiated by the IMS. | | -| Deactivation: Step 2.1 (ALT) | ALARM SUPPRESSION DEACTIVATION NOTIFICATION – The Alarm Suppression Deactivation operation was successfully performed by the IMS without any issues. An Alarm Suppression status change notification is sent to the SMO by the IMS. | | -| Deactivation: Step 2.2 (ALT) | EXCEPTION: UNEXPECTED CONDITION – The IMS might not be able to process the Alarm Suppression Deactivation operation. No notification to the SMO is necessary for the failure case. | | -| Deactivation: Step 3 (O) | ALARM LIST SYNCHRONIZATION – After deactivation of Alarm Suppression, the Alarm Synchronization Use Case may be invoked to synchronize alarm status in SMO and IMS. | 3.7.6 Alarm Synchronization Use Case | - -| | | | -|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Ends when | This use case ends if the IMS encounters an unexpected condition, or a successful Alarm Suppression Activation / Update / Deactivation operation has been performed. | | -| Exceptions | UNEXPECTED CONDITION – If the IMS was unable to perform the Alarm Suppression Activation / Update / Deactivation operation, this exception is encountered. | | -| Post-conditions | SUCCESS:
(1) Notification of the Alarm Suppression Activation / Update / Deactivation is sent to the SMO.
(2) For Alarm Suppression Activation, the alarm notification has been suppressed based on the suppression criteria.
For the Alarm Suppression Update, the suppression criteria have been updated.
For the Alarm Suppression Deactivation, alarm notification has no longer suppressed and alarm status between SMO and IMS are synchronized.
FAILURE: No notification to the SMO is necessary for the failure case. | | -| Traceability | REQ-ORC-O2-83 | | - -##### 3.7.12.3.3 UML Sequence Diagram - -![UML Sequence Diagram for IMS-Initiated Alarm Suppression. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows three use cases: Activation, Update, and Deactivation. Each use case has a 'Successful' path (returning status) and an 'Exception' path (no notification). A 'ref' block for 'Alarm Synchronization Use Case' is shown within the Deactivation use case.](a7450c80e88ad3f6ca1427ad84020998_img.jpg) - -**PRECONDITIONS:** - SMO has connectivity to O-Cloud - O-Cloud has registered its IMS with the SMO - The identification & privileges of a SMO user has been verified - -**IMS-initiated Alarm Suppression Activation Use Case** - -1 Alarm Suppression Activation initiated - -**alt** [Successful Alarm Suppression Activation] - 2.1 Alarm Suppression Activation Status (Success) with current criteria -**[Exception: Unexpected Condition]** - 2.2 No Notification is necessary for failure case - -End IMS-initiated Alarm Suppression Activation Use Case - -**IMS-initiated Alarm Suppression Update Use Case** - -1 Alarm Suppression Update initiated - -**alt** [Successful Alarm Suppression Update] - 2.1 Alarm Suppression Update Status (Success) with updated criteria -**[Exception: Unexpected Condition]** - 2.2 No Notification is necessary for failure case - -End IMS-initiated Alarm Suppression Update Use Case - -**IMS-initiated Alarm Suppression Deactivation Use Case** - -1 Alarm Suppression Deactivation initiated - -**alt** [Successful Alarm Suppression Deactivation] - 2.1 Alarm Suppression Deactivation Status (Success) -**[Exception: Unexpected Condition]** - 2.2 No Notification is necessary for failure case - -**ref** 3. Alarm Synchronization Use Case - -End IMS-initiated Alarm Suppression Deactivation Use Case - -UML Sequence Diagram for IMS-Initiated Alarm Suppression. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows three use cases: Activation, Update, and Deactivation. Each use case has a 'Successful' path (returning status) and an 'Exception' path (no notification). A 'ref' block for 'Alarm Synchronization Use Case' is shown within the Deactivation use case. - -Figure 3-38: IMS-Initiated Alarm Suppression - -### 3.7.13 Alarm Purge Use Case - -#### 3.7.13.1 High Level Description - -The Alarm Purge Use case describes Purging of alarms. Alarms in the alarm list that are older than the Retention Period will be purged. This is the most basic situation, when an alarm in the alarm list is older than the Retention Period, the IMS automatically purges old inactive and acknowledged cleared alarms. - -From the Alarm List Configuration use case (see Clause 3.7.11), after the Retention Period expires, alarms in the Alarm List would be purged based on alarm policy. For example, the Retention Period might cause certain types of alarms from a certain Compute Node resource to be purged after a certain period or based on triggers. - -This Use Case also describes the forced Purge of alarms requested by the O-Cloud Operator. In this case, alarms to be purged are removed from the Alarm List irrespective of the Retention Period. See RFC 8632 [22] for related specifications. Only inactive alarms or acknowledged active alarms can be purged. - -NOTE 1: A forced Purge of alarms might be used if the storage capacity for the Alarm List approaches or is at capacity; and an operator wants to remove (warning and minor) alarms from the Alarm List to free up space. - -NOTE 2: If an alarm condition persists after the original alarm is purged that it will reappear as a new alarm (spurred from that same condition) in the Alarm List. - -#### 3.7.13.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <> Related Use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------| -| Use Case Title | Alarm Purge Use Case | | -| Goal |

This use case describes Alarm Purge operations.

  • - Forced Alarm Purge – Purging Alarms can be requested through a forced Purge operation which purges alarms by removing from the Alarm List irrespective of the Retention Period.
  • - Alarm List Configuration Use Case – Alarms can also be purged when the Alarm List Configuration use case changes the Retention Period. Alarms in the Alarm List that are older than the Retention Period will be subject to purging.
  • - Old Alarms – When Alarms in the Alarm List are older than the Retention Period, the IMS autonomously purges them by removing from the Alarm List.

NOTE 1: Only inactive alarms or acknowledge active alarms can be purged.

| 3.7.11 Alarm List Configuration Use Case | -| Actors and Roles |

O-Cloud Operator – The O-Cloud operator is a user that is interested in performing an Alarm Purge request (forced).

SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer or management entity that performs the Alarm List Configuration operation or handles the Alarm Purge request (forced).

IMS – The IMS within the O-Cloud performs the Alarm Purge operations.

| | -| Assumptions | There are no assumptions. | | -| Preconditions |

Connectivity – The Subscriber has connectivity to the Publisher by some mechanism. The mechanism by which the subscriber achieves connectivity to the publisher is out of the scope of this Use Case.

O-Cloud Operational – The O-Cloud is installed, operating, and registered with the SMO.

Privilege – The consumer identification and privileges of a SMO user have been verified to be able to perform O2 operations.

| | -| Begins when |

This use case begins when:

  • - Forced Alarm Purge – An operator at the SMO wishes to purge alarms through an Alarm Purge (forced) operation.
  • - Alarm List Configuration Use Case – The Alarm List Configuration operation changes the Retention Period.
| | - -| | | | -|----------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |
  • Old Alarms – When the IMS autonomously triggers a process to evaluate if alarms are ready to be purged.

NOTE 2: Additionally, alarms may be purged when a resource is removed or deleted. In this case, the IMS will perform internal clean up to preserve referential integrity. This would be implementation specific.

| | -| Operator/SMO initiated (Forced) Alarm Purge Steps | | | -| Step 1 (M) |

ALARM PURGE REQUEST (FORCED)
An entity, or O-Cloud Operator requests for an Alarm Purge to the SMO.

The Alarm Purge request contains an order that requests for inactive and acknowledged alarm(s) to be purged from the Alarm List.

| | -| Step 2 (M) |

ALARM PURGE REQUEST (FORCED)
The Alarm Purge request is sent from the SMO (or entity) to IMS in the O-Cloud.

The IMS processes the Alarm Purge request.

The IMS purges alarms defined in the Alarm Purge request. Only inactive alarms or acknowledge active alarms can be purged. Purged alarms are removed from the Alarm List irrespective of the Retention Period.

| | -| Step 3.1 (ALT) |

SUCCESSFUL ALARM PURGE –

If the purge operation was successful, then a success response is sent to the SMO from the IMS over the O2ims interface

| | -| Step 3.2 (ALT) |

SUCCESSFUL ALARM PURGE –

If the purge operation was successful, then the results from the Alarm Purge command are given to the O-Cloud operator.

| | -| Step 3.3 (ALT) |

ALT EXCEPTION: NO ALARMS MATCHING THE ALARM PURGE REQUEST FOUND –

This exception is encountered when the Alarm Purge request contains only non-existent alarms.

Because no alarms in the Alarm Purge request are in the Alarm List, no alarms will be purged.

An exception is sent from the IMS to the SMO over the O2ims interface indicating that no alarms in the Alarm List match in the alarm purge request.

| | -| Step 3.4 (ALT) |

ALT EXCEPTION: NO ALARMS MATCHING THE ALARM PURGE REQUEST FOUND –

An Alarm Purge Command results are given to the O-Cloud Operator.

The Use Case ends.

| | -| Step 3.5 (ALT) |

ALT EXCEPTION: UNEXPECTED CONDITION –

The IMS might not be able to perform the Alarm Purge according to the request. There might have been a software issue trying to process the Alarm Purge request.

An unexpected condition is sent from the IMS to the SMO over the O2ims interface.

| | - -| | | | -|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------| -| Step 3.6 (ALT) | ALT EXCEPTION: UNEXPECTED CONDITION –
A response is sent to the requesting entity from the SMO, that the IMS encountered an unexpected condition processing the request.
The Use Case ends. | | -| Alarm Purge from Alarm List Configuration Change of Retention Period Steps | | | -| Step 1 | OLD ALARMS PURGED BY IMS
The Alarm list Configuration Use Case Steps 1-2 are performed (REF)
The IMS processes the Alarm List Configuration request.
The IMS purges alarms because of a change in the Alarm Retention Period. Alarms that are older than the new Alarm Retention Period are purged. Old inactive alarms or acknowledged active alarms are purged by removing them from the Alarm List.
The Alarm list Configuration Use Case Steps 3.1-4 are performed (REF)
NOTE 3: Active alarms and unacknowledged active alarms are not purged irrespective of changes in the Alarm Retention Period changes. | Alarm List Configuration Use Case (3.7.11) | -| Autonomous Alarm Purge by IMS | | | -| Step 1 | IMS OPERATIONS TRIGGER
The IMS autonomously triggers a process to evaluate if alarms are ready to be purged. | | -| Step 2 | OLD ALARMS PURGED BY IMS
Alarms that are older than the Alarm Retention Period are purged autonomously by the IMS. Old inactive alarms or acknowledged active alarms are purged by removing them from the Alarm List.
NOTE 4: The logging of the purge of alarms by the IMS is left to implementation. It is reasonable to expect that the IMS would log the purging of one or more alarms. | | -| Ends when | This Use Case ends under two cases:
PURGE OPERATION SUCCEEDS – The use case will end if the Alarm Purge operation successfully completed.
EXCEPTION CASE – The use case ends when either the “ No Alarms matching the Alarm Purge request were found ” or “ Unexpected condition ” exceptions are encountered. | | -| Exceptions | EXCEPTION CASE: NO ALARMS MATCHING THE ALARM PURGE REQUEST FOUND – This exception is encountered when the Alarm Purge request contains only non-existent alarms. In this case, no alarms are purged since none match the request.
EXCEPTION CASE: UNEXPECTED CONDITION – The IMS might not be able to perform to the Alarm Purge request perhaps due to a software fault. In this case, the Unexpected Condition exception is encountered. | | -| Post-conditions | SUCCESS – The Alarm Purge operation has been successfully completed and status returned to the requesting entity (e.g., O-Cloud operator). | | - -| | | | -|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | FAILURE – An exception notification for a “ No Alarms matching the Alarm Purge request were found ” or “ Unexpected Condition ” has been issued. | | -| Traceability | [REQ-ORC-O2-97], [REQ-ORC-O2-98] | | - -#### 3.7.13.3 UML Sequence Diagram - -![UML Sequence Diagram for Alarm Purge. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows three main sequences: 1. Operator/SMO initiated (Forced) Alarm Purge, 2. Alarm Purge from Alarm List Configuration Change of Retention Period, and 3. Autonomous Alarm Purge by IMS. Each sequence includes preconditions, request messages, processing steps, and return messages or exception handling.](2b00743506f6a3bbd17af764162dc76d_img.jpg) - -**PRECONDITIONS:** - SMO has connectivity to O-Cloud - O-Cloud has registered its IMS with the SMO - The identification & privileges of a SMO user has been verified - -**Sequence 1: Begin Operator/SMO initiated (Forced) Alarm Purge** - -- 1 Alarm Purge Request (O-Cloud Operator → FOCOM) -- 2 Alarm Purge Request (FOCOM → IMS) -- IMS processes Alarm Purge Request -- Alarms are Purged (removed from the Alarm List) based on Alarm Purge request order -- alt [Successful Command]: - - 3.1 Alarm Purge Results(Success) (IMS → FOCOM) - - 3.2 Alarm Purge Command Results (FOCOM → O-Cloud Operator) -- alt [Exception: Purge Request for Non-existing Alarms]: - - Failure Case: 3.3 No Alarms matching the Alarm Purge request were found (IMS → FOCOM) - - 3.4 Exception Response (FOCOM → O-Cloud Operator) - - Use Case Ends -- alt [Exception: Unexpected Condition]: - - Failure Case: 3.5 Unexpected Condition (IMS → FOCOM) - - 3.6 Exception Response (FOCOM → O-Cloud Operator) - - Use Case Ends - -**End Operator/SMO initiated (Forced) Alarm Purge** - -**Sequence 2: Begin Alarm Purge from Alarm List Configuration Change of Retention Period** - -- ref: Alarm List Configuration Use Case (steps 1 - 2) Update of Retention Period -- IMS processes Alarm List Configure Command -- Alarms are Purged (removed from the Alarm List) from changes in the Retention Period -- ref: Alarm List Configuration Use Case (steps 3.1 - 4) responses & returns - -**End Alarm Purge from Alarm List Configuration Change of Retention Period** - -**Sequence 3: Begin Autonomous Alarm Purge by IMS** - -- 1 (Autonomous) IMS Operations Trigger (IMS → IMS) -- Old Alarm exceeds Retention Period -- Alarms are Purged (removed from the Alarm List) autonomously by IMS - -**End Autonomous Alarm Purge by IMS** - -UML Sequence Diagram for Alarm Purge. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows three main sequences: 1. Operator/SMO initiated (Forced) Alarm Purge, 2. Alarm Purge from Alarm List Configuration Change of Retention Period, and 3. Autonomous Alarm Purge by IMS. Each sequence includes preconditions, request messages, processing steps, and return messages or exception handling. - -Figure 3-39: Alarm Purge - -### 3.7.14 Log Discovery Use Case - -#### 3.7.14.1 High Level Description - -This use case describes the process for discovering the logs available within an O-Cloud. The goal is to discover what logs are available in an O-Cloud. This use case does not return the contents of the logs. Refer to clause 3.7.8 Log Query for details of how logs that have been discovered may subsequently be queried for their contents. Refer to clause 3.7.10 Logging Configuration for details of how logs that have been discovered may subsequently be configured. Because different O-Cloud implementations may be built out of different software components, Log Discovery is necessary to determine what logs are present in a specific O-Cloud prior to performing Log Query or Logging Configuration. - -#### 3.7.14.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Log Discovery Use Case | | -| Goal |

The goals of this use case are to:

  • Discover available logs in an O-Cloud related to a specific resource (e.g. O-Cloud site, O-Cloud cluster, O-Cloud node) or the entire O-Cloud.
| | -| Actors and Roles |

O-Cloud Operator – The O-Cloud operator is a user that is interested in discovering what logs are available to be queried or configured.

Service Management Orchestrator (SMO) – The FOCOM in the SMO is the consumer that will request the discovery of logs.

Infrastructure Management Services (IMS) – The IMS processes the request for the discovery of logs. The O-Cloud IMS functionality acts as a manager for any requesting authorized client.

| | -| Assumptions |

The following assumption is relevant to this use case:

  • Logs exist
| | -| Preconditions |

Connectivity – The Subscriber has connectivity to the Publisher by some mechanism. The mechanism by which the subscriber achieves connectivity to the publisher is out of the scope of this Use Case.

O-Cloud Operational – The O-Cloud is installed, operating, and registered with the SMO.

Privilege – The consumer identification and privileges of a SMO user have been verified to be able to perform O2 operations.

| | -| Begins when | This use case begins when there is a request to discover available O-Cloud logs. | | -| Step 1 (M) |

A request to get a list of O-Cloud logs is sent from an entity or O-Cloud Operator to FOCOM.

A Resource as defined in Clause 4.2.1.4.4 of WG6 O-Cloud Information Model [23] may be supplied as an optional filter to determine which logs will be discovered. It is not guaranteed that all Resources will have logs.

A non-exhaustive list of Resources that might be good choices for performing Log Discovery on includes:

  • O-Cloud Node Cluster
| | - -| | | | -|---------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |
  • • O-Cloud Node
  • • O-Cloud Gateway
  • • O-Cloud Attachment Circuit
  • • O-Cloud Site
  • • AAL Hardware Accelerator Manager

Logs are not necessarily stored on, in or by the Resource, it is left to the IMS to determine which logs, if any, are associated with the Resource that is optionally supplied in the filter.

It is expected that the logs available in an O-Cloud will depend on the vendor implementation and will vary between O-Clouds depending on the constituent software out of which different vendors construct their O-Cloud.

| | -| Step 2 (M) | A request to get a list of O-Cloud logs is sent from FOCOM to IMS (optionally with an O-Cloud Resource as a filter). | | -| Step 3.1-3.2 (M) |

The IMS responds with the list of available logs for either the entire O-Cloud or for the specified Resource.

If a Resource supplied as an optional filter is of a Resource Type that does not have logs, the list returned will be empty. This is not an exception case.

It is possible that there may be difference between O-Cloud vendors in which Resource Types have logs. This use case does not mandate which Resource Types have logs associated with them or what logs must exist in an O-Cloud.

| | -| Step 3.3-3.4 (ALT) | An unexpected condition occurs, and an exception is returned | | -| Ends when | This use case ends when a successful response is received from the O-Cloud with the list of available logs or when an Exception is encountered. | | -| Exceptions | Unexpected conditions | | -| Post-conditions |

The SMO has discovered the available O-Cloud logs or has encountered an error.

See Note

| | -| Traceability | [REQ-ORC-O2-117], [REQ-ORC-O2-118] | | -| | Note: An entity or O-Cloud Operator may choose from among the available logs for other log related requests. SMO (FOCOM) may store the list of discovered logs. | | - -#### 3.7.14.3 UML Sequence Diagram - -![UML Sequence Diagram for Discovery O-Cloud Logs. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The sequence starts with PRECONDITIONS, followed by Begin Log Discovery, Log Discovery Requests, a Successful Command alt block (with Store discovered list of O-Cloud Logs opt block), an Exception: Unexpected Condition alt block (with Failure Case), and End Log Discovery.](9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg) - -``` - -sequenceDiagram - actor O-Cloud Operator as Personnel - participant FOCOM as Service Management & Orchestration Framework (Subscriber) - participant IMS as O-Cloud Platform (Publisher) - - Note right of FOCOM: PRECONDITIONS: -SMO has connectivity to O-Cloud -O-Cloud has registered its IMS with the SMO -The identification & privileges of a SMO user has been verified - - Note over FOCOM: Begin Log Discovery - O-Cloud Operator->>FOCOM: 1 Log Discovery Request - FOCOM->>IMS: 2 Log Discovery Request - Note right of IMS: IMS processes Log discovery Request - - alt Successful Command - IMS-->>FOCOM: 3.1 Log Discovery Results(Success) - Note right of FOCOM: opt Store discovered list of O-Cloud Logs - FOCOM-->>O-Cloud Operator: 3.2 Log Discovery Results - else Exception: Unexpected Condition - IMS-->>FOCOM: 3.3 Unexpected Condition - Note right of FOCOM: Failure Case - FOCOM-->>O-Cloud Operator: 3.4 Exception Response - end - - Note over FOCOM: End Log Discovery - -``` - -UML Sequence Diagram for Discovery O-Cloud Logs. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The sequence starts with PRECONDITIONS, followed by Begin Log Discovery, Log Discovery Requests, a Successful Command alt block (with Store discovered list of O-Cloud Logs opt block), an Exception: Unexpected Condition alt block (with Failure Case), and End Log Discovery. - -Figure 3-40: Discovery O-Cloud Logs - -## 3.8 Performance Use Cases - -### 3.8.1 Performance Measurement Job Creation Use Case - -#### 3.8.1.1 High Level Description - -A Performance Measurement Job (PM Job) is a task for collecting measurements and metrics related to O-Cloud Resources. It is the central entity for coordinating performance management activities. The IMS collects metrics and measurements from O-Cloud Resource(s). The PM Job is created in the IMS. - -NOTE 1: The concept of PM Job is described in O-RAN WG6 GA&P, Clause 3.9.5. - -This use case describes: - -- (1) The creation of PM Job(s) -- (2) The collection and processing of measurement data from O-Cloud Resource(s) tasked by the PM Job. - -NOTE 2: processing entails operations such as the conversion of counters from one form to another, storage of data, scraping data from one format to another. - -#### 3.8.1.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Performance Measurement Job (PM Job) Creation Use Case | | -| Goal | The PM Jobs are created within the IMS.
Performance data is made available to the SMO by the PM Jobs. | | -| Actors and Roles | SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer of performance data.
IMS – The IMS within the O-Cloud is used to represent any provider of the performance data.
O-Cloud Resource – This is a resource in the O-Cloud that produces metrics and measurements. See WG6 O2 CADS [7] for definition of an O-Cloud Resource. | | -| Assumptions | There are no assumptions. | | -| Preconditions | Connectivity – The Subscriber has connectivity to the Publisher by some mechanism. The mechanism by which the subscriber achieves connectivity to the publisher is out of the scope of this Use Case. | | -| Begins when | The Use Case begins during O-Cloud genesis when the O-Cloud starts Preinstalled PM jobs. | | -| Step 1 (M) | PREINSTALLED PM JOBS STARTED – O-Cloud Preinstalled PM Jobs are started within the IMS upon cloud genesis. These Preinstalled PM Jobs address Performance Management needs for O-Cloud functions. | | -| Step 2 (M) | IMS INFORMS SMO PREINSTALLED PM JOBS – The IMS informs SMO of the Preinstalled PM Jobs that have been started within the IMS after O-Cloud genesis. | | -| Step 3 (OPT) | SMO REQUEST – (Optional) SMO Requests for additional PM Jobs.
(Optional) If the request contains subscription related information, then an embedded subscription will be created as part of the created PM Job(s) or threshold(s).
See note 1 and 2. | | -| Step 4 (OPT) | IMS RESPONSE – PM Jobs creation status returns the status of PM Jobs running in the IMS. | | -| Step 5.1 (M) | OPERATION – O-Cloud resources operate. | | -| Step 5.2 (M) | DATA CREATED – Performance data (metrics and measurements) is identified. | | -| Step 5.3 (M) | DATA COLLECTED BY IMS – The O-Cloud resources send performance data to the IMS. The collected performance data is processed according to the PM Jobs. The PM Jobs make the performance data available for reporting. | | - -| | | | -|------------------------|--------------------------------------------------------------------------------------------------|--| -| Ends when | The Use Case ends when the PM Jobs have a body of data ready for reporting. | | -| Exceptions | None specified in the present document version. | | -| Post-conditions | The PM Jobs have performance data across O-Cloud Resources available for subscription reporting. | | -| Traceability | [REQ-ORC-O2-31, REQ-ORC-O2-32] | | - -NOTE 1: An *embedded subscription* means to optionally embed subscription related into the PM Job or threshold. Ends up in created PM Job objects. - -NOTE 2: This allows the SMO to request for a subscription following the ETSI format or the 3GPP procedure. - -#### 3.8.1.3 UML Sequence Diagram - -![UML Sequence Diagram for PM Job Creation. Lifelines: FOCOM (Service Management & Orchestration Framework), IMS (O-Cloud Platform), and OC Resource (O-Cloud Platform). The sequence starts with a precondition 'SMO has connectivity to O-Cloud'. It then enters the 'Performance Measurement Job (PM Job) Creation Use Case'. Step 1: 'O-Cloud Node Preinstalled PM jobs are started' (internal IMS message). Step 2: '2 PM Jobs status (Preinstalled jobs)' from IMS to FOCOM. Step 3: Inside an 'opt [SMO Requests for PM Jobs]' block, '3 SMO requests for additional PM Jobs' from FOCOM to IMS. Step 4: '4 PM Jobs status response to SMO request' from IMS to FOCOM. Step 5: 'PM job(s) are created or triggered' (internal IMS message). Sub-steps 5.1-5.3: 'Operations generate data', 'Performance data created', and 'Data is sent to the IMS' (internal OC Resource to IMS messages). A note indicates 'Performance data is collected across O-Cloud and processed according to the PM Job(s)'. Another note indicates 'Data made available for reporting'. The sequence ends with 'End Performance Measurement Job (PM Job) Creation Use Case'.](a3d6b1f562612dbd5a5d7c4ce91999d1_img.jpg) - -``` - -sequenceDiagram - participant FOCOM as Service Management & Orchestration Framework - participant IMS as O-Cloud Platform - participant OC_Resource as O-Cloud Resource - - Note right of FOCOM: Precondition: SMO has connectivity to O-Cloud - - Note over FOCOM, IMS: Performance Measurement Job (PM Job) Creation Use Case - - Note right of IMS: 1 O-Cloud Node Preinstalled PM jobs are started - IMS->>FOCOM: 2 PM Jobs status (Preinstalled jobs) - - opt SMO Requests for PM Jobs - FOCOM->>IMS: 3 SMO requests for additional PM Jobs - IMS->>FOCOM: 4 PM Jobs status response to SMO request - end - - Note right of IMS: PM job(s) are created or triggered - - Note right of OC_Resource: 5.1 Operations generate data - Note right of OC_Resource: 5.2 Performance data created - Note right of OC_Resource: 5.3 Data is sent to the IMS - OC_Resource->>IMS: 5.3 Data is sent to the IMS - - Note right of IMS: Performance data is collected across O-Cloud and processed according to the PM Job(s). - Note right of IMS: Data made available for reporting - - Note over FOCOM, IMS: End Performance Measurement Job (PM Job) Creation Use Case - -``` - -UML Sequence Diagram for PM Job Creation. Lifelines: FOCOM (Service Management & Orchestration Framework), IMS (O-Cloud Platform), and OC Resource (O-Cloud Platform). The sequence starts with a precondition 'SMO has connectivity to O-Cloud'. It then enters the 'Performance Measurement Job (PM Job) Creation Use Case'. Step 1: 'O-Cloud Node Preinstalled PM jobs are started' (internal IMS message). Step 2: '2 PM Jobs status (Preinstalled jobs)' from IMS to FOCOM. Step 3: Inside an 'opt [SMO Requests for PM Jobs]' block, '3 SMO requests for additional PM Jobs' from FOCOM to IMS. Step 4: '4 PM Jobs status response to SMO request' from IMS to FOCOM. Step 5: 'PM job(s) are created or triggered' (internal IMS message). Sub-steps 5.1-5.3: 'Operations generate data', 'Performance data created', and 'Data is sent to the IMS' (internal OC Resource to IMS messages). A note indicates 'Performance data is collected across O-Cloud and processed according to the PM Job(s)'. Another note indicates 'Data made available for reporting'. The sequence ends with 'End Performance Measurement Job (PM Job) Creation Use Case'. - -Figure 3-41: PM Job Creation - -### 3.8.2 Performance Management Subscription Use Case - -#### 3.8.2.1 High Level Description - -This use case describes the flow for an entity to subscribe to Performance Management data from an O-Cloud. Performance Measurement Jobs collect and compose measurements. The PM Subscription determines when and how those measurements are reported. The subscription allows a subscriber to get data that has been collected in the O-Cloud. Once subscribed, the measurement data is sent to a performance management subscriber, an entity north-bound of the O-Cloud. In the O-RAN context, it is the SMO; however, it could be another other subscribing entity. - -![Figure 3-42: PM Data and PM Subscription flow between SMO and O-Cloud.](f99313b06c15e9882079b773ce50a7b2_img.jpg) - -``` - -sequenceDiagram - participant SMO as Service Management Orchestrator (SMO) - participant IMS as Infrastructure Management Service (IMS) - participant PMJ as PM Job(s) - participant OCR as O-Cloud Resource - - Note over SMO: Metrics used in Analysis - SMO->>IMS: Performance Management Subscription - OCR->>PMJ: Measurement / Telemetry data - PMJ->>IMS: Gathered Data - IMS->>IMS: Performance Subscription Manager (Composes Report) - IMS->>SMO: Measurement Stream / Measurement Report - Note over SMO: Subscriber/Notification Endpoint - -``` - -The diagram illustrates the flow of Performance Management (PM) data and subscription between the Service Management Orchestrator (SMO) and the O-Cloud. The SMO (top) contains a 'Measurement Report' icon, a 'Subscriber/Notification Endpoint' icon, and a 'Metrics used in Analysis' box. The O-Cloud (bottom) contains 'O-Cloud Resource' icons feeding 'Measurement / Telemetry data' into 'PM Job(s)'. The 'Infrastructure Management Service (IMS)' within the O-Cloud includes a 'Performance Subscription Manager' that interacts with a local database. Arrows indicate a 'Performance Management Subscription' going from the SMO to the IMS, and a 'Measurement Stream' / 'Measurement Report' flowing from the IMS 'Publisher endpoint' to the SMO. - -Figure 3-42: PM Data and PM Subscription flow between SMO and O-Cloud. - -Figure 3-42: PM Data and PM Subscription - -The Figure above shows the basic flow of Performance Data collection and subscription. Measurement and telemetry data is collected within the O-Cloud and gathered by PM Job(s) and stored locally. The Performance Subscription Manager within the IMS can retrieve the data to be sent to the SMO. There is a publisher and subscriber notification end point that is used to send the performance data to that is defined in the subscription. Measurement reports are composed at the Performance Subscription Manager within the IMS and can then be used to perform analysis on within the SMO. - -Performance measurements in an O-Cloud might use event notification reporting, stream-based reporting, or file-based reporting to a subscriber. For performance measurements to be sent, a subscription needs to be created. The subscription indicates an end point for where the performance measurements should be sent to. The subscription filter qualifies what data from the PM Jobs should be sent. - -The subscription will indicate the interval. A capabilities exchange could occur between the SMO and the O-Cloud indicating the mechanism and formats supported by the O-Cloud. The SMO can then subscribe to the mechanisms and formats within the subscription filter. In the capabilities exchange, the IMS would report the jobs and their collection intervals. - -#### 3.8.2.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Performance Management Subscription (IMS) | | -| Goal |

This use case describes a flow where one or more consumers which want to receive performance event reporting notifications (file ready notifications, event notification reporting, or streaming reporting) can issue a subscription to IMS which publishes Performance events.

Each SUBSCRIBER has a consumer subscription identifier. There is one consumer subscription identifier per subscription. It doesn't have to be unique for that subscription. The consumer subscription identifier is a character string that can be associated with meta-data within the SMO. See note.

| | -| Actors and Roles |

SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer of performance measurement data.

IMS – The IMS within the O-Cloud is used to represent any provider of the performance measurement data.

| | -| Assumptions |

There can be multiple subscribers to a single publisher. The subscriber-publisher cardinality is not enforced nor monitored.

Each subscription is associated with one subscriber. Each subscription provides information about a single endpoint for receiving performance related notifications. Thus, there cannot be multiple endpoints for sending performance related notifications from a single subscription.

The subscriber may not be the ultimate consumer of performance notifications. The subscriber is not necessarily the same entity as the endpoint for notifications.

| | -| Preconditions |

CONNECTIVITY– The Subscriber has connectivity to the publisher by some mechanism. The mechanism by which the subscriber achieves connectivity to the publisher is out of the scope of this Use Case.

O-Cloud OPERATIONAL– O-Cloud is installed, operating, and the IMS in the O-Cloud has registered with SMO.

| | -| Begins when |

The use case is triggered when a subscriber wishes to:

  • (1) NOTIFICATION – A subscriber wishes to be notified of O-Cloud performance events.
  • (2) OPERATOR INITIATED - An O-Cloud operator may also initiate a subscription.
| | -| Step 1 (M) |

NOTIFICATION CRITERIA – This gives a notification criterion which initiates the subscription.

The subscription criteria will indicate whether the subscribing entity wish to have file based, event notification based, or streaming based performance reporting.

| | -| Step 2 (M) |

SUBSCRIPTION – The subscriber sends a performance event subscription to the publisher. The subscription includes the Consumer Subscription Identifier.

| | -| Step 3 (O) |

CALLBACK REACHABILITY CHECK (Should) – A Reachability Check can be performed between the subscriber and publisher. This is a connectivity and authorization check. This check is optional. However, it is recommended that a

| | - -| | | | -|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | reachability check is performed. This step should be performed; though it is stated as optional in ETSI IFA 032 [19]. | | -| Step 4 (ALT) | REACHABILITY SUCCESS – This step indicates that the reachability check has passed successfully. | | -| Step 5 (ALT) | REACHABILITY FAILURE – This step indicates that the reachability check has failed. | | -| Step 6 (ALT) | SUBSCRIPTION DENIED (FAILURE) – The IMS has failed the reachability check. IMS will proceed to deny the performance subscription. | | -| Step 7 (ALT) | SUBSCRIPTION STATUS (FAILURE) – If the reachability check has failed, the subscription status will indicate a failure. The use case will end at this point. This is a return to Step 2. | | -| Step 8 (M) | SUBSCRIPTION ACKNOWLEDGE – The publisher indicates a subscription acknowledge. This essentially indicates a success for the subscription. (Optional) The consumer subscription identifier may be passed back in the subscription acknowledge. | | -| Step 9 (M) | SUBSCRIPTION STATUS (SUCCESS) – A subscription status will indicate a success back to O-Cloud Operator. This is a return to Step 1. | | -| Ends when | This use case ends when a performance subscription status has been sent successfully or on one of the failure cases, when there was a subscription failure. | | -| Exceptions | FAILURE CASE 1: FAILURE INDICATION - The Subscription acknowledge indicates a failure.
FAILURE CASE 2: CONNECTIVITY ISSUE - Can't reach the publisher, the reachability check has failed.
ALTERNATE CASE 1: VALIDITY CHECK (Optional) – A validity check confirms the reachability of the callback endpoint, checking that the publisher has permission to reach the consumer through a TLS connection. If a validity check is performed AND it fails, this would lead to Fail Case 2 (Connectivity Issue). | | -| Post-conditions | SUCCESS: The publisher has the subscriber call-back (a fully qualified URL), and it is persisted. The publisher has created its own internal association for subscription which includes the consumer subscription identifier, the call-back URL and subscription filter.
FAILURE: The performance subscription operation has failed. See the exception cases. | | -| Traceability | REQ-ORC-02-15, REQ-ORC-02-37, REQ-ORC-02-38 | | -| NOTE: The general event Subscribe pattern is defined in clause 5.9 of ETSI GS NFV-SOL 015 and clause 4.6.2 of 3GPP TS 29.501 [13]. An example of this is in clause 7.5.4 of ETSI GS NFV-IFA 013 for Performance Management subscribe operation with filtering. Examples of Performance Management operations applied to Network Service objects are described in (stage 2) clause 7.5 of ETSI GS NFV-IFA 013 [16]. | | | - -#### 3.8.2.3 UML Sequence Diagram - -![Sequence diagram for IMS Performance Management Subscription Use Case. Lifelines: Cloud Operator (Personnel), Service Management & Orchestration Framework (Subscriber) with FOCOM, and O-Cloud Platform (Publisher) with IMS. The process involves notification criteria, subscription, a reachability test, and a final subscription status.](65b5e4a95d403df0ea5e8ff94f162a6a_img.jpg) - -The sequence diagram illustrates the interaction for the IMS Performance Management Subscription Use Case. It begins with preconditions: SMO has connectivity to O-Cloud and O-Cloud has registered its IMS with the SMO. The Cloud Operator sends a '1 Notification Criteria' message to FOCOM. FOCOM sends a '2 Subscription' message to IMS, which responds with 'Subscription has consumer subscription identifier'. An 'opt [Reachability Test]' block follows. Inside, FOCOM sends a '3 Callback Reachability Check (Should)' to IMS. An 'alt [If Reachable and Authorized]' block contains two paths: '4 Reachability Success' (dotted return) and '5 Reachability Failure' (dotted return). The 'Failure Case' path continues with '6 Subscription Denied (Failure)' (dotted return) and '7 Subscription Status (Failure)' (dotted return to operator), ending the use case. The 'Success' path continues with '8 Subscription Acknowledge' (dotted return) and '9 Subscription Status (Success)' (dotted return to operator). The diagram then transitions to the 'Performance Management Subscription End Use Case'. - -Sequence diagram for IMS Performance Management Subscription Use Case. Lifelines: Cloud Operator (Personnel), Service Management & Orchestration Framework (Subscriber) with FOCOM, and O-Cloud Platform (Publisher) with IMS. The process involves notification criteria, subscription, a reachability test, and a final subscription status. - -Figure 3-43: PM Subscription - -### 3.8.3 Performance Measurement Event Notification Reporting Use Case - -#### 3.8.3.1 High Level Description - -In the context of O-RAN Cloud managed systems, performance measurements can be transmitted by one of three Report delivery mechanisms: event notification(s), streaming based reporting, or file-based reporting. The performance management subscription use case defined the service connection end point where the events are sent to in the subscription filter. - -- **EVENT NOTIFICATIONS** – Event based reporting would send individual events to a subscriber and a connection is opened each time a notification is to be sent. Non-real-time performance measurements could use event-notification reporting mechanisms. -- **STREAMING BASED REPORTING** – Streaming is typically used for a continuous session to send performance measurement data. For streaming, the connection is opened and kept open without having to renegotiate. - -- **FILE REPORTING** – Off-line, or non-real time performance measurements could use file-based or event-notification reporting mechanisms. - -The SMO is expected to support all three of the above Report delivery mechanisms. However, any given IMS (O-Cloud) implementation may not support all three. - -This use case will cover performance measurement event notification reporting to send performance data. An entity that subscribes to these performance measurement event notifications will get an event or callback invoked for each reporting message. - -Notification reports are based on a subscription. The performance management subscription determines three things: - -- **REPORTING FREQUENCY** – The subscription filter indicates the reporting frequency when data is included in a report. The subscription filter establishes the trigger mechanism during the subscription that triggers when the callback would be invoked. -- **REPORT DELIVERY MECHANISM** – The Report delivery mechanism is specified in the subscription filter. The Report delivery mechanisms are event notifications, streaming based reporting, or file reporting mechanisms. The Report delivery mechanism will be defined in the information model. See WG6.O-CLOUD-IM [23], clause 4.2.1.4.21 for more details. -- **ITEMS TO REPORT** - It is expected each criterion define: a list of PM Jobs and their lists of measures that are of interest to report. - -Event based notification would be utilized for low frequency and low volume of reporting since a session is re-established with the sending of each event. At higher data volumes a continuous session would be more efficient. See the streaming reporting use case for more details. - -There are three basic exception cases: - -- **CONNECTION LOST** – If connectivity between the subscriber and the publisher (IMS) is lost, a connection would not be able to be opened. There are implementation considerations such as: how long data is held for, recovery of the connection, backing up data, preventing data storms upon recovery, and management after recovery. -- **DATA UNAVAILABLE** – This exception occurs when the performance measurement data is not available in the O-Cloud on the IMS when it should be reported. This results in a missed timing window when data was expected, but it was not available. In the interface, it would be expected the notification would indicate data was unavailable. There are implementation considerations such as: O-Cloud failures, IMS failures, data recovery, and data synchronization. -- **PM JOB FAILURES & ISSUES** – If the PM Job is unable to perform its function. If there are failures or issues with the PM Job(s) which might result in data being unavailable it is expected that there would alarms that would be raised by the IMS. This results in data being unavailable. - -#### 3.8.3.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <> Related Use | -|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Use Case Title | Performance Measurement Event Notification Reporting (IMS) Use Case | | -| Goal | The following goals for this use case are:

SEND EVENTS – To report performance data through an event-based reporting mechanism to a subscriber.

CONNECTION – To establish a connection to the subscriber to send performance data. | | - -| | | | -|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Actors and Roles |

SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer of performance measurement data.

IMS – The IMS within the O-Cloud is used to represent any publisher of the performance measurement data.

| | -| Assumptions |

It is assumed that performance management subscription has been established.

It is also assumed that the Performance Measurement (PM) Job Creation use case has successfully completed.

| | -| Preconditions |

CONNECTIVITY – The Subscriber has connectivity to the publisher.

AUTHENTICATION – The Publisher has user credentials for the Subscriber’s end point.

PM JOB(S) ACTIVE – PM Job(s) are running and actively collecting performance measurement data.

| | -| Begins when | When the Performance Subscription Manager (PSM) determines that performance data should be sent | | -| Step 1.1 (M) | DATA TO BE SENT – The Performance Subscription Manager based on the subscription(s) determines that performance data needs to be sent, and the subscription criteria indicate that data should be sent with an event notification. | | -| Step 1.2 (M) | RETRIEVE DATA – The PSM retrieves the performance data from the local storage. The performance data is written by the PM Job(s) within the O-Cloud. The data is composed to be ready to be sent. See note 1. | | -| Step 2 (M) | OPEN CONNECTION – A connection is attempted by the IMS to the subscription endpoint. The subscription endpoint is typically the SMO but could be some other entity. | | -| Step 3 (ALT) | CONNECTION TO ENDPOINT SUCCESSFUL – The connection to the subscription endpoint was opened successfully, and a success response is given to the publisher (IMS). | | -| Step 4 (ALT) | EXCEPTION: CONNECTION CANNOT BE ESTABLISHED – A connection could not be established to the endpoint. See notes 2, 3, and 4. | | -| Step 5 (M) | SEND PERFORMANCE NOTIFICATION EVENT – A connection has been successfully established. IMS sends performance data in a performance event notification. | | -| Step 6 (ALT) | PERFORMANCE DATA RECEIVED RESPONSE – The performance data was received successfully by the subscriber. A Performance Data Received response is sent to the publisher (IMS). | | -| Step 7 (ALT) |

EXCEPTION: RECEIVER REJECTED REQUEST – The receiver (subscriber) is indicating to the publisher (IMS) that it has rejected the data. This might occur with loss of user privilege.

Translations of the data type or not following the proper data format may result in this exception. Conversion of the data was improper. Format rejected. For example, yang data requested, json sent.

This exception is suggested to be logged; however, it is left up to the implementation if it is logged.

| | - -| | | | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | In the received rejected data the post-condition is that the subscriber likely suspends the job. The subscription exists, but data cannot be sent. | | -| Ends When | This Use Case ends when either the Performance Measurement Event Notification has been sent successfully, or one of the two Exception cases has been encountered – Connection would not be established, or the receiver rejected the data. | | -| Exceptions | EXCEPTION: CONNECTION CANNOT BE ESTABLISHED – In this case, a connection to the subscriber endpoint was attempted but could not be established.

EXCEPTION: RECEIVER REJECTED REQUEST – In this case, the subscriber has indicated that it is rejecting the data. | | -| Post-conditions | SUCCESSFUL – A successful post condition is that a connection is successfully opened. The performance measurement notification event has been sent and then the connection closed.

FAILURE – The use case may end with a post-condition where it encountered one of the two exceptions. If the connection was unable to be established, attempts to reopen the connection might be tried. In the received rejected data the post-condition is that the subscriber likely suspends the job. The subscription exists, but data cannot be sent. | | -| Traceability | [REQ-ORC-O2-39] | | -|

NOTE 1: It might be possible that the resource might be unavailable, and objects are deleted and data from the resource are not available. This would be incorporated into the data to be sent.

NOTE 2: It is expected that most IMS implements would log a fault would be logged in this case by the IMS.

NOTE 3: A dead subscription endpoint might be encountered. In this case, a retry interval might be specified; after which it will attempt to reopen a connection. A configuration for a set number of attempts might also be used. However, it is left up to implementation for a specific solution.

NOTE 4: This exception is suggested to be logged; however, it is left up to the implementation if it is logged.

| | | - -#### 3.8.3.3 UML Sequence Diagram - -![UML Sequence Diagram for Performance Measurement Event Notification Reporting Use Case. Lifelines: Service Management & Orchestration Framework (Subscriber) with FOCOM, and O-Cloud Platform (Publisher) with IMS. The diagram shows the interaction for reporting performance measurement events, including connection opening, data identification, data retrieval, and data sending with success or failure handling.](921f8fa0f7ce2c9956f20d33162c13a2_img.jpg) - -``` - -sequenceDiagram - participant FOCOM as Service Management & Orchestration Framework (Subscriber) - participant IMS as O-Cloud Platform (Publisher) - Note right of IMS: Precondition: IMS has connectivity to SMO -PM Job(s) running - - Note over FOCOM, IMS: Performance Measurement Event Notification Reporting Use Case - - Note right of IMS: Performance Subscription Manager (PSM) -determines what and when to send data - - IMS-->>IMS: PSM 1.1 identifies data - IMS-->>IMS: PSM 1.2 retrieves PM Data - - FOCOM->>IMS: 2 Open Connection - - alt Connection to Endpoint Successful - IMS-->>FOCOM: 3 Open Connection (Success) - else Exception: Cannot open connection or connection was lost / Failure Case - IMS-->>FOCOM: 4 Connection cannot be established - end - - FOCOM->>IMS: 5 Send Performance data in a performance event notification - - alt Performance Data Sent Successfully - IMS-->>FOCOM: 6 Performance Data Received Response - else Exception: Receiver rejected data - IMS-->>FOCOM: 7 Receiver Rejected data - end - - Note over FOCOM, IMS: End Performance Measurement Event Notification Reporting Use Case - -``` - -UML Sequence Diagram for Performance Measurement Event Notification Reporting Use Case. Lifelines: Service Management & Orchestration Framework (Subscriber) with FOCOM, and O-Cloud Platform (Publisher) with IMS. The diagram shows the interaction for reporting performance measurement events, including connection opening, data identification, data retrieval, and data sending with success or failure handling. - -Figure 3-44: Performance Measurement Event Notification Reporting - -### 3.8.4 Performance Measurement Streaming Reporting Use Case - -#### 3.8.4.1 High Level Description - -In the context of O-RAN Cloud managed systems, performance measurements can be transmitted by one of three Report delivery mechanisms: active collection by a consumer, active push by a producer (e.g. streaming-based reporting), and/or file-based reporting. The performance management subscription use case defines the service connection end point where the events are sent to in the subscription filter. Both active push and active collection have similar purposes, but the active control is with either the producer or consumer. - -- **ACTIVE PUSH BY A PRODUCER** – A producer (IMS) could send performance data through pushing data to a consumer. At least two options may be identified: - - **ACTIVE SESSION** – A session is a continuous data flow between consumer & producer for data reporting. For streaming, the data flow is typically established and kept open without having to renegotiate. Streaming is used to send a flow of performance measurement data bursts. Once the data flow , i.e. session is established, the meta-data about the streams is exchanged, the consumer can then receive the serialized data. The point is that meta-data does not need to be exchanged with every data burst. The session can be connection based, or non-connection based e.g. Message bus. - - **EVENT NOTIFICATIONS** – The second option is by event notifications, where a new connection is reestablished between a consumer and producer for each data reporting. This is like how 5GC SBA - -works (3GPP TS23.501 5G Architecture [26], TS23.502 procedures [27]). The data is sent as a payload of a notification. The major difference is in the overhead associated with the notification because even to report a small amount of data requires the header and establishing a connection. - -- **ACTIVE COLLECTION BY A CONSUMER** – The consumer could also actively collect data from a producer. - - o **CONFIGURATION MANAGEMENT READ ONLY ATTRIBUTES** – Reuse of configuration management approach where attribute conveying the value of performance data is read by the consumer like any other configuration management attribute. - - o **DATA SCRAPING** – Use of data scraping common to cloud native implementations where a collector reads the data from a pre-defined URI. -- **FILE BASED REPORTING** – File based reporting is not used for real-time, historically it is used for low-priority or background collection for large amounts of performance data. The file-based reporting has potential options: file upload by the producer and file download by the consumer following a file ready notification. - - o **FILE UPLOAD BY PRODUCER** – There is not an artificial delay, the data is reported whenever it is available. The shortfall is that it involves action by the producer. - - o **FILE DOWNLOAD BY CONSUMER** – It removes the burden from the producer, but may rely upon either periodic polling, or notification from the producer about the data being ready for download. The latter case is how 3GPP file-based reporting works in 3GPP TS28.532 Clause 11.6 [25]; and ETSI ISG NFV specifications (IFA008 [28], IFA013 [16]). - -The SMO is expected to support all three of the above Report delivery mechanisms. However, any given IMS (O-Cloud) implementation may not support all three. - -To stream performance measurements, a connection session is established between the IMS as a publisher and a subscriber (FOCOM at the SMO). While the connection persists, performance data would be transmitted while it matches the subscription filter. - -Performance Data is sent to the subscriber endpoint based on the subscription filter. The PM Jobs collect performance data and store it locally. When the subscription indicates when data would be sent, the Performance Subscription Manager (PSM) within the IMS retrieves data. Then, the PSM formats it and sends it in a notification event in a stream. Thus, streaming-based reporting sends performance data to a subscriber endpoint based on a subscription. The subscription filter may give an interval or specify a trigger. Each element may have a criterion that determines when it is sent. - -#### 3.8.4.2 Sequence Description for WebSocket Based Streaming - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Performance Measurement Streaming Reporting Use Case | | -| Goal |

This Use Case describes Performance Measurement Streaming Reporting. Performance Measurement data is sent periodically or triggered as specified by the subscription filter.

The connections are kept open for the duration of a streaming session.

This use case has the following goals:

  • - If a connection is not already opened, then open a connection to report streaming performance data. See note 1.
  • - Send a series of performance measurement data through the opened connection based on the subscription filter.
| | -| Actors and Roles |

SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer of performance measurement data.

IMS – The IMS within the O-Cloud is used to represent any publisher of the performance measurement data.

| | - -| | | | -|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Assumptions |

SUBSCRIPTION EXISTS - It is assumed that performance management subscription has been established.

PM JOBS - It is also assumed that the Performance Measurement (PM) Job create use case has successfully completed.

| | -| Preconditions |

CONNECTIVITY – The Subscriber has connectivity to the Publisher.

AUTHENTICATION – The Publisher has user credentials for the Subscriber's end point.

PM JOB(S) ACTIVE – PM Job(s) are running and actively collecting performance measurement data.

| | -| Begins when |

This use case begins when the subscription filter at the IMS indicates that a streaming performance data session should be opened. -or-

This use case begins when the subscriber initiates a streaming session.

| | -| Step 1.1 (M) |

DATA TO BE SENT – The Performance Subscription Manager (PSM) based on the subscription(s) determines that performance data needs to be sent, and the subscription filter indicates that data should be sent with a performance measurement streaming reporting.

| | -| Step 1.2 (M) |

RETRIEVE DATA – The PSM retrieves the performance data from the local storage. The performance data is written by the PM Job(s) within the O-Cloud. The data is composed to be ready to be sent. See notes 2, 3, 4, and 5.

| | -| Step 2.1 (ALT1) |

PUBLISHER INITIATED SESSION CONNECTION

OPEN CONNECTION – If Publisher (IMS) does not already have a connection to the Subscriber (FOCOM), then IMS attempts to open a connection to the subscription endpoint. The Subscriber is typically the SMO but could be some other entity.

| | -| Step 2.2 (ALT1) |

PUBLISHER INITIATED SESSION CONNECTION

CONNECTION TO ENDPOINT SUCCESSFUL – The connection to the subscription endpoint was opened successfully, and a success response is given to the publisher (IMS).

| | -| Step 2.3 (ALT1) |

PUBLISHER INITIATED SESSION CONNECTION

EXCEPTION: CONNECTION CANNOT BE ESTABLISHED – A connection could not be established to the subscription endpoint. See note 6.

In this case, the use case ends. See notes 7 and 8.

| | -| Step 3.1 (ALT2) |

SUBSCRIBER INITIATED SESSION CONNECTION

OPEN CONNECTION – If FOCOM does not already have a connection to the Publisher (IMS), then FOCOM attempts to open a connection to the Publisher endpoint.

| | -| Step 3.2 (ALT2) |

SUBSCRIBER INITIATED SESSION CONNECTION

CONNECTION TO ENDPOINT SUCCESSFUL – The connection to the subscription endpoint was opened successfully, and a success response is given to the Subscriber (FOCOM).

| | - -| | | | -|-----------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 3.3 (ALT2) |

SUBSCRIBER INITIATED SESSION CONNECTION

EXCEPTION: CONNECTION CANNOT BE ESTABLISHED – A connection could not be established to the Publisher endpoint.

In this case, the use case ends. See notes 9 and 10.

| | -| Step 4 (M) |

SEND PERFORMANCE STREAM – A connection has been successfully established or a connection already exists between the Publisher and Subscriber.

The IMS sends performance data in a performance stream.

| | -| Step 5 (ALT) |

PERFORMANCE DATA RECEIVED RESPONSE – The performance data was received successfully by the Subscriber. A Performance Data Received response is sent to the Publisher (IMS).

| | -| Step 6 (ALT) |

EXCEPTION: RECEIVER REJECTED REQUEST – The receiver (subscriber) is indicating to the Publisher (IMS) that it has rejected the data. This might occur with loss of user privilege.

Translations of the data type or not following the proper data format may result in this exception. Conversion of the data was improper. Format rejection might also result in this exception. For example, yang data requested, however json sent.

This exception is suggested to be logged; however, it is left up to the implementation if it is logged.

In the received rejected data, the post-condition is that the subscriber likely suspends the subscription. The subscription exists, but data cannot be sent.

See note 11.

| | -| Ends When |

This Use Case ends when either the Performance Event data has been successfully streamed, or one of the two Exception cases has been encountered: connection would not be established, or the receiver rejected the data.

| | -| Exceptions |

EXCEPTION: CONNECTION CANNOT BE ESTABLISHED – In this case, a persistent connection to the Subscriber endpoint did not exist and was attempted but could not be established (in the publisher-initiated case). Also, if a connection to the publisher endpoint could not be established (in the subscriber-initiated case).

EXCEPTION: RECEIVER REJECTED REQUEST – In this case, the Subscriber has indicated that it is rejecting the data.

| | -| Post-conditions |

SUCCESSFUL – If a connection did not already exist, A successful post condition is that a connection is successfully opened. Then, the performance has been streamed. The connection is kept open.

FAILURE – The use case may end with a post-condition where it encountered one of the two exceptions. If the connection was unable to be established, attempts to reopen the connection might be tried. In the receiver rejected data exception case, the post-condition is that the Subscriber likely suspends the job. The subscription exists, but data cannot be sent. See note 12.

| | -| Traceability |

REQ-ORC-O2-40, REQ-ORC-O2-41

| | -|

NOTE 1: Recovery from a failed attempt to open a connection is left to implementation.

| | | - -NOTE 2: It might be possible that the resource might be unavailable, and objects are deleted and data from the resource are not available. This would be incorporated into the data to be sent. - -NOTE 3: There are two alt series of steps: - -Alt 1 – steps 2.1, 2.2, and 2.3. This describes a publisher-initiated session connection. In this case, the Publisher opens a permanent connection to the Subscriber. - -Alt 2 – steps 3.1, 3.2, and 3.3. This describes a subscriber-initiated session connection. In this case, the Subscriber opens a permanent connection to the Publisher. - -NOTE 4: Only one of the Alt series of steps will be used in any given cloud implementation. They are both equivalently viable options. - -NOTE 5: An alternative pattern would be that the upon evaluation of the subscription, a session would be established immediately before any data is needed to be sent. This would be left up to implementation. - -NOTE 6: It is expected that most IMS implementations would log a fault. This exception is suggested to be logged; however, it is left up to the implementation if it is logged. - -NOTE 7: A dead subscription endpoint might be encountered. In this case, a retry interval might be specified; after which it will attempt to reopen a connection. A configuration for a set number of attempts might also be used. However, it is left up to implementation for a specific solution. - -NOTE 8: The protocol that opens the connection should have a means whereby the Publisher (IMS) can assess that a connection could not be established. - -NOTE 9: It is expected that most FOCOM implementations would log a fault. This exception is suggested to be logged; however, it is left up to the implementation if it is logged. - -NOTE 10: The protocol that opens the connection should have a means whereby the Subscriber (FOCOM) can assess that a connection could not be established. - -NOTE 11: This is left to implementation. - -NOTE 12: This is left to implementation. - -#### 3.8.4.3 UML Sequence Diagram for WebSocket Based Streaming - -![UML Sequence Diagram for Performance Management Streaming Notification Reporting Use Case. Lifelines: Service Management & Orchestration Framework (Subscriber) with FOCOM, and O-Cloud Platform (Publisher) with IMS. The diagram shows the interaction for streaming performance data via WebSocket, including connection establishment (alternatives for publisher-initiated and subscriber-initiated), data sending, and handling of successful or rejected data.](8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg) - -``` - -sequenceDiagram - participant FOCOM as Service Management & Orchestration Framework (Subscriber) - participant IMS as O-Cloud Platform (Publisher) - - Note right of IMS: Precondition: IMS has connectivity to SMO -PM Job(s) running - - Note over FOCOM, IMS: Performance Management Streaming Notification Reporting Use Case - - Note right of IMS: Performance Subscription Manager (PSM) -determines what and when to send data - - IMS->>IMS: 1.1 identifies data - IMS->>IMS: 1.2 retrieves PM Data - - Note right of FOCOM: If no existing connection to the subscriber exists yet - - rect rgb(255, 255, 255) - Note over FOCOM, IMS: alt [Alt 1 Publisher initiated session to connect to Subscriber Endpoint] - IMS->>FOCOM: 2.1 Open Connection - FOCOM-->>IMS: 2.2 Open Connection (Success) - Note over FOCOM, IMS: [Exception: Cannot open connection or connection was lost] - FOCOM-->>IMS: 2.3 Connection cannot be established - Note right of FOCOM: Failure Case - Note right of FOCOM: Use Case Ends - end - - rect rgb(255, 255, 255) - Note over FOCOM, IMS: alt [Alt 2 Subscriber initiates session to connect to Publisher Endpoint] - FOCOM->>IMS: 3.1 Open Connection - IMS-->>FOCOM: 3.2 Open Connection (Success) - Note over FOCOM, IMS: [Exception: Cannot open connection or connection was lost] - IMS-->>FOCOM: 3.3 Connection cannot be established - Note right of FOCOM: Failure Case - Note right of FOCOM: Use Case Ends - end - - IMS->>FOCOM: 4 Send Performance data - - rect rgb(255, 255, 255) - Note over FOCOM, IMS: alt [Performance Data Send Successful] - FOCOM-->>IMS: 5 Performance Data Received - Note over FOCOM, IMS: [Exception: Receiver rejected data] - IMS-->>FOCOM: 6 Receiver Rejected data - end - - Note over FOCOM, IMS: End Performance Management Streaming Notification Reporting Use Case - -``` - -UML Sequence Diagram for Performance Management Streaming Notification Reporting Use Case. Lifelines: Service Management & Orchestration Framework (Subscriber) with FOCOM, and O-Cloud Platform (Publisher) with IMS. The diagram shows the interaction for streaming performance data via WebSocket, including connection establishment (alternatives for publisher-initiated and subscriber-initiated), data sending, and handling of successful or rejected data. - -Figure 3-45: Performance Measurement Streaming Reporting for WebSocket Based Streaming - -#### 3.8.4.4 Sequence Description for Message Bus Based Streaming - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Performance Measurement Streaming Reporting Use Case | | -| Goal |

This Use Case describes Performance Measurement Streaming Reporting Using Message Bus Based Streaming. Performance Measurement data is sent periodically or triggered as specified by the subscription filter for ,active sessions based on message bus.

This use case has the following goals:

  • - If a session is not already established, then open a session to report streaming performance data. See Note 1.
  • - Send a series of performance measurement data through the opened session based on the subscription filter.
| | -| Actors and Roles |

SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer of performance measurement data.

IMS – The IMS within the O-Cloud is used to represent any publisher of the performance measurement data.

| | -| Assumptions |

SUBSCRIPTION EXISTS – It is assumed that performance management subscription has been established.

SERIALIZATION FORMAT, COMPRESSION ALGORITHM AGREED – It is assumed that the data model, serialization format and compression algorithm to be used for streaming the performance data have been agreed between Subscriber and Publisher.

STREAMING METHOD – It is assumed that the streaming mechanism and transport protocol/framework to be used have been agreed between Subscriber and Publisher

PM JOBS – It is also assumed that the Performance Measurement (PM) Job create use case has successfully completed.

| | -| Preconditions |

CONNECTIVITY – The Subscriber has connectivity to the Publisher.

AUTHENTICATION – The Publisher has user credentials for the Subscriber's end point.

PM JOB(S) ACTIVE – PM Job(s) are running and actively collecting performance measurement data.

Consumer and Producer are aware of stream framework e.g. Message bus

| | -| Begins when | This use case begins when the subscriber initiates a streaming session. | | -| Step 1.1 (M) | DATA TO BE SENT – The Performance Subscription Manager (PSM) based on the subscription(s) determines that performance data needs to be sent, and the subscription filter indicates that data should be sent with a performance measurement streaming reporting. | | -| Step 1.2 (M) | RETRIEVE DATA – The PSM retrieves the performance data from the local storage. The performance data is written by the PM Job(s) within the O-Cloud. The data is composed to be ready to be sent. See Notes 2,3,4 and 5. | | - -| | | | -|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 2.1 (ALT) |

SUBSCRIBER INITIATED SESSION ESTABLISHMENT

OPEN SESSION– If FOCOM does not already have a session established with the Publisher (IMS), then FOCOM attempts to establish streaming session to start the dataflow between Subscriber and Publisher.

| | -| Step 2.2 (ALT) |

SUBSCRIBER INITIATED SESSION ESTABLISHMENT

SESSION TO ENDPOINT SUCCESSFUL – The session to the subscription endpoint is established successfully, and a success response is given to the Subscriber (FOCOM).

| | -| Step 2.3 (ALT) |

SUBSCRIBER INITIATED SESSION ESTABLISHMENT

EXCEPTION: SESSION CANNOT BE ESTABLISHED – A session could not be established to the Publisher endpoint.

In this case, the use case ends. See note 6.

| | -| Step 3 |

SEND PERFORMANCE STREAM – A session has been successfully established, between the Publisher and Subscriber.

The IMS sends performance data in a performance stream using transport protocol based on message bus

EXCEPTION: DATA DELIVERY FAILS – In this case, the data has failed to be transferred from the publisher to subscriber

Handle the failure within message bus implementation

| | -| Ends When | This Use Case ends when either the Performance data has been successfully streamed or when one of the exceptions below has been encountered. | | -| Exceptions |

EXCEPTION: SESSION CANNOT BE ESTABLISHED – In this case, a session to the publisher endpoint could not be established (in the subscriber-initiated case).

EXCEPTION: CONFIGURATIONS CANNOT BE APPLIED – In this case, the Publisher has failed to apply the configuration.

| | -| Post-conditions | The session is kept open, and the configurations will continue to apply, and performance data streaming continue. | | -| Traceability | REQ-ORC-O2-40, REQ-ORC-O2-41 | | -|

NOTE 1: Recovery from a failed attempt to open a session is left to implementation.

NOTE 2: It might be possible that the resource might be unavailable, and objects are deleted and data from the resource are not available. This would be incorporated into the data to be sent.

NOTE 3: There are alt series of steps:

Alt – steps 2.1, 2.2, and 2.3. This describes a subscriber-initiated session establishment. In this case, the Subscriber opens a permanent session to the publisher.

NOTE 4: Only one of the Alt series of steps will be used in any given cloud implementation. They are both equivalently viable options.

| | | - -NOTE 5: An alternative pattern would be that the upon evaluation of the subscription, a session would be established immediately before any data is needed to be sent. This would be left up to implementation. - -NOTE 6: It is expected that most IMS implementations would log a fault. This exception is suggested to be logged; however, it is left up to the implementation if it is logged. - -#### 3.8.4.5 UML Sequence Diagram for Message Bus Based Streaming - -![UML Sequence Diagram for Performance Measurement Streaming Reporting Use Case. Lifelines: Service Management & Orchestration Framework (Subscriber) with FOCOM, and O-Cloud Platform (Publisher) with IMS. The diagram shows the interaction for streaming performance data via a message bus.](6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg) - -The sequence diagram illustrates the interaction between the Service Management & Orchestration Framework (Subscriber) and the O-Cloud Platform (Publisher) for performance measurement streaming reporting. The lifelines are FOCOM (Subscriber) and IMS (Publisher). - -**Precondition:** IMS has connectivity to SMO, PM Job(s) running, Consumer and Producer are aware of streaming framework e.g Kafka. - -**Performance Measurement Streaming Reporting Use Case:** - -- The IMS performs internal steps: PSM 1.1 identifies data and PSM 1.2 retrieves PM Data. A note indicates that the Performance Subscription Manager (PSM) determines what and when to send data. -- An **alt** block titled "[Subscriber initiated session to connect to Publisher Endpoint]" is entered if no sessions exist yet. - - 2.1 Establish streaming session for data flow (FOCOM to IMS) - - 2.2 Session established (Success) (IMS to FOCOM) - - Exception: Cannot establish session or session was lost** leads to a **Failure Case**: 2.3 Session cannot be established (IMS to FOCOM). -- A **loop** block titled "3 Send performance data using transport protocol based on message bus" is entered. - - 3 Send performance data using transport protocol based on message bus (IMS to FOCOM) - - Exception: Data delivery fails** leads to a note: Handle the failure within message bus implementation. - -The sequence concludes with the **End Performance Measurement Streaming Reporting Use Case**. - -UML Sequence Diagram for Performance Measurement Streaming Reporting Use Case. Lifelines: Service Management & Orchestration Framework (Subscriber) with FOCOM, and O-Cloud Platform (Publisher) with IMS. The diagram shows the interaction for streaming performance data via a message bus. - -Figure 3-46: Performance Measurement Streaming Reporting for Message Bus Based Streaming - -### 3.8.5 Performance Measurement File Reporting Use Case - -#### 3.8.5.1 High Level Description - -In the context of O-RAN Cloud managed systems, performance measurements can be transmitted by one of three Report delivery mechanisms: active collection by a consumer (event based notification), active push by a producer (e.g. streaming-based reporting), and/or file-based reporting. - -The SMO is expected to support all three of the above Report delivery mechanisms. However, any given IMS (O-Cloud) implementation may not support all three. - -Performance Measurement File Reporting has two paradigms: - -**Pull Paradigm** - If a consumer wants to retrieve Performance Data file(s), the *callback* attribute is given in the Performance Subscription Create operation. When the Performance Data file(s) are ready, the *callback* is used by the producer as the endpoint where the *File Ready* notification is sent to inform the consumer that the Performance Data file(s) are ready to be pulled from the O-Cloud. - -**Push Paradigm** - In addition to the *callback* attribute, the consumer will also provide a *Remote File Location* attribute in the Performance Subscription Create operation that the producer can upload the Performance Data file(s) to. Here, the *callback* is the endpoint where the *File Ready* notification is sent to inform the consumer that the Performance Data file(s) have been uploaded to the requested location. What happens to the file(s) after the producer sends the Performance Data file(s) to the remote file location is implementation specific. - -#### 3.8.5.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <> Related Use | -|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Use Case Title | Performance Measurement File Reporting Use Case | | -| Goal |

This Use Case describes Performance Measurement File Reporting. Performance Measurement data is sent periodically or triggered as specified by the subscription filter.

Performance Measurement File reporting has goals based on the two different file reporting cases:

  • - PUSH Paradigm – In this case, the goal is for the Performance Subscription Manager (PSM) within the IMS to send the Performance Data file(s) to the requested location and then notify the consumer that the Performance Data file(s) are available.
  • - PULL Paradigm – In this case, the goal is for the SMO to eventually retrieve the Performance Data file(s) from the O-Cloud. This is done after a File Ready notification is sent to the subscriber, typically the SMO, that the Performance Data file(s) are available.
| | -| Actors and Roles |

SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer of Performance Data file(s) containing performance measurement data.

IMS – The IMS within the O-Cloud orchestrates the preparation of the Performance Data file(s) and notifying the SMO that the Performance Data file(s) are available.

| | -| Assumptions |

FILE FORMATING – The IMS formats the performance data in files that are compliant to the O-RAN WG6 O-CLOUD-IM [23]. The formatting is not specified in the present document version.

FILE SIZE – The payload size of the performance measurement file is not specified in the present document version.

| | -| Preconditions |

CONNECTIVITY – The SMO (FOCOM) has connectivity to the IMS.

AUTHENTICATION – The IMS has user credentials for the SMO (FOCOM) end point.

PM JOB(S) ACTIVE – PM Job(s) are running and actively collecting performance measurement data.

SUBSCRIPTION – A performance management subscription has been established. This applies for both the Push and Pull paradigms.

| | -| Begins when | The use case begins when the subscription filter at the IMS determines that performance data should be made available to a consumer in a file-based format. | | -| Step 1 (M) | DATA TO BE SENT – Based on the subscription filter the Performance Subscription Manager (PSM) determines that performance data needs to be reported using performance measurement file reporting. | | - -| | | | -|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 2 (M) | RETRIEVE DATA – The PSM retrieves the performance data from the local storage. The performance data is written by the PM Job(s) within the O-Cloud. The data is composed into Performance Data file(s). See note 1. | | -| Step 3.1 (ALT) | PUSH PARADIGM – The Performance Data file(s) are uploaded to the remote location requested by the consumer. | | -| Step 3.2 (ALT) | PULL PARADIGM – The Performance Data file(s) are stored. | | -| Step 4 (M) | OPEN CONNECTION – The producer (IMS) opens a connection to the consumer (FOCOM). The producer opens a connection to a consumer endpoint based on the subscription(s). The consumer, or subscriber, is typically the SMO but could be some other entity. | | -| Step 5.1 (ALT) | CONNECTION TO ENDPOINT SUCCESSFUL – The connection to the consumer (subscription) endpoint was opened successfully, and a success response is given to the producer (publisher, IMS). | | -| Step 5.2 (ALT) | EXCEPTION: CONNECTION CANNOT BE ESTABLISHED – A connection could not be established to the consumer endpoint. See notes 2, 3, and 4. | | -| Step 6 (M) | SEND FILE READY NOTIFICATION – The producer (IMS) sends a File Ready notification to the consumer (FOCOM) over the O2 interface. This indicates that the requested Performance Data file(s) are available.

See notes 5 and 6. | | -| Step 7.1 (ALT 1) | PULL PARADIGM

RETRIEVE PERFORMANCE DATA FILE – The consumer (FOCOM) retrieves the Performance Data file(s) from the endpoint given by the producer (IMS). | | -| Step 7.2 (ALT 1) | PULL PARADIGM

PERFORMANCE DATA FILE RECEIVED – An acknowledgement is sent from the consumer (FOCOM) to the producer (IMS) that the Performance Data file(s) have been successfully received. | | -| Step 7.3 (ALT 1) | PULL PARADIGM

EXCEPTION: INVALID FORMAT – In this exception case, the Performance Data file(s) are not following the proper data format. This might result in the improper conversion of the Performance Data. For example , yang data requested, however json sent.

This exception is suggested to be logged; however, it is left up to the implementation if it is logged.

If this exception is encountered, the use case ends. | | -| Step 8 (ALT 2) | PUSH PARADIGM

What happens to the Performance Data file(s) after the consumer is notified that the file(s) are available is implementation specific. | | - -| | | | -|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Ends When |

This Use Case ends when a File Ready notification is sent to the consumer (Push Paradigm) and when the Performance Data file(s) have been successfully retrieved by the consumer (Pull Paradigm).

The Use Case may end with if one of the two Exception cases have been encountered: connection would not be established, or an invalid format.

| | -| Exceptions |

EXCEPTION: CONNECTION CANNOT BE ESTABLISHED – In this case, a connection between the consumer and producer could not be established. Specific implementations may log this fault and reattempt to open the connection. If this exception is encountered, the use case ends.

EXCEPTION: INVALID FORMAT – In this exception case, the Performance Data file(s) are not following the proper data format. If this exception is encountered, the use case ends.

| | -| Post-conditions |

SUCCESSFUL – In a successful post condition, a connection is successfully opened. The producer (IMS) sends a File Ready notification to the consumer (FOCOM) over the O2 interface. In case of the Pull Paradigm, the consumer has retrieved the Performance Data file(s).

FAILURE – The use case may end with a post-condition where it encountered one of the two exceptions. If the connection was unable to be established, attempts to reopen the connection might be tried based on implementation. In the receiver invalid format exception case, the post-condition is that the files were not sent, and the use case ends.

| | -| Traceability | REQ-ORC-O2-42, REQ-ORC-O2-43, REQ-ORC-O2-44 | | -|

NOTE 1: It might be possible that the resource might be unavailable, and objects are deleted and data from the resource are not available. This would be incorporated into the data to be sent. If the resource was out of service for the collection time period, the suspect flag might be raised in the PM data. If the PM job was deleted or gone, the counter would be listed in the deleted measures list so that it is still accounted for in the report by the PSM.

NOTE 2: It is expected and suggested that most IMS implementations would log a fault for this exception. However, it is left up to the implementation if it is logged. If this exception is encountered, the use case ends.

NOTE 3: A dead consumer endpoint might be encountered. In this case, a retry interval might be specified; after which it will attempt to reopen a connection. A configuration for a set number of attempts might also be used. However, it is left up to implementation for a specific implementation.

NOTE 4: The protocol that opens the connection should have a means whereby the producer (IMS) can assess that a connection could not be established.

NOTE 5: There are two alt series of steps:

  • ● Alt 1 – steps 7.1, 7.2, and 7.3. This describes the PULL Paradigm, where the consumer retrieves the file(s) from the O-Cloud after receiving a File Ready notification by the producer
  • ● Alt 2 – step 8. This describes the PUSH Paradigm, where the consumer actions after receiving a File Ready notification from the Producer are not specified.

NOTE 6: Only one of the Alt series of steps will be used in any given cloud implementation. They are both equivalently viable options.

| | | - -#### 3.8.5.3 UML Sequence Diagram - -![UML Sequence Diagram for Performance Measurement File Reporting Use Case. Lifelines: Service Management & Orchestration Framework (Subscriber) FOCOM and O-Cloud Platform (Publisher) IMS. The diagram shows the interaction for reporting performance measurement files, including preconditions, PSM identification, data retrieval, and push/pull paradigms.](f4e5a86da5c799372a7c1ea2397dedb7_img.jpg) - -``` - -sequenceDiagram - participant FOCOM as Service Management & Orchestration Framework (Subscriber) FOCOM - participant IMS as O-Cloud Platform (Publisher) IMS - - Note right of IMS: Precondition: IMS has connectivity to SMO -PM Job(s) running - - Note right of IMS: Performance Subscription Manager (PSM) -determines what and when to send data - - Note right of IMS: PSM 1 identifies data - Note right of IMS: PSM 2 retrieves PM Data - - alt Push Paradigm: Performance File is uploaded to Remote Location - alt Pull Paradigm: Performance File is stored - - Note left of FOCOM: 4 Open Connection - alt Connect to Subscriber Endpoint Result: Success - alt Exception: Cannot open connection or connection was lost: Failure Case - Note right of IMS: Use Case Ends - - Note left of FOCOM: 6 Send File Ready notification - - alt PULL Paradigm: Retrieve Performance Data File - alt Success: Performance Data File received - alt Exception: Invalid format: Failure Case - alt PUSH Paradigm: What happens once consumer is notified is not part of this Use Case - Note right of IMS: Use Case Ends - - Note right of IMS: End Performance Measurement File Reporting Use Case - -``` - -The sequence diagram illustrates the interaction between the Service Management & Orchestration Framework (Subscriber) FOCOM and the O-Cloud Platform (Publisher) IMS for the Performance Measurement File Reporting Use Case. The process begins with a precondition that IMS has connectivity to SMO and PM Job(s) running. The IMS's Performance Subscription Manager (PSM) identifies data (PSM 1) and retrieves PM Data (PSM 2). An 'alt' block for the Push Paradigm shows the performance file being uploaded to a remote location, while the Pull Paradigm shows it being stored. Step 4 involves opening a connection from FOCOM. An 'alt' block for connecting to the subscriber endpoint shows a success case (5.1) and a failure case (5.2) if the connection cannot be established, ending the use case. Step 6 is a 'Send File Ready' notification from IMS to FOCOM. A 'PULL Paradigm' block involves retrieving the performance data file (7.1), receiving it (7.2) in a success case, or handling an invalid format (7.3) in a failure case. A 'PUSH Paradigm' block notes that subsequent consumer notification is outside the use case scope. The use case ends after these steps. - -UML Sequence Diagram for Performance Measurement File Reporting Use Case. Lifelines: Service Management & Orchestration Framework (Subscriber) FOCOM and O-Cloud Platform (Publisher) IMS. The diagram shows the interaction for reporting performance measurement files, including preconditions, PSM identification, data retrieval, and push/pull paradigms. - -Figure 3-47: Performance Measurement File Reporting - -### 3.8.6 Performance Measurement Job Query Use Case - -#### 3.8.6.1 High Level Description - -PM Jobs collect performance data on O-Cloud infrastructure resources. Preinstalled Performance Measurement Jobs (PM Jobs) are started on O-Cloud genesis. Additionally, PM Jobs can be created through a request from a consumer (see the PM Job Creation use case). - -This use case describes a flow where a consumer can query for PM Jobs in the O-Cloud. - -In the query request, a consumer can specify a query filter for the state of a PM Job(s) of interest. Supported PM Job states include active, suspended, and deprecated defined as follows: - -**ACTIVE STATE** – A PM Job that has been created and is currently running is defined to be in the *Active* state. - -**SUSPENDED STATE** – A PM Job that has been created, and through a request to stop measurement collection is defined to be in the *suspended state*. See the PM Job Suspend use case for more details [NOTE: for future addition]. - -**DEPRECATED STATE** – As a result of a PM job deletion request, the PM job is defined to be in the *deprecated* state. See the PM Job Delete use case (3.8.7). - -#### 3.8.6.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Performance Measurement Job (PM Job) Query Use Case | | -| Goal |

The goal of the PM Job Query Use Case is to provide a consumer information about PM Jobs based on the request query filter.

This includes the following goals to allow a consumer to perform:

  • PM Job Query requests with a query filter for PM Job IDs, PM Job status, and PM Job states.
  • PM Job Query for all active PM Jobs including Preinstalled PM Jobs.
  • PM Job Query for specific PM Jobs indicated with specific IDs in the query filter.
  • PM Job Queries for PM Jobs in the Suspended State.
  • PM Job Queries for PM Jobs in the Deprecated State as a result of delete operations that have not yet been purged.
| | -| Actors and Roles |

O-Cloud Operator – The O-Cloud Operator is a consumer (or entity) using or interfacing with the SMO (FOCOM).

SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer of the PM Job Query information.

IMS – The IMS within the O-Cloud is used to represent any provider of the PM Job Query information.

| | -| Assumptions | There are no assumptions. | | -| Preconditions |

Connectivity – The producer has end-to-end connectivity to the consumer.

O-Cloud Operational & Registered – The O-Cloud is installed, operating, and registered with the SMO.

| | - -| | | | -|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Begins when | This Use Case begins when a consumer initiates a PM Job Query operation. | | -| Step 1 (M) |

PM Job Query Request –

A PM Job Query Request is initiated by the O-Cloud Operator towards the consumer (FOCOM/SMO). The PM Job Query contains a filter that specifies the PM Jobs that the operator is interested in. The PM Job Query filter criteria include but are not limited to PM Job owner, PM Job IDs, PM Job state (e.g., suspended, active, deprecated).

| | -| Step 2 (M) |

PM Job Query Request –

The PM Job Query request with its attendant criteria is passed from the SMO to the IMS.

Privilege – The connection authentication is verified by the IMS. The consumer identification and privileges are verified for the requestor to be able to perform the PM Job Query operation.

| | -| Step 3 (ALT) |

ALT Successful Query –

The IMS authenticates the connection. The IMS processes the PM Job Query operation.

If the PM Job Query was successful, the producer (IMS) passes to the consumer (FOCOM/SMO) the results matching the PM Job query criteria over the O2 IMS interface.

NOTE: It is possible to formulate a PM Job Query that has nothing matching the criteria; for example, a query for all suspended PM Jobs might be requested; and if there were no suspended PM Jobs, the successful Query would return an empty payload back.

| | -| Step 4 (ALT) |

ALT EXCEPTION: Query of a Non-Existent PM Job –

This exception is encountered when a PM Job Query is performed with a query filter that requests for a non-existent PM Job. This is a case where the query criteria returned no matching PM Jobs.

The Use Case ends.

| | -| Step 5 (ALT) |

ALT EXCEPTION: Unexpected Condition –

A response is sent to the requesting entity from the SMO, that the IMS encountered an unexpected condition processing the request.

The Use Case ends.

| | -| Ends when | This use case ends when the query on PM Job has successfully been accomplished, or one of the two exception cases have been encountered. | | -| Exceptions |

Query of a Non-Existent PM Job – This exception is encountered when a PM Job Query criteria results in a non-existent PM Job.

Unexpected Condition – This exception occurs when an unexpected condition encountered.

| | -| Post-conditions |

Success – The requested (list) of PM Job(s) and their corresponding IDs, state & status matching the PM Job Query request filter are returned to the requestor or consumer.

Failure – The request was not able to be completed. No other “clean up” needs to occur. An exception notification has been issued.

| | - -| | | | -|--------------|----------------------------------|--| -| Traceability | [REQ-ORC-O2-56], [REQ-ORC-O2-57] | | -|--------------|----------------------------------|--| - -#### 3.8.6.3 UML Sequence Diagram - -![UML Sequence Diagram for PM Job Query. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), O-Cloud Platform (IMS). The sequence starts with a 1 PM Job Query Request from the operator to FOCOM, which then sends a 2 PM Job Query Request to IMS. IMS verifies authentication and processes the query. An 'alt' block titled 'IMS Performance Measurement Job Query Use Case' handles the response: 'Successful Query' returns 3 PM Job Query State & Status (Success); 'Exception: Query of a non-existent PM Jobs' returns 4 PM Job Query Not Found; 'Exception: Unexpected Condition' returns 5 Unexpected Condition. FOCOM then sends a 6 PM Job Query Status to the operator. The sequence ends with 'Performance Measurement Job Query End Use Case'.](d3253d5db64378db6e72b66b41067a5b_img.jpg) - -``` - -sequenceDiagram - actor Operator as O-Cloud Operator - participant FOCOM as Service Management & Orchestration Framework (FOCOM) - participant IMS as O-Cloud Platform (IMS) - - Note right of FOCOM: Preconditions: -SMO (consumer) has connectivity to (producer) O-Cloud O2ims endpoint -O-Cloud has registered its IMS with the SMO - - Note over FOCOM, IMS: IMS Performance Measurement Job Query Use Case - - Operator->>FOCOM: 1 PM Job Query Request - FOCOM->>IMS: 2 PM Job Query Request - Note right of IMS: Connection authentication is verified - Note right of IMS: Query operation is processed - - alt Successful Query: 3 PM Job Query State & Status (Success) - Note right of FOCOM: [Exception: Query of a non-existent PM Jobs] - Note right of FOCOM: Failure Case: 4 PM Job Query Not Found - Note right of FOCOM: [Exception: Unexpected Condition] - Note right of FOCOM: Failure Case: 5 Unexpected Condition - - FOCOM-->>Operator: 6 PM Job Query Status - - Note over FOCOM, IMS: Performance Measurement Job Query End Use Case - -``` - -UML Sequence Diagram for PM Job Query. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), O-Cloud Platform (IMS). The sequence starts with a 1 PM Job Query Request from the operator to FOCOM, which then sends a 2 PM Job Query Request to IMS. IMS verifies authentication and processes the query. An 'alt' block titled 'IMS Performance Measurement Job Query Use Case' handles the response: 'Successful Query' returns 3 PM Job Query State & Status (Success); 'Exception: Query of a non-existent PM Jobs' returns 4 PM Job Query Not Found; 'Exception: Unexpected Condition' returns 5 Unexpected Condition. FOCOM then sends a 6 PM Job Query Status to the operator. The sequence ends with 'Performance Measurement Job Query End Use Case'. - -Figure 3-48: PM Job Query - -### 3.8.7 Performance Measurement Job Delete Use Case - -#### 3.8.7.1 High Level Description - -PM Jobs collect performance data on O-Cloud infrastructure resources. Preinstalled Performance Measurement Jobs (PM Jobs) are started on O-Cloud genesis. Additionally, PM Jobs can be created through a request from a consumer (see the PM Job Creation use case). - -This use case describes a flow where a consumer requests for PM Job(s) to be deleted. A consumer can specify the PM Job(s) to be deleted by the associated PM Job Identifiers (IDs) which can be obtained through a PM Job query or PM Job create. - -**DEPRECATED STATE** – As a result of a PM Job deletion request, the PM Job(s) go into the *deprecated* state. Deprecated PM Job(s) records are held for a retention period after which they are purged from the system. It is expected that the retention period can be configured. PM Job(s) stay in the deprecated state until they are purged; thus, PM Job(s) cannot be “resurrected” once they are in the deprecated state. - -**SUSPEND BEFORE DELETE** – Only suspended PM Jobs can be deleted. A consumer or owner needs to first suspend the PM Job(s) before they can be deleted. Preinstalled PM Jobs cannot be suspended by a typical consumer request. See the PM Job suspend use case for more details [NOTE 1: use case to be added in future]. - -**PREINSTALLED PM JOBS** – Preinstalled PM Jobs are unlike normal PM Jobs. Rather, Preinstalled PM Jobs may be deleted by IMS software update, or by privilege settings. - -**PM JOB OWNERSHIP** – It is expected that a PM Job has one owner though it might have more than one consumer. A User (Operator or Entity) has a Role, and that Role has Privilege/Permissions associated with. Thus, the role may have the permissions to affect the state or delete a PM Job. Preinstalled PM Jobs also have owners. NOTE 2: Security considerations and analysis from the O-RAN Security Requirements specification [18] is FFS. - -**NOTIFICATION AFTER DELETION** – The PM Job deletion operation may affect subscriber(s) that were getting data from the deleted PM Job(s). One of the consequences of this use case is that the subscriber(s) are notified if they had been subscribing to data collected by those PM Job(s) that were deleted. They choose to subscribe to job change notification, or they may take action after getting a report that indicates that those affected measurements were deleted. - -NOTE 3: A O-Cloud Operator may wish to minimize the computational overhead within the O-Cloud and thus may delete lower priority PM Job(s). - -#### 3.8.7.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | PM Job Delete Use Case (O2 IMS) | | -| Goal |

The goal of the PM Job Delete Use Case is to enable a consumer or entity to delete existing PM Job(s).

This includes the following goals to allow a consumer to perform:

As a result of a PM Job Deletion request, the PM Job(s) go into the deprecated state.

A check that the requested PM job(s) are in the suspended state is performed before the PM Job deletion request is started.

PM Job Delete operation can request for specific PM Job(s) with their corresponding PM Job ID(s) to be deleted.

| | -| Actors and Roles |

O-Cloud Operator – The O-Cloud Operator is a consumer (or entity) using or interfacing with the SMO (FOCOM).

SMO (FOCOM) – The FOCOM within the SMO is the actor who issues the PM Job delete request over the O2imsinterface.

IMS – The IMS within the O-Cloud processes the PM Job Delete request and receives the request over the O2imsinterface.

| | -| Assumptions | There are no assumptions. | | -| Preconditions |

Connectivity – The producer has end-to-end connectivity to the consumer.

O-Cloud Operational & Registered – The O-Cloud is installed, operating, and registered with the SMO.

| | -| Begins when | This use case begins with either: | | - -| | | | -|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

Operator Request – This use case begins when a O-Cloud Operator requests for a PM Job delete.

Autonomously Triggered – When the SMO autonomously determines that PM Job(s) need to be deleted.

| | -| Step 1 (ALT) |

PM Job Delete Request (Operator Initiated) (ALT) –

A PM Job Delete Request is initiated by the O-Cloud Operator towards the consumer (FOCOM/SMO). The PM Job Delete request identifies the PM Job(s) that the operator wants to delete.

Privilege – The connection authentication is verified by the IMS. The consumer identification and privileges are verified for the requestor to be able to perform the PM Job Delete operation.

NOTE 1: It is possible to delete a PM Job(s) in the deprecated state. This would return a success; however, it would not result in any action being taken.

| | -| Step 2 (ALT) |

PM Job Delete Request (Autonomously Initiated) (ALT) –

The PM Job Delete request is initiated autonomously from the SMO. The SMO has some trigger which initiates a PM Job Delete request for PM Job(s) to be deleted.

| | -| Step 3 (M) |

PM Job Delete Request –

The PM Job Delete request is sent from the SMO to the IMS.

The following are the actions that the IMS does to process the PM job delete request for the specified PM Job(s) to be deleted:

The IMS performs a check that the PM Job(s) to be deleted are in the suspended state.

NOTE 2: it is expected that the SMO uses PM Job identifier to identify the PM job activity to be cleaned up for the PM Jobs to be deleted.

If the PM Job has an embedded subscription, the PM Job deletion operation causes the associated PM subscription to be automatically deleted.

| | -| Step 4 (ALT) |

PM Job Delete Response (Success) –

The PM Job Delete returns an asynchronous response for the successful case.

| | -| Step 5 (ALT) |

PM Job State Change Notification

The requestor is informed through a state change notification event of the state and status of the PM Job(s) that were deleted with the request.

| | -| Step 6 (ALT) |

ALT EXCEPTION: Delete of non-suspended PM Job(s) –

This exception occurs when a PM Job delete requests for the deletion of non-suspended PM Job(s). A response is sent to the requesting entity (SMO), that the deletion request for PM Job(s) not in a suspended state is an exception case.

The IMS will include the PM Job ID and consumer subscription ID for the PM Job in the response and notification of the PM Job(s) deleted.

The Use Case ends in this exception case.

NOTE 3: The PM Job(s) need to be first placed in suspended mode so that PM jobs are not accidentally mass deleted since the operation cannot be reversed once it is processed. See requirement [REQ-ORC-O2-60]

| | - -| | | | -|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 7 (ALT) |

ALT EXCEPTION: Delete of non-existent PM Job(s) –

This exception occurs when a PM Job Delete requests for the deletion of non-existent PM Job(s). The request will not be able to be processed because the PM Job(s) does not exist. A response is sent to the requesting entity (SMO), that a request for the deletion of a non-existent PM Job is invalid.

The Use Case ends when this exception case is encountered.

NOTE 4: A request for a PM Job delete, that had been deprecated (previously deleted) and then subsequently purged, would result in this exception.

| | -| Step 8 (ALT) |

ALT EXCEPTION: Unexpected Condition –

A response is sent to the requesting entity from the SMO, that the IMS encountered an unexpected condition processing the request.

The Use Case ends.

| | -| Step 9 (M) |

Request Response –

The PM Job Delete Status is given from the consumer SMO (FOCOM) to the O-Cloud Operator.

| | -| Ends when |

This use case ends when the PM Job Delete operation has successfully been accomplished, or one of the exception cases have been encountered.

| | -| Exceptions |

Delete of non-suspended PM Job(s) – This exception is encountered when a PM Job Delete requests for the deletion of non-suspended PM Job(s).

Delete of non-existent PM Job(s) – This exception is encountered when a PM Job Delete requests for the deletion of non-existent PM Job(s).

Unexpected Condition – This exception occurs when an unexpected condition encountered.

| | -| Post-conditions |

Success – The requested (list) of PM Job(s) matching the PM Job Delete request are returned to the requestor or consumer.

Failure – The request was not able to be completed. No other “clean up” needs to occur.

| | -| Traceability |

[REQ-ORC-O2-58], [REQ-ORC-O2-59], [REQ-ORC-O2-60], [REQ-ORC-O2-84]

| | - -#### 3.8.7.3 UML Sequence Diagram - -![UML Sequence Diagram for PM Job Delete. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The sequence starts with preconditions: SMO has connectivity to O2ims endpoint and IMS is registered. The 'IMS Performance Measurement Job Delete Use Case' begins. An 'alt' block '[Operator Initiate PM Job Delete]' contains a '1 PM Job Delete Request' from Operator to FOCOM. A subsequent 'alt' block '[SMO Autonomous PM Job Delete]' contains a '2 PM Job Delete Request' from FOCOM to itself, followed by a '3 <> PM Job Delete Request' from FOCOM to IMS. IMS performs internal steps: 'Connection authentication is verified', 'Check that PM Job(s) to be deleted are suspended', and 'Delete operation is processed'. An 'alt' block '[Successful Delete]' contains '4 <> PM Job Delete Response (Success)' and '5 <> PM Job State Change Notification (Success)' from IMS to FOCOM. Two 'Exception' blocks follow: '[Exception: Delete of non-suspended PM Job(s)]' with 'Failure Case' 6, and '[Exception: Delete of non-existent PM Job(s)]' with 'Failure Case' 7. A third 'Exception' block '[Exception: Unexpected Condition]' contains 'Failure Case' 8. Finally, a '9 PM Job Delete Response' is sent from FOCOM to Operator, and the 'Performance Measurement Job Delete End Use Case' concludes.](b0384c8e0ff826a8116ab2ff67dadc43_img.jpg) - -UML Sequence Diagram for PM Job Delete. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The sequence starts with preconditions: SMO has connectivity to O2ims endpoint and IMS is registered. The 'IMS Performance Measurement Job Delete Use Case' begins. An 'alt' block '[Operator Initiate PM Job Delete]' contains a '1 PM Job Delete Request' from Operator to FOCOM. A subsequent 'alt' block '[SMO Autonomous PM Job Delete]' contains a '2 PM Job Delete Request' from FOCOM to itself, followed by a '3 <> PM Job Delete Request' from FOCOM to IMS. IMS performs internal steps: 'Connection authentication is verified', 'Check that PM Job(s) to be deleted are suspended', and 'Delete operation is processed'. An 'alt' block '[Successful Delete]' contains '4 <> PM Job Delete Response (Success)' and '5 <> PM Job State Change Notification (Success)' from IMS to FOCOM. Two 'Exception' blocks follow: '[Exception: Delete of non-suspended PM Job(s)]' with 'Failure Case' 6, and '[Exception: Delete of non-existent PM Job(s)]' with 'Failure Case' 7. A third 'Exception' block '[Exception: Unexpected Condition]' contains 'Failure Case' 8. Finally, a '9 PM Job Delete Response' is sent from FOCOM to Operator, and the 'Performance Measurement Job Delete End Use Case' concludes. - -Figure 3-49: PM Job Delete - -### 3.8.8 Performance Measurement Job Update Use Case - -#### 3.8.8.1 High Level Description - -PM Jobs collect performance data on O-Cloud infrastructure resources. Preinstalled Performance Measurement Jobs (PM Jobs) are started on O-Cloud genesis. Additionally, PM Jobs can be created through a request from a consumer (see the PM Job Creation use case). - -This use case describes Performance Measurement Job (PM Job) updates that can occur from one of two reasons as described: - -**RESOURCE CHANGES** – Resource changes can cause PM Job(s) to update. PM Job(s) collect data from O-Cloud infrastructure resources. When O-Cloud resources are updated, added, or deleted that a PM Job depends on, the PM Job update use case may be invoked. Resources changes can impact the PM Job measure criteria which include the measured Resources, collected Measures, qualified Resource Types, and/or Resource scope criteria which may trigger a PM Job update. It is possible that the result of the evaluation may not alter the PM Job(s). - -**UPDATE BY REQUEST** – A consumer (operator or entity) may also request for an update to PM Job(s) through a request operation. A consumer may request for data collection updates for PM Job(s). For example, different data to be collected from O-Cloud infrastructure resources. This may occur autonomously from a consumer, for example through a policy trigger. Only a consumer with the proper permissions that own the PM Job(s) can update the PM Job. - -#### 3.8.8.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | PM Job Update Use Case (O2 IMS) | | -| Goal |

The goal of the PM Job Update Use Case is to enable a consumer or entity to update an existing PM Job information such as the new measured resources or collected measures.

As subordinate goals, the O-Cloud allows a consumer to perform these actions:

An update of the measure selection criteria which in turn updates the measured Resources, collected Measures, qualified Resource Types, measure selection criteria, and/or Resource scope criteria.

Adds, removes, or changes to the above types of things in the PM Job.

| | -| Actors and Roles |

O-Cloud Operator – The O-Cloud operator is a consumer (or entity) using or interfacing with the SMO (FOCOM).

SMO (FOCOM) – The FOCOM within the SMO is the actor who issues the PM Job Update request over the O2ims interface.

IMS – The IMS within the O-Cloud processes the PM Job Update request and receives the request over the O2ims interface.

| | -| Assumptions | There are no assumptions. | | -| Preconditions |

Connectivity – The producer (IMS) has end-to-end connectivity to the consumer (SMO/FOCOM).

O-Cloud Operational & Registered – The O-Cloud is installed, operating, and registered with the SMO.

| | -| Begins when |

This use case begins with either:

Operator Request – When an O-Cloud operator requests for an update to a PM Job.

Autonomously Triggered – When the SMO autonomously determines that a PM Job needs to be updated.

| | -| Step 1 (ALT) |

PM Job Update Request (Operator Initiated) (ALT) –

  • - A PM Job Update Request is initiated by the O-Cloud operator towards the consumer (FOCOM/SMO). The PM Job Update request identifies the PM Job(s) that the operator wants to update.
  • - The PM Job Update request contains parameters to update via the measure selection criteria. The measure selection criteria can change the measured Resources, collected Measures, qualified Resource Types, and/or Resource scope criteria which will be applied by the target PM Job. NOTE 1: the measure selection criteria are a read/write attributes whereas the others are read-only because updates to those aspects occur through the measure selection criteria.
| | - -| | | | -|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

The PM Job Update request may update different aspects of the PM Job and what it is collecting.

The PM Job Update operation can only be applied to active and suspended PM Jobs. The PM Job Update operation is rejected for deprecated PM Jobs.

NOTE 2: Different PM Jobs may have different permissions based on the role of the requestor.

| | -| Step 2 (ALT) |

PM Job Update Request (Autonomously Initiated) (ALT) –

The PM Job Update request is initiated autonomously from the SMO. The SMO has some trigger which initiates a PM Job Update request for a PM Job to be updated.

The SMO may update measured Resources, collected Measures, qualified Resource Types, measure selection criteria, and/or Resource scope criteria for the target PM Job through the PM Job Update request.

| | -| Step 3 (M) |

PM Job Update Request –

The PM Job Update request is sent from the SMO to the IMS.

| | -| Step 4 (M) |

IMS Processes PM Job Update Request –

The IMS performs the following actions to process the PM Job Update Request:

Existence – The IMS checks that the affected PM Job exists.

Permissions – The IMS checks the ownership for the PM Job against the permissions (role) of the requestor. A PM Job has one owner. The role has the permissions to update a PM Job. A user (operator or entity) has permissions based on their role.

Request Parameters – The IMS processes the parameters in the request which indicate how the PM Job should be updated. These potentially include updates to the measured Resources, collected Measures, qualified Resource Types, measure selection criteria, and/or Resource scope criteria.

| | -| Step 5 (ALT) |

PM Job Update Response (Success) –

The PM Job Update returns an asynchronous response for the successful case.

| | -| Step 6 (ALT) |

PM Job Update Notification (Success) –

Other consumers/subscribers are informed about PM Job Updates to the PM Job(s) that they are subscribing to.

| | -| Step 7 (ALT) |

ALT EXCEPTION: Update request for non-existent PM Job –

This exception occurs when a PM Job Update requests for the update of a non-existent PM Job. The request will not be able to be processed because the PM Job does not exist. A response is sent to the requesting entity (SMO), that a request for the update of a non-existent PM Job is invalid.

The Use Case ends when this exception case is encountered.

| | -| Step 8 (ALT) |

ALT EXCEPTION: Unexpected Condition –

A response is sent to the requesting entity from the SMO, that the IMS encountered an unexpected condition processing the request.

The Use Case ends when this exception case is encountered.

| | -| Step 9 (M) |

UPDATE RESPONSE

| | - -| | | | -|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | The PM Job Update Response is given from the consumer SMO (FOCOM) to the O-Cloud Operator | | -| Ends when | This use case ends when the PM Job Update operation has successfully been accomplished, or one of the exception cases have been encountered. | | -| Exceptions | Update of non-existent PM Job – This exception is encountered when a PM Job Update requests for the update of a non-existent PM Job.
Unexpected Condition – This exception occurs when an unexpected condition is encountered. | | -| Post-conditions | Success – On a successful PM Job Update operation, the requestor gets a response to their request which includes the result of the operation.
Failure – The request was not able to be completed. No other “clean up” for this use case needs to occur within the O-Cloud or IMS. The requestor gets a response to their request indicates the failure. | | -| Traceability | [REQ-ORC-02-66], [REQ-ORC-02-67], [REQ-ORC-02-68] | | - -#### 3.8.8.3 UML Sequence Diagram - -![UML Sequence Diagram for PM Job Update. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The diagram shows the interaction for the 'IMS Performance Measurement Job Update Use Case'. It includes an 'alt' block for 'Operator Initiated PM Job Update' and 'SMO Autonomous PM Job Update'. The process involves sending a request, processing it (checking existence, ownership, and parameters), and returning a response or handling exceptions (non-existent job or unexpected condition).](6059b0a3a051cc20b414d51a4e412f3e_img.jpg) - -**Preconditions:** -SMO (consumer) has connectivity to (producer) O-Cloud O2ims endpoint -O-Cloud has registered its IMS with the SMO - -**IMS Performance Measurement Job Update Use Case** - -**alt** [Operator Initiated PM Job Update] -1 PM Job Update request - -[SMO Autonomous PM Job Update] -2 PM Job Update trigger - -3 «O2ims» PM Job Update request - -4 Update operation is processed -Update operation is processed: -Check that PM Job exists -Check ownership & permissions -Evaluate request parameters - -**alt** [Successful Update] -5 «O2ims» PM Job Update response -6 «O2ims» PM Job Update Notification - -[Exception: Update of a non-existent PM Job] -Failure Case 7 «O2ims» PM Job Not Found -Use Case Ends - -[Exception: Unexpected Condition] -Failure Case 8 «O2ims» Unexpected Condition -Use Case Ends - -9 PM Job Update response - -**Performance Measurement Job Update End Use Case** - -UML Sequence Diagram for PM Job Update. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The diagram shows the interaction for the 'IMS Performance Measurement Job Update Use Case'. It includes an 'alt' block for 'Operator Initiated PM Job Update' and 'SMO Autonomous PM Job Update'. The process involves sending a request, processing it (checking existence, ownership, and parameters), and returning a response or handling exceptions (non-existent job or unexpected condition). - -Figure 3-50: PM Job Update - -### 3.8.9 Performance Measurement Job Suspend Use Case - -#### 3.8.9.1 High Level Description - -PM Jobs collect performance data on O-Cloud infrastructure resources. Preinstalled Performance Measurement Jobs (PM Jobs) are started on O-Cloud genesis. Additionally, PM Jobs can be created through a request from a consumer (see the PM Job Creation use case). - -This use case describes a flow where a Performance Measurement Job (PM jobs) is suspended. Suspending a PM Job might be done to improve system performance because PM Jobs come at the cost of system overhead and computational cycles. Suspending a PM Job will cause it to be inactive when its report timer is triggered where it would normally collect data. - -**DORMANCY PERIODS** – PM Job(s) can be suspended for a specified time period (dormancy period). A consumer may specify when PM Job(s) can be returned to normal operation. The request can either specify a dormancy filter or suspend the PM Job indefinitely (“PM Job Stop”). PM Jobs indefinitely suspended need a consumer request to resume operations. See the PM Job Resume use case. - -**RELATION TO PM JOB DELETE OPERATION** – Only suspended PM Jobs can be deleted. A consumer or owner first suspends PM Job(s) before they can be deleted. Preinstalled PM Jobs cannot be suspended by a typical consumer request. See the PM Job delete use case for more details. - -**PM JOB OWNERSHIP** – It is expected that a PM Job has one owner, though it might have more than one consumer. The role has the permissions to suspend a PM Job. A User (Operator or Entity) has a Role, and that Role has Privilege/Permissions associated with. Thus, a user (operator or entity) has permissions based on their role. Preinstalled PM Jobs also have owners. Relationship to the Security specification is FFS. - -#### 3.8.9.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | PM Job Suspend Use Case (O2 IMS) | | -| Goal |

The goal of the PM Job Suspend Use Case is to enable a consumer (SMO) or entity to request to suspend existing PM Job. PM Job Suspend operation can request for a specific PM Job with their corresponding PM Job ID to be suspended.

As a result of a PM Job Suspend request goal, the requested PM Job transitions into the suspend state.

| | -| Actors and Roles |

O-Cloud Operator – The O-Cloud operator is a consumer (or entity) using or interfacing with the SMO (FOCOM).

SMO (FOCOM) – The FOCOM within the SMO is the actor who issues the PM Job Suspend request over the O2ims interface.

IMS – The IMS within the O-Cloud processes the PM Job Suspend request and receives the request over the O2ims interface.

| | -| Assumptions | There are no assumptions. | | -| Preconditions |

Connectivity – The producer (IMS) has end-to-end connectivity to the consumer (SMO/FOCOM).

O-Cloud Operational & Registered – The O-Cloud is installed, operating, and registered its IMS with the SMO.

| | -| Begins when |

This use case begins with either:

Operator Request – When an O-Cloud operator requests for a PM Job to be suspended.

Autonomously Triggered – When the SMO autonomously determines that a PM Job needs to be suspended.

| | -| Step 1 (ALT) |

PM Job Suspend request (Operator Initiated) (ALT) –

A PM Job Suspend request is initiated by the O-Cloud operator towards the consumer (FOCOM/SMO). The PM Job Suspend request identifies the PM Job that the operator wants to suspend. The request contains the dormancy period and dormancy filter.

| | - -| | | | -|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

Privilege – The connection authentication is verified by the IMS. The consumer identification and privileges are verified for the requestor to be able to perform the PM Job Suspend operation.

NOTE 1: It is possible to suspend a PM Job already in the suspend state. This operation would return a success; however, it would not result in any action being taken.

| | -| Step 2 (ALT) |

PM Job Suspend request (Autonomously Initiated) (ALT) –

The PM Job Suspend request is initiated autonomously from the SMO. The SMO has some trigger which initiates a PM Job Suspend request for a PM Job to be suspended.

| | -| Step 3 (M) |

PM Job Suspend request –

The PM Job Suspend request is sent from the SMO to the IMS.

| | -| Step 4 (M) |

IMS Processes PM Job Suspend request –

The IMS performs the following actions to process the PM Job Suspend Request:

Existence – The IMS checks that the requested PM Job exists.

Permissions – The IMS checks the ownership for the PM Job against the permissions (role) of the requestor.

NOTE 2: PM Job(s) have one owner. The role has the permissions to suspend a PM Job. A user (operator or entity) has permissions based on their role.

Dormancy – The IMS evaluates the request filter and dormancy periods. The request can specify a PM Job to be suspended for a specified time (dormancy period). The request might suspend a PM Job indefinitely (“PM Job Stop”).

| | -| Step 5 (M) |

PM Job Suspend response (Success) –

The PM Job Suspend returns an asynchronous response in the successful case.

| | -| Step 6 (M) |

State Change Notification (Success) –

The requestor is informed through a state change notification event of the state and status of the PM Job. This is sent because the state and status of the affected PM Job transition to the suspend due to a successful PM Job Suspend operation.

| | -| Step 7 (ALT) |

ALT EXCEPTION: PM Job Suspend request for non-existent PM Job –

This exception occurs when a PM Job Suspend requests for the suspend of a non-existent PM Job. The request will not be able to be processed because the PM Job does not exist. A response is sent to the requesting entity (SMO), that a request for the suspension of a non-existent PM Job is invalid.

The Use Case ends when this exception case is encountered.

| | -| Step 8 (ALT) |

ALT EXCEPTION: Unexpected Condition –

A response is sent to the requesting entity from the IMS, that the IMS encountered an unexpected condition processing the request.

The Use Case ends.

| | -| Ends when |

This use case ends when the PM Job Suspend operation has successfully been accomplished, or one of the exception cases have been encountered.

| | - -| | | | -|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Exceptions |

Suspend of non-existent PM Job(s) – This exception is encountered when a PM Job Suspend requests to suspend a non-existent PM Job(s).

Unexpected Condition – This exception occurs when an unexpected condition encountered.

| | -| Post-conditions |

Success – On a successful PM Job Suspend operation, the requestor gets a response to their request which includes the results of the operation. Additionally, subscribed consumer(s) get a state change notification of PM Job(s) in the Suspend state.

Failure – The request was not able to be completed. No other “clean up” needs to occur. The requestor gets a response of the failure.

| | -| Traceability | [REQ-ORC-02-69], [REQ-ORC-02-70] | | - -#### 3.8.9.3 UML Sequence Diagram - -![UML Sequence Diagram for IMS Performance Measurement Job Suspend Use Case. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The diagram shows the interaction for suspending a PM job, including preconditions, operator-initiated and autonomous paths, and success/exception handling.](ffe2d3e622dd30bea4caf15951c60e42_img.jpg) - -**Sequence Diagram: IMS Performance Measurement Job Suspend Use Case** - -**Lifelines:** Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), O-Cloud Platform (IMS) - -**Preconditions:** - SMO (consumer) has connectivity to (producer) O-Cloud O2ims endpoint - O-Cloud has registered its IMS with the SMO - -**Sequence of Messages:** - -- alt: [Operator Initiated PM Job Suspend]** - 1 PM Job Suspend request (Operator → FOCOM) -- alt: [SMO Autonomous PM Job Suspend]** - 2 PM Job Suspend trigger (FOCOM → FOCOM) -- 3 «O2ims» PM Job Suspend request (FOCOM → IMS) -- 4 Suspend operation is processed (IMS → IMS) - Note: Suspend operation is processed: - Check that PM Job(s) exist - Check ownership & permissions - Evaluate request filter & dormancy -- alt: [Successful PM Job Suspend operation]** - 5 «O2ims» PM Job Suspend response (IMS → FOCOM) - 6 «O2ims» PM Job State Change Notification [Suspend] (Success) (IMS → FOCOM) -- alt: [Exception: Suspend of non-existent PM Job(s)]** - Failure Case: 7 «O2ims» PM Job(s) Not Found (IMS → FOCOM) - Use Case Ends -- alt: [Exception: Unexpected Condition]** - Failure Case: 8 «O2ims» Unexpected Condition (IMS → FOCOM) - Use Case Ends -- 9 PM Job Suspend Response (FOCOM → Operator) - -**Performance Measurement Job Suspend End Use Case** - -UML Sequence Diagram for IMS Performance Measurement Job Suspend Use Case. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The diagram shows the interaction for suspending a PM job, including preconditions, operator-initiated and autonomous paths, and success/exception handling. - -Figure 3-51: PM Job Suspend - -### 3.8.10 Performance Measurement Job Resume Use Case - -#### 3.8.10.1 High Level Description - -PM Jobs collect performance data on O-Cloud infrastructure resources. Preinstalled Performance Measurement Jobs (PM Jobs) are started on O-Cloud genesis. Additionally, PM Jobs can be created through a request from a consumer (see the PM Job Creation use case). - -This use case describes resuming one Performance Measurement Job (PM Job) that has previously been suspended. See the PM Job Suspend Use case for more details. - -**RESUMING OPERATIONS** – PM Job(s) in the *suspend* state have had their measurement collection activity halted. The PM Job Resume operation will request that the PM Job start operations again. The PM Job will transition to the *active* state. The PM Job will begin measurement collection at their next scheduled collection interval period. The PM Job will continue to collect measurements based on their criteria. To change the interval times or collection behavior, a PM Job update would need to be performed. - -**PM JOB OWNERSHIP** – It is expected that a PM Job has one owner, though it might have more than one consumer. The role has the permissions to resume a PM Job. A User (Operator or Entity) has a Role, and that Role has Privilege/Permissions associated with. Thus, a user (operator or entity) has permissions based on their role. Preinstalled PM Jobs also have owners. Relationship to the Security specification is FFS. - -#### 3.8.10.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | PM Job Resume Use Case (O2 IMS) | | -| Goal |

The goal of the PM Job Resume Use Case is to enable a consumer (SMO) or entity to request to resume a previously suspended PM Job. The PM Job Resume operation can be requested for a specified PM Job with its corresponding PM Job ID to be resumed.

As result of a PM Job Resume request, the requested PM Job transitions into the active state. Successfully resumed PM Job will start collecting data adding to any existing data sets with a time period and collection filter set for the PM Job including measured Resources, qualified Resource Types, collected Measures, and measure selection criteria.

The PM Job Resume request is a single request to resume one (atomic) PM Job.

| | -| Actors and Roles |

O-Cloud Operator – The O-Cloud operator is a consumer (or entity) using or interfacing with the SMO (FOCOM).

SMO (FOCOM) – The FOCOM within the SMO is the actor who issues the PM Job Resume request over the O2ims interface.

IMS – The IMS within the O-Cloud processes the PM Job Resume request and receives the request over the O2ims interface.

| | -| Assumptions | There are no assumptions. | | -| Preconditions | Connectivity – The producer (IMS) has end-to-end connectivity to the consumer (SMO/FOCOM). | | - -| | | | -|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | O-Cloud Operational & Registered – The O-Cloud is installed, operating, and registered its IMS with the SMO. | | -| Begins when | This use case begins with either:
Operator Request – When an O-Cloud operator requests for a PM Job Resume operation.
Autonomously Triggered – When the SMO autonomously determines that a PM Job needs to be resumed. | | -| Step 1 (ALT) | PM JOB RESUME REQUEST (Operator Initiated) (ALT) –
A PM Job Resume request is initiated by the O-Cloud operator towards the consumer (FOCOM/SMO). The PM Job Resume request specifies the PM Job that the operator wants to resume.
NOTE 1: Different PM Jobs may have different permissions based on the role of the requestor. Thus, some resume requests may be rejected while others are applied.
NOTE 2: It is possible that the requested PM Job is already in the active state. This operation would return a success; however, it would not result in any action being taken. | | -| Step 2 (ALT) | PM JOB RESUME REQUEST (Autonomously Initiated) (ALT) –
The PM Job Resume request is initiated autonomously from the SMO. In this case, the SMO has a trigger which initiates a PM Job Resume request for a PM Job to be resumed. | | -| Step 3 (M) | PM JOB RESUME REQUEST –
The PM Job Resume request is sent from the SMO to the IMS. | | -| Step 4 (M) | IMS PROCESSES PM JOB RESUME REQUEST –
The IMS performs the following actions to process the PM Job Resume request:
PM Job in Suspended State – The IMS checks that the requested PM Job is in suspended state. Reactivating the suspended PM Job transitioning to the active state and counters populated into the PM table.
Deprecated State – The IMS checks that the requested PM Job is not in the deprecated state. The resume of a deprecated PM Job would fail with an appropriate error code.
Active State – This would be an idempotent case. The operation would succeed, as the PM job is already in the outcome state.
Permissions – The IMS checks the ownership for the PM Job against the permissions (role) of the requestor. PM Jobs have one owner. The role has the permissions to resume a PM Job. A user (operator or entity) has permissions based on their role. | | -| Step 5 (ALT) | PM JOB RESUME RESPONSE (Success) –
The PM Job Resume returns an asynchronous response for the successful case. | | -| Step 6 (ALT) | STATE CHANGE NOTIFICATION (Success) –
The requestor and subscribed consumer(s) are informed through a state change notification event of the state and status of the PM Job. This is sent because the state and status of the affected PM Job transition to the active state due to a successful PM Job Resume operation. | | - -| | | | -|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 7 (ALT) |

ALT EXCEPTION: PM JOB RESUME REQUEST FOR A NON-EXISTENT PM JOB –

This exception occurs when a PM Job Resume requests for the resume of a non-existent PM Job. The request will not be able to be processed because the PM Job does not exist. A response is sent to the requesting entity (SMO), that a request for the resumption of the PM Job is invalid.

The Use Case ends when this exception case is encountered.

| | -| Step 8 (ALT) |

ALT EXCEPTION: PM JOB RESUME REQUEST FOR A DEPRECATED PM JOB

This exception occurs when a PM Job Resume requests for the resume of a deprecated PM Job. The request will not be able to be processed because the PM Job is in the deprecated state. A response is sent to the requesting entity (SMO), that a request for the resume of the deprecated PM Job is invalid.

The Use Case ends when this exception case is encountered.

| | -| Step 9 (ALT) |

ALT EXCEPTION: UNEXPECTED CONDITION –

A response is sent to the requesting entity from the SMO, that the IMS encountered an unexpected condition processing the request.

The Use Case ends when this exception case is encountered.

| | -| Step 10 (M) |

PM JOB RESUME RESPONSE

The PM Job Update Response is given from the SMO (FOCOM) to the O-Cloud Operator.

| | -| Ends when |

This use case ends when the PM Job Resume operation has successfully been accomplished, or one of the exception cases have been encountered.

| | -| Exceptions |

Resume of non-existent PM Job – This exception is encountered when a PM Job Resume requests to resume anon-existent PM Job.

Resume of a Deprecated PM Job – This exception occurs when a PM Job Resume requests to resume a PM Job in the Deprecated state.

Unexpected Condition – This exception occurs when an unexpected condition is encountered.

| | -| Post-conditions |

Success – On a successful PM Job Resume operation, the requestor gets a response to their request which includes the result of the operation. Additionally, subscribed consumer(s) get a state change notification of PM Job in the active state.

Failure – The request was not able to be completed. No other “clean up” for this use case needs to occur within the O-Cloud or IMS. The requestor gets a response of the failure.

| | -| Traceability |

[REQ-ORC-02-71], [REQ-ORC-02-72]

| | - -#### 3.8.10.3 UML Sequence Diagram - -![UML Sequence Diagram for PM Job Resume. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The diagram shows the interaction for resuming a performance measurement job, including preconditions, operator-initiated and SMO-autonomous resume paths, and various success and exception handling cases.](e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg) - -**Preconditions:** -SMO (consumer) has connectivity to (producer) O-Cloud O2ims endpoint -O-Cloud has registered its IMS with the SMO - -**IMS Performance Measurement Job Resume Use Case** - -**alt: [Operator Initiated PM Job Resume]** -1 PM Job Resume request (Operator to FOCOM) - -**alt: [SMO Autonomous PM Job Resume]** -2 PM Job Resume trigger (FOCOM to FOCOM) - -3 «O2ims» PM Job Resume request (FOCOM to IMS) -4 Resume operation is processed (IMS to IMS) - -**Resume operation is processed:** -Check that PM Job(s) exist -Check PM Job(s) are not deprecated -Check ownership & permissions -Resume PM Job(s) - -**alt: [Successful Resume]** -5 «O2ims» PM Job Resume response (IMS to FOCOM) -6 «O2ims» PM Job State Change Notification [Active state](Success) (IMS to FOCOM) - -**[Exception: Resume of non-existent PM Job(s)]** -Failure Case: 7 «O2ims» PM Job(s) Not Found (IMS to FOCOM) -Use Case Ends - -**[Exception: Resume of deprecated PM Job(s)]** -Failure Case: 8 «O2ims» PM Job(s) are deprecated (IMS to FOCOM) -Use Case Ends - -**[Exception: Unexpected Condition]** -Failure Case: 9 «O2ims» Unexpected Condition (IMS to FOCOM) -Use Case Ends - -10 PM Job Resume response (FOCOM to Operator) - -**End Performance Measurement Job Resume Use Case** - -UML Sequence Diagram for PM Job Resume. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (IMS). The diagram shows the interaction for resuming a performance measurement job, including preconditions, operator-initiated and SMO-autonomous resume paths, and various success and exception handling cases. - -Figure 3-52: PM Job Resume - -### 3.8.11 Performance Management Dictionary Discovery IMS Use Case - -#### 3.8.11.1 High Level Description - -When a new O-Cloud Resource Type is discovered in the O-Cloud infrastructure either on O-Cloud genesis or during run-time, the IMS would inform FOCOM (SMO) about that new Resource Type so that the appropriate corresponding Performance Management Dictionary can be identified. - -NOTE: every version of Resource has its own Resource Type and thus a Performance Management Dictionary associated with it. - -It is expected that the SMO would have already onboarded the associated Resource Type before it is discovered by the O-Cloud infrastructure, as described in O2 IMS Specification [17]. The four situations where a Performance Management dictionary could be discovered are: - -- a) **RESOURCE SOFTWARE UPDATE** – A software update of a Resource creates a new Resource Type with its attendant Performance Management Dictionary in inventory. Existing resources can either remain pointing to the existing Resource Type or be software updated to the newly loaded Resource Type. Each Resource Type has its own unique Performance Management dictionary associated with it at the SMO. -- b) **QUERY & SYNCHRONIZATION** – A query service may also result in the discovery of new Resource Types in the O-Cloud infrastructure. Additionally, the initial synchronization of the model between the O-Cloud and management system (SMO) may result in the discovery of Resource Types to be managed. -- c) **NEW RESOURCES ADDED** – New objects have been added to the O-Cloud infrastructure. Subsequently, new Resource Types corresponding to those new objects may be added which then may result in an Infrastructure Inventory Event being generated to a consumer (FOCOM/SMO) or subscriber. -- d) **IMS LIFE CYCLE SOFTWARE UPDATE** – When the software of the O-Cloud is updated new Resource Types can be discovered. The updated IMS software could come with new Resource types including their Performance Management Dictionaries. - -There are two possible ways the IMS gets the Performance Management Dictionary (PM Dictionary). The first is that SMO might update the IMS with the Performance Management Dictionary. The second method is for the IMS to get the Performance Management Dictionary from the O-Cloud Resource (or external proxy for the resource). See the Resource Type Onboarding LCM Use Case for more details. The source of truth is in the cloud for O-Cloud Resource Types. - -#### 3.8.11.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Performance Management (PM) Dictionary Discovery (IMS) | | -| Goal |

The primary goal of this use case is where the consumer (SMO) adds a Performance Management Dictionary corresponding to a new discovered Resource Type in the O-Cloud infrastructure.

A consequence is that the consumer (SMO) has a corresponding Performance Management Dictionary that corresponds to every Resource Type that would emit Performance Measures. The triggers for this use case revolve around insuring that consistency.

| | -| Actors and Roles |

O-Cloud Operator – The O-Cloud Operator is a consumer (or entity) using or interfacing with the SMO (FOCOM).

SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer of this use case.

IMS – The IMS within the O-Cloud is used to represent any provider of the responses to the use case triggers.

| | -| Assumptions | No Assumptions | | -| Preconditions |

Connectivity – The producer has connectivity to the consumer by some mechanism. The mechanism by which the subscriber achieves connectivity to the publisher is out of the scope of this Use Case.

O-Cloud Operational & Registered – The O-Cloud is installed, operating, and registered with the SMO.

Privilege – The consumer identification and privileges have been verified to be able to perform O2 operations.

| | - -| | | | -|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

Performance Management Dictionaries Onboarded – Performance Management Dictionary(ies) are onboarded with the Resource Type definition(s) into the O-Cloud Infrastructure Inventory. This is performed by software in the O-Cloud that manages Resource Types.

| | -| Begins when |

There are four triggers that invokes this Use Case:

Software update of an O-Cloud Resource – When software is updated for an O-Cloud Infrastructure Resource(s), a new Resource Type might be discovered which will trigger this use case.

New Resources deployed – When new Resources are deployed to the O-Cloud Infrastructure, it may cause new Resource Types to be discovered which would subsequently trigger this use case.

Query Infrastructure Inventory – A Query Infrastructure Inventory for a Resource Type triggers this use case. One place this occurs is in O-Cloud Registration & Initialization during O-Cloud genesis, the consumer performs a Query Infrastructure Inventory. The consumer then gets the Performance Management Dictionaries for all the Resource Types discovered during genesis. See the O-Cloud Registration & Initialization use case.

IMS Life Cycle Software Update – When the software of the O-Cloud is updated new Resource Types can be discovered which will trigger this use case.

| | -| Step 1 (M) |

RESOURCE TYPE RECORD CREATED (causes Performance Management Dictionary to be onboarded)

When a new Resource Type record is created during O-Cloud onboarding a Performance Management Dictionary corresponding to that Resource Type is onboarded within the O-Cloud (see pre-conditions).

These triggers cause a new Resource Type record to be created:

Software update of an O-Cloud Resource – When software is updated for an O-Cloud Resource(s), a new Resource Type is created.

IMS Life Cycle Software Update – When the software of the O-Cloud is updated new Resource Types record is created.

New Resources deployed – When new Resources are deployed to the O-Cloud Infrastructure, it may cause new Resource Type to be created.

These two triggers would cause a new Resource Type record to be discovered by SMO:

Query Infrastructure Inventory – A Query Infrastructure Inventory for a Resource Type is discovered for a previously created Resource Type record.

Infrastructure Inventory Notification – A Infrastructure Inventory Notification from the O-Cloud to the subscriber, the IMS will send a copy of the Resource Type record.

| | -| Step 2 (ALT) |

O-CLOUD INFRASTRUCTURE INVENTORY EVENT NOTIFICATION (Alt) –

The IMS sends an O-Cloud Infrastructure Inventory Event Notification over O2ims interface to the consumer, FOCOM/SMO, if a subscription already exists. This notification is sent if Step 1 triggers the creation of new Resource Type(s) or discovers new Resource Type(s). The O-Cloud Infrastructure Inventory Event Notification communicates the Resource Type(s) information.

NOTE 1: For the definition of the InfrastructureInventoryEventNotification see Reference [17].

| | -| Step 3 (ALT) |

QUERY O-CLOUD INFO REQUEST –

| | - -| | | | -|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | The consumer, FOCOM/SMO, can send a request to Query the O-Cloud for inventory information. This request will result in the SMO discovering new Resource Type(s). | | -| Step 4 (ALT) | QUERY O-CLOUD INFO RESPONSE –

The producer, IMS, processes the Query request and returns any new Resource Types that have been discovered for a previously created Resource Type record.

NOTE 2: Upon receipt, the consumer, SMO, is expected to associate the new Performance Management Dictionary/Dictionaries with the newly discovered Resource Type(s). The Resource Type object contains the Performance Management Dictionary associate with the Resource ID or vendor make & model data.

NOTE 3: The IMS might get the Performance Management Dictionary from the O-Cloud Resource and sent it to the SMO.

| | -| Step 5 (M) | PERFORMANCE Management DICTIONARY ASSOCIATED -

It is expected that the consumer, SMO, will associate the Performance Management Dictionar(ies) for the new Resource Type(s) sent by the IMS or it already has the proper Performance Management Dictionar(ies).

NOTE 4: The consumer, SMO, will likely aggregate all the Performance Management Dictionaries across the O-Clouds that it has purview to. This is implementation specific.

NOTE 5: (error case) If a Resource Type collects Performance metrics, then there is a Performance Management Dictionary, but it was not loaded (due to error), for this use case, the IMS will indicate there is no dictionary for this Resource Type. If later, a Performance metric is sent for that resource instance with a missing Performance Management Dictionary, a consumer, SMO, will have to debug and potentially attempt to reload the Performance Management Dictionary post facto.

| | -| Ends when | This use case ends when the consumer has associated new Performance Management Dictionar(ies) to newly create or discovered Resource Type(s). | | -| Exceptions | None | | -| Post-conditions | Success – Upon successful completion of the use case, the consumer, SMO, associates the proper Performance Management Dictionar(ies) to newly discovered or created Resource Type(s).
Failure – No failure cases | | -| Traceability | [REQ-ORC-O2-52], [REQ-ORC-O2-53] | | - -#### 3.8.11.3 UML Sequence Diagram - -![UML Sequence Diagram for PM Dictionary Discovery. Lifelines: Personnel (Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS).](27c9c38b326b85de631d54a9ff1e2bd4_img.jpg) - -``` - -sequenceDiagram - participant CO as Personnel (Cloud Operator) - participant SMO as Service Management & Orchestration Framework (Subscriber) (FOCOM) - participant IMS as O-Cloud Platform (Publisher) (IMS) - - Note over SMO: PRECONDITIONS: -SMO has connectivity to O-Cloud -O-Cloud has registered its IMS with the SMO -The identification & privileges of a SMO user has been verified -Performance Management Dictionaries onboarded for the Resource Type - - rect rgb(240, 240, 240) - Note over CO, IMS: Performance Management Dictionary Discovery Use Case - end - - Note over SMO: TRIGGER CONDITION: -(1) Software update of O-Cloud Resource -or- -(2) LCM objects of new Resource deployed to O-Cloud -or- -(3) Resynchronization of inventory between SMO & IMS -or- -(4) IMS Life Cycle Software Update -Result: new O-Cloud Resource Types added - - Note right of IMS: 1 New Resource Type record is created - Note right of IMS: Software update and LCM onboarding occurs (q.v. other use cases) - - alt Subscription exists for new Resource Types - IMS->>SMO: 2 <> O-Cloud Infrastructure Inventory Event Notification - else Query / Polling for Inventory Changes - SMO->>IMS: 3 <> Query O-Cloud Info Request (Success) - IMS-->>SMO: 4 <> Query O-Cloud Info Response (Success) - end - - SMO->>CO: 5 Performance Management Dictionary associated for new Resource Types - - rect rgb(240, 240, 240) - Note over CO, IMS: End Performance Management Dictionary Discovery Use Case - end - -``` - -UML Sequence Diagram for PM Dictionary Discovery. Lifelines: Personnel (Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). - -Figure 3-53: PM Dictionary Discovery - -### 3.8.12 Performance Management Subscription Query (IMS) Use Case - -#### 3.8.12.1 High Level Description - -This use case details the management of Performance Management Subscriptions; in particular, the query service operation. The query of a Performance Management Subscription is the ability of an authorized entity to get the details of a Performance Management Subscription including its performance subscription filter. - -The create, update, and delete of a Performance Management Subscription is documented in the other Performance Management Subscription use cases. This use case only concerns the query of a Performance Management Subscription. - -**NOTE:** The query-response paradigm and CRUD paradigm (Read in this case) are synonymous in terms of this use case. That is, Query (cf. query-response) and Read (cf. CRUD operations) are synonymous in for this use case. - -The performance framework is described in the O2 GA&P [9]. The Performance Management Subscription filter defines the following things (among others) for collecting and reporting Performance Measurements over O2ims: - -- The subscription filter qualifies what data from the Performance Measurement jobs should be sent. -- The subscription filter indicates the collection timing interval. -- The subscription filter specifies the Report delivery mechanisms (event notification reporting, stream-based reporting, file-based reporting). -- The query filter could include the *Consumer Performance Subscription Identifier(s)*. - -An entity performing the query would usually be the SMO; however, it could also be another authorized user, technician, or machine (e.g. software, script, etc.). Typically, an entity would perform a subscription query to cross-check their Performance Management Subscription. Though, it could also be utilized for other management purposes as well. - -Performance Management Subscription describes a subscription mechanism dedicated to getting reports for Performance Measurements. The Performance Management Subscription is not used since we have dedicated subscriptions for measurements specifically. - -#### 3.8.12.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Performance Management Subscription Query | | -| Goal | An entity (typically the SMO), desires to query the Performance Management Subscription(s) from the IMS. (NOTE 1) (NOTE 2) (NOTE 3) (NOTE 4) | | -| Actors and Roles | O-Cloud Operator – The O-Cloud operator is a user that is interested in getting Performance subscription query results.
SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer of the Performance Management Subscription query service.
IMS – The IMS within the O-Cloud is used to represent any provider of the Performance Management Subscription status query service. | | -| Assumptions | There are no assumptions. | | -| Preconditions | Connectivity – The Subscriber has connectivity to the publisher by some mechanism. The mechanism by which the subscriber achieves connectivity to the publisher is out of the scope of this Use Case.
O-Cloud Operational – The O-Cloud is installed, operating, and registered with the SMO.
Privilege – The consumer identification and privileges of a SMO user have been verified to be able to perform O2 operations. | | -| Begins when | The use case begins when an operator at the SMO wishes to query the Performance Management Subscription(s). | | -| Step 1 (M) | PERFORMANCE SUBSCRIPTION QUERY REQUEST –
The O-Cloud operator initiates a query for Performance Management Subscription(s) with a query filter. | | -| Step 2 (M) | PERFORMANCE SUBSCRIPTION QUERY REQUEST –
The query Performance Management Subscription request is issued from FOCOM (SMO) to the publisher (IMS) with query filter. (NOTE 5) | | - -| | | | -|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | SUCCESSFUL PERFORMANCE SUBSCRIPTION QUERY – | | -| Step 3 (ALT) | A connection authentication is verified by the publisher (IMS). This is a standard type of check; and a standard response would be issued in this case. The query request operation is processed by the publisher. If the query request results in Performance Management Subscription(s) matching the query filter, then a success response is sent to FOCOM (SMO) in step 8. | | -| Step 4 (ALT) | EXCEPTION: QUERY OF NON-EXISTING PERFORMANCE SUBSCRIPTION – If the query operation results in no Performance Management Subscription that matches the query filter, then a Performance Management Subscription not found is issued back to the requestor.

For example, if no consumer subscription identifier(s) matches any Performance Subscription, this exception would be encountered. (NOTE 6) | | -| Step 5 (ALT) | EXCEPTION: QUERY OF NON-EXISTING PERFORMANCE SUBSCRIPTION RESPONSE –

If the query operation results in no Performance Management Subscriptions that match the query filter, then a “no existing Performance Management Subscriptions” response is issued from FOCOM to the O-Cloud Operator. This is a return/response for Step 1.

The Use Case ends here. | | -| Step 6 (ALT) | EXCEPTION: UNEXPECTED CONDITION –

The IMS might not be able to comply with the request. There might have been a software issue trying to process the Performance Management Subscription query request. | | -| Step 7 (ALT) | EXCEPTION: UNEXPECTED CONDITION –

The SMO (FOCOM) returns to the operator that there was an unexpected condition.

The Use Case ends here. | | -| Step 8 (M) | QUERY PERFORMANCE SUBSCRIPTION (SUCCESS) –

A successful Performance Management Subscription query operation will result in a success from FOCOM back to O-Cloud operator. This is a return/response for Step 1. | | -| Ends when | This Use Case ends under two cases:

EXCEPTION CASE – The use case ends when there an exception case is encountered. For example, when a requestor tries to perform a query operation where all of the requested Performance Management Subscriptions do not exist.

QUERY OPERATION SUCCEEDS – The use case will end if the query operation of Performance Management Subscription successfully completed. | | -| Exceptions | EXCEPTION CASE: NON-EXISTENT SUBSCRIPTION – None of the requested Performance Management Subscriptions exist in the query operation.

EXCEPTION CASE: UNEXPECTED CONDITION – The IMS might not be able to comply to the Performance Management Subscription query request. In this case, the unexpected condition exception is encountered. | | -| Post-conditions | Success: The Performance Management Subscription has been returned to the requestor (O-Cloud operator) | | - -| | | | -|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|--| -| | Failure: An exception notification of a non-existent Performance Management Subscription or Unexpected Condition has been issued. | | -| Traceability | [REQ-ORC-O2-85], [REQ-ORC-O2-86] | | -|

NOTE 1: Query (cf. query-response) and Read (cf. CRUD operations) are synonymous for this use case. This is the “R” in CRUD.

NOTE 2: An entity may be any authorized user or machine (e.g. software or script, etc.).

NOTE 3: This use case is one in a series of use cases related to Performance Management Subscription management (CRUD operations). The create, update, and delete Performance Management Subscription operations are described in other use cases.

NOTE 4: The IMS could have more than one Performance Management Subscription. This use case covers the query of one or multiple Performance Management Subscription(s).

NOTE 5: The query filter could include the Consumer Subscription Identifier(s).

NOTE 6: If a Performance Management Subscription Query has a mixture of valid and non-existing subscriptions, the operation will only return information about the content.

| | | - -#### 3.8.12.3 UML Sequence Diagram - -![UML Sequence Diagram for PM Subscription Query. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows the interaction for a Performance Management Subscription Query, including preconditions, a successful query path, and two exception paths (non-existent subscription and unexpected condition).](0d9149a10167a487a93c349f5d848b7d_img.jpg) - -``` - -sequenceDiagram - actor Personnel as O-Cloud Operator - participant FOCOM as Service Management & Orchestration Framework (Subscriber) - participant IMS as O-Cloud Platform (Publisher) - - Note right of FOCOM: PRECONDITIONS: -SMO has connectivity to O-Cloud -O-Cloud has registered its IMS with the SMO -The identification & privileges of a SMO user has been verified - - Note over FOCOM, IMS: Performance Management Subscription Query Use Case - - Personnel->>FOCOM: 1 Performance Management Subscription Query - Note right of FOCOM: Subscribers have consumer subscription identifier. - FOCOM->>IMS: 2 Performance Management Subscription Query - Note right of IMS: Connection authentication is verified -Subscription query operation is processed - alt Successful Query - IMS-->>FOCOM: 3 Performance Management Subscription Query Status (Success) - else Exception: Query of a non-existent Performance Subscription - IMS-->>FOCOM: 4 Performance Management Subscription not found - FOCOM-->>Personnel: 5 Performance Management Subscription not found - Note right of FOCOM: Use Case Ends - else Exception: Unexpected condition - IMS-->>FOCOM: 6 Unexpected condition - FOCOM-->>Personnel: 7 Unexpected condition - Note right of FOCOM: Use Case Ends - end - FOCOM-->>Personnel: 8 Performance Management Subscription Query Status (Success) - - Note over FOCOM, IMS: End Performance Management Subscription Query Use Case - -``` - -UML Sequence Diagram for PM Subscription Query. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows the interaction for a Performance Management Subscription Query, including preconditions, a successful query path, and two exception paths (non-existent subscription and unexpected condition). - -Figure 3-54: PM Subscription Query - -### 3.8.13 Performance Management Subscription Update (IMS) Use Case - -#### 3.8.13.1 High Level Description - -This use case describes the update of a Performance Management Subscription. ETSI GS NFV-SOL 003 [24] specifies the API to perform a PM Job update. The update of PM Job allows for the update of the subscription including the callback URIs for the notification of events of PM Jobs. - -The create, query, and delete of a Performance Management Subscription is documented in other Performance Management Subscription related use cases. The query-response paradigm and CRUD paradigm (update in this case) are synonymous in terms of this use case. This use case only concerns the update of a Performance Management Subscription. - -The Performance Management Subscription update allows for an entity to modify the subscription filter for notifications of interest by a consumer with an update order (see below). Because there is metadata related to the Performance Management Subscription it is meaningful to have an update operation. The Performance Management Subscription update would be able to change the following things: - -**Connection Information** – This describes the connection information which includes the Performance Subscription ID, the Report delivery mechanism, remote file location, and callback URI. - -**Resources, Resource Types** – The Performance Subscription Criteria are a part of the update order that describes the O-Cloud resources, or the O-Cloud resource types of interest. It details any resources that are of the specified type, and metrics of interest to be collected on. - -**Delivery Details** – This describes the delivery information including the measurement reporting frequencies, and whether redundant data should be suppressed. - -**Received Measures** – This describes the measures to be received to be reported. - -**PM Jobs** – The subscription update can alter the PM Jobs involved. - -NOTE: Some modifications concerning the Performance Management Subscription, such as callback URI, can also be performed by modifying/updating the underlying PM Jobs. - -An entity requesting for a subscription update would usually be the SMO; however, it could also be another authorized user, administrator, technician, or machine (e.g., software, script, etc.). Typically, an endpoint moved, or there are new URI endpoints. Only an entity with the proper permissions or authorization would be allowed to make a PM subscription update. - -#### 3.8.13.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------| -| Use Case Title | Performance Management Subscription Update | | -| Goal | An entity (typically the SMO), desires to update the Performance Management Subscription(s) from the IMS. (NOTEs 1, 2, 3 and 4) | 3.8.1 PM Job Creation Use Case | -| Actors and Roles | O-Cloud Operator – The O-Cloud operator is a user that is interested in updating Performance Management Subscription.
SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer of the Performance Management Subscription service. | | - -| | | | -|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | IMS – The IMS within the O-Cloud performs the Performance Management Subscription update operation. | | -| Assumptions | There are no assumptions. | | -| Preconditions | Connectivity – The Subscriber has connectivity to the publisher by some mechanism. The mechanism by which the subscriber achieves connectivity to the publisher is out of the scope of this Use Case.

O-Cloud Operational – The O-Cloud is installed, operating, and registered with the SMO.

Privilege – The consumer identification and privileges of a SMO user have been verified to be able to perform O2 operations. | | -| Begins when | The use case begins when an operator at the SMO wishes to update the Performance Management Subscription(s). | | -| Step 1 (M) | PERFORMANCE MANAGEMENT SUBSCRIPTION UPDATE REQUEST –

The O-Cloud operator initiates an update for Performance Management Subscription(s) with an update order. | | -| Step 2 (M) | PERFORMANCE MANAGEMENT SUBSCRIPTION UPDATE REQUEST –

The update Performance Management Subscription request is issued from FOCOM (SMO) to the publisher (IMS) with update order. | | -| Step 3 (ALT) | SUCCESSFUL PERFORMANCE MANAGEMENT SUBSCRIPTION UPDATE –

A connection authentication is verified by the publisher (IMS). This is a standard type of check; and a standard response would be issued in this case. The update request operation is processed by the publisher. If the update request results in Performance Management Subscription(s) matching the update order, then a success response is sent to FOCOM (SMO) in step 8. | | -| Step 4 (ALT) | EXCEPTION: UPDATE OF NON-EXISTING PERFORMANCE MANAGEMENT SUBSCRIPTION – If the update operation results in no Performance Management Subscription that matches the update order, then a Performance Management Subscription not found is issued back to the requestor.

For example, if a consumer subscription identifier does not match any Performance Management Subscription, this exception would be encountered. (NOTE 5) | | -| Step 5 (ALT) | EXCEPTION: UPDATE OF NON-EXISTING PERFORMANCE MANAGEMENT SUBSCRIPTION RESPONSE –

If the update operation results in no Performance Management Subscriptions that match the requested subscriptions to be updated, then a “no existing Performance Management Subscriptions” response is issued from FOCOM to the O-Cloud Operator. This is a return/response for Step 1.

The Use Case ends here. | | - -| | | | -|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 6 (ALT) | EXCEPTION: UNEXPECTED CONDITION –
The IMS might not be able to perform the necessary updates according to the request. There might have been a software issue trying to process the Performance Management Subscription update request. | | -| Step 7 (ALT) | EXCEPTION: UNEXPECTED CONDITION –
The SMO (FOCOM) returns to the operator that there was an unexpected condition.
The Use Case ends here. | | -| Step 8 (M) | UPDATE PERFORMANCE MANAGEMENT SUBSCRIPTION (SUCCESS) –
A successful Performance Management Subscription update operation will result in a success from FOCOM back to O-Cloud operator. This is a return/response for Step 1. | | -| Ends when | This Use Case ends under two cases:
EXCEPTION CASE – The use case ends when an exception case is encountered. For example, when a requestor tries to perform an update operation where no Performance Management Subscription(s) match the request.
UPDATE OPERATION SUCCEEDS – The use case will end if the update operation of Performance Management Subscription successfully completed. | | -| Exceptions | EXCEPTION CASE: NON-EXISTENT SUBSCRIPTION – This exception is encountered if the update operation results in no Performance Management Subscriptions that match the requested subscriptions to be updated.
EXCEPTION CASE: UNEXPECTED CONDITION – The IMS might not be able to perform to the Performance Management Subscription update request perhaps due to a software fault. In this case, the unexpected condition exception is encountered. | | -| Post-conditions | SUCCESS – The Performance Management Subscription has been updated successfully and status returned to the requestor (O-Cloud operator).
FAILURE – An exception notification of a non-existent Performance Management Subscription or Unexpected Condition has been issued. | | -| Traceability | [REQ-ORC-O2-87], [REQ-ORC-O288] | | -| NOTE 1: Update is a basic type of operation (cf. CRUD operations), the “U” in CRUD.
NOTE 2: An entity may be any authorized user or authorized management function.
NOTE 3: This use case is one in a series of use cases related to Performance Management Subscription management (CRUD operations). The create, query, and delete Performance Management Subscription operations are described in other use cases.
NOTE 4: PM Subscription update is also applicable to embedded subscriptions which are created in PM Job Creation (see the PM Job Creation Use Case).
NOTE 5: If a Performance Management Subscription update has a mixture of valid and non-existing subscriptions, the operation will only perform operations of valid subscriptions. | | | - -#### 3.8.13.3 UML Sequence Diagram - -![UML Sequence Diagram for PM Subscription Update. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows the interaction for updating a performance management subscription, including preconditions, a successful update path, and two exception paths for non-existent subscription and unexpected conditions.](1fd763be1b7a05b52e554f0583617642_img.jpg) - -**PRECONDITIONS:** - SMO has connectivity to O-Cloud - O-Cloud has registered its IMS with the SMO - The identification & privileges of a SMO user has been verified - -**Performance Management Subscription Update Use Case** - -- 1 Performance Management Subscription Update (O-Cloud Operator to FOCOM) -- 2 Performance Management Subscription Update (FOCOM to IMS) - - Subscribers have consumer subscription identifier. - - Connection authentication is verified - - Subscription operation is processed -- 3 Performance Management Subscription Update Status (Success) (IMS to FOCOM) -- 4 Performance Management Subscription not found (IMS to FOCOM) [Exception: Update of a non-existent Performance Management Subscription] -- 5 Performance Management Subscription not found (FOCOM to O-Cloud Operator) -- 6 Unexpected condition (IMS to FOCOM) [Exception: Unexpected condition] -- 7 Unexpected condition (FOCOM to O-Cloud Operator) -- 8 Performance Management Subscription Update Status (Success) (FOCOM to O-Cloud Operator) - -**End Performance Management Subscription Update Use Case** - -UML Sequence Diagram for PM Subscription Update. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows the interaction for updating a performance management subscription, including preconditions, a successful update path, and two exception paths for non-existent subscription and unexpected conditions. - -Figure 3-55: PM Subscription Update - -### 3.8.14 Performance Management Subscription Delete (IMS) Use Case - -#### 3.8.14.1 High Level Description - -This use case is about the Management of Performance Management Subscriptions; in particular, the delete service operation. The create, update, and query of a Performance Management Subscription are documented in separate use cases. This use case only concerns the deletion of one or more Performance Management Subscription(s) based on a list of subscription(s). - -The delete of a Performance Management Subscription is the ability of an authorized entity to delete a Performance Management Subscription towards the IMS. An entity here would usually be the SMO; however, it could also be another authorized user/technician, or machine (e.g., software, script, etc.). - -Any subscription operations that change a subscription are logged. Therefore, the delete of a Performance Management subscription is expected to be logged within the O-Cloud IMS. - -#### 3.8.14.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------| -| Use Case Title | Performance Management Subscription Delete | | -| Goal | An entity (typically the SMO) initiates the delete of one or more Performance Management Subscription(s) based on a list of subscription(s). The operation is handled by the IMS. (NOTES 1, 2, 3, 4 and 5) | 3.8.7
Performance Measurement Job Delete Use Case | -| Actors and Roles |

O-Cloud Operator – The O-Cloud operator is a user that is interested in deleting a Performance Management Subscription.

SMO (FOCOM) – The FOCOM within the SMO is used in this use case to represent any consumer or management entity for the Performance Management Subscription.

IMS – The IMS within the O-Cloud performs the Performance Management Subscription delete operation.

| | -| Assumptions | There are no assumptions. | | -| Preconditions |

Connectivity – The Subscriber has connectivity to the Publisher by some mechanism. The mechanism by which the subscriber achieves connectivity to the publisher is out of the scope of this Use Case.

O-Cloud Operational – The O-Cloud is installed, operating, and registered with the SMO.

Privilege – The consumer identification and privileges of a SMO user have been verified to be able to perform O2 operations.

| | -| Begins when | The use case begins when an operator at the SMO wishes to delete Performance Management Subscription(s). | | -| Step 1 (M) |

PERFORMANCE SUBSCRIPTION DELETE REQUEST –

The O-Cloud operator initiates the deletion of one or more Performance Management Subscription(s) indicating the list of subscription(s) to be deleted.

| | -| Step 2 (M) |

PERFORMANCE SUBSCRIPTION DELETE REQUEST –

The delete Performance Management Subscription request is issued from FOCOM (SMO) to the publisher (IMS) indicating the list of subscription(s) to be deleted. (NOTE 6)

| | -| Step 3 (ALT) |

PERFORMANCE MANAGEMENT SUBSCRIPTION DELETE OPERATION –

A connection authentication is verified by the publisher (IMS). This is a standard type of check. The update request operation to delete one or more Performance Management Subscription(s) is processed by the IMS (publisher).

The Performance Management Subscription delete operation will be logged by the IMS. (NOTE 7)

| | -| Step 4 (ALT) | PERFORMANCE MANAGEMENT SUBSCRIPTION DELETE – | | - -| | | | -|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | If the Performance Management Subscription operation was successful, then a success response is sent to the SMO (consumer) over the O2ims interface. (NOTE 8) | | -| Step 5 (ALT) | ALT EXCEPTION: NO PERFORMANCE MANAGEMENT SUBSCRIPTION(S) FOUND –

This exception is encountered when the PM Subscription delete operation requests contains only non-existent PM Subscription(s).

In this case, none of the PM Subscription(s) in the request were found.

For example, the PM Job delete operation with associated embedded subscriptions would cause those PM Subscriptions to be deleted. Thus, when this PM Job Subscription request is received, if the request had only those PM Subscriptions listed it would trigger this exception.

A “no Performance Management Subscriptions found” response is issued from IMS to FOCOM (SMO).

The Use Case ends. | | -| Step 6 (ALT) | ALT EXCEPTION: UNEXPECTED CONDITION –

A response is sent to the requesting entity from the SMO, that the IMS encountered an unexpected condition processing the request.

The Use Case ends. | | -| Step 7 (M) | DELETE PERFORMANCE MANAGEMENT SUBSCRIPTION RESPONSE –

A response is returned to the FOCOM (SMO) from the IMS for the delete Performance Management Subscription operation. | | -| Ends when | This Use Case ends when either the Performance Management Subscription(s) have been deleted successfully, or one of the two Exception cases has been encountered. | | -| Exceptions | EXCEPTION: NO PERFORMANCE MANAGEMENT SUBSCRIPTION(S) FOUND – This exception is encountered if no Performance Management Subscriptions match the Performance Management Subscription delete request.

EXCEPTION: UNEXPECTED CONDITION – The IMS might not be able to perform to the Performance Management Subscription delete operation perhaps due to a software fault. In this case, the unexpected condition exception is encountered. | | -| Post-conditions | SUCCESS – The Performance Management Subscription(s) have been deleted successfully and status returned to the requestor (O-Cloud operator).

FAILURE – An exception notification of “No Performance Management Subscriptions found” or “Unexpected Condition” has been issued. | | -| Traceability | [REQ-ORC-O2-89], [REQ-ORC-O2-90] | | -| NOTE 1: Delete is a basic type of operation (cf. CRUD operation), the “D” in CRUD.

NOTE 2: An entity may be any authorized management function.

NOTE 3: This use case is one in a series of use cases related to Performance Management Subscription management (CRUD operations). The create, update, and update of Performance Management Subscription operations are described in other use cases. | | | - -- NOTE 4: The PM Job deletion operation in the case of embedded subscriptions causes the associated PM subscription to be automatically deleted. -- NOTE 5: If a PM Subscription Delete depends on a PM Job, and that PM Job is deleted through the PM Job delete operation. The PM subscription is automatically deleted. (See the Performance Measurement Job Delete Use Case). -- NOTE 6: It would be left to protocol design how handle the deletion of multiple subscriptions. -- NOTE 7: If some of the PM Subscription(s) exist in the request, and some PM subscription(s) do not, the operation would be processed successfully, returning the ones that were deleted. -- NOTE 8: If the PM Subscription deletion request was successful, the operator is notified in step 7. - -#### 3.8.14.3 UML Sequence Diagram - -![UML Sequence Diagram for PM Subscription Delete. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The sequence starts with a 'Delete Performance Subscription request' from the operator to FOCOM. FOCOM then sends a 'Delete Performance Subscription request' to IMS. IMS verifies authentication and processes the delete operation. An 'alt' block titled '[Successful Delete]' shows FOCOM sending a 'Delete Performance Management Subscription Status (Success)' response to the operator. Two 'Exception' blocks follow: '[Exception: No Performance Subscriptions found]' leading to a 'Failure Case' and 'Use Case Ends', and '[Exception: Unexpected condition]' leading to another 'Failure Case' and 'Use Case Ends'. Finally, the operator receives a 'Delete Performance Management Subscription Status response (Success)' from FOCOM, and the use case ends.](b0a5d736df5f6fe2c0c6dd800bb0ff9a_img.jpg) - -**PRECONDITIONS:** -SMO has connectivity to O-Cloud -O-Cloud has registered its IMS with the SMO -The identification & privileges of a SMO user has been verified - -**Sequence of Interactions:** - -- 1 Delete Performance Subscription request**: O-Cloud Operator → Service Management & Orchestration Framework (Subscriber) (FOCOM). Note: Subscribers have consumer subscription identifier. -- 2 Delete Performance Subscription request**: FOCOM → O-Cloud Platform (Publisher) (IMS). Note: Connection authentication is verified. -- 3 Process delete operation for one Subscription**: Internal message within IMS. -- alt [Successful Delete]**: - - 4 Delete Performance Management Subscription Status (Success)**: IMS → FOCOM. -- [Exception: No Performance Subscriptions found]**: - - Failure Case**: IMS → FOCOM: **5 No Performance Management Subscriptions found**. Use Case Ends. -- [Exception: Unexpected condition]**: - - Failure Case**: IMS → FOCOM: **6 Unexpected condition**. Use Case Ends. -- 7 Delete Performance Management Subscription Status response (Success)**: FOCOM → O-Cloud Operator. -- End Delete Performance Management Subscription Use Case**: Final message indicating the end of the use case. - -UML Sequence Diagram for PM Subscription Delete. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The sequence starts with a 'Delete Performance Subscription request' from the operator to FOCOM. FOCOM then sends a 'Delete Performance Subscription request' to IMS. IMS verifies authentication and processes the delete operation. An 'alt' block titled '[Successful Delete]' shows FOCOM sending a 'Delete Performance Management Subscription Status (Success)' response to the operator. Two 'Exception' blocks follow: '[Exception: No Performance Subscriptions found]' leading to a 'Failure Case' and 'Use Case Ends', and '[Exception: Unexpected condition]' leading to another 'Failure Case' and 'Use Case Ends'. Finally, the operator receives a 'Delete Performance Management Subscription Status response (Success)' from FOCOM, and the use case ends. - -Figure 3-56: PM Subscription Delete - -### 3.8.15 Performance Management Configuration Use Case - -#### 3.8.15.1 High Level Description - -The Performance Management Configuration use case will allow for a requesting entity to alter other attributes not covered in the Performance Measurement Job Creation Use Case and the Performance Management Subscription Use Cases. - -This use case complements the Performance Measurement Job Creation Use Case, Performance Measurement Job Update Use Case, Performance Management Subscription Use Case, Performance Management Subscription Update Use Case which are other use cases that will configure the behavior of the Performance Management operation. These other use cases can alter subtending attributes of the PerformanceSubscription and PerformanceMeasurementJob family of related objects. - -Thus, this use case is focused on the ability to change other attributes related to Performance Management operation. For example, the PerformanceMeasureStore class has a retentionPeriod attribute which can be configured with this use case. The definition of the retentionPeriod is covered in the O2 Information Model. See the Alarm Purge Use Case (see clause 3.7.13 in this document) and Alarm List Creation Use Case (see clause 3.7.11 in this document) and Retention Period concepts for further details (O-RAN WG6.O2-GA&P [9]) - -#### 3.8.15.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Use Case Title | Performance Management Configuration Use Case | | -| Goal | This use case described how an authorized entity (typically the SMO) can change the configuration of Performance Management related attributes. See note 1. | Performance Measurement Job Creation, Performance Measurement Job Update, Performance Management Subscription, Performance Management Subscription Update Use Case | -| Actors and Roles | O-Cloud Operator – The O-Cloud operator is a user that is interested in configuring Performance Management related attributes.
SMO (FOCOM) – The FOCOM within the SMO is used in this use case to request for a Performance Management Configuration change.
IMS – The IMS within the O-Cloud performs the Performance Management Configuration operation. | | -| Assumptions | There are no assumptions. | | -| Preconditions | Connectivity – The Subscriber has connectivity to the Publisher by some mechanism. The mechanism by which the subscriber achieves connectivity to the publisher is out of the scope of this Use Case. | | - -| | | | -|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

O-Cloud Operational – The O-Cloud is installed, operating, and registered with the SMO.

Privilege – The consumer identification and privileges of a SMO user have been verified to be able to perform O2 operations.

| | -| Begins when | This use case being when a management entity, typically the SMO, requests for an update of Performance Configuration attributes. | | -| Step 1 (M) |

PERFORMANCE MANAGEMENT CONFIGURATION REQUEST –

The O-Cloud operator initiates a request to configure Performance Management attributes

| | -| Step 2 (M) |

PERFORMANCE MANAGEMENT CONFIGURATION REQUEST –

The Performance Management Configuration request is issued from the management entity (FOCOM / SMO) to the IMS.

The IMS authenticates the connection.

The IMS configures the attributes values for requested objects. If the IMS is unable to configure the attribute(s) with requested values, they are not updated.

IMS performs post configuration operations. For example, if the retention period is altered, the IMS will purge elements that are older than the new retention period.
See note 2.

| | -| Step 3 (ALT) |

PERFORMANCE MANAGEMENT CONFIGURATION OPERATION SUCCESS / PARTIAL SUCCESS –

SUCCEEDED - If every requested attribute was successfully updated, then the IMS responds to the requesting management entity, a Performance Management Configuration succeeded.

PARTIALLY SUCCEEDED - If only some of the requested attributes could be configured and some of the requested attributes could not be configured, then the IMS configures the attributes that it can and responds to the requesting management entity, a Performance Management Configuration partially succeeded.

| | -| Step 4 (ALT) |

EXCEPTION: ALL REQUESTED OBJECT(S)/ATTRIBUTE(S) NOT FOUND –

If the Performance Management Configuration request has only object(s) and attribute(s) that do not exist, then a Performance Management Configuration of All requested Object(s) and Attribute(s) not found is issued back to the requestor. See note 3.

| | -| Step 5 (ALT) |

EXCEPTION: ALL REQUESTED OBJECT(S) AND ATTRIBUTE(S) NOT FOUND –

If the configuration operation results in all Performance Management objects and attributes were not found, then a “All requested object and attributes were not found” response is issued from FOCOM to the O-Cloud Operator. This is a return/response for Step 1.

The Use Case ends here.

| | - -| | | | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 6 (ALT) | EXCEPTION: UNEXPECTED CONDITION IMS to SMO –

The IMS might not be able to perform the configuration operation. There might have been a software issue encountered in the processing of the Performance Management configuration request.

A response is sent to the requesting entity from the IMS, that the IMS encountered an unexpected condition processing the request. | | -| Step 7 (ALT) | EXCEPTION: UNEXPECTED CONDITION SMO to O-Cloud Operator –

The SMO (FOCOM) returns to the operator that there was an unexpected condition.

The Use Case ends here. | | -| Step 8 (M) | PERFORMANCE MANAGEMENT CONFIGURATION RESPONSE –

A successful Performance Management Configuration operation will result in a success from FOCOM back to O-Cloud operator. This is a return/response for Step 1. | | -| Ends when | This Use Case ends under two cases:

EXCEPTION CASE – The use case ends when an exception case is encountered. For example, when a requestor tries to perform an update operation where all requested object(s) and attribute(s) are not found.

UPDATE OPERATION SUCCEEDS – The use case will end if the configuration operation of Performance Management attribute(s) successfully completed. | | -| Exceptions | EXCEPTION CASE: ALL REQUESTED OBJECT(S) AND ATTRIBUTE(S) NOT FOUND – This exception is encountered if no Performance Management objects and attributes were not found that match those in the Performance Management Configuration request.

EXCEPTION CASE: UNEXPECTED CONDITION – The IMS might not be able to perform to the Performance Management Configuration request perhaps due to a software fault. In this case, the unexpected condition exception is encountered. | | -| Post-conditions | SUCCESS – The Performance Management Configuration has resulted in successfully configuration attributes. A status is returned to the requestor (O-Cloud operator).

FAILURE – An exception notification none of the request object(s) and attribute(s) were found or an Unexpected Condition has been issued. | | -| Traceability | [REQ-ORC-02-99], [REQ-ORC-02-100] | | -| NOTE 1: The Performance Measurement Job Creation Use Case and the Performance Management Subscription Use Case allow for a user to configure attributes related to PM Jobs and Performance Management Subscriptions

NOTE 2: Race conditions that may occur because of changing the retention period is resolved through IMS implementation.

NOTE 3: If a Performance Management Configuration update has a mixture of valid objects-attributes and non-existing objects-attributes, then the operation will only be completed for the configurable attribute(s). This would return a partial success indicator (in Step 3). | | | - -#### 3.8.15.3 3.8.15.3 UML Sequence Diagram - -![UML Sequence Diagram for PM Configuration. Lifelines: Personnel (Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows the interaction for a Performance Management Configuration Use Case, including preconditions, the main flow, and two exception paths.](0f666d2ebbad7fab84c7c4fb531ea932_img.jpg) - -**PRECONDITIONS:** -SMO has connectivity to O-Cloud -O-Cloud has registered its IMS with the SMO -The identification & privileges of a SMO user has been verified - -**Performance Management Configuration Use Case** - -- 1 Performance Management Configuration request (Cloud Operator to FOCOM) -- 2 Performance Management Configuration request (FOCOM to IMS) - - Connection authentication is verified - - PM Configuration request is processed - - Post-configuration impacts are processed by the IMS -- 3 Performance Management Configuration status (Success or Partial Success) (IMS to FOCOM) -- 4 All requested Object(s) and Attribute(s) not found (Exception: Update of only non-existent Object(s) or Attribute(s)) (IMS to FOCOM) -- 5 All requested Object(s) and Attribute(s) not found (FOCOM to Cloud Operator) -- Use Case Ends -- 6 Unexpected condition (Exception: Unexpected condition) (IMS to FOCOM) -- 7 Unexpected condition (FOCOM to Cloud Operator) -- Use Case Ends -- 8 Performance Management Configuration response (FOCOM to Cloud Operator) - -**End Performance Management Configuration Use Case** - -UML Sequence Diagram for PM Configuration. Lifelines: Personnel (Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows the interaction for a Performance Management Configuration Use Case, including preconditions, the main flow, and two exception paths. - -Figure 3-57: PM Configuration - -## 3.9 VLAN Management Use Cases - -### 3.9.1 VLAN Allocation Use Case - -#### 3.9.1.1 High Level Description - -This Use Case supports allocation of a VLAN ID to support various deployment use cases such a network slice. - -As an example, one of the consumers is RAN NSSMF (Network Slice Subnet Management Function) that needs to associate a RAN slice to a VLAN ID during slice subnet provisioning procedures. Within a given O-Cloud, RAN NSSMF uses this VLAN ID as handover between O-Cloud and transport network so that the slice could be carried through the transport network across multiple O-Clouds. If a slice spans multiple O-Clouds, this handover is necessary for each segment of the transport connecting these O-Clouds. See Annex A in the O-RAN.WG1.Slicing-Architecture-v05.00 [14] as to how this VLAN ID is used in various deployments. - -The scope of this use case is simply to allocate/reserve a VLAN ID within O-Cloud. As a part of this use case, no configuration is pushed in the O-Cloud. - -Since VLANs have a local significance, each O-Cloud manages a pool of VLAN IDs, and returns a VLAN ID upon a query/request from SMO (FOCOM). To avoid using the same VLAN ID multiple times, O-Cloud may take the VLAN ID out of the “available” pool after it allocates it. O-Cloud may choose any mechanism to ensure that same VLAN IDs is not used multiple times. - -NOTE: There are other viable identifiers to associate a slice with (such as VLANs, VNIs, VRFs, etc.). In the initial version of O-RAN network slicing, VLAN IDs are used for this purpose. Additional identifiers, or an abstract identifier may be introduced in future. This does not impose any networking constrains within O-Cloud. - -#### 3.9.1.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Allocation of VLAN ID (and associate it to a network slice optionally). See O-RAN.WG1.Slicing-Architecture-v05.00 [14] | | -| Actors and Roles | RAN NSSMF – acts as a consumer of VLAN Allocation use case for network slice subnet management purposes.
SMO/FOCOM – Federated O-Cloud Orchestration and Management IMS/DMS | | -| Assumptions | Slicing is used as an example consumer of this VLAN ID allocation service.
1. NSSMF function is available and drives the creation of network slice
2. If network slice spans multiple O-Clouds within RAN domain, below use case request is executed each O-Cloud | | -| Preconditions | 1. SMO is available
2. The VLAN IDs Pool is available in O-Cloud
3. NF has already been deployed. | | -| Begins when | As a part of network slice creation, NSSMF requests a VLAN identifier from O-Cloud. Optionally, a metadata may be provided by NSSMF that could include Slice ID.
Metadata is a generic structure that could be passed along with the request. This structure could include various data items such as Slice ID.
As specified in Step 4 below, if metadata is provided, O-Cloud associates VLAN ID with the metadata. | | -| Step 1 (M) | SMO/FOCOM requests a VLAN ID from O-Cloud. This request may be on O2ims/O2dms | | -| Step 2(M) | O-Cloud does the feasibility check – i.e., if a VLAN ID is available. | | -| Step 3 (M) | O-Cloud selects an available VLAN ID from the pool of available VLAN IDs | | -| Step 4 (O) | O-Cloud associates the VLAN ID to metadata provided by the SMO, which may include slice identification related information.
. | | -| Step 5 (M) | O-Cloud returns the selected VLAN ID to SMO.
How SMO uses this VLAN ID is described in section 3.9.1.1 | | -| Ends when | The response is returned | | -| Exceptions | No VLAN ID is available | | -| Post Conditions | VLAN ID is reserved/allocated in O-Cloud | | -| Traceability | REQ-ORC-GEN24 | | - -#### 3.9.1.3 UML sequence diagram - -![UML sequence diagram for VLAN Allocation. Lifelines: Service Management & Orchestration Framework (NSSMF, FOCOM) and O-Cloud Platform (IMS/DMS). The sequence starts with a 'VLAN Allocate Request' from FOCOM to IMS/DMS. Step 1 is 'Allocate VLAN ID Request' from FOCOM to IMS/DMS. A 'ref' block 'Feasibility Check Procedure' follows. A note indicates 'Remove the VLAN ID from "available" VLAN IDs Pool'. An 'opt' block '[Metadata is specified (Optionally)]' contains a 'ref' block 'Associate VLAN ID with Metadata and save in DB'. An 'alt' block '[Successful fulfilment of the request]' shows '5 VLAN ID is returned' from IMS/DMS to FOCOM. An 'alt' block '[Exception: No VLAN ID is available]' is also present. The sequence ends with 'End VLAN Allocate Request' from FOCOM to IMS/DMS.](d884367c84ba50f250499f79c4b4b950_img.jpg) - -UML sequence diagram for VLAN Allocation. Lifelines: Service Management & Orchestration Framework (NSSMF, FOCOM) and O-Cloud Platform (IMS/DMS). The sequence starts with a 'VLAN Allocate Request' from FOCOM to IMS/DMS. Step 1 is 'Allocate VLAN ID Request' from FOCOM to IMS/DMS. A 'ref' block 'Feasibility Check Procedure' follows. A note indicates 'Remove the VLAN ID from "available" VLAN IDs Pool'. An 'opt' block '[Metadata is specified (Optionally)]' contains a 'ref' block 'Associate VLAN ID with Metadata and save in DB'. An 'alt' block '[Successful fulfilment of the request]' shows '5 VLAN ID is returned' from IMS/DMS to FOCOM. An 'alt' block '[Exception: No VLAN ID is available]' is also present. The sequence ends with 'End VLAN Allocate Request' from FOCOM to IMS/DMS. - -Figure 3-58: VLAN Allocation - -### 3.9.2 VLAN Deallocation Use Case - -#### 3.9.2.1 High Level Description - -This use case supports deallocation of a VLAN ID when a given VLAN ID not needed anymore, such as at the time of deletion of a network slice. A given VLAN IDs is a returned back to “available” pool of VLAN IDs in each O-Cloud. - -VLAN IDs are a limited/finite set of pool. Therefore, it is important to recycle the VLAN IDs as they are not needed anymore. As an example, when a network slice is deleted, RAN NSSMF sends a deallocate VLAN ID request to O-Cloud. O-Cloud moves the VLAN ID into the pool of available VLAN IDs. - -#### 3.9.2.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | Freeing of VLAN ID (associated with network slice). See O-RAN.WG1.Slicing-Architecture-v05.00 [14] | | -| Actors and Roles | RAN NSSMF – acts as a consumer of VLAN Allocation use case for network slice subnet management purposes.
SMO/FOCOM – Federated O-Cloud Orchestration and Management
IMS/DMS | | -| Assumptions | Slicing is used as an example consumer of this VLAN ID allocation service.
1. NSSMF function is available and drives the deletion of network slice | | - -| | | | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------| -| | 2. If network slice spans multiple O-Clouds within RAN domain, below use case request is executed for each O-Cloud | | -| Preconditions | 1. SMO is available
2. Network slice already exists | 3.9.1 VLAN ID Allocation | -| Begins when | As a part of network slice deletion, NSSMF requests O-Cloud to free the VLAN ID associated with the slice. | | -| Step 1 (M) | O-Cloud verifies that the VLAN ID is valid that is being deleted. If this is not a valid VLAN ID, no action is taken and response with error is returned. Verification of the valid VLAN ID can be multifold, such as:
1. Is this a valid number?
2. Is it within the range of available VLAN IDs pool? | | -| Step 2 (O) | O-Cloud deletes the metadata previously associated to the VLAN ID | | -| Step 3 (M) | O-Cloud returns freed VLAN ID to the pool of available VLANs | | -| Ends when | The response is returned | | -| Exceptions | Invalid VLAN ID specified | | -| Post Conditions | VLAN ID is freed in O-Cloud | | -| Traceability | REQ-ORC-GEN24 | | - -#### 3.9.2.3 UML sequence diagram - -![UML sequence diagram for VLAN Deallocation. Lifelines: NSSMF, FOCOM (Service Management & Orchestration Framework) and IMS/DMS (O-Cloud Platform). The sequence starts with a 'VLAN Deallocate Request' from FOCOM to IMS/DMS. Step 1: 'Deallocate VLAN ID Request' is sent. A 'ref' block 'Validation of VLAN ID Procedure' occurs. An 'opt' block '[Metadata associated with VLAN ID is specified]' contains a 'ref' block 'Delete VLAN ID and associated Metadata from the DB'. Step 2: 'Return VLAN ID to "available" VLAN IDs Pool' is sent. An 'alt' block '[Successful fulfilment of the request]' contains step 3: 'VLAN ID has been successfully deallocated'. An 'Exception: Invalid VLAN ID' is also shown. The sequence ends with 'End VLAN Deallocate Request'.](99315a3665b263851e1ea8f65af6231b_img.jpg) - -``` - -sequenceDiagram - participant NSSMF - participant FOCOM - participant IMS/DMS - Note right of FOCOM: VLAN Deallocate Request - FOCOM->>IMS/DMS: 1 Deallocate VLAN ID Request - Note right of IMS/DMS: ref Validation of VLAN ID Procedure - Note right of IMS/DMS: opt [Metadata associated with VLAN ID is specified] - Note right of IMS/DMS: ref Delete VLAN ID and associated Metadata from the DB - IMS/DMS-->>FOCOM: Return VLAN ID to "available" VLAN IDs Pool - alt Successful fulfilment of the request: 3 VLAN ID has been successfully deallocated - else Exception: Invalid VLAN ID - end - Note right of FOCOM: End VLAN Deallocate Request - -``` - -UML sequence diagram for VLAN Deallocation. Lifelines: NSSMF, FOCOM (Service Management & Orchestration Framework) and IMS/DMS (O-Cloud Platform). The sequence starts with a 'VLAN Deallocate Request' from FOCOM to IMS/DMS. Step 1: 'Deallocate VLAN ID Request' is sent. A 'ref' block 'Validation of VLAN ID Procedure' occurs. An 'opt' block '[Metadata associated with VLAN ID is specified]' contains a 'ref' block 'Delete VLAN ID and associated Metadata from the DB'. Step 2: 'Return VLAN ID to "available" VLAN IDs Pool' is sent. An 'alt' block '[Successful fulfilment of the request]' contains step 3: 'VLAN ID has been successfully deallocated'. An 'Exception: Invalid VLAN ID' is also shown. The sequence ends with 'End VLAN Deallocate Request'. - -Figure 3-59: VLAN Deallocation - -## 3.10 Network Slicing Use Cases - -### 3.10.1 Network Slice Creation Use Case - -#### 3.10.1.1 High Level Description - -This use case supports creation of RAN slice subnet. - -Network slices may span across multiple domains such as RAN, Core, and Transport. The slice is divided into multiple subnets; one subnet per domain, i.e., RAN Slice Subnet, Transport Slice Subnet, and Core Slice Subnet. This section only covers the RAN Slice Subnet. - -Network slice creation requires creation of O-RAN Network Slice Subnet Instance (O-NSSI). RAN Network Slice Subnet Management Function (NSSMF) manages the creation and deletion of O-NSSI. For details, please see O-RAN.WG1.Slicing-Architecture-v06.00 [14]. - -RAN NSSMF also manages disaggregated RAN deployment use cases where Network Functions (such as O-DU and O-CU) are deployed in different O-Clouds or in different locations in each O-Cloud. RAN NSSMF manages creation of O-NSSI and relevant Network Functions (NFs) across multiple O-Clouds. RAN NSSMF triggers the Network Functions management operation via NFO. RAN NSSMF also coordinates with the constituent Transport NSSMF to achieve the slice connectivity across multiple O-Clouds. - -RAN NSSMF coordinates with its constituent Transport NSSMF through NSMF to stitch the connectivity across multiple O-Clouds or multiple sites in a distributed O-Cloud (for disaggregated RAN deployments). In such deployments, the network connectivity for the slice may require multiple network connections, herein referred to as network segments. For example, a slice spanning across two O-Clouds connected by transport may have up to 5 network segments. Two network segments within each O-Cloud, two segments between the O-Clouds and their respective Transport attachment points and a fifth network segment in the transport network. - -In multi-vendor O-RAN deployments, many flavors of NFs may co-exist. Some may require trunked interfaces whereas others may require access interfaces. Similarly, multiple forms for NFs may exist such as CNFs, VNFs, or PNFs. - -The End-2-End slice is associated with a network segment unique identifier per network segment, herein called a tag. While a choice of various viable identifiers (such as VLANs, VNIs, VRFs, etc.) is available, in this Use Case a VLAN ID is one of the example identifier/tags for network slicing. In that case, VLAN IDs are chosen for both within O-Cloud as well as for handover to the transport network. - -NOTE 1: The use case further elaborates on the scenario of using VLAN IDs, but other network segmentation solutions are also possible. - -The packets marked with this unique tag/VLAN ID traverse the network segments within O-Cloud and are of local significance within a given network segment. This tag/VLAN ID may be stitched/mapped to a different tag by the O-Cloud Gateway to handover to the transport network attachment point. As an example, say VLAN ID 100 was chosen to mark an EMBB slice. This VLAN ID 100 may map to a VRF\_X at O-Cloud Gateway and a VLAN ID 200 may be used to carry the same packets in the transport network. This mapping allows the transport network to carry the packets associated with each slice. - -Depending upon the slice SLAs and deployment scenario of a slice, RAN NSSMF makes the decisions such as: - -- If additional NF instances need to be deployed (e.g., one O-DU instance per slice), or -- Use the existing NF for the new slice (e.g., shared resources for a slice) -- RAN NSSMF/SMO makes an NF placement decision taking all relevant information into account. -- Etc. - -NOTE 2: The actual details of such decisions by RAN NSSMF are out of the scope for this use case. See O-RAN.WG1.Slicing-Architecture-v06.00 for details. - -#### 3.10.1.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|----------------------------------------------|-------------------------| -| Goal | Creation of network slice subnet in O-Cloud. | | - -| | | | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------| -| Actors and Roles |

RAN NSSMF – Manages network slice subnet, e.g., through SMO services. This includes:

  • Triggers the Instantiation of NFs for a given slice
  • Orchestrates the end-2-end connectivity between different involved NFs for a given slice

SMO/FOCOM/IMS – Federated O-Cloud Orchestration and Management
NFO/DMS – To deploy NFs, if needed

| | -| Assumptions |
  1. RAN NSSMF function is available and drives the creation of network slice subnet instance (O-NSSI)
  2. RAN NSSMF uses FOCOM to communicate with IMS, and it interacts NFO to trigger the NF management with DMS
  3. If network slice spans multiple O-Clouds (or multiple sites in a distributed O-Cloud) within RAN domain below use case request is executed for each O-Cloud or site.
  4. RAN NSSMF may, but need not, request the deployment of NFs (depending upon the slice SLAs)
| | -| Preconditions |
  1. SMO is available
  2. IMS and DMS are available
  3. The O-Cloud Node Cluster Network access or trunk port is created if the NFs require access or trunk port support.
| | -| Begins when | RAN NSSMF starts the creation of an instance of O-NSSI | | -| Step 1(M) |

SMO/FOCOM requests an O-Cloud internal VLAN ID from O-Cloud over O2ims to associate with the slice. The requested VLAN ID will be used to tag the data frames of the NF's respective slice, configured through the O1 interface. Also, the requested VLAN ID will be used to provision the O-Cloud Site Network Fabric.

If NF is already deployed and is using trunk port, add this VLAN ID to the trunk port and If NF is using cluster access mode ports, add a new access port and this VLAN ID to it.

| VLAN Allocation
Use case [3.9.1] | -| Step 2(O) |

If a slice spans across multiple O-Clouds or sites in a distributed O-Cloud:

NFs associated with the slice need to be connected to the O-Cloud Gateway so that they can connect to their counterpart through transport network in the remote O-Cloud or site in a distributed O-Cloud. 3GPP TS 28.541 defines EP_Transport for this connectivity.

For example: O-DU connects to endpoint EP_F1U to communicate with O-CU_UP. This EP_F1U needs to be connected to EP_Transport to achieve this connectivity.

FOCOM sends request to IMS to ensure connectivity of the NFs associated with slice to the O-Cloud Gateway. This connectivity requires two interconnections. One connection from the NF to O-Cloud Gateway and second from the O-Cloud Gateway to the Transport network. Depending upon the case, the following options are possible to ensure inter-domain connectivity:

  1. The Network Segment (e.g., VLAN ID) used for handover shall be selected/reserved by the O-Cloud
  2. The O-Cloud shall be capable of receiving the Network Segment (e.g., VLAN ID) used for handover as an input for the O-Cloud internal configuration
| | -| Step 3(O) |

If NF need to be instantiated as part of the creation of slice subnet instance:

SMO/ NFO sends request to O-Cloud via O2dms interface to deploy NFs. NFO may select appropriate cluster to deploy the NF on.
Execute “Instantiate Network Function on O-Cloud” Use Case.

If NF needs to be connected to the trunk port, the trunk port is created prior to deploying the NF. Add the VLAN ID allocated in step 1 to this trunk port.

| Instantiate NF
use case [3.2.1] | - -| | | | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | If NF needs an access port for the new slice, infrastructure to create access port and assign the VLAN ID to that port. | | -| Step 4(M) | The response is returned | | -| Step 5(O) |

Exceptions: Slice creation fails. The failure exception could occur because of partial failures, such as:

  • • Fail to deploy NF
  • • Fail to create connectivity for any network segment

Clean up resources are required for such exceptions, such as:

  • • Free up resources allocated for the deployment of NFs
  • • Free up network resources, e.g., IPAM, VLAN ID, etc.
| | -| Post Conditions | None | | -| Traceability | REQ-ORC-GEN25, REQ-ORC-GEN26, REQ-ORC-GEN27, REQ-ORC-GEN28, REQ-ORC-O2-46, REQ-ORC-O2-64, REQ-ORC-O2-65 | | - -#### 3.10.1.3 UML sequence diagram - -![UML sequence diagram for Network Slice Creation. Lifelines: Service Management & Orchestration Framework (NSSMF, FOCOM, NFO) and O-Cloud Platform (IMS, DMS). The process involves a 'Create Slice Request' followed by VLAN ID allocation, optional gateway connectivity, optional NF deployment, and final resource cleanup or success confirmation.](8f78b5d84dca49cf2769440c7942a27d_img.jpg) - -``` - -sequenceDiagram - participant SMF as NSSMF - participant FOCOM as FOCOM - participant NFO as NFO - participant IMS as IMS - participant DMS as DMS - - Note right of SMF: Create Slice Request - SMF->>IMS: 1 VLAN ID Request to associate with Slice - Note right of IMS: Execute the VLAN ID Allocation procedure - alt VLAN ID needs to be added to the trunk port - Note right of IMS: Add the allocated VLAN ID to trunk port of NF - else NF requires Access port - Note right of IMS: Create access port and assign the allocated VLAN ID to the port - end - opt Slice spans multiple O-Clouds - SMF->>IMS: 2 O-Cloud Gateway connectivity request - Note right of IMS: Extend NF network connectivity to the O-Cloud Gateway - end - opt new Network Function instance need to deployed - SMF->>IMS: 3 Deploy Network Function (NF) Request - alt NF requires connectivity to trunk port - Note right of IMS: Add the allocated VLAN ID to trunk port of NF - else NF requires Access port - Note right of IMS: Create access port and assign the allocated VLAN ID to the port - end - Note right of IMS: Execute Instantiate Network Function procedure - alt Successful fulfilment of the request - Note right of IMS: 3.1 successful deployment of NF - else Exception: Failed to deploy NF - Note right of SMF: 3.2 Clean Up resources - Note right of IMS: Clean up all resources allocated to deploy the NF - end - end - alt Successful fulfilment of the request - Note right of IMS: 4 Successful fulfilment of request - else Exception: Failed to fulfill request - Note right of SMF: 5 Clean Up resources - Note right of IMS: Clean up all networking resources including VLAN ID - end - Note right of SMF: End Create Slice Request - -``` - -UML sequence diagram for Network Slice Creation. Lifelines: Service Management & Orchestration Framework (NSSMF, FOCOM, NFO) and O-Cloud Platform (IMS, DMS). The process involves a 'Create Slice Request' followed by VLAN ID allocation, optional gateway connectivity, optional NF deployment, and final resource cleanup or success confirmation. - -Figure 3-60: Network Slice Creation - -### 3.10.2 Network Slice Deletion Use Case - -#### 3.10.2.1 High Level Description - -This use case supports the deletion of the network slice. - -When RAN NSSMF deletes a slice subnet, the Network Function instances associated with the slice may need to be terminated as well. Depending upon the deployment scenario (e.g., shared network functions vs. non shared), RAN NSSMF makes decision if NF needs to be terminated or not. RAN NSSMF sends request to NFO to terminate appropriate NFs. - -A VLAN ID associated with the slice is deallocated (both at O-Cloud Site Network Fabric as well as O-Cloud Node Cluster Network level) so that O-Cloud could reuse the VLAN ID for further use. - -#### 3.10.2.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------| -| Goal | Deletion of slice subnet instance in O-Cloud or a site in a distributed O-Cloud | | -| Actors and Roles | RAN NSSMF – Manages network slice subnet management.
SMO/FOCOM/IMS – Federated O-Cloud Orchestration and Management
NFO/DMS – To terminate NFs, if needed | | -| Assumptions |
  1. 1. RAN NSSMF function is available and drives the deletion of network slice subnet instance
  2. 2. RAN NSSMF uses FOCOM to communicate with IMS, and it interacts NFO to trigger the NF management with DMS
  3. 3. If network slice spans multiple O-Clouds (or sites in a distributed O-Cloud) within RAN domain, below use case request is executed for each O-Cloud or sites.
  4. 4. RAN NSSMF may, but need not, trigger the termination of NFs
| | -| Preconditions |
  1. 1. SMO is available
  2. 2. IMS and DMS are available
| | -| Begins when | RAN NSSMF starts the deletion of an instance of O-NSSI | | -| Step 1 (O) | If NF need to be terminated as part of the deletion of slice subnet instance:
SMO/ NFO sends request to O-Cloud via O2dms interface to terminate NFs
Execute the “Terminate Network Function on O-Cloud” Use Case | Terminate NF use case [3.2.5] | -| Step 2 (M) | SMO/FOCOM sends a request to O-Cloud over O2ims to deallocate the VLAN ID associated with the slice | VLAN Deallocation Use case [3.9.2] | -| Step 3 (O) | If slice spans across multiple O-Clouds, FOCOM sends request to IMS to remove the connectivity of the NFs associated with the slice from the O-Cloud Gateway. | | -| Step 4(M) | The response is returned | | -| Exceptions | Slice deletion fails | | -| Post Conditions | None | | -| Traceability | REQ-ORC-GEN25, REQ-ORC-GEN26, REQ-ORC-GEN27, REQ-ORC-GEN28, REQ-ORC-O2-46, REQ-ORC-O2-64, REQ-ORC-O2-65 | | - -#### 3.10.2.3 UML sequence diagram - -![UML sequence diagram for Network Slice Deletion. Lifelines: Service Management & Orchestration Framework (NSSMF, FOCOM, NFO) and O-Cloud Platform (IMS, DMS). The process involves sending a Delete Slice Request, optionally terminating Network Functions, deallocating VLAN IDs, removing gateway connectivity, and finally ending the request with a successful fulfillment or exception handling.](909e1cd5419742a8ea8a95a16a40d849_img.jpg) - -``` - -sequenceDiagram - participant SMF as NSSMF - participant FOCOM as FOCOM - participant NFO as NFO - participant IMS as IMS - participant DMS as DMS - - Note left of SMF: Service Management & Orchestration Framework - Note right of IMS: O-Cloud Platform (IMS/DMS) - - SMF->>IMS: Delete Slice Request - opt If Network Function instance need to be terminated - SMF->>IMS: 1 Terminate Network Function (NF) Request - Note right of IMS: Execute Terminate Network Function procedure - alt Successful fulfilment of the request - IMS-->>SMF: 1.1 successful termination of NF - else Exception: Failed to terminate NF - end - end - SMF->>IMS: 2 Deallocation of VLAN ID Request associated with Slice - Note right of IMS: Execute the VLAN ID Deallocation procedure - opt If VLAN ID needs to be removed from the trunk port - Note right of IMS: Remove the VLAN ID from trunk port of NF - end - opt If Slice spans multiple O-Clouds - SMF->>IMS: 3 O-Cloud Gateway connectivity removal request - Note right of IMS: Remove network connectivity from the O-Cloud Gateway - end - alt Successful fulfilment of the request - IMS-->>SMF: 4 Successful fulfilment of request - else Exception: Failed to fulfill request - end - SMF->>IMS: End Delete Slice Request - Note left of SMF: Service Management & Orchestration Framework - Note right of IMS: O-Cloud Platform (IMS/DMS) - -``` - -UML sequence diagram for Network Slice Deletion. Lifelines: Service Management & Orchestration Framework (NSSMF, FOCOM, NFO) and O-Cloud Platform (IMS, DMS). The process involves sending a Delete Slice Request, optionally terminating Network Functions, deallocating VLAN IDs, removing gateway connectivity, and finally ending the request with a successful fulfillment or exception handling. - -Figure 3-61: Network Slice Deletion - -## 3.11 Provisioning Use Cases - -### 3.11.1 Network Resource Provisioning for base O-Cloud Site Network Use Case - -#### 3.11.1.1 High level description - -This use case describes the procedure for SMO to provision the base O-Cloud Site Network, realized on the O-Cloud Site Network Fabric, which provides infrastructure-level network connectivity within the O-Cloud Site and enables connectivity among O-Cloud Nodes and with the O-Cloud Site Gateway, which can be connected to transport networks outside of the O-Cloud Site. - -NOTE 1: The provisioning of the base O-Cloud Site Network results in the creation of the O-Cloud Site Network enabling the network connectivity referenced above. Additional O-Cloud Site Networks can be provisioned by additional provisioning procedures to fulfill other requirements of connectivity, e.g., O-Cloud Site Networks used as O-Cloud Node Cluster Networks, which are described in other use cases. - -NOTE 2: Even though the use case describes a single base O-Cloud Site Network, it is not limited that multiple O-Cloud Site Networks can be provisioned. - -This procedure can be invoked independently to the existing O-Cloud Basic Use Case specified in clause 3.1. - -#### 3.11.1.2 Sequence description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Network resource provisioning for the O-Cloud Site Network enabling O-Cloud Nodes to be interconnected as well as with transport networks via O-Cloud Site Gateway. | | -| Actors and Roles | SMO: FOCOM
IMS
Network Operator | | -| Assumptions | Network resources of the O-Cloud Site Network Fabric have not been provisioned for base O-Cloud Site Network. | | -| Preconditions | 1) SMO and IMS are available.
2) Network connectivity exists between the O-Cloud and SMO.
3) The compute systems for the O-Cloud Nodes and the O-Cloud Network Fabric are physically interconnected (i.e., cables are wired). | | -| Begins when | Network operator decides to provision O-Cloud Site Network to enable O-Cloud Site Network Fabric resources for the base O-Cloud Site Network. | | -| Step 1 (M) | SMO sends a request to the IMS using O2ims services to provision the O-Cloud Site network to enable O-Cloud Site Network Fabric resources for the base O-Cloud Site Network, which enables network connectivity among O-Clouds Nodes. | | -| Step 2 (M) | IMS sends a response to the SMO to inform that the request is accepted and it starts provisioning. IMS performs the O-Cloud Site Network Fabric resource provisioning for the base O-Cloud Site Network to the O-Cloud Node and if necessary, set specific L2 level configuration on the O-Cloud Site Network Fabric and O-Cloud Site Gateway for L3 level as well. (NOTE) | | -| Step 3 (M) | IMS informs the SMO of the success or failure of the network provisioning request. | | -| Ends when | Network resources for the base O-Cloud Site Network are provisioned. | | -| Exceptions | None identified. | | -| Post Conditions | Network resources for the base O-Cloud Site Network have been provisioned and network connectivity has been established between O-Cloud Nodes and with transport network via O-Cloud Site Gateway. | | -| Traceability | REQ-ORC-02-45, REQ-ORC-02-46 | | -| NOTE: | Network resource provisioning for the base O-Cloud Site Network can be also performed, e.g., during O-Cloud Platform Software Installation Use Case described in clause 3.1.2. | | - -#### 3.11.1.3 UML sequence diagram - -![Sequence diagram for Network Resource Provisioning for base O-Cloud Site Network. Lifelines: Personnel (Network Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud (IMS). The process involves three steps: 1. Request provisioning of base O-Cloud Site NW on O-Cloud Site NW Fabric resources; 2. Request accepted and informing start of provisioning; 3. Networking provisioning complete. A note indicates that IMS performs the provisioning to enable O-Cloud Site Network Fabric resources and necessary configuration on the O-Cloud Site Network Fabric and O-Cloud Site Gateway.](16c8aea7b68120358abcb5ef6ef3ae0b_img.jpg) - -``` - -sequenceDiagram - participant Personnel as Network Operator - participant FOCOM as Service Management & Orchestration Framework - participant IMS as O-Cloud - - Note right of FOCOM: O-Cloud Site Network Fabric resource provisioning for base O-Cloud Site Network - - FOCOM->>IMS: 1 Request provisioning of base O-Cloud Site NW on O-Cloud Site NW Fabric resources - IMS-->>FOCOM: 2 Request accepted and informing start of provisioning - Note right of IMS: IMS performs the O-Cloud Site Network provisioning to enable O-Cloud Site Network Fabric resources for the base O-Cloud Site Network and if necessary, specific configuration on the O-Cloud Site Network Fabric and O-Cloud Site Gateway. - IMS-->>FOCOM: 3 Networking provisioning complete - - Note right of FOCOM: End O-Cloud Site Network Fabric resource provisioning for base O-Cloud Site Network Use Case - -``` - -Sequence diagram for Network Resource Provisioning for base O-Cloud Site Network. Lifelines: Personnel (Network Operator), Service Management & Orchestration Framework (FOCOM), and O-Cloud (IMS). The process involves three steps: 1. Request provisioning of base O-Cloud Site NW on O-Cloud Site NW Fabric resources; 2. Request accepted and informing start of provisioning; 3. Networking provisioning complete. A note indicates that IMS performs the provisioning to enable O-Cloud Site Network Fabric resources and necessary configuration on the O-Cloud Site Network Fabric and O-Cloud Site Gateway. - -Figure 3-62: Network Resource Provisioning for base O-Cloud Site Network - -### 3.11.2 Create O-Cloud Node Cluster Use Cases - -#### 3.11.2.1 General - -There are two methods for creating an O-Cloud Node Cluster. The first use case focuses on create a Kubernetes (K8s) Cluster and is tailored to establish a containerized K8s environment. The second use case leverages an Managed Infrastructure Template, which uses a declarative approach. The Managed Infrastructure Template specifies the desired state and target configuration for the O-Cloud, ensuring that the necessary computing, storage, and network resources are allocated to form the O-Cloud Node Cluster. The resulting O-Cloud Node Cluster can be of any type, such as Kubernetes (K8s), bare metal, virtual machines or other configurations. - -#### 3.11.2.2 Create Kubernetes (K8s) Cluster - -#### 3.11.2.2.1 High level description - -This use case describes the processing of a request to create a single Kubernetes (K8s) Cluster from the FOCOM towards the IMS at the O-Cloud. The use case aims to assign a suitable set of computer systems, storage resources and network connectivity as a basis for a K8s Cluster, to establish a K8s Cluster in the O-Cloud and to inform the requesting entity what has been created. Before this use case is started it is expected that SMO has concluded that a new K8s Cluster needs to be created in a specific O-Cloud. When the use case is concluded, any modified O-Cloud (exposed) Resources are updated in the O-Cloud Inventory model. - -NOTE: A Kubernetes (K8s) Cluster is an example of O-Cloud Node Cluster supporting container infrastructure services. - -##### 3.11.2.2.2 Sequence description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Create Kubernetes (K8s) Cluster | | -| Goal | The goals of this use case are to:
1. Assign suitable computer systems, storage resources, and networking connectivity as a basis for a new K8s Cluster. | | - -| | | | -|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |
  1. 2. Establish a new K8s Cluster in the O-Cloud.
  2. 3. Inform the requestor (normally FOCOM) that the K8s Cluster deployment management applications are operational and communicate the DMS Endpoint associated to the new K8s Cluster. (NOTE 1)
| | -| Actors and Roles |

Service Management Orchestrator (SMO) – The SMO provides the “requirements” and needs for CNFs, and the K8s Cluster to be created. FOCOM is the endpoint for O2ims at the SMO as a client to IMS in the O-Cloud.

Infrastructure Management Services (IMS) – The IMS Provisions Abstracted Resources. The IMS functionality in the O-Cloud is the manager side of the endpoint for FOCOM.

| | -| Assumptions |

The following assumptions are relevant to this use case:

  1. 1. Bare Metal infrastructure – It is assumed that O-Cloud Resources form a bare metal hardware infrastructure that will be used by the K8s Cluster.
  2. 2. O-Cloud Site Network Fabric – The O-Cloud Site Network enabling connectivity among O-Cloud Nodes is established and available.
  3. 3. O-Cloud exists – The O-Cloud is running and has undergone genesis.
  4. 4. External Storage Resources – External storage resources are available so that K8s Clusters can be connected to the external storage resource.
| | -| Preconditions |

The following preconditions are used by this use case:

  1. 1. Bare Metal deployed – The deployment of the hardware infrastructure layer has been successfully performed. This is done either as operator on-premises cloud resources or made available from a Cloud Provider. The hardware infrastructure layer includes O-Cloud internal resources such as computer systems, network resources, and storage resources.
  2. 2. IMS operational – The IMS services in the O-Cloud are active and operational. For the IMS to be running, it is assumed that the O-Cloud is configured, active and in a running state.
  3. 3. Connectivity & Authorized – The O-Cloud has connectivity and authorization allowing communication with the SMO.
| | -| Begins when | This use case begins when there is a request to create a K8s Cluster. | | -| Step 1 (M) |

REQUEST TO CREATE KUBERNETES (K8s) CLUSTER –

A request to create new Kubernetes (K8s) Cluster is sent from FOCOM to IMS with the Cluster ID. The request can contain or reference a Cluster Template, which describes the declarative target for the O-Cloud Node Cluster. At the IMS, the (O-Cloud internal) resources are booked for the new K8s Cluster. The IMS marks the resources as booked for new K8s Cluster with the Cluster ID. (NOTE 2) (NOTE 3)

The request from the SMO (FOCOM) for a new K8s Cluster on an O-Cloud Site near a Location from the O-Cloud (IMS Provisioning Service) provides some of the following input objectives. FOCOM requests a new K8s Cluster in a Location with “X” vCPU performance and “Y” Memory from the IMS Provisioning Service. In addition, the following non-exhaustive list of requirements will be transferred, directly or by reference, to IMS by means of a Cluster Template. The requirements defined in 3 through 7 might need to be repeated per Node Pool Group/Type (Definition of these requirements are FFS).

  1. 1. LOCATION: Kubernetes (K8s) Cluster shall be [On] or [Near] a given geographic Location.
  2. 2. LABELS: K8s Cluster shall have the following Labels (if that is required).
    1. a. Labels can be requested on Cluster and/or NodePool levels
    2. b. Taints – Taints can be applied by IMS at creation to support the DMS to place Pods according to its demands defined by Tolerances. Taints can be considered as a special preconfigured Label. Taints should be possible to be given as requirements by the requestor of a K8s Cluster (or later update) and applied by the IMS logic.
  3. 3. COMPUTE/MEMORY: K8s Cluster shall have at least “X” vCPU as performance and “Y” amount of Memory (CPU RAM).
| | - -| | | | -|----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |
  1. 4. NODES: K8s Cluster shall have a minimum of “Z” nodes (if that is required).
  2. 5. SPECIAL NEEDS: This defines if there are special needs or capabilities for the Host/Node. Some examples of special needs are Host Profiles, Accelerators, and Affinity rules. The special needs are for FFS.
  3. 6. NETWORKING: K8s Cluster and/or its Nodes shall have the following capabilities (some of them also created with the K8s initial creation). (NOTE 4)
    O-Cloud Networking objectives (one or more where applicable) are specified:
    1. a. NIC with I/F Type [Std] or [SR-IOV].
    2. b. External DC-GW (N-S) connectivity [Port, Encapsulation-method and Traffic Type Identifier] (e.g. VLAN ID on a Port).
    3. c. K8s Cluster Nodes (as O-Cloud Nodes) shall be transparently connected as [Pod Access I/F] or [Pod Trunk I/F].
    4. d. O-Cloud Internal (E-W) Inter-Cluster network (never leaves the O-Cloud).
    5. e. O-Cloud Site Internal (E-W) Inter-Cluster network (never leaves the O-Cloud Site).
    6. f. K8s Cluster (E-W) Intra-Cluster network (never leaves the Cluster).
    7. g. Minimum requirement on its Network Attachment Definition in the K8s Cluster.
  4. 7. STORAGE: K8s Cluster and/or its Nodes shall have the following capabilities (some of them also created with the K8s initial creation) for O-Cloud Storage objectives (one or more where applicable) are specified:
    1. a. Capacity – How much storage is needed.
    2. b. Storage Classes – This indicates factors for the storage offered. Abstracts underlying implementation detail. Storage Classes definitions/categories will be FFS.
    3. c. Persistency –If storage is requested to be of a persistent storage type it implies that the storage data will survive restarts.
    4. d. Dynamic creation supported_ – This indicates if dynamic creation of storage is supported or whether the storage is statically allocated.
    5. e. Redundancy_ – Indicates if the storage is redundant.
  5. 8. K8s VERSION: K8s Cluster shall have a specific [Version].
  6. 9. CLUSTER/DEPLOYMENT TYPE: Some expected cluster types will be FFS. (if that is required) (Type can be Native K8s...). Based on deployment model. The deployment type and cluster type will be FFS. For instance, high-availability, redundancy, topology, and resiliency requirements of the cluster are FFS.
  7. 10. USER CREDENTIALS: The Create K8s Cluster request has User Credentials. Security Policies are executed. (NOTE 5)
| | -|

Step 2 (ALT)

|

O-CLOUD PROCESSING OF THE CREATE -

The following things happen within the O-Cloud if suitable resources are found:

  • • The IMS creates a new Kubernetes (K8s) Cluster ID.
  • • The IMS books resources in the O-Cloud for the new Kubernetes (K8s) Cluster.
  • • The IMS marks the resources as booked for the new Kubernetes (K8s) Cluster ID.
  • • The IMS creates the Kubernetes (K8s) Cluster by allocating the required O-Cloud Resources.
  • • The IMS starts the Kubernetes (K8s) Cluster and configures the requested cluster-wide services including CRDs, CNIs, CSIs, and Network Interface Connection Points. (NOTE 6)
  • • Required Kubernetes K8s Operators get created. These operators are created based on input requirements from Step 1. There could be different operators for other operations, for example, "networking".
  • • Native Kubernetes microservices are spawned and given associated namespaces.
  • • Platform service(s) are installed with a namespace that is provided by the platform service package or overridden by the cluster lifecycle manager. A platform service package is a bundle of service(s) that provide an application with specific service(s). However, these platform service(s) are not contained in the deployment of the application. The platform service(s)
| | - -| | | | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

might be exposed as a capability of the K8s Cluster on which a package is installed. (NOTE 7) (NOTE 8)

  • • Requested initial pre-provisioned configurations are set. For example, the initial Network Attachment Definitions (NAD).
  • • A DMS user and/or credentials with limited and authorized privileges and permissions as per agreed security policies (FFS) is added.
  • • The IMS assigns the DMS user credentials to the K8s Cluster. This means that the DMS is created and/or associated with the K8s Cluster. (NOTE 9)

RESPONSE TO CREATE KUBERNETES (K8s) CLUSTER –

After the above happens, the IMS responds to the create Kubernetes (K8s) Cluster request with the DMS end point and Kubernetes (K8s) Cluster ID. The O-Cloud (exposed) Inventory is also updated to reflect any changes in the use of O-Cloud Resources. (NOTE 10)

| | -| Step 3 (ALT) | EXCEPTION: RESPONSE TO INSUFFICIENT RESOURCES FOUND – There were insufficient resources to be able to create the requested Kubernetes (K8s) Cluster. In this case, the IMS responds to the request that there are insufficient suitable resources. IMS cleans up all internal actions for this request. (NOTE 11) (NOTE 12) | | -| Step 4 (ALT) | EXCEPTION: RESPONSE TO MALFORMED REQUEST – The request had an incorrect format and was not understood by the IMS. An unsuccessful create request is returned to the requestor. The request was non-sensical or the parameters comprising the request do not make sense. IMS cleans up all internal actions for this request. (NOTE 13) | | -| Ends when | This use case ends when the Kubernetes (K8s) Cluster is created, or the use case has encountered an exception. | | -| Exceptions |

INSUFFICIENT RESOURCES – If there are insufficient resources to fulfill the request. The request to create a Kubernetes Cluster cannot be performed.

MALFORMED REQUEST – The request had an incorrect format and could not be processed by the IMS. The request to create a Kubernetes Cluster is rejected.

| | -| Post-conditions |

SUCCESS: There is a new provisioned K8s Cluster with a K8s Cluster ID.

There are provisioned resources for the new K8s Cluster.

The requested O-Cloud networking and connectivity to support the K8s Cluster has been established.

The O-Cloud (exposed) Inventory is updated with the with newly created K8s Cluster as a Resource instance of a specific Resource Type. Resource Type is FFS.

FAILURE: The state of the O-Cloud and IMS is in the same state as before the request arrived: no resources are booked, and no IDs are assigned.

| | -| Traceability | REQ-ORC-O2-47, REQ-ORC-O2-48, REQ-ORC-O2-49 | | -|

NOTE 1: The intent is to hide all O-Cloud internal implementation specific actions that the IMS implementations need to do to create the requested K8s Cluster. The O-Cloud internally will search for and book usable O-Cloud internal resources (whose exposure to the SMO depends on the resource view and inventories resources exposed by the IMS) to create a new K8s Cluster that satisfies the request.

NOTE 2: Within this use case, the term “booked resource” is a resource that has been reserved internal to the O-Cloud. As compared to an allocated resource which is a term that describes a booked resource that is externally exposed.

NOTE 3: The create K8s Cluster request only exposes Worker nodes. The IMS internally manages supporting nodes (e.g. Control Plane nodes) which are not exposed.

| | | - -- NOTE 4: the following traffic requirements relate to Primary Networks and Secondary Networks. However, the expression of these is FFS. -- NOTE 5: These user credentials are later used to authorize the user to have access to or use the created K8s Cluster based on their role privilege (DMS privileges). -- NOTE 6: The management and configuration of “Cloud Provider Controllers” is FFS. -- NOTE 7: An application here is any type of software that consume the platform service(s). -- NOTE 8: The scope of the platform services can be within a namespace or cluster-wide. -- NOTE 9: The DMS user credentials will allow workload placement later onto the K8s Cluster. DMS is not the K8s control plane, just a slice of the functionality exposed by the K8s control plane. -- NOTE 10: The IMS may indicate that resources are found, booked, and creation will start. Though this will be further defined in the protocol specifications. -- NOTE 11: The IMS “cleans up”, meaning that any internal activities and reservations that occurred in processing the failed request are reversed. -- NOTE 12: if some resources were found that match the request, but insufficient to fully satisfy the request, the IMS will respond insufficient resources found. It is up to the requestor to query and reformulate a new request. -- NOTE 13: The IMS “cleans up” meaning that any internal activities and reservations that occurred in processing the failed request are reversed. - -3.11.2.2.3 UML sequence diagram - -![UML sequence diagram for 'Create Kubernetes (K8s) Cluster' use case. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The diagram shows the interaction between FOCOM and IMS to create a new K8s cluster, including prerequisites, resource search, cluster creation steps, and exception handling for insufficient resources or malformed requests.](55a415876cf7b7c2509c0318bb857efa_img.jpg) - -``` - -sequenceDiagram - participant FOCOM as Service Management & Orchestration Framework (FOCOM) - participant IMS as O-Cloud Platform (IMS) - - Note right of FOCOM: PREREQUISITE: SMO is active, IMS is active and has connectivity to SMO - Note left of FOCOM: Pre-condition: FOCOM decides it needs a new K8s Cluster in a location with X vCPU performance from the IMS Provisioning Service. - - Note over FOCOM, IMS: Create K8s Cluster Use Case - - FOCOM->>IMS: 1 Request new K8s Cluster for DMS User - Note right of IMS: IMS search for suitable resources at locations that fulfills requested requirements. - - alt Success - Note right of IMS: Create new K8s Cluster ID. - Note right of IMS: Book resources and mark them as booked for new K8s Cluster. - Note right of IMS: Create K8s Cluster and establish initially required CRDs, CNIs, CSI, NADs, etc. - Note right of IMS: Create required K8s Cluster Operators - Note right of IMS: Create new K8s Cluster User with limited user privileges and assign DMS User Credentials - IMS-->>FOCOM: 2 Respond to New K8s Cluster Request - Note left of FOCOM: Respond with resources found, creation will start, DMS End Point and K8s Cluster ID - else Exception if Insufficient Resources - Note right of IMS: Insufficient resources to create the K8s Cluster. - IMS-->>FOCOM: 3 Respond with Insufficient Resources - Note right of IMS: "Clean Up". - else Exception Malformed Request - Note right of IMS: IMS evaluates the request, but it has a bad format. - IMS-->>FOCOM: 4 Respond Malformed Request - Note right of IMS: "Clean Up". - end - - Note over FOCOM, IMS: End Create K8s Cluster Use Case - -``` - -UML sequence diagram for 'Create Kubernetes (K8s) Cluster' use case. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The diagram shows the interaction between FOCOM and IMS to create a new K8s cluster, including prerequisites, resource search, cluster creation steps, and exception handling for insufficient resources or malformed requests. - -Figure 3-63: Create Kubernetes (K8s) Cluster - -### 3.11.2.3 Create O-Cloud Node Cluster using Managed Infrastructure Template - -#### 3.11.2.3.1 High Level Description - -This use case describes the processing of a request to create a single O-Cloud Node Cluster using a Managed Infrastructure Template from the SMO (FOCOM) towards the IMS at the O-Cloud. The use case aims to assign a suitable set of computer systems, storage resources and network connectivity as a basis O-Cloud Node Cluster to establish a Node Cluster in the O-Cloud and to inform the requesting entity what has been created. Before this use case is started it is expected that SMO has concluded that a new Node Cluster needs to be created in a specific O-Cloud. When the use case is concluded, the relevant modeled representation of O-Cloud resources are updated with the newly created O-Cloud Node Cluster and its references to other resources. - -#### 3.11.2.3.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Create O-Cloud Node Cluster using Managed Infrastructure Template | | -| Goal |

The goals of this use case are to:

  1. 1. Assign suitable computer systems, storage resources, and networking connectivity as a basis for a new Node Cluster.
  2. 2. Establish a new Node Cluster in the O-Cloud using Managed Infrastructure Template
  3. 3. Inform the requestor (normally FOCOM) that the O-Cloud Node Cluster is operational and communicate the DMS Endpoint associated to the new O-Cloud Node Cluster.

See NOTE 1.

| | -| Actors and Roles |

Service Management Orchestrator (SMO) – The SMO provides the “requirements” and needs for CNFs, and the O-Cloud Node Cluster to be created. FOCOM is the endpoint for O2ims at the SMO as a client to IMS in the O-Cloud.

Infrastructure Management Services (IMS) – The IMS Provisions Abstracted Resources. The IMS functionality in the O-Cloud is the manager side of the endpoint for FOCOM.

| | -| Assumptions |

The following assumptions are relevant to this use case:

  1. 1. Infrastructure – It is assumed that O-Cloud Resources form an infrastructure that will be used by the O-Cloud Node Cluster.
  2. 2. Underlay Network – The underlay network is established and available.
  3. 3. O-Cloud exists – The O-Cloud is running and has undergone genesis.
  4. 4. Storage Resources – storage resources are available so that O-Cloud Node Clusters can be provided with storage resource.
  5. 5. Managed Infrastructure Template – It is assumed that the Managed Infrastructure Template referenced in the Provisioning Request exists in the Managed Infrastructure Template catalog for both SMO and corresponding O-Cloud.
  6. 6. A Provisioning Request shall be capable of creating a Node Cluster based on the Managed Infrastructure Template
  7. 7. The Provisioning Request object may include required or optional input
| | - -| | | | -|-----------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

parameters according to an input data template parameter schema definition in the Managed Infrastructure Template.

  1. 8. The Provisioning Request object is a declarative definition of the reference to a Managed Infrastructure Template and corresponding required or optional parameters.
| | -|

Preconditions

|

The following preconditions are used by this use case:

  1. 1. Infrastructure deployed – The deployment of the infrastructure layer has been successfully performed. This is done either as operator on-premises cloud resources or made available from a Cloud Provider. The infrastructure layer includes O-Cloud internal resources such as computer systems, network resources, and storage resources.
  2. 2. SMO is aware of what parameters if any to be supplied with the request.
  3. 3. IMS operational – The IMS services in the O-Cloud are active and operational. For the IMS to be running, it is assumed that the O-Cloud is configured, active and in a running state.
  4. 4. Connectivity & Authorized – The O-Cloud has connectivity and authorization allowing communication with the SMO.
| | -|

Begins when

|

This use case begins when there is a request to create a O-Cloud Node Cluster.

| | -|

Step 1 (M)

|

REQUEST TO CREATE O-CLOUD NODE CLUSTER –

A Provisioning Request object to create new O-Cloud Node Cluster using a Managed Infrastructure Template is sent from SMO (FOCOM) to IMS. The request contains a reference to a Managed Infrastructure Template in the catalog, which describes the declarative target for the O-Cloud Node Cluster. At the IMS, the (O-Cloud internal) resources are booked for the new O-Cloud Node Cluster.

The Managed Infrastructure Template and provisioning request provide requirements about capacity and capabilities of the O-Cloud Node Cluster related to number of O-Cloud Nodes, compute and storage types and capacities, requirements for the O-Cloud Node Cluster Site Networks, location of the O-Cloud Node Cluster, and other characterizations.

See NOTE 2.

| | -|

Step 2 (ALT)

|

O-CLOUD PROCESSING OF THE PROVISIONING REQUEST OBJECT -

The IMS responds to SMO (FOCOM), confirming that the Provisioning Request object has been created.

The following things happen within the O-Cloud if suitable resources are found:

  • • The IMS creates a new O-Cloud Cluster ID.
  • • The IMS books resources in the O-Cloud for the new Node Cluster.
  • • The IMS marks the resources as booked for the new O-Cloud Cluster ID.
  • • Refer to Step 3-4 for monitoring the status of the Provisioning Request.
  • • The IMS creates the Node Cluster by allocating the required O-Cloud Resources.
  • • The IMS updates the Provisioning Request object status throughout the Node Cluster creation progress.
| | - -| | | | -|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

SUCCESSFUL CREATION OF NODE CLUSTER

After the above happens, the IMS updates the Provisioning Request object with the corresponding successful status.

A new or existing DMS endpoint is associated with the provisioned O-Cloud Node Cluster.

The relevant modeled representation of O-Cloud resources are updated with the newly created O-Cloud Node Cluster and its references to other resources.

See NOTE 3.

| | -| Step 3-4 (PAR) |

The process of creating O-Cloud Node Cluster may take significant time. During this period, SMO could monitor the provisioning status until the creation request is either successfully completed or has failed.

See NOTE 4.

The SMO (FOCOM) begins monitoring the status of the Provisioning Request object:

  • • A Provisioning Request object status request is sent from the SMO (FOCOM) to the IMS.
  • • A response from IMS to SMO (FOCOM) is sent containing the current Provisioning Request object status

EXCEPTION: INSUFFICIENT RESOURCES – There were insufficient resources to be able to create the requested O-Cloud Node Cluster. In this case, the IMS updates the Provisioning Request object that there are insufficient suitable resources. IMS cleans up all internal actions for this request.

EXCEPTION: CREATION FAILED – The creation of a new O-Cloud Node Cluster could not be completed. In this case, the IMS updates the Provisioning Request object that the creation has failed. IMS cleans up all internal actions for this request.

See NOTE 5 and NOTE 6.

| | -| Step 5 (ALT) |

EXCEPTION: MALFORMED REQUEST – The request had an incorrect format and was not understood by the IMS. An unsuccessful Provisioning Request response is returned to the requestor. The request was non-sensical or the parameters comprising the request do not make sense. IMS cleans up all internal actions for this request.

See NOTE 7.

| | -| Ends when |

This use case ends when the O-Cloud Node Cluster is created, or the use case has encountered an exception.

| | -| Exceptions |

INSUFFICIENT RESOURCES – If there are insufficient resources to fulfill the request. The request to create a O-Cloud Node Cluster cannot be performed.

CREATION FAILED – The creation of a new O-Cloud Node Cluster couldn't be completed.

MALFORMED REQUEST – The request had an incorrect format and could not be processed by the IMS. The request to create an O-Cloud Node Cluster is rejected.

| | -| Post-conditions |

SUCCESS: There is a new provisioned O-Cloud Node Cluster with an O-Cloud Cluster ID.

| | - -| | | | -|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

There are provisioned resources for the new O-Cloud Node Cluster.

A new or existing DMS endpoint is associated with the provisioned O-Cloud Node Cluster.

See NOTE 8.

The relevant modeled representation of O-Cloud resources are updated with the newly created O-Cloud Node Cluster and its references to other resources.

FAILURE: The state of the O-Cloud and IMS is in the same state as before the request arrived: no resources are booked, and no IDs are assigned.

| | -| Traceability | REQ-ORC-O2-49, REQ-ORC-O2-107, REQ-ORC-O2-108 | | -| Notes |

NOTE 1: The intent is to hide all O-Cloud internal implementation specific actions that the IMS implementations need to do to create the requested O-Cloud Node Cluster. The O-Cloud internally will search for and book usable O-Cloud internal resources (whose exposure to the SMO depends on the resource view and inventories resources exposed by the IMS) to create a new O-Cloud Node Cluster that satisfies the request.

NOTE 2: Within this use case, the term “booked resource” is a resource that has been reserved internal to the O-Cloud. As compared to an allocated resource which is a term that describes a booked resource that is externally exposed. Provisioning Request

NOTE 3: The IMS may indicate that resources are found, booked, and creation will start by updating the Provisioning Request object. Though this will be further defined in the protocol specifications.

NOTE 4: The IMS may also indicate via a notification to the SMO the successful or failed creation of the O-Cloud Node Cluster.

NOTE 5: The IMS “cleans up”, meaning that any internal activities and reservations that occurred in processing the failed request are reversed.

NOTE 6: If some resources were found that match the request, but insufficient to fully satisfy the request, the IMS will respond insufficient resources found. It is up to the requestor to track the Provisioning Request object and reformulate a new request.

NOTE 7: The IMS “cleans up” meaning that any internal activities and reservations that occurred in processing the failed request are reversed.

NOTE 8: Access to the DMS also requires credentials or access rights to the endpoint.

| | - -3.11.2.3.3 UML Sequence Diagram - -![UML Sequence Diagram for 'Create O-Cloud Node Cluster using Managed Infrastructure Template Use Case'. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The diagram shows the interaction for creating a node cluster, including preconditions, provisioning request, resource booking, status tracking, and various exception handling paths (insufficient resources, creation failed, malformed request).](573293af67ee571aef04bf725fcefbe5_img.jpg) - -**Service Management & Orchestration Framework (FOCOM)** - -**O-Cloud Platform (IMS)** - -**PRE-CONDITION:** -FOCOM decides it needs a new Node Cluster in a specific O-Cloud -Managed Infrastructure Template exists for the associated O-Cloud -SMO populates necessary parameters based on Managed Infrastructure Template schema - -**PREREQUISITE:** -SMO is active, IMS is active and has connectivity to SMO - -**Create O-Cloud Node Cluster using Managed Infrastructure Template Use Case** - -1 Create Provisioning Request - -The Provisioning Request object contains a reference to the Managed Infrastructure Template along with the required parameters - -**alt [Success]** - -Create Provisioning Request Object - -2 Response Provisioning Request Creation - -Create new O-Cloud Cluster ID - -Book resources and mark them as booked for new Node Cluster. - -**par [Control Loop]** - -SMO begins tracking the Provisioning Request object in the IMS - -3 Provisioning Request Object Status - -4 Response Provisioning Request Object Status - -**Exception If Insufficient Resources** - -Insufficient resources to create Node Cluster -Update Provisioning Request Object Status - -The IMS "cleans up" meaning that any internal activities and reservations that occurred in processing the failed request are reversed. - -**Exception Creation Failed** - -Creation of Node Cluster could not be completed -Update Provisioning Request Object Status - -The IMS "cleans up" meaning that any internal activities and reservations that occurred in processing the failed request are reversed. - -Creates Node Cluster according to the referenced Managed Infrastructure Template - -IMS updates the Provisioning Request object with Node Cluster creation progress - -A new or existing DMS endpoint is associated with the provisioned O-Cloud Node Cluster. - -**Exception Malformed Request** - -IMS evaluates the request, but it has a bad format - -5 Respond Malformed Request - -The IMS "cleans up" meaning that any internal activities and reservations that occurred in processing the failed request are reversed. - -**End Create O-Cloud Node Cluster Using Managed Infrastructure Template Use Case** - -UML Sequence Diagram for 'Create O-Cloud Node Cluster using Managed Infrastructure Template Use Case'. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The diagram shows the interaction for creating a node cluster, including preconditions, provisioning request, resource booking, status tracking, and various exception handling paths (insufficient resources, creation failed, malformed request). - -Figure 3-64: Create O-Cloud Node Cluster using Managed Infrastructure Template - -### 3.11.3 Delete O-Cloud Node Cluster Use Cases - -#### 3.11.3.1 Delete Kubernetes (K8s) Cluster Use Case - -##### 3.11.3.1.1 High Level Description - -This use case describes the processing of a request to delete a single Kubernetes (K8s) Cluster from FOCOM to IMS in the O-Cloud. The objective of the operation is to delete a previously created Kubernetes Cluster. This is part of a family of O2 IMS Provisioning operations related to Kubernetes Clusters. - -When the use case is concluded, the specified Kubernetes (K8s) Cluster in the O-Cloud is deleted. Typically, the associated (exposed) O-Cloud Resources are released and updated in the O-Cloud Inventory model. Depending on implementation the O-Cloud Resources may not immediately be released. - -##### 3.11.3.1.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Delete Kubernetes (K8s) Cluster | | -| Goal |

The goals of this use case are to:

  1. 1. Delete an existing K8s Cluster in the O-Cloud.
  2. 2. Release assigned O-Cloud Resources from the K8s Cluster.
  3. 3. Inform the requestor (normally FOCOM) that the K8s Cluster has been deleted.
| | -| Actors and Roles |

Service Management Orchestrator (SMO) – The FOCOM in the SMO is the consumer that will request the deletion of the K8s Cluster.

Infrastructure Management Services (IMS) – The IMS processes the request for the deletion of the K8s Cluster. The O-Cloud IMS functionality acts as a manager for any requesting authorized client.

| | -| Assumptions |

The following assumption is relevant to this use case:

  1. 1. Kubernetes Cluster exists – An existing Kubernetes Cluster has been previously created.
  2. 2. Workload migration – If the user of the cluster would like to migrate any traffic that it is interested in, it is assumed that such traffic has already been migrated away. This should be done at the SMO.
  3. 3. Clean up – It is assumed that the SMO would have deleted the relevant O-RAN NF before the delete cluster request is sent.
| | -| Preconditions |

The following preconditions are used by this use case:

  1. 4. IMS operational – The IMS in the O-Cloud is active and operational. For the IMS to be running, it is assumed that the O-Cloud is configured, active and in a running state.
  2. 5. Connectivity & Authorized – The O-Cloud has connectivity and authorization allowing communication with the SMO.
| | -| Begins when | This use case begins when there is a request to delete a K8s Cluster. | | -| Step 1 (M) |

REQUEST TO DELETE KUBERNETES (K8s) CLUSTER –

A request to delete an existing Kubernetes (K8s) Cluster is sent from FOCOM to IMS with the Cluster ID over the O2 IMS interface.

| | - -| | | | -|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------| -| | NOTE 1: Cluster ID is an O-Cloud unique identity for the specific Cluster to be deleted. Its exact place in the information model and format are FFS. | | -| Step 2 (ALT) |

O-CLOUD PROCESSES THE DELETE K8s CLUSTER -

The following steps are done by the IMS in the O-Cloud to process the K8s Cluster deletion request:

  • • The IMS will gracefully terminate the cluster, release its resources, and update the O-Cloud Resource configurations.
    • ○ If the Cluster is non-responsive, then the IMS performs a forceful delete of the association of the O-Cloud Resources to the cluster and update the configurations.
  • • Delete K8s Cluster ID – The K8s Cluster ID in the request is deleted.
  • • Clean internal resources – The O-Cloud internal resources are cleaned.
  • • Release resources - Typically, the associated (exposed) O-Cloud Resources are released and updated in the O-Cloud Inventory model. Depending on implementation the O-Cloud Resources may not be immediately released.
  • • Inventory updated – The O-Cloud inventory for O-Cloud resources is updated when resources are released.
  • • List of Clusters is updated – The O-Cloud inventory that lists the clusters is updated.
  • • Cluster endpoint deleted – The corresponding Cluster endpoint is deleted.
  • • NOTE 2: There are cases where a deletion request could not be processed properly. For example, a token mismatch where the connections are bad, a CNI (container network interface) connectivity issue, or Kubeconfig error where the registry is not deleted. This may place the K8s cluster in a Terminating or Pending state. In this case, the IMS will get an indication that the K8s termination error is returned.

NOTE 3: When the delete K8s Cluster operation is executed, the nodes in the cluster are not drained before deletion.

NOTE 4: Void

RESPONSE TO DELETE KUBERNETES (K8s) CLUSTER –

After the above happens, the IMS then responds to the delete Kubernetes (K8s) request with the response over the O2 IMS interface. The O-Cloud (exposed) Inventory is also updated to reflect any changes in the use of O-Cloud Resources.

| Note: see also the O-Cloud Inventory Update Use Case | -| Step 3 (ALT) | EXCEPTION: KUBERNETES CLUSTER NOT FOUND – The requested Kubernetes Cluster ID was not found or does not exist in the O-Cloud. | | -| Ends when | This use case ends when the Kubernetes (K8s) Cluster is deleted, or the use case has encountered an exception. | | -| Exceptions | KUBERNETES CLUSTER NOT FOUND – The requested Kubernetes Cluster ID was not found or does not exist in the O-Cloud. | | -| Post-conditions |

SUCCESS: The K8s Cluster with requested K8s Cluster ID has been deleted.

Resources are released for the deleted K8s Cluster.

The requested O-Cloud networking and connectivity to support the K8s Cluster are released.

NOTE 5: if there are any faults in the O-Cloud Resources those should be reported through normal Fault Management Operations.

The O-Cloud (exposed) Inventory is updated reflect the deletion of the K8s Cluster.

| | - -| | | | -|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

When the delete Kubernetes Cluster operation is done, IMS performs the internal clean up and reports resultant updates to O-Cloud inventory and communicate changes for those resources.

FAILURE: The state of the O-Cloud and IMS is in the same state as before the bad request arrived. No Kubernetes Cluster is affected or altered.

| | -| Traceability | Requirement [REQ-ORC-O2-61], [REQ-ORC-O2-62], [REQ-ORC-O2-63] | | - -3.11.3.1.3 UML Sequence Diagram - -![UML Sequence Diagram for Delete Kubernetes (K8s) Cluster Use Case](e1e41cc8c8434891237529fedcbba418_img.jpg) - -``` - -sequenceDiagram - participant FOCOM as Service Management & Orchestration Framework (FOCOM) - participant IMS as O-Cloud Platform (IMS) - - Note over FOCOM, IMS: PREREQUISITE: - SMO is active - IMS is active and has connectivity to SMO - Note over FOCOM: Pre-condition: - Authentication to perform the action - - rect rgb(240, 240, 240) - Note over FOCOM, IMS: Delete K8s Cluster Use Case - FOCOM->>IMS: 1 Request delete K8s Cluster - Note right of IMS: Process delete. - - alt Success - Note right of IMS: Process delete K8s Cluster - Delete K8s Cluster ID - Release resources - Inventory updated - List of Clusters is updated in inventory - IMS-->>FOCOM: 2 Respond to delete K8s Cluster Request - Note left of FOCOM: SMO processes inventory - changes from K8s deletion - else Exception Kubernetes® Cluster Not Found - Note right of IMS: IMS evaluates the request, but the K8s® Cluster was not found. - IMS-->>FOCOM: 3 Respond K8s® Cluster Not Found - Note right of IMS: "Clean Up". - end - Note over FOCOM, IMS: End Delete K8s Cluster Use Case - rect - -``` - -The diagram shows the sequence of interactions for deleting a Kubernetes cluster. It starts with FOCOM sending a delete request to IMS. Under the 'Success' alternative, IMS processes the deletion, updates the inventory, and responds to FOCOM, which then processes the inventory changes. Under the 'Exception' alternative (cluster not found), IMS informs FOCOM and performs a cleanup. - -UML Sequence Diagram for Delete Kubernetes (K8s) Cluster Use Case - -Figure 3-65: Delete Kubernetes (K8s) Cluster - -### 3.11.3.2 Delete O-Cloud Node Cluster Created Using Managed Infrastructure Template Use Case - -#### 3.11.3.2.1 High Level Description - -This use case describes the processing of a request to delete an O-Cloud Node Cluster from FOCOM to IMS in the O-Cloud that was previously created using Managed Infrastructure Template. The objective of the operation is to delete a previously created O-Cloud Node Cluster. This is part of a family of O2 IMS Provisioning operations related to O-Cloud Node Clusters. - -#### 3.11.3.2.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <<Uses>>
Related Use | -|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------| -| Use Case Title | Delete O-Cloud Node Cluster Created Using Managed Infrastructure Template Use Case | | -| Goal |

The goals of this use case are to:

  • • Delete an existing O-Cloud Node Cluster in the O-Cloud.
  • • Release assigned O-Cloud Resources from the O-Cloud Node Cluster.
| | -| Actors and Roles |

Service Management Orchestrator (SMO) – The FOCOM in the SMO is the consumer that will request the deletion of the O-Cloud Node Cluster.

Infrastructure Management Services (IMS) – The IMS processes the request for the deletion of the O-Cloud Node Cluster. The O-Cloud IMS functionality acts as a manager for any requesting authorized client.

| | -| Assumptions |

The following assumption is relevant to this use case:

  1. 1. O-Cloud Node Cluster exists – An existing O-Cloud Node Cluster has been previously created.
  2. 2. Workload migration – if the user of the cluster would like to migrate any traffic that it is interested in, it is assumed that such traffic has already been migrated away. This should be done at the SMO.
  3. 3. Clean up – It is assumed that the SMO would have deleted the relevant O-RAN NF before the delete cluster request is sent
| | -| Preconditions |

The following preconditions are used by this use case:

  • • IMS operational – The IMS in the O-Cloud is active and operational. For the IMS to be running, it is assumed that the O-Cloud is configured, active and in a running state.
  • • Connectivity & Authorized – The O-Cloud has connectivity and authorization allowing communication with the SMO.
| | -| Begins when | This use case begins when there is a request to delete an O-Cloud Node Cluster. | | -| Step 1 (M) |

REQUEST TO DELETE O-CLOUD NODE CLUSTER

A request to delete an existing O-Cloud Node Cluster is sent from FOCOM to IMS to delete an existing Provisioning Request Object.

See NOTE 1.

| | - -| | | | -|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 2 (ALT) |

RESPONSE TO DELETE PROVISIONING REQUEST OBJECT

After the above happens, the IMS then responds to the delete Provisioning Request with the response over the O2 IMS interface.

O-CLOUD PROCESSES THE DELETE PROVISIONING REQUEST

The following steps are done by the IMS in the O-Cloud to process the delete ProvisioningRequest object associated with the O-Cloud Node Cluster

  1. 1. The IMS will gracefully start terminating the O-Cloud Node Cluster, release its resources, and update the O-Cloud Resource configurations.
  2. 2. The ProvisioningRequest object is updated with the status
  3. 3. Clean internal resources – The O-Cloud internal resources are cleaned.
| | -| Step 3-4 (PAR) |

SMO (FOCOM) begins monitoring the status of the Provisioning Request object:

  • • A Provisioning Request object status request is sent from the SMO to the IMS.
  • • A response from IMS to SMO is sent containing the current status of the Delete Provisioning Request status.

EXCEPTION: DELETE FAILED – Delete of the O-Cloud Node Cluster could not be completed. The Provisioning Request object is updated with an error status. IMS cleans up all internal action for this request.

| | -| Ends when |

This use case ends when the O-Cloud Node Cluster is deprovisioned and deleted and IMS deletes the Provisioning Request Object associated with the O-Cloud Node Cluster.

| | -| Exceptions |

MALFORMED REQUEST - The request had an incorrect format and could not be processed by the IMS. The request to delete the Provisioning Request Object is rejected.

| | -| Post-conditions |

SUCCESS: The O-Cloud Node Cluster is deprovisioned and Provisioning Request object is deleted.

FAILURE: The state of the O-Cloud and IMS is in the same state as before one of the exception cases were encountered. No O-Cloud Node Cluster is affected or altered.

Resources are released for the deleted O-Cloud Node Cluster.

See NOTE 2.

The O-Cloud (exposed) Inventory is updated reflect the deletion of the O-Cloud Node Cluster.

When the delete O-Cloud Node Cluster operation is done, IMS performs the internal clean up and reports resultant updates to O-Cloud inventory and communicate changes for those resources.

FAILURE: The state of the O-Cloud and IMS is in the same state as before the bad request arrived. No O-Cloud Node Cluster is affected or altered.

| | -| Traceability |

Requirement [REQ-ORC-O2-61], [REQ-ORC-O2-62], [REQ-ORC-O2-63]

| | -| Notes |

NOTE 1: The Provisioning Request Object identify the specific O-Cloud Node Cluster.

NOTE 2: If there are any faults in the O-Cloud Resources those should be reported through normal Fault Management Operations.

| | - -### 3.11.3.2.3 UML Sequence Diagram - -![UML Sequence Diagram for 'Delete O-Cloud Node Cluster Created Using Managed Infrastructure Template Use Case'. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The sequence starts with a 'Delete Provisioning Request' from FOCOM to IMS. IMS processes the request, starting with tracking the object and then deleting the O-Cloud Node Cluster. A control loop handles the status updates (pending, progressing, fulfilled, deleting, failed). Two exception blocks are shown: 'Exception Delete Failed' where the deletion cannot be completed, and 'Exception Malformed Request' where the request has a bad format. The sequence ends with a 'Respond Malformed Request' from IMS to FOCOM.](351243fd59cdae993f191da9ebb48016_img.jpg) - -``` - -sequenceDiagram - participant FOCOM as Service Management & Orchestration Framework (FOCOM) - participant IMS as O-Cloud Platform (IMS) - - Note over FOCOM, IMS: PREREQUISITE: SMO is active, IMS is active and has connectivity to SMO, O-Cloud Node Cluster exists - Note over FOCOM, IMS: Pre-condition: Provisioning Request object exists for the associated O-Cloud - - rect rgb(240, 240, 240) - Note over FOCOM, IMS: Delete O-Cloud Node Cluster Created Using Managed Infrastructure Template Use Case - FOCOM->>IMS: 1 Delete Provisioning Request - Note right of IMS: Delete Provisioning Request of a ProvisioningRequest object in the IMS - - alt [Delete Provisioning Request accepted] - IMS-->>FOCOM: 2 Response Delete Provisioning Request - Note right of IMS: IMS starts processing the Delete Provisioning Request - Note right of IMS: IMS starts deleting the O-Cloud Node Cluster associated to the Provisioning Request object - - par [Control Loop] - Note left of FOCOM: SMO begins tracking the Provisioning Request Object in the IMS - FOCOM->>IMS: 3 Provisioning Request Object Status - IMS-->>FOCOM: 4 Response Provisioning Request Object Status (pending, progressing, fulfilled, deleting, failed) - end - - opt [Exception Delete Failed] - Note right of IMS: Deletion of O-Cloud Node Cluster could not be completed Update Provisioning Request Object Status as failed - end - - Note right of IMS: O-Cloud Node Cluster is deprovisioned and deleted. Allocated resources are released back to IMS. - Note right of IMS: IMS deletes the Provisioning Request object associated to the O-Cloud Node Cluster - - else [Exception Malformed Request] - Note right of IMS: IMS evaluates the request, but it has a bad format - IMS-->>FOCOM: 5 Respond Malformed Request - end - - Note over FOCOM, IMS: End Delete O-Cloud Node Cluster Created Using Managed Infrastructure Template Use Case - end - -``` - -UML Sequence Diagram for 'Delete O-Cloud Node Cluster Created Using Managed Infrastructure Template Use Case'. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The sequence starts with a 'Delete Provisioning Request' from FOCOM to IMS. IMS processes the request, starting with tracking the object and then deleting the O-Cloud Node Cluster. A control loop handles the status updates (pending, progressing, fulfilled, deleting, failed). Two exception blocks are shown: 'Exception Delete Failed' where the deletion cannot be completed, and 'Exception Malformed Request' where the request has a bad format. The sequence ends with a 'Respond Malformed Request' from IMS to FOCOM. - -Figure 3-66: Delete O-Cloud Node Cluster Created Using Managed Infrastructure Template - -## 3.11.4 Update O-Cloud Node Cluster Use Cases - -### 3.11.4.1 General - -An O-Cloud Node Cluster can be updated by adding or removing O-Cloud Nodes, or by adjusting its capabilities, and one option for doing so is by using a Managed Infrastructure Template with a declarative approach. In this approach, the desired final state of the Node Cluster is specified within the Managed Infrastructure Template. The O-Cloud system automatically determines how to modify the existing resources such as computing, storage, and network capacity to meet the desired state. - -### 3.11.4.2 Update O-Cloud Node Cluster - -#### 3.11.4.2.1 High Level Description - -This use case describes the flow of a request to update a single O-Cloud Node Cluster with O-Cloud Node addition(s) or reduction(s), including adding/removing cluster capabilities. The update request of an O-Cloud Node Cluster originates from FOCOM and is sent towards the IMS within the O-Cloud. The objective of the operation is to update a previously created and configured O-Cloud Node Cluster. This is part of a family of O2 IMS Provisioning operations related to O-Cloud Node Clusters. - -An update of an O-Cloud Node Cluster can also include updates of configuration that are cluster-wide, and updating the capabilities of cluster, e.g., adding support for new types of resources comprising the O-Cloud Nodes or modes of network connectivity. - -NOTE: the operations that are performed during an update may be part of maintenance or management functions. - -When the use case is concluded, the specified O-Cloud Node Cluster in the O-Cloud has been updated. - -A disruption policy is the amount of disruption allowed during the update operation. An update of an O-Cloud Node Cluster is manually initiated or automatically scheduled, planned, or triggered. This deployment-level tolerance for disruption is the number of O-Cloud Nodes that can become simultaneously unavailable during the update. For example, a deployment could be created with a disruption policy of losing up to 2 nodes. In this case, it would be possible to lose 2 nodes and continue while performing the cluster update. Each pod may have its own Disruption policy. The idea is to calculate how many nodes could be updated at a time. - -#### 3.11.4.2.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------| -| Use Case Title | Update O-Cloud Node Cluster | | -| Goal | The goals of this use case are to:
  1. Update a previously created and configured O-Cloud Node Cluster in the O-Cloud by adding or removing O-Cloud Nodes to make the resulting cluster have increased or decreased capacities and/or capabilities for workload deployments.
  2. Accommodate pre-planned upgrades.
  3. Inform the requestor (normally FOCOM) that the O-Cloud Node Cluster has been updated.
  4. Perform this upgrade below the allowed disruption policy.
| 3.1.5
Hardware Infrastructure Scaling of O-Cloud
Post Deployment | -| Actors and Roles | Service Management Orchestrator (SMO) – The FOCOM in the SMO is the consumer that will request for the O-Cloud Node Cluster to be updated.

Infrastructure Management Services (IMS) – The IMS processes the request for an O-Cloud Node Update. | | -| Assumptions | The following assumptions are relevant to this use case:
  1. O-Cloud Node Cluster exists – An existing O-Cloud Node Cluster has been previously created.
  2. Disruption Policy – There is a known disruption policy. The update operation takes place within the limits of the disruption policy. NOTE 1: The Cluster scheduler takes into account the disruption policy depending on a non-critical update operation (add, remove, upgrade a node).
  3. Forced Update – The management system could initiate a forced O-Cloud Node update in critical situations irrespective of a disruption policy. NOTE 2: A forced update could impact the underlying NF SLA objectives within the cluster.
| 3.1.5
Hardware Infrastructure Scaling of O-Cloud
Post Deployment | - -| | | | -|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| -| |

4. Migration – In case of removal of O-Cloud Nodes as part of the update, it is assumed that NFO has migrated relevant workloads (NF deployment units) away from the node that is to be removed so that the procedure could be performed within a disruption policy.

5. Hardware Infrastructure Scaling of an O-Cloud – It is assumed that at some point the Hardware Infrastructure has been installed, thus invoking the Hardware Infrastructure Scaling of an O-Cloud Use case. The Hardware is known for the O-Cloud. NOTE 3: The use case does not preclude that when adding new H/W, at the same time this same new H/W is also added to a cluster.

6. O-Cloud Node Role – When the Update request is received, it is assumed that the Role of the O-Cloud Node to be incorporated is known.

| | -| Preconditions |

The following preconditions are used by this use Case:

  1. 1. IMS operational – The IMS in the O-Cloud is active and operational.
  2. 2. Connectivity & Authorized – The O-Cloud has connectivity and authorization allowing communication with the SMO.
| | -| Begins when | This use case begins when there is a request to Update an O-Cloud Node Cluster. | | -| Step 1 (M) |

REQUEST TO UPDATE O-CLOUD NODE CLUSTER –

A request to update an existing O-Cloud Node Cluster is sent from FOCOM to IMS with the Cluster ID over the O2ims interface. The Request includes the Nodes to remove or the number and types of Nodes to add as well as their other cluster capabilities, for instance, network connectivity modes. The request can contain or reference a Cluster Template, which describes the declarative target for the O-Cloud Node Cluster to be realized with the update.

| | -| Step 2 (M) |

O-CLOUD PROCESSES THE UPDATE O-CLOUD NODE CLUSTER -

The following steps are done by the IMS in the O-Cloud to process the Update O-Cloud Node Cluster request:

  • • Pod/Disruption Check –The IMS checks if the request can be honored with the appropriate disruption level including all relevant resources, for instance network requirements.
  • • Network Feasibility Check – In the case that the update O-Cloud Node Cluster operation adds a node, the IMS performs feasibility checks for network related aspects.
  • • Resource Check – IMS checks the resources associated and the IMS processes the request which is asking for O-Cloud resource additions or reductions.
  • • Mark Roles for Nodes – If Nodes are added through the update operation, they are marked with their roles. NOTE 4: the role marking is FFS.
  • • O-Cloud Node Addition/Removal – The IMS allocates or deallocates an O-Cloud Resource with the intention to start (addition) or stop (removal) using it as an O-Cloud Node.
  • • Inventory Updates – The IMS updates the inventory for the DMS associated with the modified cluster to consider the changes in capabilities and/or capacity for the O-Cloud Node Cluster. If a subscription for notifications has been established, then a notification is sent to the SMO.

NOTE 5: Update of the O-Cloud Node Cluster may also impact workloads deployed from the NFO/DMS.

NOTE 6: Additions and removals of O-Cloud Nodes will result in O-Cloud Node Clusters that have increased or decreased capacities and/or capabilities for workload deployments.

| Note: see also 3.1.4 O-Cloud Inventory Update Use Case | -| Step 3 (M) | CONFIGURATION AND NETWORK RELATED UPDATES PROCESSED | | - -| | | | -|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------| -| | If the update is deemed feasible within disruption policy and with available resources, the configuration or network related impacts are processed. | | -| Step 4 (ALT) | RESPONSE TO UPDATE O-CLOUD NODE CLUSTER –
After the above happens, the IMS then responds to the Update O-Cloud Node request with the response over the O2 IMS interface.
NOTE 7: afterward, the SMO can process the inventory changes from O-Cloud Node Update. See to 3.1.4 O-Cloud Inventory Update Use Case. | 3.1.4 O-Cloud Inventory Update Use Case | -| Step 5 (ALT) | EXCEPTION: O-CLOUD NODE CLUSTER NOT FOUND – The requested O-Cloud Node Cluster ID was not found or does not exist in the O-Cloud.
The Use Case Ends. | | -| Step 6 (ALT) | EXCEPTION: O-CLOUD NODE CLUSTER UNAVAILABLE –
In this case a valid Cluster is found, however the O-Cloud Node cluster is unavailable, busy, or malfunctioning.
The Use Case Ends. | | -| Step 7 (ALT) | EXCEPTION: INSUFFICIENT RESOURCES TO PERFORM OPERATION
The O-Cloud does not have enough resources to perform the Update operation.
The Use Case Ends. | | -| Step 8 (ALT) | EXCEPTION: DISRUPTION POLICY VIOLATION
The O-Cloud cannot honour the disruption policy necessary to perform the update operation. The assumption of performing the operation within the policy was not fulfilled.
The Use Case Ends. | | -| Ends when | This Use Case Ends when a O-Cloud Node Cluster is updated, or the use case has encountered an exception. | | -| Exceptions | O-CLOUD NODE CLUSTER NOT FOUND – The requested O-Cloud Node Cluster ID was not found or does not exist in the O-Cloud.
O-CLOUD NODE CLUSTER UNAVAILABLE – The O-Cloud Node Cluster is unavailable, busy, or malfunctioning.
INSUFFICIENT RESOURCES TO PERFORM OPERATION – There are insufficient resources to perform the Update operation.
DISRUPTION POLICY VIOLATION – The Update operation cannot be performed within the disruption policy. | | -| Post-conditions | SUCCESS: The O-Cloud Node Cluster with requested O-Cloud Node Cluster ID has been updated.
FAILURE: The state of the O-Cloud and IMS is in the same state as before one of the exception cases were encountered. No O-Cloud Node Cluster is affected or altered. | | -| Traceability | [REQ-ORC-O2-91], [REQ-ORC-O2-92], [REQ-ORC-O2-93] | | - -3.11.4.2.3 UML Sequence Diagram - -![UML Sequence Diagram for 'Update O-Cloud Node Cluster' use case. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The diagram shows a request from FOCOM to IMS, followed by internal IMS checks (Disruption policy, Network feasibility, Resource checks, O-Cloud resource addition/removals), and then configuration updates. An 'alt [Success]' block contains a response and inventory update. Subsequent 'Exception' blocks for 'Not Found', 'Unavailable', 'Insufficient Resources', and 'disruption policy violation' show error responses and use case termination. The diagram ends with 'End Update O-Cloud Node Cluster Use Case'.](c0ef0292328b1602e278f6a0b2ee07e0_img.jpg) - -**Service Management & Orchestration Framework** -FOCOM - -**O-Cloud Platform** -IMS - -**PREREQUISITE:** -SMO is active -IMS is active and has connectivity to SMO -Authentication to perform the action - -**Update O-Cloud Node Cluster Use Case** - -1 Request Update O-Cloud Node Cluster - -**IMS Processes Update O-Cloud Node Cluster Operation** - -- Disruption policy check -- Network feasibility check -- Resource checks -- O-Cloud resource addition/removals - -2 - -3 Process Configuration & Network updates - -**alt [Success]** - -4 Respond to Update O-Cloud Node Cluster Request - -SMO processes inventory changes from O-Cloud Node Update - -**[Exception O-Cloud Node Cluster Not Found]** - -IMS evaluates the request, but the O-Cloud Node Cluster was not found. - -5 Respond O-Cloud Node Cluster Not Found - -"Clean Up" - -Use Case Ends - -**[Exception O-Cloud Node Cluster Unavailable]** - -6 Respond O-Cloud Node Cluster Unavailable - -Use Case Ends - -**[Exception Insufficient Resources]** - -7 Respond Insufficient Resources - -Use Case Ends - -**[Exception disruption policy violation]** - -8 Respond disruption policy violation - -Use Case Ends - -**End Update O-Cloud Node Cluster Use Case** - -FOCOM - -IMS - -UML Sequence Diagram for 'Update O-Cloud Node Cluster' use case. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The diagram shows a request from FOCOM to IMS, followed by internal IMS checks (Disruption policy, Network feasibility, Resource checks, O-Cloud resource addition/removals), and then configuration updates. An 'alt [Success]' block contains a response and inventory update. Subsequent 'Exception' blocks for 'Not Found', 'Unavailable', 'Insufficient Resources', and 'disruption policy violation' show error responses and use case termination. The diagram ends with 'End Update O-Cloud Node Cluster Use Case'. - -Figure 3-67: Update O-Cloud Node Cluster - -### 3.11.4.3 Update O-Cloud Node Cluster using Managed Infrastructure Template - -#### 3.11.4.3.1 High level description - -This use case describes the flow of a request to update a single O-Cloud Node Cluster using Managed Infrastructure Template. For example, O-Cloud Node addition(s) or reduction(s), including adding/removing cluster capabilities. The update request of an O-Cloud Node Cluster originates from FOCOM and is sent towards the IMS within the O-Cloud. The objective of the operation is to update a previously created and configured O-Cloud Node Cluster. This is part of a family of O2 IMS Provisioning operations related to O-Cloud Node Clusters. - -An update of an O-Cloud Node Cluster can also include updates of configuration that are cluster-wide, and updating the capabilities of cluster, e.g., adding support for new types of resources comprising the O-Cloud Nodes or modes of network connectivity. See NOTE 1 in clause 3.11.4.3.2. O-Cloud Node Cluster can also be updated to a specified configuration by using any previously created Provisioning Request revision known to SMO; however, a previously used Provisioning Request revision does not guarantee that it can be re-applied again successfully since the O-Cloud state might have changed in the meantime (e.g., amount of available O-Cloud resources has changed). - -When the use case is concluded, the specified O-Cloud Node Cluster in the O-Cloud has been updated. - -#### 3.11.4.3.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Update O-Cloud Node Cluster using Managed Infrastructure Template | | -| Goal |

The goals of this use case are to:

  1. 1. Update a previously created and configured O-Cloud Node Cluster in the O-Cloud using Managed Infrastructure Template by referring to a new Managed Infrastructure Template and/or updated parameters to update the cluster accordingly. The updated cluster may have increased or decreased capabilities and/or capacities for workload deployments.
  2. 2. Inform the requestor (normally FOCOM) that the O-Cloud Node Cluster has been updated.
| | -| Actors and Roles |

Service Management Orchestrator (SMO) – The FOCOM in the SMO is the consumer that will request for the O-Cloud Node Cluster to be updated.

Infrastructure Management Services (IMS) – The IMS processes the request for an O-Cloud Node Update.

| | -| Assumptions |

The following assumption is relevant to this use case:

  1. 1. O-Cloud Node Cluster exists – An existing O-Cloud Node Cluster has been previously created.
| | -| Preconditions |

The following preconditions are used by this use case:

  1. 1. IMS Operational – The IMS in the O-Cloud is active and operational.
  2. 2. Connectivity & Authorized – The O-Cloud has connectivity and authorization allowing communication with the SMO.
| | -| Begins when | This use case begins when the FOCOM determines that an update of an O-Cloud Node Cluster is needed. | | -| Step 1 | The FOCOM sends to the IMS an update provisioning request. The Update Provisioning Request object contains the reference of the Managed Infrastructure Template along with all relevant parameters | | - -| | | | -|-----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 2 (ALT) |

IMS PROCESSES THE UPDATE PROVISIONING REQUEST

The following steps are done by the IMS in the O-Cloud to process the Update Provisioning Request:

  • • Network Feasibility Check – In the case that the update O-Cloud Node Cluster operation adds a node, the IMS performs feasibility checks for network related aspects.
  • • Resource Check – IMS checks the resources associated and the IMS processes the request which is asking for O-Cloud resource additions or reductions.

See NOTE 2.

| | -| Step 3 |

RESPONSE TO UPDATE PROVISIONING REQUEST

After the above happens, the IMS then responds to the Update Provisioning request with a response over the O2 IMS interface back to the SMO (FOCOM).

At this point refer to Step 5-6 for monitoring the Update Provisioning request status.

| | -| Step 4 |

IMS performs updates to O-Cloud Node Cluster based on the request.

O-Cloud Node Addition/Removal – The IMS allocates or deallocates an O-Cloud Resource with the intention to start (addition) or stop (removal) using it as an O-Cloud Node.

See NOTE 3.

| | -| Step 5-6 (PAR) |

SMO (FOCOM) begins monitoring the status of the Provisioning Request object:

  • • A Provisioning Request object status request is sent from the SMO to the IMS.
  • • A response from IMS to SMO is sent containing the current status of the Update Provisioning Request status.

EXCEPTION: INSUFFICIENT RESOURCES - There were insufficient resources to be able to update the requested O-Cloud Node Cluster. In this case, the IMS updates the Provisioning Request object that there are insufficient suitable resources. IMS cleans up all internal actions for this request.

EXCEPTION: UPDATE FAILED – Update of the O-Cloud Node Cluster could not be completed. The Provisioning Request object is updated with an error status. IMS cleans up all internal action for this request.

See NOTE 4.

| | -| Ends when |

This use case ends when an O-Cloud Node Cluster is updated using the Updated Provisioning Request, or the use case has encountered an exception.

| | -| Exceptions |

O-CLOUD NODE CLUSTER NOT FOUND – The requested O-Cloud Node Cluster ID was not found or does not exist in the O-Cloud.

UPDATE FAILED – Update of O-Cloud Node Cluster could not be completed.

INSUFFICIENT RESOURCES TO PERFORM OPERATION – There are insufficient resources to perform the Update operation.

MALFORMED REQUEST - The request had an incorrect format and could not be processed by the IMS. The request to update the Provisioning Request Object is rejected.

See NOTE 5.

| | - -| | | | -|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Post-conditions |

SUCCESS: The O-Cloud Node Cluster with O-Cloud Node Cluster ID has been updated.

FAILURE: The state of the O-Cloud and IMS is in the same state as before one of the exception cases were encountered. No O-Cloud Node Cluster is affected or altered.

| | -| Traceability | [REQ-ORC-02-91], [REQ-ORC-02-92], [REQ-ORC-02-93] | | -| Notes |

NOTE 1: The operations that are performed during an update can be part of maintenance or management functions.

NOTE 2: Update of the O-Cloud Node Cluster can also impact workloads deployed from the NFO/DMS.

NOTE 3: Additions and removals of O-Cloud Nodes will result in O-Cloud Node Clusters that have increased or decreased capacities and/or capabilities for workload deployments.

NOTE 4: The IMS “cleans up” meaning that any internal activities and reservations that occurred in processing the failed request are roll-backed.

NOTE 5: The implementation might encounter more exceptions of what is described in this current use case.

| | - -3.11.4.3.3 UML Sequence Diagram - -![UML Sequence Diagram for 'Update O-Cloud Node Cluster using Managed Infrastructure Template Use Case'. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The diagram shows the interaction for updating a node cluster, including pre-conditions, a control loop for tracking, and several exception handling blocks for insufficient resources, malformed requests, and not found errors.](9f5f9afcedaa0d9b7991976f5000865c_img.jpg) - -**Service Management & Orchestration Framework** (FOCOM) -**O-Cloud Platform** (IMS) - -**PREQUISITE:** -SMO is active, IMS is active and has connectivity to SMO -O-Cloud Node Cluster exists - -**Pre-condition:** -Managed Infrastructure Template exists for the associated O-Cloud - -**Update O-Cloud Node Cluster using Managed Infrastructure Template Use Case** - -1 Update Provisioning Request -The Update Provisioning Request object contains the reference of the Managed Infrastructure Template along with all relevant parameters - -**alt [Success]** - -2 IMS processes the update provisioning request object -3 Response Update Provisioning Request -4 IMS performs the update O-Cloud Node Cluster including resources updates - -**par [Control loop]** -SMO begins tracking the Provisioning Request Object in the IMS - -5 Provisioning Request Object Status -6 Response Provisioning Request Object Status - -**[Exception if insufficient Resources]** -Insufficient resources to create Node Cluster -Update Provisioning Request Object Status -The IMS "cleans up" meaning that any internal activities and reservations that occurred in processing the failed request are roll-backed. - -**[Exception Update Failed]** -Update of Node Cluster could not be completed -Update Provisioning Request Object Status -The IMS "cleans up" meaning that any internal activities and reservations that occurred in processing the failed request are roll-backed. - -Update Node Cluster using new Managed Infrastructure Template version and/or updated parameters -IMS updates the Provisioning Request object with Node Cluster update progress -Node Cluster is updated - -**[Exception Malformed Request]** -IMS evaluates the request, but it has a bad format -7 Respond Malformed Request -The IMS "cleans up" meaning that any internal activities and reservations that occurred in processing the failed request are roll-backed. - -**[Exception O-Cloud Node Cluster Not Found]** -IMS evaluates the request, but the O-Cloud Node Cluster was not found -8 Respond O-Cloud Node Cluster Not Found -The IMS "cleans up" meaning that any internal activities and reservations that occurred in processing the failed request are roll-backed. - -**End Update O-Cloud Node Cluster Using Managed Infrastructure Template Use Case** - -UML Sequence Diagram for 'Update O-Cloud Node Cluster using Managed Infrastructure Template Use Case'. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The diagram shows the interaction for updating a node cluster, including pre-conditions, a control loop for tracking, and several exception handling blocks for insufficient resources, malformed requests, and not found errors. - -Figure 3-68: Update O-Cloud Node Cluster using Managed Infrastructure Template - -### 3.11.5 Provisioning of Infrastructure Resources using Managed Infrastructure Template - -#### 3.11.5.1 General - -This section describes the management and LCM use cases for managed Infrastructure Resources, using Managed Infrastructure Template . The Managed Infrastructure Template concept, as described in GA&P section 3.4.3.8, can be used to specify a declarative target for the desired state of a set of Infrastructure Resources, represented by a provisioning request sent from SMO to IMS. - -Examples of Infrastructure Resources to which Managed Infrastructure Template based provisioning can be applied are site networks, gateways and attachment circuits. - -#### 3.11.5.2 Create Infrastructure Resources using Managed Infrastructure Template Use Case - -##### 3.11.5.2.1 High Level Description - -This use case describes the processing of a request to create a set of managed O-Cloud Infrastructure Resources based of a referenced declarative target of a Managed Infrastructure Template, sent from the SMO (FOCOM) towards IMS at O-Cloud. This use case aims to assign and configure a suitable set of O-Cloud Resources as the basis for the O-Cloud Infrastructure Resources and to enable the requestor to monitor the progress and verify that requested declarative target is fulfilled and operational. - -Before this use case is started it is expected that SMO has concluded that specific set of Infrastructure Resources needs to be created in a specific O-Cloud. When the use case is concluded, a set of relevant modeled representations of O-Cloud Infrastructure resources are created and exposed through the O-Cloud Infrastructure Resource objects, with references to its assigned O-Cloud Resources in the inventory. - -##### 3.11.5.2.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Create Infrastructure Resources using Managed Infrastructure Template Use Case | | -| Goal |

The goals of this use case are to:

  1. 1. Create Infrastructure Resources as described by a declarative target represented by the Managed Infrastructure Template and Parameters supplied with the Provisioning Request.
  2. 2. Enable the requestor to monitor the progress and verify that requested declarative target is fulfilled and operational.
  1. 1. See NOTE 1.
| | -| Actors and Roles |

Service Management Orchestrator (SMO) – The SMO provides the “requirements” for the Infrastructure Resources to be created. FOCOM is the endpoint for O2ims at the SMO as a client to IMS in the O-Cloud.

Infrastructure Management Services (IMS) – The IMS Provisions Infrastructure Resources. The IMS functionality in the O-Cloud is the manager side of the endpoint for FOCOM.

| | -| Assumptions |

The following assumptions are relevant to this use case:

  1. 1. O-Cloud exists – The O-Cloud is running and has undergone genesis.
| | - -| | | | -|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |
  1. 2. Network Infrastructure – The Site Network Fabric and Site GW resources are available and operational.
  2. 3. The Provisioning Request referenced Managed Infrastructure Template may include required or optional input parameters.
  3. 4. The Provisioning Request referenced Managed Infrastructure Template and supplied parameters is a declarative definition of the expected Infrastructure Resource targets.
| | -| Preconditions |

The following preconditions are used by this use case:

  1. 1. The Managed Infrastructure Template referenced in the Provisioning Request exists in O-Cloud and corresponding Managed Infrastructure Template information is available to SMO
  2. 2. SMO is aware of what parameters if any to be supplied with the request.
  3. 3. The O-Cloud has connectivity and authorization allowing communication with the SMO.
| | -| Begins when |

This use case begins when there is a request to create a set of O-Cloud Infrastructure Resources.

| | -| Step 1 (M) |

REQUEST TO CREATE O-CLOUD INFRASTRUCTURE RESOURCES -

SMO (FOCOM) sends a request for a new Provisioning Request to be created by the IMS. The request contains a reference to a selected Managed Infrastructure Template, and all supplied mandatory and optional parameters as given by the Managed Infrastructure Template, representing the declarative target of the requested set of O-Cloud Infrastructure Resources.

IMS validates the request with the referenced Managed Infrastructure Template and supplied parameters and creates a new Provisioning Request object upon success.

A created Provisioning Request object is now exposed and can be discovered & accesses by SMO.

| | -| Step 2 |

RESPONSE TO PROVISIONING REQUEST CREATE REQUEST

The IMS then responds to the Provisioning request create request with a response over the O2 IMS interface back to the SMO (FOCOM).

At this point refer to Step 4-5 for monitoring the Update Provisioning request status.

| | -| Step 3 (ALT) |

O-CLOUD PROCESSING OF THE PROVISIONING REQUEST OBJECT -

The following things happen within the O-Cloud if suitable resources are found:

  • • The IMS creates resourceIDs for requested Infrastructure Resources.
  • • The IMS books resources in the O-Cloud for the new Infrastructure Resources.
  • • The IMS marks the internal resources as booked for their respective Infrastructure Resource ID.
  • • Refer to Step 4-5 for monitoring the status of the Provisioning Request.
  • • The IMS updates the Provisioning Request object status throughout the Infrastructure Resource creation progress. (NOTE 2) (NOTE 3)
| | - -| | | | -|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 4-5 (PAR) |

The process of creating managed Infrastructure Resources may take significant time. During this period, SMO could monitor the provisioning status until the creation request is either successfully completed or has failed. (NOTE 4)

The SMO (FOCOM) begins monitoring the status of the Provisioning Request object:

  • • A Provisioning Request object status request is sent from the SMO (FOCOM) to the IMS.
  • • A response from IMS to SMO (FOCOM) is sent containing the current Provisioning Request object status

EXCEPTION: INSUFFICIENT RESOURCES – There were insufficient resources to be able to fulfill Provisioning Request. In this case, the IMS updates the Provisioning Request object that there are insufficient suitable resources and publishes a list of successfully created Infrastructure Resources. A list of individual provisioning status of all Infrastructure Resource requested, including failed ones, is also published with Provisioning Request Status. IMS at O-Cloud continues to attempt acquiring required resources.

EXCEPTION: CREATION FAILED – The creation of a new Infrastructure Resource is not completed due to some internal failure. In this case, the IMS updates the Provisioning Request object that the Infrastructure Resources provisioning has failed and publishes a list of successfully created Infrastructure Resources. A list of individual provisioning status of all Infrastructure Resource requested, including failed ones, is also published with Provisioning Request Status. IMS at O-Cloud bail-out on further processing of the provisioning request until further intervention from consumer (FOCOM) to update or delete the Provisioning Request. (NOTE 5)

| | -| Step 6 (ALT) |

SUCCESSFUL CREATION OF INFRASTRUCTURE RESOURCES

If all Infrastructure Resources requested by the Provisioning Request are created successfully, the IMS updates the Provisioning Request object with the successful status and information on created Infrastructure Resources.

| | -| Step 7 (ALT) |

EXCEPTION: MALFORMED REQUEST – The request had an incorrect format and was not understood by the IMS. An unsuccessful Provisioning Request response is returned to the requestor. The request was non-sensical or the parameters comprising the request are not valid. IMS cleans up all internal actions for this request.

| | -| Ends when |

This use case ends when all requested Infrastructure Resources are created, or the use case execution have encountered an exception where none, or just some of the Infrastructure Resources have been created.

| | -| Exceptions |

INSUFFICIENT RESOURCES – If there are insufficient resources to fulfill the request. The request to create the Infrastructure Resources cannot be performed.

CREATION FAILED – The creation of a new Infrastructure Resource couldn't be completed.

MALFORMED REQUEST – The request had an incorrect format and could not be processed by the IMS. The request to create a managed Infrastructure Resource is rejected.

| | -| Post-conditions |

SUCCESS: There is a set of new provisioned Infrastructure Resources created with corresponding Infrastructure Resource ID.

FAILURE:O-Cloud encounters failure in processing the Provisioning Request and it was possible to create only a subset of Infrastructure Resources requested.

INSUFFICIENT RESOURCE: O-Cloud is experiencing insufficient resources to fulfill the provisioning request. It is possible that a subset of requested Infrastructure is successfully created and remaining are waiting for additional resources to fulfill the request. This situation shall change either on O-Cloud adding additional resources to

| | - -| | | | -|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | fulfill the request or when SMO (FOCOM) updates the provisioning request. (NOTE 6) | | -| Traceability | REQ-ORC-O2-109 | | -| Notes |

NOTE 1: The intent of using Managed Infrastructure Template is to simplify the interactions between consumers and the IMS implementations to create the requested Infrastructure Resources. The O-Cloud internally will search for and book usable O-Cloud internal resources (whose exposure to the SMO depends on the resource view and inventories resources exposed by the IMS), to create new Infrastructure Resources that satisfies the request.

NOTE 2: Within this use case, the term “booked resource” is a resource that has been reserved internal to the O-Cloud. As compared to an allocated resource which is a term that describes a booked resource that is externally exposed.

NOTE 3: The IMS may indicate that resources are found, booked, and creation will start by updating the Provisioning Request object. Though this will be further defined in the protocol specifications.

NOTE 4: The IMS may also indicate via a notification to the SMO the successful or failed creation of managed Infrastructure Resources.

NOTE 5: If some resources were found that match the request, but insufficient to fully satisfy the request, the IMS will respond insufficient resources found. It is up to the requestor to track the Provisioning Request object and reformulate a new request.

NOTE 6: During the processing of a Provisioning Request for a set of Infrastructure Resources, the provisioning status of each individual Infrastructure Resource is published with the Provisioning Request status, in a Resource Provisioning Status list.

| | - -### 3.11.5.2.3 UML Sequence Diagram - -![UML Sequence Diagram for 'Create Infrastructure Resources using Managed Infrastructure Template Use Case'. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The diagram shows the interaction for creating infrastructure resources, including a success path and several exception paths (insufficient resources, creation failed, malformed request).](5f5a8699620b98137f36540ead9912f9_img.jpg) - -**Service Management & Orchestration Framework** (FOCOM) and **O-Cloud Platform** (IMS) lifelines. - -**PREREQUISITE:** SMO is active, IMS is active and has connectivity to SMO - -**Pre-condition:** -FOCOM decides it needs a set of Infrastructure Resources in a specific O-Cloud -A Managed Infrastructure Template exists for provisioning of Infrastructure Resources for the associated O-Cloud -SMO populates necessary parameters based on the parameter schema of the Managed Infrastructure Template - -**Use Case:** Create Infrastructure Resources using Managed Infrastructure Template - -**Sequence of Messages:** - -- 1 Provisioning Request Create request**: FOCOM sends to IMS. Note: The Provisioning Request object contains a reference to the Managed Infrastructure Template along with the required parameters. -- alt [Success]**: - - IMS validates the Provisioning Request data and creates Provisioning Request Object. - - 2 Provisioning Request Create response**: IMS sends to FOCOM. - - IMS processes the create Provisioning Request, creates Infrastructure Resource IDs, and allocates resources (mark them as booked). - - par [Control Loop]**: - - FOCOM begins tracking the Provisioning Request object in the IMS. - - 4 Provisioning Request Read Object Status request**: FOCOM sends to IMS. - - 5 Provisioning Request Read Object Status response**: IMS sends to FOCOM. - - [Provisioning Request processing]**: IMS creates Infrastructure Resources according to the referenced Managed Infrastructure Template and updates the Provisioning Request object with progress. -- [Exception If Insufficient Resources]**: IMS notes insufficient resources, updates the Provisioning Request Object Status, and provides a list of successfully created resources and individual provisioning status. -- [Exception Creation Failed]**: IMS notes creation could not be completed, updates the Provisioning Request Object Status, and provides a list of successfully created resources and individual provisioning status. -- 6 IMS updates ProvisioningRequest phase to FULFILLED**: IMS sends to FOCOM. Note: Provisioning Request Create fulfilled. -- [Exception Malformed Request]**: IMS evaluates the request, finds a bad format, responds with a malformed request, and cleans up internal activities and reservations. - -**End Create Infrastructure Resources Using Managed Infrastructure Template Use Case** - -UML Sequence Diagram for 'Create Infrastructure Resources using Managed Infrastructure Template Use Case'. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The diagram shows the interaction for creating infrastructure resources, including a success path and several exception paths (insufficient resources, creation failed, malformed request). - -Figure 3-69: Create Infrastructure Resources using Managed Infrastructure Template - -### 3.11.5.3 Update Infrastructure Resources using Managed Infrastructure Template - -#### 3.11.5.3.1 High level description - -This use case describes the processing of a request to update a set of Infrastructure Resources previously created using declarative target represented by the Provisioning Request based on a Managed Infrastructure Template. Updates may include Infrastructure Resource addition(s) or reduction(s), and updating resource configurations and capabilities. The update request for the Infrastructure Resources originates from FOCOM and is sent towards the IMS within the O- - -Cloud. The objective of the operation is to update a set of previously created and configured Infrastructure Resources. This is part of a family of O2 IMS Provisioning operations related to managed Infrastructure Resources. - -When the use case is concluded, the specified Infrastructure Resources in the O-Cloud has been updated according to the updated declarative target represented by the Provisioning Request. - -### 3.11.5.3.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Update Infrastructure Resources using Managed Infrastructure Template | | -| Goal |

The goals of this use case are to:

  1. 1. Update a previously created and configured Infrastructure Resources in the O-Cloud using Managed Infrastructure Template by referring to a new Managed Infrastructure Template and/or updated parameters to update infrastructure resources accordingly.
  2. 2. Inform the requestor (normally FOCOM) that the Infrastructure Resources has been updated.
| | -| Actors and Roles |

Service Management Orchestrator (SMO) – The FOCOM in the SMO is the consumer that will request for the managed Infrastructure Resource to be updated.

Infrastructure Management Services (IMS) – The IMS processes the request for managed Infrastructure Resource Update.

| | -| Assumptions |

The following assumption is relevant to this use case:

  1. 1. Infrastructure Resource exists – Infrastructure Resource that is requested to be updated, has been previously created.
| | -| Preconditions |

The following preconditions are used by this use case:

  1. 1. IMS Operational – The IMS in the O-Cloud is active and operational.
  2. 2. Connectivity & Authorization – The O-Cloud has connectivity and authorization allowing communication with the SMO.
| | -| Begins when | This use case begins when the FOCOM determines that an update is needed for a set of previously created Infrastructure Resources. | | -| Step 1 |

REQUEST TO UPDATE O-CLOUD INFRASTRUCTURE RESOURCES -

The FOCOM sends to the IMS a Provisioning Request update request. The updated Provisioning Request object contains the reference of the Managed Infrastructure Template along with all relevant parameters.

| | -| Step 2 |

RESPONSE TO PROVISIONING REQUEST UPDATE REQUEST

IMS validates the request with the referenced Managed Infrastructure Template and supplied parameters and sends a response over the O2 IMS interface back to the SMO (FOCOM).

At this point refer to Step 4 - 5 for monitoring the Update Provisioning request status.

| | -| Step 3 (ALT) |

O-CLOUD PROCESSING OF THE UPDATED PROVISIONING REQUEST OBJECT

The following steps are done by the IMS in the O-Cloud to process the Provisioning Request update request:

  • • Resource Check – IMS checks the resources associated and the IMS processes the request which is asking for O-Cloud resource additions,
| | - -| | | | -|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | reductions or updates.
  • • Infrastructure Resource Update – The IMS performs updates to existing Infrastructure Resources based on the request.
  • • Infrastructure Resource Addition/Removal – The IMS allocates or deallocates an O-Cloud Resource with the intention to start (addition) or stop (removal) using it.
| | -| Step 4-5 (PAR) | SMO (FOCOM) begins monitoring the status of the Provisioning Request object:
  • • A Provisioning Request object status request is sent from the SMO to the IMS.
  • • A response from IMS to SMO is sent containing the current status of the Update Provisioning Request status.

EXCEPTION: INSUFFICIENT RESOURCES – There were insufficient resources to be able to fulfill the update of the Provisioning Request. In this case, the IMS updates the Provisioning Request object that there are insufficient suitable resources and publishes a list of successfully updated Infrastructure Resources. A list of individual provisioning status of all Infrastructure Resource requested, including failed ones, is also published with Provisioning Request Status. IMS at O-Cloud continues to attempt acquiring required resources.

EXCEPTION: UPDATE FAILED – IMS encountered failures in processing of the updated Provisioning Request. In this case the IMS updates the Provisioning Request object that the Infrastructure Resources provisioning has failed and publishes a list of successfully provisioned Infrastructure Resources. A list of individual provisioning status of all Infrastructure Resource requested, including failed ones, is also published with Provisioning Request Status. IMS at O-Cloud bail-out on further processing of the provisioning request until further intervention from consumer SMO (FOCOM). (NOTE1)

| | -| Step 6 (ALT) | SUCCESSFUL PROCESSING OF UPDATE PROVISIONING REQUEST
If all requested Infrastructure Resources requested by the Managed Infrastructure Template are created successfully, the IMS updates the Provisioning Request object with the successful status and information on created Infrastructure Resources. | | -| Step 7 (ALT) | EXCEPTION: MALFORMED REQUEST – The request had an incorrect format and was not understood by the IMS. An unsuccessful Provisioning Request response is returned to the requestor. The request was non-sensical or the parameters comprising the request are not valid. IMS cleans up all internal actions for this request. (NOTE 2) | | -| Ends when | This use case ends when all requested Infrastructure Resources are updated, or the use case execution have encountered an exception where none, or just some of the Infrastructure Resources have been updated. | | -| Exceptions |

UPDATE FAILED – Update of managed Infrastructure Resources as requested by the Provisioning Request could not be completed due to O-Cloud internal failures.

INSUFFICIENT RESOURCES – There are insufficient resources to perform the Update Provisioning Request operation.

MALFORMED REQUEST – The request had an incorrect format and could not be processed by the IMS. The request to update the Provisioning Request Object is rejected. (NOTE 2) (NOTE 3)

| | -| Post-conditions |

SUCCESS: Infrastructure Resources are successfully created, updated or removed as requested by the updated Provisioning Request with corresponding Infrastructure Resource ID has been updated.

FAILURE/PARTIAL SUCCESS: IMS publishes a list of successfully provisioned Infrastructure Resources. A list of individual provisioning status of all Infrastructure Resource requested, including failed ones, is also published with Provisioning

| | - -| | | | -|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | Request Status. (NOTE 3) | | -| Traceability | REQ-ORC-O2-110, REQ-ORC-O2-111 | | -| Notes |

NOTE 1: Update of the Infrastructure Resource can also impact workloads deployed from the NFO/DMS.

NOTE 2: The implementation might encounter more exceptions of what is described in this current use case.

NOTE 3: During the processing of a Provisioning Request for a set of Infrastructure Resources, the provisioning status of each individual Infrastructure Resource is published with the Provisioning Request status in a Resource Provisioning Status list.

| | - -3.11.5.3.3 UML Sequence Diagram - -![UML Sequence Diagram for 'Update Infrastructure Resources using Managed Infrastructure Template Use Case'. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The diagram shows the interaction for updating infrastructure resources, including success, insufficient resources, failed update, and malformed request scenarios.](3d885b841119080a2bcfd603a7afca63_img.jpg) - -**Service Management & Orchestration Framework** (FOCOM) and **O-Cloud Platform** (IMS) lifelines. - -**PREREQUISITE:** SMO is active, IMS is active and has connectivity to SMO. ProvisioningRequest being updated exists. - -**Pre-condition:** Managed Infrastructure Template exists for the associated O-Cloud. - -**Use Case:** Update Infrastructure Resources using Managed Infrastructure Template Use Case. - -**Sequence of Messages:** - -- 1 Provisioning Request update request:** FOCOM sends to IMS. Note: The Update Provisioning Request object contains a reference to the Managed Infrastructure Template along with all relevant parameters. -- alt [Success]:** - - IMS validates the Provisioning Request data and creates a Provisioning Request Object. - - 2 Provisioning Request update response:** IMS sends to FOCOM. - - 3 IMS processes the update ProvisioningRequest:** Internal message in IMS. -- par [Control Loop]:** - - FOCOM begins tracking the Provisioning Request object in the IMS. - - 4 Provisioning Request Read Object Status request:** FOCOM sends to IMS. - - 5 Provisioning Request Read Object Status response:** IMS sends to FOCOM. - - IMS updates the Provisioning Request object with Infrastructure Resource creation progress. -- [Exception if Insufficient Resources]:** - - Insufficient resources to create or update requested Infrastructure Resources. Update Provisioning Request Object Status. - - IMS updates the Provisioning Request object with a list of successfully created Infrastructure Resources and the individual provisioning status of all Infrastructure Resources requested. -- [Exception Update Failed]:** - - Update or create or delete of requested Infrastructure Resources could not be completed. Update Provisioning Request Object Status. - - IMS updates the Provisioning Request object with a list of successfully created Infrastructure Resources and the individual provisioning status of all Infrastructure Resources requested. -- 6 IMS updates Provisioning Request phase to FULFILLED:** Internal message in IMS. Note: Infrastructure Resources are created or updated or deleted as requested by the Provisioning Request. -- [Exception Malformed Request]:** - - IMS evaluates the request, but it has a bad format. - - 7 Respond Malformed Request:** IMS sends to FOCOM. Note: The IMS "cleans up" meaning that any internal activities and reservations that occurred in processing the failed request are reversed. - -**End Update Infrastructure Resources Using Managed Infrastructure Template Use Case** - -UML Sequence Diagram for 'Update Infrastructure Resources using Managed Infrastructure Template Use Case'. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The diagram shows the interaction for updating infrastructure resources, including success, insufficient resources, failed update, and malformed request scenarios. - -Figure 3-70: Update Infrastructure Resources using Managed Infrastructure Template - -### 3.11.6 Networking Infrastructure Provisioning Use Cases - -#### 3.11.6.1 Create Networking Infrastructure across O-Cloud Sites with a Managed Infrastructure Template Use Case - -##### 3.11.6.1.1 High Level Description - -This use case describes the creation of Network Infrastructure related to Node Cluster(s), by following a declarative provisioning approach. A Node Cluster may require several different types of end-to-end Networks across O-Cloud networking segments in one or more O-Cloud Sites, that interconnect Ports of the Site Networks, realized through one or more O-Cloud Site Network Fabric(s) and with O-Cloud Site Gateway(s) attached to Attachment Circuit(s), representing the O-Cloud Site connection to the Transport Network. This applies to networks with both intra and inter O-Cloud Site connectivity. - -![Figure 3-71: Basic connectivity scenarios. A complex diagram showing various network connectivity paths within an O-Cloud environment. It includes O-Cloud Sites, O-Cloud Node Clusters (Local and Distributed), DMS, IMS, and external systems. Numbered arrows (1-5) indicate different connectivity types: 1. Intra-O-Cloud Site Intra-Cluster, 2. Intra-O-Cloud Site Inter-Cluster, 3. Inter-O-Cloud Site Inter-Cluster, 4. Inter-O-Cloud Site Intra-Cluster (Distributed), and 5. External connectivity.](a2abc60c3ed8cd00bc8e6f9a7f4b64f0_img.jpg) - -Figure 3-71: Basic connectivity scenarios. A complex diagram showing various network connectivity paths within an O-Cloud environment. It includes O-Cloud Sites, O-Cloud Node Clusters (Local and Distributed), DMS, IMS, and external systems. Numbered arrows (1-5) indicate different connectivity types: 1. Intra-O-Cloud Site Intra-Cluster, 2. Intra-O-Cloud Site Inter-Cluster, 3. Inter-O-Cloud Site Inter-Cluster, 4. Inter-O-Cloud Site Intra-Cluster (Distributed), and 5. External connectivity. - -Figure 3-71: Basic connectivity scenarios - -**(1) Intra-O-Cloud Site Intra-Cluster connectivity:** This type of connectivity is encapsulated entirely within one O-Cloud Node Cluster that resides at one O-Cloud Site. This connectivity can e.g. be achieved by provisioning Site Networks connecting a set of Nodes within a Node Cluster. - -**(2) Intra-O-Cloud Site Inter-Cluster connectivity:** This type of connectivity is an inter-cluster connectivity that connects to different O-Cloud Node Clusters in the same O-Cloud Site. This connectivity can e.g. be achieved by provisioning Site Networks and/or Gateways that are shared across more than one O-Cloud Node Clusters. - -**(3) Inter-O-Cloud Site Inter-Cluster connectivity:** This type of connectivity is one that connects two or more different O-Cloud Node Clusters within an O-Cloud comprising different O-Cloud Sites. This connectivity can e.g. be achieved by separately provisioning Site Networks and/or Gateways to each O-Cloud Node Clusters residing on different O-Cloud Sites and needed Attachment Circuits for transport connectivity between sites. - -**(4) Inter-O-Cloud Site Intra-Cluster connectivity (Distributed Cluster):** This type of connectivity is one that connects a distributed O-Cloud Node Cluster, i.e., one that spans multiple O-Cloud Sites. This connectivity can e.g. be achieved by provisioning Site Networks in more than one O-Cloud Site, each connecting a set of Nodes in different O-Cloud Sites, belonging to a common Node Cluster, with requested O-Cloud Gateways and needed Attachment Circuits for transport connectivity between sites. - -**(5) External connectivity:** O-Cloud external connectivity is one where a cluster connects towards external system(s) that are outside of the O-Cloud; for example, a network that connects to a O-RU. This connectivity can e.g. be achieved using Site Networks connecting a set of Nodes within a Node Cluster and requested Gateways and needed Attachment Circuits for transport connectivity towards external systems. - -For an NF Deployment to be deployed on O-Cloud Node Clusters, it requires connectivity across O-Cloud networking endpoints, represented by Ports. IMS can establish Site Networks, based on provisioning requests from SMO, that an O-Cloud Node Cluster can use for its NodeClusterSiteNWs using the SiteNetworks specified IP address ranges. When the NF Deployment is instantiated on a O-Cloud Node Cluster, that O-Cloud Node Cluster can then utilize those IP addresses to make the appropriate connections. For example, in the K8s case, the Network Attachment Definitions (NAD) are used to accomplish the mapping between the Ports to the NF Deployment Pod interfaces. - -The purpose of the ‘Create Networking Infrastructure across O-Cloud Sites’ Use Case is to create Infrastructure Resources e.g., Site Network(s), Gateway(s) and/or Attachment Circuit(s) enabling needed connectivity for Node Cluster(s). This use case establishes inter-O-Cloud Site and intra-O-Cloud Site connectivity as requested by one or more Provisioning Request(s) that have their respective declarative target(s) given by a Managed Infrastructure Template reference and a set of parameters. - -Connectivity within an O-Cloud Site is achieved using Site Network(s) and O-Cloud Gateway(s), and the connectivity to transport networks through O-Cloud Gateway(s) and Attachment Circuit(s) are leveraged to achieve inter-O-Cloud Site connectivity. Once Site Network(s) are created, they establish connectivity among the site local O-Cloud Cluster Nodes and to the O-Cloud Gateway(s) through Site Network Fabric(s). The Create Networking Infrastructure across O-Cloud Sites includes the five basic connectivity scenarios described above, that can be combined for specific deployments. Following is an example of a set of possible Provisioning Requests. - -![Figure 3-72: Examples of Networking Infrastructure Provisioning. The diagram shows three provisioning requests (1, 2, 3) being processed by a C2-IMS provider. Request 1 uses MIT 'NF_A_net_infra' to create SiteNetwork 1, 2, Gateway 1, and AC1 for O-Cloud Site 1. Request 2 uses MIT 'Shared_ext_net_infra' to create SiteNetwork 3, Gateway 2, and AC2 for shared connectivity. Request 3 uses MIT 'NF_B_net_infra' to create SiteNetwork 4, 5, Gateways 3, 4, and AC3, 4 for O-Cloud Site 2. The bottom part shows the physical layout with Node Cluster 1 and 2 in O-Cloud Site 1, and Node Cluster 2 in O-Cloud Site 2, all connected to a central O-Cloud and Transport system.](36790164991deef00875cc7875965a92_img.jpg) - -The diagram illustrates the provisioning of networking infrastructure across two O-Cloud Sites (Site 1 and Site 2) via a C2-IMS provider. Three provisioning requests are shown: - -- Provisioning Request 1:** Uses Managed Infrastructure Template (MIT) `NF_A_net_infra`. It creates: - - SiteNetwork 1 (SiteNWFabric X, VLAN A, IP\_pool a.b.c.0/24) - - SiteNetwork 2 (SiteNWFabric X, VLAN B, IP\_pool p.q.r.0/24, gateway interface p.q.r.1) - - Gateway 1 (SiteGW 1, connectedNetworks: -gateway interface: p.q.r.1) - - Attachment Circuit AC1 (Bearer, Segment) -- Provisioning Request 2:** Uses MIT `Shared_ext_net_infra`. It creates: - - SiteNetwork 3 (SiteNWFabric X, VLAN C, IP\_pool x.y.z.0/24, gateway interface x.y.z.1, Shared: true) - - Gateway 2 (SiteGW 1, connectedNetworks: -gateway interface: x.y.z.1) - - Attachment Circuit AC2 (Bearer, Segment) -- Provisioning Request 3:** Uses MIT `NF_B_net_infra`. It creates: - - SiteNetwork 4 (SiteNWFabric X, VLAN D, IP\_pool d.e.f.0/24, gateway interface d.e.f.1) - - SiteNetwork 5 (SiteNWFabric Y, VLAN D, IP\_pool d.e.g.0/24, gateway interface d.e.g.1) - - Gateway 3 (SiteGW 1, connectedNetworks: -gateway interface: d.e.f.1) - - Gateway 4 (SiteGW 2, connectedNetworks: -gateway interface: d.e.g.1) - - Attachment Circuit AC3 (Bearer, Segment) - - Attachment Circuit AC4 (Bearer, Segment) - -The bottom part of the diagram shows the physical layout: - -- O-Cloud Site 1:** Contains Node Cluster 1 and Node Cluster 2. Node Cluster 1 is connected to SiteNetwork 1 and SiteNetwork 2. SiteNetwork 1 connects to Gateway 1 (AC1). SiteNetwork 2 connects to Gateway 2 (AC2). Node Cluster 2 is connected to SiteNetwork 3 and SiteNetwork 4. SiteNetwork 3 connects to Gateway 2 (AC2). SiteNetwork 4 connects to Gateway 3 (AC3). -- O-Cloud Site 2:** Contains Node Cluster 2. It is connected to SiteNetwork 5. SiteNetwork 5 connects to Gateway 4 (AC4). -- All Gateways (Gateway 1, 2, 3, 4) are connected to a central **O-Cloud** and **Transport** system, which is further connected to **External systems**. - -Figure 3-72: Examples of Networking Infrastructure Provisioning. The diagram shows three provisioning requests (1, 2, 3) being processed by a C2-IMS provider. Request 1 uses MIT 'NF\_A\_net\_infra' to create SiteNetwork 1, 2, Gateway 1, and AC1 for O-Cloud Site 1. Request 2 uses MIT 'Shared\_ext\_net\_infra' to create SiteNetwork 3, Gateway 2, and AC2 for shared connectivity. Request 3 uses MIT 'NF\_B\_net\_infra' to create SiteNetwork 4, 5, Gateways 3, 4, and AC3, 4 for O-Cloud Site 2. The bottom part shows the physical layout with Node Cluster 1 and 2 in O-Cloud Site 1, and Node Cluster 2 in O-Cloud Site 2, all connected to a central O-Cloud and Transport system. - -Figure 3-72: Examples of Networking Infrastructure Provisioning - -Above Figure 3.11.6.1-2 depicts an example provisioning of Networking Infrastructure needed for two Node Clusters, using three different Provisioning Requests. - -This example includes provisioning of following end-to-end networks. - -- Provisioning Request 1 using Managed Infrastructure Template `NF_A_net_infra` to create - - - SiteNetwork 1 connecting a set of Nodes of Node Cluster1 (*Intra-O-Cloud Site Intra-Cluster connectivity*) - - SiteNetwork 2, Gateway 1 and Attachment Circuit AC1, providing O-Cloud Site external connectivity to a set of NodeCluster 1 nodes (*External connectivity*) -- Provisioning Request 2 using Managed Infrastructure Template `Shared_ext_net_infra` to create - - - Shared network SiteNetwork 3, Gateway 2 and Attachment Circuit AC2, providing a shared network with external connectivity to NodeCluster 1 and NodeCluster 2 (*Intra-O-Cloud Site Inter-Cluster connectivity*) -- Provisioning Request 3 using Managed Infrastructure Template `NF_B_net_infra` to create - - -- a. SiteNetwork 4, Gateway 3 and Attachment Circuit AC3 in O-Cloud Site 1 and SiteNetwork 5, Gateway 4 and Attachment Circuit AC4 in O-Cloud Site 2, providing end-to-end intra cluster connectivity to Distributed Cluster NodeCluster 2 (*Inter-O-Cloud Site Intra-Cluster connectivity*) - -### 3.11.6.1.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Create networking infrastructure. | | -| Actors and Roles | O-Cloud Operator – The O-Cloud operator is a consumer (or entity) using or interfacing with the SMO (FOCOM).

SMO (FOCOM) – The FOCOM within the SMO is the actor who issues the Create Infrastructure request over the O2ims interface.

IMS – The IMS within the O-Cloud processes the Create Infrastructure request over the O2ims interface. | | -| Assumptions | None. | | -| Preconditions | Attachment Circuit at Edge Transport Network Equipment – The SMO has detected a need for external connection between Node Clusters or Node Cluster(s) to external system(s). The transport network has provisioned the transport side of the Attachment Circuit.

Site Network Fabric – The Site Network Fabric has been provisioned enabling infrastructure-level connectivity between O-Cloud Nodes and O-Cloud Gateway(s).

Connectivity – The SMO is connected to the O-Cloud.

O-Cloud Operational – The O-Cloud is installed, operating, and registered with the SMO.

Privilege – The consumer identification and privileges of a SMO user have been verified to be able to perform O2 operations.

Managed Infrastructure Template – Appropriate O-Cloud Managed Infrastructure Templates are available for the provisioning of required O-Cloud Infrastructure Resources for desired connectivity. | | -| Begins when | The use case begins when an operator at the SMO wishes to establish Networking Infrastructure within and across O-Cloud Sites, as needed by the Node Cluster(s). | | -| Step 1(M) | OPERATOR INITIATES REQUEST –

The O-Cloud Operator initiates Networking Infrastructure Provisioning Request(s). In each request, the operator will specify one or more type of end-to-end network(s) to be created.
Operator may issue multiple such Provisioning Requests representing networking resources, either in context of a Node Cluster, or a set of shared resources that can be utilized by multiple Node Clusters. | | -| Step 2(M) | CREATE NETWORKING INFRASTRUCTURE REQUEST –

In response to Operator's request, FOCOM (SMO) initiates Networking Infrastructure Provisioning Request towards the O-Cloud specifying one or more end-to-end type of networks to be created.

Following different types of end-to-end Networking Infrastructure connection scopes can be set up by Provisioning Request(s):
  • - Intra-O-Cloud Site Intra-Cluster connectivity: This type of connectivity is encapsulated entirely within one O-Cloud Node Cluster that resides at one O-Cloud Site.
  • - Intra-O-Cloud Site Inter-Cluster connectivity: This type of connectivity is an inter-cluster connectivity that connects to different O-Cloud Node Clusters in the same O-Cloud Site.
| | - -| | | | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |
  • - Inter-O-Cloud Site Inter-Cluster connectivity: This type of connectivity is one that connects two or more different O-Cloud Node Clusters within an O-Cloud sitting on different sites.
  • - Inter-O-Cloud Site Intra-Cluster connectivity (Distributed Cluster): This type of connectivity is one that connects a distributed cluster, i.e., an O-Cloud Node Cluster that spans multiple O-Cloud Node Sites.
  • - External connectivity: A transport network where a cluster connects to an external system (outside of the O-Cloud). (NOTE 1)
| | -| Step 3 (ALT) | INTRA-O-CLOUD SITE INTRA-CLUSTER CONNECTIVITY
For Intra-O-Cloud Site Intra-Cluster connectivity the IMS creates connectivity that resides within on O-Cloud Node Cluster within a O-Cloud Site. | | -| Step 4 (ALT) | INTRA-O-CLOUD SITE INTER-CLUSTER CONNECTIVITY
For Intra-O-Cloud Site Inter-Cluster connectivity the IMS creates the inter-cluster connectivity that spans multiple O-Cloud Node Clusters within a O-Cloud Site. (NOTE 1) | | -| Step 5 (ALT) | INTER-O-CLOUD SITE INTER-CLUSTER CONNECTIVITY
For Inter-O-Cloud Site Inter-Cluster connectivity, the IMS creates the inter-cluster connectivity across multiple O-Cloud sites. For connectivity between O-Cloud Sites, for a given bearer, the IMS needs to create the attachment circuit. (NOTE 1) | | -| Step 6 (ALT) | INTER-O-CLOUD SITE INTRA-CLUSTER CONNECTIVITY (Distributed Cluster)
For Inter-O-Cloud Site Intra-Cluster connectivity, the IMS creates the intra-cluster connectivity that is a distributed O-Cloud Node cluster, one that spans multiple O-Cloud sites. For connectivity between O-Cloud Sites, for a given bearer, the IMS needs to create the attachment circuit. | | -| Step 7 (ALT) | EXTERNAL CONNECTIVITY
For connectivity to non-O-Cloud systems through transport networks, for a given bearer the IMS needs to create the attachment circuit. | | -| Step 8 (ALT) | ERROR CASE
An Error has been detected. A failure condition is returned to the FOCOM (SMO) and the Use Case Ends. | | -| Post Conditions | None | | -| Traceability | [REQ-ORC-O2-112], [REQ-ORC-O2-113] | | -| NOTE 1: Inter-O-Cloud Site Inter-Cluster connectivity scenario requires individual Provisioning Requests from the Operator for each Node Cluster. | | | -| NOTE 2: Refer to clause 3.11.2 regarding provisioning of O-Cloud Node Clusters. The provisioning of O-Cloud Node Clusters is performed through other provisioning requests not described in the present use case. | | | - -### 3.11.6.1.3 UML Sequence Diagram - -![UML Sequence Diagram for 'Create Networking Infrastructure across O-Cloud Sites with a Managed Infrastructure Template'.](c9bfcc4c4ef694696c292b03de45d2bb_img.jpg) - -``` -sequenceDiagram - participant Operator as O-Cloud Operator - participant FOCOM as FOCOM (SMO Framework) - participant IMS as IMS (O-Cloud Platform) - - Note over Operator, IMS: Precondition: Attachment Circuit at Edge Transport Network Equipment is available, Site Network Fabric has been provisioned, Connectivity (SMO connected), O-Cloud Operational, Privilege (SMO user is valid), Managed Infrastructure Template available. - - Note left of Operator: Identify each required Networking Infrastructure Request needed - Operator->>FOCOM: 1 Networking Infrastructure Request(s) - Note over FOCOM, IMS: Networking Infrastructure across O-Cloud Sites Create Use Case - - loop for each Networking Infrastructure Request - FOCOM->>IMS: 2 Networking Infrastructure Request - alt Intra-site Intra-Cluster - IMS-->>IMS: 3 Intra-O-Cloud Site Intra-Cluster connectivity - else Intra-O-Cloud Site Inter-Cluster networks - IMS-->>IMS: 4 Intra-O-Cloud Site Inter-Cluster networks - else Inter-O-Cloud Site Intra-Cluster networks (Distributed Cluster) - IMS-->>IMS: 5 Inter-O-Cloud Site Intra-Cluster connectivity - else External connectivity - IMS-->>IMS: 6 connectivity towards External system(s) - end - end - - alt Exception Case - IMS-->>FOCOM: 7 Exception Error - Note over FOCOM: Use Case Ends - end - - IMS->>FOCOM: 8 Networking Infrastructure Response - FOCOM->>Operator: Networking Infrastructure Response - -``` - -UML Sequence Diagram for 'Create Networking Infrastructure across O-Cloud Sites with a Managed Infrastructure Template'. - -Figure 3-73: Create Networking Infrastructure across O-Cloud Sites with a Managed Infrastructure Template - -## 3.11.7 O-Cloud Managed Infrastructure Template Discovery Use Case - -### 3.11.7.1.1 High Level Description - -This use case describes the process for discovering the O-Cloud Managed Infrastructure Templates available within an O-Cloud. The goal is to retrieve all existing Managed Infrastructure Template which the SMO can use to initiate a provisioning request to provision or update an O-Cloud Node Cluster. The use case also outlines the Event Notification pattern triggered by changes (Addition/Deletion) of O-Cloud Managed Infrastructure Template, assuming the SMO has subscribed to receive such events. - -### 3.11.7.1.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <>
Related Use | -|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | O-Cloud Managed Infrastructure Template Discovery Use Case | | -| Goal | The goals of this use case are to:
  • Discover available O-Cloud Managed Infrastructure Template in an O-Cloud.
| | - -| | | | -|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Actors and Roles |

Service Management Orchestrator (SMO) – The FOCOM in the SMO is the consumer that will request the discovery of O-Cloud Managed Infrastructure Template

Infrastructure Management Services (IMS) – The IMS processes the request for the discovery of O-Cloud Managed Infrastructure Template The O-Cloud IMS functionality acts as a manager for any requesting authorized client.

| | -| Assumptions |

The following assumption is relevant to this use case:

  • • O-Cloud Managed Infrastructure Template exists – O-Cloud Managed Infrastructure Template are available in the O-Cloud.
  • • Notification Event Subscription – The SMO is subscribed to event notifications from the IMS. This apply only to the Event Notification pattern.
| | -| Preconditions |

The following preconditions are used by this use case:

1 - IMS Operational – The IMS in the O-Cloud is active and operational, and the O-Cloud is configured, active and in a running state.
2 - Connectivity & Authorized – The O-Cloud has connectivity and authorization allowing communication with the SMO.

| | -| Begins when | This use case begins when there is a request from the FOCOM to discover available O-Cloud Managed Infrastructure Template | | -| Step 1 (M) |

QUERY O-CLOUD Managed Infrastructure Template

A request to query available O-Cloud Managed Infrastructure Template is sent from FOCOM to IMS to retrieve the (potentially filtered) list by e.g. Managed Infrastructure Template name and/or version of available O-Cloud Managed Infrastructure Template

| | -| Step 2 (M) |

RESPONSE TO QUERY O-CLOUD Managed Infrastructure Template

After the above happens, the IMS then responds to the get O-Cloud Managed Infrastructure Template with the list of O-Cloud Managed Infrastructure Template including metadata for identifying each Managed Infrastructure Template and its associated parameters schema.

The SMO can optionally store the discovered list of O-Cloud Managed Infrastructure Template

| | -| Step 3 (Opt) |

QUERY O-CLOUD Managed Infrastructure Template

A request to query details of O-Cloud Managed Infrastructure Template is sent from FOCOM to IMS to retrieve the attributes (e.g. parameter schema and characteristics) of an O-Cloud Managed Infrastructure Template available in the O-Cloud if not earlier retrieved.

| | -| Step 4 (Opt) |

RESPONSE TO QUERY O-CLOUD Managed Infrastructure Template

IMS responds with the attributes (e.g. parameter schema and characteristics) associated to the requested O-Cloud Managed Infrastructure Template. The SMO can optionally store corresponding attributes associated with the O-Cloud Managed Infrastructure Template.

| | -| Step 5 (M) |

In this use case using the Event Notification pattern, IMS notify SMO of changes in the IMS for addition and deletion of O-Cloud Managed Infrastructure Template The notification message includes the information to identify the Managed Infrastructure Template(s)

| | - -| | | | -|------------------------|----------------------------------------------------------------------------------------------------------------------------------------|--| -| Ends when | This use case ends when a response or notification is received by the FOCOM with the available O-Cloud Managed Infrastructure Template | | -| Exceptions | None identified. | | -| Post-conditions | The SMO has discovered the available O-Cloud Managed Infrastructure Template | | -| Traceability | [REQ-ORC-02-114], [REQ-ORC-02-115], [REQ-ORC-02-116] | | - -### 3.11.7.1.3 UML Sequence Diagram - -![UML Sequence Diagram for Discovery O-Cloud Managed Infrastructure Templates. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The sequence includes: 1. Query O-Cloud Managed Infrastructure Templates (w/wo filters) from FOCOM to IMS; 2. Response Query O-Cloud Managed Infrastructure Templates from IMS to FOCOM; 3. Query O-Cloud Managed Infrastructure Template details from FOCOM to IMS; 4. Response Query O-Cloud Managed Infrastructure Template from IMS to FOCOM; 5. Notify O-Cloud Managed Infrastructure Template Addition/Deletion from IMS to FOCOM via an Event Notification Pattern. Notes indicate prerequisites, optional storage of templates and attributes, and SMO processing of notifications.](1a1f0ff74dee05dae773437f24c5a996_img.jpg) - -``` - -sequenceDiagram - participant FOCOM as Service Management & Orchestration Framework (FOCOM) - participant IMS as O-Cloud Platform (IMS) - - Note right of FOCOM: PREREQUISITE: -SMO is active -IMS is active and has connectivity to SMO -SMO is subscribed to O-Cloud Managed Infrastructure Template events - - Note over FOCOM, IMS: O-Cloud Managed Infrastructure Templates Discovery Use Case - - FOCOM->>IMS: 1 Query O-Cloud Managed Infrastructure Templates (w/wo filters) - Note right of IMS: Discover available O-Cloud Managed Infrastructure Templates in the IMS - Note right of IMS: IMS returns (potentially filtered) list of available O-Cloud Managed Infrastructure Templates - IMS-->>FOCOM: 2 Response Query O-Cloud Managed Infrastructure Templates - Note left of FOCOM: Optionally store discovered O-Cloud Managed Infrastructure Templates - - opt Query O-Cloud Managed Infrastructure Template details - FOCOM->>IMS: 3 Query O-Cloud Managed Infrastructure Template - Note right of IMS: Return O-Cloud Managed Infrastructure Template attributes (e.g. parameter schema and characteristics) - IMS-->>FOCOM: 4 Response Query O-Cloud Managed Infrastructure Template - Note left of FOCOM: Optionally store corresponding attributes of the O-Cloud Managed Infrastructure Template - end - - Note over FOCOM, IMS: Event Notification Pattern - Note right of IMS: O-Cloud Managed Infrastructure Template addition/deletion detected - IMS-->>FOCOM: 5 Notify O-Cloud Managed Infrastructure Template Addition/Deletion - Note left of FOCOM: SMO can process the Managed Infrastructure Template changes information from the message - - Note over FOCOM, IMS: End O-Cloud Managed Infrastructure Template Discovery Use Case - -``` - -UML Sequence Diagram for Discovery O-Cloud Managed Infrastructure Templates. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The sequence includes: 1. Query O-Cloud Managed Infrastructure Templates (w/wo filters) from FOCOM to IMS; 2. Response Query O-Cloud Managed Infrastructure Templates from IMS to FOCOM; 3. Query O-Cloud Managed Infrastructure Template details from FOCOM to IMS; 4. Response Query O-Cloud Managed Infrastructure Template from IMS to FOCOM; 5. Notify O-Cloud Managed Infrastructure Template Addition/Deletion from IMS to FOCOM via an Event Notification Pattern. Notes indicate prerequisites, optional storage of templates and attributes, and SMO processing of notifications. - -Figure 3-74: Discovery O-Cloud Managed Infrastructure Templates - -## 3.11.8 Provisioning of an O-Cloud Node Cluster and Infrastructure Resources using a Managed Infrastructure Template - -### 3.11.8.1 General - -This section describes the management and LCM use cases for a combination of an O-Cloud Node Cluster and corresponding Infrastructure Resources, using a Managed Infrastructure Template. The Managed Infrastructure Template (referred henceforth as MIT) concept, as described in GA&P section 3.4.3.8, can be used to specify a declarative target for the desired state of an O-Cloud Node Cluster together with a set of Infrastructure Resources, represented by a provisioning request sent from SMO to IMS. Examples of Infrastructure Resources to which MIT based provisioning can be applied are site networks, gateways and attachment circuits. - -### 3.11.8.2 Create an O-Cloud Node Cluster and Infrastructure Resources using MIT Use Case - -#### 3.11.8.2.1 High Level Description - -This use case describes the processing of a Provisioning Request create request to create an O-Cloud Node Cluster and corresponding set of managed O-Cloud Infrastructure Resources based on a referenced declarative target of an MIT, sent from the SMO (FOCOM) towards IMS at O-Cloud. This use case aims to assign and configure a suitable set of O-Cloud Resources as the basis for the O-Cloud Node Cluster and a set of O-Cloud Infrastructure Resources and to enable the requestor to monitor the progress and verify that requested declarative target is fulfilled and operational. - -Before this use case is started it is expected that SMO has concluded that an O-Cloud Node Cluster and corresponding set of Infrastructure Resources needs to be created in a specific O-Cloud. When the use case is concluded, a set of relevant modeled representations of the O-Cloud Node Cluster and O-Cloud Infrastructure resources are created and exposed through the O-Cloud Node Cluster and O-Cloud Infrastructure Resource objects, with references to its assigned O-Cloud Resources in the inventory. - -#### 3.11.8.2.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Create O-Cloud Node Cluster and Infrastructure Resources using a Template Use Case | | -| Goal |

The goals of this use case are to:

  1. 1. Create an O-Cloud Node Cluster and corresponding set of Infrastructure Resources as described by a declarative target represented by the MIT and Parameters supplied with the Provisioning Request.
  2. 2. Enable the requestor to monitor the progress and verify that requested declarative target is fulfilled.

See NOTE 1.

| | -| Actors and Roles |

Service Management Orchestrator (SMO) – The SMO provides the “requirements” for the Infrastructure Resources to be created. FOCOM is the endpoint for O2ims at the SMO as a client to IMS in the O-Cloud.

Infrastructure Management Services (IMS) – The IMS Provisions Infrastructure Resources. The IMS functionality in the O-Cloud is the manager side of the endpoint for FOCOM.

| | -| Assumptions |

The following assumptions are relevant to this use case:

  1. 1. O-Cloud exists – The O-Cloud is running and has undergone genesis.
  2. 2. Infrastructure – It is assumed that O-Cloud Resources form an infrastructure that can be used by the O-Cloud Node Cluster and Infrastructure Resources.
  3. 3. Network Infrastructure – The Site Network Fabric and Site GW resources are available and operational for IMS so that they can be used to realize managed Infrastructure Resources.
  4. 4. Storage Resources – storage resources are available so that O-Cloud Node Clusters can be provided with storage resource.
  5. 5. SMO is aware of the O-Cloud capabilities and capacities, e.g., by consuming IMS inventory services information. With this information SMO
| | - -| | | | -|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

can also check the feasibility of the Provisioning Request by interacting with IMS.

  1. 6. The Provisioning Request referenced MIT includes any required parameters along with optional input parameters.
  2. 7. The Provisioning Request referenced MIT and supplied parameters is a declarative definition of the expected O-Cloud Node Cluster and Infrastructure Resource targets.
| | -| Preconditions |

The following preconditions are used by this use case:

  1. 1. The MIT referenced in the Provisioning Request exists in O-Cloud and corresponding MIT information is available to SMO
  2. 2. SMO is aware of what parameters if any to be supplied with the request.
  3. 3. The O-Cloud has connectivity and authorization allowing communication with the SMO.
| | -| Begins when |

This use case begins when there is a request to create an O-Cloud Node Cluster along with a set of O-Cloud Infrastructure Resources.

| | -| Step 1 (M) |

REQUEST TO CREATE O-CLOUD INFRASTRUCTURE RESOURCES -

SMO (FOCOM) sends a request for a new Provisioning Request to be created by the IMS. The request contains a reference to a selected MIT, and all supplied mandatory and optional parameters as given by the MIT, representing the declarative target of the requested O-Cloud Node Cluster and a set of O-Cloud Infrastructure Resources.

The MIT and provisioning request provides requirements about the capacity and capabilities of the O-Cloud Node Cluster related to the number of O-Cloud Nodes, compute and storage types and capacities, requirements for the O-Cloud Node Cluster Site Networks, location of the O-Cloud Node Cluster, and other characterizations.

IMS validates the request with the referenced Template and supplied parameters and creates a new Provisioning Request object upon success.

A created Provisioning Request object is now exposed and can be discovered & accessed by SMO.

| | -| Step 2 |

RESPONSE TO PROVISIONING REQUEST CREATE REQUEST

The IMS then responds to the Provisioning request create request with a response over the O2 IMS interface back to the SMO (FOCOM).

At this point refer to Step 4-5 for monitoring the Update Provisioning request status.

| | -| Step 3 (ALT) |

O-CLOUD PROCESSING OF THE PROVISIONING REQUEST OBJECT -

The following things happen within the O-Cloud if suitable resources are found:

  • • The IMS creates resourceID for the O-Cloud Node Cluster.
  • • The IMS creates resourceIDs for requested Infrastructure Resources.
  • • The IMS books resources in the O-Cloud for the new O-Cloud Node Cluster and Infrastructure Resources.
  • • The IMS marks the internal resources as booked for respective Node Cluster ID and infrastructure Resource IDs.
  • • Refer to Step 4-5 for monitoring the status of the Provisioning Request.
  • • The IMS updates the Provisioning Request object status throughout the
| | - -| | | | -|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

Infrastructure Resource creation progress.

See NOTE 2 and NOTE 3

| | -| Step 4-5 (PAR) |

The process of creating managed Infrastructure Resources may take significant time. During this period, SMO could monitor the provisioning status until the creation request is either successfully completed or has failed.

See NOTE 4.

The SMO (FOCOM) begins monitoring the status of the Provisioning Request object:

  • • A Provisioning Request object status request is sent from the SMO (FOCOM) to the IMS.
  • • A response from IMS to SMO (FOCOM) is sent containing the current Provisioning Request object status

EXCEPTION: INSUFFICIENT RESOURCES – There were insufficient resources to be able to fulfill Provisioning Request. In this case, the IMS updates the Provisioning Request object that there are insufficient suitable resources and publishes a list of successfully created Infrastructure Resources and the status of Node Cluster provisioning. A list of individual provisioning status of all Infrastructure Resource requested, including failed ones, is also published with Provisioning Request Status. IMS at O-Cloud continues to attempt acquiring required resources. This exception can be resolved either by O-Cloud adding additional O-Cloud Resources to fulfil the Provisioning Request; Or by SMO (FOCOM) updating the Provisioning Request to suit the available O-Cloud resources.

EXCEPTION: CREATION FAILED – The creation of a new Infrastructure Resource is not completed due to some internal failure. In this case, the IMS updates the Provisioning Request object that the Node Cluster and Infrastructure Resources provisioning has failed and publishes a list of successfully created Infrastructure Resources and the status of Node Cluster provisioning. A list of individual provisioning status of all Infrastructure Resource requested, including failed ones, is also published with Provisioning Request Status. IMS at O-Cloud bail-out on further processing of the provisioning request until further intervention from consumer (FOCOM) to update or delete the Provisioning Request.

See Note 6

| | -| Step 6 (ALT) |

SUCCESSFUL CREATION OF INFRASTRUCTURE RESOURCES

If the O-Cloud Node Cluster and all Infrastructure Resources requested by the Provisioning Request are created successfully then IMS performs the following.

  • • A new or existing DMS endpoint is associated with the provisioned O-Cloud Node Cluster.
  • • The relevant modelled representation of O-Cloud resources are updated with the newly created O-Cloud Node Cluster or Infrastructure Resources, and its references to other resources.
  • • The IMS updates the Provisioning Request object with the successful status and information on created O-Cloud Node Cluster and Infrastructure Resources.
| | -| Step 7 (ALT) |

EXCEPTION: MALFORMED REQUEST – The request had an incorrect format and was not understood by the IMS. An unsuccessful Provisioning Request response is returned to the requestor. The request was non-sensical or the parameters comprising the request are not valid. IMS cleans up all internal actions for this request.

| | - -| | | | -|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Ends when | This use case ends when the O-Cloud Node Cluster and all requested Infrastructure Resources are created, or the use case execution have encountered an exception where the requested O-Cloud Node Cluster and/or requested Infrastructure Resources are not created, or just some of the Infrastructure Resources have been created. | | -| Exceptions |

INSUFFICIENT RESOURCES – If there are insufficient resources to fulfill the request. The request to create the O-Cloud NodeCluster and Infrastructure Resources cannot be performed.

CREATION FAILED – The creation of a new O-Cloud NodeCluster and Infrastructure Resource couldn't be completed.

MALFORMED REQUEST – The request had an incorrect format and could not be processed by the IMS. The request to create an O-Cloud NodeCluster and Infrastructure Resource is rejected.

| | -| Post-conditions |

SUCCESS: There is an O-Cloud Node Cluster and a set of new provisioned Infrastructure Resources created with corresponding Resource IDs.

FAILURE:O-Cloud encounters failure in processing the Provisioning Request and it was possible to create only a subset of Infrastructure Resources requested.

INSUFFICIENT RESOURCE: O-Cloud is experiencing insufficient resources to fulfill the provisioning request. It is possible that a subset of requested Infrastructure is successfully created and remaining are waiting for additional resources to fulfill the request. This situation shall change either on O-Cloud adding additional resources to fulfil the request or when SMO (FOCOM) updates the provisioning request.

See NOTE 6

| | -| Traceability | REQ-ORC-O2-119, REQ-ORC-O2-120 | | -| Notes |

NOTE 1: The intent of using MITs is to simplify the interactions between consumers to create the requested O-Cloud Node Cluster and corresponding Infrastructure Resources. The O-Cloud internally will search for and book usable O-Cloud internal resources (whose exposure to the SMO depends on the resource view and inventories resources exposed by the IMS), to create a new O-Cloud Node Cluster and Infrastructure Resources that satisfies the request.

NOTE 2: Within this use case, the term “booked resource” is a resource that has been reserved internal to the O-Cloud. As compared to an allocated resource which is a term that describes a booked resource that is externally exposed.

NOTE 3: The IMS may indicate that resources are found, booked, and creation will start by updating the Provisioning Request object. Though this will be further defined in the protocol specifications.

NOTE 4: The IMS may also indicate via a notification to the SMO the successful or failed creation of O-Cloud Node Cluster and managed Infrastructure Resources.

NOTE 5: If some resources were found that match the request, but insufficient to fully satisfy the request, the IMS will respond with insufficient resources found. It is up to the requestor to track the Provisioning Request object and reformulate a new request.

NOTE 6: During the processing of a Provisioning Request for the O-Cloud Node Cluster and/or set of Infrastructure Resources, the provisioning status of O-Cloud Node Cluster and each individual Infrastructure Resource is published with the Provisioning Request status, in a Resource Provisioning Status list.

| | - -3.11.8.2.3 UML Sequence Diagram - -![UML Sequence Diagram titled 'Create a Node Cluster and Infrastructure Resources using MIT Use Case'. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The diagram shows the interaction for creating a node cluster and infrastructure resources, including preconditions, a success path, and two exception paths (Insufficient Resources and Malformed Request).](8c05782074bb11421b43f2d5d6799b62_img.jpg) - -**Service Management & Orchestration Framework** (FOCOM) and **O-Cloud Platform** (IMS) lifelines. - -**PREREQUISITE:** SMO is active, IMS is active and has connectivity to SMO - -**Pre-condition:** -FOCOM decides it needs an O-Cloud Node Cluster along with a set of Infrastructure Resources in a specific O-Cloud -A MIT exists for provisioning of the O-Cloud Node Cluster and Infrastructure Resources for the associated O-Cloud -SMO populates necessary parameters based on the parameter schema of the MIT - -**Create O-Cloud Node Cluster and Infrastructure Resources using MIT Use Case** - -- 1 Provisioning Request Create request**: FOCOM sends to IMS. Note: The Provisioning Request object contains a reference to the MIT along with the required parameters. -- alt [Success]**: - - IMS validates the Provisioning Request data and create Provisioning Request Object. - - 2 Provisioning Request Create response**: IMS sends to FOCOM. - - 3 IMS processes the create Provisioning Request**: Internal IMS steps: Create Resource IDs, Allocate resources and mark them as booked. - - par [Control Loop]**: - - FOCOM begins tracking the Provisioning Request object in the IMS. - - 4 Provisioning Request Read Object Status request**: FOCOM sends to IMS. - - 5 Provisioning Request Read Object Status response**: IMS sends to FOCOM. - - [Provisioning Request processing]**: - - IMS creates the O-Cloud Node Cluster and Infrastructure Resources according to the referenced MIT. - - IMS updates the Provisioning Request object with the O-Cloud Node Cluster and Infrastructure Resource creation progress. - - [Exception if Insufficient Resources]**: - - Insufficient resources to create requested O-Cloud Node Cluster or an Infrastructure resource requested. - - IMS updates Provisioning Request Object Status along with a list of successfully created Infrastructure Resources and a list of individual provisioning status of all Infrastructure Resources requested. - - [Exception Creation Failed]**: - - Creation of requested O-Cloud Node Cluster and Infrastructure Resources could not be completed due to some internal failure. - - IMS updates the Provisioning Request object status along with a list of successfully created Infrastructure Resources and a list of individual provisioning status of all Infrastructure Resources requested. - - 6 IMS updates ProvisioningRequest phase to FULFILLED**: Internal IMS step. - - Note: Provisioning Request Create fulfilled. -- [Exception Malformed Request]**: - - IMS evaluates the request, but it has a bad format. - - 7 Respond Malformed Request**: IMS sends to FOCOM. - - Note: The IMS "cleans up" meaning that any internal activities and reservations that occurred in processing the failed request are reversed. - -**End Create O-Cloud Node Cluster Infrastructure Resources Using MIT Use Case** - -UML Sequence Diagram titled 'Create a Node Cluster and Infrastructure Resources using MIT Use Case'. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). The diagram shows the interaction for creating a node cluster and infrastructure resources, including preconditions, a success path, and two exception paths (Insufficient Resources and Malformed Request). - -Figure 3-75: Create a Node Cluster and Infrastructure Resources using MIT - -### 3.11.8.3 Update O-Cloud Node Cluster and Infrastructure Resources using MIT - -#### 3.11.8.3.1 High level description - -This use case describes the processing of a Provisioning Request update request to update an O-Cloud Node Cluster and/or corresponding set of Infrastructure Resources previously created using a declarative target represented by the Provisioning Request based on an MIT. Updates may include O-Cloud Node addition(s) or reduction(s), including adding/removing cluster capabilities for the O-Cloud Node Cluster and/or Infrastructure Resource addition(s) or reduction(s), and updating Infrastructure Resource configurations and capabilities. The update request originates from FOCOM and is sent towards the IMS within the O-Cloud. The objective of the operation is to update previously created and configured O-Cloud Node Cluster and corresponding Infrastructure Resources created. This is part of a family of O2 IMS Provisioning operations related to managed Infrastructure Resources. - -When the use case is concluded, the specified O-Cloud Node Cluster and Infrastructure Resources in the O-Cloud has been updated according to the updated declarative target represented by the Provisioning Request. - -#### 3.11.8.3.2 Sequence Description - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Use Case Title | Update O-Cloud Node Cluster and Infrastructure Resources using MIT | | -| Goal |

The goals of this use case are to:

  1. 1. Update a previously created and configured O-Cloud Node Cluster and Infrastructure Resources in the O-Cloud using MIT by referring to a new MIT and/or updated parameters to update infrastructure resources accordingly.
  2. 2. Inform the requestor (normally FOCOM) that the O-Cloud NodeCluster and Infrastructure Resources has been updated.
| | -| Actors and Roles |

Service Management Orchestrator (SMO) – The FOCOM in the SMO is the consumer that will request for the O-Cloud Node Cluster and managed Infrastructure Resources to be updated.

Infrastructure Management Services (IMS) – The IMS processes the request to update the O-Cloud Node Cluster and managed Infrastructure Resource.

| | -| Assumptions |

The following assumption is relevant to this use case:

  1. 1. Provisioning Request exists – The Provisioning Request being updated is previously created and exists in O-Cloud.
| | -| Preconditions |

The following preconditions are used by this use case:

  1. 1. IMS Operational – The IMS in the O-Cloud is active and operational.
  2. 2. Connectivity & Authorization – The O-Cloud has connectivity and authorization allowing communication with the SMO.
| | -| Begins when | This use case begins when the FOCOM determines that an update is needed for an O-Cloud Node Cluster and corresponding set of previously created Infrastructure Resources created. | | -| Step 1 |

REQUEST TO UPDATE A NODE CLUSTER AND O-CLOUD INFRASTRUCTURE RESOURCES -

The FOCOM sends to the IMS a Provisioning Request update request. The updated Provisioning Request object contains the reference of the MIT along with all relevant parameters.

| | - -| | | | -|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 2 |

RESPONSE TO PROVISIONING REQUEST UPDATE REQUEST

IMS validates the request with the referenced Template and supplied parameters and sends a response over the O2 IMS interface back to the SMO (FOCOM).

At this point refer to Step 4 - 5 for monitoring the Update Provisioning request status.

| | -| Step 3 (ALT) |

O-CLOUD PROCESSING OF THE UPDATED PROVISIONING REQUEST OBJECT

The following steps are done by the IMS in the O-Cloud to process the Provisioning Request update request:

  • Resource Check – IMS checks the resources associated and the IMS processes the request which is asking for O-Cloud resource additions, reductions or updates.
  • Node Cluster Update – The IMS performs updates to existing Node Cluster based on the request.
  • Infrastructure Resource Update – The IMS performs updates to existing Infrastructure Resources based on the request.
  • Infrastructure Resource Addition/Removal – The IMS allocates or deallocates an O-Cloud Resource with the intention to start (addition) or stop (removal) using it.
| | -| Step 4-5 (PAR) |

SMO (FOCOM) begins monitoring the status of the Provisioning Request object:

  • A Provisioning Request object status request is sent from the SMO to the IMS.
  • A response from IMS to SMO is sent containing the current status of the Update Provisioning Request status.

EXCEPTION: INSUFFICIENT RESOURCES – There were insufficient resources to be able to fulfill the update of the Provisioning Request. In this case, the IMS updates the Provisioning Request object that there are insufficient suitable resources and publishes a list of successfully updated Infrastructure Resources. A list of individual provisioning status of the O-Cloud Node Cluster and all Infrastructure Resource requested, including failed ones, is also published with Provisioning Request Status. IMS at O-Cloud continues to attempt acquiring required resources. This exception can be resolved either by O-Cloud adding additional O-Cloud Resources to fulfil the Provisioning Request Or by SMO (FOCOM) updating the Provisioning Request to suit the available O-Cloud resources.

EXCEPTION: UPDATE FAILED – IMS encountered failures in processing of the updated Provisioning Request. In this case the IMS updates the Provisioning Request object that the Infrastructure Resources provisioning has failed and publishes a list of successfully provisioned Infrastructure Resources. A list of individual provisioning status of all Infrastructure Resource requested, including failed ones, is also published with Provisioning Request Status. IMS at O-Cloud bail-out on further processing of the provisioning request until further intervention from consumer SMO (FOCOM).

See NOTE 1

| | -| Step 6 (ALT) |

SUCCESSFUL PROCESSING OF UPDATE PROVISIONING REQUEST

If updates to the O-Cloud Node Cluster and all Infrastructure Resources requested by the MIT are processed successfully, the IMS updates the Provisioning Request object with the successful status and information on the O-Cloud Node Cluster and Infrastructure Resources.

| | -| Step 7 (ALT) |

EXCEPTION: MALFORMED REQUEST – The request had an incorrect format and was not understood by the IMS. An unsuccessful Provisioning Request response is returned to the requestor. The request was non-sensical or the parameters comprising the request are not valid. IMS cleans up all internal actions for this request.

| | - -| | | | -|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | See NOTE 2 | | -| Ends when | This use case ends when the O-Cloud Node Cluster and all requested Infrastructure Resources are updated, or the use case execution have encountered an exception where requested O-Cloud Node Cluster and/or Infrastructure Resources have not been updated. | | -| Exceptions | UPDATE FAILED – Update of the O-Cloud Node Cluster or the managed Infrastructure Resources as requested by the Provisioning Request could not be completed due to O-Cloud internal failures.

INSUFFICIENT RESOURCES – There are insufficient resources to perform the Update Provisioning Request operation.

MALFORMED REQUEST – The request had an incorrect format and could not be processed by the IMS. The request to update the Provisioning Request Object is rejected.

See NOTE 2 and NOTE 3 | | -| Post-conditions | SUCCESS: The O-Cloud Node Cluster is successfully updated and corresponding Infrastructure Resources are successfully created, updated or removed as requested by the updated Provisioning Request.

FAILURE/PARTIAL SUCCESS: IMS publishes a list of successfully provisioned Infrastructure Resources. A list of individual provisioning status of all Infrastructure Resource requested, including failed ones, is also published with Provisioning Request Status.

See NOTE 3 | | -| Traceability | REQ-ORC-02-121, REQ-ORC-02-122, REQ-ORC-02-123, REQ-ORC-02-124 | | -| Notes | NOTE 1: Update of the O-Cloud Node Cluster and/or Infrastructure Resource can also impact workloads deployed from the NFO/DMS.

NOTE 2: The implementation might encounter more exceptions of what is described in this current use case.

NOTE 3: During the processing of a Provisioning Request for an O-Cloud Node Cluster and a set of Infrastructure Resources, the provisioning status of the O-Cloud Node Cluster and each individual Infrastructure Resource is published with the Provisioning Request status in a Resource Provisioning Status list. | | - -### 3.11.8.3.3 UML Sequence Diagram - -![UML Sequence diagram for 'Update O-Cloud Node Cluster and Infrastructure Resources using MIT Use Case'. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS).](14af2781d0bd19b98b10672b74daaca2_img.jpg) - -**PREREQUISITE:** -SMO is active, IMS is active and has connectivity to SMO -ProvisioningRequest being updated exists - -**Pre-condition:** -Managed Infrastructure Template exists for the associated O-Cloud - -**Update O-Cloud Node Cluster and Infrastructure Resources using MIT Use Case** - -- 1 Provisioning Request update request (FOCOM to IMS) -The Update Provisioning Request object contains a reference to the Managed Infrastructure Template along with all relevant parameters -- alt [Success] - - 2 Provisioning Request update response (IMS to FOCOM) - - 3 IMS processes the update ProvisioningRequest -Validate the Provisioning Request data and create Provisioning Request Object - - par [Control Loop] - - 4 Provisioning Request Read Object Status request (FOCOM to IMS) -SMO begins tracking the Provisioning Request object in the IMS - - 5 Provisioning Request Read Object Status response (IMS to FOCOM) - - IMS updates the O-Cloud Node Cluster and Infrastructure Resources according to the Provisioning Request and referenced Managed Infrastructure Template - - IMS updates the Provisioning Request object with the O-Cloud Node Cluster and Infrastructure Resource creation progress -- Exception If Insufficient Resources - - Insufficient resources for requested update of the O-Cloud Node Cluster and/or create or update requested Infrastructure Resources - - IMS updates the Provisioning Request object with the Provisioning status of the O-Cloud Node Cluster and requested Infrastructure Resources -- Exception Update Failed - - Update of the O-Cloud Node Cluster and/or create, update or delete of requested Infrastructure Resources could not be completed due to internal failure - - IMS updates the Provisioning Request object with the Provisioning status of the O-Cloud Node Cluster and requested Infrastructure Resources -- 6 IMS updates Provisioning Request phase to FULFILLED -The O-Cloud Node Cluster is updated and corresponding Infrastructure Resources are created or updated or deleted as requested by the Provisioning Request - -- Exception Malformed Request -- IMS evaluates the request, but it has a bad format -- 7 Respond Malformed Request (IMS to FOCOM) -The IMS "cleans up" meaning that any internal activities and reservations that occurred in processing the failed request are reversed. - -**End Update O-Cloud Node Cluster and Infrastructure Resources Using MIT Use Case** - -UML Sequence diagram for 'Update O-Cloud Node Cluster and Infrastructure Resources using MIT Use Case'. Lifelines: Service Management & Orchestration Framework (FOCOM) and O-Cloud Platform (IMS). - -Figure 3-76: Update a Node Cluster and Infrastructure Resources using MIT - -## 3.12 Resource Optimization Use Cases - -### 3.12.1 Introduction - -O-Cloud resource optimization is the process of utilizing the O-Cloud resources in an efficient manner and eliminating waste of O-Cloud resources by selecting, provisioning, and rightsizing the resources within the O-Cloud. - -The Network Functions (NFs) within O-Cloud are orchestrated as VNFs/CNFs. The SMO (NFO, FOCOM) handle the management and orchestration of VNFs/CNFs and underlying O-Cloud infrastructure. The SMO's management, orchestration, and optimization functionalities can be enhanced by intelligent observability analysis from VNFs/CNFs and O-Cloud. - -The Non-RT RIC hosts third-party applications such as rApp in the SMO, which can collect and read various O1 and O2-related observability data and metrics through O1 & O2 related services. These third-party rApps can be leveraged to provide guidance/recommendations to the NFO and FOCOM for management, orchestration, and optimization of VNFs/CNFs and underlying O-Cloud infrastructure. - -### 3.12.2 O-Cloud Drain Node Use Case - -#### 3.12.2.1 High Level Description - -This use case describes the procedure for the SMO and O-Cloud to drain one or more O-Cloud Node(s) based on recommendations from rApp or manually by O-Cloud Maintainer via SMO. The draining of O-Cloud Node(s) will mark the specific O-Cloud Node(s) as cordoned or un-schedulable and can necessitate means to relocate, migrate or terminate Network Functions or its components to another O-Cloud Node. - -There are various possible scenarios where there's a need to drain an O-Cloud Node(s). One such example scenario could be where rApp, with the help of AI/ML, can provide insights to FOCOM/NFO for O-Cloud Node failure. rApp predicting the O-Cloud Node failure can recommend FOCOM/NFO to drain that particular O-Cloud Node and proactively migrate the workloads from the O-Cloud Node. Subsequently, this NF migration, as a result of the node draining recommendation, ensures service continuity by minimizing disruption and assuring the quality of service for the network slices and services. - -In this use case, the SMO manages NF(s) relocation. The request for draining an O-Cloud Node(s) can be manual, or rApps can send a recommendation to FOCOM/NFO. This use-case (along with other Resource Optimization use-cases) envisions a data-driven approach for optimizing O-Cloud resources. The rApps in non-RT RIC utilizing AI/ML framework can provide guidance to FOCOM/NFO complementing FOCOM/NFO scheduling capabilities and empowering the system to make more data driven placement decisions. - -NOTE 1 : The current version of the specification does not specify whether it's the IMS or DMS that receives the request to drain the O-Cloud node(s). - -NOTE 2 : The O-Cloud Node(s) is set to maintenance mode (see clause 3.10.2 in O2 GA&P [9]) by default, when this use case is called. - -#### 3.12.2.2 Sequence Description - -| Use Case Stage | Evolution / Specification | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | To drain O-Cloud Node(s) by labelling the node(s) as cordoned or un-schedulable, and it may safely evict/migrate all the Network Function(s) and/ or its components from the O-Cloud Node(s). | -| Actors and Roles | O-Cloud Maintainer
SMO: FOCOM /NFO
IMS: Infrastructure Management Services
DMS - Deployment Management Services | - -| | | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | rApp (via Non-RT RIC)
NF - Network Function (Application) | -| Assumptions |
  1. 1. The “Service Request” to the SMO includes the identifiers of the O-Cloud Node(s) to be drained.
  2. 2. A trigger for draining a O-Cloud Node is received from FOCOM/NFO based on a request from O-Cloud Maintainer, or recommendation from rApp.
  3. 3. Data traffic from the node(s) that needs to be drained has been moved before triggering the O-Cloud Node(s) draining procedure.
| -| Pre- conditions |
  1. 1. SMO is available
  2. 2. O-Cloud is available
  3. 3. O1 & O2 events have been subscribed by the monitoring system supervised by the O-Cloud Maintainer and /or rApp.
| -| Begins when | Existing O-Cloud Node(s) is/are determined to be drained based on a request from O-Cloud Maintainer or recommendation from rApp. | -| Step 1 (M) | O-Cloud Maintainer provides a request or rApp provides recommendation to FOCOM/NFO to drain the specific set of O-Cloud Node(s). | -| Step 2 (M) | Once the recommendation from rApp or the request from the O-Cloud Maintainer to FOCOM/NFO gets accepted, FOCOM/NFO requests the IMS/DMS over the O2 interface to drain one or more O-Cloud Node(s). | -| Step 3 (M) | IMS/DMS will mark the O-Cloud Node(s) as cordoned or un-schedulable. | -| Step 4 (M) | IMS/DMS will drain the O-Cloud Node(s), which can trigger migrating NF Deployment(s) from each individual O-Cloud Node.

NOTE 1: Steps 2-4 can be looped for each O-Cloud Node.
NOTE 2: Once the O-Cloud Node(s) is drained, all the NF Deployments(s) are either migrated or terminated from the O-Cloud Node(s).. | -| Step 5 (ALT) | SUCCESS:
5.1 IMS/DMS notifies FOCOM/NFO that the O-Cloud Node(s) drain action is completed.
5.2 FOCOM/NFO notifies the rApp or O-Cloud Maintainer that the O-Cloud Node(s) drain is completed. | -| Step 6 (ALT) | EXCEPTION:
The O-Cloud Node draining procedure encountered an exception. There can be various reasons for the exception, like the Node Cluster not found, the Node Cluster not responding or unavailable, or the Node Cluster having insufficient resources to migrate NF Deployment(s).

6.1. IMS/DMS notifies FOCOM/NFO that the O-Cloud Node(s) drain action was unsuccessful.
6.2. FOCOM/NFO notifies the rApp or O-Cloud Maintainer that the O-Cloud Node(s) drain action was unsuccessful. | -| Ends when | This use case ends when the O-Cloud Node(s) have been drained, i.e., when the O-Cloud Node(s) have been marked as cordoned or un-schedulable, and the NF deployment(s) have been moved to other O-Cloud Node instances, or the use case has encountered an exception. | -| Exceptions | The Node Cluster Not Found – The requested Node Cluster was not found or does not exist in the O-Cloud.
The Node Cluster is unavailable – The requested Node Cluster is unavailable, busy, not responding, or malfunctioning.
Insufficient Resources – There are insufficient resources to migrate the NFs Deployment(s) within the O-Cloud Node Cluster. | -| Post-conditions | SUCCESS: The requested O-Cloud Node(s) in the Node Cluster has been marked cordoned or un-schedulable, and all the NF Deployment(s) are migrated to other O-Cloud Node(s) within the Node Cluster.

FAILURE: The O-Cloud and IMS/DMS state is in the same state as before the request arrived: no resources are amended, and no NF Deployment(s) are migrated or terminated. | -| Traceability | [REQ-ORC-GEN29], [REQ-ORC-O2-94], [REQ-ORC-O2-95] | - -### 3.12.2.3 UML Sequence Diagram - -![UML Sequence Diagram for O-Cloud Node Draining. The diagram shows interactions between Personnel (O-Cloud Maintainer), Service Management & Orchestration Framework (rApp via Non-RT RIC, FOCOM & NFO), and O-Cloud Platform (IMS & DMS). It details the process from node determination and draining requests to the actual draining loop and success/exception handling responses.](9144d599bb5bf98cd607202d768a4956_img.jpg) - -``` - -sequenceDiagram - actor Personnel as O-Cloud Maintainer - participant rApp as rApp (via Non-RT RIC) - participant FOCOM as FOCOM & NFO - participant IMS as IMS & DMS - - Note over rApp, FOCOM: PREREQUISITE: -SMO is available -O-Cloud is available -O1 & O2 events subscription by the monitoring system -supervised by the O-Cloud Maintainer and/or rApp. - - Note over FOCOM: O-Cloud Node Determination - Note over Personnel, rApp: Cloud Maintainer or rApp determines -to drain O-Cloud Nodes - - Note over FOCOM: O-Cloud Node Draining - - alt Request/Recommend - Personnel->>FOCOM: 1.1 Request to drain O-Cloud Node(s) - rApp->>FOCOM: 1.2 Recommend to drain O-Cloud Node(s) - end - - Note over FOCOM: FOCOM/NFO receives and process -the recommendation from rApp or -request from O-Cloud Maintainer -to drain O-Cloud Node(s) - - loop for each O-Cloud Node(s) - FOCOM->>IMS: 2 <> Request to drain the O-Cloud Node - IMS-->>IMS: 3 Mark the O-Cloud Node as cordoned or un-schedulable - IMS-->>IMS: 4 Drain the O-Cloud Node - end - - alt Success - IMS->>FOCOM: 5.1 <> Response to drain O-Cloud Node(s) - FOCOM->>rApp: 5.2 Response to drain O-Cloud Node(s) - rApp->>Personnel: 5.3 Response to drain O-Cloud Node(s) - else Exception - Note over IMS: IMS/DMS evaluates the request, but -the O-Cloud Node draining procedure -encountered an exception. - IMS->>FOCOM: 6.1 <> Response to drain O-Cloud Node(s) with exception - FOCOM->>rApp: 6.2 Response to drain O-Cloud Node(s) with exception - rApp->>Personnel: 6.3 Response to drain O-Cloud Node(s) with exception - Note over IMS: "Clean Up" - end - - Note over rApp: Use Case Ends - Note over FOCOM: End O-Cloud Node Draining Use Case - -``` - -UML Sequence Diagram for O-Cloud Node Draining. The diagram shows interactions between Personnel (O-Cloud Maintainer), Service Management & Orchestration Framework (rApp via Non-RT RIC, FOCOM & NFO), and O-Cloud Platform (IMS & DMS). It details the process from node determination and draining requests to the actual draining loop and success/exception handling responses. - -Figure 3-77: O-Cloud Node Draining - -### 3.12.3 O-Cloud Cordon and Uncordon Use Case - -#### 3.12.3.1 High Level Description - -This use case describes how to Cordon and then Uncordon an O-Cloud Node(s) (after the successful cordoning of the node) in a O-Cloud Node Cluster. - -Cordoning(s) a node is performed in order to mark the O-Cloud Node(s) un-schedulable. Marking the O-Cloud Node(s) as un-schedulable prevents the scheduler from placing new NF deployments on the specified O-Cloud Node(s) but does not affect existing NF deployments on the O-Cloud Node(s). This is useful as a preparatory step before draining an O-Cloud Node(s). - -The action to Cordon or Uncordon an O-Cloud Node(s) can be a recommendation by an rApp or a manual request submitted by Cloud Maintainer via SMO - -In the context of O-Cloud Resource Optimisation, rApps utilizing O2 telemetry data can recommend the cordoning and uncordoning of O-Cloud Nodes, to achieve optimized resource allocation, as explained below. To enable this functionality, O-Cloud exposes the following telemetry data to FOCOM and rApp, including but not limited to: - -- 1 O-Cloud Node(s) CPU utilisation -- 2 O-Cloud Node(s) Memory utilisation -- 3 O-Cloud Node(s) Disk utilisation - -rApps can correlate the above information with other data e.g., O1 telemetry data related to Network Traffic. - -rApps can predict periods of high resource utilization (e.g., within the next 4 hours) and recommend Cordoning of O-Cloud Node(s) to FOCOM. This ensures that critical performance-sensitive workloads are not placed on specific O-Cloud Nodes during peak times. - -rApps continuously evaluate the conditions (based on O2 and/or O1 telemetry data and their correlation) Once the predicted high traffic period has passed and the resource utilization on the O-Cloud Node has returned to normal levels, the rApp can recommend Uncordoning the O-Cloud Node to allow new NF deployments to be scheduled on the node again. - -Alternatively, if periods of high resource utilization are predicted, then one possible action could be to recommend to uncord some previously cordoned nodes (i.e., those that are done with the maintenance activities) so that they are available for this period. And when decreased resource utilization is predicted, the recommendation could be to cordon specific O-Cloud nodes that are not required for handling the NF Deployment. - -NOTE 1: rApps take into consideration the potential impact of Cordoning & Uncordoning of the O-Cloud Node(s) on future system performance. Therefore, the rApps will only recommend Cordoning of the O-Cloud Node(s) if it predicts a prolonged period of high or low O-Cloud resource usage, and Uncordoning if the resource utilization returns to normal levels, to avoid unnecessary and frequent Cordoning and Uncordoning of the O-Cloud Node(s). - -NOTE 2: This version of the use case does not describe the role and involvement of FOCOM vs. NFO and how IMS interacts with the DMS. - -Editor’s Note: Architecture issues associated with the use case such as the involvement of FOCOM vs. NFO and on how IMS interacts with the DMS are still under discussion and should be reviewed for any impact on the sequence description and UML flow diagrams. - -### 3.12.3.2 Sequence Description - -| Use Case Stage | Evolution / Specification | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Goal | Cordon the O-Cloud Node to mark it as un-schedulable and subsequently Uncordon the O-Cloud Node to make it available for NF deployments | -| Actors and Roles | Cloud Maintainer
SMO: FOCOM
IMS: Infrastructure Management Services
rApp (via Non-RT RIC)
NF: Network Function (Application) | -| Assumptions |
  1. 1) The Service Request to the SMO includes the identifiers of the O-Cloud Node(s) to be Cordon and Uncordon.
  2. 2) A trigger to Cordon and/or Uncordon O-Cloud Node(s) is received from FOCOM based on a request from Cloud Maintainer, or recommendation from rApp.
| -| Pre-conditions |
  1. 1) SMO is available.
  2. 2) O-Cloud is available.
  3. 3) Network connectivity exists between the O-Cloud and SMO
  4. 4) O1 & O2 events have been subscribed by the monitoring system supervised by O-Cloud Maintainer and/or rApp.
| -| Begins when | Existing O-Cloud Node(s) is/are determined to be Cordon based on a request from O-Cloud Maintainer or recommendation from rApp. | - -| | | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Step 1 (M) | Cloud Maintainer provides a request or rApps provides recommendation to FOCOM to Cordon the specific set of O-Cloud Node(s). | -| Step 2 (M) | Once the recommendation from rApp or the request from the O-Cloud Maintainer to FOCOM gets accepted, FOCOM requests the IMS over the O2 interface to Cordon one or more O-Cloud Node(s).
NOTE 1: FOCOM verifies that the request or recommendation is valid before sending it to IMS
NOTE 2: FOCOM may reject the Cloud Maintainer's request or rApp's recommendation of cordon/uncordon for some reasons such as too-frequent requests. (e.g. 429 too many request) | -| Step 3 (M) | IMS will mark the O-Cloud Node(s), as cordoned or un-schedulable for new NF Deployments.
NOTE 3: Steps 2-3 can be looped for each O-Cloud Node. | -| Step 4 (ALT) | SUCCESS:
4.1 IMS notifies FOCOM that the O-Cloud Node(s) Cordon operation is complete.
4.2, 4.3 FOCOM notifies the rApp or Cloud Maintainer that the O-Cloud Node(s) Cordon is completed. | -| Step 5 (ALT) | EXCEPTION:
The O-Cloud Node Cordon procedure encountered an exception. There can be various reasons for the exception, like Node is already cordoned, there is a network or communication issue.

5.1 IMS notifies FOCOM that the O-Cloud Node(s) Cordon action was unsuccessful (e.g., "Node is already cordoned" or "communication timeout")
5.2, 5.3 FOCOM notifies the rApp or Cloud Maintainer that the O-Cloud Node(s) Cordon action was unsuccessful. | -| Step 6 (O) | Cloud Maintainer provides a request or rApps provides recommendation to FOCOM to Uncordon the specific set of O-Cloud Node(s). | -| Step 7 (O) | Once the recommendation from rApp or the request from the O-Cloud Maintainer to FOCOM gets accepted, FOCOM requests the IMS over O2 interface to Uncordon one or more O-Cloud Node(s). | -| Step 8 (O) | IMS will mark the O-Cloud Node(s), as uncordoned or schedulable for new NF Deployments.
NOTE 4: Steps 7-8 can be looped for each O-Cloud Node. | -| Step 9 (O) | SUCCESS:
9.1 IMS notifies FOCOM that the O-Cloud Node(s) Uncordon operation is complete.
9.2, 9.3 FOCOM notifies the rApp or Cloud Maintainer that the O-Cloud Node(s) Uncordon is completed. | -| Step 10 (ALT) | EXCEPTION:
The O-Cloud Node Uncordon procedure encountered an exception. There can be various reasons for the exception, like Node is already uncordoned, there is a network or communication issue.

10.1 IMS notifies FOCOM that the O-Cloud Node(s) Uncordon action was unsuccessful. (e.g., "Node is already uncordoned" or "communication timeout").
10.2, 10.3 FOCOM notifies the rApp or Cloud Maintainer that the O-Cloud Node(s) Uncordon action was unsuccessful. | -| Ends when | O-Cloud Node(s) have been Cordon and IMS marks the Node(s) in the existing Node pool as un-schedulable or the use case has encountered an exception
OR
O-Cloud node(s) have been Uncordon and IMS marks the Node(s) in the existing Node pool as schedulable or the use case has encountered an exception | -| Exceptions | 1. Cordon operation is not successful on the O-Cloud Node(s).
2. Uncordon operation is not successful on the O-Cloud Node(s). | -| Post-conditions | SUCCESS: The requested O-Cloud Node(s) in the Node Cluster has been marked cordoned or un-schedulable. If required, O-Cloud Node(s) draining operation can be initiated on the O-Cloud Node(s)
OR
Subsequently, the requested O-Cloud Node(s) in the Node Cluster has been Uncordoned or schedulable.
FAILURE: The O-Cloud and IMS stay is in the same state as before the request arrived | -| Traceability | [REQ-ORC-GEN31], [REQ-ORC-GEN32] [REQ-ORC-O2-101], [REQ-ORC-O2-102], [REQ-ORC-O2-103], [REQ-ORC-O2-104] | - -### 3.12.3.3 UML Sequence Diagram - -![UML Sequence Diagram for Node Cordon and Uncordon. Lifelines: Personnel (Cloud Maintainer), Service Management & Orchestration Framework (rApp & Non-RT RIC, FOCOM), and O-Cloud Platform (IMS). The diagram shows two main procedures: O-Cloud Node(s) Cordon Procedure and O-Cloud Node(s) Uncordon Procedure, each with success and exception paths.](f63b447b65c94acf4135bcd496ebfe05_img.jpg) - -``` - -sequenceDiagram - actor Cloud Maintainer as Cloud Maintainer - participant rApp & Non-RT RIC as rApp & Non-RT RIC - participant FOCOM as FOCOM - participant IMS as IMS - - Note right of rApp & Non-RT RIC: O-Cloud Node(s) Determination - Note left of FOCOM: Cloud Maintainer or rApp determines to Cordon a O-Cloud Node(s) - Note right of FOCOM: O-Cloud Node(s) Cordon Procedure - alt 1.1 Request to Cordon O-Cloud Node(s) / 1.2 Recommendation to Cordon O-Cloud Node(s) - FOCOM->>IMS: 2 <> Cordon O-Cloud Node(s) - Note right of IMS: loop [for each O-Cloud Node(s)] - IMS-->>FOCOM: 3 Cordon O-Cloud Node(s) - alt Success - IMS-->>FOCOM: 4.1 <> O-Cloud Status Notification - FOCOM-->>rApp & Non-RT RIC: 4.2 O-Cloud Status Notification - FOCOM-->>Cloud Maintainer: 4.3 O-Cloud Status Notification - alt Exception - Note right of IMS: IMS evaluates the request, but the O-Cloud Node cordon procedure encountered an exception. - IMS-->>FOCOM: 5.1 <> Response to cordon O-Cloud Node(s) with exception - FOCOM-->>rApp & Non-RT RIC: 5.2 Response to Cordon O-Cloud Node(s) with exception - FOCOM-->>Cloud Maintainer: 5.3 Response to Cordon O-Cloud Node(s) with exception - end - - Note right of rApp & Non-RT RIC: O-Cloud Node(s) Uncordon Procedure - Note left of FOCOM: Cloud Maintainer or rApp determines to Uncordon a O-Cloud Node(s) - Note right of FOCOM: O-Cloud Node(s) Uncordon Procedure - alt 6.1 Request to Uncordon O-Cloud Node(s) / 6.2 Recommendation to Uncordon O-Cloud Node(s) - FOCOM->>IMS: 7 <> Uncordon O-Cloud Node(s) - Note right of IMS: loop [for each O-Cloud Node(s)] - IMS-->>FOCOM: 8 Uncordon O-Cloud Node(s) - alt Success - IMS-->>FOCOM: 9.1 <> O-Cloud Status Notification - FOCOM-->>rApp & Non-RT RIC: 9.2 O-Cloud Status Notification - FOCOM-->>Cloud Maintainer: 9.3 O-Cloud Status Notification - alt Exception - Note right of IMS: IMS evaluates the request, but the O-Cloud Node uncordon procedure encountered an exception. - IMS-->>FOCOM: 10.1 <> Response to Uncordon O-Cloud Node(s) with exception - FOCOM-->>rApp & Non-RT RIC: 10.2 Response to Uncordon O-Cloud Node(s) with exception - FOCOM-->>Cloud Maintainer: 10.3 Response to Uncordon O-Cloud Node(s) with exception - end - - Note right of FOCOM: End Use Case - -``` - -UML Sequence Diagram for Node Cordon and Uncordon. Lifelines: Personnel (Cloud Maintainer), Service Management & Orchestration Framework (rApp & Non-RT RIC, FOCOM), and O-Cloud Platform (IMS). The diagram shows two main procedures: O-Cloud Node(s) Cordon Procedure and O-Cloud Node(s) Uncordon Procedure, each with success and exception paths. - -Figure 3-78: Node Cordon and Uncordon - -## 3.13 Heartbeat Monitoring Use Cases - -### 3.13.1 Heartbeat Subscription Use Case - -#### 3.13.1.1 High Level Description - -This Use Case supports subscription to an IMS heartbeat. SMO or other entities will be able to subscribe to receiving heartbeat messages from the IMS to detect reachability failures to the IMS. The subscription will include, the subscriber callback endpoint, heartbeat messages period and missed heartbeat message threshold(s) to trigger failure. - -NOTE: Heartbeat messages will be defined in the Heartbeat UC. - -#### 3.13.1.2 Sequence Description - -| USE CASE STAGE | EVOLUTION / SPECIFICATION | <
>

Related Use | -|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------| -| Use Case Title | Heartbeat Subscription (IMS) | | -| Goal |

This use case describes a flow where one or more consumers subscribe to receiving heartbeat messages from the IMS in order to detect communication failures.

Each SUBSCRIBER has a consumer subscription identifier. There is one consumer subscription identifier per subscription. It doesn't have to be unique for that subscription. The consumer subscription identifier is a character string that can be associated with meta-data within the SMO.

| | -| Actors and Roles |

SMO (FOCOM) – The FOCOM within the SMO or other entities.

IMS – The IMS within the O-Cloud.

| | -| Assumptions |

There can be multiple subscribers to exchange heartbeat messages with the IMS.

Each subscription is associated with one subscriber. Thus, each subscription will only go to one endpoint. Thus, there cannot be multiple endpoints for single subscription.

The subscriber may not be the ultimate consumer of the HB. The subscriber is not necessarily the same entity as the endpoint for notifications.

| | -| Preconditions |

CONNECTIVITY – The Subscriber has connectivity to the IMS by some mechanism.

O-Cloud OPERATIONAL – O-Cloud is installed, operating, and the IMS in the O-Cloud has registered with SMO.

| | -| Begins when |

The use case is triggered when a subscriber wishes to:

  1. (1) NOTIFICATION – A subscriber wishes to subscribe to receiving heartbeat messages from the IMS.
  2. (2) HEARTBEAT SUBSCRIPTION CHANGE – To change the characteristics of a heartbeat subscription a user would need to create a new heartbeat subscription followed by a deleting the previous heartbeat subscription. This is done because there is no heartbeat subscription update procedure.
| | - -| | | | -|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | (3) OPERATOR INITIATED - An O-Cloud operator may also initiate a subscription. | | -| Step 1 (M) | NOTIFICATION CRITERIA – This gives a notification criterion which initiates the subscription.

The subscription criteria will indicate the endpoint for the IMS to send heartbeat, period and missed heartbeat pulse threshold(s) to trigger failure. | | -| Step 2 (M) | SUBSCRIPTION – The subscriber sends a heartbeat subscription to the IMS. The subscription includes the Consumer Subscription Identifier . | | -| Step 3 (M) | CALLBACK REACHABILITY CHECK – A Reachability Check is performed between the subscriber and IMS. This is a connectivity and authorization check. | | -| Step 4 (ALT) | REACHABILITY SUCCESS – This step indicates that the reachability check has passed successfully. | | -| Step 5 (ALT) | REACHABILITY FAILURE – This step indicates that the reachability check has failed. | | -| Step 6 (ALT) | SUBSCRIPTION DENIED (FAILURE) – The IMS has failed the reachability check. IMS will proceed to deny the heartbeat subscription. | | -| Step 7 (ALT) | SUBSCRIPTION STATUS (FAILURE) – If the reachability check has failed, the subscription status will indicate a failure. The use case will end at this point. This is a return to Step 2. | | -| Step 8 (M) | SUBSCRIPTION ACKNOWLEDGE – The IMS indicates a subscription acknowledge. This essentially indicates a success for the heartbeat subscription. (Optional) The consumer subscription identifier may be passed back in the subscription acknowledge. | | -| Step 9 (M) | SUBSCRIPTION STATUS (SUCCESS) – A subscription status will indicate a success back to O-Cloud Operator. This is a return to Step 1. | | -| Ends when | This use case ends when a heartbeat subscription status has been sent successfully or on one of the failure cases, when there was a subscription failure. | | -| Exceptions | FAILURE CASE 1: FAILURE INDICATION - The Subscription acknowledge indicates a failure.

FAILURE CASE 2: CONNECTIVITY ISSUE - Can't reach the publisher, the reachability check has failed.

ALTERNATE CASE 1: VALIDITY CHECK – A validity check confirms the reachability of the callback endpoint, checking that the IMS has permission to reach the consumer through a TLS connection. If a validity check is performed AND it fails, this would lead to Fail Case 2 (Connectivity Issue). | | -| Post-conditions | SUCCESS: The IMS has the subscriber call-back (a fully qualified URL), and it is persisted. The IMS has created its own internal association for heartbeat subscription which includes the consumer subscription identifier, the call-back URL and along with heartbeat message period and thresholds.

FAILURE: The heartbeat subscription operation has failed. See the exception cases. | | - -| | | | -|--------------|-----------------------------------------------------|--| -| Traceability | [REQ-ORC-02-15], [REQ-ORC-02-105], [REQ-ORC-02-106] | | -|--------------|-----------------------------------------------------|--| - -3.13.1.3 UML Sequence Diagram - -![UML Sequence Diagram for Heartbeat Subscription. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows the interaction for an IMS Heartbeat Subscription Use Case, including preconditions, subscription steps, a reachability check with success and failure cases, and the final subscription status.](d4a6d3795fe79e002987abc462a30f61_img.jpg) - -The sequence diagram illustrates the interaction for the **IMS Heartbeat Subscription Use Case**. The lifelines are **Personnel (O-Cloud Operator)**, **Service Management & Orchestration Framework (Subscriber) (FOCOM)**, and **O-Cloud Platform (Publisher) (IMS)**. - -**Preconditions:** - SMO has connectivity to O-Cloud - O-Cloud has registered its IMS with the SMO - -**Sequence of Messages:** - -- 1 Notification Criteria:** Personnel sends a message to FOCOM. -- 2 Subscription:** FOCOM sends a message to IMS. Note: *Subscribers have consumer subscription identifier.* -- 3 Callback Reachability Check:** IMS sends a message to FOCOM. Note: *Subscription has consumer subscription identifier.* -- alt [If Reachable and Authorized]:** - - 4 Reachability Success:** IMS sends a dashed return message to FOCOM. - - Failure Case:** - - 5 Reachability Failure:** IMS sends a dashed return message to FOCOM. - - 6 Subscription Denied (Failure):** IMS sends a dashed return message to FOCOM. - - 7 Subscription Status (Failure):** FOCOM sends a dashed return message to Personnel. - - Use Case Ends:** A note indicating the end of the failure case. -- 8 Subscription Acknowledge:** IMS sends a message to FOCOM. Note: *Subscription Entry is created.* -- 9 Subscription Status (Success):** FOCOM sends a message to Personnel. - -The sequence concludes with the **Heartbeat Subscription End Use Case**. - -UML Sequence Diagram for Heartbeat Subscription. Lifelines: Personnel (O-Cloud Operator), Service Management & Orchestration Framework (Subscriber) (FOCOM), and O-Cloud Platform (Publisher) (IMS). The diagram shows the interaction for an IMS Heartbeat Subscription Use Case, including preconditions, subscription steps, a reachability check with success and failure cases, and the final subscription status. - -Figure 3-79: Heartbeat Subscription - -## 4 Orchestration Requirements - -The following section contains requirements on the O-Cloud, SMO, O1 and O2 based on the Orchestration Use Cases above. - -### 4.1 General Requirements - -| | | | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------| -| [REQ-ORC-GEN1] | The O-RAN SMO shall support the creation of a globally unique identifier (Global O-Cloud ID) which can uniquely identify an O-Cloud instance in a provider's network. | Use Case 3.1.1 | -| [REQ-ORC-GEN2] | The O-RAN SMO shall be able to create an inventory placeholder based on a Global O-Cloud ID for an O-Cloud expected to be managed by the SMO. | Use Case 3.1.1 | -| [REQ-ORC-GEN3] | The O-RAN SMO shall be able to initiate an O-Cloud build out by loading the first O-Cloud server and providing a “blueprint” of the functionality and resources needed. | Use Case 3.1.2 | -| [REQ-ORC-GEN4] | The O-RAN O-Cloud Infrastructure Management Services shall be able to orchestrate the control plane and resource nodes from O-Cloud Nodes as they are detected. | Use Case 3.1.2 | -| [REQ-ORC-GEN5] | The O-RAN O-Cloud Infrastructure Management Services shall be able to notify the SMO when it has completed the O-Cloud build and is ready to be integrated to the SMO. | Use Case 3.1.2 | -| [REQ-ORC-GEN6] | The O-RAN O-Cloud Infrastructure Management Services shall be able to provide SMO with information about its current SW inventory and platform software | Use Case 3.1.3 | -| [REQ-ORC-GEN7] | The O-RAN SMO shall be able to verify an O-Cloud instance is at the SW inventory or build expected for platform software for given deployment | Use Case 3.1.3 | -| [REQ-ORC-GEN8] | The SMO shall be able to configure an O-Cloud to notify the SMO of O-Cloud Configuration Changes, Faults detected within, and performance of O-Cloud Nodes. | Use Case 3.1.3 | -| [REQ-ORC-GEN9] | The O-RAN O-Cloud Infrastructure Management Services shall be able to provide on demand a list of its DMS with the resource locations that each can support and information linking the DMS with the deployment descriptor model types that each support. | Use Case 3.1.3 | -| [REQ-ORC-GEN10] | The O-RAN O-Cloud Infrastructure Management Services shall be able to provide on demand a list of resource build configurations (aka "flavors") that it can currently support. | Use Case 3.1.4 | -| [REQ-ORC-GEN11] | The O-RAN O-Cloud Infrastructure Management Services shall be able to provide on demand a report of capacity that it could support based on the "flavors" it has defined. | Use Case 3.1.4 | -| [REQ-ORC-GEN12] | The O-RAN O-Cloud Infrastructure Management Services shall be able to provide on demand a report of availability that it can still support and utilization, based on the "flavors" it has defined. | Use Case 3.1.4 | -| [REQ-ORC-GEN13] | The O-RAN O-Cloud Infrastructure Management Services shall be able to notify the SMO when there is a change in Inventory status. | Use Case 3.1.4 | -| [REQ-ORC-GEN14] | The O-RAN O-Cloud Infrastructure Management Services shall be able to detect, configure and incorporate new O-Cloud Nodes into the O-Cloud instance according to the rules identified in the O-Cloud blueprint. | Use Case 3.1.5 | - -| | | | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| -| [REQ-ORC-GEN15] | The O-RAN O-Cloud Infrastructure Management Services shall be able to notify the SMO when resources which can affect the total capacity of the O-Cloud are changed. | Use Case 3.1.5 | -| [REQ-ORC-GEN16] | The O-RAN O-Cloud Infrastructure Management Services shall be able to support secure get of software packages of specific version from a server within the SMO for the purpose of upgrading and downgrading the O-Cloud software build. | Use Case 3.1.6 | -| [REQ-ORC-GEN17] | The O-RAN O-Cloud Infrastructure Management Services shall be able to evaluate a downloaded software package and verify that it can be activated without impacting applications or networks executing on the affected O-Cloud resources. | Use Case 3.1.6 | -| [REQ-ORC-GEN18] | The O-RAN SMO shall be able to separate requests for managing an O-Cloud and managing O-RAN Network Functions on the O-Cloud. | Use Case 3.2.1 | -| [REQ-ORC-GEN19] | The O-RAN SMO shall determine which locations within the O-Cloud that should be used for implementing an end-to-end service or an xAPP if these are not specified in the service request | Use Case 3.2.1, 3.3.2 | -| [REQ-ORC-GEN20] | The O-Cloud Deployment Management Services shall be able to use a descriptor to orchestrate the creation and management of NF Deployments. | Use Case 3.2.1 | -| [REQ-ORC-GEN20a] | The O-Cloud Deployment Management Services shall have the capability to handle the NF Deployment lifecycle requests according to the NF Deployment's requirements and the capabilities and capacities of the O-Cloud Node Clusters. | Use Cases 3.2.1, 3.2.2, 3.2.3, and 3.2.4 | -| [REQ-ORC-GEN20b] | The O-Cloud Deployment Management Services shall have the capability to allocate O-Cloud Node Cluster resources on request from the SMO to instantiate an NF Deployment. | Use Case 3.2.1
See also REQ-ORC-GEN20a | -| [REQ-ORC-GEN21] | The O-RAN SMO shall be able to restore a NF to a previous configuration as needed for network recovery. | Use Case 3.4, see also [8] | -| [REQ-ORC-GEN22] | The O-Cloud Deployment Management Service shall be able to allocate new resources to an NF Deployment on request from the SMO in order to support scale out of an NF Deployment. | Use Case 3.2.2
See also REQ-ORC-GEN20a | -| [REQ-ORC-GEN23] | The O-Cloud Deployment Management Service shall be able to deallocate resources from an NF Deployment on request from the SMO in order to support scale in of an NF Deployment. | Use Case 3.2.3
See also REQ-ORC-GEN20a | -| [REQ-ORC-GEN24] | The O-Cloud shall be able to allocate and deallocate VLAN IDs upon request from SMO (FOCOM). | Use Case 3.9.1, 3.9.2 | -| [REQ-ORC-GEN25] | The O-Cloud shall support network connectivity to attach NFs to the required endpoints within one location/site. | Use Case 3.10.1,
3.10.2 | -| [REQ-ORC-GEN26] | The O-Cloud shall be able to connect the NF's endpoint to the endpoint at O-Cloud Gateway so that it can be connected to the external entity. | Use Case 3.10.1,
3.10.2 | -| [REQ-ORC-GEN27] | The O-Cloud shall support a reservation mechanism for Network Segment(s) (e.g., VLAN ID) based upon the request triggered via FOCOM over the O2ims interface.

NOTE: The reservation process includes that the reserved ID(s) is returned to the FOCOM | Use Case 3.10.1,
3.10.2 | - -| | | | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------| -| [REQ-ORC-GEN28] | The O-Cloud shall support mapping the ports connecting the O-Cloud Site Network Fabric and ports connecting to the transport (e.g., Transport Network Element) on the O-Cloud Gateway (e.g., VRF) when deployed. | Use Case 3.10.1,
3.10.2 | -| [REQ-ORC-GEN29] | The SMO (FOCOM/NFO) shall support the capability to receive recommendations to drain O-Cloud node(s). | Use Case 3.12.1 | -| [REQ-ORC-GEN30] | All detected faults shall be logged in a Fault Log(s) by the O-Cloud Resource detecting the fault.
NOTE: Fault logs can be kept remotely or locally by the O-Cloud Resource. | Use Case 3.7.8, 3.7.10

(Log Query, Logging Configuration Use Case) | -| [REQ-ORC-GEN31] | The SMO (FOCOM) shall support the capability to receive recommendations to Cordon O-Cloud Node(s). | Use Case 3.12.3 (O-Cloud Cordon and Uncordon) | -| [REQ-ORC-GEN32] | The SMO (FOCOM) shall support the capability to receive recommendations to Uncordon O-Cloud Node(s). | Use Case 3.12.3 (O-Cloud Cordon and Uncordon) | -| [REQ-ORC-GEN33] | The SMO (NFO) shall support the capability to send NF Deployment Software Modification request to the O-Cloud (DMS) over O2 interface. | Use Case 3.2.4 | -| [REQ-ORC-GEN34] | The O-Cloud Deployment Management Service shall be able to allocate new resources to an NF Deployment on request from the SMO in order to support software modification of an NF Deployment. | Use Case 3.2.4

See also REQ-ORC-GEN20a | -| [REQ-ORC-GEN35] | The O-Cloud Deployment Management Service shall be able to deallocate resources from an NF Deployment on request from the SMO in order to support software modification of an NF Deployment. | Use Case 3.2.4

See also REQ-ORC-GEN20a | -| [REQ-ORC-GEN36] | All logged events in O-Cloud logs (e.g. Alarm, Fault, Debug) shall be Date and Time stamped | Use Case 3.7.8 (Log Query) | -| [REQ-ORC-GEN37] | The consumer (e.g., SMO) shall have the appropriate identification, privileges, and authorization to invoke an O2 operation (e.g., Scale Out, Log Query, Performance Management Configuration). | All Use Cases | - -## 4.2 Orchestration Requirements Relating to O1 - -Defines requirements for O-RAN managed function IM elements and FM/PM elements needed for orchestration using the O1 interface. - -| | | | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------| -| [REQ-ORC-O1-1] | The O-RAN SMO shall be able to subscribe to notification of configuration events, fault events and performance measurements from an O-RAN NF instantiated on an O-Cloud, using the O1 interface. | Use Case 3.2.1 | -| [REQ-ORC-O1-2] | An O-RAN NF instantiated on an O-Cloud shall be able to send notification of configuration changes to the O-RAN SMO using the O1 interface. | Use Case 3.3.2, 3.4 | - -NOTE: These requirements may overlap with those in [5] and may be moved to [5] in future. - -## 4.3 Orchestration Requirements Relating to O2 - -| | | | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------| -| [REQ-ORC-O2-1] | The O-RAN SMO shall be able to provide a boot image for a remote node using the O2 interface. | Use Case 3.1.2 | -| [REQ-ORC-O2-2] | The O-RAN SMO shall be able to send a cloud descriptor, (i.e., cloud deployment and configuration files) for initial cloud startup using the O2 interface. | Use Case 3.1.2 | -| [REQ-ORC-O2-3] | The O-RAN SMO shall be able to send a Query Information request to query the O-Cloud for objects and attributes such as SW inventory using the O2 interface. | Use Case 3.1.3, 3.1.11 | -| [REQ-ORC-O2-4] | The O-Cloud shall be able to receive a request to download software sent to it from the SMO using the O2 interface, such as request for download of an xAPP deployment. | Use Case 3.1.3, 3.3.2 | -| [REQ-ORC-O2-5] | The O-RAN SMO shall be able to subscribe to notification of configuration events, fault events and performance measurements from the O-Cloud using the O2 interface. | Use Case 3.1.3 | -| [REQ-ORC-O2-6] | The O-RAN SMO shall be able to query the O-Cloud for the DMS end points it supports using the O2 interface. | Use Case 3.1.3 | -| [REQ-ORC-O2-7] | The O-RAN SMO shall be able to query the O-Cloud for attributes such as capabilities and capacities using the O2 interface. | Use Case 3.1.4 | -| [REQ-ORC-O2-8] | The O-Cloud shall be able to send asynchronous events to the SMO when available capabilities or capacities are changed, including when new hardware is added, using the O2 interface. | Use Case 3.1.4, 3.1.5 | -| [REQ-ORC-O2-9] | The O-Cloud shall be able to asynchronously notify the SMO when a software update (upgrade or downgrade) completes, using the O2 interface. | Use Case 3.1.6 | -| [REQ-ORC-O2-10] | The O-RAN SMO shall be able to request the O-Cloud to instantiate a NF Deployment using cloud resources through the O2 interface. | Use Case 3.2.1 | -| [REQ-ORC-O2-11] | The O-RAN SMO shall be able to request the O-Cloud to terminate NF Deployment using O2 interface. | Use Case 3.2.5 | -| [REQ-ORC-O2-12] | The O-RAN SMO shall be able to request the O-Cloud to heal NF Deployment(s) through the O2 interface.

NOTE: The NF Deployment could be restarted (stop and start) or its associated resources be reallocated/replaced on the same or different O-Cloud Nodes. Alternatively, to perform service recovery, new NF Deployment instances can be created on O-Cloud Nodes with resources of equivalent characteristics and profile as defined in that NF deployment descriptors and cloud native descriptors. | Use Case 3.6.2 | -| [REQ-ORC-O2-13] | The O-RAN SMO shall be able to request the O-Cloud to heal O-Cloud Node(s) through the O2 interface.

NOTE: The O-Cloud Node could be restarted (stop and start), or be reallocated/replaced by other O-Cloud infrastructure resources. NF deployment requirements from the NF deployment descriptor and cloud native descriptors, that are available to O-Cloud DMS, shall be taken into consideration as part of the O-Cloud Node healing. | Use Case 3.6.3 | -| [REQ-ORC-O2-14] | The O-RAN SMO shall be able to issue a subscription to the O-Cloud to receive alarm event notifications using the O2 interface. | Use Case 3.7.1

(IMS O2 Alarm Subscription) | - -| | | | -|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [REQ-ORC-O2-15] | Each subscriber should have a consumer subscription identifier .
NOTE: The consumer subscription identifier is an identifier provided by the consumer that is reflected in the alarm and performance notifications. | Use Case 3.7.1, 3.7.4, 3.7.5, 3.8.2, 3.13.1
(IMS O2 Alarm Subscription, Alarm Subscription Query, Alarm Subscription Delete, Performance Subscription, Heartbeat Subscription) | -| [REQ-ORC-O2-16] | The IMS in the O-Cloud (alarm producer) shall be able to asynchronously notify the endpoint specified by the SMO (alarm consumer) of alarm notifications related to O-Cloud resources using the O2 interface. | Use Case 3.7.2
(IMS O2 Alarm Notification) | -| [REQ-ORC-O2-17] | The SMO shall be able to query the O-Cloud for alarms on O-Cloud resources with query criteria which define the alarm characteristics that the SMO is interested in using the O2 interface. | Use Case 3.7.3
(IMS O2 Alarm Query) | -| [REQ-ORC-O2-18] | The IMS O-Cloud shall return alarms in response to the SMO alarm query that match the alarm query criteria using the O2 interface. | Use Case 3.7.3
(IMS O2 Alarm Query) | -| [REQ-ORC-O2-19] | The SMO shall be able to query the O-Cloud for state and status information using the O2 Interface. This is called a functional status query. Furthermore, the SMO uses query criteria in the query to indicate specific kinds of state and status information it is interested in. | Use Case 3.1.7
(Functional Status Query) | -| [REQ-ORC-O2-20] | The IMS shall respond to a functional status query using the O2 Interface. The IMS does so by returning state and status information for the O-Cloud based on the query criteria. | Use Case 3.1.7
(Functional Status Query) | -| [REQ-ORC-O2-21] | The SMO shall be able to perform an Alarm Subscription query towards the IMS using the O2 Interface. | Use Case 3.7.4
(Alarm Subscription Query) | -| [REQ-ORC-O2-22] | The IMS shall be able to process and respond to an Alarm Subscription query from the SMO using the O2 Interface. | Use Case 3.7.4
(Alarm Subscription Query) | -| [REQ-ORC-O2-23] | The SMO shall be able to request for an Alarm Subscription delete towards the IMS using the O2 Interface. | Use Case 3.7.5
(Alarm Subscription Delete) | -| [REQ-ORC-O2-24] | The IMS shall be able to process and respond to an Alarm Subscription delete requests from the SMO using the O2 Interface. | Use Case 3.7.5
(Alarm Subscription Delete) | -| [REQ-ORC-O2-25] | The O-Cloud operator, SMO, or IMS shall be able to initiate an alarm synchronization operation using the O2 Interface. | Use Case 3.7.6
(Alarm Synchronization) | -| [REQ-ORC-O2-26] | The SMO shall correlate and resolve discrepancies by all alarms of interest from O-Cloud during alarm synchronization operation using the O2 Interface. | Use Case 3.7.6
(Alarm Synchronization) | -| [REQ-ORC-O2-27] | The O-Cloud operator or SMO shall be able to initiate an alarm acknowledge operation using the O2 Interface. | Use Case 3.7.7
(Alarm Acknowledge/ Clear) | -| [REQ-ORC-O2-28] | The O-Cloud operator or SMO shall be able to initiate an alarm clear operation using the O2 Interface. | Use Case 3.7.7
(Alarm Acknowledge/ Clear) | -| [REQ-ORC-O2-29] | The IMS shall be able to process and respond to an alarm acknowledge request from the SMO using the O2 Interface. | Use Case 3.7.7
(Alarm Acknowledge/ Clear) | - -| | | | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------| -| [REQ-ORC-O2-30] | The IMS shall be able to process and respond to an alarm clear request from the SMO using the O2 Interface. | Use Case 3.7.7
(Alarm Acknowledge/ Clear) | -| [REQ-ORC-O2-31] | The SMO shall be able to request to the IMS for PM Job(s) to be created using the O2 interface. | Use Case 3.8.1
(IMS PM Job Creation) | -| [REQ-ORC-O2-32] | The IMS shall be able to create PM Job(s) requested by the SMO. | Use Case 3.8.1
(IMS PM Job Creation) | -| [REQ-ORC-O2-33] | The consumer (SMO) shall be able to query the O-Cloud for any Log using the O2 Interface.

NOTE: The typical logs can be Alarm, Debug and Fault Logs.

The SMO shall be able to specify a Log Query filter in the Log Query request to provide details of what it is interested in. | Use Case 3.7.8
(Log Query Use Case) | -| [REQ-ORC-O2-34] | The consumer (SMO) shall be able to receive and process Log Files if the IMS returns files. | Use Case 3.7.8
(Log Query Use Case) | -| [REQ-ORC-O2-35] | The consumer (SMO) shall be able to accept an endpoint from the producer (IMS). The SMO shall be able to try to access the endpoint to retrieve those files. | Use Case 3.7.8
(Log Query Use Case) | -| [REQ-ORC-O2-36] | The producer (IMS) shall respond to a Log Query using the O2 Interface.

The IMS shall return either Log File(s) matching the Log Query request or an endpoint that a consumer can retrieve the Log File(s) at. | Use Case 3.7.8
(Log Query Use Case) | -| [REQ-ORC-O2-37] | The O-RAN SMO shall be able to request for a Performance Management Subscription towards the IMS (in the O-Cloud) using the O2 Interface to receive performance reporting data (file ready, event notifications, or streaming events). | Use Case 3.8.2
(Performance Management Subscription) | -| [REQ-ORC-O2-38] | The IMS shall be able to create a Performance Management Subscription when requested by a subscriber. The IMS shall issue a notification of the status of the Performance Subscription request. | Use Case 3.8.2
(Performance Management Subscription) | -| [REQ-ORC-O2-39] | When the subscription indicates that performance data should be sent (based on the subscription criteria), the IMS shall attempt to open a connection to a subscriber endpoint. If successfully opened, the IMS shall send a performance event notification to the subscriber. | Use Case 3.8.3
(Performance Measurement Event Notification Reporting) | -| [REQ-ORC-O2-40] | When the subscription indicates that performance data should be sent in a streaming session (based on the subscription filter), if there is not already a persistent connection, the IMS shall attempt to open a connection to a subscriber endpoint.

Alternatively, the consumer (FOCOM) may establish a communication session that can be connection based, or non-connection based to the producer (IMS) | Use Case 3.8.4
(Performance Measurement Streaming Reporting) | -| [REQ-ORC-O2-41] | Upon, successful establishment of a communication session, the IMS shall send a performance event notification to the subscriber. | Use Case 3.8.4
(Performance Measurement Streaming Reporting) | -| [REQ-ORC-O2-42] | When the subscription filter indicates that performance data should be sent in a file, the producer (IMS) shall attempt to open a connection to a consumer (subscriber) endpoint. | Use Case 3.8.5
(Performance Measurement File Reporting) | -| [REQ-ORC-O2-43] | The producer (IMS) shall send the Performance Data file(s), or the producer (IMS) shall send a file ready notification for the consumer to retrieve the files later over the O2 interface. | Use Case 3.8.5 | - -| | | | -|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | (Performance Measurement File Reporting) | -| [REQ-ORC-O2-44] | The consumer (FOCOM) shall be able to receive Performance Data file(s) from the producer (IMS) or receive a file ready notification. | Use Case 3.8.5
(Performance Measurement File Reporting) | -| [REQ-ORC-O2-45] | The O-RAN SMO shall be able to request provisioning of the base O-Cloud Site Network through the O2 interface, enabling infrastructure-level connectivity among O-Cloud Nodes. | Use Case 3.11.1, 3.1.2 | -| [REQ-ORC-O2-46] | The O-Cloud shall support the provisioning of the O-Cloud Site Network and the O-Cloud GW via FOCOM over the O2ims interface. See note. | Use Case 3.11.1, 3.1.2, 3.10.1, 3.10.2

NOTE: Provisioning of O-Cloud Site Network and O-Cloud GW is realized, when applicable based on the O-Cloud Site networking realization, by means of provisioning of network resources on the O-Cloud Site Network Fabric and O-Cloud Site GW. | -| [REQ-ORC-O2-47] | The FOCOM (SMO) shall be able to send a create Kubernetes (K8s) Cluster with user credentials and requested capability parameters for the K8s Cluster.

NOTE: These user credentials are later used to authorize the user to have access or use to the created K8s Cluster based on their role privilege (DMS privileges). | Use Case 3.11.2.2
(Create K8s Cluster) | -| [REQ-ORC-O2-48] | IMS in the O-Cloud shall be able to process a request to create Kubernetes (K8s) cluster based on requested capability parameters. | Use Case 3.11.2.2
(Create K8s Cluster) | -| [REQ-ORC-O2-49] | IMS shall clean up after an exception of the create an O-Cloud Node Cluster request.

NOTE: The specific details of actions or activities that are reversed to accomplish a “clean up” is left up to implementation. | Use Case 3.11.2.1
(Create Kubernetes (K8s) Cluster Use Case)

Use Case 3.11.2.2
(Create O-Cloud Node Cluster using Managed Infrastructure Template) | -| [REQ-ORC-O2-50] | The SMO (FOCOM) shall be able to request updating of the O-Cloud Resource state and status (functional status update) using the O2 Interface. | Use Case 3.1.8
(Functional Status Update) | -| [REQ-ORC-O2-51] | The IMS shall be able to process and respond to a functional status update request using the O2 Interface. | Use Case 3.1.8 (Functional Status Update) | -| [REQ-ORC-O2-52] | The consumer (SMO) shall be able to issue a Query O-Cloud Info Request which is a generalized query for any Inventory object and its associated inventory information over the O2 Interface. | Use Case 3.7.9, 3.8.11
(Alarm Dictionary Discovery Use Case, PM Dictionary Discovery Use Case) | -| [REQ-ORC-O2-53] | The producer (IMS) shall respond to the Query O-Cloud Info Request over the O2 Interface by providing the information associated with the request Inventory object(s).

NOTE: Upon receipt, the consumer (SMO) is expected to associate the new Alarm/PM Dictionaries with the newly discovered Resource Types. | Use Case 3.7.9, 3.8.11
(Alarm Dictionary Discovery Use Case, PM Dictionary Discovery Use Case) | - -| | | | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [REQ-ORC-O2-54] | An entity, or SMO, shall be able to perform Logging Management operations to administer, provision, and configure logging behavior using the O2 Interface.

Some examples include configuring the retention period of logs, activating logging, configuring the logging rotation method, and configure Log Levels. | Use Case 3.7.10

(Logging Configuration Use Case) | -| [REQ-ORC-O2-55] | An IMS shall be able to process a Logging Management operation from an entity or SMO requested over the O2 Interface. | Use Case 3.7.10
(Logging Configuration Use Case) | -| [REQ-ORC-O2-56] | The consumer (SMO) shall be able to perform a PM Job Query towards the IMS using the O2 Interface. | Use Case 3.8.6
(PM Job Query) | -| [REQ-ORC-O2-57] | The IMS shall be able to process and respond to an PM Job Query from the consumer (SMO) using the O2 Interface. | Use Case 3.8.6
(PM Job Query) | -| [REQ-ORC-O2-58] | The consumer (SMO) shall be able to issue a PM Job Delete request to delete PM Job(s) towards the IMS using the O2 Interface. | Use Case 3.8.7
(PM Job Delete) | -| [REQ-ORC-O2-59] | The IMS shall be able to process and respond to an PM Job Delete request from the consumer (SMO) using the O2 Interface. | Use Case 3.8.7
(PM Job Delete) | -| [REQ-ORC-O2-60] | PM Job(s) shall first be placed in a suspended state before they can be deleted. | Use Case 3.8.7
(PM Job Delete) | -| [REQ-ORC-O2-61] | The FOCOM (SMO) shall be able to send a delete O-Cloud Node Cluster request over the O2 IMS Interface. | Use Case 3.11.3.1 (Delete K8s Cluster Use Case)

Use Case 3.11.3.2 (Delete O-Cloud Node Cluster Created Using Managed Infrastructure Template Use Case) | -| [REQ-ORC-O2-62] | IMS in the O-Cloud shall be able to process a request to delete an O-Cloud Node Cluster. | Use Case 3.11.3.1 (Delete K8s Cluster Use Case)

Use Case 3.11.3.2 (Delete O-Cloud Node Cluster Created Using Managed Infrastructure Template Use Case) | -| [REQ-ORC-O2-63] | When the delete O-Cloud Node Cluster is done, IMS shall perform internal clean up and report resultant updates to O-Cloud inventory and communicate changes for those resources | Use Case 3.11.3.1 (Delete K8s Cluster Use Case)

Use Case 3.11.3.2 (Delete O-Cloud Node Cluster Created Using Managed Infrastructure Template Use Case) | -| [REQ-ORC-O2-64] | The O-Cloud shall support the attachment of the Network Functions to the O-Cloud Node Cluster Network via NFO over the O2dms interface.

NOTE: The relevant O-Cloud Node interfaces to connect to the O-Cloud Node Cluster Network shall be provisioned before being able to perform the attachment of the NF Deployments. | Use Case 3.10.1 (Network Slice Creation Use Case), 3.10.2 (Network Slice Deletion Use Case) | -| [REQ-ORC-O2-65] | The O-Cloud shall support provisioning of the O-Cloud GW ports connecting the Transport Network Element where the following options are possible (depending on the case):

I. The Network Segment (e.g., VLAN ID) used for handover shall be selected/reserved by the O-Cloud.

II. The O-Cloud shall be capable of receiving the Network Segment (e.g., VLAN ID) used for handover as an input for the O-Cloud internal configuration. | Use Case 3.10.1 (Network Slice Creation Use Case), 3.10.2 (Network Slice Deletion Use Case) | - -| | | | -|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------| -| [REQ-ORC-O2-66] | The consumer (SMO) shall be able to issue a PM Job Update request to update a PM Job's characteristics through request parameters towards the IMS using the O2 Interface. | Use Case 3.8.8
(PM Job Update) | -| [REQ-ORC-O2-67] | The IMS shall be able to process and respond to a PM Job Update request from the consumer (SMO) using the O2 Interface. | Use Case 3.8.8
(PM Job Update) | -| [REQ-ORC-O2-68] |

The IMS shall be able to update the measure selection criteria which in turn will cause the PM Job to update the different aspects of collection including the measured Resources, qualified Resource Types, collected Measures, and measure selection criteria.

NOTE: If currently running collections are affected by a PM Job update, it will be implementation specific as to what happens with data collection already in progress. For example, if a 5-minute interval PM Job is updated to now collect at 7-minute intervals and the update request arrives 2 minutes into the existing 5-minute interval. There would be an extra data point which could have a suspect flag.

| Use Case 3.8.8
(PM Job Update) | -| [REQ-ORC-O2-69] | The consumer (SMO) shall be able to issue a PM Job Suspend request to suspend a PM Job towards the IMS using the O2 Interface. | Use Case 3.8.9
(PM Job Suspend) | -| [REQ-ORC-O2-70] | The IMS shall be able to process and respond to a PM Job Suspend request from the consumer (SMO) using the O2 Interface. | Use Case 3.8.9
(PM Job Suspend) | -| [REQ-ORC-O2-71] | The consumer (SMO) shall be able to issue a PM Job Resume request to resume a PM Job towards the IMS using the O2 Interface. | Use Case 3.8.10
(PM Job Resume Use Case) | -| [REQ-ORC-O2-72] | The IMS shall be able to process and respond to a PM Job Resume request from the consumer (SMO) using the O2 Interface. | Use Case 3.8.10
(PM Job Resume Use Case) | -| [REQ-ORC-O2-73] | An entity, SMO, operator shall be able to issue an Alarm List Configuration request to update the Retention Period for the entire Alarm List over the O2 interface. The request may also include additional extension parameters specific to implementation. | Use Case 3.7.11
(Alarm List Configuration Use Case) | -| [REQ-ORC-O2-74] | The IMS in the O-Cloud shall be able to process and respond to an Alarm List Configuration request by adjusting the Retention Period or process additional extension parameters and respond with the results of the operation. | Use Case 3.7.11
(Alarm List Configuration Use Case) | -| [REQ-ORC-O2-75] | The SMO (FOCOM) shall be able to request an IMS Software Update towards the IMS using the O2 Interface | Use Case 3.1.9
(IMS Software Update) | -| [REQ-ORC-O2-76] | The O-RAN O-Cloud Infrastructure Management Services shall be able process and respond to an IMS Software Update request from the SMO (FOCOM) using the O2 Interface. | Use Case 3.1.9
(IMS Software Update) | -| [REQ-ORC-O2-77] | The O-Cloud shall be able to heal NF Deployment(s), triggered either by a request over O2-DMS or via auto-healing triggers inside the O-Cloud. | Use Case 3.6.2
(NF Deployment Level Healing) | -| [REQ-ORC-O2-78] | The O-Cloud shall be able to heal O-Cloud Node(s), triggered either by a request over O2-IMS or via auto-healing triggers inside the O-Cloud. | Use Case 3.6.3
(O-Cloud Node Level Healing) | - -| | | | -|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------| -| [REQ-ORC-O2-79] | The SMO (FOCOM) shall be able to request an update of a DMS software within an O-Cloud towards the IMS using the O2 Interface. | Use Case 3.1.10
(DMS Software Update) | -| [REQ-ORC-O2-80] | The O-RAN O-Cloud Infrastructure Management Services shall be able to process and respond to a DMS Software Update request from the SMO (FOCOM) using the O2 Interface, and to perform consequently the DMS software update according to the request. | Use Case 3.1.10
(DMS Software Update) | -| [REQ-ORC-O2-81] | The O-Cloud operator or SMO shall be able to initiate an alarm suppression activation, deactivation, query, and update operation using the O2 Interface. | Use Case 3.7.12.2
(Alarm Suppression) | -| [REQ-ORC-O2-82] | The IMS shall be able to process and respond to an alarm suppression activation, deactivation, query, and update request from the SMO using the O2 Interface. | Use Case 3.7.12.2
(Alarm Suppression) | -| [REQ-ORC-O2-83] | The IMS shall be able to notify the SMO using the O2 Interface when IMS autonomously activate, deactivate, and update an alarm suppression. | Use Case 3.7.12.3
(Alarm Suppression) | -| [REQ-ORC-O2-84] | If the PM Job has an embedded subscription, the PM Job deletion request shall cause the associated PM subscription to be also deleted. | Use Case 3.8.7 (Performance Measurement Job Delete Use Case) | -| [REQ-ORC-O2-85] | The SMO shall be able to perform a Performance Management Subscription query towards the IMS using the O2 Interface. | Use Case 3.8.12
(Performance Management Subscription Query Use Case) | -| [REQ-ORC-O2-86] | The IMS shall be able to process and respond to a Performance Management Subscription query from the SMO using the O2 Interface. | Use Case 3.8.12
(Performance Management Subscription Query Use Case) | -| [REQ-ORC-O2-87] | The SMO shall be able to perform a Performance Management Subscription update (embedded or normal) with an update order towards the IMS using the O2 Interface. | Use Case 3.8.13
(Performance Management Subscription Update Use Case) | -| [REQ-ORC-O2-88] | The IMS shall be able to process and respond to a Performance Management Subscription update using the update order in the request from the SMO using the O2 Interface. | Use Case 3.8.13
(Performance Management Subscription Update Use Case) | -| [REQ-ORC-O2-89] | The SMO shall be able to perform a Performance Management Subscription delete request towards the IMS using the O2 Interface. | Use Case 3.8.14
(Performance Management Subscription Delete Use Case) | -| [REQ-ORC-O2-90] | The IMS shall be able to process and respond to a Performance Management Subscription delete request from the SMO using the O2 Interface. | Use Case 3.8.14
(Performance Management Subscription Delete Use Case) | -| [REQ-ORC-O2-91] | The FOCOM (SMO) shall be able to send an update O-Cloud Node Cluster request over the O2ims Interface.

NOTE: The update request includes information to identify the O-Cloud Node Cluster update and the update (increase or decrease) requirements. | Use Case 3.11.4.1 (Update Kubernetes (K8s) Cluster))

Use Case 3.11.4.2 (Update O-Cloud Node Cluster using Managed Infrastructure Template) | -| [REQ-ORC-O2-92] | IMS in the O-Cloud shall be able to process a request to update a O-Cloud Node Cluster. | Use Case 3.11.4.1 (Update Kuberenetes (K8s) Cluster)

Use Case 3.11.4.2 (Update O-Cloud Node Cluster using | - -| | | | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| -| | | Managed Infrastructure Template) | -| [REQ-ORC-O2-93] | When the update O-Cloud Node Cluster is done, IMS shall update the appropriate inventory. | Use Case 3.11.4.1(Update Kubernetes (K8s) Cluster)
Use Case 3.11.4.2 (Update O-Cloud Node Cluster using Managed Infrastructure Template) | -| [REQ-ORC-O2-94] | The SMO (FOCOM/NFO) shall support the capability to send O-Cloud Node draining request to the O-Cloud (IMS/DMS) over O2 interface. | Use Case 3.12.2 (O-Cloud Node Draining Use Case) | -| [REQ-ORC-O2-95] | The SMO (FOCOM/NFO) shall support the capability to receive O-Cloud Node draining response from the O-Cloud (IMS/DMS) over O2 interface. | Use Case 3.12.2 (O-Cloud Node Draining Use Case) | -| [REQ-ORC-O2-96] | The IMS shall be able to process and respond to a Query Information request from the SMO using the O2 Interface. | Use Case 3.1.11 (Query Information Use Case) | -| [REQ-ORC-O2-97] | The SMO shall be able to issue an Alarm Purge request that specify alarms to be purged towards the IMS using the O2 Interface. | Use Case 3.7.13
(Alarm Purge Use Case) | -| [REQ-ORC-O2-98] | The IMS shall be able to process Alarm Purge request from the SMO using the O2 Interface by removing inactive alarms or acknowledge active alarms from the Alarm List and respond to the request back to the requestor. | Use Case 3.7.13
(Alarm Purge Use Case) | -| [REQ-ORC-O2-99] | The SMO shall be able to request for a Performance Management Configuration to update attribute(s) of specified object(s) towards the IMS using the O2 Interface. | Use Case 3.8.15
(Performance Management Configuration Use Case) | -| [REQ-ORC-O2-100] | The IMS shall be able process a Performance Management Configuration request from the SMO and return a success or partial success based on outcomes.
NOTE: If a Performance Management Configuration update has a mixture of valid object(s) and attribute(s) and non-existing object(s) and attribute(s), then the operation will only be completed for the configurable attribute(s). This situation would return a partial success from the IMS to the requestor. | Use Case 3.8.15
(Performance Management Configuration Use Case) | -| [REQ-ORC-O2-101] | The SMO (FOCOM) shall support the capability to send O-Cloud Node(s) Cordon request to the O-Cloud (IMS) over O2 interface | Use Case 3.12.3 (O-Cloud Cordon and Uncordon Use Case) | -| [REQ-ORC-O2-102] | The SMO (FOCOM) shall support the capability to send O-Cloud Node(s) Uncordon request to the O-Cloud (IMS) over O2 interface | Use Case 3.12.3 (O-Cloud Cordon and Uncordon Use Case) | -| [REQ-ORC-O2-103] | The SMO (FOCOM) shall support the capability to receive O-Cloud Node(s) Cordon response from the O-Cloud (IMS) over O2 interface | Use Case 3.12.3 (O-Cloud Cordon and Uncordon Use Case) | -| [REQ-ORC-O2-104] | The SMO (FOCOM) shall support the capability to receive O-Cloud Node(s) Uncordon response from the O-Cloud (IMS) over O2 interface | Use Case 3.12.3 (O-Cloud Cordon and Uncordon Use Case) | -| [REQ-ORC-O2-105] | The O-RAN SMO shall be able to request for a Heartbeat Subscription towards the IMS (in the O-Cloud) using the O2 Interface to receive a heartbeat messages. | Use Case 3.13.1
(Heartbeat Subscription Use Case) | -| [REQ-ORC-O2-106] | The IMS shall be able to create a Heartbeat Subscription when requested by a subscriber. The IMS shall issue a notification of the status of the Heartbeat Subscription request. | Use Case 3.13.1 | - -| | | | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------| -| | | (Heartbeat Subscription Use Case) | -| [REQ-ORC-O2-107] | The SMO (FOCOM) shall be able to send a create O-Cloud Node Cluster using Managed Infrastructure Template. | Use Case 3.11.2.3
(Create O-Cloud Node Cluster using Managed Infrastructure Template) | -| [REQ-ORC-O2-108] | IMS in the O-Cloud shall be able to process a request to create an O-Cloud Node Cluster using Managed Infrastructure Template. | Use Case 3.11.2.3
(Create O-Cloud Node Cluster using Managed Infrastructure Template) | -| [REQ-ORC-O2-109] | IMS in the O-Cloud shall be able to process a request to create Infrastructure Resources based on a declarative target. | Use Case 3.11.5.2 (Create Infrastructure Resources using Managed Infrastructure Template) | -| [REQ-ORC-O2-110] | IMS in the O-Cloud shall be able to process a request to update existing Infrastructure Resources based on a declarative target. | Use Case 3.11.5.3 (Update Infrastructure Resources using Managed Infrastructure Template) | -| [REQ-ORC-O2-111] | IMS in the O-Cloud shall be able to process a request to delete existing Infrastructure Resources based on a declarative target. | Use Case 3.11.5.3 (Update Infrastructure Resources using Managed Infrastructure Template) | -| [REQ-ORC-O2-112] | The SMO shall be able to issue Networking Infrastructure Create provisioning request(s) to fulfill the networking requirements for Node Clusters, including one or more end-to-end Networks scenarios e.g., Intra-O-Cloud Site Intra-Cluster connectivity, Intra-O-Cloud Site Inter-Cluster connectivity, Inter-O-Cloud Site Intra-Cluster connectivity, and connectivity to transport networks. | Use Case 3.11.6.1
(Create Networking Infrastructure across O-Cloud Sites with a Template Use Case) | -| [REQ-ORC-O2-113] | The IMS shall be able to process Networking Infrastructure Create provisioning request(s) to fulfill the networking requirements for Node Clusters, including one or more end-to-end Network connectivity scenarios e.g., connectivity for an Intra-O-Cloud Site Intra-Cluster connectivity, Intra-O-Cloud Site Inter-Cluster connectivity, Inter-O-Cloud Site Intra-Cluster connectivity, and connectivity to transport networks. | Use Case 3.11.6.1
(Create Networking Infrastructure across O-Cloud Sites with a Template Use Case) | -| [REQ-ORC-O2-114] | The IMS shall be able to process and respond to query Managed Infrastructure Template(s) request from the SMO using the O2 Interface | Use Case 3.11.7 (O-Cloud Managed Infrastructure Template Discovery Use Case) | -| [REQ-ORC-O2-115] | The FOCOM (SMO) shall be able to discover available O-Cloud Managed Infrastructure Template in an O-Cloud. | Use Case 3.11.7 (O-Cloud Managed Infrastructure Template Discovery Use Case) | -| [REQ-ORC-O2-116] | The O2 IMS interface shall be able to asynchronously notify the SMO of O-Cloud Managed Infrastructure Template addition or deletion in the O-Cloud. | Use Case 3.11.7 (O-Cloud Managed Infrastructure Template Discovery Use Case) | -| [REQ-ORC-O2-117] | The FOCOM (SMO) shall be able to discover available O-Cloud Logs in an O-Cloud. | Use Case 3.7.14 (Log Discovery Use Case) | -| [REQ-ORC-O2-118] | The O2 IMS interface shall be able to notify return a list the SMO of O-Cloud Logs to the SMO. | Use Case 3.7.14 (Log Discovery Use Case) | - -| | | | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------| -| [REQ-ORC-O2-119] | The SMO (FOCOM) shall be able to send a Provisioning Request create request towards IMS over O2-IMS Interface to create O-Cloud Node Cluster and corresponding Infrastructure Resources based on a declarative target. | Use Case 3.11.8.2 (Create an O-Cloud Node Cluster and Infrastructure Resources using MIT Use Case) | -| [REQ-ORC-O2-120] | IMS in the O-Cloud shall be able to process a Provisioning Request create request to create Node Cluster and a set of Infrastructure Resources based on a declarative target. | Use Case 3.11.8.2 (Create an O-Cloud Node Cluster and Infrastructure Resources using MIT Use Case) | -| [REQ-ORC-O2-121] | The FOCOM (SMO) shall be able to send a Provisioning Request update request towards IMS over O2 interface to update O-Cloud Node Cluster and corresponding Infrastructure Resources based on a declarative target. | Use Case 3.11.8.3 (Update O-Cloud Node Cluster and Infrastructure Resources using MIT) | -| [REQ-ORC-O2-122] | IMS in the O-Cloud shall be able to process a Provisioning Request update request to update existing Node Cluster and/or corresponding Infrastructure Resources based on a declarative target. | Use Case 3.11.8.3 (Update O-Cloud Node Cluster and Infrastructure Resources using MIT) | -| [REQ-ORC-O2-123] | The FOCOM (SMO) shall be able to send a Provisioning Request update request towards IMS over O2 interface to add and delete O-Cloud Node Cluster and/or corresponding Infrastructure Resources based on a declarative target. | Use Case 3.11.8.3 (Update O-Cloud Node Cluster and Infrastructure Resources using MIT) | -| [REQ-ORC-O2-124] | IMS in the O-Cloud shall be able to process a Provisioning Request update request that result in addition and deletion of existing Node Cluster and/or associated Infrastructure Resources based on a declarative target. | Use Case 3.11.8.3 (Update O-Cloud Node Cluster and Infrastructure Resources using MIT) | - -## 4.4 Requirements Relating to NF Deployment Descriptor - -The following section contains requirements on the Deployment Descriptor for NF Deployment. - -| | | | -|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------| -| [REQ-DESC-1] | The Deployment Descriptor shall contain deployment information that enables the SMO, together with other input data to deploy an NF Deployment. | Use case 3.2.1
(NF Deployment Instantiation) | -| [REQ-DESC-2] | The Deployment Descriptor shall contain lifecycle parameters that enable customization of an NF Deployment. | Use case 3.2.1
(NF Deployment Instantiation) | -| [REQ-DESC-3] | The Deployment Descriptor shall contain information related to cloud resource requirements. | Use case 3.2.1
(NF Deployment Instantiation) | - -## Annex A (Informative): Terminology Used in O-Cloud Requirements - -The following terms and definitions are used in the O-Cloud requirements. - -| Requirements Term | Description | -|----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| deployment descriptor | Deployment descriptor is a completed data model which provides an O-Cloud the necessary information to create a deployment. | -| deployment descriptor model type |

Deployment descriptors use a model type such as TOSCA, HELM, or HOT Templates to describe the deployment to be performed. The type of model used by the descriptor should be included in its metadata.

NOTE: HELM is a registered trademark of the Linux Foundation, in the United States and other countries. O-RAN is not affiliated with, endorsed or sponsored by the Linux Foundation.

| -| NF deployment | NF deployment (or “Deployment”) is defined in [9]. | -| NF deployment unit | Part of a NF deployment that may be individually scaled. | -| flavor | In the case of O-Clouds the deployment units are in defined patterns known as [deployment] flavors [2]. The flavors are part of the deployment descriptor. | -| capacity | This is the capacity that an entity is designed for. For each flavor defined the maximum that could be deployed should be reported to the SMO. Cloud Scale Up and Scale Down would affect these values and cause the change to be reported to the SMO. | -| utilization | This is the count that is currently allocated from the O-Cloud capacity, for each flavor. | -| availability | This is the count that could be allocated based on the capacity minus the utilization, for each flavor. | -| cloud descriptor | This is the outlined plan for the O-Cloud. From this plan the O-Cloud Infrastructure Management Services knows which pools are expected to be available as resources are discovered and what version of software is required for O-Cloud Nodes in each pool. | -| cloud blueprint | This is information about the functionality and resources needed in an O-Cloud build out. | - -## Annex (Informative): Change History - -| Date | Revision | Description | -|------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2023.11.28 | 09.00 | Incorporated 5 CRs for 2023 Nov train
#18 O2 OrchUC FM AlarmListConfiguration UseCase_v00.03
#21 DTAG.AO-2023.06.02-WG6-CR-0004-Performance_Measurement_Subscription-v02.00
#24 DTAG.AO-2023.09.22-WG6-CR-0006-Preinstalled PM Job_v01.00
#26 ERI-2023.09.11-WG6-CR-0052-OUC updates for AAL
#32 DCM-2023.10.11-WG6-ORCH-UC-O-Cloud_Node_Backup UC_v03
Fixed 2 bugs in Bug List
#1 Fixed Preconditions from "Valid User" to "Privilege" for consistency
#3 Editorial corrections | -| 2024.3.28 | 10.00 | Incorporated 2 CRs for 2024 Mar train
#29 DCM-2024.02.16-WG6-CR-0003-ORCH-UC Cluster templates and network alignments-v02
#33 ERI-2024.02.27-WG6-CR-0027-NF-Deployment-Use-Cases-Update-v02
Fixed a bug Bug List
#4 Editorial correction
Incorporated editorial comments in WG Approval Comment Wiki | -| 2024.7.26 | 11.00 | Incorporated 4 CRs for 2024 July train
#24 NOK 2024.05.28 WG6 CR Deployment NF Descriptor Requirements V01.02 https://oranalliance.atlassian.net/wiki/download/attachments/2210398393/DCM-2024.02.16-WG6-CR-0003-ORCH-UC_Cluster_templates_and_network_alignments-v02.docx?api=v2
#33 DELL.AO-2024.04.01-WG6-CR0008-ORCH UC-Logging Configuration-v00.05
#34 DELL.AO-2024.03.08-WG6-CR-0006-ORCH UC-Performance Management CR-v00.06
#36 DTAG-2023.08.28-WG6-CR-0005-3.2.1 Instantiate Network Function Deployment on O-Cloud-v15.03
Fixed 2 bugs in Bug List
#3 ORCH-UC Clause 4.4 (fixed the use case name to "NF Deployment Instantiation")
#4 ORCH-UC Clause 4.1 (fixed the use case name to "Logging Configuration")
Incorporated editorial comments in WG Approval Comment Wiki | -| 2024.12.10 | 12.00 | Incorporated 7 CRs for 2024 Nov train
DTAG-2024.07.24-WG6-CR-0010-3.2.5 NF Deployment Termination-v01.01
DTAG.AO-2024.09.02-WG6-CR-0008_O Cloud Pre Deployment_v01.00
ERI-2024.06.24-WG6-CR-0037-Scale-Out-NF-Deployment-Use-Case-Update-v09
ERI-2024.06.24-WG6-CR-0043-Scale-In-NF-Deployment-Use-Case-Update-v04
DCM-2024.10.30-WG6-CR-0004-ORCH-UC Clarify NW to which O-Cloud connects-v01
RHT.AO-2024.08.30-WG6-CR-0001-Provisioning-Cluster-Template-Use-Case-v000.8
RHT.AO-2024.09.23-WG6-CR-0001-Update-Using-Cluster-Template-Use-Case-v0.5
Incorporated editorial comments in WG Approval Comment Wiki | -| 2025.3.31 | 13.00 | Incorporated 8 CRs for 2025 Mar train
NEC.AO-2025.01.28-WG6-CR0002-ORCH-UC corrections in PM Event Notification reporting UC_v2.0
NEC.AO-2025.01.28-WG6-CR0003-ORCH-UC Replace incorrect UML Sequence diagram in Fault UC IMS Alarm Subscription Query_v1.00
NEC.AO-2025.01.24-WG6-CR001-ORCH-UC corrections in PM Job QueryUC_v1.00
NOK.AO-2025.01.31-WG6-CR0151-O2 PM NotificationReportingUC Update_v01.00
DTAG-2025.02.11-WG6-CR-0011-NF Deployment SW Modification-v03.00
DTAG.AO-2025.02.18-WG6-CR-0013-Performance Measurement File Reporting Use Case_v01.00
ERI-2025.02.25-WG6-CR-0067-NF-Deployment-Use-Cases-Future-Work-Items-v01
RHT-2024.10.01-WG6-CR-0003-Delete-Using-Cluster-Template-Use-Case-v05
Minor editorial corrections | -| 2025.7.18 | 14.00 | Incorporated 7 CRs for 2025 July train
DTAG-2024.09.03-WG6-CR-0009-Log Date and Time stamping requirement-v02.00 | - -| | | | -|------------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | NOK.AO-2023.12.07-WG6-CR0110-OrchUC_PrivilegePrecondition_ConsistencyUpdate_v03.00
NOK.AO-2025.04.25-WG6-CR0170-OrchUC_PMSubscription_UC_Editorials-v01.00
NOK.AO-2025.03.10-WG6-CR0152-End-to-End_Networking_Infrastructure_across_O-Cloud_Sites_UseCase_v03
ERI.AO-2025.04.20-WG6-CR-0069-TemplateBasedInfrastructureResourceProvisioningUseCases-CR-v04
DCM-2025.05.22-WG6-CR-0005-ORCH-UC-Clause_3_11_1_Network_provisioning_UC_term_updates-v04
RHT-2025.05.01-WG6-CR-0004-Cluster-Templates-Discovery-Use-Case-v0.7
Minor editorial corrections | -| 2025.11.27 | 15.00 | Incorporated 16 CRs for 2025 Nov train
NOK.AO-2025.05.02-WG6-CR0171-OrchUC_PMMgmt_SubscriptionCreate_Update-v02.00.docx
NEC.AO-2025.08.21-WG6-CR0007-Editorial corrections in PM Usecases_WG6.ORCH-USE-CASES_UC_v1.0.docx
ERI.AO-2025.07.15-WG6-CR-0084-NodeClusterAndInfrastructureResourcesProvisioningUsingTemplatesUseCases-CR-v06.docx
ATT-2025.06.11-WG6-CR-0002-Log-Discovery-Use-Case-v0.6.docx
DTAG.AO-2025.07.17-WG6-CR-0015-PM Job Notifications ORCH Update_v01.00.docx
DCM-2025.09.19-WG6-CR-0006-ORCH-UC-Clarify_Deployment_capability_and_requirement_v04.docx
RMI.AO-2025.09.25-WG6-CR-0025-Create-Using-MIT-Use-Case-v00.03.docx
RMI.AO-2025.09.25-WG6-CR-0024-Update-Using-MIT-Use-Case-v00.03.docx
RMI.AO-2025.09.25-WG6-CR-0023-Delete-Using-MIT-Use-Case-v00.03.docx
RMI.AO-2025.10.09-WG6-CR-0029-Networking-MIT-Use-Case-v00.03.docx
RMI.AO-2025.10.09-WG6-CR-0030-O-Cloud-MIT-Discovery-Use-Case-v00.03.docx
RMI.AO-2025.10.09-WG6-CR-0031-Provisioning-and-Update-Infrastructure-Resource-MIT-Use-Case-v00.02.docx
DCM-2025.10.06-WG6-CR-0007-ORCH-UC_Rollback_Cluster_by_using_ProvisioningRequest-v02.docx
RMI-2025.10.17-WG6-CR-0016-O-Cloud PM data streaming use case enhancement solution-v05.docx
RMI-2025.10.17-WG6-CR-0015-O-Cloud PM data streaming use case enhancement high level description-v04.docx
RMI-2025.10.17-WG6-CR-0017-O-Cloud PM data streaming use case enhancement requirement-v04.docx
Minor editorial corrections from Bugs List / Editorials (All Specs) and November 2025 WG Approval Comment Wiki . | \ No newline at end of file diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/00504fc688ebcf131ccbeff94dfc9939_img.jpg deleted file mode 100644 index b975e0520e41d035bd446098b6a0cebe767c3096..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/00504fc688ebcf131ccbeff94dfc9939_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f9cacd9423b594d3af34ddac0ebe31b1fed4f3356905280cba3e3a77c040ca4b -size 204274 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/01b37b45a159c6e8efb7e2f67f99ba68_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg deleted file mode 100644 index e0836a43ca0135ff9f91030c1fdb3cd7f9e9de78..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e272b906a714c64a395c3e6ab04c2c5c6adf73d75ff541783dbff0a12618686b -size 3089 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/09032127b49c74c07fdc4e0d5275a115_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/09032127b49c74c07fdc4e0d5275a115_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/09032127b49c74c07fdc4e0d5275a115_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0931f3e098bd4539041de11c50cec2d2_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0931f3e098bd4539041de11c50cec2d2_img.jpg deleted file mode 100644 index 880bfadf82c2a62b40d7f35733c401f1ad5cbc75..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0931f3e098bd4539041de11c50cec2d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bfcf905aa8e605b4f6e369b9263ab3c4bae07d64fb033baccc4fad3766411950 -size 138511 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/09fcf056902487318885284a6b43b08c_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/09fcf056902487318885284a6b43b08c_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/09fcf056902487318885284a6b43b08c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0d9149a10167a487a93c349f5d848b7d_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0d9149a10167a487a93c349f5d848b7d_img.jpg deleted file mode 100644 index bcdfdf61b6fc0428ba18f4afaf12faae7d488cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0d9149a10167a487a93c349f5d848b7d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5a954765a74ac32fb73d0b59090b42dcde73ed867cf04674a47b9d571e593797 -size 123180 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg deleted file mode 100644 index b7f7850de38fbe9c869ca736c49364243df0eb04..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:03f453ad47667d302030ac23d35462db8417742c1f6dd331edeb93a4095122bc -size 171913 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg deleted file mode 100644 index 46e604bab5d50fd31c0c67690f906d7a62e845b1..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0e30ef35d69bb9ea5d79f41ee2c0704b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:627f744a5d54ef5b50d0dc33f72186d7d19a07ac04053cc3eb96c21aa49beb4d -size 2918 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0e611959485447591664307862231ffd_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0e611959485447591664307862231ffd_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0e611959485447591664307862231ffd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0f666d2ebbad7fab84c7c4fb531ea932_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0f666d2ebbad7fab84c7c4fb531ea932_img.jpg deleted file mode 100644 index 8e403d3bcda6ee26ff07fd1f72c3d128d34620af..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0f666d2ebbad7fab84c7c4fb531ea932_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3825ad887654aa8c24c1276db3ceeb0432a41457014b7e5d728e56ea9d9854f8 -size 153135 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg deleted file mode 100644 index c56b30f1811f3d50bdb83bff694ecf0761c3ee2b..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/0f6e3cdce0f01d6ccceabcced508bb5b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1c0afc66d6ad9a453c79d1602fe7b8f5736902289d28dc1655e400d522b80728 -size 159199 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/11f18bf0233d812ad2604f88f3385d60_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/11f18bf0233d812ad2604f88f3385d60_img.jpg deleted file mode 100644 index fb7e16dbfb96d0fe700b85b753918ed22af25e9e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/11f18bf0233d812ad2604f88f3385d60_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95be025ab7c96d1059b3dfaf9bf0f96eb4ef4067f8c69dc13c252b6fa556c0f5 -size 213835 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1396371bb5cf61891981fff2e338ec58_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/14af2781d0bd19b98b10672b74daaca2_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/14af2781d0bd19b98b10672b74daaca2_img.jpg deleted file mode 100644 index 33d6b13140f4d06c8ed605676658e9b8997c50c4..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/14af2781d0bd19b98b10672b74daaca2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ece57ed1332f7d14b73f29942f7333db29d02bbbf903e8c225278dc070cb2220 -size 265692 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/16152cf1d84aea10848758f51a91ff6a_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/16152cf1d84aea10848758f51a91ff6a_img.jpg deleted file mode 100644 index 04e019434ef72d8e716ddf16952ffd50bf68104b..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/16152cf1d84aea10848758f51a91ff6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:77d81c6aceba54b454415e7471bc0122d9bff516cca36da89707412fc6a85a85 -size 120608 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/16c8aea7b68120358abcb5ef6ef3ae0b_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/16c8aea7b68120358abcb5ef6ef3ae0b_img.jpg deleted file mode 100644 index bf5864839f7b1ca68773c09ceec7e6ea0a94ec0c..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/16c8aea7b68120358abcb5ef6ef3ae0b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fa4b2bde1fe4642f038ef8bf77f8392d46152a136d4fe8618f9fcf33ebde1ba0 -size 92407 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1a1f0ff74dee05dae773437f24c5a996_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1a1f0ff74dee05dae773437f24c5a996_img.jpg deleted file mode 100644 index fb30684250d6f306bbcccd14493ceb236d2299ee..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1a1f0ff74dee05dae773437f24c5a996_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4423e40d3b98a7036462e1b190c5691f61a7463c6ae7ca7d7857e634a729bc19 -size 126293 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg deleted file mode 100644 index 433108ea16e8d1ad7f707eda20d598d4b859b807..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1ba419fcea9fa7639cbc3c7c80396fcde382680eeeabbf4fb53850a8baad5692 -size 95687 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1baaba7a6e54e77197475726c871067d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1baf92180f2964741688e8215d7183da_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1baf92180f2964741688e8215d7183da_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1baf92180f2964741688e8215d7183da_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg deleted file mode 100644 index 9a66bfd95f27b61a6efdb13e1c078e1c35868da7..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1ea7909aea2fb749a6fe98fbdb8cacae_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f8cb41109e754918097b46fa3e0b98da15f63ac02b29c1c2bf3e0c5d52adf593 -size 115305 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1fd763be1b7a05b52e554f0583617642_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1fd763be1b7a05b52e554f0583617642_img.jpg deleted file mode 100644 index 0ee574f7461883c43d221e8258b7fd0155472279..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/1fd763be1b7a05b52e554f0583617642_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ba9b15a08ff4ca88c84e62a0056cc77ec24eb8db74d38853813e7e3cc31f2b2c -size 127182 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/20f6eb79fde32ab3f6b6757552e424ce_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/227840abf8cd09f4f3e83336421daccb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/233a8b9743fe86cccae4bfca4aa9a0b0_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/233a8b9743fe86cccae4bfca4aa9a0b0_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/233a8b9743fe86cccae4bfca4aa9a0b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/27ac7312556b7c7fb279e4fb33be33cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/27c9c38b326b85de631d54a9ff1e2bd4_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/27c9c38b326b85de631d54a9ff1e2bd4_img.jpg deleted file mode 100644 index 3dae03a1d2a0b702bae55ca230563f7a14ceb30c..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/27c9c38b326b85de631d54a9ff1e2bd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15d9d3979ef2a56789ea6d919051f8a0e3ad1ac0ddd2d0ee43e926baece78d39 -size 150529 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2a185522b492253375ed16f0c515c230_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2a185522b492253375ed16f0c515c230_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2a185522b492253375ed16f0c515c230_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2b00743506f6a3bbd17af764162dc76d_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2b00743506f6a3bbd17af764162dc76d_img.jpg deleted file mode 100644 index 731f55362fed21a3cd09481b2d6d13eae676ce83..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2b00743506f6a3bbd17af764162dc76d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:cc70defa51223c2837b9851a6ddb8828f600c0dc842ff451c975979975602b1b -size 225967 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2e1d7b4c07a00dd0f26b51558abbe428_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2e1d7b4c07a00dd0f26b51558abbe428_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2e1d7b4c07a00dd0f26b51558abbe428_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2e4532799b1f5837a5d909b20ab68ab6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2f587210e4f97c32758c5972e2e83d20_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2f587210e4f97c32758c5972e2e83d20_img.jpg deleted file mode 100644 index efabcffa9c3fa0b9a8181809710a6fff98a46589..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/2f587210e4f97c32758c5972e2e83d20_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:810750de9b36c461fb9ab6eda0a074eeaf7636fb79564c52833e49e689c0e414 -size 197439 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg deleted file mode 100644 index 14030379bf64285067fa396ff50bab822948ca1d..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c29b7b773f76cee2da5316eb59a4a6a4340054ae6a4f2285d7362e4d6e04be7d -size 190513 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/347010b7ac06d3ae97927fde0f784d7c_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/347010b7ac06d3ae97927fde0f784d7c_img.jpg deleted file mode 100644 index a8c43a79317a14877f5d4dbb74fcdc1e22bff45d..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/347010b7ac06d3ae97927fde0f784d7c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7ad9d4805d97e371394e821138817049c0d754dec7cac11ca71c386daca615d9 -size 195437 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/351243fd59cdae993f191da9ebb48016_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/351243fd59cdae993f191da9ebb48016_img.jpg deleted file mode 100644 index e26e0cd3fc76280d39d5fc6831d0f6dccd80a3c0..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/351243fd59cdae993f191da9ebb48016_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e8add42bd00ce6c50912c6cd58db46f190759c53b22e7b9f2bc3cc91d673f501 -size 204417 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/35437f160e157760713aa85be471c3f3_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/35437f160e157760713aa85be471c3f3_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/35437f160e157760713aa85be471c3f3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/365fdce90bacd7a819819a2e05e70403_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/365fdce90bacd7a819819a2e05e70403_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/365fdce90bacd7a819819a2e05e70403_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/366398d17120ce12a2c36b95c54033c5_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/366398d17120ce12a2c36b95c54033c5_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/366398d17120ce12a2c36b95c54033c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/36790164991deef00875cc7875965a92_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/36790164991deef00875cc7875965a92_img.jpg deleted file mode 100644 index dfeaab87aa9c48b5bfb558be836788c20ea3233c..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/36790164991deef00875cc7875965a92_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2cbff33c1f7ff24d84ab9a529e71e42b52ed62badf7978d7ac007611e2836fdf -size 104753 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg deleted file mode 100644 index e0836a43ca0135ff9f91030c1fdb3cd7f9e9de78..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/36e2350ea1a3ef6ca68c655394300a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e272b906a714c64a395c3e6ab04c2c5c6adf73d75ff541783dbff0a12618686b -size 3089 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/37d5d6957e175201847002c556b5a29d_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/37d5d6957e175201847002c556b5a29d_img.jpg deleted file mode 100644 index e0836a43ca0135ff9f91030c1fdb3cd7f9e9de78..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/37d5d6957e175201847002c556b5a29d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e272b906a714c64a395c3e6ab04c2c5c6adf73d75ff541783dbff0a12618686b -size 3089 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/3b89d812329a65ab156184a40524adf0_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/3b89d812329a65ab156184a40524adf0_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/3b89d812329a65ab156184a40524adf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/3d885b841119080a2bcfd603a7afca63_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/3d885b841119080a2bcfd603a7afca63_img.jpg deleted file mode 100644 index d13179abd1215405f2cea5916f20c708c240bf76..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/3d885b841119080a2bcfd603a7afca63_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6b686d53bdaf57690290d6cb648e3c1b36ea45b887e8a4a9a7af2863e3ed2eee -size 255503 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/448ea8ec42a54ed159e2974fe85dd4f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4665bbd9c3079135f242a62a0e931eec_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4665bbd9c3079135f242a62a0e931eec_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4665bbd9c3079135f242a62a0e931eec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg deleted file mode 100644 index 6c7ff85a0e468cc4038331b5d786901ec03c32c6..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f026104931ada17105c99ecf65029c573d16bb50ad499ad1d29a6ee6afb218fe -size 3102 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4b241e690aacaf391e2b28dd9307575c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg deleted file mode 100644 index bbca4c369c38d64f3a438f9174159fe6cfd94261..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4d6f13ca04e51575f82581193c077f64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bb10ec02c7dffaf89e409439791ed29ae9b167d9bff7b9173413209563929802 -size 3144 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index bbca4c369c38d64f3a438f9174159fe6cfd94261..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bb10ec02c7dffaf89e409439791ed29ae9b167d9bff7b9173413209563929802 -size 3144 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg deleted file mode 100644 index d002842db0fe7d84a797ad59aa7e8b4e068484f2..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4e85fe330de2c4f5eea6de4b2a53c77f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b04e97193d4b2cfc5556dc9f98ae5f4f9361d61fff0ee9e80211a9d20b37bc5c -size 183958 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg deleted file mode 100644 index e5c7f505487bb87f3949fc1216a6868b2eedb5bb..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3c973b0eaf6e4b318f0a568170288a3213c501410c9afef51783614b32268bb0 -size 97578 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/527578a453197a501cd46c0d0e579cd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index c04293510fc8c567a3be39878e9e59ec76ce398e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d879ce8f00d0139ed00678477ecd5237c8cce4fcf42ea3a17986f977e955e756 -size 2946 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5492a5cd6785b64f9f3c7a3c54051aaa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/55a415876cf7b7c2509c0318bb857efa_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/55a415876cf7b7c2509c0318bb857efa_img.jpg deleted file mode 100644 index 497c45954c3bcf5b2f53496dfcfb13b61720d467..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/55a415876cf7b7c2509c0318bb857efa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:20da4532baed9968e7593aef6532653b818aa00681ea617261cf8c789416467b -size 193683 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/568031aac86c633aab96b734dba3835e_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/568031aac86c633aab96b734dba3835e_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/568031aac86c633aab96b734dba3835e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/573293af67ee571aef04bf725fcefbe5_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/573293af67ee571aef04bf725fcefbe5_img.jpg deleted file mode 100644 index 494c1811622d8606344f6ae7c8a35091caa7f842..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/573293af67ee571aef04bf725fcefbe5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c885ad8504e720aa416c3538fb24becb625fa4d12d04bfdc0c754dd3c570a13b -size 228481 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/575d7d345b3ec04393bb2ec720ebabca_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/575d7d345b3ec04393bb2ec720ebabca_img.jpg deleted file mode 100644 index 0a27186e609d1357a489bcc2e45e8f4d3db85cb2..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/575d7d345b3ec04393bb2ec720ebabca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ffee705c77d4d30f13a156728af688fef83102ec753e8228875f7fb00a4afbe9 -size 139031 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/59368942873b0c35eef79a7a985025dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/59edd779768a6eb448c9b0ca5402346e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5cf80bac69830ea773ac17c87e0ae24d_img.jpg deleted file mode 100644 index 58224a6314f1b63f2a7474612e80f7ee16476578..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5cf80bac69830ea773ac17c87e0ae24d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e8d7cfa691be7b9896f2046f9b2755ee0b749a8ea8a6a2bea1e6d7001c7919fb -size 173324 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5e185b54d270cd15d1299478a13f1f97_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5e185b54d270cd15d1299478a13f1f97_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5e185b54d270cd15d1299478a13f1f97_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5f533a4c9388beded5aba3c037ab7be8_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5f533a4c9388beded5aba3c037ab7be8_img.jpg deleted file mode 100644 index bbca4c369c38d64f3a438f9174159fe6cfd94261..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5f533a4c9388beded5aba3c037ab7be8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bb10ec02c7dffaf89e409439791ed29ae9b167d9bff7b9173413209563929802 -size 3144 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5f5a8699620b98137f36540ead9912f9_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5f5a8699620b98137f36540ead9912f9_img.jpg deleted file mode 100644 index 0a6403576ba04e768b33cf11c233ef93b68f24d2..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5f5a8699620b98137f36540ead9912f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f52646452bcb2c1bb08f8a2672121f1f0f3ccf5a54a5ee59632b5a383679cce3 -size 215606 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5fa61cb21e87cecbe7049420f633a811_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5fa61cb21e87cecbe7049420f633a811_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5fa61cb21e87cecbe7049420f633a811_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5fbe6b9515c3d8f7d2526ca5bfbd012d_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5fbe6b9515c3d8f7d2526ca5bfbd012d_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/5fbe6b9515c3d8f7d2526ca5bfbd012d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6059b0a3a051cc20b414d51a4e412f3e_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6059b0a3a051cc20b414d51a4e412f3e_img.jpg deleted file mode 100644 index 8c8acb787c0318293d747a2de94b469c378b99ef..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6059b0a3a051cc20b414d51a4e412f3e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7556144c3a9bcc962e0e6553ff84caca838bbfd5f24e2f4f8e28b3b758710ff5 -size 166724 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/624dbf9b985f5bd85e902ec59b87ba4f_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/624dbf9b985f5bd85e902ec59b87ba4f_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/624dbf9b985f5bd85e902ec59b87ba4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg deleted file mode 100644 index 1a4ed200f39b8897941bb9df1178cd2d649b472c..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/64cda8ce20067bc360ce2f3a5c9352b7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bb668ba0c45613d24ac9ac8f576bf5713dd812781f7d0db54531da945191f686 -size 127902 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/65b5e4a95d403df0ea5e8ff94f162a6a_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/65b5e4a95d403df0ea5e8ff94f162a6a_img.jpg deleted file mode 100644 index 179cb0da513a99f5d321f6b3808e4e932672e174..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/65b5e4a95d403df0ea5e8ff94f162a6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:932fd20b5493eac767419c0b8d3e3ccae37a3653543fc3926709f48ddd9560f0 -size 173375 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/65e8c0628536d6d4245e9ab46ba070c3_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/65e8c0628536d6d4245e9ab46ba070c3_img.jpg deleted file mode 100644 index 2b8e959e1be30ef8c101649b9897e8b3366e45fd..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/65e8c0628536d6d4245e9ab46ba070c3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5858fac031001e5d8634b2ef4951ee73afa7940df57e8c4c6f9c37f0c9ce11a8 -size 90802 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg deleted file mode 100644 index 423d6a0c5e18d06d6af2ca8860692fe630a12336..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9df2da4f4e8d26f6e39c4cd8dd1fd298bcd7cac9faffdd7be13a3aa991add6e9 -size 184851 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/67fd5cc2c3bec87e3a06d5ad92744560_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/67fd5cc2c3bec87e3a06d5ad92744560_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/67fd5cc2c3bec87e3a06d5ad92744560_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6860dd5d8bfc2c1b4d7fd8166307d800_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/686705f78594bdc18af4f9cb04b455e0_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/686705f78594bdc18af4f9cb04b455e0_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/686705f78594bdc18af4f9cb04b455e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/69467ece0a576b4c2ec3e0c89ba61527_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/69467ece0a576b4c2ec3e0c89ba61527_img.jpg deleted file mode 100644 index 89498486ef1e4aa5eb84f32495e3e637e56557ab..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/69467ece0a576b4c2ec3e0c89ba61527_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d1ad4f21dee7df368f589090bb9427d5f9dd9409eff079088517edb59cd8a267 -size 251539 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6983ff962c0a32659de18c30790e1519_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6983ff962c0a32659de18c30790e1519_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6983ff962c0a32659de18c30790e1519_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/69e5f1993021af230d08c08aac97d9df_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/69e5f1993021af230d08c08aac97d9df_img.jpg deleted file mode 100644 index 7ed9ed743a3c41cd284440c6a730e1199673d1b6..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/69e5f1993021af230d08c08aac97d9df_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a6f65028e1ca80c9ffb4c4ae80d9decc7e4b80b1bb2c8683a737713fde3cff5a -size 90810 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6d8454e3fdef6561c6f64adf0092e9b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6da6e06f73c5bf331c5e55773dc6d010_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg deleted file mode 100644 index bee4f92d2e79743b87eb2324a4d4a64c6422c958..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6ebc3724d8a9c6dac981f189ea2e77dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:164a6f5f54e6050468604519af047b8f0b2119182b35a15dd99acc1c09f50e35 -size 118199 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6f794c8c41326b510934ce3f3d622202_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/78b47bea9d645c52984f5f4c6740db05_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 2de94530e8cdf7d500a9dfde4bc75393c5d3fdb7..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ad551cf0160c0012b18cc98743e7db5a9de9969ef1230d147fcadde947c03666 -size 2951 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/79e1709a7317ead45379cbb8ff3ba802_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/79e1709a7317ead45379cbb8ff3ba802_img.jpg deleted file mode 100644 index a110057ec4bc3575b513d07a84d2a857415d61ac..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/79e1709a7317ead45379cbb8ff3ba802_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:151cd026a27a5fe55e6236c5c49d8b3c8075df567b1be8c992a5429959c0f1f6 -size 91752 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg deleted file mode 100644 index bbca4c369c38d64f3a438f9174159fe6cfd94261..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bb10ec02c7dffaf89e409439791ed29ae9b167d9bff7b9173413209563929802 -size 3144 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7e86b957cd3c33e57d22a8389947ce46_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7e86b957cd3c33e57d22a8389947ce46_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7e86b957cd3c33e57d22a8389947ce46_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7ed5d5770331f31ade15439a21c31425_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7ed5d5770331f31ade15439a21c31425_img.jpg deleted file mode 100644 index 8a20609cc3d88706ac3729a3aac99930782355a2..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7ed5d5770331f31ade15439a21c31425_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d75d3f456528f547d8d67cb5fdcea096c8ef82d71c5960d3cbb9387fb569060 -size 15745 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/898fb89a50d9ec1dfb4e425c816976a7_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/898fb89a50d9ec1dfb4e425c816976a7_img.jpg deleted file mode 100644 index 243ef91e14d381d366920b69a77dabd6b10b8b23..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/898fb89a50d9ec1dfb4e425c816976a7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5feff6ba9d4dfb5e8300342319303e4bf8cb1240dba2343c366a2be7b3b5fa88 -size 88916 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8b4befaffc5166da571069410e207aea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg deleted file mode 100644 index bbca4c369c38d64f3a438f9174159fe6cfd94261..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8bb3ad7f71de1324b1350d7b8711de25_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bb10ec02c7dffaf89e409439791ed29ae9b167d9bff7b9173413209563929802 -size 3144 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8c05782074bb11421b43f2d5d6799b62_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8c05782074bb11421b43f2d5d6799b62_img.jpg deleted file mode 100644 index ea15dee62a6206bacda3beca881506bf8b1a33e1..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8c05782074bb11421b43f2d5d6799b62_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:087784a6bd435218d1988ec6a25522ed7dad7e950dd588690f4450f4b01db932 -size 235545 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8f78b5d84dca49cf2769440c7942a27d_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8f78b5d84dca49cf2769440c7942a27d_img.jpg deleted file mode 100644 index 8abd86958c82c695f282e61273656a2b31bab384..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8f78b5d84dca49cf2769440c7942a27d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c677d423a2692e3410ab35fd1c091c39bc7daf1d0db849a809da384afabdb197 -size 234045 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg deleted file mode 100644 index 64a5700eb600b118e9b8d68571e6eda1e45ff672..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/8faeb7db381e28ab1ba06e9f48c19c6e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:245336d2f7749e68b7c0902975e00a64dfc22ad8a13cb9768c5a7dc06a3b7625 -size 232774 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/909e1cd5419742a8ea8a95a16a40d849_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/909e1cd5419742a8ea8a95a16a40d849_img.jpg deleted file mode 100644 index 49603713d0a01da87518d357a4592d696d758c26..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/909e1cd5419742a8ea8a95a16a40d849_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:99dad571bbbbe309f73ca4bcb1f20b589cb7e5051c996dfb5b8e89fd9ae21694 -size 176748 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/90ddb84c323b956e2d50a54d3f870566_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/90ddb84c323b956e2d50a54d3f870566_img.jpg deleted file mode 100644 index 22c7174ddf71e43b19d9071689f06a7f239b5006..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/90ddb84c323b956e2d50a54d3f870566_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bc96590842c003f717d840d2a86233cda2e87bfb7dd749a6d2d17fa890e45307 -size 119384 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9144d599bb5bf98cd607202d768a4956_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9144d599bb5bf98cd607202d768a4956_img.jpg deleted file mode 100644 index bbd322713a8aeb48ed88bc489d81f888935cd993..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9144d599bb5bf98cd607202d768a4956_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8daf9c1c89960fbef1ea6197fb2eb914ee486944f72f6cd930eb7cc184c8d9cd -size 158920 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg deleted file mode 100644 index 8ffcf98ac25d2d777f40552ac514e7f1ab6972c1..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/921f8fa0f7ce2c9956f20d33162c13a2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:dc0310afb0f135bd62182e6ae9f7ca9b5ac4c6bff409ada4051bb548a3e05c5d -size 139640 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/96950fc5bb426ec5054f9d2cf1ce0f7b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/99315a3665b263851e1ea8f65af6231b_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/99315a3665b263851e1ea8f65af6231b_img.jpg deleted file mode 100644 index 9ab8789e513c959bad473f936eb78afda99dcf43..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/99315a3665b263851e1ea8f65af6231b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:98ddbe1aeb396fcc433efb4299599f1365b9513eee92c81bd8c5552db40e40f2 -size 95008 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9b1ec0090070bdf52ea28763b8d52477_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9b1ec0090070bdf52ea28763b8d52477_img.jpg deleted file mode 100644 index 28532e085b7b1e2521a27589737494187325bc62..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9b1ec0090070bdf52ea28763b8d52477_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:42b2ca80f363e177196ddb9eaa694eed0be03808c35a7520d3502a50f706497e -size 84523 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9b3e75266694bdf164036baf1bb25422_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9b3e75266694bdf164036baf1bb25422_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9b3e75266694bdf164036baf1bb25422_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9c1d3678db4a12d5864cb2a4def1135d_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9c1d3678db4a12d5864cb2a4def1135d_img.jpg deleted file mode 100644 index f95daee109df0b47edac6b62ea9f3737bfc33e14..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9c1d3678db4a12d5864cb2a4def1135d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:079cd229cb95b55ea9e940cd68c7aaef6b75eef252275a9e7233edb2cba5f054 -size 118567 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9c34076a317aa1ad4225725b4b578f9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg deleted file mode 100644 index c287218cb088c3f462ae3012a088afcdb68ddeaa..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9cd6ff4a43174e4afe1cc5e4ea2fcae4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:26d56bbe566c89b4b128a4b69ecfe5c85be07efed5cf95d68d4ed1914fc7e3af -size 127013 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9e8ebf03cae78f4f81b697548c2d7250_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9e8ebf03cae78f4f81b697548c2d7250_img.jpg deleted file mode 100644 index 78bd163477e2c02b490d0b6873021fcc563819d1..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9e8ebf03cae78f4f81b697548c2d7250_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c35b7538dbfb6c512bd28c619f9392e138dd985a9a553badd8e92234b5c6746b -size 245614 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9eca164aaad7ddabe4856ac6ba1c5ef0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9f5f9afcedaa0d9b7991976f5000865c_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9f5f9afcedaa0d9b7991976f5000865c_img.jpg deleted file mode 100644 index 574c3699e413b613e924b806adde9a35116491ac..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/9f5f9afcedaa0d9b7991976f5000865c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:62e85c2d94de2ed41e082b145c71527d25f1299a92b8d44b817ea3ee8f41469f -size 225745 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a0e8fe7862a6d7341faf5dac275277cc_img.jpg deleted file mode 100644 index 827a96e75bdcf4fd17f25563ab52710a2a3e6398..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a0e8fe7862a6d7341faf5dac275277cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:79968a0aa273eaa8dc27e4899a9d0a0802d9ffcfbf35f2cbc7021f7dac6ddd59 -size 175610 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a2abc60c3ed8cd00bc8e6f9a7f4b64f0_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a2abc60c3ed8cd00bc8e6f9a7f4b64f0_img.jpg deleted file mode 100644 index 4fd93273fafb9d38a77f313f827b731308d86e30..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a2abc60c3ed8cd00bc8e6f9a7f4b64f0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:590ba79734887d93f61b4b6e203431b7554a49a2d24d702b113caa393f5cc596 -size 122065 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a2de7634ddc040dbb9bda8403c9b49b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a3d6b1f562612dbd5a5d7c4ce91999d1_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a3d6b1f562612dbd5a5d7c4ce91999d1_img.jpg deleted file mode 100644 index 5bb74c8387abaf250a15daecbcc3df3c9f15a251..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a3d6b1f562612dbd5a5d7c4ce91999d1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d5f907279f5970d076f86e5308576fe84a7cf6a11ce608c03cc665f2900bee2b -size 125731 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg deleted file mode 100644 index bbca4c369c38d64f3a438f9174159fe6cfd94261..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a5b5f7018c1568c86f11e01fb258093e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bb10ec02c7dffaf89e409439791ed29ae9b167d9bff7b9173413209563929802 -size 3144 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a5f09d21af8c3e909361c622a501c7f2_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a5f09d21af8c3e909361c622a501c7f2_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a5f09d21af8c3e909361c622a501c7f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a7450c80e88ad3f6ca1427ad84020998_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a7450c80e88ad3f6ca1427ad84020998_img.jpg deleted file mode 100644 index 273e2f27aab9f75daa6874080576304c5b650f98..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a7450c80e88ad3f6ca1427ad84020998_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6ee89d3b04aac26e8ad1ee18cc96af998d0d63d34aae2a2cd455351948545ff0 -size 209396 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index 46e604bab5d50fd31c0c67690f906d7a62e845b1..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:627f744a5d54ef5b50d0dc33f72186d7d19a07ac04053cc3eb96c21aa49beb4d -size 2918 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a93f84544e1dc2029d8b41292b8b5c03_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a93f84544e1dc2029d8b41292b8b5c03_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a93f84544e1dc2029d8b41292b8b5c03_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/a9f8bc87c084c4c84bae1128815c277c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg deleted file mode 100644 index 46e604bab5d50fd31c0c67690f906d7a62e845b1..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:627f744a5d54ef5b50d0dc33f72186d7d19a07ac04053cc3eb96c21aa49beb4d -size 2918 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg deleted file mode 100644 index 2cf7e703516e4d4fd16af871fb635f29e889bf24..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b0384c8e0ff826a8116ab2ff67dadc43_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:800fa30d908a4612677a66fc462ef91bfec4f18dcc33877c99a743368f37ebd8 -size 149132 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b0a5d736df5f6fe2c0c6dd800bb0ff9a_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b0a5d736df5f6fe2c0c6dd800bb0ff9a_img.jpg deleted file mode 100644 index 78b1858a3b9c27d22a64302fff2eb7632ecd9b45..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b0a5d736df5f6fe2c0c6dd800bb0ff9a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f44da37285676c8b5b0f8b9f1ea4d7bfbef39cfe3438258047cd75e28e025fe6 -size 127613 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b0e533f20bac2474664e1bebb7813606_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b51423b6c049f5b5fcde42e50b58f18b_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b51423b6c049f5b5fcde42e50b58f18b_img.jpg deleted file mode 100644 index 008a80db51a601c7335eff2432a2a848ed8cc2f1..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b51423b6c049f5b5fcde42e50b58f18b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:49fe724003772cb59a0913865016e8b6a4c99bbd2527c73c6eb6d9d5f7434faf -size 215265 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b7deb15a64425aa7a86d391b2f4c848f_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b7deb15a64425aa7a86d391b2f4c848f_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b7deb15a64425aa7a86d391b2f4c848f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg deleted file mode 100644 index 77a7b538d5e9d989f2788677abc66b6229ff0d10..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5f93befdb3b256c547e25739a5b7dc749785eb8066f7f782000cdd81ca759608 -size 51811 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/bb8abc0cc19db87acc1c3d7321599690_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/bfcea196796f3bc23aeb4499b396cab1_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/bfcea196796f3bc23aeb4499b396cab1_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/bfcea196796f3bc23aeb4499b396cab1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c0ef0292328b1602e278f6a0b2ee07e0_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c0ef0292328b1602e278f6a0b2ee07e0_img.jpg deleted file mode 100644 index 83a592cf7526a33443b9f711cff5fac1857b7068..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c0ef0292328b1602e278f6a0b2ee07e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:41138d58a9662455cc2308d6f210cce0605c03db0b2571ce467ca35ad13be886 -size 214610 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c5eb42ed730ecb12621fc63444830d4b_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c5eb42ed730ecb12621fc63444830d4b_img.jpg deleted file mode 100644 index bbca4c369c38d64f3a438f9174159fe6cfd94261..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c5eb42ed730ecb12621fc63444830d4b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bb10ec02c7dffaf89e409439791ed29ae9b167d9bff7b9173413209563929802 -size 3144 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c76f518c4d95210969837b001e52d73b_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c76f518c4d95210969837b001e52d73b_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c76f518c4d95210969837b001e52d73b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c9bfcc4c4ef694696c292b03de45d2bb_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c9bfcc4c4ef694696c292b03de45d2bb_img.jpg deleted file mode 100644 index 6da2a7d0f85a763580161e69fbabc1e5ab647262..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/c9bfcc4c4ef694696c292b03de45d2bb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bdf63e11279ba18aa873848272faf2f8c3c6c10d075386fc9289bcf054946a74 -size 129776 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/cd9d31fecf784261aecb1220c3fe10a5_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/cd9d31fecf784261aecb1220c3fe10a5_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/cd9d31fecf784261aecb1220c3fe10a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/cdb7ea1e3072c3b9885c63d496dc7d84_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/cdb7ea1e3072c3b9885c63d496dc7d84_img.jpg deleted file mode 100644 index 46e604bab5d50fd31c0c67690f906d7a62e845b1..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/cdb7ea1e3072c3b9885c63d496dc7d84_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:627f744a5d54ef5b50d0dc33f72186d7d19a07ac04053cc3eb96c21aa49beb4d -size 2918 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/cdfbee2c06c086fdee6cb58317c947e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d3253d5db64378db6e72b66b41067a5b_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d3253d5db64378db6e72b66b41067a5b_img.jpg deleted file mode 100644 index 8bc866b98edbc4a250586a59d330cec3d18528ed..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d3253d5db64378db6e72b66b41067a5b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ecf94c272bd9330aa2019fb410a3457620fb3f09e0c5f34319a3de94fe34b7db -size 131781 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d35a80e3faed208324083399568c7461_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d35a80e3faed208324083399568c7461_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d35a80e3faed208324083399568c7461_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d4a6d3795fe79e002987abc462a30f61_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d4a6d3795fe79e002987abc462a30f61_img.jpg deleted file mode 100644 index de63e9e633d240edb2447f26f6694f155e663210..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d4a6d3795fe79e002987abc462a30f61_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:641512bceeb32d547848b127d35f0cb5b583bdfa9acc9e68463bbdfb4c5c9578 -size 175358 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d79de2dd022d74722a84f1b2ffce691c_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d79de2dd022d74722a84f1b2ffce691c_img.jpg deleted file mode 100644 index bb4addf1bf184706c6efe957445b3cc305e194f9..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d79de2dd022d74722a84f1b2ffce691c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f9cccd3a9157acfc74a9bffc7b17119061ecd469573a0698d4eb7df61efb75c2 -size 105222 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d7b324ee9d9caae532ed5e898261c278_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d7b324ee9d9caae532ed5e898261c278_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d7b324ee9d9caae532ed5e898261c278_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d884367c84ba50f250499f79c4b4b950_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d884367c84ba50f250499f79c4b4b950_img.jpg deleted file mode 100644 index 1e3aa24f9ebeb168f227067c4901405ff47764e6..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d884367c84ba50f250499f79c4b4b950_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1dbea58cfc4953f7f26d4b70df3b2c34130467354289bba9c44e10df1b150b4f -size 91167 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index d02680c09b9f25e25698cf38e7a8e97654acd907..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c95b292178dfb712021c46bcfa3c976bd458658ee41343fb79806fb688c84897 -size 2914 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/dfafe39c233a62ec8ebd71e42992c14d_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/dfafe39c233a62ec8ebd71e42992c14d_img.jpg deleted file mode 100644 index 67471a87700eff41ad3a63b4e0a3db8688a23864..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/dfafe39c233a62ec8ebd71e42992c14d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe04637fbd852bc96fcce33b95157ed38b867b8877b3c913ab2ff8a182d3575f -size 105103 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/dfe556fea00682b09a59427aaf72051c_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/dfe556fea00682b09a59427aaf72051c_img.jpg deleted file mode 100644 index 25a5c7869e2ae9254e4595069e6cfb5a5d9e8f41..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/dfe556fea00682b09a59427aaf72051c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fda21e0b74721070445206c86e1d21b4ecc051363b93beb157cf0c76680a8e78 -size 132994 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e1e41cc8c8434891237529fedcbba418_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e1e41cc8c8434891237529fedcbba418_img.jpg deleted file mode 100644 index bbbcf89f56b8d4f68147cca5db5827671cc7f3d2..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e1e41cc8c8434891237529fedcbba418_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:300d080832ef3814a8c953323183152e61c7009e92ec2e38e3635699ebdd5ded -size 163504 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg deleted file mode 100644 index e0836a43ca0135ff9f91030c1fdb3cd7f9e9de78..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e339d97a55f726bb82f15798d7eb80b7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e272b906a714c64a395c3e6ab04c2c5c6adf73d75ff541783dbff0a12618686b -size 3089 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg deleted file mode 100644 index 89fe207976859dc0b13c30bd3eae3b5a3a956fdf..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a111b5939b9b630e9dfeba3ba6f74209d6b79062e0d515583b9c7f8aba593e3 -size 3114 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg deleted file mode 100644 index bbca4c369c38d64f3a438f9174159fe6cfd94261..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e6fd4575ef3cf7eb94822dd1ff429503_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bb10ec02c7dffaf89e409439791ed29ae9b167d9bff7b9173413209563929802 -size 3144 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg deleted file mode 100644 index 74556dab5a33e040d1f4d532a1d314d4e5694767..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:200007c35451fbe783230b6808c07d8445e99483742dad0e4f9237875683786f -size 175235 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg deleted file mode 100644 index 209e3f8e7cb30063f40b90fe8a1e059252c6f8e3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e9d7df9758d9a042bb17daa9842760db_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f814f427188316646a043c9dd9faebeee30626cc205860d56dad7055051cb144 -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e9f27efdab43ce5b3ecbe74f09c4cfe2_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e9f27efdab43ce5b3ecbe74f09c4cfe2_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/e9f27efdab43ce5b3ecbe74f09c4cfe2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg deleted file mode 100644 index 4b1c08d34e3b04fcb6ede00d1e088a4d4f56fdba..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/eb03559a4d92ea9ebd63ea9be663c50a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:93aa0613f6c9a36297ea3fffdfe7fe787d3df5e1c11fa66efff43933e86d61c8 -size 148855 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f4c40d970ceccdbca2595357cd06a080_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg deleted file mode 100644 index 4e7c70356e9a93e1f89ac9dec484e64c22c2cd65..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f4e5a86da5c799372a7c1ea2397dedb7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a93844ba3ab405a1ad87b0fea3d13b608ca1b1f1c09b30ba331bb4164606b88d -size 191525 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg deleted file mode 100644 index 025dac0e54c6f856ac7562204ff5f74f6cc9ed0b..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f5a5f52bc25d95a7f616290c99e88ae6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:da577f7a26718de82e31189146b8e6e61373bf6524f45daf34bc5742d9f4ef2b -size 84404 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f5deee2f3301ee351c4008283ffafbb3_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f5deee2f3301ee351c4008283ffafbb3_img.jpg deleted file mode 100644 index 03d6cd69b4bee7c33cd438628df088fa1875eff3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f5deee2f3301ee351c4008283ffafbb3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bb2a607770ef14e2bfa0708a1a9d684f2cb5450451b4937b297ef4b974ce1d2e -size 98015 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f63b447b65c94acf4135bcd496ebfe05_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f63b447b65c94acf4135bcd496ebfe05_img.jpg deleted file mode 100644 index 017a3805191077bd932c98b0e1dccdc600fbad87..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f63b447b65c94acf4135bcd496ebfe05_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d79d8d0dfa7bff1a1483cded319f17508b64f9c33af75d398d64a45354aae5f8 -size 237086 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f74adaa1840504407cd4272995426f82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f99313b06c15e9882079b773ce50a7b2_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f99313b06c15e9882079b773ce50a7b2_img.jpg deleted file mode 100644 index e1a5e67df77c23e70c08e46f747708d4ee64e436..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f99313b06c15e9882079b773ce50a7b2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1b3c966647d927a65182f15d3eb2bd90c6806e73d5b0bf147d00a46369396f71 -size 122903 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/facce731b2dbfae43a8609231a700be1_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/facce731b2dbfae43a8609231a700be1_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/facce731b2dbfae43a8609231a700be1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fbee1b51966e04afd72119133d952535_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fbee1b51966e04afd72119133d952535_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fbee1b51966e04afd72119133d952535_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fc3e2b49a9f850951570e502393b697f_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fc3e2b49a9f850951570e502393b697f_img.jpg deleted file mode 100644 index 2b920e4ab191490e2f4efb8c0b1e13547f5748da..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fc3e2b49a9f850951570e502393b697f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7db2ed3f90618bd17440dfb3a698f6a43142aae05149ba42b44249f2f536ee83 -size 140546 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fcc757566216206ceddbd6c775e8db02_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fcc757566216206ceddbd6c775e8db02_img.jpg deleted file mode 100644 index b15b5ab5de4f816f95bfe5d6a652a6f4333f00bc..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fcc757566216206ceddbd6c775e8db02_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1558c7e7e11cb0271f889cf02c216ad183f3f1a521daeceb6e08d16bf8caa475 -size 121765 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index f100b05b2d8ffc86089df311847a852b5b9e2f9c..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3f18c6635cc9ddaa01e58e0a0acdddebe5e9b774301289be0669610dea3bef33 -size 3820 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fe07d230fde7b9a0c4efa6ddb07e8595_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fe07d230fde7b9a0c4efa6ddb07e8595_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fe07d230fde7b9a0c4efa6ddb07e8595_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fec5f1bac5cf3187f7618d1adb95871f_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fec5f1bac5cf3187f7618d1adb95871f_img.jpg deleted file mode 100644 index bbca4c369c38d64f3a438f9174159fe6cfd94261..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/fec5f1bac5cf3187f7618d1adb95871f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bb10ec02c7dffaf89e409439791ed29ae9b167d9bff7b9173413209563929802 -size 3144 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index 6f9500d233d1bc4a3a3a6cf371683911e58f6847..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:57053da912e7f7f046430bdc4d6fec7bb0e15ee7053127a5363a7755272a532d -size 2930 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/ff81d88ebb5c5673a41bbcf9e41f6763_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/ff81d88ebb5c5673a41bbcf9e41f6763_img.jpg deleted file mode 100644 index 050111136f9db6a043a5523c191ec384a4618cca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/ff81d88ebb5c5673a41bbcf9e41f6763_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5732ae2d69c186c643a29ce739108e0e07d3dc32b71c8a7a54ecc846e1d18f79 -size 3146 diff --git a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/ffe2d3e622dd30bea4caf15951c60e42_img.jpg b/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/ffe2d3e622dd30bea4caf15951c60e42_img.jpg deleted file mode 100644 index 1b4596cbb2359a41dc8a6c1054467b56290fb177..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.ORCH-USE-CASES-R005-v15.00/images/ffe2d3e622dd30bea4caf15951c60e42_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c09706f2ce6bd8ef879ff296fca2f4b4b9960ee5d3d600cd2da148b91fda8e68 -size 159863 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/doc.md b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/doc.md deleted file mode 100644 index 5df8e4883d0c5eb00c4d7f0a99cad83824d5c5ff..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/doc.md +++ /dev/null @@ -1,1709 +0,0 @@ - - -# --- **O-RAN Work Group 6 (Cloudification and Orchestration)****Report on FOCOM and NFO SMOSs Northbound Interfaces** - -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., Buschkauer Weg 27, 53347 Alfter, Germany -Register of Associations, Bonn VR 11238, VAT ID DE321720189 - -# Contents - -| | | -|------------------------------------------------------------------------------------------------------------------|----| -| List of figures ..... | 2 | -| List of tables ..... | 2 | -| Foreword..... | 3 | -| Modal verbs terminology ..... | 3 | -| Introduction ..... | 4 | -| 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 Analysis of FOCOM SMOS and NFO SMOS Use Cases ..... | 6 | -| 4.1 Overview ..... | 6 | -| 4.2 Use Cases for the Exposure of FOCOM SMOS NBI ..... | 6 | -| 4.2.1 O-Cloud resources related information Query ..... | 6 | -| 4.2.2 O-Cloud template information Query Use Case..... | 9 | -| 4.2.3 Create, update and execute O-Cloud provisioning request using O-Cloud Template ..... | 11 | -| 4.2.4 Create, update and execute existing O-Cloud provisioning request revision using same O-Cloud Template..... | 16 | -| 4.2.5 Create, update and execute existing O-Cloud provisioning request revision using new O-Cloud Template..... | 18 | -| 4.2.6 Registering FOCOM SMOS for PM DME datatypes and associated operations..... | 21 | -| 4.2.7 Subscribing to PM Datatype/Dataset & associated operations (Update/Remove subscriptions) ..... | 24 | -| 4.2.8 Delete O-Cloud provisioningRequest instance..... | 30 | -| 4.2.9 Restore or Update O-Cloud provisioning request revision..... | 32 | -| 4.2.10 O-Cloud provisioningRequest status query ..... | 36 | -| 4.2.11 Support Fetching of PM Data through one-time/ad-hoc data requests..... | 37 | -| 4.2.12 O-Cloud Platform Software Update Use Case ..... | 39 | -| 4.2.13 Fetching of alarms based on Alarm query criteria ..... | 41 | -| 4.2.14 Subscribing for Alarm Event notifications based on alarm subscription/notification filter criteria ..... | 43 | -| 4.2.15 Fetching available O-Cloud Logs based on filter criteria..... | 44 | -| 4.2.16 IMS Software Update Use Case ..... | 45 | -| 4.2.17 DMS Software Update Use Case ..... | 47 | -| 5 Potential Requirements on the FOCOM and NFO SMOS services ..... | 49 | -| 5.1 Potential Functional and Interface Requirements ..... | 49 | -| 6 Recommendations ..... | 53 | -| Annex (Informative): Change history/Change request (history) ..... | 55 | - -# List of figures - -| | | -|-------------------------------------------------------------------------------------------------------------------------------|----| -| Figure 4.2.1.3-1: O-Cloud resource related information Query ..... | 8 | -| Figure 4.2.2.3-1: O-Cloud template information Query use case ..... | 10 | -| Figure 4.2.3.3-1: Create, update and execute O-Cloud provisioning request using O-Cloud Template..... | 16 | -| Figure 4.2.4.3-1: Create, update and execute existing O-Cloud provisioning request revision using same O-Cloud Template ..... | 18 | -| Figure 4.2.5.3-1: Create, update and execute existing O-Cloud provisioning request revision using new O-Cloud Template ..... | 20 | -| Figure 4.2.6.3-1: Registering FOCOM SMOS for Performance DME datatype & associated operations ..... | 24 | -| Figure 4.2.7.3-1: Subscribing PM Datatype/Data Set & associated operations (Update/Remove subscriptions) ..... | 29 | -| Figure 4.2.8.3-1: Delete O-Cloud provisioningRequest instance ..... | 32 | -| Figure 4.2.9.3-1: Restore or Update O-Cloud provisioning request revision ..... | 35 | -| Figure 4.2.10.3-1: O-Cloud provisioningRequest status query..... | 37 | -| Figure 4.2.11.3-1: Fetching PM Data for one-time/ad-hoc data requests..... | 39 | -| Figure 4.2.12.3-1: O-Cloud Platform Software Update..... | 41 | -| Figure 4.2.13.3-1: Fetching of alarms based on Alarm query criteria ..... | 42 | -| Figure 4.2.14.3-1: Subscribing for Alarm Event notifications based on alarm subscription/notification filter criteria .... | 44 | -| Figure 4.2.15.3-1: Fetching available O-Cloud Logs based on filter criteria ..... | 45 | -| Figure 4.2.16.3-1: IMS Software Update..... | 47 | -| Figure 4.2.17.3-1: DMS Software Update ..... | 49 | - -# List of tables - -| | | -|------------------------------------------------------------------------------------------------------------------------------|----| -| Table 4.2.1.2-1: O-Cloud resources related information Query ..... | 6 | -| Table 4.2.2.2-2: O-Cloud template information Query use case ..... | 9 | -| Table 4.2.3.2-3: Create, update and execute O-Cloud provisioning request using O-Cloud Template ..... | 11 | -| Table 4.2.4.2-4: Create, update and execute existing O-Cloud provisioning request revision using same O-Cloud Template ..... | 16 | -| Table 4.2.5.2-5: Create, update and execute existing O-Cloud provisioning request revision using new O-Cloud Template ..... | 19 | -| Table 4.2.6.2-6: Registering FOCOM SMOS for Performance DME datatype & associated operations ..... | 21 | -| Table 4.2.7.2-7: Subscribing to PM Datatype/Dataset & associated operations (Update/Remove subscriptions) ..... | 24 | -| Table 4.2.8.2-8: Delete O-Cloud provisioningRequest instance..... | 30 | -| Table 4.2.9.2-9: Restore or Update O-Cloud provisioning request revision..... | 33 | -| Table 4.2.10.2-10: O-Cloud provisioningRequest status query ..... | 36 | -| Table 4.2.11.2-11 Fetching PM Data for one-time/ad-hoc data requests..... | 38 | -| Table 4.2.12.2-12: O-Cloud Platform Software Update ..... | 40 | -| Table 4.2.13.2-1 Fetching of alarms based on Alarm query criteria..... | 42 | -| Table 4.2.14.2-1 Subscribing for Alarm Event notifications based on alarm subscription/notification filter criteria .... | 43 | -| Table 4.2.15.2-1 Fetching available O-Cloud Logs based on filter criteria ..... | 44 | -| Table 4.2.16.2-1: O-Cloud IMS Software Update ..... | 45 | -| Table 4.2.17.2-1: O-Cloud DMS Software Update ..... | 47 | -| Table 6-1: List of use cases and potential functional requirements ..... | 53 | - -# Foreword - -This Technical Report (TR) has been produced by 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 technical report explores and documents the impacts and gaps associated with the FOCOM and NFO SMO services and provides recommended potential requirements on the interactions of FOCOM and NFO SMO services with other SMO services by identifying and analysing the use cases as defined in O-RAN.WG1.Decoupled-SMO-Architecture, clause 5.6 and 6.1.3 [i.1]. - -# 1 Scope - -The scope of this present document is to identify and analyse use cases for FOCOM and NFO SMO services. Identification of use cases includes use cases defined in other O-RAN specifications as well as use cases identified in this present document which includes the new use cases in context of O-RAN.WG1.Decoupled-SMO-Architecture [i.1]. From the analysis of the use cases, recommendations are made for modifications to existing use cases, if needed and to provide potential requirements that can be used for future specifications for the FOCOM and NFO services - -# 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] O-RAN.WG1.Decoupled-SMO-Architecture-R004-v3.00: "Decoupled SMO Architecture". -- [i.2] O-RAN.WG6.ORCH-USE-CASES-R004: “O-RAN Orchestration Use Cases and Requirements for O-RAN Virtualized RAN”. -- [i.3] O-RAN.WG10.TS.OAM-Architecture: "O-RAN Operations and Maintenance Architecture" -- [i.4] O-RAN.WG6.TS.O2-GA&P: “O-RAN O2 Interface General Aspects and Principles” -- [i.5] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications" -- [i.6] O-RAN.WG2.TS.R1GAP: “R1 General Aspects and Principles“ -- [i.7] O-RAN.WG1.TS.OAD: “O-RAN Architecture Description” -- [i.8] O-RAN.WG6.TS.O-CLOUD-IM: “O-Cloud Information Model” -- [i.9] O-RAN.WG6.TS.O2IMS-INTERFACE: “O-RAN O2ims Interface Specification” -- [i.10] O-RAN.WG2.TS.R1AP: "Application Protocols for R1 services" - -# 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 3GPP TR 21.905 [i.5], O-RAN.WG1.Decoupled-SMO-Architecture [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 3GPP TR 21.905 [i.5] and O-RAN.WG1.Decoupled-SMO-Architecture [i.1] - -Void - -# 4 Analysis of FOCOM SMOS and NFO SMOS Use Cases - -## 4.1 Overview - -The capabilities of the FOCOM, as O2IMS consumer, are to discover and manage the O-Cloud resources, while the capabilities of the NFO, as O2DMS consumer, are to orchestrate the NF Deployments, as specified in O-RAN.WG6.TS.O2-GA&P, clause 2.2.1 [i.4]. Clause 4 provides analysis and recommendations concerning the different orchestration use cases highlighting the required capabilities to be exposed by FOCOM SMOS and NFO SMOS, including new and existing use cases defined in other O-RAN specifications. - -Clause 4 introduces the roles of FOCOM SMOS Producer and FOCOM SMOS Consumer. The principle of these roles is the same as service producer and service consumer as specified in O-RAN.WG1.TS.OAD, clause 5.3.1 [i.7]. - -## 4.2 Use Cases for the Exposure of FOCOM SMOS NBI - -### 4.2.1 O-Cloud resources related information Query - -#### 4.2.1.1 High level description - -This use case enables an authorized FOCOM SMOS Consumer to request a FOCOM SMOS Producer to retrieve information about the O-Cloud resources as provided by the IMS and O-Cloud templates identifiers supported in each O-Cloud. - -The O-Cloud resources include all the O-Cloud physical and logical resources. The FOCOM SMOS Consumer (e.g., an rApp or other SMOF), can query this information from the FOCOM SMOS Producer to understand the capabilities, relationships and characteristics of the O-Cloud. The O-RAN.WG6.TS.O-CLOUD-IM [i.8] specifies the information model about O-Cloud resources, which is structured, from an information modelling perspective, into different namespaces. - -The O-Cloud resources information may be cached within a FOCOM SMOS Producer and in that case FOCOM SMOS Producer can subscribe to receive notifications when there is an update to the O-Cloud resources using the O2ims interface. - -#### 4.2.1.2 Sequence Description - -**Table 4.2.1.2-1: O-Cloud resources related information Query** - -| Use Case Stage | Evolution / Specification | >>Uses<< | -|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| -| Use Case Title | O-Cloud resource related information Query Use Case | | -| Goal |

The goal of the Query O-Cloud resource information Use Case is the following:

  • To return information on O-Cloud resources as previously retrieved from the IMS.

To return all information on O-Cloud resources that are specified in the query filter within the Query O-Cloud resource information request.

| | -| Actors and Roles |

FOCOM SMOS Consumer – An authorized consumer e.g. rApp or other SMOF, consuming the services of FOCOM SMOS Producer.

FOCOM SMOS Producer –As service Producer, receives Query O-Cloud resource information requests and sends back Query O-Cloud resource information responses.

| | - -| | | | -|--------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------| -| | IMS - The IMS within the O-Cloud processes the Query Information request and receives the request over the O2ims interface. | | -| Assumptions | FOCOM SMOS Consumer knows about what information/data can be used to filter a query for information. | | -| Preconditions | O-Cloud Operational – O-Cloud is operational and has registered with the SMO.
Privilege – The FOCOM SMOS Consumer is authorized. | | -| Begins when | A FOCOM SMOS Consumer, sends a query request for O-Cloud information to the FOCOM SMOS Producer. | Ref to R1 interface: O-RAN.WG2.TS.R1GAP , clause 5.5.2.2 [i.6]. | -| Step 1 (M) | The FOCOM SMOS Consumer, initiates a Query O-Cloud resource information request with a query information payload which includes query filter.

The query filter specifies the objects of interest in the Query O-Cloud resource Information request. A query filter may point to specific O-Cloud objects (like resources, artifacts, etc.) by referring to their attribution, as specified in the O-RAN.WG6.TS.O-CLOUD-IM [i.8]. | | -| Step 2 (M) | On receiving the request from FOCOM SMOS Consumer, The FOCOM SMOS Producer authenticates the connection and processes the Query O-Cloud resource information request. FOCOM SMOS Consumer retrieve the available requested information. | | -| Based on the query request from FOCOM SMOS Consumer, if FOCOM SMOS Producer needs additional information it initiates a query request to the IMS | | | -| OPT | On receiving the request from FOCOM SMOS Consumer the FOCOM SMOS Producer initiate a Query O-Cloud Information Request to IMS over the O2ims interface to retrieve additional information.

NOTE: The sequence of interactions between the FOCOM SMOS Producer and IMS is specified in ORAN.WG6.ORCH-USE-CASES, clause 3.1.11 [i.2] | ORAN.WG6.ORCH-USE-CASES, clause 3.1.11 [i.2]. | -| Step 3 (ALT) | If the Query Information operation was successful, the FOCOM SMOS Producer responds to FOCOM SMOS Consumer, with the results matching the Query filter in the Query O-Cloud resource information request. The information provided in the response message may contain additional details added by the FOCOM SMOS Producer. | | -| Step 4 (ALT) | If an exception occurs during the request processing, the FOCOM SMOS Producer returns information to FOCOM SMOS Consumer about the exception and probable cause such as:

1. no existing objects or attributes exception encountered
2. IMS encountered an unexpected condition | | -| Ends when | FOCOM SMOS Consumer receives the requested information or information on an occurred exception. | | -| Exceptions | EXCEPTION: QUERY WITH NO EXISTING OBJECTS OR ATTRIBUTES

This exception is encountered when a Query O-Cloud Information request specifies objects that do not exist. An exception notification will be returned; and the use case will end this situation. | | - -| | | | -|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | EXCEPTION: UNEXPECTED CONDITION
The IMS encountered an unexpected condition, such as an internal software fault. An exception notification will be returned; and the use case will end this this situation. | | -| Post-conditions | N/A | | -| Traceability | [REQ-FOCOM-FUN[1], REQ-FOCOM-FUN[2], REQ-FOCOM-FUN[3]] | | - -#### 4.2.1.3 UML Sequence Diagram - -![UML Sequence Diagram for O-Cloud resource related information Query. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer (within Service Management & Orchestration Framework), and IMS (within O-Cloud). The sequence involves a query request, internal retrieval, an optional additional information step, and a final response or exception handling.](7a0db9703b68b3d06cdaeefc084c0006_img.jpg) - -``` - -sequenceDiagram - participant FSC as FOCOM SMOS Consumer - participant FSP as FOCOM SMOS Producer - participant IMS as IMS - Note right of FSP: PRECONDITION: -SMO has connectivity to O-Cloud -O-Cloud has registered its IMS with the SMO -The identification & privileges of a SMO use has been verified -The FOCOM SMOS Consumer is authorized - - FSC->>FSP: 1 Query O-Cloud resource information request (query information) - FSP->>FSP: 2 Retrieves available query information - Note right of FSP: FOCOM SMOS Producer initiates request to IMS to query O-Cloud resource Information for additional information - opt If FOCOM SMOS Producer need additional information - ref see the Use Case in ORAN.WG6.ORCH-USE-CASES, clause 3.1.11 [i.2] - end - alt FOCOM SMOS Consumer receives successful response - FSP->>FSC: 3 Query O-Cloud resource information response - else FOCOM SMOS Consumer receives an exception - Note right of FSP: Exception case - FSP->>FSC: 4 No existing object or attributes or Unexpected condition - end - -``` - -UML Sequence Diagram for O-Cloud resource related information Query. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer (within Service Management & Orchestration Framework), and IMS (within O-Cloud). The sequence involves a query request, internal retrieval, an optional additional information step, and a final response or exception handling. - -Figure 4.2.1.3-1: O-Cloud resource related information Query - -### 4.2.2 O-Cloud template information Query Use Case - -#### 4.2.2.1 High level description - -This use case enables a FOCOM SMOS Consumer e.g. an rApp or other SMOF, to retrieve information about the O-Cloud templates such as template characteristics, metadata and instance parameter schema information from FOCOM SMOS. FOCOM SMOS Consumer may use this information to understand the characteristics of the O-Cloud Node Cluster that are based on the O-Cloud templates and utilize this information for use cases such as create, delete or update a O-Cloud Node Cluster etc., - -#### 4.2.2.2 Sequence Description - -**Table 4.2.2.2-2: O-Cloud template information Query use case** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Enable FOCOM SMOS Consumer to query O-Cloud template information | | -| Actors and Roles | FOCOM SMOS Producer as service Producer
FOCOM SMOS Consumer e.g. rApp or other SMOF | | -| Assumptions | N/A | | -| Preconditions | 1) O-Cloud registration Use Case as defined in ORAN.WG6.ORCH-USE-CASES, clause 3.1.3 [i.2] has been executed and FOCOM SMOS Producer has discovered the current O-Cloud template(s) information.
2) FOCOM SMOS Consumer query O-Cloud resource information which includes the information of O-Cloud template identifier matching O-Cloud site | | -| Begins when | FOCOM SMOS Consumer intends to query the O-Cloud template information. | | -| Step 1 (M) | FOCOM SMOS Consumer sends a request to FOCOM SMOS Producer to query available O-Cloud template(s) information. | | -| Step 2 (M) | FOCOM SMOS Producer checks if the request received is from an authorized consumer. | | -| Step 3(M) | FOCOM SMOS Producer retrieves the available O-Cloud templates information | | -| Step 4 (alt) | FOCOM SMOS Producer responds with O-Cloud template(s) information. | | -| Step 5 (alt) | If an exception occurs during the request processing, the FOCOM SMOS Producer returns information to FOCOM SMOS Consumer about the exception and probable cause such as:

3. no existing objects or attributes exception encountered

4. IMS encountered an unexpected condition | | -| Ends when | FOCOM SMOS Consumer receives the O-Cloud templates information or information on an occurred exception. | | -| Exceptions | EXCEPTION: QUERY WITH NO EXISTING OBJECTS OR ATTRIBUTES | | - -| | | | -|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

This exception is encountered when a Query O-Cloud Information request specifies objects that do not exist. An exception notification will be returned; and the use case will end this this situation.

EXCEPTION: UNEXPECTED CONDITION

The IMS encountered an unexpected condition, such as an internal software fault. An exception notification will be returned; and the use case will end this this situation.

| | -| Post Conditions | N/A | | -| Traceability | REQ-FOCOM-FUN4 | | - -#### 4.2.2.3 UML Sequence Diagram - -![UML Sequence diagram for O-Cloud template information Query use case. Lifelines: FOCOM SMOS Consumer and FOCOM SMOS Producer. The diagram shows a request for template information, authorization check, retrieval, and an alt block for successful response or exception case.](d26959f4514c26ca19c3d6f00da85956_img.jpg) - -``` - -sequenceDiagram - participant Consumer as FOCOM SMOS Consumer - participant Producer as FOCOM SMOS Producer - Note right of Producer: PRECONDITION: -1)O-Cloud registration Use Case as defined in ORAN.WG6.ORCH-USE-CASES, clause 3.1.3 [i.2] has been executed and FOCOM SMOS Producer has discovered the current O-Cloud template(s) information. -2)FOCOM SMOS Consumer query O-Cloud resource information which includes the information of O-Cloud template identifier matching O-Cloud site - - Consumer->>Producer: 1 query O-Cloud template information request (templateId(s)) - Note right of Producer: 2 check if the consumer is authorized to query O-Cloud template(s) information - Note right of Producer: 3 Retrieves available O-Cloud template(s) information - alt FOCOM SMOS Consumer receives successful response - Producer-->>Consumer: 4 Query O-Cloud template information response (O-Cloud template(s) information) - else FOCOM SMOS Consumer receives an exception: Exception case - Producer-->>Consumer: 5 No existing object or attributes or Unexpected condition - end - -``` - -UML Sequence diagram for O-Cloud template information Query use case. Lifelines: FOCOM SMOS Consumer and FOCOM SMOS Producer. The diagram shows a request for template information, authorization check, retrieval, and an alt block for successful response or exception case. - -Figure 4.2.2.3-1: O-Cloud template information Query use case - -### 4.2.3 Create, update and execute O-Cloud provisioning request using O-Cloud Template - -#### 4.2.3.1 High level description - -The use case aims to assign a suitable set of O-Cloud resources to create an O-Cloud Node Cluster. Before this use case is started it is expected that the FOCOM SMOS Consumer has discovered the O-Cloud Template information. O-Cloud Template information is the properties about the O-Cloud Template that is exposed by the IMS towards the SMO. See clause 4.2.2 for further information. - -To create an O-Cloud Node Cluster there are 3 different steps defined in this use case: - -- 1) Create provisioningRequest revision -- 2) Update provisioningRequest revision -- 3) Execute provisioningRequest revision - -NOTE: Even though the use case describes the three different steps of creation, updating and execution, these steps do not necessarily always take place sequentially, and these steps may be performed individually. Use case describes all of them for completeness of all relevant processes. - -The term “version” refers to an O-Cloud template with same O-Cloud template name but with a different O-Cloud template version. The term “revision” refers to O-Cloud provisioning request instance with same provisioningRequestId but different revisionId e.g. updated in order to prepare for an update of existing O-Cloud provisioning request instance. - -As specified in ORAN.WG6.ORCH-USE-CASES, clause 3.11.2.1 [i.2], the provisioning request from FOCOM SMOS towards the IMS at O-Cloud uses a declarative approach to create a O-Cloud Node Cluster. In this use case, FOCOM SMOS Consumer e.g. an rApp or other SMOF, request to FOCOM SMOS to create, update and execute a provisioning request based on supported O-Cloud Template. - -The provisioning request from FOCOM SMOS Consumer will be stored and version controlled inside FOCOM SMOS as a Cluster and Infrastructure ProvisioningRequest instance which is referring to one single O-Cloud Template (template name/template version). Version control of the ProvisioningRequest enables tracking of new revisions of the ProvisioningRequest with any updated instance specific configuration and enables roll back to an old revision of the ProvisioningRequest in order to restore an older configuration. FOCOM SMOS will do the feasibility check of the required resources requested from FOCOM SMOS Consumer. - -#### 4.2.3.2 Sequence Description - -**Table 4.2.3.2-3: Create, update and execute O-Cloud provisioning request using O-Cloud Template** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To create an O-Cloud Node cluster by creating, updating and executing the O-Cloud provisioning Request instance based on an O-Cloud Template | | -| Actors and Roles | FOCOM SMOS Consumer – An authorized consumer e.g. rApp or other SMOF, consuming the services of FOCOM SMOS

FOCOM SMOS Producer – Receives create, update and execute request for the O-Cloud provisioning request and sends back responses. | | -| Assumptions | There are no assumptions for this use case | | -| Preconditions | O-Cloud Operational – O-Cloud is operational and has registered with the SMO

FOCOM SMOS Consumer has the O-Cloud resource information and O-Cloud Template information (see clause 4.2.2)

Privilege – The FOCOM SMOS Consumer is authorized | | - -| | | | -|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Begins when | A FOCOM SMOS Consumer, sends a request to create a draft O-Cloud provisioning request revision | | -| Step 1 (M) | FOCOM SMOS Consumer sends a request to create a draft O-Cloud provisioning request revision by referring to the O-Cloud and O-Cloud template information which includes templateName, templateVersion and templateParameters.

See NOTE 1 | | -| Step 2 (M) | FOCOM SMOS Producer create a draft revision and generates new provisioningRequestId | | -| Step 3 (M) | FOCOM SMOS Producer sends an asynchronous response and Information about the state and status of provisioningRequest such as URI to fetch the information. | | -| Step 4 (M) | FOCOM SMOS Producer validates the template parameter based on the O-Cloud template schema exposed as part of O-Cloud template information.

See NOTE 2 | | -| Step 5 (M) | Validation of the template parameter is failed, FOCOM SMOS Producer responds to FOCOM SMOS Consumer with provisioningRequestId and information regarding the validation fail. | | -| Step 6 (M) | Validation is success, FOCOM SMOS Producer queries the IMS for identified resource types.

See NOTE 3 | | -| Step 7 (M) | IMS responds to the request | | -| Step 8 (M) | After receiving the response from IMS, FOCOM SMOS Producer performs a feasibility check by validating if enough resources are available | | -| Step 9 (M) | Validation of parameter and resource check success, FOCOM SMOS Producer respond with provisioningRequestId and resource check success. | | -| Step 10 (M) | Validation of parameter success but resource check fail. FOCOM SMOS Producer respond with provisioningRequestId and information regarding resource check failure. | | -| FOCOM SMOS Consumer, may update the new draft revision of the O-Cloud provisioning request with the instance specific input data.
Step 11 – Step 19 are optional. | | | -| Step 11 | FOCOM SMOS Consumer sends a request to update the draft provisioning request with provisioningRequestId and updated template parameters | | -| Step 12 | FOCOM SMOS Producer sends an asynchronous response | | - -| | | | -|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 13 | FOCOM SMOS Producer validates the template parameter based on the O-Cloud template schema exposed as part of O-Cloud template information.
See NOTE 2. | | -| Step 14 | Validation of the template parameter is failed, FOCOM SMOS Producer responds to FOCOM SMOS Consumer with provisioningRequestId and information regarding the validation fail | | -| Step 15 | Validation is success, FOCOM SMOS Producer queries the IMS for identified resource types.
See NOTE 3 | | -| Step 16 | IMS responds to the request | | -| Step 17 | After receiving the response from IMS, performs a feasibility check by validating validates if enough resources are available | | -| Step 18 | Validation of parameter and resource check success, FOCOM SMOS Producer respond with provisioningRequestId and resource check success. | | -| Step 19 | Validation of parameter success but resource check fail. FOCOM SMOS Producer respond with provisioningRequestId and information regarding resource check failure. | | -| Step 20 (M) | FOCOM SMOS Consumer request to FOCOM SMOS Producer to approve the draft and execute the O-Cloud provisioning request
See NOTE 4 | | -| Step 21 (M) | FOCOM SMOS Producer check if the provisioningRequest is validated and resource check success | | -| FOCOM SMOS Producer accepts and approves the Provisioning Request and initiate a request to create provisioning request towards the IMS at O-Cloud

See NOTE 5 | | | -| Step 22 (M) | FOCOM SMOS Producer updates the fulfilled O-Cloud provisioning request with information on provisioned resources. | | -| Step 23 (M) | If an exception occurs during the request processing, the FOCOM SMOS Producer returns information to FOCOM SMOS Consumer about the exception and probable cause such as:
  • 5. no existing objects or attributes exception encountered
  • 6. IMS encountered an unexpected condition
| | -| Step 24 (M) | FOCOM SMOS Producer rejects to approve the provisioning request with information of rejection.
SEE NOTE 6 | | -| Ends when | FOCOM SMOS Consumer successfully request the creation of an O-Cloud Node Cluster and/or infrastructure resources or when the use case has encountered an exception | | - -| | | | -|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Exceptions | EXCEPTION: UNEXPECTED CONDITION

The exception is encountered an unexpected condition, such as an insufficient resources, creation failed, malformed request. An exception notification will be returned; and the use case will end this situation

See NOTE 7 | | -| Post Conditions | N/A | | -| Traceability | REQ-FOCOM-FUN5, REQ-FOCOM-FUN6, REQ-FOCOM-FUN7, REQ-FOCOM-FUN8 | | -| NOTE 1: A draft is a new O-Cloud provisioning request instance revision that is used by the FOCOM SMOS Consumer to prepare the new configuration information that has not been approved and executed the requested instance
NOTE 2: The validation is to provide feedback to the FOCOM SMOS Consumer whether the provided input data is compliant to the O-Cloud Template schema, e.g., if some mandatory data is missing etc.,
NOTE 3: FOCOM SMOS Producer needs to be aware of O-Cloud template parameters and template characteristics provided in the O-Cloud template information representing the below information:
  1. 1. O-Cloud site
  2. 2. If node groups are used, number of nodes per group and eligible resource types (for instance compute and site networks)
  3. 3. If node groups are not used, number of nodes and eligible resource types (for instance compute and site networks)
NOTE 4: An approve O-Cloud provisioning request instance revision is approved by the FOCOM SMOS Consumer and accepted for execution by FOCOM SMOS Producer
NOTE 5: The sequence of interactions between the FOCOM SMOS Producer and IMS is specified in ORAN.WG6.ORCH-USE-CASES, clause 3.11.2.3 [i.2]
NOTE 6: FOCOM SMOS Consumer repeats the update procedure (step 8-14) of provisioningRequest and triggers the approve request only when the updates are successfully validated and resource check success.
NOTE 7: After receiving the exception, FOCOM SMOS Producer will not automatically delete the instance of the provisioning request. The provisioning request will be updated as failed with the failure reason. Based on the failure further actions to be done from FOCOM SMOS Consumer | | | - -#### 4.2.3.3 UML Sequence Diagram - -![UML Sequence diagram for O-Cloud provisioning. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer (within Service Management & Orchestration Framework), and IMS (within O-Cloud). The diagram shows three main interactions: Create, Update, and Approve. The Create interaction includes validation and resource feasibility checks. The Update interaction is a loop until all data is updated. The Approve interaction includes a reference to another sequence diagram for the IMS interaction details.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg) - -``` - -sequenceDiagram - participant FOCOM_SMOS_Consumer as FOCOM SMOS Consumer - participant FOCOM_SMOS_Producer as FOCOM SMOS Producer - participant IMS as IMS - Note right of FOCOM_SMOS_Producer: PRECONDITION: -FOCOM SMOS Consumer has -the O-Cloud Template information - - Note over FOCOM_SMOS_Producer: Create a draft O-Cloud provisioning Request - - FOCOM_SMOS_Consumer->>FOCOM_SMOS_Producer: 1 Create request: A draft O-Cloud provisioning request revision (templateName, templateVersion, templateParameters, oCloudId) - FOCOM_SMOS_Producer->>FOCOM_SMOS_Producer: 2 create a draft revision and generates new provisioningRequestId - FOCOM_SMOS_Producer-->>FOCOM_SMOS_Consumer: 3 Create response: A draft O-Cloud provisioning request revision response (provisioningRequestId, statusInformation) - FOCOM_SMOS_Producer->>FOCOM_SMOS_Producer: 4 validates template parameters - - alt FOCOM SMOS Consumer receives an exception validation failed - FOCOM_SMOS_Producer-->>FOCOM_SMOS_Consumer: 5 Validation failed - else FOCOM SMOS Producer successfully validate the parameter and doing the feasibility check - FOCOM_SMOS_Producer->>IMS: 6 Query IMS for identified resource types - IMS-->>FOCOM_SMOS_Producer: 7 Query response - FOCOM_SMOS_Producer->>FOCOM_SMOS_Producer: 8 feasibility check by validating if enough resources are available - - alt FOCOM SMOS Consumer receives successful response validation and resources check success - FOCOM_SMOS_Producer-->>FOCOM_SMOS_Consumer: 9 Validation and resource check success - else FOCOM SMOS Consumer receives an exception validation success but resource check failed - FOCOM_SMOS_Producer-->>FOCOM_SMOS_Consumer: 10 Validation success but resource check failed - end - end - - Note over FOCOM_SMOS_Producer: may be some delay - - Note over FOCOM_SMOS_Producer: Update a draft O-Cloud provisioning Request - - opt until all required input data is updated - FOCOM_SMOS_Consumer->>FOCOM_SMOS_Producer: 11 Update request: A draft O-Cloud provisioning request revision (provisioningRequestId, templateParameters) - FOCOM_SMOS_Producer-->>FOCOM_SMOS_Consumer: 12 Update response - FOCOM_SMOS_Producer->>FOCOM_SMOS_Producer: 13 validates template parameters - - alt FOCOM SMOS Consumer receives an exception - FOCOM_SMOS_Producer-->>FOCOM_SMOS_Consumer: 14 Validation Failed - else FOCOM SMOS Producer successfully validate the parameter and doing the feasibility check - FOCOM_SMOS_Producer->>IMS: 15 Query request to IMS for identified resource types - IMS-->>FOCOM_SMOS_Producer: 16 Query response - FOCOM_SMOS_Producer->>FOCOM_SMOS_Producer: 17 feasibility check by validating if enough resources are available - - alt FOCOM SMOS Consumer receives successful response - FOCOM_SMOS_Producer-->>FOCOM_SMOS_Consumer: 18 Validation and resource check success - else FOCOM SMOS Consumer receives an exception - FOCOM_SMOS_Producer-->>FOCOM_SMOS_Consumer: 19 Validation and resource check fail - end - end - end - - Note over FOCOM_SMOS_Producer: may be some delay - - Note over FOCOM_SMOS_Producer: Approve the draft and Execute O-Cloud provisioning Request - - FOCOM_SMOS_Consumer->>FOCOM_SMOS_Producer: 20 approve the draft and execute the O-Cloud Provisioning Request Instance (provisioningRequestId) - FOCOM_SMOS_Producer->>FOCOM_SMOS_Producer: 21 if the provisioningRequestId is validated and resource check success. - - alt FOCOM SMOS approves the request and interact with IMS - Note right of FOCOM_SMOS_Producer: ref: 1. FOCOM initiates request to IMS to create provisioning request -2. see the Use Case in ORAN.WG6.ORCH-USE-CASES, clause 3.11.2.3 [i.2] - alt FOCOM SMOS Consumer receives successful response - Note right of FOCOM_SMOS_Producer: FOCOM SMOS Producer fulfilled provisioning status from IMS - FOCOM_SMOS_Producer-->>FOCOM_SMOS_Consumer: 22 O-Cloud provisioning request fulfilled (provisioningRequestId, info on provisioned resources) - else FOCOM SMOS Consumer receives an exception - Note right of FOCOM_SMOS_Producer: Exception case - FOCOM_SMOS_Producer-->>FOCOM_SMOS_Consumer: 23 Unexpected condition - end - else FOCOM SMOS Producer doesn't approve the request - FOCOM_SMOS_Producer-->>FOCOM_SMOS_Consumer: 24 Request not approved - end - -``` - -UML Sequence diagram for O-Cloud provisioning. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer (within Service Management & Orchestration Framework), and IMS (within O-Cloud). The diagram shows three main interactions: Create, Update, and Approve. The Create interaction includes validation and resource feasibility checks. The Update interaction is a loop until all data is updated. The Approve interaction includes a reference to another sequence diagram for the IMS interaction details. - -**Figure 4.2.3.3-1: Create, update and execute O-Cloud provisioning request using O-Cloud Template** - -### 4.2.4 Create, update and execute existing O-Cloud provisioning request revision using same O-Cloud Template - -#### 4.2.4.1 High level description - -The use case aims to assign a suitable set of O-Cloud resources to update an O-Cloud Node Cluster and/or infrastructure resources using same O-Cloud Template. Before this use case is started it is expected that the FOCOM SMOS Consumer e.g. an rApp or other SMOF has acquired the provisioningRequestId by querying the list of already created and accepted provisioning request instance and has discovered the O-Cloud template information. O-Cloud template information is the properties about the O-Cloud Template that is exposed by the IMS towards the SMO. See clause 4.2.2 for further information. - -In comparison with the use case in clause 4.2.3.2, this use case takes as a pre-condition that a ProvisioningRequest already exists and the purpose is to update it by providing new/updated parameter values. - -To update an O-Cloud Node Cluster and/or infrastructure resources there are 3 different steps defined in this use case: - -- 1) Create provisioningRequest revision -- 4) Update provisioningRequest revision -- 5) Execute provisioningRequest revision - -**NOTE:** Even though the use case describes the three different steps of creation, updating and execution, these steps do not necessarily always take place sequentially, and these steps may be performed individually. Use case describes all of them for completeness of all relevant processes - -FOCOM SMOS Consumer, request to FOCOM SMOS to create, update and execute a new draft of O-Cloud provisioning Request revision based on the content from the current revision of the provisioning request and same O-Cloud Template version. - -See clause 4.2.3.1 for further information on the term “version”, “revision”, O-Cloud provisioningRequest instance and the purpose of version control of provisioning request. - -#### 4.2.4.2 Sequence Description - -**Table 4.2.4.2-4: Create, update and execute existing O-Cloud provisioning request revision using same O-Cloud Template** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To update an O-Cloud Node Cluster and/or infrastructure resources by creating, updating and executing the O-Cloud provisioningRequest instance based on the content from the current revision of the provisioning request and same O-Cloud Template name and O-Cloud Template version | | -| Actors and Roles | FOCOM SMOS Consumer – An authorized consumer e.g. rApp or other SMOF, consuming the services of FOCOM SMOS

FOCOM SMOS Producer – Receives create, update and execute request for the O-Cloud provisioning request and sends back responses.

IMS – To execute the request received from FOCOM SMOS Producer | | -| Assumptions | There are no assumptions for this use case | | -| Preconditions | O-Cloud Operational – O-Cloud is operational and has registered with the SMO | | - -| | | | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |

FOCOM SMOS Consumer - Has acquired provisioningRequestId by querying the list of already created and accepted provisioning request and has acquired O-Cloud template information

IMS - Declarative Provisioning request object exists

Privilege – The FOCOM SMOS Consumer is authorized

| | -| Begins when | A FOCOM SMOS Consumer, sends a request to create a new draft to update the O-Cloud provisioning request revision | | -| Step 1 (M) |

FOCOM SMOS Consumer initiates a request to create a new draft to update O-Cloud provisioning request revision request with template parameter and provisioningRequestId as a parameter.

See NOTE 1

| | -| Step 2 (M) | FOCOM SMOS Producer create a draft revision | | -| Step 3 (M) | FOCOM SMOS Producer create a draft revision and sends an asynchronous response and Information about the state and status of provisioningRequest such as URI to fetch the information. | | -| Steps 4 to 21 on this use case are same as step 4 to step 21 of the use case specified in clause 4.2.3.2. But, Step 6, 7, 8 and Step 15, 16 and 17 in clause 4.2.3.2, will only be executed by the FOCOM SMOS Producer if additional O-Cloud resources are required due to the updated Provisioning request. | | | -| FOCOM SMOS Producer accepts and approves the Provisioning Request and initiate a request to update provisioning request towards the IMS at O-Cloud | | | -| See NOTE 2 | | | -| Steps 22 to 24 on this use case are same as step 22 to step 24 of the use case specified in clause 4.2.3.2 | | | -| Ends when | FOCOM SMOS Consumer successfully request an update to an O-Cloud Node Cluster and/or infrastructure resources or when the use case has encountered an exception | | -| Exceptions | See clause 4.2.3.2 | | -| Post Conditions | N/A | | -| Traceability | REQ-FOCOM-FUN9, REQ-FOCOM-FUN4, REQ-FOCOM-FUN6, REQ-FOCOM-FUN7, REQ-FOCOM-FUN8 | | -| NOTE 1: A draft is a new O-Cloud provisioning request instance revision that is used by the FOCOM SMOS Consumer to prepare the new configuration information that has not been approved and executed the requested instance.
NOTE 2: The sequence of interactions between the FOCOM SMOS Producer and IMS is specified in ORAN.WG6.ORCH-USE-CASES, clause 3.11.4.3 [i.2] | | | - -#### 4.2.4.3 UML Sequence Diagram - -![UML Sequence Diagram for 'Create, update and execute existing O-Cloud provisioning request revision using same O-Cloud Template'. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer (Service Management & Orchestration Framework), and O2-IMS (O-Cloud). The diagram shows a 'Create request' message from Consumer to Producer, a 'create a draft revision' self-call on Producer, and a 'Create response' message from Producer to Consumer. It includes preconditions and references to other use cases.](8fa679f79a1bb1f527cba9f29e784e89_img.jpg) - -**Service Management & Orchestration Framework** - -**O-Cloud** - -FOCOM SMOS Consumer      FOCOM SMOS Producer      O2-IMS - -**PRECONDITION:** - FOCOM SMOS Consumer: - 1. Has acquired provisioningRequestId by querying the list of already created and accepted provisioning request - 2. Has acquired O-Cloud template information - IMS: Declarative Provisioning request object exist - -**Create a new draft to update the O-Cloud provisioning Request revision based on the content from the current revision of the provisioning request & same O-Cloud template name and O-Cloud template version** - -1 Create request: A draft O-Cloud provisioning request revision request (templateParameter, provisioningRequestId) - 2 create a draft revision - 3 Create response: A draft O-Cloud provisioning request revision response (provisioningRequestId, statusInformation) - -Steps 4 to step 21 on this use case are same as step 4 to step 21 of the use case specified in clause 4.2.3.2. - But, Step 6, 7, 8 and Step 15, 16 and 17 in clause 4.2.3.2, will only be executed by the FOCOM SMOS Producer if additional O-Cloud resources are required due to the updated Provisioning request. - -**ref** - 1. FOCOM initiates request to IMS to update provisioning request - 2. see the Use Case in ORAN.WG6.ORCH-USE-CASES, clause 3.11.4.3 [i.2] - -Steps 22 to step 24 on this use case are same as step 22 to step 24 of the use case specified in clause 4.2.3.2 - -FOCOM SMOS Consumer      FOCOM SMOS Producer      O2-IMS - -UML Sequence Diagram for 'Create, update and execute existing O-Cloud provisioning request revision using same O-Cloud Template'. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer (Service Management & Orchestration Framework), and O2-IMS (O-Cloud). The diagram shows a 'Create request' message from Consumer to Producer, a 'create a draft revision' self-call on Producer, and a 'Create response' message from Producer to Consumer. It includes preconditions and references to other use cases. - -**Figure 4.2.4.3-1: Create, update and execute existing O-Cloud provisioning request revision using same O-Cloud Template** - -### 4.2.5 Create, update and execute existing O-Cloud provisioning request revision using new O-Cloud Template - -#### 4.2.5.1 High level description - -The use case aims to assign a suitable set of O-Cloud resources to update an O-Cloud Node Cluster and/or infrastructure resources using new O-Cloud Template. Before this use case is started it is expected that the FOCOM SMOS Consumer e.g. an rApp or other SMOF has acquired the provisioningRequestId by querying the list of already created and accepted provisioning request instance and has discovered the new O-Cloud template information. O-Cloud template information is the properties about the O-Cloud Template that is exposed by the IMS towards the SMO. See clause 4.2.2 for further information. - -In comparison with the use case in clause 4.2.3.2, this use case takes a pre-condition that a ProvisioningRequest already exists and the purpose is to update it by referencing to a new O-Cloud template, with potentially providing new/updated parameter values. - -To update an O-Cloud Node Cluster and/or infrastructure resources there are 3 different steps defined in this use case: - -- 1) Create provisioningRequest revision -- 6) Update provisioningRequest revision -- 7) Execute provisioningRequest revision - -**NOTE:** Even though the use case describes the three different steps of creation, updating and execution, these steps do not necessarily always take place sequentially, and these steps may be performed individually. Use case describes all of them for completeness of all relevant processes - -FOCOM SMOS Consumer, request to FOCOM SMOS Producer to create, update and execute a new draft of O-Cloud provisioning Request revision based on the content from the current revision of the provisioning request and new O-Cloud Template version - -See clause 4.2.3.1 for further information on the term “version”, “revision”, O-Cloud provisioningRequest instance and the purpose of versioning the provisioning request. - -#### 4.2.5.2 Sequence Description - -**Table 4.2.5.2-5: Create, update and execute existing O-Cloud provisioning request revision using new O-Cloud Template** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To update an O-Cloud Node Cluster and/or infrastructure resources by creating, updating and executing the O-Cloud provisioningRequest instance based on the content from the current revision of the provisioning request and with new O-Cloud Template version and/or O-Cloud Template name | | -| Actors and Roles | FOCOM SMOS Consumer – An authorized consumer e.g. rApp or other SMOF, consuming the services of FOCOM SMOS
FOCOM SMOS Producer – Receives create, update and execute request for the O-Cloud provisioning request and sends back responses.
IMS – To execute the request received from FOCOM SMOS Producer | | -| Assumptions | There are no assumptions for this use case | | -| Preconditions | O-Cloud Operational – O-Cloud is operational and has registered with the SMO
FOCOM SMOS Consumer - Has acquired provisioningRequestId by querying the list of already created and accepted provisioning request and has acquired new O-Cloud template information
IMS - Declarative Provisioning request object exists
Privilege – The FOCOM SMOS Consumer is authorized | | -| Begins when | A FOCOM SMOS Consumer, request to create a new draft to update the O-Cloud provisioning request revision based on new O-Cloud Template | | -| Step 1 (M) | FOCOM SMOS Consumer initiates a request create a new draft O-Cloud provisioning request revision request which includes templateName, templateVersion and templateParameters and provisioningRequestId as a parameter.

templateName together with templateVersion uniquely identifies a template, where the templateName gives a human operator the association of what the template is meant for.

See NOTE 1 | | -| Step 2 (M) | FOCOM SMOS Producer create a draft revision | | -| Step 3 (M) | FOCOM SMOS Producer create a draft revision and sends an asynchronous response and Information about the state and status of provisioningRequest such as URI to fetch the information. | | - -| | | | -|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -|

Steps 4 to 21 on this use case are same as step 4 to step 21 of the use case specified in clause 4.2.3.2. But, Step 6, 7, 8 and Step 15, 16 and 17 in clause 4.2.3.2, will only be executed by the FOCOM SMOS Producer if additional O-Cloud resources are required due to the updated Provisioning request

| | | -|

FOCOM SMOS Producer accepts and approves the Provisioning Request and initiate a request to update provisioning request towards the IMS at O-Cloud

| | | -|

See NOTE 2

| | | -|

Steps 22 to 24 on this use case are same as step 22 to step 24 of the use case specified in clause 4.2.3.2

| | | -| Ends when | FOCOM SMOS Consumer successfully request an update to an O-Cloud Node Cluster and/or infrastructure resources or when the use case has encountered an exception | | -| Exceptions | See clause 4.2.3.2 | | -| Post Conditions | N/A | | -| Traceability | REQ-FOCOM-FUN10, REQ-FOCOM-FUN4, REQ-FOCOM-FUN6, REQ-FOCOM-FUN7, REQ-FOCOM-FUN8 | | -|

NOTE 1: A draft is a new O-Cloud provisioning request instance revision that is used by the FOCOM SMOS Consumer to prepare the new configuration information that has not been approved and executed the requested instance.
NOTE 2: The sequence of interactions between the FOCOM SMOS Producer and IMS is specified in ORAN.WG6.ORCH-USE-CASES, clause 3.11.4.3 [i.2].

| | | - -#### 4.2.5.3 UML Sequence Diagram - -![UML Sequence Diagram for 'Create, update and execute existing O-Cloud provisioning request revision using new O-Cloud Template'. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer (under Service Management & Orchestration Framework), and O2-IMS (under O-Cloud). The sequence starts with a precondition block. Step 1: Consumer sends 'Create request' to Producer. Step 2: Producer sends 'create a draft revision' to itself. Step 3: Producer sends 'Create response' to Consumer. A note covers steps 4-21, mentioning that steps 6, 7, 8, 15, 16, and 17 are only executed by the Producer if additional resources are needed. A 'ref' block contains: 1. FOCOM initiates request to IMS to update provisioning request; 2. see the Use Case in ORAN.WG6.ORCH-USE-CASES, clause 3.11.4.3 [i.2]. A final note covers steps 22-24.](a3472689858b068ef469213682965325_img.jpg) - -``` - -sequenceDiagram - participant Consumer as FOCOM SMOS Consumer - participant Producer as FOCOM SMOS Producer - participant IMS as O2-IMS - - Note right of Producer: PRECONDITION: -FOCOM SMOS Consumer: has acquired provisioningRequestId of the provisioning request by querying the list of already created and accepted provisioning request -FOCOM SMOS Consumer: has discovered the new version of the O-Cloud template information -IMS: Declarative Provisioning request object exist - - Note right of Producer: Create a new draft to update O-Cloud provisioning Request revision based on the content from the current revision of the provisioning request and with new O-Cloud template version and/or O-Cloud template name - - Consumer->>Producer: 1 Create request: A new draft O-Cloud provisioning request revision request (templateName, templateVersion, templateParameters, provisioningRequestId) - Producer->>Producer: 2 create a draft revision - Producer-->>Consumer: 3 Create response: A new draft O-Cloud provisioning request revision response (provisioningRequestId, statusInformation) - - Note right of Producer: Steps 4 to step 21 on this use case are same as step 4 to step 21 of the use case specified in clause 4.2.3.2 -But, Step 6, 7, 8 and Step 15, 16 and 17 in clause 4.2.3.2, will only be executed by the FOCOM SMOS Producer if additional O-Cloud resources are required due to the updated Provisioning request - - Note right of Producer: ref -1. FOCOM initiates request to IMS to update provisioning request -2. see the Use Case in ORAN.WG6.ORCH-USE-CASES, clause 3.11.4.3 [i.2] - - Note right of Producer: Steps 22 to step 24 on this use case are same as step 22 to step 24 of the use case specified in clause 4.2.3.2 - -``` - -UML Sequence Diagram for 'Create, update and execute existing O-Cloud provisioning request revision using new O-Cloud Template'. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer (under Service Management & Orchestration Framework), and O2-IMS (under O-Cloud). The sequence starts with a precondition block. Step 1: Consumer sends 'Create request' to Producer. Step 2: Producer sends 'create a draft revision' to itself. Step 3: Producer sends 'Create response' to Consumer. A note covers steps 4-21, mentioning that steps 6, 7, 8, 15, 16, and 17 are only executed by the Producer if additional resources are needed. A 'ref' block contains: 1. FOCOM initiates request to IMS to update provisioning request; 2. see the Use Case in ORAN.WG6.ORCH-USE-CASES, clause 3.11.4.3 [i.2]. A final note covers steps 22-24. - -Figure 4.2.5.3-1: Create, update and execute existing O-Cloud provisioning request revision using new O-Cloud Template - -### 4.2.6 Registering FOCOM SMOS for PM DME datatypes and associated operations - -#### 4.2.6.1 High level description - -The use case aims to register FOCOM SMOS as the data producer for a defined performance datatype in DME. PM data consumers e.g. rApps can discover these registered DME datatypes (see Note 1) and can request or subscribe to performance data for that DME datatype. - -As part of the register procedure, the FOCOM SMOS derives needed Performance data/PM Job related details & then uses DME APIs (see Note 2) for PM DME datatype registration by sharing PM data/PM Job related details (DME Type Information). - -FOCOM SMOS finally maintains mapping of created PM jobs for corresponding registered DME datatypes. - -Additionally, these registered datatypes can also be updated/deregistered as and when required using DME mechanism & FOCOM SMOS.s - -NOTE 1: DME functionalities (Like Discovering registered Datatypes) are out of scope for this TR & are just mentioned to explain the need of this use case. - -NOTE 2: R1 DME service APIs are defined in O-RAN.WG2.TS.R1AP [i.10], but DME SMOS APIs are not yet defined. - -NOTE 3: Detailed depiction of O2 interactions/actions towards O-Clouds are out of scope for this TR. - -#### 4.2.6.2 UML Sequence Table - -**Table 4.2.6.2-6: Registering FOCOM SMOS for Performance DME datatype & associated operations** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal (1) | Registration: The FOCOM SMOS registers as producer of data for a DME type. | | -| Actors and Roles |
  • - FOCOM SMOS: Data Registration Service consumer
  • - DME SMOS: Data registration service producer.
  • - O-Cloud IMS: To execute the request received from FOCOM SMOS
| | -| Assumptions | Capabilities assessment/exchange between SMO/FOCOM & O-Cloud(s)IMS(s) to :
  • - Identify supported protocols, mechanisms, and formats supported by O-Clouds
  • - IMS reports Performance Measurement Jobs and details like collection intervals to SMO
| | -| Preconditions |
  • - The FOCOM SMOS is authenticated/authorized to access & use the DME services.
  • - Performance datatypes defined in DME SMOS
  • - Availability of Default/customized PM Jobs
| | -| Begins when | FOCOM SMOS determines the need to register as a producer of performance data for a DME type. | | -| Step 1 (M) | Using Capability info, FOCOM derives the “data type identifier and needed DME type information” required to register as producer against any DME Datatype | | -| Using DME APIs | The FOCOM SMOS interacts with DME SMOS for Registering DME datatype to DME SMOS using DME datatype registration service API
Reference: see NOTE2 | | -| Step 2(M) | FOCOM SMOS maintains mapping of PM jobs for corresponding registered DME datatypes | | -| Ends when | FOCOM SMOS registers as producer of performance data for a DME type & maintains mapping of PM jobs for corresponding registered DME datatypes. | | -| Exceptions | n/a | | - -| | | | -|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Post Conditions | The performance DME type is discoverable by authenticated/authorized DME service consumers | | -| Traceability | REQ-FOCOM-FUN11 | | -| Goal (2) | Updating: The FOCOM SMOS as producer of performance data updates a DME type registration it has previously created. | | -| Actors and Roles |
  • - FOCOM SMOS: Data registration and discovery service Consumer.
  • - DME SMOS: Data registration and discovery service Producer.
| | -| Assumptions | | | -| Preconditions |
  • - The FOCOM SMOS is authenticated/authorized to access & use the DME Services.
  • - The FOCOM SMOS is registered as producer of data for a DME type.
| | -| Begins when | The FOCOM SMOS determines the need to update a DME type registration previously created | | -| Step 1 (M) | Based on Capability info changes (O-Cloud Level/PM Job level), FOCOM derives the updates needed on “data type identifier or on DME type information” required to update the previous configured DME datatype registration | | -| Using DME APIs | The FOCOM SMOS interacts with DME SMOS to Update DME datatype on DME SMOS using Update registered service API
Reference: see NOTE2 | | -| Step 2 (M) | FOCOM SMOS updates the mapping list of PM job to registered DME datatypes | | -| Ends when | The FOCOM SMOS has updated the DME type registration & updates the mapping list of PM job to registered DME | | -| Exceptions | n/a | | -| Post Conditions | The “updated” Performance DME type is discoverable by authenticated/authorized DME Service Consumer. | | -| Traceability | REQ-FOCOM-FUN11 | | -| Goal (3) | Deregistration: The FOCOM SMOS deregisters as producer of performance data for a DME type. | | -| Actors and Roles |
  • - FOCOM SMOS: Data registration and discovery service consumer.
  • - DME SMOS: Data registration and discovery service producer.
| | -| Assumptions | FOCOM SMOS is not producing any data for the DME type. | | -| Preconditions |
  • - The FOCOM SMOS is authenticated/authorized to access & use the DME Services.
  • - The FOCOM SMOS is registered as producer of data for a DME type
| | -| Begins when | The FOCOM SMOS determines the need to deregister as producer of data for a DME type that it no longer intends to produce. | | -| Step 1 (M) | Interface with respective O-Clouds(O2 IMSs) & Delete mapped PM Job (Suspended State) accordingly [Refer ORAN.WG6.ORCH-USE-CASES, clause3.8.7 [i.2]] | | -| Using DME APIs | The FOCOM SMOS interacts with DME SMOS for Deregistering DME datatype on DME SMOS using Deregister service API
Reference: see NOTE2. | | -| Step 2 (M) | FOCOM SMOS Updates the mapping list of PM job to registered DME datatypes | | -| Ends when | The FOCOM SMOS was able to deregister the as producer of performance data for the DME type along with corresponding PM jobs deletion & mapping maintenance. | | -| Exceptions | n/a | | -| Post Conditions | The FOCOM SMOS will not receive any request of performance data for the DME type | | -| Traceability | REQ-FOCOM-FUN11 | | - -#### 4.2.6.3 UML Sequence Diagram - -![UML Sequence Diagram for Service Management & Orchestration Framework (DME SMOS, FOCOM SMOS) and IMS (O-Cloud(s) IMS(s)). The diagram shows four main interaction sequences: Capabilities assessment, Registering Performance related DME datatypes, Update previously registered Performance DME datatype, and Deregister DME type. Each sequence includes preconditions, internal logic, and API references (NOTE2).](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) - -**Service Management & Orchestration Framework** - -**DME SMOS** -DME Service Producer - -**FOCOM SMOS** -DME Service Consumer - -**IMS** -O-Cloud(s) IMS(s) - -**PRECONDITION:** -The FOCOM SMOS is authenticated/authorized to access & use the DME Services. -Performance datatypes defined in DME SMOS -Availability of Default/customized PM Jobs - -**Assumption: Capabilities assessment/exchange between SMO/FOCOM & O-Cloud(s)IMS(s)** -Identifies supported protocols, mechanisms, and formats supported by O-Cloud IMS reports Performance Measurement Jobs and details like collection intervals to SMO - -**Registering Performance related DME datatypes** - -**Using Capability info captured above** -1 FOCOM derives the "data type identifier and needed DME type information" required to register as producer against any DME Datatype - -**ref** -Registering DME datatype to DME SMOS using DME datatype registration service API -Reference: see NOTE2 - -Maintains mapping of PM jobs -2 for corresponding Registered DME DataTypes - -**PRECONDITION:** -The FOCOM SMOS is authenticated/authorized to access & use the DME Services. -The FOCOM SMOS is registered as producer of data for a DME type - -**Update previously registered Performance DME datatype** - -**Based on Capability info changes (O-Cloud Level/PM Job level)** -1 FOCOM derives the updates needed on "data type identifier or on DME type information" required to update the previous configured DME datatype registration - -**ref** -Updating DME datatype on DME SMOS using Update registered service API -Reference: see NOTE2 - -2 Update the mapping list of PM job to registered DME datatypes - -**Deregister DME type** - -**For cases like customized PM job/data NOT needed anymore** -1 Interface with respective O-Clouds(O2 IMSs) & Delete mapped PM Job (Suspended State) accordingly -[Refer the Use Case in ORAN.WG6.ORCH-USE-CASES, clause 3.8.7 [i.2]] - -**ref** -Deregistering DME datatype on DME SMOS using Deregister service API -Reference: see NOTE2 - -2 Update the mapping list of PM job to registered DME datatypes - -UML Sequence Diagram for Service Management & Orchestration Framework (DME SMOS, FOCOM SMOS) and IMS (O-Cloud(s) IMS(s)). The diagram shows four main interaction sequences: Capabilities assessment, Registering Performance related DME datatypes, Update previously registered Performance DME datatype, and Deregister DME type. Each sequence includes preconditions, internal logic, and API references (NOTE2). - -**Figure 4.2.6.3-1: Registering FOCOM SMOS for Performance DME datatype & associated operations** - -### 4.2.7 Subscribing to PM Datatype/Dataset & associated operations (Update/Remove subscriptions) - -#### 4.2.7.1 High level description - -The use case describes how an authenticated & authorized PM data consumer (like rApp) can subscribe and obtain PM data using DME mechanism & FOCOM SMOS NBIs. Additionally, these subscriptions can also be updated/removed as and when required using FOCOM SMOS NBIs. - -The use case also covers these operations (create/update/remove subscription) in multi-user scenario. - -#### 4.2.7.2 UML Sequence Table - -**Table 4.2.7.2-7: Subscribing to PM Datatype/Dataset & associated operations (Update/Remove subscriptions)** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------| -| Goal (1) | Subscription: The DME service consumer subscribes & obtains PM data. | | -| Actors and Roles |
  • - FOCOM SMOS: In the role of “FOCOM SMOS Producer”
  • - DME SMOS: In the role of “DME Service Producer” & “FOCOM SMOS Consumer”
  • - DME service consumer: End consumer of performance data e.g. rApps or other SMOF
  • - O-Cloud IMS: To execute the request received from FOCOM SMOS
| | -| Assumptions | | | -| Preconditions |
  • - The DME services consumer is authenticated/authorized to access & use the DME Services.
  • - The DME services consumer has obtained the registered PM datatype information e.g. by discovery.
  • - The FOCOM SMOS consumer is authenticated/authorized to access & use the FOCOM SMOS services.
| | -| Begins when | The DME Service Consumer determines the need to subscribe to required PM data. | | -| Step 1 (M) | The DME service consumer triggers subscription request of PM data with subscription request information. This information may comprise ConsumerId, PM datatype/dataset info, and subscription criteria (optional). | | -| Step 2 (M) | The DME service producer validates the received subscription request information | | -| Alternative Procedure (ALT1) | If no preexisting subscriptions for requested PM datatype/dataset | | -| Step 3 (ALT1) | The DME service producer creates a new Consumer Subscription identifier entry on the PM datatype/dataset for that consumer [e.g. consumer subscription ID1]. | | -| Step 4 (ALT1) | Upon creation of Consumer Subscription identifier entry, the DME SMOS in role of “FOCOM SMOS consumer” triggers a data subscription request towards FOCOM SMOS | | -| Step 5 (ALT1) | FOCOM SMOS identifies the corresponding PM jobs that are mapped with the datatype/dataset. | | -| Step 6 (ALT1) | Based on the requested subscription, FOCOM SMOS interfaces with respective O-Cloud (O2 IMSs) functions & configures the requested subscription to the mapped PM jobs. These PM jobs will be triggered and moved from suspended state to running. | Refer ORAN.WG6.ORCH-USE-CASES, clause 3.8.2 & 3.8.10 [i.2] | - -| | | | -|----------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------| -| | | | -| Step 7(ALT1) | FOCOM SMOS responds back to DME SMOS with confirmation of subscription creation. | | -| Step 8 (ALT1) | The DME service producer maintains a mapping info of Consumer Subscription identifier entry to subscribed PMdatatypes/dataset | | -| Alternative Procedure (ALT2) | If preexisting similar subscriptions for requested datatype/dataset exists | | -| Step 9 (ALT2) | The DME service producer creates a new Consumer Subscription identifier entry on the PM datatype/dataset for the new consumer [e.g. consumer subscription ID2] | | -| Step 10(ALT2) | The DME service producer updates the mapping info of the already subscribed PMdatatypes/dataset with the new Consumersubscription ID | | -| Step 11(M) | The DME service producer sends success response to DME service consumer (rApp) with the newly created Consumersubscription ID. | | -| Once Subscribed data is available. Based on requested (& Supported) Delivery mechanism | | | -| Step (M) | FOCOM SMOS coordinates with respective O-Cloud IMS for Collecting & Aggregating PM Data from Multiple O-Clouds | | -| Step (M) | FOCOM SMOS Transfer the needed notifications and Subscribed PM data to FOCOM SMOS Consumer | | -| Step (M) | DME SMOS finally Transfer the needed notifications and Subscribed PM data to end Consumer/subscriber | | -| Ends when | End consumer is able to subscribe and finally receive needed notifications and Subscribed PM data | | -| Exceptions | n/a | | -| Post Conditions | DME service consumer/end consumer (e.g. rApp) is able to receive needed notifications and intended subscribed PM data | | -| Traceability | REQ-FOCOM-FUN12 , REQ-FOCOM-FUN15 | | -| Goal (2) | Update: The DME service consumer/end consumer (e.g. rApps) updates its previously created PM data subscription. | | -| Actors and Roles |
  • - FOCOM SMOS: In the role of “FOCOM SMOS Producer”
  • - DME SMOS: In the role of “DME Service Producer” & “FOCOM SMOS Consumer”
  • - DME service consumer: End consumer of performance data e.g. rApps or other SMOF
  • - O-Cloud IMS: To execute the request received from FOCOM SMOS
| | -| Assumptions | | | -| Preconditions |
  • - The consumer is authenticated/authorized to access & use the DME services.
  • - The consumer has previously created PM data subscription.
  • - The DME services consumer has obtained the registered PM datatype information e.g. by discovery.
| | -| Begins when | The DME service consumer determines the need to update a subscription it has previously created | | -| Step 1 (M) | The DME service consumer triggers update request with subscription update information.
This information may comprise ConsumerId, Consumersubscription ID and update information. | | -| Step 2 (M) | DME SMOS (DME service producer) validates the received update subscription request | | -| Alternative Procedure (ALT1) | If associated PM datatype is mapped with only single Consumersubscription ID | | -| Step 3 (ALT1) | DME SMOS (FOCOM SMOS consumer) triggers update subscription request towards FOCOM SMOS producer | | -| Step 4 (ALT1) | Based on the requested update, FOCOM SMOS interfaces with respective O-Cloud (O2 IMSs) functions & configures the requested update to the mapped PM jobs. | Refer ORAN.WG6.ORCH-USE-CASES, clause 3.8.13 [i.2] | -| Step 5 (ALT1) | FOCOM SMOS producer shares the update subscription success response to DME SMOS (FOCOM SMOS consumer) | | -| Alternative Procedure (ALT2) | If associated PM datatype is mapped with multiple Consumersubscription IDs | | - -| | | | -|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------| -| Step 6 (ALT2) | The DME SMOS (DME service producer) removes the received Consumersubscription ID as well as its entries from the Consumersubscription IDs - PMdatatype Mapping table. | | -| Step 7 (ALT2) | Aligned to consumer update subscription changes, The DME service producer creates a new subscription entry for the requested PM datatype/dataset for that consumer [e.g. consumer subscription IDx]. | | -| Step 8 (ALT2) | Upon creation of subscription entry, the DME SMOS in role of "FOCOM SMOS consumer" triggers a data subscription request towards FOCOM SMOS | | -| Step 9 (ALT2) | FOCOM SMOS identifies the corresponding PM jobs that are mapped with the requested datatype/dataset. | | -| Step 10 (ALT2) | Based on the requested subscription, FOCOM SMOS interfaces with respective O-Cloud (O2 IMSs) functions & configures the requested subscription to the mapped PM jobs. These PM jobs will be triggered and moved from suspended state to running. | | -| Step 11(ALT2) | FOCOM SMOS responds back to DME SMOS with confirmation of subscription creation. | | -| Step 12 (ALT2) | The DME service producer maintains a mapping info of Consumersubscription IDs to subscribed PMdatatypes/dataset(as per update request) | | -| Step 13 (M) | The DME service producer sends success response to DME service consumer (rApp) with same or newly created Consumersubscription ID. | | -| Ends when | DME Service Consumer (like rApp) has updated the data subscription. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-FOCOM-FUN13 | | -| Goal (3) | The DME service Consumer/End Consumer (e.g. rAPP) removes the data subscription. | | -| Actors and Roles |
  • - FOCOM SMOS: In the role of "FOCOM SMOS Producer"
  • - DME SMOS: In the role of "DME Service Producer" & "FOCOM SMOS Consumer"
  • - DME service consumer: End consumer of performance data e.g. rApps or other SMOF
  • - O-Cloud IMS: To execute the request received from FOCOM SMOS
| | -| Assumptions | | | -| Preconditions | - The Consumer has previously created PM data subscription. | | -| Begins when | The DME Service Consumer (like rApp) determines the need to remove a subscription it has previously created | | -| Step 1 (M) | The DME Service Consumer (like rApp) triggers Unsubscribe request towards DME service Producer by sharing details like (ConsumerId, Consumersubscription ID) | | -| Step 2 (M) | DME SMOS (DME service Producer) Validate the Consumer's remove subscription request | | -| Alternative procedure (ALT1) | If associated subscribed PM datatype is Mapped with multiple Consumersubscription IDs | | -| Step 3 (ALT1) | DME SMOS (DME service Producer) Remove current Consumersubscription IDs & update Consumersubscription IDs - PMdatatype Mapping Table | | -| Alternative Procedure (ALT2) | if associated subscribed PM datatype is Mapped with only single Consumersubscription ID | | -| Step 4 (ALT2) | DME SMOS (FOCOM SMOS Consumer) triggers remove Subscription request towards FOCOM SMOS Producer | | -| Step 5 (ALT2) | FOCOM SMOS Producer in turns coordinates with respective O-Cloud IMSs & remove Subscription entries from mapped PM Jobs towards IMS | [Refer ORAN.WG6.ORCH-USE-CASES, clause 3.8.14 [i.2]] | -| Step 6 (ALT2) | FOCOM SMOS Producer shares the remove subscription success from mapped jobs response to DME SMOS (FOCOM SMOS Consumer) | | -| Step 7 (ALT2) | DME SMOS (DME service Producer) Remove this Consumersubscription IDs & update Consumersubscription IDs - PMdatatype Mapping Table | | -| Step 8 (M) | DME SMOS (DME service Producer) response to DME Service Consumer (like rApp) with Successful completion of remove Subscription request | | - -| | | | -|-----------------|---------------------------------------------------------------------|--| -| Ends when | DME Service Consumer (like rApp) has removed the data subscription. | | -| Exceptions | n/a | | -| Post Conditions | n/a | | -| Traceability | REQ-FOCOM-FUN14 | | - -#### 4.2.7.3 UML Sequence Diagram - -![UML Sequence Diagram for Service Management & orchestration Framework. Lifelines: DME Service Consumer, DME Services Producer, FOCOM SMOS Consumer, FOCOM SMOS Producer, O2-IMS. The diagram shows the interaction for subscribing to data, including preconditions, subscription creation, data mapping, and data delivery from O-Clouds.](28d75f39a24203712ee907b32cf0bbe5_img.jpg) - -**Service Management & orchestration Framework** - -**PRECONDITION:** - The DME Services Consumer is authenticated/authorized to access & use the DME Services. - The DME Services Consumer has obtained the registered PM datatype information e.g. by discovery. - The FOCOM SMOS Consumer is authenticated/authorized to access & use the FOCOM SMOS. - -**Sequence of Messages:** - -- Subscribe data request** (ConsumerId, PM datatype/dataset info, Subscription Criteria (optional)) from DME Service Consumer to DME Services Producer. -- Validate Subscription request** (PM datatype/dataset correctness, any preexisting similar subscriptions for requested datatype etc) from DME Services Producer to DME Service Consumer. -- alt: [If No Preexisting subscriptions for requested PM datatype.]** - - 3 **Create requested Subscription Entry** (Consumersubscription ID1) from DME Services Producer to DME Service Consumer. - - DME functions subscribes data from FOCOM SMOS** (activation): - - 4 **Trigger Data Subscription request** from DME Services Producer to FOCOM SMOS Producer. - - 5 **Identifies the mapped PM Jobs with datatype.** (self-call on FOCOM SMOS Producer). - - Coordinates with O-Clouds O2IMSs & configure requested subscription to mapped PM Jobs. - - 6 **Trigger(Resume)PM Jobs.** [Refer the Use Case in ORAN.WG6.CRCH-USE-CASES, clause 3.8.2 & 3.8.10 [i.2]] from FOCOM SMOS Producer to O2-IMS. - - 7 **Trigger Data Subscription response** from FOCOM SMOS Producer to DME Services Producer. - - 8 **Maintains mapping info of Consumersubscription IDs** to subscribed PMdatatypes/dataset from DME Services Producer to DME Service Consumer. -- alt: [If preexisting similar subscriptions for requested datatype exists by some other Consumer as well]** - - 9 **Create requested new Subscription Entry** (Consumersubscription ID2) for new consumer from DME Services Producer to DME Service Consumer. - - 10 **Updated (appends) mapping info of new Consumersubscription IDs** to subscribed PMdatatypes/dataset from DME Services Producer to DME Service Consumer. - -11 **Subscribe data response** (Success) from DME Services Producer to DME Service Consumer. - -**Once Subscribed data is available. Based on requested(& Supported) Delivery mechanism.** (activation): - -- Collecting & Aggregating Data from Multiple O-Clouds from O2-IMS to FOCOM SMOS Producer. -- Transfer the needed notifications and Subscribed PM data to FOCOM SMOS Consumer from FOCOM SMOS Producer to FOCOM SMOS Consumer. -- Transfer the needed notifications and Subscribed PM data to end Consumer/subscriber via DME SMOS from FOCOM SMOS Consumer to DME Service Consumer. - -UML Sequence Diagram for Service Management & orchestration Framework. Lifelines: DME Service Consumer, DME Services Producer, FOCOM SMOS Consumer, FOCOM SMOS Producer, O2-IMS. The diagram shows the interaction for subscribing to data, including preconditions, subscription creation, data mapping, and data delivery from O-Clouds. - -![Sequence diagram for subscribing PM Datatype/Data Set & associated operations (Update/Remove subscriptions).](fa01531ea2c45beeb4036005da3037a4_img.jpg) - -**PRECONDITION:** -The Consumer is authenticated/authorized to access & use the DME Services. -The Consumer has previously created PM data subscription. - -**Sequence Diagram: Subscribing PM Datatype/Data Set & associated operations (Update/Remove subscriptions)** - -**Participants:** - -- DME Service Consumer -- DME Services Producer -- FOCOM SMOS Consumer -- FOCOM SMOS Producer -- O-Cloud(s) IMS(s) - -**Operations:** - -- Update PM data Subscription** - - DME Service Consumer sends **Update subscription request** (ConsumerId, Consumersubscription ID, subscription update information) to DME Services Producer. - - DME Services Producer validates the Consumer's Update subscription request. - - alt: If associated subscribed PM datatype is Mapped with only single Consumersubscription ID** - - FOCOM SMOS Consumer sends **Update Subscription towards data producer request** to FOCOM SMOS Producer. - - FOCOM SMOS Producer sends **Update Subscription to mapped PM Jobs towards IMS** (Refer the Use Case in ORAN.WG6.ORCH-USE-CASES, clause 3.8.13 [i.2]) to O-Cloud(s) IMS(s). - - FOCOM SMOS Producer receives **Update Subscription to data producer response** from FOCOM SMOS Consumer. - - alt: Associated subscribed PM datatype is Mapped with multiple Consumersubscription IDs** - - DME Services Producer removes current Consumersubscription IDs (update Consumersubscription IDs - PMdatatype Mapping Table). - - DME Services Producer creates new Consumersubscription ID entry. - - FOCOM SMOS Consumer sends **Create new Subscription based on Update request** to FOCOM SMOS Producer. - - FOCOM SMOS Producer identifies the mapped PM Jobs with datatype. - - FOCOM SMOS Producer sends **Based on Update request, Create Subscription to mapped PM Jobs towards IMS** to O-Cloud(s) IMS(s). - - FOCOM SMOS Producer receives **Create new Subscription based on Update response(success)** from FOCOM SMOS Consumer. - - DME Services Producer maintains/updates new Consumersubscription IDs (PMdatatype Mapping Table). - - DME Services Producer sends **Update subscription response(success)** to DME Service Consumer. -- Remove PM data Subscription** - - DME Service Consumer sends **Unsubscribe request** (ConsumerId, DME subscription ID) to DME Services Producer. - - DME Services Producer validates the Consumer's Unsubscribe request. - - alt: If Associated subscribed PM datatype is Mapped with multiple Consumersubscription IDs** - - DME Services Producer removes current Consumersubscription IDs (update Consumersubscription IDs - PMdatatype Mapping Table). - - alt: If associated subscribed PM datatype is Mapped with only single Consumersubscription ID** - - FOCOM SMOS Consumer sends **Request for removal of mapped PM Jobs/data Subscription** to FOCOM SMOS Producer. - - FOCOM SMOS Producer sends **remove Subscription entries from mapped PM Jobs towards IMS** (Refer the Use Case in ORAN.WG6.ORCH-USE-CASES, clause 3.8.14 [i.2]) to O-Cloud(s) IMS(s). - - FOCOM SMOS Producer receives **Response for removal of mapped PM Jobs/data Subscription** from FOCOM SMOS Consumer. - - DME Services Producer removes Consumersubscription ID (update Consumersubscription IDs - PMdatatype Mapping Table). - - DME Services Producer sends **Unsubscribe response (success)** to DME Service Consumer. - -Sequence diagram for subscribing PM Datatype/Data Set & associated operations (Update/Remove subscriptions). - -Figure 4.2.7.3-1: Subscribing PM Datatype/Data Set & associated operations (Update/Remove subscriptions) - -### 4.2.8 Delete O-Cloud provisioningRequest instance - -#### 4.2.8.1 High level description - -The use case aims to enable a FOCOM SMOS Consumer e.g. an rApp or other SMOF, to delete the existing O-Cloud provisioningRequest instance. Before this use case is initiated it is assumed that all FOCOM SMOS Consumers have coordinated in regard to deleting the provisioning Request. - -#### 4.2.8.2 Sequence Description - -**Table 4.2.8.2-8: Delete O-Cloud provisioningRequest instance** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To delete the O-Cloud provisioningRequest instance | | -| Actors and Roles | FOCOM SMOS Consumer – An authorized consumer e.g. rApp or other SMOF, consuming the services of FOCOM SMOS
FOCOM SMOS Producer – Execute the request to delete O-Cloud provisioning request instance.
IMS - To execute the request received from FOCOM SMOS Producer | | -| Assumptions | 1. It is assumed that all FOCOM SMOS Consumers have coordinated in regard to deleting the provisioningRequest | | -| Preconditions | 1. FOCOM SMOS Producer has acquired provisioningRequestId
2. FOCOM SMOS Consumer is authorized to delete provisioningRequestId | | -| Begins when | FOCOM SMOS Consumer intends to delete the O-Cloud Node cluster and/or infrastructure resources | | -| Step 1 (M) | FOCOM SMOS Consumer sends a request to FOCOM SMOS Producer to delete the O-Cloud Node cluster and/or infrastructure resources with provisioningRequestId as a parameter | | -| Step 2 (M) | FOCOM SMOS Consumer validates the request | | -| Step 3 (M) | If the validation is successful, FOCOM SMOS Producer checks if the provisioningRequestId is in draft state. If provisioningRequestId is in draft state, FOCOM SMOS Producer delete the instance of the provisioningRequestId. | | -| Step 4(M) | FOCOM SMOS Producer responds to FOCOM SMOS Consumer | | -| Step 5(M) | If the validation is successful, FOCOM SMOS Producer checks if the provisioningRequestId is in approved state. FOCOM SMOS Producer interacts with IMS to delete the resources.

NOTE 1 | | -| Step 6 (M) | If success received from IMS, FOCOM SMOS Producer deletes the information related to the provisioningRequestId | | -| Step 7 (M) | FOCOM SMOS Producer sends success response to FOCOM SMOS Consumer | | -| Step 8 (M) | If failure is observed in IMS, FOCOM SMOS Producer responds with information about the failure | | - -| | | | -|-------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 9 (M) | If the validation fail, FOCOM SMOS Producer responds with information about the failure | | -| Ends when | FOCOM SMOS Consumer successfully requests the deletion of the O-Cloud Node Cluster and/or infrastructure resources or when information about the failure is received | | -| Exceptions |
  1. 1. The exception is encountered such as O-Cloud Node Cluster not found,. An exception notification will be returned; and the use case will end this situation
  2. 2. Validation Fail – This exception occurs when the validation of the request fails
| | -| Post Conditions | ProvisioningRequest instance is deleted and O-Cloud Resource is released | | -| Traceability | REQ-FOCOM-FUN16 | | -| NOTE 1: The sequence of interactions between the FOCOM SMOS Producer and IMS is specified in ORAN.WG6.ORCH-USE-CASES, clause 3.11.3 [i.2] | | | - -#### 4.2.8.3 UML Sequence Diagram - -![UML Sequence Diagram for 'Delete O-Cloud provisioningRequest instance'. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer, IMS. The diagram shows a request from Consumer to Producer, followed by validation steps involving the IMS. It includes nested alt blocks for 'validation is successful' and 'validation fail', with sub-alt blocks for 'draft state' and 'approve state'.](b5335262987c819d7f71ce40f99cb71b_img.jpg) - -``` - -sequenceDiagram - participant Consumer as FOCOM SMOS Consumer - participant Producer as FOCOM SMOS Producer - participant IMS as IMS - - Note right of Producer: PRECONDITION: -FOCOM SMOS Producer has acquired the provisioningRequestId -FOCOM SMOS Consumer is authorized - - Note over Consumer, Producer: Delete O-Cloud provisioningRequest instance - - Consumer->>Producer: 1 Delete provisioningRequest instance request (provisioningRequestId) - Producer->>Producer: 2 validates the request - alt validation is successful - Producer->>IMS: 3 check if the provisioningRequestId is in draft or in approved state - alt provisioningRequestId is in draft state - Producer->>Producer: 4 delete the information related to provisioningRequestId - Producer-->>Consumer: 5 Delete provisioningRequest instance response - else provisioningRequestId is approve state - Note right of Producer: FOCOM interact with IMS to delete the associated O-Cloud Node Cluster. -see the Use Case in ORAN.WG6.ORCH-USE-CASES, clause 3.11.3 [i.2] - alt O-Cloud Node cluster delete in IMS - Producer->>Producer: 6 delete the information related to provisioningRequestId - Producer-->>Consumer: 7 Delete provisioningRequest instance response - else failure observed in IMS - Producer-->>Consumer: 8 Delete provisioningRequest instance response (info of the failure) - end - end - else validation fail - Producer-->>Consumer: 9 Delete provisioningRequest instance response (info of the failure) - end - - Note over Consumer, Producer: Delete O-Cloud provisioningRequest instance - -``` - -UML Sequence Diagram for 'Delete O-Cloud provisioningRequest instance'. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer, IMS. The diagram shows a request from Consumer to Producer, followed by validation steps involving the IMS. It includes nested alt blocks for 'validation is successful' and 'validation fail', with sub-alt blocks for 'draft state' and 'approve state'. - -Figure 4.2.8.3-1: Delete O-Cloud provisioningRequest instance - -### 4.2.9 Restore or Update O-Cloud provisioning request revision - -#### 4.2.9.1 High level description - -The use case aims to restore to a previously created and accepted provisioning request configuration. The procedure is the same as the update procedure i.e., FOCOM SMOS Consumer uses the previous provisioning request revisionId and updates the configurations. - -Before this use case is started it is expected that the FOCOM SMOS Consumer e.g. an rApp or other SMOF - -1. Has acquired provisioningRequestId and O-Cloud template information. - -- Created and/or updated a draft provisioning request revision using same O-Cloud Template or different O-Cloud Template version. - -#### 4.2.9.2 Sequence Description - -**Table 4.2.9.2-9: Restore or Update O-Cloud provisioning request revision** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------| -| Goal | To restore/update to previously created and approved provisioning request instance | | -| Actors and Roles | FOCOM SMOS Consumer – An authorized consumer e.g. rApp or other SMOF, consuming the services of FOCOM SMOS
FOCOM SMOS Producer – Receives update and execute request for the O-Cloud provisioning request and sends back responses.
IMS – To execute the request received from FOCOM SMOS Producer | | -| Assumptions |
  1. Previously allocated resources on the IMS have not changed compared to previously successfully deployed state
  2. In the failed state, IMS shouldn't release the requested resources by the FOCOM SMOS Consumer
| | -| Preconditions | O-Cloud Operational – O-Cloud is operational and has registered with the SMO
FOCOM SMOS Consumer - Has acquired available provisioningRequestId and O-Cloud template information. Has created/updated a draft provisioning request revision using same O-Cloud Template or different O-Cloud Template version
IMS - Declarative Provisioning request object exists
Privilege – The FOCOM SMOS Consumer is authorized | Use case 4.2.2, Step 1 to 3 of use case 4.2.3 and 4.2.4 | -| Begins when | A FOCOM SMOS Consumer, request to approve the draft O-Cloud provisioning request | | -| Step 1 (M) | FOCOM SMOS Consumer request to FOCOM SMOS Producer to approve the draft and execute the O-Cloud provisioning request with provisioningRequestId as a parameter
See NOTE 1 | | -| FOCOM SMOS Producer accepts and approves the Provisioning Request and initiates a request to update provisioning request towards the IMS at O-Cloud
See NOTE 2 | | | -| Step 2 (M) | A failure was observed, the FOCOM SMOS Producer returns information to FOCOM SMOS Consumer about the failure and probable cause | | -| FOCOM SMOS Consumer, may
Alternatives:
  1. FOCOM SMOS Consumer either update the failed configuration or
  2. FOCOM SMOS Consumer restore to same configuration of the previous revision and use that in order to create the new revision with new revisionId
| | | -| Alternative 1: | | | -| Step 3 (M) | FOCOM SMOS Consumer initiates a request to create a new draft to update O-Cloud provisioning request revision request with updated template parameter and provisioningRequestId as a parameter | | - -| | | | -|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Step 4 (M) | FOCOM SMOS Producer create a new draft revision based on the updated configuration | | -| Step 5 (M) | FOCOM SMOS Producer respond to FOCOM SMOS Consumer with provisioningRequestId as a parameter | | -| Alternative 2 | | | -| Step 6 (M) | FOCOM SMOS Consumer request FOCOM SMOS Producer to retrieve the previously approved revisionId of the provisioningRequest with provisioningRequestId, as a parameter | | -| Step 7 (M) | FOCOM SMOS Producer fetch the previously approved revisionId of the provisioningRequestId | | -| Step 8 (M) | FOCOM SMOS Producer respond with the revisionId | | -| Step 9 (M) | FOCOM SMOS Consumer request FOCOM SMOS Producer to restore the configuration of the provisioningRequest with provisioningRequestId, and previous revisionId as a parameter | | -| Step 10 (M) | FOCOM SMOS Producer create a new draft revision based on the previous approved configuration | | -| Step 11 (M) | FOCOM SMOS Producer, sends an asynchronous response to restore request with provisioningRequestId as a parameter | | -| Steps 12 to step 28 on this use case are same as step 4 to step 21 of use case specified in clause 4.2.3.2. But, Step 6, 7, 8 and Step 15, 16 and 17 in clause 4.2.3.2, will only be executed by the FOCOM SMOS Producer if additional O-Cloud resources are required due to the updated Provisioning request. | | | -| FOCOM SMOS Producer accepts and approves the Provisioning Request and initiates a request to update provisioning request towards the IMS at O-Cloud | | | -| See NOTE 2 | | | -| Steps 29 to 31 on this use case are same as step 22 to step 24 of the use case specified in clause 4.2.3.2 | | | -| Ends when | FOCOM SMOS Consumer either
  1. 1. FOCOM SMOS Consumer either update the failed configuration or
  2. 2. FOCOM SMOS Consumer restore to same configuration of the previous revision and use that in order to create the new revision with new revisionId
| | -| Exceptions | N/A | | -| Post Conditions | N/A | | -| Traceability | REQ-FOCOM-FUN17, REQ-FOCOM-FUN4, REQ-FOCOM-FUN6, REQ-FOCOM-FUN7, REQ-FOCOM-FUN8 | | -| NOTE 1: An approve O-Cloud provisioning request instance revision is approved by the FOCOM SMOS Consumer and accepted for execution by FOCOM SMOS Producer.
NOTE 2: The sequence of interactions between the FOCOM SMOS Producer and IMS is specified in ORAN.WG6.ORCH-USE-CASES, clause 3.11.4 [i.2]. | | | - -#### 4.2.9.3 UML Sequence Diagram - -![UML Sequence Diagram for Restore or Update O-Cloud provisioning request revision. Lifelines: FOCOM SMOS Consumer, Service Management & Orchestration Framework (FOCOM SMOS), and O-Cloud (O2-IMS).](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) - -**PRECONDITION:** - FOCOM SMOS Consumer: - 1. Has acquired provisioningRequestId by querying the list of already created and accepted provisioning request and has acquired O-Cloud template information - 2. Has created/updated a draft provisioning request revision using same O-Cloud Template or different O-Cloud Template version. - FOCOM SMOS Producer: Validation and feasibility check succeeded on the provisioningRequest - IMS: Declarative Provisioning request object exists - -**Assumption:** - 1. Previously allocated resources on the O2IMS has not changed compared to previously successfully deployed state - 2. In the failed state, IMS shouldn't release the requested resources by the FOCOM SMOS Consumer - -**Sequence:** - -- FOCOM SMOS Consumer sends "approve the draft and execute the O-Cloud Provisioning Request Instance (provisioningRequestId)" to FOCOM SMOS. -- FOCOM SMOS sends a request to O2-IMS (ref: 1. FOCOM initiates request to IMS to update provisioning request, 2. see the Use Case in ORAN.WG6.ORCH-USE-CASES, clause 3.11.4.3 [i.2]). -- O2-IMS returns a failure (provisioningRequestId.info on failure) to FOCOM SMOS. -- FOCOM SMOS Consumer receives failure and decides to either update the failed configuration or roll back to the previous revision. -- alt: [FOCOM SMOS Consumer update the failed configuration]** - - FOCOM SMOS Consumer sends "Create request: A draft O-Cloud provisioning request revision request (templateParameter, provisioningRequestId)" to FOCOM SMOS. - - FOCOM SMOS sends "create a new draft revision based on the updated configuration" to O2-IMS. - - FOCOM SMOS returns "Create response: A draft O-Cloud provisioning request revision response (provisioningRequestId, statusInformation)" to FOCOM SMOS Consumer. -- alt: [FOCOM SMOS Consumer restore to same configuration of the previous revision and use that in order to create the new revisionId]** - - FOCOM SMOS Consumer sends "Query previously approved revisionId request(provisioningRequestId)" to FOCOM SMOS. - - FOCOM SMOS sends "Fetch previously approved revisionId" to O2-IMS. - - O2-IMS returns "Query previously approved revisionId response (revisionId)" to FOCOM SMOS. - - FOCOM SMOS Consumer sends "Restore configuration request(provisioningRequestId, previous revisionId)" to FOCOM SMOS. - - FOCOM SMOS sends "create a new draft revision based on the previous approved configuration" to O2-IMS. - - FOCOM SMOS returns "Restore configuration response (provisioningRequestId)" to FOCOM SMOS Consumer. - -Steps 12 to step 28 on this use case are same as step 4 to step 21 of the use case specified in clause 4.2.3.2. But, Step 6, 7, 8 and Step 15, 16 and 17 in clause 4.2.3.2, will only be executed by the FOCOM SMOS Producer if additional O-Cloud resources are required due to the updated Provisioning request - -**ref:** 1. FOCOM initiates request to IMS to update provisioning request, 2. see the Use Case in ORAN.WG6.ORCH-USE-CASES, clause 3.11.4.3 [i.2] - -Steps 29 to step 31 on this use case are same as step 22 to step 24 of the use case specified in clause 4.2.3.2 - -UML Sequence Diagram for Restore or Update O-Cloud provisioning request revision. Lifelines: FOCOM SMOS Consumer, Service Management & Orchestration Framework (FOCOM SMOS), and O-Cloud (O2-IMS). - -Figure 4.2.9.3-1: Restore or Update O-Cloud provisioning request revision - -### 4.2.10 O-Cloud provisioningRequest status query - -#### 4.2.10.1 High level description - -The use case aims to enable a FOCOM SMOS Consumer e.g. an rApp or other SMOF, to retrieve the status of the provisioningRequest. Before this use case is initiated, FOCOM SMOS has created the provisioningRequestId. - -#### 4.2.10.2 Sequence Description - -**Table 4.2.10.2-10: O-Cloud provisioningRequest status query** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | To retrieve the O-Cloud provisioningRequest status information | | -| Actors and Roles | FOCOM SMOS Consumer – An authorized consumer e.g. rApp or other SMOF, consuming the services of FOCOM SMOS
FOCOM SMOS Producer – Produces the status information of provisioningRequest.
IMS - To execute the request received from FOCOM SMOS Producer | | -| Assumptions | N/A | | -| Preconditions | 3. FOCOM SMOS Producer has created provisioningRequestId
4. FOCOM SMOS Consumer is authorized to retrieve the status information | | -| Begins when | FOCOM SMOS Consumer intends to query the status of O-Cloud provisioningRequest | | -| Step 1 (M) | FOCOM SMOS Consumer sends a request to FOCOM SMOS Producer to query the status of provisioningRequest with provisioningRequestId as a parameter | | -| Step 2 (M) | FOCOM SMOS Producer validates the request | | -| | If the validation is success, Step 3 and Step 4 are mandatory and use case ends.
If the validation is fail skip step 3 and 4 and step 5 is mandatory and use case ends, | | -| Step 3 (M) | If the validation is successful, FOCOM SMOS Producer retrieves the status information related to the provisioningRequest or optionally fetch the latest status information of the provisioningRequest from the IMS as defined in O-RAN.WG6.TS.O2IMS-INTERFACE , clause 3.4.6.2.4 [i.9]. | | -| Step 4 (M) | FOCOM SMOS Producer responds with status information | | -| Step 5 (M) | If the validation fail, FOCOM SMOS Producer responds with information about the failure | | -| Ends when | FOCOM SMOS Consumer receives the status information of provisioningRequest or information about the failure | | -| Exceptions | Validation Fail – This exception occurs when the validation of the request fails | | - -| | | | -|-----------------|-----------------|--| -| Post Conditions | N/A | | -| Traceability | REQ-FOCOM-FUN10 | | - -#### 4.2.10.3 UML Sequence Diagram - -![UML Sequence diagram for O-Cloud provisioningRequest status query. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer, IMS. The diagram shows a query request from Consumer to Producer, followed by internal validation and status retrieval by the Producer, and a final response back to the Consumer. An optional interaction with IMS is also shown.](04cfca33e3fc26513abe649d7474f733_img.jpg) - -``` - -sequenceDiagram - participant Consumer as FOCOM SMOS Consumer - participant Producer as FOCOM SMOS Producer - participant IMS as IMS - - Note right of Producer: PRECONDITION: -FOCOM SMOS Producer has created provisioningRequestId -FOCOM SMOS Consumer is authorized - - Note over Consumer, Producer: O-Cloud provisioningRequest status query - - Consumer->>Producer: 1 Query provisioningRequest status request (provisioningRequestId) - Producer->>Producer: 2 validates the request - alt validation is successful - Producer->>IMS: 3 retrieves the status information related to provisioningRequestId - Note right of IMS: Optionally, FOCOM SMOS Producer may interact with IMS to fetch the latest provisioningRequest status information as defined in O-RAN.WG6.02IMS-INTERFACE [i.9], clause 3.4.6.2.4. - Producer-->>Consumer: 4 Query provisioningRequest status response (info regarding provisioningRequestId) - else validation fail - Producer-->>Consumer: 5 Validation fail (info of the failure) - end - - Note over Consumer, Producer: End O-Cloud provisioningRequest status query use case - -``` - -UML Sequence diagram for O-Cloud provisioningRequest status query. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer, IMS. The diagram shows a query request from Consumer to Producer, followed by internal validation and status retrieval by the Producer, and a final response back to the Consumer. An optional interaction with IMS is also shown. - -Figure 4.2.10.3-1: O-Cloud provisioningRequest status query - -### 4.2.11 Support Fetching of PM Data through one-time/ad-hoc data requests - -#### 4.2.11.1 High level Description - -The use case describes how an authenticated & authorized DME Service Consumer can obtain PM data (without subscription) that it needs to consume, using DME mechanism & FOCOM SMOS NBIs. - -Before triggering the one-time/ad-hoc data requests, it's considered that using DME mechanism, DME Service Consumer have discovered (& is aware of) the available PM DME datatypes. - -#### 4.2.11.2 Sequence Description - -**Table 4.2.11.2-11 Fetching PM Data for one-time/ad-hoc data requests** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | The DME Service Consumer obtains the data they intend to consume through one-time/ad-hoc data requests | | -| Actors and Roles |
  • - FOCOM SMOS: In the role of "FOCOM Service Producer"
  • - DME SMOS: In the role of "DME Service Producer" & "FOCOM Service Consumer"
  • - DME Service Consumer: An Authorized end Consumer of Performance data e.g. rApp
  • - O-Cloud IMS: To execute the request received from FOCOM SMOS
| | -| Assumptions |

This use-case focuses on data requests for PM metrics which are dependent/mapped to PM jobs. Additionally, this covers Positive/Success Scenarios only.

PM jobs already exist during Registration step (& are kept in Suspended state unless datatype is Subscribed by any DME Service Consumer)

Once data is collected for one-time/adhoc request, job state is changed back to "Suspended"

| | -| Preconditions |

The DME Services Consumer is authenticated/authorized to access & use the DME Services.

The DME Services Consumer has obtained registered PM datatype information e.g. by discovery.

The FOCOM SMOS Consumer is authenticated/authorized to access & use the FOCOM SMOS.

| | -| Begins when | The DME Service Consumer initiates the request data procedure. | | -| Step 1 (M) | The DME Service Consumer sends to the Data management and exposure functions a request data request to obtain data for consumption, providing its Consumer identifier and data instance information. | | -| Step 2 (M) | The DME Service Producer receives the request & validates request i.e.PM datatype/dataset correctness & if requested data is already available or not. | | -| Alternative Procedure (ALT1) | If Requested data is already available (due to any preexisting subscription by some other DME Service Consumer). | | -| Step 3 (ALT1) | The DME Service Producer Retrieves Pull delivery details of data from repository | | -| Alternative Procedure (ALT2) | If Requested data is NOT available/collected previously (since datatype is not subscribed by any DME Service Consumer yet). | | -| Step 4 (ALT2) | The DME SMOS (as FOCOM SMOS Consumer) triggers PM Data Collection request towards FOCOM SMOS. | | -| Step 5 (ALT2) | The FOCOM SMOS identifies the mapped PM Jobs for requested datatype | | -| Step 6 (ALT2) | The FOCOM SMOS Interfaces with respective O2 IMSes & Triggers (resumes) needed mapped PM Jobs | | -| Step 7 (ALT2) | The FOCOM SMOS Interfaces with respective O2 IMSes to Collect & Uses <> service procedures for collecting requested PM Data. | | -| Step 8 (ALT2) | Once PM data transfer to repository is acknowledged by FOCOM SMOS FOCOM SMOS responds back to DME SMOS (FOCOM Consumer) for PM data collection request with Pull delivery Details | | -| Step 9 (ALT2) | The DME Service Producer Retrieves Pull delivery details of data from repository | | -| Step 10 (M) | DME producer responds to DME Service Consumer with Pull delivery details of requested PM data | | -| Step 11 (M) | DME Service Consumer triggers Pull PM data request (Using Pull delivery details) | | -| Step 12 (M) | DME Producer responds to DME Service Consumer with Pull PM data response (PM data included in the payload.) | | -| Ends when | The requested data have been delivered to the DME Service Consumer for consumption. | | - -| | | | -|-----------------|-----------------------------------------------------------|--| -| Exceptions | n/a | | -| Post Conditions | The DME Service Consumer has consumed the requested data. | | -| Traceability | REQ-FOCOM-FUN15 | | - -#### 4.2.11.3 UML Sequence Diagram - -![UML Sequence Diagram for Fetching PM Data for one-time/ad-hoc data requests. Lifelines: DME Service Consumer, DME Service Producer, FOCOM Service Consumer, FOCOM Service Producer, IMS (O-Cloud(s) IMS(s)). The diagram shows the interaction for pulling PM data, including validation, repository checks, and data collection from IMS if necessary.](f5deee2f3301ee351c4008283ffafbb3_img.jpg) - -``` - -sequenceDiagram - participant DME Service Consumer - participant DME Service Producer - participant FOCOM Service Consumer - participant FOCOM Service Producer - participant IMS as O-Cloud(s) IMS(s) - - Note right of DME Service Consumer: PRECONDITION: -The DME SERVICES Consumer is authenticated/authorized to access & use the DME Services. -The FOCOM SMOS Consumer is authenticated/authorized to access & use the FOCOM SMOS. -The DME SERVICES Consumer have discovered DME data types(PM related)information. - - DME Service Consumer->>DME Service Producer: 1 PM data request (ConsumerId,PM data Instance information) - DME Service Producer-->>DME Service Consumer: 2 Validate the DME Service Consumer's PM data request (mapped to valid Registered DME datatype.) - - alt If Requested data is already available (due to any preexisting subscription by some other DME Service Consumer). - DME Service Producer-->>DME Service Consumer: 3 Retrieves Pull delivery details of data from repository - else If Requested data is NOT available/collected previously (since datatype is not subscribed by any DME Service Consumer yet!). - FOCOM Service Consumer->>FOCOM Service Producer: 4 Collect PM data request - FOCOM Service Producer-->>FOCOM Service Consumer: 5 By using the mapping table maintained during datatype registration, FOCOM Identifies the mapped PM Jobs with datatype. - FOCOM Service Consumer-->>IMS: 6 Interface with respective O2 IMSs & Triggers(resumes) necessary PM Jobs - IMS-->>FOCOM Service Consumer: 7 Uses <> service procedures for collecting requested PM Data. Collected data Placed in Repository. - FOCOM Service Consumer-->>FOCOM Service Producer: 8 (Once PM data transfer to repository is acknowledged by FOCOM SMOS) Collect PM data response (pull delivery details) - FOCOM Service Producer-->>DME Service Consumer: 9 Retrieves Pull delivery details of data from repository - end - - DME Service Consumer-->>DME Service Producer: 10 PM data response (Pull delivery details of requested PM data) - DME Service Consumer->>DME Service Producer: 11 Pull PM data request (Using Pull delivery details) - DME Service Producer-->>DME Service Consumer: 12 Pull PM data response (PM data included in the payload) - -``` - -UML Sequence Diagram for Fetching PM Data for one-time/ad-hoc data requests. Lifelines: DME Service Consumer, DME Service Producer, FOCOM Service Consumer, FOCOM Service Producer, IMS (O-Cloud(s) IMS(s)). The diagram shows the interaction for pulling PM data, including validation, repository checks, and data collection from IMS if necessary. - -Figure 4.2.11.3-1: Fetching PM Data for one-time/ad-hoc data requests - -### 4.2.12 O-Cloud Platform Software Update Use Case - -#### 4.2.12.1 High level description - -This use case enables an authorized FOCOM SMOS Consumer to trigger an O-Cloud Platform Software Update (upgrades and downgrades) by interacting with a FOCOM SMOS Producer within the Service Management and Orchestration Framework. - -#### 4.2.12.2 Sequence Description - -**Table 4.2.12.2-12: O-Cloud Platform Software Update** - -| Use Case Stage | Evolution / Specification | >>Uses<< | -|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| -| Goal | To enable the FOCOM SMOS Consumer to trigger an O-Cloud Platform Software update (upgrades and downgrades) by initiating the request and receiving acknowledgment through the FOCOM SMOS Producer. | | -| Actors and Roles | FOCOM SMOS Consumer: An authorized FOCOM SMOS Consumer that requests O-Cloud platform software updates via FOCOM SMOS Producer.
FOCOM SMOS Producer: Validates and acknowledges the update request and initiates the update with the O2 IMS for O-Cloud Platform Software update | | -| Assumptions | FOCOM SMOS Consumer is authorized to initiate O-Cloud Platform Software update (upgrades and downgrades)
FOCOM SMOS Consumer has necessary information to trigger request for O-Cloud Platform Software update. | | -| Preconditions | O-Cloud Operational – O-Cloud is operational and has registered with the SMO.
Privilege – The FOCOM SMOS Consumer is authorized. | | -| Begins when | The FOCOM SMOS Consumer sends a request to FOCOM SMOS Producer for a specific O-Cloud Platform Software update. | | -| Step 1 (M) | The FOCOM SMOS Consumer sends a request to initiate a specific O-Cloud Platform Software update. The request may include details such as the O-Cloud ID, the scope of the update (a single O-Cloud node, an O-Cloud node cluster, or the entire O-Cloud), and the desired software version. | | -| Step 2 (M) | FOCOM SMOS Producer validates the received O-Cloud Platform software update request. | | -| Alternative Procedure: Upon receiving a specific O-Cloud Platform Software update request from the FOCOM SMOS Consumer, the FOCOM SMOS Producer validates the request and, if successful, sends an acknowledgment response, and initiate request over O2 IMS to trigger Specific O-Cloud Platform Software update. | | | -| Step 3.1 (ALT) | If the request is verified, FOCOM SMOS Producer response to Acknowledge O-Cloud platform software update request with Acknowledgement ID. | | -| Step 3.2 (ALT) | If validation fails, FOCOM SMOS Producer informs the FOCOM SMOS Consumer about the failure and provides failure details. | | -| Alternative Procedure: if verification succeed, FOCOM SMOS Producer start to interact with O2 IMS
Ref Use case: 3.1.6 of ORAN.WG6.ORCH-USE-CASES [i.2] | | | -| Step 4 (ALT) | FOCOM SMOS Producer Notify to the FOCOM SMOS Consumer about the outcome of O-Cloud Platform software update request once it received the outcome over O2 IMS. | | -| Ends when | The FOCOM SMOS Consumer receives the outcome of the O-Cloud Platform Software update request. | | -| Exceptions | None | | -| Post-conditions | The O-Cloud Platform Software is successfully updated, and a confirmation/notification is provided to the FOCOM SMOS Consumer. | | - -| | | | -|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| | In case O-Cloud Platform Software is not successfully updated, the software update has been rolledback as per the FOCOM-IMS procedure (see referenced clause 3.1.6 of ORAN.WG6.ORCH-USE-CASES [i.2]). | | -| Traceability | [REQ-FOCOM-Platform SW Update-FUN19], [REQ-FOCOM-Platform SW Update-FUN20], [REQ-FOCOM-Platform SW Update-FUN21], [REQ-FOCOM-Platform SW Update-FUN22] | | - -#### 4.2.12.3 UML Sequence Diagram - -![UML Sequence Diagram for O-Cloud Platform Software Update. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer, IMS. The diagram shows a request for a software update, validation, and subsequent interaction with the IMS.](838c31609fac483fa2c01c7896a2fd6d_img.jpg) - -``` - -sequenceDiagram - participant FOCOM SMOS Consumer - participant FOCOM SMOS Producer - participant IMS - - Note right of FOCOM SMOS Consumer: PRECONDITION: -FOCOM SMOS Consumer is authorized to initiate O-Cloud Platform Software update (upgrades and downgrades) -FOCOM SMOS Consumer has necessary information to trigger request for O-Cloud Platform Software update. - - Note over FOCOM SMOS Consumer, FOCOM SMOS Producer: O-Cloud Platform Software Update - - FOCOM SMOS Consumer->>FOCOM SMOS Producer: 1 Request to initiate a specific O-Cloud Platform Software Update (upgrades and downgrades) (O-Cloud Id, Update Scope, Software Version) - FOCOM SMOS Producer->>FOCOM SMOS Consumer: 2 Validate the request - - alt validation succeed: 3.1 Acknowledges specific O-Cloud Platform Software Update Request - alt Validation failed: 3.2 Verification fail (info of the request validation failure) - - alt If validation succeed FOCOM SMOS start interaction with O2 IMS: ref FOCOM SMOS initiate request to IMS for a specific O-Cloud Platform Software Update (upgrades and downgrades). see the Use Case in ORAN.WG6.ORCH-USE-CASES, clause 3.1.6 [i.2]. Note : Enhancement discussions for Use Case 3.1.6 are currently in progress with WG6's O2 IMS Provisioning workstream - FOCOM SMOS Producer->>FOCOM SMOS Consumer: 4 Notification about the outcome of the specific O-Cloud IMS Software Update request. - end - - Note right of FOCOM SMOS Consumer: FOCOM NBI can provide other capabilities e.g. update a O-Cloud Platform software update request by creating a new revision, restoring to previous revision or a update in configuration,which will be describe in other use cases related to Software Update. - - Note over FOCOM SMOS Consumer, FOCOM SMOS Producer: O-Cloud Platform Software Update - -``` - -UML Sequence Diagram for O-Cloud Platform Software Update. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer, IMS. The diagram shows a request for a software update, validation, and subsequent interaction with the IMS. - -Figure 4.2.12.3-1: O-Cloud Platform Software Update - -### 4.2.13 Fetching of alarms based on Alarm query criteria - -#### 4.2.13.1 High level Description - -The use case describes how FOCOM Service Consumer can query for specific kinds of alarms or groups of alarms based on the alarm query criteria. - -E.g.: Using FOCOM SMOS NBIs, FOCOM Service consumer can request to FOCOM SMOS to retrieve “alarm status” for all the O-Cloud resources by issuing alarm query with a criteria of “all O-Cloud resources” and “all alarms” (on those resources). - -#### 4.2.13.2 Sequence Description - -Table 4.2.13.2-13 Fetching of alarms based on Alarm query criteria - -| Use Case Stage | Evolution / Specification | <> Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| Goal | Using FOCOM NBIs, the FOCOM Service Consumer queries & obtains the O-Cloud resource alarm data they intend to consume. | | -| Actors and Roles |
  • - FOCOM SMOS: In the role of “FOCOM Service Producer”
  • - FOCOM Service Consumer: An Authorized end Consumer of Alarm data e.g. rApp
  • - O-Cloud IMS: To execute the request received from FOCOM SMOS
| | -| Assumptions | This use-case focuses on Positive/Success Scenarios only. | | -| Preconditions |
  • • The FOCOM Service Consumer is authenticated/authorized to access & use the FOCOM SMOS.
  • • AlarmDictionaries are registered as discoverable DME datatype.
  • • By discovering/fetching necessary AlarmDictionaries, FOCOM Service Consumers have required info about "O-Cloud resources\Alarm conditions" to configure appropriate alarm queries.
| | -| Begins when | This use case begins when the FOCOM Service Consumer initiates an Alarm Query based on alarm query criteria. | | -| Step 1 (M) | An alarm query is initiated from the FOCOM Service Consumer towards FOCOM SMOS along with alarm query criteria that specifies what type of alarms the FOCOM Service Consumer is interested in. Alarm query criteria includes Alarm characteristics like O-Cloud resource Identifiers/severities etc | | -| Step 2 (M) | Using that Alarm query criteria FOCOM SMOS further interacts with respective O-Cloud O2IMS & fetches query response from O2IMS (based on Alarm List content) [O-RAN.WG6.ORCH-USE-CASES [i.2], clause 3.7.3 shall apply] | | -| Step 3 (M) | FOCOM SMOS shares the Alarms Query response (alarm content matching the alarm query criteria) back to FOCOM Service Consumer | | -| Ends when | The requested alarm query response has been delivered to the FOCOM Service Consumer. | | -| Exceptions | n/a | | -| Post Conditions | The FOCOM Service Consumer has consumed the requested data. | | -| Traceability | REQ-FOCOM-FUN23 | | - -#### 4.2.13.3 UML Sequence Diagram - -![UML Sequence Diagram for Fetching of alarms based on Alarm query criteria. Lifelines: FOCOM Service Consumer, FOCOM SMOS Producer, O-Cloud Platform (IMS). The diagram shows the interaction flow with a precondition block and a 'Fetching of alarms based on Alarm query criteria' message block.](030c758fd425016b03290c8f11bef69d_img.jpg) - -``` - -sequenceDiagram - participant FSC as FOCOM Service Consumer - participant FSP as FOCOM SMOS Producer - participant IMS as O-Cloud Platform (IMS) - - Note right of FSC: PRECONDITION: -The FOCOM Service Consumer is authenticated/authorized to access & use the FOCOM SMOS. -AlarmDictionaries are registered as discoverable DME datatype. -By discovering/fetching necessary AlarmDictionaries, FOCOM Service Consumers have needed info about "O-cloud resources\Alarm conditions" to configure appropriate alarm queries. - - Note right of FSC: Fetching of alarms based on Alarm query criteria - FSC->>FSP: Alarms Query request based on alarm query criteria (Alarm characteristics like O-Cloud resource Identifiers/severities etc) - FSP->>IMS: Interacts with respective O-Cloud o2IMS & fetch query response from O2IMS (based on Alarm List content) [O-RAN.WG6.ORCH-USE-CASES [i.2], clause 3.7.3 shall apply] - IMS-->>FSP: - FSP-->>FSC: Alarms Query response (alarm content matching the alarm query criteria) - -``` - -UML Sequence Diagram for Fetching of alarms based on Alarm query criteria. Lifelines: FOCOM Service Consumer, FOCOM SMOS Producer, O-Cloud Platform (IMS). The diagram shows the interaction flow with a precondition block and a 'Fetching of alarms based on Alarm query criteria' message block. - -Figure 4.2.13.3-1: Fetching of alarms based on Alarm query criteria - -### 4.2.14 Subscribing for Alarm Event notifications based on alarm subscription/notification filter criteria - -#### 4.2.14.1 High level Description - -The use case describes how FOCOM Service consumers request for subscription of Alarm Event notifications based on alarm subscription/notification filter criteria. - -#### 4.2.14.2 Sequence Description - -**Table 4.2.14.2-14 Subscribing for Alarm Event notifications based on alarm subscription/notification filter criteria** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Using FOCOM NBIs, the FOCOM Service Consumer can issue subscription request to receive alarm event notifications. | | -| Actors and Roles |
  • - FOCOM SMOS: In the role of “FOCOM Service Producer”
  • - FOCOM Service Consumer: An Authorized end Consumer of Alarm data e.g. rApp
  • - O-Cloud IMS: To execute the request received from FOCOM SMOS
| | -| Assumptions | This use-case focuses on Positive/Success Scenarios only. | | -| Preconditions |
  • • The FOCOM Service Consumer is authenticated/authorized to access & use the FOCOM SMOS.
  • • AlarmDictionaries are registered as discoverable DME datatype.
  • • By discovering/fetching necessary AlarmDictionaries, FOCOM Service Consumers have needed info about "O-Cloud resources\Alarm conditions" etc to configure needed subscription filter criteria's.
| | -| Begins when | This use case begins when the FOCOM Service Consumer initiates an Alarm subscription request based on subscription/notification filter criteria. | | -| Step 1 (M) | An alarm subscription request is initiated by FOCOM Service Consumer towards FOCOM SMOS along with alarm notification filter criteria & its FOCOM Service consumer subscription identifier. Alarm subscription/notification criteria may include info like Alarm characteristics like O-Cloud resource Identifiers/severities etc. | | -| Step 2 (M) | FOCOM SMOS maintain the mapping data of FOCOM Service consumer subscription identifier & their requested subscription filter criteria's | | -| Step 3 (M) | Using that Alarm subscription/notification criteria & FOCOM SMOS Identifier, FOCOM SMOS further interacts with respective O-Cloud O2IMS for configuration of needed subscription [O-RAN.WG6.ORCH-USE-CASES [i.2], clause 3.7.1 shall apply] | | -| Step 4 (M) | FOCOM SMOS shares the response to alarm subscription request completion to FOCOM Service Consumer. | | -| Step 5 (M) | If the alarm/alarmlist updates (when occurred) is not filtered by the subscription criteria, corresponding alarm notification is shared to SMO [O-RAN.WG6.ORCH-USE-CASES [i.2], clause 3.7.2 shall apply] | | -| Step 6 (M) | FOCOM SMOS, performs the additional tasks like needed Alarm correlation (if any) and forwards the needed Alarm notifications events to the respective FOCOM Service Consumer according to the mapped “FOCOM Service consumer subscription identifier” | | -| Ends when | The requested/subscribed alarm notifications have been delivered to the FOCOM Service Consumer. | | -| Exceptions | n/a | | -| Post Conditions | The FOCOM Service Consumer receives the relevant/subscribed alarm notification events | | -| Traceability | REQ-FOCOM-FUN24 | | - -#### 4.2.14.3 UML Sequence Diagram - -![UML Sequence Diagram for Figure 4.2.14.3-1: Subscribing for Alarm Event notifications based on alarm subscription/notification filter criteria. The diagram shows interactions between FOCOM Service Consumer, FOCOM SMOS Producer, and O-Cloud Platform (IMS).](8e80de0cac529b2c3775d677c5203133_img.jpg) - -The sequence diagram illustrates the interaction for subscribing to alarm notifications. It begins with a PRECONDITION block: "The FOCOM Service Consumer is authenticated/authorized to access & use the FOCOM SMOS. AlarmDictionaries are registered as discoverable DME datatype. By discovering/fetching needed AlarmDictionaries, FOCOM Service Consumers have needed info about "O-cloud resources\Alarm conditions" etc to configure needed filter criteria." - -The main sequence is titled "Subscription for Alarm Event notifications/n (Based on alarm subscription/notification filter criteria)". The interaction steps are: - - -- The FOCOM Service Consumer sends an "Alarms Subscription request based on alarm notification filter criteria (Alarm characteristics like O-Cloud resource identifiers/severities etc)" to the FOCOM SMOS Producer. -- The FOCOM SMOS Producer responds with "Alarms Subscription response/n(Success)". -- Inside the FOCOM SMOS Producer lifeline, there are internal actions: "Maintain mapping data of FOCOM Service consumer subscription identifier & filter criteria's", "Interacts with respective O-Cloud oIMS & configures needed subscription from SMO to IMS [O-RAN.WG6.ORCH-USE-CASES [i.2], clause 3.7.1 shall apply]", "If the alarm/alarmist updates is not filtered by the subscription criteria, alarm notification is shared to SMO [O-RAN.WG6.ORCH-USE-CASES [i.2], clause 3.7.2 shall apply]", and "Performs the additional tasks like needed Alarm correlation (if any)". -- Finally, the FOCOM SMOS Producer sends an "Alarm notification accordingly pushed to End consumer" to the FOCOM Service Consumer. - -UML Sequence Diagram for Figure 4.2.14.3-1: Subscribing for Alarm Event notifications based on alarm subscription/notification filter criteria. The diagram shows interactions between FOCOM Service Consumer, FOCOM SMOS Producer, and O-Cloud Platform (IMS). - -**Figure 4.2.14.3-1: Subscribing for Alarm Event notifications based on alarm subscription/notification filter criteria** - -### 4.2.15 Fetching available O-Cloud Logs based on filter criteria - -#### 4.2.15.1 High level Description - -The use case describes how FOCOM SMOS consumers uses FOCOM NBIs for fetching available O-Cloud Logs based on filter criteria. - -#### 4.2.15.2 Sequence Description - -**Table 4.2.15.2-15 Fetching available O-Cloud Logs based on filter criteria** - -| Use Case Stage | Evolution / Specification | <>
Related use | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------| -| Goal | Using FOCOM NBIs, the FOCOM SMOS Consumer can issue requests for fetching available O-Cloud Logs based on filter criteria. | | -| Actors and Roles |
  • FOCOM SMOS: In the role of "FOCOM Service Producer"
  • FOCOM SMOS Consumer: An Authorized end Consumer of O-Cloud logs e.g. rApp
  • O-Cloud Platform (IMS): To execute the request received from FOCOM SMOS
| | -| Assumptions |
  • This use-case focuses on Positive/Success Scenarios only.
| | -| Preconditions |
  • The FOCOM SMOS Consumer is authenticated/authorized to access & use the FOCOM SMOS.
  • Available Logs list is registered as discoverable DME datatype.
  • By discovering available Logs list, FOCOM SMOS Consumers have needed info about valid values for types of logs for configuring appropriate filters about the logs the consumer is interested in.
| | -| Begins when | This use case begins when the FOCOM SMOS Consumer wishes to get a log. | | -| Step 1 (M) | A Log fetch request is initiated by FOCOM SMOS Consumer towards FOCOM SMOS along with appropriate filter criteria. Filters indicate the logs the FOCOM SMOS consumer is interested in. For example, these filters may include the date (ranges), types of logs, types of events, log level (severity), and device(s)/resource(s) or types of resources | | -| Step 2 (M) | Using that Filter inputs, FOCOM SMOS further interacts with respective O-Cloud IMS for processing Log fetch request (e.g. returning Log files/Log files repository endpoints responses that match the request filter). [O-RAN.WG6.ORCH-USE-CASES [i.2], clause 3.7.8 shall apply] | | - -| | | | -|-----------------|--------------------------------------------------------------------------------------------------------|--| -| Step 3 (M) | FOCOM SMOS Producer shares the Log fetch response of O-Cloud Log fetch request to FOCOM SMOS Consumer. | | -| Ends when | The requested O-Cloud Logs has been delivered to the FOCOM SMOS Consumer. | | -| Exceptions | n/a | | -| Post Conditions | The FOCOM SMOS Consumer receives the relevant O-Cloud Logs | | -| Traceability | REQ-FOCOM-FUN25 | | - -#### 4.2.15.3 UML Sequence Diagram - -![UML Sequence Diagram for Fetching available O-Cloud Logs based on filter criteria. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer (within Service Management & orchestration Framework), and O-Cloud Platform (IMS). The sequence starts with a Log Fetch request from Consumer to Producer, which then interacts with IMS. IMS returns a response to Producer, which then forwards it to Consumer. A precondition note states that the Consumer is authenticated and has discovered the FOCOM SMOS. A note on the interaction with IMS mentions O-RAN.WG6.ORCH-USE-CASES [1.2], clause 3.7.8.](a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg) - -UML Sequence Diagram for Fetching available O-Cloud Logs based on filter criteria. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer (within Service Management & orchestration Framework), and O-Cloud Platform (IMS). The sequence starts with a Log Fetch request from Consumer to Producer, which then interacts with IMS. IMS returns a response to Producer, which then forwards it to Consumer. A precondition note states that the Consumer is authenticated and has discovered the FOCOM SMOS. A note on the interaction with IMS mentions O-RAN.WG6.ORCH-USE-CASES [1.2], clause 3.7.8. - -Figure 4.2.15.3-1: Fetching available O-Cloud Logs based on filter criteria - -### 4.2.16 IMS Software Update Use Case - -#### 4.2.16.1 High level description - -This use case enables an authorized FOCOM SMOS Consumer to trigger an IMS Software Update (upgrades and downgrades) by interacting with a FOCOM SMOS Producer within the Service Management and Orchestration Framework. - -#### 4.2.16.2 Sequence Description - -Table 4.2.16.2-16: O-Cloud IMS Software Update - -| Use Case Stage | Evolution / Specification | >>Uses>> | -|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| -| Goal | To enable the FOCOM SMOS Consumer to trigger an IMS Software update (upgrades and downgrades) by initiating the request and receiving acknowledgment through the FOCOM SMOS Producer. | | -| Actors and Roles | FOCOM SMOS Consumer: An authorized FOCOM SMOS Consumer that requests IMS Software updates via FOCOM SMOS Producer.
FOCOM SMOS Producer: Validates and acknowledges the update request and initiates the update over the O2ims for IMS Software update | | -| Assumptions | FOCOM SMOS Consumer is authorized to initiate IMS Software Update procedure (upgrades and downgrades).
FOCOM SMOS Consumer has required necessary information to trigger request for IMS Software Update procedure.
O-Cloud having the IMS software version requested by the FOCOM SMOS Consumer for the Update procedure (upgrades and downgrades). | | - -| | | | -|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Preconditions | O-Cloud Operational – O-Cloud is operational and has registered with the SMO.
Privilege – The FOCOM SMOS Consumer is authorized. | | -| Begins when | The FOCOM SMOS Consumer sends a request to FOCOM SMOS Producer for a specific IMS Software update at Specific O-Cloud. | | -| Step 1 (M) | The FOCOM SMOS Consumer sends a request to initiate IMS Software update to specific O-Cloud. The request may include details such as the O-Cloud ID, and the desired IMS Software version. | | -| Step 2 (M) | FOCOM SMOS Producer validates the received IMS Software update request. | | -| Alternative Procedure: Upon receiving a specific IMS Software update request from the FOCOM SMOS Consumer, the FOCOM SMOS Producer validates the request and, if successful, sends an acknowledgment response, and initiate request over O2ims to trigger Specific IMS Software update at Specific O-Cloud. | | | -| Step 3.1 (ALT) | If the request is verified, FOCOM SMOS Producer informs the FOCOM SMOS Consumer the processing of the IMS software update request providing information to identify the IMS SW update process. | | -| Step 3.2 (ALT) | If validation fail, FOCOM SMOS Producer informs the FOCOM SMOS Consumer about the failure and provides failure details. | | -| Alternative Procedure: If verification succeed, FOCOM SMOS Producer start to interact with O2 IMS
Ref Use case: 3.1.9 of Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN [i.2] | | | -| Step 4 (ALT) | FOCOM SMOS Producer Notify to the FOCOM SMOS Consumer about the outcome of IMS Software update request once it received the outcome over O2 IMS. | | -| Ends when | The FOCOM SMOS Consumer receives the outcome of the IMS Software update request. | | -| Exceptions | None | | -| Post-conditions | The IMS Software is successfully updated, and a confirmation/notification is provided to the FOCOM SMOS Consumer.
In case IMS Software is not successfully updated, the software update has been rollbacked as per the FOCOM-IMS procedure (see referenced clause 3.1.9 of Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN [i.2]). | | -| Traceability | [REQ-FOCOM-IMS Update-FUN26], [REQ-FOCOM-IMS Update-FUN27],
[REQ-FOCOM-IMS Update-FUN28], [REQ-FOCOM-IMS SW Update-FUN29] | | - -#### 4.2.16.3 UML Sequence Diagram - -![UML Sequence Diagram for IMS Software Update. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer (within Service Management & Orchestration Framework), and IMS. The sequence starts with a request from the Consumer to the Producer, followed by validation, an acknowledgment or failure, and a notification after an interaction with O2 IMS. A note indicates that FOCOM can provide other capabilities like updating or restoring software revisions.](a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg) - -``` - -sequenceDiagram - participant Consumer as FOCOM SMOS Consumer - participant Producer as FOCOM SMOS Producer - participant IMS as IMS - - Note right of Consumer: PRECONDITION: -FOCOM SMOS Consumer is authorized to initiate IMS Software update (upgrades and downgrades). -FOCOM SMOS Consumer has necessary information to trigger request for IMS Software update - - Note over Producer: IMS Software Update - - Consumer->>Producer: 1 Request to initiate a specific IMS Software Update (upgrades and downgrades) (O-Cloud ID, IMS Software Information) - Producer->>Producer: 2 Validate the request - alt validation succeed: 3.1 Acknowledges specific IMS Software Update Request - else Validation failed: 3.2 Verification fail (info of the request validation failure) - alt If validation succeed FOCOM SMOS start Interaction with O2 IMS: ref FOCOM SMOS initiate request to O2 IMS for a specific IMS Software Update. Use case 3.1.9 of Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN [i.2] Note: We are planning to have enhancement discussions for Use Case 3.1.9 with WG6's O2 IMS Provisioning workstream - Producer->>Consumer: 4 Notification about the outcome of the specific O-Cloud IMS Software Update request - - Note right of Consumer: FOCOM can provide other capabilities e.g. Update a IMS software update request by creating a new revision, restoring to previous revision or a update it configuration, which will be described in other use cases related to Software Update. - - Note over Producer: IMS Software Update - -``` - -UML Sequence Diagram for IMS Software Update. Lifelines: FOCOM SMOS Consumer, FOCOM SMOS Producer (within Service Management & Orchestration Framework), and IMS. The sequence starts with a request from the Consumer to the Producer, followed by validation, an acknowledgment or failure, and a notification after an interaction with O2 IMS. A note indicates that FOCOM can provide other capabilities like updating or restoring software revisions. - -Figure 4.2.16.3-1: IMS Software Update - -### 4.2.17 DMS Software Update Use Case - -#### 4.2.17.1 High level description - -This use case enables an authorized FOCOM SMOS Consumer to trigger an DMS Software Update (upgrades and downgrades) by interacting with a FOCOM SMOS Producer within the Service Management and Orchestration Framework. - -#### 4.2.17.2 Sequence Description - -Table 4.2.17.2-17: O-Cloud DMS Software Update - -| Use Case Stage | Evolution / Specification | >>Uses<< | -|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| -| Goal | To enable the FOCOM SMOS Consumer to trigger an DMS Software update (upgrades and downgrades) by initiating the request and receiving acknowledgment through the FOCOM SMOS Producer. | | -| Actors and Roles | FOCOM SMOS Consumer: An authorized FOCOM SMOS Consumer that requests DMS Software update via FOCOM SMOS Producer.

FOCOM SMOS Producer: Validates and acknowledges the update request and initiates the update over the O2ims for DMS Software update. | | - -| | | | -|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| Assumptions |

FOCOM SMOS Consumer is authorized to initiate DMS Software Update procedure (upgrades and downgrades).

FOCOM SMOS Consumer has necessary information to trigger request for DMS Software update.

O-Cloud having the DMS software version requested by the FOCOM SMOS Consumer for the Update procedure (upgrades and downgrades).

| | -| Preconditions |

O-Cloud Operational – O-Cloud is operational and has registered with the SMO.

Privilege – The FOCOM SMOS Consumer is authorized.

| | -| Begins when | The FOCOM SMOS Consumer sends a request to FOCOM SMOS Producer for a specific DMS Software update on Specific O-Cloud. | | -| Step 1 (M) | The FOCOM SMOS Consumer sends a request to initiate DMS Software update to specific O-Cloud. The request may include details such as the O-Cloud ID, and the desired DMS Software version. | | -| Step 2 (M) | FOCOM SMOS Producer validates the received DMS Software update request. | | -| Alternative Procedure: Upon receiving a specific DMS Software update request from the FOCOM SMOS Consumer, the FOCOM SMOS Producer validates the request and, if successful, sends an acknowledgment response, and initiate request over O2ims to trigger Specific DMS Software update at Specific O-Cloud. | | | -| Step 3.1 (ALT) | If the request is verified, FOCOM SMOS Producer informs the FOCOM SMOS Consumer the processing of the DMS software update request providing information to identify the DMS SW update process. | | -| Step 3.2 (ALT) | If validation fail, FOCOM SMOS Producer informs the FOCOM SMOS Consumer about the failure and provides failure details. | | -| Alternative Procedure: If verification succeed, FOCOM SMOS Producer start to interact with O2 IMS
Ref Use case: 3.1.10 of Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN [i.2] | | | -| Step 4 (ALT) | FOCOM SMOS Producer Notify to the FOCOM SMOS Consumer about the outcome of DMS Software update request once it received the outcome over O2 IMS. | | -| Ends when | The FOCOM SMOS Consumer receives the outcome of the DMS Software update request. | | -| Exceptions | None | | -| Post-conditions |

The DMS Software is successfully updated, and a confirmation/notification is provided to the FOCOM SMOS Consumer.

In case DMS Software is not successfully updated, the software update has been rollbacked as per the FOCOM-IMS procedure (see referenced clause 3.1.10 of Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN [i.2]).

| | -| Traceability | [REQ-FOCOM-DMS Update-FUN30], [REQ-FOCOM-DMS Update-FUN31], [REQ-FOCOM-DMS Update-FUN32], [REQ-FOCOM-DMS SW Update-FUN33] | | - -#### 4.2.17.3 UML Sequence Diagram - -![UML Sequence Diagram for DMS Software Update. Lifelines: FOCOM SMOS Consumer, Service Management & Orchestration Framework (FOCOM SMOS Producer), and IMS. The sequence starts with a request from the Consumer to the Producer. The Producer validates the request. An 'alt' block 'validation succeed' leads to acknowledgement (3.1), while 'Validation failed' leads to a verification fail (3.2). Another 'alt' block 'If validation succeed FOCOM SMOS start Interaction with O2 IMS' contains a 'ref' block detailing the interaction with O2 IMS. A note at the bottom mentions other capabilities like updating or restoring revisions.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) - -``` - -sequenceDiagram - participant FOCOM SMOS Consumer - participant Service Management & Orchestration Framework as FOCOM SMOS Producer - participant IMS - - Note right of FOCOM SMOS Consumer: PRECONDITION: -FOCOM SMOS Consumer is authorized to initiate DMS Software update (upgrades and downgrades). -FOCOM SMOS Consumer has necessary information to trigger request for DMS Software update. - - Note over FOCOM SMOS Consumer, Service Management & Orchestration Framework: DMS Software Update - - FOCOM SMOS Consumer->>Service Management & Orchestration Framework: 1 Request to initiate a specific DMS Software Update (upgrades and downgrades) (O-Cloud Id, Software Version) - Service Management & Orchestration Framework-->>Service Management & Orchestration Framework: 2 Validate the request - - alt validation succeed: 3.1 Acknowledges specific DMS Software Update Request - alt Validation failed: 3.2 Verification fail (info of the request validation failure) - - alt If validation succeed FOCOM SMOS start Interaction with O2 IMS: ref FOCOM SMOS initiate request to O2 IMS for a specific DMS Software Update. - Note right of Service Management & Orchestration Framework: Use case 3.1.10 of Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN [i.2] -Note: We are planning to have enhancement discussions for Use Case 3.1.10 with WG6's O2_IMS Provisioning workstream - end - - Service Management & Orchestration Framework-->>FOCOM SMOS Consumer: 4 Notification about the outcome of the specific O-Cloud DMS Software Update request - - Note right of FOCOM SMOS Consumer: FOCOM can provide other capabilities e.g. Update a DMS software update request by creating a new revision, restoring to previous revision or a update it configuration, which will be described in other use cases related to Software Update. - -``` - -UML Sequence Diagram for DMS Software Update. Lifelines: FOCOM SMOS Consumer, Service Management & Orchestration Framework (FOCOM SMOS Producer), and IMS. The sequence starts with a request from the Consumer to the Producer. The Producer validates the request. An 'alt' block 'validation succeed' leads to acknowledgement (3.1), while 'Validation failed' leads to a verification fail (3.2). Another 'alt' block 'If validation succeed FOCOM SMOS start Interaction with O2 IMS' contains a 'ref' block detailing the interaction with O2 IMS. A note at the bottom mentions other capabilities like updating or restoring revisions. - -Figure 4.2.17.3-1: DMS Software Update - -# 5 Potential Requirements on the FOCOM and NFO SMOS services - -## 5.1 Potential Functional and Interface Requirements - -| REQ | Description | Notes | -|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------| -| REQ-FOCOM_SMOS-FUN1 | The FOCOM SMOS should have the capability enabling a FOCOM SMOS Consumer to query O-Cloud objects (like resources, artifacts, etc) and O-Cloud templates identifiers matching each O-Cloud site from a FOCOM SMOS | 4.2.1 (O-Cloud resources related information Query Use Case) | -| REQ-FOCOM_SMOS-FUN2 | The FOCOM SMOS should have the capability to expose information about FOCOM SMOS exposed information about O-Cloud objects (like resources, artifacts, etc.) is exposed as READ ONLY” | 4.2.1 (O-Cloud resources related information Query Use Case) | -| REQ-FOCOM_SMOS-FUN3 | The FOCOM SMOS should have the capability to subscribe to receive notifications when there is an update | 4.2.1 (O-Cloud resources related information Query Use Case) | - -| | | | -|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | to the O-Cloud resources using the O2ims interface | | -| REQ-FOCOM-FUN4 | A FOCOM SMOS Consumer shall be able to query information contained in O-Cloud template exposed to the SMO |

4.2.2 (O-Cloud template information Query use case)

4.2.4 (Create, update and execute existing O-Cloud provisioning request revision using same O-Cloud Template)

4.2.5 (Create, update and execute existing O-Cloud provisioning request revision using new O-Cloud Template)

| -| REQ-FOCOM-FUN5 | The FOCOM SMOS shall have the capability enabling a_FOCOM SMOS Consumer to create, update and execute O-Cloud provisioning request based on O-Cloud Template | 4.2.3 (Create, update and execute O-Cloud provisioning request using O-Cloud Template) | -| REQ-FOCOM-FUN6 | The FOCOM SMOS shall have the capability to handle the provisioning request revisions for instance by using a version control system. |

4.2.3 (Create, update and execute O-Cloud provisioning request using O-Cloud Template)

4.2.4 (Create, update and execute existing O-Cloud provisioning request revision using same O-Cloud Template)

4.2.5 (Create, update and execute existing O-Cloud provisioning request revision using new O-Cloud Template)

| -| REQ-FOCOM-FUN7 | FOCOM SMOS shall have the capability to validate O-Cloud provisioning request |

4.2.3 (Create, update and execute O-Cloud provisioning request using O-Cloud Template)

4.2.4 (Create, update and execute existing O-Cloud provisioning request revision using same O-Cloud Template)

4.2.5 (Create, update and execute existing O-Cloud provisioning request revision using new O-Cloud Template)

| -| REQ-FOCOM-FUN8 | FOCOM SMOS shall have the capability to do a feasibility check on the requested resources from FOCOM SMOS Consumer |

4.2.3 (Create, update and execute O-Cloud provisioning request using O-Cloud Template)

4.2.4 (Create, update and execute existing O-Cloud provisioning request revision using same O-Cloud Template)

4.2.5 (Create, update and execute existing O-Cloud provisioning request revision using new O-Cloud Template)

| -| REQ-FOCOM-FUN9 | The FOCOM SMOS shall have the capability enabling a_FOCOM SMOS Consumer to create, update and execute an existing O-Cloud provisioning request revision using | 4.2.4 (Create, update and execute existing O-Cloud provisioning request revision using same O-Cloud Template) | - -| | | | -|------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | same O-Cloud Template name and O-Cloud Template version. | | -| REQ-FOCOM-FUN10 | The FOCOM SMOS shall have the capability enabling a FOCOM SMOS Consumer to create, update and execute an existing O-Cloud provisioning request revision using new O-Cloud Template version and/or O-Cloud Template name | 4.2.5 (Create, update and execute existing O-Cloud provisioning request revision using new O-Cloud Template) | -| REQ-FOCOM-FUN11 | FOCOM SMOS should be able to support DME datatype registration process by handling tasks related concluding “data type identifier and needed DME type information” required to register as producer against any DME Datatype | 4.2.6 (Registering FOCOM SMOS for performance DME datatypes and associated operations) | -| REQ-FOCOM-FUN12 | The FOCOM SMOS NBI shall support necessary steps related to the creation of subscription of Performance datatype/dataset. | 4.2.7 (Subscribing PM Datatype/Data Set & associated operations (Update/Remove subscriptions)) | -| REQ-FOCOM-FUN13 | The FOCOM SMOS NBI shall support necessary steps related to update of subscription of Performance datatype/dataset. | 4.2.7 (Subscribing PM Datatype/Data Set & associated operations (Update/Remove subscriptions)) | -| REQ-FOCOM-FUN14 | The FOCOM SMOS NBI shall support necessary steps related to termination of subscription of Performance datatype/dataset. | 4.2.7 (Subscribing PM Datatype/Data Set & associated operations (Update/Remove subscriptions)) | -| REQ-FOCOM-FUN15 | The FOCOM SMOS NBI shall receive and respond to PM data requests (ad-hoc or subscribed) from DME SMOS. | 4.2.7 (Subscribing PM Datatype/Data Set & associated operations (Update/Remove subscriptions))
4.2.11 (Support Fetching of PM Data through one-time/ad-hoc data requests) | -| REQ-FOCOM-FUN16 | The FOCOM SMOS shall have the capability enabling a FOCOM SMOS Consumer to delete the O-Cloud Node cluster and/or infrastructure resources | 4.2.8 (Delete O-Cloud provisioningRequest instance) | -| REQ-FOCOM-FUN17 | The FOCOM SMOS shall have the capability enabling a FOCOM SMOS Consumer to restore previously created and accepted provisioning request configuration. | 4.2.9 (Restore or Update O-Cloud provisioning request revision) | -| REQ-FOCOM-FUN18 | The FOCOM SMOS shall have the capability enabling a FOCOM SMOS Consumer to retrieve the status of O-Cloud provisioningRequest | 4.2.10 (O-Cloud provisioningRequest status query) | -| REQ-FOCOM-Platform Software Update-FUN19 | FOCOM SMOS Producer shall have the capability enabling a FOCOM SMOS Consumer to request O-Cloud Platform Software update. | 4.2.12 (O-Cloud Platform Software Update Use Case) | -| REQ-FOCOM-Platform Software Update-FUN20 | FOCOM SMOS Producer shall have the capability to validate the request from FOCOM SMOS Consumer for O-Cloud platform software update. | 4.2.12 (O-Cloud Platform Software Update Use Case) | - -| | | | -|------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------| -| REQ-FOCOM-Platform Software Update-FUN21 | FOCOM SMOS Producer shall have the capability to notify FOCOM SMOS Consumer the result of a O-Cloud software update. | 4.2.12 (O-Cloud Platform Software Update Use Case) | -| REQ-FOCOM-Platform Software Update-FUN22 | FOCOM SMOS Producer shall have the capability to notify FOCOM SMOS Consumer the result from the verification of the O-Cloud platform software update request. | 4.2.12 (O-Cloud Platform Software Update Use Case) | -| REQ-FOCOM-FUN23 | The FOCOM SMOS shall support the capability for an authorized consumer to request and receive Alarms information based on alarm query criteria. | 4.2.13 (Fetching of alarms based on Alarm query criteria) | -| REQ-FOCOM-FUN24 | The FOCOM SMOS shall support Subscribing for Alarm Event notifications based on alarm subscription/notification filter criteria and receiving the subscribed alarm notifications | 4.2.14 (Subscribing for Alarm Event notifications based on alarm subscription/notification filter criteria) | -| REQ-FOCOM-FUN25 | The FOCOM SMOS shall support the capability for an authorized consumer to request and receive available O-Cloud logs based on filter criteria. | 4.2.15 (Fetching available O-Cloud Logs based on filter criteria) | -| REQ-FOCOM-IMS Software Update-FUN26 | The FOCOM SMOS Producer shall have the capability enabling a FOCOM SMOS Consumer to send IMS Software update request. | 4.2.16 (IMS Software Update) | -| REQ-FOCOM-IMS Software Update-FUN27 | FOCOM SMOS Producer shall have the capability to validate the request from FOCOM SMOS Consumer for IMS Software update request. | 4.2.16 (IMS Software Update) | -| REQ-FOCOM-IMS Software Update-FUN28 | FOCOM SMOS Producer shall have the capability to notify FOCOM SMOS Consumer the result of an IMS Software update. | 4.2.16 (IMS Software Update) | -| REQ-FOCOM-IMS Software Update-FUN29 | FOCOM SMOS Producer shall have the capability to notify FOCOM SMOS Consumer the result from the verification of the IMS Software update request. | 4.2.16 (IMS Software Update) | -| [REQ-FOCOM-DMS Software Update-FUN30] | The FOCOM SMOS Producer shall have the capability enabling a FOCOM SMOS Consumer to send DMS Software update request. | 4.2.17 (DMS Software Update) | -| [REQ-FOCOM-DMS Software Update-FUN31] | FOCOM SMOS Producer shall have the capability to validate the request from FOCOM SMOS Consumer for DMS Software update. | 4.2.17 (DMS Software Update) | -| [REQ-FOCOM-DMS Software Update-FUN32] | FOCOM SMOS Producer shall have the capability to notify FOCOM SMOS Consumer the result of an DMS Software update. | 4.2.17 (DMS Software Update) | - -| | | | -|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| -| [REQ-FOCOM-DMS Software Update-FUN33] | FOCOM SMOS Producer shall have the capability to notify FOCOM SMOS Consumer the result from the verification of the DMS Software update request. | 4.2.17 (DMS Software Update) | -|---------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------| - -# 6 Recommendations - -The current version of the present document has documented use cases and potential requirements as provided in section 4 and section 5 and as summarized in table 6-1. The use cases describe potential interactions on the NBI of the FOCOM SMOS regarding: - -- O-Cloud infrastructure and resources provisioning, -- O-Cloud performance data collection and monitoring - -It is recommended to further perform an analysis of the identified use cases and potential requirements, in order to determine the concepts, capabilities and management aspects produced by the FOCOM SMOS to other FOCOM SMOS Consumer. The outcome of this analysis is recommended to be captured and incorporated into the FOCOM SMOS NBI Technical Specifications, while new FOCOM SMOS NBI use cases can be documented as part of existing ORAN.WG6.ORCH-USE-CASES [i.2]. The list of use cases is not completed, and it can be further extended and/or update in future versions of the present document. The analysis is also recommended to consider any new and/or updated use cases that might be documented as part of future versions of the present document. - -**Table 6-1: List of use cases and potential functional requirements** - -| SNo | Use Cases from section 4 | Potential requirements from section 5 | -|-----|-------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------| -| 1 | 4.2.1 O-Cloud resources related information Query Use Case | REQ-FOCOM_SMOS-FUN1
REQ-FOCOM_SMOS-FUN2
REQ-FOCOM_SMOS-FUN3 | -| 2 | 4.2.2 O-Cloud template information Query use case | REQ-FOCOM-FUN4 | -| 3 | 4.2.3 Create, update and execute O-Cloud provisioning request using O-Cloud Template | REQ-FOCOM-FUN5
REQ-FOCOM-FUN6
REQ-FOCOM-FUN7
REQ-FOCOM-FUN8 | -| 4 | 4.2.4 Create, update and execute existing O-Cloud provisioning request revision using same O-Cloud Template | REQ-FOCOM-FUN4
REQ-FOCOM-FUN6
REQ-FOCOM-FUN7
REQ-FOCOM-FUN8
REQ-FOCOM-FUN9 | -| 5 | 4.2.5 Create, update and execute existing O-Cloud provisioning request revision using new O-Cloud Template | REQ-FOCOM-FUN4
REQ-FOCOM-FUN6
REQ-FOCOM-FUN7 | - -| | | | -|----|----------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------| -| | | REQ-FOCOM-FUN8
REQ-FOCOM-FUN10 | -| 6 | 4.2.6 Registering FOCOM SMOS for performance DME datatypes and associated operations | REQ-FOCOM-FUN11 | -| 7 | 4.2.7 Subscribing PM Datatype/Data Set & associated operations (Update/Remove subscriptions) | REQ-FOCOM-FUN12
REQ-FOCOM-FUN13
REQ-FOCOM-FUN14
REQ-FOCOM-FUN15 | -| 8 | 4.2.8 Delete O-Cloud provisioningRequest instance | REQ-FOCOM-FUN16 | -| 9 | 4.2.9 Restore or Update O-Cloud provisioning request revision | REQ-FOCOM-FUN4
REQ-FOCOM-FUN6
REQ-FOCOM-FUN7
REQ-FOCOM-FUN8
REQ-FOCOM-FUN17 | -| 10 | 4.2.10 O-Cloud provisioningRequest status query | REQ-FOCOM-FUN18 | - -# Annex (Informative): Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2025.07.18 | 01.00 | Final version for July 2025 train, incorporating previous versions (00.00.01 to 00.00.08) which includes,
  • • FOCOM SMOS Use Cases, covering:
    • ○ O-Cloud infrastructure and resources provisioning
    • ○ O-Cloud performance data collection and monitoring
    • ○ Software management
  • • Potential requirements introduced for FOCOM SMOS.
  • • Recommendations for further analysis related to the FOCOM SMOS NBI Technical Specification
| -| 2025.11.20 | 01.00.01 | Implemented CRs NEC-0009, NEC-0010, NEC-0011, RMI-0031, RMI-0026 | -| 2025.11.26 | 01.00.02 | Changes made based on review comments | -| 2025.11.28 | 02.00 | Final version 02.00 | \ No newline at end of file diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/030c758fd425016b03290c8f11bef69d_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/030c758fd425016b03290c8f11bef69d_img.jpg deleted file mode 100644 index f4f0b579ba3f392b121af3515d16ad90836e88b8..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/030c758fd425016b03290c8f11bef69d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ff76b28d2f4f102aaa5cd7b3f930c51d928a94c2430332a9edef68ecdc924095 -size 66902 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/04cfca33e3fc26513abe649d7474f733_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/04cfca33e3fc26513abe649d7474f733_img.jpg deleted file mode 100644 index 2b18a80de0d430b6f00d463b391ad5b4f2fdb4a9..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/04cfca33e3fc26513abe649d7474f733_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2375346ba10bf1c0e900bb953702a87bac7f14398756523e98b75aad414bbba2 -size 149563 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/1a827b10290f33d4fec04d0e8ef7a897_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/1a827b10290f33d4fec04d0e8ef7a897_img.jpg deleted file mode 100644 index 4c653d6bb9997914133702ee9f8de893f0436a6d..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/1a827b10290f33d4fec04d0e8ef7a897_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9e87f2ce5c01e58749861cb8c11d3029294751ab178da78f1b643e08b7a7fe7a -size 283832 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/2837ffdadcdb1e5bababa56b564e56ed_img.jpg deleted file mode 100644 index 0848df58eb9a51f8612c377a46dbba3eac5c4f63..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/2837ffdadcdb1e5bababa56b564e56ed_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fef4550bcd32fc49a96c89b37fc86ebd182c604ca03cd44ee6616c4e7ef73f7a -size 261812 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/28d75f39a24203712ee907b32cf0bbe5_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/28d75f39a24203712ee907b32cf0bbe5_img.jpg deleted file mode 100644 index c17e114d4943f5348628c45f0393b86fab58a017..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/28d75f39a24203712ee907b32cf0bbe5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5ac6f5b17cd1ea07458f7a377db7f7acef7cd13537739fcea53d0f6fa44c8299 -size 186814 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg deleted file mode 100644 index 5fffd369c337f716169392393db1fae1d15a0637..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ab7146b91abfb0805b381a576bf368ad980583b1033f8566128f4e45b7fd0155 -size 149439 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index 930b29c592e18e4ee9b7f13de4f79020ff712459..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5f8013eada922e4dd6d610cf1f66e7ef4cde52eba107e33f0825d24ae802b0e6 -size 4550 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index b65c9819ba60bfe19f6cdb95d3075d756b2b6c71..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0cad14f9ac2225f628dcfe49bccbde098fb99facc8adc2cec5e351074d1e3eee -size 4528 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/7a0db9703b68b3d06cdaeefc084c0006_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/7a0db9703b68b3d06cdaeefc084c0006_img.jpg deleted file mode 100644 index b0e54622f015f670a9e9bbf8ee3658214248b7e8..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/7a0db9703b68b3d06cdaeefc084c0006_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b53aa09b487b994db0199cb0597ce4af849100dc6591ec51f1d8541ac3c89065 -size 145529 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/838c31609fac483fa2c01c7896a2fd6d_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/838c31609fac483fa2c01c7896a2fd6d_img.jpg deleted file mode 100644 index d0d44b8c468b1b4abcde51fbcf1047d86d59a706..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/838c31609fac483fa2c01c7896a2fd6d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:14431bfad6c887f90ebf37f24faf21749383f6a43d7b4ea0b6c5c167c6db10f7 -size 162350 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/854df8ad60507803253274673f9062cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 8e175f20de029384f1e89e83f74d5a93814f5fc9..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b5cadb4f72741f4e411d8ddef0af3a5754dd6365f16b3d65d9fe017f8a130605 -size 4516 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/8e80de0cac529b2c3775d677c5203133_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/8e80de0cac529b2c3775d677c5203133_img.jpg deleted file mode 100644 index 07c65f22a353633114169d60c6412d651d176784..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/8e80de0cac529b2c3775d677c5203133_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:039ba5505bdfea5c24d507bad2c4f15b5019b96623f5317e543c9e618b6e2405 -size 70406 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/8fa679f79a1bb1f527cba9f29e784e89_img.jpg deleted file mode 100644 index 0235ed3b140483af1bad85e01a740268307b6626..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/8fa679f79a1bb1f527cba9f29e784e89_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b08868348ecaca5e074e46263dd719dd6341ef0aef478efef410245b1e56cb97 -size 141770 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index b65c9819ba60bfe19f6cdb95d3075d756b2b6c71..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0cad14f9ac2225f628dcfe49bccbde098fb99facc8adc2cec5e351074d1e3eee -size 4528 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg deleted file mode 100644 index a6acb60bfc0876c1c89bdde765abd2809ec6bc10..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/a003ffe7299e0a48bceb7f1e45a4f1a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2a03de3117cea4f0c7f3b9e1dd0d44d6cf992bbe65187e4718507e1a7db29661 -size 149254 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg deleted file mode 100644 index 4ccbc89ed27e07af781e4e0a95096a52cb2dcaa5..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/a161a2bbb4d830e847ccb4f44b7e41a9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:47f1ea8d882842d86f37e934db235c8d3145db6349433cb3195d02249e8976a9 -size 58026 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/a3472689858b068ef469213682965325_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/a3472689858b068ef469213682965325_img.jpg deleted file mode 100644 index 67cd62ae9f7d4578a289c77d9811ecf2e37b9705..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/a3472689858b068ef469213682965325_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2a06b6798d2b43ac55514f52d982ec78885e9886ca0bc57f19b118ab4e45bd04 -size 150684 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg deleted file mode 100644 index eab86d6440ce719d8845d748850a6e0c77919a97..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f4418568a10b568fcae4e03951f5e29d5e310f059e2052f940b3eae988426a24 -size 227809 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/b5335262987c819d7f71ce40f99cb71b_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/b5335262987c819d7f71ce40f99cb71b_img.jpg deleted file mode 100644 index 9bb6b498cfcd429a1a52b7dc442093a06fd20f35..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/b5335262987c819d7f71ce40f99cb71b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0129c9c62ddf583e4dc073958aadbb5636861bfba363d7993b2ada2c540e330c -size 182884 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 0719d9b662dad25c29233ab2163d9df2777a7e0a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:48fc024d6159442c0a0007f6f8b66e2368910d5ddb2250bcf7fc34f695726411 -size 4492 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/d26959f4514c26ca19c3d6f00da85956_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/d26959f4514c26ca19c3d6f00da85956_img.jpg deleted file mode 100644 index 41954db8e3b0e2565540a2aa048fe89bd56a8ece..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/d26959f4514c26ca19c3d6f00da85956_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1521c9df7dd20765b93887535e6eb07fe6892bf7cdf82fc8f8b1d736938f551c -size 141050 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index 25c3de7eea7b3c381ecf3960d79d1fa32d1c5533..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d502c14c70a134234eb71c90497070bd25cc7f1a4365927e8843303ef34d4706 -size 4498 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index eca96f14eff173ab5ead5b4ef80ff5827e92c33d..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a8bb0af2dd788e055159db7a05c0b9285e7d655c861421ac8dc37e4b94c3b343 -size 4454 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index debceee0b47444ead4235bfb842ae0e0f55e9bf1..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4c5ef872d704eef2a7102f968c144e3b22a959003dd192ef5acd1c286aa4815e -size 4561 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index b65c9819ba60bfe19f6cdb95d3075d756b2b6c71..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0cad14f9ac2225f628dcfe49bccbde098fb99facc8adc2cec5e351074d1e3eee -size 4528 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 177351ab5ef5b4ac9c28fee6595310aa3c7c929b..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:018b00f084ea7ed43fdf85c27fd850157cebe839c4f8c5fa879c60df49e9c2a5 -size 4512 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/f5deee2f3301ee351c4008283ffafbb3_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/f5deee2f3301ee351c4008283ffafbb3_img.jpg deleted file mode 100644 index 255e4018376c9b0d7972e7a82d337ee734e95341..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/f5deee2f3301ee351c4008283ffafbb3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:528cd4d0082801f23b1f973e694e3a4bbacc90eb428b11c8c2225d5587e51073 -size 138356 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 602e94046000f14899adf3d1ab8d220a9635a879..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64a304437f8e7342c4cde5ed3b8cdb9446ace6349aa993a67fa0f6b028d7188f -size 4499 diff --git a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg b/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg deleted file mode 100644 index 8b59d2ed1cfc2d257eecedcae0ede3292b27abd0..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TR.FOCOM-NFO-SMOS-NBI-R005-v02.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:41e2370c8f6f258d02883bccfcd62b073e16e30387c78b49af4dcb6de66afb73 -size 199882 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/doc.md b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/doc.md deleted file mode 100644 index 7e41b317e6191a195e51e6c75a55a4b9beae310a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/doc.md +++ /dev/null @@ -1,4533 +0,0 @@ - - -# --- **O-RAN Work Group 6 (Cloudification and Orchestration)** - -# **O-Cloud Information Model** - -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 - -| | | -|---------------------------------------------------------------|----| -| List of figures ..... | 3 | -| List of tables ..... | 3 | -| Foreword..... | 5 | -| Modal verbs terminology ..... | 5 | -| Executive summary ..... | 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 ..... | 7 | -| 3.1 Terms ..... | 7 | -| 3.2 Symbols..... | 7 | -| 3.3 Abbreviations..... | 7 | -| 4 O-Cloud Information Model ..... | 7 | -| 4.1 Information Modeling Conventions..... | 7 | -| 4.1.1 Modeling approach, Unified Modeling Language (UML)..... | 7 | -| 4.1.2 Namespaces in the Information Model ..... | 7 | -| 4.1.3 Namespace Relationships..... | 8 | -| 4.2 Information Model Definitions ..... | 8 | -| 4.2.1 Namespace: ORAN.O2ims.Inventory ..... | 8 | -| 4.2.2 Namespace: ORAN.O2ims.Artifacts ..... | 65 | -| 4.2.3 Namespace: ORAN.O2ims.Cluster..... | 70 | -| 4.2.4 Namespace: ORAN.O2ims.Provisioning..... | 78 | -| 4.2.5 Namespace: ORAN.O2ims.Infrastructure..... | 84 | -| Annex (informative): Change History..... | 97 | - -# List of figures - -Figure 4.1.3-1 Relationship between Namespaces ..... 8 - -Figure 4.2.1.3.1.2-1 O2ims Inventory Objects Relationship Views..... 10 - -Figure 4.2.1.3.1.2-2 O2ims Inventory Event Subscribe/Notify Relationship View ..... 11 - -Figure 4.2.1.3.1.3.1-1 O2ims Alarm Relationship View ..... 11 - -Figure 4.2.1.3.1.3.2-1 Performance Monitoring Information Flow ..... 12 - -Figure 4.2.1.3.1.3.2-2 O2ims Performance Store Relationship View ..... 13 - -Figure 4.2.1.3.1.3.2-3 O2ims Performance Measurement Job Relationship View ..... 14 - -Figure 4.2.1.3.1.3.2-4 O2ims Performance Subscription Relationship View..... 15 - -Figure 4.2.1.3.1.3.2-5 O2ims Performance Report Relationship View ..... 16 - -Figure 4.2.1.3.1.4.1-1 illustrates the O-Cloud networking-related Resource relationships between the Information Object Classes..... 17 - -Figure 4.2.1.3.1.4.2.2-1 illustrates the Hardware Layer View and networking related Information Object Classes ..... 18 - -Figure 4.2.1.3.1.4.2.3-1 illustrates the Execution Environment Layer View and networking related Information Object Classes ..... 19 - -Figure 4.2.1.3.2.1-1 O2ims Inventory Intra-Namespace Inheritance ..... 19 - -Figure 4.2.1.3.2.1-2 O2ims Inventory Inter-Namespace Inheritance ..... 20 - -Figure 4.2.1.3.2.2-1 O2ims Alarm Inheritance ..... 20 - -Figure 4.2.1.3.2.2-1 O2ims Performance Inheritance..... 20 - -Figure 4.2.1.4.16.4-1 State & Status Diagram for PerformanceMeasurementJob ..... 44 - -Figure 4.2.2.3.1.2-1 ORAN.O2ims.Artifacts Intra-Namespace Relationships..... 66 - -Figure 4.2.2.3.1.3-1 ORAN.O2ims.Artifacts Inter-Namespace Relationships..... 67 - -Figure 4.2.2.3.2.1-1 ORAN.O2ims.Artifacts Inheritance..... 67 - -Figure 4.2.3.3.1.2-1 ORAN.O2ims.Cluster Intra-Namespace Relationships ..... 71 - -Figure 4.2.3.3.1.3-1 ORAN.O2ims.Cluster Inter-Namespace Relationships ..... 71 - -Figure 4.3.2.2.2.1-1 ORAN.O2ims.Cluster Inheritance ..... 72 - -Figure 4.2.4.3.1.2-1 ORAN.O2ims.Provisioning Intra-Namespace Relationships ..... 79 - -Figure 4.2.4.3.1.3-1 ORAN.O2ims.Provisioning Inter-Namespace Relationships ..... 79 - -Figure 4.2.4.3.2.1-1 ORAN.O2ims.Provisioning Inheritance ..... 80 - -Figure 4.2.5.3.1.2-1 O-Cloud Networking Overview ..... 86 - -Figure 4.2.5.3.1.2-2 ORAN.O2ims.Infrastructure Intra-Namespace Relationships ..... 87 - -Figure 4.2.5.3.1.3-1 ORAN.O2ims.Infrastructure Inter-Namespace Relationships ..... 87 - -Figure 4.2.5.3.2.1-1 ORAN.O2ims.Infrastructure Inheritance ..... 88 - -# List of tables - -Table 4.2.1.2.1-1 Imported Entities ..... 8 - -Table 4.2.1.2.2-1 Associated Entities ..... 9 - -Table 4.2.1.4.1.2-1 Attributes Properties for OCloud..... 21 - -Table 4.2.1.4.2.2-1 Attributes Properties for ResourceType ..... 23 - -Table 4.2.1.4.3.2-1 Attributes Properties for ResourcePool..... 25 - -Table 4.2.1.4.4.2-1 Attributes Properties for Resource ..... 26 - -Table 4.2.1.4.5.2-1 Attributes Properties for DeploymentManager ..... 28 - -Table 4.2.1.4.6.2-1 Attributes Properties for InventorySubscription ..... 29 - -Table 4.2.1.4.8.1-1 InfrastructureInventoryEvent Requirements ..... 31 - -Table 4.2.1.4.8.2-1 Attributes Properties for InfrastructureInventoryEvent..... 31 - -Table 4.2.1.4.9.1-1 OCloudAvailableNotification Requirements ..... 32 - -Table 4.2.1.4.9.2-1 Attributes Properties for OCloudAvailableNotification..... 32 - -Table 4.2.1.4.10.1-1 AlarmEventRecord Requirements..... 33 - -Table 4.2.1.4.10.2-1 Attributes Properties for AlarmEventRecord ..... 33 - -Table 4.2.1.4.11.1-1 AlarmEvent Requirements ..... 36 - -Table 4.2.1.4.11.2-1 Attributes Properties for AlarmEvent..... 36 - -Table 4.2.1.4.12.1-1 Subscription Requirements..... 37 - -Table 4.2.1.4.12.2-1 Attributes Properties for AlarmSubscription..... 37 - -Table 4.2.1.4.13.1-1 AlarmList Requirements ..... 38 - -Table 4.2.1.4.13.2-1 Attributes Properties for AlarmList..... 38 - -Table 4.2.1.4.14.1-1 PerformanceMeasurementStore Requirements ..... 39 - -Table 4.2.1.4.14.2-1 Attributes Properties for PerformanceMeasurementStore..... 39 - -Table 4.2.1.4.15.2-1 Attributes Properties for PerformanceMeasurementRecord ..... 40 - -Table 4.2.1.4.16.1-1 PerformanceMeasurementJob Requirements ..... 41 - -Table 4.2.1.4.16.2-1 Attributes Properties for PerformanceMeasurementJob ..... 41 - -Table 4.2.1.4.16.3-1 Attributes Constraints for PerformanceMeasurementJob ..... 43 - -Table 4.2.1.4.17.2-1 Attributes Properties for MeasuredResource..... 44 - -Table 4.2.1.4.18.2-1 Attributes Properties for CollectedMeasurement ..... 45 - -Table 4.2.1.4.19.2-1 Attributes Properties for PerformanceMeasurementJobChangeSubscription ..... 46 - -Table 4.2.1.4.20.2-1 Attributes Properties for PerformanceMeasurementJobChangeNotification ..... 48 - -Table 4.2.1.4.21.1-1 PerformanceSubscription Requirements ..... 50 - -Table 4.2.1.4.21.2-1 Attributes Properties for PerformanceSubscription..... 50 - -Table 4.2.1.4.22.2-1 Attributes Properties for PerformanceReportingFrequency ..... 52 - -Table 4.2.1.4.23.2-1 Attributes Properties for PerformanceSubscriptionCriteria ..... 53 - -Table 4.2.1.4.24.1-1 PerformanceMeasurementReport Requirements..... 54 - -Table 4.2.1.4.24.2-1 Attributes Properties for PerformanceMeasurementReport ..... 54 - -Table 4.2.1.4.25.2-1 Attributes Properties for JobReport..... 56 - -Table 4.2.1.4.26.2-1 Attributes Properties for ResourceReport ..... 56 - -Table 4.2.1.4.27.2-1 Attributes Properties for MeasurementValue ..... 57 - -Table 4.2.1.4.28.2-1 Attributes Properties for NotifyFileReady ..... 58 - -Table 4.2.1.4.29.2-1 Attributes Properties for FileInfo ..... 59 - -Table 4.2.1.4.30.2-1 Attributes Properties for Location ..... 61 - -Table 4.2.1.4.31.2-1 Attributes Properties for OCloudSite ..... 62 - -Table 4.2.1.4.32.2-1 Attributes Properties for LogQuery ..... 63 - -Table 4.2.1.4.33.2-1 Attributes Properties for DateRange ..... 65 - -Table 4.2.1.4.33.3-2 Attributes Constraints for DateRange ..... 65 - -Table 4.2.2.2.1-1 Imported Entities ..... 66 - -Table 4.2.2.2.2-1 Associated Entities ..... 66 - -Table 4.2.3.2.1-1 Imported Entities ..... 70 - -Table 4.2.3.2.2-1 Associated Entities ..... 70 - -Table 4.2.3.4.1.2-1 Attributes Properties for NodeClusterType..... 72 - -Table 4.2.3.4.2.2-1 Attributes Properties for NodeCluster..... 73 - -Table 4.2.3.4.3.2-1 Attributes Properties for ClusterResourceType..... 75 - -Table 4.2.3.4.4.2-1 Attributes Properties for ClusterResource..... 76 - -Table 4.2.3.4.5.2-1 Attributes Properties for ClusterResourceGroup..... 77 - -Table 4.2.4.2.1-1 Imported Entities ..... 78 - -Table 4.2.4.2.2-1 Associated Entities ..... 79 - -Table 4.2.4.4.1.2-1 Attributes Properties for ProvisioningRequest..... 80 - -Table 4.2.4.4.1.3-3 Attributes Constraints for ProvisioningRequest..... 81 - -Table 4.2.4.4.2.2-1 Attributes Properties for ProvisioningStatus ..... 82 - -Table 4.2.4.4.2.2-1 Attributes Properties for ProvisionedResourceSet ..... 84 - -Table 4.2.5.2.1-1 Imported Entities ..... 85 - -Table 4.2.5.2.2-1 Associated Entities ..... 85 - -Table 4.2.5.4.1.2-1 Attributes Properties for InfrastructureResourceType ..... 88 - -Table 4.2.5.4.1.2-1 Attributes Properties for InfrastructureResource..... 89 - -Table 4.2.5.4.3.2-1 Attributes Properties for Gateway ..... 91 - -Table 4.2.5.4.4.2-1 Attributes Properties for SiteNetwork ..... 92 - -Table 4.2.5.4.5.2-1 Attributes Properties for AttachmentCircuit ..... 94 - -Table 4.2.5.4.6.2-1 Attributes Properties for Port..... 94 - -Table 4.2.5.4.7.2-1 Attributes Properties for SegmentationElement..... 95 - -Table 4.2.5.4.8.2-1 Attributes Properties for NetworkAddress ..... 96 - -Table 4.2.5.4.8.3-1 Attributes Constraints for EndPoint ..... 96 - -# Foreword - -This Technical Specification (TS) has been produced by WG6 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. - -# Executive summary - -The O-Cloud Information Model provides the logical model of information elements and their relationships. This includes: - -- Enumerations which provide a predefined list of choices. -- Information Object Classes intended to convey classes that can become an Information Object -- Data Types which provide structure to the elements of an Information Object Class -- Notifications which is the information conveyed in a message from a service publisher to a service consumer - -# Introduction - -The O2 interface exposes information about the O-Cloud to external clients, presumably the SMO as the primary consumer. There are many relationships between elements of the model which need to be captured. - -The O-Cloud Information Model is based on the 3GPP process defined to document a Network Resource Model (NRM). The content contains all the salient elements of the NRM but does not follow the strict outline defined in 3GPP TS 32.160 [i.1]. The outline has been modified to align with other WG6 documents and to eliminate duplicative maintenance which leads to discord within the model. - -UML provides a rich set of concepts, notations, and model elements to model distributive systems. 3GPP TS 32.156 [1] provides the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism <> to model network management systems and their managed nodes. These conventions are applied to the O-Cloud Information Model. - -The Information model uses embedded PlantUML for diagraming. The information model relationships are modeled using UML Class diagram conventions. - -# 1 Scope - -The contents of the present document are 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. - -This document is both a Specification and an Informational Report in that it specifies the Information Model that is foundational for O-RAN's model-driven architecture for the O-Cloud information exposed over the O2 interface. - -In addition, this document includes information about existing standards and industry work that serve as a basis for work items in O-RAN. - -Lastly, this document describes the de facto methods and procedures with respect to a “modeling continuum” that aims to establish and evolve an O-Cloud Information Model from which O-RAN Data Models may be generated manually or with a set of tools. - -# 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 32.156: "Fixed Mobile Convergence repertoire ". -- [2] O-RAN.WG10.TS. Information Model and Data Models: "O-RAN Information Model and Data Models Specification". -- [3] O-RAN.WG6.TS.Orch-Use-Cases: “Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN” -- [4] OMG: "Unified Modelling Language Specification, Version 2.5.1". -. -- [5] IETF RFC 5424 : "The Syslog Protocol” - -## 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 32.160: "Management service template". -- [i.2] O-RAN.WG6.TS.O2-GA&P: "O2 Interface General Aspects and Principles". -- [i.3] O-RAN.WG6.TS.CADS: "Cloud Architecture and Deployment Scenarios". -- [i.4] ITU-T Recommendation X.733 (02/92): "Information technology - Open Systems Interconnection - Systems Management: Alarm reporting function" -- [i.5] ITU-T Recommendation X.736, "Information Technology - Open Systems Interconnection - System Management: Security Alarm Reporting Function", 1992" - -# --- 3 Definition of terms, symbols and abbreviations - -## 3.1 Terms - -For the purposes of the present document, the following terms apply: - -Generalized Object This is a kind of object whereby specialized objects can be derived from. - -Specialized Object This is a kind of object which is derived from one or more Generalized Object(s). - -## 3.2 Symbols - -For the purposes of the present document, the following symbols apply: - -## 3.3 Abbreviations - -For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply: - -| | | -|-----|-------------------------------| -| AAL | Accelerator Abstraction Layer | -| OIM | O-Cloud Information Model | - -# --- 4 O-Cloud Information Model - -## 4.1 Information Modeling Conventions - -### 4.1.1 Modeling approach, Unified Modeling Language (UML) - -The Information Model within O-Cloud Infrastructure shall use the Unified Modeling Language™ (UML®) version 2.5.1 [4] from the Object Management Group (OMG). - -The O-Cloud Infrastructure Information Model shall follow methodology documented in 3GPP TS 32.160 [i.1] Clause 5.2. - -### 4.1.2 Namespaces in the Information Model - -A Namespace provides a container for named elements, which are called its members. A Namespace may also import named elements from other specifications, in which case those elements become members of the importing Namespace. - -### 4.1.3 Namespace Relationships - -Figure 4.1.3-1 describes the relationship between each namespace defined in this specification. - -![Relationship diagram between O-RAN O2ims namespaces: Provisioning, Cluster, Infrastructure, Inventory, and Artifacts. Provisioning is fulfilled by Cluster, which is fulfilled by Infrastructure. Inventory is used by Cluster. Artifacts are used by Cluster and are the basis for Infrastructure and Cluster.](5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg) - -The diagram illustrates the relationships between five O-RAN O2ims namespaces: - -- ORAN.O2ims.Provisioning** (O-Cloud Provisioning): - - Contains: Provisioning Requests with ID, Object is LCM:ed as long as there is a Requirement (SLO), SMO -> O-Cloud, Point to a Template, Include issued Template Parameters, O-Cloud -> SMO, Request Creation/Update Status, Point to referenced Cluster and Infrastructure resources. - - Relationship: "Fulfilled by" points to **ORAN.O2ims.Cluster**. - - Service: "O-Cloud provided Managed Cluster services." -- ORAN.O2ims.Cluster** (O-Cloud (Managed) Node Clusters): - - Contains: Have a NodeClusterResourceTypes, Have Cluster Resources of ClusterResourceTypes, Use consumable Resources (from Inventory), Incur indirect "costs" based on allocated Resources (from Inventory), Have status on composed Cluster Resources, Have metrics on composed Cluster Resources, E.g. NodeClusters, Nodes, NodeGroups, NodeClusterSiteNWs, DeploymentManagers?. - - Relationship: "Fulfilled by" points to **ORAN.O2ims.Infrastructure**. - - Relationship: "Use" points to **ORAN.O2ims.Inventory**. - - Relationship: "Use" points to **ORAN.O2ims.Artifacts**. - - Service: "O-Cloud provided Managed Infrastructure services." -- ORAN.O2ims.Infrastructure** (O-Cloud (Managed) Infrastructure): - - Contains: Have a InfrastructureResourceTypes, Have Infrastructure Resources of InfrastructureResourceTypes, Use consumable Resources (from Inventory), Incur indirect "costs" based on allocated Resources (from Inventory), Have status on composed Infrastructure, Have metrics on composed Infrastructure, E.g. O-CloudGWs, SiteNWs and AttachmentCircuits. - - Relationship: "Based on\*" points to **ORAN.O2ims.Artifacts**. -- ORAN.O2ims.Inventory** (Exposed O-Cloud Resources): - - Contains: Consumables (finite availability), Incur some sort of "costs", Have "reality-based" status, Have "reality-based" metrics, Have a ResourceType descriptions, E.g. Servers, VMs, Accelerators, Networks, Gateways, Storages. - - Relationship: "Use" by **ORAN.O2ims.Cluster**. -- ORAN.O2ims.Artifacts** (O-Cloud Artifacts): - - Contains: Have Artifact Resources of ArtifactResourceTypes, Not consumable, Incur no "costs", Don't have status, Don't have metrics, E.g. Templates, Blueprints, SW, FW, Config bundles, files, images, libraries. - - Relationship: "Based on\*" by **ORAN.O2ims.Infrastructure**. - - Relationship: "Based on\*" by **ORAN.O2ims.Cluster**. - -\*) Node Cluster and Infrastructure are based on the Artifacts Template that is pointed out by the ProvisioningRequest and not directly from any Node Cluster or Infrastructure attributes/references - -Relationship diagram between O-RAN O2ims namespaces: Provisioning, Cluster, Infrastructure, Inventory, and Artifacts. Provisioning is fulfilled by Cluster, which is fulfilled by Infrastructure. Inventory is used by Cluster. Artifacts are used by Cluster and are the basis for Infrastructure and Cluster. - -Figure 4.1.3-1 Relationship between Namespaces - -## 4.2 Information Model Definitions - -### 4.2.1 Namespace: ORAN.O2ims.Inventory - -#### 4.2.1.1 Namespace Overview - -The O-RAN O2ims Inventory namespace defines the classes and their attributes which are directly exposed to the consumer (SMO) via its O2 IMS Interface. - -This namespace is used for O-Cloud infrastructure Resources. That content is meant only to be internally consumable to the O-Cloud. The O2ims Inventory has status, metrics and types as well as its topologies. These resources can be used to build up the O-Cloud Node Clusters and their compute, networking and storage capabilities. - -#### 4.2.1.2 Imported and associated information entities - -##### 4.2.1.2.1 Imported information entities and local labels - -Information entities imported into the model are also elements of the namespace and therefore shall remain unique within the namespace. - -Table 4.2.1.2.1-1 Imported Entities - -| Label reference | Local label | -|----------------------------------------------|-------------| -| TS 28.622 [6], information object class, Top | Top | - -##### 4.2.1.2.2 Associated information entities and local labels - -Information entities referenced in the model through an association which may be extended and overloaded with a new entity of the same name within the namespace are listed in the associated entities table. - -**Table 4.2.1.2.2-1 Associated Entities** - -| Label reference | Local label | -|------------------------------------------------------|------------------------------| -| WG10 IM/DM [2], PerformanceMeasureDictionary | PerformanceMeasureDictionary | -| WG10 IM/DM [2], PerformanceMeasureDefinition_ | PerformanceMeasureDefinition | -| WG10 IM/DM [2], AlarmDictionary | AlarmDictionary | -| WG10 IM/DM [2], AlarmDefinition | AlarmDefinition | -| WG10 IM/DM [2], ProbableCause | ProbableCause | -| 4.2.2.4.1, ArtifactResourceType | ArtifactResourceType | -| 4.2.2.4.1, ArtifactResource | ArtifactResource | -| 4.2.3.4.1, ClusterResourceType | ClusterResourceType | -| 4.2.3.4.2, ClusterResource | ClusterResource | -| 4.2.3.4.3, NodeClusterType | NodeClusterType | -| 4.2.3.4.4, NodeCluster | NodeCluster | -| 4.2.4.4.1, InfrastructureResourceType | InfrastructureResourceType | -| 4.2.4.4.2, InfrastructureResource | InfrastructureResource | - -#### 4.2.1.3 Class Diagram - -##### 4.2.1.3.1 Relationships - -###### 4.2.1.3.1.1 Description - -This clause depicts the set of classes (e.g. IOCs) that encapsulates the information relevant for the O-RAN Cloud (O-Cloud). This clause provides an overview of the relationships between relevant classes in UML. Subsequent clauses provide more detailed specification of various aspects of these classes. The UML Class diagram depicts a view of the namespace maintaining a defined focus so as not to overcrowd a single diagram trying to depict all relationships within the namespace. - -###### 4.2.1.3.1.2 O2ims Inventory Object Relationships - -The O2ims services have operations on the following managed service objects that are provided by the O-Cloud: - -- OCloud, -- Location, -- OCloudSite, -- ResourceType, -- ResourcePool, -- Resource, -- DeploymentManager, and -- InventoryChangeSubscription - -Figure 4.2.1.3.1.2-1 illustrates the relationships in between the information entities of the O2ims\_InfrastructureInventory services. Figure 4.2.1.3.1.2-2 illustrates the relationship for the subscribe/notify pattern. - -``` -@startuml -skin rose -skinparam ClassSterotypeFontStyle normal -skinparam style strictuml -hide members - -Namespace ORAN.O2ims.Inventory { -Class "O-Cloud" as OCloud -``` - -``` - -Class OCloudAvailableNotification <> -Class DeploymentManager - -Class Location - -Class "O-CloudSite" as OCloudSite - -Class ResourcePool - -Class Resource - -Class ResourceType - -Enum ResourceKind <> - -Enum ResourceClass <> - -OCloud .u.> OCloudAvailableNotification : SendsOnCreation -OCloud "1" *--> "+deploymentManagers\n1..*" DeploymentManager -OCloud "1" *--> "+oCloudSites\n1..*" OCloudSite -OCloud "1" *--> "+locations\n1..*" Location -Location "1" <--> "+oCloudSites\n0..*" OCloudSite : "\n" -OCloudSite "1" --> "+resourcePools\n1..*" ResourcePool -ResourcePool "1" *--> "+resources\n1..*" Resource -Resource "1" o--> "+elements\n0..*" Resource : IsComposedOf -Resource "0..*" --> "+resourceType\n1" ResourceType -OCloud "1" *--> "+resourceTypes\n1..*" ResourceType -ResourceType .. ResourceKind -ResourceType .. ResourceClass -ResourceType "1" -r-> "+alarmDictionary\n0..1" ORAN.ManagementArtifacts.AlarmDictionary -ResourceType "1" -r-> "+performanceDictionary\n0..1" -ORAN.ManagementArtifacts.PerformanceDictionary - -ORAN.ManagementArtifacts.AlarmDictionary -[hidden]- -ORAN.ManagementArtifacts.PerformanceDictionary - -} -@enduml - -``` - -![UML Class Diagram titled 'ORAN.O2ims.Inventory' showing relationships between O-Cloud, DeploymentManager, Location, O-CloudSite, ResourcePool, Resource, and ResourceType. It also includes a nested box for ORAN.ManagementArtifacts containing AlarmDictionary and PerformanceDictionary. Relationships include associations with multiplicities and stereotypes like <> and <>.](e9314c83043183351ed74908e9bf2f90_img.jpg) - -``` - -classDiagram - namespace ORAN.O2ims.Inventory { - class OCloudAvailableNotification { - <> - } - class O-Cloud - class DeploymentManager - class Location - class O-CloudSite - class ResourcePool - class Resource - class ResourceType - class ResourceKind { - <> - } - class ResourceClass { - <> - } - } - - namespace ORAN.ManagementArtifacts { - class AlarmDictionary - class PerformanceDictionary - } - - O-Cloud --> OCloudAvailableNotification : SendsOnCreation - O-Cloud "1" *-- "1..*" DeploymentManager : +deploymentManagers - O-Cloud "1" *-- "1..*" Location : +locations - O-Cloud "1" -- "0..*" O-CloudSite : +oCloudSites - Location "1" -- "1..*" O-CloudSite : +oCloudSites - O-CloudSite "1" *-- "1..*" ResourcePool : +resourcePools - ResourcePool "1" *-- "1..*" Resource : +resources - Resource "1" -- "1" ResourceType : +resourceType - Resource "1" -- "0..*" Resource : IsComposedOf - Resource "1" -- "0..*" Resource : +elements - ResourceType "1" -- "1..*" ResourceKind - ResourceType "1" -- "1..*" ResourceClass - ResourceType "1" -- "1" AlarmDictionary : +alarmDictionary - ResourceType "1" -- "0..1" PerformanceDictionary : +performanceDictionary - -``` - -UML Class Diagram titled 'ORAN.O2ims.Inventory' showing relationships between O-Cloud, DeploymentManager, Location, O-CloudSite, ResourcePool, Resource, and ResourceType. It also includes a nested box for ORAN.ManagementArtifacts containing AlarmDictionary and PerformanceDictionary. Relationships include associations with multiplicities and stereotypes like <> and <>. - -Figure 4.2.1.3.1.2-1 O2ims Inventory Objects Relationship Views - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -``` - -``` - -Namespace ORAN.O2ims.Inventory { -Class InventorySubscription - -Abstract Class InfrastructureInventoryObject_ -InfrastructureInventoryObject_ <|-- Resource -InfrastructureInventoryObject_ <|-- ResourceType -InfrastructureInventoryObject_ <|-- ResourcePool -InfrastructureInventoryObject_ <|-- DeploymentManager -InfrastructureInventoryObject_ <|-- "O-Cloud" -InfrastructureInventoryObject_ <|-- Location -InfrastructureInventoryObject_ <|-- "O-CloudSite" - -Enum NotificationEventType <> - -Class InfrastructureInventoryEvent <> - -InfrastructureInventoryEvent .r. NotificationEventType -InfrastructureInventoryEvent "*" --> "+priorObjectState\n0..1" InfrastructureInventoryObject_ -InfrastructureInventoryEvent "*" --> "+postObjectState\n0..1" InfrastructureInventoryObject_ -InventorySubscription "1" --> "*" InfrastructureInventoryEvent : -Subscription_Creates_Notification - -} -@enduml - -``` - -![UML Class Diagram titled 'ORAN.O2ims.Inventory' showing relationships between InventorySubscription, InfrastructureInventoryEvent, InfrastructureInventoryObject_, and its subclasses (Resource, ResourceType, ResourcePool, DeploymentManager, O-Cloud, Location, O-CloudSite). It also shows associations with NotificationEventType and multiplicity constraints like +priorObjectState and +postObjectState.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) - -``` - -classDiagram - class InventorySubscription - class InfrastructureInventoryEvent { - <> - } - class NotificationEventType { - <> - } - class InfrastructureInventoryObject_ { - <> - } - class Resource - class ResourceType - class ResourcePool - class DeploymentManager - class O-Cloud - class Location - class O-CloudSite - - InventorySubscription "1" --> "*" InfrastructureInventoryEvent : Subscription_Creates_Notification - InfrastructureInventoryEvent ..|> InfrastructureInventoryObject_ : +priorObjectState 0..1 - InfrastructureInventoryEvent ..|> InfrastructureInventoryObject_ : +postObjectState 0..1 - InfrastructureInventoryEvent ..|> NotificationEventType - InfrastructureInventoryObject_ <|-- Resource - InfrastructureInventoryObject_ <|-- ResourceType - InfrastructureInventoryObject_ <|-- ResourcePool - InfrastructureInventoryObject_ <|-- DeploymentManager - InfrastructureInventoryObject_ <|-- O-Cloud - InfrastructureInventoryObject_ <|-- Location - InfrastructureInventoryObject_ <|-- O-CloudSite - -``` - -UML Class Diagram titled 'ORAN.O2ims.Inventory' showing relationships between InventorySubscription, InfrastructureInventoryEvent, InfrastructureInventoryObject\_, and its subclasses (Resource, ResourceType, ResourcePool, DeploymentManager, O-Cloud, Location, O-CloudSite). It also shows associations with NotificationEventType and multiplicity constraints like +priorObjectState and +postObjectState. - -Figure 4.2.1.3.1.2-2 O2ims Inventory Event Subscribe/Notify Relationship View - -###### 4.2.1.3.1.3 Infrastructure Monitoring Relationships - -###### 4.2.1.3.1.3.1 Infrastructure Fault Relationships - -The O2ims\_InfrastructureMonitoring services has operations on the following managed service objects that are provided by the O-Cloud for faults: - -- AlarmList -- AlarmSubscription -- LogQuery - -Figure 4.2.1.3.1.3.1 -1 illustrates the relationships in between the information entities of the O2ims\_InfrastructureMonitoring fault services. - -``` -@startuml -``` - -``` -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -Namespace ORAN.ManagementArtifacts { - Class AlarmDefinition - - Class ProbableCause -} - -Namespace ORAN.O2ims.Any { - Class ObjectType <> - - Class Object <> - - Object -u[hidden]-> ObjectType - Object -u[hidden]-> ORAN.ManagementArtifacts.AlarmDefinition -} - -Namespace ORAN.O2ims.Inventory { - - Class AlarmSubscription - - Enum AlarmNotificationType <> - - Enum PerceivedSeverity <> - - Class AlarmEventRecord <> - - AlarmEventRecord --> ORAN.ManagementArtifacts.ProbableCause : IsDiagnosedAs - AlarmEventRecord --> PerceivedSeverity - - Class AlarmEvent <> - - AlarmEvent *-> AlarmEventRecord - - AlarmEvent --> AlarmNotificationType - AlarmSubscription --> AlarmEvent : Creates - - AlarmEventRecord -u-> ORAN.O2ims.Any.ObjectType : References - AlarmEventRecord -u-> ORAN.O2ims.Any.Object : References - - AlarmEventRecord --> ORAN.ManagementArtifacts.AlarmDefinition : IsDefinedByA - - Class AlarmList - AlarmList *-d-> AlarmEventRecord : HasMany - - Class LogQuery - Class DateRange <> - LogQuery "1" *---> "0..*\\n+dateRanges" DateRange - Class NotifyFileReady <> - LogQuery --> NotifyFileReady : MayCreate - - DateRange -l[hidden]- AlarmEvent -} -@enduml -``` - -![UML Class Diagram showing O2ims Alarm Relationship View. It includes three packages: ORAN.O2ims.Any, ORAN.O2ims.Inventory, and ORAN.ManagementArtifacts. ORAN.O2ims.Any contains ObjectType and Object data types. ORAN.O2ims.Inventory contains AlarmList, AlarmSubscription, LogQuery, AlarmEventRecord, AlarmEvent, NotifyFileReady, DateRange, PerceivedSeverity, and AlarmNotificationType. ORAN.ManagementArtifacts contains AlarmDefinition and ProbableCause. Relationships include References, HasMany, Creates, MayCreate, IsDefinedByA, and IsDiagnosedAs.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) - -``` - -classDiagram - class ORAN_O2ims_Any { - <> ObjectType - <> Object - } - class ORAN_O2ims_Inventory { - AlarmList - AlarmSubscription - LogQuery - <> AlarmEventRecord - <> AlarmEvent - <> NotifyFileReady - <> DateRange - <> PerceivedSeverity - <> AlarmNotificationType - } - class ORAN_ManagementArtifacts { - AlarmDefinition - ProbableCause - } - - ORAN_O2ims_Any.ObjectType --> ORAN_O2ims_Inventory.AlarmEventRecord : References - ORAN_O2ims_Any.Object --> ORAN_O2ims_Inventory.AlarmEventRecord : References - ORAN_O2ims_Inventory.AlarmList --> ORAN_O2ims_Inventory.AlarmEventRecord : HasMany - ORAN_O2ims_Inventory.AlarmSubscription --> ORAN_O2ims_Inventory.AlarmEventRecord : Creates - ORAN_O2ims_Inventory.LogQuery --> ORAN_O2ims_Inventory.AlarmEventRecord : MayCreate - ORAN_O2ims_Inventory.LogQuery --> ORAN_O2ims_Inventory.DateRange : +dateRanges - ORAN_O2ims_Inventory.AlarmEventRecord --> ORAN_ManagementArtifacts.AlarmDefinition : IsDefinedByA - ORAN_O2ims_Inventory.AlarmEventRecord --> ORAN_ManagementArtifacts.ProbableCause : IsDiagnosedAs - ORAN_O2ims_Inventory.AlarmEventRecord --> ORAN_O2ims_Inventory.AlarmEvent : - ORAN_O2ims_Inventory.AlarmEvent --> ORAN_O2ims_Inventory.NotifyFileReady : - ORAN_O2ims_Inventory.AlarmEventRecord --> ORAN_O2ims_Inventory.PerceivedSeverity : - ORAN_O2ims_Inventory.AlarmEvent --> ORAN_O2ims_Inventory.AlarmNotificationType : - -``` - -UML Class Diagram showing O2ims Alarm Relationship View. It includes three packages: ORAN.O2ims.Any, ORAN.O2ims.Inventory, and ORAN.ManagementArtifacts. ORAN.O2ims.Any contains ObjectType and Object data types. ORAN.O2ims.Inventory contains AlarmList, AlarmSubscription, LogQuery, AlarmEventRecord, AlarmEvent, NotifyFileReady, DateRange, PerceivedSeverity, and AlarmNotificationType. ORAN.ManagementArtifacts contains AlarmDefinition and ProbableCause. Relationships include References, HasMany, Creates, MayCreate, IsDefinedByA, and IsDiagnosedAs. - -Figure 4.2.1.3.1.3.1-1 O2ims Alarm Relationship View - -###### 4.2.1.3.1.3.2 Infrastructure Performance Relationships - -The O2ims\_InfrastructureMonitoring services follow a flow described in the O2 GAP[i.2] clause 3.9.9. This primarily consists of: - -- 1) The Performance Measurement Store - used for storage and configuration of performance measurements. -- 2) The Performance Measurement Job - used to collect performance measurements and insert them into the Performance Measurement Store. -- 3) The Performance Subscription - used to identify what PerformanceMeasurementRecord(s) in the PeformanceMeasurementStore are reported, when they are reported, and how the report is to be delivered to the subscriber. -- 4) The Performance Measurement Report - The notification payload used to convey measurement values identified by a Performance Subscription to the identified subscriber in a format selected by the subscriber. - -![Flowchart of Performance Monitoring Information Flow. The flow is: Performance Measurement Job (Collect) -> Performance Measurement Store (Store) -> Performance Subscription (Transform) -> Performance Measurement Report (Receive). Intermediate steps are Insert, Extract, and Transmit.](16c1175b5f05a4b55e6d396fc51b15b3_img.jpg) - -``` - -graph LR - subgraph PMJ [Performance Measurement Job] - direction TB - P1[Collect] --> P2[Insert] - end - subgraph PMS [Performance Measurement Store] - direction TB - P3[Store] --> P4[Extract] - end - subgraph PS [Performance Subscription] - direction TB - P5[Transform] --> P6[Transmit] - end - subgraph PMR [Performance Measurement Report] - direction TB - P7[Receive] - end - PMJ --> PMS - PMS --> PS - PS --> PMR - -``` - -The Performance Measurement Job collects measurements and inserts them into the Performance Measurement Store from which a Performance Subscription selects and formats into a Performance Measurement Report and delivers the report to an identified subscriber endpoint. - -Flowchart of Performance Monitoring Information Flow. The flow is: Performance Measurement Job (Collect) -> Performance Measurement Store (Store) -> Performance Subscription (Transform) -> Performance Measurement Report (Receive). Intermediate steps are Insert, Extract, and Transmit. - -Figure 4.2.1.3.1.3.2-1 Performance Monitoring Information Flow - -The O2ims\_InfrastructureMonitoring information model have sub-components as follows: - -- Performance Store - - o PerformanceMeasurementStore - -- PerformanceMeasurementRecord -- Performance Jobs - - PerformanceMeasurementJob - - MeasuredResource - - CollectedMeasurement - - PerformanceMeasurementJobChangeSubscription - - PerformanceMeasurementJobChangeNotification -- Performance Subscriptions - - PerformanceSubscription - - PerformanceReportingFrequency - - PerformanceSubscriptionCriteria -- Performance Reports - - PerformanceMeasurementReport - - JobReport - - ResourceReport - - MeasurementValue - - NotifyFileReady - - FileInfo - -Figure 4.2.1.3.1.3.2-2 illustrates the relationships in between the PerformanceMeasurementStore and PerformanceMeasurementRecord and other information entities. - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -Namespace ORAN.O2ims.Inventory { - Class Resource - - Class PerformanceMeasurementRecord <> - - PerformanceMeasurementRecord "*" --> "1" PerformanceMeasurementJob : CollectedBy - PerformanceMeasurementRecord "*" --> "1" ORAN.O2ims.Inventory.Resource : MeasuredObject - PerformanceMeasurementRecord "*" --> "1" ORAN.ManagementArtifacts.PerformanceMeasurementDefinition : IsDefinedBy - - Class PerformanceMeasurementStore << InformationObjectClass >> - - PerformanceMeasurementStore "1" *--> "*" PerformanceMeasurementRecord : MayHaveMany -} - -Namespace ORAN.ManagementArtifacts { - Class PerformanceMeasurementDefinition -} - -@enduml - -``` - -![UML Class Diagram showing relationships in ORAN.O2ims.Inventory and ORAN.ManagementArtifacts namespaces. PerformanceMeasurementStore (InformationObjectClass) has a 1..* relationship with PerformanceMeasurementRecord (dataType) labeled 'MayHaveMany'. PerformanceMeasurementRecord has relationships with Resource (MeasuredObject), PerformanceMeasurementJob (CollectedBy), and PerformanceMeasurementDefinition (IsDefinedBy).](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) - -``` - -classDiagram - class PerformanceMeasurementStore { - <> - } - class PerformanceMeasurementRecord { - <> - } - class Resource { - } - class PerformanceMeasurementJob { - } - class PerformanceMeasurementDefinition { - } - - PerformanceMeasurementStore "1" *-- "*" PerformanceMeasurementRecord : MayHaveMany - PerformanceMeasurementRecord "*" -- "1" Resource : MeasuredObject - PerformanceMeasurementRecord "*" -- "1" PerformanceMeasurementJob : CollectedBy - PerformanceMeasurementRecord "*" -- "1" PerformanceMeasurementDefinition : IsDefinedBy - -``` - -UML Class Diagram showing relationships in ORAN.O2ims.Inventory and ORAN.ManagementArtifacts namespaces. PerformanceMeasurementStore (InformationObjectClass) has a 1..\* relationship with PerformanceMeasurementRecord (dataType) labeled 'MayHaveMany'. PerformanceMeasurementRecord has relationships with Resource (MeasuredObject), PerformanceMeasurementJob (CollectedBy), and PerformanceMeasurementDefinition (IsDefinedBy). - -Figure 4.2.1.3.1.3.2-2 O2ims Performance Store Relationship View - -Figure 4.2.1.3.1.3.2-3 illustrates the relationships in between the PerformanceMeasurementJob, MeasuredResource, CollectedMeasurement, PerformanceMeasurementJobChangeSubscription and other information entities. - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -Namespace ORAN.O2ims.Inventory { - - Enum PerformanceMeasurementJobChangeSubscriptionType <> - Enum PerformanceMeasurementJobChangeSubscriptionDetailType <> - - Class PerformanceMeasurementJobChangeSubscription << InformationObjectClass >> - - PerformanceMeasurementJobChangeSubscription .. PerformanceMeasurementJobChangeSubscriptionType - PerformanceMeasurementJobChangeSubscription .u. - PerformanceMeasurementJobChangeSubscriptionDetailType - - Class PerformanceMeasurementJobChangeNotification << (N,orchid) Notification >> - - PerformanceMeasurementJobChangeNotification .u. - PerformanceMeasurementJobChangeSubscriptionType - PerformanceMeasurementJobChangeNotification --> MeasuredResource - PerformanceMeasurementJobChangeNotification --> CollectedMeasurement - - PerformanceMeasurementJobChangeSubscription "1" --> "*" - PerformanceMeasurementJobChangeNotification : Subscription_Creates_Notification - - Enum PerformanceMeasurementJobState <> - - Class MeasuredResource <> - MeasuredResource --> Resource - MeasuredResource --> ResourceType - Class CollectedMeasurement <> - -``` - -``` - -Class PerformanceMeasurementJob <> - -PerformanceMeasurementJob .. PerformanceMeasurementJobState -PerformanceMeasurementJob "1" *-u-> "*\nresource" MeasuredResource : Job_Measures_Resources -PerformanceMeasurementJob "1" *-u-> "*\nresource" CollectedMeasurement : Job_Collects_Measurements -PerformanceMeasurementJob "*" --> "*" ORAN.O2ims.Inventory.ResourceType : Job_Measures_ResourceTypes - -CollectedMeasurement "*" --> "1" ORAN.ManagementArtifacts.PerformanceMeasurementDefinition : Measure_DefinedBy_Dictionary -CollectedMeasurement --> ResourceType : identifiesDictionary -Class PerformanceMeasurementRecord <> - -PerformanceMeasurementRecord "*" --> "1" PerformanceMeasurementJob : CollectedBy -} - -Namespace ORAN.ManagementArtifacts { - Class PerformanceMeasurementDefinition -} - -@enduml - -``` - -![UML Class Diagram showing O2ims Performance Measurement Job Relationship View. The diagram is titled 'ORAN.O2ims.Inventory' and includes a nested box for 'ORAN.ManagementArtifacts'. It shows classes like PerformanceMeasurementJob, PerformanceMeasurementRecord, MeasuredResource, CollectedMeasurement, and various enumerations and notifications with their relationships.](8307f6b04df072c9332f9987e034272c_img.jpg) - -``` - -classDiagram - class PerformanceMeasurementJob { - <> - } - class PerformanceMeasurementRecord { - <> - } - class MeasuredResource { - <> - } - class CollectedMeasurement { - <> - } - class PerformanceMeasurementJobState { - <> - } - class PerformanceMeasurementJobChangeSubscription { - <> - } - class PerformanceMeasurementJobChangeSubscriptionDetailType { - <> - } - class PerformanceMeasurementJobChangeSubscriptionType { - <> - } - class PerformanceMeasurementJobChangeNotification { - <> - } - class Resource { - } - class ResourceType { - } - class PerformanceMeasurementDefinition { - <> - } - - PerformanceMeasurementJobState -.-> PerformanceMeasurementJob - PerformanceMeasurementJob -.-> MeasuredResource : Job_Measures_Resources - PerformanceMeasurementJob -.-> CollectedMeasurement : Job_Collects_Measurements - PerformanceMeasurementJob --> ResourceType : Job_Measures_ResourceTypes - PerformanceMeasurementRecord --> PerformanceMeasurementJob : CollectedBy - MeasuredResource --> Resource : resource - CollectedMeasurement --> PerformanceMeasurementDefinition : Measure_DefinedBy_Dictionary - CollectedMeasurement --> ResourceType : identifiesDictionary - PerformanceMeasurementJobChangeSubscription -.-> PerformanceMeasurementJob - PerformanceMeasurementJobChangeSubscriptionDetailType -.-> PerformanceMeasurementJobChangeSubscription - PerformanceMeasurementJobChangeSubscriptionType -.-> PerformanceMeasurementJobChangeSubscription - PerformanceMeasurementJobChangeSubscription --> PerformanceMeasurementJobChangeNotification : Subscription_Creates_Notification - PerformanceMeasurementJobChangeNotification --> MeasuredResource - PerformanceMeasurementJobChangeNotification --> PerformanceMeasurementRecord - PerformanceMeasurementJobChangeNotification --> CollectedMeasurement - -``` - -UML Class Diagram showing O2ims Performance Measurement Job Relationship View. The diagram is titled 'ORAN.O2ims.Inventory' and includes a nested box for 'ORAN.ManagementArtifacts'. It shows classes like PerformanceMeasurementJob, PerformanceMeasurementRecord, MeasuredResource, CollectedMeasurement, and various enumerations and notifications with their relationships. - -Figure 4.2.1.3.1.3.2-3 O2ims Performance Measurement Job Relationship View - -Figure 4.2.1.3.1.3.2-4 illustrates the relationships in between the PerformanceSubscription, PerformanceReportingFrequency, PerformanceSubscriptionCriteria and other information entities. - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -Namespace ORAN.O2ims.Inventory { - -Class PerformanceMeasurementStore << InformationObjectClass >> - -Class PerformanceSubscriptionCriteria <> - -enum ReportDeliveryMechanism -enum SubscriptionMode - -Class PerformanceReportingFrequency <> - -PerformanceReportingFrequency .r. SubscriptionMode - -Class PerformanceSubscription <> - -PerformanceSubscription .. ReportDeliveryMechanism -PerformanceSubscription *--> PerformanceReportingFrequency -PerformanceSubscription *--> PerformanceSubscriptionCriteria - -PerformanceSubscription ..> PerformanceMeasurementStore : SelectsFrom - -} - -@enduml - -``` - -![UML Class Diagram titled 'ORAN.O2ims.Inventory' showing relationships between PerformanceSubscription, PerformanceReportingFrequency, PerformanceSubscriptionCriteria, PerformanceMeasurementStore, and ReportDeliveryMechanism. PerformanceSubscription has a composition relationship with PerformanceReportingFrequency, which is associated with SubscriptionMode. PerformanceSubscription has associations with PerformanceSubscriptionCriteria and ReportDeliveryMechanism. PerformanceSubscription has a 'SelectsFrom' association with PerformanceMeasurementStore.](9b9d2abd741ed4bafe7f78f89961c663_img.jpg) - -``` - -classDiagram - class PerformanceSubscription { - <> - } - class PerformanceReportingFrequency { - <> - } - class PerformanceSubscriptionCriteria { - <> - } - class PerformanceMeasurementStore { - <> - } - class ReportDeliveryMechanism - class SubscriptionMode - - PerformanceSubscription *--> PerformanceReportingFrequency - PerformanceReportingFrequency -- SubscriptionMode - PerformanceSubscription --> PerformanceSubscriptionCriteria - PerformanceSubscription --> ReportDeliveryMechanism - PerformanceSubscription ..> PerformanceMeasurementStore : SelectsFrom - -``` - -UML Class Diagram titled 'ORAN.O2ims.Inventory' showing relationships between PerformanceSubscription, PerformanceReportingFrequency, PerformanceSubscriptionCriteria, PerformanceMeasurementStore, and ReportDeliveryMechanism. PerformanceSubscription has a composition relationship with PerformanceReportingFrequency, which is associated with SubscriptionMode. PerformanceSubscription has associations with PerformanceSubscriptionCriteria and ReportDeliveryMechanism. PerformanceSubscription has a 'SelectsFrom' association with PerformanceMeasurementStore. - -Figure 4.2.1.3.1.3.2-4 O2ims Performance Subscription Relationship View - -Figure 4.2.1.3.1.3.2-5 illustrates the relationships in between the PerformanceMeasurementReport, JobReport, ResourceReport, MeasurementValue, NotifyFileReady, FileInfo and other information entities. - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -Namespace ORAN.O2ims.Inventory { - -Class PerformanceSubscription << InformationObjectClass >> - -Class MeasurementValue <> - -``` - -``` -MeasurementValue "measureId" -d- ORAN.ManagementArtifacts.PerformanceMeasurementDefinition : -identifies -``` - -``` -Note left on link : measureId can be either:\n\t- performanceMeasurementName\n\t- performanceMeasureId. -``` - -``` -Class ResourceReport <> -``` - -``` -ResourceReport "1" *--> "*" MeasurementValue : hasMany -ResourceReport "1" *--> "1" ORAN.O2ims.Inventory.Resource : MeasuredObject -``` - -``` -Class JobReport <> -``` - -``` -JobReport "1" .. "1" PerformanceMeasurementJob : IsFor -JobReport "1" *--> "1..*" ResourceReport : hasMany -``` - -``` -Class PerformanceMeasurementReport <> -``` - -``` -PerformanceMeasurementReport .u. PerformanceSubscription: Subscription_Creates_Notification -PerformanceMeasurementReport "1" *--> "1..*" JobReport : hasMany -``` - -``` -Enum FileDataType <> -``` - -``` -Class FileInfo <> -``` - -``` -FileInfo .. FileDataType -``` - -``` -Class NotifyFileReady <> -``` - -``` -NotifyFileReady *--> FileInfo -NotifyFileReady .u. PerformanceSubscription: Subscription_Creates_Notification -``` - -``` -} -``` - -``` -@enduml -``` - -![UML Class Diagram titled 'ORAN.O2ims.Inventory' showing relationships between PerformanceSubscription, PerformanceMeasurementReport, JobReport, ResourceReport, MeasurementValue, Resource, NotifyFileReady, FileInfo, and FileDataType. It also shows a relationship to ORAN.ManagementArtifacts.](5445597cceefaca1ac89e710fe339325_img.jpg) - -``` - -classDiagram - class PerformanceSubscription { - <> - } - class PerformanceMeasurementReport { - <> - } - class JobReport { - <> - } - class ResourceReport { - <> - } - class MeasurementValue { - <> - } - class Resource { - } - class PerformanceMeasurementJob { - } - class NotifyFileReady { - <> - } - class FileInfo { - <> - } - class FileDataType { - <> - } - class PerformanceMeasurementDefinition { - } - - PerformanceSubscription --> PerformanceMeasurementReport : Subscription_Creates_Notification - PerformanceSubscription --> NotifyFileReady : Subscription_Creates_Notification - PerformanceMeasurementReport "1" --> "1..*" JobReport : hasMany - JobReport "1" --> "1..*" ResourceReport : hasMany - JobReport "1" --> "1" PerformanceMeasurementJob : IsFor - ResourceReport "1" --> "1" Resource : MeasuredObject - ResourceReport "1" --> "*" MeasurementValue : hasMany - MeasurementValue --> PerformanceMeasurementDefinition : measuredId - FileInfo --> FileDataType - NotifyFileReady --> FileInfo - Note right of PerformanceMeasurementDefinition: measuredId can be either: -- performanceMeasurementName -- performanceMeasuredId. - PerformanceMeasurementDefinition --> MeasurementValue : identifies - -``` - -UML Class Diagram titled 'ORAN.O2ims.Inventory' showing relationships between PerformanceSubscription, PerformanceMeasurementReport, JobReport, ResourceReport, MeasurementValue, Resource, NotifyFileReady, FileInfo, and FileDataType. It also shows a relationship to ORAN.ManagementArtifacts. - -Figure 4.2.1.3.1.3.2-5 O2ims Performance Report Relationship View - -##### 4.2.1.3.1.4 O-Cloud Networking Relationships - -###### 4.2.1.3.1.4.1 O-Cloud Networking Relationships Overview - -The O-Cloud Network provides seamless connectivity within an O-Cloud Site and facilitates external connectivity, such as transport network access, to various O-Cloud Resources. Clause 3.4.3 of the O-RAN.WG6.O2-GA&P [i.2] specification, outlines the fundamental concepts of the O-Cloud provisioning and defines these concepts at different layers. For instance, networking-related concepts such as O-Cloud Site Network Fabric (aka. SiteNWFabric) and O-Cloud Site Gateway (aka. SiteGW) can be - -defined at the hardware layer, which is related to that layers' consumable constructs, and the networking-related concepts such as O-Cloud Site Network (aka. SiteNW), O-Cloud Gateway, and O-Cloud AttachmentCircuit can be defined at the execution environment layer as described in the O-RAN.WG6.O2-GA&P [i.2] spec. Also, there can be inter-namespace relationships for instance, Networking concept related to an O-Cloud Node Cluster such as, O-Cloud Node Cluster Site Network (aka. NodeClusterSiteNW) defined in ORAN.O2ims.Clusters namespace mapped to a SiteNW object and terminated by an O-Cloud Gateway object defined in ORAN.O2ims.Inventory namespace. - -An O-Cloud AttachmentCircuit as defined in O-RAN.WG6.O2-GA&P [i.2], clause 3.4.3.5.10 has two possible associations — one with an O-Cloud Gateway and another with the SiteNW. This accommodates the two scenarios where a SiteNW connects to the transport network through an O-Cloud Gateway or where a SiteNW connects directly to the transport network. There can also be the case that SiteNWs are only used for internal connectivity within an O-Cloud Site, in which case, there is no need to associate (neither directly, nor via an O-Cloud Gateway) a SiteNW to an O-Cloud AttachmentCircuit. - -Figure 4.2.1.3.1.4-1 illustrates the O-Cloud networking-related Resource relationships between the Information Objects Classes. - -``` -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -namespace ORAN.O2ims.Clusters { -Class NodeClusterSiteNW <> -} - -namespace ORAN.O2ims.Inventory { -Class Gateway <> -Class SiteGW <> -Class SiteNW <> -Class SiteNWFabric <> -Class AttachmentCircuit <> -Class Compute <> - -Gateway "*" --> "1" SiteGW : "RealizedBy" -Gateway "1" --> "*" AttachmentCircuit : "AttachTo" -SiteNW "1" --> "*" AttachmentCircuit : "AttachTo" -SiteNW "*" --> "*" Gateway : "TerminatedBy" -SiteNW "*" --> "1" SiteNWFabric : "RealizedBy" -SiteNW "*" --> "*" Compute : "TerminatedBy" -SiteGW "*" --> "*" SiteNWFabric : "ConnectedTo" -ORAN.O2ims.Clusters.NodeClusterSiteNW "*" --> "*" Gateway : "TerminatedBy" -ORAN.O2ims.Clusters.NodeClusterSiteNW "1" --> "1" SiteNW : "MappedTo" -Compute "*" --> "*" SiteNWFabric : "ConnectedTo" -} - -@enduml -``` - -![UML Class diagram showing O-Cloud networking-related Resource relationships between Information Object Classes. The diagram includes two packages: ORAN.O2ims.Clusters and ORAN.O2ims.Inventory. Classes include NodeClusterSiteNW, SiteNW, Compute, AttachmentCircuit, SiteGW, and SiteNWFabric. Relationships include MappedTo, TerminatedBy, AttachTo, RealizedBy, and ConnectedTo.](d53cd0fd1cf896a9353fd63de1505ba2_img.jpg) - -``` - -classDiagram - class NodeClusterSiteNW - class SiteNW - class Compute - class AttachmentCircuit - class SiteGW - class SiteNWFabric - class Gateway - - NodeClusterSiteNW "1" --> "*" SiteNW : MappedTo - SiteNW "*" --> "1" NodeClusterSiteNW - SiteNW "*" --> "*" Compute : TerminatedBy - SiteNW "*" --> "*" AttachmentCircuit : RealizedBy - SiteNW "*" --> "*" SiteNWFabric : ConnectedTo - SiteNW "*" --> "*" Gateway : TerminatedBy - Compute "*" --> "*" SiteNWFabric : ConnectedTo - AttachmentCircuit "*" --> "1" SiteNWFabric - AttachmentCircuit "*" --> "1" SiteGW : AttachTo - AttachmentCircuit "*" --> "*" SiteNWFabric : ConnectedTo - SiteGW "*" --> "1" AttachmentCircuit : RealizedBy - SiteGW "*" --> "*" SiteNWFabric : ConnectedTo - SiteGW "*" --> "1" Gateway : AttachTo - -``` - -UML Class diagram showing O-Cloud networking-related Resource relationships between Information Object Classes. The diagram includes two packages: ORAN.O2ims.Clusters and ORAN.O2ims.Inventory. Classes include NodeClusterSiteNW, SiteNW, Compute, AttachmentCircuit, SiteGW, and SiteNWFabric. Relationships include MappedTo, TerminatedBy, AttachTo, RealizedBy, and ConnectedTo. - -**Figure 4.2.1.3.1.4.1-1 O-Cloud networking-related Resource relationships between the Information Object Classes.** - -###### **4.2.1.3.1.4.2 O-Cloud Networking Relationships View** - -###### **4.2.1.3.1.4.2.1 Overview** - -The O-RAN.WG6.O2-GA&P [i.2], clause 3.4.3.3 outlines fundamental concepts of the Resource View. For enabling separation of authority and operations, O-Cloud offers various types of resource views, in the form of different group of actors, some of them deals with hardware or more physical types of O-Cloud Resources whereas, others consume logical set of O-Cloud Resources. - -###### **4.2.1.3.1.4.2.2 Hardware Layer View** - -The O-RAN.WG6.O2-GA&P [i.2], clause 3.4.3.4 explains the Hardware Layer concept, which forms the foundation of a cloud, comprising physical computes that are inter-connected through network fabric and routers for external connectivity. According to O-RAN.WG6.CADS [i.3], a Cloud Site hosts Cloud Infrastructure equipment, abstracting O-Cloud Resources for leasing - -through the IMS. From the SMO perspective, understanding hardware concepts focuses on O-Cloud Resource locations, capabilities, capacity, availability, and potential disturbances, rather than physical realization. - -``` -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -namespace ORAN.O2ims.Inventory { - -package "Hardware Layer" as HWL <> { - Class SiteNWFabric <> - Class SiteGW <> - Class Compute <> - - SiteGW "*" --> "*" SiteNWFabric : "ConnectedTo" - Compute "*" --> "*" SiteNWFabric : "ConnectedTo" -} - -@enduml -``` - -![UML Class Diagram titled 'ORAN.O2ims.Inventory' showing the 'Hardware Layer' package. Inside the package, there are three classes: 'Compute', 'SiteGW', and 'SiteNWFabric', all stereotyped as '«InformationObjectClass»'. Arrows labeled 'ConnectedTo' with '*' multiplicity point from 'Compute' and 'SiteGW' to 'SiteNWFabric'.](844077b3034f0030b404207db0ad76b4_img.jpg) - -``` - -classDiagram - class Compute { - <> - } - class SiteGW { - <> - } - class SiteNWFabric { - <> - } - Compute "*" --> "*" SiteNWFabric : ConnectedTo - SiteGW "*" --> "*" SiteNWFabric : ConnectedTo - -``` - -UML Class Diagram titled 'ORAN.O2ims.Inventory' showing the 'Hardware Layer' package. Inside the package, there are three classes: 'Compute', 'SiteGW', and 'SiteNWFabric', all stereotyped as '«InformationObjectClass»'. Arrows labeled 'ConnectedTo' with '\*' multiplicity point from 'Compute' and 'SiteGW' to 'SiteNWFabric'. - -Figure 4.2.1.3.1.4.2.2-1 Hardware Layer View and networking related Information Object Classes - -###### 4.2.1.3.1.4.2.3 Execution Environment Layer View - -The O-RAN.WG6.O2-GA&P [i.2], clause 3.4.3.5 explains the Execution Environment Layer concept, which transforms hardware layer constructs into consumable O-Cloud Node(s), Site Network(s), Gateway(s), and many more, as abstract O-Cloud Resources available for leasing through the IMS. - -``` -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -namespace ORAN.O2ims.Inventory { - -package "Execution Environment Layer" as EEL<> { - Class Gateway <> - Class SiteNW <> - Class AttachmentCircuit <> -} - -@enduml -``` - -``` - -Gateway "1" --> "*" AttachmentCircuit : "AttachTo" -SiteNW "1" --> "*" AttachmentCircuit : "AttachTo" -SiteNW "*" --> "*" Gateway : "TerminatedBy" -} -} - -@enduml - -``` - -![UML Class Diagram titled 'ORAN.O2ims.Inventory' showing the 'Execution Environment Layer'. It contains three classes: SiteNW, Gateway, and AttachmentCircuit. SiteNW has a 1-to-many relationship with AttachmentCircuit labeled 'AttachTo'. Gateway has a 1-to-many relationship with AttachmentCircuit labeled 'AttachTo'. SiteNW has a many-to-many relationship with Gateway labeled 'TerminatedBy'.](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg) - -``` - -classDiagram - class SiteNW { - <> - } - class Gateway { - <> - } - class AttachmentCircuit { - <> - } - SiteNW "1" -- "*" AttachmentCircuit : AttachTo - Gateway "1" -- "*" AttachmentCircuit : AttachTo - SiteNW "*" -- "*" Gateway : TerminatedBy - -``` - -UML Class Diagram titled 'ORAN.O2ims.Inventory' showing the 'Execution Environment Layer'. It contains three classes: SiteNW, Gateway, and AttachmentCircuit. SiteNW has a 1-to-many relationship with AttachmentCircuit labeled 'AttachTo'. Gateway has a 1-to-many relationship with AttachmentCircuit labeled 'AttachTo'. SiteNW has a many-to-many relationship with Gateway labeled 'TerminatedBy'. - -Figure 4.2.1.3.1.4.2.3-1 Execution Environment Layer View and networking related Information Object Classes - -#### 4.2.1.3.2 Inheritance - -##### 4.2.1.3.2.1 O2ims Inventory Inheritance - -This subclause depicts the inheritance relationships of inventory object classes. - -This subclause depicts the inheritance relationships. - -``` - -@startuml -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -Abstract Class Top <> -Abstract Class InfrastructureInventoryObject_ <> -Top <|-- InfrastructureInventoryObject_ -Top <|- InventorySubscription - -``` - -``` - -Class InventorySubscription <> - -Class Resource <> -Class ResourceType <> -Class ResourcePool <> -Class DeploymentManager <> -Class Location <> -Class "O-Cloud" <> -Class "O-CloudSite" <> - -InfrastructureInventoryObject_ <|-- Resource -InfrastructureInventoryObject_ <|-- ResourceType -InfrastructureInventoryObject_ <|-- ResourcePool -InfrastructureInventoryObject_ <|-- DeploymentManager -InfrastructureInventoryObject_ <|-- "O-Cloud" -InfrastructureInventoryObject_ <|-- Location -InfrastructureInventoryObject_ <|-- "O-CloudSite" - -@enduml - -``` - -![UML Class diagram showing inheritance hierarchy. Top class: Top. Subclasses of Top: InventorySubscription, InfrastructureInventoryObject_. Subclasses of InfrastructureInventoryObject_: ResourceType, ResourcePool, Location, O-Cloud, O-CloudSite, DeploymentManager, and Resource.](26d664119ad25250780f554633444e54_img.jpg) - -``` - -classDiagram - class Top["«InformationObjectClass» -Top"] - class InventorySubscription["«InformationObjectClass» -InventorySubscription"] - class InfrastructureInventoryObject_["«InformationObjectClass» -InfrastructureInventoryObject_"] - class ResourceType["«InformationObjectClass» -ResourceType"] - class ResourcePool["«InformationObjectClass» -ResourcePool"] - class Location["«InformationObjectClass» -Location"] - class O_Cloud["«InformationObjectClass» -O-Cloud"] - class O_CloudSite["«InformationObjectClass» -O-CloudSite"] - class DeploymentManager["«InformationObjectClass» -DeploymentManager"] - class Resource["«InformationObjectClass» -Resource"] - - Top <|-- InventorySubscription - Top <|-- InfrastructureInventoryObject_ - InfrastructureInventoryObject_ <|-- ResourceType - InfrastructureInventoryObject_ <|-- ResourcePool - InfrastructureInventoryObject_ <|-- Location - InfrastructureInventoryObject_ <|-- O_Cloud - InfrastructureInventoryObject_ <|-- O_CloudSite - InfrastructureInventoryObject_ <|-- DeploymentManager - InfrastructureInventoryObject_ <|-- Resource - -``` - -UML Class diagram showing inheritance hierarchy. Top class: Top. Subclasses of Top: InventorySubscription, InfrastructureInventoryObject\_. Subclasses of InfrastructureInventoryObject\_: ResourceType, ResourcePool, Location, O-Cloud, O-CloudSite, DeploymentManager, and Resource. - -**Figure 4.2.1.3.2.1-1 O2ims Inventory Intra-Namespace Inheritance** - -``` - -@startuml -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -Namespace ORAN.O2ims.Inventory { - Abstract Class InfrastructureInventoryObject_ <> -} - -Namespace ORAN.O2ims.Artifacts { - Class ArtifactResourceType <> - Class ArtifactResource <> - - ArtifactResourceType -d[hidden]- ArtifactResource -} -} - -``` - -``` - -Namespace ORAN.O2ims.Cluster { - Class ClusterResourceType <> - Class ClusterResource <> - Class NodeCluster <> - Class NodeClusterType <> -} - -Namespace ORAN.O2ims.Infrastructure { - Class InfrastructureResourceType <> - Class InfrastructureResource <> - - InfrastructureResourceType -d[hidden]- InfrastructureResource -} - -ORAN.O2ims.Inventory.InfrastructureInventoryObject_ <| -u- -ORAN.O2ims.Artifacts.ArtifactResourceType - -ORAN.O2ims.Inventory.InfrastructureInventoryObject_ <| -r- -ORAN.O2ims.Artifacts.ArtifactResource - -ORAN.O2ims.Inventory.InfrastructureInventoryObject_ <| -- -ORAN.O2ims.Cluster.ClusterResourceType - -ORAN.O2ims.Inventory.InfrastructureInventoryObject_ <| -- ORAN.O2ims.Cluster.ClusterResource - -ORAN.O2ims.Inventory.InfrastructureInventoryObject_ <| -- ORAN.O2ims.Cluster.NodeClusterType - -ORAN.O2ims.Inventory.InfrastructureInventoryObject_ <| -- ORAN.O2ims.Cluster.NodeCluster - -ORAN.O2ims.Inventory.InfrastructureInventoryObject_ <| -u- -ORAN.O2ims.Infrastructure.InfrastructureResourceType - -ORAN.O2ims.Inventory.InfrastructureInventoryObject_ <| -l- -ORAN.O2ims.Infrastructure.InfrastructureResource - -@enduml - -``` - -![UML Class Diagram showing inheritance relationships for InfrastructureInventoryObject_ across different namespaces.](90ddb84c323b956e2d50a54d3f870566_img.jpg) - -``` - -classDiagram - class ORAN.O2ims.Artifacts.ArtifactResourceType - class ORAN.O2ims.Artifacts.ArtifactResource - class ORAN.O2ims.Infrastructure.InfrastructureResourceType - class ORAN.O2ims.Infrastructure.InfrastructureResource - class ORAN.O2ims.Inventory.InfrastructureInventoryObject_ - class ORAN.O2ims.Cluster.NodeClusterType - class ORAN.O2ims.Cluster.NodeCluster - class ORAN.O2ims.Cluster.ClusterResource - class ORAN.O2ims.Cluster.ClusterResourceType - - ORAN.O2ims.Artifacts.ArtifactResourceType <|-- ORAN.O2ims.Inventory.InfrastructureInventoryObject_ - ORAN.O2ims.Artifacts.ArtifactResource <|-- ORAN.O2ims.Inventory.InfrastructureInventoryObject_ - ORAN.O2ims.Infrastructure.InfrastructureResourceType <|-- ORAN.O2ims.Inventory.InfrastructureInventoryObject_ - ORAN.O2ims.Infrastructure.InfrastructureResource <|-- ORAN.O2ims.Inventory.InfrastructureInventoryObject_ - ORAN.O2ims.Cluster.NodeClusterType <|-- ORAN.O2ims.Inventory.InfrastructureInventoryObject_ - ORAN.O2ims.Cluster.NodeCluster <|-- ORAN.O2ims.Inventory.InfrastructureInventoryObject_ - ORAN.O2ims.Cluster.ClusterResource <|-- ORAN.O2ims.Inventory.InfrastructureInventoryObject_ - ORAN.O2ims.Cluster.ClusterResourceType <|-- ORAN.O2ims.Inventory.InfrastructureInventoryObject_ - -``` - -UML Class Diagram showing inheritance relationships for InfrastructureInventoryObject\_ across different namespaces. - -Figure 4.2.1.3.2.1-2 O2ims Inventory Inter-Namespace Inheritance - -##### 4.2.1.3.2.2 Infrastructure Monitoring Inheritance - -This subclause depicts the inheritance relationships of alarm and performance. - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal - -``` - -``` - -skinparam style strictuml -hide members - -Abstract Class Top - -Top <|-- AlarmList -Top <|-- AlarmSubscription -Top <|-- LogQuery - -@enduml - -``` - -![UML Class Diagram showing inheritance from Top to AlarmList, AlarmSubscription, and LogQuery.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg) - -``` - -classDiagram - class Top { - <> - } - Top <|-- AlarmList - Top <|-- AlarmSubscription - Top <|-- LogQuery - -``` - -UML Class Diagram showing inheritance from Top to AlarmList, AlarmSubscription, and LogQuery. - -Figure 4.2.1.3.2.2-1 O2ims Alarm Inheritance - -Figure 4.2.1.3.2.2-2 depicts the inheritance relationships of Performance. - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -Abstract Class Top - -Top <|-r- PerformanceMeasurementStore -Top <|-l- PerformanceMeasurementJob -Top <|-u- PerformanceMeasurementJobChangeSubscription -Top <|-d- PerformanceSubscription - -@enduml - -``` - -![UML Class Diagram showing inheritance from Top to PerformanceMeasurementJob, PerformanceMeasurementStore, and PerformanceSubscription, with PerformanceMeasurementJobChangeSubscription inheriting from Top.](e29665b8abcea967ef289c6aff07ae4c_img.jpg) - -``` - -classDiagram - class Top { - <> - } - Top <|-- PerformanceMeasurementStore - Top <|-- PerformanceMeasurementJob - Top <|-- PerformanceMeasurementJobChangeSubscription - Top <|-- PerformanceSubscription - -``` - -UML Class Diagram showing inheritance from Top to PerformanceMeasurementJob, PerformanceMeasurementStore, and PerformanceSubscription, with PerformanceMeasurementJobChangeSubscription inheriting from Top. - -Figure 4.2.1.3.2.2-1 O2ims Performance Inheritance - -#### 4.2.1.4 Class Definitions - -##### 4.2.1.4.1 OCloud - -###### 4.2.1.4.1.1 Definition - -The OCloud represents an instance of an O-Cloud. For more information about O-Cloud, refer to the "O-RAN O2 General Aspects and Principles Specification", clause 3.1 [i.2]. - -###### 4.2.1.4.1.2 - -###### Attributes - -Table 4.2.1.4.1.2-1 Attributes Properties for OCloud - -| Attribute name | Data Type/Description | Properties | -|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| oCloudId | Data Type: string
Description: Identifier of the O-Cloud instance. Internally generated within an O-Cloud instance. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| globalCloudId | Data Type: string
Description: Identifier of the O-Cloud instance assigned by the SMO. This identifier is globally unique across O-Cloud instances known to the SMO. This value was provided by the SMO at cloud genesis and is stored in the O-Cloud IMS Inventory. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| name | Data Type: string
Description: Human readable name of the O-Cloud as identified by the SMO at cloud genesis. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| description | Data Type: string
Description: Human readable description of the O-Cloud as provided by the SMO at cloud genesis. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| infrastructureManagementServicesEndPoint | Data Type: string
Description: The URI root to all services provided by the O2ims interface. Inventory is one of these services. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| resourceTypes | Data Type: array
Description: List of Resource types. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 1
uniqueItems: True
items:

ResourceType | -| locations | Data Type: array
Description: List of locations where O-Cloud Sites are deployed or can be deployed. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 1
uniqueItems: True
items:
Location | -| oCloudSites | Data Type: array
Description: List of O-Cloud Sites that are known by the IMS | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | - -| Attribute name | Data Type/Description | Properties | -|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | and need to be exposed to the SMO for Homing. | x-isOrdered: False
minItems: 1
uniqueItems: True
items: OCloudSite | -| deploymentManagers | Data Type: array

Description: List of Deployment managers. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 1
uniqueItems: True
items:

DeploymentManager | -| smoRegistrationService | Data Type: string

Description: IP address endpoint or the URL of the SMO. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
format: uri | -| extensions | Data Type: array

Description: These are unspecified (not standardized) properties (keys) which are tailored by the vendor to extend the information provided about the O-Cloud. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:

AttributeValuePair | - -###### 4.2.1.4.1.3 Attribute constraints - -None. - -###### 4.2.1.4.1.4 State diagram - -None. - -#### 4.2.1.4.2 ResourceType - -##### 4.2.1.4.2.1 Definition - -The ResourceType represents a resource type in an O-Cloud. - -Resource types provide the categorization of O-Cloud Nodes as described in the O-RAN Cloud Architecture and Deployment Scenarios [i.3] specification. The values for these types are used to build the inventory and enable an authorized consumer to track resource changes over time. The O-Cloud provides a mechanism to discover the resource types with respective operations on resource types. - -###### 4.2.1.4.2.2 - -###### Attributes - -Table 4.2.1.4.2.2-1 Attributes Properties for ResourceType - -| Attribute name | Data Type/Description | Properties | -|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| resourceTypeId | Data Type: string
Description: Identifier of the resource type. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| name | Data Type: string
Description: Name of the resource type as identified by the cloud provider. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| description | Data Type: string
Description: Human readable description of the resource type. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| vendor | Data Type: string
Description: Name of the provider of the resource type. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | -| model | Data Type: string
Description: Information about the model of the resource type | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | -| version | Data Type: string
Description: Version or generation of the resource type. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | -| alarmDictionaryId | Data Type: string
Description: Identifier of the associated dictionary of alarms that can be generated by the resource type. If no alarms are reported against a resource of this resourceType then the alarmDictionaryId is not present. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| performanceDictionaryId | Data Type: string
Description: Identifier of the associated dictionary of performance measurements that can be collected for the resource type. If the resource of this resourceType does not provide any measurements then the performanceDictionaryId is not present. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| resourceKind | Data Type: string
Description: A value describing the "physicality" of the resource type. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False | - -| Attribute name | Data Type/Description | Properties | -|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | x-stateChangeNotification: False
enum:
- UNDEFINED
- PHYSICAL
- LOGICAL | -| resourceClass | Data Type: string
Description: A value describing the functional role within the cloud for the resource type.
The list of resource classes is not exhaustive, additional classes will be assessed on a case by case basis. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
enum:
- UNDEFINED
- COMPUTE
- NETWORKING
- STORAGE | -| extensions | Data Type: array
Description: These are unspecified (not standardized) properties (keys) which are tailored by the vendor to extend the information provided about the Resource Type. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:
AttributeValuePair | - -###### 4.2.1.4.2.3 Attribute constraints - -None. - -###### 4.2.1.4.2.4 State diagram - -None. - -##### 4.2.1.4.3 ResourcePool - -##### 4.2.1.4.3.1 Definition - -The ResourcePool represents a resource pool instance in an O-Cloud. - -The O-Cloud is a distributed cloud with resources placed in different locations. Those resources are organized into resource pools. There can be more than one resource pool for a given O-Cloud at the same physical location. However, each resource pool requires a different identity since the SMO will direct a deployment based on homing policies to a specific location. This is different than typical cloud deployments as location is key to meeting latency requirements, sometime to elements outside of the O-Cloud. - -NOTE 1: The identity of a resource pool cannot be tied to a specific resource within the pool as that resource may be replaced as part of the O-Cloud lifecycle. - -NOTE 2: The resource pool is described in the Cloud Architecture and Deployment Scenarios Technical Report [i.3] but may not be needed for exposure through the Information Model and subsequent O2 IMS interface. - -###### 4.2.1.4.3.2 Attributes - -**Table 4.2.1.4.3.2-1 Attributes Properties for ResourcePool** - -| Attribute name | Data Type/Description | Properties | -|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| resourcePoolId | Data Type: string
Description: Identifier of the resource pool. Locally unique within the scope of an O-Cloud instance. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| name | Data Type: string
Description: Human readable name of the resource pool. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| oCloudSiteId | Data Type: string
Description: Identifier of the O-Cloud site the resource pool is a part of. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| description | Data Type: string
Description: Human readable description of the resource pool. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| resources | Data Type: array
Description: List of resource IDs that are part of the resource pool. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 1
uniqueItems: True
items: string | -| extensions | Data Type: array
Description: These are unspecified (not standardized) properties (keys) which are tailored by the vendor to extend the information provided about the Resource Pool. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:

AttributeValuePair | - -###### 4.2.1.4.3.3 Attribute constraints - -None. - -###### 4.2.1.4.3.4 State diagram - -None. - -##### 4.2.1.4.4 Resource - -##### 4.2.1.4.4.1 Definition - -The Resource represents an instance of a resource in the O-Cloud. - -Resource pools are comprised of resources, wherein a specific instance of a resource can only be part of a single resource pool. - -Resources are of a specific resource type. The resource type of a given resource instance does not change over the lifetime of such a resource instance. - -The Resource is a Specialized Object that derives from a Generalized Object, the *InfrastructureInventoryObject\_*. The Resource inherits the attributes from the *InfrastructureInventoryObject\_*. - -###### 4.2.1.4.4.2 Attributes - -**Table 4.2.1.4.4.2-1 Attributes Properties for Resource** - -| Attribute name | Data Type/Description | Properties | -|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| resourceId | Data Type: string
Description: Identifier of the resource. Locally unique within the scope of an O-Cloud instance. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| description | Data Type: string
Description: Human readable description of the resource. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| resourceTypeId | Data Type: string
Description: Reference to the resource type of the resource. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| globalAssetId | Data Type: string
Description: Identifier or serial number of the resource, if available. It is required only if the resource has been identified during its addition to the cloud as a reportable asset in the SMO inventory. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
x-nullable: True | -| resourcePoolId | Data Type: string
Description: Reference to the resource pool that the resource is part of. | support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| elements | Data Type: array
Description: The resource might be composed of smaller resources or other resource instances of a different type. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items: Resource | - -| Attribute name | Data Type/Description | Properties | -|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| tags | Data Type: array

Description: Keywords describing or classifying the resource instance. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items: string | -| groups | Data Type: array

Description: Keywords denoting groups a resource belongs to. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items: string | -| extensions | Data Type: array

Description: These are unspecified (not standardized) properties (keys) which are tailored by the vendor to extend the information provided about the Resource. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:









AttributeVa
luePair | - -###### 4.2.1.4.4.3 Attribute constraints - -None. - -###### 4.2.1.4.4.4 State diagram - -None. - -##### 4.2.1.4.5 DeploymentManager - -##### 4.2.1.4.5.1 Definition - -The DeploymentManager represents an instance of a DMS in the O-Cloud. This class allows a client to discover the details about a DMS instance. This class provides a list of supported capabilities, and metrics for total capacity, current allocations, current reservations. For more information about DMS, refer to "O-RAN O2 General Aspects and Principles Specification, clause 1.3.1 "[i2]. - -The available capacity information supported by a DeploymentManager shall be calculated as Capacity - Allocated - Reserved. - -###### 4.2.1.4.5.2 Attributes - -**Table 4.2.1.4.5.2-1 Attributes Properties for DeploymentManager** - -| Attribute name | Data Type/Description | Properties | -|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| -| deploymentManagerId | Data Type: string

Description: Identifier of the deployment manager. Locally unique within the scope of an O-Cloud instance. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | - -![O-RAN ALLIANCE logo](6e3cdcccf7bacc5d43c63eebb58c7931_img.jpg) - -O-RAN.WG6.TS.O-Cloud-IM.0-R005-v06.00 - -| Attribute name | Data Type/Description | Properties | -|-------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| name | Data Type: string

Description: Human readable name of the deployment manager as identified by the cloud provider. |
x-support-qualifier:        M readOnly:                   True x-isInvariant:              False x-inventoryNotification:    True x-stateChangeNotification:  False
| -| description | Data Type: string

Description: Human readable description of the deployment manageras populated by the cloud provider. |
x-support-qualifier:        M readOnly:                   True x-isInvariant:              False x-inventoryNotification:    True x-stateChangeNotification:  False
| -| oCloudId | Data Type: string

Description: Reference to the O-Cloud associated to the deployment manager. |
x-support-qualifier:        M readOnly:                   True x-isInvariant:              True x-inventoryNotification:    True x-stateChangeNotification:  False format:                     uuid
| -| deploymentManagementServiceEndpoint | Data Type: string

Description: Endpoint to access the management services of the deployment manager. |
x-support-qualifier:        M readOnly:                   True x-isInvariant:              False x-inventoryNotification:    True x-stateChangeNotification:  False format:                     uri
| -| supportedLocations | Data Type: array

Description: List of globalLocationIDs that were assigned to resource pools that resources allocated to the service instance belong to. |
x-support-qualifier:        M readOnly:                   True x-isInvariant:              False x-inventoryNotification:    True x-stateChangeNotification:  False x-isOrdered:                False minItems:                   1 uniqueItems:               True items:                      string
| -| capabilities | Data Type: array

Description: Information about the capabilities supported by this set of deployment management services based on the resources allocated to the service instance. See Note. |
x-support-qualifier:        M x-isAlwaysPresent:          False readOnly:                   True x-isInvariant:              False x-inventoryNotification:    True x-stateChangeNotification:  False x-isOrdered:                False minItems:                   0 uniqueItems:               True items:                      AttributeValuePair
| -| capacity | Data Type: array

Description: Information about the available, allocated and reserved O-Cloud resources capacity allocated to the deployment manager. See Note. |
x-support-qualifier:        M x-isAlwaysPresent:          False readOnly:                   True x-isInvariant:              False x-inventoryNotification:    True x-stateChangeNotification:  False x-isOrdered:                False minItems:                   0 uniqueItems:               True items:                      AttributeValuePair
| -| extensions | Data Type: array

Description: These are |
x-support-qualifier:        M x-isAlwaysPresent:          False readOnly:                   True
| - -© 2026 by the O-RAN ALLIANCE e.V. Your use is subject to the copyright statement on the cover page of this specification. - -35 - - - -| Attribute name | Data Type/Description | Properties | -|----------------|----------------------------------------|------------| -| | provided then all events are reported. | | - -##### 4.2.1.4.6.3 Attribute constraints - -None. - -###### 4.2.1.4.6.4 State diagram - -None. - -#### 4.2.1.4.7 *InfrastructureInventoryObject\_* - -##### 4.2.1.4.7.1 Definition - -The *InfrastructureInventoryObject\_* is an abstract class which shall be implemented by one of its specific sub-classes. The *InfrastructureInventoryObject\_* does not have any common attributes. - -The *InfrastructureInventoryObject\_* is a Generalized Object for which specializations of this class, Specialized Object classes, can be included in a change notification. - -###### 4.2.1.4.7.2 Attributes - -This class does not provide any attributes. - -###### 4.2.1.4.7.3 Attribute constraints - -None. - -###### 4.2.1.4.7.4 State diagram - -None. - -#### 4.2.1.4.8 *InfrastructureInventoryEvent <>* - -##### 4.2.1.4.8.1 Definition - -The *InfrastructureInventoryEvent* is sent to consumers with an accepted subscription request and a filter criterion matching the content of the *InfrastructureInventoryEvent* attributes. This event can be triggered by change to an attribute in any subclass of the *InfrastructureInventoryObject\_* in which the property for x-inventoryNotification: or x-stateChangeNotification is “True”. - -NOTE: It is up to the protocol and data model specification to determine the one or various protocol operations enabling the notification service to invoke the specified callback procedure. - -**Table 4.2.1.4.8.1-1 InfrastructureInventoryEvent Requirements** - -| Referenced Specification | Requirement | Comment | -|------------------------------|---------------|-------------------------------| -| O-RAN.WG6.ORCH-USE-CASES [3] | REQ-ORC-GEN13 | Optional clarification | -| O-RAN.WG6.ORCH-USE-CASES [3] | REQ-ORC-O2-08 | | - -The information representing *InfrastructureInventoryEvent* shall follow the provisions indicated in table 4.2.1.4.8.2-1. - -##### 4.2.1.4.8.2 Attributes - -Table 4.2.1.4.8.2-1 Attributes Properties for InfrastructureInventoryEvent - -| Attribute name | Data Type/Description | Properties | -|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| consumerSubscriptionId | Data Type: string
Description: The consumer may provide its identifier for tracking, routing, or identifying the subscription used to report the event. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | -| notificationEventType | Data Type: string
Description: The type (CREATE, MODIFY, DELETE) of event being reported | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
format: enum
- CREATE
- MODIFY
- DELETE | -| objectRef | Data Type: string
Description: The resultant reference to the object on which the action occurred. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-nullable: True
format: url | -| priorObjectState | Data Type: InfrastructureInventoryObject
Description: If the Event type is 'MODIFY' or 'DELETE' this this field will be populated with a copy of the object prior to the event. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
x-nullable: True | -| postObjectState | Data Type: InfrastructureInventoryObject
Description: If the Event type is 'CREATE' or 'MODIFY' this this field will be populated with a copy of the object after the event. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
x-nullable: True | - -##### 4.2.1.4.8.3 Attribute constraints - -None. - -##### 4.2.1.4.8.4 State diagram - -None. - -#### 4.2.1.4.9 OCloudAvailableNotification <> - -##### 4.2.1.4.9.1 Definition - -Although the Genesis lifecycle event precedes the existence of the O2ims in the O-Cloud there is a minimal set of data expected to be provided from the SMO to the process. This information is retained in the O-Cloud and is used to register the - -O-Cloud with the SMO once it becomes usable. Data expected to be included with the callback URI in the genesis data is the globalCloudId, each globalLocationId, and each globalAssetId for infrastructure at those locations. Once enough of the O-Cloud is discovered, provisioned and is available for additional provisioning or workload deployments, the O-Cloud shall send the O-CloudAvailableNotification to the consumer (SMO), thus registering its InfrastructureManagementServiceEndPoint with the SMO. After receiving the notification, the SMO will interrogate the InfrastructureInventory APIs to account for corporate assets and discover the DMS service endpoints to allow workloads to be deployed. - -NOTE: It is up to the protocol and data model specification to determine the one or various protocol operations enabling the notification service to invoke the specified callback procedure. - -**Table 4.2.1.4.9.1-1 OCloudAvailableNotification Requirements** - -| Referenced Specification | Requirement | Comment | -|------------------------------|--------------|-------------------------------| -| O-RAN.WG6.ORCH-USE-CASES [3] | REQ-ORC-GEN5 | Optional clarification | - -The information representing OCloudAvailableNotification shall follow the provisions indicated in table 4.2.1.4.9.2-1. - -##### 4.2.1.4.9.2 Attributes - -**Table 4.2.1.4.9.2-1 Attributes Properties for OCloudAvailableNotification** - -| Attribute name | Data Type/Description | Properties | -|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| -| globalCloudId | Data Type: string
Description: Identifier of the O-Cloud instance assigned by the SMO. This identifier is globally unique across O-Cloud instances known to the SMO. This value was provided by the SMO at cloud genesis and is stored in the O-Cloud IMS Inventory. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| oCloudId | Data Type: string
Description: Identifier of the O-Cloud instance. Unique within an O-Cloud instance. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| IMS_EP | Data Type: string
Description: URL to the resource within the O-Cloud for other attributes. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uri | - -###### 4.2.1.4.9.3 Attribute constraints - -None. - -###### 4.2.1.4.9.4 State diagram - -None. - -##### 4.2.1.4.10 AlarmEventRecord <> - -##### 4.2.1.4.10.1 Definition - -The AlarmEventRecord represents a stored instance of an alarm detected within the O-Cloud Resources and stored by the IMS. - -The AlarmEventRecord can represent either a current active alarm or one that occurred in the past. Retention of an AlarmEventRecord is dependent on IMS configuration which would be set through an IMS Provisioning service. - -**Table 4.2.1.4.10.1-1 AlarmEventRecord Requirements** - -| Referenced Specification | Requirement | Comment | -|------------------------------|---------------|-------------------------------| -| O-RAN.WG6.ORCH-USE-CASES [3] | REQ-ORC-O2-17 | Optional clarification | -| O-RAN.WG6.ORCH-USE-CASES [3] | REQ-ORC-O2-73 | | - -##### 4.2.1.4.10.2 Attributes - -**Table 4.2.1.4.10.2-1 Attributes Properties for AlarmEventRecord** - -| Attribute name | Data Type/Description | Properties | -|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| alarmEventRecordId | Data Type: string
Description: Identifier of an entry in the AlarmEventRecord. Locally unique within the scope of an O-Cloud instance. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| objectTypeId | Data Type: string
Description: A reference to the type of resource which caused the alarm. This could be from any namespace (e.g., a resourceTypeId in the inventory namespace, or a nodeClusterTypeId in the cluster namespace). The objectClass attribute identifies which class of object is being referenced. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| objectId | Data Type: string
Description: A reference to the resource instance which caused the alarm. This could be from any namespace (e.g., a resourceId in the inventory namespace, or a nodeClusterId in the cluster namespace). The objectClass attributes identifies which class of object is being referenced. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| objectClass | Data Type: string
Description: The name of the class of the object being referenced by the objectId attribute. This includes the namespace and class name of the object being referenced to disambiguate it from other objects in the same namespace as well as objects in other namespaces. From this a client can infer the type of objectType referenced by the objectTypeId attribute. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
example:
"oran.o2ims.cluster.ClusterResource" | -| alarmDefinitionId | Data Type: string | x-support-qualifier: M | - -| Attribute name | Data Type/Description | Properties | -|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | Description: A reference to the Alarm Definition record in the Alarm Dictionary associated with the referenced Object Type. | readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | -| probableCauseId | Data Type: string
Description: A reference to the ProbableCause of the Alarm. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | -| eventType | Data Type: string
Description: Type of event of the Alarm. Values are defined as an enumeration, and their meanings are as defined in ITU-T X.733 [i.4] and ITU-T X.736 [i.5]. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
enum:
- COMMUNICATIONS_ALARM
- PROCESSING_ERROR_ALARM
- ENVIRONMENTAL_ALARM
- QOS_ALARM
- EQUIPMENT_ALARM
- INTEGRITY_ALARM
- INTEGRITY_VIOLATION
- OPERATIONAL_VIOLATION
- PHYSICAL_VIOLATION
- SECURITY_SERVICE_OR_MECHANISM_VIOLATION
- TIME_DOMAIN_VIOLATION
- OTHER

See NOTE. | -| alarmRaisedTime | Data Type: string
Description: This field is populated with a Date/Time stamp value when the AlarmEventRecord is created. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: date-time | -| alarmChangedTime | Data Type: string
Description: This field is populated with a Date/Time stamp value when any value of the AlarmEventRecord is modified. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
format: date-time | -| alarmClearedTime | Data Type: string
Description: This field is populated with a Date/Time stamp value when the alarm condition is cleared. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: True
format: date-time | -| alarmAcknowledgeTime | Data Type: string
Description: This field is populated with a Date/Time stamp value when the alarm condition is acknowledged. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: True
format: date-time | -| alarmAcknowledged | Data Type: boolean
Description: This is a Boolean | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False | - -| Attribute name | Data Type/Description | Properties | -|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | value defaulted to False. When a system acknowledges an alarm, it is then set to True. | x-stateChangeNotification: True
default: False | -| perceivedSeverity | Data Type: string

Description: This is an enumerated set of values which identify the perceived severity of the alarm. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
enum:
- CRITICAL
- MAJOR
- MINOR
- WARNING
- INDETERMINATE
- CLEARED | -| extensions | Data Type: array

Description: Unspecified (not standardized) properties (keys) which are tailored by the vendor or operator to extend the information provided about the O-Cloud Alarm. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:

AttributeValuePair | - -NOTE: The value of "OTHER" is for the case that the alarm cannot be assigned any other specified value. - -###### 4.2.1.4.10.3 Attribute constraints - -None. - -##### 4.2.1.4.10.4 State diagram - -None. - -##### 4.2.1.4.11 AlarmEvent <> - -###### 4.2.1.4.11.1 Definition - -The AlarmEvent represents a notification of an Alarm sent by the IMS to a registered Subscriber for a fault detected within an O-Cloud Resources. - -The AlarmEvent can represent either a new alarm, a change of occurrence, or state change of an existing alarm. - -**Table 4.2.1.4.11.1-1 AlarmEvent Requirements** - -| Referenced Specification | Requirement | Comment | -|------------------------------|---------------|-------------------------------| -| O-RAN.WG6.ORCH-USE-CASES [3] | REQ-ORC-O2-16 | Optional clarification | - -##### 4.2.1.4.11.2 Attributes - -**Table 4.2.1.4.11.2-1 Attributes Properties for AlarmEvent** - -| Attribute name | Data Type/Description | Properties | -|----------------|-----------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| -| globalCloudId | Data Type: string

Description: Identifier of the O-Cloud instance assigned by the SMO. This identifier is globally | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | - -| Attribute name | Data Type/Description | Properties | -|------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | unique across O-Cloud instances known to the SMO. This value was provided by the SMO at cloud genesis and is stored in the O-Cloud IMS Inventory. | format: uuid | -| consumerSubscriptionID | Data Type: string
Description: Identifier provided by the subscriber for event to subscription traceability within the consumer realm. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | -| alarmNotificationType | Data Type: string
Description: This is an enumerated set of values which identify the type of notification being sent to the subscriber. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
enum:
- NEW
- CHANGE
- CLEAR
- ACKNOWLEDGE | -| objectRef | Data Type: string
Description: This is a URL entry to the AlarmEventRecord for this notification within the AlarmList | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: url | -| alarmEventRecord | Data Type: AlarmEventRecord
Description: This is a copy of the AlarmEventRecord associated with this event preventing the need for the alarm consumer to do a read after the notification is received. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | - -###### 4.2.1.4.11.3 Attribute constraints - -None. - -###### 4.2.1.4.11.4 State diagram - -None. - -##### 4.2.1.4.12 AlarmSubscription - -##### 4.2.1.4.12.1 Definition - -The AlarmSubscription represents a consumer wishing to be notified when specified alarm conditions occur. - -The AlarmSubscription can be filtered by criteria based on the type of notification of fields of the AlarmEventRecord. - -**Table 4.2.1.4.12.1-1 Subscription Requirements** - -| Referenced Specification | Requirement | Comment | -|------------------------------|---------------|---------| -| O-RAN.WG6.ORCH-USE-CASES [3] | REQ-ORC-02-14 | | -| O-RAN.WG6.ORCH-USE-CASES [3] | REQ-ORC-02-15 | | - -##### 4.2.1.4.12.2 Attributes - -**Table 4.2.1.4.12.2-1 Attributes Properties for AlarmSubscription** - -| Attribute name | Data Type/Description | Properties | -|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| alarmSubscriptionId | Data Type: string
Description: Identifier of the subscription. Locally unique within the scope of an O-Cloud instance. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| consumerSubscriptionID | Data Type: string
Description: The consumer may provide its identifier for tracking, routing, or identifying the subscription used to report the event if a value was provided in the SubscriptionRequest. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | -| filter | Data Type: string
Description: Criteria for events which do not need to be reported or will be filtered by the subscription notification service. Therefore, if a filter is not provided then all events are reported. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
enum:
- NEW
- CHANGE
- CLEAR
- ACKNOWLEDGE | -| callback | Data Type: string
Description: The URI of the callback to which notifications are delivered to. | x-support-qualifier: M
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: url | - -##### 4.2.1.4.12.3 Attribute constraints - -None. - -##### 4.2.1.4.12.4 State diagram - -None. - -##### 4.2.1.4.13 AlarmList - -##### 4.2.1.4.13.1 Definition - -The AlarmList represents the configuration parameters of the AlarmList and the list of AlarmEventRecords currently maintained in the O-Cloud. - -**Table 4.2.1.4.13.1-1 AlarmList Requirements** - -| Referenced Specification | Requirement | Comment | -|------------------------------|-----------------|---------| -| O-RAN.WG6.ORCH-USE-CASES [3] | [REQ-ORC-02-74] | | -| O-RAN.WG6.ORCH-USE-CASES [3] | [REQ-ORC-02-98] | | - -##### 4.2.1.4.13.2 Attributes - -**Table 4.2.1.4.13.2-1 Attributes Properties for AlarmList** - -| Attribute name | Data Type/Description | Properties | -|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| retentionPeriod | Data Type: integer
Description: Specifies the number of days to retain cleared/acknowledge alarms in the AlarmList. Entries in the alarmEventRecords will be at least as long as the retentionPeriod but can be longer depending on the implementation of the purge feature. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-units: Days
minimum: 0 | -| alarmEventRecords | Data Type: array
Description: The alarmEventRecords provides the storage array for AlarmEventRecords that are active or have been cleared but not purged according to the implementation of the purge feature. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: True
minItems: 0
uniqueItems: True
items:
AlarmEventRecord | -| extensions | Data Type: array
Description: These are unspecified properties (keys and values) which can be tailored to control the behaviour of the Alarm List. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:
AttributeValuePair | - -##### 4.2.1.4.13.3 Attribute constraints - -None. - -###### 4.2.1.4.13.4 State diagram - -None. - -##### 4.2.1.4.14 PerformanceMeasurementStore - -##### 4.2.1.4.14.1 Definition - -The PerformanceMeasurementStore represents the O-Cloud internal store where PerformanceMeasurementRecord(s) are retained according to the retention policy of the O-Cloud based on the configured retention period. - -**Table 4.2.1.4.14.1-1 PerformanceMeasurementStore Requirements** - -| Referenced Specification | Requirement | Comment | -|------------------------------|------------------|---------| -| O-RAN.WG6.ORCH-USE-CASES [3] | [REQ-ORC-O2-100] | | - -The information representing the attributes of the PerformanceMeasurementStore follows the provisions indicated in table 4.2.1.4.14.2-1. - -##### 4.2.1.4.14.2 Attributes - -**Table 4.2.1.4.14.2-1 Attributes Properties for PerformanceMeasurementStore** - -| Attribute name | Data Type/Description | Properties | -|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| retentionPeriod | Data Type: integer
Description: The number in days (24 hours) that measurements will be retained. The exact timing of when measurements are deleted are implementation dependent. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
format: uInteger
x-units: days
minimum: 0 | -| measurements | Data Type: array
Description: List of PerformanceMeasurementRecord(s) collected and stored in the performance measurement store. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 0
uniqueItems: True
items:

PerformanceMeasurementRecord | -| extensions | Data Type: array
Description: These are unspecified properties (keys and values) which can be tailored to control the behaviour of the Performance Service. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:

AttributeValuePair | - -##### 4.2.1.4.14.3 Attribute constraints - -None. - -##### 4.2.1.4.14.4 State diagram - -None. - -##### 4.2.1.4.15 PerformanceMeasurementRecord <> - -##### 4.2.1.4.15.1 Definition - -The PerformanceMeasurementRecord represents a collected measurement in the PerformanceMeasurementStore. - -The information representing the attributes of the PerformanceMeasurementRecord follows the provisions indicated in table 4.2.1.4.15.2-1. - -##### 4.2.1.4.15.2 Attributes - -**Table 4.2.1.4.15.2-1 Attributes Properties for PerformanceMeasurementRecord** - -| Attribute name | Data Type/Description | Properties | -|------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| performanceMeasurementJobId | Data Type: string
Description: The job identifier assigned by the O-Cloud when a performance measurement job is created. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| resourceId | Data Type: string
Description: The resource identifier for the resource for which the collected measurement is against. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| performanceMeasurementDefinitionId | Data Type: string
Description: The Performance Dictionary definition identifier for the collected measurement. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | -| timeStamp | Data Type: string
Description: The date and time in which the measurement was collected. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
format: date-time | -| measurementValue | Data Type: Any type
Description: The value of the measurement collected. The ValueType represents a variety of types depending on the measurement type. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | -| isSuspect | Data Type: boolean
Description: This flag is set to True if anomalous behaviour was detected on the resource during the last collection interval. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
default: False | - -###### 4.2.1.4.15.3 Attribute constraints - -None. - -##### 4.2.1.4.15.4 State diagram - -None. - -##### 4.2.1.4.16 PerformanceMeasurementJob - -##### 4.2.1.4.16.1 Definition - -The PerformanceMeasurementJob represents a process established to collect measurements and place them in the PerformanceMeasurementStore. - -The information representing the attributes of the PerformanceMeasurementJob follows the provisions indicated in table 4.2.1.4.16.2-1. - -For attributes with x-inventoryNotification: set to True or x-stateChangeNotification set to True, the notification to be sent will be the PerformanceMeasurementJobChangeNotification. - -**Table 4.2.1.4.16.1-1 PerformanceMeasurementJob Requirements** - -| Referenced Specification | Requirement | Comment | -|------------------------------|---------------|-------------------------------| -| O-RAN.WG6.ORCH-USE-CASES [3] | REQ-ORC-02-31 | Optional clarification | -| O-RAN.WG6.ORCH-USE-CASES [3] | REQ-ORC-02-32 | | - -##### 4.2.1.4.16.2 Attributes - -**Table 4.2.1.4.16.2-1 Attributes Properties for PerformanceMeasurementJob** - -| Attribute name | Data Type/Description | Properties | -|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| performanceMeasurementJobId | Data Type: string
Description: Identifier of the performance job instance within the IMS. This value is assigned by the IMS when the job is created | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| consumerPerformanceJobId | Data Type: string
Description: Identifier optionally provided by the consumer for its purpose of managing performance jobs. This value could be the same across multiple instances of IMS performance job instances. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| state | Data Type: string
Description: The current state of the PerformanceMeasurementJob. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: True
enum:
- ACTIVE
- SUSPENDED
- DEPRECATED | -| collectionInterval | Data Type: integer
Description: The interval at which performance measurements will be collected and stored. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-units: Seconds
minimum: 0
default: 300 | -| resourceScopeCriteria | Data Type: array
Description: Key value pairs of | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False | - -| Attribute name | Data Type/Description | Properties | -|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | resource attributes which are used to select resources from which measures are to be collected.

This criterion determines, the value set for the Qualified Resource Types. | x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items: AttributeValuePair

example:
[
{"resourceTypeId", "[
"7c491f8f-7207-4c00-9b67-3d2ee8b008f0",
"31040dec-8106-44db-83bc-62e1d618ea17"
]"} ] | -| measurementSelectionCriteria | Data Type: array

Description: Key value pairs that identify the distinct set of measurements within the scope of a PerformanceMeasurementJob. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 1
uniqueItems: True
items: AttributeValuePair
example:
[
{"measurementGroup", "MemoryUsage"},
{"measurementName", "cpuAverageUtilization"}
] | -| status | Data Type: string

Description: The current status within the state. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: True
enum:
- RUNNING
- FAILED
- DEGRADED
- IDLE
- PENDING_DELETE | -| preinstalledJob | Data Type: boolean

Description: This is an indicator if the performance job was created for the IMS (True) or as the result of an IMS consumer request (False) | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | -| qualifiedResourceTypes | Data Type: array

Description: This list is computed from evaluation of the resourceScopeCriteria. The resulting qualifiedResourceTypes are the distinct set of ResourceTypes among those measuredResources.

This list of resource type UUIDs is used to qualify collectedMeasurements defined in the PM Dictionary of the qualified resource types. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items: uuid
example: '[
"7c491f8f-7207-4c00-9b67-3d2ee8b008f0",
"31040dec-8106-44db-83bc-62e1d618ea17"
]' | -| measuredResources | Data Type: array

Description: This is the historical list of resources measured by this job. Resources | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False | - -| Attribute name | Data Type/Description | Properties | -|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | added and deleted are kept track of for the life of the job. | minItems: 0
uniqueItems: True
items: MeasuredResource | -| collectedMeasurements | Data Type: array
Description: The historical list of measurements that are or have been collected by this job based on its resourceScopeCriteria and measurementSelectionCriteria over the life of the job. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items: CollectedMeasurement | -| extensions | Data Type: array
Description: These are unspecified (not standardized) properties (key/value) which extend the information about the Performance Measurement Job. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items: AttributeValuePair | - -##### 4.2.1.4.16.3 Attribute constraints - -Table 4.2.1.4.16.3-1 Attributes Constraints for PerformanceMeasurementJob - -| Name | Definition | -|----------------------------------------|---------------------------------------------------------------------------------| -| Status is RUNNING, FAILED, or DEGRADED | Condition: Job is in the ACTIVE state. | -| Status is IDLE | Condition: Job is in the SUSPENDED state. | -| Status is PENDING_DELETE | Condition: Job is in the DEPRECATED state. | -| WriteableExtensions | Condition: preInstalledJob is False then extensions can be created and updated. | -| ReadOnlyExtensions | Condition: preInstalledJob is True then extensions, if present are read only. | - -##### 4.2.1.4.16.4 State diagram - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -[*] --> ACTIVE : Create -ACTIVE : status in (RUNNING, FAILED, DEGRADED) -ACTIVE --> SUSPENDED : Suspend -SUSPENDED : status = IDLE -Note right of SUSPENDED - isSuspect will be True for - first collected measure on - Resume -End note -DEPRECATED : status = PENDING_DELETE -Note left of DEPRECATED - Job will remain deprecated until - the last performance measurement - referring to it is deleted from - the PM Store -End note -SUSPENDED --> ACTIVE : Resume -SUSPENDED -.-> DEPRECATED : Delete - -``` - -DEPRECATED -> [\*] - -@enduml - -![State & Status Diagram for PerformanceMeasurementJob. States: ACTIVE (status in (RUNNING, FAILED, DEGRADED)), SUSPENDED (status = IDLE), DEPRECATED (status = PENDING_DELETE). Transitions: Create to ACTIVE, Suspend to SUSPENDED, Resume from SUSPENDED to ACTIVE, Delete from SUSPENDED to DEPRECATED. Notes: 'isSuspect will be TRUE for first collected measure on Resume' and 'Job will remain deprecated until the last performance measurement referring to it is deleted from the PM Store'.](08f6ace0c83e7394657fa372b47aec04_img.jpg) - -``` - -stateDiagram-v2 - [*] --> ACTIVE : Create - ACTIVE --> SUSPENDED : Suspend - SUSPENDED --> ACTIVE : Resume - SUSPENDED --> DEPRECATED : Delete - DEPRECATED --> [*] - - state "ACTIVE (status in (RUNNING, FAILED, DEGRADED))" as ACTIVE - state "SUSPENDED (status = IDLE)" as SUSPENDED - state "DEPRECATED (status = PENDING_DELETE)" as DEPRECATED - -``` - -State & Status Diagram for PerformanceMeasurementJob. States: ACTIVE (status in (RUNNING, FAILED, DEGRADED)), SUSPENDED (status = IDLE), DEPRECATED (status = PENDING\_DELETE). Transitions: Create to ACTIVE, Suspend to SUSPENDED, Resume from SUSPENDED to ACTIVE, Delete from SUSPENDED to DEPRECATED. Notes: 'isSuspect will be TRUE for first collected measure on Resume' and 'Job will remain deprecated until the last performance measurement referring to it is deleted from the PM Store'. - -Figure 4.2.1.4.16.4-1 State & Status Diagram for PerformanceMeasurementJob - -##### 4.2.1.4.17 MeasuredResource <> - -##### 4.2.1.4.17.1 Definition - -The MeasuredResource represents a Resource that is or has been within the scope of a PerformanceMeasurementJob. - -The information representing the attributes of the MeasuredResource follows the provisions indicated in table 4.2.1.4.17.2-1. - -##### 4.2.1.4.17.2 Attributes - -Table 4.2.1.4.17.2-1 Attributes Properties for MeasuredResource - -| Attribute name | Data Type/Description | Properties | -|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| resourceTypeId | Data Type: string
Description: The resource identifier assigned by the O-Cloud when a performance measurement job is created. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| resourceId | Data Type: string
Description: The resource identifier for the resource for which the collected measurement is against. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| timeAdded | Data Type: array
Description: List of timestamps when the resource was added to the job. All resources shall have at least one timeAdded value. It could have multiple if changes caused a deletion and subsequent reinstatement to occur. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 1
uniqueItems: True
items: date-time | -| timeDeleted | Data Type: array
Description: List of timestamps when the resource was deleted from a job. Multiple values may be present if deletion occurred at different times. The effective period of the measurement | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 0
uniqueItems: True
items: date-time | - -| Attribute name | Data Type/Description | Properties | -|---------------------|------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | would be the times between a timeAdded and timeDeleted values. | | -| isCurrentlyMeasured | Data Type: boolean
Description: Indicates if the resource is currently being measured by the contained performance job. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
default: True | - -##### 4.2.1.4.17.3 Attribute constraints - -None. - -##### 4.2.1.4.17.4 State diagram - -None. - -##### 4.2.1.4.18 CollectedMeasurement <> - -##### 4.2.1.4.18.1 Definition - -The CollectedMeasurement represents a measurement associated with a specific ResourceType that is or has been within the scope of a PerformanceMeasurementJob. - -The information representing the attributes of the CollectedMeasurement follows the provisions indicated in table 4.2.1.4.18.2-1. - -##### 4.2.1.4.18.2 Attributes - -**Table 4.2.1.4.18.2-1 Attributes Properties for CollectedMeasurement** - -| Attribute name | Data Type/Description | Properties | -|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| resourceTypeId | Data Type: string
Description: The resource identifier assigned by the O-Cloud when a performance measurement job is created. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| performanceMeasurementDefinitionId | Data Type: string
Description: Identifier of the measurement definition with the PM Dictionary for the specific device type identified by the resourceTypeId. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| timeAdded | Data Type: array
Description: List of timestamps when the resource was added to the job. All measurements shall have at least one timeAdded value. It could have multiple if changes caused a deletion and subsequent reinstatement to occur. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 1
uniqueItems: True
items: date-time | - -| Attribute name | Data Type/Description | Properties | -|---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| timeDeleted | Data Type: array

Description: List of timestamps when the measurement was deleted from a job. Multiple values may be present if deletion occurred at different times. The effective period of the measurement would be the times between a timeAdded and timeDeleted values. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 0
uniqueItems: True
items: date-time | -| isCurrentlyMeasured | Data Type: boolean

Description: Indicates if the resource is currently being measured by the contained performance job. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
default: True | - -##### 4.2.1.4.18.3 Attribute constraints - -None. - -##### 4.2.1.4.18.4 State diagram - -None. - -##### 4.2.1.4.19 PerformanceMeasurementJobChangeSubscription - -##### 4.2.1.4.19.1 Definition - -The PerformanceMeasurementJobChangeSubscription represents a subscription for events to be notified such as when the scope of a PerformanceMeasurementJob changes either due to an update to its criteria or a change in inventory, or updates to other attributes (e.g. collection interval, state, status). - -The information representing the attributes of the PerformanceJobChangeSubscription follows the provisions indicated in table 4.2.1.4.19.2-1. - -##### 4.2.1.4.19.2 Attributes - -**Table 4.2.1.4.19.2-1 Attributes Properties for PerformanceMeasurementJobChangeSubscription** - -| Attribute name | Data Type/Description | Properties | -|-------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| -| performanceMeasurementJobChangeSubscriptionId | Data Type: string

Description: Identifier of the PerformanceMeasurementJobChangeSubscription which will generate this notification. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| consumerPerformanceMeasurementJobChangeSubscriptionId | Data Type: string

Description: The consumer identification value if provided on the PerformanceMeasurementJobChangeSubscription which will generate this notification. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| performanceChangesToNotify | Data Type: string | x-support-qualifier: M | - - - -| Attribute name | Data Type/Description | Properties | -|-------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| criptionId | Description: Identifier of the PerformanceMeasurementJobChangeSubscription. | readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| consumerPerformanceMeasurementJobChangeSubscriptionId | Data Type: string
Description: The consumer identification value if provided on the PerformanceMeasurementJobChangeSubscription. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | -| performanceMeasurementJobId | Data Type: string
Description: The UUID of the PerformanceMeasurementJob that incurred a change due to a change in scope criteria, a change to O-Cloud Infrastructure Inventory, a change to collection interval, a change to state and/or status, or a change to the extensions. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| objectRef | Data Type: string
Description: The URL of the service object which was modified. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
format: uri | -| typeOfChange | Data Type: string
Description: The enumerated value representing the type of changes to resources and/or measurements included in the notification. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
enum:
- ADD
- DELETE
- BOTH | -| resourceChangeDetails | Data Type: array
Description: If the subscription criteria indicates DELTA or COMPLETE extended information then all relevant added and/or deleted resources to the job are listed. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 0
uniqueItems: True
x-isOrdered: True
items:

MeasuredResource | -| measurementChangeDetails | Data Type: array
Description: If the subscription criteria indicates DELTA or COMPLETE extended information then all relevant added and/or deleted measurements of the performance measurement job are listed. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 0
uniqueItems: True
x-isOrdered: True
items: | - -| Attribute name | Data Type/Description | Properties | -|--------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | CollectedMeasurement | -| consumerPerformanceJobId | Data Type: string
Description: Identifier provided by the consumer for its purpose of managing performance jobs. This value could be the same across multiple instances of IMS performance job instances. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | -| collectionInterval | Data Type: integer
Description: The interval at which performance measurement will be collected and stored. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-nullable: True
x-units: Seconds
minimum: 0
default: 300 | -| state | Data Type: string
Description: The current state of the PerformanceMeasurementJob. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
enum:
- ACTIVE
- SUSPENDED
- DEPRECATED | -| status | Data Type: string
Description: The current status within the state. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
enum:
- RUNNING
- FAILED
- DEGRADED
- IDLE
- PENDING_DELETE | -| extensions | Data Type: array
Description: These are unspecified (not standardized) properties (key/value) which extend the information about the Performance Measurement Job | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:
AttributeValuePair | - -##### 4.2.1.4.20.3 Attribute constraints - -None. - -##### 4.2.1.4.20.4 State diagram - -None. - -##### 4.2.1.4.21 PerformanceSubscription - -##### 4.2.1.4.21.1 Definition - -The PerformanceSubscription represents the information required to establish the criteria by which a PerformanceMeasurementReport notification is to be generated and where to send that notification. - -**Table 4.2.1.4.21.1-1 PerformanceSubscription Requirements** - -| Referenced Specification | Requirement | Comment | -|------------------------------|---------------|-------------------------------| -| O-RAN.WG6.ORCH-USE-CASES [3] | REQ-ORC-O2-37 | Optional clarification | -| O-RAN.WG6.ORCH-USE-CASES [3] | REQ-ORC-O2-38 | | - -The information representing the attributes of the PerformanceSubscription follows the provisions indicated in table 4.2.1.4.21.2-1. - -##### 4.2.1.4.21.2 Attributes - -**Table 4.2.1.4.21.2-1 Attributes Properties for PerformanceSubscription** - -| Attribute name | Data Type/Description | Properties | -|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| performanceSubscriptionId | Data Type: string
Description: Identifier of the performance subscription instance within the IMS. This value is assigned by the IMS when the subscription is created. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| consumerPerformanceSubscriptionId | Data Type: string
Description: Identifier optionally provided by the consumer for its purpose of managing performance data. This value could be the same across multiple instances of IMS subscription instances. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | -| subscriptionCriteria | Data Type: PerformanceSubscriptionCriteria
Description: This is the criteria which will apply to this subscription. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | -| reportDeliveryMechanism | Data Type: string | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
enum:
- NOTIFICATION
- FILE
- STREAM | - -| Attribute name | Data Type/Description | Properties | -|-------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

Description: Enumerated set of reporting mechanisms for delivery of the data identified by the PerformanceSubscription which are identified as:

NOTIFICATION: Call the callback with the data at the specified intervals providing the data, e.g., in JSON format

FILE: generate a file, e.g., formatted in XML to be collected and call the callback with the filename whenever one is generated.

STREAM: Session will remain open and continue to send the data in a streaming format, e.g., Google Protocol Buffers (GPB), at the specified intervals until the session or subscription is terminated.

| | -| remoteFileLocation |

Data Type: string

Description: When the reportFormat is FILE this field is populated with the URL to the remote directory where the service is expected to push the requested performance files to a remote files system. If the reportFormat is not FILE, the field is empty or not present.

|
x-support-qualifier:      M x-isAlwaysPresent:        False x-isInvariant:            False x-inventoryNotification:  False x-stateChangeNotification: False Format:                  uri
| -| callback |

Data Type: string

Description: The callback to send responses for modes NOTIFICATION, or the file notification for FILE. The field is not required if mode is STREAM.

|
x-support-qualifier:      M x-isAlwaysPresent:        False x-isInvariant:            False x-inventoryNotification:  False x-stateChangeNotification: False Format:                  uri
| -| measurementReportingFrequency |

Data Type: PerformanceReportingFrequency

Description: The frequency that specified measurements are to be reported.

|
x-support-qualifier:      M x-isInvariant:            False x-inventoryNotification:  False x-stateChangeNotification: False
| - -##### 4.2.1.4.21.3            Attribute constraints - -None. - -##### 4.2.1.4.21.4 State diagram - -None. - -#### 4.2.1.4.22 PerformanceReportingFrequency <> - -##### 4.2.1.4.22.1 Definition - -The PerformanceReportingFrequency represents the frequency that specified measurements are to be reported. - -The information representing the attributes of the PerformanceReportingFrequency follows the provisions indicated in table 4.2.1.4.22.2-1. - -##### 4.2.1.4.22.2 Attributes - -**Table 4.2.1.4.22.2-1 Attributes Properties for PerformanceReportingFrequency** - -| Attribute name | Data Type/Description | Properties | -|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| subscriptionMode | Data Type: string
Description: An enumerated set of values which will identify the mode in which data is reported. The valid values are as follows:
TARGET_DEFINED:
Producer of the PM data decides if ON_CHANGE or SAMPLE is more optimal.
ON_CHANGE: Value is reported as soon as the PM Job collects it.
SAMPLE: Value is reported at the reportInterval period. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
enum:
- TARGET_DEFINED
- ON_CHANGE
- SAMPLE | -| reportInterval | Data Type: integer
Description: This is the reporting interval for the data, it is an unsigned integer representing the number of milliseconds between reports. If the reportInterval is lower than the service can provide the subscription shall return an error indicating such. If the value is set to zero (0) then the service will use its lowest supported value for the reportInterval. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-nullable: True
minimum: 0
default: 300
x-units: seconds | -| supressRedundant | Data Type: boolean
Description: This flag identifying if SAMPLE values that have not changed shall (False) or shall Not (True) be transmitted. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
default: False | -| heartbeatInterval | Data Type: integer
Description: When the suppressRedundant is set to (True), if heartbeatInterval is a | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | - -| Attribute name | Data Type/Description | Properties | -|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------| -| | non-zero value then a duplicate value will be sent at least once per heartbeatInterval. The value shall be zero (0) or a value greater than or equal to the reportInterval. | minimum: 0
default: 0
x-units: seconds | - -##### 4.2.1.4.22.3 Attribute constraints - -None. - -###### 4.2.1.4.22.4 State diagram - -None. - -##### 4.2.1.4.23 PerformanceSubscriptionCriteria <> - -##### 4.2.1.4.23.1 Definition - -The PerformanceSubscriptionCriteria represents the information required to establish which measurements for which resource shall be included in a PerformanceMeasurementReport. - -The information representing the attributes of the PerformanceSubscriptionCriteria follows the provisions indicated in table 4.2.1.4.23.2-1. - -##### 4.2.1.4.23.2 Attributes - -Table 4.2.1.4.23.2-1 Attributes Properties for PerformanceSubscriptionCriteria - -| Attribute name | Data Type/Description | Properties | -|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| jobCriteria | Data Type: array
Description: The list of performanceMeasurementJobId of interest.
See note. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 0
uniqueItems: True
items: string | -| resourceTypeCriteria | Data Type: array
Description: Key/Value list of criteria compared to Resource Type data. The Key shall correspond to the specified attribute names of the ResourceType (see clause 4.2.1.4.2.2), and the Value shall indicate the value of that attribute.
See note. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 0
uniqueItems: True
items: AttributeValuePair | -| resourceCriteria | Data Type: array
Description: Key/Value list of criteria compared to Resource data. The Key shall correspond to the specified attribute names of the Resource (see clause 4.2.1.4.4.2), and the Value shall indicate the value of that | x-isAlwaysPresent: False
x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 0
uniqueItems: True
items: AttributeValuePair | - -| Attribute name | Data Type/Description | Properties | -|---------------------|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | attribute.

See note. | luePair | -| measurementCriteria | Data Type: array

Description: The list of performanceMeasureDefinitionId [2] of interest.

See note. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 0
uniqueItems: True
items: string | - -NOTE: At least one of the attributes shall be included. If more than one is included, the criteria selection operates as an “inclusion” (i.e., AND-operator). - -##### 4.2.1.4.23.3 Attribute constraints - -None. - -##### 4.2.1.4.23.4 State diagram - -None. - -##### 4.2.1.4.24 PerformanceMeasurementReport <> - -##### 4.2.1.4.24.1 Definition - -The PerformanceMeasurementReport notification represents the information required to define the scope of the JobReports being sent in the notification. - -**Table 4.2.1.4.24.1-1 PerformanceMeasurementReport Requirements** - -| Referenced Specification | Requirement | Comment | -|------------------------------|---------------|-------------------------------| -| O-RAN.WG6.ORCH-USE-CASES [3] | REQ-ORC-O2-39 | Optional clarification | - -The information representing the attributes of the PerformanceMeasurementReport follows the provisions indicated in table 4.2.1.4.24.2-1. - -##### 4.2.1.4.24.2 Attributes - -**Table 4.2.1.4.24.2-1 Attributes Properties for PerformanceMeasurementReport** - -| Attribute name | Data Type/Description | Properties | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| -| globalCloudId | Data Type: string

Description: Identifier of the O-Cloud instance assigned by the SMO. This identifier is globally unique across O-Cloud instances known to the SMO. This value was provided by the SMO at cloud genesis and is stored in the O-Cloud IMS Inventory. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| notificationTime | Data Type: string

Description: The date and time that the notification was sent. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | - -| Attribute name | Data Type/Description | Properties | -|-----------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | format: date-time | -| performanceSubscriptionId | Data Type: string
Description: Identifier of the performance subscription instance within the IMS. This value is assigned by the IMS when the job is created. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| consumerPerformanceSubscriptionId | Data Type: string
Description: Identifier optionally provided by the consumer for its purpose of managing performance data. This value could be the same across multiple instances of IMS subscription instances. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | -| jobReports | Data Type: array
Description: The list of performance reports by jobId. A single subscription can subscribe to measurements collected by multiple jobs. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 1
uniqueItems: True
items: JobReport | - -###### 4.2.1.4.24.3 Attribute constraints - -None. - -###### 4.2.1.4.24.4 State diagram - -None. - -##### 4.2.1.4.25 JobReport <> - -##### 4.2.1.4.25.1 Definition - -The JobReport provides the list of performance reports generated from corresponding PerformanceMeasurementJobs. A single subscription can be used to subscribe to measurements collected by multiple PerformanceManagementJobs. The data from the PerformanceMeasurementJobs are aggregated into a single report per PerformanceSubscription. - -The information representing the attributes of the JobReport follows the provisions indicated in table 4.2.1.4.25.2-1. - -##### 4.2.1.4.25.2 Attributes - -**Table 4.2.1.4.25.2-1 Attributes Properties for JobReport** - -| Attribute name | Data Type/Description | Properties | -|------------------|-------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| -| performanceJobId | Data Type: string
Description: The UUID of the PerformanceMeasurementJob from which collected measurements are reported. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| consumerJobId | Data Type: string
Description: Identifier provided | x-support-qualifier: M
readOnly: True | - -| Attribute name | Data Type/Description | Properties | -|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | by the consumer for its purpose of managing performance jobs. This value could be the same across multiple instances of IMS performance job instances. | x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | -| measuredResources | Data Type: array
Description: The list of collected measurements for each Resource within the scope of the subscription to be included in this PerformanceMeasurementReport. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 1
items: ResourceReport | - -##### 4.2.1.4.25.3 Attribute constraints - -None. - -##### 4.2.1.4.25.4 State diagram - -None. - -##### 4.2.1.4.26 ResourceReport <> - -##### 4.2.1.4.26.1 Definition - -The ResourceReport dataType represents the information required to identify the resource for which a set of measurements are being reported in the notification. - -The information representing the attributes of the ResourceReport follows the provisions indicated in table 4.2.1.4.26.2-1. - -##### 4.2.1.4.26.2 Attributes - -**Table 4.2.1.4.26.2-1 Attributes Properties for ResourceReport** - -| Attribute name | Data Type/Description | Properties | -|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| resourceId | Data Type: string
Description: The UUID of the Resource as specified in Infrastructure Inventory. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| measurementValues | Data Type: array
Description: The list of collected measurements for the Resource within the subscription included in this PerformanceMeasurementReport. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 1
uniqueItems: True
items: MeasurementValue | - -##### 4.2.1.4.26.3 Attribute constraints - -None. - -##### 4.2.1.4.26.4 State diagram - -None. - -##### 4.2.1.4.27 MeasurementValue <> - -##### 4.2.1.4.27.1 Definition - -The MeasurementValue dataType represents the information about a collected measurement and its value to be included in a notification. - -The information representing the attributes of the MeasurementValue follows the provisions indicated in table 4.2.1.4.27.2-1. - -##### 4.2.1.4.27.2 Attributes - -**Table 4.2.1.4.27.2-1 Attributes Properties for MeasurementValue** - -| Attribute name | Data Type/Description | Properties | -|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| performanceMeasurementId | Data Type: string
Description: Based on encoding this value can be either a string consisting of the performanceMeasureName of the MeasurementDefinition in the Performance Dictionary for the Resource Type or an unsigned integer consisting of the performanceMeasurementId of the MeasurementDefinition. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | -| measurementCollectionTime | Data Type: string
Description: If present, this is the value that is added to the PerformanceMeasurementStore. When omitted then the notificationTime is assumed to the time the value was added to the PerformanceMeasurementStore as would be the case if the subscriptionMode equated to ON_CHANGE. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
format: date-time | -| measurementValue | Data Type: Any type
Description: This is the actual value of the measurement which varies in type from measurement to measurement. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | -| isSuspect | Data Type: boolean
Description: This flag is set to True if anomalous behavior was detected on the resource between this measurement value and a prior measurement value. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
default: False | - -##### 4.2.1.4.27.3 Attribute constraints - -None. - -##### 4.2.1.4.27.4 State diagram - -None. - -##### 4.2.1.4.28 NotifyFileReady <> - -##### 4.2.1.4.28.1 Definition - -The NotifyFileReady notification represents the information about one (1) or more files to be made available to a subscriber when the reportFormat of a PerformanceSubscription is FILE or a LogQuery when a callback is supplied. This notification only makes the consumer aware of the file and does not predicate delivery of the file (push or pull). - -The information representing the attributes of the NotifyFileReady follows the provisions indicated in table 4.2.1.4.28.2-1. - -##### 4.2.1.4.28.2 Attributes - -**Table 4.2.1.4.28.2-1 Attributes Properties for NotifyFileReady** - -| Attribute name | Data Type/Description | Properties | -|------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| globalCloudId | Data Type: string
Description: Identifier of the O-Cloud instance assigned by the SMO. This identifier is globally unique across O-Cloud instances known to the SMO. This value was provided by the SMO at cloud genesis and is stored in the O-Cloud IMS Inventory. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| subscriptionId | Data Type: string
Description: When the notification is created due to a PerformanceSubscription this attribute will contain the identifier of the performanceSubscriptionId for this notification. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| consumerSubscriptionId | Data Type: string
Description: When the notification is created due to a PerformanceSubscription this attribute will contain the identifier provided by the consumer for its purpose of managing performance data and may be included in the PerformanceSubscription.

If the notification is due to a logQuery request this attribute shall provide the consumerLogRequestId when provided on the request to allow the consumer to correlate it to the original request. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | -| eventTime | Data Type: string
Description: The date and time that the notification was issued. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
format: date-time | - -| Attribute name | Data Type/Description | Properties | -|----------------|-------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| fileInfoList | Data Type: array
Description: The list of information about one or more files included in this notification. |
x-support-qualifier:        M readOnly:                   True x-isInvariant:              False x-inventoryNotification:     False x-stateChangeNotification:  False minItems:                   1 uniqueItems:                True items:                      FileInfo
| - -##### 4.2.1.4.28.3 Attribute constraints - -None. - -##### 4.2.1.4.28.4 State diagram - -None. - -##### 4.2.1.4.29 FileInfo <> - -##### 4.2.1.4.29.1 Definition - -The FileInfo dataType represents information about one or more generated files collected by a producer and which are now available to a consumer. - -The information representing the attributes of the FileInfo follows the provisions indicated in table 4.2.1.4.29.2-1. - -##### 4.2.1.4.29.2 Attributes - -**Table 4.2.1.4.29.2-1 Attributes Properties for FileInfo** - -| Attribute name | Data Type/Description | Properties | -|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| fileLocation | Data Type: string
Description: Location of the file |
x-support-qualifier:        M readOnly:                   True x-isInvariant:              False x-inventoryNotification:     False x-stateChangeNotification:  False format:                     uri
| -| fileSize | Data Type: integer
Description: Size of the file, unit is byte |
x-support-qualifier:        M readOnly:                   True x-isInvariant:              False x-inventoryNotification:     False x-stateChangeNotification:  False format:                     int32 minimum:                    0 x-units:                    bytes
| -| fileReadyTime | Data Type: string
Description: Date and time when the file was last closed and made available by the producer. The file content will not be changed any more |
x-support-qualifier:        M readOnly:                   True x-isInvariant:              False x-inventoryNotification:     False x-stateChangeNotification:  False format:                     date-time
| -| fileExpirationTime | Data Type: string
Description: Date and time after which the file may be deleted. |
x-support-qualifier:        M readOnly:                   True x-isInvariant:              False x-inventoryNotification:     False x-stateChangeNotification:  False format:                     date-time
| - -| Attribute name | Data Type/Description | Properties | -|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| fileCompression | Data Type: string

Description: If compression is applied to the file, the name of the compression algorithm used for compressing the file. |
x-support-qualifier:      M x-isAlwaysPresent:        False readOnly:                 True x-isInvariant:            True x-inventoryNotification:  False x-stateChangeNotification: False
| -| fileDataType | Data Type: string

Description: An enumerated set of values identifying the type of data contained in the file. The valid set of values are described as follows:
PERFORMANCE: The file contains a PerformanceMeasurementReport.

ANALYTIC: The file contains analytic data.

LOG: The file contains log entries identified in a logQuery request. |
x-support-qualifier:      M readOnly:                 True x-isInvariant:            True x-inventoryNotification:  False x-stateChangeNotification: False enum:   - PERFORMANCE   - ANALYTIC   - LOG
| - -###### 4.2.1.4.29.3 Attribute constraints - -None. - -##### 4.2.1.4.29.4 State diagram - -None. - -##### 4.2.1.4.30 Location - -###### 4.2.1.4.30.1 Definition - -The Location represents an instance of a Location where an O-Cloud Site may be available. - -###### 4.2.1.4.30.2 Attributes - -**Table 4.2.1.4.30.2-1 Attributes Properties for Location** - -| Attribute name | Data Type/Description | Properties | -|------------------|----------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| globalLocationId | Data Type: string

Description: Identifier of the location as defined by the SMO. |
x-support-qualifier:      M readOnly:                 True x-isInvariant:            True x-inventoryNotification:  False x-stateChangeNotification: False
| -| name | Data Type: string

Description: Human readable name of the location as defined by the SMO. |
x-support-qualifier:      M readOnly:                 True x-isInvariant:            False x-inventoryNotification:  True x-stateChangeNotification: False
| -| description | Data Type: string

Description: Human readable description of the location as |
x-support-qualifier:      M readOnly:                 True x-isInvariant:            False x-inventoryNotification:  True x-stateChangeNotification: False
| - -| Attribute name | Data Type/Description | Properties | -|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | defined by the SMO. | | -| oCloudId | Data Type: string
Description: Reference to the O-Cloud available at the location. | support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| oCloudSiteIds | Data Type: array
Description: List of O-Cloud Site identifiers referencing the O-Cloud Sites available at the location. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items: string | -| coordinate | Data Type: string
Description: The latitude and longitude of the location (shall be supplied if a postal address not provided). | support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | -| address | Data Type: string
Description: Postal address of the facility (shall be supplied if a coordinate is not provided). | support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | -| extensions | Data Type: array
Description: These are unspecified (not standardized) properties (keys) which are tailored by the vendor to extend the information provided about the location. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:
AttributeValuePair | - -###### 4.2.1.4.30.3 Attribute constraints - -None. - -###### 4.2.1.4.30.4 State diagram - -None. - -##### 4.2.1.4.31 OCloudSite - -##### 4.2.1.4.31.1 Definition - -The OCloudSite represents an O-Cloud Site instance in an O-Cloud, as described in the O-RAN Cloud Architecture and Deployment Scenarios specification [i.3]. - -###### 4.2.1.4.31.2 - -###### Attributes - -Table 4.2.1.4.31.2-1 Attributes Properties for OCloudSite - -| Attribute name | Data Type/Description | Properties | -|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| oCloudSiteId | Data Type: string
Description: Identifier of the O-Cloud site. Locally unique within the scope of an O-Cloud instance. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| locationId | Data Type: string
Description: Reference to location where the O-Cloud site is deployed at. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| name | Data Type: string
Description: Human readable name of the O-Cloud site as identified by the cloud provider. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| description | Data Type: string
Description: Human readable description of the O-Cloud site as provided by the cloud provider. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| oCloudId | Data Type: string
Description: Reference to the O-Cloud of which the O-Cloud site is part. | support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| resourcePools | Data Type: array
Description: List of resource pools that are part of the O-Cloud site. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 1
uniqueItems: True
items:

ResourcePool | -| extensions | Data Type: array
Description: These are unspecified (not standardized) properties (keys) which are tailored by the vendor to extend the information provided about the O-Cloud site. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:

AttributeValuePair | - -###### 4.2.1.4.31.3 Attribute constraints - -None. - -##### 4.2.1.4.31.4 State diagram - -None. - -##### 4.2.1.4.32 LogQuery - -##### 4.2.1.4.32.1 Definition - -The LogQuery represents a request for O-Cloud log files for specific resources or resource of specific ResourceTypes to be collected and made available to the requestor. - -###### 4.2.1.4.32.2 Attributes - -Table 4.2.1.4.32.2-1 Attributes Properties for LogQuery - -| Attribute name | Data Type/Description | Properties | -|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| logType | Data Type: string

Description: This identifies the type of log(s) to be collected. The exact list of valid log types to be discovered via a log capability discovery. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | -| dateRanges | Data Type: array

Description: list of date ranges that log data is to be extracted and placed into the log file for collection. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 1
items: DateRange | -| eventTypes | Data Type: array

Description: List of event types that are to be extracted and placed in the log file for collection. If the attribute is not provided, all event types are selected.

The exact list of valid event types are to be discovered via a log capability discovery. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
minItems: 0
items: string | -| resources | Data Type: array

Description: list of resource selection criteria to identify which resources are in scope for the query. If the attribute is not provided, all resources are selected. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 0
items:

AttributeValuePair | -| resourceTypes | Data Type: array

Description: list of resourceType selection criteria to identify which resources matching the resourceTypes are | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 0
items: | - -| Attribute name | Data Type/Description | Properties | -|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | in scope for the query. If the attribute is not provided, all resourceTypes are selected. | AttributeValuePair | -| logLevels | Data Type: array
Description: List of logging levels that are to be extracted and placed in the log file for collection. If the attribute is not provided, all logging levels are selected.

The log levels specified in Clause 6.2.1, Table 2 of IETF RFC 5424 [5] shall be supported by the O-Cloud instance. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
minItems: 0
items: string | -| remoteFileLocation | Data Type: string
Description: When the service is expected to push to a remote file system, this field is populated with the URL to the remote directory, otherwise the field is empty or not present. | support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
format: uri | -| callback | Data Type: string
Description: The URL of the callback to which asynchronous notifications are delivered to. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
format: uri | -| consumerLogRequestId | Data Type: string
Description: Identifier optionally provided by the consumer for its purpose of tracking a request for log data. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | - -###### 4.2.1.4.32.3 Attribute constraints - -None. - -##### 4.2.1.4.32.4 State diagram - -None. - -##### 4.2.1.4.33 DateRange <> - -##### 4.2.1.4.33.1 Definition - -The DateRange represent a start and end date and time value to indicate a span of time. - -##### 4.2.1.4.33.2 Attributes - -Table 4.2.1.4.33.2-1 Attributes Properties for DateRange - -| Attribute name | Data Type/Description | Properties | -|----------------|--------------------------|------------------------| -| startDateTime | Data Type: string | x-support-qualifier: M | - -| Attribute name | Data Type/Description | Properties | -|----------------|------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------| -| startDateTime | Description: This identifies the start of a time range. | x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
format: date-time | -| endDateTime | Data Type: string
Description: This identifies the end of a time range. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
format: date-time | - -##### 4.2.1.4.33.3 Attribute constraints - -**Table 4.2.1.4.33.3-2 Attributes Constraints for DateRange** - -| Name | Definition | -|--------------------|-------------------------------------------------------------------------| -| START_PRECEDES_END | Condition: startDateTime shall chronologically precede the endDateTime. | - -##### 4.2.1.4.33.4 State diagram - -None. - -### 4.2.2 Namespace: ORAN.O2ims.Artifacts - -#### 4.2.2.1 Namespace Overview - -The O-RAN O2ims Artifacts namespace defines the classes and their attributes which are directly exposed to the consumer (SMO) via its O2 IMS Interface. - -This namespace is used for the O-Cloud artifacts e.g. Cluster Templates, Initial Configuration Sets, OS/SW/FW, etc. that e.g. The O-Cloud artifacts can be used for configuring O-Cloud Resources from the Inventory and Cluster namespaces. The artifacts are not consumed when they are used and can be referenced in the Inventory, Cluster and Provisioning structures. - -#### 4.2.2.2 Imported and associated information entities - -##### 4.2.2.2.1 Imported information entities and local labels - -Information entities imported into the model are also elements of the namespace and therefore shall remain unique within the namespace. - -**Table 4.2.2.2.1-1 Imported Entities** - -| Label reference | Local label | -|-----------------|-------------| -| | | -| | | - -##### 4.2.2.2.2 Associated information entities and local labels - -Information entities referenced in the model through an association which may be extended and overloaded with a new entity of the same name within the namespace are listed in the associated entities table. - -Table 4.2.2.2.2-1 Associated Entities - -| Label reference | Local label | -|-------------------------------------------|--------------------------------| -| 4.2.1.2.1 Top | Top | -| 4.2.1.4.7, InfrastructureInventoryObject_ | InfrastructureInventoryObject_ | - -#### 4.2.2.3 Class Diagram - -##### 4.2.2.3.1 Relationships - -###### 4.2.2.3.1.1 Description - -This clause depicts the set of classes (e.g. IOCs) that encapsulates the information relevant for the O-RAN Cloud (O-Cloud). This clause provides an overview of the relationships between relevant classes in UML. Subsequent clauses provide more detailed specification of various aspects of these classes. The UML Class diagram depicts a view of the namespace maintaining a defined focus so as not to overcrowd a single diagram trying to depict all relationships within the namespace. - -###### 4.2.2.3.1.2 ORAN.O2ims.Artifacts Intra-Namespace Relationships - -``` -@startuml -Namespace ORAN.O2ims.Artifacts #Magenta { -Skinparam BorderColor Red -Skinparam ArrowColor Black -Hide Members -Hide Circle - -Class ArtifactResourceType <> { - artifactResourceTypeId UUID - name String - resource String - description String - extensions[] KeyValuePair -} - -Class ArtifactResource <> { - artifactResourceId UUID - name String - description String -} - -ArtifactResource --> ArtifactResourceType : isOfType -ArtifactResource --> ArtifactResource : ReferenceOrUse - -@enduml -``` - -![UML Class Diagram showing two classes within the ORAN.O2ims.Artifacts namespace. The top class is ArtifactResource (stereotype: InformationObjectClass) and the bottom class is ArtifactResourceType (stereotype: InformationObjectClass). A directed association arrow points from ArtifactResource to ArtifactResourceType with the label 'isOfType'. A self-association arrow on ArtifactResource points back to itself with the label 'ReferenceOrUse'.](443ee770f0d3d98d7411497a3191e2e0_img.jpg) - -``` - -classDiagram - class ArtifactResource { - <> - } - class ArtifactResourceType { - <> - } - ArtifactResource --> ArtifactResourceType : isOfType - ArtifactResource --> ArtifactResource : ReferenceOrUse - -``` - -UML Class Diagram showing two classes within the ORAN.O2ims.Artifacts namespace. The top class is ArtifactResource (stereotype: InformationObjectClass) and the bottom class is ArtifactResourceType (stereotype: InformationObjectClass). A directed association arrow points from ArtifactResource to ArtifactResourceType with the label 'isOfType'. A self-association arrow on ArtifactResource points back to itself with the label 'ReferenceOrUse'. - -Figure 4.2.2.3.1.2-1 ORAN.O2ims.Artifacts Intra-Namespace Relationships - -###### 4.2.2.3.1.3 ORAN.O2ims.Artifacts Inter-Namespace Relationships - -``` - -@startuml -Hide Members -Hide Circle - -Namespace ORAN.O2ims.Cluster #LightSteelBlue { - Class NodeCluster - Class ClusterResource -} - -Namespace ORAN.O2ims.Infrastructure #Lavender { - Abstract Class InfrastructureResource - Class InfrastructureResource -} - -Namespace ORAN.O2ims.Artifacts #Magenta { - -Class ArtifactResource <> - -} - -ORAN.O2ims.Cluster.NodeCluster --> ORAN.O2ims.Artifacts.ArtifactResource : BasedOn - -ORAN.O2ims.Cluster.ClusterResource --> ORAN.O2ims.Artifacts.ArtifactResource : BasedOn - -ORAN.O2ims.Infrastructure.InfrastructureResource --> ORAN.O2ims.Artifacts.ArtifactResource : BasedOn - -@enduml - -``` - -![UML class diagram showing inter-namespace relationships. Three namespaces are depicted: ORAN.O2ims.Cluster (light blue), ORAN.O2ims.Infrastructure (lavender), and ORAN.O2ims.Artifacts (magenta). In the Cluster namespace, NodeCluster and ClusterResource classes have 'BasedOn' associations pointing to the ArtifactResource class in the Artifacts namespace. In the Infrastructure namespace, the InfrastructureResource class also has a 'BasedOn' association pointing to the ArtifactResource class. ArtifactResource is stereotyped as <>.](a634891d16b60b21df90a35c2af72c67_img.jpg) - -``` - -classDiagram - namespace ORAN_O2ims_Cluster { - class NodeCluster - class ClusterResource - } - namespace ORAN_O2ims_Infrastructure { - class InfrastructureResource - } - namespace ORAN_O2ims_Artifacts { - class ArtifactResource { - <> - } - } - NodeCluster --> ArtifactResource : BasedOn - ClusterResource --> ArtifactResource : BasedOn - InfrastructureResource --> ArtifactResource : BasedOn - -``` - -UML class diagram showing inter-namespace relationships. Three namespaces are depicted: ORAN.O2ims.Cluster (light blue), ORAN.O2ims.Infrastructure (lavender), and ORAN.O2ims.Artifacts (magenta). In the Cluster namespace, NodeCluster and ClusterResource classes have 'BasedOn' associations pointing to the ArtifactResource class in the Artifacts namespace. In the Infrastructure namespace, the InfrastructureResource class also has a 'BasedOn' association pointing to the ArtifactResource class. ArtifactResource is stereotyped as <>. - -Figure 4.2.2.3.1.3-1 ORAN.O2ims.Artifacts Inter-Namespace Relationships - -##### 4.2.2.3.2 Inheritance - -###### 4.2.2.3.2.1 ORAN.O2ims.Artifacts Inheritance - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -Namespace ORAN.O2ims.Inventory { - Abstract Class Top <> - - Abstract Class InfrastructureInventoryObject_ <> - -``` - -``` - -Top <|-d- InfrastructureInventoryObject_ -} - -Namespace ORAN.O2ims.Artifacts { - - Class ArtifactResource <> - ArtifactResource -u->| ORAN.O2ims.Inventory.InfrastructureInventoryObject_ - - Class ArtifactResourceType <> - ArtifactResourceType -u->| ORAN.O2ims.Inventory.InfrastructureInventoryObject_ - -} - -@enduml - -``` - -![UML Class diagram showing inheritance. ORAN.O2ims.Inventory contains Top and InfrastructureInventoryObject_ classes. ORAN.O2ims.Artifacts contains ArtifactResourceType and ArtifactResource classes. Arrows show inheritance from the latter two to InfrastructureInventoryObject_.](2a476a0b3dbc3429436246db4784ff9f_img.jpg) - -``` - -classDiagram - class Top - class InfrastructureInventoryObject_ - class ArtifactResourceType - class ArtifactResource - - subgraph ORAN.O2ims.Inventory - Top - InfrastructureInventoryObject_ - end - subgraph ORAN.O2ims.Artifacts - ArtifactResourceType - ArtifactResource - end - ArtifactResourceType --|> InfrastructureInventoryObject_ - ArtifactResource --|> InfrastructureInventoryObject_ - InfrastructureInventoryObject_ --|> Top - -``` - -UML Class diagram showing inheritance. ORAN.O2ims.Inventory contains Top and InfrastructureInventoryObject\_ classes. ORAN.O2ims.Artifacts contains ArtifactResourceType and ArtifactResource classes. Arrows show inheritance from the latter two to InfrastructureInventoryObject\_. - -Figure 4.2.2.3.2.1-1 ORAN.O2ims.Artifacts Inheritance - -#### 4.2.2.4 Class Definitions - -##### 4.2.2.4.1 ArtifactResourceType - -###### 4.2.2.4.1.1 Definition - -The ArtifactResourceType represents a resource type for a stored artifact resource in an O-Cloud. - -Artifact resource types provide the categorization of O-Cloud artifacts used as declarative templates or binary images for provisioning or deployment. The values for these types are used to build the inventory with provisioning enablers. The O-Cloud provides a mechanism to discover data about artifacts with respective operations on artifact resource types. - -The ArtifactResourceType is a Specialized Object that derives from a Generalized Object, the *InfrastructureInventoryObject\_*. The ArtifactResourceType inherits the attributes from the *InfrastructureInventoryObject\_* and allows it and all specializations of this class to be included in a change notification. - -Image: O-RAN ALLIANCE logo - -O-RAN.WG6.TS.O-Cloud-IM.0-R005-v06.00 - -4.2.2.4.1.2 Attributes - -**Table 4.2.2.4.1.2-1 Attributes Properties for ArtifactResourceType** - -| Attribute name | Data Type/Description | Properties | -|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| artifactResourceTypeId | Data Type: string

Description: Cloud unique identifier for the artifact type. |
x-support-qualifier:      M x-isInvariant:            True x-inventoryNotification:   True x-stateChangeNotification: False format:                   uuid
| -| name | Data Type: string

Description: Human readable name for the artifact type. |
x-support-qualifier:      M x-isInvariant:            True x-inventoryNotification:   False x-stateChangeNotification: False
| -| description | Data Type: string

Description: Description of the artifact type. |
x-support-qualifier:      M x-isInvariant:            True x-inventoryNotification:   False x-stateChangeNotification: False
| -| extensions | Data Type: array

Description: These are unspecified (not standardized) properties (keys) which are tailored by the vendor to extend the information provided about the artifact resource type. |
x-support-qualifier:      M x-isAlwaysPresent:        False x-isInvariant:            False x-inventoryNotification:   False x-stateChangeNotification: False x-isOrdered:              False minItems:                 0 uniqueItems:              True items:                           AttributeValuePair
| - -4.2.2.4.1.3 Attribute constraints - -None. - -4.2.2.4.1.4 State diagram - -None. - -4.2.2.4.2 ArtifactResource - -4.2.2.4.2.1 Definition - -The ArtifactResource represents a stored artifact resource in an O-Cloud. - -ArtifactResource provides the ability to expose information about the artifact that is needed by consumers without the need of parsing the artifact itself by the consumer. The O-Cloud provides a mechanism to discover new artifacts with respective operations on artifact resources. - - The ArtifactResource is a Specialized Object that derives from a Generalized Object, the *InfrastructureInventoryObject\_*. The ArtifactResource inherits the attributes from the *InfrastructureInventoryObject\_* and allows it and all specializations of this class to be included in a change notification. - -4.2.2.4.2.2 Attributes - -**Table 4.2.2.4.2.2-1 Attributes Properties for ArtifactResource** - -| Attribute name | Data Type/Description | Properties | -|--------------------|--------------------------|----------------------------------------| -| artifactResourceId | Data Type: string |
x-support-qualifier:      M
| - -© 2026 by the O-RAN ALLIANCE e.V. Your use is subject to the copyright statement on the cover page of this specification. - -76 - -![O-RAN ALLIANCE logo](87c7651f032131db92d8f802429023bc_img.jpg) - -O-RAN.WG6.TS.O-Cloud-IM.0-R005-v06.00 - -| Attribute name | Data Type/Description | Properties | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | Description: O-Cloud unique identifier for the artifact. |
x-isInvariant:           True x-inventoryNotification:  True x-stateChangeNotification: False format:                  uuid
| -| name | Data Type: string

Description: Human readable name of the artifact. |
x-support-qualifier:      M x-isInvariant:           True x-inventoryNotification:  False x-stateChangeNotification: False
| -| version | Data Type: string

Description: Version of the artifact. |
x-support-qualifier:      M x-isInvariant:           True x-inventoryNotification:  False x-stateChangeNotification: False
| -| description | Data Type: string

Description: Description of the artifact. |
x-support-qualifier:      M x-isInvariant:           True x-inventoryNotification:  False x-stateChangeNotification: False
| -| parameterSchema | Data Type: array

Description: Properties (keys) which are tailored by the artifact composition when it is to be used as a parameterized template. See NOTE. |
x-support-qualifier:      M x-isAlwaysPresent:        False readOnly:                 True x-isInvariant:           False x-inventoryNotification:  False x-stateChangeNotification: False x-isOrdered:             False minItems:                0 uniqueItems:             True items:                          AttributeValuePair
| -| NOTE: Since the ArtifactResource is generic for any kind of artifact at an information model level, no keys are specified since this would have dependency on the kind of resource to which the artifact applies. | | | - -4.2.2.4.2.3 Attribute constraints - -None. - -4.2.2.4.2.4 State diagram - -None. - -### 4.2.3 Namespace: ORAN.O2ims.Cluster - -#### 4.2.3.1 Namespace Overview - -The O-RAN O2ims Cluster namespace defines the classes and their attributes which are directly exposed to the consumer (SMO) via its O2 IMS Interface. - -This namespace is used for the provisioned O-Cloud Node Clusters with status and metrics as well as its internal topologies. The O-Cloud Node Clusters are assembled based on the ORAN.O2ims.Inventory objects and configured through ORAN.O2ims.Artifacts. - -#### 4.2.3.2 Imported and associated information entities - -##### 4.2.3.2.1 Imported information entities and local labels - -Information entities imported into the model are also elements of the namespace and therefore shall remain unique within the namespace. - -© 2026 by the O-RAN ALLIANCE e.V. Your use is subject to the copyright statement on the cover page of this specification. - -77 - -**Table 4.2.3.2.1-1 Imported Entities** - -| Label reference | Local label | -|-----------------|-------------| -| | | -| | | - -##### **4.2.3.2.2 Associated information entities and local labels** - -Information entities referenced in the model through an association which may be extended and overloaded with a new entity of the same name within the namespace are listed in the associated entities table. - -**Table 4.2.3.2.2-1 Associated Entities** - -| Label reference | Local label | -|-------------------------------------------------|---------------------------------------| -| 4.2.1.4.7 InfrastructureInventoryObject_ | InfrastructureInventoryObject_ | -| | | - -#### **4.2.3.3 Class Diagram** - -##### **4.2.3.3.1 Relationships** - -###### **4.2.3.3.1.1 Description** - -This clause depicts the set of classes (e.g. IOCs) that encapsulates the information relevant for the O-RAN Cloud (O-Cloud). This clause provides an overview of the relationships between relevant classes in UML. Subsequent clauses provide more detailed specification of various aspects of these classes. The UML Class diagram depicts a view of the namespace maintaining a defined focus so as not to overcrowd a single diagram trying to depict all relationships within the namespace. - -###### **4.2.3.3.1.2 ORAN.O2ims.Cluster Intra-Namespace Relationships** - -``` -@startuml -Hide Members -Hide Circle - -Namespace ORAN.O2ims.Cluster #LightSteelBlue { -Class NodeCluster <> -Class NodeClusterType <> -Class ClusterResourceGroup <> -Class ClusterResource <> -Class ClusterResourceType <> - -NodeCluster "1" --> "0..N\n+clusterResourceGroups" ClusterResourceGroup -NodeCluster --> NodeClusterType : Has -ClusterResourceGroup "1" -r-> "1..N\n+clusterResources" ClusterResource : "\t\t\t" -NodeCluster "1" --> "1..N\n+clusterResourceIds" ClusterResource -ClusterResource --> ClusterResourceType : Has -ClusterResource "1" --> "0..N\n+memberOf" ClusterResource -} - -@enduml -``` - -![UML Class Diagram titled 'ORAN.O2ims.Cluster Intra-Namespace Relationships'. It shows five classes: NodeCluster, ClusterResourceGroup, ClusterResource, NodeClusterType, and ClusterResourceType. NodeCluster has a 1-to-0..N relationship with ClusterResourceGroup (role: +clusterResourceGroups) and a 1-to-1..N relationship with ClusterResource (role: +clusterResourceIds). It also has a 'Has' relationship with NodeClusterType. ClusterResourceGroup has a 1-to-1..N relationship with ClusterResource (role: +clusterResources). ClusterResource has a self-association (1-to-0..N, role: +memberOf) and a 'Has' relationship with ClusterResourceType.](d31b402b650e68c7d6b55d3cf8fda086_img.jpg) - -``` - -classDiagram - class NodeCluster { - <> - } - class ClusterResourceGroup { - <> - } - class ClusterResource { - <> - } - class NodeClusterType { - <> - } - class ClusterResourceType { - <> - } - NodeCluster "1" --> "0..N" ClusterResourceGroup : +clusterResourceGroups - NodeCluster "1" --> "1..N" ClusterResource : +clusterResourceIds - NodeCluster "1" --> "1" NodeClusterType : Has - ClusterResourceGroup "1" --> "1..N" ClusterResource : +clusterResources - ClusterResource "1" --> "0..N" ClusterResource : +memberOf - ClusterResource "1" --> "1" ClusterResourceType : Has - -``` - -UML Class Diagram titled 'ORAN.O2ims.Cluster Intra-Namespace Relationships'. It shows five classes: NodeCluster, ClusterResourceGroup, ClusterResource, NodeClusterType, and ClusterResourceType. NodeCluster has a 1-to-0..N relationship with ClusterResourceGroup (role: +clusterResourceGroups) and a 1-to-1..N relationship with ClusterResource (role: +clusterResourceIds). It also has a 'Has' relationship with NodeClusterType. ClusterResourceGroup has a 1-to-1..N relationship with ClusterResource (role: +clusterResources). ClusterResource has a self-association (1-to-0..N, role: +memberOf) and a 'Has' relationship with ClusterResourceType. - -Figure 4.2.3.3.1.2-1 ORAN.O2ims.Cluster Intra-Namespace Relationships - -###### 4.2.3.3.1.3 ORAN.O2ims.Cluster Inter-Namespace Relationships - -``` - -@startuml -Hide Members -Hide Circle - -Namespace ORAN.O2ims.Cluster #LightSteelBlue { - Class NodeCluster <> - Class ClusterResource <> -} - -Namespace ORAN.O2ims.Inventory #LightYellow { - Class Resource <> -} - -Namespace ORAN.O2ims.Infrastructure #Lavender { - Class InfrastructureResource <> -} - -Namespace ORAN.O2ims.Artifacts #Magenta { - Class ArtifactResource <> -} - -Namespace ORAN.O2ims.Provisioning #FireBrick { - Class ProvisioningRequest <> -} - -ORAN.O2ims.Provisioning.ProvisioningRequest --> ORAN.O2ims.Cluster.NodeCluster : Fulfill - -ORAN.O2ims.Cluster.NodeCluster --> ORAN.O2ims.Artifacts.ArtifactResource : BasedOn - -ORAN.O2ims.Cluster.ClusterResource -l-> ORAN.O2ims.Inventory.Resource : "\tMappedTo\t" -ORAN.O2ims.Cluster.ClusterResource .u. ORAN.O2ims.Infrastructure.InfrastructureResource -Note Left on Link -This relation will exist but its exact definitions -are dependent on the definition of specialized -classes within each namespace. -End note - -ORAN.O2ims.Cluster.ClusterResource "\n0..N" --> "0..N\n+artifactResourceIds\t\t\t\n" -ORAN.O2ims.Artifacts.ArtifactResource : "\n" - -``` - -``` -@enduml -``` - -![UML Class Diagram showing inter-namespace relationships for ORAN.O2ims.Cluster. The diagram includes namespaces ORAN.O2ims.Infrastructure, ORAN.O2ims.Provisioning, ORAN.O2ims.Inventory, ORAN.O2ims.Cluster, and ORAN.O2ims.Artifacts. Relationships include MappedTo, Fulfill, and BasedOn with multiplicities 0..N.](18bb06865e2dada3656ea3d57f290f7f_img.jpg) - -``` - -classDiagram - namespace ORAN_O2ims_Infrastructure { - class InfrastructureResource["«InformationObjectClass» -InfrastructureResource"] - } - namespace ORAN_O2ims_Provisioning { - class ProvisioningRequest["«InformationObjectClass» -ProvisioningRequest"] - } - namespace ORAN_O2ims_Inventory { - class Resource["«InformationObjectClass» -Resource"] - } - namespace ORAN_O2ims_Cluster { - class ClusterResource["«InformationObjectClass» -ClusterResource"] - class NodeCluster["«InformationObjectClass» -NodeCluster"] - } - namespace ORAN_O2ims_Artifacts { - class ArtifactResource["«InformationObjectClass» -ArtifactResource"] - } - - ClusterResource --> Resource : MappedTo - ProvisioningRequest --> NodeCluster : Fulfill - NodeCluster --> ArtifactResource : BasedOn - ClusterResource --> ArtifactResource : 0..N BasedOn - note for InfrastructureResource "This relation will exist but its exact definitions -are dependent on the definition of specialized -classes within each namespace." - -``` - -This relation will exist but its exact definitions are dependent on the definition of specialized classes within each namespace. - -UML Class Diagram showing inter-namespace relationships for ORAN.O2ims.Cluster. The diagram includes namespaces ORAN.O2ims.Infrastructure, ORAN.O2ims.Provisioning, ORAN.O2ims.Inventory, ORAN.O2ims.Cluster, and ORAN.O2ims.Artifacts. Relationships include MappedTo, Fulfill, and BasedOn with multiplicities 0..N. - -**Figure 4.2.3.3.1.3-1 ORAN.O2ims.Cluster Inter-Namespace Relationships** - -##### 4.2.3.3.2 Inheritance - -###### 4.2.3.3.2.1 ORAN.O2ims.Cluster Inheritance - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -Namespace ORAN.O2ims.Inventory { - Abstract Class InfrastructureInventoryObject_ <> -} - -Namespace ORAN.O2ims.Cluster { - - Abstract Class Top <> - - Class NodeCluster <> - NodeCluster -r->|> ORAN.O2ims.Inventory.InfrastructureInventoryObject_ - - Class NodeClusterType <> - NodeClusterType -u->|> ORAN.O2ims.Inventory.InfrastructureInventoryObject_ - - Class ClusterResourceGroup <> - ClusterResourceGroup -d->|> Top - - Class ClusterResource <> - ClusterResource -u->|> ORAN.O2ims.Inventory.InfrastructureInventoryObject_ - - Class ClusterResourceType <> - ClusterResourceType -l->|> ORAN.O2ims.Inventory.InfrastructureInventoryObject_ - -} -@enduml - -``` - -@endum1 - -![UML Class diagram showing inheritance for ORAN.O2ims.Cluster. The diagram shows ORAN.O2ims.Inventory as the root class with a nested class InfrastructureInventoryObject_. ORAN.O2ims.Cluster inherits from InfrastructureInventoryObject_. Inside ORAN.O2ims.Cluster, there are five nested classes: ClusterResource, ClusterResourceGroup, NodeClusterType, ClusterResourceType, and NodeCluster. ClusterResourceGroup inherits from Top, which in turn inherits from InfrastructureInventoryObject_.](2f587210e4f97c32758c5972e2e83d20_img.jpg) - -``` - -classDiagram - class ORAN_O2ims_Inventory { - <> - InfrastructureInventoryObject_ - } - class ORAN_O2ims_Cluster { - <> - ClusterResource - ClusterResourceGroup - NodeClusterType - ClusterResourceType - NodeCluster - Top - } - ORAN_O2ims_Cluster --|> ORAN_O2ims_Inventory - ClusterResourceGroup --|> Top - Top --|> InfrastructureInventoryObject_ - -``` - -UML Class diagram showing inheritance for ORAN.O2ims.Cluster. The diagram shows ORAN.O2ims.Inventory as the root class with a nested class InfrastructureInventoryObject\_. ORAN.O2ims.Cluster inherits from InfrastructureInventoryObject\_. Inside ORAN.O2ims.Cluster, there are five nested classes: ClusterResource, ClusterResourceGroup, NodeClusterType, ClusterResourceType, and NodeCluster. ClusterResourceGroup inherits from Top, which in turn inherits from InfrastructureInventoryObject\_. - -Figure 4.3.2.2.2.1-1 ORAN.O2ims.Cluster Inheritance - -#### 4.2.3.4 Class Definitions - -##### 4.2.3.4.1 NodeClusterType - -###### 4.2.3.4.1.1 Definition - -The NodeClusterType represents a resource type for a NodeCluster in an O-Cloud. - -Node cluster types provide the categorization of O-Cloud resource types used to create a node cluster. The O-Cloud provides a mechanism to discover the node cluster types with respective operations on node cluster types. - -The NodeClusterType is a Specialized Object that derives from a Generalized Object, the *InfrastructureInventoryObject\_*. The NodeClusterType inherits the attributes from the *InfrastructureInventoryObject\_* and allows it and all specializations of this class to be included in a change notification. - -###### 4.2.3.4.1.2 Attributes - -Table 4.2.3.4.1.2-1 Attributes Properties for NodeClusterType - -| Attribute name | Data Type/Description | Properties | -|-------------------|---------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| -| NodeClusterTypeId | Data Type: string
Description: Unique identifier for the NodeClusterType instance. | x-support-qualifier: M
x-isInvariant: True
x-inventoryNotification: True
x-stateChangeNotification: False
format: uuid | -| name | Data Type: string
Description: Name of the Node Cluster Type. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| description | Data Type: string
Description: Human readable description of the Node Cluster Type. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| extensions | Data Type: array
Description: These are unspecified (not standardized) properties (keys) which are | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | - -| Attribute name | Data Type/Description | Properties | -|----------------|-----------------------------------------------------------------------|--------------------------------------------------------------------------------------------| -| | tailored extend the information provided about the Node Cluster Type. | x-isOrdered: False
minItems: 0
uniqueItems: True
items:

AttributeValuePair | - -###### 4.2.3.4.1.3 Attribute constraints - -None. - -###### 4.2.3.4.1.4 State diagram - -None. - -##### 4.2.3.4.2 NodeCluster - -###### 4.2.3.4.2.1 Definition - -The NodeCluster represents a set of resource used to deploy workloads in an O-Cloud. - -Node cluster provides inventory of the resources used in a NodeCluster. The O-Cloud provides a mechanism to discover the node cluster with respective operations on node clusters. - -The NodeCluster is a Specialized Object that derives from a Generalized Object, the *InfrastructureInventoryObject\_*. The NodeCluster inherits the attributes from the *InfrastructureInventoryObject\_* and allows it and all specializations of this class to be included in a change notification. - -###### 4.2.3.4.2.2 Attributes - -**Table 4.2.3.4.2.2-1 Attributes Properties for NodeCluster** - -| Attribute name | Data Type/Description | Properties | -|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| -| nodeClusterId | Data Type: string
Description: Unique identifier for the NodeCluster instance assigned by the O-Cloud. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: True
x-stateChangeNotification: False
format: uuid | -| clientNodeClusterId | Data Type: string
Description: Unique identifier for the NodeCluster instance assigned by the consumer who requested its creation. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: True
x-inventoryNotification: True
x-stateChangeNotification: False | -| name | Data Type: string
Description: Name of the NodeCluster. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| description | Data Type: string
Description: Human readable description of the NodeCluster. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| extensions | Data Type: array
Description: These are unspecified (not standardized) properties (keys) which are | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False | - -| Attribute name | Data Type/Description | Properties | -|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | tailored extend the information provided about the NodeCluster. | x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:

AttributeValuePair | -| clusterDistributionDescription | Data Type: string
Description: Human readable text identifying the method of distribution of ClusterResources over O-Cloud Sites. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| NodeClusterTypeId | Data Type: string
Description: Identifier for the NodeClusterType that this NodeCluster is. | x-support-qualifier: M
x-isInvariant: True
x-inventoryNotification: True
x-stateChangeNotification: False
format: uuid | -| artifactResourceId | Data Type: string
Description: Identifier for the template artifact which this NodeCluster is based on. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: True
x-stateChangeNotification: False
format: uuid | -| clusterResourceIds | Data Type: array
Description: The list of cluster resource identifiers that are used to construct this NodeCluster. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 1
uniqueItems: True
items: string
format: uuid | -| clusterResourceGroups | Data Type: array
Description: Optional list node groups that comprise the cluster resources which compose the NodeCluster. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items: string
format: uuid | - -###### 4.2.3.4.2.3 Attribute constraints - -None. - -###### 4.2.3.4.2.4 State diagram - -None. - -##### 4.2.3.4.3 ClusterResourceType - -###### 4.2.3.4.3.1 Definition - -The ClusterResourceType represents a resource type for a ClusterResource in an O-Cloud. - -Cluster resource types provide the categorization of O-Cloud resource types used to create a node cluster. The O-Cloud provides a mechanism to discover the cluster resource types with respective operations on cluster resource types. - -The ClusterResourceType is a Specialized Object that derives from a Generalized Object, the *InfrastructureInventoryObject\_*. The ClusterResourceType inherits the attributes from the *InfrastructureInventoryObject\_* and allows it and all specializations of this class to be included in a change notification. - -###### 4.2.3.4.3.2 Attributes - -**Table 4.2.3.4.3.2-1 Attributes Properties for ClusterResourceType** - -| Attribute name | Data Type/Description | Properties | -|---------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| clusterResourceTypeI
d | Data Type: string

Description: Unique identifier for the ClusterResourceType instance. | x-support-qualifier: M
x-isInvariant: True
x-inventoryNotification: True
x-stateChangeNotification: False
format: uuid | -| name | Data Type: string

Description: Name of the Cluster Resource Type. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| description | Data Type: string

Description: Human readable description of the Cluster Resource Type. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| extensions | Data Type: array

Description: These are unspecified (not standardized) properties (keys) which are tailored extend the information provided about the Cluster Resource Type. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:









AttributeVa
luePair | - -###### 4.2.3.4.3.3 Attribute constraints - -None. - -###### 4.2.3.4.3.4 State diagram - -None. - -##### 4.2.3.4.4 ClusterResource - -###### 4.2.3.4.4.1 Definition - -The ClusterResource represents a resource used to construct a NodeCluster in an O-Cloud. - -Node cluster resource provides inventory of the resources used in a NodeCluster. The O-Cloud provides a mechanism to discover the node cluster resources with respective operations on node cluster resources. - -The ClusterResource is a Specialized Object that derives from a Generalized Object, the *InfrastructureInventoryObject\_*. The ClusterResource inherits the attributes from the *InfrastructureInventoryObject\_* and allows it and all specializations of this class to be included in a change notification. - -###### 4.2.3.4.4.2 - -###### Attributes - -Table 4.2.3.4.4.2-1 Attributes Properties for ClusterResource - -| Attribute name | Data Type/Description | Properties | -|---------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| clusterResourceId | Data Type: string
Description: Unique identifier for the ClusterResource instance. | x-support-qualifier: M
x-isInvariant: True
x-inventoryNotification: True
x-stateChangeNotification: False
format: uuid | -| name | Data Type: string
Description: Name of the cluster resource. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| description | Data Type: string
Description: Human readable description of the cluster resource. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| extensions | Data Type: array
Description: These are unspecified (not standardized) properties (keys) which are tailored extend the information provided about the Cluster Resource. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:

AttributeVa
luePair | -| clusterResourceTypeI
d | Data Type: string
Description: Identifier for the ClusterResourceType for this resource. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: True
x-stateChangeNotification: False
format: uuid | -| memberOf | Data Type: array
Description: list of other ClusterResources which are linked together. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:
string | -| artifactResourceIds | Data Type: array
Description: Identifiers for the artifact(s) which this resource is based on. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:
string
format:
uuid | -| resourceId | Data Type: string
Description: Identifier for the inventory resource which this | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: True
x-stateChangeNotification: False | - -| Attribute name | Data Type/Description | Properties | -|----------------|------------------------|--------------| -| | resource is mapped to. | format: uuid | - -###### 4.2.3.4.4.3 Attribute constraints - -None. - -###### 4.2.3.4.4.4 State diagram - -None. - -##### 4.2.3.4.5 ClusterResourceGroup - -###### 4.2.3.4.5.1 Definition - -The ClusterResourceGroup represents a collection of ClusterResources as a named set. - -###### 4.2.3.4.5.2 Attributes - -**Table 4.2.3.4.5.2-1 Attributes Properties for ClusterResourceGroup** - -| Attribute name | Data Type/Description | Properties | -|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| clusterResourceGroup | Data Type: string
Description: Unique identifier for the ClusterResourceGroup. | x-support-qualifier: M
x-isInvariant: True
x-inventoryNotification: True
x-stateChangeNotification: False
format: uuid | -| name | Data Type: string
Description: Name of the Node Group. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| description | Data Type: string
Description: Human readable description of the ClusterResourceGroup. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| extensions | Data Type: array
Description: These are unspecified (not standardized) properties (keys) which are tailored extend the information provided about the ClusterResourceGroup. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:

AttributeValuePair | -| clusterResources | Data Type: array
Description: The list of Cluster Resources belonging to this ClusterResourceGroup. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 1
uniqueItems: True
items: string
format: uuid | - -###### 4.2.3.4.5.3 Attribute constraints - -None. - -###### 4.2.3.4.5.4 State diagram - -None. - -### 4.2.4 Namespace: ORAN.O2ims.Provisioning - -#### 4.2.4.1 Namespace Overview - -The O-RAN O2ims Provisioning namespace defines the classes and their attributes which are directly exposed to the consumer (SMO) via its O2 IMS Interface. - -This namespace is used for provisioning requests and fulfillments, e.g. of O-Cloud Node Clusters, representing the requested and agreed service levels and their current identifiers. - -#### 4.2.4.2 Imported and associated information entities - -##### 4.2.4.2.1 Imported information entities and local labels - -Information entities imported into the model are also elements of the namespace and therefore shall remain unique within the namespace. - -**Table 4.2.4.2.1-1 Imported Entities** - -| Label reference | Local label | -|----------------------------------------------|-------------| -| TS 28.622 [6], information object class, Top | Top | -| | | - -##### 4.2.4.2.2 Associated information entities and local labels - -Information entities referenced in the model through an association which may be extended and overloaded with a new entity of the same name within the namespace are listed in the associated entities table. - -**Table 4.2.4.2.2-1 Associated Entities** - -| Label reference | Local label | -|-----------------|-------------| -| | | -| | | - -#### 4.2.4.3 Class Diagram - -##### 4.2.4.3.1 Relationships - -###### 4.2.4.3.1.1 Description - -This clause depicts the set of classes (e.g. IOCs) that encapsulates the information relevant for the O-RAN Cloud (O-Cloud). This clause provides an overview of the relationships between relevant classes in UML. Subsequent clauses provide more detailed specification of various aspects of these classes. The UML Class diagram depicts a view of the namespace maintaining a defined focus so as not to overcrowd a single diagram trying to depict all relationships within the namespace. - -###### 4.2.4.3.1.2 ORAN.O2ims.Provisioning Intra-Namespace Relationships - -``` -@startuml -Namespace ORAN.O2ims.Provisioning #FireBrick { -``` - -``` - -Skinparam BorderColor Red -Skinparam ArrowColor Yellow -Hide Empty Members -Hide Circle - -Class ProvisioningRequest <> - -Class ProvisioningStatus <> - -ENUM ProvisioningPhase <> - -ProvisioningRequest --> ProvisioningStatus -ProvisioningStatus -r- ProvisioningPhase - -} -@enduml - -``` - -![UML class diagram showing relationships within the ORAN.O2ims.Provisioning namespace. ProvisioningRequest (InformationObjectClass) has an arrow pointing to ProvisioningStatus (dataType), which in turn has a line connecting to ProvisioningPhase (enumeration).](5cf80bac69830ea773ac17c87e0ae24d_img.jpg) - -``` - -classDiagram - class ProvisioningRequest { - <> - } - class ProvisioningStatus { - <> - } - class ProvisioningPhase { - <> - } - ProvisioningRequest --> ProvisioningStatus - ProvisioningStatus -- ProvisioningPhase - -``` - -UML class diagram showing relationships within the ORAN.O2ims.Provisioning namespace. ProvisioningRequest (InformationObjectClass) has an arrow pointing to ProvisioningStatus (dataType), which in turn has a line connecting to ProvisioningPhase (enumeration). - -Figure 4.2.4.3.1.2-1 ORAN.O2ims.Provisioning Intra-Namespace Relationships - -###### 4.2.4.3.1.3 ORAN.O2ims.Provisioning Inter-Namespace Relationships - -``` - -@startuml -Hide Members -Hide Circle - -Skinparam ArrowColor MediumSeaGreen - -Namespace ORAN.O2ims.Provisioning #FireBrick { - Class ProvisioningRequest <> -} - -Namespace ORAN.O2ims.Artifacts #Magenta { - Abstract Class Template <> -} - -Namespace ORAN.O2ims.Cluster #LightSteelBlue { - Class NodeCluster <> -} - -Namespace ORAN.O2ims.Infrastructure #Lavender { - Abstract Class InfrastructureResource <> -} - -ORAN.O2ims.Provisioning.ProvisioningRequest : "\n\n" - -ORAN.O2ims.Provisioning.ProvisioningRequest -l-> ORAN.O2ims.Artifacts.Template : " -accordingTo -" - -ORAN.O2ims.Provisioning.ProvisioningRequest "\n\nl\n+provisioningRequestId" <-r-> "0..N\n\nnodeClusterId" ORAN.O2ims.Cluster.NodeCluster : " " - -``` - -``` -ORAN.O2ims.Provisioning.ProvisioningRequest "1\n+provisioningRequestId\n\n" <-u-> -"\nn0..N\n+infrastructureResourceIds" ORAN.O2ims.Infrastructure.InfrastructureResource : -"\n\n\n" - -@enduml -``` - -![UML Class Diagram showing inter-namespace relationships for ORAN.O2ims.Provisioning. The diagram includes four namespaces: ORAN.O2ims.Infrastructure, ORAN.O2ims.Artifacts, ORAN.O2ims.Provisioning, and ORAN.O2ims.Cluster. ORAN.O2ims.Provisioning contains ProvisioningRequest, which has a 0..N association with InfrastructureResource, an 'accordingTo' association with Template, and a 0..N association with NodeCluster.](750b1652a4f4791b84c02aa755a1dedd_img.jpg) - -``` - -classDiagram - namespace ORAN.O2ims.Infrastructure { - class InfrastructureResource { - <> - } - } - namespace ORAN.O2ims.Artifacts { - class Template { - <> - } - } - namespace ORAN.O2ims.Provisioning { - class ProvisioningRequest { - <> - } - } - namespace ORAN.O2ims.Cluster { - class NodeCluster { - <> - } - } - - ProvisioningRequest "1" -- "0..N" InfrastructureResource : +infrastructureResourceIds - Template -- ProvisioningRequest : accordingTo - ProvisioningRequest "1" -- "0..N" NodeCluster : +nodeClusterId - NodeCluster -- ProvisioningRequest : +provisioningRequestId - -``` - -UML Class Diagram showing inter-namespace relationships for ORAN.O2ims.Provisioning. The diagram includes four namespaces: ORAN.O2ims.Infrastructure, ORAN.O2ims.Artifacts, ORAN.O2ims.Provisioning, and ORAN.O2ims.Cluster. ORAN.O2ims.Provisioning contains ProvisioningRequest, which has a 0..N association with InfrastructureResource, an 'accordingTo' association with Template, and a 0..N association with NodeCluster. - -Figure 4.2.4.3.1.3-1 ORAN.O2ims.Provisioning Inter-Namespace Relationships - -##### 4.2.4.3.2 Inheritance - -###### 4.2.4.3.2.1 ORAN.O2ims.Provisioning Inheritance - -``` -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -Abstract Class Top <> -Class ProvisioningRequest <> - -Top <|-- ProvisioningRequest - -@enduml -``` - -![UML Class Diagram showing inheritance. ProvisioningRequest inherits from Top. Both classes have the stereotype InformationObjectClass.](8a0a9aa5fac5d73eefb772afd44649f6_img.jpg) - -``` - -classDiagram - class Top { - <> - } - class ProvisioningRequest { - <> - } - Top <|-- ProvisioningRequest - -``` - -UML Class Diagram showing inheritance. ProvisioningRequest inherits from Top. Both classes have the stereotype InformationObjectClass. - -Figure 4.2.4.3.2.1-1 ORAN.O2ims.Provisioning Inheritance - -#### 4.2.4.4 Class Definitions - -##### 4.2.4.4.1 ProvisioningRequest - -###### 4.2.4.4.1.1 Definition - -The ProvisioningRequest represents a request for item(s) to be provisioned in the O-Cloud. The SMO makes the declarative request to the O-Cloud through the O2ims. - -###### 4.2.4.4.1.2 Attributes - -Table 4.2.4.4.1.2-1 Attributes Properties for ProvisioningRequest - -| Attribute name | Data Type/Description | Properties | -|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| provisioningRequestId | Data Type: string
Description: Identifier of the provisioning request instance assigned by the SMO. | x-support-qualifier: M
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| name | Data Type: string
Description: Human readable name of the provisioning request instance as assigned by the SMO. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | -| description | Data Type: string
Description: Human readable description of the provisioning request instance as assigned by the SMO. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | -| templateName | Data Type: string
Description: Name of the template to be used as the basis for the declarative model for the provisioning request instance. When combined with the templateVersion it shall resolve to a templateId. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | -| templateVersion | Data Type: string
Description: Version of the template used as the basis for the declarative model for the provisioning request instance. When combined with the templateName it shall resolve to a templateId. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | -| templateParameters | Data Type: array
Description: List of variables/value pairs used within the template to tailor the template to this request instance. | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items: AttributeValuePair | -| provisioningRequestReference | Data Type: string
Description: A unique reference of this ProvisioningRequest assigned by the service producer at the time of request creation. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | -| status | Data Type: ProvisioningStatus
Description: The time of the last message and the current provisioningPhase of the ProvisioningRequest. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: True | - -| Attribute name | Data Type/Description | Properties | -|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| provisionedResourceSet | Data Type: provisionedResourceSet

Description: The resources that have been successfully provisioned as part of the provisioningRequest. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | - -###### 4.2.4.4.1.3 Attribute constraints - -**Table 4.2.4.4.1.3-3 Attributes Constraints for ProvisioningRequest** - -| Name | Definition | -|---------------------|---------------------------------------------------------------------------------------------------------------------------| -| ReadOnlyAfterCreate | The following attributes are provided by the SMO on the create request but are readOnly afterwards: provisioningRequestId | - -###### 4.2.4.4.1.4 State diagram - -None. - -##### 4.2.4.4.2 ProvisioningStatus <> - -###### 4.2.4.4.2.1 Definition - -The ProvisioningStatus represents the status of a ProvisioningRequest indicating the time of the last message and the current provisioningPhase and the provisioning status of the NodeCluster and/or individual InfrastructureResource(s) being provisioned by the ProvisioningRequest. The provisioningPhase is an enumerated set of values – PENDING, PROGRESSING, FULFILLED, FAILED, DELETING, that reflect the current phase of the provisioning request. The high-level definition of each provisioningPhase, are: - -- PENDING: The ProvisioningRequest is waiting to be processed by the O-Cloud (IMS). -- PROGRESSING: The O-Cloud (IMS) is processing the ProvisioningRequest and executing the actions to fulfill it. -- FULFILLED: The ProvisioningRequest has been successfully processed and completed by the O-Cloud (IMS). -- FAILED: The ProvisioningRequest could not be fully processed by the O-Cloud (IMS). -- DELETING: The ProvisioningRequest is in the process of being deleted by the O-Cloud (IMS). - -###### 4.2.4.4.2.2 Attributes - -**Table 4.2.4.4.2.2-1 Attributes Properties for ProvisioningStatus** - -| Attribute name | Data Type/Description | Properties | -|-------------------|-------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| -| updateTime | Data Type: string

Description: The last date and time that the provisioningPhase attribute was modified. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: True
format: date-time | -| message | Data Type: string

Description: Human readable text about the provisioningPhase at the last updateTime. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: True | -| provisioningPhase | Data Type: string

Description: This is an enumerated set of values which | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False | - -| Attribute name | Data Type/Description | Properties | -|------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | reflects the current phase of the provisioning request. | x-stateChangeNotification: True
enum:
- PENDING
- PROGRESSING
- FULFILLED
- FAILED
- DELETING | -| nodeClusterProvisioningStatus | Data Type: ResourceProvisionigStatus
Description: The current provisioning status of the NodeCluster. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: True | -| infrastructureResourceProvisioningStatus | Data Type: array
Description: The current provisioning status of individual InfrastructureResource(s). | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: True
x-isOrdered: False
minItems: 0
uniqueItems: True
items:
ResourceProvisionigStatus | - -###### 4.2.4.4.2.3 Attribute constraints - -None. - -###### 4.2.4.4.2.4 State diagram - -``` - -@startuml -skinparam NoteFontColor white -[*] -[#green]-> PENDING : Create -PENDING -[#blue]-> PROGRESSING : Accepted -PENDING -[#blue]--> FAILED : Failed -PENDING -[#green]--> DELETING : Delete -PROGRESSING -[#blue]-> FULFILLED : Completed -PROGRESSING -[#green]-> PENDING : Update -PROGRESSING -[#blue]--> FAILED : Failed -PROGRESSING -[#green]--> DELETING : Delete -FAILED -[#green]--> PENDING : Update -FAILED -[#green]--> DELETING : Delete -FULFILLED -[#green]-> PENDING : Update -FULFILLED -[#green]--> DELETING : Delete -DELETING -[#blue]->[*] : Deletion\nCompleted -note "O-Cloud Internal Transitions" as N1 #blue -note "Service Operation Request" as N2 #green -@enduml - -``` - -![State diagram for Provisioning Request (provisioningPhase) Phase Transition. The diagram shows four states: PENDING, PROGRESSING, FAILED, and FULFILLED, leading to a DELETING state and finally a Deletion Completed end state. Transitions are categorized into O-Cloud Internal Transitions (blue) and Service Operation Requests (green).](8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg) - -The state diagram illustrates the lifecycle of a Provisioning Request (provisioningPhase). It begins with an initial state leading to PENDING via a 'Create' Service Operation Request. From PENDING, an 'Accepted' internal transition leads to PROGRESSING, while 'Update' and 'Delete' are Service Operation Requests. PROGRESSING can lead to FULFILLED via 'Completed' (internal) or to FAILED via 'Failed' (internal). Both FULFILLED and FAILED can lead to DELETING via 'Delete' (Service Operation Request). Additionally, 'Update' (Service Operation Request) can transition the state from PROGRESSING, FAILED, or FULFILLED back to PENDING. All states (PENDING, PROGRESSING, FAILED, FULFILLED) have a 'Delete' Service Operation Request transition to DELETING. The DELETING state concludes with a 'Deletion Completed' internal transition to the final state. - -``` - -stateDiagram-v2 - [*] --> PENDING : Create - PENDING --> PROGRESSING : Accepted - PENDING --> FAILED : Failed - PENDING --> FULFILLED : Update - PENDING --> DELETING : Delete - PROGRESSING --> PENDING : Update - PROGRESSING --> FAILED : Failed - PROGRESSING --> FULFILLED : Completed - PROGRESSING --> DELETING : Delete - FAILED --> PENDING : Update - FAILED --> DELETING : Delete - FULFILLED --> PENDING : Update - FULFILLED --> DELETING : Delete - DELETING --> [*] : Deletion Completed - -``` - -State diagram for Provisioning Request (provisioningPhase) Phase Transition. The diagram shows four states: PENDING, PROGRESSING, FAILED, and FULFILLED, leading to a DELETING state and finally a Deletion Completed end state. Transitions are categorized into O-Cloud Internal Transitions (blue) and Service Operation Requests (green). - -Figure - -4.2.4.4.2.4-1 State Diagram for Provisioning Request (provisioningPhase) Phase Transition - -##### 4.2.4.4.3 ProvisionedResourceSet <> - -###### 4.2.4.4.3.1 Definition - -The ProvisionedResourceSet represents the resources that have been successfully provisioned as part of the ProvisioningRequest. - -###### 4.2.4.4.3.2 Attributes - -**Table 4.2.4.4.3.2-1 Attributes Properties for ProvisionedResourceSet** - -| Attribute name | Data Type/Description | Properties | -|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| nodeClusterId | Data Type: String

Description: If the request is fulfilled by a NodeCluster this field will contain its Id. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-nullable: True
format: uuid | -| infrastructureResources | Data Type: array

Description: If the request is fulfilled by InfrastructureResource(s) this list will contain the Id(s) of all resources used to fulfil it. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items: string | - -###### 4.2.4.4.3.3 Attribute constraints - -None. - -###### 4.2.4.4.3.4 State diagram - -None. - -##### 4.2.4.4.4 ResourceProvisioningStatus <> - -###### 4.2.4.4.4.1 Definition - -The ResourceProvisioningStatus represents the provisioning status of a resource indicating the ‘name’, ‘resourceId’ and ‘resourceProvisioningPhase’ of the NodeCluster or the InfrastructureResource. The ‘resourceProvisioningPhase’ is an enumerated set of values – PROCESSING, PROVISIONED, AWAITING\_FREE\_RESOURCES and FAILED, that reflect the current provisioning phase of the NodeCluster or an InfrastructureResource. The meanings of the possible values for resourceProvisioningPhase are as follows: - -- PROCESSING: The resource provisioning is under processing. -- PROVISIONED: The resource has been provisioned successfully. -- AWAITING\_FREE\_RESOURCES: IMS is waiting for free O-Cloud Resources to be available to fulfill the provisioning of the requested resource. IMS continues to attempt to acquire required resources. This situation can be resolved if required O-Cloud Resources are made available by O-Cloud, or by SMO (FOCOM) updating the Provisioning Request to suit the available O-Cloud resources. -- FAILED: O-Cloud has experienced some internal failures for the provisioning of the resource. IMS at O-Cloud stops further processing for provisioning of corresponding resource until further intervention from consumer SMO (FOCOM). - -###### 4.2.4.4.4.2 Attributes - -Table 4.2.4.4.4.2-1 Attributes Properties for ResourceProvisioningStatus - -| Attribute name | Data Type/Description | Properties | -|----------------------------|------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| resourceName | Data Type: string
Description: Name of the resource as given in ProvisioningRequest parameters. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False | -| resourceId | Data Type: string
Description: Identifier of the resource, as assigned by the O-Cloud. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
format: uuid | -| resourceProvisioning Phase | Data Type: string
Description: Current provisioning phase of the resource. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: True
enum:
- PROCESSING
- PROVISIONED
- AWAITING_FREE_RESOURCES
- FAILED | - -###### 4.2.4.4.4.3 Attribute constraints - -None - -###### 4.2.4.4.4.4 State diagram - -``` -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -state PROCESSING -state FAILED -state PROVISIONED -state "AWAITING_FREE_RESOURCES" as WAITING - -PROCESSING --> FAILED : O-Cloud\nInternal failure -FAILED -l-> PROCESSING : ProvisioningRequest\nupdate request -PROCESSING -d-> PROVISIONED : ProvisioningRequest\nupdate request -PROVISIONED --> PROCESSING -PROCESSING -d-> WAITING : O-Cloud could not\nacquire enough\nresources -WAITING --> PROCESSING : O-Cloud adds\nrequired resources -WAITING --> PROCESSING : ProvisioningRequest\nupdate request -FAILED -d[hidden]-> PROVISIONED -FAILED -r[hidden]-> WAITING -WAITING -d[hidden]-> PROVISIONED - -@enduml -``` - -![State Diagram for ResourceProvisioningPhase transitions. States: PROCESSING, FAILED, AWAITING_FREE_RESOURCES, PROVISIONED. Transitions include ProvisioningRequest update request, O-Cloud Internal failure, O-Cloud could not acquire enough resources, O-Cloud adds required resources.](487c58c79e44e6cf98b6368b6667b9c6_img.jpg) - -``` - -stateDiagram-v2 - [*] --> PROCESSING - PROCESSING --> FAILED : O-Cloud Internal failure - PROCESSING --> AWAITING_FREE_RESOURCES : O-Cloud could not acquire enough resources - PROCESSING --> PROVISIONED : ProvisioningRequest update request - PROCESSING --> PROCESSING : ProvisioningRequest update request - FAILED --> PROCESSING : ProvisioningRequest update request - AWAITING_FREE_RESOURCES --> PROCESSING : O-Cloud adds required resources - AWAITING_FREE_RESOURCES --> PROCESSING : ProvisioningRequest update request - PROVISIONED --> PROCESSING : ProvisioningRequest update request - -``` - -State Diagram for ResourceProvisioningPhase transitions. States: PROCESSING, FAILED, AWAITING\_FREE\_RESOURCES, PROVISIONED. Transitions include ProvisioningRequest update request, O-Cloud Internal failure, O-Cloud could not acquire enough resources, O-Cloud adds required resources. - -Figure 4.2.4.4.4.4-1 State Diagram for ResourceProvisioningPhase transitions - -### 4.2.5 Namespace: ORAN.O2ims.Infrastructure - -#### 4.2.5.1 Namespace Overview - -The O-RAN O2ims Infrastructure namespace defines the classes and their attributes which are directly exposed to the consumer (SMO) via its O2 IMS Interface. - -This namespace is used for fulfillment of provisioning requests which produce configured resources for later provisioning requests. - -#### 4.2.5.2 Imported and associated information entities - -##### 4.2.5.2.1 Imported information entities and local labels - -Information entities imported into the model are also elements of the namespace and therefore shall remain unique within the namespace. - -Table 4.2.5.2.1-1 Imported Entities - -| Label reference | Local label | -|-----------------|-------------| -| | | -| | | - -##### 4.2.5.2.2 Associated information entities and local labels - -Information entities referenced in the model through an association which may be extended and overloaded with a new entity of the same name within the namespace are listed in the associated entities table. - -Table 4.2.5.2.2-1 Associated Entities - -| Label reference | Local label | -|--------------------------------------------------|---------------------------------------| -| 4.2.1.4.7, InfrastructureInventoryObject_ | InfrastructureInventoryObject_ | -| | | - -#### 4.2.5.3 Class Diagram - -##### 4.2.5.3.1 Relationships - -###### 4.2.5.3.1.1 Description - -This clause depicts the set of classes (e.g. IOCs) that encapsulates the information relevant for the O-RAN Cloud (O-Cloud). This clause provides an overview of the relationships between relevant classes in UML. Subsequent clauses provide more detailed specification of various aspects of these classes. The UML Class diagram depicts a view of the namespace maintaining a defined focus so as not to overcrowd a single diagram trying to depict all relationships within the namespace. - -###### 4.2.5.3.1.2 ORAN.O2ims.Infrastructure Intra-Namespace Relationships - -The O-Cloud Networking consists of both intra- and inter-namespace relationships, which are complex in nature. The overview diagram (Figure 4.2.5.3.1.2-1) which simplifies the relationships has been drawn to help build a high-level understanding of the various object classes and their relationships. For example, a “Node” of type VM, BareMetal, and/or IaaS, which is a cluster resource type, terminates one or more site networks, which is an infrastructure resource type. Similarly, a gateway can terminate one or more site networks, forming an intra-namespace relationship since both the gateway and site networks belong to the infrastructure namespace. - -![UML Class Diagram showing O-Cloud Networking Overview. It includes classes Node (>ClusterResource), SiteNW (>InfraResource), Gateway (>InfraResource), and AttachmentCircuit (>InfraResource) with their relationships like TerminatedBy and AttachTo.](02dfdcd208dbdc8fa4f645885e59dd17_img.jpg) - -``` - -classDiagram - class Node { - <> - VM/BM/IaaS - } - class SiteNW { - <> - } - class Gateway { - <> - } - class AttachmentCircuit { - <> - } - - Node --> SiteNW : TerminatedBy - Node --> Gateway : TerminatedBy - Gateway --> SiteNW : TerminatedBy - Gateway --> AttachmentCircuit : AttachTo - AttachmentCircuit --> Gateway : InterfaceIP [v4,v6, v4 and v6] - -``` - -The diagram illustrates the O-Cloud networking architecture. At the top, two "Node" blocks (stereotyped as >ClusterResource, with types VM/BM/IaaS) are connected via "TerminatedBy" relationships to a central horizontal bus. This bus connects to a "SiteNW" block (>InfraResource) and a "Gateway" block (>InfraResource). The Gateway is also linked to the SiteNW via a "TerminatedBy" relationship. Below the Gateway, two "AttachmentCircuit" blocks (>InfraResource) are shown. The Gateway connects to these via "AttachTo" relationships, while the AttachmentCircuits provide "InterfaceIP [v4,v6, v4 and v6]" back to the Gateway. The entire diagram is contained within a light yellow box labeled "O-Cloud". - -UML Class Diagram showing O-Cloud Networking Overview. It includes classes Node (>ClusterResource), SiteNW (>InfraResource), Gateway (>InfraResource), and AttachmentCircuit (>InfraResource) with their relationships like TerminatedBy and AttachTo. - -Figure 4.2.5.3.1.2-1 O-Cloud Networking Overview - -These relationships, however, involve various elements and endpoints to support multiplicity, which introduces several implicit data types such as **Port**, **NetworkAddress**, and **SegmentationElement**. Each of these elements can include multiple endpoints representing a termination or an external connectivity attachment. These implicit data types and their relationships with O-Cloud Networking objects are captured in Figure 4.2.5.3.1.2-2, which illustrates the intra-namespace relationships between specialized infrastructure namespace objects. - -There is a relationship between “Port” and “AttachmentCircuit” to represent the endpoint connectivity provided by “Port” for O-Cloud Site connectivity, using two possible associations to the transport network described in Clause 4.2.1.3.1.4.1. - -Note: This document version represents the relationship with a dotted line, as the O-Cloud Networking Information Model is still in development. - -``` - -@startuml -Hide members -Hide circle - -Namespace ORAN.O2ims.Infrastructure #Lavender { - - Class InfrastructureResource <> - - InfrastructureResource "1" o--> "0..N\n+n+linkedInfrastructureResources" InfrastructureResource - - Class InfrastructureResourceType <> - - InfrastructureResource -u-> InfrastructureResourceType : isOfType - - Class Gateway <> - Class Port <> - Class NetworkAddress <> - - Class SiteNetwork <> - Class SegmentationElement <> - Class AttachmentCircuit <> - - SiteNetwork "1" *--> "1..N\n+n+segmentation" SegmentationElement : "\n\n\n" - SiteNetwork "1" o-r-> "0..N\n+n+attachedTo" Port : "\t\t\t" - AttachmentCircuit "1" *-u-> "1..N\n+n+segmentation" SegmentationElement - Gateway "1" *-u-> "1..N\n+n+connectedNetworks" Port : "\n\n\n" - Gateway "1" *-u-> "0..N\n+n+attachedTo" Port - Port "1" *-r-> "1..N\n+n+endPoints" NetworkAddress : "\t\t\t" - - AttachmentCircuit .1. Port - -} - -@enduml - -``` - -![UML Class Diagram titled 'ORAN.O2ims.Infrastructure Intra-Namespace Relationships'. The diagram shows the following classes and their relationships: - - InfrastructureResourceType (InformationObjectClass) - - SiteNetwork (InformationObjectClass) - - Port (dataType) - - NetworkAddress (dataType) - - InfrastructureResource (InformationObjectClass) - - SegmentationElement (dataType) - - Gateway (InformationObjectClass) - - AttachmentCircuit (InformationObjectClass) - - Relationships: - - InfrastructureResourceType is the base class for InfrastructureResource (isOfType). - - InfrastructureResource has a self-association 'linkedInfrastructureResources' (0..N to 1..N). - - SiteNetwork has a composition relationship with SegmentationElement ('+segmentation', 1 to 1..N). - - SiteNetwork has an association with Port ('+attachedTo', 1 to 0..N). - - AttachmentCircuit has an association with SegmentationElement ('+segmentation', 1 to 1..N). - - Gateway has associations with Port ('+connectedNetworks' and '+attachedTo', 1 to 1..N and 0..N). - - Port has an association with NetworkAddress ('+endPoints', 1 to 1..N). - - AttachmentCircuit has a directed association to Port (multiplicity 1 at AttachmentCircuit end).](ffe0fef452a0ae9a20253c319c54e13c_img.jpg) - -UML Class Diagram titled 'ORAN.O2ims.Infrastructure Intra-Namespace Relationships'. The diagram shows the following classes and their relationships: - - InfrastructureResourceType (InformationObjectClass) - - SiteNetwork (InformationObjectClass) - - Port (dataType) - - NetworkAddress (dataType) - - InfrastructureResource (InformationObjectClass) - - SegmentationElement (dataType) - - Gateway (InformationObjectClass) - - AttachmentCircuit (InformationObjectClass) - - Relationships: - - InfrastructureResourceType is the base class for InfrastructureResource (isOfType). - - InfrastructureResource has a self-association 'linkedInfrastructureResources' (0..N to 1..N). - - SiteNetwork has a composition relationship with SegmentationElement ('+segmentation', 1 to 1..N). - - SiteNetwork has an association with Port ('+attachedTo', 1 to 0..N). - - AttachmentCircuit has an association with SegmentationElement ('+segmentation', 1 to 1..N). - - Gateway has associations with Port ('+connectedNetworks' and '+attachedTo', 1 to 1..N and 0..N). - - Port has an association with NetworkAddress ('+endPoints', 1 to 1..N). - - AttachmentCircuit has a directed association to Port (multiplicity 1 at AttachmentCircuit end). - -Figure 4.2.5.3.1.2-2 ORAN.O2ims.Infrastructure Intra-Namespace Relationships - -###### 4.2.5.3.1.3 ORAN.O2ims.Infrastructure Inter-Namespace Relationships - -``` - -@startuml -Hide Members -Hide Circle - -``` - -``` - -Namespace ORAN.O2ims.Inventory #LightYellow { - Class Resource <> -} - -Namespace ORAN.O2ims.Cluster #LightSteelBlue { - Class ClusterResource <> -} - -Namespace ORAN.O2ims.Infrastructure #Lavender { - Class InfrastructureResource <> -} - -Namespace ORAN.O2ims.Artifacts #Magenta { - Class ArtifactResource <> -} - -ORAN.O2ims.Infrastructure.InfrastructureResource "1" -l-> "\n1..N\n+inventoryResourceIds" -ORAN.O2ims.Inventory.Resource : "\t\trealizedBy\t\t" - -ORAN.O2ims.Infrastructure.InfrastructureResource .d. ORAN.O2ims.Cluster.ClusterResource -Note Left on Link -This relation will exist but its exact definitions -are dependent on the definition of specialized -classes within each namespace. -End note - -ORAN.O2ims.Infrastructure.InfrastructureResource "1" -r-> "\n1\n+artifactResourceId" -ORAN.O2ims.Artifacts.ArtifactResource : "\t\tBasedOn\t\t" - -@enduml - -``` - -![UML Class diagram showing inter-namespace relationships. ORAN.O2ims.Inventory (yellow) has a class 'Resource'. ORAN.O2ims.Infrastructure (lavender) has a class 'InfrastructureResource'. ORAN.O2ims.Artifacts (magenta) has a class 'ArtifactResource'. ORAN.O2ims.Cluster (blue) has a class 'ClusterResource'. A solid line labeled 'realizedBy' connects 'InfrastructureResource' (multiplicity 1) to 'Resource' (multiplicity 1..N, role -inventoryResourceIds). A solid line labeled 'BasedOn' connects 'InfrastructureResource' (multiplicity 1) to 'ArtifactResource' (multiplicity 1, role +artifactResourceId). A dashed line connects 'InfrastructureResource' to 'ClusterResource'. A note on the dashed line states: 'This relation will exist but its exact definitions are dependent on the definition of specialized classes within each namespace.'](a963ca41bde1669b18a4b783616f228b_img.jpg) - -UML Class diagram showing inter-namespace relationships. ORAN.O2ims.Inventory (yellow) has a class 'Resource'. ORAN.O2ims.Infrastructure (lavender) has a class 'InfrastructureResource'. ORAN.O2ims.Artifacts (magenta) has a class 'ArtifactResource'. ORAN.O2ims.Cluster (blue) has a class 'ClusterResource'. A solid line labeled 'realizedBy' connects 'InfrastructureResource' (multiplicity 1) to 'Resource' (multiplicity 1..N, role -inventoryResourceIds). A solid line labeled 'BasedOn' connects 'InfrastructureResource' (multiplicity 1) to 'ArtifactResource' (multiplicity 1, role +artifactResourceId). A dashed line connects 'InfrastructureResource' to 'ClusterResource'. A note on the dashed line states: 'This relation will exist but its exact definitions are dependent on the definition of specialized classes within each namespace.' - -Figure 4.2.5.3.1.3-1 ORAN.O2ims.Infrastructure Inter-Namespace Relationships - -##### 4.2.5.3.2 Inheritance - -###### 4.2.5.3.2.1 ORAN.O2ims.Infrastructure Inheritance - -``` - -@startuml -skin rose -skinparam ClassStereotypeFontStyle normal -skinparam style strictuml -hide members - -Namespace ORAN.O2IMS.Inventory { - Abstract Class InfrastructureInventoryObject_ <> -} - -Namespace ORAN.O2IMS.Infrastructure { - Class InfrastructureResource <> -} - -``` - -``` - -InfrastructureResource -u->|> ORAN.O2IMS.Inventory.InfrastructureInventoryObject_ - -Class InfrastructureResourceType <> - InfrastructureResourceType -u->|> ORAN.O2IMS.Inventory.InfrastructureInventoryObject_ -} - -@enduml - -``` - -![UML Class diagram showing inheritance. ORAN.O2IMS.Inventory is the base class containing InfrastructureInventoryObject_. ORAN.O2IMS.Infrastructure is a subclass that inherits from the base class. InfrastructureResourceType and InfrastructureResource are shown as subclasses of InfrastructureInventoryObject_ within the Infrastructure namespace.](de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg) - -``` - -classDiagram - class ORAN.O2IMS.Inventory { - <> - InfrastructureInventoryObject_ - } - class ORAN.O2IMS.Infrastructure { - <> - InfrastructureResourceType - InfrastructureResource - } - ORAN.O2IMS.Inventory <|-- ORAN.O2IMS.Infrastructure - InfrastructureResourceType <|-- ORAN.O2IMS.Inventory - InfrastructureResource <|-- ORAN.O2IMS.Inventory - -``` - -UML Class diagram showing inheritance. ORAN.O2IMS.Inventory is the base class containing InfrastructureInventoryObject\_. ORAN.O2IMS.Infrastructure is a subclass that inherits from the base class. InfrastructureResourceType and InfrastructureResource are shown as subclasses of InfrastructureInventoryObject\_ within the Infrastructure namespace. - -Figure 4.2.5.3.2.1-1 ORAN.O2ims.Infrastructure Inheritance - -#### 4.2.5.4 Class Definitions - -##### 4.2.5.4.1 InfrastructureResourceType - -###### 4.2.5.4.1.1 Definition - -The InfrastructureResourceType represents a resource type in an O-Cloud. - -Infrastructure resource types provide the categorization of O-Cloud resources used to connect the O-Cloud resources and to build components of the Cluster namespace. The values for these types are used to build the configured inventory and enable an authorized consumer to track infrastructure resource changes over time. The O-Cloud provides a mechanism to discover the infrastructure resource types with respective operations on infrastructure resource types. - -The InfrastructureResourceType is a Specialized Object that derives from a Generalized Object, the *InfrastructureInventoryObject\_*. The InfrastructureResourceType inherits the attributes from the *InfrastructureInventoryObject\_* and allows it and all specializations of this class to be included in a change notification. - -###### 4.2.5.4.1.2 Attributes - -Table 4.2.5.4.1.2-1 Attributes Properties for InfrastructureResourceType - -| Attribute name | Data Type/Description | Properties | -|------------------------------|-------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| -| infrastructureResourceTypeId | Data Type: string
Description: Identifier of the infrastructure resource type. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: True
x-stateChangeNotification: False
format: uuid | -| name | Data Type: string
Description: Name of the infrastructure resource type as identified by the cloud provider. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| description | Data Type: string | x-support-qualifier: M
readOnly: True | - -| Attribute name | Data Type/Description | Properties | -|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | Description: Human readable description of the infrastructure resource type. | x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| extensions | Data Type: array
Description: These are unspecified (not standardized) properties (keys) which are tailored by the vendor to extend the information provided about the Infrastructure Resource Type. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: True
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items:

AttributeVa
luePair | - -###### 4.2.5.4.1.3 Attribute constraints - -None. - -###### 4.2.5.4.1.4 State diagram - -None. - -##### 4.2.5.4.2 InfrastructureResource - -###### 4.2.5.4.2.1 Definition - -The InfrastructureResource is a Specialized Object that derives from a Generalized Object, the *InfrastructureInventoryObject\_*. The InfrastructureResource inherits the attributes from the *InfrastructureInventoryObject\_* and allows it and all specializations of this class to be included in a change notification. - -###### 4.2.5.4.2.2 Attributes - -**Table 4.2.5.4.1.2-1 Attributes Properties for InfrastructureResource** - -| Attribute name | Data Type/Description | Properties | -|----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| -| infrastructureResource
Id | Data Type: string
Description: Identifier of the resource. Locally unique within the scope of an O-Cloud instance. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: True
x-stateChangeNotification: False
format: uuid | -| name | Data Type: string
Description: Human readable name of the infrastructure resource instance. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| description | Data Type: string
Description: Human readable description of the infrastructure resource. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| infrastructureResource
TypeId | Data Type: string
Description: Identifier of infrastructure resource type that | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: True
x-stateChangeNotification: False | - -| Attribute name | Data Type/Description | Properties | -|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | this instance is a type of. | format: uuid | -| linkedInfrastructureResourceIds | Data Type: array
Description: List of infrastructure resource IDs that are used to realize this infrastructure resource instance. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items: string | -| inventoryResourceIds | Data Type: array
Description: List of inventory resource IDs that are used to realize this infrastructure resource instance. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
x-isOrdered: False
minItems: 1
uniqueItems: True
items: string | -| artifactResourceId | Data Type: string
Description: Identifier of artifact resource Id that the instance was configured with. | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: True
x-stateChangeNotification: False
format: uuid | -| extensions | Data Type: array
Description: These are unspecified (not standardized) properties (keys) which are tailored by the vendor to extend the information provided about the Resource Pool. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
x-isOrdered: False
minItems: 0
uniqueItems: True
items: AttributeValuePair | - -###### 4.2.5.4.2.3 Attribute constraints - -None. - -###### 4.2.5.4.2.4 State diagram - -None. - -##### 4.2.5.4.3 Gateway - -###### 4.2.5.4.3.1 Definition - -The Gateway infrastructure resource is a specialization of the InfrastructureResource. As such in addition to the attributes below, all attributes of the InfrastructureResource are also a member of this class. - -NOTE 1: The present document version does not specify QoS related attributes/classes. - -NOTE 2: The present document version does not specify complete L2/L3 related attributes/classes associated to the Gateway. - -The Gateway is a Specialized Object that derives from a Generalized Object, the InfrastructureResource. The Gateway inherits the attributes from the InfrastructureResource. - -###### 4.2.5.4.3.2 Attributes - -Table 4.2.5.4.3.2-1 Attributes Properties for Gateway - -| Attribute name | Data Type/Description | Properties | -|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| tags | Data Type: array
Description: The list of tags/labels on the Gateway resource. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
minItems: 0
items:

AttributeVa
luePair | -| status | Data Type: string
Description: The Gateway status. For instance, ACTIVE, DOWN, BUILD or ERROR. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: True | -| connectedNetworks | Data Type: array
Description: The list of port(s) to support one or multiple Site Networks termination. A port is a list of Gateway interfaceIPs e.g. IPv4 and IPv6 for a Site Network. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
minItems: 0
items:
Port | -| realizedBy | Data Type: string
Description: Where this gateway is implemented/realized (e.g. SiteGW). | x-support-qualifier: M
readOnly: True
x-isInvariant: True
x-inventoryNotification: True
x-stateChangeNotification: False
format:
uuid | -| attachedTo | Data Type: array
Description: The list of port(s) to support one or multiple Attachment Circuits. A port is a list of Gateway interfaceIPs e.g. IPv4 and IPv6 for an Attachment Circuit. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
minItems: 0
items:
Port | - -###### 4.2.5.4.3.3 Attribute constraints - -None. - -###### 4.2.5.4.3.4 State diagram - -None. - -#### 4.2.5.4.4 SiteNetwork - -##### 4.2.5.4.4.1 Definition - -The SiteNetwork infrastructure resource is a specialization of the InfrastructureResource. As such in addition to the attributes below, all attributes of the InfrastructureResource are also a member of this class. - -NOTE: The present document version does not specify QoS related attributes/classes. - -The SiteNetwork is a Specialized Object that derives from a Generalized Object, the InfrastructureResource. The SiteNetwork inherits the attributes from the InfrastructureResource. - -###### 4.2.5.4.4.2 Attributes - -**Table 4.2.5.4.4.2-1 Attributes Properties for SiteNetwork** - -| Attribute name | Data Type/Description | Properties | -|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| tags | Data Type: array
Description: The list of tags/labels on the SiteNetwork resource. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
items:

AttributeVa
luePair | -| mtu | Data Type: integer
Description: The maximum transmission unit (MTU) value to address fragmentation. Minimum value is 68 for IPv4, and 1280 for IPv6. | x-support-qualifier: M
x-isAlwaysPresent: False
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| segmentation | Data Type: array
Description: The list of segmentationElement(s) to support one or multiple segments where, a segmentationElement is a list of segmentationID (e.g. 100, 200) and segmentationType (e.g. flat, vlan, vxlan, or gre) | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
minItems: 1
items:

Segmentatio
nElement | -| realizedBy | Data Type: string
Description: Where this network/segment is implemented/realized (e.g. SiteNWFabric). | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| shared | Data Type: boolean
Description: Indicates if the network is shared (True). | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | -| status | Data Type: string
Description: The SiteNetwork status. For instance, ACTIVE, DOWN, BUILD or ERROR. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: True | - - - -| Attribute name | Data Type/Description | Properties | -|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| segmentation | Data Type: array

Description: The list of segmentationElement(s) to support one or multiple segments where, a segmentationElement is a list of segmentationID (e.g. 100, 200) and segmentationType (e.g. flat, vlan, vxlan, or gre) | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
minItems: 1
items:

SegmentationElement | -| bearer | Data Type: string

Description: A physical or logical link that establishes connectivity between the O-Cloud Site and external networks. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False | - -# 4.2.5.4.5.3 Attribute constraints - -None. - -4.2.5.4.5.4 State diagram - -None. - -4.2.5.4.6 Port <> - -4.2.5.4.6.1 Definition - -The Port is a list of network addresses (IPv4, IPv6, or IPv4 and IPv6) which a network device is connected to. - -4.2.5.4.6.2 Attributes - -**Table 4.2.5.4.6.2-1 Attributes Properties for Port** - -| Attribute name | Data Type/Description | Properties | -|----------------|--------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| endPoints | Data Type: array

Description: The list of addresses to support one or multiple network connections. | x-support-qualifier: M
readOnly: True
x-isInvariant: False
x-inventoryNotification: True
x-stateChangeNotification: False
minItems: 1
items:

NetworkAddress | - -4.2.5.4.6.3 Attribute constraints - -None. - -4.2.5.4.6.4 State diagram - -None. - -4.2.5.4.7 SegmentationElement <> - -4.2.5.4.7.1 Definition - -The SegmentationElement represents one segment of a SiteNetwork. A SiteNetwork may have more than one segment. - -4.2.5.4.7.2 Attributes - -**Table 4.2.5.4.7.2-1 Attributes Properties for SegmentationElement** - -| Attribute name | Data Type/Description | Properties | -|------------------|----------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| -| segmentationType | Data Type: string
Description: The description of the type of segmentation. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | -| Segments | Data Type: array
Description: list of segmentIds for a given SiteNetwork segment. | x-support-qualifier: M
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False
minItems: 1
items: string | - -4.2.5.4.7.3 Attribute constraints - -None. - -4.2.5.4.7.4 State diagram - -None. - -4.2.5.4.8 NetworkAddress <> - -4.2.5.4.8.1 Definition - -The NetworkAddress is an IP address (IPv4, IPv6, or IPv4 & IPv6) which identifies a network address. - -4.2.5.4.8.2 Attributes - -**Table 4.2.5.4.8.2-1 Attributes Properties for NetworkAddress** - -| Attribute name | Data Type/Description | Properties | -|----------------|---------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------| -| ipv4Addr | Data Type: ipv4Addr
Description: IPv4 address as defined in 3GPP TS 28.623 | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | -| ipv6Addr | Data Type: ipv6Addr
Description: IPv6 address as defined in 3GPP TS 28.623 | x-support-qualifier: M
x-isAlwaysPresent: False
x-isInvariant: False
x-inventoryNotification: False
x-stateChangeNotification: False | - -## 4.2.5.4.8.3 Attribute constraints - -**Table 4.2.5.4.8.3-1 Attributes Constraints for EndPoint** - -| Name | Definition | -|----------------------------|------------------------------------------------------------------------------------------------------------------| -| ATLEAST_ONE_ADDRESS_EXISTS | Condition: if ipv4Addr exists then ipv6Addr is optional. Likewise, if ipv6Addr exists then ipv4Addr is optional. | - -## 4.2.5.4.8.4 State diagram - -None. - ---- - -## Annex (informative): Change History - -| Date | Revision | Description | -|-------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2023.03.21 | 00.01.00 | Create initial O-RAN version, from template with modifications for 3GPP TS 32.160 | -| 2023.04.28 | 00.01.01 | Modified Scope, Introduction, References, and Annex Formatting CR: ATT-2023.03.15-WG6-CR-001-O2IM Introduction and Scope Changes - v02. | -| 2023.04.28 | 00.01.02 | Modified Section 4 Outline with examples CR: ATT-2023.04.04-CR-003-O2IM Section 4 new Outline-v04. | -| 2023.06.02 | 00.01.03 | Incorporated the following CRs:
ATT-2023.05.02-WG6-CR-004-ORIM Template Cleanup-v01
ATT-2023.05.03-WG6-CR-005-O2IM IMS Diagrams-v03
ATT-2023.05.23-WG6-CR-006-O2IM Imported and Associated Entities-v03
ATT-2023.05.23-WG6-CR-007-O2IM Fault Monitoring-v04 | -| 2023.07.10 | 00.02.00 | Initial internal release based on the current O2IMS Specification.

Incorporated the following CRs:
ATT-2023.05.30-WG6-CR-008-O2IM Infrastructure Inventory-v05
ATT-2023.05.23-WG6-CR-009-O2IM LCM-v03
ATT-2023.05.31-WG6-CR-010-O2IM Performance Store-v03
ATT-2023.05.31-WG6-CR-011-O2IM Performance Job-v04
ATT-2023.06.01-WG6-CR-012-O2IM Performance Subscription-v04
ATT-2023.06.01-WG6-CR-013-O2IM Performance Report-v03 | -| 2024.03.12 | 01.00.00 | Initial release

Incorporated the following CRs:
ATT-2024.03.01-WG6-CR-019-O2IM CR Merge Corrections-v03
DELL.AO-2023.09.26-WG6-CR-0002-O2IM_Site_v07
ATT-2024.01.26-WG6-CR-017-O2IM Namespace alignment-V02
ATT-2024.01.26-WG6-CR-018-O2IM Measurement Job Corrections-V04
ATT-2023.09.15-WG6-CR-016-O2IM Deferred Comment Corrections-V04
DELL.AO-2023.02.21-WG6-CR-0001-O2IM Extensions to infrastructure service objects-v03
ATT-2023.08.25-WG6-CR-015-O2IM New PM Use Case Support-v03
ATT-2023.06.01-WG6-CR-014-O2IM New Alarm Use Case Support-v06
Editorial, missing clauses for new section 4.3.3.5.3, 4.3.3.5.4 | -| 2024.07.01 | 01.00.04 | Incorporated the following CRs:
ERI.AO-2024.04.09-WG6-CR-0029-Namespace-Updates-v03
ATT-2024.04.15-WG6-CR-0020-New Namespace Skeletons-v03
ATT-2024.04.23-CR-021-Remove Performance Measurement Subscription-v01
ERI.AO-2023.07.25-WG6-CR-0024-OCloud_Networking_Information_Model-v21 | -| 2024.07.05 | 01.00.05 | Incorporated the following CRs:
ATT-2024.05.28-WG6-CR-0022-Performance Subscription Correction-v02
ATT-2024.05.28-WG6-CR-0023-log Query Enhancements-v05 | -| 2024.07.19 | 01.00.06 | Incorporated Release review Comments | -| 2024.07.30. | 02.00.00 | Release 2.0 | -| 2024.11.12 | 02.00.01 | Incorporated the following CRs:
DELL.AO-2024.08.27-WG6-CR-0010-O2IM_DictionaryId_v01
NOK.AO-2024.09.10-WG6-CR0131-GenSpclResource_Guidelines_v01.01
ATT-2024.07.30-WG6-CR-0024-Provisioning Relationship Modeling-v06
ATT.AO-2024.07.31-WG6-CR-0025-Networking Infrastructure Attribution-v09
ATT.AO-2024.09.11-WG6-CR-0026-Infrastructure Specialized Classes-v09
ATT-2024.09.11-WG6-CR-0027-PM Job Writeable Extensions-v02
ATT-2024.09.11-WG6-CR-0028-InfrastructureInventoryObject Name Correction-v03
ATT-2024.10.02-WG6-CR-0030-Cluster Classes and Attribution-v05
ATT-2024.10.02-WG6-CR-0031-Artifact Classes and Attribution-v04
ATT-2024.10.02-WG6-CR-0032-Provisioning Classes and Attribution-v08
ATT.AO-2024.10.15-WG6-CR-0033-3GPP Alignment to Release 18-v02
The following Editorial changes were made to make the document cohesive
Boiler plate text required for the Infrastructure Namespace which was not included in
ATT-CR-0025 or ATT-CR-0026. This included the clause 4.2.5 itself and clauses
4.2.5.1, 4.2.5.2, and 4.2.5.3 | -| 2024.11.26 | 03.00.00 | Release 3.0 | - -| | | | -|------------|----------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2025.03.11 | 03.00.01 | Incorporated the following CR:
DTAG-2025.01.24-WG6-CR-0002-O2IM_extensions attribute_v02.00
DELL.AO-2025.01.28-WG6-CR-0012-O2IM_Location_v03.00
ERI.AO-2025.01.13-WG6-CR-0056-O2IM-Update-ProvisioningRequest-InfoObjectClass-CR-v05 | -| 2025.03.18 | 03.00.02 | Incorporated Release comments from Information Modeling Team. Many Font changes, especially to tables for consistency and alignment to the O-RAN template. | -| 2025.03.21 | 03.00.03 | Incorporated Release review Comments | -| 2025.03.27 | 04.00.00 | Release 4.0 | -| 2025.06.23 | 04.00.01 | Incorporated the following CR:
DTAG-29.04.2025-WG6-CR-0003_Update to NotifyFileReady and LogQuery_v02.00
DTAG.AO-23.05.2025-WG6-CR-0004 PM Job Change Notification_v01.00
DTAG.AO-23.05.2025-WG6-CR-0006 Consumer provided identifier format IM-v01.00
ERI.AO-2025.04.10-WG6-CR-0074-O2IM-ProvisioningRequest-InfoObjectClass-CR-v04 | -| 2025.06.24 | 04.00.02 | Incorporated the following CR:
RHT.2025.04.07-WG6-CR-0002-O2IM_Generic_Object_References_For_Alarms_v04.00 | -| 2025.07.07 | 04.00.03 | Formatting changes to align with new O-RAN Template | -| 2025.07.07 | 05.00 | Release 5.0 | -| 2025.11.07 | 05.00.01 | Incorporated the following CRs:
ATT-2025.04.01-WG6-CR-0034-Collection and report interval alignment-v02
DCM-2025.10.02-O-RAN.WG6.O2IM-CR-001-addition_of_eventType-v02
DTAG.AO-29.07.2025-WG6-CR-0007 Introduce x-isAlwaysPresent and x-nullable properties-v03.00
DTAG.AO-29.07.2025-WG6-CR-0008 Clarification for PerformanceSubscription-v02.00
ERI.AO-2025.10.4-WG6-CR-0089-O2IM-ProvisioningRequest-API-ProvisioningStatus-CR-v06 | -| 2025.11.19 | 05.00.05 | Corrections to CR incorporation. | \ No newline at end of file diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg deleted file mode 100644 index b548da241a1a69e5532a0c63ad3fc70b28e2f813..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/02dfdcd208dbdc8fa4f645885e59dd17_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d1187bfbda192a151e09541078c9dee9d7df5ef12d136e9b75d84ba34b9ee4c5 -size 67030 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/08783c875dd39684fee7f2a40b584c64_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/08f6ace0c83e7394657fa372b47aec04_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/08f6ace0c83e7394657fa372b47aec04_img.jpg deleted file mode 100644 index 32e5d4ae08285ccfa6a6f99f2a616cba5e8d9614..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/08f6ace0c83e7394657fa372b47aec04_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:945ea30e31b26a88c66717e6bc7c7331d717a09d1e5a070ff24afd299bd46dcb -size 50593 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg deleted file mode 100644 index 522592560c05ca17514c40ba6c87e0546c993b48..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:098294823e9eb557e17933b166f647f488d7ca7d931a2d4bc5b48a8ebc2bcc11 -size 64522 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/14af8d47efd24c21fddf71b2415b6397_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg deleted file mode 100644 index 7a81fc772bfb76a422452b6ed9b71374c0f82b77..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/16c1175b5f05a4b55e6d396fc51b15b3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f609fba3026e3656efc302ae901bc42c76818faecffb4b3899620ea0a52b5bcc -size 87398 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/185df94f4a6a5245323255e844a30ec0_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/18bb06865e2dada3656ea3d57f290f7f_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/18bb06865e2dada3656ea3d57f290f7f_img.jpg deleted file mode 100644 index aeff5b10f7023856aa99aa30c58bb3d1da7e95c8..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/18bb06865e2dada3656ea3d57f290f7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:90638354fedff7046062733c6722b038da53ca4ef705081f1259f5ce955b542e -size 92505 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 7b709785e7bde6ab0aefde9a9de8aa8821419443..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7fce5ec145d266c60c3b370530b3bedf9dceca212603e3c67667c5ad79226fb7 -size 4577 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/22af211207188ebc64d7b60ca052b367_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/26d664119ad25250780f554633444e54_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/26d664119ad25250780f554633444e54_img.jpg deleted file mode 100644 index 2a2122d591d3323156778f5e7a6394ecd5b01cb8..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/26d664119ad25250780f554633444e54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a75372cf660f018adabb0544574e2222e379a3d49005e5ebd1b416f9810d688 -size 53672 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/27b06ec9f42b5d727a2630f61a5f1861_img.jpg deleted file mode 100644 index 5e954aaecff40e120ae72e255e9cb79a24d91507..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/27b06ec9f42b5d727a2630f61a5f1861_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ecb6bc8c43caa96cebd5d9433379b73589fec760cafce0e71b7bc54f4d058dda -size 62787 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/29f3760c0230631eb03f67030ef65ed0_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/2a476a0b3dbc3429436246db4784ff9f_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/2a476a0b3dbc3429436246db4784ff9f_img.jpg deleted file mode 100644 index 8aaa6da9fc777934511f6b081784db06e6861f69..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/2a476a0b3dbc3429436246db4784ff9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ad459563d310bf45a10be0214c40c9c964fcd111afa31a78c1ba56bbe1e865d9 -size 52267 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg deleted file mode 100644 index dfd0839f2d183598c18e536b107fe7372599d34f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/2ae3eae1bd80a90f192f568ae246a9a6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:70741915b5fd37d95226f115500dc3f743203541904726f8f6ac7654bd923b51 -size 12159 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/2f587210e4f97c32758c5972e2e83d20_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/2f587210e4f97c32758c5972e2e83d20_img.jpg deleted file mode 100644 index c74b6c87c9a8cc26bae0a79889046144bab07bed..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/2f587210e4f97c32758c5972e2e83d20_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3960f3929ebf9888942348dbd716313672f8268b5a0608035e0f0902498327a7 -size 50949 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/36fb8f844f936e7a1de4838da774f2f9_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/38222c3ae003223a67635bfcc6950fbb_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/443ee770f0d3d98d7411497a3191e2e0_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/443ee770f0d3d98d7411497a3191e2e0_img.jpg deleted file mode 100644 index 683da78aa577172c9d085e4c1b321bb6b24826c5..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/443ee770f0d3d98d7411497a3191e2e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:412bab91ae6d39bd8cd0c46341ddc9f18b40f46a7e0459234606121b995d1e0b -size 28848 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/481b1f80fc31ebebb30d1f57d31e3af3_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/487c58c79e44e6cf98b6368b6667b9c6_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/487c58c79e44e6cf98b6368b6667b9c6_img.jpg deleted file mode 100644 index 02205d31f6e596f4c61acd66e6e02b7a1070c1e1..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/487c58c79e44e6cf98b6368b6667b9c6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:39e3dc640325f7490a4225ee86c5da5cded4dc6b1950ed9797bd7ececcb676c8 -size 57769 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/4b297191fa254f84c021e73b3b79e860_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/4db00373eb0bec04341ee887235bbfea_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg deleted file mode 100644 index 52a81dc19366c5aa88a9141e1c9b69e83b88684e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c2440765a5a52bac96bac612d5c513bd64e96c2e3add92f4892bcc8e2bd381c7 -size 79502 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/52a225f71b166b0c65c2f29f32a79f7f_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/5445597cceefaca1ac89e710fe339325_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/5445597cceefaca1ac89e710fe339325_img.jpg deleted file mode 100644 index 061a7829a0d777360cb57c6c72ef305f40828a91..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/5445597cceefaca1ac89e710fe339325_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d6f5a99be6bfb269ade109f332b3fcdb0101040c088da153f04149835b2c4275 -size 127367 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/56ac11fb9683d7b846fb65c845d80f22_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg deleted file mode 100644 index b07156175843b8478dc71d1c83d7383a1e953068..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/5860ad6bd2a2dd8d1ab12864b8f90f37_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f3fd8d0821e51a5eafd2fc64276f6c7c81d49e87924bb801be05e8e443eabea1 -size 146337 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/59368942873b0c35eef79a7a985025dc_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/59fcc0e3699f239444841881a2e75da0_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/5ae3023386ee15fae372871afce28865_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/5cf80bac69830ea773ac17c87e0ae24d_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/5cf80bac69830ea773ac17c87e0ae24d_img.jpg deleted file mode 100644 index f2841eb67cce6ce6ef4340a9a8b4e6e2529c57b5..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/5cf80bac69830ea773ac17c87e0ae24d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4b324747b591224ea1377c055acb3013589e4019e68a202a9edc92677922222b -size 28230 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/681c354e00e1c0fe098ba665ff155cb8_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/6a5342571eca4b46338fdfb3c42a8055_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/6b0834ca8cdd18832ed461378d51dcb7_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/6c8a96787f532bd1fa4719e738cf556f_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/6e3cdcccf7bacc5d43c63eebb58c7931_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/6e3cdcccf7bacc5d43c63eebb58c7931_img.jpg deleted file mode 100644 index eb76c58fabc2462569cbe06c9eea63b0ef5c84bd..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/6e3cdcccf7bacc5d43c63eebb58c7931_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0fc7c3353fc2ce6b991f9b35d2186a531535b75b68c17b9f257ebfff1d132c29 -size 4072 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/750b1652a4f4791b84c02aa755a1dedd_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/750b1652a4f4791b84c02aa755a1dedd_img.jpg deleted file mode 100644 index 3a01c4eda0b385ae473935034bfb51b69ff4cbc2..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/750b1652a4f4791b84c02aa755a1dedd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d7b4de5345d2a0bb153051fbf303a58f4aabfd0568b139d1ef911072cb5e7753 -size 46305 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/79898de98da3367d0ea9beef38f5c01c_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/7a3d4c97055e3021cefb0c5850050bff_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/7d08458fbe0bd5f306c00c16d68b25f2_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/7f4320cee12fc1dbb865cc6b67462a91_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/829cdaf00f7219d70e571064b2b13291_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8307f6b04df072c9332f9987e034272c_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8307f6b04df072c9332f9987e034272c_img.jpg deleted file mode 100644 index 1b1b67c5d3e9c864bd03889c4429574b564b2bef..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8307f6b04df072c9332f9987e034272c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f5e90184d4c2fbea800a8bcc00ab30b0f476bed094cdbbcc1aa24b0def8e6e3e -size 108156 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/83ee9f10bd3636e192d68decf7f04cec_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/844077b3034f0030b404207db0ad76b4_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/844077b3034f0030b404207db0ad76b4_img.jpg deleted file mode 100644 index 408e231fb19469f56bfde27627449e4f03976dfc..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/844077b3034f0030b404207db0ad76b4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6913fde95818f7215cf222a785a51660fcd8296977a06aa99fdb543ab7b00737 -size 44499 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/87c7651f032131db92d8f802429023bc_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/87c7651f032131db92d8f802429023bc_img.jpg deleted file mode 100644 index 2f5de0eca5b5418a1ddf5542efc340cfe20cc522..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/87c7651f032131db92d8f802429023bc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:47fd0c6f2adb2a73bf1ef6f9d5bbd9c9695919e48008334169d0f67b16da85d3 -size 4410 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/89100a6476d1d96f22c192db16502fec_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg deleted file mode 100644 index 5a4b6f94853b9f41d3ac245c66e2d002d1b20549..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8a0a9aa5fac5d73eefb772afd44649f6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eaa2355d7911b77f25eeb60b2386c59ac92911c3510fcf075eb4204a69638ad9 -size 12842 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8b4befaffc5166da571069410e207aea_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg deleted file mode 100644 index a91ee2aa64f2516d7deb13af0dec6bad2a325f19..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bf82dad10379035b7b0e8912916dc6c7da47f80120ccf368463ff49498686aac -size 95660 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8d129c93d18909f0643766f372e9ebf6_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8d138b6bf0be359dc7f079db4899bc41_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8dcca7651accff77ce832523fe2c7e64_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/90ddb84c323b956e2d50a54d3f870566_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/90ddb84c323b956e2d50a54d3f870566_img.jpg deleted file mode 100644 index 018ac5ec3ecff12d42b5042e8f574d68f215bb8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/90ddb84c323b956e2d50a54d3f870566_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5693cb53cf179722ea514a76a9540987ec814a4d0c025c0418d6d5bba0564212 -size 88222 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/9156549264d36ead617a1dec7987f970_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/970a901d8e537da4b6ff719d8931912f_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/990afa9d07fb81cf8760867cb4247a79_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/9b59a11096b85b2bc74c6f653a354e28_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/9b9d2abd741ed4bafe7f78f89961c663_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/9b9d2abd741ed4bafe7f78f89961c663_img.jpg deleted file mode 100644 index aa2c826aa8f79da5dcd4b4a3f733e785bafe2e1e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/9b9d2abd741ed4bafe7f78f89961c663_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:218e871d414c83968500cb617a4304aa53210d528c3c8f8862d414ee7111df41 -size 58698 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/a634891d16b60b21df90a35c2af72c67_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/a634891d16b60b21df90a35c2af72c67_img.jpg deleted file mode 100644 index f82d915f9dbda0214a60775120642eb5edb98260..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/a634891d16b60b21df90a35c2af72c67_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:20a889d1d591eddc488812957d7b90bf73badd962631bff3264e2e854556c888 -size 49497 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/a76a30cf23764f0b907220e7c3c70ce1_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/a7fcb275d0eed586509a47f4f86a9725_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/a82aef1d2f3f1a527328950e9db947ee_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/a963ca41bde1669b18a4b783616f228b_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/a963ca41bde1669b18a4b783616f228b_img.jpg deleted file mode 100644 index cf663481342702d79e9d6a74b123a6f407d2947f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/a963ca41bde1669b18a4b783616f228b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4ee048f62d5a321fcaf7492bea8472b7c48cf8c803354c85ed4b77da994daffd -size 58860 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg deleted file mode 100644 index 83c1d059f9e82c3e5c4af73f91df2189f7566029..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:70c4404ea27b1f21ff61a810a1af3f2467971f5df07ad1a7f5d374fd5208bea7 -size 49076 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/be8d4d130f4e1f103926de61c4bfc23c_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/c5538ac451af9d74926b82278f11fb87_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d2c29dfabebacb6f853683a6c3759320_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d31b402b650e68c7d6b55d3cf8fda086_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d31b402b650e68c7d6b55d3cf8fda086_img.jpg deleted file mode 100644 index a93fd5d5c3440086e3f9adf4cb8932b57bec064f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d31b402b650e68c7d6b55d3cf8fda086_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b7751f6ea5fc57c775feaa6308d309302b59e34d94000c7a2f11a42aa51ca4bf -size 57646 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg deleted file mode 100644 index 71ede4b4977616d8d119ec4085da07488e169029..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d53cd0fd1cf896a9353fd63de1505ba2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4d814efdc5f0efea050c2f5a69393d55eb227b80eae4f0c0bd927e871d6c9861 -size 109968 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d90d939bcbf43d474efaeeaa335a635c_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/d90f17b29a73eddf151f51effa8912e0_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/da8cb3d696f15f2c6de7aff6955d12d3_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg deleted file mode 100644 index 0ffb6be125c81033c621bf1053d01a040b620778..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/de63e4b6d8b0aa76b85e1fe3236eac27_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:90e751202a659ac394ca850f1a9bc9f9cfa377a3ec56df83bc72ad785d34ba69 -size 45399 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e29665b8abcea967ef289c6aff07ae4c_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e29665b8abcea967ef289c6aff07ae4c_img.jpg deleted file mode 100644 index 8b91360505bb067784955dde1de61c78991fbc9e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e29665b8abcea967ef289c6aff07ae4c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ac9ea70fde903b7a40c3d6bcfa600ee033bf5061fffb490ab62636a104b781b6 -size 30786 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e32e1bcf367a284cc7a4186056810d22_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg deleted file mode 100644 index 4b94da934e2c8c85c0123640346015b174f8dc14..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:53785b160680d7d75d469ea49f0daf5b5a3522fbee704e81dcd409934e1d112e -size 4601 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e47215539168b9c4f4a14a2fe1a6dd93_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e87df69ebd4cd2dbbf6749079e6c057a_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e882a6bdfd0e868314f3a26f536145a3_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg deleted file mode 100644 index a8fb986845a4bb39505dcbf04e2f132cf6992ad6..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:128c736e15fdd41d9eaa68213b160fb5ba560ca978e0015b07c46844781affcc -size 123800 diff --git a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/f3d768b0299c4763bc703b606391c48b_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.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/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/ffe0fef452a0ae9a20253c319c54e13c_img.jpg deleted file mode 100644 index 8d35f4edb79ba27eeb358c6232d1de8f5f3e3550..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/O-RAN.WG6.TS.O-Cloud-IM-R005-v06.00/images/ffe0fef452a0ae9a20253c319c54e13c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e0517cae2f81102600d931cbac3128b07ed15e1960d7d0120d86077363e22104 -size 64338 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/doc.md b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/doc.md deleted file mode 100644 index 937963f608d13f0183fe45fb554302d17b38ef2a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/doc.md +++ /dev/null @@ -1,1702 +0,0 @@ - - -# --- **O-RAN Work Group 6 (Cloudification and Orchestration)****O2 Interface General Aspects and Principles** - -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 - -- List of figures.....4 -- List of tables .....4 -- Foreword.....5 -- Modal verbs terminology.....5 -- 1 Introduction .....5 - - 1.1 Scope .....5 - - 1.2 References .....5 - - 1.2.1 Normative references .....5 - - 1.2.2 Informative references .....7 - - 1.3 Definition of terms, symbols and abbreviations .....7 - - 1.3.1 Terms .....7 - - 1.3.2 Symbols .....8 - - 1.3.3 Abbreviations.....8 -- 2 General Aspects.....9 - - 2.1 Introduction to O2 .....9 - - 2.2 Alignment with O-RAN Architecture .....9 - - 2.2.1 Alignment with Overall Architecture .....9 - - 2.2.2 Alignment with OAM Architecture .....11 - - 2.3 Technology Independence.....11 - - 2.4 General Requirements .....11 - - 2.5 Relationship with Existing Standards and Open Source Solutions .....11 - - 2.5.1 ETSI NFV .....11 - - 2.5.2 IETF.....13 - - 2.5.3 3GPP.....13 - - 2.5.4 Kubernetes .....13 - - 2.5.5 OpenStack.....13 - - 2.5.6 ONAP/OSM.....13 -- 3 O2 Interface General Principles .....13 - - 3.1 O-Clouds .....13 - - 3.2 O-Cloud Inventory .....14 - - 3.2.0 Overview .....14 - - 3.2.1 Infrastructure Inventory .....15 - - 3.2.2 Logical Inventory.....15 - - 3.2.3 Deployment Inventory .....15 - - 3.3 O-Cloud Monitoring Service .....16 - - 3.3.0 Overview .....16 - - 3.3.1 General Capabilities.....16 - - 3.4 O-Cloud Provisioning.....17 - - 3.4.0 Overview .....17 - - 3.4.1 Affinity, Anti-Affinity, Quorum Diversity Rules .....18 - - 3.4.2 O-Cloud Capacity and Availability .....18 - - 3.4.3 O-Cloud Provisioning Basic Concepts .....19 - - 3.5 O-Cloud Software Management.....30 - - 3.5.1 General Capabilities.....30 - - 3.6 O-Cloud Life Cycle Management .....31 - - 3.7 O-Cloud Deployment Life Cycle Management.....32 - - 3.7.1 Overview .....32 - - 3.7.2 General Capabilities.....33 - - 3.7.3 Deployment Management Services .....33 - - 3.8 O-Cloud Fault Management Concepts .....34 - - 3.8.0 Overview .....34 - - 3.8.1 Fault Information Model.....34 - - 3.8.2 Subscription .....34 - - 3.8.3 Notifications .....34 - - 3.8.4 Parallel Reporting .....35 - - 3.8.5 Simple Devices .....35 - -- 3.8.6 Source of Truth .....35 -- 3.8.7 Alarm Dictionary .....35 -- 3.8.8 Queries.....35 -- 3.8.9 Filtering .....36 -- 3.8.10 Void .....36 -- 3.8.11 Alarm Synchronization .....36 -- 3.8.12 Alarm Correlation .....36 -- 3.8.13 Escalation Strategy .....37 -- 3.8.14 Fault Domains.....37 -- 3.8.15 Fault Tolerance .....37 -- 3.8.16 Metrics .....38 -- 3.8.17 Alarm Suppression.....38 -- 3.8.18 Fault Supervision .....39 -- 3.8.19 Logs for Fault Management.....39 -- 3.8.20 Logging Level.....41 -- 3.8.21 Alarm List.....42 -- 3.8.22 Retention Period .....42 -- 3.8.23 Alarm Purge.....42 -- 3.8.24 Archiving Alarms .....42 -- 3.9 O-Cloud Performance Basic Concepts .....43 - - 3.9.0 Overview .....43 - - 3.9.1 O-Cloud Performance Measurements .....44 - - 3.9.2 Performance Indicators .....44 - - 3.9.3 Performance Metric .....44 - - 3.9.4 Performance Reports.....44 - - 3.9.5 Performance Management (PM) Job .....44 - - 3.9.6 Source of Truth .....45 - - 3.9.7 Performance Threshold.....45 - - 3.9.8 Performance Dictionary .....46 - - 3.9.9 Performance Measurement Operation Example .....46 - - 3.9.10 Performance Measurement Transformation.....47 - - 3.9.11 Retention Period .....48 -- 3.10 O-Cloud Operational Modes .....48 - - 3.10.1 Overview .....48 - - 3.10.2 Maintenance Mode .....48 - - 3.10.3 Test Mode .....49 -- Annex A (informative): O-Cloud and IMS Initialization .....50 - - A.1 Overview .....50 - - A.2 UML sequence diagram for O-Cloud and IMS initialization .....50 -- Annex B (informative): O-Cloud Resource View examples and operations that use these Views .....51 -- Annex C (informative): IMS example usage of ICS applied to ResourceTypes .....52 -- Annex D (normative): O-Cloud capabilities identification for use in LCM for the NF Deployment .....53 -- Annex (informative): Change history/Change request (history) .....54 - -# --- List of figures - -| | | -|-----------------------------------------------------------------------------------------------------|----| -| Figure 2.2-1 O-Cloud IMS and DMS Relationships to SMO ..... | 10 | -| Figure 2.2-2 O2 RP Service Based-Interfaces..... | 10 | -| Figure 3.1-1 O-Cloud Services, Interfaces, and High-Level Concepts ..... | 14 | -| Figure 3.2-1 O-Cloud Infrastructure Inventory ..... | 15 | -| Figure 3.2-2 Logical Clouds Example..... | 15 | -| Figure 3.3-1 Telemetry Types ..... | 16 | -| Figure 3.4-1 Diagram of kinds of Resources and examples of Resources ..... | 20 | -| Figure 3.4-2 Resource Views seen as different actor's perspective ..... | 21 | -| Figure 3.4-3 Resource Views – Abstracted & Assigned Resources Example..... | 23 | -| Figure 3.4-4 Hardware Layer Concepts ..... | 24 | -| Figure 3.4-5 Execution Environment Layer Concepts ..... | 25 | -| Figure 3.4-6 O-Cloud example with Local and Distributed Node Clusters ..... | 27 | -| Figure 3.4-7 Managed Infrastructure Template related parts and references in SMO and O-Clouds ..... | 29 | -| Figure 3.7-1 O2 Deployment LCM Services..... | 33 | -| Figure 3.8-1 Parallel Reporting & Alarm Correlation..... | 36 | -| Figure 3.8-2 Concept of Fault Domains ..... | 37 | -| Figure 3.8-3 Alarm Suppression Function ..... | 39 | -| Figure 3.8-4 Fault and Alarm Logging..... | 41 | -| Figure 3.9-1 Performance Measurement Reporting ..... | 43 | -| Figure 3.9-2 Performance Measurement Operation Example ..... | 46 | -| Figure 3.9-3 Semantic Performance Measurement Transformation Example..... | 47 | -| Figure A-1 O-Cloud and IMS Initialization ..... | 50 | -| Figure C-1 Example of ICS Concept Usage..... | 52 | - -# --- List of tables - -| | | -|----------------------------------------------------|----| -| Table 2.4-1: O2 related general requirements ..... | 11 | -|----------------------------------------------------|----| - -# Foreword - -This Technical Specification (TS) has been produced by WG6 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 Introduction - -## 1.1 Scope - -The present document specifies O-RAN O-Cloud functions and protocols for the O-RAN O2 interface. The document studies the functions conveyed over the interface, including management functions, procedures, operations and corresponding solutions, and identifies existing standards and industry work that can serve as a basis for O-RAN work. - -## 1.2 References - -### 1.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] Void. -- [2] O-RAN.WG1.TS.OAD: "O-RAN Architecture Description". -- [3] O-RAN.WG1.OAM-Architecture: "O-RAN Operations and Maintenance Architecture". -- [4] O-RAN.WG1.O1-Interface: "O-RAN Operations and Maintenance Interface". - -- [5] Void. -- [6] ONAP v7.2 May 2020: “VES Event Listener Specification”. -- [7] IETF RFC 6241 June 2011: “Network Configuration Protocol (NETCONF)”. -- [8] IETF RFC 7950 August 2016: “The YANG 1.1 Data Modeling Language”. -- [9] NIST SP 800-145 September 2011: “The NIST Definition of Cloud Computing”. -- [10] 3GPP TS 29.501: “5G System; Principles and Guidelines for Services Definition; Stage 3”. -- [11] ETSI GS NFV-SOL 013 (V4.5.1): "Network Functions Virtualisation (NFV) Release 4; Protocols and Data Models; Specification of common aspects for RESTful NFV MANO APIs". -- [12] ETSI GS NFV-SOL 015 (V1.2.1): "Network Functions Virtualisation (NFV); Protocols and Data Models; Specification of Patterns and Conventions for RESTful NFV-MANO APIs". -- [13] O-RAN.WG6.ORCH-USE-CASES-R004: “O-RAN Orchestration Use Cases and Requirements for O-RAN Virtualized RAN”. -- [14] 3GPP TS28.550: “Management and orchestration; Performance assurance”. -- [15] 3GPP TS28.531: “Management and orchestration; Provisioning”. -- [16] ETSI GS NFV-SOL003 (V4.5.1): “Network Functions Virtualisation (NFV) Release 4; Protocols and Data Models; RESTful protocols specification for the Or-Vnfm Reference Point”. -- [17] RFC 5424: “The Syslog Protocol”. -- [18] ETSI GS NFV-SOL 009 (V4.3.1): “Network Functions Virtualisation (NFV) Release 4; Protocols and Data Models; RESTful protocols specification for the management of NFV-MANO”. -- [19] ETSI GS NFV-IFA 036: “Network Functions Virtualisation (NFV) Release 4; Management and Orchestration; Requirements for service interfaces and object model for container cluster management and orchestration specification”. -- [20] IETF RFC8632 ISSN: 2070-1721 September 2019: “A YANG Data Model for Alarm Management”. -- [21] 3GPP TS32.111-2: “Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)”. -- [22] O-RAN.WG6.ASD: “O-RAN Application Service Descriptor specification”. -- [23] ETSI GS NFV-SOL 001 (V4.5.1): "Network Functions Virtualisation (NFV) Release 4; Protocols and Data Models; NFV descriptors based on TOSCA specification". -- [24] ETSI GS NFV-SOL 002 (V4.5.1): "Network Functions Virtualisation (NFV) Release 4; Protocols and Data Models; RESTful protocols specification for the Ve-Vnfm Reference Point". -- [25] ETSI GS NFV-SOL 004 (V4.4.1): "Network Functions Virtualisation (NFV) Release 4; Protocols and Data Models; VNF Package and PNFD Archive specification". -- [26] ETSI GS NFV-SOL 005 (V4.5.1): "Network Functions Virtualisation (NFV) Release 4; Protocols and Data Models; RESTful protocols specification for the Os-Ma-nfvo Reference Point". -- [27] ETSI GS NFV-SOL 006 (V4.3.1): "Network Functions Virtualisation (NFV) Release 4; Protocols and Data Models; NFV descriptors based on YANG Specification". -- [28] ETSI GS NFV-SOL 007 (V4.5.1): "Network Functions Virtualisation (NFV) Release 4; Protocols and Data Models; Network Service Descriptor File Structure Specification". -- [29] ETSI GS NFV-SOL 014 (V4.5.1): "Network Functions Virtualisation (NFV) Release 4; Protocols and Data Models; YAML data model specification for descriptor-based virtualised resource management". -- [30] ETSI GS NFV-SOL 018 (V4.5.1): "Network Functions Virtualisation (NFV) Release 4; Protocols and Data Models; Profiling specification of protocols and data model solutions for OS Container management and orchestration". - -- [31] ETSI GS NFV-SOL 020 (V4.5.1): "Network Functions Virtualisation (NFV) Release 4; Protocols and Data Models; Specification of protocols and data models for Container Infrastructure Service Cluster Management". -- [32] ETSI GR NFV-IFA 029 (V3.3.1): "Network Functions Virtualisation (NFV) Release 3; Architecture; Report on the Enhancements of the NFV architecture towards "Cloud-native" and "PaaS"". -- [33] ETSI GS NFV-IFA 040 (V4.5.1): "Network Functions Virtualisation (NFV) Release 4; Management and Orchestration; Requirements for service interfaces and object model for OS container management and orchestration specification". -- [34] ETSI GS NFV-IFA 036 (V4.5.1): "Network Functions Virtualisation (NFV) Release 4; Management and Orchestration; Requirements for service interfaces and object model for container cluster management and orchestration specification". -- [35] ETSI GS NFV-IFA 005 (V4.5.1): "Network Functions Virtualisation (NFV) Release 4; Management and Orchestration; Or-Vi reference point – Interface and Information Model Specification". -- [36] ETSI GS NFV-IFA 006 (V4.5.1): "Network Functions Virtualisation (NFV) Release 4; Management and Orchestration; Vi-Vnfm reference point – Interface and Information Model Specification". -- [37] ETSI GS NFV-SEC 021 (V4.5.1): "Network Functions Virtualisation (NFV) Release 4; Security; VNF Package Security Specification". -- [38] ETSI GS NFV-SEC 022 (V4.5.1): "Network Functions Virtualisation (NFV) Release 4; Security; Access Token Specification for API Access". -- [39] O-RAN.WG4.TS.CUS.0-R004-v17.00: "O-RAN Working Group 4 (Open Fronthaul Interfaces WG); Control, User and Synchronization Plane Specification". - -### 1.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] O-RAN.WG6.CADS: "O-RAN Cloud Architecture and Deployment Scenarios for O-RAN Virtualized RAN". - -## 1.3 Definition of terms, symbols and abbreviations - -### 1.3.1 Terms - -For the purposes of the present document, the terms [given in [i.1] and the following] apply: - -**Cloudified NF:** a RAN Network Function software that is deployed in the O-Cloud via one or more NF Deployments. - -**Deployment ID:** correlation identity created by the O-Cloud for the SMO to relate to its inventory and manage. - -**Deployment Management Services (DMS):** the DMS are the logical services provided by the O-Cloud providing for managing the life cycle of deployments which use cloud resources. - -**Federated O-Cloud Orchestration and Management (FOCOM):** the SMO treats the collection of O-Clouds as a single federated cloud. The FOCOM are the logical services provided by the SMO to manage the distribution of O-Cloud software and provides orchestration for O-Cloud life cycle processes. - -**Infrastructure Management Services (IMS):** the IMS are the logical services provided by the O-Cloud which provides the interface to orchestrate O-Cloud life cycle processes with the network functions it may be hosting and other operational procedures. - -**Managed Infrastructure Template (MIT):** a representation of the declarative target of a set of managed O-Cloud Resources, which defines its input parameters and indicate the known target characteristics of the provisioned O-Cloud Resources. - -**Network Function Orchestration (NFO):** the NFO are the logical services of the SMO which coordinates between the O-Cloud for managing deployment life cycle events, open loop, and closed loop operational procedures. - -**NF Deployment:** a software deployment on O-Cloud resources that realizes, all or part of, a Cloudified NF. - -**NF Deployment Descriptor:** a completed data model which provides an O-Cloud the necessary information to create a deployment. - -**O-Cloud:** a collection of O-Cloud Resources, Resource Pools and O-Cloud Services at one or more O-Cloud Sites including the software to manage O-Cloud Resource provisioning, Nodes, Clusters and Deployments hosted on them. - -**O-Cloud Node:** an O2ims exposed Abstracted Resource based on the Cloud infrastructure components. - -NOTE: Cloud infrastructure components typically comprised of physical and/or logical CPUs, Memories, Storages, NICs, HW Accelerators, etc. - -**O-Cloud Node Cluster:** a collection of O-Cloud Nodes that work in concert with each other, through a set of interconnecting O-Cloud Node Cluster Site Networks. - -**O-Cloud Platform:** a platform comprising hardware and software that provides O-Cloud capabilities and services to execute RAN network functions. - -### 1.3.2 Symbols - -Void - -### 1.3.3 Abbreviations - -For the purposes of the present document, the abbreviations [given in [i.1] and the following] apply: - -NOTE: An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in [i.1]. - -| | | -|-------|---------------------------------------------------------| -| API | Application Programming Interface | -| FCAPS | Fault, Configuration, Accounting, Performance, Security | -| KPI | Key Performance Indicators | -| MANO | Management and Orchestration | -| MOC | Managed Object Class | -| MOI | Managed Object Instance | -| NIC | Network Interface Card | -| O-RAN | Open Radio Access Network | -| ONAP | Open Network Automation Platform | -| OSM | Open Source MANO | - -| | | -|------|--------------------------------------| -| PM | Performance Management | -| PSM | Performance Subscription Manager | -| RAN | Radio Access Network | -| SMO | Service Management and Orchestration | -| T-BC | Telecom Boundary Clock | -| TR | Technical Report | -| TS | Technical Specification | - -# 2 General Aspects - -## 2.1 Introduction to O2 - -The O2 interface is an open logical interface within O-RAN architecture providing secured communication between the SMO and O-Cloud. It enables the management of O-Cloud infrastructures and the deployment life cycle management of O-RAN cloudified NFs that run on O-Cloud. The O2 interface is defined in an extensible way that enables new information or functions to be added without necessarily needing to change the protocol or the procedures. This interface enables a multi-vendor environment and is independent of specific implementations of the SMO and O-Cloud. - -## 2.2 Alignment with O-RAN Architecture - -This section provides any added detail not found in the high-level O-RAN architecture documents which define and describe the O2 interface. The intent is to extend knowledge and not to redefine existing information. Therefore, if a conflict exists between this document and the O-RAN Architecture Description [2] or the O-RAN OAM Architecture [3] the information presented will not supersede those documents. - -### 2.2.1 Alignment with Overall Architecture - -This document adopts the architecture as described in the O-RAN Architecture Description [2]. The O2 is described as the interface between the SMO and the O-Cloud to provide platform resources and workload management. - -The O-Cloud needs to be created before the SMO can interface with it. - -O-Cloud can consist of multiple Deployment Management Services. Each DMS can manage leased resources from multiple resource pools and span multiple locations. There is a single IMS for O-Cloud that manages all resources of DMSes as well as resources that are not allocated to any DMS in the O-Cloud. Diagram below depicts relationship between SMO and components of O-Cloud. - -![Diagram showing the relationship between Service Management & Orchestration (NFO, FOCOM), DMS, IMS, and O-Cloud resource pools.](2ba086df3506f81bae3a9b53725dcfea_img.jpg) - -### O-Cloud IMS & DMS relationships to SMO - -The diagram illustrates the O-Cloud IMS & DMS relationships to the SMO. At the top, the 'Service Management & Orchestration' layer contains two components: 'NFO' and 'FOCOM'. Below this, there are two main O-Cloud areas. The left O-Cloud area contains four 'DMS' boxes, each with three 'Lease' icons. Below these DMSes is an 'IMS' box. At the bottom, a large dashed box labeled 'O-Cloud' contains four 'Resource Pool' boxes (Resource Pool 1 @Location X, Resource Pool 2 @Location X, Resource Pool 3 @Location Y, Resource Pool n @Location Z). Each resource pool contains 'PhysicalResources' and 'Unprovisioned Resource' boxes. Arrows show connections from NFO to each DMS and IMS, and from FOCOM to the IMS. Within the O-Cloud, arrows show connections from DMSes to the IMS, and from the IMS to the resource pools. Each resource pool also has an arrow pointing to its corresponding 'PhysicalResources' box. The right O-Cloud area contains two 'DMS' boxes and an 'IMS' box, with arrows showing connections from FOCOM to the IMS, and from the IMS to the DMSes. - -Diagram showing the relationship between Service Management & Orchestration (NFO, FOCOM), DMS, IMS, and O-Cloud resource pools. - -**Figure 2.2-1 O-Cloud IMS and DMS Relationships to SMO** - -SMO can utilize blueprints or other pre-configuration templates to assign resources to resource pools and to assign resource to a DMS. - -Once the O-Cloud is operational the O-RAN Architecture Description [2] describes the functions to be performed over the O2 interfaces as: - -- O-Cloud Infrastructure Resource Management: - - O-Cloud infrastructure Discovery and administration - - O-Cloud infrastructure Scale-In, Scale-Out - - O-Cloud infrastructure FCAPS (PM, CM, FM, Communication Surveillance) - - O-Cloud infrastructure Platform Software Management -- Managing Abstracted Resources and DMSes: - - Creation, Scale-In, Scale-Out of abstracted assigned O-Cloud infrastructure resources - - Deployment FCAPS (PM, FM) for abstracted O-Cloud infrastructure resources - - Deployment DMS (Creation, Deletion and Lease of O-Cloud infrastructure) -- NF & Services Deployment Orchestration - - Deployment Software Management - - Deployment, Termination, Scaling, and Healing of NF & Services deployment resources - - FCAPS (PM, FM) for NF & Services deployment resources - -These functions fall into 3 categories: managing infrastructure, managing abstract resource and DMSes, and managing NF & Services life-cycle on the DMSs. - -These functions can be divided into two classes. Those which manage the infrastructure and those which manage deployments on that infrastructure. Therefore, the O-Cloud is logically composed of two functional blocks. The SMO has two logical blocks for the consumers of the O-Cloud services. The O2 as a Reference Point (RP) described in [10] are thus broken down into two (2) Service Based Interfaces (SBI) this decomposition is depicted in Figure 2.2-2 O2 RP Service Based-Interfaces - -![Diagram of O2 RP Service Based-Interfaces showing SMO and O-Cloud functional blocks and their interfaces.](54fabc351eda5228d2fa28cd9ba07971_img.jpg) - -The diagram illustrates the decomposition of the O2 Reference Point into two Service Based Interfaces (SBIs). At the top, the SMO (Service Management and Orchestration) block contains two functional components: 'Federated O-Cloud Orchestration and Management (FOCOM)' and 'Network Function Orchestration (NFO)'. At the bottom, the O-Cloud block contains 'Infrastructure Management Services (IMS)' and multiple 'Deployment Management Services (DMS)' units. A horizontal line labeled 'O2' separates the SMO and O-Cloud. An interface labeled 'O2ims' connects FOCOM to the IMS. Another interface labeled 'O2dms' connects NFO to the DMS units. A yellow callout box labeled 'Separation of Concerns boundary' points to the O2 line, indicating the logical separation between the SMO's orchestration functions and the O-Cloud's management functions. Brackets on the left side group the SMO and O-Cloud components under the heading 'Service Provider Functionality'. - -Diagram of O2 RP Service Based-Interfaces showing SMO and O-Cloud functional blocks and their interfaces. - -**Figure 2.2-2 O2 RP Service Based-Interfaces** - -The following are a description of the functional blocks identified in Figure 2.2-2 O2 RP Service Based-Interfaces - -- **Federated O-Cloud Orchestration and Management (FOCOM):** The FOCOM is responsible for accounting and asset management of the resources in the cloud. The FOCOM is the primary consumer of services provided by the - -IMS. The FOCOM has information about the O-Cloud resources management. Specifically, the FOCOM needs to know whether the services are within the operator domain or external. - -- **Network Function Orchestration (NFO):** The NFO is responsible for orchestrating the assembly of the network functions as a composition of NF Deployments in the O-Cloud. The NFO is the primary consumer of the DMS. -- **Infrastructure Management Services (IMS):** The IMS is responsible for management of the O-Cloud resources and the software which is used to manage those resources. The IMS generally provides services for consumption by the FOCOM. -- **Deployment Management Services (DMS):** The DMS is responsible for management of NF Deployments into the O-Cloud. It provides the ability to instantiate, monitor, and terminate NF Deployments. The DMS generally provides services for consumption by the NFO. - -### 2.2.2 Alignment with OAM Architecture - -This document adopts the O-RAN OAM architecture defined in [3], including the principles, requirements and reference architecture. It provides added detail on the use of the O2 Interface and associated functional blocks within SMO and O-Cloud. - -## 2.3 Technology Independence - -The intent of this specification is to keep it open and extensible such that it can adapt over time to technology not yet available. Therefore, functionality is described or cited with the intent to leverage open standards. There is a preference to reuse existing standards or open approaches such as Kubernetes and OpenStack. - -## 2.4 General Requirements - -The requirements below may be superseded in the O2 Specification as the interface evolves. - -**Table 2.4-1: O2 related general requirements** - -| Requirement ID | Requirement | Description | -|------------------------|-------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------| -| REQ-O2-GEN-SMO-FUN-1 | All SMOs (e.g., ONAP, OSM, etc.) shall support the O2 services and their requirements allocated to the role of the SMO. | SMO supports O2. | -| REQ-O2-GEN-OC-FUN-1 | All O-Cloud implementations shall support the O2 services, and their requirements allocated to the role of the O-Cloud. | O-Cloud supports O2. | -| REQ- O2-GEN-TLS-FUN-1 | Management Service providers and consumers that use TLS shall support TLS v1.2 or higher. | Communications between SMO and O-Cloud are secure. | -| REQ- O2-GEN-HTTP-FUN-1 | Management Service providers and consumers that use HTTP shall support HTTP v1.1 or higher. | HTTP minimum is v1.1. | - -## 2.5 Relationship with Existing Standards and Open Source Solutions - -The O-RAN O2 O-Cloud management services follow existing standards wherever possible. The focus of this document is to identify the use cases which conform to existing standards, identify gaps in management services for O-RAN and define needed extensions. For identified gaps, the goal is to modify the standards to include the needed O-RAN extensions and update the references in this document as the standards evolve to cover the gaps. If extensions and gaps are not specified, it is expected that the management services producers and consumers are conforming to referenced specifications. - -### 2.5.1 ETSI NFV - -This is a list of the relevant ETSI NFV standards documents which require evaluation in order to analyze packaging, LCM operations, and security for managing VMs and Containers. The versions will be specified in the O2 technical specification. - -ETSI NFV standards provide a common model for the management and orchestration of VNFs (both based on VMs and containers) and NSs, as compositions of VNFs and PNFs together with network constructs for their interconnectivity. - -NOTE 1: ETSI GS NFV-SOL XYZ specifications include stage 3 level specification, i.e., protocols and data models, while ETSI GS NFV-IFA XYZ specification concern stage 1 and 2 work, i.e., functional requirements, interface and information model and architecture specification. - -- ETSI GS NFV-SOL004 [25] standard is used for VNF and PNF packages. -- ETSI GS NFV-SOL007 [28] standard is used for NS package. -- ETSI GS NFV-SOL001 [23] standard is used to describe VNF, PNF, and NS in TOSCA. -- ETSI GS NFV-SOL 006 [27] standard is used to describe VNF, PNF, and NS in YANG. -- ETSI GS NFV-SOL003 [16] standard is used, primarily, for VNF, LCM and Monitoring (including fault, performance and VNF indicators). -- ETSI GS NFV-SOL 002 [24] standard is used for VNF/VNFC-level EM triggered scenarios (LCM, Fault, Performance, Configuration). -- ETSI GS NFV-SOL005 [26] standard is used for NS/PNF/VNF Package Management, NS/VNF LCM and Monitoring (including fault and performance), NFVI capacity information, and VNF snapshot package management. -- ETSI GS NFV-SEC 021 [37] standard specifies specific VNF Package security requirements, while ETSI GS NFV-SEC 022 [38] standard specifies specific API and interface security mechanisms. -- ETSI GS NFV-SOL 018 [30] standard is used for the OS container workloads management provided by so-called container infrastructures services management (CISM) function that concerns to DMS. The protocol and data model of ETSI GS NFV-SOL 018 [30] profiles Kubernetes®, Helm™ and OCI™ Distribution Specification API solutions to fulfil the OS container workload, compute, storage, network, and configuration management service interface requirements specified in the ETSI GS NFV-IFA 040 [33]. These specifications are based on the study analysis performed in the ETSI GR NFV-IFA 029 [32] on enhancements of the NFV architecture towards "Cloud-native" and "PaaS". -- ETSI GS NFV-SOL 020 [31] is used for the container infrastructure services (CIS) cluster management, which concerns the management of O-Cloud Node Clusters, as equivalent abstraction in the O-RAN's defined O-Cloud domain. The protocol and data model of ETSI GS NFV-SOL 020 [31] profiles the Cluster API solution to fulfil the CIS cluster management service interface requirements specified in the ETSI GS NFV-IFA 036 [34]. -- ETSI GS NFV-IFA 005/006 [35][36] covers topics Software Image Management, Virtual Resource Management (Information, Quota, Capacity, Change Notification, and Reservation) Virtual Resource Performance Management, Virtual Resource Fault Management and network forwarding path (NFP) management. ETSI GS NFV-SOL 014 [29] standard is used for the virtualised resource descriptors as input/output for the management of virtualised resources offered by the Virtualised Infrastructure Management (VIM) function that concerns to DMS. - -The O2 interfaces generally follow ETSI GS NFV-SOL 013 [11] section 8 for interface security. Further refinements will be based on recommendations from the WG11. - -NOTE 2: Other recommendations can be provided in future versions of the present document. - -Furthermore, clauses 5.2.2, 5.3, 5.4.2, 6, 6.4, 9.1, 9.2, 9.3 and 9.4 of ETSI GS NFV-SOL 013 [11] are referenced for the relevant O2ims and O2dms RESTful APIs. - -NOTE 3: Other sections of ETSI GS NFV-SOL 013 [11] are still under review and relevant recommendations can be provided in future versions of the present document. - -ETSI GS NFV-SOL 015 [12] provides RESTful Patterns. Section 5.9 defines the Subscribe-Notify pattern. Generally, this pattern is adopted by the O2, with the following caveats. - -- Notifications should indicate success or failure of the receipt of the notification to the notifying function. - -- The subscribe and POST may not be in the same service API. The typical pattern for the O2 is that the subscribe, or its equivalent, is in the O-Cloud services and the post for the notification is an SMO service. There are no existing use cases of notifications from the SMO to the O-Cloud. -- The event types may be extended over time. Therefore, the O-Cloud services should provide the ability to discover what event types the cloud instance supports. The minimal list of supported event types shall be: - - Inventory Change - - Configuration Change - - Fault Events - - Performance Reporting - - Heartbeat - -Another form of notification is the callback mechanism where the notify function is identified in the request. This mechanism is used in platform the software update procedure, as the cloud may not yet be configured for notifications when the update occurs. It is expected that all subscriptions and identified callbacks are persisted through a restart or a software update. - -### 2.5.2 IETF - -Not documented in the present document. - -### 2.5.3 3GPP - -The O2 interface is composed of services provided by the SMO and service provided by the O-Cloud. This closely resemble the Reference Points and Service Based Interface (SBI) definitions described in 3GPP TS 29.501 [10]. Therefore, this specification follows the intent of the practices defined in [10] but has modified it from its intended 5G Core implementation to align with the O-RAN O2 interface. - -### 2.5.4 Kubernetes - -Not documented in the present document. - -### 2.5.5 OpenStack - -Not documented in the present document. - -### 2.5.6 ONAP/OSM - -Not documented in the present document. - -# --- 3 O2 Interface General Principles - -## 3.1 O-Clouds - -O-RAN clouds are described in [i.2] as a distributed cloud composed of O-Cloud [Resource] Pools (as shown in the diagram below) where each pool is a collection of O-Cloud Resources within a Cloud Site with a specific location. An O-Cloud Node is the basic computational resource designator that is used to execute workloads and can be commonly thought of as a leased physical or logical server that is connected to the O-Cloud network. An Operator may have several O-Clouds from different vendors but will manage them as a single entity. These O-Clouds are viewed by the Service Management and Orchestration (SMO) Framework as a Federated O-Cloud. - -O-Cloud Nodes are provisioned (leased) from the O-Cloud Resource Pools, with assigned Operating System and Cluster software, into managed O-Cloud Node Clusters. The O-Cloud Nodes are commonly interconnected on the Cloud Site by the O-Cloud Node Cluster Site Networks that are provisioned from the O-Cloud Site Network Fabric (where available). The workloads (e.g., micro-services or Network Functions) are deployed on the O-Cloud Deployment Plane that is constituted by the set of available O-Cloud Node Clusters with its O-Cloud Nodes and O-Cloud Node Cluster Site Networks. - -O2 Infrastructure Management Services (IMS) are tailored for management and provisioning of O-Cloud Resources that are available for the SMO through the Federated O-Cloud Management (FOCOM) over O2ims. This includes allocation of the available O-Cloud Resources (e.g., Computes and Networks) into the O-Cloud Node Clusters and all cluster-wide operations on the O-Cloud Node Clusters throughout its complete life cycle. - -O2 Deployment Management Services (DMS) for NF Deployment lifecycle management can be discovered over O2ims. This NF Deployment lifecycle management is available for the SMO through the Network Function Orchestration (NFO) over O2dms. - -As introduced in the CADS [i.2], management of the Cloud Infrastructure where the O-Cloud is deployed is managed by the Cloud Infrastructure provider (operator internal or external). As a general concept the O-Cloud can be seen as having three functional planes that can use separate or shared resources. The control and management planes described below may be deployed on SMO-provisioned O-Cloud Nodes or outside the O-Cloud. The O-Cloud Nodes are associated with the functional plane they serve [indicated as M, C, D in the figure], to inform SMO of their roles. - -- Management Plane: O-Cloud Nodes serving this plane host functions which is responsible for managing the O-Cloud, i.e., IMS and the DMS functions (indicated as M in the figure) -- Control Plane: O-Cloud Nodes serving this plane host the functions which manages the resources assigned in the deployment plane to specific deployment instances (indicated as C in the figure) -- Deployment Plane: O-Cloud Nodes and O-Cloud Node Cluster Site Networks serving this plane are used to host O-Cloud NF Deployments (indicated as D in the figure) - -![Figure 3.1-1 O-Cloud Services, Interfaces, and High-Level Concepts. This diagram illustrates the O-Cloud architecture layers. At the top, FOCOM (O-Cloud Provisioning & LCM) and NFO (Workload Homing to O-Cloud and DMS) are shown. FOCOM connects to the Infrastructure Management Services (IMS) via the O2ims interface. NFO connects to the Deployment Management Services (DMS) via the O2dms interface. The IMS layer includes SW Repo, OS iso, and Node [M] OS. The DMS layer includes Node [M] OS and Node [C] OS. The Deployment Plane is divided into Workload Deployment, NF Part Deployment, and NF Deployment. It shows Node Cluster Site Networks, Distributed Node Cluster Networks, and Node Clusters. The bottom layer shows Resource Pools (Storage, Compute) and Cloud Sites (Unspecified Resource Pool, Site Network Fabric, Site Gateway). A Cloud Infrastructure Management box on the left indicates the Cloud Provider's management of internal Cloud Infra resources and settings. The diagram also shows a 'Distributed O-Cloud' and 'Distributed across locations'.](1b5a812c8aa20fd5cba28e97001d32de_img.jpg) - -Figure 3.1-1 O-Cloud Services, Interfaces, and High-Level Concepts. This diagram illustrates the O-Cloud architecture layers. At the top, FOCOM (O-Cloud Provisioning & LCM) and NFO (Workload Homing to O-Cloud and DMS) are shown. FOCOM connects to the Infrastructure Management Services (IMS) via the O2ims interface. NFO connects to the Deployment Management Services (DMS) via the O2dms interface. The IMS layer includes SW Repo, OS iso, and Node [M] OS. The DMS layer includes Node [M] OS and Node [C] OS. The Deployment Plane is divided into Workload Deployment, NF Part Deployment, and NF Deployment. It shows Node Cluster Site Networks, Distributed Node Cluster Networks, and Node Clusters. The bottom layer shows Resource Pools (Storage, Compute) and Cloud Sites (Unspecified Resource Pool, Site Network Fabric, Site Gateway). A Cloud Infrastructure Management box on the left indicates the Cloud Provider's management of internal Cloud Infra resources and settings. The diagram also shows a 'Distributed O-Cloud' and 'Distributed across locations'. - -Figure 3.1-1 O-Cloud Services, Interfaces, and High-Level Concepts - -## 3.2 O-Cloud Inventory - -### 3.2.0 Overview - -From the perspective of the SMO, O-Cloud Inventory consists of the exposed O-Cloud Resources based on the physical and logical Cloud Infrastructure resources, the logical clouds which it provides as interfaces for deployments, and the inventory of deployments using the logical clouds. One of the responsibilities of the SMO is for “financial” accounting of the physical and - -logical inventory. The SMO inquires about the mapping of resources to their use. The O-Cloud is responsible for the assignment of resources to their use. Typically, the O-Cloud inventory is the result of the SMO provisioning requests and assignments of O-Cloud Resources with additions of O-Cloud internal status of the existing internal resources, e.g., if some of the resources are down due to faults or maintenance operations. - -### 3.2.1 Infrastructure Inventory - -Infrastructure inventory is passed between the O-Cloud and the SMO over the O2ims. An O-Cloud Resource Identifier is used to correlate the inventory. This identifier needs to be discoverable by the O-Cloud and would likely be on an “invoice” for the O-Cloud “purchase order” or whatever method that is applied to account for requested resources. The O-Cloud Resource Identifier is to be immutable. - -The IMS will add O-Cloud Resources to the relevant O-Cloud Resource Pool(s) when they are ready to be provisioned as an O-Cloud Resource. The IMS can then allocate the available O-Cloud Resources to O-Cloud Nodes and O-Cloud Site Networks when there are needs in the O-Cloud Node Clusters. SMO is then notified or can discover the O-Cloud Node, O-Cloud Node Cluster Site Network and O-Cloud Node Cluster. - -The SMO receives O-Cloud Resources startup events and updates its inventory accordingly. The O-Cloud Resource Identifier is matched with “invoice” data in order to provide “financial” asset tracking reports or similar assurance reports. The location and use identifiers are used to track inventory which will be monitored as part of cloud service assurance. - -![Figure 3.2-1 O-Cloud Infrastructure Inventory diagram showing Service Provider Functionality (FOCOM) connected to multiple Cloud Provider Functionality blocks via O2ims interfaces. Arrows indicate Physical/Logical Inventory and Provisioning/Maintenance flows.](bffdddb47fced140f8d17fdc2a29f592_img.jpg) - -The diagram illustrates the infrastructure inventory flow. At the top, 'Service Provider Functionality' contains a 'FOCOM' block. Below it, a dashed line separates this from the 'Cloud Provider Functionality' section. Multiple 'Cloud Provider Functionality' blocks are shown, each containing 'O2 Cloud Provider Infrastructure Management Services'. These blocks are connected to the FOCOM via 'O2ims' interfaces. On the left, an upward arrow labeled 'Physical/Logical Inventory' points from the cloud provider to the service provider. On the right, a downward arrow labeled 'Provisioning/Maintenance' points from the service provider to the cloud provider. - -Figure 3.2-1 O-Cloud Infrastructure Inventory diagram showing Service Provider Functionality (FOCOM) connected to multiple Cloud Provider Functionality blocks via O2ims interfaces. Arrows indicate Physical/Logical Inventory and Provisioning/Maintenance flows. - -Figure 3.2-1 O-Cloud Infrastructure Inventory - -### 3.2.2 Logical Inventory - -The O-Cloud itself needs to have one or more DMS available within its distributed footprint to enable NF Deployments. These could be based on different virtual cluster technologies e.g., Kubernetes/Docker and Open Stack. Each DMS endpoint provides an O2dms interface and is inventoried by the SMO as a Logical Cloud. The Logical Cloud and its Cloud Site locations are used by the SMO in order to select the O-Cloud to be used for a deployment during the Logical Cloud selection process. - -![Figure 3.2-2 Logical Clouds Example diagram showing Service Provider Functionality (NFO) connected to IMS Functionality blocks containing DMS (OpenStack, Kubernetes, Distributed Cluster) and Resource Pools. Annotations explain the separation of concerns and the appearance of O2dms endpoints as logical clouds.](3f1987804d7d78bc3b3bc560e974280a_img.jpg) - -This diagram shows the logical inventory structure. 'Service Provider Functionality' at the top contains an 'NFO' block. Below it, 'IMS Functionality' blocks are shown. Each IMS block contains 'DMS' (Distributed Management Service) units, such as 'OpenStack Cluster', 'Kubernetes Cluster', or 'Distributed Cluster on Cloud Site 2 and 3'. Each DMS unit is associated with 'Resource Pool' blocks and a specific 'Cloud Site' (e.g., 'Cloud Site 1 @Location 1'). Annotations include: '2 O-Clouds with presence at 3 Cloud Sites with a total of 6 Resource Pools and 4 DMS Services appearing as Logical Clouds'; 'Separation of Concerns boundary' between NFO and IMS; 'O2dms end point appears as a Logical Cloud to the SMO for VNF Homing and NF Orchestration'; and 'Resource Pool with a global unique Cloud Site ID'. At the bottom, labels identify 'Single Site O-Cloud' and 'Distributed O-Cloud'. - -Figure 3.2-2 Logical Clouds Example diagram showing Service Provider Functionality (NFO) connected to IMS Functionality blocks containing DMS (OpenStack, Kubernetes, Distributed Cluster) and Resource Pools. Annotations explain the separation of concerns and the appearance of O2dms endpoints as logical clouds. - -Figure 3.2-2 Logical Clouds Example - -### 3.2.3 Deployment Inventory - -Although the cloud could support IaaS and PaaS deployments, most O-RAN MEs are composed of SaaS deployments as defined by NIST [9]. The Deployment Descriptor is a set of metadata contained in a datatype matching a capability advertised by the O-Cloud. Logical Cloud selection in the NFO will match the descriptor type with the capability type to enable deployment. The Deployment Descriptor will cause one or more cloud resources to be allocated (VMs, Pods, Containers, Networks) but will return a single correlation ID, referred to here as the Deployment ID. The O-Cloud will provide, over the O2dms, the ability to fetch the details of these objects from their Deployment ID. - -## 3.3 O-Cloud Monitoring Service - -### 3.3.0 Overview - -When the O-Cloud Infrastructure or the ORAN cloudified NFs fails, it needs to be fixed immediately, and preferably automatically, to prevent end users from experiencing service disruptions. To avoid this service disruption Network Operations must consider the telemetry information of O-Cloud deployments in the network. The telemetry information serves as a vital resource for analysing the O-Cloud's state and health, and for delivering on service monitoring goals. - -The O-Cloud Monitoring Service uses telemetry data to provide monitoring of O-Cloud infrastructures. The telemetry data is provided by Deployments and Infrastructure and is correlated to reduce duplication of effort in determining the root cause in the network. - -There are different types of telemetry, Managed Element Telemetry, Deployment Telemetry, and Infrastructure Telemetry. - -1. For Managed Element Telemetry, the objective is to monitor the application behaviour. This will be addressed in the O1 Specification [4]. -2. For Deployment Telemetry, the objective is to monitor the number of deployment instances an O-Cloud has at that moment and how many were expected, how the on-progress deployment is going, and health checks. Additional Deployment Telemetry metrics like CPU, network, and memory usage can also be collected. This will be addressed in the O2 Specification. -3. For Infrastructure Telemetry, the objective is to monitor the health of the O-Cloud Infrastructure components. Network Operations are interested in discovering if all the components in the O-Cloud Infrastructure are working properly and at what capacity, how many deployments are running on each node, and the resource utilization of the O-Cloud Infrastructure. This will be addressed in the O2 Specification. - -![Diagram illustrating Telemetry Types. It shows three levels of monitoring: Managed Element Telemetry (top level with four 'Deployment' icons), Deployment Telemetry (middle level with four server icons), and Infrastructure Telemetry (bottom level with a rack of server units). Arrows on the left point to each level, and the background is divided into three horizontal color-coded sections: blue for Managed Element, yellow for Deployment, and light blue for Infrastructure.](f57a881fcbcaf494a7dedc4f61224991_img.jpg) - -Diagram illustrating Telemetry Types. It shows three levels of monitoring: Managed Element Telemetry (top level with four 'Deployment' icons), Deployment Telemetry (middle level with four server icons), and Infrastructure Telemetry (bottom level with a rack of server units). Arrows on the left point to each level, and the background is divided into three horizontal color-coded sections: blue for Managed Element, yellow for Deployment, and light blue for Infrastructure. - -Figure 3.3-1 Telemetry Types - -### 3.3.1 General Capabilities - -Business Capabilities: - -- As Network Operations I need telemetry data from Network Functions in order to provide service assurance of the network (Note: This is assumed to be handled by the O1) -- As Network Operations I need telemetry data from the infrastructure in order to provide service assurance of the network -- As Network Operations I need to be able to correlate Network Function Telemetry and Infrastructure Telemetry in order to reduce duplication of effort in determining one root cause - -Functional Capabilities: - -- The SMO shall be able to correlate ME telemetry to Infrastructure and Deployment telemetry to aggregate problems to a root cause -- The O-Cloud shall be able to make all Configuration Data and any external changes to it available to the SMO -- O-Cloud telemetry shall minimally consist of Fault, Performance, and Configuration Data -- The SMO shall be able to correlate a Managed Element to its deployment components -- The O-Cloud shall be able to report telemetry of deployment resources relative to those identified in the deployment descriptor -- The O-Cloud shall be able to report Infrastructure telemetry and identify the deployments using the resource -- O-Cloud shall provide the collection and reporting of performance information of O-Cloud resources -- O-Cloud shall support the capability to notify about the availability of performance information -- O-Cloud shall expose the type of performance information that can be collected for the allocated O-Cloud resource(s) -- O-Cloud shall expose the type of O-Cloud resource, for which the performance information can be collected -- O-Cloud shall provide the collection of fault information for O-Cloud resources -- O-Cloud shall support providing notification of fault information related to O-Cloud resources - -## 3.4 O-Cloud Provisioning - -### 3.4.0 Overview - -O-Cloud Provisioning is the allocation and configuration of O-Cloud Resources and Services to an O-Cloud Node, Node Group, Node Cluster Site Network, Node Cluster and/or Logical Cloud (as represented by a DMS). This is one of the key functionalities of the O-Cloud, relating to how an O-RAN Cloudified Network Function or part thereof can be deployed on the O-Cloud services and resources. The O-Cloud resources are deployed flexibly over the distributed O-Cloud Sites to match the O-RAN Cloudified Network Function's fluctuating demands. The O-Cloud Node Clusters and Logical Clouds typically scale out using additional O-Cloud Resources to accommodate spikes in usage and scale in by releasing the used O-Cloud Resources when demands decrease. O-Cloud Provisioning enables numerous benefits including scalability, speed, and cost saving. - -To support the deployments, O-Cloud Provisioning will need to provide several functionalities. There will be initial support for the following: - -- Affinity, Anti-Affinity, Quorum Diversity Rules -- Capacity Query -- Availability Query -- Managed O-Cloud Node Clusters and Logical Clouds - - Creation, Deletion, and Scaling for Cloud Site localized Clusters - -- Identification of the O-Cloud Capabilities which are relevant for NF Deployments, that realize, all or part of, a Cloudified NF, as defined in Annex D - -Support for the following functionalities is not addressed by the present version of the specification: - -- Subscriptions -- Flavor Management -- Server Group Management -- Capabilities Discovery -- Switch Fabric Management -- O-Cloud Gateway Management -- Managed O-Cloud Node Clusters and Logical Clouds for distributed Clusters over multiple Cloud Sites -- Quota Management -- Resource Performance Management -- Virtual Resource Performance Management - -### 3.4.1 Affinity, Anti-Affinity, Quorum Diversity Rules - -#### 3.4.1.0 Overview - -An Affinity rule specifies that deployments with the same rule applied must be collocated within the same scope. This can be applied to a single O-Cloud Node or an O-Cloud Node Group. Anti-Affinity is the opposite of the Affinity Rule in that deployments with the same rule applied cannot be collocated within the same scope. Affinity and Anti-Affinity rules can be applicable to entities outside of the current deployment such as Tenant or Namespace. - -A Quorum diversity rule stipulates that deployments with this rule can be collocated if less than 50% of the deployments exist within the same scope. This rule can only be enforced when there is a minimum of 3 deployments. In which it will be the same deployment assignment as Anti-Affinity. In scenarios with more than 3 deployments a minimum of 3 different resource assignments at the specified scope (O-Cloud Nodes or O-Cloud Node Group) will be used. More can be used at the discretion of the O-Cloud Resource Scheduler. - -#### 3.4.1.1 General Capabilities - -Business Capabilities: - -- Network Function Orchestration (NFO) shall be able to apply Affinity, Anti-Affinity, Quorum Diversity rules over the O2dms interface - -Functional Capabilities: - -- O-Cloud Provisioning shall provide Create rule for Affinity, Anti-Affinity, and Quorum Diversity -- O-Cloud Provisioning shall provide Read rule for Affinity, Anti-Affinity, and Quorum Diversity -- O-Cloud Provisioning shall provide Update rule for Affinity, Anti-Affinity, and Quorum Diversity -- O-Cloud Provisioning shall provide Delete rule for Affinity, Anti-Affinity, and Quorum Diversity -- O-Cloud Provisioning shall provide NFO with means to perform NF Deployments according to rules for Affinity, Anti-Affinity, and Quorum Diversity - -### 3.4.2 O-Cloud Capacity and Availability - -#### 3.4.2.0 Overview - -Cloud Infrastructure Providers install and configure the available O-Cloud Resources for an O-Cloud. O-Cloud Resources are allocated to O-Cloud Node Clusters and configured by the IMS to enable NF Deployments by the DMS where each DMS may have a different distribution of Capacity, and Availability. - -The O-Cloud Capacity is the number of exposed O-Cloud Resources of each ResourceType that can be allocated or reserved for O-Cloud Node Clusters. The O-Cloud Availability is the currently free number of exposed O-Cloud Resources of each ResourceType that is not allocated or reserved. The Capacity may be larger than the sum of available exposed physical resources if the O-Cloud allows oversubscription. - -#### 3.4.2.1 General Capabilities - -Business Capabilities: - -- Network Operations shall be able to view the Capacity and Availability of an O-Cloud - -Functional Capabilities: - -- O-Cloud Provisioning shall provide Query of O-Cloud Capacity -- O-Cloud Provisioning shall provide Query of O-Cloud Capacity allocations and reservations -- O-Cloud Provisioning shall provide Query of O-Cloud Availability - -### 3.4.3 O-Cloud Provisioning Basic Concepts - -#### 3.4.3.0 Overview - -These basic concepts will become relevant moving from the traditional RAN paradigm of total network and resource ownership to cloudified networks where there are more stakeholders, and the resources are shared amongst stakeholders. This section will describe basic concepts related to provisioning in the context of IMS and DMS. This section will elucidate that the IMS and DMS have a difference in kind. Provisioning is basic OA&M functionality. The concepts described here will motivate the development of O-Cloud O2 IMS & DMS provisioning service modelling, and information modelling. - -Provisioning in the context of the GA&P is the act of providing access to entities, e.g., resources. - -The general concepts described here relate to O-Cloud entities as well as provisioning functionality. The subsections group together like concepts. - -#### 3.4.3.1 Workload - -A workload is any software application(s) that consumes an Abstracted Resource (as defined in this document). - -For example, this workload could be a Host Operating System, Guest Operating System, micro-service, or the software part of a Physical Network Function (PNF), Virtualized Network Function (VNF) or Cloud Native Network Function (CNF) which would typically be deployed by a DMS. - -#### 3.4.3.2 Resource Related Concepts - -##### 3.4.3.2.1 Resource - -An O-Cloud Resource is defined in an O-Cloud infrastructure as one that may be provisioned and managed through an abstraction. O-Cloud infrastructure has two kinds of resources: physical and logical resources. A physical resource is defined as a kind of resource that has a manifestation in the real world. A logical resource is defined as a kind of resource that uses a number of physical resources, or a portion of physical resources, or a number of software entities. A resource can be assigned to an orchestrator that will deploy workloads for resource consumption (see figure 1). - -For example, some kinds of physical resources could be servers, switches, and storage units. - -For example, some kinds of logical resources are Openstack and K8S clusters. - -![Diagram of kinds of Resources and examples of Resources. It shows three categories: Managed O-Cloud Service, Logical Resource, and Physical Resource, each with associated examples. Managed O-Cloud Service examples include Boot Service, Upgrade Service, and Management Service. Logical Resource examples include Container Cluster, VM Cluster, and Site Network. Physical Resource examples include Computer System, HW Accelerator, and Site Network Fabric. The categories are grouped into Resource Pools.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg) - -The diagram illustrates the classification of resources into three main categories, each with its own set of examples: - -- Managed O-Cloud Service** (Examples: Boot Service, Upgrade Service, Management Service) -- Logical Resource** (Examples: Container Cluster, VM Cluster, Site Network) -- Physical Resource** (Examples: Computer System, HW Accelerator, Site Network Fabric) - -The Managed O-Cloud Service, Logical Resource, and Physical Resource categories are grouped into separate **Resource Pools**. - -Diagram of kinds of Resources and examples of Resources. It shows three categories: Managed O-Cloud Service, Logical Resource, and Physical Resource, each with associated examples. Managed O-Cloud Service examples include Boot Service, Upgrade Service, and Management Service. Logical Resource examples include Container Cluster, VM Cluster, and Site Network. Physical Resource examples include Computer System, HW Accelerator, and Site Network Fabric. The categories are grouped into Resource Pools. - -Figure 3.4-1 Diagram of kinds of Resources and examples of Resources - -##### 3.4.3.2.2 Managed O-Cloud Service - -A Managed O-Cloud Service is an exposed, provisioned, monitorable, or managed entity that performs some operations for a client or consumer. A Managed O-Cloud service is an entity that provides some functionality to other entities. Managed O-Cloud Services could execute on physical and/or logical cloud infrastructure resources thereby consuming cloud infrastructure resources not usable by the O-Cloud. Managed O-Cloud Services could also execute outside of the cloud infrastructure resources. Unlike logical services, Managed O-Cloud Services are created on demand ad infinitum. The IMS is the management endpoint for the Managed O-Cloud Service. - -NOTE: Exposure means it is visible outside of the IMS through the IMS endpoint as a managed object; thus, the SMO is aware of it. - -For example, an autonomous service as a managed O-Cloud service, which as a plug-in to the cloud that performs some unique functions upon resources. - -For example, some kinds of Managed O-Cloud service might be boot services, upgrade services, and DMS. - -#### 3.4.3.3 Resource Views - -##### 3.4.3.3.0 Overview - -A *Resource View* is defined as the visible and/or accessible part of the Resource that an actor sees based on their authority. Resources are seen by different actors that need to manage or act upon resources. Different perspectives from these actors are “views” of the Resources. O-Clouds can have multiple Resource Views to enable separation of authority and operations of the resources, into logical groups of actors (generally other SW entities). The four kinds of O-Cloud resource views are: *Cloud Infrastructure Resource*, *Abstracted Resources*, *Assigned Resource*, and *Consumed Resource*. This is done to provide maximum separation of concern between different actors. These views accommodate public, external, and shared private cloud deployments. - -For example, Consider a hotel room as a resource. The front desk staff who assigns a room to a tenant has a relationship to the room and job requirements of how to manage the room. That is, they have a “view” of the room. The tenant that checks into the room has a different “*resource view*” of that same room. The cleaning staff has yet another relationship, or “*resource view*”, to the same hotel room. - -![Diagram showing different actor perspectives on a central 'RESOURCE' block. A red 'Workload' icon points down to the top of the resource. A yellow 'FOCOM (SMO)' icon points to the left side. A blue 'NFO (SMO)' icon points to the right side. A green 'Infrastructure Manager' icon points to the bottom. Each actor has a magnifying glass over a different part of the resource, with a callout box stating 'Each actor has a different perspective of the resource'.](c5655e700cc3e9aac7e9f4f07f30264d_img.jpg) - -Diagram showing different actor perspectives on a central 'RESOURCE' block. A red 'Workload' icon points down to the top of the resource. A yellow 'FOCOM (SMO)' icon points to the left side. A blue 'NFO (SMO)' icon points to the right side. A green 'Infrastructure Manager' icon points to the bottom. Each actor has a magnifying glass over a different part of the resource, with a callout box stating 'Each actor has a different perspective of the resource'. - -Figure 3.4-2 Resource Views seen as different actor's perspective - -##### 3.4.3.3.1 Cloud Infrastructure Resource View (Green) - -The Cloud Infrastructure Resource view is a resource view of a resource that is managed by Cloud internal physical, software and tool components. Cloud Infrastructure Resource can also be composed of other Cloud Infrastructure Resources and services. These can be used to compose or expose Abstracted Resources. The Cloud Infrastructure Resources are typically provided by the Internal, External or Public Cloud Providers. - -NOTE: The cloud infrastructure manager (green) is often implemented by a different organization than the FOCOM organization (yellow). - -For example, a resource view of the Cloud Infrastructure Resource might have a computer, storage, acceleration, network hardware, and software implementing certain services from a public cloud provider. This is the hardware foundation in any sort of data center that serves as the hardware infrastructure. - -##### 3.4.3.3.2 Abstracted Resource View (Yellow) - -An Abstracted Resource View is a Resource View of a composed Cloud Infrastructure Resource (with a provisioning reference tag) that is offered through Provisioning. Abstracted Resources thereby map underlying cloud infrastructure resources (act of composing). The Abstracted Resource View is a perspective on the actual Abstracted Resources. This abstraction facilitates assigned users to perform their authorized management and LCM operations for these resources. The SMO sends the objectives to the IMS, which are the SMO requirements for Abstracted Resources that are being requested from IMS. See the figure below on “Resource views: abstracted and assigned resources”. - -NOTE: The act of composing a Cloud Infrastructure Resource could be as simple as finding suitable resources and tagging it as an Abstracted Resource. - -For example, an Abstracted Resource View might contain a set of available computer systems and a K8S cluster that are composed by the cloud infrastructure. The Computer Systems are referenced with an abstraction identifier (assigned by the cloud owner) and the underlying physical compute resources are not exposed. The K8S Cluster is also referenced with an abstraction identifier and the underlying compute, network and storage resources are generally not exposed. Some examples of operations on Abstracted Resources include listings of available resources and booking of available resources. For the logical resource e.g., the K8S Cluster other common operations would also include creation, scaling, update, and deletion of the cluster. - -##### 3.4.3.3.3 Assigned Resource View (Blue) - -**An Assigned Resource View is a Resource View of an Abstracted Resource provisioned to the SMO that can prepare and adapt the resource(s) for Workload placement and consumption including its related FM and PM interfaces. The IMS assigns resources to the cluster and reports to the SMO. The Assigned Resources are the Abstracted Resources that the O-Cloud assigns in order to fulfill a SMO request for resources (see example in Figure 3.4-3 Resource Views – Abstracted & Assigned Resources Example** - -). When requests are fulfilled, the bookkeeping of Assigned Resources and Cloud Infrastructure Resources is done by the O-Cloud IMS. See the figure below on “Resource views: abstracted and assigned resources”. - -For example, the Assigned Resource View might present one or many K8S cluster(s) and other sorts of resources as an Assigned Resource. Some examples of workload orchestration that can be performed on Assigned Resources are cluster preparation for the workload, placement (deployment) of workloads, and scaling of the workload on the cluster. - -For example, consider a rental car as a resource. The Vehicle Identification Number (VIN) is associated with the car. The rental company has a rental agreement number for the same car. The person who rents the car has an entitlement according to the rental agreement using the rental agreement number that is not tied to the VIN. In this case, the rental agreement number is a representation of the car an Abstracted Resource. The renter views the car as an Assigned Resource. At any point in the time, the VIN & agreement number are linked, however, the link can be changed over time. For instance, car #1 breaks down and the rental agreement becomes associated to a new car #2 with a new VIN associated with car #2 all under the same rental agreement number. This illustrates how FOCOM gets Abstracted Resources and hands it to NFO as Assigned Resources. - -##### 3.4.3.3.4 Consumed Resource View (Red) - -Workload Consumed Resources View is a resource view that describes the workloads software program execution in the CPU; acceleration execution in the dedicated HW accelerator; as well as packet classification, manipulation and forwarding in a packet forwarding device. - -For example, the Operating System that consumes CPU instruction resources from the Computer System or Virtual Machine expect to acquire CPU metrics based on information to its OS drivers to offer its built-in performance management services e.g., the common OS TOP commands that indicates how the CPU resources are consumed. - -![Diagram illustrating the flow from Service Management Orchestrator (SMO) to IMS and DMS for resource management.](d734a6ea1b381280f043fcf70391b6db_img.jpg) - -The diagram shows the flow of resource management within the O-RAN architecture. At the top, the **Service Management Orchestrator (SMO)** contains **FOCOM** (Federation Controller) and **NF** (Network Function). An arrow labeled **Assignments** points from FOCOM to NF. Below FOCOM, an **Objectives** icon points down to the **IMS** (Inventory Management System). Below NF, an arrow points down to the **DMS** (Distributed Management System). The IMS is associated with **Provisioning Abstracted resources** and **Abstracted Resources**, which include **Physical Resource**, **Logical Resource**, and **Managed O-Cloud Service**, collectively forming a **Resource Pool**. The DMS is associated with **Prepare, Place, Scale workloads on assigned resources**, which include **Node Cluster**, **Node**, and **Node Cluster Networks**, collectively forming **Assigned Resources**. A large arrow labeled **IMS Cluster Creation use Abstracted Resources that are Assigned to Node Clusters exposed through DMS for Workload placement** points from the IMS to the DMS. - -Diagram illustrating the flow from Service Management Orchestrator (SMO) to IMS and DMS for resource management. - -Figure 3.4-3 Resource Views – Abstracted & Assigned Resources Example - -#### 3.4.3.4 Hardware Layer Concepts - -##### 3.4.3.4.0 Overview - -At the foundation of a cloud is the physical hardware with physical computers to execute workloads on and some networks to interconnect the computers with each other. In the real world there are also many different provider organizations that need clear boundaries of their responsibilities e.g., between the cloud infrastructure and the outside world that will be served by the cloud infrastructure and its workloads. There is also a need to house the physical computers, networks, and other related equipment in some physical enclosure. - -As introduced in the CADS [i.2] a Cloud Site is a physical place that has Cloud Infrastructure equipment that can be used to provide O-Cloud Resources that are abstracted from the actual physical realization. This enables O-Cloud to lease out O-Cloud Resources through the IMS, based on Cloud Infrastructure physical resources on the Cloud Sites that serves the distributed O-Cloud. - -From an SMO point of view, it is important to understand the basic concepts of the hardware layer, not from the realization point of view, but from the O-Cloud Resource locations, capabilities, capacity, availability, and potential disturbances (e.g., at faults or maintenance operations) points of view. - -##### 3.4.3.4.1 Computer System - -A Computer System is defined to be a physical or composed system capable of performing computations and is also connected to the Site Network Fabric enabling the Computer System to work in a cloud and act as part of a cluster. The Computer System typically includes one or more main CPUs with their memory subsystems, Network Interfaces Controllers (NIC) and sometimes also Storage drives and HW Accelerators. See diagram 4: “Hardware Layer Concepts”. If the Computer System realizes an O-Cloud Node that performs the role of Telecom Slave Clock (T-TSC) LLS-C3 or Telecom Boundary Clock (T-BC) LLS-C1/C2, such Computer System shall embed high speed and low latency NIC(s) with support for PTP Hardware Clock (PHC). - -A Computer System can run any major Operating System with or without Virtualization and/or Container support functionality. - -For example, a server in a data centre connected to a Site Network Fabric. - -![Figure 3.4-4 Hardware Layer Concepts diagram showing Computer Systems, Site Network Fabric, and Site Gateway components.](366a77fdefb0097b3289b4a011911390_img.jpg) - -The diagram illustrates the hardware layer concepts within a Cloud Site. It is divided into three main components: - - -- Computer System:** Represented by a light blue rounded rectangle containing two server icons. A green label 'Computer System' points to this box. -- Site Network Fabric:** Represented by a light orange rounded rectangle containing a desktop computer icon. A green label 'Site Network Fabric' points to this box. -- Site Gateway:** Represented by a blue circular icon containing a router icon. A green label 'Site Gateway' points to this icon. - - Connections are shown as blue arrows: - - -- Two arrows originate from the 'Computer System' box and point to the 'Site Network Fabric' box. -- One arrow originates from the 'Site Network Fabric' box and points to the 'Site Gateway' icon. - -Figure 3.4-4 Hardware Layer Concepts diagram showing Computer Systems, Site Network Fabric, and Site Gateway components. - -**Figure 3.4-4 Hardware Layer Concepts** - -##### 3.4.3.4.2 Site Network Fabric - -A Site Network Fabric is a physically connected network on a Cloud Site enabling Computer Systems to communicate with each other and with the Gateway(s) connected to networks outside of the Cloud Site. - -The Site Network Fabric generally limits how far Layer 2 connectivity can span without being routed or bridged over external routed networks that will normally change the connection characteristics in the form of longer access times. For Full Timing Support networks (refer to clauses 11.2.3 and 11.2.4.2.1 in O-RAN.WG4.TS.CUS.0-R004-v17.00 [39], the Site Network Fabric shall support PTP in order to act as T-BC or Telecom Transparent Clock (T-TC). - -For very small Cloud Sites the Site Network Fabric realization can be collapsed to the direct links between the Computer Systems and the Gateways which then are to be treated as fixed connections. - -The Site Network Fabric can provision O-Cloud Site Networks as a special type of O-Cloud Resources that can interconnect pooled O-Cloud Resources with each other on the physical level e.g., Computer Systems and Gateways. - -##### 3.4.3.4.3 Site Gateway - -A Site Gateway (as can be seen in figure 3.4-4) are commonly placed between each Cloud Site and the externally provided transport network to ensure a clear separation of cloud internal and cloud external traffic in terms of security, traffic treatment and operational separation of concerns. - -The Site Gateways normally implements routing functionality that separates the Layer 2 domains between the Cloud Sites Site Network Fabric and the external transport domains. - -When the Site Gateway is used to connect to the Fronthaul (between O-DU and O-RU), for Full Timing Support networks, the Site Gateway shall support PTP in order to act as T-BC. - -Site Gateways can be implemented as part of the Cloud Infrastructure, O-Cloud or provided by the transport organization. Regardless of where the Site Gateways are implemented, they could be deployed with management either from the Cloud Infrastructure, O-Cloud, or transport organizations. - -#### 3.4.3.5 Execution Environment Layer Concepts - -##### 3.4.3.5.0 Overview - -To make the hardware layer consumable as O-Cloud Nodes, O-Cloud Node Clusters, O-Cloud Site Networks and O-Cloud Gateways, there is a need for Operating Systems and configurations on Computer System, Switch Fabric Network and Site Gateway resources. To enable a distributed O-Cloud and to get traffic in and out of the cloud there is also a need for a configuration of the Gateway(s) that makes it an O-Cloud Gateway. - -Beside the Operating System on the Compute Nodes, they can also include cluster software and/or configurations that connects a set of O-Cloud Nodes into a O-Cloud Node Cluster and to a O-Cloud Gateway. - -![Diagram of Execution Environment Layer Concepts showing a Compute Cluster with OS Instances and Computer Systems, connected to an O-Cloud Site Network, Site Network Fabric, and O-Cloud Gateway via an O-Cloud Attachment Circuit.](2734e7f9be3e1dc046f14be2e6c9a085_img.jpg) - -The diagram illustrates the Execution Environment Layer Concepts. It is divided into two main horizontal sections. The top section, labeled 'Compute Cluster', contains two identical nodes. Each node consists of an 'OS Instance' (represented by a circular icon with a gear) and a 'Computer System' (represented by a server rack icon). These nodes are grouped together by a bracket on the right, labeled 'Compute Nodes exposed as O-Cloud Nodes'. The bottom section represents the network infrastructure, starting with an 'O-Cloud Attachment Circuit' (represented by a satellite icon) on the left. This is connected to an 'O-Cloud Site Network' (represented by a desktop computer icon), which is further connected to a 'Site Network Fabric' (represented by a switch icon). The 'Site Network Fabric' is connected to an 'O-Cloud Gateway' (represented by a cloud icon). The entire network section is enclosed in a yellow box, and the entire diagram is enclosed in a green border. - -Diagram of Execution Environment Layer Concepts showing a Compute Cluster with OS Instances and Computer Systems, connected to an O-Cloud Site Network, Site Network Fabric, and O-Cloud Gateway via an O-Cloud Attachment Circuit. - -Figure 3.4-5 Execution Environment Layer Concepts - -##### 3.4.3.5.1 Operating System (OS) - -An Operating System (OS) is a system software that manages and abstracts the Computer System hardware and software resources as well as provides common services for computer programs such as scheduling and network connectivity. In order to support time synchronization, the OS on a Computer System that performs the role of T-TSC or T-BC shall be configured to synchronize with hardware time stamping by PTP (as an example to relevant OS configuration items, refer to clauses 5.5.1.1.2.1 and 5.5.1.2.2.1 of O-RAN.WG6.CADs **Error! Reference source not found.**). - -##### 3.4.3.5.2 Operating System with Virtual Machines - -An Operating System with Virtual Machines is an OS that through software or hardware implementation includes the ability to offer multiple Virtual Machines, each acting as a well-separated Computer System. - -##### 3.4.3.5.3 Operating System with Containers - -An Operating System (OS) with Containers is an OS that include the ability to offer multiple separated name spaces, quotas, and management for Containers. - -##### 3.4.3.5.4 Compute Node - -A Compute Node is a Computer System with a running managed Operating System that is network connected. - -##### 3.4.3.5.5 O-Cloud Node - -An O-Cloud Node is an O2ims exposed Abstracted Resource based on the Cloud infrastructure internal Compute Node. (CAD definition: “An O-Cloud Node is a collection of CPUs, Mem, Storage, NICs, Accelerators, BIOSes, BMCs, etc., and can be thought of as a server.”). - -An O-Cloud Node that participates in the deployment of NF Deployments concerning vO-DU, acting as a master/slave clock, shall be provisioned on a Computer System and OS that has the required PTP support. - -##### 3.4.3.5.6 O-Cloud Site Network - -An O-Cloud Site Network is a logical network interconnect enabling Compute Nodes to communicate with each other within their cluster and through the O-Cloud Gateway(s) connected to networks outside of the O-Cloud Site including other O-Cloud Sites. The O-Cloud Site Networks can represent a partition of the physically available O-Cloud Site Network Fabrics available networks (sometimes referred to as underlay networks, although it is an ambiguous term since it can refer to any layer that supports another layer). The O-Cloud Site Networks can also be further encapsulated on the O-Cloud Site Networks physical partitions or even on other O-Cloud Site Networks (sometimes referred to as overlay networks, that is neither a distinct term since it can refer to any layer, but the very lowest physical layer). - -O-Cloud Site Networks can be provisioned into O-Cloud Node Cluster Site Networks or O-Cloud Node Group Site Networks (often referred to as overlay networks) where they can be used to interconnect the provisioned O-Cloud Nodes inside a O-Cloud Node Cluster on the local O-Cloud Site. The O-Cloud Node Cluster Site Networks can span all the O-Cloud Nodes on the O-Cloud Site while the O-Cloud Node Group Site Network can only span the O-Cloud Nodes within its own O-Cloud Node Group on the O-Cloud Site. - -O-Cloud Site Networks, which are used to provision O-Cloud Node Clusters Networks and O-Cloud Node Group Networks in the O-Cloud Site that support NF Deployments with strict time sync requirements, e.g., concerning O-DU wherein the O-DU acts as a master/slave clock, shall be provisioned to support T-TC or T-BC. - -##### 3.4.3.5.7 Compute Cluster - -A Compute Cluster is a selected set of Computer Systems that are physically interconnected through a Site Network Fabric which can be used to setup a O-Cloud Node Cluster (as defined below). - -##### 3.4.3.5.8 O-Cloud Node Cluster - -An O-Cloud Node Cluster is a set of O-Cloud Site Network interconnected Compute Nodes of a specific type. The following four types of O-Cloud Node Clusters are defined: - -1. **Bare Metal Container Cluster** – A Bare Metal Container Cluster is a set of network-connected computer systems with their individual operating system instances that supports containers in a cluster configuration. -2. **VM-based Container Cluster** – A VM-based Container Cluster is a set of network-connected Virtual Machines with their individual guest operating system instance that supports containers in a clustered configuration. -3. **VM Cluster** – A VM Cluster is a set of network-connected Computer Systems with their individual operating instance that supports virtual machines in a cluster configuration. -4. **OS Cluster** – A OS Cluster is a set of network-connected Computer Systems with their individual operating system instance that supports a cluster configuration. - -An O-Cloud Node Cluster that participates in the deployment of NF Deployments concerning O-DU, acting as a master/slave clock, shall be provisioned with O-Cloud Nodes whose Computer System and OS have the required PTP support (see clause 3.4.3.5.5). - -##### 3.4.3.5.9 O-Cloud Gateway - -An O-Cloud Gateway can also be used to encapsulate, bridge, or stitch the O-Cloud Site Networks in different O-Cloud Sites via transport networks e.g., for realizing Distributed O-Cloud Node Cluster Networks. - -In case an O-Cloud Gateway is used to connect to the Fronthaul, and the O-DU in the O-Cloud Site needs time synchronization to connect with O-RU, the O-Cloud Gateway shall support the configuration in order to act as T-BC. - -##### 3.4.3.5.10 O-Cloud Attachment Circuit - -An O-Cloud Attachment Circuit (OCAC) is a logical connection enabling connectivity of Site Networks deployed within the O-Cloud Site to outside of the O-Cloud Site. In the deployment scenario where an O-Cloud Site includes the gateway functionality, one or more OCACs can exist on the O-Cloud Gateway. - -##### 3.4.3.5.11 O-Cloud Bearer - -An O-Cloud Bearer is a physical or logical link that establishes connectivity between the O-Cloud Site and transport networks or other networks outside the O-Cloud Site. It's possible to carry one or more OCAC over the same O-Cloud Bearer. - -#### 3.4.3.6 Local and Distributed O-Cloud Node Clusters - -##### 3.4.3.6.0 Overview - -Node Clusters can be deployed local to one Cloud Site or distributed over multiple Cloud Sites, but they are always within one O-Cloud. - -![Diagram of O-Cloud architecture showing local and distributed node clusters across multiple cloud sites connected to a central IMS and external transport networks.](15e4a144a88176b71ea3eff2722253b0_img.jpg) - -The diagram illustrates the O-Cloud architecture across three Cloud Sites. At the top, a yellow box represents the IMS. Below it, each Cloud Site contains a blue box labeled DMS. The first Cloud Site on the left has two 'Node Cluster - Local' units. Each unit contains a 'Node Group' with 'Compute Node' boxes, which in turn contain 'OS instance' and 'Computer System' boxes. These are connected to a 'Node Cluster Site NW' box, which is part of a larger 'Site Network' box. The second Cloud Site in the middle has a 'Node Cluster - Distributed' unit. This unit contains 'Node Groups' with 'Compute Node' boxes containing 'OS instance' and 'VirtualMachine' boxes. These are connected to a 'Distributed Node Cluster Network - Bridged/stitched between Sites' box, which is part of a 'Site Network' box. The third Cloud Site on the right has another 'Node Cluster - Local' unit, similar to the first site. All three 'Site Network' boxes connect to a central 'Distributed O-Cloud Transport' box, which is further connected to an 'Operator WAN Transport' box at the bottom. Each Cloud Site also has an 'O-Cloud Gateway' box connecting its 'Site Network' to the 'Distributed O-Cloud Transport'. - -Diagram of O-Cloud architecture showing local and distributed node clusters across multiple cloud sites connected to a central IMS and external transport networks. - -Figure 3.4-6 O-Cloud example with Local and Distributed Node Clusters - -##### 3.4.3.6.1 Distributed O-Cloud Node Cluster Networks - -Distributed O-Cloud Node Clusters that span multiple O-Cloud Sites also span an O-Cloud Gateway routing function that can connect the O-Cloud Node Cluster Site Network traffic on the local O-Cloud Site to an external transport network. The O-Cloud Gateway routing functions in each O-Cloud Site where the distributed O-Cloud Node Cluster has O-Cloud Nodes, are configured to stitch, or bridge each O-Cloud Site's local O-Cloud Node Cluster Site Networks with each other. The O-Cloud Gateway router function can also be configured to stitch or bridge selective O-Cloud Node Group Site Networks in between O-Cloud Sites. - -The external transport network could be a dedicated Distributed O-Cloud Transport or a configured partition of the Operators WAN Transport network. - -For deployments of distributed O-Cloud Node Clusters that will depend on the local traffic characteristics of the local O-Cloud Site the O-Cloud Nodes on each O-Cloud Site ought to be provisioned into one or more O-Cloud Node Groups if the clusters have a scheduling mechanism e.g., K8s. O-Cloud Node Group Site Networks can be used where specific O-Cloud Site local traffic treatment or isolation is desirable. - -#### 3.4.3.7 Initiation Configuration Set Concept - -Several Cloud Infrastructure and O-Cloud Resources have to be initiated or initially configured before they can be used for anything. This initialization could be done at installation, power-on, boot-up, start-up or as a re-configuration when the resource is not in-service. - -Many of these initial configurations have dependencies of each other and might be destructive to its functionality, characteristics or even expected lifespan, e.g., an incorrect combination of configurations could permanently destroy resources. Examples of such configuration parameters are found in servers BIOS settings and networking devices port configurations or setup of physical layer parameters. - -Some initial parameters only take effect during start-up and others could later be changed during run-time. Examples of parameters generally used only at start-up are specific hardware mode configurations and links to firmware and software images supplied by the Cloud Infrastructure or O-Cloud. Examples of run-time changeable configurations are port speeds of IO modules. An important parameter for a Compute Resource to be useful is the OS image (possibly including Cluster SW and other functions) that will be booted for an O-Cloud user. The image enables the O-Cloud Resource to be used and exposed as a O-Cloud Node in a O-Cloud Node Cluster. Other important initiation configuration concerns the settings on the hardware (such as Computer Systems and Site NW Fabrics) and OS layers to support time synchronization. - -To allow the O-Cloud users a safe yet flexible way to setup these initial configuration parameters in a coherent way, the O-Cloud has a concept of an Initiation Configuration Set (ICS) artifact that should be a consistent, validated, static and safe set of configuration parameter available in the O-Cloud. The ICS artifact content can be applied to the O-Cloud Resources at each start-up occasion. ICS artifacts are likely rather specific for each ResourceType and should have an association that indicate what ResourceType or ResourceTypes it is validate for. - -The resulting started O-Cloud Node keeps a reference to the used ICS that can be used to understand the static initiation parameters that can only be set at start-up. Configuration parameters initialized by the ICS, that can be modified in run-time towards the O-Cloud Node, will not change in the ICS since that is a static artifact. These parameters in the ICS could consequently not be used as reference to what is currently running in the O-Cloud Node. - -When the ICS is applied to the Resource at initialization it will result in a new set of capabilities. The user of the O-Cloud Resources will have to keep within the capabilities (hard limitations) of the installed and available O-Cloud Resources but have the opportunity to apply different ICS to tailor these Resources at each start-up to take into account the new set of capabilities and capacities. - -Each ICS are linked to the ResourceType it can be applied to, but there can be multiple ICS that support the same ResourceType enabling the O-Cloud user a selection of soft limitations to be applied at start-up. If the O-Cloud supports, the use of ICS then O2ims need to expose available and referenced ICS. - -Where a ResourceType supports multiple separated or hierarchical restart or start-up domains the ResourceType could select to divide up its total set of start-up configuration parameters in separate ICS that can be individually applied for each such domain. This pattern enables a ResourceType to perform a partial reconfiguration of the resource during run-time, but it can also be used for other practical reasons. For fixed pre-configured Resources there might not even be an ICS available in the O-Cloud. - -#### 3.4.3.8 Managed Infrastructure Template Concept - -The Managed Infrastructure Template (MIT) concept enables repetitive creation and updates of managed O-Cloud Resources. Examples of such managed O-Cloud Resources are O-Cloud Node Clusters and Infrastructure Resources that are provisioned for the O-Cloud client (SMO) and managed by the O-Cloud. - -The MIT contains a parameter schema enabling an O-Cloud client to determine the mandatory and optional parameters to be supplied with a client's provisioning request for a set of managed O-Cloud Resources. The MIT can also contain a set of known target characteristics that enable the O-Cloud client to understand what capabilities and capacities the resulting set of managed O-Cloud Resources will have when they are provisioned. These characteristics are intended to support the O-Cloud client in their selection of what MIT to choose for a specific provisioning request. - -The O-Cloud has the MIT source-of-truth, and a set of O-Cloud internal MIT related content used to control the realization of managed O-Cloud Resources when provisioning requests are received. The MIT with a valid set of parameters serves as the declarative target configuration of a provisioning request. - -Templates are a common concept used for declarative target of clusters in various initiatives, e.g., in clause 6.2 of ETSI GS NFV-IFA 036 [19] for the case of container infrastructure clusters. - -SMO selects a MIT representing a desired set of characteristics of managed O-Cloud Resources, selects values for that MIT's defined parameters and sends a provisioning request to the O-Cloud. The known target characteristics and a parameter schema are part of the MIT. The O-Cloud exposes the MITs to the SMO as MIT Artifact Resource objects on O2ims hence enabling the SMO to discover them and query them about their attributes. The parameter schema in the MIT defines the parameters, their types, their allowed value ranges and whether they are mandatory or optional to supply with a provisioning request that references this MIT. - -When the SMO issues a provisioning request referencing a MIT in the O-Cloud and, where applicable, includes a valid set of parameter values, it triggers the O-Cloud to start convergence towards the MIT declarative target of the requested managed O-Cloud Resources. The O-Cloud applies its O-Cloud internal MIT realization control recipe on O-Cloud Inventory Resources and O-Cloud internal resources that enable the O-Cloud to converge to the declarative target configuration of the managed O-Cloud Resources. - -The O-Cloud internal MIT realization control recipe provides the O-Cloud with required information to build the managed O-Cloud Resources, including configuration, topology and structure of O-Cloud Inventory Resources and/or O-Cloud internal hardware and software resources. The MIT can also include the managed O-Cloud Resources known characteristics to be made available in their respective resulting target managed O-Cloud Resource objects. A standardized set of managed O-Cloud Resource capabilities used for the Node Cluster creation and updates are defined in Annex D. The resulting managed O-Cloud Resources will be built and reconciled in the O-Cloud, whereafter it is configured e.g. as an O-Cloud Node Cluster and/or a set of O-Cloud Infrastructure Resources reflecting the selected MIT with its known characteristics. When a provisioning request is fulfilled and the managed O-Cloud Resource has converged to its declarative target, they will have their own set of detailed characteristics exposed through their respective resource objects e.g. Node Cluster Resources and Infrastructure Resources. - -An O-Cloud Node Cluster instantiated based on a MIT will have specific capabilities and capacities that can make it more suitable or less suitable for orchestrating certain NF Deployments on that O-Cloud Node Cluster. Supported capabilities can be expressed by labelling. - -![Diagram showing the interaction between SMO and O-Cloud regarding Managed Infrastructure Templates (MITs).](f0a97d0d3818a253c1d2a009966081b1_img.jpg) - -The diagram illustrates the interaction between the SMO (Service Management and Orchestration) and the O-Cloud regarding Managed Infrastructure Templates (MITs). The SMO contains a 'SMO Managed Infrastructure Template list' with entries for 'SMO MIT Name & Version (SMO scoped)' and '....'. Below this is a box for 'SMO awareness of each O-Cloud Managed Infrastructure Template' containing a 'MIT' section with 'O-Cloud MIT Name & Version', 'MIT Parameters Schema', 'MIT known Target Characteristics\* list', and 'Capability : Capacity\*\*'. It also includes 'MIT Metadata (SMO complemented data)'. The O-Cloud contains an 'O-Cloud Artifact catalogue' with 'O-Cloud MIT (Name & Version) ArtifactResource' and '....'. Below this is a box for 'O-Cloud Managed Infrastructure Template related content' containing 'O-Cloud Managed Infrastructure Template' with 'MIT Name & Version', 'MIT Parameters Schema', 'MIT known Target Characteristics\* list', and 'Capability : Capacity\*\*'. It also includes 'O-Cloud internal MIT realization control recipe [not O2 exposed]' and 'O-Cloud internal resources [not O2 exposed]'. At the bottom are two boxes for 'O-Cloud Resources (Inventory)'. A yellow arrow labeled 'O2ims' points from the SMO to the O-Cloud. Another yellow arrow points from the O-Cloud to the SMO, labeled with 'Discover MITs' and 'Read MIT content'. Footnotes at the bottom explain: '\*') Target Characteristics not depending on parameters' and '\*\*') Capabilities and Capacities may be O-RAN well-known (standardized), O-Cloud Vendor defined, or NW Operator defined through MIT'. - -Diagram showing the interaction between SMO and O-Cloud regarding Managed Infrastructure Templates (MITs). - -**Figure 3.4-7 Managed Infrastructure Template related parts and references in SMO and O-Clouds** - -The intended usage of the MITs is that a provisioning request with a MIT reference together with its populated parameters represents a target configuration of a set of managed O-Cloud Resources. That target configuration has a set of known characteristics that are well suited for the deployment of the intended target workloads (e.g., NF Deployments) through the fulfilment of their required capabilities, such as NF Deployments realizing O-RAN Cloudified NF that need support for time synchronization. - -An example of using a MIT for Cluster provisioning and configuration settings to an O-Cloud Node Cluster are functions related to time synchronization. In such an example, the provisioning request, with referenced MIT and needed parameterization defines the requirements for O-Cloud Site NWs, and/or O-Cloud Gateways to support PTP transmission, and O-Cloud Node Cluster to include O-Cloud Nodes whose OS is set to handle hardware time stamping for PTP. - -For the creation of a MIT and its O-Cloud related content, the following aspects need to be considered: O-Cloud exposed and internal resources, their internal connectivity, software, and configuration parameters as well as the requirements of the workloads that might be deployed on the resulting set of managed O-Cloud Resources. The MIT is immutable and can only be created or deleted. It is referenced by a Name and a Version that together shall be unique within an O-Cloud. The MIT Name is intended to enable the Network Operator to keep track of what main purpose the MIT has, and the MIT Version is a way to allow the Network Operator to have several versions of the MIT with a specific Name. When a MIT and its related content is created for an O-Cloud and is ready for usage in the O-Cloud, it is exposed as an O-Cloud Artifact Resource. This MIT - -Artifact Resource provides the parameters schema that SMO needs to inject suitable parameters, and a representation of the resulting known managed O-Cloud Resources target characteristics, such as, but not limited to their capabilities and capacities. SMO can detect any new MIT over the O2ims through polling or subscribed change notifications of the MIT Artifact catalogue and can then read each MIT when it is required. The SMO can build up its own representation of each O-Cloud's MIT and complement these with relevant metadata such as where in the O-Cloud the MIT is supported. This information enables the SMO to understand the applicability of a MIT and where it can be used to deploy its targeted set of managed O-Cloud Resources. - -SMO keeps track of MITs to enable its orchestrators and other functions to understand what MITs are available in each O-Cloud, and what known characteristics could be realized by a provisioning request referencing a specific MIT and other relevant metadata about the MITs. This information is required to enable SMO to select a relevant MIT for the set of targeted managed O-Cloud Resources that can serve the intended workloads. - -When a SMO requests a new or updated set of managed O-Cloud Resources it references the desired MIT in the O2ims ProvisioningRequest along with a complete set of valid parameters for the selected MIT. The O-Cloud will then reconcile the set of managed O-Cloud Resources to the declarative target given by the referenced MIT and SMO supplied parameters. The managed O-Cloud Resources and its constituent O-Cloud Resources and topologies are reflected through their respective objects using the O2ims Inventory service that SMO can poll or get notifications about. - -NOTE 1: The method of how the MIT is inserted in the O-Cloud is not described in the present document. - -NOTE 2: The method of how the MIT is created and deleted is not described in the present document. - -NOTE 3: The method of how the MIT is created and tested is not described in the present document. - -NOTE 4: The SMO represented MIT characteristics such as Capabilities and Capacities are not described in the present document. - -## 3.5 O-Cloud Software Management - -Software Management should be a priority as without proper management unnecessary risks may be taken. Software Management ensures security, cost management and software support. There are many benefits to Software Management, of which the main benefits are: - -- Prevents unauthorized software from being installed -- Maintains a catalog of authorized software and its versions -- Provides visibility into what software and version is being used -- Provides a better view of which software products and versions are vendor supported - -In O-RAN, from an O-Cloud perspective, there are four types of software which needs to be managed on the O2 Interface: - -- The IMS software within an O-Cloud -- The DMS software within an O-Cloud -- The O-Cloud Platform software -- The O-RAN Cloudified NF software is the software implementation of O-RAN NFs which is capable of running over the O-Cloud - -### 3.5.1 General Capabilities - -Pre-requisite: - -- O-RAN Cloudified Network Function Software Package is onboarded to SMO with required information, the details are not documented in the present document -- From an O-Cloud perspective the O-RAN Cloudified Network Function Software Image includes the underlying software executable image, image properties/metadata such as version - -- IMS Software Version image(s) is available in or from SMO with required information, the details are not documented in the present document -- DMS Software Version image(s) is available in or from SMO with required information, the details are not documented in the present document -- Security/Certificates, the details are not documented in the present document - -Business Capabilities: - -- Network Operations shall be able to perform the Software Image Management of O-Cloud Platform, IMS, DMS and O-RAN Cloudified Network Function - -Functional Capabilities: - -- O-Cloud shall provide Add Software Images of O-Cloud Platform, IMS, DMS and O-RAN Cloudified Network Function to O-Cloud repository -- O-Cloud shall provide Delete Software Images of O-Cloud Platform, IMS, DMS and O-RAN Cloudified Network Function from O-Cloud repository -- O-Cloud shall provide Update Software Images of O-Cloud Platform, IMS, DMS and O-RAN Cloudified Network Function to O-Cloud repository -- O-Cloud shall provide Query Software Images of O-Cloud Platform, IMS, DMS and O-RAN Cloudified Network Function from O-Cloud repository -- O-Cloud shall provide Software Image properties information of O-Cloud Platform, IMS, DMS and O-RAN Cloudified Network Function. - - SoftwareImageId, Vendor, and Version -- IMS can obtain the requested IMS Software, perform needed pre-check(s), and perform the update -- IMS can obtain the requested DMS Software, perform needed pre-check(s), and perform the update - -## 3.6 O-Cloud Life Cycle Management - -O-Clouds are a set of hardware and software components that provide cloud computing capabilities to execute O-RAN Cloudified Network Functions. These O-Clouds can be deployed centrally or at edge based on the deployment scenario and this typically involves cost and complexity. The goal of O-Cloud Life Cycle Management is to reduce this cost and complexity by orchestrating the deployment and management of the O-Clouds. - -In O-RAN the O-Cloud Life Cycle Management will provide the following capabilities: - -- Deploy -- Registration -- Scale - -The objective of Deployment is to provide automated provisioning of the O-Cloud Infrastructure. - -The objective of Registration is to register an O-Cloud and make it available for deployments. The SMO provides information for the registration of O-Clouds, this includes security handshake required for the trusted connection, the O-Cloud IMS endpoint, and the O-Cloud ID which is used to correlate the SMO inventory record with the deployed cloud instance. - -After the registration of an O-Cloud with the SMO, the following information but not limited to can be discovered: - -- O-Cloud (IMS) provided Inventory services - - List of All Resource Pools in the O-Cloud - - Attributes of a specific O-Cloud - - List of all resources of an O-Cloud Pool - -- Attributes of each O-Cloud Resource - - List of all DMS -- O-Cloud (DMS) provided Inventory services - - List of Locations Supported - - For a given location the Capabilities supported, such as: - - Descriptor types - - Technology types - - Accelerator types - - For a given location the Capacity of the location - - For a given location the Availability of the location - -The Scaling is not present in the current document. - -## 3.7 O-Cloud Deployment Life Cycle Management - -### 3.7.1 Overview - -RAN networks are in an evolutionary journey towards NFV/SDN, Openness and Network Function disaggregation. This journey enables the CSP's quest for future network and operational efficiency, where they can rapidly deliver new services and update the existing services with less cost than today. The goal is to reduce the time to market for a new service launch. - -To achieve this end state of higher service agility and lower operational economics, the CSPs are unambiguous in their support for a new network operational framework. The life cycle management of RAN network functions is an important consideration for this new network operational approach. - -In O-RAN, the O-Cloud will provide Deployment Life Cycle Management of NF Deployments. The following capabilities will be provided: - -- Instantiate, which deploys NF Deployments on O-Cloud with necessary O-Cloud resources. -- Terminate, which terminates NF Deployments on O-Cloud with releasing associated O-Cloud resources. -- Scale, which scales functional behavior and resources of NF Deployments to support services. There is different variance in scaling: - - Horizontal Scaling provides dynamic functional scaling of NF Deployments' behaviour by Scale In/Out. This scaling can have different invoke actors such as O-Cloud and SMO. - - Vertical Scaling provides dynamic resource scaling of NF Deployments by Scale Up/Down. -- Heal, which provides the ability to recover/mitigate the NF Deployments' abnormal behaviour in the network. - -![Diagram of O2 Deployment LCM Services showing the interaction between Service Provider Functionality, SMO, and O-Cloud. The SMO contains FOCOM and NFO. The O-Cloud contains IMS and DMS. The O2 interface separates them. A callout box lists: Instantiate, Terminate, Scale, Heal. Another callout box points to the O2 interface with the text 'Separation of Concerns boundary'.](318886a86a1dcc59e1fc83db6f157c60_img.jpg) - -The diagram illustrates the O2 Deployment LCM Services architecture. At the top, the **Service Provider Functionality** is associated with the **SMO** (Service Management and Orchestration). The SMO contains two main components: **Federated O-Cloud Orchestration and Management (FOCOM)** and **Network Function Orchestration (NFO)**. Below the SMO is the **O-Cloud**, which contains **Infrastructure Management Services (IMS)** and **Deployment Management Services (DMS)**. The **O2** interface separates the SMO from the O-Cloud. A callout box on the left points to the O2 interface with the text "Separation of Concerns boundary". A callout box on the right lists the following capabilities: **Instantiate**, **Terminate**, **Scale**, and **Heal**. - -Diagram of O2 Deployment LCM Services showing the interaction between Service Provider Functionality, SMO, and O-Cloud. The SMO contains FOCOM and NFO. The O-Cloud contains IMS and DMS. The O2 interface separates them. A callout box lists: Instantiate, Terminate, Scale, Heal. Another callout box points to the O2 interface with the text 'Separation of Concerns boundary'. - -Figure 3.7-1 O2 Deployment LCM Services - -### 3.7.2 General Capabilities - -Business Capabilities: - -- The SMO provides the capability for Network Operations to initiate the lifecycle management functional capabilities - -Functional Capabilities: - -1. O-Cloud supports Instantiating an NF Deployment instance -2. O-Cloud supports Terminating an NF Deployment instance -3. O-Cloud supports Horizontal Scaling (in and out) of an NF Deployment instance -4. O-Cloud supports Healing of an NF Deployment instance -5. O-Cloud supports Querying information about an NF Deployment instance -6. O-Cloud supports Querying status of LCM operations -7. O-Cloud supports Upgrading of any or all components of an NF Deployment instance - -### 3.7.3 Deployment Management Services - -The O-Cloud provides services over the O2dms interface to allow an SMO to trigger the functional capabilities specified in Section 0. As allowed by the O-RAN Cloud Architecture and Deployment Scenarios [12] specification, O-Cloud implementations can incorporate a multitude of virtualization technologies (e.g., VMs, containers, bare metal) and technology stacks which have major differences from each other. To account for these differences, each O-Cloud might have its own specific O2dms service API profile(s). An O2 DMS specification for a specific profile describes the API provided by the profile and how to use them to achieve the capabilities listed in Section 0. An SMO is intended to be able know which profile it is using and orchestrate according to description provided in the O2dms service API profile(s). The profile specific APIs will be defined in each stage 3 O2dms specification. The SMO needs to understand which O-Cloud capabilities are available in the O-Cloud, and what capabilities are needed by NF Deployments, that realize, all or part of, a Cloudified NF, so it can match the infrastructure requirements for the NF Deployments with the capabilities available in the different O-Cloud Node Clusters (this is part of the NF Deployment homing process). The DMS needs to understand the capabilities available in the O-Cloud Node Cluster to know where to place the NF Deployment on the O-Cloud Node Cluster. A standard set of O-Cloud capabilities used for the deployment purposes of the NF Deployments are defined in Annex D. - -The O2dms specification will contain the following information: - -- a) O-Cloud profile scope and technology stack specifies what types of technologies (e.g., VMs, containers) the profile applies to and specifies particular software systems (e.g., K8S, Prometheus, etc.) and versions that are part of the stack. - -- b) O2dms functional capabilities description specifies how the APIs provided by the O-Cloud Profile are used (e.g., interaction flow) to implement the functional capabilities specified in Section 0. To achieve these capabilities, dependent on the specific profile the SMO can do one or more of the following: - - 1. Initiate the procedure via a single DMS API profile call. - - 2. Orchestrate using several DMS API profile calls. - - 3. Relegate responsibility to the O-Cloud by leveraging O-Cloud capabilities, SMO does nothing to manage these capabilities. -- c) O-Cloud profile API specification: specifies what APIs are provided by an O-Cloud conforming to the O-Cloud Profile. -- d) O-Cloud profile data model specifies the actual data elements used by the API. - -The O-Cloud Profiles form the basis for the protocol and data model O2dms interoperability – any O-Cloud implementation which supports a particular O-Cloud Profile is expected to interoperate with any SMO implementation that also supports the same O-Cloud Profile but not with an SMO that only supports a different O-Cloud Profile. - -## 3.8 O-Cloud Fault Management Concepts - -### 3.8.0 Overview - -This section details general concepts related to IMS & DMS fault management. Fault management is a basic part of OA&M functions. The concepts described here will motivate the development of the O-Cloud O2 IMS & DMS Fault services and information modeling. - -The O-Cloud may be a confederation of resource pools comprised of various compute, storage, and networking resources. These might be provided by different public cloud providers. The public cloud provider is defined as computing services offered by third-party providers over the public Internet, making them available to anyone who wants to use or purchase them. Thus, it is important to outline some basic principles that can apply and are relevant to disparate vendors and providers. - -The following basic concepts are considered for IMS & DMS fault management: - -### 3.8.1 Fault Information Model - -A fault information model is expected to be developed in the O2ims information model. As a general concept, an information model provides a common lexicon, terminology, and model to serve as a basis for coordination between a group of actors. It facilitates communications between groups and aligns their contributions. The fault information model is applicable for the resources & resource pools as defined in the infrastructure information model. - -### 3.8.2 Subscription - -It is expected that there will be a subscription mechanism between a client and an agent. The client would pass an endpoint where notifications should be sent to. It is expected that multiple clients can be supported. Procedures are expected to be defined in the O2 specifications for IMS and DMS. Subscriptions originate from the client (e.g., SMO). - -For example, the concept of a subscription allows a client, such as the SMO, to register for call-backs to the O-Cloud to receive Alarm Notifications. - -### 3.8.3 Notifications - -Alarm Notifications originate from the IMS within the O-Cloud. There is a relationship between the Subscription and the Notification. When a condition occurs on an O-Cloud Resource which causes the current alarm list to change, this triggers an evaluation of the Alarm Subscription criteria by IMS. If deemed relevant by the Subscription criteria, an event is issued towards clients that have subscribed to receive such a type of Alarm Notification. - -For example, a user could receive alerts on an Alarm dashboard GUI based on O-Cloud IMS Alarm Notifications. - -### 3.8.4 Parallel Reporting - -A fault occurrence on an O-Cloud Resource may be reported by IMS to consumer(s) as an Alarm Notification. DMS resource faults are associated with a workload. It is possible that multiple resources can associate with a workload, whereby one fault might trigger an Alarm Notification on IMS, DMS and O1. Due to the nature of the subscribe/notify mechanism for Alarm reporting, it is possible to: (1) have multiple publishers sending to a single consumer and (2) conversely a single publisher that can send to multiple consumers. The interfaces for subscription & notification of Alarm reporting are: O2ims, O2dms, O1. - -For example, it is conceivable that a vDU application might report a fault on O1, and a related physical server allocated to a workload of a vDU would raise a DMS fault which might also have an infrastructure Alarm raised on IMS. - -### 3.8.5 Simple Devices - -Collectively, in the O-Cloud it is conceivable that many devices are simple devices that do not have a full suite of OAM S/W. - -For example, suppose a network interface card (NIC) is a resource that is a simple device, and if that NIC encounters a fault it might not be able to register, store, or log faults. It is expected that O-Cloud infrastructure could manage these kinds of simple devices to be able to fulfill some of the other basic fault concepts described in this section. The O-Cloud infrastructure works with the IMS to report these faults. - -### 3.8.6 Source of Truth - -In an O-Cloud IMS context, it is expected that the “*source of truth*” will be the resources of the O-Cloud itself. When an Alarm has been reported to a client, such as the SMO, the fault data is replicated within the Alarm Notification to provide details and information of the associated fault. Thus, the fault information now exists in multiple places both in the IMS and the entity receiving the Alarm Notification. Which element then has the “true” information should the network or elements be disconnected or faulty? After connectivity returns, how would the SMO reconcile its view of the existing Alarms against the current Alarms on the O-Cloud? The answer is for IMS to query the *source of truth* (O-Cloud Resource) for the most current faults. - -For example, if a resource in the O-Cloud goes out of service, and IMS had previously sent an Alarm Notification, and then later the O-Cloud Resource returns to service, potentially the client (SMO) and the O-Cloud will have different Alarm information. But the O-Cloud Resource is the source of truth, and it is expected that client (IMS) would query the O-Cloud Resource for the current information and reconcile that with client data and if deemed necessary based on the subscription criteria, an event is issued towards clients that have subscribed to receive such a type of Alarm Notification. - -### 3.8.7 Alarm Dictionary - -An Alarm Dictionary is a reference which details the alarms that can be emitted from that O-Cloud for one or more O-Cloud Resource(s). The set of Alarm Dictionaries define the failure/fault conditions that would be reported by the IMS in the O-Cloud so that the SMO could act on those. The IMS delivers the set of Alarm Dictionaries to the SMO, for example during the process of 1) O-Cloud registration, 2) IMS Software update 3) O-Cloud Resource addition and 4) O-Cloud Resource software update. The desirable goal is commonality of the Alarm Dictionaries across O-Clouds even though they will differ to some degree by implementation. - -For example, the Alarm Dictionary could be used for a variety of purposes. It might help a user decode the meaning of an Alarm Notification. As another example, an Alarm Dictionary could allow for fault signatures or patterns to be identified which may constitute a condition which requires a coordinated response. - -### 3.8.8 Queries - -In the IMS case, the SMO (client) can issue an Alarm Query towards IMS (publisher) related to the O-Cloud. In the SMO to DMS case, the SMO (client) can issue a specific query related to xApp/NF deployments (e.g., workloads) from the DMS (publisher). In the IMS case, an Alarm Query is a message which is expecting a response message from the IMS which matches the selection criteria. In the DMS case, the Alarm Query is expecting a response from the DMS. - -For example, the client may request status of a specific type of Alarm, or new active alarms conditions. The O-Cloud would reply to the query by responding with data based on the parameters of the query (e.g., IDs or severity). - -### 3.8.9 Filtering - -It is expected that the client, such as the SMO, can query for specific kinds of Alarms or groups of Alarms through a filter. In addition, filtering can also be applied to Subscriptions to determine if Notifications should be set. - -For example, it might request from the O-Cloud all the major severity alarms from a particular O-Cloud. The O-Cloud would select records based on the query pattern and send the details according to the Notifications. This concept will guide the IMS information model development of procedures that can support filtering. - -### 3.8.10 Void - -Void. - -NOTE: The contents of this clause (Fault Logging) has moved to clause 3.8.19. - -### 3.8.11 Alarm Synchronization - -There are many potential situations where a client and source of truth might become disconnected or disrupted. In this case, the client will need to synchronize with the source of truth after it is able to reconnect. - -For example, network fault might prevent communication between the SMO (client) and IMS resources in the O-Cloud. By the time connectivity has been restored, many new alarm conditions might have arisen and logged. This would motivate the SMO to resynchronize to get the current alarms again. A variety of mechanisms might be used to trigger alarm resynchronization. It might also trigger an upload of the most recent fault logs. - -### 3.8.12 Alarm Correlation - -As described in Parallel Reporting, it might be possible that a fault condition might result in a variety of different conditions or be reported in any combination of IMS, DMS and O1 Alarm Notifications. It is not the job of the O-Cloud IMS fault management to correlate faults between the application/NF and O-Cloud Resources. Thus, it would be up to higher layers of fault management to correlate disparate Alarm events to identify common root causes. - -For example, the SMO may receive an Alarm Notification for a fault with a root cause of a network issue among the O-Cloud Resources which manifests itself in a deployment and application fault as well. Thus, the SMO might receive three notifications over O2ims, O2dms and O1. It might correlate these Alarms to a common root cause. - -![Diagram titled 'PARALLEL REPORTING & ALARM CORRELATION' showing layers: Management (SMO with FOCOM and NFO), Applications, DMS Workloads (Workloads), and IMS Resources (servers). Arrows show alarm reporting paths: O2ims from IMS Resources to FOCOM, O2dms from Workloads to NFO, and O1 from Applications to NFO.](e038bf4fcea08f51944b4a2dd6e197a5_img.jpg) - -*Correlation occurs at the management layer (SMO) because it has a view of alarms coming from parallel reporting through O1, O2dms and O2ims pathways.* - -Diagram titled 'PARALLEL REPORTING & ALARM CORRELATION' showing layers: Management (SMO with FOCOM and NFO), Applications, DMS Workloads (Workloads), and IMS Resources (servers). Arrows show alarm reporting paths: O2ims from IMS Resources to FOCOM, O2dms from Workloads to NFO, and O1 from Applications to NFO. - -Figure 3.8-1 Parallel Reporting & Alarm Correlation - -### 3.8.13 Escalation Strategy - -Fault conditions in an IMS resource may trigger an escalation strategy. An escalation strategy is a mechanism to increase visibility to a condition of duress which is typically a precursor to a more severe situation. - -For example, recurring alarms, fault signatures and severity levels may have an escalation strategy to raise higher severity alarms for higher tier recovery actions. As another example, a minor alarm in an O-Cloud resource with a certain occurrence rate within a time window might trigger an escalation strategy to raise a major alarm. - -### 3.8.14 Fault Domains - -A fault domain is a “*unit of failure*”. A fault domain associates a collection of IMS O-Cloud resources together. We expect a fault domain to be within a Data Center Zone (see the provisioning chapter basic concepts for more detail). Faults could be associated with a fault domain. In the context of IMS fault area, fault domains are an attribute that could be correlative but do not have intrinsic fault operations, they are not a manageable entity. - -This would allow operators to design systems that are fault tolerant across fault domains. This might also guide placement strategies, and update cycles to improve reliability and availability. - -For example, a network cloud can host some number of servers per rack (e.g., 40 servers) with a number of racks of equipment (e.g., 10 racks) in a single deployment (totaling 400 servers). A fault domain might be defined to be rack. If a fault occurred, this concept would allow an operator trying to isolate the problem down to a rack (the fault domain). It would also allow a user to correlate a problem if multiple racks served by a common infrastructure resource. - -![Diagram illustrating the concept of Fault Domains. It shows three server racks, each enclosed in a red box labeled 'Fault Domain'. The top two racks have dashed green boxes around individual server units, labeled 'Individual IMS Resource'. A green arrow labeled 'IMS Resources' points to the entire group of three racks. The top of the diagram has a black header bar with the text 'FAULT DOMAIN' and a subtitle 'A Fault Domain is a "unit of failure"'.](9ff1b32449ea068bba9647d71904bd59_img.jpg) - -Diagram illustrating the concept of Fault Domains. It shows three server racks, each enclosed in a red box labeled 'Fault Domain'. The top two racks have dashed green boxes around individual server units, labeled 'Individual IMS Resource'. A green arrow labeled 'IMS Resources' points to the entire group of three racks. The top of the diagram has a black header bar with the text 'FAULT DOMAIN' and a subtitle 'A Fault Domain is a "unit of failure"'. - -Figure 3.8-2 Concept of Fault Domains - -### 3.8.15 Fault Tolerance - -A fault tolerant system is one that is designed to withstand failures and continue to be able to provide service. Based on observations, some *actions* can be taken to insure reliability. Fault tolerant solutions & strategies will vary between O-Cloud providers and network function providers. - -An example of a fault tolerant strategy is the use of geo-redundancy and Data Center Zones. Geographically separating Data Center Zones allows service to continue should a physical natural disaster strike one data center. An *action* might be to migrate traffic from one zone to another. - -### 3.8.16 Metrics - -Metrics allow users to define thresholds to monitor and manage IMS O-Cloud resources. From these metrics, a user/system could take action based on threshold crossings and/or chart the metrics over time. Also, to achieve fault tolerance, there could be a mechanism for alerting, monitoring & auditing as a health check. - -For example, in the basic fault concept of *Escalation Strategies*, we might need metrics of how **often** a fault occurs within a certain period of time. These *metrics* might be used as a threshold in an escalation strategy for better reliability. If the fault occurred 100 times in an hour action might be taken. - -### 3.8.17 Alarm Suppression - -Alarm floods are defined as a multitude of alarm notifications within a short period of time. Alarm floods could be caused by disasters or maintenance work. Thus, it is desirable to be able to suppress alarms in order to avoid alarm floods which distract and overload operators and their monitoring of management systems. The suppression of alarms would cause certain alarms not to be raised when a certain failure(s) happens. The functionality can be managed via the O2ims and/or at the SMO. Furthermore, an operator might be interested in suppressing only certain alarms or types of alarms; hence, an operator could configure the filter for the suppression of alarms via the O2ims. - -It is expected that the fault originating from the source of truth, the O-Cloud Resource is still raised to the IMS. It is expected that the O-Cloud Resource faults would still be logged even if they are suppressed. The IMS would also perform the transformation of the fault into an alarm (as normal), and record that an alarm occurred. However, the IMS would suppress the alarm notification over O2ims interface towards the SMO. - -There are two motivations for alarm suppression: - -1. Reactive suppression – reacting to a situation/disaster which caused/causing an alarm flood. -2. Proactive suppression – a priori, the operator is aware of activity which will cause an alarm flood. - -There are two types of suppression: - -1. Suppression Type #1 – A mass suppression of alarms, where the suppression filter is requesting for many alarms to be suppressed. This will eventually cause mismatches between IMS and the alarm history at the SMO which would be reconciled later. -2. Suppression Type #2 – The suppression of repeated alarms would suppress an alarm that is being raised many times. - -SMO dashboard can filter alarms, which can help a user comprehend and digest a large quantity of alarm information. - -- SMO – The SMO Dashboard can choose to filter the display of alarms to make the management of a system more tenable for an operator. Filtering SMO would offer capabilities of filter, the type of alarms that are of interest to an operator. - -Alarm suppression occurs in two areas: - -1. IMS – The IMS is responsible for transforming faults received from O-Cloud resource into alarms. It would suppress alarms based on its alarm suppression filter. -2. Source of Truth – The O-Cloud resource could suppress faults. This would be implementation specific. - -NOTE 1: It is expected that all faults originated from O-Cloud resources would be sent to the IMS. - -NOTE 2: It is expected that if the O-Cloud resource suppresses its faults that it would notify the IMS, though this is implementation specific. - -Aspects of alarm suppression at the IMS: - -1. IMS – Suppresses alarms based on a suppression filter. Suppressed alarms are not raised that would have normally been raised as alarm notifications towards the SMO (client) over the O2ims interface. Consequently, the state of the active alarms in the SMO (client) may be mismatched with the state of alarms in the IMS (O-Cloud) because of alarm suppression. -2. IMS – Respond with its Alarm List information based on the Alarm List query criteria (e.g., a time window which encompasses the suppression period) for purposes of synchronization & reconciliation by a client. The requested - -Alarm List can be used by a client to align with its view of alarms after the situation has passed. See the Alarm List Management Use Case for more details. - -3. IMS – The IMS would keep an alarm suppression filter(s). The suppression filter is configured by the SMO through the O2ims interface. The IMS may also configure an alarm suppression filter autonomously and inform the SMO through the O2ims interface. The IMS could respond with the current filter that it has, even if it currently has no filter. See the Alarm Suppression Use Case for more details. -4. IMS – IMS would still continue to perform fault-to-alarm transformation and record an alarm occurred irrespective of any alarm suppression filter. This is important that the O-Cloud continue to operate normally so that later when the condition passes the active alarm list can be reconciled by a client. -5. IMS – The cessation of alarm suppression could occur from one of three mechanisms. Alarm suppression can end through specification in the alarm suppression filter request, through a time-out mechanism, and/or by a configurable policy (which would be implementation specific). See the Alarm Suppression Use Case for more details. - -![Figure 3.8-3 Alarm Suppression Function diagram showing the interaction between SMO, IMS, RAN O-RU, and O-Cloud Resource. The diagram is titled 'ALARM SUPPRESSION FUNCTION'. It shows three main components: SMO (top), IMS (middle), and RAN O-RU/O-Cloud Resource (bottom right). Arrows indicate data flow: SMO to IMS (Configures Suppression Filter for IMS), IMS to SMO (Warnings, Minor Alarms, Major Alarms, Critical Alarms), and RAN O-RU/O-Cloud Resource to IMS (Fault). Numbered callouts explain: 1. SMO filters view of alarms on dashboard display; 2. IMS suppresses alarms based on a suppression filter, responds with active alarm list, keeps filter configuration, and continues fault-to-alarm transformation; 3. Source of Truth – O-Cloud Resource or PNF can perform suppression (Implementation specific).](b58cedaf15ad4f0edee5621820865ccc_img.jpg) - -Figure 3.8-3 Alarm Suppression Function diagram showing the interaction between SMO, IMS, RAN O-RU, and O-Cloud Resource. The diagram is titled 'ALARM SUPPRESSION FUNCTION'. It shows three main components: SMO (top), IMS (middle), and RAN O-RU/O-Cloud Resource (bottom right). Arrows indicate data flow: SMO to IMS (Configures Suppression Filter for IMS), IMS to SMO (Warnings, Minor Alarms, Major Alarms, Critical Alarms), and RAN O-RU/O-Cloud Resource to IMS (Fault). Numbered callouts explain: 1. SMO filters view of alarms on dashboard display; 2. IMS suppresses alarms based on a suppression filter, responds with active alarm list, keeps filter configuration, and continues fault-to-alarm transformation; 3. Source of Truth – O-Cloud Resource or PNF can perform suppression (Implementation specific). - -Figure 3.8-3 Alarm Suppression Function - -An example of Alarm suppression is as follows. Suppose O-Cloud Resource Compute Node #1 raises a fault #150 towards the IMS. The IMS would change the fault #150 to a corresponding alarm. If a suppression filter were active, causing that alarm to be suppressed, the IMS would not send the alarm notification (see the alarm notification Use Case). Alarm is still in IMS alarm list (not acked). Expected to have a sync, and SMO reconcile alarm. - -Some examples of Use Cases for Alarm Suppression are: - -- Use Case #1: Something in Maintenance the alarms should be suppressed -- Use Case #2: Disaster turn off all (major, minor, warning) alarms - -### 3.8.18 Fault Supervision - -Fault Supervision is a Fault Management (FM) concept regarding the process or operations involved in the fault management of O-Cloud resources. - -Examples of Fault Supervision are the operations of Alarm Acknowledge and Alarm Clear. See the corresponding use cases in the Orchestration and Cloudification Use Cases and Requirements for O-RAN Virtualized RAN [13]. - -### 3.8.19 Logs for Fault Management - -There are three basic kinds of logs that might be kept within the Cloud (both exposed O-Cloud and Cloud infrastructure): - -- ALARM LOGS – Alarm logs are a record of the alarms that have been raised by the IMS. The IMS keeps and produces an Alarm Log. It is expected that the IMS logs every alarm (including suppressed alarms) that it sends to the FOCOM (SMO). Alarm Logs are exposed in an O-Cloud to northbound entities. - -NOTE 1: It is also possible to log additional events or actions against alarms, such as clearing and acknowledgment of alarms. See the Log Query and Logging Management Use Cases for further details [13]. - -- FAULT LOGS – All detected Faults are raised by an O-Cloud Resource. Faults information is stored by the O-Cloud Resource, either remotely or locally, in a Fault Log. Not every fault necessarily raises an alarm, hence the necessity to log events for both fault information and alarms. The present document does not specify or describe the creation and operation of fault logs. Disclaimer: it is possible to combine Fault and Debug logs together. Fault logs, once activated, would be exposed to northbound entities. Fault Logging may be part of the general event logging and is a concept where fault information is stored by the O-Cloud Resource (the source of truth), either remotely or locally, for a configured amount of time. The concept of Fault Logging and storing fault information allows a client, algorithm, or user to query the fault log and analyze those faults. Faults that are intermittent, repetitive, or transient can be identified this way. For example, Debug traces used by some O-Cloud providers might be a way to facilitate fault logging meaning that certain condition can trigger writing to the fault log. -- DEBUG LOGS – The present document does not specify or describe the creation and operation of Debug Logs. They might be able to be turned off. The log level would typically be configurable (at the source, middle, and end user level). For example, a typical implementation may use syslog (defined in RFC 5424, see reference [17]) which defines a “log level” to select informational (most detail), trace, warnings, errors, to critical (least detail) messages. Disclaimer: It might be possible that Fault logs and Debug logs might be combined. Debug logs, once activated, would be exposed to northbound entities. - -A Timestamp is a particular point in time when an entry in a log is created, and timestamps are typically used for correlated analysis across logs and in maintenance activities. Therefore, all log files typically follow a timestamp format which would enable for correlation across log files. - -Logging Management uses mechanism(s) such as Retention Period to manage the length of time that entries in a log are maintained. For example, logs for an O-Cloud Resource could be stored for 1 week. - -There may be other logs besides Alarm, Fault and Debug logs that might be kept in the O-Cloud. The present document does not specify or describe what other types of logs beyond Alarm, Fault and Debug logs are to be handled by the O-Cloud. - -The following diagram illustrates the basic concept for Fault and Alarm Logging: - -![Fault and Alarm Logging diagram showing O-Cloud Resource #1 sending fault events to the IMS, which then transforms them into alarms and logs them.](95e259e8cb3519025066052af263f8c0_img.jpg) - -The diagram illustrates the Fault and Alarm Logging process. It features three main components: O-Cloud, Infrastructure Management Service (IMS), and Consumer (FOCOM). - -1. **O-Cloud**: Contains 'O-Cloud Resource #1'. This resource encounters 'Fault A' and 'Fault B'. - -2. **Infrastructure Management Service (IMS)**: - -- 'Fault A' and 'Fault B' are sent as 'Fault event sent to IMS' to the IMS. - -- Simultaneously, 'Fault Log' entries for both faults are sent to 'Storage (Local or Remote)'. - -- Inside the IMS, an 'Alarm Manager' performs 'Fault to Alarm Transformation'. - -- The result is an 'Alarm Log' which is also sent to 'Storage (Local or Remote)'. - -3. **Consumer (FOCOM)**: The IMS sends an 'Alarm notification' over the 'O2ims' interface to the Consumer. - -Fault and Alarm Logging diagram showing O-Cloud Resource #1 sending fault events to the IMS, which then transforms them into alarms and logs them. - -Figure 3.8-4 Fault and Alarm Logging - -In the above diagram, O-Cloud Resource #1 encounters two faults, Fault A and Fault B. It sends those as Fault events to the IMS when they occur. O-Cloud Resource #1 might also store the occurrence of Fault A and Fault B into a Fault Log in local or remote storage. The IMS would assess and transform Fault A and Fault B into the appropriate Alarm(s). Suppose in this case, the IMS determines that Fault A would not need to be raised as an Alarm; however, the IMS determines that Fault B needs to be transformed into Alarm#10. The IMS would store the Alarm#10 into its alarm log to be stored either locally or remotely. The IMS would raise the Alarm#10 as an alarm notification over the O2ims interface. - -NOTE 2: The Alarm Manager shown in the diagram above is software which transforms Faults to Alarms that need to be exposed. The alarm manager depicted in figure 1 is only for illustrative purposes to show the process of logging alarm done by the IMS. - -### 3.8.20 Logging Level - -The Logging Levels adjust the amount of detail recorded in Fault and Debug Logs captured from O-Cloud resources. The Logging Level is associated with the severity levels and thus what is captured in logs. - -The motivation for the Logging Level concept is to change how much information should be captured and sent from O-Cloud resources. For example, while debugging, a developer might raise the Logging Level to see more faults. - -NOTE: Logging Levels may apply differently to Fault Logs vs Debug Logs. - -The notion of Logging Level is applicable to the source generating logs and from the perspective of the viewer. At the generation side, the Logging Level is adjusted to change the amount of data captured and sent; at the viewing side, the Logging Level indicates the level of detail recorded by logs. The higher the Logging Level, the more data that is captured and potentially sent on the generation side. - -Some relevant specifications include IETF RFC 5424 [17], The Syslog Protocol. ETSI GS NFV-SOL 009 v4.3.1 clause 8 which is the API on Log Management [18]. These describe how a consumer can set up a Log job. Log jobs collect logging information based on criteria with the possibility to indicate Logging Level. The SOL 009 specification: (1) describes the management of NFV-MANO, (2) It has a Log management API, and (3) the Log management API refers to IETF RFC 5424. - -### 3.8.21 Alarm List - -The Alarm List in the O-Cloud contains the history of Alarm Events that have been detected by the IMS. Each IMS manages one and only one Alarm List. The entries in the Alarm List are Alarm Event Records against resources and their respective resource type. - -The Alarm List contains both the active and inactive (a.k.a. cleared) alarms. - -The Alarm List concept is used in the Alarm List Management and Alarm Purge Use Case in the O-RAN.WG6.Orch-Use-Cases [13], Clauses 3.7.11 and 3.7.13 respectively. - -Alarm Life Cycle Management is described in IETF RFC 8632 [20]. 3GPP TS32.111 [21] introduces concepts related to Alarm List. - -NOTE: The present document considers that both acknowledged and cleared alarms are in the Alarm List. This differs from 3GPP TS32.111 [20] where clearing and acknowledging alarms causes them to be removed from the Alarm List. - -### 3.8.22 Retention Period - -Alarm Event records in the Alarm List conform to an Alarm Management Policy which specifies how long Alarms should be kept in the Alarm List. - -When Alarm Event records in the Alarm List exceed the time period for retention, those records are purged or archived based on Alarm Management Policy. - -The Retention Period is not set per resource type. Instead, the Retention Period is applicable to all entries in the Alarm List. Therefore, an Alarm List has one and only one Retention Period attribute. - -The Retention Period applies to alarms that are both inactive and acknowledged. - -### 3.8.23 Alarm Purge - -The concept of Alarm Purge is defined by the operation of removing Alarm Event Records from the Alarm List permanently. The Alarm Event records to be purged are determined by the Retention Period. See the concept from Clause 3.8.22. Alarms in the Alarm List that reach the age of the Retention Period will be purged. When an alarm in the Alarm List is older than the Retention Period, the IMS automatically purges those old Alarm Event records if they are also inactive and acknowledged alarms. Alarms can also be manually purged through an Alarm Purge request from an O-Cloud operator. In this case, alarms to be purged are removed from the Alarm List irrespective of the Retention Period. - -For further information, see IETF RFC 8632 [20]. - -NOTE 1: Only inactive alarms and acknowledged alarms can be purged. - -NOTE 2: A forced Purge of alarms might be used if the storage capacity for the Alarm List approaches or is at capacity; and an operator wants to remove (e.g., warning, and minor) alarms from the Alarm List to free up space. - -NOTE 3: If an alarm condition persists after the original alarm is purged, it will reappear as a new alarm (spurred from that same condition) back in the Alarm List. - -### 3.8.24 Archiving Alarms - -The concept of Archiving Alarms is defined by the operation of moving Alarm Event Records to a long-term storage or collection area. - -NOTE: The Archiving of Alarms may mean moving them off the O-Cloud to a separate off-site storage location. Archiving alarms is likely to be handled by tiered storage paradigms which will handle the archival of alarms. This would be implementation specific. - -## 3.9 O-Cloud Performance Basic Concepts - -### 3.9.0 Overview - -The following section describes basic concepts for O2 Performance Concepts. - -In general, the purpose of performance is to report operational information related to O-cloud resources. Typically, performance information allows an operator or administrator of the O-cloud a sense of how well the system is operating. It is distinct from faults in that it is not about failures in the system but about how well the overall system is performing. Though, faults or alarms may negatively impact performance of the O-Cloud which might be observable in performance measurements. - -Performance measurements are typically captured periodically through time. They are collected and stored at regular intervals by the system in order to gauge the performance of a system over a period of time. This allows for analytical operations to be performed on the collected data and statistics to be built over time. This can tell an operator or system analyst whether they have sufficient capacity in a network based on the demands of the network. This can be vital for making business operational decisions such as scaling a network. - -The following are basic performance related concepts that will be used in the O2 Cloud performance use cases and modeling. - -![Figure 3.9-1 Performance Measurement Reporting diagram showing the flow of data from O-Cloud resources through PM Job(s) and the Infrastructure Management Service (IMS) to the Service Management Orchestrator (SMO).](bc9d0c0b02cbe628b1b6548cc1107734_img.jpg) - -The diagram illustrates the performance measurement reporting flow. At the top, the **Service Management Orchestrator (SMO)** is shown in a green box. It receives a **Measurement Report** (represented by a document icon) from a **Subscriber/Notification Endpoint** (represented by a red square icon). The SMO then processes this report using **Metrics used in Analysis** (represented by a gauge icon). Below the SMO, a central vertical double-headed arrow represents the **Measurement Info Transfer**. This transfer is facilitated by a **Publisher endpoint** (red square) and a **Perf. Measurement Subscription** (yellow box). The bottom section, labeled **O-Cloud** and **Infrastructure Management Service (IMS)** in a blue box, contains **O-Cloud Resource** icons (server and cloud). These resources send **Measurement / Telemetry data** (gauge icon) to **PM Job(s)** (green bar with gauge icons). The PM Job(s) then send a **Measurement Report** (document icon) to the **Performance Subscription Manager** (yellow box with gauge icon) within the IMS. The PSM then sends the report to the SMO via the Measurement Info Transfer path. - -Figure 3.9-1 Performance Measurement Reporting diagram showing the flow of data from O-Cloud resources through PM Job(s) and the Infrastructure Management Service (IMS) to the Service Management Orchestrator (SMO). - -Figure 3.9-1 Performance Measurement Reporting - -Figure 3.9-1 shows the basic flow of Performance Data framework. Measurement and Telemetry data is collected from O-Cloud resources by PM Job(s) and stored locally. The Performance Subscription Manager (PSM) within the IMS can retrieve the data to be sent to the SMO. There is a consumer (subscriber) notification end point that is used to send the performance data to. The notification end point is known to the PSM from the subscription. Measurement reports are composed by the PSM and sent to the SMO. The SMO can then be used to perform analysis on the Measurement Report. - -Performance measurements in an O-Cloud might streamed (pushed) or it might be pulled (measurement reporting files) by a user or a PM job in the SMO (consumer). For performance measurements to be streamed, a subscription needs to be created. - -The subscription and criteria indicate an end point for where the measurements are sent to. The notification end point can be updated by performance subscription update. - -The subscription will indicate the interval. A capabilities exchange could occur between the SMO and the O-Cloud indicating the mechanism & formats supported by the O-Cloud. The SMO can then subscribe to the mechanisms & formats within the subscription filter. In the capabilities exchange, the IMS would report the jobs and their collection intervals. A performance subscription can be created, queried, updated, and deleted over O2ims. - -### 3.9.1 O-Cloud Performance Measurements - -Measurements are defined as the act of quantitatively checking the O-Cloud resources for defined gauges of operation. A measurement is an individual quantitative gauge of a quality. - -For example, the O-Cloud might measure the computational performance of an O-Cloud compute resource in terms of CPU utilization. - -### 3.9.2 Performance Indicators - -Performance indicators take execution measurements and use them in a way that can give a meaningful notion of how a system is utilizing its resources and/or how well a system is operating. Indicators might be local in the sense of a function or more broader in scope for a group of functions. Performance indicators are typically a formula-driven application usage of performance measurements. Thus, the indicators are amenable to statistical analysis. The indicator formula needs to be exposed so that users can understand the meaning of the indicator. Indicators use a measurement, or gauge, to show an aspect of a thing. Key Performance Indicators (KPI) are performance indicators that are typically used to detect and report overall network health. - -For example, the CPU utilization might be a performance measurement. A performance indicator might be the fraction of time that a system is over a threshold, such as 80% CPU utilization. This would be a simple ratio calculation that could give a sense of how close to being overloaded a system is. - -### 3.9.3 Performance Metric - -A performance metric represents standards of measurements. Metrics might be pre-defined, or they might define performance threshold targets to try to achieve. Metrics may utilize measurements and indicators. Performance metrics could be used by O-Cloud operators to achieve OPEX business objectives. - -For example, a performance metric could be a target that an operator would like to have a system operate at. For example, a metric to operate at five-9's reliability, or CPU utilization that is under a threshold. - -### 3.9.4 Performance Reports - -Performance reports are a collection of measurements. Usually, they are gathered in a file; however, they may also be sent as a data stream. Typically, reports are created at regular (configurable) intervals or triggered by thresholds. The creation of performance reports may also be manually invoked. - -For example, The O-Cloud might compose a performance report which is comprised of several performance measurements recorded and stored at regular intervals. - -### 3.9.5 Performance Management (PM) Job - -#### 3.9.5.1 Basic PM Job Concepts - -A performance management job is a task whose purpose is to collect measurements, creating a measurement file, and get a performance report according to criteria set by the user. The criteria could be used to specify measurements to collect. - -NOTE: 3GPP standards also discuss measurement jobs see references, 3GPP TS28.550 [14], 3GPP TS28.531 [15], ETSI SOL003 [16]. - -For example, a PM job might be scheduled to run at 11 PM with the criteria to retrieve CPU measurements for O-Cloud resources and compose them into a measurement report. - -PM job can be created, queried, updated, suspended, resumed, and deleted over O2ims. - -#### 3.9.5.2 PM Job States and Statuses - -A PM Job can have one of the following states. Each State is mutually exclusive from the others. - -- ACTIVE – An Active PM Job is one that is operational and currently collecting one or more measurements. -- SUSPENDED – A Suspended PM Job is one that a consumer has issued an operation to stop the collection of all measurements. A Suspended PM Job when resumed goes back to the Active state. A delete operation can only be processed for a Suspended PM Job. -- DEPRECATED – A Deprecated PM Job is one that has had a delete operation issued for it; and is now pending delete. It is waiting on a pending purge of all the measurements collected by the PM Job from the PM Store whereupon the PM Job will be deleted. The system purges measurement(s) that are older than a configurable retention period. Measurements previously collected by the deleted PM Job could still be requested which would cause referential integrity issues if that PM Job were to be deleted which is why the *Deprecated* state and *Pending Delete* status exist. - -A PM Job can have one of the following statuses. Each Status is mutually exclusive from the others. - -- RUNNING – A Running status applies to an Active PM Job that is currently performing metric collection without issue. -- FAILED – A Failed status applies to an Active PM Job that is failed and is no longer collecting any measurements. -- DEGRADED – A Degraded status applies to an Active PM Job that is experiencing one or more issues but has not fully failed. A Degraded PM Job could still be collecting all or some subset of its measurements. -- IDLE – An Idle status applies to a Suspended PM Job; and is therefore, no longer collecting any measurements. -- PENDING DELETE – A Pending Delete status applies to a Deprecated PM Job which remains in the Deprecated state until all measurements associated with it have been purged. Once all its measurements have been purged, the PM Job is removed from the system. - -#### 3.9.5.3 Preinstalled PM Job - -A Preinstalled PM Job is a type of PM Job that is created automatically by the O-Cloud. Preinstalled PM Jobs can be created during O-Cloud genesis (O-Cloud start up). Preinstalled PM Jobs behave like other PM Jobs. One of the purposes of the measurements collected by Preinstalled PM Jobs is for internal O-Cloud PM operation and management. - -An IMS consumer cannot change or alter a Preinstalled PM Job. Preinstalled PM Jobs may be deleted by an IMS software update. The SMO or other entity can subscribe to Preinstalled PM Jobs and their attendant measurements. - -### 3.9.6 Source of Truth - -The source of truth is the arbiter of discrepancies in metrics. In an O-Cloud IMS Performance context, it is expected that the “*source of truth*” will be the O-Cloud (IMS + O-Cloud infrastructure resources). The PM job manages the transformation of data into a performance report. The PM job requests data from the O-Cloud (the Source of Truth) to build the performance report. - -For example, suppose there is a metric from the source of truth with a reported value of 50, and the performance report has a value of 20. That value of 20 might have been a result of corruption in sending, composition, or a software bug. In order to obtain the proper value, the source of truth can be consulted. - -### 3.9.7 Performance Threshold - -A performance threshold is a level or value which is used to check if a measurement exceeds or stays within. Typically, thresholds are used to trigger behavior or policies in a system. - -For example, a user might set a CPU utilization threshold of 80%. - -### 3.9.8 Performance Dictionary - -A Performance Dictionary is a reference which details information on performance metrics or KPIs that are relevant to one or more O-Cloud Resource(s) and that would be reported by the IMS in the O-Cloud so that the SMO could act on those measurements. The Performance Dictionary would be onboarded when a new O-Cloud Resource Type is added, for example during the process of 1) O-Cloud registration, 2) IMS Software update 3) O-Cloud Resource addition and 4) O-Cloud Resource software update; and that O-Cloud Resource Type would come with an associated a Performance Dictionary. The Performance Dictionary for an O-Cloud Resource includes all measurements supported by the O-Cloud Resource Type including ones defined by standards and the reference to the standard. - -For example, there will likely be some standardized measurements. For a CPU, that might be CPU utilization measured in percentage. However, there could also be a vendor's CPU that might have additional features such as pinning or huge page functionality. - -### 3.9.9 Performance Measurement Operation Example - -![Figure 3.9-2 Performance Measurement Operation Example diagram. The diagram shows three O-Cloud Resources (#1, #2, #3) connected to an Infrastructure Management Service (IMS). Resource #1 provides Measurements A and B; Resource #2 provides Measurement C; Resource #3 provides Measurement D. These measurements are collected by PM Jobs (Job #1 for A, Job #2 for B, Job #3 for C, Job #4 for D) with intervals of 15, 30, 45, and 15 minutes respectively. The IMS contains a Performance Subscription Manager with two subscriptions (Subscription #1 for 30 min, Subscription #2 for 60 min). A Consumer (FOCOM) interacts with the IMS via O2ims interfaces for creating subscriptions and receiving measurement reports. Blue arrows show data flow from PM jobs to a local repository and then to the PSM. Red arrows show data flow from the PSM to the Consumer. Purple arrows show subscription and report activities over the O2ims interface.](c1278da91cbcabe32628e589ebc47418_img.jpg) - -Figure 3.9-2 Performance Measurement Operation Example diagram. The diagram shows three O-Cloud Resources (#1, #2, #3) connected to an Infrastructure Management Service (IMS). Resource #1 provides Measurements A and B; Resource #2 provides Measurement C; Resource #3 provides Measurement D. These measurements are collected by PM Jobs (Job #1 for A, Job #2 for B, Job #3 for C, Job #4 for D) with intervals of 15, 30, 45, and 15 minutes respectively. The IMS contains a Performance Subscription Manager with two subscriptions (Subscription #1 for 30 min, Subscription #2 for 60 min). A Consumer (FOCOM) interacts with the IMS via O2ims interfaces for creating subscriptions and receiving measurement reports. Blue arrows show data flow from PM jobs to a local repository and then to the PSM. Red arrows show data flow from the PSM to the Consumer. Purple arrows show subscription and report activities over the O2ims interface. - -Figure 3.9-2 Performance Measurement Operation Example - -PM Job is a software task that collects measurements or telemetry data from O-Cloud resource(s). The PM Job primary function is to collect measurements or telemetry data based on a schedule; and it writes its measurements to a local repository. The PSM may take the raw data from local storage of data collected from PM Jobs and transforms it from the format in the local store to a report format. For example, the PM Job #1 collects as Measurement-A values 1, 3, 8. That is stored locally. The PSM takes those values to compose a performance report shown in figure 3.9-2. The blue shaded arrows are related to the PM job data collection. The red colored arrows are related to the PSM. The purple arrows are activities that happen over the O2ims interface. - -Figure 3.9-2 illustrates an example of the Performance Management framework. In this diagram, there are three O-Cloud Resources identified as Resource #1, Resource #2, Resource #3. There are four measurements identified as Measurement-A, Measurement-B, Measurement-C, Measurement-D that originate from these three different O-Cloud Resources. In this example, Measurement-A and Measurement-B originate from Resource #1. Measurement-C originates from Resource #2 and Measurement-D comes from Resource #3. There are four PM Jobs shown that collect Measurements specified when they are created. PM Job #1 collects Measurement-A with a collection interval of every 15 minutes. PM Job #2 collects Measurement-B with a collection interval of every 30 minutes. PM Job #3 collects Measurement-C with a collection interval of every 45 minutes. PM Job #4 collects Measurement-D with a collection interval of every 15 minutes. - -NOTE: If an operator would like to adjust the collection interval of a PM Job or adjust what measurements that PM Job is collecting it would require a PM Job update (See the PM Job Update Use Case [13]). - -The PSM within the IMS retrieves the data and composes a Measurement Report to be sent to the SMO. It does so at the specified reporting interval as defined by the subscription. For example, figure 3.9-2 shows two subscriptions. Subscription #1 has a reporting interval of 30 minutes with some combinations of measures that it reports on. Subscription #2 has a reporting interval of 60 minutes. - -The data store, shown as (🖽) in figure 3.9-2 is an internal store in the O-Cloud that is only accessible by the O-Cloud (in this case the PM Jobs and the PSM). The PM Job(s) may also direct O-Cloud Resource(s) to directly write primitive measure(s) to a data store. The realization of the PM Jobs is left up to implementation. - -### 3.9.10 Performance Measurement Transformation - -Performance Measurement Transformation is defined as taking primitive performance measurements and consequently adjusting those collected primitive measurements either syntactically or semantically. There are two kinds of performance measurement transformations: - -- Syntactic performance measurement transformations that change the format of the primitive measurement for storage and later retrieval. An example of syntactic performance measurement transformation might take raw data from a O-Cloud resource and store it into a JSON or Yang format as necessary. -- Semantic performance measurement transformations occur through meaningful calculations of primitive measures. An example of semantic performance measurement transformation are averages, means, and peaks that are derived from primitive measures. - -Transforming data is used during Performance Measurement reporting process. The PM Job creation would specify the measures and transformations their inputs, and outputs. - -![Figure 3.9-3: Semantic Performance Measurement Transformation Example. The diagram shows an O-Cloud containing Network Resource #1, which generates two primitive measurements (A and B) every 1 minute. These are processed by PM Job #1 at a 15-minute transformation interval to produce a semantic measurement (Network VLAN percentage utilization). This result is stored in a 15-minute utilization data store. The Infrastructure Management Service (IMS) contains a Performance Subscription Manager with Subscription #1 (60-minute reporting interval), which retrieves data from the data store and sends a Measurement Report to the Consumer (FOCOM).](a3083eec2a883ee8327b3c24174df6a9_img.jpg) - -``` - -graph LR - subgraph O-Cloud - NR[Network Resource #1] -- "Collection Interval 1 min" --> MA[Measurement A: Total Port VLAN Traffic] - NR -- "Collection Interval 1 min" --> MB[Measurement B: Network Port Traffic] - MA --> PMJ[PM Job #1] - MB --> PMJ - PMJ -- "Transformation Interval 15 min -Network VLAN percentage utilization..." --> DS[15 min Utilization Data store] - end - subgraph IMS [Infrastructure Management Service] - PSM[Performance Subscription Manager] -- "Reporting Interval 60 min -Subscription #1" --> MR[Measurement Report] - DS -.-> PSM - end - subgraph Consumer [Consumer FOCOM] - C[FOCOM] - end - C -- "Create Subscription" --> PSM - MR -- "O2ims: PM Data Sent, PM Notification" --> C - -``` - -The diagram illustrates the flow of performance measurement data. On the left, the O-Cloud contains Network Resource #1. This resource produces two primitive measurements: Measurement A (Total Port VLAN Traffic) and Measurement B (Network Port Traffic) at a collection interval of 1 minute. These measurements are processed by PM Job #1, which performs a semantic transformation to calculate 'Network VLAN percentage utilization of total Port Bandwidth'. This transformation occurs at a 15-minute interval. The result is stored in a '15 min Utilization Data store'. The Infrastructure Management Service (IMS) contains a 'Performance Subscription Manager' with 'Subscription #1' set to a 60-minute reporting interval. The manager retrieves data from the data store and generates a 'Measurement Report'. This report is sent to the Consumer (FOCOM) via O2ims interfaces, including 'Create Subscription', 'PM Data Sent (File, Stream, Event)', and 'PM Notification'. - -Figure 3.9-3: Semantic Performance Measurement Transformation Example. The diagram shows an O-Cloud containing Network Resource #1, which generates two primitive measurements (A and B) every 1 minute. These are processed by PM Job #1 at a 15-minute transformation interval to produce a semantic measurement (Network VLAN percentage utilization). This result is stored in a 15-minute utilization data store. The Infrastructure Management Service (IMS) contains a Performance Subscription Manager with Subscription #1 (60-minute reporting interval), which retrieves data from the data store and sends a Measurement Report to the Consumer (FOCOM). - -**Figure 3.9-3 Semantic Performance Measurement Transformation Example** - -An example of PM data collection using transformation is shown in figure 3.9-3, O-Cloud Network Resource #1 produces two primitive measures every minute. Measurement-A is the Network Port Traffic and Measurement-B is the Network Port VLAN Traffic. PM Job #1 collects these two primitive measures and performs semantical performance measurement transformation to produce Network VLAN percentage utilization of total port bandwidth which is Measurement A divided by Network Port Total Bandwidth. Another transformation would be Measurement B divided by Network Port Total Bandwidth because the utilization is defined as demand divided by capacity. PM Job #1 does this computation at a transformation interval of 15 minutes and writes the utilization to a local data store. Subscription #1 was created to report on the utilization. Its reporting interval is 60 minutes. Thus, it would have four data points for utilization every hour because PM Job #1 would store four data points within an hour. The Subscription #1 does not perform any further calculations. - -Note that PM Job #1 could also collect other primitive measures as well, and directly write that into the data store. That is, PM Job #1 is not always doing a semantical calculation or performance measurement transformation on data. - -### 3.9.11 Retention Period - -Performance Measurement records in the Performance Measurement Store conform to a Performance Management Policy which specifies how long Measurements should be retained in the Performance Measurement Store. - -Performance Measurement records are retained according to the retention policy of the O-Cloud based on the configured retention period. - -The Performance Measurement Store has one and only one Retention Period attribute, and it applies to all entries in the Performance Measurement Store. When Performance Measurement records in the Performance Measurement Store exceed the time for retention, those records are deleted or archived. - -There is a relationship between a deprecated Performance Measurement Job and the retention period. A deprecated Performance Measurement Job cannot be purged until all its associated Performance Measurement records in the Performance Measurement Store are deleted due to being older than the retention period. - -## 3.10 O-Cloud Operational Modes - -### 3.10.1 Overview - -Section 3.10 describes basic concepts related to the operational modes of O-Cloud Nodes. - -The state and status of the O-Cloud Nodes can be managed by SMO via O2 interfaces. In the following, the combination of the state and status of O-Cloud Nodes managed by SMO and the required operations specific to each mode are referred generically as operational modes. The following operational modes are further described: Maintenance mode (see section 3.10.2) and Test mode (see section 3.10.3). - -The O-Cloud operator can switch the operational mode of O-Cloud Nodes to handle specific operational requirements and events on the O-Cloud Nodes, for instance, a planned maintenance and/or functional test after fault recovery. In these cases, the behaviour and usage of O-Cloud Nodes changes according to the purposes of the operational mode. - -ITU-T X.731 defines administrative state and availability/control status which serves as the foundation of the maintenance mode and test mode concepts discussed here. - -The state transitions, what are legal states, and moving from one state to another will be described in future versions of the present document. - -### 3.10.2 Maintenance Mode - -Maintenance Mode is one of the operational modes of O-Cloud Nodes. The purpose of the Maintenance Mode is to indicate that it is under maintenance by changing the state of the managed entity. In Maintenance mode the resource is intended to be isolated and not used. This mode can be used in various use cases for fault recovery, O-Cloud Resources upgrade, and planned maintenance. - -The managed objects considered in this mode are the O-Cloud Nodes. - -NOTE 1: There could be other O-Cloud managed objects, to be described in future versions of the present document. - -O-Cloud operator switches the operational mode of O-Cloud Nodes into the Maintenance Mode using the O2ims and/or O2dms. While the O-Cloud Nodes are in Maintenance Mode, NFs/NF Deployments cannot utilize the O-Cloud Resources. - -NOTE 2: Implications of Maintenance Mode to different types of O-Cloud managed objects, the detailed meaning of Maintenance Mode for different forms of deployments (e.g., VM, container) may be described in future versions of the present document. - -### 3.10.3 Test Mode - -Test Mode is one of the operational modes of O-Cloud Nodes. The purpose of the Test Mode is to enable the means for the O-Cloud operator to test the O-Cloud Nodes using testing procedures. In Test Mode the resource can still be used but in a controlled manner typically for testing purposes. This Mode can be used after performing a maintenance of the O-Cloud Nodes, or after the O-Cloud initialization, or after installing new individual O-Cloud Nodes in the O-Cloud. - -The managed objects considered in this mode are the O-Cloud Nodes. - -NOTE 1: There could be other managed objects, but those may be described in future versions of the present document. - -O-Cloud operator switches the operational mode of O-Cloud Nodes into the Test Mode using the O2ims. O-Cloud Operator can check that the O-Cloud Node is able to operate correctly from a functional (e.g., behaviour, capabilities) and non-functional (e.g., performance) views. While the O-Cloud Nodes are in Test Mode, only test mode NF Deployments can utilize the O-Cloud Resources. - -NOTE 2: Implications of Test Mode to different types of O-Cloud managed objects such as a Test Mode NF Deployment, the detailed meaning of Test Mode for different forms of deployments (e.g., VM, container) may be described in future versions of the present document. - -NOTE 3: Alarm handling in Test Mode will be clarified in Alarm Suppression use case. - -# Annex A (informative): O-Cloud and IMS Initialization - -## A.1 Overview - -The present document does not dictate how O-Cloud is initialized and how initial endpoint for SMO to connect to is done. But here are some logical steps of the process to make it happen. This is included for informational purposes and not part of formal specification, please see Orchestration Use Cases [13]. - -1. SMO manually populated with a server that will be part of HW that is in O-Cloud. That server has connectivity to all other HW in the O-Cloud currently (at the start). The choice of that initial server is not important and is used only for bootstrapping (Genesis). -2. SMO deploys a minimalistic IMS functionality to initial server so it can do a subset of IMS functionality and bring O-Cloud up. At a minimum that IMS services should include infrastructure discovery, inventory, and administration within the O-Cloud; and deployment of O-Cloud with full IMS and DMS functionality. The configuration of the network might be sent to the server as part of its startup. In which case it might not have connectivity to all other HW but will have the ability to establish connectivity by configuring a transport path to servers in a non-collocated resource pool. -3. After O-Cloud deployment the initial server is no longer needed for minimalistic IMS services and can be returned into a pool of resources under O-Cloud control. The registration of the complete IMS services endpoint in the SMO, via a callback provided to the initial server, exposes the internal cloud services to the SMO via the IMS SBI. - -The present document does not define how O-Cloud with IMS services come into being. So, the above steps are provided for informational purposes only. - -## A.2 UML sequence diagram for O-Cloud and IMS initialization - -![UML sequence diagram for O-Cloud and IMS initialization. Lifelines: Personnel (Site Administrator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (O-Cloud Genesis Server). The sequence shows 6 steps: 1. Instantiate O-Cloud IMS, 2. Setup Server, 3. initial Server Ready, 4. Install Basic IMS, 5. IMS Cloud Infrastructure Resource Management services is ready, 6. Initial O-Cloud is Ready. Internal steps include 'Install Operating System and any necessary SW' and 'Install initial IMS'. The sequence ends with 'End Use Case'.](5c3dd31372f59e15250f0ab1613ca485_img.jpg) - -``` - -sequenceDiagram - actor Site Administrator as Site Administrator - participant FOCOM as Service Management & Orchestration Framework (FOCOM) - participant OCS as O-Cloud Platform (O-Cloud Genesis Server) - - Note right of OCS: Install Operating System and any necessary SW - Note right of OCS: Install initial IMS - - Site Administrator->>FOCOM: 1 Instantiate O-Cloud IMS - FOCOM->>OCS: 2 Setup Server - OCS-->>FOCOM: 3 initial Server Ready - FOCOM->>OCS: 4 Install Basic IMS - OCS-->>FOCOM: 5 IMS Cloud Infrastructure Resource Management services is ready - FOCOM-->>Site Administrator: 6 Initial O-Cloud is Ready - Note right of FOCOM: End Use Case - -``` - -UML sequence diagram for O-Cloud and IMS initialization. Lifelines: Personnel (Site Administrator), Service Management & Orchestration Framework (FOCOM), and O-Cloud Platform (O-Cloud Genesis Server). The sequence shows 6 steps: 1. Instantiate O-Cloud IMS, 2. Setup Server, 3. initial Server Ready, 4. Install Basic IMS, 5. IMS Cloud Infrastructure Resource Management services is ready, 6. Initial O-Cloud is Ready. Internal steps include 'Install Operating System and any necessary SW' and 'Install initial IMS'. The sequence ends with 'End Use Case'. - -Figure A-1 O-Cloud and IMS Initialization - -# Annex B (informative): O-Cloud Resource View examples and operations that use these Views - -Below follows a set of realistic examples of the four Resource views as specified in section 3.4.3.3 above. - -- Cloud Infrastructure Resources would typically include physical and logical Servers, Switches, Routers and Site Network Fabrics (as seen from the Green Robot head view) -- Abstracted Resources would typically offer physical O-Cloud Computer Systems, logical VMs and O-Cloud Site Networks (as seen from the Yellow Robot head view) -- Assigned Resources would typically include Nodes, Node Clusters and Node Cluster Site Networks (as seen from the Blue Robot head view) -- Consumed Resources would typically be CPU consumption of a Nodes, Packets transported on a NIC and Switch Port, Bandwidth used on a Site Network Fabric and Gateway (as seen from the Red Robot head view) - -Below follows a few natural flow examples of Resource handling that includes the four O-Cloud Resource views, - -1. A Cloud Site installation staff introduce a new physical Cloud Infrastructure Resource that is started up and found to be healthy and made available for the O-Cloud provisioning system as an O-Cloud ResourceType (as exemplified by the steps below) - - a. IMS adds the newly available Abstracted Resource to an O-Cloud Resource Pool, adds the O-Cloud Resource to the O-Cloud inventory and notify the subscribers of the inventory data of the relevant new/updated content - - b. SMO or IMS (if there is a pending demand for such a new Abstracted Resource) book the Abstracted Resource as a new Assigned Node for a Node Cluster - - c. DMS now have more capacity and possibly also new capabilities through the new Assigned Node and places a NF Deployment on the Node Cluster - - d. The NF Deployment (workload) Consumes the new Resource and gets the relevant metrics through the running Operating System drivers -2. FOCOM requests a new Node Cluster to be fulfilled by IMS without having any pre-assigned O-Cloud Resources available (as exemplified by the steps below) - - a. IMS searches for available and suitable Cloud Infrastructure Resources for the Control Plane Nodes and the Worker Nodes that can fulfil the requested capacity and characteristics of the Node Cluster - - b. IMS books the found and required Cloud Infrastructure Resources and creates Abstracted Resources for the Worker Nodes and the Node Cluster Site Networks that are then assigned to suitable Resource Pools - - c. The Abstracted Resources are Assigned to Nodes for the Worker Nodes and Node Cluster Site Networks for the Node Cluster - - d. IMS now starts up the Node Cluster using the Cluster Infrastructure Resources for the Control Plane Nodes, the Assigned Nodes for the Worker Nodes and the Assigned Node Cluster Site Networks for the Node Cluster communication - - e. IMS sets up the appropriate DMS user credentials and notifies FOCOM about the new inventory content as well as the DMS end-point that has been created - - f. SMO makes the new DMS available to the NFO - - g. NFO starts using the new DMS and request NF Deployments on it - - h. The NF Deployments (workloads) consume the Assigned Node Cluster and Node Resource and gets the relevant metrics through its running Operating System drivers - -# Annex C (informative): IMS example usage of ICS applied to ResourceTypes - -Below follows some examples of the Initiation Configuration Set as specified in section 3.4.3.7 above. These are only exemplifications to better understand the concept. The examples might include some non-aligned terms, and they should not be taken as new concepts or terms. - -ResourceTypes that are well suited to use ICS are Compute, HW-Accelerator, Site Network Fabric, storageunits and portgroups on any device e.g., Site Network Fabric and Compute. As an example of this flexibility for the deployed ResourceTypes, it is completely up to a specific Compute ResourceType specification to have its port configurations in the Compute ICS, in a separated portgroup ICS or have it dynamically selected during runtime. - -The IMS could be capable to understand and map O-Cloud ResourceTypes and their used ICS parameters that control their interconnections i.e., their network ports whenever the O-Cloud supports networking. This information could be used to automate or ensure that the interconnected resources are functional together when they are used as Assigned Resources e.g., in Node Clusters. Automation could be done e.g., through IMS selection of networking ResourceType ICS for the PortGroups. An example of matching ResourceType ICS is a server resource that need to have its NIC ports setup in a speed and termination type that matches the set of ports it connects to on the connected switch resources ports as exemplified in the figure below. - -![Figure C-1: Example of ICS Concept Usage. The diagram shows the process of applying an Initiation Configuration Set (ICS) to unconfigured resources to create initialized resources. On the left, the 'ICS Catalogue' lists various ICS templates like 'ComputeICS-1', 'ComputeICS-2', 'SnfPortGroupICS-1', 'SnfPortGroupICS-2', and 'SnfFabricICS-1'. Below it, 'Unconfigured Resources' show two servers (Server-1, Server-2) and a 'Site Network Fabric' with four ports. A central 'Wanted initialization' section details the desired configuration for the fabric and servers. A large blue arrow labeled 'Initialization: ICS applied' points to the right side, 'Initialized Resources used as Node related resources'. Here, the servers are now part of 'Node A' and 'Node B', with their ports configured according to the ICS templates (e.g., Port-1 and Port-2 are now LAGs). The 'Site Network Fabric' is also initialized with the appropriate ICS settings.](3493d7ba4c86f944e159de1bf45ff03d_img.jpg) - -Figure C-1: Example of ICS Concept Usage. The diagram shows the process of applying an Initiation Configuration Set (ICS) to unconfigured resources to create initialized resources. On the left, the 'ICS Catalogue' lists various ICS templates like 'ComputeICS-1', 'ComputeICS-2', 'SnfPortGroupICS-1', 'SnfPortGroupICS-2', and 'SnfFabricICS-1'. Below it, 'Unconfigured Resources' show two servers (Server-1, Server-2) and a 'Site Network Fabric' with four ports. A central 'Wanted initialization' section details the desired configuration for the fabric and servers. A large blue arrow labeled 'Initialization: ICS applied' points to the right side, 'Initialized Resources used as Node related resources'. Here, the servers are now part of 'Node A' and 'Node B', with their ports configured according to the ICS templates (e.g., Port-1 and Port-2 are now LAGs). The 'Site Network Fabric' is also initialized with the appropriate ICS settings. - -Figure C-1 Example of ICS Concept Usage - -# Annex D (normative): O-Cloud capabilities identification for use in LCM for the NF Deployment - -The O-Cloud and O-Cloud Node Clusters, in particular, have different capabilities, resources with different capabilities, and a subset of these capabilities are relevant to be understood by the SMO for use in homing and the lifecycle management of the NF Deployments. - -The standard O-Cloud capabilities identification aligns to what K8s resources can carry as part of the manifest (labels, annotations). - -These O-Cloud capabilities include, non-exhaustively: - -- AAL Profiles available (“aalProfileName” as defined in O-RAN.WG6.AAL Common API [x]), -- The labels that might be defined by the Node Feature Discovery (), feature labels which are referenced in the ASD TS [22]. Note that this does not include/reference the NFD daemon/mechanism as an implementation for provisioning these labels, -- Additional capabilities for the O-Cloud Node Clusters to support O-RAN features necessary for NF Deployments (e.g., the installed CNIs which extend the infrastructure capabilities such as secondary container cluster networking, etc). - -# Annex (informative): Change history/Change request (history) - -| Date | Revision | Description | -|------------|----------|------------------------------------------------------------------------------------------| -| 2023.11.13 | 05.00.01 | Implemented CRs ERI-0001-Networking, ERI-0021, NOK-0074, NOK-0050, and editorial updates | -| 2023.11.17 | 05.00.02 | Editorial updates based on review comments | -| 2023.11.28 | 06.00 | Final version 06.00 | -| 2024.03.19 | 06.00.01 | Implemented CRs DTAG-0002, DTAG-0003, and editorial updates | -| 2024.03.22 | 06.00.02 | Editorial updates based on review comments | -| 2024.04.01 | 07.00 | Final version 07.00 | -| 2024.07.15 | 07.00.01 | Implemented CRs ERI-0035, ERI-0033, ERI-0031, DTAG-004, DTAG-006, DCM-0006 | -| 2024.07.18 | 07.00.02 | Editorial updates based on review comments | -| 2024.07.29 | 08.00 | Final version 08.00 | -| 2024.11.14 | 08.00.01 | Implemented CR DCM-0006, and editorial updates | -| 2024.11.26 | 08.00.02 | Editorial updates based on review comments | -| 2024.12.09 | 08.01 | Final version 08.01 | -| 2025.07.11 | 08.01.01 | Implemented CRs ERI-0076, DCM-0007, ERI-0053, ERI-0073, ERI-0077, NOK-0159, NOK-0181 | -| 2025.07.17 | 08.01.02 | Editorial updates based on review comments | -| 2025.07.18 | 09.00 | Final version 09.00 | -| 2025.11.20 | 09.00.01 | Implemented CRs ERI-0086, NOK-0187, DCM-0008 | -| 2025.11.26 | 09.00.02 | Editorial updates based on review comments | -| 2025.11.28 | 09.00.03 | Updates based on review comments | -| 2025.11.28 | 10.00 | Final version 10.00 | \ No newline at end of file diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/0827b9260fe5458dbe416ebfc78c469e_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/08783c875dd39684fee7f2a40b584c64_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/14af8d47efd24c21fddf71b2415b6397_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/15e4a144a88176b71ea3eff2722253b0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/15e4a144a88176b71ea3eff2722253b0_img.jpg deleted file mode 100644 index 2413a33427a1948dd1a3bd885e364d7e1cfb2601..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/15e4a144a88176b71ea3eff2722253b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d80b3149331894b1161b07b685a5a4e07a65635943848cdd22f14a29f24718ab -size 114820 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/1b5a812c8aa20fd5cba28e97001d32de_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/1b5a812c8aa20fd5cba28e97001d32de_img.jpg deleted file mode 100644 index 8654039dd11245e03a227c74b248c2c4990de24a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/1b5a812c8aa20fd5cba28e97001d32de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:105d73537fd9d3d11ea9d7e93c46b35bda0147864193b2c3291ffcdcb4dec646 -size 201220 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/22f30783614672d201275c116a5d8516_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg deleted file mode 100644 index 2658b6f25b5ba587e8a94cc64986203790da1b50..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/2734e7f9be3e1dc046f14be2e6c9a085_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3b9976ceffcc5653d01925949d7ac59ace6c23cbf11e7b0d29da8fcbe8da2778 -size 106213 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/2ba086df3506f81bae3a9b53725dcfea_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/2ba086df3506f81bae3a9b53725dcfea_img.jpg deleted file mode 100644 index d33d9c85e1866fd656456120e567c14bcddb55c4..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/2ba086df3506f81bae3a9b53725dcfea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b39bcbfa8e61481b8075c25bb482692e9be6a5c94f2139bc5a76984091003340 -size 66583 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg deleted file mode 100644 index 8e9c440ac70850b81db8b292dd58e77e474399c1..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e83c725218338161094f0fef752f43c92332c440d43079ea65c776048e99c779 -size 59230 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/3493d7ba4c86f944e159de1bf45ff03d_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/3493d7ba4c86f944e159de1bf45ff03d_img.jpg deleted file mode 100644 index c7baba5af81414f755c47ebb471512297288bc52..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/3493d7ba4c86f944e159de1bf45ff03d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:cc22adca2c91862b2cbd5c2b500e0513ad81e7cef502326a7e13c3f6ae82122f -size 99982 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/366a77fdefb0097b3289b4a011911390_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/366a77fdefb0097b3289b4a011911390_img.jpg deleted file mode 100644 index 14303a4721d68af282271fe4f64d348019e4ef69..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/366a77fdefb0097b3289b4a011911390_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3a132a4569fba6aadd4d8c694d5c9231a3b3ed235a62af168927d44ccd4891ff -size 77508 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/38222c3ae003223a67635bfcc6950fbb_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/3f1987804d7d78bc3b3bc560e974280a_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/3f1987804d7d78bc3b3bc560e974280a_img.jpg deleted file mode 100644 index 245a6693acbe22f82fcf2306c5c509f43fe4807c..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/3f1987804d7d78bc3b3bc560e974280a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d10c9c4573d098e3c1717ca5152e31ea693a24d7372e92c167ad2a3ef1d0f977 -size 111070 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/3f727e6c0d6658bc53ea10905c4561dd_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/54fabc351eda5228d2fa28cd9ba07971_img.jpg deleted file mode 100644 index e1ef417b31c24e4a571887a99c4cc2e9ff295709..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/54fabc351eda5228d2fa28cd9ba07971_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e9941fda223bc8a6dbce4c56bee69ab21c299d621784e3c99b744c80bd4f3c62 -size 54827 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/59fcc0e3699f239444841881a2e75da0_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/5c3dd31372f59e15250f0ab1613ca485_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/5c3dd31372f59e15250f0ab1613ca485_img.jpg deleted file mode 100644 index a6cfa6f97486b316e77213a83a383c8a9a872997..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/5c3dd31372f59e15250f0ab1613ca485_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2942f2282b9869fbea71397df6c79d46e4a5471949f1e9be23f801931ea3f0f8 -size 74162 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/7f4320cee12fc1dbb865cc6b67462a91_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg deleted file mode 100644 index 173b7dbc44a2280bae97c622f2bb1f4e7ef457a9..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1f13fd11a09d9b685d2abe3153f15e330d8da684f97d29058fa25506a54f353c -size 139714 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/81b34087cd6755a80f84a70cf28fba82_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/83ee9f10bd3636e192d68decf7f04cec_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/8447c5519e85d7a9e029fbf321da4c4f_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/95e259e8cb3519025066052af263f8c0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/95e259e8cb3519025066052af263f8c0_img.jpg deleted file mode 100644 index aafc5dbe3263ff2d2cfa57dee069270de80f00de..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/95e259e8cb3519025066052af263f8c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:586eea8a358b66eb4dc3bfd1299f0b29289e9c251f30926f5741904f8d8760ab -size 104258 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/9ff1b32449ea068bba9647d71904bd59_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/9ff1b32449ea068bba9647d71904bd59_img.jpg deleted file mode 100644 index 3a9c743001348197f04a32dffe1ff646172ac3a3..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/9ff1b32449ea068bba9647d71904bd59_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b45db5b71c594aeb1a908151bbec8740f4d7462d1a9efcbf9cccf3d09a2830d2 -size 71053 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/a28ab03366399b5e0a61445bc57e3724_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/a3083eec2a883ee8327b3c24174df6a9_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/a3083eec2a883ee8327b3c24174df6a9_img.jpg deleted file mode 100644 index 8d195f9655f2b007b23f375fa5bee61e288008e2..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/a3083eec2a883ee8327b3c24174df6a9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:afa5c1b0b78c659d58c861543869d6896d30e3b9f79c736f3bf631cf07da830d -size 94314 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/a76a30cf23764f0b907220e7c3c70ce1_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/b58cedaf15ad4f0edee5621820865ccc_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/b58cedaf15ad4f0edee5621820865ccc_img.jpg deleted file mode 100644 index 0e5c64ecc916f895ed6fb7363588001459b30d2f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/b58cedaf15ad4f0edee5621820865ccc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8e168100c7494cebb6596c34104fcb6a4d41e0185a716e7b4a47c40b81119e71 -size 114641 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg deleted file mode 100644 index 4e082e0039908ab4614f25fad6017938665728c1..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/bc9d0c0b02cbe628b1b6548cc1107734_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ed561672a86ec3297be1b0dc9dc29e2fbf1407ea88702515d879e7fff5058eec -size 162783 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/bffdddb47fced140f8d17fdc2a29f592_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/bffdddb47fced140f8d17fdc2a29f592_img.jpg deleted file mode 100644 index 46da6781794ff1eef5f7d71f8acf96ead9dd695d..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/bffdddb47fced140f8d17fdc2a29f592_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a3bf1ce2ce26c0b9cda06c0ae772d49bf7162f163b8fd2f2a59e9156b63a41ec -size 51515 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/c1278da91cbcabe32628e589ebc47418_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/c1278da91cbcabe32628e589ebc47418_img.jpg deleted file mode 100644 index 545f743df8161ede4f413e63980a2e2f616ae509..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/c1278da91cbcabe32628e589ebc47418_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:293f7373eb9341485df411edc84739091b55a5645438aeeb7db92138613003cf -size 118155 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/c389468860cd886ab9c732473e959f0f_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/c4315e81a5a818379fcf31519a9c2cbe_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg deleted file mode 100644 index 530046fd52cf611838840cab95e3107e4ece084f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/c5655e700cc3e9aac7e9f4f07f30264d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0b88747eb9fb6760b632120f01ca70a8098569ddbd12cc9e1f02ec0dcec68c31 -size 115390 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/cb5f64aa26cee1c05257b7c6bbba7408_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg deleted file mode 100644 index b8f519f966a5bc74a050a0b0fe95e1e90f173fb8..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/d734a6ea1b381280f043fcf70391b6db_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9b37441ae4e47c8d799427c9b75f4b2789a0665d9c1ea5f22754ef65faa6caf2 -size 141193 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/d90d939bcbf43d474efaeeaa335a635c_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/d90f17b29a73eddf151f51effa8912e0_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/e038bf4fcea08f51944b4a2dd6e197a5_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/e038bf4fcea08f51944b4a2dd6e197a5_img.jpg deleted file mode 100644 index 9c19a7a054d4a97d0b37c8ebb93b41cb70a91801..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/e038bf4fcea08f51944b4a2dd6e197a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3182b046f5192ed512920715898f2864f7b0bab52201fad1f2a9af482731a89f -size 72103 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/e11e3fe4228e889a962514269f5a000b_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/e87df69ebd4cd2dbbf6749079e6c057a_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/f0a97d0d3818a253c1d2a009966081b1_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/f0a97d0d3818a253c1d2a009966081b1_img.jpg deleted file mode 100644 index e94661458c1e219fe118ed00cd221f2d892e33d6..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/f0a97d0d3818a253c1d2a009966081b1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e71905cf2f451620a3bc15bb9484d69856c4e614116cfe6eb4b1f86889568f33 -size 99313 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/f57a881fcbcaf494a7dedc4f61224991_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/f57a881fcbcaf494a7dedc4f61224991_img.jpg deleted file mode 100644 index 42a15e5fc34715fa6bb57f03e3de376afff23dcb..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/f57a881fcbcaf494a7dedc4f61224991_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c489e6fae92553217eb575f5f4d92e438213f68b7444638baa8ae7c5a0e01946 -size 66983 diff --git a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/f7dbd497160f02888f34fdf243648aa2_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/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 81287bbec96db7dcd5d4d3dbb5ce4b6f5babf828..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2-GA&P-R005-v10.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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/doc.md b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/doc.md deleted file mode 100644 index 2a9c3dd49db4c04c0042b3ecab95af1e8600974d..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/doc.md +++ /dev/null @@ -1,3789 +0,0 @@ - - -![O-RAN ALLIANCE logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) - -The logo for the O-RAN ALLIANCE, featuring a colorful circular icon to the left of the text "O-RAN" in blue, with "ALLIANCE" in smaller blue letters underneath. - -O-RAN ALLIANCE logo - -# --- **O-RAN Work Group 6 (Cloudification and Orchestration)****O2dms Interface Specification: Profile based on ETSI NFV** - -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 - -| | | -|----------------------------------------------------------------|----| -| List of figures..... | 4 | -| List of tables ..... | 4 | -| Foreword..... | 6 | -| Modal verbs terminology..... | 6 | -| Introduction ..... | 6 | -| 1 Scope ..... | 7 | -| 2 References ..... | 7 | -| 2.1 Normative references ..... | 7 | -| 2.2 Informative references..... | 9 | -| 3 Definition of terms, symbols and abbreviations ..... | 9 | -| 3.1 Terms..... | 9 | -| 3.2 Symbols..... | 9 | -| 3.3 Abbreviations ..... | 9 | -| 4 Profiling concepts..... | 10 | -| 4.1 Introduction ..... | 10 | -| 4.2 ETSI NFV framework and solutions ..... | 11 | -| 4.3 ETSI NFV profiling for O2dms interfaces ..... | 12 | -| 4.3.1 General..... | 12 | -| 4.3.2 Conceptual mappings..... | 13 | -| 4.3.3 API mappings ..... | 14 | -| 4.4 Service operations ..... | 14 | -| 4.4.1 Overview ..... | 14 | -| 4.4.2 NF Deployment lifecycle management..... | 15 | -| 4.4.3 NF Deployment fault management..... | 43 | -| 4.4.4 NF Deployment performance management ..... | 47 | -| 4.5 Orchestration aspects with O2dms ETSI NFV profile ..... | 57 | -| 4.5.1 O-Cloud Node Clusters, resource groups and tenancy ..... | 57 | -| 4.5.2 Placement information and constraints ..... | 58 | -| 4.5.3 Network connectivity for NF Deployments..... | 59 | -| 4.5.4 Software images information..... | 61 | -| 4.5.5 Resource management for NF Deployments ..... | 62 | -| 4.5.6 Acceleration abstraction layer..... | 63 | -| 4.5.7 DMS Interactions..... | 68 | -| 4.5.8 Monitoring of NF Deployments..... | 71 | -| 5 API definitions ..... | 72 | -| 5.1 General aspects..... | 72 | -| 5.1.1 Introduction..... | 72 | -| 5.1.2 URI structure and supported content formats ..... | 72 | -| 5.1.3 Usage of HTTP header fields..... | 73 | -| 5.1.4 Result set control ..... | 74 | -| 5.1.5 Error reporting ..... | 74 | -| 5.1.6 Common data types ..... | 74 | -| 5.1.7 Authorization of API requests and notifications..... | 76 | -| 5.1.8 Version management ..... | 76 | -| 5.1.9 HTTP conditional requests ..... | 77 | -| 5.2 O2dms_DeploymentLifecycle Service API ..... | 77 | -| 5.2.1 Description..... | 77 | -| 5.2.2 API version ..... | 77 | -| 5.2.3 REST resources structure and methods ..... | 77 | -| 5.2.4 REST resources ..... | 80 | -| 5.2.5 Notifications ..... | 82 | -| 5.2.6 Data model..... | 83 | -| 5.2.7 Error handling..... | 94 | - -- 5.3 O2dms\_DeploymentFault Service API .....96 - - 5.3.1 Description.....96 - - 5.3.2 API version .....96 - - 5.3.3 REST resources structure and methods .....96 - - 5.3.4 REST resources .....97 - - 5.3.5 Notifications .....98 - - 5.3.6 Data model.....98 -- 5.4 O2dms\_DeploymentPerformance Service API .....99 - - 5.4.1 Description.....99 - - 5.4.2 API version .....99 - - 5.4.3 REST resources structure and methods .....99 - - 5.4.4 REST resources .....101 - - 5.4.5 Notifications .....101 - - 5.4.6 Data model.....102 -- Annex A (Informative): Examples .....104 - - A.1 Overview .....104 - - A.2 AAL examples.....104 - - A.2.1 Example #1: Definition of acceleration capability requirements in NF Deployment descriptors .....104 - - A.2.2 Example #2: Definition of acceleration related configuration in NF Deployment descriptors and exchange of information on the O2dms interfaces .....105 - - A.2.3 Example #3: Exchange of information on the O2dms interfaces related to acceleration.....107 - - A.3 NF Deployment lifecycle examples .....108 - - A.3.1 Example #1: Healing procedure to recover from failure.....108 -- Annex (informative): Change History/Change request (history) .....110 - -# List of figures - -| | | -|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----| -| Figure 4.1-1: Representation of "O2-D demarcation #1" ..... | 11 | -| Figure 4.1-2: Representation of "O2-D demarcation #2" ..... | 11 | -| Figure 4.4.2.1-1: Flow of NF Deployment instantiation ..... | 17 | -| Figure 4.4.2.2-1: Flow of NF Deployment termination..... | 20 | -| Figure 4.4.2.3-1: Flow of NF Deployment termination..... | 22 | -| Figure 4.4.2.4.2-1: Flow of on-demand NF Deployment healing ..... | 24 | -| Figure 4.4.2.4.3-1: Flow of NF Deployment auto-healing ..... | 27 | -| Figure 4.4.2.5.2-1: Flow of NF Deployment scaling based on management request..... | 30 | -| Figure 4.4.2.5.3-1: Flow of NF Deployment auto-scaling ..... | 33 | -| Figure 4.4.2.6-1: Flow of changing external connectivity of NF Deployment..... | 36 | -| Figure 4.4.2.7-1: Flow of changing current NF Deployment package ..... | 39 | -| Figure 4.4.2.8-1: Flow of changing current NF Deployment package ..... | 42 | -| Figure 4.4.3.1-1: Flow of get alarm list of NF Deployment..... | 44 | -| Figure 4.4.3.2-1: Flow of fault management notifications associated to an NF Deployment ..... | 45 | -| Figure 4.4.3.3-1: Flow of acknowledging alarm of NF Deployment ..... | 46 | -| Figure 4.4.4.1-1: Flow of creating a PM job associated to an NF Deployment ..... | 47 | -| Figure 4.4.4.2-1: Flow of query/reading information of PM jobs associated to an NF Deployment ..... | 49 | -| Figure 4.4.4.3-1: Flow of deleting a PM job associated to an NF Deployment ..... | 50 | -| Figure 4.4.4.4-1: Flow of creating a threshold associated to an NF Deployment ..... | 51 | -| Figure 4.4.4.5-1: Flow of query/reading information of thresholds associated to an NF Deployment ..... | 52 | -| Figure 4.4.4.6-1: Flow of deleting a threshold associated to an NF Deployment ..... | 53 | -| Figure 4.4.4.7-1: Flow of performance management notifications associated to an NF Deployment..... | 55 | -| Figure 4.4.4.8-1: Flow of obtaining performance reports of NF Deployment ..... | 56 | -| Figure 4.5.1-1: Exemplary configuration of O-Cloud and DMS relationship with O-Cloud Node Clusters ..... | 57 | -| Figure 4.5.3-1: NF Deployment and networking concepts..... | 60 | -| Figure 4.5.6.2-1: Representation of elements in the NF Deployment package which can hold relevant configuration, capabilities, and placement requirements..... | 64 | -| Figure 4.5.7.2-1: Models in interactions ..... | 69 | -| Figure 4.5.7.2-2: Illustration of content in the O2dms and resource management models ..... | 70 | -| Figure 5.2.3-1: Resource URI structure of the O2dms_DeploymentLifecycle Service API ..... | 78 | -| Figure 5.3.3-1: Resource URI structure of the O2dms_DeploymentFault Service API..... | 96 | -| Figure 5.4.3-1: Resource URI structure of the O2dms_DeploymentPerformance Service API..... | 100 | - -# List of tables - -| | | -|--------------------------------------------------------------------------------------------------------|----| -| Table 4.3.2-1: Concepts mapping..... | 13 | -| Table 4.3.2-2: Management functions/functional blocks mapping ..... | 14 | -| Table 4.3.3-1: API mappings ..... | 14 | -| Table 4.5.6.4.2-1: Interface attributes for providing day-0 configuration to NF Deployments..... | 66 | -| Table 4.5.6.4.3-1: Interface attributes for providing day-1 configuration to NF Deployments..... | 68 | -| Table 4.5.7.2-1: Relationship between sets of content in the o2dms and resource management models..... | 70 | -| Table 5.1.1-1: Versions of the APIs specified in the present document..... | 72 | -| Table 5.1.6.1.3-1: Definition of the Link data type..... | 74 | -| Table 5.1.6.1.4-1: Definition of the NotificationLink data type..... | 75 | -| Table 5.1.6.1.6-1: ApiVersionInformation data type ..... | 75 | -| Table 5.1.6.2.2-1: Simple data types ..... | 76 | -| Table 5.2.3-1: Resources and methods overview ..... | 78 | -| Table 5.2.5.1-1: O2dms_DeploymentLifecycle notifications overview..... | 82 | -| Table 5.2.6.1-1: O2dms_DeploymentLifecycle resource data types..... | 83 | -| Table 5.2.6.4.2-1: Simple data types ..... | 89 | -| Table 5.2.6.5.3-1: Definition of ResourcePlacement data type..... | 90 | -| Table 5.2.6.5.4-1: Definition of ResourcePlacementConstraint data type ..... | 91 | -| Table 5.2.6.5.5-1: Definition of CloudAssets data type ..... | 92 | - -Table 5.2.6.5.9-1: Definition of PaasAsset data type .....93 -Table 5.3.3-1: Resources and methods overview .....97 -Table 5.3.5.1-1: O2dms\_DeploymentFault notifications overview .....98 -Table 5.3.6.1-1: O2dms\_DeploymentFault resource data types.....98 -Table 5.4.3-1: Resources and methods overview .....100 -Table 5.4.5.1-1: O2dms\_DeploymentPerformance notifications overview .....101 -Table 5.4.6.1-1: O2dms\_DeploymentFault resource data types.....102 -Figure A.3.1-1: Example of healing procedure to recover from failure .....109 - -# Foreword - -This Technical Specification (TS) has been produced by WG6 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 - -NOTE: From version v10.00, the present document follows the O-RAN.TS-template-v05. Consequently, numbering of clauses has been updated, in particular: clause 2 content in previous versions is now clause 4 of the present document version, clause 3 is changed to clause 5, and so on. In summary, technical content level-1 clauses have been renumbered as follows: [old-clause-number]+2. - -# 1 Scope - -The present document specifies the O-RAN O-Cloud's DMS interface protocol and data model based on the ETSI NFV solutions. - -# 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] Void[2] O-RAN.WG6.ORCH-USE-CASES (v03.00): "Cloudification and Orchestration Use Cases and Requirements for O-RAN Virtualized RAN". -- [3] Void. -- [4] O-RAN.WG6.TS.O2-GA&P (R004-v08.01): "O-RAN Working Group 6; O2 Interface; General Aspects and Principles". -- [5] ETSI GS NFV-IFA 005 (V5.1.1): "Network Functions Virtualisation (NFV) Release 5; Management and Orchestration; Or-Vi reference point – Interface and Information Model Specification". -- [6] ETSI GS NFV-IFA 006 (V5.1.1): " Network Functions Virtualisation (NFV) Release 5; Management and Orchestration; Vi-Vnfm reference point – Interface and Information Model Specification" -- [7] ETSI GS NFV-IFA 007 (V5.1.1): "Network Functions Virtualisation (NFV) Release 5; Management and Orchestration; Or-Vnfm reference point - Interface and Information Model Specification". -- [8] ETSI GS NFV-IFA 010 (V5.1.1): "Network Functions Virtualisation (NFV) Release 5; Management and Orchestration; Functional requirements specification". -- [9] ETSI GS NFV-IFA 040 (V5.1.1): "Network Functions Virtualisation (NFV) Release 5; Management and Orchestration; Requirements for service interfaces and object model for OS container management and orchestration specification". -- [10] ETSI GS NFV-SOL 001 (V5.1.1): "Network Functions Virtualisation (NFV) Release 5; Protocols and Data Models; NFV descriptors based on TOSCA specification". -- [11] ETSI GS NFV-SOL 003 (V5.1.1): "Network Functions Virtualisation (NFV) Release 5; Protocols and Data Models; RESTful protocols specification for the Or-Vnfm Reference Point". -- [12] ETSI GS NFV-IFA 011 (V5.1.1): "Network Functions Virtualisation (NFV) Release 5; Management and Orchestration; VNF Descriptor and Packaging Specification". -- [13] ETSI GS NFV-SOL 004 (V5.1.1): "Network Functions Virtualisation (NFV) Release 5; Protocols and Data Models; VNF Package and PNFD Archive specification". -- [14] ETSI GS NFV-SOL 006 (V4.3.1): "Network Functions Virtualisation (NFV) Release 4; Protocols and Data Models; NFV descriptors based on YANG specification". -- [15] ETSI GS NFV-SOL 013 (V5.1.1): "Network Functions Virtualisation (NFV) Release 5; Protocols and Data Models; Specification of common aspects for RESTful NFV MANO APIs". -- [16] ETSI GS NFV-SOL 014 (V5.1.1): "Network Functions Virtualisation (NFV) Release 5; Protocols and Data Models; YAML data model specification for descriptor-based virtualised resource management". - -- [17] ETSI GS NFV-SOL 015 (V1.2.1): "Network Functions Virtualisation (NFV); Protocols and Data Models; Specification of Patterns and Conventions for RESTful NFV-MANO APIs". -- [18] ETSI GS NFV-SOL 018 (V5.1.1): "Network Functions Virtualisation (NFV) Release 5; Protocols and Data Models; Profiling specification of protocol and data model solution for OS container management and orchestration". -- [19] ETSI NFV Registries: "VIM connection information registry". -- NOTE: Available at [https://nfvwiki.etsi.org/index.php?title=VIM\\_connection\\_information](https://nfvwiki.etsi.org/index.php?title=VIM_connection_information). -- [20] IETF RFC 793: "Transmission Control Protocol". -- NOTE: Available at . -- [21] IETF RFC 3339: "Date and Time on the Internet: Timestamps". -- NOTE: Available at . -- [22] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". -- NOTE: Available at . -- [23] IETF RFC 5246: "The Transport Layer Security (TLS) Protocol Version 1.2". -- NOTE: Available at . -- [24] IETF RFC 7230: "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing". -- NOTE: Available at . -- [25] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format". -- NOTE: Available at . -- [26] JSON Schema: "Core definitions and terminology", Version draft-07, November 19, 2017. -- NOTE 1: Draft-07 is available at . -- NOTE 2: The specification is available as Internet Draft at . -- [27] OpenAPI™ Specification. -- NOTE 1: Available at . -- NOTE 2: The OpenAPI™ Word Mark and OpenAPI Logo are either registered trademarks/service marks or trademarks/service marks of the Linux Foundation, in the United States and other countries and are used with the Linux Foundation's permission. O-RAN Alliance is not affiliated with, endorsed or sponsored by the Linux Foundation, or the Linux Foundation community. -- [28] Void -- [29] ETSI GS NFV-SOL 002 (V5.1.1): "Network Functions Virtualisation (NFV) Release 5; Protocols and Data Models; RESTful protocols specification for the Ve-Vnfm Reference Point". -- [30] Void. -- [31] O-RAN.WG6.AAL-GAnP.0 (v05.00): "O-RAN Acceleration Abstraction Layer; General Aspects and Principles". -- [32] O-RAN.WG6.AAL-Common-API (v03.00): "Acceleration Abstraction Layer; Common API". -- [33] Void. -- [34] ETSI GS NFV-IFA 027 (V5.1.1): "Network Functions Virtualisation (NFV) Release 5; Management and Orchestration; Performance Measurements Specification". - -- [35] ETSI GS NFV-IFA 045 (V5.2.1): "Network Functions Virtualisation (NFV) Release 5; Management and Orchestration; Fault and alarms modelling specification". -- [36] IETF RFC 2818: "HTTP over TLS". -- NOTE: Available at . -- [37] ETSI TS 133 310 (V18.3.0): "Universal Mobile Telecommunications System (UMTS); LTE; 5G; Network Domain Security (NDS); Authentication Framework (AF) (3GPP TS 33.310 version 18.3.0 Release 18)". - -## 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] O-RAN.WG6.CAD (v02.01): "Cloud Architecture and Deployment Scenarios for O-RAN Virtualized RAN". -- [i.3] ETSI GR NFV 003 (V1.8.1): "Network Functions Virtualisation (NFV); Terminology for Main Concepts in NFV". -- [i.4] ETSI GR NFV-EVE 022 (V5.1.1): "Network Functions Virtualisation (NFV) Release 5; Architectural Framework; Report on VNF configuration". - -# --- 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. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [i.1]. - -## 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. 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]. - -| | | -|-----|-----------------------------------| -| API | Application Programming Interface | -| CIR | Container Image Registry | -| CIS | Container Infrastructure Service | - -| | | -|----------|-----------------------------------------------------------------| -| CISM | Container Infrastructure Service Management | -| DMS | Deployment Management Services | -| FOCOM | Federated O-Cloud Orchestration & Management | -| HTTP | Hypertext Transfer Protocol | -| IMS | Infrastructure Management Services | -| JSON | JavaScript Object Notation | -| LCM | Lifecycle Management | -| MCIO | Managed Container Infrastructure Object | -| MCIO_P | Managed Container Infrastructure Object Package | -| NF | Network Function | -| NFO | Network Function Orchestration | -| NFV | Network Functions Virtualisation | -| NFV-MANO | NFV Management and Orchestration | -| NFVI | NFV Infrastructure | -| NFVO | NFV Orchestrator | -| REST | Representational state transfer | -| SMO | Service Management and Orchestration | -| TOSCA | Topology and Orchestration Specification for Cloud Applications | -| TLS | Transport Layer Security | -| URI | Uniform Resource Identifier | -| VIM | Virtualised Infrastructure Manager | -| VIP | Virtual IP | -| VL | Virtual Link | -| VM | Virtual Machine | -| VNF | Virtualized Network Function | -| VNFC | VNF Component | -| VNFD | VNF Descriptor | -| VNFM | VNF Manager | - -# 4 Profiling concepts - -## 4.1 Introduction - -The O-RAN framework follows similar principles as other frameworks and solutions related to network functions virtualisation and cloudification that have been or are being specified in other organizations, such as in the ETSI NFV. O-RAN.WG6.ORCH-USE-CASES [2] documents a set of use cases regarding the deployment of O-RAN NF on O-Clouds, as well as it specifies relevant functional and interface requirements between the SMO and O-Cloud. O-RAN.WG6.CAD [i.2] documents the cloudification deployment aspects of O-RAN NF based on VMs, OS container in VMs, or OS containers. These same forms of NF deployment are also considered by the ETSI NFV framework. - -With the objective to reuse existing network operator assets, e.g., as presently in use in other network deployments beyond RAN, the present document aims at specifying a profile of the ETSI NFV specifications that can also be used for the deployment of O-RAN NF on O-Clouds. - -The present O-Cloud O2dms profile based on ETSI NFV demarcates a defined protocol and data model between the SMO and O-Cloud based on the standardized virtualised resource, containerized workload, and VNF management capabilities of the functional entities and functions of the NFV-MANO architectural framework summarized in clause 4.2. - -In the definition of the applicable protocol and data models to profile, two main demarcations can be defined depending on the end point of interaction of the SMO towards the O-Cloud: - -- "O2-D demarcation #1": SMO interacts with a DMS that offer VNFM-like functionality. This case considers a more abstract "NF Deployment" view, i.e., DMS supports deployment of defined O-RAN NFs. The "NF Deployment" view is also referred in numerous use cases of O-RAN.WG6.ORCH-USE-CASES [2]. The "NF Deployment" concept is defined in the O-RAN.WG6.TS.O2-GA&P [4] and O-RAN.WG6.CAD [i.2]. Clause 2.2.1 of the same O-RAN.WG6.TS.O2-GA&P [4] describes the DMS as the functional block responsible for the management of NF Deployments into the O-Cloud. -- "O2-D demarcation #2": SMO interacts with a DMS that offers virtualised resource/containerized workload management functionality; thus, SMO performs VNFM-like functionality. This case considers a more granular "virtualised resource/containerized workload" management view, i.e., DMS has no notion at all of O-RAN NFs. - -These two demarcation cases are depicted in figures 4.1-1 and 4.1-2, respectively. - -NOTE 1: VIM/CISM and NFVI/CIS placement in the architecture figures are not meant to be accurate and it is not the focus of these figures to present the architectural mappings of other elements such as SMO, NFVO, etc. Purpose of the figures is to illustrate the demarcations/boundaries of applicability for the O2dms ETSI NFV profiles. - -NOTE 2: More information about the NFV-MANO architectural framework is provided in clause 4.2. - -![Figure 4.1-1: Representation of 'O2-D demarcation #1'. This diagram shows the O-RAN architecture where the SMO (Service Management and Orchestration) block contains the EM (Element Management) and NFVO (NFV Orchestrator). The NFVO is connected to the OSS/BSS via the Os-Ma-nfvo interface and to the VNFM via the Or-Vnfm interface. The VNFM contains a DMS (Deployment and Management Service) and is connected to the VNF via the Ve-Vnfm-vnf interface. The VNF is connected to the NFVI/CIS via the Nf-Vi interface. The NFVI/CIS is part of the O-Cloud. The O2-D demarcation point is shown as a red line between the NFVO and the VNFM, indicating the boundary of the O2dms profile. Other interfaces shown include Or-Or, Ve-Vnfm-em, and Or-Vi.](5e92d9e8e9ce204e405bff2367f88176_img.jpg) - -Figure 4.1-1: Representation of 'O2-D demarcation #1'. This diagram shows the O-RAN architecture where the SMO (Service Management and Orchestration) block contains the EM (Element Management) and NFVO (NFV Orchestrator). The NFVO is connected to the OSS/BSS via the Os-Ma-nfvo interface and to the VNFM via the Or-Vnfm interface. The VNFM contains a DMS (Deployment and Management Service) and is connected to the VNF via the Ve-Vnfm-vnf interface. The VNF is connected to the NFVI/CIS via the Nf-Vi interface. The NFVI/CIS is part of the O-Cloud. The O2-D demarcation point is shown as a red line between the NFVO and the VNFM, indicating the boundary of the O2dms profile. Other interfaces shown include Or-Or, Ve-Vnfm-em, and Or-Vi. - -Figure 4.1-1: Representation of "O2-D demarcation #1" - -![Figure 4.1-2: Representation of 'O2-D demarcation #2'. This diagram shows the O-RAN architecture where the SMO block contains the EM and the VNFM. The VNFM contains a DMS and is connected to the VNF via the Ve-Vnfm-vnf interface. The VNF is connected to the NFVI/CIS via the Nf-Vi interface. The NFVI/CIS is part of the O-Cloud. The O2-D demarcation point is shown as a red line between the VNFM and the VIM/CISM, indicating the boundary of the O2dms profile. Other interfaces shown include Or-Or, Os-Ma-nfvo, Ve-Vnfm-em, Or-Vnfm, and Or-Vi.](c78c2eefd86269d1740ab85a916f24f2_img.jpg) - -Figure 4.1-2: Representation of 'O2-D demarcation #2'. This diagram shows the O-RAN architecture where the SMO block contains the EM and the VNFM. The VNFM contains a DMS and is connected to the VNF via the Ve-Vnfm-vnf interface. The VNF is connected to the NFVI/CIS via the Nf-Vi interface. The NFVI/CIS is part of the O-Cloud. The O2-D demarcation point is shown as a red line between the VNFM and the VIM/CISM, indicating the boundary of the O2dms profile. Other interfaces shown include Or-Or, Os-Ma-nfvo, Ve-Vnfm-em, Or-Vnfm, and Or-Vi. - -Figure 4.1-2: Representation of "O2-D demarcation #2" - -The present document version specifies an ETSI NFV profile of the O2dms protocol and data models based on the "O2-D demarcation #1". - -NOTE 3: A profile based on "O2-D demarcation #2" is FFS. - -## 4.2 ETSI NFV framework and solutions - -ETSI NFV defines the NFV-MANO architectural framework, which is conformed of a set of functional blocks, functions and interfaces enabling the deployment and management of VM and container-based VNFs. The management of virtualised and container-based resources is performed by technology and solution agnostic functional entities according to a specified set of interfaces, models and APIs. - -The list of NFV-MANO architectural framework functional blocks and functions and their main responsibilities are: - -- Virtualised Infrastructure Manager (VIM): responsible for the management of virtualised resources (virtual compute, virtual network and virtual storage) in the NFV Infrastructure (NFVI) and VM software images, -- Container Infrastructure Service Management (CISM): responsible for the management of container-based resources and container workloads in Container Infrastructure Service (CIS) clusters, -- Container Image Registry (CIR): responsible for the management of OS container software images, - -- VNF Manager (VNFM): responsible for the management of VNFs, including their lifecycle, and provides corresponding management services based on a common set of interfaces and models regardless of the technology used for implementing the VNF, be it container or VM-based, and -- NFV Orchestrator (NFVO): responsible for the management of VNF Packages and other artifacts and the overall orchestration of NFVI resources across multiple sites (referred as well as NFVI-PoPs) and the lifecycle management of Network Services (NS). - -ETSI GS NFV-IFA 010 [8] specifies the principles and scope of the NFV-MANO architectural framework and functional requirements of the functional blocks and functions that are part of it. - -A set of groups specifications (GS) specifies the interfaces exposed and consumed by the NFV-MANO functional blocks and functions. The following are the GS of relevance for the present document: - -- ETSI GS NFV-IFA 007 [7] specifies stage 2 interfaces and associated information model of interfaces between the NFVO and the VNFM. ETSI GS NFV-SOL 003 [11] specifies stage 3 protocols and data models of these interfaces based on RESTful. The Release 4 version of ETSI GS NFV-SOL 003 [11] adds support for container-based VNF deployments. Refer to clause 4.4.1 for the specific version and features (VM and/or OS container-based deployments) supported by the present document. -- ETSI GS NFV-IFA 005 [5] specifies stage 2 interfaces and associated information models of interfaces between the NFVO and the VIM, which aim, among others features, at supporting VM-based NF deployments. ETSI GS NFV-SOL 014 [16] specifies a stage 3 data model of parameters for virtualised resource descriptors based on YAML. -- ETSI GS NFV-IFA 006 [6] specifies stage 2 interfaces and associated information models of interfaces between the VNFM and the VIM, which aim, among others features, at supporting VM-based NF deployments. ETSI GS NFV-SOL 014 [16] specifies a stage 3 data model of parameters for virtualised resource descriptors based on YAML. -- ETSI GS NFV-IFA 040 [9] specifies stage 2 interfaces and service requirements of interfaces produced by the CISM and CIR, which aim, among other features, at supporting OS container-based NF deployments. ETSI GS NFV-SOL 018 [18] aims at specifying stage 3 protocols and data models of these interfaces profiled on de-facto solutions. Refer to clause 4.4.1 for the specific version and features (VM and/or OS container-based deployments) supported by the present document. - -In addition to the composition of the NFV-MANO architectural framework in terms of functional blocks, functions and interfaces, one of the key aspects is the definition of both design-time and runtime elements. Design-time elements basically comprise those objects and artifacts that describe the design and requirements for the deployment of entities into or using the framework. The design-time objects comprise packages and descriptors, among which the relevant ones for the present document are the VNF Package and VNF Descriptor (VNFD). - -- ETSI GS NFV-IFA 011 [12] specifies stage 2 requirements related to VNF Package and VNF metadata and the information model of the VNFD. ETSI GS NFV-SOL 001 [10] specifies stage 3 data model of the VNFD (in addition to other descriptors such as Network Service Descriptor (NSD) and Physical Network Function Descriptor (PNFD)) based on TOSCA, while ETSI GS NFV-SOL 006 [14] specifies the same elements but based on YANG. ETSI GS NFV-SOL 004 [13] specifies the data model and structure of the VNF Packages. - -## 4.3 ETSI NFV profiling for O2dms interfaces - -### 4.3.1 General - -The present and subsequent clauses describe specific aspects of the ETSI NFV profiling for the O2dms interfaces. In the present profiling version based on the "O2-D demarcation #1" introduced in clause 4.1, the functional capabilities of the NFVO, VNFM, VIM and CISM of the NFV-MANO architectural framework are mapped to the O-RAN framework as defined in clause 4.3.2. - -The O2dms ETSI NFV profile based on "O2-D demarcation #1" is based on the ETSI GS NFV-SOL 003 [11]. The ETSI GS NFV-SOL 003 [11] specifies, among others, the RESTful API of the "VNF Lifecycle Management interface", which is used as the foundation for providing a DMS exposed API for the lifecycle management of NF Deployments of O-RAN. Specific API correspondences are defined in clause 4.3.3. - -Finally, for the orchestration and management operations through the O2dms ETSI NFV profile, it is assumed that descriptors and packaging of corresponding NF Deployments, and consequently of O-RAN NF, are on-boarded and available to the SMO and DMS. In particular, it is expected that the descriptors and packaging for O-RAN NF contain relevant metadata such as identifiers of the design-time definitions of components/constituents of an NF Deployment, which are also information either conveyed or exposed through the API. Additional mapping information about descriptor and packaging artifacts is provided in clause 4.3.2, and reference to specific elements concerning various orchestration aspects are further described in clause 4.5. - -### 4.3.2 Conceptual mappings - -The terminology and concepts used in referenced ETSI NFV specifications differs compared to the terminology used in O-RAN specifications. - -Table 4.3.2-1 defines the mapping and correspondences of management concepts and terms applicable for the O2dms service APIs and to the profiling specified in the present document version. - -**Table 4.3.2-1: Concepts mapping** - -| O-RAN concept | ETSI NFV concept | Description | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| O-RAN NF | NS or VNF |

In the case of an O-RAN NF that is composed of multiple NF Deployments, the O-RAN NF can be realized by the NS construct abstractions; however, the NS abstraction is not visible over the O2dms, and it is only understood by the responsible SMO functions when composing the set of NF Deployments realizing the O-RAN NF.

In the case of an O-RAN NF that is composed of a single NF Deployment, the O-RAN NF maps one-to-one to a VNF in terms of lifecycle management.

| -| NF Deployment | VNF | In terms of lifecycle management, a VNF instance maps one-to-one to an NF Deployment. A VNF instance is composed of one or more VNF Component (VNFC), and VNFCs can be deployed and managed based on NF Deployment items. | -| NF Deployment unit | VNFC | An NF Deployment unit, as described in Annex A of O-RAN.WG6.ORCH-USE-CASES [2], maps one-to-one to a deployable unit in a VNF. Deployable units of a VNF are VNFCs. As defined in ETSI GR NFV 003[i.3], a VNFC is an internal component of a VNF providing a subset of the VNF's functionality, with the main characteristic that a single instance of a VNFC maps to a single instance of an atomic deployable unit. An atomic deployable unit can be a single VM for hypervisor-based virtualization or one or a set of OS containers (e.g., a Pod in case of Kubernetes®) for OS-based virtualization. See note 2. | -| O-RAN NF software package | VNF package | A VNF package contains all the required files and metadata descriptors required to validate and instantiate a VNF. The structure and format of a VNF package file and its constituents are defined in ETSI GS NFV-SOL 004 [13]. | -| NF Deployment descriptor | VNFD | A VNFD describes the infrastructure resource requirements, design constraints, dependencies, and the operational behaviour, including VNF lifecycle events, of the VNF. The information model of the VNFD is defined in ETSI GS NFV-IFA 011 [12]. ETSI GS NFV-SOL 001 [10] specifies a TOSCA-based data model for the VNFD, and ETSI GS NFV-SOL 006 [14] specifies a YANG-based data model for the VNFD. See note 1. | -| NOTE 1: Parts of the profiled ETSI GS NFV-SOL 003's model references elements of a VNFD as sources of information also available at runtime over the interfaces, but the same specification does not specify a specific format and data model of a VNFD to be used. | | | -| NOTE 2: To fulfil connectivity requirements of a VNFC, an NF Deployment can also include internal VL and/or express requirements for external connectivity. At a high-level, a VL represents the network connectivity interconnecting two or more entities such as VNFC, VNF, and it is realized by the one or more (virtual) networks. For more information, refer to clause 4.5.3 on "network connectivity for NF Deployments". | | | - -Table 4.3.2-2 defines the mapping and correspondence of management functions and functional blocks that apply to endpoints of the O2 interface and to the profiling specified in the present document version. - -**Table 4.3.2-2: Management functions/functional blocks mapping** - -| O-RAN concept | ETSI NFV concept | Description | -|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| DMS (NF Deployment part) | VNFM | The VNFM functional block (FB) produced functionality maps to the DMS's NF Deployment functionality.
The DMS produces O2dms service interfaces which are mapped to VNFM produced interfaces. See note 1. | -| DMS (virtualised resources management part) | VIM | The VIM FB produced functionality maps to the DMS's virtualised resources management functionality. See note 2. | -| DMS (containerized workloads management part) | CISM | The CISM function produced services maps to the DMS's containerized workloads management functionality. See note 3. | -| SMO (NFO part) (see note 4) | NFVO (network service management part) | The NFVO's network service management functionality maps to the SMO's NFO.
The NFO consumes O2dms service interfaces according to the profiled VNFM produced interfaces in the present document. | -| SMO (FOCOM part) (see note 4) | NFVO (resource orchestration part) | The NFVO's resources orchestration functionality maps to the SMO's FOCOM. | -| NOTE 1: DMS is defined in O-RAN.WG6.TS.O2-GA&P [4] as a functional block, but without specifying dedicated parts as indicated in the present table. The parts introduced in the present table are defined for the purpose of establishing a relevant mapping functional block or function from the NFV-MANO architectural framework. | | | -| NOTE 2: In ETSI NFV standards, VIM also handles part of infrastructure management, which can be mapped to O-Cloud IMS. IMS is also defined in O-RAN.WG6..TS.O2-GA&P [4] and O-RAN.WG6.CAD[i.2]. | | | -| NOTE 3: In ETSI NFV standards, CISM also handles part of container cluster management, which can be mapped to O-Cloud IMS. IMS is also defined in O-RAN.WG6.TS.O2-GA&P [4] and O-RAN.WG6.CAD [i.2]. | | | -| NOTE 4: The FOCOM and NFO, part of the SMO, are defined in O-RAN.WG6.TS.O2-GA&P [4]. | | | - -### 4.3.3 API mappings - -The APIs specified in the present document map to the referenced standard APIs listed in table 4.3.3-1. - -**Table 4.3.3-1: API mappings** - -| O2dms service API | Referenced standard API | -|-----------------------------|-------------------------------------------------------------------------------------------| -| O2dms_DeploymentLifecycle | "VNF Lifecycle Management interface" specified in clause 5 of ETSI GS NFV-SOL 003 [11]. | -| O2dms_DeploymentFault | "VNF Fault Management interface" specified in clause 7 of ETSI GS NFV-SOL 003 [11]. | -| O2dms_DeploymentPerformance | "VNF Performance Management interface" specified in clause 6 of ETSI GS NFV-SOL 003 [11]. | - -## 4.4 Service operations - -### 4.4.1 Overview - -The present document provides the protocol and data model profiling for the O2dms interface based on the ETSI NFV standards and covering a specific subset of service interfaces and operations. The defined service interfaces and operations are listed in the subsequent clauses. - -The service interfaces and operations specified in the present document references the latest published Release 5 version of the ETSI GS NFV-SOL 003 [11], which is the one used in the protocol and data model profiling in clause 5. As indicated in clause 4.2, the Release 4 version of ETSI GS NFV-SOL 003 0 adds support for OS container-based NF deployments, and some relevant features are also documented in clause 4.5. - -### 4.4.2 NF Deployment lifecycle management - -#### 4.4.2.1 Instantiate NF Deployment - -Clause 3.2.1 of O-RAN.WG6.ORCH-USE-CASES [2] describes the use case of "Instantiate Network Function on O-Cloud", which includes steps of requesting the lifecycle management operation of instantiating NF Deployments. Related requirements are specified in clause 4.3 of O-RAN.WG6.ORCH-USE-CASES [2]. In addition, clause 3.7.1 of O-RAN.WG6.TS.O2-GA&P [4] lists for the O-Cloud the capability of deploying an O-RAN Cloudified NF instance. - -To instantiate an NF Deployment using the present O2dms API profile, the following sub-procedures are applicable: - -- 1) creation of "Individual VNF instance" resource corresponding to the NF Deployment as illustrated by the "Flow of the creation of a VNF instance resource" in clause 5.3.1 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure of creation of the VNF instance resource is further profiled as illustrated in figure 4.4.2.1-1. -- 2) instantiation of the NF Deployment by triggering the operation "Instantiate VNF" performed via the corresponding task resource "Instantiate VNF task" on the "Individual VNF instance" resource following the flow illustrated in "Flow of VNF lifecycle management operations triggered by task resources" in clause 5.3.3 of ETSI GS NFV-SOL 003 [11]. the case of an NF Deployment, the sub-procedure of VNF instantiation is further profiled as illustrated in figure 4.4.2.1-1. - -NOTE 1: While the profiled ETSI GS NFV-SOL 003 [11] VNF instantiation procedure contains steps related to VNF LCM granting exchanges between the VNFM and the NFVO of the NFV-MANO framework, the NF Deployment instantiation procedure specified in the present document version does not contain these steps. - -In addition, to monitor the status of the lifecycle operation in an asynchronous mode and be able to know the status of the operation (e.g., whether in progress or in some failed status), the API consumer shall request the creation of corresponding subscriptions to NF Deployment lifecycle management events following the flow "Flow of managing subscriptions" in clause 5.3.8 of ETSI GS NFV-SOL 003 [11]. The API consumer may also monitor the status of a lifecycle operation by query and reading information about the VNF LCM operation occurrence, which tracks the progress of the lifecycle operation. - -Figure 4.4.2.1-1 illustrates the procedure flow for the instantiation of an NF Deployment including the two sub-procedures introduced above. - -![Sequence diagram showing the interaction between SMO (NFO) and O-Cloud (DMS) for NF deployment. It includes two sub-procedures: 'Creation of Individual NF Deployment resource' and 'Instantiation of NF Deployment'. The diagram shows message exchanges, preconditions, postconditions, and optional steps.](0f985b39edc1d52ba3600c438bc8f0a5_img.jpg) - -**Sub-procedure: Creation of "Individual NF Deployment" resource** - -Precondition: None - -- 1 POST .../vnf\_instances (CreateVnfRequest) -- 2 Check availability of VNF package and creates VNF instance resource for new NF Deployment -- 3 201 Created (VnfInstance) -- 4 Send VnfIdentifierCreationNotification - -Postcondition: "Individual VNF instance" resource representing the NF Deployment is created in NOT\_INSTANTIATED state - -**Sub-procedure: Instantiation of NF Deployment** - -Precondition: "Individual VNF instance" resource representing the NF Deployment is created And in NOT\_INSTANTIATED state - -- 5 POST .../vnf\_instances/{vnfInstanceId}/instantiate (InstantiateVnfRequest) -- 6 Create VNF LCM operation occurrence resource for the instantiation -- 7 202 Accepted () -- 8 Send VnfLcmOperationOccurrenceNotification(STARTING) -- 9 Check granted resources, placement information and availability of deployment items -- 10 Send VnfLcmOperationOccurrenceNotification(PROCESSING) -- 11 NF Deployment instantiation proceeds with allocation of necessary O-Cloud resources -- 12 GET .../vnf\_lcm\_op\_occs/{vnfLcmOpOccId} -- 13 200 OK (VnfLcmOpOcc:operationState=PROCESSING) -- 14 NF Deployment instantiation is completed -- 15 Send VnfLcmOperationOccurrenceNotification(COMPLETED) -- 16 GET .../vnf\_lcm\_op\_occs/{vnfLcmOpOccId} -- 17 200 OK (VnfLcmOpOcc:operationState=COMPLETED) - -Postcondition: NF Deployment is instantiated and in INSTANTIATED state - -Sequence diagram showing the interaction between SMO (NFO) and O-Cloud (DMS) for NF deployment. It includes two sub-procedures: 'Creation of Individual NF Deployment resource' and 'Instantiation of NF Deployment'. The diagram shows message exchanges, preconditions, postconditions, and optional steps. - -**Figure 4.4.2.1-1: Flow of NF Deployment instantiation** - -NOTE 2: Due to possible race conditions, the 201 response and the VnfIdentifierCreationNotification can arrive in any order at the SMO. - -NOTE 3: Due to possible race conditions, the 202 response and the "STARTING" VnfLcmOperationOccurrenceNotification can arrive in any order at the SMO. - -The procedure of NF Deployment instantiation consists of the following steps as illustrated in figure 4.4.2.1-1: - -NOTE 4: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** None. - -- 1) The SMO sends a POST request to the "VNF instances" resource including in the message content a data structure of type "CreateVnfRequest". -- 2) The DMS checks the availability of the NF Deployment package (referred as VNF Package in the figure) and creates a new "Individual VNF instance" resource that represents the NF Deployment. - -NOTE 5: It is expected that the NF Deployment package contents are available to the O-Cloud DMS, or that the DMS can check the availability of the package as onboarded to the SMO. - -- 3) The DMS returns a 201 Created response containing a representation of the "Individual VNF instance" resource, which represents the NF Deployment, and provides the URI of the newly created resource in the "Location" HTTP header. See note 2. -- 4) The DMS sends a VNF Identifier Creation Notification to the SMO to indicate the creation of the "Individual VNF instance" resource and the associated VNF instance identifier of the NF Deployment, if the SMO is subscribed to such type of notifications. See note 2. -- 5) The SMO sends a POST request to the "Instantiate VNF task" resource that represents the NF Deployment instantiation lifecycle operation to be executed on the NF Deployment and includes in the message content a data structure of type "InstantiateVnfRequest". -- 6) The DMS creates a new "Individual VNF LCM operation occurrence" resources for the request, which represents the lifecycle operation occurrence about the NF Deployment instantiation. -- 7) The DMS returns a "202 Accepted" response with an empty message content and a "Location" HTTP header that points to the new "Individual VNF LCM operation occurrence" resource. See note 3. -- 8) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate the start of the lifecycle management operation occurrence with the "STARTING" state, if the SMO is subscribed to such type of notifications. See note 3. -- 9) The DMS checks the granted resources, placement information and availability of deployment items for the NF Deployment instantiation. -- 10) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence enters the "PROCESSING" state, if the SMO is subscribed to such type of notifications. -- 11) The DMS proceeds with the NF Deployment instantiation with the allocation of necessary O-Cloud resources. -- 12) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the ongoing lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 13) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". -- 14) The DMS completes the NF Deployment instantiation. - -- 15) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence is "COMPLETED", if the SMO is subscribed to such type of notifications. -- 16) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the completed lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 17) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". - -**Postcondition:** The NF Deployment is instantiated and in "INSTANTIATE" state. - -**Error handling:** If the NF Deployment lifecycle operation fails, error information is provided in the notification messages that reports about the erroneous completion of the procedure. Error information is also available in the resource that represents the "Individual VNF lifecycle management operation occurrence" related to the NF Deployment lifecycle management operation. - -#### 4.4.2.2 Terminate NF Deployment - -Clause 3.2.5 of O-RAN.WG6.ORCH-USE-CASES [2] describes the use case of "Terminate Network Function on O-Cloud", which includes steps of requesting the lifecycle management operation of terminating NF Deployments. Related requirements are specified in clause 4.3 of O-RAN.WG6.ORCH-USE-CASES [2]. In addition, clause 3.7.1 of O-RAN.WG6.TS.O2-GA&P [4] lists for the O-Cloud the capability of terminating an O-RAN Cloudified NF instance. - -To terminate an NF Deployment using the present O2dms API profile, the following sub-procedures are applicable: - -- 1) termination of the NF Deployment by triggering the operation "Terminate VNF" performed via the corresponding task resource "Terminate VNF task" on the "Individual VNF instance" resource following the flow illustrated in "Flow of VNF lifecycle management operations triggered by task resources" in clause 5.3.3 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure of VNF termination is further profiled as illustrated in figure 4.4.2.2-1. -- 2) deletion of the "Individual VNF instance" resource representing the NF Deployment as illustrated by the "Flow of the deletion of a VNF instance resource" in clause 5.3.2 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure of deletion of the VNF instance resource is further profiled as illustrated in figure 4.4.2.2-1. - -In addition, to monitor the status of the lifecycle operation in an asynchronous mode and be able to know the status of the operation (e.g., whether in progress or in some failed status), the API consumer shall request the creation of corresponding subscriptions to NF Deployment lifecycle management events following the flow "Flow of managing subscriptions" in clause 5.3.8 of ETSI GS NFV-SOL 003 [11]. The API consumer may also monitor the status of a lifecycle operation by query and reading information about the VNF LCM operation occurrence, which tracks the progress of the lifecycle operation. - -Figure 4.4.2.2-1 illustrates the procedure flow for the termination of an NF Deployment instance including the two sub-procedures introduced above. - -![Sequence diagram showing the termination and deletion of an NF Deployment between SMO (NFO) and O-Cloud (DMS).](2b3a967f6ce4f23649be995a353e39f8_img.jpg) - -**Sub-procedure: Termination of NF Deployment** - -Precondition: -"Individual VNF instance" resource representing the NF Deployment is in INSTANTIATED state - -- 1 POST ../vnf\_instances/{vnfInstanceId}/terminate (TerminateVnfRequest) -- 2 Create VNF LCM operation occurrence resource for the termination -- 3 202 Accepted () -- 4 Send VnfLcmOperationOccurrenceNotification(STARTING) -- 5 Check conditions for terminating the NF Deployment -- 6 Send VnfLcmOperationOccurrenceNotification(PROCESSING) -- 7 NF Deployment termination proceeds with termination of allocated O-Cloud resources -- 8 GET ../vnf\_lcm\_op\_occs/{vnfLcmOpOccId} -- 9 200 OK (VnfLcmOpOcc:operationState=PROCESSING) -- 10 NF Deployment termination is completed -- 11 Send VnfLcmOperationOccurrenceNotification(COMPLETED) -- 12 GET ../vnf\_lcm\_op\_occs/{vnfLcmOpOccId} -- 13 200 OK (VnfLcmOpOcc:operationState=COMPLETED) - -Postcondition: -NF Deployment is terminated -"Individual VNF instance" resource representing the NF Deployment is in NOT\_INSTANTIATED state - -**Sub-procedure: Deletion of "Individual NF Deployment" resource** - -Precondition: -"Individual VNF instance" resource representing the NF Deployment is in NOT\_INSTANTIATED state - -- 14 DELETE ../vnf\_instances/{vnfInstanceId} -- 15 Delete "Individual VNF instance" resource representing the NF Deployment -- 16 204 No Content -- 17 Send VnfIdentifierDeletionNotification - -Postcondition: -"Individual VNF instance" resource that represented the NF Deployment is removed - -Sequence diagram showing the termination and deletion of an NF Deployment between SMO (NFO) and O-Cloud (DMS). - -**Figure 4.4.2.2-1: Flow of NF Deployment termination** - -NOTE 1: Due to possible race conditions, the 204 response and the VnfIdentifierDeletionNotification can arrive in any order at the SMO. - -NOTE 2: Due to possible race conditions, the 202 response and the "STARTING" VnfLcmOperationOccurrenceNotification can arrive in any order at the SMO. - -The procedure of NF Deployment termination consists of the following steps as illustrated in figure 4.4.2.2-1: - -NOTE 3: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** The "Individual VNF instance" resource representing the NF Deployment is in INSTANTIATED state. - -- 1) The SMO sends a POST request to the "Terminate VNF task" resource that represents the NF Deployment termination lifecycle operation to be executed on the NF Deployment and includes in the message content a data structure of type "TerminateVnfRequest". -- 2) The DMS creates a new "Individual VNF LCM operation occurrence" resources for the request, which represents the lifecycle operation occurrence about the NF Deployment termination. -- 3) The DMS returns a "202 Accepted" response with an empty message content and a "Location" HTTP header that points to the new "Individual VNF LCM operation occurrence" resource. See note 2. -- 4) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate the start of the lifecycle management operation occurrence with the "STARTING" state, if the SMO is subscribed to such type of notifications. See note 2. -- 5) The DMS checks the conditions for terminating the NF Deployment. -- 6) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence enters the "PROCESSING" state, if the SMO is subscribed to such type of notifications. -- 7) The DMS proceeds with the NF Deployment termination with the termination of allocated O-Cloud resources of the NF Deployment. -- 8) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the ongoing lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 9) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". -- 10) The DMS completes the NF Deployment termination. -- 11) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence is "COMPLETED", if the SMO is subscribed to such type of notifications. -- 12) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the completed lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 13) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". -- 14) The SMO sends a DELETE request to the "Individual VNF instance" resource that represented the NF Deployment. -- 15) The DMS deletes the "Individual VNF instance" resource that represented the NF Deployment and the associate NF Deployment identifier. -- 16) The DMS returns to the SMO a "204 No Content" response with an empty message content. See note 1. -- 17) The DMS sends to the SMO a VNF Identifier Deletion Notification to indicate the deletion of the "Individual VNF instance" resource that represented the NF Deployment and the associated NF Deployment identifier. See note 1. - -**Postcondition:** The NF Deployment is terminated and the "Individual VNF instance" resource that represented the NF Deployment is removed. - -**Error handling:** If the NF Deployment lifecycle operation fails, error information is provided in the notification messages that reports about the erroneous completion of the procedure. Error information is also available in the resource that represents the "Individual VNF lifecycle management operation occurrence" related to the NF Deployment lifecycle management operation. - -#### 4.4.2.3 Query NF Deployment information - -**NOTE:** The O-RAN.WG6.ORCH-USE-CASES [2] neither describes use cases about querying information of "NF Deployment" or O-RAN NF, nor specifies related functional and interface requirements. Clause 3.7.1 of the O-RAN.WG6.TS.O2-GA&P [4] lists the querying information about an O-RAN Cloudified NF instance as one of the expected functional capabilities of the O-Cloud. The profiled ETSI GS NFV-SOL 003 [11] provides the capabilities to query information about "NF Deployments" by enabling the necessary HTTP methods on corresponding REST resources. This provides a more complete set of functionalities to the SMO to query information about NF Deployments that have been instantiated. The present document version includes such a functionality and service operation, even though it is not a target for the O-RAN WG6's "2022 March Train". - -To query information about one or more NF Deployment instances using the present O2dms API profile, the following sub-procedures are applicable: - -- To query information about multiple NF Deployment instances, execute a GET method on the "VNF instances" resource following the flow illustrated in "Flow of the Query VNF operation" in clause 5.3.5 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure of query information of multiple VNF instances is further profiled as illustrated in figure 4.4.2.3-1. -- To query information about a specific NF Deployment instance, execute a GET method on the "Individual VNF instance" resource following the flow illustrated in "Flow of the Query VNF operation" in clause 5.3.5 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure of query information of a particular VNF instance is further profiled as illustrated in figure 4.4.2.3-1. - -Figure 4.4.2.3-1 illustrates the procedure flow for querying information about a specific NF Deployment instance or multiple ones. - -![Sequence diagram showing the interaction between SMO (NFO) and O-Cloud (DMS) for querying NF Deployment information. The diagram includes a precondition, an 'alt' block for multiple vs. individual queries, and a postcondition.](608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg) - -``` - -sequenceDiagram - participant SMO as SMO (NFO) - participant O-Cloud as O-Cloud (DMS) - - Note right of SMO: Precondition: -For querying specific NF Deployment instance, the NF Deployment is created -None, otherwise - - alt Query information about multiple NF Deployments - SMO->>O-Cloud: 1 GET .../vnf_instances - O-Cloud-->>SMO: 2 200 OK (VnfInstance[]) - else Read information about individual NF Deployment - SMO->>O-Cloud: 3 GET .../vnf_instances/{vnfInstanceId} - O-Cloud-->>SMO: 4 200 OK (VnfInstance) - end - - Note right of SMO: Postcondition: -SMO has the queried/read information about the one or more NF Deployments - -``` - -Sequence diagram showing the interaction between SMO (NFO) and O-Cloud (DMS) for querying NF Deployment information. The diagram includes a precondition, an 'alt' block for multiple vs. individual queries, and a postcondition. - -**Figure 4.4.2.3-1: Flow of NF Deployment termination** - -The procedure of query NF Deployment information consists of the following steps as illustrated in figure 4.4.2.3-1: - -NOTE: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** For querying a specific NF Deployment, the NF Deployment is created. None, otherwise. - -- 1) If the SMO intends to query information about multiple NF Deployments, it sends a GET request to the "VNF instances" resource that contains the set of NF Deployments. -- 2) The DMS returns a "200 OK" response to the SMO and includes zero or more data structures of type "VnfInstance" in the message content, depending on the query result. -- 3) If the SMO intends to read information about a particular NF Deployment, it sends a GET a request to the "Individual VNF instance" resource with the appropriate NF Deployment identifier. -- 4) The DMS returns a "200 OK" response to the SMO and includes one data structure of type "VnfInstance" in the message content. - -**Postcondition:** The SMO has the queried/read information about the one or more NF Deployments. - -**Error handling:** In case of failure, appropriate error information is provided in the response. - -#### 4.4.2.4 Heal NF Deployment - -##### 4.4.2.4.1 Overview - -Clause 3.6 of O-RAN.WG6.ORCH-USE-CASES [2] describes use cases about recovery at different level. Clause 3.6.2 of O-RAN.WG6.ORCH-USE-CASES [2] details the "NF Deployment level reset use case". According to the use case, when some fatal error is identified which is expected (but not guaranteed) it can be resolved by resetting the NF Deployment, the SMO can send a specific reset request to the DMS over the O2dms interface. In addition, clause 3.7.1 of O-RAN.WG6.TS.O2-GA&P [4] lists for the O-Cloud the capability of healing an O-RAN Cloudified NF instance. From the ETSI NFV profile perspective, the (part of) reset capabilities can be performed via a "Healing VNF instance" operation. - -As defined in ETSI GR NFV 003 [i.3], VNF healing is a lifecycle procedure that includes all virtualisation-related corrective actions to repair a faulty VNF, and/or its VNFC instances and internal VNF Virtual Links (refer to concepts mapping in clause 4.3.2). The procedure is intended to leverage the resource virtualisation management capabilities such as, starting/stopping/restarting VMs, re-allocating VMs or containerized workloads, and other possible actions, as means to recover from faulty conditions of the VNF. Furthermore, VNF healing can be performed on-demand when a consumer explicitly requests to the producer of the lifecycle management operation or automatically triggered by the producer, also referred as "auto-healing", based on various inputs such as indicators, alarms and KPIs processed from the VNF and/or infrastructure. - -NOTE: As described above, VNF healing considers virtualisation-related corrective actions, and it does not cover other possible VNF correction actions at the application level. - -The healing capabilities of a VNF are defined by the VNF provider through the VNF descriptors. The specific list of parameters to convey the trigger of what healing action to perform are also defined through VNF descriptors (see generic information modelling in clause 7.1.5.6 of ETSI GS NFV-IFA 011 [12]). Healing actions can be different between VNFs and there are no specific means specified by the referenced ETSI NFV specifications to determine what actions are applicable to a VNF instance and not to another VNF instance as this are regarded to be VNF-specific and implementation dependent. From an interface perspective, the VNF healing operation enables the consumer to provide the list of expected parameters and their values as defined in the actual descriptors delivered by the VNF provider in the VNF package. Dedicated LCM scripts (see clause 7.1.13 in ETSI GS NFV-IFA 011 [12]) either defined via the VNF descriptors or as additional artifacts implement the logic of the concrete procedure actions. The details of the request inputs to trigger the NF Deployment healing are specified in clause 5.2.6.2.9. - -##### 4.4.2.4.2 On-demand healing - -To perform the on-demand heal of an NF Deployment using the present O2dms API profile, the following sub-procedures are applicable: - -- 1) healing of the NF Deployment by triggering the operation "Heal VNF" performed via the corresponding task resource "Heal VNF task" on the "Individual VNF instance" resource following the flow illustrated in "Flow of VNF lifecycle management operations triggered by task resources" in clause 5.3.3 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure of VNF healing is further profiled as illustrated in figure 4.4.2.4.2-1. - -NOTE 1: While the profiled ETSI GS NFV-SOL 003 [11] VNF healing procedure contains steps related to VNF LCM granting exchanges between the VNFM and the NFVO of the NFV-MANO framework, the NF Deployment healing procedure specified in the present document version does not contain these steps. - -In addition, to monitor the status of the lifecycle operation in an asynchronous mode and be able to know the status of the operation (e.g., whether in progress or in some failed status), the API consumer shall request the creation of corresponding subscriptions to NF Deployment lifecycle management events following the flow "Flow of managing subscriptions" in clause 5.3.8 of ETSI GS NFV-SOL 003 [11]. The API consumer may also monitor the status of a lifecycle operation by query and reading information about the VNF LCM operation occurrence, which tracks the progress of the lifecycle operation. - -Figure 4.4.2.4.2-1 illustrates the procedure flow for the healing of an NF Deployment including the sub-procedure introduced above. - -![Sequence diagram titled 'Healing of NF Deployment' showing the interaction between SMO (NFO) and O-Cloud (DMS). The process involves sending a heal request, receiving a 202 Accepted response, and then receiving notifications for STARTING, PROCESSING, and COMPLETED states. The diagram includes preconditions and postconditions for the NF deployment state.](366a77fdefb0097b3289b4a011911390_img.jpg) - -**Healing of NF Deployment** - -Precondition: -"Individual VNF instance" resource representing the NF Deployment is in INSTANTIATED state - -- 1 <> POST .../vnf\_instances/{vnfInstanceId}/heal (HealVnfRequest) → -- 2 Create VNF LCM operation occurrence resource for the healing -- 3 <> 202 Accepted () ← -- 4 <> Send VnfLcmOperationOccurrenceNotification(STARTING) ← -- 5 Check granted resources, placement information and availability of deployment items -- 6 <> Send VnfLcmOperationOccurrenceNotification(PROCESSING) ← -- 7 NF Deployment healing proceeds with termination, allocation and restart of necessary O-Cloud resources -- 8 <> GET .../vnf\_lcm\_op\_occs/{vnfLcmOpOccId} → (opt) -- 9 <> 200 OK (VnfLcmOpOcc.operationState=PROCESSING) ← -- 10 NF Deployment healing is completed -- 11 <> Send VnfLcmOperationOccurrenceNotification(COMPLETED) ← -- 12 <> GET .../vnf\_lcm\_op\_occs/{vnfLcmOpOccId} → (opt) -- 13 <> 200 OK (VnfLcmOpOcc.operationState=COMPLETED) ← - -Postcondition: -NF Deployment is healed and in INSTANTIATED state - -Sequence diagram titled 'Healing of NF Deployment' showing the interaction between SMO (NFO) and O-Cloud (DMS). The process involves sending a heal request, receiving a 202 Accepted response, and then receiving notifications for STARTING, PROCESSING, and COMPLETED states. The diagram includes preconditions and postconditions for the NF deployment state. - -Figure 4.4.2.4.2-1: Flow of on-demand NF Deployment healing - -NOTE 2: Due to possible race conditions, the 202 response and the "STARTING" VnfLcmOperationOccurrenceNotification can arrive in any order at the SMO. - -The procedure of on-demand NF Deployment healing consists of the following steps as illustrated in figure 4.4.2.4.2-1: - -NOTE 3: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** "Individual VNF instance" resource representing the NF Deployment is in INSTANTIATED state. - -- 1) The SMO sends a POST request to the "Heal VNF task" resource that represents the NF Deployment healing lifecycle operation to be executed on the NF Deployment and includes in the message content a data structure of type "HealVnfRequest". -- 2) The DMS creates a new "Individual VNF LCM operation occurrence" resources for the request, which represents the lifecycle operation occurrence about the NF Deployment healing. -- 3) The DMS returns a "202 Accepted" response with an empty message content and a "Location" HTTP header that points to the new "Individual VNF LCM operation occurrence" resource. See note 2. -- 4) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate the start of the lifecycle management operation occurrence with the "STARTING" state, if the SMO is subscribed to such type of notifications. See note 2. -- 5) The DMS checks the granted resources, placement information and availability of deployment items for the NF Deployment healing. The DMS also checks the specific actions (e.g., terminate and create new deployment item, restart a deployment item, etc.) to be performed for the healing based on the information contained in the descriptors of the NF Deployment. -- 6) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence enters the "PROCESSING" state, if the SMO is subscribed to such type of notifications. -- 7) The DMS proceeds with the NF Deployment healing with the allocation, termination and restart of necessary O-Cloud resources. -- 8) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the ongoing lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 9) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". -- 10) The DMS completes the NF Deployment healing. -- 11) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence is "COMPLETED", if the SMO is subscribed to such type of notifications. -- 12) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the completed lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 13) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". - -**Postcondition:** The NF Deployment is healed and in "INSTANTIATED" state. - -**Error handling:** If the NF Deployment lifecycle operation fails, error information is provided in the notification messages that reports about the erroneous completion of the procedure. Error information is also available in the resource that represents the "Individual VNF lifecycle management operation occurrence" related to the NF Deployment lifecycle management operation. - -##### 4.4.2.4.3 Auto-healing - -To perform the auto-healing of an NF Deployment using the present O2dms API profile, the following sub-procedures are applicable: - -- 1) auto-healing of the NF Deployment triggered by the DMS based on the detection of the healing condition following the flow illustrated in "Flow of automatic invocation of VNF scaling and VNF healing" in clause 5.3.4 of - -ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure of VNF healing is further profiled as illustrated in figure 4.4.2.4.3-1. - -NOTE 1: While the profiled ETSI GS NFV-SOL 003 [11] VNF auto-healing procedure contains steps related to VNF LCM granting exchanges between the VNFM and the NFVO of the NFV-MANO framework, the NF Deployment healing procedure specified in the present document version does not contain these steps. - -For the DMS to trigger the auto-healing, two conditions shall be met: - -- The auto-healing is enabled on the NF Deployment. This, in the ETSI GS NFV-SOL 003 based profile, is controlled via setting the corresponding attribute value of "isAutohealEnabled" in the "vnfConfigurableProperties" of the "VnfInstance" data type that represents the NF Deployment instance (see clause 5.2.6.2.2) and that the DMS manages. Changing the value of the attribute is made upon request by the API consumer (e.g., the SMO) by "patching" the corresponding "Individual VNF instance" resource of the NF Deployment. Patching and NF Deployment does not require re-instantiating the NF Deployment. - -NOTE 2: PATCHing of the "Individual VNF instance" resource, which represents the NF Deployment, to support modifying information of an NF Deployment is supported as indicated in clause 5.2.3. - -- The healing condition is met, e.g., by monitoring alarms related to faults of virtualised resources/containerized workloads part of the NF Deployment, NF Deployment-specific indicators like "health degradation" and/or performance data (via PM jobs or Thresholds) of the NF Deployment such as degradation of input/output packet transfer on connection points of the NF Deployment. The criterion for fulfilling the condition is NF Deployment-specific and implementation dependent and not specified in the present document. - -In addition, to monitor the status of the lifecycle operation in an asynchronous mode and be able to know the status of the operation (e.g., whether in progress or in some failed status), the API consumer shall request the creation of corresponding subscriptions to NF Deployment lifecycle management events following the flow "Flow of managing subscriptions" in clause 5.3.8 of ETSI GS NFV-SOL 003 [11]. The API consumer may also monitor the status of a lifecycle operation by query and reading information about the VNF LCM operation occurrence, which tracks the progress of the lifecycle operation. The API consumer can know that the operation has been triggered automatically as the attribute "isAutomaticInvocation" of the "VnfLcmOperationOccurrenceNotification" (see clause 5.2.5.2) and the "VnfLcmOpOcc" (see clause 5.2.6.2.3) is set to "true". - -Figure 4.4.2.4.3-1 illustrates the procedure flow for the auto-healing of an NF Deployment including the sub-procedure introduced above. - -![Sequence diagram titled 'Auto-healing of NF Deployment' showing the interaction between SMO (NFO) and O-Cloud (DMS). The process starts with a precondition where the VNF instance is INSTANTIATED and auto-healing is enabled. The sequence includes: 1. DMS detects a healing condition; 2. Create VNF LCM operation occurrence resource; 3. SMO receives STARTING notification; 4. DMS checks resources; 5. SMO receives PROCESSING notification; 6. DMS performs auto-healing (termination, allocation, restart); 7-8. SMO GETs and receives 200 OK for PROCESSING state; 9. DMS completes auto-healing; 10. SMO receives COMPLETED notification; 11-12. SMO GETs and receives 200 OK for COMPLETED state. The postcondition is that the NF Deployment is automatically healed and INSTANTIATED.](a149b400127a3e3e50b3c98d27c5935c_img.jpg) - -**Auto-healing of NF Deployment** - -**Precondition:** -"Individual VNF instance" resource representing the NF Deployment is in INSTANTIATED state -Auto-healing is enabled on the "Individual VNF instance resource" - -- DMS detects a healing condition that triggers auto-healing -- Create VNF LCM operation occurrence resource for the auto-healing -- <> Send VnfLcmOperationOccurrenceNotification(STARTING) -- Check granted resources, placement information and availability of deployment items -- <> Send VnfLcmOperationOccurrenceNotification(PROCESSING) -- NF Deployment auto-healing proceeds with termination, allocation and restart of necessary O-Cloud resources -- <> GET .../vnf\_lcm\_op\_occs/{vnfLcmOpOccId} -- <> 200 OK (VnfLcmOpOcc:operationState=PROCESSING) -- NF Deployment auto-healing is completed -- <> Send VnfLcmOperationOccurrenceNotification(COMPLETED) -- <> GET .../vnf\_lcm\_op\_occs/{vnfLcmOpOccId} -- <> 200 OK (VnfLcmOpOcc:operationState=COMPLETED) - -**Postcondition:** -NF Deployment is automatically healed and in INSTANTIATED state - -Sequence diagram titled 'Auto-healing of NF Deployment' showing the interaction between SMO (NFO) and O-Cloud (DMS). The process starts with a precondition where the VNF instance is INSTANTIATED and auto-healing is enabled. The sequence includes: 1. DMS detects a healing condition; 2. Create VNF LCM operation occurrence resource; 3. SMO receives STARTING notification; 4. DMS checks resources; 5. SMO receives PROCESSING notification; 6. DMS performs auto-healing (termination, allocation, restart); 7-8. SMO GETs and receives 200 OK for PROCESSING state; 9. DMS completes auto-healing; 10. SMO receives COMPLETED notification; 11-12. SMO GETs and receives 200 OK for COMPLETED state. The postcondition is that the NF Deployment is automatically healed and INSTANTIATED. - -Figure 4.4.2.4.3-1: Flow of NF Deployment auto-healing - -The procedure of NF Deployment auto-healing consists of the following steps as illustrated in figure 4.4.2.4.3-1: - -NOTE 3: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** "Individual VNF instance" resource representing the NF Deployment is in INSTANTIATED state and auto-healing is enabled on the "Individual VNF instance resource". - -- 1) The DMS detects a healing condition that triggers the auto-healing of the NF Deployment and selects the appropriate parameters for the operation to proceed based on the information contained in the descriptors of the NF Deployment or operational policies. -- 2) The DMS creates a new "Individual VNF LCM operation occurrence" resources for the operation, which represents the lifecycle operation occurrence about the NF Deployment auto-healing. -- 3) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate the start of the lifecycle management operation occurrence with the "STARTING" state, if the SMO is subscribed to such type of notifications. -- 4) The DMS checks the granted resources, placement information (see clause 4.5.2 and 5.2.6.5 which document related information) and availability of deployment items for the NF Deployment auto-healing. The DMS also checks the specific actions (e.g., terminate and create new deployment item, restart a deployment item, etc.) to be performed for the auto-healing based on the information contained in the descriptors of the NF Deployment. -- 5) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence enters the "PROCESSING" state, if the SMO is subscribed to such type of notifications. -- 6) The DMS proceeds with the NF Deployment auto-healing with the allocation, termination and restart of necessary O-Cloud resources. -- 7) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the ongoing lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 8) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". -- 9) The DMS completes the NF Deployment auto-healing. -- 10) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence is "COMPLETED", if the SMO is subscribed to such type of notifications. -- 11) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the completed lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 12) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". - -**Postcondition:** The NF Deployment is automatically healed and in "INSTANTIATED" state. - -**Error handling:** If the NF Deployment lifecycle operation fails, error information is provided in the notification messages that reports about the erroneous completion of the procedure. Error information is also available in the resource that represents the "Individual VNF lifecycle management operation occurrence" related to the NF Deployment lifecycle management operation. - -#### 4.4.2.5 Scale NF Deployment - -##### 4.4.2.5.1 Overview - -Clauses 3.2.2 and 3.2.3 of O-RAN.WG6.ORCH-USE-CASES [2] describe use cases about scaling out and scaling in of NF Deployment, respectively. According to the use cases, NF Deployments can be scaled out/in by adding/removing resources that conform the NF Deployment. In the use cases, scaling is performed based on a management request from the SMO, who sends a specific request to the DMS over the O2dms interface to scale the NF Deployment. - -As defined in ETSI GR NFV 003 [i.3]0, VNF scaling is the ability to dynamically extend/reduce resources of a VNF, and it can include scaling up/down and scaling out/in. In particular, the scaling out/in refers to the ability to scale by adding/removing - -resource instances to a VNF. For instance, in the case of a VM-based VNF, scaling out will add instances of VM to the VNF, while scaling in will remove VM instances to the VNF; and in the case of a container-based VNF, scaling out will add instances of one or a set of OS containers (aka Pod), while scaling in will remove instances of one or a set of OS containers. - -The scaling capabilities of a VNF are defined by the VNF provider through the VNF descriptors. The specific list of parameters to convey the trigger of what scaling aspect and levels can be performed are also defined through VNF descriptors (see generic information modelling in clause 7.1.5.4 and 7.1.5.5 of ETSI GS NFV-IFA 011 [12]). The scaling can also be handled in two forms: - -- Scale VNF: scaling a VNF by defining which aspects to scale and by which number of scaling steps to perform horizontal scaling (scale out/in), or by defining new values of resource capacity definitions to perform vertical scaling (scale up/down), and -- Scale VNF to Level: scaling a VNF to a specified scaling or VNF instantiation level. - -More information about the concepts of scaling a VNF instance is available in clause B.2 of ETSI GS NFV-SOL 003 [11]. - -The following clauses document the service operation of NF Deployment scaling considering the mappings of NF Deployment to VNF according to the present document. - -Scaling of an NF Deployment can be triggered in two ways: - -- Scaling based on a management request: in this case, the DMS receives and processes a management request sent by the API consumer (SMO). The corresponding procedure is further specified in clause 4.4.2.5.2. -- Auto-scaling: in this case, the DMS automatically invokes the scaling of the NF Deployment based on some criteria, such as changes in values of monitoring parameters (e.g., clause 7.1.11 of ETSI GS NFV-IFA 011 [12] specifies capabilities to define monitoring parameters and Indicators of a VNF) that can be monitored by the DMS on the NF Deployment. The corresponding procedure is further specified in clause 4.4.2.5.3. - -##### 4.4.2.5.2 Scaling based on management request - -To perform scaling of an NF Deployment based on an explicit management request using the present O2dms API profile, the following sub-procedures are applicable: - -- 1) scaling of the NF Deployment by triggering the operation "Scale VNF" performed via the corresponding task resource "Scale VNF task" or the operation "Scale VNF to Level" performed via the corresponding task resource "Scale VNF to Level task" on the "Individual VNF instance" resource following the flow illustrated in "Flow of VNF lifecycle management operations triggered by task resources" in clause 5.3.3 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure of VNF scaling is further profiled as illustrated in figure 4.4.2.5.2-1. - -NOTE 1: While the profiled ETSI GS NFV-SOL 003 [11] VNF scaling procedure contains steps related to VNF LCM granting exchanges between the VNFM and the NFVO of the NFV-MANO framework, the NF Deployment healing procedure specified in the present document version does not contain these steps. - -In addition, to monitor the status of the lifecycle operation in an asynchronous mode and be able to know the status of the operation (e.g., whether in progress or in some failed status), the API consumer shall request the creation of corresponding subscriptions to NF Deployment lifecycle management events following the flow "Flow of managing subscriptions" in clause 5.3.8 of ETSI GS NFV-SOL 003 [11]. The API consumer may also monitor the status of a lifecycle operation by query and reading information about the VNF LCM operation occurrence, which tracks the progress of the lifecycle operation. - -Figure 4.4.2.5.2-1 illustrates the procedure flow for the scaling of an NF Deployment including the sub-procedure introduced above. - -![Sequence diagram titled 'Scaling of NF Deployment' showing the interaction between SMO (NFO) and O-Cloud (DMS). The process involves sending a scaling request, receiving a 202 Accepted response, and then receiving notifications (STARTING, PROCESSING, COMPLETED) as the NF deployment is scaled. The diagram includes preconditions and postconditions.](fa01531ea2c45beeb4036005da3037a4_img.jpg) - -**Scaling of NF Deployment** - -Precondition: -"Individual VNF instance" resource representing the NF Deployment is in INSTANTIATED state - -**alt** [Scale NF Deployment] - -1 <> POST .../vnf\_instances/{vnfInstanceId}/scale (ScaleVnfRequest) - -**[Scale NF Deployment to Level]** - -2 <> POST .../vnf\_instances/{vnfInstanceId}/scale\_to\_level (ScaleVnfToLevelRequest) - -3 Create VNF LCM operation occurrence resource for the scaling - -4 <> 202 Accepted () - -5 <> Send VnfLcmOperationOccurrenceNotification(STARTING) - -6 Check granted resources, placement information and availability of deployment units - -7 <> Send VnfLcmOperationOccurrenceNotification(PROCESSING) - -8 NF Deployment scaling proceeds with termination and allocation of necessary O-Cloud resources - -**opt** - -9 <> GET .../vnf\_lcm\_op\_occs/{vnfLcmOpOccId} - -10 <> 200 OK (VnfLcmOpOcc:operationState=PROCESSING) - -11 NF Deployment healing is completed - -12 <> Send VnfLcmOperationOccurrenceNotification(COMPLETED) - -**opt** - -13 <> GET .../vnf\_lcm\_op\_occs/{vnfLcmOpOccId} - -14 <> 200 OK (VnfLcmOpOcc:operationState=COMPLETED) - -Postcondition: -NF Deployment is scaled and in INSTANTIATED state - -Sequence diagram titled 'Scaling of NF Deployment' showing the interaction between SMO (NFO) and O-Cloud (DMS). The process involves sending a scaling request, receiving a 202 Accepted response, and then receiving notifications (STARTING, PROCESSING, COMPLETED) as the NF deployment is scaled. The diagram includes preconditions and postconditions. - -**Figure 4.4.2.5.2-1: Flow of NF Deployment scaling based on management request** - -NOTE 2: Due to possible race conditions, the 202 response and the "STARTING" VnfLcmOperationOccurrenceNotification can arrive in any order at the SMO. - -The procedure of NF Deployment scaling based on management request consists of the following steps as illustrated in figure 4.4.2.5.2-1: - -NOTE 3: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** "Individual VNF instance" resource representing the NF Deployment is in INSTANTIATED state. - -- 1) The SMO sends a POST request to the "Scale VNF task" resource that represents the NF Deployment scaling lifecycle operation to be executed on the NF Deployment and includes in the message content a data structure of type "ScaleVnfRequest". -- 2) Alternatively, to step 1, the SMO sends a POST request to the "Scale VNF to Level task" resource that represents the NF Deployment scaling to level lifecycle operation to be executed on the NF Deployment and includes in the message content a data structure of type "ScaleVnfToLevelRequest". -- 3) The DMS creates a new "Individual VNF LCM operation occurrence" resources for the request, which represents the lifecycle operation occurrence about the NF Deployment scaling. -- 4) The DMS returns a "202 Accepted" response with an empty message content and a "Location" HTTP header that points to the new "Individual VNF LCM operation occurrence" resource. See note 2. -- 5) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate the start of the lifecycle management operation occurrence with the "STARTING" state if the SMO is subscribed to such type of notifications. See note 2. -- 6) The DMS checks the granted resources, placement information and availability of deployment items for the NF Deployment scaling. The DMS also checks the specific actions (e.g., terminate and create new deployment unit, restart a deployment unit, etc.) to be performed for the scaling based on the information contained in the descriptors of the NF Deployment. -- 7) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence enters the "PROCESSING" state if the SMO is subscribed to such type of notifications. -- 8) The DMS proceeds with the NF Deployment scaling with the allocation, termination, and restart of necessary O-Cloud resources. -- 9) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the ongoing lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 10) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". -- 11) The DMS completes the NF Deployment scaling. -- 12) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence is "COMPLETED" if the SMO is subscribed to such type of notifications. -- 13) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the completed lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 14) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". - -**Postcondition:** The NF Deployment is scaled and in "INSTANTIATED" state. - -**Error handling:** If the NF Deployment lifecycle operation fails, error information is provided in the notification messages that reports about the erroneous completion of the procedure. Error information is also available in the resource that represents the "Individual VNF lifecycle management operation occurrence" related to the NF Deployment lifecycle management operation. - -##### 4.4.2.5.3 Auto-scaling - -To perform the auto-scaling of an NF Deployment using the present O2dms API profile, the following sub-procedures are applicable: - -- 1) auto-scaling of the NF Deployment triggered by the DMS based on the detection of the scaling condition following the flow illustrated in "Flow of automatic invocation of VNF scaling and VNF healing" in clause 5.3.4 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure of VNF scaling is further profiled as illustrated in figure 4.4.2.5.3-1. - -NOTE 1: While the profiled ETSI GS NFV-SOL 003 [11] VNF auto-scaling procedure contains steps related to VNF LCM granting exchanges between the VNFM and the NFVO of the NFV-MANO framework, the NF Deployment scaling procedure specified in the present document version does not contain these steps. - -For the DMS to trigger the auto-scaling, two conditions shall be met: - -- The auto-scaling is enabled on the NF Deployment. This, in the ETSI GS NFV-SOL 003 based profile, is controlled via setting the corresponding attribute value of "isAutoscaleEnabled" in the "vnfConfigurableProperties" of the "VnfInstance" data type that represents the NF Deployment instance (see clause 5.2.6.2.2) and that the DMS manages. Changing the value of the attribute is made upon request by the API consumer (e.g., the SMO) by "patching" the corresponding "Individual VNF instance" resource of the NF Deployment. Patching an NF Deployment does not require re-instantiating the NF Deployment. - -NOTE 2: PATCHing of the "Individual VNF instance" resource, which represents the NF Deployment, to support modifying information of an NF Deployment is supported as indicated in clause 5.2.3. - -- The scaling condition is met, e.g., by monitoring performance metrics of virtualised resources/containerized workloads part of the NF Deployment, NF Deployment-specific indicators like "capacity usage" and/or performance data (via PM jobs or Thresholds) of the NF Deployment such as degradation of input/output packet transfer on connection points of the NF Deployment. The criterion for fulfilling the condition is NF Deployment-specific and implementation dependent and not specified in the present document. As a pre-condition, the DMS is expected to have the necessary information and/or policies to determine the fulfilment of the auto-scaling criterion, e.g., as contained in the NF Deployment descriptor when such descriptor is made available to the DMS. See also note 5. - -In addition, to monitor the status of the lifecycle operation in an asynchronous mode and be able to know the status of the operation (e.g., whether in progress or in some failed status), the API consumer shall request the creation of corresponding subscriptions to NF Deployment lifecycle management events following the flow "Flow of managing subscriptions" in clause 5.3.8 of ETSI GS NFV-SOL 003 [11]. The API consumer may also monitor the status of a lifecycle operation by query and reading information about the VNF LCM operation occurrence, which tracks the progress of the lifecycle operation. The API consumer can know that the operation has been triggered automatically as the attribute "isAutomaticInvocation" of the "VnfLcmOperationOccurrenceNotification" (see clause 5.2.5.2) and the "VnfLcmOpOcc" (see clause 5.2.6.2.3) is set to "true". - -NOTE 3: The referenced current version of the O-RAN.WG6.ORCH-USE-CASES [2] does not describe use cases about O-RAN NF auto-scaling. The present procedure flow might have to be updated in future versions of the present document in case additional or changed requirements are derived in case O-RAN NF auto-scaling use cases are described in future versions of the referenced document. - -Figure 4.4.2.5.3-1 illustrates the procedure flow for the auto-scaling of an NF Deployment including the sub-procedure introduced above. - -![Sequence diagram titled 'Auto-scaling of NF Deployment' showing the interaction between SMO (NFO) and O-Cloud (DMS).](318886a86a1dcc59e1fc83db6f157c60_img.jpg) - -**Auto-scaling of NF Deployment** - -**Precondition:** - "Individual VNF instance" resource representing the NF Deployment is in INSTANTIATED state - Auto-scaling is enabled on the "Individual VNF instance resource" - DMS has information/policies to determine a scaling condition and is monitoring the NF Deployment - -- DMS detects a scaling condition that triggers auto-scaling -- Create VNF LCM operation occurrence resource for the auto-scaling -- <> Send VnfLcmOperationOccurrenceNotification(STARTING) -- Check granted resources, placement information and availability of deployment units -- <> Send VnfLcmOperationOccurrenceNotification(PROCESSING) -- NF Deployment auto-scaling proceeds with termination, allocation of necessary O-Cloud resources -- opt** <> GET .../vnf\_lcm\_op\_occs/{vnfLcmOpOccId} -- <> 200 OK (VnfLcmOpOcc:operationState=PROCESSING) -- NF Deployment auto-scaling is completed -- <> Send VnfLcmOperationOccurrenceNotification(COMPLETED) -- opt** <> GET .../vnf\_lcm\_op\_occs/{vnfLcmOpOccId} -- <> 200 OK (VnfLcmOpOcc:operationState=COMPLETED) - -**Postcondition:** - NF Deployment is automatically scaled and in INSTANTIATED state - -Sequence diagram titled 'Auto-scaling of NF Deployment' showing the interaction between SMO (NFO) and O-Cloud (DMS). - -Figure 4.4.2.5.3-1: Flow of NF Deployment auto-scaling - -The procedure of NF Deployment auto-healing consists of the following steps as illustrated in figure 4.4.2.5.3-1: - -NOTE 4: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** "Individual VNF instance" resource representing the NF Deployment is in INSTANTIATED state, auto-healing is enabled on the "Individual VNF instance resource", and DMS has information/policies to determine a scaling condition and is monitoring the NF Deployment. - -NOTE 5: The provision of the information/policy criterion for the auto-scaling is not in scope of the present procedure flow. It is expected the SMO provides such criterion to the DMS. Clause 3.2.2.2 of O-RAN-WG6.ORCH-USE-CASES [2] indicates that SMO has policies (or configuration) related to NF capacity modification. - -- 1) The DMS detects a scaling condition that triggers the auto-scaling of the NF Deployment and selects the appropriate parameters for the operation to proceed based on the information contained in the descriptors of the NF Deployment or operational policies. -- 2) The DMS creates a new "Individual VNF LCM operation occurrence" resources for the operation, which represents the lifecycle operation occurrence about the NF Deployment auto-scaling. -- 3) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate the start of the lifecycle management operation occurrence with the "STARTING" state if the SMO is subscribed to such type of notifications. -- 4) The DMS checks the granted resources, placement information (see clause 4.5.2 and 5.2.6.5 which document related information) and availability of deployment items for the NF Deployment auto-scaling. The DMS also checks the specific actions (e.g., terminate and create new deployment unit, restart a deployment unit, etc.) to be performed for the auto-scaling based on the information contained in the descriptors of the NF Deployment. -- 5) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence enters the "PROCESSING" state if the SMO is subscribed to such type of notifications. -- 6) The DMS proceeds with the NF Deployment auto-scaling with the allocation, termination, and restart of necessary O-Cloud resources. -- 7) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the ongoing lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 8) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". -- 9) The DMS completes the NF Deployment auto-scaling. -- 10) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence is "COMPLETED" if the SMO is subscribed to such type of notifications. -- 11) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the completed lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 12) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". - -**Postcondition:** The NF Deployment is automatically scaled and in "INSTANTIATED" state. - -**Error handling:** If the NF Deployment lifecycle operation fails, error information is provided in the notification messages that reports about the erroneous completion of the procedure. Error information is also available in the resource that represents the "Individual VNF lifecycle management operation occurrence" related to the NF Deployment lifecycle management operation. - -#### 4.4.2.6 Change external connectivity of an NF Deployment - -With the change external connectivity operation, the following types of connectivity changes of an NF Deployment are supported: - -- Disconnect external CPs from the NF Deployment that are connected to a particular external VL and connect them to a different external VL. -- Disconnect external CP instances of an NF Deployment that represent supports in a trunk and delete them. The external CP that represents the "parent" port on the trunk cannot be neither deleted, nor disconnected, and it can only reconnect to a different external VL. -- Change the connectivity parameters of existing external CP, e.g., changing L3 addresses. -- Create new external CP that represent supports in a trunk and connect them to a particular external VL. The operation does not support creating the parent port of the trunk. - -To perform the change external connectivity of an NF Deployment using the present O2dms API profile, the following sub-procedures are applicable: - -- 1) changing external connectivity of the NF Deployment by triggering the operation "Change external VNF connectivity" performed via the corresponding task resource "Change external VNF connectivity task" on the "Individual VNF instance" resource following the flow illustrated in "Flow of VNF lifecycle management operations triggered by task resources" in clause 5.3.3 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure of VNF scaling is further profiled as illustrated in figure 4.4.2.6-1. - -NOTE 1: While the profiled ETSI GS NFV-SOL 003 [11] changing external VNF connectivity procedure contains steps related to VNF LCM granting exchanges between the VNFM and the NFVO of the NFV-MANO framework, the NF Deployment healing procedure specified in the present document version does not contain these steps. - -In addition, to monitor the status of the lifecycle operation in an asynchronous mode and be able to know the status of the operation (e.g., whether in progress or in some failed status), the API consumer shall request the creation of corresponding subscriptions to NF Deployment lifecycle management events following the flow "Flow of managing subscriptions" in clause 5.3.8 of ETSI GS NFV-SOL 003 [11]. The API consumer may also monitor the status of a lifecycle operation by query and reading information about the VNF LCM operation occurrence, which tracks the progress of the lifecycle operation. - -Figure 4.4.2.6-1 illustrates the procedure flow for the changing external connectivity of an NF Deployment including the sub-procedure introduced above. - -![Sequence diagram titled 'Changing external connectivity of NF Deployment' showing interactions between SMO (NFO) and O-Cloud (DMS).](1142ba0197b158bb198186fe8baccc32_img.jpg) - -The diagram illustrates the sequence of operations for changing the external connectivity of an NF Deployment. It features two lifelines: SMO (containing NFO) and O-Cloud (containing DMS). - -**Sequence of Messages:** - -- The SMO sends a `POST .../vnf_instances/{vnfInstanceId}/change_ext_conn (ChangeExtVnfConnectivityRequest)` to the O-Cloud. -- The O-Cloud responds with `202 Accepted ()`. -- The O-Cloud then sends a `Send VnfLcmOperationOccurrenceNotification(STARTING)` to the SMO. -- Internal O-Cloud steps: "Create VNF LCM operation occurrence resource for the change of external connectivity" and "Check granted resources, placement information and availability of deployment units". -- The O-Cloud sends a `Send VnfLcmOperationOccurrenceNotification(PROCESSING)` to the SMO. -- Internal O-Cloud step: "Changing of NF Deployment external connectivity proceeds with allocation, modification, and/or termination of necessary O-Cloud resources". -- An optional block labeled "opt" contains: - - The SMO sends a `GET .../vnf_lcm_op_occs/{vnfLcmOpOccId}` to the O-Cloud. - - The O-Cloud responds with `200 OK (VnfLcmOpOcc:operationState=PROCESSING)`. -- Internal O-Cloud step: "Changing external connectivity of NF Deployment is completed". -- The O-Cloud sends a `Send VnfLcmOperationOccurrenceNotification(COMPLETED)` to the SMO. -- Another optional block labeled "opt" contains: - - The SMO sends a `GET .../vnf_lcm_op_occs/{vnfLcmOpOccId}` to the O-Cloud. - - The O-Cloud responds with `200 OK (VnfLcmOpOcc:operationState=COMPLETED)`. - -**Precondition:** "Individual VNF instance" resource representing the NF Deployment is in INSTANTIATED state - -**Postcondition:** NF Deployment external connectivity has been changed and in INSTANTIATED state - -Sequence diagram titled 'Changing external connectivity of NF Deployment' showing interactions between SMO (NFO) and O-Cloud (DMS). - -Figure 4.4.2.6-1: Flow of changing external connectivity of NF Deployment - -NOTE 2: Due to possible race conditions, the 202 response and the "STARTING" VnfLcmOperationOccurrenceNotification can arrive in any order at the SMO. - -The procedure of changing external connectivity of NF Deployment consists of the following steps as illustrated in figure 4.4.2.6-1: - -NOTE 3: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** "Individual VNF instance" resource representing the NF Deployment is in INSTANTIATED state. - -- 1) The SMO sends a POST request to the "Change external VNF connectivity task" resource that represents the changing external NF Deployment connectivity lifecycle operation to be executed on the NF Deployment and includes in the message content a data structure of type "ChangeExtVnfConnectivityRequest". - -- 2) The DMS creates a new "Individual VNF LCM operation occurrence" resources for the request, which represents the lifecycle operation occurrence about the change of external connectivity of the NF Deployment. -- 3) The DMS returns a "202 Accepted" response with an empty message content and a "Location" HTTP header that points to the new "Individual VNF LCM operation occurrence" resource. See note 2. -- 4) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate the start of the lifecycle management operation occurrence with the "STARTING" state if the SMO is subscribed to such type of notifications. See note 2. -- 5) The DMS checks the granted resources, placement information and availability of deployment items for the change of external NF Deployment connectivity. The DMS also checks the specific actions (e.g., allocate, modify, or terminate existing O-Cloud resources) to be performed for the changing of external connectivity based on the information contained in the descriptors of the NF Deployment and the current runtime information held about the NF Deployment. -- 6) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence enters the "PROCESSING" state if the SMO is subscribed to such type of notifications. -- 7) The DMS proceeds with the change of external NF Deployment connectivity with the allocation, modification and/or termination of necessary O-Cloud resources. -- 8) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the ongoing lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 9) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". -- 10) The DMS completes the change of external NF Deployment connectivity. -- 11) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence is "COMPLETED" if the SMO is subscribed to such type of notifications. -- 12) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the completed lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 13) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". - -**Postcondition:** The NF Deployment external connectivity has been changed and is in "INSTANTIATED" state. - -**Error handling:** If the NF Deployment lifecycle operation fails, error information is provided in the notification messages that reports about the erroneous completion of the procedure. Error information is also available in the resource that represents the "Individual VNF lifecycle management operation occurrence" related to the NF Deployment lifecycle management operation. - -#### 4.4.2.7 Change current NF Deployment package - -Clause 3.2.4 of O-RAN.WG6.ORCH-USE-CASES [2] describes the use case of "Software upgrade of NF", which includes steps of deploying NF with new software and terminating the previously deployed NF in a build-and-replace software upgrade approach. Other possible approaches are mentioned as well, such as "break-fix" or "in-place upgrade". Related requirements are specified in clauses 4.1 and 4.3 of O-RAN.WG6.ORCH-USE-CASES [2]. In the general capabilities of O-Cloud Deployment Lifecycle Management listed in clause 3.7.2 of O-RAN.WG6.TS.O2-GA&P [4], a reference is also made to the capability of O-Cloud supporting upgrading of any or all components of an O-RAN Cloudified NF instance. - -The functionality of software modification of a VNF are covered in the ETSI NFV framework by a specified VNF lifecycle management operation named "Change current VNF package". This operation provides "in-place upgrade" capabilities, i.e., a VNF's software can be modified without need to perform a fresh new deployment. In the case of ETSI NFV framework, a "build-and-replace" approach is covered by reusing the VNF lifecycle management operations of "VNF instantiation" and - -"VNF termination". Both operations are profiled in the present document in the context of managing the lifecycle of NF Deployments, refer to clauses 4.4.2.1 and 4.4.2.2, respectively. - -NOTE 1: In the case of "build-and-replace", it is assumed that the SMO is in control of when the "old" NF Deployment instance can be terminated, e.g., by monitoring data collected via the O1. - -NOTE 2: "Current NF Deployment package" means the NF Deployment (software) package from which a given NF Deployment instance is based on at a specific point in time. For instance, at a given point in time NF Deployment instance #A1 is deployed and runs based on the content from NF Deployment package #A.v1. By changing the "current NF Deployment package", the lifecycle process changes the NF Deployment instance to run based on the content from another NF Deployment package. Following with the example, for instance, the NF Deployment instance #A1 is updated to run based on the content of NF Deployment package #A.v2. - -With the change of current package of an NF Deployment, the following types of changes/modifications on an NF Deployment are supported: - -- Changes of the NF Deployment virtualised resources and/or containerized workloads, such as their requirements in terms of infrastructure resources or the composition of sets of resources, but without changing the software version of the NF Deployment. -- Changes both, of the software version of the NF Deployment and the virtualised resources and/or containerized workloads. In this case, the software is changed by means of performing tasks and management on the sets of virtualised resources and/or containerized workloads. For instance, a virtualised resource running a current software version can be terminated and a new virtualised resource be instantiated running a different software version. -- Changes related to the NF Deployment descriptor. This supports the correction of bugs in the descriptors, changes in naming schemes used in the descriptors, etc. - -During the procedure of changing the current NF Deployment package, the DMS can add temporary virtualised resources and/or containerized workloads. And as indicated above, during such procedure adding and removal of virtualised resources and/or containerized workloads can also be performed as needed by the process. - -To perform the change of current NF Deployment package using the present O2dms API profile, the following sub-procedures are applicable: - -- 1) changing the current NF Deployment package by triggering the operation "Change current VNF package" performed via the corresponding task resource "Change current VNF package task" on the "Individual VNF instance" resource following the flow illustrated in "Flow of VNF lifecycle management operations triggered by task resources" in clause 5.3.3 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure of change current VNF package is further profiled as illustrated in figure 4.4.2.7-1. - -NOTE 3: While the profiled ETSI GS NFV-SOL 003 [11] changing current VNF package procedure contains steps related to VNF LCM granting exchanges between the VNFM and the NFVO of the NFV-MANO framework, the change current NF Deployment package procedure specified in the present document version does not contain these steps. - -In addition, to monitor the status of the lifecycle operation in an asynchronous mode and be able to know the status of the operation (e.g., whether in progress or in some failed status), the API consumer shall request the creation of corresponding subscriptions to NF Deployment lifecycle management events following the flow "Flow of managing subscriptions" in clause 5.3.8 of ETSI GS NFV-SOL 003 [11]. The API consumer may also monitor the status of a lifecycle operation by query and reading information about the VNF LCM operation occurrence, which tracks the progress of the lifecycle operation. - -Figure 4.4.2.7-1 illustrates the procedure flow for the changing current NF Deployment package including the sub-procedure introduced above. - -![Sequence diagram titled 'Changing current NF Deployment package' showing the interaction between SMO (NFO) and O-Cloud (DMS).](47a7beddcb8a1b7abdca746967e32bb4_img.jpg) - -The diagram illustrates the sequence of operations for changing the current NF Deployment package. It begins with a precondition: "Individual VNF instance" resource representing the NF Deployment is in INSTANTIATED state. The sequence of steps is as follows: - -- The SMO (NFO) sends a POST request to the O-Cloud (DMS) to change the VNF package: `<> POST .../vnf_instances/{vnfInstanceId}/change_vnfpkg (ChangeCurrentVnfPkgRequest)`. -- The O-Cloud (DMS) creates a VNF LCM operation occurrence resource for the change of external connectivity. -- The O-Cloud (DMS) responds with a 202 Accepted status: `<> 202 Accepted ()`. -- The O-Cloud (DMS) sends a notification indicating the operation is starting: `<> Send VnfLcmOperationOccurrenceNotification(STARTING)`. -- The O-Cloud (DMS) checks granted resources, placement information, and availability of deployment units. -- The O-Cloud (DMS) sends a notification indicating the operation is processing: `<> Send VnfLcmOperationOccurrenceNotification(PROCESSING)`. -- The O-Cloud (DMS) proceeds with the allocation, modification, and/or termination of necessary O-Cloud resources. -- An optional block contains a GET request from the SMO (NFO) to check the operation state: `<> GET .../vnf_lcm_op_occ/{vnfLcmOpOccId}`. -- The O-Cloud (DMS) responds with a 200 OK status and operation state PROCESSING: `<> 200 OK (VnfLcmOpOcc:operationState=PROCESSING)`. -- The O-Cloud (DMS) completes the changing of current NF Deployment package. -- The O-Cloud (DMS) sends a notification indicating the operation is completed: `<> Send VnfLcmOperationOccurrenceNotification(COMPLETED)`. -- Another optional block contains a GET request from the SMO (NFO) to check the operation state: `<> GET .../vnf_lcm_op_occ/{vnfLcmOpOccId}`. -- The O-Cloud (DMS) responds with a 200 OK status and operation state COMPLETED: `<> 200 OK (VnfLcmOpOcc:operationState=COMPLETED)`. - -The postcondition is: Current NF Deployment package has been changed and NF Deployment is in INSTANTIATED state. - -Sequence diagram titled 'Changing current NF Deployment package' showing the interaction between SMO (NFO) and O-Cloud (DMS). - -Figure 4.4.2.7-1: Flow of changing current NF Deployment package - -NOTE 4: Due to possible race conditions, the 202 response and the "STARTING" VnfLcmOperationOccurrenceNotification can arrive in any order at the SMO. - -The procedure of changing current NF Deployment package consists of the following steps as illustrated in figure 4.4.2.7-1: - -NOTE 5: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** "Individual VNF instance" resource representing the NF Deployment is in INSTANTIATED state. - -- 1) The SMO sends a POST request to the "Change current VNF package task" resource that represents the changing current NF Deployment package lifecycle operation to be executed on the NF Deployment and includes in the message content a data structure of type "ChangeCurrentVnfPkgRequest". - -- 2) The DMS creates a new "Individual VNF LCM operation occurrence" resources for the request, which represents the lifecycle operation occurrence about the changing the current NF Deployment package. -- 3) The DMS returns a "202 Accepted" response with an empty message content and a "Location" HTTP header that points to the new "Individual VNF LCM operation occurrence" resource. See note 4. -- 4) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate the start of the lifecycle management operation occurrence with the "STARTING" state if the SMO is subscribed to such type of notifications. See note 4. -- 5) The DMS checks the granted resources, placement information and availability of deployment items for the change of current NF Deployment package. The DMS also checks the specific actions (e.g., allocate, modify, or terminate existing O-Cloud resources) to be performed for the change of current NF Deployment package based on the information contained in the descriptors of the NF Deployment and the current runtime information held about the NF Deployment. -- 6) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence enters the "PROCESSING" state if the SMO is subscribed to such type of notifications. -- 7) The DMS proceeds with the change of current NF Deployment package with the allocation, modification and/or termination of necessary O-Cloud resources. -- 8) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the ongoing lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 9) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". -- 10) The DMS completes the change of current NF Deployment package. -- 11) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence is "COMPLETED" if the SMO is subscribed to such type of notifications. -- 12) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the completed lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 13) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". - -**Postcondition:** The current NF Deployment package has been changed and the NF Deployment is in "INSTANTIATED" state. - -**Error handling:** If the NF Deployment lifecycle operation fails, error information is provided in the notification messages that reports about the erroneous completion of the procedure. Error information is also available in the resource that represents the "Individual VNF lifecycle management operation occurrence" related to the NF Deployment lifecycle management operation. - -#### 4.4.2.8 Change NF Deployment flavour - -An NF Deployment may have one or more NF Deployment flavours. An NF Deployment flavour is a deployment configuration that describes a specific deployment of an NF Deployment supporting specific KPIs, such as capacity and performance, or capabilities, such as specific NF Services. - -NOTE 1: No reference to a specific use case from the O-RAN.WG6.ORCH-USE-CASES [2]. - -The functionality of changing the flavour of an NF Deployment is specified in the VNF lifecycle management as a dedicated operation named "Change VNF flavour". - -During the procedure of changing the NF Deployment flavour, the DMS can add temporary virtualised resources and/or containerized workloads. And as indicated above, during such procedure adding and removal of virtualised resources and/or containerized workloads can also be performed as needed by the process and the requested new deployment configuration. - -To perform the change NF Deployment flavour using the present O2dms API profile, the following sub-procedures are applicable: - -- 1) changing the NF Deployment flavour by triggering the operation "Change VNF flavour" performed via the corresponding task resource "Change VNF Flavour task" on the "Individual VNF instance" resource following the flow illustrated in "Flow of VNF lifecycle management operations triggered by task resources" in clause 5.3.3 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure of change VNF flavour is further profiled as illustrated in figure 4.4.2.8-1. - -NOTE 2: While the profiled ETSI GS NFV-SOL 003 [11] changing VNF flavour procedure contains steps related to VNF LCM granting exchanges between the VNFM and the NFVO of the NFV-MANO framework, the change NF Deployment flavour procedure specified in the present document version does not contain these steps. - -In addition, to monitor the status of the lifecycle operation in an asynchronous mode and be able to know the status of the operation (e.g., whether in progress or in some failed status), the API consumer shall request the creation of corresponding subscriptions to NF Deployment lifecycle management events following the flow "Flow of managing subscriptions" in clause 5.3.8 of ETSI GS NFV-SOL 003 [11]. The API consumer may also monitor the status of a lifecycle operation by query and reading information about the VNF LCM operation occurrence, which tracks the progress of the lifecycle operation. - -Figure 4.4.2.8-1 illustrates the procedure flow for the changing current NF Deployment package including the sub-procedure introduced above. - -![Sequence diagram titled 'Changing NF Deployment flavour' showing the interaction between SMO (NFO) and O-Cloud (DMS). The process involves sending a change_flavour request, receiving a 202 Accepted response, and then checking the operation status until it is COMPLETED. The diagram includes preconditions and postconditions related to the VNF instance state.](1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg) - -**Changing NF Deployment flavour** - -**Precondition:** -"Individual VNF instance" resource representing the NF Deployment is in INSTANTIATED state - -- 1 <> POST .../vnf\_instances/{vnfInstanceId}/change\_flavour (ChangeVnfFlavourRequest) -- 2 Create VNF LCM operation occurrence resource for the change of VNF flavour -- 3 <> 202 Accepted () -- 4 <> Send VnfLcmOperationOccurrenceNotification(STARTING) -- 5 Check granted resources, placement information and availability of deployment units -- 6 <> Send VnfLcmOperationOccurrenceNotification(PROCESSING) -- 7 Changing of NF Deployment flavour proceeds with allocation, modification, and/or termination of necessary O-Cloud resources -- 8 <> GET .../vnf\_lcm\_op\_occs/{vnfLcmOpOccId} -- 9 <> 200 OK (VnfLcmOpOcc:operationState=PROCESSING) -- 10 Changing of NF Deployment flavour is completed -- 11 <> Send VnfLcmOperationOccurrenceNotification(COMPLETED) -- 12 <> GET .../vnf\_lcm\_op\_occs/{vnfLcmOpOccId} -- 13 <> 200 OK (VnfLcmOpOcc:operationState=COMPLETED) - -**Postcondition:** -NF Deployment flavour has been changed and NF Deployment is in INSTANTIATED state - -Sequence diagram titled 'Changing NF Deployment flavour' showing the interaction between SMO (NFO) and O-Cloud (DMS). The process involves sending a change\_flavour request, receiving a 202 Accepted response, and then checking the operation status until it is COMPLETED. The diagram includes preconditions and postconditions related to the VNF instance state. - -Figure 4.4.2.8-1: Flow of changing current NF Deployment package - -NOTE 3: Due to possible race conditions, the 202 response and the "STARTING" VnfLcmOperationOccurrenceNotification can arrive in any order at the SMO. - -The procedure of changing NF Deployment flavour consists of the following steps as illustrated in figure 4.4.2.8-1: - -NOTE 4: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** "Individual VNF instance" resource representing the NF Deployment is in INSTANTIATED state. - -- 1) The SMO sends a POST request to the "Change VNF flavour task" resource that represents the changing NF Deployment flavour lifecycle operation to be executed on the NF Deployment and includes in the message content a data structure of type "ChangeVnfFlavourRequest". -- 2) The DMS creates a new "Individual VNF LCM operation occurrence" resources for the request, which represents the lifecycle operation occurrence about the changing of NF Deployment flavour. -- 3) The DMS returns a "202 Accepted" response with an empty message content and a "Location" HTTP header that points to the new "Individual VNF LCM operation occurrence" resource. See note 3. -- 4) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate the start of the lifecycle management operation occurrence with the "STARTING" state if the SMO is subscribed to such type of notifications. See note 3. -- 5) The DMS checks the granted resources, placement information and availability of deployment items for the change of NF Deployment flavour. The DMS also checks the specific actions (e.g., allocate, modify, or terminate existing O-Cloud resources) to be performed for the change of NF Deployment flavour based on the information contained in the descriptors of the NF Deployment and the current runtime information held about the NF Deployment. -- 6) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence enters the "PROCESSING" state if the SMO is subscribed to such type of notifications. -- 7) The DMS proceeds with the change of NF Deployment flavour with the allocation, modification and/or termination of necessary O-Cloud resources. -- 8) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the ongoing lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 9) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". -- 10) The DMS completes the change of NF Deployment flavour. -- 11) The DMS sends to the SMO a VNF lifecycle management operation occurrence notification to indicate that the lifecycle management operation occurrence is "COMPLETED" if the SMO is subscribed to such type of notifications. -- 12) If desired, the SMO can poll the "Individual VNF LCM operation occurrence" resource to obtain information about the completed lifecycle operation by sending to the DMS a GET request to the "Individual VNF LCM operation occurrence" resource. -- 13) The DMS returns to the SMO the information about the operation by providing in the message content a data structure of type "VnfLcmOpOcc". - -**Postcondition:** The NF Deployment flavour has been changed and the NF Deployment is in "INSTANTIATED" state. - -**Error handling:** If the NF Deployment lifecycle operation fails, error information is provided in the notification messages that reports about the erroneous completion of the procedure. Error information is also available in the resource that represents the "Individual VNF lifecycle management operation occurrence" related to the NF Deployment lifecycle management operation. - -### 4.4.3 NF Deployment fault management - -#### 4.4.3.1 Get alarm list - -The functionality of getting the list of alarms of a VNF is covered in the ETSI NFV framework by the specific VNF fault management operation named "Get Alarm List". The operation comprises both sub-cases: - -- Get information about multiple alarms, and -- Get information about a specific alarm. - -To perform the get alarm list associated to an NF Deployment using the present O2dms API profile, the following sub-procedures are applicable: - -- 1) Get information of multiple alarms by triggering the operation "Get Alarm List" on the "Alarms" resource following the alternative #1 in the flow illustrated in "Flow of the Get Alarm List operation" in clause 7.3.1 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure is further profiled as illustrated in figure 4.4.3.1-1. -- 2) Query/read information of a specific alarm by triggering the operation "Get Alarm List" on an "Individual alarm" resource, following the alternative #2 in the flow illustrated in "Flow of the Get Alarm List operation" in clause 7.3.1 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure is further profiled as illustrated in figure 4.4.3.1-1. - -Figure 4.4.3.1-1 illustrates the procedure flow for get alarm list of an NF Deployment including the sub-procedure introduced above. - -![Sequence diagram titled 'Flow of get alarm list of NF Deployment' showing interactions between SMO (NFO) and O-Cloud (DMS). The diagram includes a precondition 'None specified' and an alt block 'Query information about multiple alarms' with two alternatives: 1) GET ../alarms and 2) GET ../alarms/{alarmId}. The postcondition is 'SMO has the queried/read information about the one or more alarms associated to the NF Deployment'.](0c80c383f76034e117adf5e5eaadaaf3_img.jpg) - -``` - -sequenceDiagram - participant SMO as SMO (NFO) - participant OCloud as O-Cloud (DMS) - Note right of SMO: Precondition: -None specified - - alt Query information about multiple alarms: Alternative 1 - SMO->>OCloud: 1 <> GET ../alarms - OCloud-->>SMO: 2 <> 200 OK (Alarm[]) - else Read information about an individual alarm: Alternative 2 - SMO->>OCloud: 3 <> GET ../alarms/{alarmId} - OCloud-->>SMO: 4 <> 200 OK (Alarm) - end - - Note right of SMO: Postcondition: -SMO has the queried/read information about the one or more alarms associated to the NF Deployment - -``` - -Sequence diagram titled 'Flow of get alarm list of NF Deployment' showing interactions between SMO (NFO) and O-Cloud (DMS). The diagram includes a precondition 'None specified' and an alt block 'Query information about multiple alarms' with two alternatives: 1) GET ../alarms and 2) GET ../alarms/{alarmId}. The postcondition is 'SMO has the queried/read information about the one or more alarms associated to the NF Deployment'. - -Figure 4.4.3.1-1: Flow of get alarm list of NF Deployment - -The procedure of getting the alarm list of NF Deployment consists of the following steps as illustrated in figure 4.4.3.1-1: - -NOTE: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** None specified. - -- 1) If the SMO intends to query multiple alarms, it sends a GET request to the "Alarms" resource. -- 2) The DMS returns a "200 OK" response to the SMO and includes zero or more data structures of type "Alarm" in the message content, according to query request. -- 3) If the SMO intends to read the information of a particular alarm, it sends a GET request to the "Individual alarm" resource, by addressing to the appropriate alarm identifier in the resource URI. -- 4) The DMS returns a "200 OK" response and includes a data structure of type "Alarm" in the message content, according to the query request. - -**Postcondition:** The SMO has the queried/read information about the one or more alarms associated to the NF Deployment. - -**Error handling:** In case of failure, appropriate error information is provided in the response. - -#### 4.4.3.2 Notify - -Raising and alarm and sending it to a consumer of fault management of a VNF is covered in the ETSI NFV framework by the specific VNF fault management operation named "Notify". Therefore, alarms are raised and sent by means of notifications. Other kinds of notifications can also be provided related to fault management procedures. - -To perform the issuing of fault management notifications associated to an NF Deployment using the present O2dms API profile, the following procedure is applicable: - -- 1) Send a notification following the flow illustrated in "Flow of sending notifications" in clause 7.3.4 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the procedure is further profiled as illustrated in figure 4.4.3.2-1. - -In addition, to monitor the raised events in an asynchronous mode and be able to receive the corresponding notifications, the API consumer shall request the creation of corresponding subscriptions to NF Deployment fault management events following the flow of "Flow of managing subscriptions" in clause 7.3.3 of ETSI GS NFV-SOL 003 [11]. The API consumer may also monitor the status of active alarms by querying and reading information about them, as described in clause 4.4.3.1. - -Figure 4.4.3.2-1 illustrates the procedure flow for sending alarm notification associated to an NF Deployment. - -![Sequence diagram titled 'Sending notifications' showing the flow between SMO (NFO) and O-Cloud (DMS). The process starts with a precondition 'SMO has subscribed to notifications previously'. Step 1: An event occurs in the DMS that matches a subscription. Step 2: The DMS sends a POST request to the SMO's callback URI with a notification. Step 3: The SMO responds with a 204 No Content. The process ends with a postcondition 'SMO has received the notification'.](080a7af02bc47cf21ebfae4e0be39745_img.jpg) - -``` - -sequenceDiagram - participant SMO as SMO (NFO) - participant O-Cloud as O-Cloud (DMS) - Note left of SMO: Precondition: -SMO has subscribed to notifications previously - Note right of O-Cloud: 1 Event occurs that matches subscription - O-Cloud->>SMO: 2 <> POST <> (<>) - SMO-->>O-Cloud: 3 204 No Content - Note right of O-Cloud: Postcondition: -SMO has received the notification - -``` - -Sequence diagram titled 'Sending notifications' showing the flow between SMO (NFO) and O-Cloud (DMS). The process starts with a precondition 'SMO has subscribed to notifications previously'. Step 1: An event occurs in the DMS that matches a subscription. Step 2: The DMS sends a POST request to the SMO's callback URI with a notification. Step 3: The SMO responds with a 204 No Content. The process ends with a postcondition 'SMO has received the notification'. - -**Figure 4.4.3.2-1: Flow of fault management notifications associated to an NF Deployment** - -The procedure of notifying an alarm associated to an NF Deployment consists of the following steps as illustrated in figure 4.4.3.2-1: - -NOTE: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** The SMO has subscribed to notifications previously. - -- 1) An event occurs in the DMS that matches a subscription for notifications. - -- 2) The DMS generates and sends a notification that includes information about the event and sends it in the body of a POST request to the URI which the SMO has registered as part of the subscription request. The variable <> in the flow is a placeholder for the different types of notifications that can be sent via this service, including alarm notifications. -- 3) The SMO acknowledges the successful delivery of the notification by returning to the DMS a "204 No Content" response. - -**Postcondition:** The SMO has received the notification. - -**Error handling:** If the DMS does not receive the "204 No Content" response from the SMO, it can retry sending the same notification. - -#### 4.4.3.3 Acknowledge alarm - -The functionality of acknowledging an individual alarm of a VNF is covered in the ETSI NFV framework by the specific VNF fault management operation named "Acknowledge Alarm". - -To perform the acknowledgement of an alarm associated to an NF Deployment using the present O2dms API profile, the following procedure is applicable: - -- 1) Acknowledge alarm by triggering the operation "Acknowledge Alarm " on an "Individual alarm" resource following the flow illustrated in "Flow of acknowledging alarm " in clause 7.3.3 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the procedure is further profiled as illustrated in figure 4.4.3.3-1. - -Figure 4.4.3.3-1 illustrates the procedure flow for acknowledging an alarm of an NF Deployment including the procedure introduced above. - -![Sequence diagram titled 'Acknowledge alarm' showing the interaction between SMO (NFO) and O-Cloud (DMS). The process starts with a precondition 'The individual alarm has been created'. Step 1 shows a PATCH request from NFO to DMS: '<> PATCH .../alarms/{alarmId} (AlarmModifications)'. Step 2 shows a 200 OK response from DMS to NFO: '<> 200 OK (AlarmModifications)'. The process ends with a postcondition 'The individual alarm has been acknowledged'.](30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg) - -``` - -sequenceDiagram - participant SMO as SMO (NFO) - participant O-Cloud as O-Cloud (DMS) - Note right of SMO: Precondition: -The individual alarm has been created - SMO->>O-Cloud: 1 <> PATCH .../alarms/{alarmId} (AlarmModifications) - O-Cloud-->>SMO: 2 <> 200 OK (AlarmModifications) - Note right of SMO: Postcondition: -The individual alarm has been acknowledged - -``` - -Sequence diagram titled 'Acknowledge alarm' showing the interaction between SMO (NFO) and O-Cloud (DMS). The process starts with a precondition 'The individual alarm has been created'. Step 1 shows a PATCH request from NFO to DMS: '<> PATCH .../alarms/{alarmId} (AlarmModifications)'. Step 2 shows a 200 OK response from DMS to NFO: '<> 200 OK (AlarmModifications)'. The process ends with a postcondition 'The individual alarm has been acknowledged'. - -**Figure 4.4.3.3-1: Flow of acknowledging alarm of NF Deployment** - -The procedure of acknowledging an alarm associated to an NF Deployment consists of the following steps as illustrated in figure 4.4.3.3-1: - -NOTE: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** The individual alarm has been created. - -- 1) The SMO sends a PATCH request to the individual alarm, by addressing to the appropriate alarm identifier in the resource URI with a message content including a data structure of "AlarmModifications" which includes the requested modification to acknowledge the alarm's acknowledgment status. - -- 2) The DMS returns a "200 OK" response to the SMO and includes a data structure of type "AlarmModifications" in the message content. - -**Postcondition:** The individual alarm has been acknowledged. - -**Error handling:** In case of failure, appropriate error information is provided in the response. - -### 4.4.4 NF Deployment performance management - -#### 4.4.4.1 Create PM job - -The functionality of creating a PM job to collect performance information associated to a VNF is covered in the ETSI NFV framework by the specific VNF performance management operation named "Create PM Job". - -To create a PM job associated to an NF Deployment using the present O2dms API profile, the following procedure is applicable: - -- 1) Create a PM Job by triggering the operation "Create PM Job" on the "PM Jobs" resource following the flow illustrated in "Flow of creating a PM job" in clause 6.3.1 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the procedure is further profiled as illustrated in figure 4.4.4.1-1. - -Figure 4.4.4.1-1 illustrates the procedure flow for creating a PM job associated to an NF Deployment. - -![Sequence diagram showing the flow of creating a PM job. Lifelines: SMO (NFO) and O-Cloud (DMS). The process involves sending a POST request for a PM job, testing the notification endpoint with a GET request, receiving a 204 response, creating the resource, and finally receiving a 201 Created response. Preconditions and postconditions are noted.](659a041a7997f9eea79f4e2f3ba265a5_img.jpg) - -``` - -sequenceDiagram - participant SMO as SMO (NFO) - participant O-Cloud as O-Cloud (DMS) - Note over SMO, O-Cloud: Create a PM job associated to an NF Deployment - Note right of SMO: Precondition: None specified - SMO->>O-Cloud: 1 <> POST .../pm_jobs (CreatePmJobRequest) - Note over SMO, O-Cloud: Testing the notification endpoint - O-Cloud->>SMO: 2 <> GET <> - SMO->>O-Cloud: 3 <> 204 No Content - Note right of O-Cloud: 4 Creates the PM job resource - O-Cloud->>SMO: 5 <> 201 Created (PmJob) - Note right of SMO: Postcondition: PM job has been created and associated to the NF Deployment - -``` - -Sequence diagram showing the flow of creating a PM job. Lifelines: SMO (NFO) and O-Cloud (DMS). The process involves sending a POST request for a PM job, testing the notification endpoint with a GET request, receiving a 204 response, creating the resource, and finally receiving a 201 Created response. Preconditions and postconditions are noted. - -**Figure 4.4.4.1-1: Flow of creating a PM job associated to an NF Deployment** - -The procedure of creating a PM job associated to an NF Deployment consists of the following steps as illustrated in figure 4.4.4.1-1: - -NOTE: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** None specified. - -- 1) If the SMO intends to create a PM job, it sends a POST request to the "PM Jobs" resource, including one data structure of type "CreatePmJobRequest" in the message content. The request includes information about the notification endpoint to be registered and to which notifications related to events about performance monitoring based on the PM job are expected to be sent. -- 2) To test the notification endpoint that has been registered, the DMS sends a GET request to the notification endpoint URI. -- 3) The SMO returns a "204 No Content" response to indicate success in testing the notification endpoint. -- 4) The DMS proceeds with the creation of the individual PM job resource and its instance (i.e., actual application instance or configuration that implements the PM job process). -- 5) The DMS returns a "201 Created" response to the SMO and includes in the message content a representation of the PM job that has been created. - -**Postcondition:** The PM job has been created and associated to the NF Deployment. - -**Error handling:** In case of failure, appropriate error information is provided in the response. - -#### 4.4.4.2 Query/read PM job information - -The functionality of querying/reading information of one or more PM jobs associated to a VNF is covered in the ETSI NFV framework by the specific VNF performance management operation named "Query PM Job". The operation comprises two sub-cases: - -- Get information about multiple PM jobs, and -- Get information about a specific PM job. - -To query information about one or more PM jobs associated to an NF Deployment using the present O2dms API profile, the following sub-procedures are applicable: - -- 1) Get information of multiple PM jobs by triggering the operation "Get PM Job" on the "PM Jobs" resource following the alternative #1 in the flow illustrated in "Flow of querying/reading PM jobs" in clause 6.3.2 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure is further profiled as illustrated in figure 4.4.4.2-1. -- 2) Query/read information of a specific PM job by triggering the operation "Get PM Job" on an "Individual PM Job" resource, following the alternative #2 in the flow illustrated in "Flow of querying/reading PM jobs" in clause 6.3.2 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure is further profiled as illustrated in figure 4.4.4.2-1. - -Figure 4.4.4.2-1 illustrates the procedure flow for querying/reading PM jobs associated to an NF Deployment, including the sub-procedures introduced above. - -![Sequence diagram showing the flow of query/reading information of PM jobs. Lifelines: SMO (NFO) and O-Cloud (DMS). The process involves a precondition (PM jobs created), an 'alt' block for 'Query information about multiple PM jobs' (steps 1-2) and 'Read information about an individual PM job' (steps 3-4), and a postcondition (SMO has the queried information).](01e00200a536673d6cd0e6d8705047a0_img.jpg) - -``` - -sequenceDiagram - participant SMO as SMO (NFO) - participant OCloud as O-Cloud (DMS) - Note right of SMO: Precondition: -PM jobs have been created - Note over SMO,OCloud: Query/read PM job information - alt Query information about multiple PM jobs - SMO->>OCloud: 1 <> GET .../pm_jobs - OCloud-->>SMO: 2 <> 200 OK (PmJob[]) - else Read information about an individual PM job - SMO->>OCloud: 3 <> GET .../pm_jobs/{pmJobId} - OCloud-->>SMO: 4 <> 200 OK (PmJob) - end - Note right of SMO: Postcondition: -SMO has the queried/read information about the one or more PM jobs associated to the NF Deployment - -``` - -Sequence diagram showing the flow of query/reading information of PM jobs. Lifelines: SMO (NFO) and O-Cloud (DMS). The process involves a precondition (PM jobs created), an 'alt' block for 'Query information about multiple PM jobs' (steps 1-2) and 'Read information about an individual PM job' (steps 3-4), and a postcondition (SMO has the queried information). - -**Figure 4.4.4.2-1: Flow of query/reading information of PM jobs associated to an NF Deployment** - -The procedure of query/reading information of PM jobs associated to an NF Deployment consists of the following steps as illustrated in figure 4.4.4.2-1: - -NOTE: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** PM jobs have been created. - -- 1) If the SMO intends to query multiple PM jobs, it sends a GET request to the "PM jobs" resource. -- 2) The DMS returns a "200 OK" response to the SMO and includes zero or more data structures of type "PmJob" in the message content, according to the query request. -- 3) If the SMO intends to read the information of a particular PM job, it sends a GET request to the "Individual PM job" resource, by addressing to the appropriate PM job identifier in the resource URI. -- 4) The DMS returns a "200 OK" response and includes a data structure of type "PmJob" in the message content, according to the query request. - -**Postcondition:** The SMO has the queried/read information about the one or more PM jobs associated to the NF Deployment. - -**Error handling:** In case of failure, appropriate error information is provided in the response. - -#### 4.4.4.3 Delete a PM job - -The functionality of deleting a PM job associated to a VNF is covered in the ETSI NFV framework by the specific VNF performance management operation named "Delete PM Job". - -To delete a PM job associated to an NF Deployment using the present O2dms API profile, the following procedure is applicable: - -- 1) Delete a PM job by triggering the operation "Delete PM Job" on the specific "Individual PM Job" resource following the flow illustrated in "Flow of deleting a PM job" in clause 6.3.3 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the procedure is further profiled as illustrated in figure 4.4.4.3-1. - -Figure 4.4.4.3-1 illustrates the procedure flow for deleting a PM job associated to an NF Deployment. - -![Sequence diagram titled 'Delete a PM job associated to an NF Deployment'. It shows the interaction between an SMO (containing an NFO) and an O-Cloud (containing a DMS). The process starts with a Precondition: 'PM job has been created'. Step 1: The NFO sends a 'DELETE .../pm_jobs/{pmJobId}' request to the DMS. Step 2: The DMS 'Deletes the PM job resource'. Step 3: The DMS returns a '204 No Content' response to the NFO. The process ends with a Postcondition: 'The PM job associated to the NF Deployment has been deleted'.](7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg) - -Sequence diagram titled 'Delete a PM job associated to an NF Deployment'. It shows the interaction between an SMO (containing an NFO) and an O-Cloud (containing a DMS). The process starts with a Precondition: 'PM job has been created'. Step 1: The NFO sends a 'DELETE .../pm\_jobs/{pmJobId}' request to the DMS. Step 2: The DMS 'Deletes the PM job resource'. Step 3: The DMS returns a '204 No Content' response to the NFO. The process ends with a Postcondition: 'The PM job associated to the NF Deployment has been deleted'. - -Figure 4.4.4.3-1: Flow of deleting a PM job associated to an NF Deployment - -The procedure of deleting a PM job associated to an NF Deployment consists of the following steps as illustrated in figure 4.4.4.3-1: - -NOTE: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** The PM job has been created. - -- 1) If the SMO intends to delete a PM job, it sends a DELETE request to the "Individual PM job" resource, addressed by the appropriate PM job identifier in its resource URI. -- 2) The DMS deletes the "Individual PM job" resource and the PM job instance. -- 3) The DMS returns to the SMO a "204 No Content" response, with an empty message content. - -**Postcondition:** The PM job associated to the NF Deployment has been deleted. - -**Error handling:** In case of failure, appropriate error information is provided in the response. - -#### 4.4.4.4 Create a threshold - -The functionality of creating a threshold to specify threshold levels on specified performance metrics associated to a VNF is covered in the ETSI NFV framework by the specific VNF performance management operation named "Create Threshold ". - -To create a threshold associated to an NF Deployment using the present O2dms API profile, the following procedure is applicable: - -- 1) Create a threshold by triggering the operation "Create Threshold" on the "Thresholds " resource following the flow illustrated in "Flow of creating a threshold" in clause 6.3.5 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the procedure is further profiled as illustrated in figure 4.4.4.4-1. - -Figure 4.4.4.4-1 illustrates the procedure flow for creating a threshold associated to an NF Deployment. - -![Sequence diagram showing the flow of creating a threshold associated to an NF Deployment between SMO (NFO) and O-Cloud (DMS).](08f6ace0c83e7394657fa372b47aec04_img.jpg) - -``` - -sequenceDiagram - participant SMO as SMO (NFO) - participant OCloud as O-Cloud (DMS) - Note right of SMO: Precondition: None specified - SMO->>OCloud: 1 <> POST .../thresholds (CreateThresholdRequest) - Note right of OCloud: Testing the notification endpoint - OCloud->>SMO: 2 <> GET <> - SMO-->>OCloud: 3 <> 204 No Content - Note right of OCloud: 4 Creates the threshold resource - OCloud-->>SMO: 5 <> 201 Created (Threshold) - Note right of SMO: Postcondition: Threshold has been created and associated to the NF Deployment - -``` - -Sequence diagram showing the flow of creating a threshold associated to an NF Deployment between SMO (NFO) and O-Cloud (DMS). - -**Figure 4.4.4.4-1: Flow of creating a threshold associated to an NF Deployment** - -The procedure of creating a threshold associated to an NF Deployment consists of the following steps as illustrated in figure 4.4.4.4-1: - -NOTE: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** None specified. - -- 1) If the SMO intends to create a threshold, it sends a POST request to the "Thresholds" resource, including one data structure of type "CreateThresholdRequest" in the message content. The request includes information about the notification endpoint to be registered and to which notifications related to events about performance monitoring based on the threshold are expected to be sent. -- 2) To test the notification endpoint that has been registered, the DMS sends a GET request to the notification endpoint URI. -- 3) The SMO returns a "204 No Content" response to indicate success in testing the notification endpoint. -- 4) The DMS proceeds with the creation of the individual threshold resource and its instance (i.e., actual application instance or configuration that implements the threshold process). -- 5) The DMS returns a "201 Created" response to the SMO and includes in the message content a representation of the threshold that has been created. - -**Postcondition:** The threshold has been created and associated to the NF Deployment. - -**Error handling:** In case of failure, appropriate error information is provided in the response. - -#### 4.4.4.5 Query/read threshold information - -The functionality of querying/reading information of one or more thresholds associated to a VNF is covered in the ETSI NFV framework by the specific VNF performance management operation named "Query Threshold". The operation comprises two sub-cases: - -- Get information about multiple thresholds, and -- Get information about a specific threshold. - -To query information about one or more thresholds associated to an NF Deployment using the present O2dms API profile, the following sub-procedures are applicable: - -- 1) Get information of multiple thresholds by triggering the operation "Get Threshold" on the "Thresholds" resource following the alternative #1 in the flow illustrated in "Flow of querying/reading thresholds" in clause 6.3.6 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure is further profiled as illustrated in figure 4.4.4.5-1. -- 2) Query/read information of a specific threshold by triggering the operation "Get Threshold" on an "Individual threshold" resource, following the alternative #2 in the flow illustrated in "Flow of querying/reading thresholds" in clause 6.3.6 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the sub-procedure is further profiled as illustrated in figure 4.4.4.5-1. - -Figure 4.4.4.5-1 illustrates the procedure flow for querying/reading thresholds associated to an NF Deployment, including the sub-procedures introduced above. - -![Sequence diagram showing the flow of query/reading information of thresholds between SMO (NFO) and O-Cloud (DMS).](ddfa5b18550d1a022a941e3c31843814_img.jpg) - -The diagram illustrates the interaction between the SMO (NFO) and the O-Cloud (DMS) for querying threshold information. The process begins with a 'Query/read threshold information' message from SMO to O-Cloud. A precondition box indicates that 'Thresholds have been created'. The main part is an 'alt' block titled '[Query information about multiple thresholds]'. It contains two sub-alternatives: - -1) '[Query information about multiple thresholds]': SMO sends a '1 <> GET .../thresholds' request, and O-Cloud responds with '2 <> 200 OK (Threshold[])'. - -2) '[Read information about an individual threshold]': SMO sends a '3 <> GET .../thresholds/{thresholdId}' request, and O-Cloud responds with '4 <> 200 OK (Threshold)'. - -The process concludes with a postcondition box stating that 'SMO has the queried/read information about the one or more thresholds associated to the NF Deployment'. - -Sequence diagram showing the flow of query/reading information of thresholds between SMO (NFO) and O-Cloud (DMS). - -Figure 4.4.4.5-1: Flow of query/reading information of thresholds associated to an NF Deployment - -The procedure of query/reading information of thresholds associated to an NF Deployment consists of the following steps as illustrated in figure 4.4.4.5-1: - -NOTE: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** Thresholds have been created. - -- 1) If the SMO intends to query multiple thresholds, it sends a GET request to the "Thresholds" resource. -- 2) The DMS returns a "200 OK" response to the SMO and includes zero or more data structures of type "Threshold" in the message content, according to the query request. -- 3) If the SMO intends to read the information of a particular threshold, it sends a GET request to the "Individual threshold" resource, by addressing to the appropriate threshold identifier in the resource URI. -- 4) The DMS returns a "200 OK" response and includes a data structure of type "Threshold" in the message content, according to the query request. - -**Postcondition:** The SMO has the queried/read information about the one or more thresholds associated to the NF Deployment. - -**Error handling:** In case of failure, appropriate error information is provided in the response. - -#### 4.4.4.6 Delete a threshold - -The functionality of deleting a threshold associated to a VNF is covered in the ETSI NFV framework by the specific VNF performance management operation named "Delete Threshold". - -To delete a threshold associated to an NF Deployment using the present O2dms API profile, the following procedure is applicable: - -- 1) Delete a threshold by triggering the operation "Delete Threshold" on the specific "Individual threshold" resource following the flow illustrated in "Flow of deleting thresholds" in clause 6.3.7 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the procedure is further profiled as illustrated in figure 4.4.4.6-1. - -Figure 4.4.4.6-1 illustrates the procedure flow for deleting a threshold associated to an NF Deployment. - -![Sequence diagram showing the flow of deleting a threshold. Lifelines: SMO (NFO) and O-Cloud (DMS). The process starts with a precondition 'Threshold has been created'. Step 1: SMO sends a DELETE request to DMS. Step 2: DMS deletes the threshold resource. Step 3: DMS returns a 204 No Content response. The process ends with a postcondition 'The threshold associated to the NF Deployment has been deleted'.](1ca688982d625c3b8a8e382b675de466_img.jpg) - -``` - -sequenceDiagram - participant SMO - participant O-Cloud - Note left of SMO: Precondition: Threshold has been created - SMO->>O-Cloud: 1 <> DELETE .../threshold/{thresholdId} - Note right of O-Cloud: 2 Deletes the threshold resource - O-Cloud-->>SMO: 3 <> 204 No Content - Note right of O-Cloud: Postcondition: The threshold associated to the NF Deployment has been deleted - -``` - -Sequence diagram showing the flow of deleting a threshold. Lifelines: SMO (NFO) and O-Cloud (DMS). The process starts with a precondition 'Threshold has been created'. Step 1: SMO sends a DELETE request to DMS. Step 2: DMS deletes the threshold resource. Step 3: DMS returns a 204 No Content response. The process ends with a postcondition 'The threshold associated to the NF Deployment has been deleted'. - -Figure 4.4.4.6-1: Flow of deleting a threshold associated to an NF Deployment - -The procedure of deleting a threshold associated to an NF Deployment consists of the following steps as illustrated in figure 4.4.4.6-1: - -NOTE: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** The threshold has been created. - -- 1) If the SMO intends to delete a threshold, it sends a DELETE request to the "Individual threshold" resource, addressed by the appropriate threshold identifier in its resource URI. -- 2) The DMS deletes the "Individual threshold" resource and the threshold instance. -- 3) The DMS returns to the SMO a "204 No Content" response, with an empty message content. - -**Postcondition:** The threshold associated to the NF Deployment has been deleted. - -**Error handling:** In case of failure, appropriate error information is provided in the response. - -#### 4.4.4.7 Sending performance related notifications - -Sending notifications related to performance management of a VNF is covered in the ETSI NFV framework by the specific VNF fault management operation named "Notify". Therefore, performance management events, such as the availability of a performance report or a crossing of a threshold, are raised and sent by means of notifications. - -To perform the issuing of performance management notifications associated to an NF Deployment using the present O2dms API profile, the following procedure is applicable: - -- 1) Send a notification following the flow illustrated in "Flow of sending notifications" in clause 6.3.9 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the procedure is further profiled as illustrated in figure 4.4.4.7-1. - -In addition, to monitor the raised events in an asynchronous mode and be able to receive the corresponding notifications, the API consumer shall request the creation of corresponding subscriptions to NF Deployment performance management events. This is performed by providing in the procedures of creating PM jobs and thresholds the notification endpoint URI in the corresponding request messages. - -Figure 4.4.4.7-1 illustrates the procedure flow for sending performance related notification associated to an NF Deployment. - -![Sequence diagram showing the flow of performance management notifications between an SMO (NFO) and an O-Cloud (DMS). The process starts with a precondition: 'SMO has subscribed to notifications previously'. Step 1: An event related to a PM job or threshold occurs in the DMS. Step 2: The DMS sends a POST request to the SMO's callback URI with a notification. Step 3: The SMO responds with a 204 No Content. The postcondition is: 'SMO has received the notification'.](a780a960b3f2de2493d5785bedae10ff_img.jpg) - -``` - -sequenceDiagram - participant SMO as SMO (NFO) - participant O-Cloud as O-Cloud (DMS) - Note right of O-Cloud: Precondition: -SMO has subscribed to notifications previously - Note right of O-Cloud: 1 Event related to a PM job or threshold occurs that matches the subscription - O-Cloud->>SMO: 2 <> POST <> (<>) - SMO-->>O-Cloud: 3 204 No Content - Note right of O-Cloud: Postcondition: -SMO has received the notification - -``` - -Sequence diagram showing the flow of performance management notifications between an SMO (NFO) and an O-Cloud (DMS). The process starts with a precondition: 'SMO has subscribed to notifications previously'. Step 1: An event related to a PM job or threshold occurs in the DMS. Step 2: The DMS sends a POST request to the SMO's callback URI with a notification. Step 3: The SMO responds with a 204 No Content. The postcondition is: 'SMO has received the notification'. - -Figure 4.4.4.7-1: Flow of performance management notifications associated to an NF Deployment - -The procedure of notifying about performance management events associated to an NF Deployment consists of the following steps as illustrated in figure 4.4.4.7-1: - -NOTE: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** The SMO has subscribed to notifications previously. - -- 1) An event related to a PM job or threshold occurs in the DMS that matches a subscription for notifications. -- 2) The DMS generates and sends a notification that includes information about the event and sends it in the body of a POST request to the URI which the SMO has registered as part of the subscription request. The variable <> in the flow is a placeholder for the different types of notifications that can be sent via this service, including performance report availability and threshold crossing notifications. -- 3) The SMO acknowledges the successful delivery of the notification by returning to the DMS a "204 No Content" response. - -**Postcondition:** The SMO has received the notification. - -**Error handling:** If the DMS does not receive the "204 No Content" response from the SMO, it can retry sending the same notification. - -#### 4.4.4.8 Obtaining performance reports - -The functionality of obtaining performance reports of a VNF is not covered in the ETSI NFV framework by a specific VNF fault management operation, but rather by the joint functionality provided by the notification and query report procedures. - -To obtain the performance reports generated from PM jobs associated to an NF Deployment using the present O2dms API profile, the following sub-procedures are applicable: - -- 1) Receive a notification about the availability of performance information" and then query the "Individual performance report" resource following the alternative #1 in the flow illustrated in "Flow of obtaining performance - -reports" in clause 6.3.4 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the procedure is further profiled as illustrated in figure 4.4.4.8-1. - -- 2) Query/read list of available performance reports generated from a PM job, and then query the "Individual performance report" resource following the alternative #2 in the flow illustrated in "Flow of obtaining performance reports" in clause 6.3.4 of ETSI GS NFV-SOL 003 [11]. For the case of an NF Deployment, the procedure is further profiled as illustrated in figure 4.4.4.8-1. - -Figure 4.4.4.8-1 illustrates the procedure flow for obtaining performance reports of an NF Deployment including the procedure introduced above. - -![Sequence diagram showing the flow of obtaining performance reports between SMO (NFO) and O-Cloud (DMS). The process starts with an 'Acknowledge alarm' message. A precondition 'PM job has been created' is shown. An 'alt' block titled '[Receive notification about the availability of performance information]' contains two alternatives: 1) DMS sends PerformanceInformationAvailableNotification to SMO, and 2) SMO sends a GET request for pm_jobs to DMS, which returns a 200 OK (PmJob). Following this, the SMO sends a GET request for reports to DMS, which returns a 200 OK (PerformanceReport). A postcondition 'The performance report has been retrieved by the SMO' is shown at the end.](cc6f9dbfc36aa5821d9749ca84861f93_img.jpg) - -``` - -sequenceDiagram - participant SMO as SMO (NFO) - participant OCloud as O-Cloud (DMS) - Note right of SMO: Precondition: PM job has been created - alt Receive notification about the availability of performance information - Note right of OCloud: 1 <> Send PerformanceInformationAvailableNotification - Note left of SMO: [Read list of available performance reports] - Note right of SMO: 2 <> GET .../pm_jobs/{pmJobId} - Note left of OCloud: 3 <> 200 OK (PmJob) - else - Note right of SMO: 4 <> GET .../pm_jobs/{pmJobId}/reports/{reportId} - Note left of OCloud: 5 <> 200 OK (PerformanceReport) - end - Note right of SMO: Postcondition: The performance report has been retrieved by the SMO - -``` - -Sequence diagram showing the flow of obtaining performance reports between SMO (NFO) and O-Cloud (DMS). The process starts with an 'Acknowledge alarm' message. A precondition 'PM job has been created' is shown. An 'alt' block titled '[Receive notification about the availability of performance information]' contains two alternatives: 1) DMS sends PerformanceInformationAvailableNotification to SMO, and 2) SMO sends a GET request for pm\_jobs to DMS, which returns a 200 OK (PmJob). Following this, the SMO sends a GET request for reports to DMS, which returns a 200 OK (PerformanceReport). A postcondition 'The performance report has been retrieved by the SMO' is shown at the end. - -Figure 4.4.4.8-1: Flow of obtaining performance reports of NF Deployment - -The procedure of obtaining performance reports generated from a PM job associated to the NF Deployment consists of the following steps as illustrated in figure 4.4.4.8-1: - -NOTE: The procedure does not illustrate error cases, only successful procedure steps. - -**Precondition:** The PM job has been created. - -- 1) The DMS send to the SMO a PerformanceInformationAvailableNotification (see clause 4.4.4.7). The notification indicates the availability of a new performance report. The notification includes a link from which the report can be obtained. -- 2) Alternatively, the SMO can get the list of performance reports generated from a PM job by sending a GET request to the "Individual PM job" resource. The representation of the "Individual PM job" can include information about performance reports that are available for this PM job, including their links. -- 3) In case of the SMO requesting the information of the PM job, the DMS returns a "200 OK" response, including a data structure of type "PmJob" in the message content. - -- 4) Based on the information received either from step 1) or step 3), the SMO sends to the DMS a GET request to the URI obtained in those steps. The GET request addresses, by using corresponding identifiers, the particular "Individual PM job" resource and "Individual performance report" of interest. -- 5) The DMS returns a "200 OK" response to the SMO and includes a data structure of type "PerformanceReport" in the message content. - -**Postcondition:** The performance report has been retrieved by the SMO. - -**Error handling:** In case of failure, appropriate error information is provided in the response. - -## 4.5 Orchestration aspects with O2dms ETSI NFV profile - -### 4.5.1 O-Cloud Node Clusters, resource groups and tenancy - -For the deployment and lifecycle of NF Deployments either or both, virtualised resources and containerized workloads are necessary. Virtualised resources and/or containerized workloads are allocated from O-Cloud Node Clusters built from O-Cloud resource pools. The O-Cloud resource pools can also be shared or common for the deployment of multiple O-RAN NF. This is typically realized by enabling features such as resource groups and multi-tenancy. - -Figure 4.5.1-1 illustrates an exemplary configuration of the O-Cloud and DMS to describe the relationships between the DMS based on the ETSI NFV profile and the concept of O-Cloud Node Clusters described in O-RAN.WG6.TS.O2-GA&P [4]. - -![Diagram showing the relationship between SMO (NFO, FOCOM), O-Cloud (DMS, NF Deployment mgmt), and IMS. The SMO connects to the O-Cloud via O2dms and O2ims interfaces. The O-Cloud contains multiple DMS units, each with an NF Deployment mgmt component. These components manage O-Cloud Node Clusters for VMs and containers. A legend indicates that black squares represent virtualised resource management & control (e.g., OpenStack®) and blue squares represent container resource management & control (e.g., K8s®).](7e74ac663f3e644b589ed28f5fd29398_img.jpg) - -Diagram showing the relationship between SMO (NFO, FOCOM), O-Cloud (DMS, NF Deployment mgmt), and IMS. The SMO connects to the O-Cloud via O2dms and O2ims interfaces. The O-Cloud contains multiple DMS units, each with an NF Deployment mgmt component. These components manage O-Cloud Node Clusters for VMs and containers. A legend indicates that black squares represent virtualised resource management & control (e.g., OpenStack®) and blue squares represent container resource management & control (e.g., K8s®). - -**Figure 4.5.1-1: Exemplary configuration of O-Cloud and DMS relationship with O-Cloud Node Clusters** - -As illustrated in the figure 4.5.1-1, an NFO can interact with multiple DMS. Furthermore, as per the ETSI NFV profile, a single DMS can manage resources for NF Deployments in multiple O-Cloud Node Clusters (i.e., DMS 1:N O-Cloud Node Cluster relationship). In practical scenarios, based on de-facto or commonly used solutions for virtualised and containerized workload and resources management, it is assumed that a single virtualised resource management and control component (refer to the legend in figure 4.5.1-1) can manage resources from multiple O-Cloud Node Clusters for VM. In the case of O-Cloud Node Clusters for containers, it is assumed that the relationship is 1:1, i.e., one single container resource management and control component manages resources on a single O-Cloud Node Cluster for containers. This is represented in figure 4.5.1-1 by showing the endpoint of container resource management and control being associated 1:1 to one O-Cloud Node Cluster for container, and a single endpoint of VM resource management and control being associated to either one or multiple O-Cloud Node Cluster for VM. For more information about the interactions and relationship between the NF Deployment management and virtualised resources/containerized workload management and control, refer to clause 4.5.7. - -In the ETSI NFV-profiled O2dms interface, resource grouping, multi-tenancy and signalling of which O-Cloud Node Clusters to use for the NF Deployment are achieved by conveying over the O2 interface information that identifies the resource groups - -and tenant users to which the NF Deployments relate to in the form of one or multiple "VIM connection info". The data type "VimConnectionInfo" exchanged over the O2dms interface between the NFO and the DMS, and which is, and which is defined in clause 5.2.6.3.2, serves such purposes. Clause 5.2.6.3.2 specifies provisions about the conditions and usage of the various attributes in the "VimConnectionInfo" when applied to the management of NF Deployments on O-Cloud Node Clusters. - -The "VimConnectionInfo" contains attributes that support determining the type and specific function to use for resource infrastructure management (i.e., either virtualised resource or containerized management and control functions) of the O-Cloud resources assigned to the O-Cloud Node Cluster. Types of infrastructure management solutions that can be used are registered in the ETSI NFV registry of VIM-related information [19]. The structure of the registry is defined in Annex C of ETSI GS NFV-SOL 003 [11]. - -The ETSI NFV registry of VIM-related information [19] contains entries to support VM and containerized workloads management such as: - -- Registry entries related to VM-based resource management: a) registration of ETSINFV.OPENSTACK\_KEystone.V\_2, i.e., OpenStack® with Keystone V2, and b) registration of ETSINFV.OPENSTACK\_KEystone.V\_3, i.e., OpenStack® with Keystone V3, and -- Registry entries related to containerized workloads management: a) registration of ETSINFV.KUBERNETES.V\_1, i.e., Kubernetes®, b) registration of ETSINFV.DOCKER.V\_2, i.e., Docker® registry as CIR, and c) registration of ETSINFV.HELM.V\_3, i.e., Helm® as MCIOP Repository. - -NOTE 1: Void. - -NOTE 2: The OpenStack® Word Mark and OpenStack Logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. - -NOTE 3: The Kubernetes® Word Mark and Kubernetes Logo are either registered trademarks/service marks or trademarks/service marks of The Linux Foundation, in the United States and other countries and are used with the Linux Foundation's permission. - -NOTE 4: The Helm® Word Mark and Helm Logo are either registered trademarks/service marks or trademarks/service marks of The Linux Foundation, in the United States and other countries and are used with the Linux Foundation's permission. - -NOTE 5: The Docker® and the Docker logo are trademarks or registered trademarks of Docker, Inc. in the United States and/or other countries. - -Information about "VIM connection info" shall be known to the SMO as pre-requisite to perform NF Deployment lifecycle. The present document does not specify how the SMO builds the "VIM connection infos", although it is assumed that the SMO can use the information from the O2ims services produced by the IMS, such as the inventory services exposing information about O-Cloud Resources, including O-Cloud Node Clusters, and the available Deployment Management Services. - -The resources that are granted for consumption from the resource pools can be further grouped by "infrastructure resource groups", which can be mapped to logical groupings of virtualised resources assigned to a tenant (or user) within the O-Cloud. This is represented by the "resourceGroupId" attribute in the "ResourcePlacement" defined in clause 5.2.6.5.3. - -In the case of containerized workloads, the logical grouping of a particular set of identifiers, resources, policies and authorizations is realized by means of "namespaces". In addition, namespace quotas define the upper limit on specific types of resources that can be used to deploy containerized workloads within the scope of a namespace. This is represented by the "containerNamespace" attribute in the "ResourcePlacement" defined in clause 5.2.6.5.3. - -### 4.5.2 Placement information and constraints - -Placement information and constraints for NF Deployments are conveyed in the O2dms ETSI NFV profile out-of-band from the O2dms\_LifecycleDeployment API. ETSI GS NFV-SOL 003 [11] specifies data types which carry relevant information about placement and constraints, and such data types are either exchanged via the granting procedures or provided as placement requirements information in the descriptors. - -NOTE 1: In the present document version, granting exchanges are not specified. ETSI GS NFV-SOL 003 [11] defines the "VNF LCM granting interface" as the mechanism to convey placement and constraints information "in-band" from an API perspective. - -NOTE 2: Various forms for conveying placement and constraints information are possible, including: a) using some form of additional grant-less (no grant exchanges) API interactions, b) using declarative descriptors or configuration files, c) using granting exchanges conforming to those defined by ETSI GS NFV-SOL 003 [11], or d) a combination thereof. However, the present document version does not specify support for any of these specifically and it is left for specific deployment or implementation. - -The present clause describes the relevant information as defined in the "ResourcePlacement" type in clause 5.2.6.5.3 and "ResourcePlacementConstraint" type in clause 5.2.6.5.4. The information that can be conveyed using these types shall be made available to the DMS as a pre-condition for the instantiation of an NF Deployment by means not specified by the present document (see also note 2). - -Relevant attributes and types are: - -- "vimConnectionId": since there can be multiple connections to underlaying infrastructure resource management functions, the scope of management of an entity implementing such a function also determines a level of placement control. For instance, infrastructure resource management entities can be associated to manage resources of specific O-Cloud Node Clusters. Therefore, by indicating the VIM connection to use, a selection of which O-Cloud Node Cluster can be determined for a given NF Deployment to manage. -- "zoneId": resource zones provide a physical segregation of O-Cloud resources within an O-Cloud Site, and by identifying them, it can be controlled to which zone a resource is expected to be deployed. -- "ResourcePlacementConstraint": the type represents information about the placement constraints for two or more resources or containerized workloads of an NF Deployment in terms of affinity and anti-affinity and for diverse scope levels, such as O-Cloud Site, resource zones within an O-Cloud Site, and O-Cloud Nodes. The information about affinity and anti-affinity is typically provided by the deployment descriptors of the NF Deployment. - -NOTE 3: In the case of the ETSI GS NFV-SOL 003 [11], such a descriptor is referred as VNFD. Refer also to the description in table 4.3.2-1 of the present document. - -Containerized workloads can also have specific deployment constraints. Examples of deployment constraints are the following: defining specific O-Cloud Nodes to be used for the deployment or capabilities of the O-Cloud Nodes such as support for acceleration. The "mcioConstraints" attribute in the "ResourcePlacement" type defined in clause 5.2.6.5.3 can be used to convey these specific deployment constraints. - -### 4.5.3 Network connectivity for NF Deployments - -Network connectivity information of NF Deployments in the O2dms ETSI NFV profile is exposed and/or conveyed via specific data types. Furthermore, in terms of network connectivity the profile modelling is based on the following key concepts: virtual links and connection points. - -A virtual link is an abstraction of a network, which is used by the management and orchestration functions in the ETSI NFV architectural framework. Once applied to the O-RAN framework, virtual links also become an abstraction of connectivity which is exposed and used over the O2dms interface. Virtual links can be realized in various forms such as virtual/overlay networks in an O-Cloud site, or a composition of various networks. Virtual links can be internal or external to an NF Deployment: - -- Internal virtual link: it expresses the connectivity between the components or constituents of an NF Deployment. -- External virtual link: it expresses the connectivity external to the NF Deployment, i.e., networks that are used to interconnect among NF Deployments, or between NF Deployments and other entities such as to other O-RAN NF, xApps, or even other systems such as management and orchestration ones. - -Internal virtual links can be modelled in two forms depending on the entity that manages the resources realizing the virtual link: - -- NF Deployment virtual link: it denotes an internal NF Deployment virtual link that is managed by the DMS. The data type providing information about such kind of virtual link is named "VnfVirtualLinkResourceInfo" (see clause 5.2.6.3.9). - -- Externally-managed virtual link: it denotes an internal NF Deployment virtual link that is managed externally to the DMS, e.g., in the present profiling case the SMO. The data type providing information about such kind of virtual link is named "ExtManagedVirtualLinkInfo" (see clause 5.2.6.3.7). - -NOTE 1: The reason for differentiating the two types comes from the fact that there are deployment cases where the network resources are managed by organizations or systems different to those managing the NF Deployments. - -A connection point is also an abstraction that denotes the port/interface of connectivity of an NF Deployment or a constituent within an NF Deployment to a network. Similarly, as with the virtual link case, connections points are further qualified as internal or external connections points of an NF Deployment. - -- Internal connections points: these are the connection points used to connect to the internal virtual links of an NF Deployment. The structured "vnfcCpInfo" attribute in the "VnfcResourceInfo" provides information about such kind of connection point (see clause 5.2.6.3.8). -- External connection points: these are the connection points used to connect the NF Deployment to the external virtual links. The data type providing information about such kind of connection point is named "VnfExtCpInfo" (see clause 5.2.6.3.4). - -Figure 4.5.3-1 illustrates the composition of an NF Deployment and the relationship with the networking concepts. - -![Diagram of NF Deployment (VNF) showing internal virtual links, NF Deployment components (VNFC), storage, and external virtual links with connection points.](802707b774f2d2973b49cea2020e8453_img.jpg) - -The diagram illustrates the internal structure of an NF Deployment (VNF). At the top, a box labeled "Internal virtual link(s)" is connected to two "NF Deployment component (VNFC)" boxes. Each VNFC box contains a green circle representing an "Internal connection point" connected to the internal virtual link, and a blue circle representing an "External connection point". The left VNFC box also contains a "Storage" box connected to its internal connection point. An ellipsis (...) is shown between the two VNFC boxes. Below the VNF box, a box labeled "External virtual link(s)" is connected to the external connection points of the VNFCs. A legend at the bottom shows a green circle for "Internal connection point" and a blue circle for "External connection point". - -Diagram of NF Deployment (VNF) showing internal virtual links, NF Deployment components (VNFC), storage, and external virtual links with connection points. - -**Figure 4.5.3-1: NF Deployment and networking concepts** - -External connection points can be associated to various types of other connection points. For instance, an external connection point can be realized by an actual internal connection point of an NF Deployment, i.e., the internal connection point is re-exposed externally and used for connecting to the external virtual link, or it can also be realized by associating the external connection point directly with an internal virtual link. The former case is the one illustrated in figure 4.5.3-1. The type of the connection point and how it relates to the other constituents of an NF Deployment is denoted by a series of specific attributes in the "VnfExtCpInfo". - -In addition, other specific connection points are also defined depending on how they are further realized or mapped to. - -- Virtual IP connection point: it denotes a connection point which is basically a Virtual IP (VIP). -- Virtual connection point: it denotes a connection point which does not have a specific virtual resource representation in the infrastructure; instead, it is typically realized by some form of configuration into one or multiple resources (e.g., external load balancers). - -EXAMPLE 1: Kubernetes® Service is an example of a virtual connection point. - -Depending on the type of connection point, additional elements are modelled, such as the virtual link ports and network attachment definition resources to specify the points of attachment to the virtual links. - -- A virtual link port defines the point of attachment of a virtual network interface of a VM-based component of an NF Deployment to a virtual network. - -EXAMPLE 2: An OpenStack® Layer 2 Networking Port is an example of virtual link port. - -- A network attachment definition resource defines the point of attachment of a virtual network interface of an OS-container component of an NF Deployment to a secondary container cluster network. - -EXAMPLE 3: A Network Attachment Definition (NAD) of Multus CNIT™ is an example of a network attachment definition resource. - -NOTE 2: Void. - -NOTE 3: The CNIT™ Word Mark is a registered trademarks/service marks of The Linux Foundation, in the United States and other countries and are used with the Linux Foundation's permission. - -The virtual connection points and network attachment definition resources are features either specified or referenced by the Release 4 version of ETSI GS NFV-SOL 003 [11] and primarily concern to OS container-based deployments. There is no need to define connections points for the OS-container components of an NF Deployment that are connected to the primary container cluster network, because the OS-container components are by default connected to such a network when deployed. - -As defined in the present document, the API consumer (i.e., SMO) can convey various sets of network protocol information to the DMS to realize various network connectivity patterns. Two cases of connection point provisioning can be realized as supported by the attributes in the "VnfExtCpConfig" data type specified in clause 5.2.6.3.5: - -- The API consumer provisions with the infrastructure management functions in the O-Cloud the connection points in advance and provides subsequently to the DMS references to the virtual link ports or network attachment definition resources that have been provisioned. This case is applicable for both virtual link port-based and network attachment definition resource connectivity. -- The API consumer provides specific protocol layer information to the DMS, and the DMS subsequently uses such information to provision the virtual link ports or virtual connection points, depending on the type of connection point. This is only applicable for the case of virtual link port-based connectivity and virtual connection points. - -Regarding the protocol layer information, the "CpProtocolData" and "CpProtocolInfo" data types defined in clauses 5.2.6.3.25 and 5.2.6.3.13, respectively, represent information about the protocol layer(s) that a connection point uses and the associated protocol information. According to the profiled version of ETSI GS NFV-SOL 003 [11], two types of layer protocol types are supported: - -- "IP\_OVER\_ETHERNET": used to provide network address data for IP over Ethernet. -- "IP\_FOR\_VIRTUAL\_CP": used to provide network address data for an external connection point realized as a virtual connection point. - -For the IP over Ethernet case, additional data types provide the support to define MAC addresses, IP addresses, and types of segmentation and encapsulation, including VLAN ID support. For the IP for virtual connection point, the data types enable the support to assign concrete fixed IP addresses corresponding to the external load balancers associated to the virtual connection point. - -### 4.5.4 Software images information - -As described in clause 3.5.1 of O-RAN.WG6.TS.O2-GA&P [4], an O-RAN Cloudified Network Function Software Package is onboarded to further perform software and lifecycle management of O-RAN NF. The NF software package contains software images for the compute resource components of the NF. In the ETSI NFV-based profile, the NF software packaging concept is fulfilled by the "VNF package" artifact. - -To instantiate NF Deployments corresponding compute resource components of the NF Deployment have associated software images: - -- in the case of a VM-based NF Deployment: VM software images, and - -- in the case of a container-based NF Deployment, OS container software images. - -NOTE 1: O-Cloud assets are assumed to be conveyed out-of-band because in the present document version, granting exchanges are not specified. ETSI GS NFV-SOL 003 [11] defines the "VNF LCM granting interface" as the mechanism to convey such information "in-band". - -Regarding the NF Deployment lifecycle management, the onboarding of the software images to the O-Cloud and the transfer of related software image information of the NF Deployment shall be conveyed out-of-band of the O2dms\_LifecycleDeployment service API prior to requesting the instantiation of the NF Deployment. The provision of such information is realized in the form of "O-Cloud assets", which are specified in clause 5.2.6.5.5 using the data type "CloudAssets". In the context of ETSI GS NFV-SOL 003 [11] these are referred as "VIM assets". - -VIM assets contain "software image assets" that define the mapping between software images referred in the VNFD (NF Deployment descriptor) and software images managed in the infrastructure resource managers such as the VIM (for VM-based software images) and dedicated repositories such as the CIR (for container-based software images). - -NOTE 2: Void. - -OS container software images are features either specified or referenced by the Release 4 version of ETSI GS NFV-SOL 003 [11] and concern to OS container-based deployments. - -### 4.5.5 Resource management for NF Deployments - -NF Deployments are realized by one or multiple instances and types of resources, such as compute, storage and network. In the O2dms ETSI NFV profile, resource handles play a key role in keeping the traceability, inventory and accountability of the resources that are used by an NF Deployment. Resource handles also enable the DMS to manage such resources via the other DMS resource infrastructure functions. The data type providing information about a virtualised resource instance in the infrastructure is named "ResourceHandle" (see clause 5.2.6.3.20). All the constituents of an NF Deployment that have a resource representation in the O-Cloud have an associated resource handle. - -A resource handle compiles various types of information, but primarily: - -- An identification of the VIM or CISM connection (interface information and credentials) used to manage the resource. -- An identification of the resource within the scope of the infrastructure resource provisioning functions. -- Information about the type of resource within the scope of the infrastructure resource provisioning functions. -- Additional information about the resource which is specific to the resource and its type and that is made available by the underlying infrastructure resource management functions of the DMS (in the ETSI NFV terminology these are referred as VIM and CISM). -- Namespace of the resource, in case of a containerized workload resource. - -The types of resources composing the NF Deployment differ depending on the deployment form: - -- For VM-based deployments: compute, storage and network resources are realized as "virtual compute" (or VirtualCompute), "virtual storage" (or VirtualStorage) and "virtual network" (or VirtualNetwork). -- For OS container-based deployments: compute, storage and network resources are modeled as "Compute MCIO", "Storage MCIO" and "Network MCIO". MCIO stands for "Managed Container Infrastructure Object" and it models the objects that are managed and exposed by the container infrastructure services management and represents the desired and actual state of a containerized workload. - -EXAMPLE: In case of a Kubernetes® based implementation of infrastructure resources management functions for OS container-based deployments, examples of "Compute MCIO" are Deployment, Pod, StatefulSet; examples of "Storage MCIO" are: PersistentVolumeClaim; and examples of "Network MCIO" are Ingress, Service. For a full list of mapped Kubernetes® resource objects mapped to MCIOs, refer to ETSI GS NFV-SOL 018 [18]. - -Resources for NF Deployments are also defined based on the content in the deployment descriptors. In the case of the O2dms ETSI NFV profile, it is assumed that the NF Deployment has a corresponding deployment descriptor that provides - -requirements and describes the characteristics of the resources necessary for the deployment and lifecycle of the NF Deployment. - -NOTE 1: In the case of the ETSI GS NFV-SOL 003 [11], such a descriptor is referred as VNFD. Refer also to the description in table 4.3.2-1 of the present document. - -Key characteristics about resources that are of use by the profile are: - -- Deployment descriptors are identified. In the case of VNFD, the attribute is typically named as "vnfdId". -- Different types of resources can compose an NF Deployment (see also above). As per the present document version, the following are defined based on the classes defined in the "ResourceDefinition" data type (see clause 5.2.6.5.2). - - COMPUTE: represents a VM-based compute resource. - - VL: represents a virtual link, which in turns represents a network resource, e.g., virtual network. - - STORAGE: represents a storage resource. - - LINKPORT: represents a link port, i.e., a port of attachment to a network. - - OSCONTAINER: represents an OS container-based compute resource. - - VIRTUALCP: represents a virtual connection point. -- Resources have associated resource templates (declarative descriptors). In the case of a VM-based compute resource, the template is further identified by the attribute named "vduId". -- Allocated resources are identifiable using a corresponding "ResourceHandle". - -NOTE 2: Void. - -In the case of OS container-based deployments, additional types defined by the ETSI GS NFV-SOL 003 [11] are also considered: - -- "McioInfo": it provides information on the MCIO(s) representing the constituents of the NF Deployment that are realized by one or a set of OS containers and that are created using the same declarative descriptor. - -As introduced in clause 4.5.1, the "VimConnectionInfo" is used to indicate the type of resource infrastructure management to use as well as the necessary information to enable the consumption of such management. - -### 4.5.6 Acceleration abstraction layer - -#### 4.5.6.1 Overview - -The O-RAN.WG6.AAL-GAnP.0 [31] introduces the concepts of acceleration abstraction layer (AAL), whose purpose is to specify a common and consistent interface for hardware accelerators to the applications in order to facilitate the decoupling of an application, e.g., an O-RAN NF, from a specific hardware implementation. - -In the context of the O2dms ETSI NFV profile and related orchestration procedures, there are three aspects to be considered: - -- The description of acceleration requirements for an NF Deployment, -- Information exchange between the DMS consumer and the DMS about requested acceleration capabilities for an NF Deployment, and -- Injecting acceleration-related configuration into the NF Deployment. - -Annex A.2 describes examples related to AAL when using the O2dms ETSI NFV profile related specifications. - -#### 4.5.6.2 Description of acceleration requirements - -NF Deployment descriptors can contain information and requirements about the acceleration capabilities and resources that are needed by an NF Deployment. The descriptors also provide the means for declaring configurable properties, extensions, or additional lifecycle parameters. These can be used to apply configuration related to acceleration capabilities and resources used - -by the NF Deployment. Figure 4.5.6.2-1 provides a high-level conceptual illustration of the main elements contained in the descriptors, which are summarized as follows: - -- Additional capabilities requirements: description that is used to define requirements the NF Deployment has with respect to additional capabilities, typically, offered by the infrastructure. -- Placement constraints: description that indicates constraints and requirements regarding the placement rules for the NF Deployment and its constituents. -- Configurable properties and modifiable attributes: description about configuration parameters and information that can be modified on an NF Deployment. -- LCM additional parameters: description of parameters that are provided during NF Deployment lifecycle management operations. - -These sets of information and relationship with acceleration related aspects are further described in the present and subsequent clauses. - -![Diagram of NF Deployment package structure based on ETSI NFV. The package contains a VNFD block with four sub-elements: Additional capabilities requirements, Placement constraints, VNF/VNFC configurable properties and modifiable attributes, and VNF LCM additional parameters. Below the VNFD block are two more elements: Other artifacts (e.g., software images) and MCIOP(s).](977811d1c73b74f801be9f4c376694ca_img.jpg) - -``` - -graph TD - subgraph Package [NF Deployment package (based on ETSI NFV)] - subgraph VNFD [VNFD] - A[Additional capabilities requirements] - B[Placement constraints] - C[VNF/VNFC configurable properties and modifiable attributes] - D[VNF LCM additional parameters] - end - E[Other artifacts (e.g., software images)] - F[MCIOP(s)] - end - -``` - -Diagram of NF Deployment package structure based on ETSI NFV. The package contains a VNFD block with four sub-elements: Additional capabilities requirements, Placement constraints, VNF/VNFC configurable properties and modifiable attributes, and VNF LCM additional parameters. Below the VNFD block are two more elements: Other artifacts (e.g., software images) and MCIOP(s). - -**Figure 4.5.6.2-1: Representation of elements in the NF Deployment package which can hold relevant configuration, capabilities, and placement requirements** - -Regarding the declaration of additional capabilities, in the case of the O2dms ETSI NFV profile and the use of the VNFD as defined in ETSI GS NFV-IFA 011 [12], requirements for additional capabilities of compute-related resources are defined as follows: - -- In the case of OS container-based components of an NF Deployment, the "Vdu" information element specified in ETSI GS NFV-IFA 011 [12] includes the "requestAdditionalCapabilities" attribute, which is used to specify requirements for additional capabilities such as acceleration ones. -- In the case of VM-based components of an NF Deployment, the "VirtualComputeDesc" information element specified in ETSI GS NFV-IFA 011 [12] includes as well a "requestAdditionalCapabilities" attribute, with the same purpose as described in the item above. - -Regarding network related resources, the "VirtualNetworkInterfaceRequirements" defined in the NF Deployment unit connection points (referred as "VduCpd" in ETSI GS NFV-IFA 011 [12]) and in NF Deployment external connection points (referred as "VnfExtCpd" in ETSI GS NFV-IFA 011 [12]) enable the NF designer to indicate standard and additional network interface requirements, e.g., to support SR-IOV or secondary container cluster network interfaces. - -**NOTE:** The present document version does not specify the source(s) from where requested additional capabilities and virtual network interface requirements can be referenced into the NF Deployment descriptor. - -The "RequestedAdditionalCapability" information element in NF Deployment descriptor can be used to describe for each of the components in the NF Deployment the requirements about what AAL profiles and other associated characteristics are needed by the NF Deployment. This can be described on a per deployable unit of the NF Deployment. - -In addition, for the concrete case of OS container-based component of an NF Deployment, the "mcioConstraintsParams" in the "Vdu" information element provides parameter names for constraints expected to be assigned to the MCIO realizing the NF Deployment unit. ETSI GS NFV-IFA 011 [12] specifies the following MCIO constraint parameter values to express associated semantical constraint context and which are related to acceleration capabilities: - -- "nodeAdditionalCapabilityDpdk": to indicate that the NF Deployment unit needs a cluster node with DPDK driver capability. -- "nodeAdditionalCapabilitySriov": to indicate that the NF Deployment unit needs a cluster node with SR-IOV card(s). -- "nodeAdditionalCapabilityGpu": to indicate that the NF Deployment unit needs a cluster node with GPU acceleration device(s). -- "nodeAdditionalCapabilityFpga": to indicate that the NF Deployment unit needs a cluster node with FPGA device(s). - -More information about the relationship between NF Deployment and the concept of MCIO is available in clause 4.5.5. - -The use of configurable properties, modifiable attributes, and LCM additional parameters for conveying relevant acceleration configuration information are further described in subsequent clauses. - -#### 4.5.6.3 O2dms interface exchanges - -AAL LPU requirements for the NF Deployment as well as other deployment constraints and requirements can be provided to the DMS in two forms: - -- On O2dms interface exchanges, and -- NF Deployment descriptors. - -Regarding O2dms interface exchanges, acceleration capabilities and resources information cover the following aspects: - -- MCIO constraints: these are used to provide values assigned to the MCIOs of an NF Deployment that has OS container-based components. This is provided as part of the "ResourcePlacement" data type specified in clause 5.2.6.5.3. The "key" part of the key-value pair of MCIO constraints is defined in the NF Deployment descriptor (see clause 4.5.6.2), while the "value" part of the key-value pair is the actual key-value pair used in the labelling of the O-Cloud Nodes in the O-Cloud Node Cluster. -- NF Deployment (and units) configurable properties and modifiable attributes: these are used to provide to the DMS runtime configuration and information, e.g., to cater for specific deployment scenarios or state. -- NF Deployment lifecycle additional parameters: these are used to provide to the DMS additional parameters applicable to the specific lifecycle management operation that is performed for the NF Deployment. - -The actual requirements about the AAL profiles that are required by an NF Deployment is part of the NF Deployment descriptors (see previous clause 4.5.6.2). The NF Deployment descriptors are made available to the DMS, either as a pre-condition to initiate the lifecycle operation or during the lifecycle management procedures in which components of an NF Deployment (i.e., NF Deployment units) are created, updated, or terminated. - -The O2dms ETSI NFV profile also supports the capability to provide runtime configuration related to acceleration capabilities in case that specific deployment information is expected and is not possible to be determined at design time of the NF Deployment via the corresponding descriptors (refer to items #2 and #3 in the list above). Additional description about these attributes is provided in clause 4.5.6.4. - -Processing by the DMS of which concrete instances of LPU to allocate is regarded to be an implementation matter of the DMS. However, the DMS implementation shall be capable to process the expressed requirements provided via the NF Deployment descriptors together with the additional input configuration and information provided via the O2dms interface(s). In addition, DMS shall consider if a pre-selection of AAL resources and O-Cloud Nodes have been determined by the SMO. This information can be made available by the SMO to the DMS using the MCIO constraints based on specific values of O-Cloud Nodes labelling (see also clause 4.5.6.2). - -#### 4.5.6.4 Configuring NF Deployments with acceleration related information - -##### 4.5.6.4.1 Overview - -As described in clause 4.2.2 of O-RAN.WG6.AAL-Common-API [32] and clause 4.1.6 of O-RAN.WG6.AAL-GAnP.0 [31], AAL applications (as part of the NF Deployment) might need certain configuration about the assigned LPUs (e.g., LPU address in the form of a PCI device identification). In case configuration related to acceleration is to be injected into the NF Deployments via lifecycle management procedures, the O2dms ETSI NFV profile provides the following supporting mechanisms: - -- Provisioning configuration data using day-0 mechanisms: in this case, the relevant configuration data is injected during the allocation of the O-Cloud resources and creation of the VM/OS containers realizing the NF Deployment unit. -- Provisioning configuration data using day-1 mechanisms: in this case, the relevant configuration data is injected after the O-Cloud resource has been allocated and the VM/OS container realizing the NF Deployment unit has been created, but before determining that the NF Deployment is fully operational and ready (i.e., instantiation is completed). - -ETSI GR NFV-EVE 022 [i.4] reports about available VNF configuration mechanisms, and clause 4.2 of ETSI GR NFV-EVE 022 [i.4] includes descriptions about the meanings of "day-0" and "day-1" configuration in relation to instantiation process of VNF and VNFC instances, which are mapped to NF Deployment and NF Deployment units, respectively, in the present document. - -##### 4.5.6.4.2 Day-0 configuration - -For day-0 configuration, two mechanisms for providing configuration related to acceleration capabilities to the NF Deployment are defined depending on the form of deployment of the NF Deployment units constituting the NF Deployment: - -- NF Deployment unit based on VM: the "boot data" defined in the NF Deployment descriptor contains strings or URL to files contained in the NF Deployment package that can be used to customize the VM compute resource at boot time. The boot data can contain variable parts that are replaced by deployment specific values during the NF Deployment lifecycle operation before sending the data to the infrastructure manager responsible for creating and setting up the VM. -- NF Deployment unit based on OS container: the configuration data is declared in the NF Deployment descriptor and in other configuration files within the MCIOPs (e.g., Helm® Charts). The technical realization of the mechanism depends on the container infrastructure management solution. When Kubernetes® and Helm® are used, Helm® Charts can contain values.yaml file(s) with key-value pairs. The DMS can create new values.yaml files to override the value in a key-value pair with the value provided by one or more configurable properties. The key-value pairs in the values.yaml can be used to parameterize Kubernetes® objects such as ConfigMap or Secret, or also be used by Init containers or combinations of commands and arguments declared in the Pod specification manifest. - -NOTE: The mechanism of NF Deployment unit based on OS container can also be used for day-1 configuration. - -Day-0 configuration data values related to acceleration capabilities can be provided to the DMS by the SMO according to the O2dms ETSI NFV profile using specific attributes of the "InstantiateVnfRequest" (see clause 5.5.2.4 of ETSI GS NFV-SOL 003 [11]) and "VnfInfoModificationRequest" (see clause 5.5.2.12 of ETSI GS NFV-SOL 003 [11]). The VNFD, as NF Deployment descriptor, specifies and indicates whether to use one or multiple of the attributes above, and which ones to use. Table 4.5.6.4.2-1 describes the relevant attributes for providing day-0 configuration to NF Deployments. - -**Table 4.5.6.4.2-1: Interface attributes for providing day-0 configuration to NF Deployments** - -| Attribute | Data type in the O2dms ETSI NFV profile | Associated information elements and attributes in the descriptor (reference to ETSI GS NFV-IFA 011 [12]). See note 1 | Description and usage | -|------------------|------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------| -| additionalParams | InstantiateVnfRequest (see clause 5.5.2.4 of ETSI GS NFV-SOL 003 [11]) | VnfLcmOperationsConfiguration
-> instantiateVnfOpConfig
-> parameter | Parameters that are specified for its use only during the instantiation of an NF Deployment. | - -| | | | | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | It can be used to provide to the DMS acceleration related configuration only for VM-based NF Deployment units. It can be used to fill/modify as "volatile" values the variable parts of the boot data. See note 2. | -| extensions | InstantiateVnfRequest and VnfInfoModificationRequest (see clause 5.5.2.12 of ETSI GS NFV-SOL 003 [11]) | Vnfd.modifiableAttributes
-> extension |

Parameters that are used to affect the lifecycle management of the NF Deployment. The attributes and values are stored persistently by the DMS and can be queried and modified. The parameters are intended to be consumed by the DMS or by the lifecycle management scripts during the execution of the NF Deployment lifecycle operation. The values can indirectly affect the configuration of the NF Deployment.

It can be used to provide to the DMS acceleration related configuration only for VM-based NF Deployment units. It can be used to fill/modify as "persistent" values the variable parts of the boot data. See note 2.

| -| vnfConfigurableProperties | InstantiateVnfRequest and VnfInfoModificationRequest | Vnfd.configurableProperties
-> additionalConfigurableProperty

and

Vnfd.vdu.configurableProperties
-> additionalVnfcConfigurableProperty |

Parameters that are used to configure an NF Deployment. Modifying the values directly affects the configuration of an existing NF Deployment instance.

It can be used to provide to the DMS acceleration related configuration for both VM-based and OS container-based NF Deployment units.

In the case of VM-based NF Deployment units, it can be used to fill/modify as "persistent" values the variable parts of the boot data. See note 2.

In the case of OS container-based NF Deployment units, it can be used to provide runtime values to the configuration objects associated to the NF Deployment unit depending on their container infrastructure management solution.

| -| NOTE 1: NFV descriptors based on TOSCA are specified in ETSI GS NFV-SOL 001 [10]. Equivalent data types and attributes in TOSCA are referenced in clause 6.1 of ETSI GS NFV-SOL 001 [10]. | | | | -| NOTE 2: "Volatile" refers to values that are only applicable during the respective NF Deployment lifecycle management operation execution. "Persistent" refers to values that are applicable during the whole lifecycle of the NF Deployment. | | | | - -##### 4.5.6.4.3 Day-1 configuration - -For day-1 configuration, the O2dms ETSI NFV profile enables the SMO to provide NF Deployment configuration values using the attributes described in table 4.5.6.4.3-1. - -**Table 4.5.6.4.3-1: Interface attributes for providing day-1 configuration to NF Deployments** - -| Attribute | Data type in the O2dms ETSI NFV profile | Associated information elements and attributes in the descriptor (reference to ETSI GS NFV-IFA 011 [12]). See note | Description and usage | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| vnfConfigurableProperties | InstantiateVnfRequest and VnfInfoModificationRequest | Vnfd.configurableProperties
-> additionalConfigurableProperty

and

Vnfd.vdu.configurableProperties
-> additionalVnfcConfigurableProperty | Parameters that are used to configure an NF Deployment. Modifying the values affects directly the configuration of an existing NF Deployment instance.

It can be used to provide to the DMS acceleration related configuration for both VM-based and OS container-based NF Deployment units. | -| NOTE: NFV descriptors based on TOSCA are specified in ETSI GS NFV-SOL 001 [10]. Equivalent data types and attributes in TOSCA are referenced in clause 6.1 of ETSI GS NFV-SOL 001 [10]. | | | | - -The mechanisms by which the DMS applies the configuration depend on the form of deployment of the relevant NF Deployment units, and these are not "visible" over the interfaces specified in the present O2dms ETSI NFV profile. The mechanisms are regarded to be an implementation or integration matter of the different solutions that constitute an DMS. A description of potential solutions is provided for information purposes: - -- In the case the NF Deployment is realized by VM-based technology and depending on the mechanism that the NF Deployment supports, possible mechanisms are: a) using the "VNF configuration" interface specified by ETSI GS NFV-SOL 002 [29], b) using other standard interfaces based on other protocols such as NETCONF, c) using specific agent-less based configuration tools such as Ansible®. -- In the case the NF Deployment is realized by OS container-based technology, and depending on the mechanism that the NF Deployment supports, possible mechanisms are: a) using the "VNF configuration" interface specified by ETSI GS NFV-SOL 002 [29], b) using other standard interfaces based on other protocols such as NETCONF, c) using specific agent-less based configuration tools such as Ansible, and in addition, d) using specific mechanisms supported by the container infrastructure management solution such as ConfigMap and Secrets in case of Kubernetes®. - -NOTE: The Ansible® trademark is a registered trademark of Red Hat, Inc. in the United States, and other countries. - -### 4.5.7 DMS Interactions - -#### 4.5.7.1 Overview - -As described in clause 4.3.2 and as per the present profile based on "O2-D demarcation #1" (see clause 4.1), the DMS has two main parts: - -- NF Deployment management, and -- Resource management of NF Deployments, wherein resources can be virtualised resources and containerized workloads. - -On the northbound, the DMS exposes the interfaces specified by the present document, which are at the NF Deployment level. Internally, the DMS performs the resources management to fulfil the necessary resources for the NF Deployment. Considering the types of resources (virtual resources and containerized workloads), interactions with other components responsible for the management of these types of resources from the associated O-Cloud Node Clusters, are assumed to take place within the DMS. As described in table 4.3.2-2, according to the ETSI NFV standards, the VIM is the functional block in ETSI NFV - -responsible for the management of virtualised resources within an O-Cloud Node Cluster, and the CISM the function is responsible for the management of containerized workloads within an O-Cloud Node Cluster. - -#### 4.5.7.2 Models in DMS interactions - -The present document specifies the protocol and data model of the O2dms interactions. The NF Deployment is the managed object exposed on O2dms, and the models are concerned to such a level of management. As described in clause 4.5.5, NF Deployments are realized by one or multiple instances of types of resources: in VM-based deployment, these are referred as virtualised resources, and for OS container-based deployments, these are referred as MCIOs (but more typically referred as containerized workloads). - -The virtualised resources and containerized workloads management parts of the DMS may use specific resources models tailored for the types of resources realizing the NF Deployment. The resources models (indicated by (2) in figure 4.5.7.2-1) can contain information defined at design time of the NF Deployment, but also be complemented by information extracted (coming from) the O2dms interactions based on NF deployment models (indicated by (1) in figure 4.5.7.2-1). - -![Diagram of Models in interactions. A central box labeled 'DMS' contains three sub-boxes: 'NF Deployment mgmt' at the top, 'Virtualised resources mgmt' at the bottom left, and 'Containerized workloads mgmt' at the bottom right. A double-headed vertical arrow labeled '(1) O2dms NF deployment models' connects the top of the DMS box to the 'NF Deployment mgmt' box. Two double-headed vertical arrows labeled '(2) resources models' connect the 'NF Deployment mgmt' box to both the 'Virtualised resources mgmt' and 'Containerized workloads mgmt' boxes.](4260aa4a7ece77c411597094c9d197bd_img.jpg) - -Diagram of Models in interactions. A central box labeled 'DMS' contains three sub-boxes: 'NF Deployment mgmt' at the top, 'Virtualised resources mgmt' at the bottom left, and 'Containerized workloads mgmt' at the bottom right. A double-headed vertical arrow labeled '(1) O2dms NF deployment models' connects the top of the DMS box to the 'NF Deployment mgmt' box. Two double-headed vertical arrows labeled '(2) resources models' connect the 'NF Deployment mgmt' box to both the 'Virtualised resources mgmt' and 'Containerized workloads mgmt' boxes. - -Figure 4.5.7.2-1: Models in interactions - -The O2dms NF deployment models comprise two main aspects: - -- NF Deployment design-time information: this is also referred as NF Deployment descriptor, and -- NF Deployment run-time information and management interfaces: this corresponds to the O2dms ETSI NFV profile modelling specified in the present document. - -The resources models can comprise, as well, two main aspects: - -- Resources run-time information and management interfaces: these correspond to interfaces and information provided by the virtualised resources and containerized workloads management parts of the DMS. -- (Optionally) declarative descriptors for resources management: these can be manifests or templates modelling the actual resources and that can be used to facilitate the interactions towards the resources management functions. - -According to the present O2dms ETSI NFV profile, the NF Deployment models provide a generic modelling for managing NF Deployments, irrespective of the types of resources that comprise them. It is a responsibility of the NF Deployment management functions to resolve the necessary resource type specific models. For this, the NF Deployment management functions may, but need not, make use of resources models manifests or templates contained in the O-RAN NF software package. - -Figure 4.5.7.2-2 illustrates an overview of the set of models and indicative sets of content in respective descriptors/template/manifests and APIs. - -![Diagram illustrating the content of O2dms and resource management models. It shows two rows of boxes connected by a dashed line. Row 1: (1) O2dms NF deployment models, containing 'NF Deployment descriptor' and 'O2dms API' with a plus sign between them. Row 2: (2) resources models, containing 'Resource templates/descriptors' and 'Resource management API (internal to DMS)' with a plus sign between them. Arrows point from Row 1 to Row 2.](b35ea3e304aad7d350a9902270413930_img.jpg) - -**(1) O2dms NF deployment models** - -**NF Deployment descriptor** - (1.1a) Design time attributes with values - (1.1b) Configurable properties keys - (1.1c) API additional parameters keys - -+ - -**O2dms API** - (1.2a) Standard run-time parameters values - (1.2b) Configurable properties values - (1.2c) API additional parameters values - ---- - -**(2) resources models** - -**Resource templates/descriptors** - (2.1a) Design time attributes with values - (2.1b) Configuration keys - (2.1c) Resource management API parameters keys - -+ - -**Resource management API (internal to DMS)** - (2.2a) Resource management API parameters values (\*) - (2.2b) Configuration values (\*) - -Diagram illustrating the content of O2dms and resource management models. It shows two rows of boxes connected by a dashed line. Row 1: (1) O2dms NF deployment models, containing 'NF Deployment descriptor' and 'O2dms API' with a plus sign between them. Row 2: (2) resources models, containing 'Resource templates/descriptors' and 'Resource management API (internal to DMS)' with a plus sign between them. Arrows point from Row 1 to Row 2. - -**Figure 4.5.7.2-2: Illustration of content in the O2dms and resource management models** - -Table 4.5.7.2-1 summarizes the relationship between the sets of content in the O2dms and resource management models. - -**Table 4.5.7.2-1: Relationship between sets of content in the o2dms and resource management models** - -| Group | Content set | Description | Relationship | -|--------------------------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------| -| NF Deployment descriptor | 1.1a | Standardized design time attributes with values provided by the NF designer. Attributes can concern to NF Deployment and resource properties/requirements. | Resource related properties/requirements can relate to 2.1a. | -| | 1.1b | Configurable properties keys, some can be defined by standard, some can be defined by the NF designer. Properties can concern to NF Deployment and resource related configuration. | Part of the attributes can relate to 2.1b. | -| | 1.1c | Definition of keys for additional parameters defined by the NF designer. Parameters can concern to NF Deployment management and resource related management. | Part of the parameters can relate to 2.1c. | -| O2dms API | 1.2a | Standardized parameters defined by the API with capability to provide values at run-time. Parameters can concern to NF Deployment management, and some can concern to resource properties. | Values for the 1.1a. Part of the parameters can relate to 2.2a. | -| | 1.2b | Provides values for the NF Deployment configurable properties. | Values for the 1.1b. | -| | 1.2c | Provides values for the API additional parameters. | Values for the 1.1c. | -| Resource templates/descriptors | 2.1a | Attributes and values of resources of the NF Deployment defined according to the resource templates/descriptors data models. | Some attributes and values can also be defined on the 1.1a. | -| | 2.1b | Definition of parameter keys for resource-level configuration. | Some of the configuration values can also be defined in 1.1b. | -| | 2.1c | Definition of parameters keys related to resource management defined by the NF designer. | Keys can relate to 2.1a for making parts of the templates parameterizable. | -| Resource management API | 2.2a | Provides values for the resource management API parameters keys. | Values for the 2.1c. See note. | - -| | | | | -|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------|------------------------------------------------------|-----------------------------------| -| | 2.2b | Provides values for the resource-level configuration | Values for the 2.1b.
See note. | -| NOTE: Depending on the form of the API, this data could be provided via files (e.g., a "values.yaml" in the case of Helm), instead of actual content in the API messages. | | | | - -### 4.5.8 Monitoring of NF Deployments - -#### 4.5.8.1 Overview - -NF Deployments are realized by one or multiple instances and types of resources, such as compute, storage, and network. Associated to NF Deployments, as managed objects, performance information and faults can be monitored. - -#### 4.5.8.2 Performance monitoring - -Performance monitoring is performed via the present O2DMS ETSI NFV profile via the exposure of a corresponding API produced by the DMS, the O2dms\_DeploymentPerformance Service API. The monitoring is performed via: - -- PM Jobs, and -- Thresholds. - -Collection and reporting of performance information is controlled via PM Jobs. - -The performance information is associated to managed object instances, which in the case of the O2DMS, these are the NF Deployments. In addition, sub-object instances can also be further qualified. These are determined depending on the type of metrics that can be monitored from the NF Deployment. For instance, the NF Deployment serves as the main object type, while an NF Deployment unit (aka as VNFC in the case of ETSI NFV) is a kind of sub-object that is part of an NF Deployment. A consumer, such as the SMO, can learn about the managed objects, such as the NF Deployment, via the O2dms\_DeploymentLifecycle Service. - -Performance metrics associated to VNF instances, and consequently to NF Deployments (as per the current profile) are specified in ETSI GS NFV-IFA 027 [34]. - -#### 4.5.8.3 Fault monitoring - -Fault monitoring is performed via the present O2DMS ETSI NFV profile via the exposure of a corresponding API produced by the DMS, the O2dms\_DeploymentFault Service API. The monitoring is performed via Alarms, which are raised to provide information about faults and failures associated to the managed objects of concern. - -Like in the case of performance monitoring, NF Deployment serves as the main object type, while other sub-objects are also identified to which specific fault information can be associated. A consumer, such as the SMO, can learn about the managed objects, such as the NF Deployment, via the O2dms\_DeploymentLifecycle Service. - -Standard alarms associated to VNF instances, and consequently to NF Deployments (as per the current profile) are specified in ETSI GS NFV-IFA 045 [35]. - -# 5 API definitions - -## 5.1 General aspects - -### 5.1.1 Introduction - -The present document defines the protocol and data model for the following O2dms service interfaces in the form of RESTful Application Programming Interface (API) specifications: - -- O2dms\_DeploymentLifecycle Service API (as produced by the DMS towards the SMO). -- O2dms\_DeploymentFault Service API (as produced by the DMS towards the SMO). -- O2dms\_DeploymentPerformance Service API (as produced by the DMS towards the SMO). - -NOTE: Other service APIs are expected to be defined in future versions of the present document. - -Table 5.1.1-1 lists the versions of the APIs defined in the present document. - -**Table 5.1.1-1: Versions of the APIs specified in the present document** - -| API | API version | -|-----------------------------------------|-------------| -| O2dms_DeploymentLifecycle Service API | 2.14.0 | -| O2dms_DeploymentFault Service API | 1.14.0 | -| O2dms_DeploymentPerformance Service API | 2.13.0 | - -In clause 5, general aspects are specified that apply to multiple APIs for O2dms services. In addition, the provisions in clauses 5.1.2, 5.1.3, 5.1.4, 5.1.5, 5.1.6, 5.1.7, and 5.1.8 define common aspects of RESTful APIs, and shall apply for all APIs defined in the present document. - -In the subsequent clauses, the protocol and data model for the individual interfaces are specified. Per interface, the resource structure with associated HTTP methods is defined and applicable flows are provided, if necessary. Further, the resources and the data model are specified in detail. - -Even though the different interfaces defined in the present document are related, implementations shall not assume a particular order of messages that arrive via different interfaces. - -### 5.1.2 URI structure and supported content formats - -This clause specifies the URI prefix and the supported formats applicable to the O2dms RESTful APIs based on the ETSI NFV profile. - -All resource URIs of the APIs shall have the following prefix, except the "API versions" resource which shall follow the rules specified in clause 9.3 of ETSI GS NFV-SOL 013 [15]: - -**{apiRoot}//** - -The request URIs used in HTTP requests from the API service consumer towards the API service producer shall have the Resource URI structure defined in clause 4.1 of ETSI GS NFV-SOL 013 [15] and further qualified as follows: - -**{apiRoot}//** - -with the following components: - -- The {apiRoot} indicates the scheme ("https"), the host name and optional port, and an optional sequence of path segments that together represent a prefix path, -- The indicates the API name of the service interface in an abbreviated form. The {apiName} of each interface is defined in the clause specifying the corresponding O2dms RESTful API, - -- The indicates the current major version of the API and is defined in the clause specifying the corresponding O2dms RESTful API, and -- The indicates a resource URI of the API, and shall be set as described in the corresponding O2dms RESTful API for each one of the defined resources. - -HTTP/1.1, as defined in IETF RFC 7230 [24], shall be used. The Transmission Control Protocol (TCP) as specified in IETF RFC 793 [20] shall be used as transport protocol for HTTP/1.1. - -For HTTP requests and responses that have a body, the content format JSON (see IETF RFC 8259 [25]) shall be supported. The JSON format shall be signalled by the content type "application/json". - -All APIs shall support and use HTTP over TLS (also known as HTTPS) (see IETF RFC 2818 [36]). All APIs shall use TLS version 1.2 as defined by IETF RFC 5246 [23] or later. - -NOTE 1: The HTTP protocol elements mentioned in the O2dms RESTful APIs originate from the HTTP specification; HTTPS runs the HTTP protocol on top of a TLS layer. For simplicity, the O2dms RESTful APIs specifications therefore use the statement above to mention "HTTP request", "HTTP header", etc., without explicitly calling out HTTPS. - -NOTE 2: There are a number of best practices and guidelines how to configure and implement TLS 1.2 in a secure manner, as security threats evolve. A detailed specification of those is beyond the scope of the present document; the reader is referred to external documentation such as annex E of ETSI TS 133 310 [37]. - -All resource URIs of the API shall comply with the URI syntax as defined in IETF RFC 3986 [22]. An implementation that dynamically generates resource URI parts (individual path segments, sequences of path segments that are separated by "/", query parameter values) shall ensure that these parts only use the character set that is allowed by IETF RFC 3986 [22] for these parts. - -NOTE 3: This means that characters not part of this allowed set are escaped using percent-encoding as defined by IETF RFC 3986 [22]. - -Unless otherwise specified explicitly, all request URI parameters that are part of the path of the resource URI shall be individual path segments, i.e., shall not contain the "/" character. - -NOTE 4: A request URI parameter is denoted by a string in curly brackets, e.g. {fooId}. - -### 5.1.3 Usage of HTTP header fields - -#### 5.1.3.1 General - -HTTP headers are components of the header section of the HTTP request and response messages. They contain the information about the server/client and metadata of the transaction. The use of HTTP header fields shall comply with the provisions defined for those header fields in the specifications referenced from tables 5.1.3.2-1 and 5.1.3.3-1. The following clauses describe more details related to selected HTTP header fields. - -#### 5.1.3.2 Request header fields - -The request header fields that shall be supported by O2dms RESTful APIs are as specified in clause 4.2.2 of ETSI GS NFV-SOL 013 [15]. - -NOTE: ETSI GS NFV-SOL 013 [15] refers to "RESTful NFV-MANO API" specification; and wherever such reference is provided "O2dms RESTful API" is to be considered instead for the purpose of the present document. - -#### 5.1.3.3 Response header fields - -The response header fields that shall be supported by O2dms RESTful APIs are as specified in clause 4.2.3 of ETSI GS NFV-SOL 013 [15]. - -NOTE: ETSI GS NFV-SOL 013 [15] refers to "RESTful NFV-MANO API" specification; and wherever such reference is provided "O2dms RESTful API" is to be considered instead for the purpose of the present document. - -### 5.1.4 Result set control - -#### 5.1.4.1 Introduction - -This clause specifies procedures that allow to control the size of the result set of GET requests w.r.t. the number of entries in a response list (using attribute-based filtering) or w.r.t. the number of attributes returned in a response (using attribute selection). - -#### 5.1.4.2 Attribute-based filtering and selector - -The use of attribute-based filtering shall be supported by O2dms RESTful APIs as specified in clause 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [15]. - -NOTE: ETSI GS NFV-SOL 013 [15] refers to "RESTful NFV-MANO API" specification; and wherever such reference is provided "O2dms RESTful API" is to be considered instead for the purpose of the present document. - -#### 5.1.4.3 Handling of large query results - -The handling of large query results shall be supported by O2dms RESTful APIs as specified in clause 5.4.2 of ETSI GS NFV-SOL 013 [15]. - -### 5.1.5 Error reporting - -In RESTful interfaces, application errors are mapped to HTTP errors. Since HTTP error information is generally not enough to discover the root cause of the error, additional application specific error information is typically delivered. - -The error reporting shall be supported by O2dms RESTful APIs as specified in clause 6 of ETSI GS NFV-SOL 013 [15]. - -NOTE: ETSI GS NFV-SOL 013 [15] refers to "RESTful NFV-MANO API" specification; and wherever such reference is provided "O2dms RESTful API" is to be considered instead for the purpose of the present document. - -### 5.1.6 Common data types - -#### 5.1.6.1 Structured data types - -##### 5.1.6.1.1 Introduction - -This clause defines data structures that are referenced from data structures in multiple O2dms RESTful APIs. - -##### 5.1.6.1.2 Introduction - -An object contains structured data and shall comply with the provisions of clause 4 of IETF RFC 8259 [25]. - -##### 5.1.6.1.3 Type: Link - -This type represents a link to a resource using an absolute URI. It shall comply with the provisions defined in table 5.1.6.1.3-1. - -**Table 5.1.6.1.3-1: Definition of the Link data type** - -| Attribute name | Data type | Cardinality | Description | -|----------------|-----------|-------------|---------------------------------------------------------------------------------------------------------------------| -| href | Uri | 1 | URI of another resource referenced from a resource. Shall be an absolute URI (i.e., a URI that contains {apiRoot}). | - -##### 5.1.6.1.4 Type: NotificationLink - -This type represents a link to a resource in a notification, using an absolute or relative URI. It shall comply with the provisions defined in table 5.1.6.1.4-1. - -**Table 5.1.6.1.4-1: Definition of the NotificationLink data type** - -| Attribute name | Data type | Cardinality | Description | -|----------------|-----------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| href | Uri | 1 | URI of a resource referenced from a notification. Should be an absolute URI (i.e., a URI that contains {apiRoot}), however, may be a relative URI (i.e., a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available. | - -##### 5.1.6.1.5 Type: KeyValuesPairs - -This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key-value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259 [25]. In the following example, a list of key-value pairs with four keys ("aString", "aNumber", "anArray" and "anObject") is provided to illustrate that the values associated with different keys can be of different type. - -###### EXAMPLE: - -``` -{ - "aString" : "O2dms service", - "aNumber" : 0.03, - "anArray" : [1,2,3], - "anObject" : {"organization" : "O-RAN", "workingGroup" : "WG6"} -} -``` - -##### 5.1.6.1.6 Type: ApiVersionInformation - -This type represents API version information. It shall comply with the provisions defined in table 5.1.6.1.6-1. - -**Table 5.1.6.1.6-1: ApiVersionInformation data type** - -| Attribute name | Data type | Cardinality | Description | -|-----------------|---------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| uriPrefix | String | 1 | Specifies the URI prefix for the API, in the following form {apiRoot}/{apiName}/{apiMajorVersion}/. | -| apiVersions | Structure (inlined) | 1..N | Version(s) supported for the API signaled by the uriPrefix attribute. | -| >version | String | 1 | Identifies a supported version. The value of the version attribute shall be a version identifier as specified in clause 9.1 of ETSI GS NFV-SOL 013 [15]. | -| >isDeprecated | Boolean | 0..1 | If such information is available, this attribute indicates whether use of the version signaled by the version attribute is deprecated (true) or not (false).
See note. | -| >retirementDate | DateTime | 0..1 | The date and time after which the API version will no longer be supported.
This attribute may be included if the value of the isDeprecated attribute is set to true and shall be absent otherwise. | - -NOTE: A deprecated version is still supported by the API producer but is recommended not to be used any longer. When a version is no longer supported, it does not appear in the response body. - -#### 5.1.6.2 Simple data types and enumerations - -##### 5.1.6.2.1 Introduction - -This clause defines simple data types and enumerations that can be referenced from data structures defined in multiple interfaces. - -##### 5.1.6.2.2 Simple data types - -Table 5.1.6.2.2-1 lists the simple data types that are referenced from multiple interfaces. - -**Table 5.1.6.2.2-1: Simple data types** - -| Type name | Description | -|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Identifier | An identifier with the intention of being globally unique. Representation: string of variable length. See note 1. | -| DateTime | A date-time stamp. Representation: String formatted as defined by the date-time production in IETF RFC 3339 [21]. | -| Uri | A string formatted according to IETF RFC 3986 [22]. | -| Boolean | A data type having two values (true and false). | -| IpAddress | An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons. | -| Version | A version. Representation: string of variable length. | -| String | A string as defined in IETF RFC 8259 [25]. | -| Number | A number as defined in IETF RFC 8259 [25]. | -| Integer | An integer, i.e., a number that cannot have a fractional component. See note 2. | -| UnsignedInt | An unsigned integer, i.e., an integer that can't assume negative values. See note 2. | -| NOTE 1: | Individual API specifications are assumed to define types for additional identifiers with dedicated scope (e.g., identifiers scoped by some O-Cloud). | -| NOTE 2: | In the JSON instance data model, only the concept of a "number" is used to represent numerical data. Numbers in JSON can be integral, i.e., have no fractional part, or can include a fractional part. The additional numeric types defined in the present document represent constraints on the general "number" type present in JSON instances which can be enforced e.g., during parsing when processing the JSON instance or expressed as constraints in modelling languages such as JSON Schema [26] or OpenAPI [27]. | - -### 5.1.7 Authorization of API requests and notifications - -#### 5.1.7.1 Introduction - -The present version of this document does not specify specific authorization mechanisms to be considered for handling API requests and notifications specified in the present document. The provisions specified in clause 8 of ETSI GS NFV-SOL 013 [15] shall apply. Furthermore, annex G of ETSI GS NFV-SOL 003 [11] defines authorization scope values for selected APIs that are profiled in the present document. - -NOTE: ETSI GS NFV-SOL 013 [15] refers to "RESTful NFV-MANO API" specification; and wherever such reference is provided "O2dms RESTful API" is to be considered instead for the purpose of the present document. - -### 5.1.8 Version management - -#### 5.1.8.1 Version identifiers and parameters - -API version identifiers and rules for incrementing version identifier fields shall be supported by O2dms RESTful APIs as specified in clause 9.1 and 9.2 of ETSI GS NFV-SOL 013 [15]. - -NOTE: ETSI GS NFV-SOL 013 [15] refers to "RESTful NFV-MANO API" specification and OpenAPI specification that ETSI publishes; and wherever such reference is provided "O2dms RESTful API" and OpenAPI that O-RAN publishes is to be considered instead for the purpose of the present document. - -Clause 9.2.2 of ETSI GS NFV-SOL 013 [15] provides examples of backward and non-backward compatible changes. - -#### 5.1.8.2 Version information retrieval and signaling - -The API producer shall support the dedicated URIs to enable API consumers to retrieve information about API versions supported by an API producer as specified in clause 9.3 of ETSI GS NFV-SOL 013 [15], and the API consumer shall include the "Version" HTTP header in each HTTP request as specified in clause 9.4 of ETSI GS NFV-SOL 013 [15]. - -NOTE: ETSI GS NFV-SOL 013 [15] refers to "RESTful NFV-MANO API" specification; and wherever such reference is provided "O2dms RESTful API" is to be considered instead for the purpose of the present document. - -### 5.1.9 HTTP conditional requests - -Conditional requests are HTTP (POST, PUT, PATCH and DELETE) requests that include one or more header fields indicating a precondition to be tested before applying the method semantics to the target resource. They are supported by metainformation about the resource that was provided in earlier HTTP responses. The set of HTTP header fields to compose a conditional request allowed in the present version of the present document is defined in clause 4.8 of ETSI GS NFV-SOL 003 [11]. - -## 5.2 O2dms\_DeploymentLifecycle Service API - -### 5.2.1 Description - -This service interface enables an API consumer (e.g., the SMO) to invoke lifecycle management operations of NF Deployments towards the DMS. The service interface also enables the management of subscriptions to notifications raised by the DMS regarding the lifecycle of the NF Deployments. - -### 5.2.2 API version - -For the O2dms\_DeploymentLifecycle Service API version as specified in the present document, the MAJOR version field shall be "2", the MINOR version field shall be "14", and the PATCH version field shall be "0" as specified in clause 5.1.a of ETSI GS NFV-SOL 003 [11]. Consequently, the {apiMajorVersion} URI variable shall be set to "v2". - -### 5.2.3 REST resources structure and methods - -All resource URIs of the API shall use the base URI specified defined in clause 5.1.2. The string "vnflcm" shall be used to represent {apiName} as defined in clause 5.2 of ETSI GS NFV-SOL 003 [11]. All resource URIs in clauses below are defined relative to the formed based URI (i.e., {apiRoot}/xyz/{apiVersion}). - -When ambiguity is possible, the term REST resource is used to make the distinction between the term resource as understood within the context of REST API from the term resource as understood within the context of O-RAN. - -The resource URI structure defined for the O2dms\_DeploymentLifecycle Service API shall be as specified in clause 5.2 of ETSI GS NFV-SOL 003 [11]. Applicable individual REST resources for the present version of the O2dms\_DeploymentLifecycle Service API are listed in table 5.2.3-1. - -Figure 5.2.3-1 illustrates the overall resource URI structure defined for the O2dms\_DeploymentLifecycle Service API. - -![Resource URI structure tree diagram for the O2dms_DeploymentLifecycle Service API. The root is {apiRoot}/vnflcm/{apiMajorVersion}. It branches into /vnf_instances, /vnf_lcm_op_occs, and /subscriptions. /vnf_instances branches into /vnf_instances/{vnfInstanceId}, which further branches into /instantiate, /terminate, /heal, /scale, /scale_to_level, /change_ext_conn, /change_vnfpkg, and /change_flavour. /vnf_lcm_op_occs branches into /vnf_lcm_op_occs/{vnfLcmOpOccId}, which further branches into /retry, /rollback, /fail, and /cancel. /subscriptions branches into /subscriptions/{subscriptionId}.](66e89867f97592fd4bfab0e4f2b2054f_img.jpg) - -``` - - {apiRoot}/vnflcm/{apiMajorVersion} - ├── /vnf_instances - │ └── /vnf_instances/{vnfInstanceId} - │ ├── /instantiate - │ ├── /terminate - │ ├── /heal - │ ├── /scale - │ ├── /scale_to_level - │ ├── /change_ext_conn - │ ├── /change_vnfpkg - │ └── /change_flavour - ├── /vnf_lcm_op_occs - │ └── /vnf_lcm_op_occs/{vnfLcmOpOccId} - │ ├── /retry - │ ├── /rollback - │ ├── /fail - │ └── /cancel - └── /subscriptions - └── /subscriptions/{subscriptionId} - -``` - -Resource URI structure tree diagram for the O2dms\_DeploymentLifecycle Service API. The root is {apiRoot}/vnflcm/{apiMajorVersion}. It branches into /vnf\_instances, /vnf\_lcm\_op\_occs, and /subscriptions. /vnf\_instances branches into /vnf\_instances/{vnfInstanceId}, which further branches into /instantiate, /terminate, /heal, /scale, /scale\_to\_level, /change\_ext\_conn, /change\_vnfpkg, and /change\_flavour. /vnf\_lcm\_op\_occs branches into /vnf\_lcm\_op\_occs/{vnfLcmOpOccId}, which further branches into /retry, /rollback, /fail, and /cancel. /subscriptions branches into /subscriptions/{subscriptionId}. - -**Figure 5.2.3-1: Resource URI structure of the O2dms\_DeploymentLifecycle Service API** - -Table 5.2.3-1 lists the individual REST resources defined and the applicable HTTP methods. The DMS shall support responding to requests for all HTTP methods on the resources in table 5.2.3-1 that are marked as "M" (mandatory) in the "Cat" column. - -**Table 5.2.3-1: Resources and methods overview** - -| Resource name | Resource URI | HTTP method | Cat | Description (see note 2) | -|-------------------------|-----------------------------------------------------------|-------------|-----|-----------------------------------------------------------------------------------------------| -| VNF instances | /vnf_instances
See note 1. | GET | M | Query multiple NF Deployments. | -| | | POST | M | Create a new "Individual VNF instance" resource which represents an individual NF Deployment. | -| Individual VNF instance | /vnf_instances/{vnfInstanceId}
See note 1. | GET | M | Read information about an individual NF Deployment. | -| | | PATCH | M | Modify information of an individual NF Deployment. | -| | | DELETE | M | Delete an "Individual VNF instance" resource representing an individual NF Deployment. | -| Instantiate VNF task | /vnf_instances/{vnfInstanceId}/instantiate
See note 1. | POST | M | Instantiate an NF Deployment. | -| Terminate VNF task | /vnf_instances/{vnfInstanceId}/terminate
See note 1. | POST | M | Terminate an NF Deployment instance. | - -| | | | | | -|-----------------------------------------|-----------------------------------------------------------------|--------|------------|----------------------------------------------------------------------------------------------------------------------------------------| -| Heal VNF task | /vnf_instances/{vnfInstanceId}/heal
See note 1. | POST | M | Heal an NF Deployment instance. | -| Scale VNF task | /vnf_instances/{vnfInstanceId}/scale
See note 1. | POST | M | Scale an NF Deployment instance. | -| Scale VNF to Level task | /vnf_instances/{vnfInstanceId}/scale_to_level
See note 1. | POST | M | Scale an NF Deployment instance to a target level. | -| Change external VNF connectivity task | /vnf_instances/{vnfInstanceId}/change_ext_conn
See note 1. | POST | M | Change the external connectivity of an NF Deployment instance. | -| Change current VNF package task | /vnf_instances/{vnfInstanceId}/change_vnfpkg
See note 1. | POST | M | Change the current package on which an NF Deployment is based. | -| Change VNF flavour task | /vnf_instances/{vnfInstanceId}/change_flavour
See note 1. | POST | M | Change the flavour of an NF Deployment instance. | -| VNF LCM operation occurrences | /vnf_lcm_op_occurrences
See note 1. | GET | M | Query information about multiple lifecycle management operation occurrences of NF Deployments. | -| Individual VNF LCM operation occurrence | /vnf_lcm_op_occurrences/{vnfLcmOpOccId}
See note 1. | GET | M | Query information about an "Individual VNF LCM operation occurrence" corresponding to the lifecycle of an NF Deployment. | -| Retry operation task | /vnf_lcm_op_occurrences/{vnfLcmOpOccId}/retry
See note 1. | POST | M | Retry a lifecycle management operation occurrence of an NF Deployment | -| Rollback operation task | /vnf_lcm_op_occurrences/{vnfLcmOpOccId}/rollback
See note 1. | POST | M | Rollback a lifecycle management operation occurrence of an NF Deployment | -| Fail operation task | /vnf_lcm_op_occurrences/{vnfLcmOpOccId}/fail
See note 1. | POST | M | Fail a lifecycle management operation occurrence of an NF Deployment | -| Cancel operation task | /vnf_lcm_op_occurrences/{vnfLcmOpOccId}/cancel
See note 1. | POST | M | Cancel a lifecycle management operation occurrence of an NF Deployment | -| Subscriptions | /subscriptions
See note 1. | POST | M | Subscribe to NF Deployment lifecycle notifications. | -| | | GET | M | Query information about multiple subscriptions to NF Deployment lifecycle notifications. | -| Individual subscription | /subscriptions/{subscriptionId}
See note 1. | GET | M | Read an "Individual subscription" resource which represents information about a subscription to NF Deployment lifecycle notifications. | -| | | DELETE | M | Terminate a subscription to NF Deployment lifecycle notifications. | -| Notification endpoint | (provided by API consumer)
See note 1. | POST | See note 3 | Notify about NF Deployment lifecycle events. | -| | | GET | See note 3 | Test the notification endpoint for NF Deployment lifecycle events. | - -NOTE 1: The resource URI value is the same as the one specified in ETSI GS NFV-SOL 003 [11]. - -NOTE 2: The specified meaning of the resource name and supported HTTP method in ETSI GS NFV-SOL 003 [11] applies, unless otherwise stated. Additional description can be presented in case of further refining its meaning in the context of O2dms specification. - -NOTE 3: The DMS shall support invoking the HTTP methods defined for the "Notification endpoint" resource exposed by the API consumer. If the API consumer supports invoking the POST method on the "Subscriptions" resource towards the DMS, it shall also support responding to the HTTP requests defined for the "Notification endpoint" resource. - -### 5.2.4 REST resources - -#### 5.2.4.1 General - -The DMS and API consumer of the O2dms\_DeploymentLifecycle Service API shall support all the provisions specified in clause 5.4 of ETSI GS NFV-SOL 003 [11], with the following considerations: - -- NFVO and VNFM entities referred in the ETSI GS NFV-SOL 003 [11] are mapped to SMO and DMS as defined in clause 4.3.2 of the present document. -- VNF and VNFC referred in the ETSI GS NFV-SOL 003 [11] are mapped to NF Deployment and NF Deployment unit as defined in clause 4.3.2 of the present document. -- Only the provisions associated to corresponding REST resources and methods listed in table 5.2.3-1 are applicable for the present document. That is, if a REST resource and method is not listed in table 5.2.3-1 of the present document, the corresponding clause in the ETSI GS NFV-SOL 003 [11] that specifies such REST resource, and its supported methods, is not required to be supported according to the present document version. If specific provisions to REST resources are considered with respect to the profiled API, these are specified in subsequent sub-clauses within clause 5.2.4 of the present document. -- For the list of referenced data types for notifications to support, these are defined in clause 5.2.5 of the present document. -- For the list of REST resource data types, structured data types and referenced simple types to be supported, refer to clauses 5.2.6.1, 5.2.6.2, 5.2.6.3 and 5.2.6.4 of the present document. - -NOTE 1: From version v07.00 of the present document, several resource and data model clauses have been voided to simplify the profile specification, since no specific provisions and/or considerations had been specified with respect to the baseline specification in ETSI GS NFV-SOL 003 [11]. - -As defined in clause 5.4.1.2 of ETSI GS NFV-SOL 003 [11], to handle the lifecycle operations of the managed entities a number of task resources are defined. These are related to potentially long-running operations such as instantiation and termination, in the case of the present document, of NF Deployments. Each occurrence of the NF Deployment lifecycle operation is represented by an "Individual VNF LCM operation occurrence". In the present document, the pre-conditions and postconditions for the operations defined in table 5.4.1.2-1 of ETSI GS NFV-SOL 003 [11] that apply are only: - -- Operation "Instantiate VNF", i.e., "Instantiate NF Deployment". -- Operation "Terminate VNF", i.e., "Terminate NF Deployment". -- Operation "Heal VNF", i.e., "Heal NF Deployment". -- Operation "Scale VNF", i.e., "Scale NF Deployment". -- Operation "Scale VNF to Level", i.e., "Scale NF Deployment to Level". -- Operation "Change external VNF connectivity", i.e., "Change external NF Deployment connectivity". -- Operation "Change current VNF package", i.e., "Change current NF Deployment package". -- Operation "Change VNF flavour", i.e., "Change NF Deployment flavour". - -In addition, the following specific DMS applicability conditions are considered with respect to the referenced specification regarding the NF Deployment lifecycle: - -- As part of the NF Deployment lifecycle processing for all relevant supported LCM operations, the DMS need not proceed with obtaining the grant. - -NOTE 2: Granting exchanges between DMS and SMO are not supported in the present document version. - -- Selected deployable modules and resource capacity definitions of an NF Deployment can be requested to be instantiated as part of the "Instantiate NF Deployment", "Change NF Deployment flavour" and "Change current NF Deployment package". However, the deployable modules cannot be changed or additional ones be selected once the NF Deployment is instantiated according to a specified NF Deployment flavour and referenced NF Deployment package, since the present document version does not profile the necessary task resource enabling such a capability. - -Resource capacity definitions can be used to perform vertical scaling (i.e., increasing or decreasing the resource capacity of all instances of one or multiple NF Deployment units) as part of the "Scale NF Deployment". - -#### 5.2.4.2 REST resource: VNF instances - -##### 5.2.4.2.1 Description - -This resource represents NF Deployment instances. The API consumer can use this resource to create and query "Individual VNF instance" resources, which represent the NF Deployments. - -##### 5.2.4.2.2 Resource definition - -The resource definition is defined in clause 5.4.2.2 of ETSI GS NFV-SOL 003 [11]. - -##### 5.2.4.2.3 Resource methods - -###### 5.2.4.2.3.1 POST - -The POST method for this resource is defined in clause 5.4.2.3.1 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- The "VNF package" represents the packaging of the NF Deployment as described in clause 4.3.2 of the present document. The packaging is expected to be onboarded and enabled as a condition for successfully creating the "Individual VNF instance" resource. The specification of how the VNF package is onboarded is outside the scope of the present document. -- The VNFD represents the NF Deployment descriptor as described in clause 4.3.2 of the present document. The DMS applies information and metadata from the VNFD into the "Individual VNF instance" resource as specified in clause 5.4.2.3.1 of ETSI GS NFV-SOL 003 [11]. - -#### 5.2.4.3 REST resource: Retry operation task - -##### 5.2.4.3.1 Description - -This task resource represents the "Retry operation". The API consumer can use this resource to request the retrying of a lifecycle management operation occurrence on an NF Deployment that is in a transient failure state. More information about error handling in NF Deployment lifecycle procedures is available in clause 5.2.7. - -#### 5.2.4.4 REST resource: Rollback operation task - -##### 5.2.4.4.1 Description - -This task resource represents the "Rollback operation". The API consumer can use this resource to request the rolling back of a lifecycle management operation occurrence on an NF Deployment. More information about error handling in NF Deployment lifecycle procedures is available in clause 5.2.7. - -##### 5.2.4.4.2 Resource definition - -The resource definition is defined in clause 5.4.15.2 of ETSI GS NFV-SOL 003 [11]. - -##### 5.2.4.4.3 Resource methods - -###### 5.2.4.4.3.1 POST - -The POST method for this resource is defined in clause 5.4.15.3.1 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following specific DMS applicability conditions are considered with respect to the referenced specification clause: - -- In case of rolling back an occurrence of the NF Deployment instantiation lifecycle operation, the DMS shall request to underlying infrastructure manager the release of the virtualised resources and/or containerized workloads that had been allocated to the NF Deployment. - -#### **5.2.4.5 REST resource: Fail operation task** - -##### **5.2.4.5.1 Description** - -This task resource represents the "Fail operation". The API consumer can use this resource to request marking the lifecycle management operation occurrence of an NF Deployment as "failed". More information about error handling in NF Deployment lifecycle procedures is available in clause 5.2.7. - -#### **5.2.4.6 REST resource: Cancel operation task** - -##### **5.2.4.6.1 Description** - -This task resource represents the "Cancel operation". The API consumer can use this resource to request cancelling an ongoing lifecycle management operation occurrence of an NF Deployment. More information about error handling in NF Deployment lifecycle procedures is available in clause 5.2.7. - -### **5.2.5 Notifications** - -#### **5.2.5.1 General** - -Notifications issued on the O2dms\_DeploymentLifecycle Service API shall comply to the Subscribe/Notify pattern described in clause 5.9 of ETSI GS NFV-SOL 015 [17]. - -Table 5.2.5.1-1 provides an overview of the notifications. - -**Table 5.2.5.1-1: O2dms\_DeploymentLifecycle notifications overview** - -| Data type | Clause defined | Description | -|---------------------------------------|--------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| VnflcmOperationOccurrenceNotification | 5.2.5.2 | This type represents the notification about an NF Deployment lifecycle management operation occurrence. | -| VnflIdentifierCreationNotification | 5.5.2.18 of ETSI GS NFV-SOL 003 [11] | This type represents the notification about the creation of an identifier for the NF Deployment. | -| VnflIdentifierDeletionNotification | 5.5.2.19 of ETSI GS NFV-SOL 003 [11] | This type represents the notification about the deletion of an identifier of the NF Deployment, and consequently of the deletion of the resource representing the NF Deployment. | - -#### **5.2.5.2 Type: VnflcmOperationOccurrenceNotification** - -This type represents the notification about an NF Deployment lifecycle management operation occurrence. It is used to inform the API consumer about changes in the lifecycle of the NF Deployment which are caused due to an occurrence of a respective lifecycle operation. - -The type is defined in clause 5.5.2.17 of ETSI GS NFV-SOL 003 [11]. In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- Only the following trigger conditions apply: - - Instantiation of the VNF, i.e., of the NF Deployment. - - Termination of the VNF instance, i.e., of the NF Deployment instance. - - Healing of the VNF instance, i.e., of the NF Deployment instance. This includes both "on-demand healing" and "auto-healing" (see clause 4.4.2.4). - -- Scaling of the VNF instance, i.e., of the NF Deployment instance. This includes both "on-demand scaling" and "auto-scaling" (see clause 4.4.2.5). -- Changing external connectivity of the VNF instance, i.e., of the NF Deployment instance. -- Changing of the current VNF package of the VNF instance, i.e., of the NF Deployment instance. -- Changing of the VNF flavour of the VNF instance, i.e., of the NF Deployment instance. -- Sequence of notifications in relation to "granting" are not applicable - -NOTE: Granting exchanges between DMS and SMO are not supported in the present document version. Refer also to the conditions described in clause 5.2.4.1. - -### 5.2.6 Data model - -#### 5.2.6.1 REST resource data types - -This clause specifies the data types used in resource representations and notifications supported by the present API. Table 5.2.6.1-1 lists the data types. - -**Table 5.2.6.1-1: O2dms\_DeploymentLifecycle resource data types** - -| Data type | Clause defined | Description | -|-------------|----------------|---------------------------------------------------------------------------------------| -| VnfInstance | 5.2.6.2.2 | This type represents an NF Deployment instance. | -| VnfLcmOpOcc | 5.2.6.2.3 | This type represents a lifecycle management operation occurrence of an NF Deployment. | - -#### 5.2.6.2 Structured data types - -##### 5.2.6.2.1 Introduction - -This clause defines the structured data types to be used in resource representations. - -All the structured data types specified in clause 5.5.2 of ETSI GS NFV-SOL 003 [11] shall be supported, with the exception of those that are only used in REST resources and message contents of non-supported REST resources and methods, i.e., that are not listed in table 5.2.3-1. If specific provisions to structured data types are considered with respect to the profiled API, these are specified in subsequent sub-clauses within clause 5.2.6.2 of the present document. - -##### 5.2.6.2.2 Type: VnfInstance - -The "VnfInstance" type represent an NF Deployment instance. The type is defined in clause 5.5.2.2 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- The following attributes need not be supported: -- The following links to resources need not be present even when the current status of the NF Deployment permits its presence: - - "\_links.indicators", - - "\_links.operate", - - "\_links.createSnapshot", - - "\_links.revertToSnaspsheet". - -All structure data types referenced (i.e., used as data type of attributes) in the "VnfInstance" shall be supported, with the following exceptions: - -- Void. - -##### 5.2.6.2.3 Type: VnfLcmOpOcc - -This type represents a NF Deployment lifecycle management operation occurrence. The type is defined in clause 5.5.2.13 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- The following attributes are further qualified as follows: - - "operationParams": supported objects content of the attribute shall correspond only to supported lifecycle management operations on the NF Deployment: INSTANTIATE, TERMINATE, SCALE, SCALE\_TO\_LEVEL, HEAL, CHANGE\_EXT\_CONN, CHANGE\_VNFPKG, CHANGE\_FLAVOUR. -- The following attributes need not be supported: - - "grantId", which indicates the identifier of the grant related to the operation occurrence (see note 2). - - "vnfSnapshotInfoId", - - "lcmCoordinations", - - "rejectedLcmCoordinations", -- The following links to resources need not be present even when the current status of the NF Deployment permits its presence: - - "\_links.grant", and - - "\_links.vnfSnapshot". - -NOTE 1: Void. - -NOTE 2: Granting exchanges between DMS and SMO are not supported in the present document version. Refer also to the conditions described in clause 5.2.4.1. - -NOTE 3: Void. - -##### 5.2.6.2.4 Type: HealVnfRequest - -The type represents the request parameters for the "Heal NF Deployment" operation (referred as "Heal VNF" in ETSI GS NFV-SOL 003 [11]). The type is defined in clause 5.5.2.9 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause of ETSI GS NFV-SOL 003 [11]: - -- The DMS shall support the following additional attributes in the "HealVnfRequest" message content: - - \* "vnfcInstanceId", with data type, cardinality and meaning as defined in clause 5.5.2.9 of ETSI GS NFV-SOL 002 [29], and - - \* "healScript", with data type content, cardinality and meaning as defined in clause 5.5.2.9 of ETSI GS NFV-SOL 002 [29]. - -NOTE: The additional attributes from the ETSI GS NFV-SOL 002 offer the capability to perform a "more granular" healing request, as well as further indications on the scripts or healing actions or set of rules for the healing procedure. - -#### 5.2.6.3 Referenced structured data types - -##### 5.2.6.3.1 Introduction - -This clause defines the structured data types that are referenced by other data types. - -All the referenced structured data types specified in clause 5.5.2 of ETSI GS NFV-SOL 003 [11] shall be supported, with the exception of those that are only used in REST resources and message contents of non-supported REST resources and methods, - -i.e., that are not listed in table 5.2.3-1. If specific provisions to referenced structured data types are considered with respect to the profiled API, these are specified in subsequent sub-clauses within clause 5.2.6.3 of the present document. In addition, all common structured data types in clause 4.4.1 of ETSI GS NFV-SOL 003 [11] shall be supported if referenced/used by other data types as indicated above. - -##### 5.2.6.3.2 Type: VimConnectionInfo - -This type represents parameters for a DMS to establish connectivity with underlying virtualised resource managers, containerized workload managers, container image repositories and MCIOP repositories. The structure is used to convey interface connectivity and credentials related parameters over the O2 interface. Additional parameters may be configured into the DMS by means outside the scope of the present document. - -The type is defined in clause 4.4.1.6 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- Following "vimType" attribute values shall be used depending on the kind of O-Cloud Node Cluster to be used for the NF Deployment: - - \* "VIM", when referencing a virtualised resource management and control function managing resources and software images for virtualised resources for one or multiple O-Cloud Node Clusters for VMs. - - \* "CISM", when referencing a containerized workload management and control function managing resources for a single O-Cloud Node Cluster for containers. - - \* "CIR", when referencing a software image repository for containerized workloads for one or multiple O-Cloud Node Clusters for containers. - - \* "MCIOP", when referencing a managed container infrastructure object package repository for containerized workloads for one or multiple O-Cloud Node Clusters for containers. -- "interfaceInfo" shall contain the information to access the endpoint of respective management and control function, and in particular: - - \* in the case of an O-Cloud Node Cluster for containers, it points to the control plane function of its respective cluster, and - - \* in the case of an O-Cloud Node Cluster for VMs, it points to the control plane function managing the one or multiple clusters assigned to it. -- the "accessInfo" shall contain the information to identify and access the infrastructure resource group that represents a single O-Cloud Node Cluster for VMs. - -##### 5.2.6.3.3 Type: IntVnfCpData - -This type represents input data related to one or more internal connection points of the NF Deployment created based on the same declarative descriptor. The type is defined in clause 4.4.1.18 of ETSI GS NFV-SOL 003 [11]. - -NOTE: The referenced ETSI GS NFV-SOL 003 [11] only supports referencing to internal connection points of the NF Deployment when attached to secondary container cluster networks, i.e., only applicable for connectivity of containerized workloads of an NF Deployment. - -##### 5.2.6.3.4 Type: VnfExtCpInfo - -This type represents information about an external connection point of an NF Deployment. The type is defined in clause 5.5.3.17 of ETSI GS NFV-SOL 003 [11]. - -##### 5.2.6.3.5 Type: VnfExtCpConfig - -This type represents network address information per instance of an external connection point of the NF Deployment. - -In the case of VM-based NF Deployment, the DMS will have to either use existing link ports to the virtualised networks enabled for the external connectivity or create the link ports itself. - -In the case of OS container-based deployment of a component of the NF Deployment exposing the external connection point, the DMS will have to use the network attachment definition resource of secondary container cluster network when connecting the connection point to the external VL. - -In all cases, including the case of using a Virtual CP as an external connection point of the NF Deployment, the "cpProtocolData" contained in the "VnfExtCpConfig" supports providing configuration of the network protocols (e.g., IP address data). - -The type is defined in clause 4.4.1.10a of ETSI GS NFV-SOL 003 [11]. - -##### 5.2.6.3.6 Type: ExtManagedVirtualLinkData - -This type represents an externally-managed internal virtual link of an NF Deployment. The type is defined in clause 4.4.1.12 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- The following attributes are further qualified as follows: - - "vimConnectionId", the attribute shall be supported since only direct-mode for resource management is supported, i.e., the part of the DMS exposing the present O2dms\_LifecycleDeployment interacts directly with the functions responsible for the infrastructure resource provisioning. -- The following attributes need not be supported: - - "extManagedMultisiteVirtualLinkId", which indicates an externally-managed multi-site virtual link instance (see note). -- The following attributes need not be present even when the conditions permit its presence: - - "resourceProviderId". - -##### 5.2.6.3.7 Type: ExtManagedVirtualLinkInfo - -This type represents information about an externally-managed internal virtual link of an NF Deployment. The type is defined in clause 5.5.3.3 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- The following attributes need not be supported: - - "extManagedMultisiteVirtualLinkId", which indicates the identifier of the externally-managed multi-site virtual link instance in the case that NF Deployment can span more than one O-Cloud site and multi-site connectivity becomes thus necessary. - -##### 5.2.6.3.8 Type: VnfcResourceInfo - -This type represents information about a component of an NF Deployment and the used virtualised compute and storage resources for VM-based deployment or Compute MCIO and Storage MCIO for OS container-based deployment. The type is defined in clause 5.5.3.5 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- The following attributes need not be supported: - - "reservationId". - -##### 5.2.6.3.9 Type: VnfVirtualLinkResourceInfo - -This type represents information about an internal virtual link instance of an NF Deployment and the associated virtualised network resource or Network MCIO. The type is defined in clause 5.5.3.6 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- The following attributes need not be supported: - -- "reservationId". - -##### 5.2.6.3.10 Type: VirtualStorageResourceInfo - -This type represents information about storage of an NF Deployment and the associated virtualised storage resource or Storage MCIO. The type is defined in clause 5.5.3.7 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- The following attributes need not be supported: - - "reservationId". - -##### 5.2.6.3.11 Type: McioInfo - -This type represents information about an MCIO representing the set of component instances of an NF Deployment that are realized by one or a set of OS containers and that have been created based on the same declarative descriptor. The type is defined in clause 5.5.3.24 of ETSI GS NFV-SOL 003 [11]. - -##### 5.2.6.3.12 Type: ExtLinkPortData - -This type represents an externally provided link port to be used to connect an external connection point of the NF Deployment to an external virtual link. This type is used in case of VM-based NF Deployments which use ports to connect to the virtual networks. The type is defined in clause 4.4.1.14 of ETSI GS NFV-SOL 003 [11]. - -##### 5.2.6.3.13 Type: VnfLinkPortData - -This type represents an externally provided link port to be used to connect a connection point of a constituent of the NF Deployment to an internal virtual link of the NF Deployment that is managed externally. This type is used in case of VM-based NF Deployments which use ports to connect to the virtual networks. The type is defined in clause 5.5.3.18 of ETSI GS NFV-SOL 003 [11]. - -##### 5.2.6.3.14 Type: VirtualCpAddressData - -This type represents network address data for a virtual CP. The type is defined in clause 4.4.1.10d of ETSI GS NFV-SOL 003 [11]. - -Refer to the provisions specified in clause 4.4.1.10d of ETSI GS NFV-SOL 003 [11] regarding the handling of providing IP address data for the external load balancer realizing the virtual CP, such as the case when no IP address is provided, and it is assigned by the container cluster, and to the cases when an external IP address is assigned but not by the container cluster. - -##### 5.2.6.3.15 Type: AffectedVnfc - -This type represents information about added, deleted, modified or temporary components of an NF Deployment. The type is defined in clause 5.5.3.13 of ETSI GS NFV-SOL 003 [11]. - -- The following attributes need not be supported: - - "resourceDefinitionId", which identifies resource definitions exchanged via the granting (see note 1). - -NOTE 1: Granting exchanges between DMS and SMO are not supported in the present document version. Refer also to the conditions described in clause 5.2.4.1. - -NOTE 2: Void. - -##### 5.2.6.3.16 Type: AffectedVirtualLink - -This type represents information about added, deleted, modified or temporary internal virtual links of an NF Deployment. The type is defined in clause 5.5.3.14 of ETSI GS NFV-SOL 003 [11]. - -- The following attributes need not be supported: - -- "resourceDefinitionId", which identifies resource definitions exchanged via the granting (see note 1). - -NOTE 1: Granting exchanges between DMS and SMO are not supported in the present document version. Refer also to the conditions described in clause 5.2.4.1. - -NOTE 2: Void. - -##### 5.2.6.3.17 Type: AffectedExtLinkPort - -This type represents information about added, deleted, modified external link ports attached to external virtual links to an NF Deployment. The type is defined in clause 5.5.3.14a of ETSI GS NFV-SOL 003 [11]. - -- The following attributes need not be supported: - - "resourceDefinitionId", which identifies resource definitions exchanged via the granting (see note). - -NOTE: Granting exchanges between DMS and SMO are not supported in the present document version. Refer also to the conditions described in clause 5.2.4.1. - -##### 5.2.6.3.18 Type: AffectedVipCp - -This type represents information about added, deleted, modified VIP connection points of an NF Deployment. The type is defined in clause 5.5.3.14b of ETSI GS NFV-SOL 003 [11]. - -##### 5.2.6.3.19 Type: AffectedVirtualStorage - -This type represents information about added, deleted, modified or temporary virtualised storage resources of an NF Deployment. The type is defined in clause 5.5.3.15 of ETSI GS NFV-SOL 003 [11]. - -- The following attributes need not be supported: - - "resourceDefinitionId", which identifies resource definitions exchanged via the granting (see note 1). - -NOTE 1: Granting exchanges between DMS and SMO are not supported in the present document version. Refer also to the conditions described in clause 5.2.4.1. - -NOTE 2: Void. - -##### 5.2.6.3.20 Type: ResourceHandle - -This type represents information addressing a resource that is used by an NF Deployment instance. Information about the resource is available from underlying O-Cloud infrastructure resource managers part of the DMS. - -The type is defined in clause 4.4.1.7 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- The following attributes are further qualified as follows: - - "vimConnectionId", the attribute shall be supported since only direct-mode for resource management is supported, i.e., the part of the DMS exposing the present O2dms\_LifecycleDeployment interacts directly with the functions responsible for the infrastructure resource provisioning. -- The following attributes need not be present even when the conditions permit its presence: - - "resourceProviderId". - -##### 5.2.6.3.21 Type: AdditionalResourceInfo - -This type represents additional resource information that is resource and resource type specific and that is made available by the underlying infrastructure resource managers of the DMS. The type is defined in clause 4.4.1.16 of ETSI GS NFV-SOL 003 [11]. - -##### **5.2.6.3.22**      **Type: ExtVirtualLinkData** - -This type represents an external virtual link of an NF Deployment. The type is defined in clause 4.4.1.11 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- The following attributes are further qualified as follows: - - "vimConnectionId", the attribute shall be supported since only direct-mode for resource management is supported, i.e., the part of the DMS exposing the present O2dms\_LifecycleDeployment interacts directly with the functions responsible for the infrastructure resource provisioning. -- The following attributes need not be present even when the conditions permit its presence: - - "resourceProviderId". - -##### **5.2.6.3.23**      **Type: NetAttDefResourceData** - -This type represents a network attachment definition resource that specifies the interface to be used to connect one or multiple connections points to a secondary container cluster network that realizes a VL. The type is defined in clause 4.4.1.17 of ETSI GS NFV-SOL 003 [11]. - -##### **5.2.6.3.24**      **Type: NetAttDefResourceInfo** - -This type represents the information related to a network attachment definition resource providing the information about an interface that is used to connect one or multiple connections points to a secondary container cluster network. The type is defined in clause 5.5.3.28 of ETSI GS NFV-SOL 003 [11]. - -#### **5.2.6.4**      **Simple data types and enumerations** - -##### **5.2.6.4.1**      **Introduction** - -The present clause defines simple data types and enumerations that can be referenced from data structures defined in other clauses. The simple data types defined in a request body, response body, or a structure type are defined in ETSI GS NFV-SOL 013 [15] or the present clause of the specification. - -All the simple data types and enumerations specified in clause 5.5.4 of ETSI GS NFV-SOL 003 [11] shall be supported with the exception of those that are only used in REST resources and message contents of non-supported REST resources and methods, i.e., that are not listed in table 5.2.3-1. If specific provisions to simple data types and enumerations are considered with respect to the profiled API, these are specified in subsequent sub-clauses within clause 5.3.6.4 of the present document. In addition, all common simple data types and enumerations in clause 4.4.2 4.4.1 of ETSI GS NFV-SOL 003 [11] shall be supported if referenced/used by other data types as indicated above. - -##### **5.2.6.4.2**      **Simple data types** - -The simple data types defined in table 5.2.6.4.2-1 shall be supported. - -**Table 5.2.6.4.2-1: Simple data types** - -| Type name | Type definition | Description | -|--------------------------------------------------------------------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| IdentifierInVnfd | N/A | An identifier that is unique within a deployment descriptor of an NF Deployment. Representation: string of variable length. See note. | -| IdentifierInVim | N/A | An identifier maintained by the functions responsible for the infrastructure resource provisioning in the DMS. It is expected to be unique within a function responsible for the infrastructure resource provisioning. Representation: string of variable length. See note. | -| IdentifierInVnf | N/A | An identifier that is unique for the respective type within an NF Deployment instance, but that need not be globally unique. Representation: string of variable length. See note. | -| NOTE: See also definition in clause 4.4.2.2 of ETSI GS NFV-SOL 003 [11]. | | | - -##### **5.2.6.4.3 Enumeration: LcmOperationType** - -The enumeration is defined in clause 5.5.4.7 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- Only the following values shall be supported: INSTANTIATE, TERMINATE, SCALE, SCALE\_TO\_LEVEL, HEAL, CHANGE\_EXT\_CONN, CHANGE\_VNFPKG, and CHANGE\_FLAVOUR, as defined in table 5.5.4.7-1 of ETSI GS NFV-SOL 003 [11]. - -##### **5.2.6.4.4 Enumeration: CancelModeType** - -The enumeration is defined in clause 5.5.4.6 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following specific DMS applicability conditions are considered with respect to the referenced specification clause: - -- GRACEFUL: In the case the lifecycle management operation occurrence is in "STARTING" state, the DMS need not wait for a granting request - -NOTE: Granting exchanges between DMS and SMO are not supported in the present document version. Refer also to the conditions described in clause 5.2.4.1. - -#### **5.2.6.5 Other data types** - -##### **5.2.6.5.1 Introduction** - -The present clause defines data types that are not referenced explicitly by the O2dms\_LifecycleDeployment API but that are necessary for representing additional information to be considered by the orchestration procedures between the SMO and the DMS. - -##### **5.2.6.5.2 Type: ResourceDefinition** - -This type represents information about a resource that is expected to be used or is already associated to an NF Deployment. The type is defined in clause 9.5.3.2 of ETSI GS NFV-SOL 003 [11]. - -NOTE 1: The present type is not referenced by any of the other types and resource representations of the O2dms\_LifecycleDeployment API. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- The following attributes are further qualified as follows: - - "id", the identifier shall be unique within the scope of an NF Deployment and need not be unique within the scope of the referred "GrantRequest" structure. -- The following attributes need not be present even when the conditions permit its presence: - - "snapshotResDef". - -NOTE 2: Void. - -##### **5.2.6.5.3 Type: ResourcePlacement** - -This type represents information about the placement information and constraints for a resource that is expected to be used or is already associated to an NF Deployment. - -The data type shall comply with the provisions defined in table 5.2.6.5.3-1. - -**Table 5.2.6.5.3-1: Definition of ResourcePlacement data type** - -| Attribute name | Data type | Cardinality | Description | -|----------------------|------------|-------------|-----------------------------------------------------------------------------------------------| -| resourceDefinitionId | Identifier | 1 | Identifier of the related "ResourceDefinition" structure defining the resource to be managed. | - -| | | | | -|--------------------|-----------------|------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| vimConnectionId | Identifier | 0..1 | Identifier of the connection to the functions responsible for the infrastructure resource provisioning. Shall be present for new resources and shall be absent for resources that have already been allocated.
The applicable "VimConnectionInfo" structure, which is referenced by this attribute, can be obtained from the "vimConnectionInfo" attribute of the "Vnfnstance" structure. | -| zoneId | Identifier | 0..1 | Identifier of the resource zone, as managed by the O-Cloud resource management functions, into which the resource is to be placed. Shall be present for new resources and if the resource zones abstraction is applicable to them (e.g., for compute related resources). Shall be absent for resources that have already been allocated. | -| resourceGroupId | IdentifierInVim | 0..1 | Identifier of the "infrastructure resource group" to be provided when allocating the resource. The "infrastructure resource group" represents a logical grouping of O-Cloud resources assigned to a tenant. Shall be present for new resources.
Shall be absent for resources that have already been allocated. | -| containerNamespace | String | 0..1 | The value of the namespace in which the containerized workloads of an NF Deployment shall be deployed. Shall be present if the underlying resource are managed by functions responsible for the infrastructure resource provisioning equivalent to a CISM (e.g., a Kubernetes® cluster). | -| mcioConstraints | KeyValuePair | 0..N | The constraint values to be assigned to containerized workloads of an NF Deployment with containerized components.
The key in the key-value pair indicates the parameter name of the constraint in the declarative descriptor of the containerized workload and shall be one of the possible enumeration values of the "mcioConstraintsParams" attribute as specified in clause 7.1.6.2.2 of ETSI GS NFV-IFA 011 [12]. The value in the key-value pair indicates the value to be assigned to the constraint. Shall be present if the underlying resource are managed by functions responsible for the infrastructure resource provisioning equivalent to a CISM (e.g., a Kubernetes® cluster). | - -##### 5.2.6.5.4 Type: ResourcePlacementConstraint - -This type represents information about the placement constraints between two or more resources of an NF Deployment. - -The data type shall comply with the provisions defined in table 5.2.6.5.4-1. - -**Table 5.2.6.5.4-1: Definition of ResourcePlacementConstraint data type** - -| Attribute name | Data type | Cardinality | Description | -|------------------------|----------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| affinityOrAntiAffinity | Enum (inlined) | 1 | The type of constraint.

Permitted values:
- AFFINITY
- ANTI_AFFINITY | -| scope | Enum (inlined) | 1 | The scope of the resource placement constraint indicating the category of the scope where the constraint applies.

Permitted values:
- NFVI_POP: it represents the scope of a O-Cloud Site.
- ZONE: it represents the scope of a resource zone in an O-Cloud Site.
- NFVI_NODE: it represents the scope of an O-Cloud Node for VM-based deployments.
- CIS_NODE: it represents the scope of a CIS cluster node, i.e., an O-Cloud Node in an O-Cloud Node Cluster for container-based deployments.
- CONTAINER_NAMESPACE: it represents the scope of a container namespace. | - -| | | | | -|-------------|---------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | See note. | -| resource | Structure (inlined) | 2..N | The resources that are involved in the constraint rule. | -| >idType | Enum (inlined) | 1 | The type of the identifier.

Permitted values:
- RES_MGMT: it represents a resource management level identifier, i.e., an identifier as known/exposed by the functions responsible for the infrastructure management provisioning.
- RES_DEFINITION: it represents an identifier of the "ResourceDefinition" structure. | -| >resourceId | Identifier | 1 | The value of the resource identifier within the scope indicated by the "idType" attribute. | - -NOTE: The "CIS\_NODE" and "CONTAINER\_NAMESPACE" scopes shall only be used to express affinity or anti-affinity relationship between containerized workloads. - -##### 5.2.6.5.5 Type: CloudAssets - -This type represents information about O-Cloud assets that can be used or be associated to an NF Deployment. - -The data type shall comply with the provisions defined in table 5.2.6.5.5-1. - -**Table 5.2.6.5.5-1: Definition of CloudAssets data type** - -| Attribute name | Data type | Cardinality | Description | -|-------------------------|---------------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| computeResourceFlavours | VimComputeResourceFlavour | 0..N | Mappings between virtual compute descriptors defined in the NF Deployment descriptor and compute resource flavours managed in the O-Cloud functions responsible for virtualised infrastructure management. | -| softwareImages | VimSoftwareImage | 0..N | Mappings between software images defined in the NF Deployment descriptor and software images managed in the O-Cloud functions responsible for serving as software image repository. | -| storageAssets | StorageAsset | 0..N | Mappings between virtual storages defined in the NF Deployment descriptor and virtual storages managed in the O-Cloud. | -| paasAssets | PaasAsset | 0..N | Mappings between PaaS Services requests defined in the NF Deployment descriptor and PaaS Services managed in the O-Cloud. | - -##### 5.2.6.5.6 Type: VimComputeResourceFlavour - -This type defines the mapping between a virtual compute descriptor and the corresponding compute resource flavour managed by the O-Cloud functions responsible for virtualised infrastructure management. - -The type is defined in clause 9.5.3.9 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- The following attributes are further qualified as follows: - - "vimConnectionId", the attribute shall be supported since only direct-mode for resource management is supported, i.e., the part of the DMS exposing the present O2dms\_LifecycleDeployment service API interacts directly with the functions responsible for the infrastructure resource provisioning. -- The following attributes need not be present even when the conditions permit its presence: - - "resourceProviderId". - -##### **5.2.6.5.7 Type: VimSoftwareImage** - -This type defines the mapping between a software image definition in the descriptor of the NF Deployment and the corresponding software image managed by the O-Cloud functions performing the serving as image repository and managing the software images. - -The type is defined in clause 9.5.3.10 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- The following attributes are further qualified as follows: - - "vimConnectionId", the attribute shall be supported since only direct-mode for resource management is supported, i.e., the part of the DMS exposing the present O2dms\_LifecycleDeployment service API interacts directly with the functions responsible for the infrastructure resource provisioning. -- The following attributes need not be present even when the conditions permit its presence: - - "resourceProviderId". - -##### **5.2.6.5.8 Type: StorageAsset** - -This type defines the mapping between a virtual storage description in the NF Deployment descriptor and the corresponding virtual storage managed in the O-Cloud. - -The type is defined in clause 9.5.3.13 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following DMS applicability conditions are considered with respect to the referenced specification clause: - -- The following attributes are further qualified as follows: - - "vimConnectionId", the attribute shall be supported since only direct-mode for resource management is supported, i.e., the part of the DMS exposing the present O2dms\_LifecycleDeployment service API interacts directly with the functions responsible for the infrastructure resource provisioning. -- The following attributes need not be present even when the conditions permit its presence: - - "resourceProviderId". - -##### **5.2.6.5.9 Type: PaasAsset** - -This type defines the mapping between a PaaS service request in the NF Deployment descriptor (i.e., the VNFD) and the assigned PaaS Service provided by the O-Cloud. - -The type is defined as a structure inlined in clause 9.5.2.3 of ETSI GS NFV-SOL 003 [11], and also represented in the following table 5.2.6.5.9-1. - -**Table 5.2.6.5.9-1: Definition of PaasAsset data type** - -| Attribute name | Data type | Cardinality | Description | -|----------------------|-------------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| paasServiceType | String | 1 | The type of PaaS Service. The value of this attribute is expected to be matched against values of the registered PaaS Services in the PaaS Services Repository function. | -| paasServiceId | Identifier | 1 | Identifier of the assigned PaaS Service as managed by the PaaS Services Management function. | -| paasServiceVersion | Version | 0..1 | Version of the PaaS Service. It shall be present if the PaaS Service is versioned. | -| paasServiceRequestId | IdentifierInVnfd | 1 | Identifier of the PaaS Service request in the Deployment Descriptor that maps to the assigned PaaS Service. | -| paasServiceHandle | PaasServiceHandle | 1 | A handle enabling the access and use of the PaaS Service by the NF Deployment. | - -### 5.2.7 Error handling - -#### 5.2.7.1 General - -For the O2dms\_DeploymentLifecycle Service API, HTTP error responses shall be supported as specified in clause 5.1.5. - -#### 5.2.7.2 Error handling in NF Deployment lifecycle procedures - -##### 5.2.7.2.1 Introduction - -Clause 5.6.1 in ETSI GS NFV-SOL 003 [11] describes basic concepts for error handling to be considered during lifecycle management operation occurrences. The same clause also describes what are common failure resolution strategies and the concepts of retry and rollback of lifecycle management operations. In the descriptions, references to the NFV-MANO functional blocks are provided (e.g., NFVO and VNFM), while in the present profile document, the corresponding O-RAN framework elements are to be considered instead according to the mappings in clause 4.3.2 and the specification in clause 5.2.4.1. - -##### 5.2.7.2.2 States and state transitions of lifecycle management operation occurrences of NF Deployments - -The state and state transition of lifecycle management operation occurrences of NF Deployments shall be supported by the DMS according to the provisions in clause 5.6.2 of ETSI GS NFV-SOL 003 [11], with the following additional DMS applicability conditions with respect to the referenced specification clause: - -- The provisions and descriptions related to "obtaining the grant" need not be supported. - -NOTE: Granting exchanges between DMS and SMO are not supported in the present document version. Refer also to the conditions described in clause 5.2.4.1. - -Based on the above, specific states as supported by the present document version have the following characteristics. - -###### A) about states: - -- STARTING: - - \* The VNF lifecycle management operation occurrence of the NF Deployment shall transit into the PROCESSING state once the DMS has checked that a) resources management fulfillment information (without performing a granting exchange), b) placement information, and c) deployment items of the NF Deployment are available to the DMS. The items a), b) and c) in the previous listing are hereafter referred as "NF Deployment lifecycle items" - - \* If an error occurs during the checking steps, or the DMS does not have the necessary information to proceed with the infrastructure resources fulfillment for the NF Deployment, the lifecycle management operation occurrence of the NF Deployment shall transit into the "ROLLED\_BACK" state. -- FAILED\_TEMP: - - \* If "NF Deployment lifecycle items" for the lifecycle operation were available, these are still valid. - -###### B) about error handling operations: - -- Retry: - - \* The "Retry" shall operate within the bounds of the "NF Deployment lifecycle items" information available to the DMS. -- Rollback: - - \* The "Rollback" shall operate within the bounds of the "NF Deployment lifecycle items" information available to the DMS. - -##### 5.2.7.2.3 Specific cases of error handling - -###### 5.2.7.2.3.1 Immediate failure - -The description and provisions for the DMS to handle an immediate failure is provided in clause 5.6.3.1 of ETSI GS NFV-SOL 003 [11]. - -###### 5.2.7.2.3.2 Failure in "STARTING" state - -The description and provisions for the DMS to handle a failure in "STARTING" state is provided in clause 5.6.3.2 of ETSI GS NFV-SOL 003 [11]. The following additional DMS applicability conditions with respect to the referenced specification clause apply: - -- The provisions and descriptions related to "obtaining the grant" need not be supported, so if the operation fails before the DMS has the necessary "NF Deployment lifecycle items" information, no persistent change to the state of the NF Deployment has happened. - -NOTE: Granting exchanges between DMS and SMO are not supported in the present document version. Refer also to the conditions described in clause 5.2.4.1. - -###### 5.2.7.2.3.3 Failure during the LCM operation execution - -The description and provisions for the DMS to handle during the execution of the LCM operation is provided in clause 5.6.3.3 of ETSI GS NFV-SOL 003 [11]. The following additional DMS applicability conditions with respect to the referenced specification clause apply: - -- The provisions and descriptions related to "obtaining the grant" need not be supported. - -NOTE: Granting exchanges between DMS and SMO are not supported in the present document version. Refer also to the conditions described in clause 5.2.4.1. - -###### 5.2.7.2.3.4 Cancellation of LCM operation execution - -The description and provisions for the DMS to handle during the cancellation of an LCM operation is provided in clause 5.6.3.4 of ETSI GS NFV-SOL 003 [11]. The following additional DMS applicability conditions with respect to the referenced specification clause apply: - -- The provisions and descriptions related to "obtaining the grant" need not be supported. - -NOTE: Granting exchanges between DMS and SMO are not supported in the present document version. Refer also to the conditions described in clause 5.2.4.1. - -#### 5.2.7.3 Flows of erroring handling lifecycle management operation occurrences of NF Deployments - -##### 5.2.7.3.1 Overview - -Clause 3.2.7.b defines and references to flows about error handling of lifecycle management operation occurrences of NF Deployments. In the description, references to already documented flows in ETSI GS NFV-SOL 003 [11] is provided, with the consideration of the mapping meanings of NFVO and VNFM to the O-RAN framework as specified in clause 5.2.4.1 of the present document. - -##### 5.2.7.3.2 Flow of retrying a lifecycle management operation occurrence of an NF Deployment - -Clause 5.3.10 in ETSI GS NFV-SOL 003 [11] describes the flow of retrying a VNF lifecycle management operation, which is also applicable in the case of lifecycle management operations on an NF Deployment. - -##### **5.2.7.3.3 Flow of rolling back a lifecycle management operation occurrence of an NF Deployment** - -Clause 5.3.11 in ETSI GS NFV-SOL 003 [11] describes the flow of rolling back a VNF lifecycle management operation, which is also applicable in the case of lifecycle management operations on an NF Deployment. - -##### **5.2.7.3.4 Flow of failing a lifecycle management operation occurrence of an NF Deployment** - -Clause 5.3.12 in ETSI GS NFV-SOL 003 [11] describes the flow of failing a VNF lifecycle management operation, which is also applicable in the case of lifecycle management operations on an NF Deployment. - -##### **5.2.7.3.5 Flow of cancelling a lifecycle management operation occurrence of an NF Deployment** - -Clause 5.3.13 in ETSI GS NFV-SOL 003 [11] describes the flow of cancelling a VNF lifecycle management operation, which is also applicable in the case of lifecycle management operations on an NF Deployment. - -## 5.3 O2dms\_DeploymentFault Service API - -### 5.3.1 Description - -This service interface enables an API consumer (e.g., the SMO) to invoke fault management operations of NF Deployments towards the DMS. The service interface also enables the management of subscriptions to notifications raised by the DMS regarding the fault management of the NF Deployments. - -### 5.3.2 API version - -For the O2dms\_DeploymentFault Service API version as specified in the present document, the MAJOR version field shall be "1", the MINOR version field shall be "14", and the PATCH version field shall be "0" as specified in clause 7.1a of ETSI GS NFV-SOL 003 [11]. Consequently, the {apiMajorVersion} URI variable shall be set to "v1". - -### 5.3.3 REST resources structure and methods - -All resource URIs of the API shall use the base URI specified defined in clause 5.1.2. The string "vnffm" shall be used to represent {apiName} as defined in clause 7.2 of ETSI GS NFV-SOL 003 [11]. All resource URIs in clauses below are defined relative to the formed based URI (i.e., {apiRoot}/xyz/{apiVersion}). - -When ambiguity is possible, the term REST resource is used to make the distinction between the term resource as understood within the context of REST API from the term resource as understood within the context of O-RAN. - -The resource URI structure defined for the O2dms\_DeploymentFault Service API shall be as specified in clause 7.2 of ETSI GS NFV-SOL 003 [11]. Applicable individual REST resources for the present version of the O2dms\_DeploymentFault Service API are listed in table 5.3.3-1. - -Figure 5.3.3-1 illustrates the overall resource URI structure defined for the O2dms\_DeploymentFault Service API. - -![A hierarchical tree diagram showing the resource URI structure. The root is {apiRoot}/vnffm/{apiMajorVersion}. It branches into /alarms and /subscriptions. /alarms further branches into/{alarmId}. /subscriptions further branches into/{subscriptionId}.](b4fb54e441be8184578e6a7372c90ec6_img.jpg) - -``` - - {apiRoot}/vnffm/{apiMajorVersion} - ├── /alarms - │ └── /{alarmId} - └── /subscriptions - └── /{subscriptionId} - -``` - -A hierarchical tree diagram showing the resource URI structure. The root is {apiRoot}/vnffm/{apiMajorVersion}. It branches into /alarms and /subscriptions. /alarms further branches into/{alarmId}. /subscriptions further branches into/{subscriptionId}. - -**Figure 5.3.3-1: Resource URI structure of the O2dms\_DeploymentFault Service API** - -Table 5.3.3-1 lists the individual REST resources defined and the applicable HTTP methods. The DMS shall support responding to requests for all HTTP methods on the resources in table 5.3.3-1 that are marked as "M" (mandatory) in the "Cat" column. - -**Table 5.3.3-1: Resources and methods overview** - -| Resource name | Resource URI | HTTP method | Cat | Description (see note 2) | -|-------------------------|------------------------------------------------|-------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------| -| Alarms | /alarms
See note 1. | GET | M | Query multiple alarms related to NF Deployments. | -| Individual alarm | /alarms/{alarmId}
See note 1. | GET | M | Read an individual alarm related to an NF Deployment. | -| | | PATCH | M | Modify information of an individual alarm related to an NF Deployment. | -| Subscriptions | /subscriptions
See note 1. | POST | M | Subscribe to fault management notifications related to NF Deployments. | -| | | GET | M | Query information about multiple subscriptions to NF Deployment fault management notifications. | -| Individual subscription | /subscriptions/{subscriptionId}
See note 1. | GET | M | Read an "Individual subscription" resource which represents information about a subscription to NF Deployment fault management notifications. | -| | | DELETE | M | Terminate a subscription to NF Deployment fault management notifications. | -| Notification endpoint | (provided by API consumer)
See note 1. | POST | See note 3 | Notify about NF Deployment fault management events. | -| | | GET | See note 3 | Test the notification endpoint for NF Deployment fault management events. | - -NOTE 1: The resource URI value is the same as the one specified in ETSI GS NFV-SOL 003 [11]. - -NOTE 2: The specified meaning of the resource name and supported HTTP method in ETSI GS NFV-SOL 003 [11] applies, unless otherwise stated. Additional description can be presented in case of further refining its meaning in the context of O2dms specification. - -NOTE 3: The DMS shall support invoking the HTTP methods defined for the "Notification endpoint" resource exposed by the API consumer. If the API consumer supports invoking the POST method on the "Subscriptions" resource towards the DMS, it shall also support responding to the HTTP requests defined for the "Notification endpoint" resource. - -### 5.3.4 REST resources - -#### 5.3.4.1 General - -The DMS and API consumer of the O2dms\_DeploymentFault Service API shall support all the provisions specified in clause 7.4 of ETSI GS NFV-SOL 003 [11], with the following considerations: - -- NFVO and VNFM entities referred in the ETSI GS NFV-SOL 003 [11] are mapped to SMO and DMS as defined in clause 4.3.2 of the present document. Concerning to the managed object types to which alarms can be associated/related to, VNF instance is mapped to NF Deployment, as also defined in clause 5.3.2 of the present document. -- Only the provisions associated to corresponding REST resources and methods listed in table 5.3.3-1 are applicable for the present document. That is, if a REST resource and method is not listed in table 5.3.3-1 of the present document, the corresponding clause in the ETSI GS NFV-SOL 003 [11] that specifies such REST resource, and its supported methods, is not required to be supported according to the present document version. If specific provisions to REST resources are considered with respect to the profiled API, these are specified in subsequent sub-clauses within clause 5.3.4 of the present document. - -- For the list of referenced data types for notifications to support, these are defined in clause 5.3.5 of the present document. -- For the list of REST resource data types, structured data types and referenced simple types to be supported, refer to clauses 5.3.6.1, 5.3.6.2, 5.3.6.3 and 5.3.6.4 of the present document. - -### 5.3.5 Notifications - -#### 5.3.5.1 General - -Notifications issued on the O2dms\_DeploymentFault Service API shall comply with the Subscribe/Notify pattern as described in clause 5.9 of ETSI GS NFV-SOL 015 [17]. - -Table 5.3.5.1-1 provides an overview of the notifications supported by the present API. - -**Table 5.3.5.1-1: O2dms\_DeploymentFault notifications overview** - -| Data type | Clause defined | Description | -|------------------------------|-------------------------------------|-----------------------------------------------------------------------------------------------------| -| AlarmNotification | 7.5.2.5 of ETSI GS NFV-SOL 003 [11] | This type represents an alarm notification about NF Deployment faults. | -| AlarmClearedNotification | 7.5.2.6 of ETSI GS NFV-SOL 003 [11] | This type represents an alarm cleared notification about NF Deployment faults. | -| AlarmListRebuiltNotification | 7.5.2.7 of ETSI GS NFV-SOL 003 [11] | This type represents a notification that the alarm list related to NF Deployments has been rebuilt. | - -### 5.3.6 Data model - -#### 5.3.6.1 REST resource data types - -This clause specifies the data types used in resource representations and that shall be supported by the present API. - -Table 5.3.6.1-1 lists the data types. - -**Table 5.3.6.1-1: O2dms\_DeploymentFault resource data types** - -| Data type | Clause defined | Description | -|----------------|-------------------------------------|-------------------------------------------------------------------------------------------------------------| -| Alarm | 5.3.6.2.2 | This type represents an alarm associated to an NF Deployment. | -| FmSubscription | 7.5.2.3 of ETSI GS NFV-SOL 003 [11] | This type represents a subscription related to notifications related to fault management of NF Deployments. | - -#### 5.3.6.2 Structured data types - -##### 5.3.6.2.1 Introduction - -This clause defines the structured data types to be used in resource representations. - -All the structured data types specified in clause 7.5.2 of ETSI GS NFV-SOL 003 [11] shall be supported. If specific provisions to structured data types are considered with respect to the profiled API, these are specified in subsequent sub-clauses within clause 5.3.6.2 of the present document. - -##### 5.3.6.2.2 Type: Alarm - -The "Alarm" type encapsulates the information about an alarm associated to an NF Deployment instance. The type is defined in clause 7.5.2.4 of ETSI GS NFV-SOL 003 [11]. - -In addition, the following O-Cloud applicability conditions and clarifications are considered with respect to the referenced specification clause: - -- For attributes name descriptions referring to NFVI, in the context of the present profiling specification, NFVI concerns to O-Cloud. - -#### 5.3.6.3 Referenced structured data types - -##### 5.3.6.3.1 Introduction - -This clause defines the structured data types that are referenced by other data types. - -All the referenced structured data types specified in clause 7.5.3 of ETSI GS NFV-SOL 003 [11] shall be supported. If specific provisions to referenced structured data types are considered with respect to the profiled API, these are specified in subsequent sub-clauses within clause 5.3.6.3 of the present document. In addition, all common structured data types in clause 4.4.1 of ETSI GS NFV-SOL 003 [11] shall be supported if referenced/used by other data types as indicated above. - -#### 5.3.6.4 Simple data types and enumerations - -##### 5.3.6.4.1 Introduction - -The present clause defines simple data types and enumerations that can be referenced from data structures defined in other clauses. The simple data types defined in a request body, response body, or a structure type are defined in ETSI GS NFV-SOL 013 [15] or the present clause of the specification. - -All the simple data types and enumerations specified in clause 7.5.4 of ETSI GS NFV-SOL 003 [11] shall be supported. If specific provisions to simple data types and enumerations are considered with respect to the profiled API, these are specified in subsequent sub-clauses within clause 5.3.6.4 of the present document. In addition, all common simple data types and enumerations in clause 4.4.2 4.4.1 of ETSI GS NFV-SOL 003 [11] shall be supported if referenced/used by other data types as indicated above. - -#### 5.3.6.5 Other data types - -##### 5.3.6.5.1 Introduction - -The present clause defines other data types necessary for representing information to be considered by the orchestration procedures between the SMO and the DMS. - -No particular other data type is defined currently for the present API. - -## 5.4 O2dms\_DeploymentPerformance Service API - -### 5.4.1 Description - -This service interface enables an API consumer (e.g., the SMO) to invoke performance management operations of NF Deployments towards the DMS. The service interface also enables the management of subscriptions to notifications raised by the DMS regarding the performance management of the NF Deployments via the management of PM jobs and Threshold. - -### 5.4.2 API version - -For the O2dms\_DeploymentPerformance Service API version as specified in the present document, the MAJOR version field shall be "2", the MINOR version field shall be "13", and the PATCH version field shall be "0" as specified in clause 6.1a of ETSI GS NFV-SOL 003 [11]. Consequently, the {apiMajorVersion} URI variable shall be set to "v2". - -### 5.4.3 REST resources structure and methods - -All resource URIs of the API shall use the base URI specified defined in clause 5.1.2. The string "vnfpm" shall be used to represent {apiName} as defined in clause 6.2 of ETSI GS NFV-SOL 003 [11]. All resource URIs in clauses below are defined relative to the formed based URI (i.e., {apiRoot}/xyz/{apiVersion}). - -When ambiguity is possible, the term REST resource is used to make the distinction between the term resource as understood within the context of REST API from the term resource as understood within the context of the O-Cloud. - -The resource URI structure defined for the O2dms\_DeploymentPerformance Service API shall be as specified in clause 6.2 of ETSI GS NFV-SOL 003 [11]. Applicable individual REST resources for the present version of the O2dms\_DeploymentPerformance Service API are listed in table 5.4.3-1. - -Figure 5.4.3-1 illustrates the overall resource URI structure defined for the O2dms\_DeploymentPerformance Service API. - -![A hierarchical tree diagram showing the resource URI structure. The root is {apiRoot}/vnfpm/{apiMajorVersion}. It branches into /pm_jobs and /thresholds. /pm_jobs branches into /{pmJobId}, which further branches into /reports, which then branches into /{reportId}. /thresholds branches into /{thresholdId}.](e1ce114c43dcefce51eadcd12f2da6d2_img.jpg) - -``` - - {apiRoot}/vnfpm/{apiMajorVersion} - ├── /pm_jobs - │ └── /{pmJobId} - │ └── /reports - │ └── /{reportId} - └── /thresholds - └── /{thresholdId} - -``` - -A hierarchical tree diagram showing the resource URI structure. The root is {apiRoot}/vnfpm/{apiMajorVersion}. It branches into /pm\_jobs and /thresholds. /pm\_jobs branches into /{pmJobId}, which further branches into /reports, which then branches into /{reportId}. /thresholds branches into /{thresholdId}. - -**Figure 5.4.3-1: Resource URI structure of the O2dms\_DeploymentPerformance Service API** - -Table 5.4.3-1 lists the individual REST resources defined and the applicable HTTP methods. The DMS shall support responding to requests for all HTTP methods on the resources in table 5.4.3-1 that are marked as "M" (mandatory) in the "Cat" column. - -**Table 5.4.3-1: Resources and methods overview** - -| Resource name | Resource URI | HTTP method | Cat | Description (see note 2) | -|-------------------------------|---------------------------------------|-------------|------------|---------------------------------------------------------------------------------| -| PM jobs | /pm_jobs | POST | M | Create a PM job related to NF Deployments. | -| | See note 1. | GET | M | Query multiple PM jobs related to NF Deployments. | -| Individual PM job | /pm_jobs/{pmJobId} | GET | M | Read an individual PM job related to NF Deployments. | -| | See note 1. | PATCH | M | Update an individual PM job related to NF Deployments. | -| | | DELETE | M | Delete an individual PM job related to NF Deployments. | -| Individual performance report | /pm_jobs/{pmJobId}/reports/{reportId} | GET | M | Read an individual performance report related to NF Deployments. | -| Thresholds | /thresholds | POST | M | Create a threshold related to NF Deployments. | -| | See note 1. | GET | M | Query multiple thresholds related to NF Deployments. | -| Individual threshold | /thresholds/{thresholdId} | GET | M | Read an individual threshold related to NF Deployments. | -| | See note 1. | PATCH | M | Update an individual threshold related to NF Deployments. | -| | | DELETE | M | Delete an individual threshold related to NF Deployments. | -| Notification endpoint | (provided by API consumer) | POST | See note 3 | Notify about NF Deployment performance management events. | -| | See note 1. | GET | See note 3 | Test the notification endpoint for NF Deployment performance management events. | - -NOTE 1: The resource URI value is the same as the one specified in ETSI GS NFV-SOL 003 [11]. - -NOTE 2: The specified meaning of the resource name and supported HTTP method in ETSI GS NFV-SOL 003 [11] applies, unless otherwise stated. Additional description can be presented in case of further refining its meaning in the context of O2dms specification. - -NOTE 3: The DMS shall support invoking the HTTP methods defined for the "Notification endpoint" resource exposed by the API consumer. If the API consumer supports invoking the POST method on the "PM jobs" or "Thresholds" resource towards the DMS, it shall also support responding to the HTTP requests defined for the "Notification endpoint" resource. - -### 5.4.4 REST resources - -#### 5.4.4.1 General - -The DMS and API consumer of the O2dms\_DeploymentPerformance Service API shall support all the provisions specified in clause 6.4 of ETSI GS NFV-SOL 003 [11], with the following considerations: - -- NFVO and VNFM entities referred in the ETSI GS NFV-SOL 003 [11] are mapped to SMO and DMS as defined in clause 4.3.2 of the present document. Concerning to the managed object types to which performance monitoring elements (e.g., PM jobs and thresholds) can be associated/related to, VNF instance is mapped to NF Deployment, as also defined in clause 4.3.2 of the present document. -- Only the provisions associated to corresponding REST resources and methods listed in table 5.4.3-1 are applicable for the present document. That is, if a REST resource and method is not listed in table 5.4.3-1 of the present document, the corresponding clause in the ETSI GS NFV-SOL 003 [11] that specifies such REST resource, and its supported methods, is not required to be supported according to the present document version. If specific provisions to REST resources are considered with respect to the profiled API, these are specified in subsequent sub-clauses within clause 5.4.4 of the present document. -- For the list of referenced data types for notifications to support, these are defined in clause 5.4.5 of the present document. -- For the list of REST resource data types, structured data types and referenced simple types to be supported, refer to clauses 5.4.6.1, 5.4.6.2, 5.4.6.3 and 5.4.6.4 of the present document. - -### 5.4.5 Notifications - -#### 5.4.5.1 General - -Notifications issued on the O2dms\_DeploymentPerformance Service API shall comply with the Subscribe/Notify pattern as described in clause 5.9 of ETSI GS NFV-SOL 015 [17]. - -Table 5.4.5.1-1 provides an overview of the notifications supported by the present API. - -**Table 5.4.5.1-1: O2dms\_DeploymentPerformance notifications overview** - -| Data type | Clause defined | Description | -|---------------------------------------------|-------------------------------------|----------------------------------------------------------------------------------------------------------------------| -| ThresholdCrossedNotification | 6.5.2.4 of ETSI GS NFV-SOL 003 [11] | This type represents a notification of a crossed threshold associated to an NF Deployment. | -| PerformanceInformationAvailableNotification | 6.5.2.5 of ETSI GS NFV-SOL 003 [11] | This type represents a notification indicating that the performance information (a performance report) is available. | - -### 5.4.6 Data model - -#### 5.4.6.1 REST resource data types - -This clause specifies the data types used in resource representations and that shall be supported by the present API. - -Table 5.4.6.1-1 lists the data types. - -**Table 5.4.6.1-1: O2dms\_DeploymentFault resource data types** - -| Data type | Clause defined | Description | -|-------------------|--------------------------------------|------------------------------------------------------------------------------------------| -| PmJob | 6.5.2.7 of ETSI GS NFV-SOL 003 [11] | This type represents a PM job associated to NF Deployments. | -| Threshold | 6.5.2.9 of ETSI GS NFV-SOL 003 [11] | This type represents a threshold. | -| PerformanceReport | 6.5.2.10 of ETSI GS NFV-SOL 003 [11] | This type represents a performance report of measurements collected as part of a PM job. | - -#### 5.4.6.2 Structured data types - -##### 5.4.6.2.1 Introduction - -This clause defines the structured data types to be used in resource representations. - -All the structured data types specified in clause 6.5.2 of ETSI GS NFV-SOL 003 [11] shall be supported. If specific provisions to structured data types are considered with respect to the profiled API, these are specified in subsequent sub-clauses within clause 5.4.6.2 of the present document. - -#### 5.4.6.3 Referenced structured data types - -##### 5.4.6.3.1 Introduction - -This clause defines the structured data types that are referenced by other data types. - -All the referenced structured data types specified in clause 6.5.3 of ETSI GS NFV-SOL 003 [11] shall be supported. If specific provisions to referenced structured data types are considered with respect to the profiled API, these are specified in subsequent sub-clauses within clause 5.4.6.3 of the present document. In addition, all common structured data types in clause 4.4.1 of ETSI GS NFV-SOL 003 [11] shall be supported if referenced/used by other data types as indicated above. - -#### 5.4.6.4 Simple data types and enumerations - -##### 5.4.6.4.1 Introduction - -The present clause defines simple data types and enumerations that can be referenced from data structures defined in other clauses. The simple data types defined in a request body, response body, or a structure type are defined in ETSI GS NFV-SOL 013 [15] or the present clause of the specification. - -All the simple data types and enumerations specified in clause 6.5.4 of ETSI GS NFV-SOL 003 [11] shall be supported. If specific provisions to simple data types and enumerations are considered with respect to the profiled API, these are specified in subsequent sub-clauses within clause 5.4.6.4 of the present document. In addition, all common simple data types and enumerations in clause 4.4.2 4.4.1 of ETSI GS NFV-SOL 003 [11] shall be supported if referenced/used by other data types as indicated above. - -#### 5.4.6.5 Other data types - -##### 5.4.6.5.1 Introduction - -The present clause defines other data types necessary for representing information to be considered by the orchestration procedures between the SMO and the DMS. - -No particular other data types are defined currently for the present API. - -# Annex A (Informative): Examples - -## A.1 Overview - -Annex A describes examples of usage of the O2dms ETSI NFV profile on various aspects. - -## A.2 AAL examples - -### A.2.1 Example #1: Definition of acceleration capability requirements in NF Deployment descriptors - -The following example illustrates how the NF Deployment descriptor based on ETSI NFV's VNFD, in particular based on TOSCA according to ETSI GS NFV-SOL 001 [10], can declare acceleration requirements for a VM-based NF Deployment unit by leveraging the definition of the requested additional capabilities. The example describes the use of the requested additional capabilities and the reference to AAL-related key-value. - -NOTE 1: The example is not meant to be accurate in terms of necessary AAL parameterization (e.g., the requested capability name, values of "requested\_additional\_capability\_name", version parameters, "profile\_type" and "other\_profile\_params" in the example are just indicative) and its purpose is only to indicate the "placeholder" for such information in the VNFD. The example can be revisited in future versions of the present document based on the progress made in referenced O-RAN WG6 AAL specifications. - -NOTE 2: The example only focuses on specific parts of the NF Deployment descriptors. - -``` -tosca_definitions_version: tosca_simple_yaml_1_3 -description: Template of an NF Deployment example with acceleration requirements -imports: - - etsi_nfv_sol001_vnfd_types.yaml # all of TOSCA VNFD types as defined in ETSI - GS NFV-SOL 001 - -node_types: - MyExample.OranNF.1_0: - derived_from: tosca.nodes.nfv.VNF - ... - -topology_template: - substitution_mappings: - node_type: MyExample.OranNF.1_0 - requirements: - ... - -node_templates: - OranNF: - type: MyExample.OranNF.1_0 - properties: - ... - interfaces: - ... - - NfDeploymentUnitExample: - type: tosca.nodes.nfv.Vdu.Compute - properties: - ... - capabilities: - virtual_compute: - properties: -``` - -``` - -... -requested_additional_capabilities: - aal_profile_fec: - requested_additional_capability_name: "AAL-FEC" - support_mandatory: true - min_requested_additional_capability_version: "1" - preferred_requested_additional_capability_version: "1" - target_performance_parameters: - profile_type: "AAL-FEC" - other_profile_params: "values" - aal_profile_downlink_high_phy: - requested_additional_capability_name: "AAL-DOWNLINK-High-PHY" - support_mandatory: true - min_requested_additional_capability_version: "1" - preferred_requested_additional_capability_version: "2" - target_performance_parameters: - profile_type: "AAL-DOWNLINK-High-PHY" - other_profile_params: "values" - aal_profile_uplink_high_phy: - requested_additional_capability_name: "AAL-UPLINK-High-PHY" - support_mandatory: true - min_requested_additional_capability_version: "1" - preferred_requested_additional_capability_version: "2" - target_performance_parameters: - profile_type: "AAL-UPLINK-High-PHY" - other_profile_params: "values" - -``` - -In the example above: - -- In red, the modelling concerns only to the choice of TOSCA as NF Deployment descriptor according to ETSI GS NFV-SOL 001 [10] and does not concern to modelling of AAL information or requirements. In other words, the red parts show how the NF designer models the capability within the descriptor by following the ETSI GS NFV-SOL 001 [10] specification. -- In blue, the modelling concerns to AAL and what is (expected) to be specified by O-RAN. The O-Cloud is expected to be provisioned with such a capability in order for the NF Deployment to be successful. The values here are only an example. The possible values and parameters names ("profile\_type", version number, "other\_profile\_params") are assumed to be referenced from O-RAN specification. -- In black, these are other parts that do not concern specifically to AAL and are only depicted for completeness of the example. - -### A.2.2 Example #2: Definition of acceleration related configuration in NF Deployment descriptors and exchange of information on the O2dms interfaces - -The following example illustrates how the NF Deployment descriptor based on ETSI NFV's VNFD, in particular based on TOSCA according to ETSI GS NFV-SOL 001 [10], can declare configurable properties that can be used for providing runtime configuration information into boot data to be injected into a VM-based NF Deployment unit. - -NOTE 1: The example is not meant to be accurate in terms of necessary AAL parameterization and its purpose is only to indicate the "placeholder" for such information in the VNFD. The example can be revisited in future versions of the present document based on the progress made in referenced O-RAN WG6 AAL specifications. - -NOTE 2: The example only focuses on specific parts of the NF Deployment descriptors. - -``` - -tosca_definitions_version: tosca_simple_yaml_1_3 -description: Template of an NF Deployment example with acceleration requirements - -``` - -``` - -imports: - - etsi_nfv_sol001_vnfd_types.yaml # all of TOSCA VNFD types as defined in ETSI - GS NFV-SOL 001 - -data_types: - MyExample.datatypes.nfv.VnfInstantiateAdditionalParameters: - derived_from: tosca.datatypes.nfv.VnfOperationAdditionalParameters - properties: - aal_param_01: - type: string - required: true - default: value_1 - aal_param_02: - type: string - required: true - default: value_2 - MyExample.datatypes.nfv.VnfConfigurableProperties: - derived_from: tosca.datatypes.nfv.VnfConfigurableProperties - properties: - additional_vnf_configurable_properties: - type: MyExample.datatypes.nfv.AdditionalVnfConfigurableProperties - required: true - - MyExample.datatypes.nfv.AdditionalVnfConfigurableProperties - derived_from: tosca.datatypes.nfv.VnfAdditionalConfigurableProperties - properties: - aal_param_03: - type: string - required: true - default: value_3 - -node_types: - MyExample.OranNF.1_0: - derived_from: tosca.nodes.nfv.VNF - properties: - ... - configurable_properties: - type: MyExample.datatypes.nfv.VnfConfigurableProperties - interfaces: - Vnflcm: - type: tosca.interfaces.nfv.Vnflcm - operations: - instantiate: - inputs: - additional_parameters: - type: MyExample.datatypes.nfv.VnfInstantiateAdditionalParameters - required: false - -topology_template: - substitution_mappings: - node_type: MyExample.OranNF.1_0 - requirements: - ... - - node_templates: - OranNF: - type: MyExample.OranNF.1_0 - -``` - -``` - -properties: - ... -interfaces: - Vnflcm: - operations: - instantiate: - implementation: ... - -NfDeploymentUnitExample: - type: tosca.nodes.nfv.Vdu.Compute - properties: - ... - boot_data: - kvp_data: - data: - aal_address_1: { get_property: [OranNF, configurable_properties, -additional_configurable_properties, aal_param_03] } - ... - -``` - -In the example above: - -- In red, the modelling concerns only to the choice of TOSCA as NF Deployment descriptor according to ETSI GS NFV-SOL 001 [10] and does not concern to modelling of AAL information or requirements. In other words, the red parts show how the NF designer models the capability within the descriptor by following the ETSI GS NFV-SOL 001 [10] specification. -- In blue, the modelling concerns to AAL and what is (expected) to be specified by O-RAN regarding relevant AAL configuration parameters. The values here are only an example. The possible values and parameters names ("profile\_type", version number, "other\_profile\_params") are assumed to be referenced from O-RAN specification or simply referenced from the respective O-RAN specification by the ETSI GS NFV-SOL 001 [10]. -- In black, these are other parts that do not concern specifically to AAL and are only depicted for completeness of the example. - -It is to be noted that MyExample.datatypes.nfv.VnfInstantiateAdditionalParameters and MyExample.datatypes.nfv.AdditionalVnfConfigurableProperties are datatypes defined by the NF designer and not further specified by ETSI GS NFV-SOL 001 [10]. However, from an O-RAN standpoint, standard parameters related to AAL might be defined. - -### A.2.3 Example #3: Exchange of information on the O2dms interfaces related to acceleration - -Based on the example described in clause A.2.2, the following related example illustrates how the runtime configuration data can be provided by the SMO to the DMS as part of content message data during the NF Deployment instantiation request. - -``` - -POST /vnflcm/v2/vnf_instances/nf-deployment-A/instantiate -Host: ocloud.com -Accept: application/json -Content-Type: application/json -Content-Length: XX - -{ - "flavourId": "small", - "instantiationLevelId": "level-1", - "additionalParams": { - "aal_param_01": "aal-profile-fec", - "aal_param_02": "v1" - } -} - -``` - -``` - } - "vnfConfigurableProperties": { - "aal_param_03": "PCI-address", - } -} -``` - -## A.3 NF Deployment lifecycle examples - -### A.3.1 Example #1: Healing procedure to recover from failure - -The present example describes a more end-to-end procedure to recover from a faulty situation impacting an NF Deployment. In this example, a failure happens on the NF Deployment regarding one or more of its NF Deployment units due to failures happening in respective O-Cloud resources like virtualised resources or containerized workloads. The fault(s) is (are) reported by means of one or multiple Alarms. When the failure is detected, and reported, the DMS starts the auto-healing, if the auto-healing configuration has been set for the management of the NF Deployment. Otherwise, the consumer, in this case the NFO, can trigger the healing to recover from the failure. - -Figure A.3.1-1 illustrates the procedure flow of the healing to recover from the failure. - -NOTE: While the procedure illustrates internal DMS interactions, these are only introduced for illustrative purpose to shows the relationship between the resource-level failure situation and the NF Deployment healing. - -![Sequence diagram showing the healing procedure to recover from failure. Lifelines: SMO (NFO), O-Cloud (DMS: Deployment mgmt, VR/container mgmt), and NF Deployment resource(s). The process involves fault detection, alarm sending, alarm processing, and then either an auto-healing procedure or an on-demand healing procedure based on configuration, followed by alarm clearance notification.](81a0abf9a79b27cf9d765553216b173c_img.jpg) - -``` - -sequenceDiagram - participant SMO as SMO (NFO) - subgraph O-Cloud - participant DMS as DMS (Deployment mgmt, VR/container mgmt) - end - participant NFDR as NF Deployment resource(s) - - Note right of NFDR: Failure occurs in the one or more of its virtualised resources or containerized workloads associate to the NF Deployment - NFDR->>DMS: 1 Detects the virtualised resource (VR) or container workload fault - DMS->>SMO: 2 Sends alarm(s) associated to the VR/container fault - SMO-->>DMS: 3 Processes the received alarm(s) and associates to NF Deployment and its units - Note left of SMO: ref Execute steps of FM notification (see figure 4.4.3.2-1) for notification about new alarm(s) associated to the faulty NF Deployment - alt Auto-healing is enabled for the NF Deployment - Note left of SMO: ref Execute steps #1 to #6 of the NF Deployment auto-healing procedure (see figure 4.4.2.4.3-1) - DMS->>NFDR: 4 Interactions to create, update, terminate VR/container workloads to recover the NF Deployment - NFDR-->>DMS: 5 Creation, update, termination of VR/container workloads on the NF Deployment - Note left of SMO: ref Execute steps #9 to #10 of the NF Deployment auto-healing procedure (see figure 4.4.2.4.3-1) - else Auto-healing is not enabled for the NF Deployment - Note left of SMO: ref Execute steps #1 to #7 of the NF Deployment on-demand healing procedure (see figure 4.4.2.4.2-1) - DMS->>NFDR: 6 Interactions to create, update, terminate VR/container workloads to recover the NF Deployment - NFDR-->>DMS: 7 Creation, update, termination of VR/container workloads on the NF Deployment - Note left of SMO: ref Execute steps #10 to #11 of the NF Deployment on-demand healing procedure (see figure 4.4.2.4.2-1) - end - Note left of SMO: ref Execute steps of FM notification (see figure 4.4.3.2-1) to send alarm clearance notification(s) regarding the previously faulty NF Deployment - Note right of NFDR: NF Deployment is recovered from the failure - -``` - -Sequence diagram showing the healing procedure to recover from failure. Lifelines: SMO (NFO), O-Cloud (DMS: Deployment mgmt, VR/container mgmt), and NF Deployment resource(s). The process involves fault detection, alarm sending, alarm processing, and then either an auto-healing procedure or an on-demand healing procedure based on configuration, followed by alarm clearance notification. - -Figure A.3.1-1: Example of healing procedure to recover from failure - -# Annex (informative): Change History/Change request (history) - -| Date | Revision | Description | -|------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2023.11.13 | 05.00.01 | Implemented CRs DCM-0024, DCM-0025, DCM-0026, DCM-0027, DCM-0028, DCM-0029, DCM-0030, DCM-0031, | -| 2023.11.17 | 05.00.02 | Editorial updates based on review comments | -| 2023.11.28 | 06.00 | Final version 06.00 | -| 2024.03.19 | 06.00.01 | Implemented CRs DCM-0032, DCM-0033, DCM-0034 | -| 2024.04.01 | 07.00 | Final version 07.00 | -| 2024.07.09 | 07.00.01 | Implemented approved CRs for July Train:
  • - DCM-2024.06.25-WG6-CR-0035-O2dms_ETSI_NFV_profile_update_API_versions-v01
  • - DCM-2024.06.25-WG6-CR-0036-O2dms_ETSI_NFV_profile_bug_fixes-v01
Rapporteur actions:
  • - Corrected few occurrences of "error! Reference source not found" in clause 3.1.2 and 3.1.6.1.6. Added the corresponding missing references in the clause 1.2 (i.e. [36] and [37]).
  • - In reference [18] (SOL018), the notes 1 and 2 can be deleted, because as per CR-0035, a reference to a published version can be made.
| -| 2024.07.23 | 07.00.02 | Addressing July Train 2024 review comments:
  • - Comment #4 on correcting cross-references.
| -| 2024.07.29 | 08.00 | Final version for 2024 July Train
Upgraded release number to R004. | -| 2025.03.13 | 08.00.01 | Implemented approved CRs for 2025 March Train:
  • - DCM-2025.02.24-WG6-CR-0037-O2dms_ETSI_NFV_profile_update_API_versions-v01
  • - DCM-2025.02.24-WG6-CR-0038-O2dms_ETSI_NFV_profile_cluster_relationship_descriptions-v02
  • - DCM-2025.02.24-WG6-CR-0039-O2dms_ETSI_NFV_profile_healing_example-v01
| -| 2025.03.28 | 09.00 | Final version for 2025 March Train. | -| 2025.11.10 | 09.00.01 | Implemented approved CRs for 2025 November Train:
  • - DCM-2025.10.24-WG6-CR-0040-Apply_new_TS_template-v02
Additional rapporteur updates:
  • - Corrected references to new clause numbers of figures in plantuml and figure A.3.1-1.
| -| 2025.11.11 | 09.00.02 | Rapporteur updates:
  • - Update to O-RAN Release R005 and date of copyright to 2026.
| -| 2025.11.27 | 10.00 | Final version for 2025 November Train | \ No newline at end of file diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/01e00200a536673d6cd0e6d8705047a0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/01e00200a536673d6cd0e6d8705047a0_img.jpg deleted file mode 100644 index 137fa9237693d1360d2bc29614238c0967cbd639..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/01e00200a536673d6cd0e6d8705047a0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b886bc628345af61f95e8355b53237d1c723111f503ab2cef52f36645ccaa1e3 -size 109202 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/080a7af02bc47cf21ebfae4e0be39745_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/080a7af02bc47cf21ebfae4e0be39745_img.jpg deleted file mode 100644 index e377f93f89abde2fd22fa1f601ce627a32924761..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/080a7af02bc47cf21ebfae4e0be39745_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:95df647b58e580a4206a712d15b1fc2aaff0893e6d014d25cee0b893aea8e1b2 -size 77380 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 6134992ce9c5d512e70c1e2ff37d9530ef08bf5d..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/08783c875dd39684fee7f2a40b584c64_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/08f6ace0c83e7394657fa372b47aec04_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/08f6ace0c83e7394657fa372b47aec04_img.jpg deleted file mode 100644 index 647713d643524cf1b9876247c3f2d24087f743aa..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/08f6ace0c83e7394657fa372b47aec04_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2db887ba67fb3bf819b47e147e6f48a4d23a20d8f4ae58df4500325c199776a2 -size 107273 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/0a65720e640be13541e947c06c7a8c7f_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/0c80c383f76034e117adf5e5eaadaaf3_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/0c80c383f76034e117adf5e5eaadaaf3_img.jpg deleted file mode 100644 index b49273202a47705863a0634bede534fe48111739..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/0c80c383f76034e117adf5e5eaadaaf3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:16f7641c7fb6ed25b4548167b77c9c549664a7f22ac4798e6008f02fd2a863fd -size 103777 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg deleted file mode 100644 index 43d0715410e0b110888943d5448f2fc34073fed2..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/0f985b39edc1d52ba3600c438bc8f0a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:21d38aba114be56fd878f69b3cb635f9bbd748a40bcb3a44fef845d45a4e014d -size 220168 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/1099a4137017f2d9721d546bbb1e9362_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/1142ba0197b158bb198186fe8baccc32_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/1142ba0197b158bb198186fe8baccc32_img.jpg deleted file mode 100644 index 3204849e1186086ef62030d1d7de7d189c8f3141..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/1142ba0197b158bb198186fe8baccc32_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:12daf35c4710ea89781c18083f73118561b72fa7d8ed177ac1233e6ac98be332 -size 183313 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/14af8d47efd24c21fddf71b2415b6397_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg deleted file mode 100644 index 035d35cc725753f1b2cb7f1f07df9115597916f2..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3ab78a2327beb9375186178f60ff6fd6eab9790b6ad509ca17917be4b614cdbf -size 191160 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/1ca688982d625c3b8a8e382b675de466_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/1ca688982d625c3b8a8e382b675de466_img.jpg deleted file mode 100644 index 69a74f7a2d00fb87adb2395c18321419c229fa1a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/1ca688982d625c3b8a8e382b675de466_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5542fa96487e70d51c770edeb4b210a5582df20e9e6f72253e99781e11455af2 -size 76859 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/22f30783614672d201275c116a5d8516_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/29f3760c0230631eb03f67030ef65ed0_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/2b3a967f6ce4f23649be995a353e39f8_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/2b3a967f6ce4f23649be995a353e39f8_img.jpg deleted file mode 100644 index 716a1f6f7c9d5a25d75c194685dc8efc090c22f0..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/2b3a967f6ce4f23649be995a353e39f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:aa9f1fa2446b29019da9d266b13974ca041055347092fc29ecb83f9ccdaf3d7e -size 231923 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg deleted file mode 100644 index b35330f51e24c48748e85d092c042d5f545c0e09..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b3500bcb56900c04cded15b92bc018698cf060deb13c79ddfb6fe422f51fec0f -size 4585 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg deleted file mode 100644 index 462c5f016a918c8162ae952d3e072699ad783d81..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/30a91d1c3ead5af4823f4f3330e4ac1e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6576cc184488b7e10fb5d3cf6e3ce10c363978ae752f1cc233f0dd26c9f21849 -size 69903 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg deleted file mode 100644 index 4f4c070e5721fb27e25a8f715632bbfaf5fe0e06..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b5857c8d5e15ab88754742341b4c53ee3236058840630610f9ff19a91ac55472 -size 212955 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/366a77fdefb0097b3289b4a011911390_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/366a77fdefb0097b3289b4a011911390_img.jpg deleted file mode 100644 index 074af85b3ae363d43558c68245b6de5b05c23aa1..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/366a77fdefb0097b3289b4a011911390_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b1fe42be196eef26ac6d45ad3043801bdfdf97bd3cdd04beca89bba008483f99 -size 196590 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 2f54633a796f0d866754433c73dd79178cd34273..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/38222c3ae003223a67635bfcc6950fbb_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/3a4f4369128594c5db0aa6b853c0666e_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/3f727e6c0d6658bc53ea10905c4561dd_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4260aa4a7ece77c411597094c9d197bd_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4260aa4a7ece77c411597094c9d197bd_img.jpg deleted file mode 100644 index 93aeaec336d2a6fcdafc09059fe42992435a4dbb..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4260aa4a7ece77c411597094c9d197bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5acf9f3a6a19ae52f503c1cef2081969b8cec947befd079f44de03015c43e558 -size 31139 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index d8d7e75d64112953d540ff59e7c660dcc4a24b00..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/446c0bd806260f25430cadb01a6786c7_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/47a7beddcb8a1b7abdca746967e32bb4_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/47a7beddcb8a1b7abdca746967e32bb4_img.jpg deleted file mode 100644 index a3b67f4c0f3e091f4b23fd3863c511d71036ee25..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/47a7beddcb8a1b7abdca746967e32bb4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3fccf2e1ec377f134dd8334c2dabfb79eb4936e2a5f354c92aa61a5429d11db1 -size 191247 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/481b1f80fc31ebebb30d1f57d31e3af3_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index bef92370b92f7f62fcf03e62e04f4f2905eeb0df..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:29af4545675cb00eb2790504afe0c0bc329627f1c20c8d6156b2f4290d8d8d75 -size 4502 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg deleted file mode 100644 index da3c245a896c7264217a35402ebfa9936f8ea07c..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a87aeeda16525c348f0dcb56d9f74f7c281bcbbcadfa788a75c6d3b97040209e -size 4606 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4b81ac66c571b3118659e4d9f47abb22_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4db00373eb0bec04341ee887235bbfea_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/5009e30a55479d3941af523871208f9d_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/5009e30a55479d3941af523871208f9d_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/52a225f71b166b0c65c2f29f32a79f7f_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/56ac11fb9683d7b846fb65c845d80f22_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/59368942873b0c35eef79a7a985025dc_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/59fcc0e3699f239444841881a2e75da0_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/5ae3023386ee15fae372871afce28865_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/5e92d9e8e9ce204e405bff2367f88176_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/5e92d9e8e9ce204e405bff2367f88176_img.jpg deleted file mode 100644 index dd466484826224f53e10c19000d703d830f2b2e4..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/5e92d9e8e9ce204e405bff2367f88176_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:511a57482bd90480b1120af8630a8bb277df5627da879510c370f9f1f0d968a1 -size 40172 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg deleted file mode 100644 index d4a369fd93a12cdaf7d1497be809aad0f7b93a9f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/608f1b5ef8f3dc0723f2b4ea1fb72be2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a71118e65d101410bae1fc1f931d6c003cd507060d24325c5a0a7681b1b7022f -size 92889 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/60d6a326e6061d71ea69c9375ec96631_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/60e345365fd1e52e01c91e3fd3cc6515_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/6588b1c7f14069d96744b473ad663248_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/659a041a7997f9eea79f4e2f3ba265a5_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/659a041a7997f9eea79f4e2f3ba265a5_img.jpg deleted file mode 100644 index 19b2af35065dce3c42285ce4085331ac3d1d4d68..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/659a041a7997f9eea79f4e2f3ba265a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9c2224e23835bc27758a9b743d36f39562fca5fff712134fd613d658e1cee2cd -size 102435 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/66e89867f97592fd4bfab0e4f2b2054f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/66e89867f97592fd4bfab0e4f2b2054f_img.jpg deleted file mode 100644 index b6fc0908d7ebd3ab3e9bae0800b5f11c739a372f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/66e89867f97592fd4bfab0e4f2b2054f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:740109dacdc22e69b92b8521eb569ee1d40eb6a71db33112b8600dff3834f06a -size 81408 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg deleted file mode 100644 index bef92370b92f7f62fcf03e62e04f4f2905eeb0df..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:29af4545675cb00eb2790504afe0c0bc329627f1c20c8d6156b2f4290d8d8d75 -size 4502 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/6a9c5a85a12499d60c5a3a75c643b852_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/6c6024603c6fd57b23210b79f573b3bd_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/6c8a96787f532bd1fa4719e738cf556f_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/78fe18e63ba327b1e224bad8a7c4de54_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/79898de98da3367d0ea9beef38f5c01c_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7a3d4c97055e3021cefb0c5850050bff_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7d08458fbe0bd5f306c00c16d68b25f2_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg deleted file mode 100644 index be70db0a94b9911121943ecbda65db5f9f13e543..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7e61b2e2506cc7e5d6e16ce9c9df25bb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d1ba723be973e52cffb16fc8b19b6f2130551b17480b6c777030d9d98c3f79b -size 75867 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7e74ac663f3e644b589ed28f5fd29398_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7e74ac663f3e644b589ed28f5fd29398_img.jpg deleted file mode 100644 index bd10f720577e72ca1d6240d913878b5e8d86dc20..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7e74ac663f3e644b589ed28f5fd29398_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f90e9d7e7802579e6a3da1c9d292284e9c0efc4ae6bca8f24365d90093a91934 -size 83444 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/7f4320cee12fc1dbb865cc6b67462a91_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/802707b774f2d2973b49cea2020e8453_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/802707b774f2d2973b49cea2020e8453_img.jpg deleted file mode 100644 index fd476a9cc77a1e616e28cf7bddc9f19b6984894d..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/802707b774f2d2973b49cea2020e8453_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f41e0df1e5a9b25fa379244f0625263885206358dae7c752b9b9cc24047c67b -size 40677 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/81a0abf9a79b27cf9d765553216b173c_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/81a0abf9a79b27cf9d765553216b173c_img.jpg deleted file mode 100644 index 1b38c3e07df73cb5be238a3b05f897e18fc2b377..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/81a0abf9a79b27cf9d765553216b173c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f356f3b93de0711d84d63c533ebe703bf457e041109dcbc896dff3af59d2cfd2 -size 182850 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/829cdaf00f7219d70e571064b2b13291_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/83ee9f10bd3636e192d68decf7f04cec_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/8447c5519e85d7a9e029fbf321da4c4f_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/854df8ad60507803253274673f9062cf_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/8b4befaffc5166da571069410e207aea_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 2f54633a796f0d866754433c73dd79178cd34273..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/8fbe9e67b51710384633b6407d60420d_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/9159d999b6514420a64eae80e52f1fd5_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/977811d1c73b74f801be9f4c376694ca_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/977811d1c73b74f801be9f4c376694ca_img.jpg deleted file mode 100644 index 6a80e22b88ffe4b0576270b52d218f36aa1398d4..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/977811d1c73b74f801be9f4c376694ca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3083c51122e9792c673a9378438a6ddc93f36535b5c87fb3af790e236a60bfc2 -size 44381 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/990afa9d07fb81cf8760867cb4247a79_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg deleted file mode 100644 index 346af46058e6e5946b96295b564b6cab027bd19e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a149b400127a3e3e50b3c98d27c5935c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2a4e83998e75f1929682b06150c6f6269f0a340163881fb138a7ee688532582f -size 199583 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a28ab03366399b5e0a61445bc57e3724_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a780a960b3f2de2493d5785bedae10ff_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a780a960b3f2de2493d5785bedae10ff_img.jpg deleted file mode 100644 index 0db02a6fca65fc88bb8999d0b11df74c2be8c2a8..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a780a960b3f2de2493d5785bedae10ff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe99e105267ff86e67cf4e8b7ec7b269fb08bce270c17511e26cd6eeec306bbc -size 85471 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a7fcb275d0eed586509a47f4f86a9725_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a82aef1d2f3f1a527328950e9db947ee_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/a9bb99d15f54792e1c9a14b1e465369a_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/b35ea3e304aad7d350a9902270413930_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/b35ea3e304aad7d350a9902270413930_img.jpg deleted file mode 100644 index 6c115274c845461e9826ee18a5281cfef2a99df4..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/b35ea3e304aad7d350a9902270413930_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:479415c6b8b8372e727ea2e120fefb214da5a4460f36785a40b6f3a71e6e6b03 -size 87261 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/b4fb54e441be8184578e6a7372c90ec6_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/b4fb54e441be8184578e6a7372c90ec6_img.jpg deleted file mode 100644 index cd11735aafd99ce481d01e62cf6259950a26a3ac..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/b4fb54e441be8184578e6a7372c90ec6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d0d8a1bc8931770bfd5e8d83e2022a7cae1994e7756489e8c2c4ec69c2a97cf3 -size 18394 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/bc0074c9be2d587e0b85224d9cb083ec_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/be8d4d130f4e1f103926de61c4bfc23c_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/be8d4d130f4e1f103926de61c4bfc23c_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/c5538ac451af9d74926b82278f11fb87_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/c78c2eefd86269d1740ab85a916f24f2_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/c78c2eefd86269d1740ab85a916f24f2_img.jpg deleted file mode 100644 index f1b10f80a43a29c63a9ba909dd961a714b53caec..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/c78c2eefd86269d1740ab85a916f24f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:02ae38773a2416bf09c7474a5b39fdc79f9172ad291a4049584697050e2ab6ed -size 41595 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg deleted file mode 100644 index 219f1ad80a4d8ef2486a221bc48ae7f586450c10..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/cc6f9dbfc36aa5821d9749ca84861f93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0090ac8f201f2febb31387e5ad2054875c47b87d77ae96a52634b4f809e4d97f -size 119440 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/d0516b99882398c64c90f71c12e808e2_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index a1a3705a3f17fb272015a65d1091679c3253cc88..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/d2c29dfabebacb6f853683a6c3759320_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/d52ae84d18c68f7d66ee994f5eec34b0_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/d879e5f2c388bb87ee9614f63364dcf0_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/d90d939bcbf43d474efaeeaa335a635c_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/da74b0e807fd62f32abdc3c05ffbabf4_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/dbd230eafb5429741c22c2f7293118af_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/ddfa5b18550d1a022a941e3c31843814_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/ddfa5b18550d1a022a941e3c31843814_img.jpg deleted file mode 100644 index 07fb138c4dcd3ff74639355b3896c9197e12338e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/ddfa5b18550d1a022a941e3c31843814_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9b23ff50841c66ae30b787fc79fe294999f31b12f49cd9eeb8bf832a42118457 -size 106178 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e1ce114c43dcefce51eadcd12f2da6d2_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e1ce114c43dcefce51eadcd12f2da6d2_img.jpg deleted file mode 100644 index 301f8d98ac545283aa77db31f7d3ad468f9a056c..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e1ce114c43dcefce51eadcd12f2da6d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fc98b96c286920635a21d94b1dc5ec87dca68afdb4040368cdcdc95f225aad8e -size 24357 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e32e1bcf367a284cc7a4186056810d22_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 2f54633a796f0d866754433c73dd79178cd34273..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e345315706e3fe633bb6d593246c01bf_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index e03044741055310b08a6b3f8abec1d50e31965e1..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edb7959e0fb16d0497c3306c5926c07307853a637aeeb7ee9b52b4d331d0f8da -size 4569 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e511e373339b5f948f239b19e0c37dd4_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/e87df69ebd4cd2dbbf6749079e6c057a_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/f3d768b0299c4763bc703b606391c48b_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index 2f54633a796f0d866754433c73dd79178cd34273..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/f74adaa1840504407cd4272995426f82_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/f7dbd497160f02888f34fdf243648aa2_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg deleted file mode 100644 index 614fd5feb001c1715cd5b1ea4d4e0dc41ffff27a..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_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/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg deleted file mode 100644 index 98b859f7322059ef6dd53679c137bc6f825475e9..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/fa01531ea2c45beeb4036005da3037a4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ec1a67c6b26ae6f82103f63ae96e602281abb3433e017eea5c8636c06ac1239c -size 212767 diff --git a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index bbe1a3a2908e6d0a9af25326efdda49e31f19d70..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2DMS-INTERFACE-ETSI-NFV-PROFILE-R005-v10.00/images/ff748955b94dcb8337283fbe12baa475_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/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/doc.md b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/doc.md deleted file mode 100644 index 7239b8ae756cb4faf480899e9a2dcd1c050cc77e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/doc.md +++ /dev/null @@ -1,5603 +0,0 @@ - - -# **O-RAN Working Group 6****O2ims Interface 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., Buschkauler Weg 27, 53347 Alfter, Germany -Register of Associations, Bonn VR 11238, VAT ID DE321720189 - -# Contents - -| | | | -|-------|---------------------------------------------------------|-----| -| 1 | Introduction ..... | 4 | -| 1.1 | Scope ..... | 4 | -| 1.2 | References..... | 4 | -| 1.3 | Definitions and Abbreviations ..... | 6 | -| 1.3.1 | Definitions..... | 6 | -| 1.3.2 | Abbreviations ..... | 6 | -| 2 | Service Definitions ..... | 7 | -| 2.1 | O2ims Services ..... | 7 | -| 2.1.1 | General ..... | 7 | -| 2.1.2 | O2ims_InfrastructureInventory Services..... | 8 | -| 2.1.3 | O2ims_InfrastructureMonitoring Services..... | 10 | -| 2.1.4 | O2ims_InfrastructureProvisioning Services..... | 13 | -| 2.1.5 | O2ims_InfrastructureSoftwareManagement Services..... | 16 | -| 2.1.6 | O2ims_InfrastructureLifecycleManagement Services ..... | 16 | -| 2.1.7 | O2ims_InfrastructurePerformance Services..... | 17 | -| 2.1.8 | O2ims_InfrastructureLogging Services..... | 27 | -| 3 | API definitions ..... | 31 | -| 3.1 | General aspects ..... | 31 | -| 3.1.1 | Introduction ..... | 31 | -| 3.1.2 | URI structure and supported content formats..... | 31 | -| 3.1.3 | Usage of HTTP header fields ..... | 32 | -| 3.1.4 | Result set control..... | 34 | -| 3.1.5 | Error reporting..... | 34 | -| 3.1.6 | Common data types..... | 34 | -| 3.1.7 | Security ..... | 37 | -| 3.1.8 | Version management..... | 37 | -| 3.2 | O2ims_InfrastructureInventory Service API ..... | 37 | -| 3.2.1 | Description ..... | 37 | -| 3.2.2 | API version..... | 38 | -| 3.2.3 | REST resources structure and methods ..... | 38 | -| 3.2.4 | REST resources..... | 40 | -| 3.2.5 | Notifications ..... | 78 | -| 3.2.6 | Data model ..... | 79 | -| 3.2.7 | Error handling ..... | 89 | -| 3.2.8 | Security ..... | 89 | -| 3.3 | O2ims_InfrastructureMonitoring Service API..... | 89 | -| 3.3.1 | Description ..... | 89 | -| 3.3.2 | API version..... | 89 | -| 3.3.3 | REST resources structure and methods ..... | 90 | -| 3.3.4 | REST resources..... | 92 | -| 3.3.5 | Notifications ..... | 111 | -| 3.3.6 | Data model ..... | 112 | -| 3.3.7 | Error handling ..... | 116 | -| 3.3.8 | Security ..... | 117 | -| 3.4 | O2ims_InfrastructureProvisioning Service API ..... | 117 | -| 3.4.1 | Description ..... | 117 | -| 3.4.2 | API Version..... | 117 | -| 3.4.3 | REST resources structure and methods ..... | 117 | -| 3.4.4 | REST resources..... | 118 | -| 3.4.5 | Notifications ..... | 125 | -| 3.4.6 | Data model ..... | 125 | -| 3.4.7 | Error handling ..... | 128 | -| 3.4.8 | Security ..... | 129 | -| 3.5 | O2ims_InfrastructureSoftwareManagement Service API..... | 129 | - -- 3.6 O2ims\_InfrastructureLifecycleManagement Service API..... 129 - - 3.6.1 Description ..... 129 - - 3.6.2 API version..... 129 - - 3.6.3 REST resources structure and methods..... 129 - - 3.6.4 REST resources ..... 129 - - 3.6.5 Notifications..... 129 - - 3.6.6 Data Model..... 130 - - 3.6.7 Error handling ..... 130 - - 3.6.8 Security ..... 131 -- 3.7 O2ims\_InfrastructurePerformance Service API ..... 131 - - 3.7.1 Description ..... 131 - - 3.7.2 API version..... 131 - - 3.7.3 REST resources structure and methods..... 132 - - 3.7.4 REST resources ..... 133 - - 3.7.5 Notifications..... 150 - - 3.7.6 Data Model..... 150 - - 3.7.7 Error handling ..... 159 - - 3.7.8 Security ..... 160 -- 3.8 O2ims\_InfrastructureLogging Service API ..... 160 -- 4 O-Cloud Alarms ..... 161 - - 4.1 General..... 161 - - 4.2 Alarm Definition Identifiers ..... 162 - - 4.3 Probable Cause Identifiers ..... 163 -- Annex (informative): Change History ..... 168 - -# 1 Introduction - -## 1.1 Scope - -This Technical Specification has been produced by the O-RAN.org. - -The contents of the present document are subject to continuing work within O-RAN WG6 and may change following formal O-RAN approval. Should the O-RAN.org modify the contents of the present document, it will be re-released by O-RAN Alliance with an identifying change of release date and an increase in version number as follows: - -Release x.y.z - -where: - -- x the first digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. (the initial approved document will have x=01). -- y the second digit is incremented when editorial only changes have been incorporated in the document. -- z the third digit included only in working versions of the document indicating incremental changes during the editing process. - -This document defines O-RAN O-Cloud IMS interface functions and protocols for the O-RAN O2 interface. The document studies the functions conveyed over the interface, including management functions, procedures, operations and corresponding solutions, and identifies existing standards and industry work that can serve as a basis for O-RAN work. - -## 1.2 References - -In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in 3GPP Release 18. - -- [1] 3GPP TR 21.905: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications" -- [2] O-RAN Whitepaper -- [3] ORAN-WG4.MP.0-v01.00: O-RAN Alliance Working Group 4 Management Plane Specification -- [4] O-RAN WG1 Architecture Description -- [5] O-RAN WG1 OAM Architecture -- [6] O-RAN WG1 O1 Interface Specification -- [7] O-RAN WG6 Cloud Architecture and Deployment Scenarios -- [8] RFC 6241, "Network Configuration Protocol (NETCONF)", IETF, June 2011 -- [9] RFC 7950, "The YANG 1.1 Data Modeling Language", IETF, August 2016 -- [10] RFC 2119, "Key words for use in RFCs to Indicate Requirement Levels", IETF, March 1997 -- [11] 3GPP TS 29.501 "5G System; Principles and Guidelines for Services Definition; Stage 3" -- [12] 3GPP TS 29.571 "" -- [13] ONAP VES Event Listener Specification v7.2, May 2020 (Draft) -- [14] 3GPP TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3". -- [15] OpenAPI: "OpenAPI 3.0.0 Specification", . -- [16] 3GPP TS 33.501: "Security architecture and procedures for 5G system". -- [17] IETF RFC 6749: "The OAuth 2.0 Authorization Framework". -- [18] 3GPP TS 29.510: "5G System; Network Function Repository Services; Stage 3". - -- [19] IETF RFC 7540: "Hypertext Transfer Protocol Version 2 (HTTP/2)". -- [20] IETF RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format". -- [21] IETF RFC 7807: "Problem Details for HTTP APIs". -- [22] ETSI GS NFV-SOL 013 v3.3.1: "Protocols and Data Models; Specification of common aspects for RESTful NFV MANO APIs", September 2020 -- [23] O-RAN WG6 "Orchestration Use Case and Requirements for O-RAN Virtualized RAN" -- [24] O-RAN WG6 "O-RAN O2 General Aspects and Principles Specification" -- [25] ETSI GS NFV-SOL 015v1.2.1: "Protocols and Data Models; Specification of Patterns and Conventions for RESTful NFV-MANO APIs", December 2020 -- [26] ISO/IEC 9646-7: "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". -- [27] ITU-T Recommendation X.733 (02/92): "Information technology - Open Systems Interconnection - Systems Management: Alarm reporting function". -- [28] ITU-T Recommendation X.736, "Information Technology - Open Systems Interconnection - System Management: Security Alarm Reporting Function', 1992" -- [29] IETF RFC 7396: "JSON Merge Patch" -- [30] IETF RFC 7230: "Hypertext Transfer Protocol (HTTP/1.1)" -- [31] IETF RFC 793: "Transmission Control Protocol" -- [32] IETF RFC 2818: "HTTP Over TLS" -- [33] IETF RFC 5246: "The TLS Protocol Version 1.2" -- [34] IETF RFC 3986: "Uniform Resource Identifier (URI)" -- [35] ETSI TS 133 310: "Universal Mobile Telecommunications System (UMTS); LTE; Network Domain Security (NDS); Authentication Framework (AF)" -- [36] O-RAN WG6 "O-Cloud Information Model" -- [37] O-RAN WG10 "O-RAN Work Group 10 (OAM for O-RAN); O-RAN Information Model and Data Models Specification". -- [38] ETSI GS NFV-IFA 045 (V5.2.1 2024-11): "Network Functions Virtualisation (NFV) Release 4; Management and Orchestration; Faults and alarms modelling specification". -- [39] 3GPP TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)" -- [40] 3GPP TS 32.404: "Technical Specification Group Services and System Aspects; Telecommunication management; Performance Management (PM); Performance measurements" -- [41] ETSI GS NFV-IFA 027 V4.2.1: "Network Functions Virtualisation (NFV) Release 4; Management and Orchestration; Performance Measurements Specification" -- [42] 3GPP TS 28.111: "Technical Specification Group Services and System Aspects; Management and orchestration; Fault Management (FM)" -- [43] IETF RFC 3339: "Date and Time on the Internet: Timestamps" -- [44] IETF RFC 7946: "The GeoJSON Format" -- [45] IETF RFC 4676: "Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Address Configuration Information" -- [46] O-RAN.WG11.TS.SecProtSpec: "O-RAN Work Group 11 (Security Work Group); Security Protocols Specifications" - -## 1.3 Definitions and Abbreviations - -### 1.3.1 Definitions - -FFS. - -### 1.3.2 Abbreviations - -For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 0 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 0. - -| | | -|---------|---------------------------------------------------------| -| DMS | O-Cloud Deployment Management Services | -| FCAPS | Fault, Configuration, Accounting, Performance, Security | -| HATEOAS | Hypermedia as the Engine of Application State | -| IMS | O-Cloud Infrastructure Management Services | -| MANO | Management and Orchestration | -| MnS | Management Service | -| MOC | Managed Object Class | -| MOI | Managed Object Instance | -| MVP | Minimum Viable Product | -| O-RAN | Open Radio Access Network | -| ONAP | Open Network Automation Platform | -| OSM | Open Source Mano | -| RAN | Radio Access Network | -| TLS | Transport Layer Security | -| TR | Technical Report | -| TS | Technical Specification | -| SMO | Service Management and Orchestration | - -# 2 Service Definitions - -## 2.1 O2ims Services - -### 2.1.1 General - -Table 2.1.1-1 O2ims Services to API mapping summarizes the corresponding O2ims service APIs defined. - -**Table 2.1.1-1 O2ims Services to API mapping** - -| Service Name | Clause | Description | apiName | -|---------------------------------------------------|--------|------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------| -| O2ims_InfrastructureInventory Services | 3.2 | Service for querying the O-Cloud resources and management services. | O2ims_infrastructureInventory | -| O2ims_InfrastructureMonitoring Services | 3.3 | Services related to O-Cloud infrastructure fault management. | O2ims_infrastructureMonitoring | -| O2ims_InfrastructureProvisioning Services | 3.4 | Service for configuring the O-Cloud node cluster and infrastructure resources. | O2ims_infrastructureProvisioning | -| O2ims_InfrastructureSoftware Management Services | 3.5 | Services for software inventory and updating the software used for O-Cloud infrastructure resources and management services. | Not specified in the present document version | -| O2ims_InfrastructureLifecycle Management Services | 3.6 | Services related to O-Cloud infrastructure lifecycle management and events. | O2ims_infrastructureLifeCycleManagement | -| O2ims_InfrastructurePerformance Services | 3.7 | Services related to O-Cloud infrastructure performance management | O2ims_infrastructurePerformance | -| O2ims_InfrastructureLogging Services | 3.8 | Services related to O-Cloud infrastructure logging management | Not specified in the present document version | - -The information elements for the O2ims services are contained in the O-Cloud Information Model Specification, see O-RAN WG6.O-CLOUD-IM [36]. - -2.1.1.1 Void - -2.1.1.2 Void - -2.1.1.3 Void - -2.1.1.4 Void - -### 2.1.2 O2ims\_InfrastructureInventory Services - -Any object in the O-Cloud which can generate a fault, a performance metric, or is exposed to the SMO for configuration needs to have a type, which depicts the class of object. Generally, an O-Cloud is a composition of provisioned resources serving different roles, such as compute, storage, or networking. - -#### 2.1.2.1 Service description - -O-Clouds contain physical, software and logical resources. The O-Cloud is the source of information for these assets but is required to provide a mechanism for asset management to account for them. The O2ims\_InfrastructureInventory services provides the read-only interface to its inventory such that accounting can be achieved. - -The O-Cloud SHALL expose its capabilities and supported resource types to the SMO. - -The O2ims\_InfrastructureInventory services SHALL be available only after the O-Cloud has registered its IMS endpoint with the SMO. - -The O2ims\_InfrastructureInventory services SHALL provide the list of resource type(s) supported by the O-Cloud across all resource pools defined in its distributed deployment. - -#### 2.1.2.2 Service operations - -##### 2.1.2.2.1 O-Cloud Information Query - -The O2ims\_InfrastructureInventory service shall enable an authorized consumer to query and retrieve various information related to the O-Cloud infrastructure and its resources. - -NOTE: It is up to the protocol and data model specification to determine the one or various protocol operations enabling the authorized consumer to retrieve the O-Cloud information. - -Table 2.1.2.2.1-1 lists the information flow exchanged between the SMO and the O-Cloud. - -**Table 2.1.2.2-1: O2ims\_InfrastructureInventory Query operation** - -| Message | Direction | -|-------------------------|---------------| -| QueryOcloudInfoRequest | SMO → O-Cloud | -| QueryOcloudInfoResponse | O-Cloud → SMO | - -The input parameters sent when invoking the operation shall support means to: - -- Filter to select which information is queried about the supported Inventory Infrastructure Service Objects which can be any subclass of the InfrastructureInventoryObject as depicted in the Information Model, see O-RAN WG6.O-CLOUD-IM [36], clause 4.2.1.3.2.1. Filtering the Service Objects by their names, identifiers, metadata information and status information shall be supported. When the filter results in no matching Service Objects, the operation shall return an empty list. -- Select the list of attributes of information of the supported Inventory Infrastructure Service Objects to be returned matching the filter. An absence of attribute selection shall return the complete information of the Service Objects matching the filter the authorized consumer is allowed to query. - -The Query operation shall support returning information about one or a set of service objects (i.e., list/array of service objects). The Query Service Operation shall support the ability to handle a large amount of data in return sets as described in ETSI GS NFV-SOL 013 [22], clause 5.4.2.1. - -As a result of this operation, the producer (O-Cloud) shall indicate to the consumer whether the query was processed successfully. If the operation is not successful, the O-Cloud shall return to the consumer appropriate error information. An example of an error case is where the query filter is malformed, or attributes are not able to be processed. - -The Alarm Dictionary Discovery and Performance Dictionary Discovery are pertinent use cases for this Service Operation. Those relate to this operation because the dictionary data for those use cases are contained within the Inventory Objects associated with this Service. See O-RAN WG6.ORCH-USE-CASES [23], clause 3.7.9, and 3.8.11 respectively for more details. - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23], clause 4.3. The following identifiers uniquely specify the requirements applicable to the producer (O-Cloud) for this operation: [REQ-ORC-O2-53]. - -##### 2.1.2.2.2 O-Cloud Inventory Event Notifications - -The O2ims\_InfrastructureInventory service shall provide a consumer who has established a valid subscription to be notified when an event which matches the subscription filter selection criteria to be sent to the consumer (SMO). - -NOTE: It is up to the protocol and data model specification to determine the one or various protocol operations enabling the authorized consumer to subscribe to the notification service, and to allow the notification service to invoke the specified callback procedure. - -Table 2.1.2.2.2-1 lists the information flow exchanged between the SMO and the O-Cloud. - -**Table 2.1.2.2.2-1: O2ims Inventory Subscribe/Notify operation** - -| Message | Direction | -|------------------------------------------|---------------| -| SubscribeInfrastructureInventoryRequest | SMO → O-Cloud | -| SubscribeInfrastructureInventoryResponse | O-Cloud → SMO | -| InfrastructureInventoryEventNotification | O-Cloud → SMO | - -The information representing one subscription shall follow the provisions indicated in table 2.1.2.2.2-2. - -**Table 2.1.2.2.2-2: Attributes of the InfrastructureInventoryEvent** - -| Attribute | Qualifier | Description | -|------------------------|-----------|---------------------------------------------------------------------------------------------------------------------------| -| consumerSubscriptionId | M | The consumer may provide its identifier for tracking, routing, or identifying the subscription used to report the event. | -| notificationEventType | M | The type (CREATE, MODIFY, DELETE) of event being reported | -| objectRef | M | The resultant reference to the object on which the action occurred | -| priorObjectState | M | If the Event type is 'MODIFY' or 'DELETE' this this field will be populated with a copy of the object prior to the event. | -| postObjectState | M | If the Event type is 'CREATE' or 'MODIFY' this this field will be populated with a copy of the object after the event. | - -The Alarm Dictionary Discovery and Performance Dictionary Discovery are pertinent use cases for this Service Operation. Dictionary data is sent via an O-Cloud Inventory Event Notification. See O-RAN WG6.ORCH-USE-CASES [23], clause 3.7.9, and 3.8.11 respectively for more details. - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23], clause 4. The following identifiers uniquely specify the requirements applicable to the producer (O-Cloud) for this operation: [REQ-ORC-GEN13], [REQ-ORC-O2-8]. - -### 2.1.3 O2ims\_InfrastructureMonitoring Services - -#### 2.1.3.1 Alarm Services - -Any object in the Infrastructure Inventory can generate faults. Also, a consumer such as the SMO may want to monitor the reachability of the IMS and therefore request a heartbeat message to be periodically sent. The O2ims\_InfrastructureMonitoring services provide these. IMS Heartbeat is not specified in the present document version. - -It is important to understand the differences between faults and alarms. All faults are logged, only some faults may be worthy of being an alarm. Policies within the IMS determine if a fault or set of faults warrant an alarm to be created. All Alarms are also logged. The following services are associated with alarms. - -##### 2.1.3.1.1 Service description - -The O-Cloud has a historical table of past and active alarms. The SMO or any other consumer with permissions can query this table for trending analysis, correlation, or synchronization. Additionally, the service provides the ability to subscribe to alarm events which are evaluated whenever a change occurs to an AlarmEventRecord. - -For a complete list of requirements see the O-Cloud Alarm related use cases in O-RAN WG6.ORCH-USE-CASES [23]. - -##### 2.1.3.1.2 Service operations - -###### 2.1.3.1.2.1 Query Alarm Information - -The O2ims\_InfrastructureMonitoring service shall enable an authorized consumer to query and retrieve AlarmEventRecord information related to the O-Cloud infrastructure and its resources. - -NOTE: It is up to the protocol and data model specification to determine the one or various protocol operations enabling the authorized consumer to retrieve the O-Cloud information. - -The information elements of an AlarmEventRecord are specified in the O-Cloud Information Model, see O-RAN WG6.O-CLOUD-IM [36], clause 4.2.1.4.10. - -Table 2.1.3.1.2.1-1 lists the information flow exchanged between the SMO and the O-Cloud. - -**Table 2.1.3.1.2.1-1: Query O2ims\_InfrastructureAlarmInformation operation** - -| Message | Direction | -|--------------------------|---------------| -| QueryOcloudAlarmRequest | SMO → O-Cloud | -| QueryOcloudAlarmResponse | O-Cloud → SMO | - -The input parameters sent when invoking the operation shall support means to: - -- Filter to select which information is queried about the supported service objects specified in clause 2.1.3.1.2. Filtering by names, identifiers, metadata information and status information shall be supported. -- Select the list of attributes of information of the supported service objects to be returned matching the filter. An absence of attribute selection shall return the complete information of the service objects matching the filter the authorized consumer is allowed to query. - -The query operation shall support returning information about one or a set of service objects (i.e., list/array of service objects). - -As a result of this operation, the producer (O-Cloud) shall indicate to the consumer whether the query was processed successfully. If the operation is not successful, the O-Cloud shall return to the consumer appropriate error information. - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23]. The following identifiers uniquely identify the requirements applicable to this operation: [REQ-ORC-O2-17], [REQ-ORC-O2-18], [REQ-ORC-O2-21], [REQ-ORC-O2-22], [REQ-ORC-O2-25]. - -###### **2.1.3.1.2.2 Infrastructure Alarm Acknowledge** - -The O2ims\_InfrastructureMonitoring service shall enable an authorized consumer to acknowledge an AlarmEventRecord recorded in the IMS. - -NOTE: It is up to the protocol and data model specification to determine the one or various protocol operations enabling the authorized consumer to acknowledge an alarm. - -Table 2.1.3.1.2.2-1 lists the information flow exchanged between the SMO and the O-Cloud. - -**Table 2.1.3.1.2.2-1: O2ims\_InfrastructureAlarmAcknowledge operation** - -| Message | Direction | -|----------------------------------------|---------------| -| AcknowledgeInfrastructureAlarmRequest | SMO → O-Cloud | -| AcknowledgeInfrastructureAlarmResponse | O-Cloud → SMO | - -The input parameters sent when invoking the operation shall support the means to: - -- identify the specific AlarmEventRecord to be acknowledged. - -As a result of this operation, the producer (O-Cloud) shall indicate to the consumer whether the AlarmEventRecord was acknowledged successfully. If the operation is not successful, the O-Cloud shall return to the consumer appropriate error information. - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23]. The following identifiers uniquely identify the requirements applicable to this operation: [REQ-ORC-O2-27], [REQ-ORC-O2-29] - -###### **2.1.3.1.2.3 Infrastructure Alarm Clear** - -The O2ims\_InfrastructureMonitoring service shall enable an authorized consumer to clear an AlarmEventRecord recorded in the IMS which requires manual clearing by its definition in the alarm dictionary. - -NOTE: It is up to the protocol and data model specification to determine the one or various protocol operations enabling the authorized consumer to clear an alarm. - -Table 2.1.3.1.2.3-1 lists the information flow exchanged between the SMO and the O-Cloud. - -**Table 2.1.3.1.2.3-1: O2ims\_InfrastructureAlarmClear operation** - -| Message | Direction | -|----------------------------------|---------------| -| ClearInfrastructureAlarmRequest | SMO → O-Cloud | -| ClearInfrastructureAlarmResponse | O-Cloud → SMO | - -The input parameters sent when invoking the operation shall support the means to: - -- identify the specific AlarmEventRecord to be cleared. - -NOTE: If the identified entry is defined with a clearing type of AUTOMATIC then it is up to the cloud vendor implementation on how this will affect the AlarmEventRecord and the ClearInfrastructureAlarmResponse. One example implementation may allow manual clear of an automatic alarm and if the O-Cloud re-detects the fault a new alarm is issued. Another implementation example may reject the request and leave the AlarmEventRecord unchanged. - -As a result of this operation, the producer (O-Cloud) shall indicate to the consumer whether the AlarmEventRecord was cleared successfully. If the operation is not successful, the O-Cloud shall return to the consumer appropriate error information. - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23]. The following identifiers uniquely identify the requirements applicable to this operation: [REQ-ORC-O2-28], [REQ-ORC-O2-30]. - -###### 2.1.3.1.2.4 Infrastructure Alarm Event Notifications - -The O2ims\_InfrastructureMonitoring service shall provide a consumer who has established a valid subscription to alarms to be notified when an event which matches the subscription filter criteria to be sent to the consumer (SMO). - -NOTE: It is up to the protocol and data model specification to determine the one or various protocol operations enabling the authorized consumer to subscribe to the notification service, and to allow the notification service to invoke the specified callback procedure. - -Table 2.1.3.1.2.4-1 lists the information flow exchanged between the SMO and the O-Cloud. - -**Table 2.1.3.1.2.4-1: O2ims Alarm Subscribe/Notify operation** - -| Message | Direction | -|--------------------------------------|---------------| -| SubscribeInfrastructureAlarmRequest | SMO → O-Cloud | -| SubscribeInfrastructureAlarmResponse | O-Cloud → SMO | -| InfrastructureAlarmEventNotification | O-Cloud → SMO | - -The information sent in an InfrastructureAlarmEventNotification shall contain the information specified in the AlarmEvent as specified in the O-Cloud Information Model, see O-RAN WG6.O-CLOUD-IM [36], clause 4.2.1.4.11. As a result of this operation, the producer (O-Cloud) shall indicate to the consumer whether the subscription was processed successfully. If the operation is not successful, the O-Cloud shall return to the consumer appropriate error information. - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23]. The following identifiers uniquely identify the requirements applicable to this operation: [REQ-ORC-O2-14], [REQ-ORC-O2-15], [REQ-ORC-O2-23], [REQ-ORC-O2-24] - -###### 2.1.3.1.2.5 Infrastructure Alarm Purge - -Normally alarms are removed from the AlarmList when they age past the retentionPeriod. The Infrastructure Alarm Purge operation deletes inactive and acknowledged alarms based on parameters in the InfrastructureAlarmPurgeRequest from the alarm list irrespective of the retentionPeriod. - -The Alarm Purge operation is requested by the service consumer (SMO). To see a complete description of this operation, refer to O-RAN.WG6.ORCH-USE-CASES [23], clause 3.7.13. - -Table 2.1.3.1.2.5-1 lists the information flow exchanged between the SMO and the O-Cloud in a request/response pattern. - -**Table 2.1.3.1.2.5-1: O2ims\_InfrastructureAlarmPurge operation** - -| Message | Direction | -|----------------------------------|---------------| -| InfrastructureAlarmPurgeRequest | SMO → O-Cloud | -| InfrastructureAlarmPurgeResponse | O-Cloud → SMO | - -The input parameters sent when invoking the operation shall support the means to: - -- identify the specific AlarmEventRecord(s) to be purged based on attributes of the AlarmEventRecord described in the O-Cloud Information Model, see O-RAN WG6.O-CLOUD-IM [36], clause 4.2.1.4.10. - -When this operation is successful, it will result in AlarmEventRecords contained in the AlarmList to be removed irrespective of the retentionPeriod. - -The full requirements definitions can be found in O-RAN.WG6.ORCH-USE-CASES [23], clause 4.3. The following identifiers uniquely specify the requirements applicable to this operation: [REQ-ORC-O2-98]. - -###### 2.1.3.1.2.6 Alarm List Configure - -The Alarm List Configure enables the SMO to view/set attributes which configure the behavior of Alarm List Management at the IMS. The request for Alarm List Configure is sent from the FOCOM towards the IMS. The request - -has parameters which describe the attributes associated with an Alarm List to be configured. To see a complete description of the Alarm List Configure operation, refer to O-RAN.WG6.ORCH-USE-CASES [23], clause 3.7.11. - -The IMS keeps all the current alarms in an Alarm List. The Retention Period of alarms can be changed by the Alarm List Configure operation. After the Retention Period expires, alarms in the Alarm List will be purged or archived based on alarm policy. For example, the Alarm List Configure request could have an attribute to specify to Retention Period by the IMS of Compute Node alarms (resource types) for 72 hours. When the current value of the `retentionPeriod` is reduced then the Alarm Purge Use Case is triggered, found in O-RAN.WG6.ORCH-USE-CASES [23], clause 3.7.13. - -Another Alarm List Configure operation could adjust the value(s) in the Extension attribute list of the Alarm List. Additional extensions attributes in the Alarm List Management request could change other aspects of Alarm List Management behavior. This would allow for implementation specific behavior. For example, an extension attribute might cause alarms to be purged or archived based on triggers. Extensions might define overflow behavior, or Alarm List composition handling. - -Table 2.1.3.1.2.6-1 lists the information flow exchanged between the SMO and the O-Cloud in a request/response pattern over O2 IMS. - -**Table 2.1.3.1.2.6-1: O2ims\_AlarmListConfigure operation** - -| Message | Direction | -|----------------------------|---------------| -| AlarmListConfigureRequest | SMO → O-Cloud | -| AlarmListConfigureResponse | O-Cloud → SMO | - -The input parameters sent when invoking the operation shall support the means to modify the attributes of the `AlarmList` as specified in the O-Cloud Information Model, see O-RAN WG6.O-CLOUD-IM [36], clause 4.2.1.4.13: - -- Provide updated values of the Retention Period applicable to the alarms in the Alarm List, and -- Provide values for the extension attribute list applicable to the Alarm List. - -When this operation is successful, it will result in a change of the Alarm List management behavior. - -The full requirements definitions can be found in O-RAN.WG6.ORCH-USE-CASES [23], clause 4.3. The following identifiers uniquely specify the requirements applicable to this operation: [REQ-ORC-O2-74]. - -#### 2.1.3.2 Void - -#### 2.1.3.3 Void - -### 2.1.4 O2ims\_InfrastructureProvisioning Services - -#### 2.1.4.1 O-Cloud Node Cluster and Infrastructure Declarative Service - -##### 2.1.4.1.1 Service description - -The O-Cloud Node Cluster and Infrastructure Declarative Service provides services for allocating, deallocating, and configuring O-Cloud Resources based on a declarative target request, referred as `ProvisioningRequest`. By means of the `ProvisioningRequest`, the consumer (SMO) can request to provision an O-Cloud Node Cluster and/or O-Cloud Infrastructure Resource(s). - -Additionally, the O-Cloud Node Cluster and Infrastructure Declarative Service offers the capability to a consumer of listing and reading existing `ProvisioningRequests`. This includes reading the status of ongoing creation, update, and deletion operations related to the declarative target execution of the `ProvisioningRequests`. - -##### 2.1.4.1.2 Service operations - -###### 2.1.4.1.2.1 ProvisioningRequest Management Operations - -According to the O-RAN WG6.O-CLOUD-IM [36], the `ProvisioningRequest` represents a request for item(s), such as an O-Cloud Node Cluster and/or O-Cloud Infrastructure Resource(s), to be provisioned within the O-Cloud. The `ProvisioningRequest` is a declarative target request issued by the SMO to the O-Cloud via the O-Cloud Node Cluster and Infrastructure Declarative service over the O2ims interface. O-Cloud Node Cluster and Infrastructure Declarative service operations follow a request-response pattern. Table 2.1.4.1.2.1-1 lists the service operations requested from the SMO to the O-Cloud to manage `ProvisioningRequest`. - -**Table 2.1.4.1.2-1 List of Service operations to manage ProvisioningRequest** - -| Message | Direction | -|------------------------------------------------|---------------| -| ProvisioningRequestCreateRequest | SMO → O-Cloud | -| ProvisioningRequestCreateResponse | O-Cloud → SMO | -| ProvisioningRequestReadRequest | SMO → O-Cloud | -| ProvisioningRequestReadResponse | O-Cloud → SMO | -| ProvisioningRequestUpdateRequest | SMO → O-Cloud | -| ProvisioningRequestUpdateResponse | O-Cloud → SMO | -| ProvisioningRequestDeleteRequest | SMO → O-Cloud | -| ProvisioningRequestDeleteResponse | O-Cloud → SMO | - -Figure 2.1.4.1.2.1-1 depicts in a single diagram all the different Service operations on a `ProvisioningRequest`. - -NOTE: For simplicity and readability reasons, the response from the O-Cloud to SMO for each Service operations are not depicted in the Figure 2.1.4.1.2.1-1. - -![Sequence diagram showing service operations on a ProvisioningRequest between FOCOM and IMS.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) - -``` - -sequenceDiagram - participant FOCOM as Service Management & Orchestration Framework (FOCOM) - participant IMS as O-Cloud Platform (IMS) - - rect rgb(255, 255, 255) - Note over FOCOM, IMS: Create ProvisioningRequest - FOCOM->>IMS: 1 Create ProvisioningRequest - Note right of IMS: Create ProvisioningRequest object and -add the object to existing list of ProvisioningRequest objects - IMS->>IMS: 2 Processing ProvisioningRequest object, -once the request is accepted - opt - Note over FOCOM, IMS: Get ProvisioningRequest object status through -"Read ProvisioningRequest object" service operation - end - end - - rect rgb(255, 255, 255) - Note over FOCOM, IMS: Read a list of ProvisioningRequests and/or a ProvisioningRequest object - FOCOM->>IMS: 3 Read a list of existing ProvisioningRequests - FOCOM->>IMS: 4 Read a ProvisioningRequest object - end - - rect rgb(255, 255, 255) - Note over FOCOM, IMS: Update ProvisioningRequest object - FOCOM->>IMS: 5 Update ProvisioningRequest object - IMS->>IMS: 6 Processing ProvisioningRequest object, -once the request is accepted - opt - Note over FOCOM, IMS: Get ProvisioningRequest object status through -"Read ProvisioningRequest object" service operation - end - end - - rect rgb(255, 255, 255) - Note over FOCOM, IMS: Delete ProvisioningRequest object - FOCOM->>IMS: 7 Delete ProvisioningRequest object - IMS->>IMS: 8 Processing ProvisioningRequest object, -once the request is accepted - Note right of IMS: Delete ProvisioningRequest object - opt - Note over FOCOM, IMS: Get ProvisioningRequest object status through -"Read ProvisioningRequest object" service operation - end - end - -``` - -Sequence diagram showing service operations on a ProvisioningRequest between FOCOM and IMS. - -**Figure 2.1.4.1.2.1-1 Service operations on a ProvisioningRequest** - -The information sent in a `ProvisioningRequest` shall include the information specified in the `ProvisioningRequest` as outlined in the O-Cloud Information Model, see O-RAN WG6.O-CLOUD-IM [36], clause 4.2.4.4.1. In response to this operation, the producer (O-Cloud) shall indicate to the consumer (SMO) whether the request has been accepted for processing. If the request is not accepted, the O-Cloud shall return appropriate error information to the consumer. - -The processing of the `ProvisioningRequest` is an asynchronous operation, where requested fulfilment of the given declarative target of the `ProvisioningRequest` can or cannot be fulfilled, as processing can fail during its execution. If or when the `ProvisioningRequest` is eventually fulfilled or fails, the producer (O-Cloud) shall update the `ProvisioningRequest` status by updating the `provisioningPhase`. For more details, see O-RAN WG6.O-CLOUD-IM [36], clause 4.2.4.4.2. - -The consumer (SMO) can send a read request for the `ProvisioningRequest`, for instance, while it is under processing and receive the current status of the `ProvisioningRequest`. The response to the read `ProvisioningRequest` will indicate the provisioning phase by means of the "provisioningPhase" attribute information. - -The create and update O-Cloud Node Cluster using O-Cloud Template are applicable use cases for this service operations. See O-RAN WG6.ORCH-USE-CASES [23], clause 3.11.2.3 and 3.11.4.3 for more details. - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23], clause 4. The following identifiers uniquely specify the requirements applicable to the producer (O-Cloud) for this operation: [REQ-ORC-O2-49], [REQ-ORC-O2-92], [REQ-ORC-O2-93], [REQ-ORC-O2-108] and the requirement applicable to the consumer (SMO) for this operation: [REQ-ORC-O2-91], [REQ-ORC-O2-107]. - -### 2.1.5 O2ims\_InfrastructureSoftwareManagement Services - -#### 2.1.5.1 Service description - -The `O2ims_InfrastructureSoftwareManagement` services support procedures that enable SMO/FOCOM to initiate the software update process for the O-Cloud Infrastructure Management software, the Deployment Management software, Server OS Software, updates, and patches, and firmware updates for accelerators. For initial release the O-Cloud software can be manually updated. Therefore, the orchestrated Software Update procedure is deferred FFS. - -### 2.1.6 O2ims\_InfrastructureLifecycleManagement Services - -#### 2.1.6.1 Service description - -Although O-Clouds are usually built for future capacity, they are not static. Physical resources can become defective or obsolete. Also, the O-Cloud may grow beyond its initial deployed capacity. These activities represent life cycle events to the O-Cloud. Automation is expected to offload manual processes due to the high numbers expected of O-Cloud instances. `O2ims_InfrastructureLifecycleManagement` Services support procedures for the automation of O-Clouds lifecycle events. - -#### 2.1.6.2 Service operations - -Primary Use cases for O-Cloud Genesis and O-Cloud Scaling are FFS. However, for this release the Notification to a callback specified at the onset of O-Cloud Genesis is defined. - -##### 2.1.6.2.1 O-Cloud Available Event Notification - -The `O2ims_InfrastructureLifecycle` service shall provide a consumer who was established at the onset of O-Cloud Genesis. Data expected to be included with the callback URI in the genesis data is the `globalCloudId`, each `globalLocationID`, and each `AssetID` for infrastructure at those locations. Once enough of the O-Cloud is discovered, provisioned and is available for additional provisioning or workload deployments, the O-Cloud shall send the `O-CloudAvailableEvent` to the consumer (SMO), thus registering its `InfrastructureManagementServiceEndPoint` with the SMO. After receiving the notification, the SMO will interrogate the `InfrastructureInventory` APIs to account for corporate assets and discover the DMS service endpoints to allow workloads to be deployed. - -NOTE: It is up to the protocol and data model specification to determine the one or various protocol operations enabling the notification service to invoke the specified callback procedure. - -Table 2.1.6.2.1-1 lists the information flow exchanged between the SMO and the O-Cloud. - -**Table 2.1.6.2.1-1: O2ims Lifecycle Notification operation** - -| Message | Direction | -|------------------------------------------|---------------| -| OCloudAvailableNotification | O-Cloud → SMO | - -The information representing O-Cloud Available Notification shall follow the provisions indicated in the O-Cloud Information Model, see O-RAN WG6.O-CLOUD-IM [36], clause 4.2.1.4.9. - -### 2.1.7 O2ims\_InfrastructurePerformance Services - -#### 2.1.7.1 Service description - -The Service Operations described in the following clauses relate to Performance Management functions. These operations fall into four basic categories: Performance Measurement Job, Performance Management Reporting, Performance Management Subscription handling, and Performance Management configuration. Each of these service operations relates to the four areas in the Information Model related to Performance Management: Performance Measurement Store, Performance Measurement Report, Performance Subscription and Performance Measurement Jobs. See the O-RAN WG6.O-CLOUD-IM [36] for more details. The functions described in the following service operations collectively provide fundamental operations which enable a management system, such as the SMO, to setup Performance Measurement Jobs, to establish Performance Management Subscriptions (to receive reports), to configure Performance Management behaviour, and to interact with a Performance Measurement Store. - -There are Service Operations to Create, Query, Delete, Update, Suspend and Resume Performance Measurement Jobs. There are also Service Operations for Performance Management Subscription Query, Performance Management Subscription Update and Performance Management Subscription Delete. Once running, an entity, such as the SMO, can establish Performance Management Subscriptions to receive the collected Performance Measurements. - -Service Operations relate to functioning of both kinds of Performance Measurement Jobs. Within the O-Cloud, there are Performance Measurement Jobs and preinstalled Performance Measurement Jobs. These have the function of collecting Performance Measurements from O-Cloud Resources and storing them into a Performance Measurement Store. - -The behaviour of Performance Management reporting can be controlled by Performance Management Service Operations. There are three ways that an entity could receive Performance Measurement reports: through file reporting, notification reporting or streaming. Service Operations can also alter the Performance Management behaviour through the Performance Management Configure Service Operation, the Performance Measurement Job Update Service Operation, and Performance Management Subscription Update Service Operation. - -#### 2.1.7.2 Service operations - -##### 2.1.7.2.1 Performance Measurement Job Query - -Performance Measurement (PM) Jobs collect performance data on O-Cloud infrastructure resources. The O2ims\_InfrastructureMonitoring service shall enable an authorized consumer to query and retrieve PerformanceMeasurementJob information and its attributes for PM Jobs that reside in the O-Cloud. - -The PM Job Query Service enables a consumer to: - -- Query for all PM Jobs in the Active State including default PM Jobs (based on Owner). -- Query for PM Jobs in the Suspended State. -- Query for PM Jobs in the Deprecated State because of delete operations that have not yet been purged. -- Query for certain PM Jobs by indicating specific PM Job IDs in the query filter. - -NOTE 1: It is up to the protocol and data model specification to determine the one or various protocol operations enabling the authorized consumer to retrieve the Performance Measurement Job information. - -Table 2.1.7.2.1-1 lists the information flow exchanged between the SMO and the O-Cloud using the request-response pattern. - -**Table 2.1.7.2.1-1: O2ims\_PerformanceMeasurementJobQuery operation** - -| Message | Direction | -|----------------------------------------|---------------| -| PerformanceMeasurementJobQueryRequest | SMO → O-Cloud | -| PerformanceMeasurementJobQueryResponse | O-Cloud → SMO | - -The input parameters sent when invoking the operation shall support the means to: - -- Specify a filter that defines the selection of PM Jobs to be included in the results. The attributes for filtering of the `PerformanceMeasurementJob` Information Object Class are specified in O-Cloud Information Model, see O-RAN WG6.O-CLOUD-IM [36], clause 4.2.1.4.16. Thus, the filter supports the requests based on PM Job IDs, PM Job status, PM Job owner, and PM Job states. -- Specify the list of associated attributes for the filtered PM Jobs to be returned in the results. An absence of attribute specification shall return the complete information of filtered PM Jobs back to the requestor. - -NOTE 2: There is only one filter and only one list of associated attributes. Thus, for all filtered PM Jobs the request returns the same set of associated attributes. - -The PM Job query operation shall support returning information about one or a set of filtered PM Jobs. The service operation shall support the ability to handle a large amount of data in return sets as described in ETSI GS NFV-SOL 013 [22], clause 5.4.2.1. - -As a result of this operation, the producer (O-Cloud) shall indicate to the consumer whether the query was processed successfully. If the operation is not successful, the O-Cloud shall return to the consumer appropriate error information. - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23], clause 4.3. The following identifiers uniquely specify the requirements applicable to the producer (O-Cloud) for this operation: [REQ-ORC-O2-57]. - -##### 2.1.7.2.2 Performance Management Configure - -The Performance Management Configure Service operation enables a requesting entity, such as the SMO, to configure the behavior of the Performance Management system. - -This Service Operation complements the Performance Measurement Job Creation Service Operation, Performance Measurement Job Update Service Operation, Performance Management Subscription Service Operation and, Performance Management Subscription Update Service Operation which are other Service Operations that can alter the behavior of Performance Management functionality. - -The Performance Management Configure Service Operation enables a requesting entity, such as the SMO, to modify the Retention Period attribute or the Extension attribute list in the `PerformanceMeasureStore`. - -The Performance Management Configure Service Operation can be used to adjust the value(s) in the Extension attribute list of the `PerformanceMeasurementStore`. Updates to the Extensions attribute list from the Performance Management Configure request can change other aspects of Performance Management behavior, hence enabling for implementation specific behavior. - -The Retention Period is described in the O-RAN.WG6.O2-GA&P [24], clause 3.9.11 and in the O-Cloud Information Model, see O\_RAN WG6.O-CLOUD-IM [36], clause 4.2.1.4.14.2. - -Table 2.1.7.2.2-1 lists the information flow exchanged between the SMO and the O-Cloud in a request/response pattern over the O2ims interface. - -**Table 2.1.7.2.2-1: O2ims\_PerformanceManagementConfigure operation** - -| Message | Direction | -|-----------------------------------------|---------------| -| PerformanceManagementConfigure Request | SMO → O-Cloud | -| PerformanceManagementConfigure Response | O-Cloud → SMO | - -The input parameters sent when invoking this Service Operation shall support the means to: - -- Identify the objects with the attributes to configure. For updating the Retention Period or Extension attributes, this relates to the Performance Measurement Store object. -- Provide updated value of the Retention Period for the requested object to be configured. -- Provide updated value(s) for the Extension attribute list of the requested object(s) to be configured. - -When this Service Operation is successful, it will result in modification of the Performance Management behavior. - -A description of the Performance Management Configuration Use Case which is relevant to this Service Operation can be found in O-RAN.WG6.ORCH-USE-CASES [23], clause 3.8.15. - -The full requirements definitions can be found in O-RAN.WG6.ORCH-USE-CASES [23], clause 4.3. The following identifiers uniquely specify the requirements applicable to this operation: [REQ-ORC-O2-100]. - -##### 2.1.7.2.3 Performance Measurement Job Create - -Performance Measurement Jobs collect performance measurements and metrics on O-Cloud infrastructure resources. The O2ims\_ InfrastructureMonitoring service shall enable an authorized consumer to create a Performance Measurement Job in the O-Cloud over the O2 interface. The requested Performance Measurement Job would be in addition to the Preinstalled Performance Measurement Jobs that would already be running in the O-Cloud. For further information on Performance Measurement Jobs, see O-RAN WG6 O2 GA&P [24], Clause 3.9.5. For further information on the Performance Measurement Job Creation Use Case, see O-RAN WG6 ORCH-USE-CASES [23], Clause 3.8.1. - -To create a Performance Measurement Job, a requestor would provide the following upon invoking the service operation: - -- Consumer Performance Job Id – This is an identifier provided by the consumer for purposes of managing PM Jobs. This value could be the same across multiple instances of a PM Job. -- Collection Interval - This is provided by the requestor at time of Performance Measurement Job creation to define the interval at which performance measurements will be collected and stored. -- Resource Scope Criteria – The Resource Scope Criteria determines the value set for the Qualified Resource Types. It allows for the requestor of the Service Operation to indicate the list of Resources of interest from which measurements are to be collected. This criterion determines, the value set for the Qualified Resource Types (See Note). -- Measurement Selection Criteria – This is provided by the requestor at time of Performance Measurement Job creation to describe the measurements and/or resources that the PM Job is responsible for collecting and calculating. If a Resource Type is specified in the order, then the Performance Measurement Job operations applies to all resources of that Resource Type. From the Resource Scope Criteria, the Resource Types of interest can be calculated and from that the relevant PM Dictionaries. The Measurement Selection Criteria can then use these PM Dictionaries to identify the measurements of interest. -- Extensions - These are unspecified properties (key/value) which extend the information provided about the Performance Measurement Job - -NOTE: It is up to the protocol and data model specification to determine the one or various protocol operations enabling the authorized consumer to retrieve the Performance Measurement Job information. - -Table 2.1.7.2.3-1 lists the information flow exchanged between the SMO and the O-Cloud using the request-response pattern. - -**Table 2.1.7.2.3-1: O2ims\_PerformanceMeasurementJobCreate operation** - -| Message | Direction | -|-----------------------------------------|---------------| -| PerformanceMeasurementJobCreateRequest | SMO → O-Cloud | -| PerformanceMeasurementJobCreateResponse | O-Cloud → SMO | - -The input parameters sent when invoking the operation shall support the means to: - -- Specify an order that defines the Resource Scope Criteria, Measured Resources and Resources Type which indicates the pertinent resources for the Performance Measurement Job. From these the relevant PM Dictionaries can be identified. -- Specify an order that defines the Measurement Selection Criteria that the Performance Measurement Job would be responsible for. The relevant attributes given in an order to create a - -PerformanceMeasurementJob Information Object Class are specified in O-Cloud Information Model in O-RAN WG6.O-CLOUD-IM [36], see clause 4.2.1.4.16.2. - -As a result of the PM Job Create service operation, the producer (O-Cloud) shall indicate to the consumer whether the PM Job Create service operation was processed successfully. As a result, this operation will return the status of the newly created PM jobs running in the IMS. If the operation is not successful, the O-Cloud shall return to the consumer the appropriate error information. - -The producer determines the Measured Resources as a list of Resources relevant to the PM Job; it is a read-only attribute derived from the Measurement Selection Criteria. Furthermore, the Collected Measurements are derived from the Resource Scope Criteria and Measurement Selection Criteria; this gives the measurements to be collected by the PM Job. - -The Qualified Resource Types are computed from the evaluation of the Measurement Selection Criteria, thus is derived during the PM Job Create Service Operation. It is also part of the Information Model. These are byproducts of the operation inputs. The computation from the Resource Scope Criteria results in a unique set of Resource Types relevant to the PM Job create service operation. From those resources, Resource Types of interest can be calculated. From those, the associated PM Dictionaries can be deduced. From the Measurement Selection Criteria, the Qualified Measurements that the PM Job is responsible for are calculated. The Qualified Resource Type allows an operator to check these interim results. - -After the service operation is complete, the IMS puts the PM Job into the Active State; and it immediately starts collecting measurements based on its collection interval. - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23], clause 4.3. The following identifiers uniquely specify the requirements applicable to the producer (O-Cloud) for this operation: [REQ-ORC-O2-32]. - -##### 2.1.7.2.4 Performance Management Subscription Create - -The purpose of the Performance Management Subscription Create Service Operation is to create Subscriptions related to Performance Management. The Performance Management Subscription Create operation is vital because Subscriptions first need to be created before Performance Measurements Reports can be created by the producer. - -Each subscription is associated with one subscriber. Each subscriber can have many subscriptions. Each Subscriber (consumer) has a consumer subscription identifier. However, the value could be the same across multiple instances of IMS subscription instances. A subscription only supports one reporting mechanism. - -During the Query Information service operation, read-only attributes will provide an entity or the SMO with a capabilities assessment which indicate the protocol(s) supported for reporting, mechanism(s), and format(s) supported by the O-Cloud. Then, an entity or the SMO can subscribe to the mechanism(s) and format(s) by indicating them within the subscription filter. In the capabilities exchange, the IMS would report the Performance Measurement Jobs and their associated collection intervals. - -During the Performance Management Subscription Create Service Operation, the creation request will indicate an endpoint for where the Performance Measurement Report(s) will be sent to. The subscription filter qualifies what data from the Performance Measurement Jobs will be sent. The Performance Management Subscription Create Service Operation will indicate the Subscription reporting interval. Performance Measurements in an O-Cloud might be sent through event notification reporting, stream-based reporting, or file-based reporting to a subscriber. - -To create a Performance Management Subscription the following list explains the usage of the parameters that can be provided in service operation: - -- **Consumer Performance Subscription ID** – This identifier can be optionally provided to indicate a consumer performance subscription which may be used to manage performance data. This value could be the same across multiple instances of IMS subscription instances. -- **Resource and Resource Types** – The Resources and Resource Types of interest can be provided by the requestor of the Service Operation. -- **Measurement Selection Criteria** – This is provided by the requestor at time of Performance Management Subscription creation to describe the measurement(s) of interest. - -- **Report Delivery Mechanism** – This parameter indicates whether the subscription is expected to be fulfilled through Event Notifications, File-based reporting or through a Stream. For Event Notifications, performance data is sent at the specified intervals. For File-base reporting, a file is generated, which can then be retrieved by the consumer. For Stream based reporting, a session will remain open and continue to send the data in a streaming format, e.g., Google Protocol Buffers (GPB), at the specified intervals until the session or subscription is terminated. Reporting use cases can be found in O-RAN WG6.ORCH-USE-CASES [23], clause 3.8.3, 3.8.4 and 3.8.5. -- **Callback** – The Performance Subscription Creation operation can (optionally) provide an end point where Performance subscription reporting notifications are to be delivered. For File-based reporting, the Callback is an endpoint where a file ready notification is sent. For Event-based reporting, the Callback is an endpoint where a performance measurement report notification is sent. The field is not required if the report format is Stream because the Callback is not used. -- **Measurement Reporting Frequency** – This is used to establish Performance monitoring processes. This indicates the periodicity that specified performance data shall be sent. Each process definition can have a Subscription Mode, Report Interval, Suppress Redundant Flag, and Heartbeat Interval. The Subscription Mode can be *Target Defined*, *On Change*, or *Sampled*. If *Target Defined*, the behaviour of the producer will be to act as either *On Change* or *Sample*, as determined by the producer. If *On Change*, data is sent whenever the value changes. If it is *Sampled*, it is sent regularly with a periodicity of the Report Interval. If the Suppress Redundant Flag is set to true, the process shall not send data at the Sample Report Interval if the value has not changed unless the Heartbeat Interval is set to a non-zero value. If the Heartbeat Interval is set it will always send data samples regularly. -- **Remote File Location** – This provides a destination for the consumer to push Performance Files to. - -For file-based reporting, Performance Files produced in the O-Cloud can be retrieved by the consumer as in a pull paradigm. If a consumer wants to retrieve Performance Files, the callback is given in the Performance Subscription Create operation. When the Performance Files are ready, the callback is used as a notification endpoint for the O-Cloud to inform the consumer that the Performance Files are ready to be pulled. - -For file-based reporting, Performance Files can also be delivered by the producer as in a push paradigm. In this case, the consumer will provide a *Remote File Location* (as an attribute in the operation) that the producer (O-Cloud) can upload the Performance Files to. Here, the callback is the endpoint where the files ready notification is sent. This informs the consumer that the Performance Files have been uploaded. In the push paradigm, what happens to the files after the producer sends the Performance files to the remote file location is implementation specific. - -The Performance Subscription can establish multiple monitoring processes. Each of those can have different Reporting Frequencies. Each of those processes could have different Subscription Modes, with Target Defined (producer determined), On Change or reported at every Reporting Interval. It is also possible to have a process report data periodically as defined by a heartbeat interval regardless of change when the suppress redundancy is set to true. For example, one process within the Performance Subscription could report data only when a target changes value, another process within that same Performance Subscription may report data every 8 minutes (on the heartbeat interval). - -NOTE: It is up to the protocol and data model specification to determine the one or various protocol operations enabling the authorized consumer to do a Performance Management Subscription create operation. - -Table 2.1.7.2.4-1 lists the information flow exchanged between the SMO and the O-Cloud using the request, response, and notification patterns. - -**Table 2.1.7.2.4-1: O2ims\_PerformanceManagementSubscriptionCreate operation** - -| Message | Direction | -|-------------------------------------------------|---------------| -| PerformanceManagementSubscriptionCreateRequest | SMO → O-Cloud | -| PerformanceManagementSubscriptionCreateResponse | O-Cloud → SMO | -| FileReadyNotification | O-Cloud → SMO | - -The input parameters sent when invoking the operation shall support the means to: - -- **Consumer Performance Subscription ID** – This optional input parameter is a string without requirements on the format that can be provided by the requestor. This value could be the same across multiple instances of IMS subscription instances. - -- **Resources** – This would be provided in the Global Subscription Criteria. The Resources are key-value pairs that indicate the Resource(s) of interest for the subscription. -- **Resource Types** – This is provided in a Global Subscription Criteria. The Resource Types are key-value pairs that indicate the Resource Type(s) of interest for the subscription. -- **Measurement Selection Criteria** – This is provided in the Performance Management Subscription to describe the measurement(s) of interest. -- **Report Delivery Mechanism** – This parameter is provided indicating whether the Performance subscription is fulfilled via Event Notifications, File-based reporting, or Stream reporting. -- **Callback** – A Callback can be provided in the Performance Subscription as an endpoint to send Performance-related notifications to. -- **Measurement Reporting Frequency** – This is an array of definitions which is used to establish Performance monitoring processes. Each process definition can have a Subscription Mode, Report Interval, Suppress Redundant Flag, and Heartbeat Interval. -- **Remote File Location** – This provides a destination for the consumer to push Performance Files to. - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23], clause 4.3. The following identifiers uniquely specify the requirements applicable to the producer (O-Cloud) for this operation: [REQ-ORC-O2-38]. Requirements related to the endpoint for where the Performance Measurement Reports will be sent to are described [REQ-ORC-O2-39], [REQ-ORC-O2-40], [REQ-ORC-O2-42]. - -##### 2.1.7.2.5 Performance Measurement Job Delete - -Performance Measurement Jobs collect performance measurements and metrics on O-Cloud infrastructure resources. The O2ims\_InfrastructurePerformance service shall enable an authorized consumer to delete a Performance Measurement Job in the O-Cloud over the O2 interface. An authorized consumer needs to first suspend a Performance Measurement Job before it can be deleted. The Preinstalled Performance Measurement Jobs cannot be deleted. For further information on Performance Measurement Jobs, see O-RAN WG6 O2 GA&P [24], Clause 3.9.5. For further information on the Performance Measurement Job Delete Use Case, see O-RAN WG6 ORCH-USE-CASES [23], Clause 3.8.7. - -To delete a Performance Measurement Job, a requestor would provide the following upon invoking the service operation: - -- **Performance Measurement Job Id** – Identifier provided by the consumer that identifies Performance Measurement Job to be deleted. - -**NOTE:** To delete multiple Performance Measurement Jobs, the Performance Measurement Job Delete operation can be invoked separately for each Performance Measurement Job Id. This approach was chosen to minimize implementation complexity and avoid the significant technical overhead associated with bulk operations, particularly in handling various corner cases and ensuring transactional consistency. - -Table 2.1.7.2.5-1 lists the information flow exchanged between the SMO and the O-Cloud using the request-response pattern. - -**Table 2.1.7.2.5-1: O2ims\_PerformanceMeasurementJobDelete operation** - -| Message | Direction | -|---------------------------------------------|---------------| -| PerformanceMeasurementJobDeleteRequest | SMO → O-Cloud | -| PerformanceMeasurementJobDeleteResponse | O-Cloud → SMO | -| PerformanceMeasurementJobChangeNotification | O-Cloud → SMO | - -Prior to the deletion, the consumer should have suspended the Performance Measurement Job which it wants to delete. - -As a result of the Performance Measurement Job Delete service operation, the producer (O-Cloud) shall indicate to the consumer whether the Performance Measurement Job Delete service operation was processed successfully. As a result, this operation will return the status of the deleted Performance Measurement Job. If the operation is not successful, the O-Cloud shall return to the consumer the appropriate error information. - -When a Performance Measurement Job is successfully deleted and changes its status to “*DEPRECATED*”, a notification of that change is sent to all of consumer(s) that have been subscribing to the data collected by the deleted Performance Measurement Job. The deletion of a Performance Measurement Job shall also result in the deletion of any associated embedded PM subscription. - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23], clause 4.3. The following identifiers uniquely specify the requirements applicable to the producer (O-Cloud) for this operation: [REQ-ORC-O2-59], [REQ-ORC-O2-60], [REQ-ORC-O2-84]. - -##### 2.1.7.2.6 Performance Measurement Event Notification Reporting - -In the context of O-RAN Cloud managed systems, performance measurements can be transmitted by any of the following mechanisms: performance measurement event notification(s), performance measurement streaming based reporting, or performance measurement file-based reporting. The performance management subscription create service operation subscription filter defines the service connection end point where the event notifications shall be sent to. Event based notification are expected to be utilized for non-real time performance measurements and for situations that have a low frequency and low volume of reporting since a session is re-established with the sending of each performance measurement event notification. At higher data volumes a streaming session would be more efficient. See O-RAN WG6.ORCH-USE-CASES, clause 3.8.3 [23] for more details. - -This service model describes performance measurement event notification reporting to send performance data. An entity that subscribes to these performance event notifications will get a notification for each reporting message on the indicated notification callback endpoint. Notification reports are based on a performance management subscription. The performance subscription filters are described in the Performance Management Subscription Create Service Model. See Clause 2.1.3.2.2.4 for more information. Other service models in the present specification will describe the streaming based reporting and file-based reporting. - -The O2ims\_InfrastructurePerformance services shall provide a consumer who has established a valid subscription to be notified when an event which matches the subscription filter selection criteria to be sent to the consumer (SMO). - -NOTE: It is up to the protocol and data model specification to determine the one or various protocol operations enabling the authorized consumer to subscribe to the notification service, and to allow the notification service to invoke the specified callback procedure. - -Table 2.1.7.2.6-1 lists the information flow exchanged between the SMO and the O-Cloud for this service operation. The Performance Measurement Event Notification is used for reporting. - -**Table 2.1.7.2.6-1: O2ims\_PerformanceMeasurementEventNotification Reporting operation** - -| Message | Direction | -|-----------------------------------------|---------------| -| PerformanceMeasurementEventNotification | O-Cloud → SMO | - -There are three basic exception cases for this service operation: - -- CONNECTION LOST – If connectivity between the subscriber and the publisher (IMS) is lost, a connection would not be able to be opened. There are implementation considerations such as: how long data is held for, recovery of the connection, backing up data, preventing data storms upon recovery, and management after recovery. -- DATA UNAVAILABLE – This exception occurs when the performance measurement data is not available in the O-Cloud at the IMS when it should be reported. This results in a missed timing window when data was expected, but it was not available. In the O2 interface, it would be expected that the notification would indicate data was unavailable. There are implementation considerations such as: O-Cloud failures, IMS failures, data recovery, and data synchronization. -- PM JOB FAILURES & ISSUES – If the PM Job is unable to perform its function. If there are failures or issues with the PM Job(s) which might result in data being unavailable it is expected that there would alarms that would be raised by the IMS. This results in performance data being unavailable when it is needed to be reported. - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23], clause 4.3. The following identifiers uniquely specify the requirements applicable to the producer (O-Cloud) for this operation: [REQ-ORC-O2-39]. - -##### 2.1.7.2.7 Performance Measurement Job Update - -Performance Measurement Jobs collect performance measurements and metrics on O-Cloud Resources. The O2ims\_InfrastructurePerformance service enables an authorized consumer to update a Performance Measurement Job in the O-Cloud over the O2 interface. The Preinstalled Performance Measurement Jobs cannot be updated. Performance Measurement Job Update can occur for one of two reasons as described below: - -- **RESOURCE CHANGES** – O-Cloud Resource changes can cause a Performance Measurement Job to update. When O-Cloud Resources are updated, added, or deleted that a Performance Measurement Job depends on, the Performance Measurement Job update use case may be invoked. O-Cloud Resources changes can impact on the Performance Measurement Job measurement selection criteria, which triggers evaluation of the measured resources and collected measurements, and/or the resource scope criteria, which triggers evaluation of the qualified resource types and collected measurements. It is possible that the result of the O-Cloud Resource change may not alter the Performance Measurement Job. -- **UPDATE BY REQUEST** – A consumer may also request for an update to a Performance Measurement Job through a request operation. A consumer may request data collection updates (i.e. measurement selection criteria, resource scope criteria) and/or other updates (e.g. collection interval, extensions) for a Performance Measurement Job. This may occur autonomously from a consumer, for example through a policy trigger. Only a consumer with the proper permissions that owns the Performance Measurement Job can update the Performance Measurement Job. - -To update a Performance Measurement Job the following list explains the usage of the parameters that can be provided in the service operation: - -- **Consumer Performance Job ID** – This is an identifier optionally provided by the consumer for its purpose of managing Performance Measurement Job(s). -- **Resource Scope Criteria** – Key value pairs of resource attributes which are used to select the resources from which measurements are to be collected. -- **Measurement Selection Criteria** – Key value pairs that identify the distinct set of measurements within the scope of a Performance Measurement Job. -- **Collection Interval** – The interval at which performance measurements will be collected and stored. -- **Extensions** - These are key/value pairs which extend the information about the Performance Measurement Job. - -All consumer(s) who are subscribed to a Performance Measurement Job are notified via the PerformanceMeasurementJobChangeNotification when the Performance Measurement Job is updated. - -For further information on Performance Measurement Jobs, see O-RAN WG6 O2 GA&P [24], Clause 3.9.5. For further information on the Performance Measurement Job Update Use Case, see O-RAN.WG6. ORCH-USE-CASES [23], clause 3.8.8. - -Table 2.1.7.2.7-1 lists the information flow exchanged between the SMO and the O-Cloud using the request-response pattern. - -**Table 2.1.7.2.7-1: O2ims\_PerformanceMeasurementJobUpdate operation** - -| Message | Direction | -|---------------------------------------------|---------------| -| PerformanceMeasurementJobUpdateRequest | SMO → O-Cloud | -| PerformanceMeasurementJobUpdateResponse | O-Cloud → SMO | -| PerformanceMeasurementJobChangeNotification | O-Cloud → SMO | - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23], clause 4.3. The following identifiers uniquely specify the requirements applicable to the producer (O-Cloud) for this operation: [REQ-ORC-O2-67], [REQ-ORC-O2-68]. - -##### 2.1.7.2.8 Performance Management Subscription Query - -Performance Management Subscription encompasses a subscription mechanism dedicated to getting reports for Performance Measurements. The query of a Performance Management Subscription is the ability of an authorized entity to get the details of a Performance Management Subscription including its performance subscription filter. The other Performance Management Subscription related service operations include the ability to create, update, and delete a subscription. The Performance Management Subscription Query operation can be performed on a set of subscriptions or a single subscription. - -The Performance Management Subscription filter (applied to a list) in the service model defines the following for collecting and reporting Performance Measurements over O2ims. This operation can also be applied to a single subscription if a Subscription Identifier is provided. - -- **Performance Measurement Data** – The subscription filter qualifies what data from the Performance Measurement jobs shall be sent. -- **Timing Interval** – The subscription filter indicates the reporting timing interval. -- **Reporting Mechanisms** – The subscription filter specifies the reporting mechanisms (file-based reporting, stream-based reporting, event notification reporting). -- **Report Formats** – The subscription filter dictates the report formats. -- **Consumer Performance Subscription Identifiers** – The query filter can include the *Consumer Performance Subscription Identifier(s)*. - -The SMO can act as the consumer entity performing the query; however, it can also be another authorized user, technician, or machine (e.g. software, script, etc.). A typical use case for using the subscription query is to cross-check the Performance Management Subscription of the consumer. Though, it can also be utilized for other management purposes as well. - -It is expected that the Performance Management Subscription Create operation will have been performed prior to a query operation. However, if a Performance Management Subscription Query has a mixture of valid and non-existing subscriptions, the operation will only return information about the content that does exist (this is not an exception case). Table 2.1.7.2.8-1 lists the information flow exchanged between the SMO and the O-Cloud for this service operation. The Performance Measurement Event Notification is used for reporting. - -**Table 2.1.7.2.8-1: O2ims\_PerformanceManagementSubscriptionQuery operation** - -| Message | Direction | -|------------------------------------------------|---------------| -| PerformanceManagementSubscriptionQueryRequest | SMO → O-Cloud | -| PerformanceManagementSubscriptionQueryResponse | O-Cloud → SMO | - -Aside from unexpected condition exception, the only other exception case for this service operation is: - -- **QUERY OF NON-EXISTING PERFORMANCE SUBSCRIPTION** – If the query operation results in no Performance Management Subscription that matches the query filter, then a “Performance Management Subscription not found” is issued back to the requestor. - -Details about the Performance Management Subscription Query filter (applies to a subscription list) are as follows. This operation can also be applied to a single subscription if a Subscription Identifier is provided. - -- **Performance Measurement Data** - The subscription query filter qualifies the data of interest that is collected by Performance Management Subscription(s). A Subscription Query service operation returns Subscriptions that are providing that data of interest. The filter can specify a set of collected Measurements, see O-RAN WG6.O-Cloud-IM [36], clause 4.2.1.4.18 for more details. - -- **Timing Interval** – This relates to the reporting timing interval for how often data is reported. In the Subscription Query service operation, the filter indicates the reporting timing of interest. This will cause the service operation to return subscription(s) that have the timing cadence specified in the filter. -- **Reporting Mechanisms** – This will cause the Subscription Query service operation to return subscription(s) that match the reporting mechanisms specified in the filter. The reporting mechanisms indicate the type of reporting that is of interest whether file-based reporting, stream-based reporting, or event notification reporting. -- **Report Formats** – The filter can indicate the report formats of interest. The format is either File-based, Streaming or Notification based reporting. -- **Consumer Performance Subscription Identifiers** – The query filter can include the *Consumer Performance Subscription Identifier(s)*. The service operation will return those subscription(s) that match the *Consumer Performance Subscription Identifier(s)* if available. This value can be the same across multiple instances of IMS subscription instances. - -The full requirements related to the present service operation are specified in O-RAN WG6.ORCH-USE-CASES [23], clause 4.3. The following identifiers uniquely specify the requirements applicable to the producer (O-Cloud) for this operation: [REQ-ORC-O2-86]. - -##### 2.1.7.2.9 Performance Measurement Job Suspend - -Performance Measurement Jobs collect performance measurements and metrics on O-Cloud infrastructure resources. The O2ims\_InfrastructurePerformance service shall enable an authorized consumer to suspend a Performance Measurement Job in the O-Cloud over the O2 interface. The Preinstalled Performance Measurement Jobs cannot be suspended. - -Suspending a Performance Measurement Job might be done to improve system performance because Performance Measurement Jobs come at the cost of system overhead and computational cycles. Suspending a Performance Measurement Job will cause it to be inactive when its collection timer is triggered where it would normally collect data. - -The consumer request to suspend a Performance Measurement Job can specify a suspension timer, where the Performance Measurement Job is suspended for a specified time period, or specify the indefinite suspension of the Performance Measurement Job. Performance Measurement Jobs which are suspended indefinitely need a consumer request to resume operations for the Performance Measurement Job. - -All consumer(s) who are subscribed to a Performance Measurement Job are notified via the PerformanceMeasurementJobChangeNotification when the Performance Measurement Job is suspended. - -Table 2.1.7.2.9-1 lists the information flow exchanged between the SMO and the O-Cloud using the request-response pattern. - -**Table 2.1.7.2.9-1: O2ims\_PerformanceMeasurementJobSuspend operation** - -| Message | Direction | -|---------------------------------------------|---------------| -| PerformanceMeasurementJobSuspendRequest | SMO → O-Cloud | -| PerformanceMeasurementJobSuspendResponse | O-Cloud → SMO | -| PerformanceMeasurementJobChangeNotification | O-Cloud → SMO | - -The input parameters which can be sent when invoking the operation are: - -- Performance Measurement Job Id – the identity of the specific Performance Measurement Job(s) to be suspended. -- Suspension Timer - Provides a time window for the indicated Performance Measurement Job(s) to be suspended. If this parameter is not included, then the identified Performance Measurement Job(s) will remain suspended until such time as the consumer requests to resume the Performance Measurement Job. - -For further information on Performance Measurement Jobs, see O-RAN WG6 O2 GA&P [24], Clause 3.9.5. For further information on the Performance Measurement Job Suspend Use Case, see O-RAN.WG6. ORCH-USE-CASES [23], Clause 3.8.9. - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23], clause 4.3. The following identifiers uniquely specify the requirements applicable to the producer (O-Cloud) for this operation: [REQ-ORC-O2-70]. - -##### 2.1.7.2.10 Performance Measurement Job Resume - -Performance Measurement Jobs collect performance measurements and metrics on O-Cloud infrastructure resources. The O2ims\_InfrastructurePerformance service shall enable an authorized consumer to resume a Performance Measurement Job in the O-Cloud over the O2 interface. - -Resuming a Performance Measurement Job operation will request that the Performance Measurement Job starts again their measurement collection activity that were halted. The Performance Measurement Job will transition to the “*ACTIVE*” state. The Performance Measurement Job will begin measurement collection at their next scheduled collection interval period. - -A Performance Measurement Job can only be resumed if its current state is “*SUSPENDED*”. - -All consumer(s) who are subscribed to a Performance Measurement Job are notified via the PerformanceMeasurementJobChangeNotification when the Performance Measurement Job is resumed. - -NOTE 1: The `isSuspect` attribute of the PerformanceMeasurementRecord should be set to True when resuming a PM Job. This is because the current reading might be a partial measurement, not representative of the full measurement period. This attribute tells the consumer that the data might be incomplete, allowing them to handle it accordingly. For further information on the `isSuspect` attribute, see O-RAN.WG6.TS.O-Cloud-IM [36], Clause 4.2.1.4.15.2. - -NOTE 2: If the requested Performance Measurement Job is already in the “*ACTIVE*” state, this operation would return a success. However, it would not result in any action being taken. - -NOTE 3: Performance Measurement Job in the “*DEPRECATED*” state cannot be resumed. - -For further information on Performance Measurement Jobs, see O-RAN WG6 O2 GA&P [24], Clause 3.9.5. For further information on the Performance Measurement Job Resume Use Case, see O-RAN.WG6. ORCH-USE-CASES [23], Clause 3.8.10 - -Table 2.1.7.2.10-1 lists the information flow exchanged between the SMO and the O-Cloud using the request-response pattern. - -**Table 2.1.7.2.10-1: O2ims\_PerformanceMeasurementJobResume operation** - -| Message | Direction | -|---------------------------------------------|---------------| -| PerformanceMeasurementJobResumeRequest | SMO → O-Cloud | -| PerformanceMeasurementJobResumeResponse | O-Cloud → SMO | -| PerformanceMeasurementJobChangeNotification | O-Cloud → SMO | - -The input parameter which can be sent when invoking the operation is: - -- Performance Measurement Job Id – This is an identifier provided by the consumer that identifies Performance Measurement Job to be resumed. - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23], clause 4.3. The following identifiers uniquely specify the requirements applicable to the producer (O-Cloud) for this operation: [REQ-ORC-O2-72]. - -### 2.1.8 O2ims\_InfrastructureLogging Services - -#### 2.1.8.1 Service description - -Logging Services have service operations that are related to the operation and management of Logging functions within the O-Cloud. Logs can be kept at different entities within an O-Cloud. They can be kept within O-Cloud resources, Clusters, and IMS. Each of those entities can generate different kinds of logs including Alarm, Fault, Debug, Trace, Security, and Informational logs. - -#### 2.1.8.2 Service operations - -##### 2.1.8.2.1 Logging Configuration Service Operation - -The Logging Configuration is related to how the IMS administers, provisions, and configures logging management for logs that are generated in the O-Cloud. There are many kinds of logs that may exist in the O-Cloud such as Alarm Logs, Fault Logs, Debug Logs, and other logs. See O-RAN WG6.O2-GA&P [24], clause 3.8.19 for more details. This service operation will configure the logging behaviour of those logs. Further logging management configuration for specific types of logs are implementation specific. - -Examples of elements that can be configured through the Logging Configuration Service Operation are the retention period, the activation of logging, logging behaviour (e.g., rotation of older logs (FIFO)), and log levels. Not all logs will have each of these kinds of configurable attributes. - -See O-RAN WG6.ORCH-USE-CASES [23], clause 3.7.10 Logging Management Use Case for more information. - -The Logging Configuration Service Operation is related to the Log Capability Query (IMS) Service Operation (see NOTE 1) because Logging Configuration sets the behaviour how IMS handles the management of logging. - -NOTE 1: The Log Capability Query Service Operation is not defined in the present document. - -NOTE 2: It is up to the protocol and data model specification to determine the one or various protocol operations enabling the authorized consumer to retrieve the O-Cloud information. - -Table 2.1.8.2.1-1 lists the information flow exchanged between the SMO and the O-Cloud. - -**Table 2.1.8.2.1-1: O2ims\_InfrastructureLoggingConfiguration operation** - -| Message | Direction | -|----------------------------------------------|---------------| -| InfrastructureLogging Configuration Request | SMO → O-Cloud | -| InfrastructureLogging Configuration Response | O-Cloud → SMO | - -The input parameters sent when invoking the operation shall support the means to specify configuration of different aspects of the management of Logs of interest for the IMS and for O-Cloud Resources: - -- **Log Type** – Specify types of Log(s) supported for the IMS and O-Cloud Resources. These might include, but are not limited to Alarm Logs, Fault Logs, Debug Logs. Other logs could be described in the input parameter as well. -- **Retention Period** – Specify the Retention Period for the different types of Log(s). This attribute indicates the period of time for which a particular type of Log would be retained for. -- **Logging State** – This is an attribute to indicate the activate state for a particular type of Log. Each Log Type might have an active or inactive state to indicate whether that Log Type is used or not. -- **Expiry method** – Configure logging expiry method for a type of Log which describes what happens if the age of a Log exceeds the Retention Period. The expiry methods could include behaviours such as LIFO, FIFO, and FILO. -- **Logging Level** – Configure the Logging Level(s) for the Logs of interest. See O-RAN WG6.O2-GA&P [24], clause 3.8.20 for more details. - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23], clause 4.3. The following identifiers uniquely specify the requirements applicable to the producer (O-Cloud) for this operation: [REQ-ORC-O2-55]. - -##### 2.1.8.2.2 Logging Query Service Operation - -The Log Query Service Operation allows a user, application, or entity (e.g., SMO) to query logs based on query filter. Logs could be queried by the SMO to the IMS via O2. This Service Operation concerns the retrieval and reading of logs within the O-Cloud that are present and managed by the IMS. A user, application, or entity can query for logs that are - -available in the Cloud: both exposed O-Cloud and Cloud Infrastructure logs. Any log kept in the Cloud infrastructure might be queried through an implementation specific user interface client or file transfer client such as CLI, SSH2, SFTP. The associated Log Query Use Case describes the concept and flow of this operation. See O-RAN WG6.ORCH-USE-CASES [23], clause 3.7.8 Log Query Use Case for more information. - -There are three basic kinds of logs that might be kept within the Cloud (both exposed O-Cloud and Cloud infrastructure): Alarm Logs, Fault Log, and Debug Logs. Additionally, there may be many other kinds of Logs that might available as well, such as Trace Logs, Security Logs, Informational Logs, and Maintenance Logs among others. See O-RAN WG6.O2-GA&P [24], clause 3.8.19 for more details. - -The Service Operation is filter driven which allows a requestor to retrieve Log data of interest. Log events are time and date stamped and Log events have a severity and source. Thus, these serve as a basis for Log querying and the filter in the Service Operation. For example, using a filter, an entity invoking the service operation could request for all the alarm logs in the O-Cloud within a certain date range or a log level. - -Logs can be used for a variety of purposes. The Log Query Service Operation facilities system probing, troubleshooting assistance, network optimization, and network investigation (forensics). Logs can be used for system probing to deduce an operational view of the system. For example, an entity could query for logged faults and alarms that have not been cleared. - -Logs of interest produced in the O-Cloud can be retrieved by the consumer as in a pull paradigm. If a consumer wants to retrieve logs, the callback is given in the Log Query operation. When the Logs are ready, the callback is used as a notification endpoint for the O-Cloud to inform the consumer that the Logs are ready to be pulled. In a large distribute cloud native system, it can take a long time to write or move Logs, hence the callback is used as a notification mechanism to a consumer. - -Logs of interest can also be delivered by the producer as in a push paradigm. In this case, the consumer will provide a *Remote File Location* (as an attribute in the operation) that the producer (O-Cloud) can upload the logs of interest to. Here, the callback is the endpoint where the Log File Ready notification is sent. This informs the consumer that the log files have been uploaded. In the push paradigm, what happens to the files after the producer sends the log files to the remote file location is implementation specific. - -The Logging Capability Query use case permits an entity to query for the types of Logs that are supported by the O-Cloud. - -NOTE: It is up to the protocol and data model specification to determine the one or various protocol operations enabling the authorized consumer to retrieve the O-Cloud information. - -The Log Query Service Operation follows a request, response, and notification service pattern. Table 2.1.8.2.2-1 lists the information flow exchanged between the SMO and the O-Cloud. - -**Table 2.1.8.2.2-1: O2ims\_InfrastructureLoggingQuery operation** - -| Message | Direction | -|------------------------------------|---------------| -| InfrastructureLoggingQueryRequest | SMO → O-Cloud | -| InfrastructureLoggingQueryResponse | O-Cloud → SMO | -| FileReadyNotification | O-Cloud → SMO | - -The Log Query Service Operation request has input parameters that are sent when invoking the operation. These shall support the means to specify different aspects of the Querying Logs of interest for to the requestor: - -- **Log Type** – This allows a consumer to specify the types of Log(s) to retrieve. These might include, but are not limited to Alarm Logs, Fault Logs, Debug Logs. Other logs could be described in this input parameter as well. See O-RAN WG6.O2-GA&P [24], clause 3.8.19 for Log type concepts. -- **Date Ranges** – This parameter specifies a range of dates for entries in the Log type(s) of interest. -- **Types of Events** – The Event Type(s) can be specified as an input. Log(s) containing entries with certain types of events of interest to the requestor can be specified as an input. -- **Resources** – The Resources and Resource Types can be specified as an input. Log(s) containing entries from certain types of Resources or Resource Types of interest to the requestor can be specified. - -- **Log Level (Severity)** – The Logging Level(s) can be specified as an input parameter. This would result in a Query for Logs with entries matching certain Logging Level(s) in the requested Log Type(s) of interest. See O-RAN WG6.O2-GA&P [24], clause 3.8.20 for the Log Level concept. -- **Callback** – This provides an endpoint to send “log ready” notifications to. It is given by a requesting entity so that the O-Cloud can send Log Query related notifications to. -- **Remote File Location (Optional)** – The consumer can provide a URI location where the logs of interest can be uploaded to in a push paradigm. If a Remote File Location is provided, the files of interest to the consumer will be uploaded to that location and a file list would be returned in the response with a file available notification using the Callback provided. - -For example, the Log Query filters in the request may include input parameters specifying the date (ranges), types of logs, types of events, log level (severity), resource(s), or resource type(s) of interest to the consumer. - -The Log Query service operation can experience three exceptions as follows: - -- **Non-Existing Logs** – This exception occurs when the Log Query service operation results in a query for non-existent log(s). In this case, an object not found is returned for the operation. -- **No Content** – The Log Query service operation may have a Log Query filter that returns an empty set. This would return a failure from the operation. -- **Unable to Parse** – This exception happens when the records are unavailable for parsing or retrieval by the producer. This might occur because the Log File is corrupt, has been moved, or deleted. - -The full requirements definitions can be found in O-RAN WG6.ORCH-USE-CASES [23], clause 4.3. The following identifiers uniquely specify the requirements applicable to the producer (O-Cloud) for this operation: [REQ-ORC-O2-36]. - -# 3 API definitions - -## 3.1 General aspects - -### 3.1.1 Introduction - -The present document defines the protocol and data model for the following O2ims service interfaces in the form of RESTful Application Programming Interface (API) specifications: - -- O2ims\_InfrastructureInventory Service API (as produced by the O-Cloud towards the SMO) -- O2ims\_InfrastructureMonitoring Service API (as produced by the O-Cloud towards the SMO) -- O2ims\_InfrastructureProvisioning Service API (as produced by the O-Cloud towards the SMO) -- O2ims\_InfrastructureSoftwareManagement Service API (as produced by the O-Cloud towards the SMO) -- O2ims\_InfrastructureLifecycleManagement Service API (as produced by the O-Cloud towards the SMO) -- O2ims\_InfrastructurePerformance Service API (as produced by the O-Cloud towards the SMO) -- O2ims\_InfrastructureLogging Service API (as produced by the O-Cloud towards the SMO) - -Table 3.1.1-1 lists the versions of the APIs defined in the present document. - -**Table 3.1.1-1: Versions of the APIs specified in the present document** - -| Service API | API version | -|-----------------------------------------------------|-------------| -| O2ims_InfrastructureInventory Service API | 2.0.0 | -| O2ims_InfrastructureMonitoring Service API | 2.0.0 | -| O2ims_InfrastructureProvisioning Service API | 1.2.0 | -| O2ims_InfrastructureSoftwareManagement Service API | TBD | -| O2ims_InfrastructureLifecycleManagement Service API | 1.0.0 | -| O2ims_InfrastructurePerformance Service API | 2.1.0 | -| O2ims_InfrastructureLogging Service API | TBD | - -The design of the protocol and data model for the above interfaces is based on the information model and requirements defined in [36]. In clause 3, general aspects are specified that apply to multiple APIs for O2ims services. In addition, the provisions in clauses 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.1.6, 3.1.7, and 3.1.8 define common aspects of RESTful APIs, and shall apply for all APIs defined in the present document. - -In the subsequent clauses, the protocol and data model for the individual interfaces are specified. Per interface, the resource structure with associated HTTP methods is defined and applicable flows are provided. Further, the resources and the data model are specified in detail. - -Even though the different interfaces defined in the present document are related, implementations shall not assume a particular order of messages that arrive via different interfaces. - -### 3.1.2 URI structure and supported content formats - -This clause specifies the URI prefix and the supported formats applicable to the O2ims RESTful APIs. - -All resource URIs of the APIs shall have the following prefix, except the "API versions" resource which shall follow the rules specified in clause 9.3 of ETSI GS NFV-SOL 013 [22]: - -**{apiRoot}///** - -The request URIs used in HTTP requests from the API service consumer towards the API service producer shall have the Resource URI structure defined in clause 4.4.1 of 3GPP TS 29.501 [11], i.e.: - -**{apiRoot}
** - -with the following components: - -- The {apiRoot} shall be set as described in clause 4.4.1 of 3GPP TS 29.501 [11]. -- The indicates the API name of the service interface in an abbreviated form. The {apiName} of each interface is defined in the clause specifying the corresponding O2ims RESTful API. -- The indicates the current major version of the API and is defined in the clause specifying the corresponding O2ims RESTful API. -- The indicates a resource URI of the API, and shall be set as described in in the corresponding O2ims RESTful API for each one of the defined resources. - -Either HTTP/2, as defined in IETF RFC 7540 [19], or HTTP/1.1, as defined in IETF RFC 7230 [30] shall be used. - -The Transmission Control Protocol (TCP) as specified in IETF RFC 793 [31] shall be used as transport protocol for HTTP/2 and HTTP/1.1. - -For HTTP requests and responses that have a body, the content format JSON (see IETF RFC 8259 [20]) shall be supported. The JSON format shall be signalled by the content type "application/json". - -All APIs shall support and use HTTP over TLS (also known as HTTPS) (see IETF RFC 2818 [32]). At least support TLS version 1.2 but recommended to support TLS version 1.3 as defined by IETF RFC 5246 [33] shall be supported. - -NOTE 1: The HTTP protocol elements mentioned in the O2ims RESTful APIs originate from the HTTP specification; HTTPS runs the HTTP protocol on top of a TLS layer. For simplicity, the O2ims RESTful APIs specifications therefore use the statement above to mention "HTTP request", "HTTP header", etc., without explicitly calling out HTTPS. - -NOTE 2: There are a number of best practices and guidelines how to configure and implement TLS 1.2 in a secure manner, as security threats evolve. A detailed specification of those is beyond the scope of the present document; the reader is referred to external documentation such as annex E of ETSI TS 133 310 [35]. - -All resource URIs of the API shall comply with the URI syntax as defined in IETF RFC 3986 [34]. An implementation that dynamically generates resource URI parts (individual path segments, sequences of path segments that are separated by "/", query parameter values) shall ensure that these parts only use the character set that is allowed by IETF RFC 3986 [34] for these parts. - -NOTE 3: This means that characters not part of this allowed set are escaped using percent-encoding as defined by IETF RFC 3986 [34]. - -Unless otherwise specified explicitly, all request URI parameters that are part of the path of the resource URI shall be individual path segments, i.e., shall not contain the "/" character. - -NOTE 4: A request URI parameter is denoted by a string in curly brackets, e.g. {fooId}. - -### 3.1.3 Usage of HTTP header fields - -#### 3.1.3.1 General - -HTTP headers are components of the header section of the HTTP request and response messages. They contain the information about the server/client and metadata of the transaction. The use of HTTP header fields shall comply with the provisions defined for those header fields in the specifications referenced from tables 3.1.3.2-1 and 3.1.3.3-1. The following clauses describe more details related to selected HTTP header fields. - -#### 3.1.3.2 Request header fields - -This clause describes the usage of selected HTTP header fields of the request messages in the O2ims RESTful APIs. The HTTP header fields used in the request messages that shall be supported are specified in table 3.1.3.2-1. - -**Table 3.1.3.2-1: Header fields supported in the request message** - -| Header field name | Reference | Example | Descriptions | -|-------------------|-----------------------------|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------| -| Accept | IETF RFC 7231 [ref-rfc7231] | application/json | Content-Types that are acceptable for the response.
This header field shall be present if the response is expected to have a non-empty message body. | -| Content-Type | IETF RFC 7231 [ref-rfc7231] | application/json | The MIME type of the body of the request.
This header field shall be present if the request has a non-empty message body. | -| Authorization | IETF RFC 7235 [ref-rfc7235] | Bearer mF_9.B5f-4.1JqM | The authorization token for the request. | -| Range | IETF RFC 7233 [ref-rfc7233] | 1 000-2 000 | Requested range of bytes from a file. | -| Version | IETF RFC 4229 [ref-rfc4229] | 1.2.0
or
1.2.0-impl.example.com:myProduct:4 | Version of the API requested to use when responding to this request. | - -#### 3.1.3.3 Response header fields - -This clause describes the usage of selected HTTP header fields of the response messages in the O2ims RESTful APIs. The HTTP header fields used in the response messages are specified in table 3.1.3.3-1. - -**Table 3.1.3.3-1: Header fields supported in the response message** - -| Header field name | Reference | Example | Descriptions | -|-------------------|-----------------------------|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Content-Type | IETF RFC 7231 [ref-rfc7231] | application/json | The MIME type of the body of the response.
This header field shall be present if the response has a non-empty message body. | -| Location | IETF RFC 7231 [ref-rfc7231] | http://www.example.com/apiname/v1/objects/123 | Used in redirection, or when a new resource has been created.
This header field shall be present if the response status code is 201 or 3xx.
In the O2ims RESTful APIs this header field is also used if the response status code is 202 and a new resource was created. | -| WWW-Authenticate | IETF RFC 7235 [ref-rfc7235] | Bearer realm="example" | Challenge if the corresponding HTTP request has not provided authorization, or error details if the corresponding HTTP request has provided an invalid authorization token. | -| Accept-Ranges | IETF RFC 7233 [ref-rfc7233] | bytes | Used by the server to signal whether or not it supports ranges for certain resources. | -| Content-Range | IETF RFC 7233 [ref-rfc7233] | bytes 21 010 - 47 021/47 022 | Signals the byte range that is contained in the response, and the total length of the file. | - -| Header field name | Reference | Example | Descriptions | -|-------------------|-----------------------------|--------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Retry-After | IETF RFC 7231 [ref-rfc7231] | Fri, 31 Dec 1999 23:59:59 GMT
or
120 | Used to indicate how long the user agent ought to wait before making a follow-up request.
It can be used with 503 responses. The value of this field can be an HTTP-date or a number of seconds to delay after the response is received. | -| Link | IETF RFC 8288 [ref-rfc8288] | ; rel="next" | Reference to other resources. Used for paging in the present document, see clause 3.1.4. | -| Version | IETF RFC 4229 [ref-rfc4229] | 1.2.0
or
1.2.0-impl:example.com:myProduct:4 | Version of the API requested to use when responding to this request. | - -### 3.1.4 Result set control - -#### 3.1.4.1 Introduction - -This clause specifies procedures that allow to control the size of the result set of GET requests w.r.t. the number of entries in a response list (using attribute-based filtering) or w.r.t. the number of attributes returned in a response (using attribute selection). - -#### 3.1.4.2 Attribute-based filtering and selector - -The use of attribute-based filtering shall be supported by O2ims RESTful APIs as specified in clause 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [22]. - -NOTE: ETSI GS NFV-SOL 013 [22] refers to "RESTful NFV-MANO API" specification; and wherever such reference is provided "O2ims RESTful API" is to be considered instead for the purpose of the present document. - -#### 3.1.4.3 Handling of large query results - -The handling of large query results shall be supported by O2ims RESTful APIs as specified in clause 5.4.2 of ETSI GS NFV-SOL 013 [22]. - -### 3.1.5 Error reporting - -In RESTful interfaces, application errors are mapped to HTTP errors. Since HTTP error information is generally not enough to discover the root cause of the error, additional application specific error information is typically delivered. - -The error reporting shall be supported by O2ims RESTful APIs as specified in clause 6 of ETSI GS NFV-SOL 013 [22]. - -NOTE: ETSI GS NFV-SOL 013 [22] refers to "RESTful NFV-MANO API" specification; and wherever such reference is provided "O2ims RESTful API" is to be considered instead for the purpose of the present document. - -### 3.1.6 Common data types - -#### 3.1.6.1 Structured data types - -##### 3.1.6.1.1 Introduction - -This clause defines data structures that are referenced from data structures in multiple O2ims RESTful APIs. - -##### **3.1.6.1.2 Type: Object** - -An object contains structured data and shall comply with the provisions of clause 4 of IETF RFC 8259 [20]. - -##### **3.1.6.1.3 Type: Link** - -This type represents a link to a resource using an absolute URI. It shall comply with the provisions defined in table 7.1.3-1. - -**Table 3.1.6.1.3-1: Definition of the Link data type** - -| Attribute name | Data type | Cardinality | Description | -|----------------|-----------|-------------|--------------------------------------------------------------------------------------------------------------------| -| href | Uri | 1 | URI of another resource referenced from a resource. Shall be an absolute URI (i.e. a URI that contains {apiRoot}). | - -##### **3.1.6.1.4 Type: NotificationLink** - -This type represents a link to a resource in a notification, using an absolute or relative URI. It shall comply with the provisions defined in table 3.1.6.1.4-1. - -**Table 3.1.6.1.4-1: Definition of the NotificationLink data type** - -| Attribute name | Data type | Cardinality | Description | -|----------------|-----------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| href | Uri | 1 | URI of a resource referenced from a notification. Should be an absolute URI (i.e. a URI that contains {apiRoot}), however, may be a relative URI (i.e. a URI where the {apiRoot} part is omitted) if the {apiRoot} information is not available. | - -##### **3.1.6.1.5 Type: KeyValuesPairs** - -This type represents a list of key-value pairs. The order of the pairs in the list is not significant. In JSON, a set of key-value pairs is represented as an object. It shall comply with the provisions defined in clause 4 of IETF RFC 8259 [20]. In the following example, a list of key-value pairs with four keys ("aString", "aNumber", "anArray" and "anObject") is provided to illustrate that the values associated with different keys can be of different type. - -EXAMPLE: - -``` -{ - "aString" : "O2ims service", - "aNumber" : 0.03, - "anArray" : [1,2,3], - "anObject" : {"organization" : "O-RAN", "workingGroup" : "WG6"} -} -``` - -##### **3.1.6.1.6 Type: ApiVersionInformation** - -This type represents API version information. It shall comply with the provisions defined in table 3.1.6.1.6-1. - -**Table 3.1.6.1.6-1: ApiVersionInformation data type** - -| Attribute name | Data type | Cardinality | Description | -|-----------------|---------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| uriPrefix | String | 1 | Specifies the URI prefix for the API, in the following form {apiRoot}/{apiName}/{apiMajorVersion}/. | -| apiVersions | Structure (inlined) | 1..N | Version(s) supported for the API signaled by the uriPrefix attribute. | -| >version | String | 1 | Identifies a supported version. The value of the version attribute shall be a version identifier as specified in clause 3.1.6.2. | -| >isDeprecated | Boolean | 0..1 | If such information is available, this attribute indicates whether use of the version signaled by the version attribute is deprecated (true) or not (false).
See note. | -| >retirementDate | DateTime | 0..1 | The date and time after which the API version will no longer be supported.

This attribute may be included if the value of the isDeprecated attribute is set to true and shall be absent otherwise. | - -NOTE: A deprecated version is still supported by the API producer but is recommended not to be used any longer. When a version is no longer supported, it does not appear in the response body. - -#### 3.1.6.2 Simple data types and enumerations - -##### 3.1.6.2.1 Introduction - -This clause defines simple data types and enumerations that can be referenced from data structures defined in multiple interfaces. - -##### 3.1.6.2.2 Simple data types - -Table 3.1.6.2.2-1 lists the simple data types that are referenced from multiple interfaces. - -**Table 3.1.6.2.2-1: Simple data types** - -| Type name | Description | -|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Identifier | An identifier with the intention of being globally unique. Representation: string of variable length. See note 1. | -| DateTime | A date-time stamp. Representation: String formatted as defined by the date-time production in IETF RFC 3339 [43]. | -| Uri | A string formatted according to IETF RFC 3986 [34]. | -| Boolean | A data type having two values (true and false). | -| IpAddress | An IPV4 or IPV6 address. Representation: In case of an IPV4 address, string that consists of four decimal integers separated by dots, each integer ranging from 0 to 255. In case of an IPV6 address, string that consists of groups of zero to four hexadecimal digits, separated by colons. | -| Version | A version. Representation: string of variable length. | -| String | A string as defined in IETF RFC 8259 [20]. | -| Number | A number as defined in IETF RFC 8259 [20]. | -| Integer | An integer, i.e. a number that cannot have a fractional component. See note 2. | -| UnsignedInt | An unsigned integer, i.e. an integer that can't assume negative values. See note 2. | -| Point | A geometry object as defined in IETF RFC 7946 [44]. | - -NOTE 1: Individual API specifications are assumed to define types for additional identifiers with dedicated scope (e.g. identifiers scoped by some O-Cloud). - -NOTE 2: In the JSON instance data model, only the concept of a "number" is used to represent numerical data. Numbers in JSON can be integral, i.e. have no fractional part, or can include a fractional part. The additional numeric types defined in the present document represent constraints on the general "number" type present in JSON instances which can be enforced e.g. during parsing when processing the JSON instance or expressed as constraints in modelling languages such as JSON Schema [ref-json-scheme] or OpenAPI [ref-openapi]. - -### 3.1.7 Security - -#### 3.1.7.1 Introduction - -The current version of the present document mandates compliance with the authorization mechanisms outlined in the O-RAN.WG11.TS.SecProtSpec [46] for handling API requests and notifications specified herein, to ensure alignment with the following best practices and guidelines: - -- O-RAN.WG11.TS.SecProtSpec [46] clause 4.10 for HTTP over TLS (HTTPS), -- O-RAN.WG11.TS.SecProtSpec [46] clause 4.7 for OAuth 2.0 framework and token usage. - -### 3.1.8 Version management - -#### 3.1.8.1 Version identifiers and parameters - -API version identifiers and rules for incrementing version identifier fields shall be supported by O2ims RESTful APIs as specified in clause 9.1 and 9.2 of ETSI GS NFV-SOL 013 [22]. - -NOTE: ETSI GS NFV-SOL 013 [22] refers to "RESTful NFV-MANO API" specification and OpenAPI specification that ETSI publishes; and wherever such reference is provided "O2ims RESTful API" and OpenAPI that O-RAN publishes is to be considered instead for the purpose of the present document. - -Clause 9.2.2 of ETSI GS NFV-SOL 013 [22] provides examples of backward and non-backward compatible changes. - -#### 3.1.8.2 Version information retrieval and signaling - -The API producer shall support the dedicated URIs to enable API consumers to retrieve information about API versions supported by an API producer as specified in clause 9.3 of ETSI GS NFV-SOL 013 [22], and the API consumer shall include the "Version" HTTP header in each HTTP request as specified in clause 9.4 of ETSI GS NFV-SOL 013 [22]. - -NOTE: ETSI GS NFV-SOL 013 [22] refers to "RESTful NFV-MANO API" specification; and wherever such reference is provided "O2ims RESTful API" is to be considered instead for the purpose of the present document. - -## 3.2 O2ims\_InfrastructureInventory Service API - -### 3.2.1 Description - -This API allows the SMO to invoke O2ims\_InfrastructureInventory Services towards the O-Cloud. - -The operations defined for O2ims\_InfrastructureInventory Services through this API are: - -- Query information about one or multiple Resource Type -- Query information about one or multiple Resource Pool -- Query information about one or multiple Resource -- Query information about one or multiple Deployment Manager -- Query information about one or multiple Subscriptions -- Query information about one or multiple Alarm Dictionary -- Query information about one or multiple Performance Dictionary -- Query information about one or multiple Location -- Query information about one or multiple O-Cloud Site - -- Notify consumer identified by an established subscription which is not filtered by the filter criteria of the occurrence of a change to the infrastructure inventory objects - -### 3.2.2 API version - -For the O2ims\_InfrastructureInventory Service API version as specified in the present document, the MAJOR version field shall be 2, the MINOR version field shall be 0, and the PATCH version field shall be 0. - -Table 3.2.2-1 lists the history of API versions of the O2ims\_InfrastructureInventory Service and the main capabilities added/removed across versions. - -**Table 3.2.2-1: History of API versions of the O2ims\_InfrastructureInventory Service.** - -| Version | Description | -|---------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 1.0.0 | Initial API Supporting:
O-Cloud Description
Resource Type List
Resource Type Description
Resource Pool List
Resource Pool Description
Resource List
Resource Description
Deployment Manager List
Deployment Manager Description
Inventory Subscription List
Inventory Subscription Description | -| 1.1.0 | Modified method:
Inventory Subscription Description

New resources:
Performance Dictionary
Alarm Dictionary
Alarm Dictionary List
Performance Dictionary List | -| 1.2.0 | Modified Data Type:
ResourceTypeInfo | -| 2.0.0 | New resources:

Location List
Location Description
O-Cloud Site List
O-Cloud Site Description

Modified Data Types:
ResourcePoolInfo
CloudInfo
InventorySubscriptionInfo | - -### 3.2.3 REST resources structure and methods - -All resource URIs of the API shall use the base URI specification defined in clause 3.1.2. The string "O2ims\_infrastructureInventory" shall be used to represent {apiName}. All resource URIs in the clauses below are defined relative to the formed base URI (i.e., {apiRoot}/O2ims\_infrastructureInventory/{apiVersion}). - -When ambiguity is possible, the term REST resource is used to make the distinction between the term resource as understood within the context of REST API from the term resource as understood within the context of O-RAN. - -Figure 3.2.3-1 shows the overall resource URI structure defined for the O2ims\_InfrastructureInventory Service API. - -![Resource URI structure of the O2ims_infrastructureInventory API diagram](47a7beddcb8a1b7abdca746967e32bb4_img.jpg) - -``` - -graph TD - Root["{apiRoot}/O2ims_infrastructureInventory/{apiMajorVersion}"] - Root --- RT["/resourceTypes"] - Root --- RP["/resourcePools"] - Root --- DM["/deploymentManagers"] - Root --- S["/subscriptions"] - Root --- AD["/alarmDictionaries"] - Root --- PD["/performanceDictionaries"] - Root --- LOC["/locations"] - Root --- OS["/oCloudSites"] - - RT --- RTId["/{resourceTypeId}"] - RTId --- PDic["/performanceDictionary"] - RTId --- ADic["/alarmDictionary"] - - RP --- RPId["/{resourcePoolId}"] - RPId --- RES["/resources"] - RES --- ResId["/{resourceId}"] - - DM --- DMId["/{deploymentManagerId}"] - - S --- SId["/{subscriptionId}"] - - AD --- ADId["/{alarmDictionaryId}"] - - PD --- PDId2["/{performanceDictionaryId}"] - - LOC --- GLId["/{globalLocationId}"] - - OS --- OSId["/{oCloudSiteId}"] - -``` - -Resource URI structure of the O2ims\_infrastructureInventory API diagram - -**Figure 3.2.3-1 Resource URI structure of the O2ims\_infrastructureInventory API** - -Table 3.2.3-1 provides an overview of the resources and applicable HTTP methods. - -The O-Cloud shall support responding to requests for all HTTP methods on the resources in Table 3.2.3-1 that are marked as "M" (mandatory) in the "Cat" column. The O-Cloud shall also support the "API versions" resources as specified in clause 3.1.8. - -**Table 3.2.3-1 Resources and methods overview** - -| Resource name | Resource URI | HTTP method | Cat | Description | -|------------------------------------|------------------------------------------------------------------------------------------------------------|-------------|-----|---------------------------------------------------------------------| -| O-Cloud Description | / | GET | M | To get the attributes of the O-Cloud instance | -| Resource Type List | /resourceTypes | GET | M | To get a list of resource types | -| Resource Type Description | /resourceTypes/{resourceTypeId} | GET | M | To get an individual resource type description | -| Performance Dictionary | /resourceTypes/{resourceTypeId}/performanceDictionary
/performanceDictionaries/{performaneDictionaryId} | GET | M | To get the Performance Dictionary | -| Alarm Dictionary | /resourceTypes/{resourceTypeId}/alarmDictionary
/alarmDictionaries/{alarmDictionaryId} | GET | M | To get the Alarm Dictionary | -| Resource Pool List | /resourcePools | GET | M | To get a list of resource pools | -| Resouce Pool Description | /resourcePools/{resourcePoolId} | GET | M | To get an individual resource pool description | -| Resource List | /resourcePools/{resourcePoolId}/resources | GET | M | To get a list of resources in the resource pool | -| Resource Description | /resourcePools/{resourcePoolId}/resources/{resourceId} | GET | M | To get an individual resource description | -| Deployment Manager List | /deploymentManagers | GET | M | To get a list of deployment managers | -| Deployment Manager Description | /deploymentManagers/{deploymentManagerId} | GET | M | To get an individual deployment manager description | -| Inventory Subscription List | /subscriptions | GET | M | To get a list of subscriptions | -| Inventory Subscription List | /subscriptions | POST | M | To create an individual subscription | -| Inventory Subscription Description | /subscriptions/{subscriptionId} | GET | M | To get an individual subscription description | -| Inventory Subscription Description | /subscriptions/{subscriptionId} | DELETE | M | To delete an individual subscription | -| Alarm Dictionary List | /alarmDictionaries | GET | M | To get the list of individual Dictionaries that qualify | -| Performance Dictionary List | /performanceDictionaries | GET | M | To get the list of individual Performance Dictionaries that qualify | -| Location List | /locations | GET | M | To get a list of locations | -| Location Description | /locations/{globalLocationId} | GET | M | To get an individual location description | -| O-Cloud Site List | /oCloudSites | GET | M | To get a list of O-Cloud sites | -| O-Cloud Site Description | /oCloudSites/{oCloudSiteId} | GET | M | To get an individual O-Cloud site description | - -### 3.2.4 REST resources - -#### 3.2.4.1 Introduction - -There are no preconditions or postconditions for a successful execution of each of the O2ims\_InfrastructureInventory Service API triggered by an operation. - -#### 3.2.4.2 REST resource: Resource Type List - -##### 3.2.4.2.1 Description - -This resource represents the list of resource types that the O-Cloud is designed to support. The Resource Type List contains Resource Type Descriptions. - -##### 3.2.4.2.2 Resource definition - -Resource URI: {apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/resourceTypes - -This resource shall support the resource URI variables defined in Table 3.2.4.2.2-1. - -**Table 3.2.4.2.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | string | See clause 3.1.2 | -| apiMajorVersion | string | See clause 3.1.2 | - -##### 3.2.4.2.3 Resource methods - -###### 3.2.4.2.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.2.4.2.3.2 GET - -The GET operation is used to retrieve the list of resource type. - -This method shall support the URI query parameters specified in Table 3.2.4.2.3.2-1. - -**Table 3.2.4.2.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| filter | 0..1 | Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [22].
The O-Cloud shall support receiving this parameter as part of the URI query string. The API consumer may supply this parameter.
All attribute names that appear in the ResourceTypeInfo and in data types referenced from it shall be supported by the O-Cloud in the filter expression. | -| all_fields | 0..1 | Include all complex attributes in the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter. | -| fields | 0..1 | Complex attributes to be included into the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_fields | 0..1 | Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_default | 0..1 | Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.
The following attributes shall be excluded from the list of ResourceTypeInfo in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided:
- TBD | -| nextpage_opaque_marker | 0..1 | Marker to obtain the next page of a paged response. Shall be supported by the O-Cloud if the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource. | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.2.3.2-2. - -**Table 3.2.4.2.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|------------------|------------------|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | ResourceTypeInfo | 0..N | 200 OK |

Shall be returned when information about zero or more ResourceTypeInfo instances has been queried successfully.

The response body shall contain an array the representations of zero or more ResourceTypeInfo instances, as defined in clause 3.2.6.2.2.

If the "filter" URI parameter or one of the "all_fields", "fields" (if supported), "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request, the data in the response body shall have been transformed according to the rules specified in clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [22], respectively.

If the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, inclusion of the Link HTTP header in this response shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013 [22].

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute-based filtering expression.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute selector.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Response too big.

If the O-Cloud supports alternative 1 (error) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, this error response shall follow the provisions in clause 5.4.2.2 of ETSI GS NFV-SOL 013 [22].

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx |

In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned.

| - -###### **3.2.4.2.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.2.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.2.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### 3.2.4.3 REST resource: Resource Type Description - -##### 3.2.4.3.1 Description - -This resource represents the description of a resource type. The Resource Type Description is a record of the attributes. The record contains mandatory fields and allows for non-standard attributes to also be inventoried. - -##### 3.2.4.3.2 Resource definition - -Resource URI: {apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/resourceTypes/{resourceTypeId} - -This resource shall support the resource URI variables defined in Table 3.2.4.3.2-1. - -**Table 3.2.4.3.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| resourceTypeId | Identifier | The identifier of the Resource Type Description resource. See note. | -| NOTE: This identifier can be retrieved from the resourceTypeId attribute in the payload body of the response to a GET request getting the list of "ResourceType" resources. | | | - -##### 3.2.4.3.3 Resource methods - -###### 3.2.4.3.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.2.4.3.3.2 GET - -The GET operation is used to retrieve the resource type description of a single resource type. - -This method shall support the URI query parameters specified in Table 3.2.4.3.3.2-1. - -**Table 3.2.4.3.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.3.3.2-2. - -**Table 3.2.4.3.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|------------------|------------------|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | ResourceTypeInfo | 1 | 200 OK | Shall be returned when information about a ResourceTypeInfo instance has been queried successfully. The response body shall contain a representation of the ResourceTypeInfo instance, as defined in clause 3.2.6.2.2. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.2.4.3.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.3.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.3.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### **3.2.4.4 REST resource: Resource Pool List** - -##### **3.2.4.4.1 Description** - -This resource represents the list of Resource Pools that the O-Cloud has resource deployed to. The Resource Pool List contains Resource Pool Descriptions. - -##### **3.2.4.4.2 Resource definition** - -Resource URI: {apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/resourcePools - -This resource shall support the resource URI variables defined in Table 3.2.4.4.2-1. - -**Table 3.2.4.4.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | - -##### **3.2.4.4.3 Resource methods** - -###### **3.2.4.4.3.1 POST** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.4.3.2 GET** - -The GET operation is used to retrieve the list of resource pools. - -This method shall support the URI query parameters specified in Table 3.2.4.4.3.2-1. - -**Table 3.2.4.4.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|----------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| filter | 0..1 | Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [22].
The O-Cloud shall support receiving this parameter as part of the URI query string. The API consumer may supply this parameter.
All attribute names that appear in the ResourcePoolInfo and in data types referenced from it shall be supported by the O-Cloud in the filter expression. | -| all_fields | 0..1 | Include all complex attributes in the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter. | -| fields | 0..1 | Complex attributes to be included into the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_fields | 0..1 | Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_default | 0..1 | Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.
The following attributes shall be excluded from the list of ResourcePoolInfo in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided:
- TBD | -| nextpage_opaque
_marker | 0..1 | Marker to obtain the next page of a paged response. Shall be supported by the O-Cloud if the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource. | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.4.3.2-2. - -**Table 3.2.4.4.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|------------------|------------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | ResourcePoolInfo | 0..N | 200 OK |

Shall be returned when information about zero or more ResourcePoolInfo instances has been queried successfully.

The response body shall contain an array the representations of zero or more ResourcePoolInfo instances, as defined in clause 3.2.6.2.3.

If the "filter" URI parameter or one of the "all_fields", "fields" (if supported), "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request, the data in the response body shall have been transformed according to the rules specified in clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [22] , respectively.

If the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, inclusion of the Link HTTP header in this response shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013 [22] .

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute-based filtering expression.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute selector.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Response too big.

If the O-Cloud supports alternative 1 (error) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, this error response shall follow the provisions in clause 5.4.2.2 of ETSI GS NFV-SOL 013 [22] .

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.2.4.4.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### **3.2.4.4.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### **3.2.4.4.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -#### 3.2.4.5 REST resource: Resource Pool Description - -##### 3.2.4.5.1 Description - -The Resource Pool Description represents the description of a resource pool. This includes some mandatory attributes and allows for extended attributes as well. - -##### 3.2.4.5.2 Resource definition - -Resource URI: {apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/resourcePools/{resourcePoolId} - -This resource shall support the resource URI variables defined in Table 3.2.4.5.2-1. - -**Table 3.2.4.5.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| resourcePoolId | Identifier | The identifier of the Resource Pool Description resource. See note. | -| NOTE: This identifier can be retrieved from the resourcePoolId attribute in the payload body of the response to a GET request getting the list of "ResourcePool" resources. | | | - -##### 3.2.4.5.3 Resource methods - -###### 3.2.4.5.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### 3.2.4.5.3.2 GET - -The GET operation is used to retrieve the resource pool description of a single resource pool. - -This method shall support the URI query parameters specified in Table 3.2.4.5.3.2-1. - -**Table 3.2.4.5.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.5.3.2-2. - -**Table 3.2.4.5.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|------------------|------------------|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | ResourcePoolInfo | 1 | 200 OK | Shall be returned when information about a ResourcePoolInfo instance has been queried successfully. The response body shall contain a representation of the ResourcePoolInfo instance, as defined in clause 3.2.6.3.2. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.2.4.5.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### **3.2.4.5.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### **3.2.4.5.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -#### **3.2.4.6 REST resource: Resource List** - -##### **3.2.4.6.1 Description** - -This resource represents the list of resources in a specific Resource Pool. The Resource List contains Resource Descriptions. - -##### **3.2.4.6.2 Resource definition** - -Resource URI: -**{apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/resourcePools/{resourcePoolId}/resources** - -This resource shall support the resource URI variables defined in Table 3.2.4.6.2-1. - -**Table 3.2.4.6.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|---------------------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| resourcePoolId | Identifier | The identifier of the Resource Pool Description resource. See note. | -| NOTE: This identifier can be retrieved from the resourcePoolId attribute in the payload body of the response to a GET request getting the list of "ResourcePool" resources. | | | - -##### **3.2.4.6.3 Resource methods** - -###### **3.2.4.6.3.1 POST** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### **3.2.4.6.3.2 GET** - -The GET operation is used to retrieve the list of resource descriptions in the specific Resource Pool. - -This method shall support the URI query parameters specified in Table 3.2.4.6.3.2-1. - -**Table 3.2.4.6.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| filter | 0..1 | Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [22] .
The O-Cloud shall support receiving this parameter as part of the URI query string. The API consumer may supply this parameter.
All attribute names that appear in the ResourceInfo and in data types referenced from it shall be supported by the O-Cloud in the filter expression. | -| all_fields | 0..1 | Include all complex attributes in the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter. | -| fields | 0..1 | Complex attributes to be included into the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_fields | 0..1 | Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_default | 0..1 | Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.
The following attributes shall be excluded from the list of ResourceInfo in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided:
- TBD | -| nextpage_opaque_marker | 0..1 | Marker to obtain the next page of a paged response. Shall be supported by the O-Cloud if the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource. | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.6.3.2-2. - -Table 3.2.4.6.3.2-2: Details of the GET request/response on this resource - -| Request body | Data type | Cardinality | Description | | -|---------------|----------------|------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | ResourceInfo | 0..N | 200 OK |

Shall be returned when information about zero or more ResourceInfo instances has been queried successfully. The response body shall contain an array the representations of zero or more ResourceInfo instances, as defined in clause 3.2.6.2.4.

If the "filter" URI parameter or one of the "all_fields", "fields" (if supported), "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request, the data in the response body shall have been transformed according to the rules specified in clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [22] , respectively.

If the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, inclusion of the Link HTTP header in this response shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013 [22] .

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute-based filtering expression.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute selector.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Response too big.

If the O-Cloud supports alternative 1 (error) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, this error response shall follow the provisions in clause 5.4.2.2 of ETSI GS NFV-SOL 013 [22] .

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx |

In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned.

| - -###### 3.2.4.6.3.3 PUT - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### 3.2.4.6.3.4 PATCH - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### 3.2.4.6.3.5 DELETE - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -#### 3.2.4.7 REST resource: Resource Description - -##### 3.2.4.7.1 Description - -The Resource Description represents the description of an individual resource instance in a resource pool. This includes some mandatory attributes including a reference to the Resource Type that defines it and allows for extended attributes as well. - -##### 3.2.4.7.2 Resource definition - -Resource URI: - -**{apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/resourcePools/{resourcePoolId}/resources/{resourceId}** - -This resource shall support the resource URI variables defined in Table 3.2.4.7.2-1. - -**Table 3.2.4.7.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------------------| -| apiRoot | string | See clause 4.1.1 | -| apiMajorVersion | String | See clause 3.1.2 | -| resourcePoolId | Identifier | The identifier of the Resource Pool Description resource. See note1. | -| resourceId | Identifier | The identifier of the Resource in the Resource Pool. See note2. | -| NOTE 1: This identifier can be retrieved from the resourcePoolId attribute in the payload body of the response to a GET request getting the list of "ResourcePool" resources. | | | -| NOTE 2: This identifier can be retrieved from the resourceId attribute in the payload body of the response to a GET request getting the list of "ResourcePoolDescription" resources. | | | - -##### 3.2.4.7.3 Resource methods - -###### 3.2.4.7.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### 3.2.4.7.3.2 GET - -The GET operation is used to retrieve the resource description of an individual resource instance in a resource pool. - -This method shall support the URI query parameters specified in Table 3.2.4.7.3.2-1. - -**Table 3.2.4.7.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.7.3.2-2. - -**Table 3.2.4.7.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|----------------|------------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | ResourceInfo | 1 | 200 OK | Shall be returned when information about a ResourceInfo instance has been queried successfully. The response body shall contain a representation of the ResourceInfo instance, as defined in clause 3.2.6.2.4. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.2.4.7.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### **3.2.4.7.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### **3.2.4.7.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -#### **3.2.4.8 REST resource: Deployment Manager List** - -##### **3.2.4.8.1 Description** - -This resource represents the set of Deployment Managers in the O-Cloud the SMO can use for managing Deployments. The Deployment Manager List contains Deployment Manager Descriptions. - -##### **3.2.4.8.2 Resource definition** - -Resource URI: {apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/deploymentManagers - -This resource shall support the resource URI variables defined in Table 3.2.4.8.2-1. - -**Table 3.2.4.8.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | - -##### **3.2.4.8.3 Resource methods** - -###### **3.2.4.8.3.1 POST** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### 3.2.4.8.3.2 GET - -The GET operation is used to retrieve the list of deployment manager. - -This method shall support the URI query parameters specified in Table 3.2.4.8.3.2-1. - -**Table 3.2.4.8.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| filter | 0..1 | Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [22] .
The O-Cloud shall support receiving this parameter as part of the URI query string. The API consumer may supply this parameter.
All attribute names that appear in the DeploymentManagerInfo and in data types referenced from it shall be supported by the O-Cloud in the filter expression. | -| all_fields | 0..1 | Include all complex attributes in the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter. | -| fields | 0..1 | Complex attributes to be included into the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_fields | 0..1 | Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_default | 0..1 | Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.
The following attributes shall be excluded from the list of DeploymentManagerInfo in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided:
- TBD | -| nextpage_opaque_marker | 0..1 | Marker to obtain the next page of a paged response. Shall be supported by the O-Cloud if the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource. | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.8.3.2-2. - -Table 3.2.4.4.3.2-2: Details of the GET request/response on this resource - -| Request body | Data type | Cardinality | Description | | -|---------------|-----------------------|------------------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | DeploymentManagerInfo | 0..N | 200 OK |

Shall be returned when information about zero or more DeploymentManagerInfo instances has been queried successfully.

The response body shall contain in an array the representations of zero or more DeploymentManagerInfo instances, as defined in clause 3.2.6.2.5.

If the "filter" URI parameter or one of the "all_fields", "fields" (if supported), "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request, the data in the response body shall have been transformed according to the rules specified in clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [22] , respectively.

If the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, inclusion of the Link HTTP header in this response shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013 [22] .

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute-based filtering expression.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute selector.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Response too big.

If the O-Cloud supports alternative 1 (error) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, this error response shall follow the provisions in clause 5.4.2.2 of ETSI GS NFV-SOL 013 [22] .

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### 3.2.4.8.3.3 PUT - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### 3.2.4.8.3.4 PATCH - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### 3.2.4.8.3.5 DELETE - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -#### 3.2.4.9 REST resource: Deployment Manager Description - -##### 3.2.4.9.1 Description - -The Deployment Manager Description represents the description of a Deployment Manager instance in the O-Cloud. This includes some mandatory attributes including a reference to the capabilities that defines it and allows for extended attributes as well. - -##### 3.2.4.9.2 Resource definition - -Resource URI: - -**{apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/deploymentManagers/{deploymentManagerId}** - -This resource shall support the resource URI variables defined in Table 3.2.4.9.2-1. - -**Table 3.2.4.9.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| deploymentManagerId | Identifier | The identifier of the Deployment Manager Description resource. | -| NOTE: This identifier can be retrieved from the deploymentManagerId attribute in the payload body of the response to a GET request getting the list of "DeploymentManagerInfo" resources. | | | - -##### 3.2.4.9.3 Resource methods - -###### 3.2.4.9.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### 3.2.4.9.3.2 GET - -The GET operation is used to retrieve the deployment manager description of a single deployment manager. - -This method shall support the URI query parameters specified in Table 3.2.4.9.3.2-1. - -**Table 3.2.4.9.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.9.3.2-2. - -**Table 3.2.4.9.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|-----------------------|------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | DeploymentManagerInfo | 1 | 200 OK | Shall be returned when information about a DeploymentManagerInfo instance has been queried successfully.
The response body shall contain a representation of the DeploymentManagerInfo instance, as defined in clause 3.2.6.2.2. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.2.4.9.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### **3.2.4.9.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### **3.2.4.9.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -#### **3.2.4.10 REST resource: Cloud Description** - -##### **3.2.4.10.1 Description** - -This resource represents the attributes of the O-Cloud instance and provides the Cloud Description. - -##### **3.2.4.10.2 Resource definition** - -Resource URI: {apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/ - -This resource shall support the resource URI variables defined in Table 3.2.4.10.2-1. - -**Table 3.2.4.10.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | string | See clause 3.1.2 | -| apiMajorVersion | string | See clause 3.1.2 | - -##### **3.2.4.10.3 Resource methods** - -###### **3.2.4.10.3.1 POST** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### **3.2.4.10.3.2 GET** - -The GET operation is used to retrieve the O-Cloud description. - -This method shall support the URI query parameters specified in Table 3.2.4.10.3.2-1. - -**Table 3.2.4.10.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|-----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| all_fields | 0..1 | Include all complex attributes in the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter. | -| fields | 0..1 | Complex attributes to be included into the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_fields | 0..1 | Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_default | 0..1 | Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.
The following attributes shall be excluded from the list of ResourceTypeInfo in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided:
- TBD | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.10.3.2-2. - -**Table 3.2.4.10.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|----------------|------------------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | OCloudInfo | 1 | 200 OK | Shall be returned when information for the OCloudInfo has been queried successfully.
The response body shall contain a representation of the OCloudInfo instance, as defined in clause 3.2.6.2.6. | -| | ProblemDetails | 1 | 400 Bad Request | Shall be returned upon the following error: Invalid attribute-based filtering expression.
The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error. | -| | ProblemDetails | 1 | 400 Bad Request | Shall be returned upon the following error: Invalid attribute selector.
The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.2.4.10.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### **3.2.4.10.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### 3.2.4.10.3.5 DELETE - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -#### 3.2.4.11 REST resource: Inventory Subscription List - -##### 3.2.4.11.1 Description - -This resource represents the set of Inventory Subscriptions in the O-Cloud the SMO can use for being notified when certain changes in the inventory object occur. The Inventory Subscription List contains Inventory Subscription Descriptions. - -##### 3.2.4.11.2 Resource definition - -Resource URI: {apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/subscriptions - -This resource shall support the resource URI variables defined in Table 3.2.4.11.2-1. - -**Table 3.2.4.11.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | - -##### 3.2.4.11.3 Resource methods - -###### 3.2.4.11.3.1 POST - -The POST operation is used to create an inventory subscription. - -This method shall support the URI query parameters specified in Table 3.2.4.11.3.1-1. - -**Table 3.2.4.11.3.1-1 URI query parameters supported by the POST method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.11.3.1-2. - -**Table 3.2.4.11.3.1-2: Details of the POST request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|---------------------------|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | Response Codes | Description | | | -| Response body | InventorySubscriptionInfo | 1 | The InventorySubscriptionInfo instance to be created as defined in clause 3.2.6.2.7. Note: The supplied SubscriptionId is ignored and assigned by the O-Cloud. | | -| | ProblemDetails | See clause 3.1.5 | 201 Created | Shall be returned when information about a InventorySubscriptionInfo instance has been created successfully. The response body shall contain a representation of the InventorySubscriptionInfo instance, as defined in clause 3.2.6.2.7. | -| | | | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### 3.2.4.11.3.2 GET - -The GET operation is used to retrieve the list of inventory subscriptions. - -This method shall support the URI query parameters specified in Table 3.2.4.11.3.2-1. - -**Table 3.2.4.11.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------------------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| filter | 0..1 | Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [22] .
The O-Cloud shall support receiving this parameter as part of the URI query string. The API consumer may supply this parameter.
All attribute names that appear in the InventorySubscriptionInfo and in data types referenced from it shall be supported by the O-Cloud in the filter expression. | -| all_fields | 0..1 | Include all complex attributes in the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter. | -| fields | 0..1 | Complex attributes to be included into the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_fields | 0..1 | Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_default | 0..1 | Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.
The following attributes shall be excluded from the list of InventorySubscriptionInfo in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided:
- TBD | -| nextpage_opaque_marker | 0..1 | Marker to obtain the next page of a paged response. Shall be supported by the O-Cloud if the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource. | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.11.3.2-2. - -**Table 3.2.4.11.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|---------------------------|------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | InventorySubscriptionInfo | 0..N | 200 OK |

Shall be returned when information about zero or more InventorySubscriptionInfo instances has been queried successfully.

The response body shall contain in an array the representations of zero or more InventorySubscriptionInfo instances, as defined in clause 3.2.6.2.7.

If the "filter" URI parameter or one of the "all_fields", "fields" (if supported), "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request, the data in the response body shall have been transformed according to the rules specified in clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [22] , respectively.

If the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, inclusion of the Link HTTP header in this response shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013 [22] .

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute-based filtering expression.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute selector.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Response too big.

If the O-Cloud supports alternative 1 (error) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, this error response shall follow the provisions in clause 5.4.2.2 of ETSI GS NFV-SOL 013 [22] .

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx |

In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned.

| - -###### **3.2.4.11.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### **3.2.4.11.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### **3.2.4.11.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -#### 3.2.4.12 REST resource: Inventory Subscription Description - -##### 3.2.4.12.1 Description - -The Inventory Subscription Description represents the description of a subscription to inventory change events in the O-Cloud. - -##### 3.2.4.12.2 Resource definition - -Resource URI: {apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/subscriptions/{subscriptionId} - -This resource shall support the resource URI variables defined in Table 3.2.4.12.2-1. - -**Table 3.2.4.12.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| subscriptionId | Identifier | The identifier of the Inventory Subscription Description resource. | -| NOTE: This identifier can be retrieved from the subscriptionId attribute in the payload body of the response to a GET request getting the list of "InventorySubscriptionInfo" resources. | | | - -##### 3.2.4.12.3 Resource methods - -###### 3.2.4.12.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### 3.2.4.12.3.2 GET - -The GET operation is used to retrieve the inventory subscription description of a single inventory subscription. - -This method shall support the URI query parameters specified in Table 3.2.4.12.3.2-1. - -**Table 3.2.4.12.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.12.3.2-2. - -**Table 3.2.4.12.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|---------------------------|------------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | InventorySubscriptionInfo | 1 | 200 OK | Shall be returned when information about a InventorySubscriptionInfo instance has been queried successfully.
The response body shall contain a representation of the InventorySubscriptionInfo instance, as defined in clause 3.2.6.2.7. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.2.4.12.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### **3.2.4.12.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### **3.2.4.12.3.5 DELETE** - -The DELETE operation is used to delete the inventory subscription description of a single inventory subscription. - -This method shall support the URI query parameters specified in Table 3.2.4.12.3.5-1. - -**Table 3.2.4.12.3.5-1 URI query parameters supported by the DELETE method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.12.3.5-2. - -**Table 3.2.4.12.3.5-2: Details of the DELETE request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|----------------|------------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | ProblemDetails | See clause 3.1.5 | 204
4xx/5xx | No content.
In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -#### **3.2.4.13 REST resource: Alarm Dictionary** - -##### **3.2.4.13.1 Description** - -The Alarm Dictionary REST resource dedicated to the Alarm Dictionary which describes alarms that are collected. The Alarm Dictionaries are integrated by the IMS in the O-Cloud and provided to the SMO for consumption. - -##### **3.2.4.13.2 Resource definition** - -###### **3.2.4.13.2.1 Resource URI for Alarm Dictionaries** - -Resource URI: -**{apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/alarmDictionaries/{alarmDictionaryId}** - -This resource shall support the resource URI variables defined in Table 3.2.4.13.2.1-1. - -**Table 3.2.4.13.2.1-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-------------------|------------|-----------------------------------------------------------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| alarmDictionaryId | Identifier | The alarmDictionaryId is a unique identifier that singles out an individual Alarm Dictionary of interest. | - -NOTE: This identifier can be retrieved from the alarmDictionaryId attribute in the payload body of the response to a GET request getting a "ResourceType" resource. It can also be retrieved from the payload body of the response to a GET request getting "AlarmDictionaries" - -###### **3.2.4.13.2.2 Resource URI for Resource Type Alarm Dictionary** - -Resource URI: -`{apiRoot}/O2ims_infrastructureInventory/{apiMajorVersion}/resourceTypes/{resourceTypeId}/alarmDictionary` - -This resource shall support the resource URI variables defined in Table 3.2.4.13.2.2-1. - -**Table 3.2.4.13.2.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|------------|---------------------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| resourceTypeId | Identifier | The identifier of the Resource Type Description resource. See Note. | - -NOTE: This identifier can be retrieved from the resourceTypeId attribute in the payload body of the response to a GET request getting the list of "ResourceType" resources. - -##### **3.2.4.13.3 Resource methods** - -###### **3.2.4.13.3.1 POST** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.13.3.2 GET** - -The GET operation is used to retrieve a single dictionary. - -This method shall support the URI query parameters specified in Table 3.2.4.13.3.2-1. - -**Table 3.2.4.13.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.13.3.2-2. - -**Table 3.2.4.13.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|-----------------|------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | AlarmDictionary | 1 | 200 OK | Shall be returned when information about an AlarmDictionary instance has been queried successfully. The response body shall contain a representation of the AlarmDictionary instance, as defined in clause 3.2.6.2.8. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.2.4.13.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.13.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.13.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### **3.2.4.14 REST resource: Alarm Dictionary List** - -##### **3.2.4.14.1 Description** - -The Alarm Dictionary List resource represents the collection of Alarm Dictionaries. The API consumer can use this resource to query multiple Alarm Dictionaries. - -##### **3.2.4.14.2 Resource definition** - -Resource URI: {apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/alarmDictionaries - -This resource shall support the resource URI variables defined in Table 3.2.4.14.2-1. - -**Table 3.2.4.14.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | - -##### **3.2.4.14.3 Resource methods** - -###### **3.2.4.14.3.1 POST** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.14.3.2 GET** - -The GET operation is used to retrieve a list of Alarm dictionaries. - -This method shall support the URI query parameters specified in Table 3.2.4.14.3.2-1. - -**Table 3.2.4.14.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Filter | 0..1 | Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [22].
The O-Cloud shall support receiving this parameter as part of the URI query string. The API consumer may supply this parameter.
All attribute names that appear in the AlarmDictionary shall be supported by the O-Cloud in the filter expression. | -| all_fields | 0..1 | Include all complex attributes in the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter. | -| Fields | 0..1 | Complex attributes to be included into the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_fields | 0..1 | Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_default | 0..1 | Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.
The following attributes shall be excluded from the list of AlarmDictionary in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided:
- alarmDefinition | -| nextpage_opaque_marker | 0..1 | Marker to obtain the next page of a paged response. Shall be supported by the O-Cloud if the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource. | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.14.3.2-2. - -Table 3.2.4.14.3.2-2: Details of the GET request/response on this resource - -| Request body | Data type | Cardinality | Description | | -|---------------|-----------------|------------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | AlarmDictionary | 0..N | 200 OK |

Shall be returned when information about zero or more AlarmDictionary instances has been queried successfully. The response body shall contain in an array the representations of zero or more AlarmDictionary instance(s), as defined in clause 3.2.6.2.8.

If the "filter" URI parameter or one of the "all_fields", "fields" (if supported), "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request, the data in the response body shall have been transformed according to the rules specified in clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [22], respectively.

If the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, inclusion of the Link HTTP header in this response shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013 [22].

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute-based filtering expression.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute selector.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Response too big.

If the O-Cloud supports alternative 1 (error) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, this error response shall follow the provisions in clause 5.4.2.2 of ETSI GS NFV-SOL 013 [22].

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### 3.2.4.14.3.3 PUT - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.2.4.14.3.4 PATCH - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.2.4.14.3.5 DELETE - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### 3.2.4.15 REST resource: Performance Dictionary - -##### 3.2.4.15.1 Description - -The Performance Dictionary REST resource dedicated to the Performance Dictionary which describes performance measurements that can be collected. The Performance Dictionaries are integrated by the IMS in the O-Cloud and provided to the SMO for consumption. - -##### 3.2.4.15.2 Resource definition - -###### 3.2.4.15.2.1 Resource URI for Performance Dictionaries - -Resource URI: - -**{apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/performanceDictionaries/{performanceDictionaryId}** - -This resource shall support the resource URI variables defined in Table 3.2.4.15.2.1-1. - -**Table 3.2.4.15.2.1-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-------------------------|------------|-----------------------------------------------------------------------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| performanceDictionaryId | Identifier | The performanceDictionaryId is a unique identifier that singles out an individual performance dictionary of interest. | - -NOTE: This identifier can be retrieved from the performanceDictionaryId attribute in the payload body of the response to a GET request getting a "ResourceType" resource. It can also be retrieved from the payload body of the response to a GET request getting "PerformanceDictionaries" - -###### 3.2.4.15.2.2 Resource URI for Resource Type Performance Dictionary - -Resource URI: - -**{apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/resourceTypes/{resourceTypeId}/performanceDictionary** - -This resource shall support the resource URI variables defined in Table 3.2.4.15.2.2-1. - -**Table 3.2.4.15.2.2-2 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|------------|---------------------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| resourceTypeId | Identifier | The identifier of the Resource Type Description resource. See Note. | - -NOTE: This identifier can be retrieved from the resourceTypeId attribute in the payload body of the response to a GET request getting the list of "ResourceType" resources. - -##### 3.2.4.15.3 Resource methods - -###### 3.2.4.15.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.2.4.15.3.2 GET - -The GET operation is used to retrieve a single dictionary. - -This method shall support the URI query parameters specified in Table 3.2.4.15.3.2-1. - -**Table 3.2.4.15.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.15.3.2-2. - -**Table 3.2.4.15.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|-----------------------|------------------|----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | PerformanceDictionary | 1 | 200 OK | Shall be returned when information about an PerformanceDictionary instance has been queried successfully. The response body shall contain a representation of the PerformanceDictionary instance, as defined in clause 3.2.6.2.11. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.2.4.15.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.15.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.15.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### **3.2.4.16 REST resource: Performance Dictionary List** - -##### **3.2.4.16.1 Description** - -The Performance Dictionary List resource represents the collection of Performance Dictionaries. The API consumer can use this resource to query multiple Performance Dictionaries. - -##### **3.2.4.16.2 Resource definition** - -Resource URI: {apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/performanceDictionaries - -This resource shall support the resource URI variables defined in Table 3.2.4.16.2-1. - -**Table 3.2.4.16.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | - -##### 3.2.4.16.3 Resource methods - -###### 3.2.4.16.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.2.4.16.3.2 GET - -The GET operation is used to retrieve a list of Performance dictionaries. - -This method shall support the URI query parameters specified in Table 3.2.4.16.3.2-1. - -**Table 3.2.4.16.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Filter | 0..1 | Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [22].
The O-Cloud shall support receiving this parameter as part of the URI query string. The API consumer may supply this parameter.
All attribute names that appear in the PerformanceDictionary shall be supported by the O-Cloud in the filter expression. | -| all_fields | 0..1 | Include all complex attributes in the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter. | -| Fields | 0..1 | Complex attributes to be included into the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_fields | 0..1 | Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_default | 0..1 | Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.
The following attributes shall be excluded from the list of PerformanceDictionary in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided:
- PerformanceMeasureDefinition | -| nextpage_opaque_marker | 0..1 | Marker to obtain the next page of a paged response. Shall be supported by the O-Cloud if the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource. | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.16.3.2-2. - -**Table 3.2.4.16.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|-----------------------|------------------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | PerformanceDictionary | 0..N | 200 OK |

Shall be returned when information about zero or more PerformanceDictionary instances has been queried successfully. The response body shall contain in an array the representations of zero or more PerformanceDictionary instance(s), as defined in clause 3.2.6.2.12.

If the "filter" URI parameter or one of the "all_fields", "fields" (if supported), "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request, the data in the response body shall have been transformed according to the rules specified in clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [22], respectively.

If the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, inclusion of the Link HTTP header in this response shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013 [22].

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute-based filtering expression.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute selector.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Response too big.

If the O-Cloud supports alternative 1 (error) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, this error response shall follow the provisions in clause 5.4.2.2 of ETSI GS NFV-SOL 013 [22].

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx |

In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned.

| - -###### **3.2.4.16.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.16.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.16.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### 3.2.4.17 REST resource: Location List - -##### 3.2.4.17.1 Description - -This resource represents the list of Locations where O-Cloud Sites can be available. The Location List contains Location Descriptions. - -##### 3.2.4.17.2 Resource definition - -Resource URI: {apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/locations - -This resource shall support the resource URI variables defined in Table 3.2.4.17.2-1. - -**Table 3.2.4.17.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | - -##### 3.2.4.17.3 Resource methods - -###### 3.2.4.17.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.2.4.17.3.2 GET - -The GET operation is used to retrieve the list of locations. - -This method shall support the URI query parameters specified in Table 3.2.4.17.3.2-1. - -**Table 3.2.4.17.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------------------------|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| filter | 0..1 | Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [22].
The O-Cloud shall support receiving this parameter as part of the URI query string. The API consumer may supply this parameter.
All attribute names that appear in the LocationInfo and in data types referenced from it shall be supported by the O-Cloud in the filter expression. | -| all_fields | 0..1 | Include all complex attributes in the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter. | -| fields | 0..1 | Complex attributes to be included into the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_fields | 0..1 | Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_default | 0..1 | Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.
The following attributes shall be excluded from the list of LocationInfo in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided:
- TBD | -| nextpage_opaque_marker | 0..1 | Marker to obtain the next page of a paged response. Shall be supported by the O-Cloud if the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource. | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.17.3.2-2. - -**Table 3.2.4.17.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|----------------|------------------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | LocationInfo | 0..N | 200 OK |

Shall be returned when information about zero or more LocationInfo instances has been queried successfully. The response body shall contain in an array the representations of zero or more LocationInfo instances, as defined in clause 3.2.6.2.16.

If the "filter" URI parameter or one of the "all_fields", "fields" (if supported), "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request, the data in the response body shall have been transformed according to the rules specified in clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [22] , respectively.

If the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, inclusion of the Link HTTP header in this response shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013 [22] .

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute-based filtering expression.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute selector.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Response too big.

If the O-Cloud supports alternative 1 (error) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, this error response shall follow the provisions in clause 5.4.2.2 of ETSI GS NFV-SOL 013 [22] .

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx |

In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned.

| - -###### **3.2.4.17.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.17.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.2.4.17.3.5 DELETE - -3.2.4.18 This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22].**REST resource: Location Description** - -##### 3.2.4.18.1 Description - -This resource represents the description of a Location and provides information about its characteristics and other data. - -##### 3.2.4.18.2 Resource definition - -Resource URI: {apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/locations/{globalLocationId} - -This resource shall support the resource URI variables defined in Table 3.2.4.18.2-1. - -**Table 3.2.4.18.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| globalLocationId | Identifier | The identifier of the Location Description resource. See note. | -| NOTE: This identifier can be retrieved from the globalLocationId attribute in the payload body of the response to a GET request getting the list of "Location" resources. | | | - -##### 3.2.4.18.3 Resource methods - -###### 3.2.4.18.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.2.4.18.3.2 GET - -The GET operation is used to retrieve the resource type description of a single location. - -This method shall support the URI query parameters specified in Table 3.2.4.18.3.2-1. - -**Table 3.2.4.18.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------|-------------|-------------| -| n/a | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.18.3.2-2. - -**Table 3.2.4.18.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|----------------|------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | LocationInfo | 1 | 200 OK | Shall be returned when information about a LocationInfo instance has been queried successfully. The response body shall contain a representation of the LocationInfo instance, as defined in clause 3.2.6.2.16. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.2.4.18.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.18.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.18.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### **3.2.4.19 REST resource: O-Cloud Site List** - -##### **3.2.4.19.1 Description** - -This resource represents the list of O-Cloud Sites. The O-Cloud Site List contains O-Cloud Site Descriptions. - -##### **3.2.4.19.2 Resource definition** - -Resource URI: {apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/oCloudSites - -This resource shall support the resource URI variables defined in Table 3.2.4.19.2.-1. - -**Table 3.2.4.19.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | - -##### **3.2.4.19.3 Resource methods** - -###### **3.2.4.19.3.1 POST** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.19.3.2 GET** - -The GET operation is used to retrieve the list of O-Cloud Sites. - -This method shall support the URI query parameters specified in Table 3.2.4.19.3.2-1. - -**Table 3.2.4.19.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| filter | 0..1 | Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [22].
The O-Cloud shall support receiving this parameter as part of the URI query string. The API consumer may supply this parameter.
All attribute names that appear in the OCloudSiteInfo and in data types referenced from it shall be supported by the O-Cloud in the filter expression. | -| all_fields | 0..1 | Include all complex attributes in the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter. | -| fields | 0..1 | Complex attributes to be included into the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_fields | 0..1 | Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_default | 0..1 | Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.
The following attributes shall be excluded from the list of OCloudSiteInfo in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided:
- TBD | -| nextpage_opaque_marker | 0..1 | Marker to obtain the next page of a paged response. Shall be supported by the O-Cloud if the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource. | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.19.3.2-2. - -**Table 3.2.4.19.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|----------------|------------------|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | OCloudSiteInfo | 0..N | 200 OK |

Shall be returned when information about zero or more OCloudSiteInfo instances has been queried successfully.

The response body shall contain in an array the representations of zero or more OCloudSiteInfo instances, as defined in clause 3.2.6.2.17.

If the "filter" URI parameter or one of the "all_fields", "fields" (if supported), "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request, the data in the response body shall have been transformed according to the rules specified in clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [22] , respectively.

If the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, inclusion of the Link HTTP header in this response shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013 [22] .

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute-based filtering expression.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute selector.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Response too big.

If the O-Cloud supports alternative 1 (error) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, this error response shall follow the provisions in clause 5.4.2.2 of ETSI GS NFV-SOL 013 [22] .

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx |

In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned.

| - -###### **3.2.4.19.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.19.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.2.4.19.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### 3.2.4.20 REST resource: O-Cloud Site Description - -##### 3.2.4.20.1 Description - -This resource represents the description of an O-Cloud Site. The O-Cloud Site Description is a record of the attributes. - -##### 3.2.4.20.2 Resource definition - -Resource URI: {apiRoot}/O2ims\_infrastructureInventory/{apiMajorVersion}/oCloudSites/{oCloudSiteId} - -This resource shall support the resource URI variables defined in Table 3.2.4.20.2-1. - -**Table 3.2.4.20.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| oCloudSiteId | Identifier | The identifier of the O-Cloud Site Description resource. See note. | -| NOTE: This identifier can be retrieved from the oCloudSiteId attribute in the payload body of the response to a GET request getting the list of "OCloudSite" resources. | | | - -##### 3.2.4.20.3 Resource methods - -###### 3.2.4.20.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.2.4.20.3.2 GET - -The GET operation is used to retrieve the resource type description of a single O-Cloud site. - -This method shall support the URI query parameters specified in Table 3.2.4.20.3.2-1. - -**Table 3.2.4.20.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------|-------------|-------------| -| n/a | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.2.4.20.3.2-2. - -**Table 3.2.4.20.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|----------------|------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | OCloudSiteInfo | 1 | 200 OK | Shall be returned when information about an OCloudSiteInfo instance has been queried successfully.
The response body shall contain a representation of the OCloudSiteInfo instance, as defined in clause 3.2.6.2.17. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### 3.2.4.20.3.3 PUT - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.2.4.20.3.4 PATCH - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.2.4.20.3.5 DELETE - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -### 3.2.5 Notifications - -#### 3.2.5.1 General - -Notifications shall comply to the Subscribe/Notify pattern described in clause 5.9 of ETSI GS NFV-SOL 015 [25]. - -**Table 3.2.5.1-1 Notifications overview** - -| Notification | Callback URI | HTTP method | Description | -|-------------------------------|---------------------------------|-------------|----------------------------------------------------------------------| -| Inventory Change Notification | Inventory Subscription.callback | POST | Notify subscribers when objects in the O2ims inventory have changed. | - -##### 3.2.5.1.1 Inventory Change Notification Description - -The Inventory Change Notification is used by the O-Cloud Infrastructure Management Service to report changes to the O2ims Inventory to a O2ims consumer that has subscribed to such notifications. - -##### 3.2.5.1.2 Target URI - -The Inventory Subscription.Callback URI "{InventoryEventNotification}" shall be used with the callback URI variables define in table 3.2.5.1.2-1. - -**Table 3.2.5.1.2-1 Inventory Subscription.Callback URI Variables** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------------|------------|----|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| consumerSubscriptionId | Identifier | O | 0..1 | The value provided by the consumer in the subscription. | -| notificationEventType | Integer | M | 1 | One of the following values:
  • 0 for “CREATE”
  • 1 for “MODIFY”
  • 2 for “DELETE”
| -| objectRef | String | CO | 0..1 | The URL to the object. This is not required if the notificationEventType is 2 (DELETE). It will point to one of the following data types defined in clause 3.2.6 and the reference will match the type of objects supplied in priorObjectState and/or postObjectState:
  • ResourceInfo
  • ResourceTypeInfo
  • ResourcePoolInfo
  • DeploymentManagerInfo
  • CloudInfo
  • LocationInfo
  • OCloudSiteInfo
| -| priorObjectState | String | CM | 0..1 | This is required if the notificationEventType is 1 (MODIFY) or 2 (DELETE) and is one of the following data types defined in clause 3.2.6 and will match the type of object in postObjectState and/or the type referred to in objectRef:
  • ResourceInfo
  • ResourceTypeInfo
  • ResourcePoolInfo
  • DeploymentManagerInfo
  • CloudInfo
  • LocationInfo
  • OCloudSiteInfo
| -| postObjectState | String | CM | 0..1 | This is required if the notificationEventType is 0 (CREATE) or 1 (MODIFY) and is one of the following data types defined in clause 3.2.6 and will match the type of object in priorObjectState and/or the type referred to in objectRef:
  • ResourceInfo
  • ResourceTypeInfo
  • ResourcePoolInfo
  • DeploymentManagerInfo
  • CloudInfo
  • LocationInfo
  • OCloudSiteInfo
| - -### 3.2.6 Data model - -#### 3.2.6.1 REST resource data types - -This clause specifies the data types to be used in resource representations and notifications supported by the present API. - -Table 3.2.6.1-1 specifies the data types defined for the O2ims\_InfrastructureInventory service API. - -**Table 3.2.6.1-1: O2ims\_InfrastructureInventory resource data types** - -| Data type | Clause defined | Description | Applicability | -|---------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| ResourceTypeInfo | 3.2.6.2.2 | This data type represents the type of a resource deployed in the O-Cloud Infrastructure. | | -| ResourcePoolInfo | 3.2.6.2.3 | This data type represents a logical Resource Pool for the collection of O-Cloud Resources at a location. | | -| ResourceInfo | 3.2.6.2.4 | This data type represents a resource instance of the O-Cloud Infrastructure | | -| DeploymentManagerInfo | 3.2.6.2.5 | This data type represents a Deployment Manager for managing Deployments into the O-Cloud. | | -| CloudInfo | 3.2.6.2.6 | This data type represents an O-Cloud instance. | | -| InventorySubscriptionInfo | 3.2.6.2.7 | This data type represents an instance of a subscription to O2ims Inventory change events. | | -| AlarmDictionary | 3.2.6.2.8 | This data type represents an Alarm Dictionary for alarms that can be reported by a given ResourceType within the O-Cloud. | | -| PerformanceDictionary | 3.2.6.2.12 | This data type represents a Performance Dictionary of performance measurement definitions that can be reported for a given ResourceType within the O-Cloud. | | -| LocationInfo | 3.2.6.2.16 | This data type represents a location instance where O-Cloud Sites can be available. | | -| OCloudSiteInfo | 3.2.6.2.17 | This data type represents an O-Cloud Site instance. | | - -#### 3.2.6.2 Structured data types - -##### 3.2.6.2.1 Introduction - -This clause defines the structures to be used in resource representations. - -##### 3.2.6.2.2 Type: ResourceTypeInfo - -This type represents information about a type of a resource deployed in the O-Cloud Infrastructure. It shall comply with the provisions defined in table 3.2.6.2.2-1. - -**Table 3.2.6.2.2-1 Definition of type ResourceTypeInfo** - -| Attribute name | Data type | P | Cardinality | Description | -|-------------------------|-----------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| resourceTypeId | Identifier | M | 1 | Identifier for the Resource Type. This identifier is allocated by the O-Cloud. | -| name | String | M | 1 | Human readable name of the resource type. | -| description | String | M | 1 | Human readable description of the resource type. | -| vendor | String | M | 1 | Provider of the Resource. | -| model | String | M | 1 | Information about the model of the resource as defined by its provider. | -| version | String | M | 1 | Version or generation of the resource as defined by its provider. | -| alarmDictionary | AlarmDictionary | M | 0..1 | Dictionary of alarms for this resource type. See Note 1. | -| alarmDictionaryId | Identifier | M | 0..1 | Identifier of the Alarm Dictionary for this resource type. See Note 2. | -| performanceDictionaryId | Identifier | M | 0..1 | Identifier of the Performance Dictionary for this resource type. See Note 2. | -| resourceKind | Enum (inlined) | M | 1 | Value describing “physicality” of the resource type
Permitted values:
  • UNDEFINED
  • PHYSICAL
  • LOGICAL
| -| resourceClass | Enum (inlined) | M | 1 | Functional role of the resource type within the cloud.
Permitted values:
  • UNDEFINED
  • COMPUTE
  • NETWORKING
  • STORAGE
| -| extensions | KeyValues | M | 0..1 | List of metadata key-value pairs used to associate meaningful metadata to the related resource type. | - -NOTE 1: alarmDictionary attribute is deprecated and it may be removed in future releases. - -NOTE 2: The IMS shall ensure that the identifier points to the same dictionary available under the URI path of the resource type (refer to Table 3.2.3-1). - -##### 3.2.6.2.3 Type: ResourcePoolInfo - -This type represents information about a logical Resource Pool which comprises O-Cloud Resources at a location. It shall comply with the provisions defined in table 3.2.6.2.3-1. - -**Table 3.2.6.2.3-1 Definition of type ResourcePoolInfo** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------|------------|---|-------------|-----------------------------------------------------------------------------------------------------------| -| resourcePoolId | Identifier | M | 1 | Identifier for the resource pool in the O-Cloud instance. This identifier is allocated by the O-Cloud. | -| oCloudId | Identifier | M | 1 | Identifier for the containing O-Cloud. (NOTE 1) | -| globalLocationId | Identifier | M | 1 | This identifier is copied from the O-Cloud Id assigned by the SMO during the O-Cloud deployment. (NOTE 2) | -| name | String | M | 1 | Human readable name of the resource pool. | -| oCloudSiteId | Identifier | M | 1 | Identifier of the O-Cloud site the resource pool is a part of. | -| description | String | M | 1 | Human readable description of the resource pool. | -| location | String | O | 0..1 | Information about the geographical location of the resource pool as detected by the O-Cloud. (NOTE 3) | -| extensions | KeyValues | O | 0..1 | List of metadata key-value pairs used to associate meaningful metadata to the related resource pool. | - -NOTE 1: oCloudId attribute is deprecated and may be removed in future releases. - -NOTE 2: globalLocationId attribute is deprecated and may be removed in future releases. - -NOTE 3: location attribute is deprecated and may be removed in future releases. - -##### 3.2.6.2.4 Type: ResourceInfo - -This type represents a resource instance of the O-Cloud Infrastructure. It shall comply with the provisions defined in table 3.2.6.2.4-1. - -**Table 3.2.6.2.4-1 Definition of type ResourceInfo** - -| Attribute name | Data type | P | Cardinality | Description | -|----------------|---------------|----|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| resourceId | Identifier | M | 1 | Identifier for the Resource. This identifier is allocated by the O-Cloud. | -| resourcePoolId | Identifier | M | 1 | Identifier of the Resource Pool containing this resource (refer to type “ResourcePoolInfo”). | -| resourceTypeId | Identifier | M | 1 | Identifier for the Resource Type of this resource (refer to type “ResourceTypeInfo”). | -| globalAssetId | String | CM | 0..1 | Identifier or serial number of the resource, if available. It is required only if the resource has been identified during its addition to the cloud as a reportable asset in the SMO inventory. | -| description | String | M | 1 | Human readable description of the resource | -| elements | ResourceInfo | M | 0..N | The resource might be composed of smaller resources or other resource instances of a different type | -| tags | String | M | 0..N | Keywords describing or classifying the resource instance. | -| groups | String | M | 0..N | Keywords denoting groups a resource belongs to. | -| extensions | KeyValuePairs | M | 0..1 | List of metadata key-value pairs used to associate meaningful metadata to the related resource. | - -##### 3.2.6.2.5 Type: DeploymentManagerInfo - -This type represents information about a Deployment Manager for managing Deployments into the O-Cloud. It shall comply with the provisions defined in table 3.2.6.2.5-1. - -**Table 3.2.6.2.5-1 Definition of type DeploymentManagerInfo** - -| Attribute name | Data type | P | Cardinality | Description | -|---------------------|---------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| deploymentManagerId | Identifier | M | 1 | Identifier for the Deployment Manager. This identifier is allocated by the O-Cloud. | -| name | String | M | 1 | Human readable name of the deployment manager. | -| description | String | M | 1 | Human readable description of the deployment manager. | -| oCloudId | Identifier | M | 1 | Identifier for the containing O-Cloud. | -| serviceUri | Uri | M | 1 | The fully qualified URI to a Deployment Management server for O2dms services. Since the O2dms provides multiple services, this entry is for the {apiRoot} only. | -| supportedLocations | String | M | 1..N | List of globalLocationIDs that were assigned to the O-Cloud Site(s) which this Deployment Manager supports. | -| capabilities | KeyValuePairs | M | 0..N | Information about the capabilities supported by the Deployment Manager and its set of deployment management services based on the resources allocated to the Deployment Manager. | -| capacity | KeyValuePairs | M | 0..N | Information about the available, allocated and reserved capacity of O-Cloud Resources allocated to the Deployment Manager. | -| extensions | KeyValuePairs | O | 0..N | List of metadata key-value pairs used to associate meaningful metadata to the related Deployment Manager. | - -##### 3.2.6.2.6 Type: CloudInfo - -This type represents information about an O-Cloud instance. It shall comply with the provisions defined in table 3.2.6.2.6-1. - -**Table 3.2.6.2.6-1 Definition of type CloudInfo** - -| Attribute name | Data type | P | Cardinality | Description | -|----------------|------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| oCloudId | Identifier | M | 1 | Identifier of the O-Cloud instance. Internally generated within an O-Cloud instance. | -| globalCloudId | Identifier | M | 1 | Identifier of the O-Cloud instance. Globally unique across O-Cloud instances. This value was provided by the SMO with the callback URI at the beginning of O-Cloud genesis and used in registration at the end of genesis. | -| name | String | M | 1 | Human readable name of the O-Cloud. | -| description | String | M | 1 | Human readable description of the O-Cloud. | -| serviceUri | Uri | M | 1 | The fully qualified URI root to all services provided by the O2ims interface, Inventory only being one of them. Since the O2ims provides multiple services this entry is for the {apiRoot} only. | -| extensions | KeyValues | M | 0..1 | These are unspecified (not standardized) properties (keys) which are tailored by the vendor to extend the information provided about the O-Cloud. | - -##### 3.2.6.2.7 Type: InventorySubscriptionInfo - -This type represents information about an instance of a subscription to O2ims Inventory change events. It shall comply with the provisions defined in table 3.2.6.2.7-1. - -**Table 3.2.6.2.7-1 Definition of type InventorySubscriptionInfo** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------------|------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| subscriptionId | Identifier | M | 1 | Identifier for the Subscription. This identifier is allocated by the O-Cloud. | -| consumerSubscriptionId | String | O | 0..1 | Identifier for the consumer of events sent due to the Subscription. | -| filter | String | O | 0..1 | Criteria for events which do not need to be reported or will be filtered by the subscription notification service. Therefore, if a filter is not provided then all events are reported. | -| callback | Uri | M | 1 | The fully qualified URI to a consumer procedure which can process a Post of the InventoryEventNotification. | - -##### 3.2.6.2.8 Type: AlarmDictionary - -This type represents information about alarms that can be reported by a given ResourceType within the O-Cloud. The Alarm Dictionary object is defined not only for O-Clouds but for Network Functions as well. Therefore, its structure may overlap with other O-Cloud structures and contain redundant information that is used by the SMO. It shall comply with the provisions defined in table 3.2.6.2.8-1. - -**Table 3.2.6.2.8-1 Definition of type AlarmDictionary** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------------------|-------------------------------------------------------------------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| alarmDictionaryId | Identifier | M | 1 | The Identifier of the Alarm Dictionary. The Identifier is unique within an O-Cloud. | -| alarmDictionaryVersion | String | M | 1 | Version of the Alarm Dictionary. Version is vendor defined such that the version of the dictionary can be associated with a specific version of the software delivery of this product. | -| alarmDictionarySchemaVersion | String Constant (See Note 1) | M | 1 | Version of the Alarm Dictionary Schema to which this alarm dictionary conforms. (See Note 2) | -| entityType | String | M | 1 | O-RAN entity type emitting the alarm: This shall be unique per vendor ResourceType.model and ResourceType.version | -| vendor | String | M | 1 | Vendor of the Entity Type to whom this Alarm Dictionary applies. This should be the same value as in the ResourceType.vendor attribute. | -| managementInterfaceId | ENUM
-O1
-O2DMS
-O2IMS
-OpenFH

(See Note 3) | M | 1..N | List of management interface over which alarms are transmitted for this Entity Type.

RESTRICTION: For the O-Cloud IMS Services this value is limited to O2IMS. | -| pkNotificationField | String Constant "alarmDefinitionId" | M | 1..N | Identifies which field or list of fields in the alarm notification contains the primary key (PK) into the Alarm Dictionary for this interface; i.e. which field contains the Alarm Definition ID. | -| alarmDefinition | AlarmDefinition | M | 1..N | Contains the list of alarms that can be detected against this ResourceType. | -| probableCauses | ProbableCause | M | 1..N | Contains the list of Probable Causes that indicate the root cause of the Alarm events. | - -NOTE 1: String value is not yet defined but would match a specific Schema Version. -NOTE 2: The specific value for this should be defined in the IM/DM specification for the Alarm Dictionary Model Schema when it is published at a future date. -NOTE 3: Italicized and grayed text is only provided for informative purposes. These values are used by other dictionary providers, but not the O2 IMS. - -##### 3.2.6.2.9 Type: AlarmDefinition - -This type represents information about an alarm that can be reported by a given ResourceType within the O-Cloud. It shall comply with the provisions defined in table 3.2.6.2.9-1. - -Table 3.2.6.2.9-1 Definition of type AlarmDefinition - -| Attribute name | Data type | P | Cardinality | Description | -|-----------------------|----------------------------------------------------------------------------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| alarmDefinitionId | UUID | M | 1 | Provides a unique identifier of the alarm being raised. This is the Primary Key into the Alarm Dictionary. | -| alarmName | String | M | 1 | Provides short name for the alarm. | -| alarmLastChange | String | M | 1 | Indicates the Alarm Dictionary Version in which this alarm last changed. | -| alarmChangeType | ENUM:
-added
-deleted
-modified | M | 1 | Indicates the type of change that occurred during the alarm last change; added, deleted, modified. | -| alarmDescription | String | M | 1 | Provides a longer descriptive meaning of the alarm condition and a description of the consequences of the alarm condition. This is intended to be read by an operator to give an idea of what happened and a sense of the effects, consequences, and other impacted areas of the system. | -| proposedRepairActions | String | M | 1 | Provides guidance for proposed repair actions. | -| clearingType | ENUM:
-automatic
-manual | M | 1 | Identifies whether alarm is cleared automatically or manually. | -| managementInterfaceId | ENUM
-O1
-O2DMS
-O2IMS
-OpenFH
(See Note 1) | M | 0..N | List of management interface over which alarms are transmitted for this Entity Type.

RESTRICTION: For the O-Cloud IMS Services this value is limited to O2IMS. | -| pkNotificationField | String Constant
"alarmDefinitionId" | M | 0..N | Identifies which field or list of fields in the alarm notification contains the primary key (PK) into the Alarm Dictionary for this interface; i.e. which field contains the Alarm Definition ID. | -| alarmAdditionalFields | KeyValuesPairs | M | 0..N | List of metadata key-value pairs used to associate meaningful metadata to the related resource type. | - -NOTE 1: Italicized and grayed text is only provided for informative purposes. These values are used by other dictionary providers, but not the O2 IMS. - -##### 3.2.6.2.10 Type: ProbableCause - -This type represents information about the ProbableCause which provides an indication of the root cause of an alarm event. ProbableCause is intended to help operators determine the root cause of an alarm event. It shall comply with the provisions defined in table 3.2.6.2.10-1. - -There are industry suggested lists of probable causes that could be used. When used the ProbableCause definition should allow for an indication of such a source. See O-RAN WG10 Information Model and Data Models [37], clause 5.2.1.4.13. - -Alarm Definitions may provide one or more ProbableCause(s) as part of their extended fields. However, each alarm event should have a ProbableCause that is specific to that alarm instance. The ProbableCause(s) used by the product vendor for alarm events shall be listed independently in the alarm dictionary. - -**Table 3.2.6.2.10-1 Definition of type ProbableCause** - -| Attribute name | Data type | P | Cardinality | Description | -|--------------------------|-------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------| -| probableCauseCode | String | M | 1 | This identifies a specific probableCause instance in the AlarmDictionary. This is the Primary Key into the probableCauses. | -| probableCauseDescription | String | M | 1 | This provides any additional information beyond the probableCauseCode to describe the probable cause | -| standardReference | StandardReference | M | 0..1 | This gives a reference to the standard body when the Probable Cause definition has been provided by another Standards body. | - -##### 3.2.6.2.11 Type: StandardReference - -When definition has been provided by another Standards body this dataType provides a reference to the standard body that is author of particular definition, as well as to where the definition can be found. It shall comply with the provisions defined in table 3.2.6.2.11-1. - -**Table 3.2.6.2.11-1 Definition of type StandardReference** - -| Attribute name | Data type | P | Cardinality | Description | -|--------------------------------|-----------|---|-------------|--------------------------------------------------------| -| standardDefinitionOrganization | String | M | 1 | Provides the Organization that provided the Definition | -| standardSpecification | String | M | 1 | Gives the Specification of the Standards Organization | -| versionOrRelease | String | M | 1 | Gives the version of the Specification of interest | - -NOTE: With reference to the baseline modeling in the O-RAN.WG10.Information Model and Data Models [37], the “clause” attribute in the type “StandardReference” is not specified in the present document version. - -##### 3.2.6.2.12 Type: PerformanceDictionary - -This type represents information about performance measurements for a performance dictionary that can be reported by a given ResourceType within the O-Cloud. It shall comply with the provisions defined in table 3.2.6.2.12-1. These are also described in O-RAN.WG10.Information Model and Data Models [37], clause 5.2.1. - -**Table 3.2.6.2.12-1 Definition of type PerformanceDictionary** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------------------------|----------------------------------------------------------------------------------------|---|-------------|-------------------------------------------------------------------------------------| -| performanceDictionaryId | Identifier | M | 1 | The Identifier of the Alarm Dictionary. The Identifier is unique within an O-Cloud. | -| performanceDictionaryVersion | String | M | 1 | Version of the Performance Dictionary | -| performanceDictionarySchemaVersion | String | M | 1 | Schema Version of the Performance Dictionary | -| vendorSoftwareProduct | String | M | 1 | Vendor Software Product | -| supportedInterfaces | ENUM
-O1
-O2DMS
-O2IMS
-OpenFH
(See Note 1) | M | 1 | This gives the supported interfaces for the Performance Dictionary | -| supportedMeasurements | PerformanceMeasurementDefinition | M | 1..N | This lists the supported Performance Measurements | - -NOTE 1: Italicized and grayed text is only provided for informative purposes. These values are used by other dictionary providers, but not the O2 IMS. - -##### 3.2.6.2.13 Type: PerformanceMeasurementDefinition - -This type represents a performance measurement definition. The PerformanceMeasurementDefinition inherits attributes from Top IOC (defined in 3GPP TS 28.622 [39], clause 4.3.29). It shall comply with the provisions defined in table 3.2.6.2.13-1. - -**Table 3.2.6.2.13-1 Definition of type PerformanceMeasurementDefinition** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------------------------|--------------------------------------|---|-------------------------------------|-----------------------------------------------------------------------------------------------------------------------| -| performanceMeasurementDefinitionId | UUID | M | 1 | Provides a unique identifier of the performance Measurement. This is the Primary Key into the Performance Dictionary. | -| performanceMeasurementId | String | M | 1 | This gives the Performance Measurement Id | -| standardReference | String | M | 1 | Gives the Standards Reference from which this Performance Measurement comes from | -| supportedInterfaces | String | M | 0..1 | Supported Interfaces | -| extensions | Key/ValuePairs | M | 0..1 | This gives Extension | -| measurementDefinition | 3GPPPerformanceMeasurementDefinition | M | 0 if ETSI, 1 if 3GPP.
(See Note) | If it is a 3GPP measurement, this would use the 3GPP Performance Measurement Definition (concrete class). See Note | -| measurementDefinition | ETSIPerformanceMeasurementDefinition | M | 0 if 3GPP, 1 if ETSI.
(See Note) | If it is a ETSI measurement, this would use the ETSI Performance Measurement Definition (concrete class). See Note | - -NOTE: The measurementDefinition would be either 3GPPPerformanceMeasurementDefinition or ETSIPerformanceMeasurementDefinition. The “P” is “M” because this needs to be supported on the interface. - -##### 3.2.6.2.14 Type: 3GPPPerformanceMeasurementDefinition - -The 3GPPPerformanceMeasurementDefinition is a concrete class of the PerformanceMeasurementDefinition\_ class from which it inherits attributes from. It extends the class with attribute fields defined in 3GPP TS 32.404 [40] clause 3.3. - -##### 3.2.6.2.15 Type: ETSIPerformanceMeasurementDefinition - -The ETSIPerformanceMeasurementDefinition is a concrete class of the PerformanceMeasurementDefinition\_ class from which it inherits attributes from. It extends the class with attribute fields defined in ETSI GS NFV-IFA 027 [41] clause 5. - -##### 3.2.6.2.16 Type: LocationInfo - -This type represents information about a location, where O-Cloud Site may be available. It shall comply with the provisions defined in table 3.2.6.2.16-1. - -**Table 3.2.6.2.16-1 Definition of type LocationInfo** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------|------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| globalLocationId | String | M | 1 | Identifier of the location as defined by the SMO. | -| name | String | M | 1 | Human readable name of the location as defined by the SMO. | -| description | String | M | 1 | Human readable description of the location. | -| oCloudSiteIds | Identifier | M | 0.. N | List of O-Cloud Site identifiers referencing the O-Cloud Sites available at the location. | -| coordinate | Point (see [43]) | M | 0.. N | The coordinates (including latitude and longitude) of the location. The content of this attribute shall follow the provisions for the “Point” geometry object as defined IETF RFC 7946 [43], for which the “type” member shall be set to the value “Point”. See note. | - -| | | | | | -|------------------------------------------------------------------------------------------------|---------------------|---|-------|---------------------------------------------------------------------------------------------------------------------------------------| -| civicAdress | Structure (inlined) | M | 0..N | Civic address of the location. It includes zero or more elements comprising the civic address. See note. | -| >caType | Integer | M | 1 | Describes the content type of caValue. The value of caType shall comply with IETF RFC 4776 [45]. | -| >caValue | String | M | 1 | Content of civic address element corresponding to the caType. The format caValue shall comply with section 3.4 of IETF RFC 4776 [45]. | -| address | String | M | 0.. 1 | Human readable format of address of the location. See note. | -| extensions | KeyValuePairs | M | 0..1 | List of metadata key-value pairs used to associate meaningful metadata to the related location. | -| NOTE: At least one of the ‘‘coordinate’’ or ‘‘civicAddress’’ or ‘‘address’’ shall be provided. | | | | | - -##### 3.2.6.2.17 Type: OCloudSiteInfo - -This type represents information about O-Cloud site instance. It shall comply with the provisions defined in table 3.2.6.2.17-1. - -**Table 3.2.6.2.17-1 Definition of type OCloudSiteInfo** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------|---------------|---|-------------|-----------------------------------------------------------------------------------------------------| -| oCloudSiteId | Identifier | M | 1 | Identifier of the O-Cloud site. Locally unique within the scope of an O-Cloud instance. | -| globalLocationId | String | M | 1 | Identifier of location where the O-Cloud site is deployed at. | -| name | String | M | 1 | Human readable name of the O-Cloud site as identified by the cloud provider. | -| description | String | M | 1 | Human readable description of the O-Cloud site as provided by the cloud provider. | -| resourcePools | Identifier | M | 1.. N | List of resource pools that are part of the O-Cloud site. | -| extensions | KeyValuePairs | M | 0..1 | List of metadata key-value pairs used to associate meaningful metadata to the related O-Cloud site. | - -#### 3.2.6.3 Simple data types and enumerations - -##### 3.2.6.3.1 Introduction - -This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. The simple data types defined in a request body, response body, or a structured type are defined in ETSI GS NFV-SOL 013 [22] or this clause of the specification. - -##### 3.2.6.3.2 Simple data types - -The simple data types defined in table 3.2.6.3.2-1 shall be supported. - -**Table 3.2.6.3.2-1: Simple data types** - -| Type Name | Type Definition | Description | -|-----------|-----------------|-------------| -| n/a | | | - -### 3.2.7 Error handling - -#### 3.2.7.1 General - -For the O2ims\_InfrastructureInventory Service API, HTTP error responses shall be supported as specified in clause 3.1.5. - -In addition, the requirements in the following clauses are applicable for the O2ims\_InfrastructureInventory Service API. - -#### 3.2.7.2 Protocol errors - -No specific protocol errors for the O2ims\_InfrastructureInventory Service API are specified. - -#### 3.2.7.3 Application errors - -No specific application errors for the O2ims\_InfrastructureInventory Service API are specified - -### 3.2.8 Security - -No specific security procedures for the O2ims\_InfrastructureInventory Service API are specified beyond those in clause 3.1.7. - -## 3.3 O2ims\_InfrastructureMonitoring Service API - -### 3.3.1 Description - -This API allows the SMO to invoke O2ims\_InfrastructureMonitoring Services towards the O-Cloud. - -The operations defined for O2ims\_InfrastructureMonitoring Services through this API are: - -- Query information about one or multiple Alarms; -- Create a subscription to Alarms of interest; -- Notify consumer identified by an established subscription which is not filtered by the filter criteria of the occurrence of a change to the alarm objects; -- Acknowledge an Alarm; -- Clear an Alarm; -- Ability to query and modify the configurable values which govern the behaviour of the Alarm Service; and -- Purge Alarms - -Services for IMS Heartbeat are not specified in the present document version. - -### 3.3.2 API version - -For the O2ims\_InfrastructureMonitoring Service API version as specified in the present document, the MAJOR version field shall be 2, the MINOR version field shall be 0, and the PATCH version field shall be 0. - -Table 3.3.2-1 lists the history of API versions of the O2ims\_InfrastructureMonitoring Service and the main capabilities added/removed across versions. - -**Table 3.3.2-1: History of API versions of the O2ims\_InfrastructureMonitoring Service.** - -| Version | Description | -|---------|--------------------------------------------------------------------------------------------------------------------------------------------------------| -| 1.0.0 | Initial API Supporting:
Alarm Query
Alarm Subscription
Alarm Notification | -| 1.1.0 | New methods:
Acknowledge Alarm
Clear Alarm
Alarm Service Configure | -| 1.2.0 | Updated methods:
Alarm Subscription

New resources:
Purge Alarms Task
Task Operation List
Task Operation Occurrence | -| 2.0.0 | Updated Notification:
Alarm Change Notification

Updated Data Type:
AlarmSubscriptionInfo
AlarmEventRecord
Alarm Change Notification | - -### 3.3.3 REST resources structure and methods - -All resource URIs of the API shall use the base URI specification defined in clause 3.1.2. The string "O2ims\_infrastructureMonitoring" shall be used to represent {apiName}. All resource URIs in the clauses below are defined relative to the formed base URI (i.e., {apiRoot}/O2ims\_infrastructureMonitoring/{apiMajorVersion}). - -When ambiguity is possible, the term REST resource is used to make the distinction between the term resource as understood within the context of REST API from the term resource as understood within the context of O-RAN. - -Figure 3.3.3-1 shows the overall resource URI structure defined for the O2ims\_InfrastructureMonitoring Service API. - -![Resource URI structure of the O2ims_infrastructureMonitoring API](90183a52275501da5a0fd5c63d837009_img.jpg) - -``` -graph TD; Root["{apiRoot}/O2ims_infrastructureMonitoring/{apiMajorVersion}"] --- Alarms["/alarms"]; Root --- AlarmSubscriptions["/alarmSubscriptions"]; Root --- AlarmServiceConfiguration["/alarmServiceConfiguration"]; Root --- TaskOperations["/taskOperations"]; Alarms --- AlarmEventRecordId["/{alarmEventRecordId}"]; Alarms --- Purge["/purge"]; AlarmSubscriptions --- AlarmSubscriptionId["/{alarmSubscriptionId}"]; TaskOperations --- OperationOccurrenceId["/{operationOccurrenceId}"]; -``` - -The diagram illustrates the hierarchical structure of the O2ims\_infrastructureMonitoring API. The root path is {apiRoot}/O2ims\_infrastructureMonitoring/{apiMajorVersion}. It branches into four main resource paths: /alarms, /alarmSubscriptions, /alarmServiceConfiguration, and /taskOperations. The /alarms path further branches into /{alarmEventRecordId} and /purge. The /alarmSubscriptions path branches into /{alarmSubscriptionId}. The /taskOperations path branches into /{operationOccurrenceId}. The /purge path is shown with a dashed border. - -Resource URI structure of the O2ims\_infrastructureMonitoring API - -**Figure 3.3.3-1 Resource URI structure of the O2ims\_infrastructureMonitoring API** - -Table 3.3.3-1 provides an overview of the resources and applicable HTTP methods. - -The O-Cloud shall support responding to requests for all HTTP methods on the resources in table 3.3.3-1 that are marked as “M” (mandatory) in the “Cat” column. The O-Cloud shall also support the “API versions” resources as specified in clause 3.1.8. - -**Table 3.3.3-1 Resources and methods overview** - -| Resource name | Resource URI | HTTP method | Cat | Description | -|--------------------------------|-------------------------------------------|-------------|-----|----------------------------------------------------------------------------------------------| -| Alarm List | /alarms | GET | M | To get a list of alarms | -| Alarm Record | /alarms/{alarmEventRecordId} | GET | M | To get an individual alarm record | -| | | PATCH | M | To modify (acknowledge, clear) an individual alarm record | -| Purge Alarms Task | /alarms/purge | POST | M | To purge alarms from the list. | -| Alarm Subscription List | /alarmSubscriptions | POST | M | To create an individual alarm subscription | -| | | GET | M | To get a list of alarm subscriptions | -| Alarm Subscription Description | /alarmSubscriptions/{alarmSubscriptionId} | GET | M | To get an individual alarm subscription description | -| | | DELETE | M | To delete an individual alarm subscription | -| Alarm Service Configuration | /alarmServiceConfiguration | GET | M | To get the current configuration of the alarm service. | -| | | PUT | M | To set a whole new configuration of the alarm service. | -| | | PATCH | M | Partially update the configuration of the alarm service. | -| Task Operation List | /taskOperations | GET | M | To query information about multiple task operation occurrences related to alarm management. | -| Task Operation Occurrence | /taskOperations/{operationOccurrenceId} | GET | M | To query information about a specific task operation occurrence related to alarm management. | - -### 3.3.4 REST resources - -#### 3.3.4.1 Introduction - -There are no preconditions or postconditions for a successful execution of each of the O2ims\_InfrastructureMonitoring Service API triggered by a corresponding operation. - -#### 3.3.4.2 REST resource: Alarm List - -##### 3.3.4.2.1 Description - -This resource represents the list of alarms that the O-Cloud has seen during its alarm retention period. The Alarm List can contain Alarm Records. - -##### 3.3.4.2.2 Resource definition - -Resource URI: {apiRoot}/O2ims\_infrastructureMonitoring/{apiMajorVersion}/alarms - -This resource shall support the resource URI variables defined in Table 3.3.4.2.2 1. - -**Table 3.3.4.2.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | string | See clause 3.1.2 | -| apiMajorVersion | string | See clause 3.1.2 | - -##### **3.3.4.2.3 Resource methods** - -###### **3.3.4.2.3.1 POST** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.3.4.2.3.2 GET** - -The GET operation is used to retrieve the list of alarms. - -This method shall support the URI query parameters specified in Table 3.3.4.2.3.2 1. - -**Table 3.3.4.2.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| filter | 0..1 | Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [22] .
The O-Cloud shall support receiving this parameter as part of the URI query string. The API consumer may supply this parameter.
All attribute names that appear in the AlarmEventRecord and in data types referenced from it shall be supported by the O-Cloud in the filter expression. | -| all_fields | 0..1 | Include all complex attributes in the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter. | -| fields | 0..1 | Complex attributes to be included into the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_fields | 0..1 | Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_default | 0..1 | Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.
The following attributes shall be excluded from the list of AlarmEventRecord in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided:
- TBD | -| nextpage_opaque_marker | 0..1 | Marker to obtain the next page of a paged response. Shall be supported by the O-Cloud if the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource. | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.3.4.2.3.2-2. - -**Table 3.3.4.2.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|------------------|------------------|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | AlarmEventRecord | 0..N | 200 OK |

Shall be returned when information about zero or more AlarmEventRecord instances has been queried successfully.

The response body shall contain in an array the representations of zero or more AlarmEventRecord instances, as defined in clause 3.3.6.2.2.

If the "filter" URI parameter or one of the "all_fields", "fields" (if supported), "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request, the data in the response body shall have been transformed according to the rules specified in clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [22], respectively.

If the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, inclusion of the Link HTTP header in this response shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013 [22].

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute-based filtering expression.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute selector.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Response too big.

If the O-Cloud supports alternative 1 (error) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, this error response shall follow the provisions in clause 5.4.2.2 of ETSI GS NFV-SOL 013 [22].

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx |

In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned.

| - -###### **3.3.4.2.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.3.4.2.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.3.4.2.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### 3.3.4.3 REST resource: Alarm Record - -##### 3.3.4.3.1 Description - -This resource represents the details of an Alarm Record in the Alarm List. The Alarm Record is a record of the details of an Alarm since its creation. - -##### 3.3.4.3.2 Resource definition - -Resource URI: {apiRoot}/O2ims\_infrastructureMonitoring/{apiMajorVersion}/alarms/{alarmEventRecordId} - -This resource shall support the resource URI variables defined in Table 3.3.4.3.2 1. - -**Table 3.3.4.3.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|--------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| alarmEventRecordId | Identifier | The identifier of the Alarm Record resource. See note. | -| NOTE: This identifier can be retrieved from the alarmEventRecordId attribute in the payload body of the response to a GET request getting the list of "Alarm Record" resources. | | | - -##### 3.3.4.3.3 Resource methods - -###### 3.3.4.3.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.3.4.3.3.2 GET - -The GET operation is used to retrieve the details of a single Alarm Event Record. - -This method shall support the URI query parameters specified in Table 3.3.4.3.3.2 1. - -**Table 3.3.4.3.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.3.4.3.3.2-2. - -**Table 3.3.4.3.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|------------------|------------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | AlarmEventRecord | 1 | 200 OK | Shall be returned when information about a AlarmEventRecord instance has been queried successfully.
The response body shall contain a representation of the AlarmEventRecord instance, as defined in clause 3.3.6.2.2. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.3.4.3.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.3.4.3.3.4 PATCH** - -The PATCH method is used to modify an individual alarm record. Supported modifications of an individual alarm record include: - -- Acknowledging an alarm, and -- Clearing an alarm. - -A PATCH request shall only target a single type of modification from the list above. Upon processing the request, the IMS shall update the requested attributes from the "AlarmEventRecord" (see clause 3.3.6.2.2) representing the individual alarm record, as well as other related attributes concerning the requested modifications. For instance, if the alarm record is requested to be acknowledged, the "alarmAcknowledgeTime" attribute in the "AlarmEventRecord" is expected to be also updated accordingly. - -This method shall support the URI query parameters specified in Table 3.3.4.3.3.4-1. - -**Table 3.3.4.3.3.4-1 URI query parameters supported by the PATCH method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.3.4.3.3.4-2. - -Table 3.3.4.3.3.4-2: Details of the PATCH request/response on this resource - -| Request body | Data type | Cardinality | Description | | | -|---------------|-------------------------------|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------| -| | AlarmEventRecordModifications | 1 | The parameter for the alarm record modification, as defined in clause 3.3.6.2.4.

The Content-Type header shall be set to "application/merge-patch+json" according to IETF RFC 7396 [29]. | | | -| Response body | Data type | | Cardinality | Response Codes | Description | -| | AlarmEventRecordModifications | 1 | 200 OK | Shall be returned when the request has been accepted and completed.

The response body shall contain attribute modifications for an individual alarm record resource (see clause 3.3.6.2.4). | | -| | ProblemDetails | 1 | 409 Conflict | Shall be returned upon the following error: The operation cannot be executed currently, due to a conflict with the state of the individual alarm record resource.

Typically, this is due to the fact that the alarm is already in the state that is requested to be set (such as trying to acknowledge an already-acknowledged alarm, or clearing an already-cleared alarm).

The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error. | | -| | ProblemDetails | 0..1 | 412 Precondition failed | Shall be returned upon the following error: A precondition given in an HTTP request header is not fulfilled.

Typically, this is due to an ETag mismatch, indicating that the resource was modified by another entity.

The response body should contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error. | | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | | - -###### 3.3.4.3.3.5 DELETE - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### 3.3.4.4 REST resource: Alarm Subscription List - -##### 3.3.4.4.1 Description - -This resource represents the set of Alarm Subscriptions in the O-Cloud the SMO can use for being notified when certain changes in the Alarm List occur. The Alarm Subscription List can contain Alarm Subscription Descriptions. - -##### 3.3.4.4.2 Resource definition - -Resource URI: {apiRoot}/O2ims\_infrastructureMonitoring/{apiMajorVersion}/alarmSubscriptions - -This resource shall support the resource URI variables defined in Table 3.3.4.2-1. - -**Table 3.3.4.4.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | - -##### **3.3.4.4.3 Resource methods** - -###### **3.3.4.4.3.1 POST** - -The POST operation is used to create an alarm subscription. - -This method shall support the URI query parameters specified in Table 3.3.4.4.3.1-1. - -**Table 3.3.4.4.3.1-1 URI query parameters supported by the POST method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.3.4.4.3.1-2. - -**Table 3.3.4.4.3.1-2: Details of the POST request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|-----------------------|------------------|-----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | AlarmSubscriptionInfo | 1 | The AlarmSubscriptionInfo instance to be created. Note: The supplied SubscriptionId is ignored and assigned by the O-Cloud. | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | AlarmSubscriptionInfo | 1 | 201
Created | Shall be returned when information about a AlarmSubscriptionInfo instance has been created successfully.
The response body shall contain a representation of the AlarmSubscriptionInfo instance, as defined in clause 3.3.6.2.3. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.3.4.4.3.2 GET** - -The GET operation is used to retrieve the list of alarm subscriptions. - -This method shall support the URI query parameters specified in Table 3.3.4.4.3.2-1. - -**Table 3.3.4.4.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|----------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| filter | 0..1 | Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [22].
The O-Cloud shall support receiving this parameter as part of the URI query string. The API consumer may supply this parameter.
All attribute names that appear in the AlarmSubscriptionInfo and in data types referenced from it shall be supported by the O-Cloud in the filter expression. | -| all_fields | 0..1 | Include all complex attributes in the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter. | -| fields | 0..1 | Complex attributes to be included into the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_fields | 0..1 | Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_default | 0..1 | Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.
The following attributes shall be excluded from the list of AlarmSubscriptionInfo in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided:
- TBD | -| nextpage_opaque
_marker | 0..1 | Marker to obtain the next page of a paged response. Shall be supported by the O-Cloud if the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource. | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.3.4.4.3.2-2. - -**Table 3.3.4.4.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|-----------------------|------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | AlarmSubscriptionInfo | 0..N | 200 OK |

Shall be returned when information about zero or more AlarmSubscriptionInfo instances has been queried successfully.

The response body shall contain in an array the representations of zero or more AlarmSubscriptionInfo instances, as defined in clause 3.3.6.2.3.

If the "filter" URI parameter or one of the "all_fields", "fields" (if supported), "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request, the data in the response body shall have been transformed according to the rules specified in clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [22], respectively.

If the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, inclusion of the Link HTTP header in this response shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013 [22].

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute-based filtering expression.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute selector.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Response too big.

If the O-Cloud supports alternative 1 (error) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, this error response shall follow the provisions in clause 5.4.2.2 of ETSI GS NFV-SOL 013 [22].

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx |

In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned.

| - -###### **3.3.4.4.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.3.4.4.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.3.4.4.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### 3.3.4.5 REST resource: Alarm Subscription Description - -##### 3.3.4.5.1 Description - -The Alarm Subscription Description represents the description of a subscription to alarm change events in the O-Cloud. - -##### 3.3.4.5.2 Resource definition - -Resource URI: - -**{apiRoot}/O2ims\_infrastructureMonitoring/{apiMajorVersion}/alarmSubscriptions/{alarmSubscriptionId}** - -This resource shall support the resource URI variables defined in Table 3.3.4.5.2-1. - -**Table 3.3.4.5.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|---------------------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| alarmSubscriptionId | Identifier | The identifier of the Alarm Subscription Description resource. This identifier can be retrieved from the alarmSubscriptionId attribute in the payload body of the response to a GET request getting the list of "AlarmSubscriptionInfo" resources. | - -##### 3.3.4.5.3 Resource methods - -###### 3.3.4.5.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.3.4.5.3.2 GET - -The GET operation is used to retrieve the alarm subscription description of a single alarm subscription. - -This method shall support the URI query parameters specified in Table 3.3.4.5.3.2-1. - -**Table 3.3.4.5.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.3.4.5.3.2-2. - -**Table 3.3.4.5.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|-----------------------|------------------|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | AlarmSubscriptionInfo | 1 | 200 OK | Shall be returned when information about a AlarmSubscriptionInfo instance has been queried successfully.
The response body shall contain a representation of the AlarmSubscriptionInfo instance, as defined in clause 3.3.6.2.3. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.3.4.5.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.3.4.5.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.3.4.5.3.5 DELETE** - -The DELETE operation is used to delete the alarm subscription description of a single alarm subscription. - -This method shall support the URI query parameters specified in Table 3.3.4.5.3.5-1. - -**Table 3.3.4.5.3.5-1 URI query parameters supported by the DELETE method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.3.4.5.3.5-2. - -**Table 3.3.4.5.3.5-2: Details of the DELETE request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|----------------|------------------|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | n/a | 1 | 204 (no content) | Shall be returned when the individual instance of Alarm Subscription has been deleted successfully. The response body shall be empty. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -#### **3.3.4.6 REST resource: Alarm Service Configuration** - -##### **3.3.4.6.1 Description** - -The Alarm Service Configuration represents the ability to get and set the configurable values which govern the behaviour of the alarm service. - -##### 3.3.4.6.2 Resource definition - -Resource URI: {apiRoot}/O2ims\_infrastructureMonitoring/{apiMajorVersion}/alarmServiceConfiguration - -This resource shall support the resource URI variables defined in Table 3.3.4.6.2-1. - -**Table 3.3.4.6.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | - -##### 3.3.4.6.3 Resource methods - -###### 3.3.4.6.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### 3.3.4.6.3.2 GET - -The GET operation is used to retrieve the current alarm service configuration. - -This method shall support the URI query parameters specified in Table 3.3.4.6.3.2-1. - -**Table 3.3.4.6.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.3.4.6.3.2-2. - -**Table 3.3.4.6.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|---------------------------|------------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | AlarmServiceConfiguration | 1 | 200 OK | Shall be returned when information about an AlarmServiceConfiguration instance has been queried successfully.
The response body shall contain a representation of the AlarmServiceConfiguration instance, as defined in clause 3.3.6.2.5. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in ETSI GS NFV-SOL 013 [22], clause 6.4 may be returned. | - -###### 3.3.4.6.3.3 PUT - -The PUT method is used to update all fields of the Alarm Service Configuration. It operates as a “replace” or “overwrite” semantic model. - -A 200 OK response with the updated copy of the final object content after the update has been performed is the acceptable response for objects with minimal complexity. - -This method shall support the URI query parameters specified in Table 3.3.4.6.3.3-1. - -**Table 3.3.4.6.3.3-1 URI query parameters supported by the PUT method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.3.4.6.3.3-2. - -**Table 3.3.4.6.3.3-2: Details of the PUT request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|---------------------------|------------------|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | Response Codes | Description | | | -| | AlarmServiceConfiguration | 1 | The parameter for the Alarm Service Configuration, as defined in clause 3.3.6.2.5. | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | Response Codes | Description | | | -| | AlarmServiceConfiguration | 1 | 200 OK | Shall be returned when the request has been accepted and completed.

The response body shall contain attribute modifications for the alarm service configuration (see clause 3.3.6.2.5). | -| | ProblemDetails | 0..1 | 412 Precondition failed | Shall be returned upon the following error: A precondition given in an HTTP request header is not fulfilled.

Typically, this is due to an ETag mismatch, indicating that the resource was modified by another entity prior to this request.

The response body should contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in ETSI GS NFV-SOL 013 [22], clause 6.4 may be returned. | - -###### **3.3.4.6.3.4 PATCH** - -The PATCH method is used to modify individual fields of the Alarm Service Configuration. - -A PATCH request shall enable only those fields of the alarm service configuration that are contained in the request to be modified. Attributes not contained in the request will remain unmodified. This is sometimes referred to as a partial update. - -This method shall support the URI query parameters specified in Table 3.3.4.6.3.4-1. - -**Table 3.3.4.6.3.4-1 URI query parameters supported by the PATCH method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.3.4.6.3.4-2. - -**Table 3.3.4.6.3.4-2: Details of the PATCH request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|---------------------------|------------------|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | AlarmServiceConfiguration | | 1 | | -| Response body | Data type | | Cardinality | Response Codes | -| | AlarmServiceConfiguration | 1 | 200 OK |

Shall be returned when the request has been accepted and completed.

The response body shall contain attribute modifications for the alarm service configuration (see clause 3.3.6.2.5).

| -| | ProblemDetails | 0..1 | 412 Precondition failed |

Shall be returned upon the following error: A precondition given in an HTTP request header is not fulfilled.

Typically, this is due to an ETag mismatch, indicating that the resource was modified by another entity.

The response body should contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in ETSI GS NFV-SOL 013 [22], clause 6.4 may be returned. | - -###### **3.3.4.6.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in ETSI GS NFV-SOL 013 [22], clause 6.4. - -#### **3.3.4.7 REST resource: Purge Alarms task** - -##### **3.3.4.7.1 Description** - -This task resource represents the "Purge Alarms" operation. The API consumer can use this resource to request purging one or multiple Alarms Event Records in the Alarms List. - -##### **3.3.4.7.2 Resource definition** - -The resource URI is: - -**{apiRoot}/O2ims\_infrastructureMonitoring/{apiMajorVersion}/alarms/purge** - -This resource shall support the resource URI variables defined in table 3.3.4.7.2-1. - -**Table 3.3.4.7.2-1: Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | string | See clause 3.1.2 | -| apiMajorVersion | string | See clause 3.3.2 | - -##### 3.3.4.7.3 Resource Methods - -###### 3.3.4.7.3.1 POST - -The POST operation is used to purge Alarm Event Record(s) contained in the alarm list. The request body input parameters can identify the specific Alarm Event Record(s) to be purged. For additional information about the purge service operation, refer to the service model in clause 2.1.3.1.2.5. - -This method shall follow the provisions specified in table 3.3.4.7.3.1-1 for URI query parameters. - -**Table 3.3.4.7.3.1-1 URI query parameters supported by the POST method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in table 3.3.4.7.3.1-2. - -**Table 3.3.4.7.3.1-2: Details of the POST request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|----------------|------------------|-------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | PurgeRequest | 1 | This identifies the specific AlarmEventRecord(s) to be purged based on attributes of the AlarmEventRecord | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | n/a | | 202 Accepted | Shall be returned when the request has been accepted for processing. The response body shall be empty. The HTTP response shall include a "Location" HTTP header that contains the URI of the newly created "Task Operation Occurrence" resource corresponding to the purge operation. | -| | ProblemDetails | 1 | 409 Conflict |

Shall be returned upon the following error: The operation cannot be executed currently, due to a conflict with the state of the resource.

Typically, this is due to the fact that another task operation is ongoing on the affected resources.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute shall convey more information about the error.

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### 3.3.4.7.3.2 GET - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.3.4.7.3.3 PUT - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.3.4.7.3.4 PATCH - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.3.4.7.3.5 DELETE - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### 3.3.4.8 REST resource: Task Operation List - -##### 3.3.4.8.1 Description - -This resource represents the list of task operation occurrences triggered through the respective API. The API consumer can use this resource to query status information about multiple task operation occurrences. - -##### 3.3.4.8.2 Resource definition - -The resource URI is: - -**{apiRoot}/O2ims\_infrastructureMonitoring/{apiMajorVersion}/taskOperations** - -This resource shall support the resource URI variables defined in table 3.3.4.8.2-1. - -**Table 3.3.4.8.2-1: Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | string | See clause 3.1.2 | -| apiMajorVersion | string | See clause 3.1.2 | - -##### 3.3.4.8.3 Resource methods - -###### 3.3.4.8.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.3.4.8.3.2 GET - -The API consumer can use this method to query status information about multiple task operation occurrences. - -This method shall follow the provisions specified in Table 3.3.4.8.3.2-1 for URI query parameters. - -**Table 3.3.4.8.3.2-2 URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------------------------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| filter | 0..1 | Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [22].
The O-Cloud shall support receiving this parameter as part of the URI query string. The API consumer may supply this parameter.
All attribute names that appear in the TaskOperationInfo and in data types referenced from it shall be supported by the O-Cloud in the filter expression. | -| all_fields | 0..1 | Include all complex attributes in the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter. | -| fields | 0..1 | Complex attributes to be included into the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_fields | 0..1 | Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_default | 0..1 | Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.
The following attributes shall be excluded from the list of XYZ in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided.
- TBD | -| nextpage_opaque_marker | 0..1 | Marker to obtain the next page of a paged response. Shall be supported by the O-Cloud if the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource. | - -This method shall support the request data structures, the response data structures, and response codes specified in table 3.3.4.8.3.2-2. - -Table 3.3.4.8.3.2-2: Details of the GET request/response on this resource - -| Request body | Data type | Cardinality | Description | | -|---------------|-------------------|------------------|-----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | TaskOperationInfo | 0..N | 200 OK |

Shall be returned when information about zero or more task operation occurrences has been queried successfully.

The response body shall contain in an array the representations of zero or more TaskOperationInfo instances, as defined in clause 3.3.6.2.7.

If the "filter" URI parameter or one of the "all_fields", "fields" (if supported), "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request, the data in the response body shall have been transformed according to the rules specified in clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [22], respectively.

If the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, inclusion of the Link HTTP header in this response shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013 [22].

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute-based filtering expression.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute selector.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Response too big.

If the O-Cloud supports alternative 1 (error) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, this error response shall follow the provisions in clause 5.4.2.2 of ETSI GS NFV-SOL 013 [22].

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx |

In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned.

| - -###### 3.3.4.8.3.3 PUT - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.3.4.8.3.4 PATCH - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.3.4.8.3.5 DELETE - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### 3.3.4.9 REST resource: Task Operation Occurrence - -##### 3.3.4.9.1 Description - -This resource represents a task operation resource. The API can use this resource to read status information about an individual task operation occurrence. - -The O-Cloud may remove an individual task operation occurrence resource some time after it has reached one of the terminal states (i.e., the "operationState" attribute of its representation is equal to one of the values "COMPLETED", "FAILED" or "ROLLED\_BACK"). The minimum time how long the O-Cloud waits before deleting such a resource is not defined by the present document version. - -##### 3.3.4.9.2 Resource definition - -The resource URI is: - -`{apiRoot}/O2ims_infrastructureMonitoring/{apiMajorVersion}/taskOperations/{operationOccurrenceId}` - -This resource shall support the resource URI variables defined in Table 3.3.4.9.2-1. - -**Table 3.3.4.9.2-1: Resource URI variables for this resource** - -| Name | Data type | Definition | -|------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|------------------------------------------------------| -| apiRoot | string | See clause 3.1.2 | -| apiMajorVersion | string | See clause 3.3.2 | -| operationOccurrenceId | Identifier | Identifier of a task operation occurrence. See note. | -| NOTE: This identifier can be retrieved from the resource referenced by the "Location HTTP" header in the response to a POST request triggering a task operation. | | | - -##### 3.3.4.9.3 Resource methods - -###### 3.3.4.9.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.3.4.9.3.2 GET - -The API consumer can use this method to retrieve status information about a task operation occurrence by reading a "Task Operation Occurrence" resource. - -This method shall follow the provisions specified in table 3.3.4.9.3.2-1 for URI query parameters. - -**Table 3.3.4.9.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|----------------|-------------|-------------| -| none supported | | | - -This method shall support the request data structures, the response data structures, and response codes specified in table 3.3.4.9.3.2-2. - -**Table 3.3.4.9.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|-------------------|------------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | TaskOperationInfo | 1 | 200 OK | Shall be returned when information about an individual task operation occurrence has been read successfully.

The response body shall contain status information about a task operation occurrence (see clause 3.3.6.2.7). | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.3.4.9.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.3.4.9.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.3.4.9.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -### 3.3.5 Notifications - -#### 3.3.5.1 General - -Notifications shall comply to the Subscribe/Notify pattern described in clause 5.9 of ETSI GS NFV-SOL 015 [25]. - -**Table 3.3.5.1-1 Notifications overview** - -| Notification | Callback URI | HTTP method | Description | -|---------------------------|-----------------------------|-------------|-----------------------------------------------------------------------| -| Alarm Change Notification | Alarm Subscription.callback | POST | Notify subscribers when objects in the O2ims Alarm List have changed. | - -##### 3.3.5.1.1 Alarm Change Notification Description - -The Alarm Change Notification is used by the O-Cloud Infrastructure Monitoring Service to report changes to the O2ims alarm List to an O2ims consumer that has subscribed to such notifications. - -##### 3.3.5.1.2 Target URI - -The Alarm Subscription.Callback URI "{AlarmEventNotification}" shall be used with the callback URI variables define in table 3.3.5.1.2-1. - -**Table 3.3.5.1.2-1 Definition of Alarm Change Notification type** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------------|------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| globalCloudId | Identifier | M | 1 | The global cloud identifier assigned by the SMO. | -| consumerSubscriptionId | String | M | 0..1 | The value optionally provided by the consumer in the subscription. | -| notificationEventType | Integer | M | 1 | One of the following values:
  • 0 for "NEW"
  • 1 for "CHANGE"
  • 2 for "CLEAR"
  • 3 for "ACKNOWLEDGE"
| -| objectRef | String | M | 0..1 | The URL to the AlarmEventRecord object. | -| alarmEventRecordId | Identifier | M | 1 | The identifier for the AlarmEventRecord Object. | -| objectTypeId | Identifier | M | 1 | A reference to the type of object which caused the alarm. | -| objectId | Identifier | M | 1 | A reference to the object instance which caused the alarm. | -| objectClass | String | M | 1 | The fully qualified name of the class of the object being referenced by the objectId attribute (e.g., "oran.o2ims.cluster.ClusterResource"). | -| alarmDefinitionId | Identifier | M | 1 | A reference to the Alarm Definition record in the Alarm Dictionary associated with the referenced Object Type. | -| probableCauseId | Identifier | M | 1 | A reference to the ProbableCause of the Alarm. | -| alarmRaisedTime | DateTime | M | 1 | Date/Time stamp value when the AlarmEventRecord has been created. | -| alarmChangedTime | DateTime | M | 1 | Date/Time stamp value when any value of the AlarmEventRecord has been modified. | -| alarmAcknowledgeTime | DateTime | M | 1 | Date/Time stamp value when the alarm condition is acknowledged. | -| alarmAcknowledged | Boolean | M | 1 | Boolean value indicating of a management system has acknowledged the alarm. | -| perceivedSeverity | integer | M | 1 | One of the following values:
  • 0 for "CRITICAL"
  • 1 for "MAJOR"
  • 2 for "MINOR"
  • 3 for "WARNING"
  • 4 for "INDETERMINATE"
  • 5 for "CLEARED"
| -| extensions | KeyValue | M | 0..N | Unspecified (not standardized) properties (keys) which are tailored by the vendor or operator to extend the information provided about the O-Cloud Alarm. | - -### 3.3.6 Data model - -#### 3.3.6.1 REST resource data types - -This clause specifies the data types to be used in resource representations and notifications supported by the present API. - -Table 3.3.6.1-1 specifies the data types defined for the O2ims\_InfrastructureMonitoring service API. - -**Table 3.3.6.1-1: O2ims\_InfrastructureMonitoring resource data types** - -| Data type | Clause defined | Description | Applicability | -|---------------------------|-----------------------|-------------------------------------------------------------------------------------------|----------------------| -| AlarmEventRecord | 3.2.6.2.2 | This data type represents an instance of an Alarm detected by the O-Cloud Infrastructure. | | -| AlarmSubscriptionInfo | 3.2.6.2.3 | This data type represents an instance of a subscription to O2ims Alarm change events. | | -| AlarmServiceConfiguration | 3.3.6.2.5 | This type represents information about the Alarm Service Configuration. | | -| TaskOperationInfo | 3.3.6.2.7 | This type represents a task operation occurrence. | | - -#### 3.3.6.2 Structured data types - -##### 3.3.6.2.1 Introduction - -This clause defines the data structures to be used in resource representations. - -##### 3.3.6.2.2 Type: AlarmEventRecord - -This type represents information about an Alarm in the O-Cloud Infrastructure. It shall comply with the provisions defined in table 3.3.6.2.2-1. - -**Table 3.3.6.2.2-1 Definition of type AlarmEventRecord** - -| Attribute name | Data type | P | Cardinality | Description | -|----------------------|------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| alarmEventRecordId | Identifier | M | 1 | The identifier for the AlarmEventRecord Object. | -| objectTypeId | Identifier | M | 1 | A reference to the type of resource which caused the alarm. | -| objectId | Identifier | M | 1 | A reference to the resource instance which caused the alarm. | -| objectClass | String | M | 1 | The fully qualified name of the object being referenced by the objectId attribute (e.g., "oran.o2ims.cluster.ClusterResource"). | -| alarmDefinitionId | Identifier | M | 1 | A reference to the Alarm Definition record in the Alarm Dictionary associated with the referenced Object Type. | -| probableCauseId | Identifier | M | 1 | A reference to the ProbableCause of the Alarm. | -| alarmRaisedTime | DateTime | M | 1 | Date/Time stamp value when the AlarmEventRecord has been created. | -| alarmChangedTime | DateTime | M | 0..1 | Date/Time stamp value when any value of the AlarmEventRecord has been modified. It shall be present if the alarm record has been modified. | -| alarmAcknowledgeTime | DateTime | M | 0..1 | Date/Time stamp value when the alarm condition is acknowledged. It shall be present if the alarm record has been acknowledged. | -| alarmAcknowledged | Boolean | M | 1 | Boolean value indicating if a management system has acknowledged the alarm. "True" if the alarm has been acknowledged, and "False" otherwise. | -| alarmClearedTime | DateTime | M | 0..1 | Date/Time stamp value indicating when the alarm was cleared. It shall be present if the alarm record has been cleared. | -| perceivedSeverity | integer | M | 1 | One of the following values:
  • 0 for "CRITICAL"
  • 1 for "MAJOR"
  • 2 for "MINOR"
  • 3 for "WARNING"
  • 4 for "INDETERMINATE"
  • 5 for "CLEARED"
| -| extensions | KeyValue | M | 0..N | Unspecified (not standardized) properties (keys) which are tailored by the vendor or operator to extend the information provided about the O-Cloud Alarm. | - -##### 3.3.6.2.3 Type: AlarmSubscriptionInfo - -This type represents information about a Subscription for Alarms in the O-Cloud. It shall comply with the provisions defined in table 3.3.6.2.3-1. - -**Table 3.3.6.2.3-1 Definition of type AlarmSubscriptionInfo** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------------|------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| alarmSubscriptionId | Identifier | M | 1 | Identifier for the Alarm Subscription. This identifier is allocated by the O-Cloud. | -| consumerSubscriptionId | String | O | 0..1 | Identifier for the consumer of events sent due to the Subscription. | -| filter | String | O | 0..1 | Criteria for events which do not need to be reported or will be filtered by the subscription notification service. Therefore, if a filter is not provided then all events are reported. | -| callback | Uri | M | 1 | The fully qualified URI to a consumer procedure which can process a Post of the AlarmEventNotification. | - -##### 3.3.6.2.4 Type: AlarmEventRecordModifications - -This type represents modifications for an individual alarm record, i.e., modification to a resource representation based on the "AlarmEventRecord" data type. The attributes of "AlarmEventRecord" that can be modified according to the provision in clause 3.3.6.2.2 are included in the "AlarmEventRecordModifications" data type. - -The "AlarmEventRecordModifications" data type shall comply with the provisions defined in table 3.3.6.2.4-1. - -**Table 3.3.6.2.4-1: Definition of type AlarmEventRecordModifications** - -| Attribute name | Data type | P | Cardinality | Description | -|-------------------|-----------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| alarmAcknowledged | Boolean | M | 0..1 | New value of the "alarmAcknowledged" attribute in "AlarmEventRecord". See note. | -| perceivedSeverity | Integer | M | 0..1 | New value for the "perceivedSeverity" attribute in "AlarmEventRecord" to indicate that the alarm record is requested to be cleared. Only the value "5" for "CLEARED" is permitted in a request message content. See note. | - -NOTE: Either "alarmAcknowledged" or "perceivedSeverity" shall be included in a request message content, but not both. - -##### 3.3.6.2.5 Type: AlarmServiceConfiguration - -This type represents request information about the Alarm Service Configuration which includes attributes to control the retention of Alarms in the O-Cloud Alarm List. It shall comply with the provisions defined in table 3.3.6.2.5-1. - -**Table 3.3.6.2.5-1 Definition of type AlarmServiceConfiguration** - -| Attribute name | Data type | P | Cardinality | Description | -|-----------------|-----------|---|-------------|------------------------------------------------------------------------------------------------------| -| retentionPeriod | Integer | M | 1 | Number of days for alarm history to be retained.
See Note. | -| extensions | KeyValues | M | 0..N | List of metadata key-value pairs used to associate meaningful metadata to the related alarm service. | - -NOTE: this value has a minimum limit such that it can't be set to a value lower than the limit. - -##### 3.3.6.2.6 Type: PurgeRequest - -This data type is used in the Alarm Purge operation. The PurgeRequest data type is used to specify the Alarm Record IDs and a time window for alarms to be purged through the API. It shall comply with the provisions defined in table 3.3.6.2.6-1. See clause 3.3.4.7.3 for more details on the Alarm Purge Operation. - -**Table 3.3.6.2.6-1: Definition of type PurgeRequest** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------|--------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| alarmRecordId | String | M | 0..N | A list of AlarmRecord ID (strings) if provided would be the alarm records that are to be purged. See note. | -| purgeConditions | Structure (inline) | M | 0..1 | Provides a time window (begin time, end time) for inactive and acknowledged alarms to be purged within. See note. | -| >startWindowTime | DateTime | M | 0..1 | Start time of the timing window of Alarms to be purged. Time refers to the "alarmClearedTime" in the AlarmEventRecord. If attribute is not provided, all cleared alarms older than the "endWindowTime" are considered for the purge request. | -| >endWindowTime | DateTime | M | 1 | End time of the timing windows of Alarms to be purged. Time refers to the "alarmClearedTime" in the AlarmEventRecord. If only this attribute is provided in the purgeConditions, all cleared alarms older than this time are considered for the purge request. | - -NOTE: At least either alarmRecordId or purgeCondition shall be provided in a request. If more than one attribute is provided, the API producer shall determine the intersection between the affected alarm event records and the purge conditions. For instance, if a list of alarm records is provided, as well as additional purge conditions, then those purge conditions are only to be applied to the list of alarm records provided. - -##### 3.3.6.2.7 Type: TaskOperationInfo - -This type represents a task operation occurrence. It shall comply with the provisions defined in table 3.2.6.2.7-1. - -**Table 3.3.6.2.7-1 Definition of type TaskOperationInfo** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------|----------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Id | Identifier | M | 1 | Identifier of this task operation occurrence. | -| operationState | Enum (inlined) | M | 1 | The state of the alarm management operation.

Permitted values:
- PROCESSING: the operation is currently in execution.
- COMPLETED: the operation has completed successfully.
- FAILED: the operation has failed.
- ROLLED_BACK: the operation has rolled back. | -| stateEnteredTime | DateTime | M | 1 | Date-time when the current state has been entered. | -| startTime | DateTime | M | 1 | Date-time of the start of the operation. | -| operation | Enum (inlined) | M | 1 | Type of the operation represented by this task operation occurrence.

Permitted values:
- PURGE: represents the "purge alarms" alarm management operation. | -| operationParams | Object | M | 0..1 | Input parameters of the triggered operation. This attribute shall be formatted according to the request data type of the related alarms management operation.

The following mapping between operation attribute and the data type of this attribute shall apply:
- PURGE: PurgeRequest

This attribute shall be present if this data type is returned in a response to reading an individual resource and may be present according to the chosen attribute selector parameter if this data type is returned in a response to a query of a container resource. | -| error | ProblemDetails | M | 0..1 | If "operationState" is "FAILED", this attribute shall be present and contain error information, unless it has been requested to be excluded via an attribute selector. | - -#### 3.3.6.3 Simple data types and enumerations - -##### 3.3.6.3.1 Introduction - -This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. The simple data types defined in a request body, response body, or a structured type are defined in ETSI GS NFV-SOL 013 [22] or this clause of the specification. - -##### 3.3.6.3.2 Simple data types - -The simple data types defined in table 3.3.6.3.2-1 shall be supported. - -**Table 3.3.6.3.2-1: Simple data types** - -| Type Name | Type Definition | Description | -|-----------|-----------------|-------------| -| n/a | | | - -### 3.3.7 Error handling - -#### 3.3.7.1 General - -For the O2ims\_InfrastructureMonitoring Service API, HTTP error responses shall be supported as specified in clause 3.1.5. - -In addition, the requirements in the following clauses are applicable for the O2ims\_InfrastructureMonitoring Service API. - -#### 3.3.7.2 Protocol errors - -No specific protocol errors for the O2ims\_InfrastructureMonitoring Service API are specified. - -#### 3.3.7.3 Application errors - -No specific application errors for the O2ims\_InfrastructureMonitoring Service API are specified - -### 3.3.8 Security - -No specific security procedures for the O2ims\_InfrastructureMonitoring Service API are specified beyond those in clause 3.1.7. - -## 3.4 O2ims\_InfrastructureProvisioning Service API - -### 3.4.1 Description - -This API enables the SMO to invoke O2ims\_InfrastructureProvisioning Service towards the O-Cloud. - -The operations defined for O2ims\_InfrastructureProvisioning Service through this API are- create, read, update, or delete. Elements provisioned through a ProvisioningRequest include but are not limited to the following: - -- O-Cloud NodeCluster -- O-Cloud InfrastructureResource(s) - -### 3.4.2 API Version - -For the O2ims\_InfrastructureProvisioning Service API version as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 2, and the PATCH version field shall be 0. - -Table 3.4.2-1 lists the history of API versions of the O2ims\_InfrastructureProvisioning Service and the main capabilities added/removed across versions. - -**Table 3.4.2-1: History of API versions of the O2ims\_InfrastructureProvisioning Service.** - -| Version | Description | -|---------|--------------------------------------------------------------------------------------------------------------------------| -| 1.0.0 | Initial API Supporting:
ProvisioningRequest List
ProvisioningRequest Description | -| 1.1.0 | Modified data types:
ProvisioningRequestInfo | -| 1.2.0 | Modified data types:
ProvisionedResourceSet
ProvisioningStatus

New data type:
ResourceProvisioningStatus | - -### 3.4.3 REST resources structure and methods - -All resource URIs of the API shall use the base URI specification defined in clause 3.1.2. The string "O2ims\_infrastructureProvisioning" shall be used to represent {apiName}. All resource URIs in the clauses below are defined relative to the formed base URI (i.e., {apiRoot}/O2ims\_infrastructureProvisioning/{apiVersion}). - -When ambiguity is possible, the term REST resource is used to make the distinction between the term resource as understood within the context of REST API from the term resource as understood within the context of O-RAN. - -Figure 3.4.3-1 shows the overall resource URI structure defined for the O2ims\_infrastructureProvisioning API. - -![A hierarchical diagram showing the URI structure. At the top is a rounded rectangle containing '{apiRoot}/O2ims_infrastructureProvisioning/{apiMajorVersion}'. A line descends from this box to a label '/provisioningRequests'. From this label, another line descends to a second rounded rectangle containing '/{provisioningRequestId}'.](4b2dd266b605b2f31a8759f802637301_img.jpg) - -A hierarchical diagram showing the URI structure. At the top is a rounded rectangle containing '{apiRoot}/O2ims\_infrastructureProvisioning/{apiMajorVersion}'. A line descends from this box to a label '/provisioningRequests'. From this label, another line descends to a second rounded rectangle containing '/{provisioningRequestId}'. - -**Figure 3.4.3-1 Resource URI structure of the O2ims\_infrastructureProvisioning API** - -Table 3.4.3-1 provides an overview of the resources and applicable HTTP methods. - -The O-Cloud shall support responding to requests for all HTTP methods on the resources in table 3.4.3-1 that are marked as "M" (mandatory) in the "Cat" column. The O-Cloud shall also support the "API versions" resources as specified in clause 3.1.8. - -**Table 3.4.3-1: Resources and methods overview** - -| Resource name | Resource URI | HTTP method | Cat | Description | -|---------------------------------|-----------------------------------------------|-------------|-----|-------------------------------------------------------------| -| ProvisioningRequest List | /provisioningRequests | GET | M | To get a list of ProvisioningRequests | -| | | POST | M | To create an individual ProvisioningRequest | -| ProvisioningRequest Description | /provisioningRequests/{provisioningRequestId} | GET | M | To get the description of an individual ProvisioningRequest | -| | | PUT | M | To replace/update an individual ProvisioningRequest | -| | | DELETE | M | To delete an individual ProvisioningRequest | - -### 3.4.4 REST resources - -#### 3.4.4.1 Introduction - -There are no preconditions or postconditions for a successful execution of each of the O2ims\_InfrastructureProvisioning Service API triggered by an operation. - -#### 3.4.4.2 REST resource: ProvisioningRequest List - -##### 3.4.4.2.1 Description - -This resource represents the list of ProvisioningRequests that the O-Cloud has created based on request from the SMO as declarative target to provision O-Cloud Node Cluster and/or O-Cloud Infrastructure Resource(s). The API consumer can use this resource to create a new ProvisioningRequest and to query the list of created ProvisioningRequests. - -##### 3.4.4.2.2 Resource definition - -Resource URI: {apiRoot}O2ims\_infrastructureProvisioning/{apiMajorVersion}/provisioningRequests - -This resource shall support the resource URI variables defined in Table 3.4.4.2.2-1. - -**Table 3.4.4.2.2-1: Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | - -##### **3.4.4.2.3 Resource methods** - -###### **3.4.4.2.3.1 POST** - -The POST operation is used to create an individual ProvisioningRequest. As a result of successfully executing this method, a new ProvisioningRequest instance resource as defined in clause 3.4.6.2.3 shall have been created, and the value of the "status" attribute in the representation of the ProvisioningRequest instance shall reflect the current phase in the provisioning request when the response is provided. - -**NOTE:** The present document version does not specify the protocol and data model mechanisms to address the handling of ProvisioningRequests in a "multi-tenancy" scenario. - -This method shall support the URI query parameters specified in Table 3.4.4.2.3.1-1. - -**Table 3.4.4.2.3.1-1: URI query parameters supported by the POST method on this resource** - -| Name | Cardinality | Description | -|------|-------------|-------------| -| n/a | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.4.4.2.3.1-2. - -**Table 3.4.4.2.3.1-2: Details of the POST request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|-------------------------|------------------|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | ProvisioningRequestData | 1 | | Parameters for the ProvisioningRequest instance to be created as defined in clause 3.4.6.2.2. | -| Response body | Data type | Cardinality | Response Codes | Description | -| | ProvisioningRequestInfo | 1 | 201
Created | Shall be returned when information about a ProvisioningRequest instance has been created successfully.
The response body shall contain a representation of the created ProvisioningRequestInfo instance, as defined in clause 3.4.6.2.3.
The HTTP response shall include a "Location" HTTP header that contains the resource URI of the newly-created ProvisioningRequest. | -| | ProblemDetails | 1 | 409
Conflict | Shall be returned upon the following error: the operation cannot be executed due to a conflict with the state of the resource.

Typically, this is due to the fact that the consumer has requested to create a ProvisioningRequest instance with same "provisioningRequestId" as an already existing other ProvisioningRequest instance.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.4.4.2.3.2 GET** - -The GET method is used to retrieve the list of ProvisioningRequests. - -This method shall support the URI query parameters specified in Table 3.4.4.2.3.2-1. - -**Table 3.4.4.2.3.2-1: URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| filter | 0..1 | Attribute-based filtering expression according to clause 5.2 of ETSI GS NFV-SOL 013 [22] .
The O-Cloud shall support receiving this parameter as part of the URI query string. The API consumer may supply this parameter.
All attribute names that appear in the ProvisioningRequestInfo and in data types referenced from it shall be supported by the O-Cloud in the filter expression. | -| all_fields | 0..1 | Include all complex attributes in the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter. | -| fields | 0..1 | Complex attributes to be included into the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_fields | 0..1 | Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_default | 0..1 | Indicates to exclude the following complex attributes from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.
The following attributes shall be excluded from the list of ProvisioningRequestInfo in the response body if this parameter is provided, or none of the parameters "all_fields", "fields", "exclude_fields", "exclude_default" are provided:
- TBD | -| nextpage_opaque_marker | 0..1 | Marker to obtain the next page of a paged response. Shall be supported by the O-Cloud if the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource. | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.4.4.2.3.2-2. - -Table 3.4.4.2.3.2-2: Details of the GET request/response on this resource - -| Request body | Data type | Cardinality | Description | | -|---------------|-------------------------|------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | ProvisioningRequestInfo | 0..N | 200 OK |

Shall be returned when information about zero or more ProvisioningRequestInfo instances has been queried successfully.

The response body shall contain in an array the representations of zero or more ProvisioningRequestInfo instances, as defined in clause 3.4.6.2.3.

If the "filter" URI parameter or one of the "all_fields", "fields" (if supported), "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request, the data in the response body shall have been transformed according to the rules specified in clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [22] , respectively.

If the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, inclusion of the Link HTTP header in this response shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013 [22] .

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute-based filtering expression.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute selector.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Response too big.

If the O-Cloud supports alternative 1 (error) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, this error response shall follow the provisions in clause 5.4.2.2 of ETSI GS NFV-SOL 013 [22] .

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx |

In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned.

| - -###### 3.4.4.2.3.3 PUT - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### 3.4.4.2.3.4 PATCH - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### 3.4.4.2.3.5 DELETE - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -#### 3.4.4.3 REST resource: ProvisioningRequest Description - -##### 3.4.4.3.1 Description - -The ProvisioningRequest Description represents an individual ProvisioningRequest that exists in the O-Cloud. - -##### 3.4.4.3.2 Resource definition - -Resource URI: - -**{apiRoot}O2ims\_infrastructureProvisioning/{apiMajorVersion}/provisioningRequests/{provisioningRequestId}** - -This resource shall support the resource URI variables defined in Table 3.4.4.3.2-1. - -**Table 3.4.4.3.2-1: Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------------|------------|-----------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| provisioningRequestId | Identifier | The identifier of the ProvisioningRequest resource. | - -NOTE: This identifier can be retrieved from the provisioningRequestId attribute in the payload body of the response to a GET request getting the list of "ProvisioningRequestInfo" resources. This identifier can be also retrieved from the resource referenced by the "Location" HTTP header in the response to a POST request creating a new ProvisioningRequest resource. - -##### 3.4.4.3.3 Resource methods - -###### 3.4.4.3.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### 3.4.4.3.3.2 GET - -The GET method is used to retrieve the description of a single ProvisioningRequest. - -This method shall support the URI query parameters specified in Table 3.4.4.3.3.2-1. - -**Table 3.4.4.3.3.2-1: URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------|-------------|-------------| -| n/a | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.4.4.3.3.2-2. - -**Table 3.4.4.3.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|-------------------------|------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | ProvisioningRequestInfo | 1 | 200 OK | Shall be returned when information about a ProvisioningRequestInfo instance has been queried successfully.
The response body shall contain a representation of the ProvisioningRequestInfo instance, as defined in clause 3.4.6.2.3. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.4.4.3.3.3 PUT** - -The PUT method is used to update fields of the ProvisioningRequest object. It operates as a “replace” or “overwrite” semantic model. All fields that are input to the ProvisioningRequest, i.e., as indicated by the data type "provisioningRequestData", can be updated, with the exception of the "provisioningRequestId". In case a different value of "provisioningRequestId" is indicated in the request payload compared to the "provisioningRequestId" that identifies the created ProvisioningRequest, the API producer shall return an appropriate error response. - -This method shall support the URI query parameters specified in Table 3.4.4.3.3.3-1. - -**Table 3.4.4.3.3.3-1: URI query parameters supported by the PUT method on this resource** - -| Name | Cardinality | Description | -|------|-------------|-------------| -| n/a | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.4.4.3.3.3-2. - -**Table 3.4.4.3.3.3-2: Details of the PUT request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|-------------------------|------------------|-----------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | ProvisioningRequestData | 1 | The parameters for the ProvisioningRequest, as defined in clause 3.4.6.2.2. | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | ProvisioningRequestInfo | 1 | 200 OK |

Shall be returned when the request has been accepted.

The response body shall contain a representation of the ProvisioningRequestInfo instance, as defined in clause 3.4.6.2.3.

| -| | ProblemDetails | 1 | 422 Unprocessable Content |

Shall be returned upon the following error: the content type of the message content is supported, and the message content of the request contains syntactically correct data, but the data cannot be processed.

In particular, this is due to the fact that the consumer has requested to modify values of the ProvisioningRequest instance that are not modifiable due to specific API producer logic such as trying to modify the value of the "provisioningRequestId".

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in ETSI GS NFV-SOL 013 [22], clause 6.4 may be returned. | - -###### **3.4.4.3.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### **3.4.4.3.3.5 DELETE** - -The DELETE method is used to perform delete operation on a single ProvisioningRequest. On receiving a DELETE request, the ProvisioningRequest instance transitions to 'DELETING' phase and in case resources had been provisioned, the O-Cloud starts performing the deprovision of corresponding O-Cloud NodeCluster and/or other Infrastructure Resources represented by the ProvisioningRequest instance being deleted. During this period the consumer can poll for the status of deletion using GET method on the ProvisioningRequest resource URI. Once there are no resources provisioned by the ProvisionedRequest, such as all corresponding resources are deleted successfully, the ProvisionigRequest resource instance is deleted. Further onwards a GET on this ProvisionigRequest URI shall return '404 Not Found' response. - -This method shall support the URI query parameters specified in Table 3.4.4.3.3.5-1. - -**Table 3.4.4.3.3.5-1: URI query parameters supported by the DELETE method on this resource** - -| Name | Cardinality | Description | -|------|-------------|-------------| -| n/a | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.4.4.3.3.5-2. - -**Table 3.4.4.3.3.5-2: Details of the DELETE request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|----------------|------------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | n/a | 1 | 202 Accepted | Shall be returned when the request has been accepted.
The HTTP response shall include a "Location" HTTP header containing the URI for the ProvisioningRequest instance being deleted. This URI can be used to poll for status of the delete request. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -### 3.4.5 Notifications - -#### 3.4.5.1 General - -The ProvisioningRequest object is designed for on-demand status retrieval. The consumer (SMO) can send a read request for the ProvisioningRequest object to retrieve its status. For example, while the ProvisioningRequest is being processed, the consumer can request the current status. The response will indicate the ProvisioningRequest's status, including its current ProvisioningPhase. - -Additionally, the set of provisioned resources that are provisioned once the ProvisioningRequest is fulfilled could include an O-Cloud NodeCluster and/or O-Cloud InfrastructureResource(s). These resources will be notified through the O-Cloud inventory change notification subscription. - -NOTE: Change notifications for ProvisioningRequest object is not defined in the present version of the document. - -### 3.4.6 Data model - -#### 3.4.6.1 REST resource data types - -This clause specifies the data types to be used in resource representations supported by the present API. - -Table 3.4.6.1-1 specifies the data types defined for the O2ims\_infrastructureProvisioning API. - -**Table 3.4.6.1-1: O2ims\_infrastructureProvisioning resource data types** - -| Data type | Clause defined | Description | Applicability | -|-------------------------|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------| -| ProvisioningRequestInfo | 3.2.6.2.2 | This data type represents the information about the ProvisioningRequest object to provision O-Cloud Node Cluster and/or O-Cloud Infrastructure Resource(s) in an O-Cloud | | - -#### 3.4.6.2 Structured data types - -##### 3.4.6.2.1 Introduction - -This clause defines the structures to be used in resource representations. - -##### 3.4.6.2.2 Type: ProvisioningRequestData - -This type represents information about the input parameters of a ProvisioningRequest object to provision O-Cloud Node Cluster and/or O-Cloud Infrastructure Resource(s) in an O-Cloud. It shall comply with the provisions defined in table 3.4.6.2.2-1. - -**Table 3.4.6.2.2-1: Definition of type ProvisioningRequestData** - -| Attribute name | Data type | P | Cardinality | Description | -|-----------------------|---------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| provisioningRequestId | Identifier | M | 1 | Identifier of the ProvisioningRequest instance assigned by the SMO. | -| name | String | M | 1 | Human readable name of the ProvisioningRequest instance as assigned by the SMO. | -| description | String | M | 1 | Human readable description of the ProvisioningRequest instance as assigned by the SMO. | -| templateName | String | M | 1 | Name of the template to be used as the basis for the declarative model for the ProvisioningRequest instance. When combined with the templateVersion it shall resolve to a templateId. | -| templateVersion | String | M | 1 | Version of the template used as the basis for the declarative model for the ProvisioningRequest instance. When combined with the templateName it shall resolve to a templateId. | -| templateParameters | KeyValuePairs | M | 0..1 | List of variables/value pairs used within the template to tailor the template to this ProvisioningRequest instance. | - -##### 3.4.6.2.3 Type: ProvisioningRequestInfo - -This type represents information about the ProvisioningRequest object to provision O-Cloud Node Cluster and/or O-Cloud Infrastructure Resource(s) in an O-Cloud. It shall comply with the provisions defined in table 3.4.6.2.3-1. - -**Table 3.4.6.2.3-1: Definition of type ProvisioningRequestInfo** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------------------|-------------------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| provisioningRequestData | ProvisioningRequestData | M | 1 | It represents information about the input parameters of a ProvisioningRequest object to provision O-Cloud Node Cluster and/or O-Cloud Infrastructure Resource(s) in an O-Cloud. It shall comply with the provisions defined in table 3.4.6.2.2-1. | -| provisioningRequestReference | Identifier | M | 1 | A unique reference of this ProvisioningRequest, assigned by the service producer (O-Cloud) at the time of request creation. This attribute can be used for, e.g., troubleshooting purposes. | -| status | ProvisioningStatus | M | 1 | The time of the last message and the current ProvisioningPhase of the ProvisioningRequest. | -| provisionedResourceSet | ProvisionedResourceSet | M | 0..1 | The resources that have been successfully provisioned as part of the ProvisioningRequest. | - -##### 3.4.6.2.4 Type: ProvisioningStatus - -This type represents information about the status of the ProvisioningRequest object to provision an O-Cloud Node Cluster and/or O-Cloud Infrastructure Resource(s) in an O-Cloud. It shall comply with the provisions defined in table 3.4.6.2.4-1. - -**Table 3.4.6.2.4-1: Definition of type ProvisioningStatus** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------------------------------|----------------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| updateTime | DateTime | M | 1 | The last date and time that the provisioningPhase attribute was modified. This attribute will follow the date-time format. | -| message | String | M | 1 | Human readable text about the provisioningPhase at the last updateTime. | -| provisioningPhase | ProvisioningPhase | M | 1 | This is an enumerated set of values which reflects the current phase of the provisioning request. | -| nodeClusterProvisioningStatus | ResourceProvisioningStatus | M | 0..1 | If the ProvisioningRequest includes provisioning of the NodeCluster, this attribute will contain the provisioning phase of the NodeCluster. | -| infrastructureResourceProvisioningStatus | ResourceProvisioningStatus | M | 0..N | If the ProvisioningRequest includes provisioning of the InfrastructureResource(s) this attribute will contain the individual provisioning phase of InfrastructureResources used to fulfil it. | - -##### **3.4.6.2.5 Type: ProvisionedResourceSet** - -This type represents information about the resources that have been successfully provisioned as part of the ProvisioningRequest in the O-Cloud. It shall comply with the provisions defined in table 3.4.6.2.5-1. - -**Table 3.4.6.2.5-1: Definition of type ProvisionedResourceSet** - -| Attribute name | Data type | P | Cardinality | Description | -|---------------------------|-----------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------| -| nodeClusterId | String | M | 0..1 | If the ProvisioningRequest is fulfilled by a NodeCluster this field will contain its Id. | -| infrastructureResourceIds | String | M | 0..N | If the ProvisioningRequest is fulfilled by InfrastructureResource(s) this list will contain the Id(s) of all resources used to fulfil it. | - -##### **3.4.6.2.6 Type: ResourceProvisioningStatus** - -This type represents information about the provisioning status of a resource requested to be provisioned using the ProvisioningRequest. It shall comply with the provisions defined in table 3.4.6.2.6-1 - -**Table 3.4.6.2.6-1: Definition of type ResourceProvisioningStatus** - -| Attribute name | Data type | P | Cardinality | Description | -|---------------------------|---------------------------|---|-------------|----------------------------------------------------------------------------------------------------| -| resourceName | String | M | 1 | Name of the resource as given in ProvisioningRequest parameters | -| resourceId | Identifier | M | 0..1 | Identifier of the resource, as assigned by the O-Cloud | -| resourceProvisioningPhase | ResourceProvisioningPhase | M | 1 | This is an enumerated set of values which presents the current provisioning phase of the resource. | - -#### **3.4.6.3 Simple data types and enumerations** - -##### **3.4.6.3.1 Introduction** - -This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. The simple data types defined in a request body, response body, or a structure type are defined in ETSI GS NFV-SOL -013 [22] or this clause of the present document. - -##### **3.4.6.3.2 Simple data types** - -The simple data types defined in table 3.4.6.3.2-1 shall be supported. - -**Table 3.4.6.3.2-1: Simple data types** - -| Type Name | Type Definition | Description | -|-----------|-----------------|-------------| -| n/a | | | - -##### 3.4.6.3.3 Enumerations - -###### 3.4.6.3.3.1 ProvisioningPhase - -The enumeration ProvisioningPhase shall comply with the provisions defined in table 3.4.6.3.3.1-1. - -**Table 3.4.6.3.3.1-1: Enumeration ProvivisoningPhase** - -| Enumeration value | Description | -|-------------------|--------------------------------------------------------------------------------------------------| -| PENDING | The ProvisioningRequest is waiting to be processed by the O-Cloud (IMS). | -| PROGRESSING | The O-Cloud (IMS) is processing the ProvisioningRequest and executing the actions to fulfill it. | -| FULFILLED | The ProvisioningRequest has been successfully processed and completed by the O-Cloud (IMS). | -| FAILED | The ProvisioningRequest could not be fully processed by the O-Cloud (IMS). | -| DELETING | The ProvisioningRequest is in the process of being deleted by the O-Cloud (IMS). | - -###### 3.4.6.3.3.2 ResourceProvisioningPhase - -This enumeration contains the possible values of the current provisioning phase of a resoure and shall comply with the provisions defined in table 3.4.6.3.3.2-1. - -**Table 3.4.6.3.3.2-1: Enumeration ResourceProvisioningPhase** - -| Enumeration value | Description | -|-------------------------|-------------------------------------------------------------------------------------------------| -| PROCESSING | The resource provisioning is under processing. | -| PROVISIONED | The resource has been provisioned successfully . | -| AWAITING_FREE_RESOURCES | IMS is waiting for free O-Cloud resources to be available for the provisioning of the resource. | -| FAILED | O-Cloud has experienced failures in provisioining the resource. | - -### 3.4.7 Error handling - -#### 3.4.7.1 General - -For the O2ims\_InfrastructureProvisioning Service API, HTTP error responses shall be supported as specified in clause 3.1.5. - -In addition, the requirements in the following clauses are applicable for the O2ims\_InfrastructureProvisioning Service API. - -#### 3.4.7.2 Protocol errors - -No specific protocol errors for the O2ims\_InfrastructureProvisioning Service API are specified. - -NOTE: Descriptions on how to perform error handling based on the ProvisioningRequest machinery are not provided in the present document version. - -#### 3.4.7.3 Application errors - -No specific application errors for the O2ims\_InfrastructureProvisioning Service API are specified. - -NOTE: Descriptions on how to perform error handling based on the ProvisioningRequest machinery are not provided in the present document version. - -### 3.4.8 Security - -No specific security procedures for the O2ims\_InfrastructureProvisioning Service API are specified beyond those in clause 3.1.7. - -## 3.5 O2ims\_InfrastructureSoftwareManagement Service API - -Not specified in the present document version. - -## 3.6 O2ims\_InfrastructureLifecycleManagement Service API - -### 3.6.1 Description - -This API allows the SMO to invoke O2ims\_InfrastructureLifecycleManagement Services towards the O-Cloud. - -Operations against SMO Service objects are not defined. - -At this time no operations are defined for O2ims\_InfrastructureLifecycleManagement in the present document version. - -### 3.6.2 API version - -For the O2ims\_InfrastructureLifecycleManagement Service API version as specified in the present document, the MAJOR version field shall be 1, the MINOR version field shall be 0, and the PATCH version field shall be 0. - -### 3.6.3 REST resources structure and methods - -REST resource structure and methods for this API are not specified in the present document version. - -### 3.6.4 REST resources - -Not specified in the present document version. - -### 3.6.5 Notifications - -#### 3.6.5.1 General - -Notifications shall comply to the Subscribe/Notify pattern described in clause 5.9 of ETSI GS NFV-SOL 015 [25]. - -**Table 3.6.5.1-1 Notifications overview** - -| Notification | Callback URI | HTTP method | Description | -|-------------------------------|--------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| -| OCloud Available Notification | callback | POST | Notify SMO when the O-Cloud has determined that it is complete enough to allow provisioning from the SMO and/or to begin to support workload deployments. | - -##### 3.6.5.1.1 OCloud Available Notification Description - -The OCloud Available Notification is used by the O-Cloud Infrastructure Management Service to register itself with the SMO. This occurs as part of the Genesis life cycle procedure when the O-Cloud has determined it can begin to support interactions with the SMO. - -##### 3.6.5.1.2 Target URI - -OCloud Available Notification.Callback URI "{oCloudAvailableEventNotification}" shall be used with the callback URI variables defined in table 3.6.5.1.2-1. - -**Table 3.6.5.1.2-1 OCloud Available Notification.Callback URI Variables** - -| Attribute name | Data type | P | Cardinality | Description | -|----------------|------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| globalCloudId | Identifier | M | 1 | Identifier of the O-Cloud instance. Globally unique across O-Cloud instances. This value was provided by the SMO with the callback URI at the beginning of O-Cloud genesis and used in registration at the end of genesis. | -| oCloudId | Identifier | M | 1 | Identifier of the O-Cloud instance. Unique within an O-Cloud instance. | -| IMS_EP | String | M | 1 | The URI to the Infrastructure Services APIRoot. | - -### 3.6.6 Data Model - -#### 3.6.6.1 REST resource data types - -This clause is not specified in the present document version. - -#### 3.6.6.2 Structured data types - -This clause is not specified in the present document version. - -#### 3.6.6.3 Simple data types and enumerations - -##### 3.6.6.3.1 Introduction - -This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. The simple data types defined in a request body, response body, or a structured type are defined in ETSI GS NFV-SOL 013 [22] or this clause of the specification. - -##### 3.6.6.3.2 Simple data types - -The simple data types defined in table 3.6.6.3.2-1 shall be supported. - -**Table 3.6.6.3.2-1: Simple data types** - -| Type Name | Type Definition | Description | -|-----------|-----------------|-------------| -| n/a | | | - -### 3.6.7 Error handling - -#### 3.6.7.1 General - -For the O2ims\_ InfrastructureLifecycleManagement Service API, HTTP error responses shall be supported as specified in clause 3.1.5. - -In addition, the requirements in the following clauses are applicable for the O2ims\_InfrastructureLifecycleManagement Service API. - -#### 3.6.7.2 Protocol errors - -No specific protocol errors for the O2ims\_InfrastructureLifecycleManagement Service API are specified. - -#### 3.6.7.3 Application errors - -No specific application errors for the O2ims\_InfrastructureLifecycleManagement Service API are specified - -### 3.6.8 Security - -No specific security procedures for the O2ims\_InfrastructureLifecycleManagement Service API are specified beyond those in clause 3.1.7. - -## 3.7 O2ims\_InfrastructurePerformance Service API - -### 3.7.1 Description - -This API allows the SMO to invoke O2ims\_InfrastructurePerformance Services towards the O-Cloud. - -The operations defined for O2ims\_InfrastructurePerformance Services through this API are: - -- Query information about one or more Performance Measurement Jobs, -- Create an individual Performance Measurement Job, -- Delete an individual Performance Measurement Job, -- Suspend an individual Performance Measurement Job, -- Resume an individual Performance Measurement Job, -- Ability to query and modify the configurable values which govern the behaviour of the Performance Service, -- Create an individual Performance Management Subscription and -- Query information about one or more Performance Management Subscriptions. - -### 3.7.2 API version - -For the O2ims\_InfrastructurePerformance Service API version as specified in the present document, the MAJOR version field shall be 2, the MINOR version field shall be 1, and the PATCH version field shall be 0. - -Table 3.7.2-1 lists the history of API version of the O2ims\_InfrastructurePerformance Service and the main capabilities added/removed across versions. - -**Table 3.7.2-1: History of API versions of the O2ims\_InfrastructurePerformance Service.** - -| Version | Description | -|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 1.0.0 | Initial API Supporting:
Measurement Job Query | -| 1.1.0 | New resources:
Performance Measurement Job Create
Performance Management Configuration | -| 2.0.0 | New method:
Performance Measurement Job Delete

Updated Data types:
MeasurementJob
MeasurementJobRequest | -| 2.1.0 | New resources:
Performance Measurement Job Suspend Task
Performance Measurement Job Resume Task
Performance Management Subscription
Performance Management Subscription List

New Data type:
MeasurementJobSuspendRequest | - -### 3.7.3 REST resources structure and methods - -All resource URIs of the API shall use the base URI specification defined in clause 3.1.2. The string "O2ims\_infrastructurePerformance" shall be used to represent {apiName}. All resource URIs in the clauses below are defined relative to the formed base URI (i.e., {apiRoot}/O2ims\_infrastructurePerformance/{apiVersion}). - -When ambiguity is possible, the term REST resource is used to make the distinction between the term resource as understood within the context of REST API from the term resource as understood within the context of O-RAN. - -Figure 3.7.3-1 shows the overall resource URI structure defined for the O2ims\_infrastructurePerformance Service API. - -![A hierarchical tree diagram showing the REST resource URI structure for the O2ims_infrastructurePerformance API. The root node is {apiRoot}/O2ims_infrastructurePerformance/{apiMajorVersion}. It branches into three main paths: /measurementJobs, /performanceServiceConfiguration, and /performanceSubscriptions. /measurementJobs further branches into /{measurementJobId}, which then branches into /suspend and /resume. /performanceSubscriptions branches into /{performanceSubscriptionId}.](a5481fd31c02b525617e70f2de357039_img.jpg) - -``` - -graph TD - Root["{apiRoot}/O2ims_infrastructurePerformance/{apiMajorVersion}"] - Root --- MJ["/measurementJobs"] - Root --- PSC["/performanceServiceConfiguration"] - Root --- PS["/performanceSubscriptions"] - MJ --- MJId["/{measurementJobId}"] - MJId --- Suspend["/suspend"] - MJId --- Resume["/resume"] - PS --- PSId["/{performanceSubscriptionId}"] - -``` - -A hierarchical tree diagram showing the REST resource URI structure for the O2ims\_infrastructurePerformance API. The root node is {apiRoot}/O2ims\_infrastructurePerformance/{apiMajorVersion}. It branches into three main paths: /measurementJobs, /performanceServiceConfiguration, and /performanceSubscriptions. /measurementJobs further branches into /{measurementJobId}, which then branches into /suspend and /resume. /performanceSubscriptions branches into /{performanceSubscriptionId}. - -**Figure 3.7.3-1: Resource URI structure of the O2ims\_infrastructurePerformance API** - -Table 3.7.3-1 provides an overview of the resources and applicable HTTP methods. - -The O-Cloud shall support responding to requests for all HTTP methods on the resources in table 3.7.3-1 that are marked as "M" (mandatory) in the "Cat" (category) column. The O-Cloud shall also support the "API versions" resources as specified in clause 3.1.8. - -**Table 3.7.3-1: Resources and methods overview** - -| Resource name | Resource URI | HTTP method | Cat | Description | -|------------------------------------------|-------------------------------------------------------|-------------|-----|----------------------------------------------------------------| -| Measurement Job List | /measurementJobs | POST | M | To create an individual Performance Measurement Job. | -| | | GET | M | To get a list of Performance Measurement Jobs | -| Measurement Job | /measurementJobs/{measurementJobId} | GET | M | To get an individual Performance Measurement Job | -| | | DELETE | M | To delete an individual Performance Measurement Job | -| Measurement Job Suspend Task | /measurementJobs/{measurementJobId}/suspend | POST | M | To suspend an individual Performance Measurement Job. | -| Measurement Job Resume Task | /measurementJobs/{measurementJobId}/resume | POST | M | To resume an individual Performance Measurement Job. | -| Performance Service Configuration | /performanceServiceConfiguration | GET | M | To get the current configuration of the performance service. | -| | | PUT | M | To set a whole new configuration of the performance service. | -| | | PATCH | M | Partially update the configuration of the performance service. | -| Performance Management Subscription List | /performanceSubscriptions | POST | M | To create an individual Performance Management Subscription. | -| | | GET | M | To get a list of Performance Management Subscriptions | -| Performance Management Subscription | /performanceSubscriptions/{performanceSubscriptionId} | GET | M | To get an individual Performance Management Subscription | - -### 3.7.4 REST resources - -#### 3.7.4.1 Introduction - -The O2ims Infrastructure Performance Service API described in the following clauses relate to Performance Management operations. These fall into four categories: Performance Measurement Job, Performance Management Reporting, Performance Management Subscription handling, and Performance Management configuration operations. Each of these REST operations relates to the four areas in the Information Model for Performance Management: Performance Measurement Store, Performance Measurement Report, Performance Subscription and Performance Measurement Jobs. See the O-RAN WG6.O-CLOUD-IM, clause 4.2.1.4.24, 4.2.1.4.21, 4.2.1.4.14 and 4.2.1.4.16 [36] for more details. These APIs enable a management system, such as the SMO, to setup Performance Measurement Jobs, to establish Performance Management Subscriptions (to receive reports), to configure Performance Management behaviour, and to interact with a Performance Measurement Store. There are REST resources and supported methods to Create, Query, Delete, Update, Suspend and Resume Performance Measurement Jobs. There are also REST resources and supported methods for Performance Management Subscription Query, Performance Management Subscription Update and Performance Management Subscription Delete. - -There are no preconditions or postconditions for a successful execution of each of the O2ims\_InfrastructurePerformance Service API triggered by a corresponding operation. - -#### 3.7.4.2 REST resource: Measurement Job List - -##### 3.7.4.2.1 Description - -This resource represents the list of Performance Measurement Jobs. The list can include Performance Measurement Jobs created either by the O-Cloud for internal monitoring or created by the SMO for additional measurement collection. - -##### 3.7.4.2.2 Resource definition - -Resource URI: {apiRoot}/O2ims\_infrastructurePerformance/{apiMajorVersion}/measurementJobs - -This resource shall support the resource URI variables defined in Table 3.7.4.2.2.1. - -**Table 3.7.4.2.2-1: Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | - -##### 3.7.4.2.3 Resource methods - -###### 3.7.4.2.3.1 POST - -The POST operation is used to create a Performance Measurement Job. - -This method shall support the URI query parameters specified in Table 3.7.4.2.3.1-1. - -**Table 3.7.4.2.3.1-1 URI query parameters supported by the POST method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.7.4.2.3.1-2. - -**Table 3.7.4.2.3.1-2: Details of the POST request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|-----------------------|------------------|-----------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | MeasurementJobRequest | 1 | Request for Performance Measurement Job instance to be created. | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | MeasurementJob | 1 | 201 Created | Shall be returned when a Performance Measurement Job instance has been created successfully.
The response body shall contain a representation of the MeasurementJob instance, as defined in clause 3.7.6.2.2. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### 3.7.4.2.3.2 GET - -The GET operation is used to retrieve the list of Performance Measurement Jobs. - -This method shall support the URI query parameters specified in Table 3.7.4.2.3.2-1. - -In the provisions below, according to clause 5.3.2.1 of ETSI GS NFV-SOL 013 [22], *complex attributes* are assumed to be those attributes that are structured or that are arrays and are thus atomic in nature. - -**Table 3.7.4.2.3.2-2: URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------------------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| filter | 0..1 | Attribute-based filtering expression according to ETSI GS NFV-SOL 013 [22], clause 5.2. The O-Cloud shall support receiving this parameter as part of the URI query string. The API consumer may supply this parameter.

All attribute names that appear in the MeasurementJob and in data types referenced from it shall be supported by the O-Cloud in the filter expression. | -| all_fields | 0..1 | Include all complex attributes in the response. See ETSI clause 5.3 of GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter. | -| fields | 0..1 | Complex attributes to be included into the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_fields | 0..1 | Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter. | -| exclude_default | 0..1 | Presence of this URI query parameter requests that a default set of complex attributes shall be excluded from the response. This parameter is a flag, i.e., it has no value. If none of the attribute selector parameters are specified, the " exclude_default " parameter shall be assumed as the default. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.

The following attributes shall be excluded from the list of MeasurementJob if this parameter is provided:
  • - measuredResources
  • - collectedMeasurements
| -| nextpage_opaque_marker | 0..1 | Marker to obtain the next page of a paged response. Shall be supported by the O-Cloud if the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource. | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.7.4.2.3.2-2. - -Table 3.7.4.2.3.2-2: Details of the GET request/response on this resource - -| Request body | Data type | Cardinality | Description | | -|---------------|----------------|------------------|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | MeasurementJob | 0..N | 200 OK |

Shall be returned when information about zero or more MeasurementJob instances has been queried successfully.

The response body shall contain in an array the representations of zero or more MeasurementJob instances, as defined in clause 3.7.6.2.2.

If the "filter" URI parameter or one of the "all_fields", "fields" (if supported), "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request, the data in the response body shall have been transformed according to the rules specified in clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [22], respectively.

If the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, inclusion of the Link HTTP header in this response shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013 [22].

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute-based filtering expression.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute selector. The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Response too big.

If the O-Cloud supports alternative 1 (error) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, this error response shall follow the provisions in clause 5.4.2.2 of ETSI GS NFV-SOL 013 [22].

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx |

In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned.

| - -###### 3.7.4.2.3.3 PUT - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.7.4.2.3.4 PATCH - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.7.4.2.3.5 DELETE - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### 3.7.4.3 REST resource: Measurement Job - -##### 3.7.4.3.1 Description - -This resource represents the details of a Performance Measurement Job in the Measurement Job List. The Measurement Job also keeps a record of the details of the Measurement Job since its creation, such as the historical list of resources measured with the Performance Measurement Job. - -##### 3.7.4.3.2 Resource definition - -Resource URI: - -**{apiRoot}/O2ims\_infrastructurePerformance/{apiMajorVersion}/measurementJobs/{measurementJobId}** - -This resource shall support the resource URI variables defined in Table 3.7.4.3.2-1. - -**Table 3.7.4.3.2-1: Resource URI variables for this resource** - -| Name | Data type | Definition | -|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| measurementJobId | Identifier | The identifier of the Measurement Job resource. See note. | -| NOTE: This identifier can be retrieved from the performanceMeasurementJobId attribute in the payload body of the response to a GET request getting the "Measurement Job List". | | | - -##### 3.7.4.3.3 Resource methods - -###### 3.7.4.3.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.7.4.3.3.2 GET - -The GET operation is used to retrieve the details of an individual Measurement Job. - -This method shall support the URI query parameters specified in Table 3.7.4.3.3.2-1. - -**Table 3.7.4.3.3.2-1: URI query parameters supported by the GET method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in 3.7.4.3.3.2-2. - -**Table 3.7.4.3.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|----------------|------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | MeasurementJob | 1 | 200 OK | Shall be returned when information about a MeasurementJob instance has been queried successfully.
The response body shall contain a representation of the MeasurementJob instance, as defined in clause 3.7.6.2.2. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.7.4.3.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.7.4.3.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.7.4.3.3.5 DELETE** - -The DELETE method is used to delete an individual Performance Measurement Job. - -This method shall support the URI query parameters specified in Table 3.7.4.3.3.5-1. - -**Table 3.7.4.3.3.5-1 URI query parameters supported by the DELETE method on this resource** - -| Name | Cardinality | Description | -|------|-------------|-------------| -| n/a | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.7.4.3.3.5-2. - -**Table 3.7.4.3.3.5-2: Details of the DELETE request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|----------------|------------------|------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | n/a | 1 | 204 (no content) | Shall be returned when the Performance Measurement Job has been deleted successfully. The response body shall be empty. | -| | ProblemDetails | 1 | 409 Conflict | Shall be returned upon the following error: Deletion of non-suspended Performance Measurement Job. The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error. | -| | ProblemDetails | 1 | 404 Not Found | Shall be returned upon the following error: Deletion of non-existent Performance Measurement Job. The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error. | -| | ProblemDetails | 1 | 403 Forbidden | Shall be returned upon the following error: Deletion was requested on a Preinstalled Performance Measurement Job, which is not permitted. The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -#### 3.7.4.4 REST resource: Performance Service Configuration - -##### 3.7.4.4.1 Description - -The Performance Service Configuration represents the ability to get and set the configurable values which govern the behaviour of the performance service. - -##### 3.7.4.4.2 Resource definition - -Resource URI: - -**{apiRoot}/O2ims\_infrastructurePerformance/{apiMajorVersion}/performanceServiceConfiguration** - -This resource shall support the resource URI variables defined in Table 3.7.4.4.2-1. - -**Table 3.7.4.4.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | - -##### 3.7.4.4.3 Resource methods - -###### 3.7.4.4.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] . - -###### 3.7.4.4.3.2 GET - -The GET operation is used to retrieve the current performance service configuration. - -This method shall support the URI query parameters specified in Table 3.7.4.4.3.2-1. - -**Table 3.7.4.4.3.2-1 URI query parameters supported by the GET method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.7.4.4.3.2-2. - -**Table 3.7.4.4.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|---------------------------------|------------------|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | PerformanceServiceConfiguration | 1 | 200 OK | Shall be returned when information about a PerformanceServiceConfiguration instance has been queried successfully.
The response body shall contain a representation of the PerformanceServiceConfiguration instance, as defined in clause 3.7.6.2.4. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in ETSI GS NFV-SOL 013 [22], clause 6.4 may be returned. | - -###### 3.7.4.4.3.3 PUT - -The PUT method is used to update all fields of the Performance Service Configuration. It operates as a replace or overwrite of the whole information representing the Performance Service Configuration - -This method shall support the URI query parameters specified in Table 3.7.4.4.3.3-1. - -**Table 3.7.4.4.3.3-2 URI query parameters supported by the PUT method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.7.4.4.3.3-2. - -**Table 3.7.4.4.3.3-2: Details of the PUT request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|---------------------------------|------------------|------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | Data type | | Cardinality | Response Codes | -| | PerformanceServiceConfiguration | 1 | The parameter for the Performance Service Configuration, as defined in clause 3.7.6.2.4. | | -| Response body | PerformanceServiceConfiguration | 1 | 200 OK |

Shall be returned when the request has been accepted and completed.

The response body shall contain a representation of the PerformanceServiceConfiguration with the result of the update (see clause 3.7.6.2.4).

| -| | ProblemDetails | 0..1 | 412 Precondition failed |

Shall be returned upon the following error: A precondition given in an HTTP request header is not fulfilled.

Typically, this is due to an ETag mismatch, indicating that the resource was modified by another entity prior to this request.

The response body should contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in ETSI GS NFV-SOL 013 [22], clause 6.4 may be returned. | - -###### **3.7.4.4.3.4 PATCH** - -The PATCH method is used to modify individual fields of the Performance Service Configuration, also referred to as a partial update - -A PATCH request shall enable only those fields of the performance service configuration that are contained in the request to be modified. Attributes not contained in the request will remain unmodified. - -NOTE: It is not specified in the present document version the handling of the modifications of the child attributes of the “extension” attribute in the representation of the performance service configuration. - -This method shall support the URI query parameters specified in Table 3.7.4.4.3.4-1. - -**Table 3.7.4.4.3.4-1 URI query parameters supported by the PATCH method on this resource** - -| Name | Data type | P | Cardinality | Description | Applicability | -|------|-----------|---|-------------|-------------|---------------| -| n/a | | | | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.7.4.4.3.4-2. - -**Table 3.7.4.4.3.4-2: Details of the PATCH request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|---------------------------------|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | PerformanceServiceConfiguration | 1 | The parameter for the Performance Service Configuration, as defined in clause 3.7.6.2.4. Only parameters requested to be updated shall be included in the message content

The Content-Type header shall be set to "application/merge-patch+json" according to IETF RFC 7396 [29]. | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | PerformanceServiceConfiguration | 1 | 200 OK | Shall be returned when the request has been accepted and completed.

The response body shall contain only the attributes that have been modified for the performance service configuration (see clause 3.7.6.2.4). | -| | ProblemDetails | 0..1 | 412 Precondition failed | Shall be returned upon the following error: A precondition given in an HTTP request header is not fulfilled.

Typically, this is due to an ETag mismatch, indicating that the resource was modified by another entity.

The response body should contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in ETSI GS NFV-SOL 013 [22], clause 6.4 may be returned. | - -###### **3.7.4.4.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in ETSI GS NFV-SOL 013 [22], clause 6.4. - -#### **3.7.4.5 REST resource: Performance Management Subscription List** - -##### **3.7.4.5.1 Description** - -This resource represents the list of Performance Management Subscriptions in the O-Cloud which the SMO can use to be notified when certain changes occur. The Performance Management Subscription List contains Performance Management Subscriptions. - -##### **3.7.4.5.2 Resource definition** - -Resource URI: {apiRoot}/O2ims\_infrastructurePerformance/{apiMajorVersion}/performanceSubscriptions - -This resource shall support the resource URI variables defined in Table 3.7.4.5.2-1. - -**Table 3.7.4.5.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|-----------------|-----------|------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | - -##### **3.7.4.5.3 Resource methods** - -###### **3.7.4.5.3.1 POST** - -The POST operation is used to create a Performance Management Subscription. - -This method shall support the URI query parameters specified in Table 3.7.4.5.3.1-1. - -**Table 0.1-1 URI query parameters supported by the POST method on this resource** - -| Name | Cardinality | Description | -|------|-------------|-------------| -| n/a | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.7.4.5.3.1-2. - -**Table 3.7.4.5.3.1-2: Details of the POST request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|-----------------------------|------------------|-----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | PerformanceSubscriptionData | 1 | The parameters for the creation of the Performance Management Subscription. | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | PerformanceSubscriptionInfo | 1 | 201
Created | Shall be returned when information about a PerformanceSubscriptionInfo instance has been created successfully.
The response body shall contain a representation of the PerformanceSubscriptionInfo instance, as defined in clause 3.7.6.2.6. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.7.4.5.3.2 GET** - -The GET operation is used to retrieve the list of Performance Management Subscriptions. - -This method shall support the URI query parameters specified in Table 0.2-1. - -In the provisions below, according to clause 5.3.2.1 of ETSI GS NFV-SOL 013 [22], *complex attributes* are assumed to be those attributes that are structured or that are arrays and are thus atomic in nature. - -**Table 0.2-1: URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------------------------|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| filter | 0..1 |

Attribute-based filtering expression according to ETSI GS NFV-SOL 013 [22], clause 5.2. The O-Cloud shall support receiving this parameter as part of the URI query string. The API consumer may supply this parameter.

All attribute names that appear in the PerformanceSubscriptionInfo and in data types referenced from it shall be supported by the O-Cloud in the filter expression.

| -| all_fields | 0..1 |

Include all complex attributes in the response. See ETSI clause 5.3 of GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.

| -| fields | 0..1 |

Complex attributes to be included into the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter.

| -| exclude_fields | 0..1 |

Complex attributes to be excluded from the response. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud should support this parameter.

| -| exclude_default | 0..1 |

Presence of this URI query parameter requests that a default set of complex attributes shall be excluded from the response. This parameter is a flag, i.e., it has no value. If none of the attribute selector parameters are specified, the "exclude_default" parameter shall be assumed as the default. See clause 5.3 of ETSI GS NFV-SOL 013 [22] for details. The O-Cloud shall support this parameter.

The following attributes shall be excluded from the list of PerformanceSubscriptionInfo if this parameter is provided:

  • - TBD
| -| nextpage_opaque_marker | 0..1 |

Marker to obtain the next page of a paged response. Shall be supported by the O-Cloud if the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource.

| - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.7.4.5.3.2-2. - -Table 3.7.4.5.3.2-2: Details of the GET request/response on this resource - -| Request body | Data type | Cardinality | Description | | -|---------------|-----------------------------|------------------|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | PerformanceSubscriptionInfo | 0..N | 200 OK |

Shall be returned when information about zero or more PerformanceSubscriptionInfo instances has been queried successfully.

The response body shall contain in an array the representations of zero or more PerformanceSubscriptionInfo instances, as defined in clause 3.7.6.2.6.

If the "filter" URI parameter or one of the "all_fields", "fields" (if supported), "exclude_fields" (if supported) or "exclude_default" URI parameters was supplied in the request, the data in the response body shall have been transformed according to the rules specified in clauses 5.2.2 and 5.3.2 of ETSI GS NFV-SOL 013 [22], respectively.

If the O-Cloud supports alternative 2 (paging) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, inclusion of the Link HTTP header in this response shall follow the provisions in clause 5.4.2.3 of ETSI GS NFV-SOL 013 [22].

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute-based filtering expression.

The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Invalid attribute selector. The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error.

| -| | ProblemDetails | 1 | 400 Bad Request |

Shall be returned upon the following error: Response too big.

If the O-Cloud supports alternative 1 (error) according to clause 5.4.2.1 of ETSI GS NFV-SOL 013 [22] for this resource, this error response shall follow the provisions in clause 5.4.2.2 of ETSI GS NFV-SOL 013 [22].

| -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx |

In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned.

| - -###### 3.7.4.5.3.3 PUT - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.7.4.5.3.4 PATCH - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.7.4.5.3.5 DELETE - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### 3.7.4.6 REST resource: Performance Management Subscription - -##### 3.7.4.6.1 Description - -This resource represents the details of a Performance Management Subscription in the O-Cloud which the SMO can use to be notified when certain changes occur. - -##### 3.7.4.6.2 Resource definition - -Resource URI: {apiRoot}/O2ims\_infrastructurePerformance/{apiMajorVersion}/performanceSubscriptions/{performanceSubscriptionId} - -This resource shall support the resource URI variables defined in Table 3.7.4.6.2-1. - -**Table 3.7.4.6.2-1 Resource URI variables for this resource** - -| Name | Data type | Definition | -|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------------------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| performanceSubscriptionId | Identifier | The identifier of the Performance Management Subscription. See note. | -| NOTE: This identifier can be retrieved from the performanceSubscriptionId attribute in the payload body of the response to a GET request getting the list of Performance Management Subscriptions. | | | - -##### 3.7.4.6.3 Resource methods - -###### 3.7.4.6.3.1 POST - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### 3.7.4.6.3.2 GET - -The GET operation is used to retrieve the details of an individual Performance Management Subscription. - -This method shall support the URI query parameters specified in Table 3.7.4.6.3.2-1. - -**Table 0.2-1: URI query parameters supported by the GET method on this resource** - -| Name | Cardinality | Description | -|------|-------------|-------------| -| n/a | | | - -This method shall support the request data structures, the response data structures, and response codes specified in 3.7.4.6.3.2-2. - -**Table 3.7.4.6.3.2-2: Details of the GET request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|-----------------------------|------------------|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | PerformanceSubscriptionInfo | 1 | 200 OK | Shall be returned when information about a PerformanceSubscriptionInfo instance has been queried successfully.
The response body shall contain a representation of the PerformanceSubscriptionInfo, as defined in clause 3.7.6.2.6. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -###### **3.7.4.6.3.3 PUT** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.7.4.6.3.4 PATCH** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -###### **3.7.4.6.3.5 DELETE** - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### **3.7.4.7 REST resource: Measurement Job Suspend Task** - -##### **3.7.4.7.1 Description** - -This task resource represents the Performance Measurement Job Suspend operation. The suspend operation on an individual Performance Measurement Job suspends collection of performance measurements and metrics on O-Cloud infrastructure. - -#### **3.7.4.7.2 Resource definition** - -Resource URI: -**{apiRoot}/O2ims\_infrastructurePerformance/{apiMajorVersion}/measurementJobs/{measurementJobId}/suspend** - -This resource shall support the resource URI variables defined in Table 3.7.4.7.2 1. - -**Table 0-1: Resource URI variables for this resource** - -| Name | Data type | Definition | -|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| measurementJobId | Identifier | The identifier of the Measurement Job resource. See note. | -| NOTE: This identifier can be retrieved from the performanceMeasurementJobId attribute in the payload body of the response to a GET request getting the "Measurement Job List". | | | - -### 3.7.4.7.3 Resource methods - -#### 3.7.4.7.3.1 POST - -The POST operation is used to suspend a Performance Measurement Job. Once the consumer issues a POST operation, the consumer can retrieve the state and status of the Performance Measurement Job by querying the Measurement Job resource. - -This method shall support the URI query parameters specified in Table 3.7.4.7.3.1-1. - -**Table 3.7.4.7.3.1-1 URI query parameters supported by the POST method on this resource** - -| Name | Cardinality | Description | -|------|-------------|-------------| -| n/a | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.7.4.7.3.1-2. - -**Table 3.7.4.7.3.1-2: Details of the POST request/response on this resource** - -| Request body | Data type | Cardinality | Description | | -|---------------|-------------------------------|------------------|----------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | MeasurementJobSuspend Request | 1 | This provides a time window (begin time, end time) for the Performance Measurement Job to be suspended within. | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | n/a | 1 | 202 Accepted | Shall be returned when the request has been accepted for processing. The response body shall be empty. | -| | ProblemDetails | 1 | 409 Conflict | Shall be returned upon the following error:
Suspending Performance Measurement Job in the "DEPRECATED" state. The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error. | -| | ProblemDetails | 1 | 404 Not Found | Shall be returned upon the following error:
Suspension of non-existent Performance Measurement Job.
The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -#### 3.7.4.7.3.2 GET - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### 3.7.4.7.3.3 PUT - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -#### 3.7.4.7.3.4 PATCH - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -### 3.7.4.7.3.5 DELETE - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -## 3.7.4.8 REST resource: Measurement Job Resume Task - -### 3.7.4.8.1 Description - -This task resource represents the Performance Measurement Job Resume operation. The resume operation on an individual Performance Measurement Job resumes collection of performance measurements and metrics on O-Cloud infrastructure. - -### 3.7.4.8.2 Resource definition - -Resource URI: - -`{apiRoot}/O2ims_infrastructurePerformance/{apiMajorVersion}/measurementJobs/{measurementJobId}/resume` - -This resource shall support the resource URI variables defined in Table 3.7.4.8.2 1. - -**Table 0-1: Resource URI variables for this resource** - -| Name | Data type | Definition | -|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------| -| apiRoot | String | See clause 3.1.2 | -| apiMajorVersion | String | See clause 3.1.2 | -| measurementJobId | Identifier | The identifier of the Measurement Job resource. See note. | -| NOTE: This identifier can be retrieved from the performanceMeasurementJobId attribute in the payload body of the response to a GET request getting the "Measurement Job List". | | | - -### 3.7.4.8.3 Resource methods - -#### 3.7.4.8.3.1 POST - -The POST operation is used to resume a Performance Measurement Job. Once the consumer issues a POST operation, the consumer can retrieve the state and status of the Performance Measurement Job by querying the Measurement Job resource. - -This method shall support the URI query parameters specified in Table 3.7.4.8.3.1-1. - -**Table 3.7.4.8.3.1-1 URI query parameters supported by the POST method on this resource** - -| Name | Cardinality | Description | -|------|-------------|-------------| -| n/a | | | - -This method shall support the request data structures, the response data structures, and response codes specified in Table 3.7.4.8.3.1-2. - -Table 3.7.4.8.3.1-2: Details of the POST request/response on this resource - -| Request body | Data type | Cardinality | Description | | -|---------------|----------------|------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | n/a | | | | -| Response body | Data type | Cardinality | Response Codes | Description | -| | n/a | 1 | 202 Accepted | Shall be returned when the request has been accepted for processing. The response body shall be empty. | -| | ProblemDetails | 1 | 409 Conflict | Shall be returned upon the following error: Resumption of Performance Measurement Job in the “ DEPRECATED ” state. The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error. | -| | ProblemDetails | 1 | 404 Not Found | Shall be returned upon the following error: Resumption of non-existent Performance Measurement Job.
The response body shall contain a ProblemDetails structure, in which the "detail" attribute should convey more information about the error. | -| | ProblemDetails | See clause 3.1.5 | 4xx/5xx | In addition to the response codes defined above, any common error response code as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22] may be returned. | - -3.7.4.8.3.2 GET - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -3.7.4.8.3.3 PUT - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -3.7.4.8.3.4 PATCH - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -3.7.4.8.3.5 DELETE - -This method is not supported. When this method is requested on this resource, the O-Cloud shall return a "405 Method Not Allowed" response as defined in clause 6.4 of ETSI GS NFV-SOL 013 [22]. - -### 3.7.5 Notifications - -The O2ims\_InfrastructurePerformance Service API does not specify any notifications. - -### 3.7.6 Data Model - -#### 3.7.6.1 REST resource data types - -Table 3.7.6.1-1 specifies the data types defined for the O2ims\_InfrastructurePerformance service API. - -**Table 3.7.6.1-1: O2ims\_InfrastructurePerformance resource data types** - -| Data type | Clause defined | Description | Applicability | -|---------------------------------|-----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------| -| MeasurementJob | 3.7.6.2.2 | This data type represents an instance of a Performance Measurement Job created either by the O-Cloud for internal monitoring or created by the SMO for additional measurement collection. | | -| MeasurementJobRequest | 3.7.6.2.3 | This data type represents a request for creation of a Performance Measurement Job by the consumer for measurement collection. | | -| PerformanceServiceConfiguration | 3.7.6.2.4 | This data type represents the Performance Service Configuration information. | | -| PerformanceSubscriptionInfo | 3.7.6.2.6 | This data type represents an instance of a Performance Management Subscription. | | - -### 3.7.6.2 Structured data types - -#### 3.7.6.2.1 Introduction - -This clause defines the structures to be used in resource representations. - -#### 3.7.6.2.2 Type: MeasurementJob - -This data type represents an instance of a Performance Measurement Job created either by the O-Cloud for internal monitor or created by the SMO for additional measurement collection. It shall comply with the provisions defined in table 3.7.6.2.2-1. - -**Table 3.7.6.2.2-1: Definition of type MeasurementJob** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------------------|----------------------|---|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| performanceMeasurementJobId | Identifier | M | 1 | Identifier of this instance of Performance Measurement Job within the IMS. This value is assigned by the IMS when the job is created | -| consumerPerformanceJobId | String | M | 0..1 | Identifier provided by the consumer for its purpose of managing performance jobs. This value could be the same across multiple instances of IMS performance job instances. | -| state | MeasurementJobState | M | 1 | The current state of the Performance Measurement Job. | -| collectionInterval | Integer | M | 1 | The interval at which performance measurements will be collected and stored. | -| resourceScopeCriteria | Key-value Pairs | M | 0..1 | Key-value pairs of resource attributes which are used to select resources from which measurements are to be collected.

This criterion determines, the value set for the Qualified Resource Types. | -| measurementSelectionCriteria | Key-value Pairs | M | 1 | Key-value pairs that identify the distinct set of measurements within the scope of a Performance Measurement Job. | -| status | MeasurementJobStatus | M | 1 | The current status within the state. See note 1. | -| preinstalledJob | Boolean | M | 1 | Boolean which is True if the PerformanceMeasurementJob was created by the O-Cloud and False for external consumer such as the SMO. | -| qualifiedResourceTypes | String | M | 0..N | This list is computed from evaluation of the resourceScopeCriteria. The resulting qualifiedResourceTypes are the distinct set of ResourceTypes among those measuredResources.

This list of resource type UUIDs is used to qualify collectedMeasurements defined in the PM Dictionary of the qualified resource types. | -| measuredResources | MeasuredResource | M | 0..N | This is the historical list of resources measured by this job. Resources added and deleted are kept track of for the life of the job. | -| collectedMeasurements | CollectedMeasurement | M | 0..N | The historical list of measurements that are or have been collected by this job based on its resourceScopeCriteria and measurementSelectionCriteria over the life of the job. | -| extensions | Key-value Pairs | M | 0..1 | These are unspecified properties (keys and values) which extend the information provided about the Performance Measurement Job. See note 2. | - -NOTE 1: The O-RAN WG6.O-CLOUD-IM [36], clauses 4.2.1.4.16.3 and 4.2.1.4.16.4 have more details for the valid status values per state. -NOTE 2: The extensions are not specified in the present document. None of the referenced documents do currently specify such extensions. - -**3.7.6.2.3 Type: MeasurementJobRequest** - -This data type represents a request for the creation of a Performance Measurement Job for measurement collection. It shall comply with the provisions defined in table 3.7.6.2.3-1. - -**Table 3.7.6.2.3-1: Definition of type MeasurementJobRequest** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------------------|----------------|---|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| consumerPerformanceJobId | String | M | 0..1 | Identifier provided by the consumer for purpose of managing the performance job. | -| collectionInterval | Integer | M | 1 | The interval at which performance measurements will be collected and stored. The unit shall be seconds. | -| resourceScopeCriteria | KeyValuesPairs | M | 0..1 | Key value pairs of resource attributes which are used to select resources from which measurements are to be collected.

This criterion determines the value set for the Qualified Resource Types. | -| measurementSelectionCriteria | KeyValuesPairs | M | 1 | Key value pairs that identify the distinct set of measurements within the scope of a Performance Measurement Job. | -| extensions | KeyValuesPairs | M | 0..1 | These are unspecified properties (keys and values) which extend the information provided about the Performance Measurement Job. See note. | - -NOTE: The extensions are not specified in the present document. None of the referenced documents do currently specify such extensions. - -**3.7.6.2.4 Type: PerformanceServiceConfiguration** - -This type represents information about the Performance Service Configuration which includes attributes to control the retention of measurements, and the meaningful metadata related to the performance service in the PerformanceMeasureStore, see O-RAN WG6.O-CLOUD-IM [36], clause 4.2.1.4.14. It shall comply with the provisions defined in table 3.7.6.2.4-1. - -**Table 3.7.6.2.4-1 Definition of type PerformanceServiceConfiguration** - -| Attribute name | Data type | P | Cardinality | Description | -|-----------------|----------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------| -| retentionPeriod | Integer | M | 1 | Number of days for measurements to be retained.

See note 1. | -| extensions | KeyValuesPairs | M | 0..1 | These are unspecified properties (keys and values) which can be tailored to control the behaviour of the Performance Service. See note 2. | - -NOTE 1: This value has a minimum limit such that it can't be set to a value lower than the limit. -NOTE 2: The extensions are not specified in the present document. None of the referenced documents do currently specify such extensions - -**3.7.6.2.5 Type: PerformanceSubscriptionData** - -The PerformanceSubscriptionData represents the attributes of the request to create a Performance Management Subscription. It shall comply with the provisions defined in table 3.7.6.2.5-1. - -**Table 3.7.6.2.5-2: Definition of type PerformanceSubscriptionData** - -| Attribute name | Data type | P | Cardinality | Description | -|---------------------------------------|-----------------------------------------|---|-------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| consumerPerformance
SubscriptionId | String | M | 0..1 | Identifier optionally provided by the consumer for the purpose of managing performance data. This value could be the same across multiple IMS instances because each may have separate subscription instances | -| subscriptionCriteria | PerformanceS
ubscriptionCrit
eria | M | 1 | This is the criteria which will apply to this subscription. | -| reportDeliveryMechani
sm | Enum (inlined) | M | 1 | The type of reporting mechanism for delivery of performance data.

The permitted values:
  • - NOTIFICATION: Send to the callback the data at the specified intervals.
  • - FILE: Generate a file with the data to be collected and send a notification to the callback with the filename whenever one is generated.
  • - STREAM: A streaming session remains open and continues to send the data in a streaming format at the specified intervals until the session or subscription is terminated.
See Note. | -| remoteFileLocation | Uri | M | 0..1 | When the reportDeliveryMechanism is set to FILE this field is populated with the URL to the remote directory where the service is expected to push the requested performance files to a remote files system. If the reportDeliveryMechanism is not FILE, the field is not present. | -| callback | Uri | M | 0..1 | The callback to send Measurement Report notification to when reportDeliveryMechanism is set to NOTIFICATION, or the File Ready notification when reportDeliveryMechanism is set to FILE. The attribute is not present if reportDeliveryMechanism is STREAM. | -| measurementReportin
gFrequency | Structure
(inlined) | M | 1 | The frequency that specified measurements are to be reported. | -| >subscriptionMode | Enum (inlined) | M | 1 | The mode in which data is reported.
The permitted valid values are:
  • - TARGET_DEFINED: The behaviour of the producer will be to act as either ON_CHANGE or SAMPLE, as determined by the producer.
  • - ON_CHANGE: Value is reported as soon as the Performance Measurement Job collects it.
SAMPLE: Value is reported at the reportInterval | -| >reportInterval | Integer | M | 0..1 | This is the reporting interval for the data, it is an unsigned integer representing the number of seconds between reports. If the reportInterval is lower than the service can provide the subscription shall return an error indicating such. If the value is set to zero (0) then the service will use its lowest supported value for the reportInterval. If this attribute is not provided in a request, the API producer shall use zero (0) as default value. | -| >suppressRedundant | Boolean | M | 0..1 | This flag identifies if SAMPLE values that have not changed shall (False) or shall not (True) be transmitted. If this attribute is not provided in a request, the API producer shall use False as default value. | - -| | | | | | -|--------------------|---------|---|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| >heartbeatInterval | Integer | M | 0..1 | When the suppressRedundant is set to (True), if heartbeatInterval is a non-zero value then a duplicate value will be sent at least once per heartbeatInterval. The value shall be zero (0) or a value greater than or equal to the reportInterval. If this attribute is not provided in a request, the API producer shall use zero (0) as default value. | -|--------------------|---------|---|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| - -NOTE: The formats of notification (e.g., JSON payload), file (e.g., XML file) and streaming (e.g., Google Protocol Buffers (GPB)) are not specified in the present document version - -### 3.7.6.2.6 Type: PerformanceSubscriptionInfo - -The PerformanceSubscriptionInfo represents the attributes of the Performance Management Subscription. It shall comply with the provisions defined in table 3.7.6.2.6-1. - -**Table 3.7.6.2.6-2: Definition of type PerformanceSubscriptionInfo** - -| Attribute name | Data type | P | Cardinality | Description | -|-----------------------------------|---------------------------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| performanceSubscriptionId | Identifier | M | 1 | Identifier of the performance subscription instance within the IMS. This value is assigned by the IMS when the subscription is created. | -| consumerPerformanceSubscriptionId | String | M | 0..1 | Identifier optionally provided by the consumer for the purpose of managing performance data. This value could be the same across multiple IMS instances because each may have separate subscription instances | -| subscriptionCriteria | PerformanceSubscriptionCriteria | M | 1 | This is the criteria which will apply to this subscription. | -| reportDeliveryMechanism | Enum (inlined) | M | 1 |

The type of reporting mechanism for delivery of performance data.

The permitted values are:

  • - NOTIFICATION: Send to the callback the data at the specified intervals.
  • - FILE: Generate a file with the data to be collected and send a notification to the callback with the filename whenever one is generated.
  • - STREAM: A streaming session remains open and continues to send the data in a streaming format at the specified intervals until the session or subscription is terminated.

See Note.

| -| remoteFileLocation | Uri | M | 0..1 | When the reportDeliveryMechanism is set to FILE this field is populated with the URL to the remote directory where the service is expected to push the requested performance files to a remote files system. If the reportDeliveryMechanism is not FILE, the field is not present. | -| callback | Uri | M | 0..1 | The callback to send Measurement Report notification to when reportDeliveryMechanism is set to NOTIFICATION, or the File Ready notification when reportDeliveryMechanism is set to FILE. The attribute is not present if reportDeliveryMechanism is STREAM. | -| measurementReportingFrequency | PerformanceReportingFrequency | M | 1 | The frequency that specified measurements are to be reported. | - -NOTE: The formats of notification (e.g., JSON payload), file (e.g., XML file) and streaming (e.g., Google Protocol Buffers (GPB)) are not specified in the present document version - -### 3.7.6.2.7 Type: PerformanceSubscriptionCriteria - -The PerformanceSubscriptionCriteria represents the information required to establish which measurements for which resource(s) are requested to be reported. It shall comply with the provisions defined in table 3.7.6.2.7-1. - -**Table 3.7.6.2.7-1: Definition of type PerformanceSubscriptionCriteria** - -| Attribute name | Data type | P | Cardinality | Description | -|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|---|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| jobCriteria | Identifier | M | 0..N | The list of performanceMeasurementJobId of interest. See Note. | -| resourceTypeCriteria | KeyValuesPairs | M | 0..1 | Key/Value list of criteria compared to Resource Type data. The Key shall correspond to the specified attribute names of the ResourceType (see clause 3.2.6.2.2), and the Value shall indicate the value of that attribute. See Note. | -| resourceCriteria | KeyValuesPairs | M | 0..1 | Key/Value list of criteria compared to Resource data. The Key shall correspond to the specified attribute names of the Resource (see clause 3.2.6.2.4), and the Value shall indicate the value of that attribute. See Note. | -| measurementCriteria | Identifier | M | 0..N | The list of performanceMeasurementDefinitionId of interest. See Note. | -| NOTE: At least one of these attributes shall be included. If more than one is included, the criteria selection operates as an "inclusion" (i.e., AND-operator). | | | | | - -### 3.7.6.2.8 Type: PerformanceReportingFrequency - -The PerformanceReportingFrequency represents the frequency that specified measurements are requested to be reported. It shall comply with the provisions defined in table 3.7.6.2.8-1. - -The information representing the attributes of the PerformanceReportingFrequency follows the provisions indicated in table 3.7.6.2.8-1. - -**Table 3.7.6.2.8-1: Definition of type PerformanceReportingFrequency** - -| Attribute name | Data type | P | Cardinality | Description | -|-------------------|----------------|---|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| subscriptionMode | Enum (inlined) | M | 1 | The mode in which data is reported.
The permitted valid values are:
- TARGET_DEFINED: The behaviour of the producer will be to act as either ON_CHANGE or SAMPLE, as determined by the producer.
- ON_CHANGE: Value is reported as soon as the Performance Measurement Job collects it.
- SAMPLE: Value is reported at the reportInterval | -| reportInterval | Integer | M | 1 | This is the reporting interval for the data, it is an unsigned integer representing the number of seconds between reports. If the reportInterval is lower than the service can provide the subscription shall return an error indicating such. If the value is set to zero (0) then the service will use its lowest supported value for the reportInterval. | -| suppressRedundant | Boolean | M | 1 | This flag identifies if SAMPLE values that have not changed shall (False) or shall not (True) be transmitted. | -| heartbeatInterval | Integer | M | 1 | When the suppressRedundant is set to (True), if heartbeatInterval is a non-zero value then a duplicate value will be sent at least once per heartbeatInterval. The value shall be zero (0) or a value greater than or equal to the reportInterval. | - -### 3.7.6.2.9 Type: MeasurementJobSuspendRequest - -This data type is used in the suspension of a Performance Measurement Job. The MeasurementJobSuspendRequest data type is used to specify a time window for Performance Management Job to be suspended through the API. It shall comply with the provisions defined in table 3.7.6.2.9-1. - -**Table 3.7.6.2.9-1: Definition of type MeasurementJobSuspendRequest** - -| Attribute name | Data type | P | Cardinality | Description | -|------------------|--------------------|---|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| timeWindow | Structure (inline) | M | 0..1 | Provides a time window (begin time, end time) for “ACTIVE” Performance Measurement Job to be suspended within. | -| >startWindowTime | DateTime | M | 0..1 | Start time of the timing window for the Performance Measurement Job to be suspended. If this attribute is not provided, the specified Performance Measurement Job will be suspended immediately. | -| >endWindowTime | DateTime | M | 0..1 | End time of the timing window for the Performance Measurement Job to be suspended. If this attribute is provided, the Performance Measurement Job will be suspended until the specified “endWindowTime”. If this attribute is not provided, the specified Performance Measurement Job will be suspended indefinitely. | - -### 3.7.6.3 Simple data types and enumerations - -#### 3.7.6.3.1 Introduction - -This clause defines simple data types and enumerations that can be referenced from data structures defined in the previous clauses. The simple data types defined in a request body, response body, or a structured type are defined in ETSI GS NFV-SOL 013 [22] or this clause of the specification. - -#### 3.7.6.3.2 Simple data types - -The simple data types defined in table 3.7.6.3.2-1 shall be supported. - -**Table 3.7.6.3.2-1 Simple data types** - -| Type Name | Type Definition | Description | -|-----------|-----------------|-------------| -| n/a | | | - -#### 3.7.6.3.3 Enumerations - -##### 3.7.6.3.3.1 MeasurementJobState - -The MeasurementJobState contains the value for the current condition of the Performance Measurement Job which reflects operational actions that is part of a state machine for the Performance Measurement Job. See O-RAN WG6.O-CLOUD-IM [36], clause 4.3.1.4.16.3 for more details. - -**Table 3.7.6.3.3.1-1 Enumeration MeasurementJobState** - -| Enumeration value | Description | -|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| ACTIVE | A Performance Measurement Job that has been created and is currently running is defined to be in the ACTIVE state. | -| SUSPENDED | Performance Measurement Job that has been created, and through a request to stop measurement collection is defined to be in the SUSPENDED state. See the Performance Measurement Job Suspend use case in the O-RAN WG6.ORCH-USE-CASES [23], clause 3.8.9 for more details. | -| DEPRECATED | Job has been deleted but there are still counters it collected in the Performance Measurement Store. As a result of a Performance Measurement job deletion request, the Performance Measurement job is defined to be in the DEPRECATED state. A Performance Measurement job will remain deprecated until the last performance measurement referring to it is deleted from the Performance Measurement Store. See the Performance Measurement Job Delete use case in the O-RAN WG6.ORCH-USE-CASES [23], clause 3.8.7 for more details. | - -**3.7.6.3.3.2 MeasurementJobStatus** - -The MeasurementJobStatus is further information within a current MeasurementJobState of a Performance Measurement Job. The state and status together provide a more complete view of the operational condition of a Performance Measurement Job. See O-RAN WG6.O-CLOUD-IM [36], clause 4.2.1.4.16.3 for more details. - -**Table 3.7.6.3.3.2-1: Enumeration MeasurementJobStatus** - -| Enumeration value | Description | -|-------------------|----------------------------------------------------------------------------------------------------------| -| RUNNING | Performance Measurement Job is ACTIVE and running without error. | -| FAILED | Performance Measurement Job is supposed to be collecting measures but has totally failed. | -| DEGRADED | Performance Measurement Job is having issues collecting some of the measures, but it is collecting some. | -| IDLE | Performance Measurement Job is SUSPENDED. | -| PENDING_DELETE | Performance Measurement Job is DEPRECATED. | - -### 3.7.7 Error handling - -#### 3.7.7.1 General - -For the O2ims\_InfrastructurePerformance Service API, HTTP error responses shall be supported as specified in clause 3.1.5. - -In addition, the requirements in the following clauses are applicable for the O2ims\_InfrastructurePerformance Service API. - -#### 3.7.7.2 Protocol errors - -No specific protocol errors for the O2ims\_InfrastructurePerformance Service API are specified. - -#### 3.7.7.3 Application errors - -No specific application errors for the O2ims\_InfrastructurePerformance Service API are specified. - -### 3.7.8 Security - -No specific security procedures for the O2ims\_InfrastructurePerformance Service API are specified beyond those in clause 3.1.7. - -## 3.8 O2ims\_InfrastructureLogging Service API - -Not specified in the present document version. - -# 4 O-Cloud Alarms - -## 4.1 General - -Clause 4 specifies the list of common alarms for O-Cloud, so that SMO can interpret the alarms from O-Cloud and perform root cause analysis in a multi-vendor environment. - -The template of alarms has been defined in clause 5.2.3.11.2 in O-RAN.WG10.Information Model and Data Models.0 [37]. This template consists of the attribute names for AlarmDictionary (such as alarmDefinitions and probableCauses). The specifications of O-Cloud alarms consist of possible values for such attributes, alarmDefinitionId and probableCauseId. - -ETSI NFV has defined alarms related to virtualized, containerized and cluster resources in clause 7 of ETSI GS NFV-IFA 045 [38]. Alarm definitions in ETSI GS NFV-IFA 045 specify the identifiers/names of the alarms, probable causes, associated managed objects and fault details, where applicable. - -Since the functional capabilities in NFV and O-Cloud environments are related, O-Cloud alarms can be based, but not limited to, on alarms specified in ETSI GS NFV-IFA 045 [38]. Therefore, here feasible, terminology of alarm definitions can be generalized to align and make reusable the alarm definitions between O-RAN and ETSI NFV frameworks. Table 4.1-1 provides a mapping between the O-RAN and ETSI NFV concepts and identified objects that are managed by respective frameworks. - -NOTE 1: Table 4.1-1 identifies in the present document version mapping of objects related to O-Cloud Node Clusters. The list can be extended in future versions of the present document. - -**Table 4.1-1: Concepts mapping between O-RAN and ETSI NFV** - -| O-RAN concept | ETSI NFV concept | Description | Reference | -|-----------------------------------|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------| -| O-Cloud Node Cluster | CIS cluster | In ETSI NFV, CIS refers to Container Infrastructure Services, which when termed together with cluster it implies that is a cluster that provides capabilities for deployment of containerized workloads. In O-RAN, the O-Cloud Node Cluster concept is described in clause 3.4.3.5.8 of O-RAN.WG6.O2-GA&P [24]. | Clause 7.6 of ETSI GS NFV-IFA 045 [38] specifies alarms associated to CIS cluster. | -| O-Cloud Node | CIS cluster node | A CIS cluster node is a compute resource that runs container infrastructure data plane services, or control plane services, or both. In O-RAN, the O-Cloud Node concept is described in clause 3.4.3.5.5 of O-RAN.WG6.O2-GA&P [24]. | Clause 7.6 of ETSI GS NFV-IFA 045 [38] specifies alarms associated to CIS cluster node. | -| O-Cloud Node Cluster Site Network | CIS cluster network | A CIS cluster network is a network connecting part of or the whole set of CIS cluster nodes conforming the CIS cluster. In O-RAN, the O-Cloud Node Cluster Site Network concept is described in clause 3.4.3.5.6 of O-RAN.WG6.O2-GA&P [24]. | Clause 7.6 of ETSI GS NFV-IFA 045 [38] specifies alarms associated to CIS cluster network. | - -In alarm definitions of ITU-T X.733 [27] and ETSI GS NFV-IFA 045 [38], five basic categories of alarm, which are named as “event type”, are specified as shown in Table 4.1-2 below. Additional five categories for security alarm causes are specified in ITU-T X.736 [28] and 3GPP TS 28.111 [42], and those are provided in Table 4.1-2. - -In ETSI GS NFV-IFA 045 [38], as well as in 3GPP TS 28.111 [42], all the probable causes are associated to specific "event type". The "event type" categories the kind of Alarms hence providing information for analysis and further correlation. - -**Table 4.1-2: Event types** - -| Event type | Description | -|-----------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| COMMUNICATIONS_ALARM | An alarm of this type is associated with the procedure and/or process required for conveying information from one point to another. (as defined by Recommendation ITU-T X.733 [27]). | -| PROCESSING_ERROR_ALARM | An alarm of this type is associated with a software or processing fault. (as defined by Recommendation ITU-T X.733 [27]). | -| ENVIRONMENTAL_ALARM | An alarm of this type is associated with a condition related to an enclosure in which the equipment resides. (as defined by Recommendation ITU-T X.733 [27]). | -| QOS_ALARM | An alarm of this type is associated with degradation in the quality of service. (as defined by Recommendation ITU-T X.733 [27]). | -| EQUIPMENT_ALARM | An alarm of this type is associated with an equipment fault. Equipment can be either logical devices that are realized via some form of virtualisation or physical devices. (as defined by Recommendation ITU-T X.733 [27]). | -| INTEGRITY_VIOLATION | An indication that information may have been illegally modified, inserted or deleted. (as defined by Recommendation ITU-T X.736 [28]). | -| OPERATIONAL_VIOLATION | An indication that the provision of the requested service was not possible due to the unavailability, malfunction or incorrect invocation of the service. (as defined by Recommendation ITU-T X.736 [28]). | -| PHYSICAL_VIOLATION | An indication that a physical resource has been violated in a way that suggests a security attack. (as defined by Recommendation ITU-T X.736 [28]). | -| SECURITY_SERVICE_OR_MECHANISM VIOLATION | An indication that a security attack has been detected by a security service or mechanism. (as defined by Recommendation ITU-T X.736 [28]). | -| TIME_DOMAIN_VIOLATION | An indication that an event has occurred at an unexpected or prohibited time. (as defined by Recommendation ITU-T X.736 [28]). | - -## 4.2 Alarm Definition Identifiers - -This clause describes the list of O-RAN standardised values for alarmDefinitionId. - -Table 4.2-1 lists the specified alarm definitions, based on ETSI GS NFV-IFA 045 [38] alarms definition scopes, with the alarm definition identifier and a description of the meaning (semantics) of the alarm in the O-Cloud context. - -**Table 4.2-1 List of alarmDefinitionIds** - -| Associated object | Alarm definition Identifier | Description | -|-----------------------------------|-----------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| O-Cloud Node Cluster | CLUSTER_WARNING | One or multiple of the underlying resources of the O-Cloud Node Cluster have potential impeding service impacts, but the O-Cloud Node Cluster is still operational. | -| | CLUSTER_MINOR | One or multiple of the underlying resources of the O-Cloud Node Cluster are experimenting non-service affecting fault conditions and the O-Cloud Node Cluster has nonservice affecting fault conditions. | -| | CLUSTER_MAJOR | One or multiple of the underlying resources of the O-Cloud Node Cluster have service affecting conditions, but the O-Cloud Node Cluster is still operational. | -| | CLUSTER_CRITICAL | One or multiple of the underlying resources of the O-Cloud Node Cluster has service affecting conditions and the O-Cloud Node Cluster is not fully operational. | -| O-Cloud Node | CLUSTERNODE_WARNING | One or multiple of the underlying resources or software of the O-Cloud Node have potential impeding service impacts, but the O-Cloud Node is still operational. | -| | CLUSTERNODE_MINOR | One or multiple of the underlying resources or software of the O-Cloud Node are experimenting non-service affecting fault conditions and the O-Cloud Node has non-service affecting fault conditions. | -| | CLUSTERNODE_MAJOR | One or multiple of the underlying resources or software of the O-Cloud Node have service affecting conditions, but the O-Cloud Node is still operational. | -| | CLUSTERNODE_CRITICAL | One or multiple of the underlying resources or software of the O-Cloud Node has service affecting conditions and the O-Cloud Node is not fully operational. | -| O-Cloud Node Cluster Site Network | CLUSTERNETWORK_WARNING | One or multiple of the underlying resources or software of the O-Cloud Node Cluster Site Network resource have potential impeding service impacts, but the O-Cloud Node Cluster Site Network resource is still operational. | -| | CLUSTERNETWORK_MINOR | One or multiple of the underlying resources or software of the O-Cloud Node Cluster Site Network resource are experimenting non-service affecting fault conditions and the O-Cloud Node Cluster Site Network resource has non-service affecting fault conditions. | -| | CLUSTERNETWORK_MAJOR | One or multiple of the underlying resources or software of the O-Cloud Node Cluster Site Network resource have service affecting conditions, but the O-Cloud Node Cluster Site Network resource is still operational. | -| | CLUSTERNETWORK_CRITICAL | One or multiple of the underlying resources or software of the O-Cloud Node Cluster Site Network resource has service affecting conditions and the O-Cloud Node Cluster Site Network resource is not fully operational. | - -## 4.3 Probable Cause Identifiers - -This clause describes the list of O-RAN standardised values for probableCauseId. The probable causes are used to provide additional information when reporting an alarm involving those listed as "associated objects". The objects - -shown in the following Table 4.3-1 does not imply that associated objects are individually managed, but rather lists a set of objects with probable cause information about the failures. - -Table 4.3-1 lists the specified probable causes, based on ETSI GS NFV-IFA 045 [38] probable cause scopes, with the probable cause identifiers, event types, and the fault details in the O-Cloud context. - -NOTE 1: The probable causes specified in ETSI GS NFV-IFA 045 [38] are in turn based on and cover the typical probable cause scopes as defined in ITU-T Recommendation X.733 [27], but considering the specific referenced objects listed in Table 4.3-1 and their resource-level realization, such as, for instance, when a compute related object (see O-Cloud Node in table 4.3-1) contains also network and storage elements. - -NOTE 2: Table 4.3-1 provides a list of defined probable causes and associated event types. Implementations may define/use additional probable causes with tailored description and semantics to be mapped to a different event type, if necessary. - -**Table 4.3-1 List of probableCauseIds** - -| Associated object | Probable cause identifier | Description | Event type | -|----------------------|---------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|------------------------| -| O-Cloud Node Cluster | CLUSTER_COMMUNICATION | Event related to the communication within the O-Cloud Node Cluster between O-Cloud Nodes. | COMMUNICATIONS_ALARM | -| O-Cloud Node | CERTIFICATE_EXPIRATION | Event related to expiration of certificate(s) for the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | CPU_BUS | Event related to buses of a CPU resource associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | CPU_CONFIGURATION | Configuration related event or state change on a CPU resource associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | CPU_DOWN | CPU resource associated to the O-Cloud Node is down/not available. | EQUIPMENT_ALARM | -| | CPU_PROTOCOL | Event related to CPU protocol, e.g. initialization procedure, state transitions, etc., on a CPU resource associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | CPU_TEMPERATURE | Event related to the temperature on a CPU resource associated to the O-Cloud Node. | ENVIRONMENTAL_ALARM | -| | CPU_THROTTLING | Throttling related event or state change on a CPU resource associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | HOST_OS_ERROR | Event related to processing failure in the host OS of the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | MEMORY_BIT_ERROR | Event related to single/multiple bit errors of the memory resource associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | MEMORY_CONFIGURATION | Event related to configuration of the memory resource associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | MEMORY_ECC | Event related to changes in states or rates concerning Error Correction Code (ECC) of the memory resource associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | MEMORY_REDUNDANCY | Event related to redundancy configuration of the memory resource associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | MEMORY_STATE | Event related to change of state on the memory resource associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | - -| Associated object | Probable cause identifier | Description | Event type | -|-------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|------------------------| -| | MEMORY_TEMPERATURE | Event related to the temperature of memory resource associated to the O-Cloud Node. | ENVIRONMENTAL_ALARM | -| | INFRA_COMPONENT_MAINTENANCE | Event related to maintenance of an infrastructure component associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | INFRA_COMPONENT_POWER_OUTAGE | Event related to power outage of an infrastructure component associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | NIC_CABLE | Event related to cabling/connection of the network interface associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | NIC_CONFIGURATION | Event related to a configuration of the network interface associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | NIC_DOWN | Event related to the NIC associated to the O-Cloud Node is down/not available. | EQUIPMENT_ALARM | -| | NIC_LINK_DOWN | Event related to a link down on the network interface associated to the O-Cloud Node. | COMMUNICATIONS_ALARM | -| | NIC_LINK_TUNING | Event related to link tuning of the network interface associated to the O-Cloud Node. | COMMUNICATIONS_ALARM | -| | NIC_PCI_ERROR | Event related to a component of a Peripheral Component Interconnect (PCI) device of the network interface associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | NIC_PCI_PARITY_ERROR | Event related to PCI parity errors of the network interface associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | NIC_PCIE_ERROR | Event related to a component of a PCI Express (PCIE) device of the network interface associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | NIC_RECEIVE_FAILURE | Event related to errors in the reception of packet/frames by the network interface associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | NIC_TRANSMIT_FAILURE | Event related to errors in the transmission of packet/frames by the network interface associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | NODE_DOWN | Event related to the virtual compute or bare-metal machine associated to the O-Cloud Node is down/not available. | EQUIPMENT_ALARM | -| | PROCESSOR_SENSOR | Sensor related event or state change on a processor resource associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | STORAGE_BIT_ERROR | Event related to single/multiple bit errors on the storage resource associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | STORAGE_BLOCK_ERROR | Event related to bad blocks on the storage resource associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | STORAGE_CACHE | Event related to the cache of the storage resource associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | STORAGE_CAPACITY | Event related to capacity (such as shortage) of the storage resource associated to the O-Cloud Node. | QOS_ALARM | - -| Associated object | Probable cause identifier | Description | Event type | -|-------------------|--------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| -| | STORAGE_CHECK | Event related to consistency checks on a storage resource associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | STORAGE_COMMUNICATION | Event related to the communication to/from the storage resource associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | STORAGE_CONFIGURATION | Event related to the configuration of the storage associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | STORAGE_CONTROLLER | Event related to the controller of the storage resource associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | STORAGE_DOWN | Storage resource associated to the O-Cloud Node is down/not available. | PROCESSING_ERROR_ALARM | -| | STORAGE_DRIVE_ARRAY | Event related to storage's drive array associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | STORAGE_ECC | Event related to changes in states or rates concerning Error Correction Code (ECC) of the storage or memory resources associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | STORAGE_ENCLOSURE | Event related to the enclosure of the storage resource associated to the O-Cloud Node. | ENVIRONMENTAL_ALARM | -| | STORAGE_FAILURE_PREDICTION | Event related to a predictive failure confirmed on a storage resource associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | STORAGE_MEMORY | Event related memory resources of the storage resource associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | STORAGE_PHYSICAL_DISK_DEGRADED | Event related to the performance on a physical disk resource associated to the O-Cloud Node. | QOS_ALARM | -| | STORAGE_PHYSICAL_DISK_STATE | The state has changed on a physical disk resource associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | STORAGE_POWER | Event related to power supply and/or power status of the storage resource associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | STORAGE_REBUILD | Event related to the rebuild process of the storage resource associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | STORAGE_REDUNDANCY | Event related to redundancy configuration of the storage resource associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | STORAGE_SCSI | Event related to the Small Computer System Interface (SCSI) of the storage resource associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | STORAGE_SENSOR | Event or state change related to sensor of the storage resource associated to the O-Cloud Node. | EQUIPMENT_ALARM | -| | STORAGE_SMART | Event related to the Self-Monitoring Analysis and Reporting Technology (SMART) feature of the storage resource associated to the O-Cloud Node. | EQUIPMENT_ALARM | - -| Associated object | Probable cause identifier | Description | Event type | -|-----------------------------------|-------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------| -| | STORAGE_TEMPERATURE | Event related to the temperature of the storage resource associated to the O-Cloud Node. | ENVIRONMENTAL_ALARM | -| | STORAGE_VIRTUAL_DISK_DEGRADED | Event related to the performance on a virtual disk resource associated to the O-Cloud Node. | QOS_ALARM | -| | STORAGE_VIRTUAL_DISK_STATE | The state has changed on a virtual disk resource associated to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| | SYSTEM_LICENSE_EXPIRATION | Event related to expiration of a license applicable to the O-Cloud Node. | PROCESSING_ERROR_ALARM | -| O-Cloud Node Cluster Site Network | NETWORK_CONFIGURATION | Event related to configuration issues with a network resource associated to the O-Cloud Node Cluster Site Network. | PROCESSING_ERROR_ALARM | -| | NETWORK_CONNECTIVITY_SIGNAL | Event related to loss or changes in the connectivity signal provided/supported by a network resource associated to the O-Cloud Node Cluster Site Network. | COMMUNICATIONS_ALARM | -| | NETWORK_CPU_OVERLOAD | Event related to overload in the CPU/compute subsystems of a network resource associated to the O-Cloud Node Cluster Site Network. | PROCESSING_ERROR_ALARM | -| | NETWORK_MEMORY_OVERLOAD | Event related to overload in the memory subsystems of a network resource associated to the O-Cloud Node Cluster Site Network. | PROCESSING_ERROR_ALARM | -| | NETWORK_OVERLOAD | Event related to overload network input/output on a network resource associated to the O-Cloud Node Cluster Site Network. | QOS_ALARM | -| | NETWORK_PACKET_LOSS | Event related to packet loss experienced on a network resource associated to the O-Cloud Node Cluster Site Network. | COMMUNICATIONS_ALARM | -| | NETWORK_QOS | Event related to degradation of QoS levels of a network resource associated to the O-Cloud Node Cluster Site Network. | QOS_ALARM | - -## Annex (informative): Change History - -| Date | Revision | Description | -|------------|----------|----------------------------------------------------------------------------------------------------------------------------------| -| 2023.10.13 | 04.00.01 | Implemented CRs ATT-021, NOK-0066, NOK-0077 | -| 2023.11.10 | 04.00.02 | Implemented CRs ATT-0022, DCM-0001, NOK-0078, and editorial updates | -| 2023.11.17 | 04.00.03 | Editorial updates based on review comments | -| 2023.11.28 | 05.00 | Final version 05.00 with editorial updates | -| 2024.03.19 | 05.00.01 | Implemented CRs NOK-0095, NOK-0092, DTAG-0001, DTAG-0002, ATT-0023 | -| 2024.03.20 | 05.00.02 | Editorial updates based on review comments | -| 2024.03.22 | 05.00.03 | Editorial updates based on review comments | -| 2024.03.22 | 05.00.04 | Editorial updates based on review comments | -| 2024.04.01 | 06.00 | Final version 06.00 | -| 2024.07.15 | 06.00.01 | Implemented CRs ATT-024, ATT-0025, ATT-026, DELL-0007, NOK-0087, NOK-0114, NOK-0102 | -| 2024.07.19 | 06.00.02 | Editorial updates based on review comments | -| 2024.07.29 | 07.00 | Final version 07.00 | -| 2024.11.14 | 07.00.01 | Implemented CRs ATT-0027, DCM-002, DTAG-0005, DTAG-0007, DTAG-0004, NOK-0128, NOK-0132, NOK-0129, and editorial changes | -| 2024.11.26 | 07.00.02 | Editorial updates based on review comments | -| 2024.12.02 | 07.00.03 | Updates made based on review comments | -| 2024.12.03 | 07.00.04 | Updates made based on review comments | -| 2024.12.03 | 07.00.05 | Updates made based on review comments | -| 2024.12.09 | 08.00 | Final version 08.00 | -| 2025.03.14 | 08.00.01 | Implemented CRs DCM-003, DELL-0011, DTAG-0008, ERI-0054, ERI-0058, NOK-0115, NOK-0145 | -| 2025.03.19 | 08.00.02 | Updates made based on review comments | -| 2025.03.20 | 08.00.03 | Updates made based on review comments | -| 2025.03.26 | 09.00 | Final version 09.00 | -| 2025.07.11 | 09.00.01 | Implemented CRs ATT-0028, DCM-0004, DELL-0013, DTAG-0011, DTAG-0014, DTAG-0010, ERI-0068, NOK-0149, RHT-0005, RHT-0006, RMI-0038 | -| 2025.07.17 | 09.00.02 | Updates made based on review comments | -| 2025.07.17 | 09.00.03 | Updates made based on review comments | -| 2025.07.18 | 10.00 | Final version 10.00 | -| 2025.11.20 | 10.00.01 | Implemented CRs DTAG-0009, DTAG-0015, DTAG-0017, DTAG-0019, ERI-0088, ERI-0090 | -| 2025.11.26 | 10.00.02 | Updates made based on review comments | -| 2025.11.28 | 11.00 | Final version 11.00 | \ No newline at end of file diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/05ec650892a1d3916ffe3d2a7ec29928_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/06e272c534fab6c7202d1355b043faf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/09fcf056902487318885284a6b43b08c_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/09fcf056902487318885284a6b43b08c_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/09fcf056902487318885284a6b43b08c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/0a65720e640be13541e947c06c7a8c7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg deleted file mode 100644 index 5573e6eb8e16d8b6dcd2ab04900f1bbadca2db92..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/0ae5a5c69a1f265dcdb1abf5d46d0de1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:07d85c8d8455dd1d432a4c876a9c5e5e32c2db3b125b5d1da4dc3597c9a89213 -size 3895 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/1099a4137017f2d9721d546bbb1e9362_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg deleted file mode 100644 index 8d4af7af6f97ed9d06f4202eedc3fb3669b12033..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/110058f0fd9c7ca251db430f6df06b80_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3819c22741753857d090b72b5497407df3e246ab79514e2c140d5af1c8bcc7 -size 3887 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/13249a22bfff48bf6d20110d7228bfcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/14af8d47efd24c21fddf71b2415b6397_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg deleted file mode 100644 index 9521bc0068649c1df30945e1661689082c9fbec5..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/153b4763edcf6b16d783052c7ad165f1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a0e6778892783df8645cfbb6f3a56c196c45d4b973c1653ca680f8ce74012fbb -size 3889 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/188fd1cc0a6b1ef1f70fb01d59e058c0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/1baaba7a6e54e77197475726c871067d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg deleted file mode 100644 index 8d4af7af6f97ed9d06f4202eedc3fb3669b12033..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/1e7157ed1c2b915b5b1823b6ad189038_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3819c22741753857d090b72b5497407df3e246ab79514e2c140d5af1c8bcc7 -size 3887 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg deleted file mode 100644 index 5573e6eb8e16d8b6dcd2ab04900f1bbadca2db92..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/1f0d4018f872bfcffec260045c6dd734_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:07d85c8d8455dd1d432a4c876a9c5e5e32c2db3b125b5d1da4dc3597c9a89213 -size 3895 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 022e87bb71372a7b6538215f2499319d726c6c51..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a9ff00a222f00dccfb1d05935f62869d2fc3b19ae53459cec9615bdf7fa2fce8 -size 3875 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg deleted file mode 100644 index 8d4af7af6f97ed9d06f4202eedc3fb3669b12033..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/256ec100c3aeedb411eee5a09386812e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3819c22741753857d090b72b5497407df3e246ab79514e2c140d5af1c8bcc7 -size 3887 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index 8d4af7af6f97ed9d06f4202eedc3fb3669b12033..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3819c22741753857d090b72b5497407df3e246ab79514e2c140d5af1c8bcc7 -size 3887 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/2b7c350726e78976d2dfd3ce90daa9f7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg deleted file mode 100644 index 98fa195c98ee1a0bdb7583d8c45295d7409254d5..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/2cb201535956cd78d7fd3cc89f3c7d03_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b2ec9b90fadc22d8f8bfd6b18c98a34b854e3ba75135266cedfdbecf0fd2e38d -size 3914 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/2d6a2e109d10cdfbc7b816a4d60d0174_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/2d7f360dbd01bbd1afb87d7db0cdae5c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg deleted file mode 100644 index 8d4af7af6f97ed9d06f4202eedc3fb3669b12033..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/3117e1f4e4767bab3f5c7cfaf4804652_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3819c22741753857d090b72b5497407df3e246ab79514e2c140d5af1c8bcc7 -size 3887 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/318db222fae24a59c370fa6471d541b8_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/318db222fae24a59c370fa6471d541b8_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/318db222fae24a59c370fa6471d541b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/35437f160e157760713aa85be471c3f3_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/35437f160e157760713aa85be471c3f3_img.jpg deleted file mode 100644 index 022e87bb71372a7b6538215f2499319d726c6c51..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/35437f160e157760713aa85be471c3f3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a9ff00a222f00dccfb1d05935f62869d2fc3b19ae53459cec9615bdf7fa2fce8 -size 3875 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg deleted file mode 100644 index fcc8de3880c83dd858faea9d2d670e19b6fd72d2..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/36e4a08fb5114c98c80f946714cc6c30_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a988b79737893a992c835186be603cd3a1175db327506e447f177abdaf177a58 -size 3874 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 022e87bb71372a7b6538215f2499319d726c6c51..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a9ff00a222f00dccfb1d05935f62869d2fc3b19ae53459cec9615bdf7fa2fce8 -size 3875 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index 8d4af7af6f97ed9d06f4202eedc3fb3669b12033..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3819c22741753857d090b72b5497407df3e246ab79514e2c140d5af1c8bcc7 -size 3887 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/3b89d812329a65ab156184a40524adf0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/3b89d812329a65ab156184a40524adf0_img.jpg deleted file mode 100644 index 6bc4227912ebd1dbeb86a2e89424bae60819f821..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/3b89d812329a65ab156184a40524adf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8542c92209e866bc151a1bb611f4d3bd1cf5ea3a8ff363f5ce37c4406c38cd06 -size 3901 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 90e28037e184fb3c0c977a4ae14ef8a6a2ef6c5e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:df4e1f868ba79d5c03d4c5802d7959558fc1aa6137de60a1692cf3005d5f54b9 -size 3954 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/41863cc6f48c5a6ff0290186547042d9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/446c0bd806260f25430cadb01a6786c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/47a7beddcb8a1b7abdca746967e32bb4_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/47a7beddcb8a1b7abdca746967e32bb4_img.jpg deleted file mode 100644 index c8aaf04b98789b0c49c9bc9e7edd9bab979eabe1..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/47a7beddcb8a1b7abdca746967e32bb4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:596d3d41fa2f13c74c2a789f4d8dff66223da5f90fc3a09571e7e30a92e06d7d -size 133879 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg deleted file mode 100644 index 5573e6eb8e16d8b6dcd2ab04900f1bbadca2db92..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/488b6387bc5fe15b9528eca7968a8733_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:07d85c8d8455dd1d432a4c876a9c5e5e32c2db3b125b5d1da4dc3597c9a89213 -size 3895 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4932f76f000f1673ac40baf1419fbb3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4a04896dfb569893fba50729314024f5_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4a04896dfb569893fba50729314024f5_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4a04896dfb569893fba50729314024f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4ac6d3aa8e1c3a53e6aa7fc55759df51_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4b297191fa254f84c021e73b3b79e860_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4b2dd266b605b2f31a8759f802637301_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4b2dd266b605b2f31a8759f802637301_img.jpg deleted file mode 100644 index e46b4a1f7945a4182d1a5ef891ec5f6f10fef17f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4b2dd266b605b2f31a8759f802637301_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9f4112a7b33c3469baf666068de311007d84f2106ca714dccb49217f0aedf1c9 -size 22129 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4b81ac66c571b3118659e4d9f47abb22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index 41e3870380037e7c442e703303e85a207c149a9e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4db00373eb0bec04341ee887235bbfea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f7a7bba3177faf97967936ef45e1884f92ebc90d289a8773473b1ddd4c20ff99 -size 4017 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index aa4fc36c4c8bf48a8ab8cfc59a037754e9a3e345..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7638bce3b4638f509f92537e0b032492d41b72de31fafe79b06a3d220c31ef89 -size 3958 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/5009e30a55479d3941af523871208f9d_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/5009e30a55479d3941af523871208f9d_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/5009e30a55479d3941af523871208f9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg deleted file mode 100644 index 41e3870380037e7c442e703303e85a207c149a9e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/51878675eb6a813e99b9fe26951bd5cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f7a7bba3177faf97967936ef45e1884f92ebc90d289a8773473b1ddd4c20ff99 -size 4017 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/52a225f71b166b0c65c2f29f32a79f7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/53c9adf3dd12b16e2b9f70350cdcbdf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/56ac11fb9683d7b846fb65c845d80f22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/59368942873b0c35eef79a7a985025dc_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/59368942873b0c35eef79a7a985025dc_img.jpg deleted file mode 100644 index 058fd35f78c40c0a753a06371d66602bf857585f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/59368942873b0c35eef79a7a985025dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1dea13c566ccbf8f8dc61e08403e9c15d6737fa3a2e5e03e0e3f9d05c5948d59 -size 4017 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/59fcc0e3699f239444841881a2e75da0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index 8d4af7af6f97ed9d06f4202eedc3fb3669b12033..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3819c22741753857d090b72b5497407df3e246ab79514e2c140d5af1c8bcc7 -size 3887 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg deleted file mode 100644 index 022e87bb71372a7b6538215f2499319d726c6c51..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/60d6a326e6061d71ea69c9375ec96631_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a9ff00a222f00dccfb1d05935f62869d2fc3b19ae53459cec9615bdf7fa2fce8 -size 3875 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/60e345365fd1e52e01c91e3fd3cc6515_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6588b1c7f14069d96744b473ad663248_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/681c354e00e1c0fe098ba665ff155cb8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6b0834ca8cdd18832ed461378d51dcb7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6c6024603c6fd57b23210b79f573b3bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6c8a96787f532bd1fa4719e738cf556f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6f20bcd5fdff11e5d65b3d8b5d84fc3b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg deleted file mode 100644 index 8d4af7af6f97ed9d06f4202eedc3fb3669b12033..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/6ff798305e82bdf8233f1381ff9f7c49_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3819c22741753857d090b72b5497407df3e246ab79514e2c140d5af1c8bcc7 -size 3887 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg deleted file mode 100644 index 07b334e77600cfa816084f09a5ee2b5c80b554a0..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c85c3dc30d47dfedb5afcf7ad2844d6c688a5d81c428ba151b691c98b38fb57c -size 174924 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/728298e0fbc8de5f3894ce6cb10fb413_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 8d4af7af6f97ed9d06f4202eedc3fb3669b12033..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3819c22741753857d090b72b5497407df3e246ab79514e2c140d5af1c8bcc7 -size 3887 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index 9521bc0068649c1df30945e1661689082c9fbec5..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/79898de98da3367d0ea9beef38f5c01c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a0e6778892783df8645cfbb6f3a56c196c45d4b973c1653ca680f8ce74012fbb -size 3889 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7a3d4c97055e3021cefb0c5850050bff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7c66f12495a47e87f0a0314a0d3a2eff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index a2bfb15dee6061ea5a407e7b56321cf2cfe7b8bf..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b88fd87b104feab9f2bba6332d24d3c92b6f77c696213a1bbce789b7b81fae15 -size 3872 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg deleted file mode 100644 index 41e3870380037e7c442e703303e85a207c149a9e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/7f4320cee12fc1dbb865cc6b67462a91_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f7a7bba3177faf97967936ef45e1884f92ebc90d289a8773473b1ddd4c20ff99 -size 4017 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/81b34087cd6755a80f84a70cf28fba82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8237c46643affc7cc057ae950dbcf1f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index aa4fc36c4c8bf48a8ab8cfc59a037754e9a3e345..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/829cdaf00f7219d70e571064b2b13291_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7638bce3b4638f509f92537e0b032492d41b72de31fafe79b06a3d220c31ef89 -size 3958 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/83a07943a0cfe37fc5e9fa09d9f7afc1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index 022e87bb71372a7b6538215f2499319d726c6c51..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a9ff00a222f00dccfb1d05935f62869d2fc3b19ae53459cec9615bdf7fa2fce8 -size 3875 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/854df8ad60507803253274673f9062cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 022e87bb71372a7b6538215f2499319d726c6c51..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a9ff00a222f00dccfb1d05935f62869d2fc3b19ae53459cec9615bdf7fa2fce8 -size 3875 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8b4befaffc5166da571069410e207aea_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8b4befaffc5166da571069410e207aea_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8b4befaffc5166da571069410e207aea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8e0160fd55391f6f2bbdef38ceb6f823_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg deleted file mode 100644 index aa4fc36c4c8bf48a8ab8cfc59a037754e9a3e345..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8fa517d2ddade6ee8fc26d015f1fc59a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7638bce3b4638f509f92537e0b032492d41b72de31fafe79b06a3d220c31ef89 -size 3958 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/8fbe9e67b51710384633b6407d60420d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/90183a52275501da5a0fd5c63d837009_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/90183a52275501da5a0fd5c63d837009_img.jpg deleted file mode 100644 index f45963bb7b63ef0f0a9037f2030064e49a482d95..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/90183a52275501da5a0fd5c63d837009_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d5d2f9a0911170b38d901d61a6e220fc13bdc1aa0a1a29057bd16476380c8186 -size 51873 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9159d999b6514420a64eae80e52f1fd5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/970a901d8e537da4b6ff719d8931912f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/990afa9d07fb81cf8760867cb4247a79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9a2aa33c5d905f8a0646278a48a2e565_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index fcc8de3880c83dd858faea9d2d670e19b6fd72d2..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a988b79737893a992c835186be603cd3a1175db327506e447f177abdaf177a58 -size 3874 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg deleted file mode 100644 index 058fd35f78c40c0a753a06371d66602bf857585f..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/9c7046c19fb32a2d21ac26f5e90a7098_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1dea13c566ccbf8f8dc61e08403e9c15d6737fa3a2e5e03e0e3f9d05c5948d59 -size 4017 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a28ab03366399b5e0a61445bc57e3724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a2d3f917a06e0fe4b7c7158ab115aa1b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a5481fd31c02b525617e70f2de357039_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a5481fd31c02b525617e70f2de357039_img.jpg deleted file mode 100644 index 7bb61480a34514a95730955e5581295cd9259bd9..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a5481fd31c02b525617e70f2de357039_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0aaca40756d43fdd98826e1672441d241b27c0c503786caa46f2775c1033c262 -size 61429 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index 9521bc0068649c1df30945e1661689082c9fbec5..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a0e6778892783df8645cfbb6f3a56c196c45d4b973c1653ca680f8ce74012fbb -size 3889 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a86a27f2fcb9b8a773abf2a2a97f9592_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/a9bb99d15f54792e1c9a14b1e465369a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/aa05feb33e250a75136ea52816d3c19a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg deleted file mode 100644 index 8d4af7af6f97ed9d06f4202eedc3fb3669b12033..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/ac6d1fa092b8fd6a0e4aefa65ffd54c8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3819c22741753857d090b72b5497407df3e246ab79514e2c140d5af1c8bcc7 -size 3887 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/acfb2707966cd2618f2dc86b1a02702c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/aef4390a4629604196222b9ed006a786_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/aef4390a4629604196222b9ed006a786_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/aef4390a4629604196222b9ed006a786_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/b8c4f98c3dd7c229927bf91a5e96c0ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/bb9f586190c7197099d25db7df9050af_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/bb9f586190c7197099d25db7df9050af_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/bb9f586190c7197099d25db7df9050af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 4af59d8e8aa00d083b9a628182c7344a716c8921..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e2d947f60c9c61fa962852f91d7777af08a177160dd8c6167724ef5000c99755 -size 3958 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/c521036a3eb59673388f5e034f4e6c9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/c5538ac451af9d74926b82278f11fb87_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg deleted file mode 100644 index 41e3870380037e7c442e703303e85a207c149a9e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/cb8f0521a69f168a06222045bea81a86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f7a7bba3177faf97967936ef45e1884f92ebc90d289a8773473b1ddd4c20ff99 -size 4017 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/ce5e18b28bd9714a4cc8d8fe7546cecd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d0516b99882398c64c90f71c12e808e2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d1ec9820fe8d23d83e066389a9cd7338_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg deleted file mode 100644 index 8d4af7af6f97ed9d06f4202eedc3fb3669b12033..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d2c29dfabebacb6f853683a6c3759320_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3819c22741753857d090b72b5497407df3e246ab79514e2c140d5af1c8bcc7 -size 3887 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d35a80e3faed208324083399568c7461_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d35a80e3faed208324083399568c7461_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d35a80e3faed208324083399568c7461_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg deleted file mode 100644 index 022e87bb71372a7b6538215f2499319d726c6c51..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d4135b58ef709033f4a5dc0f5cc3abd2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a9ff00a222f00dccfb1d05935f62869d2fc3b19ae53459cec9615bdf7fa2fce8 -size 3875 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg deleted file mode 100644 index 8d4af7af6f97ed9d06f4202eedc3fb3669b12033..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d597715604d00e1ab3b00cc3f16e59de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f3819c22741753857d090b72b5497407df3e246ab79514e2c140d5af1c8bcc7 -size 3887 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/d96da198567c411a05faab4ce5b4e58c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index 022e87bb71372a7b6538215f2499319d726c6c51..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a9ff00a222f00dccfb1d05935f62869d2fc3b19ae53459cec9615bdf7fa2fce8 -size 3875 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/dbd230eafb5429741c22c2f7293118af_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/dd94fe110cdb6fbaaf0d9f47492655d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg deleted file mode 100644 index 5573e6eb8e16d8b6dcd2ab04900f1bbadca2db92..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/df495bddeb5d8826c7571714e6db1478_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:07d85c8d8455dd1d432a4c876a9c5e5e32c2db3b125b5d1da4dc3597c9a89213 -size 3895 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e010d665d27407ff5e238d1c45c1c98f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e06de71ced5f7c5e97414f01f39d550c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e1d97826df530020bf86c791d8c7d724_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e374c531ea6c45899ce8ec331e437bd1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e3b551138548092502c92a99ebfdb7bc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 5573e6eb8e16d8b6dcd2ab04900f1bbadca2db92..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:07d85c8d8455dd1d432a4c876a9c5e5e32c2db3b125b5d1da4dc3597c9a89213 -size 3895 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index aa4fc36c4c8bf48a8ab8cfc59a037754e9a3e345..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7638bce3b4638f509f92537e0b032492d41b72de31fafe79b06a3d220c31ef89 -size 3958 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e6eb959227f4726d42277c0f920bedbc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e87df69ebd4cd2dbbf6749079e6c057a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/e882a6bdfd0e868314f3a26f536145a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/eb08b089f7e59a7e96a8b3c146668d6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f3d768b0299c4763bc703b606391c48b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f74adaa1840504407cd4272995426f82_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f74adaa1840504407cd4272995426f82_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f74adaa1840504407cd4272995426f82_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg deleted file mode 100644 index 022e87bb71372a7b6538215f2499319d726c6c51..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f7dbd497160f02888f34fdf243648aa2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a9ff00a222f00dccfb1d05935f62869d2fc3b19ae53459cec9615bdf7fa2fce8 -size 3875 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f80b58b972f3d6b74a5efe2bf1e0ba4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f929e9fcf3f37d82af20f84f9c8b942a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/f9b17af787dbdc9711539cd71df3d782_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/facce731b2dbfae43a8609231a700be1_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/facce731b2dbfae43a8609231a700be1_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/facce731b2dbfae43a8609231a700be1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 868e0727111a4272151525b2c0599e8a48739416..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a67b2c6d89bc5bd83148806429c072baf105603ad92d64fe028879b57ede1e94 -size 3930 diff --git a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index e5ef8b5bc386805b18bf57a27a51a92dd4a5854e..0000000000000000000000000000000000000000 --- a/files/WG6/O-RAN.WG6.TS.O2IMS-INTERFACE-R005-v11.00/images/ff748955b94dcb8337283fbe12baa475_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0df777ab11f4b5abd60c301d0a23363adba8be905c604b7d79b18c0cd19a8a79 -size 3877 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/doc.md b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/doc.md deleted file mode 100644 index 41285078bb0ee330eb3f1cfd21f661e90b305896..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/doc.md +++ /dev/null @@ -1,3365 +0,0 @@ - - -# **O-RAN White Box Hardware Working Group Hardware Reference Design Specification for Outdoor Micro Cell with Split Architecture Option 7.2** --- - -Copyright © 2023 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., Buschkauer Weg 27, 53347 Alfter, Germany - -1 - -# Revision History - -| Date | Revision | Author | Description | -|------------|----------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 11/11/2025 | V05.00 | WG7 | Addition of SDR SoC Reference design in 2.3.3 | -| 02/15/2023 | v04.00 | WG7 | Addition of Optional Die to Die Interfacing in 2.3.2.3 | -| 06/22/2022 | v03.00 | WG7 | Expanded chapter 2.3.7 to include detailed information on thermal design. Added chapter 2.3.2.3 to provide details of optional internal interfaces within an O-RU. Updated header and footers. | -| 07/21/2021 | v02.00 | WG7 | Add normative and informative notification to scope. | -| 02/03/2021 | v01.00 | WG7 | First Published Version | - -2 - -3 - -# Contents - -| | | | -|----|---------------------------------------------------------------------|----| -| 1 | Contents | | -| 2 | Revision History..... | 2 | -| 3 | Tables ..... | 7 | -| 4 | Figures..... | 8 | -| 5 | Chapter 1 Introductory Material..... | 10 | -| 6 | 1.1 Scope..... | 10 | -| 7 | 1.2 References..... | 10 | -| 8 | 1.3 Definitions and Abbreviations ..... | 12 | -| 9 | 1.3.1 Definitions ..... | 12 | -| 10 | 1.3.2 Abbreviations ..... | 12 | -| 11 | Chapter 2 Hardware Reference Design 1 ..... | 17 | -| 12 | 2.1 O-CU Hardware Reference Design..... | 17 | -| 13 | 2.2 O-DU 7-2 Hardware Reference Design..... | 17 | -| 14 | 2.2.1 O-DU 7-2 High-Level Functional Block Diagram ..... | 18 | -| 15 | 2.2.2 O-DU 7-2 Hardware Design Description..... | 18 | -| 16 | 2.2.3 O-DU 7-2 Hardware Components..... | 19 | -| 17 | 2.2.3.1 Digital Processing Unit..... | 19 | -| 18 | 2.2.3.1.1 Digital Processing Unit Requirements..... | 19 | -| 19 | 2.2.3.1.1.1 Interfaces ..... | 20 | -| 20 | 2.2.3.1.1.1.1 Memory Channel Interfaces ..... | 20 | -| 21 | 2.2.3.1.1.1.2 PCIe ..... | 20 | -| 22 | 2.2.3.1.1.1.3 Ethernet..... | 20 | -| 23 | 2.2.3.1.2 Digital Processing Unit Design..... | 20 | -| 24 | 2.2.3.2 Hardware Accelerator..... | 21 | -| 25 | 2.2.3.2.1 Accelerator Design Solution 1 ..... | 21 | -| 26 | 2.2.3.2.1.1 Accelerator Requirements ..... | 21 | -| 27 | 2.2.3.2.1.2 Accelerator Design..... | 23 | -| 28 | 2.2.3.2.2 Accelerator Design Solution 2 ..... | 23 | -| 29 | 2.2.3.2.2.1 Accelerator Requirement..... | 24 | -| 30 | 2.2.3.2.2.2 Accelerator Design..... | 24 | -| 31 | 2.2.3.2.3 Accelerator Design Solution 3 ..... | 25 | -| 32 | 2.2.3.2.3.1 Accelerator Hardware Features..... | 25 | -| 33 | 2.2.3.2.3.2 Hardware Accelerator Firmware Features..... | 26 | -| 34 | 2.2.3.2.4 Accelerator Design Solution 4 ..... | 27 | -| 35 | 2.2.3.2.4.1 Accelerator Hardware Features..... | 27 | -| 36 | 2.2.3.2.4.2 Hardware Accelerator Firmware Features..... | 28 | -| 37 | 2.2.3.2.5 Accelerator Design Solution 5 ..... | 28 | -| 38 | 2.2.3.2.5.1 Accelerator Requirements ..... | 29 | -| 39 | 2.2.3.2.5.2 Accelerator Design..... | 29 | -| 40 | 2.2.3.3 Baseboard Management Controller ..... | 30 | -| 41 | 2.2.4 Synchronization and Timing ..... | 31 | -| 42 | 2.2.4.1 Synchronization and Timing Design 1 ..... | 31 | -| 43 | 2.2.4.2 Hardware Requirements ..... | 31 | - -1       2.2.4.3       Hardware Design ..... 31 - -2       2.2.5       External Interface Ports ..... 31 - -3       2.2.5.1       Hardware Requirements ..... 31 - -4       2.2.5.2       Hardware Design ..... 32 - -5       2.2.6       O-DU Firmware..... 32 - -6       2.2.7       Mechanical ..... 32 - -7       2.2.7.1       Mother Board..... 32 - -8       2.2.7.2       Chassis ..... 33 - -9       2.2.7.3       Cooling ..... 34 - -10       2.2.8       Power Unit..... 34 - -11       2.2.8.1       Hardware Requirements ..... 34 - -12       2.2.8.2       Hardware Design ..... 35 - -13       2.2.9       Thermal..... 35 - -14       2.2.10       Environmental and Regulations ..... 35 - -15       2.3       O-RU7.2 Hardware Reference Design ..... 36 - -16       2.3.1       O-RU7.2 High-Level Functional Block Diagram..... 36 - -17       2.3.2       O-RU7.2 Hardware for FPGA Based Design..... 36 - -18       2.3.2.1       Digital Processing Unit..... 39 - -19       2.3.2.1.1       FPGA/ASIC Solution..... 40 - -20       2.3.2.1.1.1       FPGA Specifications ..... 40 - -21       2.3.2.1.1.2       FPGA Design ..... 41 - -22       2.3.2.2       RF Processing Unit..... 42 - -23       2.3.2.2.1       Transceiver Reference Design ..... 42 - -24       2.3.2.2.1.1       Hardware Specifications..... 42 - -25       2.3.2.2.1.1.1       Interface ..... 42 - -26       2.3.2.2.1.1.2       Algorithm..... 44 - -27       2.3.2.2.1.1.3       Device Configuration..... 44 - -28       2.3.2.2.1.1.4       Power Dissipation..... 44 - -29       2.3.2.2.1.1.5       RF Specifications..... 44 - -30       2.3.2.2.1.2       Hardware Design..... 47 - -31       2.3.2.2.2       Power Amplifier (PA) Reference Design ..... 48 - -32       2.3.2.2.2.1       Hardware Specifications..... 48 - -33       2.3.2.2.2.1.1       Interface ..... 48 - -34       2.3.2.2.2.1.2       Power Specifications ..... 48 - -35       2.3.2.2.2.1.3       RF Specifications..... 48 - -36       2.3.2.2.2.2       Hardware Design..... 48 - -37       2.3.2.2.3       Low Noise Amplifier (LNA) Reference Design ..... 49 - -38       2.3.2.2.3.1.1       Interface ..... 49 - -39       2.3.2.2.3.1.2       Power Specifications ..... 49 - -40       2.3.2.2.3.1.3       RF Performance Specifications ..... 50 - -41       2.3.2.2.3.2       Hardware Design..... 50 - -42       2.3.2.2.4       Circulator Reference Design ..... 50 - -43       2.3.2.2.4.1       Hardware Specifications..... 50 - -44       2.3.2.2.4.1.1       Interface ..... 50 - -45       2.3.2.2.4.1.2       RF Specifications..... 51 - -46       2.3.2.2.4.2       Hardware Design..... 51 - -| | | | | -|----|---------------|-----------------------------------------------------------------------|----| -| 1 | 2.3.2.2.5 | Antenna / Phased Array Reference Design..... | 51 | -| 2 | 2.3.2.2.5.1 | Hardware Specifications for Omnidirectional Antenna ..... | 51 | -| 3 | 2.3.2.2.5.1.1 | Hardware Design for Omnidirectional Antenna..... | 52 | -| 4 | 2.3.2.2.5.2 | Hardware Specifications for Directional Antenna ..... | 52 | -| 5 | 2.3.2.2.5.2.1 | Hardware Design for Directional Antenna..... | 53 | -| 6 | 2.3.2.3 | Internal Interfaces ..... | 54 | -| 7 | 2.3.2.3.1 | Optional JES204 Interfacing ..... | 54 | -| 8 | 2.3.2.3.2 | Optional Die to Die Interfacing..... | 59 | -| 9 | 2.3.3 | O-RU 7-2 Hardware Components for SDR SoC based Design..... | 61 | -| 10 | 2.3.3.1 | Digital Processing Unit..... | 62 | -| 11 | 2.3.3.2 | RF Processing Unit..... | 62 | -| 12 | 2.3.3.2.1 | Transceiver RFIC Reference Design ..... | 63 | -| 13 | 2.3.3.2.2 | Power Amplifier (PA) Reference Design ..... | 64 | -| 14 | 2.3.3.2.3 | Directional Coupler..... | 66 | -| 15 | 2.3.3.2.4 | Circulator..... | 67 | -| 16 | 2.3.3.2.5 | Band Pass Filter..... | 69 | -| 17 | 2.3.3.2.6 | Low Noise Amplifier (LNA) Reference Design..... | 70 | -| 18 | 2.3.3.2.7 | RF Switch Reference Design ..... | 71 | -| 19 | 2.3.3.2.8 | Antenna Reference Design..... | 73 | -| 20 | 2.3.4 | Synchronization and Timing ..... | 73 | -| 21 | 2.3.4.1 | Hardware Specifications ..... | 74 | -| 22 | 2.3.4.1.1 | Interface..... | 74 | -| 23 | 2.3.4.1.2 | Performance Specifications..... | 74 | -| 24 | 2.3.4.1.3 | Synchronizer ..... | 74 | -| 25 | 2.3.4.1.3.1 | Hardware Specifications..... | 74 | -| 26 | 2.3.4.1.3.1.1 | Interface ..... | 74 | -| 27 | 2.3.4.1.3.1.2 | Performance Specifications ..... | 75 | -| 28 | 2.3.4.1.3.2 | Hardware Design..... | 75 | -| 29 | 2.3.4.1.4 | Reference Synthesizer..... | 75 | -| 30 | 2.3.4.1.4.1 | Hardware Specifications..... | 76 | -| 31 | 2.3.4.1.4.1.1 | Interface ..... | 76 | -| 32 | 2.3.4.1.4.1.2 | Performance Specifications ..... | 76 | -| 33 | 2.3.4.1.4.2 | Hardware Design..... | 77 | -| 34 | 2.3.4.2 | Hardware Design ..... | 77 | -| 35 | 2.3.5 | External Interface Ports ..... | 77 | -| 36 | 2.3.5.1 | Hardware Specifications..... | 77 | -| 37 | 2.3.5.2 | Hardware Design ..... | 78 | -| 38 | 2.3.5.2.1 | Fronthaul Interface ..... | 78 | -| 39 | 2.3.5.2.2 | Debug Interface ..... | 78 | -| 40 | 2.3.5.2.3 | Power Interface ..... | 79 | -| 41 | 2.3.5.2.4 | RF Interface..... | 79 | -| 42 | 2.3.6 | Mechanical ..... | 80 | -| 43 | 2.3.7 | Power Unit..... | 81 | -| 44 | 2.3.7.1 | Hardware Specifications ..... | 81 | -| 45 | 2.3.7.2 | Hardware Design ..... | 82 | -| 46 | 2.3.8 | Thermal..... | 82 | - -1 2.3.9 Environmental and Regulations ..... 84 - -2 2.4 Integrated O-DU & O-RU (gNB-DU) Reference Design..... 85 - -3 2.4.1 O-DU Portion of Integrated Reference Design ..... 85 - -4 2.4.1.1 O-DU High-Level Functional Block Diagram ..... 85 - -5 2.4.1.2 O-DU Hardware Components ..... 85 - -6 2.4.1.2.1 Digital Processing Unit ..... 85 - -7 2.4.1.2.2 Hardware Accelerator (if required by design) ..... 85 - -8 2.4.1.2.2.1 Accelerator Design 1 ..... 85 - -9 2.4.1.2.2.2 Accelerator Design 2 ..... 85 - -10 2.4.1.3 Synchronization and Timing..... 85 - -11 2.4.2 O-RU Portion of Integrated Reference Design ..... 85 - -12 2.4.2.1 O-RU High-Level Functional Block Diagram ..... 85 - -13 2.4.2.2 O-RU Hardware Components..... 85 - -14 2.4.2.2.1 Digital Processing Unit ..... 85 - -15 2.4.2.2.2 RF Processing Unit ..... 85 - -16 2.4.2.2.2.1 Transceiver Reference Design..... 85 - -17 2.4.2.2.2.2 Power Amplifier (PA) Reference Design..... 85 - -18 2.4.2.2.2.3 Low Noise Amplifier (LNA) Reference Design ..... 85 - -19 2.4.2.2.2.4 RF Switch Reference Design..... 85 - -20 2.4.2.2.2.5 Antenna / Phased Array Reference Design ..... 85 - -21 2.4.2.2.3 Synchronization and Timing ..... 85 - -22 2.4.3 External Interface Ports ..... 85 - -23 2.4.4 O-DU/O-RU Firmware (if required by design)..... 85 - -24 2.4.5 Mechanical ..... 85 - -25 2.4.6 Power Unit..... 85 - -26 2.4.7 Thermal..... 86 - -27 2.4.8 Environmental and Regulations ..... 86 - -28 2.5 Integrated O-CU & O-DU Reference Design ..... 86 - -29 2.5.1 O-CU Portion of Integrated Reference Design ..... 86 - -30 2.5.1.1 Integrated O-CU High-Level Functional Block Diagram ..... 86 - -31 2.5.1.2 O-CU Hardware Components..... 86 - -32 2.5.1.2.1 Digital Processing Unit ..... 86 - -33 2.5.1.2.2 Hardware Accelerator (if required by design) ..... 86 - -34 2.5.1.2.2.1 Accelerator Design 1 ..... 86 - -35 2.5.1.2.2.2 Accelerator Design 2 ..... 86 - -36 2.5.1.3 Synchronization and Timing..... 86 - -37 2.5.1.4 O-CU Firmware (if required by design) ..... 86 - -38 2.5.2 O-DU Portion of Hardware Reference Design..... 86 - -39 2.5.2.1 O-DU High-Level Functional Block Diagram ..... 86 - -40 2.5.2.2 O-DU Hardware Components ..... 86 - -41 2.5.2.2.1 Digital Processing Unit ..... 86 - -42 2.5.2.2.2 Hardware Accelerator (if required by design) ..... 86 - -43 2.5.2.2.2.1 Accelerator Design 1 ..... 86 - -44 2.5.2.2.2.2 Accelerator Design 2 ..... 86 - -45 2.5.2.3 Synchronization and Timing..... 86 - -46 2.5.3 External Interface Ports ..... 86 - -1 2.5.4 O-DU Firmware..... 86 - 2 2.5.5 Mechanical ..... 86 - 3 2.5.6 Power Unit..... 87 - 4 2.5.7 Thermal..... 87 - 5 2.5.8 Environmental and Regulations ..... 87 - 6 2.6 FHGW Hardware Reference Design..... 87 - 7 2.6.1 FHGW High-Level Functional Block Diagram ..... 87 - 8 2.6.2 FHGW Hardware Components ..... 87 - 9 2.6.2.1 Digital Processing Unit..... 87 - 10 2.6.3 Synchronization and Timing ..... 87 - 11 2.6.4 External Interface Ports ..... 87 - 12 2.6.5 Mechanical ..... 87 - 13 2.6.6 Power..... 87 - 14 2.6.7 Thermal..... 87 - 15 2.6.8 Environmental ..... 87 - 16 Annex 1: Parts Reference List..... 87 - 17 Annex 1.1 O-CU Reference Parts List..... 87 - 18 Annex 1.2 O-DU7-2 Reference Parts List ..... 88 - 19 Annex 1.3 O-RU7-2 Reference Parts List ..... 88 - 20 Annex 1.4 SDR SoC based O-RU7-2 Reference Parts List..... 89 - 21 - -# --- 22 Tables - -23 Table 2.2.3-1 Processor Feature List..... 20 - 24 Table 2.2.3-2 Memory Channel Feature List ..... 20 - 25 Table 2.2.3-3 Accelerator Hardware Feature List..... 22 - 26 Table 2.2.3-4 Accelerator Firmware Feature List ..... 22 - 27 Table 2.2.3-5 Accelerator Hardware Feature List..... 24 - 28 Table 2.2.3-6 Accelerator Firmware Feature List ..... 24 - 29 Table 2.2.3-7 Accelerator Hardware Features ..... 25 - 30 Table 2.2.3-8 Hardware Accelerator Firmware Features ..... 26 - 31 Table 2.2.3-9 Accelerator Hardware Features ..... 27 - 32 Table 2.2.3-10 Hardware Accelerator Firmware Features ..... 28 - 33 Table 2.2.3-11 Accelerator Hardware Feature List] ..... 29 - 34 Table 2.2.3-12 Accelerator Firmware Feature List..... 29 - 35 Table 2.2.5-1 External Port List..... 32 - 36 Table 2.2.8-1 Power Supply Rail Requirements ..... 34 - 37 Table 2.2.8-2 Power Supply Unit Feature List ..... 35 - 38 Table 2.2.10-1 Environmental Features ..... 35 - 39 Table 2.3.2-1 FPGA Interface Specifications ..... 41 - 40 Table 2.3.2-2 FPGA Functional Blocks ..... 42 - 41 Table 2.3.2-3 RF Processing Unit Interface Specifications ..... 42 - -1 Table 2.3.2-4 JESD204B/C Serial Data Rates ..... 44 - -2 Table 2.3.2-5 Transceiver RF Specifications ..... 44 - -3 Table 2.3.2-6 Power Amplifier Interface Specifications..... 48 - -4 Table 2.3.2-7 Power Amplifier RF Specifications..... 48 - -5 Table 2.3.2-8 LNA Interfaces ..... 49 - -6 Table 2.3.2-9 LNA RF Specifications..... 50 - -7 Table 2.3.2-10 Circulator Specifications..... 51 - -8 Table 2.3.2-11 Omnidirectional Antenna Specifications ..... 52 - -9 Table 2.3.2-12 Directional Antenna Specifications ..... 53 - -10 Table 2.3.2-13 JESD204 Abridged Lexicon ..... 55 - -11 Table 2.3.3-1 Synchronization and Timing Interface Specifications..... 74 - -12 Table 2.3.3-2 Synchronizer Interface Specifications ..... 74 - -13 Table 2.3.3-3 Synchronizer Performance Specifications ..... 75 - -14 Table 2.3.3-4 Synthesizer Interface Specifications..... 76 - -15 Table 2.3.3-5 TCXO Clock Performance Specifications..... 76 - -16 Table 2.3.4-1 External Port List..... 77 - -17 Table 2.3.6-1 Transceiver Module Specifications ..... 81 - -18 Table 2.3.6-2 RF Front End Module Specifications ..... 82 - -19 Table 2.3.7-1 Thermal Conductivity of common Metals [13] ..... 82 - -20 Table 2.3.7-2 Convective heat transfer coefficient [14]..... 83 - -21 Table 2.3.8-1 Environmental Features ..... 84 - -22 - -# 23 **Figures** - -24 Figure 2.2.1-1 O-DU7.2 Functional Block Diagram..... 18 - -25 Figure 2.2.2-1 O-DU7.2 Hardware Block Diagram ..... 19 - -26 Figure 2.2.3-1 Accelerator Design 1 without optional NIC Device..... 23 - -27 Figure 2.2.3-2 Accelerator Design 1 with optional NIC Device..... 23 - -28 Figure 2.2.3-3 Structured ASIC Accelerator Design ..... 24 - -29 Figure 2.2.3-4 Dual-chip FPGA-based Hardware Acceleration in O-DU7.2..... 26 - -30 Figure 2.2.3-5 Single-chip FPGA-based Hardware Acceleration in O-DU7.2 ..... 28 - -31 Figure 2.2.3-6 Accelerator Design Using PCIe..... 30 - -32 Figure 2.2.3-7 Accelerator Design Using Ethernet..... 30 - -33 Figure 2.2.4-1 O-DU Timing Synchronization ..... 31 - -34 Figure 2.2.5-1 External Interface Reference Design..... 32 - -35 Figure 2.2.7-1 Mother Board Layout Diagram ..... 33 - -36 Figure 2.2.7-2 Chassis Mechanical Diagram ..... 34 - -37 Figure 2.3.1-1 High-Level Functional Block Diagram..... 36 - -38 Figure 2.3.2-1 4T4R General Block Diagram with full RF front end..... 37 - -39 Figure 2.3.2-2 8T8R General Block Diagram with RF front end ..... 38 - -40 Figure 2.3.2-3 O-RU Architecture Example Implementation 1 ..... 39 - -1 Figure 2.3.2-4 Digital Processing Unit Block Diagram (L1 Processing + optional Beamforming)..... 40 - -2 Figure 2.3.2-5 Digital Processing Unit Block Diagram (DFE)..... 40 - -3 Figure 2.3.2-6 Transceiver with Integrated CFR and DPD ..... 47 - -4 Figure 2.3.2-7 Power Amplifier Reference Design..... 49 - -5 Figure 2.3.2-8 LNA Reference Design ..... 50 - -6 Figure 2.3.2-9 Circulator Reference Design ..... 51 - -7 Figure 2.3.2-10 Canister Style Omni Antenna..... 52 - -8 Figure 2.3.2-11 Mounting arrangement scenario 1 of 4T4R radios on the back of Directional Antenna ..... 53 - -9 Figure 2.3.2-12 Mounting arrangement scenario 2 of 4T4R radios remotely mounted with Directional - -10 Antenna ..... 54 - -11 Figure 2.3.2-13 Example 4T4R JESD204 Configuration ..... 56 - -12 Figure 2.3.2-14 4T4R Example Data Mapping..... 57 - -13 Figure 2.3.2-15 Example 8T8R JESD204 Configuration ..... 58 - -14 Figure 2.3.2-16 8T8R Example Data Mapping..... 59 - -15 Figure 2.3.17-1 Basic die-to-die parallel architecture..... 59 - -16 Figure 2.3.3-1 Clock and Synchronization Functional Block Diagram..... 73 - -17 Figure 2.3.3-2 Synchronizer Block Diagram ..... 75 - -18 Figure 2.3.3-3 Synthesizer Block Diagram..... 77 - -19 Figure 2.3.4-1 SFP+ case and connector..... 78 - -20 Figure 2.3.4-2 RJ45 Interface..... 78 - -21 Figure 2.3.4-3 Power Interface..... 79 - -22 Figure 2.3.4-4 (a) 4.3-10+ RF Connector [9] [11] (b) M-LOC cluster/multiport connector [12] ..... 79 - -23 Figure 2.3.5-1 Mechanical Enclosure Side View..... 80 - -24 Figure 2.3.5-2 Mechanical Enclosure End View ..... 81 - -25 Figure 2.3.6-1 Power Reference Design ..... 82 - -26 - -27 - -# Chapter 1 Introductory Material - -## 1.1 Scope - -This Technical Specification has been produced by the O-RAN.org. - -The contents of the present document are subject to continuing work within O-RAN WG7 and may change following formal O-RAN approval. Should the O-RAN.org modify the contents of the present document, it will be re-released by O-RAN Alliance with an identifying change of release date and an increase in version number as follows: - -Release x.y.z - -where: - -x the first digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. (the initial approved document will have x=01). - -y the second digit is incremented when editorial only changes have been incorporated in the document. - -z the third digit included only in working versions of the document indicating incremental changes during the editing process. This variable is for internal WG7 use only. - -The present document specifies system requirements and high-level architecture for the Outdoor Micro Cell for FR1 deployment scenario as specified in the Deployment Scenarios and Base Station Classes document [1]. - -In the main body of this specification (in any “chapter”) the information contained therein is informative, unless explicitly described as normative. Information contained in an “Annex” to this specification is always informative unless otherwise marked as normative. - -## 1.2 References - -The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - -[1] ORAN-WG7.DSC.0-V02.00 Technical Specification, ‘Deployment Scenarios and Base Station Classes for White Box Hardware’. - -[2] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". - -[3] 3GPP TR 38.104: "NR; Base Station (BS) radio transmission and reception". -[http://www.3gpp.org/ftp/Specs/archive/38\\_series/38.104/38104-g10.zip](http://www.3gpp.org/ftp/Specs/archive/38_series/38.104/38104-g10.zip) - -[4] ORAN-WG4.CUS.0-v05.00 Technical Specification, ‘O-RAN Fronthaul Working Group Control, User and Synchronization Plane Specification’. - -- 1 [5] 3GPP TS 38.113:"NR: Base Station (BS) Electromagnetic Compatibility (EMC)". -2 [http://www.3gpp.org/ftp/Specs/archive/38\\_series/38.113/38113-f80.zip](http://www.3gpp.org/ftp/Specs/archive/38_series/38.113/38113-f80.zip) -- 3 [6] ORAN-WG7.OMC. HAR-v01.00 Technical Specification, 'Outdoor Micro Cell Hardware Architecture -4 and Requirement (FR1) Specification'. . -- 5 [7] "Data Plane Development Kit", -- 6 [8] "Baseband Device Library", [https://doc.dpdk.org/guides/prog\\_guide/bbdev.html](https://doc.dpdk.org/guides/prog_guide/bbdev.html). -- 7 [9] IEC 61169-54 International Standard, "Radio frequency connectors – Part 54: Sectional specification for -8 coaxial connectors with 10 mm inner diameter of outer conductor, nominal characteristic impedance 50 Ohms, -9 Series 4.3-10", -- 10 [10] AISG 2.0, "Control interface for antenna line devices", Antenna Interface Standards Group, June 2006. -- 11 [11] -12 [https://www.rosenberger.com/0\\_documents/de/catalogs/ba\\_communication/catalog\\_coax/15\\_Chapter\\_43-](https://www.rosenberger.com/0_documents/de/catalogs/ba_communication/catalog_coax/15_Chapter_43-10_41-95.pdf) -13 [10\\_41-95.pdf](https://www.rosenberger.com/0_documents/de/catalogs/ba_communication/catalog_coax/15_Chapter_43-10_41-95.pdf) (Accessed on March 30, 2022) -- 14 [12] [https://www.commScope.com/product-type/cable-assemblies/wireless-cable-assemblies/coaxial-cable-](https://www.commScope.com/product-type/cable-assemblies/wireless-cable-assemblies/coaxial-cable-assemblies/itemmloc-flxm-4) -15 [assemblies/itemmloc-flxm-4](https://www.commScope.com/product-type/cable-assemblies/wireless-cable-assemblies/coaxial-cable-assemblies/itemmloc-flxm-4) (Accessed on March 30, 2022) -- 16 [13] Zhong, J., Liu, D., Li, Z., & Sun, X, High thermal conductivity materials and their application on the -17 electronic products. In 2012 IEEE Asia-Pacific Conference on Antennas and Propagation, pp. 173-175, August -18 2012. -- 19 [14] [https://www.engineersedge.com/heat\\_transfer/convective\\_heat\\_transfer\\_coefficients\\_13378.htm](https://www.engineersedge.com/heat_transfer/convective_heat_transfer_coefficients_13378.htm) -20 (Accessed on April 8, 2022) -- 21 [15] (Accessed on April 8, 2022) -- 22 [16] "Serial Interface for Data Converters", JESD204C.1, December 2021, [www.jedec.org](http://www.jedec.org) -- 23 [17] "JESD204x Frame Mapping Table Generator", [https://www.analog.com/en/license/licensing-](https://www.analog.com/en/license/licensing-agreement/jesd204x-frame-mapping-table-generator.html) -24 [agreement/jesd204x-frame-mapping-table-generator.html](https://www.analog.com/en/license/licensing-agreement/jesd204x-frame-mapping-table-generator.html) -- 25 [18] AIB specification: -- 26 [19] BoW PHY specification: [https://opencomputeproject.github.io/ODSA-BoW/bow\\_specification.html](https://opencomputeproject.github.io/ODSA-BoW/bow_specification.html) -- 27 [20] Universal Chiplet Interconnect Express web site: -- 28 - -## 1.3 Definitions and Abbreviations - -### 1.3.1 Definitions - -For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [2] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [2]. For the base station classes of Pico, Micro and Macro, the definitions are given in 3GPP TR 38.104 [3]. - -**Integrated architecture:** In the integrated architecture, the O-RU and O-DU are implemented on one platform. Each O-RU and RF front end is associated with one O-DU. They are then aggregated to O-CU and connected by F1 interface. - -**Split architecture:** The O-RU and O-DU are physically separated from one another in this architecture. A switch may aggregate multiple O-RUs to one O-DU. O-DU, switch and O-RUs are connected by the fronthaul interface as defined in WG4. - -### 1.3.2 Abbreviations - -For the purposes of the present document, the abbreviations given in [2] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, as in [2]. - -| | | -|-------|------------------------------------------------------------------------------------| -| 3GPP | Third Generation Partnership Project | -| 5G | Fifth-Generation Mobile Communications | -| 7-2 | Fronthaul interface split option as defined by O-RAN WG4, also referred to as 7-2x | -| ACLR | Adjacent Channel Leakage Ratio | -| ADC | Analog to Digital Converter | -| AGC | Automatic Gain Control | -| AIB | Advanced Interface Bus | -| AISG | Antenna Interface Standards Group | -| ASIC | Application Specific Integrated Circuit | -| BBDEV | Baseband Device | -| BH | Backhaul | -| BIOS | Basic Input/Output System | -| BMC | Baseboard Management Controller | -| BoW | Bunch of Wires | - -| | | | -|----|--------|-------------------------------------------------------| -| 1 | BS | Base Station | -| 2 | BW | Bandwidth | -| 3 | C2C | Chip to Chip Interface | -| 4 | CDR | Clock and Data Recovery | -| 5 | CFR | Crest Factor Reduction | -| 6 | CISPR | International Special Committee on Radio Interference | -| 7 | CLB | Configurable Logic Block | -| 8 | CPU | Central Processing Unit | -| 9 | CRC | Cyclic Redundancy Check | -| 10 | CU | Centralized Unit as defined by 3GPP | -| 11 | DAC | Digital to Analog Converter | -| 12 | DDC | Digital Down Conversion | -| 13 | DDR | Double Data Rate | -| 14 | DEVCLK | Device Clock | -| 15 | DIMM | Dual-Inline-Memory-Modules | -| 16 | D2D | Die-to-Die Interface | -| 17 | DL | Downlink | -| 18 | DMA | Direct Memory Access | -| 19 | DPD | Digital Pre-Distortion | -| 20 | DPDK | Data Plane Development Kit | -| 21 | DPU | Digital Processing Unit | -| 22 | DSP | Digital Signal Processor | -| 23 | DU | Distributed Unit as defined by 3GPP | -| 24 | DUC | Digital Up Conversion | -| 25 | ECC | Error Correcting Code | -| 26 | eCPRI | evolved Common Public Radio Interface | -| 27 | EMC | Electro Magnetic Compatibility | -| 28 | ENIAC | Embedded NIC Inline Accelerator | -| 29 | EVM | Error Vector Magnitude | - -| | | | -|----|---------------------|---------------------------------------------------------------------------------------------| -| 1 | FCC | Federal Communications Commission | -| 2 | FEC | Forward Error Correction | -| 3 | FFT | Fast Fourier Transform | -| 4 | FH | Fronthaul | -| 5 | FHGW | Fronthaul Gateway | -| 6 | FHGW x | Fronthaul gateway with no FH protocol translation, supporting an O-DU with split option x | -| 7 | | and an O-RU with split option x, with currently available options 6□6, 7-2□7-2 and 8□8 | -| 8 | FHGW x→y | Fronthaul Gateway that can translate fronthaul protocol from an O-DU with split option x to | -| 9 | | an O-RU with split option y, with currently available option 7-2□8. | -| 10 | FHHL | Full Height Half Length | -| 11 | FPGA | Field Programmable Gate Array | -| 12 | GbE | Gigabit Ethernet | -| 13 | GMC | Grand Master Clock | -| 14 | GNSS | Global Navigation Satellite System | -| 15 | GPIO | General Purpose Input Output | -| 16 | GPP | General Purpose Processor | -| 17 | GPS | Global Positioning System | -| 18 | GUI | Graphical User Interface | -| 19 | HAR | Hardware Architecture Requirement | -| 20 | HARQ | Hybrid Automatic Repeat request | -| 21 | HDD | Hard Disk Drive | -| 22 | HHHL | Half Height Half Length | -| 23 | HRD | Hardware Reference Design | -| 24 | HW | Hardware | -| 25 | I/O | Input/Output | -| 26 | I2C | Inter-Integrated Circuit (multi IC interface standard) | -| 27 | IEEE | Institute of Electrical and Electronics Engineers | -| 28 | IFFT | Inverse Fast Fourier Transform | -| 29 | IMC | Integrated Memory Controller | - -| | | | -|----|-------------------|----------------------------------------------------------------------------------------------| -| 1 | IMD | Inter Modulation Distortion | -| 2 | JTAG | Joint Test Action Group | -| 3 | KVM | Kernel-based Virtual Machine | -| 4 | L1 | Layer 1 | -| 5 | L2 | Layer 2 | -| 6 | LDPC | Low-Density Parity Codes | -| 7 | LNA | Low Noise Amplifier | -| 8 | LRDIMM | Load-Reduced Dual In-line Memory Module | -| 9 | LTE | Long Term Evolution | -| 10 | LUT | Look-up Table | -| 11 | MH | Midhaul | -| 12 | NEBS | Network Equipment-Building System | -| 13 | NFV | Network Functions Virtualization | -| 14 | NIC | Network Interface Controller | -| 15 | NR | New Radio | -| 16 | OAM | Operations, administration and management | -| 17 | O-CU | O-RAN Centralized Unit as defined by O-RAN | -| 18 | OCXO | Oven Controlled Crystal Oscillator | -| 19 | O-DU x | A specific O-RAN Distributed Unit having fronthaul split option x where x may be 6, 7-2 | -| 20 | | (as defined by WG4) or 8. | -| 21 | OMC | Outdoor Microcell | -| 22 | O-RU x | A specific O-RAN Radio Unit having fronthaul split option x, where x is 6, 7-2 (as defined | -| 23 | | by WG4) or 8, and which is used in a configuration where the fronthaul interface is the same | -| 24 | | at the O-DU x . | -| 25 | ORx | Observation Receiver | -| 26 | PA | Power Amplifier | -| 27 | PCH | Platform Controller Hub | -| 28 | PCIe | Peripheral Component Interface Express | -| 29 | PHC | Physical Hardware Clock | -| 30 | PHY | Physical Layer | - -| | | | -|----|--------|-------------------------------------------| -| 1 | PMBus | Power Management Bus | -| 2 | PPS | Pulse Per Second | -| 3 | PRACH | Physical Random-Access Channel | -| 4 | PTP | Precision Time Protocol | -| 5 | PWM | Pulse Width Modulation | -| 6 | QSFP | Quad Small Form-factor Pluggable | -| 7 | RAN | Radio Access Network | -| 8 | RDIMM | Registered Dual In-line Memory Module | -| 9 | RE | Resource Element | -| 10 | RF | Radio Frequency | -| 11 | RoE | Radio over Ethernet | -| 12 | RU | Radio Unit as defined by 3GPP | -| 13 | Rx | Receiver | -| 14 | SDFEC | Soft-Decision Forward Error Correction | -| 15 | SERDES | Serializer / De-serializer | -| 16 | SFP | Small Form-factor Pluggable | -| 17 | SFP+ | Small Form-factor Pluggable plus | -| 18 | SMA | Sub-Miniature Version A (connector) | -| 19 | SoC | System On Chip | -| 20 | SPI | Serial Peripheral Interface | -| 21 | SSD | Solid State Drive | -| 22 | SyncE | Synchronous Ethernet | -| 23 | TCXO | Temperature Compensate Crystal Oscillator | -| 24 | TDD | Time Division Duplex | -| 25 | TDP | Thermal Design Power | -| 26 | TR | Technical Report | -| 27 | TR | Transmit Receive (switch) | -| 28 | TRx | Transceiver | -| 29 | TS | Technical Specification | - -| | | | -|---|------|---------------------------------------| -| 1 | Tx | Transmitter | -| 2 | UEFI | Unified Extensible Firmware Interface | -| 3 | UCIe | Universal Chiplet Interface Express | -| 4 | UL | Uplink | -| 5 | USB | Universal Serial Bus | -| 6 | UTC | Coordinate Universal Time | -| 7 | WG | Working Group | - ---- - -## 8 Chapter 2 Hardware Reference Design 1 - -9 This chapter describes a white box hardware reference design example for outdoor Microcell deployment -10 scenario. It includes O-CU and O-DU7-2 for OMC deployment scenario. - -### 11 2.1 O-CU Hardware Reference Design - -12 The O-CU white box hardware is the platform that perform the O-CU function of upper L2 and L3. The -13 hardware systems specified in this document meet the computing, power and environmental requirements of -14 use cases configurations and feature sets of RAN physical node. These requirements are described in the early -15 hardware requirement specification as well as in the use cases document. The O-CU hardware includes the -16 chassis platform, mother board, peripheral devices and cooling devices. The mother board contains processing -17 unit, memory, the internal I/O interfaces, and external connection ports. The midhaul (MH) and backhaul (BH) -18 interface are used to carry the traffic between O-CU and O-DU7-2 as well as O-CU and core network. The other -19 hardware functional components include: the storage for software, hardware and system debugging interfaces, -20 board management controller, just to name a few; the O-CU designer will make decision based on the specific -21 needs of the implementation. - -22 The HW reference design of O-CU is the same as O-DU7-2 except for the need of HW accelerator, thus detail -23 design will be described in O-DU7-2 section 2.2. - -### 24 2.2 O-DU7-2 Hardware Reference Design - -25 The O-DU7-2 white box hardware is the platform that performs the O- DU7-2 functions such as upper L1 and -26 lower L2 functions. The hardware systems specified in this document meet the computing, power and -27 environmental requirements of use case's configurations and feature sets of RAN physical node. These -28 requirements are described in the early hardware requirement specification as well as in the use cases document. -29 The O-DU7-2 hardware includes the chassis platform, mother board, peripheral devices and cooling devices. -30 The mother board contains processing unit, memory, the internal I/O interfaces, and external connection ports. -31 The fronthaul and backhaul interface are used to carry the traffic between O-RU7-2 / FHGW7-2 / FHGW7-2→8 -32 and O-DU7-2 as well as O-CU and O-DU7-2. The O-DU7-2 design may also provide an interface for hardware -33 accelerator if that option is preferred. The other hardware functional components include: the storage for - -1 software, hardware and system debugging interfaces, board management controller, just to name a few; the O- - 2 DU7-2 designer will make decision based on the specific needs of the implementation. - -3 Note that the O-DU7-2 HW reference design is also feasible for O-CU and integrated O-CU / O-DU7-2. - -### 4 2.2.1 O-DU7-2 High-Level Functional Block Diagram - -5 **Figure 2.2.1-1** shows the major functional blocks of O-DU7-2. The digital processing unit handles the baseband - 6 processing workload. To make the processing more efficient, an accelerator can be used to assist with the - 7 baseband workload processing. The memory devices include the random-access memory (RAM) for - 8 temporary storage of data while flash memory is used for codes and logs. The storage device is for persistent - 9 storage. The external network cards can be used for fronthaul or backhaul connection. The baseboard - 10 management controller (BMC) is a microcontroller which monitors hardware operation on motherboard. The - 11 clock circuits provide digital processing unit with required clock signals. - -12 - -![Functional block diagram of O-DU7-2 showing a central Digital Processing Unit connected to an Accelerator, Baseboard Management Controller, and Clock on the left, and to DDR RAM, Flash Memory, Storage Drives, and an Ethernet Card on the right.](77464a47f104d0d647b2414591137b64_img.jpg) - -``` - -graph LR - subgraph ODU72 [O-DU7-2] - DPU[Digital Processing Unit] - Acc[Accelerator] - BMC[Baseboard Management Controller] - Clock[Clock] - DDR[DDR RAM] - Flash[Flash Memory] - Storage[Storage Drives] - Ethernet[Ethernet Card] - - Acc <--> DPU - BMC <--> DPU - Clock <--> DPU - DPU <--> DDR - DPU <--> Flash - DPU <--> Storage - DPU <--> Ethernet - end - -``` - -Functional block diagram of O-DU7-2 showing a central Digital Processing Unit connected to an Accelerator, Baseboard Management Controller, and Clock on the left, and to DDR RAM, Flash Memory, Storage Drives, and an Ethernet Card on the right. - -13 - -Figure 2.2.1-1 O-DU7-2 Functional Block Diagram - -14 - -15 - -### 16 2.2.2 O-DU7-2 Hardware Design Description - -17 Figure 2.2.2-1 describes the various components and connections inside the O-DU7-2 white box. - -![O-DU7-2 Hardware Block Diagram showing SoC CPU, BMC, PCH, and various I/O components like DDR4, SATA, Ethernet, USB, and M.2 connectors.](2b3a967f6ce4f23649be995a353e39f8_img.jpg) - -The diagram illustrates the hardware architecture of the O-DU7-2. At the center is a System on Chip (SoC) labeled 'U1 SoC CPU'. It is connected to four DDR4 DIMM slots (labeled 'DDR4 1866/2133/2400/2666'). The SoC is also connected to a Platform Controller Hub (PCH) via a PCIe 3.0 x16 link. The PCH manages various I/O components: - - -- SATA:** Four SATA3.0 ports (0-3) are connected to the PCH. -- Ethernet:** A 10G PHY is connected to the PCH, which in turn connects to a Network Interface Card (NIC). The NIC is connected to two Ethernet ports labeled JLAN3 and JLAN2. -- USB:** A USB 3.0/2.0 controller is connected to the PCH, leading to 'USB 3.0 Rear I/O'. A USB 2.0 HUB is also connected to the PCH, providing 'USB 2.0 Header' and 'M.2 (E-key) CONN(JMD3)'. -- M.2 Connectors:** Multiple M.2 connectors are shown: 'M.2 (B-key) CONN(JMD2)', 'M.2 (E-key) CONN(JMD3)', and 'M.2 (M-key) CONN(JMD1)'. These are connected via PCIe 3.0 x2 and PCIe 3.0 x1 links. -- Other I/O:** The PCH connects to 'JLANT' (1GbE x1), 'JLAN4' (1GbE x4), 'JTPM1 Header' (SPI), and 'eSPI'. -- BMC:** A Baseboard Management Controller (BMC) is connected to the SoC via a PCIe 3.0 x1 link. The BMC is connected to 'DDR4', 'FLASH', 'COM1/2', 'PHY' (for 3rd LAN), and 'VGA HEADER'. -- REAR IO:** The rear I/O section includes 'COM + 3rd LAN', 'USB3.0', '1G LAN', 'SFP+', '10G LAN', and '1G LAN(2x4)'. - -O-DU7-2 Hardware Block Diagram showing SoC CPU, BMC, PCH, and various I/O components like DDR4, SATA, Ethernet, USB, and M.2 connectors. - -Figure 2.2.2-1 O-DU7-2 Hardware Block Diagram - -As described in the previous section, the O-DU7-2 hardware can be implemented with different design choices. Here, we use a SoC design-based as an example which performs most of the workload for O-DU7-2. The accelerator can be used to perform other functions based on the overall performance requirement. Several Ethernet controllers are also used for front haul link, back haul link and remote console control connection. The other parts include: RAM, flash memory, and hard drive storage. The JTAG and USB ports are provided for hardware debug and local connection if needed. Finally, BMC block is mainly responsible for monitoring the hardware status of the motherboard. - -### 2.2.3 O-DU7-2 Hardware Components - -In this section, we describe the details of the O-DU7-2 hardware component's requirements, their features and parameters. The component selection is based on the use case requirements which are listed in the hardware architecture and requirements document [6]. - -#### 2.2.3.1 Digital Processing Unit - -This example of the digital processing unit in O-DU7-2 is based on the General-Purpose Processor (GPP). - -##### 2.2.3.1.1 Digital Processing Unit Requirements - -The GPP requirements are listed in Table 2.2.3-1. - -Table 2.2.3-1 Processor Feature List - -| Item Name | Description | -|--------------------------------------------|-------------| -| # of Cores | 16 | -| # of Threads | 32 | -| Base Frequency | 2.20 GHz | -| Max Turbo Frequency | 3.00 GHz | -| Cache | 22 MB | -| Thermal Design Power (TDP) | 100W | -| Max Memory Size (dependent on memory type) | 512 GB | -| Memory Types | DDR4 | -| Max # of Memory Channels | 4 | - -#### 2.2.3.1.1.1 Interfaces - -The interface specifications on the main board are described in the sections below. - -##### 2.2.3.1.1.1.1 Memory Channel Interfaces - -The system memory capacity, type and related information are described in Table 2.2.3-2. - -Table 2.2.3-2 Memory Channel Feature List - -| Item Name | Description | -|----------------------|-------------------------| -| Memory Types | DDR4 | -| # of Memory Channels | 4 | -| ECC LRDIMM | Up to 512GB | -| ECC RDIMM | Up to 256GB | -| Memory Speed | 2666/2400/2133MHz | -| DIMM Sizes | 128GB, 64GB, 32GB, 16GB | -| Memory Voltage | 1.2 V | - -##### 2.2.3.1.1.1.2 PCIe - -PCIe Gen 3 should be supported by the processor. There are total of 32 PCIe lanes with 128 Gb/s bandwidth. The 32 PCIe lanes can be divided into two x16 slots by using a riser card. - -##### 2.2.3.1.1.1.3 Ethernet - -The system should be capable to offer aggregated 48 Gb/s Ethernet bandwidth. The breakout the ports are discussed in later section. When higher Ethernet bandwidth required, an Ethernet card can be installed in one of the PCIe slot. - -#### 2.2.3.1.2 Digital Processing Unit Design - -The digital processing unit is a system-on-a-chip (SoC) device which is a 64-bit multi-core server class processor. This SoC includes an integrated Platform Controller Hub (PCH), integrated high-speed I/O, Integrated Memory Controllers (IMC), and four integrated 10 Gigabit Ethernet ports. - -The SoC supports 512-bit wide vector processing instruction set. It also supports hardware virtualization to enable dynamic provisioning of services as communication service providers extend network functions virtualization (NFV). Figure 2.2.2-1 shows the major functional blocks of the digital processing unit. - -### 2.2.3.2 Hardware Accelerator - -Hardware accelerators can be used in O-DU7-2 to offload computationally intensive functions and to optimize the performance under varying traffic and loading conditions. While the hardware acceleration functional requirements and implementation are system designer's choice; however, the O-DU7-2 is required to meet the minimum system performance requirements under various loading conditions and deployment scenarios. In most cases, a Field Programmable Gate Array (FPGA) or Application Specific Integrated Circuit (ASIC) based PCIe card can be used to optimize the system performance. The FPGA(s) are part of a Network Interface Controller (NIC) that further provides connectivity services. - -#### 2.2.3.2.1 Accelerator Design Solution 1 - -Channel coding for Low-Density Parity Codes (LDPC) and fronthaul compression requires a significant amount of bit level processing and is well suited to a fine-grained FPGA architecture and/or low cost/power structured ASIC. Options include: - -- Virtualization: Multi-channel DMA, Virtual machine integration, load balancing functions -- Look-aside FEC: LDPC (de)coding, Polar (de)coding, Rate (De)Matcher, (De) Interleaver, Cyclic Redundancy Check (CRC), Hybrid Automatic Repeat request (HARQ) retransmission -- Bump-in-wire Fronthaul: compression / decompression for latency and bandwidth reduction - -##### 2.2.3.2.1.1 Accelerator Requirements - -Hardware and firmware requirements for this accelerator design are given in Table 2.2.3-3 and Table 2.2.3-4, respectively. - -1 - -**Table 2.2.3-3 Accelerator Hardware Feature List** - -| Item Name | Description | -|-----------------------------------------------|-------------------------------------------------------------------------------------------------| -| PCIe (Interface with digital processing unit) | Gen4 x16 (and lower) | -| Form factor | FHHL | -| Connectivity | 2x QSFP28/56 | -| FPGA | Logic Elements: 1437K
M20K Memory: 139Mb
Quad A53 Hard Processor Sub-system | -| NIC Device | 100Gb xHAUL for FH, BH & MH traffic shaping. Optional FPGA co-processing. | -| DDR Main | 8+8+1GB DDR4 | -| Flash (FPGA images) | >=1 Gbit | -| BMC | Telemetry, Security, remote upgrade | -| Clocking | For O-RAN C1, C2, C3 & C4 | -| Fronthaul | eCPRI, RoE IEEE1914.3, O-RAN WG4 | -| GPS | SMA for 1 PPS & 10MHz (in/out) | -| Operating Temperature (ambient) | NEBS Compliant | -| Power | <75W (without optional NIC device) | -| Clock Accuracy | Low-Jitter, configurable clock ranging from 10MHz to 750MHz. Option for OCXO (TCXO as standard) | - -2 - -3 - -**Table 2.2.3-4 Accelerator Firmware Feature List** - -| Item Name | Description | -|--------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Remote system upgrade | Securely upgradable FPGA flash image | -| Queuing | 64 Queues supported equally split between UL & DL. | -| LDPC Acceleration | NR LDPC Encoding with, interleaving and rate-matching.
NR LDPC Decoding with sub-block de-interleaving function of reverse rate matching.
Early Termination, CRC attachment and HARQ buffering.
5G Throughput: DL 14.8Gbps, UL 3.2Gbps | -| Load Balancing (channel coding) | Load balancer distributes the pending encoder/decoder requests to encoder/decoders | -| Descriptor Format (channel coding) | Code block-based interface.
Software enablement by BBDEV API (DPDK) [7], [8] | -| Fronthaul Compression | In-line compression/decompression for Mu-Law, block-floating point and quantization according to the O-RAN WG4 specification. | -| Open programmable acceleration environment | Support for:
  • • FPGA Flashing upgrade
  • • Firmware version reporting
  • • PCIe diagnostics
  • • Ethernet diagnostics
  • • Temperature and voltage telemetry information
| - -4 - -1 2.2.3.2.1.2 Accelerator Design - -2 Figure 2.2.3-1 illustrates Accelerator Design 1 without optional NIC Device. Figure 2.2.3-2 illustrates the -3 Accelerator Design 1 with optional NIC Device. - -![Figure 2.2.3-1: Accelerator Design 1 without optional NIC Device. The diagram shows a Digital Processing Unit (DPU) connected to an FPGA via a PCIe Gen 4x16 (200G) link. The DPU contains L3, L2, and part of L1 cache. The FPGA contains Connectivity & L1 Processing, C1,2,3,4 Sync, and a 1PPS & 10MHz SMA connector. The FPGA is connected to an external FH 2x2x56Gbps (Or lower) interface.](844077b3034f0030b404207db0ad76b4_img.jpg) - -``` - -graph LR - DPU[Digital Processing Unit -L3,L2,L1(part)] <--> |"PCIe Gen 4x16 -Or lower (200G)"| FPGA - subgraph FPGA - F[Connectivity & L1 Processing. -C1,2,3,4 Sync] - SMA[1PPS & 10MHz SMA] - end - F --> SMA - F <--> |"FH 2x2x56Gbps -Or lower"| FH[ ] - style FH fill:none,stroke:none - -``` - -Figure 2.2.3-1: Accelerator Design 1 without optional NIC Device. The diagram shows a Digital Processing Unit (DPU) connected to an FPGA via a PCIe Gen 4x16 (200G) link. The DPU contains L3, L2, and part of L1 cache. The FPGA contains Connectivity & L1 Processing, C1,2,3,4 Sync, and a 1PPS & 10MHz SMA connector. The FPGA is connected to an external FH 2x2x56Gbps (Or lower) interface. - -4 -5 **Figure 2.2.3-1 Accelerator Design 1 without optional NIC Device** - -![Figure 2.2.3-2: Accelerator Design 1 with optional NIC Device. This diagram extends Figure 2.2.3-1 by adding an optional NIC i40. The DPU is connected to the FPGA via PCIe Gen 4x16. The FPGA is connected to the NIC i40 via PCIe Gen 4x8 (100G). The NIC i40 is also connected to the FPGA via a 100Gb link. The 1PPS & 10MHz SMA connector is now connected to the NIC i40. The FPGA still connects to the external FH 2x2x56Gbps (Or lower) interface.](ab846b81e78dbc8da2a6f9511e2f248a_img.jpg) - -``` - -graph TD - DPU[Digital Processing Unit -L3,L2,L1(part)] <--> |"PCIe Gen 4x16"| FPGA - subgraph FPGA - F[Connectivity & L1 Processing. -C1,2,3,4 Sync] - NIC[ ] - SMA[ ] - end - F <--> |"PCIe Gen 4x8 -Or lower (100G)"| NIC - NIC <--> |"100Gb"| F - NIC --> SMA - SMA --> |"1PPS & 10MHz SMA"| NIC - F <--> |"FH 2x2x56Gbps -Or lower"| FH[ ] - style FH fill:none,stroke:none - style NIC fill:none,stroke:none - style SMA fill:none,stroke:none - -``` - -Figure 2.2.3-2: Accelerator Design 1 with optional NIC Device. This diagram extends Figure 2.2.3-1 by adding an optional NIC i40. The DPU is connected to the FPGA via PCIe Gen 4x16. The FPGA is connected to the NIC i40 via PCIe Gen 4x8 (100G). The NIC i40 is also connected to the FPGA via a 100Gb link. The 1PPS & 10MHz SMA connector is now connected to the NIC i40. The FPGA still connects to the external FH 2x2x56Gbps (Or lower) interface. - -6 -7 -8 **Figure 2.2.3-2 Accelerator Design 1 with optional NIC Device** - -9 -10 2.2.3.2.2 Accelerator Design Solution 2 - -11 Channel coding for LDPC and fronthaul compression requires a significant amount of bit level processing and -12 is well suited to a fine-grained structured ASIC. Features include: - -- 13 • Virtualization: Multi-channel DMA, Virtual machine integration, load balancing functions -- 14 • Look-aside FEC: Turbo (de)coding, LDPC (de)coding, Rate (De)Matcher, (De) Interleaver, CRC, HARQ -15 retransmission & (de) interleaver. - -16 - -1 2.2.3.2.2.1 Accelerator Requirement - -2 Accelerator Hardware and Firmware features are listed in Table 2.2.3-5 and Table 2.2.3-6, respectively. - -3 - -4 - -Table 2.2.3-5 Accelerator Hardware Feature List - -| Item Name | Description | -|-----------------------------|-----------------------------------------------------------| -| PCIe | Gen3 x16 | -| Form factor | HHHL | -| DDR | DDR4 (64-bit +ECC), 2667Mbps Interface for HARQ buffering | -| Board Management Controller | Telemetry, Security. | -| Power | <35W | - -5 - -6 - -7 - -Table 2.2.3-6 Accelerator Firmware Feature List - -| Item Name | Description | -|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Queuing | 64 Queues supported equally split between UL & DL. | -| LDPC Acceleration | NR LDPC Encoding with, interleaving and rate-matching.
NR LDPC Decoding with sub-block de-interleaving function of reverse rate matching.
Early Termination, CRC attachment and HARQ buffering.
5G Throughput: DL 23Gbps, UL 8Gbps | -| Load Balancing (channel coding) | Load balancer distributes the pending encoder/decoder requests to encoder/decoders | -| Descriptor Format (channel coding) | Code block and transport block-based interface.
Software enablement by BBDEV API (DPDK) [7], [8] | - -8 - -9 2.2.3.2.2.2 Accelerator Design - -10 - -The following diagram shows the structured ASIC based accelerator design. - -![Diagram showing the Structured ASIC Accelerator Design. A Digital Processing Unit (containing L3, L2, L1(part)) is connected via a PCIe Gen 3x16 Or lower (100G) interface to a Structured ASIC (containing Turbo/LDPC Code/Transport Block).](ea49c15f36ffb089d44f1d793f013778_img.jpg) - -``` - -graph LR - subgraph DPU [Digital Processing Unit] - L3L2L1["L3, L2, L1(part)"] - end - subgraph ASIC [Structured ASIC] - TurboLDPC["Turbo/LDPC Code/Transport Block"] - end - DPU <--> |"PCIe Gen 3x16 Or lower (100G)"| ASIC - -``` - -Diagram showing the Structured ASIC Accelerator Design. A Digital Processing Unit (containing L3, L2, L1(part)) is connected via a PCIe Gen 3x16 Or lower (100G) interface to a Structured ASIC (containing Turbo/LDPC Code/Transport Block). - -11 - -12 - -Figure 2.2.3-3 Structured ASIC Accelerator Design - -13 - -1       2.2.3.2.3 Accelerator Design Solution 3 - -2       The O-DU7.2 system is typically implemented using a multi-core processor and one or more hardware - 3       accelerators. Parts of O-DU7.2 protocol stack can be implemented in software running on the multi-core - 4       processors and the computationally intensive L1 and L2 functions can be offloaded to an FPGA-based - 5       hardware accelerator. This accelerator comprises two FPGAs for L1 offload and fronthaul connectivity in - 6       lookaside mode. The accelerator hardware and firmware features are listed in Table 2.2.3-7 and Table 2.2.3-8. - -7 - 8       2.2.3.2.3.1 Accelerator Hardware Features - -9                       **Table 2.2.3-7 Accelerator Hardware Features** - -| Item Name | Description | | -|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------| -| SoC Resources | FPGA 1
System Logic cells - 930K
CLB LUT - 425K
SDFEC -8
DSP Slices - 4,272
BRAM - 38.0Mb
URAM - 22.5Mb | FPGA 2
System Logic cells - 1,143K
CLB LUT - 523K
CLB Flip-Flops -1,045K
DSP Slices - 1,968
BRAM - 34.6Mb
URAM - 36.0Mb | -| Form Factor | FHHL PCIe Form Factor | | -| PCIe Interface | Gen 3 x16 with Bifurcation | | -| On Board Memory | FPGA1
Total Capacity 4 GB in Programmable Logic, upgradeable to 8GB
Total Capacity 2 GB in Programmable Subsystem, upgradeable to 4GB | FPGA2
Total Capacity 4 GB in Programmable Logic, upgradeable to 8GB
Total Capacity 2 GB in Programmable Subsystem, upgradeable to 4GB | -| Network Interface(s) | 2xSFP28 optical interfaces to FPGA2
(User Configurable, includes 10/25 Ethernet) | | -| Other External Interface(s) | Micro USB for JTAG support (FPGA programming and debug) and access to BMC | | -| Graphical User interface | GUI for monitoring the basic board parameters, monitoring temperature alerts, firmware upgrades for BMC | | -| Board Management Controller | Telemetry, Security, Remote Upgrade | | -| Clocking | O-RAN C1, C2, C3, C4 | | -| Fronthaul | eCPRI, RoE IEEE1914.3, O-RAN WG4 FH | | -| GPS | GPS SMA for 1 PPS (In/Out) | | -| Operating Temperature | NEBS Compliant | | -| Power | < 75 W | | -| Clocking Options | Low-Jitter, configurable clock ranging from 10MHz to 750MHz
1 PPS input and output with assembly option for OCXO and TCXO | | - -10 - -11 - -1 2.2.3.2.3.2 Hardware Accelerator Firmware Features - -2 Table 2.2.3-8 Hardware Accelerator Firmware Features - -| Item Name | Description | -|--------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Remote System Upgrade | Securely upgradable FPGA flash image | -| L1 Acceleration | 5G NR LDPC encoding/decoding with interleaving/de-interleaving and rate-matching/rate-de-matching along with early termination, CRC attachment, and HARQ management | -| Hardware-Software APIs | Fully compliant with DPDK/BBDEV APIs | -| Fronthaul Protocols/Compression | Fully compliant with O-RAN WG4 M, C,U & S-planes Specifications | -| Open Programmable Acceleration Environment | Support for:
  • • FPGA flashing upgrade
  • • Firmware version reporting
  • • PCIe diagnostics
  • • Ethernet diagnostics
  • • Temperature and voltage telemetry information
| - -3 -4 The hardware accelerator supports x86 or non-x86-based processors. Figure 2.2.3-4 illustrates the two-chip -5 acceleration architecture comprising two FPGAs with multi-lane PCIe interfaces toward the CPU and external -6 connectivity toward O-RU7-2(s) via eCPRI and O-CU(s) through GbE connectivity. The example architecture -7 further depicts multi-lane Gen3 PCIe interfaces between each FPGA and the CPU. The FPGAs communicate -8 through high-bandwidth Ethernet (GbE) transport. - -![Figure 2.2.3-4: Dual-chip FPGA-based Hardware Acceleration in O-DU7-2. The diagram shows an X86 or ARM-based CPU (L2 and Partial L1) connected to two FPGAs. FPGA1 (L1 Offload) and FPGA2 (Connectivity) are both connected to the CPU via a [Bifurcated] PCIe Interface (PCIe Gen3x16 100G). FPGA1 and FPGA2 are also connected to each other via an Inter Chip Interface (100G Ethernet). The CPU is connected to an F1 Interface (Ethernet (10/25G)). FPGA2 is connected to a Fronthaul Interface (10/25G Ethernet/eCPRI).](392a79ccd95e682ccd08f35ab2e64144_img.jpg) - -9 - -Figure 2.2.3-4: Dual-chip FPGA-based Hardware Acceleration in O-DU7-2. The diagram shows an X86 or ARM-based CPU (L2 and Partial L1) connected to two FPGAs. FPGA1 (L1 Offload) and FPGA2 (Connectivity) are both connected to the CPU via a [Bifurcated] PCIe Interface (PCIe Gen3x16 100G). FPGA1 and FPGA2 are also connected to each other via an Inter Chip Interface (100G Ethernet). The CPU is connected to an F1 Interface (Ethernet (10/25G)). FPGA2 is connected to a Fronthaul Interface (10/25G Ethernet/eCPRI). - -10 -11 Figure 2.2.3-4 Dual-chip FPGA-based Hardware Acceleration in O-DU7-2 - -1 -2 2.2.3.2.4 Accelerator Design Solution 4 - -3 The O-DU7.2 system is typically implemented using a multi-core processor (CPU) and one or more hardware -4 accelerators. Parts of O-DU7.2 protocol stack can be implemented in software running on the multi-core -5 processors and the computationally intensive L1 and L2 functions can be offloaded to an FPGA-based -6 hardware accelerator. This accelerator comprises a single FPGA for L1 offload in lookaside mode. The -7 accelerator hardware and firmware features are listed in Table 2.2.3-9 and Table 2.2.3-10. - -8 -9 2.2.3.2.4.1 Accelerator Hardware Features - -10 **Table 2.2.3-9 Accelerator Hardware Features** - -| Item Name | Description | -|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------| -| SoC Resources | System Logic cells - 930K
CLB LUT - 425K
SDFEC -8
DSP Slices - 4,272
BRAM - 38.0Mb
URAM - 22.5Mb | -| Form Factor | HHHL PCIe Form Factor | -| PCIe Interface | Gen 3 x16 (Gen4 x8) | -| On Board Memory | Total Capacity 4 GB in Programmable Logic, upgradeable to 8GB
Total Capacity 2 GB in Processor Subsystem, upgradeable to 4GB | -| Other External Interface(s) | Micro USB for JTAG support (FPGA programming and debug) and access to BMC | -| Graphical User interface | GUI for monitoring the basic board parameters, monitoring temperature alerts, firmware upgrades for BMC | -| Board Management Controller | Telemetry, Security, Remote Upgrade | -| Operating Temperature | NEBS Compliant | -| Power | < 35 W | - -11 - -1 2.2.3.2.4.2 Hardware Accelerator Firmware Features - -2 **Table 2.2.3-10 Hardware Accelerator Firmware Features** - -| Item Name | Description | -|--------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Remote System Upgrade | Securely upgradable FPGA flash image | -| L1 Acceleration | 5G NR LDPC encoding/decoding with interleaving/de-interleaving and rate-matching/rate-de-matching along with early termination, CRC attachment, and HARQ management | -| Hardware-Software APIs | Fully compliant with DPDK/BBDEV APIs | -| Open Programmable Acceleration Environment | Support for:
  • • FPGA flashing upgrade
  • • Firmware version reporting
  • • PCIe diagnostics
  • • Ethernet diagnostics
  • • Temperature and voltage telemetry information
| - -3 -4 The hardware accelerator supports x86 or non-x86-based processors. Figure 2.2.3-5 illustrates the single- -5 chip acceleration architecture comprising one FPGA with Gen3 x16 or Gen4 x8 PCIe interfaces toward the -6 CPU. -7 - -![Diagram of single-chip FPGA-based hardware acceleration architecture. A central box labeled 'X86 or ARM-based CPU (L2 and Partial L1)' is connected to an 'FPGA (L1 Offload)' box via a 'PCIe Interface' (labeled 'PCIe Gen3x16 or Gen4 x8 100G'). The CPU box is also connected to an 'F1 Interface' (labeled 'Ethernet (10/25G)').](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) - -Diagram of single-chip FPGA-based hardware acceleration architecture. A central box labeled 'X86 or ARM-based CPU (L2 and Partial L1)' is connected to an 'FPGA (L1 Offload)' box via a 'PCIe Interface' (labeled 'PCIe Gen3x16 or Gen4 x8 100G'). The CPU box is also connected to an 'F1 Interface' (labeled 'Ethernet (10/25G)'). - -8 **Figure 2.2.3-5 Single-chip FPGA-based Hardware Acceleration in O-DU7-2** - -9 -10 2.2.3.2.5 Accelerator Design Solution 5 - -11 -12 This design includes an Embedded NIC Inline Accelerator (ENIAC) with an ASIC that is capable of providing -13 NIC functions. One option supports a high-capacity O-DU using multiple PCIe cards in standard racks and -14 aligns with the FAPI interface to maximize software reuse. The second option supports a high-capacity O-DU -15 using an Ethernet-based backplane interconnect and aligns with the nFAPI interface to maximize software -16 reuse. ENIAC unloads L1 from the host, allowing it to focus on L2. - -1 -2 -3 -4 -5 - -2.2.3.2.5.1 Accelerator Requirements - -Hardware and firmware requirements for this accelerator design are given in Table 2.2.3-11 and Table 2.2.3-12, respectively. - -**Table 2.2.3-11 Accelerator Hardware Feature List** - -| Item Name | Description | -|-----------------------------------------------|-------------------------------------------------------------------------------------------------| -| PCIe (Interface with digital processing unit) | Gen4 x16 (and lower) | -| Form factor | FHHL | -| Connectivity | QSFP28/SFP | -| NIC Device | 100Gb xHAUL for FH, BH & MH traffic shaping. | -| DDR Main | Min 4 GB DDR4 | -| Flash (FPGA images) | >=1 Gbit | -| BMC | Telemetry, Security, remote upgrade | -| Clocking | For O-RAN C1, C2, C3 & C4 | -| Fronthaul | eCPRI, RoE IEEE1914.3, O-RAN WG4 | -| GPS | SMA for 1 PPS & 10MHz (in/out) | -| Operating Temperature (ambient) | NEBS Compliant | -| Power | <75W | -| Clock Accuracy | Low-Jitter, configurable clock ranging from 10MHz to 750MHz. Option for OCXO (TCXO as standard) | - -6 -7 - -**Table 2.2.3-12 Accelerator Firmware Feature List** - -| Item Name | Description | -|--------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Remote system upgrade | Securely upgradable image | -| Queuing | Command queuing at FAPI interface | -| LDPC Acceleration | Rel15 compliant | -| Fronthaul Compression | In-line compression/decompression for Mu-Law, block-floating point and quantization according to the O-RAN WG4 specification. | -| Open programmable acceleration environment | Support for:
  • Flashing upgrade
  • Firmware version reporting
  • PCIe diagnostics
  • Ethernet diagnostics
  • Temperature and voltage telemetry information.
| - -8 -9 -10 -11 - -2.2.3.2.5.2 Accelerator Design - -Figure 2.2.3-6 illustrates Accelerator Design 5 with integrated NIC and PCIe connectivity to L2. Figure 2.2.3-7 illustrates Accelerator Design 5 with integrated NIC and Ethernet connectivity to L2. - -![Figure 2.2.3-6: Accelerator Design Using PCIe. This block diagram shows the interconnections for an accelerator design using PCIe. On the left, there are two boxes: 'L2 Processing' at the top and 'Timing' at the bottom. 'L2 Processing' is connected to a central box labeled 'L1 Upper Phy Accelerator' via a double-headed arrow labeled 'FAPI on PCIe4x16'. 'Timing' is connected to the same central box via a double-headed arrow labeled 'PPS 10 MHz'. The central box contains the text '8 Layer MIMO Embedded NIC with eCPRI'. To the right of the central box, there are four labels stacked vertically: 'O-RAN 7-2x', 'eCPRI FH QSFP28', '100 Gbps Ethernet', and 'SyncE'. A double-headed arrow points from the right side of the central box to these labels.](fa01531ea2c45beeb4036005da3037a4_img.jpg) - -Figure 2.2.3-6: Accelerator Design Using PCIe. This block diagram shows the interconnections for an accelerator design using PCIe. On the left, there are two boxes: 'L2 Processing' at the top and 'Timing' at the bottom. 'L2 Processing' is connected to a central box labeled 'L1 Upper Phy Accelerator' via a double-headed arrow labeled 'FAPI on PCIe4x16'. 'Timing' is connected to the same central box via a double-headed arrow labeled 'PPS 10 MHz'. The central box contains the text '8 Layer MIMO Embedded NIC with eCPRI'. To the right of the central box, there are four labels stacked vertically: 'O-RAN 7-2x', 'eCPRI FH QSFP28', '100 Gbps Ethernet', and 'SyncE'. A double-headed arrow points from the right side of the central box to these labels. - -Figure 2.2.3-6 Accelerator Design Using PCIe - -![Figure 2.2.3-7: Accelerator Design Using Ethernet. This block diagram shows the interconnections for an accelerator design using Ethernet. On the left, there are two boxes: 'L2 Processing' at the top and 'Timing' at the bottom. 'L2 Processing' is connected to a central box labeled 'L1 Upper Phy Accelerator' via a double-headed arrow labeled 'FAPI on Ethernet'. 'Timing' is connected to the same central box via a double-headed arrow labeled 'PPS 10 MHz'. The central box contains the text '8 Layer MIMO Embedded NIC with eCPRI'. To the right of the central box, there are four labels stacked vertically: 'O-RAN 7-2x', 'eCPRI FH QSFP28', '100 Gbps Ethernet', and 'SyncE'. A double-headed arrow points from the right side of the central box to these labels.](744acfe8d4e31bcf03f95714c2f6e567_img.jpg) - -Figure 2.2.3-7: Accelerator Design Using Ethernet. This block diagram shows the interconnections for an accelerator design using Ethernet. On the left, there are two boxes: 'L2 Processing' at the top and 'Timing' at the bottom. 'L2 Processing' is connected to a central box labeled 'L1 Upper Phy Accelerator' via a double-headed arrow labeled 'FAPI on Ethernet'. 'Timing' is connected to the same central box via a double-headed arrow labeled 'PPS 10 MHz'. The central box contains the text '8 Layer MIMO Embedded NIC with eCPRI'. To the right of the central box, there are four labels stacked vertically: 'O-RAN 7-2x', 'eCPRI FH QSFP28', '100 Gbps Ethernet', and 'SyncE'. A double-headed arrow points from the right side of the central box to these labels. - -Figure 2.2.3-7 Accelerator Design Using Ethernet - -### 2.2.3.3 Baseboard Management Controller - -BMC is used to perform hardware power control (power on, power off and power cycle), monitor hardware status (temperatures, voltages, etc), monitor Basic I/O System (BIOS)/ Unified Extensible Firmware Interface (UEFI) firmware status, and log system events. It provides remote access via shared or dedicated NIC. System user can do console access via serial or physical/Kernel-based Virtual Machine (KVM). The BMC has dedicated RAM and flash memory. It provides access via serial port or Ethernet port. Figure 2.2.2-1 describes the BMC connections with related components. - -1 2.2.4 Synchronization and Timing - -2 2.2.4.1 Synchronization and Timing Design 1 - -3 This section describes the synchronization and timing mechanism that is used in the O-DU7-2. - -4 2.2.4.2 Hardware Requirements - -5 The O-DU7-2 shall support following timing synchronization methods: - -- 6 1. GNSS Synchronization -- 7 2. Ethernet based IEEE1588V2 Synchronization -- 8 3. GNSS and IEEE1588 switching - -9 2.2.4.3 Hardware Design - -10 Depending on the timing distribution topologies used, the O-DU7-2 system clock is able to synchronize with - 11 the Grand Master Clock (GMC) using IEEE1588 via either the front haul NIC or backhaul NIC or - 12 synchronizing timing using Global Navigation Satellite System (GNSS). In the case of IEEE1588, the Physical - 13 Hardware Clock (PHC) within the NIC is synchronized with the GMC first, then the O-DU7-2 system clock is - 14 synchronized with the PHC. The O-DU7-2 is also capable to provide a clock to the O-RU7-2 via front haul if - 15 needed. When GNSS becomes available to O-DU7-2, it will be able to synchronize the system clock to - 16 Coordinated Universal Time (UTC). Figure 2 7 outlines the O-DU7-2 timing synchronization mechanisms. - -![Diagram of O-DU Timing Synchronization showing GNSS, PHC, System Clock, and NIC connections.](f64e1e0997695248c0cd4122c5b1a170_img.jpg) - -The diagram illustrates the timing synchronization architecture for the O-DU7-2. At the top, a 'GNSS' block provides a '1pps' (one pulse per second) signal to a 'PHC' (Physical Hardware Clock) block. This 'PHC' block is located within a 'NIC' (Network Interface Card) labeled 'Fronthaul'. Below this, another 'PHC' block is shown within a 'NIC' labeled 'Backhaul'. Both 'PHC' blocks are connected to a central 'System Clock' block via bidirectional arrows. The 'System Clock' block is also connected to the 'PHC' in the 'Fronthaul' NIC via a bidirectional arrow. The 'Backhaul' NIC's 'PHC' is connected to the 'System Clock' via a bidirectional arrow. The 'Fronthaul' NIC's 'PHC' is connected to the 'System Clock' via a bidirectional arrow. The 'GNSS' block is connected to the 'PHC' in the 'Fronthaul' NIC via a downward arrow labeled '1pps'. - -Diagram of O-DU Timing Synchronization showing GNSS, PHC, System Clock, and NIC connections. - -17 -18 **Figure 2.2.4-1 O-DU Timing Synchronization** - -19 -20 2.2.5 External Interface Ports - -21 The external interfaces of O-DU7-2 are described below. - -22 2.2.5.1 Hardware Requirements - -23 The following table shows the external ports or slots that the system provides. - -Table 2.2.5-1 External Port List - -| Item Name | Description | -|--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Ethernet | Octave Gigabit Ethernet LAN connectors
Dual 10GbE Base-T Ethernet connectors
Dual 10GbE SFP+ Faber Ethernet connectors
2x100G QSFP28 or 2x25G SFP28 | -| USB | 2 USB 3.0 ports | -| Serial Port | 1 COM port via RJ45 | -| Antenna port | 1 SMA connector for GNSS | - -### 2.2.5.2 Hardware Design - -The digital processing unit is a SoC device which provides the external ports described in the hardware requirement section. The system includes 2 USB 3.0 ports, and the serial RS232 port that can be used for Console Redirection, e.g. Out-of-Band Management. The system provides eight 1Gbps and four 10Gbps Ethernet ports. There are two or four 25G eCPRI ports in system depends on the accelerator card used. The system also provides a RF interface to connect GNSS antenna. The following diagram outlines the external interfaces that supported. - -![Diagram of O-DU z external interfaces. A central box labeled 'O-DU z' has four external connections: '2 USB 3.0 Ports' on the top left, 'Serial Port' on the bottom left, 'GNSS Antenna Port' on the top right, and 'Ethernet Ports' on the bottom right. Each connection is shown with a double-headed arrow.](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg) - -Diagram of O-DU z external interfaces. A central box labeled 'O-DU z' has four external connections: '2 USB 3.0 Ports' on the top left, 'Serial Port' on the bottom left, 'GNSS Antenna Port' on the top right, and 'Ethernet Ports' on the bottom right. Each connection is shown with a double-headed arrow. - -Figure 2.2.5-1 External Interface Reference Design - -### 2.2.6 O-DU Firmware - -BIOS and BMC firmware are needed in the system and shall be installed. - -### 2.2.7 Mechanical - -The mechanical design for mother board, chassis, and cooling are listed in this section. - -#### 2.2.7.1 Mother Board - -The mechanical layout of the mother board shows the location of major components and interface ports. The following diagram also provides the dimension of the board. - -![Mother Board Layout Diagram showing various components like VGA, COM, NIC, LAN ports, BMC, SATA, USB, and a central 45x52.5mm (SoC) block. The board is labeled with dimensions 8 inches by 10 inches.](318886a86a1dcc59e1fc83db6f157c60_img.jpg) - -The diagram illustrates the layout of a mother board within an 8" by 10" chassis. Key components and their locations are as follows: - -- Central Component:** A large rectangular block labeled "45x52.5mm (SoC)" is positioned in the center. -- Memory:** Two vertical bars labeled "DDR4 2667MHz" are located to the right of the SoC. -- Power:** An "ATX 24 pin" connector is at the bottom right, with "HDD PWR" and "5pin 2V/3pin" labels nearby. A "PWRICQ" and "USB2.0 header" are also present. -- Storage:** Four "SATA" ports are shown, two on the right side and two at the bottom. -- Network:** Eight RJ45 LAN ports are labeled "LAN1 LAN2 LAN3 LAN4 LAN5 LAN6 LAN7 LAN8". There are also "10GbE BaseT x2" and "10GbE x2 SFP+" ports. Several "NIC" (Network Interface Card) blocks are distributed across the board. -- Management:** A "BMC" (Baseboard Management Controller) block is located in the upper right area. -- Connectivity:** "VGA" and "COM" ports are on the left. "USB Typa" is on the left. "LAN LEDs /GPIO" is on the left. -- Expansion:** A long vertical block on the left is labeled "PCIe x32". -- Security:** "TPM header" and "SoC SMBus" are on the right. -- Front Panel:** A "Front Panel" section is at the bottom left, including "Fans" (labeled Fan1, Fan2, Fan3, Fan4, Fan5, Fan6). -- Dimensions:** The overall width is marked as 8" and the height as 10". - -Mother Board Layout Diagram showing various components like VGA, COM, NIC, LAN ports, BMC, SATA, USB, and a central 45x52.5mm (SoC) block. The board is labeled with dimensions 8 inches by 10 inches. - -Figure 2.2.7-1 Mother Board Layout Diagram - -1 -2 -3 -4 -5 -6 - -2.2.7.2 Chassis - -The 1U rack mount chassis contains the layout of the power supply, Solid State Drive (SSD) and fans. The chassis dimension is showed in following figure. - -![Chassis Mechanical Diagram showing internal components including Power Supply, SSD, Installed Fans, and Optional Fans. Dimensions are 437 mm (width), 381 mm (depth), and 43 mm (height).](eadd8abb2c85161842bcd823881cbe5f_img.jpg) - -Chassis Mechanical Diagram showing internal components including Power Supply, SSD, Installed Fans, and Optional Fans. Dimensions are 437 mm (width), 381 mm (depth), and 43 mm (height). - -Figure 2.2.7-2 Chassis Mechanical Diagram - -1 -2 -3 -4 -5 -6 - -### 2.2.7.3 Cooling - -The system installs 4x 40x28mm PWM fans for the cooling. Up to 6 fans can be installed if needed. - -## 2.2.8 Power Unit - -In a fully loaded system with two PCIe slots populated with 75W each, the system power consumption should be less than 400W. The total system power requirement shall be kept less than 80% of the power supply capacity. - -### 2.2.8.1 Hardware Requirements - -The O-DU requires a 500W high-efficiency power supply with Power Management Bus (PMBus) 1.2 capability. The required power input range and output power rails are listed in the table below. - -Table 2.2.8-1 Power Supply Rail Requirements - -| Item Name | Description | -|-----------|----------------------------------------------------------------------| -| AC Input | 100-240V, 50-60Hz, 6.6A max | -| DC Output | +3.3V: 12A
+5V: 15A
+5V standby: 3A
+12V: 41A
-12V: 0.2A | - -15 - -1        2.2.8.2 Hardware Design - -2        The O-DU7.2 chassis design includes one 500W power supply unit. The power supply unit is auto-switching - 3        capable, which enables it to automatically sense and operate at a 100v to 240v input voltage. The power supply - 4        unit features are listed in the following table. - -5                      **Table 2.2.8-2 Power Supply Unit Feature List** - -| Item Name | Description | -|-----------------------------|----------------------------------------------------------------| -| Output connectors | 24pin/8pin/4+4pin/HDD/I2C | -| Dimension (W x D x H) | 3.9 x 7.1 x 1.6 inch | -| Maximum Output Power | +3.3V: 12A
+5V: 15A
+12V: 41A
-12V: 0.2A
+5Vsb: 3A | -| Rated Input Voltage/Current | 100-240Vac / 6.6A max | -| Rated Input Frequency | 50-60HZ | -| Inrush current | Less than 30A | - -6 - -7        2.2.9 Thermal - -8        Active cooling with up to 6 fans is integrated in the chassis. - -9        The hardware acceleration cards described in 2.2.3.2 use passive cooling and a custom heatsink and is equipped - 10       with temperature sensors. It is designed to operate in temperatures ranging from -5°C to +55°C. - -11       2.2.10 Environmental and Regulations - -12       The O-DU7.2 hardware system is RoHS Compliant. The power supply unit is EMC FCC/CISPR Class B - 13       compliant. Table 2 10 lists the environmental related features and parameters. - -14                      **Table 2.2.10-1 Environmental Features** - -| Item Name | Description | -|---------------------------------|----------------------------| -| Operating Temperature | -5°C to +55°C | -| Non-operating Temperature | -40°C to 70°C | -| Operating Relative Humidity | 8% to 90% (non-condensing) | -| Non-operating Relative Humidity | 5% to 95% (non-condensing) | - -15 - -16       The hardware accelerator described in 2.2.3.2 is designed to operate in indoor environments and in - 17       temperatures ranging from -5°C to +55°C. - -## 2.3 O-RU7-2 Hardware Reference Design - -This chapter defines the hardware reference design for the Outdoor Microcell O-RU7-2. This is defined by a 7-2 interface to the O-DU on one side and up to 8T8R on the antenna port. Because this design is up to 10W per channel of conducted power, the external power is supplied by either AC or a standard 48V telecom source. - -### 2.3.1 O-RU7-2 High-Level Functional Block Diagram - -Figure 2.3.1-1 provides a high-level functional block diagram depicting the major HW/SW components. It also highlights the internal/external interfaces that are required. This document shows how to implement the system defined by the OMC-HAR [6] document. - -![High-Level Functional Block Diagram of O-RU7-2. The diagram shows a dashed box labeled 'O-RU7-2' containing several functional blocks: 'O-RAN FH Processing Unit', 'Digital Processing Unit', 'RF Processing Unit', 'Timing Unit', and 'Power Unit'. External connections include 'To/From O-DU7-2' via an 'O-RAN FH Interface' to the FH Processing Unit, and 'To/From Antenna' from the RF Processing Unit. An optional 'GNSS' block provides 'Local timing from GNSS or equivalent' to the Timing Unit. The Timing Unit provides 'Local timing from CDR' to the FH Processing Unit, 'Digital Processing Unit', and 'RF Processing Unit'. The Power Unit provides power to the 'Timing Unit', 'Digital Processing Unit', and 'RF Processing Unit'.](ac31fdfebb9751f7f10416dfe33bc872_img.jpg) - -High-Level Functional Block Diagram of O-RU7-2. The diagram shows a dashed box labeled 'O-RU7-2' containing several functional blocks: 'O-RAN FH Processing Unit', 'Digital Processing Unit', 'RF Processing Unit', 'Timing Unit', and 'Power Unit'. External connections include 'To/From O-DU7-2' via an 'O-RAN FH Interface' to the FH Processing Unit, and 'To/From Antenna' from the RF Processing Unit. An optional 'GNSS' block provides 'Local timing from GNSS or equivalent' to the Timing Unit. The Timing Unit provides 'Local timing from CDR' to the FH Processing Unit, 'Digital Processing Unit', and 'RF Processing Unit'. The Power Unit provides power to the 'Timing Unit', 'Digital Processing Unit', and 'RF Processing Unit'. - -Figure 2.3.1-1 High-Level Functional Block Diagram - -### 2.3.2 O-RU7-2 Hardware for FPGA Based Design - -Figure 2.3.2-1 shows a 4T4R implementation and Figure 2.3.2-2 shows an 8T8R implementation. In each of these diagrams, the Digital Processing Unit is further detailed in 2.2.3.1. Items under the umbrella of RF Processing Unit, including the Transceiver, RFFE and other RF items are reviewed in additional detail in 2.3.2.2. Clock and Synchronization are reviewed in 2.3.2.3. The Power Unit is detailed in 2.3.7. - -![Figure 2.3.2-1 4T4R General Block Diagram with full RF front end](145d00f59802048185303f15937ea65c_img.jpg) - -The diagram illustrates the internal architecture of a 4T4R (4 Transmit, 4 Receive) radio unit. The main components and their connections are as follows: - -- Digital Processing Unit:** The central processing block. It has a bidirectional external interface. It outputs "Tx enable" and "Rx enable" signals. It connects to the Transceiver via "SERDES" and "SPI" interfaces. It receives "Network Clock" and "SPI" from the Clock block and "Clean Clock" from the Synchronizer. -- Clock:** Connected to an external crystal/oscillator and ground. It provides "Network Clock" and "SPI" signals to the Digital Processing Unit. -- Synchronizer:** Connected to an external crystal and ground. It provides a "Clean Clock" to the Digital Processing Unit and connects to the Transceiver. -- Power Unit:** Provides power to the system components. -- Transceiver:** Interfaces between the digital processing and the RF front end. It has multiple ports: Rx0, Tx0, ORx0, ORx1, Tx1, and Rx1, which are duplicated for two identical RF chains shown. - - Transmit Path (Tx):** From the Transceiver (Tx0, Tx1), the signal goes through a driver amplifier, then to a Power Amplifier (PA) with an "enable" control, and finally through a circulator and filter to the antenna port. - - Receive Path (Rx):** From the antenna port, the signal goes through a filter, a circulator, and into an RF Front-End (RFFE) block. The RFFE contains a Low Noise Amplifier (LNA) and a filter. It features a "bypass" path and an "enable" control. The output goes to the Transceiver (Rx0, Rx1). - - Observation Receive Path (ORx):** Feedback paths (ORx0, ORx1) are taken from the PA outputs back to the Transceiver for monitoring/calibration. -- Port A:** Represents the four antenna ports, each equipped with a filter and antenna symbol. - -Figure 2.3.2-1 4T4R General Block Diagram with full RF front end - -**Figure 2.3.2-1 4T4R General Block Diagram with full RF front end** - -1 - -![Figure 2.3.2-2 8T8R General Block Diagram with RF front end. The diagram shows a Digital Processing Unit connected to two Transceivers via SERDES and SPI interfaces. Each Transceiver is connected to four RF front-end (RFFE) blocks, which are further connected to Power Amplifiers (PA) and Port A. The system also includes a Clock, Synchronizer, and Power Unit.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg) - -The diagram illustrates the internal architecture of an 8T8R system. On the left, a 'Digital Processing Unit' is shown with various input and output connections. It receives 'Tx enable' and 'Rx enable' signals from the top. It is connected to a 'Clock' block, a 'Synchronizer' block, and a 'Power Unit'. The 'Digital Processing Unit' is connected to two 'Transceiver' blocks via 'SERDES' and 'SPI' interfaces. Each 'Transceiver' block is connected to four 'RF FE' (Radio Frequency Front End) blocks. Each 'RF FE' block is connected to a 'PA' (Power Amplifier) and a 'Port A'. The 'RF FE' blocks also have 'bypass' and 'enable' inputs. The 'Port A' labels are on the right side of the diagram, indicating the output ports for the RF signals. - -Figure 2.3.2-2 8T8R General Block Diagram with RF front end. The diagram shows a Digital Processing Unit connected to two Transceivers via SERDES and SPI interfaces. Each Transceiver is connected to four RF front-end (RFFE) blocks, which are further connected to Power Amplifiers (PA) and Port A. The system also includes a Clock, Synchronizer, and Power Unit. - -Figure 2.3.2-2 8T8R General Block Diagram with RF front end - -2 - -3 - -4 - -5 - -6 - -Figure 2.3.2-3 shows an example of an high-level block details of an O-RU Hardware implementation. The description of each block from left to right is given below. - -An O-RU7.2 communicate with the O-DU7.2 through the O-RAN Fronthaul interface and the control/data packets are processed by the O-RAN Fronthaul unit with the help of the CUS plane processing block. Subsequently the packets are processed by the low-PHY functional blocks such as encoding, scrambling, modulation, layer mapping, precoding, beamforming, and resource element mapping in the downlink. Exactly the reverse operation is done during the uplink process. The output of the low-PHY block is fed to the digital processing unit through packet interface. Here the frequency conversion in digital domain i.e., digital up conversion (DUC) in DL and digital down conversion (DDC) in UL are done. Furthermore, DPD and CFR algorithms are implemented in the digital processing unit to enhance the power amplifier efficiency by reducing the PAPR/ACLR in the RF front end. The output of digital processing unit is fed to the RF processing unit through the digital interface. The digital signals are converted to analog in the DL and vice versa in the UL with the help of DAC and ADC functional blocks in the Transceiver unit, respectively. The signals are further amplified with the help of functional blocks like the PA in DL and LNA in UL both of which are part of the analog RF front end unit. The output of the power amplifier is fed to cavity filter to suppress the unwanted signals in DL and is done before amplification in the case of UL operation i.e., receive operation to improve selectivity. The TDD switch is used to switch the operation between DL and UL, i.e., transmit and receive operations. The output of the cavity filter is fed to antenna unit and then transmitted over the air. The processing units such as FH, Digital, and RF powered from the power unit and clocking and synchronization is provided from the timing/synchronization block. In the case of a beamforming scenarios, antenna calibration is implemented using the antenna calibration processing block. This coordinates with the low-PHY processing unit and calibration switch (Cal switch) and process the signals coming from and going to the antenna calibration port to compensate the amplitude and phase offsets existing in each RF chain. Other implementations are also possible by rearranging the functional blocks of O-RAN FH, Digital processing, and RF processing units. - -![Block diagram of O-RU Architecture Example Implementation 1](9f6dec4d4e9fde40bce018861ef1278e_img.jpg) - -``` - -graph LR - subgraph O-RU7.2x - subgraph FH_Unit [O-RAN Fronthaul Processing Unit] - eCPRI[eCPRI C-Plane, S-Plane, and M-Plane Processing] - LowPhy[Low-Phy Processing] - eCPRI --> LowPhy - end - - subgraph Digital_Unit [Digital Processing Unit] - PacketInt[Packet Interface] - DDC[DDC] - DUC[DUC] - DPD[DPD] - CFR[CFR] - PacketInt --> DDC - PacketInt --> DUC - DDC --> DPD - DUC --> CFR - end - - subgraph RF_Unit [RF Processing Unit] - DigitalInt[Digital Interface] - Transceiver[Transceiver DAC ADC] - PA_LNA[PA+LNA & TDD Switch] - CavityFilter[Cavity Filter] - Filter[Filter] - DigitalInt --> Transceiver - Transceiver --> PA_LNA - PA_LNA --> CavityFilter - CavityFilter --> Filter - end - - PowerUnit[Power Unit] - TimingSync[Timing/Sync. Unit] - AntCal[Antenna Calibration Processing] - CalSwitch[CAL Switch] - Antenna[Antenna] - - FH_Unit -- Packet Interface --> Digital_Unit - Digital_Unit -- Digital Interface --> RF_Unit - RF_Unit --> Antenna - - TimingSync --> FH_Unit - TimingSync --> Digital_Unit - TimingSync --> RF_Unit - - PowerUnit --> FH_Unit - PowerUnit --> Digital_Unit - PowerUnit --> RF_Unit - - AntCal --> LowPhy - AntCal --> CalSwitch - CalSwitch --> Transceiver - Antenna -- Calibration Port --> AntCal - end - - ODU[To/From O-DU7.2] -- O-RAN FH interface --> FH_Unit - -``` - -Block diagram of O-RU Architecture Example Implementation 1 - -Figure 2.3.2-3 O-RU Architecture Example Implementation 1 - -### 2.3.2.1 Digital Processing Unit - -The digital processing unit of the O-RU7.2 performs the fronthaul interface, lower L1, Synchronization, RF interface, antenna calibration, digital beamforming and OAM. The following block diagram describes the digital processing unit as per example implementation in - -1 - -![Figure 2.3.2-4: Digital Processing Unit Block Diagram (L1 Processing + optional Beamforming). The diagram shows a central FPGA/ASIC block. On its left, a CPU block is connected to Boot Flash, DDR, OAM, and an SFP/QSFP interface labeled '10/25 GBPS'. On the right side of the FPGA/ASIC, there is a dashed box labeled 'L1 Proc. + Beamforming'. Below this box, the FPGA/ASIC connects to three external blocks: 'eCPRI/CPRI' to a 'DFE' block, 'Clock & Control' to a 'Clock & Sync' block, and 'Data & Control' to an 'Antenna Calibration' block.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg) - -Figure 2.3.2-4: Digital Processing Unit Block Diagram (L1 Processing + optional Beamforming). The diagram shows a central FPGA/ASIC block. On its left, a CPU block is connected to Boot Flash, DDR, OAM, and an SFP/QSFP interface labeled '10/25 GBPS'. On the right side of the FPGA/ASIC, there is a dashed box labeled 'L1 Proc. + Beamforming'. Below this box, the FPGA/ASIC connects to three external blocks: 'eCPRI/CPRI' to a 'DFE' block, 'Clock & Control' to a 'Clock & Sync' block, and 'Data & Control' to an 'Antenna Calibration' block. - -Figure 2.3.2-4 Digital Processing Unit Block Diagram (L1 Processing + optional Beamforming) - -2 - -3 - -4 - -![Figure 2.3.2-5: Digital Processing Unit Block Diagram (DFE). The diagram shows a central FPGA/ASIC block. On its left, a CPU block is connected to Boot Flash, DDR, OAM, and a 'Digital Processing' block. The 'Digital Processing' block connects to the FPGA/ASIC via an 'eCPRI/CPRI' interface. On the right side of the FPGA/ASIC, there is a dashed box labeled 'DFE'. Below this box, the FPGA/ASIC connects to two external blocks: 'JESD204B/C' to a 'DFE' block, and 'Clock & Control' to a 'Clock & Sync' block.](132cff7e872feb31f629703959beddd7_img.jpg) - -Figure 2.3.2-5: Digital Processing Unit Block Diagram (DFE). The diagram shows a central FPGA/ASIC block. On its left, a CPU block is connected to Boot Flash, DDR, OAM, and a 'Digital Processing' block. The 'Digital Processing' block connects to the FPGA/ASIC via an 'eCPRI/CPRI' interface. On the right side of the FPGA/ASIC, there is a dashed box labeled 'DFE'. Below this box, the FPGA/ASIC connects to two external blocks: 'JESD204B/C' to a 'DFE' block, and 'Clock & Control' to a 'Clock & Sync' block. - -Figure 2.3.2-5 Digital Processing Unit Block Diagram (DFE) - -5 - -6 - -7 - -### 2.3.2.1.1 FPGA/ASIC Solution - -8 - -This solution for the digital processing unit is based on an FPGA with embedded ARM processor. - -9 - -#### 2.3.2.1.1.1 FPGA Specifications - -10 - -Table 2.3.2-2 shows the general interfaces required for an FPGA based design based on Figure 2.3.2-4 and Figure 2.3.2-5. - -11 - -12 - -1 - -**Table 2.3.2-1 FPGA Interface Specifications** - -| Item Name | Description | -|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| eCPRI Port | High speed bi-directional interface transporting data and control information. Total payload will be determined by the antennas/layers served, bandwidth supported, bit precision, subcarrier spacing, etc. It is typically served by one or more QSFP+ or SFP28 connectors depending on the payload. | -| SERDES | Up to 16 high speed JESD204B/C serial interface lanes between FPGA fabric and transceiver depending on transceiver configuration selected. | -| Boot Clock | Clock for any uC or fabric functions required immediately at power on | -| Sysref | JESD204B/C synchronization signal | -| DevCLK | JESD204B/C device clock | -| ARM Clock | Clock for the ARM processor | -| Memory Clock | Memory clock | -| OAM Port | Control interface used for maintenance | -| DDR | Interface for external DDR memory | - -2 - -3 - -#### 2.3.2.1.1.2 FPGA Design - -4 - -Table 2.3.2-2 shows the general blocks required for the design. The core elements implemented in this design - -5 - -are required to be sized to support the requirements shown in the OMC-HAR [6] document. Specifically, the - -6 - -DPU should support up to 200 MHz of occupied BW with up to two 100 MHz component carriers. In addition - -7 - -to signal processing, the DPU should support C, U, S and M plane handling. Major processing blocks in the - -8 - -DPU are shown in Table 2.3.2-2. - -1 - -**Table 2.3.2-2 FPGA Functional Blocks** - -| Item Name | Description | Cat A | Cat B | -|-----------------|-----------------------------------------------------------------|----------|----------| -| FFT & CP- | FFT and Cyclic Prefix removal for uplink processing | Required | Required | -| iFFT & CP+ | iFFT and Cyclic Prefix insertion for downlink processing | Required | Required | -| PRACH Front End | PRACH front end processor | Required | Required | -| Channel DDC | Component Carrier Digital Down Converter | Optional | Optional | -| Channel DUC | Component Carrier Digital Up Converter | Optional | Optional | -| JESD204B/C | JEDEC High speed serial interface type B or C framer/de-framer | Required | Required | -| CFR | Crest Factor Reduction | Optional | Optional | -| DPD | Digital Pre-Distortion | Optional | Optional | -| C/U/M Plane | Control, User and management Plane processing | Required | Required | -| 1588v2 Stack | IEEE 1588v2 Synchronization Software Stack | Required | Required | -| eCPRI | evolved Common Public Radio Interface framer/de-framer | Required | Required | -| I/Q Compression | I/Q compression/decompression for fronthaul lane rate reduction | Optional | Optional | -| Beamforming | Create & steer several beams | Optional | Optional | -| Pre-coding | Pre-coding | Optional | Required | -| RE Mapping | Resource Element Mapping to Antenna port | Optional | Required | - -2 - -3 - -### 2.3.2.2 RF Processing Unit - -4 - -The RF Processing Unit of O-RU7.2 includes the power amplifier (PA), low noise amplifier (LNA), Tx/Rx filters and conversion between analog and digital domain. Physical and logical partitioning within the RF processing unit need not occur at any specific boundary. - -5 - -6 - -#### 2.3.2.2.1 Transceiver Reference Design - -7 - -For the O-RU7.2 the sampling function and frequency conversion function is performed by transceiver. The purpose of the transceiver is to translate the RF signal to digital as early as possible in the signal chain and to reduce the data rate as low as possible to save power. The Transceiver is to convert between high-speed baseband data and a low-level RF for both transmit and receive signal chain. The transceiver may be responsible for orchestration of external gain control elements in both the receive and transmit paths. Other radio functions may need to be controlled by the FPGA/ASIC where they need to be control fast and synchronized with the TDD frame structure. Such elements include the transmit / receive switch, PA and LNA enable. - -8 - -9 - -##### 2.3.2.2.1.1 Hardware Specifications - -10 - -11 - -###### 2.3.2.2.1.1.1 Interface - -12 - -13 - -14 - -15 - -16 - -17 - -18 - -**Table 2.3.2-3 RF Processing Unit Interface Specifications** - -| Item Name | Description | -|-----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| High Speed Data (SERDES Out, SERDES In) | High speed data represents the baseband information being transmitted or received. Depending on the configuration of the ORAN device, various bandwidths may be supported leading to a range of payload | - -| | | -|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | rates. Options for data include JESD204B and JESD204C. Up to 8 lanes in each direction may be supported although fewer is preferred. Options such as DPD and numeric precision will impact the payload rate. Several options are shown in the following table. All data represents IQ 16-bit (N=16) precision. Some devices support IQ 12 bit (N'=12) which may reduce the required data rates accordingly. | -| Reference Clock (REF Clock In) | The transceiver should receive a reference for internal clock and LO synthesis needs. This reference clock can function as the JESD204 Device Clock where the interface is by SERDES. The specific clock frequency is determined by the operation mode of the transceiver. | -| SYSREF | If the transceiver supports SERDES, then it should accept a SYSREF signal from the clock or data source as appropriate. The number and configuration for the SYSREF is dependent on the operating mode of the transceiver. | -| SYNC\ | If the transceiver supports SERDES, then it should also support a SYNCH for each link as appropriate. | -| Control (SCLK, CSB, SDO, SDIO, etc) | Control of the transceiver is by way of 3 or 4 wire SPI or I2C functioning as a slave. Support for 1.8V control is required and tolerance of 3.3V is preferred. The transceiver may optionally include a separate SPI master for control of peripheral devices as required. | -| GPIO (GPIO 1 – GPIO #) | The transceiver may optionally include GPIO for controlling peripherals including but not limited to PAs, LNAs and other devices. These GPIOs should at a minimum support 1.8V outputs but the specifics will be determined by the connected devices. The GPIO should also support input from peripheral devices. Input should at a minimum support 1.8V logic with tolerance of 3.3V preferred. | -| Tx Enable | The transceiver should provide an output to support enabling and disabling the external devices in the transmit chain such as a TxVGA (optional) and PA. This may be part of the GPIO pins. | -| Rx Enable | The transceiver should provide an output to support enabling and disabling the external devices in the transmit chain such as a RF Front End Module or LNA. This may be part of the GPIO pins. | -| LNA Bypass | The transceiver should provide an output to support bypassing the LNA appropriately in the condition of a large blocker if so required. This may be part of the GPIO pins. | -| RF Outputs (Tx1 – Tx4) | RF outputs including the main Tx signal should support 50 ohm or 100 ohms signalling. These outputs can be either single ended or differential. | -| RF Inputs (Rx1 – Rx4 & ORx 1 – ORx4) | RF inputs including the main Rx and the Observation Rx (ORx) (for DPD) should support 50 ohm or 100 ohms signalling. These inputs can be either single ended or differential. The device should support at least 1 ORx. | - -Table 2.3.2-4 JESD204B/C Serial Data Rates - -| Bandwidth | JESD204B | JESD204C | JESD204B | JESD204C | -|-----------|----------|----------|----------|----------| -| | 4T4R | | 8T8R | | -| 20 | 4.9152 | 4.05504 | 9.8304 | 8.11008 | -| 50 | 9.8304 | 8.11008 | 19.6608 | 16.22016 | -| 100 | 19.6608 | 16.22016 | 39.3216 | 32.44032 | -| 200 | 39.3216 | 32.44032 | 78.6432 | 68.88064 | - -2.3.2.2.1.1.2 Algorithm - -The transceiver is required to provide appropriate algorithms to sustain RF operation including but not limited to Rx AGC, Tx Power control, DPD and CFR. - -2.3.2.2.1.1.3 Device Configuration - -The transceiver should support either 4T4R or 8T8R. In addition, at least one ORx path should be provided to support DPD functionality. - -2.3.2.2.1.1.4 Power Dissipation - -Total dissipation of the TRx should be less than 6W for 4T4R. - -2.3.2.2.1.1.5 RF Specifications - -Table 2.3.2-5 Transceiver RF Specifications - -| Parameter | Symbol | Min | Typ | Max | Unit | Test Condition/Comment | -|--------------------------------------------------|--------|-----|--------|------|--------|--------------------------------------------------------------------------------------------------------------| -| Transmitters | | | | | | | -| Center Frequency | | 650 | | 6000 | MHz | | -| Transmitter Synthesis Bandwidth | | | | 450 | MHz | | -| Transmitter Large Signal Bandwidth | | | | 200 | MHz | | -| Transmitter Attenuator Power Control Range | | 0 | | 32 | dB | Signal to noise ratio (SNR) maintained for attenuation between 0 and 20 dB | -| Transmitter Attenuation Power Control Resolution | | | 0.05 | | dB | 20 MHz LTE/NR at -12 dBFS | -| Adjacent Channel Leakage Ratio (ACLR) | | | -66 | | dB | 75 MHz < f ≤ 2800 MHz | -| In Band Noise Floor | | | -154.5 | | dBm/Hz | 0 dB attenuation; in band noise falls 1 dB for each dB of attenuation for attenuation between 0 dB and 20 dB | -| Out of Band Noise Floor | | | -153 | | dBm/Hz | 600 MHz < f ≤ 3000 MHz | - -| Parameter | Symbol | Min | Typ | Max | Unit | Test Condition/Comment | -|----------------------------------------------------|-------------------|-----|-------|------|------|----------------------------------------------------------------------------------------------------------------------------------| -| Maximum Output Power | | | 6 | | dBm | 0 dB attenuation; 3 × bandwidth/2 offset | -| Third Order Output Intermodulation Intercept Point | OIP3 | | 27 | | dBm | 600 MHz < f ≤ 3000 MHz | -| Error Vector Magnitude (3GPP Test Signals) | EVM | | | | | | -| 1900 MHz LO | | | 0.6 | | % | 50 kHz RF PLL loop bandwidth | -| 3800 MHz LO | | | 0.53 | | % | 300 kHz RF PLL loop bandwidth | -| Observation Receivers | ORx | | | | | | -| Center Frequency | | 450 | | 6000 | MHz | | -| Gain Range | | | 30 | | dB | IIP3 improves dB for dB for the first 18 dB of gain attenuation; QEC performance optimized for 0 dB to 6 dB of attenuation only. | -| Analog Gain Step | | | 0.5 | | dB | For attenuation steps from 0 dB to 6 dB | -| Receiver Bandwidth | | | | 450 | MHz | | -| Maximum Usable Input Level | P HIGH | | -11 | | dBm | 0 dB attenuation; increases dB for dB with attenuation. | -| Integrated Noise | | | -58.7 | | dBFS | 450 MHz Integration bandwidth | -| | | | -57.5 | | dBFS | 491.52 MHz Integration bandwidth | -| Third Order Input Intermodulation Intercept Point | IIP3 | | | | | | -| Narrow Band | | | | | | Maximum observation receiver gain; test condition: P HIGH -11 dB/tone | -| 1900 MHz | | | 15 | | dBm | | -| 2600 MHz | | | 16.5 | | dBm | | -| 3800 MHz | | | 18 | | dBm | | -| Wide Band | | | | | | IM3 products > 130 MHz at baseband; test condition: P HIGH - 11 dB/tone; 491.52 MSPS | -| 1900 MHz | | | 13 | | dBm | | -| 2600 MHz | | | 11 | | dBm | | -| 3800 MHz | | | 13 | | dBm | | -| Third Order Intermodulation Product | IM3 | | -70 | | dBc | 600 MHz < f ≤ 3000 MHz | - -| Parameter | Symbol | Min | Typ | Max | Unit | Test Condition/Comment | -|-----------------------------------------|------------|-----|-----|------|------|------------------------------------------------------------------------------------------------------------------| -| Spurious Free Dynamic Range | SFDR | | 64 | | dB | Non IMx related spurs, does not include HDx; ( $P_{HIGH} - 11$ ) dB input signal | -| Harmonic Distortion Second Order | HD2 | | -80 | | dBc | ( $P_{HIGH} - 11$ ) dB input signal
In band HD falls within $\pm 100$ MHz | -| Harmonic Distortion Product | | | -73 | | dBc | Out of band HD falls within $\pm 225$ MHz | -| Third Order Harmonic Distortion Product | HD3 | | -70 | | dBc | In band HD falls within $\pm 100$ MHz | -| | | | -65 | | dBc | Out of band HD falls within $\pm 225$ MHz | -| Receivers | | | | | | | -| Center Frequency | | | | 6000 | MHz | | -| Analog Gain Step | | | 30 | | dB | Attenuator steps from 0 dB to 6 dB | -| | | | 1 | | dB | Attenuator steps from 6 dB to 30 dB | -| Receiver bandwidth | | | | 200 | MHz | | -| Maximum Usable Input Level | $P_{HIGH}$ | | | | | 0 dB attenuation; increase dB for dB with attenuation; continuous wave = 1800 MHz; corresponds to -1 dBFS at ADC | -| Noise Figure | NF | | -11 | | dBm | 75 MHz $< f \leq 3000$ MHz | -| Input Third Order Intercept Point | IIP3 | | 12 | | dB | 0 dB attenuation at receiver port
600 MHz $< f \leq 3000$ MHz | -| Difference Product | IIP3, d | | | | | Two ( $P_{HIGH} - 9$ ) dB tones near band edge | -| 2600 MHz (Wideband) | | | 17 | | dBm | | -| 2600 MHz (Midband) | | | 21 | | dBm | | -| Sum Product | IIP3, s | | | | | Two ( $P_{HIGH} - 9$ ) dB tones, at bandwidth/6 offset from the LO | -| 2600 MHz (Wideband) | | | 20 | | dBm | | -| HD3 | HD3 | | | | | ( $P_{HIGH} - 6$ ) dB continuous wave tone at bandwidth/6 offset from the LO | -| | | | -66 | | dBc | 600 MHz $< f \leq 4800$ MHz | - -1 -2 -3 -4 -5 -6 - -2.3.2.2.1.2 Hardware Design - -For the O-RU7.2 the sampling function and frequency conversion function can be performed by the transceiver. The transceiver integrates the ADC, DAC, LO, down converter, up converter and related functions. The block diagram of transceiver design is shown in Figure 2.3.2-6. - -![Block diagram of a transceiver with integrated CFR and DPD. The diagram shows internal components including Clock, Synchronization & Synthesis; multiple Receiver Blocks (1-4) with mixers and ADCs; multiple Transmit Blocks (1-4) with mixers and DACs; an Observation Receiver; Decimation/pFIR/AGC/Tuning/RSSI/Overload/Device Management blocks; an Interpolation/pFIR/Tuning/Device Management block; a DPD Engine; and external interfaces like SPI Port, Control Interface, and JESD204B/C Serial Interface. External pins include REF Clock, SRE, Ext LO/Clock In, Rx1-Rx4, Tx1-Tx4, ORx1-ORx4, SCLK, CSB, SDO, SDIO, GPIO1-3, GPIO#, SYNC IN, SERDES Out/In, and SYNC OUT.](69e5f1993021af230d08c08aac97d9df_img.jpg) - -Block diagram of a transceiver with integrated CFR and DPD. The diagram shows internal components including Clock, Synchronization & Synthesis; multiple Receiver Blocks (1-4) with mixers and ADCs; multiple Transmit Blocks (1-4) with mixers and DACs; an Observation Receiver; Decimation/pFIR/AGC/Tuning/RSSI/Overload/Device Management blocks; an Interpolation/pFIR/Tuning/Device Management block; a DPD Engine; and external interfaces like SPI Port, Control Interface, and JESD204B/C Serial Interface. External pins include REF Clock, SRE, Ext LO/Clock In, Rx1-Rx4, Tx1-Tx4, ORx1-ORx4, SCLK, CSB, SDO, SDIO, GPIO1-3, GPIO#, SYNC IN, SERDES Out/In, and SYNC OUT. - -Figure 2.3.2-6 Transceiver with Integrated CFR and DPD - -7 -8 -9 - -1 2.3.2.2.2 Power Amplifier (PA) Reference Design - -2 2.3.2.2.2.1 Hardware Specifications - -3 2.3.2.2.2.1.1 Interface - -4 **Table 2.3.2-6 Power Amplifier Interface Specifications** - -| Item Name | Description | -|-----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| RF Enable | The enable input should be compatible with 1.8V logic and tolerate 3.3V as required. A logic high enables the PA. A logic low disables the device and places it in a minimum dissipation mode. | -| RF Output | RF outputs support 50-ohm single ended to properly interface to a directional coupler, isolator, switch or antenna. | -| RF Input | RF inputs should support 50-ohm, single ended match to the transceiver output or preamp. | - -5 2.3.2.2.2.1.2 Power Specifications - -6 RF output power required is nominally 10 W (40 dBm). DC power is driven by efficiency of the PA and -7 should not be more than 27W and the efficiency should be greater than 37%. - -8 2.3.2.2.2.1.3 RF Specifications - -9 The PA and driver should have enough gain to boost the transceiver output to the rated power level. The -10 output power should be at least 10W (40 dBm) including the loss of the circulator and antenna filter. The -11 ACLR with DPD and CFR should be better than 47dBc according to the related 3GPP test models. - -12 **Table 2.3.2-7 Power Amplifier RF Specifications** - -| Item Name | n 77, 48 | n 41 | -|--------------------|-------------------------|--------------------------------| -| Gain | >60 dB including driver | To be provided in next version | -| P3dB | 51 dBm | | -| Input Return Loss | <-15 dB | | -| Output Return Loss | <-15 dB | | -| Switching Speed | <1uS | | -| HD2 | >28 dBc | | -| HD3 | >30 dBc | | - -13 2.3.2.2.2.2 Hardware Design - -14 RFin is the input of the PA, RFout is the output of the PA. Vdd and Vbias is the power input of the PA. PAenable -15 is the control pin to disable or enable the PA. The input and output should be matched to 50 ohms to optimize -16 return loss as much as possible. Proper decoupling shall be provided to minimize impact of supply ripple on -17 the RF output. - -![Schematic diagram of a Power Amplifier Reference Design. It shows a central amplifier triangle with four external connections: RFin (input) on the left, RFout (output) on the right, Vdd (power supply) at the top, and Vbias (bias voltage) at the bottom. An additional label RFen (enable) is shown with a line pointing to the bottom input of the amplifier triangle.](01e00200a536673d6cd0e6d8705047a0_img.jpg) - -Schematic diagram of a Power Amplifier Reference Design. It shows a central amplifier triangle with four external connections: RFin (input) on the left, RFout (output) on the right, Vdd (power supply) at the top, and Vbias (bias voltage) at the bottom. An additional label RFen (enable) is shown with a line pointing to the bottom input of the amplifier triangle. - -Figure 2.3.2-7 Power Amplifier Reference Design - -1 -2 -3 -4 -5 -6 - -2.3.2.2.3 Low Noise Amplifier (LNA) Reference Design - -2.3.2.2.3.1.1 Interface - -Table 2.3.2-8 LNA Interfaces - -| Item Name | Description | -|-------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Enable | The enable input should be compatible with 1.8V logic and tolerate 3.3V as required. A logic high enables the LNA. A logic low disables the device and places it in a minimum dissipation mode. | -| LNA Bypass | The LNA Bypass skips the second stage LNA effectively reducing the overall gain. This would be selected when the input signal compromises the linearity of the amplifier. | -| RF Out | RF outputs support 50-ohm single ended to properly interface to the RF filtering and Rx input port of transceiver. | -| TR Switch | The TR switch is used to shunt any reflected RF power that reaches the LNA to a shunt load during the transmit period. | -| RF Input | RF inputs should support 50-ohm, single ended match to circulator. | -| Termination | This RF output port shunts any reflected transmit power to an appropriate load during the Transmit period to protect the input of the LNA. | - -7 -8 -9 - -2.3.2.2.3.1.2 Power Specifications - -DC power per channel should not exceed 0.5W. - -1 2.3.2.2.3.1.3 RF Performance Specifications - -2 Table 2.3.2-9 LNA RF Specifications - -| Item Name | n 77, 48 | n 41 | -|------------------|------------|--------------------------------| -| Gain (High/Low) | 32/16 dB | To be provided in next version | -| NF (High/Low) | 1.5/1.5 dB | | -| OIP3 (High/Low) | 31/31 dBm | | -| OP1dB (High/Low) | 18/13 dBm | | -| TR Switch Time | <1uS | | - -3 -4 2.3.2.2.3.2 Hardware Design - -5 Figure 2.3.2-8 shows the configuration for a dual-stage LNA. The RF inputs and outputs should be properly -6 matched to optimize the noise performance and flatness of the amplifier. The input switch is used to forward -7 any reflected transmit energy to an external load during the transmit period to protect the LNA from damage. -8 The DC supply voltage, VCC, should be properly filtered to prevent power supply noise from entering the -9 LNA and reducing performance. - -![Circuit diagram of an LNA reference design. It shows an RF input (RF_in) connected to a switch. One position of the switch connects RF_in to the input of a dual-stage LNA. The other position connects RF_in to a termination load (Termination_ext). A transmit (TR) signal controls the switch. The LNA has a power supply input (VCC), an enable input (LNAEN), and a bypass input (LNA_bypass). The output of the LNA is labeled RF_out.](fd76efce549d3713543bb5ed9b023c2e_img.jpg) - -Circuit diagram of an LNA reference design. It shows an RF input (RF\_in) connected to a switch. One position of the switch connects RF\_in to the input of a dual-stage LNA. The other position connects RF\_in to a termination load (Termination\_ext). A transmit (TR) signal controls the switch. The LNA has a power supply input (VCC), an enable input (LNAEN), and a bypass input (LNA\_bypass). The output of the LNA is labeled RF\_out. - -10 Figure 2.3.2-8 LNA Reference Design - -11 -12 -13 2.3.2.2.4 Circulator Reference Design - -14 For TDD use, the Tx and Rx links work in time duplex. To properly couple the Tx energy to the antenna and -15 the Rx signal to the LNA input, a circulator is used to perform this function given the potentially high RF -16 power being processed through this device. The circulator can be configured as a clockwise or -17 counterclockwise device depending on the layout details. - -18 2.3.2.2.4.1 Hardware Specifications - -19 2.3.2.2.4.1.1 Interface - -20 The circulator includes 3 ports that can function as an input or an output. If the device is labelled clockwise, -21 then for each input, its nominal output is the next pin rotating right around the device. If it is counterclockwise, -22 the nominal output is the next pin rotating to the left around the device. - -1 2.3.2.2.4.1.2 RF Specifications - -2 **Table 2.3.2-10 Circulator Specifications** - -| Item Name | n 77, 48 | n 41 | -|----------------|--------------|--------------------------------| -| Rotation | CW or CCW | To be provided in next version | -| Average Power | Up to 46 dBm | | -| Peak Power | 52 dBm | | -| Impedance | 50 ohms | | -| Insertion Loss | -0.3 dB | | -| Isolation | 20 dB | | -| Return Loss | 22 dB | | - -3 - -4 2.3.2.2.4.2 Hardware Design - -5 The example on the left in Figure 2.3.2-9 is a clockwise oriented device. The RF input enters pin 1 and exits -6 pin 2. Pin 2 can also be used as an input and its output is pin 3. Finally pin 3 can also function as an input -7 with pin 1 being the output. The device on the right is counterclockwise oriented and the signal flow is the in -8 the opposite direction. - -![Figure 2.3.2-9 Circulator Reference Design. Two diagrams of circulators. The left diagram shows a clockwise oriented circulator with pins 1 (top), 2 (bottom right), and 3 (bottom left). A curved arrow inside the circle points clockwise from pin 1 to pin 2. The right diagram shows a counterclockwise oriented circulator with the same pin configuration. A curved arrow inside the circle points counterclockwise from pin 1 to pin 3.](78e846f2858d131dc5a4dcbabcca1e4d_img.jpg) - -Figure 2.3.2-9 Circulator Reference Design. Two diagrams of circulators. The left diagram shows a clockwise oriented circulator with pins 1 (top), 2 (bottom right), and 3 (bottom left). A curved arrow inside the circle points clockwise from pin 1 to pin 2. The right diagram shows a counterclockwise oriented circulator with the same pin configuration. A curved arrow inside the circle points counterclockwise from pin 1 to pin 3. - -9 **Figure 2.3.2-9 Circulator Reference Design** - -10 - -11 - -12 2.3.2.2.5 Antenna / Phased Array Reference Design - -13 The antenna is a transducer, and it is used to convert electrical signal to the Electromagnetic waves during the -14 transmit mode and vice versa in the reception mode. radiate the TX power and to receive the RX signal. Based -15 on the radiation pattern characteristics of the antenna, it is broadly classified as omni-directional and directional -16 antennas and examples of such antennas are Two options are listed below for reference. - -17 2.3.2.2.5.1 Hardware Specifications for Omnidirectional Antenna - -18 The following table shows the typical electrical omnidirectional antenna specifications for the O-RU7.2. - -1 - -**Table 2.3.2-11 Omnidirectional Antenna Specifications** - -| Frequency band | n 77 | n 48 | n 41 | -|-----------------------|-----------------|-----------------|--------------------------------| -| Antenna Type | Omnidirectional | Omnidirectional | To be provided in next version | -| VSWR (max) | 1.5:1 | 1.5:1 | | -| Power capacity | ≥10 W | ≥10 W | | -| Gain (max) | 5.5 dBi | 5.5 dBi | | -| Beam width (vertical) | 35° | 35° | | -| Polarization | ±45° | ±45° | | - -2 - -3 - -2.3.2.2.5.1.1 Hardware Design for Omnidirectional Antenna - -4 - -One possible choice of the omnidirectional antenna is a cannister type with multiple ports including the 4 ports for the 4T4R radio. Conceptual design is shown in the following figure. - -5 - -![A 3D rendering of a dark grey cylindrical antenna. At the base of the cylinder, four small rectangular ports are visible, arranged in a square pattern.](da0c058ea922c6a070a172412990e535_img.jpg) - -A 3D rendering of a dark grey cylindrical antenna. At the base of the cylinder, four small rectangular ports are visible, arranged in a square pattern. - -6 - -7 - -**Figure 2.3.2-10 Canister Style Omni Antenna** - -8 - -9 - -10 - -2.3.2.2.5.2 Hardware Specifications for Directional Antenna - -11 - -The following table shows the typical electrical directional antenna specifications for the O-RU7-2. - -Table 2.3.2-12 Directional Antenna Specifications - -| Frequency band | n 77 | n 48 | n 41 | -|------------------------------------------------|------------------------------------------------|------------------------------------------------|------------------------------------------------| -| Antenna Type | Directional | Directional | To be provided in next version | -| Antenna with Embedded RET & AISG[10] Compliant | Antenna with Embedded RET & AISG[10] Compliant | Antenna with Embedded RET & AISG[10] Compliant | Antenna with Embedded RET & AISG[10] Compliant | -| VSWR (max) | 1.5:1 | 1.5:1 | 1.5:1 | -| Power capacity | ≥10 W | ≥10 W | ≥10 W | -| Gain (max) | 16 dBi | 16 dBi | 16 dBi | -| Beam width (horizontal) | 65° | 65° | 65° | -| Beam width (vertical) | 11° | 11° | 11° | -| Polarization | ±45° | ±45° | ±45° | -| Variable Tilt | 0-10 ° | 0-10 ° | 0-10 ° | -| Tilt Accuracy | ±1 ° | ±1 ° | ±1 ° | -| 3rd Order PIM, @2x43 dBm (dBc) | ≤-153 | ≤-153 | ≤-150 | -| Isolation (RF Ports) (dB) | ≥25 | ≥25 | ≥20 | - -2.3.2.2.5.2.1 Hardware Design for Directional Antenna - -One possible choice of directional antennas are the radios mounted on the back of the antenna with 4 ports for the 4T4R radio on the back of the antenna just below each radio. Conceptual design is shown in the following figure. - -![Diagram showing the mounting arrangement scenario 1 of 4T4R radios on the back of a Directional Antenna. The diagram shows a vertical antenna structure with two O-RU (Open Radio Unit) components. Arrows labeled '4T4R RF connectivity' point to the back of each O-RU, indicating the connection points for the radios.](c0c7f65c51c83fbe595b47326f6b089a_img.jpg) - -Diagram showing the mounting arrangement scenario 1 of 4T4R radios on the back of a Directional Antenna. The diagram shows a vertical antenna structure with two O-RU (Open Radio Unit) components. Arrows labeled '4T4R RF connectivity' point to the back of each O-RU, indicating the connection points for the radios. - -Figure 2.3.2-11 Mounting arrangement scenario 1 of 4T4R radios on the back of Directional Antenna - -Another possible choice of directional antennas are the radios located away from the antenna with ports for each of the 4T4R radios on the bottom cap of the antenna. Conceptual design is shown in the following figure. - -![Diagram showing a directional antenna at the top with '4T4R RF connectivity' indicated by a line. Below the antenna, two dashed boxes labeled 'O-RU' represent remote radio units. Each O-RU has four small circles at its base, representing the 4T4R radio components.](640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg) - -Diagram showing a directional antenna at the top with '4T4R RF connectivity' indicated by a line. Below the antenna, two dashed boxes labeled 'O-RU' represent remote radio units. Each O-RU has four small circles at its base, representing the 4T4R radio components. - -Figure 2.3.2-12 Mounting arrangement scenario 2 of 4T4R radios remotely mounted with Directional Antenna - -### 2.3.2.3 Internal Interfaces - -The following sections describe potentially useful optional interfaces within the white box. These optional interfaces are not required and may be used at the discretion of the manufacturer. This section is provided strictly as information only to better clarify the functionality of these interfaces. - -#### 2.3.2.3.1 Optional JESD204 Interfacing - -O-RU solutions requiring chip to chip interfacing of high-speed time domain data may benefit from utilization of JEDEC defined standard JESD204 [16]. This interface is specified for chip-to-chip interfacing that provides fast, low latency and time aligned data. The benefit of such an interface is to enable an open standard that allows for devices from multiple vendors to seamlessly interface. From a logistical perspective JESD204 allows multiple devices to communicate over the same link in a multiplex fashion while preserving time alignment and providing deterministic latency. This makes JESD204 a good candidate interface for carrying the signals for multiple antennas, multiple component carriers including I and Q data. This allows for relative simplicity requiring only a few differential pairs along with a ‘device clock’ and ‘sysref’ signals to carry and synchronize all time aligned signals. - -Figure 2.3.2-13 provides an example of a typical configuration for a JESD204 configuration. The lines labeled ‘JESD for UL x2’ and ‘JESD for DL x2’ are the data bearing connections and consist of differential pairs. In this example, there are 2 differential pairs for the UL data (receiver path) and 2 differential pairs for the DL data (transmit path). These connections provide data using an embedded clock and synchronization with a transport layer coding used to ensure sufficient transitions that the embedded clock can be recovered on the receiving end. - -The second signal is labeled ‘Device Clock’. The device clock provides the frequency reference to devices in the configuration. Within the scope of JESD204, this signal provides the reference for the interface. In practice, the Device Clock also provides the frequency reference to the individual devices and is usually a - -1 multiple of 30.72 MHz. JESD204 connected devices would use this reference for both the interface as well as - 2 other frequency services within the device such as sample clocks and other PLLs. - -3 The final signal is the ‘Sysref’ which enables deterministic latency in the system. Each interconnected device - 4 uses this signal in conjunction with ‘Device Clock’ to determine exactly when the sample edge should occur. - 5 There are different ways to configure and use ‘Sysref’ to achieve different goal. For more details on - 6 configuration, see [16]. - -7 JESD204 is an evolving standard. Although it has been around for a while, as process technology evolves and - 8 data needs grow, JESD has evolved to keep pace with throughput needs. The initial variation supported up to - 9 3.125 Gbps. JESD204A brought speeds up to 6.25 Gbps. JESD204B brought throughput to 12.5 Gbps. Most - 10 recently JESD204C offers throughputs up to 32.45 Gbps. Each variety offers at least one option for transport - 11 layer coding like 8B/10B as well as a range of other features including sub-channel coding which allows - 12 control channels to be passed along with the primary data. Currently most devices support JESD204B and - 13 JESD204C. As of this writing, JEDEC is underway defining the next phase of JESD204x which will further - 14 increase data rates as demanded by increasing bandwidth in wireless and other application. - -15 **Table 2.3.2-13 JESD204 Abridged Lexicon** - -| Parameter | Description | -|------------|--------------------------------------------------| -| M | Number of converters/converter device (link) | -| NP (or N') | Total number of bits per sample | -| S | Samples transmitted/single converter/frame cycle | -| F | Octets/Frame | -| K | Number of frames per multi-frame | -| SC | Sample Clock Rate | -| L | Number of lanes/converter device (link) | - -16 To better comprehend the JESD204 standard, understanding the lexicon is important. There are many - 17 parameters that can be used, but those in Table 2.3.2-13 provide the core definitions. Most of these are basic - 18 parameters related to common data converter characteristics and include the number of converters, number of - 19 bits and sample rate. The remaining parameters are related to the transport layer and physical implementation - 20 of the interface. - -21 Combined, the parameters in this lexicon help define the data throughput, number of lanes required as well as - 22 the framing of data onto the interfaces. Starting with the payload, it is determined by computing the serial data - 23 rate and adding the transport layer (ie 8B/10B, 64B/66B etc) to that as defined in the following equation: - -$$24 \quad M \times NP \times SC \times Transport Layer Coding = Payload Rate$$ - -25 This equation provides the total payload to be delivered between devices. This data is delivered over one or - 26 more lanes. If the payload exceeds the capacity of one lane, additional lanes are added to ensure that the - 27 throughput per lane matches the capability of the standard. As highlighted in preceding paragraphs, currently - 28 JESD204B supports up to 12.5 Gbps and JESD204C supports up to 32.45 Gbps but future evolutions will - 29 include higher lane capacity. Where the Payload Rate exceeds an individual lane's capacity, the total Payload - 30 Rate is divided by the lane capacity, currently 12.5 Gbps or 32.45 Gbps, to determine the approximate number - 31 of lanes required. The actual number is the next higher integer to ensure that the lane rate is less than the - -1 maximum specified or desired. As the standard continues to evolve, this same math will be used to determine - 2 the payload and number of lanes, L. - -3 -$$L = \text{Celing} \left( \frac{\text{Payload Rate}}{\text{Max Lane Rate}} \right)$$ - -4 The final important term is F, the number of octets per frame. In JESD204, an octet represents an encoded 8- - 5 bit word. Fundamentally, F defines the frame structure given the number of lanes and the specific payload to - 6 deliver. F is defined by the following equation and represents the number of octets per frame: - -7 -$$F = \frac{M \times X \times NP}{8 \times L}$$ - -8 Figure 2.3.2-13 provides an example 4T4R configuration supporting a typical 100 MHz waveform. The low - 9 PHY device processes complex (I & Q data) for each datapath and thus there are a total of 8 data streams that - 10 must be moved between the digital chip and the data conversion. The bit precision of this data is sufficient to - 11 meet the noise requirements of the solution and could be 12 or more bits. For this example, 16-bits will be - 12 assumed. To support a 100 MHz bandwidth, a complex data rate of 122.88 MSPS will be used as indicated - 13 by Table B.5.2-2 of [3]. - -![Figure 2.3.2-13 Example 4T4R JESD204 Configuration diagram showing the interconnection between a digital chip (containing ADCs and DACs) and a PHY device (DFE & Low PHY Or Low PHY) via JESD204 lanes. The diagram includes clock synthesis, system references (Sysref A, Sysref B), and connections to RFFE and Fronthaul.](0997dbaa9dfecedd60029d70b53327b8_img.jpg) - -The diagram illustrates a 4T4R JESD204 configuration. On the left, a digital chip is shown with four ADCs and four DACs. The ADCs are connected to a 'JESD PHY' block, which in turn connects to a 'Clock Synthesis' block. The DACs are also connected to a 'JESD PHY' block, which connects to a 'DFE & Low PHY Or Low PHY' block. The 'Clock Synthesis' block provides 'Device Clock A' to the ADCs and 'Device Clock B' to the DFE. It also provides 'Sysref A' to the ADCs and 'Sysref B' to the DFE. The 'JESD for UL x2' (Upstream) lanes connect the ADCs to the DFE, and the 'JESD for DL x2' (Downstream) lanes connect the DFE to the DACs. The DFE is connected to 'Fronthaul' on the right. A bracket on the left indicates the connection 'To RFFE'. - -Figure 2.3.2-13 Example 4T4R JESD204 Configuration diagram showing the interconnection between a digital chip (containing ADCs and DACs) and a PHY device (DFE & Low PHY Or Low PHY) via JESD204 lanes. The diagram includes clock synthesis, system references (Sysref A, Sysref B), and connections to RFFE and Fronthaul. - -14 - 15 **Figure 2.3.2-13 Example 4T4R JESD204 Configuration** - -16 Using this information and the equations above and applying 8B10B transport layer coding, the total payload, - 17 number of lanes and octets per frame can be computed. Since this is a 4T4R application and each path is - -1 represented by a complex stream, ‘M’ equals 8. ‘NP’ is 16 bits. ‘SC’ equals 122.88 MSPS. Total data payload - 2 can be computed using the following equation: - -$$3 \quad Payload = 8 \times 16 \times 122.88^6 \times \frac{10}{8} = 19.6608 Gbps$$ - -4 Assuming the interface is based on JESD204B, then the maximum data rate for a single lane would be 12.5 - 5 Gbps. Therefore, we need to divide the data onto two physical lanes of 9.8304 Gbps each. Hence in this - 6 example, ‘L’ equals 2. - -$$7 \quad L = Ceiling \left( \frac{19.6608 Gbps}{12.5 Gbps} \right) = 2$$ - -8 Finally, ‘F’ the number of Octets/Frame is computed to be 8. - -$$9 \quad F = \frac{8 \times 1 \times 16}{8 \times 2} = 8$$ - -10 Using this information, the mapping of data can be determined by using online tools such as [17]. These tools - 11 describe how the converter data is mapped onto each lane by octet as shown in Figure 2.3.2-14. In this example - 12 on lane 0, the first octet conveyed are the most significant bits of converter 0. This is followed by the LSBs - 13 in the second octet. This is followed by converter 1, 2 and 3 on lane 0. In parallel, lane 1 provides the data - 14 for converters 5 through 7 with the most significant octet leading. In this figure, M#SO represents the logical - 15 converter where # identifies the specific converter. - -| 4 (L = 2, M = 8, F = 8, S = 1, NP = 16) | | | | | | | | | -|------------------------------------------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------|----------------| -| Frame 0 | | | | | | | | | -| Lanes | Octet 0 | Octet 1 | Octet 2 | Octet 3 | Octet 4 | Octet 5 | Octet 6 | Octet 7 | -| | | | | | | | | | -| 0 | M0S0[15:8] | M0S0[7:0] | M1S0[15:8] | M1S0[7:0] | M2S0[15:8] | M2S0[7:0] | M3S0[15:8] | M3S0[7:0] | -| 1 | M4S0[15:8] | M4S0[7:0] | M5S0[15:8] | M5S0[7:0] | M6S0[15:8] | M6S0[7:0] | M7S0[15:8] | M7S0[7:0] | - -16 - -**Figure 2.3.2-14 4T4R Example Data Mapping** - -17 - -18 More complicated examples are also supported as shown in Figure 2.3.2-15 where an 8T8R is described. This - 19 configuration supports a 200 MHz iBW and thus requires a complex data rate of 245.76 MSPS. In this case, - 20 there are 8 transmit and 8 receive paths. Each of these requires a complex path to the low PHY device. - -1 Therefore ‘M’ equals 16. Each of these are represented by 16 bits. In this example, JESD204C is assumed - 2 and thus 64B/66B coding is used. Thus, the total throughput becomes: - -3 -$$16 \times 16 \times 245.76^6 \times \frac{66}{64} = 64.88064Gbps$$ - -![Figure 2.3.2-15 Example 8T8R JESD204 Configuration diagram. The diagram shows a central 'Clock Synthesis' block connected to 'Device Clock A' and 'Device Clock B'. 'Device Clock A' is connected to a stack of 8 ADCs and a stack of 8 DACs. 'Device Clock B' is connected to a 'DFE & Low PHY Or Low PHY' block. The ADCs are connected to the DFE via 'JESD for UL x2' lanes. The DACs are connected to the DFE via 'JESD for DL x2' lanes. The DFE is connected to 'Fronthaul'. A bracket on the left labeled 'To RFFE' groups the ADC and DAC stacks. Sysref A and Sysref B are also shown connected to the DFE.](e417ae35ab07134888be901c201d54cd_img.jpg) - -Figure 2.3.2-15 Example 8T8R JESD204 Configuration diagram. The diagram shows a central 'Clock Synthesis' block connected to 'Device Clock A' and 'Device Clock B'. 'Device Clock A' is connected to a stack of 8 ADCs and a stack of 8 DACs. 'Device Clock B' is connected to a 'DFE & Low PHY Or Low PHY' block. The ADCs are connected to the DFE via 'JESD for UL x2' lanes. The DACs are connected to the DFE via 'JESD for DL x2' lanes. The DFE is connected to 'Fronthaul'. A bracket on the left labeled 'To RFFE' groups the ADC and DAC stacks. Sysref A and Sysref B are also shown connected to the DFE. - -4 -5 - -**Figure 2.3.2-15 Example 8T8R JESD204 Configuration** - -6 JESD204C supports up to 32.45 Gbps and therefore 2 lanes will be required as shown below. In this example, - 7 2 UL and 2 DL JESD lanes connect between the two devices. - -8 -$$L = \text{Ceiling} \left( \frac{64.88064Gbps}{32.45 Gbps} \right) = 2$$ - -1 Using the equation for ‘F’ determines the octets per frame to be 16 in this example. The frame structure as - 2 defined by JESD204 is shown in Figure 2.3.2-16 As with the 4T4R example, the frame structure is little endian - 3 with lane 0 beginning with converter 0 and lane 1 beginning with converter 8. Complete details on JESD204 - 4 can be found [16]. - -5 -$$F = \frac{16 \times 1 \times 16}{8 \times 2} = 16$$ - -| 8 (L = 2, M = 16, F = 16, S = 1, NP = 16) | | | | | | | | | | | | | | | | | -|-------------------------------------------|------------|-----------|------------|-----------|-------------|------------|-------------|------------|-------------|------------|-------------|------------|-------------|------------|-------------|------------| -| Frame 0 | | | | | | | | | | | | | | | | | -| Lanes | Octet 0 | Octet 1 | Octet 2 | Octet 3 | Octet 4 | Octet 5 | Octet 6 | Octet 7 | Octet 8 | Octet 9 | Octet 10 | Octet 11 | Octet 12 | Octet 13 | Octet 14 | Octet 15 | -| 0 | M0S0[15:8] | M0S0[7:0] | M1S0[15:8] | M1S0[7:0] | M2S0[15:8] | M2S0[7:0] | M3S0[15:8] | M3S0[7:0] | M4S0[15:8] | M4S0[7:0] | M5S0[15:8] | M5S0[7:0] | M6S0[15:8] | M6S0[7:0] | M7S0[15:8] | M7S0[7:0] | -| 1 | M8S0[15:8] | M8S0[7:0] | M9S0[15:8] | M9S0[7:0] | M10S0[15:8] | M10S0[7:0] | M11S0[15:8] | M11S0[7:0] | M12S0[15:8] | M12S0[7:0] | M13S0[15:8] | M13S0[7:0] | M14S0[15:8] | M14S0[7:0] | M15S0[15:8] | M15S0[7:0] | - -7 **Figure 2.3.2-16 8T8R Example Data Mapping** - -8 **2.3.2.3.2 Optional Die to Die Interfacing** - -9 The existing specification O-RAN.WG7.OMC-HRD-Opt7-2-v03.00 has several references to SERDES links, - 10 either in text or diagrams. The SERDES link is very appropriate for deployments where RF and baseband - 11 chips are separated by 10s of cm on a PCB, as it provides low wire count with decent power consumption - 12 (pJ/bit). For multi-chip modules, however, where die are separated by 10 mm or less, die-to-die (D2D) parallel - 13 interfaces such as Advanced Interface Bus (AIB) [18], Bunch of Wires (BoW) [19] or Universal Chiplet - 14 Interconnect Express (UCIe) [20] offer a lower power, lower complexity option, at the cost of more I/O. - -![Diagram of basic die-to-die parallel architecture showing DIE #1 (Digital Baseband unit) and DIE #2 (Transceiver) connected via die bumps on a package substrate or interposer. The distance between dies is less than 10 mm. DIE #1 contains a Data Source with I/Q DATA OUT and a CLK (1.4 GHz) with DCC. DIE #2 contains a Data Sink with I/Q DATA IN and a DLL. Data lines (TX0-TX15) connect the Data Source to the Data Sink. Clock lines (CLK+, CLK-) connect the DCC to the DLL.](91b12db3c85bbf466ad27eb3665a1b06_img.jpg) - -Diagram of basic die-to-die parallel architecture showing DIE #1 (Digital Baseband unit) and DIE #2 (Transceiver) connected via die bumps on a package substrate or interposer. The distance between dies is less than 10 mm. DIE #1 contains a Data Source with I/Q DATA OUT and a CLK (1.4 GHz) with DCC. DIE #2 contains a Data Sink with I/Q DATA IN and a DLL. Data lines (TX0-TX15) connect the Data Source to the Data Sink. Clock lines (CLK+, CLK-) connect the DCC to the DLL. - -16 **Figure 2.3.27-17 Basic die-to-die parallel architecture** - -17 The simplicity of the die-to-die parallel architecture is illustrated in the figure above which depicts a 16-bit - 18 unidirectional “data unit” with single-ended drivers and receivers, plus a differential forwarded clock. The - 19 salient features of die-to-die interfaces are: - -1. Uni-directional throughput rates in the 100-1000 Gbps/mm depending on packaging technology, clock rate, channel length, and use of source/load terminations. 1 -2. Power consumption in the .5-1.0 pJ/bit range. -3. Scaleable, via the addition of more data units consisting of 16-20 I/O each, encompassing more silicon beachfront or bump rows. -4. Simple PHY architecture not requiring any complex pre-emphasis or equalization...usually only Duty Cycle Correction (DCC) and a Delay Lock Loop (DLL). -5. Reliable link such that FEC is typically not required. - -The diagram above shows an implementation of D2D in a Multi-chip module including the Digital Baseband unit and the Transceiver in one package. Referring to Figure 2.3.2-2, the Digital Processing unit in the figure corresponds to the Digital Baseband unit in the figure above. This figure shows DL I/Q data flowing to the transceiver, but there would be a corresponding path in the other direction for UL I/Q data flowing from Transceiver to the Digital Baseband unit. - -In Figure 2.3.27-17, the clock source is shown on the left of the data transmitting unit. Since DDR mode may be used for max throughput, and the clock is typically in the 1-4 GHz range, an accurate duty cycle is required. The Duty Cycle Correction (DCC) block would be employed to ensure that a duty cycle close to 50% is maintained. - -On the RX side, a Delay Lock Loop (DLL) may be used to ensure that the clock strobes data into the data register at approximately the middle of the data bits. If so, a calibration or initialization procedure would determine the clock phase shift required to center the strobe. - -The packaging technology and bump pitch used for each die greatly influences the final throughput expressed as Gbps/mm. Standard chip scale bump pitches of 100 um or greater, used with organic substrate chip scale packaging, allow for simplified D2D interconnect but will not give the maximum throughput. The use of micro-bumps and specialized interposer technology, or even EMIB, will provide for throughput approaching 1 Tbps/mm and lower power. - -With the AIB, UCIe, and BoW D2D interfaces mentioned initially, a standardized bump map for each data unit is either required, or strongly recommended. (At a minimum, there needs to be a wiring order so that packages with different bump pitches can still be used and data lines routed through the RDL without criss-crossing or excess routing skew.) The # of routing layers in the packaging interconnect determines how many data units (with their associated physical bump patterns) can be adjoined (inwards towards the die), in order to further increase throughput for the same silicon beachfront. - -Initial D2D deployments used un-terminated drivers and receivers, which was sufficient for clock rates in the low GHz range and channel lengths of a few mm. To achieve longer channel lengths and/or higher base clock rates, terminations may be employed at the source driver, the receiver, or both. - -1 Here the linear mm dimension refers to the silicon edge beachfront dedicated to the parallel I/O - -### 2.3.3 O-RU7-2 Hardware Components for SDR SoC based Design - -General block diagrams for 4T4R and 8T8R O-RU7-2 examples for FPGA based design are shown in section 2.3.2. The block diagrams for SDR SoC-based 2T2R and 4T4R designs are very similar and are shown below. - -![Figure 2-18: 2T2R General Block Diagram for SDR SoC based design](50ef8602c7c9edd2da0e2133e772c2a2_img.jpg) - -The diagram illustrates a 2T2R SDR SoC-based design. A central 'Digital Processing Unit' is connected via SerDes to external memory components: DDR4, eMMC, and NOR Flash, and via SPI to other components. It interfaces with a 'Transceiver' block through 'Analog I/Q' and 'Clean Clock' signals. The Digital Processing Unit also connects to a 'DPLL' (Digital Phase-Locked Loop), which is linked to a 'PSU' (Power Supply Unit). Control signals originating from the Digital Processing Unit include TXFB\_RX\_SW Control, PA Enable, LNA Bypass, LNA Enable, and T/R\_SW Control. These signals route to two RF chains. Each chain consists of a transmit path (TX0, TX1) with a power amplifier and power detector (PDET0, PDET1), and a receive path (RX0, RX1) with low-noise amplifiers. The paths terminate at antenna ports through filters and circuital components. - -Figure 2-18: 2T2R General Block Diagram for SDR SoC based design - -**Figure 2-18: 2T2R General Block Diagram for SDR SoC based design** - -![Figure 2-19: 4T4R General Block Diagram for SDR SoC based design](e05434e963901d7e9c0bf5a6758200ed_img.jpg) - -This diagram illustrates a 4T4R SDR SoC-based design, expanding on the 2T2R architecture. It features the same core components: a 'Digital Processing Unit' connected to DDR4, eMMC, NOR Flash, and SPI; a 'Transceiver' block; a 'DPLL'; and a 'PSU'. The control signal bus (TXFB\_RX\_SW Control, PA Enable, LNA Bypass, LNA Enable, T/R\_SW Control) now services four RF chains instead of two. There are four transmit paths (TX0, TX1, TX2, TX3) each with its own power detector (PDET0-PDET3) and four receive paths (RX0, RX1, RX2, RX3), all connecting to four separate antenna interfaces through respective filtering and switching circuitry. - -Figure 2-19: 4T4R General Block Diagram for SDR SoC based design - -Figure 2-19: 4T4R General Block Diagram for SDR SoC based design - -2.3.3.1 Digital Processing Unit - -The digital processing unit of O-RU7.2 is mainly for performing tasks related to FH interface, lower L1, RF interface, and OAM. - -*i. SDR SoC based Solution Design* - -The Software Defined Radio SOC unit of O-RU7.2 is mainly responsible for FH interface, Low PHY, RF I/Q interface, and management functions. - -*a. SDR SoC requirement:* - -The following items are required for the O-RU7.2: - -- Interface requirement: One lane of bi-directional 10 Gbps SerDes for FH Split 7.2, 4-Port ADC/DAC IQ pairs for 4T4R and 2-port ADC/DAC IQ pairs for 2T2R. -- Resource Requirement: Built-in DSP, RTOS and processors to implement 2T2R and 4T4R ORU 7.2 Low PHY features. - -*b. SDR SoC Design:* - -![SDR SoC Design block diagram showing internal components like Processor, DSP + RTOS, AFE, DPD HW Accelerator, PLL, Sync Timer, Low Speed Interface, High Speed Interface, and external connections to Power, Tranceiver, Clock Generator, SFP+, Flash, Debug, and DDR.](7913c315e0db8233cb1ac2455e4a0a81_img.jpg) - -The diagram illustrates the internal architecture of the SDR SoC. At the top, a power input block lists voltages: 0.8, 0.9, 1.1, 1.2, 1.8, and 3.3v. The central 'SDR SOC' block contains several sub-components: 'Processor', 'DSP + RTOS', 'AFE', 'DPD HW Accelerator', 'PLL', and 'Sync Timer'. External connections include: - - -- 'Tranceiver' connected via 'I/Q Interfaces' to the AFE. -- 'Clock Generator' connected via SPI to the AFE and Sync Timer, and via I2C to the High Speed Interface. It provides three clock signals: 122.88MHz, 250Mhz, and 156.25Mhz. -- 'SFP+' connected via 'SerDes' to the High Speed Interface. -- 'Flash', 'Debug', and 'DDR' connected to the Low Speed Interface. - -SDR SoC Design block diagram showing internal components like Processor, DSP + RTOS, AFE, DPD HW Accelerator, PLL, Sync Timer, Low Speed Interface, High Speed Interface, and external connections to Power, Tranceiver, Clock Generator, SFP+, Flash, Debug, and DDR. - -Figure 2-20: SDR SoC Design - -2.3.3.2 RF Processing Unit - -The RF processing unit of O-RU7.2 performs functionalities of local oscillator, down converter, up converter etc. - -1 2.3.3.2.1 Transceiver RFIC Reference Design - -High Band: 4.2 ~ 5.0 GHz - Mid Band : 3.3 ~ 4.2 GHz - Low Band : 2.5 ~ 3.0 GHz - -![Block diagram of Transceiver RFIC Reference Design showing various functional units like Tri RF Bands Unit 0, Tri RF Bands Unit1, External Sensor Control Unit, RF Processor Unit, BB <-> RF Convert, RF IQ Cal, Digital Control Unit, TRX BB Unit0, ORX BB Unit, and TRX BB Unit1.](376f80eb8a41369e87da63a0210d173e_img.jpg) - -The diagram illustrates the internal architecture of the Transceiver RFIC. A large central block represents the 'RF Processor Unit'. Within this unit, there's a 'BB <-> RF Convert' block and an 'RF IQ Cal' block. Above the RF Processor Unit are two 'Tri RF Bands' blocks, labeled 'Unit 0' and 'Unit1'. To the right of these is an 'External Sensor Control Unit'. Below the RF Processor Unit are three blocks: 'TRX BB Unit0', 'ORX BB Unit', and 'TRX BB Unit1'. A vertical 'Digital Control Unit' is positioned on the left side, spanning the height of the RF Processor Unit and the TRX/ORX BB units. - -Block diagram of Transceiver RFIC Reference Design showing various functional units like Tri RF Bands Unit 0, Tri RF Bands Unit1, External Sensor Control Unit, RF Processor Unit, BB <-> RF Convert, RF IQ Cal, Digital Control Unit, TRX BB Unit0, ORX BB Unit, and TRX BB Unit1. - -2 -3 **Figure 2-21: Transceiver RFIC Reference Design** - -4 The key features of the transceiver RFIC are as follows: - -- 5 • Tri-Band 2x2 5G NR sub-6 GHz RF transceiver -- 6 • Flexible analog baseband filter - 50 MHz - 400 MHz modulation in TX mode -- 7 • Flexible analog baseband filter - 20 MHz - 200 MHz modulation in RX mode -- 8 • Observation path for DPD support -- 9 • Analog differential I/Q interface to baseband -- 10 • Programmable RFIC control, configuration and calibration - -11 The key receiver features are as follows: - -- 12 • Direct conversion, low noise and high dynamic range receive chains -- 13 • High speed AGC interface (Rx gain control) to baseband - -14 The key transmitter feature is as follows: - -- Direct conversion with adjustable gain on the transmission chains - -It includes an auxiliary ADC that supports: - -- Calibration of internal circuits -- External voltage and temperature measurements -- External PA Power Envelope Measurements - -The RFIC includes: - -- Interfaces for configuration and bi-directional data with baseband IC - -### 2.3.3.2.2 Power Amplifier (PA) Reference Design - -The Power Amplifier boosts the RF output to the level required for the base station class. - -#### *a. Hardware Requirements* - -The PA is the final stage that amplifies the downlink RF signal. Considering the requirement of the conducted output power of 37 dBm at the antenna connector and the maximum 3 dB insertion loss between the PA and the antenna, including the directional coupler, the circulator, and the band-pass filter, the PA output power should be at least 40 dBm (same output power as in **2.3.2.2.2**). The ACLR should be less than -28.2 dBc (before applying the DPD) to ease the hardware processing requirements of the DPD algorithm and still be able to meet the 3GPP TS38.104 ACLR requirements (clause 6.6.3). To support TDD mode, the PA should be capable of swiftly turning ON and OFF. The switching time should be less than 1 usec. - -**Table 2-14: PA Requirements** - -| Parameter | Specification | Additional Information | -|---------------------|-----------------|---------------------------------------------------------------------------| -| Gain | >28.2 dB | @ 3400 MHz | -| | >28.1 dB | @ 3800 MHz | -| Drain Efficiency | >36 % | @ 3400 MHz | -| | >40 % | @ 3800 MHz | -| P3dB | >47.4 dBm | @ 3400 MHz | -| | >47.5 dBm | @ 3800 MHz | -| Linear Output Power | 40 dBm, typ. | | -| ACLR | -28.2 dBc, typ. | Adjacent channels (ADJ) with 1-carrier 20 MHz LTE (PAPR 8 dB) | -| | -42.4 dBc, typ. | Alternative adjacent channels (ALT) with 1-carrier 20 MHz LTE (PAPR 8 dB) | - -- Interface Requirements - -The interface requirements of the transmit PA are listed in **Table 2-15**. - -**Table 2-15: Interface requirements of the transmit PA** - -| Item Name | Description | -|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Power Supplies | The PA module is two-stage Doherty GaN architecture which needs the following power supplies: stage-1 and stage-2 peaking drain supplies; stage-1 and stage-2 peaking gate supplies; stage-1 and stage-2 carrier drain supplies; stage-1 and stage-2 carrier gate supplies. | -| RF Outputs | RF outputs support 50-ohm single ended to properly interface to a directional coupler, isolator, switch or antenna. | -| RF Inputs | RF inputs should support 50-ohm, single ended match to the transceiver output or preamp. | - -*b. Hardware Design* - -Input is the RF input and Output is the RF output of the PA. VDP1 and VDP2 are the stage-1 and stage-2 peaking drain supplies respectively; VGP1 and VGP2 are the stage-1 and stage-2 peaking gate supplies respectively; VDC1 and VDC2 are the stage-1 and stage-2 carrier drain supplies respectively; VGC1 and VGC2 are the stage-1 and stage-2 carrier gate supplies respectively. Ensure all the gate voltages are adjusted according to the recommended drain bias current and the drain voltage for the best RF performance. Ensure all the power supplies follow the recommended power-up and power-down sequences to avoid PA damage. Ensure that the RF input and output ports see 50 ohms terminations for best PA performance. Bulk capacitors should be used to reduce the ripples of the drain voltages and decoupling capacitors to decouple the RF energy to ground plane. Ensure the grounding is good enough. Otherwise, the PA is subject to oscillations. **Figure 2-22** shows the details. - -![PA Reference Design diagram showing two parallel power amplifier stages. Each stage consists of Stage 1 and Stage 2. The top stage has inputs VDP1, VGP1, and VDC1, and outputs VDP2, VGP2, and VDC2. The bottom stage has inputs VGC1 and VGC2, and outputs VGC2. The input signal is split into both stages, and their outputs are combined at the final Output.](fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg) - -PA Reference Design diagram showing two parallel power amplifier stages. Each stage consists of Stage 1 and Stage 2. The top stage has inputs VDP1, VGP1, and VDC1, and outputs VDP2, VGP2, and VDC2. The bottom stage has inputs VGC1 and VGC2, and outputs VGC2. The input signal is split into both stages, and their outputs are combined at the final Output. - -Figure 2-22: PA Reference Design - -2.3.3.2.3 Directional Coupler - -a. Hardware Requirements - -O-RU needs to comply with 3GPP TS38.104 ACLR requirements (clause 6.6.3). Directional Coupler is a necessary component to implement the DPD feedback path. With the directional coupler, the TX RF signal is coupled back to the RX port for DPD calculation. Its input pin is connected to the output pin of PA, and the coupled pin is connected to the RX with a 50 ohms attenuator. The isolated pin is terminated with a 50 Ω resistor. Minimum 18 dB directivity is required to reject the self-interference due to limited antenna isolation. - -Table 2-16: Directional Coupler Requirements - -| Parameter | Specification | Unit | -|-----------|---------------|------| -|-----------|---------------|------| - -| | | | -|---------------------------------------|------------|-----| -| Coupling | 20 +/-1.5 | dB | -| Maximum Operating Band Insertion Loss | 0.075 | dB | -| Minimum Operating Band Return Loss | 18 | dB | -| Minimum Directivity | 18 | dB | -| Minimum Average Input Power | 40 | W | -| Operating Temperature | -55 ~ +150 | °C | -| Maximum VSWR | 1.22:1 | N/A | - -1 -2 -3 -4 -5 - -*b. Hardware Design* - -The Input of the directional coupler is connected to the output of the PA. The Direct port is connected to port-1 of the circulator. The Coupled port is connected to the common port of the RF switch. The Isolated port is terminated by a 50 ohms resistor. Make sure all the RF ports see 50 ohms terminations for best directivity performance. - -![Diagram of a directional coupler showing four pins: Pin 1 (Input), Pin 2 (Direct), Pin 3 (Isolated), and Pin 4 (Coupled). The diagram shows a central horizontal bar with diagonal hatching, and four ports extending from it. Pin 1 and Pin 2 are on the top, Pin 4 and Pin 3 are on the bottom. The ports are labeled: Pin 1 (top left), Pin 2 (top right), Pin 4 (bottom left), and Pin 3 (bottom right).](9e26cd5584f423e1b2155fb341db579f_img.jpg) - -Diagram of a directional coupler showing four pins: Pin 1 (Input), Pin 2 (Direct), Pin 3 (Isolated), and Pin 4 (Coupled). The diagram shows a central horizontal bar with diagonal hatching, and four ports extending from it. Pin 1 and Pin 2 are on the top, Pin 4 and Pin 3 are on the bottom. The ports are labeled: Pin 1 (top left), Pin 2 (top right), Pin 4 (bottom left), and Pin 3 (bottom right). - -Figure 2-23: Directional Coupler - -6 -7 -8 -9 - -Table 2-17: Directional Coupler Pin Connectivity - -| | | | | -|-------|--------|----------|---------| -| Pin 1 | Pin 2 | Pin 3 | Pin 4 | -| Input | Direct | Isolated | Coupled | - -10 -11 -12 -13 -14 -15 - -2.3.3.2.4 Circulator - -*a. Hardware Requirements* - -The circulator is used to increase the isolation among antennas. Using the circulator, the DPD feedback path's signal-to-noise ratio can be improved by up to 18 dB, which eases the burden on the DPD algorithm. Two types: clockwise and counter-clockwise, are available depending on the - -1 -2 -3 - -trace routing. Minimum 18 dB isolation is required to reject the self-interference due to limited antenna isolation. - -**Table 2-18: Circulator Requirements** - -| Parameter | Value | Additional Information | -|--------------------------|------------|------------------------| -| Insertion Loss | <0.25dB | | -| Isolation | >20dB | | -| Return loss | <-20dB | | -| Average Power | >50Watt | | -| Peak Power | >500Watts | | -| IMD3 | <-65dBc | 2x10W, 1MHz Spacing | -| 2 nd Harmonic | <-50dBc | | -| 3 rd Harmonic | <-60dBc | | -| Operating Temperature | -40 ~ +110 | °C | - -4 -5 -6 -7 -8 -9 - -*b. Hardware Design* - -Port-1 of the circulator is connected to the output of the directional coupler. Port-2 is connected to the BPF. Port-3 is connected to the common port of the RF switch. Make sure all the RF ports see 50 ohms terminations for best isolation performance. The RF switch should be switched to the port of 50 ohms termination during TX period. - -![Circuit diagram of a circulator with three ports. Port 1 is connected to a directional coupler output and a 50-ohm termination. Port 2 is connected to a Band Pass Filter (BPF) and then to an antenna. Port 3 is connected to the common port of an RF switch, which can be switched between a 50-ohm termination and the antenna.](f796c4b6ef101faa39b887a86820c3d1_img.jpg) - -Circuit diagram of a circulator with three ports. Port 1 is connected to a directional coupler output and a 50-ohm termination. Port 2 is connected to a Band Pass Filter (BPF) and then to an antenna. Port 3 is connected to the common port of an RF switch, which can be switched between a 50-ohm termination and the antenna. - -10 -11 -12 - -**Figure 2-24: Circulator** - -1 2.3.3.2.5 Band Pass Filter - -2 a. *Hardware Requirements* - -3 The BPF placed between the circulator and the antenna rejects the spurs and the harmonics in the TX - 4 path and suppresses the unwanted blockers in the RX path. Low insertion loss is required to meet TX - 5 output power and RX sensitivity requirements. High rejection at the band-edge is required to - 6 suppress the Out-of-Band blocking signal specified in 3GPP TS 38.104 clause 7.5. - -7 The BPF placed between the LNA output and RFIC input is optional and can be added if further - 8 suppression at the band-edge is required. - -9 High peak power handling is required to withstand the high peak-to-average ratio of CP-OFDM - 10 signal. - -11 **Table 2-19: Band Pass Filter Requirements** - -| Parameter | | @ 25°C | @ -40°C ~ 105°C | Unit | | -|-------------------------------------------|---------------------------------------------------------------------------------|-----------|-----------------|------|--| -| Maximum Passband Insertion Loss | | 1.5 | 2.0 | dB | | -| Maximum Passband Ripple | | 1.0 | 1.2 | dB | | -| Minimum Passband Input/Output Return Loss | | 15 | | dB | | -| Minimum Attenuation | 1 MHz to (f UL_low - Δf OOB ) MHz | 18 | | dB | | -| | (f UL_high + Δf OOB ) MHz to (2*f UL_low ) MHz | 18 | | | | -| | (2*f UL_low ) MHz to (2*f UL_high ) MHz | 30 | | | | -| | (3*f UL_low ) MHz to (3*f UL_high ) MHz | 20 | | | | -| Average Input Power | | 20 | | W | | -| Peak Input Power | | 200 | | W | | -| Operating Temperature | | -40 ~ 105 | | °C | | - -12 Note 1: ΔfOOB is the maximum offset of the out-of-band boundary from the uplink operating band edge - -13 Note 2: ΔfOOB= 20 MHz if (fUL\_high - fUL\_low) MHz is no larger than 200 MHz; ΔfOOB= 60 MHz if (fUL\_high - - 14 fUL\_low) MHz is larger than 200 MHz - -15 b. *Hardware Design* - -16 Input and Output are the RF ports of the BPF. Make sure the RF input and output ports see 50 ohms - 17 terminations for best BPF performance. - -![Diagram of a Band Pass Filter (BPF) showing Input and Output ports with internal wave symbols.](472a73112a9b2ed65777d54d33a3ba9c_img.jpg) - -Diagram of a Band Pass Filter (BPF) showing Input and Output ports with internal wave symbols. - -19 - -Figure 2-25: Band Pass Filter - -2.3.3.2.6 Low Noise Amplifier (LNA) Reference Design - -The LNA is required at the RX path prior to the RF transceiver. It not only boosts the RX signal but also reduces the cascaded noise figure for best RX sensitivity. Since the BPF may not reject the interference over the air, the LNA must have enough OIP3 to tolerate the interference to mitigate the de-sensitization. Another benefit of higher OIP3 is higher maximum input power of the wanted signal. - -*a. Hardware Requirements* - -The requirements of the LNA are listed here. - -- Interface Requirements: The interface requirements of the transmit LNA are listed in **Table 2-20**. - -**Table 2-20: LNA Requirements** - -| Parameter | Value | Additional Information | -|--------------------|----------|------------------------| -| NF | <1dB | Low-gain mode | -| Gain | >35dB | High-gain mode | -| | >19dB | Low-gain mode | -| OP1dB | >17dBm | High-gain mode | -| | >14.5dBm | Low-gain mode | -| Input return loss | <-10dB | | -| Output return loss | <-10dB | | -| Switching Speed | <1us | | -| OIP3 1 | >32.5dBm | High-gain mode | -| | >30dBm | Low-gain mode | -| K | >1 | up to f = 12.5 GHz | - -Note 1: 2 Tone CW -40dBm with 10 MHz difference - -- Power Dissipation: Less than 600 mW when device is fully enabled in receive mode. - -*b. Hardware Design* - -Input is the RF input of the LNA and Output is the RF output of the LNA. Vcc is the power supply of the LNA and the internal bias circuits. Enable is the control pin to enable or disable the Stage-1 LNA. BP is the control pin to bypass Stage-2 LNA. Make sure the RF input and output ports see 50 ohms terminations for best LNA performance. Bulk capacitors should be used to reduce the ripples of Vcc and decoupling - -1 capacitors to decouple the RF energy to ground plane. Minimize the insertion loss from the antenna port to - 2 the RF input of the LNA as much as possible to reduce the cascaded noise figure. Ensure the grounding is - 3 good enough. Otherwise, the LNA is subject to oscillations. **Figure 2-26** shows the details. - -![Block diagram of an LNA with two stages. Stage 1 has an Input, Vcc, and Enable pin. Stage 2 has a Bypass Switch, Vcc, BP, and Output pin. The output of Stage 1 is connected to the input of Stage 2.](5e9af8986a5845504f251d3079da8078_img.jpg) - -Block diagram of an LNA with two stages. Stage 1 has an Input, Vcc, and Enable pin. Stage 2 has a Bypass Switch, Vcc, BP, and Output pin. The output of Stage 1 is connected to the input of Stage 2. - -4 -5 -6 -**Figure 2-26: LNA** - -7 **2.3.3.2.7 RF Switch Reference Design** - -8 The RF switch is used to change the RF path from a common port. The insertion loss at the through path - 9 should be as small as possible, while the insertion loss at the blocked path should be as large as possible. The - 10 first use case is to switch TX and RX path from the antenna port for TDD applications. The second use case - 11 is to switch the TX feedback and RX at the RX input of RF transceiver. In the first use case, the common - 12 port of the RF switch is connected to port-3 as shown in Figure 2-24. During TX duration, the RF switch is - 13 switched to the port of 50 ohms termination. - -14 *a. Hardware Requirements* - -15 The requirements of the RF switch are listed here. - -- 16 • Interface Requirements: - -17 The interface requirements of the switch are listed in **Table 2-21** and **Table 2-22**. - -18 **Table 2-21: Interface requirements of the RF switch for use case 1** - -| Item Name | Description | -|-----------|-----------------------------------------------------------------------------------------------------------------------------------| -| Control | Control the switch working mode | -| RF COM | The port connected to port-3 of the circulator.
RF inputs should support 50 ohm, single ended to match the circulator. | -| RF 1 | The port connected to the LNA.
RF inputs should support 50 ohm, single ended to match the LNA. | -| RF 2 | The port connected to the 50 ohms termination.
RF inputs should support 50 ohm, single ended to match the 50 ohms termination. | - -19 **Table 2-22: Interface requirements of the RF switch for use case 2** - -| Item Name | Description | -|-----------|--------------------------------------------------------------------------------------------------------------------------------------------------------| -| Control | Control the switch working mode | -| RF COM | The port connected to RX input of RF transceiver.
RF inputs should support 50 ohm, single ended to match the RF transceiver. | -| RF port 1 | The port connected to the coupling port of the directional coupler.
RF inputs should support 50 ohm, single ended to match the directional coupler. | -| RF port 2 | The port connected to the LNA output.
RF input should support 50 ohm, single ended to match the LNA output. | - -1 - -2 - -- RF Specifications - -3 - -The switch should have larger P1dB to not degrade the ACLR or damage the switch itself. The output power should be at least 40dBm considering the loss of antenna filter, and it must have low loss. Also, the isolation needs to be high to protect the LNA. Higher HD2 and HD3 are needed to reduce the out-of-band emissions. - -4 - -5 - -**Table 2-23: RF Switch Requirements** - -| Parameter | Value | Additional Information | -|-----------------------------|--------|---------------------------------------------------------| -| Loss | <0.5dB | | -| Maximum average input power | >40dBm | CP-OFDM with 10.5 dB PAPR, BW = 100 MHz, QPSK modulated | -| Input return loss | <-15dB | | -| Output return loss | <-15dB | | -| Switching Speed | <0.5us | | -| Isolation | >30dB | | - -7 - -8 - -*b. Hardware Design* - -9 - -RFcom is the common port of the RF switch which is switched to RF1 or RF2 by CTRL pin. Vcc is the power supply of the transistor and control logic. DC blocks are required at each RF port if non-zero DC exists. Decoupling capacitors are added at Vcc to decouple the RF energy to ground plane. - -10 - -11 - -**Figure 2-27** shows the details. - -12 - -13 - -14 - -15 - -![Circuit diagram of an SPDT RF Switch Reference Design. It shows a switch symbol with two input ports labeled RF1 and RF2 on the left, a common output port labeled RFcom on the right, a control input labeled CTRL at the bottom, and a supply voltage input labeled Vcc at the top.](7f7211748473542096717109ebe5a9d6_img.jpg) - -Circuit diagram of an SPDT RF Switch Reference Design. It shows a switch symbol with two input ports labeled RF1 and RF2 on the left, a common output port labeled RFcom on the right, a control input labeled CTRL at the bottom, and a supply voltage input labeled Vcc at the top. - -**Figure 2-27: SPDT RF Switch Reference Design** - -**2.3.3.2.8 Antenna Reference Design** - -The Antenna reference design is similar to the one described in 2.3.2.2.5 - -**2.3.4 Synchronization and Timing** - -The clock and synchronization are determined by the PTP and SyncE signals transported by ethernet L2 via the fronthaul in conjunction with clock recovery in the hardware. Together these provide the local time of day and frequency reference for the O-RU7-2. - -![Functional block diagram for Clock and Synchronization. A central 'Clock Software Stack' block is connected to 'Ethernet TRx' (receiving 'Ethernet Clock'), 'QSFP' (receiving 'Embedded CLK'), and 'GPS/Aux or Cascade' (receiving 'GPS/Aux Clock'). It also connects to a 'Clock Synthesizer' (receiving 'Clock, Sync & Control') which is connected to an 'XTAL' crystal. The 'Clock Software Stack' sends 'Control' signals to an 'RF TRx' and 'Clock, Sync & Control' signals to a 'Synchronizer'. The 'Synchronizer' is connected to a 'TCXO' and outputs 'DevCLK, Sysref' to the 'RF TRx'.](007fefafb4fcbdb7d388209f63a0ba5d_img.jpg) - -Functional block diagram for Clock and Synchronization. A central 'Clock Software Stack' block is connected to 'Ethernet TRx' (receiving 'Ethernet Clock'), 'QSFP' (receiving 'Embedded CLK'), and 'GPS/Aux or Cascade' (receiving 'GPS/Aux Clock'). It also connects to a 'Clock Synthesizer' (receiving 'Clock, Sync & Control') which is connected to an 'XTAL' crystal. The 'Clock Software Stack' sends 'Control' signals to an 'RF TRx' and 'Clock, Sync & Control' signals to a 'Synchronizer'. The 'Synchronizer' is connected to a 'TCXO' and outputs 'DevCLK, Sysref' to the 'RF TRx'. - -**Figure 2.3.4-1 Clock and Synchronization Functional Block Diagram** - -1 2.3.4.1 Hardware Specifications - -2 2.3.4.1.1 Interface - -3 Table 2.3.4-1 Synchronization and Timing Interface Specifications - -| Item Name | Description | -|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------| -| Clock Inputs | Depending on the configuration, the following clock inputs may exist: QFSP, Ethernet, GPS, Cascaded unit clocks, Synchronized Clock. | -| Clock Outputs | Depending on functional requirements, the following clocks may be delivered: QFSP, Ethernet, DDR, CPU, RF Transceiver clock, Synchronizer reference. | -| Clock Control | SPI or I2C to control the clock synthesizer and synchronizer. | -| Clock Sync | Logic signal to phase align and time align the synchronizer with master. | -| Crystal Reference | One or more reference oscillators to provide required phase noise and short/long term stability. | - -4 -5 2.3.4.1.2 Performance Specifications - -6 See device specifications in Table 2.3.4-3. - -7 2.3.4.1.3 Synchronizer - -8 The purpose of the Synchronizer is to function as part of the local clock recovery in conjunction with an -9 IEEE1588v2 software stack to provide local time of day and to generate a local synchronous reference signals -10 to be used for synthesis of necessary clocks to other functions within the O-RU7.2. - -11 2.3.4.1.3.1 Hardware Specifications - -12 2.3.4.1.3.1.1 Interface - -13 Table 2.3.4-2 Synchronizer Interface Specifications - -| Item Name | Description | -|---------------------------------------------|---------------------------------------------------------------------------| -| REFA, REFAA | differential or single ended reference pulse inputs. | -| REFB, REFB | differential or single ended reference pulse inputs. | -| Status and Control | control core operation and report on state of the PLL. | -| XOA, XOB | complimentary reference inputs or reference crystal connections | -| Output0 and Output0N & Output1 and Output1N | reference outputs to feed further synthesis, transceiver or logic blocks. | - -14 - -1 2.3.4.1.3.1.2 Performance Specifications - -2 Table 2.3.4-3 Synchronizer Performance Specifications - -| Item Name | Description | Notes | -|----------------|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 10 Hz Offset | –77 dBc/Hz | Device configuration: f OSC = 52 MHz crystal, f REF = 30.72 MHz, f VCO = 2457.6 MHz, f OUT = 245.76 MHz, DPLL BW = 50 Hz, internal zero delay operation | -| 100 Hz Offset | –93 dBc/Hz | | -| 1 kHz Offset | –114 dBc/Hz | | -| 10 kHz Offset | –125 dBc/Hz | | -| 100 kHz Offset | –130 dBc/Hz | | -| 1 MHz Offset | –140 dBc/Hz | | -| 10 MHz Offset | –156 dBc/Hz | | - -3 -4 2.3.4.1.3.2 Hardware Design - -![Synchronizer Block Diagram showing internal architecture including PLL0, PLL1, reference inputs, and distribution outputs.](64544fbada794f3cdf4f78f5d83613e4_img.jpg) - -The block diagram illustrates the internal architecture of a synchronizer. On the left, 'REFERENCE INPUTS' (REFA, REFAA, REFB, REFBB) are processed through a 'REFERENCE MONITORS' block and a 'REFERENCE SWITCHING CONTROL' block. These are followed by 'AUXILIARY NCOs' and 'AUXILIARY TDCs'. A 'DIGITAL CROSS POINT MUX' connects these to 'STATUS AND CONTROL PINS'. Below this is an 'M0 TO M6' block connected to an 'EEPROM (OPTIONAL)'. The central part contains two PLL blocks: 'PLL0' and 'PLL1'. Each contains a 'DPLL', 'NCO', 'PLL', 'VCO', and a '÷2' divider. 'INTERNAL ZERO DELAY' lines connect the DPLLs to the distribution outputs. 'DISTRIBUTION OUTPUTS' for PLL0 include OUT0AP, OUT0AN, OUT0BP, OUT0BN, OUT0CP, and OUT0CN. 'DISTRIBUTION OUTPUTS' for PLL1 include OUT1AP, OUT1AN, OUT1BP, and OUT1BN. A 'SYSTEM CLOCK' block includes 'SYSTEM CLOCK PLL', 'SYSTEM CLOCK COMPENSATION', and a 'TEMPERATURE SENSOR'. A 'SERIAL PORT (SPI#C) AND EEPROM CONTROLLER' is connected to the 'SERIAL PORT' and 'M0 TO M6' block. 'XOA' and 'XOB' pins are shown on the right. - -Synchronizer Block Diagram showing internal architecture including PLL0, PLL1, reference inputs, and distribution outputs. - -Figure 2.3.4-2 Synchronizer Block Diagram - -5 -6 -7 -8 2.3.4.1.4 Reference Synthesizer - -9 The purpose of the clock synthesizer is to generate low jitter, high stability reference clocks as needed -10 throughout the design. - -1       2.3.4.1.4.1    Hardware Specifications - -2       2.3.4.1.4.1.1    Interface - -3                            **Table 2.3.4-4   Synthesizer Interface Specifications** - -| Item Name | Description | -|--------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Reference Clock(s) Input | The clock inputs device should receive a stable reference from a crystal, network reference or other suitable source. More than one input is allowed that may be selected between as required by the system. | -| Control | Control of the transceiver is by way of 3 or 4 wire SPI or I2C functioning as a slave. Support for 1.8V control is required and tolerance of 3.3V is preferred. Typically, the clock devices will be part of an IEEE1588v2 protocol loop controlled by way of this control interface, or other GPIO lines as required by the hardware implementation. | -| Clock Outputs | One or more clock outputs are required to drive the digital device and transceiver clock inputs. Each output should be independently programmable in frequency to suit the application. The outputs should nominally be differential to preserve clocking edge and to maximize tolerance of high common mode signals. | - -4 -5       2.3.4.1.4.1.2    Performance Specifications - -6                            **Table 2.3.4-5   TCXO Clock Performance Specifications** - -| Item Name | Description | -|----------------|--------------| -| Frequency | 25 MHz | -| Stability | +/- 0.28 ppm | -| 10 Hz Offset | -90 dBc/Hz | -| 100 Hz Offset | -120 dBc/Hz | -| 1 kHz Offset | -140 dBc/Hz | -| 10 kHz Offset | -151 dBc/Hz | -| 100 kHz Offset | -152 dBc/Hz | -| 1 MHz Offset | -154 dBc/Hz | - -7 - -1 2.3.4.1.4.2 Hardware Design - -![Synthesizer Block Diagram showing internal components like PLL1, PLL2, and various output stages (OUT0 to OUT13).](ffb6acd27b8e3a54392840948a75869f_img.jpg) - -The diagram illustrates the internal architecture of a synthesizer. It is divided into several functional blocks. On the left, there's a PLL1 block containing a Phase Detector, Charge Pump, Loop Filter, and multiple 10-bit Dividers. This is connected to REF\_A, REF\_B, and REF\_SEL inputs. Below it, a SYSREF input is processed through a series of dividers and multiplexers. A central PLL2 block contains a Phase Detector, Loop Filter, and a 10-bit Divider. To the right, there are multiple output stages, each consisting of a 10-bit Counter, a 10-bit Divisor, and a Driver, labeled OUT0, OUT1, OUT2 to OUT11, OUT12, and OUT13. Various control signals like SDO, SDA, SCL, RESET, and Status\_0\_1 are shown on the left side, along with an I2C/SPI interface block. Power supply pins like VCC, VCCD, VCCIO, VCCRF, and VCCRF2 are indicated at the top. - -Synthesizer Block Diagram showing internal components like PLL1, PLL2, and various output stages (OUT0 to OUT13). - -Figure 2.3.4-3 Synthesizer Block Diagram - -5 2.3.4.2 Hardware Design - -6 2.3.5 External Interface Ports - -7 2.3.5.1 Hardware Specifications - -8 The following table shows the external ports or slots provided by the O-RU7-2. External connections can be - 9 aggregated into a composite connector to minimize the points of environmental ingress as required for a - 10 specific deployment. - -11 Table 2.3.5-1 External Port List - -| Port Name | Feature Description | -|-----------------------------|----------------------------------------------------------------------------------------------------------------------------| -| Fronthaul interface | One or more 25Gbps optical interfaces including a primary link and optionally a second link for redundancy or daisy chain. | -| Debug interface | RJ45 for maintenance access. | -| Power interface | Two pin male panel mount connectors (x1) | -| RF Interface | 4.3-10+ IP67 connector (x4) [9] [11] / M-LOC cluster/multiport RF connector [12] | -| Calibration Port (Optional) | N Female or 4.3-10+ Female | -| AISG[10] RET Port | RS-485, IEC 60130-9, or RF connectors | - -12 - -### 2.3.5.2 Hardware Design - -#### 2.3.5.2.1 Fronthaul Interface - -The fronthaul interface to the OMC is provided by an optical fiber or fibers connected to the chassis by way of a SFP or SFP+ cage connector. In addition, an IP67 connector seal should be selected to provide appropriate environmental protection. - -![SFP+ case and connector](92979cab89ec8747992c43d33b6c51da_img.jpg) - -An isometric line drawing of an SFP+ cage connector. It is a rectangular metal housing designed to be mounted on a PCB. The top surface has several circular ventilation holes. The front opening is designed to receive an SFP+ module, and the bottom features multiple pins for electrical connection to a circuit board. - -SFP+ case and connector - -**Figure 2.3.5-1 SFP+ case and connector** - -#### 2.3.5.2.2 Debug Interface - -The local maintenance port or debug port is by way of a standard ethernet connector. The RJ45 Ethernet connector are standardized components and available from multiple vendors. The following figure describes the general form factor of one such RJ45 connector. - -![RJ45 Interface](bafee83a7eadee0dab23f856ae7228c1_img.jpg) - -An isometric line drawing of a shielded RJ45 Ethernet connector. It shows a modular jack with a metal outer shell. The front opening has the standard 8-pin configuration for an Ethernet plug. The bottom and sides have metal tabs and pins for mounting and grounding on a PCB. - -RJ45 Interface - -**Figure 2.3.5-2 RJ45 Interface** - -1 2.3.5.2.3 Power Interface - -2 The standard power interface is defined by a 2-pin panel mount connector as shown in the following figure. - -![Figure 2.3.5-3: Power Interface. A 3D rendering of a square panel mount connector with a circular opening, connected by a cable to a circular plug connector.](5f5caa1debf59230cc4c1cda0e285ed9_img.jpg) - -Figure 2.3.5-3: Power Interface. A 3D rendering of a square panel mount connector with a circular opening, connected by a cable to a circular plug connector. - -3 - -4 - -Figure 2.3.5-3 Power Interface - -5 - -2.3.5.2.4 RF Interface - -6 - -The standard RF interface are the 4.3-10+ Low PIM RF connector and the M-LOC cluster/multiport connector - -7 - -as shown in the following figure. - -![Figure 2.3.5-4 (a): 4.3-10+ RF Connector. A technical drawing showing the front face of the connector with concentric circles and four mounting holes. Dimensions are indicated: 4.13 mm, 10 mm, 15.16 mm, and 20 mm.](9658365eb8d9ea36ca5ca9a830508819_img.jpg) - -Figure 2.3.5-4 (a): 4.3-10+ RF Connector. A technical drawing showing the front face of the connector with concentric circles and four mounting holes. Dimensions are indicated: 4.13 mm, 10 mm, 15.16 mm, and 20 mm. - -(a) - -![Figure 2.3.5-4 (b): M-LOC cluster/multiport connector. A 3D rendering of the connector above a technical drawing. The drawing shows a square panel with six circular ports arranged in a cluster. Dimensions include 36.00, 30.00, 19.00, 30.00, 19.00, 40.00, and 13.44.](f033879165b16c0b7c82e459042ec3f0_img.jpg) - -Figure 2.3.5-4 (b): M-LOC cluster/multiport connector. A 3D rendering of the connector above a technical drawing. The drawing shows a square panel with six circular ports arranged in a cluster. Dimensions include 36.00, 30.00, 19.00, 30.00, 19.00, 40.00, and 13.44. - -(b) - -8 - -9 - -Figure 2.3.5-4 (a) 4.3-10+ RF Connector [9] [11] (b) M-LOC cluster/multiport connector [12] - -1 2.3.6 Mechanical - -2 One such mechanical structure is shown in the following figure. The shell should provide appropriate -3 environmental protection, RF shielding and passive thermal dissipation. Internally, thermal pads are used to -4 contact local heat sources and transfer that heat to the frame which in turn dissipates the heat through bulk -5 metal and fins used to increase the effective surface area. Other enclosures are possible. - -![Side view of a mechanical enclosure with dimensions 410 mm height and 330 mm width.](e03e8c02d5fc29e318efe40bfe3762df_img.jpg) - -A side view of a rectangular mechanical enclosure. The enclosure has a dark grey, vertically-ribbed front panel. The top edge features two circular mounting rings. The bottom edge has four small, cylindrical feet. A vertical dimension line on the left indicates a height of 410 mm, and a horizontal dimension line at the bottom indicates a width of 330 mm. A small handle is visible on the left side of the enclosure. - -Side view of a mechanical enclosure with dimensions 410 mm height and 330 mm width. - -6 -7 - -Figure 2.3.6-1 Mechanical Enclosure Side View - -![Mechanical Enclosure End View showing a 170 mm height dimension.](b2da20e7e7ccb0f7656992aa3b2d3062_img.jpg) - -The image shows the end view of a mechanical enclosure. It is a rectangular box with a series of vertical fins on the top and bottom surfaces for heat dissipation. On the front face, there are two circular components, likely antennas or sensors, mounted symmetrically. A vertical dimension line on the right side of the enclosure indicates a height of 170 mm. - -Mechanical Enclosure End View showing a 170 mm height dimension. - -Figure 2.3.6-2 Mechanical Enclosure End View - -## 2.3.7 Power Unit - -For the Outdoor Microcell, the power solution of the O-RU7.2 is provided externally from a telco -48V supply. Internally, the telco supply is converted and distributed to devices using appropriate DC-DC and LDO converters. Optionally the unit can be powered by AC line power which is not shown here. - -### 2.3.7.1 Hardware Specifications - -The power unit is responsible for isolating and converting the telco supply to appropriate voltages for distribution to individual supply domains in the O-RU7.2. The typical dissipation is outlined below. The RF front end is broken out separately since different deployment scenarios will require different frequencies and power levels resulting in significantly different total dissipation. Total Power is the sum of the two sections below. - -Table 2.3.7-1 Transceiver Module Specifications - -| Module | 4T4R (Watts) | | Notes | -|-----------------------------------------------------------|--------------|--|-------------------------------| -| FPGA | 16 | | | -| Transceiver | 7 | | | -| Synchronization & Clocking | 3 | | | -| DDR | 1 | | | -| Others | 3 | | | -| SFP+ Module | 1.5 | | 1 module installed | -| total device consumption | 31.5 | | | -| O-RU 7.2 Low PHY Transceiver power consumption | 36.8 | | On board power efficiency 85% | - -Table 2.3.7-2 RF Front End Module Specifications - -| Module | 4T4R (Watts) | | Notes | -|----------------------------------------------------|--------------|--|------------------------------------------| -| PA | 125 | | 75% Tx, Max RF. 10W rms output @ 100 MHz | -| PA Drive Amp | 4 | | | -| LNA | 0.5 | | 25% Rx | -| Others | 2.5 | | Bias generators and controller | -| total device consumption | 132 | | | -| O-RU 7-2 RF Front End power consumption | 155.3 | | On board power efficiency 85% | - -### 2.3.7.2 Hardware Design - -The block diagram of the power unit is shown in the figure below, which depict the power distribution to various functional modules such as RF PAM board and FPGA/RF SoC board (Digital) along with approximate power requirements. - -![Figure 2.3.7-1 Power Reference Design block diagram. A Telco supply (-48 V) enters an Over Voltage Protection Module, Over Current Protection Module, Reverse polarity module, and EMI Filter. This module connects to two Isolated Modules, #1 and #2. Isolated Module #1 outputs 12 V/5 V to Local Supply Generators (DC-DC & LDO)/ Buck Converter for FPGA/Digital Board. Isolated Module #2 outputs 50 V/28 V to Local Supply Generators (DC-DC & LDO)/ Buck Converter for PAM Tile/Board #1 and Local Supply Generators (DC-DC & LDO)/ Buck Converter for PAM Tile/Board #n. A BMC (Battery Management Controller) is connected to Isolated Module #2. The output of the Local Supply Generators for FPGA/Digital Board is ...V to ...V @ ...W. The output of the Local Supply Generators for PAM Tile/Board #1 is ...V to ...V @ ...W. The output of the Local Supply Generators for PAM Tile/Board #n is ...V to ...V @ ...W.](4537891530c9f6f139a2e1ebf544edc4_img.jpg) - -Figure 2.3.7-1 Power Reference Design block diagram. A Telco supply (-48 V) enters an Over Voltage Protection Module, Over Current Protection Module, Reverse polarity module, and EMI Filter. This module connects to two Isolated Modules, #1 and #2. Isolated Module #1 outputs 12 V/5 V to Local Supply Generators (DC-DC & LDO)/ Buck Converter for FPGA/Digital Board. Isolated Module #2 outputs 50 V/28 V to Local Supply Generators (DC-DC & LDO)/ Buck Converter for PAM Tile/Board #1 and Local Supply Generators (DC-DC & LDO)/ Buck Converter for PAM Tile/Board #n. A BMC (Battery Management Controller) is connected to Isolated Module #2. The output of the Local Supply Generators for FPGA/Digital Board is ...V to ...V @ ...W. The output of the Local Supply Generators for PAM Tile/Board #1 is ...V to ...V @ ...W. The output of the Local Supply Generators for PAM Tile/Board #n is ...V to ...V @ ...W. - -Figure 2.3.7-1 Power Reference Design - -### 2.3.8 Thermal - -Heat dissipation in O-RU7-2 is widely done through passive cooling via three modes: conduction, convection, and radiation. These mechanisms are accomplished with help of heat sink, heat pipes and vapor chamber etc. - -The transfer of heat though conduction can usually be described by Fourier's law, which is stated: - -$$q = (k/s)A \cdot dT$$ - -k is the thermal conductivity of the material, and has units of W/m·K, s = material thickness, A = heat transfer area, dT = temperature difference between inside and outside wall. - -Table 2.3.8-1 Thermal Conductivity of common Metals [13] - -| Type of material | Thermal Conductivity (W/m.K) | -|------------------|------------------------------| -|------------------|------------------------------| - -| | | -|------------------------|---------| -| Diamond | 2300 | -| Pure Al | 237 | -| Hard Aluminium 4.5% Cu | 177 | -| Au | 315-317 | -| Ag 99.9% | 411-429 | -| Iron | 80 | -| Tin | 67 | - -1 The heat sinks transfer heat to the space by thermal convection and radiation. For thermal convection, it can - 2 be calculated by the Newton's Equation: - -$$3 \quad Q_d = \alpha_c A \Delta t = \alpha_c A (t_\omega - t_f)$$ - -4 where, $Q_d$ is the convention heat (W), $t_\omega$ is the surface temperature of object (K), $t_f$ is the temperature of airflow - 5 (K), $A$ is the surface area of the object involved in heat transfer ( $m^2$ ), $\Delta t$ is the temperature difference between - 6 the surface temperature of object and airflow (K), $\alpha_c$ is convective heat transfer coefficient ( $W/m^2.K$ ). - -7 **Table 2.3.8-2 Convective heat transfer coefficient [14]** - -| Flow Type | Heat transfer coefficients ( $W/m^2.K$ ) | -|---------------------------------------------------------------------|------------------------------------------| -| Forced convection; low speed flow of air over a surface | 10 | -| Forced convection; moderate speed flow of air over a surface | 100 | -| Forced convection; moderate speed cross flow of air over a cylinder | 200 | -| Forced convection; moderate flow of water in a pipe | 3000 | - -8 - 9 For thermal radiation, it can be calculated by the following Equation: - -$$10 \quad Q_r = \varepsilon \delta A (t_\omega^4 - t_f^4)$$ - -11 where, $Q_r$ is the radiation heat (W), $\varepsilon$ is the thermal emissivity, $\delta$ is the Stefan–Boltzmann constant, its value - 12 is $5.67032 \times 10^{-8} \text{ W/ (m}^{-2} \cdot \text{K}^{-4}\text{)}$ . From these Equations, we can see that the increase of surface area $A$ and - 13 thermal emissivity $\varepsilon$ will improve the heat dissipation. - -14 Different materials can have widely different emissivity values within the range of 0 to 1.00. - -| Material | Emissivity Value ( $\varepsilon$ ) | -|---------------------------------|------------------------------------| -| Aluminium: anodized | 0.77 | -| Aluminium: polished | 0.05 | -| Brass: highly polished | 0.03 | -| Brass: oxidized | 0.61 | -| Carbon: candle soot | 0.95 | -| Carbon: graphite, filed surface | 0.98 | -| Copper: polished | 0.05 | -| Copper: oxidized | 0.65 | - -16 - -1 2.3.9 Environmental and Regulations - -2 The O-RU7-2 hardware system is RoHS Compliant. Unit is passively cooled. - -3 **Table 2.3.9-1 Environmental Features** - -| Item Name | Description | Notes | -|-----------------------------|----------------|--------------------| -| Operating Temperature | -40°C to +55°C | Cold and hot start | -| Operating Relative Humidity | 5% to 95% | | -| Atmospheric Pressure | 70 to 106Kpa | | - -4 - -## 1 2.4 Integrated O-DU & O-RU (gNB-DU) Reference Design - -### 2 2.4.1 O-DU Portion of Integrated Reference Design - -#### 3 2.4.1.1 O-DU High-Level Functional Block Diagram - -#### 4 2.4.1.2 O-DU Hardware Components - -##### 5 2.4.1.2.1 Digital Processing Unit - -##### 6 2.4.1.2.2 Hardware Accelerator (if required by design) - -###### 7 2.4.1.2.2.1 Accelerator Design 1 - -###### 8 2.4.1.2.2.2 Accelerator Design 2 - -##### 9 2.4.1.3 Synchronization and Timing - -### 10 2.4.2 O-RU Portion of Integrated Reference Design - -#### 11 2.4.2.1 O-RU High-Level Functional Block Diagram - -#### 12 2.4.2.2 O-RU Hardware Components - -##### 13 2.4.2.2.1 Digital Processing Unit - -##### 14 2.4.2.2.2 RF Processing Unit - -###### 15 2.4.2.2.2.1 Transceiver Reference Design - -###### 16 2.4.2.2.2.2 Power Amplifier (PA) Reference Design - -###### 17 2.4.2.2.2.3 Low Noise Amplifier (LNA) Reference Design - -###### 18 2.4.2.2.2.4 RF Switch Reference Design - -###### 19 2.4.2.2.2.5 Antenna / Phased Array Reference Design - -##### 20 2.4.2.2.3 Synchronization and Timing - -### 21 2.4.3 External Interface Ports - -### 22 2.4.4 O-DU/O-RU Firmware (if required by design) - -### 23 2.4.5 Mechanical - -### 24 2.4.6 Power Unit - -## 1 2.4.7 Thermal - -## 2 2.4.8 Environmental and Regulations - -## 3 2.5 Integrated O-CU & O-DU Reference Design - -### 4 2.5.1 O-CU Portion of Integrated Reference Design - -#### 5 2.5.1.1 Integrated O-CU High-Level Functional Block Diagram - -#### 6 2.5.1.2 O-CU Hardware Components - -##### 7 2.5.1.2.1 Digital Processing Unit - -##### 8 2.5.1.2.2 Hardware Accelerator (if required by design) - -###### 9 2.5.1.2.2.1 Accelerator Design 1 - -###### 10 2.5.1.2.2.2 Accelerator Design 2 - -##### 11 2.5.1.3 Synchronization and Timing - -##### 12 2.5.1.4 O-CU Firmware (if required by design) - -### 13 2.5.2 O-DU Portion of Hardware Reference Design - -#### 14 2.5.2.1 O-DU High-Level Functional Block Diagram - -#### 15 2.5.2.2 O-DU Hardware Components - -##### 16 2.5.2.2.1 Digital Processing Unit - -##### 17 2.5.2.2.2 Hardware Accelerator (if required by design) - -###### 18 2.5.2.2.2.1 Accelerator Design 1 - -###### 19 2.5.2.2.2.2 Accelerator Design 2 - -##### 20 2.5.2.3 Synchronization and Timing - -### 21 2.5.3 External Interface Ports - -### 22 2.5.4 O-DU Firmware - -### 23 2.5.5 Mechanical - -1 2.5.6 Power Unit - -2 2.5.7 Thermal - -3 2.5.8 Environmental and Regulations - -## 4 2.6 FHGW Hardware Reference Design - -5 2.6.1 FHGW High-Level Functional Block Diagram - -6 2.6.2 FHGW Hardware Components - -7 2.6.2.1 Digital Processing Unit - -8 2.6.3 Synchronization and Timing - -9 2.6.4 External Interface Ports - -10 2.6.5 Mechanical - -11 2.6.6 Power - -12 2.6.7 Thermal - -13 2.6.8 Environmental - ---- - -## 14 Annex 1: Parts Reference List - -### 15 Annex 1.1 O-CU Reference Parts List - -16 The tables below represent potential options for component selection for O-CU7-2. - -17 The HW reference design of O-CU is identical to the O-DU7-2 except for the need of HW accelerator as -18 outlined in section 2.2. - -19 - -1 - -## Annex 1.2 O-DU7-2 Reference Parts List - -2 - -The tables below represent potential options for component selection for O-DU7-2. - -3 - -4 - -### Intel Based O-DU7-2 - -| No. | Item Name | Description | -|-----|--------------------------------------|---------------------------------------------| -| 1 | Intel® Xeon® Processor D-2183IT | Intel® Xeon® Skylake D D-2100 SoC processor | -| 2 | Intel® I350 | Intel® 1GbE x4 Ethernet controller | -| 3 | Intel® X557-AT2 | Intel® 10GbE x2 Ethernet controller | -| 4 | Intel® I210 | Intel® 1GbE Ethernet controller | -| 5 | ASPEED® AST-2500 | ASPEED® BMC controller | -| 6 | UnilC® SCQ08GU03H1F1C-26V | UnilC® DDR4 8GB | -| 7 | Powerleader® MTFDDAK480TDC-1AT1ZABYY | Powerleader® SSD 480GB | -| 8 | Accelink® RTX228-551 | Accelink® 10Gbps Optical module | - -5 - -6 - -## Annex 1.3 O-RU7-2 Reference Parts List - -7 - -The tables below represent potential options for component selection for O-RU7-2. - -1 - -**ADI Based O-RU7-2** - -| No. | Item Name | Description | -|-----|----------------------|------------------------------------------------------------------------| -| 1 | ADP196ACBZ-R7 | 5V, 3A Logic Controlled High-Side Power Switch | -| 2 | LTC7150SEY#PBF | 20V, 20A Synchronous Ste-Down Regulator | -| 3 | ADRV9029 | Integrated, Quad RF Transceiver with Observation Path and DPD/CFR | -| 4 | ADP223ACPZ-R7 | Dual, 300 mA Adjustable Output, Low Noise, High PSRR Voltage Regulator | -| 5 | LTC4217IDHC#PBF | 2A Integrated Hot Swap Controller | -| 6 | ADCLK846BCPZ-REEL7 | 1.8V, 6 LVDS/12 CMOS Output Low Power Clock Fanout Buffer | -| 7 | AD9545BCPZ | IEEE 1588 V2 and 1 pps Synchronizer and Adaptive Clock Translator | -| 8 | ADRF5545A | Dual-Channel 2.4 to 4.2 GHz Receiver Front End | -| 9 | LTC3315AIV#TRMPBF | Dual 5V, 2A Synchronous Step-Down DC/DCs | -| 10 | LTC3634EUFD#PBF | 15V Dual 3A Monolithic Step-Down Regulator for DDR Power | -| 11 | LTC2928IUHF#BPF | Multichannel Power Supply Sequencer and Supervisor | -| 12 | ADP5054ACPZ-R7 | Quad Buck Regulator Integrated Power Solution | -| 13 | AD9576BPZ | Dual PLL, Asynchronous Clock Generator | -| 14 | LT1389ACS8-1.25#PBF | Nanopower Precision Shunt Voltage Reference | -| 15 | Intel® Arria® 10 SoC | Intel® Arria® 10 SoC 1AS048F35 | -| 16 | MAX1619MEE | Temp Sensor with Dual-Alarm Outputs and PMBus | - -2 - -3 - -## Annex 1.4 SDR SoC based O-RU7-2 Reference Parts List - -4 - -The tables below represent potential options for component selection for O-RU7-2. - -5 - -**Metanoia Based O-RU7-2** - -| No. | Item Name | Description | -|-----|---------------------------|------------------------------------------------------------------------------------| -| 1 | MT2824GF-A1 | MT2824 5G System on Chip | -| 2 | MT3812GN-A1 | 5G Transceiver | -| 3 | MT53E2G32D4DE-046
WT:C | LPDDR4X/LPDDR4 SDRAM | -| 4 | MX52LM04A11XSI | 2G/4G/8G-byte e•MMC™ Memory | -| 5 | MX25U25643GM2I00 | 1.8V 256M-BIT [x 1/x 2/x 4] CMOS MXSMIO®
(SERIAL MULTI I/O) FLASH MEMORY | -| 6 | SI5518D-B16625-GM | NetSync™ Low-Phase-Noise Jitter-Attenuating Clock for
5G/ eCPRI/SyncE/IEEE 1588 | -| 7 | OG19470001 | Oven-Controlled Crystal Oscillator (OCXO) 19.44 MHz | - -| | | | -|----|-----------------------|-------------------------------------------------------------------------------------------| -| 8 | 7M-20MAHE-T | Crystal 20 MHz | -| 9 | V4180 | Ultra Low Noise and Jitter VCXO 122.88 MHz | -| 10 | 735912048 | Surface Mount Single Junction Circulator 3300-3800 MHz, Clockwise, 10.0mm | -| 11 | 735912049 | Surface Mount Single Junction Circulator 3300-3800 MHz, Counterclockwise, 10.0mm Diameter | -| 12 | A5M36TG140-TC | 3400-3800 MHz, 31 dB, 10 W Avg. AIRFAST POWER AMPLIFIER MODULE | -| 13 | BTS6403UJ | Wideband high gain high linearity pre-driver amplifier 2.3 GHz - 4.2 GHz | -| 14 | BTS7202UJ | 3.3 GHz – 4.2 GHz RX Front-End Module | -| 15 | SE8R3550B500_25.7_037 | Dielectric Filter 3300-3800 MHz | -| 16 | LMH2120UM/NOPB | LMH2120 6 GHz Linear RMS Power Detector with 40 dB Dynamic Range | -| 17 | LMP92066PWPR | LMP92066 Dual Temperature-Controlled DAC with Integrated EEPROM and Output ON/OFF Control | -| 18 | X4C40K1-30S | Directional Coupler 30dB | -| 19 | C8A50Z4B | Surface Mount Termination 8 Watts, 50Ω | -| 20 | BGS12P2L6E6327XTSA1 | SPDT General Purposes Switch for High Power Applications | -| 21 | 3550LP14A0300001T | 3.5 GHz EIA 0603 Low Pass Filter | -| 22 | HHM2952A1 | Multilayer Directional Coupler For 3400-5950MHz | \ No newline at end of file diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/007fefafb4fcbdb7d388209f63a0ba5d_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/007fefafb4fcbdb7d388209f63a0ba5d_img.jpg deleted file mode 100644 index d4725f0013277442e841f34389ee08feb429f366..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/007fefafb4fcbdb7d388209f63a0ba5d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c93cdbfc918109cdea9b1e8daa62051f852b00849b029f1c1bb191d0d71fabe9 -size 49470 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/01e00200a536673d6cd0e6d8705047a0_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/01e00200a536673d6cd0e6d8705047a0_img.jpg deleted file mode 100644 index 96d2b11830755eea57d92962df4e5bff25b8a604..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/01e00200a536673d6cd0e6d8705047a0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bd91984b6b64128f2bf8cfa595ed26350d3eac2efc909d4463aef4bf8ded1130 -size 15469 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/0997dbaa9dfecedd60029d70b53327b8_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/0997dbaa9dfecedd60029d70b53327b8_img.jpg deleted file mode 100644 index 14e588223ce33ebe9af1ffc83cb906ea35fc817c..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/0997dbaa9dfecedd60029d70b53327b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:272bc8a773377ec9d810d616ac514cdcc15c9ebc982c142a89bc5da6372757e4 -size 53277 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/11358a9fa9cfdf9faa0e5645ce4336f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/132cff7e872feb31f629703959beddd7_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/132cff7e872feb31f629703959beddd7_img.jpg deleted file mode 100644 index 2d346be28e08ddc91cc27ef1705002efff7a9e52..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/132cff7e872feb31f629703959beddd7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:af182c22e73f86d2748b55c0c2086ac81c529a149315860a05a12c4f45f7f411 -size 44380 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/145d00f59802048185303f15937ea65c_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/145d00f59802048185303f15937ea65c_img.jpg deleted file mode 100644 index fffe17f95f1bf50031c0fad1c5385b2d52874614..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/145d00f59802048185303f15937ea65c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fa047d03e73c2ad132cd478d39eae08d1c0b46d5972196f6c2332949d757ec15 -size 92549 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/14af8d47efd24c21fddf71b2415b6397_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/14af8d47efd24c21fddf71b2415b6397_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/14af8d47efd24c21fddf71b2415b6397_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/1baaba7a6e54e77197475726c871067d_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/1baaba7a6e54e77197475726c871067d_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/1baaba7a6e54e77197475726c871067d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 9d55649b49cd8ee4bd4236d1939bb51c85a5ea2a..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5dd8375d88bcff1ef4cdc77c712482c64e9df5833d7cec3b0f0b1d7c6ad98b64 -size 4603 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/2b357e4034ff41a2e0c3ca8c25c00c9d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/2b3a967f6ce4f23649be995a353e39f8_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/2b3a967f6ce4f23649be995a353e39f8_img.jpg deleted file mode 100644 index 95a6b9cd2db44f52f75c86a85ed49075edc71628..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/2b3a967f6ce4f23649be995a353e39f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:997c3742995bd3200106c7e6cc12ad50f64978400988b663bdd5465bdb439c75 -size 75108 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg deleted file mode 100644 index f7db04a9e705c2d854f314eed7cc456825784ae8..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/318886a86a1dcc59e1fc83db6f157c60_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e0c43b5aa5ade79dbe0e9bcd08b2e78281af679b1c9c82ef6c459808f31e7cfa -size 93089 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/329c96049bb432e9c2cbda4e224a0c9c_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/329c96049bb432e9c2cbda4e224a0c9c_img.jpg deleted file mode 100644 index c00370e4ddad62dc75962276f75109406e3a8b51..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/329c96049bb432e9c2cbda4e224a0c9c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a74e7e51ecc27cfb10ef7029b8df8cab37a2d3290055f773b5f1b6c824c3f7fd -size 46287 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/36fb8f844f936e7a1de4838da774f2f9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/376f80eb8a41369e87da63a0210d173e_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/376f80eb8a41369e87da63a0210d173e_img.jpg deleted file mode 100644 index 46d8fb01438d66a2c34fe25c8e458e2c00e3f8cf..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/376f80eb8a41369e87da63a0210d173e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:747790cfb989257b72e43ece75974de4dddc2cf89f393e090b9ff4ce1eced5e9 -size 53288 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/392a79ccd95e682ccd08f35ab2e64144_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/392a79ccd95e682ccd08f35ab2e64144_img.jpg deleted file mode 100644 index 1ba1f0442c0530e100bee77b15ff82f7bedc086f..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/392a79ccd95e682ccd08f35ab2e64144_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4b21d7425f01238d64a1f6541b98bfcf309008f2285df7ef45a2b6abd2e803c2 -size 44549 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/3a4f4369128594c5db0aa6b853c0666e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/4537891530c9f6f139a2e1ebf544edc4_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/4537891530c9f6f139a2e1ebf544edc4_img.jpg deleted file mode 100644 index 720e62b3dd1f29581d6387fc3a0db84068cd895f..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/4537891530c9f6f139a2e1ebf544edc4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:cb94dd948d4082880b51170e007e5fc621d77fdd2d358388fd56b29e105bd831 -size 59714 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/472a73112a9b2ed65777d54d33a3ba9c_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/472a73112a9b2ed65777d54d33a3ba9c_img.jpg deleted file mode 100644 index e70eaccaca8c54ec5e58f6dec4a0968ded4bed9b..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/472a73112a9b2ed65777d54d33a3ba9c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ff00cf1a3285ce2189aac767a29a7ea2c194e08997b04cb9094bac51ca5d39de -size 7920 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg deleted file mode 100644 index e873481907939580079c444e8a6a3d5f5f546b20..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/481b1f80fc31ebebb30d1f57d31e3af3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b04c8ff60016f230051fd1e6b7faab682b49355b563a68403fc5d65e0720146f -size 4564 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/4db00373eb0bec04341ee887235bbfea_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/4db00373eb0bec04341ee887235bbfea_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/4db00373eb0bec04341ee887235bbfea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg deleted file mode 100644 index 13f027ad39c3f9a8301637dbd99a36ae9bd61a23..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:789488ee6000e4ccc888cca349596a2ecc40605267eebd704ca6f81de75c5ba3 -size 46840 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/5e9af8986a5845504f251d3079da8078_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/5e9af8986a5845504f251d3079da8078_img.jpg deleted file mode 100644 index d27d8ec07efe403a20320fbfb32b506b2e8e4e0c..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/5e9af8986a5845504f251d3079da8078_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:634cd53064a9563fb93bf27ed1467a26098a5e02d46d5610434972beefcbdb38 -size 20805 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/5f5caa1debf59230cc4c1cda0e285ed9_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/5f5caa1debf59230cc4c1cda0e285ed9_img.jpg deleted file mode 100644 index b57a7e7ce2d6b9fd57d727d5e771de2562f370ee..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/5f5caa1debf59230cc4c1cda0e285ed9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:22f66fff47d6ed7e8ec26b24d800ab8e609a4f10173aa1f26998e148d8a6305f -size 15549 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg deleted file mode 100644 index fb3b22f192eccb61c0ab644483f72b18647fd42d..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/640d28a694bbdbaf9b11a3bfdcc800fc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:931d9168f5cf12d00d5d62d7952c50013ca5b864a5dce445ad1705112f6a214c -size 13085 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/64544fbada794f3cdf4f78f5d83613e4_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/64544fbada794f3cdf4f78f5d83613e4_img.jpg deleted file mode 100644 index 27e7f0e550310dfb2108283b668b986cfb931565..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/64544fbada794f3cdf4f78f5d83613e4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5770a366290f7c6a5b142b1994107fde0a3b7a59c3e6ae30602641f6318b63b -size 96076 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg deleted file mode 100644 index f51f1b725ce0eade7913f8a105ffd6ed0ff2d614..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1e3e72b9911f913757fd2efbbecea9ec539bcfbafd768eefa5314f95813a72cb -size 151378 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/69e5f1993021af230d08c08aac97d9df_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/69e5f1993021af230d08c08aac97d9df_img.jpg deleted file mode 100644 index 8659346bcf48d131bec3b24b10981ad9b3c0076a..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/69e5f1993021af230d08c08aac97d9df_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f78338743347639d93fd7e9b5c5f98502ec1e0919b87450476308bb780f792d5 -size 130314 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg deleted file mode 100644 index bbb9da63bcd78dd538a34d8ecc5912ec480ad280..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:50783cd391476b7179ff72db8d7a45385061e74e15d5e094e5481457aa8991b5 -size 34046 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/744acfe8d4e31bcf03f95714c2f6e567_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/744acfe8d4e31bcf03f95714c2f6e567_img.jpg deleted file mode 100644 index ef770b96c515d73adc13a164b4cb5e93e611af53..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/744acfe8d4e31bcf03f95714c2f6e567_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7312801a726a684e8ff647207bc72cb989a13f1906c2ea467afa1c8003792e1f -size 36622 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/77464a47f104d0d647b2414591137b64_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/77464a47f104d0d647b2414591137b64_img.jpg deleted file mode 100644 index 0736d493c56704358aaeaf3c03256872a4f6b393..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/77464a47f104d0d647b2414591137b64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e789a1226cccdd7653ea80e32ab4645d6f439f6c0b24cd2c5078c121d19a0723 -size 35932 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg deleted file mode 100644 index 4c5bfde44cc47e58683f5e7944c52e6c863658fc..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/78e846f2858d131dc5a4dcbabcca1e4d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d61b2db1c015f26e1743ce200552c9a9b0d4ede5b9c0847d8a19ef1aeb8cedbd -size 15487 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/7913c315e0db8233cb1ac2455e4a0a81_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/7913c315e0db8233cb1ac2455e4a0a81_img.jpg deleted file mode 100644 index ba10c7e9acc0669bb0e7fb120e9c145bad38c9a2..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/7913c315e0db8233cb1ac2455e4a0a81_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5c48612cf3a6f9405405110fedf524b0dd5e249d25c093ff570d94af4c6fd07d -size 52183 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/79898de98da3367d0ea9beef38f5c01c_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/79898de98da3367d0ea9beef38f5c01c_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/79898de98da3367d0ea9beef38f5c01c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/7d08458fbe0bd5f306c00c16d68b25f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/7f7211748473542096717109ebe5a9d6_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/7f7211748473542096717109ebe5a9d6_img.jpg deleted file mode 100644 index 80417c2e856efd3c0f3a527dcec725f468c07bc3..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/7f7211748473542096717109ebe5a9d6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f5226fed57c1013a28425180b9a45ec2ee9b14093d8a09b85fe8fd360e5ab37c -size 7966 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/829cdaf00f7219d70e571064b2b13291_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/829cdaf00f7219d70e571064b2b13291_img.jpg deleted file mode 100644 index e873481907939580079c444e8a6a3d5f5f546b20..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/829cdaf00f7219d70e571064b2b13291_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b04c8ff60016f230051fd1e6b7faab682b49355b563a68403fc5d65e0720146f -size 4564 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 9d55649b49cd8ee4bd4236d1939bb51c85a5ea2a..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5dd8375d88bcff1ef4cdc77c712482c64e9df5833d7cec3b0f0b1d7c6ad98b64 -size 4603 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/844077b3034f0030b404207db0ad76b4_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/844077b3034f0030b404207db0ad76b4_img.jpg deleted file mode 100644 index 50733bdb2a971d1323217ba3d179b8b39167c53f..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/844077b3034f0030b404207db0ad76b4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ec05bcca4190fbb1515f0fefef31f7e63e44cb59403fdaedc41107631a537cab -size 39786 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/854df8ad60507803253274673f9062cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9159d999b6514420a64eae80e52f1fd5_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9159d999b6514420a64eae80e52f1fd5_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9159d999b6514420a64eae80e52f1fd5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/91b12db3c85bbf466ad27eb3665a1b06_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/91b12db3c85bbf466ad27eb3665a1b06_img.jpg deleted file mode 100644 index 402dfe27fa903c39457663eb403d33b7649a90eb..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/91b12db3c85bbf466ad27eb3665a1b06_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b0956dc294388b8740b0cf0f05e91a5c24aab566f9d8ea0053e3dc8ec6f3b114 -size 67365 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/92979cab89ec8747992c43d33b6c51da_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/92979cab89ec8747992c43d33b6c51da_img.jpg deleted file mode 100644 index 594b3676c8a8e26520d994532b8710f535cff9dc..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/92979cab89ec8747992c43d33b6c51da_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:cbfcb5b599ecc743b43df67af67b747f8b2167a57ce740d6f8d6b80e8d1f71f1 -size 19691 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9658365eb8d9ea36ca5ca9a830508819_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9658365eb8d9ea36ca5ca9a830508819_img.jpg deleted file mode 100644 index ac3a467bd8bc759f47956421054c565a3325b3e7..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9658365eb8d9ea36ca5ca9a830508819_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7dd0320fde32fda8a79e1faef50df2e9d3ab509d3ad851573266c52c77fa6f66 -size 34192 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/990afa9d07fb81cf8760867cb4247a79_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/990afa9d07fb81cf8760867cb4247a79_img.jpg deleted file mode 100644 index e873481907939580079c444e8a6a3d5f5f546b20..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/990afa9d07fb81cf8760867cb4247a79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b04c8ff60016f230051fd1e6b7faab682b49355b563a68403fc5d65e0720146f -size 4564 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9e26cd5584f423e1b2155fb341db579f_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9e26cd5584f423e1b2155fb341db579f_img.jpg deleted file mode 100644 index 4fa4dd3d8e9af6858da4250c2a439541e755d336..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9e26cd5584f423e1b2155fb341db579f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e3afb726cc0a2fbbe9d8f9d104c42add2b56a03abd455bc6f9d0d6b1c44b343c -size 11321 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9f6dec4d4e9fde40bce018861ef1278e_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9f6dec4d4e9fde40bce018861ef1278e_img.jpg deleted file mode 100644 index 574d37cb1e302b5556065e866916d9aa325d186e..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/9f6dec4d4e9fde40bce018861ef1278e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:405de9a00e5621ec858118c4b967988374fa55ec777f3fcee6e7c058c828b6ed -size 58953 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg deleted file mode 100644 index 0c1762d773fa295d7e7544c82c63267b583f878d..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c82f6b51330382618c69af8a144ee2aa221c7130479cfbc2314a722b3468a86e -size 15759 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/a7a2a8be6bea14f9e4740dbb3d24437e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/a7fcb275d0eed586509a47f4f86a9725_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/a82aef1d2f3f1a527328950e9db947ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg deleted file mode 100644 index cbce551bfe6c484ff3a8fd8a6db1e147fa6d7868..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/ab846b81e78dbc8da2a6f9511e2f248a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:58e792523cc7321a3bcbc1f8f26633c19698483e16d02d4a8797d0b9752fee6f -size 44470 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/ac31fdfebb9751f7f10416dfe33bc872_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/ac31fdfebb9751f7f10416dfe33bc872_img.jpg deleted file mode 100644 index 3f2fd0f78a0e8041eb9214a9a3db96a256d1d1ef..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/ac31fdfebb9751f7f10416dfe33bc872_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8a92cb1114ef6e5d7a533f47edea977356b1510fbd043fa344c171910771f3c0 -size 66912 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/b2da20e7e7ccb0f7656992aa3b2d3062_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/b2da20e7e7ccb0f7656992aa3b2d3062_img.jpg deleted file mode 100644 index 09989206d3ecebd5ce5ba312f62e06edfa123793..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/b2da20e7e7ccb0f7656992aa3b2d3062_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1f3459c525e9a76c02109bc8922d4337d91e4f020d4c8e8588d0ccc0b7d403df -size 26101 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/bafee83a7eadee0dab23f856ae7228c1_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/bafee83a7eadee0dab23f856ae7228c1_img.jpg deleted file mode 100644 index ead099dd6899375926c429d9c0aa50c78f5c87c4..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/bafee83a7eadee0dab23f856ae7228c1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9523fac9bdc881a54e049aa0b453ab4fa965c7bc86e17765367852c1686819c5 -size 18519 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/bc0074c9be2d587e0b85224d9cb083ec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/c0c7f65c51c83fbe595b47326f6b089a_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/c0c7f65c51c83fbe595b47326f6b089a_img.jpg deleted file mode 100644 index ac95c678952dc6a0e47e06d5d6894d40ad039c6d..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/c0c7f65c51c83fbe595b47326f6b089a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4a0c576c52b89fd1948d8d835ddc5c876b16a73529e8260b32d3218f5e1906c4 -size 15001 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index e56eafa147abe886a74be5612d30f459b3d79aad..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5274eab1088d0344971f8767843769132fb44d6ad16a9d89bf109272124ea2c -size 4547 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg deleted file mode 100644 index 0a801dd2ecab3401992b48dc2bde5c829ec7a03b..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/d52ae84d18c68f7d66ee994f5eec34b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:610f672e2793f1c32c50e8d98df1c31573ef2d0985a7acb0fd53f3322fe617fb -size 4473 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/da0c058ea922c6a070a172412990e535_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/da0c058ea922c6a070a172412990e535_img.jpg deleted file mode 100644 index b6e6702853ec4df0c750954a6c3cbe718f924d5c..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/da0c058ea922c6a070a172412990e535_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:35c9fe41047ba3fdeaf6252cac99139321ed134e0fb2f03754fd817e7796756b -size 5405 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/da74b0e807fd62f32abdc3c05ffbabf4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/da8cb3d696f15f2c6de7aff6955d12d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e03e8c02d5fc29e318efe40bfe3762df_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e03e8c02d5fc29e318efe40bfe3762df_img.jpg deleted file mode 100644 index bd1ea5496d21ed31c3359f9608c323f2cc37eb02..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e03e8c02d5fc29e318efe40bfe3762df_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b660b3d7733dff6e06641ffae9aada86944facf0552d1ad78c2893acbd2e08de -size 69897 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e05434e963901d7e9c0bf5a6758200ed_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e05434e963901d7e9c0bf5a6758200ed_img.jpg deleted file mode 100644 index b562d724b086098c7c1efed22b36ff13557a202b..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e05434e963901d7e9c0bf5a6758200ed_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:cb873b4c0b07ac1ca7d7a99af644b19a95b4bc6aafd43df9bdfaa99f3ae660b0 -size 66798 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e11a88256307cfd7ebdbb5f6adcfa07a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e11e3fe4228e889a962514269f5a000b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index e873481907939580079c444e8a6a3d5f5f546b20..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e345315706e3fe633bb6d593246c01bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b04c8ff60016f230051fd1e6b7faab682b49355b563a68403fc5d65e0720146f -size 4564 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e417ae35ab07134888be901c201d54cd_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e417ae35ab07134888be901c201d54cd_img.jpg deleted file mode 100644 index fb167418a825b6b5cff004e9b76b3a838e421836..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e417ae35ab07134888be901c201d54cd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a9519af810251555b791a45181c37347a8c9d13d109cc0c2738f2372b912556 -size 82428 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/ea49c15f36ffb089d44f1d793f013778_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/ea49c15f36ffb089d44f1d793f013778_img.jpg deleted file mode 100644 index 3bd18d145c4dbb99dd1d4b9bf6fcfb8cdbc77ca0..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/ea49c15f36ffb089d44f1d793f013778_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f5c7d5ccf1073aaf845fdad0e58781e6caf471d0b8228ea786ca7ee5f5203c68 -size 31194 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/eadd8abb2c85161842bcd823881cbe5f_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/eadd8abb2c85161842bcd823881cbe5f_img.jpg deleted file mode 100644 index 4ed348338be96629744b7220426c812a250a1149..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/eadd8abb2c85161842bcd823881cbe5f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d8b1a7385262ad4947f4f339b4177eb4df37d95205264b5c368ea872f4378be8 -size 64417 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/f033879165b16c0b7c82e459042ec3f0_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/f033879165b16c0b7c82e459042ec3f0_img.jpg deleted file mode 100644 index 849ecd8bd041162e0b437efd9333d2b1cec47e44..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/f033879165b16c0b7c82e459042ec3f0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d5db7d3d2f1088f2fa8d6d62a5f51727ad83012feaf81b20d0eab2a1f4c1baa6 -size 29928 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/f64e1e0997695248c0cd4122c5b1a170_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/f64e1e0997695248c0cd4122c5b1a170_img.jpg deleted file mode 100644 index ba0724cd2416e6847b186756758cf136fb16ea27..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/f64e1e0997695248c0cd4122c5b1a170_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d331ad122eb1f07ed32831a5cdd10cb998fc826da5719d1da9a1ef9b05e254f -size 15069 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/f796c4b6ef101faa39b887a86820c3d1_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/f796c4b6ef101faa39b887a86820c3d1_img.jpg deleted file mode 100644 index c56ecaedf5cbaa93677d1bce83e06a058e41ce54..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/f796c4b6ef101faa39b887a86820c3d1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5590a1518c41b90cc3b03b2f9e1689a7953af831f6bb7fbdd7fea5b125ff2def -size 14416 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/fa01531ea2c45beeb4036005da3037a4_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/fa01531ea2c45beeb4036005da3037a4_img.jpg deleted file mode 100644 index a79d98e18e86a14f2aa30ee892649824f15487f2..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/fa01531ea2c45beeb4036005da3037a4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:21ffd091045cb10e32076c3085f1d8685617fbd82eb1d2608bcfa78d5118dcfc -size 35664 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg deleted file mode 100644 index 9d9a4dcfa473fbd34121a45f64f4588e67e235ee..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/fd30746c44f82f41d780ec264b0ee2d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e8fbbcd1220b218e03a9f31ec2e3695f0c5916ae10057d0a86111213e7d455cf -size 4523 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/fd76efce549d3713543bb5ed9b023c2e_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/fd76efce549d3713543bb5ed9b023c2e_img.jpg deleted file mode 100644 index 093c389f8aae1643c205a282c7ee0a65bf882380..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/fd76efce549d3713543bb5ed9b023c2e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2d83537ea6619f9b6ae32d86f547d82c1fa26a386f39524c99906670311c2b61 -size 17104 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg deleted file mode 100644 index 1194e5353bd73602c93bb0bc262be09ac63e09d9..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/fef7e3f08b408e4ab937a75f5c8b6bfc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:04b13214c6dbe50ad20f0888d942d86a54a92260a2ed92caf2b48318d4a05961 -size 66492 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/ff748955b94dcb8337283fbe12baa475_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/ff748955b94dcb8337283fbe12baa475_img.jpg deleted file mode 100644 index ab8747bcf11ee5cf47dcdd3c8b54b7c708088eff..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/ff748955b94dcb8337283fbe12baa475_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e27f16daf351d3488d0b74dd3d08e156d509b6380babeb760d41bf766bebaa24 -size 4527 diff --git a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/ffb6acd27b8e3a54392840948a75869f_img.jpg b/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/ffb6acd27b8e3a54392840948a75869f_img.jpg deleted file mode 100644 index d31f43ce5fe9df7baea4c1c2dc97b3962da4a70f..0000000000000000000000000000000000000000 --- a/files/WG7/O-RAN.WG7.TS.OMC-HRD-Opt7-2-R005-v05.01/images/ffb6acd27b8e3a54392840948a75869f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3e3afd99d615ae35e0a53e9a78bb4ae1ba26c10068deaa8c3abdfb71e4499104 -size 64868 diff --git a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/doc.md b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/doc.md deleted file mode 100644 index fe14d752d90df017e8f24750aa2ee1177f770c21..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/doc.md +++ /dev/null @@ -1,426 +0,0 @@ - - -![O-RAN ALLIANCE logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) - -The logo for the O-RAN ALLIANCE, featuring a colorful circular icon to the left of the text "O-RAN" in blue, with "ALLIANCE" in smaller blue letters underneath. - -O-RAN ALLIANCE logo - -# --- **O-RAN Open X-haul Transport Working Group****Architecture and Requirements for RAN Fronthaul over Converged Packet Transport Network** - -Copyright © 2025 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 - -| | | -|-------------------------------------------------------------------------------------|----| -| List of figures..... | 3 | -| Foreword..... | 4 | -| Modal verbs terminology..... | 4 | -| Executive summary ..... | 4 | -| Introduction ..... | 4 | -| 1 Scope ..... | 6 | -| 2 References ..... | 7 | -| 2.1 Normative references ..... | 7 | -| 2.2 Informative references..... | 7 | -| 3 Definition of terms, symbols and abbreviations..... | 8 | -| 3.1 Conventions..... | 8 | -| 3.2 Terms..... | 8 | -| 3.3 Symbols..... | 8 | -| 3.4 Abbreviations ..... | 8 | -| 4 Functional planes and data flows in the RAN fronthaul ..... | 9 | -| 4.1 Control Plane (C-Plane) ..... | 9 | -| 4.2 User Plane (U-Plane)..... | 10 | -| 4.3 Synchronization Plane (S-Plane)..... | 10 | -| 4.4 Management Plane (M-Plane)..... | 11 | -| 5 Functional Reference Architecture..... | 12 | -| 5.1 Provider Transport Network's demarcation ..... | 12 | -| 5.2 Transport Network Entity functional set in the Provider Transport Network ..... | 13 | -| 7 Conclusions ..... | 13 | -| Annex (informative): Change history/Change request (history) ..... | 14 | - -# --- List of figures - -Figure 1 An example of RAN Fronthaul .....5 - -Figure 2 C-Plane Protocol Structure.....10 - -Figure 3 U-Plane Protocol Structure .....10 - -Figure 4 S-Plane Protocol Structure .....11 - -Figure 5 M-Plane Protocol Structure.....11 - -Figure 6 Reference Functional Architecture for RAN Fronthaul in Converged Packet Transport Network.....12 - -# Foreword - -This Technical Specification (TS) has been produced by WG9 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. - -# Executive summary - -This document provides a functional reference architecture of the RAN Fronthaul over Converged Packet Transport Networks. It is intended to be used by operators to specify the building blocks of their fronthaul networks and to provide some deployment guidance. It is intended to be used by vendors to select what to implement and support in their products. - -# Introduction - -This specification is an implementation agreement. It does not define technology, but instead references standardized technologies from other SDs, e.g., ITU-T, IEEE, IETF, to establish requirements that ensure the realization of a packet transport network for RAN Fronthaul. - -Several fundamental changes in the radio access network (RAN) architecture were introduced in the evolution from 4G to 5G [3]. Utilizing new spectrum and beamforming radios results in a significant increase in radio capacity for 5G. The novel use cases asked for more deployment flexibility. These changes triggered the introduction of new splits in the RAN protocol stack. Figure 1 shows an example of the lower layer split (LLS), also known as fronthaul. Fronthaul, in conjunction with midhaul and backhaul, creates the end-to-end 5G RAN transport. - -![Diagram of RAN Fronthaul architecture showing Cell Site and Hub Site components connected by eCPRI interfaces.](e394c2b5c61344f6a12397f430086072_img.jpg) - -The diagram illustrates a RAN Fronthaul architecture. It is divided into two main sections: 'Cell Site' and 'Hub Site', connected by a 'Fronthaul' link. The 'Midhaul/Backhaul' is shown on the right side of the Hub Site. - -**Cell Site:** Contains two User Equipment (UE) units. The top UE connects to an O-RU via an 'Air Interface'. The O-RU connects to a 'CSR' (Cell Site Router) via an 'eCPRI' interface. The bottom UE connects to an 'RRH' via an 'Air Interface'. The RRH connects to a 'PHY' unit via a 'CPRI' interface. The PHY unit then connects to the 'CSR' via an 'eCPRI' interface. Both the O-RU and the PHY unit are connected to a 'Sync' block. - -**Hub Site:** Contains an 'HSR' (Hub Site Router) which receives 'eCPRI' traffic from the 'CSR'. The 'HSR' is connected to an 'O-DU' (Open Distributed Unit) via an 'eCPRI' interface. The 'O-DU' is connected to the 'Midhaul/Backhaul'. Both the 'HSR' and the 'O-DU' are connected to a 'Sync' block. - -**Legend:** - -- CSR – Cell Site Router -- HSR – Hub Site Router - -Diagram of RAN Fronthaul architecture showing Cell Site and Hub Site components connected by eCPRI interfaces. - -Juniper Business Use Only - -**Figure 1 An example of RAN Fronthaul** - -The 5G architecture and service expectations, including ultra-reliable high bandwidth, low latency, and jitter communication, demand a resilient and scalable network. With the introduction of the eCPRI [4] interface, a packetized Ethernet-based transport could be utilized in the fronthaul. In addition to Ethernet, a packetized fronthaul can leverage IP/MPLS transport technology to provide highly resilient and traffic-engineered transport. Most current dynamic IP routing protocols can provide a highly scalable and resilient underlay network for this architecture. In addition, the Service Level Agreement (SLA) of each application can be guaranteed via a service-aware transport network, assigning a service slice for the appropriate application based on its throughput and latency needs, among other criteria. - -The transport itself can be built from existing technologies like segment routing and SRv6 to provide the traffic engineering, resiliency, and Operations, Administration, and Maintenance (OAM) tools needed for fronthaul. Services like EVPN or IP-VPN can be created over this transport to provide transport with an appropriate SLA for Layer 2 eCPRI and, in the future, Layer 3 eCPRI. This packetized fronthaul can provide transportation for other applications as well, which is beyond the scope of this document. - -This document outlines the necessary transport service-specific requirements for the fronthaul and coordination of the interface to comply with the increased demands of 5G and beyond 5G networks. It lists the required functions to provide flexibility in mixing and matching different deployment scenarios, functional splits, and potentially other services on the same packet network. - -# 1 Scope - -Fronthaul networks have to provide flexibility to mix and match different deployment scenarios (CRAN, DRAN), functional splits, and other mobile traffic on the same packet network. CPRI remains the preferred choice for legacy (2G/3G) support. For 4G/5G technologies and beyond, the novel LLS and eCPRI together are capable of reducing bitrate requirements on the fronthaul for classic radios, preventing the rate explosion for massive MIMO, and enabling connectivity flexibility in packet fronthaul. - -The majority of today's deployments are DRANs, typically using wireless microwave links or leased lines transporting packets for S1/NG and X2 backhaul. However, CRANs enable key potential benefits, such as simplification antenna sites, full inter-site coordination, and operational gains by centralizing processing resources at hub sites. The flexible relationship between radios and physical ports on a baseband together with the user data-dependent characteristics of eCPRI/LLS, allows a baseband node to serve a larger set of radios and utilize processing capacity more efficiently. - -Several important characteristics of packet-based fronthaul networks need to be met, such as - -- Efficiency – make use of the statistical aggregation possibilities in eCPRI/LLS, -- Flexibility – allow for connectivity between all radios and all basebands, -- Scalability – small to large CRAN deployments using the same architectural principles, -- Resiliency – a robust network to minimize the effects of failures, -- Observability – based on the telemetry. -- Security – via service isolation, integrity and privacy protection. -- Simplicity – a network easy to dimension and deploy, -- RAN-agnostic – support of both purpose-built and cloud-native RAN networks, -- Synchronization – providing sync for the RAN components. - -A service overlay network architecture enables the separation of the physical network topology from the application service structure and connectivity. Packet-based transport can utilize protocols that have been broadly deployed and well-understood for years for sharing network topology and characteristic information. For example, the eCPRI L2 Ethernet traffic can be handled as a virtual overlay Ethernet service with fronthaul-specific strict service requirements. Such architecture can combine additional virtual overlay Ethernet or IP services with tailored characteristics. - -This networking concept provides ease of deployment and connection flexibility by enabling the establishment of software-defined overlays in combination with optional traffic-engineered paths. Distributed IP control protocols on the packet infrastructure make the network self-contained and give a fast response to failures. There is no need for multiple control planes as extensions in the routing protocols make it possible to distribute RAN-specific forwarding information (including traffic engineering). - -The overlay service runs on top of the packet network to create virtual network connectivity. e.g., via L2 EVPN or L3 IP-VPN services. The MP-BGP protocol and an SDN controller may drive the configuration and control of virtual networks and services. They can fully control traffic steering and traffic engineering for the virtual service by utilizing, for example, segment routing traffic engineering (SR-TE) capabilities of the transport infrastructure. - -The distribution of functions to different sites for tailored services drives the need to simplify the deployment and operation of both RAN and its related transport. A tight interaction between the two is necessary to achieve cost-efficient deployment and operation. - -Another essential new requirement is to provide a synchronization service in the new architecture. When transitioning from CPRI to eCPRI in the fronthaul, the time distribution between the baseband and O-RU has shifted from being carried by the CPRI frame itself to being carried by protocols like the packet-based precision time protocol (PTP) or Synchronous Ethernet (SyncE). ITU-T has specified several PTP profiles with relevant properties for telecom. Requirements for time alignment and frequency stability in the fronthaul network remain the same as those for CPRI-based solutions. - -For the RAN to support full functionality, a performant synchronization solution must be available. With packet switches in the fronthaul network, special attention must be given to maintaining synchronization to or between radios and ensuring - -sufficient synchronization availability. The transport nodes can distribute sync and hold-over functionality located in the RAN nodes (baseband, radio) or outside (packet nodes). to mitigate sync interruptions from e.g., GNSS-derived sources. - -The packet fronthaul transport is a cornerstone for future automation, because of (1) simplified deployment and maintenance via SDN orchestration, (2) service-aware routing and traffic engineering, and (3) compatibility with cloud-native RAN and containerized vRAN functions. - -Packet transport is not just a replacement for CPRI, but a whole transport network transformation: - -- Supports both DRAN and CRAN deployments. -- Optimizes OPEX and CAPEX by enabling multiplexing and centralization. -- Provides a scalable foundation for 6G-ready architectures with integrated synchronization, SDN, and cloud-native capabilities. - -The scope of the Technical Specification includes: - -- To provide functional reference architecture and nodal requirements for realizing transport services for the O-RAN fronthaul interfaces in the converged packet-switching transport networks. The packet-switching transport consists of one or more packet transport functions between the fronthaul radio and baseband equipment, e.g., O-RU and O-DU. Applicability to the fronthaul interfaces other than those defined in O-RAN is not precluded. -- To define end-to-end reference architecture for transport network solution based on a packet-switched technology and services addressing control, user, and management traffic in support of the packet-switching fronthaul transport. -- Transport for RAN synchronization distribution in packet-switching fronthaul. -- Security in fronthaul, including all planes - data, control, management, and synchronization. -- Produce industry awareness and liaisons to relevant SDOs. - -# --- 2 References - -## 2.1 Normative references - -- [1] O-RAN.WG1.TS.OAD: "O-RAN Architecture Description". -- [2] O-RAN.WG1.TS.Slicing-Architecture-R004-v13.01: "O-RAN Slicing Architecture 13.01". -- [3] 3GPP, 3GPP TS 38.401, NG-RAN; "Architecture description". -- [4] Common Public Radio Interface V2.0, 2019: "eCPRI Interface Specification". -- [5] O-RAN.WG4.TS.CUS.0-R004-v18.00: "Control, User and Synchronization Plane Specification". - -## 2.2 Informative references - -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. - -- [i1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". -- [i2] ETSI 20180426 Version 1.1: "ETSI PAS Process Guide". -- [i3] IEEE: "2021 IEEE SA Standards Style Manual". -- [i4] ITU-T A-1500: "Author's guide for drafting ITU-T Recommendations". -- [i5] ITU-T 14 February 2020: "Manual for rapporteurs and editors". -- [i6] IETF RFC 2119: "Key words for use in RFCs to Indicate Requirement Levels". -- [i7] IETF RFC 8174: "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words". -- [i8] IEEE 802.1Q-2018: "IEEE Standard for Local and metropolitan area networks--Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks". -- [i9] IEEE 802.3-2022: "IEEE Standard Ethernet". -- [i10] ITU-T G.8013/Y.1731 June 2023: "OAM functions and mechanisms for Ethernet based networks". - -| | | -|-------|----------------------------------------------------------------------------------------------| -| [i11] | IETF RFC 5036 October 2007: “LDP Specification”. | -| [i12] | IETF RFC 3209 December 2001: “RSVP-TE: Extensions to RSVP for LSP Tunnels”. | -| [i13] | IETF RFC 8660 December 2019: “Segment Routing with the MPLS Data Plane”. | -| [i14] | IETF RFC 1195 December 1990: “Use of OSI IS-IS for Routing in TCP/IP and Dual Environments”. | -| [i15] | IETF RFC 4271 January 2006: “A Border Gateway Protocol (BGP-4)”. | -| [i16] | IETF RFC 7432 February 2015: “BGP MPLS-Based Ethernet VPN”. | - -# --- 3 Definition of terms, symbols and abbreviations - -## 3.1 Conventions - -The Architecture and Requirements for RAN Fronthaul in Converged Packet Transport Networks document uses the conventions and style conformant to ETSI Publicly Available Specification (PAS). See ETSI PAS Process Guide [i2] for details. However, the document makes numerous references to works of other organizations that comply with their own conventions and style guidance, which may or may not align with ETSI PAS. For example: - -- IEEE SA - 2021 IEEE SA Standards Style Manual [i3]. -- ITU-T - Author's guide for drafting ITU-T Recommendations [i4]. -- ITU-T Manual for rapporteurs and editors [i5]. -- IETF - Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words [i7]. -- IETF - Key words for use in RFCs to Indicate Requirement Levels [i6]. - -Attention and care should be taken to understand and comply with the conventions of each referenced document. - -## 3.2 Terms - -Void - -## 3.3 Symbols - -Void - -## 3.4 Abbreviations - -For the purposes of the present document, the abbreviations [given in [i.1] and the following] apply: - -| | | -|----------|---------------------------------------------------| -| AC | Attachement Circuit | -| BGP | Border Gateway Protocol | -| CAPEX | Capital Expence | -| CPRI | Common Public Radio Interface | -| CRAN | Centralized RAN | -| DRAN | Distributed RAN | -| ETSI PAS | ETSI Publicly Available Specification | -| ETSI | European Telecommunications Institute | -| EVPN | Ethernet VPN | -| EVPN | Ethernet VPN | -| GNSS | Global Navigation Sattelite System | -| IEEE | Institute of Electrical and Electronics Engineers | -| IETF | Internet Engineering Task Force | -| IGP | Interior Gateway Protocol | - -| | | -|--------|-----------------------------------------------| -| IP | Internet Protocol | -| IS-IS | Intermediate System to Intermediate System | -| ITU | International Telecommunication Union | -| ITU-T | ITU- Telecommunication Standardization Sector | -| L2 | Layer 2 | -| L3 | Layer 3 | -| LDP | Label Distribution Protocol | -| LLS | Lower Layer Split | -| LSP | Label Switched Path | -| MIMO | Multiple Input Multiple Output | -| MP-BGP | Multi-protocol BGP | -| MPLS | Multiprotocol Label Switching | -| O-DU | O-RAN Distributed Unit | -| OPEX | Operational Expence | -| O-RU | O-RAN Radio Unit | -| PRACH | Physical Random Access Channel | -| PTN | Packet Transport Network | -| PTP | Precision Time Protocol | -| RAN | Radio Access Network | -| SDN | Software-Defined Networking | -| SDO | Standard Defining Organization | -| SR-TE | Segment Routing Traffic Engineering | -| SyncE | Synchronous Ethernet | -| TNE | Transport Network Element | -| VPN | Virtual Private Network | -| VPN | Virtual Private Network | - -# 4 Functional planes and data flows in the RAN fronthaul - -In the O-RAN architecture, a single split point, known as "7-2x", is chosen as the functional split for defining the fronthaul interface between O-DU and O-RU. The split 7-2x allows a variation in placing the precoding function either in the O-DU or in the O-RU. In other architectures, the split can be at different points. The fronthaul interface facilitates the transmission of control, user, and management data between O-DU and O-RU. - -The fronthaul is divided into Control, User, and Synchronization Plane (CUS-Plane) and the Management Plane (M-Plane) to support different types of data flows. The CUS-Plane carries both real-time and non-real-time traffic, including user data and control information required for radio signal processing, while the M-Plane handles configuration, monitoring, and management features. - -## 4.1 Control Plane (C-Plane) - -Control Plane (C-Plane) handles real-time control and signaling information between O-DU and O-RU. C-Plane provides instructions on scheduling, beamforming, and resource allocation to coordinate the transmission of user data. The C-Plane also ensures that O-RU processes and transmits data according to the O-DU's instructions while supporting advanced radio features. C-Plane messages have lower bandwidth requirements, whereas they have higher reliability requirements. - -The C-Plane supports the eCPRI protocol over Ethernet networks illustrated in Figure 2, which provides encapsulation and prioritization for control messages distinct from user data. C-Plane messages are not concatenated with User Plane (U-Plane) messages within the same Ethernet frame. The C-Plane protocol stack may also include IP/UDP for data transmission, if supported by both the transmitting and receiving nodes. - -The C-Plane features include: - -- C-Plane provides low-latency and high-reliability signaling, which is necessary for 5G features such as massive MIMO (Multiple-Input Multiple-Output) and network slicing. - -![Figure 2 C-Plane Protocol Structure diagram showing a stack of four layers: eCPRI, IP/UDP (optional), Eth L2 + VLAN, and Eth L1.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) - -| | -|-------------------| -| eCPRI | -| IP/UDP (optional) | -| Eth L2 + VLAN | -| Eth L1 | - -Figure 2 C-Plane Protocol Structure diagram showing a stack of four layers: eCPRI, IP/UDP (optional), Eth L2 + VLAN, and Eth L1. - -**Figure 2 C-Plane Protocol Structure** - -- It facilitates dynamic scheduling and flexible resource allocation for radio transmissions. -- It enables real-time beamforming control for advanced antenna systems. -- With support for slot-level signaling instructions, C-Plane enables data-flow coordination and efficient and adaptive radio access. - -## 4.2 User Plane (U-Plane) - -User Plane (U-Plane) supports transport of user data i.e., IQ (In-phase Quadrature) samples representing digitized radio signals between O-DU and O-RU for uplink and downlink transmissions. U-Plane is also responsible for transferring PRACH (Physical Random Access Channel) IQ from O-RU to O-DU needed for initial UE access. U-Plane may utilize compression for IQ sample transmission to maximize throughput and efficiency of fronthaul. - -The U-Plane supports the eCPRI protocol over Ethernet networks illustrated in Figure 3. The U-Plane protocol stack may also include IP/UDP for data transmission, if supported by both the transmitting and receiving nodes. - -![Figure 3 U-Plane Protocol Structure diagram showing a stack of four layers: eCPRI, IP/UDP (optional), Eth L2 + VLAN, and Eth L1.](54fabc351eda5228d2fa28cd9ba07971_img.jpg) - -| | -|-------------------| -| eCPRI | -| IP/UDP (optional) | -| Eth L2 + VLAN | -| Eth L1 | - -Figure 3 U-Plane Protocol Structure diagram showing a stack of four layers: eCPRI, IP/UDP (optional), Eth L2 + VLAN, and Eth L1. - -**Figure 3 U-Plane Protocol Structure** - -The U-Plane features include: - -- U-Plane provides high-bandwidth and low-latency data transfer for user data. -- It can utilize efficient compression techniques for IQ samples transmission to maximize fronthaul efficiency. -- It supports fragmentation and reassembly of O-RU to O-DU user data packets. -- U-Plane supports massive MIMO and dynamic beamforming. -- It works closely with the C-Plane to ensure data delivery aligns with dynamic scheduling and radio resource allocations. - -## 4.3 Synchronization Plane (S-Plane) - -Synchronization Plane (S-Plane) is responsible for maintaining synchronization between O-RAN components and with references such as GNSS in terms of frequency, time and phase. S-Plane achieves synchronization by distributing precise clock signals from grandmaster, PTP messages and SyncE signals as required by different synchronization configurations. - -The S-Plane supports PTP and SyncE protocols over Ethernet networks illustrated in Figure 4. - -![Figure 4 S-Plane Protocol Structure diagram showing a stack of protocols: PTP and SyncE at the top, followed by Eth L2, and Eth L1 at the bottom.](e9314c83043183351ed74908e9bf2f90_img.jpg) - -| | | -|--------|-------| -| PTP | SyncE | -| Eth L2 | | -| Eth L1 | | - -Figure 4 S-Plane Protocol Structure diagram showing a stack of protocols: PTP and SyncE at the top, followed by Eth L2, and Eth L1 at the bottom. - -Figure 4 S-Plane Protocol Structure - -The S-Plane features include: - -- It maintains precise frequency, time and phase synchronization across O-RUs and O-DUs. -- S-plane provides delay compensation for fronthaul links with variable latency. -- It supports standard synchronization protocols (PTP and SyncE) for interoperability and easier integration. -- It provides precise timing alignment for advanced radio features such as TDD, carrier aggregation, MIMO and beamforming. - -## 4.4 Management Plane (M-Plane) - -Management Plane (M-Plane) responsible for non-real-time management operations of O-RU. It facilitates initialization, configuration and management of O-RU. It supports both hierarchical model (O-RU managed by O-DU) and hybrid model (O-RU managed by network management systems). To support different functionalities, various types of messages are carried over M-Plane which includes configuration management commands, performance management reports, fault management notification, and messages for software management. - -M-Plane uses NETCONF/YANG as the network element management protocol and data modelling language. It requires an end-to-end IP connectivity between O-RU and the elements managing it. The M-Plane protocols stack is displayed in Figure 5. - -![Figure 5 M-Plane Protocol Structure diagram showing a stack of protocols: NETCONF at the top, followed by SSH/TLS, TCP, IP, Eth L2 + VLAN, and Eth L1 at the bottom.](7c6d9bfe9c31ce872722d60b73d20df1_img.jpg) - -| | -|---------------| -| NETCONF | -| SSH/TLS | -| TCP | -| IP | -| Eth L2 + VLAN | -| Eth L1 | - -Figure 5 M-Plane Protocol Structure diagram showing a stack of protocols: NETCONF at the top, followed by SSH/TLS, TCP, IP, Eth L2 + VLAN, and Eth L1 at the bottom. - -Figure 5 M-Plane Protocol Structure - -The M-Plane features include: - -- It enables multi-vendor support with standardized models for seamless integration. -- It supports both hierarchical and hybrid management architectures, enabling flexible deployment. -- It provides mechanisms for software upgrades, logging, and advanced diagnostics to maintain a performant and reliable RAN system. - -# 5 Functional Reference Architecture - -![Figure 6: Reference Functional Architecture for RAN Fronthaul in Converged Packet Transport Network. The diagram shows an 'Antenna site' on the left with three Radio Units (RUs) connected to mobile devices (phone, car, laptop) via air interfaces. Each RU is connected via an 'Ethernet' link to a Transport Network Element (TNE). The TNEs are connected to a central 'IP and/or MPLS Transport Network' cloud. Inside this cloud, there are three logical paths: 'EVPN', 'VPLS/PW', and 'Ethernet'. Each path connects to another TNE on the right side of the cloud. These TNEs are then connected via 'Ethernet' links to three Distributed Units (DUs). The DUs are connected to a 'Midhaul/Backhaul' cloud. Two 'Sync' boxes are shown, one at the bottom left of the antenna site and one at the bottom right of the hub site, indicating synchronization points.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg) - -DU – Distributed Unit - RU – Radio Unit - TNE – Transport Network Element - - - - represents a bidirectional logical connection - -Figure 6: Reference Functional Architecture for RAN Fronthaul in Converged Packet Transport Network. The diagram shows an 'Antenna site' on the left with three Radio Units (RUs) connected to mobile devices (phone, car, laptop) via air interfaces. Each RU is connected via an 'Ethernet' link to a Transport Network Element (TNE). The TNEs are connected to a central 'IP and/or MPLS Transport Network' cloud. Inside this cloud, there are three logical paths: 'EVPN', 'VPLS/PW', and 'Ethernet'. Each path connects to another TNE on the right side of the cloud. These TNEs are then connected via 'Ethernet' links to three Distributed Units (DUs). The DUs are connected to a 'Midhaul/Backhaul' cloud. Two 'Sync' boxes are shown, one at the bottom left of the antenna site and one at the bottom right of the hub site, indicating synchronization points. - -**Figure 6 Reference Functional Architecture for RAN Fronthaul in Converged Packet Transport Network** - -A functional reference architecture is a blueprint that outlines a system's functions and their interactions, providing a generalized, reusable model that can be adapted to create specific solutions. It focuses on what the system does (the functions) without delving into the specifics of how it's implemented (the physical architecture), making it useful for design, testing, and development, as well as ensuring consistency across different projects or systems. - -This project approaches the RAN Fronthaul transport architecture from the perspective of the Provider Transport Network (PTN). Mobile traffic in all planes, as noted in Section 4, is considered application (overlay) data of the respective PTN tunnels and is transparent to the PTN. In the scope of this document, transporting over the PTN the Ethernet-encapsulated traffic of the Control, User, Synchronization planes. As a result, the PTN provides transparent bridging of Ethernet frames. For this document, IP forwarding based on information in a packet that belongs to CUS-Planes of the RAN Fronthaul is outside the scope of this document. - -The PTN, shown in Figure 6, provides fronthaul interface service using a combination of underlying network technologies, such as Ethernet, IP, and MPLS. Some underlay technologies, e.g., Segment Routing, allow for path engineering, thus improving utilization of network capacity. Other technologies, such as RFC 9543 Network Slicing, support resource reservation in combination with path engineering, thereby realizing the traffic engineering paradigm. In some deployment scenarios, PTN can use EVPN over Segment Routing in IPv6 (SRv6), in MPLS (SR-MPLS), or IP/MPLS underlay. In other deployments, PTN can use an Ethernet underlay network. - -## 5.1 Provider Transport Network's demarcation - -The Ethernet Attachment Circuits (AC) provide reference points for network demarcation. TNE's interfaces facing RU or DU support Ethernet AC in port and VLAN modes. In the port mode, all traffic is processed regardless of any VLAN tags present. In the latter mode, individual VLANs are treated as separate connections. That can be used with simple or multiple tags (IEEE 802.1Q [i8][i8]). Furthermore, the TNE's set of functions includes the Ethernet OAM, as defined in Link OAM (Clause 57/IEEE 802.3 [i9]) and/or ITU-T G.803/Y.1731 [i10] [i10], that provides essential for operating the fronthaul interface at the required quality level. - -## 5.2 Transport Network Entity functional set in the Provider Transport Network - -A TNE, which is a part of the PTN that provides transport service for the fronthaul interface, includes functions in the data, control, and management planes. For example, a TNE that is part of the MPLS-based PTN supports a label distribution mechanism. Label distribution can be provided by LDP [i11], RSVP-TE [i12] for IP/MPLS networks, or by the Segment Routing extension of Interior Gateway Protocols (IGPs) for SR-MPLS [i13][i13] networks to set up LSPs. Also, labels can be provisioned over the management plane. A TNE that is a part of an IP-based PTN includes a mechanism that provides dynamic route information distribution, for example, by IS-IS [i14], as an example of IGP. In some environments, routing information can be provisioned using the paradigm of the Software Defined Network using the management plane. Segment Routing, through IGP extensions, enables path engineering for PTN. BGP [i15] can be used as the control plane of the Ethernet VPN (EVPN) [i16], a technology that provides virtual Layer 2 connectivity between dispersed sites over an IP or MPLS network. - -# --- 7 Conclusions - -The specification positions packet-based fronthaul not merely as a CPRI replacement but as a transformational enabler for future RAN architectures, including 6G, with integrated synchronization, SDN orchestration, and cloud-native support. - -# Annex (informative): Change history/Change request (history) - - - - - - - -| Date | Revision | Description | -|------------|----------|------------------------------------------------------------------------| -| 2019.01.22 | 00.00.01 | Create initial O-RAN version, with change-marks from previous content. | -| 2019.01.24 | 00.00.02 | Implemented CRs ERI-0011, NOK-0032 and DCM-0008 | -| 2019.01.31 | 01.00 | Final version 01.00 | -| | | | \ No newline at end of file diff --git a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.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/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/185df94f4a6a5245323255e844a30ec0_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/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/27b06ec9f42b5d727a2630f61a5f1861_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/27b06ec9f42b5d727a2630f61a5f1861_img.jpg deleted file mode 100644 index 60fedaecf3cf3292c206b11f2e2ffa60cc46a97b..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/27b06ec9f42b5d727a2630f61a5f1861_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2979d9c52996f2cae020f499eada2d1720d5ca50b1f6f85b38fb381466173e8f -size 80390 diff --git a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg deleted file mode 100644 index 6177c192b8095c822629c12267aee127710e5472..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fe682a4c29533798084a021326af3585ef2aba84d012e512eb624d7b29feada8 -size 4590 diff --git a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index c5c6fd3ba38d7d3881c6836ab72c888b45162e8f..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.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/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/54fabc351eda5228d2fa28cd9ba07971_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/54fabc351eda5228d2fa28cd9ba07971_img.jpg deleted file mode 100644 index 69f653f9f64be7653a0e6381f4e15a68cbb6ae91..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/54fabc351eda5228d2fa28cd9ba07971_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ee19081a7d87d09531fece20f1a0ad2d10d92f24b4be8e66e742520960485b9d -size 9092 diff --git a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.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/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg deleted file mode 100644 index 27b12127576bbbd64861512b30334977c22437ba..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/7c6d9bfe9c31ce872722d60b73d20df1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6c1c67d538bb65c4ae0b0c39f8116702f9255a9bf6276691dcbbf4aeadf5e4a5 -size 10692 diff --git a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/7ccb49293384cf59a3bbe659b053f3cc_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/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg deleted file mode 100644 index 7429cee58f6b43bf97b2e7ad3fe464ee11aaefc7..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/83ee9f10bd3636e192d68decf7f04cec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:15547aceb1e524165623668b58b2c28cd3e14dc6c6309b856741316a94e85300 -size 4494 diff --git a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/854df8ad60507803253274673f9062cf_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/854df8ad60507803253274673f9062cf_img.jpg deleted file mode 100644 index 9b1a19bf382de0ddb1d0ed1207c6eab10aa26669..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/854df8ad60507803253274673f9062cf_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/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 2994d9f720d2a888914c7ec44aef224aa81387c7..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/89100a6476d1d96f22c192db16502fec_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/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 979ff6a483b5b1efe6653ecef16753cf4e35c6ca..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/8dcca7651accff77ce832523fe2c7e64_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/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 7000eb688193144b835369e9a36cb3528f3dc195..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/c389468860cd886ab9c732473e959f0f_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/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg deleted file mode 100644 index b4513469ba6caf80b2205ca7bdcacee8c2dcfd63..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:01cd381d7cc80e3c474f57f18c8efd6a7d2e870644b9e817899a929b27cd7814 -size 8607 diff --git a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/e345315706e3fe633bb6d593246c01bf_img.jpg deleted file mode 100644 index 8fabf3d89b808a92981a41d3a5446b8b1d83a581..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.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/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/e394c2b5c61344f6a12397f430086072_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/e394c2b5c61344f6a12397f430086072_img.jpg deleted file mode 100644 index c31c5c9a361869047e140221da1f44d7f4d4e2ea..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/e394c2b5c61344f6a12397f430086072_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1ae06994134d05684a465a987ffac2739274e936fd4db83c38ef7bc29c7fd5d9 -size 50124 diff --git a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg b/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg deleted file mode 100644 index 00656e904339ce4c5a1852618c14800cfe19a80d..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.TS.ARCH-REQ-RAN-FH-CPTN .X-R005-v01.00/images/e9314c83043183351ed74908e9bf2f90_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:488b20fbc53cfa0cf22f83d5675dcf975bd3d0be0845a1d39692b73014cd1644 -size 6622 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/doc.md b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/doc.md deleted file mode 100644 index be0927d49cf96bbc4264fd33c904f19c477def35..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/doc.md +++ /dev/null @@ -1,9048 +0,0 @@ - - -![O-RAN ALLIANCE logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) - -The logo for the O-RAN ALLIANCE. It features a colorful circular icon on the left, composed of segments in red, orange, yellow, green, and blue. To the right of the icon, the text "O-RAN" is written in a bold, blue, sans-serif font. Below "O-RAN", the word "ALLIANCE" is written in a smaller, blue, sans-serif font, with wide letter spacing. - -O-RAN ALLIANCE logo - -ORAN-WG9.XPSAAS.0-R005-v10.00 - -Technical Specification - -# **O-RAN Open Xhaul Transport Working Group 9****Xhaul Packet Switched Architectures and Solutions** - -Copyright © 2025 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 - -![O-RAN Alliance logo](c803f6f6e2c49429d2951832bd0f208d_img.jpg) - -O-RAN Alliance logo - -1 - -# 1 Revision History - -| Date | Revision | Author | Description | -|------------|----------|-----------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 2020/11/11 | V01.00 | All Authors | 1 st revision outlining a packet switched O-RAN solution based on an underlay transport infrastructure based on MPLS or IPv6 with Segment Routing (SRv6) with mobile services provided by Multi-protocol BGP based VPNs. | -| 2021/07/01 | V02.00 | Simon Spraggs, Krzysztof Grzegorz Szarkowicz, Luis Miguel Contreras Murillo, Ivan Bykov, Lujing Cai | Update of references as required. Addition of annex F describing a packet switched slicing solution appropriate to slicing phase 1 described in O-RAN.WG1.Slicing-Architecture-v05.00 | -| 2022/02/27 | V03.00 | Simon Spraggs, Krzysztof Grzegorz Szarkowicz | Updates to annex F to support slicing phase 1 and 2 as described in O-RAN.WG1.Use Cases Detailed Specification-v06.00. Addition of a section on TNE security. | -| 2022/10/28 | V04.00 | Krzysztof Grzegorz Szarkowicz, Phil Bedard, Simon Spraggs | Updates to Annex F to support slicing phase 3 as described in O-RAN.WG1.Slicing-Architecture-v07.00. Updates of section 17 about TNE security (adding physical security, user security, control plane security and IEEE 802.1X). Updated Section 18 about service slice to underlay transport plane mapping. Updates to reference list. Updated Section 11.5.1 about Seamless MPLS with transport planes. Updated Section 9.4 to clarify which IETF documents can be referenced. Annex ZZZ (O-RAN Adopter License Agreement) removed, as it is no longer needed | -| 2023/02/24 | V05.00 | Krzysztof Grzegorz Szarkowicz | Updates to Section 17.4 about IEEE 802.1X | -| 2023/06/09 | V06.00 | Ivan Bykov, Lujing Cai, Krzysztof Grzegorz Szarkowicz | Updates of references as required. Updates to Section 10 regarding CTI references. Updates to Annex F regarding slicing phase 4 in Midhaul. | -| 2023/09/27 | V07.00 | Krzysztof Grzegorz Szarkowicz | Updates references, as required (added 3GPP references related to certificate management, added IETF reference related to 5G transport slicing). Updates section 17.4 (IEEE 802.1X authentication towards Compute and O-Cloud-Gateways; additional section about certificate management) | -| 2024/02/16 | V08.00 | Nicolas Fevrier, Luis Miguel Contreras Murillo, Ole Reinartz, Krzysztof Grzegorz Szarkowicz, | Addition of Section 17.2.3: “Security Protocols”, and Section 19: “Energy efficiency in the context of Xhaul Packet Switched Transport Network Equipments” | -| 2025/07/14 | V09.00 | Krzysztof Grzegorz Szarkowicz, Richard Roberts | Enhancements to Section 19: “Energy efficiency in the context of Xhaul Packet Switched Transport Network Equipments”. | - -![O-RAN ALLIANCE logo](7ee2d12e8cbaacaf65b0c332d1c76daf_img.jpg) - -O-RAN ALLIANCE logo - -| | | | | -|------------|--------|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | |

Modification of section 3 with TN scope clarifying scope with WG6/O-CLOUD – removed obsolete content

New content in section 6 with reference design and terminology alignment

Minor changes: search and replace all occurrence Transport Network Element to Transport Network Equipment (except ref to management document)

| -| 2025/11/01 | V10.00 | Sapna Sangal, Luis Miguel Contreras Murillo |

Adding subsections about D2 interface (7.3, 8.8, 8.9, 20.4.3) and updating subsection 9.1.

Adding section 21: Applicability of IETF Computing-Aware Traffic Steering (CATS) to O-RAN Scenarios

| - -1 - -2 - -## 1.1 Contributors - -3 - -Editor: Krzysztof Grzegorz Szarkowicz - -4 - -Contributors in alphabetical order: Jennifer Andreoli-Fang, Phil Bedard, Lujing Cai, Nicolas - -5 - -Fevrier, Francois Fredricx, Ivan Bykov, Kashif Islam, Luis Miguel Contreras Murillo, Toby Rees, - -6 - -Ole Reinartz, Sapna Sangal, Simon Spraggs, Krzysztof Grzegorz Szarkowicz, Reza Vaez-Ghaemi, - -7 - -Nader Zein, Jeffrey Zhang - -![O-RAN Alliance logo](dc1e692e5b7efd8e5a2a790c458646d9_img.jpg) - -O-RAN Alliance logo - -1 - -2 - -# 2 Contents - -| | | | | -|----|--------|-----------------------------------------------------------------------------------|----| -| 3 | 1 | Revision History ..... | 2 | -| 4 | 1.1 | Contributors..... | 3 | -| 5 | 2 | Contents ..... | 4 | -| 6 | 3 | Scope..... | 9 | -| 7 | 3.1 | Overview ..... | 9 | -| 8 | 3.2 | Version History..... | 11 | -| 9 | 4 | References ..... | 13 | -| 10 | 5 | Definitions and abbreviations..... | 21 | -| 11 | 5.1 | Definitions..... | 21 | -| 12 | 5.2 | Abbreviations..... | 21 | -| 13 | 6 | Transport network Reference Design and Requirements..... | 28 | -| 14 | 6.1 | Reference Design and Terminology..... | 28 | -| 15 | 6.2 | Transport Network Requirements ..... | 29 | -| 16 | 7 | 5G logical connectivity requirements ..... | 31 | -| 17 | 7.1 | Fronthaul ..... | 31 | -| 18 | 7.1.1 | O-RAN 7.2x Fronthaul ..... | 31 | -| 19 | 7.1.2 | O-RAN Fronthaul logical transport requirements..... | 33 | -| 20 | 7.2 | Non-ORAN Fronthaul..... | 33 | -| 21 | 7.2.1 | eCPRI based C-RAN solutions..... | 34 | -| 22 | 7.2.2 | Radio over Ethernet (RoE) based C-RAN solutions..... | 34 | -| 23 | 7.2.3 | Non O-RAN Fronthaul logical transport requirements ..... | 35 | -| 24 | 7.3 | D2 interface transport requirements ..... | 35 | -| 25 | 7.4 | Midhaul logical transport requirements..... | 36 | -| 26 | 7.4.1 | Overall Midhaul logical transport requirements ..... | 37 | -| 27 | 7.5 | Backhaul logical transport requirements ..... | 37 | -| 28 | 7.5.1 | Overall Backhaul logical transport requirements..... | 38 | -| 29 | 8 | Operator's use cases..... | 39 | -| 30 | 8.1 | Scenario 1: C-RAN architecture with collocated O-DU and O-CU ..... | 40 | -| 31 | 8.2 | Scenario 2: C-RAN architecture with collocated O-RU and O-DU ..... | 41 | -| 32 | 8.3 | Scenario 3: C-RAN architecture with coexistence of legacy Backhaul traffic..... | 41 | -| 33 | 8.4 | Scenario 4: C-RAN architecture with coexistence of legacy Fronthaul traffic ..... | 42 | -| 34 | 8.5 | Scenario 5: C-RAN architecture with further split of O-DU and O-CU..... | 43 | -| 35 | 8.6 | Scenario 6: C-RAN architecture with local breakout ..... | 44 | -| 36 | 8.7 | Scenario 7: Transport slicing ..... | 44 | -| 37 | 8.8 | Scenario 8/9: C-RAN architecture with co-located O-DUs ..... | 47 | -| 38 | 8.9 | Scenario 10: C-RAN architecture with non co-located O-DUs..... | 48 | -| 39 | 9 | Overall packet switched Open Xhaul architecture..... | 49 | -| 40 | 9.1 | Physical layout and xHaul transport options..... | 49 | -| 41 | 9.2 | Open Xhaul architecture in revision 1 and 2..... | 50 | -| 42 | 9.3 | Technology and architectural choices ..... | 51 | -| 43 | 9.4 | Standardization ..... | 51 | -| 44 | 9.5 | Document organization ..... | 52 | -| 45 | 10 | Physical network design for packet switched Xhaul..... | 52 | -| 46 | 10.1 | Packet over fibre ..... | 54 | -| 47 | 10.1.1 | Access..... | 54 | -| 48 | 10.1.2 | Pre-aggregation / Aggregation / Core transport..... | 58 | -| 49 | 10.2 | Alternative physical transport solutions ..... | 60 | -| 50 | 10.2.1 | WDM in access network ..... | 60 | - -![O-RAN ALLIANCE logo](a0167e3dcece9dcd8a378bcd98fb9cfa_img.jpg) - -O-RAN ALLIANCE logo - -| | | | | -|----|--------|-----------------------------------------------------------------------------|-----| -| 1 | 10.2.2 | Passive Optical Networks (PONs)..... | 60 | -| 2 | 10.2.3 | DOCSIS Networks ..... | 65 | -| 3 | 10.2.4 | Microwave and mmwave radio transport technologies..... | 68 | -| 4 | 10.3 | Data Centers ..... | 75 | -| 5 | 10.3.1 | Complete separation between DC and WAN infrastructure..... | 75 | -| 6 | 10.3.2 | DC integrated into WAN infrastructure. .... | 75 | -| 7 | 11 | Packet-switched underlay network – MPLS based..... | 75 | -| 8 | 11.1 | MPLS data plane..... | 76 | -| 9 | 11.2 | MPLS control plane ..... | 77 | -| 10 | 11.3 | Classic MPLS control plane ..... | 78 | -| 11 | 11.4 | SR/MPLS control plane..... | 80 | -| 12 | 11.4.1 | Interior Gateway Protocol (IGP) for SR/MPLS..... | 80 | -| 13 | 11.4.2 | SR/MPLS Traffic Engineering ..... | 84 | -| 14 | 11.5 | Scaling the MPLS infrastructure..... | 85 | -| 15 | 11.5.1 | Seamless MPLS architecture..... | 85 | -| 16 | 11.5.2 | Controller based network scaling architectures ..... | 88 | -| 17 | 11.6 | MPLS Quality of Service ..... | 94 | -| 18 | 11.7 | MPLS OAM ..... | 94 | -| 19 | 11.8 | IP/MPLS service infrastructure..... | 94 | -| 20 | 12 | Packet-switched underlay network – SRv6 based ..... | 94 | -| 21 | 12.1 | SRv6 data plane ..... | 95 | -| 22 | 12.2 | SRv6 control plane..... | 95 | -| 23 | 12.2.1 | Interior Gateway Protocol (IGP) for SRv6..... | 96 | -| 24 | 12.2.2 | SRv6 Traffic Engineering ..... | 100 | -| 25 | 12.2.3 | Inter-domain connectivity ..... | 101 | -| 26 | 12.3 | Scaling an SRv6 underlay infrastructure ..... | 102 | -| 27 | 12.3.1 | Route summarization and redistribution ..... | 102 | -| 28 | 12.3.2 | Controller based scaling..... | 104 | -| 29 | 12.3.3 | SRv6 scaling conclusion ..... | 105 | -| 30 | 12.4 | IPv6 Quality of Service ..... | 105 | -| 31 | 12.5 | SRv6 OAM..... | 105 | -| 32 | 12.5.1 | Ping / Traceroute to a remote IPv6 network address..... | 105 | -| 33 | 12.5.2 | Ping / Traceroute to remote SID functions..... | 106 | -| 34 | 12.6 | SRv6 Service infrastructure..... | 106 | -| 35 | 13 | Packet-switched Xhaul services Infrastructure..... | 107 | -| 36 | 13.1 | MP-BGP design..... | 107 | -| 37 | 13.2 | Ethernet services ..... | 107 | -| 38 | 13.2.1 | Ethernet services redundancy ..... | 108 | -| 39 | 13.3 | IP Services..... | 113 | -| 40 | 13.3.1 | Building flexible L3VPN service topologies..... | 113 | -| 41 | 13.3.2 | Constraints based Traffic Steering in L3VPNs..... | 113 | -| 42 | 14 | Quality of Service in packet-switched networks ..... | 114 | -| 43 | 14.1 | Xhaul transport core interface QoS..... | 114 | -| 44 | 14.1.1 | Transport network core interface classification..... | 115 | -| 45 | 14.1.2 | Core interface queue structure..... | 115 | -| 46 | 14.1.3 | Transport network core interface marking structure ..... | 117 | -| 47 | 14.1.4 | Core interface scheduling model ..... | 117 | -| 48 | 14.2 | Xhaul transport network edge interface QoS..... | 118 | -| 49 | 14.2.1 | Transport network domain PE ingress classification of Ethernet frames. .... | 118 | -| 50 | 14.2.2 | Transport domain PE ingress classification IP packets. .... | 120 | -| 51 | 14.2.3 | Admission control..... | 121 | -| 52 | 14.2.4 | PE Egress scheduling..... | 121 | -| 53 | 15 | Multicast..... | 121 | -| 54 | 15.1 | Multicast use cases..... | 121 | -| 55 | 15.1.1 | Multicast transport for fixed line services..... | 122 | -| 56 | 15.1.2 | MBMS/5MBS transport..... | 122 | - -![O-RAN ALLIANCE logo](afe5eb459b7c9cfe880b067777d876d8_img.jpg) - -O-RAN ALLIANCE logo - -| | | | | -|----|--------|----------------------------------------------------------------------------------------------|-----| -| 1 | 15.2 | Overlay and underlay multicast ..... | 123 | -| 2 | 15.3 | Recommendation/considerations for multicast solutions..... | 123 | -| 3 | 16 | Packet-switched orchestration and telemetry ..... | 124 | -| 4 | 17 | Packet Switched TNE Security..... | 124 | -| 5 | 17.1 | TNE physical security ..... | 124 | -| 6 | 17.1.1 | Console Port..... | 125 | -| 7 | 17.1.2 | Auxiliary Port..... | 125 | -| 8 | 17.1.3 | USB Port..... | 125 | -| 9 | 17.1.4 | Front Panel functions ..... | 126 | -| 10 | 17.1.5 | TNE software security ..... | 126 | -| 11 | 17.1.6 | Zero Touch Provisioning..... | 126 | -| 12 | 17.1.7 | PXE boot over management or data ports ..... | 127 | -| 13 | 17.2 | TNE user access security..... | 127 | -| 14 | 17.2.1 | TACACS+ Authentication ..... | 127 | -| 15 | 17.2.2 | Login Message ..... | 128 | -| 16 | 17.2.3 | Security Protocols..... | 129 | -| 17 | 17.2.4 | Password requirements ..... | 129 | -| 18 | 17.2.5 | Device lockout..... | 129 | -| 19 | 17.3 | Transport Network control plane security ..... | 129 | -| 20 | 17.3.1 | Control plane DoS/DDoS protection ..... | 129 | -| 21 | 17.3.2 | Control plane protocols protection..... | 130 | -| 22 | 17.4 | Port-based network access control (IEEE 802.1X-2020) ..... | 132 | -| 23 | 17.4.1 | Certificate time validation..... | 134 | -| 24 | 17.4.2 | Certificate management for TNEs providing Open Fronthaul transport ..... | 135 | -| 25 | 18 | 5G Slicing in a packet switched Xhaul network..... | 137 | -| 26 | 18.1 | Packet-switched underlay network..... | 140 | -| 27 | 18.1.1 | Underlay transport plane ..... | 140 | -| 28 | 18.1.2 | Single transport plane for all slices..... | 140 | -| 29 | 18.1.3 | Transport plane per 5G service type ..... | 140 | -| 30 | 18.1.4 | Transport plane per slice customer ..... | 141 | -| 31 | 18.1.5 | Transport plane per 5QI group (5QI-aware mapping)..... | 142 | -| 32 | 18.2 | Quality of Service ..... | 143 | -| 33 | 18.2.1 | Edge QoS ..... | 143 | -| 34 | 18.2.2 | Core QoS..... | 143 | -| 35 | 18.3 | 5G Services and slices..... | 145 | -| 36 | 19 | Energy efficiency in the context of Xhaul Packet Switched Transport Network Equipments ..... | 145 | -| 37 | 19.1 | Architecture level..... | 145 | -| 38 | 19.2 | Transport Network (TN) level ..... | 146 | -| 39 | 19.3 | Transport Network Equipment (TNE) level ..... | 146 | -| 40 | 19.3.1 | TNE hardware design ..... | 147 | -| 41 | 19.3.2 | SerDes energy optimization ..... | 150 | -| 42 | 19.3.3 | PHY energy optimization..... | 151 | -| 43 | 19.3.4 | PFE energy optimization..... | 151 | -| 44 | 19.3.5 | Line card energy optimization..... | 154 | -| 45 | 19.3.6 | Switching fabric energy optimization ..... | 154 | -| 46 | 20 | Supporting mobile scenarios on a packet switched Xhaul network..... | 156 | -| 47 | 20.1 | Physical network..... | 157 | -| 48 | 20.2 | Logical underlay architecture ..... | 158 | -| 49 | 20.2.1 | Underlay Quality of Service (QoS)..... | 159 | -| 50 | 20.3 | Service architecture..... | 160 | -| 51 | 20.3.1 | Automated VPN Traffic Steering ..... | 160 | -| 52 | 20.4 | Mobile services..... | 160 | -| 53 | 20.4.1 | Open Fronthaul..... | 160 | -| 54 | 20.4.2 | Non O-RAN Fronthaul..... | 163 | -| 55 | 20.4.3 | D2 ..... | 163 | -| 56 | 20.4.4 | Midhaul and Backhaul ..... | 164 | - -![O-RAN Alliance logo](9ebd85380ef496499e5f23ec0d9cd744_img.jpg) - -O-RAN Alliance logo - -| | | | | -|----|--------|---------------------------------------------------------------------------------------|-----| -| 1 | 20.5 | Scenario 1 and 5..... | 166 | -| 2 | 20.6 | Scenario 2..... | 168 | -| 3 | 20.7 | Scenario 3 5G C-RAN with legacy D-RAN..... | 169 | -| 4 | 20.7.1 | Scenario 3a..... | 169 | -| 5 | 20.7.2 | Scenario 3b..... | 169 | -| 6 | 20.8 | Scenario 4 5G C-RAN with RoE mappers ..... | 170 | -| 7 | 20.9 | Scenario 6 5G C-RAN with distributed UPF..... | 171 | -| 8 | 20.10 | Scenario 7 Slicing ..... | 171 | -| 9 | 21 | Applicability of IETF Computing-Aware Traffic Steering (CATS) to O-RAN Scenarios..... | 172 | -| 10 | 21.1 | Introduction ..... | 172 | -| 11 | 21.2 | Overview of the CATS Framework ..... | 172 | -| 12 | 21.2.1 | Introduction to CATS ..... | 172 | -| 13 | 21.2.2 | Key components of CATS ..... | 172 | -| 14 | 21.2.3 | Architectural planes ..... | 173 | -| 15 | 21.3 | Insights on CATS Metric Creation for Steering Decisions..... | 173 | -| 16 | 21.3.1 | Importance of metrics ..... | 173 | -| 17 | 21.3.2 | Metric Levels and Types..... | 173 | -| 18 | 21.3.3 | Metric Fields and Representation ..... | 174 | -| 19 | 21.3.4 | Metric Distribution and Update Frequency ..... | 174 | -| 20 | 21.4 | Applicability of CATS to Midhaul..... | 174 | -| 21 | 21.4.1 | O-RAN Midhaul overview..... | 174 | -| 22 | 21.4.2 | Dynamic Association of DU and CU..... | 174 | -| 23 | 21.4.3 | Role of CATS in Midhaul ..... | 174 | -| 24 | 21.4.4 | CATS components in Midhaul context..... | 175 | -| 25 | 21.4.5 | Connectivity Realization..... | 175 | -| 26 | 21.5 | Applicability of CATS to D2 interface..... | 175 | -| 27 | 21.6 | Interaction Between O-RAN Components and IETF CATS Components ..... | 175 | -| 28 | 21.6.1 | Mapping CATS Components to O-RAN ..... | 175 | -| 29 | 21.6.2 | Control Plane Interactions..... | 176 | -| 30 | 21.6.3 | Integration with IETF Network Slice Service ..... | 176 | -| 31 | 22 | Annex A: Overview of “Segment Routing” (SR)..... | 176 | -| 32 | | Background..... | 176 | -| 33 | | Segment Routing..... | 176 | -| 34 | | Segment Routing architectural principle ..... | 177 | -| 35 | | Segment Routing data plane ..... | 178 | -| 36 | | Segment Routing control plane..... | 180 | -| 37 | 23 | Annex B: IETF Ethernet Virtual Private Networks ..... | 182 | -| 38 | 24 | Annex C: MP-BGP based L3VPNs ..... | 188 | -| 39 | | Building blocks of a L3 VPN service..... | 188 | -| 40 | | Traffic Steering into an BGP VPN..... | 190 | -| 41 | 25 | Annex D: Quality of Service ..... | 191 | -| 42 | | What is Quality of Service? ..... | 191 | -| 43 | | Why do we need QoS? ..... | 192 | -| 44 | | QoS functional elements..... | 192 | -| 45 | | Network level behaviour ..... | 193 | -| 46 | | Node level behaviour ..... | 193 | -| 47 | | Traffic classification and marking..... | 194 | -| 48 | | Congestion management..... | 196 | -| 49 | | Congestion avoidance..... | 199 | -| 50 | 26 | Annex E: Multicast Technologies background..... | 204 | -| 51 | | Overlay multicast ..... | 204 | -| 52 | | PIM-based overlay signalling for IPVPN ..... | 204 | -| 53 | | BGP-based overlay signalling for IPVPN and EVPN ..... | 204 | -| 54 | | Underlay multicast ..... | 205 | -| 55 | | MVPN/EVPN and Seamless MPLS/SR ..... | 206 | - -![O-RAN Alliance logo](892f25e3d71d8e315a2a51092a8a8da7_img.jpg) - -O-RAN Alliance logo - -| | | | | -|----|----|-----------------------------------------------------------------------------------|-----| -| 1 | 27 | Annex F: Transport network slicing solution for WG1 Slicing (informational) ..... | 207 | -| 2 | | WG-1 Phase 1 scope ..... | 207 | -| 3 | | WG-1 Phase 2 scope ..... | 209 | -| 4 | | WG-1 Phase 3 scope ..... | 211 | -| 5 | | Overall Packet Switched Transport Architecture ..... | 212 | -| 6 | | Underlay network for WG-1 slicing phase 1, 2 and 3 ..... | 213 | -| 7 | | Service Models for WG-1 slicing phase 1, 2 and 3 ..... | 214 | -| 8 | | Transport and DC management networks..... | 214 | -| 9 | | Transport network management network ..... | 215 | -| 10 | | Data Centre (DC) management network..... | 215 | -| 11 | | O-RAN control and management networks..... | 216 | -| 12 | | O-RAN Fronthaul Management network (M-Plane)..... | 216 | -| 13 | | O-RAN Control and Management network (A1, E2, O1 interfaces)..... | 217 | -| 14 | | 3GPP Control Plane network ..... | 217 | -| 15 | | O-RAN and 3GPP user planes networks ..... | 218 | -| 16 | | Slicing Phase 1 ..... | 218 | -| 17 | | Slicing phase 2 and 3 ..... | 219 | -| 18 | | Fronthaul C/U plane network..... | 219 | -| 19 | | Midhaul user plane network (F1-U and Xn-U)..... | 220 | -| 20 | | Backhaul user plane network (N3 and N9)..... | 221 | -| 21 | | Data Network (N6)..... | 224 | -| 22 | | Transport Network Quality of Service architecture..... | 224 | -| 23 | | Transport QoS considerations in a 5G environment..... | 225 | -| 24 | | 3GPP QoS flows and Transport QoS ..... | 226 | -| 25 | | Transport QoS Architecture for O-RAN slicing phase 1, 2 and 3 ..... | 228 | -| 26 | | | | -| 27 | | | | -| 28 | | | | - -![O-RAN Alliance logo](d4e9f8f6bf5d7853ecae9c9633900af1_img.jpg) - -The O-RAN Alliance logo, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -## 3 Scope - -### 3.1 Overview - -This Technical Specification has been produced by the O-RAN Alliance. The document is intended to describe best practices for O-RAN Transport Network (TN) based on end-to-end packet switching technology. It is recognized that other solutions, not based on packet switching, could be employed or mixed with a packet switching solution. Beyond the solutions described in this document, other packet switching solutions may be adequate for TN and can be considered in future versions of this document. - -In the context of 3GPP, the TN is referred as a non 3GPP-managed domain that supports connectivity within and between RAN and Core Network CN (refer to TS 28.530 [13]). Therefore, the TN consolidates the RAN infrastructure by bridging the O-RAN functional split: - -- between RAN components (e.g. Network Functions) -- between RAN components and External Systems (e.g. Core Network) - -However, in the context of O-RAN, the O-Cloud can manage certain aspects of RAN connectivity through to the IMS (for more information refer to WG6 CADS document [14]). This alters the traditional definition of the TN, as certain connectivity aspects are no longer within its scope. - -Hence, given this shift, we define the TN in O-RAN based on domain and management boundaries, explicitly excluding O-Cloud-managed connectivity. Figure 3.1 presents examples of the interplay between O-CLOUD and TN management domains in RAN connectivity: - -- The TN is not involved in connectivity between O-DU and O-CU from site A. This is handled within the O-CLOUD. -- The TN is partially involved in connectivity between O-DU site B and O-CU site A, the portion of the connectivity within site A is managed by the O-CLOUD. -- The TN provides full connectivity between the O-RU and the physical O-DU of site C since it is not part of any O-CLOUD. -- The TN provides connectivity to the 5GC in an external site. The external site may physically match an O-RAN site, however it is considered logically external since it pertains to a non O-RAN managed domain. - -![O-RAN Alliance logo](625e10f48104ba2b06b2220a9b224712_img.jpg) - -O-RAN Alliance logo - -![Figure 3-1: Scope of the Transport Network in O-RAN. The diagram shows a central 'TRANSPORT NETWORK' cloud connected to three O-RAN sites: Site A, Site B, and Site C. Site A contains O-DU, O-CU, and O-CLOUD NETWORKING. Site B contains O-DU. Site C contains O-DU physical and O-RU. All sites are connected to the central transport network cloud. An 'External Site' containing 5GC is also connected to the transport network. The entire area is enclosed in a large orange box labeled 'O-CLOUD'.](cfda9df1319e04207eb28bcefd1dab7b_img.jpg) - -Figure 3-1: Scope of the Transport Network in O-RAN. The diagram shows a central 'TRANSPORT NETWORK' cloud connected to three O-RAN sites: Site A, Site B, and Site C. Site A contains O-DU, O-CU, and O-CLOUD NETWORKING. Site B contains O-DU. Site C contains O-DU physical and O-RU. All sites are connected to the central transport network cloud. An 'External Site' containing 5GC is also connected to the transport network. The entire area is enclosed in a large orange box labeled 'O-CLOUD'. - -Figure 3-1: Scope of the Transport Network in O-RAN - -The TN includes Fronthaul, Midhaul, or Backhaul network (Figure 3-2). For the definitions of Fronthaul and Midhaul, authors refer to Open Fronthaul Working Group (WG4) CUS specification [18]. Backhaul is defined as the TN infrastructure that interconnects the RAN and the Core Network. This document uses the term Xhaul to indicate Fronthaul, Midhaul or Backhaul. - -![Figure 3-2: TN decomposition applicable in O-RAN. The diagram shows a sequence of components connected in a line: O-RU (connected via eCPRI 7-2x) -> Fronthaul (F2) cloud -> O-DU -> Midhaul (F1) cloud -> O-CU -> Backhaul (N2, N3) cloud -> 5GC cloud. A legend below shows a cloud icon labeled 'Transport Network'.](b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg) - -Figure 3-2: TN decomposition applicable in O-RAN. The diagram shows a sequence of components connected in a line: O-RU (connected via eCPRI 7-2x) -> Fronthaul (F2) cloud -> O-DU -> Midhaul (F1) cloud -> O-CU -> Backhaul (N2, N3) cloud -> 5GC cloud. A legend below shows a cloud icon labeled 'Transport Network'. - -**(F2, F1, N2, N3)** 3GPP interfaces depicted for reference. For more information refer to 3GPP specifications TS 38.401 and TS 23.501 - -Figure 3-2: TN decomposition applicable in O-RAN - -This specification defines an architecture for an Open Xhaul transport network based on an end-to-end packet switching architecture that utilizes statistical multiplexing and a hierarchy of packet switching “Transport Node Equipment” (TNE) starting at the cell site in the access layer and going to the core layer of the transport network capable of supporting the requirements outlined in the O-RAN WG9 Transport Requirements document [20]. - -Within the Xhaul transport network it is assumed that the L0/L1 transport technology connecting the packet switches are high capacity, low delay Ethernet point to point circuits. These circuits can be - -![O-RAN Alliance logo](d336e7ffee4f537d0805ca840ec28582_img.jpg) - -O-RAN Alliance logo - -1 derived from dark fibre, WDM or other technologies capable of presenting Ethernet. These L0/L1 - 2 technologies are clearly very important but out of scope of this document. - -3 - 4 To allow the operators to offer the most flexibility in designing their RAN infrastructure the Xhaul - 5 transport network should utilize the same design paradigm as the transport core, aggregation and pre- - 6 aggregation. However, in some instances this may not be an option, so this document identifies other - 7 potential access technologies, provides a description and considerations/trade-offs for their usage. - -8 - 9 WG9 sub-teams are working on several solution documents. This document focuses on packet- - 10 based transport technologies. It also includes sections on some of the technologies used in physical - 11 network such as PON, DOCSIS® networks and wireless Xhaul. WDM in the access network - 12 providing Fronthaul services is covered in a different document [21]. - -13 - 14 This document does not cover: - -- 15 - 16 1. Timing and synchronization –Another O-RAN WG-9 effort is underway. [22] -- 17 2. WDM in access for Fronthaul services -Another O-RAN WG-9 effort is underway[21]. -- 18 3. Highly specialized URLLC, for example motion control in an industrial setting. I.e., private - 19 network, tightly constrained, requiring TSN in the Backhaul and RAN looking like a TSN - 20 bridge. This can be covered in a later edition. -- 21 4. OTN or SPN/G.mtn as a transport layer. - -## 22 3.2 Version History - -23 - 24 Version 1 of this document covers: - -- 25 - 26 1. High level transport requirements -- 27 2. 5G-Fronthaul, Midhaul, Backhaul transport requirement -- 28 3. 5G-Operator use cases - -29 - 30 The document then considers packet infrastructure and how the packet infrastructure can support the - 31 identified requirements and use cases. It describes a packet architecture consisting of an underlay - 32 packet switching infrastructure which supports L2 and L3 services. - -33 - 34 The document covers two potential underlay solutions; MPLS based or SRv6 based. In both cases the - service infrastructure consists of MP-BGP VPN solutions supporting L2 and L3 services. - -35 - 36 The last part of the document outlines, using examples, how the packet switching infrastructure can - 37 support the operator use cases outlined earlier in the document. - -38 - 39 Version 3 builds on the MPLS and SRv6 functionality described in Version 1 and 2 and outlines a - 40 transport slicing solution capable of supporting phase 1 and 2 of WG-1 slicing architecture [25]. This - 41 is primarily covered in an informational annex (Annex F: Transport network slicing solution for WG1 - 42 Slicing (informational)). - -43 - 44 This document uses information and requirements published by O-RAN, 3GPP, IEEE, ITU-T, - 45 IETF, CableLabs, NGMN, MEF, BBF and many other standard bodies and industry associations. - -46 - Version 4 brings following updates/enhancements to the document: - -![O-RAN Alliance logo](ec0158057f8ccaf74edba16682ec5444_img.jpg) - -The O-RAN Alliance logo, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -- 1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15 -- Section 9.4 provides more clarification, which IETF work can be referenced in this document - - in Section 11.5.1 evolution of Seamless MPLS architecture, with colored underlay transport, is added. - - major update to Section 17 provides details about desired TNE security, including physical security, user access security, transport network control plane security, and port-based access control. - - Section 18 is enhanced with additional mapping option for service slice to underlay transport plane mapping, as well has enhanced in general to provide more details about each mapping method. - - Small changes to Annex F are added to align with slicing phase 3 as described in O-RAN.WG1.Slicing-Architecture [25] - - Annex ZZZ (O-RAN Adopter License Agreement) is removed, as it is no longer needed - -16 -17 -18 -19 - -Version 5 brings small update to Section 17.4: Port-based network access control (IEEE 802.1X-2020), adding some discussion about the TNE-to-TNE authentication methods, as well as describing the behavior when a certificate expires. - -20 -21 -22 - -Version 6 brings small updates to Section 10 (reference to CTI documents updated), as well as additions in Annex F related to the description of network slicing phase 4 in midhaul. - -23 -24 -25 -26 - -Version 7 brings update to Section 17.4, adding discussion about operator-signed certification management for TNEs providing Open Fronthaul transport connectivity. Annex F is slightly enhanced to reference relevant IETF TEAS WG 5G transport slicing draft. - -27 -28 -29 -30 -31 - -Version 8 brings enhancement to Section 17.2: “TNE user access security”, by addition a new subsection 17.2.3: “Security Protocols”. Version 8 also introduces new section, which discusses energy efficiency aspects of the transport network (Section 19: “Energy efficiency in the context of Xhaul Packet Switched Transport Network Equipments”) - -32 -33 - -Version 9 clarify the scope of the TN as well as the Terminology (TNE, Attachment circuit etc.). - -34 -35 -36 - -Version 10 brings new content: D2 interface (sections 7.3, 8.8, 8.9, 20.4.3) and Computing-Aware Traffic Steering (Section 21). - -![O-RAN Alliance logo](5f8af0cfcf796986f40e70571bb950f5_img.jpg) - -The O-RAN Alliance logo, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -## 4 References - -The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - -- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. -- For a specific reference, subsequent revisions do not apply. -- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in Release 17. - -### 3GPP references - -- [1] 3GPP TS 23.501 V17.10.0: "System Architecture for 5G System (5GS)" -- [2] 3GPP TS 23.203 V17.2.0: "Policy Control and Charging Architecture" -- [3] 3GPP TS 28.316 V17.0.0: "Management and orchestration; Plug and Connect; Data formats" -- [4] 3GPP TS 29.060 V17.4.0: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface" -- [5] 3GPP TS 29.274 V17.9.0: "3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3" -- [6] 3GPP TS 29.281 v17.4.0: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)" -- [7] 3GPP TS 32.509 V16.0.0.: "Telecommunication management; Data formats for multi-vendor plug and play eNode B connection to the network" -- [8] 3GPP TS 33.310 V17.7.0: "Network Domain Security (NDS); Authentication Framework (AF)" -- [9] 3GPP TS 36.422 V17.1.0: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 signalling transport" -- [10] 3GPP TS 36.424 v17.0.0: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 data transport" -- [11] 3GPP TS 38.306 V17.6.0: "NR; User equipment (UE) radio access capabilities" -- [12] 3GPP TS 38.401 V17.6.0: "NG-RAN; Architecture description" -- [13] 3GPP TS 38.415 V17.0.0: "NG-RAN; PDU Session User Plane Protocol" -- [14] 3GPP TS 38.422 V17.1.0: "NG-RAN; Xn signalling transport" -- [15] 3GPP TS 38.462 V17.0.0: "NG RAN; E1 signalling transport" -- [16] 3GPP TS 38.474 V17.0.0: "NG-RAN; F1 data transport". -- [17] 3GPP TS 28.530 V18.1.0: "Management and orchestration; Concepts, use cases and requirements" - -### O-RAN references - -- [18] O-RAN.WG4.CUS.0-v09.00 "Open Fronthaul Control, User and Synchronization Plane Specification Version v09.00", August 2022 -- [19] O-RAN.WG4.MP.0-v09.00: "Open Fronthaul Management Plane Specification v09.00", April 2022 - -![O-RAN ALLIANCE logo](78f163db583eb0c6d013e6f8ffe6d7d8_img.jpg) - -O-RAN ALLIANCE logo - -- 1 [20] O-RAN.WG9.XTRP-REQ-v01.00 “Xhaul Transport Requirements v01.00”, -2 November 2020 -- 3 [21] O-RAN.WG9.WDM.0-v02.00 “WDM-based Fronthaul Transport v02.00”, -4 November 2021 -- 5 [22] O-RAN.WG9.XTRP-SYN.0-v03.00 “Synchronization Architecture and -6 Solution Specification v03.00”, July 2022 -- 7 [23] O-RAN.WG9.XTRP-MGT.0-v04.00 “Management interfaces for Transport -8 Network Elements v04.00”, July 2022 -- 9 [24] O-RAN.WG4.CTI-TCP.0-R003-v04.00, “Cooperative Transport Interface -10 Transport Control Plane Specification v04.00”, April 2023 -11 -- 12 [25] O-RAN.WG4.CTI-TMP.0-R003-v04.00, “Cooperative Transport Interface -13 Transport Management Procedures Specification v04.00”, April 2023 -14 -- 15 [26] O-RAN.WG1.Slicing Architecture-v07.00, April 2022 -- 16 -- 17 [27] O-RAN.WG11.Security-Requirements-Specifications-v04, November 2022 -18 -- 19 [28] MITRE-12-05-2022-WG1-CR-0001-UseCaseAnalysisReport-RAN-Sharing- -20 Via-Midhaul-v09, May 2022 -21 -- 22 [29] O-RAN ALLIANCE TS: "O-RAN Security Protocols Specification" -23 -- 24 [30] O-RAN.WG6.CADS-v08 - “O-RAN Working Group 6 - Cloud Architecture and -25 Deployment Scenarios for O-RAN Virtualized RAN” -26 -- 27 [31] O-RAN.WG1.TS.OAD: "O-RAN Architecture Description" -28 -- 29 [32] ORAN-WG9.XPSAAS.0-R005-v10.00: "D2 Interface: General Aspects and -30 Principles" -31 -32 -33 -- 34 **IEEE references** -- 35 [33] IEEE 802.3-2018: “IEEE Standard for Ethernet” -- 36 [34] IEEE 802.1Q-2018: “IEEE Standard for Local and metropolitan area -37 networks— Bridges and Bridged Networks” -- 38 [35] IEEE 802.1CM-2018: “Time-Sensitive Networking for Fronthaul” -- 39 [36] IEEE Std 1914.1TM-2019: “IEEE Standard for Packet-based Fronthaul -40 Transport Network” -- 41 [37] IEEE 802.3av “Physical Layer Specifications and Management Parameters for -42 10 Gb/s Passive Optical Networks” -- 43 [38] IEEE 802.3bk “Physical Layer Specifications and Management Parameters for -44 Extended Ethernet Passive Optical Networks” -- 45 [39] IEEE 802.3ca “Physical Layer Specifications and Management Parameters for -46 25 Gb/s and 50 Gb/s Passive Optical Networks” - -![O-RAN ALLIANCE logo](589af9a5d6f5bbbdc8f482e364688676_img.jpg) - -O-RAN ALLIANCE logo - -| | | | -|----|------------------------|---------------------------------------------------------------------------------------------------------------------------| -| 1 | [40] | IEEE Std 1914.3-2018 – IEEE standard for radio over Ethernet Encapsulations and Mappings | -| 2 | | | -| 3 | [41] | IEEE Std 802.1X-2020 “IEEE Standard for Local and Metropolitan Area Networks--Port-Based Network Access Control” | -| 4 | | | -| 5 | | | -| 6 | IETF references | | -| 7 | [42] | IETF RFC 791: “INTERNET PROTOCOL” | -| 8 | [43] | IETF RFC 768: “User Datagram Protocol” | -| 9 | [44] | IETF RFC 1195: “Use of OSI IS-IS for routing in TCP/IP and dual environments” | -| 10 | | | -| 11 | [45] | IETF RFC 1771: “A Border Gateway Protocol 4” | -| 12 | [46] | IETF RFC 2205: “Resource ReSerVation Protocol” | -| 13 | [47] | IETF RFC 2209: “Resource ReSerVation Protocol (RSVP) --Version 1 Message Processing Rules” | -| 14 | | | -| 15 | [48] | IETF RFC 2210: “The use of RSVP with IETF Integrated Services” | -| 16 | [49] | IETF RFC 2328: “OSPF Version 2” | -| 17 | [50] | IETF RFC 2475: “An Architecture for Differentiated Services” | -| 18 | [51] | IETF RFC 2474: “Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers” | -| 19 | | | -| 20 | [52] | IETF RFC 2545: Use of BGP-4 Multiprotocol Extensions for IPv6 Inter-Domain Routing” | -| 21 | | | -| 22 | [53] | IETF RFC 2597: “Assured Forwarding PHB Group” | -| 23 | [54] | IETF RFC 2598: “An Expedited Forwarding PHB” | -| 24 | [55] | IETF RFC 2745: “RSVP Diagnostic Messages” | -| 25 | [56] | IETF RFC 2747: “RSVP Cryptographic Authentication” | -| 26 | [57] | IETF RFC 2858: “Multiprotocol Extensions for BGP-4” | -| 27 | [58] | IETF RFC 2865: “Remote Authentication Dial In User Service (RADIUS)” | -| 28 | [59] | IETF RFC 2866: “RADIUS Accounting” | -| 29 | [60] | IETF RFC 2961: “RSVP Refresh Overhead Reduction Extensions” | -| 30 | [61] | IETF RFC 2983: “Differentiated Services and Tunnels” | -| 31 | [62] | IETF RFC 3031: “Multiprotocol Label Switching Architecture” | -| 32 | [63] | IETF RFC 3032: “MPLS Label Stack Encoding” | -| 33 | [64] | IETF RFC 3097: “RSVP Cryptographic Authentication—Updated Message Type Value” | -| 34 | | | -| 35 | [65] | IETF RFC 3107: “Carry Label Information in BGP-4” | -| 36 | [66] | IETF RFC 3209: “Extensions to RSVP for LSP Tunnels” | -| 37 | [67] | IETF RFC 3212: “Constraint-Based LSP Setup using LDP” | -| 38 | [68] | IETF RFC 3215: “LDP State Machine” | -| 39 | [69] | IETF RFC 3246: “An Expedited Forwarding PHB (Per-Hop Behavior)” | -| 40 | [70] | IETF RFC 3443: “Time To Live (TTL) Processing in Multi-Protocol Label Switching (MPLS) Networks” | -| 41 | | | -| 42 | [71] | IETF RFC 3477: “Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)” | -| 43 | | | -| 44 | [72] | IETF RFC 3478: “Graceful Restart Mechanism for Label Distribution Protocol” | -| 45 | [73] | IETF RFC 3579: “RADIUS (Remote Authentication Dial In User Service) Support For Extensible Authentication Protocol (EAP)” | -| 46 | | | -| 47 | [74] | IETF RFC 3630: “Traffic Engineering (TE) Extensions to OSPF Version 2” | -| 48 | [75] | IETF RFC 3719: “Recommendations for Interoperability using ISIS” | - -![O-RAN ALLIANCE logo](662933fe00899933b36b5a214ac6095c_img.jpg) - -O-RAN ALLIANCE logo - -| | | | -|----|-------|---------------------------------------------------------------------------------------------------------------------------------------| -| 1 | [76] | IETF RFC 4072: “Diameter Extensible Authentication Protocol (EAP) Application” | -| 2 | | | -| 3 | [77] | IETF RFC 4090: “Fast Reroute Extensions to RSVP-TE for LSP Tunnels” | -| 4 | [78] | IETF RFC 4115: “A Differentiated Service Two-Rate, Three-color Marker with Efficient Handling of in-Profile Traffic” | -| 5 | | | -| 6 | [79] | IETF RFC 4182: “Removing a Restriction on the use of MPLS Explicit NULL” | -| 7 | [80] | IETF RFC 4210: “Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP)” | -| 8 | | | -| 9 | [81] | IETF RFC 4271: “A Border Gateway Protocol 4 (BGP-4)” | -| 10 | [82] | IETF RFC 4303: “OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)” | -| 11 | | | -| 12 | [83] | IETF RFC 4206: Label Switched Paths (LSP) Hierarchy with Generalized Multi-Protocol Label Switching (GMPLS) Traffic Engineering (TE)” | -| 13 | | | -| 14 | [84] | IETF RFC 4252: “The Secure Shell (SSH) Authentication Protocol” | -| 15 | [85] | IETF RFC 4443: “ICMPv6 (ICMP for IPv6)” | -| 16 | [86] | IETF RFC 4552: “Authentication/Confidentiality for OSPFv3” | -| 17 | [87] | IETF RFC 4558: “Node-ID Based Resource Reservation Protocol (RSVP) Hello” | -| 18 | | | -| 19 | [88] | IETF RFC 4561: “Record Route Object (RRO) Node-Id Sub-Object” | -| 20 | [89] | IETF RFC 4594: “Configuration Guidelines for DiffServ Service Classes” | -| 21 | [90] | IETF RFC 4364: “BGP/MPLS IP Virtual Private Networks (VPNs)” | -| 22 | [91] | IETF RFC 4684: “Constrained Route Distribution for BGP/MPLS IP VPNs” | -| 23 | | Computation Element Protocol (PCEP)” | -| 24 | [92] | IETF RFC 4760: “Multiprotocol Extensions for BGP-4” | -| 25 | [93] | IETF RFC 4875: “Extensions to Resource Reservation Protocol – Traffic Engineering for Point to Multipoint TE Label Switched Paths” | -| 26 | | | -| 27 | [94] | IETF RFC 5036: “LDP Specification” | -| 28 | [95] | IETF RFC 5130: “A Policy Control Mechanism in IS-IS Using Administrative Tags” | -| 29 | | | -| 30 | [96] | IETF RFC 5216: “The EAP-TLS Authentication Protocol” | -| 31 | [97] | IETF RFC 5246: “The Transport Layer Security (TLS) Protocol Version 1.2” | -| 32 | [98] | IETF RFC 5283: “LDP Extension for Inter-Area Label Switched Paths (LSPs)” | -| 33 | [99] | IETF RFC 5291: “Outbound Route Filtering Capability for BGP-4” | -| 34 | [100] | IETF RFC 5292 “Address-Prefix-Based Outbound Route Filter for BGP-4” | -| 35 | [101] | IETF RFC 5302 “Domain-Wide Prefix Distribution with Two-Level IS-IS” | -| 36 | [102] | IETF RFC 5303: “Three-Way Handshake for IS-IS Point-to-Point Adjacencies” | -| 37 | [103] | IETF RFC 5305: “IS-IS Extensions for Traffic Engineering” | -| 38 | [104] | IETF RFC 5308: “Routing IPv6 with ISIS” | -| 39 | [105] | IETF RFC 5310: “IS-IS Generic Crypto Authentication” | -| 40 | [106] | IETF RFC 5329: “Traffic Engineering Extensions to OSPF Version 3” | -| 41 | [107] | IETF RFC 5340: “OSPF for IPv6” | -| 42 | [108] | IETF RFC 5420: “Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE)” | -| 43 | | | -| 44 | [109] | IETF RFC 5440: “Path Computational Element (PCE) Communications Protocol (PCEP)” | -| 45 | | | -| 46 | [110] | IETF RFC 5443: “LDP IGP Synchronization” | -| 47 | [111] | IETF RFC 5496: “The Reverse Path Forwarding (RPF) Vector TLV” | -| 48 | [112] | IETF RFC 5512: “The BGP Encapsulation Subsequent Address Family Identifier (SAFI) and the BGP Tunnel Encapsulation Attribute” | -| 49 | | | - -![O-RAN ALLIANCE logo](7b1cea8c45c49887a750926f2135fa84_img.jpg) - -O-RAN ALLIANCE logo - -| | | | -|----|-------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 1 | [113] | IETF RFC 5561: “LDP capabilities” | -| 2 | [114] | IETF RFC 5838: “Support of Address Families in OSPFv3” | -| 3 | [115] | IETF RFC 5925: “The TCP Authentication Option” | -| 4 | [116] | IETF RFC 5926: “Cryptographic Algorithms for the TCP Authentication Option (TCP-AO)” | -| 5 | | | -| 6 | [117] | IETF RFC 6232: “Purge Originator Identification TLV for IS-IS” | -| 7 | [118] | IETF RFC 6388: “Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths” | -| 8 | | | -| 9 | [119] | IETF RFC 6391: “Flow-Aware Transport of pseudowires over an MPLS Packet Switched Network” | -| 10 | | | -| 11 | [120] | IETF RFC 6512: “Using Multipoint LDP When the Backbone has No Route to the ROOT” | -| 12 | | | -| 13 | [121] | IETF RFC 6513: “Multicast in MPLS/BGP IP VPNs” | -| 14 | [122] | IETF RFC 6514: “BGP Encodings and procedures for multicast in MPLS/BGP IP VPNs” | -| 15 | | | -| 16 | [123] | IETF RFC 7432: “BGP MPLS-Based Ethernet VPN” | -| 17 | [124] | IETF RFC 7471: “OSPF Traffic Engineering (TE) Metric Extensions” | -| 18 | [125] | IETF RFC 7524: “Inter-Area Point to Multipoint Segmented Label Switched Paths (LSPs)” | -| 19 | | | -| 20 | [126] | IETF RFC 7570: “Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)” | -| 21 | | | -| 22 | [127] | IETF RFC 7761: “Protocol Independent Multicast” | -| 23 | [128] | IETF RFC 7810: “IS-IS Traffic Engineering (TE) Metric Extensions” | -| 24 | [129] | IETF RFC 8029: “Detecting Multiprotocol Label Switched (MPLS) Data-plane Failures” | -| 25 | | | -| 26 | [130] | IETF RFC 8200: “Internet Protocol, Version 6 (IPv6) Specification” | -| 27 | [131] | IETF RFC 8214: “Virtual Private Wire Service Support in Ethernet VPN” | -| 28 | [132] | IETF RFC 8231: “Path Computational Element Communications Protocol (PCEP) Extensions for Stateful PCE” | -| 29 | | | -| 30 | [133] | IETF RFC 8277: “BGP and Labeled Address Prefixes” | -| 31 | [134] | IETF RFC 8279: “Multicast Using Bit Index Explicit Replication (BIER)” | -| 32 | [135] | IETF RFC 8287: “Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes” | -| 33 | | | -| 34 | | | -| 35 | [136] | IETF RFC 8296: “Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS Networks” | -| 36 | | | -| 37 | [137] | IETF RFC 8317: “Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN)” | -| 38 | | | -| 39 | [138] | IETF RFC 8366: “A Voucher Artifact for Bootstrapping Protocols” | -| 40 | [139] | IETF RFC 8370: “Techniques to Improve the Scalability of RSVP-TE Deployments” | -| 41 | | | -| 42 | [140] | IETF RFC 8395: “Extension to BGP-Signaled pseudowires to support flow-aware transport labels” | -| 43 | | | -| 44 | [141] | IETF RFC 8402: “Segment Routing Architecture” | -| 45 | [142] | IETF RFC 8446: “The Transport Layer Security (TLS) Protocol Version 1.3” | -| 46 | [143] | IETF RFC 8476: “Signaling Maximum SID depth using OSPF” | -| 47 | [144] | IETF RFC 8491: “Signaling Maximum SID depth using IS-IS” | -| 48 | [145] | IETF RFC 8571: “BGP – Link State (BGP-LS) Advertisement of IGP Traffic Engineering Performance Metric Extensions” | -| 49 | | | - -![O-RAN ALLIANCE logo](2150ae7f14a2e4ad1866ac0c8ec685ad_img.jpg) - -O-RAN ALLIANCE logo - -| | | | -|----|-------|----------------------------------------------------------------------------| -| 1 | [146] | IETF RFC 8572: “Secure Zero Touch Provisioning (SZTP)” | -| 2 | [147] | IETF RFC 8577: “Signaling RSVP-TE Tunnels on a Shared MPLS Forwarding | -| 3 | | Plane” | -| 4 | [148] | IETF RFC 8660: “Segment Routing with MPLS Dataplane” | -| 5 | [149] | IETF RFC 8661: “Segment Routing MPLS Interworking with LDP” | -| 6 | [150] | IETF RFC 8664: “PCEP Extensions for Segment Routing” | -| 7 | [151] | IETF RFC 8666: “OSPFv3 Extensions for Segment Routing” | -| 8 | [152] | IETF RFC 8667: “IS-IS Extensions for Segment Routing” | -| 9 | [153] | IETF RFC 8754: “IPv6 Segment Routing Header (SRH)” | -| 10 | [154] | IETF RFC 8814: “Signaling Maximum SID Depth (MSD) Using the BGP – | -| 11 | | Link State” | -| 12 | [155] | IETF RFC 8907: “The Terminal Access Controller Access-Control System Plus | -| 13 | | (TACACS+) Protocol” | -| 14 | [156] | IETF RFC 8986: “SRv6 Network Programming” | -| 15 | [157] | IETF RFC 9085: “Border Gateway Protocol - Link State (BGP-LS) Extensions | -| 16 | | for Segment Routing” | -| 17 | [158] | IETF RFC 9136: “IP prefix Advertisements in Ethernet VPN (EVPN)” | -| 18 | [159] | IETF RFC 9252: “BGP Overlay Services Based on Segment Routing over IPv6 | -| 19 | | (SRv6)” | -| 20 | [160] | IETF RFC 9256: “Segment Routing Policy Architecture” | -| 21 | [161] | IETF RFC 9259: “Operations, Administration, and Maintenance (OAM) in | -| 22 | | Segment Routing Networks over IPv6 (SRv6)” | -| 23 | [162] | IETF RFC 9350: “IGP Flexible Algorithm” | -| 24 | [163] | IETF RFC 9351: “Flexible Algorithm Definition Advertisement with BGP Link- | -| 25 | | State” | -| 26 | [164] | IETF RFC 9352: “IS-IS Extensions to support SR over IPv6 dataplane” | -| 27 | [165] | IETF RFC 9513: “OSPFv3 Extensions for Segment Routing over IPv6 (SRv6)” | -| 28 | [166] | IETF RFC 9514: “Border Gateway Protocol - Link State (BGP-LS) Extensions | -| 29 | [167] | IETF RFC 9524: “Segment Routing Replication for Multipoint Service | -| 30 | | Delivery” | -| 31 | [168] | IETF RFC 9552: “Distribution of Link-State and Traffic Engineering | -| 32 | | Information Using BGP” | -| 33 | [169] | IETF RFC 9572: “Updates to EVPN Broadcast, Unknown Unicast, or Multicast | -| 34 | | (BUM) Procedures” | -| 35 | [170] | IETF RFC 9603: “Path Computation Element Communication Protocol (PCEP) | -| 36 | | Extensions for IPv6 Segment Routing” | -| 37 | [171] | IETF RFC 9604: “Carrying Binding Label/SID in PCE-Based Networks” | -| 38 | [172] | IETF RFC 9641: “A YANG Data Model for a Truststore” | -| 39 | [173] | IETF RFC 9705: “Refresh-Interval Independent RSVP Fast Reroute Facility | -| 40 | | Protection” | -| 41 | [174] | IETF RFC 9744: “EVPN Virtual Private Wire Service (VPWS) Flexible Cross- | -| 42 | | Connect (FXC) Service” | -| 43 | [175] | IETF RFC 9785: “Preference-Based EVPN Designated Forwarder (DF) | -| 44 | | Election” | -| 45 | [176] | IETF RFC 9786: “EVPN Port-Active Redundancy Mode” | -| 46 | [177] | IETF RFC 9800: “Compressed SRv6 Segment List Encoding” | -| 47 | [178] | IETF RFC 9889: “A Realization of Network Slices for 5G Networks Using | -| 48 | | Current IP/MPLS Technologies” | - -![O-RAN ALLIANCE logo](b0d9faaee53565a4a333764297aa7b97_img.jpg) - -O-RAN ALLIANCE logo - -- 1 [179] Draft-ietf-bess-bgp-multicast-controller-16: “Controller-based BGP Multicast - 2 Signaling” -- 3 [180] Draft-ietf-cats-framework-17: “A Framework for Computing-Aware Traffic - 4 Steering CATS” -- 5 [181] Draft-ietf-cats-metric-definition-04: “CATS Metric Definition” -- 6 [182] Draft-ietf-mpls-seamless-mpls-07: “Seamless MPLS Architecture” -- 7 [183] Draft-ietf-pce-segment-routing-policy-cp-27: “PCEP extension to support - 8 Segment Routing Candidate Path for Segment Routing over IPv6 (SRv6)” -- 9 [184] Draft-ietf-pim-sr-p2mp-policy-22: “Segment Routing Point-to-Multipoint - 10 Policy” -- 11 [185] Draft-ietf-rtgwg-segment-routing-ti-lfa-21: “Topology Independent Fast Reroute - 12 using Segment Routing” -- 13 -- 14 **Others** -- 15 [186] NGMN “5G RAN CU-DU network architecture, transport options and - 16 dimensioning, version 1.0 12 April 2019” -- 17 [187] MEF 61.1: “IP Service attributes” -- 18 [188] MEF 10.3: “Ethernet Service attributes” -- 19 [189] MEF 6.2: “EVC service definition” -- 20 [190] Broadband Forum TR-101 “Migration to Ethernet-Based Broadband - 21 Aggregation” -- 22 [191] Broadband Forum TR-156 “Using GPON Access in the context of TR-101” -- 23 [192] ITU-R M.2083: “IMT Vision – framework and overall objectives of the future - 24 development of IMT for 2020 and beyond. -- 25 [193] ITU-T GSTR-TN5G – Transport network support of IMT 2020/5G -- 26 [194] ITU-T G.Sup.66 “5G wireless Fronthaul requirements in a passive optical - 27 network context” -- 28 [195] ITU-T G.9807 series “10-Gigabit-capable symmetric passive optical network”, - 29 ITU-T G.989 series “40-Gigabit-capable passive optical networks (NG PON2)”, - 30 On-going work ITU-T G.HSP -- 31 [196] ITU-T G.8271 “Time and phase synchronization aspects of telecommunication - 32 networks” -- 33 [197] ITU-T G.8271.1 “Network limits for time synchronization in packet networks - 34 with full timing support from the network” -- 35 [198] ITU-T G.8273.2 “Timing characteristics of telecom boundary clocks and - 36 telecom time slave clocks” -- 37 [199] ITU-T G.8275.1 “Precision time protocol telecom profile for phase/time - 38 synchronization with full timing support from the network” -- 39 [200] 40m Transmission of OAM mode and Polarization Multiplexing in E-band, - 40 Globcom, Dec 2019. M.Hirabe, et. Al -- 41 [201] CableLabs “Low Latency Mobile Xhaul over DOCSIS Technology” - 42 -- 43 [202] CableLabs “Synchronization Techniques for DOCSIS Technology - 44 Specification” -- 45 [203] CableLabs “Data-Over-Cable Service Interface Specifications 3.1, MAC and - 46 Upper Layer Protocols Interface” - 47 - -![O-RAN ALLIANCE logo](33e70787e71eebc7a200bc7fe352dadc_img.jpg) - -O-RAN ALLIANCE logo - -- 1 [204] CableLabs “Data-Over-Cable Service Interface Specifications 4.0, MAC and - 2 Upper Layer Protocols Interface” - 3 -- 4 [205] CableLabs “Remote PHY Specification” - 5 -- 6 [206] “Study on new radio access technology: Radio access architecture and - 7 interfaces” 3GPP TR 38.801 Table A-1. -- 8 [207] Cisco Press, MPLS and VPN Architectures, Volume 1, 420 pages, by Ivan - 9 Pepelnjak, and Jim Guichard, 2001 -- 10 [208] Cisco Press, MPLS and VPN Architectures, Volume 2, 470 pages, by Ivan - 11 Pepelnjak, Jim Guichard, and Jeff Apcar, 2003 -- 12 [209] O’Reilly, MPLS in the SDN Era, 890 pages, by Antonio Sánchez-Monge, and - 13 Krzysztof Grzegorz Szarkowicz, 2015 -- 14 [210] BBF TR-221: Technical Specification for MPLS in Mobile Backhaul Networks, - 15 99 pages, Oct 2011 -- 16 [211] BBF TR-221, Amd.1: Technical Specifications for MPLS in Mobile Backhaul - 17 Networks, 24 pages, Nov 2013 -- 18 [212] BBF TR-221, Amd.2: Technical Specifications for MPLS in Mobile Backhaul - 19 Networks, 22 pages, Sep 2017 -- 20 [213] ETSI GR mWT 012 V1.1.1 (2018-11): 5G Wireless Backhaul/Xhaul -- 21 [214] Microwave and millimeter-wave technology overview and evolution, Workshop - 22 on Evolution of Fixed Service in Backhaul support of IMT 2020 / 5G, Geneva, - 23 29 April 2019, [https://www.itu.int/en/ITU-R/study-](https://www.itu.int/en/ITU-R/study-groups/workshops/fsimt2020/Pages/default.aspx) - 24 [groups/workshops/fsimt2020/Pages/default.aspx](https://www.itu.int/en/ITU-R/study-groups/workshops/fsimt2020/Pages/default.aspx) -- 25 [215] ISO/IEC 10589-2002: “Intermediate System to Intermediate System intra- - 26 domain routeing information exchange protocol for use in conjunction with the - 27 protocol for providing the connectionless-mode network service” - 28 - 29 - -![O-RAN Alliance logo](3376f33dd811eb3e39ff47117c958ed9_img.jpg) - -O-RAN Alliance logo - -1 - -## 5 Definitions and abbreviations - -### 5.1 Definitions - -The key words “**SHALL**”, “**SHALL NOT**”, “**SHOULD**”, “**SHOULD NOT**”, “**MAY**”, and “**OPTIONAL**” in this document are to be interpreted as described in IETF RFC 2119 [25]. All key words must be in upper case, bold text. - -Items that are **REQUIRED** (contain the words **SHALL** or **SHALL NOT**) will be labelled as **[Rx]** for required. Items that are **RECOMMENDED** (contain the words **SHOULD** or **SHOULD NOT**) will be labelled as **[Dx]** for desirable. Items that are **OPTIONAL** (contain the words **MAY** or **OPTIONAL**) will be labelled as **[Ox]** for optional. - -Items, if supported, are not meant to be active at all times, but should be available for use. Their state (active or not active) should be based on configuration. - -### 5.2 Abbreviations - -Abbreviations defined in this document take precedence over the definition of 3GPP - -15 - -| Abbreviations | Meaning or explanation | -|---------------|---------------------------------------------------------------------------| -| 3GPP | Third Generation Partnership Project – Standards Development Organization | -| 4G | Fourth-generation mobile network | -| 5G | Fifth-generation mobile network | -| ABR | Area Border Router | -| AC | Attachment Circuit | -| Amd | Amendment (term used by BBF) | -| API | Application Programming Interfaces | -| ARPU | Average revenue per user | -| AS | Automated (traffic) steering | -| AS | Autonomous System | -| ASBR | Autonomous System Border Router | -| ASIC | Application-Specific Integrated Circuits | -| BBF | Broadband Forum | -| BBU | Baseband unit | -| BGP | Border Gateway Protocol | -| BGP-LU | BGP labelled unicast | -| BGP-LS | BGP link state | -| BIER | Bit Indexed Explicit Replication | -| BITS | Building Integrated Timing System | -| C-NMA | Computing-Aware Traffic Steering - Network Metric Agent | -| C-PS | Computing-Aware Traffic Steering - Path Selector | - -![O-RAN ALLIANCE logo](55d74563d1b88865295879cdaffce3ff_img.jpg) - -O-RAN ALLIANCE logo - -| | | -|----------|-----------------------------------------------------------| -| C-RAN | Centralized Radio Access Network | -| C-SMA | Computing-Aware Traffic Steering - Service Metric Agent | -| C-TC | Computing-Aware Traffic Steering - Traffic Classifier | -| CA | Carrier Aggregation | -| CA | Certification Authority | -| CapEx | Capital expenditure | -| CATS | Computing-Aware Traffic Steering | -| CBWRED | Class based Weighted Random Early Detection | -| CDN | Content delivery network | -| CDMA | Code Division Multiple-Access – a mobile radio standard | -| CMPv2 | Certificate Management Protocol version 2 | -| COTS | Commercial off the shelf | -| CPE | Customer premises equipment | -| CPRI | Common public radio interface | -| CPU | Central Processing Unit | -| CSP | Communications service provider | -| CSR | Cell Site Router | -| CU | Centralized Unit | -| CU-UP | Centralized Unit – User Plane | -| CUPS | Control/User Plane Separation | -| D-RAN | Distributed Radio Access Network | -| DB | Dynamic Bandwidth assignment | -| DC | Data center | -| DDR-RAM | Double Data Rate Synchronous Dynamic Random-Access Memory | -| DHCP | Dynamic Host Configuration Protocol | -| DHCPv4 | Dynamic Host Configuration Protocol for IPv4 hosts | -| DHCPv6 | Dynamic Host Configuration Protocol for IPv6 hosts | -| DiffServ | Differentiated services – a quality-of-service mechanism | -| DSCP | DiffServ Code Point | -| DU | Distributed Unit | -| DWDM | Dense Wavelength Division Multiplexing | -| E-SE | Edge Site Equipment | -| E-TNE | Edge Transport Network Equipment | -| EAP | Extensible Authentication Protocol | -| ECMP | Equal-cost multipath | -| eCPRI | Enhanced Common Radio Interface (CPRI) | -| eMBB | Enhanced mobile broadband | -| eNB | Enhanced Node B | -| EPC | Evolved packet core | - -![O-RAN Alliance logo](f756d8e1fde6bc6ebdf4a5d7f1b2a57a_img.jpg) - -O-RAN Alliance logo - -| | | -|---------------------|-----------------------------------------------------------------------------------------------| -| ESMC | Ethernet Synchronization Message Channel | -| EVPN | Ethernet VPN | -| EXP | Experimental | -| FDD | Frequency division duplexing | -| FHG | Fronthaul Gateway | -| FIB | Fabric Interface Board | -| FIB | Forwarding Information Base | -| FIFO | First In, First Out | -| FMC | Fixed-mobile convergence | -| FMC | Fixed-mobile convergence | -| FQDN | Fully Qualified Domain Name | -| FPGA | Field Programmable Gateway Array | -| Fronthaul | Portion of the mobile network supporting O-RAN 7.2x, eCPRI, RoE or CPRI protocols | -| FRR | Fast Re-Route | -| Gbps | Gigabits per second | -| GNSS | Global Navigation Satellite System (example being GPS) | -| GPS | Global Positioning System | -| HLS | High-level split | -| HSR | Hub Site Router | -| IANA | Internet Assigned Numbers Authority | -| iBGP | internal Border Gateway Protocol | -| IEC | International Electrotechnical Commission | -| IEEE | Institute of Electrical and Electronics Engineers – Standards Development Organization | -| IETF | Internet Engineering Task Force – Standards Development Organization | -| IGP | Interior Gateway Protocol | -| IoT | Internet of Things (see also mMTC) | -| IP | Internet Protocol | -| IPoDWDM | Internet Protocol over Dense Wavelength Division Multiplexing | -| IPsec | Internet Protocol Security | -| IS-IS | Intermediate System to Intermediate System | -| ISO | International Standardization Organization | -| ITU-T | International Telecommunication Union-Telecommunication – Standards Development Organization | -| ITU-R | International Telecommunication Union-Radiocommunication – Standards Development Organization | -| JSON | JavaScript Object Notation | -| L0 / L1 / L2 | Level 0 / Level 1 / Level 2 abstraction levels of Computing-Aware Traffic Steering metrics | -| L1 / L2 / L3 | Layer 1 / layer 2 / layer 3 of the network protocol stack | -| L3VPN | Layer 3 Virtual Private Network | -| LC | Line Card | -| LDP | Label Distribution Protocol | - -![O-RAN ALLIANCE logo](7cdd3a0b8107619a3a05ea9ed16eff02_img.jpg) - -O-RAN ALLIANCE logo - -| | | -|---------|--------------------------------------------------------------| -| LLS | Low-level splits | -| LSDB | Link state database | -| LSP | Label Switched Path | -| LTE | Long Term Evolution (generation of Mobile networks – see 4G) | -| LTE-A | Long Term Evolution – Advanced | -| MEC | Formerly Mobile Edge Compute, now Multi-Access Edge Compute | -| mMTC | Massive machine type communications | -| MIMO | Multiple-Input Multiple-Output (number of antennas) | -| MNO | Mobile Network Operator | -| MP-BGP | Multi-protocol Border Gateway Protocol | -| MPLS | Multiprotocol Label Switching | -| MSD | Maximum Segment Depth | -| MVNO | Mobile virtual network operator | -| NAT | Network Address Translation | -| NETCONF | Network Configuration Protocol | -| NF | Network Function | -| NFV | Network functions virtualization | -| NGFI | Next-generation Fronthaul interface | -| NLRI | Network Layer Reachability Information | -| NPU | Network Processing Unit | -| NR | New radio | -| NSI | Network Slice Instance | -| NSSI | Network Subnet Slice Instance | -| NTP | Network Time Protocol | -| O-Cloud | Open Cloud | -| O-CU | Open Central Unit | -| O-DU | Open Distributed Unit | -| O-RU | Open Radio Unit | -| OAM | Operations, administration, and maintenance | -| ODN | On-demand next hop | -| ODN | Optical Distribution Network | -| OLT | Optical Line Termination | -| ONU | Optical Network Unit | -| OpEx | Operational expenses | -| ORF | Outbound Route Filter | -| OSPF | Open Shortest Path First | -| OTN | Optical Transport Networking | -| P | Provider (router) | -| PCC | Path computation client | - -![O-RAN ALLIANCE logo](71dea59c7a8cc6669fcce714dca70021_img.jpg) - -O-RAN ALLIANCE logo - -| | | -|---------|------------------------------------------------------------------| -| PCE | Path computation element | -| PCEP | Path computation element protocol | -| PE | Provider edge (router) | -| PFE | Packet Forwarding Engine | -| PHY | Physical Layer | -| PIM | Protocol for IP Multicast | -| PKI | Public Key Infrastructure | -| PoE | Power over Ethernet | -| PON | Passive Optical Network | -| PSU | Power Supply Unit | -| PTP | Precision Time Protocol | -| QoS | Quality of Service | -| RA | Registration Authority | -| RAM | Random-Access Memory | -| RAN | Radio access network | -| RE | Radio equipment | -| RE | Routing Engine | -| REC | Radio equipment controller | -| RoE | Radio over Ethernet | -| RRO | Record Route Object | -| RRU | Remote Radio Unit | -| RSVP | Resource Reservation Protocol | -| RSVP-TE | Resource Reservation Protocol – Traffic Engineering | -| RT | Route Target | -| RTT | Round-trip times | -| RU | Rack unit | -| RU | Remote (radio) unit | -| RX | Receive | -| SD-WAN | Software-defined wide area network | -| SDH | Synchronous Digital Hierarchy – a digital communications system | -| SDN | Software-defined networks | -| SerDes | Serialize and Deserialize | -| SID | Segment Identifier | -| SLA | Service level agreement | -| SMB | Small and medium business | -| SMO | Service Management and Orchestration | -| SONET | Synchronous Optical Networking – a digital communications system | -| SPF | Shortest Path First | -| SR | Segment Routing | - -![O-RAN ALLIANCE logo](f2f0092624aaf8ad2bcb99a821409714_img.jpg) - -O-RAN ALLIANCE logo - -| | | -|--------|--------------------------------------------------------------------------| -| SR-DPM | Segment Routing-data plane management | -| SR-TE | Segment Routing – traffic engineering | -| SR-PCE | Segment Routing – path computation element | -| SRH | Segment Routing header | -| SIB | Switch Interface Board | -| SRLG | Shared risk link groups | -| SSH | Secure Shell | -| SSU | Synchronization Supply Unit | -| SyncE | Synchronous Ethernet | -| T-GM | Telecom – Grand Master – a PTP clock type | -| T-TSC | Telecom – Time Slave Clock – a PTP clock type | -| TAE | Time Alignment Error | -| TC | Traffic Class | -| TDD | Time-division duplexing – a radio communications technique | -| TDM | Time division multiplexing | -| TE | Traffic engineering | -| TE | Time Error | -| TI-LFA | Topology-independent loop-free alternative | -| TLS | Transport Layer Security | -| TLV | Type-Length-Value | -| TNE | Transport Network Equipment (an O-RAN term to denote a transport device) | -| TNM | Transport Network Management | -| ToD | Time of the Day | -| TR | Technical report | -| TTL | Time to live | -| TWDM | Time and Wavelength Domain Multiplexing | -| TX | Transmit | -| UE | User equipment | -| URLLC | Ultra-reliable low-latency communications | -| UPF | User plane functions | -| VIM | Virtualized infrastructure managers | -| VLAN | Virtual Local Area Network | -| VNF | Virtual network function(s) | -| VPN | Virtual private network | -| VRF | Virtual Routing and Forwarding | -| WAN | Wide area network | -| WDM | Wavelength Division Multiplexing | -| Xhaul | Collective name for Fronthaul, Midhaul, and Backhaul | -| XML | eXtensible Markup Language | - -![O-RAN ALLIANCE logo](8de18f629e5d8ab818f3eff277a9c08b_img.jpg) - -The logo for the O-RAN Alliance, featuring a colorful circular icon to the left of the text "O-RAN" in blue, with "ALLIANCE" in smaller blue letters underneath. - -O-RAN ALLIANCE logo - -| | | -|------|-------------------------------------------------------| -| YANG | Yet another next generation – data modelling language | -|------|-------------------------------------------------------| - -1 - -## 6 Transport network Reference Design and Requirements - -### 6.1 Reference Design and Terminology - -Following the boundaries outlined in previous sections, Figure 6-1 introduces a segmentation of connectivity between O-RAN NF for packet Networks based on management perimeters. The following terms are also introduced: - -- **Transport Network Equipment (TNE):** any node in the Transport Network (e.g. routers, switches). -- **Edge Transport Network Equipment (E-TNE):** the Edge TNE is a TNE that terminates an Attachment Circuit (e.g. a PE router) -- **Edge Site Equipment (E-SE):** the Edge Site Equipment terminates the Attachment Circuit within the O-RAN site to connect to the Transport Network (e.g. O-CLOUD gateway or a Network Function). -- **Attachment Circuit (AC):** the AC is a logical connection that attaches the Edge Site and the Transport Network Equipment. The AC serves as a demarcation between the TN and the O-RAN domains. -- **Bearer:** a physical or logical link that connects an Edge Site Equipment to the Transport Network. A bearer can be a wireless or wired link. The bearer refers to the underlying connection for the provisioning of an Attachment Circuit (e.g. a physical Ethernet connection on which an AC is configured thanks to vlan). One or multiple attachment circuits may be hosted over the same bearer (e.g., multiple VLANs on the same bearer realized by a physical link). -- **O-Cloud and TN Segment:** segment of the logical connectivity realized respectively within O-Cloud and Transport Network domains. The O-Cloud segment is optional since the NF may directly attach to the TN via the AC. -- **O-RAN Site:** the O-RAN Site refers to a location - physical or logical - hosting one or more O-RAN components (e.g., O-RU, O-DU, O-CU) and may include elements of the O-Cloud. -- - -![Figure 6-1: Reference Design for TN integration (logical). The diagram shows a logical connectivity path between two O-RAN Sites. On the left, an O-RAN Site contains an NF and an E-SE. The E-SE is connected to an AC, which is hosted on a Bearer. This Bearer connects to an E-TNE, which is part of a central Transport Network cloud. The Transport Network cloud contains two TNE nodes. On the right, another E-TNE connects to another AC, which is hosted on another Bearer. This Bearer connects to an E-SE, which is connected to an NF within a second O-RAN Site. Above the diagram, segments are labeled: 'O-CLOUD Segment(1)' (optional, between NF and E-SE), 'Attachment Circuit' (between E-SE and E-TNE), 'TN Segment' (within the Transport Network cloud), and 'Attachment Circuit' (between E-TNE and E-SE).](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) - -Figure 6-1: Reference Design for TN integration (logical). The diagram shows a logical connectivity path between two O-RAN Sites. On the left, an O-RAN Site contains an NF and an E-SE. The E-SE is connected to an AC, which is hosted on a Bearer. This Bearer connects to an E-TNE, which is part of a central Transport Network cloud. The Transport Network cloud contains two TNE nodes. On the right, another E-TNE connects to another AC, which is hosted on another Bearer. This Bearer connects to an E-SE, which is connected to an NF within a second O-RAN Site. Above the diagram, segments are labeled: 'O-CLOUD Segment(1)' (optional, between NF and E-SE), 'Attachment Circuit' (between E-SE and E-TNE), 'TN Segment' (within the Transport Network cloud), and 'Attachment Circuit' (between E-TNE and E-SE). - -(1) The O-CLOUD segment is optional as the NF can connect directly to the AC (i.e. the NF is the Edge Site Equipment) - -**Figure 6-1: Reference Design for TN integration (logical)** - -Notes - -![O-RAN ALLIANCE logo](e84dd53f6912e1d1da8c934533cc599f_img.jpg) - -O-RAN ALLIANCE logo - -- This representation is a logical view, whereby left and right components (i.e., TNE, AC, E-SE, etc.) can be identical. -- Connectivity to External Systems (External Sites) is not represented since it is out of the scope of O-RAN. Notwithstanding, this model is applicable for the connectivity between the O-RAN site and the TN. -- E-SE and E-TNE are logical components responsible for terminating TN-related connectivity within O-RAN site and TN management domains. In practice, their implementation can involve multiple components, in the same way as the distributed CE/PE architecture described in IETF specifications [178] - -The decomposition is aligned with IETF specifications for TN Slicing [178] through the mapping table in Figure 6-2. For convenience, this table also introduces the terminology in use for O-RAN WG6. - -| O-RAN WG9 | O-RAN WG6 | IETF | -|---------------------|----------------------------------|--------------------| -| Transport Network | Transport Network | Provider Network | -| TNE | TNE | | -| Edge TNE | PE | Provider Edge | -| O-RAN Site | O-CLOUD site | Customer Site | -| Edge Site Equipment | O-CLOUD Gateway Network Function | Customer Edge | -| Attachment Circuit | Attachment Circuit | Attachment Circuit | -| Bearer | Bearer | Bearer | - -Figure 6-2: Mapping Table for IETF terminology alignment - -## 6.2 Transport Network Requirements - -For full details of the O-RAN transport requirements, bandwidth and delay estimates of a 5G network see [20]. - -Requirements for the transport architecture can be characterized in following categories: - -1. Latency, Frame Loss Ratio and Bandwidth requirements for Fronthaul, Midhaul, and Backhaul. -2. Operability requirements that include fault and performance management. -3. Synchronization requirements. -4. “ITU-T GSTP-TN5G: Transport support of IMT-2020/5G” [193] identifies the need for the transport to be multi-service in nature. In addition to mobile services, the infrastructure needs to support fixed line consumer and enterprise services. These services are not explicitly covered in the document, but the architecture must enable L2 or L3 services to be created between any two edge TNEs regardless of relative position to each other in the transport network. -5. End to end support of 4G/5G mobile infrastructure including Fronthaul / Midhaul / Backhaul. -6. Concurrent support for RAN deployment scenarios outlined in “ITU-T GSTP-TN5G: Transport support of IMT-2020/5G” [193] running from a single cell site location. These shown in Figure 6-3 are: - - a. Co-located O-CU and O-DU – O-RAN split 7.2x from cell site - -![O-RAN Alliance logo](b99bfa6a26ede115d00d81059ee4ce6b_img.jpg) - -O-RAN Alliance logo - -- b. Independent O-RU, O-CU, O-DU locations – O-RAN 7.2x from cell site -- c. O-RU and O-DU integration on cell site – O-RAN split 2 from cell site -- d. O-RU, O-DU and O-CU integration on cell sites – Split 1 from cell site - -![Figure 6-3: ITU-T 5G use cases](dd5771673aececa53d42ece89218299d_img.jpg) - -The diagram shows four network architecture scenarios across five domains: Cell site, Access, Pre-Aggregation, Aggregation, and Core (5GC). A reference cloud diagram at the top shows the physical connectivity between these domains. - -- Scenario 1: O-RU (Cell site) connects via FH to O-DU (Access), which connects via BH to O-CU (Aggregation), which connects to UPF/N6 (Core). -- Scenario 2: O-RU (Cell site) connects via FH to O-DU (Pre-Aggregation), which connects via MH (Xn) to O-CU (Aggregation), which connects to UPF/N6 (Core). -- Scenario 3: O-RU and O-DU are integrated (Cell site) and connect via MH to O-CU (Aggregation), which connects to UPF/N6 (Core). -- Scenario 4: O-RU, O-DU, and O-CU are integrated (Cell site) and connect via BH to UPF/N6 (Core). - -All scenarios show a BH(N9) connection from the UPF to the 5GC. - -Figure 6-3: ITU-T 5G use cases - -**Figure 6-3: ITU-T 5G use cases** - -7. Central, distributed or a mix of the two for user plane termination. Central, distributed or a mix of two for 5G control plane placement. (Figure 6-4) - -![Figure 6-4: 5G central and distributed user plane termination](6470d350326789d5306eabcb76533951_img.jpg) - -This diagram illustrates the separation of Control Plane (CP) and User Plane (UP) for the O-CU. The domains are Cell site, Access, Pre-Aggregation, Aggregation, and Core (5GC). - -- O-RU (Cell site) connects via FH to O-DU (Access). -- O-DU (Access) has two paths: - - A Control Plane path via MH to O-CU CP (Aggregation). - - A User Plane path via MH to O-CU UP (Pre-Aggregation). -- O-CU CP and O-CU UP are connected via an Xn interface. -- O-CU UP connects via BH to a UPF (Pre-Aggregation), which then connects via BH to the Core (5GC). -- The UPF also has an N6 AF interface. - -Figure 6-4: 5G central and distributed user plane termination - -**Figure 6-4: 5G central and distributed user plane termination** - -8. Concurrent support for 4G and 5G RAN solutions running from a single cell site. In addition to the use cases outlined in earlier figures, support for 4G radios running alongside 5G radios is required. Figure 6-5 illustrates the two 4G architectures that need to co-exist with the 5G architectures outlined above. In the upper case, the 4G RAN infrastructure utilizes a C-RAN architecture where the RRH and BBU support split 8 which is converted to 7.2x or RoE for - -![O-RAN Alliance logo](c65ad236792ad44010344a71df2b4947_img.jpg) - -O-RAN Alliance logo - -transportation across the packet access infrastructure. In the lower case, the 4G RAN infrastructure uses D-RAN or split 1 architecture. - -![Figure 6-5: 4G use cases. The diagram shows two network architectures. The top architecture is a cloud-based model with components: Cell site (antenna icon), Access (cloud), Pre-Aggregation (cloud), Aggregation (cloud), and Core (5GC box). The bottom architecture shows two cases: 1) RRH connected to BBU via FH CPRI/eCPRI/RoE, with BBU connected to SAE GW via BH, and SAE GW connected to GILAN. 2) eNB connected directly to SAE GW via BH, and SAE GW connected to GILAN.](00504fc688ebcf131ccbeff94dfc9939_img.jpg) - -Figure 6-5: 4G use cases. The diagram shows two network architectures. The top architecture is a cloud-based model with components: Cell site (antenna icon), Access (cloud), Pre-Aggregation (cloud), Aggregation (cloud), and Core (5GC box). The bottom architecture shows two cases: 1) RRH connected to BBU via FH CPRI/eCPRI/RoE, with BBU connected to SAE GW via BH, and SAE GW connected to GILAN. 2) eNB connected directly to SAE GW via BH, and SAE GW connected to GILAN. - -Figure 6-5: 4G use cases - -9. End to end support for 5G slicing and 5G service types. - -## 7 5G logical connectivity requirements - -The transport network needs to be very flexible as depending on the use case and the RAN design each part of the physical transport network may need to support multiple slices, multiple 5G services and also different 3GPP interfaces. This section covers the logical transport connectivity requirements of the 5G Fronthaul, Midhaul and Backhaul components. Further details can be found in O-RAN WG9.Transport Requirements document [20]. - -### 7.1 Fronthaul - -The Fronthaul infrastructure potentially needs to support: - -- O-RAN 7.2x Fronthaul (for 5G NR) -- Non-ORAN Fronthaul - -#### 7.1.1 O-RAN 7.2x Fronthaul - -The O-RAN 7.2x is a split 7 “Low Level Split” (LLS) that runs between the O-RU and the O-DU (optional more than one for network and DU based redundancy). The associated mobile interfaces for the Fronthaul are the Control, User and Synchronization and Management planes. The synchronization plane is covered in a separate WG-9 Timing and Synchronization Architecture and solutions document [22]. - -1 - -![Figure 7-1: Fronthaul O-RAN 7.2x control and user plane using an Ethernet encapsulation. The diagram shows six O-RUs connected to a central cloud representing the Access Network. Each O-RU is connected to a CSR (Cell Site Router) within the cloud. The CSRs are connected to a Hub Site Router (HSR) at the edge of the cloud. The HSR is connected to an O-DU. Below the O-DU, a label indicates 'Individual Interface / VLAN per O-RU'. At the bottom, a label 'L2 VPWS (via EVPN) for 7.2X C/U Plane' is shown.](e05b36c0d46549e681ce6581422c66b2_img.jpg) - -Figure 7-1: Fronthaul O-RAN 7.2x control and user plane using an Ethernet encapsulation. The diagram shows six O-RUs connected to a central cloud representing the Access Network. Each O-RU is connected to a CSR (Cell Site Router) within the cloud. The CSRs are connected to a Hub Site Router (HSR) at the edge of the cloud. The HSR is connected to an O-DU. Below the O-DU, a label indicates 'Individual Interface / VLAN per O-RU'. At the bottom, a label 'L2 VPWS (via EVPN) for 7.2X C/U Plane' is shown. - -2 -3 - -**Figure 7-1: Fronthaul O-RAN 7.2x control and user plane using an Ethernet encapsulation** - -![Figure 7-2: O-RAN 7.2x Hybrid Management plane. The diagram shows a network path from left to right: Cell site, Access, Pre-Aggregation, Aggregation, and Core. At the Cell site, three O-RUs are connected to a CSR. The CSR is connected to the Access cloud. An O-DU is connected to the Access cloud. The Access cloud is connected to the Pre-Aggregation cloud. The Pre-Aggregation cloud is connected to the Aggregation cloud. The Aggregation cloud is connected to the Core cloud. An NMS is connected to the Core cloud. A thick orange line labeled 'Open fronthaul management plane' runs across the top of the diagram, connecting the O-RUs to the NMS.](a05e675f8651ae7ccea1d0d68691d1a9_img.jpg) - -Figure 7-2: O-RAN 7.2x Hybrid Management plane. The diagram shows a network path from left to right: Cell site, Access, Pre-Aggregation, Aggregation, and Core. At the Cell site, three O-RUs are connected to a CSR. The CSR is connected to the Access cloud. An O-DU is connected to the Access cloud. The Access cloud is connected to the Pre-Aggregation cloud. The Pre-Aggregation cloud is connected to the Aggregation cloud. The Aggregation cloud is connected to the Core cloud. An NMS is connected to the Core cloud. A thick orange line labeled 'Open fronthaul management plane' runs across the top of the diagram, connecting the O-RUs to the NMS. - -**Figure 7-2: O-RAN 7.2x Hybrid Management plane** - -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15 -16 -17 -18 -19 - -- **O-RAN 7.2x Control and User planes:** These interfaces are described in O-RAN.WG4.CUS.0-v09.00: Control, User and Synchronization Plane Specification [18]. These interfaces run between the O-RUs and their serving O-DU. Ethernet encapsulation is a mandatory requirement and IP encapsulation is optional and applies if the transmitting and receiving nodes support IP capabilities. In both cases the payload is one or more eCPRI transport headers with respective application data. The latency requirements associated with 7.2x control plane and user plane traffic are very low, and the bandwidth requirements are generally high but vary based on the level of user data traffic being transmitted. -- **O-RAN 7.2x Synchronization plane:** This interface is described in O-RAN.WG4.CUS.0-v9.00: Control, User and Synchronization Plane Specification [18]. In C-RAN architectures accurate synchronization between the O-DU and O-RUs is required to support “Time Division Duplex” (TDD), Carrier Aggregation (CA) using multiple O-RUs, MIMO and other processes. In an O-RAN Fronthaul environment using an Ethernet transport layer, protocols such as PTP - -![O-RAN Alliance logo](40647355b8fe9eeaadd5a58444dfe51d_img.jpg) - -O-RAN Alliance logo - -and SyncE are used to achieve synchronization between the O-RUs and O-DUs. For more details refer to WG-9 Timing and Synchronization Architecture and solutions document [22]. - -- **O-RAN 7.2x Management plane:** This interface is described in O-RAN.WG4.MP.0-v09.00 Management plane specification[19]. Two M-Plane models are defined. - - Hierarchical model: In this model, an O-RU is managed by one or more O-DUs. These O-DUs are entirely responsible for sub-ordinate O-RUs, which means the NMS only needs to interact with the O-DU level. In this mode the O-RAN 7.2x M-Plane interface only runs between the O-DU and sub-ordinate O-RUs. - - Hybrid model: In this model, an O-RU is managed by one or more NMSs, in addition to the serving O-DU. In this mode the O-RAN 7.2x M-Plane interface runs between the O-RUs, O-DUs and the NMS. - -The O-RAN 7.2x M-plane uses IP/NETCONF and the basic transport requirement is end-to-end IP connectivity between the O-RU and the elements managing it. IPv4 shall be supported as a mandatory transport protocol for M-Plane and IPv6 support is optional. - -### 7.1.2 O-RAN Fronthaul logical transport requirements - -Details of the O-RAN transport requirements are illustrated in Figure 7-1. - -#### C/U-Planes: - -1. Ethernet connectivity from O-RUs to serving O-DU with potential backup to a redundant O-DU. -2. Optional IP connectivity from O-RUs to serving O-DU with potential backup to a redundant O-DU. -3. O-RUs and serving O-DU in close proximity to each other to meet delay criteria associated with Fronthaul. It is unlikely the Fronthaul components (ie O-RUs and serving O-DU) will extend beyond the access transport network. - -#### S-Plane: - -1. This is covered in the “WG-9 Timing and Synchronization Architecture and Solutions document [22]. - -#### M-Plane - -Details of the O-RAN M-Plane transport running in hybrid mode are illustrated in Figure 7-2. - -1. IP connectivity allowing NMS to communicate with O-DUs and O-RUs if running the hybrid model. -2. IP connectivity allowing serving O-DU to communicate with all its sibling O-RUs if running in either hybrid or hierarchical models. - -Note: In addition to the 7.2x management plane other management components may need to communicate with entities at the cell site. For example, remote monitoring of sensors and actuators in the cell site. These are not explicitly covered in this document, but the specified transport architecture can cater for scenarios, where management and monitoring, are based on either Ethernet or IP connectivity. - -## 7.2 Non-ORAN Fronthaul - -Legacy Fronthaul scenarios are those C-RAN use cases where the Fronthaul traffic is transported over a packet switch network while not using the O-RAN compliant encapsulation protocol that - -![O-RAN Alliance logo](307998a4f76d5fa18ce3713f51d0692f_img.jpg) - -O-RAN Alliance logo - -1 supports 7.2x split. The two most likely legacy Fronthaul scenario in a packet switched transport - 2 network are: - -- 3 -- 4 • eCPRI based C-RAN solutions: using eCPRI encapsulation protocol not compliant to O- -- 5 RAN WG4 CUS specifications [18]. i.e., a non O-RAN 7.2x split. -- 6 • RoE based C-RAN solutions: CPRI encapsulated by the RoE protocol. -- 7 - -### 8 7.2.1 eCPRI based C-RAN solutions - -9 An operator may choose a packet-based C-RAN Fronthaul architecture that is not O-RAN 7.2x - 10 compliant. In this case the RU and DU uses eCPRI as the packet encapsulation protocol to - 11 packetize the Fronthaul data but implements a non-O-RAN compliant radio message protocol to - 12 support a different function split. - -13 - -14 Following 3GPP recommendation [9], the possible function splits may include - -- 15 • Option 6, split between MAC and PHY layers -- 16 • Option 7.1, 7.2, or 7.3, splits within PHY layer -- 17 • Option 8, split between radio and PHY layer -- 18 - -### 19 7.2.2 Radio over Ethernet (RoE) based C-RAN solutions - -20 In this scenario an operator has an existing radio deployed at the cell site and the operator intends to - 21 convert these radios to support a C-RAN Fronthaul architecture whilst implementing their 5G RAN - 22 infrastructure. In this case it is likely the legacy equipment (RRH and BBU) only supports an - 23 optical CPRI interfaces. To implement a C-RAN Fronthaul architecture in a packet switched - 24 transport network the CPRI needs to be converted to an Ethernet frame at the cell site, transported - 25 over the access network as packet and then get converted back to CPRI at the hub for processing - 26 from the BBU. In this scenario a component called a RoE mapper is used to perform a CPRI to - 27 Ethernet frame conversion at the cell site and an Ethernet frame to CPRI conversion at the location - 28 where the BBU is located. - -#### 29 7.2.2.1 RoE Mapper transport - -30 The design, implementation, management, and interface from the RoE mapper to the legacy - 31 equipment is not in the scope of WG-9 but the expectation is the RoE mapper will present either O- - -32 RAN 7.2x compliant Ethernet or Ethernet IP packets or IEEE 1914.3 Radio over Ethernet packets - -33 [40] to the transport network. At this time O-RAN has not defined a CPRI to O-RAN 7.2x - -34 conversion capability so implementations out in the market are based on CPRI to Radio Over - -35 Ethernet. - -36 - -37 It is then the responsibility of the transport network to transport these packets to their destination - -38 with appropriate characteristics for the legacy connection to function. - -#### 39 7.2.2.2 Radio over Ethernet - -40 Radio over Ethernet (RoE) is defined in IEEE Std 1914.3-2018 – IEEE standard for radio over - -41 Ethernet Encapsulations and Mappings [40]. Two mapping techniques for supporting CPRI to - -42 packet conversion are defined. - -#### 43 - -### 44 Structure-agnostic RoE mapper - -![O-RAN Alliance logo](cff94fda4719415b20d835d30d2bef5a_img.jpg) - -O-RAN Alliance logo - -The structure-agnostic RoE mapper captures bits from one end of a constant bit rate link, packetizes the bits into Ethernet frames, sends the frames across the network, and then recreates the bit stream at the far end of the link. While the constant bit-rate data stream is commonly encoded with the CPRI protocol, it could also be of any other protocol, provided it is within the range of data rates supported by that equipment. - -The structure-agnostic RoE mapper has two main modes of operation: - -- Tunnelling mode or type 0 works as a simple Ethernet tunnel. It does not remove any line coding bits and does not interpret any special characters (such as K-characters). If the source data is 8b/10b-encoded, the 10-bit symbols present on the line will be tunnelled by this RoE mapper as 10 bits of data. Similarly, 66-bit symbols will be sent for 64b/66b-encoded data as 66 bits of data. The entire stream is simply packetized. -- Line-coding-aware mode or type 1 removes the line coding bits such as for CPRI encoded with 8b/10b or 64b/66b. If the source data is 8b/10b-encoded, the 8-bit symbols present on the line will be tunnelled by this RoE mapper as 8 bits of data. Similarly, if the source data is 64b/66b encoded, the 64-bit symbols present on the line will be tunnelled by this RoE mapper as 64 bits of data. To allow the restoration of the 10-bit or 66-bit symbols at the de-mapper, the RoE mapper/de-mapper must have some awareness of the protocol it is mapping/de-mapping; the locations of the special characters must be known a priori relative to an event that is indicated in the RoE frame. - -### Structure-aware RoE mapper - -In this mode only the useful information in the CPRI stream is packetized into the RoE frames and different types of data (such as control words and data words) can be encapsulated into separate frames for prioritized processing. Those unused fields within the CPRI stream will be ignored thus bring the benefit of Fronthaul BW reduction. This mode requires full knowledge of the protocol layout of the CPRI and due to the proprietary nature of CPRI will require input from the radio vendor. - -### 7.2.3 Non O-RAN Fronthaul logical transport requirements - -The main use case identified by operators for non O-RAN fronthaul is 4G equipment that uses CPRI between the RRH and the BBU (see section 8.4). To support this over a packet based fronthaul network, the CPRI stream needs to be packetized as it ingresses the packet network and the CPRI stream reconstructed as it egresses the packet network. Bandwidth, delay and jitter characteristics in the packet network clearly depend on the technology used to perform this function, which is outside the scope of O-RAN. To provide some guidance on support of this traffic it has been assumed that it is presented as Ethernet and has similar delay and jitter requirements as 7.2x fronthaul traffic. - -## 7.3 D2 interface transport requirements - -ORAN TS OAD specification ([31]) defines the D2 interface that connects a pair of O-DUs. Figure 7-3 is taken from ORAN TS WG5 D2 GAP specification ([32]) clause 4.2. - -1 - -![Figure 7-3: D2 Interface diagram showing the network architecture. At the top, an O-CU-UP1 is connected to an O-CU-CP1 via an E1 interface. The O-CU-CP1 is connected to three O-DUs (O-DU1, O-DU2, and O-DUn) via F1-c interfaces. The O-CU-UP1 is also connected to the O-DUs via F1-u interfaces. The O-DUs are connected to three O-RUs (O-RU1, O-RU2, and O-RU3) via Open FH interfaces. The O-DUs are interconnected via D2-c and D2-u interfaces, shown as orange lines between O-DU1 and O-DU2, and between O-DU2 and O-DUn.](2837ffdadcdb1e5bababa56b564e56ed_img.jpg) - -Figure 7-3: D2 Interface diagram showing the network architecture. At the top, an O-CU-UP1 is connected to an O-CU-CP1 via an E1 interface. The O-CU-CP1 is connected to three O-DUs (O-DU1, O-DU2, and O-DUn) via F1-c interfaces. The O-CU-UP1 is also connected to the O-DUs via F1-u interfaces. The O-DUs are connected to three O-RUs (O-RU1, O-RU2, and O-RU3) via Open FH interfaces. The O-DUs are interconnected via D2-c and D2-u interfaces, shown as orange lines between O-DU1 and O-DU2, and between O-DU2 and O-DUn. - -Figure 7-3: D2 Interface - -2 - -3 - -4 - -5 - -The D2 interface is a logical interface connecting two O-DUs for supporting inter O-DU carrier aggregation. A pair of O-DUs can be connected with each other by the D2 interface to support control and user plane message exchange for supporting features such as inter O-DU carrier aggregation. D2 interface supports control (D2-c) and user plane (D2-u) functionality. - -6 - -7 - -8 - -### 7.3.1 Overall D2 requirements - -9 - -10 - -1. Control Plane: - -11 - -- a. Point to point at the IP interfaces level (IPv6 and/or IPv4) between O-DUs (D2-c interface). - -12 - -13 - -2. Data Plane: - -14 - -- a. Point to point at the IP interfaces level (IPv6 and/or IPv4) between O-DUs (D2-u interface) with strict latency requirement as mentioned in ORAN TS WG5 D2 GAP specification [32]. - -15 - -16 - -17 - -3. Some operators may wish to use the single ethernet connectivity for D2 transport. - -18 - -19 - -4. Some operators may wish to treat D2 transport as discrete logical networks. D2 transport can travel through a network that includes a small finite number of switches/routers to meet the latency requirement of D2. - -20 - -21 - -22 - -23 - -## 7.4 Midhaul logical transport requirements - -24 - -25 - -3GPP TS 38.401 [9] defines the de-aggregated RAN, it's characteristics and outlines the F1-U, F1-C and E1 interfaces. Figure 7-4, taken from 3GPP TS 38.401 illustrates the components and interfaces. The Midhaul transport infrastructure is responsible for supporting these interfaces. - -26 - -27 - -28 - -29 - -![Diagram of a deaggregated gNB showing its internal components and interfaces. The gNB is enclosed in a dashed box. Inside, there is a gNB-CU-CP (Control Plane) connected to multiple gNB-CU-UPs (User Plane) via E1 interfaces. The gNB-CU-CP is also connected to multiple gNB-DUs (Distributed Units) via F1-C (Control) interfaces. The gNB-CU-UPs are connected to the gNB-DUs via F1-U (User) interfaces.](145d00f59802048185303f15937ea65c_img.jpg) - -Diagram of a deaggregated gNB showing its internal components and interfaces. The gNB is enclosed in a dashed box. Inside, there is a gNB-CU-CP (Control Plane) connected to multiple gNB-CU-UPs (User Plane) via E1 interfaces. The gNB-CU-CP is also connected to multiple gNB-DUs (Distributed Units) via F1-C (Control) interfaces. The gNB-CU-UPs are connected to the gNB-DUs via F1-U (User) interfaces. - -Figure 7-4: Deaggregated gNB - -The characteristics of a disaggregated gNB are: - -- A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs and multiple gNB-DUs -- DUs and CU-UPs are connected to one CU-CP via the E1 interface or the F1-C interface -- DUs can connect to multiple CU-UPs -- Multiple CU-UPs can connect to one CU-CP -- For resiliency reasons, DUs and CU-UPs may connect to multiple CU-CPs - -The 3GPP interface associated with O-DU and O-CU communication is the F1 interface. It has a control (F1-C) and data (F1-U) plane component. - -**Note:** W1 interface is the 4G equivalent of the F1 interface. It will not be discussed further in this document as its characteristics are expected to be like the 5G equivalent. - -The 3GPP interfaces associated with intra O-CU communications is the E1 interfaces. It runs between the gNB-CU-CP and a gNB-CU-UP. It allows these two components to run as separate entities and potentially in different locations. - -#### 7.4.1 Overall Midhaul logical transport requirements - -5. Control Plane: - - a. Multi-point at the IP interfaces level (IPv4 or IPv6) between O-CU-CP and multiple O-DUs (F1-C interface). - - b. Multi-point at the IP interfaces level (IPv4 or IPv6) between O-CU-CP and multiple O-CU-UPs (E1 interface). -6. Data Plane: Multi-point at the IP interfaces level (IPv4 or IPv6) between O-CU-UP and multiple O-DUs (F1-U interface). -7. IP connectivity between O-CUs for Xn interface. -8. Some operators may wish to run the user plane interface (F1-U) separately from the control plane interfaces (E1 and F1-C). -9. Some operators may wish to treat Midhaul and Backhaul as a single logical network. -10. Some operators may wish to treat Midhaul and Backhaul as discrete logical networks. - -## 7.5 Backhaul logical transport requirements - -Figure 7-5 shows components and the 3GPP interfaces in the mobile Backhaul. It has a control plane and user plane component. It is not uncommon to see the control plane and the data plane divided into separate closed user groups (VPNs) at the transport layer to ensure a clear demarcation between customer user data and the 3GPP control plane. - -![Diagram of 5G Backhaul components and interfaces. The diagram shows the flow of control and user plane traffic between various 5G components. On the left, a UE connects to an (R)AN via the N1 interface. The (R)AN connects to the AMF via the N2 interface. The AMF connects to the SMF via the N11 interface. The SMF connects to the PCF via the N7 interface. The PCF connects to the AF via the N5 interface. The SMF also connects to the UPF via the N4 interface. The UPF connects to the DN via the N6 interface. The (R)AN also connects to the UPF via the N3 interface. The UPF connects to another UPF via the N9 interface. The diagram is shaded to indicate control plane (light blue) and user plane (light green) traffic. The legend on the right indicates BH UP (Backhaul User Plane) and BH CP (Backhaul Control Plane).](02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg) - -Diagram of 5G Backhaul components and interfaces. The diagram shows the flow of control and user plane traffic between various 5G components. On the left, a UE connects to an (R)AN via the N1 interface. The (R)AN connects to the AMF via the N2 interface. The AMF connects to the SMF via the N11 interface. The SMF connects to the PCF via the N7 interface. The PCF connects to the AF via the N5 interface. The SMF also connects to the UPF via the N4 interface. The UPF connects to the DN via the N6 interface. The (R)AN also connects to the UPF via the N3 interface. The UPF connects to another UPF via the N9 interface. The diagram is shaded to indicate control plane (light blue) and user plane (light green) traffic. The legend on the right indicates BH UP (Backhaul User Plane) and BH CP (Backhaul Control Plane). - -Figure 7-5: 5G Backhaul components and interfaces Source: Adapted from 3GPP TS 23.501 v6.4.0(2020-03): System Architecture for 5G [1] with control plane / user plane shading added by document authors. - -The 5G 3GPP interfaces associated with Backhaul are: - -- **N1 interface** is a logical control plane interface between the mobile core network and the UE. From a physical perspective it flows via the RAN through the Backhaul infrastructure to the AMF. It is a signalling interface between the UE and the AMF. -- **N2 interface** supports control plane signalling between RAN and 5G core. It is primarily concerned with connection management, UE context and PDU session management, and UE mobility management. In addition, Non-Access Spectrum (NAS) signalling between the UE and the AMF is transported over the N2 connection for that UE. This signalling includes information regarding access control, authentication and authorization, and session management procedures. -- **N4 Interface** is the bridge between the control plane and the user plane of the 5GC. It runs between the SMF and the UPF and is responsible for conveying policy rules regarding policy handling, forwarding and usage reporting to the UPF. -- **N3 interface** is the user plane interface between the O-CU component of the (gNB) and the initial UPF. -- **N9 interface** is a user plane interface that runs between two UPFs. (i.e. an intermediate UPF and the UPF session anchor). - -### 7.5.1 Overall Backhaul logical transport requirements - -1. Control Plane: Multi-point at the IP interfaces level (IPv4 or IPv6) between O-CU, UPF and 5GC components (N1, N2, N4, Xn-c). -2. User Plane: Multi-point at the IP interfaces level (IPv4 or IPv6) between O-CU ↔ UPF (N3), UPF ↔ UPF (N9) and O-CU ↔ O-CU (Xn-u). -3. Some operators may wish to run the Backhaul user plane (N3/N9) separate from the Backhaul control plane (N1/N2/N4). -4. Some operators may wish to treat Midhaul and Backhaul as a single logical network. -5. Some operators may wish to treat Midhaul and Backhaul as discrete logical networks. - -1 - -## 8 Operator's use cases - -Operators have indicated the following use cases are of interest. Any combination of these scenarios may apply in practical deployments though they are described individually. Unless otherwise stated, the eCPRI traffic herein is O-RAN compliant and presents the data according to O-RAN Open Fronthaul CUS plane and management plane specifications [18][19]. - -Multicast use cases are deferred to section 15.1, after logical network and services have been described, so that they can be provided with better background. - -Before describing the individual deployment scenarios, it is worth clarifying the terminology of C-RAN vs. D-RAN. In a 5G Distributed RAN (D-RAN) architecture, the O-CU, O-DU, and O-RU all reside at the cell site (Figure 8-1). - -![Figure 8-1: 5G O-RAN D-RAN architecture diagram. It shows a 'Cell Site' containing an antenna connected to an O-RU, which is connected to an O-DU, which is connected to an O-CU. The O-CU is connected to a TNE. A 'Backhaul' line connects this TNE to another TNE at a 'Centralized Site', which is then connected to a 5GC EPC. Vertical dashed red lines separate the Cell Site and Centralized Site components.](9f862801bce82634d3b5a1e0a195a799_img.jpg) - -Figure 8-1: 5G O-RAN D-RAN architecture diagram. It shows a 'Cell Site' containing an antenna connected to an O-RU, which is connected to an O-DU, which is connected to an O-CU. The O-CU is connected to a TNE. A 'Backhaul' line connects this TNE to another TNE at a 'Centralized Site', which is then connected to a 5GC EPC. Vertical dashed red lines separate the Cell Site and Centralized Site components. - -Figure 8-1 5G O-RAN D-RAN architecture - -5G Centralized RAN (C-RAN) architectures splits the radio components into discrete components which can be in different locations. In 5G O-RAN model (Figure 8-2), operators may decide to only place the O-RU at the cell site, and centralize the O-DUs or the O-DUs together with O-CU in a central location. The other alternative can be represented by locating the O-RUs and O-DUs at the cell-site and centralizing the O-CUs in a location farther away. - -![Figure 8-2: 5G O-RAN C-RAN architectures diagram. It shows two alternative configurations. The top configuration shows a 'Cell Site' with an O-RU connected to a TNE. A 'Fronthaul' line connects this TNE to another TNE at a 'Centralized Site', which is connected to an O-DU, then a TNE. A 'Midhaul F1' line connects this TNE to another TNE, which is connected to an O-CU, then a TNE. A 'Backhaul N2,N3' line connects this TNE to a 5GC EPC. The bottom configuration shows a 'Cell Site' with an O-RU connected to an O-DU, which is connected to a TNE. A 'Midhaul' line connects this TNE to another TNE at a 'Centralized Site', which is connected to an O-CU, then a TNE. A 'Backhaul N2,N3' line connects this TNE to a 5GC EPC. Vertical dashed red lines separate the Cell Site and Centralized Site components.](b560268ea8f6526970f23f0da225b099_img.jpg) - -Figure 8-2: 5G O-RAN C-RAN architectures diagram. It shows two alternative configurations. The top configuration shows a 'Cell Site' with an O-RU connected to a TNE. A 'Fronthaul' line connects this TNE to another TNE at a 'Centralized Site', which is connected to an O-DU, then a TNE. A 'Midhaul F1' line connects this TNE to another TNE, which is connected to an O-CU, then a TNE. A 'Backhaul N2,N3' line connects this TNE to a 5GC EPC. The bottom configuration shows a 'Cell Site' with an O-RU connected to an O-DU, which is connected to a TNE. A 'Midhaul' line connects this TNE to another TNE at a 'Centralized Site', which is connected to an O-CU, then a TNE. A 'Backhaul N2,N3' line connects this TNE to a 5GC EPC. Vertical dashed red lines separate the Cell Site and Centralized Site components. - -Figure 8-2 5G O-RAN C-RAN architectures - -![O-RAN Alliance logo](936b3e95dfcb46dbc0aafc0d71e13469_img.jpg) - -O-RAN Alliance logo - -When considering a C-RAN architecture there are both positive and negative impacts. On the positive side, it can increase component efficiency by pooling RAN elements in a centralised location and improve co-ordination between the radio component. On the negative side a C-RAN architecture can significantly increase the bandwidth required if the Fronthaul protocols are traversing the transport network. - -**Note:** The representation of the access and aggregation networks in the use case figures below are not to scale. In scenarios where a Fronthaul component exists, the access network will be geographically constrained due to delay requirements of the Fronthaul protocols. In contrast, the aggregation network in the figures can cover much greater areas due to more relaxed delay requirements of the 5G Midhaul and Backhaul protocols. - -## 8.1 Scenario 1: C-RAN architecture with collocated O-DU and O-CU - -As illustrated in Figure 8-3 for this scenario, O-DU and O-CU are collocated at a Hub site, therefore the Midhaul traffic between O-DU and O-CU is local and not going through the transport network. The eCPRI traffic from the 7.2x split from the O-RU, is transported by a packet switched access transport network to the C-RAN Hub. At the other end of the C-RAN Hub, the aggregation transport network transports the Backhaul traffic to the mobile core. - -The O-RU can be a new NR radio as well as a legacy LTE radio, as long as they are made to have the O-RAN compliant Fronthaul interface with 7.2x function split. - -The Xn traffic that performs the inter-gNB coordination is considered as part of Midhaul traffic, but it will not reach to the Core. Instead, it is routed to another O-CU, either within the same Hub site or between the Hub sites, via the aggregation transport network. - -There is inter-connection between the access and aggregation transport networks for the passing through services such as management traffic. In some cases, the two transport networks can share a same edge router that naturally completes the connection. - -![Diagram of C-RAN architecture with collocated O-DU and O-CU. The diagram shows three main components: Cell site, C-RAN Hub, and Core. The Cell site contains an O-RU connected to a 7.2x split. The C-RAN Hub contains an O-DU and an O-CU connected by an F1 interface. The Core contains a 5GC. The O-RU is connected to the O-DU via an eCPRI interface (red dashed line) through an Access network (cloud). The O-DU is connected to the O-CU via an F1 interface (orange dashed line). The O-CU is connected to the 5GC via an N2/N3 interface (green dashed line) through an Aggregation network (cloud). The Xn interface (green dashed line) is shown between the O-CU and the Aggregation network. A legend at the bottom indicates: Red dashed line = Fronthaul, Orange dashed line = Midhaul, Green dashed line = Backhaul.](ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg) - -Diagram of C-RAN architecture with collocated O-DU and O-CU. The diagram shows three main components: Cell site, C-RAN Hub, and Core. The Cell site contains an O-RU connected to a 7.2x split. The C-RAN Hub contains an O-DU and an O-CU connected by an F1 interface. The Core contains a 5GC. The O-RU is connected to the O-DU via an eCPRI interface (red dashed line) through an Access network (cloud). The O-DU is connected to the O-CU via an F1 interface (orange dashed line). The O-CU is connected to the 5GC via an N2/N3 interface (green dashed line) through an Aggregation network (cloud). The Xn interface (green dashed line) is shown between the O-CU and the Aggregation network. A legend at the bottom indicates: Red dashed line = Fronthaul, Orange dashed line = Midhaul, Green dashed line = Backhaul. - -Figure 8-3: Scenario 1 – C-RAN architecture with collocated O-DU and O-CU - -![O-RAN Alliance logo](7f78becb007c69a3a1b4aef8edc0e328_img.jpg) - -O-RAN Alliance logo - -## 8.2 Scenario 2: C-RAN architecture with collocated O-RU and O-DU - -In this scenario, both O-RU and O-DU are deployed at the cell site and O-CU is located at the Hub site. By 3GPP standard, the O-DU and O-CU is split by the functional split option 2 and connected with F1 interface, which is transported by the access transport network that connects the cell site and the Hub site. The aggregation transport network carries the N2/N3 Backhaul traffic to the 5G core. - -O-RU and O-DU may be collocated or be in close proximity around the cell site. In both cases, O-RU and O-DU communicate to each other by the Fronthaul interfaces via the Cell Site Router (CSR), which is located at the cell site and is considered as part of access transport network, as shown in Figure 8-4 - -![Diagram of C-RAN architecture with collocated O-RU and O-DU. The diagram shows three main locations: Cell site, C-RAN Hub, and Core. At the Cell site, there are O-DU and O-RU units connected to a Cell Site Router (CSR). The O-RU is connected to the CSR via a 7.2x split eCPRI interface. The O-DU is connected to the CSR via an F1 interface. The CSR is part of the Access network. The Access network connects to the C-RAN Hub via a Midhaul interface. At the C-RAN Hub, there is an O-CU unit connected to the Midhaul. The O-CU is connected to the Core via an N2/N3 Backhaul interface. The Core is part of the Aggregation network. The Aggregation network connects to the CSR via an Xn interface. A legend at the bottom indicates: Fronthaul (red dashed line), Midhaul (orange dashed line), and Backhaul (green dashed line).](34b047489058d6400b412cd0ae2334ba_img.jpg) - -Diagram of C-RAN architecture with collocated O-RU and O-DU. The diagram shows three main locations: Cell site, C-RAN Hub, and Core. At the Cell site, there are O-DU and O-RU units connected to a Cell Site Router (CSR). The O-RU is connected to the CSR via a 7.2x split eCPRI interface. The O-DU is connected to the CSR via an F1 interface. The CSR is part of the Access network. The Access network connects to the C-RAN Hub via a Midhaul interface. At the C-RAN Hub, there is an O-CU unit connected to the Midhaul. The O-CU is connected to the Core via an N2/N3 Backhaul interface. The Core is part of the Aggregation network. The Aggregation network connects to the CSR via an Xn interface. A legend at the bottom indicates: Fronthaul (red dashed line), Midhaul (orange dashed line), and Backhaul (green dashed line). - -**Figure 8-4: Scenario 2 – C-RAN architecture with collocated O-RU and O-DU** - -NOTE: In this scenario the location of the CSR, O-DU and O-RU relative to each other may be close or in some scenarios more distant. For example, within a stadium environment, the O-DU could be centralised and the O-RUs distributed around the stadium. In all cases consideration needs to be given to the low latency requirements associated with the Fronthaul interfaces. - -## 8.3 Scenario 3: C-RAN architecture with coexistence of legacy Backhaul traffic - -This scenario is an extension of Scenario 1, or Scenario 2, where 3G / 4G D-RAN deployments coexist with a 5G C-RAN deployment. The access transport network thus carries the Backhaul traffic from LTE (S1) or 3G UMTS (Iu/lub) in addition to the Fronthaul traffic from Scenario 1, or Midhaul traffic from Scenario 2, as illustrated in Figure 8-5 and Figure 8-6 respectively. - -The aggregation transport network is responsible for carrying the Backhaul traffic for both new and legacy mobile services. - -![O-RAN ALLIANCE logo](156f69727798ad3823fa3a908c455101_img.jpg) - -O-RAN ALLIANCE logo - -![Figure 8-5: Scenario 3a – 7.2x interface combined with legacy Backhaul at access layer. This diagram shows a network architecture where a Cell site with an O-RU connects via a 7.2x split to an eCPRI interface. This interface connects to an Access network cloud, which is also connected to an LTE/UMTS RRH+BBU via an S1/lu interface. The Access network connects to a C-RAN Hub containing an O-DU and an O-CU, linked by an F1 interface. The O-CU connects to the Core (5GC) via an N2/N3 interface. The O-DU connects to the Access network via a Midhaul (F1) interface. The Access network also connects to an Aggregation network cloud, which is connected to an EPC / 3G core via an S1/lu interface. The Aggregation network connects to the Core (5GC) via an N2/N3 interface. The legend indicates: Red dashed line for Fronthaul, Orange dashed line for Midhaul, and Green dashed line for Backhaul.](1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg) - -Figure 8-5: Scenario 3a – 7.2x interface combined with legacy Backhaul at access layer. This diagram shows a network architecture where a Cell site with an O-RU connects via a 7.2x split to an eCPRI interface. This interface connects to an Access network cloud, which is also connected to an LTE/UMTS RRH+BBU via an S1/lu interface. The Access network connects to a C-RAN Hub containing an O-DU and an O-CU, linked by an F1 interface. The O-CU connects to the Core (5GC) via an N2/N3 interface. The O-DU connects to the Access network via a Midhaul (F1) interface. The Access network also connects to an Aggregation network cloud, which is connected to an EPC / 3G core via an S1/lu interface. The Aggregation network connects to the Core (5GC) via an N2/N3 interface. The legend indicates: Red dashed line for Fronthaul, Orange dashed line for Midhaul, and Green dashed line for Backhaul. - -1 -2 -3 -4 -5 -6 -7 - -Figure 8-5 Scenario 3a – 7.2x interface combined with legacy Backhaul at access layer - -![Figure 8-6: Scenario 3b – Midhaul combined legacy Backhaul at access layer. This diagram shows a network architecture where a Cell site with an O-DU and an O-RU connects via an F1 interface to an Access network cloud. The O-RU also connects to the Access network via a 7.2x split. The Access network is also connected to an LTE/UMTS RRH+BBU via an S1/lu interface. The Access network connects to a C-RAN Hub containing an O-CU, which connects to the Core (5GC) via an N2/N3 interface. The O-DU connects to the Access network via a Midhaul (F1) interface. The Access network also connects to an Aggregation network cloud, which is connected to an EPC / 3G core via an S1/lu interface. The Aggregation network connects to the Core (5GC) via an N2/N3 interface. The legend indicates: Red dashed line for Fronthaul, Orange dashed line for Midhaul, and Green dashed line for Backhaul.](e05122559f56af5699789b7118d8fe87_img.jpg) - -Figure 8-6: Scenario 3b – Midhaul combined legacy Backhaul at access layer. This diagram shows a network architecture where a Cell site with an O-DU and an O-RU connects via an F1 interface to an Access network cloud. The O-RU also connects to the Access network via a 7.2x split. The Access network is also connected to an LTE/UMTS RRH+BBU via an S1/lu interface. The Access network connects to a C-RAN Hub containing an O-CU, which connects to the Core (5GC) via an N2/N3 interface. The O-DU connects to the Access network via a Midhaul (F1) interface. The Access network also connects to an Aggregation network cloud, which is connected to an EPC / 3G core via an S1/lu interface. The Aggregation network connects to the Core (5GC) via an N2/N3 interface. The legend indicates: Red dashed line for Fronthaul, Orange dashed line for Midhaul, and Green dashed line for Backhaul. - -8 -9 -10 -11 -12 - -Figure 8-6: Scenario 3b – Midhaul combined legacy Backhaul at access layer - -These mixed D-RAN and C-RAN scenarios are important for the brown field deployment. - -13 -14 - -## 8.4 Scenario 4: C-RAN architecture with coexistence of legacy Fronthaul traffic - -15 -16 -17 -18 -19 -20 - -In this scenario, shown in Figure 8-7, both the 4G and 5G networks utilise a C-RAN Fronthaul deployment in the access transport network. In this scenario it is assumed the 4G radio infrastructure consists of RRHs communicating with their serving BBU using CPRI. To migrate these services to a packet based Fronthaul, the native CPRI is converted to packets as it enters the packet infrastructure and converted from packets back to native CPRI as it egresses the packet infrastructure. This scenario assumes the CPRI to packet conversion function is performed by an - -![O-RAN Alliance logo](023d970f080d18a5ec7578ebb73205b4_img.jpg) - -O-RAN Alliance logo - -RoE Mapper using the IEEE 1914.3 standard [40]. The RoE mapper is out of scope of this specification. The impact on the access transport network is it carries 7.2x and RoE fronthaul traffic. - -In the Backhaul network, S1 from LTE is transported together with NR Backhaul N2/N3. - -![Figure 8-7: Scenario 4 – C-RAN architecture with coexistence of legacy Fronthaul traffic](ddee3e67e0dfc22e25188fa635a19558_img.jpg) - -The diagram illustrates Scenario 4, showing the coexistence of legacy and O-RAN traffic. -- \*\*Cell site\*\*: Contains an O-RU and an LTE RRH. The O-RU connects via eCPRI (red dashed line) to an Access network cloud. The LTE RRH connects to a RoE Mapper, which then connects via CPRI (red dashed line) to the same Access network cloud. -- \*\*Access Network\*\*: A cloud containing three interconnected switches/routers. -- \*\*C-RAN Hub\*\*: Contains an O-DU, an O-CU, and an LTE BBU. The O-DU connects to the Access network via F1 (orange dashed line). The LTE BBU connects to the Access network via a RoE Mapper. -- \*\*Aggregation Network\*\*: A cloud containing four interconnected switches/routers. It receives traffic from the C-RAN Hub (S1, N2/N3) and connects to the Core. -- \*\*Core\*\*: Contains 5GC and EPC. Connections include N2/N3 (green dashed line) to 5GC, and S1, X2, and Xn (green dashed lines) to EPC. -- \*\*Legend\*\*: Red dashed line = Fronthaul; Orange dashed line = Midhaul; Green dashed line = Backhaul. - -Figure 8-7: Scenario 4 – C-RAN architecture with coexistence of legacy Fronthaul traffic - -**Figure 8-7: Scenario 4 – C-RAN architecture with coexistence of legacy Fronthaul traffic** - -This scenario is important to support migration plan from 4G to 5G, such as the NSA architecture. - -## 8.5 Scenario 5: C-RAN architecture with further split of O-DU and O-CU - -This is a C-RAN architecture with two RAN splits with the O-RUs, O-DUs, and O-CUs hosted at separate locations. The O-DU is placed at C-RAN Hub site closer to the cell sites for shorter latency and the O-CU is more centralized at a different location as shown in Figure 8-8. The Midhaul traffic, identified as F1 from the 3GPP option 2 split, is carried by an addition transport network segment (pre-aggregation transport network) that connects the two hub sites. Similar to other use cases, the Backhaul traffic is transported by the aggregation transport network. - -![Figure 8-8: Scenario 5 – Dual split C-RAN architecture](0908107b858fa3783d10d93b3a3444b2_img.jpg) - -The diagram illustrates Scenario 5, showing a dual-split architecture across multiple sites. -- \*\*Cell site\*\*: Contains an O-RU, which connects via eCPRI (red dashed line) to an Access network cloud. -- \*\*Access Network\*\*: A cloud with two switches/routers connecting the Cell site to C-RAN Hub 1. -- \*\*C-RAN Hub 1\*\*: Contains an O-DU. It connects to the Access network (Fronthaul) and to a Pre-aggregation network via F1 (orange dashed line). -- \*\*Pre-aggregation Network\*\*: A cloud with two switches/routers connecting C-RAN Hub 1 to C-RAN Hub 2. -- \*\*C-RAN Hub 2\*\*: Contains an O-CU. It connects to the Pre-aggregation network (Midhaul) and to an Aggregation network via N2/N3 and Xn (green dashed lines). -- \*\*Aggregation Network\*\*: A cloud with three switches/routers connecting C-RAN Hub 2 to the Core. -- \*\*Core\*\*: Contains 5GC, receiving N2/N3 and Xn traffic (Backhaul). -- \*\*Legend\*\*: Red dashed line = Fronthaul; Orange dashed line = Midhaul; Green dashed line = Backhaul. - -Figure 8-8: Scenario 5 – Dual split C-RAN architecture - -**Figure 8-8: Scenario 5 – Dual split C-RAN architecture** - -![O-RAN Alliance logo](87538011bcfcd46e392fe6278cb18ead_img.jpg) - -O-RAN Alliance logo - -## 8.6 Scenario 6: C-RAN architecture with local breakout - -In supporting URLLC to reduce the data plane latency, or fixed wireless application to offload large amounts of user data locally, the User Plane Function (UPF) breakouts before the aggregation network. In this case the aggregation network only carries the control plane traffic N2 (Figure 8-9). - -![Diagram of C-RAN architecture with local user plane breakout. The diagram shows a Cell site with an O-RU connected via eCPRI (Fronthaul) to an Access network. The Access network connects to a C-RAN Hub containing an O-DU and an O-CU via F1 (Midhaul). The O-CU connects to a Core network (5GC AMF/SMF) via N2/N3 (Backhaul). The O-CU also connects to an Aggregation network via N2 (Backhaul). The Aggregation network connects to a UPF via N3 (Backhaul). The UPF is connected to the Aggregation network via Xn (Backhaul). The legend indicates: Fronthaul (red dashed line), Midhaul (orange dashed line), and Backhaul (green dashed line).](cf8bd014a50b7c69435e804f67f9617f_img.jpg) - -Diagram of C-RAN architecture with local user plane breakout. The diagram shows a Cell site with an O-RU connected via eCPRI (Fronthaul) to an Access network. The Access network connects to a C-RAN Hub containing an O-DU and an O-CU via F1 (Midhaul). The O-CU connects to a Core network (5GC AMF/SMF) via N2/N3 (Backhaul). The O-CU also connects to an Aggregation network via N2 (Backhaul). The Aggregation network connects to a UPF via N3 (Backhaul). The UPF is connected to the Aggregation network via Xn (Backhaul). The legend indicates: Fronthaul (red dashed line), Midhaul (orange dashed line), and Backhaul (green dashed line). - -Figure 8-9: Scenario 6 – C-RAN architecture with local user plane breakout - -## 8.7 Scenario 7: Transport slicing - -An O-RAN wide initiative to develop end-to-end O-RAN slicing solutions has started, led by WG-1. The architecture and phasing are defined in O-RAN.WG1.Slicing-Architecture-v07.00 [25] and is based on operator use cases and the slicing capability of the O-RAN components. This operator scenario will now track the phasing and slicing use cases developed by WG-1. - -Revision 2 of this document now includes Annex F: Transport network slicing solution for WG1 Slicing (informational), which define an example transport solution for slice phase 1 contained in O-RAN.WG1.Slicing-Architecture-v07.00 [25]. - -From the operator use case given in previous subsection, it is observed that the transport network, especially the access transport network, may experience all types of transport flows simultaneously when operators have the need to engage mixed use cases in their deployment. Possible transport service range widely with: - -- Fronthaul, Midhaul, and Backhaul -- NR, legacy LTE and legacy UMTS -- Control plan, User plane, and Management plane -- To support transport operation for different operators -- To support different types of end-to-end services or applications (such as URLLC and eMBB) - -Each of them may be multiplexed into a commonly shared transport network with largely different transport requirements, which include latency, throughput, transmission reliability. - -To reduce complexity and manage network resource more efficiently, these transport flows can be classified into transport slices according to common service requirements. One example is shown in Table 1. - -![O-RAN Alliance logo](acf9eb2c446cfb72d7cb44a9149e24aa_img.jpg) - -O-RAN Alliance logo - -1 -2 - -| Transport Slices | Description | Transport flows | Transport BW | Transport timing sensitivity | Transport reliability | -|------------------|--------------------------------------------------------|---------------------------------------------------|--------------|------------------------------|-----------------------| -| TS 1 | Fronthaul | 7.2x CUS-plane, RoE | High | High | High | -| TS 2_1 | Data plane for Backhaul of URLLC service of Operator A | F1-U, S1-U, N3, X2/Xn-U | Medium | High | High | -| TS 2_2 | Data plane for Midhaul, Backhaul of Operator B | F1-U, S1-U, N3, X2/Xn-U | Medium | Medium | High | -| TS 3 | Control plane for Midhaul, Backhaul, Management plane | 7.2x M-Plane, F1-C, S1-C, N2, X2/Xn-C, Management | Low | Low | Low | - -3 -4 -5 -**Table 1 Transport slicing example** - -6 -7 -8 -The above transport slice may further split into more sub-slices if necessary, for different end-to-end user applications or different operators depending on separate needs of the priority, latency, or bandwidth. - -9 -10 -These transport slices are designed to meet the objectives: - -- 11 -12 -13 -• Provide the transport elements to support network slicing. As part of network sub-network instances, the transport network interfaces with other network segments by the transport slices. -- 14 -15 -• Allow flexible configuration to efficiently support adding/deleting/reconfiguring slices and services -- 16 -• Support protection/isolation/prioritization mechanisms to minimize inter-slice effects -- 17 -• Support monitoring/reporting the slice KPIs - -18 -19 -20 -21 -22 -23 -24 -25 -With reference to the network slicing use cases described in WG1 network slicing specification document [25], Figure 8-10 presents a transport realization example in supporting the phase 1 scope summarized in *Annex F: Transport network slicing solution for WG1 Slicing (informational)*. This is based on the dual split transport architecture (scenario 5) combined with scenario 3b described in previous sections. The purpose of this example is to illustrate a practical scenario of traffic distribution in a slicing transport network. - -![O-RAN Alliance logo](b73e15bd8ab2756cf10f9344fe551227_img.jpg) - -O-RAN Alliance logo - -![Figure 8-10: Scenario 7 – Transport based on dual split architecture. The diagram shows a network architecture with four main components: Cell Site, DU hub, CU hub, and Core. The Cell Site contains High band (O-DU, O-RU), Low band (O-RU), and LTE (BBU) connected to a CSR (Cell Site Router). The DU hub contains multiple O-DUs connected to an HSR (Hub Site Router). The CU hub contains multiple O-CUs connected to an Agg-HSR (Aggregation Hub Site Router). The Core contains mMTc/NB-IoT (UPF) and eMBB (UPF, SMO OAM) connected to a Core-HSR (Core Hub Site Router). The transport network is divided into three segments: Access (between Cell Site and DU hub), Pre-Aggregation (between DU hub and CU hub), and Aggregation (between CU hub and Core). The Access segment includes HSR-F (Fronthaul Hub Site Router) and HSR (Midhaul Hub Site Router). The Pre-Aggregation segment includes HSR-M (Midhaul Hub Site Router). The Aggregation segment includes HSR-B (Backhaul Hub Site Router). The diagram also shows connections to 'Other cell sites', 'Other C-RAN hubs', and 'Other C-RAN hubs'.](e22af684d8e56d4c61e61bb5ddac1087_img.jpg) - -Figure 8-10: Scenario 7 – Transport based on dual split architecture. The diagram shows a network architecture with four main components: Cell Site, DU hub, CU hub, and Core. The Cell Site contains High band (O-DU, O-RU), Low band (O-RU), and LTE (BBU) connected to a CSR (Cell Site Router). The DU hub contains multiple O-DUs connected to an HSR (Hub Site Router). The CU hub contains multiple O-CUs connected to an Agg-HSR (Aggregation Hub Site Router). The Core contains mMTc/NB-IoT (UPF) and eMBB (UPF, SMO OAM) connected to a Core-HSR (Core Hub Site Router). The transport network is divided into three segments: Access (between Cell Site and DU hub), Pre-Aggregation (between DU hub and CU hub), and Aggregation (between CU hub and Core). The Access segment includes HSR-F (Fronthaul Hub Site Router) and HSR (Midhaul Hub Site Router). The Pre-Aggregation segment includes HSR-M (Midhaul Hub Site Router). The Aggregation segment includes HSR-B (Backhaul Hub Site Router). The diagram also shows connections to 'Other cell sites', 'Other C-RAN hubs', and 'Other C-RAN hubs'. - -Figure 8-10: Scenario 7 – Transport based on dual split architecture - -The TNEs in the figure are defined as follows: - -- CSR: Cell Site Router, aggregating traffics from collocated O-RUs -- HSR: Hub Site Router, aggregating traffics from multiple cell sites -- HSR-F: Hub Site Router that distribute fronthaul traffics to O-DUs -- HSR-B/M: Hub Site Router that aggregate Backhaul or Midhaul traffics -- Agg-HSR: Hub Site Router at centralized O-CU site that aggregate the traffic from multiple O-DU hub sites -- Core-HSR: Hub Site Router at Core site that aggregate traffic from multiple O-CU hub sites - -The logical link across the Access transport network between cell site and C-RAN hub is seen with complex traffic types: fronthaul, midhaul, and backhaul are mixed. Specifically, following traffic flows are jointly transported cross the transport: - -UP: 7.2x C/U-P, S1-U, F1-U, X2/Xn-U - -CP: S1-C, F1-C, X2/Xn-C - -MP: 7.2x M-P, O1, E2 - -At the Pre-aggregation transport network, there is no presence of the fronthaul anymore. Those traffics are merged and carried by the network - -UP: S1-U, F1-U, X2/Xn-U - -CP: S1-C, F1-C, X2/Xn-C - -MP: O1, E2 - -At the aggregation transport network, only backhaul traffic are distributed to UPFs that may be geographically separated for eMBB and mMTC/NB-IoT: - -UP: N3, N9, S1-U - -CP: N2, S1-C - -MP: O1, E2 - -The transport solutions provided in this specification, as described in section 18 and *Annex F: Transport network slicing solution for WG1 Slicing (informational)* are expected to provide adequate toolbox to achieve prioritization, isolation, QoS, and configuration objectives in managing the above transport scenarios. - -## 8.8 Scenario 8/9: C-RAN architecture with co-located O-DUs - -In this scenario both the O-DUs supporting D2 interface are deployed at cell site and O-CU is located at cell Hub. By 3GPP standard, the O-DU and O-CU are split by the functional split option 2 and connected with F1 interface, which is transported by the access transport network that connects the cell site and the Hub site. The aggregation transport network carries the N2/N3 Backhaul traffic to the 5G core. - -O-DUs may be collocated or be in close proximity around the cell site. In both cases, O-DUs communicate with each other by the D2 via either a direct fiber connection as shown in Figure 8-11, or as shown in Figure 8-12 through the Cell Site Router (CSR), or other TNE, which are located at the cell site and is considered as part of access transport network. - -![Figure 8-11: Scenario 8 – C-RAN architecture with Co-located O-DUs connected via direct Fiber. The diagram shows a Cell Site with O-DU1, O-DU2, O-RU1, and O-RU2 connected to a CSR. The CSR is connected to a C-RAN Hub via an F1 interface. The C-RAN Hub is connected to a Core via an N2/N3 interface. The CSR is also connected to an Aggregation network via an Xn interface. The Aggregation network is connected to the Core via an SGC. The legend indicates: D2 (blue dashed line), Fronthaul (red dashed line), Midhaul (yellow dashed line), and Backhaul (green dashed line).](69e5f1993021af230d08c08aac97d9df_img.jpg) - -Figure 8-11: Scenario 8 – C-RAN architecture with Co-located O-DUs connected via direct Fiber. The diagram shows a Cell Site with O-DU1, O-DU2, O-RU1, and O-RU2 connected to a CSR. The CSR is connected to a C-RAN Hub via an F1 interface. The C-RAN Hub is connected to a Core via an N2/N3 interface. The CSR is also connected to an Aggregation network via an Xn interface. The Aggregation network is connected to the Core via an SGC. The legend indicates: D2 (blue dashed line), Fronthaul (red dashed line), Midhaul (yellow dashed line), and Backhaul (green dashed line). - -Figure 8-11: Scenario 8 – C-RAN architecture with Co-located O-DUs connected via direct Fiber - -![Figure 8-12: Scenario 9 – C-RAN architecture with Co-located O-DUs connected via CSR. This diagram is identical to Figure 8-11, showing the same network components and interfaces, but the O-DUs are connected to the CSR via direct fiber connections instead of through a separate D2 interface.](052543d8c9c0643b05b3ce45c6decca1_img.jpg) - -Figure 8-12: Scenario 9 – C-RAN architecture with Co-located O-DUs connected via CSR. This diagram is identical to Figure 8-11, showing the same network components and interfaces, but the O-DUs are connected to the CSR via direct fiber connections instead of through a separate D2 interface. - -Figure 8-12: Scenario 9 – C-RAN architecture with Co-located O-DUs connected via CSR - -![O-RAN Alliance logo](d952d1b71abf550d8d9740581f6e7e02_img.jpg) - -O-RAN Alliance logo - -## 8.9 Scenario 10: C-RAN architecture with non co-located O-DUs - -In this scenario as shown in Figure 8-13, one of the O-DU supporting D2 interface is deployed at cell site while other one is at cell Hub with O-CU. O-DU1 and O-DU2 are connected with different O-RUs, configured with the carriers that can be used to provide inter O-DU CA. By 3GPP standard, the O-DU and O-CU is split by the functional split option 2 and connected with F1 interface, which is transported by the access transport network that connects the cell site and the Hub site. The aggregation transport network carries the N2/N3 Backhaul traffic to the 5G core. - -![Diagram of C-RAN architecture with non co-located O-DUs. The diagram shows three main locations: Cell Site, C-RAN Hub, and Core. At the Cell Site, O-DU1 and O-RU1 are connected via a D2 interface (blue dashed line). O-DU1 is also connected to O-RU2 via a Fronthaul interface (red dashed line). O-RU2 is connected to the C-RAN Hub via an F1 interface (yellow dashed line). At the C-RAN Hub, O-DU2 and O-CU are connected via an F1 interface (yellow dashed line). O-DU2 is connected to the C-RAN Hub via a Midhaul interface (yellow dashed line). The C-RAN Hub is connected to the Core via an Aggregation network. The Aggregation network is connected to the 5G Core (SGC) via an N2/N3 Backhaul interface (green dashed line). The Aggregation network is also connected to the C-RAN Hub via an Xn interface (green dashed line). The legend indicates: D2 (blue dashed line), Fronthaul (red dashed line), Midhaul (yellow dashed line), and Backhaul (green dashed line).](7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg) - -Diagram of C-RAN architecture with non co-located O-DUs. The diagram shows three main locations: Cell Site, C-RAN Hub, and Core. At the Cell Site, O-DU1 and O-RU1 are connected via a D2 interface (blue dashed line). O-DU1 is also connected to O-RU2 via a Fronthaul interface (red dashed line). O-RU2 is connected to the C-RAN Hub via an F1 interface (yellow dashed line). At the C-RAN Hub, O-DU2 and O-CU are connected via an F1 interface (yellow dashed line). O-DU2 is connected to the C-RAN Hub via a Midhaul interface (yellow dashed line). The C-RAN Hub is connected to the Core via an Aggregation network. The Aggregation network is connected to the 5G Core (SGC) via an N2/N3 Backhaul interface (green dashed line). The Aggregation network is also connected to the C-RAN Hub via an Xn interface (green dashed line). The legend indicates: D2 (blue dashed line), Fronthaul (red dashed line), Midhaul (yellow dashed line), and Backhaul (green dashed line). - -8 -9 - -Figure 8-13: Scenario 10 – C-RAN architecture with non co-located O-DUs - -## 9 Overall packet switched Open Xhaul architecture - -There are different ways packet switching could be deployed to support an Open Xhaul architecture. Factors include: - -- Span of the packet switching components. Packet switching could be deployed from cell site to the transport core or mixed with other technologies, for example WDM in access, to form the end-to-end network. -- The nature of the underlying L0/L1 transport used by the packet switching equipment. -- The network protocols used at the packet switching layer. -- How Xhaul services are built on the Xhaul infrastructure. - -### 9.1 Physical layout and xHaul transport options - -A simple model illustrated in Figure 9-1 relies on an end-to-end packet-based transport architecture that builds on a physical network. In this model, Fronthaul, D2 transport, Midhaul and Backhaul deploy packet-based transport technologies. The diagram represents a logical view of the network. The physical network implementation might be different. For example, an O-DU might be connected to a single TNE port but deliver two logical connections to a second TNE in Fronthaul network, and a third TNE in Midhaul network. - -![Figure 9-1: Packet based architecture in front-, mid- and Backhaul networks. This diagram shows a logical network topology. At the top, an O-RU1 is connected via a 7-2x interface to a TNE, which is part of the Fronthaul network. This TNE connects to another TNE, which in turn connects to an O-DU1. O-DU1 has two logical connections: one to a TNE in the Fronthaul network and another to a TNE in the D2 transport network. The D2 TNE connects to another TNE, which is part of the Midhaul network. The Midhaul TNE connects to an O-CU. The O-CU connects to a TNE in the Backhaul network (labeled N2,N3), which finally connects to a 5GC/EPC cloud. Below the logical components, two horizontal arrows represent the network layers: an orange arrow for the 'Packet Switched Network: Ethernet, MPLS, IP' and a red arrow for the 'Physical Network: xWDM, PON, Wireless, DOCSIS'.](a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg) - -Figure 9-1: Packet based architecture in front-, mid- and Backhaul networks. This diagram shows a logical network topology. At the top, an O-RU1 is connected via a 7-2x interface to a TNE, which is part of the Fronthaul network. This TNE connects to another TNE, which in turn connects to an O-DU1. O-DU1 has two logical connections: one to a TNE in the Fronthaul network and another to a TNE in the D2 transport network. The D2 TNE connects to another TNE, which is part of the Midhaul network. The Midhaul TNE connects to an O-CU. The O-CU connects to a TNE in the Backhaul network (labeled N2,N3), which finally connects to a 5GC/EPC cloud. Below the logical components, two horizontal arrows represent the network layers: an orange arrow for the 'Packet Switched Network: Ethernet, MPLS, IP' and a red arrow for the 'Physical Network: xWDM, PON, Wireless, DOCSIS'. - -**Figure 9-1 Packet based architecture in front-, mid- and Backhaul networks** - -Unlike the previous architecture some operators may decide to use the packet-based technology only in Mid- and Backhaul, and use simple physical networking to connect the O-DU ports with O-RUs (Figure 9-2). In this case the physical network between the O-RUs and O-DUs could - in the simplest case - be dark fiber links. The next choice in terms of simplicity can be a passive WDM system. - -![Figure 9-2: Packet based architecture in mid and Backhaul networks. This diagram shows a logical network topology similar to Figure 9-1, but with a key difference in the Fronthaul section. An O-RU is connected via a 7-2x interface to a TNE, which connects to another TNE. This second TNE connects directly to an O-DU. The O-DU then connects to a TNE in the Midhaul network (labeled F1), which connects to an O-CU. The O-CU connects to a TNE in the Backhaul network (labeled N2,N3), which connects to a 5GC/EPC cloud. Below the logical components, two horizontal arrows represent the network layers: an orange arrow for the 'Packet Switched Network: Ethernet, MPLS, IP' and a red arrow for the 'Physical Network: xWDM, PON, Wireless, DOCSIS'. The packet-switched network layer is shown only for the Midhaul and Backhaul sections, while the Fronthaul section is represented by the physical network layer.](1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg) - -Figure 9-2: Packet based architecture in mid and Backhaul networks. This diagram shows a logical network topology similar to Figure 9-1, but with a key difference in the Fronthaul section. An O-RU is connected via a 7-2x interface to a TNE, which connects to another TNE. This second TNE connects directly to an O-DU. The O-DU then connects to a TNE in the Midhaul network (labeled F1), which connects to an O-CU. The O-CU connects to a TNE in the Backhaul network (labeled N2,N3), which connects to a 5GC/EPC cloud. Below the logical components, two horizontal arrows represent the network layers: an orange arrow for the 'Packet Switched Network: Ethernet, MPLS, IP' and a red arrow for the 'Physical Network: xWDM, PON, Wireless, DOCSIS'. The packet-switched network layer is shown only for the Midhaul and Backhaul sections, while the Fronthaul section is represented by the physical network layer. - -**Figure 9-2: Packet based architecture in mid and Backhaul networks** - -![O-RAN Alliance logo](3eddc247052fc64b4d863672db9fa2b0_img.jpg) - -O-RAN Alliance logo - -Another architectural variant (Figure 9-3) can be designed by inserting TDM based layer 1 transport technologies between the packet-based and physical networks. OTN and SPN/G.mtn are two choices that allow for aggregation and transparent transport of larger traffic volumes, and design of hard slicing architectures. In this architecture, the OTN or SPN/G.mtn infrastructure must present Ethernet clients at UNI-C/UNI-N interfaces to the packet switched network. The clients need to be transparent and operate at full Ethernet line rates, because the packet switched network elements are responsible for QoS and need to rely on client signals with proper bandwidth. - -![Figure 9-3: Use of TDM based technologies with Ethernet presentation in Xhaul networks. The diagram shows a sequence of components: O-RU, TNE, Fronthaul eCPRI (7.2x), TNE, O-DU, TNE, Midhaul F1, TNE, O-CU, TNE, Backhaul N2,N3, TNE, and 5GC. Below this, a packet switched network layer is shown, with OTN, SPN, and Physical Network (xWDM, PON, Wireless, DOCSIS) layers indicated.](3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg) - -Figure 9-3: Use of TDM based technologies with Ethernet presentation in Xhaul networks. The diagram shows a sequence of components: O-RU, TNE, Fronthaul eCPRI (7.2x), TNE, O-DU, TNE, Midhaul F1, TNE, O-CU, TNE, Backhaul N2,N3, TNE, and 5GC. Below this, a packet switched network layer is shown, with OTN, SPN, and Physical Network (xWDM, PON, Wireless, DOCSIS) layers indicated. - -Figure 9-3 Use of TDM based technologies with Ethernet presentation in Xhaul networks - -In cases where there are underlying L0/L1 transport solutions, the synchronization and timing flows must not be impaired by these layers, as any impairment will impact the synchronization function of the packet switched network, and the overall synchronization performance of the end-to-end system. - -## 9.2 Open Xhaul architecture in revision 1 and 2 - -Revision 1,2 and 3 of this document describes a packet switched transport architecture illustrated in Figure 9-4. - -![Figure 9-4: Packet switched transport for mobile Xhaul. The diagram shows a layered architecture: Transport SDN / Orchestration and Telemetry (top), Mobile Services: MP-BGP EVPN and L3VPN, Underlay transport fabric: MPLS or SRv6, QoS, timing. Below this, the network consists of Access, Pre-Agg, Aggregation, and Transport Core nodes, connected by Dark fibre / WDM and Dark fibre / switched WDM. External connections include Peering and Cloud.](5c3dd31372f59e15250f0ab1613ca485_img.jpg) - -Figure 9-4: Packet switched transport for mobile Xhaul. The diagram shows a layered architecture: Transport SDN / Orchestration and Telemetry (top), Mobile Services: MP-BGP EVPN and L3VPN, Underlay transport fabric: MPLS or SRv6, QoS, timing. Below this, the network consists of Access, Pre-Agg, Aggregation, and Transport Core nodes, connected by Dark fibre / WDM and Dark fibre / switched WDM. External connections include Peering and Cloud. - -Figure 9-4 Packet switched transport for mobile Xhaul - -It is a converged end to end packet switched infrastructure, beginning at the cell site, located in the edge of the access layer and stretching to the core of the transport layer. The packet switching TNEs are QoS enabled, high capacity, low latency devices interconnected by point-to-point Ethernet interfaces running at the full capacity of the Ethernet interface, typically using either point to point - -![O-RAN Alliance logo](b87b52c04ccb835fa90fd2c6926f224d_img.jpg) - -The logo for the O-RAN Alliance, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with the word "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -fibres or via a WDM infrastructure. It incorporates data centers suitably placed across the transport network infrastructure to support virtual and physical NFs associated with mobile and fixed services but also potentially the placement of “Application Functions” associated with value-add services and customer specific application. - -The logical architecture is based on a common underlay packet switching infrastructure based on either MPLS or SRv6 overlaid with a L2 / L3 service infrastructure (VPNs) that uses the capabilities of the underlay packet switched network to support the mobiles interfaces. - -The underlay packet switching infrastructure provides basic network services such as; any-to-any connectivity between TNEs, scaling, fast convergence, shortest path and traffic engineered forwarding, packet-based Quality of Service (QoS) and timing. - -The service layer supports native Ethernet services, using EVPN technology and IP VPN services, using MP-BGP based L3VPNs. These services can utilise the facilities offered by the underlay packet switched infrastructure to support the different mobile interfaces in an appropriate fashion. Where possible transport services are built on an end-to-end basis without intermediate stitching / switching points within the transport infrastructure. This approach has been taken to minimise the transport service orchestration overhead. - -### 9.3 Technology and architectural choices - -As discussed in the introduction to this section there are other packet-switched solutions and potentially many design approaches available that may have the same capabilities of the architecture described in this revision of the document. Future versions of this document may describe alternative technologies and designs based on operator requirements and suitably mature standards. - -### 9.4 Standardization - -The underlay packet-switching technologies described in this document are based on MPLS and IPv6 with an emphasis on the Segment Routing (SR) control and data planes. The overlay service layer uses EVPN and MP-BGP L3VPNs. The IETF is the primary standardization body for these technologies. The key specification of the IETF is the “Request For Comments” (RFC). RFCs are labelled with different statuses: Internet Standard, Proposed Standard, Best Current Practice, Experimental, Informational, and Historic. RFCs usually begin as Internet-Drafts written by Individuals, or a small group and are known as individual drafts. Depending on interest an individual draft can be adopted by an IETF Work Group (WG) where it is improved and revised by a wider group and can ultimately become an RFC. This process is well defined by the IETF, with guides and considerations for the progression of a document. If the process completes, then the document is published as an RFC by the IETF RFC Editor. If a document does not follow the process or doesn’t meet the guidelines outlined, then the drafts will expire and never become an RFC. Depending on subject matter the process of moving from an WG adopted draft to an RFC can several years. - -To present architectures suitable for 5G, based on modern packet-switching technologies, Standards, proposed standards, best current practise and informational RFCs and current workgroup adopted drafts with the same designations can be referenced in this document. All experimental and historic RFCs and workgroup adopted drafts and all forms of personal drafts MUST NOT be - -![O-RAN Alliance logo](c002a785d5d05bd7f69d54a01401fd86_img.jpg) - -The logo for the O-RAN Alliance, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -referenced. When writing requirements around these different types of documents consideration should be given to document type and their status. - -Future revisions of this document MUST be updated to reflect the status of IETF drafts which are referenced. If they expire, they MUST be removed and if they complete the IETF standardization process, references and requirements MUST be updated to remove the IETF draft and include the appropriate RFC number. - -## 9.5 Document organization - -The remainder of this document describes the physical and logical architecture of a packet switching Xhaul architecture and how it can support 5G and legacy mobile services. It is arranged as follows: - -**Section 10** describes the end-to-end physical network infrastructure. - -**Sections 11 and 12** describes two underlay packet switching architectures capable of supporting a 5G mobile environment. The first is based on MPLS, the second IPv6 with Segment Routing (SRv6). Depending on scale and preference, operators will need to select one or the other. - -**Section 13** describes how IP and Ethernet services suitable for 5G are delivered on a packet switched Xhaul network. The approach is common regardless of the underlay technology deployed. - -**Section 14** describes the QoS architecture for a packet switched Xhaul network. - -**Section 15** describes multicast and consideration for deployment. - -**Section 16** covers packet-switched orchestration and telemetry. Currently it is empty and will be completed in a later revision of this document or in a separate document. - -**Section 17** covers TNE and transport network security. - -**Section 18 and 19** describes how the packet switched Xhaul architecture supports 5G and legacy mobile use cases outlined in section 8. - ---- - -## 10 Physical network design for packet switched Xhaul - -Figure 10-1 shows two of the most common physical topologies seen in transport networks between the access and the core of the transport network. In the first, there are four layers of transport infrastructure; access, pre-aggregation, aggregation, and transport core. In the second, there are three layers of transport infrastructure; access, aggregation, and transport core. Packet switches are used within each layer and provides connectivity between the layers. - -The way the mobile RAN and core infrastructure is arranged over these different segments varies based on geography and the MNO's RAN and mobile core designs and individual operator's classification of different components in the physical network. It should be noted that in most cases the transport core doesn't form part of the 5G RAN infrastructure, which is restricted to the access - -![O-RAN Alliance logo](3e785accf62f005fb821a0eeb2796bcb_img.jpg) - -O-RAN Alliance logo - -1 and aggregation infrastructure (often called the metro network), but it does play an important role in - 2 scaling and connecting metro infrastructures together to enable end to end services to be built. - 3 - -![Two diagrams showing physical transport components. The top diagram shows a linear flow: Access (green cloud) connected to a Cell Site Router (CSR), then Pre-aggregation (blue cloud) connected to a Hub Site Router (HSR), then Aggregation (red cloud) connected to a 5G Core, which is then connected to the Transport Core. The bottom diagram shows a simplified flow: Access (green cloud) connected to a CSR, then Aggregation (red cloud) connected to a 5G Core, which is then connected to the Transport Core. A legend below the diagrams identifies the CSR and HSR icons.](a0e8fe7862a6d7341faf5dac275277cc_img.jpg) - -Two diagrams showing physical transport components. The top diagram shows a linear flow: Access (green cloud) connected to a Cell Site Router (CSR), then Pre-aggregation (blue cloud) connected to a Hub Site Router (HSR), then Aggregation (red cloud) connected to a 5G Core, which is then connected to the Transport Core. The bottom diagram shows a simplified flow: Access (green cloud) connected to a CSR, then Aggregation (red cloud) connected to a 5G Core, which is then connected to the Transport Core. A legend below the diagrams identifies the CSR and HSR icons. - -4 - 5 **Figure 10-1: Physical transport components** - 6 - -![A hierarchical diagram of a transport network. At the center is a 'Transport Core' cloud. Radiating from it are several 'Aggregation' clouds (red), which in turn connect to multiple 'Access' clouds (green). Each cloud contains various network elements like routers and base stations, represented by icons with antennas and signal waves.](df1966d80c74bc127f159a48f38b13ee_img.jpg) - -A hierarchical diagram of a transport network. At the center is a 'Transport Core' cloud. Radiating from it are several 'Aggregation' clouds (red), which in turn connect to multiple 'Access' clouds (green). Each cloud contains various network elements like routers and base stations, represented by icons with antennas and signal waves. - -7 - 8 **Figure 10-2 Hierarchical designed transport network consisting of access / aggregation and** - 9 **transport core.** - 10 - -11 Figure 10-2 shows an example of a logical transport network consisting of a number of access, - 12 aggregation domains connected hierarchically to form a single transport core domain. From a logical - -![O-RAN Alliance logo](bc0363f46427865273bebd3bbe4dad53_img.jpg) - -The O-RAN Alliance logo, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -1 architecture perspective, the entire infrastructure needs to be considered as a whole, but at the physical -2 layer there are significant differences in these discrete physical segments. These include: - -- 3 -- 4 1. Distances between sites -- 5 2. Layout of the physical media -- 6 3. Technology employed -- 7 4. Environmental conditions -- 8 5. Bandwidth requirements -- 9 6. Cost structures surrounding equipment and real estate. - -## 10.1 Packet over fibre - -12 This document concentrated primarily on a transport infrastructure built using packet over fibre -13 solutions in all physical segments of the network. - -### 10.1.1 Access - -15 A Transport Network Equipment (TNE) – Ethernet switch or IP router – resides in the cell site -16 aggregating traffic received on access ports (downlinks) from end-hosts (O-RUs, or O-DUs, as -17 outlined in Section 8, as well as other types of end-hosts, like for example 4G BBUs, business -18 CPEs, etc. in hybrid deployment models), and statistically multiplexing this traffic onto a higher -19 capacity Ethernet uplink, typically established over a dark fibre or WDM lambda, or any other -20 underlying technology (for example microwave radio link). Link speed will depend on the traffic -21 levels required by the services running in the access network. The anticipated ranges will be from -22 1...50 Gbps (downlink) up to bundles of 100 Gbps (uplink). - -#### 10.1.1.1 Topology - -24 The physical topology employed in the transport access network is operator dependent and driven -25 mainly by the three aspects: - -- 26 • fibre topology, its availability -- 27 • the traffic matrix -- 28 • latency and time error requirements - -30 The main physical architectures anticipated in the transport access are: - -- 31 • ring -- 32 • chain -- 33 • hub and spoke (called as well spine and leaf), with redundant CSR connectivity -- 34 • hub and spoke (called as well spine and leaf), without redundant CSR connectivity - -35 -36 as shown in Figure 10-3, Figure 10-4, Figure 10-5 and Figure 10-6. - -![Ring based access physical topology diagram showing a ring of 8 nodes (6 CSR, 2 HSR) connected to a cloud.](a780a960b3f2de2493d5785bedae10ff_img.jpg) - -A diagram showing a ring-based access physical topology. It consists of a ring of eight nodes: six labeled 'CSR' and two labeled 'HSR'. The nodes are connected in a continuous loop. The two 'HSR' nodes are connected to a cloud-shaped icon on the right, representing a connection to the rest of the network. - -Ring based access physical topology diagram showing a ring of 8 nodes (6 CSR, 2 HSR) connected to a cloud. - -**Figure 10-3: Ring based access physical topology** - -1 -2 -3 - -![Chain based access physical topology diagram showing a linear chain of 5 nodes (4 CSR, 1 HSR) connected to a cloud.](18e519d1f91133e080347562f681dfb5_img.jpg) - -A diagram showing a chain-based access physical topology. It consists of a linear chain of five nodes: four labeled 'CSR' and one labeled 'HSR'. The nodes are connected in a series. The 'HSR' node at the end of the chain is connected to a cloud-shaped icon on the right. - -Chain based access physical topology diagram showing a linear chain of 5 nodes (4 CSR, 1 HSR) connected to a cloud. - -**Figure 10-4 Chain based access physical topology** - -4 -5 -6 - -![Redundant hub and spoke access physical topology diagram showing four CSR nodes connected to two HSR nodes, which are then connected to a cloud.](71b0a68b4dd64961465d2b0e790538de_img.jpg) - -A diagram showing a redundant hub and spoke access physical topology. Four nodes labeled 'CSR' are connected to two nodes labeled 'HSR'. Each 'CSR' node has connections to both 'HSR' nodes. The two 'HSR' nodes are then connected to a cloud-shaped icon on the right, providing redundancy in the path to the cloud. - -Redundant hub and spoke access physical topology diagram showing four CSR nodes connected to two HSR nodes, which are then connected to a cloud. - -**Figure 10-5 Redundant hub and spoke access physical topology (also often called spine and leaf)** - -7 -8 -9 - -![Non-redundant hub and spoke access physical topology diagram showing four CSR nodes connected to a single HSR node, which is then connected to a cloud.](daf05db9f13b34fb12da52f007bbfe5b_img.jpg) - -A diagram showing a non-redundant hub and spoke access physical topology. Four nodes labeled 'CSR' are connected to a single node labeled 'HSR'. The 'HSR' node is then connected to a cloud-shaped icon on the right. There is no redundancy in the path to the cloud. - -Non-redundant hub and spoke access physical topology diagram showing four CSR nodes connected to a single HSR node, which is then connected to a cloud. - -**Figure 10-6 Non-redundant hub and spoke access physical topology (also often called spine and leaf)** - -10 -11 -12 -13 - -14     10.1.1.2 Suitability to support O-RAN Fronthaul/Midhaul/Backhaul - -15     As discussed in detail in Section 8, depending on the use case, O-DU function can be placed at the - 16     cell site, together with O-RU function, or placed away from the O-RU, at the hub site. The O-DU - 17     placement has big influence on the possible physical topology for the access domain of the transport - 18     network. - -![O-RAN ALLIANCE logo](6450d1043578af5919949d716e3349b1_img.jpg) - -O-RAN ALLIANCE logo - -Open Fronthaul Interface between O-RU and O-DU has very strict latency and timing budgets (O-RAN.WG9.XTRP-REQ-v01.00 ‐Xhaul Transport Requirements v01.00‐, November 2020 [20]). The implication of these requirements on the transport network design is, the number of Transport Network Equipments (TNEs) between O-RU and O-DU should be minimized, as each TNE increases the latency and time error. - -While each of the depicted access topology could be used for Fronthaul, topologies with limited number of transit Transport Network Equipments – hub-and-spoke or spine-and-leaf – leave more latency budget for delay caused by light propagation in the fiber, allowing for extending Fronthaul over larger distances, comparing to the topologies with bigger number of transit Transport Network Equipments (ring or chain topologies). - -Ring or chain topologies can be used for Fronthaul, providing that latency and timing error budgets required for particular Fronthaul deployment are maintained. For example, designing Fronthaul for standard NR performance (O-RAN.WG9.XTRP-REQ-v01.00 ‐Xhaul Transport Requirements v01.00‐, November 2020 [20] Table 3), mandates maximum 100 $\mu\text{s}$ one-way latency between O-RU and O-DU. This latency budget is consumed by the fiber ( $\sim 4.9 \mu\text{s/km}$ ), as well as by transit Transport Network Equipments ( $\sim 1\text{-}20 \mu\text{s}$ per node, depending on hardware capabilities and port speeds). Assuming 10 $\mu\text{s}$ latency per Transport Network Equipment, a chain or ring with 10 Transport Network Equipments would completely consume entire Fronthaul latency budget (ring might break, so any Fronthaul design must be prepared for link failures not only from traffic rerouting perspective, but as well must take into account increased number of transit network elements, leading to increased latency, under ring failure condition). - -Shorter chain or ring, with for example 7 Transport Network Equipments, leaves only 30 $\mu$ (6 km) latency budget for fiber. - -Note: the maximum number of TNEs can be limited due to overall synchronization requirements and the consideration of time error contributions of integrated T-BC/T-TC. Examples are given in CUS specification Annex H, and will be provided in WG9 Timing and Synchronization architecture solution document [22]. - -For Midhaul/Backhaul interfaces, there are not so strict requirements regarding latency budgets, so any access topology (ring, chain or hub-and-spoke/spine-and-leaf) can be used without special considerations. - -Note: Hub and spoke architectures are often super-imposed over a physical ring topology using WDM technology. To minimize the Fronthaul latency, direct (dark) fibre should be used in hub and spoke (spine and leaf) access physical architecture carrying Fronthaul traffic. Otherwise (ring topology), detailed latency analysis must be performed to confirm that latency stays within mandated Fronthaul budget. - -#### 10.1.1.2.1 Time Sensitive Networking (TSN) for Fronthaul - -IEEE 802.1CM [35] defines two Time Sensitive Networking (TSN) profiles, with main characteristics summarized in Table 2. - -| Characteristic | TSN Profile A | TSN Profile B | -|----------------|---------------|---------------| -|----------------|---------------|---------------| - -| | | | -|--------------------------------------------------|--------------|--------------| -| Max frame size for Fronthaul data | 2,000 octets | 2,000 octets | -| Max frame size for non-Fronthaul data | 2,000 octets | no limit | -| Differentiated prioritization for Fronthaul data | yes | yes | -| Frame pre-emption of non-Fronthaul data | no | yes | - -Table 2 TSN Profile A and Profile B comparison - -The major differences between TSN Profile A and TSN Profile B are therefore the maximum frame size of non-Fronthaul traffic, as well frame pre-emption, as pictured in Figure 10-7. - -![Figure 10-7: Comparison of TSN Profile A and TSN Profile B operations. The diagram shows four time steps (T0, T1, T2, T3) for both profiles. In Profile A (no preemption), packet 1 is transmitted from T0 to T2, and packet 2 starts at T3. In Profile B (preemption), packet 2 appears in the eCPRI queue at T1, preempts packet 1 at T2, and finishes at T3. Packet 2 serialization delay is noted as equal to eCPRI latency/PDV.](c419b566d720267c499087add1506018_img.jpg) - -The diagram illustrates the operation of TSN Profile A (no preemption) and TSN Profile B (preemption) over four time steps: $T_0$ , $T_1$ , $T_2$ , and $T_3$ . Both profiles show a queue with four slots: eCPRI (highest priority), AF2, AF1, and BE (lowest priority). - -- TSN Profile A (no preemption):** - - $T_0$ : packet 1 transmit starts (in AF2 slot). - - $T_1$ : packet 2 appears in eCPRI queue (in eCPRI slot). - - $T_2$ : packet 1 transmit finishes (AF2 slot empty). - - $T_3$ : packet 2 transmit starts (in eCPRI slot). - - Note: $T_2 - T_1 \rightarrow$ packet 2 serialization delay ( $=$ eCPRI latency/PDV). -- TSN Profile B (preemption):** - - $T_0$ : packet 1 transmit starts (in AF2 slot). - - $T_1$ : packet 2 appears in eCPRI queue (in eCPRI slot). - - $T_2$ : packet 2 preempts packet 1 (Frame preemption). Max 155 bytes transmitted since $T_1$ . - - $T_3$ : packet 2 transmit starts (in eCPRI slot). - - Note: $T_2 - T_1 \rightarrow$ 155 bytes of packet 2 serialization delay ( $=$ eCPRI latency/PDV). - -Figure 10-7: Comparison of TSN Profile A and TSN Profile B operations. The diagram shows four time steps (T0, T1, T2, T3) for both profiles. In Profile A (no preemption), packet 1 is transmitted from T0 to T2, and packet 2 starts at T3. In Profile B (preemption), packet 2 appears in the eCPRI queue at T1, preempts packet 1 at T2, and finishes at T3. Packet 2 serialization delay is noted as equal to eCPRI latency/PDV. - -Figure 10-7 TSN Profile A and TSN Profile B operations - -IEEE 802.1CM has detailed discussion about Transport Network Equipment latency calculation (Section 7.2), as well as example end-to-end delay calculations (Annex B), therefore these calculations are not repeated in this document. This document, however, focuses on delay differences of Fronthaul traffic introduced by Transport Network Equipment operating in accordance with TSN Profile A or TSN Profile B. - -Following delay components contribute to overall Transport Network Equipment delay: - -- **Frame transmission delay**, which is the time taken to transmit the frame at the transmission rate of the port. Since both TSN Profile A and TSN Profile B mandate for Fronthaul data maximum frame size of 2000 bytes, this delay component is equal for Fronthaul data frames with both TSN Profile A and TSN Profile B. -- **Self-queueing delay**, which is the delay caused by other frames in the same traffic class as frame to be sent (i.e. both frames are for example Fronthaul data frames). The part of the self-queueing delay caused by frames that arrive at more or less the same time from different input ports is referred to as fan-in delay; however, it is simpler to handle fan-in delay as part of the self-queueing delay. Since both TSN Profile A and TSN Profile B mandate that Fronthaul data frames cannot be pre-empted, this delay component is equal for Fronthaul data frames with both TSN Profile A and TSN Profile B. - -![O-RAN Alliance logo](1edf00a8a0ad2faa21bedfd66e9323d7_img.jpg) - -O-RAN Alliance logo - -- **Queuing delay**, which is the delay caused by the frame of which transmission already started in an arbitrarily small time before frame X became eligible for transmission, plus the delay caused by queued-up frames from all flows with higher priority than the traffic class of frame X. Since both TSN Profile A and TSN Profile B mandate that Fronthaul data must be prioritized over non-Fronthaul data, in both profiles only single non-Fronthaul frame can contribute to this delay. In case of TSN Profile A, a non-Fronthaul frame size is limited to 2,000 bytes (2,020 bytes including preamble, start of frame delimiter and inter-frame gap). In case of TSN Profile B, a non-Fronthaul frame can be pre-empted, but at least 155 bytes of pre-empted frame are transmitted due to the characteristics of frame preemption. -- **Store-and-forward delay**, which includes all other elements of the forwarding delay that are a consequence of the internal processing of the Transport Network Equipment, including the time to select the input for transmission to the egress port, assuming that the input queue under consideration and output queues are empty. This delay factor is highly hardware dependent, but is equal for both TSN Profile A and TSN Profile B on given hardware. - -Summarizing, the only differentiated delay factor between TSN Profile A and TSN Profile B is queueing delay of non-Fronthaul data (queueing delay of 2,020 octets in TSN Profile A, versus queueing delay of 155 octets in TSN Profile B). - -Table 3 summarizes this queueing delay for various port speeds. - -| Port speed | TSN Profile A
Queuing delay of 2,020 bytes | TSN Profile B
Queuing delay of 155 bytes | Difference | | -|------------|-----------------------------------------------|---------------------------------------------|------------|---------| -| 1 Gbps | 16.160 µs | 1.240 µs | 14.920 µs | 3,045 m | -| 10 Gbps | 1.616 µs | 0.124 µs | 1.492 µs | 304 m | -| 25 Gbps | 0.646 µs | 0.050 µs | 0.596 µs | 122 m | -| 50 Gbps | 0.323 µs | 0.025 µs | 0.298 µs | 61 m | -| 100 Gbps | 0.162 µs | 0.012 µs | 0.149 µs | 30 m | -| 200 Gbps | 0.081 µs | 0.006 µs | 0.075 µs | 15 m | -| 400 Gbps | 0.040 µs | 0.003 µs | 0.037 µs | 8 m | - -**Table 3 Queuing delay of non-Fronthaul data** - -Significant difference between TSN Profile A and TSN Profile B can be observed over port with 1 Gbps speed (14.92 µs, which is equivalent to ~3 km fiber). For port speeds 10 Gbps or above, the latency difference introduced to Fronthaul traffic (1.494 µs, which is equivalent to 305 m fiber, or less) is not so significant for designs targeting standard NR performance (with 100 µs overall latency budget). - -### 10.1.2 Pre-aggregation / Aggregation / Core transport - -Pre-aggregation and aggregation and the core transport infrastructure can support Midhaul and Backhaul requirements. Due to the delay requirements associated with Fronthaul, it is unlikely O-RAN 7.2x or RoE will be seen in these portions of the network. Additionally, in most scenarios the transport core will not be part of the Midhaul or Backhaul environment but may provide N6 connectivity to any of the following: - -1. Peering points for mobile consumer services. -2. Enterprise locations for mobile enterprise solutions. - -3. Inter region voice communications within the operator. -4. Other operators. - -#### 10.1.2.1 Physical media and topologies - -The assumption made in this architecture is the connectivity between routers in the pre-aggregation, aggregation and transport core is provided by point-to-point Ethernet connections where the full capacity of the Ethernet interface is available to the router. Link speed will depend on the traffic levels required by the services running and the position in the network. The anticipated ranges will be from 10Gbps up to bundles of 400Gbps with the capacity provided over dark fibre or some form of WDM solution. - -The physical topology employed in the pre-aggregation, aggregation and transport core are operator dependent and driven by fibre topology, its availability and the traffic matrix. The main physical architectures seen in these segments of the network are all redundant and include ring, “hub and spoke” and mesh. These are shown in Figure 10-8. - -Note: This document uses the term “hub and spoke architecture” but it is used inter-changeably with leaf / spine and fabric architectures. - -![Figure 10-8: Physical topologies anticipated in Xhaul pre-aggregation, aggregation and core. The diagram shows three topologies: 1. Ring: Five router icons arranged in a circle and connected sequentially. 2. Hub and Spoke or Fabric design: Four router icons on the left connected to two router icons on the right in a bipartite leaf-spine arrangement. 3. Mesh: Six router icons arranged in a hexagon with multiple cross-connections. Below the mesh is the text 'Resiliency not shown'.](b774dfc5023e15e9c352b97ca25a56d4_img.jpg) - -Ethernet point-2-point links - -Ring - -Hub and Spoke -or Fabric design - -Mesh -Resiliency not shown - -Figure 10-8: Physical topologies anticipated in Xhaul pre-aggregation, aggregation and core. The diagram shows three topologies: 1. Ring: Five router icons arranged in a circle and connected sequentially. 2. Hub and Spoke or Fabric design: Four router icons on the left connected to two router icons on the right in a bipartite leaf-spine arrangement. 3. Mesh: Six router icons arranged in a hexagon with multiple cross-connections. Below the mesh is the text 'Resiliency not shown'. - -**Figure 10-8 Physical topologies anticipated in Xhaul pre-aggregation, aggregation and core** - -1. Ring: This architecture is commonly seen in pre-aggregation and aggregation networks where traffic is being collected and aggregated from the access towards components in the aggregation or transport core. Connectivity between routers is either via direct dark fibre connections or via lambdas derived from a WDM system. -2. Dual hub and spoke: This architecture is most commonly seen in aggregation and core transport networks but also sometimes in pre-aggregation networks. It is used to collect and aggregate traffic towards common aggregation points. Connectivity between routers is typically via direct dark fibre or via lambdas derived from a WDM system. - -Note: Hub and spoke architectures are often super-imposed over a physical ring topology using WDM technology. - -3. Mesh: This is architecture is normally seen in transport core networks but can be seen in aggregation networks. It is used when traffic is flowing in an any-to-any fashion. As drive distances increase and connectivity becomes meshier in nature, so there is increasing use of DWDM and ROADM technology to derive the links between routers. - -## 10.2 Alternative physical transport solutions - -This document concentrates packet switching over a fibre infrastructure. However, there are other physical solutions that can be employed in Xhaul networks. This section outlines some of those technologies and discusses their applicability in different Xhaul roles. - -### 10.2.1 WDM in access network - -The access network uses optical technology with no packet switching transport functionality. Figure 10-9 illustrates a passive WDM Fronthaul design but the same design principle applies regardless of the WDM solution. Each O-RU directly connected to the WDM multiplexer/demultiplexer by a colored optic and an optical cable. At the O-DU side in the central office, the WDM multiplexer/demultiplexer performs wavelength multiplexing/demultiplexing, which realize the one-to-one optical wavelength connection. The WDM solution can be passive, semi active or active. - -![Diagram of a passive WDM Fronthaul design showing three AAUs on the left connected via individual colored lines to a trapezoidal multiplexer. A single multi-colored line connects this to a second trapezoidal demultiplexer on the right, which then connects via individual colored lines to a DU unit.](3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg) - -The diagram shows a point-to-point WDM architecture. On the left, three Active Antenna Units (AAUs) are shown. Each AAU is connected to a WDM multiplexer/demultiplexer via a specific colored optical fiber (representing a specific wavelength). These multiple wavelengths are combined into a single optical fiber (the common link). On the right side, another WDM multiplexer/demultiplexer separates the wavelengths back into individual fibers that connect to the Distributed Unit (DU). This setup provides a dedicated, one-to-one optical wavelength connection between each AAU and the DU over a shared physical fiber. - -Diagram of a passive WDM Fronthaul design showing three AAUs on the left connected via individual colored lines to a trapezoidal multiplexer. A single multi-colored line connects this to a second trapezoidal demultiplexer on the right, which then connects via individual colored lines to a DU unit. - -**Figure 10-9 WDM Fronthaul design (passive)** - -WG-9 has a work item underway considering WDM-based Fronthaul transport [21], consequently this document does not consider this type of access network design further. - -### 10.2.2 Passive Optical Networks (PONs) - -Passive Optical Networks (PONs) are fiber-based point-multipoint access networks, relying on TDM/TDMA for the exchange of traffic between a central Optical Line Termination (OLT) and multiple Optical Network Units (ONUs). PONs also use WDM for separation of up- and downstream traffic, and for overlaying of multiple different PON technologies over the same fiber infrastructure called Optical Distribution Network (ODN). Note that there are two basic flavours of PON; - -1. Time or Time +Wavelength Division Multiplexing (TDM or TWDM) PONs apply point-multipoint connections (one up/down wavelength pair (called Channel Pair) is shared over multiple ONUs) over a point-multipoint ODN. -2. Wavelength Division Multiplexing (WDM) PONs apply point-point connections between each ONU and the OLT (one Channel Pair per ONU) over a point-multipoint ODN. - -WDM PONs are like dedicated point-point links whereas TDM/TWDM PONs have some fundamental characteristics to bear in mind when considering them for mobile Xhaul, described below. - -![O-RAN Alliance logo](38e2f36189a1eef7ecbdd4c44bdeea2e_img.jpg) - -O-RAN Alliance logo - -![Figure 10-10: Typical TDM PON network diagram. The diagram illustrates the network architecture and data flow. At the top, three sub-diagrams show: 1) Upstream/Downstream duplex with a graph of Up (green) and Down (red) signals on a wavelength λ, noting that Channel Pair = λ_up + λ_down separated by WDM. 2) Downstream multiplexing: selection by TDM, showing three data streams (1, 2, 3) being combined. 3) Upstream multiplexing: access and selection by TDMA, showing three data streams (1, 2, 3) being combined. The main diagram shows multiple ONUs (ONU 1, ONU 2, ONU ..., ONU N) connected via drop fibers to a 1:N passive optical splitter(s). The splitter is connected via a feeder fiber to a PON OLT. The OLT is connected to two Service Network Interfaces (SNIs): Mobile Access & Core and Residential / Business Edge & aggregation. The ODN (Optical Distribution Network) class determines reach & split ratio combination, and includes fiber, splices, connectors, splitters, and filters. UNIs (User Network Interfaces) are shown connected to the ONUs.](b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg) - -Figure 10-10: Typical TDM PON network diagram. The diagram illustrates the network architecture and data flow. At the top, three sub-diagrams show: 1) Upstream/Downstream duplex with a graph of Up (green) and Down (red) signals on a wavelength λ, noting that Channel Pair = λ\_up + λ\_down separated by WDM. 2) Downstream multiplexing: selection by TDM, showing three data streams (1, 2, 3) being combined. 3) Upstream multiplexing: access and selection by TDMA, showing three data streams (1, 2, 3) being combined. The main diagram shows multiple ONUs (ONU 1, ONU 2, ONU ..., ONU N) connected via drop fibers to a 1:N passive optical splitter(s). The splitter is connected via a feeder fiber to a PON OLT. The OLT is connected to two Service Network Interfaces (SNIs): Mobile Access & Core and Residential / Business Edge & aggregation. The ODN (Optical Distribution Network) class determines reach & split ratio combination, and includes fiber, splices, connectors, splitters, and filters. UNIs (User Network Interfaces) are shown connected to the ONUs. - -**Figure 10-10: Typical TDM PON network. In TWDM PON multiple Channel Pairs are muxed per ODN** - -TDM/TWDM PONs are standardized technologies (see [195], [37], [38], [39]) and are characterized by generic capabilities (independently of the use case): - -- PON line rates are shared over the ONUs and existing technologies reach 10 Gbit/s per channel (up to 4x 10 Gbit/s with NG-PON2), with new variants being developed at 25 Gbit/s and 50 Gbit/s. Note that some fraction is consumed by the technology-specific overheads (e.g. by parity bits for Forward Error Correction). -- Depending on the technology the maximum distance can reach 20 km or 40 km (or 60 km with a reach extender), the maximum amount of ONUs per PON port can reach 64 or 128. Note that the reach (distance) and scalability (amount of ONUs per PON ODN) are a mutual trade-off bound by the optical budget (many classes of optical budget exist, e.g. Class N1 covers optical losses from 14dB to 29dB). -- The max amount of traffic flows per PON port can reach 4k (independently of physical layer considerations). -- The upstream TDMA multiplexing is controlled by a Dynamic Bandwidth Assignment (DBA) algorithm in the OLT (which is equivalent to upstream shaping over the PON segment). The DBA allocates the bandwidth needs per transport container (each ONU can have one or multiple transport containers) and update its assigned bandwidth. The assigned bandwidth is then converted into a burstiness (rate and size of bursts). Bandwidth can also be (partially or fully) assigned as a fixed value. The upstream latency is influenced by the DBA behaviour, with a trade-off between latency and efficiency (more frequent bursts means less waiting time between bursts but more overhead). -- Protection of (parts of) the passive ODN and active OLT equipment by automated switch-over from working to protecting parts of the equipment. -- Management and configuration of the ONUs. Note that ONUs operate at Layer 2 only (e.g. for Layer 2 flow classification). An ONU can be connected to (or integrated with) a Layer 3 device like a residential gateway. - -PON ports are terminated in the OLT node, which terminates the PON layers and acts as an aggregation and multiplexing node for the multiple PON ports. Contrary to the PON layer, the - -![O-RAN Alliance logo](e559cb8d15d95b7f4c5761d295051cc0_img.jpg) - -O-RAN Alliance logo - -OLT's features are not strictly standardized, although reference deployment models are defined in Broadband Forum documents (See [190], [191]). Typical OLT features include; - -- QoS-aware packet forwarding between user side and network side (unicast, multicast, Layer 2 switching, Layer 3 routing) -- Traffic management (classification, (re)marking, queuing and scheduling, policing, shaping...) -- User-side protocol interaction (e.g., DHCP relay agent, IGMP proxy, ARP relay, ...) or on the contrary protocol transparency -- Network-side protocol support (e.g., IP routing protocols, IGMP proxy, MPLS signalling, ...) - -The datagrams (typically IP over Ethernet) undergo several handlings when being transported from end to end over a PON system. The different steps can be summarized as follows: - -#### **Downstream (OLT SNI ingress to ONU UNI egress)** - -1. Traffic Management (classification, policing, queuing and scheduling) at ingress (OLT SNI), -2. Forwarding (Layer 2 switching or Layer 3 routing) towards corresponding PON MAC (PON port), -3. Encapsulation in PON MAC (according to standard, ITU-T or IEEE), -4. OLT PON port egress queuing and scheduling, -5. Fiber propagation, -6. ONU (Layer 2 based) forwarding to corresponding UNI, -7. Decapsulation of PON MAC layer, -8. ONU UNI egress queuing and scheduling (Layer 2) - -#### **Upstream (ONU UNI ingress to OLT SNI egress)** - -1. DBA processing in OLT for burst-based TDMA transmission (acts as policer and shaper), -OLT notifies grants to ONUs by sending a Bandwidth Map to all ONUs, -2. Traffic Management (Layer 2 classification, queuing and scheduling) at ingress (ONU UNI), -3. Encapsulation in PON MAC (according to standard, ITU-T or IEEE), -4. Burst generation as per bandwidth map, -5. Fiber propagation, -6. Decapsulation of PON MAC layer, -7. Forwarding (L2 switching or L3 routing) to right OLT uplink (SNI), -8. OLT uplink (SNI) egress queuing and scheduling - -PONs are widely used for all FTTx use cases (Cabinet, DPU, Office, Home, ...), and are designed for multi-service support (residential triple play, business services, Wireless LAN access points). As explained in the next section and [194], PONs have been extended with additional features and are also suitable for multiple Xhaul scenario's. PONs can act as layer 2 legs in the end-end transport, or participate (from OLT upwards) to layer 3 routing. - -##### **10.2.2.1 Using PON for Xhaul: specific features** - -As a PON is an asymmetrical (bandwidth and latency) point-to-multipoint medium, time and frequency synchronization have to be transported using native media means using media converters (in OLT and ONU). The PON technology have in-built mechanisms for providing frequency and phase synchronization. This will be described in [22]. - -![O-RAN ALLIANCE logo](26e59f6e6ab842a448d8270473d5c8a8_img.jpg) - -O-RAN ALLIANCE logo - -The PON DBA is being extended with a cooperative mode DBA (called Cooperative DBA or CO DBA in short) for interaction with O-RAN CTI ([24], [25]) making it suitable for some Fronthaul needs by improving the multiplexing while keeping transport latency low. - -A specific side effect of T(W)DM PONs is the need for discovery and ranging of new ONUs by means of short interruptions (up to a couple of 100's of $\mu\text{s}$ ) of upstream traffic. Such interruptions are likely to impact the performance at the mobile radio layer, but several ways to mitigate the impact or reduce or eliminate the interruptions are being developed (ranging notification from OLT to O-DU by CTI, optimization of ranging timing to minimize impact, avoiding ranging on the latency-sensitive channel by means of separate dedicated activation wavelength). - -### 10.2.2.2 Xhaul Use cases: topologies - -#### **PON for Fronthaul** - -![Figure 10-11: PON for transport of Fronthaul flows](a4bfa2343d75076b79f7e33d93915e00_img.jpg) - -The diagram illustrates the network architecture for Fronthaul over PON. From left to right: A smartphone connects to a Cell site containing an O-RU. The O-RU connects to an ONU. The ONU and a PON OLT are enclosed in a yellow box labeled "Fronthaul NW". An arrow points from the ONU to the PON OLT. The PON OLT connects to an "Aggr Node" (Aggregation Node). A dashed line labeled "CTI" connects the PON OLT and the Aggr Node. The Aggr Node connects to an O-DU. The O-DU connects to a dashed box labeled "(Midhaul NW)". This connects to an O-CU. The O-CU connects to a grey box labeled "Backhaul NW", which finally connects to the "Mobile Core" cloud. - -Figure 10-11: PON for transport of Fronthaul flows - -**Figure 10-11 PON for transport of Fronthaul flows** - -Points of attention for Fronthaul deployments are latency at transport level, capacity per O-RU, and time synchronization accuracy (Time Error between the O-RUs). For Fronthaul the O-RUs are connected to ONUs, the OLT is connected to multiple O-DUs (or O-DU/O-CUs), possibly through intermediate aggregating node(s). The PON system can be on-site (e.g., cell site = event zone) or reach up to the cell site (ONU at cell site). - -The appropriateness of a PON technology depends on several points: - -- the considered radio bandwidth and corresponding Fronthaul throughput and the number of O-RUs per PON that can multiplexed per single PON port -- the obtained latency at packet transport level which depends on the DBA settings (and use of CTI). The requirements for Fronthaul depend on the combination of O-DU and O-RU categories, which have one-way latency budgets ranging from tens to hundreds of $\mu\text{s}$ for usual Fronthaul, and multiple ms for non-ideal Fronthaul (see [18]). Plain DBA is not suited for usual fronthaul, for which Cooperative DBA with CTI is required. Plain DBA can address non-ideal fronthaul. See 10.2.2.3 for more details. -- The time accuracy between O-RUs on PON systems will be described in [22]. - -#### **PON for Midhaul** - -![Figure 10-12: PON for transport of Midhaul flows](a4b868a176f7e0448ee72483727e9f6f_img.jpg) - -The diagram illustrates the network architecture for Midhaul over PON. From left to right: A smartphone connects to a Cell site containing an O-RU. The O-RU connects to a dashed box labeled "(Fronthaul NW)". This connects to an O-DU. The O-DU connects to an ONU. The ONU and a PON OLT are enclosed in a yellow box labeled "Midhaul NW". An arrow points from the ONU to the PON OLT. The PON OLT connects to an "Aggr Node". The Aggr Node connects to an O-CU. The O-CU connects to a grey box labeled "Backhaul NW", which connects to the "Mobile Core" cloud. - -Figure 10-12: PON for transport of Midhaul flows - -**Figure 10-12: PON for transport of Midhaul flows** - -Points of attention for Midhaul deployments are latency at application level (e.g. for URLLC), QoS differentiation (for achieving better statistical multiplexing), capacity per O-RU. For Midhaul the - -![O-RAN Alliance logo](8e7f7b57b2b087bea39bac584f91d580_img.jpg) - -O-RAN Alliance logo - -O-DUs are connected to ONUs, the OLT is connected to multiple O-CUs, possibly through intermediate aggregating node(s). The PON system (ONU) can reach up to the cell site or to some higher aggregation point. - -The appropriateness of a PON technology depends on - -- the considered radio bandwidth and corresponding Midhaul throughput, -- the number of O-RUs per PON that can multiplexed per single PON port and the obtained latency at application level (for higher CoS like e.g. URLLC). See 10.2.3.2 for more details. -- the requirement for time alignment accuracy of TDD transmitters between O-RU and the PRTC (Class 4A 3 $\mu s$ ) is independent of the topology of O-RU clusters (mutual position of O-RUs on the PONs). The time accuracy with PON systems will be described in [22]. - -**PON for Backhaul** - -![Diagram of PON for transport of Backhaul flows](977811d1c73b74f801be9f4c376694ca_img.jpg) - -``` - -graph LR - subgraph Cell_Site [Cell site] - Smartphone((Smartphone)) - Antenna((Antenna)) - ORU[O-RU] - end - - subgraph Fronthaul_NW [Fronthaul NW] - direction LR - end - - ODU[O-DU] - - subgraph Midhaul_NW [Midhaul NW] - direction LR - end - - OCU[O-CU] - ONU[ONU] - - subgraph Backhaul_NW [Backhaul NW] - PON_OLT[PON OLT] - Aggr_Node[Aggr Node] - end - - Mobile_Core((Mobile Core)) - - Antenna --- ORU - ORU --- Fronthaul_NW - Fronthaul_NW --- ODU - ODU --- Midhaul_NW - Midhaul_NW --- OCU - OCU --- ONU - ONU --- PON_OLT - PON_OLT --- Aggr_Node - Aggr_Node --- Mobile_Core - -``` - -The diagram illustrates the network path for backhaul flows. It starts at the cell site with a smartphone and antenna connected to an O-RU. This connects through a Fronthaul NW to an O-DU, then through a Midhaul NW to an O-CU. The O-CU connects to an ONU, which then enters the Backhaul NW (highlighted in yellow) containing a PON OLT and an Aggregation Node. Finally, the path connects to the Mobile Core. - -Diagram of PON for transport of Backhaul flows - -Figure 10-13 PON for transport of Backhaul flows - -The points of attention are similar as for Midhaul. For Backhaul the O-CUs are connected to ONUs, the OLT is connected to the mobile core, possibly through intermediate Backhaul aggregating node(s). The PON system (ONU) can reach up to the cell site or to some higher aggregation point. The appropriateness of a PON technology is similar as for Midhaul. - -**PON for carrying traffic mixes** - -Note that PON systems are multi-service, hence mixes of different Xhaul flavours can co-exist on the same PON system (e.g. Midhaul + Backhaul) and can also co-exist with non-mobile traffic (e.g. business services). There is also the possibility of re-using the passive fiber infrastructure for different PON technologies by means of WDM overlay, e.g., one system for mobile and one system for residential services. Traffic characteristics of each PON system are then fully independent of the other system. - -**10.2.2.3 Using PON for Xhaul: trade-offs of the technology** - -PON systems can be used in many situations, but obviously not all. Each Xhaul transport use case poses specific requirements, which must be considered in light of the possible trade-offs inherent to the PON technology: - -1. Latency - - a. versus bandwidth efficiency (making bursts more numerous and shorter decreases latency but increases physical layer overhead). - - b. versus statistical multiplexing (the higher the ratio of variable versus fixed BW allocations, the better the multiplexing but the higher the latency can become). Using CTI allows to reach higher statistical multiplexing while keeping latency limited. - - c. versus reach (5 $\mu s$ /km one-way propagation time) - - d. As guideline, using PONs with fixed bitrate allows to support very low latencies (sub-100 $\mu s$ ) but this is not efficient for variable rate fronthaul. PONs with plain DBA efficiently follow variable rate traffic but introduce a latency in the order of one to several ms. When combining CTI with Cooperative DBA in the OLT for variable rate - -![O-RAN Alliance logo](31d640309e19a64318c874023ba0aadd_img.jpg) - -O-RAN Alliance logo - -fronthaul traffic (like O-RAN 7.2x), the extra latency can be reduced by an order of magnitude compared to plain DBA, and such PONs can support several use cases of usual fronthaul and all combinations of non-ideal fronthaul (see O-RU and O-DU combinations as per [18]). - -2. Bandwidth per Xhaul node versus the number of nodes served per ODN (bandwidth sharing) -3. phase synchronization accuracy versus topology of O-RU clusters in PONs and path propagation difference up/down (max fiber distance and wavelength-dependent correction factors). This will be described in [22]. - -### 10.2.3 DOCSIS Networks - -Today's modern cable operators deploy and manage extensive hybrid fiber coaxial (HFC) networks. The HFC plant reaches 93% of American households and connects to virtually every building across north America. The data-over-cable service interface specification (DOCSIS®) is the protocol designed to work on the HFC network. DOCSIS suite of specifications is standardized and maintained by CableLabs® [203][204], and is deployed worldwide. DOCSIS technology has evolved through six generations of progressive refinement. Originally developed for delivering high speed broadband to residential customers, the cable industry has made many advances in the HFC technology, making it a promising option for 5G transport. The HFC plants are already extensively deployed in areas where 5G will be in the most demands, especially in dense urban and suburban environments. Additionally, the HFC plant is active, providing power needed for small cell radios. The cable operators typically have the right of way on the strands where radios can be hung, eliminating the need to obtain permits from government. Leveraging the existing HFC deployments significantly reduces time-to-market and cost of deploying 5G. - -#### 10.2.3.1 DOCSIS technology overview - -DOCSIS protocol is a Layer 2 transmission protocol that encapsulates the IEEE 802.3 Ethernet. The technology supports both Layer 2 and Layer 3 services and is aware of both. DOCSIS network is a point-to-multipoint access network, where the transmission of upstream and downstream is controlled by the cable modem termination system (CMTS). Figure 10-14 shows a typical HFC plant. The CMTS is typically located in either a headend or a hub, which is connected to the fiber nodes through digital or analog fiber. From there, the communication path traverses through a coax network of zero or more amplifiers to the neighborhoods. The hybrid (fiber and coax) network topology is called “N+x”, where “N” is the fiber node, where the fiber ends and coax starts, and “x” is the number of amplifiers traversed. The average north American plant is between N+2 and N+5. The smaller the x, the closer the fiber node it is to the neighborhood, the larger the amount of capacity would be available to each customer. - -The traditional physical CMTS controls 50k cable modems (CMs). It is expected to scale up as the CMTS moves to the cloud native architecture. - -![Figure 10-14: Typical HFC plant diagram. The diagram shows a Mobile Core and Residential/business aggregation connected to a CMTS (Headend/Hub). The CMTS is connected via Fiber (Average reach ~30km) to an Aggregation node. The Aggregation node is connected to two Fiber nodes. Each Fiber node is connected to a Coax (including amplifiers, taps) line. The Coax lines are connected to four Cable Modems, which are then connected to various devices: a mobile device, a building, a mobile device, and a laptop.](e0627c8e3dfda5da1ee8d5a90c9f7489_img.jpg) - -Figure 10-14: Typical HFC plant diagram. The diagram shows a Mobile Core and Residential/business aggregation connected to a CMTS (Headend/Hub). The CMTS is connected via Fiber (Average reach ~30km) to an Aggregation node. The Aggregation node is connected to two Fiber nodes. Each Fiber node is connected to a Coax (including amplifiers, taps) line. The Coax lines are connected to four Cable Modems, which are then connected to various devices: a mobile device, a building, a mobile device, and a laptop. - -Figure 10-14: Typical HFC plant - -Table 4 shows the capabilities of the most recent DOCSIS standards. While DOCSIS 4.0 will provide over 10 Gbps of downstream capacity, even higher rates can be supported. A unique aspect of the DOCSIS technology is its ability to progressively expand downstream and upstream capacities when and where it is needed. Traditionally, the same plant is used to provide video and broadband services. As the cable industry moves away from traditional video delivery, the RF spectrum that is used for video can be reclaimed for broadband. Moreover, as cable operators move to reduce the “x” in the N+x topology, node segmentation takes place. For every node that is segmented into two, the network capacity essentially doubles. - -| Requirements | D3.1 today (2020) | D3.1 max (2021-22) | D4.0 (2023-24) | -|---------------------|-----------------------------------------------------------------------------|-----------------------------------------|--------------------------------------| -| | Shared spectrum with video | Full spectrum through video reclamation | Extending to 1.8 GHz, possibly 3 GHz | -| Downstream spectrum | 54 – 1002 MHz | 258-1218 MHz | 602 – 1794 MHz | -| Upstream spectrum | 5 – 42 MHz | 5 – 204 MHz | 5 – 492 MHz | -| DS capacity | 8.5 Gbps | 8.6 Gbps | 10.8 Gbps | -| US capacity | 0.1 Gbps | 1.4 Gbps | 3.7 Gbps | -| Upstream latency | Best effort: 5 – 50 ms
With LLX / CTI: 1 – 2 ms (can be further reduced) | | | -| Synchronization | Frequency sync only
No time sync | Frequency + time sync through DTP | | - -Table 4 DOCSIS Capabilities; Today and the near future - -The DOCSIS specification provides a rich set of QoS mechanisms, including traffic classification, queuing, multiple scheduling services, policing, traffic shaping. Each CM supports 16-32 service flows in each direction. DOCSIS technology supports several native upstream scheduling mechanisms: best effort, unsolicited grant service (UGS), real-time polling service (RTPS), and proactive grant service (PGS). Latency on the upstream can range from minimum of 3-5 ms to average of 12 ms under best effort, to 1-5 ms under UGS or PGS. For best effort scheduling service, latency is dependent on the load, as well as frame configurations such as OFDM frame size and interleaver depth. For UGS/PGS services, there are trade-offs between incurring capacity overhead vs. lowering the latency. The recommendation is to transport mobile Xhaul traffic over the DOCSIS network via best effort service. To address the latency concern, CableLabs standardized the Low - -![ORAN Alliance logo](8a7178c57b4e93672de9bed2cffdaf28_img.jpg) - -ORAN Alliance logo - -Latency Xhaul (LLX) technology [201], which provides consistent 1-2 ms of latency on the upstream. The latency could potentially be further reduced with some configuration optimizations. The ORAN CTI ([24], [25]) specification uses a similar scheduler pipelining mechanism as LLX. Typically, the latency on the downstream is 1ms. - -Cable operators are in the midst of disaggregating the traditional CMTS. The “Distributed Access Architecture” (DAA), shown in Figure 10-15, has been specified by CableLabs [205] and is being deployed. Replacing the traditional “integrated” CMTS, PHY layer component of the CMTS is being pushed to the fiber node and is called Remote PHY Device (RPD), while MAC and upper layers are implemented as DAA Core, and is located in the headend or regional data center. The DAA Core has been architected with the cloud native architecture. The links between the fiber node and the hub are being upgraded to a digital fiber network, with DWDM as a starting point, but some operators may choose to migrate to point-to-point coherent optics. A device called “CTD” is being specified to terminate the fiber from the hub, and is essentially be a Layer 2 switch that provides high-speed Ethernet to the neighborhood. A multitude of services can be provided through the CTD, including 5G Fronthaul, PON, etc, thus achieving a form of transport convergence. - -![Figure 10-15: Distributed Access Architecture (DAA) for transport convergence diagram. The diagram shows a network architecture starting from the 'True Cloud (AWS, GCP, Azure)' at the top, connected via 'Peering' to an 'RDC / Headend'. The headend contains components like 5GC, MM PA, CU-CP, PTP GM, CU-UP, DAA Core, UPF, and Video Core. A 'Fiber Ring' connects the headend to a 'Switch Hub'. The hub is connected to a 'CTD Aggregation Node' via 'P2P Coherent' optics. The CTD is connected to an 'RPD/RMD Node' via 'Gray Optics'. The RPD/RMD Node is connected to a 'DOCSIS CM' via 'Coax'. The DOCSIS CM is connected to various 'On Prem' services including 5G DU/RU, eNB gNB, STB, and Wi-Fi. A legend on the right defines the components: CTD: coherent termination device, CIN: converged interconnect network, RPD: R-PHY device, RMD: R-MACPHY device, MM: MAC manager, PA: packet aggregator, PTP: precision time protocol, GM: grand master clock, CP: control plane, UP: user plane, CU: central unit, DU: distributed unit, RU: radio unit, UPF: user plane function, 5GC: 5G core.](dfafe39c233a62ec8ebd71e42992c14d_img.jpg) - -Figure 10-15: Distributed Access Architecture (DAA) for transport convergence diagram. The diagram shows a network architecture starting from the 'True Cloud (AWS, GCP, Azure)' at the top, connected via 'Peering' to an 'RDC / Headend'. The headend contains components like 5GC, MM PA, CU-CP, PTP GM, CU-UP, DAA Core, UPF, and Video Core. A 'Fiber Ring' connects the headend to a 'Switch Hub'. The hub is connected to a 'CTD Aggregation Node' via 'P2P Coherent' optics. The CTD is connected to an 'RPD/RMD Node' via 'Gray Optics'. The RPD/RMD Node is connected to a 'DOCSIS CM' via 'Coax'. The DOCSIS CM is connected to various 'On Prem' services including 5G DU/RU, eNB gNB, STB, and Wi-Fi. A legend on the right defines the components: CTD: coherent termination device, CIN: converged interconnect network, RPD: R-PHY device, RMD: R-MACPHY device, MM: MAC manager, PA: packet aggregator, PTP: precision time protocol, GM: grand master clock, CP: control plane, UP: user plane, CU: central unit, DU: distributed unit, RU: radio unit, UPF: user plane function, 5GC: 5G core. - -Figure 10-15 Distributed Access Architecture (DAA) for transport convergence - -### 10.2.3.2 Xhaul transport DOCSIS network - -Functionally, the DOCSIS network can interconnect the small cells or radios as shown in Figure 10-16. However, the requirement on capacity and latency vary between Backhaul, Midhaul, and Fronthaul. Backhaul and Midhaul are both based on an IP encapsulation of the original mobile transport. Thus, the bandwidth requirement on the transport network roughly matches the mobile traffic rate. - -The latency requirement for Backhaul is based on the application. Additional service-level agreement (SLA) can be specified by the mobile operator. Midhaul latency is generally considered to be less than 10 ms [206]. LLX can be implemented to ensure these requirements can be met, as well as providing better latency performance, particularly for latency-sensitive flows. - -![O-RAN Alliance logo](d091b5e790d0a8989de686e48854c200_img.jpg) - -O-RAN Alliance logo - -![Figure 10-16 Mobile Xhaul over DOCSIS Network. The diagram shows three network configurations: Backhaul, Midhaul, and Fronthaul. Each configuration consists of a CPE (Customer Premises Equipment), a Node, a Hub, and a Headend / Edge. In the Backhaul configuration, the CPE contains an eNB/gNB connected to a CM (Cable Modem), which is connected to a DAA Node. The DAA Node is connected to a Leaf Switch in the Hub, which is connected to a DAA Core in the Headend / Edge. The DAA Core is connected to a 5GC CP (5G Core Control Plane) and an Edge UPF (User Plane Function). A dashed blue line labeled LLX connects the CPE to the Headend / Edge. In the Midhaul configuration, the CPE contains an RU (Radio Unit) connected to a DU (Distributed Unit), which is connected to a CM, which is connected to a DAA Node. The DAA Node is connected to a Leaf Switch in the Hub, which is connected to a DAA Core in the Headend / Edge. The DAA Core is connected to a 5GC CP, a CU (Central Unit), and an Edge UPF. A dashed blue line labeled LLX connects the CPE to the Headend / Edge. In the Fronthaul configuration, the CPE contains an RU connected to a CM, which is connected to a DAA Node. The DAA Node is connected to a Leaf Switch in the Hub, which is connected to a DAA Core in the Headend / Edge. The DAA Core is connected to a 5GC CP, a DU, a CU, and an Edge UPF. A dashed blue line labeled LLX / CTI connects the CPE to the Headend / Edge.](27788c2a26d9641e68232a4eff1299b9_img.jpg) - -Figure 10-16 Mobile Xhaul over DOCSIS Network. The diagram shows three network configurations: Backhaul, Midhaul, and Fronthaul. Each configuration consists of a CPE (Customer Premises Equipment), a Node, a Hub, and a Headend / Edge. In the Backhaul configuration, the CPE contains an eNB/gNB connected to a CM (Cable Modem), which is connected to a DAA Node. The DAA Node is connected to a Leaf Switch in the Hub, which is connected to a DAA Core in the Headend / Edge. The DAA Core is connected to a 5GC CP (5G Core Control Plane) and an Edge UPF (User Plane Function). A dashed blue line labeled LLX connects the CPE to the Headend / Edge. In the Midhaul configuration, the CPE contains an RU (Radio Unit) connected to a DU (Distributed Unit), which is connected to a CM, which is connected to a DAA Node. The DAA Node is connected to a Leaf Switch in the Hub, which is connected to a DAA Core in the Headend / Edge. The DAA Core is connected to a 5GC CP, a CU (Central Unit), and an Edge UPF. A dashed blue line labeled LLX connects the CPE to the Headend / Edge. In the Fronthaul configuration, the CPE contains an RU connected to a CM, which is connected to a DAA Node. The DAA Node is connected to a Leaf Switch in the Hub, which is connected to a DAA Core in the Headend / Edge. The DAA Core is connected to a 5GC CP, a DU, a CU, and an Edge UPF. A dashed blue line labeled LLX / CTI connects the CPE to the Headend / Edge. - -Figure 10-16 Mobile Xhaul over DOCSIS Network - -Fronthaul is much more difficult to support over the coax portion of the HFC network. Studies have shown that the eCPRI-based Fronthaul transport needs significantly more bandwidth, overhead, and one-way latency in the neighborhood of 250 microseconds between the O-RU and O-DU and between TNEs 100 microseconds. Even with LLX, it will be difficult to reduce the DOCSIS latency to this level. Because of the stringent requirements, Fronthaul is better carried directly over the digital fiber network and over CTD as shown in Figure 10-16. - -## 10.2.4 Microwave and mmwave radio transport technologies - -### 10.2.4.1 Overview of Microwave and mmwave technology - -For over 20 years, microwave has been the primary solution for the rapid and cost-effective rollout of mobile Backhaul infrastructure with over 50% of mobile sites worldwide today connected via Microwave (MW) or Millimetre Wave (mmW) radio links and up to over 90% in some networks. The evolution from 4G towards 5G presents significant challenges to all transport technologies and wireless ones make no exception. - -Spectrum is a vital asset to support the mobile Backhaul requirements and certainly this topic becomes increasingly relevant as future mobile access data rates and respective Backhaul capacity requirements continue to rise. Various frequency bands are used today for mobile Backhaul depending on the requested capacity, hop length, link availability, spectrum availability and frequency re-use capability. The spectrum that is available for mobile Backhaul ranges from the traditional microwave bands up to the millimetre wave spectrum as illustrated in the Figure 10-17. These bands are allocated for fixed services by the WRC Radio regulations. Their channel plans are detailed by the ITU-R F-series recommendations as well as some regional or national regulatory regimes, such as CEPT. Fixed services spectrum uses authorisations awarded by national - -![O-RAN Alliance logo](00c0ab3499a5b8f3290a0f6faa14fd62_img.jpg) - -O-RAN Alliance logo - -administrations on the basis of link by link assignments as either coordinated or self-coordinated, or as block assignments. - -![Figure 10-17: Microwave and mmwave spectrum diagram. A horizontal axis shows frequency from 10 to 180 GHz. Below the axis, colored blocks represent different bands: Traditional Bands (6~42G) in blue, E-Band (71GHz - 86GHz) in green, W-Band (92 GHz - 114.25 GHz) in yellow, and D-Band (130GHz - 174.8 GHz) in orange. Specific frequency markers include 5, 6, 7, 8, 11, 13, 15, 18, 23, 26, 28, 32, 38, 42, 52, 55, 57 - 71GHz, 71GHz - 86GHz, 92 GHz - 114.25 GHz, and 130GHz - 174.8 GHz.](f455955c4bc84005728b4138f19098dc_img.jpg) - -Figure 10-17: Microwave and mmwave spectrum diagram. A horizontal axis shows frequency from 10 to 180 GHz. Below the axis, colored blocks represent different bands: Traditional Bands (6~42G) in blue, E-Band (71GHz - 86GHz) in green, W-Band (92 GHz - 114.25 GHz) in yellow, and D-Band (130GHz - 174.8 GHz) in orange. Specific frequency markers include 5, 6, 7, 8, 11, 13, 15, 18, 23, 26, 28, 32, 38, 42, 52, 55, 57 - 71GHz, 71GHz - 86GHz, 92 GHz - 114.25 GHz, and 130GHz - 174.8 GHz. - -**Figure 10-17 Microwave and mmwave spectrum** - -The engineering of a MW or mmW link involves finding the optimal combination of link length, capacity, frequency band and availability. - -The physics of radio waves propagation determine the relation among capacity, availability and link length. Since the available spectrum is proportional to the center frequency, the highest frequencies are also those that carry the most capacity, but also cover the comparatively shortest link lengths. As a rule of thumb, frequencies below 13 GHz can be considered mostly unaffected by the intensity of rainfall and frequencies above are more and more influenced by the attenuation caused by rain, so that as a general principle higher frequencies are used for shorter links, as illustrated in Figure 10-18. It should be noted that features could be inherited for links combining different bands as indicated in the circles in this figure. - -![Figure 10-18: Interdependence among frequency, capacity and availability. A graph plots Frequency (Y-axis) against Coverage (X-axis). Three main categories are shown: mmW (E-Band, W-Band, D-Band), 15-42 GHz (Traditional Microwave), and 6-13 GHz (Long Haul Microwave). Each category has a box with details and a corresponding circle representing its characteristics. Arrows show inheritance of features between bands. Data labels indicate throughput: 10..100 Gbps for mmW, 1.5 Gbps for Traditional Microwave, and 1.2 Gbps for Long Haul Microwave.](4260aa4a7ece77c411597094c9d197bd_img.jpg) - -**mmW** - -- E-Band** • 80 GHz • Huge available spectrum -- W-Band** • 100 GHz • Peak rate: Nx10Gbps -- D-Band** • 150 GHz • Lowest Latency - -**10..100 Gbps** - -**Ultra High Capacity -Ultra Low Latency** - -**15-42 GHz** - -- Traditional Microwave** • 15 and 18 GHz • 23 and 38 GHz... - - Good resistance to rain - - High spectral efficiency - - High reliability Multiband links - -**1..5 Gbps** - -**High Peak Capacity -High Reliability** - -**6-13 GHz** - -- Long Haul Microwave** • Huge deployment of 6/7/8 GHz • 11 and 13 GHz - - Longest links 100km - - 2 Gbps per channel - - Ultra high reliability - -**1..2 Gbps** - -**Long Reach -High Capacity & Reliability** - -Figure 10-18: Interdependence among frequency, capacity and availability. A graph plots Frequency (Y-axis) against Coverage (X-axis). Three main categories are shown: mmW (E-Band, W-Band, D-Band), 15-42 GHz (Traditional Microwave), and 6-13 GHz (Long Haul Microwave). Each category has a box with details and a corresponding circle representing its characteristics. Arrows show inheritance of features between bands. Data labels indicate throughput: 10..100 Gbps for mmW, 1.5 Gbps for Traditional Microwave, and 1.2 Gbps for Long Haul Microwave. - -**Figure 10-18 Interdependence among frequency, capacity and availability. Source ETS TS mWT** - -The availability of MW/mmW spectrum depends on both technological and regulatory factors. Technology is available and under development to make full use of existing (6-86 GHz) and future (90-300 GHz) spectrum: E-band (80 GHz) has been commercially deployed for several years, W-band (100 GHz) and D-band (150 GHz) are the most promising upcoming bands, with prototypes already appearing in the market. - -![O-RAN ALLIANCE logo](07084c9c570a88714025135af11324a0_img.jpg) - -O-RAN ALLIANCE logo - -Wider channels (112MHz, even 224MHz where possible) in traditional frequency bands and raw availability of spectrum (10GHz in E-band, 18GHz in W-band and 30GHz in D-band) provide the main resources to expand the capacity of MW and mmW radio systems. Overview of available spectrum for wireless transport network with corresponding capability related to link capacity, latency and hop length is illustrated in Figure 10-19. - -![Figure 10-19: Bands characteristics and capabilities. A diagram showing the relationship between frequency bands, available spectrum, link capacity, latency, and hop length.](a346e19f92f1699e3f96432c0464c957_img.jpg) - -| Band Type | Band | GHz | Available Spectrum / Channels | Link Capacity | Latency | Hop length | -|------------------|--------|--------------------------------------------------|-------------------------------|----------------|---------|------------| -| New mmW Bands | D-Band | 170 | 30GHz – Up to 2GHz | Up to 100 Gbps | <10us | <1 km | -| | W-Band | 115 | | | | | -| Millimeter Waves | E-Band | 80 | 10GHz - Up to 2GHz | Up to 20 Gbps | 10us | < 7 Km | -| | V-Band | 60 | | | | | -| Microwave Bands | | 38, 32, 25, 23, 18, 15, 13, 11, 10, 7/8, 6, 5, 3 | 1GHz - Up to 224MHz | 1-5 Gbps | 50us | 7-150Km | - -Figure 10-19: Bands characteristics and capabilities. A diagram showing the relationship between frequency bands, available spectrum, link capacity, latency, and hop length. - -**Figure 10-19 Bands characteristics and capabilities. Source ETSI TSG mWT** - -#### 10.2.4.2 Evolving technologies - -There are a number of existing and evolving technologies which are applied in microwave and mmwave radio to enhance its spectrum efficiency, achievable capacity and reducing latency. An overview of these technologies is presented in[214]. As follow is a summary of these applicable technologies in the microwave and mwave radio transport systems. - -##### Capacity and spectrum efficiency enhancement - -Larger channels are no longer a technology limit. In MW bands recent regulatory limit shifted up to Channel Spacing CS=224MHz, but not everywhere. Up to CS=2000MHz is standardised in E-Band and above 100GHz. - -Larger CS are needed where Carrier Aggregation, in same band or adjacent band is employed. - -Higher Modulation schemes reached the reasonable top at 4096QAM (and more). After 1024QAM spectral efficiency gain is less than 10% for every step. Higher order result in reduction in system gain (impacting availability), however, with adaptive modulation availability can be maintained with lower modulation order (i.e. scarifying capacity). - -##### Frequency reuse with cross polar interference cancellation (XPIC) - -This is a well-known technique for doubling the spectral efficiency by utilising the cross polarisation of the channel bandwidth occupied. - -##### LoS-MIMO Line of Sight Multi-Input Multi-Output - -![O-RAN Alliance logo](81c2fa4df3adbe409a3d45790bc574cf_img.jpg) - -O-RAN Alliance logo - -Exploiting link geometry deployment, two different signals in the same channel can be transmitted. - 4x4 LoS-MIMO is obtained with LoS-MIMO 2x2 plus XPIC - LoS MIMO needs optimal antennas separation. - Under optimal conditions, spectral efficiency close to four times capacity improvement can be achieved, while lower performance in case of suboptimal conditions should be expected. - -![Diagram of FDD - LoS-MIMO 4x4 showing two base stations with two antennas each. The distance between the antennas on each base station is labeled 'D=Optimal separation'. Arrows indicate signal paths between the antennas of the two base stations.](5e9af8986a5845504f251d3079da8078_img.jpg) - -**FDD – LoS-MIMO 4X4** - -Diagram of FDD - LoS-MIMO 4x4 showing two base stations with two antennas each. The distance between the antennas on each base station is labeled 'D=Optimal separation'. Arrows indicate signal paths between the antennas of the two base stations. - -Figure 10-20 4x4 Multiplexing with LoS MIMO and XPIC - -### Orbital Angular Momentum - -OAM is a new transmission mechanism allowing multiplexing multiple streams simultaneously over the same frequency channel without the limitation imposed by the optimum separation distance of antennas in the LoS MIMO. Using different antennas, multiple OAM signals with different spiral phase front (mode) can be transmitted. OAM modes are orthogonal of each other. A pragmatic OAM system, uses uniform circular antenna array while the OAM signal is generated at the base band as illustrated in the Figure 10-21. - -![Diagram of Orbital Angular Momentum transmission. On the left, two 'MOD' blocks feed into a 'MUX (8x8 DFT)' block, which is labeled '*DFT : Discrete Fourier Transform'. The output of the MUX is an '8-element UCA' (Uniform Circular Array) represented by a circle of 8 dots. An arrow points from the UCA to a circle containing eight OAM modes labeled 'mode 0', 'mode +1', 'mode +2', 'mode +3', 'mode -1', 'mode -2', 'mode -3', and 'mode 0'. Below this, five specific modes are shown as spiral phase fronts: '< mode #0>' (0°), '< mode #1>' (45°), '< mode #2>' (90°), '< mode #3>' (135°), and '< mode #4>' (180°). Each mode is accompanied by a formula: '45° x 0 = 0°', '45° x 1 = 45°', '45° x 2 = 90°', '45° x 3 = 135°', and '45° x 4 = 180°'.](b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg) - -Diagram of Orbital Angular Momentum transmission. On the left, two 'MOD' blocks feed into a 'MUX (8x8 DFT)' block, which is labeled '\*DFT : Discrete Fourier Transform'. The output of the MUX is an '8-element UCA' (Uniform Circular Array) represented by a circle of 8 dots. An arrow points from the UCA to a circle containing eight OAM modes labeled 'mode 0', 'mode +1', 'mode +2', 'mode +3', 'mode -1', 'mode -2', 'mode -3', and 'mode 0'. Below this, five specific modes are shown as spiral phase fronts: '< mode #0>' (0°), '< mode #1>' (45°), '< mode #2>' (90°), '< mode #3>' (135°), and '< mode #4>' (180°). Each mode is accompanied by a formula: '45° x 0 = 0°', '45° x 1 = 45°', '45° x 2 = 90°', '45° x 3 = 135°', and '45° x 4 = 180°'. - -Figure 10-21 Orbital Angular momentum transmission - -An OAM system with 8 Uniform Circular Array UCA antenna elements allows the transmission of 16 orthogonal streams resulting in capacity of around 105Gbps. [200] - -### Bands & Carriers Aggregation (BCA) - -BCA joins different channels that may be even in different bands, providing a single big capacity pipe. Lower band will provide capacity pipe's segment with high availability, while higher band the best effort capacity pipe segment. Packets may be adaptively re-routed among different channels according to their priority and channels condition. - -![Figure 10-22: Bands and carrier aggregation concept and benefits. The diagram shows the flow from Traffic and Services QoS through a Carrier aggregation engine, which uses Channels conditions to select from Frequency band 1 (channels 1, 2, ..., N) and Frequency band 2. These are then processed by Radio channels. On the right, a BCA (Bands and Carriers Aggregation) link is shown between two antennas, utilizing a Lower Band (V, H) and an E-Band.](638a308af25f1f56b4456a1fc503f161_img.jpg) - -Figure 10-22: Bands and carrier aggregation concept and benefits. The diagram shows the flow from Traffic and Services QoS through a Carrier aggregation engine, which uses Channels conditions to select from Frequency band 1 (channels 1, 2, ..., N) and Frequency band 2. These are then processed by Radio channels. On the right, a BCA (Bands and Carriers Aggregation) link is shown between two antennas, utilizing a Lower Band (V, H) and an E-Band. - -Figure 10-22 Bands and carrier aggregation concept and benefits - -One of the most valuable approach is 15/18/23 GHz with E-Band where dual band antennas are available: - -- Links up to 7-10Km are feasible. Capacity may even exceed 10Gbps -- High spectral efficiency obtained because E-Band can reach longer links than in traditional approach. - -BCA among two MW bands is another variant when distance becomes more challenging i.e.: rural application. - -### Geographical spectral efficiency: Dense reuse of channels - -To better exploit the scarce resource (spectrum) it is advisable to increase not only the single channel spectral efficiency but also the channel reusability in a given area, guaranteeing the “interference free operation”. - -Nodal configuration is the key point to understand the concept of geographical spectral efficiency. Better antenna class are introduced (e.g. ETSI Class 4), reducing significantly the minimum angle between two links using the same/adjacent channels (angle discrimination). Cross polar (XPIC) can also be used in reducing angle discrimination. - -Co-Channel Interference Canceller (CCIC) further improve the re-use of channels with very narrow angle discrimination. - -![Figure 10-23: Increase nodal capacity is now easy with no additional spectrum with XPIC. The diagram shows a central node with four outgoing links. The top two links use channel f1 (green boxes). The bottom two links use channel f2 (orange boxes). This illustrates the reuse of channels f1 and f2 at the same node, enabled by XPIC.](a6f9ef297168667527ab18da412f917d_img.jpg) - -Figure 10-23: Increase nodal capacity is now easy with no additional spectrum with XPIC. The diagram shows a central node with four outgoing links. The top two links use channel f1 (green boxes). The bottom two links use channel f2 (orange boxes). This illustrates the reuse of channels f1 and f2 at the same node, enabled by XPIC. - -Figure 10-23 Increase nodal capacity is now easy with no additional spectrum with XPIC - -When additional capacity is needed and then additional channels shall be used, CCIC permits an optimal re-use of channels with very narrow angle discrimination - -![Diagram illustrating the further increase in nodal capacity with increased spectral utilization by applying CCIC technique. It shows a central node connected to four remote nodes. Each remote node is shown with two separate data streams (f1, f3 and f2, f4) being transmitted simultaneously, demonstrating the use of multiple frequency bands to increase capacity.](7f7211748473542096717109ebe5a9d6_img.jpg) - -Diagram illustrating the further increase in nodal capacity with increased spectral utilization by applying CCIC technique. It shows a central node connected to four remote nodes. Each remote node is shown with two separate data streams (f1, f3 and f2, f4) being transmitted simultaneously, demonstrating the use of multiple frequency bands to increase capacity. - -**Figure 10-24 Further increase nodal capacity with increased spectral utilization by applying CCIC technique** - -Combination of the above technologies gives enhancements to microwave/mmwave capabilities as indicated below [213]. - -| MW Backhaul Technology | 56 MHz BW | 112 MHz BW | 224 MHz BW | +XPIC | + Los 2x2 MIMO | + BCA (with higher MW Band) | +BCA (with mmW Band) | -|------------------------|-----------|------------|------------|----------|----------------|-----------------------------|----------------------| -| 6-15 GHz | 0.5 Gbps | 1 Gbps | | 2 Gbps | | 3-4Gbps | | -| 18-42 GHz | 0.5 Gbps | 1 Gbps | 2 Gbps | 2-4 Gbps | 4-8 Gbps | | 4-10 Gbps | - -| mmW Backhaul Technology | 500 MHz BW | 2 GHz BW | 4 GHz BW | +XPIC | +LOS 2x2 MIMO/OAM | -|-------------------------|------------|-----------|-----------|-----------|-------------------| -| V-band (60GHz) | | >4 Gbps | | | | -| E-band (70/80GHz) | 3.2 Gbps | 12.8 Gbps | | 25.6 Gbps | 51.2 Gbps | -| W-band (100GHz) | 3.2 Gbps | 12.8 Gbps | 25.2 Gbps | 51.2 Gbps | 102.4 Gbps | -| D-band (150GHz) | 3.2 Gbps | 12.8 Gbps | 25.6 Gbps | 51.2 Gbps | 102.4 Gbps | - -**Table 5 Microwave/mmwave enhancements** - -#### 10.2.4.3 Support for packet - -MW or mmW links are characterised by their physical capabilities related to the combination of link length, capacity, frequency band and availability, which is independent of their network layer functionalities and use cases. These radio links are usually capable of multiplexing various types of traffic over single radio channel and can be equipped with multiple network interfaces including FE/GbE (RJ45, SFP) and CWDM filter support. Various packet functions are also supported as optional features and can be configured by network operators, such as L2 pass through, feature rich L2 switch with ERPS, H-QoS among others enabling carrier grade Ethernet services. MPLS-TP is also supported for layer 2 services, and for timing and synchronisation support includes 1588v2 (TC, BC) and SyncE. - -These network features make MW and mmwave radio popular in Backhaul and Xhaul network infrastructure by themselves. They are also used as a complementing technology to other physical technologies where the MW and mmwave radio links can be used as part of network segments to close links where underlying technology infrastructure is missing or absent or as a back-up in mission critical part of the network. The section below illustrates some use case examples where MW and mmwave radio links are utilised. - -![O-RAN Alliance logo](2ee5c15604dce579e4f931d4566ce708_img.jpg) - -O-RAN Alliance logo - -#### 10.2.4.4 Topology example use cases - -##### **Dense urban/urban (C-RAN plus D-RAN support) case** - -The figure below illustrates an example of transport network use in an end-to-end network with C-RAN infrastructure used to provide network coverage in a Dense Urban/Urban environment with support for some D-RAN sites. - -In this network, the core is connected to the O-CU via a Backhaul aggregate and pre-aggregate transport part of the network. At the aggregation/pre-aggregation transport network, a bandwidth of 10G or more will be required, mainly 25G or more. MW and mmW will be used as alternative (ring closer) or redundant circuit to fibre, and the application of wide-bandwidth products in the E/D/W bands will be the main focus. - -At the Midhaul transport network, MW and mmW radio equipment can be used in almost the same band as conventional Backhaul. From the transport perspective, there is little different between 5G and 4G transport networks, with additional synchronisation and delay requirements. - -![Figure 10-25: Network topology example for dense urban/urban environment with microwave and mmwave links. The diagram shows a 5G Core connected to an O-CU via a Core link (25~100G). The O-CU is connected to multiple O-DU units via Backhaul (BH) links (10~25G). The O-DU units are connected to O-RU units via Fronthaul (LLS/eCPRI) links (25G~100G). The O-RU units are connected to O-DU units via IAB (Integrated Access Backhaul) links (10~40G). The O-DU units are also connected to a Midhaul network (HLS) (3~10G).](708e4c9a044ef61f586126676eb2eeb8_img.jpg) - -``` - -graph LR - Core[5G Core] -- "Core (25~100G)" --> OCU[O-CU] - OCU -- "BH (10~25G)" --> ODU1[O-DU] - OCU -- "BH (10~25G)" --> ODU2[O-DU] - ODU1 -- "Midhaul HLS (3~10G)" --> ODU3[O-DU] - ODU3 -- "Fronthaul LLS/eCPRI (25G~100G)" --> ORU1[O-RU] - ODU3 -- "Fronthaul LLS/eCPRI (25G~100G)" --> ORU2[O-RU] - ORU1 -- "IAB (10~40G)" --> ORU3[O-RU/O-DU] - ORU3 -- "IAB (10~40G)" --> ORU4[O-RU/O-DU] - ORU4 --> ORU5[O-RU] - -``` - -Figure 10-25: Network topology example for dense urban/urban environment with microwave and mmwave links. The diagram shows a 5G Core connected to an O-CU via a Core link (25~100G). The O-CU is connected to multiple O-DU units via Backhaul (BH) links (10~25G). The O-DU units are connected to O-RU units via Fronthaul (LLS/eCPRI) links (25G~100G). The O-RU units are connected to O-DU units via IAB (Integrated Access Backhaul) links (10~40G). The O-DU units are also connected to a Midhaul network (HLS) (3~10G). - -**Figure 10-25 Network topology example for dense urban/urban environment with microware and mmwave links** - -In urban centers, high bandwidth services are required, hence Fronthaul LLS needs to be more than 25G (25-100G). In many cases, LLS is used when DU/RU are collocated in the same building. It may be in short distances. In this case, MW/mmW radio equipment is of limited application. - -Within the urban environment, some D-RAN sites may also be connected to edge site. In this case IAB (integrated Access Backhaul) base station to base station communication, which cover about 100 metres with LoS, can be used. - -##### **Rural (C-RAN) case** - -In this topology scenario, coverage in rural areas is migrated using existing fibres in a C-RAN configuration for 4G. Generalisation of equipment is made possible by upgrading CPRI links to Ethernet utilising eCPRI or IEEE1914.3 mechanism. The link capacity requirements in this case is in the range 10 to 25G. The application of MW/mmW radio equipment is used to extend coverage and other uses due to its ease of installation. - -![O-RAN Alliance logo](902f71a0cadbca9c579485eaa69effaf_img.jpg) - -O-RAN Alliance logo - -![Figure 10-26: Network topology example for rural environment with microware and mmwave links. The diagram shows a 5G Core connected to an O-CU/O-DU via a Core (25~100G) link. This O-CU/O-DU is connected to another O-CU/O-DU via a Backhaul (BH) link (10~25G). The second O-CU/O-DU is connected to multiple O-RUs via Fronthaul links (LLS/eCPRI) (10~25G). The O-RUs are connected to user equipment (UE) via microware and mmwave links. The diagram also shows WDM components and various network elements like servers and antennas.](d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg) - -Figure 10-26: Network topology example for rural environment with microware and mmwave links. The diagram shows a 5G Core connected to an O-CU/O-DU via a Core (25~100G) link. This O-CU/O-DU is connected to another O-CU/O-DU via a Backhaul (BH) link (10~25G). The second O-CU/O-DU is connected to multiple O-RUs via Fronthaul links (LLS/eCPRI) (10~25G). The O-RUs are connected to user equipment (UE) via microware and mmwave links. The diagram also shows WDM components and various network elements like servers and antennas. - -Figure 10-26 Network topology example for rural environment with microware and mmwave links. - -## 10.3 Data Centers - -Data center solutions, connectivity to the Xhaul transport infrastructure and orchestration are not in scope of this version of document. However, it is important to note the critical role Data centers play in 5G, with key components of the 5G architecture running on servers either virtualized, containerized or as bare metal located in data centers. Consequently, operators need to consider how data centers are connected to the Xhaul transport network and how end to end transport services are built that span the DC and the WAN. At a high-level two basic approaches to interconnecting DC to the Xhaul transport network are available. - -### 10.3.1 Complete separation between DC and WAN infrastructure - -This refers to data centers that are discrete from the WAN infrastructure with each domain potentially running different underlay and overlay transport network technologies. The interconnection between the two domains is via “Data Center Interconnect” (DCIs) routers. These routers reside in both the DC and WAN domains and have an awareness of the DC environment on one side and an awareness of the WAN on the other. To provision an end-to-end network service, the data center and the WAN are provisioned separately, using a cross-domain orchestrator to stitch the two separate service environments together. - -### 10.3.2 DC integrated into WAN infrastructure. - -This refers to data centers that run the same underlay and service infrastructures as the WAN. In this case, although there maybe DCIs to create underlay separation between the WAN and the DC, it is possible to treat the network service infrastructure as a single orchestration domain with WAN transport services directly configured on the Top of Rack (ToRs) devices or on soft switches / routers residing on the server themselves. - -## 11 Packet-switched underlay network – MPLS based - -This document presents two packet switched underlay technologies, the first is based on MPLS contained in this section (section 11) and the second based on SRv6 contained in section 12. An operator wishing to implement the transport architecture outlined in this document will need to select one of the two and implement the requirements outlined in the associated section. It should be - -![O-RAN Alliance logo](15faea1eb0f5fbd0d54291a786091afc_img.jpg) - -O-RAN Alliance logo - -1 noted that other transport architectures are potentially available but not covered in this revision of - 2 the document. - -3 - 4 This section outlines a packet switched underlay model based on “Multi-Protocol Label Switching” - 5 (MPLS). MPLS data plane is based on label switching but has more than one control plane - 6 technology. The first, classic approach is based on the control plane developed when MPLS was - 7 first conceived in the mid 1990s and utilizes IGPs, BGP-LU, LDP and RSVP. An emerging - 8 approach, very appropriate to mobile transport networks, is based on Segment Routing (SR) - 9 extensions to IGP and BGP, which have been developed since around 2010 and aim to simplify and - 10 minimize the number of protocols running in network, as well as reduce the state held on the TNEs. - 11 This document describes scalable, multi-domain Xhaul transport architecture that can involve - 12 domains with different MPLS control plane technologies (classic: LDP, RSVP, BGP-LU, as well as - 13 emerging: SR, SR with Flex-Algo, or SR-TE), in order to support both brownfield (extending - 14 existing mobile transport network using classic control plane with additional domains using new, - 15 emerging SR control plane) and greenfield (building new Xhaul transport network) deployment use - 16 cases. However, in order to avoid duplications with BBF technical reports documenting classic - 17 MPLS control plane in mobile transport network designs, and to keep the size of this document - 18 within reasonable limits, this document puts more focus on the new, emerging control plane based - 19 on SR. - -20 - 21 Regardless which MPLS control plane – classic or SR – is used to distribute underlay transport - 22 labels, the services are overlaid on-top. The service layer is independent from the underlaying - 23 MPLS transport layer and supports native Ethernet services and layer 3 services. - -## 25 11.1 MPLS data plane - -26 MPLS architecture relies on an MPLS data plane using MPLS encapsulated IP (for L3VPN) or - 27 Ethernet (for L2VPN/EVPN) data packets. MPLS label stack, containing potentially multiple labels, - 28 pushed on the data packet might encode various information, like for example: - -- 29 • path through the transport network (transport labels) -- 30 • entropy for load balancing on transit routers (flow or entropy labels) -- 31 • function/service on egress router (L3VPN/EVPN labels) - -32 - 33 Figure 11-1 shows examples for Ethernet based eCPRI and IP based eCPRI encapsulated in MPLS. - -![Diagram showing two MPLS encapsulation structures. The left structure shows an Ethernet frame (ETH header + Ethernet payload (eCPRI)) encapsulated with an EVPN label and a Transport label. The right structure shows an IP packet (IP header + IP payload (eCPRI)) encapsulated with an L3VPN label and a Transport label.](149826281804ec51b5cca5603c88b23b_img.jpg) - -34 - -| | | -|--------------------------|--------------------| -| Transport label | Transport label | -| EVPN label | L3VPN label | -| ETH header | IP header | -| Ethernet payload (eCPRI) | IP payload (eCPRI) | - -Diagram showing two MPLS encapsulation structures. The left structure shows an Ethernet frame (ETH header + Ethernet payload (eCPRI)) encapsulated with an EVPN label and a Transport label. The right structure shows an IP packet (IP header + IP payload (eCPRI)) encapsulated with an L3VPN label and a Transport label. - -35 - 36 **Figure 11-1 MPLS encapsulation of Ethernet frame or IP packet** - -37 - 38 To support packet switching transport with MPLS data plane, the transport device will need to - 39 support: - -![O-RAN Alliance logo](8a19b7d36c6b4ac9467a138b1faa3b93_img.jpg) - -O-RAN Alliance logo - -- 1 [R1]: MUST support MPLS architecture as defined by “Multiprotocol Label Switching - 2 Architecture”, RFC 3031 [62]. - 3 [R2]: MUST support MPLS label stack encoding defined by “MPLS Label Stack Encoding” RFC - 4 3032 [63]. - 5 [R3]: MUST support TTL processing defined by “Time To Live (TTL) Processing in Multi- - 6 Protocol Label Switching (MPLS) Networks”, RFC 3443 [70]. - 7 [D1]: SHOULD support MPLS Explicit Null operation defined by “Removing a Restriction on the - 8 use of MPLS Explicit NULL”, RFC 4182 [79]. - 9 - -## 10 11.2 MPLS control plane - -11 The MPLS control plane is used to distribute information required to deliver the packets through the - 12 transport network. It typically includes following information: - 13 - -- 14 • Topological information (nodes and links in transport network, including attributes, like - 15 metrics, IP prefixes administrative groups, SRLGs, etc., associated with these topological - 16 elements) -- 17 • IP prefixes -- 18 • MPLS transport label information - -19 Based on the collected information, control plane responsibility is to - 20 - -- 21 • calculate paths (shortest path to the destination, or path fulfilling certain administrative - 22 constraints, which are not necessarily the shortest paths – for example low latency path) -- 23 • program data plane with information required to forward the MPLS packets through the - 24 network (next-hops, MPLS labels stack manipulation rules – pop, push, swap) -- 25 • calculate and program in the data plane backup paths required for rapid protection - 26 mechanisms (fast re-route – FRR) - -27 - 28 - 29 In a packet switched transport network consisting of a large number of routers, a mix of WAN and - 30 data centers components, the need to support traffic engineering, the underlay control plane is a - 31 typically a collection of independent routing domains that interact in a collaborate fashion. - 32 - -![Figure 11-2 MPLS packet switched underlay architecture diagram. The diagram shows a network architecture with a 'Distributed PCE Layer' at the top containing three 'PCE' nodes. Below this is a transport network consisting of 'CSR' (Customer Service Router) nodes connected to 'O-RU' (Open Radio Unit) nodes. The transport path includes 'ACCESS' (connected to CSR), 'HSR' (High Speed Router), 'AGGREGATION' (connected to HSR), 'TRANSPORT CORE' (consisting of two core routers), 'AGGREGATION' (connected to the core), 'HSR' (connected to the second aggregation), 'ACCESS' (connected to the second HSR), and another 'CSR' node. Green arrows labeled 'PCEP' connect the PCEs to the CSRs. Red arrows labeled 'BGP-LS' and 'Telemetry' connect the CSRs to the PCEs. A thick green line at the bottom represents the 'End-to-End Label Switched Path'.](4bd793f76f6a26ed6c66127dbbef21f8_img.jpg) - -Figure 11-2 MPLS packet switched underlay architecture diagram. The diagram shows a network architecture with a 'Distributed PCE Layer' at the top containing three 'PCE' nodes. Below this is a transport network consisting of 'CSR' (Customer Service Router) nodes connected to 'O-RU' (Open Radio Unit) nodes. The transport path includes 'ACCESS' (connected to CSR), 'HSR' (High Speed Router), 'AGGREGATION' (connected to HSR), 'TRANSPORT CORE' (consisting of two core routers), 'AGGREGATION' (connected to the core), 'HSR' (connected to the second aggregation), 'ACCESS' (connected to the second HSR), and another 'CSR' node. Green arrows labeled 'PCEP' connect the PCEs to the CSRs. Red arrows labeled 'BGP-LS' and 'Telemetry' connect the CSRs to the PCEs. A thick green line at the bottom represents the 'End-to-End Label Switched Path'. - -33 - 34 **Figure 11-2 MPLS packet switched underlay architecture** - 35 - -![O-RAN ALLIANCE logo](cad9f65638b7c839304d8939cb11e6d2_img.jpg) - -O-RAN ALLIANCE logo - -Figure 11-2 illustrates how a large packet switched MPLS transport infrastructure might be designed and how different components interact. It should be noted that not all these components are required, and some serve the same purpose but in different ways. - -1. Each routing domain has an IGP for internal connectivity. -2. Each routing domain has a protocol for distributing label information. It could be SR extension to an IGP, or could be as well legacy protocol like RSVP or LDP. Architecture supporting legacy MPLS transports (LDP and/or RSVP) is especially important in brown-field deployments, with legacy MPLS transport already in place. -3. Mechanisms to calculate Traffic Engineered paths within a routing domain. Depending on scale, TE paths can be calculated on the transport devices themselves (distributed constrained shortest path first – D-CSPF – calculation), calculation can be off-loaded from less powerful transport devices to more powerful transport devices (on-box PCE), or even dedicated servers could be deployed (off-box PCE). The diagram shows a distributed “Path Computation Element” (PCE) layer with “Path Computation Element Protocol” PCEP running between the edge nodes and the PCE -4. Mechanism to establish end-to-end MPLS LSPs between IGP domains. To achieve highly scalable architecture, two mechanism could be considered: Seamless MPLS Architecture, or a controller-based Architecture. Both architectures are described in more details in Section 11.5. -5. Mechanism to convey topology and network state information from the network to the PCE and other management elements. BGP Link State (BGP-LS) and Telemetry feeds are recommended tools to fulfil this requirement. - -## 11.3 Classic MPLS control plane - -The classic control plane is widely implemented, and designs and requirements are well documented in: - -- Cisco Press, MPLS and VPN Architectures, Volume 1, 420 pages, by Ivan Pepelnjak, and Jim Guichard, 2001 [207] -- Cisco Press, MPLS and VPN Architectures, Volume 2, 470 pages, by Ivan Pepelnjak, Jim Guichard, and Jeff Apcar, 2003 [208] -- O'Reilly, MPLS in the SDN Era, 890 pages, by Antonio Sánchez-Monge, and Krzysztof Grzegorz Szarkowicz, 2015 [209] - -The application of classic MPLS control plane protocols (IGP, LDP, RSVP, BGP) to the mobile transport networks is defined by Broadband Forum (BBF) in following technical reports: - -- BBF TR-221: Technical Specification for MPLS in Mobile Backhaul Networks, 99 pages, Oct 2011u [210] -- BBF TR-221, Amd.1: Technical Specifications for MPLS in Mobile Backhaul Networks, 24 pages, Nov 2013 [211] -- BBF TR-221, Amd.2: Technical Specifications for MPLS in Mobile Backhaul Networks, 22 pages, Sep 2017 [212] - -### 11.3.1.1 LDP base requirements - -If an operator wishes to use LDP MPLS control plane in some routing domain, then the routing equipment in that routing domain will require: - -![O-RAN ALLIANCE logo](76cef7549f47c105c5b01ab9b5957de8_img.jpg) - -O-RAN ALLIANCE logo - -- [D2]:** SHOULD support constraint-based LSP setup using LDP defined by “Constraint-Based LSP Setup using LDP”, RFC 3212 [67] -**[R4]:** MUST support LDP state machine defined by “LDP State Machine”, RFC 3215 [68] -**[D3]:** SHOULD support graceful restart mechanism for LDP defined by “Graceful Restart Mechanism for Label Distribution Protocol”, RFC 3478 [72] -**[R5]:** MUST support LDP defined by “LDP Specification”, RFC 5036 [94] -**[D4]:** SHOULD support LDP extension for inter-area label switched paths defined by “LDP Extension for Inter-Area Label Switched Paths (LSPs)”, RFC 5283 [98] -**[D5]:** SHOULD support LDP IGP synchronization defined by “LDP IGP Synchronization”, RFC 5443 [110] -**[D6]:** SHOULD support LDP capabilities defined by “LDP capabilities”, RFC 5561 [113] - -### 11.3.1.2 RSVP base requirements - -If an operator wishes to use RSVP MPLS control plane in some routing domain, then the routing equipment in that routing domain will require: - -- [R6]:** MUST support “Resource ReSerVation Protocol (RSVP)”, RFC 2205 [46], RFC 2209 [47], RFC 2210 [48] -**[R7]:** MUST support “RSVP Diagnostic Messages”, RFC 2745[55] -**[R8]:** MUST support “RSVP Refresh Overhead Reduction Extensions”, RFC 2961[60] -**[D7]:** SHOULD support “RSVP Cryptographic Authentication—Updated Message Type Value”, RFC 3097 [64] -**[R9]:** MUST support “RSVP-TE: Extensions to RSVP for LSP Tunnels”, RFC 3209 [66] -**[D8]:** SHOULD support “Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)”, RFC 3477 [71] -**[R10]:** MUST support “Traffic Engineering (TE) Extensions of OSPF Version 2”, RFC 3630 [74] -**[D9]:** SHOULD support “Fast Reroute Extensions to RSVP-TE for LSP Tunnels”, RFC 4090 [77] -**[D10]:** SHOULD support “OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)”, RFC 4203 [83] -**[D11]:** SHOULD support “Node-ID Based Resource Reservation Protocol (RSVP) Hello”, RFC 4558 [86] -**[R11]:** MUST support “Record Route Object (RRO) Node-Id Sub-Object”, RFC 4561[88] -**[R12]:** MUST support “IS-IS Extensions for Traffic Engineering”, RFC 5305 [103] -**[D12]:** SHOULD support “Traffic Engineering Extensions to OSPF Version 3”, RFC 5329 [106] -**[R13]:** MUST support Encoding of Attributes for MPLS LSP Establishment Using Resource Reservation Protocol Traffic Engineering (RSVP-TE), RFC 5420 [108] -**[R14]:** MUST support “Label Switched Path (LSP) Attribute in the Explicit Route Object (ERO)”, RFC 7570 [126] -**[D13]:** SHOULD support “Techniques to Improve the Scalability of RSVP-TE Deployments”, RFC 8370 [139] - -![O-RAN Alliance logo](48bd33b4281a86fca8d1147e46a766e6_img.jpg) - -O-RAN Alliance logo - -1 **[D14]: SHOULD** support “Signaling RSVP-TE Tunnels on a Shared MPLS Forwarding Plane”, - 2 RFC 8577 [147] - -3 **[D15]: SHOULD** support “Refresh-Interval Independent RSVP Fast Reroute Facility Protection”, - 4 RFC 9705 [173] - -## 5 11.4 SR/MPLS control plane - -6 The following section outlines the control plane requirements for SR/MPLS environment. - -### 7 11.4.1 Interior Gateway Protocol (IGP) for SR/MPLS - -8 The distribution of labels, rapid convergence and distribution of traffic engineering information and - 9 optional calculation of TE optimized transport planes in a single SR domain is done by a link-state - 10 IGP, in the form of either IS-IS or OSPF, with suitable SR enhancements. This document separately - 11 outlines the requirements for IS-IS and OSPF with support for TiLFA for fast convergence and - 12 optional support for flex-algorithm for the creation of multiple transport planes optimised for - 13 different criteria and potentially using different topologies. - -14 - 15 SR/MPLS requires at least one IGP with SR awareness per routing domain or autonomous system. - 16 There are two IGPs that support SR/MPLS; ISIS or OSPF. They are both link-state protocols and - 17 have similar capabilities but there are operational differences which is beyond the scope of this - 18 document. - -19 - 20 The IGP provides internal connectivity within a routing domain. The size of a routing domain is - 21 determined by technical, operational and organizational considerations, such as protocol scalability - 22 and spans of control. In large networks, such as a 5G infrastructure, extending from the access to - 23 the transport core, it is very common to see multiple autonomous systems, IGPs and segmentation - 24 within the IGPs. - -25 - 26 In an SR/MPLS environment the IGP is responsible for distributing node, prefix and label - 27 information to all nodes within the routing domain and for calculating the “Routing Information - 28 Base” (RIB) and the Label Forwarding Information Base (LFIB) on each TNE. Optionally it can - 29 provide fast convergence mechanisms and distribute traffic engineering attributes within the domain - 30 and build multiple transport planes. Both IS-IS and OSPF have facilities to create a hierarchical - 31 routing structure within a routing domain using levels and areas respectively. They also have the - 32 facility to bring external routing information into a routing domain and push its routing information - 33 into other routing domains using route redistribution. - -34 - 35 Note: There are other techniques to achieve route re-distribution between routing domains, such as - 36 BGP and centralised SDN controllers. - -37 - 38 Note: When looking at SR/MPLS IGP requirements there are sets of requirements for ISIS and - 39 OSPF. Operators need to follow the requirements associated with IGPs they are using within their - 40 network infrastructure. - -#### 41 11.4.1.1 Topology Independent Loop Free Alternative (TiLFA) - -42 In the SR/MPLS underlay design outlined in this document, TiLFA can be used to achieve fast IGP - 43 convergence in the event of a network failure. Topology Independent Loop Free Alternative as - 44 defined “Topology Independent Fast Reroute” using Segment Routing (draft ietf-rtgwg-segment- - 45 routing-ti-lfa [185]) is an IGP capability supported by Segment Routing that provides a local repair - -mechanism that achieves 100% coverage within a routing domain against links, nodes and SRLGs failures with convergence times, once failure detection has occurred, H/W dependent but typically less than 50ms. - -For each destination in the network, TI-LFA pre-installs a backup forwarding entry for each protected destination ready to be activated upon detection of the failure of a link used to reach the destination. TI-LFA provides protection in the event of any one of the following: single link failure, single node failure, or single SRLG failure. In link failure mode, the destination is protected assuming the failure of the link. In node protection mode, the destination is protected assuming that the neighbor connected to the primary link has failed. In SRLG protecting mode, the destination is protected assuming that a configured set of links sharing fate with the primary link has failed (e.g. a linecard or a set of links sharing a common transmission pipe). The mechanics of the TiLFA in an SR/MPLS environment at failure is shown in Figure 11-3 and upon convergence in Figure 11-4. One of the key advantages of TiLFA over some other fast convergence mechanisms, not well illustrated in the example below, is that the TiLFA backup path is the same as the post convergence path, thus minimising micro-loops that can occur as IGPs converge. - -![Diagram illustrating TiLFA at failure with SR/MPLS. The network topology shows a central node (1) connected to two Customer Edge (CE) nodes and two other nodes (2 and 5). Node 2 is connected to node 3, which is connected to another CE node. Node 5 is connected to node 4, which is also connected to node 3. A link failure is indicated by a red circle with a slash on the link between node 2 and node 3. Green arrows show the backup path: CE -> 1 -> 5 -> 4 -> 3. Node 1 has a UDP header with SA: 6.6.6.6, DA: 7.7.7.7, Port: UDP. Node 2 has an MPLS header (345) and a UDP header (SA: 6.6.6.6, DA: 7.7.7.7, Port: UDP). Node 5 has an MPLS header (541), an MPLS header (345), and a UDP header (SA: 6.6.6.6, DA: 7.7.7.7, Port: UDP). Node 4 has an MPLS header (345) and a UDP header (SA: 6.6.6.6, DA: 7.7.7.7, Port: UDP).](b87818c8505328b198d035761bbc3f2d_img.jpg) - -Failure - -Diagram illustrating TiLFA at failure with SR/MPLS. The network topology shows a central node (1) connected to two Customer Edge (CE) nodes and two other nodes (2 and 5). Node 2 is connected to node 3, which is connected to another CE node. Node 5 is connected to node 4, which is also connected to node 3. A link failure is indicated by a red circle with a slash on the link between node 2 and node 3. Green arrows show the backup path: CE -> 1 -> 5 -> 4 -> 3. Node 1 has a UDP header with SA: 6.6.6.6, DA: 7.7.7.7, Port: UDP. Node 2 has an MPLS header (345) and a UDP header (SA: 6.6.6.6, DA: 7.7.7.7, Port: UDP). Node 5 has an MPLS header (541), an MPLS header (345), and a UDP header (SA: 6.6.6.6, DA: 7.7.7.7, Port: UDP). Node 4 has an MPLS header (345) and a UDP header (SA: 6.6.6.6, DA: 7.7.7.7, Port: UDP). - -Figure 11-3 TiLFA at failure with SR/MPLS - -1 - -## Converged - -![Diagram illustrating post convergence traffic flow with SR/MPLS. The network consists of a central node (1) connected to two Customer Edge (CE) nodes and two other nodes (2 and 3). Node 1 is connected to CE on the left and node 2 above it. Node 1 is also connected to node 5 below it. Node 5 is connected to node 4 to its right. Node 4 is connected to node 3 above it. Node 3 is connected to CE on the right. A green arrow indicates the traffic flow from the left CE, through node 1, then through node 5, node 4, and node 3 to the right CE. Two packet diagrams are shown. The first packet at node 1 shows SA: 6.6.6.6, DA: 7.7.7.7, Port: UDP, and UDP Header/Data. The second packet at node 4 shows MPLS: 345, SA: 6.6.6.6, DA: 7.7.7.7, Port: UDP, and UDP Header/Data.](e5ded42f8e352da02ee86cb55550c45d_img.jpg) - -Diagram illustrating post convergence traffic flow with SR/MPLS. The network consists of a central node (1) connected to two Customer Edge (CE) nodes and two other nodes (2 and 3). Node 1 is connected to CE on the left and node 2 above it. Node 1 is also connected to node 5 below it. Node 5 is connected to node 4 to its right. Node 4 is connected to node 3 above it. Node 3 is connected to CE on the right. A green arrow indicates the traffic flow from the left CE, through node 1, then through node 5, node 4, and node 3 to the right CE. Two packet diagrams are shown. The first packet at node 1 shows SA: 6.6.6.6, DA: 7.7.7.7, Port: UDP, and UDP Header/Data. The second packet at node 4 shows MPLS: 345, SA: 6.6.6.6, DA: 7.7.7.7, Port: UDP, and UDP Header/Data. - -**Figure 11-4 Post convergence traffic flow with SR/MPLS** - -2 - -3 - -4 - -5 - -### 11.4.1.2 IGP Flexible-Algorithm - -6 - -7 - -8 - -9 - -10 - -11 - -12 - -13 - -14 - -15 - -16 - -17 - -18 - -19 - -20 - -21 - -22 - -In the SR/MPLS underlay design outlined in this document Flexible Algorithm can be used to within an IGP domain to provide an IGP based traffic engineering facility. Flexible-Algorithm is an IGP based traffic engineering technique that permits multiple forwarding tables to be created in the IGP based on operator programmed criteria. It is a simple, automatic way, in which a packet switched transport network can be traffic engineered, using only the IGP, to create different transport planes designed to meet specific operator defined criteria. - -Standard ISIS and OSPF use the IGP metric on links and the “Shortest Path First” (SPF) algorithm to calculate the “best” path between an ingress and egress point in the network. For many services this approach is sufficient, however this approach cannot, for example, take into account real-time link latency, utilization, packet loss and whether an ECMP path shares links using the same underlying fibre ducts. - -IGP Flex-Algo, defined in RFC 9350 [162] is an IGP based Segment Routing traffic engineering capability, that enables an operator to define their own custom algorithm, based on a wide range of variables including: link latency, packet loss, bandwidth, affinity and shared risk link groups (SRLG), to achieve a specific forwarding aim. This is illustrated in Figure 11-5. - -![Figure 11-5: Flex-algo example with three topologies. The diagram shows a central mesh network with 10 nodes (0-9). Node 0 is black, nodes 1-3 are green, nodes 4-6 are red, and nodes 7-9 are grey. Three arrows point to different topologies derived from this mesh: 1. Algo 0 (Default forwarding): Shows the full mesh with all nodes and links. 2. Algo 128 (delay optimized): Shows a path from node 0 (green) through nodes 1, 2, 3, and 9 (all green) to node 5 (red). 3. Algo 129 (security optimized): Shows a path from node 0 (red) through nodes 5, 6, 7, 8, and 9 (all red) to node 3 (green).](b1784a5cbeeb3d9fb9e60b333019c721_img.jpg) - -Figure 11-5: Flex-algo example with three topologies. The diagram shows a central mesh network with 10 nodes (0-9). Node 0 is black, nodes 1-3 are green, nodes 4-6 are red, and nodes 7-9 are grey. Three arrows point to different topologies derived from this mesh: 1. Algo 0 (Default forwarding): Shows the full mesh with all nodes and links. 2. Algo 128 (delay optimized): Shows a path from node 0 (green) through nodes 1, 2, 3, and 9 (all green) to node 5 (red). 3. Algo 129 (security optimized): Shows a path from node 0 (red) through nodes 5, 6, 7, 8, and 9 (all red) to node 3 (green). - -**Figure 11-5 Flex-algo example with three topologies** - -This enables an operator, using a single IGP instance, to build multiple forwarding tables within an SR/MPLS underlay network based on different optimization criteria. The base forwarding instance is still based on IGP metrics, but an operator can build additional IGP Traffic engineered forwarding tables based, for example on lowest latency or avoiding certain links or a combination of the two. - -The requirements to support flex-algorithm are all associated with the IGP requirements and contained in sections 11.4.1.3 and 11.4.1.4 - -#### 11.4.1.3 IS-IS SR/MPLS base requirements - -If an operator wishes to use IS-IS to support SR/MPLS with TiLFA and optionally flexible Algorithm (flex-algo) then a TNE providing the packet switching function will require: - -**[R15]:** If IPv4 control plane is used, MUST support Routing IPv4 with ISIS, as defined in ISO/IEC 10589 [215], RFC 1195 [44], RFC 3719 [75] - -**[R16]:** If IPv6 control plane is used, MUST support Routing IPv6 with ISIS, as defined in Routing IPv6 with ISIS, RFC5308 [104] - -**[R17]:** MUST support “IS-IS Extensions for Segment Routing”, RFC 8667 [152] - -**[D16]:** SHOULD support “Signaling Maximum SID Depth (MSD) Using IS-IS”, RFC 8491 [144] - -**[D17]:** SHOULD support “IGP Flexible Algorithm”, RFC 9350 [162] - -**[R18]:** MUST support IS-IS TE Extensions, RFC5305 [103] and RFC7810 [128] - -**[D18]:** SHOULD support “Topology Independent Fast Reroute using Segment Routing”, draft-ietf-rtgwg-segment-routing-ti-lfa [185] - -**[R19]:** MUST support ISIS cryptographic extensions as defined in RFC5310 [105] - -![O-RAN Alliance logo](8212253dda29ea0f382e879cda1715a1_img.jpg) - -O-RAN Alliance logo - -**[R20]:** MUST support Domain-Wide Prefix Distribution with Two-Level IS-IS as defined in RFC5302 [101]. - -**[R21]:** MUST support Three-Way Handshake for IS-IS Point-to-Point Adjacencies as defined in RFC5303 [102] - -**[D19]:** SHOULD support purge originator identification TLV for IS-IS as defined in RFC6232 [117] - -#### 11.4.1.4 OSPF SR/MPLS basic requirements - -If an operator wishes to use OSPF (v2 or v3) to support SR/MPLS with TiLFA and optionally flexible Algorithm (flex-algo) then a TNE providing the packet switching function will require: - -**[R22]:** If IPv4 control plane is used, MUST support OSPFv2 as defined in RFC2328 [49]. - -**[R23]:** If IPv6 control plane is used, MUST support OSPFv3 as defined in RFC5340 [107] and RFC 5838 [114]. - -**[R24]:** MUST support “OSPFv3 Extensions for Segment Routing”, RFC 8666 [151] - -**[D20]:** SHOULD support “Signalling Maximum SID Depth (MSD) Using OSPF,” RFC 8476 [143] - -**[D21]:** SHOULD support “IGP Flexible Algorithm”, RFC 9350 [162] - -**[R25]:** MUST support “OSPF TE Extensions”, as defined in RFC3630 [74] and RFC 7471 [124] - -**[D22]:** SHOULD support Topology Independent Fast Reroute using Segment Routing “draft-ietf-rtgwg-segment-routing-ti-lfa [185] - -**[D23]:** SHOULD support authentication/confidentiality for OSPFv3, as defined in RFC 4552 [86] - -#### 11.4.2 SR/MPLS Traffic Engineering - -SR/MPLS supports two forms of SR policies or Traffic Engineering. Both solutions rely on the IGP to gather and convey topological and resource information around the network and optionally to an SR Path Computation Element (SR-PCE) via BGP-LS. - -##### 11.4.2.1 Segment Routing Traffic Engineering (SR-TE) - -The SR policy consists of a list of SIDs the packet needs to traverse and is programmed into the packet on the source node. The SID list can consist of a mix of prefix and adjacency SIDs. In SR this form of TE allows a path to be: - -1. Loosely source routed where some intermediate points, but not all, are specified between the ingress and egress node. Paths between these intermediate points typically use the shortest path, ECMP based routing determined by the IGP. -2. Explicitly source routed where all intermediate points and even links are specified between the ingress and egress nodes. - -![O-RAN Alliance logo](bf4c652fad7b49024d2ffb350009d799_img.jpg) - -O-RAN Alliance logo - -1 In all cases, topology information and live network status within a routing domain is distributed - 2 within a routing domain by the IGP with suitable extensions. In single routing domain environments - 3 path computation can be performed either by individual head-end routers or via a centralised “SR - 4 Path Computational Element” (SR-PCE). In multi-domain routing environments, then path - 5 computation generally occurs on a “centralised SR-PCE” component that has topology information - 6 for all domains being traversed. This function can be a standalone entity or be integrated into - 7 strategically placed TNEs. This form of traffic engineering can support loose and explicitly routed - 8 paths, low-latency paths, bandwidth-guaranteed paths, and disjoint paths. Precise TE capability - 9 depends on the capabilities of the SR-PCE component. - -#### 10 11.4.2.2 IGP Flexible Algorithm - -11 IGP Flexible-Algorithm is described in section 11.4.1.2. It is an IGP based traffic engineering - 12 technique that permits multiple logical topologies to be created in an IGP domain based on operator - 13 programmed criteria. When used in a single IGP routing domain the IGP calculates and maintains - 14 the path. The ingress node simply needs to address the packet to the MPLS label associated with the - 15 flexible algorithm. This removes the need for a head-end or centralised PCE path computation - 16 element and also keeps SID list contained in the label stack to a minimum. - -17 This works in a single IGP domain but depending on area border router and autonomous system - 18 border router capabilities can be supported in multi-domain environments based on redistribution. - -19 - 20 For flex-algo requirements for SR/MPLS, see section 11.4.1.3 and 11.4.1.4. - -### 21 11.5 Scaling the MPLS infrastructure - -22 In order to provide communication between two MPLS TNEs, end-to-end MPLS LSPs must be - 23 available between the TNEs. This implies, that unique MPLS label towards the Transport Network - 24 Equipment, which possibly resides in different routing domain, must be available. In highly scaled - 25 environment the number of potential next-hops can be high, therefore care must be taken to ensure - 26 that resources, especially forwarding plane resources, are utilized in an efficient way, while - 27 providing end-to-end MPLS connectivity. - -28 - 29 While the requirement for having unique label per remote Transport Network Equipment increases - 30 the pressure on scaling, the benefit of unique label is faster detection of remote Transport Network - 31 Equipment failure, resulting from unique underlay prefix/label withdrawal. For architectures, which - 32 can use prefix summarization for remote Transport Network Equipment reachability, like for - 33 example SRv6 architecture discussed in Section 12, such capability is missing, since remote - 34 Transport Network Equipment failure does not influence underlay summary prefix state. - -#### 35 11.5.1 Seamless MPLS architecture - -36 Seamless MPLS (draft-ietf-mpls-seamless-mpls [182]) is applicable to for both LDP/RSVP and SR - 37 based control planes. Seamless MPLS is based on following architectural aspects: - -- 38 - 39 • Transport network is divided into multiple smaller routing domains. Routing domains can be - 40 represented by separate BGP autonomous systems, or separate IGP domains (areas). Or, - 41 combination of BGP autonomous systems and IGP areas, where BGP autonomous systems - 42 are further divided with IGP areas. -- 43 • The size of each routing domain might vary, but must be chosen in such a way, that even the - 44 weakest transport device in given routing domain can participate in intra-domain routing and - -![O-RAN Alliance logo](d261c34ab67ef2c320a5b6a75ceed2c5_img.jpg) - -O-RAN Alliance logo - -intra-domain MPLS path (SR, SR-TE, Flex-Algo, RSVP, LDP) establishment without any scaling concerns. - -- Inter-domain routing and MPLS path establishment is achieved by BGP labelled unicast (BGP LU), running on top of intra-domain protocols. BGP-LU is used for both prefix distribution (PE loopbacks), as well as label distribution (labels allocated for PE loopbacks) - -This concept is outlined in Figure 11-6. - -![Figure 11-6: Seamless MPLS architecture diagram. The diagram shows a network path from O-RU units through ACCESS, PRE-AGGREGATION, AGGREGATION, CORE, and EDGE domains. In the ACCESS domain, O-RUs connect to nodes running ISIS L1 and LDP. In the PRE-AGGREGATION domain, nodes run ISIS L2 and SR-TE. In the AGGREGATION domain, nodes run SR-TE. In the CORE domain, nodes run RSVP. In the EDGE domain, nodes run BGP-LU. The diagram illustrates the flow of BGP-LU prefixes and labels across these domains, with labels being passed along in the control plane. A text box on the right explains the scaling optimization of BGP-LU.](64323b705244afc70bf77babdacb6ce5_img.jpg) - -BGP-LU distributes prefixes (router's loopbacks) together with their labels, across all domains, with following scaling optimization: - -- BGP-LU not installed in the forwarding plane (just in the control plane) → typical transport node control plane scales few times (10x) better than forwarding plane -- BGP service prefixes (L3VPN, EVPN) use automatic constrained route distribution (RFC 4684) → only required BGP service prefixes delivered -- Optionally: Outbound Route Filtering (ORF, RFC 5292) generated automatically from the next-hops of received BGP service prefixes, further decreases the scaling pressure - -Figure 11-6: Seamless MPLS architecture diagram. The diagram shows a network path from O-RU units through ACCESS, PRE-AGGREGATION, AGGREGATION, CORE, and EDGE domains. In the ACCESS domain, O-RUs connect to nodes running ISIS L1 and LDP. In the PRE-AGGREGATION domain, nodes run ISIS L2 and SR-TE. In the AGGREGATION domain, nodes run SR-TE. In the CORE domain, nodes run RSVP. In the EDGE domain, nodes run BGP-LU. The diagram illustrates the flow of BGP-LU prefixes and labels across these domains, with labels being passed along in the control plane. A text box on the right explains the scaling optimization of BGP-LU. - -Figure 11-6 Seamless MPLS architecture - -BGP-LU operation can be further optimized for enhanced scaling: - -- BGP-LU prefixes (loopbacks of remote TNE) are not installed in the forwarding table (FIB) – they are just installed in the routing table (RIB), which consumes only control plane resources. On typical transport device, control plane resources scale better than forwarding plane resources -- Service NLRIs (L3VPN, EVPN) are automatically filtered on route reflectors (not shown in Figure 11-6, for diagram simplicity), and distributed only to the TNEs requiring specific service prefixes. This is achieved with constrained route distribution. -- Only these automatically filtered service NLRIs are installed in the forwarding plane, using the BGP-LU transport label of the required BGP-LU prefix (remote TNE loopback). Therefore, usage of forwarding plane resources is highly minimized. -- Further optimization of control plane resources is possible, where TNE (PE) requests from route reflector only limited set of BGP-LU prefixes. This can be achieved with outbound route filtering (ORF) of BGP-LU prefixes with ORF filter automatically generated to allow only BGP-LU prefixes required to resolve protocol next-hops of accepted (filtered with constrained route distribution mechanism) service NLRIs. - -With Seamless MPLS architecture, ingress PE uses recursive next-hop resolution, where service NLRI received from remote PE is resolved over BGP protocol next-hop (BGP-LU loopback of remote PE), which in turn is resolved over local intra-domain MPLS tunnel (SR/SR-TE or legacy RSVP/LDP). - -![O-RAN Alliance logo](d4adfc6e910fa1c0c08db2ba4da84754_img.jpg) - -O-RAN Alliance logo - -1 If an operator wishes to use Seamless MPLS architecture for enhanced scaling of an MPLS - 2 underlay, then the transport device will require: - -3 - 4 **[R26]:** MUST support “Seamless MPLS architecture”, draft-ietf-mpls-seamless-mpls [182] (note: - 5 this is an expired IETF draft but is a widely referenced document that describes the - 6 architecture) - -7 **[R27]:** MUST support BGP Labelled Unicast (BGP-LU), as defined in RFC3107/RFC8277 - 8 [65]/[133] - -9 **[D24]:** SHOULD support Constrained Route Distribution for BGP/MPLS virtual private networks, - 10 RFC4684 [91] - -11 **[R28]:** MAY support Outbound Route Filter (ORF) for BGP, RFC5291/RFC5292 [99][100] - -12 - 13 In scenarios where seamless MPLS is operating in heterogeneous environments where some - 14 domains are LDP based and some are SR based, then a Segment Routing Mapping Server can be - 15 used to provide an interworking function between the two environments. - -16 - 17 **[D25]:** SHOULD support Segment Routing MPLS Interworking with LDP, RFC8661 [149] - -18 - 19 IETF conducts work on enhancing the Seamless MPLS architecture to support inter-domain, multi- - 20 plane (multi-color) underlay transport infrastructure, as depicted in Figure 11-7. For example, one - 21 colored underlay transport plane (represented by color ‘A’) might be optimized for low latency, - 22 while another colored underlay transport plane (represented by color ‘B’) might be optimized for - 23 high-capacity, but not necessarily low-latency. More detailed discussion about colored underlay - 24 transport planes, and mapping of slice services to these colored underlay transport planes can be - 25 found in Section 18.1. - -![Figure 11-7: Seamless MPLS architecture with colored underlay transport planes. The diagram shows a network topology with five domains: ACCESS, PRE-AGGREGATION, AGGREGATION, CORE, and EDGE. The ACCESS domain contains four O-RU units connected to an O-RAN Unit (O-RU). The PRE-AGGREGATION and AGGREGATION domains are part of AS X, while the CORE and EDGE domains are part of AS Y. The diagram illustrates the flow of traffic from the O-RUs through the domains, showing the use of ISIS L1 and ISIS L2 protocols, and the distribution of colored intra-domain tunnels (Flex- Algo, colored RSVP, colored SR-TE). The tunnels are mapped to three colored underlay transport planes: UNDERLAY A (green), UNDERLAY B (orange), and UNDERLAY C (red). The diagram also shows the use of BGP (with new IETF extensions) to distribute prefixes (router's loopbacks) for each colored underlay (transport plane across all domains). The inter-domain (end-to-end) colored BGP tunnels are tunneled inside intra-domain tunnel in each domain.](d15e2d3e8dd9157eb7f0cc120097484a_img.jpg) - -26 - -Figure 11-7: Seamless MPLS architecture with colored underlay transport planes. The diagram shows a network topology with five domains: ACCESS, PRE-AGGREGATION, AGGREGATION, CORE, and EDGE. The ACCESS domain contains four O-RU units connected to an O-RAN Unit (O-RU). The PRE-AGGREGATION and AGGREGATION domains are part of AS X, while the CORE and EDGE domains are part of AS Y. The diagram illustrates the flow of traffic from the O-RUs through the domains, showing the use of ISIS L1 and ISIS L2 protocols, and the distribution of colored intra-domain tunnels (Flex- Algo, colored RSVP, colored SR-TE). The tunnels are mapped to three colored underlay transport planes: UNDERLAY A (green), UNDERLAY B (orange), and UNDERLAY C (red). The diagram also shows the use of BGP (with new IETF extensions) to distribute prefixes (router's loopbacks) for each colored underlay (transport plane across all domains). The inter-domain (end-to-end) colored BGP tunnels are tunneled inside intra-domain tunnel in each domain. - -27 - 28 **Figure 11-7 Seamless MPLS architecture with colored underlay transport planes** - -29 - 30 To this end, within the IETF Inter-Domain Routing WG there are two active experimental IETF - 31 drafts on BGP enhancements to support this enhanced architecture. As these IETF standards - 32 mature and are found to benefit packet switched xHaul, future versions of this document may - 33 describe in detail the BGP mechanisms chosen by the IETF to convey the inter-domain multi- - 34 plane/multi-color transport information. - -1 - -2 - -## 11.5.2 Controller based network scaling architectures - -3 - -In addition to the “Seamless MPLS” approach which is an infrastructure-based scaling technique, an external controller in the form of a distributed “Path Computational Element” (PCE) could be used for scaling across multiple MPLS domains. The approach aims to simplify the underlying infrastructure by reducing interactions between domains at the infrastructure level and delegating cross domain path determination to a distributed PCE component. - -4 - -5 - -6 - -7 - -8 - -Figure 11-8 shows the general architecture with a distributed PCE layer that gathers IGP topology information from their respective domain. PCE's can exchange topology information with each other using BGP-LS. In scenarios where the headend is not able to resolve the next-hop locally, it may rely on PCE to provide an End-to-End Path when requested. The headend communicates with the PCE using Path Computation Element Protocol (PCEP). This mechanism can help save resources on CSR's contributing to overall Xhaul Network scale. - -9 - -10 - -11 - -12 - -13 - -14 - -15 - -![Figure 11-8: General concept of a controller-based architecture. The diagram shows three IGP domains (IGP Domain 0, IGP Domain 1, and IGP Domain 2) connected in a linear fashion. Each domain contains several routers (circles with arrows) and a central PCE (square box). Above each domain is a Controller (square box) connected to the PCE. The PCEs are connected to each other via BGP-LS links. The Controllers are connected to the PCEs via BGP-LS links. The headend (CSR) in IGP Domain 0 sends a PCEP based Path Computation Request and Response to the PCE. The PCE then sends a BGP-LS link to the Controller. The Controller sends a BGP-LS link to the PCE in IGP Domain 1. The PCE in IGP Domain 1 sends a BGP-LS link to the Controller in IGP Domain 1. The Controller in IGP Domain 1 sends a BGP-LS link to the PCE in IGP Domain 2. The PCE in IGP Domain 2 sends a BGP-LS link to the Controller in IGP Domain 2. The Controller in IGP Domain 2 sends a BGP-LS link to the PCE in IGP Domain 2. The PCE in IGP Domain 2 sends a PCEP based Path Computation Request and Response to the headend (CSR) in IGP Domain 2.](75d6e15345b73203451a499ee83ace47_img.jpg) - -Figure 11-8: General concept of a controller-based architecture. The diagram shows three IGP domains (IGP Domain 0, IGP Domain 1, and IGP Domain 2) connected in a linear fashion. Each domain contains several routers (circles with arrows) and a central PCE (square box). Above each domain is a Controller (square box) connected to the PCE. The PCEs are connected to each other via BGP-LS links. The Controllers are connected to the PCEs via BGP-LS links. The headend (CSR) in IGP Domain 0 sends a PCEP based Path Computation Request and Response to the PCE. The PCE then sends a BGP-LS link to the Controller. The Controller sends a BGP-LS link to the PCE in IGP Domain 1. The PCE in IGP Domain 1 sends a BGP-LS link to the Controller in IGP Domain 1. The Controller in IGP Domain 1 sends a BGP-LS link to the PCE in IGP Domain 2. The PCE in IGP Domain 2 sends a BGP-LS link to the Controller in IGP Domain 2. The Controller in IGP Domain 2 sends a BGP-LS link to the PCE in IGP Domain 2. The PCE in IGP Domain 2 sends a PCEP based Path Computation Request and Response to the headend (CSR) in IGP Domain 2. - -**Figure 11-8 General concept of a controller-based architecture** - -16 - -17 - -18 - -The figure above shows network simplification and scalability by: - -19 - -- Creating a multi domain topology, each with its own PCE Controller -- Removing extensive Route leaking and filtering requirements between IGP domains. -- Removing the need for the headend to populate its routing table with topology and routing information. -- Use Passive Stateful PCE Path Computation Request/Response as per RFC 8231 to create an end-to-end path. - -20 - -21 - -22 - -23 - -24 - -25 - -26 - -Each domain may have its own path consideration and constraints that can independently be implemented and communicated to the PCE/PCEs. PCEs can calculate end to end path based on these constraints and communicated to the headend TNE via PCEP as shown in Figure 11-9. - -27 - -28 - -29 - -30 - -![Diagram illustrating a path with domain-specific constraints using a PCE-based architecture across three IGP domains (IGP Domain 0, IGP Domain 1, and IGP Domain 2). Each domain contains multiple routers and a Controller (PCE). The PCEs are connected via BGP-LS and PCEP protocols. The path is shown as a purple line traversing the domains, with the PCEs providing domain-specific constraints.](778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg) - -Diagram illustrating a path with domain-specific constraints using a PCE-based architecture across three IGP domains (IGP Domain 0, IGP Domain 1, and IGP Domain 2). Each domain contains multiple routers and a Controller (PCE). The PCEs are connected via BGP-LS and PCEP protocols. The path is shown as a purple line traversing the domains, with the PCEs providing domain-specific constraints. - -**Figure 11-9 Path with Domain specific constraints using PCE based architecture** - -The SID list provided by the PCE to the headend is in actuality a label stack. Depending on the network size and the use-case, the SID list may exceed the platform's label stack capacity. In those cases, the SID list across domains could be further optimized by using techniques offered by one of the following two architectures. - -- Using Forwarding Adjacency (FA) between domain boundaries, with associated Adjacency SID, abstracting the path between domain boundaries -- Using SR-TE policies between domain boundaries, with associated Binding SID, abstracting the path between domain boundaries - -Both these approaches are optional architectures that could be used to further optimize the size of the label stack in controller-based solutions. - -While the PCE is shown as a separate entity in the figure above, an operator may choose to either have PCE functionality integrated into the infrastructure router(s) or use a dedicated device or devices for PCE. As long as the PCE's in the distributed PCE layer can exchange topology information and communicate with their respective PCEP clients, the positioning of PCE functionality can be a choice an operator makes based on their respective network environment. - -Following are the requirements that should be met for implementing a controller-based architecture. These additions are in addition to baseline Segment Routing and Segment Routing Traffic Engineering requirements already mentioned: - -**[R29]:** MUST support BGP Link State (BGP-LS), RFC9552 [168] - -**[R30]:** MUST Support BGP-LS Extensions for SR as per RFC9085 [157] - -**[D26]:** SHOULD support "Signaling Maximum SID Depth using Border Gateway Protocol Link-State", RFC8814 [154] - -**[R31]:** MUST support "Segment Routing Policy Architecture", RFC9256 [160] - -**[R32]:** MUST support "Path Computation Element Protocol (PCEP)", RFC5440 [109] - -![O-RAN Alliance logo](13167dabf1b789d860061e607fa23acb_img.jpg) - -O-RAN Alliance logo - -- 1 **[R33]:** MUST support PCEP for communication between CSR and PCE as per “Path Computation - 2 Element Communication Protocol (PCEP) Extensions for Segment Routing”, RFC-8664 - 3 [150] -- 4 **[D27]:** SHOULD support PCEP extension to support Segment Routing Policy Candidate Paths as - 5 per draft-ietf-pce-segment-routing-policy-cp [183] -- 6 **[D28]:** SHOULD support “PCEP Extensions for Stateful PCE”, RFC8231 [132] -- 7 -- 8 **[D29]:** SHOULD support “BGP – Link State (BGP-LS) Advertisement of IGP Traffic Engineering - 9 Performance Metric Extensions”, RFC8571 [145] -- 10 - -#### 11 11.5.2.1 Forwarding Adjacency architecture for cross domain scale - -12 Forwarding Adjacency abstracting the path between domain boundary routers is one of the ways to - 13 optimize and scale a controller based Xhaul architecture. Forwarding Adjacency architecture is - 14 based on following architectural concepts: - -15 - -- 16 • Transport network is divided into multiple smaller routing domains. Routing domains can - 17 be represented by separate BGP autonomous systems, or separate IGP domains (areas). - 18 Or, combination of BGP autonomous systems and IGP areas, where BGP autonomous - 19 systems are further divided with IGP areas. - - 20 • The size of each routing domain might vary, but must be chosen in such a way, that even - 21 the weakest transport device in given routing domain can participate in intra-domain - 22 routing and intra-domain MPLS path (SR, SR-TE, Flex-Algo, RSVP, LDP) establishment - 23 without any scaling concerns - - 24 • Head-end router (border router) of intra-domain LSP advertises the intra-domain LSP (of - 25 any kind, i.e. SR, SR-TE, Flex-Algo, RSVP, LDP) as standard link in BGP Link State - 26 (LS) topology database, with attributes similar to standard link, like for example SR - 27 Adjacency-SID, administrative group (link color, link affinity), SRLG, etc. IGP - 28 forwarding adjacency is established (RFC 4206) between domain border routers creating - 29 abstracted topology of the routing domain. - - 30 • BGP-LS (RFC 8571) is used to distribute abstracted topology. Given the fact that only - 31 border routers, and only abstracted forwarding adjacency links between these border - 32 routers are exported, the size of the topology database exported via BGP-LS is - 33 considerably smaller. BGP-LS distribution can happen in two way, depending on the - 34 overall network scale - - 35 ○ BGP-LS topology is exchanged between routers in different routing domains - - 36 ○ BGP-LS topology is exchanged between PCEs in distributed PCE layer -- 37 - -38 The first approach is more suitable for small to medium scale deployments. In this approach, any - 39 Transport Network Equipment has the detailed topology visibility of the local routing domain, and - 40 abstracted (with Forwarding Adjacencies advertised as links in BGP-LS) visibility of the remote - 41 routing domains. This significantly reduces the topology database stored on the Transport Network - 42 Equipments, therefore, in small/medium deployments PCE might not be necessary. - -43 - -44 The headend PE, based on the full topology database (detailed topology from local routing domain - 45 + topology abstracted with links representing forwarding adjacencies from remote routing - 46 domains), performs calculation of end-to-end SR-TE paths (local constrained shortest path first – - 47 CSPF – calculation). Each forwarding adjacency is represented in the resulting SR-TE label stack as - 48 single Adjacency-SID associated with given forwarding adjacency, regardless of the underlying - -![O-RAN ALLIANCE logo](49520c9e7f737cb730421eaec2c71ab0_img.jpg) - -O-RAN ALLIANCE logo - -MPLS transport used for given forwarding adjacency. At each border node, this Adjacency SID is mapped to the actual transport label stack (LDP, RSVP, SR, SR-TE) used for the given forwarding adjacency. - -This concept is outlined in Figure 11-10. - -![Figure 11-10 Forwarding Adjacency architecture diagram. It shows a network topology with four domains: ACCESS, PRE-AGGREGATION, AGGREGATION, and CORE. The ACCESS domain contains four O-RU units connected to a central node. The PRE-AGGREGATION domain contains two nodes connected by an ISIS L1 link. The AGGREGATION domain contains two nodes connected by an ISIS L2 link. The CORE domain contains two nodes connected by an ISIS L2 link. The diagram illustrates the flow of traffic from the O-RUs through the various domains, with labels indicating different types of links (ISIS L1, ISIS L2, SR-TE tunnels) and protocols (BGP-LS, ISIS + BFD). A legend on the right explains the forwarding adjacency over local LDP, RSVP, or SR/SR-TE underlay, and lists problems such as the TE database being too large for ingress PEs.](f7b2cf9e1b71dc4f900f3810646d3903_img.jpg) - -Figure 11-10 Forwarding Adjacency architecture diagram. It shows a network topology with four domains: ACCESS, PRE-AGGREGATION, AGGREGATION, and CORE. The ACCESS domain contains four O-RU units connected to a central node. The PRE-AGGREGATION domain contains two nodes connected by an ISIS L1 link. The AGGREGATION domain contains two nodes connected by an ISIS L2 link. The CORE domain contains two nodes connected by an ISIS L2 link. The diagram illustrates the flow of traffic from the O-RUs through the various domains, with labels indicating different types of links (ISIS L1, ISIS L2, SR-TE tunnels) and protocols (BGP-LS, ISIS + BFD). A legend on the right explains the forwarding adjacency over local LDP, RSVP, or SR/SR-TE underlay, and lists problems such as the TE database being too large for ingress PEs. - -Figure 11-10 Forwarding Adjacency architecture - -As further scaling optimization of this architecture, ingress PEs (typically cell site routers, with limited control plane resources required for efficient end-to-end path computation) can be off-loaded from end-to-end path computation. Distributed PCEs (Path Computation Elements) can be placed on more powerful transport devices (for example pre-aggregation or aggregation routers), or containerized/virtualized PCE function can be placed in the distributed telco cloud environment to execute end-to-end path computation duties over simplified (via forwarding adjacencies) full network topology. In this scenario, ingress PE requests from PCE on demand path computation for unresolved next-hops, as outlined in Figure 11-11. - -![Figure 11-11 Forwarding Adjacency architecture with distributed PCE layer diagram. This diagram is similar to Figure 11-10 but adds a PCE layer. Two PCE units are shown in the PRE-AGGREGATION domain. An arrow labeled 'PCEP Request' points from the ACCESS domain to one of the PCEs. Another arrow labeled 'PCEP Response: via R5 (54, 70, 20, 24, 40)' points from the PCE back to the ACCESS domain. The legend on the right updates the points to reflect the role of the PCE: the ingress PE (CSR) holds only TE for the local domain, while the PCE performs path calculation and returns the path to the ingress PE (CSR) for BGP next-hops from remote domains.](b1e7bb95fa1587d870de03df02477df4_img.jpg) - -Figure 11-11 Forwarding Adjacency architecture with distributed PCE layer diagram. This diagram is similar to Figure 11-10 but adds a PCE layer. Two PCE units are shown in the PRE-AGGREGATION domain. An arrow labeled 'PCEP Request' points from the ACCESS domain to one of the PCEs. Another arrow labeled 'PCEP Response: via R5 (54, 70, 20, 24, 40)' points from the PCE back to the ACCESS domain. The legend on the right updates the points to reflect the role of the PCE: the ingress PE (CSR) holds only TE for the local domain, while the PCE performs path calculation and returns the path to the ingress PE (CSR) for BGP next-hops from remote domains. - -Figure 11-11 Forwarding Adjacency architecture with distributed PCE layer - -If an operator wishes to use a forwarding adjacency based architecture for enhanced scaling of MPLS underlay, then the transport device will require: - -**[R34]:** MUST support “forwarding adjacency links”, RFC4206 [135] - -### 11.5.2.2 Using Binding SID (BSID) for cross domain scale - -As mentioned earlier, a controller-based architecture make use of the PCE to provides the SID list to the headend for an end-to-end path across multiple domains. If no constraints are imposed on the traffic, the SID list would consist of Area Border Routers Prefix SIDs as next hop. Traffic within the domain will use IGP to get to the next hop while utilizing well established IGP routing mechanism such as Equal Cost Multi Path (ECMP), metric based best path etc. At the ABR, the top most SID is popped and the new next hop SID/Label is exposed, starting the routing within the next IGP are or domain. The process is repeated until traffic reaches its destination. Figure 11-12 shows such behaviour between IGP Domain 0, 1 and 2. - -![Diagram illustrating the Basic SID list with no constraints across three IGP domains (0, 1, and 2). The diagram shows a path from a source router (S-R) in IGP Domain 0 to a destination router (S-R) in IGP Domain 2, passing through Area Border Routers (ABRs) in each domain. The path is controlled by a central Controller (PCE) via BGP-LS and PCEP protocols. The SID list across the path is shown as a stack of SIDs: 10, 20, 30, 40. The path is segmented into three domains: IGP Domain 0 (blue), IGP Domain 1 (yellow), and IGP Domain 2 (green). The SIDs are associated with the ABRs: 10 for the ABR in Domain 0, 20 for the ABR between Domain 0 and 1, 30 for the ABR between Domain 1 and 2, and 40 for the ABR in Domain 2.](4540c7355b250cb891be0b54b0ba25c7_img.jpg) - -Diagram illustrating the Basic SID list with no constraints across three IGP domains (0, 1, and 2). The diagram shows a path from a source router (S-R) in IGP Domain 0 to a destination router (S-R) in IGP Domain 2, passing through Area Border Routers (ABRs) in each domain. The path is controlled by a central Controller (PCE) via BGP-LS and PCEP protocols. The SID list across the path is shown as a stack of SIDs: 10, 20, 30, 40. The path is segmented into three domains: IGP Domain 0 (blue), IGP Domain 1 (yellow), and IGP Domain 2 (green). The SIDs are associated with the ABRs: 10 for the ABR in Domain 0, 20 for the ABR between Domain 0 and 1, 30 for the ABR between Domain 1 and 2, and 40 for the ABR in Domain 2. - -**Figure 11-12 Basic SID list with no constraints** - -There may be scenarios where more explicit path considerations and constraints could be required, such as using low latency path or inclusion/exclusion of certain links or node. In those scenarios, rather than provide a SID list that encompasses every link/node through the path, mechanisms such as Flex Algo could be used to optimize the SID list on the head end. Figure 11-13 shows a scenario with latency and link/node constraints across the path. In this case operator may use Flex-Algo within a domain and use the PCE controller to provide SID list to the headend accordingly. Notice while the SID depth is no different from the earlier scenario Figure 11-13) and while it still only contain prefix-SIDs of ABR as next hop label, the SID's now refer to the node's Flex-Algo Prefix SID, instead of default algo SID. Due to this, the traffic behavior is also different and the next Hop SID automatically uses the desired constraints-based path. - -![O-RAN Alliance logo](a536d26fb2c7417a5684349af394986d_img.jpg) - -O-RAN Alliance logo - -![Figure 11-13: Constraint based SID list with Flex-Algorithm. The diagram shows three IGP domains (0, 1, and 2) connected by PCEs. Domain 0 uses Default Algo - Lowest IGP Metric. Domain 1 uses Flex Algo Lowest Latency. Domain 2 uses Flex Algo Link Constraint. PCEs are connected via BGP-LS and PCEP protocols.](8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg) - -Figure 11-13: Constraint based SID list with Flex-Algorithm. The diagram shows three IGP domains (0, 1, and 2) connected by PCEs. Domain 0 uses Default Algo - Lowest IGP Metric. Domain 1 uses Flex Algo Lowest Latency. Domain 2 uses Flex Algo Link Constraint. PCEs are connected via BGP-LS and PCEP protocols. - -Figure 11-13 Constraint based SID list with Flex-Algorithm - -In scenarios where an operator is unable or unwilling to use Flex-Algo for SID list optimization, an SRTE Binding SID (BSID) could be used. A Binding SID is a fundamental component of Segment Routing network that may be used to provide SID and network scaling. A BSID is a SID that is associated with an SRTE policy's active path and is a representation of an End-to-End candidate path. BSIDs could be used to provide additional scale by using nested SRTE policies across domains. The PCE instead of providing a full path through multiple domains, may provide the headend with a path within its own domain and a BSID corresponding to the next domain. When, exposed at the domain boundaries, the BSID gets translated into another set of SID List, providing extensibility and scalability throughout the topology. This process is shown in Figure 11-14. - -![Figure 11-14: SID scaling using binding SID. This diagram compares two scenarios for an end-to-end path across three domains. The top part shows 'SID List Without Flex Algo' where a full list of SIDs (10, 20, 22, 23, 31, 32, 33, 40) is provided. The bottom part shows 'SID List with Nested BSID' where the path is represented by a smaller set of SIDs (10, 20, 90) that are translated into the appropriate domain-specific SIDs at the boundaries.](d9638e837004a4e09dbbc50b8aecbd5f_img.jpg) - -Figure 11-14: SID scaling using binding SID. This diagram compares two scenarios for an end-to-end path across three domains. The top part shows 'SID List Without Flex Algo' where a full list of SIDs (10, 20, 22, 23, 31, 32, 33, 40) is provided. The bottom part shows 'SID List with Nested BSID' where the path is represented by a smaller set of SIDs (10, 20, 90) that are translated into the appropriate domain-specific SIDs at the boundaries. - -Figure 11-14 SID scaling using binding SID - -Figure 11-14 compares the two scenarios where an End-to-End path is required with latency and link/nodes constraints along the path. The first scenario is where the PCE provides a full SID list to the headend for the entire path, with based path is required end to end. The second scenario uses a Binding, exposed at domain boundaries and then use the appropriate constrains based SID within the domain in question. - -![O-RAN ALLIANCE logo](c49b985171e8b894ea6136ed358d0b50_img.jpg) - -O-RAN ALLIANCE logo - -If an operator wishes to implement controller based architectural scaling, in addition to underlying segment-routing based transport with controllers, a device will need to support: - -**[R35]:** SHOULD support Binding SID as per RFC 9604 [171] - -## 11.6 MPLS Quality of Service - -The MPLS data plane includes a 3-bit field in the MPLS header, the TC – Traffic Class (previously EXP - Experimental) bits. These bits are assignable as a marker for QoS mechanisms in transport nodes to use as a classification and marking tool. The per-hop behavior for MPLS forwarding elements can be defined based on these markings. Because of the restricted size of the TC field, the specific markings are not standardized, but are open for individual operators to define. For a full discussion of a proposed marking scheme and QoS architecture for TNEs in Xhaul, see Chapter 14. - -## 11.7 MPLS OAM - -Basic OAM tools are Ping and Traceroute. Ping is required to test liveliness to a remote MPLS underlay destination and traceroute is required to trace paths and perform hop-by-hop fault isolation to remote MPLS underlay destination. The following capabilities are required on all TNEs. - -**[R36]:** MUST support “Detection of MPLS Data Plane Failures”, RFC8029 [129] - -**[R37]:** MUST support LSP Ping/Traceroute for SR IGP Prefix-SID and IGP Adjacency-SID with MPLS Data Plane, as defined in RFC8287 [135] - -## 11.8 IP/MPLS service infrastructure - -For IPv4, IPv6 and Ethernet services an overlay solution is used. Please refer to section 13 for a description of overlay service recommendations for a 5G Xhaul infrastructure. - -## 12 Packet-switched underlay network – SRv6 based - -This document presents two packet switched underlay technologies, the first based on MPLS contained in section 11 and the second based on SRv6 contained in this section (section 12). An operator wishing to implement the transport architecture outlined in this document will need to select one of the two and implement the requirements outlined in the associated section. It should be noted that other transport architectures are potentially available but not covered in this revision of the document. This section outlines a packet switched underlay model based on SRv6. - -SRv6 is based on the segment routing architecture as defined in RFC8402 [141]. For more information on Segment Routing see annex A. In an SRv6 infrastructure, like an MPLS environment, it is important to consider the underlay / fabric of the transport infrastructure somewhat separately from the services that run on-top of the infrastructure. The emphasis with the underlay / fabric is to provide an environment that will scale and support the services required by a 5G infrastructure. In contrast, the services infrastructure runs on-top of the underlay/fabric of the transport network and supports the different components of the 5G infrastructure (Fronthaul, Midhaul, Backhaul). - -This chapter is specific to an SRv6 underlay/fabric, its data plane, control plane and how to scale it. Although there are some similarities with an SR-MPLS environment, in terms of architecture, there - -![O-RAN Alliance logo](6efd71634730bb1daff9fcfcba9591eb_img.jpg) - -O-RAN Alliance logo - -1 are some key differences in requirements and particularly on how to scale the underlay - 2 infrastructure, which is critical in a 5G environment. - -3 - 4 The service infrastructure and how to support 5G service requirements for both SR-MPLS and - 5 SRv6 are covered in a common services section (section 13) as the technologies used and the - 6 designs have many similarities. - -## 7 12.1 SRv6 data plane - -8 SRv6 relies on an IPv6 data plane with segments defined using SIDs contained in the IPv6 header. - 9 SRv6 SIDs are specified in “Segment Routing Header” (SRH) and standardised in RFC8754 [153]. - 10 Packet switching TNEs supporting SRv6 will need to: - -11 - 12 **[R38]:** MUST support “IPv6 Segment Routing Header (SRH)” RFC8754 [153] - -13 - 14 **[R39]:** MUST support “SRv6 Network Programming”, RFC8986 [156] - -15 - 16 **[D30]:** SHOULD support “Compressed SRv6 Segment List Encoding”, RFC 9800 [177] - -## 17 12.2 SRv6 control plane - -18 The SRv6 control plane refers to routing and path control within the SRv6 underlay/fabric. This - 19 infrastructure can extend to customer devices or stop at a Provider Edge (PE) function. Its role can - 20 be summarised as learning the topology, calculation, and implementation of dynamic and explicit - 21 routes across the SRv6 infrastructure and providing rapid protection and repair mechanisms. - 22 In a packet switched transport network consisting of a large number of routers, a mix of WAN and - 23 data centers components, the need to support traffic engineering, the underlay control plane is a - 24 typically a collection of independent routing domains that interact in a collaborate fashion. - 25 - -![Figure 12-1 SRv6 underlay architecture diagram](0726a03ffb4e106eb90cd4f9283a6347_img.jpg) - -The diagram illustrates the SRv6 underlay architecture. At the top, a box labeled 'Distributed SR-PCE' contains three 'SR-PCE' units. Below this, a network topology is shown with three main components: 'IGP#1', 'IGP#2', and 'IGP#3'. 'IGP#1' and 'IGP#3' each consist of an 'Access' node (represented by a radio tower icon), an 'Aggregation' node (represented by a circle with four arrows), and a 'Transport Core' node (represented by a circle with four arrows). 'IGP#2' is a 'Transport Core' node. Arrows indicate connections: 'PCEP' from the 'SR-PCE' units to the 'Access' nodes; 'BGP-LS + Telemetry' from the 'Transport Core' nodes to the 'SR-PCE' units; and 'BGP or IGP redistribution' between the 'IGP#1', 'IGP#2', and 'IGP#3' nodes. - -Figure 12-1 SRv6 underlay architecture diagram - -26 - 27 **Figure 12-1 SRv6 underlay architecture** - -28 - 29 Figure 12-1 illustrates how a large packet-switched transport infrastructure might be designed and - 30 how different components interact. It should be noted that not all these components are required, - 31 and some serve the same purpose but in different ways. - -- 32 1. Each routing domain has an IGP for internal connectivity. - -![O-RAN Alliance logo](e3a643cd846de9aea87f9111e89d2a58_img.jpg) - -O-RAN Alliance logo - -2. Mechanisms to calculate SR policies or Traffic Engineer paths and convey them to the source nodes. Figure 12-1 shows a distributed “Path Computation Element” (PCE), with “Path Computation Element Protocol” (PCEP) running between the edge nodes and the PCE but there are other network-based mechanisms to calculate SR policies such as Flex-algo running in the IGP or head-end calculated paths. -3. Mechanisms to convey routing between IGP domains. This could be provided by summarization and redistribution, E-BGP between AS boundaries or via a multi-domain “Path Computation Element” (PCE). One of the key differences between an MPLS and IPv6 based underlay is that IPv6 enables address summarization within routing domains and also between routing domains. This makes an IPv6 based underlay network more scalable and less complex than a corresponding MPLS solution. -4. Mechanisms to convey topology and network state information from the network to the PCE and other central management elements. BGP Link State (BGP-LS) and Telemetry feeds are recommended tools to fulfil this requirement. - -### 12.2.1 Interior Gateway Protocol (IGP) for SRv6 - -SRv6 requires at least one IPv6 IGP per routing domain or autonomous system. There are two IGPs that support SRv6; ISIS for IPv6 or OSPFv3. They are both link-state protocols and have similar capabilities but there are operational differences which is beyond the scope of this document. - -The IGP provides internal connectivity within a routing domain. The size of a routing domain is determined by technical, operational and organizational considerations, such as protocol scalability and spans of control. In large networks, such as a 5G infrastructure, extending from the access to the transport core, it is very common to see multiple autonomous systems, IGPs and segmentation within the IGPs. - -In an SRv6 environment the IGP is responsible for distributing node, prefix and SID information to all nodes within the routing domain and for calculating the forward tables between these nodes. Optionally it can provide fast convergence mechanisms and distribute traffic engineering attributes within the domain and build multiple transport planes. Both IS-IS for IPv6 and OSPFv3 have facilities to create a hierarchical routing structure within a routing domain using levels and areas respectively. They also have the facility to bring external routing information into a routing domain and push routing information into other routing domains using route redistribution. - -**Note:** There are other techniques to achieve route re-distribution between routing domains, such as BGP and centralised SDN controllers. - -**Note:** When looking at SRv6 IGP requirements, there are sets of requirements for ISIS for IPv6 and OSPFv3. Operators need to follow the requirements associated with IGPs they are using within their network infrastructure. - -#### 12.2.1.1 Topology Independent Loop Free Alternative (TiLFA) - -In the SRv6 underlay design outlined in this document TiLFA can be used to achieve fast IGP convergence in the event of a network failure. Topology Independent Loop Free Alternative as defined “Topology Independent Fast Reroute” using Segment Routing [185] is an IGP capability supported by Segment Routing that provides a local repair mechanism that achieves 100% coverage within a routing domain against links, nodes and SRLGs failures with convergence times, once failure detection has occurred, H/W dependent but typically less than 50ms. - -For each destination in the network, TI-LFA pre-installs a backup forwarding entry for each protected destination ready to be activated upon detection of the failure of a link used to reach the destination. TI-LFA provides protection in the event of any one of the following: single link failure, single node failure, or single SRLG failure. In link failure mode, the destination is protected assuming the failure of the link. In node protection mode, the destination is protected assuming that the neighbor connected to the primary link has failed. In SRLG protecting mode, the destination is protected assuming that a configured set of links sharing fate with the primary link has failed (e.g. a linecard or a set of links sharing a common transmission pipe). The mechanics of the TiLFA for SRv6 at failure is shown in Figure 12-2 and upon convergence in Figure 12-3. One of the key advantages of TiLFA over some other fast convergence mechanisms, not well illustrated in the example below, is that the TiLFA backup path is the same as the post convergence path, thus minimising micro-loops that can occur as IGPs converge. - -![Diagram of TiLFA at failure with SRv6. A network of nodes 1, 2, 3, 4, 5 and CE nodes. A link failure is marked between node 2 and 3. Traffic is rerouted from node 1 to node 2, then back to node 1, then through node 5 and 4 to reach node 3.](0dfdff10c725fe9c332b07ade9d23a5e_img.jpg) - -### Failure - -The diagram shows the packet encapsulation at different stages of the network during a link failure between Node 2 and Node 3. Node 1 acts as the Point of Local Repair (PLR). - -**Packet at CE (Left)** - -| | -|-----------------| -| SA: 6.6.6.6 | -| DA: 7.7.7.7 | -| Port: UDP | -| UDP Header/Data | - -**Packet at Node 1** - -| | -|---------------------| -| SA: 2001::1 | -| DA: 2001:0:0:3:45:: | -| NH: IPv4 | -| SA: 6.6.6.6 | -| DA: 7.7.7.7 | -| Port: UDP | -| UDP Header/Data | - -**Packet at Node 2 (Rerouted)** - -| | -|---------------------------------------| -| SA: 2001::1 | -| DA: 2001:0:0:5:41:: | -| NH: RH | -| Type: 4 (SRH) | -| NH: IPv4 SL: 1 | -| Segment List:
[0]: 2001:0:0:3:45:: | -| SA: 6.6.6.6 | -| DA: 7.7.7.7 | -| Port: UDP | -| UDP Header/Data | - -**Packet at Node 5/4** - -| | -|---------------------| -| SA: 2001::1 | -| DA: 2001:0:0:3:45:: | -| NH: IPv4 | -| SA: 6.6.6.6 | -| DA: 7.7.7.7 | -| Port: UDP | -| UDP Header/Data | - -Diagram of TiLFA at failure with SRv6. A network of nodes 1, 2, 3, 4, 5 and CE nodes. A link failure is marked between node 2 and 3. Traffic is rerouted from node 1 to node 2, then back to node 1, then through node 5 and 4 to reach node 3. - -Figure 12-2 TiLFA at failure with SRv6 - -## Converged - -![Figure 12-3: Post convergence traffic flow with SRv6. The diagram shows a network path from a left CE node to a right CE node. The path goes through nodes 1, 5, 4, and 3. Node 2 is connected to node 1 but is not on the active path. A green arrow indicates the traffic flow. Packet headers are shown at two points: entering node 1 (IPv4 UDP packet) and between nodes 1 and 3 (SRv6 encapsulated packet).](ffe0fef452a0ae9a20253c319c54e13c_img.jpg) - -``` - -graph LR - CE1[CE] --- 1((1)) - 1 --- 2((2)) - 1 --- 5((5)) - 5 --- 4((4)) - 4 --- 3((3)) - 3 --- CE2[CE] - - subgraph Packet_at_Node_1 - P1[SA: 6.6.6.6 -DA: 7.7.7.7 -Port: UDP -UDP Header/Data] - end - - subgraph Packet_between_1_and_3 - P2[SA: 2001::1 -DA: 2001:0:0:3:45:: -NH: IPv4 ---- -SA: 6.6.6.6 -DA: 7.7.7.7 -Port: UDP -UDP Header/Data] - end - - linkStyle 0,2,3,4,5 stroke:green,stroke-width:2px; - -``` - -Figure 12-3: Post convergence traffic flow with SRv6. The diagram shows a network path from a left CE node to a right CE node. The path goes through nodes 1, 5, 4, and 3. Node 2 is connected to node 1 but is not on the active path. A green arrow indicates the traffic flow. Packet headers are shown at two points: entering node 1 (IPv4 UDP packet) and between nodes 1 and 3 (SRv6 encapsulated packet). - -**Figure 12-3 Post convergence traffic flow with SRv6** - -### 12.2.1.2 IGP Flexible-Algorithm - -IGP Flexible-Algorithm is an IGP based traffic engineering technique that permits multiple forwarding tables to be created in the IGP based on operator programmed criteria. It is a simple, automatic way, in which a packet switched transport network can be traffic engineered, using only the IGP, to create different transport planes designed to meet specific operator defined criteria. - -Standard ISIS for IPv6 and OSPFv3 use the IGP metric on links and the “Shortest Path First” (SPF) algorithm to calculate the “best” path between an ingress and egress point in the network. For many services this approach is sufficient, however this approach cannot, for example, take into account real-time link latency, utilization, packet loss and whether an ECMP path shares links using the same underlying fibre ducts. - -IGP Flex-Algo, defined in RFC 9350 [162] is an IGP based Segment Routing traffic engineering capability, that enables an operator to define their own custom algorithm, based on a wide range of variables including: link latency, packet loss, bandwidth, affinity and shared risk link groups (SRLG), to achieve a specific forwarding aim. This is illustrated in Figure 12-4. - -![Figure 12-4: Flex-algo example with three topologies. The diagram shows a central mesh network of 10 nodes (0-9) with various links. Three arrows point from this central network to three separate, simplified topologies below. The first topology, labeled 'Algo 0 Example: Default forwarding', shows a subset of nodes and links. The second topology, labeled 'Algo 128 Example: delay optimized', shows a different subset. The third topology, labeled 'Algo 129 Example: security optimized', shows yet another subset, with some nodes and links highlighted in red.](592f13acca3e6d5152dd4489f030d004_img.jpg) - -Figure 12-4: Flex-algo example with three topologies. The diagram shows a central mesh network of 10 nodes (0-9) with various links. Three arrows point from this central network to three separate, simplified topologies below. The first topology, labeled 'Algo 0 Example: Default forwarding', shows a subset of nodes and links. The second topology, labeled 'Algo 128 Example: delay optimized', shows a different subset. The third topology, labeled 'Algo 129 Example: security optimized', shows yet another subset, with some nodes and links highlighted in red. - -**Figure 12-4 Flex-algo example with three topologies** - -This enables an operator, using a single IGP instance, to build multiple forwarding tables within an SRv6 underlay network based on different optimization criteria. The default forwarding instance uses shortest path forwarding based on IGP metrics, but an operator can build additional IGP Traffic Engineered forwarding tables based, for example on lowest latency or avoiding certain links or a combination of the two. - -The requirements to support flex-algorithm are all associated with the IGP requirements and contained in sections 12.2.1.3 and 12.2.1.4. - -#### 12.2.1.3 ISIS for IPv6 base requirements - -If an operator wishes to use ISIS for IPv6 with TiLFA and optionally Flexible Algorithm (flex-algo) with SRv6 then the TNE will require: - -**[R40]:** MUST support routing IPv6 with ISIS as defined in RFC5308 [104]. - -**[R41]:** MUST support RFC 9352: “IS-IS Extensions to Support Segment Routing over IPv6 Data Plane” [164] - -**[R42]:** MUST support “Topology Independent Fast Reroute using Segment Routing”, draft-ietf-rtgwg-segment-routing-ti-lfa [185] - -**[R43]:** MUST support IS-IS TE Metric Extensions, as defined in RFC5305 [103] and RFC7810 [128]. - -**[D31]:** SHOULD support RFC 9350: “IGP Flexible Algorithm”, [162] - -#### 12.2.1.4 OSPFv3 basic requirements - -If an operator wishes to use OSPFv3 with TiLFA and optionally flexible Algorithm (flex-algo) with SRv6 then the TNE will require: - -![O-RAN Alliance logo](edbcecfff447173e9b62de586f536fc7_img.jpg) - -O-RAN ALLIANCE - -O-RAN Alliance logo - -**[R44]:** MUST support OSPFv3, RFC5340 [107]. - -**[R45]:** MUST support ‘‘OSPFv3 Extensions for Segment Routing over IPv6 (SRv6)’’, RFC 9513 [165] - -**[R46]:** MUST support ‘‘Topology Independent Fast Reroute using Segment Routing’’, draft-ietf-rtgwg-segment-routing-ti-lfa [185]. - -**[R47]:** MUST support OSPFv3 TE Metric Extensions, as defined in RFC5329 [106]. - -**[D32]:** SHOULD support RFC 9350: ‘‘IGP Flexible Algorithm’’ [162] - -## 12.2.2 SRv6 Traffic Engineering - -SRv6 supports two forms of SR policies or SR Traffic Engineering. Both solutions rely on the IGP to gather and convey topological and resource information around the network and optionally to a Path Computation Element (PCE) optimized for SR via BGP-LS. - -### 12.2.2.1 Segment Routing Traffic Engineering (SR-TE) - -The SR policy consists of a list of SIDs the packet needs to traverse and is programmed into the packet on the source node. The SID list can consist of a mix of prefix and adjacency SIDs. In SR this form of TE allows a path to be: - -1. Loosely source routed where some intermediate points, but not all, are specified between the ingress and egress node. Paths between these intermediate points typically use the shortest path, ECMP based routing determined by the IGP. -2. Explicitly source routed where all intermediate points and even links are specified between the ingress and egress nodes. - -In all cases, topology information and live network status within a routing domain is distributed within a routing domain by the IGP with suitable extensions. In single routing domain environments path computation can be performed either by individual head-end routers or via a centralised ‘‘SR Path Computational Element’’ (SR-PCE). In multi-domain routing environments, then path computation generally occurs on a ‘‘centralised SR-PCE’’ component that has topology information for all domains being traversed. This function can be a standalone entity or be integrated into strategically placed TNEs. This form of traffic engineering can support loose and explicitly routed paths, low-latency paths, bandwidth-guaranteed paths, and disjoint paths. Precise TE capability depends on the capabilities of the SR-PCE component. - -### 12.2.2.2 IGP Flexible Algorithm - -IGP Flexible-Algorithm is described in section 12.2.1.2. It is an IGP based traffic engineering technique that permits multiple logical topologies to be created in an IGP domain based on operator programmed criteria. When used in a single IGP routing domain the IGP calculates and maintains the path. The ingress node simply needs to address the packet to the ‘‘locator-block’’ associated with the flexible algorithm. This removes the need for a head-end or centralised PCE path computation element and also keeps SID list to a minimum. - -This works in a single IGP domain but depending on area border router and autonomous system border router capabilities can be supported in multi-domain environments based on redistribution. For flex-algo requirements in an SRv6 environment see section 12.2.1.3 and 12.2.1.4. - -![O-RAN ALLIANCE logo](491facfcef71bd091768b201bb2c0064_img.jpg) - -O-RAN ALLIANCE logo - -## 12.2.3 Inter-domain connectivity - -In a large packet-switched transport network the underlay infrastructure will need to be sub-divided into multiple routing domains. These routing domains can be within an autonomous system, at the IGP level, or between autonomous systems. One motivation is IGP scalability, but other reasons include fault isolation between domains and organizational, for example different groups run the DC and WAN infrastructures. However, even though the infrastructure is divided, connectivity between routers in different routing domains is still required to build end to end services, therefore the underlay infrastructure needs mechanisms to enable inter-domain connectivity and services to be built inter-domain. In an SRv6 environment, potential mechanisms for interchanging routing between domains include: - -1. IGP based hierarchy -2. Inter-domain IGP redistribution -3. Inter AS BGP -4. Controller based - -### 12.2.3.1 IGP based hierarchy - -Both ISIS for IPv6 and OSPFv3 have the concept of routing hierarchy in their basic designs. In an SRv6 environment, route summarization or injection of a default route between IS-IS levels or OSPFv3 areas is sufficient to enable EVPN or L3VPNs services to be built over an SRv6 hierarchical IGP infrastructure. - -### 12.2.3.2 Inter-domain IGP redistribution - -One or more routers are located on the boundary between two or more IGP routing domains. These routers run multiple IGP instances, so have routing awareness of all the IGPs they participate in. Routing information is mutually re-distributed between the IGP protocols allowing reachability between the domains. This redistribution can be in the form of full routing, summarised routes or even default routes. The choice is dependent on the level of awareness required between domains. - -See Figure 12-5 for more detail. IGP route re-distribution in both IS-IS for IPv6 and OSPFv3 is a common capability. - -### 12.2.3.3 Inter-AS BGP based routing - -A router in each autonomous system exchanges routing information using BGP-4 supporting the IPv6 address family. It should be noted that this scheme provides better separation than inter-domain IGP redistribution but typically requires separate routers in each autonomous system. See Figure 12-6 for more detail. - -### 12.2.3.4 Controller based path calculation - -In this scenario no routing information is exchanged between routing domains at the device level. Instead, each routing domain provides its topology to an SR Path Computation Element (SR-PCE), which is a central SDN control element responsible for determining and finding routes to a destination node on behalf of a source node. Although the SR-PCE is logically a central component, for scale and resiliency reasons it can consist of multiple individual entities distributed around and - -![O-RAN Alliance logo](f03929249a5b45fa7fb006ae5a5b88e4_img.jpg) - -O-RAN Alliance logo - -serving different parts of the network. In this case the source TNE requires very limited visibility of the overall network, as end to end cross-domain path computation is delegated to the SR-PCE. - -A SR-PCE function in an SRv6 underlay transport network has three main functions. - -1. Gather data about the topology of the overall SRv6 network underlay. Several options exist: - - a. The SR-PCE participates in the IGP domains and directly collects each domains IGP link-state database. - - b. Use BGP Link-State (BGP-LS) with appropriate extensions for SRv6 to collect the IGP's link-state database from each routing domain. This is done through one or more BGP session between the SR-PCE and a TNE in each routing domain participating in the domain's IGP. The TNEs retrieve information from the IGP LSDB and distribute it to the controller using the BGP link-state address family. -2. Communications between the PCE and PCC (path computation client) which is the headend TNE. In this document it is assumed to PCEP (path computation Element Protocol) is used as the communication mechanism between the source TNE and the SR-PCE. -3. Path computation. The PCE uses information gathered from the various domains to compute an SR policy consisting of a SID list which packets using the SR policy will traverse. This SID list can be a loosely sourced routed or explicitly source routed. - -## 12.3 Scaling an SRv6 underlay infrastructure - -Scaling is one of the key challenges in building a packet switched infrastructure supporting 5G services. Communications and support of L2 and L3 VPN services between two SRv6 TNEs relies entirely on IP routing mechanisms on the underlay transport fabric. In SRv6 this is based on longest IP prefix matching and forwarding, so TNEs can support routing and forwarding based on full IPv6 host routes, summarized IPv6 routes or default routing or a combination, derived from dynamic routing protocols or statically defined. Further, different TNEs in the end to end path can use different levels of route summarization appropriate to their position in the network and their computation, memory and NPU/ASIC resources. - -### 12.3.1 Route summarization and redistribution - -Summarization within ISIS for IPv6 and OSPFv3 is part of the base protocol capability and can occur between levels in IS-IS for IPv6 and between areas in OSPFv3 using “Area Border Routers” (ABRs). Summarization is also a common capability when redistributing routes between different routing domains and is also supported between Autonomous Systems using BGP-4 between “Autonomous System Border Routers” (ASBRs). This is illustrated in Figure 12-5 and Figure 12-6 and shows how PE1-4's routing tables can be controlled through route summarization. - -1 - -![Figure 12-5: Summarization / redistribution using IGPs. The diagram shows a network topology with two cloud-like domains, P1 and P2. Domain P1 contains PE1, PE2, and ABR1. Domain P2 contains PE3, PE4, and ABR2. ABR1 and ABR2 are connected to each other. Above the domains, summary routes are shown: 'Summary: fcbb:bb00:200::/40 ALG 0' and 'Summary: fcbb:bb01:200::/40 ALG128' pointing from ABR1 to ABR2. On the left, PE1 and PE2 have locators fcbb:bb00:101::/48 and fcbb:bb01:101::/48. On the right, PE3 and PE4 have locators fcbb:bb00:203::/48 and fcbb:bb01:204::/48.](fc3e2b49a9f850951570e502393b697f_img.jpg) - -Figure 12-5: Summarization / redistribution using IGPs. The diagram shows a network topology with two cloud-like domains, P1 and P2. Domain P1 contains PE1, PE2, and ABR1. Domain P2 contains PE3, PE4, and ABR2. ABR1 and ABR2 are connected to each other. Above the domains, summary routes are shown: 'Summary: fcbb:bb00:200::/40 ALG 0' and 'Summary: fcbb:bb01:200::/40 ALG128' pointing from ABR1 to ABR2. On the left, PE1 and PE2 have locators fcbb:bb00:101::/48 and fcbb:bb01:101::/48. On the right, PE3 and PE4 have locators fcbb:bb00:203::/48 and fcbb:bb01:204::/48. - -2 -3 -4 - -Figure 12-5 Summarization / redistribution using IGPs - -![Figure 12-6: Summarization / redistribution using BGP-4. This diagram is similar to Figure 12-5 but replaces the internal routers ABR1 and ABR2 with ASBR1, ASBR2, ASBR3, and ASBR4. ASBR1 and ASBR2 are connected to domain P1, while ASBR3 and ASBR4 are connected to domain P2. Red double-headed arrows labeled 'BGP' connect ASBR1 to ASBR3 and ASBR2 to ASBR4, indicating inter-domain routing. The same summary routes and locators are shown as in Figure 12-5.](5a01395925fc88802da68fb5ac0f31ff_img.jpg) - -Figure 12-6: Summarization / redistribution using BGP-4. This diagram is similar to Figure 12-5 but replaces the internal routers ABR1 and ABR2 with ASBR1, ASBR2, ASBR3, and ASBR4. ASBR1 and ASBR2 are connected to domain P1, while ASBR3 and ASBR4 are connected to domain P2. Red double-headed arrows labeled 'BGP' connect ASBR1 to ASBR3 and ASBR2 to ASBR4, indicating inter-domain routing. The same summary routes and locators are shown as in Figure 12-5. - -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15 -16 -17 -18 -19 - -Figure 12-6 Summarization / redistribution using BGP-4 - -This approach offers considerable flexibility, as operators can choose the level of summarization, ranging from no summarization to default routing between domains depending on the size of the network and level of awareness required between domains. It can also offer inter-domain traffic engineering support based on flexible algorithm within an IGP domain. However, there are some considerations and limitations: - -1. Address planning is critical and needs to occur upfront. -2. Route summarization might result in sub-optimal routing in certain designs. -3. Some traffic engineering scenarios cannot be achieved with route summarization alone. -4. A source TNE cannot rely on a host route withdrawal to detect a remote TNE failure covered by a summary route. In this situation over forms of device or service verification are required. - -![O-RAN Alliance logo](240d66bb698171f40d1acd5b0c098e4f_img.jpg) - -O-RAN Alliance logo - -**[D33]:** ABRs SHOULD have flex-algorithm aware summarization/redistribution function. This is a local behavior. - -To use BGP-4 to transmit underlay SRv6 routing between Autonomous Systems requires: - -**[R48]:** BGP with IPv6 multi-protocol extensions (RFC1771, RFC2545, RFC2858) [45][52][57] - -### 12.3.2 Controller based scaling - -Route summarization and redistribution is simple and allows massive scale and allows end to end traffic engineering based on flex-algo. However, some traffic engineering scenarios cannot be achieved, such as path diversity and bandwidth optimization, because summarization hides topological details. - -To achieve more complex TE solutions, end-to-end visibility of the network is required, and a controller-based solution based on an SR-PCE is used. The SR-PCE receives detailed topology information via BGP-LS protocol from each domain. The SR-PCE then has a full picture of end to end reachability. When an ingress PE need to establish an end to end path it requests information from SR-PCE via PCEP protocol. SR-PCE responds with stack of SIDs to establish path to egress PE. - -Figure 12-7 illustrates an SR-PCE based solution where PE1 needs to establish shortest path to PE3. - -![Figure 12-7: Path computation based on SR-PCE. A central SR-PCE node is at the top. It has bidirectional BGP-LS links to ABR1 and ABR2, and bidirectional PCEP links to PE1 and PE3. The network is divided into two cloud-like domains, P1 and P2. PE1 and PE2 are connected to domain P1. PE3 and PE4 are connected to domain P2. ABR1 and ABR2 sit between and connect domains P1 and P2.](bc3d1c04d342094c893d5064974c9ee7_img.jpg) - -**Node SID Information:** - -**PE1:** -fcbb:bb00:101::/48 Locator ALG 0 -fcbb:bb01:101::/48 Locator ALG128 - -**PE2:** -fcbb:bb00:102::/48 Locator ALG 0 -fcbb:bb01:102::/48 Locator ALG128 - -**ABR1/ABR2:** -END:fcbb:bb00:300:eeee:: - -**PE3:** -fcbb:bb00:203::/48 Locator ALG 0 -fcbb:bb01:203::/48 Locator ALG128 - -**PE4:** -fcbb:bb00:204::/48 Locator ALG 0 -fcbb:bb01:204::/48 Locator ALG128 - -Figure 12-7: Path computation based on SR-PCE. A central SR-PCE node is at the top. It has bidirectional BGP-LS links to ABR1 and ABR2, and bidirectional PCEP links to PE1 and PE3. The network is divided into two cloud-like domains, P1 and P2. PE1 and PE2 are connected to domain P1. PE3 and PE4 are connected to domain P2. ABR1 and ABR2 sit between and connect domains P1 and P2. - -**Figure 12-7 Path computation based on SR-PCE** - -1. SR-PCE gathers topology from each domain via BGP-LS. -2. PE1 sends a PCEP request to SR-PCE -3. PCE will respond with list of SIDs fcbb:bb00:300, fcbb:bb00:203:ffff::. - -For more complex path establishment SR-PCE will provide more complex SID list. - -![O-RAN ALLIANCE logo](2fc0e242cbd93c41bb82f48339de7ac1_img.jpg) - -O-RAN ALLIANCE logo - -**[R49]:** PCE and at least one TNE in each domain MUST support BGP Link State (BGP-LS), RFC9552 [168] - -**[R50]:** SR-PCE and at least one TNE in each domain MUST support “Border Gateway Protocol - Link State (BGP-LS) Extensions for Segment Routing over IPv6 (SRv6)”, RFC9514 [166] - -**[D34]:** SR-PCE and at least one TNE in each domain SHOULD support extensions to advertise Flexible Algorithm Definition as part of the topology, RFC 9351 [163] - -**[R51]:** SR-PCE and TNEs providing PE functionality MUST support Path Computation Element Protocol (PCEP), as described in RFC5440 [109] - -**[R52]:** SR-PCE and TNEs providing PE functionality MUST support PCEP protocol client functionality with SRv6 extensions, RFC9603 [170] - -**[D35]:** SR-PCE SHOULD support “IGP Flexible Algorithm be able to compute paths based on different flexible algorithms - -### 12.3.3 SRv6 scaling conclusion - -To build an underlay transport network that is highly scalable and supports traffic engineering the simplest way is to uses a multi-domain IGP that supports flex-algo and use address summarization. This design might not be sufficient for all application requirements. In these instances, a PCE based solution could be deployed in tandem for TE use cases that require additional network visibility. - -## 12.4 IPv6 Quality of Service - -The IPv6 packet includes a 6-bit field in the IPv6 header, the DiffServ Code Point (DSCP). These bits are assignable as a marker for QoS mechanisms in transport nodes to use as a classification and marking tool. The per-hop behavior for IPv6 forwarding elements can be defined based on these markings. For a full discussion of a proposed marking scheme and QoS architecture for TNEs in Xhaul, section 14. - -## 12.5 SRv6 OAM - -SRv6 OAM functionality is required to understand the status of the network. SRv6 OAM is described in “Operations, Administration, and Maintenance (OAM) in Segment Routing over IPv6 (SRv6)” RFC 9259 [161] - -### 12.5.1 Ping / Traceroute to a remote IPv6 network address - -Ping is required to test liveliness to a remote SRv6 underlay address and traceroute is required to trace paths and perform hop-by-hop fault isolation to remote SRv6 underlay address. The following capabilities are required on all TNEs. - -**[R53]:** TNEs MUST support ICMPv6 (RFC4443) [85] - -**[R54]:** TNEs MUST support IPv6 ping to query liveliness of a remote IPv6 address along the shortest path for default SPF algorithm. - -![O-RAN ALLIANCE logo](83a718de2dd31ecd7acfb09449924e04_img.jpg) - -O-RAN ALLIANCE logo - -**[R55]:** TNEs MUST support IPv6 ping to query liveliness of a remote IPv6 address along a path calculated by a flex-algorithm. - -**[R56]:** TNEs MUST support IPv6 ping to query liveliness of a remote IPv6 address along a path designated by a list of SIDs. - -**[R57]:** TNEs MUST support IPv6 traceroute to trace the path to a remote IPv6 address along the shortest path for default SPF algorithm - -**[R58]:** TNEs MUST support IPv6 traceroute to trace the path to a remote IPv6 address along a path calculated by a flexible algorithm. - -**[R59]:** TNEs MUST support IPv6 traceroute to trace the path to a remote IPv6 address along a path designated by a list of SIDs. - -## 12.5.2 Ping / Traceroute to remote SID functions - -Ping is required to test liveliness to a remote SID and traceroute is required to trace paths and perform hop-by-hop fault isolation to a remote SRv6 SID. The following capabilities are required on all Transport Nodes. - -**[R60]:** TNEs MUST support IPv6 ping to query liveliness of a remote EVPN and L3VPN services along the shortest path for default SPF algorithm. - -**[R61]:** TNEs MUST support IPv6 ping to query liveliness of a remote EVPN and L3VPN services along a path calculated by a flex-algorithm. - -**[R62]:** TNEs MUST support IPv6 ping to query liveliness of a remote EVPN and L3VPN service along a path designated by a list of SIDs. - -**[R63]:** TNEs MUST support IPv6 traceroute to trace the path to a remote EVPN and L3VPN service along the shortest path for default algorithm - -**[R64]:** TNEs MUST support IPv6 traceroute to trace the path to a remote EVPN and L3VPN service along a path calculated by a flexible algorithm. - -**[R65]:** TNEs MUST support IPv6 traceroute to trace the path to a remote EVPN and L3VPN service along a path designated by a list of SIDs. - -## 12.6 SRv6 Service infrastructure - -An SRv6 transport underlay supports basic IPv6 services natively at the control and data plane. For Ethernet, IPv4 and IPv6 VPN services an overlay control plane infrastructure is used to convey VPN connectivity information. At the data plane the P devices can utilise a standard IPv6 data plane with the PE devices requiring an IPv6 data plane with SRv6 VPN network programming awareness [156]. Please refer to section 13 for a description of overlay service recommendations for a 5G Xhaul infrastructure. - -## 13 Packet-switched Xhaul services Infrastructure - -To support an Xhaul environment requires the packet switched network to support L2 and L3 services. Both an MPLS and IPv6 packet switched underlays use EVPN to support L2 and MP-BGP L3VPNs. - -### 13.1 MP-BGP design - -Both EVPN and MP-BGP L3VPNs use MP-BGP, with appropriate address-family support for EVPN and L3VPN, to convey service connectivity information between Provider Edge (PE) equipment. - -Typically, the MP-BGP infrastructure for L2 and L3 services uses a Route Reflector design rather than an I-BGP mesh between all PEs. In large networks, operators will normally implement a hierarchical Route Reflector (RR) design for Multi-Protocol BGP (MP-BGP) peering. A pair of Route Reflectors (RR) could be used at every domain to provide scalability and extensibility. - -![Figure 13-1: Hierarchical Route Reflector Design for Multiple Protocol BGP. The diagram shows a hierarchy of Route Reflectors (RRs) across different network domains: Hub RR, Edge RR, Regional RR, and National RR. On the left, two CSRs (CSR-R1 and CSR-R2) are connected to an O-RU. These CSRs are part of a 'FrontHaul' domain. The Hub RR is connected to the CSRs and to an O-DU at a 'Hub Site'. The Hub RR is connected to an Edge RR via a 'MidHaul' domain. The Edge RR is connected to an O-CU at an 'Edge DC' and to a Regional RR via a 'Backhaul' domain. The Regional RR is connected to a UPF at a 'Regional DC' and to a National RR via a '5G and/or Transport Core' domain. The National RR is the top-level RR. PE Routers are shown connecting the RRs to the various sites and DCs.](c995e0bb4efc8c0f2994428aa1245709_img.jpg) - -Figure 13-1: Hierarchical Route Reflector Design for Multiple Protocol BGP. The diagram shows a hierarchy of Route Reflectors (RRs) across different network domains: Hub RR, Edge RR, Regional RR, and National RR. On the left, two CSRs (CSR-R1 and CSR-R2) are connected to an O-RU. These CSRs are part of a 'FrontHaul' domain. The Hub RR is connected to the CSRs and to an O-DU at a 'Hub Site'. The Hub RR is connected to an Edge RR via a 'MidHaul' domain. The Edge RR is connected to an O-CU at an 'Edge DC' and to a Regional RR via a 'Backhaul' domain. The Regional RR is connected to a UPF at a 'Regional DC' and to a National RR via a '5G and/or Transport Core' domain. The National RR is the top-level RR. PE Routers are shown connecting the RRs to the various sites and DCs. - -Figure 13-1 Hierarchical Route Reflector Design for Multiple Protocol BGP - -Figure 13-1 shows the Hierarchical Route Reflector Design utilizing RR pairs in each network domain, all peering with National Route Reflector core. - -### 13.2 Ethernet services - -Ethernet services will be provided by EVPN over either MPLS or IPv6 depending on the underlay network employed by the operator. More details on EVPN are provided in annex B. - -EVPN VPWS can be used as transport service for Open Fronthaul (eCPRI), as well a transport service for Radio over Ethernet (RoE) as outlined in following Figure 13-2 and Figure 13-3. - -![Figure 13-2: EVPN VPWS for eCPRI. The diagram shows an O-RU connected to a CSR at a 'Cell site'. The CSR is connected to an HSR (Host Service Router) via a 'Fronthaul' domain. The HSR is connected to an O-DU at a 'Hub site'. A red line represents the 'eCPRI flow' and an orange line represents the 'EVPN VPWS'. Both lines pass through the CSR, the Fronthaul domain, and the HSR.](7ef82ab74729923b27507495301d73a6_img.jpg) - -Figure 13-2: EVPN VPWS for eCPRI. The diagram shows an O-RU connected to a CSR at a 'Cell site'. The CSR is connected to an HSR (Host Service Router) via a 'Fronthaul' domain. The HSR is connected to an O-DU at a 'Hub site'. A red line represents the 'eCPRI flow' and an orange line represents the 'EVPN VPWS'. Both lines pass through the CSR, the Fronthaul domain, and the HSR. - -Figure 13-2 EVPN VPWS for eCPRI - -![Figure 13-3: EVPN VPWS for RoE diagram. The diagram shows a 'Cell site' on the left containing an RRH connected to a RoE Mapper, which is connected to a CSR. A 'Hub site' on the right contains a BBU connected to a RoE Mapper, which is connected to an HSR. A 'Fronthaul' cloud connects the CSR and the HSR. Three types of flows are shown: CPRI flow (green line), RoE flow (blue line), and EVPN VPWS (orange line). The RoE flow and EVPN VPWS are shown passing through the Fronthaul cloud between the CSR and the HSR.](af3b2fa532cb9b02a2aaeeb49e0118d0_img.jpg) - -Figure 13-3: EVPN VPWS for RoE diagram. The diagram shows a 'Cell site' on the left containing an RRH connected to a RoE Mapper, which is connected to a CSR. A 'Hub site' on the right contains a BBU connected to a RoE Mapper, which is connected to an HSR. A 'Fronthaul' cloud connects the CSR and the HSR. Three types of flows are shown: CPRI flow (green line), RoE flow (blue line), and EVPN VPWS (orange line). The RoE flow and EVPN VPWS are shown passing through the Fronthaul cloud between the CSR and the HSR. - -Figure 13-3 EVPN VPWS for RoE - -To support EVPN VPWS for eCPRI or RoE, the transport device will need to support: - -**[D36]:** SHOULD support “Flow-Aware Transport of Pseudowires over an MPLS Packet Switched Network”, RFC 6391 [119] - -**[R66]:** MUST support “Virtual Private Wire Service Support in Ethernet VPN”, RFC 8214 [131] - -**[D37]:** If the Flow-Aware Transport is supported, then MUST support “Extensions to BGP-Signaled Pseudowires to Support Flow-Aware Transport Labels”, Internet Engineering Task Force, RFC 8395 [140] - -**[R67]:** If using SRv6 as the underlay technology TNEs providing PE functionality MUST support “BGP Overlay Services Based on Segment Routing over IPv6 (SRv6)”, Internet Engineering Task Force, RFC 9252 [159] - -### 13.2.1 Ethernet services redundancy - -EVPN VPWS can provide redundancy for O-RU to O-DU (Open Fronthaul) interface to react to the transport network errors that might occur. - -#### 13.2.1.1 Ethernet services redundancy – Option 1 - -![Figure 13-4: EVPN VPWS redundancy option 1 diagram. The diagram shows a 'Cell site' on the left containing an O-RU connected to a MAC-A, which is connected to a CSR. A 'Hub site' on the right contains an O-DU connected to a MAC-B. The O-RU is connected to two HSRs (HSR-1 and HSR-2) in the Hub site. The HSRs are connected to the O-DU. Two types of flows are shown: eCPRI flow (red line) and EVPN VPWS (orange line). The eCPRI flow is shown passing through the Fronthaul cloud between the CSR and the HSRs. The EVPN VPWS is shown passing through the Fronthaul cloud between the CSR and the HSRs, and then through the HSRs to the O-DU.](ab9c25a3205779c1860b702caaece17b_img.jpg) - -Figure 13-4: EVPN VPWS redundancy option 1 diagram. The diagram shows a 'Cell site' on the left containing an O-RU connected to a MAC-A, which is connected to a CSR. A 'Hub site' on the right contains an O-DU connected to a MAC-B. The O-RU is connected to two HSRs (HSR-1 and HSR-2) in the Hub site. The HSRs are connected to the O-DU. Two types of flows are shown: eCPRI flow (red line) and EVPN VPWS (orange line). The eCPRI flow is shown passing through the Fronthaul cloud between the CSR and the HSRs. The EVPN VPWS is shown passing through the Fronthaul cloud between the CSR and the HSRs, and then through the HSRs to the O-DU. - -Figure 13-4 EVPN VPWS redundancy option 1 - -This option assumes that O-DU supports Link Aggregation Group (LAG, also called Ethernet bundling) and terminates the eCPRI stream on a MAC address associated with the Ethernet bundle - -![O-RAN Alliance logo](2e5f9e03131e55d2383bdfa422419916_img.jpg) - -O-RAN Alliance logo - -(e.g. MAC-B in the diagram). Therefore, eCPRI stream can arrive on any physical interface (via HSR-1 or via HSR-2) to O-DU, and O-DU might send eCPRI stream, again, on any interface (via HSR-1 or via HSR-2) (see Figure 13-4). - -To facilitate fast failover in case of HSR $\leftrightarrow$ O-DU link failure, following architectural design choices are recommended: - -- O-DU uplinks towards HSR pair should be bundled on O-DU to create Link Aggregation Group (LAG), often called an “Ethernet bundle”. -- EVPN VPWS service should be terminated on HSR pair as ‘multi-homed all-active’ service - -When O-RU generates eCPRI stream towards O-DU, this stream can be sent from CSR via EVPN VPWS leg towards HSR-1, or via EVPN VPWS leg towards HSR-2. It is CSR implementation choice, towards which HSR eCPRI stream will be sent. In case multiple O-RUs are connected to single CSR, and multiple eCPRI streams are forwarded from CSR towards O-DU via HSR pair, each eCPRI stream might take different path (i.e. via HSR-1 or HSR-2). - -When for example HSR-1 $\leftrightarrow$ O-DU link failure happens, following EVPN failure detection machinery, the EVPN VPWS leg between CSR and HSR-1 is disabled, and eCPRI stream flows now over HSR-2. Since EVPN VPWS termination on HSR-2 was originally ‘active’ (multi-homed all-active service) no special forwarding plane reprogramming is needed on HSR-2, allowing quick delivery of rerouted eCPRI streams towards O-DU, as outlined in Figure 13-5. - -![Figure 13-5: EVPN VPWS Redundancy option 1 – failure event. The diagram shows a Cell site (O-RU, MAC-A, CSR) connected via a Fronthaul cloud to a Hub site. The Hub site contains HSR-1 and HSR-2, both connected to an O-DU (MAC-B). A failure event is indicated by 'X' marks on the links between HSR-1 and the O-DU. The legend indicates eCPRI flow (red line) and EVPN VPWS (orange line).](aa22da43c463563d3d0035722bd79449_img.jpg) - -Figure 13-5: EVPN VPWS Redundancy option 1 – failure event. The diagram shows a Cell site (O-RU, MAC-A, CSR) connected via a Fronthaul cloud to a Hub site. The Hub site contains HSR-1 and HSR-2, both connected to an O-DU (MAC-B). A failure event is indicated by 'X' marks on the links between HSR-1 and the O-DU. The legend indicates eCPRI flow (red line) and EVPN VPWS (orange line). - -Figure 13-5 EVPN VPWS Redundancy option 1 – failure event - -### 13.2.1.2 Ethernet services redundancy – Option 2 - -Option 2 is similar to option 1, with the difference that O-DU expects to receive eCPRI stream on a particular interface (for example, on the interface from HSR-1), as outlined in Figure 13-6 - -![Figure 13-6: Ethernet services redundancy – Option 2. The diagram shows a Cell site (O-RU, MAC-A, CSR) connected via a Fronthaul cloud to a Hub site. The Hub site contains HSR-1 and HSR-2, both connected to an O-DU (MAC-B). HSR-1 is labeled 'DF' (Designated Forwarder) and HSR-2 is labeled 'nDF' (non-Designated Forwarder). A green arrow labeled 'LACP OOS' points from HSR-2 to the O-DU. The legend indicates eCPRI flow (red line) and EVPN VPWS (orange line).](f9873201604e723ae0bafb7e389ef619_img.jpg) - -Figure 13-6: Ethernet services redundancy – Option 2. The diagram shows a Cell site (O-RU, MAC-A, CSR) connected via a Fronthaul cloud to a Hub site. The Hub site contains HSR-1 and HSR-2, both connected to an O-DU (MAC-B). HSR-1 is labeled 'DF' (Designated Forwarder) and HSR-2 is labeled 'nDF' (non-Designated Forwarder). A green arrow labeled 'LACP OOS' points from HSR-2 to the O-DU. The legend indicates eCPRI flow (red line) and EVPN VPWS (orange line). - -Figure 13-6 EVPN VPWS Redundancy Option 2 - -For this option, following architectural design choices are recommended: - -- O-DU uplinks towards HSR pair should be bundled on O-DU to create Link Aggregation Group (LAG), often called an “Ethernet bundle”. -- EVPN VPWS service should be terminated on HSR pair as ‘multi-homed single-active’ service -- Deterministic Designated Forwarder (DF) election should be used on HSR pair, to ensure that one of the HSR is deterministically elected as ‘active’ forwarder (DF), and second HSR is deterministically elected as ‘standby’/’passive’ forwarder (non-DF) -- Per physical port (rather than default per-VLAN) DF election should be used on HSR pair -- HSR should signal the non-DF status to O-DU via OAM (for example LACP – Link Aggregation Control Protocol – Out of Sync signalling) - -In addition to requirements already mentioned in the main section, to support this option following requirements must be supported on HSR: - -**[R68]:** MUST support “Preference-Based EVPN Designated Forwarder (DF) Election”, RFC 9785 [175] - -**[R69]:** MUST support "EVPN Port-Active Redundancy Mode" ", RFC 9786 [176] - -As outlined in Figure 13-7, when HSR-1 ↔ O-DU link failure happens, following EVPN failure detection machinery, the EVPN VPWS leg between CSR and HSR-1 is disabled, HSR-2 becomes DF and EVPN VPWS leg between CSR and HSR-2 is enabled. Additionally, LACP Out-of-Sync state from HSR-2 to O-DU is cleared, allowing forwarding over the HSR-2 ↔ O-DU link. eCPRI stream flows now over HSR-2. As opposed to Option 1, since EVPN VPWS termination on HSR-2 was originally ‘standby’ (multi-homed single-active service), DF election, LACP OOS clearance and forwarding plane reprogramming is needed on HSR-2, thus failover is longer than in case of Option 1. - -![Diagram illustrating EVPN VPWS Redundancy Option 2 failure event. On the left, an O-RU (MAC-A) is connected to a Cell site containing a CSR. A red line (eCPRI flow) and an orange line (EVPN VPWS) connect the CSR to a Hub site. The Hub site contains two HSR units: HSR-1 (nDF) and HSR-2 (DF). HSR-1 is connected to an O-DU (MAC-B). A failure event is shown with a large 'X' over the link between HSR-1 and the O-DU. The eCPRI flow is rerouted from HSR-1 to HSR-2, and then to the O-DU. The EVPN VPWS flow is also rerouted from HSR-1 to HSR-2. The Fronthaul is shown as a green cloud between the Cell site and the Hub site.](2277d0ec6e1001b063d4f06dc3842e92_img.jpg) - -Diagram illustrating EVPN VPWS Redundancy Option 2 failure event. On the left, an O-RU (MAC-A) is connected to a Cell site containing a CSR. A red line (eCPRI flow) and an orange line (EVPN VPWS) connect the CSR to a Hub site. The Hub site contains two HSR units: HSR-1 (nDF) and HSR-2 (DF). HSR-1 is connected to an O-DU (MAC-B). A failure event is shown with a large 'X' over the link between HSR-1 and the O-DU. The eCPRI flow is rerouted from HSR-1 to HSR-2, and then to the O-DU. The EVPN VPWS flow is also rerouted from HSR-1 to HSR-2. The Fronthaul is shown as a green cloud between the Cell site and the Hub site. - -Figure 13-7 EVPN VPWS Redundancy Option 2 -failure event - -### 13.2.1.3 Ethernet services redundancy – Option 3 - -Option 3 is further modification of option 2. It is suitable for O-DUs that do not support LAG bundling, but have the capability to terminate eCPRI stream on some internal virtual MAC, allowing reception of eCPRI stream over any uplink. - -![O-RAN Alliance logo](5f0b57710a125afec285a2c3c9d2e0b1_img.jpg) - -O-RAN Alliance logo - -![Figure 13-8: EVPN VPWS Redundancy Option 3 diagram. On the left, a 'Cell site' contains an 'O-RU' connected to a 'CSR'. The 'CSR' is connected to 'MAC-A'. A red line labeled 'eCPRI flow' goes from 'MAC-A' through a green cloud labeled 'Fronthaul' to 'HSR-1' in the 'Hub site'. An orange line labeled 'EVPN VPWS' also goes from 'MAC-A' through the 'Fronthaul' cloud to 'HSR-1'. In the 'Hub site', 'HSR-1' and 'HSR-2' are connected to 'MAC-B', which is connected to an 'O-DU'. The 'eCPRI flow' from 'HSR-1' goes to 'MAC-B' and then to the 'O-DU'. The 'EVPN VPWS' from 'HSR-1' also goes to 'MAC-B' and then to the 'O-DU'.](59e29b37c5e332b0be088cde8c4d217e_img.jpg) - -Figure 13-8: EVPN VPWS Redundancy Option 3 diagram. On the left, a 'Cell site' contains an 'O-RU' connected to a 'CSR'. The 'CSR' is connected to 'MAC-A'. A red line labeled 'eCPRI flow' goes from 'MAC-A' through a green cloud labeled 'Fronthaul' to 'HSR-1' in the 'Hub site'. An orange line labeled 'EVPN VPWS' also goes from 'MAC-A' through the 'Fronthaul' cloud to 'HSR-1'. In the 'Hub site', 'HSR-1' and 'HSR-2' are connected to 'MAC-B', which is connected to an 'O-DU'. The 'eCPRI flow' from 'HSR-1' goes to 'MAC-B' and then to the 'O-DU'. The 'EVPN VPWS' from 'HSR-1' also goes to 'MAC-B' and then to the 'O-DU'. - -Figure 13-8 EVPN VPWS Redundancy Option 3 - -For this option, following architectural design choices are recommended: - -- Two O-DU uplinks towards HSR pair are not bundled, but are standalone links placed inside internal bridge on O-DU -- EVPN VPWS service should be terminated on HSR pair as ‘multi-homed single-active’ service - -In this option, one of the HSR routers (for example HSR-1) is automatically elected by EVPN control plane as ‘active’ (Designated Forwarder) router, and eCPRI stream is delivered over EVPN VPWS service from CSR to active HSR only, where it is forwarded to O-DU in Ethernet frames. Internal bridge at O-DU performs MAC learning (to learn O-RU MAC: MAC-A), therefore the eCPRI stream generated from O-DU side and destined to O-RU (MAC-A) follows the same path via HSR-1. - -As outlined in Figure 13-9, when HSR-1 ↔ O-DU link failure happens, following EVPN failure detection machinery, the EVPN VPWS leg between CSR and HSR-1 is disabled, HSR-2 becomes DF and EVPN VPWS leg between CSR and HSR-2 is enabled. eCPRI stream flows now over HSR-2, and internal bridge in O-DU relearns the MAC-A via HSR-2. As opposed to Option 1, since EVPN VPWS termination on HSR-2 was originally ‘standby’ (multi-homed single-active service), DF election and forwarding plane reprogramming is needed on HSR-2, thus failover is longer than in case of Option 1. - -![Figure 13-9: EVPN VPWS Redundancy Option 3 – failure event diagram. This diagram shows the same setup as Figure 13-8, but with a failure event. The link between 'HSR-1' and 'MAC-B' is marked with a large 'X', indicating a failure. The 'eCPRI flow' (red line) is now shown going from 'MAC-A' through the 'Fronthaul' cloud to 'HSR-2' in the 'Hub site', and then from 'HSR-2' to 'MAC-B' and the 'O-DU'. The 'EVPN VPWS' (orange line) is also shown going from 'MAC-A' through the 'Fronthaul' cloud to 'HSR-2' and then to 'MAC-B' and the 'O-DU'.](6322885569221ec51d70560d7dba1339_img.jpg) - -Figure 13-9: EVPN VPWS Redundancy Option 3 – failure event diagram. This diagram shows the same setup as Figure 13-8, but with a failure event. The link between 'HSR-1' and 'MAC-B' is marked with a large 'X', indicating a failure. The 'eCPRI flow' (red line) is now shown going from 'MAC-A' through the 'Fronthaul' cloud to 'HSR-2' in the 'Hub site', and then from 'HSR-2' to 'MAC-B' and the 'O-DU'. The 'EVPN VPWS' (orange line) is also shown going from 'MAC-A' through the 'Fronthaul' cloud to 'HSR-2' and then to 'MAC-B' and the 'O-DU'. - -Figure 13-9 EVPN VPWS Redundancy Option 3 – failure event - -#### 13.2.1.4 Ethernet services redundancy – Option 4 - -Option 4 is suitable for O-DUs with only basic Ethernet support. i.e. O-DUs not supporting LAG, internal bridge, or virtual MAC for eCPRI stream termination. Therefore, O-DU is represented by two MAC addresses: MAC-B, on the link towards HSR-1, and MAC-C, on the link towards HSR-2. - -![Figure 13-10: EVPN VPWS Redundancy Option 4 diagram. A Cell site (O-RU, MAC-A, CSR) is connected via a Fronthaul cloud to a Hub site. The Hub site contains two HSR units (HSR-1 and HSR-2) and an O-DU (MAC-B, MAC-C). HSR-1 is the Designated Forwarder (DF) and HSR-2 is the non-Designated Forwarder (nDF). An eCPRI flow (red line) goes from the CSR to the O-DU. EVPN VPWS service (orange line) is terminated on the HSR pair.](4c1ea859b93043f2fa17a8fe72fb6176_img.jpg) - -Figure 13-10: EVPN VPWS Redundancy Option 4 diagram. A Cell site (O-RU, MAC-A, CSR) is connected via a Fronthaul cloud to a Hub site. The Hub site contains two HSR units (HSR-1 and HSR-2) and an O-DU (MAC-B, MAC-C). HSR-1 is the Designated Forwarder (DF) and HSR-2 is the non-Designated Forwarder (nDF). An eCPRI flow (red line) goes from the CSR to the O-DU. EVPN VPWS service (orange line) is terminated on the HSR pair. - -Figure 13-10 EVPN VPWS Redundancy Option 4 - -For this option, following architectural design choices are recommended: - -- Two O-DU uplinks towards HSR pair are not bundled, but are standalone links placed inside internal bridge on O-DU -- EVPN VPWS service should be terminated on HSR pair as ‘multi-homed single-active’ service - -In this option, eCPRI stream generated at O-RU uses of the O-DUs MAC addresses, for example MAC-B, as the destination MAC in eCPRI Ethernet frames. Therefore, EVPN DF election must be deterministic, similar to the DF election on Option 2. - -In addition to requirements already mentioned in the main section, to support this option following requirements must be supported on HSR: - -**[R70]:** MUST support “Preference-Based EVPN Designated Forwarder (DF) Election”, RFC 9785 [175] - -As outlined in Figure 13-11, when HSR-1 ↔ O-DU link failure happens, following EVPN failure detection machinery, the EVPN VPWS leg between CSR and HSR-1 is disabled, HSR-2 becomes DF and EVPN VPWS leg between CSR and HSR-2 is enabled. However, as opposed to all options discussed previously, in this option, when failure happens, O-RU configuration must be changed by the orchestrator, so that new MAC address (MAC-C) is used as the destination MAC in eCPRI Ethernet frames. This contributes to the highest failover time among all options discussed so far. - -![Figure 13-11: EVPN VPWS Redundancy Option 4 – failure event diagram. This diagram shows the state after a failure. The link between HSR-1 and the O-DU is broken, indicated by large 'X' marks. HSR-2 is now the Designated Forwarder (DF). The eCPRI flow (red line) is now directed to MAC-C on the O-DU. The EVPN VPWS service (orange line) is still active, terminating on the HSR pair.](4ecb55f0a56c2f3deb9eeddfde39d501_img.jpg) - -Figure 13-11: EVPN VPWS Redundancy Option 4 – failure event diagram. This diagram shows the state after a failure. The link between HSR-1 and the O-DU is broken, indicated by large 'X' marks. HSR-2 is now the Designated Forwarder (DF). The eCPRI flow (red line) is now directed to MAC-C on the O-DU. The EVPN VPWS service (orange line) is still active, terminating on the HSR pair. - -Figure 13-11 EVPN VPWS Redundancy Option 4 – failure event - -## 13.3 IP Services - -Mobile IP services will be provided by MP-BGP based L3 VPNs (RFC4364) [90] over MPLS or SRv6 depending on the underlay network technology employed by the operator. More details on L3VPN are provided in annex C. - -Operators that choose to implement IP services using the BGP Based L3VPN services may use the following architectural design options: - -### 13.3.1 Building flexible L3VPN service topologies - -L3VPN services can be used to establish L3 connectivity between various mobile components. BGP L3 VPN support both IPv4 and IPv6 VPNs and offer flexible connectivity models including: - -- IP N:N multipoint services -- IP 1:N multipoint services -- IP 1:1 connectivity services - -![Figure 13-12: Flexible L3 VPN service topologies diagram. The diagram shows a network architecture with three VPN clouds (VPN 1 in blue, VPN 2 in orange, VPN 3 in green) at the top. Below them, a '5G and/or Transport Core' cloud contains three PE Routers. On the left, two CSRs (CSR-R1 and CSR-R2) connected to O-RUs are part of a 'Hub Site' containing an O-DU and a Hub Site Router (R3). On the right, an 'Edge DC' contains an O-CU and a PE Router. A 'Regional DC' contains a UPF and another PE Router. Connections are labeled: 'FrontHaul' between CSRs and R3, 'MidHaul' between R3 and the first PE Router, and 'Backhaul' between the first and second PE Routers. The third PE Router connects to the UPF.](878e3f080378afb04bb23d5863edc6a5_img.jpg) - -Figure 13-12: Flexible L3 VPN service topologies diagram. The diagram shows a network architecture with three VPN clouds (VPN 1 in blue, VPN 2 in orange, VPN 3 in green) at the top. Below them, a '5G and/or Transport Core' cloud contains three PE Routers. On the left, two CSRs (CSR-R1 and CSR-R2) connected to O-RUs are part of a 'Hub Site' containing an O-DU and a Hub Site Router (R3). On the right, an 'Edge DC' contains an O-CU and a PE Router. A 'Regional DC' contains a UPF and another PE Router. Connections are labeled: 'FrontHaul' between CSRs and R3, 'MidHaul' between R3 and the first PE Router, and 'Backhaul' between the first and second PE Routers. The third PE Router connects to the UPF. - -**Figure 13-12 Flexible L3 VPN service topologies** - -### 13.3.2 Constraints based Traffic Steering in L3VPNs - -By default, BGP based L3VPN use shortest path routing across the transport underlay. However, BGP based VPN traffic can also get automatically steered into SR policy, such as one created by a flexible algorithm or a point-to-point TE tunnel. This is achieved by coloring VPN routes within MP-BGP with extended community attributes. As illustrated in Figure 13-13 this can be done in two ways - -1. While defining a VRF, define a color for all Prefixes associated with that VRF, or -2. When sending or receiving BGP routes, using a policy to “color” the route. - -![O-RAN Alliance logo](75b916cf99a8170ef33ffc901cb9d197_img.jpg) - -O-RAN Alliance logo - -![Diagram illustrating the import/export of route colors for SR policy selection in an O-RAN network. The diagram shows a flow from the RAN (O-RU, CSR-R1, CSR-R2) through FrontHaul, MidHaul, and Backhaul segments to the 5G and/or Transport Core. Key components include Hub Site Router R3, O-DU, O-CU, PE Routers, and UPF. Annotations indicate that routes are tagged with SRTE colors at the RAN and exported with these colors through the transport network.](7e12e1e0d03a03790d2e9d74c3454bff_img.jpg) - -The diagram illustrates the network architecture and route propagation for SR policy selection. On the left, the RAN consists of O-RU units connected to two CSRs (CSR-R1 and CSR-R2). These CSRs are connected to a Hub Site Router (R3) via the FrontHaul segment. The Hub Site Router is connected to an O-DU at the Hub Site. The O-DU is connected to an O-CU at the Edge DC. The O-CU is connected to PE Routers, which are then connected to a UPF at the Regional DC. The transport network is divided into three segments: FrontHaul (between CSRs and Hub Site Router), MidHaul (between Hub Site Router and O-CU), and Backhaul (between O-CU and PE Routers). The PE Routers are connected to the 5G and/or Transport Core. Two callouts indicate route tagging: 'Use BGP Policy to tag a route with SRTE color' at the CSRs and 'Export VRF Route with an SRTE policy Color' at the Hub Site Router. - -Diagram illustrating the import/export of route colors for SR policy selection in an O-RAN network. The diagram shows a flow from the RAN (O-RU, CSR-R1, CSR-R2) through FrontHaul, MidHaul, and Backhaul segments to the 5G and/or Transport Core. Key components include Hub Site Router R3, O-DU, O-CU, PE Routers, and UPF. Annotations indicate that routes are tagged with SRTE colors at the RAN and exported with these colors through the transport network. - -**Figure 13-13 Import / Export of route colors for SR policy selection** - -In either case, the VPN route will now be tagged with a color and traffic for the destination will automatically get steering into an SR policy based on the color associated with the VPN route. - -An operator using MP-BGP L3VPN services for Xhaul, TNEs need to support: - -**[R71]:** MUST support Multiprotocol Extensions for BGP-4, RFC4760 [92] - -**[R72]:** MUST Support BGP/MPLS IP Virtual Private Networks (VPNs), RFC4364 [90] - -**[D38]:** SHOULD support SRTE Policy configuration as RFC 9256 [160], if SRTE policies are used with L3VPN services - -**[D39]:** SHOULD support EVPN and L3VPN traffic steering based on “color extended community BGP attributes” defined in RFC5512 [112] - -**[D40]:** SHOULD support to color extended community attribute for VPNv4, VPNv6 and EVPN BGP address families defined in RFC5512 [112] - -**[R73]:** If using SRv6 as the underlay technology TNEs providing PE functionality MUST support “BGP Overlay Services Based on Segment Routing over IPv6 (SRv6)”, Internet Engineering Task Force, RFC 9252 [159] - -## 14 Quality of Service in packet-switched networks - -This chapter discusses the Quality of Service (QoS) capabilities that must be deployed to support the delivery of Xhaul traffic and non-Xhaul traffic in the RAN network. - -### 14.1 Xhaul transport core interface QoS - -For the purposes of this document, the transport network domain will be considered to be constructed of two interface types. Core interfaces and edge interfaces. An interface is considered to be transport network core if it is interconnecting two devices inside the transport domain. An interface is considered transport network edge if it is connecting to an element outside the transport domain. - -### 1 14.1.1 Transport network core interface classification - -2 Interfaces in the transport network core domain should perform classification on the outer transport - 3 header only. The header in use will depend on the transport model selected by the operator. An - 4 example classification scheme for MPLS TC (EXP) to queue is shown below in Figure 14-1 - -5 - -6 **[R74]:** TNEs MUST support classification based on MPLS TC in a MPLS underlay transport - 7 network - -8 **[R75]:** TNEs MUST support classification based on IPv6 DSCP in an SRv6 underlay transport - 9 network - -10 - -### 11 14.1.2 Core interface queue structure - -12 The Xhaul domain must support a differentiated QoS architecture supporting priority queueing and - 13 scheduling with weighted fair queue scheduler for non-priority packets. - -14 - -15 **[R76]:** MUST support EF forwarding described in IETF RFC 3246 [69] mapped to a strict priority - 16 scheduler with shaping and policing to prevent bandwidth starvation of other classes. - -17 **[R77]:** MUST support AF forwarding model described in IETF RFC 2597 [53] mapped to a WFQ, - 18 WRR or MDRR scheduler for non-priority classes. - -19 **[R78]:** MUST support the ability to manipulate queue depths - -20 - -#### 21 14.1.2.1 Flat queue model - -22 In the flat queue model, the TNE should support a single level of queue on each physical interface. - 23 This model is used for a single topology infrastructure, or a “soft slicing” where the QoS model for - 24 each slice is common and bandwidth is dynamically shared between slices. - -![Diagram of the Xhaul queue model showing six queues with different traffic types and MPLS TC markings. The queues are: 1. Latency sensitive fronthaul traffic + G.8275.2 PTP (unaware node) (PQ) with marking 5; 2. Latency sensitive U-plane + business traffic with marking 2; 3. Latency Sensitive Network control plane (BFD, IGP, PTP) with marking 7; 4. Guaranteed bandwidth traffic (e.g. management) with marking 6; 5. Guaranteed bandwidth U-plane and business traffic with markings 3,4; 6. Other best effort (may be guaranteed) with markings 0,1. A circular arrow indicates the queueing process, and a pipe represents the output link.](78c6bfdfef4d292384fc7667315392ab_img.jpg) - -Example queue marking -(E.g. MPLS TC) - -| Traffic Type | Example Queue Marking (E.g. MPLS TC) | -|------------------------------------------------------------------------|--------------------------------------| -| Latency sensitive fronthaul traffic + G.8275.2 PTP (unaware node) (PQ) | 5 | -| Latency sensitive U-plane + business traffic | 2 | -| Latency Sensitive Network control plane (BFD, IGP, PTP) | 7 | -| Guaranteed bandwidth traffic (e.g. management) | 6 | -| Guaranteed bandwidth U-plane and business traffic | 3,4 | -| Other best effort (may be guaranteed) | 0,1 | - -Diagram of the Xhaul queue model showing six queues with different traffic types and MPLS TC markings. The queues are: 1. Latency sensitive fronthaul traffic + G.8275.2 PTP (unaware node) (PQ) with marking 5; 2. Latency sensitive U-plane + business traffic with marking 2; 3. Latency Sensitive Network control plane (BFD, IGP, PTP) with marking 7; 4. Guaranteed bandwidth traffic (e.g. management) with marking 6; 5. Guaranteed bandwidth U-plane and business traffic with markings 3,4; 6. Other best effort (may be guaranteed) with markings 0,1. A circular arrow indicates the queueing process, and a pipe represents the output link. - -25 - -26 - -27 - -**Figure 14-1 Example Xhaul queue model** - -28 - -29 - -30 - -The system should be capable of supporting a minimum of six queues within the core domain. An - example queuing model is provided in Figure 14-1 which should be adapted to fit the available - queue and scheduling model available in the deployed hardware. - -31 - -32 - -All deployments must support a strict priority queue dedicated to latency sensitive front haul traffic - (shown as queue marking 5). This queue must be serviced in strict priority over all other queues up - -![O-RAN Alliance logo](dfc404a5cd40cf7c47d775536cb7d9b5_img.jpg) - -The O-RAN Alliance logo, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -1 to its shaped or policed limit. If the node is providing transit for G.8275.2 PTPoIP as a PTP -2 unaware element, then PTP packets MUST also be scheduled in this queue. If the hardware -3 supports multiple levels of strict priority queueing, and is a PTP unaware node, then PTP MAY also -4 be scheduled in a dedicated highest priority queue to minimise packet delay variation (PDV). - -5 Two further latency sensitive queues are defined, one for network control (shown as queue marking -6 7) and one for other latency sensitive transit traffic (e.g. latency sensitive Backhaul or Midhaul U- -7 plane or latency sensitive business or consumer traffic) (shown as queue marking 2). These queues -8 should be configured to be serviced with a latency bound suitable for the traffic associated with -9 them. The scheduling model used will be dependent on the specific HW choice. For example, this -10 could be a guaranteed bandwidth queue with suitable scheduler weight and queue depth, or a high -11 priority queue with lower priority scheduling than that for the latency sensitive Fronthaul traffic. - -12 Additional queues are defined for guaranteed bandwidth traffic (Management (shown as queue -13 marking 6), guaranteed bandwidth U-plane (shown as queue marking 3,4) and best effort traffic -14 (shown as queue marking 0,1)). - -15 Additional queues may be supported if the carrier deems necessary. - -16 The example queue model is show in Figure 14-1 provides example MPLS “Traffic Class” (TC) or -17 often called EXP, based classification for the queues. It should be noted that a transport based on -18 SRv6 allows the use of IP DSCP as the QoS marker, allowing for more flexibility in the queue -19 model, and that more queues may be used if the marking scheme and hardware are appropriate. - -20 **[R79]:** MUST support a minimum of 6 HW queues per physical interface - -#### 22 14.1.2.2 Hierarchical queue model - -23 The hierarchical queue model provides a capability to support a segmented infrastructure “Hard -24 slicing” where the QoS model for each slice is different, or where each slice requires dedicated -25 bandwidth. (see Figure 14-2 for details) - -26 Here the model the transport device must support a minimum of two levels of queue hierarchy on -27 each physical interface. - -![Figure 14-2 Sample hierarchical queue model diagram. The diagram shows two tiers of queues. The first tier (child level) consists of 10 individual queues, each labeled with a traffic type and an example MPLS TC value. The second tier (parent level) consists of two large vertical pipes representing schedulers. The first scheduler is connected to the first five child queues (TCs 5, 2, 7, 6, 3,4), and the second scheduler is connected to the remaining five child queues (TCs 5, 2, 7, 6, 3,4). Both schedulers output into a single horizontal pipe on the right, representing the physical interface. Curved arrows indicate the flow of traffic from child queues to schedulers and then to the output pipe.](2d548db0b26b7bf33244320322d5ee2c_img.jpg) - -Example queue marking -(E.g. MPLS TC) - -| Traffic Type | Example queue marking (E.g. MPLS TC) | -|------------------------------------------------------------------------|--------------------------------------| -| Latency sensitive fronthaul traffic + G.8275.2 PTP (unaware node) (PQ) | 5 | -| Latency sensitive U-plane + business traffic | 2 | -| Latency sensitive Network control plane(BFD, IGP, PTP) | 7 | -| Guaranteed bandwidth traffic (e.g. management) | 6 | -| Guaranteed bandwidth U-plane and business traffic | 3,4 | -| Other best effort (may be guaranteed) | 0,1 | -| Latency sensitive fronthaul traffic + G.8275.2 PTP (unaware node) (PQ) | 5 | -| Latency sensitive U-plane + business traffic | 2 | -| Latency sensitive Network control plane(BFD, IGP, PTP) | 7 | -| Guaranteed bandwidth traffic (e.g. management) | 6 | -| Guaranteed bandwidth U-plane and business traffic | 3,4 | -| Other best effort (may be guaranteed) | 0,1 | - -Figure 14-2 Sample hierarchical queue model diagram. The diagram shows two tiers of queues. The first tier (child level) consists of 10 individual queues, each labeled with a traffic type and an example MPLS TC value. The second tier (parent level) consists of two large vertical pipes representing schedulers. The first scheduler is connected to the first five child queues (TCs 5, 2, 7, 6, 3,4), and the second scheduler is connected to the remaining five child queues (TCs 5, 2, 7, 6, 3,4). Both schedulers output into a single horizontal pipe on the right, representing the physical interface. Curved arrows indicate the flow of traffic from child queues to schedulers and then to the output pipe. - -**Figure 14-2 Sample hierarchical queue model** - -In this model the first, or child level defines the queues needed to support the capabilities associated with the slice. These might be the same as in the flat queue model or may be different. In the second or parent level, a scheduler is defined to allocate the maximum bandwidth that will be available to that hard slice. It should be noted that the sum of the guaranteed bandwidth to each shaper should not exceed the interface bandwidth. As with the flat queue model, example is provided which should be adapted for the specific HW in use. - -**[R80]:** MUST support a minimum of 6 HW queues per logical interface - -**[R81]:** MUST support a minimum of two tiers of configurable scheduler per physical interface - -### 14.1.3 Transport network core interface marking structure - -Transport nodes should preserve the QoS marking of transported frames and packets across the transport network. This should be accomplished via the use of the pipe or short pipe model described in IETF RFC2983[61]. - -The specific marking structure used to define the transport QoS behaviours is left to the individual providers and is dependent on the transport encapsulation implemented. An example marking structure for MPLS TC values is shown in Figure 14-1. - -### 14.1.4 Core interface scheduling model - -Latency sensitive and network control plane traffic should be forwarded using an expedited forwarding model as described in IETF RFC 3246[69]. In order to preserve minimum latency, these queues should be scheduled with a maximum of one packet in each queue and be allocated a priority forwarding schedule in the NPU. To prevent bandwidth starvation of non-priority scheduled traffic, each priority queue should be shaped or policed at a combined capacity less than the physical rate of each egress interface in the core, and with sufficient bandwidth capacity available - -![O-RAN Alliance logo](458010a93dad72d629626466df35b3d4_img.jpg) - -O-RAN Alliance logo - -1 for the latency sensitive Fronthaul services they are supporting. Where needed a TSN based - 2 scheduler may also be implemented if the interface bandwidth demands such optimisation. Details - 3 on TSN may be found in section 10.1.1.2.1. - -4 Guaranteed bandwidth queues (management and best effort) should be scheduled using the assured - 5 forwarding model described in IETF RFC 2597[53]. These queues should be scheduled using a - 6 Weighted Round Robin (WRR), Minimum deficit round robin (MDRR) or weighted fair queue - 7 (WFQ) scheduler, depending on the capability available in the NPU. Where network control traffic - 8 is assigned to a guaranteed bandwidth queue, the scheduler for that queue must be configured to - 9 support minimum latency to ensure time sensitive network control traffic (eg BFD) is not delayed. - 10 The scheduler MUST have sufficient buffer capacity to avoid loss in these queues due to the effects - 11 of micro-burst caused by the aggregation of traffic from different ingress interfaces, or speed - 12 mismatch (higher to lower). - -## 13 14.2Xhaul transport network edge interface QoS - -14 PE elements in the transport network domain will be responsible for providing logical separation - 15 and encapsulation for transport. It can be assumed that there are two types of traffic that will be - 16 presented for transport. - -- 17 1. Ethernet frames. For example, RoE or eCPRI frames not using an IP header. -- 18 2. IP packets. For example, eCPRI packets or Backhaul traffic whose encapsulation includes an - 19 IP header. - -### 20 14.2.1 Transport network domain PE ingress classification of Ethernet frames. - -21 For the purposes of this section, it is assumed that there will be a physical or logical interface - 22 attaching the Ethernet frame device to the transport network edge PE. As an example, this could be - 23 a Mobile Client, such as a Front Haul Gateway or O-DU supporting an RU using RoE. PE nodes in - 24 the transport network will perform classification on traffic ingressing the domain using different - 25 models. - -![Diagram showing three models for PE ingress classification of Ethernet frames. Each model shows an RRH connected to a RoE mapper, which is connected to a PE. 1) Untagged frames (port) - the connection is a simple line. 2) Tagged frames (VLAN), PCP unset or untrusted - the connection is a simple line. 3) Tagged frames (VLAN), PCP set and trusted - the connection is a simple line.](1bd6a020aa71784ed74367899560cbb9_img.jpg) - -26 - -1) Untagged frames (port) - -2) Tagged frames (VLAN), PCP unset or untrusted - -3) Tagged frames (VLAN), PCP set and trusted - -Diagram showing three models for PE ingress classification of Ethernet frames. Each model shows an RRH connected to a RoE mapper, which is connected to a PE. 1) Untagged frames (port) - the connection is a simple line. 2) Tagged frames (VLAN), PCP unset or untrusted - the connection is a simple line. 3) Tagged frames (VLAN), PCP set and trusted - the connection is a simple line. - -![O-RAN Alliance logo](c1ac5a44074f1a512562283a8b7a4763_img.jpg) - -O-RAN Alliance logo - -Figure 14-3 Ethernet ingress classification models - -1 - -2 - -3 - -4 - -5 - -6 - -7 - -8 - -9 - -10 - -11 - -12 - -13 - -14 - -15 - -16 - -17 - -18 - -19 - -20 - -21 - -22 - -23 - -24 - -25 - -26 - -27 - -28 - -29 - -30 - -31 - -32 - -33 - -34 - -35 - -36 - -37 - -38 - -39 - -40 - -41 - -Figure 14-3 identifies three models by which transport domain PE devices will classify traffic originating from a ROE mapper. All three models must be supported. - -#### 14.2.1.1 Untagged frames - -As per Figure 14-3(1) the Mobile Client (MC) presents a flow of untagged frames to the PE. The PE uses the local port as the context for the MC. This context must be preserved in the transport network and presented at the port level (untagged) at the remote PE. Because the PE has no knowledge of the MC encapsulation model, or priority needed for each frame, all frames must be given the same appropriate treatment (and transport marking) to support the encapsulation mode. It can be assumed that the operator has this knowledge at the port level and can apply the appropriate local policy for both transport marking and PHB for all frames. These frames should be encapsulated with the appropriate transport and marked with QoS marking for carried in the class defined in section 14.1.2 for Latency sensitive Fronthaul traffic. - -#### 14.2.1.2 Tagged frames (VLAN), PCP unset or untrusted - -As per Figure 14-3(2) The RoE mapper presents a flow of VLAN tagged frames to the PE. The PE uses the VLAN and local port as the context for the RoE mapper. This context must be preserved in the transport network and presented at the remote PE with the same VLAN marking. Because the PE has no knowledge of the RoE mapper encapsulation model, or priority needed for each frame, all frames must be given the same appropriate treatment and transport marking, to support the encapsulation mode. It can be assumed that the operator has this knowledge at the either the VLAN or port level and can apply the appropriate local policy for both transport marking and PHB for all frames. These frames should be encapsulated with the appropriate transport and marked with QoS marking for carried in the class defined in 14.1.2 for Latency sensitive Fronthaul traffic. - -#### 14.2.1.3 Tagged frames (VLAN), PCP set and trusted - -As per Figure 14-3(3). The RoE mapper presents a flow of VLAN tagged frames to the PE. The PE uses the VLAN and local port as the context for the RoE mapper. This context must be preserved in the transport network and presented at the remote PE with the same VLAN marking. In this model it is assumed that the RoE mapper supports a differential marking scheme for flows requiring different treatment. The marking is placed in the PCP field of the VLAN header (described by IEEE 802.1p). The PE should be capable of classifying flows based on the PCP marking and implementing an appropriate PHB. The PE should also apply an appropriate marking to the frames as supported by the transport model in use. It can be assumed that the operator has this knowledge of the PCP markings from the RoE mapper. - -Each class presented by the RoE mapper must be mapped to one of the class markings defined in section 14.1.2. It is assumed that the operator has appropriate knowledge to determine this mapping. - -**[R82]:** MUST support classification of frames based on 802.1p PCP bit field - -**[R83]:** MUST support classification of frames based on incoming logical interface. - -![O-RAN Alliance logo](94d139463de55bcc311241aab71fac81_img.jpg) - -O-RAN Alliance logo - -1 -2 **[D41]:** SHOULD support ingress policing using a single rate 2 color policer described in RFC2698 -3 [54] or RFC4115 [78] - -4 **[D42]:** SHOULD support ingress policing using a dual rate 3 color policer described in RFC2698 -5 [54] or RFC4115 [78] - -6 **[R84]:** MUST support ingress marking of frames based on result of soft policing using policers in -7 [D41]: and [D42]:. - -## 8 9 14.2.2 Transport domain PE ingress classification IP packets. - -10 Unlike Ethernet frames, IP packets will always have a QoS marking field available to them. As a -11 result, we do not have to be concerned with IP packets arriving unmarked from a QoS perspective -12 and must simply determine if we trust the marking. - -### 13 14.2.2.1 Marked packets DSCP untrusted - -14 Similar to Figure 14-3(2). The client element presents a flow of DSCP marked packets to the PE. -15 The PE uses local port as the context for the flow. This context must be preserved in the transport -16 network and presented at the remote PE with the same DSCP marking. Because the PE has no -17 knowledge of the client element encapsulation model, or priority needed for each packet, all packets -18 must be given the same appropriate treatment and transport marking, to support the encapsulation -19 mode. It can be assumed that the operator has this knowledge at the port level and can apply the -20 appropriate local policy for both transport marking and PHB for all frames. These frames should be -21 encapsulated with the appropriate transport and marked with QoS marking for carried in the class -22 defined in section 14.1.2 for Latency sensitive Fronthaul traffic. - -### 23 14.2.2.2 Marked packets DSCP trusted - -24 Similar to Figure 14-3. The client element presents a flow of DSCP marked packets to the PE. The -25 PE uses the local port as the context for the flow. This context must be preserved in the transport -26 network and presented at the remote PE with the same DSCP marking. In this model it is assumed -27 that the client element or IP source supports a differential marking scheme for flows requiring -28 different treatment. The marking is placed in the DSCP field of the IP header. The PE should be -29 capable of classifying flows based on the DSCP marking and implementing an appropriate PHB. -30 The PE should also apply an appropriate marking to the frames as supported by the transport model -31 in use. It can be assumed that the operator has this knowledge of the DSCP markings from the client -32 element or IP source. - -33 Each class presented by the client element or IP source must be mapped to one of the class -34 markings defined in section 14.1.2. It is assumed that the operator has appropriate knowledge to -35 determine this mapping. - -36 **[R85]:** MUST support classification of frames based on IPv4 DSCP field - -37 -38 **[R86]:** MUST support classification of frames based on IPv6 DSCP field - -![O-RAN Alliance logo](805f16ab0445ab8949eaca614d4a06d6_img.jpg) - -O-RAN Alliance logo - -### 1 14.2.3 Admission control - -2 Admission control via policing should be applied to all sources of traffic at the PE. It is important to - 3 recognise that suitable capacity MUST be made available for all traffic (especially where loss is - 4 problematic) in each element of the infrastructure. Where statistical multiplexing is expected to be - 5 used to support additional service capacity in the network, excess traffic, beyond that which is - 6 committed, MUST be marked as excess and be eligible for drop to protect other committed traffic - 7 under heavy usage periods. - -### 8 14.2.4 PE Egress scheduling - -9 Traffic arriving at a PE from the infrastructure, to be transmitted to a CE device should be done so - 10 based on the model used for its classification on ingress. - -#### 11 14.2.4.1 Unclassified traffic - -12 Where an interface is using unclassified traffic, that is; - -13 all traffic is always marked as default by the CE or - -14 traffic with no marking available e.g. ethernet without a VLAN header, - -15 traffic should be forwarded on a FIFO basis. In this model it must be ensured that the flow of traffic - 16 into the PE toward the CE MUST be at a lower rate than the interface attaching the PE to the CE to - 17 avoid congestion resulting in latency or loss. - -#### 18 14.2.4.2 Classified traffic - -19 Where an interface is using classified traffic, that is traffic has a marking scheme available, and - 20 traffic is marked using this scheme, traffic should be forwarded to the CE with a queueing scheme - 21 and scheduling model that is appropriate to the traffic for that CE. The specific marking and - 22 queueing scheme are beyond the scope of this document but MUST be understood by the operator. - 23 In this model the PE MUST support the classification and queueing of the CE destined traffic based - 24 on the marking on the CE packet or frame. This is understood as “pipe model – after” as defined in - 25 IETF RFC 2983, section 5 – 6. - -26 - -27 **[R87]:** MUST support classification of encapsulated frames or packets based on 802.1p PCP bit - 28 field or IP DSCP field as described in IETF RFC 2983 section 5-6 - -29 - ---- - -## 30 15 Multicast - -### 31 15.1 Multicast use cases - -32 Multicast use cases in an Xhaul transport network come from two categories as described below. - 33 - -### 15.1.1 Multicast transport for fixed line services - -As mentioned in the requirements section: - -*“ITU-T GSTP-TN5G: Transport support of IMT-2020/5G” identifies the need for the transport to be multi-service in nature. In addition to mobile services, the infrastructure needs to support fixed line consumer and enterprise services.* - -Fixed line consumer/enterprise services like IPTV and VPN all require multicast support in the transport network. - -### 15.1.2 MBMS/5MBS transport - -3GPP TS 23.246 *MBMS Architecture and Functional Specification* (R15) and TR 23.757 *Study on architectural enhancements for 5G multicast-broadcast services (5MBS, R17)* all support “shared delivery method” with which multicast/broadcast traffic is transported via multicast to RAN nodes (N3/N9), who will then transmit over the air. This means multicast transport is needed to CU-UP. - -Another “individual delivery method” may also be used – UPFs send individual copies of multicast traffic over PDU sessions to UEs, transparent to RAN nodes. With this method, if UPFs are distributed, then multicast should be used in DNN to the UPFs (N6). Note that, a UPF may be connected to multiple DNNs as the anchored PDU sessions may belong to multiple DNNs. - -![Diagram illustrating Mobile multicast use cases. It shows two delivery methods from a 5G CN to UEs via a 5G RAN. The top method is 'Shared MBS Traffic delivery' using 'Shared Transport' to a 5G RAN, which then uses 'PTM or PTP over radio' to deliver to two UEs. The bottom method is 'Individual MBS Traffic Delivery' where traffic is replicated in the 5G CN and sent via separate 'PDU Sessions' through the 5G RAN to two different UEs.](10ceb47973510a1b47421741263146cc_img.jpg) - -The diagram illustrates two mobile multicast use cases within a 5G architecture. On the right, a '5G CN' (Core Network) receives 'MBS traffic'. In the top case, the traffic is sent via 'Shared Transport' to a '5G RAN' (Radio Access Network) for 'Shared MBS Traffic delivery'. The 5G RAN then transmits this to two 'UE' (User Equipment) devices using 'PTM or PTP over radio'. In the bottom case, the traffic is first processed by a 'Replication' function in the 5G CN, resulting in 'Individual MBS Traffic Delivery'. This individual traffic is sent over separate 'PDU Sessions' through the 5G RAN to two different 'UE' devices. - -Diagram illustrating Mobile multicast use cases. It shows two delivery methods from a 5G CN to UEs via a 5G RAN. The top method is 'Shared MBS Traffic delivery' using 'Shared Transport' to a 5G RAN, which then uses 'PTM or PTP over radio' to deliver to two UEs. The bottom method is 'Individual MBS Traffic Delivery' where traffic is replicated in the 5G CN and sent via separate 'PDU Sessions' through the 5G RAN to two different UEs. - -Figure 15-1 Mobile multicast use cases - -## 1 15.2 Overlay and underlay multicast - -2 The multi-service nature of 5G transport network is not only that the transport network is also used - 3 for fixed line service transport. Even for 5G itself, the same transport network is used for multiple - 4 purposes, e.g., N3/N9 transport, N6 transport and Xhaul transport. - -![Figure 15-2: VPN infrastructure for mobile. The diagram shows a network architecture with five layers: Cell site, Access, Pre-Aggregation, Aggregation, and Core. At the Cell site, there are O-RU, O-DU, and UPF components. The Access layer contains a UPF and an O-CU/DU. The Pre-Aggregation, Aggregation, and Core layers each contain a UPF. Two VPN tunnels are shown: 'VPN for N6 (DN)' in orange at the top, connecting the UPF in the Cell site to the UPF in the Core; and 'VPN for N3/N9' in green at the bottom, connecting the O-DU in the Cell site to the UPF in the Core. The tunnels are overlaid on a common transport network represented by black lines and circular nodes.](f1ba1e68228ebd4c3109371574a723e6_img.jpg) - -Figure 15-2: VPN infrastructure for mobile. The diagram shows a network architecture with five layers: Cell site, Access, Pre-Aggregation, Aggregation, and Core. At the Cell site, there are O-RU, O-DU, and UPF components. The Access layer contains a UPF and an O-CU/DU. The Pre-Aggregation, Aggregation, and Core layers each contain a UPF. Two VPN tunnels are shown: 'VPN for N6 (DN)' in orange at the top, connecting the UPF in the Cell site to the UPF in the Core; and 'VPN for N3/N9' in green at the bottom, connecting the O-DU in the Cell site to the UPF in the Core. The tunnels are overlaid on a common transport network represented by black lines and circular nodes. - -5 -6 -7 -8 -9 -**Figure 15-2 VPN infrastructure for mobile** - -10 As described in the service capability section, different transports are rendered as different - 11 IPVPN/EVPN overlay services over a common transport underlay. When it comes to multicast, it is - 12 just an aspect of the IPVPN/EVPN, as further described in section 13. - 13 - -## 14 15.3 Recommendation/considerations for multicast solutions - -15 With the background discussion provided in Annex E: Multicast Technologies background, the - 16 following multicast solutions are recommended: - 17 - -- 18 1. BGP-MVPN and EVPN-BUM for overlay, with tunnel segmentation if different tunnel - 19 types/instances are necessary/desired for different ASes/areas. -- 20 2. Currently deployed underlay tunnel solutions can still be used even with Segment Routing - 21 (mLDP/RSVP protocol would only be used for multicast not unicast purposes). If end-to- - 22 end tunnels are used without tunnel segmentation, PIM RPF Vector or mLDP Recursive - 23 FEC or controller signalling need to be used. -- 24 3. Controller-signaled multicast can be used if tree calculation and signalling by controllers are - 25 desired to satisfy TE constraints, or to remove legacy LDP/RSVP protocols from the - 26 network. This includes SR-P2MP and BGP-signalled mLDP tunnels, with the latter offering - 27 the best flexibility – easy transition from existing mLDP deployment and flexible ways of - 28 tunnel identification via mLDP FEC. -- 29 4. BIER can be deployed in (part of) the network when enough routers support BIER - 30 (RFC8279 [134], RFC8296 [136]). - 31 - -32 Depending on the selected solution, some of the following standards may need to be supported. - 33 - -34 **[O1]:**BGP Encoding and Procedures for Multicast in MPLS/BGP IP VPNs, RFC6514 [122] - -![O-RAN ALLIANCE logo](7f9a7d3e2d9215f8ee2f56fec9c3d9e4_img.jpg) - -O-RAN ALLIANCE logo - -1 -2 **[O2]:**BGP MPLS-Based Ethernet VPN, RFC7432 [123] - -3 -4 **[O3]:**Update on EVPN BUM Procedures, RFC9572 [169] - -5 -6 **[O4]:**Protocol Independent Multicast - Sparse Mode (PIM-SM) Protocol Specification, RFC 7761 -7 [127] - -8 -9 **[O5]:**The Reverse Path Forwarding (RPF) Vector TLV, RFC 5496 [111] - -10 -11 **[O6]:**Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint -12 Label Switched Paths, RFC6388 [118] - -13 **[O7]:**Using Multipoint LDP When the Backbone Has No Route to the Root, RFC 6512 [120] - -14 -15 **[O8]:**Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to- -16 Multipoint TE Label Switched Paths (LSPs), RFC4875 [93] - -17 **[O9]:**Controller Based BGP Multicast Signaling, draft-ietf-bess-bgp-multicast-controller [179] - -18 -19 **[O10]:** Segment Routing Point-to-Multipoint Policy, draft-ietf-pim-sr-p2mp-policy [184] - -## 20 16 Packet-switched orchestration and telemetry - -21 -22 -23 Packet switched orchestration and telemetry covers how the packet switching transport network is -programmed at a device and service level and how telemetry data is retrieved from TNEs. This will -be covered in a separate document[23]. - -## 24 17 Packet Switched TNE Security - -25 -26 -27 Packet Switched Transport Network Equipment (TNE) plays a vital role in building the transport -infrastructure needed to support a 5G infrastructure. As such the packet switched TNEs needs to -support a set of security features associated with: - -- 28 1) The security of the TNEs (both physical security nad user access security) -- 29 2) The security of the network control, data and management plane protocols the TNEs run -- 30 3) Security functionality required by the TNEs to support security functionality required by the 5G -31 mobile components. - -32 -33 -34 -35 -36 This section, which deals with transport specific requirements, in association with O- -RAN.WG11.Security-Requirements-Specifications [27] provides guidelines and requirements for -security features required for an O-RAN compliant packet switched transport infrastructure. - -### 37 17.1 TNE physical security - -38 -39 -40 This section describes the measures to improve the security of the TNE, when the TNE is placed in -unsecured, publicly accessible location. For example, such as remote unattended site, or a shared -rack with a partner or customer organization - -![O-RAN Alliance logo](32f2554a03fff77b461bd9f3704a91a3_img.jpg) - -The logo for the O-RAN Alliance, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -### 1 17.1.1 Console Port - -2 Typical TNE has a console port, which is typically used for last resort, emergency access to the -3 TNE. Console port on TNE MUST be properly secured to prevent unauthorized access over the -4 console port. - -5 -6 One type of such unauthorized access could happen, when an authorized user is logged into the -7 console port and inadvertently disconnects the cable without properly logging out. The next time -8 someone connects to the console, they could have access to the TNE without authenticating. - -9 -10 **[R88]:** TNE MUST automatically log out a user connected over console when console cable is -11 disconnected - -12 -13 The other type of unattended session occurs when a connection is left idle, which is rather common -14 situation when a terminal server is used, as in that case the console cable is always connected. - -15 -16 **[R89]:** TNE MUST support automatic log out of users connected over console, when the session is -17 idle for a (configurable) period - -18 -19 The Root or “Super user” account is the most important and most powerful user account on a TNE. -20 Very often, TNEs do not provide idle timers for the root account. Therefore, to increase the console -21 security, the root user MUST be prevented from directly login using the console. This essentially -22 forces console users to initially authenticate using a regular user account, and subsequently, from -23 within the session of the regular user, authenticate as the root user. If the root session, running -24 within regular user session, is idle for a (configurable) period, regular user session is idle as well. -25 Based on [R89]:, the regular user session MUST be automatically logged out, which will -26 automatically break all other user sessions (i.e., root user) within that regular user session, too. - -27 -28 **[R90]:** TNE MUST prevent root user login over the console - -### 29 17.1.2 Auxiliary Port - -30 -31 Many TNEs have as well an auxiliary port, which is intended to be used with a modem to provide -32 dial-in access to a TNE in remote locations. In most cases, the auxiliary port can also be used as a -33 secondary console port, in which case it inherits some console port security concerns. In most cases, -34 the auxiliary port is not used in typical network deployments. Leaving that port enabled creates -35 security concern. - -36 -37 **[R91]:** TNE MUST provide capability to disable auxiliary port - -38 -39 **[R92]:** TNE MUST provide capability to secure auxiliary port in a similar manner as console port, if -40 the auxiliary port is used - -### 41 17.1.3 USB Port - -42 -43 Many TNEs today have external user accessible USB ports used for booting the device off a USB -44 stored image or for loading software onto the device’s internal storage. The USB port can be -45 exploited to load malicious device software or used to easily transfer provider information in the -46 case of a device with a compromised management plane. In many cases the device when booting - -![O-RAN Alliance logo](dc0338212e8a6ac4e88649b89292e119_img.jpg) - -O-RAN Alliance logo - -1 will give the user an option to boot off the USB if a capable USB storage device is connected. - 2 Leaving the USB port active creates a security concern. - -3 - 4 **[R93]:** TNE MUST provide capability to disable USB port - -#### 5 6 17.1.4 Front Panel functions - -7 Many TNEs have front panel with physical buttons, LCD displays or menu options to perform - 8 system control and maintenance functions, like bringing a line-card offline or online, restoring the - 9 factory default configuration, acknowledging alarms, etc. There may be scenarios, where TNEs are - 10 placed in an unsecure location, such as remote unattended site, or a shared rack with a partner or - 11 customer organization. Such unsecure locations require enhanced security for front panel functions - 12 (buttons, LCD displays, menus, etc.). - -13 - 14 **[R94]:** TNE MUST provide capability to disable/enable front panel functions (buttons, menus, LCD - 15 displays, etc.) - -#### 16 17 17.1.5 TNE software security - -18 Due to the security risks posed by malicious software, the TNE must validate software loaded onto - 19 the device before execution. The method for implementation is outside the scope of this document, - 20 however the signing of all software images by the TNE vendor's private key is the common - 21 industry practice. Image signing applies to boot software as well as incremental updates applied to - 22 a running device. - -23 - 24 **[D43]:** TNE SHOULD validate the device boot loader before execution, halting boot on revocation - -25 **[D44]:** TNE SHOULD support signed boot images validated by the device boot loader before - 26 execution, halting boot on revocation - -27 **[D45]:** TNE SHOULD validate all software images and updates prior to execution - -#### 28 29 17.1.6 Zero Touch Provisioning - -30 Due to the scale of today's mobile packet switched networks, Zero Touch Provisioning (ZTP) is - 31 often used either in the field to deploy new devices or replace existing devices with hardware - 32 impairments. While ZTP operations are typically internal to a provider network, it's important to - 33 secure the communication and components used with ZTP. RFC 8572 [146] defines Secure ZTP, a - 34 framework for ensuring the ZTP process is secure end to end. The primary points of security for - 35 ZTP are: - -- 36 - 37 1) ZTP client validation, to ensure the client is trusted by the server before offering ZTP artifacts or - 38 configuration information -- 39 2) ZTP server validation, to ensure the server is trusted by the client before accepting any ZTP - 40 configuration or artifacts -- 41 3) Artifact validation, to ensure the ZTP components downloaded from the ZTP server are trusted - 42 before being loaded or executed - -43 - 44 **[R95]:** TNE MUST follow the SZTP framework defined in RFC 8572 [146] if the device - 45 supports ZTP - -![O-RAN Alliance logo](cfa6466163467e81d9b2d9c5785222bf_img.jpg) - -O-RAN Alliance logo - -1 **[R96]:** TNE MUST follow methods and formats defined in RFC 8366 [138] to ensure the validity of - 2 the device from the manufacturer using an Ownership Voucher - 3 - -#### 4 17.1.7 PXE boot over management or data ports - -5 Many TNEs today will attempt to boot via PXE as part of their Zero Touch Provisioning process. - 6 The ZTP process can run on the management Ethernet interface as well as on standard data - 7 interfaces. This process can be a security risk if the physical device location is compromised, - 8 allowing an attacker to load malicious software onto the device or compromise its boot integrity - 9 protections. - -10 - 11 **[R97]:** TNE MUST provide capability to disable ZTP, if ZTP is not in use - 12 - -### 13 17.2 TNE user access security - -14 This section describes the measures to improve the security of the TNE, preventing unauthorized - 15 user to access the device. - 16 - -#### 17 17.2.1 TACACS+ Authentication - -18 Typically, the default authentication used to authenticate user on the TNE is password - 19 authentication using locally stored user data (username, password). In large-scale deployments, like - 20 5G Xhaul deployment, local authentication database on each TNE is very impractical. Therefore, - 21 the recommended solution is to use TACACS+ server, which should always be considered the first - 22 and principal authentication method. - -23 - 24 After integrating the TNE into TACACS+ authentication infrastructure, the TACACS+ - 25 authentication method should be preferred over password authentication using local authentication - 26 database. When user authentication order is set on TNE (with TACACS+ authentication as first, and - 27 authentication using local authentication database as second) the user is first authenticated with - 28 TACACS+ server. If TACACS+ server responds (either granting the access or refusing the - 29 access), this response is used by the TNE to either allow or deny the user access to the device. - 30 However, if TACACS+ server doesn't respond (is unreachable), local password authentication is - 31 used to grant or deny access to the device. Therefore, it is always recommended to have limited - 32 number of local users defined on the TNE as a last resort for authentication. These users can be - 33 used for authentication purpose in failure cases, when TACACS+ server is not available. - 34 - -35 TACACS+ provides not only user authentication, i.e., to determine who a user is, but as well - 36 authorization, i.e., to grant access rights to certain portions of the TNE, or to certain configuration - 37 or operational commands on the TNE. Additionally, TACACS+ performs accounting, which is the - 38 action of recording what a user is doing and/or has done. This is commonly known as AAA - 39 (Authentication, Authorization, Accounting). - -40 - 41 - 42 **[R98]:** TNE MUST support TACACS+ for user authentication, in accordance with Section 5 of - 43 RFC 8907: "The Terminal Access Controller Access-Control System Plus (TACACS+) - 44 Protocol" [155] - 45 - -![O-RAN Alliance logo](7c944c119a9d45d12741620a742a3ab1_img.jpg) - -O-RAN Alliance logo - -1 **[R99]:** TNE MUST support TACACS+ for user authorization, in accordance with Section 6 of RFC - 2 8907: “The Terminal Access Controller Access-Control System Plus (TACACS+) Protocol” - 3 [155] - -4 - 5 **[D46]:** TNE SHOULD support TACACS+ for user accounting, in accordance with Section 7 of - 6 RFC 8907: “The Terminal Access Controller Access-Control System Plus (TACACS+) - 7 Protocol” [155] - -8 - 9 **[R100]:** TNE MUST support specification of authentication order, preferring TACACS+ - 10 authentication (RFC 8907 [155]) over authentication using local user database - 11 - -## 12 17.2.2 Login Message - -13 Typically, by default, no message is displayed by the TNE before or after login. It is strongly - 14 advised that a system login message is present before the user logs in, as well as another message - 15 after user successfully logged in. A strongly worded login banner SHOULD include statements - 16 regarding the following: - -- 17 ▪ Clear prohibition of unauthorized access. -- 18 ▪ Clear prohibition of unauthorized use. This warns authorized users against unauthorized use of - 19 the system. -- 20 ▪ Warning that the system may be monitored. Note that the wording might have important - 21 ramifications for successful prosecutions. Do not say the system will be monitored. -- 22 ▪ Statement that there is no expectation of privacy. This statement insures that no legal defense can - 23 be mounted claiming that the company should not have monitored an unauthorized user. -- 24 ▪ Statement that results of monitoring may be provided to the appropriate authorities. -- 25 ▪ Statement that continued use of the system implies consent to the stated terms and conditions. -- 26 ▪ Warning to log off immediately if consent is not given. - -27 - 28 Login banners SHOULD NOT include any of the following information: - -- 29 ▪ Information about the device type or software -- 30 ▪ Information about the device location -- 31 ▪ Contact information -- 32 ▪ Administrator information - -33 - 34 There could be two level of messages displayed by on TNE’s terminal: one message appearing - 35 before the user logs in, and 2nd message after the user logs in. - -36 - 37 **[R101]:** TNE MUST support modifiable messages displayed on the user session before and after - 38 user login - -![O-RAN ALLIANCE logo](02917cf4d4af3d6e32df094efdeceb85_img.jpg) - -The logo for the O-RAN Alliance, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with "ALLIANCE" in smaller letters underneath. - -O-RAN ALLIANCE logo - -1 -2 **[D47]:** Login banners SHOULD NOT include details about the device, location or -3 contact/administrator information -4 - -### 5 17.2.3 Security Protocols - -6 In order to provide secure user to access to TNEs for configuration management, security protocols -7 are required that provide Confidentiality, Integrity, Authenticity and replay protection. This section -8 provides details on Secure Shell (SSH, RFC4252, [84]) and Transport Layer Security (TLS, -9 RFC5246, [97] and RFC8446, [142]). - -#### 10 17.2.3.1 Secure Shell (SSH) - -11 Requirements for O-RAN elements supporting SSH are generally defined in the O-RAN -12 ALLIANCE TS: “O-RAN Security Protocols Specification” ([29]). - -13 -14 **[D48]:** TNEs supporting SSH SHOULD implement the protocol as defined in [29], clause 4.1. -15 - -#### 16 17.2.3.2 Transport Layer Security (TLS) - -17 Requirements for O-RAN elements supporting TLS are generally defined in the O-RAN -18 ALLIANCE TS: “O-RAN Security Protocols Specification” ([29]). - -19 -20 **[D49]:** TNEs supporting SSH SHOULD implement the protocol as defined in [29], clause 4.2. -21 - -### 22 17.2.4 Password requirements - -23 Variety of requirements can be used to strengthen passwords for greater security. TNE should -24 provide a framework allowing to enforce password rules defined by the operator to conform to a -25 particular set of requirements defined in operator’s security policy. These password rules may -26 include such things as length, number of changes, type of characters, numbers, or letters, case, etc. -27 - -28 **[D50]:** TNE SHOULD support definition and enforcement of user password rules like length, -29 number of changes, type of characters, numbers, or letters, case, etc. - -### 30 17.2.5 Device lockout - -31 Malicious users sometimes might try to log in to a secure TNE by guessing an authorized user -32 account’s password. Locking out a user account after several failed authentication attempts helps -33 protect the device from malicious users. -34 - -35 **[D51]:** TNE SHOULD have the possibility to lockout the user after a number of failed attempts, and -36 to set the amount of time before the user can attempt to log in to the device again. - -## 37 17.3 Transport Network control plane security - -### 38 17.3.1 Control plane DoS/DDoS protection - -39 A denial-of-service (DoS) attack against an TNE is any attempt to disturb legitimate traffic or deny -40 valid users access the TNE by using up all the resources of the TNE. Distributed denial-of-service - -![O-RAN Alliance logo](d73afb244bcc76da2339ec0d69bc0368_img.jpg) - -O-RAN Alliance logo - -(DDoS) attacks involve an attack from multiple sources, enabling a much greater amount of traffic to attack the TNE. The attacks typically use network protocol control packets to trigger a large number of exceptions, which are packets handed over from the data plane to the control plane of the TNE. This results in an excessive processing load that disrupts normal network operations. - -TNE MUST have DDoS protection capability, which enables the TNE to continue functioning while under an attack. It identifies and suppresses malicious control packets while enabling legitimate control traffic to be processed. TNE SHOULD have possibility to customize DDoS protection profiles allowing to optimize DDoS protection of network control traffic in a particular deployment. - -To protect against DDoS attacks, typically filters and policers for host-bound exception traffic are used. The filters completely block specific types of control traffic (for example, if OSPF is not used in particular deployment, there is no need to send OSPF packets to the TNE's control plane), while policers specify rate limits for individual types of protocol control packets or for all control packet types for a protocol. Control traffic is dropped when it exceeds policer values. Each violation SHOULD immediately generates a notification to alert operators about a possible attack. The violation SHOULD be counted, the time that the violation starts noted, and the time of the last observed violation noted. - -**[R102]:** TNE MUST support protection mechanisms (filters, policer) to protect own control plane from DoS/DDoS attacks - -**[D52]:** TNE SHOULD have the possibility to customize DoS/DDoS protection parameters to protect own control plane - -**[D53]:** TNE SHOULD have the possibility to raise alarms, when DoS/DDoS attacks are detected - -### 17.3.2 Control plane protocols protection - -Transport control plane uses various protocols to exchange information between TNEs. This information is required to build paths across transport network, exchange label information (in MPLS deployments), exchange service information (L3VPN, L2VPN), monitor the network state (periodic OAM messages), and more (for example, determine the virtual gateway state in multi-homed environment). These protocols could be divided into following groups: - -- IGP (e.g., OSPFv2, OSPFv3, IS-IS) -- Multicast (e.g., PIM, MSDP) -- Protocols to distribute transport labels (e.g. LDP, RSVP) -- Other protocols (e.g. BFD, VRRP, ...) - -This document doesn't mandate any specific protocol to be used. For example, one deployment could use OSPFv2 as the IGP, while other deployment could use IS-IS as the IGP. However, if certain protocol is used, this document mandates minimum security requirements for each protocol that must be fulfilled. - -![O-RAN Alliance logo](887ea91be733df298b3c9643b2fbec60_img.jpg) - -O-RAN Alliance logo - -### 17.3.2.1 IS-IS - -All IS-IS packets (Hello, Link State, Sequence Numbers) shall be authenticated with the Hashed Message Authentication Code with the Secure Hash Algorithm (HMAC-SHA-1) cryptographic checksum in accordance with the recommendations outlined in RFC 5310: “IS-IS Generic Cryptographic Authentication” [105]. Cryptographic checksum is calculated over additional fields from IS-IS packets (LSP ID, Sequence Number) not covered by basic IS-IS checksum defined in ISO/IEC 10589:2002: “Intermediate System to Intermediate System intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode network service” [215], Section 7.3.11. With basic IS-IS checksum, undetected bit errors (caused for example due to some hardware failure) in LSP ID or Sequence Number fields may lead to complete network outage in the worst case. - -**[R103]:** In deployments using IS-IS, TNE MUST support HMAC-SHA-1 authentication for all IS-IS packets (Hello, Link State, Sequence Numbers) in accordance with RFC 5310: “IS-IS Generic Cryptographic Authentication” [105] - -### 17.3.2.1 OSPFv2 - -OSPFv2 has built-in authentication mechanism defined in RFC 2328: “OSPF Version 2” [49]. It defines three authentication types: - -- 0: Null authentication -- 1: Simple password -- 2: Cryptographic authentication - -Null (no authentication) and simple (clear text) authentication methods are not sufficient in today’s network. - -**[R104]:** In deployments using OSPFv2, TNE MUST support cryptographic authentication in accordance with RFC 2328: “OSPF Version 2” [49]. - -### 17.3.2.2 OSPFv3 - -OSPF version 3 (OSPFv3), unlike OSPF version 2, does not have a built-in authentication method and relies on IPsec to provide this functionality. This authentication functionality for OSPFv3 is defined in RFC 4552: “Authentication/Confidentiality for OSPFv3” [86]. - -**[R105]:** In deployments using OSPFv3, TNE MUST support IPsec based authentication for OSPFv3 packets in accordance with RFC 4552: “Authentication/Confidentiality for OSPFv3” [86] - -### 17.3.2.3 BGP - -BGP is TCP based protocol, therefore it benefits from RFC 5925: “The TCP Authentication Option” (TCP-AO) [115] to protect against the malicious or accidental insertion of unauthorized BGP data into the network by preventing the establishment of BGP adjacencies with any unauthenticated router. As per [115] TCP-AO specifies the use of stronger Message Authentication Codes (MACs), protects against replays even for long-lived TCP connections, and provides more details on the association of security with TCP connections than TCP MD5 introduced in the BGP specification [81]. Further, TCP-AO uses cryptographic algorithms to compute the MAC that is - -![O-RAN Alliance logo](6719a115173a966954d1bc7d03d7c80c_img.jpg) - -O-RAN Alliance logo - -1 used to authenticate a segment and its headers. MAC algorithms are specified in a separate RFC - 2 5926: “Cryptographic Algorithms for the TCP Authentication Option (TCP-AO)” [116]. This - 3 allows updating the algorithm requirements independently from the protocol. - -4 - 5 **[R106]:** TNE MUST support the TCP Authentication Option Authentication to secure BGP - 6 sessions in accordance with RFC 5925: “The TCP Authentication Option Authentication” - 7 [115] - -8 - 9 **[R107]:** TNE MUST support HMAC-SHA-1-96 MAC algorithm for TCP-AO in accordance with - 10 RFC 5926: “Cryptographic Algorithms for the TCP Authentication Option (TCP-AO)” [116] - -11 - 12 **[D54]:** TNE SHOULD support AES-128-CMAC-96 MAC algorithm for TCP-AO in accordance - 13 with RFC 5926: “Cryptographic Algorithms for the TCP Authentication Option (TCP-AO)” - 14 [116] - -#### 15 16 17.3.2.4 LDP - -17 LDP, similarly to BGP, uses TCP for underlay transport. Therefore, TCP-AO [115] applies to LDP - 18 as well. - -19 - 20 **[R108]:** In deployments using LDP, TNE MUST support the TCP Authentication Option - 21 Authentication to secure LDP sessions in accordance with RFC 5925: “The TCP - 22 Authentication Option Authentication” [115] - -#### 23 24 17.3.2.1 RSVP - -25 IETF defined authentication for RSVP using MD5 one-way hashes in RFC 2747: “RSVP - 26 Cryptographic Authentication” [56]. RSVP protocol exchanges can be authenticated to guarantee - 27 that only trusted neighbors participate in setting up reservations. RSVP authentication uses an - 28 HMAC MD5 message-based digest. This scheme produces a message digest based on a secret - 29 authentication key and the message contents. - -30 - 31 Small error correction to RFC 2547 [56] was provided via RFC 3097 “RSVP Cryptographic - 32 Authentication—Updated Message Type Value” [64]. IETF didn’t specified, so far, any more - 33 modern authentication method for RSVP. - -34 - 35 **[R109]:** In deployments using RSVP, TNE MUST support MD5-based cryptographic - 36 authentication to secure RSVP sessions in accordance with RFC 2747: “RSVP - 37 Cryptographic Authentication” [56] - -38 - 39 **[R110]:** In deployments using RSVP, TNE MUST support amendment to the cryptographic - 40 authentication in accordance with RFC 3097 “RSVP Cryptographic Authentication— - 41 Updated Message Type Value” [64]. - -### 42 17.4 Port-based network access control (IEEE 802.1X-2020) - -43 WG11 has standardized (O-RAN.WG11.Security-Requirements-Specifications [27]) on IEEE - 44 802.1X-2020 [41] as the port security mechanism in O-RAN compliant network infrastructure. - -![O-RAN Alliance logo](996c91d1d5b379328eade886b5451672_img.jpg) - -The logo for the O-RAN Alliance, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with the word "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -1 Based on [27], from the transport network domain perspective, following aspects of IEEE 802.1X- -2 2020 [41] SHALL be supported on the TNE deployed in Open Fronthaul - -3 -4 **[R111]:** Port-based network access control for point-to-point LAN segments for both port types: -5 with Layer-2 and Layer-3 encapsulation. Note: VLAN-based access control or access control -6 for non-point-to-point LAN segments is optional. - -7 -8 **[R112]:** IEEE 802.1X-2020 [41] authenticator functionality for each port connection towards the -9 O-RAN compliant network elements. - -10 -11 IEEE 802.1X-2020 [41] can be used with various authentication methods to interact with an -12 authentication server. The exact requirements, mandatory and optional methods are specified in O- -13 RAN.WG11.Security-Requirements-Specifications [27]. - -14 -15 Figure 17-1 outlines the scope of IEEE 802.1X in Open Fronthaul showing all features required on -16 TNE deployed in Open Fronthaul point-to-point LAN segment links for support of TNE-to-O-RU, -17 TNE-to-FHG, TNE-to-FHM, TNE-to-O-DU TNE-to-Compute or TNE-to-O-Cloud-Gateway. O- -18 DU can be physical O-DU (O-DU on a bare-metal) directly connected to TNE (1), virtual O-DU -19 deployed on a compute node directly connected to the TNE (2), or an O-DU deployed in the O- -20 Cloud, which connects to TNE via O-Cloud gateway (3). In use cases (2) and (3) TNE uses IEEE -21 802.1X [41] authentication not towards O-DU, but towards physical device directly connected to -22 TNE (compute node or O-Cloud gateway). IEEE 802.1X [41] authentication beyond the physical -23 device (compute node or O-Cloud gateway) directly connected to TNE is out-of-scope for this -24 document. - -25 Intermediate relay TNEs without Layer-2 or Layer-3 switching/routing functionality enabled are out -26 of scope for IEEE 802.1X-2020 [41] port-based network access control because there are no point- -27 to-point LAN segment links. Furthermore, in packet switched transport network architecture using -28 MPLS or SRv6 underlay, as described in this document (Sections 11 and 12), transport network -29 control plane protocols (e.g., IS-IS, OSPF, BGP, LDP, RSVP) have built-in authentication -30 mechanisms (Section 17.3.2) for authentication and authorization of the Open Fronthaul between -31 TNEs. - -32 - -![Diagram illustrating IEEE 802.1X scope in Open Fronthaul. It shows three scenarios (1, 2, 3) of network configurations connected to a TNE (Transport Network Element) which is part of the WG9 scope. Each scenario involves an IEEE 802.1X Supplicant (S) and an IEEE 802.1X Authenticator (A) connected via Open Fronthaul eCPRI (7.2x) links. The TNE is connected to an Authentication Server via RADIUS/Diameter based authentication. The legend defines the symbols: S for IEEE 802.1X Supplicant, A for IEEE 802.1X Authenticator, S-A for Port-based EAP TLS authentication, and a dashed double-headed arrow for RADIUS/Diameter based authentication.](cf03eff1218a8cc1be6b05de892162de_img.jpg) - -1 - -The diagram illustrates the IEEE 802.1X scope in Open Fronthaul across three scenarios: - -- (1) O-RU (S) connected to TNE (A) via Open Fronthaul eCPRI (7.2x). RRH connected to FHG (S) via non 7.2x LLS. FHG connected to TNE (A) via Open Fronthaul eCPRI (7.2x). O-RU connected to FHM (S) via Open Fronthaul eCPRI (7.2x). FHM connected to TNE (A) via Open Fronthaul eCPRI (7.2x). O-DU (S) connected to TNE (A) via Open Fronthaul eCPRI (7.2x). -- (2) vO-DU (S) connected to TNE (A) via Open Fronthaul eCPRI (7.2x). vO-DU connected to Compute (S) via non 7.2x LLS. Compute connected to vO-Cloud GW (S) via non 7.2x LLS. vO-Cloud GW connected to TNE (A) via Open Fronthaul eCPRI (7.2x). -- (3) O-DU connected to O-Cloud (S) via non 7.2x LLS. O-Cloud connected to O-Cloud GW (S) via non 7.2x LLS. O-Cloud GW connected to TNE (A) via Open Fronthaul eCPRI (7.2x). - -The TNE (Transport Network Element) is part of the WG9 scope and is connected to an Authentication Server via RADIUS/Diameter based authentication. The legend defines the symbols: - -- S: IEEE 802.1X Supplicant -- A: IEEE 802.1X Authenticator -- S-A: Port-based EAP TLS authentication -- Dashed double-headed arrow: RADIUS/Diameter based authentication - -Diagram illustrating IEEE 802.1X scope in Open Fronthaul. It shows three scenarios (1, 2, 3) of network configurations connected to a TNE (Transport Network Element) which is part of the WG9 scope. Each scenario involves an IEEE 802.1X Supplicant (S) and an IEEE 802.1X Authenticator (A) connected via Open Fronthaul eCPRI (7.2x) links. The TNE is connected to an Authentication Server via RADIUS/Diameter based authentication. The legend defines the symbols: S for IEEE 802.1X Supplicant, A for IEEE 802.1X Authenticator, S-A for Port-based EAP TLS authentication, and a dashed double-headed arrow for RADIUS/Diameter based authentication. - -Figure 17-1: IEEE 802.1X scope in Open Fronthaul (Example) - -At the high-level, the overall authentication process via EAP-TLS (RFC5216, [96]) can be divided into three phases: - -1. Limited authentication using manufacturer pre-installed certificate -2. Certificate enrollment into operator's Public Key Infrastructure (PKI) -3. Full authentication using operator installed certificate - -The details of this authentication process are described and standardized in O-RAN.WG11.Security-Requirements-Specifications [27], Section 5.2.5.5.2. All three phases SHALL be supported on the TNE deployed in Open Fronthaul. - -Note: IEEE 802.1X-2020 [41] support on TNEs deployed in other parts of the network (not Open Fronthaul) is optional. - -#### 17.4.1 Certificate time validation - -Operation of the EAP-TLS method requires the TNE verify the certificate chain presented by the authenticator PAE, including confirming the certificate's validity periods. TNEs using IEEE 802.1X port-based access control shall be able to verify the certificate validity periods during the EAP-TLS exchange, e.g., by employing Global Navigation Satellite System (GNSS), PTP, or NTP-based ToD (Time of the day) synchronization, or employing a persistent clock previously synchronized to GNSS, PTP or NTP. - -If the TNE cannot verify the certificates validity, e.g., because there is not available GNSS/PTP/NTP time source, and a persistent clock has failed or was never synchronized to - -![O-RAN Alliance logo](a54a85f03c26edd563f88dfc92ae279a_img.jpg) - -O-RAN Alliance logo - -1 GNSS/PTP/NTP, the EAP authentication procedure will fail. The behavior to handle such situation - 2 is not specified in this document but is up to the operator's policy. - -## 3 17.4.2 Certificate management for TNEs providing Open Fronthaul transport - -### 4 17.4.2.1 Trust anchor provisioning - -5 Before a TNE can establish a mutual EAP-TLS connection with a signaling peer, e.g., with an IEEE - 6 802.1X supplicant, a TNE needs to be able to trace the peer's certificate path to a valid trust anchor. - 7 To validate against a trust anchor, the TNE shall be able to be provisioned with one or more trust - 8 anchor certificates. The TNE shall ensure that all trust anchor certificates are stored in reset - 9 persistent memory and protected from external modification. - -10 - 11 The TNE shall be able to be provisioned with new trust anchors. The TNE shall be able to have an - 12 existing trust anchor replaced, e.g., because it has expired. The TNE should support ietf-truststore - 13 YANG model ([172]) to enable to recover the list of provisioned trust anchors and associated public - 14 keys. - -15 - 16 The present document defines the use of Certification Management Protocol version 2 (CMPv2, - 17 [80]) Initialization Response message to allow the discovered Certification Authority (CA) and - 18 Registration Authority (RA) server to provision a trust anchor. - -19 - 20 NOTE: The CA/RA Server identity is configured manually or by the DHCP server using - 21 techniques described in section 17.4.2.2. The Dynamic Host Configuration Protocol - 22 (DHCP) server is not considered by the TNE as a trusted source of security - 23 bootstrapping data. - -24 - 25 When shipped, a TNE only trusts information that is signed or encrypted using a certificate chain - 26 leading to a pre-loaded trust anchor. - -### 27 17.4.2.2 Operator-signed certificate enrolment - -28 A TNE shall support certificate enrolment using CMPv2 ([80]). Reachability (IP address, Fully - 29 Qualified Domain Name – FQDN) to the CA/RA servers can be configured on TNE during initial - 30 TNE provisioning. Alternatively, 3GPP TS 32.509 ([7]), clause 4.2.2, specifies how the TNE - 31 supporting certificate enrolment over IPv4 can be configured with the IP address or FQDN of one - 32 or more CA/RA servers using DHCP Option 43. - -33 - 34 The DHCP Options specified in 3GPP TS 32.509 ([7]), do not specify how to signal a CA/RA - 35 server identity using DHCP for IPv6 hosts (DHCPv6). Hence, TNE certificate enrolment using - 36 CMPv2 over IPv6 shall support the signaling of vendor specific options using DHCPv6 option 17. - 37 The format of the DHCPv6 option 17 follows the format of the DHCP for IPv4 hosts (DHCPv4) - 38 encoding as specified in clause 4.2.2 of 3GPP TS 32.509 ([7]), with the additional inclusion of an - 39 Enterprise Number prior to the Type-Length-Value (TLV) option data. The Internet Assigned - 40 Numbers Authority (IANA) allocated private enterprise number to be used with DHCPv6 option 17 - 41 shall be 53148 (as allocated by IANA to O-RAN Alliance). - -42 - 43 3GPP has since published 3GPP TS 28.316 ([3]), which now specifies how to signal a CA/RA - 44 server identity with DHCPv6 option 17 messages using the 3GPP registered IANA Enterprise - 45 Number (10415). The DHCP Options defined in [7] are a subset of those defined in [3]. An operator - 46 and vendor can agree to use the 3GPP registered IANA Enterprise Number in DHCPv6 messages - -![O-RAN Alliance logo](ee8a6b77d1ef86f5640e28868874cace_img.jpg) - -O-RAN Alliance logo - -1 that signal the CA/RA server information instead of the O-RAN registered IANA Enterprise - 2 Number. - -3 - 4 If a TNE provides Layer-3 (IP) transport connectivity between IEEE 802.1X supplicants, the TNE - 5 shall operate as the default gateway to the IEEE 802.1X supplicant to provide connectivity between - 6 the IEEE 802.1X supplicant and a remote CA/RA server, when the IEEE 802.1X supplicant is - 7 required to perform certificate enrolment using CMPv2, the TNE shall provide means for the IEEE - 8 802.1X supplicant to access the operator CA/RA for the IEEE 802.1X supplicant certificate - 9 enrolment at the IP address conveyed as described above. If the FQDN option is used instead, the - 10 TNE shall provide means for the IEEE 802.1X supplicant to access an operator DNS server in - 11 addition. Examples of providing such access by a TNE include: - -- 12 - 13 - An IP forwarding function within the TNE providing access to the operators PKI. -- 14 - A Network Address Translation (NAT) function within the TNE providing access to the operators PKI. -- 15 - A Registration Authority function accessible by the TNE (in the same domain), which is part of the - 16 operator PKI. - -17 A TNE shall report any discovered multi-vendor plug-and-play servers using the o-ran-dhcp YANG - 18 model (reference needed). - -#### 19 17.4.2.3 CMPv2 based certificate enrolment - -20 This section covers the use case where a TNE is configured with the identity of a CMPv2 capable - 21 CA/RA server that the operator uses for certificate enrolment. The TNE shall attempt to enroll in - 22 the operator-PKI and may be issued an operator-signed certificate. - -23 - 24 Clause 9 of 3GPP TS 33.310 ([8]) specifies the use of CMPv2 used by base stations to obtain an - 25 operator-signed certificate using a secured communication based on the vendor-signed certificate in - 26 the base station and a vendor root certificate pre-installed in the CA/RA server. While the approach - 27 has been defined for provisioning certificates on base stations for use in either IPSec or TLS, the - 28 same techniques defined for provisioning TLS certificates on base stations can be used for - 29 provisioning TLS certificates on TNEs. - -30 - 31 The handling of certificates, including certificate profiles, shall follow the rules defined in 3GPP TS - 32 33.310 ([8]) for TLS CA certificates. In addition: - -- 33 - 34 - when a TNE generates a certificate signing request it shall populate the Subject Distinguished Name field - 35 with a string that includes the TNE manufacturer's name, model and serial number. The exact Subject - 36 DN sub-field used is defined in the operator of the CA/RA server's certificate policy. - -37 NOTE 1: In future, an O-RAN defined certificate policy may be defined to normalize the sub- - 38 field definition across the O-RAN ecosystem. - -39 - 40 NOTE 2: There are various characters that may not be permissible in the Subject Distinguished - 41 Name Field, e.g., ":" (colon, hexadecimal character 0x34), "." (period, hexadecimal - 42 character 0x2E), "\_" (underscore, hexadecimal character 0x5F), "#" (hash, hexadecimal - 43 0x23), "£" (pound, hexadecimal 0xa3), "\*" (asterisk, hexadecimal 0x2a) or "" (double - 44 quote, hexadecimal 0x22). Manufacturers that include such characters in their name, - 45 model and/or serial number should ensure such characters are removed before including - 46 in the Subject Distinguished Name Field. - -- when transferring messages to the CA/RA server, the TNE shall use the "port number of the CA/RA server" and the "path to the CA/RA directory" as signalled using the DHCP options as specified in clause 4.2.2 of 3GPP TS 32.509 ([7]). If no DHCP based configuration is received by a TNE, the TNE shall use the default port 443 and default directory "/pkix/". -- The CA/RA server shall include the trust anchor for the operator issued certificate and the appropriate certificate chains in the initialization response message. -- The TNE shall store the operator issued certificate and corresponding certificate chain in reset persistent memory. - -When configured to operate with EAP-TLS, a TNE that has a valid certificate issued by an operator PKI shall use this certificate to establish a mutually authenticated EAP-TLS connection for IEEE 802.1X-2020 [41] authentication. - -#### 17.4.2.4 Operation with vendor-signed certificates - -All TNEs should be pre-provisioned at a factory with a unique device vendor-signed certificate and its entire certificate chain up to the root. If a TNE fails to enroll in an operator-PKI, as specified in section 17.4.2.2, a TNE configured to operate with TLS may use its vendor-signed certificate initially. The vendor's public trusted certificate and certificate management services should be accessible within the operator network to allow management of vendor-signed certificates. The extended use of unmanaged vendor-signed certificates, such as outside of enrolment, is not recommended. - -## 18 5G Slicing in a packet switched Xhaul network - -Network Slicing is end-to-end partitioning of the network resources and network functions so that selected applications/services/connections may run in isolation from each other for a specific business purpose. The overall slicing architecture is shown in Figure 18-1 and covers the orchestration infrastructure and at the physical layer can cover the radio access network, the mobile core, including data centers and virtualization aspects, and the X-haul transport network. - -![Figure 18-1: Overall 5G slicing architecture diagram. The diagram shows a hierarchical management structure. At the top is the Communications Service Management Function (CSMF), which connects to the Network Slice Management Function (NSMF). The NSMF is connected to three Slice Subnet Management Functions (SSMFs): (Access) SSMF, (Transport) SSMF, and (Core) SSMF. Each SSMF is associated with a stack of NSSTs (Network Slice Selection Assistance Information). Below the SSMFs are three Network Service Instances (NSIs): Access network (AN), Transport network (TN), and Mobile core (CN). Each NSI contains three slices (Slice 1, Slice 2, Slice 3) represented by colored boxes (green, red, orange). The AN, TN, and CN are interconnected by colored lines representing the slices. The entire NSI section is enclosed in a dashed box labeled 'Network Service Instances(NSI)'.](a34a521d4a9ba7071e87adf963f12fa7_img.jpg) - -Figure 18-1: Overall 5G slicing architecture diagram. The diagram shows a hierarchical management structure. At the top is the Communications Service Management Function (CSMF), which connects to the Network Slice Management Function (NSMF). The NSMF is connected to three Slice Subnet Management Functions (SSMFs): (Access) SSMF, (Transport) SSMF, and (Core) SSMF. Each SSMF is associated with a stack of NSSTs (Network Slice Selection Assistance Information). Below the SSMFs are three Network Service Instances (NSIs): Access network (AN), Transport network (TN), and Mobile core (CN). Each NSI contains three slices (Slice 1, Slice 2, Slice 3) represented by colored boxes (green, red, orange). The AN, TN, and CN are interconnected by colored lines representing the slices. The entire NSI section is enclosed in a dashed box labeled 'Network Service Instances(NSI)'. - -Figure 18-1: Overall 5G slicing architecture - -![O-RAN Alliance logo](88a5a5ef66b246fe6f55e8600f8b0764_img.jpg) - -O-RAN Alliance logo - -Although slicing is a key capability of 5G, there is debate as to how it exactly translates into the transport network, which mobile interfaces (Fronthaul, Midhaul, Backhaul, N6) need to be sliced, what form they will take, and the number of slices required at the transport layer. For the purposes of this document the Xhaul transport infrastructure needs the capability to support transport requirements of the: - -1. O-RAN and 3GPP control, management, and user plane interfaces. -2. Wireline consumer, enterprise, and wholesale services. - -This includes 5G transport slicing, which from a mobile perspective may include: - -1. Transport separation between Fronthaul, Midhaul, Backhaul interfaces. -2. Transport separation between Control, management, and user plane interfaces of each domain. -3. Flexible mapping of Network Slice Instances (NSIs) to physical or logical transport network instances. - -Figure 18-2 is an example of how three NSIs could be mapped to logical networks within an Xhaul transport network. In this example there is a: - -1. Common logical transport infrastructure supporting the Fronthaul and Midhaul management planes for all three NSIs -2. Common logical transport infrastructure supporting Fronthaul control and user planes for all three NSIs. -3. Common logical transport network supporting Midhaul user plane for all three NSIs. -4. Common logical transport network supporting 3GPP control plane (Midhaul and Backhaul) for all three NSIs. -5. Dedicated logical transport networks for backhaul and N6 networks for each NSI. - -![Figure 18-2: Overall 5G slicing architecture diagram. The diagram shows a 'Transport Network' cloud at the center. On the left, 'Cell Sites' containing 'O-RU' and 'O-DU' units are connected to a 'Common FH C/U plane' (red cloud). This plane connects to a 'Far Edge DC' containing an 'O-DU'. Above the transport network are two common clouds: 'Common O-RAN management and control' (orange) and 'Common 3GPP Control plane Network' (purple). A 'Common MH user' cloud (yellow) is also connected to the transport network. On the right, three Network Slice Instances (NSIs) are shown: 'BH Slice #1', 'N6 - slice #1'; 'BH slice #2', 'N6 - Slice #2'; and 'BH slice #3', 'N6 - slice #3'. Each NSI's backhaul (BH) and N6 slices connect to the transport network. Below the transport network, three vertical stacks represent the user plane for each NSI: the first contains 'vO-CU-IF', 'vO-CU-UF', and 'vO-CU-UP'; the second and third each contain three 'UPF' units. All three stacks connect to a 'Central DC' on the far right.](6e50e3275fbdccd63dc258477b94bef6_img.jpg) - -Figure 18-2: Overall 5G slicing architecture diagram. The diagram shows a 'Transport Network' cloud at the center. On the left, 'Cell Sites' containing 'O-RU' and 'O-DU' units are connected to a 'Common FH C/U plane' (red cloud). This plane connects to a 'Far Edge DC' containing an 'O-DU'. Above the transport network are two common clouds: 'Common O-RAN management and control' (orange) and 'Common 3GPP Control plane Network' (purple). A 'Common MH user' cloud (yellow) is also connected to the transport network. On the right, three Network Slice Instances (NSIs) are shown: 'BH Slice #1', 'N6 - slice #1'; 'BH slice #2', 'N6 - Slice #2'; and 'BH slice #3', 'N6 - slice #3'. Each NSI's backhaul (BH) and N6 slices connect to the transport network. Below the transport network, three vertical stacks represent the user plane for each NSI: the first contains 'vO-CU-IF', 'vO-CU-UF', and 'vO-CU-UP'; the second and third each contain three 'UPF' units. All three stacks connect to a 'Central DC' on the far right. - -Figure 18-2: Overall 5G slicing architecture - -The characteristics of a transport slice are defined in clause 5.2.3 of 3GPP Technical Report 22.891. Although not referenceable, further useful information can be found in various expired personal informational IETF drafts which provide thinking on the characteristics of a sliced transport network. Some of the key points are: - -![O-RAN Alliance logo](2d3cbcc7e78c2e571a58628a299e97c3_img.jpg) - -O-RAN Alliance logo - -- Management and lifecycle of the network - - Definition - - Creation / deletion - - Modification -- Per slice OAM -- Resource Reservation -- Slice isolation - - Performance - - Operational - - Security - - Reliability -- Abstraction - - Virtualization of network functions (where appropriate) - - Use of shared compute resources - -In the transport space, the informal terms, hard and soft slicing has emerged. This refers to the level of isolation between different slices. In both cases they need to support the functions outlined above but the way the slice is built and managed differs considerably. - -- Hard slicing: Transport resources are dedicated to a specific “Network Slice Instance” (NSI). In this case a resource is dedicated to a particular slice and not available to other slices. -- Soft slicing: The transport slice has the characteristics outlined above but a resource is shared and can be re-used by other slice instances. - -A packet switched infrastructure, as described in this document, has an extensive toolset, consisting of underlay forwarding solutions, Quality of Service (QoS) and VPNs that allows an operator to scalable partition the transport network to cater for both hard and soft slices use cases. Figure 18-3 outlines some of the packet switched features that can be flexibly combined to create transport slice with different level of resource sharing. - -| | Isolation | Topology | Resources | -|---------|--------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

Image: Diagram showing five stacked boxes labeled VPN1 to VPN5, representing traffic isolation.

|

Image: Diagram showing three stacked network planes (Slice A, Slice B, Slice C) over a physical topology, representing different topological subsets.

|

Image: Diagram showing four stacked horizontal bars labeled Slice 1 to Slice 4, representing resource allocation.

| -| PURPOSE |
  • ▪ Traffic isolation between slices
|
  • ▪ Subset of physical topology
  • ▪ Low Latency slice
  • ▪ High Capacity slice
  • ▪ Plane A, Plane B slices
|
  • ▪ Resources
  • ▪ Links
  • ▪ Bandwidth
  • ▪ Queues/buffers
| -| TOOLSET |
  • ▪ L3VPN
  • ▪ EVPN L2 Services
  • ▪ VLANs
|
  • ▪ Intra-domain slicing architectures
    • SR Flexible Algorithms
    • SR Traffic Engineering
    • RSVP Traffic Engineering
  • ▪ Inter-domain slicing architectures
    • Seamless / redistribution
    • Controller based
|
  • ▪ Bandwidth Management with Call Admission Control
  • ▪ Dedicated components
  • ▪ Per-link slicing
  • ▪ Hierarchical QoS
  • ▪ Hierarchical Policers
| - -Figure 18-3: Packet switched toolset for transport level slicing - -![O-RAN Alliance logo](997340cf22533b0b7cea41bdb3db664d_img.jpg) - -The logo for the O-RAN Alliance, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -1 When considering hard and soft slices it is important to bear in mind they should be thought of as a - 2 spectrum of capability, rather than one or the other. - 3 - -## 4 18.1 Packet-switched underlay network - -5 The packet-switched underlay network can use MPLS, SRv6 or a combination. - -### 6 18.1.1 Underlay transport plane - -7 The transport plane determines how traffic is sent over the packet-switched underlay infrastructure. - 8 Four approaches are outlined for constructing the underlay transport plane/planes for a 5G transport - 9 infrastructure. In each of the first three cases the level of resource sharing reduces, hence the slice - 10 solution becomes harder in nature but may introduce scalability and operational challenges. Fourth - 11 mapping approach is based on 5QI/DSCP, and scaling doesn't depend on the number of slices. - -### 12 18.1.2 Single transport plane for all slices - -13 The underlay network relies solely on the routing protocols (IGPs and EGPs) to calculate a single - 14 forwarding table based on shortest path routing. The routing protocol sees all links and there is a - 15 single forwarding table based on IGP and BGP metrics. All traffic takes the shortest path between - 16 two points within the network and utilises ECMP. - -17 In the context of slicing, all slices will see the same set of paths between end points within the - 18 network. It can be considered the softest slicing solution in terms of the underlay transport plane. - 19 However, although the infrastructure is shared between slices, it is highly scalable, widely - 20 implemented in 4G and critical enterprise environments, and is capable of delivering high quality - 21 SLAs. - -### 22 18.1.3 Transport plane per 5G service type - -23 Within the underlay network multiple transport planes are built to meet the specific forwarding - 24 behaviors associated with the different 5G services types. One or more customers can then use these - 25 transport planes. This is achieved using VPNs and traffic steering techniques. The transport planes - 26 can utilise different topologies and be optimized based on different criteria. For example, a URLLC - 27 service types could be optimised to use only the most reliable links in the network and select the - 28 best paths between endpoints based on link delay metrics. In contrast, the eMBB service types - 29 could be designed to use cheap, high bandwidth links, based on paths calculated with IGP metrics - 30 correlated with link capacity (high link capacity → low IGP metric). And, NB-IoT service types, - 31 which don't require neither low latency communication, nor high capacity, could use a 3rd transport - 32 plane with paths established based on TE metrics, favoring links for this type of services. This - 33 concept is outlined in Figure 18-4. - 34 - -![O-RAN Alliance logo](806d2632fa8b6a9bd79d816e1722de6b_img.jpg) - -O-RAN Alliance logo - -![Diagram showing the mapping of 5G service types (eMBB, NB-IoT, URLLC) to transport planes (X, Y, Z) via VPNs and PEs. The diagram includes tables for service prefixes and their associated colors, and a network topology showing O-DUs connected to PEs (PE1, PE2, PE3, PE4) which are then connected to O-CUs.](3b20eb477ef174b7adaad37703f5d611_img.jpg) - -Transport Plane is a group of paths (tunnels) with common optimization strategy (topology constraints, metric type, ...) - -Tunnel types: Flex-Algo, RSVP-TE, SR-TE, SRv6-TE, BGP-CT - -VRF Import based on RT - -Mapping based on Color - -Automatic mapping between service prefix and underlay transport plane based on Color Extended Community - -| Prefix: eMBB1 | Prefix: eMBB2 | Prefix: URLLC2 | -|---------------|---------------|----------------| -| VPN Label: V1 | VPN Label: V2 | VPN Label: V6 | -| PNH: PE1 | PNH: PE1 | PNH: PE1 | -| RT: VPN01 | RT: VPN02 | RT: VPN06 | -| Color: 1 | Color: 1 | Color: 3 | - -Diagram showing the mapping of 5G service types (eMBB, NB-IoT, URLLC) to transport planes (X, Y, Z) via VPNs and PEs. The diagram includes tables for service prefixes and their associated colors, and a network topology showing O-DUs connected to PEs (PE1, PE2, PE3, PE4) which are then connected to O-CUs. - -Figure 18-4: Transport Plane per 5G service type – midhaul example - -To implement such an approach, a mix of shortest path routing and traffic engineering solutions could be used. Traffic engineering options include flex-algo, SR-TE or traditional MPLS TE. As with any traffic engineering approach, consideration needs to be made of scale and state held within the network. Perhaps the simplest approach would be to use the default Flex-algorithm for eMBB and the mMTC services and a delay optimized flexible algorithm for the URLLC services. Backbone links and even nodes could be considered for inclusion or exclusion into the delay optimized flex-algorithm transport planes based on whether the algorithm is enabled on a TNE and TE affinities associated with the links. - -The mapping between services and transport planes can be simplified with the usage of Color Extended Community defined in RFC 5512 [100]. Each transport plane (each tunnel being part of specific transport plane) is associated with some color value. For example, latency optimized tunnels use color 1 (Transport Plane A), capacity optimized tunnels use color 2 (Transport Plane B), and remaining tunnels use color 3 (Transport Plane C). At the same time, service prefixes are advertised via BGP with appropriate Color Extended Community. URLLC service prefixes use community value 1, eMBB service prefixes community value 2, and NB-IoT service prefixes community 3. On the PE router receiving such service prefixes, selection of appropriate transport plane is automatic based on matching colors advertised via Color Extended Community with the service prefix and the color associated with the transport plane. - -#### 18.1.4 Transport plane per slice customer - -This is a variation on the previous scheme. In this case rather than a transport plane per 5G service type, a transport plane for individual customers is defined, as depicted in Figure 18-5. The same techniques outlined above would be used but very careful consideration needs to be given to scale and operational complexity of such an approach. In this case, scalability is a function of the number of customers using the network rather than the 5G service types. - -![Diagram showing the mapping of service prefixes (Cust-1, Cust-2, Cust-6) to transport planes (Plane A, Plane B, Plane C, Plane D, Plane E, Plane F) based on color. The diagram illustrates the flow from O-DU units through various VPNs (VPN01-VPN06) to different transport planes, which then connect to PE1 and PE2 units and finally to O-CU units. The mapping is based on the color associated with each VPN/Prefix.](1684f5f8c34bd0ef6e933664d88b9d86_img.jpg) - -Transport Plane is a group of paths (tunnels) with common optimization strategy (topology constraints, metric type, ...) - -Tunnel types: Flex-Algo, RSVP-TE, SR-TE, SRv6-TE, BGP-CT - -VRF Import based on RT - -Mapping based on Color - -| Prefix: Cust-1 | Prefix: Cust-2 | Prefix: Cust-6 | -|----------------|----------------|----------------| -| VPN Label: V1 | VPN Label: V2 | VPN Label: V6 | -| PNH: PE1 | PNH: PE1 | PNH: PE1 | -| RT: VPN01 | RT: VPN02 | RT: VPN06 | -| Color: 1 | Color: 2 | Color: 6 | - -Automatic mapping between service prefix and underlay transport plane based on Color Extended Community - -Diagram showing the mapping of service prefixes (Cust-1, Cust-2, Cust-6) to transport planes (Plane A, Plane B, Plane C, Plane D, Plane E, Plane F) based on color. The diagram illustrates the flow from O-DU units through various VPNs (VPN01-VPN06) to different transport planes, which then connect to PE1 and PE2 units and finally to O-CU units. The mapping is based on the color associated with each VPN/Prefix. - -Figure 18-5: Transport Plane per slice customer – midhaul example - -Mapping per customer and mapping per 5G service type might be used together to address scaling challenges. E.g., as the default approach mapping per 5G service type might be used, and only small number of selected premium customers might have mapping to individual transport planes. - -#### 18.1.5 Transport plane per 5QI group (5QI-aware mapping) - -5G slices might carry traffic belonging to multiple 5QI flows. Annex F: Transport network slicing solution for WG1 Slicing (informational) proposes an approach for mapping between 5QI and DSCP, and for grouping multiple 5QI/DSCP flows to limited number of 5QI/DSCP groups, where each group contains 5QI/DSCP flows (from multiple slices) with similar characteristics. This grouping is introduced to allow easy mapping of large number of 5QIs to limited set of transport resources, like for example queues in TNEs. 5QI/DSCP grouping allows as well for intelligent transport plane mapping, as outlined in Figure 18-6. - -![Diagram illustrating 5QI-aware mapping of traffic from O-DUs through VPNs to Transport Planes X, Y, and Z, and then to PE routers (PE1, PE2, PE3) connected to O-CUs. The mapping is based on DSCP values (A, B, C, D, E, F) which are grouped into three transport planes. PE routers perform automatic mapping based on DSCP or PCP values.](ecae674475cecdd0962200a5d1e2591e_img.jpg) - -1 - -Transport Plane is a group of paths (tunnels) with common optimization strategy (topology constraints, metric type, ...) - -Tunnel types: Flex-Algo, RSVP-TE, SR-TE, SRv6-TE, BGP-CT - -Automatic mapping between slice service packet and underlay transport plane based on DSCP or PCP value - -Diagram illustrating 5QI-aware mapping of traffic from O-DUs through VPNs to Transport Planes X, Y, and Z, and then to PE routers (PE1, PE2, PE3) connected to O-CUs. The mapping is based on DSCP values (A, B, C, D, E, F) which are grouped into three transport planes. PE routers perform automatic mapping based on DSCP or PCP values. - -2 -3 -4 -**Figure 18-6: Transport Plane per 5QI group (5QI-aware mapping) – midhaul example** - -5 -6 -7 -8 -In this example, three 5QI groups (group X: DCSP A; group Y: DSCP B, D; group Z: DSCP C, E, F) are uniquely mapped to three transport planes. With this approach, Color Extended Community is no longer used, as the mapping is based on DSCP (which corresponds to some 5QI). 5QI-aware mapping is most advanced mapping option between the service flows and underlay transport planes. - -## 9 18.2 Quality of Service - -10 -11 -12 -13 -14 -Quality of Service is an important component in slicing a transport infrastructure. As with the transport plane, different approaches could be taken depending on the level of isolation required between slices. In considering QoS it is necessary to look at the edge QoS solution and the core QoS solutions. For more info on QoS refer to section 14 and 25. - -### 15 18.2.1 Edge QoS - -16 -17 -18 -19 -20 -21 -22 -23 -24 -Edge interfaces to packet transport networks are generally the slowest and also where congestion and packet drop most often occurs. Regardless of the QoS structures implemented in the transport core, it is important with slicing to support edge conditioning of traffic on ingress and scheduling on egress to the transport network. This ensures that each slice gets its contracted overall bandwidth and class bandwidth as it enters and leaves the transport network. When slices are presented via VLANs from the mobile clients, the PE router needs a hierarchical QoS capability that can account for the overall contracted bandwidth at the VLAN level and also the overall contracted class bandwidth within the VLAN. - -### 25 18.2.2 Core QoS - -26 -27 -Within the core network different QoS strategies can be applied that determine the level of bandwidth and queue sharing that occurs between different slices. - -![O-RAN Alliance logo](f7565d053f61e82dae98ec4228d1fde1_img.jpg) - -O-RAN Alliance logo - -### 1 18.2.2.1 Shared queue architecture - -2 This approach follows the classic Diffserv QoS architecture. Slice traffic would be conditioned, and - 3 optionally marked or remarked as it enters the Diffserv domain, in this case the transport network. - 4 These markings determine the behaviour or Per Hop Behaviour (PHB) the traffic receives in the - 5 transport network. The number of PHBs in the core is determined by a number of factors; the - 6 number of PHBs that can be marked, the number of queues supported on the TNEs and operational - 7 complexity of the solution. Typically, in an MPLS network the traffic-class field is used to - 8 designate the PHB in the core. This is 3 bits, giving a maximum of 8 markings. In an IPv6 network - 9 the DSCP field is used to designate the PHB in the core. This is 6 bits giving a maximum of 64 - 10 markings. Even with more marking options, the number of PHBs in the core is generally kept small - 11 (<8) to simplify configuration, management and is generally done as a one-time set-up when a link - 12 is first installed. Core PHBs are enabled using a combination of queues, congestion management - 13 and scheduling techniques and are normally set-up in a work preserving fashion. That is, if one - 14 PHB is not fully utilised, the unused capacity can be used by traffic with other PHBs. - 15 Applying this to slicing. Each slice has an SLA based on overall and class bandwidth it receives. - 16 This is enforced on ingress at the PEs. In this QoS model, core queues are shared between slices and - 17 can be considered to be a soft form of slicing, but there is protection between slices through ingress - 18 edge conditioning of traffic. This architecture it is well tried, and tested, is simple and scales and - 19 able to support very tight SLAs. - 20 - -### 21 18.2.2.2 Dedicated queue architecture - -22 This approach uses the same Diffserv QoS architecture, except one or more PHBs is exclusively - 23 dedicated to a particular slice or slice type. An example could be a high priority PHB, which is - 24 dedicated exclusively to the URLLC slice. At the same time other slices can share the remaining - 25 PHBs. Given the small numbers of queues normally provisioned in the core (and available traffic - 26 classes in an MPLS environment), this type of solution needs to be used with extreme care, however - 27 it is a model used today successfully in production networks to support private line services which - 28 run in a dedicated high priority queue, while simultaneously supporting other services using a - 29 shared queue architecture. - 30 - -### 31 18.2.2.3 Dedicated links and queues per slice - -32 This QoS approach achieves hard slicing by either dedicating core links or parts of a core link to a - 33 specific slice. This can be achieved by one of the following approaches: - -- 34 • Using dedicated links per slice in the transport network. This could be done using full - 35 physical Ethernet interfaces or using Ethernet TDM technology, such as flexE, to create - 36 dedicated Ethernet channels for different slices. Within these links, class-based queuing - 37 would be used to support different traffic types associated with the slice. This approach - 38 offers no ability to share unused bandwidth between slices as the links are hard partitioned. -- 39 • Using hierarchically scheduled bandwidth on core links. In this case core links would be split - 40 using a shaper to govern the level of bandwidth available to each slice, with class-based - 41 queuing within the shaped bandwidth. This approach does offer the ability to share unused - 42 bandwidth between slices. - -43 - 44 In addition to dividing the core bandwidth up, mechanisms are required to guide slice traffic into - 45 the links or shaped bandwidth associated with each slice. Slice traffic could be guided into the - 46 appropriate links using a TE solution, such as flex-algo or SR-TE or alternatively the core routers - -![O-RAN Alliance logo](c85d9353a4a587e3d4c92fad86440b4f_img.jpg) - -O-RAN Alliance logo - -1 could be enhanced to schedule on a slice identifier within the packet. At this time there is discussion - 2 on this subject but as yet nothing solid. Like with the previous example, this could support a small - 3 number of slices but scaling up would be highly problematic with core provisioning, as well as edge - 4 provisioning required when a slice is defined, changed or deleted. It is also a large departure in the - 5 way QoS in core of packet networks has been managed in the past. - -## 6 18.35G Services and slices - -7 MP-BGP based L2 EVPN and L3 VPNs are used to create slice instances. VPNs are very scalable in - 8 terms of numbers and endpoints and allow different flexible connectivity models. This means slices - 9 could be based on 5G service, customer or a combination of the two. - -10 Each slice would have a VPN associated with it. By default, VPNs use the default IGP based - 11 forwarding tables to forward traffic. However, VPN traffic can be directed, either by configuration - 12 or using automated traffic steering techniques based on BGP “color extended community attribute” - 13 to use traffic engineered paths. In this way, a URLLC slice could be directed to use a delay - 14 optimised TE solution. Further control of the transport level connectivity within the VPN can be - 15 achieved using Route Target filtering. For example, “Route Target” filtering could be used to stop - 16 transport level connectivity between UPFs of different customers but allow O-CUs to communicate - 17 with any UPF. - -## 18 19 Energy efficiency in the context of Xhaul Packet 19 Switched Transport Network Equipments - -20 Energy efficiency is becoming relevant as sustainability goal in the operation of any kind of - 21 network, and in consequence, also for the purpose of Xhaul. - -22 - 23 The O-RAN Alliance has already setup activities in regards energy efficiency in WG5 and WG10, - 24 in relation to the management of the energy consumption at the radio level, enabled by e.g. the - 25 possibility of handling “sleep modes” of radio elements. This work is complementary to that by - 26 focusing on the transport side, specifically on which relates to packet switches solutions, as part of - 27 the scope of WG9. - -28 - 29 When dealing with Transport Network Equipments (TNEs), different approaches can be considered: - -- 30 - 31 • Actions taken at architectural level -- 32 • Actions taken at transport network (TN) level -- 33 • Actions taken at Transport Network Equipment (TNE) level - -34 - 35 The following sections elaborate on each of those approaches. - -### 36 37 19.1 Architecture level - -38 Here the purpose is the identification of actions that can positively influence the consumption of - 39 energy of the Xhaul segment at architectural level. This means the identification of architectural - 40 propositions resulting more efficient from an energy consumption perspective. This is much related - 41 to the design of the overall Xhaul solution by leveraging on architectural approaches in the direction - 42 of reducing the number of elements present in the network. Actions that could lay on this set are for - 43 instance: - -![O-RAN Alliance logo](51b44891ed19b748b56f3f543816631d_img.jpg) - -O-RAN Alliance logo - -- Topological optimizations by concentrating the number of TNEs aggregating O-RU's, O-DU's and O-CU's, while keeping the necessary redundancy levels to satisfy service SLAs. -- On scenarios requiring both packet-switched TNEs and an underlay optical network, schemes favouring the reduction of elements such as IPoDWDM solutions (i.e., the support of coloured interfaces on routers to avoid transponders). -- When feasible, the support of coloured interfaces directly on O-RU's, O-DU's and O-CU's. - -Any of these actions require an initial planning or a migration process. There could be structural dependencies on the suitability of these approaches based on the architecture design of the operators in their actual aggregation networks. - -## 19.2 Transport Network (TN) level - -Here the purpose is to improve the energy consumption of a network by implementing mechanisms that can dynamically optimize such consumption according to network status and conditions. Some events need to be identified as triggers for such optimization, that could require of smart management and control capabilities to make the network adapt to the observed circumstances, while reducing energy. Actions that could lay on this set are for instance: - -- Concentration of traffic flows in some links during low-activity periods, then freeing up some of the links for reducing the consumption on the corresponding TNEs. This could be done by the transport network in an isolated manner, or as part of a combined radio-transport optimization scenario. Note that additional capabilities are needed at device level for taking advantage of the links becoming empty as consequence of the traffic consolidation. -- Exposure of energy per path or topology based on the consumption of the participating individual devices, so that upper management systems can build an overall view of the energy consumption map for taking decisions (e.g., function placement, traffic consolidation as before, etc). - -These actions leverage on the capability of the management system to collect the necessary information, decide on top of the collected data, and enforce control actions on the network all in an automated manner, ensuring prompting reaction to observed and even predicted network status. - -## 19.3 Transport Network Equipment (TNE) level - -Here the objective is to leverage on intrinsic capabilities of the TNEs for reducing its individual energy consumption under conditions that can be triggered either internally or externally (i.e., from the management systems referred before). Actions that could lay on this set are for instance: - -- Presence of native capabilities for supporting “sleep modes” of operation, that is, reducing the consumption during periods of time according to e.g. traffic patterns. -- Possibility of switching off TNE parts, especially for modular architectures, in situations where those parts do not participate of the communications. This could be simply because there is no active participation, or because the consolidation of network traffic as described in 19.2. - -![O-RAN Alliance logo](48b8c4214eaf2c253f097bf484c605f6_img.jpg) - -O-RAN Alliance logo - -1 -2 These actions leverage on the capabilities of each device, so are dependent of the particular -3 implementations for equipment vendors. There is also a great dependency on the capabilities of the -4 installed base, so brownfield scenarios can be no such efficient as new deployments. -5 - -### 6 19.3.1 TNE hardware design - -7 -8 Based on the hardware structure, TNEs can be grouped into two main categories -9 - -- 10 ■ fixed systems -- 11 ■ modular chassis - -12 -13 Fixed systems (Figure 19-1) are typically 1 RU or 2 RU devices, which do not have replacable -14 network modules. Modular chassis (Figure 19-2), on the other hand, are typically bigger devices, -15 with flexible hardware options (line cards, modules). This allows assembling the TNE with -16 interfaces specifically required for the particular deployment. Fixed systems, while less flexible, -17 when it comes to port type variations, due to their simpler hardware structure, are typically more -18 power efficient compared to modular chassis. -19 - -![High-level architecture for fixed-systems diagram](6541fef32fd472072600f905d8b11009_img.jpg) - -The diagram illustrates the high-level architecture for fixed-systems. A central 'Chassis' block contains several interconnected components: - -- Four 'PHY' blocks, each connected to an external interface on the left. -- Three 'PFE' (Packet Forwarding Engine) blocks, each connected to a 'PHY' block. -- A central 'Fabric' block connected to all three 'PFE' blocks. -- A 'CPU' and 'DDR' memory block connected to the 'Fabric'. -- A 'Misc circuits FPGA' block connected to the 'Fabric'. - -External interfaces and factors on the left include: - -- 'Optic type, Conversion efficiency, Traffic load, PoE' connected to the top PHY. -- 'Features' connected to the second PHY. -- 'Port configuration, Features, Traffic Load, PFE state' connected to the third PHY. - -On the right, the architecture includes: - -- A 'Load' block at the top right. -- Four 'Fans' represented by orange icons, with a callout 'Optics, PHY, PFE and Fabric heat dissipation'. -- Two 'Power Supplies' represented by power symbol icons, with a callout 'Variable efficiency, based on power supply type'. -- A 'Features' block at the bottom right. -- A bottom callout box stating 'Temperature and Elevation influence all system components'. - -High-level architecture for fixed-systems diagram - -20 -21 **Figure 19-1: High-level architecture for fixed-systems** -22 - -![O-RAN Alliance logo](1abc95ab6792c81f3488f3b3188127e3_img.jpg) - -O-RAN Alliance logo - -![Figure 19-2: High-level architecture for modular chassis. The diagram shows a central RE (Radio Equipment) unit connected to multiple LC (Line Card) units via a FIB (Fabric Interconnect). The RE unit contains 'Misc circuits', a 'CPU', and 'DDR'. The LC units contain 'PHY', 'PFE', 'LC', 'CPU', and 'DDR'. The FIB units contain 'PHY' and 'Fabric ASIC'. A 'Load' is connected to the RE unit. A 'Fans' unit is shown on the right, with callouts for 'Optics, PHY, PFE and Fabric heat dissipation', 'Traffic load PFE state', and 'Variable efficiency, based on power supply type'. A 'PSM' (Power Supply Module) is also shown. A box at the bottom indicates 'Temperature and Elevation influence all system components'. Various callouts on the left list features like 'Optic type', 'Conversion efficiency', 'Traffic load', 'PoE', and 'Port configuration'.](00a0b3a0485d8e735df9cb73dbdf36d6_img.jpg) - -Figure 19-2: High-level architecture for modular chassis. The diagram shows a central RE (Radio Equipment) unit connected to multiple LC (Line Card) units via a FIB (Fabric Interconnect). The RE unit contains 'Misc circuits', a 'CPU', and 'DDR'. The LC units contain 'PHY', 'PFE', 'LC', 'CPU', and 'DDR'. The FIB units contain 'PHY' and 'Fabric ASIC'. A 'Load' is connected to the RE unit. A 'Fans' unit is shown on the right, with callouts for 'Optics, PHY, PFE and Fabric heat dissipation', 'Traffic load PFE state', and 'Variable efficiency, based on power supply type'. A 'PSM' (Power Supply Module) is also shown. A box at the bottom indicates 'Temperature and Elevation influence all system components'. Various callouts on the left list features like 'Optic type', 'Conversion efficiency', 'Traffic load', 'PoE', and 'Port configuration'. - -Figure 19-2: High-level architecture for modular chassis - -In both cases, fixed systems and modular chassis, components consuming energy are: - -- Pluggable optical modules inserted into the system. Responsible for electric $\Leftrightarrow$ optic conversion of the signal. Energy consumption of pluggable optical modules can greatly vary, depending on the module type. For example, 800 Gbps optical module consumes significantly more energy than 1 Gbps optical module. Similarly, long range or extended range optical module consumes significantly more energy than short range optical module. Additionally, energy consumption might depend on the traffic load. Some optical modules, the so called Power over Ethernet (PoE) optical modules, can also provide power to the attached end-user equipment (e.g. small in-house O-RU), which considerably increases the energy drawn by the optical module. -- Physical Layer (PHY). Dedicated chipset responsible for providing an electrical, mechanical, and procedural interface to the transmission medium. Energy consumption might depend on the features supported by PHY. -- Packet Forwarding Engine (PFE). Called as well Network Processing Unit (NPU). It is a dedicated chipset (or group of chipsets) responsible for TN data plane, switching frames or routing packets from one port to another port of the device. PFE/NPU energy consumption increases with increased traffic volume (for example, 800 Gbps PFE/NPU, consumes significantly more energy than 1 Gbps PFE/NPU), as well as with features supported and enabled on the port (for example, enabling MACsec or IPsec encryption might increase the energy consumption). -- Central Processing Unit (CPU) and Double Data Rate Synchronous Dynamic Random-Access Memory (DDR-RAM). In TNEs, CPUs together DDR-RAM, are responsible for handling transport network control plane, processing messages exchanged by various transport network protocols (IGP, BGP, LDP, ...). Control plane load, for example sizes of the routing and forwarding tables that must be maintained, number of IGP/BGP peers, inbound/outbound route policy complexity, etc. have effect on energy consumption. Additionally, modular chassis design relies on distributed control plane, with additional CPUs and DDR-RAMs in the line cards (LCs). - -![O-RAN Alliance logo](3c6e58a263aca26400c2f3a883bffbe2_img.jpg) - -O-RAN Alliance logo - -- Fabric. Dedicated chipset(s) to provide internal connectivity between PFEs/NPUs in multi PFE/NPU systems. In modular systems the fabric chipsets can be distributed across multiple fabric interface boards (FIBs). Energy consumption depends mainly on the traffic load. -- Miscellaneous chipsets. Some additional functions (for example, PTP handling, IPsec or MACsec encryption) might be implemented via dedicated Application-Specific Integrated Circuits (ASICs) or Field Programmable Gateway Arrays (FPGAs). These circuits consume energy to fulfill their functions. -- Fans. Fans are used to improve heat dissipation from the device. Fans energy consumption increases with the temperature. Also, some fixed systems are constructed as fanless devices, with heat dissipation realized via other means (like extensive use of dedicated heatsinks, or reusing itself the metal shelf of the device as a heatsinks). Fanless device design might be applicable to smaller TNEs only, like for example small cell site routers. -- Power Supply Unit (PSU). Energy consumed by PSU is related to the efficiency of PSU. PSU with efficiency 90% consumes less energy (10% from total energy drawn) than PSU with efficiency 85% (15% from total energy drawn). - -In modular chassis, the components are placed in different field replaceable modules, for example: - -- Routing Engine (RE). Hosts main CPU and main DDR-RAM -- Line Card (LC). Hosts optical modules, PHY, PFE and LC dedicated CPU + DDR-RAM. -- Fabric Interface Board (FIB). Hosts Fabric ASICs and PHY, to interconnect PFEs spread across multiple LCs -- Fan trays -- Power Supply Module (PSM) - -Figure 19-3 and Figure 19-4 provides an example of energy consumption distribution across various components for both fixed systems and modular chassis. Components that typically consumes most energy are PFEs, or FPCs hosting PFEs. Other significant energy consumers are optics, fabric, and – for modular chassis – fans. Therefore, it is most important to energy optimize these components of a TNE. - -![Figure 19-3: Example of energy consumption distribution – fixed system. A 3D stacked bar chart showing energy consumption percentages for various components. The total energy is 100%. The components and their percentages are: Optics max (26%), PSU (7%), MISC (7%), FAN (2%), CPU (2%), PFE (41%), PHY (4%), and Fabric (11%).](9c01fc6fde0eb030a38b32f202079c17_img.jpg) - -| Component | Percentage | -|------------|------------| -| Optics max | 26 % | -| PSU | 7 % | -| MISC | 7 % | -| FAN | 2 % | -| CPU | 2 % | -| PFE | 41 % | -| PHY | 4 % | -| Fabric | 11 % | - -Figure 19-3: Example of energy consumption distribution – fixed system. A 3D stacked bar chart showing energy consumption percentages for various components. The total energy is 100%. The components and their percentages are: Optics max (26%), PSU (7%), MISC (7%), FAN (2%), CPU (2%), PFE (41%), PHY (4%), and Fabric (11%). - -Figure 19-3: Example of energy consumption distribution – fixed system - -![O-RAN Alliance logo](b4478614140064dedc2161238ce2f2a5_img.jpg) - -O-RAN Alliance logo - -![Figure 19-4: Example of energy consumption distribution – modular chassis. Two stacked bar charts show energy distribution for 25C / 30% IMIX and 40C / Line Rate IMIX scenarios. The legend indicates: Optics max (green), FANs (red), RE (yellow), LC (grey), and Fabric (blue).](19e8a93bade890b206ffafe0de45ae73_img.jpg) - -| Scenario | Fabric (%) | LC (%) | RE (%) | FANs (%) | Optics max (%) | -|----------------------|------------|--------|--------|----------|----------------| -| 25C / 30% IMIX | 19 | 51 | 1 | 7 | 22 | -| 40C / Line Rate IMIX | 18 | 49 | 1 | 14 | 18 | - -Figure 19-4: Example of energy consumption distribution – modular chassis. Two stacked bar charts show energy distribution for 25C / 30% IMIX and 40C / Line Rate IMIX scenarios. The legend indicates: Optics max (green), FANs (red), RE (yellow), LC (grey), and Fabric (blue). - -Figure 19-4: Example of energy consumption distribution – modular chassis - -### 19.3.2 SerDes energy optimization - -SerDes is a functional block (single chipset or group of chipsets) that Serializes and Deserializes digital data used between electrical side of optics inserted in the port socket and a PFE. In some TNE designs PHY might be placed between port and PFE to aggregate multiple lower speed SerDes lines to higher speed SerDes line (Figure 19-5). - -![Figure 19-5: SerDes energy optimization. Two diagrams show SerDes energy optimization. The left diagram (PFE0) shows four ports (Port0, Port1, Port2, Port3) connected to a PFE. Port0 is empty, Port1 has a 400GE module, Port2 has a 100GE module, and Port3 is unused. SerDes ① is shutdown for Port0, and SerDes ② is shutdown for Port3. The right diagram (PFE1) shows four ports (Port4, Port5, Port6, Port7) connected to a PHY, which is connected to a PFE. Port4 is empty, Port5 has a 100GE module, Port6 has a 100GE module, and Port7 is unused. SerDes ① is shutdown for Port4, SerDes ② is shutdown for Port7, and SerDes ③ is shutdown for Port4 and Port7.](b320ccb4d6f993cc67c7b5b0b85cfacc_img.jpg) - -Figure 19-5: SerDes energy optimization. Two diagrams show SerDes energy optimization. The left diagram (PFE0) shows four ports (Port0, Port1, Port2, Port3) connected to a PFE. Port0 is empty, Port1 has a 400GE module, Port2 has a 100GE module, and Port3 is unused. SerDes ① is shutdown for Port0, and SerDes ② is shutdown for Port3. The right diagram (PFE1) shows four ports (Port4, Port5, Port6, Port7) connected to a PHY, which is connected to a PFE. Port4 is empty, Port5 has a 100GE module, Port6 has a 100GE module, and Port7 is unused. SerDes ① is shutdown for Port4, SerDes ② is shutdown for Port7, and SerDes ③ is shutdown for Port4 and Port7. - -Figure 19-5: SerDes energy optimization - -To optimize energy usage TNE should support following features: - -**[D55]:** TNE SHOULD automatically shut down SerDes associated with empty port (optical cage not populated with any pluggable optical module). This process SHOULD not impact neighboring ports → (1) - -**[D56]:** TNE SHOULD automatically restart SerDes associated with port to which a pluggable optical module has been inserted. This process SHOULD not impact neighboring ports → (1) - -**[D57]:** TNE SHOULD have capability to administratively declare a port as “unused”. SerDes associated with “unused” port (regardless, if populated with pluggable optical module or not) - -![O-RAN Alliance logo](28339846e409f75f9604bbe53984b4c7_img.jpg) - -O-RAN Alliance logo - -1 SHOULD be automatically shut down. Further, power to pluggable optical module inserted - 2 into “unused” port SHOULD be switched off, which also results in TX laser off. This - 3 process SHOULD not impact neighboring ports → (2) - -4 - 5 **[D58]:** TNE SHOULD have capability to administratively clear “unused” port state. If port with - 6 cleared “unused” state is populated with optical module, SerDes associated with such port - 7 SHOULD be automatically restarted and power to pluggable optical module inserted into - 8 such port SHOULD be enabled, which also results in TX laser on. This process SHOULD - 9 not impact neighboring ports → (2) - -10 - 11 **[D59]:** Higher speed SerDes aggregated by PHY, where all contributing lower speed SerDes are - 12 shutdown SHOULD be shut down as well. If at least one contributing lower speed SerDes - 13 restarts, higher speed aggregated SerDes SHOULD restart as well → (3) - -### 15 19.3.3 PHY energy optimization - -16 After SerDes, next component in forwarding path is PHY. PHY should be automatically shut down, - 17 when all connected SerDes lines are shut down (Figure 19-6). - -![Figure 19-6: PHY energy optimization diagram. The diagram shows a stack of components: PFE2 at the top, PG4 below it, and a PHY block below PG4. The PHY block is connected to four ports: Port4, Port5, Port6, and Port7. Port4, Port5, and Port6 are labeled 'Empty'. Port7 is labeled 'unused' and has a 100GE optical module inserted. To the right of the PHY block, there are three callouts: 'PFE SerDes Shutdown' pointing to the connection between PFE2 and PG4, 'PHY in "shutdown" mode' pointing to the PHY block, and 'WAN SerDes Shutdown' pointing to the connection between the PHY block and Port7.](cef981f48160da6ca248560bbf31eb7f_img.jpg) - -18 - -Figure 19-6: PHY energy optimization diagram. The diagram shows a stack of components: PFE2 at the top, PG4 below it, and a PHY block below PG4. The PHY block is connected to four ports: Port4, Port5, Port6, and Port7. Port4, Port5, and Port6 are labeled 'Empty'. Port7 is labeled 'unused' and has a 100GE optical module inserted. To the right of the PHY block, there are three callouts: 'PFE SerDes Shutdown' pointing to the connection between PFE2 and PG4, 'PHY in "shutdown" mode' pointing to the PHY block, and 'WAN SerDes Shutdown' pointing to the connection between the PHY block and Port7. - -19 - 20 **Figure 19-6: PHY energy optimization** - -21 - 22 **[D60]:** PHY with all connected SerDes in shutdown state SHOULD automatically shut down. When - 23 some of connected SerDes restarts (for example, due to pluggable optical module insertion - 24 into a “used” port cage, or due to administrative change of port state from “unused” to - 25 “used” for port with pluggable optical module already inserted) PHY SHOULD - 26 automatically restart. This process SHOULD not impact neighboring ports. - -### 28 19.3.4 PFE energy optimization - -29 As visible in Figure 19-3 and Figure 19-4 the major energy consumer in a TNE is the packet - 30 forwarding engine (PFE). - -31 - 32 PFE energy can be optimized via different approaches: - -- Flexible, fully programmable versus fixed pipeline PFE chipsets - -PFE chipsets can be divided into two main categories: flexible, fully programmable (1), and fixed pipeline, with limited programmability (2). Fixed pipeline chipsets consume less energy (Figure 19-7), as their design is simpler – they are designed to perform pre-determined functions (for example, to do the MPLS switching) with limited flexibility to program other functions (for example, perform SRv6 encapsulation/decapsulation, if the chipset was not designed from day one to perform this function). Therefore, to support particular throughput, they require less transistors comparing to flexible, fully programmable chipsets. This results in lower energy consumption. However, the tradeoff is feature flexibility offered by flexible, fully programmable PFE chipsets. - -![Figure 19-7: PFE chipset evolution. Two bar charts comparing energy consumption (Watts/Gbps) for flexible (fully programmable) and fixed pipeline chipsets across different generations and process nodes.](55448600b72a05f749215a83f8d2aef7_img.jpg) - -The figure consists of two bar charts. The left chart shows the energy consumption for flexible (fully programmable) chipsets, and the right chart shows it for fixed pipeline chipsets. Both charts plot Watts/Gbps on the y-axis against different generations and process nodes on the x-axis. - -| Architecture | Generation | Process Node | Year | Watts/Gbps (approx.) | -|-------------------------------|---------------------|--------------|------|----------------------| -| Flexible (fully programmable) | 1 st Gen | 65nm | 2009 | 2.25 | -| | 2 nd Gen | 65/40nm | 2012 | 1.8 | -| | 3 rd Gen | 40nm | 2014 | 1.6 | -| | 4 th Gen | 28nm | 2016 | 0.75 | -| | 5 th Gen | 16nm | 2019 | 0.4 | -| | 6 th Gen | 7nm | 2022 | 0.1 | -| Fixed pipeline | 1 st Gen | 40nm | 2012 | 0.9 | -| | 2 nd Gen | 28nm | 2016 | 0.3 | -| | 3 rd Gen | 16nm | 2019 | 0.2 | -| | 4 th Gen | 14nm | 2020 | 0.1 | -| | 5 th Gen | 7nm | 2022 | 0.05 | - -Figure 19-7: PFE chipset evolution. Two bar charts comparing energy consumption (Watts/Gbps) for flexible (fully programmable) and fixed pipeline chipsets across different generations and process nodes. - -Figure 19-7: PFE chipset evolution - -**[D61]:** To optimize PFE energy consumption, it is recommended TNE is built using fixed pipeline PFE chipsets. - -- PFE chipset generations - -Newer generation of chipsets, produced with 16 nm, or 7 nm (and emerging 5 nm) technologies consume significantly less energy (Figure 19-7) compared to older generation chipsets (28nm – 65nm). - -**[D62]:** To optimize PFE energy consumption, it is recommended TNE is build using new generation (<16 nm) PFE chipsets. - -- Traffic Load - -Traffic load might impact TNE energy consumption by about 10%-20% (TNE with minimal traffic load, versus TNE with maximal traffic load). Thus, minimizing traffic load might bring some energy savings. Some exemplary techniques to minimize traffic load are: - -- Use efficient transport encapsulation with small overhead (for example, MPLS overhead is typically smaller than SRv6 overhead) - -![O-RAN Alliance logo](26e477c1000006055ae0f5cad72cb057_img.jpg) - -O-RAN Alliance logo - -- Compress data before transmission, where possible and applicable (for example, photos and videos might be resized and compressed by the application server, before they are sent to the user equipment). However, this might increase energy consumption by servers hosting applications. -- Cache frequently used data close to end-users (for example, web cache) -- Use optimized multicast replication for multicast streams (for example, IPTV distribution via optimized multicast tree instead of ingress replication) -- PFE power off - -Both, administrative and automatic PFE power off bring energy savings. - -**[D63]:** TNE SHOULD have capability to administratively switch off the power of a PFE (Figure 19-8), which also automatically switches off the power of associated PHY, SerDes and pluggable optical modules. This process SHOULD not impact other PFEs. - -![Diagram illustrating PFE administrative power off. A central PFE block is connected to multiple PHY blocks, which are in turn connected to LC (Line Card) blocks. The top PFE block is labeled 'PFE admin power off' and has dashed lines connecting it to the LC blocks. The bottom PFE block is labeled 'PFE' and has solid lines connecting it to the LC blocks. To the right of the PFE blocks, there are two boxes labeled 'LC CPU' and 'DDR'.](88842d98d695fe6a281f8af82f9ac951_img.jpg) - -Diagram illustrating PFE administrative power off. A central PFE block is connected to multiple PHY blocks, which are in turn connected to LC (Line Card) blocks. The top PFE block is labeled 'PFE admin power off' and has dashed lines connecting it to the LC blocks. The bottom PFE block is labeled 'PFE' and has solid lines connecting it to the LC blocks. To the right of the PFE blocks, there are two boxes labeled 'LC CPU' and 'DDR'. - -**Figure 19-8: PFE administrative power off** - -**[D64]:** TNE SHOULD automatically switch off the power of a PFE, if all associates SerDes are in shutdown state (**Error! Reference source not found.**). When some of connected SerDes restarts (for example, due to pluggable optical module insertion into a “used” port cage, or due to administrative change of port state from “unused” to “used” for port with pluggable optical module already inserted) PFE SHOULD automatically restart. This process SHOULD not impact other PFEs. - -![O-RAN Alliance logo](885eef49ebd0d6c58ca2ac79ca9f1f5e_img.jpg) - -O-RAN Alliance logo - -![Diagram illustrating PFE automatic power off. It shows four PFEs (PFE0, PFE1, PFE2, PFE3) connected to a common switching fabric. Each PFE has multiple ports (Port0, Port1, ..., Port3). PFE0 has Port0 unused, Port1 active, and Port3 active. PFE1 has Port0 unused, Port1 active, and Port3 active, with a label 'PFE1 automatic power off' above it. PFE2 has Port0 active, Port1 unused, and Port3 active. PFE3 has Port0 unused, Port1 active, and Port3 active, with a label 'PFE3 automatic power off' above it. The diagram shows that PFEs can be automatically powered off when all their ports are unused.](60f844d947ea0bccdd9f64d81d5f8d26_img.jpg) - -Diagram illustrating PFE automatic power off. It shows four PFEs (PFE0, PFE1, PFE2, PFE3) connected to a common switching fabric. Each PFE has multiple ports (Port0, Port1, ..., Port3). PFE0 has Port0 unused, Port1 active, and Port3 active. PFE1 has Port0 unused, Port1 active, and Port3 active, with a label 'PFE1 automatic power off' above it. PFE2 has Port0 active, Port1 unused, and Port3 active. PFE3 has Port0 unused, Port1 active, and Port3 active, with a label 'PFE3 automatic power off' above it. The diagram shows that PFEs can be automatically powered off when all their ports are unused. - -Figure 19-9: PFE automatic power off - -### 19.3.5 Line card energy optimization - -Even when all PFEs are switched off (either automatically, or by administrative action) line card still consumes some energy. This energy is consumed by ASICs not associated with any particular PFE, like for example line card CPU. - -**[D65]:** TNE SHOULD have capability to administratively switch off the power of a line card, which also automatically switches off the power of associated PFE, PHY, SerDes and pluggable optical modules. This process SHOULD not impact other line cards. - -**[D66]:** TNE SHOULD automatically switch off the power of a line card, if all associated PFEs are in shutdown state. When some of connected PFEs restarts (for example, due to pluggable optical module insertion into a “used” port cage, or due to administrative change of port state from “unused” to “used” for port with pluggable optical module already inserted) line card SHOULD automatically restart. This process SHOULD not impact other line cards. - -### 19.3.6 Switching fabric energy optimization - -Switching fabric complex contains fabric ASICs, and SerDes complexes interconnecting fabric ASICs with PFEs (Figure 19-2). Therefore, in fabric complex, energy could be saved by switching off fabric ASICs or fabric SerDes complexes. - -There are couple of possible options for switch fabric design, when it comes to fabric redundancy in modular chassis. One of the common switching fabric redundancy designs is N+1 redundancy, where ‘N’ fabric interface boards provide capacity sufficient to interconnect all PFEs, and there is +1 fabric interface board as spare. For example, if the node has 8 PFEs, each PFE with 500 Gbps, the required switching fabric capacity is 4 Tbps. If the capacity of single fabric ASICs is 500 Gbps, and single fabric interface board hosts two fabric ASIC (1 Tbps per FIB), equipping the node with 5 fabric interface boards (5 Tbps in total) would provide N+1 switching fabric redundancy. - -In case of single fabric interface board failure, the switching fabric is still able to provide full required capacity of 4 Tbps. However, when two fabric interface boards fail, the maximum fabric capacity is reduced to 3 Tbps only. In order to provide protection for two fabric interface boards failures, N+2 (two “spare” fabric interface boards) redundancy mode would be required. - -![O-RAN Alliance logo](20ee25255c8ef2c61cdc2e9bba26988e_img.jpg) - -O-RAN Alliance logo - -[D67]: TNE SHOULD automatically shut down SerDes between fabric and PFE, if corresponding LC slot is empty (line card not inserted), or LC/PFE is powered off (Figure 19-10). This process SHOULD not impact other LCs or PFEs. - -![Figure 19-10: Fabric SerDes energy optimization diagram. It shows a line card (LC-0) with PHY and PFE connected to a Fabric ASIC. Another line card (LC-1) is shown with 'PFE Power off' and 'Slot 2 Empty' and 'Slot 3 Empty' labels. Green arrows point to the SerDes links between the PFEs and the Fabric ASICs, indicating energy optimization when slots are empty or powered off.](137bcfed81ada68ca5162ca5afed35c7_img.jpg) - -Figure 19-10: Fabric SerDes energy optimization diagram. It shows a line card (LC-0) with PHY and PFE connected to a Fabric ASIC. Another line card (LC-1) is shown with 'PFE Power off' and 'Slot 2 Empty' and 'Slot 3 Empty' labels. Green arrows point to the SerDes links between the PFEs and the Fabric ASICs, indicating energy optimization when slots are empty or powered off. - -Figure 19-10: Fabric SerDes energy optimization - -Often the TNE doesn’t operate at its full possible capacity. Some line cards or PFEs could be switched off. Some ports might be set to unused state, or not all ports might be populated with pluggable optical module. Therefore, very often the full switching fabric capacity is not required. In such situation, to maintain N+1 switching fabric redundancy, it is sufficient to take into consideration capacity requirements for PFE with highest capacity requirement (Figure 19-11). - -![Figure 19-11: Fabric interface board energy optimization diagram. It shows a central Fabric ASIC connected to multiple line cards (LC-0, LC-1, LC-2, LC-3). Each line card has PFEs with different capacity requirements (e.g., Max 100 Gbps, Max 200 Gbps, Max 300 Gbps). The diagram highlights 'TOP PFE: 300G' for LC-0 and LC-2. It also shows states like 'Port unused', 'switched off', 'stand-by', and 'active'. Connections to multiple FIBs (FIB-0 to FIB-4) are indicated.](51501a01b2c29ac95e126882508f8831_img.jpg) - -Figure 19-11: Fabric interface board energy optimization diagram. It shows a central Fabric ASIC connected to multiple line cards (LC-0, LC-1, LC-2, LC-3). Each line card has PFEs with different capacity requirements (e.g., Max 100 Gbps, Max 200 Gbps, Max 300 Gbps). The diagram highlights 'TOP PFE: 300G' for LC-0 and LC-2. It also shows states like 'Port unused', 'switched off', 'stand-by', and 'active'. Connections to multiple FIBs (FIB-0 to FIB-4) are indicated. - -Figure 19-11: Fabric interface board energy optimization - -In the example in Figure 19-11 each PFE is connected to 5 FIBs (10 fabric ASICs – for readability, only connections between PFEs and fabric ASICs in FIB-0 are shown in the figure). Connections to - -![O-RAN Alliance logo](6a791970c2c6af10a647cff11d071fc9_img.jpg) - -O-RAN Alliance logo - -8 fabric ASICs provide full required capacity. Therefore, capacity of connection between single PFE and single fabric ASIC is 65.2 Gbps (62.5 Gbps x 8 = 500 Gbps), or 125 Gbps between single PFE and single FIB. If in given deployment maximum required PFE capacity is 300 Gbps, it is sufficient to use 3 active FIBs (3 x 125 Gbps = 375 Gbps) + one additional FIB as spare. - -**[D68]:** TNE SHOULD have capability to administratively switch off the FIB (Figure 19-11), which also automatically switches off the power of associated SerDes modules. This process SHOULD not impact any LCs or PFEs. - -**[D69]:** TNE SHOULD automatically shut down FIB or multiple FIBs in such a way that remaining FIBs provide N+1 switching fabric redundancy even for the highest capacity PFE (Figure 19-11). When the capacity of highest capacity PFE increases (for example, due to pluggable optical module insertion into a “used” port cage, or due to administrative change of port state from “unused” to “used” for port with pluggable optical module already inserted) TNE SHOULD automatically re-evaluate, if, in order to provide N+1 switching fabric redundancy, additional FIB must be powered on and eventually automatically power on additional FIB. This process SHOULD not impact any LCs or PFEs. - -## 20 Supporting mobile scenarios on a packet switched Xhaul network - -What is clear in discussions with operators is that although section 8 outlines individual use cases, operator’s expect multiple use cases to be present in their transport network based on the need to support 4G and 5G, maturity and timelines of the O-RAN specifications, vendor product readiness, use cases and latency requirements. Figure 20-1, an adapted operator’s view, illustrates this well with multiple 4G/5G architectures present along with Enterprise and consumer services. - -![Figure 20-1: Diagram illustrating a packet switched Xhaul network architecture. The network is divided into four main segments: Access, Pre-Aggregation, Aggregation, and Transport Core. On the left, various radio units (RRH, O-RU, O-CU, eNB, gNB, APs) connect to a Centralized Switching Router (CSR). The CSR connects to the Access segment. The Access segment connects to the Pre-Aggregation segment, which in turn connects to the Aggregation segment. The Aggregation segment connects to the Transport Core. The Transport Core connects to the Internet. Various network functions are shown above or below the segments: UPF, AF, SON, RIC are shown above the Pre-Aggregation and Aggregation segments; OSS/BSS, SON, RIC, EPC, S/PGW, 5GC, UPF, AF are shown above the Aggregation and Transport Core segments; O-DU, O-CU, BBU, UPF, AF, SON are shown below the Aggregation segment; OLT FTTH and ENTERPRISE are shown below the Aggregation segment.](48fecf94dd9fb955caddbf2fb01b7b9b_img.jpg) - -Figure 20-1: Diagram illustrating a packet switched Xhaul network architecture. The network is divided into four main segments: Access, Pre-Aggregation, Aggregation, and Transport Core. On the left, various radio units (RRH, O-RU, O-CU, eNB, gNB, APs) connect to a Centralized Switching Router (CSR). The CSR connects to the Access segment. The Access segment connects to the Pre-Aggregation segment, which in turn connects to the Aggregation segment. The Aggregation segment connects to the Transport Core. The Transport Core connects to the Internet. Various network functions are shown above or below the segments: UPF, AF, SON, RIC are shown above the Pre-Aggregation and Aggregation segments; OSS/BSS, SON, RIC, EPC, S/PGW, 5GC, UPF, AF are shown above the Aggregation and Transport Core segments; O-DU, O-CU, BBU, UPF, AF, SON are shown below the Aggregation segment; OLT FTTH and ENTERPRISE are shown below the Aggregation segment. - -![O-RAN ALLIANCE logo](bc2ae13444c5d7158a37b4af477e63b7_img.jpg) - -The logo for the O-RAN Alliance, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with the word "ALLIANCE" in smaller letters underneath. - -O-RAN ALLIANCE logo - -1 **Figure 20-1: An adapted O-RAN operator's view of mobile component placement** - -2 -3 In order to make this document generic to operators, simplification is required. For this reason, the -4 following physical topology and underlay transport solution is used as a baseline. Operators can -5 then use the information and customize to their specific requirements. - -## 6 20.1 Physical network - -7 Figure 20-2 illustrates physical network layout for a metro network and its connectivity to the -8 transport core. It consists of: - -- 9 1. A collection of metro networks surrounding a transport core. Each metro network consists of -10 a number of access networks that are consolidated by an aggregation network towards to the -11 transport core. - - 12 2. All sites which interface to customer or mobile components supports Provider Edge -13 functionality for L2 and L3 overlay services. - - 14 3. Data centers or location for positioning mobile components potentially exist at the hub sites, -15 edge sites and in centralised locations. - - 16 4. Connectivity between routers is provided by line-rate point-to-point Ethernet connections -17 derived from dark fibre or WDM. - - 18 5. Access networks could be based on either small rings, star, chained or hub and spoke -19 topologies. To simplify the following discussion, it is assumed each cell site has a CSR -20 connected via a single high-capacity dark fibre to the HSR in a star topology. Refer to -21 section 10 for more details on potential fiber access topologies. - - 22 6. The Aggregation network originates from the HSR and is based on either a ring or a hub and -23 spoke topology. For some scenarios the aggregation network may be split into a pre- -24 aggregation and aggregation component. In this case, there is an intermediate layer of packet -25 switches and an additional layer of statistical multiplexing. (See greyed out router / switch in -26 Figure 20-2) -- 27 -28 -29 -30 - -1 - -![Figure 20-2: An example physical architecture diagram. The diagram shows a network topology starting with three 'Access' clouds on the left, each connected to a 'Cell Site Router (CSR)'. Each CSR is connected to an 'Edge DC'. The Edge DCs are connected to a central 'Aggregation Network' which contains two 'Agg DC' units, one of which is labeled 'optional'. The Aggregation Network is connected to a 'Hub Site Router (HSR)'. The HSR is connected to an 'Edge Router (ER)'. The ER is connected to a 'Regional DC'. The Regional DC is connected to a 'Transport Core', which in turn is connected to a 'Central DC'. Various icons representing routers and switches are placed throughout the diagram to indicate connection points.](511f9b05a4c458937dd12c30936fd7d6_img.jpg) - -Cell Site Router (CSR)      Hub Site Router (HSR)      Edge Router (ER) - -Figure 20-2: An example physical architecture diagram. The diagram shows a network topology starting with three 'Access' clouds on the left, each connected to a 'Cell Site Router (CSR)'. Each CSR is connected to an 'Edge DC'. The Edge DCs are connected to a central 'Aggregation Network' which contains two 'Agg DC' units, one of which is labeled 'optional'. The Aggregation Network is connected to a 'Hub Site Router (HSR)'. The HSR is connected to an 'Edge Router (ER)'. The ER is connected to a 'Regional DC'. The Regional DC is connected to a 'Transport Core', which in turn is connected to a 'Central DC'. Various icons representing routers and switches are placed throughout the diagram to indicate connection points. - -2 -3 - -**Figure 20-2: An example physical architecture** - -## 4 20.2 Logical underlay architecture - -5 The logical underlay is illustrated in Figure 20-3 and consists of QoS enabled infrastructure that - 6 either uses an IP/MPLS or an SRv6 underlay data and control plane. It provides any-to-any - 7 connectivity between TNEs in the network, regardless of whether they reside in the same metro - 8 network, a different metro network or the transport core and supports both shortest path routing and - 9 traffic engineering. The underlay data planes, control plane and scaling mechanisms to enable this - 10 for IP/MPLS and SRv6 are different and discussed in their respective chapters. Both solutions have - 11 the capabilities to support best effort and traffic engineered forwarding and the capability to create - 12 discrete constrained based topologies using either traditional traffic engineering or flexible - 13 algorithm which can be optimized on criteria such as shortest path, delay and bandwidth. - -![O-RAN ALLIANCE logo](2d22d155e3f98dbb44dabef33853c268_img.jpg) - -O-RAN ALLIANCE logo - -1 - -![Figure 20-3: An example logical architecture diagram showing the flow from Cell Site Routers (CSR) through Edge DCs, Aggregation Networks, and Regional DCs to a Central DC via a Transport Core. It also shows various routers like Hub Site Router (HSR) and Edge Router (ER).](e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg) - -Figure 20-3: An example logical architecture diagram showing the flow from Cell Site Routers (CSR) through Edge DCs, Aggregation Networks, and Regional DCs to a Central DC via a Transport Core. It also shows various routers like Hub Site Router (HSR) and Edge Router (ER). - -End to end underlay transport infrastructure using IP/MPLS or SRv6 - -2 -3 - -**Figure 20-3: An example logical architecture** - -4 - -**20.2.1 Underlay Quality of Service (QoS)** - -5 -6 -7 -8 -9 -10 -11 -12 - -Refer to section 14 for fuller discussion on QoS. Underlay QoS refers to the scheduling used on the core or backbone links. All backbone links are enabled with a combination of priority and class-based queueing. Assignment of traffic to different queues within the core is based on marking within the packet header. In an MPLS backbone this is based on the EXP bits or traffic class field, a three-bit field, giving a maximum number of core behaviours of eight. In an IPv6 backbone this is based on the DSCP bits, a six-bit field, giving a maximum number of 64 markings and potential behaviours. - -![Figure 20-4: Example Xhaul queue structure diagram showing six traffic types with their respective queue numbers and a visual representation of a queueing mechanism.](a4c493cd9a047cf61c944c8c56ecf282_img.jpg) - -| Traffic Type | Queue Number | -|---------------------------------------------------|--------------| -| Latency sensitive fronthaul traffic (P1) | 5 | -| Latency sensitive U-plane + business traffic (P2) | 2 | -| Network control plane(BFD, IGP, PTP) (P3) | 7 | -| Guaranteed bandwidth traffic (e.g. management) | 6 | -| Guaranteed bandwidth U-plane and business traffic | 3,4 | -| Other best effort (may be guaranteed) | 0,1 | - -Figure 20-4: Example Xhaul queue structure diagram showing six traffic types with their respective queue numbers and a visual representation of a queueing mechanism. - -13 -14 -15 -16 - -**Figure 20-4: Example Xhaul queue structure** - -## 20.3 Service architecture - -For mobile services it is proposed to use BGP based VPNs to overlay service functionality onto the underlay transport network as described in section 13. - -NOTE: There is no reason this same transport infrastructure cannot support other VPN solutions such as VXLAN or SD-WAN type solutions. - -All PEs and DCIs (which are also PEs) should be capable of supporting point to point Ethernet services using EVPN VPWS services and L3 BGP VPN services described in section 13. With these two basic service overlays all the scenarios outlined in section 8 can be accommodated. - -### 20.3.1 Automated VPN Traffic Steering - -If required traffic from different VPNs or specific flows within an VPN can be steered into different underlay transport planes based on coloring the MP-BGP VPN routes associated with L2 and L3 VPNs. This capability is described in *Annex C: MP-BGP based L3 VPNs*. - -## 20.4 Mobile services - -There are many ways Fronthaul, Midhaul and Backhaul services could be provisioned onto the transport network. Below are a set of assumptions and mechanisms used to illustrate how a packet switched architecture can accommodate the scenarios outlined. These can easily be adapted based on operator's individual requirements. - -### 20.4.1 Open Fronthaul - -Figure 20-5 illustrates a physical and logical design that supports Open Fronthaul traffic. It is fairly simple in nature, however, can easily be adapted based on operator designs and requirements. It uses the underlay building blocks discussed earlier chapters. - -![Figure 20-5: Fronthaul physical and logical topology diagram. The diagram shows six O-RU units connected to two separate GSR (Gateway Router) units. Each GSR is connected to a central Hub Site Router (HSR). The HSR is connected to an O-DU (Distributed Unit). The O-RUs are connected to the GSRs via individual interfaces or VLANs. The GSRs are connected to the HSR via L3 VPN tunnels. The HSR is connected to the O-DU via L2 VPWS (via EVPN) tunnels. The diagram also shows two management planes: 'Open fronthaul management plane (L3VPN)' and 'L3 VPN for 7.2X M-Plane'.](d01f4371bb8136148156771a18b9ea89_img.jpg) - -The diagram illustrates the physical and logical topology for Open Fronthaul. On the left, six O-RU (Radio Unit) blocks are stacked vertically. Each O-RU is connected to one of two GSR (Gateway Router) blocks. The top GSR and bottom GSR are each connected to a central Hub Site Router (HSR) block. The HSR is connected to an O-DU (Distributed Unit) block at the bottom. The connections between O-RUs and GSRs are labeled 'Individual Interface / VLAN per O-RU'. The connections between GSRs and the HSR are labeled 'L3 VPN for 7.2X M-Plane'. The connection between the HSR and the O-DU is labeled 'L2 VPWS (via EVPN) for 7.2X C/U Plane'. At the top, a shaded area represents the 'Open fronthaul management plane (L3VPN)'. - -Figure 20-5: Fronthaul physical and logical topology diagram. The diagram shows six O-RU units connected to two separate GSR (Gateway Router) units. Each GSR is connected to a central Hub Site Router (HSR). The HSR is connected to an O-DU (Distributed Unit). The O-RUs are connected to the GSRs via individual interfaces or VLANs. The GSRs are connected to the HSR via L3 VPN tunnels. The HSR is connected to the O-DU via L2 VPWS (via EVPN) tunnels. The diagram also shows two management planes: 'Open fronthaul management plane (L3VPN)' and 'L3 VPN for 7.2X M-Plane'. - -**Figure 20-5: Fronthaul physical and logical topology** - -![O-RAN Alliance logo](deb817f1a57c7185d59319e4113beb4f_img.jpg) - -The O-RAN Alliance logo, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -#### 1 20.4.1.1 Assumptions - -- 2 1. 7.2x C/U planes connects to the transport network via a VLAN on a physical Ethernet -- 3 interfaces on O-RUs and O-DUs. -- 4 -- 5 2. 7.2x C/U planes traffic uses Ethernet / VLAN encapsulation option and not the optional -- 6 Ethernet / VLAN / IP encapsulation. -- 7 -- 8 3. 7.2x C/U planes uses an Ethernet service across the transport network to connect O-RUs to -- 9 O-DUs. This is via an Ethernet PWPS service using EVPN in the transport network. -- 10 -- 11 4. If the 7.2x C/U planes traffic used an Ethernet / VLAN / IP encapsulation, then the transport -- 12 network could use a L3 VPN service to transport the traffic between the O-RU and the O- -- 13 DU, but this is not considered in the following sections. -- 14 -- 15 5. 7.2x M-plane connects to the transport network via a VLAN on a physical Ethernet. -- 16 -- 17 6. 7.2x M-plane uses an Ethernet / VLAN / IP encapsulation. -- 18 -- 19 7. 7.2x M-plane is operating in hybrid mode and uses an L3 VPN service across the transport -- 20 network to connect O-RUs, O-DUs and O-RAN NMS together. This is via an overlay MP- -- 21 BGP based L3VPN. -- 22 -- 23 8. For the following discussion, the 7.2x C/U planes and M plane share a single physical -- 24 Ethernet interface on the O-RU towards the CSR with the C/U plane and M-Plane running in -- 25 different VLANs. -- 26 -- 27 9. Each O-RU has its own dedicated Ethernet port on the CSR. I.E There is no lower level -- 28 aggregation of statistical multiplexing component between an O-RU and the CSR. -- 29 -- 30 10. O-RU and O-DU set appropriate QoS markings for C/U and M-plane traffic that the -- 31 transport network can trust. In other words, the TNE does not need to classify different -- 32 components of Fronthaul for transport. -- 33 - -#### 34 20.4.1.2 Open Fronthaul physical design - -- 35 1. 3 O-RUs per cell site. -- 36 -- 37 2. In the above example, each O-RU is connected via a dedicated Ethernet interface to a co- -- 38 located CSR. This single Ethernet supports both the C/U planes and the M-plane presented -- 39 through two VLANs. The required capacity of the Ethernet link between the O-RU and the -- 40 CSR is primarily dependent on the O-RU's radio capabilities. The requirements document -- 41 [20] provides some bandwidth examples for Open Fronthaul bandwidth. The expectation is -- 42 that the C/U plane traffic will be significantly larger than the M-Plane traffic, therefore these -- 43 Ethernet interfaces should be provisioned to deal with the peak 7.2x C/U-plane traffic of an -- 44 O-RU. It should be noted that unlike CPRI, the 7.2x C/U plane traffic loads are dependent on -- 45 user activity, so peak loading will only occur when the O-RU is running at full theoretical -- 46 capacity. -- 47 - -![O-RAN ALLIANCE logo](0a7136b9ffcd39128eaeb609dbfe8913_img.jpg) - -O-RAN ALLIANCE logo - -3. In the above example, each CSR is connected using a single Ethernet link across dark fibre to the HSR. Other underlay transport technologies and topologies are available, such as redundant hub and spoke, chain or ring topologies in the access network. Regardless of the WAN technology and topology employed, careful consideration needs to be given the latency and jitter requirements of C/U plane traffic between the O-RU and the O-DU. Transport considerations includes fibre distances between the O-RU and the O-DU, the number of routers/switches traversed, link speeds and switching times of the intermediate transport network equipment. (*see section 10.1.1.2 for more details*). As O-RAN 7.2x traffic loads are dependent on user activity and in the example there are multiple O-RUs in the cell site, the link capacity between the CSR and HSR does not need to be provisioned at the theoretical sum of the O-RU’s peak rates because a statistical gain can be realised. The bandwidth provisioning should be based on usage and the real achievable peak rates associated with the O-RUs. The real achievable peak rates are dependent on factors such as number and proximity of radios to each other and environmental factors. Precise provisioning rules for 5G Fronthaul is subject to further investigation. - -#### 20.4.1.3 QoS - -1. The QoS scheme outlined in section 20.2.1, Figure 20-4 will be applied across the transport network and is capable of supporting Fronthaul, Midhaul and Backhaul traffic running on the same link. If an SRv6 underlay is to be used, then at a minimum the same queue structure supported by appropriate operator selected DSCP marking should be used. -2. O-RU and O-DU set appropriate QoS markings for C/U and M-plane traffic that transport network can trust. -3. In the above example, the C/U and M-plane traffic share the same physical interface, separated using VLANs between the O-RU and CSR and between HSR and O-DU. In this situation the mobile components (O-RUs and O-DUs) will need to support: - - An internal scheduling mechanism to prioritise C/U plane traffic over M-Plane traffic onto the Ethernet interface - - Depending on O-RU $\leftrightarrow$ CSR and HSR $\leftrightarrow$ O-DU link speeds, the O-RU, O-DU, CSR and HSR may need to support TSN frame pre-emption to control serialization delay. (refer to section 10.1.1.2.1 for more details). Alternatively, if the O-RU or CSR do not support TSN frame pre-emption or the O-DU or HSR do not support TSN frame pre-emption, then separate physical interfaces could be used to separate the C/U plane and M-plane traffic. -5. C/U and M-plane traffic from all O-RUs in the cell site share the same transport link between the CSR and the HSR. In most scenarios where a CSR supports multiple radios running fronthaul, this link will be 25Gbps or above and therefore does not really benefit from TSN frame pre-emption. However, in some instances, the link between the CSR and HSR may be lower speed and would benefit from TSN frame pre-emption. (see section 10.1.1.2.1 for more details) -6. C/U plane traffic must be prioritized over M-plane traffic on the WAN links. CSR and HSR must be provisioned at both the link level and within the link level queuing infrastructure in a manner such that C/U plane traffic is not dropped or experiences queuing delay in either the CSR or HSR (or any additional Transport Network Equipment in the path between the O-RU and the O-DU). M-plane traffic can experience a level of delay, so be configured to use a lower priority queue or a queuing scheme such as Weighted Round Robin that reserves a small amount of bandwidth for management traffic (see section 14 for an example) - -![O-RAN Alliance logo](7f46e92a1d022a1c67559541c7cb1596_img.jpg) - -O-RAN Alliance logo - -#### 20.4.1.4 Services - -1. C/U plane traffic uses an EVPN VPWS service to transport traffic between the O-RU and O-DU over the access network. To simplify cell site VLAN provisioning, common VLANs could be used between the O-RUs and the CSR and VLAN tag translation could occur on the HSR to provide a unique interface / VLAN id per O-RU towards the O-DU. Depending on the capabilities of the O-DU, EVPN has mechanisms that can provide service level resiliency but this is dependent on the O-DU network implementation. -2. The M-plane traffic on the O-RU and O-DU connects, via a VLAN or physical interface to a MP-BGP based L3 VPN service. This provides layer 3 connectivity between the management components on the O-RU, O-DU and the O-RAN “Network Management System” (NMS). “Route Target” filtering could be used to restrict transport level connectivity between management entities. For example, the transport network could be configured such that IP connectivity is only permitted between the NMS and the O-DUs and O-RUs, while no IP connectivity is permitted between O-RUs. - -#### 20.4.2 Non O-RAN Fronthaul - -The assumptions, design approach and considerations discussed for the C/U planes in Open Fronthaul are used for Non O-RAN Fronthaul. - -#### 20.4.3 D2 - -Figure 20-6 illustrates a physical and logical design that supports D2 traffic. It is fairly simple in nature, however, can easily be adapted based on operator designs and requirements. It uses the underlay building blocks discussed earlier chapters - -![Figure 20-6: D2 Logical topology diagram showing two O-DUs (O-DU1 and O-DU2) connected via Open Fronthaul VPWS Circuits. Each O-DU contains a D2 Control plane (green) and a D2 User plane (orange).](dc79f71c6bae35b5d62f636dbc7f9bb9_img.jpg) - -The diagram illustrates the logical topology for D2 traffic between two O-DUs, O-DU1 and O-DU2. Each O-DU is represented by a large oval containing two horizontal planes: a green 'D2 Control plane' on top and an orange 'D2 User plane' on the bottom. Vertical double-headed arrows within each O-DU indicate internal connectivity. Between the two O-DUs, two horizontal double-headed arrows connect the corresponding planes: one for the control planes and one for the user planes. Above the O-DUs, the text 'Open Fronthaul VPWS Circuits' is accompanied by red dashed lines that point to the connections between the O-DUs. Below each O-DU oval is a rectangular box labeled 'O-DU1' and 'O-DU2' respectively. Each O-DU also has a vertical stack of colored bars (red, green, blue, yellow) on its left and right sides, representing various interfaces or ports. - -Figure 20-6: D2 Logical topology diagram showing two O-DUs (O-DU1 and O-DU2) connected via Open Fronthaul VPWS Circuits. Each O-DU contains a D2 Control plane (green) and a D2 User plane (orange). - -Figure 20-6: D2 Logical topology - -#### 20.4.3.1 Assumptions - -- O-DU set appropriate QoS markings for C and U-plane traffic that the transport network can trust. In other words, the TNE does not need to classify different components of D2 for transport. - -### 20.4.3.2 D2 transport physical topology - -- O-DUs connect, via Ethernet interface/interfaces on a direct fiber connection, to a co-located HSR or CSR, or via other TNE. The Ethernet interface/interfaces support D2 control and user plane traffic via two discrete VLANs. -- D2 user plane traffic levels are dependent on UE usage. The O-RAN Transport Requirements document [20] outlines some of the provisioning rules widely used in planning 4G Backhaul networks. Although not directly applicable to the 5G, they provide a good starting point. Longer term network capacity planning should be done based on monitoring and modelling the live network. - -### 20.4.3.3 QoS - -- D2-U traffic is latency sensitive (though D2-C traffic is far more tolerant to delay). Hence, for most 5G use-cases fiber propagation delay, number of hops, transport equipment switching times and serialization delays should be considered while designing D2 networks. - -### 20.4.3.4 Services - -- Two L3 VPNs are created; the first D2 control plane traffic and the second is D2 user plane traffic. O-DUs, connects to both L3VPNs. - -## 20.4.4 Midhaul and Backhaul - -Figure 20-7 illustrates a physical and logical design that could be employed to support Midhaul and Backhaul traffic. It is a simple example but can easily be adapted based on operator designs and requirements. It uses the underlay building blocks discussed earlier in the chapter. - -![Figure 20-7: Midhaul and Backhaul logical topology diagram. The diagram shows a logical topology over an Aggregation Transport Network. On the left, an O-DU is connected to a Hub Site Router (HSR). The HSR is connected to an Open Fronthaul management plane (L3VPN) which is also connected to an FH Mgmt box. The HSR is also connected to an Open Fronthaul VPWS circuit. The HSR is connected to an O-CU via two L3VPNs: MH/BH control plane (L3VPN) and MH/BH user plane (L3VPN). The O-CU is connected to a 5GC box. The 5GC box is connected to an N6 cloud. The N6 cloud is connected to a UPF box. The UPF box is connected to the Aggregation Transport Network.](27c0455a3b08749fed8057467366b0ce_img.jpg) - -Figure 20-7: Midhaul and Backhaul logical topology diagram. The diagram shows a logical topology over an Aggregation Transport Network. On the left, an O-DU is connected to a Hub Site Router (HSR). The HSR is connected to an Open Fronthaul management plane (L3VPN) which is also connected to an FH Mgmt box. The HSR is also connected to an Open Fronthaul VPWS circuit. The HSR is connected to an O-CU via two L3VPNs: MH/BH control plane (L3VPN) and MH/BH user plane (L3VPN). The O-CU is connected to a 5GC box. The 5GC box is connected to an N6 cloud. The N6 cloud is connected to a UPF box. The UPF box is connected to the Aggregation Transport Network. - -**Figure 20-7: Midhaul and Backhaul logical topology** - -![O-RAN Alliance logo](b93f124d1a7bfa31a18e5ffae184e015_img.jpg) - -O-RAN Alliance logo - -1 The following design assumptions have been made about the Midhaul / Backhaul components and - 2 how traffic is presented and moved across the transport network. - -#### 3 20.4.4.1 Assumptions - -- 4 1. Midhaul and Backhaul traffic share the same L3 VPNs. -- 5 2. There are dedicated and separate L3 VPNs for control plane traffic (N1, N2) and user plane -- 6 traffic (N3 and N9). -- 7 3. If legacy Backhaul is required, it shares the same L3 VPN transport services used by the 5G -- 8 EMBB Midhaul and Backhaul user and control plane infrastructure. -- 9 4. If there are multiple Midhaul and Backhaul transport slices, they could run in their own -- 10 independent L3 VPNs (see Annex F: Transport network slicing solution for WG1 Slicing -- 11 (informational)) -- 12 5. Midhaul and Backhaul mobile components will either use a discrete independent VLAN or a -- 13 dedicated physical Ethernet to separate control and user plane traffic. For the following -- 14 discussion it is assumed they are presented via VLANs on a single Ethernet interface. -- 15 6. Midhaul and Backhaul mobile components which require connectivity to different transport -- 16 slices will either use a discrete VLAN or a dedicated physical interfaces per slice. For the -- 17 following discussion it is assumed they will be presented via VLANs. -- 18 7. The transport and RAN teams have collaborated on Midhaul / Backhaul QoS marking and -- 19 packets emerging from O-DUs, O-CUs and UPFs have a DSCP marking appropriate to their -- 20 5G forwarding requirements, and the TNEs can trust these markings. -- 21 8. N6 networks associated with different customers, applications or use cases will use L3 -- 22 VPNs. - -23 - 24 Note: Other service designs could be considered, for example a design where only Ethernet services - 25 are used from the cell site and the hub sites and L3 VPN services are built at the hub sites. The - 26 primary reason for the choice outlined above is to make the service orchestration as simple as - 27 possible, so services only need to be configured where the mobile clients connect to the transport - 28 network and no intermediate stitching points within the transport network are needed. - -#### 29 20.4.4.2 Midhaul and Backhaul physical topology - -- 30 1. O-DUs connect, via Ethernet interface/interfaces, to a co-located HSR or CSR. The Ethernet -- 31 interface/interfaces support Midhaul control and user plane traffic via two discrete VLANs. -- 32 2. O-CUs connect, via Ethernet interfaces to the transport network. The O-CU Ethernet -- 33 interface/interfaces support Midhaul and Backhaul control and user plane traffic via two -- 34 discrete VLANs. -- 35 3. The UPFs connect, via Ethernet interfaces to the transport network. The UPF connects to the -- 36 common control and user plane Midhaul/Backhaul VPNs. -- 37 4. The location of the O-CUs and UPFs is service dependent and the choice of the operator. -- 38 Additionally, these components may be virtualized or containerized and reside in a data -- 39 center. In these scenarios, orchestration techniques maybe be required to connect the -- 40 virtualized O-DU, O-CU and UPF components in the data centers to the correct WAN -- 41 L3VPNs. -- 42 5. 5G Core components connect via Ethernet interfaces to the transport network in their -- 43 respective locations. These components may be virtualized or containerized and reside in a -- 44 data center. In these scenarios, orchestration techniques are required to connect the 5G -- 45 control plane entities in the data centers to the Midhaul and Backhaul control plane WAN -- 46 L3VPNs. - -![O-RAN Alliance logo](6080df47bc782c101b2abbb9803962f2_img.jpg) - -O-RAN Alliance logo - -6. O-CU can reside in the same location as the O-DUs it controls, therefore Midhaul traffic never leaves the site and is switched between the two entities by the either the CSR or HSR. Alternatively, the O-CU can reside in a different location to the O-DUs it controls. In this case the Midhaul traffic traverses the WAN. -7. HSRs provides the boundary between the access and aggregation networks. Connectivity to the aggregation network will typically use high-capacity Ethernet interfaces or bundles of high capacity Ethernet interface. The topology of the aggregation network is normally resilient, but topologies vary based on operator choices and constraints, with hub and spoke and rings very common. -8. Midhaul and Backhaul user plane traffic levels are dependent on UE usage, the characteristics of the radio and the number the proximity of radios to each other. The O-RAN Transport Requirements document [20] outlines some of the provisioning rules widely used in planning 4G Backhaul networks. Although not directly applicable to the 5G, they provide a good starting point. Longer term network capacity planning should be done based on monitoring and modelling the live network. - -#### 20.4.4.3 QoS - -1. O-CU and UPFs mark the packets they produce based on the behaviour required for the mobile data the carry. -2. Most Midhaul and Backhaul traffic is far more tolerant to delay, and jitter compared with Fronthaul traffic. The exception could be some URLLC based use-cases. However, for most 5G use-cases fibre propagation delay, number of hops, transport equipment switching times and serialization delays are not of a huge issue when designing Midhaul and Backhaul networks. -3. In some scenarios, particularly when some forms of slicing are considered then edge QoS in the form of ingress and egress H-QoS will be required. - -#### 20.4.4.4 Services - -1. Two L3 VPNs are created; the first is Midhaul/Backhaul control plane traffic and the second is Midhaul/Backhaul user plane traffic. O-DUs, O-CUs, UPFs connects to both L3VPNs. The 5GC connect only to the control plane L3VPN. If required “Route Target” filtering could be used to restrict transport level connectivity between mobile entities. - -### 20.5 Scenario 1 and 5 - -Both scenario 1 and 5 represent a full two split C-RAN architecture. The main difference is the location and proximity of the O-DUs and the O-CUs to each other. In scenario 1 they are contained in a single hub site location, in scenario 5 they are split across different locations. - -At the high level the basic service layout for scenario 1 and 5 is shown in Figure 20-8 and Figure 20-9 with a more detailed layout shown in Figure 20-10. - -![ORAN ALLIANCE logo](cc9b98d9bd87c73583bc813c02b91351_img.jpg) - -ORAN ALLIANCE logo - -1 - -![Figure 20-8: Scenario 1 layout diagram](0eb348bf17d67bf96326e07011d1c1ad_img.jpg) - -This diagram illustrates the network architecture for Scenario 1. On the left, three O-RU units are connected via VPWS to an O-DU. The O-DU is co-located with an O-CU and an Edge DC. The O-DU connects to a central cloud representing the Midhaul/Backhaul Control Plane (L3VPN), which in turn connects to the Midhaul/Backhaul Data Plane (L3VPN). The O-CU connects to the Control Plane cloud. The Data Plane cloud connects to a UPF, which is co-located with a Regional DC. The UPF connects to an N6 cloud. Above the clouds, a Fronthaul management plane (L3VPN) is shown, connecting to the O-RU units and the O-RAN MGMT/5G CP unit. The O-RAN MGMT/5G CP unit is connected to the Control Plane cloud. - -Figure 20-8: Scenario 1 layout diagram - -Figure 20-8: Scenario 1 layout - -2 -3 -4 -5 - -![Figure 20-9: Scenario 5 layout diagram](c2dbaf7c88ad38cb8620f6d731935ed8_img.jpg) - -This diagram illustrates the network architecture for Scenario 5. On the left, three O-RU units are connected via VPWS to an O-DU, which is co-located with an Edge DC. The O-DU connects to a central cloud representing the Midhaul/Backhaul Control Plane (L3VPN). The O-DU also connects to an O-CU, which is co-located with an Agg DC. The O-CU connects to the Control Plane cloud. The Control Plane cloud connects to the Midhaul/Backhaul Data Plane (L3VPN) cloud. The Data Plane cloud connects to a UPF, which is co-located with a Regional DC. The UPF connects to an N6 cloud. Above the clouds, a Fronthaul management plane (L3VPN) is shown, connecting to the O-RU units and the O-RAN MGMT/5G CP unit. The O-RAN MGMT/5G CP unit is connected to the Control Plane cloud. - -Figure 20-9: Scenario 5 layout diagram - -Figure 20-9: Scenario 5 layout - -6 -7 - -![O-RAN Alliance logo](5ba4353c6c79c5cc8f47b2f425afd0cc_img.jpg) - -O-RAN Alliance logo - -1 - -![Figure 20-10: L2 / L3 service layout for scenario 1 and 5. This diagram shows the network architecture where O-RUs are connected to a Cell Site Router (CSR) at the cell site. The CSR is connected to an O-DU and an O-CU at a hub site via 'Fronthaul interfaces with VLANs or discrete Ethernet interfaces' (Access). The O-CU is connected to a Hub Site Router (HSR), which is part of the 'Midhaul / Backhaul' network (Aggregation) leading to the 5GC and UPF. Three service planes are shown: 'Open fronthaul management plane (L3VPN)' (orange), 'Midhaul/Backhaul Control Plane (L3VPN)' (green), and 'Midhaul/Backhaul user Plane (L3VPN)' (green). A 'L2 EVPN VPWS for 7.2X C/U Plane' is indicated between the CSR and the O-DU. A 'Backhaul CP interface' is shown at the 5GC connection point.](febb6833677d1ca3a5550901b7673b63_img.jpg) - -Figure 20-10: L2 / L3 service layout for scenario 1 and 5. This diagram shows the network architecture where O-RUs are connected to a Cell Site Router (CSR) at the cell site. The CSR is connected to an O-DU and an O-CU at a hub site via 'Fronthaul interfaces with VLANs or discrete Ethernet interfaces' (Access). The O-CU is connected to a Hub Site Router (HSR), which is part of the 'Midhaul / Backhaul' network (Aggregation) leading to the 5GC and UPF. Three service planes are shown: 'Open fronthaul management plane (L3VPN)' (orange), 'Midhaul/Backhaul Control Plane (L3VPN)' (green), and 'Midhaul/Backhaul user Plane (L3VPN)' (green). A 'L2 EVPN VPWS for 7.2X C/U Plane' is indicated between the CSR and the O-DU. A 'Backhaul CP interface' is shown at the 5GC connection point. - -2 - -3 - -4 - -Figure 20-10: L2 / L3 service layout for scenario 1 and 5 - -5 - -## 20.6 Scenario 2 - -6 - -Scenario 2 represent a full two split C-RAN architecture with the O-RU and O-DU at the cell site and the O-CU at the hub site and is shown in Figure 20-11. - -7 - -8 - -9 - -![Figure 20-11: L2 / L3 service layout for scenario 2. This diagram shows the network architecture where both O-RU and O-DU are located at the cell site and connected to a Cell Site Router (CSR). The CSR provides an 'L2 x-connect for 7.2X C/U Plane' between the O-RU and O-DU. The O-DU is connected to an O-CU at a hub site via 'O-DU Midhaul interfaces to L3 VPNs'. The O-CU is connected to a Hub Site Router (HSR), which is part of the 'Midhaul / Backhaul' network (Aggregation) leading to the 5GC and UPF. Three service planes are shown: 'Open fronthaul management plane (L3VPN)' (orange), 'Midhaul/Backhaul Control Plane (L3VPN)' (green), and 'Midhaul/Backhaul user Plane (L3VPN)' (green). A 'Backhaul CP interface' is shown at the 5GC connection point.](3eb092cb663bfa38f2ed2ea2548460ed_img.jpg) - -Figure 20-11: L2 / L3 service layout for scenario 2. This diagram shows the network architecture where both O-RU and O-DU are located at the cell site and connected to a Cell Site Router (CSR). The CSR provides an 'L2 x-connect for 7.2X C/U Plane' between the O-RU and O-DU. The O-DU is connected to an O-CU at a hub site via 'O-DU Midhaul interfaces to L3 VPNs'. The O-CU is connected to a Hub Site Router (HSR), which is part of the 'Midhaul / Backhaul' network (Aggregation) leading to the 5GC and UPF. Three service planes are shown: 'Open fronthaul management plane (L3VPN)' (orange), 'Midhaul/Backhaul Control Plane (L3VPN)' (green), and 'Midhaul/Backhaul user Plane (L3VPN)' (green). A 'Backhaul CP interface' is shown at the 5GC connection point. - -10 - -11 - -Figure 20-11: L2 / L3 service layout for scenario 2 - -12 - -Notes on the design: - -13 - -1. Fronthaul traffic is restricted to the cell site with the CSR providing a local L2 x-connect function to get C/U plane traffic between the O-RUs and the O-DU. - -14 - -2. The Midhaul/Backhaul control and user plane L3 VPNs need to be extended to the cell site router. - -15 - -16 - -![O-RAN Alliance logo](3eeec80822340aa7c74d7dc2f215bfc5_img.jpg) - -O-RAN Alliance logo - -3. In above diagram the O-DU has two physical interfaces with one supporting Fronthaul traffic and the other supporting, via VLANs, Midhaul and Backhaul control plane, user plane and Open Fronthaul M-plane traffic. In this instance TSN frame pre-emption is not really a consideration. If the Midhaul, Backhaul and Fronthaul traffic shared the same physical interface on the O-DU and the CSR, then depending on interface speeds, TSN frame pre-emption may need to run between the O-DU and the CSR. - -## 20.7 Scenario 3 5G C-RAN with legacy D-RAN - -### 20.7.1 Scenario 3a - -Scenario 3a is a full two split C-RAN architecture with the O-RU at the cell site and O-DU at the hub site sitting alongside an existing 4G D-RAN architecture and is shown in Figure 20-12. O-CU, UPF and 5GC location are largely immaterial but they do need connectivity to the appropriate L3VPNs. - -![Figure 20-12: L2 / L3 service layout for scenario 3a. The diagram shows a network architecture with the following components and connections: - - On the left, an 'eNB' and an 'O-RU' are connected to a 'Cell Site Router (CSR)'. - - The 'CSR' is connected to a 'Hub Site Router (HSR)' via 'Fronthaul interfaces with VLANs or discrete Ethernet interfaces' (labeled 'Access'). - - The 'HSR' is connected to an 'O-DU' and an 'O-CU'. - - The 'O-DU' is connected to a 'UPF' via 'Midhaul / Backhaul interfaces with VLANs or discrete Ethernet Interfaces' (labeled 'Aggregation'). - - The 'UPF' is connected to a '5GC'. - - A 'Backhaul CP interface' is shown between the '5GC' and the 'UPF'. - - Three tunnels are depicted between the 'CSR' and the 'UPF': - - 'Open fronthaul management plane (L3VPN)' (orange) - - 'Midhaul/Backhaul Control Plane (L3VPN)' (green) - - 'Midhaul/Backhaul user Plane (L3VPN)' (green) - - A red dashed line labeled '7.2X C/U plane via EVPN VPWS' connects the 'eNB' to the 'UPF'.](5f3f302d1ab63beb8898d1ecfb7b63fe_img.jpg) - -Figure 20-12: L2 / L3 service layout for scenario 3a. The diagram shows a network architecture with the following components and connections: - - On the left, an 'eNB' and an 'O-RU' are connected to a 'Cell Site Router (CSR)'. - - The 'CSR' is connected to a 'Hub Site Router (HSR)' via 'Fronthaul interfaces with VLANs or discrete Ethernet interfaces' (labeled 'Access'). - - The 'HSR' is connected to an 'O-DU' and an 'O-CU'. - - The 'O-DU' is connected to a 'UPF' via 'Midhaul / Backhaul interfaces with VLANs or discrete Ethernet Interfaces' (labeled 'Aggregation'). - - The 'UPF' is connected to a '5GC'. - - A 'Backhaul CP interface' is shown between the '5GC' and the 'UPF'. - - Three tunnels are depicted between the 'CSR' and the 'UPF': - - 'Open fronthaul management plane (L3VPN)' (orange) - - 'Midhaul/Backhaul Control Plane (L3VPN)' (green) - - 'Midhaul/Backhaul user Plane (L3VPN)' (green) - - A red dashed line labeled '7.2X C/U plane via EVPN VPWS' connects the 'eNB' to the 'UPF'. - -Figure 20-12: L2 / L3 service layout for scenario 3a - -Notes on the design: - -1. Open Fronthaul traffic runs over the access network to an O-DU located in the Hub site using a VPWS EVPN service. -2. The Midhaul/Backhaul control and user plane VPNs extend to the cell site to support the existing 4G D-RAN solution. -3. The QoS design in the access network needs to be able to cater for the requirements of the Open Fronthaul when D-RAN Backhaul traffic is sharing the same physical link. - -### 20.7.2 Scenario 3b - -Scenario 3b is a full two split C-RAN architecture with the O-RU and O-DU at the cell site and the O-CU located at the hub site sitting alongside an existing D-RAN architecture and is shown in Figure 20-13 - -![ORAN ALLIANCE logo](17f5dcaf382b0b243584197a6456c1f5_img.jpg) - -ORAN ALLIANCE logo - -1 - -![Figure 20-13: L2 / L3 service layout for scenario 3b. This diagram shows the network architecture for scenario 3b. On the left, O-DU, O-RU, and eNB units are connected to a Cell Site Router (CSR). The O-DU and Legacy D-RAN connect to three VPN tunnels: Open fronthaul management plane (L3VPN), Midhaul/Backhaul Control Plane (L3VPN), and Midhaul/Backhaul user Plane (L3VPN). The O-RU and eNB connect via an L2 xconnect for the 7.2X C/U Plane. The CSR connects to a Hub Site Router (HSR) which is part of the O-CU. The HSR connects to the Aggregation network, which includes a 5GC and a UPF. The Aggregation network interfaces with the Midhaul/Backhaul via VLANs or discrete Ethernet Interfaces. The Backhaul CP interface connects the 5GC to the Aggregation network.](1fd763be1b7a05b52e554f0583617642_img.jpg) - -Figure 20-13: L2 / L3 service layout for scenario 3b. This diagram shows the network architecture for scenario 3b. On the left, O-DU, O-RU, and eNB units are connected to a Cell Site Router (CSR). The O-DU and Legacy D-RAN connect to three VPN tunnels: Open fronthaul management plane (L3VPN), Midhaul/Backhaul Control Plane (L3VPN), and Midhaul/Backhaul user Plane (L3VPN). The O-RU and eNB connect via an L2 xconnect for the 7.2X C/U Plane. The CSR connects to a Hub Site Router (HSR) which is part of the O-CU. The HSR connects to the Aggregation network, which includes a 5GC and a UPF. The Aggregation network interfaces with the Midhaul/Backhaul via VLANs or discrete Ethernet Interfaces. The Backhaul CP interface connects the 5GC to the Aggregation network. - -Figure 20-13: L2 / L3 service layout for scenario 3b - -2 -3 -4 -5 -6 -7 - -Notes on the design: - -- 1. The only difference between scenario 2 is that the legacy D-RAN equipment also connect to the Midhaul/Backhaul control and user plane VPNs at the cell site. - -8 - -## 20.8 Scenario 4 5G C-RAN with RoE mappers - -9 -10 - -Scenario 4 is a full two split C-RAN architecture with O-RAN 7.2x and non O-RAN Fronthaul protocols running across the access network and is shown in Figure 20-14. - -![Figure 20-14: L2 / L3 service layout for scenario 4. This diagram shows the network architecture for scenario 4. On the left, O-DU and RRU units are connected to a Cell Site Router (CSR). The O-DU connects to three VPN tunnels: Open fronthaul management plane (L3VPN), Midhaul/Backhaul Control Plane (L3VPN), and Midhaul/Backhaul user Plane (L3VPN). The RRU connects via a RoE mapper to the CSR. The CSR connects to a Hub Site Router (HSR) which is part of the BBU. The BBU connects to the Aggregation network, which includes a 5GC and a UPF. The Aggregation network interfaces with the Midhaul/Backhaul via VLANs or discrete Ethernet Interfaces. The Backhaul CP interface connects the 5GC to the Aggregation network. The 7.2X C/U plane via EVPN VPWS is shown between the O-DU and the HSR. The RoE/7.2X via L2 EVPN VPWS is shown between the RRU and the HSR. The CPRI interface is shown between the RRU and the BBU.](17e0c0ae0c4cb562e192cbde7642a209_img.jpg) - -Figure 20-14: L2 / L3 service layout for scenario 4. This diagram shows the network architecture for scenario 4. On the left, O-DU and RRU units are connected to a Cell Site Router (CSR). The O-DU connects to three VPN tunnels: Open fronthaul management plane (L3VPN), Midhaul/Backhaul Control Plane (L3VPN), and Midhaul/Backhaul user Plane (L3VPN). The RRU connects via a RoE mapper to the CSR. The CSR connects to a Hub Site Router (HSR) which is part of the BBU. The BBU connects to the Aggregation network, which includes a 5GC and a UPF. The Aggregation network interfaces with the Midhaul/Backhaul via VLANs or discrete Ethernet Interfaces. The Backhaul CP interface connects the 5GC to the Aggregation network. The 7.2X C/U plane via EVPN VPWS is shown between the O-DU and the HSR. The RoE/7.2X via L2 EVPN VPWS is shown between the RRU and the HSR. The CPRI interface is shown between the RRU and the BBU. - -Figure 20-14: L2 / L3 service layout for scenario 4 - -11 -12 -13 -14 -15 -16 - -Notes on the design: - -- 1. O-RAN 7.2x C/U plane and non O-RAN Fronthaul packet traffic (between RoE mappers) use VPWS EVPN services. - -![O-RAN Alliance logo](abf48594fdb5b54bb90df7ec9359efd9_img.jpg) - -O-RAN Alliance logo - -2. The expectation is both the O-RAN 7.2x C/U plane traffic and the non O-RAN Fronthaul traffic will have similar delay and jitter characteristics so will run in the same traffic class which is priority queued. -3. The vendor of the RoE mapper function will need to provide details of traffic rates and whether they are fixed or vary depending on user data. The network planner will need to take this into account when capacity planning the access links between the CSR and the HSR. - -## 20.9 Scenario 6 5G C-RAN with distributed UPF - -Scenario 6 includes the insertion of distributed UPFs in the architecture. The solution is illustrated in Figure 20-15 and is easily to achieve by simply connecting the distributed UPF to the Midhaul/Backhaul control and user plane L3VPN. All necessary transport routing will occur automatically through the L3VPN control plane. - -![Figure 20-15: L2 / L3 service layout for scenario 6. The diagram shows a network architecture with two O-RU units connected to a Cell Site Router (CSR). The CSR is connected to an O-DU and an O-CU. The O-DU and O-CU are connected to a Hub Site Router (HSR). The HSR is connected to two UPF units and a 5GC unit. The diagram illustrates various network planes: L2 EVPN VPWS for 7.2X C/U Plane, Open fronthaul management plane (L3VPN), Midhaul/Backhaul Control Plane (L3VPN), and Midhaul/Backhaul user Plane (L3VPN). The diagram is divided into Access and Aggregation sections. The Aggregation section includes the HSR, UPFs, and the 5GC. The Access section includes the O-RUs, CSR, O-DU, and O-CU. The HSR is connected to the UPFs via Midhaul / Backhaul interfaces with VLANs or discrete Ethernet Interfaces. The O-DU and O-CU are connected to the HSR via Fronthaul interfaces with VLANs or discrete Ethernet interfaces. The 5GC is connected to the HSR via a Backhaul CP interface.](04238bd6d89845c9012e10d19d0e2b1f_img.jpg) - -Figure 20-15: L2 / L3 service layout for scenario 6. The diagram shows a network architecture with two O-RU units connected to a Cell Site Router (CSR). The CSR is connected to an O-DU and an O-CU. The O-DU and O-CU are connected to a Hub Site Router (HSR). The HSR is connected to two UPF units and a 5GC unit. The diagram illustrates various network planes: L2 EVPN VPWS for 7.2X C/U Plane, Open fronthaul management plane (L3VPN), Midhaul/Backhaul Control Plane (L3VPN), and Midhaul/Backhaul user Plane (L3VPN). The diagram is divided into Access and Aggregation sections. The Aggregation section includes the HSR, UPFs, and the 5GC. The Access section includes the O-RUs, CSR, O-DU, and O-CU. The HSR is connected to the UPFs via Midhaul / Backhaul interfaces with VLANs or discrete Ethernet Interfaces. The O-DU and O-CU are connected to the HSR via Fronthaul interfaces with VLANs or discrete Ethernet interfaces. The 5GC is connected to the HSR via a Backhaul CP interface. - -Figure 20-15: L2 / L3 service layout for scenario 6 - -## 20.10 Scenario 7 Slicing - -This section has been removed because WG-1 is now developing the overall slice architecture and use cases [25] for the whole of the O-RAN organization. The WG-1 slicing task force is developing the slicing solution in phases over multiple O-RAN releases. The packet switched architecture has an extensive set of capabilities to support transport level slicing which are outlined in section 17. As the slice use cases are going to rapidly evolve based on WG-1 slice use cases, slicing scenario have been moved to Annex F where solution examples are presented. - -![O-RAN Alliance logo](3d03999e085fe4b9fdcb93dfbcb55218_img.jpg) - -The O-RAN Alliance logo, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -# 21 Applicability of IETF Computing-Aware Traffic Steering (CATS) to O-RAN Scenarios - -## 21.1 Introduction - -Efficient coordination in O-RAN across the fronthaul, midhaul, and backhaul segments is essential to meet the demanding requirements of 5G and future systems, particularly in terms of latency, bandwidth, and resource efficiency. - -The IETF Computing-Aware Traffic Steering (CATS) framework [180] provides a systematic approach to traffic steering that jointly considers both computing and network metrics to take the steering decisions towards different instances of a functional entity (e.g., CU-UP). This capability aligns closely with the needs of O-RAN deployments, where traffic could be dynamically distributed across diverse infrastructure resources to optimize service performance. - -This section describes the applicability of the IETF CATS framework in O-RAN scenarios, with focus on both the midhaul segment and the D2 interface, where the potential for the flexibility offered by CATS is especially of interest. - -The steering decisions will be based on metrics collected in both the network substrate, according to the status observed in the Xhaul transport, but also based on the compute environment, hosting the O-RAN functional entities running the disaggregated radio processing stack. The hierarchical organization of metrics proposed in CATS supports scalable and flexible decision-making. - -CATS components can be integrated with O-RAN management entities such as the Service Management and Orchestration (SMO) framework, O-Cloud, and Transport Network Management (TNM). By articulating these interactions, this section aims to illustrate how CATS principles can enhance end-to-end orchestration and enable adaptive traffic steering strategies that can be critical for the continued evolution of O-RAN architectures. - -## 21.2 Overview of the CATS Framework - -### 21.2.1 Introduction to CATS - -Computing-Aware Traffic Steering (CATS) is a traffic engineering approach developed by the IETF that optimizes traffic forwarding decisions by considering both computing and network resource metrics. It aims to dynamically steer traffic to the most appropriate service instance based on real-time resource availability and network conditions, thus improving overall service performance and resource utilization. - -### 21.2.2 Key components of CATS - -The CATS framework [180] introduces several functional components that interact to enable computing-aware traffic steering: - -- **CATS Service Metric Agent (C-SMA):** Collects metrics related to compute resources such as CPU utilization, memory usage, and service load at service instances. - -![O-RAN Alliance logo](7d2c50f88ff6fac5f6d6af3dd39e1074_img.jpg) - -The logo for the O-RAN Alliance, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -- **CATS Network Metric Agent (C-NMA):** Gathers network performance metrics like bandwidth, latency, and reliability from the underlying transport network. -- **CATS Path Selector (C-PS):** Central or distributed decision entity that selects the optimal path and service contact instance based on collected metrics. -- **CATS Traffic Classifier (C-TC):** Classifies incoming traffic flows based on service identifiers and forwards them along CATS-computed paths. -- **CATS-Forwarders:** Network nodes that enforce the steering decisions by forwarding traffic towards selected service contact instances. - -### 21.2.3 Architectural planes - -The framework operates across three logical planes: - -- **Management Plane:** Responsible for configuration, monitoring, and maintenance of CATS components. -- **Control Plane:** Executes path selection algorithms considering compute and network metrics. -- **Data Plane:** Handles actual packet forwarding according to the control plane decisions. - -Together, these components enable a flexible overlay framework that can dynamically adapt traffic flows to service and network conditions. - -## 21.3 Insights on CATS Metric Creation for Steering Decisions - -### 21.3.1 Importance of metrics - -Metrics form the foundation of effective traffic steering in CATS. They provide quantitative information about the current state of computing and networking resources, which the C-PS utilizes to select the optimal service contact instance and network path. - -### 21.3.2 Metric Levels and Types - -To balance scalability and accuracy, CATS metrics [181] are defined at three abstraction levels: - -- **Level 0 (L0) - Raw Metrics:** Detailed, unprocessed data such as CPU frequency (GHz), memory utilization (%), network throughput (Mbps), and delay (microseconds). These metrics carry units and are solution specific. -- **Level 1 (L1) - Normalized Metrics:** Aggregated and normalized metrics within categories (compute, communication, composed). For example, a normalized compute metric may aggregate CPU, memory, and storage metrics into a single score scaled between 0 and 10. -- **Level 2 (L2) - Fully Normalized Metric:** A single normalized score that combines all lower-level metrics to represent the overall capability or suitability of a service instance. - -![O-RAN Alliance logo](35bdae77185f296854f8406f6a3f7439_img.jpg) - -O-RAN Alliance logo - -This hierarchical approach allows implementations to trade-off complexity and overhead against decision agility and accuracy. - -### 21.3.3 Metric Fields and Representation - -Metrics are represented with fields defining their type, format, units, source (nominal, measured, estimated, normalized, aggregated), statistic (mean, max, min, current), and value. For example: - -- **Metric Type:** compute\_CPU\_frequency -- **Level:** L0 -- **Format:** Float -- **Unit:** GHz -- **Value:** 2.2 - -Such structured representation facilitates interoperability and extensibility. - -### 21.3.4 Metric Distribution and Update Frequency - -Metrics can be distributed using centralized, distributed, or hybrid models. Frequent updates (especially for compute metrics) require careful management to avoid overwhelming control planes or routing protocols. Techniques like aggregation, threshold-triggered updates, and normalization help maintain scalability. - -## 21.4 Applicability of CATS to Midhaul - -### 21.4.1 O-RAN Midhaul overview - -In O-RAN architecture, the midhaul network connects Distributed Units (DUs) and Centralized Units (CUs), specifically between DU and CU User Plane (CU-UP). The midhaul segment typically uses an IP/MPLS aggregation network managed by Transport Network Elements (TNEs) under a Transport Network Manager (TNM). - -### 21.4.2 Dynamic Association of DU and CU - -While the fronthaul connection between RUs and DUs tends to be static, the midhaul association between DUs and CUs can be dynamic, influenced by runtime conditions such as CU load, energy efficiency, or workload migration. - -### 21.4.3 Role of CATS in Midhaul - -CATS provides a framework to enhance midhaul traffic steering by considering both: - -- **Compute Metrics:** CPU, memory utilization, or service load of DU and CU-UP instances. -- **Network Metrics:** Bandwidth, latency, and reliability of paths between DU and CU, or between DUs. - -The entire DU traffic (user plane) is steered to a selected CU-UP instance (or to another DU instance in the case of D2 interface), since the payload is a pre-processed analog radio signal that cannot be easily split into individual flows. - -![O-RAN Alliance logo](6b6d27ae1c0c8c9bebfdc07af29d3d1e_img.jpg) - -O-RAN Alliance logo - -#### 21.4.4 CATS components in Midhaul context - -- **CATS-Forwarders:** The TNEs act as CATS-Forwarders enforcing steering decisions. -- **C-SMA:** Collects compute metrics from CU-UP instances deployed across different data centers. -- **C-NMA:** Monitors midhaul network performance metrics. -- **C-PS:** It could be integrated as part of the TNM or in the O-RAN SMO, and selects the optimal DU or CU-UP instance to where steer the traffic based on combined metrics. - -#### 21.4.5 Connectivity Realization - -The midhaul connectivity can leverage IETF Network Slice Services to create hub-and-spoke VPNs from the DU to multiple CU-UP instances or among DU instances in the case of D2 interface. CATS can use as service match criteria at the time of enforcing the IETF Network Slice Service the destination IP of the targeted instance (i.e., either CU-UP or DU) to enforce traffic steering via the network slice. - -### 21.5 Applicability of CATS to D2 interface - -Similarly to the midhaul case, dynamicity can be found as well in the support of D2 interface for the interconnection of DU instances along time. As in the previous case, CATS can provide a framework to enhance D2 interface traffic steering by taking into account metrics of the network connecting the DU instances and the ones from the compute substrate hosting them. As before, the CATS components can play a similar role, and the connectivity can be realized in the same manner. - -### 21.6 Interaction Between O-RAN Components and IETF CATS Components - -#### 21.6.1 Mapping CATS Components to O-RAN - -The O-RAN management architecture is composed by three major components relevant for the integration of CATS: - -- **Service and Management Orchestrator (SMO):** Manages RAN domain including DUs and CUs. -- **O-Cloud:** Manages cloud infrastructure metrics, such as compute resource utilization. -- **Transport Network Manager (TNM):** Controls and manages Transport Network Elements (TNEs) and underlay transport network. - -Thus, when mapping functional behavior of CATS framework for integration with O-RAN, the following approach could be followed: - -- **C-SMA:** Maps to O-Cloud functionality, providing compute and service metrics. -- **C-NMA:** Resides within TNM or TNE, providing network metrics. -- **C-PS:** Could be part of SMO or either TNM, and is responsible for path selection. Implications on different approaches (i.e., SMO-centric or TNM-centric) should be analyzed. -- **CATS-Forwarders:** Implemented by TNEs in the midhaul network. - -![O-RAN Alliance logo](80ccc3e44bb7682a94bf1c000e904e61_img.jpg) - -The O-RAN Alliance logo, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -## 21.6.2 Control Plane Interactions - -Two main interaction models exist: - -- **SMO-centric:** SMO collects compute metrics from O-Cloud and network metrics from TNM, performs path selection (C-PS), and instructs TNM for traffic steering. -- **TNM-centric:** TNM obtains compute metrics from SMO/O-Cloud, performs path selection, and enforces steering independently. - -Both models require well-defined interfaces between SMO and TNM. - -## 21.6.3 Integration with IETF Network Slice Service - -O-RAN connectivity both at midhaul and D2 interface can be realized using IETF Network Slice Services, which provide flexible, policy-driven slice creation and management. CATS enhances this by dynamically selecting the appropriate slice (e.g., VPN instance) for a DU-to-CU (or DU-to-DU) connection based on compute and network metrics. - ---- - -# 22 Annex A: Overview of “Segment Routing” (SR) - -This annex gives an overview of segment routing based on the Segment Routing Architecture defined in RFC8402 [141] and related drafts. It has been included as an annex because the main document describes two architecture/designs that utilise Segment Routing: SR-MPLS and SR for IPv6 or SRv6. There are differences between the two implementations and capabilities of SR when using an MPLS and IPv6 data plane but there are also many similarities in the basic architectural concepts and the motivation for using the technology. Consequently, this annex describes the basic SR architecture and the “logical architecture sections” in the main document goes into more detail on the technologies and outlines implementation and design considerations when using the respective technologies. - -This annex utilises many different information sources and, in some instances, takes content very literally from these sources. Information sources include IETF documents, research and vendor documents. - -## Background - -The Internet and role of packet switching has changed over the last couple of decades and continues to evolve rapidly. This is no better illustrated than by the 5G transport requirements which anticipates billions of endpoints, massive numbers of antenna, huge bandwidths and the ability to concurrently support different 5G services. This evolution is challenging existing Internet protocols, equipment and increasing the operational complexity of the network. Segment Routing and related technology evolutions aims to address these challenges through protocol simplification, removal of state from the network and embracing technology advances such as Software Defined Networking. - -## Segment Routing - -Segment Routing (SR) is based on the loose Source Routing concept. A node can include an ordered list of instructions in the packet headers. These instructions steer the forwarding and the processing of the packet along its path in the network. Single instructions are called segments, a sequence of instructions is called a segment list or an SR Policy. Each segment can enforce a - -1 topological requirement (e.g. pass through a node or an interface) or a service requirement (e.g. - 2 execute an operation on the packet). The term segment refers to the fact that a network path towards - 3 a destination can be split in segments by adding intermediate waypoints. The segment list can be - 4 included by the original source of the packet or by an intermediate node. When the segment list is - 5 inserted by an intermediate node, it can be removed by another node along the path of the packet, - 6 supporting the concept of *tunneling* through an *SR domain* from an *ingress* node to an *egress* node. - 7 The implementation of the Segment Routing Architecture requires a data plane which is able to - 8 carry the segment lists in the packet headers and to properly process them. Control plane operations - 9 complement the data plane functionality, allowing segment allocation (i.e. associate a segment - 10 identifier to a specific instruction in a node) and distribution of segment identifiers within an SR - 11 domain. - -![Figure 22-1: Segment Routing protocol stack and path capabilities. The diagram shows a network topology with six nodes. A 'Dynamic path' is shown as a green curved arrow from the ingress node to the egress node. An 'Explicit path' is shown as an orange curved arrow from the ingress node to the egress node. Above the nodes, a legend indicates 'Path expressed in the packet' (grey box) and 'Data' (grey box). To the right, a protocol stack diagram is shown. The 'Control Plane' includes 'Routing protocols with extensions (IS-IS, OSPF, BGP)' and 'SDN controller'. The 'Data Plane' includes 'MPLS (segment labels)' and 'IPv6 (+SR header)'. Below the data plane, 'Paths options' are listed: 'Dynamic (SPF computation)' and 'Explicit (expressed in the packet)'.](0f666d2ebbad7fab84c7c4fb531ea932_img.jpg) - -Figure 22-1: Segment Routing protocol stack and path capabilities. The diagram shows a network topology with six nodes. A 'Dynamic path' is shown as a green curved arrow from the ingress node to the egress node. An 'Explicit path' is shown as an orange curved arrow from the ingress node to the egress node. Above the nodes, a legend indicates 'Path expressed in the packet' (grey box) and 'Data' (grey box). To the right, a protocol stack diagram is shown. The 'Control Plane' includes 'Routing protocols with extensions (IS-IS, OSPF, BGP)' and 'SDN controller'. The 'Data Plane' includes 'MPLS (segment labels)' and 'IPv6 (+SR header)'. Below the data plane, 'Paths options' are listed: 'Dynamic (SPF computation)' and 'Explicit (expressed in the packet)'. - -14 **Figure 22-1: Segment Routing protocol stack and path capabilities** - -## 16 Segment Routing architectural principle - -17 There is a single SR architecture which is defined in RFC8402 [141]. This defines the general - 18 concepts of SR and is independent from the specific data plane. Currently, there are two - 19 instantiations of the SR architecture designed and implemented in production code, SR over MPLS - 20 (SR-MPLS) and SR over IPv6 (SRv6). - -21 - 22 The architecture relies on segments identifiers (SIDs) and SID lists. The SID represents a single - 23 instruction which can be related to how the packet is forwarded or a function that needs to be - 24 performed on a packet. A SID lists or the SR policy is a collection of SIDs or instructions to be - 25 performed on the packet as it traverses the SR domain. Typically, a SID list is imposed on the - 26 packets as it enters the SR domain and is either empty or completed by the time it leaves an SR - 27 domain. - -28 There are two basic types of segment, global segments which correspond to instructions that are - 29 globally valid in an SR domain and local segments which correspond to instructions that are only - 30 valid within a single node. Some of the key segment types are: - -- 31 1. IGP Prefix and IGP node segments: These are global SIDs and are instructions on how to - 32 forward a packet towards a destination IP network or destination IP node. As the name - 33 suggests these are conveyed by IGP and can be used by any node in the SR domain to send - 34 traffic to a node or IP prefix. -- 35 2. Adjacency segments: These are local SIDs which identify the links available on that node. - -![O-RAN Alliance logo](d41b7d532c3b6df53d42863e7c50b9f3_img.jpg) - -O-RAN Alliance logo - -3. Anycast segments: These are a special IGP-prefix segment that corresponds to an anycast prefix. ie a prefix advertised by more than one router. Anycast and anycast segments are commonly used to provide high availability or load balancing solutions. -4. Binding Segments: These are a single SID that is associated with a segment list or SR policy. This means the node that processes the Binding SID replaces the single segment with a segment list. - -Using Figure 22-1 as an example, the basic SR architecture can support: - -1. A dynamically locally computed forwarding path between an ingress and egress point within the SR domain by the ingress node either imposing the node SID of the egress node or the prefix SID of the destination prefix. Typically, a link-state IGP or an EGP routing protocol, running locally on the routers calculate these types of paths and they exhibit the behaviour of normal routing protocols such “Shortest Path Forwarding” and “Equal Cost Multi Pathing (ECMP) -2. A fully deterministic path between the ingress and egress points. In this case the SR policy or SID list includes all nodes on the path and if required adjacency SIDs to select links between nodes. -3. A combination of the two. The SR architecture can build a path between an ingress and egress node that combines dynamically computed forwarding and explicitly routed forwarding. - -## Segment Routing data plane - -Two data plane instantiations are designed and implement: SR over MPLS (SR-MPLS) and SR over IPv6 (SRv6). - -### SR-MPLS - -The MPLS data plane (SR-MPLS) is specified in RFC 8660 “Segment Routing with MPLS data plane”[148], In the case of SR-MPLS, Segment Routing does not require any change to the MPLS forwarding plane. An SR Policy is instantiated through the MPLS Label Stack and the Segment IDs (SIDs) of a Segment List are inserted as MPLS Labels. The classical forwarding functions available for MPLS networks allow implementing the SR operations. - -### IPv6 data plane (SRv6) - -For the IPv6 data plane (SRv6), a new type of IPv6 Routing Extension Header, called Segment Routing Header (SRH) has been defined in RFC 8754 IPv6 Segment Routing Header (SRH) [153]. The SRH contains the Segment List (SR Policy) as an ordered list of IPv6 addresses: each address in the list is a SID. A dedicated field, referred to as *Segments Left*, is used to maintain the pointer to the active SID of the Segment List. This SRH format and basic operation of the SRH is illustrated in Figure 22-2. - -![O-RAN Alliance logo](a9b24297dc6417e733ccbe4ed6505eac_img.jpg) - -O-RAN Alliance logo - -![SRH header structure diagram and bit layout. The left side shows a stack: IPv6 header, TAG, Segments Left, Locator 1/Function 1, Locator 2/Function 2, Locator 3/Function 3, and Metadata TLV. An orange arrow points from Segments Left to the Locator/Function pairs. The right side shows the bit layout: Next Header, Hdr Ext Len, Routing Type, Segments Left, Last Entry, Flags, Tag, Segment List[0] (128 bits IPv6 address), ..., Segment List[n] (128 bits IPv6 address), and Optional Type Length Value objects (variable).](662c84f65e27aff9b64ec351f9d8cca8_img.jpg) - -SRH header structure diagram and bit layout. The left side shows a stack: IPv6 header, TAG, Segments Left, Locator 1/Function 1, Locator 2/Function 2, Locator 3/Function 3, and Metadata TLV. An orange arrow points from Segments Left to the Locator/Function pairs. The right side shows the bit layout: Next Header, Hdr Ext Len, Routing Type, Segments Left, Last Entry, Flags, Tag, Segment List[0] (128 bits IPv6 address), ..., Segment List[n] (128 bits IPv6 address), and Optional Type Length Value objects (variable). - -Figure 22-2 SRH header and interaction between segments left and SID list - -To explain the SRv6 data plane, there are three categories of nodes: Source SR nodes, Transit nodes and SR Segment Endpoint nodes. A Source SR node corresponds to the *headend* node, it can be a host originating an IPv6 packet, or an SR domain ingress router encapsulating a received packet in an outer IPv6 header. - -![Network topology diagram showing nodes 1, 2, 3, 4, and 5. Node 1 is connected to 2, 3, 4, and 5. Node 2 is connected to 3. Node 3 is connected to 5. Node 4 is connected to 5. A dashed box encloses nodes 1, 2, 3, 4, and 5. Below the diagram, four packet structures are shown: 1. IPv4 SA=A.A.A.A, DA=B.B.B.B; 2. IPv6 SA=A::1, DA=B:0:0:2:C3::, SR (B:0:0:5:DB::) SL=1, IPv4 SA=A.A.A.A, DA=B.B.B.B; 3. IPv6 SA=A::1, DA=B:0:0:5:DB::, IPv4 SA=A.A.A.A, DA=B.B.B.B; 4. IPv4 SA=A.A.A.A, DA=B.B.B.B.](a9042d8edc99d26ea117a7d56e171d8e_img.jpg) - -Network topology diagram showing nodes 1, 2, 3, 4, and 5. Node 1 is connected to 2, 3, 4, and 5. Node 2 is connected to 3. Node 3 is connected to 5. Node 4 is connected to 5. A dashed box encloses nodes 1, 2, 3, 4, and 5. Below the diagram, four packet structures are shown: 1. IPv4 SA=A.A.A.A, DA=B.B.B.B; 2. IPv6 SA=A::1, DA=B:0:0:2:C3::, SR (B:0:0:5:DB::) SL=1, IPv4 SA=A.A.A.A, DA=B.B.B.B; 3. IPv6 SA=A::1, DA=B:0:0:5:DB::, IPv4 SA=A.A.A.A, DA=B.B.B.B; 4. IPv4 SA=A.A.A.A, DA=B.B.B.B. - -Figure 22-3 Packet and SRH construct for IPv4 payload for traffic following nodes 1,2,5 - -In Figure 22-3, which considers the latter case the source SR node (S1) is an edge router that encapsulates a packet (which can be IPv6, IPv4 or an Layer 2 frame) into an outer IPv6 packet and inserts the SR Header (SRH) as a Routing Extension Header in the outer IPv6 header. The traffic is destined for S5 and for policy reasons the operator wishes to send the traffic via S2 and S3 which is not the shortest IGP path. To implement this policy, a segment list is composed of S2 and S5. S3 does not need to be specified because the shortest path from S2 to S5 is via S3. To implement this SR policy and assuming the use of a reduced SRH (for details see RFC8754[148]) the packet details are shown in Figure 22-3. - -![O-RAN Alliance logo](6240cc0a7da4e8cbe8f5f9541de3d4fe_img.jpg) - -O-RAN Alliance logo - -1 In addition to the basic operations, the *SRv6 Network Programming* model [156] describes a set of - 2 functions that can be associated to segments and executed in a given SRv6 node. Examples of such - 3 functions are: different types of packet encapsulation (e.g. IPv6 in IPv6, IPv4 in IPv6, Ethernet in - 4 IPv6), corresponding decapsulation, lookup operation on a specific routing table (e.g. to support - 5 VPNs). The list of functions described in [156] is not meant to be exhaustive, as any function can be - 6 associated to a segment identifier in a node. Obviously, the definition of a standardized set of - 7 segment routing functions facilitates the deployment of SR domains with interoperable equipment - 8 from multiple vendors. - -## 9 Segment Routing control plane - -10 The control plane is responsible for calculating, building the connectivity graphs and implementing - 11 the SR policies within the network. Segment Routing can support distributed, centralised or hybrid - 12 control plane architectures. See Figure 22-4 for more details. - -![Figure 22-4: Distributed, centralised and hybrid control planes. The diagram shows three network architectures: Traditional Control Plane Architecture (Distributed), Hybrid Control Plane Architecture, and SDN Control Plane Architecture (Centralized). Each architecture shows a network of nodes (Data Plane) and control plane elements (Distributed or Centralized) interacting via APIs. A legend identifies the components: Application (red), Distributed Control Plane (green), Centralized Control Plane (yellow), Data Plane (blue), and APIs (dashed green lines).](9af97997b7d3fbca90b8ddba0ea39c6c_img.jpg) - -13 - -The diagram illustrates three network architectures for Segment Routing control planes: - -- Traditional Control Plane Architecture (Distributed):** Shows a network of nodes (Data Plane) with control plane elements (Distributed Control Plane) distributed across them. The control plane elements are represented by green cylinders, and the data plane by blue cylinders. Red cylinders represent applications. Dashed green lines represent APIs. -- Hybrid Control Plane Architecture:** Shows a network of nodes (Data Plane) with a mix of distributed and centralized control plane elements. A yellow cylinder represents the centralized control plane, and green cylinders represent the distributed control plane. Red cylinders represent applications. Dashed green lines represent APIs. -- SDN Control Plane Architecture (Centralized):** Shows a network of nodes (Data Plane) with a single centralized control plane element (yellow cylinder). Red cylinders represent applications. Dashed green lines represent APIs. - -Legend: - -- Application (red cylinder) -- Distributed Control Plane (green cylinder) -- Centralized Control Plane (yellow cylinder) -- Data Plane (blue cylinder) -- APIs (dashed green lines) - -Figure 22-4: Distributed, centralised and hybrid control planes. The diagram shows three network architectures: Traditional Control Plane Architecture (Distributed), Hybrid Control Plane Architecture, and SDN Control Plane Architecture (Centralized). Each architecture shows a network of nodes (Data Plane) and control plane elements (Distributed or Centralized) interacting via APIs. A legend identifies the components: Application (red), Distributed Control Plane (green), Centralized Control Plane (yellow), Data Plane (blue), and APIs (dashed green lines). - -14 -15 **Figure 22-4 Distributed, centralised and hybrid control planes** - -16 -17 In a distributed control plane environment, the transport nodes independently interact with each - 18 other to convey routing information and independently make decisions to set-up and enforce SR - 19 policies. This is achieved through a combination of IGP and EGP protocols running between the - 20 transport nodes. - -21 In a centralised control plane environment, central SDN controllers have full knowledge of the - 22 network topology and calculates SR policies centrally. These are then programmed onto the TNEs - 23 in the network. - -24 The hybrid approach splits the responsibilities, the TNEs in the network support some functions, - 25 such as building the link state database, calculating the intra-domain routing tables, monitoring the - 26 links to attached nodes, and rapidly recovering in the event of failure. At the same time the central - 27 SDN controllers has a feed from the network and is used for functions that require a network wide - 28 view such as transport optimization and inter-domain routing. - -## 30 MPLS-SR distributed control plane - -31 The MPLS-SR distributed control plane utilises ISIS or OSPF routing protocols with extensions to - 32 advertise the different types of IGP segments (prefix, node, adjacency, any cast) between TNEs. - -![O-RAN Alliance logo](64bc20572e786c96baee9996e0c52ab2_img.jpg) - -O-RAN Alliance logo - -## 1 IPv6 distributed control plane - -2 For the IPv6 data plane, the process of advertising the IGP-prefix, IGP-node and IGP-anycast - 3 segments is simplified due to the use of IPv6 addresses as SIDs. In particular, there is no need to - 4 extend the IGP routing protocols to distribute these segment types, because they are IPv6 prefixes - 5 natively distributed by the routing protocols. This means that the Control Plane for SRv6 can use - 6 the regular IPv6 link state IGP routing protocols (OSPFv3, ISIS) to support the basic operations, - 7 while extensions are still needed ([151][152]) to distribute IGP-Adjacency segments and other SR - 8 configuration information. - -## 9 Centralised control plane - -10 Although much emphasis has been made of fully centralised control plane models in academia for - 11 path computation, they have not made their ways into production large scale WAN designs due to - 12 the distributed nature of the transport nodes and the need for the transport nodes to communicate at - 13 all times with the central controller. As a consequence, most WAN SDN designs today are hybrid in - 14 nature, where intelligence is split between the TNEs and central SDN controllers. - -15 - 16 Note: This discussion above only considers path computation element of a central controller. There - 17 are many aspects of a central SDN controller including orchestration, data analytics etc. - -## 18 Hybrid control plane - -19 The hybrid control plane is combination of distributed control plane and centralised SDN control - 20 plane functionality. Like the central control plane model there is no universal architecture for a - 21 hybrid control plane design, other than some functions are provided centrally and others occur - 22 locally on the TNEs. One of the most common hybrid control plane designs is where the central - 23 SDN controllers provides a “Path Computation Element” capability. In this model the PCE is - 24 responsible for path computation and inter-domain routing with the distributed control planes - 25 running on the TNEs, responsible for building the link state database, calculating the network graph - 26 and building the shortest path forwarding tables. In this scenario there is generally a tight - 27 relationship between the two components. - -- 28 - 29 A. The TNEs exchange topology information, creates the link-state database and computes the - 30 shortest path forwarding tables. - 31 B. The centralised control plane component needs to get visibility of the distributed protocol's - 32 link-state database to understand the current topology. Some of the common approaches are: - 33 a. The SDN controller participates in the IGP and as a consequence builds its own link- - 34 state database and network graph. - 35 b. The SDN controller extracts IGP databases from the network using proprietary - 36 mechanisms. - 37 c. BGP-LS (BGP link state) runs between one or more TNEs and centralised - 38 controllers. In this way the centralised controller gets visibility of the network - 39 through BGP-LS. - 40 C. In many instances the centralised control plane needs to gather other information about the - 41 network, for example link loading. Currently, there is no single standard for collecting this - 42 information. Common mechanisms include SNMP, telemetry feeds and operational data from - 43 Yang models residing on the devices. - 44 - 45 D. The central controller and the TNEs also need to communicate when, either a TNE requests a - 46 service from the central SDN controller, or the central SDN controller wants to push an explicit - -![O-RAN Alliance logo](01c8a7aebdecdae1e64430198a8e4b8c_img.jpg) - -O-RAN Alliance logo - -policy to a TNE. An example would be if a TNE needs build an SR policy and wants to use the services of a PCE. The transport node and the PCE need to communicate, some of the common protocols used for this type of communications include: - -- a. Network Configuration Protocol -- b. PCE (PCEP) -- c. BGP -- d. Openflow (SR-MPLS) - -## 23 Annex B: IETF Ethernet Virtual Private Networks - -IETF Ethernet Virtual Private Network (EVPN) is a service supporting transportation of Ethernet frames across a transport network encapsulated in MPLS or IP. There are multiple flavors of IETF EVPN service as outlined Table 6. - -| Service Type | | | Standardization status | -|--------------|---------------|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Layer 2 VPN | E-LAN | VLAN-based | RFC 7432 [123]: BGP MPLS-Based Ethernet VPN | -| | | VLAN-bundle | | -| | | VLAN-aware bundle | | -| | E-Tree | VLAN-based | RFC 8317[137] : Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN) | -| | | VLAN-bundle | | -| | | VLAN-aware bundle | | -| | E-Line (VPWS) | VLAN-based | RFC 8214 [131]: Virtual Private Wire Service Support in Ethernet VPN
RFC 9744 [174]: EVPN Virtual Private Wire Service (VPWS) Flexible Cross-Connect (FXC) Service | -| | | VLAN-bundle | | -| | Layer 3 VPN | | RFC 9136 [158]: IP Prefix Advertisement in Ethernet VPN (EVPN) | - -**Table 6: EVPN service classification** - -The two major building blocks of EVPN are: - -- Control plane, based on Border Gateway Protocol (BGP), to distribute all necessary information required for proper EVPN operation -- Data plane, with different underlay transport options, to suit various requirements: - - MPLS (LDP, RSVP, BGP-LU, MPLSoUDP, SR, SR-TE) - - IP (VxLAN, SRv6) - -### EVPN E-LAN service - -EVPN E-LAN service is a Layer 2 multipoint-to-multipoint service. In essence, EVPN E-LAN emulates Layer 2 switch behavior, with attachment circuits (ACs) of this single emulated Layer 2 switch present on multiple Provider Edge (PE) routers, which are placed in different network locations, as outlined in Figure 23-1 - -![Diagram of EVPN E-LAN service showing two network states. The top state shows four Customer Edge (CE) devices (CE1, CE2, CE3, CE4) connected to four Provider Edge (PE) devices (PE1, PE2, PE3, PE4) which are part of a central EVPN instance. BGP signaling is shown between the PEs. The bottom state shows the same CE devices connected to a central switching hub where traffic is being forwarded between them, indicated by yellow and black arrows.](aadbdbdbe20c27e20e40cc56c1b8ee9c_img.jpg) - -Diagram of EVPN E-LAN service showing two network states. The top state shows four Customer Edge (CE) devices (CE1, CE2, CE3, CE4) connected to four Provider Edge (PE) devices (PE1, PE2, PE3, PE4) which are part of a central EVPN instance. BGP signaling is shown between the PEs. The bottom state shows the same CE devices connected to a central switching hub where traffic is being forwarded between them, indicated by yellow and black arrows. - -Figure 23-1: EVPN E-LAN service - -Similar to ordinary Layer-2/Layer-3 switch, EVPN E-LAN service provides - -- MAC learning capability (globally or per VLAN) -- capability to carry Ethernet frames without VLAN tag, as well as with single or double VLAN tags, including VLAN translation -- single-homed, as well as multi-homed (both single-active and all-active) attachment circuits capability -- BUM optimization mechanisms (like for example APR proxy/suppression, IGMP proxy, etc.) -- handover to Layer-3 domain via integrated routing and bridging (IRB) operation and more. - -EVPN E-Tree service - -EVPN E-Tree service is an enhancement of EVPN E-LAN service, which allows to restrict certain communication patterns, creating in essence a point-to-multipoint service model. As outlined in Figure 23-2, each attachment circuit is designated as *root* (R) or *leaf* (L). As per EVPN E-Tree definition, only *root* $\leftrightarrow$ *root* and *root* $\leftrightarrow$ *leaf* Layer 2 communication is permitted, while *leaf* $\leftrightarrow$ *leaf* Layer 2 communication is blocked. - -![O-RAN Alliance logo](97c84277db020d4b9a9c3da9757baeea_img.jpg) - -O-RAN Alliance logo - -![Diagram of EVPN E-Tree services showing two network states. The top state shows four Customer Edge (CE) devices (CE1, CE2, CE3, CE4) connected to Provider Edge (PE) devices (PE1, PE2, PE3, PE4) within a central cloud. PE1 and PE3 are designated as 'Root' (R), while PE2 and PE4 are 'Leaf' (L). BGP messages are shown between the PEs. The bottom state shows the same network with yellow arrows indicating traffic flow: traffic from CE1 and CE2 is sent to PE1 (Root), which then replicates it to PE3 (Root) and PE2 (Leaf). PE3 (Root) then delivers it to CE3 and CE4. PE2 (Leaf) does not forward traffic to other CEs.](d455e47a6d660a3cc29a125a2cbe355b_img.jpg) - -Diagram of EVPN E-Tree services showing two network states. The top state shows four Customer Edge (CE) devices (CE1, CE2, CE3, CE4) connected to Provider Edge (PE) devices (PE1, PE2, PE3, PE4) within a central cloud. PE1 and PE3 are designated as 'Root' (R), while PE2 and PE4 are 'Leaf' (L). BGP messages are shown between the PEs. The bottom state shows the same network with yellow arrows indicating traffic flow: traffic from CE1 and CE2 is sent to PE1 (Root), which then replicates it to PE3 (Root) and PE2 (Leaf). PE3 (Root) then delivers it to CE3 and CE4. PE2 (Leaf) does not forward traffic to other CEs. - -Figure 23-2 EVPN E-Tree services - -At a high level, EVPN E-LAN service can be considered as a special case of EVPN E-Tree service, with all attachment circuits designated as *root*. In fact, many vendors use the same configuration constructs for EVPN E-LAN and EVPN E-Tree, defaulting the attachment circuit to a *root*, with some configuration knobs turning it to a *leaf*. - -EVPN E-Line service - -EVPN E-Line, called as well EVPN Virtual Private Wire Service (VPWS), is point-to-point Layer 2 service, without MAC learning. Ethernet frame received from an end device connected via single-homed or multi-homed attachment circuit, is transported over this point-to-point service to the remote end device, connected again via single-homed or multi-homed attachment circuit. Since it is pure point-to-point communication, no MAC learning is required, and thus MAC learning is not part of EVPN E-Line (VPWS) architecture. - -![Diagram of EVPN E-Line services showing two network states. The top state shows CE1 and CE2 connected to PE1 and PE2 respectively, which are part of a point-to-point service (indicated by a single yellow line) to PE3 and PE4, which are then connected to CE3 and CE4. The bottom state shows the direct point-to-point connections: a yellow line between CE1 and CE3, and a red line between CE2 and CE4, bypassing the PEs.](8512afe2a50a7087c8b77a68dd354994_img.jpg) - -Diagram of EVPN E-Line services showing two network states. The top state shows CE1 and CE2 connected to PE1 and PE2 respectively, which are part of a point-to-point service (indicated by a single yellow line) to PE3 and PE4, which are then connected to CE3 and CE4. The bottom state shows the direct point-to-point connections: a yellow line between CE1 and CE3, and a red line between CE2 and CE4, bypassing the PEs. - -![O-RAN Alliance logo](9377b88f1c826970045f861ff1b24872_img.jpg) - -O-RAN Alliance logo - -Figure 23-3 EVPN E-Line (VPWS) services - -### EVPN VLAN-based service - -EVPN architecture uses three implementation constructs defined on the Provider Edge (PE) devices: - -- EVPN Instance (EVI), called as well MAC-VRF. Both EVI and MAC-VRF will be used in this document interchangeably. -- Bridge (MAC learning) domain/table -- Broadcast (flooding) domain (i.e. VLAN) - -Depending how these building blocks are used, EVPN architecture defines 3 options for constructing EVPN services: - -- EVPN VLAN-based service (applicable to EVPN E-LAN, EVPN E-Tree and EVPN E-Line services) -- EVPN VLAN-bundle service (applicable to EVPN E-LAN, EVPN E-Tree and EVPN E-Line services) -- EVPN VLAN-aware bundle (applicable to EVPN E-LAN and EVPN E-Tree services only) - -In EVPN VLAN-based service, each EVI contains single bridge (MAC learning) domain/table, which in turn contains only single VLAN (single broadcast/flooding domain). This is the simplest EVPN service with 1:1 mapping between VLAN and EVI as outlined in 0 - -![Diagram of EVPN VLAN-based services showing three instances (Instance 1, 2, 3) between PE1 and PE2. Instance 1 maps VLAN ID 1 to VLAN ID 11. Instance 2 maps VLAN ID 2 to VLAN ID 12. Instance 3 maps VLAN ID 3 to VLAN ID 12. Each instance contains a Bridge (MAC learning) domain and a Broadcast (flooding) domain.](cc4b80f3af11f554590470dbaa70daf8_img.jpg) - -The diagram illustrates three EVPN instances (Instance 1, Instance 2, and Instance 3) configured between two Provider Edge (PE) devices, PE1 and PE2. Each instance is represented by a light green rectangular box containing two nested boxes: a 'Bridge (MAC learning) domain' and a 'Broadcast (flooding) domain'. - - Instance 1: Connected to 'VLAN ID 1' on PE1 and 'VLAN ID 11' on PE2. Its internal domains are labeled 'Bridge (MAC learning) domain A' and 'Broadcast (flooding) domain X'. - - Instance 2: Connected to 'VLAN ID 2' on PE1 and 'VLAN ID 12' on PE2. Its internal domains are labeled 'Bridge (MAC learning) domain B' and 'Broadcast (flooding) domain Y'. - - Instance 3: Connected to 'VLAN ID 3' on PE1 and 'VLAN ID 12' on PE2. Its internal domains are labeled 'Bridge (MAC learning) domain C' and 'Broadcast (flooding) domain Z'. - The PE1 and PE2 devices are shown as dashed grey boxes on the left and right respectively, with horizontal lines connecting the VLAN labels to the corresponding EVPN instances. - -Diagram of EVPN VLAN-based services showing three instances (Instance 1, 2, 3) between PE1 and PE2. Instance 1 maps VLAN ID 1 to VLAN ID 11. Instance 2 maps VLAN ID 2 to VLAN ID 12. Instance 3 maps VLAN ID 3 to VLAN ID 12. Each instance contains a Bridge (MAC learning) domain and a Broadcast (flooding) domain. - -Figure 23-4 EVPN VLAN-based services (E-LAN, E-Tree, E-Line) - -EVPN VLAN-based service allows for VLAN tag translation, where incoming VLAN tag (for example VLAN 2) is translated to VLAN 12. Additionally, EVPN VLAN-based service provides - -1 the option to carry the Ethernet frame with the VLAN tag across EVPN network, or to strip the -2 VLAN tag before carrying the Ethernet frame across EVPN network. - -3 EVPN VLAN-bundle service - -4 The biggest challenge with basic EVPN VLAN-based service is scaling. In EVPN VLAN-based -5 service each VLAN consumes dedicated EVI, thus the maximum numbers of VLANs that can be -6 served is limited by the supported EVIs on given hardware platform. EVPN VLAN-bundle service -7 addresses this scaling limitation by bundling multiple VLANs into single bridge (MAC learning) -8 domain/table and single EVI (MAC-VRF), as outlined in Figure 23-5 - -![Diagram of EVPN VLAN-bundle service showing three VLANs (ID 10, 20, 30) connected to two PE devices (PE1, PE2) through a single EVPN Instance 1. The instance contains a Bridge (MAC learning) domain A, which is further divided into three Broadcast (flooding) domains: X, Y, and Z. Each VLAN is connected to one of these broadcast domains.](60ce0fc249173a32463028d12805feca_img.jpg) - -9 - -The diagram illustrates the EVPN VLAN-bundle service architecture. On the left, three green boxes represent VLAN IDs 10, 20, and 30. Lines connect these VLANs to a central light green box labeled 'EVPN Instance 1'. Inside this instance, there is a box for 'Bridge (MAC learning) domain A', which contains three stacked boxes labeled 'Broadcast (flooding) domain X', 'Broadcast (flooding) domain Y', and 'Broadcast (flooding) domain Z'. Lines connect VLAN ID 10 to domain X, VLAN ID 20 to domain Y, and VLAN ID 30 to domain Z. On the right, three more green boxes represent the output VLAN IDs 10, 20, and 30, connected from the broadcast domains to two grey boxes labeled 'PE1' and 'PE2' at the bottom of the instance. - -Diagram of EVPN VLAN-bundle service showing three VLANs (ID 10, 20, 30) connected to two PE devices (PE1, PE2) through a single EVPN Instance 1. The instance contains a Bridge (MAC learning) domain A, which is further divided into three Broadcast (flooding) domains: X, Y, and Z. Each VLAN is connected to one of these broadcast domains. - -10 -11 **Figure 23-5 EVPN VLAN-bundle service (E-LAN, E-Tree, E-Line)** - -12 -13 VLAN bundling allows dramatic reduction of MAC-VRFs that otherwise would be needed on the -14 router. Therefore, EVPN VLAN-bundle service is typically used in high-scale environment, with -15 large number of VLANs or VLAN combination (QinQ) that must be transported with EVPN -16 service. - -17 -18 This scaling improvements brings improvements, as well some restrictions for service deployment, -19 namely: - -- 20 -- the original VLAN tag must be carried with frame across EVPN network and VLAN -21 translation is not supported - - MACs cannot be re-used across different VLANs -- 22 - -23 -24 The first restriction is related to the fact, that underlying transport identification (i.e. MPLS label -25 with MPLS underlay transport, Function:Argument with SRv6 underlay transport) identifies the -26 bridge domain. Therefore, the underlying transport identification cannot be used to distinguish -27 Ethernet frames - received over EVPN network - as belonging to different VLANs, if VLAN tag is -28 stripped before sending Ethernet frames across EVPN. And this differentiation is required to -29 maintain per-VLAN broadcast/flooding restrictions. - -30 -31 Second restriction is the straight result of bundling multiple VLANs in single bridge (MAC -32 learning) domain/table. All these bundled VLANs use the same MAC table, therefore all MACs -33 must be unique across all bundle VLANs. - -![O-RAN ALLIANCE logo](cefc8594a8e8125d6cba7dab877c86f2_img.jpg) - -O-RAN ALLIANCE logo - -1 EVPN VLAN-aware bundle Service - -2 Restrictions of EVPN VLAN-bundle services are removed by EVPN VLAN-aware bundle service. - 3 EVPN VLAN-aware bundle service is a trade-off between EVPN VLAN-based service (poor - 4 scaling, but simple service without restrictions related to VLAN translation or MAC learning) and - 5 EVPN VLAN-bundle service (good scaling, but restricting VLAN translation support and requiring - 6 MAC uniqueness). - -7 EVPN VLAN-aware bundle brings back separate bridge (MAC learning) domain/table per VLAN, - 8 still keeping the option to bundle multiple VLANs with single EVI (MAC-VRF), as outlined in - 9 Figure 23-6. - -10 - -![Diagram of EVPN Instance 1 showing three separate bridge (MAC learning) domains (A, B, C) and broadcast (flooding) domains (X, Y, Z) connected to PE1 and PE2. PE1 is connected to VLAN ID 1, 2, and 3. PE2 is connected to VLAN ID 11, 12, and 13.](5099b826c109bf4df1229d96520da57f_img.jpg) - -The diagram illustrates an EVPN Instance 1 spanning between two Provider Edge (PE) devices, PE1 and PE2. Inside the instance, there are three distinct bridge (MAC learning) domains labeled A, B, and C. Each bridge domain is associated with a corresponding broadcast (flooding) domain labeled X, Y, and Z. PE1, on the left, is connected to three external VLANs: VLAN ID 1, VLAN ID 2, and VLAN ID 3. PE2, on the right, is connected to three external VLANs: VLAN ID 11, VLAN ID 12, and VLAN ID 13. Lines connect each external VLAN to its respective broadcast domain within the EVPN instance. - -Diagram of EVPN Instance 1 showing three separate bridge (MAC learning) domains (A, B, C) and broadcast (flooding) domains (X, Y, Z) connected to PE1 and PE2. PE1 is connected to VLAN ID 1, 2, and 3. PE2 is connected to VLAN ID 11, 12, and 13. - -11 -12 -13 **Figure 23-6 EVPN VLAN-aware bundle service (E-LAN, E-Tree)** - -14 -15 Scaling wise EVPN VLAN-aware bundle service sits between EVPN VLAN-based service and - 16 EVPN VLAN-bundle service, optimizing number of required EVIs (MAC-VRFs), while keeping - 17 the same number of bridge (MAC learning) domain as EVPN VLAN-based service. - -18 -19 Table 7 summarizes different EVPN service models. - -20 - -| Characteristic | VLAN-based | VLAN-bundle | VLAN-aware bundle | -|------------------------------------------|------------|-------------|-------------------| -| Broadcast domains (VLANs) per EVI | =1 | ≥1 | ≥1 | -| Bridge (MAC learning) domains per EVI | =1 | =1 | ≥1 | -| MACs must be unique across VLANs | no | yes | no | -| VLAN translation allowed | yes | no | yes | -| VLAN tag carried over | yes/no | yes | yes | -| Ethernet Tag (BD) ID on BD scoped routes | 0 | 0 | ≠0 | -| Port based service support | no | yes | yes | - -21 -22 **Table 7: EVPN VLAN service types comparison** - -![O-RAN Alliance logo](683260ef6ff6db4c965953b66974c872_img.jpg) - -O-RAN Alliance logo - -1 MEF/EVPN service mapping - -2 MEF 6.3 (Subscriber Ethernet Service Definitions) defines Ethernet services commonly used in - 3 Ethernet metro aggregation architectures. Table 8 provides the mapping between MEF service - 4 definitions and IETF EVPN service implementations. - -| MEF 6.3 Ethernet Service Definitions | IETF EVPN Service Definition | -|-----------------------------------------|------------------------------------------------------------------------------------| -| EPL: Ethernet Private Line | EVPN E-Line VLAN-based | -| EVPL: Virtual Ethernet Private Line | EVPN E-Line VLAN-bundle (port-based) | -| EP-LAN: Ethernet Private LAN | EVPN E-LAN VLAN-based | -| EVP-LAN: Ethernet Virtual Private LAN | EVPN E-LAN VLAN-bundle (port-based)
EVPN E-LAN VLAN-aware bundle (port based) | -| EP-Tree: Ethernet Private Tree | EVPN E-Tree VLAN-based | -| EVP-Tree: Ethernet Virtual Private Tree | EVPN E-Tree VLAN-bundle (port-based)
EVPN E-Tree VLAN-aware bundle (port based) | - -5 -6 **Table 8: MEF Ethernet Services to IETF EVPN Services Mapping** - -## 8 24 Annex C: MP-BGP based L3VPNs - -9 BGP based layer 3 VPNs are a widely deployed connectivity application in Service Provider - 10 networks and work over an MPLS and SRv6 underlay infrastructure. BGP based layer 3 VPNs are - 11 based on RFC4364 [90] and use a peer-to-peer model that uses Border Gateway Protocol (BGP) to - 12 distribute VPN-related information. It is a highly scalable, peer-to-peer model that through route - 13 filtering allows flexible connectivity models within a VPN. VPN topologies include any-to-any L3 - 14 multi-point solutions as well as L3 tree solutions where connectivity constraints are built into the - 15 VPN infrastructure through controlled exportations and importation of routing information. This - 16 makes it an effective and efficient technology for L3 services associated with Xhaul transport. - -### 17 Building blocks of a L3 VPN service - -18 A typical L3 VPN services consists of the following: - -- 19 -- 20 • A Provider Edge (PE) Routers -- 21 • Virtual Routing Forwarding -- 22 • Route Distinguisher (RD) -- 23 • Route Target (RT) -- 24 • Multi-Protocol Border Gateway Protocol (MP-BGP) -- 25 - -#### 26 Provider Edge (PE) Router - -27 A Provider Edge router is a device which originate or terminate a L3VPN service. In other words, a - 28 PE router is a VPN Endpoint, providing connectivity to the device(s) connected to it. - -![O-RAN Alliance logo](e5119fd755a0bf1a2106b4198c710d70_img.jpg) - -O-RAN Alliance logo - -![Figure 24-1: PE routers in an Xhaul infrastructure. The diagram shows a cloud representing the Xhaul network, divided into four segments: Fronthaul (red), Midhaul (orange), Backhaul (green), and 5G and/or Transport Core (grey). On the left, an O-RU is connected to a CSR. The CSR is connected to a PE Router. This PE Router is connected to the Fronthaul segment. The Fronthaul segment is connected to an O-DU at a Hub Site. The O-DU is connected to a PE Router. This PE Router is connected to the Midhaul segment. The Midhaul segment is connected to an O-CU at an Edge DC. The O-CU is connected to a PE Router. This PE Router is connected to the Backhaul segment. The Backhaul segment is connected to a PE Router. This PE Router is connected to a UPF at a Regional DC. The UPF is connected to the 5G and/or Transport Core segment.](dbe4ffa9778863279b48b56fe097cd23_img.jpg) - -Figure 24-1: PE routers in an Xhaul infrastructure. The diagram shows a cloud representing the Xhaul network, divided into four segments: Fronthaul (red), Midhaul (orange), Backhaul (green), and 5G and/or Transport Core (grey). On the left, an O-RU is connected to a CSR. The CSR is connected to a PE Router. This PE Router is connected to the Fronthaul segment. The Fronthaul segment is connected to an O-DU at a Hub Site. The O-DU is connected to a PE Router. This PE Router is connected to the Midhaul segment. The Midhaul segment is connected to an O-CU at an Edge DC. The O-CU is connected to a PE Router. This PE Router is connected to the Backhaul segment. The Backhaul segment is connected to a PE Router. This PE Router is connected to a UPF at a Regional DC. The UPF is connected to the 5G and/or Transport Core segment. - -Figure 24-1 PE routers in an Xhaul infrastructure - -In the context of an Xhaul packet switched transport network, the first L3 router enabling an L3VPN services to provide connectivity between the O-RAN/3GPP components (O-RU, O-DU, O-CU, UPF, 5GC) is considered a Provider Edge (PE) router. This could be a CSR or HSR in Fronthaul, Midhaul or Backhaul network. - -VPN Routing and Forwarding Tables (VRF) and Route Distinguishers (RD) - -The VPN routing and forwarding table (VRF) is a key element in the BGP based L3 VPN technology. A VRF essentially define a VPN instance on PE and associates a routing table instance with the VRF. A VRF exist on PEs and more than one VRF can exist on a single PE. The VRF contains routes that should be available to a particular set of sites participating in the VPN. - -![Figure 24-2: VRF routing tables. The diagram shows a cloud representing the Xhaul network, divided into four segments: Fronthaul (red), Midhaul (orange), Backhaul (green), and 5G and/or Transport Core (grey). On the left, an O-RU is connected to a CSR. The CSR is connected to a PE Router. This PE Router is connected to the Fronthaul segment. The Fronthaul segment is connected to an O-DU at a Hub Site. The O-DU is connected to a PE Router. This PE Router is connected to the Midhaul segment. The Midhaul segment is connected to an O-CU at an Edge DC. The O-CU is connected to a PE Router. This PE Router is connected to the Backhaul segment. The Backhaul segment is connected to a PE Router. This PE Router is connected to a UPF at a Regional DC. The UPF is connected to the 5G and/or Transport Core segment. Above the cloud, three VRF routing tables are shown: VRF A, RD 1; VRF B, RD 2; and VRF m, RD n. The VRF A Route Table contains routes for Prefix x1, x2, and x3 with next hops y1, y2, and y3 respectively. The VRF B Route Table contains routes for Prefix x1, x2, and x3 with next hops y1, y2, and y3 respectively.](8a1804669974ce61da225f5794e809e5_img.jpg) - -| VRF A Route Table | | VRF B Route Table | | | | -|-------------------|-----------|-------------------|-----|-----------|-------| -| RD1 | Prefix x1 | NH y1 | RD2 | Prefix x1 | NH y1 | -| RD1 | Prefix x2 | NH y2 | RD2 | Prefix x2 | NH y2 | -| RD1 | Prefix x3 | NH y3 | RD2 | Prefix x3 | NH y3 | -| ... | ... | ... | ... | ... | ... | - -Figure 24-2: VRF routing tables. The diagram shows a cloud representing the Xhaul network, divided into four segments: Fronthaul (red), Midhaul (orange), Backhaul (green), and 5G and/or Transport Core (grey). On the left, an O-RU is connected to a CSR. The CSR is connected to a PE Router. This PE Router is connected to the Fronthaul segment. The Fronthaul segment is connected to an O-DU at a Hub Site. The O-DU is connected to a PE Router. This PE Router is connected to the Midhaul segment. The Midhaul segment is connected to an O-CU at an Edge DC. The O-CU is connected to a PE Router. This PE Router is connected to the Backhaul segment. The Backhaul segment is connected to a PE Router. This PE Router is connected to a UPF at a Regional DC. The UPF is connected to the 5G and/or Transport Core segment. Above the cloud, three VRF routing tables are shown: VRF A, RD 1; VRF B, RD 2; and VRF m, RD n. The VRF A Route Table contains routes for Prefix x1, x2, and x3 with next hops y1, y2, and y3 respectively. The VRF B Route Table contains routes for Prefix x1, x2, and x3 with next hops y1, y2, and y3 respectively. - -Figure 24-2: VRF routing tables - -A route distinguisher (RD) is a unique value assigned to a VRF on the PE Router. A RD allows to associate and identify routes in the routing table with a particular VRF and allows for overlapping IP address space across VRFs. - -An RD is a local value on the PE in the Packet Switched RAN network. - -Route Targets (RT) - -Route Targets (RT) are the mechanism by which routing information distribution can be controlled within an BGP based VPN throughout the packet switched network. Route Target are propagated through - -![O-RAN Alliance logo](a010f0a7b8e74337e19c8f5f9219841f_img.jpg) - -O-RAN Alliance logo - -the BGP based VPN network using route-target extended MP-BGP communities. Every PE within the MPLS VPN network define a set of RT values for import or export of VPN route information. BGP based VPN uses route-target communities as follows: - -- When a VPN route is injected into MP-BGP, the route is associated with a list of VPN route-target communities. -- An import list of route-target communities is associated with each VRF. This list defines the values that should be matched against to decide whether a route is eligible to be imported into this VRF. - -![Diagram illustrating the use of route targets to control IP connectivity within a VRF. The diagram shows a network topology with two Customer Site Routers (CSR-R1 and CSR-R2) connected to an O-RU. CSR-R1 is connected to a Hub Site Router (R3) via a FrontHaul link. CSR-R2 is connected to the Hub Site Router (R3) via a MidHaul link. The Hub Site Router (R3) is connected to an O-DU (Hub Site). The O-DU is connected to an O-CU (Edge DC). The O-CU is connected to PE Routers. The PE Routers are connected to a UPF (Regional DC) and a 5G and/or Transport Core. The diagram also shows VRF configurations for each device: CSR-R1 (VRF A, RD 1, RT Export: 100:1, RT Import: 100:3), CSR-R2 (VRF A, RD 1, RT Export: 100:2, RT Import: 100:3), Hub Site Router R3 (VRF A, RD 1, RT Export: 100:3, RT Import: 100:1, RT Import: 100:2).](ce58a77ff34d610cd0634eacffbd3eaf_img.jpg) - -Diagram illustrating the use of route targets to control IP connectivity within a VRF. The diagram shows a network topology with two Customer Site Routers (CSR-R1 and CSR-R2) connected to an O-RU. CSR-R1 is connected to a Hub Site Router (R3) via a FrontHaul link. CSR-R2 is connected to the Hub Site Router (R3) via a MidHaul link. The Hub Site Router (R3) is connected to an O-DU (Hub Site). The O-DU is connected to an O-CU (Edge DC). The O-CU is connected to PE Routers. The PE Routers are connected to a UPF (Regional DC) and a 5G and/or Transport Core. The diagram also shows VRF configurations for each device: CSR-R1 (VRF A, RD 1, RT Export: 100:1, RT Import: 100:3), CSR-R2 (VRF A, RD 1, RT Export: 100:2, RT Import: 100:3), Hub Site Router R3 (VRF A, RD 1, RT Export: 100:3, RT Import: 100:1, RT Import: 100:2). - -**Figure 24-3: Use of route targets to control IP connectivity within a VRF** - -Figure 24-3 above shows a simple mechanism of import and export Route Communities within an BGP based VPN network. Where required CSR route-targets may be configured to be different than the Hub Site Router. For scalability and efficient resource usage on the CSR, the operator may choose to not import all the routes, rather importing the routes from Hub Site Route and only certain other CSR's. - -When used properly, Route Targets can be used to limit the routing table information within a BGP based VPN Network and create different IP topologies at the transport layer. These include: - -- Any to any topologies. -- Hub and spoke topologies. - -#### Multi-Protocol Border Gateway Protocol (MP-BGP) - -MPLS VPN information is propagated through the network using Multi-Protocol BGP (MP-BGP) [92]. All PE routers within the VPN must configure MP-BGP peering and enable VPN address-family and extended communities to exchange VPN related information including routing table information and Route Targets. - -#### Traffic Steering into an BGP VPN - -SR Policy operations is defined in [160]. It is a mechanism that can be used to create an end-to-end Label Switch Path (LSP) using required metrics and constraints. While using Segment Routing Traffic - -![O-RAN Alliance logo](6702cc564c13eb629b0b196798dc054f_img.jpg) - -O-RAN Alliance logo - -Engineering (SRTE) for traffic path programmability, it is possible to automatically steer BGP based VPN traffic into an SRTE policy. - -Typically, an SRTE Policy is uniquely identified using the following 3-tuple consisting of: - -- **Head End:** Starting point of the LSP created by SRTE Policy -- **End Point:** Destination for the traffic using the SRTE LSP -- **Color:** A numeric value associated with the SRTE policy. - -The SRTE policy color is a numeric value that is configurable in the SRTE policy. Once a VPN endpoint route is “tagged” with this color, traffic can be automatically steered into the SRTE policy. - -![Diagram illustrating Traffic Steering with BGP based VPNs. The diagram shows a network architecture with components: O-RU, CSR-R1, CSR-R2, Hub Site Router R3, O-DU, O-CU, PE Routers, UPF, and 5G and/or Transport Core. Traffic paths are labeled FrontHaul, MidHaul, and Backhaul. Annotations indicate: 'Export VRF Route with an SRTE policy Color' and 'Use BGP Policy to tag a route with SRTE color'.](3f47bcff76a8105d2539569fc8909db7_img.jpg) - -The diagram illustrates a network architecture for traffic steering. On the left, two O-RU units are connected to CSR-R1 and CSR-R2. These are connected to a Hub Site Router R3 via an O-DU at a Hub Site. The connection between CSR-R2 and R3 is labeled 'FrontHaul'. R3 is connected to an O-CU at an Edge DC, which is then connected to PE Routers. The connection between R3 and the O-CU is labeled 'MidHaul'. The PE Routers are connected to a UPF at a Regional DC and to the '5G and/or Transport Core'. The connection between the O-CU and PE Routers is labeled 'Backhaul'. Two callouts are present: one pointing to the connection between CSR-R1 and R3 stating 'Export VRF Route with an SRTE policy Color', and another pointing to the connection between CSR-R2 and R3 stating 'Use BGP Policy to tag a route with SRTE color'. - -Diagram illustrating Traffic Steering with BGP based VPNs. The diagram shows a network architecture with components: O-RU, CSR-R1, CSR-R2, Hub Site Router R3, O-DU, O-CU, PE Routers, UPF, and 5G and/or Transport Core. Traffic paths are labeled FrontHaul, MidHaul, and Backhaul. Annotations indicate: 'Export VRF Route with an SRTE policy Color' and 'Use BGP Policy to tag a route with SRTE color'. - -**Figure 24-4: Traffic Steering with BGP based VPNs** - -As shown above, the VPN routes can be colored in 2 possible ways: - -1. While defining a VRF, define a color for all Prefixes associated with that VRF, or -2. When sending or receiving BGP routes, using a policy to “color” the route. - -In either case, the VPN route will now be tagged with a color and traffic for the destination or a flow will automatically be steered into the SRTE policy that may provide traffic path programmability. - -## 25 Annex D: Quality of Service - -This annex gives an overview of packet base Quality of Service (QoS). - -### What is Quality of Service? - -Quality of Service (QoS) is an umbrella term that broadly covers the concept of the management of traffic flowing in an infrastructure. In general, QoS can provide two capabilities. - -1. A mechanism to actively manage the transmission of data on a network link out of a node when the link is approaching or at saturation. This active management consists of - -![O-RAN ALLIANCE logo](3cf9c03399ad83db016e51124c54e855_img.jpg) - -O-RAN ALLIANCE logo - -1 determining which data to forward next, which data to store for forwarding later, and which -2 data to drop. - -- 3 2. The enforcement of service level agreements through the selective acceptance of traffic into a -4 node (or network) based on pre-determined criteria. Again, this acceptance is based on -5 determining which data to accept now, which data to store for acceptance later and which -6 data to deny (drop). - -7 -8 Fundamentally, QoS only operates when traffic is flowing at the limits of capacity (either physical -9 or logical). When flowing traffic rates are well below the limits, QoS is essentially benign allowing -10 all traffic to be forwarded as it is received. - -## 12 Why do we need QoS? - -13 Applications using the network transport will often require certain capabilities from the network in -14 order for the application to function correctly. - -15 -16 For example, real-time voice services (telephone calls) can only sustain a maximum latency -17 between the end points before interactive speech becomes difficult. This maximum latency between -18 endpoints translates to two demands from the network; - -- 19 1. Minimising hop by hop latency as a voice packet flows across the network infrastructure. -- 20 2. Minimising jitter in the packets arriving in order to minimise the de-jitter buffer needed at the -21 receiver (which adds latency). - -22 It is useful then to be able to identify voice traffic in the network and prioritise it for forwarding -23 such that it is not held up behind other less time sensitive traffic. - -24 -25 A second example might be an Electronic Point of Sale (EPoS) application. This type of application -26 does not need to be particularly latency bound (a few 10s or 100s of milliseconds in packet arrival -27 does not impact the service), but it does need to have some guaranteed capacity in order to function. -28 I.e. we do not want the EPoS application struggling for bandwidth because a large data transfer is -29 taking place. This guaranteed bandwidth requirement also translates into network demands. - -- 30 1. Minimising packet loss for the traffic, if necessary, storing it locally until the local egress -31 interface has capacity to send it on. -- 32 2. Reserving a minimum amount of transmission time (or bandwidth) on the interface for -33 packets of the EPoS application. - -34 -35 QoS then is the mechanism by which operators can identify applications in an infrastructure and -36 apply policies to the infrastructure to maintain the applications transport requirements, even when -37 capacity is limited. - -## 39 QoS functional elements - -40 As a suite of capabilities QoS can be broken out into three distinct sets of functions; - -- 41 -- 42 1. Traffic Classification and marking -- 43 2. Congestion avoidance -- 44 3. Congestion management - -![O-RAN Alliance logo](3a6347f9ba293dba971fe22b739bdeef_img.jpg) - -O-RAN Alliance logo - -1 These three function sets work together to identify (classify) different traffic types, determine how - 2 much of each traffic type should be allowed into and through the network (congestion avoidance) - 3 and how traffic should be scheduled when interfaces become congested (congestion management). - 4 - -5 The specific implementation of these capabilities is vendor specific, but in general, the behaviours - 6 required by the different functions are defined as policies, either individually or in groups. These - 7 policies are applied to interfaces on the switching elements in a network defining the local - 8 behaviours within the device. - 9 - -## 10 Network level behaviour - -11 QoS is implicitly a mechanism that is node based; the management of traffic in one node has no - 12 direct impact on the management of traffic in surrounding nodes. However, it is important to design - 13 the QoS behaviour of a network as a whole. Just as the operator has the ability to define the routing - 14 behaviour of a network as a system of single hop by hop elements, so she has the ability to define - 15 the QoS behaviour of the network as a system. - 16 - -17 The interaction between elements is defined by the policies applied to each device and the use of - 18 “class of service” markings applied to the packets or frames flowing between the devices.1 - -19 The use of markings allows an individual network element to pass some information about a given - 20 packet to a downstream element. How this downstream element interprets the information and then - 21 acts on it, is out of the upstream elements control, but a network of devices under single - 22 administrative control may choose to use such information in network wide policy. - 23 - -## 24 Node level behaviour - -![Diagram of an example network QoS structure showing packet flow from CE to PE, then through two P nodes, then through another PE to CE. Numbered arrows indicate QoS actions at each node: 1) Classify customer traffic at the first PE, 2) Mark traffic for transport domain at the first PE, 3) Schedule traffic on transport marking and policy at the first P node, 4) Classify traffic on transport marking at the second P node, 5) Classify on customer marking at the second PE, 6) Schedule traffic on customer marking and policy at the second PE. A legend below the diagram lists these six actions.](42b224bb9b5fce80421c05b7f630c048_img.jpg) - -1) Classify customer traffic - 2) Mark traffic for transport domain - 3) Schedule traffic on transport marking and policy - 4) Classify traffic on transport marking - 5) Classify on customer marking - 6) Schedule traffic on customer marking and policy - -Diagram of an example network QoS structure showing packet flow from CE to PE, then through two P nodes, then through another PE to CE. Numbered arrows indicate QoS actions at each node: 1) Classify customer traffic at the first PE, 2) Mark traffic for transport domain at the first PE, 3) Schedule traffic on transport marking and policy at the first P node, 4) Classify traffic on transport marking at the second P node, 5) Classify on customer marking at the second PE, 6) Schedule traffic on customer marking and policy at the second PE. A legend below the diagram lists these six actions. - -25 - 26 - 27 **Figure 25-1: Example network QoS structure** - 28 - 29 - -1 The term “class of service” is used here to generically to describe the specific markings in a packet or frame. The author recognises Class of Service (COS) identifies such markings in an ethernet header as defined by IEEE 802.1p. Here it is generically used to refer to Ethernet COS, IP TOS, IP PREC, IP DSCP, MPLS EXP etc. - -![O-RAN Alliance logo](f74d8082f6a1b4ea9be39c583e6272fe_img.jpg) - -O-RAN Alliance logo - -The per-hop-behaviours (PHBs) needed in the network can generally be broken down into two sets; Those needed at the edge of the network (Edge QoS), and those needed in the core of the network (Core QoS). We can see these behaviours in Figure 25-1. - -1. Edge QoS. Here we are classifying traffic entering into the network on ingress (1) and scheduling traffic leaving the network on egress (6). Here the ingress classification (from the client) and egress classification (5) and scheduling (6) (towards the client) will (often) be determined by the markings of the client traffic being transported across the network. In addition, ingress traffic (CE → PE), once classified, will be marked (2) to conform to the transport marking scheme. -2. Core QoS. Here traffic will be classified by the transport marking scheme (4) (mentioned above), scheduled based on those markings (3). This PHB is designed to manage traffic at an aggregate level, treating services that have common requirements (defined by marking) with a common behaviour. - -These two sets of PHBs present different requirements to the underlying hardware and care should be taken when selecting a platform to ensure the operators desired PHBs can be met. - -## Traffic classification and marking - -As previously mentioned, traffic classification is a term used to describe the identification and categorisation of traffic arriving at or inside network element. Classification broadly falls into two distinct categories. - -### Context based classification - -In this model, traffic arriving at a node is classified, (allocated to some internal category) based on the context associated with its arrival. For example, it might be assumed that all traffic arriving from a specific logical or physical interface will be categorized as “best effort”. This specific example actually represents the default behaviour for almost all network elements, and is useful to recognise, as it forms the basis for all other classifications. I.e. that without further modification, traffic arriving at a node will be treated as best effort (without any specific explicit treatment). - -![Diagram illustrating context-based classification. Two Customer Equipment (CE) nodes are connected to a single Provider Edge (PE) node. A large green arrow at the top indicates the 'Direction of packet flow' from left to right. Two smaller green arrows point from the CEs to the PE: arrow 1 from the top CE and arrow 2 from the bottom CE. A legend on the right indicates: 1) Real time traffic, 2) Best effort traffic.](97f6670a8f097f23fe35d62b76d75cf0_img.jpg) - -Diagram illustrating context-based classification. Two Customer Equipment (CE) nodes are connected to a single Provider Edge (PE) node. A large green arrow at the top indicates the 'Direction of packet flow' from left to right. Two smaller green arrows point from the CEs to the PE: arrow 1 from the top CE and arrow 2 from the bottom CE. A legend on the right indicates: 1) Real time traffic, 2) Best effort traffic. - -Figure 25-2: Context based classification - -In a second example, all traffic arriving on a specific interface might be classified (categorised) as “real time” or “high priority” (see Figure 25-2). - -![O-RAN Alliance logo](437517111168a2b766400478395eff60_img.jpg) - -The O-RAN Alliance logo, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with the word "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -1 Whilst use of context-based classification is important, it is a somewhat blunt tool, and assumes that -2 all traffic arriving on an interface is of a single type and requires common treatment. - -3 Packet based classification - -4 Packet based classification gives us a more selective tool with which to categorize traffic arriving at -5 a node. In this mode the node examines one or more fields in the arriving packets (or frames) to -6 make a categorisation decision. - -7 -8 One approach is to classify traffic into categories based on some flow or application information. -9 E.g. looking at source or destination, ether type, IP protocol, UDP or TCP port number etc. In this -10 way the node can infer the required QoS capabilities (e.g. low latency, minimum bandwidth, best -11 effort etc) from the type of traffic embedded in the packet. - -12 -13 However, often the most pragmatic approach is to require that packets are pre-marked with an -14 explicit class of service marking. The specific marking model varies dependent on the transport -15 being used, but the primary marking schemes to support are Ethernet Priority Code Point (PCP) and -16 Drop Eligible Indicator (DEI) fields in Ethernet IEEE 802.1p (part of the IEEE 802.1q VLAN -17 header specification), IP TOS, PREC or DSCP ECN fields (defined in IETF RFC 2474 [51] and -18 RFC 3168) and MPLS TC (EXP) field (defined in IETF RFC 3032 [63] and RFC 5462). - -19 -20 The use of a class of service (COS) marking allows a packet source or network element to encode -21 the required QoS capabilities for a packet directly into the packet header. By predetermining the -22 marking scheme to be used for the COS field, classification using the COS field alone is often -23 sufficient to determine the PHB needed in the network node. - -24 -25 Traffic marking - -26 As described above, a key attribute of a QoS architecture is the ability to pass information about the -27 QoS status of a packet between nodes, and indeed within a node (e.g. from ingress to egress). This -28 is achieved through the use of QoS markings, setting bit fields within a packet header that convey -29 some information about the QoS related context in which this packet should be considered. - -30 -31 Again, as described above there are numerous traffic marking schemes that are in use, each -32 associated with a particular header type in the packet (or frame) world. There are also bit fields -33 defined in meta-data associated with internal forwarding in many router and switch silicon -34 architectures. Two examples of this are “Discard Class or Loss Priority” often associated with the -35 output of a policing function, but also explicitly settable, and “qos-group” or “forwarding-class”, an -36 opaque field provided in many router implementations - -37 -38 The use and meaning associated with the values represented by these bits is entirely arbitrary, as -39 defined and used by users and operators. However, the value in their use lies in having agreed -40 meaning that can be passed between network elements. Some fields, for example IP DSCP, have -41 recommend meanings that can be used between providers. Others, such as MPLS TC (EXP) are not -42 formally defined so as to remain flexible. - -![Diagram of QoS marking domains showing Customer (CE), Provider (P), and Intra-node (PE) domains.](9a8f8276c7199f1dd9f3754cf60555c6_img.jpg) - -The diagram illustrates three QoS marking domains in a network topology. On the left, a Customer Equipment (CE) node is connected to a Provider Edge (PE) node, both enclosed in a green dashed oval representing the Customer domain. On the right, another PE node is connected to a CE node, also enclosed in a green dashed oval representing the Customer domain. In the center, two Provider (P) nodes are connected to each other and to the PE nodes, enclosed in a blue dashed oval representing the Provider domain. Green arrows with numbered circles indicate the Intra-node domain (1) within the PE nodes, the Provider domain (2) between the PE and P nodes, and the Intra-node domain (3) within the P nodes. - -1) Customer domain -2) Provider domain -3) Intra-node domain - -Diagram of QoS marking domains showing Customer (CE), Provider (P), and Intra-node (PE) domains. - -Figure 25-3: QoS marking domains - -A useful concept is to consider the use of a given marking scheme within a QoS marking domain. Nodes within a domain use a common scheme, allowing identification of traffic with common properties (a traffic class). Policies are then implemented in each node to maintain the appropriate network behaviour for each identified class, when under congested conditions. - -At the border between domains, the border element should be capable of classifying traffic in the first domain and remarking it for transport in the second. Usually the policy for forwarding will be implemented to honour the class structure for the domain it is in. In Figure 25-3, three domains are identified, 1) the customer domain, 2) the provider domain 3) an intra-node domain. The PE elements on the left and right of the provider domain border the provider and customer domains and will be responsible for remarking traffic as appropriate. - -## Congestion management - -Thus far we have discussed the options available for classifying traffic. But once classified, we must consider what behaviour to apply. As mentioned in the introduction to this section, a QoS node fundamentally only has three options available for managing traffic; forward, store for forwarding later or drop, but these options need only be applied when a bandwidth resource is congested. - -A key function of QoS is that of managing traffic during congestion of an interface. Congestion occurs when the quantity of traffic to be forwarded on an interface exceeds its capacity. In its simplest form, QoS alleviates this issue by buffering the excess traffic, i.e. storing it in a local memory until such time that the interface is available to send the stored traffic. - -## FIFO Queueing - -By storing packets that need to be sent on to this interface in the order they arrive, and then sending them in that order when the interface is free, we form a “first in - first out” (FIFO) queue of packets. - -This mechanism, queueing, is a useful tool for managing temporary congestion, smoothing out the bursts of traffic flowing into an interface, and forms the basis for more complex congestion management tools. - -There are four aspects of this capability that cause challenges; - -1. By storing traffic for later sending, we intrinsically delay that traffic that is being stored, adding latency to the transmission path for that traffic. Further, because the delay may be variable, (different amounts of traffic may be enqueued prior to this packet arriving) we introduce jitter. -2. As the speeds of the interfaces we are managing increases, we need more memory capacity to store enough packets to substantively impact the traffic we are buffering. -3. The process is of queueing traffic is indiscriminate, in that it impacts all traffic flowing through an interface. This presents the same latency implication to all applications using this interface, some of which will be impacted by this delay, and some will not. -4. As the amount of memory available to for the queue is finite, so the queue is finite. As a result, if the rate of arrival of traffic to be forwarded is significantly higher than the interface rate or the burst is long enough, the available buffer will be filled, and no further traffic can be enqueued. At this point, the node has no option but to drop traffic. When a queue is full, and a node can no longer add packets to the end (tail) of the queue, traffic otherwise destined for that queue is indiscriminately dropped from the tail (tail drop), until such time that the queue depth reduces and space is made available again for new traffic. - -It is worth remembering at this point that the application of QoS to an infrastructure is only a solution for the management of how traffic is dropped under congestion conditions. It is not a replacement for capacity planning and management for traffic that MUST be delivered. I.e. if a network has less capacity available than the amount of traffic that MUST be delivered, applying QoS is not an alternative to augmenting the capacity. - -However, it is possible to significantly improve on this single FIFO queue model by combining the use of classification with a programable scheduler to determine how we enqueue traffic, how much we allow to pass, and what to do with the excess. - -#### Class based queueing - -By combining the concept of classifying traffic with the concept of a queue it is possible to allow a node to manage the traffic flowing on an interface with a behaviour that is appropriate to the applications flowing in each class. - -![Diagram illustrating Class Based Queueing (CBQ) with Priority and WFQ classes.](88a422435c7d5f8cabe4609cb0fd46b3_img.jpg) - -The diagram illustrates Class Based Queueing (CBQ). On the left, there are five horizontal blue bars representing traffic queues, numbered 1 to 5 from top to bottom. A curly brace on the left groups the first three queues (1, 2, 3) under the label 'Priority'. Another curly brace groups the last two queues (4, 5) under the label 'WFQ'. To the right of the queues is a blue trapezoidal shape representing a scheduler, with a circular arrow inside indicating a round-robin or weighted scheduling mechanism. To the right of the scheduler is a blue cylinder representing the output interface. - -Diagram illustrating Class Based Queueing (CBQ) with Priority and WFQ classes. - -![O-RAN Alliance logo](89cb4b0d1ef71532ac538cb30aa64087_img.jpg) - -The logo for the O-RAN Alliance, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with the word "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -1 **Figure 25-4: Class based queue** - -2 -3 In this model, shown in Figure 25-4, the system identifies separate logical queues for traffic -4 destined to flow out of a given interface. Traffic can be placed into a queue based on the -5 classification information gained on arrival (or if the system is capable, after the packet has been -6 forwarded – determined that it should flow out of this specific interface). - -7 -8 For example, traffic identified as needing low latency, and low jitter (real time – our voice calls -9 from earlier) may be placed into queue 1. Traffic requiring some minimum bandwidth (business -10 critical, our EPOS traffic) may be placed into queue 3. Traffic that has no specific requirements -11 (best effort) may be placed into queue 5. - -12 -13 The scheduler can now be programmed to dequeue traffic and place it onto the interface following a -14 pre-determined policy – for example; - -- 15 1. Serve all high-priority traffic first (E.g. Queue 1 and 2), up to a given capacity of the -16 interface for each queue (for example 50% and 5%). Any traffic arriving at this interface for -17 those queues that cannot be served at that rate should be placed into the appropriate queue. -- 18 2. Serve traffic from low priority queues (queue 3, 4 and 5) with equal priority (a packet from -19 each) until the minimum guaranteed amount of bandwidth allocated to that queue is met. -- 20 3. Continue to serve traffic from low priority queues until either the queue is empty, or the -21 interface bandwidth is consumed. - -22 -23 This type of policy allows maximum use of the available bandwidth whilst guaranteeing each -24 application class will have access to at least the capacity it needs to support the user base. - -25 -26 Hierarchical class-based queueing - -27 A further extension of this model uses a tiered set of schedulers to manage sets of queues that are -28 “grouped” to manage traffic associated with some logical entity on the physical interface. - -![Figure 25-5: Hierarchical class-based queue model diagram. The diagram illustrates a two-level scheduling hierarchy for a physical interface supporting two VLANs: orange and green. -- Top branch (Orange VLAN): Queues 1 and 2 are labeled 'Priority', and queues 3, 4, and 5 are labeled 'WFQ'. These five queues feed into Child scheduler (2). -- Bottom branch (Green VLAN): Queues 1, 2, and 3 are labeled 'Priority', and queues 4 and 5 are labeled 'WFQ'. These five queues feed into Child scheduler (3). -- Both Child schedulers (2) and (3) feed into the Parent Scheduler (1). -- The Parent Scheduler (1) outputs a combined stream represented by an orange arrow and a green arrow inside a single blue pipe. -- A legend on the right identifies: 1) Parent Scheduler, 2) Child scheduler (orange VLAN), and 3) Child scheduler (green VLAN).](2cf1f70c3a387c43e15192a30d212546_img.jpg) - -Figure 25-5: Hierarchical class-based queue model diagram. The diagram illustrates a two-level scheduling hierarchy for a physical interface supporting two VLANs: orange and green. -- Top branch (Orange VLAN): Queues 1 and 2 are labeled 'Priority', and queues 3, 4, and 5 are labeled 'WFQ'. These five queues feed into Child scheduler (2). -- Bottom branch (Green VLAN): Queues 1, 2, and 3 are labeled 'Priority', and queues 4 and 5 are labeled 'WFQ'. These five queues feed into Child scheduler (3). -- Both Child schedulers (2) and (3) feed into the Parent Scheduler (1). -- The Parent Scheduler (1) outputs a combined stream represented by an orange arrow and a green arrow inside a single blue pipe. -- A legend on the right identifies: 1) Parent Scheduler, 2) Child scheduler (orange VLAN), and 3) Child scheduler (green VLAN). - -**Figure 25-5: Hierarchical class-based queue model** - -In Figure 25-5, we have a physical interface supporting two VLANs (orange and green). Each VLAN has its own set of queues and its own scheduling policy for those queues. In this example the orange VLAN has two priority queues and three guaranteed bandwidth queues. The top scheduler (2) is responsible for managing the flow of traffic from the queues associated with that VLAN. The bottom scheduler (3) manages this flow of traffic from the queue associated with the green VLAN. - -Schedulers (2) and (3) are regarded as child schedulers, and their packet flow is in turn managed by scheduler (1), the parent scheduler for the interface. The parent scheduler will be programmed with a policy to manage the traffic flowing from the child schedulers toward the interface. - -This model can allow for a “hard” distribution of the bandwidth on an interface amongst the logic entities sharing that capacity, protecting the use of the bandwidth for a given VLAN (orange) from the others on the same interface (green). - -### Congestion avoidance - -Thus far we have discussed the options available for classifying traffic, and managing traffic when interfaces are under congestion. We have examined how, when an interface is congested, we can consider which packets to forward and when. However, one important aspect of QoS is the prevention of congestion in the first place. - -Congestion avoidance predominantly takes two forms; - -1. Admission control -2. Selective queue management through random early discard (RED) or weighted random early discard (WRED) - -1 Admission control - -2 This is the process of managing the amount of traffic that we accept into the network. This can be - 3 thought of as the enforcement of the contract between the applications requirements', and the - 4 networks transport capability. Returning to the example of the voice call, let us imagine that the - 5 transport network has enough capacity to sustain 100 concurrent voice calls (Figure 25-6). If more - 6 than 100 calls are introduced there is insufficient bandwidth to sustain all the calls and some traffic - 7 will inevitably be dropped. Because the dropping of traffic will be random, all calls will be - 8 impacted by the packet loss equally, resulting in reduced voice quality or even call failure. - -![Diagram illustrating admission control policing. A green arrow labeled 'Direction of packet flow' points from left to right. Below it, a circle labeled 'CE' is connected to a circle labeled 'PE' by a horizontal line. A callout '1' points to the CE circle, and a callout '2' points to the PE circle. Below the PE circle, text reads '1) Allow BW of 100 calls' and '2) Capacity for 100 calls'.](7480889e4ab8f0e8524ef7ad3e9b2536_img.jpg) - -Direction of packet flow - -1 - -CE - -PE - -2 - -1) Allow BW of 100 calls - -2) Capacity for 100 calls - -Diagram illustrating admission control policing. A green arrow labeled 'Direction of packet flow' points from left to right. Below it, a circle labeled 'CE' is connected to a circle labeled 'PE' by a horizontal line. A callout '1' points to the CE circle, and a callout '2' points to the PE circle. Below the PE circle, text reads '1) Allow BW of 100 calls' and '2) Capacity for 100 calls'. - -9 -10 -11 -12 **Figure 25-6: Admission control policing** - -13 -14 By pre-agreeing that the network can only sustain a certain number of calls, we can police the - 15 traffic arriving from the application, to the agreed level. In the case of the packet network, this - 16 means agreeing a sustainable bandwidth level and honouring that level at the point that we accept - 17 traffic from the application. - -18 -19 Once we have classified traffic to determine that it is indeed voice traffic, we can apply a policer to - 20 that traffic class to limit the amount of traffic that is accepted. If the application violates the agreed - 21 rate, the policer will drop some packets, forwarding only the rate that was previously agreed. It - 22 should be noted that for this particular application, again voice quality will suffer, however, the - 23 onus is now on the application to stay within the terms of the agreed contract for the benefit of its - 24 own service. - -25 -26 So, if by dropping traffic at admission to the network we will see the application service degrade, - 27 just as if we drop traffic in the middle of the network, why bother? Should we not simply let the - 28 traffic have access and hope there is sufficient capacity to support the application demand? - -![Diagram illustrating service protection through admission control. A Customer Edge (CE) node is connected to a Provider Edge (PE) node. A green arrow indicates the direction of packet flow from CE to PE. Three numbered points are marked: 1) on the CE side of the link, 2) on the PE side of the link, and 3) on the output interface of the PE. A legend below the diagram lists: 1) Allow BW of 60 sessions, 2) Allow BW of 40 sessions, 3) Capacity for 100 sessions.](2cdc3be3de33b97cdd52a0805b399419_img.jpg) - -Direction of packet flow - -1) Allow BW of 60 sessions -2) Allow BW of 40 sessions -3) Capacity for 100 sessions - -Diagram illustrating service protection through admission control. A Customer Edge (CE) node is connected to a Provider Edge (PE) node. A green arrow indicates the direction of packet flow from CE to PE. Three numbered points are marked: 1) on the CE side of the link, 2) on the PE side of the link, and 3) on the output interface of the PE. A legend below the diagram lists: 1) Allow BW of 60 sessions, 2) Allow BW of 40 sessions, 3) Capacity for 100 sessions. - -**Figure 25-7: Service protection through admission control** - -This is where the network level administration of QoS becomes relevant. Consider the same core network resource now being shared by two customers (Figure 25-7). If we recognise that the network can only sustain 100 calls, we can ask each customer to restrict their usage, customer 1 to 60 calls and customer 2 to 40 calls. By applying a policy that is specific to each customer context we can ensure that the available network resources are not exhausted, resulting in poor performance for all. - -If customer 1 exceeds their allocated capacity, some traffic will be dropped at point 1, resulting in poor quality for customer 1. However, if customer 2 continues to maintain their agreement not to exceed 40 calls, there will always be sufficient capacity to support their service without quality impairment. - -#### Weighted Random Early Discard (WRED) - -When looking at congestion management, the idea of a queue was introduced in order to store traffic that is awaiting transmission on an outgoing interface. In this previous discussion we saw that in a simple queue, when the queue is full, any additional traffic is “tail dropped” indiscriminately. - -For applications that are using a TCP connection over IP, the loss of one (or more) packets from the flow will cause the TCP algorithm to time out and request re-delivery of these missing packets. This also triggers the shortening of the TCP “ack window” resulting in lower throughput for that TCP session. As many TCP session may be impacted at once in a tail drop scenario, this can cause a number of sessions to “back off” reducing the total load on the interface, and the queue to be drained. - -Over time, the TCP sessions will re-open their ACK window, increasing bandwidth until the interface is once again full and the queue overwhelmed. The result is a sawtooth type bandwidth profile that oscillates around the maximum interface speed. This oscillation reduces the efficiency of the interface usage as there are periods where the interface is not full. - -Weighted Random early discard (WRED) is a modification to the queue drop behaviour that can help to eliminate this effect. The premise is to manage the acceptance of traffic into the queue in a more intelligent manner. - -![Figure 25-8: RED queue threshold diagram. A horizontal blue queue is shown with three green circles labeled 1, 2, and 3 pointing to different levels of fill. Circle 1 points to the empty queue (0% full), circle 2 points to the half-full queue (50% full), and circle 3 points to the full queue (100% full). To the right of the queue is a blue vertical rectangle representing an interface with a circular arrow, and further right is a blue cylinder representing a link.](b4cbe4bfe7868be70d1549b983749783_img.jpg) - -Figure 25-8: RED queue threshold diagram. A horizontal blue queue is shown with three green circles labeled 1, 2, and 3 pointing to different levels of fill. Circle 1 points to the empty queue (0% full), circle 2 points to the half-full queue (50% full), and circle 3 points to the full queue (100% full). To the right of the queue is a blue vertical rectangle representing an interface with a circular arrow, and further right is a blue cylinder representing a link. - -Figure 25-8: RED queue threshold - -Consider the queue in Figure 25-8, with three depths at 0% (1), 50% (2) and 100 % (3). - -As traffic arrives for the interface and the scheduler has no capacity available to forward them, the waiting packets are placed into the queue. Between queue depth 1 (0% full) and depth 2 (50% full), packets are added as normal to the queue. - -When the queue depth reaches the lower RED threshold (2) (50% in this example), rather than adding all new packets to the queue, some will be randomly dropped. The probability of dropping any given packet changes dependent on the current (and possibly historical) queue depth. As the depth of the queue increases, so does the probability of drop until at depth 3 (100% full) the probability of drop is 1 (always drop). - -The impact of this weighted behaviour is to slowly encourage individual TCP sessions flowing in the queue to find an appropriate TCP window (and hence bandwidth) such that the queue never saturates, and the link can continue flowing at 100% capacity, eliminating the sawtooth behaviour. - -#### Class based Weighted Random Early Discard - -We have seen it is possible to add traffic to a specific queue based on a classification, in order to differentiate between traffic types flowing in an interface. This allows us the flexibility to manage bandwidth to support different applications in an infrastructure. We have also seen that under some circumstances it might be possible to “borrow” bandwidth from one class to use in another class, in the event that the bandwidth in an interface is not fully used. - -It is possible to extend the idea differentiated behaviour for traffic from between queues, to within a single queue using the Weighted RED scheme. - -![Figure 25-9: Class based WRED function and behaviour diagram. On the left, a network diagram shows two circles labeled CE and PE connected by a line. Three green arrows labeled 1, 2, and 3 point to the PE node. Arrow 1 is from the top, arrow 2 is from the bottom, and arrow 3 is from the right. Above the diagram is a green arrow pointing right labeled 'Direction of packet flow'. On the right, a queue diagram shows a horizontal blue queue with four green circles labeled 4, 5, 6, and 7 pointing to different levels of fill. Circle 4 points to the empty queue, circle 5 points to a low fill level, circle 6 points to a medium fill level, and circle 7 points to a high fill level. To the right of the queue is a blue vertical rectangle representing an interface with a circular arrow, and further right is a blue cylinder representing a link.](29100fce6dce19cea57712363976bf2c_img.jpg) - -1) Sustain BW for 60 sessions, burst BW up to 100 sessions - 2) Sustain BW for 40 sessions, burst BW up to 100 sessions - 3) Capacity for BW associated with 100 sessions - -Figure 25-9: Class based WRED function and behaviour diagram. On the left, a network diagram shows two circles labeled CE and PE connected by a line. Three green arrows labeled 1, 2, and 3 point to the PE node. Arrow 1 is from the top, arrow 2 is from the bottom, and arrow 3 is from the right. Above the diagram is a green arrow pointing right labeled 'Direction of packet flow'. On the right, a queue diagram shows a horizontal blue queue with four green circles labeled 4, 5, 6, and 7 pointing to different levels of fill. Circle 4 points to the empty queue, circle 5 points to a low fill level, circle 6 points to a medium fill level, and circle 7 points to a high fill level. To the right of the queue is a blue vertical rectangle representing an interface with a circular arrow, and further right is a blue cylinder representing a link. - -Figure 25-9: Class based WRED function and behaviour - -Consider the PE node on the left of Figure 25-9, two CEs are sending EPOS traffic. The PE has capacity at (3) for 100 concurrent sessions. The number of sessions sent by each CE varies. CE 1 - -![O-RAN ALLIANCE logo](b3e29e133dd986546948ba4332cda172_img.jpg) - -O-RAN ALLIANCE logo - -has a minimum sustained rate of 60 sessions, and CE 2 has a minimum sustained rate of 40. Each has a possible peak rate of 100. - -As traffic arrives from CE 1 at point (1) the PE node classifies traffic as part of the EPOS application. It also measures the amount arriving and allows up to 100 sessions worth into the network. For traffic that exceeds the rate of 60 sessions, the node marks this traffic as having exceeded its contracted rate or “out of contract”. The same classification, policing and marking takes place at point (2) for CE 2 with a rate of 40 sessions. This extra marking is termed the discard class or DC. - -When the incoming packets arrive at the queue depicted on the right, again a decision is made prior to enqueueing the traffic. This time the decision is based on two criteria, the current queue depth AND the discard class of the packet as determined in the ingress policing and marking stages. - -A sample policy may behave as follows. For queue depth between 0% (4) and 33% (5) all traffic is enqueued. - -For traffic that is marked with the out-of-contract discard class marking, between queue depth 33% (5) and 66% (6) the drop probability varies from 0 to 1; that is at depth 66% (6) all traffic that is marked out of contract will be dropped. Traffic that is marked “in contract” will continue to be queued for transmission. - -For queue depths between 66% (6) and 100% (7) no out of contract traffic will be enqueued, and the drop probability for in contract traffic will increase from 0 to 1. - -It should be noted that the PE is not policing “sessions”, but simply the traffic associated with those sessions. The PE has no knowledge of the nature of the traffic sent by the CE (for example the membership of a specific packet to a specific session), other than the markings being examined. It should also be noted that traffic dropped at point (3) will contain packets associated with many or all of the sessions from the CE whose traffic is being marked “out-of-contract”. The impact of this is that all TCP sessions that lose traffic will again contract their TCP windows, with the effect of lowering the BW used by each session and so reducing the load on the network. - -This behaviour has the following benefits; - -1. both CE users 1 and 2 potentially have access to all the bandwidth at point 3 in the diagram when the other user is not consuming it. The network resources at 3 can be optimally used when demand from one user is high and the other is low. Compare this to the example in Service protection through admission control where the network resource at point 3 may be under used. -2. If a user constrains their traffic to within the contracted limit, they are guaranteed delivery, even under congestion caused by out-of-contract traffic being generated by other users. - -## 26 Annex E: Multicast Technologies background - -### Overlay multicast - -Overlay multicast refers to CE to CE multicast over the transport provider/underlay network. In the following example, CE1 is a First Hop Router (FHR) connecting to the source and CE2/3 are Last Hop Routers (LHRs) connecting to receivers. Receivers send IGMP/MLD joins towards the LHRs, who then send PIM joins towards their upstream routers PE2/3. If the PEs were connected by a LAN, PE2/3 would simply send PIM joins onto the LAN towards PE1. Since PEs are actually Provider Edge routers that are not directly connected and typically serve many VPNs, Overlay Multicast signalling is used to signal the overlay multicast state over, not through, the provider/underlay network. - -![Diagram illustrating multicast procedures. A source (src) connects to CE1, which connects to PE1. PE1 is connected to a cloud representing the underlay network. Inside the cloud, PE1 connects to PE2 and PE3. PE2 connects to CE2, which connects to a receiver (rcvr). PE3 connects to CE3, which connects to a receiver (rcvr). Arrows indicate the flow of PIM (Protocol Independent Multicast) and IGMP (Internet Group Management Protocol) messages. PIM messages flow from CE1 to PE1, then from PE1 to PE2 and PE3. IGMP messages flow from the receivers (rcvr) to CE2 and CE3, and then from CE2 and CE3 to PE2 and PE3 respectively.](0348dd87efbccba766e98138b073b499_img.jpg) - -Diagram illustrating multicast procedures. A source (src) connects to CE1, which connects to PE1. PE1 is connected to a cloud representing the underlay network. Inside the cloud, PE1 connects to PE2 and PE3. PE2 connects to CE2, which connects to a receiver (rcvr). PE3 connects to CE3, which connects to a receiver (rcvr). Arrows indicate the flow of PIM (Protocol Independent Multicast) and IGMP (Internet Group Management Protocol) messages. PIM messages flow from CE1 to PE1, then from PE1 to PE2 and PE3. IGMP messages flow from the receivers (rcvr) to CE2 and CE3, and then from CE2 and CE3 to PE2 and PE3 respectively. - -Figure 26-1: Multicast procedures - -### PIM-based overlay signalling for IPVPN - -The most straightforward way is to emulate a per-VPN pseudo LAN over the underlay network. The pseudo LAN is instantiated by a multicast GRE tunnel for the VPN. Every PE for the VPN joins that tunnel and can send both control plane (PIM messages) and data plane traffic over the tunnel. For example, multicast group 225.1.1.1 used for VPN1, 225.1.1.2 for VPN2, etc. - -This is referred to as PIM-MVPN and also commonly as Rosen-MVPN. It is documented in the historic RFC6037 and further in RFC6513 [121] (which documents both PIM- and BGP-based overlay signaling). - -Essentially, a PE runs PIM sessions over each pseudo LAN for each VPN. This is different from unicast, with which no per-VPN session is used. - -When there are a large number of VPNs, many PIM sessions and signalling (including message refreshes) are incurred so it does not scale well. Most implementations and deployments of PIM/Rosen-MVPN only use IP multicast tunnel in the underlay to emulate the pseudo LANs. - -### BGP-based overlay signalling for IPVPN and EVPN - -For BGP-based signalling, the overlay signalling is done by BGP just like unicast case. It is referred to as C-multicast signalling (C for Customer) in RFC6513 [121]. BGP-based signaling use unified methods for both unicast and multicast, and inherits all BGP scaling mechanisms and properties. - -Multicast (IP) VPN with BGP based overlay signalling is referred to BGP-MVPN. While RFC6513[121] covers both PIM-MVPN and BGP-MVPN concepts, BGP-MVPN specific encoding and procedures are specified in RFC6514 [122] . - -![O-RAN Alliance logo](59f59a425aab673dd9a76474db66a3c4_img.jpg) - -O-RAN Alliance logo - -BGP-MVPN also defines mechanisms to signal what type and instance of provider/underlay tunnels are used to transport overlay multicast traffic over the underlay, via Inclusive or Selective PMSI Auto-Discovery routes (often referred to as I/S-PMSI or x-PMSI routes). IP multicast, RSVP-TE P2MP, mLDP P2MP/MP2MP, Ingress Replication, BIER and future additions could all be used as underlay tunnels. - -EVPN BUM (Broadcast, Unknown unicast and Multicast) only uses BGP overlay signalling and is modelled after BGP-MVPN. It is specified in RFC7432 [123] and further in RFC9572 [169]. - -BGP-MVPN and EVPN BUM have been widely deployed and are often referred to as Next Generation MVPN (NG-MVPN). - -## Underlay multicast - -As mentioned above, overlay multicast traffic is transported via underlay multicast tunnels. Many tunnel types have been mature and widely deployed, but with Segment Routing and central control being widely adopted, it is necessary to review the pros and cons of various multicast technologies and see what is the best solution in the SR era. - -Traditionally, multicast requires per-tree state on all routers of a tree for efficient replication. PIM, RSVP-TE P2MP, mLDP P2MP/MP2MP are all signaling protocols to instantiate tree state on those routers, either from the tree leaves towards the tree root or vice versa. The new SR-P2MP (aka tree-sid) tunnels also requires per-tree state on all root/leaf and replication nodes, except that the signalling is directly from a central controller who also calculates the tree. - -Obviously, this does not go well with one principal of Segment Routing – no per-flow state inside the network. An alternative is Ingress Replication – the root tunnels individual copies directly to leaves so no per-tree state is needed inside the network. Since replication is done at the root, it is not efficient and does not work well for high fan-out high data rate cases. - -BIER (RFC8279 [134], RFC8296 [136]) is a new technology that achieves efficient replication w/o incurring per-tree state, so it is the ideal multicast solution for an SR network. However, it uses a new encapsulation and forwarding algorithm, so it requires new hardware. While this makes it difficult to deploy in non-greenfield networks, there are very well-designed brownfield deployment methods, and all major vendors have BIER implementation & hardware available/upcoming. - -For an SR network, an operator may prefer to remove all legacy multicast signaling – PIM/RSVP/mLDP and switch to controller-based tree calculation and signaling via either PCEP or BGP (i.e., SR-P2MP [draft-ietf-pim-sr-p2mp-policy [184]] [RFC 9524 [167]] or BGP-signaled IP/MPLS multicast [draft-ietf-bess-bgp-multicast-controller [179]). Notice that this still incurs per-tree state inside the network and the only real benefit is the central calculation of the tree based on many TE constraints/considerations. - -In summary, depending on many factors, multicast technologies can be considered in the following preference order: - -1. PIM or mLDP/RSVP-TE P2MP that are already deployed in existing network -2. Controller calculated/signalled IP multicast or mLDP/RSVP/SR-P2MP tunnel -3. BIER if enough routers in the network support it - -## MVPN/EVPN and Seamless MPLS/SR - -Given the vast scale of the transport network, a seamless architecture is used as described previously. In this architecture, two aspects have impacts to multicast: - -- Only border routers have routes to edge nodes (that connect to 5G NFs like RAN/UPF), while internal routers only have routes to the border routers. -- Different ASes/areas may support/prefer different types of underlay tunnels - -For a), to establish end-to-end underlay tunnels across those different ASes/areas, PIM RPF vector [RFC5496][111] or mLDP Recursive FEC [RFC6512][120] can be used – a leaf router looks up the route to the tree root, with the BGP protocol nexthop being a border router in the local area/AS. It then encodes that border router’s address in PIM/mLDP signaling so that internal routers will signal towards that border router instead of the original root. When that border router gets the signaling, it encodes the next border router’s address so that the internal routers in the next AS/area will signal towards the next border router, and so on so forth. - -An alternative solution for a) is use controller signaled multicast, since the routers become dumb forwarding devices programmed with forwarding state for the tunnels by the controllers. - -For b), MVPN/EVPN-BUM tunnel segmentation RFC7524 [125] and draft-ietf-bess-bgp-multicast-controller [179] can be used – MVPN/EVPN-BUM procedures will run on the border routers and the signaled tunnel type/identification are changed as MVPN/EVPN routes are re-advertised by the border routers, so that different tunnel types/instances are used in different ASes/areas. - -![Figure 26-2: Multicast diagram showing three scenarios for multicast tunneling across IGP areas.](710b805054943193bd9fd7674b0759f6_img.jpg) - -The diagram illustrates three multicast tunneling scenarios across three IGP areas (IGP Area 1, IGP Area 0, and IGP Area 2) connected by ABRs (ABR1 and ABR2). PE11 is in IGP Area 1, and PE21 and PE22 are in IGP Area 2. - -**Top Scenario: Three mLDP tunnels stitched by ABRs running MVPN procedures** - -- IGP Area 1: PE11 is connected to ABR1. The tunnel is labeled "I/S-PMSI, mLDP tunnel 1 rooted at PE11". -- IGP Area 0: ABR1 is connected to ABR2. The tunnel is labeled "I/S-PMSI, mLDP tunnel 2 rooted at ABR1". -- IGP Area 2: ABR2 is connected to PE21 and PE22. The tunnel is labeled "I/S-PMSI, mLDP tunnel 3 rooted at ABR2". - -**Middle Scenario: Single mLDP tunnel E2E, with recursive FEC for internal routers to resolve to upstream ABR (vs. root)** - -- IGP Area 1: PE11 is connected to ABR1. The tunnel is labeled "I/S-PMSI, mLDP tunnel 1 rooted at PE11". -- IGP Area 0: ABR1 is connected to ABR2. The tunnel is labeled "I/S-PMSI, mLDP tunnel 1 rooted at PE11". -- IGP Area 2: ABR2 is connected to PE21 and PE22. The tunnel is labeled "I/S-PMSI, mLDP tunnel 1 rooted at PE11". - -**Bottom Scenario: Single mLDP tunnel E2E, with different setup mechanisms in different areas** - -- IGP Area 1: PE11 is connected to ABR1. The tunnel is labeled "I/S-PMSI, mLDP tunnel 1 rooted at PE11, legacy signaling in area 1". -- IGP Area 0: ABR1 is connected to ABR2. The tunnel is labeled "I/S-PMSI, mLDP tunnel 1 rooted at PE11, controller 1 signaled in area 0". -- IGP Area 2: ABR2 is connected to PE21 and PE22. The tunnel is labeled "I/S-PMSI, mLDP tunnel 1 rooted at PE11, controller 2 signaled in area 2". - -Figure 26-2: Multicast diagram showing three scenarios for multicast tunneling across IGP areas. - -Figure 26-2: Multicast diagram - -## 27 Annex F: Transport network slicing solution for WG1 Slicing (informational) - -WG-1 is developing a slicing architecture contained in O-RAN.WG1.Slicing-Architecture-v07.00 [25]. It is a multi-phased effort based on the roadmaps of the different O-RAN working groups combined with use cases specified by O-RAN operators. The use cases are additive, so a slicing phase 2 environment must be able to concurrently support phase 1 and phase 2 use cases. - -This annex currently addresses the transport network solution needed to support the use cases in phase 1 and 2 of WG-1's slicing architecture [25]. There are potentially many ways a packet switched network can address the requirements outlined by WG-1, so this section has been presented as an example solution that uses capabilities defined in the main body of this document. This annex is inline with work done by IETF TEAS WG in draft-ietf-teas-5g-ns-ip-mpls dealing with a realization of IETF network slices for 5G networks using current IP/MPLS technologies ([178]). - -### WG-1 Phase 1 scope - -The role of the transport network in a 5G slicing scenario is to provide the necessary connectivity, isolation, and Quality of Service (QoS) so management, control and user plane traffic can flow between the mobile components, making up a slice, in an appropriate fashion. - -Figure 27-1 shows the use cases for slicing phase 1 in O-RAN.WG1.Slicing-Architecture-v07.00 [25]. - -![Figure 27-1: WG-1 Phase 1 use cases. A diagram showing network layers and traffic paths for three slices: MBB, mMTC, and NB-IoT. Layers include Core DC Central POP, Regional Zone Big POP, Collector Rural Mid POP, RAN Cluster POP, RAN BBU POP, and RAN RU POP. Latency requirements are shown for each layer. Traffic paths show UPF, Sec-GW, IPSEC, O-CU-UP, O-DU, BBU, and O-RU components with Split 2 IPSEC* and Split 7.2x connections. Labels 'Distributed' and 'Collocated' are used for O-DU and O-RU configurations.](f53d26a0d0ab96356a6ed4f869f8d64d_img.jpg) - -| Layer | Latency | MBB slice | mMTC slice | NB-IoT slice | -|-------------------------|-----------------|--------------------------------------------------|--------------------------------------------------|--------------------------------------------------| -| Core DC Central POP | <500km
<30ms | UPF
Sec-GW | UPF
Sec-GW | UPF
Sec-GW | -| Regional Zone Big POP | <150km
<15ms | IPSEC | IPSEC | IPSEC | -| Collector Rural Mid POP | <60km
<5ms | O-CU-UP | O-CU-UP | O-CU-UP | -| RAN Cluster POP | <30km
<2ms | | | | -| RAN BBU POP | <20km
<1ms | Split 2 IPSEC*
O-DU, BBU | Split 2 IPSEC*
O-DU, BBU | Split 2 IPSEC*
O-DU, BBU | -| RAN RU POP | | Split 7.2x
O-RU
(Distributed / Collocated) | Split 7.2x
O-RU
(Distributed / Collocated) | Split 7.2x
O-RU
(Distributed / Collocated) | - -Figure 27-1: WG-1 Phase 1 use cases. A diagram showing network layers and traffic paths for three slices: MBB, mMTC, and NB-IoT. Layers include Core DC Central POP, Regional Zone Big POP, Collector Rural Mid POP, RAN Cluster POP, RAN BBU POP, and RAN RU POP. Latency requirements are shown for each layer. Traffic paths show UPF, Sec-GW, IPSEC, O-CU-UP, O-DU, BBU, and O-RU components with Split 2 IPSEC\* and Split 7.2x connections. Labels 'Distributed' and 'Collocated' are used for O-DU and O-RU configurations. - -**Figure 27-1: WG-1 Phase 1 use cases** - -In slicing phase 1 the scope is: - -- Single Mobile Network Operator (MNO) and Transport Network Operator (TNO) who can be separate organizational entities or the same organizational entity. - -![O-RAN ALLIANCE logo](8b680f16d224d2d371ed781f38b4e798_img.jpg) - -O-RAN ALLIANCE logo - -- Single management and 3GPP and O-RAN control plane infrastructure for all slices. -- Three public geographically dispersed slices covering mobile broadband, mMTC and NB-IoT. -- Each cell site supports two radio deployments: 1) Distributed: The O-RU is in the cell site and the O-DU is in a data center, located across the transport access network. In this instance, the O-RAN 7.2x C/U protocols and procedures run across the transport access infrastructure. 2) Collocated: The O-RU and O-DU reside in the cell site. In this instance, O-RAN 7.2x protocols and procedures run locally in the cell site and Midhaul interfaces run across the transport access infrastructure. -- All three slices are present in all cell sites and all slices use both radio deployment options. - -Not illustrated in Figure 27-1, the following has been assumed or are limitations in slicing phase 1. - -- The transport network is multi-service and in addition to 5G needs to support: - - 3G and 4G mobile services - - Wireline services (consumer, enterprise, and wholesale) -- Mobile components connect directly to the transport network or reside in a data centre that connects to the transport network. -- O-RAN and 3GPP components present slices to the transport network or Data Center infrastructure via a discrete physical or logical Ethernet interface (VLANs). -- Data Centers, connected to the transport network, present slices to the transport network via logical Ethernet interfaces (VLANs). -- There is no slicing in phase 1 in Fronthaul and Midhaul due to lack of slicing support in these mobile components. -- For the transport network to support QoS appropriate to the QoS requirements of the mobile infrastructure, it is necessary for the O-RAN and 3GPP mobile components, in the Midhaul and Backhaul, to set the DSCP bits in the IP header of the GTP-U packets based on the importance of the user's traffic in the radio domain. In slicing phase 1 this is possible for Uplink and Downlink traffic in Backhaul but only for Downlink traffic in Midhaul. -- No multicast capability in required in slicing phase 1. -- Management architectures and interfaces to packet switched infrastructure for slicing are dealt with in O-RAN.WG9.XTRP-MGT.0-v04.00 “Management interfaces for Transport Network Elements v04.00”, July 2022[23] - -**NOTE:** This annex only covers 5G slice requirements, however transport network architects also need to consider the other network services outlined above when designing the transport network. - -![O-RAN ALLIANCE logo](d74c250a8e512a5480acc7b20ae0471c_img.jpg) - -**ORAN-WG9.XPSAAS.0-R005-v10.00** - -![Figure 27-2: 3GPP and O-RAN connectivity requirements for phase 1 slicing architecture](805f30f65cc9617bd3137c6e0b735595_img.jpg) - -The diagram illustrates the O-RAN architecture for network slicing. At the top, shared entities include Slice mgmt, Non-RT RIC, FH mgmt, Near RT RIC, and 5GC. These are connected via O1 and A1 interfaces. The control plane involves E2, F1-c, and Xn-c interfaces connecting the Near RT RIC, vO-CU-CP, and vO-DU. The user plane (F1-u, N3, N6, N9) shows a common vO-DU and vO-CU-UP, but with dedicated UPF and transport paths (N3, N6) for different slices, color-coded in green, orange, and pink. O-RUs are connected to the vO-DU via Open Fronthaul 7.2x U and C planes. A note mentions the O2 interface is not shown as it is a DC management interface. - -Figure 27-2: 3GPP and O-RAN connectivity requirements for phase 1 slicing architecture - -**Figure 27-2: 3GPP and O-RAN connectivity requirements for phase 1 slicing architecture** - -Figure 27-2 developed jointly between WG-1 and WG-9 shows the capabilities and transport connectivity requirements in slicing phase 1. Components and interfaces in the grey shaded box at the top of the figure are shared entities, while entities and interfaces shaded green, orange and pink at the bottom of the figure are dedicated to a slice. At the transport level the design in slicing phase 1 provides: - -1. A single O-RAN / 3GPP control plane for all slices. -2. Fronthaul service overlay is common for all slices. -3. Midhaul service overlay is common for all slices. -4. Sliced Backhaul user planes are presented to the transport network by mobile components via a discrete VLAN per slice. User plane traffic from each slice is carried in a discrete L3 VPN in the transport network. - -### WG-1 Phase 2 scope - -Figure 27-3 shows the new use cases introduced in slicing phase 2 in O-RAN.WG1.Slicing-Architecture-v07.00 [25]. - -© 2025 by the O-RAN ALLIANCE e.V. Your use is subject to the copyright statement on the cover page of this specification. 209 - -![O-RAN Alliance logo](4ad71ddb7c8022a7007934b745b36a96_img.jpg) - -O-RAN Alliance logo - -![Figure 27-3: WG-1 Phase 2 use cases diagram showing network architecture across different latency requirements and slice types.](89d5117b5c8c5209f100f1f0bf8ef540_img.jpg) - -The diagram illustrates the network architecture for WG-1 Phase 2 use cases, organized by latency requirements and slice types. - -- Latency Requirements:** - - Core DC Central POP: <500km, <30ms - - Regional Zone Big POP: <150km, <15ms - - Collector Rural Mid POP: <60km, <5ms - - RAN Cluster POP: <30km, <2ms - - RAN BBU POP: <20km, <1ms -- Slice Types:** - - MBB IPTV slice:** Features CDN, Application-driven, and (Secondary) Sec-GW, UPF components. Traffic flows through O-CU-UP, O-DU, BBU, and O-RU (Low Band and High Band). - - Enterprise Core slice:** Features Core breakout to Enterprise /public cloud and Sec-GW, UPF components. Traffic flows through O-CU-UP, O-DU, BBU, and O-RU (Low Band and High Band). - - Enterprise PC slice #1:** Features (Secondary) Sec-GW, UPF and Core breakout to Enterprise /public cloud components. Traffic flows through O-CU-UP, Sec-GW, UPF, Local breakout to Enterprise /public cloud, O-DU, BBU, and O-RU (Low Band and High Band). - - Enterprise PC slice #2:** Features Core breakout, Sec-GW1, UPF1, O-CU-UP, Sec-GW2, UPF2, and Local breakout components. Traffic flows through O-DU, BBU, and O-RU (Split 7.2x). -- Interfaces:** IPSEC is used between various components. Split 2 IPSEC\* and Split 7.2x are also indicated. -- Notes:** \*optional, IPSEC is mandatory for F1-C (not shown) - -Figure 27-3: WG-1 Phase 2 use cases diagram showing network architecture across different latency requirements and slice types. - -Figure 27-3: WG-1 Phase 2 use cases - -In slicing phase 2 the transport infrastructure needs to concurrently support the phase 1 and phase 2 use cases. Phase 2 use cases are: - -- MBB IPTV: Slice for IPTV with UPFs and CDNs located at regional and core DC levels -- Enterprise Core Slice: Slices for enterprise customers where the enterprise's UPF is located centrally. -- Enterprise Private Cloud Slice #1 and #2: Slices for enterprise customers where the enterprise's UPFs are in central and distributed locations. Two examples are shown; 1) UPFs are sited in either the RAN cluster PoP or the Collector Rural Mid PoP and the Core DC Central PoP. In this instance all UPFs share common backhaul and N6 networks. 2) UPFs are sited in Regional Zone Big PoP and the Core DC Central PoP. In this instance all UPFs share a common backhaul network but Distributed UPFs are used only for local breakout and the central UPFs are used only for centralised breakout. In this case their N6 networks are discrete logical networks. -- As per phase 1, each cell site may need to support a distributed and/or a co-located radio infrastructure. -- All phase 1 and phase 2 scenarios may be present in all cell sites and all slice types can potentially use both radio deployment options. -- Up to 1000 enterprise slices in total. - -Not illustrated in Figure 27-3, the following assumptions and limitations have changed moving from slicing phase 1 to slicing phase 2. - -- Slicing of the Midhaul user plane (F1-U interface) is supported in phase 2. This is achieved by presenting either a dedicated Ethernet interface or a separate VLAN interface per slice on O-DUs and the O-CU-UPs. Slicing phase 2 does not support fronthaul slicing. -- Midhaul mobile components associated with user plane traffic (O-DUs and O-CU-UPs) can set the DSCP bits in the IP header of the GTP-U packet for Uplink and Downlink traffic based on the importance of the user's traffic in the radio domain. -- Selection of UPFs for different traffic streams within a slice is the sole responsibility of the 3GPP mobile core. - -![Figure 27-4: 3GPP and O-RAN connectivity requirements for phase 2 slicing architecture. The diagram illustrates the network architecture for phase 2 slicing, showing shared and dedicated components. At the top, a grey shaded box labeled 'Common between slices' contains the O1, E2, A1, and 7.2x M-plane interfaces. The O1 interface connects to the Near RT RIC, which is further connected to the SMO/Non RT RIC and FH Mgmt. The E2 interface connects the Near RT RIC to the vO-CU-CP. The A1 interface connects the Near RT RIC to the 5GC. The 7.2x M-plane connects the vO-CU-CP to the vO-DU. The vO-DU is connected to two O-RUs via the Open Fronthaul 7.2x U and C planes. Below the grey box, three slices are shown, each with its own vO-CU-UP and UPF. The vO-CU-UP is connected to the vO-DU via the F1-u interface. The UPF is connected to the vO-CU-UP via the N3 interface. The UPF is also connected to the 5GC via the N6 interface. The N3 interface is labeled 'Dedicated to each slice'. The N9 interface is shown between the UPF and the 5GC. The O2 interface is not shown as it's a DC management interface.](028803093e6d1195c9c470b0abd490c6_img.jpg) - -Figure 27-4: 3GPP and O-RAN connectivity requirements for phase 2 slicing architecture. The diagram illustrates the network architecture for phase 2 slicing, showing shared and dedicated components. At the top, a grey shaded box labeled 'Common between slices' contains the O1, E2, A1, and 7.2x M-plane interfaces. The O1 interface connects to the Near RT RIC, which is further connected to the SMO/Non RT RIC and FH Mgmt. The E2 interface connects the Near RT RIC to the vO-CU-CP. The A1 interface connects the Near RT RIC to the 5GC. The 7.2x M-plane connects the vO-CU-CP to the vO-DU. The vO-DU is connected to two O-RUs via the Open Fronthaul 7.2x U and C planes. Below the grey box, three slices are shown, each with its own vO-CU-UP and UPF. The vO-CU-UP is connected to the vO-DU via the F1-u interface. The UPF is connected to the vO-CU-UP via the N3 interface. The UPF is also connected to the 5GC via the N6 interface. The N3 interface is labeled 'Dedicated to each slice'. The N9 interface is shown between the UPF and the 5GC. The O2 interface is not shown as it's a DC management interface. - -Figure 27-4: 3GPP and O-RAN connectivity requirements for phase 2 slicing architecture - -Figure 27-4 developed jointly between WG-1 and WG-9 shows the capabilities and transport connectivity requirements in slicing phase 2. Components and interfaces in the grey shaded box at the top of the figure are shared entities and interfaces, while entities and interfaces shaded green, orange and pink at the bottom of the figure are dedicated to a slice. At the transport level the design in slicing phase 2 provides: - -1. A single O-RAN / 3GPP control plane for all slices. -2. Fronthaul service overlay is common for all slices. -3. Sliced Midhaul and Backhaul user planes are presented to the transport network by mobile components via a discrete VLAN per slice. User plane traffic from each slice is carried in discrete L3VPN in the transport network. - -## WG-1 Phase 3 scope - -Figure 27-5 shows the new use cases introduced in slicing phase 2 in O-RAN.WG1.Slicing-Architecture [25]. - -![O-RAN Alliance logo](dd6ca069ca77109ad861ad55b7527083_img.jpg) - -O-RAN Alliance logo - -![Figure 27-5: WG-1 Phase 3 use cases. This diagram illustrates three network scenarios (Scenario C, Scenario C.1, and Scenario C.2) across different network layers, showing latency constraints and component placement. A vertical latency scale on the left shows typical ranges: Core DC to Regional Zone (<500km, <30ms), Regional Zone to Collector Rural (<150km, <15ms), Collector Rural to RAN Cluster (<60km, <5ms), RAN Cluster to RAN BBU (<30km, <2ms), and RAN BBU to RAN RU (<20km, <1ms). Scenario C shows a 'Core breakout' at the Regional Zone with O-CU-UP, Sec-GW2/UPF2, and Local breakout. Scenario C.1 shows a 'Core breakout' at the Collector Rural with O-CU-UP1, Sec-GW1/UPF1, Local breakout1, O-CU-UP2, Sec-GW2/UPF2, Local breakout2, and O-DU, BBU. Scenario C.2 shows two operator scenarios: Operator A with O-CU-UP1, Sec-GW1/UPF1, Local breakout1, O-DU1, BBU1, and O-RU; and Operator B with O-CU-UP2, Sec-GW2/UPF2, Local breakout2, O-DU2, BBU2, and O-RU. All scenarios lead to 'Phase 2' or 'Phase 3' at the RAN RU POP.](40135f3a8f5a6789225806e70870256d_img.jpg) - -Figure 27-5: WG-1 Phase 3 use cases. This diagram illustrates three network scenarios (Scenario C, Scenario C.1, and Scenario C.2) across different network layers, showing latency constraints and component placement. A vertical latency scale on the left shows typical ranges: Core DC to Regional Zone (<500km, <30ms), Regional Zone to Collector Rural (<150km, <15ms), Collector Rural to RAN Cluster (<60km, <5ms), RAN Cluster to RAN BBU (<30km, <2ms), and RAN BBU to RAN RU (<20km, <1ms). Scenario C shows a 'Core breakout' at the Regional Zone with O-CU-UP, Sec-GW2/UPF2, and Local breakout. Scenario C.1 shows a 'Core breakout' at the Collector Rural with O-CU-UP1, Sec-GW1/UPF1, Local breakout1, O-CU-UP2, Sec-GW2/UPF2, Local breakout2, and O-DU, BBU. Scenario C.2 shows two operator scenarios: Operator A with O-CU-UP1, Sec-GW1/UPF1, Local breakout1, O-DU1, BBU1, and O-RU; and Operator B with O-CU-UP2, Sec-GW2/UPF2, Local breakout2, O-DU2, BBU2, and O-RU. All scenarios lead to 'Phase 2' or 'Phase 3' at the RAN RU POP. - -**Figure 27-5: WG-1 Phase 3 use cases** - -WG1 phase 3 slicing doesn't introduce any new requirements on transport regarding DSCP handling. Both, WG1 phase 2 and WG1 phase 3 are based on the DSCP mechanism, in both midhaul and backhaul, as described with Phase 2. - -WG1 phase 3 slicing introduces more complex scenarios regarding placement of O-RAN components (Scenario C.1 in Figure 27-5), which doesn't change how the transport network is orchestrated, how the logical isolation between slices is realized with VPNs, or how the slices are handed-off to the transport network (VLAN hand-off). - -### Overall Packet Switched Transport Architecture - -In reading this annex the reader is expected to be fully familiar with the main body and other annexes in this document. The solution is based on a packet switched transport architecture illustrated in Figure 27-6.3 - -![Figure 27-6.3: Overall Packet Switched Transport Architecture. This diagram shows a layered transport architecture. The top layer is 'Transport SDN / Orchestration and Telemetry'. The second layer is 'Mobile Services: MP-BGP EVPN and L3VPN'. The third layer is 'Underlay transport fabric: MPLS or SRv6, QoS, timing'. Below these layers is a network topology consisting of 'Access' (connected to a radio), 'Pre-Agg', 'Aggregation', and 'Transport Core' nodes, each with a 'DC' (Data Center) connection. The 'Transport Core' is connected to 'Peering' and 'Cloud' services. At the bottom, two physical transport options are shown: 'Dark fibre / WDM' and 'Dark fibre / switched WDM'.](f86fbc9826e1910a39e36f7e62b568c2_img.jpg) - -Figure 27-6.3: Overall Packet Switched Transport Architecture. This diagram shows a layered transport architecture. The top layer is 'Transport SDN / Orchestration and Telemetry'. The second layer is 'Mobile Services: MP-BGP EVPN and L3VPN'. The third layer is 'Underlay transport fabric: MPLS or SRv6, QoS, timing'. Below these layers is a network topology consisting of 'Access' (connected to a radio), 'Pre-Agg', 'Aggregation', and 'Transport Core' nodes, each with a 'DC' (Data Center) connection. The 'Transport Core' is connected to 'Peering' and 'Cloud' services. At the bottom, two physical transport options are shown: 'Dark fibre / WDM' and 'Dark fibre / switched WDM'. - -![O-RAN Alliance logo](09e20531558819de932d1e53f83f7bc0_img.jpg) - -O-RAN Alliance logo - -**Figure 27-6 Packet switched transport for mobile Xhaul** - -It is a converged end to end packet switched infrastructure, beginning at the cell site, located in the edge of the access layer, and stretching to the core of the transport layer. The packet switching TNEs are IP/MPLS or SRv6, QoS enabled, high capacity, low latency devices interconnected by point-to-point Ethernet interfaces running at the full capacity of the Ethernet interface, typically using either point to point fibres or via a WDM infrastructure. It incorporates data centers suitably placed across the transport network infrastructure to support virtual and physical NFs associated with mobile and fixed services but also potentially the placement of “Application Functions” associated with value-add services and customer specific application. - -The logical architecture is based on a common underlay packet switching infrastructure based on either MPLS or SRv6 overlaid with an L2 / L3 service infrastructure (VPNs) that uses the capabilities of the underlay packet switched network to support the mobiles interfaces. - -The underlay packet switching infrastructure provides basic network services such as any-to-any connectivity between TNEs, scaling, fast convergence, shortest path and traffic engineered forwarding, packet-based Quality of Service (QoS) and timing. - -The service layer supports native Ethernet services, using EVPN technology and IP VPN services, using MP-BGP based L3VPNs. These services can utilise the facilities offered by the underlay packet switched infrastructure to support the different mobile interfaces in an appropriate fashion. Where possible transport services are built on an end-to-end basis without intermediate stitching / switching points within the transport infrastructure. This approach has been taken to minimise the transport service orchestration overhead. - -NOTE: The term MP-BGP L3VPNs is used throughout this annex. It refers to L3VPNs built using MP-BGP based on either RFC4364 [90] or RFC9252 [159] depending on whether the underlay technology is MPLS or SRv6. More details on the technology can be found in section 13 and Annex C: MP-BGP based L3VPNs of this document. - -## Underlay network for WG-1 slicing phase 1, 2 and 3 - -A packet switched network has extensive capabilities to support slicing. These are outlined in section 18. Slicing phase 1 is basic in nature with limited slicing capabilities in the O-RAN mobile components and the actual slices (mobile BB, MMTc, NB-IOT) are low priority and delay tolerant slices. In phase 2, some additional slice types are added (MBB IPTV, Enterprise Core, Enterprise Private Cloud), with more distributed 3GPP, O-RAN component and Application Functions (UPFs and CDNs can be located at regional and central DC levels), and more – but still not very critical – delay sensitivity (for example IPTV). Phase 3 adds even distribution possibilities. With this in mind, and more onerous slicing use cases in later phases, it is proposed to support slicing phase 1 and 2 in the transport network using: - -- Default IGP instances running in each underlay routing domain calculating shortest path routing based on IGP metrics. -- IGP supporting fast and loop free convergence. -- Inter-domain connectivity performed using either BGP, IGP redistributing or a PCE infrastructure. -- Management, control and user planes in phase 1 and 2 use shortest path routing between TNEs. I.e., the Service VPNs associated with each slice are not mapped to TE tunnels or Flex-algos in phase 1 or 2. - -![O-RAN Alliance logo](e600afc5acba7c01dcd3b8d0e40ccf79_img.jpg) - -O-RAN Alliance logo - -- QoS based on Diffserv model defined in RFC2475 [50] and outlined in section 14 and *Annex D: Quality of Service*. - -As the WG-1 slicing use cases and slicing capabilities within O-RAN equipment matures so more sophisticated forwarding techniques, such as SR-TE and Flex-algo may need to be utilised. Therefore, phase 3 introduces mapping between Service VPNs and transport planes, where each transport plane is realized via set of tunnels optimized for some common characteristics. For example, one transport plane could reflect set of tunnels optimized for latency (using latency link metrics for optimization), where another transport plane could group tunnels optimized for high capacity (but not necessarily low latency), using IGP metrics. Tunnels could be TE tunnels (RSVP, SR-TE, SRv6-TE), or different Flex-Algos. This approach might result in different path being taken by different slices. Please see Section 18.1 “Packet-switched underlay network” for discussion on how they can be applied and used to support slicing. - -NOTE: When designing and implementing the transport network Service Providers may want to anticipate more onerous slicing use cases and implement facilities such as Traffic Engineering, Flex-Algo from the outset. - -### Service Models for WG-1 slicing phase 1, 2 and 3 - -Management and control plane networks are needed to support the management, orchestration and monitoring of the transport network and the data center infrastructure. In addition to these “infrastructure components”, various management and control plane networks are needed for the management and control of the 5G 3GPP and O-RAN mobile environments. In the transport slicing architecture outlined, some management networks are discrete VPN entities, while others combine multiple management functions together in a single VPN entity. The reasoning behind these choices is outlined, but individual Service Provider’s need to assess their organizational needs and adjust accordingly. - -### Transport and DC management networks - -Both the transport network and the data center infrastructure are common capabilities used by a range of different services and in many organizations managed by different organizational groups. In this example the management networks for these two entities are separate, as shown in Figure 27-7. Both these management networks need to be set-up in advance on the transport network and are pre-requisites to building a slice across the transport network or instantiating VMs or containers within data centers. - -![Diagram of Transport network and Data centre management networks. The diagram shows four DC types (Far Edge DC, Edge DC, Regional DC, Central DC) connected to a central Transport Network cloud. Above the Transport Network are two management planes: the Transport management plane (blue) and the O2 interface plane (DC management) (yellow). Each DC is connected to the Transport Network, which is then connected to both management planes. Cell Sites are also connected to the Transport Network.](45e43022bd578b9de22acadf38122da9_img.jpg) - -Diagram of Transport network and Data centre management networks. The diagram shows four DC types (Far Edge DC, Edge DC, Regional DC, Central DC) connected to a central Transport Network cloud. Above the Transport Network are two management planes: the Transport management plane (blue) and the O2 interface plane (DC management) (yellow). Each DC is connected to the Transport Network, which is then connected to both management planes. Cell Sites are also connected to the Transport Network. - -**Figure 27-7: Transport network and Data centre management networks** - -#### Transport network management network - -A network wide in-band L3VPN is used for day-to-day management of the TNEs. Every TNE has a local network management interface with an associated network management IP address configured at installation. This is typically a loopback interface. Management protocols associated with TNE's configuration, monitoring and service orchestration are configured to use this interface as their source interface. The TNE's management interface is placed into a transport management network built using a MP-BGP L3VPN mapped to the underlay's default routing algorithm. The transport network management network can be designed as an any-to-any network, meaning that every entity within the L3VPN can connect to every other entity in the transport network management network but are more commonly built so that the central network management functions can communicate with the TNEs and vice versa but the TNEs cannot communicate with each other. - -In addition to the in-band management network Service Providers may also choose to have an out-of-band network for scenarios when in-band network connectivity has been lost. Various solutions exist, often based on access to the console port, through mobile, xDSL or PON technology. - -#### Data Centre (DC) management network - -In the packet switched transport architecture data centers are distributed around the transport network and although distributed they need to be managed centrally. The DC infrastructure supports "Network Functions" and "Applications Functions". Some functions are associated with the provision of 5G and O-RAN capabilities and services, but DCs should be considered common infrastructure facilities that support services beyond just 5G. The DC management network needs to support the O2 interface defined by O-RAN but also other data center management, monitoring and orchestration facilities. In the slicing phase 1, 2 and 3 the handoff between the DC and the transport network is via a logical Ethernet attachment circuit. The design of the management infrastructure within the DC is handled by WG-6, with connectivity between DCs and the central DC management infrastructure provided by the transport network. Each DC needs to hand-off the DC management network to a TNE via a logical Ethernet interface. On the TNE the logical Ethernet attachment circuit is placed into a MP-BGP L3VPN mapped to the underlay's default routing algorithm. This VPN connects all the DCs to the central DC management, monitoring and - -![O-RAN Alliance logo](81198a2bf24d5939ce9121693eaf7aa8_img.jpg) - -O-RAN Alliance logo - -orchestration functions. The DC management network can be designed as an any-to-any network, meaning that every entity within the L3VPN can connect to any other entity in the DC management network but are more commonly built so that the central network management functions can communicate with the DC components (servers and DC switches) and vice versa, but the DC components cannot communicate with each other. - -## O-RAN control and management networks - -The O-RAN control and management networks are illustrated in Figure 27-8. - -![Diagram of O-RAN control and management networks showing connectivity between management layers and various data centers via a transport network.](476bd53e2f910ac6842bec8208d70de5_img.jpg) - -The diagram illustrates the O-RAN control and management architecture. At the top, there are two horizontal oval layers: a pink one labeled "O-RAN control and management network (A1, E2, O1)" and an orange one below it labeled "Fronthaul Management Network (FH M-Plane)". Below these layers is a large grey cloud representing the "Transport Network". Within the transport network cloud, there are five circular nodes, each containing four arrows pointing outwards. One node is on the left, associated with "Cell Sites". The other four nodes are positioned above four rectangular boxes representing different types of Data Centers: "Far Edge DC", "Edge DC", "Regional DC", and "Central DC". Vertical lines connect the management network layers at the top to each of the five nodes in the transport network. Specifically, each node has two vertical lines connecting it to the management layers: one line (orange) goes to the Fronthaul Management Network and another line (pink) goes to the O-RAN control and management network. The nodes are also connected to their respective DC boxes or Cell Sites. - -Diagram of O-RAN control and management networks showing connectivity between management layers and various data centers via a transport network. - -**Figure 27-8: Fronthaul Management and O-RAN management and control networks** - -### O-RAN Fronthaul Management network (M-Plane) - -Based on guidance from WG-1, the O-RAN Fronthaul M-Plane interface is supported across the transport network as a dedicated VPN. This is discrete from the O-RAN Management and Control VPN that supports the O-RAN A1, E2 and O1 interfaces. The reasoning is Fronthaul management and O-RAN control and management may fall under different organizations within the Service Provider. - -Full details of Fronthaul M-plane can be found in section 7.1. The design outlined assumes the Fronthaul M-plane is operating in hybrid mode, where a central Fronthaul NMS needs IP connectivity to the O-DUs and the O-RUs. The O-RAN Fronthaul Management network in the transport network uses a MP-BGP L3VPN mapped to the underlay's default routing algorithm. The VPN needs to be present on all TNEs, through VLAN attachment circuits, that support O-RAN mobile components managed using the Fronthaul M-Plane. O-RAN mobile components that use the M-Plane need to connect to the O-RAN Fronthaul Management VPN, via a logical Ethernet interface, when they are installed or instantiated. - -The O-RAN Fronthaul Management VPN can be designed as an any-to-any network, meaning that every O-RAN component in the L3VPN can connect to any other entity in the O-RAN Fronthaul Management VPN, or more likely built so the M-Plane management components can communicate with the O-RUs and O-DUs but the O-RUs and O-DUs are restricted in their connectivity. - -![O-RAN Alliance logo](76177f18271e87e53ac3c915c7bfc63d_img.jpg) - -The logo for the O-RAN Alliance, featuring the word "O-RAN" in a stylized font with a colorful circular icon to the left, and the word "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -## 1 O-RAN Control and Management network (A1, E2, O1 interfaces) - -2 Based on guidance from WG-1, the O-RAN A1, E2, O1 interfaces are supported across the - 3 transport network as single VPN, discrete from the Fronthaul management VPN. The A1 and E2 - 4 interfaces are associated with the RAN Intelligent Controllers (RICs). The O-RAN architecture has - 5 two RIC entities: - -- 6 • Near-Real-Time RIC (Near-RT RIC). Near-RT RICs use the E2 interface to communicate - 7 with the O-CUs, and O-DUs they control. The interface controls the O-CUs and O-DUs with - 8 execution actions coming from the Near-RT RIC and feedback in the opposite direction. -- 9 - 10 • Non-Real-Time RIC (Non-RT RIC). Non-RT RICs use the A1 interface to communicate - 11 with the Near-RT RICs they control. The interface provides the Near-RT RICs with policies, - 12 enrichment info, and ML model updates. In the other direction the Near-RT RICs provides - 13 policy feedback to the Non-RT RIC. - -14 - 15 The O1 interface is associated with “Service and Management Orchestration”. This interface is an - 16 FCAPs interface with configuration, registration, security, performance, and monitoring - 17 responsibilities. - -18 - 19 The O-RAN Control and Management network in the transport network uses MP-BGP L3VPN - 20 technology, mapped to the underlay’s default routing algorithm. It needs to be present on all TNEs - 21 through VLAN attachment circuits, that support O-RAN components that use either the A1, E2 or - 22 O1 interfaces. All O-RAN components using these interfaces need to connect, via the TNEs, to the - 23 O-RAN Management and Control VPN when they are installed or instantiated. - -24 The O-RAN control and management VPN can be designed as an any-to-any network, meaning - 25 that every O-RAN component in the L3VPN can connect to any other entity in the O-RAN control - 26 and management VPN, or more likely built as a tiered VPN using a combination of Virtual Routing - 27 and Forwarding (VRFs) instances and Route Targets (RTs) so that: - -- 28 • SMO can communicate Near-RT RICs, O-CU-CPs, O-CU-UPs and O-DUs. -- 29 • Non-RT RIC can communicate with the Near-RT RICs. -- 30 • Near-RT RICs can communicate with the O-CUs, O-DUs and O-RUs. - -## 31 3GPP Control Plane network - -32 In slicing phase 1, 2 and 3 there is a single 3GPP core infrastructure running in a 3GPP control - 33 plane VPN across the transport network. See Figure 27-9 for details. It carries all the 3GPP control - 34 plane traffic associated with Midhaul and Backhaul including F1-C, E1, Xn-C, N1, N2, N4 for all - 35 slices. In the longer term it is expected that some 5G slices may have a dedicated 3GPP control - 36 plane, in these instances they could share the same transport VPN or utilise separate transport VPNs - 37 for each slice’s mobile core. - -![O-RAN Alliance logo](179dc105497e7283da7b3a6fda92b400_img.jpg) - -O-RAN Alliance logo - -![Diagram of Midhaul and Backhaul control plane network architecture. At the top, a purple oval represents the 'MH and BH Control plane Network (f1-c, E1, Xn-c, N1, N2, N4)'. Below it, a grey cloud represents the 'Transport Network'. Four 'Cell Sites' are shown as circles with four arrows, connected to the Transport Network. Below each Cell Site is a DC box: 'Far Edge DC', 'Edge DC', 'Regional DC', and 'Central DC'. Each DC box is connected to a Transport Network node (circle with four arrows), which in turn connects to the Transport Network cloud. All four DC boxes are also connected to the MH and BH Control plane Network oval.](29640f9496773db15b016e35bb17d5b8_img.jpg) - -Diagram of Midhaul and Backhaul control plane network architecture. At the top, a purple oval represents the 'MH and BH Control plane Network (f1-c, E1, Xn-c, N1, N2, N4)'. Below it, a grey cloud represents the 'Transport Network'. Four 'Cell Sites' are shown as circles with four arrows, connected to the Transport Network. Below each Cell Site is a DC box: 'Far Edge DC', 'Edge DC', 'Regional DC', and 'Central DC'. Each DC box is connected to a Transport Network node (circle with four arrows), which in turn connects to the Transport Network cloud. All four DC boxes are also connected to the MH and BH Control plane Network oval. - -**Figure 27-9: Midhaul and Backhaul control plane network** - -In slicing phase 1, 2 and 3 connectivity for the 3GPP control plane network across the transport network uses a MP-BGP L3VPN, mapped to the underlay's default routing algorithms. The 3GPP control plane VPN needs to be present on all TNEs via VLAN attachment circuits, where mobile components using the 3GPP control plane reside. All 3GPP mobile components using these control plane interfaces need to connect, via VLANs to the TNEs, to the 3GPP control plane VPN when they are installed or instantiated. - -The 3GPP control and management VPN can be designed as an any-to-any network, meaning that every 3GPP component in the L3VPN can connect to any other entity in the 3GPP control plane VPN, or more likely built with limited connectivity based on the mobile core connectivity requirements. - -## O-RAN and 3GPP user planes networks - -### Slicing Phase 1 - -Slicing phase 1 transport connectivity architecture for the O-RAN and 3GPP user planes is shown in Figure 27-10. The transport connectivity architecture is driven by two factors. - -- Fronthaul and midhaul do not support slicing -- UPFs for all slice types are positioned centrally - -![O-RAN Alliance logo](08727b263c6aa7f0934d66386f7174d1_img.jpg) - -O-RAN Alliance logo - -![Figure 27-10: Slicing Phase 1 O-RAN and 3GPP user plane networks. This diagram shows the network architecture for Phase 1. On the left, 'Cell Sites' consist of 'O-RU' units connected to 'O-DU' units. These are categorized into 'High band' and 'Low / mid band'. The 'O-DU' units connect to a central 'Transport Network' cloud. Above the transport network, several user plane slices are shown: 'CommonMH user plane(F1-u, Xn-u*)', 'BH User plane (MBB) (N3, N9)', 'BH user plane (mMTC) (N3, N9)', 'BH user plane (NB-IoT) (N3, N9)', 'N6 - mBB', 'N6 - mMTC', and 'N6 - NB-IoT'. Below the transport network, there are three main components: a 'Far Edge DC' containing an 'O-DU', a stack of three 'vO-CU-UP' units, and a stack of three 'UPF' units. All three are connected to the 'Transport Network'. On the far right, a 'Central DC' is also connected to the 'Transport Network'.](64ca20a7357e612f7c65bbe816032c8a_img.jpg) - -Figure 27-10: Slicing Phase 1 O-RAN and 3GPP user plane networks. This diagram shows the network architecture for Phase 1. On the left, 'Cell Sites' consist of 'O-RU' units connected to 'O-DU' units. These are categorized into 'High band' and 'Low / mid band'. The 'O-DU' units connect to a central 'Transport Network' cloud. Above the transport network, several user plane slices are shown: 'CommonMH user plane(F1-u, Xn-u\*)', 'BH User plane (MBB) (N3, N9)', 'BH user plane (mMTC) (N3, N9)', 'BH user plane (NB-IoT) (N3, N9)', 'N6 - mBB', 'N6 - mMTC', and 'N6 - NB-IoT'. Below the transport network, there are three main components: a 'Far Edge DC' containing an 'O-DU', a stack of three 'vO-CU-UP' units, and a stack of three 'UPF' units. All three are connected to the 'Transport Network'. On the far right, a 'Central DC' is also connected to the 'Transport Network'. - -Figure 27-10: Slicing Phase 1 O-RAN and 3GPP user plane networks - -## Slicing phase 2 and 3 - -Slicing phase 2 and 3 transport connectivity architecture for the O-RAN and 3GPP user planes is shown in Figure 27-11. The transport connectivity architecture changes to accommodate slicing in midhaul and distributed UPFs and the distribution of the N6 network closer to the radio sites. - -![Figure 27-11: Slicing phase 2 and 3 O-RAN and 3GPP user plane networks. This diagram illustrates the architecture for Phase 2 and 3. 'Cell Sites' with 'O-RU' and 'O-DU' units connect to a 'Transport Network' cloud. Above the transport network, there is a 'BH/MH Slice #1' and an 'N6 - slice #1'. The 'N6 - slice #1' extends deeper into the transport network and connects to 'Peering routers for breakout'. Below the transport network, the components are: a 'Far Edge DC' with an 'O-DU', a 'vO-CU-UP' unit connected to a 'UPF', a standalone 'UPF', and a 'Central DC'. All are connected to the 'Transport Network'.](c35369e1910a610d73fbdec77f65fd94_img.jpg) - -Figure 27-11: Slicing phase 2 and 3 O-RAN and 3GPP user plane networks. This diagram illustrates the architecture for Phase 2 and 3. 'Cell Sites' with 'O-RU' and 'O-DU' units connect to a 'Transport Network' cloud. Above the transport network, there is a 'BH/MH Slice #1' and an 'N6 - slice #1'. The 'N6 - slice #1' extends deeper into the transport network and connects to 'Peering routers for breakout'. Below the transport network, the components are: a 'Far Edge DC' with an 'O-DU', a 'vO-CU-UP' unit connected to a 'UPF', a standalone 'UPF', and a 'Central DC'. All are connected to the 'Transport Network'. - -Scaling ~100-1000 enterprise slices - -Figure 27-11: Slicing phase 2 and 3 O-RAN and 3GPP user plane networks - -This basic set-up can be used for all the phase 1 use cases and those introduced into phase 2 and 3, if midhaul slicing is supported. Each slice now has a single L3 VPN that concurrently supports midhaul and backhaul user plane traffic. Figure 27-11 also shows the N6 network extending deeper into the transport network. This is required, if distributed and centralised UPFs need to be able to access common applications or take advantage of local breakout. - -## Fronthaul C/U plane network - -In slicing phase 1, 2 and 3, slicing is not supported on O-RAN fronthaul components. In practical terms this means O-RUs and O-DUs are common across all slices and there is a single 7.2X eCPRI stream between the O-RU and O-DU which carries all the control and user plane traffic associated - -![O-RAN ALLIANCE logo](3cf228b7923919ad784bef3eeb0aebce_img.jpg) - -O-RAN ALLIANCE logo - -with all slices. The 7.2X C/U interface must support Ethernet encapsulation or optionally support Ethernet / IP encapsulation. Slicing phase 1, 2 and 3 use cases assume the Ethernet variant of the 7.2X protocol, meaning Ethernet connectivity needs to exist between O-RUs and the parent O-DU. Slicing phase 1, 2 and 3 use cases also assumes two radio deployments options: - -**Co-located O-RU and O-DU at cell site.** - -Ethernet connectivity needs to exist between the O-DU and the O-RUs and they both reside in the cell site. There are two options: - -- Direct point to point connectivity between the O-RU and the O-DU. In this case the transport network plays no part in the connectivity or the provision of an Ethernet service between the O-RU and the O-DU. -- Connectivity between the O-DU and O-RUs is via the “Cell Site Router” (CSR). In this case the Cell Site Router provides layer 2 bridging, or an L2 Ethernet cross connect function between the O-DUs port and the O-RUs port. See section 20.6 for more details. - -**O-RU and O-DU separated by access network** - -For distributed solutions, the O-RUs and the O-DUs are separated across the access portion of the transport network. In this instance, an Ethernet service needs to be created across the MPLS or SRv6 transport underlay. This Ethernet service can use either an E-Line or E-Tree service configured using EVPN over MPLS or SRv6. See sections 13.2 for more details. - -**Midhaul user plane network (F1-U and Xn-U)** - -**Slicing Phase 1** - -In slicing phase 1 slicing is not supported on Midhaul O-RAN mobile components. O-DUs and O-CU-UPs do not have a concept of slicing with the F1-U traffic from all slices originating and terminating on the same physical/logical interface and IP address on the O-DU. In scenarios, where the O-CU-UP is shared between two or more slices there is also no concept of slicing on the O-CU-UP. In situations, as shown in Figure 27-2, where the O-CU-UP is dedicated to a slice, then the O-CU-UP function will only receive and send traffic associated with that slice, however the O-CU-UP slice assignment and selection process is completely transparent to the transport network and under the control of the O-RAN / 3GPP control planes. For this reason, in slicing phase 1 a single MP-BGP L3VPN mapped to the underlay’s default routing algorithm is used across the transport network to support all Midhaul user plane traffic regardless of slice it belongs too. The L3VPN needs to be present on all TNEs and DC-TNEs that either connect directly or indirectly (through the DC infrastructure) to mobile components that support Midhaul user plane interfaces. Access to the Midhaul user plane VPN, on the TNEs, is via VLAN interfaces. - -A further challenge with Midhaul user plane interfaces in slicing phase 1 is the lack of a QoS mapping function on the O-DUs to map radio orientated QoS parameters, controlled by the 3GPP / ORAN control planes, to transport orientated DSCP QoS markings. The means the transport network QoS mechanisms must treat all uplink traffic the same, regardless of the importance of the data contained within Midhaul GTP-U packets. - -**Slicing Phase 2 and 3** - -Midhaul slicing and QoS is supported in slicing phase 2 and 3. F1-U traffic segregation is supported using a VLAN per user plane slice on the O-DUs and O-CU-UPs and QoS is supported by the O-DUs and O-CU-UPs setting a DSCP value appropriate to the importance of the user payload in the GTP-U packet. - -![ORAN Alliance logo](907205c224999d7da215523f7184b690_img.jpg) - -ORAN Alliance logo - -1 For slicing phase 2 and 3 this annex provides an example where midhaul and backhaul user plane - 2 traffic associated with a slice shares a single MP-BGP L3VPN that provides any to any - 3 connectivity. If an operator wishes to keep the midhaul and backhaul traffic separate then they - 4 could run each slice's midhaul and backhaul traffic in separate MP-BGP L3VPNs or alternatively - 5 use "Route Target" (RT) and BGP community filtering within a single L3VPN, so only backhaul - 6 mobile components can communicate with each other and only midhaul mobile components can - 7 communicate with each other. Examples of how this can be done are in the following section. - 8 - -#### 9 Slicing Phase 4 - -10 Since Slicing and Sharing utilizes similar toolbox in Transport Network domain, the RAN-Sharing - 11 via Midhaul" use-case analysis ([28]) captured by ORAN ATG and ORAN UCTG is included in - 12 Slicing Phase 4 of the current document scope. Transport Network isolation may be utilized for - 13 NPN 5G RAN-sharing architecture to support multiple operator's midhaul traffic. As shown in - 14 NPN RAN-sharing diagram in Figure 27-12, NPN RAN is shared and connected to multiple partner - 15 operator's O-CU via shared midhaul in Transport Network domain. - 16 - -![Figure 27-12: NPN RAN-sharing via midhaul. The diagram illustrates a network architecture where a Private Network (containing a 5G-RAN CU, 5G-Core, and Private MEC) is connected to the Internet. Below the Private Network, a Shared Private 5G-PHY (with PRB quota for each DU) is shown. This is connected to an O-RU (Multi-Band RF) and a Private Edge-Cloud. The Private Edge-Cloud contains two slices: 'Private DU-slice' and 'Shared Private 5G-PHY (with PRB quota for each DU)'. The 'Shared Private 5G-PHY' slice is connected to an 'MNO-1 DU Slice' which is further connected to an 'F1-Protection Proxy'. The 'F1-Protection Proxy' is connected to an 'F1 GW', which is connected to an 'MNO-1 Donor CU', which is connected to an 'MNO-1 Core'. The 'MNO-1 Core' is connected to the Internet. The 'Shared Private 5G-PHY' slice is also connected to an 'MNO-2 DU Slice' which is further connected to an 'IAB-Protection Proxy'. The 'IAB-Protection Proxy' is connected to an 'MNO-Cell-site', which is connected to an 'MNO-2 GW', which is connected to an 'MNO-2 Donor CU', which is connected to an 'MNO-2 Core'. The 'MNO-2 Core' is connected to the Internet. The 'MNO-1 Core' and 'MNO-2 Core' are both connected to a central 'MNO Central Cloud', which is connected to the Internet. The 'MNO-1 Donor CU' and 'MNO-2 Donor CU' are both connected to a 'MNO Regional Cloud', which is connected to the 'MNO Central Cloud'. The 'MNO-1 GW' and 'MNO-2 GW' are both connected to an 'MNO-Edge', which is connected to the 'MNO Regional Cloud'.](a25cc37578be51dfde4634f35f09aff3_img.jpg) - -Figure 27-12: NPN RAN-sharing via midhaul. The diagram illustrates a network architecture where a Private Network (containing a 5G-RAN CU, 5G-Core, and Private MEC) is connected to the Internet. Below the Private Network, a Shared Private 5G-PHY (with PRB quota for each DU) is shown. This is connected to an O-RU (Multi-Band RF) and a Private Edge-Cloud. The Private Edge-Cloud contains two slices: 'Private DU-slice' and 'Shared Private 5G-PHY (with PRB quota for each DU)'. The 'Shared Private 5G-PHY' slice is connected to an 'MNO-1 DU Slice' which is further connected to an 'F1-Protection Proxy'. The 'F1-Protection Proxy' is connected to an 'F1 GW', which is connected to an 'MNO-1 Donor CU', which is connected to an 'MNO-1 Core'. The 'MNO-1 Core' is connected to the Internet. The 'Shared Private 5G-PHY' slice is also connected to an 'MNO-2 DU Slice' which is further connected to an 'IAB-Protection Proxy'. The 'IAB-Protection Proxy' is connected to an 'MNO-Cell-site', which is connected to an 'MNO-2 GW', which is connected to an 'MNO-2 Donor CU', which is connected to an 'MNO-2 Core'. The 'MNO-2 Core' is connected to the Internet. The 'MNO-1 Core' and 'MNO-2 Core' are both connected to a central 'MNO Central Cloud', which is connected to the Internet. The 'MNO-1 Donor CU' and 'MNO-2 Donor CU' are both connected to a 'MNO Regional Cloud', which is connected to the 'MNO Central Cloud'. The 'MNO-1 GW' and 'MNO-2 GW' are both connected to an 'MNO-Edge', which is connected to the 'MNO Regional Cloud'. - -17 -18 **Figure 27-12: NPN RAN-sharing via midhaul** - -19 -20 Trusted and untrusted midhaul connection in which MNO's O-CU connects to shared NPN RAN- - 21 partition may be isolated using Transport Network L2/L3VPNs and other techniques from Network - 22 Slicing Framework of this document. - 23 - -#### 24 Backhaul user plane network (N3 and N9) - -25 WG-1 slicing phase 1, 2 and 3 includes user plane slicing in the backhaul network. In phase 1, 2 and - 26 3 it is assumed traffic associated with different slices originates from individual logical Ethernet - 27 interfaces on the O-CU-UPs backhaul interfaces and UPFs. These same slice mappings can be - 28 maintained across the transport network by mapping VLAN attachment circuits to different - 29 L3VPNs on the TNEs or DC-TNEs. Within the transport network MP-BGP L3VPNs can be built - 30 per slice or shared between slices depending how the mobile component present the slice traffic to - -![O-RAN Alliance logo](00d7e8859ad39a428b64fdba6fbcc269_img.jpg) - -O-RAN Alliance logo - -1 the transport network. For slicing phase 1 and 2 these L3VPNs are mapped to the underlay's default - 2 routing algorithm. In slicing phase 3, flex-algo or Traffic Engineering can be used to map L3VPN - 3 to different underlay transport planes. - -4 - 5 Backhaul L3VPNs (phase 1) or backhaul/midhaul L3VPNs (phase 2 and 3) associated with a slice - 6 needs to be present on all TNEs and DC-TNEs that either connect directly or indirectly (through the - 7 DC infrastructure) to mobile components supporting that slice. Access to the slice's L3VPN, on the - 8 TNEs, is via an VLAN attachment circuit. - -#### 9 Backhaul Transport Slicing - -10 A full description of MP-BGP based L3VPNs is contained in sections 13.3 and *Annex C: MP-BGP* - 11 *based L3VPNs*. MP-BGP based L3VPNs support flexible connectivity models and are highly - 12 scalable in terms of sites, VPNs and the number of VPN IP routes so able to - 13 deal with transport connectivity requirements associated with WG-1s slicing phases and the - 14 anticipated size of 5G environments. MP-BGP L3VPN's have two basic mechanisms for - 15 controlling connectivity within a L3VPN. - -- 16 • Virtual Routing and Forwarding (VRF) instances: These are local routing table associated - 17 with L3VPNs on Provider Edge (PE) TNEs. The VRF holds local and remote VPN routing - 18 information. Local routes are those learnt by the PE and normally consist of attachment - 19 circuits, routes learnt via routing protocols running over attachment circuits or via local - 20 static routing. Remote VPN routes are those learnt from remote PEs. They are conveyed - 21 between PEs using MP-BGP and held in the PE's BGP table. Installation of remote routes - 22 into the VRF routing table is determined by local policies. One of the key policy attributes - 23 used to determine what routes are installed into a VRF are Route Targets (RTs). -- 24 • Route Targets (RTs): RTs are a BGP attribute attached to VPN routes when they are - 25 distributed by MP-BGP from the PE where they were learnt. At the destination PE, filtering - 26 of routes based on RTs is one of the key mechanisms for determining what remote VPN - 27 routes are imported into a VRF. - -#### 29 Slicing Phase 1 - -30 Slicing phase 1 supports three general purpose 5G backhaul service slices which are network wide. - 31 For these simple slice use cases the design shown in Figure 27-13 could be used. - -![Diagram of Backhaul phase 1 slice design showing three slices (MBB, mMTC, NB-IOT) connected to PE routers via O-CU-UP units. The PEs are connected to MP-BGP Route Reflectors which are connected to UPFs and N6 interfaces for each slice. The diagram includes VRF and RT configurations for each slice.](6caa056e54d81c8403fe884e3c29fa66_img.jpg) - -The diagram illustrates the backhaul phase 1 slice design. At the top, two MP-BGP Route Reflectors are shown, connected to two PE routers. Each PE router is connected to three O-CU-UP units. The O-CU-UP units are connected to three separate backhaul slices: MBB (green), mMTC (orange), and NB-IOT (red). Each slice has its own VRF and RT configuration. The MBB slice is connected to a UPF and an N6 interface. The mMTC slice is connected to a UPF and an N6 interface. The NB-IOT slice is connected to a UPF and an N6 interface. The PEs are connected to the MP-BGP Route Reflectors via VPNv4 routes with slice RTs. - -**VRF Configuration boxes (left and right):** -MBB VRF: Import / export of MBB RT -mMTC VRF: Import / export mMTC RT -NB-IOT VRF: Import / export NB-IOT RT - -**Slices in the center:** -MBB Backhaul (N3/N9) Default forwarding plane (Green) -mMTC Backhaul (N3/N9) N3/N9 - default forwarding plane (Orange) -NB-IOT Backhaul (N3/N9) default forwarding plane (Red) - -**Interfaces on the right:** -MBB (N6) -mMTC (N6) -NB-IOT (N6) - -Diagram of Backhaul phase 1 slice design showing three slices (MBB, mMTC, NB-IOT) connected to PE routers via O-CU-UP units. The PEs are connected to MP-BGP Route Reflectors which are connected to UPFs and N6 interfaces for each slice. The diagram includes VRF and RT configurations for each slice. - -Figure 27-13: Backhaul phase 1 slice design - -- Three discrete VRFs associated with the phase 1 slices are created on PEs supporting slices. Alphabetic VRF names have been used in the illustration. In reality, VRF names could also be numeric values. - - VRF1: MBB - - VRF2: MMTC - - VRF3: NB-IOT -- Mobile components associated with each slice connects to the PE via a VLAN attachment circuit which is placed into the appropriate slice VRF. -- Each VRF on the PE learns local IP subnets containing the mobile slice components, either as connected routes, via a routing protocol or via static routes. -- A single RT is associated with each slice type. Alphabetic RT names have been used in the illustration. In reality, RT values are numeric values. - - VRF1: RT = MBB - - VRF2: RT = MMTC - - VRF3: RT = NB-IOT -- Routes from each slice's VRF are exported where they are learnt with their associated RT. -- On remote PEs each VRF imports the RT associated with their slice. -- This creates an any-to-any transport network allowing connectivity between all mobile backhaul components in the slice. - -NOTE: In many cases, Service Providers already use L3VPNs based on RFC4364 [90] and have their own methodologies for creating L3VPNs. In these instances, Service Providers could use their own VPN design methodology to create an any-to-any VPN for Backhaul slices. - -NOTE: This is a very simple transport slice architecture and suitable for general-purpose slices. More complex slice use cases may need different L3VPN topologies. The combination of VRFs, RTs and BGP communities and import and export filtering provides a powerful toolset to build these connectivity models. - -1 Slicing phase 2 and 3 - -2 The transport technology and mechanisms outlined above for slicing phase 1 are largely applicable -3 in slicing phase 2 and 3. - -![Figure 27-14: Backhaul phase 2 slice design diagram. The diagram shows a central cloud labeled 'Midhaul (F1-U) / Backhaul (N3/N9) transport slice1'. Above the cloud are 'MP-BGP Route Reflectors' connected to 'VPNv4/v6 routes with slice RTs'. Two boxes labeled 'Slice1 VRF: Import / export of slice1 RT' are connected to the route reflectors. Below the cloud, there are two 'O-DU' units connected to 'PE' routers, which are connected to the cloud. On the right, there are two 'UPF' units connected to a 'PE' router, which is connected to the cloud. At the bottom, an 'O-CU-UP' unit is connected to a 'PE' router, which is connected to the cloud. A 'UPF' unit is also connected to the 'O-CU-UP' unit.](8dd5c733658cf8d82fe930745b58994c_img.jpg) - -Figure 27-14: Backhaul phase 2 slice design diagram. The diagram shows a central cloud labeled 'Midhaul (F1-U) / Backhaul (N3/N9) transport slice1'. Above the cloud are 'MP-BGP Route Reflectors' connected to 'VPNv4/v6 routes with slice RTs'. Two boxes labeled 'Slice1 VRF: Import / export of slice1 RT' are connected to the route reflectors. Below the cloud, there are two 'O-DU' units connected to 'PE' routers, which are connected to the cloud. On the right, there are two 'UPF' units connected to a 'PE' router, which is connected to the cloud. At the bottom, an 'O-CU-UP' unit is connected to a 'PE' router, which is connected to the cloud. A 'UPF' unit is also connected to the 'O-CU-UP' unit. - -4 • -5 **Figure 27-14: Backhaul phase 2 slice design** - -6 -7 -8 The main differences are: - -- 9 -- A common midhaul/ backhaul MP-BGP L3VPN which extended to all TNEs and DC-TNEs containing midhaul and backhaul mobile components. - - Distributed UPFs also means the data network (N6) L3VPN may need to extend to distributed data centers. - - Up to 1000 slices, in addition to the three supported in slicing phase 1. -- 10 -11 -12 -13 -14 - -## 15 Data Network (N6) - -16 The data network or N6 is not part of the RAN and is not in scope of the WG-1 slicing work item. -17 However, transport slicing needs to extend to the N6 data network, particularly as the Data Network -18 (N6) network extends closer to the radio infrastructure with multiple breakout points and although -19 not discussed in this annex, the techniques outlined for the backhaul and midhaul user plane slicing -20 are largely applicable when building the data networks across a common packet switched transport -21 infrastructure. An important consideration when utilising multiple breakout points in the data -22 network (N6) is to ensure traffic exits the network in the desired place but also returning traffic -23 enters the data network (N6) in desired place. This requires UPF address block planning within the -24 data network, how these routes are advertised externally by the routers at the peering points and -25 how external routes are advertised within the Data network (N6). -26 - -## 27 Transport Network Quality of Service architecture - -28 Quality of Service (QoS) in the transport network in O-RAN phase 1, 2 and 3 is based on the -29 Diffserv architecture defined in RFC2475 [50] and further outlined in section 14 and *Annex D*: - -![O-RAN Alliance logo](1b068463b50162bd102d83e802c811ff_img.jpg) - -O-RAN Alliance logo - -1 *Quality of Service* of this document. The QoS architecture is widely implemented by Service - 2 Providers but there are significant differences between Service Providers in their QoS - 3 implementations. These include DSCP bit usage, edge policies, marking strategies, numbers of - 4 queues on the edge and within the core and how different Per Hop Behaviours (PHBs) are - 5 implemented. As such, this section aims to outline some of the key considerations associated with - 6 5G traffic and provide example QoS implementations. Service Providers can use this information to - 7 adjust their existing QoS architectures to support 5G. - -## 8 Transport QoS considerations in a 5G environment - -9 Section 7 outlines the 5G interfaces the transport network needs to support. In many areas the - 10 transport QoS requirements for 5G are very similar to existing 4G and general multi-service - 11 environments. However, there are some notable considerations and exceptions. - -- 12 • In the context of packet-based switching technologies for O-RAN and 3GPP, the interplay - 13 of QoS and transport slicing has two dimensions: 1) The QoS requirements of O-RAN - 14 fronthaul traffic 2) The QoS requirements of the mobile services, which depends on the kind - 15 of application being delivered to the end users. - 16 The transport slicing and QoS architectures needs to consider both dimensions to properly - 17 allocate QoS resources capable of satisfying the expected requirements for each kind of - 18 traffic in terms of bandwidth, latency, etc. -- 19 • O-RAN 7.2X Fronthaul Traffic: The user and control traffic stream is eCPRI based and runs - 20 between the O-RU and the O-DU. It is a new traffic type associated with 5G. The transport - 21 requirements of the Fronthaul user and control plane interfaces are contained in the O- - 22 RAN.WG9.CTRP-REQ-V01.00 [20] but can be summarised as high bandwidth and more - 23 importantly from a QoS perspective, extremely low delay (micro-seconds) traffic. Due to the - 24 low delay requirements this traffic type will only ever be seen in the access network and - 25 requires packet switching equipment to treat this traffic with the highest priority through the - 26 device and when scheduling onto attached interfaces. Today, many Service Providers use - 27 the highest priority queue for voice traffic, consequently, changes to the existing QoS - 28 schemes may be required. -- 29 • 5G introduces Midhaul: Midhaul interfaces run between the O-DUs and the O-CUs and - 30 between O-CUs. The F1 interfaces are a new set of interfaces associated with 5G, but use - 31 GTP-U and GTP-C which is the same packet types used in Backhaul. It is expected that - 32 Midhaul and Backhaul interfaces will have similar QoS requirements. -- 33 • 5G introduces new service types, each with their own QoS requirements. GTPv1-U [5] is - 34 used in the Midhaul and Backhaul for F1-U, Xn-U, N3 and N9 interfaces. The importance of - 35 user data packet within the mobile environment is indicated in the QoS Field Identifier - 36 (QFI)**Error! Reference source not found.** in the GTP-U extension header[5]. High - 37 performance TNEs do not have the capability to examine the QFI field and instead use the - 38 DSCP field in the IP header or the MPLS Traffic Class to understand the QoS requirements - 39 of packets in the transport network. For the transport network to be able to treat GTP-U - 40 packets in an appropriate fashion for the mobile service, the Midhaul (starting from O-RAN - 41 slicing phase 2) and Backhaul (starting from O-RAN slicing phase 1) mobile components - 42 (O-DUs, O-CU-UP and UPFs) must have mechanisms to set a DSCP value in the GTP IP - 43 header appropriate to the QoS requirements of the mobile service carried in the GTP-U - 44 packet. This could be achieved using a mapping mechanism on the Midhaul and Backhaul - 45 mobile components that map QFI values to DSCP values. - -46 - 47 NOTE: In O-RAN slicing phase 1, QFI to DSCP mapping facilities is a capability seen on Backhaul - 48 mobile component's (O-CU-UP (on backhaul side), UPF) user plane interfaces. In phase 2 and 3, - -![O-RAN Alliance logo](c43572681d8f7b8331d7b0510c81b1c7_img.jpg) - -The logo for the O-RAN Alliance, featuring a colorful circular icon to the left of the text "O-RAN" in a bold, sans-serif font, with "ALLIANCE" in smaller letters underneath. - -O-RAN Alliance logo - -QFI to DSCP mapping capability and associated management and control is enhanced to Midhaul mobile components (O-DU, O-CU-UP) user plane interfaces. - -### 3 3GPP QoS flows and Transport QoS - -The concept of QoS in 4G LTE is based on bearers, while the concept of QoS in 5G mobile systems is based on the QoS Flow concept [1] which provides finer granularity. Flows in 5G and 4G bearers can be divided into guaranteed bit rate flows (GBR QoS flows) and non-guaranteed bit rate flows (non-GBR QoS flows). 5G also has a new delay critical GBR flow category which is not present in LTE. QoS flows also have a service expectation which is expressed in terms of packet delay budget and packet error rate. The mobile QoS requirements are designated through the QoS Class Identifier (QCI) in LTE [2] and the 5G QoS Identifier (5QI) in 5G [2]. These identifiers can be operator defined but there is also a standardized list contained in [1]. Within the mobile domain traffic (of flows in 5G or bearers in LTE) with a given QCI or 5QI should receive the same forwarding treatment (e.g, in terms of scheduling, admission threshold, etc) - -**NOTE:** The majority of the QCI and 5QI are the same, with very few exceptions of identifiers being defined in one case but not in the other (e.g., QCI 75 or 5QI 10). - -TNEs in the transport network use DSCP or MPLS traffic class markings in the IP/MPLS header to determine QoS packet handling. To keep consistency of QoS treatment between the overlay mobile service and the underlay packet-based switching networks it is interesting to look at the different standard QCI and 5QI in qualitative terms to understand how distinct kind of flows (or bearers) at the mobile overlay level could be grouped together and treated on the underlay packet transport network. This equates to how different QCIs and QFIs could be mapped to DSCP markings on the 5G mobile components (RUs, DUs, CUs) and how these DSCPs are mapped to Diffserv Per Hop Behaviour (PHB) in the transport network. - -Figure 27-15 plots the standardized QCIs and 5QIs in relation to the defined packet loss and delay characteristics (Note, the figure is not to scale). Each box in the plot firstly contains the 5QI or QCI (top part) complemented with the values for delay / packet loss (at the bottom). To distinguish profiles, that are GBR, non-GBR or delay-critical GBR, a color code is used which is indicated in the legend of the figure (note that delay-critical GBR 5QI in 5G are simply GBR QCI in LTE). - -![O-RAN Alliance logo](5c0c0ffe0aa2bcd2d7f0a436f3c4674e_img.jpg) - -O-RAN Alliance logo - -![Figure 27-15: 5QI and QCI plot in relation to packet loss and delay. The plot shows various 5QI/QCI values on a graph of Packet loss (y-axis, logarithmic scale from 10^-8 to 10^-2) versus Delay (x-axis, linear scale from 0 to 100). A legend indicates GBR (white), Non-GBR (light orange), and Delay-critical GBR (yellow).](69af3542f800e9f0a3ea1d9bfbd07acb_img.jpg) - -Figure 27-15 is a scatter plot showing the relationship between Packet loss (Y-axis, logarithmic scale from $10^{-8}$ to $10^{-2}$ ) and Delay (X-axis, linear scale from 0 to 100). The plot includes various 5QI/QCI values, categorized into GBR (white), Non-GBR (light orange), and Delay-critical GBR (yellow). The legend indicates that Delay-critical GBR is denoted as GBR in QCIs. - -| 5QI/QCI-ID | delay / exp_PL | Category | -|------------|----------------|--------------------| -| 79 75 | 50 / -2 | Non-GBR | -| 65 | 75 / -2 | Non-GBR | -| 1 66 | 100 / -2 | Non-GBR | -| 3 | 50 / -3 | Non-GBR | -| 7 | 100 / -3 | GBR | -| 2 | 150 / -3 | Non-GBR | -| 67 | 100 / -3 | Non-GBR | -| 86 | 5 / -5 | Delay-critical GBR | -| 82 83 | 10 / -4 | Delay-critical GBR | -| 85 | 5 / -5 | Delay-critical GBR | -| 84 | 30 / -5 | Delay-critical GBR | -| 80 | 10 / -6 | Non-GBR | -| 69 | 60 / -6 | Non-GBR | -| 5 | 100 / -6 | Non-GBR | -| 71 | 150 / -6 | Non-GBR | -| 70 | 200 / -6 | Non-GBR | -| 72 | 300 / -4 | Non-GBR | -| 76 | 500 / -4 | Non-GBR | -| 4 | 300 / -6 | Non-GBR | -| 6 8 | 300 / -6 | Non-GBR | -| 73 | 300 / -8 | Non-GBR | -| 74 | 500 / -8 | Non-GBR | - -Figure 27-15: 5QI and QCI plot in relation to packet loss and delay. The plot shows various 5QI/QCI values on a graph of Packet loss (y-axis, logarithmic scale from 10^-8 to 10^-2) versus Delay (x-axis, linear scale from 0 to 100). A legend indicates GBR (white), Non-GBR (light orange), and Delay-critical GBR (yellow). - -Figure 27-15: 5QI and QCI plot in relation to packet loss and delay - -The plot identifies 5QI or QCI values with common QoS flow characteristics. It is now possible to group 5QI and QCI which require similar forwarding treatment in the transport network. Figure 27-16 presents a set of exemplary groupings, in which the 5QI/QCI are categorized into four distinct groups: group 1 consists of QoS flows requiring low delay, e.g., < 30 ms; group 2 consists of QoS flows which are in the delay range between 50 and 75 ms; group 3 consists of the rest of GBR 5QI/QCI; while finally group 4, as default group, aggregates the rest 5QI/QCI of non-GBR profile. - -![Figure 27-16: Exemplary 5QI and QCI grouping. This figure builds on Figure 27-15, showing four exemplary groupings: Exemplary grouping 1 (low delay), Exemplary grouping 2 (50-75 ms delay), Exemplary grouping 3 (GBR), and Exemplary grouping 4 - Default (rest of non-GBR).](bb22213587bd90f266a5003c78cb13d9_img.jpg) - -Figure 27-16 illustrates exemplary groupings for 5QI and QCI based on the plot in Figure 27-15. The groupings are: - -- Exemplary grouping 1:** QoS flows requiring low delay (e.g., < 30 ms). Includes 5QI/QCI values: 86, 82 | 83, 85, 84, 80. -- Exemplary grouping 2:** QoS flows in the delay range between 50 and 75 ms. Includes 5QI/QCI values: 79 | 75, 65. -- Exemplary grouping 3:** GBR 5QI/QCI. Includes 5QI/QCI values: 1 | 66, 3, 7, 2, 67. -- Exemplary grouping 4 - Default:** (for the rest not associated to other queues) Aggregates the rest 5QI/QCI of non-GBR profile. Includes 5QI/QCI values: 69, 5, 71, 70, 72, 76, 4, 6 | 8, 73, 74. - -Figure 27-16: Exemplary 5QI and QCI grouping. This figure builds on Figure 27-15, showing four exemplary groupings: Exemplary grouping 1 (low delay), Exemplary grouping 2 (50-75 ms delay), Exemplary grouping 3 (GBR), and Exemplary grouping 4 - Default (rest of non-GBR). - -Figure 27-16: Exemplary 5QI and QCI grouping - -Using the above example, a transport QoS architecture is illustrated in the next section that supports a set of transport core PHBs capable of supporting existing services, new 5G services, 5G fronthaul and protecting the infrastructure needed to deliver timing, OAM and the transport routing protocols. - -![O-RAN Alliance logo](8b84b62118ea6ad8627d8d157eb0f7df_img.jpg) - -O-RAN Alliance logo - -This annex makes no recommendations on QFI to DSCP mapping that needs to occur on the Midhaul (starting from O-RAN slicing phase 2) and Backhaul (starting from O-RAN slicing phase 1) mobile components, as there are huge variations between operators on their usage of DSCP markings. Viable approaches include: - -- A dedicated DSCP marking for some 5QI / QFI value. -- Group 5QI and QFI values, for example as shown above, and allocate all 5QIs and QFIs in the group the same DSCP value. -- A combination of the two. - -Regardless of the edge marking scheme chosen, the most important action occurs on the ingress TNE which needs to map the edge DSCP marking to the appropriate transport core marking (MPLS TC for MPLS underlays and DSCP for SRv6 underlays) to ensure the appropriate PHB in the core of the transport network. - -### Transport QoS Architecture for O-RAN slicing phase 1, 2 and 3 - -To ensure that Service Level Objectives (SLOs) requested for a particular slice are maintained, appropriate QoS scheme must be deployed in the transport network. - -The details of QoS functionality are provided in *Annex D: Quality of Service*. This section provides guidelines about particular use of the QoS concepts discussed in that annex to deploy the QoS architecture suitable for providing SLO guarantees for transport network slices. - -As outlined in Figure 27-17, the QoS model for transport network slicing has following major building blocks: - -- Ingress (input) policing (rate limiting) at the edge of the transport domain -- Mapping function at the edge of the transport domain to map potentially large number of edge traffic classes, as described earlier, into finite (typically 4 to 8) traffic classes used in the transport core -- Flat egress (output) scheduling (queuing) on the transport network transit links in the transport core with typically 4 to 8 traffic classes -- Egress (output) scheduling (queuing) at the edge – optionally hierarchical - -**NOTE:** Figure 27-17 is an example figure and for simplicity shows the traffic in one direction only (from UPF on the left-hand side to O-CU-UP on the right-hand side). However, traffic is typically bidirectional (for example UPF → O-CU-UP and O-CU-UP → UPF), therefore the building blocks mentioned earlier are deployed in opposite direction, too. Thus, all transport transit interfaces (transport core) should have flat egress (output) scheduling (queuing) deployed, whereas all transport edge interfaces would have input policing and potentially hierarchical output scheduling (queuing) deployed. Also, the figure shows only one type of interface (backhaul), in accordance with O-RAN slicing phase 1 requirements. Similar QoS concepts apply to other sliced interfaces, for example midhaul, starting from O-RAN slicing phase 2. - -![Figure 27-17: High-level QoS model for transport slices. The diagram illustrates the flow of traffic from multiple slices (VLAN 1 to 6) through a transport network domain. On the left, traffic from DC-X (UPF) is processed by an Edge TNE. The 'transport edge slice-aware ingress policing recommended' stage is shown. Traffic is then mapped via 'edge to core class mapping' into 'Transport Core Traffic Class 1' through 'Transport Core Traffic Class 8'. The 'transport core non slice-aware (flat) egress scheduling' stage follows. On the right, the 'transport edge slice-aware (hierarchical) egress scheduling optional' stage is shown, where traffic is directed to DC-Y (O-CU-UP) for the corresponding slices: Slice 1 (MBB Backhaul: N3/M9), Slice 2 (mMTC Backhaul: N3/N9), Slice 3 (NB-IOT Backhaul: N3/N9), Slice 4 (another slice), Slice 5 (another slice), and Slice 6 (another slice). The 'Transport Network Domain' is shown in the center with four circular nodes representing TNEs. Arrows indicate the 'traffic flow direction' from left to right.](afbd1c536e2ee87d33014bb58ab6d1c4_img.jpg) - -Figure 27-17: High-level QoS model for transport slices. The diagram illustrates the flow of traffic from multiple slices (VLAN 1 to 6) through a transport network domain. On the left, traffic from DC-X (UPF) is processed by an Edge TNE. The 'transport edge slice-aware ingress policing recommended' stage is shown. Traffic is then mapped via 'edge to core class mapping' into 'Transport Core Traffic Class 1' through 'Transport Core Traffic Class 8'. The 'transport core non slice-aware (flat) egress scheduling' stage follows. On the right, the 'transport edge slice-aware (hierarchical) egress scheduling optional' stage is shown, where traffic is directed to DC-Y (O-CU-UP) for the corresponding slices: Slice 1 (MBB Backhaul: N3/M9), Slice 2 (mMTC Backhaul: N3/N9), Slice 3 (NB-IOT Backhaul: N3/N9), Slice 4 (another slice), Slice 5 (another slice), and Slice 6 (another slice). The 'Transport Network Domain' is shown in the center with four circular nodes representing TNEs. Arrows indicate the 'traffic flow direction' from left to right. - -Figure 27-17: High-level QoS model for transport slices - -Subsequent subsections provide detailed discussion for each element in the QoS architecture for transport network slicing. - -## Edge QoS - -When the slice is created, mechanisms required to implement the slice in the transport network are deployed on the Transport Network Equipments (TNEs). An important building block is edge QoS to condition slice traffic at the transport edge and ensure that slice traffic does not exceed the previously requested and agreed bandwidth values. - -### Ingress policing - -Ingress policing (rate limiting) is used to police (rate limit) the traffic of a particular slice when the traffic enters the transport network domain. This slice admission control function is required to ensure, that only traffic contracted by given slice at the time of slice creation (or at the time of last slice modification) is accepted with SLO guarantees. - -**NOTE:** In the deployments where there is no expectation from the transport network to provide SLO guarantees (delay, jitter, bandwidth, no traffic interference between different slices, etc.) ingress policing might be omitted. - -Depending on the actual slice QoS profile requested at the slice creation/modification, out-of-contract traffic is either completely dropped at the transport network edge (if requested slice guaranteed rate and maximum rate are equal, or maximum guaranteed rate is missing in the request), or, if slice guaranteed rate is not equal to slice maximum rate, slice traffic is handled at the edge in following way: - -- Slice traffic under guaranteed rate: unconditionally accepted at the transport edge - -![O-RAN Alliance logo](31e08f7f7a48f3a4151828725b583a9b_img.jpg) - -O-RAN Alliance logo - -- Slice traffic above guaranteed rate and below maximum rate: conditionally accepted at the transport edge. Such traffic is marked at the transport edge with QoS marking (DSCP or MPLS Traffic Class bits) representing high drop probability. Using Class based Weighted Random Early Discard (CBWRED) functionality, described in *Annex D: Quality of Service*, and implemented on transit Transport Network Equipments, when the transit links are nearing the congestion (transmit queues on transit links are building up) CBWRED kicks in, and starts to drop packets marked with QoS marking representing high drop probability. Thus, when no congestion is observed in the transport network, slice traffic can go up to the contracted value (no drop at the transport edge for traffic volumes below slice maximum rate), but when congestion is close, high drop probability packets (above guaranteed rate but below maximum rate) are being dropped at transit. This ingress marking behaviour at the transport edge can be implemented with 2-rate 3-color policer. -- Slice traffic above maximum rate (or above guaranteed rate, if maximum rate is not specified during slice creation/modification): unconditionally dropped at the transport edge. This behaviour can be implemented with 1-rate policer (when slice guaranteed rate equals to maximum rate), or 2-rate 3-color policer (when different guaranteed and maximum rates are specified for the slice) - -There could be many reasons for misbehaving (send traffic above the contracted rates) slices, like for example: - -- Underestimate for slice traffic volume during slice creation (or slice modification) events -- Some failure within the slice, causing extra traffic generation -- Denial of Service (DoS) attack started from within the slice - -With slice admission control, implemented via ingress policing (rate limiting), it can be ensured that only legitimate in-contract slice traffic is allowed at the transport edge, thus slices that are sending traffic above the agreed rate do not negatively impact other slices. This provides traffic isolation guarantees between the different slices. - -**NOTE:** In O-RAN slicing phase 1, only per slice SLO parameters might be specified. There is no granular per class (per 5QI) SLO parametrization within each slice in phase 1. Therefore, in phase 1 of network slicing single policer (1-rate or 2-rate-3-color) per slice might be sufficient for slice admission control implementation. - -O-RAN slicing phase 2 introduces slices with multiple traffic classes (multiple 5QIs) within a single slice, like for example MBB with IPTV. Therefore, starting from slicing phase 2, more individual policers, or even hierarchical policers, might be introduced to implement slice admission control. - -### **Ingress Edge to core traffic class mapping** - -As described earlier multiple 5QIs, resulting in multiple DSCP markings, are potentially being used at the edge of the transport domain in the deployments. - -Transport core typically uses flat QoS model with up to 8 traffic classes. Therefore, mapping function to map multiple transport edge classes (represented by multiple 5QI/DSCP values) to limited set of transport core classes is implemented on the edge Transport Network Equipment as outlined in Figure 27-18. - -![Figure 27-18: Transport edge to transport core QoS mapping diagram. The diagram illustrates the mapping of traffic from six slices (VLAN 1 to 6) through transport edge ingress policing and classification into transport core (flat) egress scheduling. The mapping shows each slice being assigned to a specific transport core traffic class (1 to 8). Below this, a detailed view shows the packet structure at the transport edge, where slice identification is added to the ETH header, and transport edge QoS marking (VLAN PCP and IP DSCP) is retained. The packet is then encapsulated with new headers (ETH, MPLS, IP) added, where the MPLS header's TC field is used for transport core QoS marking. The payload is retained throughout the process.](931bd52904f67b17796a38b47af51e30_img.jpg) - -Figure 27-18: Transport edge to transport core QoS mapping diagram. The diagram illustrates the mapping of traffic from six slices (VLAN 1 to 6) through transport edge ingress policing and classification into transport core (flat) egress scheduling. The mapping shows each slice being assigned to a specific transport core traffic class (1 to 8). Below this, a detailed view shows the packet structure at the transport edge, where slice identification is added to the ETH header, and transport edge QoS marking (VLAN PCP and IP DSCP) is retained. The packet is then encapsulated with new headers (ETH, MPLS, IP) added, where the MPLS header's TC field is used for transport core QoS marking. The payload is retained throughout the process. - -Figure 27-18: Transport edge to transport core QoS mapping - -In case of MPLS encapsulation in transport core, the result of this transport edge to transport core class mapping is setting the Traffic Class (TC) field in outer MPLS label. If SRv6 is used as the encapsulation mechanism, DSCP field in the outer IPv6 header carries the transport core class marking, while DSCP field in the inner IPv4/IPv6 header, similarly to MPLS encapsulation, carried transport edge class marking. - -Transport Network Equipments (TNEs) associate transport core class markings, carried either in outer MPLS header TC field, or in outer IPv6 header DSCP field, with QoS output queues and execute appropriate scheduling mechanism to implement desired traffic prioritization during link congestion events. - -### Egress (hierarchical) scheduling - -On the egress side of transport edge, egress scheduling is implemented to provide desired traffic prioritization among the slices, as well as among traffic classes within each slice. Depending on the hardware capabilities of the edge Transport Network Equipment, as well as the intended granularity (more “soft” or more “hard”) of the enforcement, one of the following option can be used: - -- flat, non-hierarchical QoS model with up to 8 queues (similar to transport core QoS model) -- hierarchical, slice-aware QoS model with separate set of queues per each slice - -As described in the *Annex D: Quality of Service*, the hierarchical QoS scheduler model allows for a “hard” distribution of the bandwidth on an interface amongst the slices sharing that interface capacity, protecting the use of the bandwidth for a given slice from the other slices on the same interface. - -![O-RAN Alliance logo](1ef1e4c25366022dbdc6ae74f4c6dbfd_img.jpg) - -O-RAN Alliance logo - -## Core QoS - -Transport core QoS is based on a flat model with 4 to 8 queues. Transport core QoS settings are rather static in the nature, provisioned at the time the transport network infrastructure (interface settings, IGP settings, BGP settings, etc.) is provisioned. Especially, there is no direct correlation between transport core QoS and 5G slices being created/modified/deleted. Transport core QoS doesn't maintain any state related to individual 5G slice, neither adjust its QoS parameters based on 5G slices creation/modification/deletion events. - -The goal of transport core QoS is to ensure right prioritization of transport core traffic classes during congestion events caused by network failures and subsequent traffic rerouting, so that during such congestion events traffic classes requiring low latency are using priority forwarding, and traffic classes requiring low drop are not dropped. The goal of transport core QoS is not end-to-end bandwidth management or providing granular guarantees per each 5G slice. - -Table 9 contains a list of typical flows that can be observed in the multiclass transport network used to transport 5G flows as well, taking into considerations exemplary 5QI/QCI grouping described earlier in this annex. When recommending appropriate transport core QoS model, overall QoS policies for all flows must be taken into consideration. - -| Traffic type | Packet size
(order of magnitude) | Per-hop latency
(order of magnitude) 1) | Per-hop PDV
(order of magnitude) 1) | -|---------------------------------------------------------------------------------------------------------|-------------------------------------|-------------------------------------------------------|---------------------------------------------------| -| PTP (unaware mode) 2) | ~100 bytes | constant average | ~0.5 µs 3) | -| CPRI (RoE) | ~1500 bytes | ~1-20 µs | ~1-20 µs | -| eCPRI CU-plane | ~1500 bytes | ~1-20 µs | ~1-20 µs | -| OAM with aggressive timers | ~100 bytes | ~1 ms | ~1 ms | -| 5QI/QCI Group 1 (low latency U-plane) | variable | ~1 ms | ~1 ms | -| Low latency business traffic | variable | ~1 ms | ~1 ms | -| Network Control: OAM with relaxed timers, IGP, BGP, LDP, RSVP, PTP aware mode (T-TC/T-BC) 4) | variable | ~5 ms | ~1-3 ms | -| O-RAN/3GPP C-plane and M-plane 5) | variable | ~5 ms | ~1-3 ms | -| 5QI/QCI Group 2 (medium latency U-plane) | variable | ~5 ms | ~1-3 ms | -| 5QI/QCI Group 3 (remaining GBR U-plane) | variable | ~10 ms | ~5 ms | -| Guaranteed business traffic | variable | ~10 ms | ~5 ms | -| 5QI/QCI Group 4 (remaining non-GBR U-plane) | variable | ~10-50 ms | ~5-25 ms | -| Other traffic types (best effort) | | | | - -**Table 9: Different flows per-hop latency/PDV (order of magnitude)** - -**Note 1:** Per-hop latency includes all latency contributors, like frame transmission delay, self-queueing delay, queuing delay, store-and-forward delay, as described in section 10.1.1.2.1. Exact per-hop requirements depend on the overall network budget, number of hops, budget allocated to fibers, etc. The table intends to emphasize only relative order of magnitude for per-hop latency/PDV to illustrate the process of assigning traffic to QoS queues. - -**Note 2:** PTP unaware mode (i.e., router transiting G.8275.2 PTP stream, without T-TC function on the router that could add timestamps to transit PTP packets) → strict-priority queue is required to - -![O-RAN Alliance logo](2eb6e06f673af3339af5a7f0f89543ea_img.jpg) - -O-RAN Alliance logo - -minimize jitter (actual latency value is not relevant, but its average should be constant). Minimizing the latency via strict-priority queue minimizes jitter as well. - -**Note 3:** Max|TE| accumulated across the network must be $\leq 1.1 \mu\text{s}$ . - -**Note 4:** T-BC/T-TC (both G.8275.1 and G.8275.2) with physical layer time stamping $\rightarrow$ guaranteed bandwidth queue is OK, strict-priority queue is not required, since jitter/PDV will be accounted by physical layer timestamps in PTP packet. Also, latency value is not relevant, but average latency should be constant. QoS should ensure that PTP packets are not dropped during congestion, and guaranteed bandwidth queue is sufficient for that. - -**Note 5:** O-RAN/3GPP C-plane and M-plane kept in separate queue to ensure minimum bandwidth guarantees during congestion events preventing failures of these planes, as well as to increase security and separation of these planes. - -There are variety of QoS models, depending on the hardware support available on Transport Network Equipment platform. It is out of scope for this document to discuss all the various QoS models supported by different hardware platforms of Transport Network Equipments. However, for illustration purposes, two major, most common QoS models are worth to mention: with single priority queue, and with multiple priority queues. - -![Diagram of a QoS model with a single priority queue. It shows eight traffic flows entering a port through a scheduler. The first flow (CPRI (RoE), eCPRI CU-P, PTP unaware mode) is assigned to a Priority Queue (PQ) with a very high weight and mandatory PIR. The remaining seven flows are assigned to Bandwidth Queues (BQ) with varying weights and PIR values. The flows include OAM with aggressive timers (5QI/QCI Group 1), Network Control (IGP, BGP, LDP, RSVP, eCPRI S-P, PTP), O-RAN/3GPP C-plane and M-plane, 5QI/QCI Group 2, 5QI/QCI Group 3, spare capacity, and 5QI/QCI Group 4. The scheduler uses WFQ/WRR/WDRR/MDRR. Annotations indicate that the PQ is designed for ultra-low latency and that the PIR is mandatory to prevent starvation of other queues. The queue buffer size is aligned to maximum latency requirements.](b988d13a7e9ebb10a1df8e0957a15c51_img.jpg) - -Very high weight (BW over-dimensioning) to ensure frequent enqueueing in order to avoid queue congestion, and thus to keep queue latency to minimum - -Scheduler parameters - -PIR mandatory $\rightarrow$ to avoid starving of remaining queues - -Port - -Queue buffer size aligned to maximum latency requirements - -WFQ/WRR/WDRR/MDRR Scheduling - -PIR optional - -CPRI (RoE), eCPRI CU-P, PTP unaware mode PQ PIR - -OAM with aggressive timers, 5QI/QCI Group 1 (low latency U-plane), low latency business traffic BQ Weight PIR - -Network Control: OAM with relaxed timers, IGP, BGP, LDP, RSVP, eCPRI S-P, PTP (T-TC/T-BC) BQ Weight PIR - -O-RAN/3GPP C-plane and M-plane (e.g. eCPRI M-plane, other management) BQ Weight PIR - -5QI/QCI Group 2 (medium latency U-plane) BQ Weight PIR - -5QI/QCI Group 3 (remaining GBR U-plane), guaranteed business traffic BQ Weight PIR - -spare BQ Weight PIR - -5QI/QCI Group 4 (remaining non-GBR U-plane) Other best effort (may be guaranteed) BQ Weight PIR - -Diagram of a QoS model with a single priority queue. It shows eight traffic flows entering a port through a scheduler. The first flow (CPRI (RoE), eCPRI CU-P, PTP unaware mode) is assigned to a Priority Queue (PQ) with a very high weight and mandatory PIR. The remaining seven flows are assigned to Bandwidth Queues (BQ) with varying weights and PIR values. The flows include OAM with aggressive timers (5QI/QCI Group 1), Network Control (IGP, BGP, LDP, RSVP, eCPRI S-P, PTP), O-RAN/3GPP C-plane and M-plane, 5QI/QCI Group 2, 5QI/QCI Group 3, spare capacity, and 5QI/QCI Group 4. The scheduler uses WFQ/WRR/WDRR/MDRR. Annotations indicate that the PQ is designed for ultra-low latency and that the PIR is mandatory to prevent starvation of other queues. The queue buffer size is aligned to maximum latency requirements. - -**Figure 27-19: Example of QoS model with single priority queue** - -Figure 27-19 outlines an example QoS model with a single priority queue. In this hardware model, all flows with ultra-low latency/PDV sensitivity (PTP unaware mode, CPRI/RoE, eCPRI CU-plane) must be placed in this priority queue, while other flows should be distributed among remaining bandwidth queues. Bandwidth queue used for flows with low (but not ultra-low) latency/PDV sensitivity (OAM with aggressive timers, latency sensitive U-plane and business traffic) should be parametrized with relatively high weight used in WFQ/WRR/WDRR/MDRR (Weighted Fair - -![O-RAN Alliance logo](f5a92c55d9f25576d21e252a7d9e1b52_img.jpg) - -O-RAN Alliance logo - -Queueing, Weighted Round Robin, Weighted Deficit Round Robin. Modified Deficit Round Robin) scheduling algorithms, so that this queue is serviced very frequently, to avoid queue congestion and to minimize latency/PDV. With high weight parameterization this queue behaves almost as priority queue. - -To avoid starvation of the remaining queues during congestion events, priority queue, as well as highly over dimensioned bandwidth queue must have a policer or shaper to limit the rate (PIR – Peak Information Rate) of the queue. Queue buffer sizes in both cases must be aligned to maximum latency requirements of the traffic assigned to the queue. - -![Diagram of a QoS model with multiple priority queues. It shows a vertical stack of queues being scheduled by a 'Scheduler parameters' block. The queues are: 1. PTP unaware mode (PQ, PIR mandatory), 2. CPRI (RoE), eCPRI CU-P (PQ, PIR mandatory), 3. OAM with aggressive timers, 5QI/QCI Group 1 (low latency U-plane), low latency business traffic (PQ, PIR mandatory), 4. Network Control: OAM with relaxed timers, IGP, BGP, LDP, RSVP, eCPRI S-P, PTP (T-TC/T-BC) (BQ, Weight, PIR), 5. O-RAN/3GPP C-plane and M-plane (e.g. eCPRI M-plane, other management) (BQ, Weight, PIR), 6. 5QI/QCI Group 2 (medium latency U-plane) (BQ, Weight, PIR), 7. 5QI/QCI Group 3 (remaining GBR U-plane), guaranteed business traffic (BQ, Weight, PIR), 8. 5QI/QCI Group 4 (remaining non-GBR U-plane) other best effort (may be guaranteed) (BQ, Weight, PIR). A vertical label 'Priority Scheduling' is next to the first three queues, and 'WFQ/RR/DRR Scheduling' is next to the last five. All queues feed into a single 'Port' output. A note at the bottom states 'Queue buffer size aligned to maximum latency requirements'.](7d675e1c380dccba3f69e2de4e72562c_img.jpg) - -Diagram of a QoS model with multiple priority queues. It shows a vertical stack of queues being scheduled by a 'Scheduler parameters' block. The queues are: 1. PTP unaware mode (PQ, PIR mandatory), 2. CPRI (RoE), eCPRI CU-P (PQ, PIR mandatory), 3. OAM with aggressive timers, 5QI/QCI Group 1 (low latency U-plane), low latency business traffic (PQ, PIR mandatory), 4. Network Control: OAM with relaxed timers, IGP, BGP, LDP, RSVP, eCPRI S-P, PTP (T-TC/T-BC) (BQ, Weight, PIR), 5. O-RAN/3GPP C-plane and M-plane (e.g. eCPRI M-plane, other management) (BQ, Weight, PIR), 6. 5QI/QCI Group 2 (medium latency U-plane) (BQ, Weight, PIR), 7. 5QI/QCI Group 3 (remaining GBR U-plane), guaranteed business traffic (BQ, Weight, PIR), 8. 5QI/QCI Group 4 (remaining non-GBR U-plane) other best effort (may be guaranteed) (BQ, Weight, PIR). A vertical label 'Priority Scheduling' is next to the first three queues, and 'WFQ/RR/DRR Scheduling' is next to the last five. All queues feed into a single 'Port' output. A note at the bottom states 'Queue buffer size aligned to maximum latency requirements'. - -Figure 27-20: Example of QoS model with multiple priority queues - -Figure 27-20 outlines an example of queue assignment on hardware platforms supporting multiple priority queues, dequeued in strict priority order. With multiple priority queues available it is recommended to place PTP packets in unaware mode in the highest priority queue, to minimize the PDV of these packets to the highest possible degree. Putting these packets above CPRI(RoE) or eCPRI has only minimal influence on CPRI/eCPRI packets PDV, since PTP packets are very small (~100 bytes). For example, serialization delay of such small packet on 10 GE interface is only 80 ns, so PDV factor contributing to CPRI/eCPRI PDV is very small as well and can be easily handled by the CPRI/eCPRI reassembly functions. \ No newline at end of file diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/00504fc688ebcf131ccbeff94dfc9939_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/00504fc688ebcf131ccbeff94dfc9939_img.jpg deleted file mode 100644 index ed7c39390e8c33bd90d8a825e6c721a94b6ba39e..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/00504fc688ebcf131ccbeff94dfc9939_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4f9ae6f7a3e4134fb67edd29018288bc84eab514f84e9b303a1aad7a409a4905 -size 37059 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/00a0b3a0485d8e735df9cb73dbdf36d6_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/00a0b3a0485d8e735df9cb73dbdf36d6_img.jpg deleted file mode 100644 index c48e03de433ef977afd598d05aa1fc67cdb8248e..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/00a0b3a0485d8e735df9cb73dbdf36d6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:845d1748f3026dca519d6b3f7ba25ad4ecca756bb8ecdf437112f34730bf8f35 -size 97770 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/00c0ab3499a5b8f3290a0f6faa14fd62_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/00c0ab3499a5b8f3290a0f6faa14fd62_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/00c0ab3499a5b8f3290a0f6faa14fd62_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/00d7e8859ad39a428b64fdba6fbcc269_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/00d7e8859ad39a428b64fdba6fbcc269_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/00d7e8859ad39a428b64fdba6fbcc269_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/01c8a7aebdecdae1e64430198a8e4b8c_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/01c8a7aebdecdae1e64430198a8e4b8c_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/01c8a7aebdecdae1e64430198a8e4b8c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/023d970f080d18a5ec7578ebb73205b4_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/023d970f080d18a5ec7578ebb73205b4_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/023d970f080d18a5ec7578ebb73205b4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/028803093e6d1195c9c470b0abd490c6_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/028803093e6d1195c9c470b0abd490c6_img.jpg deleted file mode 100644 index c9ac0b014d00b2d44d94e855e8a3b7894c6d3e7c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/028803093e6d1195c9c470b0abd490c6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1f27a9f1ba111e4fd8d4d9852d2e16a606c932b57b82edbde4081c5c2e2308cc -size 90146 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/02917cf4d4af3d6e32df094efdeceb85_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/02917cf4d4af3d6e32df094efdeceb85_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/02917cf4d4af3d6e32df094efdeceb85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg deleted file mode 100644 index eba57a72e2662c7c2671b67a3e07f0dd8584021f..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/02bb4edc0dbdf4f0749ffd3e0ea2805c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0d7a4b07d7cbc087778ac5a4d4672bb53cdf6391a66a6492d594cd0b0ccffc08 -size 25278 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0348dd87efbccba766e98138b073b499_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0348dd87efbccba766e98138b073b499_img.jpg deleted file mode 100644 index 54434be640bd7e6117aefa78c07dd71d6d9aab19..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0348dd87efbccba766e98138b073b499_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:738721682729bf16ca76e96db4c769e9f5d9afdacbf75d0bac587878e51d87a6 -size 16430 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/04238bd6d89845c9012e10d19d0e2b1f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/04238bd6d89845c9012e10d19d0e2b1f_img.jpg deleted file mode 100644 index fb592ec5f896c960fb1da699c456aa39e6b78587..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/04238bd6d89845c9012e10d19d0e2b1f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:330a9955c1919a9d95ba23be84432fbf4f4499b6623b05a2996a2712a82d32c6 -size 84462 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/04d754e7c00513e29cda362aae421ecf_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/04d754e7c00513e29cda362aae421ecf_img.jpg deleted file mode 100644 index 5e7947994cd13e250d9c0d52ef65603522742aeb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/04d754e7c00513e29cda362aae421ecf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106e9e22973ca4ce0c1f258162dc414bc5bb34b1da32f3c4eabcbfc9045381bf -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/052543d8c9c0643b05b3ce45c6decca1_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/052543d8c9c0643b05b3ce45c6decca1_img.jpg deleted file mode 100644 index 6af380f5d6e1d80218afaad2f025448f0bbe22a5..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/052543d8c9c0643b05b3ce45c6decca1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:67c368cb4b9ae3a96cbe9a5cdd7edd8c1f5dfdd62412dc68154bf2ebf95ed9e7 -size 39092 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/07084c9c570a88714025135af11324a0_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/07084c9c570a88714025135af11324a0_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/07084c9c570a88714025135af11324a0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0726a03ffb4e106eb90cd4f9283a6347_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0726a03ffb4e106eb90cd4f9283a6347_img.jpg deleted file mode 100644 index 4e06a2e5ad305f6864d3c8069f01411bad330cc6..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0726a03ffb4e106eb90cd4f9283a6347_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f58b26986b1a813f7c8282506beffca16a4fd9f65f02385e30cfe5e4714aaa7f -size 56104 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/08727b263c6aa7f0934d66386f7174d1_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/08727b263c6aa7f0934d66386f7174d1_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/08727b263c6aa7f0934d66386f7174d1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0908107b858fa3783d10d93b3a3444b2_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0908107b858fa3783d10d93b3a3444b2_img.jpg deleted file mode 100644 index e2daf30875920363c4ff4a5675f2e58db78d95fb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0908107b858fa3783d10d93b3a3444b2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3459f39885ee47b84223a48bc0b19b8e11629fcd83c3838cb46c02fa18619c18 -size 34982 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/09e20531558819de932d1e53f83f7bc0_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/09e20531558819de932d1e53f83f7bc0_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/09e20531558819de932d1e53f83f7bc0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0a7136b9ffcd39128eaeb609dbfe8913_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0a7136b9ffcd39128eaeb609dbfe8913_img.jpg deleted file mode 100644 index 5e7947994cd13e250d9c0d52ef65603522742aeb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0a7136b9ffcd39128eaeb609dbfe8913_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106e9e22973ca4ce0c1f258162dc414bc5bb34b1da32f3c4eabcbfc9045381bf -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0aa6d2e44e40087639a801a32a28c781_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0aa6d2e44e40087639a801a32a28c781_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0aa6d2e44e40087639a801a32a28c781_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0da1791dc35edbc72e4339dab00d837c_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0da1791dc35edbc72e4339dab00d837c_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0da1791dc35edbc72e4339dab00d837c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg deleted file mode 100644 index 5c5460528e299724514c0d408c22105840c8d86c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0dfdff10c725fe9c332b07ade9d23a5e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:827fde5fd3809a09c2ffb3685a5f0f15862a8f3e21c93e259b5026c165a95203 -size 73485 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0eb348bf17d67bf96326e07011d1c1ad_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0eb348bf17d67bf96326e07011d1c1ad_img.jpg deleted file mode 100644 index 669fa65fa0c1546454e4be6b91791b3b82b5cc67..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0eb348bf17d67bf96326e07011d1c1ad_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ca4432ed64991bff8bcc82d5787d756768ca12a853b7292e31c70b301a14a8 -size 51240 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0f666d2ebbad7fab84c7c4fb531ea932_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0f666d2ebbad7fab84c7c4fb531ea932_img.jpg deleted file mode 100644 index 180b17c9aff6375176ea0c8269be06bb84e01ec2..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/0f666d2ebbad7fab84c7c4fb531ea932_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:af4127d4569c89ba1d5b7d54ac97356d494d0a39c2102dec280f33d2580a240e -size 40976 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/10ceb47973510a1b47421741263146cc_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/10ceb47973510a1b47421741263146cc_img.jpg deleted file mode 100644 index 4adc44e11ad23041555b8df60ddf597ae228a123..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/10ceb47973510a1b47421741263146cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6312072f33be9e5cd0d5d423cccde0074ee034f2bc477370476782aef7020324 -size 53568 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1139a11eee3dff36e1ab41fe7b2e862f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1139a11eee3dff36e1ab41fe7b2e862f_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1139a11eee3dff36e1ab41fe7b2e862f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg deleted file mode 100644 index 0e570ba0748a6164798a3f69e8a29edbb4359c29..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1174e0fd3f2c73de8e5c6ce8ea6bdda1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3b85561859df14bca045e188f938f6126cac20bff6fb8cb1603ab6735fb0c0ca -size 31187 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/12edb7d16ea770557899e1b08deeae34_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/12edb7d16ea770557899e1b08deeae34_img.jpg deleted file mode 100644 index 36ef3d74a3d5e4efe9fec01045563095b19fd7d1..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/12edb7d16ea770557899e1b08deeae34_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b1a6852cd7287d6175343848889237b93d25d25bfb27faa3838c8f239aa96286 -size 4546 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/13167dabf1b789d860061e607fa23acb_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/13167dabf1b789d860061e607fa23acb_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/13167dabf1b789d860061e607fa23acb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/137bcfed81ada68ca5162ca5afed35c7_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/137bcfed81ada68ca5162ca5afed35c7_img.jpg deleted file mode 100644 index 981ae1c2490e7b28a4f89085ff66248b210c562f..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/137bcfed81ada68ca5162ca5afed35c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:006f320d01bf4c09fa64009465409177d1b687000529a2a7bf4fcad5629daf3f -size 60390 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/145d00f59802048185303f15937ea65c_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/145d00f59802048185303f15937ea65c_img.jpg deleted file mode 100644 index 6c887f3ec41d85b7626d5c3a06809f0771527788..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/145d00f59802048185303f15937ea65c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:160ae6b6f76259d1bed275e1f52af64b647ce874bcf9d9e21668c175bc276e1f -size 23039 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/149826281804ec51b5cca5603c88b23b_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/149826281804ec51b5cca5603c88b23b_img.jpg deleted file mode 100644 index bda2d29635af58d31891cfc09817786123dab009..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/149826281804ec51b5cca5603c88b23b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7b6fac05430e70e367d9ada9da76cd2c5e5b9ca8e7947f4bce3a9607a88f76b2 -size 21624 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/156f69727798ad3823fa3a908c455101_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/156f69727798ad3823fa3a908c455101_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/156f69727798ad3823fa3a908c455101_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/15c0b877fdb0463e9fb589120e6064f5_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/15c0b877fdb0463e9fb589120e6064f5_img.jpg deleted file mode 100644 index 5e7947994cd13e250d9c0d52ef65603522742aeb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/15c0b877fdb0463e9fb589120e6064f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106e9e22973ca4ce0c1f258162dc414bc5bb34b1da32f3c4eabcbfc9045381bf -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/15faea1eb0f5fbd0d54291a786091afc_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/15faea1eb0f5fbd0d54291a786091afc_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/15faea1eb0f5fbd0d54291a786091afc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1684f5f8c34bd0ef6e933664d88b9d86_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1684f5f8c34bd0ef6e933664d88b9d86_img.jpg deleted file mode 100644 index 3676df38be78cc18501a13ba41283f81844bba07..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1684f5f8c34bd0ef6e933664d88b9d86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e1f4812157204b04b8452daf20074dd8e93a5a6a2a00197a5479e083cd8db919 -size 134854 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1739b693044814154f0f1c13d2237707_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1739b693044814154f0f1c13d2237707_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1739b693044814154f0f1c13d2237707_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/179dc105497e7283da7b3a6fda92b400_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/179dc105497e7283da7b3a6fda92b400_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/179dc105497e7283da7b3a6fda92b400_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/17e0c0ae0c4cb562e192cbde7642a209_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/17e0c0ae0c4cb562e192cbde7642a209_img.jpg deleted file mode 100644 index cf6f768a14ed53714f90d57a264e99e2e763216c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/17e0c0ae0c4cb562e192cbde7642a209_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f761699bae57660069cca2a51c20a909528a7a952df81ec688c7b7d04bd40756 -size 73069 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/17f5dcaf382b0b243584197a6456c1f5_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/17f5dcaf382b0b243584197a6456c1f5_img.jpg deleted file mode 100644 index 5e7947994cd13e250d9c0d52ef65603522742aeb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/17f5dcaf382b0b243584197a6456c1f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106e9e22973ca4ce0c1f258162dc414bc5bb34b1da32f3c4eabcbfc9045381bf -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/18c9335d3c0ae4c2b112e37eb74d5b67_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/18c9335d3c0ae4c2b112e37eb74d5b67_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/18c9335d3c0ae4c2b112e37eb74d5b67_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/18e519d1f91133e080347562f681dfb5_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/18e519d1f91133e080347562f681dfb5_img.jpg deleted file mode 100644 index 1de66487746987194a00451c7537221dfaea4435..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/18e519d1f91133e080347562f681dfb5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:194941c67ff3e3b695b574e14152e1ba48d0cf1b9cdb7d8fc8ea45fb48f1b136 -size 14893 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/19e8a93bade890b206ffafe0de45ae73_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/19e8a93bade890b206ffafe0de45ae73_img.jpg deleted file mode 100644 index 4b41845e54bf5a8baacec6869bacd24615c2688f..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/19e8a93bade890b206ffafe0de45ae73_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e518472d66e177054a43f80041b89aa0ace1a6b4f55ff46dd21fe20242834f2b -size 39462 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg deleted file mode 100644 index c473d29e266160cbee021673a35949b192a368eb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1ab49904e6a60be337d5b75cb7cc8ab7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ec48995fe8c4ccd97d35c37b28f45825bb8a3f18981017c5e33149fbcb343d56 -size 42247 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1abc95ab6792c81f3488f3b3188127e3_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1abc95ab6792c81f3488f3b3188127e3_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1abc95ab6792c81f3488f3b3188127e3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1b068463b50162bd102d83e802c811ff_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1b068463b50162bd102d83e802c811ff_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1b068463b50162bd102d83e802c811ff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1bd6a020aa71784ed74367899560cbb9_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1bd6a020aa71784ed74367899560cbb9_img.jpg deleted file mode 100644 index 7629b1c80b13d1d681fda4e60b89b1e77b1cf4a1..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1bd6a020aa71784ed74367899560cbb9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:04358012941ee2cdb1ad0b4e2e5fcb622ce4bbca954f7929d83f239adcd9b365 -size 42710 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1edf00a8a0ad2faa21bedfd66e9323d7_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1edf00a8a0ad2faa21bedfd66e9323d7_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1edf00a8a0ad2faa21bedfd66e9323d7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1ef1e4c25366022dbdc6ae74f4c6dbfd_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1ef1e4c25366022dbdc6ae74f4c6dbfd_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1ef1e4c25366022dbdc6ae74f4c6dbfd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1fd763be1b7a05b52e554f0583617642_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1fd763be1b7a05b52e554f0583617642_img.jpg deleted file mode 100644 index 669e82b731a6079359935c1eed81b413abb7de03..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/1fd763be1b7a05b52e554f0583617642_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:af0fd662f373f9fe11fdd75a72be6ae3c7ae9d6a59582f62762db4890c6fd921 -size 81475 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/20ee25255c8ef2c61cdc2e9bba26988e_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/20ee25255c8ef2c61cdc2e9bba26988e_img.jpg deleted file mode 100644 index 5e7947994cd13e250d9c0d52ef65603522742aeb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/20ee25255c8ef2c61cdc2e9bba26988e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106e9e22973ca4ce0c1f258162dc414bc5bb34b1da32f3c4eabcbfc9045381bf -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/20f693f9ce41e8c7d48d6cbd263376a6_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/20f693f9ce41e8c7d48d6cbd263376a6_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/20f693f9ce41e8c7d48d6cbd263376a6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2150ae7f14a2e4ad1866ac0c8ec685ad_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2150ae7f14a2e4ad1866ac0c8ec685ad_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2150ae7f14a2e4ad1866ac0c8ec685ad_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2277d0ec6e1001b063d4f06dc3842e92_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2277d0ec6e1001b063d4f06dc3842e92_img.jpg deleted file mode 100644 index 7943498e3d8c271a85d4c63749d13076753f4c75..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2277d0ec6e1001b063d4f06dc3842e92_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7addadc7d0061678489715cba27d1bd102890369d52b05335d841bde0a555c6a -size 36648 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/240d66bb698171f40d1acd5b0c098e4f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/240d66bb698171f40d1acd5b0c098e4f_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/240d66bb698171f40d1acd5b0c098e4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/26e477c1000006055ae0f5cad72cb057_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/26e477c1000006055ae0f5cad72cb057_img.jpg deleted file mode 100644 index 5e7947994cd13e250d9c0d52ef65603522742aeb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/26e477c1000006055ae0f5cad72cb057_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106e9e22973ca4ce0c1f258162dc414bc5bb34b1da32f3c4eabcbfc9045381bf -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/26e59f6e6ab842a448d8270473d5c8a8_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/26e59f6e6ab842a448d8270473d5c8a8_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/26e59f6e6ab842a448d8270473d5c8a8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/27788c2a26d9641e68232a4eff1299b9_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/27788c2a26d9641e68232a4eff1299b9_img.jpg deleted file mode 100644 index bbff87056be1d626a403a3fcdf3be945eedefc08..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/27788c2a26d9641e68232a4eff1299b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9775bd9c48695e973185206d9c0b1c6c23fc1e2b9e550022551a053895f3763b -size 95961 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/27c0455a3b08749fed8057467366b0ce_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/27c0455a3b08749fed8057467366b0ce_img.jpg deleted file mode 100644 index 5ec7d893b5f144965a33a43489683477e4cbdbb6..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/27c0455a3b08749fed8057467366b0ce_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:69ab8352e10cd0697993a97e36b9b1c84c5d7670523b1ad9c0a0e8932e17587d -size 62697 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/28339846e409f75f9604bbe53984b4c7_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/28339846e409f75f9604bbe53984b4c7_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/28339846e409f75f9604bbe53984b4c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2837ffdadcdb1e5bababa56b564e56ed_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2837ffdadcdb1e5bababa56b564e56ed_img.jpg deleted file mode 100644 index ad8fc6df7c15b4263a3c388cb83bda2fd2366f21..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2837ffdadcdb1e5bababa56b564e56ed_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e29f22236381a397c9c8fc54f039eebf5231b22356ce403ced89ec1436df67f3 -size 49170 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/29100fce6dce19cea57712363976bf2c_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/29100fce6dce19cea57712363976bf2c_img.jpg deleted file mode 100644 index 0c7b392f812fd4d77ac575d2eb68a67defd07f16..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/29100fce6dce19cea57712363976bf2c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4b72a8c350df2667e15030595bde6bda75a9f6c445a38f491512aa0812f59cab -size 43299 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/29640f9496773db15b016e35bb17d5b8_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/29640f9496773db15b016e35bb17d5b8_img.jpg deleted file mode 100644 index b67a243427688eeb2790e81302057a8dad9b219b..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/29640f9496773db15b016e35bb17d5b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7e97896e916a5edd1c378dbca57797b4af74282fce614cbbb6c97213abb600d2 -size 40433 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2cdc3be3de33b97cdd52a0805b399419_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2cdc3be3de33b97cdd52a0805b399419_img.jpg deleted file mode 100644 index f1f04d739c7d95f9a99f97b5565fd9d3764dcd30..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2cdc3be3de33b97cdd52a0805b399419_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb7323bba814b365e0e066431eaafd83e44dcfd0d205ba67cc733846dcf3d4fd -size 23342 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2cf1f70c3a387c43e15192a30d212546_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2cf1f70c3a387c43e15192a30d212546_img.jpg deleted file mode 100644 index 2965e750f178db6b23f2d07659c724ae092cf09a..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2cf1f70c3a387c43e15192a30d212546_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d4ff31fdeba16c67ebcf961fd21cc709d41edc0a9486afd23c73a604a2fb220e -size 50611 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2d22d155e3f98dbb44dabef33853c268_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2d22d155e3f98dbb44dabef33853c268_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2d22d155e3f98dbb44dabef33853c268_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2d3cbcc7e78c2e571a58628a299e97c3_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2d3cbcc7e78c2e571a58628a299e97c3_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2d3cbcc7e78c2e571a58628a299e97c3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2d548db0b26b7bf33244320322d5ee2c_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2d548db0b26b7bf33244320322d5ee2c_img.jpg deleted file mode 100644 index 6ec2b19ce3bdd9762e4e5508aed72e3cb4442061..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2d548db0b26b7bf33244320322d5ee2c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:582ee06a2a7eecca916076eeb8662b9f3dc67750d5e996ce0ceb6b5cb28a8c3f -size 89141 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg deleted file mode 100644 index 0af7a513c0afe826d224487ea3aa45b61655c292..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:58cb7cdd206713f27f841181d727271dda061c03546e7499ee57f8dbd71767ce -size 4649 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2e5f9e03131e55d2383bdfa422419916_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2e5f9e03131e55d2383bdfa422419916_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2e5f9e03131e55d2383bdfa422419916_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2eb6e06f673af3339af5a7f0f89543ea_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2eb6e06f673af3339af5a7f0f89543ea_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2eb6e06f673af3339af5a7f0f89543ea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2ee5c15604dce579e4f931d4566ce708_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2ee5c15604dce579e4f931d4566ce708_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2ee5c15604dce579e4f931d4566ce708_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2fc0e242cbd93c41bb82f48339de7ac1_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2fc0e242cbd93c41bb82f48339de7ac1_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/2fc0e242cbd93c41bb82f48339de7ac1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/307998a4f76d5fa18ce3713f51d0692f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/307998a4f76d5fa18ce3713f51d0692f_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/307998a4f76d5fa18ce3713f51d0692f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/31d640309e19a64318c874023ba0aadd_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/31d640309e19a64318c874023ba0aadd_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/31d640309e19a64318c874023ba0aadd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/31e08f7f7a48f3a4151828725b583a9b_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/31e08f7f7a48f3a4151828725b583a9b_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/31e08f7f7a48f3a4151828725b583a9b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3235c55432c173cdec0eaea69e1fa7cb_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3235c55432c173cdec0eaea69e1fa7cb_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3235c55432c173cdec0eaea69e1fa7cb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/32f2554a03fff77b461bd9f3704a91a3_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/32f2554a03fff77b461bd9f3704a91a3_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/32f2554a03fff77b461bd9f3704a91a3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3376f33dd811eb3e39ff47117c958ed9_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3376f33dd811eb3e39ff47117c958ed9_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3376f33dd811eb3e39ff47117c958ed9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/33e70787e71eebc7a200bc7fe352dadc_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/33e70787e71eebc7a200bc7fe352dadc_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/33e70787e71eebc7a200bc7fe352dadc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg deleted file mode 100644 index 796db58a8efa1d7019851263ea601911c0d7f0c2..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3442f31a562d1ef45bfa18b18a6a1ddc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:18a9f0d1c82a4ac4e277e977140cb1f2370b4fd4850b6e3d175eb0db9388a242 -size 33831 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/34b047489058d6400b412cd0ae2334ba_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/34b047489058d6400b412cd0ae2334ba_img.jpg deleted file mode 100644 index d0860a5cb0e9a24eeaf0a9bafe1262e26b167a1f..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/34b047489058d6400b412cd0ae2334ba_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:364b6388346e16a24693fa846acbfe15f0052c751b53eb09e489653ab8b49a6d -size 32478 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3570a9a55007ad14ede6c8fd6c40e5fa_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3570a9a55007ad14ede6c8fd6c40e5fa_img.jpg deleted file mode 100644 index 5e7947994cd13e250d9c0d52ef65603522742aeb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3570a9a55007ad14ede6c8fd6c40e5fa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106e9e22973ca4ce0c1f258162dc414bc5bb34b1da32f3c4eabcbfc9045381bf -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/35bdae77185f296854f8406f6a3f7439_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/35bdae77185f296854f8406f6a3f7439_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/35bdae77185f296854f8406f6a3f7439_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/369bdbec639c7a654c81db156d41596a_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/369bdbec639c7a654c81db156d41596a_img.jpg deleted file mode 100644 index 5e7947994cd13e250d9c0d52ef65603522742aeb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/369bdbec639c7a654c81db156d41596a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106e9e22973ca4ce0c1f258162dc414bc5bb34b1da32f3c4eabcbfc9045381bf -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/38e2f36189a1eef7ecbdd4c44bdeea2e_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/38e2f36189a1eef7ecbdd4c44bdeea2e_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/38e2f36189a1eef7ecbdd4c44bdeea2e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3a6347f9ba293dba971fe22b739bdeef_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3a6347f9ba293dba971fe22b739bdeef_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3a6347f9ba293dba971fe22b739bdeef_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3b20eb477ef174b7adaad37703f5d611_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3b20eb477ef174b7adaad37703f5d611_img.jpg deleted file mode 100644 index a316d81628dd16b11a5a29ef5b7c0129dd7b1433..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3b20eb477ef174b7adaad37703f5d611_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3b5ab6d9c832b9f1966cf96b66ebf52eaaa2c91a9ed71ec14de69eb1d3c69ef8 -size 133693 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3c6e58a263aca26400c2f3a883bffbe2_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3c6e58a263aca26400c2f3a883bffbe2_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3c6e58a263aca26400c2f3a883bffbe2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3cf228b7923919ad784bef3eeb0aebce_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3cf228b7923919ad784bef3eeb0aebce_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3cf228b7923919ad784bef3eeb0aebce_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3cf9c03399ad83db016e51124c54e855_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3cf9c03399ad83db016e51124c54e855_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3cf9c03399ad83db016e51124c54e855_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3d03999e085fe4b9fdcb93dfbcb55218_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3d03999e085fe4b9fdcb93dfbcb55218_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3d03999e085fe4b9fdcb93dfbcb55218_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3e785accf62f005fb821a0eeb2796bcb_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3e785accf62f005fb821a0eeb2796bcb_img.jpg deleted file mode 100644 index ddf709cf2f03795b5ae5b7ef6c26383609cfd4e4..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3e785accf62f005fb821a0eeb2796bcb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9a6989f8549e0b85a11436724b71e33f064a5dc1dd1e93d10787cbb5c60d5330 -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg deleted file mode 100644 index c4d4c4b9f0dc983090efcb416f0903a64c83ef1f..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3e8e3bdb3d90f0856266d4eaf36abba1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1afa24304bcab354db189f262ed910e8cf6f50f5d337017f137701d943c80f36 -size 19184 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3eb092cb663bfa38f2ed2ea2548460ed_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3eb092cb663bfa38f2ed2ea2548460ed_img.jpg deleted file mode 100644 index 5a08a47e85901337ac3049e191a0db3b600c61a2..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3eb092cb663bfa38f2ed2ea2548460ed_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:507c3c662b2a856faeaf5d30bc426b8401ab72b28f0fe67eb0136c55dae9c909 -size 76896 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3eddc247052fc64b4d863672db9fa2b0_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3eddc247052fc64b4d863672db9fa2b0_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3eddc247052fc64b4d863672db9fa2b0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3eeec80822340aa7c74d7dc2f215bfc5_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3eeec80822340aa7c74d7dc2f215bfc5_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3eeec80822340aa7c74d7dc2f215bfc5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3f47bcff76a8105d2539569fc8909db7_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3f47bcff76a8105d2539569fc8909db7_img.jpg deleted file mode 100644 index 59d01e0af7c4bb3ab635752dca4223b0d95de06e..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/3f47bcff76a8105d2539569fc8909db7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4607ca1a506bf50e56cc00e7bdd4e05cc6cdd0205a84a8b54b62f3522bae9021 -size 62250 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/40135f3a8f5a6789225806e70870256d_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/40135f3a8f5a6789225806e70870256d_img.jpg deleted file mode 100644 index 3e7c2f6cf54bf407274dc3223fa3c4a20dbc9241..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/40135f3a8f5a6789225806e70870256d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d39b47a9354489fe0389f24020696a7e53f8a103393a7e94d83f6ef545843a21 -size 150152 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/40647355b8fe9eeaadd5a58444dfe51d_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/40647355b8fe9eeaadd5a58444dfe51d_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/40647355b8fe9eeaadd5a58444dfe51d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4260aa4a7ece77c411597094c9d197bd_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4260aa4a7ece77c411597094c9d197bd_img.jpg deleted file mode 100644 index 0cd96a58b74260ad4603e8c08d29466ff235696f..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4260aa4a7ece77c411597094c9d197bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:98e86266c0ad4a3b8cf985b3a7d054e432935ac5a6ed3e0444318b07ec4798f2 -size 89669 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/42b224bb9b5fce80421c05b7f630c048_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/42b224bb9b5fce80421c05b7f630c048_img.jpg deleted file mode 100644 index 1db275da2255e377dd9db857bd42553a42ab5468..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/42b224bb9b5fce80421c05b7f630c048_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e530004da178f0b676e131e0d5d7c688d54a0dc9ab7f0b91ff2fffba1b1d8cd5 -size 47165 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/437517111168a2b766400478395eff60_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/437517111168a2b766400478395eff60_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/437517111168a2b766400478395eff60_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4540c7355b250cb891be0b54b0ba25c7_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4540c7355b250cb891be0b54b0ba25c7_img.jpg deleted file mode 100644 index ed420ca7a63ed17ec747e49600c144c6330d7229..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4540c7355b250cb891be0b54b0ba25c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a20790351e28902609a914ed9c81dd30dc22413aed5e84f5ed31a02bbc87ce72 -size 63342 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/458010a93dad72d629626466df35b3d4_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/458010a93dad72d629626466df35b3d4_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/458010a93dad72d629626466df35b3d4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/45e43022bd578b9de22acadf38122da9_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/45e43022bd578b9de22acadf38122da9_img.jpg deleted file mode 100644 index 740df322300fba3ced3659a282022410f49112d7..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/45e43022bd578b9de22acadf38122da9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:269f6fa2cf875df353cab9aa9f6a88281640dd26969d755d9d93e87fa5d745a6 -size 48127 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/46269d85941a43cd25f9acba1b9c666e_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/46269d85941a43cd25f9acba1b9c666e_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/46269d85941a43cd25f9acba1b9c666e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/476bd53e2f910ac6842bec8208d70de5_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/476bd53e2f910ac6842bec8208d70de5_img.jpg deleted file mode 100644 index 81422a7d149420b26055351de560758587a98639..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/476bd53e2f910ac6842bec8208d70de5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:132e5a90f49ed3b526743527fe3129508efc1e389be887f09189b7d6b0118cc8 -size 45496 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/48b8c4214eaf2c253f097bf484c605f6_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/48b8c4214eaf2c253f097bf484c605f6_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/48b8c4214eaf2c253f097bf484c605f6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/48bd33b4281a86fca8d1147e46a766e6_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/48bd33b4281a86fca8d1147e46a766e6_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/48bd33b4281a86fca8d1147e46a766e6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/48fecf94dd9fb955caddbf2fb01b7b9b_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/48fecf94dd9fb955caddbf2fb01b7b9b_img.jpg deleted file mode 100644 index e95949f37db35457090f153948d282d3ab99d4e2..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/48fecf94dd9fb955caddbf2fb01b7b9b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bc0a42d575ab137d026d616b7911ecda873ae7ffb90225611f920f6a468e8ae4 -size 50210 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/491facfcef71bd091768b201bb2c0064_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/491facfcef71bd091768b201bb2c0064_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/491facfcef71bd091768b201bb2c0064_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/49520c9e7f737cb730421eaec2c71ab0_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/49520c9e7f737cb730421eaec2c71ab0_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/49520c9e7f737cb730421eaec2c71ab0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4ab9a7f0e4a9cd029ae0c1326f9a2323_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4ab9a7f0e4a9cd029ae0c1326f9a2323_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4ab9a7f0e4a9cd029ae0c1326f9a2323_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4ad71ddb7c8022a7007934b745b36a96_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4ad71ddb7c8022a7007934b745b36a96_img.jpg deleted file mode 100644 index 2040b1cf484bdb34516956a0f8a5842d1c75689c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4ad71ddb7c8022a7007934b745b36a96_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:955a39d25d837554e07ad09d5e87f552836f4dcd80c9307e4a6eea53a2b04f11 -size 4736 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4bd793f76f6a26ed6c66127dbbef21f8_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4bd793f76f6a26ed6c66127dbbef21f8_img.jpg deleted file mode 100644 index a5767f4f7016e68bf2a49ce746140da1307a8c9a..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4bd793f76f6a26ed6c66127dbbef21f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f4be2b59f0414b88e68f0588559a03d0bb40fcf5cb98356feb338134a779f260 -size 55550 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg deleted file mode 100644 index a001fcb6641256abd711cf02312026ad3cf20849..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4c1ea859b93043f2fa17a8fe72fb6176_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:dfc724eea221bb46eda64ac2a0f6fdbde031049d55980870e438f5e5b260b7de -size 36232 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4cc429e64fa659ccd92b98e5cbe8322f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4cc429e64fa659ccd92b98e5cbe8322f_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4cc429e64fa659ccd92b98e5cbe8322f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4d2d8d3bf9f7cdd835ab71fc6126cd95_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4d2d8d3bf9f7cdd835ab71fc6126cd95_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4d2d8d3bf9f7cdd835ab71fc6126cd95_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4ecb55f0a56c2f3deb9eeddfde39d501_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4ecb55f0a56c2f3deb9eeddfde39d501_img.jpg deleted file mode 100644 index fa9478f5c1e33839885bb40fb63d840a4ce5ff24..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4ecb55f0a56c2f3deb9eeddfde39d501_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:583d33fdb574d18b072f84451caf4597ec1fc056833dc71890a6841c511a2cdc -size 37096 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4ef0df6c8f181ac6d20e02204294d8e3_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4ef0df6c8f181ac6d20e02204294d8e3_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/4ef0df6c8f181ac6d20e02204294d8e3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/507d351592c54dbf0e18cfba95528f92_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/507d351592c54dbf0e18cfba95528f92_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/507d351592c54dbf0e18cfba95528f92_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5099b826c109bf4df1229d96520da57f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5099b826c109bf4df1229d96520da57f_img.jpg deleted file mode 100644 index 103f6908abcd3ee4201d8345aa95e7af9a898abc..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5099b826c109bf4df1229d96520da57f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b72f5e8cc4170bcdacff7d1e1a4155a1a7bdd9ee0844303a0ec7b9a34f08bf11 -size 81043 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/50d4c3d6ba07f2fb58d34c227f1b312b_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/50d4c3d6ba07f2fb58d34c227f1b312b_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/50d4c3d6ba07f2fb58d34c227f1b312b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/511f9b05a4c458937dd12c30936fd7d6_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/511f9b05a4c458937dd12c30936fd7d6_img.jpg deleted file mode 100644 index 7638fc1f4518495cc365c12009e7f4b743dbfb25..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/511f9b05a4c458937dd12c30936fd7d6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:35adda9259841c0a6b46a8d0fadf6af89ca3b5c1adeaa54acb613f0370f692ab -size 66143 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/51501a01b2c29ac95e126882508f8831_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/51501a01b2c29ac95e126882508f8831_img.jpg deleted file mode 100644 index 112ba67053231eeb9f287c0457c301b4b137870d..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/51501a01b2c29ac95e126882508f8831_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a4a1fb06cd13d213caa02e55ff4386c1458666e6842943244f4a5931b2198980 -size 113375 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/51b44891ed19b748b56f3f543816631d_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/51b44891ed19b748b56f3f543816631d_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/51b44891ed19b748b56f3f543816631d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/537db0b682e0f2e10942490eb3300ca6_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/537db0b682e0f2e10942490eb3300ca6_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/537db0b682e0f2e10942490eb3300ca6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/55448600b72a05f749215a83f8d2aef7_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/55448600b72a05f749215a83f8d2aef7_img.jpg deleted file mode 100644 index 8e8b3a775096d0d8ba7d68d4e7c3e2511e673860..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/55448600b72a05f749215a83f8d2aef7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9099f5d101778fcdd6132c3350196750b4182d879cb35d95220e7e5991371da1 -size 49106 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/55d74563d1b88865295879cdaffce3ff_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/55d74563d1b88865295879cdaffce3ff_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/55d74563d1b88865295879cdaffce3ff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/589af9a5d6f5bbbdc8f482e364688676_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/589af9a5d6f5bbbdc8f482e364688676_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/589af9a5d6f5bbbdc8f482e364688676_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/592f13acca3e6d5152dd4489f030d004_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/592f13acca3e6d5152dd4489f030d004_img.jpg deleted file mode 100644 index fe7b5a559589feeab66750ee82a823c50bae3a41..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/592f13acca3e6d5152dd4489f030d004_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3459e1ef151f93bbd2f8f31f8ef9b37183882c4faf74eb79240554e02a91344e -size 37198 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/59e29b37c5e332b0be088cde8c4d217e_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/59e29b37c5e332b0be088cde8c4d217e_img.jpg deleted file mode 100644 index 616f0a3622edf350a7e3479a63826d6dcb07a3de..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/59e29b37c5e332b0be088cde8c4d217e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:70d7f95f91d39ab4e512cb36ee310722f2a0872866cb33d38f75d713beb51e25 -size 37873 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/59f59a425aab673dd9a76474db66a3c4_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/59f59a425aab673dd9a76474db66a3c4_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/59f59a425aab673dd9a76474db66a3c4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5a01395925fc88802da68fb5ac0f31ff_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5a01395925fc88802da68fb5ac0f31ff_img.jpg deleted file mode 100644 index be4ba0ffda403fe31f69d2f63890a7d5889fb71a..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5a01395925fc88802da68fb5ac0f31ff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f555fdbd352e421eec2dc945c4a213f9fd00e73f4431917cd6923331a91e2e77 -size 57712 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5ba4353c6c79c5cc8f47b2f425afd0cc_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5ba4353c6c79c5cc8f47b2f425afd0cc_img.jpg deleted file mode 100644 index 5e7947994cd13e250d9c0d52ef65603522742aeb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5ba4353c6c79c5cc8f47b2f425afd0cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106e9e22973ca4ce0c1f258162dc414bc5bb34b1da32f3c4eabcbfc9045381bf -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5c0c0ffe0aa2bcd2d7f0a436f3c4674e_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5c0c0ffe0aa2bcd2d7f0a436f3c4674e_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5c0c0ffe0aa2bcd2d7f0a436f3c4674e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5c3dd31372f59e15250f0ab1613ca485_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5c3dd31372f59e15250f0ab1613ca485_img.jpg deleted file mode 100644 index af6cc1e23967d9f0b42adc6b795554285af0a5ec..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5c3dd31372f59e15250f0ab1613ca485_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8bd95cfe882a5f7a81f1ad542e17e3bd6fa7e6f018dcf2d3ecfd63499395e38b -size 60671 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5e9af8986a5845504f251d3079da8078_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5e9af8986a5845504f251d3079da8078_img.jpg deleted file mode 100644 index db3fdeaa8ebc90f54047fe998938559a3b48d99d..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5e9af8986a5845504f251d3079da8078_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b75670a1a6620e146d3c61d2586aa8ed9a2a6c14761ccac0d922325a379a6f68 -size 24014 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5f0b57710a125afec285a2c3c9d2e0b1_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5f0b57710a125afec285a2c3c9d2e0b1_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5f0b57710a125afec285a2c3c9d2e0b1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5f3f302d1ab63beb8898d1ecfb7b63fe_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5f3f302d1ab63beb8898d1ecfb7b63fe_img.jpg deleted file mode 100644 index 677ad6daa9956f267a3c121e8f5d2ac4531d0abc..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5f3f302d1ab63beb8898d1ecfb7b63fe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:edf723280a7b3f82158dd2171f89366b309460a52839e4184691b2cc43011ebe -size 79578 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5f8af0cfcf796986f40e70571bb950f5_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5f8af0cfcf796986f40e70571bb950f5_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/5f8af0cfcf796986f40e70571bb950f5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6049efb1d32fc2106d9f8adc27141614_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6049efb1d32fc2106d9f8adc27141614_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6049efb1d32fc2106d9f8adc27141614_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6080df47bc782c101b2abbb9803962f2_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6080df47bc782c101b2abbb9803962f2_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6080df47bc782c101b2abbb9803962f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/609f0ddefa429554dbb012baf5f52880_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/609f0ddefa429554dbb012baf5f52880_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/609f0ddefa429554dbb012baf5f52880_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/60ce0fc249173a32463028d12805feca_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/60ce0fc249173a32463028d12805feca_img.jpg deleted file mode 100644 index 569d0de2ffb2096401fa1f71fc340ea83d080465..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/60ce0fc249173a32463028d12805feca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a6805670b0ba0ab51dfff949298d707b7af5ddf1c081a16abb7ce7df4afa1074 -size 64732 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/60f844d947ea0bccdd9f64d81d5f8d26_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/60f844d947ea0bccdd9f64d81d5f8d26_img.jpg deleted file mode 100644 index 7c919e13d5f6412ecbc9b8a158ea41ec036c6447..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/60f844d947ea0bccdd9f64d81d5f8d26_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4fe1b8a316f9bfc7015678b8f22529a81c44f4c251e20703b5e8a05e39c76722 -size 68575 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6240cc0a7da4e8cbe8f5f9541de3d4fe_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6240cc0a7da4e8cbe8f5f9541de3d4fe_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6240cc0a7da4e8cbe8f5f9541de3d4fe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/625e10f48104ba2b06b2220a9b224712_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/625e10f48104ba2b06b2220a9b224712_img.jpg deleted file mode 100644 index 36ef3d74a3d5e4efe9fec01045563095b19fd7d1..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/625e10f48104ba2b06b2220a9b224712_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b1a6852cd7287d6175343848889237b93d25d25bfb27faa3838c8f239aa96286 -size 4546 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6322885569221ec51d70560d7dba1339_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6322885569221ec51d70560d7dba1339_img.jpg deleted file mode 100644 index acef26db1c670c3f89d0a0d478b40961ed338c2d..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6322885569221ec51d70560d7dba1339_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:180e121772daa2d416fc0469c902b948230f8af24afb470cb4f1bb2b282c534b -size 38102 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/638a308af25f1f56b4456a1fc503f161_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/638a308af25f1f56b4456a1fc503f161_img.jpg deleted file mode 100644 index fd7ff6c499cd0c36c0aac2d92c7d454acd31ec25..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/638a308af25f1f56b4456a1fc503f161_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c4903b72283a942f53c87028c1a42ec76b3863987df7116c12c27dc6a2df86bc -size 48977 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/64323b705244afc70bf77babdacb6ce5_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/64323b705244afc70bf77babdacb6ce5_img.jpg deleted file mode 100644 index f4bba2390d4a7706877ba7fc171acc8c4011f23d..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/64323b705244afc70bf77babdacb6ce5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:857a42178b8ffcdd660e3460ae90a66cfc9828e6ea9cd00f6acb260306ede7bd -size 117175 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6450d1043578af5919949d716e3349b1_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6450d1043578af5919949d716e3349b1_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6450d1043578af5919949d716e3349b1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6470d350326789d5306eabcb76533951_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6470d350326789d5306eabcb76533951_img.jpg deleted file mode 100644 index 8c6f28e50890dadf44d0d17a2ba187644ff53692..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6470d350326789d5306eabcb76533951_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0455a8c641f54f8b197c388ae12d4d7d89a89121ae4cbdad206d2e133b4e1c4b -size 40536 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/64bc20572e786c96baee9996e0c52ab2_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/64bc20572e786c96baee9996e0c52ab2_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/64bc20572e786c96baee9996e0c52ab2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/64ca20a7357e612f7c65bbe816032c8a_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/64ca20a7357e612f7c65bbe816032c8a_img.jpg deleted file mode 100644 index 99442023033956f2e32c60820a0af09f24a532fd..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/64ca20a7357e612f7c65bbe816032c8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f816a31c1fc00143420fe6aa51fae87dbaece0c37212f9afa2555928f711f8f0 -size 60148 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6541fef32fd472072600f905d8b11009_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6541fef32fd472072600f905d8b11009_img.jpg deleted file mode 100644 index dc8a0b880e3c73eaf593ce08b16af36c30b0fd5d..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6541fef32fd472072600f905d8b11009_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bef7ed03597255c53d791e677dcf232d1d016e780f40c63c155a5918fb3bdd38 -size 86972 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/662933fe00899933b36b5a214ac6095c_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/662933fe00899933b36b5a214ac6095c_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/662933fe00899933b36b5a214ac6095c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/662c84f65e27aff9b64ec351f9d8cca8_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/662c84f65e27aff9b64ec351f9d8cca8_img.jpg deleted file mode 100644 index fc86be9d07057fcd924ca5d76401ebcb77d644f1..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/662c84f65e27aff9b64ec351f9d8cca8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:346df90cd5decebf0a2da2ed8a28a928c9618a98a2324f1af15ff9abfaca8863 -size 67866 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6702cc564c13eb629b0b196798dc054f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6702cc564c13eb629b0b196798dc054f_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6702cc564c13eb629b0b196798dc054f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6719a115173a966954d1bc7d03d7c80c_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6719a115173a966954d1bc7d03d7c80c_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6719a115173a966954d1bc7d03d7c80c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/683260ef6ff6db4c965953b66974c872_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/683260ef6ff6db4c965953b66974c872_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/683260ef6ff6db4c965953b66974c872_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/693fba7468e5c1f5d0ce13e44e3910fe_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/693fba7468e5c1f5d0ce13e44e3910fe_img.jpg deleted file mode 100644 index 5e7947994cd13e250d9c0d52ef65603522742aeb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/693fba7468e5c1f5d0ce13e44e3910fe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106e9e22973ca4ce0c1f258162dc414bc5bb34b1da32f3c4eabcbfc9045381bf -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/69af3542f800e9f0a3ea1d9bfbd07acb_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/69af3542f800e9f0a3ea1d9bfbd07acb_img.jpg deleted file mode 100644 index 3529407c9f0cacdf6d5c4cdb3637ae19b1ca69dc..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/69af3542f800e9f0a3ea1d9bfbd07acb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:df2cbea7dd355d717da2c16f8906621da06ec27c5eb96c14acea5f8ff607df59 -size 53955 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/69e5f1993021af230d08c08aac97d9df_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/69e5f1993021af230d08c08aac97d9df_img.jpg deleted file mode 100644 index 49bbcf785ef16ac99c232976dbee622d4a740e59..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/69e5f1993021af230d08c08aac97d9df_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:00c08a8a57aaac465da92c4bec7c6be023df179491104833c244158f16cf2c33 -size 38782 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6a791970c2c6af10a647cff11d071fc9_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6a791970c2c6af10a647cff11d071fc9_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6a791970c2c6af10a647cff11d071fc9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6b6d27ae1c0c8c9bebfdc07af29d3d1e_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6b6d27ae1c0c8c9bebfdc07af29d3d1e_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6b6d27ae1c0c8c9bebfdc07af29d3d1e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6caa056e54d81c8403fe884e3c29fa66_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6caa056e54d81c8403fe884e3c29fa66_img.jpg deleted file mode 100644 index bf2386033969666eaf7d25378916d63977603352..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6caa056e54d81c8403fe884e3c29fa66_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d1038e5c25de7c2c7c43ef9caa49e320dddc2486e66af2e4ca8520bdc898f6a1 -size 95939 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6e50e3275fbdccd63dc258477b94bef6_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6e50e3275fbdccd63dc258477b94bef6_img.jpg deleted file mode 100644 index 19a3bd6d0a50d82f2b55843c0f8b657c553d6104..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6e50e3275fbdccd63dc258477b94bef6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7fa78d87258a6daf7db8833801207cca3b70582eece414e645cc12b6e21ff0d4 -size 80033 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6efd71634730bb1daff9fcfcba9591eb_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6efd71634730bb1daff9fcfcba9591eb_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/6efd71634730bb1daff9fcfcba9591eb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg deleted file mode 100644 index 7a77a97355c42ac8760331e6fdd1b785a4c890c4..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fc8e77a4b7929816bbb8a5d645367a78eb843bf30a213a03edcd2700bed2d444 -size 49645 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/708e4c9a044ef61f586126676eb2eeb8_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/708e4c9a044ef61f586126676eb2eeb8_img.jpg deleted file mode 100644 index d3cad8546e02baf82d6ca7ee0e00b8bad73f13b2..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/708e4c9a044ef61f586126676eb2eeb8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4e2802464cb7dde280c5d3ae3a58e8503d82f547fa27163a37ef4c7013584c84 -size 72753 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/710b805054943193bd9fd7674b0759f6_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/710b805054943193bd9fd7674b0759f6_img.jpg deleted file mode 100644 index 892ff0739244a2c895b50fffa0ab9b7245ea669a..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/710b805054943193bd9fd7674b0759f6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:10b782a808180dadf8e25937392e06a036fa4b103e719d04c166cfed881d4ba4 -size 116069 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/71b0a68b4dd64961465d2b0e790538de_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/71b0a68b4dd64961465d2b0e790538de_img.jpg deleted file mode 100644 index d4005d75167936cb1fbed8c8d88daf0076437df2..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/71b0a68b4dd64961465d2b0e790538de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ed89b8dcfd399b809ff0f5e553d9f8aab9a2184bcbb6b4ed72ac7a4e60600e94 -size 19005 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/71dea59c7a8cc6669fcce714dca70021_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/71dea59c7a8cc6669fcce714dca70021_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/71dea59c7a8cc6669fcce714dca70021_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/741314499ddea041e960910b0a7f5c0f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/741314499ddea041e960910b0a7f5c0f_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/741314499ddea041e960910b0a7f5c0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7480889e4ab8f0e8524ef7ad3e9b2536_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7480889e4ab8f0e8524ef7ad3e9b2536_img.jpg deleted file mode 100644 index bc61ad8b0c4e97ac2e0f7e14d4deab436195f2f5..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7480889e4ab8f0e8524ef7ad3e9b2536_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:38ecd69c20d51f029af8c8cb8bc60ea5ad250700df296e377de10281e773cd50 -size 26354 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/75b916cf99a8170ef33ffc901cb9d197_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/75b916cf99a8170ef33ffc901cb9d197_img.jpg deleted file mode 100644 index 2040b1cf484bdb34516956a0f8a5842d1c75689c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/75b916cf99a8170ef33ffc901cb9d197_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:955a39d25d837554e07ad09d5e87f552836f4dcd80c9307e4a6eea53a2b04f11 -size 4736 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/75d6e15345b73203451a499ee83ace47_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/75d6e15345b73203451a499ee83ace47_img.jpg deleted file mode 100644 index 1b7fe49c6cd1cc3259628dbe559fe513157ba393..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/75d6e15345b73203451a499ee83ace47_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:60616afebf55d4a23a9623fdf7faf3485472355e35ed4242e9eda055e906ccfb -size 63265 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/76177f18271e87e53ac3c915c7bfc63d_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/76177f18271e87e53ac3c915c7bfc63d_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/76177f18271e87e53ac3c915c7bfc63d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/76cef7549f47c105c5b01ab9b5957de8_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/76cef7549f47c105c5b01ab9b5957de8_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/76cef7549f47c105c5b01ab9b5957de8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg deleted file mode 100644 index 7e40b11e5e907c93042634eb1ae4830a4708064e..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/778a90bfa183fbf83bfe2bf1ed8fa827_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4a552736df0481a253c96a8794aa54db6464bc17a620d311c7b5a4f761f2df25 -size 68543 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/78c6bfdfef4d292384fc7667315392ab_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/78c6bfdfef4d292384fc7667315392ab_img.jpg deleted file mode 100644 index 51eef4b4b779e7c4cbb6da701b36c96ef8f1def5..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/78c6bfdfef4d292384fc7667315392ab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f6ada74de22729368d6c41327fcb632ea6b330d2d7182733f4e28b8c2e5c398a -size 48881 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/78f163db583eb0c6d013e6f8ffe6d7d8_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/78f163db583eb0c6d013e6f8ffe6d7d8_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/78f163db583eb0c6d013e6f8ffe6d7d8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/79a54c80d4260cde1d39f45d43e142f2_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/79a54c80d4260cde1d39f45d43e142f2_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/79a54c80d4260cde1d39f45d43e142f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7b1cea8c45c49887a750926f2135fa84_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7b1cea8c45c49887a750926f2135fa84_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7b1cea8c45c49887a750926f2135fa84_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7c944c119a9d45d12741620a742a3ab1_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7c944c119a9d45d12741620a742a3ab1_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7c944c119a9d45d12741620a742a3ab1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7cdd3a0b8107619a3a05ea9ed16eff02_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7cdd3a0b8107619a3a05ea9ed16eff02_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7cdd3a0b8107619a3a05ea9ed16eff02_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7d2c50f88ff6fac5f6d6af3dd39e1074_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7d2c50f88ff6fac5f6d6af3dd39e1074_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7d2c50f88ff6fac5f6d6af3dd39e1074_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7d675e1c380dccba3f69e2de4e72562c_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7d675e1c380dccba3f69e2de4e72562c_img.jpg deleted file mode 100644 index a67a56c4d2c88ea1bb3815a94b112c3c20a9e75a..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7d675e1c380dccba3f69e2de4e72562c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eac60d295a0f7ed413e87dfc442af0ac5a1eb0049a6afcc335a593ebaaa46fd1 -size 163497 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7e12e1e0d03a03790d2e9d74c3454bff_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7e12e1e0d03a03790d2e9d74c3454bff_img.jpg deleted file mode 100644 index 770aeb29c61346f7328272e382bfb9907eee61aa..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7e12e1e0d03a03790d2e9d74c3454bff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0d980b8c85e216cb7caab06425bfd544f4c3ae943c9e95fa9518ea3d00ca1bb0 -size 56313 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7ee2d12e8cbaacaf65b0c332d1c76daf_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7ee2d12e8cbaacaf65b0c332d1c76daf_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7ee2d12e8cbaacaf65b0c332d1c76daf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7ef22670a44997c5e7b3ee16235f2a10_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7ef22670a44997c5e7b3ee16235f2a10_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7ef22670a44997c5e7b3ee16235f2a10_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7ef82ab74729923b27507495301d73a6_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7ef82ab74729923b27507495301d73a6_img.jpg deleted file mode 100644 index 1bf8fb2b1d0a4f395cec03a270ca5b9c7cb5f6a4..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7ef82ab74729923b27507495301d73a6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9f9ae6527d9308f18a018e3b3bc04adeca4504d2f44ebc25b6fdcb73f7f574b6 -size 30854 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7f46e92a1d022a1c67559541c7cb1596_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7f46e92a1d022a1c67559541c7cb1596_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7f46e92a1d022a1c67559541c7cb1596_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7f7211748473542096717109ebe5a9d6_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7f7211748473542096717109ebe5a9d6_img.jpg deleted file mode 100644 index a93c8d68f63479e7abb655dcfb5145dcf1e123f7..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7f7211748473542096717109ebe5a9d6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:212d9edeb946398997ea43b220c6902176433ca533bde7a700da908abcbedeb3 -size 15013 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7f78becb007c69a3a1b4aef8edc0e328_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7f78becb007c69a3a1b4aef8edc0e328_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7f78becb007c69a3a1b4aef8edc0e328_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7f9a7d3e2d9215f8ee2f56fec9c3d9e4_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7f9a7d3e2d9215f8ee2f56fec9c3d9e4_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7f9a7d3e2d9215f8ee2f56fec9c3d9e4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg deleted file mode 100644 index 1b5920e3161c884035454942574de18dcf850838..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/7fe5741e83bc9702d1b1d7585ddf66bd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ad182347dbdc0efca61104c9a13269dabc04cd771cf459e480532d803484b45d -size 32416 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/805f16ab0445ab8949eaca614d4a06d6_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/805f16ab0445ab8949eaca614d4a06d6_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/805f16ab0445ab8949eaca614d4a06d6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/805f30f65cc9617bd3137c6e0b735595_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/805f30f65cc9617bd3137c6e0b735595_img.jpg deleted file mode 100644 index af42de4cc4684bd6b50fbe5fa5841bff77649113..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/805f30f65cc9617bd3137c6e0b735595_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:1412ccc3dc6684310f6379bc8b1407902dd8b31d745597bc11e5ef5000662cca -size 85385 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/806d2632fa8b6a9bd79d816e1722de6b_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/806d2632fa8b6a9bd79d816e1722de6b_img.jpg deleted file mode 100644 index 36ef3d74a3d5e4efe9fec01045563095b19fd7d1..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/806d2632fa8b6a9bd79d816e1722de6b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b1a6852cd7287d6175343848889237b93d25d25bfb27faa3838c8f239aa96286 -size 4546 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/80ccc3e44bb7682a94bf1c000e904e61_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/80ccc3e44bb7682a94bf1c000e904e61_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/80ccc3e44bb7682a94bf1c000e904e61_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/81198a2bf24d5939ce9121693eaf7aa8_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/81198a2bf24d5939ce9121693eaf7aa8_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/81198a2bf24d5939ce9121693eaf7aa8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/81c2fa4df3adbe409a3d45790bc574cf_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/81c2fa4df3adbe409a3d45790bc574cf_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/81c2fa4df3adbe409a3d45790bc574cf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8212253dda29ea0f382e879cda1715a1_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8212253dda29ea0f382e879cda1715a1_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8212253dda29ea0f382e879cda1715a1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/823208a2fe986c0d9e269fc356b43e8c_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/823208a2fe986c0d9e269fc356b43e8c_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/823208a2fe986c0d9e269fc356b43e8c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/82bd3ecf82bd20a7d0d09bea00c879b7_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/82bd3ecf82bd20a7d0d09bea00c879b7_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/82bd3ecf82bd20a7d0d09bea00c879b7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/82dec3514a38921fd6dede9a0937d4e2_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/82dec3514a38921fd6dede9a0937d4e2_img.jpg deleted file mode 100644 index 36ef3d74a3d5e4efe9fec01045563095b19fd7d1..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/82dec3514a38921fd6dede9a0937d4e2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b1a6852cd7287d6175343848889237b93d25d25bfb27faa3838c8f239aa96286 -size 4546 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/83a718de2dd31ecd7acfb09449924e04_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/83a718de2dd31ecd7acfb09449924e04_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/83a718de2dd31ecd7acfb09449924e04_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8512afe2a50a7087c8b77a68dd354994_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8512afe2a50a7087c8b77a68dd354994_img.jpg deleted file mode 100644 index 58f619d53ae5fcb75520af5e7996c2578bcf01a9..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8512afe2a50a7087c8b77a68dd354994_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5d8b2176243d7bca0da491930605fcf53202634c47bb16b55d4ca33df5899875 -size 34015 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/85be932876bdce320688fd29341f613d_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/85be932876bdce320688fd29341f613d_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/85be932876bdce320688fd29341f613d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/85eaedd7b55b824162a79286bdf64694_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/85eaedd7b55b824162a79286bdf64694_img.jpg deleted file mode 100644 index 5e7947994cd13e250d9c0d52ef65603522742aeb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/85eaedd7b55b824162a79286bdf64694_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106e9e22973ca4ce0c1f258162dc414bc5bb34b1da32f3c4eabcbfc9045381bf -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/860f57f81cf80d82f2b90c30ae920b51_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/860f57f81cf80d82f2b90c30ae920b51_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/860f57f81cf80d82f2b90c30ae920b51_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/87538011bcfcd46e392fe6278cb18ead_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/87538011bcfcd46e392fe6278cb18ead_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/87538011bcfcd46e392fe6278cb18ead_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/878e3f080378afb04bb23d5863edc6a5_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/878e3f080378afb04bb23d5863edc6a5_img.jpg deleted file mode 100644 index 9b1418ced50d353285ed116965b66449419b95cc..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/878e3f080378afb04bb23d5863edc6a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:cc5d3901870fac26fdc268efaa5a6e873e2b632ede6f0d4a2ec08e3e8edbecb9 -size 51645 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/885eef49ebd0d6c58ca2ac79ca9f1f5e_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/885eef49ebd0d6c58ca2ac79ca9f1f5e_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/885eef49ebd0d6c58ca2ac79ca9f1f5e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/887ea91be733df298b3c9643b2fbec60_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/887ea91be733df298b3c9643b2fbec60_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/887ea91be733df298b3c9643b2fbec60_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/88842d98d695fe6a281f8af82f9ac951_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/88842d98d695fe6a281f8af82f9ac951_img.jpg deleted file mode 100644 index e86753a4a7d13f4e8c7c151bb57d1c38da5f4692..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/88842d98d695fe6a281f8af82f9ac951_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:fd89611c44d0ecc8d016407f042c3f86d1f427a2501ab2de85bd0751b777a4b1 -size 40837 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/88a422435c7d5f8cabe4609cb0fd46b3_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/88a422435c7d5f8cabe4609cb0fd46b3_img.jpg deleted file mode 100644 index 4880058ab95bfd13dd1af9d6ee526132265140b4..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/88a422435c7d5f8cabe4609cb0fd46b3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f76dccc30bd60217c4a114701f94bf7ebb3fe8cfa66a3750ef4c86c49e0b6bd6 -size 23407 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/88a5a5ef66b246fe6f55e8600f8b0764_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/88a5a5ef66b246fe6f55e8600f8b0764_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/88a5a5ef66b246fe6f55e8600f8b0764_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/892f25e3d71d8e315a2a51092a8a8da7_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/892f25e3d71d8e315a2a51092a8a8da7_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/892f25e3d71d8e315a2a51092a8a8da7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/89cb4b0d1ef71532ac538cb30aa64087_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/89cb4b0d1ef71532ac538cb30aa64087_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/89cb4b0d1ef71532ac538cb30aa64087_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/89d5117b5c8c5209f100f1f0bf8ef540_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/89d5117b5c8c5209f100f1f0bf8ef540_img.jpg deleted file mode 100644 index df9a137f9dca8b21f509c3f1435b5dfe93853129..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/89d5117b5c8c5209f100f1f0bf8ef540_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb73b3f0fd718754e1e96517b99a19278dd51e0aa30232fede0cf0f31765b7a6 -size 116492 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/89d6b16f1a9a6fff9bb52f0ba5c3b851_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/89d6b16f1a9a6fff9bb52f0ba5c3b851_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/89d6b16f1a9a6fff9bb52f0ba5c3b851_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8a1804669974ce61da225f5794e809e5_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8a1804669974ce61da225f5794e809e5_img.jpg deleted file mode 100644 index a39b4b319fcefa47cdca2508d9bcf80624dbeaad..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8a1804669974ce61da225f5794e809e5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:90b7a2061c518b670fe38197a6d2de64010e30a78d3abb844e8b254496747352 -size 82996 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8a19b7d36c6b4ac9467a138b1faa3b93_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8a19b7d36c6b4ac9467a138b1faa3b93_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8a19b7d36c6b4ac9467a138b1faa3b93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8a7178c57b4e93672de9bed2cffdaf28_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8a7178c57b4e93672de9bed2cffdaf28_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8a7178c57b4e93672de9bed2cffdaf28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8b680f16d224d2d371ed781f38b4e798_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8b680f16d224d2d371ed781f38b4e798_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8b680f16d224d2d371ed781f38b4e798_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8b84b62118ea6ad8627d8d157eb0f7df_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8b84b62118ea6ad8627d8d157eb0f7df_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8b84b62118ea6ad8627d8d157eb0f7df_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg deleted file mode 100644 index c90ac7aee9f7e4044b4d9495ceff65714d68224c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8ba270d9a35a905e16a9b78e6b3ad2b8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ef20107d7ba821338c3e9523740cc8b0c1738a720536694c614e926bc9405dce -size 69847 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8c4d6d381f79ce611494afecaef05a6a_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8c4d6d381f79ce611494afecaef05a6a_img.jpg deleted file mode 100644 index 5e7947994cd13e250d9c0d52ef65603522742aeb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8c4d6d381f79ce611494afecaef05a6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106e9e22973ca4ce0c1f258162dc414bc5bb34b1da32f3c4eabcbfc9045381bf -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8dd5c733658cf8d82fe930745b58994c_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8dd5c733658cf8d82fe930745b58994c_img.jpg deleted file mode 100644 index 3d09d361349ed089a7a32e9d30e326380ff8aaf6..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8dd5c733658cf8d82fe930745b58994c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5da87f8a390ed95e0f671432166a3c328396f795b72f95fe762e526df8851710 -size 50614 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8de18f629e5d8ab818f3eff277a9c08b_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8de18f629e5d8ab818f3eff277a9c08b_img.jpg deleted file mode 100644 index ae40ff9f65af598b608645ac037e0ecd19ebaee8..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8de18f629e5d8ab818f3eff277a9c08b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:290c93a78be0faa8bb203500020064f9fab12023b06eea4654ec694b1d3a5129 -size 4595 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8e7f7b57b2b087bea39bac584f91d580_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8e7f7b57b2b087bea39bac584f91d580_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8e7f7b57b2b087bea39bac584f91d580_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8fc4f008ed8ed83c6d5341095767d099_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8fc4f008ed8ed83c6d5341095767d099_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/8fc4f008ed8ed83c6d5341095767d099_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/902f71a0cadbca9c579485eaa69effaf_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/902f71a0cadbca9c579485eaa69effaf_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/902f71a0cadbca9c579485eaa69effaf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/907205c224999d7da215523f7184b690_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/907205c224999d7da215523f7184b690_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/907205c224999d7da215523f7184b690_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/931bd52904f67b17796a38b47af51e30_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/931bd52904f67b17796a38b47af51e30_img.jpg deleted file mode 100644 index 59a564e4c760cbe655cda2e31a668069c351d25c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/931bd52904f67b17796a38b47af51e30_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:acef0b72c26c8f1aa49fde9997b82108427bd26a463ceada273cc8bf385f4c76 -size 90555 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/936b3e95dfcb46dbc0aafc0d71e13469_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/936b3e95dfcb46dbc0aafc0d71e13469_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/936b3e95dfcb46dbc0aafc0d71e13469_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9377b88f1c826970045f861ff1b24872_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9377b88f1c826970045f861ff1b24872_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9377b88f1c826970045f861ff1b24872_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/94d139463de55bcc311241aab71fac81_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/94d139463de55bcc311241aab71fac81_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/94d139463de55bcc311241aab71fac81_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/96cde10fa2d0afcd9873bd8fd706b082_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/96cde10fa2d0afcd9873bd8fd706b082_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/96cde10fa2d0afcd9873bd8fd706b082_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/977811d1c73b74f801be9f4c376694ca_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/977811d1c73b74f801be9f4c376694ca_img.jpg deleted file mode 100644 index 3b10203f988ee00eb9336240debd753022ad0a8b..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/977811d1c73b74f801be9f4c376694ca_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:68afe0a13cffaed0d888461884150be5b5bfe3742b264e7c92712d442f642b6a -size 23601 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/97c84277db020d4b9a9c3da9757baeea_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/97c84277db020d4b9a9c3da9757baeea_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/97c84277db020d4b9a9c3da9757baeea_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/97f6670a8f097f23fe35d62b76d75cf0_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/97f6670a8f097f23fe35d62b76d75cf0_img.jpg deleted file mode 100644 index eb03aaa1dcb8c4e3a77f1ba7fc0b034db99c470c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/97f6670a8f097f23fe35d62b76d75cf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d6b2c84835aa6c9a20ccf2808c8150dee3713e1c0c56a45331a8ef9f6ce03ff3 -size 21992 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/996c91d1d5b379328eade886b5451672_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/996c91d1d5b379328eade886b5451672_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/996c91d1d5b379328eade886b5451672_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/997340cf22533b0b7cea41bdb3db664d_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/997340cf22533b0b7cea41bdb3db664d_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/997340cf22533b0b7cea41bdb3db664d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9a8f8276c7199f1dd9f3754cf60555c6_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9a8f8276c7199f1dd9f3754cf60555c6_img.jpg deleted file mode 100644 index 18ba0e7c9a44a28033f9d4ca32ad45fbb926a6a8..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9a8f8276c7199f1dd9f3754cf60555c6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:672029c8734e394726831e8d5b60dab520da851d6e0c34a4db0cb10412c9e395 -size 43972 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9af97997b7d3fbca90b8ddba0ea39c6c_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9af97997b7d3fbca90b8ddba0ea39c6c_img.jpg deleted file mode 100644 index 899852f3895094fc9432df944956c32a04494834..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9af97997b7d3fbca90b8ddba0ea39c6c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:deed030384ecafba3b0e460c8e6a3fb42cda18614bf44af9bf09eb1194029cfd -size 58349 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9c01fc6fde0eb030a38b32f202079c17_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9c01fc6fde0eb030a38b32f202079c17_img.jpg deleted file mode 100644 index 7e2b4d20d2cc9bf0619e3d1d4496c6edf72a1fcf..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9c01fc6fde0eb030a38b32f202079c17_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6f50860cec2542ca7524f5e31b116aba6f29a0c6891fdbec5817be63cb590b2a -size 30750 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9ebd85380ef496499e5f23ec0d9cd744_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9ebd85380ef496499e5f23ec0d9cd744_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9ebd85380ef496499e5f23ec0d9cd744_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9f862801bce82634d3b5a1e0a195a799_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9f862801bce82634d3b5a1e0a195a799_img.jpg deleted file mode 100644 index c6f81b711680353e48d5a23f7f2fccaa879283dd..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/9f862801bce82634d3b5a1e0a195a799_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b6e4c16fbdd32a52a97973e8a951344fb6d862db9b5718469594957e5061e386 -size 19415 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a010f0a7b8e74337e19c8f5f9219841f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a010f0a7b8e74337e19c8f5f9219841f_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a010f0a7b8e74337e19c8f5f9219841f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a0167e3dcece9dcd8a378bcd98fb9cfa_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a0167e3dcece9dcd8a378bcd98fb9cfa_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a0167e3dcece9dcd8a378bcd98fb9cfa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg deleted file mode 100644 index 18c40dcc88057bd586dc4eb3549af763331afee8..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a05e675f8651ae7ccea1d0d68691d1a9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ca31a67af2d81e77180f04fff5a460a4c5f86bfc428698a3f8f572790732e916 -size 29584 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a0e8fe7862a6d7341faf5dac275277cc_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a0e8fe7862a6d7341faf5dac275277cc_img.jpg deleted file mode 100644 index a94f7c4cf40aea3f5768395b35f5ad5bb38b68b4..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a0e8fe7862a6d7341faf5dac275277cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:99b33313ad757eb5c8e8d7d267c0b5d866098ea040ddd9fba372ce2d2e1a85c2 -size 35437 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a238be4f934380d0f89d9080afb6b239_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a238be4f934380d0f89d9080afb6b239_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a238be4f934380d0f89d9080afb6b239_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a25cc37578be51dfde4634f35f09aff3_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a25cc37578be51dfde4634f35f09aff3_img.jpg deleted file mode 100644 index 649f15b2be2c8a0d3e7501b13872e92cc6ed08d3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a25cc37578be51dfde4634f35f09aff3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b7ee98d71dd67af28567d50b45fac8da86932cae631555f24e5fb4c92d2841d3 -size 100602 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a346e19f92f1699e3f96432c0464c957_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a346e19f92f1699e3f96432c0464c957_img.jpg deleted file mode 100644 index 7a9b933cb5b5702d2a43fe62b3191235812188a1..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a346e19f92f1699e3f96432c0464c957_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d894aa2e23b941fe56d5db99b0b72e667097ea9b83984d8638418e7cac043f18 -size 79447 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a34a521d4a9ba7071e87adf963f12fa7_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a34a521d4a9ba7071e87adf963f12fa7_img.jpg deleted file mode 100644 index 2757f49f97cb4a45fa402a8581c80279cb2301e9..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a34a521d4a9ba7071e87adf963f12fa7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:2968950123327fa92b8498502d9ffcd2c8b5f60f444fcb45cdabe63dd0967d25 -size 79512 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg deleted file mode 100644 index fdfaddbae1902f8db7d5ef935ad422c7c3f6443a..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a3b3abbf6d0b18f3dd4a83680b5e3e42_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4a0da77afbe51b8f4909de4879e56aaae9e45c5b3f071e9b35cc7bdb6e777d50 -size 38603 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a4b868a176f7e0448ee72483727e9f6f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a4b868a176f7e0448ee72483727e9f6f_img.jpg deleted file mode 100644 index 7d2aae01ad2e90193e2e13e23fcd35fff2357ee6..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a4b868a176f7e0448ee72483727e9f6f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:78795d01db4be8c75bb7dbc9e60b465ce32ff8de9e3041f635d8b8060f4ea0e2 -size 21922 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a4bfa2343d75076b79f7e33d93915e00_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a4bfa2343d75076b79f7e33d93915e00_img.jpg deleted file mode 100644 index 00c9d08233d265f92b45e8634a5516d94ffdfd7f..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a4bfa2343d75076b79f7e33d93915e00_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:54d4834c77e52ea9eb6dd96b3e4a8e6fa93bd9bd7a49d7a8032e5808c3d7e563 -size 24629 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a4c493cd9a047cf61c944c8c56ecf282_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a4c493cd9a047cf61c944c8c56ecf282_img.jpg deleted file mode 100644 index 7255b41f4128cb6cf756ff281b46a7c85e790a6f..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a4c493cd9a047cf61c944c8c56ecf282_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:07a0d6ebe5a5a3dcc48a2a7a138bab5f9bac983132c0f53fe77eaab26962b8c3 -size 44441 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a536d26fb2c7417a5684349af394986d_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a536d26fb2c7417a5684349af394986d_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a536d26fb2c7417a5684349af394986d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a54a85f03c26edd563f88dfc92ae279a_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a54a85f03c26edd563f88dfc92ae279a_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a54a85f03c26edd563f88dfc92ae279a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a5b26818e1fb14c928a004d92f8b1165_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a5b26818e1fb14c928a004d92f8b1165_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a5b26818e1fb14c928a004d92f8b1165_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a6f9ef297168667527ab18da412f917d_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a6f9ef297168667527ab18da412f917d_img.jpg deleted file mode 100644 index 16fd7cb08dcc9ea05b2ebf6f868d407e030f7db6..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a6f9ef297168667527ab18da412f917d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3eafd22500204a14c270d4dbdb2c5b4d6c8e9d69bee7848f12d790d7fc57e402 -size 10646 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a780a960b3f2de2493d5785bedae10ff_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a780a960b3f2de2493d5785bedae10ff_img.jpg deleted file mode 100644 index 475116850038bf14e87c9f4f74e1893287b7f3d7..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a780a960b3f2de2493d5785bedae10ff_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e761c0b61ad3cc383b9632dca442b50bf16ebd6f4841688b56521cbd76440ab0 -size 19260 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a9042d8edc99d26ea117a7d56e171d8e_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a9042d8edc99d26ea117a7d56e171d8e_img.jpg deleted file mode 100644 index 770236d5c958c5b62fafaed1a0e349e192a3dc77..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a9042d8edc99d26ea117a7d56e171d8e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:491adbeea89380690277453c348f03e14b34fc292ccaabc367abc49abd85676d -size 28379 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a9b24297dc6417e733ccbe4ed6505eac_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a9b24297dc6417e733ccbe4ed6505eac_img.jpg deleted file mode 100644 index 5e7947994cd13e250d9c0d52ef65603522742aeb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/a9b24297dc6417e733ccbe4ed6505eac_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106e9e22973ca4ce0c1f258162dc414bc5bb34b1da32f3c4eabcbfc9045381bf -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/aa22da43c463563d3d0035722bd79449_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/aa22da43c463563d3d0035722bd79449_img.jpg deleted file mode 100644 index b4050e06e7ebe166ad452bc4edc24c78db65f338..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/aa22da43c463563d3d0035722bd79449_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8a2c71320268b6520e1414df2054e8424f1cf739db93d85abf17ec7aff1af1d -size 35933 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/aadbdbdbe20c27e20e40cc56c1b8ee9c_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/aadbdbdbe20c27e20e40cc56c1b8ee9c_img.jpg deleted file mode 100644 index 012663930366a7000d2b0446ba6dbf3527d9fcd8..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/aadbdbdbe20c27e20e40cc56c1b8ee9c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e93b9e43b1fc8ef495cee92f613337c8c675659e48822f81593a61dda74b3131 -size 46810 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ab9c25a3205779c1860b702caaece17b_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ab9c25a3205779c1860b702caaece17b_img.jpg deleted file mode 100644 index 080253680b56144876e7dd5780f1c44700b596ed..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ab9c25a3205779c1860b702caaece17b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:17c501d6bd7fe4bd6543ac8db7f9b3b900a9f08c7253c459df0803eaed919e44 -size 33582 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/abf48594fdb5b54bb90df7ec9359efd9_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/abf48594fdb5b54bb90df7ec9359efd9_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/abf48594fdb5b54bb90df7ec9359efd9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/acf9eb2c446cfb72d7cb44a9149e24aa_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/acf9eb2c446cfb72d7cb44a9149e24aa_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/acf9eb2c446cfb72d7cb44a9149e24aa_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/af3b2fa532cb9b02a2aaeeb49e0118d0_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/af3b2fa532cb9b02a2aaeeb49e0118d0_img.jpg deleted file mode 100644 index 222a5956bb55d7090cee89052195b4344f5a114d..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/af3b2fa532cb9b02a2aaeeb49e0118d0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ac20fb4a43df52a4135d0e7e169df0fdf76484a167d376c4ab85f82ce9a3d5a7 -size 51938 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/afbd1c536e2ee87d33014bb58ab6d1c4_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/afbd1c536e2ee87d33014bb58ab6d1c4_img.jpg deleted file mode 100644 index b908d38cc1d4616334ba15a8d470800141756b3d..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/afbd1c536e2ee87d33014bb58ab6d1c4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:634b7000706dc43ca5e635c33256c6b1d853758f3193088be9563ba4ed5bec38 -size 187500 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/afe5eb459b7c9cfe880b067777d876d8_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/afe5eb459b7c9cfe880b067777d876d8_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/afe5eb459b7c9cfe880b067777d876d8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b0d9faaee53565a4a333764297aa7b97_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b0d9faaee53565a4a333764297aa7b97_img.jpg deleted file mode 100644 index fcc21e112654d7b1a7ed9a34ef3276d2d094bf5e..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b0d9faaee53565a4a333764297aa7b97_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3e3d88b195f6ebbc94d62b90b99d4ba33c5bb6423e072ca345401c22c9c308f7 -size 4558 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg deleted file mode 100644 index fe7b5a559589feeab66750ee82a823c50bae3a41..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b1784a5cbeeb3d9fb9e60b333019c721_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:3459e1ef151f93bbd2f8f31f8ef9b37183882c4faf74eb79240554e02a91344e -size 37198 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b1e7bb95fa1587d870de03df02477df4_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b1e7bb95fa1587d870de03df02477df4_img.jpg deleted file mode 100644 index def6bba143666b67f5ebca7cd59f4f739e9ecb0f..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b1e7bb95fa1587d870de03df02477df4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:be01e051c1f75c15138d15aa78167da8f66ac46f4c0001b99ae3b430b6f1e3de -size 104171 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b320ccb4d6f993cc67c7b5b0b85cfacc_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b320ccb4d6f993cc67c7b5b0b85cfacc_img.jpg deleted file mode 100644 index 2fc4ba3287f6c696bc30fc629ac35e72f77e8e17..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b320ccb4d6f993cc67c7b5b0b85cfacc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:34eae50c3ac2057644d217aed1a2db6a3ffd2485fe07ad8a55751fe56a55747d -size 58395 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b3e29e133dd986546948ba4332cda172_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b3e29e133dd986546948ba4332cda172_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b3e29e133dd986546948ba4332cda172_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg deleted file mode 100644 index 0eb1bcd4f6f61de0d940bfd02ea09db083255bbf..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b432c6c13fa4f8bb90f5fb9060ef3bcd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:37f1b4b8126089348632b2eb4f5d9cbbcb26a75cf3534fc31f0276343a7d4f02 -size 49252 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b4478614140064dedc2161238ce2f2a5_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b4478614140064dedc2161238ce2f2a5_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b4478614140064dedc2161238ce2f2a5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b44856596231076ae15efca95eb8ef86_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b44856596231076ae15efca95eb8ef86_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b44856596231076ae15efca95eb8ef86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg deleted file mode 100644 index 760b470e444073458c5c3f5143a541fb2857e9c7..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d83b5b796f217aa81ace4fcc7bba0f76a84f90738b8316a4c6581c1b6fe2c67e -size 72185 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b4cbe4bfe7868be70d1549b983749783_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b4cbe4bfe7868be70d1549b983749783_img.jpg deleted file mode 100644 index 3517f5e7e55c34f542e542b343fa896c246bf446..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b4cbe4bfe7868be70d1549b983749783_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:923e2824782eed95dea3061316b0cbf437128e2b81c250587c7677357da20b85 -size 14206 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b560268ea8f6526970f23f0da225b099_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b560268ea8f6526970f23f0da225b099_img.jpg deleted file mode 100644 index 47db8b29e3205481e7f06bae3e18de31e7c92d49..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b560268ea8f6526970f23f0da225b099_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9072a4144bdb677d96490a8bd5601dc95012817f56b88df2c18307291c10f702 -size 37355 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b73e15bd8ab2756cf10f9344fe551227_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b73e15bd8ab2756cf10f9344fe551227_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b73e15bd8ab2756cf10f9344fe551227_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b774dfc5023e15e9c352b97ca25a56d4_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b774dfc5023e15e9c352b97ca25a56d4_img.jpg deleted file mode 100644 index d09381e993bfc21d8688eeffe03c544fe757451c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b774dfc5023e15e9c352b97ca25a56d4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b30d6e649e203496204f07b9da82de9c86a7840d8252c9b120e070a76be488e8 -size 44397 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg deleted file mode 100644 index 59fa5bd3734e33b1875636bb5d0acacc69831695..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b8661c6c54f72ecc7ff6cb05e47b2891_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d66c256657326ea5150681999b0c1ff96067bc2e096f79dc0d752a47a70e4d1a -size 25826 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b87818c8505328b198d035761bbc3f2d_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b87818c8505328b198d035761bbc3f2d_img.jpg deleted file mode 100644 index 63ffb8a9b6f7b227609c3506913bc50edc7d0d16..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b87818c8505328b198d035761bbc3f2d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d8beb0b9cfb736ab37ec96dcef4892ff2a0dc66dea8debd25e3624bc6cd60bd4 -size 69685 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b87b52c04ccb835fa90fd2c6926f224d_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b87b52c04ccb835fa90fd2c6926f224d_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b87b52c04ccb835fa90fd2c6926f224d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b911dd89c2efca8a4fa52d6a6cfd7b6a_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b911dd89c2efca8a4fa52d6a6cfd7b6a_img.jpg deleted file mode 100644 index 5e7947994cd13e250d9c0d52ef65603522742aeb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b911dd89c2efca8a4fa52d6a6cfd7b6a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106e9e22973ca4ce0c1f258162dc414bc5bb34b1da32f3c4eabcbfc9045381bf -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b93f124d1a7bfa31a18e5ffae184e015_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b93f124d1a7bfa31a18e5ffae184e015_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b93f124d1a7bfa31a18e5ffae184e015_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b988d13a7e9ebb10a1df8e0957a15c51_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b988d13a7e9ebb10a1df8e0957a15c51_img.jpg deleted file mode 100644 index 7e6c02a48eda1e8075352a9f41e2ecc321ec9273..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b988d13a7e9ebb10a1df8e0957a15c51_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:afad5056a362a7a1946ebf8ad07acfd33644f1f7d9bb06be04efe24fcaddbf51 -size 185421 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b99bfa6a26ede115d00d81059ee4ce6b_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b99bfa6a26ede115d00d81059ee4ce6b_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/b99bfa6a26ede115d00d81059ee4ce6b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bb22213587bd90f266a5003c78cb13d9_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bb22213587bd90f266a5003c78cb13d9_img.jpg deleted file mode 100644 index c90e03ea1a08fa47a07420a9deba990f2ac973ab..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bb22213587bd90f266a5003c78cb13d9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e7208ebdc11e1ddecccea96ef7b02a6532541e8bf41826df7629c380ae59adfb -size 68925 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bc0363f46427865273bebd3bbe4dad53_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bc0363f46427865273bebd3bbe4dad53_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bc0363f46427865273bebd3bbe4dad53_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bc2ae13444c5d7158a37b4af477e63b7_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bc2ae13444c5d7158a37b4af477e63b7_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bc2ae13444c5d7158a37b4af477e63b7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bc3d1c04d342094c893d5064974c9ee7_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bc3d1c04d342094c893d5064974c9ee7_img.jpg deleted file mode 100644 index a8c4d3b3ff820536e425602dca2afaa2efe24fdb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bc3d1c04d342094c893d5064974c9ee7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:bcebe5c00e48d83807272f06cc05f0a97d42bf63e02dff83bb91ed691def3f52 -size 54228 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bc957fc11b2b393aa61c0e2205d34fe8_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bc957fc11b2b393aa61c0e2205d34fe8_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bc957fc11b2b393aa61c0e2205d34fe8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bc9fcd67cd9525c7cf4a4cd4323e7ae8_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bc9fcd67cd9525c7cf4a4cd4323e7ae8_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bc9fcd67cd9525c7cf4a4cd4323e7ae8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bf4c652fad7b49024d2ffb350009d799_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bf4c652fad7b49024d2ffb350009d799_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/bf4c652fad7b49024d2ffb350009d799_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c002a785d5d05bd7f69d54a01401fd86_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c002a785d5d05bd7f69d54a01401fd86_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c002a785d5d05bd7f69d54a01401fd86_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c1ac5a44074f1a512562283a8b7a4763_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c1ac5a44074f1a512562283a8b7a4763_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c1ac5a44074f1a512562283a8b7a4763_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c2dbaf7c88ad38cb8620f6d731935ed8_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c2dbaf7c88ad38cb8620f6d731935ed8_img.jpg deleted file mode 100644 index 2c88be98d161d0c6489af92ec31031bcfc69a59f..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c2dbaf7c88ad38cb8620f6d731935ed8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5d1032e93b5ecce9161e9093a2255dd0377894c1f5898e5b38827b9cc11f5606 -size 52773 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c35369e1910a610d73fbdec77f65fd94_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c35369e1910a610d73fbdec77f65fd94_img.jpg deleted file mode 100644 index 6a3df27f8d5c3e9bf420a44731ef2f9aae7a48f0..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c35369e1910a610d73fbdec77f65fd94_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a181de19a35744ff231bd1021da96f73fba8cbca44c60a12dc8e3fd2dc57de19 -size 41745 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c419b566d720267c499087add1506018_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c419b566d720267c499087add1506018_img.jpg deleted file mode 100644 index e92106e1c0e6fdf25e6c27a5000e270a5aa7ca72..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c419b566d720267c499087add1506018_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b30ac0dec7211ff3d7e9ca9d5bb89eca998ac068faf6b53e660b12a5de343667 -size 132841 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c43572681d8f7b8331d7b0510c81b1c7_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c43572681d8f7b8331d7b0510c81b1c7_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c43572681d8f7b8331d7b0510c81b1c7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c49b985171e8b894ea6136ed358d0b50_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c49b985171e8b894ea6136ed358d0b50_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c49b985171e8b894ea6136ed358d0b50_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c65ad236792ad44010344a71df2b4947_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c65ad236792ad44010344a71df2b4947_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c65ad236792ad44010344a71df2b4947_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c803f6f6e2c49429d2951832bd0f208d_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c803f6f6e2c49429d2951832bd0f208d_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c803f6f6e2c49429d2951832bd0f208d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c85d9353a4a587e3d4c92fad86440b4f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c85d9353a4a587e3d4c92fad86440b4f_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c85d9353a4a587e3d4c92fad86440b4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c995e0bb4efc8c0f2994428aa1245709_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c995e0bb4efc8c0f2994428aa1245709_img.jpg deleted file mode 100644 index 3ba0cf9ffde7437383719b32828b0074e59b6d70..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c995e0bb4efc8c0f2994428aa1245709_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:50ecb3189d71f611ab3bbff812b0fd0d1cdc43d15ed77cbc227ceb9cd4f2248d -size 56365 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c9dbcb0808bdcc4e165c1cd4f74c2774_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c9dbcb0808bdcc4e165c1cd4f74c2774_img.jpg deleted file mode 100644 index 5e7947994cd13e250d9c0d52ef65603522742aeb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/c9dbcb0808bdcc4e165c1cd4f74c2774_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106e9e22973ca4ce0c1f258162dc414bc5bb34b1da32f3c4eabcbfc9045381bf -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cad9f65638b7c839304d8939cb11e6d2_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cad9f65638b7c839304d8939cb11e6d2_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cad9f65638b7c839304d8939cb11e6d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cb9ec04a3c2dd737257c1e1634ab4a90_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cb9ec04a3c2dd737257c1e1634ab4a90_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cb9ec04a3c2dd737257c1e1634ab4a90_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cc4b80f3af11f554590470dbaa70daf8_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cc4b80f3af11f554590470dbaa70daf8_img.jpg deleted file mode 100644 index 66238db5642682db5b2808a0cd737a41df0417f5..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cc4b80f3af11f554590470dbaa70daf8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0ea129b1b35d2cee2a44023e5b228f2b9f5d2e2e7aba0d4a4cfd73f61fd62f8a -size 92114 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cc9b98d9bd87c73583bc813c02b91351_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cc9b98d9bd87c73583bc813c02b91351_img.jpg deleted file mode 100644 index ddf709cf2f03795b5ae5b7ef6c26383609cfd4e4..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cc9b98d9bd87c73583bc813c02b91351_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9a6989f8549e0b85a11436724b71e33f064a5dc1dd1e93d10787cbb5c60d5330 -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg deleted file mode 100644 index 90e4475ec569d9106a0c150ca3111c0627656273..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ccfd5ed8d9795009e923e2a0cacbcd6e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6baf6a0e78aa89d29756ebf61d460dbb592b0017882c2dbb7fa541d5ea1146f2 -size 33389 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cdca70d5b05bc1e41a014d2c2cb4ad9f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cdca70d5b05bc1e41a014d2c2cb4ad9f_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cdca70d5b05bc1e41a014d2c2cb4ad9f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ce58a77ff34d610cd0634eacffbd3eaf_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ce58a77ff34d610cd0634eacffbd3eaf_img.jpg deleted file mode 100644 index 74a9fa56c1b82d2eafb0feb9a9b5c12f269e367e..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ce58a77ff34d610cd0634eacffbd3eaf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:64ad7300d375f37943f3cd159482d2778ce9497e78f42240ae23e8a123de6b7c -size 67961 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cef981f48160da6ca248560bbf31eb7f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cef981f48160da6ca248560bbf31eb7f_img.jpg deleted file mode 100644 index 39b4d05e74517e288f8307496b4c57763053ed2c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cef981f48160da6ca248560bbf31eb7f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d0d849fc1751b54a989975ab0a89baf6dc41b0d34cf6229088f7f46c59fa9793 -size 48519 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cefc8594a8e8125d6cba7dab877c86f2_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cefc8594a8e8125d6cba7dab877c86f2_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cefc8594a8e8125d6cba7dab877c86f2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cf03eff1218a8cc1be6b05de892162de_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cf03eff1218a8cc1be6b05de892162de_img.jpg deleted file mode 100644 index 99795e4e37115df5480f12fd125ce99aba09aa57..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cf03eff1218a8cc1be6b05de892162de_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:df3fdb735cdf33d605ead5154f5c515b7927aedb86a2831ed02d8097737159d5 -size 114689 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cf0c952e95d8aa8548cf54d9c35fe617_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cf0c952e95d8aa8548cf54d9c35fe617_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cf0c952e95d8aa8548cf54d9c35fe617_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cf8bd014a50b7c69435e804f67f9617f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cf8bd014a50b7c69435e804f67f9617f_img.jpg deleted file mode 100644 index 463c810080a47d07c5ddfb8da034645448a106f2..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cf8bd014a50b7c69435e804f67f9617f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7d0ec6834b2ff0fa75ab55566b630d73415aaed4f4346ab13c93b2911dcb994f -size 33432 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cf9458a921d65fc6bcee3e25f86829d3_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cf9458a921d65fc6bcee3e25f86829d3_img.jpg deleted file mode 100644 index 5e7947994cd13e250d9c0d52ef65603522742aeb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cf9458a921d65fc6bcee3e25f86829d3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106e9e22973ca4ce0c1f258162dc414bc5bb34b1da32f3c4eabcbfc9045381bf -size 4552 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cfa6466163467e81d9b2d9c5785222bf_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cfa6466163467e81d9b2d9c5785222bf_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cfa6466163467e81d9b2d9c5785222bf_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg deleted file mode 100644 index 71a255b49089887106d78d7675009a7203f86750..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cfda9df1319e04207eb28bcefd1dab7b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8c83cea298212c959fae19b7e43a6013f7111ea5353612a53be1be1627842f1c -size 65864 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cff94fda4719415b20d835d30d2bef5a_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cff94fda4719415b20d835d30d2bef5a_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/cff94fda4719415b20d835d30d2bef5a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d01f4371bb8136148156771a18b9ea89_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d01f4371bb8136148156771a18b9ea89_img.jpg deleted file mode 100644 index 1600e875a4f18b9bef88380466a932e752339f52..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d01f4371bb8136148156771a18b9ea89_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e52b42f2144164f1f313cde1d29a69becd92fd3073362372255e740189535447 -size 65423 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d091b5e790d0a8989de686e48854c200_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d091b5e790d0a8989de686e48854c200_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d091b5e790d0a8989de686e48854c200_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg deleted file mode 100644 index e1909086d83f11b18e3887deb61f9c88b5b2fa50..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d15e2d3e8dd9157eb7f0cc120097484a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:106ddedd6316860e69d7387463c723ed4bb649a8bf1ae3b897be06e3eca5fcd9 -size 119201 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d261c34ab67ef2c320a5b6a75ceed2c5_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d261c34ab67ef2c320a5b6a75ceed2c5_img.jpg deleted file mode 100644 index 36ef3d74a3d5e4efe9fec01045563095b19fd7d1..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d261c34ab67ef2c320a5b6a75ceed2c5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b1a6852cd7287d6175343848889237b93d25d25bfb27faa3838c8f239aa96286 -size 4546 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d336e7ffee4f537d0805ca840ec28582_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d336e7ffee4f537d0805ca840ec28582_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d336e7ffee4f537d0805ca840ec28582_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d41b7d532c3b6df53d42863e7c50b9f3_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d41b7d532c3b6df53d42863e7c50b9f3_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d41b7d532c3b6df53d42863e7c50b9f3_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d455e47a6d660a3cc29a125a2cbe355b_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d455e47a6d660a3cc29a125a2cbe355b_img.jpg deleted file mode 100644 index c0057d1ca6f02f3e84be944876d3b68efb2c097e..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d455e47a6d660a3cc29a125a2cbe355b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8d1d032282c738a08ce54912663ad77ef4045b7ba22e91582755db74f9cde002 -size 48713 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d4adfc6e910fa1c0c08db2ba4da84754_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d4adfc6e910fa1c0c08db2ba4da84754_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d4adfc6e910fa1c0c08db2ba4da84754_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d4e9f8f6bf5d7853ecae9c9633900af1_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d4e9f8f6bf5d7853ecae9c9633900af1_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d4e9f8f6bf5d7853ecae9c9633900af1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg deleted file mode 100644 index 5ab150b2391ca9fdb078145283a0d4c2416a06c0..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d512ce4e3ac0de6c26d0e74a85ef2cbd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:69e7d565984502ddaff86da98f73a14c14937b0fe54bd9154fd17d330d84b98c -size 71014 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d73afb244bcc76da2339ec0d69bc0368_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d73afb244bcc76da2339ec0d69bc0368_img.jpg deleted file mode 100644 index 210118bfed2915b6bd6769c673291d539e944151..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d73afb244bcc76da2339ec0d69bc0368_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:174c5469f27e7413d2eaf8b3c04b5a21bd62154742ef3db89a376a6ed40c8bf9 -size 4498 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d74c250a8e512a5480acc7b20ae0471c_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d74c250a8e512a5480acc7b20ae0471c_img.jpg deleted file mode 100644 index 6d572ed15d6dc6a338a6e4c331331cf6ef35cb29..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d74c250a8e512a5480acc7b20ae0471c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0f9dec03917960f290d3df029613b020a1727eaac66aa054c94557fbd14344b6 -size 4384 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d952d1b71abf550d8d9740581f6e7e02_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d952d1b71abf550d8d9740581f6e7e02_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d952d1b71abf550d8d9740581f6e7e02_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d9638e837004a4e09dbbc50b8aecbd5f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d9638e837004a4e09dbbc50b8aecbd5f_img.jpg deleted file mode 100644 index 89af9c9aa7d06c93b52dcfde22292c8ba9961224..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/d9638e837004a4e09dbbc50b8aecbd5f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0aeb1f6392cd7e8d901fad91243c8f57e3ec781606b4f624619254bae9765cd5 -size 75692 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/daf05db9f13b34fb12da52f007bbfe5b_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/daf05db9f13b34fb12da52f007bbfe5b_img.jpg deleted file mode 100644 index 303446520cfd97e7ef42afaa091ab78c4c63a5b6..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/daf05db9f13b34fb12da52f007bbfe5b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:02609e5245f06a8bf4baf2e5338a844eac90345c6ea8e4bf1c4e44092837a67c -size 15967 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dbe4ffa9778863279b48b56fe097cd23_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dbe4ffa9778863279b48b56fe097cd23_img.jpg deleted file mode 100644 index bec9c72c8379a56b70ae146e7348f490900dbdc5..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dbe4ffa9778863279b48b56fe097cd23_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:eb4e280950ccbf6ca81bc4877d2c2e4310ad03e3d68e647d19c04470b8946c34 -size 42449 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dc0338212e8a6ac4e88649b89292e119_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dc0338212e8a6ac4e88649b89292e119_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dc0338212e8a6ac4e88649b89292e119_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dc1e692e5b7efd8e5a2a790c458646d9_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dc1e692e5b7efd8e5a2a790c458646d9_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dc1e692e5b7efd8e5a2a790c458646d9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dc79f71c6bae35b5d62f636dbc7f9bb9_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dc79f71c6bae35b5d62f636dbc7f9bb9_img.jpg deleted file mode 100644 index 5c202f456feaf2d18d0d1965d3de1a6d51222303..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dc79f71c6bae35b5d62f636dbc7f9bb9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c116c66bab08b855bfe9241139d1553d12d2e4acb51704fdf6fe5f68888c3ead -size 30360 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dd5771673aececa53d42ece89218299d_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dd5771673aececa53d42ece89218299d_img.jpg deleted file mode 100644 index a643684f0c4431bfd02bc8e5df81248e4f540bfb..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dd5771673aececa53d42ece89218299d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c65c17eeaa79ad6b888b84b92a13f17e6133b07160b4f10e188c9727069b807a -size 66810 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dd6ca069ca77109ad861ad55b7527083_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dd6ca069ca77109ad861ad55b7527083_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dd6ca069ca77109ad861ad55b7527083_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ddee3e67e0dfc22e25188fa635a19558_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ddee3e67e0dfc22e25188fa635a19558_img.jpg deleted file mode 100644 index 18db3e800af8595c07cb059084a0ed02db8db334..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ddee3e67e0dfc22e25188fa635a19558_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e5b6d77a3e17641144d605448e09d68eb889b4987f4aa155b5945a629723981a -size 40607 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/deb817f1a57c7185d59319e4113beb4f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/deb817f1a57c7185d59319e4113beb4f_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/deb817f1a57c7185d59319e4113beb4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/df1966d80c74bc127f159a48f38b13ee_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/df1966d80c74bc127f159a48f38b13ee_img.jpg deleted file mode 100644 index 77dc5a8777e918d55a00423a477784822b9b4c80..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/df1966d80c74bc127f159a48f38b13ee_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a097bd817b5e64524864061092bd3f9effc01b5769d9c8a0b564e013eb4516ee -size 135197 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dfafe39c233a62ec8ebd71e42992c14d_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dfafe39c233a62ec8ebd71e42992c14d_img.jpg deleted file mode 100644 index 8f01f58ce5d203ef493d08eb524bcb111401198c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dfafe39c233a62ec8ebd71e42992c14d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f77ce2040180c642d5d7b0cc3fcdae58d1cb778025f4c27ce217c533cd005182 -size 60823 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dfc404a5cd40cf7c47d775536cb7d9b5_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dfc404a5cd40cf7c47d775536cb7d9b5_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/dfc404a5cd40cf7c47d775536cb7d9b5_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e05122559f56af5699789b7118d8fe87_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e05122559f56af5699789b7118d8fe87_img.jpg deleted file mode 100644 index cc6a935c8a1e6b5f4a4a42cee4b8187c7ef67691..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e05122559f56af5699789b7118d8fe87_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:78dc1928b2efab17a6f4ea335a5fa715a456d162d8ec4705d6a7762b0e1f8987 -size 38542 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e05b36c0d46549e681ce6581422c66b2_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e05b36c0d46549e681ce6581422c66b2_img.jpg deleted file mode 100644 index a6eae1543ba4266ba713399981c99df8f52266fa..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e05b36c0d46549e681ce6581422c66b2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d6414d65074fef251a741b0dc49fa53ae82eb37aa2d54253267cbb2e45b6e7ca -size 65816 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e0627c8e3dfda5da1ee8d5a90c9f7489_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e0627c8e3dfda5da1ee8d5a90c9f7489_img.jpg deleted file mode 100644 index 7d7d3aab00575a8101c825149a8dd461e6b61823..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e0627c8e3dfda5da1ee8d5a90c9f7489_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:79a25c7ed5182ccb13df464f178393d12822afc9233f809601598f36beecb6c4 -size 61430 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg deleted file mode 100644 index df3eab6d70dc30d3d893ef9ee2e03bc7d7185d80..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6aeb325b0a3a93bf30410e12c3f69ee630446699139ea778e8420e2a8beaca0b -size 64443 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e2ecc24ce8f944e62170f1927918fbbd_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e2ecc24ce8f944e62170f1927918fbbd_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e2ecc24ce8f944e62170f1927918fbbd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e3a643cd846de9aea87f9111e89d2a58_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e3a643cd846de9aea87f9111e89d2a58_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e3a643cd846de9aea87f9111e89d2a58_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e4e99fa5cbfdbea733b3164d5ac82e9e_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e4e99fa5cbfdbea733b3164d5ac82e9e_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e4e99fa5cbfdbea733b3164d5ac82e9e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e5119fd755a0bf1a2106b4198c710d70_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e5119fd755a0bf1a2106b4198c710d70_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e5119fd755a0bf1a2106b4198c710d70_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e559cb8d15d95b7f4c5761d295051cc0_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e559cb8d15d95b7f4c5761d295051cc0_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e559cb8d15d95b7f4c5761d295051cc0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e5ded42f8e352da02ee86cb55550c45d_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e5ded42f8e352da02ee86cb55550c45d_img.jpg deleted file mode 100644 index 7613c68f2a81130dc4f086c2a087c5ad57f0040b..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e5ded42f8e352da02ee86cb55550c45d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8f00d091c7d44d18fffbbc2d1c8f8adf4a847adade10d430bbd3406f122a63c2 -size 39932 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e600afc5acba7c01dcd3b8d0e40ccf79_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e600afc5acba7c01dcd3b8d0e40ccf79_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e600afc5acba7c01dcd3b8d0e40ccf79_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e6bbbd08cf99c3b3b772ef973bad0c5b_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e6bbbd08cf99c3b3b772ef973bad0c5b_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e6bbbd08cf99c3b3b772ef973bad0c5b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e84dd53f6912e1d1da8c934533cc599f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e84dd53f6912e1d1da8c934533cc599f_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e84dd53f6912e1d1da8c934533cc599f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg deleted file mode 100644 index 9d2c0ec458b12238836092e3640f9d4d8c5a7ffd..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/e9540f7fc7a084859dd5cdb0f9b7fcf2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:4feca548182d65421a32a3ac685518b9a03651d68950be0815083d2351048629 -size 63036 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ec0158057f8ccaf74edba16682ec5444_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ec0158057f8ccaf74edba16682ec5444_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ec0158057f8ccaf74edba16682ec5444_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ecae674475cecdd0962200a5d1e2591e_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ecae674475cecdd0962200a5d1e2591e_img.jpg deleted file mode 100644 index 02bfe965c822648ef2e18b1ead0273168eb823f0..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ecae674475cecdd0962200a5d1e2591e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b954aa493c1811cb130284edc0db947fff4b30bd9baa6075836878233a68df2f -size 132984 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/edbcecfff447173e9b62de586f536fc7_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/edbcecfff447173e9b62de586f536fc7_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/edbcecfff447173e9b62de586f536fc7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ee8a6b77d1ef86f5640e28868874cace_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ee8a6b77d1ef86f5640e28868874cace_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ee8a6b77d1ef86f5640e28868874cace_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ef700c02b0f82deab85f21ebd6fb4607_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ef700c02b0f82deab85f21ebd6fb4607_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ef700c02b0f82deab85f21ebd6fb4607_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f03929249a5b45fa7fb006ae5a5b88e4_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f03929249a5b45fa7fb006ae5a5b88e4_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f03929249a5b45fa7fb006ae5a5b88e4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f1ba1e68228ebd4c3109371574a723e6_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f1ba1e68228ebd4c3109371574a723e6_img.jpg deleted file mode 100644 index cacc144d18ceba72a847753f41758c3c56ae1f50..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f1ba1e68228ebd4c3109371574a723e6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c45824faecfaae02c815a179a9472806173ec1299b4fb7c679caa5e088e894c2 -size 43982 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f2f0092624aaf8ad2bcb99a821409714_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f2f0092624aaf8ad2bcb99a821409714_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f2f0092624aaf8ad2bcb99a821409714_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f33f3f93c0261cc1a43b20301b2b13b4_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f33f3f93c0261cc1a43b20301b2b13b4_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f33f3f93c0261cc1a43b20301b2b13b4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f3f1e70baae0c2d8000049b4c9a11d4e_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f3f1e70baae0c2d8000049b4c9a11d4e_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f3f1e70baae0c2d8000049b4c9a11d4e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f455955c4bc84005728b4138f19098dc_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f455955c4bc84005728b4138f19098dc_img.jpg deleted file mode 100644 index bea92d154461beeeab8a4eb11930d283ee4acb74..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f455955c4bc84005728b4138f19098dc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:7c65565ebfd87309678b94976dae5e27fdec38cd98a3f9816f91586007650f8b -size 33154 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f4ab7543d95dae81b4fbddf33d5673b9_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f4ab7543d95dae81b4fbddf33d5673b9_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f4ab7543d95dae81b4fbddf33d5673b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f53d26a0d0ab96356a6ed4f869f8d64d_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f53d26a0d0ab96356a6ed4f869f8d64d_img.jpg deleted file mode 100644 index f0eb8ac682a860b9ff50633a9998671a0bbff20e..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f53d26a0d0ab96356a6ed4f869f8d64d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a4da4d9226c85d97cbe2396bcbf327aa6fef8fee23087c53c5baf21fa3ff192f -size 102377 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f5a92c55d9f25576d21e252a7d9e1b52_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f5a92c55d9f25576d21e252a7d9e1b52_img.jpg deleted file mode 100644 index 16589edd9515331f9eaa041da17fbc85cdd1757c..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f5a92c55d9f25576d21e252a7d9e1b52_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9d54abb5c265b8903e5b0323218a8872faad23cdd69502848b814866b0641675 -size 4499 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f74d8082f6a1b4ea9be39c583e6272fe_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f74d8082f6a1b4ea9be39c583e6272fe_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f74d8082f6a1b4ea9be39c583e6272fe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f7565d053f61e82dae98ec4228d1fde1_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f7565d053f61e82dae98ec4228d1fde1_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f7565d053f61e82dae98ec4228d1fde1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f756d8e1fde6bc6ebdf4a5d7f1b2a57a_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f756d8e1fde6bc6ebdf4a5d7f1b2a57a_img.jpg deleted file mode 100644 index 10782e56d32c833ca8cea38c2e022577237b2763..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f756d8e1fde6bc6ebdf4a5d7f1b2a57a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:112792ec2031cc1578ee823814ae396882550576ab4ec3a1ff425942fc1bd166 -size 4554 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg deleted file mode 100644 index 37456643addcf6426077b6e6cdfe696b80666052..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f7b2cf9e1b71dc4f900f3810646d3903_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:af441183011422a5e68620c8a1a3fe974d7c60b65bae11933f049ee3a2bc8ce5 -size 97553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f86fbc9826e1910a39e36f7e62b568c2_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f86fbc9826e1910a39e36f7e62b568c2_img.jpg deleted file mode 100644 index 90d083bc1a68aa473f7532801e2b55cca0614804..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f86fbc9826e1910a39e36f7e62b568c2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f124c2f0c0bdb295d60bf09c54c7b0897ac629d89d5f0d5cb086add8f84ebea2 -size 60877 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f9873201604e723ae0bafb7e389ef619_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f9873201604e723ae0bafb7e389ef619_img.jpg deleted file mode 100644 index a0a24d8a64c36d00a719bc49543f291cd85c2b2e..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/f9873201604e723ae0bafb7e389ef619_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e60ffecf3f3bfa92771f194ccf6bb2461e7d1a92567c42bd0861a4b1de16c3a8 -size 36864 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/fc3e2b49a9f850951570e502393b697f_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/fc3e2b49a9f850951570e502393b697f_img.jpg deleted file mode 100644 index 939c4ef4fc6edb1941981c40ad692b020b7fc535..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/fc3e2b49a9f850951570e502393b697f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:dfd23ebd10b616a872e89235debd3b360ba1f19b4be934a5d8ae92631a6971fc -size 52546 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/fd763843f72bbac2f86c017a8a570595_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/fd763843f72bbac2f86c017a8a570595_img.jpg deleted file mode 100644 index 4cf8876a447755f86861c9cc57bc3519aa4bef53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/fd763843f72bbac2f86c017a8a570595_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33ecc79324f0b3f697346e9c64ce6b4390e9d30df5fcd1365e16c4afa1da6ce1 -size 4553 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/febb6833677d1ca3a5550901b7673b63_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/febb6833677d1ca3a5550901b7673b63_img.jpg deleted file mode 100644 index 79827a5debc0cda80c5f9d5a1c10016dbc567796..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/febb6833677d1ca3a5550901b7673b63_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9e9965cbd56b10e6ee1b99114c1d3df41c3975ad633eefe8bd0bdae0f97ba5ad -size 81569 diff --git a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ffe0fef452a0ae9a20253c319c54e13c_img.jpg b/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ffe0fef452a0ae9a20253c319c54e13c_img.jpg deleted file mode 100644 index feabd3a95a6a8ef49c9bee6307303dafff0e192b..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XPSAAS.0-R005-v10.00/images/ffe0fef452a0ae9a20253c319c54e13c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6f341342979824328951ed14843f78ec41a245e47be1a124e5c71fed9106faa1 -size 41876 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/doc.md b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/doc.md deleted file mode 100644 index 86f29308f37cde8831c7a99b2be25826dc484f64..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/doc.md +++ /dev/null @@ -1,2365 +0,0 @@ - - -![O-RAN ALLIANCE logo](2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg) - -The logo for the O-RAN ALLIANCE, featuring a colorful circular icon to the left of the text "O-RAN" in blue, with "ALLIANCE" in smaller blue letters underneath. - -O-RAN ALLIANCE logo - -O-RAN.WG9.XTRP-REQ.0-R005-v02.00 - -*Technical Specification* - -# **O-RAN Open Xhaul Transport Working Group 9** - -# **Xhaul Transport Requirements** - -Copyright © 2025 by 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 - -| Author | Company | Chapters | -|-------------------------|------------------|--------------------------| -| Sumithra Bhojan | AT&T | 7 | -| Lujing Cai | AT&T | 7, 11, 14, Appendix A | -| Philippe Chancelou | Orange | 12, Appendix C | -| Kamatchi Gopalakrishnan | Juniper Networks | 13 | -| Liuyan Han | China Mobile | 13 | -| Derek Reese | AT&T | 13, 14 | -| Stefano Ruffini | Ericsson | 13 | -| Sapna Sangal | Mavener | 10 | -| Simon Spraggs | Cisco Systems | 1-6, 8-9, 11, Appendix B | -| Krzysztof Szarkowicz | Juniper Networks | 13 | -| Reza Vaez-Ghaemi | Viavi Solutions | 1-7, Coordination | - -1 - -# 1 Revision History - -| Date | Revision | Author | Description | -|------------|----------|--------------------------------|-------------------------------------------------------------------------------------| -| 2020/11/11 | V01.00 | Reza Vaez-Ghaemi | Incorporated responses to comments from the WG9 review process ended on Nov 9, 2020 | -| 2025/11/20 | V02.00 | Sapna Sangal, Reza Vaez-Ghaemi | Added D2 Interface requirements by modifying section 6.1.3 and adding section 10 | - -2 - -3 - -# 1 2 Contents - -2 1 Revision History.....3 - -3 3 Scope.....6 - -4 4 References .....7 - -5 5 Definitions and abbreviations.....10 - -6 5.1 Definitions.....10 - -7 5.2 Abbreviations.....10 - -8 6 Open Xhaul Transport infrastructure .....12 - -9 6.1 Xhaul transport network details .....12 - -10 6.1.1 5G services and vertical markets .....12 - -11 6.1.2 Network Scale and capacity .....12 - -12 6.1.3 5G RAN Architectures.....12 - -13 6.1.4 Network DCs, MEC and NFV.....14 - -14 6.1.5 Flexible Xhaul transport infrastructure .....14 - -15 6.1.6 Xhaul multi-service capability.....16 - -16 6.2 Xhaul Functional Split .....16 - -17 6.3 High-level Xhaul Transport requirements .....17 - -18 7 Fronthaul .....18 - -19 7.1 Fronthaul details .....18 - -20 7.2 Fronthaul specific requirements.....19 - -21 8 Midhaul .....22 - -22 8.1 Midhaul details .....22 - -23 8.1.1 O-DU to O-CU communications .....23 - -24 8.1.2 Inter O-CU communications .....23 - -25 8.2 Midhaul requirements .....25 - -26 9 Backhaul.....27 - -27 9.1 Backhaul details .....27 - -28 9.2 Backhaul transport evolution in 5G.....29 - -29 9.3 Backhaul and Midhaul transport requirements .....30 - -30 10 D2 .....40 - -31 10.1 D2 details.....40 - -32 10.2 D2 Requirements .....40 - -33 11 Transport network dimensioning for Midhaul and Backhaul.....42 - -34 11.1 Transport capacity and radio density with 5G .....42 - -35 11.2 Backhaul and Midhaul transport planning.....42 - -36 11.2.1 5G NR peak bandwidth.....42 - -37 11.2.2 Site peak data rates .....43 - -38 11.2.3 Estimating cell site loads.....45 - -39 11.2.4 Transport dimensioning and provisioning for Backhaul and Midhaul .....45 - -40 11.2.5 C-RAN Backhaul dimensioning.....48 - -41 11.2.6 Midhaul dimension .....48 - -42 11.3 Backhaul and Midhaul latency.....49 - -43 12 Transport operability.....50 - -44 12.1 Operational transport requirements.....50 - -45 12.1.1 Transport equipment at antenna site .....50 - -46 12.1.2 Dual manage transport equipment at antenna site.....50 - -47 12.1.3 Supervision.....50 - -48 12.1.4 Rogue behaviour and its mitigation in access transport segment.....51 - -49 12.1.5 Transport availability.....51 - -50 12.2 Transceiver and port monitoring and identification .....52 - -51 12.2.1 Transceiver digital diagnostic monitoring.....52 - -52 12.2.2 Transceiver class of operation for bidirectional transmission.....52 - -| | | | | -|----|--------|-----------------------------------------------------------|----| -| 1 | 12.2.3 | Transceiver class of operation for WDM transmission ..... | 52 | -| 2 | 12.2.4 | Port-ID to ease field operation..... | 53 | -| 3 | 12.2.5 | Eye safety..... | 53 | -| 4 | 12.3 | Power saving and energy efficiency..... | 53 | -| 5 | 12.4 | Remote monitoring antenna site operation ..... | 54 | -| 6 | 12.5 | Operability requirements ..... | 54 | -| 7 | 13 | Synchronization ..... | 56 | -| 8 | 13.1 | Frequency, Phase and Time Accuracy Requirements ..... | 56 | -| 9 | 13.2 | Error Budget Allocation Requirements ..... | 57 | -| 10 | 13.3 | Synchronization solution requirements ..... | 59 | -| 11 | 13.4 | Summary ..... | 60 | -| 12 | 14 | Legacy Requirements..... | 62 | -| 13 | | Appendix A Fronthaul Bandwidth Calculation ..... | 64 | -| 14 | | Appendix B: Slicing in Backhaul and Midhaul..... | 66 | -| 15 | | Appendix C: Delay Asymmetry ..... | 70 | -| 16 | | | | -| 17 | | | | -| 18 | | | | - -# 3 Scope - -This document defines the requirements for an Open Xhaul transport infrastructure. As far as possible it tries to make no assumptions about the underlying transport technology, rather define a set of requirements about the overall capabilities of an Open Xhaul transport infrastructure that can support different 5G services, different radio architectures and is multi-service in nature. This document refers to 5G services, but the transport requirements also apply to O-RAN networks deploying 4G services. - -Following introductory sections 1 through 5, section 6 concentrates on a general description of Open Xhaul transport and high-level requirements. The next three sections concentrate on the transport networking requirements needed to support the different radio architectures identified in 5G, namely, Fronthaul, Midhaul and Backhaul. The aim is to provide the reader specific information about the transport infrastructure in order to support different radio splits. Section 11 provides requirement for ease of operability of transport networks. The last two main sections revolve around requirements for synchronization and legacy services. - -This document uses information published by O-RAN, 3GPP, IEEE, ITU-T, IETF, CableLabs, NGMN and several other relevant standard bodies and industry associations. It contains educational, informative, and normative content. - -What is not covered in this document: - -- As stated above, the document makes no assumption about transport technologies to be used. Technology specific architectural considerations shall be covered in other -possibly WG9- documents and will be referenced in this document as soon as published. Examples include DOCSIS, PON, WDM, Ethernet/IP based implementations, as well as, architectures that may deploy Fronthaul gateways, Fronthaul muxes or other types of CPRI/eCPRI aggregation technologies. -- The document doesn't cover the synchronization architectural options. These aspects will be covered in an upcoming WG9 Synchronization Solution document. -- Finally, this document provides no requirements on synchronization requirements at an O-RU output. They are stated in WG4 CUS Specification document [74]. - -1 - -2 - -# 4 References - -3 - -The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - -4 - -5 - -6 - -7 - -8 - -9 - -10 - -11 - -12 - -13 - -14 - -15 - -16 - -17 - -18 - -19 - -20 - -21 - -22 - -23 - -24 - -25 - -26 - -27 - -28 - -29 - -30 - -31 - -32 - -33 - -34 - -35 - -36 - -37 - -38 - -39 - -40 - -41 - -42 - -43 - -44 - -45 - -46 - -47 - -48 - -- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - - For a specific reference, subsequent revisions do not apply. - - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in Release 15. -- [1] 3GPP TS 38.472 V15.5.0: " F1 signalling transport (Release 15)". -- [2] IEEE 802.1Q-2018: "IEEE Standard for Local and metropolitan area networks—Bridges and Bridged Networks" -- [3] IETF RFC 2474: "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers" -- [4] IETF RFC 2598: "An Expedited Forwarding PHB" -- [5] IETF RFC 2597: "Assured Forwarding PHB Group" -- [6] IETF RFC 4594: "Configuration Guidelines for DiffServ Service Classes" -- [7] IETF RFC 826: "An Ethernet Address Resolution Protocol -- or -- Converting Network Protocol Addresses" -- [8] IETF RFC 792: "INTERNET CONTROL MESSAGE PROTOCOL" -- [9] IETF RFC 8200: "Internet Protocol, Version 6 (IPv6) Specification" -- [10] IETF RFC 4861: "Neighbor Discovery for IP version 6 (IPv6)" -- [11] IETF RFC 4443: "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification" -- [12] IETF RFC 6890: "Special-Purpose IP Address Registries" -- [13] IETF RFC 8190: "Updates to the Special-Purpose IP Address Registries" -- [14] IETF RFC 2131: "Dynamic Host Configuration Protocol" -- [15] IETF RFC 4361: "Node-specific Client Identifiers for Dynamic Host Configuration Protocol Version Four (DHCPv4)" -- [16] IETF RFC3315: "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)" -- [17] IETF RFC4862: "IPv6 Stateless Address Autoconfiguration" -- [18] IETF RFC768: "User Datagram Protocol" -- [19] 3GPP TS 29.060 V15.0.0: "GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface (Release 15)" -- [20] 3GPP TS 29.274 V16.1.0: "GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface (Release 15)" -- [21] 3GPP TS 36.422 version 15.1.0: "X2 signalling transport (Release 15)" -- [22] 3GPP TS 36.424 version 15.0.0: "X2 data transport (Release 15)" -- [23] 3GPP TS 38.474 V15.3.0: " F1 data transport (Release 15)". -- [24] 3GPP TS 33.117 V16.2.0: "Catalogue of general security assurance requirements (Release 16)" -- [25] IETF RFC 2119: "Key words for use in RFCs to Indicate Requirement Levels" -- [26] IEEE 802.3-2018: "IEEE Standard for Ethernet" -- [27] IETF RFC 791: "INTERNET PROTOCOL" -- [28] IETF RFC 1918: "Address Allocation for Private Internets" -- [29] IETF RFC 5357: "A Two-Way Active Measurement Protocol (TWAMP)" - -- 1 [30] IETF RFC 4656: “A One-way Active Measurement Protocol (OWAMP)” -- 2 [31] ITU-T G.8013/Y.1731(08/2015): “Operation, administration and maintenance -3 (OAM) functions and mechanisms for Ethernet-based networks” -- 4 [32] IETF RFC 4960. “Stream Control Transmission Protocol” -- 5 [33] 3GPP TS 29.281 V15.6.0: “General Packet Radio System (GPRS) Tunnelling -6 Protocol User Plane (GTPv1-U) (Release 15)” -- 7 [34] IETF RFC 1034: “DOMAIN NAMES - CONCEPTS AND FACILITIES” -- 8 [35] IETF RFC 1035: “DOMAIN NAMES - IMPLEMENTATION AND -9 SPECIFICATION” -- 10 [36] IETF RFC 4210: “Internet X.509 Public Key Infrastructure Certificate -11 Management Protocol (CMP)” -- 12 [37] IETF RFC 6083: “Datagram Transport Layer Security (DTLS) for Stream Control -13 Transmission Protocol (SCTP)” -- 14 [38] 3GPP TE 33.501 V15.6.0: “Security architecture and procedures for 5G system -15 (Release 15)” -- 16 [39] IETF RFC 4301: “Security Architecture for the Internet Protocol” -- 17 [40] 3GPP TS 33.210 V16.2.0: “Network Domain Security (NDS); IP network layer -18 security (Release 16)” -- 19 [41] 3GPP TS 33.310 V16.2.0: “Network Domain Security (NDS); Authentication -20 Framework (AF) (Release 16)” -- 21 [42] 3GPP TS 33.401 V16.0.0: “3GPP System Architecture Evolution (SAE); Security -22 architecture (Release 15)” -- 23 [43] 3GPP TR 33.821 V9.0.0: “Rationale and track of security decisions in Long Term -24 Evolved (LTE) RAN / 3GPP System Architecture Evolution (SAE) (Release 9)” -- 25 [44] IETF RFC 4303: “IP Encapsulating Security Payload (ESP)” -- 26 [45] IETF RFC 8221: “Cryptographic Algorithm Implementation Requirements and -27 Usage Guidance for Encapsulating Security Payload (ESP) and Authentication -28 Header (AH)” -- 29 [46] IETF RFC 7296: “Internet Key Exchange Protocol Version 2 (IKEv2)” -- 30 [47] ETSI GS NFV-INF 005 V1.1.1 (2014-12): Network Functions Virtualisation -31 (NFV); Infrastructure; Network Domain -- 32 [48] 3GPP TS 38.462 V15.5.0: “E1 signalling transport (Release 15)” -- 33 [49] MEF 22.3: “Transport Services for Mobile Networks, January 2018” -- 34 [50] 3GPP TS 29.303 V16.0.0: “Domain Name System Procedures; Stage 3 (Release -35 16)” -- 36 [51] eCPRI Transport Requirements V1.2, Common Public Radio Interface: -37 Requirements for the eCPRI Transport Network, June 25, 2018. -- 38 [52] IEEE 802.1CMde: Time-Sensitive Networking for Fronthaul Amendment: -39 Enhancements to Fronthaul Profiles to Synchronization, and Syntonization -40 Standards Networking for Fronthaul, —Support New Fronthaul Interface, July -41 26, 2019 -- 42 [53] IEEE 1914.1™ D3.0, Draft Fronthaul Transport Networks, November 2018. -- 43 [54] 3GPP TS 38.422 version 15.0.0 Release 15: Xn general aspects and principles -- 44 [55] GSMA:”5G Implementation Guidelines: NSA Options” -- 45 [56] NGMN: “NGMN Overview on 5G functional decomposition” -- 46 [57] ITU-T GSTR-TN5G: “Transport Network support of IMT-2020-TG” -- 47 [58] 3GPP 38.401: “NG-RAN; Architectural description” -- 48 [59] O-RAN: “WG-4 Inter-Operability Testing” -- 49 [60] O-RAN Open F1/W1/E1/X2/Xn Interfaces Working Group “Transport -50 Specification” - -- 1 [61] NGMN “5G RAN CU-DU network architecture, transport options and -2 dimensioning, version 1.0 12 April 2019)” -- 3 [62] 5G Transport Slice Connectivity Interface – draft-rokui-5g-transport-slice-00 -- 4 [63] 3GPP R3-162102 TSG-RAN Working Group 3 Meeting #93-bis CU-DU split: -5 Refinement for Annex A (Transport network and RAN internal functional -6 split) -- 7 [64] 3GPP TS 38.101: “NR, User Equipment (UE) radio transmission and reception” -- 8 [65] 3GPP TS 38.300: “NR Overall description” -- 9 [66] GSMA: “5G Implementation Guidelines v2” -- 10 [67] 3GPP TS 23.501 v6.4.0(2020-03): “System Architecture for 5G” -- 11 [68] MEF 61.1: “IP Service attributes” -- 12 [69] MEF 10.3: “Ethernet Service attributes” -- 13 [70] MEF 6.2: “EVC service definition” -- 14 [71] 3GPP TS38.306: “NR; User equipment (UE) radio access capabilities” -- 15 [72] NGMN “Guidelines for LTE Backhaul estimations” -- 16 [73] ITU-R M.2083: “IMT Vision – framework and overall objectives of the future -17 development of IMT for 2020 and beyond”. -- 18 [74] O-RAN Fronthaul Working Group, “Control, User and Synchronization Plane -19 Specification”, v03.00 (04/2020) -- 20 [75] 3GPP TS36.104, version 16.4.0, 01/2020, “Evolved Universal Terrestrial Radio -21 Access (E-UTRA) Base Station (BS) and radio transmission and reception”. -- 22 [76] 3GPP TS38.104, version 16.2.0, 01/2020, “NR Base Station (BS) and radio -23 transmission and reception”. -- 24 [77] ITU-T G.8271.1, 03/2020, “Network limits for time synchronization in packet -25 networks with full timing support from the network” -- 26 [78] ITU-T G.8272 Amendment 1, 03/2020, “Timing characteristics of primary -27 reference time clocks” -- 28 [79] ITU-T G.8272.1, Amendment 2, 08/2019, “Timing characteristics of enhanced -29 primary reference time clocks” -- 30 [80] ITU-T G.8275.1, 03/2020, “Precision time protocol telecom profile for -31 phase/time synchronization with full timing support from the network” -- 32 [81] ITU-T G.8273.2 Amendment, 03/2020, “Timing characteristics of telecom -33 boundary clocks and telecom time slave clocks” -- 34 [82] ITU-T G.8272/Y.1367, 11/2018. “Timing characteristics of primary reference -35 time clocks” -- 36 [83] 3GPP TS38.801, version 14.0.0, 03/2017, “Study on new radio access -37 technology: Radio access architecture and interfaces” -- 38 [84] NGMN “Overview on 5G RAN function decomposition” -- 39 [85] 3GPP TR22.804 v16.2.0 (2018-12), “Study on communications for automation in -40 vertical domains” -- 41 [86] O-RAN.WG5.TS.D2GAP: "D2 Interface General Aspects and Principles". -42 -43 - -1 - -# 5 Definitions and abbreviations - -## 5.1 Definitions - -The key words "**SHALL**", "**SHALL NOT**", "**SHOULD**", "**SHOULD NOT**", "**MAY**", and "**OPTIONAL**" in this document are to be interpreted as described in IETF RFC 2119 [25]. All key words must be in upper case, bold text. - -Items that are **REQUIRED** (contain the words **SHALL** or **SHALL NOT**) will be labelled as **[Rx]** for required. Items that are **RECOMMENDED** (contain the words **SHOULD** or **SHOULD NOT**) will be labelled as **[Dx]** for desirable. Items that are **OPTIONAL** (contain the words **MAY** or **OPTIONAL**) will be labelled as **[Ox]** for optional. - -Items, if supported, are not meant to be active at all times, but should be available for use. Their state (active or not active) should be based on configuration. - -## 5.2 Abbreviations - -Abbreviations defined in this document take precedence over the definition of 3GPP - -14 - -15 - -| | | | | -|------------------|-----------------------------------------|-------|-----------------------------------------------------------------| -| AF | Application Function | ITU-T | International Telecom Union-Telecom | -| AMF | Access and Mobility Management Function | LAN | Local Area Network | -| AN | Access Node | LLS | Lower Layer Split | -| ARP | Address Resolution Protocol | LTE | Long Term Evolution | -| ABW | Antenna Bandwidth | MAC | Medium Access Layer | -| BBU | Baseband Unit | MBSFN | Multimedia Broadcast multicast service Single Frequency Network | -| BH | Backhaul | MPLS | Multi-Protocol Label Switching | -| BiDi | Bidirectional | MIMO | Multiple Inputs Multiple Outputs | -| BS | Base Station | MNO | Mobile Network Operator | -| BW | Bandwidth | MRTD | Maximum Receive Time Difference | -| CAPEX | Capital Expense | NGMN | Next Generation Mobile Network | -| CBS | Committed Burst Size | NR | New Radio | -| CFP | Common Form factor Pluggable | NSA | Non-Stand Alone | -| CIR | Committed Information Rate | NSSI | Subnet Networking Slices Instance | -| CN | Core Network | OAM | Operation Administration Maintenance | -| CoMP | Coordinated Multipoint | O-CU | O-RAN Central Unit | -| CP | Control Plane | O-DU | O-RAN Distributed Unit | -| CPRI | Common Public Radio Interface | OPEX | Operation Expense | -| CU | Central Unit | O-RU | O-RAN Radio Unit | -| DC | Data Center | PCF | Policy Control Function | -| DL | Downlink | PDCP | Packet Data Convergence Protocol | -| DN | Data Network | ppb | Parts per billion | -| DHCP | Dynamic Host Configuration Protocol | PRB | Physical Resource Block | -| DSCP | Differentiated Services Codepoint | PRTC | Primary Reference Telecom Clock | -| dTE H | Dynamic Time Error High | PTP | Precision Time Protocol | -| dTE L | Dynamic Time Error Low | OFDM | Orthogonal Frequency Division Multiplexing | -| DU | Distributed Unit | QAM | Quadrature Amplitude Modulation | -| eCPRI | evolved Common Public Radio Interface | QoS | Quality of Service | -| eMBB | enhanced Mobile Broadband | QSFP | Quad SFP | -| eNB | Evolved NodeB | RB | Resource Block | -| EP | Ethernet Private | RRH | Remote Radio Head | -| EPC | Evolved Packet Core | RU | Radio Unit | -| EPL | Ethernet Private Line | SCS | Sub Carrier Spacing | -| ePRC | Enhanced Primary Reference Clock | SCTP | Stream Control Transmission Protocol | - -| | | | | -|--------|------------------------------------------|-------|------------------------------------------------| -| ePRTC | Enhanced Primary Reference Telecom Clock | SFF | Small Form Factor | -| E-UTRA | evolved UMTS Terrestrial Radio Access | SFP | Small Form factor Pluggable | -| EVP | Ethernet Virtual Private | SLA | Service Level Agreement | -| EVPL | Ethernet Virtual Private Line | TAE | Time Alignment Error | -| FDD | Frequency Division Duplex | T-BC | Telecom Boundary Clock | -| FFO | Fractional Frequency Offset | TDD | Time Division Duplex | -| FFS | For Further Study | TE | Time Error (in the context of synchronization) | -| FH | Fronthaul | T-GM | Telecom Ground Master | -| FLR | Frame Loss Ratio | TN | Transport Node | -| FR1 | Frequency Range 1 | TNE | Transport Network Equipment | -| FR2 | Frequency Range 2 | T-TSC | Telecom Time Slave Clock | -| FTTH | Fiber To The Home | TX | Transmit | -| gNB | gNodeB | UDP | User Datagram Protocol | -| GNSS | Global Navigation Satellite System | UE | User equipment | -| GPRS | General Packet Radio Service | UL | Uplink | -| GTP | GPRS Tunnelling Protocol | UNI | Universal Network Interface | -| ICMP | Internet Control Message Protocol | UNI-C | UNI-Customer edge | -| IoT | Internet of Things | UPF | User Plane Function | -| IP | Internet Protocol | URLLC | Ultra Reliable Low Latency Communication | -| IQ | In phase Quadrature | VPN | Virtual Private Network | - -1 -2 -3 - -# 6 Open Xhaul Transport infrastructure - -This section provides a definition of Open Xhaul transport, some of the key characteristics and high-level requirements associated with Open Xhaul transport. - -## 6.1 Xhaul transport network details - -At the highest-level the Open Xhaul transport network provides the connectivity from the Radio Access Network (RAN) to the mobile packet core, which subsequently makes the connection to the application function. These could reside in a public network infrastructure, such as the Internet, a walled garden or a completely private network. For details of future developments envisaged in services / spectrum and timelines please see the “International Mobile Telecommunications (IMT) 2020 and beyond” [73]. - -Below are some of the key considerations - -### 6.1.1 5G services and vertical markets - -5G networks are expected to enable a new range of services that can be categorized in three classes: - -- enhanced Mobile Broadband (eMBB) -- Ultra Reliable Low Latency Communications (URLLC) -- massive Machine Type Communications (mMTC) - -These services will drive the need for new or enhanced classes of RAN and transport networks. - -### 6.1.2 Network Scale and capacity - -Whereas eMBB services demand more capacity in transport networks, URLLC applications will pose new challenges for the design of Xhaul networks in terms of low latency and increased reliability. Finally, mMTC necessitate a network that can efficiently manage huge number of devices such as intelligent devices in utility meters or house appliances. - -### 6.1.3 5G RAN Architectures - -As illustrated in Figure 1, in a traditional D-RAN (distributed RAN) architecture, the O-DU and O-CU are integrated as a BBU, collocated with the O-RU (Radio) at cell site. When evolving to the C-RAN (centralized RAN) architecture, the O-CU, which contains the higher layer of the RAN processing stacks, is centralized in a Hub. Depending on Operator’s deployment needs, the O-DU may remain at cell site, or be centralized. The Xhaul transport (Fronthaul, D2, Midhaul, and Backhaul) serve as connections among the 3GPP RAN and core components. Transport Network Equipment (TNE) represents the transport functions necessary in Xhaul networks. Specifics of TNE are outside of the scope of this document and will be covered in WG9 solution documents: - -D-RAN: - -(O-RU+O-DU+O-CU) ← Backhaul → (5GC) - -C-RAN: - -(O-RU) ← Fronthaul → (O-DU+O-CU) ← Backhaul → (5GC) - -(O-RU) ← Fronthaul → (O-DU) ← Midhaul → (O-CU) ← Backhaul → (5GC) - -(O-RU+O-DU) ← Midhaul → (O-CU) ← Backhaul → (5GC) - -(O-RU +O-DU) ← D2 → (O-DU +O-RU) - -O-DU ← D2 → O-DU - -The X2/Xn interfaces that provide logical connection between O-CUs (or to LTE eNBs) are also depicted in Figure 1 to support the inter site coordination such as EN-DC. - -Similar to F1 and X2/Xn, the D2 interfaces that provide logical connection between O-DUs are also depicted in Figure 2: RAN reference architecture with D2 to support the inter DU connection. This interface can be used to provide different features such as inter O-DU carrier aggregation between cells configured in different O-DUs. - -![Figure 1: RAN reference architecture. The diagram illustrates four RAN scenarios: Centralized RAN Scenario 1, Centralized RAN Scenario 2, Centralized RAN Scenario 3, and Distributed RAN. Each scenario shows the connection between O-RUs, O-DUs, O-CUs, and TNEs, leading to a 5GC cloud via Backhaul N2,N3 interfaces. Scenario 1 shows two O-RUs connected to a CRAN-HUB containing an O-DU and O-CU. Scenario 2 shows an O-RU connected to an O-DU, which is then connected to an O-CU via Midhaul F1. Scenario 3 shows an O-RU connected to an O-DU, which is connected to a TNE, which is then connected to an O-CU via Midhaul F1. The Distributed RAN scenario shows an O-RU connected to an O-DU, which is connected to an O-CU, which is then connected to a TNE. All scenarios connect to a 5GC cloud via Backhaul N2,N3 interfaces. X2 and Xn interfaces are also shown between the CRAN-HUB and the 5GC cloud.](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg) - -Figure 1: RAN reference architecture. The diagram illustrates four RAN scenarios: Centralized RAN Scenario 1, Centralized RAN Scenario 2, Centralized RAN Scenario 3, and Distributed RAN. Each scenario shows the connection between O-RUs, O-DUs, O-CUs, and TNEs, leading to a 5GC cloud via Backhaul N2,N3 interfaces. Scenario 1 shows two O-RUs connected to a CRAN-HUB containing an O-DU and O-CU. Scenario 2 shows an O-RU connected to an O-DU, which is then connected to an O-CU via Midhaul F1. Scenario 3 shows an O-RU connected to an O-DU, which is connected to a TNE, which is then connected to an O-CU via Midhaul F1. The Distributed RAN scenario shows an O-RU connected to an O-DU, which is connected to an O-CU, which is then connected to a TNE. All scenarios connect to a 5GC cloud via Backhaul N2,N3 interfaces. X2 and Xn interfaces are also shown between the CRAN-HUB and the 5GC cloud. - -**Figure 1: RAN reference architecture** - -![Figure 2: RAN reference architecture with D2. The diagram shows two centralized RAN scenarios. In Scenario 1, two O-RUs are connected via Fronthaul to a CRAN-HUB containing O-DUs and TNEs. In Scenario 2, two O-RUs are connected via Fronthaul to a central unit containing O-DUs and TNEs. Both scenarios use D2 transport and Midhaul F1 to connect to a central unit (O-CU and TNEs), which then connects via Backhaul N2,N3 to a 5GC cloud through another TNE.](4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg) - -Figure 2: RAN reference architecture with D2. The diagram shows two centralized RAN scenarios. In Scenario 1, two O-RUs are connected via Fronthaul to a CRAN-HUB containing O-DUs and TNEs. In Scenario 2, two O-RUs are connected via Fronthaul to a central unit containing O-DUs and TNEs. Both scenarios use D2 transport and Midhaul F1 to connect to a central unit (O-CU and TNEs), which then connects via Backhaul N2,N3 to a 5GC cloud through another TNE. - -Figure 2: RAN reference architecture with D2 - -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15 -16 -17 -18 - -### 6.1.4 Network DCs, MEC and NFV - -Beyond the abovementioned evolution of wireless access networks with D-RAN and C-RAN, wireless operators started to take advantage of Network Function Virtualization NFV technologies to scale and control the CAPEX. Introduction of 5G creates new opportunities to use these technologies to scale functions and manage low latency in radio access networks. - -### 6.1.5 Flexible Xhaul transport infrastructure - -As outlined 5G defines different services and RAN architectures. Figure 3 is adapted from NGMN [56] and illustrates how different RAN components may be placed in different locations within the same Mobile Network Operator's (MNO) infrastructure to meet the delay and reliability requirements of a 5G service or vertical market. - -![Diagram showing CU, DU, UPF, and MEC placement for ultra-low latency (approx. max 1ms RTT)*. The diagram illustrates a network architecture where multiple RUs (Radio Units) are connected to a central DU (Distributed Unit). The DU is connected to a CU (Central Unit), which is connected to a UPF (User Plane Function) and a MEC (Multi-access Edge Computing) unit. The network is divided into three tiers: Tier 1 Site, Tier 2 Site, and Tier 3 Site. The Tier 1 Site contains the DU, UPF, and MEC. The Tier 2 Site contains the CU. The Tier 3 Site contains the UPF and MEC. The network is connected to external networks. The text 'CU, DU, UPF MEC placement for ultra-low latency (approx. max 1ms RTT)*' is highlighted in red.](724c7777b608e53be38b12b6fb3c43bc_img.jpg) - -Diagram showing CU, DU, UPF, and MEC placement for ultra-low latency (approx. max 1ms RTT)\*. The diagram illustrates a network architecture where multiple RUs (Radio Units) are connected to a central DU (Distributed Unit). The DU is connected to a CU (Central Unit), which is connected to a UPF (User Plane Function) and a MEC (Multi-access Edge Computing) unit. The network is divided into three tiers: Tier 1 Site, Tier 2 Site, and Tier 3 Site. The Tier 1 Site contains the DU, UPF, and MEC. The Tier 2 Site contains the CU. The Tier 3 Site contains the UPF and MEC. The network is connected to external networks. The text 'CU, DU, UPF MEC placement for ultra-low latency (approx. max 1ms RTT)\*' is highlighted in red. - -![Diagram showing CU, DU, UPF, and MEC placement for very low latency (approx. max 5ms RTT)*. This diagram is similar to the first one but with a different functional split. The RUs are connected to a DU, which is connected to a CU. The CU is connected to a UPF and a MEC unit. The network is divided into three tiers: Tier 1 Site, Tier 2 Site, and Tier 3 Site. The Tier 1 Site contains the DU. The Tier 2 Site contains the CU and UPF. The Tier 3 Site contains the MEC. The network is connected to external networks. The text 'CU, DU, UPF, MEC placement for very low latency (approx. max 5ms RTT)*' is highlighted in red.](7efae06af3af43ffe5d4b956a679cf54_img.jpg) - -Diagram showing CU, DU, UPF, and MEC placement for very low latency (approx. max 5ms RTT)\*. This diagram is similar to the first one but with a different functional split. The RUs are connected to a DU, which is connected to a CU. The CU is connected to a UPF and a MEC unit. The network is divided into three tiers: Tier 1 Site, Tier 2 Site, and Tier 3 Site. The Tier 1 Site contains the DU. The Tier 2 Site contains the CU and UPF. The Tier 3 Site contains the MEC. The network is connected to external networks. The text 'CU, DU, UPF, MEC placement for very low latency (approx. max 5ms RTT)\*' is highlighted in red. - -![Diagram showing CU, DU, and UPF placement for low latency (approx. max 10ms RTT)*. This diagram shows another functional split. The RUs are connected to a DU, which is connected to a CU. The CU is connected to a UPF. The network is divided into three tiers: Tier 1 Site, Tier 2 Site, and Tier 3 Site. The Tier 1 Site contains the DU. The Tier 2 Site contains the CU and UPF. The Tier 3 Site contains the UPF. The network is connected to external networks. The text 'CU DU UPF placement for low latency (approx. max 10ms RTT)*' is highlighted in red.](75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg) - -Diagram showing CU, DU, and UPF placement for low latency (approx. max 10ms RTT)\*. This diagram shows another functional split. The RUs are connected to a DU, which is connected to a CU. The CU is connected to a UPF. The network is divided into three tiers: Tier 1 Site, Tier 2 Site, and Tier 3 Site. The Tier 1 Site contains the DU. The Tier 2 Site contains the CU and UPF. The Tier 3 Site contains the UPF. The network is connected to external networks. The text 'CU DU UPF placement for low latency (approx. max 10ms RTT)\*' is highlighted in red. - -**Figure 3: End to end Xhaul transport – adapted from text and diagrams in “NGMN: Overview on 5G RAN Function Decomposition” [84]** - -These different RAN deployment models impact on where the Fronthaul, Midhaul and Backhaul overlay the Xhaul transport infrastructure or even if they are all required. Beyond these deployment models, the choice of radio technology/spectrum can impact the architectural split. Low-/mid-/high - -band radios may require different choice of functional split or Fronthaul (CPRI/eCPRI) technology. The number of antenna ports/layers (spatial multiplexing) is another factor to be considered. - -Ideally the Xhaul transport infrastructure and its design need to be flexible enough to accommodate Backhaul, Midhaul and Fronthaul and even the N6 portions of the 5G infrastructure running in the same part of the physical infrastructure. There will be exceptions to this requirement, for example some MNOs may wish to treat the transport infrastructure supporting the Fronthaul in isolation to the Midhaul and Backhaul but given the similarities and potential overlap between Backhaul/Midhaul/N6 (GiLAN) the Xhaul transport infrastructure must be able to accommodate all these capabilities running in the same portion of the physical transport infrastructure. - -### 6.1.6 Xhaul multi-service capability - -NGMN identifies the need for X-haul transport to be multi-service capable. Depending on the type of service provider the following capabilities MAY need to be supported on the X-haul transport infrastructure: - -- Non-stand Alone (NSA) and Stand-Alone deployment of 5G wireless services including eMBB, mMTC and URLLC defined by 3GPP -- Mobile vertical market solutions -- Legacy 2G/3G/4G wireless services -- Enterprise services -- Residential broadband services -- Data center interconnection - -This paper focuses on mobile deployment cases as listed in the first three bullets above. - -## 6.2 Xhaul Functional Split - -The introduction of 5G services necessitates a new look at the distribution of functions between 4G BBU and RRH (Figure 4). 4G BBU hosts the majority of functional elements with the exception of RF functions. Also known as option 8, CPRI technology provides a simple synchronous interface that allows for a low-cost design of the RRH. It also permits the introduction of advanced mobility functions such as carrier aggregation and CoMP. This simplicity comes at a cost; the CPRI interface transports time domain IQ data whose bandwidth is proportional to the bandwidth of the baseband signal and the number of antennas or more generally the number of spatial streams. Higher bandwidth and massive MIMO requirements of 5G cause an explosive growth of this interface option. - -A review of the functional split options (Figure 4) led to several new options (Options 1 through 7) that can be theoretically considered for solving the challenges raised by emerging 5G services. These options were ultimately narrowed down to three prominent options 2, 6 and 7. - -![Figure 4: Functional Split Options [83]. The diagram shows two horizontal chains of network functions representing uplink (top) and downlink (bottom) data flows. The functions are RRC, PDCP, High-RLC, Low-RLC, High-MAC, Low-MAC, High-PHY, Low-PHY, and RF. Red vertical lines with arrows indicate functional split options between adjacent functions. Option 1 is between RRC and PDCP. Option 2 is between PDCP and High-RLC. Option 3 is between High-RLC and Low-RLC. Option 4 is between Low-RLC and High-MAC. Option 5 is between High-MAC and Low-MAC. Option 6 is between Low-MAC and High-PHY. Option 7 is between High-PHY and Low-PHY. Option 8 is between Low-PHY and RF. In the uplink, data flows from left to right, with splits occurring after each function. In the downlink, data flows from right to left, with splits occurring before each function.](2cde062fd82833415971a8bd1a2cafab_img.jpg) - -Figure 4: Functional Split Options [83]. The diagram shows two horizontal chains of network functions representing uplink (top) and downlink (bottom) data flows. The functions are RRC, PDCP, High-RLC, Low-RLC, High-MAC, Low-MAC, High-PHY, Low-PHY, and RF. Red vertical lines with arrows indicate functional split options between adjacent functions. Option 1 is between RRC and PDCP. Option 2 is between PDCP and High-RLC. Option 3 is between High-RLC and Low-RLC. Option 4 is between Low-RLC and High-MAC. Option 5 is between High-MAC and Low-MAC. Option 6 is between Low-MAC and High-PHY. Option 7 is between High-PHY and Low-PHY. Option 8 is between Low-PHY and RF. In the uplink, data flows from left to right, with splits occurring after each function. In the downlink, data flows from right to left, with splits occurring before each function. - -Figure 4: Functional Split Options [83] - -Furthermore, the option 7 also presents different choices in terms of splitting the functions of the PHY layer such as options 7-1, 7-2x, and 7-3 for the Fronthaul interface. This document only focuses on option 7-2x (Figure 5) as the interface for open Fronthaul chosen by O-RAN. However, the document also considers the option 8 for the definition of Fronthaul transport requirement as this interface is widely used in 4G networks and will be presented in future networks not only for 4G services, but also as an option for carrying low bandwidth 5G services. - -## 6.3 High-level Xhaul Transport requirements - -**[R1]: MUST** support the mandatory transport capabilities outlined by WG5 in the “O-RAN Open F1/W1/E1/X2/Xn Interfaces working group transport specification”. [60] - -**[R2]: MUST** support the mandatory transport capabilities outlined by WG4 Open Fronthaul Interfaces Workgroup [74]. - -**[R3]:** Mobile components reside in the WAN and the DC. It **MUST** be possible to build L2 and L3 services where mobile components reside in both domains - -**[R4]: MAY** need to be multiservice in nature. Refer to 6.1.6 for examples of the type of services that may need to be supported on the Xhaul transport network - -**[R5]: SHOULD** support flexible placement of front / mid / Backhaul / N6 on Xhaul transport. - -**[R6]: MUST** support flexible placement of Mid/Backhaul / N6 on Xhaul transport. - -**[R7]: MUST** support L2 and L3 Virtual Private Networks (VPNs). - -**[R8]: MUST** support multi-point VPNs. - -**[R9]: MUST** support point to point VPNs. - -**[R10]: MUST** support 5G network slicing. - -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15 -16 -17 -18 -19 -20 -21 -22 -23 -24 -25 - -# 7 Fronthaul - -Fronthaul in O-RAN is defined as the connectivity in the RAN infrastructure between the Distributed Unit (O-DU) and Radio Unit (O-RU). - -## 7.1 Fronthaul details - -As explained in section 6.2, the herein presented Fronthaul requirements focus on split options 7-2x, as shown in Figure 5 [74]. Option 8 will be addressed in chapter 14. - -![Functional split diagram showing O-DU and O-RU processing blocks separated by O-RAN FH. It includes two O-RU categories: Category A (Non-precoding) and Category B (Precoding).](77464a47f104d0d647b2414591137b64_img.jpg) - -The diagram illustrates the functional split 7-2x between the O-DU and O-RU. The O-DU (top) contains the following processing blocks: Scrambling, Modulation, Layer Mapping, Precoding (bypass mode possible), RE Mapping, and IQ Compression (dotted box). The O-RU (bottom) contains: IQ Decompression (dotted box), Precoding (dotted box), Digital Beamforming (dotted box), iFFT and CP addition, Digital to Analog, and Analog Beamforming (dotted box). A central box explains that dotted blocks are optional. Two categories are shown: O-RU Category A (Non-precoding) and O-RU Category B (Precoding). - -| Feature | O-RU Category A | O-RU Category B | -|------------------------|----------------------------------------------------------------------|--------------------------------------------------------------| -| Unit Type | Non-precoding O-RAN Radio Unit. Precoding in radio is not supported. | Precoding O-RAN Radio Unit. Precoding in radio is supported. | -| Modulation Compression | | Allows support for modulation compression. | -| Beamforming | Digital and Analog beamforming optional | Digital and Analog beamforming optional | - -Functional split diagram showing O-DU and O-RU processing blocks separated by O-RAN FH. It includes two O-RU categories: Category A (Non-precoding) and Category B (Precoding). - -**Figure 5: O-RAN WG4 functional split 7-2x (Figure 2-2 in [74])** - -The use cases revolve around 4G/5G mobility services and URLLC. The presented requirements take advantage of documents already available by other standard bodies such CPRI (eCPRI Transport Requirements; [51]), IEEE 802.1CMde [52], and IEEE 1914.1 [53]. - -## 7.2 Fronthaul specific requirements - -| Category | Comments | -|----------------------------------------|----------------------------------------------------| -| Interfaces | O-RAN 7.2x, 1914.3, eCPRI, CPRI, | -| Protocols | O-RAN 7.2x: Ethernet VLAN based or IP/UDP | -| Logical connectivity requirements | | -| Bandwidth per O-RU and O-DU | Listed in this chapter below | -| Transport delay (one way) O-RU to O-DU | Listed in this chapter below | -| Transport delay asymmetry | Appendix C (For Further Study) | -| Synchronization / timing requirements | Listed in synchronization chapter of this document | - -**Table 1: High level Fronthaul requirements** - -The primary reference for Frame Loss Ratio and Latency proposed in this document is the eCPRI Transport Requirement V1.2 [51]. IEEE 802.1CMde [52] also refers to the eCPRI Transport Requirements V1.2 for latency and frame loss ratio, and therefore is not referenced for the purpose of latency and frame loss ratio requirements in this document. Further information on delay parameters can be found in WG4 CUS specification, Annex B [74]. - -IEEE 1914.1 [53] uses a different terminology for the identification of Fronthaul (NGFI-I) and Midhaul (NGFI-II). It does not include any requirements on frame loss ratio. However, it provides a table for latency requirements that distinguishes the requirements by different use cases. While there is some overlap with the limits provided in eCPRI Transport Requirements document, there are also some differences. To avoid any confusion, we are not presenting the IEEE 1914.1 requirements in this document and are proposing that it only refers to eCPRI Transport Requirement V1.2 document for latency. - -The Frame Loss Ratio and Latency requirements are summarized in Table 2 and Table 3, respectively. - -| CoS Name | Example use | Maxim One-way
Frame Loss Ratio
Performance | -|----------|----------------------------------------|--------------------------------------------------| -| High | User Plane (fast) | $10^{-7}$ | -| Medium | User Plane (slow),
C&M Plane (fast) | $10^{-7}$ | -| Low | C&M Plane | $10^{-6}$ | - -**Table 2: Frame loss ratio requirements** - -| Latency Class | Max. One-way
Frame Delay
Performance | Use case | -|---------------------|--------------------------------------------|--------------------------------------------------------------| -| High25 | 25 $\mu\text{s}$ | Ultra-low latency performance | -| High75 1 | 75 $\mu\text{s}$ | For full NR performance with fiber lengths in 10km range | -| High100 | 100 $\mu\text{s}$ | For standard NR performance with fiber lengths in 10km range | - -| | | | -|---------|--------------------------------------|----------------------------------------------------| -| High200 | 200 $\mu$ s | For installations with fiber lengths in 30km range | -| High500 | 500 $\mu$ s | Large latency installations > 30 km | -| Medium | User Plane (slow) & C&M Plane (fast) | 1 ms | -| Low | C&M Plane | 100 ms | - -1. New requirement category added based on deployment needs. - -**Table 3: One-way Delay requirements** - -Fronthaul bandwidth is dimensioned per cell site, where a number of carriers are deployed at different frequency bands (Low/mid bands in Sub 6 and mm wave in high band), and at different sectors. The Fronthaul bandwidth for a cell site depends on following key parameters - -- Number of sectors -- Radio channel bandwidth of each carrier -- MIMO order of each carrier - -Various sizes of site configuration may be considered for the eCPRI Fronthaul traffic: - -- Small: single sector, carriers in either mmWave or Sub 6 with low MIMO order -- Medium: multiple sectors, carriers in both Sub 6 and mmWave with medium MIMO order -- Large: multiple sectors, carriers in both mmWave and Sub 6 band with Massive MIMO - -Table 4 provides "typical" peak Fronthaul bandwidth "cases" in such site configurations: - -| | Number of sectors | Sub6 | | | | mmWave | | | | Total FH BW (Gbps) | -|--------|-------------------|------------------------------|-------------|------------------------|---------------------------|-----------------|-------------|-----------|--------------|--------------------| -| | | Total CBW 1 (MHz) | MIMO layers | ABW 2 (MHz) | FH BW 3 (Gbps) | Total CBW (MHz) | MIMO layers | ABW (MHz) | FH BW (Gbps) | | -| Small | 1 | | | | 0 | 400 | 2 | 800 | 15 | 15 | -| Medium | 3 | 100 | 4 | 1200 | 23 | 400 | 4 | 4800 | 87 | 110 | -| Large | 3 | 100 | 16 | 4800 | 90 | 800 | 4 | 9600 | 175 | 265 | - -1. CBW: Aggregated Channel Bandwidth of all carriers in a sector - -2. ABW: Antenna Bandwidth = number of sectors X number MIMO layers X CBW - -3. FH BW: Fronthaul Bandwidth for functional split 7-2x (transport protocol overhead not included) - -**Table 4: Fronthaul Bandwidth Reference for eCPRI traffic** - -The FH BW in Table 4 is calculated for functional split 7-2x and block floating point compression specified in O-RAN WG 4 CUS plane specification [74]. The formula used for the calculation is given as follows: - -$$FH\ BW = 2 \times 10^{-9} (1 + c) \frac{v_{layer} N_{PRB} (12 N_{mantissa} + N_{exponent})}{T_s^\mu} \text{ (Gbps)}$$ - -Where - -- $v_{layer}$ is the maximum number of supported layers - -- $N_{PRB}$ is the maximum RB allocation for a given channel bandwidth and numerology $\mu$ . -- $N_{mantissa}$ is the number of mantissa bits. $N_{mantissa} = 9$ used in Table 4. -- $N_{exponent}$ is the number of the exponent bits. $N_{exponent} = 4$ used in Table 4. -- $T_s^\mu$ is the average OFDM symbol duration in a subframe for a given numerology, i.e., -$$T_s^\mu = \frac{10^{-3}}{14 \times 2^\mu} \text{ (second)}$$ -- $c$ is the overhead from the control-plane. For downlink, $c \approx 10\%$ and for uplink $c \approx 0$ , as the control-plane is primarily the downlink traffic in O-RAN specification[74]. The overhead may also take different value depending on vender specific implementation. - -The relation of $N_{PRB}$ to the channel bandwidth and numerology is defined in 3GPP specification [64] that applies to both FDD and TDD. There is no need for any additional scaling by downlink/uplink ratio for TDD because full $N_{PRB}$ is always made available at the time of transmission in one direction (downlink or uplink). - -The Fronthaul bandwidth calculation equation does not include the protocol encapsulation overhead (e.g., eCPRI header, Ethernet header, and IP header, etc.). At an assumption of average packet size equal to 1000, an additional 3.6% overhead needs be added for L2 Ethernet Encapsulation, and 6.4% for L3 IPv4 Encapsulation. - -Note that the Fronthaul traffic from the 7-2x Lower Layer Split is user data dependent. The actual real time Fronthaul bandwidth is expected lower than its peak depending on traffic payload in the deployment. Hence certain level of over subscription to transport network with Fronthaul statistical multiplexing is allowed at operator's decision on the cell site dimensioning, user traffic profiling, and reliability requirement. More accurate calculation of such use of the Fronthaul transport is complex and is for further study. - -Examples of the site carrier configuration related to the Fronthaul bandwidth calculation are provided in Appendix A, together with some possible eCPRI or CPRI interface configurations associated with the carriers. - -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15 -16 -17 -18 -19 -20 -21 -22 -23 -24 -25 -26 -27 -28 -29 -30 -31 - -# 8 Midhaul - -There are many similarities between Midhaul and Backhaul components of a 5G RAN infrastructure and the transport infrastructure needed to support it. In order to avoid duplication this document has dedicated chapters covering Midhaul and Backhaul. These contain descriptions of the component and a requirements table. For requirements that are common for both Midhaul and Backhaul they are held in the Backhaul requirements section (see 9.3). There is also a common chapter (chapter 0) dedicated to dimensioning the transport network. - -## 8.1 Midhaul details - -The Midhaul network is a logical portion of the transport network that supports C-RAN architectures where there is a “High level Split” (HLS) or split 2 in the 5G Radio architecture which implies the O-DU and O-CU are split into independent components. It facilitates: - -- 1) O-DU and O-CUs communication and supports the transport of the 3GPP F1/W1/E1 interfaces. In scenarios where the O-DU and O-CU are a combined entity then these interfaces are not exposed, and the transport network does not have a Midhaul component. -- 2) Inter O-CU communication and supports the transport of the 3GPP Xn interface. In scenarios where the MNO has not implemented a split O-DU and O-CU RAN architecture then these interfaces need to be supported in the Backhaul network. - -Figure 6 illustrates RAN architectures where a Midhaul or HLS is present. - -![Figure 6: RAN architectures where a Midhaul transport is required. The diagram shows two network topologies. The top topology shows an O-RU connected to an O-DU via a 7.2x interface, which is then connected to an O-CU via an F1 interface, and finally to a UPF via an N3/9 interface. The O-DU and O-CU are connected to a Transport Network Element (TNE) via a Midhaul Transport (orange line). The O-RU is connected to a TNE via a Fronthaul Transport (red line). The O-CU is connected to a TNE via a Backhaul Transport (blue line). The bottom topology shows an O-RU connected directly to an O-CU via an F1 interface, which is then connected to a UPF via an N3/9 interface. The O-RU and O-CU are connected to a TNE via a Midhaul Transport (orange line). The O-CU is connected to a TNE via a Backhaul Transport (blue line).](627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg) - -Figure 6: RAN architectures where a Midhaul transport is required. The diagram shows two network topologies. The top topology shows an O-RU connected to an O-DU via a 7.2x interface, which is then connected to an O-CU via an F1 interface, and finally to a UPF via an N3/9 interface. The O-DU and O-CU are connected to a Transport Network Element (TNE) via a Midhaul Transport (orange line). The O-RU is connected to a TNE via a Fronthaul Transport (red line). The O-CU is connected to a TNE via a Backhaul Transport (blue line). The bottom topology shows an O-RU connected directly to an O-CU via an F1 interface, which is then connected to a UPF via an N3/9 interface. The O-RU and O-CU are connected to a TNE via a Midhaul Transport (orange line). The O-CU is connected to a TNE via a Backhaul Transport (blue line). - -**Figure 6: RAN architectures where a Midhaul transport is required** -**Source: Cisco** - -From an interface and protocol perspective 3GPP and O-RAN WG5 are defining these specifications. - -Note: WG5 will shortly publish O-RAN Transport Specifications 1.0 on the transport requirements for Midhaul . The requirements should be used in conjunction with this document. - -###### 1 8.1.1 O-DU to O-CU communications - -2 3GPP TS 38.401.[58] defines the de-aggregated RAN, it's characteristics and outlines the F1-U, F1- - 3 C and E1 interfaces. Figure 7, taken from 3GPP TS 38.401 illustrates the components and interfaces. - 4 The Midhaul transport infrastructure is responsible for supporting these interfaces. - 5 - 6 - -![Diagram of a de-aggregated gNB architecture. A dashed box labeled 'gNB' contains three main components: 'gNB-CU-CP', 'gNB-CU-UP' (represented by three stacked boxes), and two 'gNB-DU' boxes. The 'gNB-CU-CP' is connected to the 'gNB-CU-UP' via an 'E1' interface. Each 'gNB-DU' is connected to the 'gNB-CU-CP' via an 'F1-C' interface and to the 'gNB-CU-UP' via an 'F1-U' interface. All connections are shown as solid lines.](844077b3034f0030b404207db0ad76b4_img.jpg) - -Diagram of a de-aggregated gNB architecture. A dashed box labeled 'gNB' contains three main components: 'gNB-CU-CP', 'gNB-CU-UP' (represented by three stacked boxes), and two 'gNB-DU' boxes. The 'gNB-CU-CP' is connected to the 'gNB-CU-UP' via an 'E1' interface. Each 'gNB-DU' is connected to the 'gNB-CU-CP' via an 'F1-C' interface and to the 'gNB-CU-UP' via an 'F1-U' interface. All connections are shown as solid lines. - -7 -8 **Figure 7: De-aggregated gNB [58]** -9 - -10 The characteristics of a disaggregated gNB are: - -- 11 • A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs and multiple gNB-DUs -- 12 • DUs and CU-UPs are connected to one CU-CP via the E1 interface -- 13 • DUs can connect to multiple CU-UPs -- 14 • Multiple CU-UPs connect to one CU-CP -- 15 • For resiliency reasons DUs and CU-UPs may connect to multiple CU-CPs - -16 -17 The 3GPP interfaces associated with O-DU and O-CU communication are: - -- 18 • **F1 interface** defines the inter-connection of a gNB-CU and a gNB-DU and has a control - 19 (F1-C) and user (F1-U) plane component. -- 20 - 21 • **E1 interface** defines the control plane inter-connection between the gNB-CU-CP and a gNB- - 22 CU-UP. It allows these two components to run as separate entities and potentially in different - 23 locations. - -###### 24 25 26 8.1.2 Inter O-CU communications - -27 Xn is a 5G interface between the gNBs in 5G and X2 is the interface between eNBs in 4G. Figure 8 - 28 illustrates Xn interface in a D-RAN architecture. - 29 - 30 - -![Figure 8: Overall Architecture showing Xn interface. The diagram shows two AMF/UPF units at the top, each connected to two gNB units and two ng-eNB units via NG interfaces. The gNB units are interconnected by Xn interfaces, and the ng-eNB units are also interconnected by Xn interfaces. The AMF/UPF units are grouped as 5GC, and the gNB and ng-eNB units are grouped as NG-RAN.](366a77fdefb0097b3289b4a011911390_img.jpg) - -Figure 8: Overall Architecture showing Xn interface. The diagram shows two AMF/UPF units at the top, each connected to two gNB units and two ng-eNB units via NG interfaces. The gNB units are interconnected by Xn interfaces, and the ng-eNB units are also interconnected by Xn interfaces. The AMF/UPF units are grouped as 5GC, and the gNB and ng-eNB units are grouped as NG-RAN. - -Figure 8: Overall Architecture showing Xn interface [65] - -In scenarios where a “high level split” radio architecture has been adopted these interfaces run between the O-CUs and are considered to be part of the Midhaul transport architecture by O-RAN WG5. In D-RAN and RAN architectures that do not employ an HLS, then these interfaces will typically be considered part of the Backhaul network. - -The Xn and X2 interfaces are used to exchange signalling information between RAN nodes, and the forwarding of PDUs between RAN nodes during UE handover. The X2 interface also has an important role in the migration from 4G to 5G as it is used in some Non-Standalone Architectures (NSAs) migration solutions to convey signalling information, and in some cases user data from the 5G New Radios to the 4G Evolved Packet Core. - -![Figure 9: NSA Option 3/3a/3x networking mode. The figure consists of three sub-diagrams. Each sub-diagram shows a User plane (solid line) and a Control plane (dotted line) for a 5G UE (NR) connected to an LTE eNB, which is then connected to an EPC. The first sub-diagram (far left) shows the User plane going from the NR to the eNB and then to the EPC, while the Control plane goes from the NR to the eNB and then to the EPC. The second sub-diagram shows the User plane going from the NR to the EPC, while the Control plane goes from the NR to the eNB and then to the EPC. The third sub-diagram shows the User plane going from the NR to the eNB and then to the EPC, while the Control plane goes from the NR to the EPC.](171115f072e42b379238ed0dd438e9d7_img.jpg) - -Figure 9: NSA Option 3/3a/3x networking mode. The figure consists of three sub-diagrams. Each sub-diagram shows a User plane (solid line) and a Control plane (dotted line) for a 5G UE (NR) connected to an LTE eNB, which is then connected to an EPC. The first sub-diagram (far left) shows the User plane going from the NR to the eNB and then to the EPC, while the Control plane goes from the NR to the eNB and then to the EPC. The second sub-diagram shows the User plane going from the NR to the EPC, while the Control plane goes from the NR to the eNB and then to the EPC. The third sub-diagram shows the User plane going from the NR to the eNB and then to the EPC, while the Control plane goes from the NR to the EPC. - -Figure 9: NSA Option 3/3a/3x networking mode [66] - Source: GSMA 5G Implementation Guidelines v2: NSA Option 3 - -Figure 9 shows the NSA option 3/3a/3x networking modes. In NSA option 3 (far left in figure) the signalling and user plane traffic associated with 5G UEs is sent from gNBs to eNBs and then onto the mobile core. In this mode, traffic levels between the gNB and the eNB and between the eNB and the EPC are a function of the amount of 5G spectrum and the number of 5G UEs. It is anticipated traffic levels will initially be low due to the scarcity of 5G UEs but could become very significant as the user population transitions towards 5G UEs and gets the benefits of increased capacity from using 5G NR. This mode impacts the transport infrastructure between the gNB and the eNB and also the transport infrastructure between the eNB and the EPC. - -In NSA option 3a (middle of Figure 9) only signalling traffic traverses the X2 interface. - -NSA option 3x (far right in Figure 9) is roughly the opposite to NSA option 3. In this case signalling and user plane traffic from 4G UEs goes from eNBs via gNBs to the mobile core. In this NSA mode, the impact on the transport network is dependent on the level of 4G spectrum and the number of 4G UEs. The likely impact on the transport network is that traffic levels will be significant on the X2 interface initially, but as 4G users migrate to 5G so user plane traffic will decrease. - -X2 and Xn are logically a point to point connection between gNBs or eNBs. However, there are Xn and X2 interfaces to all adjacent eNBs / gNBs so in reality there is a multi-point relationship between entities. - -The O-CU-O-CU interfaces are: - -- **X2 interface** is the LTE interface between RAN nodes. The interface is further split into a user plane and control plane components (X2-U user plane and the X2-C). -- **Xn interface** is the 5G interface between RAN nodes. The interface is further split into a user plane and control plane components (Xn-U user plane and the Xn-C). - -## 8.2 Midhaul requirements - -There are many similarities between Midhaul and Backhaul transport requirements. The following table highlights the items specific to Midhaul. For requirements that are consistent between Midhaul and Backhaul please refer to Table 6 in the Backhaul section. - -| Capability | Requirements | Notes | -|-------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------| -| 3GPP interfaces | Control Plane: F1-C, E1
User Plane: F1-U
Control Plane: Xn-C
User Plane: Xn-U | | -| Network and transport protocols | All 3GPP interfaces are IP
Control plane interfaces: IP/SCTP
User plane interfaces: IP/UDP/GTPv2 | | -| Logical connectivity requirements | Multi-point at IP layer | | -| Transport network scale for Midhaul |

The size of the Midhaul infrastructure is highly dependent on how the C-RAN architecture is deployed.

In scenarios where an operator is running a Fronthaul infrastructure then the Midhaul will be between O-DU sites and the O-CU sites (1st topology shown in figure xx). In both cases there could be aggregation.

  1. 1) Multiple O-RUs consolidating onto a smaller number of O-DU sites.
  2. 2) Multiple O-DUs consolidating onto a smaller number of O-CU sites.
| | - -| | | | -|----------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------| -| | In scenarios where the O-RU and the O-DU are co-located in the cell site (2 nd topology shown in Figure 6) then the Midhaul will consist of every cell site plus sites where an O-CU component resides. | | -| Midhaul transport provisioning | F1 and E1 interfaces dimensioning is covered in chapter 10.
Xn and X2 interfaces are between gNBs and eNBs and traffic levels are highly dependent on the migration path being used by the MNO to move between 4G and 5G technology. | | -| End to end Midhaul transport delay (one way) | Delay constraint for midhaul are derived mainly from the target service's latency requirements, rather than specific requirements of the Midhaul's user or control planes. As service delay targets become tighter it may become necessary to:
  1. 1) Place Midhaul and Backhaul mobile components in close proximity to each other to reduce the delay impact of the transport network.
  2. 2) Combine mobile functions together so 3GPP interfaces run internally within a "Network Function" or within a data center to remove the delay impact associated with the WAN transport network. For example, combining O-RU, O-DU and O-CU or combining the O-DU and O-CU functions together.

<1.5ms-10ms [83]

| See section 11.3 for more detail. | - -**Table 5: Midhaul transport requirements.** - -**For generic Midhaul and Backhaul requirements please see -Table 6: Common Midhaul / Backhaul Xhaul transport requirements.** - -1 -2 -3 -4 -5 -6 -7 -8 - -1 - -# 9 Backhaul - -2 -3 -4 -5 -6 -7 - -There are many similarities between Midhaul and Backhaul components of a 5G RAN infrastructure and the transport infrastructure needed to support it. In order to avoid duplication this document has dedicated chapters covering Midhaul and Backhaul. These contain descriptions of the component and a requirements table. For requirements that are common for both Midhaul and Backhaul they are held in the Backhaul requirements section (see section 9.3). There is also a common chapter (chapter 0) dedicated to dimensioning the transport network. - -8 - -## 9.1 Backhaul details - -9 -10 -11 -12 -13 -14 -15 - -From a 5G architectural perspective Fronthaul, Midhaul and Backhaul components and associated interfaces are always present. However, the impact on the transport architecture depends on where the different 3GPP components are placed and their proximity to each other. In a traditional D-RAN architecture the O-RU, O-DU, O-CU (or equivalent 4G components) are either integrated together or contained within a single cell site and the transport network for Backhaul run from the cell site to the mobile core. In a C-RAN NR architecture or disaggregated RAN architecture the Backhaul network connects the “Centralised Unit” (O-CU) to the mobile core components. - -![Four network diagrams showing different 5G RAN architectures (D-RAN and C-RAN derivatives) and their transport network requirements. Each diagram shows the flow of data from O-RU/O-DU/O-CU components through TNE nodes to a UPF. The first diagram shows a standard C-RAN architecture with Fronthaul (7.2x), Midhaul (F1), and Backhaul (N3/9) segments. The second diagram shows a C-RAN architecture where O-DU and O-CU are integrated. The third diagram shows a C-RAN architecture where O-RU and O-DU are integrated. The fourth diagram shows a D-RAN architecture where all components are integrated. A legend at the bottom identifies the transport types: Fronthaul Transport (red line), Midhaul Transport (orange line), and Backhaul Transport (blue line).](db5ab5d386827a5d5f5fad0f45612b90_img.jpg) - -The diagram illustrates four different 5G RAN architectures and their transport network requirements. Each architecture consists of O-RU, O-DU, O-CU, and UPF components connected via TNE nodes. The transport network is divided into Fronthaul, Midhaul, and Backhaul segments. - -- Architecture 1 (Top):** O-RU is connected to O-DU via Fronthaul Transport (7.2x). O-DU is connected to O-CU via Midhaul Transport (F1). O-CU is connected to UPF via Backhaul Transport (N3/9). The path consists of four TNE nodes. -- Architecture 2:** O-RU is connected to a combined O-DU/O-CU unit via Fronthaul Transport (7.2x). The combined unit is connected to UPF via Backhaul Transport (N3/9). The path consists of four TNE nodes. -- Architecture 3:** A combined O-RU/O-DU unit is connected to O-CU via Fronthaul Transport (7.2x). O-CU is connected to UPF via Backhaul Transport (N3/9). The path consists of four TNE nodes. -- Architecture 4 (Bottom):** A combined O-RU/O-DU/O-CU unit is connected directly to UPF via Backhaul Transport (N3/9). The path consists of four TNE nodes. - -**Legend:** - -- Fronthaul Transport (Red line) -- Midhaul Transport (Orange line) -- Backhaul Transport (Blue line) - -Four network diagrams showing different 5G RAN architectures (D-RAN and C-RAN derivatives) and their transport network requirements. Each diagram shows the flow of data from O-RU/O-DU/O-CU components through TNE nodes to a UPF. The first diagram shows a standard C-RAN architecture with Fronthaul (7.2x), Midhaul (F1), and Backhaul (N3/9) segments. The second diagram shows a C-RAN architecture where O-DU and O-CU are integrated. The third diagram shows a C-RAN architecture where O-RU and O-DU are integrated. The fourth diagram shows a D-RAN architecture where all components are integrated. A legend at the bottom identifies the transport types: Fronthaul Transport (red line), Midhaul Transport (orange line), and Backhaul Transport (blue line). - -16 -17 -18 -19 -20 -21 -22 - -Figure 10 shows some examples of how the placement of the various 5G NR components determines the size of the transport network associated with the Backhaul. The bottom architecture is a D-RAN architecture while all the others are C-RAN derivatives. - -![Figure 10: Backhaul layout with various RAN splits. The diagram shows four different RAN split options. Each option consists of a series of TNE (Transport Network Edge) nodes connected by colored lines representing different transport types: Fronthaul (red), Midhaul (orange), and Backhaul (blue). Option 1: O-RU connects to O-DU via 7.2x (Fronthaul), O-DU connects to O-CU via F1 (Midhaul), and O-CU connects to UPF via N3/9 (Backhaul). Option 2: O-RU connects to a combined O-DU/O-CU unit via 7.2x (Fronthaul), and the combined unit connects to UPF via N3/9 (Backhaul). Option 3: O-RU/O-DU connects to O-CU via 7.2x (Midhaul), and O-CU connects to UPF via N3/9 (Backhaul). Option 4: O-RU/O-DU/O-CU connects directly to UPF via N3/9 (Backhaul).](b235edb1dbe659e2782c9a0e47775ca4_img.jpg) - -Figure 10: Backhaul layout with various RAN splits. The diagram shows four different RAN split options. Each option consists of a series of TNE (Transport Network Edge) nodes connected by colored lines representing different transport types: Fronthaul (red), Midhaul (orange), and Backhaul (blue). Option 1: O-RU connects to O-DU via 7.2x (Fronthaul), O-DU connects to O-CU via F1 (Midhaul), and O-CU connects to UPF via N3/9 (Backhaul). Option 2: O-RU connects to a combined O-DU/O-CU unit via 7.2x (Fronthaul), and the combined unit connects to UPF via N3/9 (Backhaul). Option 3: O-RU/O-DU connects to O-CU via 7.2x (Midhaul), and O-CU connects to UPF via N3/9 (Backhaul). Option 4: O-RU/O-DU/O-CU connects directly to UPF via N3/9 (Backhaul). - -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 - -**Figure 10: Backhaul layout with various RAN splits** -source: Cisco - -Figure 11 shows components and the 3GPP interfaces in the mobile Backhaul. It has a control plane component and user plane component. It is not uncommon to see the control plane and the user plane divided into separate closed user groups at the transport layer to ensure a clear demarcation between customer user data and the 3GPP control plane. - -![Figure 11: 5G Backhaul components and interfaces. This diagram illustrates the 5G system architecture with components: UE, (R)AN, AMF, SMF, PCF, AF, UPF, and DN. Interfaces are labeled N1 through N15. The diagram is shaded to distinguish between the control plane (light blue) and the user plane (light green). The control plane includes interfaces N1, N2, N11, N14, N15, and N4. The user plane includes interfaces N3, N6, N7, N8, N9, and N5. A legend on the right indicates 'BH UP' (Backhaul User Plane) in green and 'BH CP' (Backhaul Control Plane) in blue.](705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg) - -Figure 11: 5G Backhaul components and interfaces. This diagram illustrates the 5G system architecture with components: UE, (R)AN, AMF, SMF, PCF, AF, UPF, and DN. Interfaces are labeled N1 through N15. The diagram is shaded to distinguish between the control plane (light blue) and the user plane (light green). The control plane includes interfaces N1, N2, N11, N14, N15, and N4. The user plane includes interfaces N3, N6, N7, N8, N9, and N5. A legend on the right indicates 'BH UP' (Backhaul User Plane) in green and 'BH CP' (Backhaul Control Plane) in blue. - -11 -12 -13 -14 -15 -16 - -**Figure 11: 5G Backhaul components and interfaces** -Source: Adapted from 3GPP TS 23.501 v6.4.0(2020-03): System Architecture for 5G [67] with control plane / user plane shading added by document authors. - -The 5G 3GPP interfaces associated with Backhaul are: - -- **N1 interface** is a logical control plane interface between the mobile core network and the UE. From a physical perspective it flows via the RAN through the Backhaul infrastructure to the AMF. It is a signalling interface between the UE and the AMF. -- **N2 interface** supports control plane signalling between RAN and 5G core. It is primarily concerned with connection management, UE context and PDU session management, and UE mobility management. In addition, Non-Access Spectrum (NAS) signalling between the UE and the AMF is transported over the N2 connection for that UE. This signalling includes information regarding access control, authentication and authorization, and session management procedures. -- **N4 Interface** is the bridge between the control plane and the user plane of the 5GC. It runs between the SMF and the UPF and is responsible for conveying policy rules regarding policy handling, forwarding and usage reporting to the UPF. -- **N3 interface** is the user plane interface between the O-CU component of the (gNB) and the initial UPF. -- **N9 interface** is a user plane interface that runs between two UPFs. (i.e. an intermediate UPF and the UPF session anchor). - -## 9.2 Backhaul transport evolution in 5G - -The RAN Backhaul network has been a feature of every 3GPP generation, and many transport network engineers are familiar with the transport requirements RAN Backhaul of previous 3GPP generations. However, 5G introduces some significant changes that will alter the requirements and nature of the Backhaul infrastructure. - -In the past 3GPP interfaces across the Backhaul networks tended to be hub and spoke in nature, with the radios at the edge and the mobile core control and user planes gateway components located in a fairly centralised location. See Figure 12 for details. - -![Diagram illustrating the backhaul 3GPP interfaces overlaid over a transport network. On the left, three 'Cell' units are connected to a central cloud representing the transport network. Inside the cloud, a 'Mobile control plane' is connected to the transport network via a dashed blue line. The transport network is connected to 'S/PGWs' (Serving/PDN Gateways). From the S/PGWs, three solid lines lead to different types of GILAN (Gateway Interface for LTE/5G) clouds: 'Consumer GILAN' (yellow), 'Enterprise GILAN' (blue), and 'MVNO GILAN' (green). The diagram also shows '3GPP control plane interfaces' (dashed blue lines) and '3GPP User plane interfaces (GTP tunnels)' (solid blue lines) within the transport network cloud. The caption below the diagram reads 'Backhaul 3GPP interfaces overlaid over transport network'.](55136bc716146672fc680fa05989f1d2_img.jpg) - -Diagram illustrating the backhaul 3GPP interfaces overlaid over a transport network. On the left, three 'Cell' units are connected to a central cloud representing the transport network. Inside the cloud, a 'Mobile control plane' is connected to the transport network via a dashed blue line. The transport network is connected to 'S/PGWs' (Serving/PDN Gateways). From the S/PGWs, three solid lines lead to different types of GILAN (Gateway Interface for LTE/5G) clouds: 'Consumer GILAN' (yellow), 'Enterprise GILAN' (blue), and 'MVNO GILAN' (green). The diagram also shows '3GPP control plane interfaces' (dashed blue lines) and '3GPP User plane interfaces (GTP tunnels)' (solid blue lines) within the transport network cloud. The caption below the diagram reads 'Backhaul 3GPP interfaces overlaid over transport network'. - -**Figure 12: Transport organization of tradition Backhaul networks (Source Cisco)** - -1 -2 -3 -4 -5 -6 -7 -8 -9 - -With the advent of new 5G use cases, CUPS, MEC and slicing both the control and user plane Backhaul interfaces will become more multi-point in nature, with IP end points needing to communicate with other IP end points distributed around the whole transport network. This connectivity can be provided using either L3 routing or E-LAN / E-Tree services or a combination of both. In addition, with the advent of 5G slicing the transport network will need to support multiple L2 and L3 closed user groups on the transport infrastructure and in some cases permit controlled connectivity between and within closed user groups. See Figure 13 for details. - -![Diagram of 5G Backhaul infrastructure overlaying the transport infrastructure. It shows multiple e/gNB units on the left connected to a central transport network. The transport network features two main backhaul paths: a 'Yellow backhaul' and a 'Green backhaul'. Above these are 'Blue N6' and 'Yellow N6' cloud-like representations. Below are 'Blue 3GPP control plane' and 'Green 3GPP control plane' blocks. Various UPFs (User Plane Functions) are shown connected to the backhaul paths and the N6 clouds. The diagram illustrates the complex multi-point connectivity required for 5G slicing and CUPS.](7d2d1d3870cd224c4430d19334557716_img.jpg) - -Diagram of 5G Backhaul infrastructure overlaying the transport infrastructure. It shows multiple e/gNB units on the left connected to a central transport network. The transport network features two main backhaul paths: a 'Yellow backhaul' and a 'Green backhaul'. Above these are 'Blue N6' and 'Yellow N6' cloud-like representations. Below are 'Blue 3GPP control plane' and 'Green 3GPP control plane' blocks. Various UPFs (User Plane Functions) are shown connected to the backhaul paths and the N6 clouds. The diagram illustrates the complex multi-point connectivity required for 5G slicing and CUPS. - -10 -11 -12 -13 -14 -15 -16 -17 -18 - -**Figure 13: 5G Backhaul infrastructure overlaying the transport infrastructure (Source Cisco)** - -## 9.3 Backhaul and Midhaul transport requirements - -The transport requirements for Midhaul and Backhaul are very similar. The table below captures Backhaul and common Midhaul / Backhaul transport requirements. For transport requirements specific only to Midhaul please refer to Table 6. - -| Capability | Requirements | Notes | -|-----------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| 3GPP interfaces | Control Plane: N1, N2, N4
User Plane: N3, N9 | | -| Network and transport protocols | All 3GPP interfaces are IPv4 or IPv6
Control plane: IP/SCTP
Data plane: IP/UDP/GTPv2 | | -| Logical connectivity requirements | Control Plane: Multi-point connectivity at the IP interface level (IPv4 or IPv6) between mobile components.
User Plane: Multi-point at the IP interface level (IPv4 or IPv6) between mobile components | This requirement could be met by the use of an L3 or an L2 solution or a combination of the two. Technology solution for the transport network to meet these requirements will be covered in technology specific O-RAN documents or by | - -| | | | -|----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| -| | |

transport solutions specified by other organization. Later revisions of this document will reference these documents.

| -|

Scope of the transport network for Midhaul and Backhaul

|

The transport network consists of WAN components, the networking (switching) infrastructure within the DCs and Network Functions (physical or virtual) in DCs.

R1: The WAN transport network and the DC transport networks MUST inter-operate together and allow end to end connectivity between transport components and creation of transport slices that have components in the WAN and the DC.

Midhaul and Backhaul have strong similarities. These include:

  1. 1) IP endpoints with common protocols used in the Midhaul and Backhaul networks.
  2. 2) The O-CU is part of the 3GPP Midhaul and the Backhaul network, so from a transport network perspective, Midhaul and Backhaul connectivity is presented by different physical or logical interfaces in the same “Network Function” (NF) and most likely same physical locations.
  3. 3) For deployment reasons, some radios in a cell site may be running a D-RAN architecture and other radios may be running a C-RAN architecture. Consequently, the same part of the transport network could be running both Midhaul and Backhaul services.

R2: With these commonalities and overlaps strong consideration MUST be given by operators to designing, building and operating a single packet orientated transport infrastructure that supports both Midhaul and Backhaul services.

R3: In scenarios where a common transport technology is used in Backhaul, Midhaul and Fronthaul then an operator MAY choose to build a common end-to-end transport

| | - -| | | | -|--------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | infrastructure supporting Backhaul, Midhaul and Fronthaul. | | -| Transport network scale for Backhaul |

R4: For national mobile infrastructures the Transport network architecture:
MUST support mobile networks up to 100,000 O-RU locations.
MAY support mobile networks up to 500,000 O-RU locations.

|

The size of a Backhaul infrastructure depend on the radio architecture. In D-RAN scenarios the transport network could potentially need to support these very large numbers of transport endpoints. The number of endpoints in the Backhaul will be smaller if radio architectures based on Fronthaul, Midhaul or both are implemented.

The architectural solution needs to scale to very large number of transport endpoints without exhausting key transport resources or significantly inflating the transport solution costs.

| -| Transport infrastructure |

Physical interfaces
Mobile equipment associated with Midhaul and Backhaul present Ethernet interfaces at the data link layer.

In Midhaul and Backhaul the mobile equipment runs IPv4 and/or IPv6 at the network layer.

User Network Interface - Customer (UNI-C)
R5: The Midhaul and Backhaul transport network MUST support physical Ethernet interfaces at the UNI-C. See Figure to the right.

R6: The Midhaul and Backhaul transport network MUST support Ethernet services based on a full Ethernet port towards the end-user. For example, an EPL service as defined by MEF 6.2.

R7: The Midhaul and Backhaul transport network MUST support Ethernet virtual services based on VLANs within an Ethernet port towards the end user. For example, an EVPL services as defined by MEF 6.2

|

See ORAN-WG5 transport specification for Midhaul equipment. [60]

Image: Diagram showing a radio tower connected to a 'Transport Network' cloud via a 'UNI' interface. Labels include 'UNI-C: User to Network Interface-customer' and 'UNI-N: User to Network Interface-network'.

| - -| | | | -|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

R8: The Midhaul and Backhaul transport network MUST support subscriber IP services. For example, as defined by MEF61.1.


R9: The transport network MUST support subscriber IP services on a full Ethernet port basis or over VLANs within an Ethernet port.


R10: Subscriber IP services MUST be supported over a single UNI Access link.


R11: Subscriber IP services MAY be supported over:

  1. 1) UNI access links terminating on different devices at the SP.
  2. 2) UNI Access links terminating on different devices at the SP and the subscriber.
  3. 3) UNI Access links terminating on different devices at the subscriber

R12: The transport network MUST support ingress bandwidth control mechanisms for Ethernet, IPv4 and IPv6. This is applied to traffic flowing across the UNI interface from the subscriber towards the transport network.

  1. 1) Ingress classification and packet marking
  2. 2) Ingress traffic conditioning bases on classes with an Ethernet port.
  3. 3) Hierarchical ingress traffic conditioning based on VLANs and classes within the VLAN.

R13: The transport network MUST support egress bandwidth control mechanisms for Ethernet, IPv4 and IPv6. This is applied to traffic flowing across the UNI interface towards the end-user.

  1. 1) Egress traffic conditioning and scheduling based on classes with an Ethernet port.
  2. 2) Hierarchical ingress traffic conditioning and scheduling based on VLANs and classes within the VLAN.

Transport Services

R14: The transport infrastructure MUST support mechanisms to create:

|

.








Refer to MEF 61.1 [68] section 7.3 for more details on IP service UNIs





See MEF 61.1 [68] “Bandwidth Profiles” for examples of typical actions applied on ingress and egress for IP services


See MEF 10.3 [69] “Bandwidth Profiles” for examples of typical actions applied on ingress and egress of Ethernet services







Refer to MEF 61.1 [68] for details of IP services

| -|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| - -Image: O-RAN ALLIANCE logo - -O-RAN.WG9.XTRP-REQ.0-R005-v02.00 - -| | | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -|
  1. 1) Basic IPv4 and IPv6 routing infrastructure
  2. 2) IPv4 or IPv6 Virtual Private Networks – any to any
  3. 3) IPv4 or IPv6 Virtual Private Networks – controlled access
  4. 4) IPv4 or IPv6 Virtual Private Networks with extranet
  5. 5) EPL and EVPL
  6. 6) EP-LAN and EVP-LAN
  7. 7) EP-Tree and EVP-Tree
| Ref to MEF 6.2 [70] for details of Ethernet services | -|

Transport network QoS and availability

R15: Transport network MUST have mechanisms or utilise an architecture that implements Quality of Service based on QoS markings within the actual Midhaul / Backhaul packet.

QoS markings could be Ethernet class of service markings, MPLS class of service marking, IPv4 DSCP or IPv6 traffic class marking. The appropriate QoS scheme will be determined by the transport architecture employed.

R16: Transport network MUST support QoS / availability mechanisms to enable SLAs to be offered to support 5G slices.

Transport network SLAs for slices cover IP network delay characteristics and IP network availability.

R17: Transport network MUST support mechanisms to ensure suitable behavioural isolation between transport slices on access and within the core of the transport network.

R18: Transport network MUST support mechanisms to control and map a transport slice to the transport network’s physical topology.

R19: Transport network MUST implement transport slice protection / restorations schemes that allow 50ms protection of IP connectivity between slice endpoints.

R20: The transport network MAY support other mechanisms to improve Transport slice reliability between IP endpoints. These could be

|



















Note: A transport NSSI is not necessarily a network wide phenomenon. It may only be running in a small section of the network. | - - Copyright © 2025 by the O-RAN ALLIANCE e.V. - Your use is subject to the copyright statement on the cover page of this specification. - -34 - -| | | | -|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------| -| |

protection mechanisms or other schemes such as multi-path traffic delivery.

Transport network OAM and management

R21: Transport equipment (DC and WAN) MUST support standard model-based approaches to support basic device and network configuration.

R22: If appropriate, transport equipment (DC and WAN) MUST support standard model-based approaches to configure transport slices.

R23: Transport equipment MUST support OAM tools to test link level capabilities.

R24: Transport equipment MUST support OAM tools to test end to end connectivity.

R25: Mechanisms MUST exist to determine the liveliness of transport network equipment.

R26: Mechanisms MUST exist to determine liveliness of services running on the transport network

R27: Mechanisms MUST exist to determine delay and jitter of services running on the transport network

| | -|

Transport slicing for 3GPP Backhaul

|

R28: Transport network MUST support network slicing for the 3GPP Backhaul network.

Transport slice scale

R29: The transport network slicing architecture MUST support the key 5G services and within each service type support 1000s of different customers that require isolation from each other.

R30: The transport network slicing architecture MUST be capable of extending to every end site and also every DC locations.

Transport Slice capabilities

R31: The transport slicing solution MUST support the creation of slices that span from the WAN into the DC networking infrastructure.

R32: Midhaul / Backhaul transport slices MUST allow:

|

Please refer to Appendix B: Slicing in Backhaul and Midhaul

| - -| | | | -|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| -| |
  1. 1) Multi-point connectivity model between IP endpoints.
  2. 2) Connectivity between 3GPP components residing solely in the WAN space.
  3. 3) Connectivity between 3GPP components residing in either the same data center or different data centers
  4. 4) Connectivity between 3GPP components residing in the WAN and 3GPP components residing in a data center.
  5. 5) For a NF (physical or virtual) to inject and learn slice connectivity information from either WAN or DC transport components.

R33: In situations where an operator builds a common transport infrastructure for Midhaul and Backhaul. Transport slices MAY be built so a common transport slice covers both the Midhaul and Backhaul interfaces or they MAY be built so there is a dedicated transport slice for Midhaul interfaces and another for Backhaul interfaces.

Transport slice connectivity models
R34: Transport network MUST enable the creation of discrete any-to-any VPNs for different transport slices. End points will be IP entities and may reside in the WAN or a DC.

R35: Transport network MUST support the ability to run the Midhaul/Backhaul control plane and user plane of a slice in different VPNs.

R36: The transport network MUST support complete connectivity isolation within a Transport slice so only those entities associated with that slice instance can communicate at the transport layer.

R37: The transport network MUST support controlled connectivity from within one transport slice to IP entities that are either common to multiple slices or reside in another Transport slice. This is often termed Extranet connectivity

| | -|--|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--| - -| | | | -|-------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| |

R38: The transport network MUST support controlled connectivity between IP entities within the same Transport slice.

Transport slice OAM

R39: Transport network MUST support mechanisms to test and report transport slices edge-to-edge connectivity and response times to enable the performance of the transport slice to be monitored.

R40: Transport network MUST support mechanisms to export transport SLA measurement details to an external storage infrastructure.

| | -| Peak 5G DL data rates |

Peak 5G data rates are highly dependent on overall cell site configuration and radio characteristics. This document uses four example site configurations to illustrate bandwidth requirements. Theoretical 5G NR peak data bandwidths for each site type are:
Small Site (FR1): 1.8Gbps
Small Site (FR2): 3.3Gbps
Medium Site (FR1 + FR2): 25.8Gbps
Large site (FR1 + FR2): 62.7Gbps

| See chapter 10 for more details on carrier and sector peak DL bandwidth. | -| Peak site 5G DL rates with encapsulation (all carriers and sectors included). |

An encapsulation overhead of 10% has been used to calculate the peak 5G DL traffic rates.

Small Site (FR1) (1 sector): 2.0Gbps
Small Site (FR2) (1 sector): 3.7Gbps
Medium Site (FR1 + FR2) (3 sector): 28.4Gbps
Large site (FR1 + FR2) (3 sector): 68.8Gbps

| See chapter 10 for more details and considerations for selecting encapsulation overhead. | -| Transport provisioning |

Midhaul and Backhaul traffic is primarily made up of user data and precise levels depend on usage. When provisioning a statistically multiplexed transport network it is normal to assume a statistic multiplexing gain as the network travels from the edge towards the core in such networks

Access provisioning

Backhaul traffic is only present on access circuits in D-RAN architectures.
Midhaul traffic is only present on access circuits when the RU/DU are co-located on the cell site.
Using the four example site configurations and the empirical dimensioning rule outlined in chapter 10 shows the following bandwidth would be required on the access circuit. These

|

See chapter 10 for more details on different provisioning rules.

It should be noted that even in single sector cell sites operators can choose to provision the access capacity below the peak radio rate of the site.

| - -| | | | -|-----------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------| -| |

figures are similar for scenarios where the access circuit supports Backhaul or Midhaul.

Small Site (FR1 carrier only): ~2.0Gbps
Small Site (FR2 carrier only): ~3.7Gbps
Medium Site (FR1 + FR2 carriers): ~15.2Gbps
Large site (FR1 + FR2 carriers): ~36.8Gbps

Pre-Aggregation and Aggregation
Dependent on SPs specific transport dimensioning and capacity planning rules. The statistical gain will increase as the traffic moves from the access towards the mobile core if the traffic is traversing statistically multiplexing equipment.

| | -| Transport Technology | Not part of the scope of this document. | Please refer to specific technology orientated documents coming from WG-9 for technology and architectural details. | -| End to end Backhaul Transport delay (one way) |

Delay constraint for Backhaul are derived mainly from the target service's latency requirements, rather than specific requirements of the Backhaul's user or control planes. As service delay targets become tighter it may become necessary to:

3) Place Midhaul and Backhaul mobile components in close proximity to each other to reduce the delay impact of the transport network. For example, O-DU, O-CU and UPF in the same data center.

4) Combine mobile functions together so 3GPP interfaces run internally within a "Network Function" or within a data center to remove the delay impact associated with the WAN transport network. For example, combining O-RU, O-DU and O-CU or combining the O-DU and O-CU functions together.

1ms – 50ms service dependent.

|

Dependent on 5G service type

See section Error! Reference source not found. for more detail

| -| Synchronization / timing requirements | See chapter 12 for synchronization and timing requirements. | | - -**Table 6: Common Midhaul / Backhaul Xhaul transport requirements plus specific Backhaul requirements** - -###### NOTES: - -- 1) The above tables reference various documents from other standards organizations (for example the MEF). It is important to note that the requirement does not imply that the - -- 1 transport equipment, nor the transport network needs to be compliant with these particular -2 documents. Rather these documents provide a good explanation or definition of the capability. -3 2) Technology solution for the transport network to meet these requirements will be covered in -4 technology specific O-RAN documents or by other organizations specify transport solutions. -5 -6 -7 - -# 10 D2 - -## 10.1 D2 details - -This section covers the transport requirements for D2 as mentioned in section 6.1.3. Figure 14 indicates the RAN architecture where D2 interface is shown over D2. The O-RAN defined D2 interface operates on this to provide connectivity between O-DUs, which can be used to improve the user experience and coverage by supporting features such as inter O-DU Carrier Aggregation. - -![RAN architecture diagram showing O-RU2, O-DU1, O-DU2+O-RU2, O-CU, and AMF connected via Fronthaul, Midhaul, and Backhaul links. The D2 interface is highlighted between O-DU1 and O-DU2+O-RU2.](0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg) - -The diagram illustrates a RAN architecture with the following components and interfaces: - -- O-RU2** is connected to **O-DU1** via an **O-RAN 7.2x** interface (Fronthaul). -- O-DU1** is connected to **O-CU** via an **F1** interface (Midhaul). -- O-CU** is connected to **AMF** via an **N2/N3** interface (Backhaul). -- O-DU1** and **O-DU2+O-RU2** are connected via a **D2** interface (highlighted in green). -- O-DU2+O-RU2** is connected to **O-CU** via an **F1** interface (Midhaul). - -At the top, a color-coded line shows the hierarchy: **Fronthaul** (red), **Midhaul** (yellow), and **Backhaul** (blue). At the bottom, another color-coded line shows **Midhaul** (yellow) and **Backhaul** (blue). - -RAN architecture diagram showing O-RU2, O-DU1, O-DU2+O-RU2, O-CU, and AMF connected via Fronthaul, Midhaul, and Backhaul links. The D2 interface is highlighted between O-DU1 and O-DU2+O-RU2. - -Figure 14: RAN architecture where D2 is required - -D2 provides connectivity between O-DUs that can be used for various use cases such as inter O-DU Carrier Aggregation (CA) - -## 10.2 D2 Requirements - -| Category | Comments | -|----------------------------------|-------------------------------------------------------------------------------| -| Interfaces | D2 | -| Protocols | IP/UDP for D2-u or SCTP/IP for D2-c according to clauses 7 and 8 in [86] | -| Logical Connectivity requirement | Point to point at IP layer | -| Bandwidth per O-DU pair | Similar to midhaul | -| Transport delay (one-way) | Recommended as 200 microseconds one way. Maximum as 500 microseconds one way. | - -The maximum One-way Frame Loss Ratio is $10^{-7}$ . - -The D2 bandwidth requirement is same as the midhaul requirement mentioned in section 11.2 - -1 The D2 latency requirement for D2-u traffic is a 500 microseconds maximum one way, with a -2 recommended value of 200 microseconds one way as mentioned in D2 GAP specification [86]. The -3 D2 latency requirement for D2-c traffic is similar to midhaul requirements for F1-c. -4 -5 - -# 11 Transport network dimensioning for Midhaul and Backhaul - -The Backhaul and Midhaul segments of a 5G network have many similarities in terms of dimensioning and provisioning rules which feed through to the transport network as requirements. This chapter covers transport dimensioning for Midhaul and Backhaul. - -## 11.1 Transport capacity and radio density with 5G - -5G represents a significant increase in capacity and size of the transport network over previous 3GPP generations. A common quote is 5G will bring a ten-fold increase in capacity, number of radios and end-user devices when compared with LTE. - -## 11.2 Backhaul and Midhaul transport planning - -Traffic rates in Midhaul and Backhaul traffic rates are highly dependent on end user usage and it is possible to dimension and provision the transport network for Midhaul and Backhaul assuming a statistic multiplexing gain. The precise gain will vary depending on the architecture of the transport infrastructure and the RAN architecture. There are three steps in dimensioning the transport network for Midhaul and Backhaul: - -- 1) Calculate the peak rate for sectors within a site -- 2) Add Midhaul and Backhaul transport overheads -- 3) Calculate peak and average site usage -- 4) Apply a statistical multiplexing factor to determine the bandwidth to provision in various parts of the Midhaul and Backhaul transport network. - -### 11.2.1 5G NR peak bandwidth - -5G NR increases the data volumes seen in Backhaul, and if implemented in Midhaul, compared with previous generations of 3GPP technology. The formula below calculates the peak 5G data bandwidth for a single sector site. - -$$\text{data rate (in Mbps)} = 10^{-6} \cdot \sum_{j=1}^J \left( v_{\text{Layers}}^{(j)} \cdot Q_m^{(j)} \cdot f^{(j)} \cdot R_{\max} \cdot \frac{N_{\text{PRB}}^{BW(j),\mu}}{T_s^\mu} \cdot 12 \cdot (1 - OH^{(j)}) \right)$$ - -Where - -- $j$ is the sum of the carriers -- $v_{\text{layers}}^{(j)}$ is the number of MIMO layers -- $Q_m^{(j)}$ is the modulation order - - 2 - QPSK - - 4 - 16QAM - - 6 - 64QAM - - 8 - 256QAM -- $f^{(j)}$ is the scaling factor -- $R_{\max}$ is 948/1024 -- $N_{\text{PRB}}^{BW(j),\mu}$ is RB allocation. Determined by subcarrier spacing, which can be elucidated from numerology ( $\mu$ ) and bandwidth. -- $T_s^\mu = \frac{10^{-3}}{14 \times 2^\mu}$ is the average OFDM symbol duration in a subframe for numerology - -- $\mu$ is the numerology (0-15kHz SCS, 1-30kHz SCS, 2-60kHz SCS, 3 – 120kHz SCS) -- $OH^{(j)}$ is the overhead (0.14-FR1 DL, 0.18-FR2 DL, 0.08-FR1 UL, 0.10-FR2 UL) - -For explanation of above formula see 3GPP TS 38.306 version 15.2.0 Release 15 [71] There are also multiple b/w calculators on the worldwide web. For example: which calculates both “Frequency Division Duplex” FDD and “Time Division Duplex” (TDD) use cases. - -###### **Notes** - -- 1) The calculated data rate is the theoretical maximum achievable by the radio/radios. Real data rates depend on the radio placement, configuration of the cell site, the surrounding area, number of active UEs, their capabilities and usage. -- 2) This figure does not include Backhaul or Midhaul transport overhead; namely IP/UDP and GTP and potentially IPSEC encapsulation. - -Table 7 shows the peak downlink (DL) data rates for some of the radio profiles outlined in Annex A of Fronthaul Interoperability Test Specification (IOT) document and the 5G NR radio components used in the small, medium and large sites examples used throughout this document. - -| O-RAN IOT Profile or site profiles | Frequency range | Mode | Carriers (j) | MIMO layers v(j) | DL Modulation | B/W (MHz) | $\mu$ | TDD slot format | Peak DL b/w (Gbps) | -|------------------------------------|-----------------|------|--------------|------------------|---------------|-----------|-------|-----------------|--------------------| -| Profile 1&2 | FR1 | TDD | 1 | 4 | 256QAM | 100 | 1 | Format 25 | 1.84 | -| Profile 3 (low) | FR2 | TDD | 1 | 2 | 256QAM | 100 | 3 | Format 25 | 0.85 | -| Profile 3 (high) | FR2 | TDD | 8 | 2 | 256QAM | 800 | 3 | Format 25 | 6.77 | -| Profile 1 | FR1 | FDD | 1 | 8 | 256QAM | 30 | 0 | NA | 1.37 | -| Profile 2 | FR1 | FDD | 1 | 8 | 256QAM | 20 | 1 | NA | 0.87 | -| Profile 3 | FR1 | FDD | 1 | 4 | 256QAM | 30 | 1 | NA | 0.67 | -| Profile 4 | FR1 | FDD | 1 | 4 | 256QAM | 20 | 0 | NA | 0.45 | -| Small site -FR1 | FR1 | TDD | 1 | 4 | 256QAM | 100 | 1 | Format 25 | 1.84 | -| Small site-FR2 | FR2 | TDD | 1 | 2 | 256QAM | 400 | 3 | Format 25 | 3.39 | -| Medium site | FR1 | TDD | 1 | 4 | 256QAM | 100 | 1 | Format 25 | 1.84 | -| Medium site | FR2 | TDD | 1 | 4 | 256QAM | 400 | 3 | Format 25 | 6.77 | -| Large site | FR1 | TDD | 1 | 16 | 256QAM | 100 | 1 | Format 25 | 7.34 | -| Large site | FR2 | TDD | 2 | 4 | 256QAM | 400 | 3 | Format 25 | 13.54 | - -Notes - Frequency Range (FR1) refers to frequencies below 7.225 GHz - Frequency Range (FR2) refers to frequency bands from 24.250 GHz to 52.6 GHz spectrum (also referred to as “millimeter wave range”) - FDD mode: both uplink and downlink can transmit at the same time at different spectrum frequencies. - TDD mode, both uplink and downlink use the same spectrum frequencies but at different times. - Format 25 allocates 0.785714286 bandwidth to downlink - Calculation for a 1 sector cell site. - -**Table 7: Peak Backhaul DL bandwidth for a selection of O-RAN IOT and 5G NR site examples** - -### **11.2.2 Site peak data rates** - -To calculate the maximum downlink bandwidth, it is necessary to sum the bandwidths associated with all radios in the site and add encapsulation overhead. The peak 5G NR DL data rates associated with the three example site profiles; small, medium and large are shown below. - -Note: Only the 5G radio components are considered. In the real-world, previous generations of 3GPP technology will most likely be deployed alongside 5G NR, so these components also need to be added. - -| Frequency range | Mode | sectors | Carriers (j) | MIMO layers v(j) | DL Modulation | B/W (MHz) | $\mu$ | TDD slot format | Single sector DL b/w (Mbps) | Peak site DL b/w (Gbps) | -|-----------------|------|---------|--------------|------------------|---------------|-----------|-------|-----------------|-----------------------------|-------------------------| -|-----------------|------|---------|--------------|------------------|---------------|-----------|-------|-----------------|-----------------------------|-------------------------| - -| | | | | | | | | | | | -|-----|-----|---|---|---|--------|-----|---|----|------|---------------------| -| FR1 | TDD | 1 | 1 | 4 | 256QAM | 100 | 1 | 25 | 1836 | 1.84 | -| | | | | | | | | | | Total (Gbps) | -| | | | | | | | | | | 1.84 | - -**Table 8: FR1 small site peak DL data bandwidth** - -| Frequency range | Mode | sectors | Carriers (j) | MIMO layers v(j) | DL Modulation | B/W (MHz) | $\mu$ | TDD slot format | Single sector DL b/w (Mbps) | Peak site DL b/w (Gbps) | -|-----------------|------|---------|--------------|------------------|---------------|-----------|-------|-----------------|-----------------------------|-------------------------| -| FR2 | TDD | 1 | 1 | 2 | 256QAM | 400 | 3 | 25 | 3386 | 3.39 | -| | | | | | | | | | | Total (Gbps) | -| | | | | | | | | | | 3.39 | - -**Table 9: FR2 small site peak DL data bandwidth** - -| Frequency range | Mode | sectors | Carriers (j) | MIMO layers v(j) | DL Modulation | B/W (MHz) | $\mu$ | TDD slot format | Single sector DL b/w (Mbps) | Peak site DL b/w (Gbps) | -|-----------------|------|---------|--------------|------------------|---------------|-----------|-------|-----------------|-----------------------------|-------------------------| -| FR1 | TDD | 3 | 1 | 4 | 256QAM | 100 | 1 | 25 | 1836 | 5.5 | -| FR2 | TDD | 3 | 1 | 4 | 256QAM | 400 | 3 | 25 | 6772 | 20.3 | -| | | | | | | | | | | Total (Gbps) | -| | | | | | | | | | | 25.82Gbps | - -**Table 10: Medium site peak DL data bandwidth** - -| Frequency range | Mode | sectors | Carriers (j) | MIMO layers v(j) | DL Modulation | B/W (MHz) | $\mu$ | TDD slot format | Single sector DL b/w (Mbps) | Peak site DL b/w (Gbps) | -|-----------------|------|---------|--------------|------------------|---------------|-----------|-------|-----------------|-----------------------------|-------------------------| -| FR1 | TDD | 3 | 1 | 16 | 256QAM | 100 | 1 | 25 | 7344 | 2.32 | -| FR2 | TDD | 3 | 2 | 4 | 256QAM | 400 | 3 | 25 | 13544 | 40.63 | -| | | | | | | | | | | Total (Gbps) | -| | | | | | | | | | | 62.67 | - -**Table 11: Large site peak DL data bandwidth** - -To calculate the peak Backhaul and Midhaul transport bandwidth, add the network encapsulation overhead. This can be done by: - -- 1) Calculating the packet per second -- 2) Adding the network encapsulation overhead -- 3) Calculating the transport bandwidth - -Network encapsulation overhead depends on a number of factors including: - -- L1/L2 technology -- IPv4 or IPv6 -- Average packet size -- Mobile encapsulations -- Whether the Midhaul / Backhaul are running IPSEC or not. - -The NGMN Backhaul group in “Guidelines for LTE Backhaul Traffic Estimation” [72] use an overhead of 10% to represent a general case for Backhaul (it is also applicable to Midhaul). For an Ethernet transport, IPv4, with no IPSEC encryption and an IMIX packet size (576 bytes) this is a good approximation. If IPSEC is providing Midhaul or Backhaul encryption, then the packet size increases due to the IPSEC overhead. In this scenario NGMN Backhaul group in “Guidelines for LTE Backhaul Traffic Estimation” [72] use an overhead of 14%. - -| Site Type | Peak Backhaul b/w (Gbps) | -|-------------|--------------------------| -| Small (FR1) | 2.0 | -| Small (FR2) | 3.7 | -| Medium | 28.4 | -| Large | 68.8 | - -**Table 12: Peak Backhaul site bandwidth** - -Notes: - -- 1) Midhaul and Backhaul traffic is IP and use GTP as an encapsulation for user traffic. One of the main differences is Midhaul traffic carries the “Packet Data Convergence Protocol” (PDCP), while Backhaul does not. This would suggest that Midhaul traffic volumes are greater than Backhaul traffic volumes, however although PDCP adds overhead it can, through Ethernet and IP header compression reduce the size of the user’s packet size. For this reason, this document treats Backhaul and Midhaul traffic requirements as the same. - -### 11.2.3 Estimating cell site loads - -Backhaul and midhaul cell site throughput is the sum of all the traffic generated by all UEs using that site. UE throughput varies depending on the quality of the radio link to the gNB and the amount of spectrum assigned to it. 5G radios use adaptive modulation to adjust their data rates based on the radio conditions. In good conditions, where the UE has good signal strength from the radio and there is little interference, more information can be carried without errors for each unit of spectrum. This is in contrast with scenarios where the UE has low signal strength from the radio and interference levels are high. This is called spectrum efficiency and measured in bits per second, per Hz. - -The highest radio throughput occurs when there is high spectral efficiency and largest spectrum allocation for UEs. Typically, this occurs at quiet times when there are a small number of active UEs that is in close proximity to the radio. This is known as the Quiet Time Peak rate. As the number of UEs and distribution of UE’s around the cell site increases, so the busy time mean rate is seen. This is normally significantly lower than the quiet time peak rate and is impacted by interference between radios, carriers and UEs, along with environmental factors that impact signal strength and interference such as physical location of the cell site, its surroundings and other sources of interference. - -In the provisioning examples shown in Table 13, busy time mean has been calculated as 30% of quiet time peak. This is applicable to 4G implementations, however at this time it is not clear whether this figure is appropriate to 5G NR. Transport engineers will need to liaise with the radio engineers to ascertain this figure for 5G environments. - -### 11.2.4 Transport dimensioning and provisioning for Backhaul and Midhaul - -Regardless of the RAN architecture employed, the transport network consists of various segments. Figure 14 shows two of the most common splits of the transport network between the radio and the 5G core. In the first, there are three layers of transport infrastructure; access, pre-aggregation and aggregation. In the second, there are two layers of transport infrastructure; access and aggregations. In both cases the transport network needs to be considered as a whole, however potentially different technologies and provisioning rules apply in each segment. - -Notes: Neither diagrams show the core of the transport network which tends to be behind the 5G core components. - -![Figure 14: Two diagrams illustrating 5G backhaul infrastructure. The top diagram shows a sequence of components: Access (green cloud with antenna icon), Pre-aggregation (blue cloud), Aggregation (red cloud), and 5G Core (blue box), connected by routers (cylinder icons). The bottom diagram shows a simplified version: Access (green cloud with antenna icon), Aggregation (red cloud), and 5G Core (blue box), also connected by routers.](e22af684d8e56d4c61e61bb5ddac1087_img.jpg) - -Figure 14: Two diagrams illustrating 5G backhaul infrastructure. The top diagram shows a sequence of components: Access (green cloud with antenna icon), Pre-aggregation (blue cloud), Aggregation (red cloud), and 5G Core (blue box), connected by routers (cylinder icons). The bottom diagram shows a simplified version: Access (green cloud with antenna icon), Aggregation (red cloud), and 5G Core (blue box), also connected by routers. - -**Figure 14: 5G Backhaul infrastructure overlays the transport infrastructure consisting of physical networks. Source: Cisco** - -#### 11.2.4.1 D-RAN Backhaul dimension - -In a D-RAN architecture the Backhaul component of the network goes from the cell site to mobile core which tend to be positioned centrally. - -##### 11.2.4.1.1 Access (last mile) provisioning - -Access or last mile provisioning depends on the number of radios in each cell site location. - -NGMA in “Guidelines for LTE Backhaul Traffic Estimation” [72] recommends for single cell last mile provisioning should be based on quiet time peak rate of the cell. - -For multi-sector / multi-carrier cell sites then a statistical gain can be achieved on the last mile because it is unlikely that quiet peak time peaks will occur simultaneously on all radios. NGMA in “Guidelines for LTE Backhaul Traffic Estimation” [72] outlines a number of potential provisioning approaches for multi-sector, multi-carrier cell sites. - -- 1) Peak rate provisioning: In this case it is assumed that peak throughput occurs at the same time on all cells. NGMN point out this is a worst-case scenario and is highly unlikely to occur in practise and would be an expensive provisioning strategy. -- 2) Lower bound provisioning: This assumes peaks are uncorrelated but that the busy time mean applies to all cells simultaneously. The provisioning for N off eNBs is therefore the larger of the single cell peak or N x the busy time mean, thus: - -$$\text{Lower Provisioning Bound for N cells} = \text{Max (peak, N x busy time mean)}$$ - -Applying this to a 3-sector D-RAN site then - -$$\text{Access (last mile) dimensioning} = \text{Max (1 x peak, 3 x busy time mean)}$$ - -- 3) A more conservative approach assumes that whilst one cell is peaking, the others are generating traffic at the mean busy time rate, thus: - -*Conservative Lower Bound for N cells = Max [peak+(N-1) x busy time mean, N x busy time mean]* - -Applying this to a 3-sector D-RAN site then the general last mile provisioning rules is to use - -*Access (last mile) dimensioning = peak + (2 x busy time mean)* - -In Table 13 the access bandwidth needed to cater for 5G example cell sites are shown using peak quiet time provisioning for single carrier, single sector sites. For multi-carrier, multi-sector sites a comparison is made between peak rate quiet time provisioning, lower bound provisioning and conservative bound provisioning. - -| Site Type | Carrier types | Sectors | Quiet Time Peak sector rate (Mbps) | Busy time sector mean (Mbps) | | Lower provisioning bound (Gbps) | Conservative provisioning bound (Gbps) | Peak rate provisioning (Gbps) | -|-------------|---------------|---------|------------------------------------|------------------------------|--|---------------------------------|----------------------------------------|-------------------------------| -| Small (FR1) | FR1 carriers | 1 | 2020 | 606 | | N/A (single sector, carrier) | N/A (single sector, carrier) | 2.0Gbps | -| | | | | Total site | | N/A | N/A | 2.0Gbps | -| Small (FR2) | FR2 carriers | 1 | 3724 | 1117 | | N/A (single sector) | N/A (single sector) | 3.7Gbps | -| | | | | Total site | | N/A | N/A | 3.7Gbps | -| Medium | FR1 carriers | 3 | 2020 | 606 | | 2.0Gbps | 3.2Gbps | 6.1Gbps | -| | FR2 carriers | 3 | 7449 | 2234 | | 7.4Gbps | 11.9Gbps | 22.3Gbps | -| | | | | Total site | | 9.5Gbps | 15.2Gbps | 28.4Gbps | -| Large | FR1 carriers | 3 | 8078 | 2424 | | 8.1Gbps | 12.0Gbps | 24.2Gbps | -| | FR2 carriers | 3 | 14898 | 4470 | | 14.9Gbps | 23.8Gbps | 44.6Gbps | -| | | | | Total site | | 23.0Gbps | 36.8Gbps | 68.9Gbps | - -**Table 13: Last mile provisioning for 5G Backhaul (peak, lower and conservative bound)** - -Notes: - -- 1) In this example small sites are single sector, single 5G carrier sites. With additional carriers (4G or 5G) then a statistical gain can be achieved. -- 2) Medium and large sites are 3 sector, multi-carrier 5G sites. -- 3) Access circuit dimensioning only accounts for 5G services. 2G, 3G, 4G also needs to be considered as well. (discussed in more detail later). - -- 4) Busy time mean is taken as 30% of peak quiet time rate for a sector. This number has been picked antidotally through discussions with an LTE MNO. There is on-going discussion whether this ratio will apply to a 5G NR implementations as the ratio between quiet time peak rate and busy time mean rate may change. -- 5) There is on-going discussion in the industry about whether these formula for LTE provisioning will apply in the 5G NR access circuits. -- 6) In the case of point-point last mile access technologies, the values in the table can be taken per cell. In the case of point-multipoint access technologies using a shared medium (e.g.; PON, DOCSIS), the last mile itself already performs a level of aggregation between multiple cells, and section 10.2.3.2 applies. - -#### 11.2.4.2 Pre-aggregation and aggregation transport dimensioning - -If the transport technology and the network design enable statistical multiplexing, then the initial provisioning for Backhaul in the “pre-aggregation” and the “aggregation” segments of the transport network is based on predicting the level of statistical multiplexing. This will be based on network usage, network topology, levels of aggregation at different layers and usage / traffic correlation between adjacent cell sites. - -A similar initial provisioning approach could be taken as outlined by NGMA in “Guidelines for LTE Backhaul Traffic Estimation” [72] as discussed in previous section. However, when looking at aggregated Backhaul traffic then more emphasis needs to be placed on mean busy time rates than peak rates and mean busy time rates need to be calculated across multiple cell sites not across a single site (in most situations this will push the value down). - -Longer term provisioning will be based on collecting accurate traffic matrixes at the transport layer, demand level modelling and developing capacity plans rule. - -### 11.2.5 C-RAN Backhaul dimensioning - -In C-RAN architectures the access or last mile segment of the transport is not part of the Backhaul network. In these environments Backhaul dimensioning and capacity planning will be a function of the number of DUs each CU aggregates and where the CUs and UPF/UPFs resides in relation to each other and their overall position in the transport infrastructure. - -### 11.2.6 Midhaul dimension - -The Midhaul RAN component is only present in C-RAN architectures Figure 6 shows two deployments of Midhaul. In the top case the O-RU, O-DU and O-CU reside as discrete entities and at different levels of the transport network. In this case the Midhaul does not span the access portion of the network. Similar considerations as outlined in C-RAN Backhaul dimensioning can be used. - -In the lower case the O-RU and O-DU are co-located in the cell site and the Midhaul runs from the cell site, across the access infrastructure to the O-CU which is located higher up in the transport network. Similar techniques as outlined in D-RAN Backhaul dimensioning can be used. - -## 11.3 Backhaul and Midhaul latency - -Previous 3GPP generations aimed at voice and basic data services. In these scenarios' user plane one-way delay between the UE and the application could be multiple 10s of milliseconds, even reaching the low hundreds of milliseconds. These figures are the delay from the UE to the destination "Application Function". - -In a 5G RAN infrastructure this is made up of: - -*Overall one-way delay = UE delay + Radio air interface delay + FH/MH/BH transport networking delay + Radio component delays (DU, CU if used) + gateway delay + GiLAN transport network delay* - -5G introduces support for different service types (eMBB, URLLC and mMTC) and aims to cover a wide range of vertical markets, such IoT, industrial and automobile. Different services and verticals have different latency requirements, some extremely tight such as industrial motion control applications while others, such as some of IoT applications very relaxed. - -As an example, in the latest TR 22.804[85] the lowest maximum latency requirement for deterministic communication service is defined as 0.5ms for small industrial environments (50 m x 10 m x 10 m) with small packet sizes for motion control. A higher maximum latency of 500ms is given for periodic communication for standard mobile robot operation and communication services for CCTV surveillance cameras in mass rail transit with defined speeds of movement for each UE (UE speed < 50 km/h for mobile robots and $\leq 160$ km/h in urban environments). - -In scenarios where low one-way latency is required then the Midhaul and Backhaul networks will need to be designed to accommodate these requirements. As the latency requirements become tighter the following needs to be considered. - -- 1) Proximity and physical path between the UE and AF -- 2) Siting of gateway and AFs in relation to each other -- 3) Delay characteristics of the physical media -- 4) Delay characteristics of the RAN components (radio, DU, CU) -- 5) Number of physical hops and delay characteristics of the switching equipment -- 6) Whether the network is a public 5G or private 5G infrastructure. - -Figure 3 illustrates how adapting the RAN architecture and placement of RAN and "Application Function" (AFs) components can change the end-to-end latency characteristics of overall 5G infrastructure. - -1 - -# --- 12 Transport operability - -2 - -3 - -4 - -5 - -6 - -7 - -8 - -9 - -This section concerns transport requirements to ease operability of the transport. This section includes a first sub-section about transport system requirements, a second about transceiver and port monitoring and identification of the transport equipment, a third sub-section about power saving and energy efficiency. A last sub-section concerns an optional additional interface dedicated to remote monitoring of antenna site operation. - -10 - -## 12.1 Operational transport requirements - -11 - -### 12.1.1 Transport equipment at antenna site - -12 - -It is highly desirable from the network operation perspective to manage a network transport system, i.e., the equipment at the hub site together with the equipment at the antenna site, as a single entity. - -13 - -In that sense, it is desirable that the equipment at the antenna site is managed via the equipment at hub site whenever possible. Therefore, transport equipment shall support real-time management and control functions of antenna site equipment by the hub site equipment. - -14 - -15 - -16 - -17 - -18 - -### 12.1.2 Dual manage transport equipment at antenna site - -19 - -The transport equipment at the antenna site shall optionally support collaborative management partition between the dedicated management by the transport equipment at hub site and also other configuration mechanisms. - -20 - -21 - -22 - -23 - -### 12.1.3 Supervision - -24 - -It is important to take care of operational expenditure dedicated to the medium of the transport and related equipment. The goal of supervision is to reduce the operational expenditure of the transport systems, without significantly increasing the capital expenditure by including as much test and diagnostic capability as possible. Naturally, this should be achieved without compromising the available bandwidth for services, i.e., test and diagnostics must be non-service affecting. - -25 - -26 - -27 - -28 - -29 - -The ability to reliably differentiate between optical medium and electrical faults at the equipment and establish if the faults are in the optical medium or in the electronics is a key operator requirement. - -30 - -31 - -Error inference can usually be made from the presence (i.e., power or equipment failure), or absence (i.e., fibre failure), of the Dying Gasp alarm. Several key points for the supervision can be summarized as follows: - -32 - -33 - -- optical medium monitoring/checking: Monitoring and on-demand checking the condition of optical medium independently from a transport system is important to differentiate optical medium failures from transport system failures. It is desirable that such monitoring and checking be available regardless of whether the transport equipment antenna site is in service or even connected. Several implementations could be proposed. Optical monitoring solution is proposed by ITU-T G.697 to detect anomalies, defects, degradation and fault affecting the quality of the optical transport. Another solution is to use an optical time domain reflectometer (OTDR) which is a powerful tool for diagnosing such faults in the optical medium. Power meter and light source can also be used to aid in this monitoring process. Several demarcation devices are under research for further improving the optical medium monitoring and checking. -- transport system would benefit from an ability to automatically and autonomously detect and locate optical medium fault (optical medium segments : patch panel at the hub or antenna site, optical fiber cable in ducts or on the poles,..). -- End-to-end performance monitoring up to the Ethernet layer: End-to-end performance monitoring enables operators to diagnose and register where traffic may have been dropped or throttled. Higher layer tools, such as Ethernet performance monitoring, need to support the capability monitoring and verification of ingress and egress traffic flows in transport network elements. -- Proactive versus reactive repair: transport systems with their monitoring and control systems will allow operators to decide on the utilization of proactive or reactive fault repairs in most fault cases. It is of course up to the operators to decide on how to use transport status reports. -- For instance, key-performance-indicators related to the optical transport supervision could be made available to an orchestrator, higher in the network, through an abstraction of the optical devices through software-defined networking. - -### 12.1.4 Rogue behaviour and its mitigation in access transport segment - -This clause is largely concerned with rogue behaviour between FTTH (Fiber To The Home) based on PON (Passive Optical Network) technologies and Xhaul access transport operations in last mile optical fiber infrastructure. The transport equipment at the antenna site must be initially disabled in order to avoid disturbing PON system in case of miss-connection in the optical fiber enclosure. The antenna site transport equipment shall enable the transmitter to enter a handshaking process with hub equipment only after confirming that the frame structure and/or the line coding of the received downstream signal are matched with those the antenna site equipment complies with. This confirmation shall be done with both hub and antenna site equipment. - -The Xhaul transport equipment must support silent start operation to prevent bidirectional physical layer interfering with FTTH based on point to multi-point. The silent start means that the upstream physical layer doesn't transmit unless a valid downstream signal is received. - -### 12.1.5 Transport availability - -Operators need to determine the most resilient transport architecture for their reliable mobile services. Transport system should include a range of cost-effective resilience options to obtain the targeted availability of mobile services. These resilience schemes should be options available on the transport scenarios for passive and active equipment. Different types of service and specific offerings will require different recovery speeds. These may range from a few microseconds, for critical services like motion control for factories of the future, up to the order of seconds or minutes for monitoring or - -remote control applications. Note that support for resilience options should not increase the cost of such systems if deployed without resilience options. - -The protection architecture should be considered as one of the means to enhance the reliability of the Xhaul transport. However, protection shall be considered as an optional mechanism because its implementation depends on the realization of economical systems. It is also likely that other methods are used, such as cooperative technologies, e.g., fixed (optical fiber) and radio (micro-wave) for backup for cost reasons. - -Combining protection mechanisms related to Xhaul transport interfaces and the optical fiber infrastructure should even be possible, provided that the switching time of the two mechanisms is compatible or configurable. The goal should be to recover the Xhauling service in less than the common 50 ms value used for protection. - -## 12.2 Transceiver and port monitoring and identification - -### 12.2.1 Transceiver digital diagnostic monitoring - -A digital diagnostic monitoring interface for optical transceivers is used to allow access to device operating parameters. As specified in SFF-8472 and SFF-8636, data is typically retrieved from the transceiver module in a memory map of an EEPROM. Such data must be available by the data plane. With QSFP and other advanced form factor transceivers, the optical links could be multi-wavelength (4xTx & 4xRx) and/or multi-fibers (MPO - Multifiber Parallel Optic). The antenna site and hub interface management must describe a management applicable to any kind and group of media lanes. The QSFP digital diagnostic (SFF-8636) describes such media lanes. - -### 12.2.2 Transceiver class of operation for bidirectional transmission - -A plurality of transceiver modules is used today and can define operational states for pluggable form factors (like SFP, SFP+, SFP28, XFP and QSFP, QSFP+, QSFP14, QSFP28, CFP, CFP2...). Each transceiver is associated with a unique interface name and port number value. - -Concerning fiber connectivity, in the last mile network (fixed access network to reach antenna) BiDi (BiDirectional - single singlemode fiber) transceiver is the preferred implementation to simplify operation (risk of mismatch...), reduce the cost and the dimensioning of fiber cable and reduce potential path delay asymmetry. - -The interoperability between transceiver at antenna site and hub is a must. Operations at antenna site and hub must support different timeline operation, refresh and other network operations requiring different purchasers of transceivers. In order to achieve this interoperability, working classes have to be clearly identified for the required transceivers. - -### 12.2.3 Transceiver class of operation for WDM transmission - -In order to save optical fiber, wavelength division multiplexing (WDM) could be proposed. It is already the case for high bit rate transceivers (ex. 100GBase interface) with multiple wavelength per stream and per fiber. In case that Xhaul transport uses WDM transmission, a single fiber operation - -1 (bidirectional multiple wavelength) will ease network operations. This single fiber operation concerns -2 the colorized transceiver plugged in transport equipment ports and thus sharing optical fiber -3 infrastructure. This single fiber operation is important for the last mile fiber infrastructure to reach -4 the antenna site. One optical fiber per stream could be also proposed. - -5 -6 The wavelength assignment per port could be static or tuneable. Auto-tuneable wavelength allocation -7 simplifies inventory management. Each wavelength channel is tuned thanks to an embedded control -8 channel. This control channel must be interoperable to ease network operations. Similar to previous -9 subsection, interoperability is a must for WDM operation and working classes (including optical -10 spectrum parameters) have to be clearly identified. - -###### 11 12 12.2.4 Port-ID to ease field operation - -13 In order to facilitate retrieval of the transport port identifier and other physical layer parameter -14 indicators (ex. Launched optical power) during field operation (installation, maintenance,...), a port- -15 ID could be tagged on the transport hub equipment. As an example, comparison of the locally -16 measured optical power and the launched optical power information inside the port-ID should give -17 operators a mean for measuring optical power budget. Optical monitoring and supervision parameters -18 could refer to ITU-T G.697 for WDM systems and ITU-T G.988 for access systems based on received -19 signal strength indicator of transceivers. - -###### 20 21 12.2.5 Eye safety - -22 Given the higher launched optical power that can be injected into the fibre by transport equipment, -23 both at the antenna and hub sites, all necessary mechanisms must be provided to insure that no eye -24 damage can be caused to the end users unaware of the risks, especially if fibre is terminated inside -25 public facilities (small cell). All transport equipment need to conform to eye safety classes. For access -26 transport segment, the equipment must conform to the class 1M at the hub and class 1 at the antenna -27 site defined in IEC 60825-2. - -###### 28 29 12.3 Power saving and energy efficiency - -30 Saving energy in telecommunications network systems has become an increasingly important concern -31 in the interest of reducing operators' operational expenses (OPEX) and the network's contribution to -32 greenhouse gases. The power saving mechanism could be applied to reduce power consumption either -33 continuously or during a time period. - -34 -35 Transport equipment need to achieve a power saving mechanism in coordination with CORE and -36 RAN equipment like O-CU, O-DU and O-RU. Coordination interface could be proposed to achieve -37 such mechanism. Antenna and hub equipment may provide the best network energy efficiency -38 experience combining both sleep periods approaches when the link is idle and line rate switching -39 according to the actual payload to be conveyed. For the latter case, it is essential to enable the -40 necessary logic to adapt the clock rate or number of active ports and wavelengths to the necessary -41 payload at border equipment. - -42 -43 In order to provide the most energy efficient transmission for variable traffic loads, antenna site and -44 hub equipment must have the ability to adapt to it. As an example, transport equipment must provide -45 a dynamic auto-negotiation of the Ethernet PHY line rate between antenna site and hub equipment -46 and this should be enabled among the plurality of Ethernet PHY line rates supported according to the - -1 actual payload. For multi-wavelength transport (or transceiver), the number of active wavelength pair - 2 could be adapted to support the required traffic. - -3 - 4 Because of the high clock quality requirements, and long recovery time of clock recovery circuitry, - 5 no phase drift will be permitted in the downstream direction when switching line rate. Also, such - 6 switching will have to be hitless, i.e., without any Ethernet packet loss whatsoever. - -###### 7 12.4 Remote monitoring antenna site operation - -8 The antenna tower site requires also a remote monitoring of sensors and actuator (collection of alarm, - 9 active action on site...) for environmental, power, tower light, building and facility. This remote - 10 operation requires a logical link with a master unit at the hub site or other remote site. This link could - 11 be based on Ethernet (Fast or GigaEthernet). This link should be considered by the transport system - 12 between antenna site and hub site. - -###### 14 12.5 Operability requirements - -15 Table 14 captures operability transport requirements. - -| Capability | Requirements | Notes | -|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------| -| Management | The transport equipment at the antenna site MAY be managed via the transport equipment at the hub site. | | -| Supervision | The transport equipment supervision MUST differentiate equipment and infrastructure faults. | | -| Rogue behaviour | For access network segment, the transport equipment at antenna site MUST support mechanism to avoid disturbing other network operations like silent start network function | This requirement allows to prevent jamming transmission on the FTTH networks in cases of unintentional connection. | -| Availability | Operator MAY choose to use resilience mechanism for transport equipment and infrastructure. | Technology solution to meet this requirement will be covered based on coordination with CORE and RAN equipment. | -| Transceiver | The transport equipment MUST provide the digital diagnostic data of transceivers. The interoperability between transceivers at antenna site and hub is a MUST. Operator MAY choose to select bidirectional (single fiber) to ease operation. In case of WDM transport equipment, operator MAY choose auto-tunable wavelength transceivers. | | -| Port ID | For antenna site operation, optical monitoring and supervision parameters MUST be supported for remote operations. | | - -| | | | -|--------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------| -| Eye safety | The transport equipment for access segment MUST be conform to the class 1M at the hub and class 1 at the antenna site defined in IEC 60825-2 | | -| Power saving energy efficiency | The transport equipment MUST be capable to support power saving mechanism. | Technology solution to meet this requirement will be covered based on coordination with CORE and RAN equipment. | - -1 -2 -3 -4 - -**Table 14: Operability transport requirements** - -# 13 Synchronization - -This chapter spells out synchronization requirements for fronthaul networks in alignment with WG CUS specification [74]. - -## 13.1 Frequency, Phase and Time Accuracy Requirements - -The following set of synchronization requirements have been identified as relevant for O-RAN: - -- Radio frame alignment (O-RU radio interface) - - Absolute sync to support TDD : relative 3μs between antennas is transformed into +/- 1.5μs with regarding to a common reference(e.g. GNSS) - - Relative sync to support radio coordination functions. Most stringent requirement between “non-collocated” O-RUs is 260 ns TAE. Other applicable requirements are 3μs (to support TDD networks). In case of co-located O-RUs 130 ns may also apply. -- Control of the latency between O-DU and O-RU (section 2.3 from O-RAN CUS specification): - - The relative time error between the O-DU and O-RU shall be within a limit of 3μs (±1.5μs). This requirement applies whether the O-DU is on the synchronization path towards O-RU or not. -- O-DU to O-DU synchronization for Radio Frames handling (e.g., SFN generation): - - Expected in the ms range -- Frequency sync of the radio signal - - Frequency accuracy/stability of the O-RU radio interface (50 / 100 ppb) -- O-CU to O-DU synchronization - - No stringent requirement identified (alarm timestamping is one possible use case) - -Further details are provided below for some of these requirements. - The frequency synchronization requirements are summarized in Table 15. - -| Application/Technology | Frequency Accuracy Requirements | Specification | -|------------------------|---------------------------------|---------------------------------------------| -| LTE Wide Area BS | ±0.05 ppm | 3GPP TS 36.104 (01/2020) [75] section 6.5.1 | -| LTE Medium Range BS | ±0.1 ppm | 3GPP TS 36.104 (01/2020)[75] section 6.5.1 | -| LTE Local Area BS | ±0.1 ppm | 3GPP TS 36.104 (01/2020) [75] section 6.5.1 | -| LTE Home BS | ±0.25 ppm | 3GPP TS 36.104 (01/2020) [75] section 6.5.1 | -| NR Wide Area BS | ±0.05 ppm | 3GPP TS 38.104 (01/2020) [76] section 6.5.1 | -| NR Medium Range BS | ±0.1 ppm | 3GPP TS 38.104 (01/2020) [76] section 6.5.1 | - -| | | | -|------------------|----------|---------------------------------------------| -| NR Local Area BS | ±0.1 ppm | 3GPP TS 38.104 (01/2020) [76] section 6.5.1 | -|------------------|----------|---------------------------------------------| - -**Table 15: Frequency Accuracy Requirements** - -### **Time/Phase synchronization requirements:** - -The requirements for Time/Phase synchronization for LTE features and 5G features covered in WG4 CUS specification [74] can be referenced as described below: - -- Table 9-1: LTE features with time alignment error requirement at the air interface -- Table 9-2: 5G features with time alignment error requirement - -## 13.2 Error Budget Allocation Requirements - -In case of LLS-C1 and LLS-C2 the frequency error budget allocation can be based on Table 9-3 of ORAN-WG4.CUS.0-v03.00 (04/2020) [74]. - -In case of LLS-C3 the frequency error budget allocation is provided in Table 16 and is based on Table 9-4 of ORAN-WG4.CUS.0-v03.00 (04/2020) [74]. - -| | | -|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------| -| Timing Reference | O-RAN transport network contribution limit (LLS-C3) | -| PRTC | MTIE per ITU-T G.8272/Y.1367 (11/2018) [82] clause 6.2 | -| ePRTC | MTIE per ITU-T G.8272.1/ Y.1367.1 (08/2019) [79] clause 6.2 | -| PRTC in holdover | FFS (Note 1) | -| ePRTC in holdover | <100ns for 14 days per G.8272.1 clause 8.2 | -| Note 1: PRTC holdover is for further study. As an example, G.8271.1 (08/2019) Appendix V.3 Failure scenarios, refers to a holdover failure scenario of 400 ns for a short interruption (e.g. 5 min) of GNSS. This could be extended to longer periods (e.g. several hours or longer) depending on choice of oscillator and system design. | | - -**Table 16: Wander generation requirement for PRTC/ePRTC** - -ITU-T G.8272/Y.1367 (11/2018): **Timing characteristics of primary reference time clocks** - - -ITU-T G.8272.1/Y.1367.1 (11/2016) Amendment 2 (08/2019): **Timing characteristics of enhanced primary reference time clocks** - - -#### **ITU-T G.8271.1/Y.1366 (2017) Amendment 2 (08/2019) : Network limits for time synchronization in packet networks** - - - -For the case of LLS-C1 and LLS-C2 the time error budget allocation is summarized Table 17 and is based on Table 9-3 of ORAN-WG4.CUS.0-v03.00 (04/2020) [74]. Two types of O-RU are considered in the CUS specification: *Enhanced* O-RU with $|TE| < 35$ ns and *Regular* O-RU with $|TE| < 80$ ns. - -The below table considers a time error budget allocation model from Xhaul transport point of view from end to end Grandmaster to O-RU. Here it is simplified to show the transport network budget based on different PRTC/GM and type of O-RU selected for the entire Xhaul network. - -| Time error budget allocation (LLS-C1/C2) | | | | -|---------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------|-----------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------| -| Timing Reference | O-RAN transport network contribution limit (NOTE2) | O-RU | Air interface target | -| No relative $ TE $ contribution by PRTC/T-GM since PRTC/T-GM is common PTP and SyncE master to all co-operated O-RU | Relative $ TE_L \leq 60$ ns
Between 2 =-RUs UNI
Note 1
Note 2 | Enhanced O-RU

NOTE- regular O-RU can't meet this requirement | 130ns $ TAE $ between antennas

For NR Intra-band contiguous carrier aggregation (FR2) | -| | Relative $ TE_L \leq 190$ ns
Between 2 O-RUs UNI
Note 1
Note 2 | Enhanced O-RU | 260ns TAE between antennas

For NR Intra-band contiguous carrier aggregation (FR1) | -| | Relative $ TE_L \leq 100$ ns
Between 2 O-RUs UNI
Note 1
Note 2 | Regular O-RU (Note 4) | | -| Absolute $ TE \leq 100$ ns
PRTC-A/T-GM spec per ITU-T G.8272 (03/2020) [78] | Network $ TE_L \leq 1365$ ns
• Between T-GM port and O-RU UNI | Enhanced O-RU | 3 $\mu$ s TAE between antennas (TDD, NR Inter-band carrier aggregation or NR Intra-band non-contiguous carrier aggregation) | -| | Network $ TE_L \leq 1320$ ns
• Between T-GM port and O-RU UNI | Regular O-RU | | - -| | | | -|-------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------|----------------------| -| Absolute $ TE \leq 30\text{ns}$
ePRTC/T-GM
spec per ITU-T
G.8272.1
(08/2019) [79] | Network $ TE_L \leq 1435\text{ns}$
• Between T-GM port and O-RU
UNI | Enhanced O-RU | -| | Network $ TE_L \leq 1390\text{ns}$
• Between T-GM port and O-RU
UNI | Regular O-RU | -| Absolute $ TE \leq 40\text{ns}$
PRTC-B/T-GM
spec per ITU-T
G.8272.1
(08/2019) [79] | Network $ TE_L \leq 1425\text{ns}$
• Between T-GM port and O-RU
UNI | Enhanced O-RU | -| | Network $ TE_L \leq 1380\text{ns}$
• Between T-GM port and O-RU
UNI | Regular O-RU | - -**Table 17: Time Error Budget Allocation** - -Note 1 – Further details are being defined by ITU-T. - -Note 2 – Examples for allocation of time error are provided in Section 13.4. - -Note 3 – In general the table-16 describes the time error allocation break out for network versus end device requirement. The simple breakout model can be described as - -$$\text{GM/GNSS} + \text{Network} + \text{End device (O-RU)} = \text{Total budget.}$$ - -Note 4 – Regular O-RU refers to Class-B O-RU as per ORAN-WG4.CUS.0-v03.00 (04/2020) [74]. - -The time error budget allocation for the case of LLS-C3 is specified by ITU-T G.8271.1 (03/2020) [77]. - -## 13.3 Synchronization solution requirements - -Successful synchronization deployment depends on many factors. A solution architecture document for timing and synchronization will cover more in detail the following aspects: - -- Building blocks of network based synchronization -- Timing profiles -- Synchronization time error budgeting models -- Synchronization network models - factors to be considered -- Other applications and sync model -- Synchronization network monitoring and management models -- Best practices and network models - -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 - -## 13.4 Summary - -In summary, the use of Precision Timing Protocol (PTP) has been in use for many network iterations. With the migration to NR and eCPRI, it will become more prevalent and have an extended reach in mobility networks, all the way to the O-RU. This will require a PTP profile based on ITU-T G.8275.1 (03/2020) [80] with Synchronous Ethernet, in the Fronthaul, from O-DU to O-RU (note: for the O-RU it is optional the use of SyncE). The Technical Solutions Document will further describe options for the enhancing the network synchronization performance and reliability. - -Finally, Figure 15 to Figure 17 provide some examples of absolute and relative time error requirements as diagrams for LLS-C1 and LLS-C2. - -Config LLS-C3 is being studied in ITU-T (planned to be covered in ITU-T G.8271.1 (03/2020) [77]) - -![Figure 15: Example of Absolute vs Relative Requirements (Config LLS-C1 Option A, where T-GM is embedded in O-DU). The diagram shows two synchronization paths from a distribution site (A) to a remote site (C). Path 1 (top) uses PTP/SyncE from an O-DU's T-GM to enhanced O-RUs with T-TSCs. Path 2 (bottom) uses PRTC from an O-DU to regular O-RUs with T-TSCs. Various time error (TE) budgets are shown for different frequency bands (FR1, FR2) and RU types (enhanced, regular).](802707b774f2d2973b49cea2020e8453_img.jpg) - -Figure is for illustrative purpose and does not provide deployment guidance. - -PTP/SyncE path - -1PPS + ToD - -distribution site (A) - -O-DU - -T-GM - -PRTC - -remote site (C) - -O-RU (enhanced) - -T-TSC (|TE| ≤ 35 ns) - -O-RU (enhanced) - -T-TSC (|TE| ≤ 35 ns) - -ITUT G.8271 - -TAE - -(FR2) (FR1) ±30...95 ns - -(FR2) (FR1) ±65...130 ns - -(RE/eRE) 3000 ns - -distribution site (A) - -O-DU - -PRTC - -T-GM - -remote site (C) - -O-RU (regular) - -T-TSC (|TE| ≤ 80 ns) - -O-RU (regular) - -T-TSC (|TE| ≤ 80 ns) - -(FR1) 260 ns - -(FR1) ±50 ns - -(FR1) ±130 ns - -(rO-RU) (eO-RU) ±1420...1465 ns - -(rO-RU)(eO-RU) ±1500 ns - -(FR1): NR intra-band continuous carrier aggregation in FR1 -(FR2): NR intra-band continuous carrier aggregation in FR2 (co-located RUs only) -(eO-RE): enhanced O-RU -(rO-RU): regular O-RU - -PRTC A: |TE| ≤ 100 ns -PRTC B: |TE| ≤ 40 ns - -The budgeting examples are based on the conservative assumption of linear accumulation between the 2 branches relevant to the TAE requirement. - -Figure 15: Example of Absolute vs Relative Requirements (Config LLS-C1 Option A, where T-GM is embedded in O-DU). The diagram shows two synchronization paths from a distribution site (A) to a remote site (C). Path 1 (top) uses PTP/SyncE from an O-DU's T-GM to enhanced O-RUs with T-TSCs. Path 2 (bottom) uses PRTC from an O-DU to regular O-RUs with T-TSCs. Various time error (TE) budgets are shown for different frequency bands (FR1, FR2) and RU types (enhanced, regular). - -14 -15 -16 -17 - -**Figure 15: Example of Absolute vs Relative Requirements (Config LLS-C1 Option A, where T-GM is embedded in O-DU)** - -![Figure 16: Example of Absolute vs Relative Requirements (Config LLS-C1 Option B, where T-GM is directly connected to O-DU).](b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg) - -This diagram illustrates the timing budget for a radio network where the Timing Source (T-GM) is directly connected to the O-DU. The diagram is divided into five vertical sections: A (Timing Source), B (Distribution), C (Remote Site), D (Timing Budget), and E (ITU-T G.8271). - -- Section A:** Shows the PRTC/ePRTC T-GM with parameters: PRTCA (ITEI ≤ 100 ns), PRTCB (ITEI ≤ 40 ns), and ePRTC (ITEI ≤ 30 ns). -- Section B:** Shows two distribution paths. The top path goes through a 'nearest common BC' (O-DU with integrated BC or IWF). The bottom path goes through another 'distribution site' (O-DU with integrated BC or IWF). A note indicates that budgeting examples are based on a conservative assumption of linear accumulation between the two branches relevant to the TAE requirement. -- Section C:** Shows two remote site configurations. The top configuration has 'O-RU (enhanced)' units with T-TSC (ITEI ≤ 35 ns). The bottom configuration has 'O-RU (regular)' units with T-TSC (ITEI ≤ 80 ns). -- Section D:** Shows timing budget values: - - ±30...100 ns from A to B. - - ±1100 ns from A to the first distribution site. - - ±1420...1465 ns for (rO-RU) (eO-RU). - - ±1500 ns for (rO-RU)/(eO-RU). - - FR1: ±50 ns and ±130 ns. - - FR2: ±30...95 ns and ±65...130 ns. -- Section E:** Shows ITU-T G.8271 parameters: TAE (3000 ns), (RE/eRE) (3000 ns), (FR1) (260 ns), and (FR2) (130-260 ns). - -A legend on the right defines: (FR1): NR intra-band continuous carrier aggregation in FR1; (FR2): NR intra-band continuous carrier aggregation in FR2 (co-located RUs only); (eO-RE): enhanced O-RU; (rO-RU): regular O-RU. - -Figure 16: Example of Absolute vs Relative Requirements (Config LLS-C1 Option B, where T-GM is directly connected to O-DU). - -Figure 16: Example of Absolute vs Relative Requirements (Config LLS-C1 Option B, where T-GM is directly connected to O-DU) - -![Figure 17: Example of Absolute vs Relative Requirements (Config LLS-C2 Option A, where O-DU is nearest common T-BC).](50ef8602c7c9edd2da0e2133e772c2a2_img.jpg) - -This diagram illustrates the timing budget for a radio network where the O-DU is the nearest common Timing Source (T-BC). The diagram is divided into five vertical sections: A (Timing Source), B (Distribution), C (Remote Site), D (Timing Budget), and E (ITU-T G.8271). - -- Section A:** Shows the PRTC/ePRTC T-GM with parameters: PRTCA (ITEI ≤ 100 ns), PRTCB (ITEI ≤ 40 ns), and ePRTC (ITEI ≤ 30 ns). -- Section B:** Shows two distribution paths. The top path goes from the T-GM through a cloud of '0 or more T-BCs/T-TCs\*' to a 'distribution site' (O-DU with integrated BC or IWF). The bottom path goes from the T-GM through a cloud of '0 or more T-BCs/T-TCs\*' to another 'distribution site' (O-DU with integrated BC or IWF). A note indicates that budgeting examples are based on a conservative assumption of linear accumulation between the two branches relevant to the TAE requirement. -- Section C:** Shows two remote site configurations. The top configuration has 'O-RU (enhanced)' units with T-TSC (ITEI ≤ 35 ns). The bottom configuration has 'O-RU (regular)' units with T-TSC (ITEI ≤ 80 ns). -- Section D:** Shows timing budget values: - - ±30...100 ns from A to the first cloud. - - ±1100 ns from A to the first distribution site. - - ±1420...1465 ns for (rO-RU) (eO-RU). - - ±1500 ns for (rO-RU)/(eO-RU). - - FR1: ±50 ns and ±130 ns. - - FR2: ±30...95 ns and ±65...130 ns. -- Section E:** Shows ITU-T G.8271 parameters: TAE (3000 ns), (RE/eRE) (3000 ns), (FR1) (260 ns), and (FR2) (130-260 ns). - -A legend on the right defines: (FR1): NR intra-band continuous carrier aggregation in FR1; (FR2): NR intra-band continuous carrier aggregation in FR2 (co-located RUs only); (eO-RE): enhanced O-RU; (rO-RU): regular O-RU. - -Figure 17: Example of Absolute vs Relative Requirements (Config LLS-C2 Option A, where O-DU is nearest common T-BC). - -Figure 17: Example of Absolute vs Relative Requirements (Config LLS-C2 Option A, where O-DU is nearest common T-BC) - -Note: All three figures (14, 15 and 16), the T-TSC embedded in remote site and T-BC embedded in O-DU need not to be compliance to ITU-T G.8273.2, 03/2020 [81] specification. Refer the WG4 CUS spec [74] for additional details on this. - -# 14 Legacy Requirements - -Legacy radio equipment plays a role in the 5G network evolution and must be supported in the new network implementations. This means support of the Common Public Radio Interface (CPRI) must be taken into consideration as it is the interface between radios and BBU. As stated in the Scope section, legacy transport will follow 3GPP split Option 8, the PHY-RF split. This option allows to separate the RF and the PHY layer. In addition, it allows for centralization of processes at all protocol layer levels, resulting in very tight coordination of the RAN and provides efficient support of functions such as CoMP, MIMO, and load balancing. - -CPRI is a digitized and serial interface that establishes a connection between BBU and an RRH. The BBU contains the radio functions of the digital baseband domain and the radio contains the analog radio frequency functions. CPRI supports three information flows: - -1. IQ Data – user plane information in the form of In-Phase and Quadrature modulation data -2. C&M Data – Control and Management data which is exchanged between the “REC” and “RE” -3. Synchronization Data – used for CPRI frame and time alignment - -The three CPRI information flows are supported separately with a flow of frames supporting the IQ data information flow and a flow supporting the C&M data. Synchronization is provided separately. - -The Table 18 below breaks out the different requirements for each flow: - -| Plane/CPRI Flow | Latency (RTT) | Frame Loss Ratio | Traffic Type Repartion | Traffic Pattern | Traffic QoS | -|-----------------|---------------|------------------|------------------------|-------------------|-------------| -| IQ Data | 125 µs | 10 -7 | >90% | Constant Bit Rate | High | -| C&M Data | n/a | 10 -6 | <10% | Burst | Best Effort | -| Synchronization | n/a | n/a | n/a | n/a | Very High | - -**Table 18: CPRI Flow Requirements** - -For legacy LTE radios, the Fronthaul bandwidth reference for CPRI traffic is classified in Table 19 - -| | number of sectors | Total CBW (MHz) | MIMO layers | ABW (MHz) | FH BW (Gbps) | -|--------|-------------------|-----------------|-------------|-----------|--------------| -| Small | 1 | 40 | 4 | 160 | 10 | -| Medium | 3 | 40 | 4 | 480 | 29 | -| Large | 3 | 80 | 4 | 960 | 59 | - -**Table 19: Fronthaul Bandwidth Reference for LTE traffic in CPRI** - -For CPRI rate calculation associated with option 8 split, - -$$FH\ BW = 2 \cdot 10^{-9} \cdot 1.25 \cdot f_s \cdot N_{bit} \cdot N_{ant} \text{ (Gbps)}$$ - -Where - -- $f_s$ is the sample frequency, and $f_s = 30.72$ MHz for 20MHz LTE carriers -- 1.25 is the increasing factor due to the overhead from 8b/10b line code. When 66b/64b line code is used, this factor should be changed to $66/64=1.03125$ -- $\frac{16}{15}$ is the CPRI control word overhead -- $N_{bit}$ is the bitwidth of the radio I/Q sample -- $N_{ant}$ is the number of antennas - -Unlike eCPRI, the CPRI traffic will be constant regardless the user data payload. If CPRI interface is not efficiently used (such as empty AxCs in the CPRI Basic Frame) the required Fronthaul bandwidth will be expected higher. - -For co-existence of the 5G NR and LTE radios in the same cell site, both eCPRI and CPRI traffic should be considered. Combining the results given in section 7.2 for eCPRI traffic, Table 20 gives the total Fronthaul bandwidth reference with both eCPRI and CPRI traffic included. - -| | CPRI | | eCPRI | | Total FH BW (Gbps) | -|--------|------|-------|-------|-------|--------------------| -| | ABW | FH BW | ABW | FH BW | | -| Small | 160 | 10 | 800 | 15 | 24 | -| Medium | 480 | 29 | 6000 | 110 | 140 | -| Large | 960 | 59 | 14400 | 265 | 324 | - -**Table 20: Fronthaul Bandwidth Reference for eCPRI + CPRI** - -For specific RAN equipment implementation, the RAN split point may not be O-RAN option7-2x. So, different RAN vendors have different results due to different implementation details and parameter settings. Taking the following split choice as an example: - -- Downlink User Plane: option 7-3, -- Uplink User Plane: Between “Resource Element De-Mapping” and “Channel estimation”; - -Table 21 provides the bandwidth calculation based on the split point shown above and with both eCPRI and CPRI traffic included. - -| | Number of sectors | CBW (MHz) | MIMO Layers | $\mu$ | ABW (MHz) | Frequency Band | Fronthaul Interface | Air Interface | FH BW (GHz) | Example FH Interface | -|-----------|-------------------|-----------|-------------|-------|-----------|----------------|---------------------|---------------|---------------|----------------------| -| Carrier 1 | 3 | 100 | 16 | 1 | 4800 | 2.6GHz | eCPRI | NR | 68.4(22.8*3) | 3*25G eCPRI | -| Carrier 2 | 3 | 60 | 16 | 1 | 2880 | 2.6GHz | eCPRI | NR | 42.2(14.06*3) | 3*25G eCPRI | - -**Table 21: Large site configuration, Sub 6 NR(massive MIMO)** - -1 - -2 - -# Appendix A Fronthaul Bandwidth Calculation - -3 -4 -5 -6 -7 -8 - -This section provides more details for the bandwidth calculation in 7.2 with site carrier configuration examples. Different types of deployments can occur in practice; single-RAT (e.g. 5G fronthaul) versus multi-RAT (e.g. LTE CPRI + 5G fronthaul), pure front- or mid- or backhaul versus a mix of different of X-haul cases. The examples in Table 22 to Table 26 illustrate different cases and different combinations thereof. - -9 -10 -11 - -Given below are the parameter settings in evaluating the Fronthaul bandwidth via the equation provided in section 7.2 for 7-2x split based eCPRI: - -12 -13 -14 -15 - -- $N_{PRB} = 264, \mu = 3$ for 400MHz mmWave carriers [3GPP 38.101] -- $N_{PRB} = 273, \mu = 1$ for 100MHz Sub 6 carriers [3GPP 38.101] -- $N_{mantissa} = 9$ -- $N_{exponent} = 4$ - -16 -17 -18 -19 - -With about settings, a 400MHz mmWave carrier with 2 layer MIMO is found to have 14.96Gbps FH BW and 100MHz Sub 6 carrier with 4 layer MIMO being 7.74Gbps. - -20 -21 - -According to the BW calculation equation provided in section 13 the parameters are set as - -22 -23 -24 - -- $N_{bit}=15$ -- $f_s = 30.72 \text{ MHz}$ - -25 -26 -27 - -Thus for a 20MHz LTE carrier with 2 antenna branches, the CPRI rate is found to be 2.46 Gbps, which is the typical CPRI-3 line rate. - -28 -29 -30 -31 -32 -33 -34 -35 -36 - -The carrier setting examples are illustrated in Table 22 to Table 26, for small, medium, and large scenarios respectively. The Fronthaul BW for each carrier is aggregated over all sectors and is reported in FH BW column. For the purpose of reference, the optical interfaces to the radios for all sectors are provided at last Colum. Note that these FH interfaces are only exemplary. Actual interface configuration may vary depending on the radio designs from different vendors. For example, if carrier 2 and 3 is cascaded, the resulting transport can be carried by a CPRI 7 link. - -Small Examples: - -| | number of sectors | CBW (MHz) | MIMO Layers | $\mu$ | ABW (MHz) | Frequency Band | Fronthaul Interface | Air Interface | FH BW (Gbps) | Example FH Interface | -|-----------|-------------------|-----------|-------------|-------|-----------|----------------|---------------------|---------------|--------------|----------------------| -| carrier 1 | 1 | 400 | 2 | 3 | 800 | 39GHz | eCPRI | NR | 14.57 | 1x25G eCPRI | -| carrier 2 | 1 | 20 | 4 | | 80 | B-2 | CPRI | LTE | 4.92 | 1xCPRI5 | -| carrier 3 | 1 | 20 | 4 | | 80 | B-4 | CPRI | LTE | 4.92 | 1xCPRI5 | -| Total | | | | | | | | | | 24.40 | - -**Table 22: Small site configuration, LTE + mmWave NR** - -37 -38 -39 -40 -41 - -| | number of sectors | CBW (MHz) | MIMO Layers | $\mu$ | ABW (MHz) | Frequency Band | Fronthaul Interface | Air Interface | FH BW (Gbps) | Example FH Interface | -|-----------|-------------------|-----------|-------------|-------|-----------|----------------|---------------------|---------------|--------------|----------------------| -| carrier 1 | 1 | 100 | 4 | 1 | 400 | C-band | eCPRI | NR | 7.5 | 1x10G eCPRI | -| carrier 2 | 1 | 20 | 4 | | 80 | B-2 | CPRI | LTE | 4.9 | 1xCPRI5 | -| carrier 3 | 1 | 20 | 4 | | 80 | B-4 | CPRI | LTE | 4.9 | 1xCPRI5 | -| Total | | | | | | | | | | 17.4 | - -**Table 23: Small site configuration, LTE+Sub 6 NR:** - -Medium Examples: - -| | number of sectors | CBW (MHz) | MIMO Layers | $\mu$ | ABW (MHz) | Frequency Band | Fronthaul Interface | Air Interface | FH BW (Gbps) | Example FH Interface | -|-----------|-------------------|-----------|-------------|-------|-----------|----------------|---------------------|---------------|--------------|----------------------| -| carrier 1 | 3 | 400 | 4 | 3 | 4800 | 39GHz | eCPRI | NR | 87.4 | 6x25G eCPRI | -| carrier 2 | 3 | 100 | 4 | 1 | 1200 | C-band | eCPRI | NR | 22.6 | 3x10G eCPRI | -| carrier 3 | 3 | 20 | 4 | | 240 | B-2 | CPRI | LTE | 14.7 | 3xCPRI5 | -| carrier 4 | 3 | 20 | 4 | | 240 | B-4 | CPRI | LTE | 14.7 | 3xCPRI5 | -| Total | | | | | | | | | | 139.5 | - -**Table 24: Medium site configuration, LTE + Sub 6 NR + mmWave NR** - -| | number of sectors | CBW (MHz) | MIMO Layers | $\mu$ | ABW (MHz) | Frequency Band | Fronthaul Interface | Air Interface | FH BW (Gbps) | Example FH Interface | -|-----------|-------------------|-----------|-------------|-------|-----------|----------------|---------------------|---------------|--------------|----------------------| -| carrier 1 | 3 | 100 | 16 | 1 | 4800 | C-Band | eCPRI | NR | 90.4 | 6x25G eCPRI | -| carrier 2 | 3 | 20 | 4 | | 240 | B-2 | CPRI | LTE | 14.7 | 3xCPRI5 | -| carrier 3 | 3 | 20 | 4 | | 240 | B-4 | CPRI | LTE | 14.7 | 3xCPRI5 | -| Total | | | | | | | | | | 119.9 | - -**Table 25: Medium site configuration, LTE + Sub 6 NR (massive MIMO)** - -Large Example: - -| | number of sectors | CBW (MHz) | MIMO Layers | $\mu$ | ABW (MHz) | Frequency Band | Fronthaul Interface | Air Interface | FH BW (Gbps) | Example FH Interface | -|-----------|-------------------|-----------|-------------|-------|-----------|----------------|---------------------|---------------|--------------|----------------------| -| carrier 1 | 3 | 400 | 4 | 3 | 4800 | 39GHz | eCPRI | NR | 87.4 | 6x25G eCPRI | -| carrier 2 | 3 | 400 | 4 | 3 | 4800 | 24GHz | eCPRI | NR | 87.4 | 6x25G eCPRI | -| carrier 3 | 3 | 100 | 16 | 1 | 4800 | C-band | eCPRI | NR | 90.4 | 6x25G eCPRI | -| carrier 4 | 3 | 20 | 4 | | 240 | B-2 | CPRI | LTE | 14.7 | 3xCPRI5 | -| carrier 5 | 3 | 20 | 4 | | 240 | B-4 | CPRI | LTE | 14.7 | 3xCPRI5 | -| carrier 6 | 3 | 20 | 4 | | 240 | B-30 | CPRI | LTE | 14.7 | 3xCPRI5 | -| carrier 7 | 3 | 20 | 4 | | 240 | B-66 | CPRI | LTE | 14.7 | 3xCPRI5 | -| Total | | | | | | | | | | 324.2 | - -**Table 26: Large site configuration, LTE + Sub 6 NR (massive MIMO) + mmWave NR** - -Note that the FH interfaces provided in last column are only exemplary. Actual interface configuration may vary depending on the radio designs from different vendors. For example, if carrier 2 and 3 is cascaded, the resulting transport can be carried by a CPRI 7 link. - -# Appendix B: Slicing in Backhaul and Midhaul - -Network slicing is a key component of the 5G architecture. It is an end to end capability and a “Network Slice Instances” (NSIs) covers multiple “Network Subnet Slices Instances” (NSSIs) including the “Access Network” or radio network, the mobile “Core Network” (CN) and the “Transport Network”. (TN) - -Figure 18 shows the relationship between NSIs and NSSIs. These can be: - -- 1) 1:1: Each NSI utilises has its own NSSIs which is not shared with other NSIs. -- 2) n:m: NSIs share NSSIs. For example, an NSI has a dedicated access NSSI but uses a shared mobile core NSSI, or multiple NSIs have dedicated access and core NSSIs but use a common transport NSSI. - -![Diagram illustrating NSI to NSSI relationships between AN (Access Network), TN (Transport Network), and CN (Core Network).](677bcb564410628b8b966ad87b394888_img.jpg) - -The diagram illustrates three scenarios of Network Slice Instance (NSI) to Network Slice Subnet Instance (NSSI) relationships across the Access Network (AN), Transport Network (TN), and Core Network (CN). - -- Top Scenario (1:1):** Shows a single NSI (represented by a green line) connecting two AN units (radio towers) through a TN (cloud) to a single 5G Core (CN). This represents a one-to-one relationship. -- Middle Scenario (n:m):** Shows two NSIs (blue and orange lines) connecting two AN units through a shared TN (cloud) to a single 5G Core (CN). This represents an n-to-m relationship where multiple NSIs share a common core NSSI. -- Bottom Scenario (n:m):** Shows two NSIs (red and grey lines) connecting two AN units through a shared TN (cloud) to two separate 5G Cores (CN). This represents an n-to-m relationship where multiple NSIs share a common transport NSSI but have dedicated core NSSIs. - -Diagram illustrating NSI to NSSI relationships between AN (Access Network), TN (Transport Network), and CN (Core Network). - -Figure 18: NSI to NSSI relationships (Source: Cisco) - -The transport infrastructure needs to be able to account for these different eventualities and allow: - -- 1) The transport NSSI to be completely closed. In this case only components connected to the transport NSSI can communicate with each other at the IP level. -- 2) The transport NSSI is partially closed. In this case components connected to the transport NSSI can communicate with each other at the IP layer but also communicate with entities that - -are shared between NSIs. For example, a common AMF or other mobile core components used by multiple slices. - -- 3) Controlled connectivity within a transport NSSI. In this case components connected to same transport NSSI have their IP communication controlled to other entities within the same transport NSSI. For example, radio access components within the slice can communicate with each other and with all UPFs, but UPFs owned by different customers cannot communicate with each other across the transport NSSI. - -Transport slicing is a required capability within the Backhaul network. Figure 19 shows a high-level example of a transport NSSI in a D-RAN architecture and Figure 20 shows a similar example of a transport network NSSI in a C-RAN architecture. Figure 21 shows further detail of an NSSI supporting purely Backhaul and how that an NSSI can have different VPNs for different functions. - -![Diagram of Transport Network NSSI in a D-RAN architecture. It shows three RUs connected to a central 'Backhaul' cloud. The Backhaul cloud is connected to three DCs: Far Edge DC, Edge DC, and Regional DC. The Regional DC contains a UPF. The UPF is connected to an 'N6' cloud. A 'Central DC' box lists 'Common 3GPP control Plane components' and 'Per slice SMFs', connected to the Backhaul cloud via a green line.](a47713c2491e6ce619259ed2f196fd24_img.jpg) - -The diagram illustrates a D-RAN architecture. On the left, three Radio Units (RUs) are connected to a central green cloud labeled 'Backhaul'. The 'Backhaul' cloud is connected to three separate DC blocks: 'Far Edge DC', 'Edge DC', and 'Regional DC'. Each DC block has a small router icon at its connection point to the backhaul. The 'Regional DC' block contains a 'UPF' (User Plane Function). The 'UPF' is connected to a yellow cloud labeled 'N6'. Above the 'Backhaul' cloud, a 'Central DC' box is shown, containing the text 'Common 3GPP control Plane components' and 'Per slice SMFs'. This box is connected to the 'Backhaul' cloud via a green line. - -Diagram of Transport Network NSSI in a D-RAN architecture. It shows three RUs connected to a central 'Backhaul' cloud. The Backhaul cloud is connected to three DCs: Far Edge DC, Edge DC, and Regional DC. The Regional DC contains a UPF. The UPF is connected to an 'N6' cloud. A 'Central DC' box lists 'Common 3GPP control Plane components' and 'Per slice SMFs', connected to the Backhaul cloud via a green line. - -Figure 19: Transport Network NSSI in a D-RAN architecture. Transport NSSI is two discrete networks (Source: Cisco) - -![Figure 20: Transport Network NSSI in a C-RAN architecture. The diagram shows a cloud representing the transport network, divided into four discrete networks: Fronthaul (red), Midhaul (blue), Backhaul (green), and N6 (yellow). On the left, three RUs (Radio Units) are connected to a Far Edge DC containing an O-DU. The O-DU connects to the Fronthaul network. The Fronthaul network connects to an Edge DC containing an O-CU. The O-CU connects to the Midhaul network. The Midhaul network connects to a Regional DC containing a UPF. The UPF connects to the Backhaul network. The Backhaul network connects to a Central DC. The Central DC contains 'Common 3GPP control Plane components' and 'Per slice SMFs'. The Central DC also connects to the N6 network.](27788c2a26d9641e68232a4eff1299b9_img.jpg) - -Figure 20: Transport Network NSSI in a C-RAN architecture. The diagram shows a cloud representing the transport network, divided into four discrete networks: Fronthaul (red), Midhaul (blue), Backhaul (green), and N6 (yellow). On the left, three RUs (Radio Units) are connected to a Far Edge DC containing an O-DU. The O-DU connects to the Fronthaul network. The Fronthaul network connects to an Edge DC containing an O-CU. The O-CU connects to the Midhaul network. The Midhaul network connects to a Regional DC containing a UPF. The UPF connects to the Backhaul network. The Backhaul network connects to a Central DC. The Central DC contains 'Common 3GPP control Plane components' and 'Per slice SMFs'. The Central DC also connects to the N6 network. - -1 -2 -3 -4 - -Figure 20: Transport Network NSSI in a C-RAN architecture. Transport NSSI is 4 discrete networks - -![Figure 21: More details on the Transport Network NSSI in a D-RAN architecture. The diagram shows a cloud representing the transport network, divided into two main discrete networks: 'Backhaul Control Plane (N1, N3, N4)' (light green) and 'Backhaul User Plane (N3, N9)' (dark green). On the left, three RUs are connected to a Far Edge DC. The RUs connect to the Backhaul Control Plane. The Backhaul Control Plane connects to an Edge DC. The Edge DC connects to a Regional DC containing a UPF. The UPF connects to both the Backhaul Control Plane and the Backhaul User Plane. The Backhaul Control Plane connects to a Central DC. The Central DC contains 'Common 3GPP control Plane components' and 'Per slice SMFs'. The Central DC also connects to the N6 network.](bfca6639dd4b8480f2d96d2b61c806d9_img.jpg) - -Figure 21: More details on the Transport Network NSSI in a D-RAN architecture. The diagram shows a cloud representing the transport network, divided into two main discrete networks: 'Backhaul Control Plane (N1, N3, N4)' (light green) and 'Backhaul User Plane (N3, N9)' (dark green). On the left, three RUs are connected to a Far Edge DC. The RUs connect to the Backhaul Control Plane. The Backhaul Control Plane connects to an Edge DC. The Edge DC connects to a Regional DC containing a UPF. The UPF connects to both the Backhaul Control Plane and the Backhaul User Plane. The Backhaul Control Plane connects to a Central DC. The Central DC contains 'Common 3GPP control Plane components' and 'Per slice SMFs'. The Central DC also connects to the N6 network. - -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15 -16 -17 -18 - -Figure 21: More details on the Transport Network NSSI in a D-RAN architecture. D-RAN component of transport NSSI consists two discrete networks, one for control plane interfaces and the other for user plane interfaces (source: Cisco) - -General requirements of the TN have been identified as: - -- 1) Management and life cycle management of transport slice through automation - - a. Creation - - b. Change - - c. Deletion -- 2) Isolation between TN slices - -- 1 a. Performance -- 2 b. Operation -- 3 c. Reliability -- 4 d. Security -- 5 -- 6 3) TN slice OAM -- 7 a. Dynamic discovery -- 8 b. Performance and SLA measurement -- 9 -- 10 4) Virtualization and abstraction -- 11 a. Use virtualization technology -- 12 b. Isolation between slices -- 13 -- 14 5) Multi-domain -- 15 a. With other components of the slice -- 16 b. Between network domains -- 17 - -# 18 Transport engineer's considerations - -19 -20 With the introduction of network slicing transport network engineers need to consider: - -- 21 -- 22 1) Concurrent connectivity between: -- 23 a. WAN to WAN components -- 24 b. WAN to DC based NFs -- 25 c. DC based NFs to DC based NFs (local and remote) -- 26 2) L2 or L3 connectivity models -- 27 3) Closed user groups / VPNs -- 28 4) Multi-point connectivity (any to any) -- 29 5) Point to point connectivity -- 30 6) Point to multipoint. -- 31 7) Flexible connectivity models with the NSSI -- 32 8) Support consistent Quality of Service (QoS) on an end-to-end basis -- 33 9) Management infrastructure on transport devices and DC components to enable device level -- 34 management -- 35 10) Management infrastructure on transport devices and DC components to enable transport slice -- 36 definition and orchestration. -- 37 - -# 1 Appendix C: Delay Asymmetry - -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 -14 -15 -16 -17 -18 -19 -20 -21 -22 -23 -24 -25 -26 -27 -28 - -This section is not intended to describe a requirement, but rather specify a problem that is important for the design of transport networks, and yet can only be defined and solved in cooperation with other organizations such as WG4. - -Fronthaul transport networks could create a delay asymmetry between the downlink and uplink. This delay asymmetry could be caused by - -- i) difference of optical fiber lengths when uplink and downlink use separate fiber (7 m of standard single mode fiber approximatively corresponds to a 34 ns delay), -- ii) the difference of wavelength propagation times when wavelengths are not similar for uplink and downlink (typically 1.3 µm and 1.55 µm wavelength diplex causes a ~33 ns time difference over 20 km of standard single mode fiber ITU-T G.652), -- iii) the difference of processing time (including functions such as time multiplexing, encapsulation, compression) at transport equipment. Other transport functions could contribute to this latency asymmetry. - -We propose to have specifications (Table 27) in function of two type of RU: legacy RU (e.g. option 8 without PTP/SyncE) or O-RU (specified by WG4 based on split 7.2 and with PTP/SyncE). - -We also propose to have separate specification for cases with or without end user geolocation RAN services based on time measurement (OTDOA [observed time difference of arrival] or UTDOA [uplink time difference of arrival]). - -Another factor to be considered is the type of service and/or frequency range as listed in Table 27. - -1 -2 - -| Latency asymmetry up & downlink fronthaul | Without geolocation based on time measurement | With geolocation based on time measurement | | | -|-------------------------------------------|--------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| | | 4G | 5G FR1 | 5G FR2 | -| | | OTDOA accuracy : +/- 130.2 ns
OTDOA resolution : 32.5 ns
(higher-resolution mode based on 16.2 ns) | Not yet specified by 3GPP. This proposed value is based on replica of 4G mechanisms:
OTDOA accuracy: +/-32.5 ns
OTDOA resolution : 8.1 ns
Need to be updated by 3GPP Rel. 16 & 17 | Not yet specified by 3GPP. This proposed value is based on replica of 4G mechanisms:
OTDOA accuracy : +/-8.1 ns
OTDOA resolution : 2 ns
Need to be updated by 3GPP Rel. 16 & 17 | -| Legacy RU | DU could compensate this asymmetry for known value in the margin of +/- 10 000 ns | DU could compensate this asymmetry for known value in the margin of +/- 10 000 ns.

Latency fiber asymmetry < OTDOA resolution 32.5 ns (or 16.2 ns)
Proposition of values by WG9
  • - For negligible impact on geolocation time measurement < 3 ns
  • - For residual impact on geolocation time measurement < 13 ns
| N/A | Not concerned | -| O-RU | O-RAN WG4 proposes absolute and relative time error margin to fiber asymmetry in annex H of WG4.CUS.0-v03.00 | Latency fiber asymmetry < O-RU TE < OTDOA resolution 32.5 ns (or 16.2 ns)

Need to be updated by O-RAN WG4 based on 3GPP TS 36.133v14.3.0 | Latency fiber asymmetry < O-RU TE < OTDOA resolution 8.1 ns

Need to be updated by O-RAN WG4 when 3GPP Rel. 16 & 17 will be available | Latency fiber asymmetry < O-RU TE < OTDOA resolution 2 ns

Need to be updated by O-RAN WG4 when 3GPP Rel. 16 & 17 will be available | - -3 -4 -5 -6 - -Table 27: Delay Asymmetry - diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/0827b9260fe5458dbe416ebfc78c469e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg deleted file mode 100644 index dfa20b311a24ae4dce6ec43951c66a01259999e7..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/08783c875dd39684fee7f2a40b584c64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ddde26fd4eb1b611066f59252b92412da1f3af6454c57c062cb70490c63ee22b -size 4540 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg deleted file mode 100644 index 4065f908a42617457a55670de9aa2e1729135be5..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/0b3d9fe35da3ee0c88f1420bb9ed7a03_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ff750e6a1e89193d3610027741e44d0a52166a51936083ba394db763fa2b8a1c -size 36575 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/171115f072e42b379238ed0dd438e9d7_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/171115f072e42b379238ed0dd438e9d7_img.jpg deleted file mode 100644 index da17c3578bae9a2eedce20e1104250f002ad3638..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/171115f072e42b379238ed0dd438e9d7_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:43cba8bbd82e484f10c60cc6907298c603c61cfb5b4f016e74a052491d643152 -size 37074 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/185df94f4a6a5245323255e844a30ec0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/226f5e462c99b71e08dc9abaa5ae260c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/22af211207188ebc64d7b60ca052b367_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/22af211207188ebc64d7b60ca052b367_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/22af211207188ebc64d7b60ca052b367_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/22f30783614672d201275c116a5d8516_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/22f30783614672d201275c116a5d8516_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/22f30783614672d201275c116a5d8516_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/253600420ae7bd7d0119563b895cbf8a_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/27788c2a26d9641e68232a4eff1299b9_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/27788c2a26d9641e68232a4eff1299b9_img.jpg deleted file mode 100644 index a30552fc681a149486ff824e8caf213841133c40..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/27788c2a26d9641e68232a4eff1299b9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d5388c377c14bdfdf2e2dd54be9a87b1650b776a5ca9cffc42bd474ea6298e3e -size 49396 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg deleted file mode 100644 index dfa20b311a24ae4dce6ec43951c66a01259999e7..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/29f3760c0230631eb03f67030ef65ed0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ddde26fd4eb1b611066f59252b92412da1f3af6454c57c062cb70490c63ee22b -size 4540 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg deleted file mode 100644 index 449cc5a8bb329d4b858712bfaf86dad98f658171..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/2cde062fd82833415971a8bd1a2cafab_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:af78a1f4090277b7cb3ead46a5fc056fd1c7bf538e4d50c5a7de5f087ce9c93c -size 42786 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg deleted file mode 100644 index 3f2af7ad9e8e9b95b7db5f9f19900eb1626637d2..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:12b792dac51b764d8b4302212cc54b870e1977f88724459e7807344ca15b7f50 -size 4552 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/366a77fdefb0097b3289b4a011911390_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/366a77fdefb0097b3289b4a011911390_img.jpg deleted file mode 100644 index 891e846bd6d1d70bea265d90b43e38282b4a8251..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/366a77fdefb0097b3289b4a011911390_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d760d98c7a93621bfd98b51e9124db857ac63f8a8eda688c433f331c2ea028e5 -size 28543 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/38222c3ae003223a67635bfcc6950fbb_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/38866d3f212726e1c8e92001ca0dd6f8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg deleted file mode 100644 index 923104769d64ba7f7e2338a223dfe4b759eb1a3e..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ddbc95f9c289dae73e0ead332068067a973458c0109450ab4adeb0850fb90bbb -size 92352 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/3f727e6c0d6658bc53ea10905c4561dd_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg deleted file mode 100644 index 9417a3f2a2ffeadcc548fa54f3d3a7059ad3df56..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:81aacea7e8afbd8eacd74dfb5e6c98fdb88fb55ad94f761f5404c343cc1e5448 -size 61392 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/4f8349df2ca48959fefb7c42b2bc375e_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg deleted file mode 100644 index ff92e4fbb007289b840b227a824533cefb674577..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/50ef8602c7c9edd2da0e2133e772c2a2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:50dd6dc4312e6f79f776b80e771201ecca2375473fc24056406a907944a5b13f -size 135007 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/55136bc716146672fc680fa05989f1d2_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/55136bc716146672fc680fa05989f1d2_img.jpg deleted file mode 100644 index 8c1d15e7f087b8ceef5b89f643d5b93f958a06dc..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/55136bc716146672fc680fa05989f1d2_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:529cfd6d13c935bace98d91562311c916f123c7f19336fec0f166db3a2b75312 -size 57576 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/5ae3023386ee15fae372871afce28865_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/5ae3023386ee15fae372871afce28865_img.jpg deleted file mode 100644 index c822614451df7d05ce5d7252871b254fba02ad93..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/5ae3023386ee15fae372871afce28865_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:492f26bb10474585f97cc6e619b8eda50c08857e0f434b9631a7881113b565a3 -size 4536 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg deleted file mode 100644 index c22e08c67b9204a37bdde82ca947624c847989b0..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/627c5195eaae3bc7e34cbc4dbdb6f9a8_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:089ca04f958a4d5ed8ad05e6e30dc1a912a7732c899b766d668008cd173869f8 -size 42835 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/6588b1c7f14069d96744b473ad663248_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/6588b1c7f14069d96744b473ad663248_img.jpg deleted file mode 100644 index 6a80d934b6578b70e341e7e6c1bdfa1be145a27d..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/6588b1c7f14069d96744b473ad663248_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e8f842ff2c70dc6264f31527d42cf8545a659597af6c2f4f6d2e8cc2c3e32e50 -size 4539 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/677bcb564410628b8b966ad87b394888_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/677bcb564410628b8b966ad87b394888_img.jpg deleted file mode 100644 index 5f32b6fea65d48db7194d6daba7bc07fc06a5f53..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/677bcb564410628b8b966ad87b394888_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:33cf64df007c02938df403cd4b4925add6e013e2b97383ded6bbdcc69cc18472 -size 47293 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/6a5342571eca4b46338fdfb3c42a8055_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg deleted file mode 100644 index f143c542389c36d5ff07e2ee761e0cb30c54ec5d..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/6a9c5a85a12499d60c5a3a75c643b852_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:06a36f395651a6c25d0c8b178c180d0fda52d26eabacd85bbaccf75cb13aad77 -size 4576 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg deleted file mode 100644 index 6d62c54e6c346d8963cc5ef8ccae1fa667653671..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/705ee99c3c44fd2a1ea6a3348ce8878f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f138fa109e6d143dfbc0415fe99d266ea14c8cf898bfd8793cb18eb5f714e3c9 -size 24935 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg deleted file mode 100644 index fc9dd4dea1379e82707c29c673b6993e7574e026..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/724c7777b608e53be38b12b6fb3c43bc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c8e7db944c3a73ed7216a8e98c233dfc244d06d5f62b9d86247e8f14b8b4c8d2 -size 61153 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg deleted file mode 100644 index f6bd2d9f6537bcc2a693fb2e05311eeaa85b83b5..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/75f0cb39f1cd165dfe4a6aa6c4d9388d_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:24db49ca189977468d8cd1aa3429cef2245cbf9bbb9aaf35c65a705da0598f31 -size 61629 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/77464a47f104d0d647b2414591137b64_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/77464a47f104d0d647b2414591137b64_img.jpg deleted file mode 100644 index 91be471c1d227d1567b565f19baf5e645cc5c723..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/77464a47f104d0d647b2414591137b64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:22c5433e6c9a52449f8c7b7ef46128869f03e813c5882a9ea44692e40cfcccc3 -size 124103 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/78fe18e63ba327b1e224bad8a7c4de54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg deleted file mode 100644 index 6a80d934b6578b70e341e7e6c1bdfa1be145a27d..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/7ccb49293384cf59a3bbe659b053f3cc_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e8f842ff2c70dc6264f31527d42cf8545a659597af6c2f4f6d2e8cc2c3e32e50 -size 4539 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/7d2d1d3870cd224c4430d19334557716_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/7d2d1d3870cd224c4430d19334557716_img.jpg deleted file mode 100644 index 7850d211a99293abc2e4134aa2a5b9814f008344..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/7d2d1d3870cd224c4430d19334557716_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:a0bb2d374b6f420c788b434ec8a8b325e191333f3e3ddeaa698eea19bfd1273a -size 52052 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/7efae06af3af43ffe5d4b956a679cf54_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/7efae06af3af43ffe5d4b956a679cf54_img.jpg deleted file mode 100644 index ecfd9acc69a666b71b6446559a8f1ce921fe5073..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/7efae06af3af43ffe5d4b956a679cf54_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:5bf002d17b1d6da65565ab96eb5e5432d412eb8dfd2b8bd559a536205a2b4c0f -size 60925 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg deleted file mode 100644 index 7458a4869b88d8f112e30bbd717340d56e425872..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/7f1fc760c873afb92a65f08769a2ed85_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:dd63d6c8f122647e08ec0da436525a54c70632fdcc88a4ef840b69bb557cc725 -size 4540 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/802707b774f2d2973b49cea2020e8453_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/802707b774f2d2973b49cea2020e8453_img.jpg deleted file mode 100644 index 9b899c24f8d6b4c56180b22525ea8281932dc9d5..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/802707b774f2d2973b49cea2020e8453_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:e5833c6b637574b2befcbcda9cdd1f2e7adfd01bce90ad75235566128a8513db -size 116751 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/844077b3034f0030b404207db0ad76b4_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/844077b3034f0030b404207db0ad76b4_img.jpg deleted file mode 100644 index dba9cf7f14c3b1f8e2547e56ec7729362d2373e1..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/844077b3034f0030b404207db0ad76b4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ed8dab14cb75ab0715151be5cc54e8182d16b4d8dbe32a8842c9c1dd4cd0a367 -size 22330 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg deleted file mode 100644 index c822614451df7d05ce5d7252871b254fba02ad93..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/8447c5519e85d7a9e029fbf321da4c4f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:492f26bb10474585f97cc6e619b8eda50c08857e0f434b9631a7881113b565a3 -size 4536 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/89100a6476d1d96f22c192db16502fec_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg deleted file mode 100644 index c822614451df7d05ce5d7252871b254fba02ad93..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/8d129c93d18909f0643766f372e9ebf6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:492f26bb10474585f97cc6e619b8eda50c08857e0f434b9631a7881113b565a3 -size 4536 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/8d138b6bf0be359dc7f079db4899bc41_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/8dcca7651accff77ce832523fe2c7e64_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/9156549264d36ead617a1dec7987f970_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/9156549264d36ead617a1dec7987f970_img.jpg deleted file mode 100644 index dfa20b311a24ae4dce6ec43951c66a01259999e7..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/9156549264d36ead617a1dec7987f970_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:ddde26fd4eb1b611066f59252b92412da1f3af6454c57c062cb70490c63ee22b -size 4540 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/9a6ff2584005112f32fbd551cb6f0591_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg deleted file mode 100644 index 8002db8224c440c2e750a9f3ad0790239e919b44..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/9b59a11096b85b2bc74c6f653a354e28_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:d0d31330ebcce60ca560e9ec10e413de23c16974b644e6c43ebde482f409580e -size 4542 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/a47713c2491e6ce619259ed2f196fd24_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/a47713c2491e6ce619259ed2f196fd24_img.jpg deleted file mode 100644 index fcb63b2919acc9c3b81b00fb7b09f337e8df8348..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/a47713c2491e6ce619259ed2f196fd24_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9015349ae0384d9019a7891090ef4de57cbab595454769f1de3e6c6b7cca1203 -size 44924 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/a76a30cf23764f0b907220e7c3c70ce1_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/b235edb1dbe659e2782c9a0e47775ca4_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/b235edb1dbe659e2782c9a0e47775ca4_img.jpg deleted file mode 100644 index f96e2d5ef146c39ddb277a1db9c7c49ad31444c8..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/b235edb1dbe659e2782c9a0e47775ca4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:9f3e23f9aedbfd78a05b6a8496e473e7618bc00c272358b45f160c69f1a5b9dc -size 82973 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg deleted file mode 100644 index a39c8318328ffa070d8fe7254054d1c3638686ec..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/b4b91e1f5ced9a2bc4a7f3b038cf3fb6_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:8992bf8377c9637a10cdfe5d372c02b612515fa49b377978bcee83e4d27f24a2 -size 129688 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg deleted file mode 100644 index acd308d6dc03766f87b4ce92492108fa9b293b0e..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/bfca6639dd4b8480f2d96d2b61c806d9_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:c5f00d9622cdc75a34be036ce2a9f064e01e722add2af7e098195d371157b1e3 -size 51398 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/c389468860cd886ab9c732473e959f0f_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg deleted file mode 100644 index c822614451df7d05ce5d7252871b254fba02ad93..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/c4315e81a5a818379fcf31519a9c2cbe_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:492f26bb10474585f97cc6e619b8eda50c08857e0f434b9631a7881113b565a3 -size 4536 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/cb5f64aa26cee1c05257b7c6bbba7408_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/d879e5f2c388bb87ee9614f63364dcf0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/d90d939bcbf43d474efaeeaa335a635c_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/d90f17b29a73eddf151f51effa8912e0_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/db5ab5d386827a5d5f5fad0f45612b90_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/db5ab5d386827a5d5f5fad0f45612b90_img.jpg deleted file mode 100644 index dfd3d2760058415579b26046c5ff554e27006d88..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/db5ab5d386827a5d5f5fad0f45612b90_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:83b8c3f18f053af5850b53480452bd72205b462c47196a159f90400e758a1aef -size 79745 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg deleted file mode 100644 index c822614451df7d05ce5d7252871b254fba02ad93..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/e11e3fe4228e889a962514269f5a000b_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:492f26bb10474585f97cc6e619b8eda50c08857e0f434b9631a7881113b565a3 -size 4536 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg deleted file mode 100644 index 7aa4d2d8afe76c77ba61a01152c3d32f244d2cbe..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/e22af684d8e56d4c61e61bb5ddac1087_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:b770895d5e62fb257af651fbcc92c1580a8f62b7a6c88a250e05aa3f5ae73329 -size 28264 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/e32e1bcf367a284cc7a4186056810d22_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/e47215539168b9c4f4a14a2fe1a6dd93_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/e511e373339b5f948f239b19e0c37dd4_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507 diff --git a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg b/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg deleted file mode 100644 index 22399f6c5ccef62e2aea9c3adc1135c37e2120e3..0000000000000000000000000000000000000000 --- a/files/WG9/O-RAN.WG9.XTRP-REQ.0-R005-v02.00/images/f250ba4162fe40d8ddfd05b74fa48895_img.jpg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:0a2fd0c378d786847f4f0519dcc732cabe69187c3a9ab0d234b8a2b7013d0e9b -size 4507